Layer 1
Core-network protocol & service realization
TS 29.281
General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U)
C4 · Rel-8inferredOrientation inferred from the 29-series; this is not an official 3GPP stage assignment.
curatedreviewedreviewed mapping begins in Rel-15
Feature lineage · NG-RAN Functional Split
gNB-CU-CP, gNB-CU-UP and gNB-DU architecture with F1 and E1 control relationships.
Mapped specs4
Explicit stage labels0
Inferred orientations4
Relationships1
Connected WIs14
Rel-9 CR context16
1 spec
Layer 2
RAN / radio realization
TS 38.401
NG-RAN; Architecture description
R3 · Rel-15inferredOrientation inferred from the 38-series; this is not an official 3GPP stage assignment.
TS 38.473
NG-RAN; F1 Application Protocol (F1AP)
R3 · Rel-15inferredOrientation inferred from the 38-series; this is not an official 3GPP stage assignment.
TS 38.463
NG-RAN; E1 Application Protocol (E1AP)
R3 · Rel-15inferredOrientation inferred from the 38-series; this is not an official 3GPP stage assignment.
Primary feature evidence
Topic source Work Item
The reviewed topic source is not an indexed Work Item record. The source link above remains the primary evidence anchor.
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.
MBMS_EPSRel-9 · connected · 100%
3GPP ↗MBMS_EPSRel-9 · connected · 100%
3GPP ↗NDS_BackhaulRel-9 · connected · 100%
3GPP ↗TEI9Rel-9 · connected · 100%
3GPP ↗FS_SAERel-8 · connected · 100%
3GPP ↗LTERel-8 · connected · 100%
3GPP ↗SAESRel-8 · connected · 100%
3GPP ↗SAESRel-8 · connected · 100%
3GPP ↗SAES-LTERel-8 · connected · 100%
3GPP ↗SAES-SA-FP_3GPPRel-8 · connected · 100%
3GPP ↗SAES-SA-FP_3GPPRel-8 · connected · 100%
3GPP ↗SAES-SA-FP_n3GPPRel-8 · connected · 100%
3GPP ↗Cross-spec traceability
Release-valid relationships
38.473interface specification38.401curatedreviewed
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-9 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-9; they are not automatically attributed to the feature.
29.281 · CR 0013
MBMS for EPS support in GTPv1-U
revised29.281 · CR 0013 rev.1
MBMS for EPS support in GTPv1-U
approved29.281 · CR 0021
GTP-U path definition
revised29.281 · CR 0021 rev.1
GTP-U path definition
withdrawn29.281 · CR 0023
End Marker
revised29.281 · CR 0023 rev.1
End Marker
approved29.281 · CR 0025
GTP-U sequence number handling
approved29.281 · CR 0027
Sequence Number corrections
revised29.281 · CR 0027 rev.1
Sequence Number corrections
approved29.281 · CR 0028
Message applicability of MBMS in GTP-U
revised29.281 · CR 0028 rev.1
Message applicability of MBMS in GTP-U
approved29.281 · CR 0030
MTU Size
postponed29.281 · CR 0033
End Marker message
revised29.281 · CR 0033 rev.1
End Marker message
revised29.281 · CR 0035
Echo Request & Echo Response
revisedTraceability 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.