OMAF

Omnidirectional Media Application Format

Services →
Introduced in Rel-15

OMAF is a 3GPP and MPEG standard that defines the format, delivery, and rendering of 360-degree and immersive media for consistent playback over networks.

Category
Services
Introduced
Rel-15
Where
Services › Codecs
Specifications
12 specs
OMAF Description Purpose Related Classification Detected Changes Specifications

Description

OMAF, standardized as ISO/IEC 23090-2 and adopted by 3GPP in TS 26.114 and related specs, is a comprehensive media format designed specifically for omnidirectional (360-degree) media. It builds upon existing media foundations like ISO Base Media File Format (ISOBMFF) and High Efficiency Video Coding (HEVC) but adds critical extensions for spherical video. The core of OMAF is the definition of a coordinate system and projection methods to map the 360-degree spherical video onto a 2D rectangular video frame for efficient encoding and storage. Common projections include Equirectangular Projection (ERP) and Cubemap Projection (CMP).

Architecturally, OMAF defines a media processing pipeline. On the creation side, the spherical video is projected, encoded using HEVC (and optionally AVC), and packaged into ISOBMFF segments with OMAF-specific metadata. This metadata includes essential information like the Projection Format, Region-Wise Packing (which maps spherical regions to the 2D frame), and the Initial Viewing Orientation. For delivery, OMAF supports Dynamic Adaptive Streaming over HTTP (DASH), where the media is divided into segments of multiple quality levels (bitrates). A key feature is viewport-dependent streaming, where the client requests higher quality segments only for the portion of the sphere currently in the user's field of view (viewport), saving bandwidth.

On the client/player side, the OMAF player demultiplexes the stream, reads the OMAF metadata, decodes the video, and performs the inverse projection to re-render the spherical video for display, typically on a head-mounted display (HMD) or a smartphone screen used with a VR viewer. It manages viewport tracking and adapts the streaming requests accordingly. OMAF also specifies audio formats, including channel-based, scene-based (Ambisonics), and object-based audio, to accompany the 360-degree video for a fully immersive experience. Its role in the 5G network is as a key application-layer format that leverages 5G's high bandwidth and low latency for delivering immersive media services.

Purpose & Motivation

OMAF was created to address the lack of standardization in the rapidly emerging field of 360-degree and virtual reality (VR) video. Before OMAF, content creators, service providers, and device manufacturers used proprietary or incompatible formats for capturing, encoding, and streaming spherical video. This fragmentation threatened to stifle the growth of immersive media by creating walled gardens where content from one provider might not play on another's device, similar to the early days of mobile video.

The primary problem OMAF solves is ensuring interoperability. It provides a single, agreed-upon format that guarantees a piece of OMAF-compliant 360-degree content will play correctly on any OMAF-compliant player, regardless of the vendor. This reduces complexity and cost for the ecosystem. Furthermore, OMAF addresses the significant technical challenge of bandwidth. A full high-resolution 360-degree video requires enormous data rates if streamed in full quality at all times. OMAF's viewport-dependent streaming mechanism is a key innovation that solves this by dynamically streaming high quality only where the user is looking, making immersive video services feasible over mobile networks like 4G and 5G.

Its creation was motivated by the industry's move towards immersive experiences as part of 5G use cases, such as enhanced Mobile Broadband (eMBB). Standard bodies like MPEG and 3GPP collaborated to ensure the format was optimized for both storage/broadcast and adaptive streaming over IP networks. By being part of 3GPP specifications, OMAF is directly integrated into the 5G media delivery architecture, enabling operators to offer standardized, high-quality VR/360 video services.

Classification

Part ofDASH
Specific typesOMASA
Related approachesHEVCVR

Detected Changes Across Releases

from 3GPP Change Requests

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

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

Rel-16 5 changes

In Release 16, the OMAF function was enhanced to support immersive media through the integration of the ISO/IEC 23090-2 Omnidirectional Media Format standard. This provided a standardized format for 360-degree video, which can be limited in the horizontal or vertical field of view. The release also introduced support for application data channel multiplexing over a single SDP media line.

  • Corrections to 5G Media Streaming TS 26.511CR0001
  • Adding Media Feature Tag for IMS Data Channel TS 26.114CR0499
  • IETF Reference Update for Data Channel Media TS 26.114CR0510
  • Various Corrections to 5GMS Codecs and Formats TS 26.511CR0002
  • Profiles, Codecs and Formats (UCC) TS 26.511
Rel-18 5 changes

In Release 18, the OMAF function introduced new work items to study the traffic characteristics and RTP-based Application Layer FEC for extended reality (XR) traffic. It also initiated a study on an Implicit Neural Representation format for AR scenes and included corrections to the RTCP viewport feedback format value and to the signaling for IMSC 1.1, AVC, and HEVC within the 5G Media Streaming framework.

  • [FS_XRTraffic] Application Layer FEC Traffic characteristics TS 26.926CR0001
  • [FS_XRTraffic] RTP-based Application Layer FEC TS 26.926CR0002
  • [FS_5GSTAR] Implicit Neural Representation format in AR Scenes TS 26.998CR0003
  • Correction of RTCP Viewport feedback format value TS 26.114CR0577
  • [5GMS3] Correction on IMSC 1.1. AVC and HEVC signaling TS 26.511CR0011
Rel-19 4 changes

In Release 19, the OMAF function introduced updates for MV-HEVC and clarified procedures for downloading DC applications, including specifying the URL for the DC Application List. It also added the `app-dc-status` parameter to the `3gpp-req-app` attribute for SDP negotiation to manage IMS application data channels, which support multiplexing of multiple channels on a single media description.

  • [VOPS] Updates for MV-HEVC TS 26.511CR0013
  • Clarification of procedures for DC application download TS 26.114CR0585
  • Adding app-dc-status parameter to 3gpp-req-app attribute for SDP negotiation of IMS application data channels TS 26.114CR0590
  • Clarification on the URL for Downloading the DC Application List TS 26.114CR0597

Explore further

Broader topics and technologies where OMAF plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 26.114 vj10 IMS Multimedia Telephony Media Handling Rel-19
TS 26.118 vj00 Virtual Reality Media Formats Rel-19
TS 26.511 vj00 5G Media Streaming Profiles, Codecs & Formats Rel-19
TS 26.818 vf00 Audio Media Profiles Test Results for VR Streaming Rel-15
TR 26.862 vh00 Immersive Teleconferencing & Telepresence for Remote Terminals Rel-17
TS 26.891 vg00 Media Distribution Services in 5G System Rel-16
TR 26.918 vj00 Virtual Reality Relevance Study for 3GPP Rel-19
TR 26.919 vj00 Study on 5G Conversational Media Handling Rel-19
TR 26.926 vj00 Traffic Models & Quality Evaluation for Media/XR in 5G Rel-19
TR 26.962 vj00 ITT4RT Operation and Usage Guidelines Rel-19
TR 26.998 vj00 5G AR/MR Glasses Integration Study Rel-19
TR 26.999 vj00 VR Streaming Interoperability Test Material Rel-19