128-antenna phones get a smaller timing extension than some vendors wanted
vivo, Google and Xiaomi pushed to scale CSI processing deadlines fourfold for 128-port MIMO; 3GPP settled on a factor of 2 after Samsung, ZTE and Huawei preferred no change at all.
Source meetings for this article (10)
Meetings in this article’s source material. Inclusion does not mean that every meeting approved every decision.
- SA#10712 Mar 2025 – 14 Mar 2025 · Incheon · 3GPP ↗
- RAN#10712 Mar 2025 – 14 Mar 2025 · Incheon · 3GPP ↗
- CT#10712 Mar 2025 – 13 Mar 2025 · Incheon · 3GPP ↗
- RAN1#12017 Feb 2025 – 21 Feb 2025 · Athens · 3GPP ↗
- RAN4#11417 Feb 2025 – 21 Feb 2025 · Athens · 3GPP ↗
- SA3#12017 Feb 2025 – 21 Feb 2025 · Athens · 3GPP ↗
- SA5#15917 Feb 2025 – 21 Feb 2025 · Sophia-Antipolis · 3GPP ↗
- RAN3#12717 Feb 2025 – 21 Feb 2025 · Athens · 3GPP ↗
- SA2#16717 Feb 2025 – 21 Feb 2025 · Athens · 3GPP ↗
- RAN2#12917 Feb 2025 – 21 Feb 2025 · Athens · 3GPP ↗
Companies disagree over how much extra processing time a phone should get when it has to crunch Channel State Information from 128 antenna ports. vivo, Google, Xiaomi, Apple, Qualcomm and MediaTek argued the existing timing rules, built for smaller antenna counts, would leave phones short on time; Samsung, ZTE, Huawei/HiSilicon and Ericsson wanted to keep the legacy deadline unchanged to avoid adding complexity. Nobody got exactly what they asked for.
3GPP settled on a compromise for phones using the lower-power 'Capability 2' processing timeline: the CSI reference deadline (nCSI_ref) gets scaled by a factor of 2, not the factor of 4 (ceil(128/32)) that OPPO and NEC's opponents had floated. The same meeting also picked the simpler one-part CSI report format for wideband feedback on PUCCH formats 3 and 4, over a two-part alternative Qualcomm, Xiaomi, Apple and eight others backed for its potential overhead savings — Google, CMCC, Ericsson, Samsung and 11 other companies preferred keeping the legacy one-part structure.
For fast Layer 1/2 handovers, 3GPP confirmed phones can use semi-persistent CSI-RS — reference signals the network can switch on and off — for network-scheduled candidate-cell measurements, activated via a MAC CE. But extending that same flexibility to event-triggered reports, where the phone itself decides when to report, split the room 9 to 6: Spreadtrum, Ericsson, CMCC, ZTE, Samsung, Lenovo, vivo and MediaTek said letting the network control the reference signal undercuts the point of phone-driven triggering; Fujitsu, Nokia, Qualcomm, Huawei, NTT DOCOMO and CATT disagreed. Aperiodic CSI-RS for the same feature failed by a similar 10-to-7 margin, with opponents citing signaling overhead between network nodes.
MediaTek used field measurements to challenge whether 6-layer MIMO is worth standardizing for 6-antenna phones at all. Its SSB-based SNR data showed only about 5% of readings exceed 25 dB, while rival simulations claim 6-layer MIMO only beats 4-layer above 30 dB SNR — a condition MediaTek says rarely occurs in real networks. Its own link-level simulations, using a 3% transmitter error vector magnitude and antenna efficiency losses of at least 3 dB, found no gain for 6L6R over 4L6R, and it proposed dropping the requirement work entirely; no company has yet spoken up to defend continuing it.
RAN1#120bis will pick up the timing-reference proposal for candidate-cell CSI-RS measurement in LTM, skipped this quarter for lack of time, plus the still-open framework for early CSI acquisition after handover — including whether reports travel via UCI or a MAC CE. Also unresolved: which formula (InterDigital's Option 2a versus the simpler Option 3) will scale angles in the FR3 channel model used to simulate 7-24 GHz MIMO performance for 5G-Advanced and 6G.
The decisions behind this
Rel-19 Type-I codebook for wideband CSI on PUCCH will use one-part reporting for all formats
The topic is about how a phone (UE) reports Channel State Information (CSI) for large antenna arrays (up to 128 ports) in 5G-Advanced (Rel-19). Specifically, it concerns the 'Type-I Single-Panel' codebook refinement for wideband reports sent on the PUCCH (Uplink Control Channel).
A proposal (1.A) was made to decide between two alternatives for PUCCH formats 3 and 4 when reporting wideband CSI for the new 'Scheme-B' codebook: Alternative 1 uses one-part CSI (like legacy), while Alternative 2 uses two-part CSI where the spatial basis selection is reported in a second part. For PUCCH format 2, the proposal kept one-part CSI, as two-part is not supported in legacy.
The moderator's assessment noted the proposal had been discussed since a previous meeting and needed resolution. The benefit of Alternative 2 depends on whether the difference in payload size across different transmission ranks (RIs) is large enough to justify two-part CSI, especially for wideband reports. The difference becomes more significant when multiple reports (Nrep>1) are configured on the same PUCCH, a scenario practical for Carrier Aggregation.
The document lists company views: Alternative 1 was supported by Google, CMCC, Lenovo/Motorola Mobility, OPPO, Fujitsu, ZTE, CATT, Spreadtrum, Intel, Huawei/HiSilicon, New H3C, NEC, Ericsson, Samsung, and Nokia/NSB. Alternative 2 was supported by Qualcomm, Xiaomi, Fraunhofer IIS/HHI, Samsung, Tejas, vivo, Sharp, NTT DOCOMO, NTT CORP, Apple, TCL, and ETRI.
No decision was made on this proposal at RAN1#120. The meeting did not adopt it. The reason for the decision is not recorded in the provided materials.
The RAN1#120 meeting record records a partial agreement on this point: "For the Rel-19 Type-I SP codebook refinement for P=48, 64, 128 CSI-RS ports, regarding Scheme-B, when the UE is configured to report wideband CSI on PUCCH formats 3 and 4, one-part CSI is used."
| Use one-part CSI for PUCCH formats 3/4 (Alt1) | Use two-part CSI for PUCCH formats 3/4 (Alt2) |
|---|---|
| Google · CMCC · Lenovo/Motorola Mobility · OPPO · Fujitsu · ZTE · CATT · Spreadtrum · Intel · Huawei/HiSilicon · New H3C · NEC · Ericsson · Samsung · Nokia/NSB15 companies | Qualcomm · Xiaomi · Fraunhofer IIS/HHI · Samsung · Tejas · vivo · Sharp · NTT DOCOMO · NTT CORP · Apple · TCL · ETRI12 companies |
If no consensus is reached in the future, PUCCH formats 2, 3, and 4 may not be supported for wideband CSI reporting associated with the new Rel-19 Type-I 'Scheme-B' codebook, potentially limiting reporting flexibility for devices using large antenna arrays.
No change agreed for CSI reference resource timing for large antenna ports
The topic is about the timing reference a phone uses to calculate CSI for periodic or semi-persistent reports when connected to a base station with a large number of antenna ports (48, 64, or 128) in 5G-Advanced.
A proposal (1.B) suggested scaling the legacy CSI reference resource timing (nCSI_ref) by a factor of ceil(P/32) for 128 ports when using 'Capability 2' timeline, arguing that the processing time (Z2') could exceed 10ms, which is more than twice the minimum nCSI_ref. For all other cases (e.g., 48/64 ports or Capability 1), it proposed keeping the legacy timing.
The moderator's assessment noted the scaling of the processing timeline (Z/Z') by ceil(P/32) is only applied to Capability 2. While the scaling argument could be made for Capability 2, it was unclear why it was needed for Capability 1, and it didn't seem to be a problem for 48 and 64 ports.
Company views were split. Supporting the scaling proposal were vivo, Google, Xiaomi, Apple, Qualcomm, ETRI, Sharp, Fujitsu (for Cap2, 128p), NTT DOCOMO (128p Cap2), NTT CORP, and MediaTek (Cap2). Supporting the legacy (no change) baseline were Samsung, ZTE, CMCC, Huawei/HiSilicon, Lenovo/Motorola Mobility, Ericsson, and Nokia/NSB.
No decision was made on this proposal at RAN1#120. The meeting did not adopt it. The reason for the decision is not recorded in the provided materials.
The RAN1#120 meeting record records a partial agreement on this point: "For the Rel-19 Type-I SP codebook refinement for P=128 CSI-RS ports, with Capability 2 timeline, when periodic or semi-persistent CSI reporting is configured, nCSI_ref is the smallest value greater than or equal to 10⋅2μ, such that it corresponds to a valid downlink slot."
| Scale reference timing for 128 ports & Cap2 | Keep legacy reference timing |
|---|---|
| vivo · Google · Xiaomi · Apple · Qualcomm · ETRI · Sharp · Fujitsu · NTT DOCOMO · NTT CORP · MediaTek11 companies | Samsung · ZTE · CMCC · Huawei/HiSilicon · Lenovo/Motorola Mobility · Ericsson · Nokia/NSB7 companies |
The baseline remains that the CSI reference resource follows the legacy 5G design. If the scaling is not adopted, phones with 'Capability 2' processing for 128 ports might face challenges meeting the tight timing for periodic/semi-persistent CSI reports, potentially affecting reporting accuracy or requiring different UE capabilities.
- DeferredCompanies push to capture detailed trigger rules in RAN2 specificationsR1-2501556
- DeferredOffline proposal favors simple beam report flag over instance counterR1-2501556
- DeferredNo consensus on how to handle missing first PUCCH for event-driven beam reporting in Mode-AR1-2501556
- DeferredProposal for Event-7 report format extension gains broad supportR1-2501556
- DeferredTiming for CSI reference resource with 128 antenna ports is deferredR1-2501362
- DeferredProposal to define counting method for Event-7 beam triggers deferredR1-2501556