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-97 CR context0
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.
6G-REQRel-21 · connected · 40%
3GPP ↗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 ↗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-97 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-97; they are not automatically attributed to the feature.
No CR activity targeting the mapped specifications is indexed for Rel-97.
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.