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

Agenda Item:	9.15.10
Source:	Huawei, HiSilicon
Title:	UE features for IoT-NTN TDD mode
Document for:	Discussion and Decision

Conclusions
The proposals made in this contribution are summarized below:
Proposal 1: Release-17 feature group 2-1b can be the prerequisite of FG2-1 with a note to clarify that it does not imply a TDD UE should always support FDD operation. 
Proposal 2: The following components are added for the basic feature groups:
SIB1-NB is dropped in non-D NB-IoT subframes;
NPRACH periodicities of 40ms and 80ms are not supported in NB-IoT NTN TDD mode, instead, periodicities of 90ms and 180ms are supported.
Proposal 3: Release-17 feature groups 2-2a and 2-3a can be inherited in Release-19 IoT-NTN TDD.
Proposal 4: Release-18 feature groups 2-1e-1, 2-1f-1, 2-1g-1, 2-1e-2, 2-1f-2, 2-1g-2 and 2-2b can be inherited in Release-19 IoT-NTN TDD mode.
Proposal 5: For the granularity of feature groups, per UE is preferred.
Proposal 6: The basic feature group should be optional with capability signaling, and a UE must indicate the support of this FG if it supports IoT NTN TDD in 1616-1625.5 MHz MSS band.

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

Source:	vivo
Title:	Discussion on UE features for IoT-NTN TDD mode
Agenda Item:	9.15.10
Document for:	Discussion and Decision

Conclusion
In this contribution, we provide our views on NB IoT-NTN TDD mode, and have the following proposal.
Proposal 1. Agree on the FG in table1 with the following clarifications
Prerequisite feature group is Rel-17 2-1b
Capture SIB1-NB dropping and new periodicities of PRACH resources in the components
Type is set to per band
No need of FDD/TDD differentiation
Add ‘TDD only’ in the note

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

Agenda item:		9.15.10
Source:	Nokia
Title:	Views on Rel-19 NTN for Internet of Things (IoT) TDD mode UE features
Release:	Rel-19
Document for:		Discussion and Decision

Conclusion
In this contribution we have proposed our views on Rel-19 NTN for Internet of Things (IoT) TDD mode UE features, and we have made the following proposal.
Proposal 1: Adopt the proposed FGs and components in Table 1 for Rel-19 UE features for NTN for Internet of Things (IoT) TDD mode. 
Proposal 2: Adopt the proposed FGs as per band as it is special for band 1616-1626.5 MHz MSS band.

3GPP TSG RAN WG1 #121		                                  R1-2503600
St Julian’s, Malta, May 19th – 23th, 2025
Agenda item:		9.15.10
Source:			Samsung
Title:			UE features for IoT-NTN TDD mode
Document for:		Discussion and decision

TDoc file conclusion not found

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

Source:	ZTE Corporation, Sanechips
Title:	Discussion on the UE feature for IoT-NTN TDD
Agenda Item:	9.15.10
Document for: Discussion

TDoc file conclusion not found

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

Source: 	Xiaomi
Title:	Discussion on UE features for IoT-NTN TDD mode
Agenda item: 	9.15.10
Document for:	Decision

Conclusions
In this contribution, we present views on UE features for IoT-NTN TDD mode, we have the following proposals and revisions to the UE feature table:
Proposal 1: Add in FG 2-1 component 7) 90ms and 180ms NPRACH periodicities are supported in NB-IoT NTN TDD mode instead of 40ms and 80ms.
Proposal 2: Set Rel-17 FG 2-1b as a prerequisite FG for Rel-19 FG 2-1. If needed, capture the following sentence to the Rel-19 FG 2-1 Note column "The application of timeline in component 13 and component 16 in Rel-17 FG 2-1b shall be subject to the fulfillment of the components in FG 2-1"
Proposal 3: The granularity for capability indication is "per UE". 
Proposal 4: The FG 2-1 only operates in TDD only mode and the relevant columns shall be filled accordingly.
Proposal 5: The FG type is mandatory if a UE indicates support of the 1616-1626.5 MHz MSS allocated band.

Introduce the following revisions to the FG for IoT-NTN TDD mode

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

Agenda item:	9.15.10
Source: 	OPPO
Title: 	Discussion on UE features for IoT-NTN TDD mode
Document for:	Discussion and decision

Conclusion
This contribution provides our views on UE features for R19 IoT-NTN TDD mode, and the following proposals are made:
Proposal 1: Capture dropping SIB1-NB in non-D NB-IoT subframes as the component of the FG for IoT-NTN TDD mode.

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

Conclusion
In this contribution, we provided our views on Rel-19 IoT-NTN TDD mode UE features. Our proposal is as follows:
Proposal 1: Adopt the IoT-NTN TDD mode UE features in above table.   

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

Agenda item:	9.15.10
Source: 	Qualcomm Incorporated
Title: 	UE features for IOT NTN TDD mode
Document for:	Discussion / Decision

TDoc file conclusion not found

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

Source:	NTT DOCOMO, INC.
Title:	Discussion on UE features for for IoT-NTN TDD mode
Agenda Item:	9.15.10
Document for: 	Discussion and Decision

Conclusion
Based on the discussion in this contribution, the following proposal was made.
Proposal 1: Introduce the following FG for IoT-NTN TDD mode.

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

Agenda item:		9.15.10
Source:	Nordic Semiconductor ASA
Title:					On R19 TDD IoT-NTN features
Document for:		Discussion and Decision

TDoc file conclusion not found

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

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

Conclusions
TBD

TDoc file reading error