Multimedia home server systems - Conceptual model for domain management

IEC/TS 62579:2010(E) defines the conceptual model of domain management, which includes terms, requirements and reference models. The domain is a set of devices, users, and/or other entities which can share contents. Entities within a domain are allowed to play, copy and move content and usage rules to other entities within the same domain.
This publication contains colours which are considered to be useful for the correct understanding of its contents.

General Information

Status
Published
Publication Date
18-May-2010
Current Stage
PPUB - Publication issued
Start Date
31-Aug-2010
Completion Date
19-May-2010
Ref Project
Technical specification
IEC TS 62579:2010 - Multimedia home server systems - Conceptual model for domain management
English language
31 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


IEC/TS 62579 ®
Edition 1.0 2010-05
TECHNICAL
SPECIFICATION
colour
inside
Multimedia home server systems – Conceptual model for domain management

IEC/TS 62579:2010(E)
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 IEC or
IEC's member National Committee in the country of the requester.
If you have any questions about IEC copyright or have an enquiry about obtaining additional rights to this publication,
please contact the address below or your local IEC member National Committee for further information.

Droits de reproduction réservés. Sauf indication contraire, aucune partie de cette publication ne peut être reproduite
ni utilisée sous quelque forme que ce soit et par aucun procédé, électronique ou mécanique, y compris la photocopie
et les microfilms, sans l'accord écrit de la CEI ou du Comité national de la CEI du pays du demandeur.
Si vous avez des questions sur le copyright de la CEI ou si vous désirez obtenir des droits supplémentaires sur cette
publication, utilisez les coordonnées ci-après ou contactez le Comité national de la CEI de votre pays de résidence.

IEC Central Office
3, rue de Varembé
CH-1211 Geneva 20
Switzerland
Email: inmail@iec.ch
Web: www.iec.ch
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC/TS 62579 ®
Edition 1.0 2010-05
TECHNICAL
SPECIFICATION
colour
inside
Multimedia home server systems – Conceptual model for domain management

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
V
ICS 33.160; 35.240 ISBN 978-2-88910-932-6
– 2 – TS 62579 © IEC:2010(E)
CONTENTS
FOREWORD.4
INTRODUCTION.6
1 Scope.7
2 Terms, definitions and abbreviations .7
2.1 Terms and definitions .7
2.2 Abbreviations .9
3 Use cases .9
3.1 Purpose of description of use cases .9
3.2 Example 1: A domain in ARIB TR-B27.9
3.3 Example 2: A domain in DVB CPCM.10
3.4 Example 3: A domain in OMA DRM V2.0 .10
3.5 Example 4: A domain in permission code .11
3.6 Example 5: A common domain in Marlin DRM .12
4 Conceptual model.13
4.1 Definition of a domain.13
4.2 Forming a domain .13
4.3 Components of a device which can join a domain.14
4.4 Requirements.14
4.4.1 Abstract domain model .14
4.4.2 Information elements .16
4.4.3 Joining and leaving domains.16
4.4.4 Usage control by usage rules .17
4.4.5 Revocation of a device .18
4.4.6 Items gathered by content issuer .18
5 Reference models .18
5.1 General .18
5.2 Basic model .18
5.2.1 Overview of basic model.18
5.2.2 RI management domain model .18
5.2.3 Autonomous domain model.21
5.3 Enhanced model .22
5.3.1 Overview of enhanced model.22
5.3.2 Domain model which extends over multiple domains .22
5.3.3 Merged (or divorced) domain model.23
Annex A (informative) Existing domain specifications.27
Annex B (informative) Management for simultaneous information in a domain .30
Bibliography.31

Figure 1 – Domain in ARIB TR-B27.
Figure 2 – Domain in DVB CPCM.10
Figure 3 – Domain in OMA DRM V2.0 .11
Figure 4 – Domain in permission code .11
Figure 5 – Common domain in Marlin DRM .12
Figure 6 – Overview of a domain.13
Figure 7 – Components of a device.14

TS 62579 © IEC:2010(E) – 3 –
Figure 8 – Relationship between the basic elements of a domain model .15
Figure 9 – Example of RI management domain model.19
Figure 10 – Example of an RI management domain model.19
Figure 11 – Example of the RI management domain model.20
Figure 12 – Example of the RI management domain model.20
Figure 13 – Example of RI management domain model.20
Figure 14 – Example of an autonomous domain model .21
Figure 15 – Example of Autonomous domain model.22
Figure 16 – Regional domain .22
Figure 17 – Time stamped domain .23
Figure 18 – Merged user domains.23
Figure 19 – Merging domains based on user entities .24
Figure 20 – Merged domain .24
Figure 21 – Divorced user domain .25
Figure 22 – Divorced user domain based on user entities .25
Figure 23 – Divorced domain .26

Table 1 – Information elements of a domain.16
Table 2 – Device parameters that join domain .17
Table 3 – Items managed in a domain .18
Table A.1 – Domain specifications in DVB .27
Table A.2 – Domain specifications in OMA.27
Table A.3 – Domain specifications in ARIB .28
Table A.4 – Domain specifications in permission code .28
Table A.5 – Domain specifications in Marlin.28
Table A.6 – Domain specifications in iTunes .29
Table A.7 – Domain specifications in Coral .29
Table A.8 – Domain specifications in Cluster Protocol .29

– 4 – TS 62579 © IEC:2010(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
______________
MULTIMEDIA HOME SERVER SYSTEMS –
CONCEPTUAL MODEL FOR DOMAIN MANAGEMENT

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, IEC publishes International Standards, Technical Specifications,
Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC
Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested
in the subject dealt with may participate in this preparatory work. International, governmental and non-
governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely
with the International Organization for Standardization (ISO) in accordance with conditions determined by
agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly indicated in
the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and
expenses arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC
Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
The main task of IEC technical committees is to prepare International Standards. In
exceptional circumstances, a technical committee may propose the publication of a technical
specification when
• the required support cannot be obtained for the publication of an International Standard,
despite repeated efforts, or
• the subject is still under technical development or where, for any other reason, there is the
future but no immediate possibility of an agreement on an International Standard.
Technical specifications are subject to review within three years of publication to decide
whether they can be transformed into International Standards.
IEC 62579, which is a technical specification, has been prepared by technical area 8:
Multimedia home server systems of IEC technical committee 100: Audio, video and
multimedia systems and equipment.

TS 62579 © IEC:2010(E) – 5 –
The text of this technical report is based on the following documents:
Enquiry draft Report on voting
100/1626/CDV 100/1676/RVC
Full information on the voting for the approval of this technical specification can be found in
the report on voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
The committee has decided that the contents of this publication will remain unchanged until
the stability date indicated on the IEC web site under "http://webstore.iec.ch" in the data
related to the specific publication. At this date, the publication will be be
• transformed into an International standard,
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.

IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 6 – TS 62579 © IEC:2010(E)
INTRODUCTION
Compared with analog media, digital contents can be copied easily and the copies don't
decline in quality. So it is certain that digital contents should be protected.
But, compared to the rights of private records on analog media, it is hard for users to enjoy
their digital contents freely. The concept of a domain has been defined in several
organizations for the purpose of improving user convenience. Domains enable users to
consume and manage their digital contents in a manner which is more like enjoying analog
contents. Users can enjoy digital contents, which are stored on a device, not only on the
device where they are stored on but also on other devices within the same domain such as
home or school, etc. From a standpoint of copyrights, it means that the contents are allowed
to be consumed with a copy control technology on limited devices. A domain manages both
user convenience and contents protection. Depending on the scenario of the operated domain,
the limit and the boundary on domain configuration can be flexible.

TS 62579 © IEC:2010(E) – 7 –
MULTIMEDIA HOME SERVER SYSTEMS –
CONCEPTUAL MODEL FOR DOMAIN MANAGEMENT

1 Scope
This Technical Specification defines the conceptual model of domain management, which
includes terms, requirements and reference models. The domain is a set of devices, users,
and/or other entities which can share contents. Entities within a domain are allowed to play,
copy and move content and usage rules to other entities within the same domain.
Some existing systems have been proposed in this field of domain, but various vocabularies
and models are specified. This situation causes confusion and misunderstanding of systems,
and disturbs interoperability. This Technical Specification is intended to standardize the
vocabularies and clarify the models.
All kinds of digital content, including broadcast content which needs to be protected, are
considered in this specification. On the other hand, rights management and content protection
technology are beyond the scope of this specification.
NOTE In addition, network protocol and media format for content sharing and exchange are also out of the scope
of this specification. Refer also to IEC 62481-1 and IEC 62481-2 for interoperability guidelines.
2 Terms, definitions and abbreviations
2.1 Terms and definitions
For the purposes of this document the following terms and definitions apply.
NOTE These are necessary terms used in the field of domain management.
2.1.1
content issuer
rights issuer or contents holder
2.1.2
content
digital data, such as movies, images, audio and software, etc.
2.1.3
content key
encryption key related to each content
2.1.4
domain
set of devices, users, or other entities which can share contents and associated usage rules
2.1.5
domain ID
unique identifier which is related with a domain
2.1.6
domain key
secret information shared among entities in a domain

– 8 – TS 62579 © IEC:2010(E)
2.1.7
domain management server
server which issues or manages a domain ID and a domain key
2.1.8
domain join
process of including an entity in a domain, which enables the entity to obtain a new domain ID
or domain key
2.1.9
domain leave
process of excluding an entity from a domain, which ensures that the domain ID and domain
key in the device are deleted
2.1.10
domain merge
process of integrating multiple domains into a new domain with a unique domain ID
2.1.11
domain divorce
process of dividing a domain into multiple domains with different domain IDs
2.1.12
domain separate
process of dividing a domain into multiple domains with the same domain ID temporarily
2.1.13
user ID
unique identifier for the user; it could be a user account
2.1.14
user key
secret information shared among only the domains, devices or other entities bound to the
user; this information is generated by RI
2.1.15
usage rule
collection of permissions, keys and other attributes which are related to protected contents

TS 62579 © IEC:2010(E) – 9 –
2.2 Abbreviations
AD Authorized Domain
ARIB Association of Radio Industries and Businesses
CAS Conditional Access System
CL Content License
CPCM Content Protection and Copy Management
CRL Certificate Revocation List
DVB Digital Video Broadcasting
DRM Digital Rights Management
HANA High-Definition Audio-Video Network Alliance
KMB Key Management Block
LAD Localized Authorized Domain
OMA Open Mobile Alliance
RMPI Rights Management and Protection Information
RO Rights Object
RRT Round Trip Time
RI Rights Issuer
TTL Time to Live
USI Usage State Information
3 Use cases
3.1 Purpose of description of use cases
This clause is for information only and describes how domain management is specified and
how the scenario of domain is assumed in existing specifications on DRM. This leads to what
a domain management standard should contain.
In general, users can consume content without restriction of the location on all home electric
appliances, cell phones, mobile devices or car devices in the domain. The devices can share
content according to a permission system, which includes the use situation and the quality, in
each domain.
3.2 Example 1: A domain in ARIB TR-B27
A device is allowed to copy content and a certain part of the usage rule to storage media. The
content is played according to the restriction of the usage rule, as shown in Figure 1.
Domain
Plays according to the
restriction the of resolution
A content issuer controls all
devices belonging to a domain
Forwards contents and a part of
usage rules to other devices
IEC  1034/10
Figure 1 – Domain in ARIB TR-B27

– 10 – TS 62579 © IEC:2010(E)
3.3 Example 2: A domain in DVB CPCM
Users can get content available in LAD such as home network. After a certain time or event,
the content can be played on all other devices within the same domain, as shown in Figure 2.
Domain
Localised
Authorized Domain
Play in LAD
Play after
any times
24h
Localised
Authorized Domain
Play after 24
hours
The usage can be restricted within LAD
The restriction would expire after a certain time
period or event
IEC  1035/10
Figure 2 – Domain in DVB CPCM
3.4 Example 3: A domain in OMA DRM V2.0
A device forwards content and the associated usage rule to a cell phone.
The content and the usage rule are immediately usable on the cell phone without connecting
to the content issuers, if the conditions (start and end time) are satisfied.
Devices not connected to the network can obtain content and usage rules via the connected
device, using direct device-to-device connection, as shown in Figure 3.

TS 62579 © IEC:2010(E) – 11 –
Domain
Usage Rule: Play
Start and end time
Play after
Usage Rule: Play
joining domain
Start and end time
Unconnected
device
Connected
device
Usage Rule: Play
Start and end time
Gets contents,
using local
connection
IEC  1036/10
Figure 3 – Domain in OMA DRM V2.0
3.5 Example 4: A domain in permission code
A device that belongs to the domain is permitted to act as a receiver for the permission codes
(for example, play freely and copy up to 7 times, etc.).
A domain can be characterized as collective of permission receivers. A domain is also a
permission receiver, as shown in Figure 4.

Receiver ID for domain
Play: free
Copy: 7 times
Play: free
Copy: 7 times
Play: free
Copy: 7 times
Domain
Play: free
Copy: 7 times
A permission receiver can
be also a permission issuer
IEC  1037/10
Figure 4 – Domain in permission code

– 12 – TS 62579 © IEC:2010(E)
3.6 Example 5: A common domain in Marlin DRM
Multiple users can share content they have obtained provided that they are registered with the
same common domain, as shown in Figure 5.

Domain
Usage Rule: play
if user and device in
common domain
Content can be
User obtains
accessed by all
content and is
devices and users
registered with a
registered with the
common domain
common domain
IEC  1038/10
Figure 5 – Common domain in Marlin DRM

TS 62579 © IEC:2010(E) – 13 –
4 Conceptual model
4.1 Definition of a domain
A domain is a set of devices, users, and/or other entities which consume content according to
common usage rules. Devices in a domain are allowed to share content and the associated
usage rules within the same domain, as shown in Figure 6.

Domain
portable devices
home network
Usage
Rule
IEC  1039/10
Figure 6 – Overview of a domain
4.2 Forming a domain
A domain which groups a set of devices, users, and/or other entities together facilitates
content management in simple situations where no differentiation is required as to the identity
of the user. However, for situations where content is licensed based on the identity of the user
(e.g. delivery through mobile operator) a domain needs to provide for easy content access
government, based on the relationship of users with each other. In this case, a domain can
also be formed by associating a set of entities to a user entity and a common usage rule for
consuming content is then bound to the user entity instead of each individual entities. This
implies that all entities linked to the user domain are automatically governed by the same
common usage rule issued to the user entity. In addition, an entity can be part of multiple user
domains, e.g., a shared PVR in the living room can be part of two users’ domains, hence it is
allowed to consume content purchased by both users. Additionally, a multi-device, multi-user
domain model enables entities to join multiple domains and allowing a domain to contain
multiple entities, e.g., a household with 2 shared devices at home such as a PC and a PVR.
Each of these devices is linked to every user in the family, hence any content purchased by a
family member can be used on both family devices. However, this is not very efficient. An
alternative approach is to unite all users in a common domain and associate all shared
entities with the common domain, e.g., all family members are bound to a common domain
called family domain and the PVR and PC are members of this family domain.
There is a domain policy that is used to express the rules for forming a domain and
registering and deregistering entities to and from domains. The parameter for domain
management can be found in 4.4 . 2.

– 14 – TS 62579 © IEC:2010(E)
4.3 Components of a device which can join a domain
Figure 7 shows the typical components of a device which can join a domain.
Domain management: DEVICE
- Issues or receives requests to
join to or leave from a domain
Security:
- Key management
- Usage rule management
Content usage:
- acquires content data entity
- plays, copies, or exports content
IEC  1040/10
Figure 7 – Components of a device
The following list explains the components:
• Domain management: issues and receives requests to join a domain or leave a domain,
and exchanges such requests with other devices.
• Security: manages domain keys, usage rules, and other information to be protected
securely.
• Content usage: acquires content data entity via broadcasting or network, and controls
usage of content (for example playback, duplicate, export, and so on).
4.4 Requirements
4.4.1 Abstract domain model
This subclause presents the general domain model. Domain management should be modelled
using five basic elements, namely: Content (C), User Identity (P), Authorized Domain (AD),
Local Authorized Domain (LAD) and Device (D). Figure 8 illustrates the relationship between
these basic elements. Various domain models (c.f. Clause 5) can be built based on this
abstract domain model.
TS 62579 © IEC:2010(E) – 15 –
IEC  1041/10
Figure 8 – Relationship between the basic elements of a domain model
Acquired content (C) can be bound to a device (D), an authorized domain (AD) or a user
entity/identity (P). For content that is bound to a device, only the particular device is permitted
to use it. An authorized domain (AD) can consist of many devices, hence by binding content
to an AD simplifies the content authorization usage as only a single binding is needed to
enable multiple devices that are members of the AD to access the contents. Furthermore,
content can be bound to a user entity where it is purchased through a user account. Similarly,
a user entity or identity (P) can be linked to multiple authorized domains or multiple devices.
This allows for more flexibility in that th
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...