What it is and why it was wanted · chapter 2 of 7 · 6 minutes
2 Why anyone wanted it
The stated reasons, taken only from the justification text of the work items large enough to be quoted, and a plain warning about the ones that carry no reason at all.
2.1 Why this chapter is short on reasons
3GPP does not write down why a room agreed to something. What it does write down is why a piece of work was proposed, in a section of the work item description called the justification.
That section is the only stated reason this course is allowed to repeat, and it exists for a minority of the work.
The subject carries 155 short names [6]. The register quotes an objective or a justification only for the 41 that carry at least 200 documents, and says so plainly in its own list of what it does not hold.
So for most of the work below, a chapter may say what the work plan calls it and not what it promised.
2.2 Coverage where there is none
The Release 17 work item that put the older internet-of-things radio onto satellites states its case in one sentence.
Not faster and not cheaper. Somewhere there is nothing at all, and a tracker on a ship or a freight wagon has to work there anyway.
2.3 What Release 17 assumed, and what Release 18 wanted to loosen
The Release 18 radio work item opens its justification by restating what the release before it had done, and that restatement is a short summary of Release 17 in the proposers' own words.
Four assumptions sit in that one sentence, and each is a limit somebody later wanted to move:
-
Transparent payload. The satellite mirrors, the ground thinks — the split What a non-terrestrial network is sets out.
-
GSO and NGSO, geosynchronous and non-geosynchronous orbits.
-
Power class 3 devices carrying a satellite navigation receiver. The device is an ordinary handset, and it knows where it is.
-
Earth-fixed or moving cells. Either the beam is steered to hold a patch of ground, or it sweeps.
2.4 A band somebody else had already set aside
Not every reason is about coverage. The Release 19 Ku band item argues from spectrum allocation, and names no use case at all.
ITU is the International Telecommunication Union, and regions 1, 2 and 3 are how it splits the map for spectrum purposes. The whole argument is that the band is already satellite spectrum in all three, so 3GPP should write it into its own documents to match.
2.5 Power, and a band with no matching pair
The Release 19 item that defines a time-division mode for the narrowband internet-of-things radio gives two reasons at once.
The first is battery life. It proposes using the radio resources in a periodic subset of the uplink and downlink subframes, and says in the same breath that this limits power consumption [7].
The second reason is spectrum shape. The same sentence says the feature lets the radio work with an additional non-geosynchronous satellite system — one whose allocation is a single unpaired block rather than a matched pair.
2.6 A voice call through a satellite that stands still
The newest reasons in the record are about speech. The Release 20 study on an ultra low bit rate speech codec points straight back at the requirements side.
A geostationary satellite is 35,786 km up [8], and a voice call has to survive the trip there and back.
The study's own objective says it is developing recommendations for a codec whose primary application is voice over that orbit [9].
The architecture study of the same phase argues from what has already been studied rather than from a use case.
Its justification says satellite integration has been studied in Release 16, Release 17, Release 18 and Release 19, and that the requirements group was writing new use cases while it was going on [10].
2.7 The one place the record says the thing is in service
Justifications are proposals, and a proposal is free to claim. One of them claims something a reader will want to note.
That is the only statement in this subject's quoted text that says anything is deployed. It is the proposers' sentence, written to argue for more work, and nothing else on this machine confirms or contradicts it.
Read the shape of it, though. It opens with history — what was specified, what was optimised, what is claimed to be running — and only its last sentence asks for anything. A justification argues from where the work already stands.
2.8 Where this leads
The reasons above are attached to particular pieces of work, and the next two chapters are about how those pieces are named, split and carried: How the work is cut up, and who carries it for the paperwork, and The radio half, release by release for the radio line release by release.
Where the numbers in this chapter come from
- why LTE_NBIOT_eMTC_NTN was proposed section 3 of the work item description /var/www/whatthespec.net/data/data/wis/920069/RP-211601 was RP-211573 1534 1457 Rel-17 WID-IoT NTN.md, read 2026-08-05
- 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
- why NR_NTN_Ku_bands-Core was proposed section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1041135/RP-252911_WID revision for the NTN Ku band cl.md, read 2026-08-05
- why FS_ULBC was proposed section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1070055/SP-250635.md, read 2026-08-05
- why IoT_NTN_Ph3-Core was proposed section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1021096/RP-252504 WID Rev R19 IOT-NTN cl.md, read 2026-08-05
- 155 Satellites work item acronyms distinct acronyms over the 183 work plan rows this subject's rule selects, asked of /var/www/whatthespec.net/data/database/api/wp.sqlite on 2026-08-05
- why IoT_NTN_TDD-Core was proposed section 3 of the work item description /var/www/whatthespec.net/data/data/wis/1051123/RP-252935 Revised WID on introduction of IoT-NTN TDD_cl.md, read 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
- the objective of FS_ULBC section 4 of the work item description /var/www/whatthespec.net/data/data/wis/1070055/SP-250635.md, 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
Check yourself
Answers appear when you pick one, with where they come from.
Q2.1 What reason does the Release 17 internet-of-things work item give for itself?
The justification opens by saying IoT operation is critical in remote areas with low or no cellular connectivity for many industries, and the first it names is transportation and logistics. why LTE_NBIOT_eMTC_NTN was proposed
Q2.2 What does the Release 18 justification say Release 17 had assumed?
The justification restates the Release 17 scope in one sentence, and every one of those four limits is in it. Release 18 exists to widen them. why NR_NTN_enh-Core was proposed
Q2.3 Why does the Ku band work item say it is bringing that band into 3GPP?
The justification says the Ku band is allocated for primary satellite use for ITU regions 1, 2 and 3, and that the work therefore introduces it into the specifications according to those definitions. why NR_NTN_Ku_bands-Core was proposed
Q2.4 What does the time-division mode for the internet-of-things radio say it is for?
The proposal describes using radio resources in a periodic subset of the uplink and downlink subframes, thus limiting power consumption, and says the feature extends operation to an additional non-geosynchronous satellite system. why IoT_NTN_TDD-Core was proposed
Q2.5 How many of the 155 short names in this subject carry a quoted objective or justification?
The register quotes the objective and usually the justification of the 41 acronyms carrying at least 200 documents. For the other 114 a chapter may say what the work plan calls them and nothing about what they promised. 155 Satellites work item acronyms
This chapter was built from a source register generated 2026-08-05. A fresher build of the register may hold different numbers.