Skip to main content
AI/ML & Analytics · 3GPP Quarterly June 2026

AI-based channel feedback locks its data formats but not its quality metric

128 antenna ports and a fixed quantization codebook are settled; Apple, Huawei and Ericsson still want one CQI formula, while Qualcomm and vivo want vendors free to choose their own.

23 decisions20 work areas604 contributions

Plenary cycle

SA#112 · RAN#112 · CT#112

Singapore · 8 Jun 2026 – 12 Jun 2026

Source meetings for this article (11)

Meetings in this article’s source material. Inclusion does not mean that every meeting approved every decision.

3GPP QuarterlyThe next issue by email, at most eight a year.

Phones that use AI to compress channel feedback will report signal quality (CQI) using whatever method their chipset maker prefers — an outcome Apple, NTT DOCOMO, Huawei, Ericsson, CATT, ZTE and Samsung all objected to. They wanted one fixed calculation so operators could compare phones fairly; Qualcomm, vivo, OPPO, Nokia and eight others argued no single method works because the phone never sees the exact precoding matrix the network reconstructs from its report. The dispute repeated across three separate meeting sessions without resolution, leaving RAN4 — the group that writes conformance tests — unable to define what counts as an acceptable CQI implementation.

The scale of the new feature is settled: AI-compressed feedback will cover up to 128 antenna ports, rank 4 and 19 subbands, matching the massive-MIMO configurations already used in 5G-Advanced. Reports will travel in the same two-part uplink control structure as legacy high-resolution feedback, with CQI and rank in the better-protected first part and the AI-compressed detail in the second — reusing a design pattern from Enhanced Type II codebooks rather than inventing a new one.

For training data collected by the network from phones, companies picked amplitude-phase quantization (3 bits for amplitude, 4 bits for phase) over the alternative real-imaginary format, reusing the quantization tables already defined for 5G's Enhanced Type II codebook. When no custom codebook is exchanged, phones fall back to a standard set of values — 0.125, 0.375, 0.625 and 0.875 for 2-bit quantization — guaranteeing that phones and networks from different vendors interpret the same compressed numbers the same way.

Model monitoring will run on fast physical-layer (L1) signaling rather than the slower RRC-based (L3) layer: Nokia, Apple, Samsung, MediaTek, Xiaomi and LG argued L3 signaling lacks the latency control needed to catch a degrading AI model before it hurts link performance. Left unresolved is whether phones need their own beam-restriction logic (Codebook Subset Restriction) when preparing feedback for AI compression — Huawei, CATT, ZTE, KT, OPPO and vivo say the network can filter unwanted beams on its own, while Qualcomm, Ericsson, Nokia and Apple want it studied first, since it existed in earlier 5G releases.

RAN1 #126 will run the beam-restriction study companies agreed to at this meeting, comparing signal leakage and throughput when phones restrict beams themselves against when the network filters alone, using four restricted beams as the test case. The result decides whether AI-based CSI feedback needs new phone-side complexity for beam handling or whether that job stays entirely on the network side — a question that also bears on how RAN4 eventually tests these devices.

The decisions behind this

Deferred
AIML for NR air interface Phase 2
R1-2604680

CQI definition for AI-based CSI feedback remains unresolved

For CSI feedback using a two-sided AI/ML model, the Channel Quality Indicator (CQI) tells the network the data rate the phone expects. The core question is how the phone should calculate this CQI when it doesn't know the exact precoding matrix the network will reconstruct from its compressed report. A group of companies, led by the moderator (Qualcomm), proposed a conclusion stating that three implementation methods are allowed: calculating CQI based on the target CSI, calculating it with UE adjustment, or calculating it based on the output of a CSI decoder. The proposal notes that specification impact is 'For Further Study' (FFS).

The meeting did not adopt this proposal. Multiple companies, including Apple, NTT DOCOMO, Huawei, Ericsson, and CATT, objected. They argued that leaving CQI calculation fully up to UE implementation would make the reported CQI useless to the network and create confusion for RAN4, the group responsible for performance requirements. These companies pushed for specifying a single calculation method, with options like using the target CSI directly (Option 1a) or with adjustment (Option 1b). The reason for the lack of agreement is not recorded in the document.

Allow multiple UE implementation methods for CQISpecify a single CQI calculation method
Qualcomm (Moderator) · vivo · OPPO · Lenovo · Southeast University · Panasonic · InterDigital · Sharp · Toyota · Nokia · CMCC · TCL12 companiesApple · NTT DOCOMO · Huawei · Ericsson · CATT · 1Finity · Ofinno · LG Electronics · ZTE · Spreadtrum · Samsung11 companies
Why it matters

Without a decision, the fundamental link between AI-compressed channel state information and the reported link quality remains undefined. This stalls progress on finalizing the standard for this feature, as network vendors and phone chipset makers cannot align on how performance will be guaranteed.

Deferred
AIML for NR air interface Phase 2
R1-2604679

CQI calculation for AI-based CSI feedback will be left to UE implementation

This topic is about how a phone should calculate the Channel Quality Indicator (CQI) when using a new AI-based method for Channel State Information (CSI) feedback. In this 'two-sided' AI model, the phone compresses the CSI, sends it, and the network reconstructs it. The phone does not know the exact precoding matrix the network will use, making CQI calculation tricky.

RAN1, the working group responsible for the physical layer, concluded that for CSI feedback via the two-sided model, the following implementations are allowed for the phone to provide a CQI for the reconstructed precoding matrix: 'Calculate the CQI based on target CSI', 'Calculate the CQI based on target CSI with adjustment by UE', and 'Calculate the CQI based on the output of a CSI decoder'. The group noted that the specification impact of this is 'For Further Study'.

Flexible UE implementationNeed a single, clear method
vivo · OPPO · Lenovo · Southeast University · Panasonic · InterDigital · Sharp · Toyota · Nokia · CMCC · TCL11 companiesApple · NTT DOCOMO · Huawei · Ericsson · CATT · 1Finity · Ofinno · LG Electronics · ZTE9 companies
Why it matters

Phone manufacturers will have flexibility in how they implement CQI calculation for this advanced AI-based feedback, rather than being forced into a single standardized method. This could lead to different performance trade-offs between vendors. However, network operators and testing groups (RAN4) will need to define appropriate performance requirements to ensure the reported CQI is useful, despite the varying implementation methods.

  • DeferredCQI definition for AI/ML CSI feedback is left to UE implementationR1-2604678
  • DeferredCompanies propose specification options for UE-side beam restriction, no decision takenR1-2604680
  • DeferredStudy on necessity of UE-side beam restriction (CBSR) continues, no decision madeR1-2604678
  • DeferredStudy on UE-side beam restriction for AI/ML CSI is deferred, with a new evaluation planR1-2604677
  • DeferredStudy on necessity of UE-side beam restriction for AI CSI feedback continuesR1-2604679
  • DeferredNo agreement on how to monitor AI/ML CSI model performance, question sent to RAN2R1-2604677
Quotations are verbatim from moderator summaries in the 3GPP archive. Document numbers link to the original files. Back to the full report.