Mediation Function

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.

Key Features

• Protocol adaptation between NE-specific interfaces and standardized OSS interfaces
• Data filtering, aggregation, and correlation for performance and charging data
• Format conversion to 3GPP-standardized PM file and CDR file formats
• Temporal aggregation (e.g., converting 5-minute counters to hourly reports)
• Buffering and reliable transfer of management data to upstream systems
• Support for multi-vendor network environments through normalization

Evolution Across Releases

Defining Specifications