Information technology - Multimedia service platform technologies - Part 2: MPEG extensible middleware (MXM) API
Introduction: The ISO/IEC 23006 series is a suite of standards that has been developed for the purpose of enabling the easy design and implementation of media-handling value chains whose devices interoperate because they are all based on the same set of technologies, especially MPEG technologies, accessible from the middleware APIs, elementary services and aggregated services. The ISO/IEC 23006 series is referred to as MPEG Extensible Middleware (MXM) in its first edition, and it specifies an architecture (ISO/IEC 23006-1), an API (ISO/IEC 23006-2), a conformance and reference software (ISO/IEC 23006-3) and a set of protocols which MXM Devices had to adhere (ISO/IEC 23006- 4). It specifies also how to combine elementary services into aggregated services (ISO/IEC 23006-5). The ISO/IEC 23006 series is subdivided into five parts: Part 1 — Architecture: specifies the architecture that can be used as a guide to an MPEG-M implementation; Part 2 — MPEG Extensible Middleware (MXM) Application Programming Interface (APIs) (this document): specifies the middleware APIs; Part 3 — Conformance and Reference Software: specifies conformance criteria and a reference software implementation with a normative value; Part 4 — Elementary Services: specifies elementary service protocols between MPEG-M applications; Part 5 — Service Aggregation: specifies mechanisms enabling the combination of Elementary Services and other services to build Aggregated Services. vi © ISO/IEC 2016 – All rights reserved
Scope: This document specifies a set of Application Programming Interfaces (called for short MXM APIs) so that MPEG-M Applications running on an MPEG-M Device can access the standard multimedia technologies contained in its Middleware as MPEG-M Engines, as specified by ISO/IEC 23006-1. The MXM APIs belong to two classes: — the MPEG-M Engine APIs, i.e. the collection of the individual MPEG-M Engine APIs providing access to a single MPEG technology (e.g. video coding) or to a group of MPEG technologies where this is convenient; — the MPEG-M Orchestrator API, i.e. the API of the special MPEG-M Engine (called Orchestrator Engine) that is capable of creating chains of MPEG-M Engines to execute high-level application calls such as “Play a video”, as opposed to the typically low-level MPEG-M Engine API calls.