VDI

Video Decoding Interface

Interface
Introduced in Rel-7
A standardized interface within the 3GPP Multimedia Broadcast Multicast Service (MBMS) architecture that defines how a client application or user equipment requests and receives decoded video streams from a network-based decoding function. It enables efficient video delivery by offloading complex decoding tasks.

Description

The Video Decoding Interface (VDI) is a functional interface specified in the context of 3GPP's Multimedia Broadcast Multicast Service (MBMS) and related multimedia delivery frameworks. Its primary role is to define the protocols and procedures for a client, typically in user equipment (UE) or a terminal, to interact with a network-based video decoding entity. This interface allows the client to request video content that is delivered in an encoded format, which is then decoded by a network function before being sent to the client in a ready-to-display format. The architecture separates the computationally intensive task of video decoding from the resource-constrained UE, centralizing it in the network.

Operationally, the VDI works by establishing a session between the client and a Video Decoding Function (VDF) within the network. The client sends a request specifying the desired video content and potentially the required output format (e.g., resolution, codec). The network's VDF retrieves the encoded video stream, which may be broadcast/multicast via MBMS or delivered unicast, performs the decoding process, and then streams the decoded video (e.g., in a raw YUV format or a lightly packaged form) to the client over a dedicated bearer. This process involves signaling for session establishment, control commands (play, pause, stop), and the streaming of the decoded video data itself.

Key components include the VDI Client in the UE, the Video Decoding Function in the network (which could be part of a Broadcast-Multicast Service Center (BM-SC) or a dedicated media processing node), and the defined application-layer protocols for control and transport. The interface specifications cover aspects like capability negotiation, error reporting, and synchronization. Its role is critical in scenarios where the UE lacks the processing power or battery life to decode high-quality video streams locally, or when the network wants to ensure uniform video quality by managing the decoding process centrally.

Purpose & Motivation

The Video Decoding Interface was created to address the challenge of delivering high-quality video services to a wide range of mobile devices with varying computational capabilities and battery constraints. Early mobile video services required the UE to perform full video decoding, which could drain batteries quickly and exclude low-end devices from accessing advanced content. VDI solved this by introducing a network-based decoding architecture, offloading the complex task to the network infrastructure.

The primary problem it solves is enabling efficient and equitable multimedia broadcast/multicast. For MBMS, where the same content is sent to many users, performing decoding once in the network and then streaming the decoded video can be more efficient than sending encoded streams that each UE must decode individually, especially if the decoded stream can be adapted to a common format. This also allows the network to perform transcoding or transrating centrally to match different UE display capabilities.

Historically introduced in Release 7 alongside MBMS enhancements, VDI was part of the effort to make mobile TV and video broadcast services viable. It provided a standardized way to implement thin-client video architectures, reducing UE cost and complexity. While not universally deployed in all networks, it represents an important architectural concept in 3GPP for network-assisted media processing, a principle that sees echoes in later technologies like mobile edge computing and cloud gaming.

Key Features

  • Defines protocols for UE to request network-based video decoding sessions
  • Supports delivery of decoded video streams in ready-to-render formats
  • Enables capability negotiation between client and network decoding function
  • Allows control commands (play, pause, stop) to be sent over the interface
  • Facilitates error reporting and recovery mechanisms for the decoding session
  • Designed to work with both MBMS broadcast/multicast and unicast delivery mechanisms

Evolution Across Releases

Rel-7 Initial

Introduced the Video Decoding Interface as part of the enhanced MBMS (eMBMS) framework. Defined the initial architecture, protocol stack, and procedures for a client to establish a session with a network-based Video Decoding Function (VDF) to receive decoded video streams, primarily targeting mobile TV services.

Refinements and integration with the evolved packet system (EPS) and LTE. Ensured the VDI concepts aligned with the new radio access and core network architecture, maintaining support for network-based decoding in the LTE/EPC context.

Further enhancements for service continuity and improved performance, potentially involving better session management and synchronization procedures for the decoded video delivery.

Maintenance updates and potential alignment with broader IMS-based multimedia service frameworks. Ensured the interface specifications remained consistent with other multimedia delivery mechanisms.

Continued support as part of the MBMS feature set, with minor clarifications and corrections to the protocol specifications based on implementation feedback.

Integrated with further MBMS enhancements and the introduction of evolved MBMS (eMBMS) for LTE. The VDI was maintained as a possible architectural option for service providers offering network-assisted decoding.

Specifications kept stable with no major new features. The interface remained a defined component for specialized broadcast/multicast video services.

Continued as a referenceable interface within the MBMS architecture. Its development was largely frozen, with focus shifting to other enablers for multimedia delivery.

Maintained for backward compatibility and potential use in 5G broadcast scenarios, though 5G media delivery often emphasizes different architectures. No functional updates were made.

Remained part of the 3GPP specification library as a stable, mature interface definition, with no active development or enhancements planned.

No changes. The VDI specifications are preserved for historical and referential purposes within the suite of MBMS-related documents.

Continued as an unchanged specification element. Its relevance is tied to legacy MBMS service deployments that may utilize network-based decoding.

Maintained without modification, representing a specific architectural approach to video delivery within the 3GPP standards history.

Defining Specifications

SpecificationTitle
TS 23.206 3GPP TS 23.206
TS 24.206 3GPP TS 24.206
TS 24.216 3GPP TS 24.216
TS 26.998 3GPP TS 26.998