What the work is for · chapter 2 of 7 · 5 minutes
2 How an area of work like this runs
Study, then normative work, then a second phase — the shape 3GPP work takes, with Ambient IoT walked through as the example, and the kinds of paper each step produces.
2.1 The words you need before anything else
Five words carry most of the traffic in any conversation about 3GPP work, and none of them means quite what it sounds like.
-
A work item is one named piece of work 3GPP has agreed to do. A study item is a work item that only investigates and writes a report; its short name always starts
FS_, for "feasibility study". -
A WID is a work item description and a SID a study item description — the few-page document that proposes the work and, once a meeting approves it, defines it.
-
A plenary is the three-monthly meeting where a whole technical area signs work off.
-
A TS is a technical specification, the kind that tells you what to build. A TR is a technical report, the kind that studies a question and is then closed.
-
Stage 1 is what the system must do, stage 2 how it is put together, stage 3 the exact bits on the wire.
Two more turn up constantly once work is under way. A CR is a change request, one edit to a published specification; a pCR is the same thing aimed at a report still being written. A liaison statement is a letter one group sends another.
2.2 Step one: a study that asks whether it is worth doing
The Ambient IoT area opened with a study item, FS_AmbientIoT, unique id
950004, run by the group that writes what a system must do. It was approved as
document SP-220085 at plenary SP-95-e. FS_AmbientIoT SP-220085
It ran from 2022-03-10 to 2023-05-28, and its report is TR 22.840, against which 497 documents were filed. FS_AmbientIoT TR 22.840
The radio side asked a harder question than "what for" — whether such a device
is buildable at all. That study was FS_Ambient_IoT_RAN, unique id 970078.
It was approved as RP-232404 at plenary RP-101, and its report is TR 38.848. FS_Ambient_IoT_RAN RP-232404 TR 38.848
It is the only Rel-18 item in the whole area; everything else sits in Rel-19 or Rel-20. FS_Ambient_IoT_RAN
Three more studies followed once the shape was clear: the radio solutions study
FS_Ambient_IoT_solutions FS_Ambient_IoT_solutions, the architecture study
FS_AmbientIoT under a second unique id, 1020071 FS_AmbientIoT, and the
security study FS_Ambient_IoT_Sec FS_Ambient_IoT_Sec.
2.3 Step two: normative work
Normative work is the step that changes documents people build from. Each study above has a matching one.
-
Requirements:
AmbientIoT, unique id 1020030, approved as SP-231403 at plenary SP-102, producing TS 22.369. AmbientIoT SP-231403 TS 22.369 -
Radio:
Ambient_IoT_Solutions-Core, unique id 1061084, approved as RP-252105. Ambient_IoT_Solutions-Core RP-252105 -
Architecture:
AmbientIoT-ARC, unique id 1070010, approved as SP-250377. AmbientIoT-ARC SP-250377 -
Security:
AmbientIoT-SEC, unique id 1070022, producing TS 33.369. AmbientIoT-SEC TS 33.369 -
Protocols:
AmbientIoT-CT, one shared description, CP-252196, approved at plenary CP-109. CP-252196 AmbientIoT-CT
The protocol work states the ordering rule out loud: "Stage 3 work shall be started only after the applicable normative stage 2 work is available." [2]
2.4 Step three: a second phase
A finished release does not close an area. Rel-20 reopened this one as a set of
items whose names all carry Ph2, and those begin with studies of their own.
There are five: architecture FS_AmbientIoT_Ph2_ARC, application enablement FS_AmbientIoT_Ph2_APP, security FS_AIoT_SEC_Ph2, outdoor active devices FS_Ambient_IoT_Outdoor_Active and charging FS_AmbientIoT_Ph2_CH.
The phase 2 radio work item says what a second phase is for, in one sentence.
The architecture study of phase 2 states where it widens the first phase: its first work task is to "Study the support of AIoT services in Topology 2". [3]
2.5 What the paper trail looks like
Each of those steps is made of documents, and the mix says something about where the effort goes.
| Kind | How many |
|---|---|
| discussion papers | 3973 [4] |
| pCRs, edits to a report | 3620 [5] |
| CRs, edits to a published specification | 1538 [6] |
| letters between groups | 351 [7] |
Each of those four is a count of documents of that one type, drawn from the 10771 Ambient IoT documents in this data; they are four types among others and do not add up to the total. [8] The shape is still clear: more paper argues about the work than changes any document.
The years show the same story as a curve.
| Year | Documents filed |
|---|---|
| 2022 | 220 [9] |
| 2023 | 414 [10] |
| 2024 | 3384 [11] |
| 2025 | 4457 [12] |
| 2026, a part year | 2090 [13] |
2.6 Where to read this yourself
The reports the studies produced are TR 22.840, TR 38.848, TR 38.769, TR 23.700-13, TR 23.700-30, TR 23.700-26, TR 33.713 and TR 33.714. TR 22.840 TR 38.848 TR 38.769 TR 23.700-13 TR 23.700-30 TR 23.700-26 TR 33.713 TR 33.714
The specification numbers to open for the normative side are TS 22.369, TS 23.369 and TS 33.369. TS 22.369 TS 23.369 TS 33.369
The School of Specs holds none of that text. It names the document and says what it is for; reading it means opening it on 3gpp.org.
Where the numbers in this chapter come from
- what the phase 2 RAN work set out to do the first two sentences of section 4 of /var/www/whatthespec.net/data/data/wis/1081086/RP-252894 Revised WI for R20 Ambient IoT_cl/RP-252894 Revised WI for R20 Ambient IoT_cl.md, copied word for word, read 2026-08-04
- what the protocol work set out to do the first two sentences of section 4 of /var/www/whatthespec.net/data/data/wis/1080021/CP-252196_cl/CP-252196_cl.md, copied word for word, read 2026-08-04
- what the phase 2 architecture study set out to do the first two sentences of section 4 of /var/www/whatthespec.net/data/data/wis/1080063/SP-250834 R20 AmbientIoT SID clean/SP-250834 R20 AmbientIoT SID clean.md, copied word for word, read 2026-08-04
- 3973 Ambient IoT documents of type discussion Ambient IoT rows of `tdoc` whose type column is 'discussion', read 2026-08-04
- 3620 Ambient IoT documents of type pCR Ambient IoT rows of `tdoc` whose type column is 'pCR', read 2026-08-04
- 1538 Ambient IoT documents of type CR Ambient IoT rows of `tdoc` whose type column is 'CR', read 2026-08-04
- 351 Ambient IoT documents of type LS out Ambient IoT rows of `tdoc` whose type column is 'LS out', read 2026-08-04
- 10771 Ambient IoT documents rows of `tdoc` in api.sqlite whose work item column names one of the 28 Ambient IoT work item acronyms, read 2026-08-04
- 220 Ambient IoT documents filed in 2022 Ambient IoT rows of `tdoc` whose upload date falls in 2022, read 2026-08-04
- 414 Ambient IoT documents filed in 2023 Ambient IoT rows of `tdoc` whose upload date falls in 2023, read 2026-08-04
- 3384 Ambient IoT documents filed in 2024 Ambient IoT rows of `tdoc` whose upload date falls in 2024, read 2026-08-04
- 4457 Ambient IoT documents filed in 2025 Ambient IoT rows of `tdoc` whose upload date falls in 2025, read 2026-08-04
- 2090 Ambient IoT documents filed in 2026 Ambient IoT rows of `tdoc` whose upload date falls in 2026, read 2026-08-04
Check yourself
Answers appear when you pick one, with where they come from.
Q2.1 What does the prefix `FS_` on a work item's short name tell you?
A study item's short name always starts FS_, for "feasibility study". It investigates and produces a report, not a specification. 10 of them are studies
Q2.2 Which document opened the whole Ambient IoT area, and at which meeting?
SP-220085 was approved at SP-95-e and started the founding SA1 study. RP-232404 opened the RAN feasibility study later. SP-220085
Q2.3 What is the difference between a CR and a pCR?
A CR is one edit to a published specification; a pCR is the same thing aimed at a report that is still being drafted. 1538 Ambient IoT documents of type CR
Q2.4 Which kind of document is the most common in this area?
3973 discussion papers, against 3620 pCRs, 1538 CRs and 351 letters. Most of the paper is argument, not text. 3973 Ambient IoT documents of type discussion
This chapter was built from a source register generated 2026-08-04. A fresher build of the register may hold different numbers.