Spreadtrum · 10.5.4.1
Downlink control channel, scheduling for downlink and uplink transmission ·
RAN1#124bis · Source verification
the AI's delta
shifted
vs RAN1#124
Spreadtrum shifted from proposing study of two-stage DCI structures to a unified/modular DCI framework with Case 1 (single-block) and Case 2 (multi-block) containers, explicitly departing from the single-stage-only positions of other contributors. This replaces their prior two-stage DCI study proposal with a structured container-based alternative. The prior meeting's focus on reducing fallback DCI formats to exactly one DL/UL pair with identical size and fixed RNTI-scrambled field requirements is absent, as is the technical case against NR's four-pair structure and the proposal to narrow group common DCI scope to TPC and energy efficiency. Added: reuse of NR's 140-bit maximum DCI payload and existing DCI size budget, and prioritization of PDCCH energy efficiency design.
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 downlink control channel, scheduling for DL and UL transmission
Summary
{
"summary": "This Spreadtrum contribution discusses downlink control channel and scheduling design for 6GR, presenting 120 proposals and 21 observations across DCI formats, DCI structures, DCI size/budget, L1 signaling for DL/UL scheduling, PDCCH energy efficiency, and two-stage DCI. Key positions include reusing NR's 140-bit maximum DCI payload and existing DCI size budget, supporting a unified/modular DCI framework with Case 1 (single-block) and Case 2 (multi-block) containers, and prioriti
Prior contributions at RAN1#124 · 1 doc · Feb 09, 2026
Discussion on downlink control channel, scheduling for DL and UL transmission for 6GR
Position extracted by AI
Spreadtrum proposes reducing the number of fallback DCI formats to exactly one DL and one UL format with identical size, and requires fields and bit lengths in DCI scrambled by specific RNTIs to be fixed and independent of RRC configurations. They present a technical case against NR's use of four DL/UL unicast DCI format pairs, citing extreme PDCCH blind decoding complexity and cumbersome size alignment procedures. For non-fallback DCI, they propose studying two-stage DCI structures where only first-stage DCI undergoes blind detection and second-stage DCI carries variable payload without blind decoding, specifically to support multi-carrier scheduling and mixed services with better spectrum utilization. They propose identifying and clarifying which functions necessitate group common DCI rather than unicast DCI, and narrow the scope to only TPC-related commands and energy efficiency functions like NES or UE power saving.
Summary
This document from Spreadtrum/UNISOC provides a comprehensive analysis of NR DCI design issues and presents 30 proposals/observations for 6G DCI formats. It identifies key problems like excessive unicast DCI format pairs, missing BWP switching recovery, cumbersome field re-interpretation for control without data, and underused group common DCIs, then proposes a simplified DCI framework centered on unified fallback, scalable non-fallback, and two-stage DCI structures.
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
shifted.
Always verify critical claims against the original Tdocs linked above.