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

Agenda Item:	9.15.8
Source:	Huawei, HiSilicon
Title:	UE features for NTN for NR phase 3
Document for:	Discussion and Decision

Conclusions
In this contribution, the following are proposed:
Proposal 1: Update the FG 65-1-1 for UE supporting of 160ms SSB periodicity, as shown in the Annex:
Update the UE feature as mandatory or remove the FFS before “A UE that supports Rel-19 NR-NTN must support this FG”;
Remove the FFS in the prerequisite column;
Update the column of “Consequence if the feature is not supported by the UE” as “UE does not support the extended default SSB periodicity of 160ms”.
Proposal 2: Merge the FG for PDCCH reception for CSS other than Type0 PDCCH CSS and the FG for SIB1 PDSCH repetition into FG65-1-2.
Proposal 3: Update the FG 65-1-2 as in Annex:
Update the yellow part in the note to make this UE feature applicable to TN;
Remove the square brackets in the first component;
Include the component for PDCCH repetition for CSS other than Type0-CSS and other than Type3-CSS;
Include the component for SIB1 PDSCH repetition within 20 ms duration;
Remove the FFS in the prerequisite column.
Proposal 4: Adopt the FG 65-3-1 and FG 65-3-2 in Annex for UE supporting inter-slot OCC 2 with PUSCH repetition type A and inter-slot OCC 4 with PUSCH repetition type A, respectively.
Proposal 5: Adopt the FG 65-2-1 in Annex for supporting Rel-19 NR HD-FDD operation of (e)RedCap in FR1-NTN bands with the following update. 

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

Agenda Item:	9.15.8
Source:	Ericsson
Title:	On UE features for NR-NTN Phase 3
Document for:	Discussion

1	

Conclusion
Based on the discussion in the previous section we made the following observations:
Observation 1	According to the objectives in the WID, the SSB periodicity extension can only be applicable to UEs operating in non-terrestrial networks.
Observation 2	During initial cell selection, it is not possible to obtain the capability information from the UE on whether it supports extended SSB periodicity of 160 ms or not.
Observation 3	In our understanding, it is not possible to obtain the capability information from the UE on whether it supports the following: i) PDCCH repetition for CSS (except Type 3) and ii) PDSCH repetition for SIB1.
Observation 4	For HD-FDD (e)RedCap, our views on the remaining open issues are as follows:
	Components:
o	FFS: whether to divide this FG into two separate FGs between case 3 and case 4: This depends very much on the Working Assumption (WA) on collision case 4, if it is kept simple and synergies between collision cases 3 and 4 are maintained (i.e., no additional special cases and DL is default priority for both) then RAN1 can consider having a single FG for both collision cases. On the other hand, if collision case 4 becomes more complex (e.g., if the “handling of PDCCH ordered PRACH transmission” becomes a special case), then it is preferred separating collision cases 3 and 4 into independent FGs.
o	FFS: whether to divide this FG into two separate FGs between RRC CONNECTED and INACTIVE state: The potential separation between RRC CONNECTED and INACTIVE state only applies for collision case 3. Given that the behaviour for RRC INACTIVE state was captured as a conclusion rather than as an agreement, then it is sufficient to cite/capture the RRC INACTIVE state aspect for collision case 3 in the “Note” column.
	Prerequisite feature groups: In our understanding HD-FDD is L1 FG 28-3 for both RedCap and eRedCap, thus it is enough indicating 28-23 as prerequisite feature group. FFS, which NTN related prerequisite feature groups are needed.
	Need of FR1/FR2 differentiation: The WID explicitly states “in FR1-NTN bands,” thus we believe that we can capture “FR1 only” in this column.
	Note: Perform the following updates:
o	Note: this FG is for HD-FDD only.
o	Note: Collision case 3 handling is for RRC CONNECTED and INACTIVE states, and Collision case 4 is for RRC CONNECTED state only
	Mandatory/Optional: More discussion is needed around the “FFS: A UE that supports FG 28-3 in NTN band must support this FG”. Our current view is that optionality should be maintained.
Observation 5	For “UL capacity/throughput enhancement for NR-NTN”, it was agreed in RAN1#119 that there will be 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.
Observation 6	According to the objectives in the WID, the PUSCH OCC feature “may be applicable for UEs operating in terrestrial networks based on a common design”.
Observation 7	If the UE capabilities for the PUSCH OCC feature are defined “Per Band”, the feature support in each NTN and TN band can be indicated separately by the UE.


Based on the discussion in the previous sections we propose the following:
Proposal 1	RAN1 strives to keep the number of “UE feature groups” small for NR-NTN.
Proposal 2	As the term “initial cell selection” is used while defining the default periodicity of SS/PBCH blocks assumed by the UE in Section 4.1 of TS 38.213, we propose to use the same terminology in component 1 and any other columns of FG 65-1-1.
Proposal 3	RAN1 to limit the feature group 65-1-1 applicability only to NTN bands, as indicated in the WID objective, i.e., without extending it to TN bands.
Proposal 4	A UE that supports Rel-19 NR-NTN must support FG 65-1-1.
Proposal 5	RAN1 to discuss whether FG 65-1-1 is applicable to UEs indicating supportOfRedCap-r17 (i.e., FG 28-1, FG 28-3) or not.
Proposal 6	RAN1 to limit the feature group 65-1-2 applicability only to FR1-NTN bands, as indicated in the WID objective, without extending it to FR2-NTN and to TN bands.
Proposal 7	RAN1 to strive for introducing link-level enhancements associated with PDCCH CSS (except Type 3) and PDSCH for SIB1 as separate components under the same feature group of 65-1-2.
Proposal 8	RAN1 to capture the updates on the UE capabilities for NR-NTN downlink coverage enhancements as described in Table 1.
Proposal 9	RAN1 to capture the updates on the UE capabilities for “HD-FDD (e)RedCap for NR-NTN” as described in Table 2.
Proposal 10	The PUSCH OCC feature should be applicable both to NTN and TN depending on UE capability.
Proposal 11	The prerequisites for FG 65-3-1 should be “One of {5-14,11-6}”.
Proposal 12	Add RV cycling across OCC groups as a component.
Proposal 13	Add UCI multiplexing and PUSCH dropping based on OCC groups as components.
Proposal 14	RAN1 to capture the UE capabilities for PUSCH OCC as described in Table 3.

4 

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

Source:	vivo
Title:	Discussion on UE features for NTN for NR Phase 3
Agenda Item:	9.15.8
Document for:	Discussion and Decision

Conclusion
In the contribution, we provide our view on UE features for NTN for NR Phase 3, with the following proposals. The list of the detailed UE capabilities is provided in Annex.

Proposal 1: FGs introduced for NR-NTN DL coverage enhancement are only applicable to NTN deployment. FG 26-1 (basic NR NTN FG) can be the prerequisite for these FGs.
Proposal 2: FG 65-1-1 is applicable only to both FR1-NTN and FR2-NTN. 
Proposal 3: FG 65-1-1 is applicable to both FR1-NTN and FR2-NTN.
Proposal 4: FG 65-1-1 is optional without capability, and not reported to gNB.
Proposal 5: FG 65-1-2 and FR 65-1-3 are applicable only to FR1-NTN.
Proposal 6: FG 65-1-2 and FR 65-1-3 are defined as separate FGs.
Proposal 7: FG 65-1-2 and 65-1-3 are optional with capability, and can be reported to gNB.
Proposal 8: A UE capability of supporting SIB1 PDSCH repetition within 20ms duration is introduced.
Proposal 9: A UE capability of supporting Msg4 PDSCH repetition is introduced.
Proposal 10: The FG 65-2-1 should be divided into two separate FGs 65-2-1a and 65-2-1b, for case 3 and case 4 respectively.
Proposal 11: The FG 65-2-1x should not be basic FGs.
Proposal 12: A capability of supporting OCC length 2 for DFT-s-OFDM PUSCH with repetition Type A is introduced.
Proposal 13: A capability of supporting OCC length 4 for DFT-s-OFDM PUSCH with repetition Type A is introduced.

3GPP TSG RAN WG1 #121	R1- 2503405
St Julian, Malta, 19 – 23 May 2025

Agenda item:		9.15.8
Source:	Nokia
Title:	Rel-19 NR-NTN UE features
Document for:		Discussion and Decision

Conclusion
In this contribution we make the following modification proposals to the FGs present in post-RAN1#120bis FG list [1]:


In addition we propose introducing the following new FGs:

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

Agenda item:	9.15.8
Source: 	Spreadtrum, UNISOC
Title: 	Discussion on UE features for NTN
Document for:	Discussion and decision

TDoc file conclusion not found

3GPP TSG RAN WG1 #121		                                  R1-2503598
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:		9.15.8
Source:			Samsung
Title:			UE features for NTN for NR Phase 3
Document for:		Discussion and decision

TDoc file conclusion not found

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

Source:	ZTE Corporation, Sanechips
Title:	Discussion on the UE feature for NR-NTN Phase-3
Agenda Item:	9.15.8
Document for: Discussion

Summary#2 of discussion on Rel-19 NR UE features for NR-NTN Phase 3, RAN1#120bis

3GPP TSG RAN WG1 #121                                 																											R1-2503856
St Julian’s, Malta, May 19th – 23th, 2025
Source: 	CMCC
Title:	Discussion on UE features for NTN for NR Phase 3
Agenda item:	9.15.8
Document for:	Discussion & Decision

Conclusions
In this contribution, we mainly share our views on the feature groups introduced for Rel-19 NR NTN enhancement. The proposals are summarized as follows:
Proposal 1: A mandatory UE capability for the extended SSB periodicity of 160ms can be supported for Rel-19 NR NTN DL coverage enhancements. 
Proposal 2: For NR NTN DL coverage enhancement, the following updates of UE feature group for 160ms SSB periodicity can be supported.
Proposal 3: The following components can be added in the FG 65-1-2.
Support inter-slot repetition of Type-0 PDCCH.
Support receiving enabling/disabling indication in PBCH payload.
Proposal 4: For NR NTN DL coverage enhancement, support to introduce separate UE feature group for Type-0 PDCCH CSS repetition, Type-0A/1/2-PDCCH CSS repetition, SIB1 PDSCH repetition and Msg4 PDSCH repetition in NR NTN.
Proposal 5: For NR NTN DL coverage enhancement, the following UE feature groups can be introduced.
Proposal 6: Introduce the following FG for the support of handling of collision Case 3 and collision Case 4 for half-duplex FDD operation for Rel-19 NR-NTN (e)RedCap UE:
Proposal 7: Adopt the following FGs for NR NTN uplink capacity/throughput enhancement.

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

Source: 	   Xiaomi
Title:	UE features for NTN for NR Phase 3
Agenda item:    9.15.8
Document for:  Discussion and Decision

Conclusions
In this contribution, we present our perspectives on the newly updated UE features and offer the following proposals:
Proposal 1: Adopt the revisions in the annex for NR-NTN downlink coverage enhancement.
Proposal 2: Adopt the revisions in the annex for the support of RedCap and eRedCap UEs.
Proposal 3: Adopt one of FGs {5-14, 5-16, 5-17, 11-6, 30-1, 30-2}, and FG 26-1 as prerequisite FGs of NR-NTN uplink capacity enhancement. 
Proposal 4: Support inter-slot OCC multiplexing for UEs operating in TN based on a common design. 
Proposal 5: Support the differentiation between FR1 and FR2 for the inter-slot OCC multiplexing in TN scenario. 
Proposal 6: Adopt the UE features in the annex for the support of NR-NTN UL capacity enhancement.

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

Source:	OPPO
Title:	Discussion on UE features for NTN for NR Phase 3 
Agenda Item:	9.15.8
Document for:	Discussion and Decision

TDoc file conclusion not found

3GPP TSG RAN WG1 #121			R1-2504357
St Julian’s, Malta, May 19th – 23th, 2025 
 
Agenda Item:	9.15.8
Source:	Apple
Title:	On Rel-19 NR-NTN UE Features 
Document for:	Discussion/Decision

Conclusion
In this contribution, we provided our views on Rel-19 NR-NTN UE features. Our proposals are as follows:

Proposal 1: In FG 65-1-1, 
the component is “Support additional default value (apart from 20 ms value) of 160 ms periodicity of the half frames with SS/PBCH blocks during initial access.”
the prerequisite FG is FG 1-1. 
there is no need for gNB to know if the feature is supported by a UE.
a UE that supports Rel-19 NR NTN does not have to support this FG. 

Proposal 2: Introduce FG 63-1-3 of PDCCH repetition for type 0A/0B/1/1A/2/2A PDCCH CSS.

Proposal 3: In FG 65-1-2, 
the component is “Support reception of PDCCH repetition for Type0 PDCCH CSS of searchSpaceZero configured within MIB pdcch-ConfigSIB1. 
the prerequisite FG is FG 3-1.
there is no need for gNB to know if the feature is supported by a UE.
this FG is applicable to TN. 

Proposal 4: In FG 65-1-3,
the component is “Support reception of PDCCH repetition for type 0A/0B/1/1A/2/2A PDCCH CSS other than searchSpaceZero”
the prerequisite FG is FG 3-1.
gNB needs to know if the feature is supported by a UE.
the FG is defined per band.
the FG is applicable to TN. 

Proposal 5: Introduce a NR-NTN UE feature for PDSCH with SIB1 repetition.

Proposal 6: Introduce a NR-NTN UE feature for PDSCH with Msg4 repetition.

Proposal 7: Introduce a NR-NTN UE feature for inter-slot OCC-based PUSCH repetition with OCC length 2. 

Proposal 8: Introduce a NR-NTN UE feature for inter-slot OCC-based PUSCH repetition with OCC length 4. 

Proposal 9: Introduce a NR-NTN UE feature for handling collision case 3 and collision case 4 for HD-FDD (e)RedCap UE operation in FR1. 

Proposal 10: Don’t introduce separate UE feature for collision case 3 for UE in RRC INACTIVE state. 

Proposal 11: The prerequisite for FG65-2-1 include FG26-1 and one of {FG28-3, FG28-3 and FG48-1, FG28-3 and FG48-2}. 

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


Agenda item:	9.15.8
Source: 	Qualcomm Incorporated
Title: 	UE features for NR NTN
Document for:	Discussion / Decision

UE features for NR NTN

In this contribution, we present our views on Rel-19 UE features for NR NTN based on agreements made in RAN1 120bis [1] and new progress in the standardardization.

In last meeting, there were discussions on the applicability in FR2 for several UE features including 65-1-1, 65-1-2 and 65-1-3. On this issue we note the following.

Observation 1: 
System-level enhancements for FR2 are in the scope of the WI but link-level enhancements for FR2 are not in the scope of the WI [2].
Rel-19 link level enhancements have been developed with FR1 in mind including link budget analyses and specific designs. Feasibility of the related features in FR2 need additional study.

Based on the above, we propose to remove the text mentioning FR2 bands forUE feature 65-1-2 and 65-1-3.

Proposal 1:  Remove the text mentioning FR2 bands for UE feature 65-1-2 and 65-1-3 as below:


In addition, we propose to add the repetition of SIB1 PDSCH in feature 61-1-2 and to add a new UE feature for Msg 4 repetition.

Proposal 2: Add the repetition of SIB1 PDSCH repetition in feature 64-1-2 and a new feature for Msg4 repetition as below.



Additional inputs on UE features for UL capacity enhancements are in the following table. We would like to highlight that we would propose to add GSO/NGSO differentiation since, in line with the discussion in previous meetings, the RF requirements for OCC would be based on DMRS bundling, which are different for GSO and NGSO.


Proposal 3: Add new UE features as shown in the following table.



References

R1-2502967, “Session Notes of AI 9.15.8”, NTT Dococmo, RAN1#120bis, April 2025.
RP-24330, “Revised WID: Non-Terrestrial Networks (NTN) for NR Phase 3,” Thales and CATT, RP#106, Dec. 2024. 

TDoc file conclusion not found

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

Source:	NTT DOCOMO, INC.
Title:	Discussion on UE features for R19 NR NTN
Agenda Item:	9.15.8
Document for:	Discussion and Decision

Conclusion
In this contribution, we presented our views regarding UE features for R19 NR NTN. Based on the discussion in this contribution, the following proposals were made.
Proposal 1: Update FG 65-1-1 as follows.
Proposal 2: Update FG 65-1-2 as follows.
Proposal 3: Define FG 65-1-3 as follows.
Proposal 4: Define FG 65-1-4 as follows.
Proposal 5: Define FG 65-1-5 as follows.
Proposal 6: Define FG 65-1-6 as follows.
Proposal 7: Update FG 65-2-1 as follows.
Proposal 8: Define FGs 65-3-1 and 65-3-2 as follows.

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

Agenda item:	9.15.8
Source: 	Moderator (NTT DOCOMO, INC.)
Title: 	Summary of discussion on Rel-19 NR UE features for NR-NTN Phase 3
Document for:	Discussion and Decision

Conclusions

TDoc file reading error

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

Agenda item:	9.15.8
Source: 	Moderator (NTT DOCOMO, INC.)
Title: 	Summary#2 of discussion on Rel-19 NR UE features for NR-NTN Phase 3
Document for:	Discussion and Decision

Conclusions
Proposals not agreed in this week: