ISO/IEC 23006-2:2016

Overview

ISO/IEC 23006-2:2016 specifies the MPEG extensible middleware (MXM) API, a standard set of Application Programming Interfaces that lets MPEG‑M Applications running on an MPEG‑M Device access standard multimedia technologies packaged in the device Middleware as MPEG‑M Engines. The MXM APIs are organized into two classes:

• MPEG‑M Engine APIs - APIs for individual technology engines (e.g., video coding, metadata, security).
• MPEG‑M Orchestrator API - a higher‑level API for the Orchestrator Engine that can chain multiple engines to perform composite operations (for example, “Play a video”).

This part of the ISO/IEC 23006 series defines namespace conventions, common MXM interfaces and classes, detailed engine API families (Technology Engines and Protocol Engines), orchestrator APIs and MXM configuration rules (Annex A).

Key technical topics and requirements

• API architecture and naming conventions: namespace and interface design to ensure consistent MXM implementations.
• Common interfaces and classes: standard object models and base APIs that MPEG‑M Engines and applications use to interoperate.
• Technology Engine APIs: defined engine groups found in the standard, such as Digital Item Engine, Media Framework Engine, Metadata Engine, Security Engine, Search Engine, Overlay Engine, Sensory Effect Engine, Compact Descriptor for Visual Search Engine, and more.
• Protocol Engine APIs: APIs for service and protocol handling (Authenticate, Authorize, Deliver, Search, Store, etc.) enabling networked media services.
• MXM Orchestrator APIs: APIs that enable composition and orchestration of multiple engines to support high‑level application calls.
• Configuration and conformance: guidance for MXM configuration (Annex A) and integration with the ISO/IEC 23006 series conformance and reference software.

Practical applications

ISO/IEC 23006-2:2016 enables interoperable middleware solutions for media-handling value chains. Typical uses include:

• Smart TV and set‑top box middleware exposing MPEG technologies to apps.
• Media players and streaming platforms that need standardized access to codecs, metadata, DRM and search.
• Content management and delivery systems integrating MPEG file formats, metadata and rights management.
• Middleware vendors implementing a common MXM API to support third‑party multimedia applications.
• Service providers composing elementary services into aggregated services via orchestrator APIs.

Who should use this standard

• Middleware architects and API designers
• Device manufacturers (smart TVs, STBs, media players)
• Middleware and platform vendors
• Application developers targeting MPEG‑M devices
• Standards implementers and conformance test engineers

Related standards

• ISO/IEC 23006-1 - MXM Architecture
• ISO/IEC 23006-3 - Conformance and Reference Software
• ISO/IEC 23006-4 - Elementary Services (protocols)
• ISO/IEC 23006-5 - Service Aggregation

Keywords: ISO/IEC 23006-2:2016, MPEG extensible middleware, MXM API, MPEG‑M Engines, Orchestrator API, multimedia middleware, media interoperability.