6G downlink waveform study narrows after Nokia and Apple beat back DFT-s-OFDM push
Nokia, Ericsson, Samsung, InterDigital, OPPO and Apple got DFT-s-OFDM deprioritized for general downlink use; LG, CATT, Google and ZTE keep it alive only for satellite scenarios.
Source meetings for this article (11)
Meetings in this article’s source material. Inclusion does not mean that every meeting approved every decision.
- SA#1109 Dec 2025 – 12 Dec 2025 · Baltimore · 3GPP ↗
- RAN#1108 Dec 2025 – 11 Dec 2025 · Baltimore · 3GPP ↗
- CT#1108 Dec 2025 – 9 Dec 2025 · Baltimore · 3GPP ↗
- RAN1#12317 Nov 2025 – 21 Nov 2025 · Dallas · 3GPP ↗
- RAN4#11717 Nov 2025 – 21 Nov 2025 · Dallas · 3GPP ↗
- SA3#12517 Nov 2025 – 21 Nov 2025 · Dallas · 3GPP ↗
- SA5#16417 Nov 2025 – 21 Nov 2025 · Dallas · 3GPP ↗
- SA5#16313 Oct 2025 – 17 Oct 2025 · Wuhan · 3GPP ↗
- RAN3#13017 Nov 2025 – 21 Nov 2025 · Dallas · 3GPP ↗
- SA2#17217 Nov 2025 – 21 Nov 2025 · Dallas · 3GPP ↗
- RAN2#13217 Nov 2025 – 21 Nov 2025 · Dallas · 3GPP ↗
Nokia, Ericsson, Samsung, InterDigital, OPPO and Apple pushed to drop DFT-s-OFDM as a general 6G downlink waveform, arguing its lower power-amplifier stress isn't worth the added scheduling complexity; LG Electronics, CATT, Lenovo, Thales, Google and ZTE wanted to keep studying it, especially for satellite links. The moderator sided with the drop camp for phone-to-network transmissions like PDSCH and PDCCH, narrowing the debate to whether DFT-s-OFDM survives at all for non-terrestrial networks — a much smaller prize than the original proposal.
6G's timing structure is inheriting 5G almost wholesale: the 10 ms radio frame, 14-symbol slot and normal cyclic prefix all carry over from 5G NR, and 3GPP confirmed slot-based scheduling as the 6G baseline. The one crack in that continuity is a proposal, backed by the meeting moderator, to drop the extended cyclic prefix for general use entirely — pushing it into niche corners like satellite and sensing. For chipmakers, this means most of the 5G timing hardware and logic can be reused, with new engineering effort concentrated on genuinely new features rather than rebuilding the clock.
Control-channel coding shows the same pattern at a different layer: for messages within 5G's existing size limits (140 bits for DCI, 1706 bits for UCI), 3GPP agreed to reuse the 5G NR Polar code outright — a call backed by 16 of 20 and 16 of 21 contributing companies respectively. That leaves the real fight over messages that exceed those limits, where options on the table include Polarization-Adjusted Convolutional codes, 16QAM modulation, or a 1024-length Polar sequence, but RAN1 first wants confirmation from other work items that such oversized messages are even needed.
The sharpest open fight is architectural: how should a 6G phone handle a 400 MHz channel near 7 GHz, four times wider than typical 5G mid-band channels? Qualcomm, CMCC, Nokia, Ericsson and eight others want to study a single-RF-chain design using one 16k-point FFT; MediaTek, DOCOMO, Samsung and OPPO prefer two RF chains covering 200 MHz each; Apple, Xiaomi, vivo and Spreadtrum/UNISOC argue plain 200 MHz carrier aggregation, as used in 5G today, is good enough and a dedicated 400 MHz radio is overkill. The outcome will decide whether 6G devices need new, more expensive RF hardware just to use the widest 6G channels.
RAN4 is due to settle the smallest maximum bandwidth a low-tier 6G device must support — a choice among 5, 10 or 20 MHz — by June 2026, a decision that will set the floor for how cheap and power-efficient a 6G IoT sensor can be. Separately, watch for RAN#113 in September 2026, when the plenary resumes deciding whether 6G needs formal 'device types' at all, a choice that determines whether 6G repeats LTE's rigid UE-category system or moves to a more flexible, capability-based model.
The decisions behind this
6G downlink waveform study focuses on CP-OFDM enhancements, deprioritizes DFT-s-OFDM for general use
The 3GPP RAN1 working group, responsible for the physical layer, is studying waveforms for 6G. A core debate is whether to support DFT-s-OFDM as an additional downlink waveform alongside the baseline CP-OFDM, which is used in 5G. Proponents argue DFT-s-OFDM's lower Peak-to-Average Power Ratio (PAPR) could improve coverage and base station power efficiency, especially for Non-Terrestrial Networks (NTN) like satellites. Opponents argue the gains are marginal, it adds complexity, and restricts multi-user scheduling flexibility.
A coalition of companies, including Nokia, Ericsson, Samsung, InterDigital, OPPO, and Apple, proposed deprioritizing or discontinuing the study of DFT-s-OFDM for general downlink use (like PDSCH and PDCCH). They cited a lack of meaningful coverage or network energy saving gain over CP-OFDM with transparent PAPR reduction techniques, increased base station and phone complexity, and potential spectral efficiency loss.
Another coalition, including LG Electronics, CATT, Lenovo, Thales, Google, and ZTE, proposed continuing the study. They argued DFT-s-OFDM is needed to increase power amplifier output power, is beneficial for NTN and coverage-limited scenarios, and can be multiplexed with existing 5G NR signals.
The meeting's moderator (Nokia) proposed an agreement to 'Deprioritize discussion on DL DFT-s-OFDM for PDCCH/PDSCH/PBCH communication' and to continue discussing it only for NTN communication. The document containing this proposal and the summary of company positions has a status of 'noted', meaning it was taken note of but not formally approved as a meeting decision. The reason for the moderator's proposal is not stated in the meeting documents.
| Continue studying DL DFT-s-OFDM for coverage/NTN | Deprioritize or drop DL DFT-s-OFDM study |
|---|---|
| LG Electronics · CATT · Lenovo · Thales · Google · ZTE · vivo · NEC · Huawei · Panasonic10 companies | Nokia · Ericsson · Samsung · InterDigital · OPPO · Apple · Sharp · IMU8 companies |
The working group is leaning against adopting DFT-s-OFDM as a general-purpose downlink waveform for 6G, favoring enhancements to the existing CP-OFDM technology instead. The debate is now narrowly focused on whether DFT-s-OFDM has a role in specific non-terrestrial (satellite) scenarios. This suggests 6G downlinks will likely evolve from 5G's CP-OFDM foundation rather than introducing a major waveform change for most devices.
6G to support multiple duplexing modes and flexible uplink/downlink pairing
This document is a moderator's summary of proposals for 6G spectrum requirements. It compiles input from many companies but does not record a final decision from the meeting. The topic concerns how 6G should handle the direction of data flow (duplexing) and the pairing of uplink and downlink frequencies.
A coalition of 19 operators proposed that '6G RAT shall support multiple duplexing options including FDD, TDD, SDL incl. Half-Duplex (e.g. for IoT)' and '6G RAT shall support decoupling of the uplink and the downlink (to allow any UL and DL pairing)'. For non-terrestrial networks, a coalition of 16 space companies noted that 'paired bands can apply to all orbits, unpaired bands are typically restricted to the Low Earth Orbits' and listed support for FDD, TDD, and Half Duplex FDD.
Qualcomm proposed an alternative approach: 'Instead of flexible pairing, consider introducing targeted new bands for intended pairings.'
The summary presents a consolidated 'Proposal' stating: '6GR aims to support flexible spectrum resources with multiple duplexing options for DL and UL for carriers/bands to ensure optimal spectrum efficiency.' The document status is 'revised', and no record of a plenary vote on these specific proposals is provided.
| Support full decoupling of UL/DL and multiple duplex modes | Prefer targeted new bands for specific pairings |
|---|---|
| Deutsche Telekom · Vodafone · Orange · Telecom Italia · Turkcell · Spark NZ · Odido · BT · Bouygues Telecom · Telefonica · Telia Company · SK Telecom · KPN · Rakuten Mobile · CK Hutchison · Telstra · Telenor · KT Corp. · KDDI · Jio Platforms · Boost Mobile Network21 companies | Qualcomm Incorporated1 company |
The operator-led proposal, if eventually agreed, would give network architects maximum flexibility. Decoupling uplink and downlink could allow an operator to use a low-band frequency for uplink (better for coverage) and a mid-band frequency for downlink (better for capacity) without them being a pre-defined pair, potentially improving efficiency. The debate with Qualcomm's proposal centers on whether this full flexibility is necessary or if simpler, pre-defined band combinations are sufficient.
- Deferred6G coverage targets to be defined using Maximum Coupling Loss (MaxCL)RP-253778
- Deferred3GPP to study how to ensure mandatory 6G features are actually deployedRP-253874
- DeferredThree technical options proposed for 400 MHz bandwidth support around 7 GHzR1-2509482
- DeferredMaximum 6G carrier bandwidths proposed for sub-6 GHz spectrumR1-2509482
- DecidedMacro and micro cell definitions retained for 6G scenariosRP-253777
- DeferredMulti-TRP operation not introduced as a specific 6G deployment scenarioRP-253777