CDN

Content Delivery Network / Content Distribution Network

Services →
Introduced in Rel-6 Also in: Radio Access Network

CDN is a distributed network of servers that delivers web content and media to users based on geographic proximity to reduce latency and improve quality of experience.

Category
Services
Introduced
Rel-6
Where
Services › Codecs
Also touches
1 segments
Specifications
24 specs
CDN Description Purpose Related Classification Detected Changes Specifications

Description

A Content Delivery Network (CDN) is a geographically distributed network of proxy servers and data centers designed to provide high availability and performance by delivering content to end-users from the most optimal location. In 3GPP architectures, CDNs are integrated to efficiently serve multimedia content, software updates, and web applications over mobile networks. The core principle involves caching content at edge servers located closer to the user, which minimizes the distance data must travel, reduces round-trip time, and alleviates congestion on the core network and origin servers.

Architecturally, a CDN consists of origin servers that host the original content, edge servers (or Points of Presence) deployed at strategic locations, a request routing system, and a content management system. The request routing mechanism, often using DNS-based or anycast routing, intelligently directs user requests to the nearest or least-loaded edge server. This process is transparent to the user and is based on real-time factors such as server load, network conditions, and geographic location. For dynamic content or content not cached, the edge server may fetch it from the origin server, often using optimization techniques like TCP acceleration and compression.

Within 3GPP standards, CDN integration is specified to support services like Multimedia Broadcast Multicast Service (MBMS), evolved Multimedia Broadcast Multicast Service (eMBMS), and later enhancements for 5G Media Streaming. Specifications define interfaces and procedures for CDN selection, traffic steering, and policy enforcement, ensuring seamless operation with mobile core network functions like the Policy and Charging Rules Function (PCRF) and User Plane Function (UPF). Key components include the CDN Proxy, which interfaces with the user equipment, and the CDN Controller, which manages content distribution policies and caching strategies.

The role of a CDN in a mobile network is critical for managing the explosive growth of data traffic, particularly video, which constitutes a majority of mobile data. By caching popular content at the network edge, CDNs reduce the load on the radio access network (RAN) and core transport links, enabling more efficient use of network resources. They also enhance quality of experience (QoE) by providing lower latency, higher throughput, and reduced packet loss, which is essential for real-time applications like live streaming, video on demand (VoD), and online gaming. Advanced features include support for adaptive bitrate streaming (e.g., DASH, HLS), content prefetching based on user behavior prediction, and integration with network slicing for dedicated service delivery.

Purpose & Motivation

The primary purpose of a CDN in 3GPP networks is to address the challenges posed by the rapid increase in mobile data consumption, especially bandwidth-intensive multimedia content. Prior to CDN integration, all user requests for content were served directly from centralized origin servers, leading to high latency, network congestion, and poor user experience, particularly for users far from the server location. This approach was unsustainable as video streaming and large file downloads became dominant traffic types, straining network infrastructure and increasing operational costs for mobile operators.

CDNs were introduced to solve these problems by decentralizing content delivery, bringing it closer to the end-user. This reduces the distance data travels over the network, minimizing latency and jitter, which are critical for real-time services. Additionally, CDNs offload traffic from the core network and origin servers, allowing them to handle more users and requests efficiently. This is especially important in mobile networks where radio resources are scarce and expensive; by caching content at the edge, CDNs reduce the amount of data that needs to be transmitted over the RAN, improving overall network capacity and performance.

Historically, CDNs emerged in the fixed internet ecosystem, but their integration into 3GPP standards began in Release 6 to support mobile-specific requirements like mobility management, network-aware optimization, and integration with mobile core functions. This evolution was motivated by the need to provide consistent high-quality experiences for mobile users, support new services like mobile TV and video streaming, and enable efficient content distribution for operators. CDNs also facilitate cost reduction by lowering transit and peering costs, improving scalability, and enabling new revenue streams through enhanced service offerings.

Classification

Related approachesMBMS

Detected Changes Across Releases

from 3GPP Change Requests

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

Studied in Rel-6, normative work from Rel-15.

Rel-15 1 change

In Release 15, specific enhancements were introduced for CDN functions related to mission critical services delivered over MBMS. The release defined support for applying Forward Error Correction (FEC) and Robust Header Compression (ROHC) techniques to improve the reliability and efficiency of content distribution. These capabilities were integrated to optimize the unidirectional distribution of content within the defined connectionless bearer service framework.

  • FEC and ROHC for mission critical services over MBMS TS 29.116CR0021
Rel-16 6 changes

In Release 16, the CDN function was enhanced to support UE group content delivery and introduced the capability for File Repair to be hosted directly by the content provider. The specifications were also refined by aligning the Stage 2 Content Hosting function of the 5GMSd Application Server to its Stage 3 definitions. Furthermore, the release clarified procedures for an SA file returned for the download delivery session and removed redundant annex content.

  • MBMS resource sharing TS 29.116CR0037
  • SA file returned for the download delivery session TS 29.116CR0038
  • File Repair hosted by the content provider TS 29.116CR0039
  • Aligning Stage 2 Content Hosting function of 5GMSd AS to Stage 3 TS 26.501CR0029
  • UE group content delivery TS 29.116CR0029
  • Remove redundant annex content TS 29.116CR0045
Rel-17 4 changes

In Release 17, enhancements for the CDN function included essential corrections for 5G Media Streaming content hosting and clarifications for managing shared delivery tunnels in common gNB UP scenarios. The release also provided specific clarifications on Packet Detection Rules and Forwarding Action Rules within the A-UPF for Multimedia Broadcast/Multicast Service data traffic in individual delivery. Furthermore, it introduced interworking with MBMS over E-UTRAN to support broadcast services.

  • Interworking with MBMS over E-UTRAN for broadcast service TS 23.247CR0008
  • clarification on PDR and FAR in A-UPF for MBS data traffic in individual delivery TS 23.247CR0068
  • Clarification on the shared delivery tunnel management for common gNB UP case TS 23.247CR0141
  • [5GMS, TEI17] Content hosting essential correction TS 26.512CR0053
Rel-18 13 changes

In Release 18, the enhancements for CDN-related functions focused on the introduction and refinement of **Group Message Delivery** procedures and the alignment of the media delivery architecture. Key updates included clarifying the role of the NEF and the involved interfaces for group message data delivery, as well as specifying the use of a **media delivery session identifier** across the M4, M7, and M11 reference points. Furthermore, corrections and clarifications were made to support the delivery of multicast MBS session data to RRC_INACTIVE UEs and to accommodate NR RedCap UEs within the group message delivery framework.

  • Group Message Delivery TS 23.247CR0143
  • On the Update of Group Message Delivery TS 23.247CR0163
  • KI#2, adding MOCN network sharing for the same content TS 23.247CR0176
  • Update group message delivery procedure TS 23.247CR0220
  • [5GMS_Pro_Ph2] Media delivery session identifier at M4+M7+M11 TS 26.512CR0066
  • Resolve ENs on Group Message Delivery and corrections TS 23.247CR0161

+ 7 more changes

Rel-19 6 changes

In Release 19, the CDN function was enhanced through the Advanced Media Delivery (AMD) work item, introducing new features for MBS User Services and 5G Media Streaming. The release specified updates to service location media delivery recommendations and made normative updates to the CMMF Content Preparation Template and Media Player Entry references. It also initiated a future study on multi-access media delivery, focusing on distribution services characterized by unidirectional information flow.

  • Advanced Media Delivery; Stage 2 features TS 26.501CR0108
  • [FS_AMD] Advanced Media Delivery Features for MBS User Services TS 26.802CR0005
  • [FS_AMD] Advanced Media Delivery Features for 5G Media Streaming TS 26.804CR0024
  • [FS_AMD] Update to multiple service location media delivery recommendations for stage 3 TS 26.804CR0027
  • [AMD_PRO-MED] Updates to normative CMMF Content Preparation Template and Media Player Entry references. TS 26.512CR0102
  • Aspects to look into during future study on topic of multi-access media delivery TS 26.804CR0026

Explore further

Broader topics and technologies where CDN plays a role.

Defining Specifications

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

SpecificationTitleRelease
TR 21.905 vj00 3GPP Technical Terms and Definitions Rel-19
TR 22.906 vj00 IMS P2P Content Distribution Services Rel-19
TS 23.247 vj30 5G Multicast/Broadcast Service Architecture Rel-19
TR 23.737 vh20 Satellite Access in 5G Architecture Study Rel-17
TS 23.844 vc00 IMS P2P Content Distribution Services Study Rel-12
TS 25.113 vj00 EMC Requirements for UTRA Base Stations & Repeaters Rel-19
TS 26.501 vj30 5G Media Streaming (5GMS) Architecture Rel-19
TS 26.512 vj10 5G Media Streaming Protocols & APIs Rel-19
TS 26.802 vj20 Multicast Enhancements for 5G Media Streaming Rel-19
TS 26.804 vj10 5G Media Streaming Extensions Study Rel-19
TS 26.849 vc10 MBMS Operation on Demand (MooD) Rel-12
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16
TR 26.904 vj00 Future video capability requirements for streaming and MBMS Rel-19
TR 26.926 vj00 Traffic Models & Quality Evaluation for Media/XR in 5G Rel-19
TR 26.928 vj00 Study on eXtended Reality (XR) in 5G Rel-19
TR 26.938 vj00 DASH Deployment Guidelines for 3GPP Networks Rel-19
TR 26.949 vj00 TV Service Profiles for 3GPP Networks Rel-19
TR 26.957 vj00 Evaluation of MPEG DASH SAND for 3GPP Rel-19
TS 29.116 vj00 REST-based protocol for xMB reference point Rel-19
TS 36.113 vj00 EMC Requirements for E-UTRA Base Stations Rel-19
TS 37.113 vj00 EMC Requirements for Multi-Standard Radio Base Stations Rel-19
TS 38.113 vj00 NR Base Station EMC Specification Rel-19
TS 38.114 vj00 EMC Requirements for NR Repeaters and NCR Rel-19
TS 38.175 vj00 EMC for NR IAB Nodes Rel-19