14 What the record cannot tell you

14.1 Why a course should end like this

Thirteen chapters of numbers make a subject look settled. It is not, and the most useful thing this course can do at the end is mark out exactly where its own evidence stops.

Everything below is a question a reader would reasonably ask that this record cannot answer. Each one comes with what to read instead.

14.2 It cannot date anything

The register holds meeting codes and version numbers. It holds no date for the freezing of a release, the ending of a study or the publication of a specification.

So no sentence of the form "Release 20 completes in …" can be supported here, and none appears in this course. Read instead: 3GPP's own release timetable, which is not part of this data.

The only time-like figures anywhere are the per-year counts of documents uploaded, and 78 documents carry no upload time even for that ^[1].

14.3 It names nobody

The record carries the company or the role a document came from — "SA WG2", "Nokia (moderator)" — and never a human being's name RP-234069 SP-250809.

The work item descriptions on this machine do name rapporteurs. None of those names reached the register and none may reach a chapter. Read instead: the work item description itself, if you need to know who to ask.

14.4 It gives no reason for anything

A document's status is one word: approved, revised, noted, endorsed, postponed or withdrawn. SP-250809 is recorded as revised SP-250809; SP-250833 as approved SP-250833. Why, this data does not say.

That covers a lot of interesting questions. Why the radio rule-writing sits with RAN3 rather than RAN1. Why SA5 opened two studies instead of one. Why the stage 2 specification narrowed to drones. All of them have answers; none of the answers is here.

Read instead: the meeting reports of the group in question, which are outside this data.

14.5 It carries no technical content

This is the biggest gap and the one most likely to catch somebody out.

The register holds titles, scopes, objectives and counts. It holds no key issue, no candidate solution, no evaluation result and not one number out of TR 38.765 TR 38.765.

14.6 Every count is a floor

Documents were counted only when they carry one of the 14 work item acronyms. 440 documents whose titles say "integrated sensing" or "ISAC" carry no acronym at all ^[2], including every plenary approval document and everything filed before a work item existed to file it under. None of them is inside the 3492 ^[3].

And the counts are counts of what this machine holds, not of what 3GPP holds. Where the difference could matter, the right form of words is "the local record holds …".

14.7 The word is used by other work

2053 documents in this record say sensing and mean sidelink partial sensing, listen-before-talk channel sensing or the separate 6G work ^[4]. Nothing in this course was found by searching for the word, and nothing in it describes any of those three.

14.8 Small holes worth knowing

• Two specifications were left out because exactly one document names each and no work item does ^[5]. One mention is as likely a filing mistake as a real link.

• The oldest work item has no description. FS_Sensing, the Rel-19 SA1 study, has a work plan entry and an approval document but no description on this machine FS_Sensing — so no objective, no leadership line and no target document is recorded for it.

• Two acronyms cover more than one work plan entry. Sensing has three Sensing Sensing and Sensing-CT has three Sensing-CT Sensing-CT. Any count of "work items" has to say whether it means 18 entries ^[6] or 14 acronyms ^[7].

• The RAN work item is filed twice, once as the feature and once as its core part, both described by the same document, and only the core part has anything against it NR_Sensing_bis NR_Sensing_bis-Core.

• CT3 has no entry. The CT work item names CT3 as doing half the job, and no document at a CT3 meeting carries a sensing acronym yet ^[8]. A group with no entry is not a group with no involvement — the map in The map of the groups, and where the weight sat counts who filed, not who cared.

14.9 It cannot compare

Nothing in this data measures positioning, or AI in the network, or ambient IoT, or any other area of 3GPP work.

So there is no way to say from here that sensing is the largest, the fastest or the most contested subject in Release 20. 2069 of its documents are marked Release 20 ^[9] and that number stands entirely alone.

14.10 How to quote this course without misleading anybody

Four habits, and they are the same four this course tries to keep.

• Say which count you mean. 18 work plan entries or 14 acronyms ^{[6] [7]}; documents filed as change requests or change requests received by a document. A bare number with no question attached is the commonest way this data gets misused.

• Say "the local record holds". These are counts of what one machine holds, not of what 3GPP holds, and where the difference could matter the words should say so.

• Say "floor", not "total". 440 documents are outside every count here ^[2].

• Never turn a meeting code into a date. SA#111 is a position in a sequence, and nothing here converts it into a month SP-260110.

14.11 What this course is good for

Given all of the above, it is worth being clear about what does survive.

• What each group set out to do, in its own words, with the document it said it in.

• Which specifications exist, which are being changed, and how far each has got — the tables in The specifications, one at a time and Where the work stands, and why there are no dates.

• How to find the rest yourself — the acronyms, the traps and the reading order in How to follow this area yourself.

That is a map and a set of hop-off points, which is what this school is for. The text of the specifications is not carried here and never will be.

14.12 Where to go from here

• TS 22.137 TS 22.137 for the requirements, TR 22.837 TR 22.837 for the use cases behind them.

• TR 23.700-14 TR 23.700-14 and TS 23.137 TS 23.137 for the system.

• TR 38.901 TR 38.901 and TR 38.765 TR 38.765 for the radio, TR 33.777 TR 33.777 for security and privacy.

• RP-261566, SP-260297, SP-260317 and CP-261274 RP-261566 SP-260297 SP-260317 CP-261274 to follow what happens next.

Every source this course cites is listed, with the exact question that produced it, on the course's own sources page.