Description
MHEG is an ISO/IEC standard (ISO/IEC 13522) that specifies a format and an engine for interactive multimedia applications, often used in broadcast environments like digital television. In the 3GPP context, it was referenced for potential multimedia service interoperability, though its primary deployment was in broadcast. The core of MHEG is the MHEG object model. An MHEG application, or 'scene', is composed of a set of objects that are downloaded and interpreted by an MHEG engine (a virtual machine) in the receiver, such as a digital TV set-top box. Key object types include the Application object (root), Scene objects (individual screens), Presentable objects (visible elements like Text, Rectangle, Bitmap, Video, and Button), Link objects (for defining interactivity and navigation), and Script objects (for simple procedural logic). These objects have attributes and behaviors defined in the standard. The application is typically delivered as a carousel within the broadcast transport stream, allowing the receiver to access the necessary objects. The MHEG engine parses these objects, builds a scene graph, renders the visible elements on screen, and manages user interaction via remote control. For example, pressing a red button on a remote could trigger a Link object that causes the engine to transition to a new Scene object, displaying an interactive sports scoreboard. MHEG-5, a widely adopted profile, focused on a lightweight, declarative approach suitable for resource-constrained receivers, avoiding complex scripting. It used an event-action paradigm where user or system events (like a timer expiry) triggered predefined actions (like playing a video). While not a programming language per se, it provided a standardized way to create synchronized, interactive presentations combining graphics, text, and video. In 3GPP, MHEG was considered as part of early multimedia service frameworks (like MMS) for standardizing presentation formats, but its direct implementation in mobile networks was limited compared to later technologies like SVG-T or SMIL.
Purpose & Motivation
MHEG was created to address the need for a standardized, platform-independent format for interactive multimedia applications, primarily in the emerging digital television market of the 1990s. Before MHEG, interactive TV services were proprietary, locking broadcasters and consumers into specific vendor ecosystems. This fragmentation hindered the growth of interactive services. MHEG aimed to solve this by providing an open international standard that would allow an application authored once to run on any compliant receiver from any manufacturer. Its design was motivated by the constraints of broadcast receivers: limited memory, processing power, and a simple input device (a remote control). Therefore, MHEG-5 was intentionally declarative and lightweight, avoiding the need for a full-featured scripting engine. It enabled the first generation of digital TV interactive services, such as electronic program guides (EPGs), teletext-over-digital (Ceefax/Teletext replacement), and simple 'red button' applications. In the 3GPP realm, MHEG was referenced in early releases (from Rel-4) as part of exploring standardized formats for multimedia messaging and presentation, aiming for convergence between telecom and broadcast services. However, the evolution of the web (HTML, JavaScript) and more powerful mobile devices ultimately made those technologies more suitable for mobile interactive services, limiting MHEG's role in 3GPP primarily to a historical reference point for multimedia application interoperability concepts.
Key Features
- Declarative object-oriented model for defining interactive multimedia scenes
- Standardized set of presentable objects (Text, Bitmap, Rectangle, Video, Button) for UI construction
- Event-action model for defining interactivity (e.g., on user selection, transition to a new scene)
- Carousel-based delivery mechanism suitable for broadcast transport streams (like DVB)
- Lightweight MHEG-5 profile designed for resource-constrained set-top boxes
- Platform-independent application format enabling interoperability across different receiver hardware
Evolution Across Releases
Initially referenced MHEG (specifically MHEG-5) within 3GPP specifications as a potential format for multimedia applications and messaging. It was considered part of the toolkit for standardizing multimedia presentation layers in early 3G services, aligning with efforts to define rich multimedia capabilities.
Continued referencing as part of the Multimedia Messaging Service (MMS) and multimedia domain specifications. However, the focus for mobile interactive applications began shifting towards more web-compatible technologies like SVG and SMIL, reducing MHEG's prominence in the mobile context.
MHEG remains in 3GPP specifications primarily for historical reference and completeness. No significant functional enhancements were made within 3GPP, as its practical deployment was almost entirely within the digital broadcast television domain (DVB, ATSC) rather than 3GPP mobile networks.
Defining Specifications
| Specification | Title |
|---|---|
| TS 21.905 | 3GPP TS 21.905 |
| TS 22.960 | 3GPP TS 22.960 |