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 WIs100

Rel-17 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.

5GProtoc17Rel-17 · connected · 100%

3GPP ↗

5GSATRel-17 · connected · 100%

3GPP ↗

5GSAT_ARCHRel-17 · connected · 100%

Historical association · verification pending3GPP ↗

5G_AISRel-17 · connected · 100%

3GPP ↗

5G_ProSeRel-17 · connected · 100%

3GPP ↗

5MBSRel-17 · connected · 100%

Historical association · verification pending3GPP ↗

5MBS_eMCRel-17 · connected · 100%

3GPP ↗

ARCH_NR_REDCAPRel-17 · connected · 100%

3GPP ↗

ATSSS_Ph2Rel-17 · connected · 100%

Historical association · verification pending3GPP ↗

AVPRODRel-17 · connected · 100%

3GPP ↗

EAVRel-17 · connected · 100%

3GPP ↗

EDGEAPPRel-17 · connected · 100%

Historical association · verification pending3GPP ↗

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

CR activity across mapped specs

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

22.261 · CR 0365 rev.1

Introduction of Minimization of Service Interruption (MINT)

revised

22.261 · CR 0365 rev.2

Introduction of Minimization of Service Interruption (MINT)

approved

22.261 · CR 0370

CR0XXX to to 22.261 on access control for MINT

withdrawn

22.261 · CR 0371 rev.1

Addition of security requirements for critical medical applications

approved

22.261 · CR 0372 rev.1

Addition of medical telemetry requirements

approved

22.261 · CR 0374

General descriptions of network controlled interactive service

revised

22.261 · CR 0374 rev.1

General descriptions of network controlled interactive service

merged

22.261 · CR 0375

Performance requirements of interactive service

revised

22.261 · CR 0375 rev.1

Performance requirements of interactive service

revised

22.261 · CR 0375 rev.3

Performance requirements of interactive service

approved

22.261 · CR 0376

Group operation related requirements of interactive service

revised

22.261 · CR 0376 rev.1

Group operation related requirements of interactive service

revised

22.261 · CR 0376 rev.2

Group operation related requirements of interactive service

noted

22.261 · CR 0378 rev.1

CR to 22.261 on access control for MINT

revised

22.261 · CR 0378 rev.2

CR to 22.261 on access control for MINT

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 →