Layer 1
Requirements / Stage 1 orientation
TS 22.261
Service requirements for the 5G system
S1 · Rel-15inferredOrientation inferred from the 22-series; this is not an official 3GPP stage assignment.
curatedreviewedreviewed mapping begins in Rel-18
Feature lineage · XR / Immersive Media
Extended-reality service requirements, media and QoS context.
Mapped specs4
Explicit stage labels0
Inferred orientations4
Relationships1
Connected WIs28
Rel-12 CR context50
1 spec
Layer 2
System architecture & procedures / Stage 2 orientation
TS 23.501
System architecture for the 5G System (5GS)
S2 · Rel-15inferredOrientation inferred from the 23-series; this is not an official 3GPP stage assignment.
TS 23.503
Policy and charging control framework for the 5G System (5GS); Stage 2
S2 · Rel-15inferredOrientation inferred from the 23-series; this is not an official 3GPP stage assignment.
Layer 3
Media
TS 26.114
IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction
S4 · Rel-7inferredOrientation inferred from the 26-series; this is not an official 3GPP stage assignment.
Primary feature evidence
Topic source Work Item
XRM
Architecture Enhancements for XR (Extended Reality) and media service
Rel-18 · PCG approved · WG not indexed · Work Plan 100%Connected work
Work Items touching mapped specs
These Work Items share one or more mapped specifications. Atlas does not automatically claim that every connected Work Item defines this feature.
CVORel-12 · connected · 100%
3GPP ↗CVO-SA4Rel-12 · connected · 100%
3GPP ↗E2EMTSIRel-12 · connected · 100%
3GPP ↗EVS_codecRel-12 · connected · 100%
3GPP ↗EVS_codec-SA4Rel-12 · connected · 100%
3GPP ↗HEVCRel-12 · connected · 100%
3GPP ↗HEVC-SA4Rel-12 · connected · 100%
3GPP ↗HEVC-SA4IETFRel-12 · connected · 100%
3GPP ↗M3DV_ExtRel-12 · connected · 100%
3GPP ↗ProSe-SA1Rel-12 · connected · 100%
3GPP ↗TEI12Rel-12 · connected · 100%
3GPP ↗VTRIRel-12 · connected · 100%
3GPP ↗Cross-spec traceability
Release-valid relationships
23.503policy for23.501curatedreviewed
Primary WI evolution
Change Requests linked to the primary Work Item
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.
26.114 · CR 0237
Camera and Flip bits semantic clarifications
revised26.114 · CR 0237 rev.1
On Coordination of Video Orientation
revised26.114 · CR 0237 rev.2
On Coordination of Video Orientation
approved26.114 · CR 0238
Negotiation of AVPF and CCM feedback messages for video
revised26.114 · CR 0238 rev.1
Negotiation of AVPF and CCM feedback messages for video
approved26.114 · CR 0240
Session setup for asymmetric video
revised26.114 · CR 0240 rev.1
Session setup for asymmetric video
revised26.114 · CR 0240 rev.2
Session setup for asymmetric video
approved26.114 · CR 0241
Non-CVO operation
revised26.114 · CR 0241 rev.1
Non-CVO operation
revised26.114 · CR 0241 rev.2
Non-CVO operation
approved26.114 · CR 0242
Clarification of DTMF handling
withdrawn26.114 · CR 0243
Enabling Higher Granularity Rotation in CVO
revised26.114 · CR 0243 rev.1
Enabling Higher Granularity Rotation in CVO
revised26.114 · CR 0243 rev.2
Enabling Higher Granularity Rotation in CVO
revisedTraceability 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.