Spreadtrum · 10.3.1
Channel coding ·
RAN1#124bis · Source verification
the AI's delta
refined
vs RAN1#124
Spreadtrum refined their LDPC extension position with specific quantitative constraints: max code block size hardened to 8448 and information columns hardened to 22, replacing the prior meeting's general high consistency language. They added a new technical case against increasing information columns to 33 or 44, citing scheduling complexity, fragmented memory access, and reduced parallel processing efficiency with reduced lifting sizes such as 192 or 256 — parameters and degradation mechanisms not named at RAN1_124. Their Polar DCI position expanded: the prior single proposal (remove D-CRC interleaver, reuse 1024 UCI sequence) is now structured into two prioritized options — code block segmentation (Option 1, new) and interleaver removal (Option 2, preserved) — with seven other candidate options explicitly acknowledged but not preferred. The prior stance on reducing maximum iterations without performance degradation is dropped from the current position.
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 channel coding for 6GR
Position extracted by AI
Spreadtrum/UNISOC proposes that the LDPC extension beyond NR range retain the maximum code block size of 8448 and 22 information columns in the base graph, arguing that the 22×384 configuration fully preserves the NR LDPC structure and enables maximum reuse of existing implementations without altering base graph design, decoding schedule, or memory access patterns. They present a technical case against increasing the number of information columns to 33 or 44, citing increased scheduling complexity, more fragmented memory access, and reduced parallel processing efficiency, especially when combined with a reduced lifting size such as 192 or 256. For Polar code design for DCI with payload size larger than NR range, they propose prioritizing code block segmentation (Option 1) and interleaver removal (Option 2) as the options offering the highest degree of compatibility with the existing design architecture, while seven other candidate options including Mid-Block Termination-Assisted Polar Codes, zero-embedding, PAC codes with zero-padding, and new data integrity check mechanisms are acknowledged but not preferred.
Summary
Spreadtrum/UNISOC presents 3 proposals and 2 observations on 6G channel coding, covering data channel LDPC extension and control channel Polar code design for payloads beyond NR range. The document argues for preserving NR LDPC parameters (maximum code block size of 8448 and 22 information columns) and prioritizing code block segmentation plus interleaver removal for larger DCI payloads.
Prior contributions at RAN1#124 · 1 doc · Feb 09, 2026
Discussion on channel coding for 6GR
Position extracted by AI
Spreadtrum/UNISOC proposes that LDPC extension for 6G should maintain high consistency with existing NR LDPC, with only minor software or hardware modifications, and argues implementation-based solutions should receive priority consideration if they can meet data rate requirements. They specifically propose prioritizing reduction of the maximum number of iterations without significantly affecting performance for data channel coding. For control channel coding, they propose directly reusing NR Polar code design for control information within NR range, and if DCI payload size must exceed the 164-bit limit, they propose removing the D-CRC interleaver and reusing the existing 1024 sequence for UCI to extend the DCI payload upper bound.
Summary
This document from Spreadtrum/UNISOC presents three proposals on 6G channel coding, focusing on LDPC extension for data channels and Polar code extension for control channels, emphasizing minimal impact on existing hardware/software and prioritizing backward-compatible solutions.
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
refined.
Always verify critical claims against the original Tdocs linked above.