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 WIs22
Rel-11 CR context39
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.
SIRIGRel-11 · connected · 100%
3GPP ↗SIRIGRel-11 · connected · 100%
3GPP ↗SaMOG_WLAN-CNRel-11 · connected · 100%
3GPP ↗TEI11Rel-11 · connected · 100%
3GPP ↗LIPARel-10 · connected · 100%
3GPP ↗SIPTORel-10 · connected · 100%
3GPP ↗SMOG-St3Rel-10 · connected · 100%
3GPP ↗TEI10Rel-10 · connected · 100%
3GPP ↗MBMS_EPSRel-9 · connected · 100%
3GPP ↗MBMS_EPSRel-9 · connected · 100%
3GPP ↗NDS_BackhaulRel-9 · connected · 100%
3GPP ↗TEI9Rel-9 · 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-11 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-11; they are not automatically attributed to the feature.
29.281 · CR 0060
Length of PDCP PDU number
revised29.281 · CR 0043
Default inner MTU size
approved29.281 · CR 0045
Reference RFC update
revised29.281 · CR 0045 rev.1
Reference RFC update
approved29.281 · CR 0046
Defination of C-TEID in 29.281
revised29.281 · CR 0046 rev.1
Defination of C-TEID in 29.281
approved29.281 · CR 0047
GTP-U traffic over aggregated Ethernet links and ECMP routes
withdrawn29.281 · CR 0048
Dynamic allocation of UDP source ports
revised29.281 · CR 0048 rev.1
Dynamic allocation of UDP source ports
approved29.281 · CR 0049
29.281 CR Requirement for sending Error Indication
approved29.281 · CR 0050
Tunnelling between eNodeB and RNC
approved29.281 · CR 0051
Service Type in GTP-U for SIRIG
revised29.281 · CR 0051 rev.1
Service Type in GTP-U for SIRIG
postponed29.281 · CR 0052
Addition of GTP based S2a
revised29.281 · CR 0052 rev.1
Addition of GTP based S2a
approvedTraceability 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.