The two halves, and who runs them · chapter 5 of 7 · 7 minutes
5 The system half: 5GSAT, phase by phase
What the core network, the protocols and the trades around them had to change so that a phone can be served from orbit — four phases of it, plus backhaul, which runs the other way round.
5.1 Why there had to be a second half at all
Getting bits between a phone and something in orbit is a radio problem, and the RAN groups took it. It leaves a pile of questions the radio never answers.
Which network should a phone pick when the coverage overhead belongs to somebody else? What should the system do while the satellite is below the horizon? Who is billed, who may listen in, and what does the phone say?
Those are system questions. In 3GPP they sit with SA — the groups that decide what the system must do and how it is put together — and with CT, the groups that write the actual messages. The short name their work items carry is 5GSAT, not NTN.
Nothing in the register labels two halves. The split shows in the short names and in the leadership line each work item carries, and that line is where every claim here about who led what was read.
5.2 Phase 1 went requirements, then architecture, then protocol
SA1 writes what the system has to do. It studied using satellite access in 5G into TR 22.822 FS_5GSAT TR 22.822, then wrote the result into TS 22.261, the 5G service requirements 5GSAT TS 22.261.
SA2 owns the shape of the system. Its study produced TR 23.737 FS_5GSAT_ARCH TR 23.737, and the work item after it put the answer into TS 23.501, TS 23.502 and TS 23.503 5GSAT_ARCH TS 23.501 TS 23.502 TS 23.503.
CT1 led the protocol half, and that piece alone carries 912 documents 5GSAT_ARCH-CT [6]. Its own study phase had one question, and the work item description states it plainly.
A PLMN is one operator's network — the thing your phone shows as a network name. Choosing between them when the coverage comes from orbit was enough of a question to need a study of its own, and it produced TR 24.821 TR 24.821.
5.3 Phase 2 is about coverage that comes and goes
A satellite in a low orbit is overhead for a few minutes and then it is not. Phase 2 is what the system does in between.
SA2 studied it into TR 23.700-28 FS_5GSAT_Ph2 TR 23.700-28 and then wrote the rules, in a piece of work carrying 810 documents 5GSAT_Ph2 [7].
The Evolved Packet System is the older, 4G core network. It is named there beside the 5G one because a great deal of satellite work lands in the old core rather than the new one.
5.4 Phase 3 named three things and went after them
The phase 3 protocol work item opens by saying what SA2 had already settled, and it lists the three subjects by name.
A regenerative payload is a satellite that demodulates, decodes and re-encodes the signal, so a real piece of the base station is in orbit rather than on the ground [8].
Store-and-forward means the satellite takes the traffic, carries it and hands it over later — for a service that can wait, which is what TR 22.865's own scope names first [9].
Phone-to-satellite-to-phone is the one where the traffic never touches the ground at all [10].
Underneath those three sit the ordinary two steps. SA1's study produced TR 22.865, and its work item put the requirements into TS 22.261 FS_5GSAT_Ph3 TR 22.865 5GSAT_Ph3.
SA2's study produced TR 23.700-29, whose scope names the regenerative payload architecture as its first aim FS_5GSAT_Ph3_ARCH TR 23.700-29 [11].
CT1 again led the protocol side, in a piece carrying 862 documents, and its description lists 19 documents it changes — TS 24.301, what a device says to the older core, among them 5GSAT_Ph3_ARCH [12] TS 24.301.
5.5 Phase 4 is the one running now
SA1's study produced TR 22.887 FS_5GSAT_Ph4 TR 22.887, SA2's
produced TR 23.700-19 FS_5GSAT_Ph4_ARC TR 23.700-19, and the
work item turning that into rules is 5GSAT_Ph4-ARC 5GSAT_Ph4-ARC.
Its study's first work task is narrow enough to picture.
Read backwards, that is a phone call, carried by IMS — the telephony core — over a geostationary satellite, on the narrowband radio built for sensors, landing in the old 4G core.
A geostationary orbit is the circular one 35,786 km above the equator, where a satellite appears to stand still [13].
The justification says where the pressure came from: satellite work had run through four releases already, and SA1 was writing fresh use cases while phase 4 was being proposed [14].
Phase 4's other pieces have barely started. The CT work item carries one document 5GSAT_Ph4-CT, the security and application ones carry none at all 5GSAT_Ph4-SEC 5GSAT_Ph4-APP, and the charging study stands at a completion value of 0.4 FS_5GSAT_Ph4_CH.
What those numbers are, and what they are not, is Where it stands, how to follow it, and what the record cannot say.
5.6 Satellite backhaul runs the other way round
Here nothing reaches the phone from orbit. The mast is an ordinary mast; the satellite carries the link behind it, back towards the operator's network.
SA2 studied it into TR 23.700-27 FS_5GSATB TR 23.700-27 and specified it in Release 18 5GSATB, with a charging item and a management item beside it 5GSATB_CH 5GSATB_OAM.
Release 20 adds one more, for quality of service on a mobile wireless access backhaul carried over satellite, split between SA2 and CT TEI20_QoS_MWAB_SAT TEI20_QoS_MWAB_SAT-CT.
5.7 The trades around the edge
Four more groups have a piece of this, and each has its own run of studies.
SA3 does security and carries 551 documents of this subject SA3. Its studies produced TR 33.700-28, TR 33.700-29 and TR 33.700-30 TR 33.700-28 TR 33.700-29 TR 33.700-30.
SA5 does charging and management and carries 751 SA5. The charging reports are TR 28.844, TR 28.846 and TR 28.894 TR 28.844 TR 28.846 TR 28.894; the management ones are TR 28.808, TR 28.841 and TR 28.874 TR 28.808 TR 28.841 TR 28.874.
SA6 does the application layer and carries 402 SA6, with TR 23.700-01 in Release 19 and TR 23.700-02 in Release 20 TR 23.700-01 TR 23.700-02.
SA4 does speech coding, appears only in Release 20 and carries 272 SA4. Its study is on an ultra low bit rate speech codec, 325 documents of it, aimed at voice over a geostationary satellite FS_ULBC [15] TR 26.940.
For scale against those, SA1 carries 711 documents of this subject SA1, SA2 carries 3588 SA2 and CT1 carries 2164 CT1.
5.8 Where this meets the rest
The radio half built its own shelf of documents, and the system half mostly edited documents that already existed. Which is which, and how heavy each one got, is What is on the shelf, and why the bands weigh so much.
How far any of these phases has actually got is a separate question, and the record answers it in a narrower way than most people expect: Where it stands, how to follow it, and what the record cannot say.
Where the numbers in this chapter come from
- the objective of 5GSAT_ARCH-CT section 4 of the work item description /var/www/whatthespec.net/data/data/wis/911030/CP-210149-cl.md, read 2026-08-05
- the objective of 5GSAT_Ph2 section 4 of the work item description /var/www/whatthespec.net/data/data/wis/989998/SP-230109_clean_S2-2303910_WID_5GSAT_Ph2.md, read 2026-08-05
- why 5GSAT_Ph3_ARCH was proposed section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1050019/CP-250134.md, read 2026-08-05
- the objective of FS_5GSAT_Ph4_ARC section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1070011/SP-250787_was_766_was_SP-250400_Revised SID-5GSAT_ARC Phase 4-cl.md, read 2026-08-05
- the objective of 5GSATB section 4 of the work item description /var/www/whatthespec.net/data/data/wis/970056/SP-230111_clean_S2-2303823_5GSATB.md, read 2026-08-05
- 912 documents carrying the work item 5GSAT_ARCH-CT rows of the tdoc table whose work item column names 5GSAT_ARCH-CT as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05
- 810 documents carrying the work item 5GSAT_Ph2 rows of the tdoc table whose work item column names 5GSAT_Ph2 as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05
- "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
- the scope of 22.865 clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/22865/19.2.0/, read 2026-08-05
- "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
- the scope of 23.700-29 clause 1 of the parsed text at /var/www/whatthespec.net/data/friendlyspec/json/23700-29/19.0.0/, read 2026-08-05
- 862 documents carrying the work item 5GSAT_Ph3_ARCH rows of the tdoc table whose work item column names 5GSAT_Ph3_ARCH as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05
- "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
- why FS_5GSAT_Ph4_ARC was proposed section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1070011/SP-250787_was_766_was_SP-250400_Revised SID-5GSAT_ARC Phase 4-cl.md, read 2026-08-05
- 325 documents carrying the work item FS_ULBC rows of the tdoc table whose work item column names FS_ULBC as a whole word; the first and last meeting are those of its earliest and latest upload time, asked of /var/www/whatthespec.net/data/database/api/api.sqlite on 2026-08-05
Check yourself
Answers appear when you pick one, with where they come from.
Q5.1 What marks a piece of this work as belonging to the system half rather than the radio half?
The register labels no halves. The split shows in the short names and in the leadership line each work item carries, and that line is what any claim about who led what is read from. 5GSAT_ARCH-CT
Q5.2 What is phase 2 of the 5GSAT line about?
Its work item says it specifies changes to the 5G core and the older 4G core to support satellite discontinuous coverage. the objective of 5GSAT_Ph2
Q5.3 Which three things does the phase 3 protocol work item name in its own justification?
Those are the three key issues its justification names, studied by SA2 and written up in TR 23.700-29. why 5GSAT_Ph3_ARCH was proposed
Q5.4 What is satellite backhaul, as against satellite access?
Backhaul runs the other way round. Nothing reaches the phone from orbit; the satellite sits behind a normal mast, on the way back to the operator's network. the objective of 5GSATB
Q5.5 What is the first work task of the phase 4 architecture study?
The study's objective names it as work task 1 — an IMS voice call over GEO via NB-IoT NTN connecting to EPC. the objective of FS_5GSAT_Ph4_ARC
This chapter was built from a source register generated 2026-08-05. A fresher build of the register may hold different numbers.