ISO/IEC 23006-1:2011
(Main)Information technology — MPEG extensible middleware (MXM) — Part 1: MXM architecture and technologies
Information technology — MPEG extensible middleware (MXM) — Part 1: MXM architecture and technologies
ISO/IEC 23006-1:2011 specifies the MXM Architecture and references the technologies that are part of MXM. The architecture comprises a set of MXM Engines for which application programming interfaces (APIs) are defined, on top of which applications can be developed. The current list of MXM Engines includes functionalities for content creation/search, adaptation, streaming/delivery, domain management, IPMP, rights expression, licensing, metadata, event reporting, security, etc. The Orchestrator Engine plays a special role, providing access to higher-level functionalities by implementing common scenarios utilizing various MXM Engines in a pre-defined way (e.g. adaptation of content according to the usage context). In order to enable interoperable communication between MXM devices, ISO/IEC 23006-1:2011 defines MXM protocols. Only the payload format is specified, which is XML-based and can be delivered using any suitable transport protocol (e.g. HTML, Web Services). The elements of the MXM Architecture are as follows: MXM Engines, collections of specific technologies that it is meaningful to bundle together; MXM Engine APIs, APIs that can be used to access MXM Engine functionality; Orchestrator Engine, a special MXM Engine capable of creating chains of MXM Engines to execute a high-level application call such as "Play"; MXM Orchestrator Engine APIs; MXM Device, a device equipped with MXM; MXM Application, an application that runs on an MXM Device and makes calls to the MXM Application API and MXM Engine APIs; MXM protocols for MXM to MXM communications.
Technologies de l'information — Intergiciel MPEG extensible (MXM) — Partie 1: Technologies et architecture MXM
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 23006-1
First edition
2011-06-01
Information technology — MPEG
extensible middleware (MXM) —
Part 1:
MXM architecture and technologies
Technologies de l'information — Intergiciel MPEG extensible (MXM) —
Partie 1: Technologies et architecture MXM
Reference number
ISO/IEC 23006-1:2011(E)
©
ISO/IEC 2011
---------------------- Page: 1 ----------------------
ISO/IEC 23006-1:2011(E)
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56 • CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail copyright@iso.org
Web www.iso.org
Published in Switzerland
ii © ISO/IEC 2011 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 23006-1:2011(E)
Contents Page
Foreword .iv
Introduction.v
1 Scope.1
2 Terms and definitions .1
3 Abbreviated terms .3
4 System overview .4
4.1 Introduction.4
4.2 MXM Device.4
4.3 MXM Architecture .4
5 MXM Architecture .7
5.1 Introduction.7
6 MXM Engines .8
6.1 Introduction.8
6.2 Digital Item Engine .8
6.3 MPEG-21 File Engine.9
6.4 REL Engine .9
6.5 IPMP Engine.9
6.6 Media Framework Engine .9
6.7 Metadata Engine .12
6.8 Digital Item Streaming Engine .12
6.9 Digital Item Adaptation Engine .12
6.10 Event Reporting Engine.13
6.11 Content Protocol Engine .13
6.12 Licence Protocol Engine.13
6.13 IPMP Tool Protocol Engine.14
6.14 Content Search Engine.14
6.15 Security Engine .14
6.16 MVCO Engine.14
6.17 Domain Engine .15
6.18 Rendering Engine.15
6.19 Orchestrator Engine.15
Bibliography.16
© ISO/IEC 2011 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 23006-1:2011(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 23006-1 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
ISO/IEC 23006 consists of the following parts, under the general title Information technology — MPEG
extensible middleware (MXM):
⎯ Part 1: MXM architecture and technologies
⎯ Part 2: MXM API
⎯ Part 3: MXM reference software
⎯ Part 4: MXM protocols
iv © ISO/IEC 2011 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 23006-1:2011(E)
Introduction
ISO/IEC 23006 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 accessible from the MXM middleware.
This will enable the development of a global market of
⎯ MXM applications that can run on MXM devices thanks to the existence of a standard MXM application
API,
⎯ MXM devices executing MXM applications thanks to the existence of a standard MXM architecture,
⎯ MXM engines thanks to the existence of standard MXM architecture and standard APIs, and
⎯ innovative business models because of the ease to design and implement media-handling value chains
whose devices interoperate because they are all based on the same set of technologies.
© ISO/IEC 2011 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 23006-1:2011(E)
Information technology — MPEG extensible middleware
(MXM) —
Part 1:
MXM architecture and technologies
1 Scope
This part of ISO/IEC 23006 specifies the MXM architecture and references the technologies that are made
accessible through the set of MXM APIs specified in ISO/IEC 23006-2.
The elements of the MXM Architecture are as follows:
a) MXM Engines – collections of specific technologies that it is meaningful to bundle together;
b) MXM Engine APIs – APIs that can be used to access MXM Engine functionality;
c) Orchestrator Engine – a special MXM Engine capable of creating chains of MXM Engines to execute a
high-level application call such as “Play”;
d) MXM Orchestrator Engine APIs;
e) MXM Device – a device equipped with MXM;
f) MXM Application – an application that runs on an MXM Device and makes calls to the MXM Application
API and MXM Engine APIs;
g) MXM Protocols for enabling MXM to MXM communications.
2 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1
content creation device
CCD
device enabling the creation of content
NOTE Content can include audio-visual resources, rights information, metadata, etc.
2.2
content identification device
CID
device providing content identification and authentication services to another device
© ISO/IEC 2011 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 23006-1:2011(E)
2.3
content provider device
CPD
device on which content may be stored and which delivers content to another device
2.4
content search device
CSD
device providing responses to queries made by other devices about content items satisfying some criteria
2.5
device
combination of hardware and software or just an instance of software that allows a user to perform actions
2.6
domain
set of devices sharing a set of common properties such as ownership
2.7
domain management device
DMD
device managing the lifecycle of a domain and the membership of devices and users that are part of it
2.8
Event Report
representation of an Event(s) as specified by the related Event Report Request
[ISO/IEC 21000-15]
2.9
event report collection device
ECD
device collecting Event Reports generated by other devices
2.10
Inter-MXM Protocol
protocol that enables communication between MXM Devices
2.11
IPMP Tool
module performing one or more IPMP functions such as authentication, decryption, watermarking, etc.
2.12
IPMP Tool Body
executable code implementing an IPMP Tool
2.13
IPMP Tool provider device
ITD
device delivering IPMP Tools to another device
2.14
licence provider device
LPD
device delivering licences to another device according to a previously stored Licence Template
2.15
Licence Template
licence granting rights to issue licences to a device
2 © ISO/IEC 2011 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 23006-1:2011(E)
2.16
MXM Application
application that runs on an MXM Device and makes calls to the MXM Application API and MXM Engine APIs
2.17
MXM Device
device equipped with a selected assembly of MXM Engines
2.18
MXM Engine
collection of specific technologies that it is meaningful to bundle together
2.19
MXM Engine API
API of a single MXM Engine
2.20
MXM Orchestrator API
API of the MXM Orchestrator Engine
2.21
MXM Orchestrator Engine
special MXM Engine capable of creating chains of MXM Engines, i.e. to set up a sequence of connected MXM
Engines for the purpose of executing a high-level application call such as play
2.22
MXM Technology
technology that is supported by (a profile of) MXM
2.23
user
any entity making use of an MXM Device
3 Abbreviated terms
BBL Bitstream Binding Language
DIA Digital Item Adaptation
DID Digital Item Declaration
DIDL Digital Item Declaration Language
DII Digital Item Identification
DIS Digital Item Streaming
ER Event Report
ERR Event Report Request
IPMP Intellectual Property Management and Protection
MSAF Media Streaming Application Format (ISO/IEC 23000-5)
REL Rights Expression Language
URI Uniform Resource Identifier
© ISO/IEC 2011 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 23006-1:2011(E)
4 System overview
4.1 Introduction
The MPEG extensible Middleware is an architecture containing MPEG standard multimedia technologies
whose purpose is to enable the easy design and implementation of media-handling value chains whose
devices interoperate because they are all based on the same set of technologies exposed through standard
APIs.
4.2 MXM Device
An MXM Device is a combination of hardware and software or just an instance of software implementing this
International Standard.
Figure 1 depicts an MXM Device.
Figure 1 — An MXM Device
4.3 MXM Architecture
The elements of the MXM Architecture are
a) MXM Engines, collections of specific technologies that it is meaningful to bundle together
b) MXM Engine APIs, APIs that can be used to access MXM Engine functionality
c) Orchestrator Engine, a special MXM Engine capable of creating chains of MXM Engines to execute a
high-level application call such as “Play”
d) MXM Application API, the API of the MXM Orchestrator Engine
e) MXM Device, a device equipped with MXM
f) MXM Application, an application that runs on an MXM Device and makes calls to the MXM Application
API and MXM Engine APIs
Figure 2 shows a general model of an MXM device
4 © ISO/IEC 2011 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 23006-1:2011(E)
Figure 2 — The MXM architecture
As shown in Figure 2 above, MXM comprises a framework hosting a number of Engines. These are
containers of a specific set of MXM Technologies accessible by the MXM API specific of that Engine. As is
typical of most MPEG standards, the MXM standard will only define the interfaces of the MXM Engines,
named MXM Engine APIs and the MXM Orchestrator API.
In general an MXM Device can have several MXM Applications running on it (there may be other applications
but these are not relevant here). Some may be “resident”, i.e. they have been loaded by the MXM
manufacturer and some may be temporary, i.e. they have been downloaded for a specific purpose.
When an MXM Application is executed, there may be “low-level” calls directly to some MXM Engines using the
MXM Engine APIs of each specific Engines, and “high-level” calls like, say, “Play (GovernedContent)” which
will be handled by the Orchestrator Engine. The MXM Orchestrator, by calling the MXM Engine APIs of
specific engines, is capable of setting up a chain of MXM engines for handling complex operations,
orchestrating the intervention and send/receive data to/from the particular chain of Engines that a given high-
level call will trigger, thus relieving MXM Applications from the logic of handling them. Each MXM Engine will
contain a specific set of MXM Technologies accessible by an MXM Application, the MXM Orchestrator and
any other MXM Component in MXM, by means of its own MXM Engine API.
For instance, in the case of “Play (GovernedContent)” the Orchestrator engine could set-up the following
chain:
a) MP21 File engine (e.g. open the file and extract the Digital item);
b) DI engine (e.g. extract metadata and rights information);
c) REL engine (e.g. verify if the right to play is granted);
d) IPMP engine (e.g. set up IPMP Tools to decrypt protected resources);
e) Security engine (e.g. initialise the IPMP Tools with decryption keys);
f) Content Metadata engine (e.g. present content metadata to the user);
g) Media Framework engine (e.g. demux, decode and render audio-visual resources).
... and possibly others.
© ISO/IEC 2011 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 23006-1:2011(E)
NOTE Only the APIs of an MXM Engine are mandatory; how each Engine handles the operations needed to carry
out a request is dependent on the specific software or hardware MXM Engine implementation.
A specific MXM Device may also make use of the M3W standard [31] because this offers several technologies
from its parts 2 to 8, such as Resource and Quality Management, Fault Management and System Integrity
Management, that may be useful in an implementation.
MXM Devices are not only used as stand-alone devices possibly interacting with a server, but are also
devices meant to be used in a media value chain possibly with different MXM Applications that correspond to
the different roles that value chains users play in the value cha
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.