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-17 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.
5GProtoc17Rel-17 · connected · 100%
Historical association · verification pending3GPP ↗5GProtoc17-non3GPPRel-17 · connected · 100%
3GPP ↗5GSATRel-17 · connected · 100%
3GPP ↗5GSAT_ARCHRel-17 · connected · 100%
Historical association · verification pending3GPP ↗5GSAT_ARCH-CTRel-17 · connected · 100%
3GPP ↗5G_AISRel-17 · connected · 100%
3GPP ↗5G_ProSeRel-17 · connected · 100%
3GPP ↗5MBSRel-17 · connected · 100%
Historical association · verification pending3GPP ↗5MBS_eMCRel-17 · connected · 100%
3GPP ↗ARCH_NR_REDCAPRel-17 · connected · 100%
Historical association · verification pending3GPP ↗ATSSS_Ph2Rel-17 · connected · 100%
Historical association · verification pending3GPP ↗AVPRODRel-17 · 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
No indexed CRs are linked to the primary Work Item at or before this release.
Rel-17 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-17; they are not automatically attributed to the feature.
22.261 · CR 0365 rev.1
Introduction of Minimization of Service Interruption (MINT)
revised22.261 · CR 0365 rev.2
Introduction of Minimization of Service Interruption (MINT)
approved22.261 · CR 0370
CR0XXX to to 22.261 on access control for MINT
withdrawn22.261 · CR 0371 rev.1
Addition of security requirements for critical medical applications
approved22.261 · CR 0372 rev.1
Addition of medical telemetry requirements
approved22.261 · CR 0374
General descriptions of network controlled interactive service
revised22.261 · CR 0374 rev.1
General descriptions of network controlled interactive service
merged22.261 · CR 0375
Performance requirements of interactive service
revised22.261 · CR 0375 rev.1
Performance requirements of interactive service
revised22.261 · CR 0375 rev.3
Performance requirements of interactive service
approved22.261 · CR 0376
Group operation related requirements of interactive service
revised22.261 · CR 0376 rev.1
Group operation related requirements of interactive service
revised22.261 · CR 0376 rev.2
Group operation related requirements of interactive service
noted22.261 · CR 0378 rev.1
CR to 22.261 on access control for MINT
revised22.261 · CR 0378 rev.2
CR to 22.261 on access control for MINT
revisedCandidate 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 850moderate evidence
TS 29.518
5G System; Access and Mobility Management Services; Stage 3
C4 · Rel-15inferredrank 775moderate evidence
TS 29.510
5G System; Network function repository services; Stage 3
C4 · Rel-15inferredrank 750moderate evidence
TS 29.571
5G System; Common Data Types for Service Based Interfaces; Stage 3
C4 · Rel-15inferredrank 750moderate evidence
TS 38.413
NG-RAN; NG Application Protocol (NGAP)
R3 · Rel-15inferredrank 715strong evidence
graph adjacency
procedure_component with mapped TS/TR 23.502
TS 29.502
5G System; Session Management Services; Stage 3
C4 · Rel-15inferredrank 690strong evidence
graph adjacency
interface_specification with mapped TS/TR 23.502
TS 27.007
AT command set for User Equipment (UE)
C1 · Rel-4inferredrank 675moderate evidence
TS 29.512
5G System; Session Management Policy Control Service; Stage 3
C3 · Rel-15inferredrank 650moderate evidence
TS 29.513
5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3
C3 · Rel-15inferredrank 600moderate evidence
TS 29.522
5G System; Network Exposure Function Northbound APIs; Stage 3
C3 · Rel-15inferredrank 600moderate evidence
TS 38.423
NG-RAN; Xn Application Protocol (XnAP)
R3 · Rel-15inferredrank 600moderate evidence
TS 23.401
General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access
S2 · Rel-8inferredrank 575moderate 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.