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
revised
29.281 · CR 0013 rev.1
MBMS for EPS support in GTPv1-U
approved
29.281 · CR 0021
GTP-U path definition
revised
29.281 · CR 0021 rev.1
GTP-U path definition
withdrawn
29.281 · CR 0023
End Marker
revised
29.281 · CR 0023 rev.1
End Marker
approved
29.281 · CR 0025
GTP-U sequence number handling
approved
29.281 · CR 0027
Sequence Number corrections
revised
29.281 · CR 0027 rev.1
Sequence Number corrections
approved
29.281 · CR 0028
Message applicability of MBMS in GTP-U
revised
29.281 · CR 0028 rev.1
Message applicability of MBMS in GTP-U
approved
29.281 · CR 0030
MTU Size
postponed
29.281 · CR 0033
End Marker message
revised
29.281 · CR 0033 rev.1
End Marker message
revised
29.281 · CR 0035
Echo Request & Echo Response
revised
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.