Spreadtrum · 10.5.1.3
Bandwidth operation ·
RAN1#124bis · Source verification
the AI's delta
strengthened
vs RAN1#124
Spreadtrum hardened their initial access framework by adding explicit bandwidth confinement requirements: SIB1, Msg2, Msg4, and scheduling PDCCH must be confined within CORESET-0, while Msg1, Msg3, and PUCCH for Msg4 must be confined within the initial uplink BWP. The earlier language proposes directly adopting the NR mechanism for CORESET-0 becomes proposes reusing NR's mechanism,' preserving the stance. The proposal to study discontinuous frequency resources for initial BWP is preserved with identical language. The center frequency misalignment study is preserved, with the SCMC citation now accompanied by agreed asymmetric CBW.' A new structured list of NR BWP lessons appears: BB/RF parameter bloat, complicated SCS switching, redundant BWP types, contiguous-only resource restriction, and DCI-based switching reliability gaps in non-overlapped BWP scenarios. A new procedural requirement for early RAN4 involvement to avoid sub-optimal design is added. The earlier FFS items on dedicated initial BWP for LPWA and multiple initial BWPs for SCMC are dropped.
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 bandwidth operation
Position extracted by AI
Spreadtrum proposes reusing NR's mechanism for determining CORESET-0 via MIB and the concept of initial DL/UL BWP as a starting point for 6GR. They require that SIB1, Msg2, Msg4, and scheduling PDCCH bandwidths be confined within CORESET-0, while Msg1, Msg3, and PUCCH for Msg4 be confined within the initial uplink BWP. They propose studying discontinuous frequency resources for 6GR initial BWP to address operator spectrum fragmentation, and studying central frequency misalignment between DL and UL initial BWP for TDD, citing the SCMC scenario and agreed asymmetric CBW (400MHz DL / 200MHz UL). They identify specific NR BWP lessons including BB/RF parameter bloat, complicated SCS switching, redundant BWP types, contiguous-only resource restriction, and DCI-based switching reliability gaps in non-overlapped BWP scenarios, and insist on early RAN4 involvement to avoid sub-optimal design.
Summary
This Spreadtrum contribution provides 8 proposals and 2 observations on 6GR bandwidth part (BWP) operation across initial access, idle mode, and connected mode, focusing on reusing NR mechanisms while addressing spectrum fragmentation and BWP switching complexity.
Prior contributions at RAN1#124 · 1 doc · Feb 09, 2026
Discussion on bandwidth operation for 6GR
Position extracted by AI
Spreadtrum proposes directly adopting the NR mechanism for determining CORESET-0 information via MIB for 6GR initial access. They propose studying discontinuous frequency resources for initial DL/UL BWP to address the limitation that NR's continuous frequency requirement for BWP/CC restricts effective utilization of operators' discrete spectrum resources. They propose studying the feasibility of center frequency misalignment for DL/UL initial BWP, arguing that NR TDD's alignment requirement may limit 6GR application scenarios, particularly considering SCMC sub-band differences. They further propose that the NR concept of downlink/uplink initial BWP serves as a starting point for 6GR, with additional FFS items on dedicated initial BWP for LPWA and multiple initial BWPs for SCMC.
Summary
This document contains 4 proposals and 2 observations regarding 6GR BWP operation during and after initial access. It addresses discrete spectrum utilization, CORESET-0 configuration, center frequency misalignment for DL/UL BWPs, and dedicated initial BWPs for LPWA and SCMC scenarios.
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.