5G phones will get channel feedback within milliseconds of connecting
A 3 ms clock and a dedicated MAC-CE slot field for early channel reports are agreed; Huawei, ZTE, NTT DOCOMO and Sony lost on retransmissions.
Source meetings for this article (8)
Meetings in this article’s source material. Inclusion does not mean that every meeting approved every decision.
- SA#11315 Sept 2026 – 18 Sept 2026 · Madrid · 3GPP ↗
- RAN#11314 Sept 2026 – 17 Sept 2026 · Madrid · 3GPP ↗
- RAN1#12624 Aug 2026 – 28 Aug 2026 · Maastricht · 3GPP ↗
- RAN4#12024 Aug 2026 – 28 Aug 2026 · Maastricht · 3GPP ↗
- SA5#16824 Aug 2026 – 28 Aug 2026 · Prague · 3GPP ↗
- RAN3#13324 Aug 2026 – 28 Aug 2026 · Maastricht · 3GPP ↗
- SA2#17624 Aug 2026 – 28 Aug 2026 · Prague · 3GPP ↗
- RAN2#13524 Aug 2026 – 28 Aug 2026 · Maastricht · 3GPP ↗
Huawei and Samsung wanted 5G Advanced phones to transmit with deliberately noisier signals — up to 6% Error Vector Magnitude instead of today's tighter limits — in exchange for higher uplink power and better cell-edge coverage, with base stations cleaning up the distortion using Digital Pre-Distortion receivers. Nokia, Ericsson, Qualcomm, ZTE and Vodafone blocked it for this release, pointing to simulated gains swinging wildly from -0.8 dB to 4.2 dB and unresolved questions about testing multiple phone models at once. The feature now moves into 6G study instead, delaying any commercial deployment by years unless a compatible design later gets back-ported to 5G.
The bigger, quieter change is how fast a phone gets useful channel feedback after it first connects. Instead of waiting for a full RRC setup, the network will now broadcast measurement configurations in system information, let the phone declare which ones it supports in message 3 of random access, and trigger the actual sounding and CSI reporting through a MAC control element in message 4. Companies agreed the report's computation clock starts at a slot boundary exactly 3 milliseconds after the phone acknowledges that message, giving chipset makers one predictable number to design around instead of a moving target.
A parallel fight was about where the timing command lives. Ofinno, Huawei, ZTE, Xiaomi, vivo, Qualcomm and seven others won a dedicated MAC-CE field for the slot offset, with the phone ignoring the standard K2 timing in the uplink grant; the new field does the same job as K2. CATT, MediaTek, Samsung, LG, Panasonic and Sharp argued for deriving the offset from existing delay values or a configured list instead. The network gets more direct control over exactly when the first channel report lands — useful for scheduling, at the cost of one more timing path for implementers to test.
For networks running massive MIMO with 48 to 128 antenna ports, 3GPP agreed to let CSI reference signals be spread thinly across frequency — as sparse as one-eighth of resource elements per port — with RRC signaling telling the phone exactly which resource blocks carry them. New CSI subband sizes (6, 12, or 24 PRBs depending on channel bandwidth) were tailored to these low-density signals. This cuts reference-signal overhead on large arrays, freeing resource elements for actual user data, though the underlying resource-block group sizing was left untouched.
Two fights stayed open. Retransmission handling for MSG4-triggered measurements got no rule at all — a 15-company bloc including Samsung, Qualcomm, Nokia and vivo blocked new mechanisms proposed by Huawei, ZTE, NTT DOCOMO and Sony, so phones will simply re-measure on any retransmission, redundant or not. And Samsung's proposal to trigger channel feedback with a single shared state across all newly activated secondary cells still faces resistance from Nokia, Ofinno and NTT DOCOMO, who want per-cell flexibility — a question that determines how much signaling overhead SCell activation carries once it reaches specification.
The decisions behind this
Phones can report support for multiple early-SRS configurations during random access
When a phone connects to the network from idle or inactive mode, it can be configured to send channel measurements (SRS/CSI) very early in the process to speed up MIMO setup. This topic covers how the phone tells the network which measurement configurations it supports.
A proposal (Proposal 1.1.3C) was supported by a large majority of companies, including Samsung, Nokia, Huawei, Qualcomm, and MediaTek. It states that during the random access procedure (in MSG3), the phone can indicate its support for none, one, or multiple resource/report configurations that were broadcast by the network in system information. The exact signaling format (e.g., using a bitmap or a MAC-CE) is left for RAN2, the working group responsible for protocols, to decide.
This was recorded as an agreement in the RAN1#126 chair's notes.
| Support UE indication of multiple configurations | Prefer alternative indication method |
|---|---|
| Samsung · Nokia · vivo · Spreadtrum · CATT · MediaTek · Qualcomm · NTT DOCOMO · ETRI · Ofinno · 1Finity · LG · NICT · Huawei · NEC · InterDigital · Sharp17 companies | Xiaomi · ZTE · Panasonic3 companies |
This allows for more flexible network deployment. Operators can broadcast several possible measurement configurations (e.g., for different phone antenna capabilities), and each phone can signal which ones it can use. This is more efficient than a one-size-fits-all approach and helps ensure that early channel estimation works for a wider variety of devices.
Early CSI reporting slot offset for idle phones will be set by a dedicated MAC-CE field
The topic is about how to schedule the first channel state report when a phone connects to the network from idle or inactive mode. RAN1, the working group responsible for the physical layer, agreed on a method to indicate the timing for this report. For aperiodic CSI reporting triggered when a UE transitions from IDLE/INACTIVE to CONNECTED mode, a separate field in the MAC-CE (Media Access Control - Control Element) in message MSG4 will indicate the slot offset for the scheduled PUSCH (Physical Uplink Shared Channel). The UE will ignore the K2 timing value indicated by the PUSCH Time Domain Resource Allocation (TDRA) field in the uplink grant. This agreement was reached after considering alternatives where the offset was derived from a sum of delays or from a configured list.
This was recorded as an agreement in the RAN1#126 chair's notes.
| Separate MAC-CE field for slot offset | Alternative methods (sum of K2+Z2 or configured list) |
|---|---|
| ZTE · Qualcomm · Huawei · Xiaomi · vivo · NEC · NTT DOCOMO · Sony · ETRI · Spreadtrum · Ofinno · Google · Nokia · InterDigital · NICT15 companies | CATT · MediaTek · Panasonic · Samsung · LG Electronics · Sharp6 companies |
This provides the network with direct, unambiguous control over when the first channel quality report is sent after a phone wakes up, simplifying scheduling and ensuring the report arrives when the network is ready to process it. It avoids potential ambiguity from reusing other timing fields.
- DeferredNo consensus on handling retransmissions for early MIMO triggersR1-2606464
- DecidedTimeline for early CSI computation defined relative to slot boundaryR1-2606465
- DeferredNo agreement to enhance handling of MSG4 retransmissions for early triggeringR1-2606465
- DeferredNo consensus to enhance handling of MSG4 retransmissions for early triggeringR1-2606466
- DecidedSlot offset for early-CSI report PUSCH will be indicated directly in MAC-CER1-2606465
- DeferredNo extra handling for retransmissions when triggering early CSI from idle modeR1-2606467