Skip to main content
Satellites, NTN & HAPS · 3GPP Quarterly December 2025

5G satellites get simpler capacity boost as IoT gains power ramping

3GPP kept only two orthogonal cover code options for satellite uplinks and finalized power ramping for IoT devices, while a fight over timing-advance rules stalled.

13 decisions18 work areas703 contributions

Plenary cycle

SA#110 · RAN#110 · CT#110

Baltimore · 8 Dec 2025 – 12 Dec 2025

Source meetings for this article (9)

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

Ericsson and Nokia lost a fight to add explicit rules for what happens when a timing-advance command lands in the middle of a coordinated satellite uplink transmission. Vivo, DoCoMo, ZTE, CATT and LG argued the network can simply schedule around the problem, and the proposal was noted rather than adopted — leaving the exact device behavior unresolved for now. A separate, similarly contested proposal to make devices drop an entire transmission group if signal continuity breaks split the same companies in reverse: Vivo, Nokia and Panasonic wanted it specified, while Ericsson, Qualcomm, DoCoMo and ZTE said it wasn't needed.

For boosting how many devices can share the same satellite uplink resources, 3GPP confirmed orthogonal cover codes (OCC) — a technique that multiplies each device's signal by a distinct mathematical sequence so several transmissions can be separated again at the receiver. The standard keeps two versions: a length-2 code multiplexing 2 devices and a length-4 Hadamard-sequence code multiplexing 4 devices, both applied across consecutive time slots. A more complex intra-symbol variant, and a hybrid combining both approaches, were dropped from Release 19 entirely, keeping the specification simpler for chipset vendors to implement.

IoT devices connecting via satellite got two concrete upgrades to LTE-M and NB-IoT specifications. First, power ramping: if a device's initial data transmission (Msg3) under the CB-Msg3-EDT scheme isn't acknowledged, it can retransmit at higher power using a new power-control index rather than repeating at the same weak level. Second, sub-resource-block allocation: operators can now assign smaller chunks of uplink bandwidth to devices in good satellite coverage, freeing capacity, while poorer-coverage devices still get larger, more robust allocations.

A parallel study is tackling what happens when a phone's GPS/GNSS receiver goes dark mid-connection to a satellite — a scenario that throws off both timing and Doppler-shift calculations needed to keep the link synchronized. Companies agree the worst case, a total outage, should be the priority baseline, but they're split on how to model it: CMCC, CATT, ETRI, ZTE, Huawei and Apple back a simpler geometric method, while Ericsson, Nokia and CEWiT push for a more flexible vector-based one that better handles Earth's rotation and off-axis beams. MediaTek and Lenovo counter that the two methods largely agree anyway.

The GNSS-resilience study has a formal checkpoint in June 2026 to settle on a single evaluation baseline and start narrowing its catalog of fixes — including new random-access signal formats and satellite-based downlink positioning using Ericsson- and Eutelsat-backed timing parameters — down to the ones worth standardizing.

The decisions behind this

Deferred
Study on GNSS resilient NR-NTN operation
R1-2508469

Study confirms two calculation methods for satellite signal timing and frequency shifts

This document is a summary of discussions for a study on making 5G Advanced and future 6G satellite networks (Non-Terrestrial Networks, or NTN) work when a phone's built-in GPS/GNSS receiver is temporarily unavailable or inaccurate. When GNSS is unavailable, the phone's location is uncertain, which creates large variations in signal timing (delay) and frequency (Doppler shift) between the phone and satellite. The study aims to evaluate the impact of this and find solutions, with a key checkpoint scheduled for June 2026 to decide on next steps.

A core technical debate was between two methods for calculating these differential delays and Doppler shifts. 'Alt 1' is a simpler, standard geometric approach. 'Alt 2' is a more rigorous, vector-based method favored for its flexibility in modeling complex scenarios like Earth's rotation or beams pointed away from the satellite's orbital plane.

The summary notes that 'Most companies recognize Alt 1 as the traditional, baseline approach.' Companies like CMCC, CATT, ETRI, and ZTE generally support it, while Ericsson and CEWiT advocate for Alt 2. Others, like MediaTek and Lenovo, observed that 'both methodologies are fundamentally equivalent for delay evaluation' and that differences in Doppler results are minor in most practical scenarios.

The moderator's summary contains two competing proposals from the meeting. 'Proposal 1-1-v0' suggests confirming 'Alt-1' as the working assumption, with corrected formulas. 'Proposal 1-2-v0' suggests that 'Alt2 could be also captured in the TR 38.742 (e.g. in the annex).'

The document's status is 'noted,' meaning the meeting took note of these discussions and proposals but did not make a final decision. The reason for deferring a decision is not recorded in the provided materials.

Support confirming Alt 1 as the working assumptionSupport including or preferring Alt 2
CMCC · CATT · ETRI · ZTE · OPPO · Spreadtrum · Tejas Networks · Huawei · Toyota ITC · LGE · Panasonic · Apple12 companiesEricsson · CEWiT · CSCN · Nokia4 companies
Why it matters

The lack of a decision means the fundamental evaluation methodology for the study remains unresolved. Companies must continue simulations using both methods or their own interpretations until RAN1 agrees on a single baseline. This could lead to fragmented or non-comparable evaluation results in the technical report if not resolved.

Deferred
Non-Terrestrial Networks (NTN) for NR Phase 3
R1-2509480

Clarification on timing advance application during OCC operation is proposed

To maintain the orthogonality (separation) of signals from different users in an OCC group, a device must keep phase continuity and power consistency across all repetitions in that group. A change in timing advance (TA) – a command that adjusts a device's transmission timing to synchronize with the network – during the group would break this continuity.

A change proposal (CR) was presented to clarify device behavior: "When the application time of a timing advance command is between PUSCH repetitions in an OCC group, it is delayed by the UE until after the end of the OCC group. Autonomous updates of the UE-specific TA or common TA between PUSCH repetitions in an OCC group are prohibited."

The meeting did not decide on this proposal. Company views were split. Ericsson and Nokia supported the clarification. Opposing companies, including Vivo, DoCoMo, ZTE, CATT, and LG, argued it was unnecessary because the network can schedule around the issue or that expected device behavior is already clear from other specifications. The document's status is 'noted', meaning the proposal was not adopted and discussion is deferred.

Clarify UE behavior in specificationClarification not needed; handled by network/other specs
Ericsson · Nokia2 companiesVivo · DoCoMo · ZTE · CATT · LG5 companies
Why it matters

The need for explicit specification text to prevent timing adjustments from breaking OCC signals is contested. Opponents believe network scheduling and existing rules are sufficient, while proponents want clearer implementation rules. This leaves a potential ambiguity for implementers until the group reaches a consensus.

  • DeferredProposal for UE to drop entire OCC group if continuity is brokenR1-2509480
  • DecidedRAN1 confirms OCC techniques for 5G NTN uplink capacity, drops intra-symbol optionR1-2509480
  • DeferredCompanies propose a list of technical fixes for satellite access without GPSR1-2508469
  • DecidedPower ramping for IoT satellite uplink transmissions gets standardizedR1-2509489
  • DeferredNon-terrestrial networks to get smarter cell measurement timing for idle phonesR2-2508291
  • DeferredIoT satellite uplinks gain flexible resource allocation optionsR1-2509489
Quotations are verbatim from moderator summaries in the 3GPP archive. Document numbers link to the original files. Back to the full report.