1、 ETSI TS 102 825-14 V1.1.1 (2011-02)Technical Specification Digital Video Broadcasting (DVB);Content Protection and Copy Management (DVB-CPCM);Part 14: CPCM ExtensionsETSI ETSI TS 102 825-14 V1.1.1 (2011-02)2Reference DTS/JTC-DVB-222-14 Keywords broadcast, DVB ETSI 650 Route des Lucioles F-06921 Sop
2、hia 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: http:/www.etsi.org T
3、he 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 printing on ETSI p
4、rinters 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 http:/portal.etsi.or
5、g/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 and the foregoing r
6、estriction 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 its Members. 3GP
7、PTM 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. ETSI ETSI TS 102 825-14 V1.1.1 (2011-02)3Contents Intellectual
8、 Property Rights 4g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g32.1 Normative references . 5g32.2 Informative references 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 5g34 Introduction 6g35 Interoperability . 6g36 Play Count Extension . 6g36.1 Play Count
9、 Extension definition . 6g36.2 Play Count Data element 7g36.3 Play Count protocols 7g36.4 Content Management . 8g36.4.1 USI setting 8g36.4.2 Device and Content Discovery . 8g36.4.3 CPCM Functional Entity Behaviour . 8g36.4.4 USI Enforcement 8g36.4.4.1 Controls prior to content transfer 8g36.4.4.2 Co
10、ntrols to be enforced when receiving content . 9g36.5 Move Protocol 9g36.6 Content Licence Management 10g36.6.1 Content Licence Generation . 10g36.6.2 Content Licence Verification 10g36.6.3 Content Licence Protection . 10g3History 12g3ETSI ETSI TS 102 825-14 V1.1.1 (2011-02)4Intellectual Property Ri
11、ghts 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 ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essentia
12、l, 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:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has bee
13、n 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 become, essential to the present document. Foreword This Technical Specification (TS) has been produced by Joint T
14、echnical Committee (JTC) Broadcast of the European Broadcasting Union (EBU), Comit Europen de Normalisation ELECtrotechnique (CENELEC) and the European Telecommunications Standards Institute (ETSI). NOTE: The EBU/ETSI JTC Broadcast was established in 1990 to co-ordinate the drafting of standards in
15、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 for the standardization of radio and television receivers. The EBU is a professional association of broadcas
16、ting 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 60 countries in the European broadcasting area; its headquarters is in Geneva. European Broadcasting Union
17、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, network operators, software developers, regulatory bodies, content owners and others committed to designi
18、ng 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 stakeholders and consumers. DVB standards cover all aspects of digital television from transmission through interfaci
19、ng, conditional access and interactivity for digital video, audio and data. The consortium came together in 1993 to provide global standardisation, interoperability and future proof specifications. The present document is part 14 of a multi-part deliverable. Full details of the entire series can be
20、found in part 1 1. Introduction CPCM is a system for Content Protection Content Protection and Copy Management (DVB-CPCM); Part 1: CPCM Abbreviations, Definitions and Terms“. 2 ETSI TS 102 825-4: “Digital Video Broadcasting (DVB); Content Protection and Copy Management (DVB-CPCM); Part 4: CPCM Syste
21、m Specification“. 2.2 Informative references The following referenced documents are not necessary for the application of the present document but they assist 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
22、and Audio Coding in Broadcasting Applications based on the MPEG-2 Transport Stream“. i.2 ETSI TS 102 005: “Digital Video Broadcasting (DVB); Specification for the use of Video and Audio Coding in DVB services delivered directly over IP protocols“. i.3 ETSI TR 102 825-12: “ Digital Video Broadcasting
23、 (DVB); Content Protection and Copy Management (DVB-CPCM); Part 12: CPCM Implementation Guidelines 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 102 825-1 1 apply. 3.2 Abbreviations For the purposes of the present docu
24、ment, the abbreviations given in TS 102 825-1 1 apply. ETSI ETSI TS 102 825-14 V1.1.1 (2011-02)64 Introduction The CPCM System provides an interoperability platform and common trusted destination for commercial content in the consumer environment. CPCM is a flexible system that can be extended both
25、in a standard way and in a proprietary way. The present document describes CPCM Extensions standardised by DVB together with corresponding extension elements or protocols. Currently, the following standardised CPCM Extensions are defined: Play Count extension Other CPCM Extensions may be defined in
26、a next release of the present document. EXAMPLE: This may happen when an extension is developed after the completion of the Rule Set of a specific C&R Regime. 5 Interoperability A CPCM Extension implementation is optional. A CPCM Instance receiving a CPCM message as described in TS 102 825-4 2 shall
27、 ignore any element relative to an extension it does not contain and shall thus behave as if the extension element was not present. It shall ignore any message dedicated to an extension, such as CPCM_extension_message or CPCM_private_data_message, but may reply with the appropriate error message as
28、defined in TS 102 825-4 2. However, it shall not remove any element relative to an Extension from the Auxiliary Data. Table 1 gives the CPCM Extension Identifiers for CPCM Extensions defined in this specification. Other identifiers are reserved. Table 1: CPCM Extension Identifiers CPCM Extension Nam
29、e CPCM Extension Identifier Play Count 0x0001 6 Play Count Extension 6.1 Play Count Extension definition The purpose of this extension is to limit the number of consecutive plays of a given content item. If USI SVCA is not asserted, any number of simultaneous plays is allowed. If SVCA is asserted, t
30、he number of granted permissions in SVCA determines the maximum number of simultaneous viewings that constitutes one play. This also applies to stored CPCM content. EXAMPLE: If SVCA is 2,5 concurrent viewings will be considered as 3 plays. The definition of what constitutes one play is out of the sc
31、ope of the present document and left to CPCM C&R Regimes to determine. ETSI ETSI TS 102 825-14 V1.1.1 (2011-02)76.2 Play Count Data element Play count extension makes use of one extension data element CPCM_play_count_data_element. This, data element is composed of two fields: CPCM_play_limit and CPC
32、M_play_remaining. CPCM_play_limit is an 8-bit integer that, when inserted in a CPCM Auxiliary Data relative to a CPCM Content Licence, gives the original play count for the associated Content Item. CPCM_play_remaining is an 8-bit integer that, when inserted in a CPCM Auxiliary Data relative to a CPC
33、M Content Licence, gives the remaining play count for the associated Content Item. Alternatively, when used in the Move protocol, CPCM_play_remaining expresses the number of plays that are being moved to the other device, as described in clause 6.4.5. EXAMPLE: The system is able to inform the user t
34、hat they still have 3 plays remaining out of the original 5 using the two extensions data elements. Play count data extension does not use any other extension data element. The format of CPCM_play_count_data_element is shown in Table 2. Table 2: CPCM Content Licence Identifier Syntax Bits Identifier
35、 CPCM_play_count_data_element() CPCM_play_limit 8 uimsbf CPCM_play_remaining 8 uimsbf Semantics for CPCM_content_licence_identifier: CPCM_play_limit: This field indicates the original play count for the associated content item. CPCM_play_remaining: This field indicates the remaining or the requested
36、 play count for the associated content item. 6.3 Play Count protocols There are no protocols specific to the play count Extension. Play count extension affects the Move protocol. This protocol can be used to move content with a partial amount of the outstanding authorised plays to another Storage En
37、tity. To that end, play count data element shall be inserted in the optional part, as described in TS 102 825-4 2 of the following messages: CPCM Content Licence Move Invite: In this message, CPCM_play_remaining field in the CPCM_play_count_data_element which is inserted in the message extension ind
38、icates the number of plays that are invited to be moved. If this number is greater than the outstanding counts, all the counts will be moved. CPCM Content Licence Move Begin: In this message CPCM_play_remaining field in the CPCM_play_count_data_element which is inserted in the message extension indi
39、cates the number of plays that are proposed to be moved. CPCM Content Licence Move Request: In this message CPCM_play_remaining field in the CPCM_play_count_data_element which is inserted in the message extension indicates the number of plays that are eventually requested. If all the outstanding pla
40、y counts are to be moved, there is no need to use the Play Count Extension element in the above messages since the relevant information is already included in the content licence that is to be moved. Play Count extension shall be added also in the following message: CPCM Instance Enquiry Response me
41、ssage: If the Instance implements the Play Count extension, it shall insert in the conditional part of the message CPCM Extension element with no data. ETSI ETSI TS 102 825-14 V1.1.1 (2011-02)8 CPCM Discovery Response message: If the Instance implements the Play Count extension, it shall insert in t
42、he conditional part of the message CPCM Extension element with no data. Play Count Extension Element shall be ignored when inserted in any other messages. 6.4 Content Management 6.4.1 USI setting The Play Count extension may be used in conjunction with any USI settings. However, when used with the f
43、ollowing USI, the Play Count extension can no more be enforced: If Copy Control Information is set to Copy Control Not Asserted, any number of copies may be made by any CPCM Instance, including a CPCM Instance that does not implement the Extension. Consequently, the number of authorised plays can no
44、 longer be effectively controlled. If Copy Control Information is set to Copy Never, the content cannot be stored. Thus, the play count is equivalent to SVCA control and not useful. If Viewable is asserted, any Consumption Point, including an Instance that does not implement the Extension, shall be
45、able to play the content, if authorised by the USI. Thus, the count control cannot be accurate. The assumption in this specification is that Play Count restricted content is always used with Viewable not asserted and with CCI set to “Copy Once“ at the Acquisition Point or “Copy No More“ after the fi
46、rst recording. 6.4.2 Device and Content Discovery The presence of Play Count Extension in Auxiliary Data shall be signalled with other present Auxiliary Data. In addition to advertising the content as “Not Viewable“ with “Copy Once“ or with “Copy No More“, as described in clause 6.4.1, and play coun
47、t extension, Storage Entities and Acquisition Points shall also advertise the content as “Viewable“ with “Copy No More“ to enable interoperability with Instances that do not implement the Extension. .A CPCM Instance implementing the Play Count Extension shall signal it in CPCM Enquiry Response and C
48、PCM Discovery Response messages. 6.4.3 CPCM Functional Entity Behaviour A CPCM Instance that does not support this extension shall ignore it and enforce the USI as if the Extension was not present. Only CPCM Acquisition Points and Storage Entities shall adopt a specific behaviour with regard to Play
49、 Count Extension. This specific behaviour concerns the USI enforcement step, as described in clause 6.4.4. 6.4.4 USI Enforcement 6.4.4.1 Controls prior to content transfer All the controls related to the USI setting shall be performed with exception to the “Viewable“ USI that can be sourced to Consumption Points or Export Point under the conditions described below. The behaviour described below regards only Acquisition Points or Storage Entities implementing the Extension. All other Acquisition Point and Storage Entities shall enforc
