School of Specs Satellites — a base station in orbitOverview

What it is and why it was wanted · chapter 1 of 7 · 6 minutes

1 What a non-terrestrial network is

Every word in the satellite vocabulary, each taken from the document that defines it, plus the newer ones Release 20 had to invent.

1.1 The word, and the document that defines it

Every trade has a phrase it uses instead of the obvious one. 3GPP's phrase for a network whose transmitter is flying is a non-terrestrial network, short form NTN [5].

The definition sits in TS 38.108, the specification that says what a satellite base station has to transmit and receive TS 38.108.

Two phrases in that sentence carry the weight. "Or segments of networks" means a network can be terrestrial in one place and not in another. "Airborne" means the vehicle need not be in orbit at all.

The satellite gets its own line, and it is narrower than the everyday word: a space-borne vehicle carrying a transparent or a regenerative transmitter, in low earth orbit or geostationary orbit [6].

1.2 The base station that is partly in orbit

The thing a phone talks to is not called a base station here. It is a satellite access node, SAN for short [7].

Read the last sentence twice. The node is not the satellite. It takes in the payload flying overhead and the equipment on the ground, and the two together do the job one mast does on land.

1.3 What the satellite does to the signal

There are two answers, and the whole architecture turns on which one is meant.

A transparent payload changes the frequency carrier of the signal, filters it and amplifies it, and sends it on [8]. The intelligence stays on the ground; the satellite is a mirror with a power supply.

A regenerative payload transforms the signal before amplifying it, and that transformation is digital processing — demodulation, decoding, re-encoding, re-modulation, filtering [9]. Part of the base station is then in orbit.

The first definition is from TR 38.863, the report holding the radio-frequency and coexistence work for this whole subject TR 38.863. The second is from TR 38.742, a Release 20 study TR 38.742.

1.4 The two hops, and what each is called

The radio path is in two pieces and each has its own name.

The service link is the radio link between satellite and phone [11]. The feeder link is the wireless link between the satellite-gateway and the satellite [12].

The ground station at the far end of the feeder link is a satellite-gateway in TS 38.108: an earth station at the surface of the Earth with enough transmit power and enough receive sensitivity to reach the satellite [13].

The system side calls the same kind of box an NTN Gateway, an earth station providing connectivity to the payload over the feeder link [14]. Two documents, two spellings, one job.

1.5 Orbits, and the beam that comes down

Two orbit abbreviations turn up in nearly every paper. GEO is geostationary earth orbiting [15] and LEO is low earth orbiting [16].

A geostationary orbit is the circular one 35,786 km above the equator, going the way the Earth turns, so the satellite keeps its place in the sky [17].

A low orbit does not. A satellite in one covers a given area only for a limited time, which the architecture study says outright when it defines a serving satellite [18].

What arrives at the ground is a satellite beam — a beam generated by an antenna on board a satellite [19]. That is the whole definition, and it is deliberately plain.

1.6 One more word, and it is not about phones

The requirements side defines a term for the other kind of satellite equipment, the sort that sits on a roof rather than in a pocket.

It is worth knowing because it marks how wide the subject has got. TR 22.887 defines it in the same clause as satellite access and resilient notification TR 22.887, so the phase 4 study is looking at equipment on a roof as well as equipment in a pocket.

1.7 The words Release 20 had to add

The newest study reports define words the earlier documents did not need.

TR 22.887, the phase 4 requirements study TR 22.887, defines satellite access as direct connectivity between the device and the satellite [20] — no mast anywhere in the sentence.

The same report defines resilient notification: a highly reliable way of getting a notice to a device such as a smartphone when conditions on the satellite link are poor [21].

TR 23.700-19, the phase 4 architecture study TR 23.700-19, adds two more. A serving satellite is one providing the satellite access to a device, and, depending on the orbit, it covers a given area only for a limited time [18].

The second names something the ground never sees at all:

Two phones, one satellite, and nothing on the ground in between. It is defined in a study report, so the phrase has a meaning; the record says nothing about whether anything will be built to it.

1.8 Where these words turn up next

Every one of them is a term or an abbreviation quoted out of a published 3GPP document, and the register names the document and the clause for each. Nothing in this chapter is a paraphrase of somebody's slide.

The vocabulary is split across four documents, and which one a word comes from tells you who was arguing about it.

The radio side owns the hardware words, in TS 38.108 TS 38.108 and TR 38.863 TR 38.863. The requirements and architecture sides own the newer service words, in TR 22.887 TR 22.887 and TR 23.700-19 TR 23.700-19.

A word defined in a study report is a word somebody needed in order to describe a problem, not a word anything is built to yet. Every term in the section above comes from a report of exactly that kind.

Why anyone wanted it takes the reasons the work was proposed, in the words of the proposals themselves. How the work is cut up, and who carries it explains the paperwork these documents sit in, and The radio half, release by release follows the radio line release by release.

Where the numbers in this chapter come from

  1. "non-terrestrial networks" as 38.108 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  2. "Satellite Access Node" as 38.108 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  3. "Very Small Aperture Terminal (VSAT)" as 22.887 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22887/20.0.0/, read 2026-08-05
  4. "UE-Satellite-UE Communication" as 23.700-19 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-19/20.0.0/, read 2026-08-05
  5. "NTN" as 38.108 spells it out clause 3.3 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  6. "satellite" as 38.108 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  7. "SAN" as 38.108 spells it out clause 3.3 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  8. "Transparent payload" as 38.863 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38863/19.4.0/, read 2026-08-05
  9. "Regenerative payload" as 38.742 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38742/20.0.0/, read 2026-08-05
  10. why NR_NTN_enh-Core was proposed section 3 of the work item description /var/www/whatthespec.net/data/data/wis/941106/RP-232669 R18 WID NR_NTN_enh_v19.md, read 2026-08-05
  11. "Service link" as 38.863 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38863/19.4.0/, read 2026-08-05
  12. "feeder link" as 38.108 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  13. "satellite-gateway" as 38.108 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  14. "NTN Gateway" as 23.700-19 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-19/20.0.0/, read 2026-08-05
  15. "GEO" as 38.108 spells it out clause 3.3 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  16. "LEO" as 38.108 spells it out clause 3.3 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  17. "Geostationary Earth Orbit" as 38.108 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38108/19.4.0/, read 2026-08-05
  18. "Serving satellite" as 23.700-19 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-19/20.0.0/, read 2026-08-05
  19. "Satellite beam" as 38.742 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/38742/20.0.0/, read 2026-08-05
  20. "satellite access" as 22.887 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22887/20.0.0/, read 2026-08-05
  21. "Resilient Notification" as 22.887 defines it clause 3.1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22887/20.0.0/, read 2026-08-05

Every source this course is built on

Check yourself

Answers appear when you pick one, with where they come from.

Q1.1 In TS 38.108's own words, what is a Satellite Access Node?

Q1.2 What is the difference between a transparent payload and a regenerative one?

Q1.3 Which of these is the feeder link?

Q1.4 TR 23.700-19 defines phone-to-satellite-to-phone traffic. What makes it different?

Q1.5 How high is a geostationary orbit, in the words of TS 38.108?

This chapter was built from a source register generated 2026-08-05. A fresher build of the register may hold different numbers.