5 The specifications this work touches

5.1 What counts as touched

Fifty-three specifications are affected by Ambient IoT work. ^[1]

That number is not a judgement anybody made. A specification joins the 53 when either of two things is true: a work item description declares it impacted, or at least ten Ambient IoT documents name it.

The 53 fall into three piles, and telling them apart is most of understanding what this work actually did to the 5G system.

5.2 The documents written for this work

Fifteen documents exist because of Ambient IoT. Their catalogue titles all name it, which is how they are told apart from the third pile.

Spec	What it is for	Group	Documents	CRs
TS 22.369 TS 22.369	what the system must do for battery-less devices	SA1	18	17
TS 23.369 TS 23.369	how the core network is put together to support them	SA2	816	524
TS 23.370 TS 23.370	the application layer on top of the service	SA6	70	0
TS 24.369 TS 24.369	the signalling a device exchanges with the network	CT1	439	144
TS 29.369 TS 29.369	the service that stores and serves device data	CT4	110	94
TS 29.506 TS 29.506	how that data is kept in the shared data store	CT4	43	25
TS 29.569 TS 29.569	the services the Ambient IoT network function offers	CT3	102	47
TS 33.369 TS 33.369	security for isolated private networks	SA3	385	150
TS 38.191 TS 38.191	what the device's radio must transmit and receive	RAN4	98	59
TS 38.194 TS 38.194	the same for the base station and the carrier-wave node	RAN4	69	39
TS 38.195 TS 38.195	how those two are tested for conformance	RAN4	32	5
TS 38.291 TS 38.291	the physical layer — bits on the air	RAN1	12	8
TS 38.391 TS 38.391	the medium access control protocol	RAN2	36	28
TS 38.591-1 TS 38.591-1	device conformance, the shared test environment	RAN5	17	0
TS 38.591-2 TS 38.591-2	device conformance, radio transmission and reception	RAN5	10	0

TS 23.369 dwarfs the rest: 816 documents and 524 change requests, against 439 and 144 for the next busiest, TS 24.369. TS 23.369 TS 24.369

The two RAN5 documents at the bottom, TS 38.591-1 and TS 38.591-2, carry no change requests yet. TS 38.591-1 TS 38.591-2 Conformance testing is the last thing to happen, and the record shows it not having happened.

5.3 The reports

A report studies a question, is published once and is then closed. These eight are where the thinking of this area is recorded.

Report	What it studied	Group	Documents
TR 22.840 TR 22.840	the founding study: use cases and requirements	SA1	497
TR 38.848 TR 38.848	whether a RAN design is feasible at all	RAN	32
TR 38.769 TR 38.769	the radio solutions themselves	RAN1	198
TR 23.700-13 TR 23.700-13	architecture support, phase 1	SA2	746
TR 23.700-30 TR 23.700-30	architecture support, phase 2	SA2	264
TR 23.700-26 TR 23.700-26	application enablement	SA6	178
TR 33.713 TR 33.713	security aspects, phase 1	SA3	708
TR 33.714 TR 33.714	security aspects, phase 2	SA3	216

5.4 The documents that already existed

The third pile is ordinary 5G specifications that had to be edited to let Ambient IoT in. The description in each row is what that document is for in general, taken from the specification catalogue — not what Ambient IoT did to it.

Spec	What it is for in general	Group	CRs
TS 38.413 TS 38.413	the protocol between the radio network and the core	RAN3	77
TS 29.522 TS 29.522	the interfaces the core network exposes outwards	CT3	70
TS 38.300 TS 38.300	the overall description of the NR radio network	RAN2	58
TS 29.518 TS 29.518	access and mobility management services	CT4	55
TS 23.003 TS 23.003	numbering, addressing and identification	CT4	46
TS 29.510 TS 29.510	the register of network functions	CT4	40
TS 23.502 TS 23.502	the procedures of the 5G system	SA2	26
TS 29.504 TS 29.504	the shared data store's own services	CT4	26
TS 29.571 TS 29.571	the data types every core service shares	CT4	24
TS 23.501 TS 23.501	the architecture of the 5G system itself	SA2	14
TS 38.410 TS 38.410	general principles of the radio-to-core interface	RAN3	13
TS 24.007 TS 24.007	general rules for signalling messages	CT1	10
TS 28.552 TS 28.552	the measurements a network reports about itself	SA5	10
TS 22.261 TS 22.261	the service requirements of the whole 5G system	SA1	9
TS 38.401 TS 38.401	how the radio network is built	RAN3	9
TS 32.254 TS 32.254	charging through the exposure interfaces	SA5	8
TS 38.412 TS 38.412	how signalling is carried to the core	RAN3	7
TS 38.423 TS 38.423	the protocol between two radio network nodes	RAN3	6

The register carries the other specifications of the 53 too, each with its catalogue title, its owning group and its counts. ^[1]

Read that table as a bill for admitting a new kind of device: numbering had to change, the register of network functions had to change, the shared data types had to change, and the measurements the network reports about itself had to change.

5.5 Two the catalogue does not know

Two documents 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: TS 29.568 and TS 33.340. 29.568 33.340

They are named here because leaving them out would be worse. What they are for is not something this course can say, and a guess would be indistinguishable from an invention.

5.6 Where to read this yourself

The four numbers worth opening first are TS 23.369 for the system, TR 38.769 for the radio reasoning, TS 24.369 for what a device says, and TS 22.369 with its report TR 22.840 for the requirements underneath everything. TS 23.369 TR 38.769 TS 24.369 TS 22.369 TR 22.840

For the security model, read TR 33.713 first and TS 33.369 after it. TR 33.713 TS 33.369

This school does not carry the text of any of the 53 documents. Every row above tells you what a document is for and how much of this work landed in it; the words are on 3gpp.org.