Spreadtrum · 10.7.1
NTN specific requirements and design for GNSS based operation ·
RAN1#124bis · Source verification
the AI's delta
maintained
vs RAN1#124
Spreadtrum preserved their core position on reusing 5G NTN solutions as baseline, unified TN/NTN designs for cell search procedure and Lmax, longer SSB periodicity studies (160ms+), and studying TN energy-saving technologies first then adapting to NTN. They hardened their scheduling offset preference to explicit Option 1 with k_offset reuse from NR. Their GNSS position refined slightly: GNSS-based operation remains baseline, but they now explicitly scope 5GA NR NTN GNSS resilience outcomes as the starting point for GNSS-degraded and GNSS-free/GNSS-less operation. The OCC-based UL capacity increase proposal for PRACH, Msg3, and CG-based SDT is dropped from the current text. Their opposition to TDD hardened with explicit reasoning citing large and variable guard times in satellite scenarios, maintaining FDD/HD-FDD only support for 6GR day-1.
AI-synthesized from contributions · all text is paraphrased
Every position summary on this site is generated by an AI from the actual Tdoc contributions. This page shows you the exact source documents the AI read to produce the summary above, so you can verify it yourself. Click any Tdoc ID to view its detail page, or click "3gpp.org ↗" to read the original on the official 3GPP server.
Contributions at RAN1#124bis · 1 doc
Discussion on NTN specific requirements and design for GNSS based operation
Position extracted by AI
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.
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.
Prior contributions at RAN1#124 · 1 doc · Feb 09, 2026
Discussion on 6GR NTN specific requirements and design for GNSS based operation
Position extracted by AI
Spreadtrum proposes reusing 5G NTN legacy solutions as the starting point for UL frequency synchronization and UL timing advance maintenance in 6G. They require 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. They propose studying longer SSB periodicity (160ms or larger values) for NTN with limited simultaneously active beams, and support FDD and HD-FDD for 6G day-1 NTN. They propose studying OCC-based UL capacity increase with OCC schemes, OCC length, and UL channels (PRACH, Msg3, CG-based SDT), with NTN study first and conclusions applied to TN. They propose studying TN energy-saving technologies first, then adapting results to NTN considering time/frequency synchronization, timing relationship, and beam hopping.
Summary
Spreadtrum provides 2 observations and 13 proposals on 6G NTN design, focusing on leveraging 5G NTN legacy solutions as a starting point while promoting unified TN/NTN designs where applicable. The document covers synchronization, timing, initial access, coverage, capacity, signaling overhead, beam management, duplexing, and energy efficiency.
How this was derived
The AI extracted the "position extracted" field above directly from each Tdoc during summarization.
For the delta summary at the top, the AI compared Spreadtrum's consolidated stance at RAN1#124bis
against their stance at RAN1#124 and classified the change as
maintained.
Always verify critical claims against the original Tdocs linked above.