No indexed CRs are linked to the primary Work Item at or before this release.
Rel-8 context
CR activity across mapped specs
Context only: these CRs target mapped specifications in Rel-8; they are not automatically attributed to the feature.
26.114 · CR 0034 rev.1
Improvements to MTSI 3G324M interworking
approved
26.114 · CR 0037
MTSI QoE Configuration
withdrawn
26.114 · CR 0038
MTSI QoE Reporting
withdrawn
26.114 · CR 0039
MTSI QoE configuration and reporting
postponed
26.114 · CR 0039 rev.1
MTSI QoE configuration and reporting
revised
26.114 · CR 0039 rev.2
MTSI QoE configuration and reporting
approved
26.114 · CR 0041
Mode changes for MTSI MGWs
revised
26.114 · CR 0041 rev.1
Mode changes for MTSI MGWs
approved
26.114 · CR 0043
Negotiated GBR and AS bandwidths
revised
26.114 · CR 0043 rev.1
Negotiated GBR and AS bandwidths
approved
26.114 · CR 0045
Additional SDP examples for SDP offers
revised
26.114 · CR 0045 rev.1
Additional SDP examples for SDP answers
approved
26.114 · CR 0047
Initial codec mode
approved
26.114 · CR 0048
RTP/RTCP symmetric media stream
revised
26.114 · CR 0048 rev.1
RTP/RTCP symmetric media stream
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.