1、 ETSI TR 102 825-8 V1.1.2 (2011-02)Technical Report Digital Video Broadcasting (DVB);Content Protection and Copy Management (DVB-CPCM);Part 8: CPCM Authorized Domain Management scenariosETSI ETSI TR 102 825-8 V1.1.2 (2011-02)2Reference RTR/JTC-DVB-252-8 Keywords broadcast, DVB ETSI 650 Route des Luc
2、ioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: htt
3、p:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall be the p
4、rinting on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at htt
5、p:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright an
6、d the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2011. European Broadcasting Union 2011. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of
7、 its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks register
8、ed and owned by the GSM Association. ETSI ETSI TR 102 825-8 V1.1.2 (2011-02)3Contents Intellectual Property Rights 5g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g32.1 Normative references . 6g32.2 Informative references 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbre
9、viations . 6g34 Informative Authorized Domain Management (ADM) scenarios 7g34.1 Scenario 1 - Solitary Device Initialization . 7g34.1.1 Entry Conditions . 7g34.1.2 Process 7g34.1.3 Information Flows 7g34.1.4 Exit Conditions . 8g34.2 Scenario 2 - Two Blank Devices 8g34.2.1 Use Case . 8g34.2.2 Entry Co
10、nditions . 8g34.2.3 Process 8g34.2.4 Information Flows 9g34.2.5 Exit Conditions . 9g34.3 Scenario 3 - Basic AD Join 9g34.3.1 Use Case . 9g34.3.2 Entry Conditions . 9g34.3.3 Process 9g34.3.4 Information Flows 10g34.3.5 Exit Conditions . 11g34.4 Scenario 4 - Remote AD Join . 11g34.4.1 Use Case . 11g34
11、.4.2 Entry Conditions . 11g34.4.3 Process 12g34.4.4 Information Flows 12g34.4.5 Exit Conditions . 13g34.5 Scenario 5 - AD Join by Invitation . 13g34.5.1 Use Case . 13g34.5.2 Entry Conditions . 13g34.5.3 Process 14g34.5.4 Information Flows 14g34.5.5 Exit Conditions . 14g34.6 Scenario 6 - Subsequent D
12、evice Joining 15g34.6.1 Use Case . 15g34.6.2 Entry Conditions . 15g34.6.3 Process 15g34.6.4 Information Flows 15g34.6.5 Exit Conditions . 16g34.7 Scenario 7 - Device Joining with Multiple ADs available . 16g34.7.1 Use Case . 16g34.7.2 Entry Conditions . 16g34.7.3 Process 16g34.7.4 Information Flows
13、17g34.7.5 Exit Conditions . 17g34.8 Scenario 8 - Device Reconnection . 18g3ETSI ETSI TR 102 825-8 V1.1.2 (2011-02)44.8.1 Use Case . 18g34.8.2 Entry Conditions . 18g34.8.3 Process 18g34.8.4 Information Flows 18g34.8.5 Exit Conditions . 18g34.9 Scenario 9 - Remove a Device from the AD 19g34.9.1 Use Ca
14、se . 19g34.9.2 Entry Conditions . 19g34.9.3 Process 19g34.9.4 Information Flows 20g34.9.5 Exit Conditions . 23g34.10 Scenario 10 - AD naming/renaming . 23g34.10.1 Use Case . 23g34.10.2 Entry Conditions . 23g34.10.3 Process 23g34.10.4 Information Flows 24g34.10.5 Exit Conditions . 24g34.10.6 Notes .
15、24g34.11 Scenario 11 - Changing the Local Master 24g34.11.1 Use Case . 24g34.11.2 Entry Conditions . 24g34.11.3 Process 25g34.11.4 Information Flows 25g34.11.5 Exit Conditions . 25g34.12 Scenario 12 - Changing the Domain Controller . 26g34.12.1 Use Case . 26g34.12.2 Entry Conditions . 26g34.12.3 Pro
16、cess 26g34.12.4 Information Flows 27g34.12.5 Exit Conditions . 27g34.13 Scenario 13 - Splitting the Domain Controller function . 27g34.13.1 Use Case . 27g34.13.2 Entry Conditions . 27g34.13.3 Process 28g34.13.4 Information Flows 28g34.13.5 Exit Conditions . 29g34.14 Scenario 14 - Merging Domain Cont
17、roller functions . 29g34.14.1 Use Case . 29g34.14.2 Entry Conditions . 29g34.14.3 Process 29g34.14.4 Information Flows 30g34.14.5 Exit Conditions . 30g34.15 Scenario 15 - Rebalancing Domain Controllers . 30g34.15.1 Use Case . 30g34.15.2 Entry Conditions . 30g34.15.3 Process 31g34.15.4 Information Fl
18、ows 31g34.15.5 Exit Conditions . 32g3History 34g3ETSI ETSI TR 102 825-8 V1.1.2 (2011-02)5Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for
19、ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/
20、webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may b
21、ecome, essential to the present document. Foreword This Technical Report (TR) has been produced by Joint Technical Committee (JTC) Broadcast of the European Broadcasting Union (EBU), Comit Europen de Normalisation ELECtrotechnique (CENELEC) and the European Telecommunications Standards Institute (ET
22、SI). NOTE: The EBU/ETSI JTC Broadcast was established in 1990 to co-ordinate the drafting of standards in the specific field of broadcasting and related fields. Since 1995 the JTC Broadcast became a tripartite body by including in the Memorandum of Understanding also CENELEC, which is responsible fo
23、r the standardization of radio and television receivers. The EBU is a professional association of broadcasting organizations whose work includes the co-ordination of its members activities in the technical, legal, programme-making and programme-exchange domains. The EBU has active members in about 6
24、0 countries in the European broadcasting area; its headquarters is in Geneva. European Broadcasting Union CH-1218 GRAND SACONNEX (Geneva) Switzerland Tel: +41 22 717 21 11 Fax: +41 22 717 24 81 The Digital Video Broadcasting Project (DVB) is an industry-led consortium of broadcasters, manufacturers,
25、 network operators, software developers, regulatory bodies, content owners and others committed to designing global standards for the delivery of digital television and data services. DVB fosters market driven solutions that meet the needs and economic circumstances of broadcast industry stakeholder
26、s and consumers. DVB standards cover all aspects of digital television from transmission through interfacing, conditional access and interactivity for digital video, audio and data. The consortium came together in 1993 to provide global standardisation, interoperability and future proof specificatio
27、ns. The present document is part 8 of a multi-part deliverable. Full details of the entire series can be found in part 1 i.3. Introduction CPCM is a system for Content Protection and Copy Management of commercial digital content delivered to consumer products. CPCM manages content usage from acquisi
28、tion into the CPCM system until final consumption, or export from the CPCM system, in accordance with the particular usage rules of that content. Possible sources for commercial digital content include broadcast (e.g. cable, satellite, and terrestrial), Internet-based services, packaged media, and m
29、obile services, among others. CPCM is intended for use in protecting all types of content - audio, video and associated applications and data. CPCM specifications facilitate interoperability of such content after acquisition into CPCM by networked consumer devices for both home networking and remote
30、 access. This first phase of the specification addresses CPCM for digital Content encoded and transported by linear transport systems in accordance with TS 101 154 i.1. A later second phase will address CPCM for Content encoded and transported by systems that are based upon Internet Protocols in acc
31、ordance with TS 102 005 i.2. ETSI ETSI TR 102 825-8 V1.1.2 (2011-02)61 Scope The present document specifies the Scenarios that are envisaged for the Digital Video Broadcasting (DVB) Content Protection and Copy Management (CPCM) system. It is provided for informative purposes only and will be revised
32、 in due course as more scenarios are defined. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the refer
33、ence document (including any amendments) applies. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarant
34、ee their long term validity. 2.1 Normative references The following referenced documents are necessary for the application of the present document. Not applicable. 2.2 Informative references The following referenced documents are not necessary for the application of the present document but they ass
35、ist the user with regard to a particular subject area. i.1 ETSI TS 101 154: “Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in Broadcasting Applications based on the MPEG-2 Transport Stream“. i.2 ETSI TS 102 005: “Digital Video Broadcasting (DVB); Specification
36、 for the use of Video and Audio Coding in DVB services delivered directly over IP protocols“. i.3 ETSI TS 102 825-1: “Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 1: CPCM Abbreviations, Definitions and Terms“. 3 Definitions and abbreviations 3.1 Definitio
37、ns For the purposes of the present document, the terms and definitions given in TS 102 825-1 i.3 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TS 102 825-1 i.3 apply. ETSI ETSI TR 102 825-8 V1.1.2 (2011-02)74 Informative Authorized Domain Management (A
38、DM) scenarios 4.1 Scenario 1 - Solitary Device Initialization Scenario 1 covers the case where a single, Blank Instance (ADM) is activated in isolation from all other CPCM Instances. The Instance is unable to Join an existing AD, so it will perform alone. 4.1.1 Entry Conditions At the beginning of S
39、cenario 1, there is a single device with a Blank ADM Instance. 4.1.2 Process The ADM in Device A is initialized by the Device Application. The ADM in Device A initiates a Discovery process to find an AD to Join. No response is received. ADM asks the Device Application for permission to create a new
40、AD. The ADM implementation generates the ADID and asks the Security Control to create the necessary secret(s). The ADM issues an AD Update Indication to notify other CPCM Instances of the creation of the AD. 4.1.3 Information Flows Figure 1 describes the information flows required for Scenario 1. In
41、itialiseDiscover ReqTimeoutADM-A checks with device application on whether to create a new ADCreate a new AD?YesAD Update Ind.(broadcast)ADM-AApp.Figure 1: Scenario 1 Flows - Solitary Device Initialization ETSI ETSI TR 102 825-8 V1.1.2 (2011-02)84.1.4 Exit Conditions After Scenario 1 has been comple
42、ted, the following conditions apply: The ADM implementation within Device A has an ADID assigned. The Security Control implementation within Device A has security information for the AD assigned and associated with the ADID. 4.2 Scenario 2 - Two Blank Devices 4.2.1 Use Case Scenario 2 covers the cas
43、e where two Blank Devices are activated simultaneously. 4.2.2 Entry Conditions At the beginning of Scenario 2, we have: Blank Device A. Blank Device B. 4.2.3 Process The Device Application in Device A initializes ADM-A. ADM-A initiates a Discovery (broadcast). The Discovery message indicates that th
44、ere is no AD membership. No response. The Device Application in Device B initializes ADM-B. ADM-B initiates a Discovery. ADM-A responds with a Discovery Response but indicates it has no current AD membership. The ADM with the lower Instance ID (ADM-A in this case) asks its Device Application whether
45、 to create a new AD. ADM-A creates the new AD as per scenario 1. ADM-A sends a broadcast AD Update Indication describing the new AD. ADM-B responds to the AD Update Indication by restarting its own Discovery process. The scenario continues as in Scenario 3 below. ETSI ETSI TR 102 825-8 V1.1.2 (2011-
46、02)94.2.4 Information Flows Figure 2 describes the information flows required for Scenario 2. Figure 2: Scenario 2 Flows - Two Blank Devices 4.2.5 Exit Conditions After Scenario 2 has been completed, both devices proceed automatically to Scenario 3. 4.3 Scenario 3 - Basic AD Join This provides the b
47、asis for all AD Joining scenarios. 4.3.1 Use Case Scenario 3 covers the case where one device has already created a single-member AD, and a second blank device is activated. In this case the two devices are Local to each other. 4.3.2 Entry Conditions At the beginning of Scenario 3, we have: ADM-A is
48、 the sole member of AD X. ADM-B is Blank. 4.3.3 Process ADM-B is initialized. ADM-B initiates a Discovery (broadcast, indicating a self-managed AD Join is intended). ADM-A responds with the AD X information. ETSI ETSI TR 102 825-8 V1.1.2 (2011-02)10 ADM-B asks the Device Application to confirm that
49、it should Join AD X. ADM-B commences an AD Join transaction with ADM-A. ADM-A verifies with its own Device Application whether to allow ADM-B to Join the AD. If the Device Application agrees, the following steps are taken. ADM-A runs the ADSE tests to verify that AD growth is acceptable, assumes this is true. ADM-A asks SEC-A to establish a SAC to SEC-B (see figure 4). (Mutual authentication takes place during SAC establishment). ADM-A asks SEC-A to send the AD Secret(s) to SEC-B. ADM-A re
