Layer 1
Requirements / Stage 1 orientation
TS 22.261
Service requirements for the 5G system
S1 · Rel-15inferredOrientation inferred from the 22-series; this is not an official 3GPP stage assignment.
curatedreviewedreviewed from Rel-15
Feature lineage · Network Slicing
Slice selection, architecture, policy and UE/core signalling.
Mapped specs5
Explicit stage labels0
Inferred orientations5
Relationships5
Connected WIs100
Rel-19 CR context50
1 spec
Layer 2
System architecture & procedures / Stage 2 orientation
TS 23.501
System architecture for the 5G System (5GS)
S2 · Rel-15inferredOrientation inferred from the 23-series; this is not an official 3GPP stage assignment.
TS 23.502
Procedures for the 5G System (5GS)
S2 · Rel-15inferredOrientation inferred from the 23-series; this is not an official 3GPP stage assignment.
TS 23.503
Policy and charging control framework for the 5G System (5GS); Stage 2
S2 · Rel-15inferredOrientation inferred from the 23-series; this is not an official 3GPP stage assignment.
Layer 3
UE protocol realization
TS 24.501
Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3
C1 · Rel-15inferredOrientation inferred from the 24-series; this is not an official 3GPP stage assignment.
Primary feature evidence
Topic source Work Item
NETSLICE
Management and orchestration of 5G networks and network slicing
Rel-15 · PCG approved · S5 · Work Plan 100%Connected work
Work Items touching mapped specs
These Work Items share one or more mapped specifications. Atlas does not automatically claim that every connected Work Item defines this feature.
5GProtoc19Rel-19 · connected · 100%
3GPP ↗5GProtoc19-non3GPPRel-19 · connected · 100%
3GPP ↗5GSAT_Ph3Rel-19 · connected · 100%
3GPP ↗5GSAT_Ph3Rel-19 · connected · 100%
3GPP ↗5GSAT_Ph3-ARCRel-19 · connected · 100%
3GPP ↗5GSAT_Ph3_ARCHRel-19 · connected · 100%
Historical association · verification pending3GPP ↗5G_FemtoRel-19 · connected · 100%
3GPP ↗5G_FemtoRel-19 · connected · 100%
3GPP ↗5G_ProSe_Ph3Rel-19 · connected · 100%
3GPP ↗5G_RTP_Ph2Rel-19 · connected · 100%
3GPP ↗AIML_CNRel-19 · connected · 100%
Historical association · verification pending3GPP ↗AIML_MT_Ph2Rel-19 · connected · 100%
3GPP ↗Cross-spec traceability
Release-valid relationships
23.502stage realization of23.501curatedreviewed
23.503policy for23.501curatedreviewed
24.501procedure component23.502curatedreviewed
23.501stage realization of22.261curatedreviewedevidence ↗
24.501stage3 realization of23.501curatedreviewedevidence ↗
Primary WI evolution
Change Requests linked to the primary Work Item
Rel-19 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-19; they are not automatically attributed to the feature.
24.501 · CR 6489 rev.2
Update on UE capability indication for rangingsl
withdrawn3GPP CR ↗24.501 · CR 6949
Restrictions by local regulations for emergency service
reissued3GPP CR ↗24.501 · CR 6956
Unexpected MM cause for CIOT user data container
reissued3GPP CR ↗24.501 · CR 6958
Extend faster service recovery to CustomLLFailureRetry5G
reissued3GPP CR ↗24.501 · CR 6977
Conditions to include Additional information IE in UL NAS TRANSPORT message
reissued3GPP CR ↗24.501 · CR 6997
Correction to the handling of the EMM parameters in eCALL-INACTIVE state.
reissued3GPP CR ↗24.501 · CR 7003
Various corrections
reissued3GPP CR ↗24.501 · CR 7006 rev.1
Correction to MA PDU session establishment and modification
reissued3GPP CR ↗24.501 · CR 7001 rev.1
Terminology alignment for ATSSS-LL steering functionality
reissued3GPP CR ↗24.501 · CR 6981 rev.1
Clarification for the unavailability period
reissued3GPP CR ↗24.501 · CR 6983 rev.1
Correction about the Discontinuous coverage maximum time offset IE
reissued3GPP CR ↗24.501 · CR 6990 rev.1
Emergency call delay over 3GPP with ongoing procedure over non-3GPP
reissued3GPP CR ↗24.501 · CR 6767 rev.4
5GSM sublayer operation upon receiving an indication that the CIoT user data was not forwarded due to congestion control and a timer value from the 5GMM sublayer
reissued3GPP CR ↗24.501 · CR 6989 rev.1
Local de-registration during unavailability period in 5G.
reissued3GPP CR ↗24.501 · CR 6947 rev.1
Enabling N1 mode capability when slice is available
reissued3GPP CR ↗Candidate expansion · review required
Specifications Atlas may be missing from this topic
Inferred only. These records are not part of the reviewed semantic catalogue. The ranking score orders structural evidence; it is not a probability or confidence value, and there is no automatic promotion action.
TS 29.503
5G System; Unified Data Management Services; Stage 3
C4 · Rel-15inferredrank 1800moderate evidence
TS 29.522
5G System; Network Exposure Function Northbound APIs; Stage 3
C3 · Rel-15inferredrank 1750moderate evidence
TS 29.571
5G System; Common Data Types for Service Based Interfaces; Stage 3
C4 · Rel-15inferredrank 1650moderate evidence
TS 29.510
5G System; Network function repository services; Stage 3
C4 · Rel-15inferredrank 1575moderate evidence
TS 29.518
5G System; Access and Mobility Management Services; Stage 3
C4 · Rel-15inferredrank 1575moderate evidence
TS 29.513
5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3
C3 · Rel-15inferredrank 1475moderate evidence
TS 29.502
5G System; Session Management Services; Stage 3
C4 · Rel-15inferredrank 1415strong evidence
graph adjacency
interface_specification with mapped TS/TR 23.502
TS 29.512
5G System; Session Management Policy Control Service; Stage 3
C3 · Rel-15inferredrank 1350moderate evidence
TS 29.244
Interface between the Control Plane and the User Plane nodes
C4 · Rel-14inferredrank 1225moderate evidence
TS 29.514
5G System; Policy Authorization Service; Stage 3
C3 · Rel-15inferredrank 1150moderate evidence
TS 27.007
AT command set for User Equipment (UE)
C1 · Rel-4inferredrank 1100moderate evidence
TS 23.122
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
C1 · Rel-4inferredrank 1075moderate evidence
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.