Overview
ISO/IEC 23006-1:2018 defines the architecture for MPEG‑M - a standardized multimedia service platform technology for interoperable media-handling value chains. Part 1 (Architecture) specifies the service‑oriented reference architecture exposed through a set of high‑level APIs, the MPEG extensible middleware (MXM) API, elementary service protocols and service aggregation mechanisms. The document is the architectural backbone of the ISO/IEC 23006 series and is complemented by Parts 2–5 (middleware APIs, conformance/reference software, elementary services and service aggregation).
Key technical topics and requirements
- Service‑oriented architecture (SOA) for multimedia platforms that enables interoperable devices and applications across a global ecosystem.
- Middleware and engines: the architecture models middleware as a collection of engines (protocol engines, technology engines, orchestrator engine) that expose engine APIs; middleware API is the aggregate of these engine APIs.
- High‑level and low‑level APIs: devices expose a high‑level API to applications and low‑level APIs to hardware or specialized devices (security modules, network interfaces).
- Orchestration: a dedicated orchestrator engine composes chains of engines to execute complex high‑level calls (e.g., play), enabling flexible processing pipelines.
- Elementary services and aggregated services: elementary services (specified in Part 4) are composable building blocks; service providers can combine them into aggregated services (specified in Part 5).
- Conformance and reference software: Part 3 provides normative conformance criteria and a reference implementation to guide interoperable deployments.
- Namespaces and interoperability conventions: standardized namespace prefixes and XML schema guidance for consistent data and protocol exchanges.
- Informative examples: Annex A illustrates how MPEG‑M can form a fully fledged multimedia platform.
Practical applications and users
ISO/IEC 23006-1 is aimed at organizations building interoperable multimedia ecosystems:
- Developers of multimedia applications who consume the high‑level API to access device services.
- Middleware and SDK vendors implementing MXM engines and exposing engine APIs.
- Device manufacturers integrating standardized middleware to ensure global compatibility.
- Service providers designing value chains and aggregated multimedia services (content distribution, discovery, entitlement, personalized processing).
- System integrators deploying end‑to‑end media solutions that require conformance testing against the reference software.
Practical use cases include distributed content generation/processing, adaptive streaming support (interoperable with DASH and publish/subscribe models), cross‑provider service composition, and enabling new business models through easy service aggregation.
Related standards
Keywords: ISO/IEC 23006-1, MPEG‑M, multimedia service platform, architecture, MXM, middleware API, engines, orchestration, elementary services, aggregated services, conformance, reference software.
Open preview (PDF)Information technology — Multimedia service platform technologies — Part 1: Architecture