5GMS

5G Media Streaming

Services →
Introduced in Rel-16 Also in: Core Network

5GMS is a 3GPP framework for delivering media streaming services over 5G networks, defining standardized interfaces and functions for content preparation, delivery, and consumption.

Category
Services
Introduced
Rel-16
Where
Services › Codecs
Also touches
1 segments
Specifications
13 specs
5GMS Description Purpose Related Classification Detected Changes Specifications

Description

5G Media Streaming (5GMS) is a comprehensive 3GPP service framework that standardizes the delivery of media content—including live, on-demand, and linear streaming—over 5G networks. Its architecture is built around two primary functional entities: the 5GMS Application Provider (5GMS-AP) and the 5GMS Application Function (5GMS-AF). The 5GMS-AP is responsible for media-centric operations like content preparation, packaging, and rights management, typically residing in the application layer. The 5GMS-AF, integrated within the 5G core network, acts as the service enabler, interfacing with the 5G system's Policy Control Function (PCF) and Network Exposure Function (NEF) to request and manage network resources (like QoS) tailored for media sessions. This separation allows content providers to focus on media logic while leveraging standardized network capabilities for delivery optimization.

The framework operates by defining a set of open APIs, primarily the M1, M2, M3, M4, and M5 interfaces. The M1 interface is used by the 5GMS-AF to provision media session policies to the PCF. The M2 interface allows the 5GMS-AF to request network assistance (e.g., traffic steering, QoS) from the NEF. The M3 interface is the northbound API exposed by the 5GMS-AF to the 5GMS-AP, enabling the application to request media-specific network services. The M4 interface is used for configuration and provisioning between management functions. The M5 interface handles media player control and events. This API-driven architecture ensures interoperability between different vendors' media applications and 5G network components.

Key components within the 5GMS ecosystem include the Media Session Handler, which manages the lifecycle of a media streaming session and its associated network resources; the Media Player, which is a compliant client application; and the Media Distribution Network, which can be a Content Delivery Network (CDN) or a multicast/broadcast service. A critical aspect is its support for both unicast (e.g., DASH, HLS) and broadcast/multicast (e.g., 5G Broadcast, 5G Multicast-Broadcast Services) delivery methods. The framework also defines procedures for dynamic adaptive streaming, where the client's Media Player can switch between different quality representations based on real-time network conditions, with potential network assistance for smoother transitions.

Its role in the network is to act as the standardized glue between over-the-top (OTT) media services and the underlying 5G system. It enables the 5G network to be 'media-aware,' allowing it to apply optimized policies for media traffic, such as guaranteed bitrate, low latency paths, or efficient multicast distribution for popular live events. This moves beyond simple best-effort internet delivery, providing a managed service quality that can be monetized. It also facilitates edge computing scenarios, where media processing or caching can be performed at the network edge (via the Edge-enabled 5GMS Application Server, or EAS) to reduce latency and backhaul load, crucial for applications like cloud gaming or ultra-high-definition VR streaming.

Purpose & Motivation

5GMS was created to address the lack of standardized, network-integrated media delivery mechanisms in previous mobile generations. Prior to 5G, media streaming over cellular networks was largely an OTT service running transparently over best-effort IP connectivity. This led to inefficiencies, inconsistent quality of experience (QoE), and an inability for network operators to optimize or monetize the massive volume of media traffic. The explosion of video traffic, coupled with the new capabilities of 5G (e.g., network slicing, edge computing, ultra-low latency), created a need for a framework that could unlock these capabilities specifically for media applications.

The primary problems it solves are media delivery fragmentation and suboptimal resource utilization. Without 5GMS, each media provider would need to develop proprietary integrations with different mobile operators to access advanced network features, creating complexity and hindering scale. 5GMS provides a common, standards-based 'mediator' that abstracts the network complexity. It solves the problem of inefficient delivery for popular content (like live sports) by standardizing the use of 5G multicast/broadcast, which transmits a single stream to many users simultaneously, conserving precious radio and core network resources compared to thousands of individual unicast streams.

Historically, the motivation stemmed from the desire to create a viable, standardized alternative to traditional broadcast TV (e.g., DVB) using cellular networks, while also enhancing unicast streaming. It addresses the limitations of previous approaches by moving from a passive, transparent pipe model to an active, collaborative model where the application and the network exchange information and requests. This allows for proactive quality management, seamless mobility support for streaming sessions, and the enablement of new immersive media formats that require stringent performance guarantees which only a managed 5G system can provide reliably.

Classification

Part ofQoS
Specific typesEFAPIDMSMHASVDP

Release Timeline

Detected Changes Across Releases

from 3GPP Change Requests

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

Rel-16 7 changes

In Release 16, the 5G Media Streaming (5GMS) function introduced specific TV Video Profiles and defined the 5GMS DASH Interoperability Point with parameters for video codecs, content format, and transport. The release also included architectural corrections and enhancements for unicast streaming procedures, QoE metrics reporting, consumption reporting, and session handling. Furthermore, it established protocols and addressed collaboration scenarios, while providing various corrections to codecs, formats, and the stage 3 specification.

  • Corrections to 5G Media Streaming TS 26.511CR0001
  • TV Video Profiles and 5G Media Streaming TS 26.116CR0014
  • Correction of Architecture, Unicast Streaming Procedure, QoE metrics reporting, Consumption reporting and Session Handling for 5GMS TS 26.501CR0002
  • Collaboration Scenarios for 5G Media Streaming TS 26.501CR0006
  • Various Corrections to 5GMS Codecs and Formats TS 26.511CR0002
  • Corrections to 5GMS stage 3 specification TS 26.512CR0011

+ 1 more changes

Rel-17 14 changes

In Release 17, the 5GMS (5G Media Streaming) function introduced significant new capabilities including support for Edge Media Processing and enhanced integration with eMBMS for broadcast delivery. It expanded its operational scope with new data collection and reporting features, refined downlink provisioning procedures, and added support for advanced use cases like 8K TV streaming. The release also included important corrections and API enhancements, particularly for the EAS Discovery and xMB interface extensions related to 5GMS via eMBMS.

  • CR on the Support of Edge Media Processing in 5GMS TS 26.501CR0030
  • 5GMS via eMBMS TS 26.501CR0034
  • [EVEX] Data collection and reporting for 5G Media Streaming TS 26.501CR0035
  • [EVEX] [5GMS_EDGE] Expanded downlink provisioning procedures and domain model TS 26.501CR0036
  • 8K TV in 5GMS TS 26.511CR0007
  • Support for Data Collection and Reporting for 5G Media Streaming TS 26.512CR0023

+ 8 more changes

Rel-18 45 changes

In Release 18, the 5G Media Streaming (5GMS) function introduced significant enhancements including support for 5GMS over 5G Multicast-Broadcast Services (5MBS) and hybrid services, along with new procedures for Application Server configuration via the M3 interface. It also added new capabilities for uplink remote control, event exposure APIs, and dynamic policies for Service URL handling. Furthermore, the release defined mechanisms for ANBR-based network assistance data reporting and specified the carriage of a media delivery session identifier across interfaces and within QoE reports.

  • [5GMS_Ph2] Feature description, dynamic policies and Service URL handling TS 26.501CR0044
  • [5GMSA_Ph2] 5GMS over 5MBS TS 26.501CR0045
  • [5GMS_Ph2] Data collection for ANBR-based NA TS 26.501CR0056
  • [5GMS_Ph2] 5GMS AS configuration via M3 TS 26.501CR0059
  • [5GMS_Pro_Ph2] ANBR-based network assistance data reporting TS 26.512CR0040
  • [5GMS_Pro_Ph2] Event exposure APIs TS 26.512CR0041

+ 39 more changes

Explore further

Broader topics and technologies where 5GMS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 26.116 vj00 TV Video Formats for 3GPP Services Rel-19
TS 26.247 vj00 3GPP Progressive Download & DASH over HTTP Rel-19
TS 26.348 vj00 xMB Interface Specification Rel-19
TS 26.501 vj30 5G Media Streaming (5GMS) Architecture Rel-19
TS 26.511 vj00 5G Media Streaming Profiles, Codecs & Formats Rel-19
TS 26.512 vj10 5G Media Streaming Protocols & APIs Rel-19
TR 26.927 vj00 AI/ML in 5G Media Services Study Rel-19
TR 26.942 vj00 Study on Media Energy Consumption Exposure & Evaluation Rel-19
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19
TS 29.116 vj00 REST-based protocol for xMB reference point Rel-19
TS 29.517 vj40 5G AF Event Exposure Service Stage 3 Rel-19
TS 29.591 vj40 5G NEF Southbound Services Stage 3 Rel-19
TS 33.127 vj50 Lawful Interception Architecture and Functions 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.