ISO/IEC 29116-1:2008
(Main)Information technology — Supplemental media technologies — Part 1: Media streaming application format protocols
Information technology — Supplemental media technologies — Part 1: Media streaming application format protocols
ISO/IEC 29116-1:2008 specifies a set of protocols to be used in conjunction with ISO/IEC 23000-5, in applications where governed audio and video information is streamed to an end-user device, named the Media Streaming Player. Media Streaming Players can interact with a number of Media Streaming Devices: Content Provider Device, a device capable of interacting with a Media Streaming Player to provide content; Licence Provider Device, a device capable of interacting with a Media Streaming Player to provide licences; IPMP Tool Provider Device, a device capable of interacting with a Media Streaming Player to provide IPMP Tools, i.e. modules performing one or more functions such as encryption, watermarking, etc.; Domain Management Device, a device capable of managing various functions needed for a proper functioning of a domain. Two types of protocols are the target of ISO/IEC 29116-1:2008: the Access Protocols and the Domain Management Protocols. The Access Protocols specify how a Media Streaming Player can obtain from another Media Streaming Device the following information: a content item or any of its parts, either streamed to an end-user device by means of existing protocols such as MPEG-2 Transport Stream or Real Time Protocol over Internet Protocol (RTP/IP) or stored in an MPEG-21 file; a licence, which can grant the Media Streaming Player or its user(s) some rights over a content item or any of its parts, possibly under some conditions; executable code implementing security functions The Domain Management Protocols specify how a number of devices and/or users can be grouped in a domain, groups of devices or users sharing some common properties. By using domains it becomes possible to implement more flexible licensing modalities, e.g. to license content to all devices or users in a domain. Domain Management Protocols include the specification of technologies for achieving the following goals: creating, renewing or deleting a domain; issuing domain membership licences for devices and users; managing devices and users memberships of a domain, i.e. joining, renewing and leaving a domain; verifying that domain-bound content has been used within the domain according to licence terms.
Technologies de l'information — Technologies de milieux supplémentaires — Partie 1: Protocoles de format d'application de diffusion de milieux
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 29116-1
First edition
2008-06-01
Information technology — Supplemental
media technologies —
Part 1:
Media streaming application format
protocols
Technologies de l'information — Technologies de milieux
supplémentaires —
Partie 1: Protocoles de format d'application de diffusion de milieux
Reference number
ISO/IEC 29116-1:2008(E)
©
ISO/IEC 2008
---------------------- Page: 1 ----------------------
ISO/IEC 29116-1:2008(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 2008
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 2008 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 29116-1:2008(E)
Contents Page
Foreword. iv
Introduction . v
1 Scope . 1
2 Normative references . 1
3 Terms and definitions. 1
4 Abbreviated terms . 2
5 Namespace conventions. 3
6 System overview. 4
7 Access Protocols. 4
7.1 Introduction . 4
7.2 Base Protocol Representation . 4
7.3 Access Protocols Representation specification . 6
7.4 Access Protocol specification. 10
8 Domain management protocols . 13
8.1 Introduction . 13
8.2 Domain management overview. 13
8.3 Domain Information specification. 14
8.4 Domain Use Data specification . 18
8.5 Domain Protocol Information specification . 19
8.6 Domain Management Protocols specification. 27
8.7 Simultaneous Content Usage Detection protocol specification. 32
Annex A (informative) Protocol Description Schemas. 35
A.1 Base Protocol Representation schema. 35
A.2 Domain Information Representation schema . 36
A.3 Domain Protocol Information Representation schema . 38
A.4 Access Protocols Representation schema. 43
Bibliography . 47
© ISO/IEC 2008 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 29116-1:2008(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 29116-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 29116 consists of the following parts, under the general title Information technology — Supplemental
media technologies:
⎯ Part 1: Media streaming application format protocols
iv © ISO/IEC 2008 – All rights reserved
---------------------- Page: 4 ----------------------
ISO/IEC 29116-1:2008(E)
Introduction
ISO/IEC 29116 is a family of International Standards that has been developed for the purpose of providing the
complete line-up of standards that are required to practically deploy Multimedia Application Format standards.
The parts of ISO/IEC 29116 have been developed starting from submissions received by proponents. The
proposed technologies have been thoroughly reviewed prior to submission of the Committee Draft and have
undergone the full national body review during the process of balloting the Draft International Standards.
© ISO/IEC 2008 – All rights reserved v
---------------------- Page: 5 ----------------------
INTERNATIONAL STANDARD ISO/IEC 29116-1:2008(E)
Information technology — Supplemental media technologies —
Part 1:
Media streaming application format protocols
1 Scope
This International Standard specifies a set of protocols to be used in conjunction with ISO/IEC 23000-5 (Media
streaming Player) in applications where governed audio and video information is streamed to an end-user
device.
This International Standard specifies two types of protocols,
⎯ Access Protocols, allowing a device to obtain from another device a content item or parts thereof, a
license, or executable code implementing security functions, and
⎯ Domain Management Protocols, allowing a number of devices to create, join, administer, etc. a group of
users and devices where the participants share common properties.
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 23000-5, Information technology — Multimedia application format (MPEG-A) — Part 5: Media
streaming application format
3 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1
Content Provider Device
device delivering content to another device
3.2
Device
combination of hardware and software or just an instance of software that allows a user to perform actions
3.3
Domain Administrator
user creating and administering a domain by means of a Domain Management Device
3.4
Domain Management Device
device managing the lifecycle of a domain and the membership of devices and users part of it.
© ISO/IEC 2008 – All rights reserved 1
---------------------- Page: 6 ----------------------
ISO/IEC 29116-1:2008(E)
3.5
IPMP Processor
module in a Media Streaming Player in charge of retrieving, instantiating, initialising and managing the IPMP
Tools required to perform actions on content.
3.6
IPMP Tool
module performing (one or more) IPMP functions such as authentication, decryption, watermarking, etc.
3.7
IPMP Tool Agent
module instantiating, initialising, authenticating, and supervising any operation performed between IPMP
Tools within an IPMP Tool Group
3.8
IPMP Tool Body
executable code implementing either a Single IPMP Tool or an IPMP Tool Pack
3.9
IPMP Tool Group
combination of several IPMP Tools
3.10
IPMP Tool Pack
module that comprises an IPMP Tool Group and its IPMP Tool Agent
3.11
IPMP Tool Provider Device
device delivering IPMP Tools to another device
3.12
Licence Provider Device
device delivering licenses to another device
3.13
User
any identified entity interacting in a media streaming environment using a media streaming device.
4 Abbreviated terms
For the purposes of this document, the following abbreviated terms apply.
CPD Content Provider Device
DID Digital Item Declaration
DIDL Digital Item Declaration Language
DII Digital Item Identification
DMD Domain Management Device
IPMP Intellectual Property Management and Protection
LPD License Provider Device
LLAP Local License Access Protocol
2 © ISO/IEC 2008 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 29116-1:2008(E)
MSD Media Streaming Device
MSP Media Streaming Player
RCAP Remote Content Access Protocol
RLAP Remote License Access Protocol
URI Uniform Resource Identifier
5 Namespace conventions
Throughout this part of ISO/IEC 29116, 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 29116, consistent namespace prefixes are used. Table 1 gives
these prefixes and the corresponding namespace.
Table 1 — Namespaces and prefixes
Prefix Corresponding namespace
ipmpdidl urn:mpeg:mpeg21:2004:01-IPMPDIDL-NS
ipmpmsg urn:mpeg:mpeg21:2006:07-IPMPMESSAGES-NS
ipmpinfo urn:mpeg:mpeg21:2004:01-IPMPINFO-NS
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
r urn:mpeg:mpeg21:2003:01-REL-R-NS
sx urn:mpeg:mpeg21:2003:01-REL-SX-NS
m1x urn:mpeg:mpeg21:2005:01-REL-M1X-NS
xsd http://www.w3.org/2001/XMLSchema
xsi http://www.w3.org/2001/XMLSchema-instance
dsig http://www.w3.org/2000/09/xmldsig#
msap urn:mpeg:maf:schema:mediastreaming:accessprotocol:2007
msd urn:mpeg:maf:schema:mediastreaming:domain:2007
msdp urn:mpeg:maf:schema:mediastreaming:domainprotocol:2007
msbp urn:mpeg:maf:schema:mediastreaming:baseprotocol:2007
© ISO/IEC 2008 – All rights reserved 3
---------------------- Page: 8 ----------------------
ISO/IEC 29116-1:2008(E)
6 System overview
ISO/IEC 29116-1 specifies the format of the data exchanged between a Media Streaming Player and other
Media Streaming Devices, namely:
a. Content Provider Device, a device capable of interacting with a Media Streaming Player to provide Media
Streaming Content
b. Licence Provider Device, a device capable of interacting with a Media Streaming Player to provide
Licences
c. IPMP Tool Provider Device, a device capable of interacting with a Media Streaming Player to provide
1)
IPMP Tools
d. Domain Management Device, a device capable of managing various functions needed for a proper
functioning of a domain.
7 Access Protocols
7.1 Introduction
This section specifies the messages exchanged between devices when communicating with the purpose of
obtaining from another device:
Content
A license
An IPMP Tool Body
7.2 Base Protocol Representation
This section specifies the base information commonly used in both the access protocols and the domain
management protocols.The namespace msbp defines the elements on which the access protocols and the
domain protocols are based.
7.2.1 ProtocolBaseType
The msbp:ProtocolBaseType abstract complex type is defined in the figure below. All the complex types
defined in this standard extends msbp:ProtocolBaseType.
Figure 1 — The msbp:ProtocolBaseType complex type
7.2.2 ProtocolType
The abstract msbp:ProtocolType complex type, defined in the figure below, extends the
msbp:ProtocolBaseType for conveying the msbp:TransactionID element which conveys a value which is used
to track a message exchange session. Any message in response to another message shall specify the same
TransactionID value contained in the request.
Figure 2 — The msbp:ProtocolType complex type
1) Related terms include: IPMP Processor, IPMP Tool Agent, IPMP Tool Group, IPMP Tool Pack.
4 © ISO/IEC 2008 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 29116-1:2008(E)
7.2.3 Ack
The msbp:Ack element defined in the figure below extends the msbp:ProtocolType complex type by specifying
a boolean attribute, Result, which shall indicate whether the protocol was carried out with success or
otherwise, and the msbp:ProtocolResult element, that may convey further information concerning the result of
an operation.
Figure 3 — The msbp:Ack element
7.2.4 ProtocolResult
The ProtocolResult element may convey either one of the codes specified in Table 2, of a user-defined result
code. Furthermore, the DisplayString element may convey a string to be shown to a user as the result of the
operation.
Figure 4 — The msbp:ProtocolResult element
A list of result codes is given in the table below.
© ISO/IEC 2008 – All rights reserved 5
---------------------- Page: 10 ----------------------
ISO/IEC 29116-1:2008(E)
Table 2 — List of Result Code
Result Code Description
"00" RESERVED
"01" OK
"02" UNKNOWN_MESSAGE
"03" TIMEOUT
"04" UNABLE_TO_PROCESS
"05" UNKNOWN_FAILURE
"06" PERMISSION_DENIED
"07" BUSY
7.3 Access Protocols Representation specification
7.3.1 Introduction
The namespace identified by the prefix msap, indicates protocols to access content, licenses and keys.
7.3.2 AccessProtocolType
The msap:AccessProtocolType complex type, defined in the figure below, extends the msbp:ProtocolType.
Figure 5 — The msap: ProtocolType complex type
7.3.3 Ack
The msap:Ack element defined in the figure below extends the msap:AccessProtocolType complex type by
specifying a boolean attribute, Result, indicating whether the protocol was carried out with success or
otherwise, and the msbp:ProtocolResult element, that may convey further information concerning the result of
an operation.
Figure 6 — The msap:Ack element
6 © ISO/IEC 2008 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 29116-1:2008(E)
7.3.4 RequestContent
A device sends a Request Content message (specified in the figure below) to the content provider device in
order to access content.
type="msap:ContentIdentifierType"/>
type="dia:UsageEnvironmentType" minOccurs="0"/>
minOccurs="0"/>
Figure 7 — The msap:RequestContent element
The msap:RequestContent message conveys the following information:
• msap:ContentIdentifier: the identifier of the requested content item or content element within a content
item, as defined in the figure below
• msap:MimeType: the Mime Type of the content being requested. The following values are permitted:
o application/mp21 – the MPEG-21 file is requested
o application/xml – the digital item representing the content item or content element identified in
msap:ContentIdentifier is requested
o the mime type of the resource identified in msap:ContentIdentifier
• r:license: an optional license specifying additional information about the requested license needed to
access the requested content
• msap:UsageEnvironmentDescription: Tool for describing the usage environment. Each
UsageEnvironmentProperty child element describes a property of the usage environment, such as
User characteristics, or terminal capabilities, or network characteristics, or natural environment
characteristics
• dsig:Signature: an optional digital signature of the msap:RequestContent message by the device
The ContentIdentifierType complex type specified in the figure below conveys the identifier of a content item
and optionally the identifier of a content element within the content item. In the case the
msap:ContentElementIdentifier element is specified in an msap:RequestContent message, this implies that
only the specific content element is requested, and not the whole content item.
minOccurs="0"/>
Figure 8 — The msap:ContentIdentifierType complex type
© ISO/IEC 2008 – All rights reserved 7
---------------------- Page: 12 ----------------------
ISO/IEC 29116-1:2008(E)
7.3.5 RequestContentResponse
The RequestContentResponse message, sent in response to a RequestContent message, is specified in the
figure below.
maxOccurs="unbounded"/>
Figure 9 — The msap:RequestContentResponse element
The msap:RequestContentResponse message is employed by the Content Provider Device to deliver the
following information:
• msap:DI: the optional digital item representing the content item being requested
• msap:ContentURL: an optional sequence of elements (whose syntax is specified in the figure below)
specifying the URLs from where the requested resource and any associated metadata can be
obtained
• dsig:Signature: an optional digital signature applied to the message
7.3.6 ContentURL
If the target of a RequestContent message is a content element part of a content item, depending on the
nature of the content element being requested, a number of resources may be made available to the
requesting party. The ContentURL complex type allows signalling the mime type of each resource and the
URL from which each resource is available. As an example, if the content element being requested consists of
a media resource (e.g. an audio elementary stream) and associated metadata, two separate
msap:ContentURL elements shall be returned in the msap:RequestContentResponse, one indicating the URL
for the audio elementary stream and the other the URL for the metadata elementary stream.
The msap:ContentURLType complex type is specified in the figure below.
Figure 10 — The msap:RequestContentResponse element
8 © ISO/IEC 2008 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 29116-1:2008(E)
7.3.7 Request License
The msap:RequestLicense specified in the figure below is sent by a device to a License Provider Device in
order to request a license granting the device or the user of the device one or more rights over a content item
or a content element part of a content item. The msap:RequestLicense message allows requesting a license
for either a content item or content element, or a license having a specific license identifier.
type="msap:ContentIdentifierType"/>
Figure 11 — The msap:RequestLicense element
The semantics for the msap:RequestLicense message is given below:
• msap:ContentIdentifier: the identifier of the governed asset for which a license is requested
• msap:LicenseID : The identifier of the license being requested
• r:license: an optional license specifying the principal(s), the right(s), the resource(s) and the
condition(s) that the requesting party would like to be specified in the license being requested.
• dsig:Signature: an optional digital Signature of the msap:RequestLicense message.
7.3.8 RequestLicenseResponse
The msap:RequestLicenseResponse message, sent in response to an msap:RequestLicense message, is
specified in the figure below.
Figure 12 — The msap:RequestLicenseResponse element
The msap:RequestLicenseResult element is employed by the License Provider to deliver a license, which
shall be included in the r:license element. Shall this message be signed, the digital signature shall be included
in the dsig:Signature element.
© ISO/IEC 2008 – All rights reserved 9
---------------------- Page: 14 ----------------------
ISO/IEC 29116-1:2008(E)
7.3.9 RequestIPMPToolBody
The msap:RequestIPMPToolBody message, specified in the figure below, is employed by a device to request
an IPMP Tool Body to an IPMP Tool Provider Device.
Figure 13 — The msap:RequestIPMPToolBody element
The msap:RequestIPMPToolBody element conveys the following information:
• ipmpinfo:IPMPToolID: the identifier of the IPMP Tool whose IPMP Tool Body is requested
• ipmpinfo-msx:DeviceInformation: information about the hardware and/or software characteristics of
the device on which the requested IPMP Tool Body shall operate.
7.3.10 RequestIPMPToolBodyResponse
The msap:RequestIPMPToolBodyResponse message, sent in response to an msap:RequestIPMPToolBody
message, is specified in the figure below.
type="msap:RequestIPMPToolBodyResponseType"/>
Figure 14 — The msap:RequestIPMPToolBodyResponse element
The msap:RequestIPMPToolBodyResponse element is employed by an IPMP Tool Provider Device to deliver
an IPMP Tool Body. This message may contain one or more Tool Body elements conveyed within the element
ipmpinfo-msx:ToolBody, or may specify a number of remote locations from where the Tool Body elements can
be obtained.
7.4 Access Protocol specification
This section specifies how to employ the messages defined in 7.3 to request content items or parts thereof,
licenses and IPMP Tool Bodies. The messages exchanged between two devices are based on a transactional
protocol called Remote Access Protocol (RAP) that is supported over an existing network protocol (TCP/IP or
HTTP in the case of Internet/WWW access). In terms of security, the RAP uses two security layers:
• Application-Level: this corresponds to the messages described in the RAP in this document;
• Network-Level: this is represented by an underlying security protocol, i.e. the SSLv3/TLSv1 protocol.
10 © ISO/IEC 2008 – All rights reserved
---------------------- Page: 15 ----------------------
ISO/IEC 29116-1:2008(E)
Server Component Server Component
Application
Application Application
Level Security
SOAP SOAP
HTTP HTTP
Communication
SSL/TLS SSL/TLS
Level Security
TCP/IP TC
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.