Skip to main content
Radio: Bands, RF & NR Evolution · 3GPP Quarterly June 2025

128-port MIMO codebooks split vendors over how much of the old design survives

Nokia and Samsung back a clean-slate restriction scheme for 128-port codebooks; Huawei and ZTE say it only tweaks the legacy design, and the moderator says one side is simply wrong.

65 decisions42 work areas4,986 contributions

Plenary cycle

SA#108 · RAN#108 · CT#108

Prague · 9 Jun 2025 – 13 Jun 2025

Source meetings for this article (16)

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

Nokia and Samsung want the 128-port Type-II codebook restriction to be a clean, group-based replacement for the old two-level scheme; Huawei, ZTE and Fraunhofer insist it should only modify the second level of what already exists. The moderator sided with Nokia's camp — 'Understanding 1 is correct and Understanding 2 is incorrect' — but no consensus followed, and the moderator warned the whole restriction feature for Release 19 could be dropped if the deadlock continues.

Phones with three transmit antennas got eight competing technical proposals on precoding, reference-signal linking and power scaling, backed by Samsung, OPPO, ZTE, vivo and Huawei among others; Google and CATT questioned whether the changes are needed at all. None were adopted, so chipset vendors building 3TX uplink still lack a finalized rulebook covering four separate specification documents (TS 38.211, 38.212, 38.213, 38.214).

Coordinated multi-cell transmission (CJT) saw a rerun of a familiar fight: ZTE and Qualcomm wanted delay-offset reporting refined to 0.1–0.2 cyclic-prefix steps for tighter timing alignment across base stations, while Nokia argued the resulting resolution would be under 1 nanosecond — finer than a phone can distinguish from ordinary timing error. The chair had already flagged this proposal for rejection if positions didn't shift, and they didn't.

Low-band carrier switching — where a phone alternates between a primary FDD carrier and a downlink-only SDL carrier instead of true aggregation — got firmer footing: a 40ms bitmap pattern and a fixed switching gap when returning from SDL to FDD, with gap duration configurable per direction based on a phone's reported retuning time (35µs or 140µs). But the opposite direction, FDD to SDL, still has three rival proposals from MediaTek/Nokia/Ericsson (gap always at the end of FDD), vivo/OPPO/Huawei (network-configured location), and Samsung/CATT (gap always on SDL) — meaning base station vendors can't yet build a single, predictable retuning procedure.

RAN1#121 in Malta is where several of these threads converge: companies must decide whether phones measuring candidate-cell channel quality for fast Layer-1 mobility can be configured with more active CSI-RS resources than their declared capability — Fujitsu, Nokia, Qualcomm, Ericsson and DOCOMO want phones to pick which signals to measure themselves, while ZTE, vivo, Lenovo and LG want any over-configuration treated as an error. The outcome decides whether operators can broadcast a rich, one-size-fits-all measurement configuration or must tailor it precisely to each device.

The decisions behind this

Deferred
NR MIMO Phase 5
R1-2502357

Proposal for finer delay offset reporting in coordinated transmission fails to gain consensus

The topic is enhancing reporting for Coordinated Joint Transmission (CJT), where multiple base stations transmit to one phone. A proposal sought to add finer dynamic range values ({0.1CP, 0.2CP}) for reporting delay offsets between transmitters, in addition to the already agreed values of {0.5CP, CP}. Proponents like ZTE argued this is essential for performance, especially for multi-user MIMO, as current quantization is too coarse. Opponents like Nokia questioned the usefulness, noting that with existing high resolution, the proposed step would be under 1 nanosecond, and a phone cannot separate propagation delay from timing error, which could cause many 'out-of-range' reports. The Chairman had instructed that if the situation did not change from the previous meeting, the proposal would not be discussed again. The meeting did not adopt the proposal.

Support adding {0.1CP, 0.2CP} dynamic rangeNot support
ZTE · Qualcomm · Samsung · ETRI · NTT DOCOMO · NTT CORP · Huawei/HiSi · Ericsson · Tejas · Sony · KDDI · TCL · CATT · vivo · Google · HONOR · Xiaomi17 companiesNokia/NSB · Lenovo/MotM · Rakuten · Apple4 companies
Why it matters

The decision maintains the previously agreed delay offset reporting range. This means the standard will not mandate phones to support ultra-fine delay measurements at the sub-nanosecond level for CJT. Networks will have to work within the 0.5CP granularity, which may limit the precision of timing alignment for the most demanding multi-user MIMO scenarios envisioned by some vendors.

Deferred
NR MIMO Phase 5
R1-2502357

Dispute continues over the design of 128-port Type-II codebook restriction scheme

The topic is the Codebook Subset Restriction (CBSR) for the enhanced Type-II codebook supporting up to 128 ports. CBSR lets the network tell the phone to exclude certain beam combinations from its reports to reduce overhead. There is a fundamental disagreement between two camps of companies on how the new Rel-19 CBSR relates to the old one. One group (Understanding-1) believes the new scheme is a fresh, group-based design that replaces the legacy one to reduce signaling overhead. The other group (Understanding-2) believes it is an enhancement that modifies only the second level of the legacy two-level scheme. The moderator stated that 'Understanding 1 is correct and Understanding 2 is incorrect,' noting the agreed design was to replace the legacy CBSR due to excessive overhead. No consensus was reached to resolve the dispute.

Support Understanding-1 (new group-based scheme replaces legacy)Support Understanding-2 (enhances second level of legacy scheme)
Nokia/NSB · Samsung · Lenovo/MotM · Google · HONOR · NEC · Apple · CMCC · CATT · vivo · Sharp · Ericsson12 companiesIDC · NTT DOCOMO · NTT CORP · Xiaomi · Huawei/HiSi · Qualcomm · ZTE · Fraunhofer IIS/HHI · Spreadtrum9 companies
Why it matters

This is a critical blocking issue for finalizing the 128-port Type-II codebook. The two understandings lead to different specifications and phone behaviors. Until resolved, the standard cannot be completed, potentially delaying the availability of advanced 128-port MIMO features that depend on precise and efficient CSI reporting.

  • DecidedNo Consensus to Add Per-Resource Slot Offsets for CRI-Based CSIR1-2503011
  • DeferredNo consensus on defining CSI processing units for CSI acquisition after cell switch commandR1-2504889
  • DeferredNo consensus on defining CSI processing units for early CSI acquisition before cell switchR1-2504889
  • DeferredProposal to limit complexity of candidate cell CSI acquisitionR1-2502089
  • DeferredRestrictions defined for advanced CSI reporting during cell switchingR1-2502091
  • DeferredDeadlock on Codebook Subset Restriction Design for Rel-19 Type-II CodebookR1-2503011
Quotations are verbatim from moderator summaries in the 3GPP archive. Document numbers link to the original files. Back to the full report.