BSI DD IEC/TS 62579:2010
$167.15
Multimedia home server systems. Conceptual model for domain management
| Published By | Publication Date | Number of Pages |
| BSI | 2010 | 36 |
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..
PDF Catalog
| PDF Pages | PDF Title |
|---|---|
| 4 | CONTENTS |
| 6 | FOREWORD |
| 8 | INTRODUCTION |
| 9 | 1 Scope 2 Terms, definitions and abbreviations 2.1 Terms and definitions |
| 11 | 2.2 Abbreviations 3 Use cases 3.1 Purpose of description of use cases 3.2 Example 1: A domain in ARIB TR-B27 Figures Figure 1 – Domain in ARIB TR-B27 |
| 12 | 3.3 Example 2: A domain in DVB CPCM 3.4 Example 3: A domain in OMA DRM V2.0 Figure 2 – Domain in DVB CPCM |
| 13 | 3.5 Example 4: A domain in permission code Figure 3 – Domain in OMA DRM V2.0 Figure 4 – Domain in permission code |
| 14 | 3.6 Example 5: A common domain in Marlin DRM Figure 5 – Common domain in Marlin DRM |
| 15 | 4 Conceptual model 4.1 Definition of a domain 4.2 Forming a domain Figure 6 – Overview of a domain |
| 16 | 4.3 Components of a device which can join a domain 4.4 Requirements Figure 7 – Components of a device |
| 17 | Figure 8 – Relationship between the basic elements of a domain model |
| 18 | Tables Table 1 – Information elements of a domain |
| 19 | Table 2 – Device parameters that join domain |
| 20 | 5 Reference models 5.1 General 5.2 Basic model Table 3 – Items managed in a domain |
| 21 | Figure 9 – Example of RI management domain model Figure 10 – Example of an RI management domain model |
| 22 | Figure 11 – Example of the RI management domain model Figure 12 – Example of the RI management domain model Figure 13 – Example of RI management domain model |
| 23 | Figure 14 – Example of an autonomous domain model |
| 24 | 5.3 Enhanced model Figure 15 – Example of Autonomous domain model Figure 16 – Regional domain |
| 25 | Figure 17 – Time stamped domain Figure 18 – Merged user domains |
| 26 | Figure 19 – Merging domains based on user entities Figure 20 – Merged domain |
| 27 | Figure 21 – Divorced user domain Figure 22 – Divorced user domain based on user entities |
| 28 | Figure 23 – Divorced domain |
| 29 | Annex A (informative) Existing domain specifications Table A.1 – Domain specifications in DVB Table A.2 – Domain specifications in OMA |
| 30 | Table A.3 – Domain specifications in ARIB Table A.4 – Domain specifications in permission code Table A.5 – Domain specifications in Marlin |
| 31 | Table A.6 – Domain specifications in iTunes Table A.7 – Domain specifications in Coral Table A.8 – Domain specifications in Cluster Protocol |
| 32 | Annex B (informative) Management for simultaneous information in a domain |
| 33 | Bibliography |
