Satellite phones without GPS: per-beam reference points agreed, two-root PRACH narrowed
Per-beam reference points are agreed and the two-sequence PRACH design is narrowed over lone objections from ZTE and OPPO; other variants and signaling details stay open.
Source meetings for this article (9)
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 ↗
- CT#11314 Sept 2026 – 15 Sept 2026 · Madrid · 3GPP ↗
- RAN1#12624 Aug 2026 – 28 Aug 2026 · Maastricht · 3GPP ↗
- RAN4#12024 Aug 2026 – 28 Aug 2026 · Maastricht · 3GPP ↗
- SA3#12924 Aug 2026 – 28 Aug 2026 · Prague · 3GPP ↗
- SA5#16824 Aug 2026 – 28 Aug 2026 · Prague · 3GPP ↗
- RAN3#13324 Aug 2026 – 28 Aug 2026 · Maastricht · 3GPP ↗
- RAN2#13524 Aug 2026 – 28 Aug 2026 · Maastricht · 3GPP ↗
A phone talking to a satellite has to time and tune its first transmission for a long signal path and a large Doppler shift. It knows where the satellite is, because the network broadcasts the orbit data (ephemeris), but without GNSS it does not know where it is itself, so it cannot work out the distance or the Doppler. The Release 20 work gives the network two tools: a reference location the phone can use in place of its own position, and a random-access signal built so the base station can measure the error that remains.
For that signal, 3GPP narrowed the leading design — two PRACH sequences in the existing format — to Alt 1-4 as the baseline: the two sequences use different, non-conjugate roots, which lets the base station separate the timing error from the frequency error. Other variants, such as two sequences in different PRACH formats or several sequences tied to multiple reference locations, remain under study. Thales, the feature lead running the discussion, put it forward with Ericsson, Nokia, Huawei, Qualcomm and about ten others behind it; OPPO objected. 3GPP decides by consensus, so one objection can stall a proposal, but here it did not. Whether the two sequences share one random-access occasion or use separate ones will be decided at the next meeting.
In quasi-Earth-fixed cells, where the satellite steers each beam so that its footprint stays in place for a while before switching, the network will broadcast a reference location: one per cell when the cell has a single beam, one per beam when it has several. About two dozen companies argued that beam-level granularity is needed to keep residual errors within what the phone can correct. ZTE wanted a per-cell baseline, and Nokia, while backing the approach, warned that a reference point per beam adds broadcast overhead; whether a cell-level location can still be configured in multi-beam cells is left for further study. Earth-moving cells get the equivalent: a common timing-advance and Doppler value, per beam where a cell has several.
The corrections the network sends back in the random-access response are getting bigger too. The timing-advance command will be extended to cover at least the largest residual errors in the study report TR 38.742, with today's granularity kept; a 3 ms range was proposed but the value is still open. A frequency-adjustment command will be defined with its own range, granularity and positive and negative values, with the message format left to the protocol group; the granularity, either a fraction of the subcarrier spacing or a ppm step, is due to be chosen at the next meeting. How to signal the common timing advance in Earth-moving cells is not settled: reusing the 26-bit format of the existing ta-Common parameter, which reaches 270.73 ms, was only proposed as a working assumption.
On the device side, the revised work item approved at the plenary gives high-power satellite phones (Power Class 1.5) both two-antenna transmit diversity and single-layer uplink MIMO — both send one data stream from two antennas — and rules out dual-layer MIMO. MediaTek, LG, Huawei, OPPO and Samsung had leaned toward transmit diversity only; SpaceX, Apple, Amazon, Qualcomm, ViaSat and AST kept single-layer MIMO in. The same item adds half-duplex requirements for VSAT terminals in the Ka and Ku bands, which are dish- or panel-sized satellite terminals far larger than a phone, and targets the new downlink carrier aggregation in the L band at all existing power classes, PC3, PC2, PC1.5 and PC1.
The decisions behind this
Beam-specific reference locations agreed for GNSS-resilient timing in Earth-fixed satellite cells
For a phone in a 'quasi-Earth-fixed' satellite cell (where the satellite steers each beam so that its footprint stays in place for a while before switching), the network can provide a reference location to help the phone calculate timing and frequency adjustments when its own GNSS fails. A key question is whether this reference point should be defined per cell or per individual beam (SSB).
A coalition of companies proposed that beam-specific reference locations should be supported. The proposal states: 'For open-loop UL time/frequency pre-compensation on the service link in (quasi) Earth-fixed cells, support a reference-location-based approach together with satellite ephemeris where beam-specific reference location is supported. The association between reference location(s) and the applicable beam/SSB should be defined.'
The RAN1#126 chair's notes record an agreement: cell-specific reference location for cells with one SSB beam, SSB-beam-specific reference location for cells with multiple beams. Many companies supported beam-level granularity, arguing it keeps residual timing errors within the limits the physical layer can handle. ZTE wanted a cell-specific reference location as the baseline, with beam-specific support discussed later. Nokia supported the proposal in general but warned that a reference point per beam adds broadcast overhead. Whether a cell-specific location can also be configured in multi-beam cells, and whether a beam can carry several reference locations, remain for further study.
| Support beam-specific reference location | Prefer a cell-specific reference location as baseline |
|---|---|
| Ericsson · Huawei · HiSilicon · Thales · Spreadtrum · UNISOC · InterDigital · CSCN · LG Electronics · Quectel · Qualcomm · Sony · China Telecom · TCL · Samsung · OPPO · Apple · Nokia · HONOR · Sateliot · ETRI · Toyota ITC · DOCOMO · CATT · Futurewei · Panasonic · vivo27 companies | ZTE1 company |
Phones without GNSS will get a reference location matched to their beam in multi-beam satellite cells, which keeps residual timing and frequency errors small enough to correct, at the cost of more broadcast signaling.
Two-root PRACH for GNSS-resilient NTN initial access will use non-conjugate roots as baseline
When a phone loses its GNSS (Global Navigation Satellite System) signal in a Non-Terrestrial Network (NTN), like a satellite network, it cannot accurately pre-compensate the timing and frequency of its initial random-access signal (PRACH). To solve this, RAN1, the working group responsible for the physical layer, is studying a method where the phone transmits two PRACH sequences with different 'roots' (the mathematical base of the signal) so the network can estimate the large timing and frequency errors. The group evaluated several technical variants for transmitting these two sequences.
Thales, the feature lead running this agenda item, proposed adopting 'Alt 1-4' as the baseline. This alternative uses two-root transmission where the two roots are not necessarily conjugate pairs. The proposal states: 'For the solution involving transmission of two PRACH sequences with the same existing PRACH format and different roots, Alt 1-4 is adopted as baseline. RAN1 will decide in the next meeting whether Alt 1-2 can be also adopted.'
The RAN1#126 chair's notes record this as an agreement; whether the two sequences use the same or separate random-access occasions will be decided at the next meeting. The reason for the decision is not recorded in the materials.
| Support adopting non-conjugate roots (Alt 1-4) as baseline | Oppose or deprioritize Alt 1-4 |
|---|---|
| Ericsson · Nokia · LG Electronics · ZTE · Huawei · CATT · Sony · Thales · Qualcomm · TCL · NEC · Ofinno · ST Engineering iDirect · Eutelsat · Lenovo15 companies | OPPO1 company |
The baseline for GNSS-denied initial access over satellite is set: two PRACH sequences with non-conjugate roots (Alt 1-4). What remains open is how they are placed in time.
- DecidedHigh-power NTN phones (PC1.5) get two-antenna transmit diversity and single-layer uplink MIMO, not dual-layer, in Release 20RP-262238
- DecidedMsg2 Timing Advance Command to be extended for larger errors in GNSS-denied accessR1-2605609
- DecidedRAN2 to handle new capability signaling for NTN HD-FDD VSATs and downlink carrier aggregationRP-262238
- DeferredProposed encoding for common timing assistance in moving satellite cellsR1-2605609
- DeferredGranularity of Frequency Adjustment Command remains under evaluationR1-2605609
- DecidedIntra-band downlink carrier aggregation for NTN will target all existing UE power classesRP-262238