MDF

MBMS (Download & Streaming) Delivery Function

Core Network →
Introduced in Rel-14 Also in: Core Network

MDF is the core network function in eMBMS responsible for the delivery, session management, and synchronization of broadcast or multicast content from providers to the radio access network.

Category
Core Network
Introduced
Rel-14
Where
Services › Codecs
Also touches
1 segments
Specifications
5 specs
MDF Description Purpose Related Classification Detected Changes Specifications

Description

The MBMS Delivery Function (MDF) is a pivotal logical entity within the 3GPP Evolved Packet Core (EPC) and 5G Core network, specifically for the evolved Multimedia Broadcast Multicast Service (eMBMS). It acts as the central coordination point between the broadcast/multicast content source (e.g., a Broadcast-Multicast Service Center - BM-SC) and the radio access network (E-UTRAN or NG-RAN). The MDF's primary role is to manage the delivery of MBMS user data, which can be either file delivery (download) via File Delivery over Unidirectional Transport (FLUTE) or real-time streaming via RTP, to multiple UEs simultaneously.

Architecturally, the MDF is often co-located with or is a functional part of the BM-SC, as defined in specifications like TS 26.956 and TS 33.126. For MBMS download, the MDF receives files or file carousels from content providers. It then orchestrates the delivery session, which includes scheduling the transmission, applying forward error correction (FEC) encoding as per TS 26.346, and encapsulating the data into IP multicast packets. It interfaces with the MBMS Gateway (MBMS-GW) using protocols like Diameter for session control and IP multicast for user plane data distribution. A critical technical function of the MDF in streaming scenarios is to generate and distribute synchronization information, such as M1 timing references and Synchronization Protocol (SYNC) packets, to ensure all eNodeBs/gNBs in a Multimedia Broadcast Single Frequency Network (MBSFN) area transmit the same content at precisely the same time, enabling coherent macro-diversity combining at the UE.

For security, as outlined in TS 33.126-128, the MDF plays a key role in the MBMS Service Protection system. It can interface with a Key Management Function (KMF) to obtain traffic encryption keys (TEKs) and then securely distribute the associated key material (like MIKEY or MSK) to authorized UEs via the BM-SC's service announcement and key distribution procedures. This ensures that only subscribed users can decrypt the broadcast content. The MDF's management capabilities also include monitoring session status, handling error reports, and supporting service continuity for mobile users moving between broadcast and unicast delivery areas.

Purpose & Motivation

The MDF was introduced to centralize and standardize the complex delivery mechanisms required for efficient point-to-multipoint content distribution in cellular networks. Prior to eMBMS enhancements, broadcast services often relied on separate, non-integrated systems. The MDF's creation, particularly highlighted from Release 14 with enhancements for LTE-based 5G broadcast, was motivated by the growing demand for scalable multimedia services like live TV, software updates, and public warnings that could strain unicast networks.

It solves the fundamental problem of efficiently delivering identical content to a massive number of users without congesting the core and radio networks with redundant unicast streams. By managing the content delivery as a broadcast/multicast session, the MDF enables network resources to be shared, dramatically improving spectral efficiency. Its synchronization capabilities are specifically designed to enable MBSFN operation, which turns interference from multiple cell transmissions into a constructive signal, improving coverage and reliability at cell edges—a critical requirement for broadcast services.

Furthermore, the MDF addresses the need for a unified framework that supports both download (for carousel-based services like firmware updates) and streaming (for live events). Its integration with the MBMS security architecture provides a standardized method for content protection and service monetization through subscription. The evolution of the MDF through releases reflects the drive to support new use cases like ATSC 3.0 convergence, enhanced TV services, and V2X group communications, making it a cornerstone for network-based broadcast and multicast in the 5G era.

Classification

Part ofBM-SC
Related approachesMBSFN

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-17 2 changes

In Release 17, the specification for the MBMS Delivery Function (MDF) was updated to provide clarifications on its default operational behavior. These clarifications specifically address the default handling for the **ServiceScoping** procedure and the default behavior for the **Location Type** parameter at the MDF.

  • Clarification to default behaviour for ServiceScoping at the MDF TS 33.128CR0263
  • Clarification to default behaviour for Location Type at the MDF TS 33.128CR0269
Rel-19 3 changes

In Release 19, the MBMS Delivery Function (MDF) was enhanced through a refactoring of its provisioning tables and associated X1 interface extensions. It also introduced clarifications to the service scoping language used at the MDF and enabled IRI (Information Repository and Index) generation for both AMF and MME based on this service scoping.

  • Refactoring of MDF provisioning tables and X1 Extensions TS 33.128CR0747
  • Service Scoping language clarifications for service scoping at the MDF TS 33.128CR0761
  • IRI generation in the MDF for AMF and MME based on service scoping TS 33.128CR0739

Explore further

Broader topics and technologies where MDF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 26.956 vj01 Beyond 2D Video Formats & Codecs Study Rel-19
TR 26.981 vj00 MBMS Provisioning & Content Ingestion Interface Study Rel-19
TS 33.126 vj30 Lawful Interception Requirements Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions Rel-19
TS 33.128 vj50 3GPP TS 33.128: Lawful Interception Protocols Rel-19
Patrick Zandl

About the author: Patrick Zandl (b. 1974)

Telecommunications specialist, technology journalist (founder of the Mobil server), and developer who has been running since 2025 — the largest Czech-language resource on AI-assisted programming. Formerly Chief Wizard Architect at Prusa3D and head of development for Turris at CZ.NIC; currently a consultant and instructor on AI implementation in companies.