ISO/IEC 23006-4:2010
(Main)Information technology — MPEG extensible middleware (MXM) — Part 4: MXM protocols
Information technology — MPEG extensible middleware (MXM) — Part 4: MXM protocols
ISO/IEC 23006-4:2010 specifies a set of protocols enabling distributed applications to exchange information related to content items and parts thereof, including rights and protection information.
Technologies de l'information — Intergiciel MPEG extensible (MXM) — Partie 4: Protocoles MXM
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 23006-4
First edition
2010-12-01
Information technology — MPEG
extensible middleware (MXM) —
Part 4:
MXM protocols
Technologies de l'information — Intergiciel MPEG extensible (MXM) —
Partie 4: Protocoles MXM
Reference number
ISO/IEC 23006-4:2010(E)
©
ISO/IEC 2010
---------------------- Page: 1 ----------------------
ISO/IEC 23006-4:2010(E)
PDF disclaimer
This PDF file may contain embedded typefaces. In accordance with Adobe's licensing policy, this file may be printed or viewed but
shall not be edited unless the typefaces which are embedded are licensed to and installed on the computer performing the editing. In
downloading this file, parties accept therein the responsibility of not infringing Adobe's licensing policy. The ISO Central Secretariat
accepts no liability in this area.
Adobe is a trademark of Adobe Systems Incorporated.
Details of the software products used to create this PDF file can be found in the General Info relative to the file; the PDF-creation
parameters were optimized for printing. Every care has been taken to ensure that the file is suitable for use by ISO member bodies. In
the unlikely event that a problem relating to it is found, please inform the Central Secretariat at the address given below.
COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2010
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 2010 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 23006-4:2010(E)
Contents Page
Foreword .vi
Introduction.vii
1 Scope.1
2 Normative references.1
3 Terms and definitions .2
4 Abbreviated terms.2
5 Namespace conventions .2
6 System overview .3
7 Base Protocol .5
7.1 Introduction.5
7.2 Protocol data format .5
7.2.1 ProtocolBaseType.5
7.2.2 ProtocolType.5
7.2.3 Ack .5
7.2.4 ProtocolResult .6
7.2.5 ContentIdentifier.7
8 Content Protocols .8
8.1 Identify Content Protocol.8
8.1.1 Protocol specification.8
8.1.2 Protocol data format .9
8.2 Authenticate Content Protocol .12
8.2.1 Protocol specification.12
8.2.2 Protocol data format .13
8.3 Store Content Protocol .15
8.3.1 Protocol specification.15
8.3.2 Protocol data format .17
8.4 Access Content Protocol.26
8.4.1 Protocol specification.26
8.4.2 Protocol data format .26
9 License Protocols.29
9.1 Store License Protocol .29
9.1.1 Protocol specification.29
9.1.2 Protocol data format .29
9.2 Revoke License Protocol.31
9.2.1 Protocol specification.31
9.2.2 Protocol data format .31
9.3 Access License Protocol.32
9.3.1 Protocol specification.33
© ISO/IEC 2010 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 23006-4:2010(E)
9.3.2 Protocol data format. 33
10 IPMP Tool Protocols. 35
10.1 Access IPMP Tool Protocol . 35
10.1.1 Protocol specification . 35
10.1.2 Protocol data format. 36
10.2 Access IPMP Tool List Protocol. 37
10.2.1 Protocol specification . 37
10.2.2 Protocol data format. 38
11 Domain management protocols. 39
11.1 Introduction. 39
11.2 Domain management overview . 39
11.3 Domain Information specification. 40
11.3.1 Common elements defined in the mxmd namespace. 40
11.3.2 DomainBaseType. 41
11.3.3 IDType . 41
11.3.4 DomainManageInfo. 42
11.3.5 DACredentials and DomainMembershipCredentials . 42
11.3.6 DomainID . 42
11.3.7 User . 43
11.3.8 Device . 44
11.4 Domain Use Data specification . 44
11.4.1 UseData. 44
11.4.2 Record. 45
11.5 Domain Protocol Information specification . 45
11.5.1 DomainProtocolType. 45
11.5.2 Ack . 45
11.5.3 AuthenticateReq . 46
11.5.4 LocalDomainIDRequest . 46
11.5.5 LocalDomainIDResponse . 46
11.5.6 RequestKey . 47
11.5.7 RequestKeyResponse. 47
11.5.8 AddDevice . 48
11.5.9 AddUser. 48
11.5.10 RenewDevice. 48
11.5.11 RenewUser . 49
11.5.12 AddDeviceResponse, AddUserResponse, RenewDeviceResponse and
RenewUserResponse . 49
11.5.13 LeaveDevice . 50
11.5.14 LeaveUser. 51
11.5.15 CreateDomain. 51
11.5.16 CreateDomainResponse . 52
11.5.17 RenewDomain . 52
iv © ISO/IEC 2010 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 23006-4:2010(E)
11.5.18 DeleteDomain.52
11.5.19 UnLicensedSimultaneousUseNotice.52
11.6 Domain Management Protocols specification .53
11.6.1 Introduction.53
11.6.2 Protocols between the Domain Administrator and the DMD.54
11.6.3 Protocol between the DMD and the LPD.55
11.6.4 Protocols between the device/User and the DMD.55
11.7 Simultaneous Content Usage Detection protocol specification .58
11.7.1 Introduction.58
11.7.2 Use Data .58
11.7.3 Merging Use Data between Devices.58
11.7.4 Un-Licensed Simultaneous Use.59
11.7.5 Notification to Domain Management Device .59
12 Event Reporting Protocols .60
12.1 Introduction.60
12.2 Protocols Specification.60
12.2.1 Register Event Report Request Protocol.60
12.2.2 Store Event Report.60
12.3 Protocol data format .61
12.3.1 EventReportingProtocolType.61
12.3.2 Ack .61
12.3.3 RegisterERR.62
12.3.4 SendER.62
Annex A (informative) Protocol Description Schemas .63
A.1 The MXM Base Protocol schema.63
A.2 The MXM Access Content Protocol schema .64
A.3 The MXM Access IPMP Tool Protocol schema .66
A.4 The MXM Access License Protocol schema .68
A.5 The MXM Authenticate Content Protocol schema .70
A.6 The MXM Domain schema .72
A.7 The MXM Domain Protocol schema .74
A.8 The MXM Identify Content Protocol schema .79
A.9 The MXM Revoke License Protocol schema .82
A.10 The MXM Store Content Protocol schema.83
A.11 The MXM Store License Protocol schema.88
A.12 The MXM Event Reporting Protocol schema.89
Bibliography.91
© ISO/IEC 2010 – All rights reserved v
---------------------- Page: 5 ----------------------
ISO/IEC 23006-4:2010(E)
Foreword
ISO (the International Organization for Standardization) and IEC (the International Electrotechnical
Commission) form the specialized system for worldwide standardization. National bodies that are members of
ISO or IEC participate in the development of International Standards through technical committees
established by the respective organization to deal with particular fields of technical activity. ISO and IEC
technical committees collaborate in fields of mutual interest. Other international organizations, governmental
and non-governmental, in liaison with ISO and IEC, also take part in the work. In the field of information
technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of the joint technical committee is to prepare International Standards. Draft International
Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as
an International Standard requires approval by at least 75 % of the national 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 and IEC shall not be held responsible for identifying any or all such patent rights.
ISO/IEC 23006-4 was prepared by Joint Technical Committee ISO/IEC JTC 1, Information technology,
Subcommittee SC 29, Coding of audio, picture, multimedia and hypermedia information.
This first edition of ISO/IEC 23006-4 cancels and replaces ISO/IEC 29116-1:2008.
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 conformance and reference software
⎯ Part 4: MXM protocols
vi © ISO/IEC 2010 – All rights reserved
---------------------- Page: 6 ----------------------
ISO/IEC 23006-4:2010(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 to implement media-handling value chains
whose devices interoperate because they are all based on the same set of technologies, especially
WG11 technologies.
© ISO/IEC 2010 – All rights reserved vii
---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO/IEC 23006-4:2010(E)
Information technology — MPEG extensible middleware
(MXM) —
Part 4:
MXM protocols
1 Scope
This part of ISO/IEC 23006 specifies a set of protocols enabling distributed applications to exchange
information related to content items and parts thereof, including rights and protection information.
This part of ISO/IEC 23006 specifies five categories of protocols: the content protocols, the license protocols,
the IPMP tool protocols, the domain protocols and the event report protocols. The first category includes
protocols to access, authenticate, identify and store a content item or parts thereof. The second includes
protocols to access and store a license from/to a remote service. The third category includes protocols to
access an IPMP tool (a module performing protection operations such as decryption, watermarking, key
management, etc.) from a remote service while a fourth category includes the protocols allowing a number of
devices to create, join, administer, etc. a group of users and devices where the participants share common
properties. The fifth category, event report, comprises the protocol to store an event report and the protocol to
register an event report request.
In security-aware environments, the security at the communication level is assumed to be handled by
traditional underlying security protocols, e.g. the SSLv3 or TLSv1 protocols. This part of ISO/IEC 23006 does
not apply to this level. Figure 1 shows the scope of the MXM protocols.
Server Component Server Component
Application
Application Application
Level Security
SOAP SOAP
HTTP HTTP
Communication
SSL/TLS SSL/TLS
Level Security
TCP/IP TCP/IP
Figure 1 — Scope of MXM protocols
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO/IEC 23006-1, Information technology — MPEG extensible middleware (MXM) — Part 1: MXM
architecture and technologies
© ISO/IEC 2010 – All rights reserved 1
---------------------- Page: 8 ----------------------
ISO/IEC 23006-4:2010(E)
3 Terms and definitions
For the purposes of this document, the terms and definitions given in ISO/IEC 23006-1 apply.
4 Abbreviated terms
DID Digital Item Declaration
DIDL Digital Item Declaration Language
DII Digital Item Identification
DMD Domain Management Device
DoID Domain Identification Device
IPMP Intellectual Property Management and Protection
URI Uniform Resource Identifier
5 Namespace conventions
Throughout this part of ISO/IEC 23006, Qualified Names are written with a namespace prefix followed by a
colon followed by the local part of the Qualified Name.
For clarity, throughout this part of ISO/IEC 23006, consistent namespace prefixes are used. Table 1 gives
these prefixes and the corresponding namespace.
Table 1 — Namespaces and prefixes
Prefix Corresponding namespace
didl urn:mpeg:mpeg21:2002:02-DIDL-NS
didmodel urn:mpeg:mpeg21:2002:02-DIDMODEL-NS
didl-msx urn:mpeg:maf:schema:mediastreaming:DIDLextensions
dii urn:mpeg:mpeg21:2002:01-DII-NS
dsig http://www.w3.org/2000/09/xmldsig#
ipmpdidl urn:mpeg:mpeg21:2004:01-IPMPDIDL-NS
ipmpmsg urn:mpeg:mpeg21:2006:07-IPMPMESSAGES-NS
ipmpinfo urn:mpeg:mpeg21:2004:01-IPMPINFO-NS
m1x urn:mpeg:mpeg21:2005:01-REL-M1X-NS
mxmacp urn:mpeg:mpeg-m:schema:accesscontentprotocol:2009
mxmaitp urn:mpeg:mpeg-m:schema:accessipmptoolprotocol:2009
mxmalp urn:mpeg:mpeg-m:schema:accesslicenseprotocol:2009
mxmaucp urn:mpeg:mpeg-m:schema:authenticatecontentprotocol:2009
mxmbp urn:mpeg:mpeg-m:schema:baseprotocol:2009
mxmd urn:mpeg:mpeg-m:schema:domain:2009
mxmdp urn:mpeg:mpeg-m:schema:domainprotocol:2009
2 © ISO/IEC 2010 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 23006-4:2010(E)
mxmicp urn:mpeg:mpeg-m:schema:identifycontentprotocol:2009
mxmrlp urn:mpeg:mpeg-m:schema:revokelicenseprotocol:2009
mxmscp urn:mpeg:mpeg-m:schema:storecontentprotocol:2009
mxmslp urn:mpeg:mpeg-m:schema:storelicenseprotocol:2009
r urn:mpeg:mpeg21:2003:01-REL-R-NS
sx urn:mpeg:mpeg21:2003:01-REL-SX-NS
xsd http://www.w3.org/2001/XMLSchema
xsi http://www.w3.org/2001/XMLSchema-instance
6 System overview
ISO/IEC 23006-1 specifies the format of the data exchanged between distributed applications part of media-
handling value chains as shown in the figure below.
Figure 2 — Typical devices in a media-handling value chain
The devices in Figure 1 are defined as following:
⎯ Content Creation Device, a device capable of creating content items possibly including audio-visual
resources, metadata, rights information, etc.
© ISO/IEC 2010 – All rights reserved 3
---------------------- Page: 10 ----------------------
ISO/IEC 23006-4:2010(E)
⎯ Content Provider Device, a device capable of storing content and in turn providing it to other devices (e.g.
via streaming, downloading, etc.).
⎯ License Provider Device, a device capable of being configured to issue licenses to other devices upon
request.
⎯ IPMP Tool Provider Device, a device capable of interacting with other devices to provide IPMP Tools.
⎯ Content Identification Device, a device capable of providing identifiers to new content items and parts
thereof, and allowing applications to verify the authenticity of the identified objects.
⎯ Domain Management Device, a device capable of managing various functions needed for a proper
functioning of a domain.
⎯ End-User Device, a device capable of accessing content, licenses and IPMP Tools from other devices,
authenticating content and becoming part of a domain of devices.
⎯ Event Report Collecting Device, a device capable of processing ER-R and issue ER.
⎯ Content Search Device, a device providing other devices with responses to queries.
The Protocols specified by this International Standard are identified in Figure 1 with a number representing the
following:
Table 2 — List of MXM Protocols
# Protocol name Purpose
a Identify Content Protocol to identify ontent items and elements thereof, as specified in 8.1
b Authenticate Content Protocol to authenticate content items and elements thereof, as specified in
8.2
c Store Content Protocol to store content items and elements thereof, as specified in 8.3
d Access Content Protocol to obtain content items and elements thereof, as specified in 8.4
e Store License Protocol to configure a license service to issue licenses, as specified in 9.1
f Access License Protocol to obtain licenses granting rights over content items and elements
thereof, as specified in 9.3
g Access IPMP Tool Protocol to obtain IPMP Tools necessary to access protected content, as
specified in 10.1
h Manage Domain Protocol to create, join, administer, etc. a group of users and devices, as
specified in 11
i Content Search Protocol to perform searches for content items having specific
characteristics, as specified in ISO/IEC 15938-12
j Store Event Report
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.