School of Specs Ambient IoT — a tag with no batteryIn depth

What the work is for · chapter 2 of 14 · 7 minutes

2 Study first, then build, then do it again

How 3GPP turns an idea into binding text — study item, work item, phase two — with Ambient IoT as the worked example.

2.1 Why a process exists at all

Somebody has an idea. Several hundred companies have to agree on it, in writing, before anybody spends money building it. If the agreement is wrong the mistake is frozen into equipment for a decade.

So 3GPP does not go from idea to binding text in one step. It goes through a study whose output nobody has to obey, and only then writes text that everybody does. Ambient IoT is a clean example, because the whole path happened recently and is still visible in the paperwork.

2.2 The four kinds of paper

Four words cover almost everything filed in this area, and each one has a precise meaning:

  • A study item investigates a question and produces a technical report, a TR. Its short name always begins FS_, for feasibility study. Ten of this area's items are studies [2].

  • A work item produces or changes a technical specification, a TS — binding text that says what a conforming product does.

  • A SID or a WID is the few-page document that proposes the study or the work, and, once a plenary approves it, defines it. SID new, SID revised, WID new and WID revised are the types you see in a document list; the founding one here was a SID new SP-220085 and the SA1 normative work opened with a WID new SP-231403.

  • A plenary is the three-monthly meeting of a whole technical area that signs the work off. SA, RAN and CT each hold one.

2.3 What the paper actually is

Once work is running, the documents are mostly one of four kinds. The whole area breaks down like this:

Kind What it is How many
discussion a company arguing a position 3973 [3]
pCR one edit to a report still being written 3620 [4]
CR one edit to a published specification 1538 [5]
LS out a letter from one group to another 351 [6]

The shape of that table is the shape of standards work. Nearly four thousand papers exist only to say "here is what I think", and they leave no trace in any specification at all.

2.4 What a plenary approval actually looks like

The types in the document list are precise, and they tell you the state of a piece of work at a glance:

  • SID new — a study is being proposed for the first time. The founding one here is SP-220085, from SA WG1, approved at SP-95-e SP-220085.

  • SID revised — a study already running is being re-scoped. RP-232404 is a revision of the RAN feasibility study, RP-240826 of the RAN solutions study RP-232404 RP-240826.

  • WID new — binding work is being proposed. SP-250377 for the architecture, SP-250369 for charging, both at SP-107 SP-250377 SP-250369.

  • WID revised — binding work already running is being re-scoped. RP-252105 for the RAN work, CP-252196 for the CT work, SP-251196 for the security work RP-252105 CP-252196 SP-251196.

A revision is not a failure. It is how a work item that has met something unexpected is brought back into line with what the group is actually doing, and the revised document replaces the original as the definition of the work.

2.5 The road this area actually took

Thirty-seven work items and study items carry an Ambient IoT name [7]. Stripped to its spine, the road ran like this:

  • A1. SA1 asked what the system must do. Study FS_AmbientIoT, unique id 950004, 2022 to 2023 FS_AmbientIoT.

  • A2. RAN asked whether a radio was possible. Study FS_Ambient_IoT_RAN, unique id 970078, the only Rel-18 item in the area FS_Ambient_IoT_RAN.

  • A3. SA1 turned its answer into requirements. Work item AmbientIoT, unique id 1020030, approved as SP-231403 AmbientIoT.

  • A4. RAN1 looked for actual radio designs. Study FS_Ambient_IoT_solutions, unique id 1020085, approved as RP-240826 FS_Ambient_IoT_solutions RP-240826.

  • A5. SA2 studied the architecture. Study FS_AmbientIoT, unique id 1020071, approved as SP-240969 FS_AmbientIoT SP-240969.

  • A6. SA3 studied the security. Study FS_Ambient_IoT_Sec, unique id 1030031, approved as SP-240506 FS_Ambient_IoT_Sec SP-240506.

  • A7. Everybody wrote binding text. RAN1's Ambient_IoT_Solutions-Core Ambient_IoT_Solutions-Core, SA2's AmbientIoT-ARC approved as SP-250377 AmbientIoT-ARC SP-250377, SA3's AmbientIoT-SEC AmbientIoT-SEC, and the CT groups' shared item approved as CP-252196 CP-252196.

  • A8. Phase 2 started before phase 1 had finished. SA2's study FS_AmbientIoT_Ph2_ARC opened as SP-250834 in June 2025 FS_AmbientIoT_Ph2_ARC SP-250834, and its normative follow-on AmbientIoT_Ph2-ARC as SP-260296 in March 2026 AmbientIoT_Ph2-ARC SP-260296.

2.6 Why the same name appears twice

Two things about the naming trip people up, and both matter when you go looking for documents.

One short name, several work items. The SA1 study and the SA2 study are both called FS_AmbientIoT — different groups, different unique ids, different years FS_AmbientIoT FS_AmbientIoT. The same happens with AmbientIoT AmbientIoT AmbientIoT. The unique id is what identifies an item; the short name is only what you type into a search box.

One work item, several parts. A RAN work item is normally cut into a core part and a performance part, under different working groups, with different finish dates. Ambient_IoT_Solutions is the parent Ambient_IoT_Solutions; the core part sits with RAN1 Ambient_IoT_Solutions-Core and the performance part with RAN4 Ambient_IoT_Solutions-Perf. The same split repeats in phase 2 Ambient_IoT_Solutions_Ph2 Ambient_IoT_Solutions_Ph2-Core Ambient_IoT_Solutions_Ph2-Perf.

That is why the register holds 37 items while the readable list in How to follow this area yourself shows 24: the other thirteen are umbrella rows and sibling parts [7].

2.7 Phase two, and what "phase" means here

Phase 2 is not a correction of phase 1. It is a second, wider work item that starts once the first has settled, and it says so in its own words:

Phase 1 is Rel-19 and phase 2 is Rel-20, and the document counts show the handover in progress. Rel-18 carries 179 Ambient IoT documents [8], Rel-19 carries 8200 [9], and Rel-20 carries 2176 so far [10].

Each of those three figures counts the documents whose release column carries that release, and nothing else — so they do not add up to the area's total of 10771 documents [11], because some documents carry no release at all.

2.8 Where to read on

The documents that define each step of this road are the SIDs and WIDs themselves, listed by number in How to follow this area yourself.

Every one lives on 3gpp.org as a zip file, and this school carries the text of none of them. The register gives the number, the meeting and the address.

Who did each step is Seventeen groups, and where the weight sat.

Where the numbers in this chapter come from

  1. 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
  2. 10 of them are studies of the work items above, the ones whose acronym starts FS_, which is how 3GPP marks a feasibility study, read 2026-08-04
  3. 3973 Ambient IoT documents of type discussion Ambient IoT rows of `tdoc` whose type column is 'discussion', read 2026-08-04
  4. 3620 Ambient IoT documents of type pCR Ambient IoT rows of `tdoc` whose type column is 'pCR', read 2026-08-04
  5. 1538 Ambient IoT documents of type CR Ambient IoT rows of `tdoc` whose type column is 'CR', read 2026-08-04
  6. 351 Ambient IoT documents of type LS out Ambient IoT rows of `tdoc` whose type column is 'LS out', read 2026-08-04
  7. 37 Ambient IoT work items and study items folders under /var/www/whatthespec.net/data/data/wis whose metadata.json carries an acronym matching AmbientIoT, Ambient_IoT or AIoT; all 9406 folders were read and 5 other 'ambient' items were rejected, read 2026-08-04
  8. 179 Ambient IoT documents in Rel-18 Ambient IoT rows of `tdoc` whose release column is Rel-18, read 2026-08-04
  9. 8200 Ambient IoT documents in Rel-19 Ambient IoT rows of `tdoc` whose release column is Rel-19, read 2026-08-04
  10. 2176 Ambient IoT documents in Rel-20 Ambient IoT rows of `tdoc` whose release column is Rel-20, read 2026-08-04
  11. 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

Every source this course is built on

Check yourself

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

Q2.1 What does a work item short name starting `FS_` tell you?

Q2.2 How many work items and study items does the register hold for this area?

Q2.3 What is the difference between a CR and a pCR?

Q2.4 Which kind of document is the most common in this area?

Q2.5 Why is a RAN work item often split into a "Core" part and a "Perf" part?

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