Point a 5G phone at a satellite and two things break instantly

Hi all,

The first four weeks of this series were all about the satellite side of the link — link budgets, real passes, scheduling, a bit of machine learning. This week I wanted to come at it from the direction I actually know best from years in mobile networks: the 5G side. Simple question — if you took an ordinary 5G phone and pointed it at a satellite instead of a cell tower, what would break?

The answer is clean: two things break, almost immediately, and both come from assumptions quietly baked into the 5G standard.

The first is timing. 5G, like every cellular system, has to line up transmissions from many handsets so they arrive at the tower together. A handset further away has a longer travel time, so it's told to transmit slightly early — "timing advance." The catch is the standard only allows so much early: the largest standard 5G NR timing-advance command tops out around 667 microseconds, which is about 100 km of distance. There's a longer-reach mechanism for initial access that stretches to roughly 200 km, and that's the ceiling. 5G was never built to talk to something further than a long rural cell.

A satellite in low Earth orbit is 500 to 2,000 km away.

I didn't want to argue this from round numbers, so I ran it against a real satellite — a live Starlink pass over Aberdeen, computing the actual round-trip time at every moment. The timing advance needed peaked near 9,700 microseconds — more than fourteen times the standard 5G limit — even though the satellite's closest approach was still 1,386 km away. Across the entire real pass, essentially none of it fits inside standard 5G timing. The signal is late by an amount the standard has no normal way to even express. This is exactly why 3GPP's non-terrestrial-network work, from Release 17 onward, leans on GNSS in the handset: if the phone knows where it is and where the satellite is, it can pre-compute that huge timing advance itself.

The second break is frequency. A cell tower doesn't move, so the frequency you receive is the frequency it sent. A satellite crossing at 7.5 km/s Doppler-shifts the carrier — up as it approaches, down as it recedes, through zero at closest approach. At S-band (around 2 GHz, the direct-to-handset band) this real pass swung about 14 kHz each way; at Ku-band, it would reach a few hundred. Too much for a receiver expecting a stationary tower to ignore, and because it changes continuously and flips sign overhead, it has to be tracked the whole way, not corrected once.

Here's the part I care about most. It would've been easy to just plot two big curves and call it a day. But the point isn't "these numbers are big" — it's that they're big relative to a specific line the 5G standard actually draws. The 667-microsecond ceiling and the ~100 km reach are in the 3GPP specifications; I didn't invent them for effect. The whole reason NTN needed new standards work is that a satellite blows straight through them. So the red line on my timing plot isn't decoration — it's where standard 5G stops working, and the entire pass sits above it.

For me this is the week the series stops being purely about satellites and starts being about the thing I actually spent years doing — mobile networks — meeting the thing I did my MSc in. Same real pass machinery as Week 2; new question asked of it.

Until next time,
Shaif