School of Specs Satellites — a base station in orbitQuick start

What it is and why it was wanted · chapter 2 of 4 · 4 minutes

2 Why anyone wanted a phone to talk to orbit

The reason in the work items' own words, the one study the whole line starts from, and the two halves a reader keeps meeting.

2.1 The reason, in the plainest words the record holds

A work item is opened by a short paper, and that paper has a section saying why somebody thought the work was worth doing. For the internet-of-things half of this subject, that section says the point in one line: connection matters most where there is none.

The register keeps the opening of it, which breaks off in the middle of its own list of industries.

Transport first — ships, lorries, trains, aircraft — and logistics with it. Those are the things that spend their working life outside anybody's coverage.

2.2 What that work item actually promised

The same paper's objective is one sentence long, which is rare.

NB-IoT is the narrowband internet-of-things radio and eMTC is enhanced machine type communication, the other low-power flavour of the older LTE radio. Both names are written out in the title of the study that came before the work TR 36.763.

So the promise was small and clear: take the two radios that already run sensors and trackers, and make them work through a satellite.

2.3 Where the line starts

Everything in this course grows out of one Release 15 study, called "Study on NR to support non-terrestrial networks", with RAN1 named as its group. It produced one document, TR 38.811, and 124 papers were filed against it FS_NR_nonterr_nw [4] TR 38.811.

NR is the 5G radio, so the title is the whole plan in one line: find out what the 5G radio needs in order to work with a satellite in the path. What the study concluded is not held here, only that it ran and what it produced.

The paper that opened it in its revised form is RP-171450, and its recorded outcome is approved RP-171450. It went to RAN#76, the plenary that sat in West Palm Beach, Florida from 2017-06-05 to 2017-06-08 RP-76.

2.4 The two halves you keep meeting

Read a handful of these documents and the short names sort themselves into two families.

  • The radio half carries NTN in its short name and lives in the RAN groups. Its subject is the air: what is transmitted, how strong and on which band. The Release 17 rule-writing item names RAN2 as its leading group and RAN1, RAN3 and RAN4 behind it, and the two documents its work plan row creates are TS 38.108 and TS 38.181 NR_NTN_solutions.

  • The system half is spelled 5GSAT and lives in SA and CT. Its subject is everything behind the radio: the core network, what a phone says to it, which network it should pick. The protocol part of the first phase names CT1 as its leading group 5GSAT_ARCH-CT.

The register does not label those two halves anywhere. The split is visible in the short names and in the leadership line each work item writes for itself, and that is where the two sentences above come from.

2.5 From a proposal to something running

The newest of the internet-of-things phases says where the work has got to, in the proposers' own words.

That is as close as this record comes to saying the thing exists outside paperwork. It is a sentence in a proposal, written by people arguing for more work, and it is worth reading as exactly that.

2.6 Where this meets the rest of the course

A base station in orbit has the words these papers use. Who is building it, and where the weight sits is who has been filing them and where the weight sits. What exists on paper, and where to look yourself is the shelf all of it produced, and the list of questions this record cannot answer at all.

2.7 What people get wrong

Where the numbers in this chapter come from

  1. 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
  2. the objective of LTE_NBIOT_eMTC_NTN section 4 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
  3. 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
  4. 124 documents carrying the work item FS_NR_nonterr_nw rows of the tdoc table whose work item column names FS_NR_nonterr_nw 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

Every source this course is built on

Check yourself

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

Q2.1 Which industries does the Release 17 internet-of-things work item name first when it says why it was proposed?

Q2.2 How long is that work item's stated objective?

Q2.3 Where does the line of work this course follows begin?

Q2.4 What does the Release 19 internet-of-things justification say about deployment?

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