RAN1 / #124bis / FS_6G_Radio / Verify

Spreadtrum · 10.5.1.2

PRACH and RACH procedure · RAN1#124bis · Source verification
the AI's delta strengthened vs RAN1#124
Spreadtrum hardened their preamble sequence position: they added a procedural gate requiring a structured gap analysis process before any new sequence designs are considered, moving beyond the prior meeting's baseline reuse support. They added a new explicit position capping the number of preambles per RO at 64 and redirecting PRACH capacity increase studies to RO configuration and SBFD mechanisms. They added a new justification layer—'limited commercial deployment of post-Rel-16 NR features'—to support the unified Day-1 framework argument. The MSG3/MSG4 HARQ-ACK PUCCH independent scheduling proposal and the RO-SSB mapping rules for PRACH repetition study from the prior meeting are dropped. The joint coverage configuration/joint coverage request, native SBFD integration, and NR ZC sequence reuse positions are preserved with refined language.
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

R1-2601808 discussion not treated 3gpp.org ↗
Discussion on 6GR PRACH and RACH procedure
Position extracted by AI
Spreadtrum proposes that all necessary PRACH features be integrated into a unified random access framework from 6GR Day-1, citing limited commercial deployment of post-Rel-16 NR features as justification. They propose studying PRACH capacity increases via RO configuration and SBFD rather than increasing the number of preambles per RO beyond 64. For preamble sequences, they prefer reusing NR ZC sequences and require a structured gap analysis process before considering any new sequence designs. They propose a joint configuration for coverage level determination across all random-access-related channels and a joint coverage request from the UE. They support native integration of SBFD into the random access procedure to avoid separate configurations, power control, and RO-to-SSB mapping for SBFD and non-SBFD ROs.
Summary
Spreadtrum presents 2 observations and 17 proposals on 6G PRACH and RACH procedure design, arguing that NR features introduced after Rel-16 have seen limited deployment and advocating for a unified random access framework with all necessary features integrated from 6G Day-1.

Prior contributions at RAN1#124 · 1 doc · Feb 09, 2026

R1-2600113 discussion not treated 3gpp.org ↗
Discussion on 6GR PRACH and RACH procedure
Position extracted by AI
Spreadtrum proposes a unified and integrated PRACH/RACH framework from 6GR Day-1 to avoid the fragmentation and compatibility issues observed in NR Releases 16-20, where enhanced coverage features achieved limited commercial deployment. They require natively supporting random access in SBFD symbols rather than maintaining separate SBFD and non-SBFD procedures as in NR, specifically opposing the separate RO-to-SSB mapping configurations and independent power control parameters currently used for SBFD RO. They propose studying a joint coverage configuration and joint coverage request from UE spanning all related channels during random access, replacing NR's per-channel independent RSRP threshold configuration. They support reusing NR ZC sequences, NR short and long preamble formats, and NR SSB-RO association patterns as baselines, while proposing further study on RO-SSB mapping rules for PRACH repetition and SBFD/non-SBFD joint mapping. They propose removing the NR dependency where MSG3 and MSG4 HARQ-ACK PUCCH scheduling in SBFD symbols is conditional on MSG1 transmission via SBFD, advocating full independent scheduling.
Summary
This document contains 15 proposals and 3 observations from Spreadtrum on 6G PRACH and RACH procedure design, advocating for a unified Day-1 framework that integrates NR features as baseline while natively supporting SBFD and addressing capacity, coverage, and multi-carrier enhancements.
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 strengthened. Always verify critical claims against the original Tdocs linked above.