ISO/IEC 21000-4:2006/Amd 1:2007
(Amendment)Information technology — Multimedia framework (MPEG-21) — Part 4: Intellectual Property Management and Protection Components — Amendment 1: IPMP components base profile
Information technology — Multimedia framework (MPEG-21) — Part 4: Intellectual Property Management and Protection Components — Amendment 1: IPMP components base profile
Technologies de l'information — Cadre multimédia (MPEG-21) — Partie 4: Composants de gestion et de protection de propriété intellectuelle — Amendement 1: Profil de base des composants GPPI
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO/IEC
STANDARD 21000-4
First edition
2006-04-01
AMENDMENT 1
2007-12-01
Information technology — Multimedia
framework (MPEG-21) —
Part 4:
Intellectual Property Management and
Protection Components
AMENDMENT 1: IPMP components base
profile
Technologies de l'information — Cadre multimédia (MPEG-21) —
Partie 4: Composants de gestion et de protection de propriété
intellectuelle
AMENDEMENT 1: Profil de base des composants GPPI
Reference number
ISO/IEC 21000-4:2006/Amd.1:2007(E)
©
ISO/IEC 2007
---------------------- Page: 1 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(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 2007
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 2007 – All rights reserved
---------------------- Page: 2 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(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.
Amendment 1 to ISO/IEC 21000-4:2006 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 2007 – All rights reserved iii
---------------------- Page: 3 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
Information technology — Multimedia framework (MPEG-21) —
Part 4:
Intellectual Property Management and Protection Components
AMENDMENT 1: IPMP components base profile
Add Clause 9:
9 Base Profile
9.2 Introduction
ISO/IEC 21000-4 Intellectual Property Management and Protection (IPMP) Components addresses the need
for effective management and protection of intellectual property in the ISO/IEC 21000 MPEG-21 multimedia
framework over heterogeneous access and delivery infrastructures. It represents a flexible and extensible
framework for applying protection mechanisms to a Digital Item (DI). It purposely does not specify protection
measures, keys, key management, trust management, encryption algorithms, certification infrastructures or
other components. In its current form, the specification is designed to be applicable to a wide range of
application areas [14][15].
Similarly to previously developed MPEG standards, we believe the utility of this part of ISO/IEC 21000 can be
enhanced by the careful identification and development of specific profiles supporting functionality relevant to
various user communities. Base Profile specifically aims at supporting use cases in widespread use in the
area of commercial content distribution. Base Profile purposely provides a limited scope in order to facilitate
the easier and lighter implementation in devices with limited computational/storage capabilities.
9.2 Application Areas
Base Profile provides sufficient functionality to support current and emerging practices for distribution of
commercial content, with a special focus on entertainment content such as movies and music, while reducing
the requirements on end devices (e.g. footprint, memory usage, computational power, storage). To this end,
Base Profile will provide suitable protection capability for the simple applications such as music player
application, video player, music player with karaoke capability, etc.
9.3 List of Tools
9.3.1 Requirements
Based on use-cases listed in Annex M and the capabilities in the MPEG-21 IPMP Components, the following
is a list of detail required capabilities that shall be supported in Base Profile. These requirements later can be
translated into some guidelines of rationale when selecting supported elements out of the complete set of
MPEG-21 IPMP Components’ elements.
© ISO/IEC 2007 – All rights reserved 1
---------------------- Page: 4 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
One important corollary derived from the use cases is that typically protection mechanisms are not applied
independently, but rather a single mechanism (most likely incorporating several techniques, such as
encryption, key management, digital signatures and/or watermarking, and with associated non-technical
compliance enforcement methods) is used as an indivisible component. With this in mind, Base Profile can be
greatly simplified by assuming that a single Tool will be used for any given DI. Nonetheless, Base Profile
should allow for the same Tool to be applied multiple times within the same DI (e.g. to protect different
resources) and for different Licenses to be applied to different elements.
Another important result from the use cases is that it is not necessary to support multiple levels of Signature.
The use cases show that the user who assembles the DI also applies the protection. Therefore, digital
signature on a parent element in the DI is sufficient to ensure integrity of its children. A related result is that
the type of protection that is most likely to be applied to a License is a digital signature to ensure the integrity
of the License, i.e. that it has not been tampered with. Therefore, it is not necessary in Base Profile to be able
to signal governance of a License, beyond the capability of signing the parent element. Note that MPEG-21
IPMP Components is capable of supporting more flexible configurations, e.g. where the License is signed (or
otherwise “governed”) by one party, the Tool is signed by another party and the DI is assembled by yet
another party, which is not in scope for Base Profile.
Finally, in order to facilitate processing of these Digital Items in resource-constrained terminals (such as
portable devices with limited memory, processing power, connectivity and power consumption), Base Profile
limits the ability to specify Tools to either an ID or a reference to the location where the Tool can be
downloaded. (Note that this excludes the ability to specify Tools inline, which is consistent with the
assumptions that, in general, Tools will be relatively complex.) An ID can be used by the terminal to determine
if that capability is already supported. Loading of Tools specified through a reference is assumed to be
through an out-of-band mechanism.
9.3.2 Selection Rationale
Base Profile restricts the occurrence of some elements from the complete MPEG-21 IPMP Components’
elements. The guidelines for the restrictions are as follow:
1. Base Profile is designed to maintain the capability to express the protected Digital Item.
2. Base Profile is designed to reduce the requirement on end devices (e.g. device footprint, memory
usage, computational power, storage); thus, the following properties are restricted:
a. Base Profile is designed to carry one protection tool in one document.
b. Base Profile is designed to have no recursion. Recursion may consume more memory and
computing power. Having recursion capability while carrying only one tool is redundant as
protecting a single resource with same tool many times gives no additional protection effect.
c. Base Profile is designed to have no duplication of elements in many locations. For elements that
can be inserted in different locations, a suitable place among the current existing ones should be
chosen to ease the implementation while not sacrificing the feature(s) offered by that element.
3. For simplicity, tool is assumed to be ready for use in the terminal. The procedure to acquire and/or
install the tool in the terminal is out of scope of Base Profile.
4. Base Profile is designed to be simple for transfer. This requires the XML instance of Base Profile
should be as small and compact as possible. For example, rather than being able to carry the tool
binary representation in the XML document (with base64 encoding format), it is better to just carry
reference to it.
9.3.3 IPMP DIDL
Base Profile maintains the full capability to express the protected DI (guideline no. 1); therefore, it shall include
all the elements in the IPMP Digital Item Declaration Language (DIDL) schema. These elements taken
together are a Representation of the Digital Item Declaration (DID) model that allows for inclusion of
governance information (per guideline 1 in subclause 9.3.2).
2 © ISO/IEC 2007 – All rights reserved
---------------------- Page: 5 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
9.3.4 IPMP General Information Descriptor
Base Profile shall include the root element IPMPGeneralInfoDescriptor as defined in Clause 8. It shall:
⎯ Include ToolList element
⎯ Optionally include LicenseCollection element. It may contain any number of RightsDescriptor
elements (in case there are multiple assets in the digital item), although in most instances a single
RightsDescriptor element is likely to be used. The RightsDescriptor in Base Profile excludes the
possibility of having an IPMPInfoDescriptor child (per guideline 2.b)
⎯ Optionally include Signature element. If present, it is sufficient to ensure the integrity of the children
elements.
The ToolList element shall:
⎯ Include at most one instance of ToolDescription (per guideline 2.a). Note that Tools to be used in
IPMPInfoDescriptor can only reference elements in ToolList; this ensures that only a single Tool can
be defined for any given DI.
⎯ Provide no support for Signature (per guideline 2.c).
The ToolDescription element shall:
⎯ Include IPMPToolID element
⎯ Optionally include Remote element but without Signature element (per guideline 2.c)
⎯ Provide no support of MemberOf element and its children (per guideline 2.a)
⎯ Provide no support for Inline tool definition (per guideline 4)
⎯ Provide no support for ConfigurationSettings (per guideline 3)
⎯ Provide no support for RightsDescriptor. RightsDescriptor elements are carried all together under the
LicenseCollection element (per guideline 2.c)
⎯ Provide no support for Signature (per guideline 2.c)
9.3.5 IPMP Information Descriptor
Base Profile shall include the root element IPMPInfoDescriptor but with the following constraints:
⎯ Support for (at most) a single Tool
⎯ No support for RightsDescriptor (no need to specify governance over the Tool itself). The
RightsDescriptor elements are collected and expressed under the LicenseCollection element (per
guideline 2.c)
⎯ The element dsig:Signature remains optional.
The Tool element shall have the following constraint:
⎯ No attributes are needed. Since there is at most one Tool, order is no longer relevant (per
guideline 2b).
⎯ No support for ToolBaseDescription. All tool definition is carried in the ToolList while the Tool
element will only refer to it (per guideline 2.c)
© ISO/IEC 2007 – All rights reserved 3
---------------------- Page: 6 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
⎯ Include a ToolRef element (per guideline 2.c)
⎯ Optionally support the InitializationSettings element. However, there will be no support for
ToolBaseDescription (no recursion per guideline 2.b). The only supported child element shall be
InitializationData.
⎯ No support for RightsDescriptor (per guideline 2.c)
⎯ No support for Signature (per guideline 2.c)
9.4 Profile Definition
9.4.1 Namespaces
Throughout this document, 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 document, consistent namespace prefixes are used. Table 2 gives these prefixes
and the corresponding namespace.
Table 2 — Mapping of prefixes to namespaces in examples and text
Prefix Name Corresponding namespace
ipmpdidl IPMP DIDL urn:mpeg:mpeg21:2004:01-IPMPDIDL-NS
ipmpinfo IPMP Information urn:mpeg:mpeg21:2004:01-IPMPINFO-NS
didl DIDL urn:mpeg:mpeg21:2002:02-DIDL-NS
didmodel DIDL Model urn:mpeg:mpeg21:2002:02-DIDMODEL-NS
dii Digital Item urn:mpeg:mpeg21:2002:01-DII-NS
Identifier (DII)
r Rights Expression urn:mpeg:mpeg21:2003:01-REL-R-NS
Language (REL)
Core
xsd XMLSchema http://www.w3.org/2001/XMLSchema
xsi XMLSchema http://www.w3.org/2001/XMLSchema-instance
Instance
dsig XML digital http://www.w3.org/2000/09/xmldsig#
signature core
9.4.2 IPMP DIDL
IPMP DIDL is included as specified in clause 6 without any restrictions.
9.4.3 IPMP General Information Descriptor Representation
The subset of elements of the IPMP General Information Descriptor schema (see clause 8) and any
restrictions are listed in subclause 9.3.2.
Table 3 list the elements of IPMP General Information Descriptor of Base Profile.
4 © ISO/IEC 2007 – All rights reserved
---------------------- Page: 7 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
Table 3 — IPMP General Information Base Profile elements
Element/Child Element Restrictions
ipmpinfo:IPMPGeneralInfoDescriptor As defined in 8.3.1.
ipmpinfo:ToolList Identifies the IPMP Tool required to process and
unprotect the object. Restricted to contain a single
IPMP Tool.
ipmpinfo:LicenseCollection As defined in 8.5.
dsig:Signature As defined in 8.6.
ipmpinfo:ToolList An ipmpinfo:ToolList is restricted to include the
following child element: a single
ipmpinfo:ToolDescription
ipmpinfo:ToolDescription Restricted to at most one occurrence from
unbounded occurrences.
ipmpinfo:ToolDescription This element is restricted to include the following
child elements only: ipmpinfo:IPMPToolID, and an
optional ipmpinfo:Remote.
ipmpinfo:IPMPToolID As defined in 8.4.4.3.
ipmpinfo:Remote Contains the remote location from where the tool can
be retrieved.
@localID As defined in 8.4.4.1.
ipmpinfo:Remote This element is restricted to include no child
elements.
@ref As defined in 7.4.4.6.1.
ipmpinfo:RightsDescriptor This element is restricted to include the following
child elements only: one of ipmpinfo:License, or
ipmpinfo:LicenseReference.
ipmpinfo:License As defined in 7.4.7.3.
ipmpinfo:LicenseReference As defined in 7.4.7.4.
© ISO/IEC 2007 – All rights reserved 5
---------------------- Page: 8 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
Figure 3 presents a graphical overview of the profiled IPMP Information Descriptor schema elements.
Figure 3 — Base Profile IPMP General Information Descriptor elements
9.4.4 IPMP Information Descriptor Representation
The subset of elements of the IPMP Information Descriptor schema (see Clause 7) and any restrictions are
listed in subclause 9.3.2.
Table 4 list the elements of the IPMP Information Descriptor of Base Profile.
Table 4 — IPMP Information Base Profile elements
Element/Child Element Restrictions
ipmpinfo:IPMPInfoDescriptor An ipmpinfo:IPMPInfoDescriptor is restricted to
contain the following child elements: at most one
ipmpinfo:Tool, and an optional dsig:Signature.
ipmpinfo:Tool Restricted to at most one occurrence from
unbounded occurrences.
dsig:Signature As defined in 7.6.
ipmpinfo:Tool An ipmpinfo:Tool is restricted to include the following
child elements: an ipmpinfo:ToolRef, and an optional
ipmpinfo:InitializationSettings.
ipmpinfo:ToolRef As defined in 7.4.5.
ipmpinfo:InitializationSettings Detailed settings to initialize the tool.
ipmpinfo:InitializationSettings This element is restricted to include the following
child element only: ipmpinfo:InitializationData.
ipmpinfo:InitializationData As defined in 7.4.6.4.
6 © ISO/IEC 2007 – All rights reserved
---------------------- Page: 9 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
Figure 4 presents a graphical overview of the profiled IPMP Information Descriptor schema elements.
Figure 4 — Base Profile IPMP Information Descriptor elements
© ISO/IEC 2007 – All rights reserved 7
---------------------- Page: 10 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
Add Annex I:
Annex I
(normative)
IPMP DIDL Schema
The XML Schema for the profile elements and types of IPMP DIDL
attributeFormDefault="unqualified" version="0.01" xmlns="http://www.w3.org/2001/XMLSchema"
xmlns:didmodel="urn:mpeg:mpeg21:2002:02-DIDMODEL-NS" xmlns:ipmpdidl="urn:mpeg:mpeg21:2004:01-
IPMPDIDL-NS">
substitutionGroup="didmodel:Descriptor"/>
8 © ISO/IEC 2007 – All rights reserved
---------------------- Page: 11 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
substitutionGroup="didmodel:Annotation"/>
© ISO/IEC 2007 – All rights reserved 9
---------------------- Page: 12 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
10 © ISO/IEC 2007 – All rights reserved
---------------------- Page: 13 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
Add Annex J:
Annex J
(normative)
IPMP General Information Schema
The XML Schema for the profile elements and types of IPMP General Information
xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ipmpinfo="urn:mpeg:mpeg21:2004:01-IPMPINFO-NS"
xmlns:dii="urn:mpeg:mpeg21:2002:01-DII-NS" xmlns:r="urn:mpeg:mpeg21:2003:01-REL-R-NS"
xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" elementFormDefault="qualified"
attributeFormDefault="unqualified" version="0.01">
schemaLocation="http://www.w3.org/TR/2002/REC-xmldsig-core-20020212/xmldsig-core-schema.xsd"/>
© ISO/IEC 2007 – All rights reserved 11
---------------------- Page: 14 ----------------------
ISO/IEC 21000-4:2006/Amd.1:2007(E)
Add Annex K:
Annex K
(normative)
IPMP Information Schema
The XML Schema for the profile elements and types of IPMP Information
xmlns="http://www.w3.org/2001/XMLSchema" xmlns:ipmpinfo="urn:mpeg:mpeg21:2004:01-IPMPINFO-NS"
xmlns:dii="urn:mpeg:mpeg21:2002:01-DII-NS" xmlns:r="urn:mpeg:mpeg21:2003:01-REL-R-NS"
xmlns:dsig="http://www.w3.org/2000/09/xmldsig#" elementFormDefault="qualified"
attributeFormDefault="unqualified" version="0.01">
schemaLocation="http://ww
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.