No indexed CRs are linked to the primary Work Item at or before this release.
Rel-13 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-13; they are not automatically attributed to the feature.
29.281 · CR 0073
GTP-U initial and triggered message types
status unknown
29.281 · CR 0070
Sending multiple G-PDUs within a single UDP datagram
postponed
29.281 · CR 0070 rev.1
Sending multiple G-PDUs within a single UDP datagram
withdrawn
29.281 · CR 0071
Tunnelling scenarios for supporting High Latency communication
revised
29.281 · CR 0071 rev.1
Tunnelling scenarios for supporting High Latency communication
revised
29.281 · CR 0071 rev.2
Tunnelling scenarios for supporting High Latency communication
approved
29.281 · CR 0072
G-PDU extension header handling
revised
29.281 · CR 0072 rev.1
G-PDU extension header handling
revised
29.281 · CR 0072 rev.2
G-PDU extension header handling
revised
29.281 · CR 0072 rev.3
G-PDU extension header handling
approved
29.281 · CR 0074
S11-U tunneling for MO/MT data transport in control plane (SGi based)
revised
29.281 · CR 0074 rev.1
S11-U tunneling for MO/MT data transport in control plane (SGi based)
agreed
29.281 · CR 0075
End Marker handling by MME
revised
29.281 · CR 0075 rev.1
End Marker handling by MME
agreed
29.281 · CR 0076
Comprehension requirement for PDCP PDU Number
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.