Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Services

QMC

QoE Measurement Collection

Services →

QMC is a framework for collecting Quality of Experience measurements from user equipment to gather data on user-perceived service quality for network optimization and service assurance.

Introduced
Rel-14
Where
Radio Access Network › NG-RAN (5G)
Specifications
20 specs
Also in
Services, Management, Core Network
QMC Description Purpose What changed Neighbours Detected Changes Specifications

Description

QoE Measurement Collection (QMC) is a standardized framework within 3GPP for the collection of Quality of Experience (QoE) metrics from end-user devices. QoE differs from traditional Quality of Service (QoS) by focusing on the subjective perception of a service by the end-user, such as video quality, audio clarity, or application responsiveness. The QMC framework defines the procedures, signaling, and information models necessary for the network to configure, activate, and receive QoE measurements from the User Equipment (UE). It operates across multiple service types, with a primary focus on media streaming services like HTTP Adaptive Streaming (HAS).

The architecture involves several network functions. The Policy Control Function (PCF) or Application Function (AF) can request QoE measurements for specific users or services. This request is communicated to the UE via the Access and Mobility Management Function (AMF) and the Radio Access Network (RAN). The UE, equipped with a QoE measurement client, then performs the measurements according to the received configuration. This configuration includes parameters like the service type (e.g., video streaming), target metrics (e.g., initial playback delay, rebuffering ratio, video codec information), and reporting triggers (e.g., periodic, event-based).

The UE collects data during the service session. For video streaming, this can include application-layer metrics like buffer status, resolution changes, and stall events. Once collected, the measurement reports are sent back to a designated collection entity, often a Mediation Function (MF) or directly to an Application Function (AF) like a video analytics server. The reports are transported over standardized interfaces, such as Nq between the UE and the AMF, and potentially Nm between the AMF and the MF. The collected data is then aggregated and analyzed by the operator or service provider to gain insights into real-world service performance, identify problem areas, and drive network and service improvements.

Purpose & Motivation

QMC was introduced to address the growing need for operators and service providers to understand the actual end-user experience, which is not fully captured by traditional network-centric QoS metrics. As services like video streaming became dominant, issues like video stalling, resolution degradation, and slow start-up times directly impacted user satisfaction and retention. Prior to QMC, operators relied on network probes, deep packet inspection (DPI), or limited, proprietary device reporting, which provided an incomplete or indirect view of QoE.

The creation of QMC was motivated by the industry's shift towards user-centric network management. It solves the problem of obtaining direct, standardized, and rich QoE data from the endpoint itself—the UE. This enables correlation of network conditions (e.g., radio signal strength, throughput) with actual application performance as perceived by the user. By standardizing this collection framework in Rel-14 and beyond, 3GPP ensured interoperability between devices and network analytics platforms, allowing for scalable, automated QoE-driven optimization and closed-loop operations.

What changed in its specifications

The latest release-to-release comparison of specifications that define QMC. Each summary describes the whole specification, not only this term.

TS 23.501Rel-18 → Rel-19

Rel-19 added MPQUIC steering to multi-access PDU sessions, XR and media handling, and an Energy Information Function. It also added Local Offloading Management for edge computing, Vertical Federated Learning for AI/ML, and Ambient IoT text.

Full comparison in TS 23.501 →
TS 26.114Rel-18 → Rel-19

Rel-19 adds a reference to the IVAS fixed-point C code specification in TS 26.114. It also lists that specification among supported specifications for MTSI immersive audio clients.

Full comparison in TS 26.114 →

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

Specific changes extracted from the „Change history“ tables of 3GPP specifications (21 CRs across 4 releases). Complements the general historical overview above with the evidence-based evolution of this function.

Rel-15 4 changes
  • Introduction of QoE Measurement Collection for LTE TS 36.413CR1543
  • Introduction of QoE Measurement Collection for LTE TS 36.423CR1045
  • Introduction of QMC for MTSI in EUTRAN TS 36.413CR1572
  • Introduction of QMC for MTSI in EUTRAN TS 36.423CR1086
Rel-16 2 changes
Rel-17 4 changes
  • BLCR to 38.410: Support of QoE Measurement Collection for NR TS 38.410CR0034
  • BLCR to 38.420: Support of QoE Measurement Collection for NR TS 38.420CR0026
  • Align Requirements of handling QMC during RAN overload to RAN specifications TS 28.405CR0012
  • Correction on the QoE Area Scope IE in QMC Configuration Information TS 38.413CR1001
Rel-18 11 changes
  • Handling of QoE measurement collection at handover in NR TS 28.405CR0015
  • Add MDT alignment Information and RAN visible QoE Metrics to Handling QMC at Handover TS 28.405CR0019
  • QMC enhancements for NR-DC TS 38.420CR0038
  • QMC support for application session delivered via the MBS TS 26.247CR0189
  • Correction to MBS communication service type for QMC TS 26.247CR0192
  • Rel-18 CR TS 28.405 revision of S5-242206 with the updated procedure for QMC activation TS 28.405CR0033

+ 5 more changes

Defining Specifications

3GPP specifications that define or reference QMC, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 23.501 vk30 5G System Architecture Rel-20 read
TS 26.114 vk11 IMS Multimedia Telephony Client Rel-20 read
TS 26.247 vj10 Transparent End-to-End Packet-switched Streaming Rel-19 read
TS 26.567 vj20 IMS-Based Split Rendering Rel-19 read
TR 26.812 vi10 Technical Report Rel-18 read
TS 26.942 vk00 Sustainable Media Metrics and Architectural Impacts for 5G Rel-20 read
TS 28.308 vj00 QoE Measurement Collection IRP: Information Service Rel-19 read
TS 28.405 vj40 QoE Measurement Control & Configuration Rel-19 read
TS 28.406 vj00 QoE measurement collection: info definition & transport Rel-19 read
TS 32.101 vj00 PLMN Management Principles and Requirements Rel-19 read
TS 36.413 vj20 S1 Application Protocol (S1AP) for E-UTRAN Rel-19 read
TS 36.423 vj10 X2 Application Protocol (X2AP) Specification Rel-19 read
TS 37.340 vj30 Overview of Multi-Connectivity Operation using E-UTRA and NR Rel-19 read
TS 38.300 vj40 NR and NG-RAN Overall Description Rel-19 read
TS 38.410 vj20 NG-RAN; NG General Aspects and Principles Rel-19 read
TS 38.413 vj40 NG Application Protocol (NGAP) Specification Rel-19 read
TS 38.420 vj10 Introduction to Xn interface specifications Rel-19 read
TS 38.470 vj20 F1 Interface Specification for NG-RAN Rel-19 read
TS 38.473 vj40 F1 Application Protocol (F1AP) Rel-19 read
TR 38.890 vh00 NR QoE Management and Optimization Rel-17 read