curatedreviewedreviewed mapping begins in Rel-18

Feature lineage · XR / Immersive Media

Extended-reality service requirements, media and QoS context.

Reviewed topic evidence ↗Topic explorer →Ask Atlas →

Mapped specs4

Explicit stage labels0

Inferred orientations4

Relationships2

Connected WIs87

Rel-16 CR context50

Layer 1

Requirements / Stage 1 orientation

1 spec

TS 22.261

Service requirements for the 5G system

S1 · Rel-15

inferredOrientation inferred from the 22-series; this is not an official 3GPP stage assignment.

Layer 2

System architecture & procedures / Stage 2 orientation

2 specs

TS 23.501

System architecture for the 5G System (5GS)

S2 · Rel-15

inferredOrientation 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-15

inferredOrientation inferred from the 23-series; this is not an official 3GPP stage assignment.

Layer 3

Media

1 spec

TS 26.114

IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction

S4 · Rel-7

inferredOrientation 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%

3GPP source ↗Official Work Plan snapshot ↗

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.

5GLANRel-16 · connected · 100%

5GS_S6b_OptionalRel-16 · connected · 100%

5GVSCRel-16 · connected · 100%

5G_CIoTRel-16 · connected · 100%

Historical association · verification pending3GPP ↗

5G_MEDIA_MTSI_extRel-16 · connected · 100%

5G_URLLCRel-16 · connected · 100%

5G_eLCSRel-16 · connected · 100%

Historical association · verification pending3GPP ↗

5G_eSBARel-16 · connected · 100%

Historical association · verification pending3GPP ↗

5WWCRel-16 · connected · 100%

Historical association · verification pending3GPP ↗

ATSSSRel-16 · connected · 100%

Historical association · verification pending3GPP ↗

Alt_FX_EVSRel-16 · connected · 100%

CHEMRel-16 · connected · 100%

Cross-spec traceability

Release-valid relationships

23.503policy for23.501

curatedreviewed

23.501stage realization of22.261

curatedreviewedevidence ↗

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-16 context

CR activity across mapped specs

Context only: these CRs target mapped specifications in Rel-16; they are not automatically attributed to the feature.

22.261 · CR 0032 rev.2

Requirement for audio video sync timing for audio-visual interaction.

approved

22.261 · CR 0057

Selective Legacy Radio Disabling

noted

22.261 · CR 0059

Inclusion of unified access control requirements

noted

22.261 · CR 0061

Missing mobility requirements between 5G RAN and 2G/3G

revised

22.261 · CR 0061 rev.1

Missing mobility requirements between 5G RAN and 2G/3G

revised

22.261 · CR 0061 rev.2

Missing mobility requirements between 5G RAN and 2G/3G

noted

22.261 · CR 0068

Provide a more realistic KPI value for Virtual Reality

revised

22.261 · CR 0068 rev.1

Provide a more realistic KPI value for Virtual Reality

approved

22.261 · CR 0072

Clarification of delay tolerant UEs in UAC

revised

22.261 · CR 0072 rev.1

Clarification of delay tolerant UEs in UAC

withdrawn

22.261 · CR 0074

Charging for indirect network connection

noted

22.261 · CR 0075

Support of Voice Service Continuity from 5G system to UTRAN CS

revised

22.261 · CR 0075 rev.1

Support of Voice Service Continuity from 5G system to UTRAN CS

revised

22.261 · CR 0075 rev.2

Support of Voice Service Continuity from 5G system to UTRAN CS

revised

22.261 · CR 0075 rev.3

Support of Voice Service Continuity from 5G system to UTRAN CS

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.

Lineage JSON ↗Change Radar →