3GPP TSG-RAN2 Meeting#130												R2-2503375
Malta, Malta, May 19th - May 23rd, 2025

Agenda Item:	8.20.1
Source:	OPPO
Title:	Discussion on R4 LS on UE Architecture Type-4a/4b
Document for:	Discussion, Decision

Conclusion
Proposal 1	R2 confirm the new capability only needs to cover the support of new BS signaling part, while the associated intraBandNR-CA-non-collocated-r18, interBandMRDC-WithOverlapDL-Bands-r16, supportedMIMO-CapabilityDL-MRDC-r15, maxNumberMIMO-LayersMulticastPDSCH-r17 are defined as pre-requisite to reflect the RF/RRM performance.
Proposal 2	R2 sends reply LS to R4, to clarify R2 capability signaling assume fallback applicability, and check whether MIMO layer combination of <1,4> and <2,4> can be supported for UE architecture type-4b, and whether MIMO layer combination of <1,4> can be supported for UE architecture type-4a.
Proposal 3	R2 sends reply LS to R4, to check if any concern if the new BS signaling is applied for UE configured with maxMIMO-Layers with value larger than 2, and smaller than or equal to 4for at least one corresponding serving cell.

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

Agenda Item:	8.20.1
Source: 	Xiaomi, Intel Corporation, Oppo, Ericsson, Nokia, Qualcomm Incorporated, ZTE, Sanechips, CATT, T-mobile USA, CHTTL
Title:  	Discussion on DL MIMO layer capability for 6Rx UE
Document for:	Discussion and decision

Conclusion
Based on above discussion, we have following observations and proposals:
Proposal 1: Introduce a new capability for maximum 6 DL MIMO layer as optional capability. 
Observation 1: 8 DL MIMO layer can only be supported via 8 Rx receiver, which is only applicable for FWA. Generic signaling design in RAN2 specifications is used to indicate 8 DL MIMO layer in maxNumberMIMO-LayersPDSCH without differentiating FWA and handheld UE.
Proposal 2: RAN2 specification will not capture 6 DL MIMO layer is only applicable for FWA.
Proposal 3: A UE supporting 6 DL MIMO layer shall indicate both maxNumberMIMO-LayersPDSCH and maxNumberMIMO-LayersPDSCH-v1900 for a CC. When both capabilities are reported, the network which is able to decode the maxNumberMIMO-LayersPDSCH-v1900 ignores the maxNumberMIMO-LayersPDSCH.

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

		
Source:	CATT 
Title:	Consideration on CSSF optimization
Agenda Item:	8.19
Document for:	Discussion and Decision

Conclusion
According to section 2, we observe and propose:
Observation 1: The CSSF optimization introduced in RAN4 allows the UE to measure only one serving CC per band if multiple serving CCs are configured for measurement in the same band, which can reduce FR2-1 SSB based L3 measurement delay for connected mode.
Proposal 1: Introduce a new MAC CE to indicate the specific SCC per-band for CSSF optimization.

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

		
Source:	CATT 
Title:	Discussion on Rx BSF optimization for NR RRM Ph5
Agenda Item:	8.20.1
Document for:	Discussion and Decision

Conclusion
According to section 2, we observe and propose:
Observation 1: For the UE supporting multi-Rx simultaneous reception on single carrier, FR2-1 L3 measurement delay can be reduced by optimizing Rx BSF (beam sweeping factor) if UE performs Rx beam sweeping in parallel on different panels.
Observation 2: In order to reduce UE power consumption, triggering condition to activate/deactivate multi-Rx for L3 measurement which is configured by RRC signalling was agreed in RAN4.
Observation 3: The scenario of Rx BSF optimization is limited to a FR2 serving cell, without CA/DC.
Observation 4: There are still open issues on Rx BSF optimization which may impact RAN2 signalling design.
Proposal 1: RAN2 waits for RAN4 further progress for Rx BSF optimization.

TDoc file reading error

TDoc file unavailable

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

Source: KDDI Corporation, Samsung
Title:　 Discussion on singling design for Non-collocated feature
Agenda Item:	8.20.1	RAN4 
Document for:	Discussion

Conclusion
Proposal 1: RAN2 confirm to specify one capability and one BS signaling for NR-CA
Proposal 2: RAN2 discuss and confirm that one capability and one BS signaling for EN-DC, type 4a and type 4b capability can be differentiated by legacy capability, MIMO-CapabilityDL-r10 on E-UTRA carrier can work effectively. If not, separate capabilities and BS signaling may be considered.
Proposal 3: RAN2 confirm that a Rel-19 UE supporting type 4a/4b should also support and report type2 capability.
Proposal 4: RAN2 confirms that, when both the gNB and UE support the Rel-19 signaling associated with the non-collocated feature, the gNB may provide Rel-19 signaling. If the Rel-19 signaling is not supported by either the gNB or UE, the gNB using Rel-18 signaling associated with the Rel-18 non-collocated feature (if supported).  
Proposal 5: RAN2 discuss the pros and cons of the two options below and clarify that the UE follow the Rel-18 behavior has less demerits when 
the gNB does not support Rel-19 BS signaling, or
the gNB supports Rel-19 BS signaling but does not provide it to the UE,
That is, when configured with 4 MIMO layers, the UE applies the type 1 (collocated) requirements as specified in Rel-18.
	Op1: Rel-19 UE applies the type 4 (non-collocated) requirements without Rel-19 BS signaling
	OP2: Rel-19 UE follow the Rel-18 behavior without Rel-19 BS signaling e.g. applies the type 1 (collocated) requirements
Proposal 6: RAN2 discuss the pros and cons of the two options and select one of the options as a way forward  
Op1. Rel-19 UE applies the type 4 (non-collocated) requirements with Rel-19 BS signaling
Op2. Rel-19 UE applies either type1 (collocated) or type4 (non-collocated) requirements based on explicit Rel-19 BS signaling with value 0/1
Proposal 7: RAN2 discuss and decide whether to introduce new Rel-19 signaling, rather than extending the existing Rel-18 signaling to support 4 MIMO layers non-collocated requirements.


4. 

3GPP TSG-RAN WG2 Meeting #130	R2-2503942
St. Julian’s, Malta, 19 - 23 May, 2025
Source: 	Huawei, HiSilicon
Title: 	Discussion on CSSF optimization and Rx BSF optimization for NR RRM ph5
Agenda Item:	8.20.1
Document for:	Discussion and decision

Conclusion
In this contribution, we discussed NR RRM ph5 enhancements, and propose the following:
CSSF enhancement
Proposal 1: Introduce an indication in measConfig to enable/disable CSSF enhancement.
Proposal 2: If the new indication is present, based on RAN4 requirements, UE may not measure a serving cell and the corresponding intra-frequency neighbour cells even if servingCellMO is configured for this serving cell.
Proposal 3: RAN2 to down-select from the following:
Option 1: As indicated in RAN4 LS, NW indicates the SCC(s) to be measured.
Option 2: When neither PCC nor PSCC is in the band, if there are multiple SCells configured with SSB based measurements it is up to UE implementation which SCell to measure; if there are multiple SCells configured with servingCellMO and none of them is configured with SSB based measurements, it is up to UE implementation which SCell to measure. This will be not be captured in RAN2 spec.
Proposal 4: Adopt the TP in the Annex for CSSF enhancement.
Rx BSF enhancement
Proposal 5: Introduce a threshold in measConfig, to control whether multi-Rx based L3 measurement can be activated. If the measured PCell RSRP/RSRQ is below the corresponding threshold, multi-Rx based L3 measurement shall be activated if supported by the UE.
Proposal 6: Adopt the TP in the Annex for Rx BSF enhancement.

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

Agenda item:	8.20.1
Source:	Huawei, HiSilicon
Title:	Discussion on simultaneous Tx-Rx capability for TDD-SDL and TDD-FDD combinations
Document for:	Discussion and Decision

Conclusion
In this paper, we the RAN2 impacts based on RAN4 LS on simultaneous Tx-Rx capability for TDD-SDL and TDD-FDD combinations, and have the following proposals.
Proposal 1: RAN2 confirms that no RAN2 specification impacts for FDD-TDD CA band combination.
Proposal 2: The simultaneousRxTxInterBandCA is extended to cover TDD-SDL BC from Rel-15.
Proposal 3: If the Proposal 2 can be agreed, the similar changes for simultaneousRxTxInterBandCA are applied to simultaneousRxTxInterBandENDC, simultaneousRxTxInterBandCAPerBandPair and simultaneousRxTxInterBandENDCPerBandPair.

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

Agenda item:	8.20.1
Title:	Discussion on Rx BSF optimization
Source:	ZTE Corporation
Document for:	Discussion and Decision

Conclusion
Based on the above, RAN2 is requested to discuss and agree on the following observations and proposals:
Proposal 1: 	Multi-Rx L3 measurement is only applicable when the UE is configured with FR2-1 PCell only, and there is only one SSB-based MO configured, the MO is FR2-1 carrier and can be different from PCell’s frequency.
Proposal 2: 		Separate RSRP threshold and RSRQ threshold are introduced. If both are configured, it means the UE activates multi-Rx L3 measurement when both of the thresholds are satisfied.
Proposal 3: 	Do not consider TimeToTrigger and Hysteresis in activation condition.
Proposal 4: 	RAN2 assumes the UE at least deactivates multi-Rx L3 measurement when the threshold becomes not satisfied. FFS on other conditions, pending RAN4.
Proposal 5: 	Adopt the RRC TP in Annex.

TDoc file reading error

3GPP TSG-RAN WG2 Meeting #130	Tdoc R2-2504188
St Julian’s, Malta, May 19 – 23, 2025
              
Agenda Item:	8.20.1
Source:	Ericsson
Title:	Simultaneous Tx-Rx capability for TDD-SDL and TDD-FDD
Document for:	Discussion, Decision
1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	No impact in RAN2 from RAN4 agreements on simultaneous Rx/Tx capability for FR1+FR1 FDD-TDD CA combinations.
Based on the discussion in the previous sections we propose the following:
Proposal 1	A note is added to simultaneousRxTxInterBandCA (from Rel-19) to clarify that TDD-FDD also includes the case of TDD-SDL.
Proposal 2	Discuss how to update simultaneousRxTxInterBandCAPerBandPair to be applicable to all band pairs and if any update is also needed for simultaneousRxTxInterBandCA.

3GPP TSG-RAN WG2 Meeting #130	Tdoc R2-2504189
St Julian’s, Malta, May 19 – 23, 2025
              
Agenda Item:	8.20.1
Source:	Ericsson
Title:	Additional aspects on Type 4 for non-collocated deployment
Document for:	Discussion, Decision
1	

Conclusion
In the previous sections we made the following observations: 
Observation 1	RAN2 has the guideline to avoid defining functionality that has no RRC configuration but is dependent on capability bits.
Based on the discussion in the previous sections we propose the following:
Proposal 1	Type 4a/b capabilities for EN-DC are defined separately.
Proposal 2	For EN-DC, Type 4a and Type 4b are configured separately.

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

Agenda item:	8.20.1
Source: 	Huawei, HiSilicon, MediaTek Inc., Samsung, Apple
Title: 	Discussion on 6 DL MIMO layers
Document for:	Discussion and Decision
1. 

Conclusion
In this contribution, we have following proposals:
Proposal 1: Introduce a new optional per-CC capability to indicate support of maximum 6 DL MIMO layers only for FWA UE.
Proposal 2: If the new capability is included, the legacy maxNumberMIMO-LayersPDSCH shall be set to fourLayers for the corresponding component carrier. The network ignores the maxNumberMIMO-LayersPDSCH if the new capability is included.
The potential modifications are provided in the TPs of TS 38.306 and TS 38.331.
4. 

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

Source:        ZTE Corporation
Title:           Consideration on the Type 4 UE for Non-collocated Deployment
Agenda item:   8.20.1
Document for:  Discussion and Decision

Conclusion and proposals
With the above analysis, we have the following proposals:

Proposal 1: RAN2 to confirm that the signaling should support to indicate the below 3 sub-cases when maxMIMO-layers=4.
Subcase 1: The BS doesn’t support non-collocated deployment with maxMIMO-layers=4, e.g. the legacy BS. For this case, if the maxMIMO-layers=4, it’s collocated (Type-1);

Subcase 2: The BS supports non-collocated deployment with maxMIMO-layers=4, and it configures it as non-collocated. For this case, if the maxMIMO-layers=4, it’s non-collocated (Type-2);

Subcase 3: The BS supports non-collocated deployment with maxMIMO-layers=4, but it configures it as collocated. For this case, if the maxMIMO-layers=4, it’s collocated (Type-1).


Proposal 2: To distinguish the subcase 1 from the subcase 2/3, a parameter (e.g. nonCollocatedTypeNR-CA-r19/ nonCollocatedTypeMR-DC-r19) is needed to indicate whether the BS supports non-collocated deployment with maxMIMO-layers=4.

Proposal 2a: When this parameter (e.g. nonCollocatedTypeNR-CA-r19/ nonCollocatedTypeMR-DC-r19) is absent, it means the BS doesn’t support non-collocated deployment with maxMIMO-layers=4 and thus it’s collocated (Type-1);

Proposal 3: To further distinguish subcase 2 from the subcase 3, 2 values shall be introduced when the parameter (e.g. nonCollocatedTypeNR-CA-r19/ nonCollocatedTypeMR-DC-r19) is present, e.g. value 1 means subcase 2, while value 2 means subcase 3.

Proposal 4: For the NR-CA, a similar capability to the legacy intraBandNR-CA-non-collocated-r18 can be introduced for the type 4 UE. While for the EN-DC case, a similar capability to the legacy requirementTypeIndication-r18 r18 can be introduced..