No indexed CRs are linked to the primary Work Item at or before this release.
Rel-15 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-15; they are not automatically attributed to the feature.
22.261 · CR 0002
Replacement of 5G-RAN with NG-RAN
revised
22.261 · CR 0003
Updates to Definitions in TS 22.261
revised
22.261 · CR 0003 rev.1
Updates to Definitions in TS 22.261
noted
22.261 · CR 0004
Clarification on Multiple Network
revised
22.261 · CR 0004 rev.1
Clarification on Multiple Network
revised
22.261 · CR 0009
Clarification of POTS and H.248
noted
22.261 · CR 0010
Update of charging aspects in 22.261
noted
22.261 · CR 0011
Editorial modification for clarification on removal of network function
revised
22.261 · CR 0011 rev.1
Editorial modification for clarification on removal of network function
revised
22.261 · CR 0011 rev.2
Editorial modification for clarification on removal of network function
revised
22.261 · CR 0015 rev.2
Efficient User Plane
revised
22.261 · CR 0015 rev.3
Efficient User Plane
revised
22.261 · CR 0021 rev.1
Clarifications on network slicing
revised
22.261 · CR 0021 rev.2
Clarifications on network slicing
revised
22.261 · CR 0021 rev.3
Clarifications on network slicing
approved
Traceability limits
What this lineage is not claiming
The reviewed topic-to-specification mapping is Atlas-curated and non-normative even when its source is an official 3GPP record.
When an explicit stage classification is unavailable, specification layers are inferred from the TS/TR series and are labelled inferred rather than presented as official 3GPP stage assignments.
Connected Work Items and release-context Change Requests share mapped specifications; only the topic source Work Item is treated as primary evidence for the reviewed topic mapping.
This is traceability evidence and navigation, not a clause-by-clause normative feature definition.