No indexed CRs are linked to the primary Work Item at or before this release.
Rel-12 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-12; they are not automatically attributed to the feature.
29.281 · CR 0064
Introduction of Dual Connectivity Function
revised
29.281 · CR 0064 rev.1
Introduction of Dual Connectivity Function
revised
29.281 · CR 0064 rev.2
Introduction of Dual Connectivity Function
approved
29.281 · CR 0065
Correct the ambiguous GTP-U PDU
approved
29.281 · CR 0066
RAN Container GTP-U extension header
withdrawn
29.281 · CR 0067
Definition of RAN Container for flow control during X2UP handover
revised
29.281 · CR 0067 rev.1
Definition of RAN Container for flow control during X2UP handover
approved
29.281 · CR 0068
End Marker used in PMIP-based S5/S8 case
revised
29.281 · CR 0068 rev.1
End Marker used in PMIP-based S5/S8 case
approved
29.281 · CR 0069
Correct the GSN Address IE name
revised
29.281 · CR 0069 rev.1
Correct the GSN Address IE name
revised
29.281 · CR 0069 rev.2
Correct the GSN Address IE name
approved
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.