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-20 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.
5GProtoc20-CTRel-20 · connected · 20%
3GPP ↗5GSAT_Ph4Rel-20 · connected · 69%
3GPP ↗5GSAT_Ph4-ARCRel-20 · connected · 100%
3GPP ↗5GSAT_Ph4-REQRel-20 · connected · 100%
3GPP ↗AIML_CN_Ph2-ARCRel-20 · connected · 100%
3GPP ↗AdNRM_Ph4-OAMRel-20 · connected · 90%
3GPP ↗AmbientIoT_Ph2-ARCRel-20 · connected · 95%
3GPP ↗AmbientIoT_Ph2-CTRel-20 · connected · 48%
3GPP ↗CombQoSRel-20 · connected · 100%
3GPP ↗EnergyServ_Ph2-REQRel-20 · connected · 100%
3GPP ↗EnergySys_Ph2-ARCRel-20 · connected · 100%
3GPP ↗EnergySys_Ph2-CTRel-20 · connected · 80%
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-20 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-20; they are not automatically attributed to the feature.
23.501 · CR 6330 rev.5
Support of Ethernet type of BH PDU Session for MWAB
approved3GPP CR ↗23.501 · CR 6459 rev.1
Inclusion of Forbidden EPS Areas in mobility restriction for NR to LTE mobility
approved3GPP CR ↗23.501 · CR 6395 rev.3
Providing per-subscriber Allowed MAC addresses from UDM
approved3GPP CR ↗23.502 · CR 5560 rev.2
Support of allowed MAC addresses in SM subscription data in UDM
approved3GPP CR ↗23.501 · CR 6423 rev.2
Identification of INS case and hosting operator
approved3GPP CR ↗23.503 · CR 1579 rev.2
PCRT update to identify Hosting Network in case of INS
approved3GPP CR ↗23.502 · CR 5574 rev.4
Enhance the registration procedure to identify INS case and hosting operator
approved3GPP CR ↗23.502 · CR 5584 rev.3
PCF service update to identify Hosting Network in case of INS
approved3GPP CR ↗23.502 · CR 5577 rev.4
Enhance the PDU session procedure to support the INS for disaster condition
approved3GPP CR ↗23.502 · CR 5575 rev.6
Enhance the PDU session procedure and mobility procedures to identify INS case and hosting operator
approved3GPP CR ↗23.502 · CR 5599 rev.6
Enhance the registration procedure to support the INS for disaster condition
approved3GPP CR ↗23.501 · CR 6451 rev.7
Introducing NSSAA over EPC
approved3GPP CR ↗23.502 · CR 5528 rev.11
On introducing NSSAA over EPC
approved3GPP CR ↗23.501 · CR 6424 rev.9
Indirect Network Sharing for disaster condition
approved3GPP CR ↗23.501 · CR 6488
Removal of editor's notes related to VFL server registration
approved3GPP 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 1875moderate evidence
TS 29.522
5G System; Network Exposure Function Northbound APIs; Stage 3
C3 · Rel-15inferredrank 1825moderate evidence
TS 29.571
5G System; Common Data Types for Service Based Interfaces; Stage 3
C4 · Rel-15inferredrank 1725moderate evidence
TS 29.510
5G System; Network function repository services; Stage 3
C4 · Rel-15inferredrank 1675moderate evidence
TS 29.518
5G System; Access and Mobility Management Services; Stage 3
C4 · Rel-15inferredrank 1650moderate evidence
TS 29.513
5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3
C3 · Rel-15inferredrank 1550moderate evidence
TS 29.502
5G System; Session Management Services; Stage 3
C4 · Rel-15inferredrank 1490strong 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 1425moderate evidence
TS 29.244
Interface between the Control Plane and the User Plane nodes
C4 · Rel-14inferredrank 1325moderate evidence
TS 29.514
5G System; Policy Authorization Service; Stage 3
C3 · Rel-15inferredrank 1200moderate evidence
TS 23.122
Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode
C1 · Rel-4inferredrank 1125moderate evidence
TS 24.301
Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3
C1 · Rel-8inferredrank 1125moderate 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.