DIMS

Dynamic and Interactive Multimedia Scene

Services →
Introduced in Rel-8

DIMS is a 3GPP service enabling synchronized, interactive multimedia presentations across multiple devices by defining scenes composed of media components and commands.

Category
Services
Introduced
Rel-8
Where
Services › Codecs
Specifications
7 specs
DIMS Description Purpose Related Classification Detected Changes Specifications

Description

DIMS (Dynamic and Interactive Multimedia Scene) is a 3GPP standardized service (TS 26.140) that provides a framework for creating, delivering, and rendering synchronized, interactive multimedia presentations. A DIMS presentation is called a 'Scene'. A Scene is a temporal composition of multimedia components—such as video, audio, images, text, and graphics—that are spatially arranged and can change dynamically based on user interaction or timed events. The core innovation of DIMS is the 'Scene Command', a set of instructions defined in the DIMS specification that modify the state of a Scene in a deterministic way. These commands are delivered alongside or within the media streams.

Architecturally, a DIMS service involves several key entities: the DIMS Application Server, which authors and packages the Scene; the delivery network (e.g., MBMS, PSS, or streaming servers); and the DIMS Client residing on the user's device. The Scene description, often using a declarative format, defines the initial layout, media components, and their relationships. The dynamic behavior is controlled by Scene Commands. These commands are small, efficient instructions that can trigger actions like 'ShowComponent', 'HideComponent', 'MoveTo', 'ChangeVolume', or 'LoadNewMedia'. They are timestamped and synchronized with the media timeline, ensuring all clients update the Scene state at precisely the same moment.

The DIMS Client is responsible for interpreting the Scene description, receiving and buffering media components, and executing the incoming stream of Scene Commands. It maintains a scene graph representing the current state of all components. Upon receiving a command, the client updates this internal model and renders the changes accordingly. This allows for complex interactivity, such as letting a user select a camera angle during a sports event, which triggers a Scene Command to switch the video source, all while keeping other on-screen graphics synchronized. The service supports unicast, multicast, and broadcast delivery, making it suitable for both personalized and mass-media experiences.

DIMS plays a significant role in enabling next-generation multimedia services. It moves beyond simple streaming to offer a rich, application-like experience within a standardized broadcast or streaming framework. Its synchronization mechanisms are crucial for creating 'social viewing' experiences where multiple users see the same interactive elements simultaneously. Furthermore, by separating the control logic (Scene Commands) from the media assets, it allows for lightweight updates and personalization without needing to retransmit entire video streams, optimizing bandwidth usage.

Purpose & Motivation

DIMS was created to address the limitations of traditional linear broadcast and on-demand streaming services, which offered little room for synchronized interactivity and multi-screen experiences. Before DIMS, creating an interactive TV experience where graphics, alternative audio tracks, or camera angles could be changed in sync across millions of viewers required proprietary, non-interoperable technologies. This fragmented the market and increased costs for content creators and device manufacturers.

The primary problem DIMS solves is the standardized delivery of synchronized, stateful multimedia presentations. It was motivated by the growing demand for enriched TV (e.g., sports stats overlays, interactive advertising, choose-your-own-adventure stories) and the proliferation of second-screen applications. Without DIMS, synchronizing a companion app on a tablet with the main broadcast on a TV was complex and error-prone. DIMS provides a unified model where a single authored Scene can be rendered consistently across different device types, with built-in mechanisms for user input and state changes.

Historically, DIMS (introduced in Release 8) was part of 3GPP's broader push into advanced multimedia services alongside MBMS (Multimedia Broadcast Multicast Service) and PSS (Packet Switched Streaming). It aimed to leverage mobile networks' bidirectional capabilities to add interactivity to broadcast content. The technology was also seen as an enabler for rich media education, interactive advertising, and enhanced public warning systems. By providing a standardized 'scene graph' model and command set, it allowed content creators to write once and deploy everywhere, fostering innovation in interactive media while ensuring reliability and synchronization—key aspects where previous ad-hoc solutions failed.

Classification

Part ofMBMS

Detected Changes Across Releases

from 3GPP Change Requests

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

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

Rel-16 1 change

In Release 16, the Dynamic and Interactive Multimedia Scene (DIMS) function was newly introduced, mandating that MMS clients and servers support the 3GPP TS 26.142 specification. This addition formalized the use of 3D scenes as a presentation format for multimedia messages, including associated capabilities for 3D and AR scenes in the glTF2.0 format. Furthermore, the release addressed a missing XML data type for attributes within the MBMS USD (User Service Description).

  • Missing XML Data Type for Attributes in MBMS USD TS 26.346CR0658
Rel-19 2 changes

In Release 19, the DIMS function introduced new procedures for in-session unicast repair during MBMS object distribution to enhance reliability. It also incorporated improved time synchronization mechanisms specifically for MBMS delivery. These updates built upon the existing foundation where DIMS-compliant clients and servers are required to support the scene description and synchronization schemes defined in 3GPP TS 26.142.

  • [AMD_PRO-MED] In-session Unicast Repair for MBMS Object Distribution TS 26.346CR0677
  • Improved Time Synchronization for MBMS TS 26.346CR0672

Explore further

Broader topics and technologies where DIMS plays a role.

Defining Specifications

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

SpecificationTitleRelease
TS 26.140 vj00 MMS Media Formats and Codecs Specification Rel-19
TS 26.142 vj00 3GPP TS 26.142: Dynamic and Interactive Multimedia Scenes (DIMS) Rel-19
TS 26.234 vj00 3GPP PSS Protocols and Codecs Specification Rel-19
TS 26.244 vj00 3GPP File Format (3GP) Specification Rel-19
TS 26.346 vj20 MBMS User Services Media Codecs & Protocols Rel-19
TS 26.430 vj00 Timed Graphics Media Type Specification Rel-19
TR 26.907 vj00 HTML5 for 3GPP Services Study Rel-19