OTT

Over The Top

Services →
Introduced in Rel-12

OTT is a service delivered over the internet that bypasses a telecom operator's own service platforms, utilizing their IP connectivity but not their dedicated infrastructure, such as with VoIP or video streaming.

Category
Services
Introduced
Rel-12
Where
Services › Codecs
Specifications
9 specs
OTT Description Purpose Related Classification Specifications

Description

Over The Top (OTT) denotes service providers that deliver content, applications, and communications services directly to end-users via the public internet, using the internet access provided by telecommunications network operators. In the 3GPP context, OTT services are distinct from operator-managed IMS (IP Multimedia Subsystem) services like VoLTE. They run on top of the operator's IP transport layer (the 'dumb pipe') without the operator's involvement in service control, billing, or quality assurance for the application layer. Examples include Skype, WhatsApp, Netflix, and YouTube.

From an architectural perspective, the mobile network provides the underlying IP Connectivity Access Network (IP-CAN) – such as LTE or 5G NR data bearers – which offers best-effort internet access. The OTT service provider operates its own application servers in data centers or cloud platforms. The User Equipment (UE) runs a client application that establishes an encrypted connection (e.g., via TLS/HTTPS, WebRTC) directly to these OTT servers. The 3GPP core network (EPC or 5GC) is unaware of the specific OTT application; it merely routes IP packets between the UE and the internet. This contrasts with operator-managed services, where the core network elements (like P-CSCF in IMS) are deeply involved in session control and policy enforcement.

OTT services work by leveraging the standardized IP connectivity of mobile networks. The UE attaches to the network, establishes a Packet Data Network (PDN) connection or a Protocol Data Unit (PDU) Session with an Access Point Name (APN) for internet access, and receives an IP address. The OTT application on the device then uses this IP connectivity to communicate with its remote servers. Key differentiators are the lack of integration with 3GPP charging systems (using app-store or credit card billing instead) and typically no guaranteed Quality of Service (QoS) from the operator, though some operators offer sponsored data or QoS differentiation packages. 3GPP studies OTT impacts to understand traffic patterns, develop policy controls, and explore potential collaborations or new business models like edge computing partnerships.

Purpose & Motivation

The OTT phenomenon emerged due to the widespread adoption of IP-based mobile broadband (starting with HSPA and LTE), which provided sufficient bandwidth and always-on connectivity for rich internet applications. It solved the problem of service innovation being bottlenecked by slow operator development and deployment cycles. Entrepreneurs and tech companies could rapidly develop and globally deploy applications (like voice, video, messaging) directly to consumers without needing to negotiate with hundreds of operators worldwide or integrate into complex telecom signaling systems.

OTT services addressed limitations of traditional telecom services, which were often siloed, expensive (e.g., international SMS), and lacked rich features. They leveraged the internet's open, end-to-end principle and cloud scalability. For 3GPP, the rise of OTT created both challenges and opportunities. Challenges included declining revenues from legacy services (voice, SMS) and increased, unpredictable data traffic straining networks. Opportunities included increased data subscription demand and potential new roles for operators, such as providing enhanced connectivity (e.g., network slicing), edge hosting for OTT applications, or exposing network APIs (via NEF in 5G) for improved service quality.

3GPP began formally studying OTT in Release 12 to understand its technical and business impacts, leading to work on policy enhancements, traffic detection, and architectural evolutions like Service Capability Exposure that allow secure, standardized interaction between the network and OTT providers. This acknowledges that while OTT bypasses traditional service layers, collaboration can create value for both sides in the 5G era.

Classification

Part ofIMS
Related approachesMECNEF

Evolution Across Releases

Rel-12 Initial

Initiated formal 3GPP studies on OTT services, analyzing their impact on network traffic, operator business models, and potential standardization needs. Focused on understanding the technical characteristics of OTT communication services.

Enhanced policy and charging control (PCC) capabilities to better manage OTT traffic, including service data flow detection and differentiated charging. Began work on network APIs for limited service exposure.

Introduced the Network Exposure Function (NEF) as part of the 5G Service-Based Architecture, providing a standardized framework for securely exposing network capabilities (like QoS, location) to authorized third parties, including OTT providers.

Advanced edge computing (MEC) integration, enabling OTT applications to be hosted at the network edge for ultra-low latency. Enhanced network slicing to potentially offer dedicated virtual networks with specific characteristics to OTT service providers.

Ongoing exploration of deeper OTT-network integration for immersive services (eXtended Reality), AI-driven traffic optimization, and enhanced exposure of 5G-Advanced capabilities like precise positioning and deterministic networking to application providers.

Explore further

Broader topics and technologies where OTT plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 22.101 vk00 Service Principles for PLMNs Rel-20
TR 22.816 ve10 3GPP TV Service Enhancement Technical Report Rel-14
TS 22.830 vg10 Business Role Models for Network Slicing Rel-16
TS 23.791 vg20 NWDAF Data Collection & Analytics Framework Rel-16
TS 26.849 vc10 MBMS Operation on Demand (MooD) Rel-12
TR 26.909 vj00 QoE Enhancement for Streaming Services Rel-19
TR 26.922 vj00 Video Telephony Robustness Improvements Study Rel-19
TR 26.927 vj00 AI/ML in 5G Media Services Study Rel-19
TS 28.802 vf00 Management Study for 5G Network Architecture Rel-15