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-18 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.
5GProtoc18Rel-18 · connected · 100%
3GPP ↗5GProtoc18Rel-18 · connected · 100%
3GPP ↗5GProtoc18-non3GPPRel-18 · connected · 100%
3GPP ↗5GSATBRel-18 · connected · 100%
Historical association · verification pending3GPP ↗5GSATBRel-18 · connected · 100%
3GPP ↗5GSAT_Ph2Rel-18 · connected · 100%
3GPP ↗5G_ProSe_Ph2Rel-18 · connected · 100%
3GPP ↗5G_eLCS_Ph3Rel-18 · connected · 100%
3GPP ↗5G_eLCS_Ph3Rel-18 · connected · 100%
3GPP ↗5MBS_Ph2Rel-18 · connected · 100%
3GPP ↗5TRSRel-18 · connected · 100%
3GPP ↗5WWC_Ph2Rel-18 · 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-18 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-18; they are not automatically attributed to the feature.
23.502 · CR 3734 rev.1
Procedures update to support policy control enhancements for multi-modal flows
reissued3GPP CR ↗23.502 · CR 3738 rev.1
AF Session procedures update to support PDU Set QoS Parameters
reissued3GPP CR ↗23.502 · CR 3736 rev.1
Introduction of KI#6 conclusion: uplink-downlink transmission coordination
reissued3GPP CR ↗24.501 · CR 5075
NSAC applicability in SNPN
reissued3GPP CR ↗24.501 · CR 5076
Correction on reference of S-NSSAI inclusion in ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message
reissued3GPP CR ↗24.501 · CR 5152
Store the rejected NSSAI for failed or revoked NSSAA associated with EPLMN
reissued3GPP CR ↗24.501 · CR 5153
Handing pending paging message if access attempt for registration procedure is barred
reissued3GPP CR ↗24.501 · CR 4983 rev.1
Equivalent SNPNs: error cases and abnormal cases
reissued3GPP CR ↗23.501 · CR 3864 rev.5
Policy control enhancements to support multi-modal flows
reissued3GPP CR ↗23.503 · CR 0835 rev.7
Policy update to support policy control enhancements for multi-modal services
reissued3GPP CR ↗23.501 · CR 4036 rev.3
Introduction of Alternative S-NSSAI replacement determined by NSSF
revised3GPP CR ↗23.501 · CR 3792 rev.7
PCF support of 5GS Packet Delay Variation monitoring based on QoS monitoring mechanism and exposed to AF
reissued3GPP CR ↗23.503 · CR 0825 rev.3
Introduction of Power Saving requirements for XRM service
reissued3GPP CR ↗23.501 · CR 4033 rev.11
Support of discontinuous coverage
revised3GPP CR ↗23.501 · CR 3887 rev.6
Introduction of 5GS information exposure
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 1325moderate evidence
TS 29.518
5G System; Access and Mobility Management Services; Stage 3
C4 · Rel-15inferredrank 1275moderate evidence
TS 29.571
5G System; Common Data Types for Service Based Interfaces; Stage 3
C4 · Rel-15inferredrank 1275moderate evidence
TS 29.510
5G System; Network function repository services; Stage 3
C4 · Rel-15inferredrank 1225moderate evidence
TS 29.513
5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3
C3 · Rel-15inferredrank 1225moderate evidence
TS 29.522
5G System; Network Exposure Function Northbound APIs; Stage 3
C3 · Rel-15inferredrank 1200moderate evidence
TS 29.512
5G System; Session Management Policy Control Service; Stage 3
C3 · Rel-15inferredrank 1100moderate evidence
TS 29.502
5G System; Session Management Services; Stage 3
C4 · Rel-15inferredrank 1065strong evidence
graph adjacency
interface_specification with mapped TS/TR 23.502
TS 29.244
Interface between the Control Plane and the User Plane nodes
C4 · Rel-14inferredrank 1025moderate evidence
TS 38.413
NG-RAN; NG Application Protocol (NGAP)
R3 · Rel-15inferredrank 965strong evidence
graph adjacency
procedure_component with mapped TS/TR 23.502
TS 27.007
AT command set for User Equipment (UE)
C1 · Rel-4inferredrank 925moderate evidence
TS 29.514
5G System; Policy Authorization Service; Stage 3
C3 · Rel-15inferredrank 925moderate 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.