1. Trang chủ
  2. » Kỹ Thuật - Công Nghệ

Bsi bs en 62227 2008 + a1 2013

80 2 0

Đang tải... (xem toàn văn)

Tài liệu hạn chế xem trước, để xem đầy đủ mời bạn chọn Tải xuống

THÔNG TIN TÀI LIỆU

Nội dung

BS EN 62227:2008+A1:2013 BSI Standards Publication Multimedia home server systems — Digital rights permission code NO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAW raising standards worldwide™ BRITISH STANDARD BS EN 62227:2008+A1:2013 National foreword This British Standard is the UK implementation of EN 62227:2008+A1:2013 It is identical to IEC 62227:2008, incorporating amendment 1:2012 It supersedes BS EN 62227:2008, which is withdrawn The start and finish of text introduced or altered by amendment is indicated in the text by tags Tags indicating changes to IEC text carry the number of the IEC amendment For example, text altered by IEC amendment is indicated by !" The UK participation in its preparation was entrusted to Technical Committee EPL/100, Audio, video and multimedia systems and equipment A list of organizations represented on this committee can be obtained on request to its secretary This publication does not purport to include all the necessary provisions of a contract Users are responsible for its correct application © The British Standards Institution 2013 Published by BSI Standards Limited 2013 ISBN 978 580 78654 ICS 33.160.60; 35.240.99 Compliance with a British Standard cannot confer immunity from legal obligations This Draft for Development was published under the authority of the Standards Policy and Strategy Committee on 31 January 2009 Amendments/corrigenda issued since publication Date Text affected 30 June 2013 Implementation of IEC amendment 1:2012 with CENELEC endorsement A1:2013 EUROPEAN STANDARD EN 62227:2008+A1 NORME EUROPÉENNE EUROPÄISCHE NORM March 2013 ICS 33.160.60; 35.240.99 English version Multimedia home server systems Digital rights permission code (IEC 62227:2008) Systèmes serveurs multimédia domestiques Codes numériques des autorisations des droits (CEI 62227:2008) Multimedia-Homeserversysteme Zulassungsschlüssel für digitale Rechte (IEC 62227:2008) This European Standard was approved by CENELEC on 2008-09-01 CENELEC members are bound to comply with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard the status of a national standard without any alteration Up-to-date lists and bibliographical references concerning such national standards may be obtained on application to the Central Secretariat or to any CENELEC member This European Standard exists in three official versions (English, French, German) A version in any other language made by translation under the responsibility of a CENELEC member into its own language and notified to the Central Secretariat has the same status as the official versions CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia, Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain, Sweden, Switzerland and the United Kingdom CENELEC European Committee for Electrotechnical Standardization Comité Européen de Normalisation Electrotechnique Europäisches Komitee für Elektrotechnische Normung Central Secretariat: rue de Stassart 35, B - 1050 Brussels © 2008 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members Ref No EN 62227:2008 E BS EN 62227:2008+A1:2013 - ii - EN 62227:2008+A1:2013 Foreword The text of document 100/1287/CDV, future edition of IEC 62227, prepared by technicaI area 8, Multimedia home server systems, of IEC TC 100, Audio, video and multimedia systems and equipment, was submitted to the IEC-CENELEC parallel vote and was approved by CENELEC as EN 62227 on 2008-09-01 The following dates were fixed: – latest date by which the EN has to be implemented at national level by publication of an identical national standard or by endorsement (dop) 2009-06-01 – latest date by which the national standards conflicting with the EN have to be withdrawn (dow) 2011-09-01 Annex ZA has been added by CENELEC Endorsement notice The text of the International Standard IEC 62227:2008 was approved by CENELEC as a European Standard without any modification Foreword to amendment A1 The text of document 100/1953/CDV, future edition of IEC 62227:2008/A1, prepared by Technical Area 8, "Multimedia home server systems", of IEC/TC 100, "Audio, video and multimedia systems and equipment" was submitted to the IEC-CENELEC parallel vote and approved by CENELEC as EN 62227:2008/A1:2013 The following dates are fixed: • • latest date by which the document has to be implemented at national level by publication of an identical national standard or by endorsement latest date by which the national standards conflicting with the document have to be withdrawn (dop) 2013-10-03 (dow) 2016-01-03 Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights CENELEC [and/or CEN] shall not be held responsible for identifying any or all such patent rights Endorsement notice The text of the International Standard IEC 62227:2008/A1:2012 was approved by CENELEC as a European Standard without any modification BS EN 62227:2008+A1:2013 - iii - EN 62227:2008+A1:2013 Annex ZA (normative) Normative references to international publications with their corresponding European publications 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 NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD applies Publication Year Title EN/HD Year ISO 3166-1 2006 Codes for the representation of names of countries and their subdivisions Part 1: Country codes EN ISO 3166-1 2006 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) –2– CONTENTS FOREWORD INTRODUCTION Scope .9 Normative references .9 Terms, definitions and abbreviations 3.1 Terms and definitions 3.2 Abbreviated terms 15 Permission code framework 16 4.1 4.2 General 16 Assumptions associated with the permission code 17 4.2.1 Binary relationships within the content distribution value chain 17 4.2.2 Permission issued for a group of content 17 4.2.3 Common code center for permissions 18 4.2.4 Usage report 18 4.2.5 Application scenario of the permission code 18 4.2.6 Harmonization with DRM systems 19 4.3 Components of a permission code 19 4.3.1 Permission actor 19 4.3.2 Permission classification 22 4.3.3 Content usage 22 4.3.4 Content data handling 23 Permission code configuration 24 5.1 5.2 5.3 5.4 5.5 5.6 General 24 Notation 25 5.2.1 Numerical values 25 Permission code system 25 Version unit 26 5.4.1 Structure 26 5.4.2 Version unit tag 26 5.4.3 Reserved 27 5.4.4 Version 27 Permission actor unit 27 5.5.1 Structure 27 5.5.2 Permission actor unit tag 27 5.5.3 Total bytes of identifiers 27 5.5.4 Content identifier 28 5.5.5 Issuer identifier 29 5.5.6 Receiver identifier 31 Permission classification unit† 32 5.6.1 Structure 32 5.6.2 Permission classification unit tag 32 5.6.3 Reserved 32 5.6.4 Disclosure class 32 5.6.5 Usage purpose class 33 5.6.6 Charge model class 34 5.6.7 Billing class 34 BS EN 62227:2008+A1:2013 –3– 62227 © IEC:2008+A1:2013(E) 5.6.8 Application class 35 5.6.9 Sponsor class 35 5.6.10 Territory class 36 5.6.11 Usage class 36 5.7 General usage condition unit 39 5.7.1 Unit structure 39 5.7.2 General usage condition header 39 5.7.3 General usage condition descriptor 39 5.8 Extended use condition unit 48 5.9 Data management condition unit 49 5.9.1 Unit structure 49 5.9.2 Data management condition header 49 5.9.3 Data management condition 50 5.10 Data export condition unit 52 5.10.1 Unit structure 52 5.10.2 Data export condition header 52 5.10.3 Data export condition descriptor 52 5.10.4 General export descriptor 53 Annex A (informative) Permission code requirements for home servers and playback devices 57 Annex B (informative) Use-case scenario 62 Annex C (informative) Issuing a permission code 70 Figure – Permission code environment 17 Figure – Permission code environment 23 Figure – Permission code configuration 26 Figure – Basic structure of permission code unit 26 Figure – General usage condition unit 39 Figure – Data management condition unit 49 Figure – Data export condition unit 52 Figure A.1 – Permission code and domain 58 Figure A.2 – Re-issuing permission information 59 Figure A.3 – Re-issuing permission among permission code compliant objects is allowed 60 Figure A.4 – Re-issuing permission within a domain is allowed 60 Figure A.5 – Other conditions 61 Figure B.1 – Permission code structuring (1/2) 62 Figure B.2 – Permission code structuring (2/2) 63 Figure B.3 – Permission code example with respect to FairPlay (1/2) 63 Figure B.4 – Permission code example with respect to FairPlay (2/2) 64 Figure B.5 – Permission code example with respect to CPRM (1/2) 65 Figure B.6 – Permission code example with respect to CPRM (2/2) 65 Figure B.7 – Permission code example with respect to SAFIA (1/2) 66 Figure B.8 – Permission code example with respect to SAFIA (2/2) 66 Figure B.9 – Permission code example with respect to PC distribution (streaming) 67 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) –4– Figure B.10 – Permission code example with respect to PC distribution (download) (1/2) 68 Figure B.11 – Permission code example with respect to PC distribution (download) (2/2) 68 Figure B.12 – Permission code example with respect to ringtones (1/2) 69 Figure B.13 – Permission code example with respect to ringtones (2/2) 69 Figure C.1 – The flow of issuing a permission code to grant access to a single piece of content (for access on a home server) 70 Figure C.2 – The flow of issuing a permission code to grant access to a single piece of content (for access on a client device) 71 Figure C.3 – The flow of issuing a permission code to grant access to subscription content (for access on a home server) 72 Figure C.4 – The flow of issuing a permission code to grant access to subscription content (for access on a client device) 73 Table – Distinct tag interpretation 25 Table – Structure of version unit 26 Table – Structure of permission actor unit 27 Table – Structure of content identifier descriptor 28 Table – Content type code interpretation 28 Table – Structure of issuer identifier descriptor 29 Table – Issuer role code interpretation 30 Table – Issuer configuration code interpretation 30 Table – Structure of receiver identifier descriptor 31 Table 10 – Receiver role code interpretation 31 Table 11 – Receiver configuration code interpretation 31 Table 12 – Structure of permission classification unit 32 Table 13 – Structure of disclosure class 33 Table 14 – disclosure_type (DT) interpretation 33 Table 15 – Structure of usage purpose class 33 Table 16 – usage_purpose_type (UPT) interpretation 33 Table 17 – Structure of charge model class 34 Table 18 – charge_model_type (CMT) interpretation 34 Table 19 – Structure of billing class 35 Table 20 – billing_type (BT) interpretation 35 Table 21 – Structure of application class 35 Table 22 – application_type (AT) interpretation 35 Table 23 – Structure of sponsor class 36 Table 24 – Configuration of sponsor_type (ST) 36 Table 25 – Structure of territory class 36 Table 26 – Structure of usage class 37 Table 27 – Usage_type (UT) interpretation 37 Table 28 – Configuration of redistribution_Type 38 Table 29 – Structure of general usage condition header 39 Table 30 – Tag values of descriptors 40 BS EN 62227:2008+A1:2013 –5– 62227 © IEC:2008+A1:2013(E) Table 31 – Structure of playback usage condition descriptor 40 Table 32 – Structure of print usage condition descriptor 43 Table 33 – Structure of execute usage condition descriptor 46 Table 34 – Structure of data management condition header 49 Table 35 – Structure of data management condition 50 Table 36 – Structure of encryption flag (EF) 50 Table 37 – Transcode type interpretation 51 Table 38 – Structure of time-line flag (TF) 51 Table 39 – Structure of data export condition header 52 Table 40 – Tag values of descriptors 53 Table 41 – Structure of general export descriptor 53 Table 42 – storage_media_type (SMT) interpretation 54 Table 43 – encoding_type (ET) interpretation 54 Table 44 – protection_type (PT) interpretation 55 Table 45 – control_type (CT) interpretation 55 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) –6– INTERNATIONAL ELECTROTECHNICAL COMMISSION MULTIMEDIA HOME SERVER SYSTEMS – DIGITAL RIGHTS PERMISSION CODE 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 nongovernmental 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 provides no marking procedure to indicate its approval and cannot be rendered responsible for any equipment declared to be in conformity with an IEC Publication 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 International Standard IEC 62227 has been prepared by technical area 8: Multimedia home server systems, of IEC technical committee 100: Audio, video and multimedia systems and equipment The text of this standard is based on the following documents: CDV Report on voting 100/1287/CDV 100/1374/RVC Full information on the voting for the approval of this standard 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 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 62 – Annex B (informative) Use-case scenario B.1 Anticipated use-cases The following is a set of anticipated use-cases for the use of permission codes a) A producer issues usage permission directly to an end user b) An aggregator issues usage permission to a delivery service provider c) A delivery service provider issues usage permission to a home domain d) A delivery service provider issues usage permission to a device e) A delivery service provider reports usage with respect to a permission code f) A permission manager searches for a rights holder by using the content identifier included within the permission code as a search parameter B.2 B.2.1 Immediately available use cases General This subclause illustrates use cases that can be realized with the use of permission codes The structure of a permission code is illustrated graphically below The permission code is designed as it harmonizes with DRM systems, and its permission cover the range of permission of existing DRM systems Here some examples are illustrated, but the permission code is applicable for other various DRM systems Permission Code Structuring (1/2) Basic structure of a unit Version Unit Version Tag Tag Identifies info stored in Data section Version Size Data Length of The Data itself Syntax differs Data Section based on the Tag 0x10 (Ver 1.0) Variable length section Permission Actor Unit Permission Actor Tag 48 Permission Classification Unit Permission Classification Tag Permission Actor Information Content ID Issue ID Static DC UPC CMC SC BC AC TC UC Receiver ID Because the stored info is static, types of identifiers are implicitly encapsulated (oridinary 16 bytes each, but size is extendable) Because the stored info is static, respective flags are implicitly retained (The flag contents are preliminary and initial flags are displayed) DC: Disclosure Class, UPC: Usage Purpose Class, CMC: Charge Model Class, SC: Sponsor Class, BC: Billing Class, AC: Application Class, TC: Territory Class, UC: Usage Class Extended Usage Condition Unit General Usage Condition Unit Depending on the content or the Permission, the information necessary changes For example, content A requires playback conditions only, while content B requires both playback and print conditions Tags, therefore, explicitly identifies what kind of usage conditions are included Playback Condition Tag General Usage Condition Tag Static Play Count Static length section Section with implicit structure Usage Class Information Variable General Usage Condition Playback Usage Condition Play Period ・・・ Print Condition Tag Extended Usage Condition Tag Static With respect to Extended Usage Conditions, Tags are the only terms specified (This unit itself is actually unnecessary for this code) ・・・ Print Usage Condition Print Count Print Size ・・・ Tag & Data units continue (if necessary) for Edit and Modify Under the Playback Usage Condition, info to be specified is static Under the Print Usage Condition, info to be specified is static Therefore, Flags and Parameters are implicitly encapsulated Therefore, Flags and Parameters are implicitly encapsulated IEC Figure B.1 – Permission code structuring (1/2) 705/08 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 63 – Permission Code Structuring (2/2) The structure that specifies a record for each management subject, after the field that specifies the number of records, is implicit However, note that since the number of management subjects is variable, in general the length is variable Data Management Condition Unit Data Export Condition Unit Data Management Variable Data Management Condition Condition Tag Data Export Condition Tag Data Export Condition Variable N Receiver ID = Encryption Flag ZZZZZZZZ Copy Count Transcode Restrictions Expiration Date Sublicense Count Simultaneous Export Condition Tag Receiver ID = Device IDa Encryption Flag Copy Count Transcode Restrictions Expiration Date Sublicense Count Receiver ID = Device IDb Encryption Flag Copy Count Transcode Restrictions Expiration Date Sublicense Count N ・・・ Copy Count Transcode Restrictions Expiration Date Condition independent from Export target DRM CPRM Condition Tag Variable Export Condition unique to CPRM ACCS Export Condition Tag Variable Export Condition unique to ACCS SAFIA Condition Tag Variable Sublicense Count Export Condition unique to SAFIA ・・・ Receiver ID = Domain ID A Encryption Flag Variable Separated between a section that specifies conditions independent from the Export target and a section that specifies conditions dependent on the target DRM Dependent section is necessary because: ・Depending on the nature of the target DRM, special Parameters are required ・Some target DRMs require conditions to be changed Whether each data section will be further structured or whether they would be made implicit is TBD IEC 706/08 Items expressed under Data Management Condition are static and not depend on the subject managed Therefore, the record’s structure is implicit Multiple records are stored in sequence Figure B.2 – Permission code structuring (2/2) B.2.2 Permission code example with respect to fairplay Permission code conditions: As long as Mr A is using the content, there is no restriction to copy or play Export to CDs is allowed up to 10 times Permission Code Example with respect to Fairplay (1/2) Version Unit Version Tag Version 0x10 (Ver 1.0) Permission Actor Unit Permission Actor Tag 48 Permission Classification Unit Permission Actor Information Permission Classification Tag Content ID Issue ID Content ID iTunes ・iTunes issues Permission to Mr A’s PC Static Usage Class Information DC UPC CMC SC BC AC TC UC Open Permission, Permit personal use only … Receiver ID Mr A’s PC General Usage Condition Unit General Usage Condition Tag Variable General Usage Condition Extended Usage Condition Tag Extended Usage Condition is not needed Playback Condition Tag Static Playback Usage Condition ・iTunes specifies Playback use only (Other usage modes are not permitted) ・Therefore, only the Playback Condition Unit is retained Play Count Play Period ・・・ ∞ ∞ ・As long as it is used within iTunes, there is no Play Count nor Period restrictions Figure B.3 – Permission code example with respect to FairPlay (1/2) IEC 707/08 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 64 – Permission Code example with respect to FairPlay (2/2) Data Export Condition Unit Data Management Condition Unit Data Management Variable Data Management Condition Condition Tag Data Export Condition Tag Variable Data Export Condition Not specified Encryption Flag Copy Count Mr A’s Domain Encryption Flag Copy Count n/a Yes ∞ Transcode Restrictions Expiration Date Sublicense Count Transcode Restrictions Expiration Date Sublicense Count n/a none n/a none n/a ∞ ・Generally Copying content is not allowed Therefore, fields other than Copy Count is n/a (no significance) ・Copying and Re-issuance of Licenses is allowed only within Mr A’s Domain (Mr A’s PC, Mr A’s iPod) However, encryption is required for content protection Simultaneous Export Condition Tag Variable Condition independent from Export target DRM Export not allowed (including Move) CD Condition Tag Variable Condition unique to CD Export Export of copy allowed up to 10 times ・Generally, Exporting content is not allowed (even Move is not allowed) ・If the Export Target is a CD, (technically a CD DRM), Export is allowed up to 10 times ・The contents of the Permission would not allow for content control after Export to CD Therefore, effectively, it is equivalent to “Copy freely” However, this would be outside the scope of the Permission Code After changing PCs, FairPlay re-authenticates Mr A by re-connecting to the server Expressing this process through the Permission Code, Sublicense Count to Mr A would be ∞, with the Sublicense issued from the iTunes server This would be a management method unique to this particular DRM and would be reflected as such in this section IEC 708/08 Figure B.4 – Permission code example with respect to FairPlay (2/2) B.2.3 Permission code example with respect to CPRM (DVD-RW VR mode) Permission code conditions: no restrictions on playback Edit and playlist creation are allowed while further copy creation is not allowed Move is allowed as long as further content instances are not created in the process BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 65 – Permission Code Example with respect to CPRM (DVD-RW VR Mode)(1/2) Version Unit Version Tag Version 0x10 (Ver 1.0) Permission Classification Unit Permission Actor Unit Permission Actor Tag 48 Permission Actor Information Permission Content ID Content ID Classification Tag Issue ID NHK Static Usage Class Information DC UPC CMC SC BC AC TC UC Open Permission, Permit personal use only… Receiver ID DVD-RW Media ID ・NHK (representing various rights holders) issues Permission to a specific DVD-RW Disk General Usage Condition Unit General Usage Condition Tag Variable General Usage Condition Extended Usage Condition Tag Extended Usage Condition Unit is not necessary ・Specify terms for Playback use and Edit use (Other uses are not Permitted) Playback Condition Tag Static Playback Usage Condition Play Period ・・・ ∞ ∞ ・No restrictions on Play Count, Play Period or playlist creation ・Receiver ID corresponds to the DVD-RW, so as long as the user possesses this disk, the content can be played on any Device (If the Receiver ID were to be a person, or a Device, the Permission Code must or prohibit other people or other Devices from playing the content.) IEC 709/08 Play Count Figure B.5 – Permission code example with respect to CPRM (1/2) Permission Code Example with respect to CPRM (DVD-RW VR Mode) (2/2) Data Management Condition Unit Data Management Variable Condition Tag Data Export Condition Unit Data Management Condition Data Export Condition Tag Variable Data Export Condition Not Specified Encryption Flag Yes Copy Count Transcode Restrictions ∞ Not Allowed Expiration Date None Sublicense Count Time-line Edit Allowed ・Encrypted data can be freely copied There is no Expiration Date ・Sublicensing is not allowed Thereby, in practice, Copy is not allowed Move is also technically allowed in the Permission However, due to DVD-RW’s inherent physical and logical constraints, it is essentially not possible ・There are no restrictions on Edit ・If Permission were to prohibit cutting out commercials for example, Edit conditions would change Simultaneous Export Condition Tag Trusted DRM Export Condition Tag Variable Variable Condition independent from target DRM Export not allowed (incl Move) Condition for DRM “trusted” by CPRM Move Permitted No more Copies allowed at target ・Generally, content Export is not allowed, even if it is limited to Move only ・Move is Permitted so long as it is to a DRM that CPRM “trusts” (a list of “trusted” DRMs will be determined by CPRM’s operating policy) Note, however, that as is the case with Data Management Condition, Move is not possible in practice IEC Figure B.6 – Permission code example with respect to CPRM (2/2) B.2.4 Permission code example with respect to SAFIA Permission code conditions: copy count is 10, and making further copies at the copy target is not allowed Play count is 10 Edit and playlist creation are allowed Move is allowed so long as no further content instances are created in the process NOTE The current SAFIA standard does not allow for simultaneous use of copy control and play count control In addition, the current TV recording standard cannot apply copy count controls This is a future potential use case 710/08 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 66 – Permission Code Example with respect to SAFIA (1/2) Version Unit Version Tag Version 0x10 (Ver 1.0) Permission Classification Unit Permission Actor Unit Permission Actor Tag 48 Permission Classification Tag Static Permission Actor Information Content ID Content ID Issue ID NHK Usage Class Information DC UPC CMC SC BC AC TC UC Open Permission, Permit personal use only… Receiver ID iVDR Media ID ・NHK (representing various rights holders) issues Permission to a specific iVDR Media General Usage Condition Unit General Usage Condition Tag Variable General Usage Condition Extended Usage Condition Tag Extended Usage Condition Unit is not necessary ・Specify terms for Playback use and Edit use (Other uses are not Permitted) Playback Condition Tag Static Playback Usage Condition Play Count Play Period 10 ∞ ・・・ Playlist Playback Allowed ・Play Count is 10 ・No restriction on Play Period, Playlist Playback (playlist creation) etc ・Receiver ID corresponds to the iVDR media, so as long as the user possesses this iVDR media, the content can be played on any Device IEC 711/08 Figure B.7 – Permission code example with respect to SAFIA (1/2) Permission Code Example with respect to SAFIA (2/2) Data Management Condition Unit Data Management VariableData Condition Tag Data Export Condition Unit Data Export Management Condition Condition Tag Variable Data Export Condition Not Specified Encryption Flag Yes Copy Count ∞ Transcode Restrictions Not Allowed Expiration Date None Sublicense Count 10 Time-line Edit Allowed ・Encrypted data can be freely copied There is no Expiration Date ・Sublicensing is allowed up to 10 times However, Sublicensing of Sublicenses is not allowed (Sublicense target receives the Permission as “Sublicense Count=0”) ・There are no restrictions on Edit ・If Permission were to prohibit cutting out commercials for example, Edit conditions would change Simultaneous Export Condition Variable Tag Trusted DRM Export Condition Variable Tag Condition independent from target DRM Export not allowed (incl Move) Condition for DRM “trusted” by SAFIA Move Permitted No more Copies allowed at target ・Generally, content Export is not allowed, even if it is limited to Move only ・Move is Permitted so long as it is to a DRM that SAFIA “trusts” (a list of “trusted” DRMs will be determined by SAFIA’s operating policy) IEC Figure B.8 – Permission code example with respect to SAFIA (2/2) B.2.5 Key permission code examples with respect to PC distribution (WMT, streaming) Permission code conditions: copy count is 0, and making further copies at the copy target is not allowed There are no restrictions on play count There is an expiration date Edit and playlist creation are not allowed Move is not allowed 712/08 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 67 – Key Permission Code Examples with respect to PC distribution (WMT, streaming) Version Unit Version Tag Version 0x10 (Ver 1.0) Permission Actor Unit Permission Actor Tag 48 Permission Classification Unit Permission Classification Tag Static Permission Actor Information Content ID Content ID Issue ID ISP Receiver ID WMTd-0 ・ISP issues Permission to subscriber’s WMTd-0 environment Usage Class Information DC UPC CMC SC BC AC TC UC Open Permission, Permit personal use only… Streaming Permission General Usage Condition Unit General Usage Condition Tag Variable General Usage Condition Extended Usage Condition Tag Extended Usage Condition unit is not necessary Playback Condition Tag Static Playback Usage Condition Play Count Play Period day ∞ ・Specifies Playback use only (other usage modes are not Permitted) ・Therefore, only the Playback Condition Unit is retained ・・・ ・No restrictions on Play Count Play Period is specified IEC 713/08 Figure B.9 – Permission code example with respect to PC distribution (streaming) NOTE In this permission, usage type of permission classification is streaming permission This does not mean that the end user is permitted to re-distribute the content by streaming, but this means that the end user is permitted to watch this content in streaming way When the end user receives this permission code, the content is already distributed by streaming B.2.6 Key permission code example with respect to PC distribution (WMT, download) Permission code conditions: copy count is 3, and making further copies at the copy target is not allowed There are no restrictions on play count There are no play period restrictions Move is allowed so long as no further content instances are created in the process BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 68 – Key Permission Code Examples with respect to PC distribution (WMT, download) (1/2) Version Unit Version Tag Version 0x10 (Ver 1.0) Permission Actor Unit Permission Actor Tag 48 Permission Classification Unit Permission Classification Tag Static Permission Actor Information Content ID Content ID DC UPC CMC SC BC AC TC UC Open Permission, Permit personal use only… Download Permission Receiver ID WMTd-0 Issue ID ISP Usage Class Information ・ISP issues Permission to subscriber’s WMTd-0 environment General Usage Condition Unit General Usage Condition Tag General Usage Condition Variable Extended Usage Condition Tag Extended Usage Condition unit is not necessary Playback Condition Tag Static ・Specifies Playback use only (other usage modes are not Permitted) ・Therefore, only the Playback Condition Unit is retained Playback Usage Condition Play Count Play Period ∞ ∞ ・・・ IEC ・No restrictions on Play Count nor Play Period 714/08 Figure B.10 – Permission code example with respect to PC distribution (download) (1/2) Key Permission Code Example with respect to PC distribution (WMT, download) (2/2) Data Export Condition Unit Data Management Condition Unit Data Management Variable Data Management Condition Condition Tag Not Specified WMTd-0 Encryption Flag Copy Count Yes Encryption Flag Yes Copy Count T ranscode Restrictions Not Allowed Not Allowed Transcode Restrictions Expiration Date None Expiration Date None Sublicense Count Sublicense Count ・WMT-DRM environments (not specified) not allow Sublicensing ・WMTd-0 environment for the same subscriber allo ws for Sublicensing to up to machines Copy Count at the Sublicense target is Sublicense Count is There is no Expiration Date Data Export Condition Tag Variable Data Export Condition Simultaneous Export Condition Variable Condition independent from target DRM Export not allowed (incl Move) Tag Trusted DRM Condition for DRM “trusted” by WMT Export Condition Variable Tag Move Permitted No more Copies allowed at target CD Condition Tag Export Condition unique to CDs Variable Export of Copies allowed up to 10 times ・Generally, content Export is not allo wed, even if it is limited to Move only ・Move is Permitted so long as it is to a DRM that WMT “trusts” (a list of “trusted” DRMs will be determined by WMT’s operating policy) ・Export to CDs are allowed up to 10 times IEC Figure B.11 – Permission code example with respect to PC distribution (download) (2/2) 715/08 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 69 – B.2.7 Key permission code example with respect to ringtones Permission code conditions: copy is not allowed, and therefore it is not possible to make further copies at a copy target There are no restrictions on play count nor play period Move is not allowed Key Permission Code Examples with respect to ringtones (1/2) Version Unit Version Tag Version 0x10 (Ver 1.0) Permission Actor Unit Permission Actor Tag 48 Permission Classification Unit Permission Classification Tag Static Permission Actor Information Content ID Content ID Issue ID cp Usage Class Information DC UPC CMC SC BC AC TC UC Open Permission, Permit personal use only… Receiver ID Subscriber-a ・CP issues Permission to subscriber-a (same phone number) General Usage Condition Unit General Usage Condition Tag Extended Usage Condition Tag General Usage Condition Variable Extended Usage Condition unit is not necessary Playback Condition Tag Static ・Specifies Playback use only (other usage modes are not Permitted) ・Therefore, only the Playback Condition Unit is retained Playback Usage Condition Play Count Play Period ∞ ∞ ・・・ ・No restrictions on Play Count nor Play Period IEC 716/08 Figure B.12 – Permission code example with respect to ringtones (1/2) Key Permission Code Example with respect to ringtones (2/2) Data Management Condition Unit Data Export Condition Unit Data Management Variable Data Management Condition Condition Tag Data Export Condition Tag Not Specified Encryption Flag Copy Count Yes Subscriber-a Encryption Flag Yes Copy Count Transcode Restrictions Not Allowed ∞ Not Allowed Transcode Restrictions Expiration Date None Expiration Date None Sublicense Count Sublicense Count ∞ ・Ringtone environments (not specified) not allow Sublicensing ・For the same subscriber, Sublicensing is allowed Copy Count at the Sublicense target is ∞ There is no Expiration Date Variable Data Export Condition Simultaneous Export Condition Variable Condition independent from target DRM Export not allowed (incl Move) Tag Trusted DRM Export Condition Variable Condition for DRM “trusted” by WMT Move Permitted No more Copies allowed at target Tag CD Condition Tag Variable Export Condition unique to CDs Export of Copies allowed up to 10 times ・Generally, content Export is not allowed, even if it is limited to Move only ・Export to Secure SD cards (CPRM+SD binding using telephone number) is allowed IEC Figure B.13 – Permission code example with respect to ringtones (2/2) 717/08 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 70 – Annex C (informative) Issuing a permission code C.1 Permission code and home server The delivery service provider has the capacity to issue permission to a home server By connecting to the permission management center, the delivery service provider can request the permission management center to issue permission and the acquired permission code to the home server a) Issuing a permission code to grant access for a single piece of content When providing content individually, permission is expressed by utilizing a single permission code One permission code is issued for each piece of content Each permission code contains the content’s permission information When accessing content on a home server, the license is exchanged between the license server and the home server When accessing content on a client device, the license is exchanged between the license server and the client device Classification Rights Holder Permission between Rights Holder and Permission Manager Permission Code flow from the Permission Management Server to the Home Server Permission Management Server Confirm Apply Permission Confirm Apply for Permission Code Request Permission Code Permission Code Receive Permission Code Issue Permission Code Use Permission Code Record Usage History Home Server Client Apply for Permission Confirm Generate Permission Code License Server License Acquire License Encrypted Content Report Play Content Update Delete IEC Figure C.1 – The flow of issuing a permission code to grant access to a single piece of content (for access on a home server) 718/08 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 71 – Classification Rights Holder Permission Management Server Permission between Rights Holder and Permission Manager Confirm Apply Permission Confirm Permission Code flow from the Permission Management Server to the Home Server Generate Permission Code License Server Apply for Permission Code Request Permission Code Permission Code Receive Permission Code Issue Permission Code Home Server Request LIcense Confirm Use Permission Code Record Usage History Client License Encrypted Content Report Acquire License Play Content Update Delete IEC 719/08 Figure C.2 – The flow of issuing a permission code to grant access to a single piece of content (for access on a client device) b) Issuing a permission code to grant access for subscription content When offering a subscription service, permission is expressed using a parent permission code and a child permission code A parent permission code is a permission code issued to grant access to a subscription service and contains permission information concerning the subscription A child permission code is a permission code issued for each piece of content being offered as part of the subscription service and contains permission information concerning the content BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) Classification Rights Holder Permission between Rights Holder and Permission Manager Confirm Permission Permission Code flow from the Permission Management Server to the Home Server – 72 – Permission Management Server Home Server License Server Client Apply Confirm Apply for Subscription Permission Confirm Generate Parent Permission Issue Parent Permission C d Apply for Permission Code Parent Permission Code Issue Child Permission Code Request Permission Code Receive Parent Permission Code Use Parent Permission Code Child Permission Code Receive Child Permission Code Use Child Permission Code Record Usage History Parent License Child License Acquire License Encrypted Content Report Play Content Update Delete IEC Figure C.3 – The flow of issuing a permission code to grant access to subscription content (for access on a home server) 720/08 BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 73 – Classificati tion on Righ ghts ts Hold oldeer Permission between Rights Holder and Permission Manager Permission Code flow from the Permission Manager Server to the Home Server Perm Pe rmis issi sion on Ma Mannag ageement Serrver Se Confirm Apply Permission Confirm Issue Parent Permission Code Home Ho me Ser erver ver Client Apply for Subscription Permission Confirm Generate Parent Permission Code Licens Li censee Se Serrver Apply for Permission Code Parent Permission Request Permission Code Receive Parnet Permission Code Use Parent Permission Code Issue Child Permission Code Child Permission Parent License Acquire Parent License Confirm Receive Child Permission Code Parent License Request Child License Confirm Use Child Permission Code Record Usage History Acquire Parent License Child License Encrypted Content Report Acquire Child License Play Content Update Delete IEC 721/08 Figure C.4 – The flow of issuing a permission code to grant access to subscription content (for access on a client device) C.2 Managing home domains When the client device accesses content that has been authorized for domain access, it acquires the domain access license from the home server, and the content access license from the license server By instituting a system whereby the content license cannot be accessed without a domain license, content access will require the acquisition of both domain and content access licenses Therefore, the client device will require a content license and a domain license, types of licenses, in order to access content The following are several ways in which a device can be registered to a given domain: BS EN 62227:2008+A1:2013 62227 © IEC:2008+A1:2013(E) – 74 – • upon purchase of a device and storage media, the permission Issuer is notified with the device ID and storage media ID; • place a domain management server within the home and register purchased devices and storage media The process of determining whether or not a given device or storage media belongs to a given domain can be managed as follows: • the permission Issuer manages the process: the device contacts the permission issuer as necessary; • a domain Management server manages the process: the device contacts the domain Management Server as necessary; • the device / storage media itself is aware of the domain it belongs to _ This page deliberately left blank British Standards Institution (BSI) BSI is the independent national body responsible for preparing British Standards and other standards-related publications, information and services It presents the UK view on standards in Europe and at the international level BSI is incorporated by Royal Charter British Standards and other standardisation products are published by BSI Standards Limited Revisions Information on standards British Standards and PASs are periodically updated by amendment or revision Users of British Standards and PASs should make sure that they possess the latest amendments or editions It is the constant aim of BSI to improve the quality of our products and services We would be grateful if anyone finding an inaccuracy or ambiguity while using British Standards would inform the Secretary of the technical committee responsible, the identity of which can be found on the inside front cover Similary for PASs, please notify BSI Customer Services Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 BSI provides a wide range of information on national, European and international standards through its Knowledge Centre BSI offers BSI Subscribing Members an individual updating service called PLUS which ensures that subscribers automatically receive the latest editions of British Standards and PASs Tel: +44 (0)20 8996 7669 Fax: +44 (0)20 8996 7001 Email: plus@bsigroup.com Buying standards You may buy PDF and hard copy versions of standards directly using a credit card from the BSI Shop on the website www.bsigroup.com/shop In addition all orders for BSI, international and foreign standards publications can be addressed to BSI Customer Services Tel: +44 (0)20 8996 9001 Fax: +44 (0)20 8996 7001 Email: orders@bsigroup.com In response to orders for international standards, BSI will supply the British Standard implementation of the relevant international standard, unless otherwise requested Tel: +44 (0)20 8996 7004 Fax: +44 (0)20 8996 7005 Email: knowledgecentre@bsigroup.com BSI Subscribing Members are kept up to date with standards developments and receive substantial discounts on the purchase price of standards For details of these and other benefits contact Membership Administration Tel: +44 (0)20 8996 7002 Fax: +44 (0)20 8996 7001 Email: membership@bsigroup.com Information regarding online access to British Standards and PASs via British Standards Online can be found at www.bsigroup.com/BSOL Further information about British Standards is available on the BSI website at www.bsi-group.com/standards Copyright All the data, software and documentation set out in all British Standards and other BSI publications are the property of and copyrighted by BSI, or some person or entity that own copyright in the information used (such as the international standardisation bodies) has formally licensed such information to BSI for commerical publication and use Except as permitted under the Copyright, Designs and Patents Act 1988 no extract may be reproduced, stored in a retrieval system or transmitted in any form or by any means – electronic, photocopying, recording or otherwise – without prior written permission from BSI This does not preclude the free use, in the course of implementing the standard, of necessary details such as symbols, and size, type or grade designations If these details are to be used for any other purpose than implementation then the prior written permission of BSI must be obtained Details and advice can be obtained from the Copyright & Licensing Department Tel: +44 (0)20 8996 7070 Email: copyright@bsigroup.com BSI 389 Chiswick High Road London W4 4AL UK Tel +44 (0)20 8996 9001 Fax +44 (0)20 8996 7001 www.bsigroup.com/standards raising standards worldwide™

Ngày đăng: 15/04/2023, 10:24