No indexed CRs are linked to the primary Work Item at or before this release.
Rel-10 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-10; they are not automatically attributed to the feature.
29.281 · CR 0031
Addition of GTP-U interface over S2b
revised
29.281 · CR 0031 rev.1
Addition of GTP-U interface over S2b
approved
29.281 · CR 0033 rev.2
End Marker message
approved
29.281 · CR 0035 rev.1
Echo Request & Echo Response
approved
29.281 · CR 0037
TEID value 0 for GTP-U tunnel
revised
29.281 · CR 0037 rev.1
TEID value 0 for GTP-U tunnel
revised
29.281 · CR 0037 rev.2
TEID value 0 for GTP-U tunnel
approved
29.281 · CR 0038
GTP-U protocol missing information
revised
29.281 · CR 0038 rev.1
GTP-U protocol missing information
revised
29.281 · CR 0038 rev.2
GTP-U protocol missing information
revised
29.281 · CR 0038 rev.3
GTP-U protocol missing information
approved
29.281 · CR 0039
Scope of GTPv1
approved
29.281 · CR 0040
eNB Error Indication Handling
approved
29.281 · CR 0041
Path failure handling
postponed
29.281 · CR 0042
Addition of the MBMS reference points
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.