No indexed CRs are linked to the primary Work Item at or before this release.
Rel-16 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-16; they are not automatically attributed to the feature.
23.501 · CR 2864
UE radio capability clarification
revised
23.501 · CR 2867
Removal of ATC
revised
23.501 · CR 2867 rev.1
Removal of ATC
noted
23.501 · CR 2929 rev.1
Support for UPIP for other than NR
approved
23.501 · CR 0735 rev.7
ATSSS Support
merged
23.501 · CR 0736 rev.7
Introduction of indirect communication of NF services
merged
23.501 · CR 1306
Ethernet support clarification
revised
23.501 · CR 1691
Alignment with TS 23.502 and clarification on Extended Buffering
revised
23.501 · CR 1960
Definition of non-public network
status unknown
23.501 · CR 1995
AMF query SMF for PCF ID
status unknown
23.501 · CR 2139
SCP selection of another SCP
revised
23.501 · CR 2164
Correction to network selection with multiple subscribed SNPNs
revised
23.501 · CR 2430
23.501: Revision on PNI-NPN CAG Configuration Update
revised
23.501 · CR 2499
S-NSSAI handling at the Inter PLMN mobility
revised
23.501 · CR 3561
AMF re-allocation in CM connected state
noted
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.