MF

Mediation Function

Management →
Introduced in Rel-4 Also in: Core Network, User Equipment, Testing, Security

MF is a core TMN component that acts as an intermediary to collect, process, and forward performance and charging data from Network Elements to OSS systems, standardizing formats for interoperability.

Category
Management
Introduced
Rel-4
Where
Services › Codecs
Also touches
4 segments
Specifications
23 specs
MF Description Purpose Related Classification Detected Changes Specifications

Description

The Mediation Function (MF) is a fundamental architectural element within the 3GPP Telecommunication Management Network (TMN) framework, defined across numerous specifications including the 32-series for management. It resides in the mediation layer of the TMN logical hierarchy, sitting between the Network Element (NE) layer and the Network Management (NM) or Service Management layers. Its primary role is to act as a data broker and processor for management information, specifically focusing on performance management (PM) data and charging data records (CDRs). The MF collects raw data from heterogeneous network elements—such as base stations, MSCs, SGSNs, and MMEs—which may use different proprietary protocols and data formats.

Operationally, the MF performs several key transformations. First, it performs protocol adaptation, converting data from vendor-specific element management protocols (like SNMP variants or proprietary interfaces) into standardized protocols used by upper-layer OSS systems, such as CORBA, FTP, or more recently, web services. Second, it performs data mediation, which includes filtering, aggregation, correlation, and formatting. For performance data, this might involve calculating 15-minute or hourly averages from counter snapshots, or correlating data from multiple NEs to create a service-level view. For charging data, it collects CDRs from switching elements, performs validation, and assembles them into formatted files for transfer to the Billing System. A critical function is the standardization of data according to 3GPP-defined information models, ensuring that the OSS receives consistent and interpretable information regardless of the underlying equipment vendor.

The MF is a key enabler for multi-vendor network environments. By insulating OSS applications from the complexities and variations of individual network elements, it reduces integration costs and simplifies network operations. Architecturally, it can be implemented as a standalone physical node, a virtualized function, or integrated within an Element Management System (EMS). Its deployment is crucial for scalable network management, as it offloads data processing tasks from both the resource-constrained NEs and the business-focused OSS. In modern networks, the principles of the MF are embodied in data collection and mediation platforms that handle vast streams of data from 4G and 5G network functions, often in near-real-time, to support advanced analytics, automated assurance, and billing.

Purpose & Motivation

The Mediation Function was conceived to address a fundamental challenge in telecom network management: the heterogeneity of network equipment. In early digital networks, each vendor's equipment came with its own management interface, data models, and protocols. This created immense complexity for network operators who deployed multi-vendor networks, as their central Operations Support Systems (OSS) needed custom adapters for every type of network element. This was costly, slow to integrate, and hindered unified network oversight and automated processes.

The MF, as part of the standardized TMN architecture, was created to solve this interoperability problem. It introduces a clear separation of concerns by placing a normalization layer between the network and management layers. Its purpose is to absorb the variability of the network element layer and present a uniform, standardized interface to the OSS. This solves the problems of high integration costs, long deployment cycles for new network elements, and the inability to get a consolidated, vendor-agnostic view of network performance and usage. Historically, it was essential for the rollout of performance management and billing systems that could operate across GSM, UMTS, and later generations. It motivated the creation of standardized information models (like those in the 32.3xx series) and file formats (like the Performance Measurement (PM) file format in 32.432), which the MF implements, thereby future-proofing OSS investments.

Classification

Part ofTMN
Related approachesOSS

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-4, normative work from Rel-18.

Rel-18 3 changes

In Release 18, the primary update to the Mediation Function (MF) was a significant rebranding and terminology consolidation, changing its abbreviation from "DCMF" to simply "MF". This change was consistently applied across the specification's text and all associated figures. Furthermore, specific service operations related to MF Media Resource Management received updates to reflect this new naming convention.

  • Updates to MF Media Resource Management Service Operations TS 29.176CR0016
  • Change of the abbreviation DCMF to MF and related changes to the text and figures TS 33.328CR0073
  • Replacing DCMF with MF TS 33.328CR0079

Explore further

Broader topics and technologies where MF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 21.111 vj00 USIM and UICC Requirements for 3G Rel-19
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19
TS 23.700 vk00 XR Services Application Enablement Layer Rel-20
TS 24.186 vj60 IMS Data Channel applications Rel-19
TS 24.229 vj50 IMS call control protocol based on SIP and SDP Rel-19
TS 26.264 vj20 IMS-based AR Real-Time Communication Rel-19
TS 26.567 vj00 IMS-based Split Rendering Rel-19
TR 26.927 vj00 AI/ML in 5G Media Services Study Rel-19
TR 26.930 vj00 WebRTC Enhancements for Immersive RTC over 5G Rel-19
TS 29.175 vj40 IMS AS Service-Based Interface Protocol Rel-19
TS 29.176 vj40 Nmf Service Based Interface for Media Function Rel-19
TS 31.102 vj40 USIM Application Specification Rel-19
TS 31.103 vj00 ISIM Application Specification Rel-19
TS 31.121 vi50 UICC-terminal interface test specification Rel-18
TS 32.276 vj00 VCS Online Charging from Proxy Function Rel-19
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19
TS 33.108 vj00 LI Handover Interface Specification Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 33.328 vj10 IMS Media Plane Security Specification Rel-19
TS 33.790 vj10 Security for Next-Gen Real-Time Communication Phase 2 Rel-19
TS 34.229 vj21 IMS SIP/SDP UE Conformance Testing for 5GS Rel-19
TR 38.812 vg00 Study on NOMA for NR Rel-16