Description
The Performance Measurement Function (PMF) is a core component within the 3GPP management architecture, specifically defined within the context of the 5G Core Network and its service-based interfaces. It operates as a producer of performance measurement data, collecting raw metrics from network functions (NFs) such as the Access and Mobility Management Function (AMF), Session Management Function (SMF), and User Plane Function (UPF). The PMF processes this data, which can include counters for successful procedures, failure rates, latency measurements, and resource utilization, transforming it into structured performance reports. These reports are then made available to consumer functions, primarily the Network Data Analytics Function (NWDAF) or external Operations, Administration, and Maintenance (OAM) systems, via standardized service-based interfaces like Npmf.
Architecturally, the PMF is defined to support both immediate and aggregated reporting. For immediate reporting, it can provide near-real-time performance data upon request. For aggregated reporting, it collects data over defined measurement periods and generates consolidated reports. The function handles measurement jobs, which are configurations specifying what to measure, from which NF, and the reporting format. It ensures data consistency and alignment with 3GPP-specified measurement types and formats, enabling standardized analytics across multi-vendor networks.
Its role is integral to closed-loop automation and network intelligence. By providing a centralized, standardized mechanism for performance data collection, the PMF feeds the analytics engines that drive network optimization, predictive maintenance, and dynamic resource allocation. It abstracts the complexity of raw data collection from individual NFs, offering a unified service for performance management. This supports key 5G goals like network slicing, where per-slice performance monitoring is essential for Service Level Agreement (SLA) assurance.
Purpose & Motivation
The PMF was introduced to address the challenges of performance management in the 5G service-based architecture (SBA). Previous generations relied on more rigid, element-manager-centric approaches where performance data collection was often vendor-specific and tightly coupled to network elements. This made centralized, cross-domain analytics and automation difficult. The 5G SBA, with its decoupled, cloud-native functions, required a new paradigm for observability.
The primary motivation was to create a standardized, scalable, and flexible function dedicated to performance data exposure. This enables network analytics and OAM systems to consume performance data in a consistent way, regardless of the underlying NF vendor. It solves the problem of data silos and heterogeneous collection methods, which were barriers to implementing advanced, AI-driven network automation and assurance for complex 5G use cases like network slicing and ultra-reliable low-latency communication (URLLC).
By defining the PMF, 3GPP provided a foundational enabler for the Management Data Analytics Service (MDAS) and the NWDAF ecosystem. It allows the network to self-monitor and self-optimize based on actual performance data, moving from reactive to proactive and predictive network management. This is critical for meeting the diverse and stringent performance requirements of 5G services.
Classification
Release Timeline
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (7 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the Performance Measurement Function (PMF) was enhanced to introduce specific UDP port types for Multi-Path TCP (MPTCP) Proxy interactions and to allow the network to control the enabling or disabling of Round-Trip Time (RTT) measurements via PMF control information. The specification formalized the PMF protocol (PMFP) procedures, defining message transport over UDP for IP-type PDU sessions and over Ethernet frames for Ethernet-type PDU sessions, including distinct port and address assignments for 3GPP and non-3GPP access. Furthermore, it introduced the capability for a UE to indicate support for "access performance measurements per QoS flow" for non-default QoS rules.
In Release 17, the Performance Measurement Function (PMF) was enhanced to support measurements per individual QoS flow, not just for the entire PDU session. This required new procedures for handling PMF messages with specific source and destination addresses and ports depending on the access network (3GPP or non-3GPP) and the target QoS flow. Furthermore, the UPF's behavior for setting the source and destination addresses in PMF protocol messages was explicitly defined to ensure accurate end-to-end performance measurement across multi-access connections.
In Release 19, the Performance Measurement Function (PMF) was enhanced to introduce new measurements specifically for ATSSS (Access Traffic Steering, Switching and Splitting). These additions included a PMF-related measurement for ATSSS and a new capability for the network-initiated Packet Loss Rate (PLR) measurement over ATSSS connections.
Explore further
Broader topics and technologies where PMF plays a role.
Defining Specifications
3GPP specifications that define or reference PMF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TS 24.193 vj50 | ATSSS Procedures Specification | Rel-19 |
| TS 24.501 vj50 | 5G NAS Protocols Specification | Rel-19 |
| TS 28.552 vk10 | 5G Performance Management Measurements | Rel-20 |
| TS 29.244 vj40 | PFCP Specification for Control/User Plane Separation | Rel-19 |