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

Glossary term · Management

MF

Mediation Function

Management →

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.

Introduced
Rel-4
Where
Services › Codecs
Specifications
23 specs
Also in
Core Network, Security, User Equipment, Testing
MF Description Purpose What changed Neighbours 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.

What changed in its specifications

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

TR 21.905Rel-17 → Rel-18

Rel-18 brings only minor changes to TS 21.905: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TR 21.905 →
TS 23.078Rel-18 → Rel-19

Rel-19 brings only minor changes to TS 23.078: 0 clauses changed, with no change attributed to a release feature.

Full comparison in TS 23.078 →

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-4 Initial

Introduced the Mediation Function as a core component within the enhanced 3GPP Telecommunication Management Network (TMN) architecture. Defined its initial role in collecting and processing performance measurement data from GSM and UMTS Network Elements, standardizing data formats for cross-domain management, and establishing it as the crucial intermediary between network equipment and operations support systems.

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 read
TR 21.905 vj20 3GPP Terminology and Definitions Rel-19 read
TS 23.078 vj00 CAMEL Phase 4 Stage 2 Specification Rel-19 read
TS 23.700 vk10 AI/ML Application Layer Support Phase 2 Rel-20 read
TS 24.186 vk10 IMS Data Channel and AR Communication Rel-20 read
TS 24.229 vk10 IMS SIP/SDP Call Control Protocol Rel-20 read
TS 26.264 vj41 IMS Conversational Augmented Reality Services Rel-19 read
TS 26.567 vj20 IMS-Based Split Rendering Rel-19 read
TR 26.927 vj00 AI/ML in 5G Media Services Study Rel-19 read
TR 26.930 vj00 WebRTC Enhancements for Immersive RTC over 5G Rel-19 read
TS 29.175 vk10 Nimsas Service Based Interface for IMS AS Rel-20 read
TS 29.176 vk10 Nmf Media Resource Management Service Rel-20 read
TS 31.102 vk00 USIM Application Specification Rel-20 read
TS 31.103 vj10 IM Services Identity Module Specification Rel-19 read
TS 31.121 vj00 UICC Application Test Specification Rel-19 read
TS 32.276 vj00 VCS Online Charging from Proxy Function Rel-19 read
TS 33.107 vj00 Lawful Interception Architecture & Functions Rel-19 read
TS 33.108 vj00 LI Handover Interface Specification Rel-19 read
TS 33.127 vj80 Lawful Interception Architecture Rel-19 read
TS 33.328 vk10 IMS Media Plane Security Rel-20 read
TS 33.790 vj10 Security for Next-Gen Real-Time Communication Phase 2 Rel-19 read
TS 34.229 vj30 IP Multimedia Call Control Protocol Rel-19 read
TR 38.812 vg00 Study on NOMA for NR Rel-16 read