R1-2601823 discussion

Discussion on NTN specific requirements and design for GNSS based operation

From Spreadtrum
Status: not treated
WI: FS_6G_Radio
Agenda: 10.7.1
Release: Rel-20
Source: 3gpp.org ↗
Spreadtrum's prior position on 10.7.1 at RAN1#124 · AI-synthesized, paraphrased
verify sources →
Proposes reusing 5G NTN legacy solutions as the starting point for UL frequency synchronization and UL timing advance maintenance. Requires a unified TN/NTN design for cell search procedure, coverage features, HARQ process number/HARQ-ACK feedback disable, maximum SSB index count (Lmax), and cell DTX/DRX mechanism. Proposes studying longer SSB periodicity (160ms or larger values) for NTN with limited simultaneously active beams, and proposes studying OCC-based UL capacity increase with OCC schemes, OCC length, and specific UL channels (PRACH, Msg3, CG-based SDT) in NTN first, applying conclusions to TN. Proposes studying TN energy-saving technologies first, then adapting results to NTN considering time/frequency synchronization, timing relationship, and beam hopping. Supports FDD and HD-FDD for 6G day-1 NTN.

Summary

Spreadtrum presents 12 proposals and 2 observations on 6G NTN design for GNSS-based operation, covering time-frequency synchronization, timing relationships, capacity improvements, beam management, and energy efficiency with a strong emphasis on unified TN/NTN designs.

Position

Spreadtrum proposes reusing 5G NTN solutions extensively, with GNSS-based operation as the baseline mechanism for UL time-frequency synchronization and 5GA NR NTN GNSS resilience outcomes as the starting point for GNSS-degraded and GNSS-free/GNSS-less operation. They prefer Option 1 for scheduling offsets, reusing the k_offset concept from NR. They propose studying longer SSB periodicity up to 160ms or larger values for initial access, and cell DTX/DRX mechanisms for beam hopping. They emphasize unified TN/NTN designs for cell search procedure, maximum SSB index count (Lmax), and energy-saving technologies, with the latter to be studied in TN first then adapted to NTN. They oppose TDD for NTN, supporting only FDD and HD-FDD in 6GR day-1 due to large and variable guard times in satellite scenarios.

Key proposals

Your notes

Private to your account