Layer 1
Requirements / Stage 1 orientation
Service requirements for the 5G system
S1 · Rel-15Extended-reality service requirements, media and QoS context.
Layer 1
Service requirements for the 5G system
S1 · Rel-15Layer 2
System architecture for the 5G System (5GS)
S2 · Rel-15Policy and charging control framework for the 5G System (5GS); Stage 2
S2 · Rel-15Layer 3
IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction
S4 · Rel-7Primary feature evidence
Architecture Enhancements for XR (Extended Reality) and media service
Rel-18 · PCG approved · WG not indexed · Work Plan 100%Connected work
These Work Items share one or more mapped specifications. Atlas does not automatically claim that every connected Work Item defines this feature.
Cross-spec traceability
23.503policy for23.50123.501stage realization of22.261Primary WI evolution
Complete to the QoS flow binding and Miscellaneous Corrections
Rel-20 · approved3GPP CR ↗Correcting attribute name of the congestion threshold for uplink information
Rel-19 · approved3GPP CR ↗Corrections to the QosMonitoringReport data type
Rel-19 · approved3GPP CR ↗Correction to PDU set based handling
Rel-19 · approved3GPP CR ↗Corrections to the congestReports
Rel-19 · approved3GPP CR ↗Correction to the maximum number of reference to QosMonitoringData
Rel-19 · approved3GPP CR ↗Term defined for "IP PDU session type" and minor fixes in ECN marking for L4S indication IE
Rel-19 · approved3GPP CR ↗PDU Set Information Container
Rel-19 · approved3GPP CR ↗Support of MDBV and average window in AQP contained in the PCC rule
Rel-19 · approved3GPP CR ↗Update Alternative QoS Parameter Set
Rel-19 · approved3GPP CR ↗Corrections on the feature name
Rel-19 · approved3GPP CR ↗Update Alternative QoS Parameter Set
Rel-19 · approved3GPP CR ↗Corrections on MDBV and average window in AQP
Rel-19 · approved3GPP CR ↗Correction to End of Data Burst marking
Rel-19 · approved3GPP CR ↗Update Alternative QoS Parameter Set
Rel-19 · approved3GPP CR ↗Rel-98 context
Context only: these CRs target mapped specifications in Rel-98; they are not automatically attributed to the feature.
No CR activity targeting the mapped specifications is indexed for Rel-98.
Traceability limits