14 What the record cannot tell you

14.1 Why a chapter of things this course will not say

A learning site is only worth reading if it stops where its evidence stops. This course is built from 3GPP's own paperwork: work plan rows, document lists, catalogue entries, and the objective sections of work item descriptions.

That material answers a great deal and is silent on a great deal more.

What follows is every question a reader will reasonably ask that the data cannot settle. Each one names what to do instead, because a gap without a route out of it is not honesty, it is a shrug.

14.2 Eleven things this record does not hold

• U1. Whether phase 2 is finished. It is not, and nothing here says it is. The finish dates in Where the work stands, and what a percentage is worth are targets held in the work plan, not recorded outcomes, and eleven phase 2 items sit between 0 and 70 per cent AmbientIoT_Ph2-ARC Ambient_IoT_Solutions_Ph2-Perf. Instead: check the item's own page on 3gpp.org.

• U2. How fresh a completion figure is. A work plan row records when it was last modified, not whether anything has moved since. An item at 20 per cent may have finished a year ago and never been touched AmbientIoT_Ph2-OAM. Instead: treat the figure as a date-stamped opinion, not a status.

• U3. When the outdoor study really started. Its recorded start is a leftover from a template and predates the subject by years. Its finish date, 2026-03-03, is real FS_Ambient_IoT_Outdoor_Active. Instead: quote the finish date and the approving document, RP-253394 RP-253394.

• U4. How many documents a work item has. Counts are per short name, not per item. Four CT work items share AmbientIoT-CT and all four show the same 959 AmbientIoT-CT AmbientIoT-CT. The two FS_AmbientIoT rows and the two AmbientIoT rows do the same. Instead: name the short name whenever you quote such a number, and never add them together.

• U5. Which reading of Ambient_IoT_Solutions is right. The umbrella row stands at 80 per cent while both parts under it stand at 100, and the data does not settle it Ambient_IoT_Solutions Ambient_IoT_Solutions-Core Ambient_IoT_Solutions-Perf. Instead: quote the part, which is the row the working group actually updates.

• U6. What TS 29.568 and TS 33.340 are for. Both are declared impacted by phase 2 work item descriptions, and the specification catalogue on this machine holds no title, no owning group and no status for either 29.568 33.340. Instead: open their information pages on 3gpp.org, whose addresses the register carries.

• U7. Why CT6 has filed nothing. It leads a work item and has zero documents, zero meetings and no owned specification here CT6 AmbientIoT_Ph2-CT. Whether the work has not started, or is filed under a name this register cannot see, the data does not say. Instead: look in the CT6 document folder itself.

• U8. What the phase 2 management work is for. Its work item description has no objective section — the document jumps from section 3 to section 5, so there is nothing to quote AmbientIoT_Ph2-OAM. Instead: read SP-260311 in full SP-260311.

• U9. What TS 22.369's scope says. The parsed copy on this machine begins at clause 2, so the requirements specification cannot be quoted from its own scope TS 22.369. Instead: open the published version.

• U10. Exactly how many documents belong to a year or a release. Some of the 10771 documents ^[1] carry no upload date and some carry no release, so a figure such as the 4457 filed in 2025 ^[2] counts only the rows that do carry one. Instead: read those figures as floors, not totals.

• U11. Anything usable about 6G. The phase 2 RAN work item excludes "the features of 6G relevant to IoT" from its scope, and that clause is all the register carries ^[3]. Instead: nothing. One exclusion clause is not enough to build a sentence on, and this course does not try.

14.3 Four kinds of thing that are simply not in the data

Beyond the eleven specific gaps, four whole categories are missing, and no amount of reading the register will produce them.

No attendance, no votes, no debate. The data holds a document's outcome word — approved, agreed, revised, noted, merged, withdrawn — and nothing about why SP-220085. Never write why a group decided something. The nearest thing to a reason is the objective section of a work item description, and this course quotes those where they exist.

No text of any letter between groups. Four are named in this course by number and title: two from SA3 at meeting S3-128 S3-262519 S3-262517, two from SA2 at meeting S2-175 S2-2605244 S2-2605226. What any of them said is not held here. The register gives the address; the reading is yours.

No products, no chips, no deployments, no market. Not one of the 10771 documents says whether anybody has built an Ambient IoT device, sold one, or run a network with them ^[1]. The data is 3GPP's own paperwork and stops at the specification. A course that told you the market outlook would be making it up.

No abbreviation explained beyond what a title spells out. The register carries names exactly as written — "AIOTF", "Topology 2", "Device 1", "DO-A" ^[4]. Where this course explains one, it is because a catalogue title spelled it out, as TS 29.569's title spells out the Ambient IoT function TS 29.569. Everything else stays unexplained on purpose.

14.4 What the data is good for

Having said all of that, it is worth being clear about what this record does support, because it is a great deal:

• V1. Who did what, when, and in which order — the whole of Seventeen groups, and where the weight sat.

• V2. Which document to open for any part of the work — the whole of How to follow this area yourself.

• V3. What each work item said it was for, in its own words, wherever the description has an objective section — the founding SA1 study ^[5], the RAN normative work ^[6] and the CT protocol work ^[7] each carry one.

• V4. How much effort went where, with every number's origin restated: 900 companies and groups ^[8] filing across 179 meetings ^[9].

• V5. Which specifications exist because of this work and which were only amended by it — The fifty-three specifications, and what this work put in each.

That is a map. It is not the territory, and this last chapter is here so that nobody mistakes one for the other.

14.5 Where to read on

Everything named in this course lives on 3gpp.org, and every register entry carries its address.

The four to read first are TR 22.840 for the reasoning, TS 23.369 for the system, TR 38.769 for the radio and TS 24.369 for what a device says TR 22.840 TS 23.369 TR 38.769 TS 24.369.

The sources page of this course lists every entry cited anywhere in it, each with what it is and where it came from.