TDoc file reading error

3GPP RAN WG2 Meeting #130	R2-2504183
St Julian’s, Malta, May 19th – 23rd 2025                                       
Agenda Item:	8.8.3
Source:	InterDigital
Title:	Discussion on Uplink Capacity/Throughput Enhancement for NTN
Document for:	Discussion, Decision

Conclusion
In this contribution the following observations and proposals are made regarding UL Capacity/Cell throughput enhancement:
Proposal 1:	RAN2 assumes;
For DG PUSCH and CG PUSCH type 2, OCC length and OCC index won’t be configured by RRC; and
For CG type 1, OCC length and OCC index are configured by RRC.
Proposal 2: RAN2 define separate UE capabilities for OCC length 2 and OCC length 4, where UE capability for OCC length 2 is a prerequisite for UE capability for OCC length 4. 

3GPP TSG-RAN WG2 Meeting #130	R2-2504276
St Julian’s, Malta, MT 19 – 23 May, 2025
Source: 	Huawei, HiSilicon, Turkcell
Title: 	Discussion on Uplink Capacity Enhancements
Agenda Item:	8.8.3
Document for:	Discussion and decision
1	

Conclusion
This contribution analyses the OCC signalling based on RAN1 progress, and proposes the following:
Proposal 1: OCC index (i.e., the line index of the OCC matrix) and OCC length need to be indicated to the UE.
Proposal 2: For configured grant Type 1, OCC configurations are provided to the UE via RRC signalling. The OCC configuration for dynamic grant or configured grant type 2 should be provided in DCI.
Proposal 3: RAN2 to introduce separate UE capabilities for OCC length 2 and OCC length 4, and UE capability for OCC length 2 is a prerequisite for UE capability for OCC length 4.
4	

3GPP TSG-RAN WG2 Meeting #130	R2-2504352
Malta, Malta, 19th – 23rd May, 2025	


Agenda item:	8.8.3
Source:	Samsung
Title:	On RAN2 aspects of uplink OCC
WID/SID:	NR_NTN_Ph3-Core
Document for:	Discussion and Decision

Conclusion
In this contribution we discussed issues related to uplink capacity/cell throughput enhancements.
Proposal 1: RAN2 can discuss the RRC parameters based on the received parameter list from RAN1.  
Proposal 2: RAN2 confirm OCC is applicable for RACH-less handovers.  

3GPP TSG RAN WG2 Meeting #130	R2-2504391
St.Julians, Malta, May 19th – 23rd, 2025
Agenda Item:	8.8.3
Source:	CMCC	
Title:	Discussion on uplink capacity/throughput enhancement for NR NTN
Document for:	Discussion, Discussion

Conclusion
Based on the discussions mentioned above, in this contribution we provide some discussions on RAN2 aspects about uplink capacity/throughput enhancement for NR NTN and have the following proposals:
Proposal 1: Introduce 2 new UE capabilities to support OCC length 2 and OCC length 4 respectively, for OCC length 4, simultaneously supporting OCC length 2 is mandatory.
Observation 1: RAN1 has agreed that OCC length and OCC sequence for OCC with CG PUSCH Type 1 is configured by RRC higher-layers. And for the OCC sequence applied for OCC DG PUSCH and CG PUSCH Type 2, the sequence is indicated dynamically in DCI.
Proposal 2: For CG PUSCH type 1, it is proposed to introduce a new IE (e.g. occ-v19) to include OCC length and OCC sequence related configuration in PUSCH-Config.
Proposal 3: Wait for RAN1 discussion for the OCC length applied for OCC DG PUSCH and CG PUSCH Type 2.

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

Agenda item:	8.8.3
Source:	Nokia, Nokia Shanghai Bell
Title:	Discussion on UL Capacity and Throughput Enhancement
WID/SID:	NR_NTN_Ph3-Core - Release 19
Document for:	Discussion and Decision
1	

Conclusion
This document has made the following proposals:
Proposal 1: Introduce separate UE capabilities for OCC with length 2 and OCC with length 4. The UE capability for OCC length 2 is a prerequisite for UE capability for OCC length 4. The exact UE capability description can be finalized based on the RAN1 LS on feature list.
Proposal 2: For CG PUSCH Type1, RAN2 defines two RRC parameters to indicate OCC sequence length and OCC sequence index to UE. 
Proposal 3: For DG PUSCH and CG PUSCH Type 2, wait for RAN1’s conclusion on how to indicate the OCC sequence length and OCC sequence index to UE.