1、 ETSI TS 102 474 V1.1.1 (2007-11)Technical Specification Digital Video Broadcasting (DVB);IP Datacast over DVB-H: Service Purchase and ProtectionEuropean Broadcasting Union Union Europenne de Radio-Tlvision EBUUER ETSI ETSI TS 102 474 V1.1.1 (2007-11) 2 Reference DTS/JTC-DVB-190 Keywords broadcastin
2、g, data, digital, DVB, IP, video ETSI 650 Route des Lucioles 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 cop
3、ies of the present document can be downloaded from: http:/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
4、(PDF). In case of dispute, the reference shall be the printing 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 stat
5、us of this and other ETSI documents is available at http:/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 excep
6、t as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2007. European Broadcasting Union 2007. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for t
7、he benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 474 V1.1.1 (2007-11) 3 Contents
8、 Intellectual Property Rights11 Foreword.11 Introduction 11 1 Scope 12 2 References 12 2.1 Normative references .12 2.2 Informative references14 3 Definitions, symbols and abbreviations .14 3.1 Definitions14 3.2 Symbols17 3.3 Abbreviations .18 4 System overview 20 4.1 Hierarchical Model for Content/
9、Service Protection (Informative).20 4.2 The two approaches (informative)22 4.3 Use of the IP Datacast Specification for Service Purchase and Protection (normative).22 5 Signalling of Service Purchase and Protection System (normative) 23 5.1 ESG signalling23 5.2 SDP signalling24 6 Protection of conte
10、nt and media streams (normative)24 6.1 IPsec .24 6.1.1 Selectors24 6.1.2 Encapsulation protocol and mode.24 6.1.3 Encryption algorithm 25 6.1.4 Authentication algorithm 25 6.1.5 Security Association Management .25 6.2 ISMA Encryption and authentication (ISMACryp) .25 6.2.1 Streamed Content25 6.2.2 D
11、ownloadable Audio/Visual content (stored in MP4 files)26 6.3 SRTP 26 6.3.1 Key management 27 6.3.2 Encryption algorithm 27 6.3.3 Authentication algorithm 27 Annex A (normative): IPDC SPP Open Security Framework.28 A.1 Introduction 28 A.2 DVB IPDC over DVB-H System Architecture31 A.2.1 Overview 31 A.
12、2.2 Content and Service Protection Architecture .32 A.2.2.1 Key Management System (KMS).32 A.2.2.1.1 Registration .32 A.2.2.1.2 Authorization and Rights Issuing32 A.2.2.1.3 Content/Service Protection32 A.2.2.1.4 Copy Protection.33 A.2.2.2 Scrambler33 A.2.2.3 Key Management System Device Agent (KDA)3
13、3 A.2.2.4 Descrambler33 A.2.2.5 UICC.33 A.2.2.6 Session Setup34 A.3 IPDC security mechanisms 34 A.3.1 Entitlement Management Message (EMM) stream34 ETSI ETSI TS 102 474 V1.1.1 (2007-11) 4 A.3.1.1 EMM stream transport and signalling.34 A.3.1.1.1 KMSType Syntax35 A.3.1.1.2 KMSType Semantics 35 A.3.2 E
14、ntitlement Control Message (ECM) stream .35 A.3.2.1 ECM Stream transport and signalling.36 A.3.2.2 ECM stream binding.36 A.3.3 Key Management and IPsec .36 A.3.4 Key management and ISMACryp 37 A.3.5 Key Management and SRTP 37 A.4 SimulCrypt signalling for OMA-DCF files38 A.4.1 Overview 38 A.4.2 Encr
15、yption and signalling.38 A.4.2.1 OMA DCF adaptation.39 A.5 Roaming .40 A.5.1 Roaming Overview.40 A.5.2 Security Architecture41 A.5.2.1 Registration.41 A.5.2.2 Authorization 41 A.5.2.3 Rights Management 42 A.5.2.4 Key Stream .42 A.5.2.5 Content protection 42 A.5.3 Key management and distribution42 A.
16、5.3.1 Roaming PKI infrastructure42 A.5.3.2 Daily encryption keys .43 A.5.3.3 Service Encryption Keys 43 A.5.3.4 Traffic Encryption Keys .43 A.5.4 Key Generation and Validation at the Device 43 A.5.5 Roaming messages .44 A.5.5.1 Device Roaming Request44 A.5.5.2 Roaming request .44 A.5.5.3 Roaming Req
17、uest Response45 A.5.5.4 Roaming initial EMM.46 A.5.5.5 Roaming service EMM.46 A.5.5.6 Roaming Service ECM .47 A.6 UICC 48 A.6.1 Application IDentifier (AID)48 A.6.2 KMS Application Selection49 A.7 Secure Authenticated Channel Protocol.49 A.7.1 High level description of the SAC49 A.7.2 The cryptograp
18、hic keys and parameters .50 A.7.2.1 The Descramblers keys 50 A.7.3 The SAC protocol.50 A.7.3.1 Session key establishment 50 A.7.3.2 Secure key exchange.50 A.8 Adaptation of DVB Simulcrypt interfaces to the DVB-H Environment50 A.8.1 Reference DVB-Headend Architecture 51 A.8.2 DVB-H Headend Architectu
19、re and Interfaces52 A.8.3 DVB-H Headend Architecture for Roaming Support.53 A.8.3.1 Roaming ECMs 53 A.8.3.2 Roaming EMMs53 A.9 Mobile Device Security Framework 54 A.9.1 Key Management System Device Agent54 A.9.1.1 Overview 54 A.9.1.2 J2ME Mobile Information Device Profile (MIDP).55 A.9.2 KDA Platfor
20、m 55 A.9.2.1 Interactivity Channel.56 A.9.3 Security Background 56 A.9.4 KDA APIs 57 ETSI ETSI TS 102 474 V1.1.1 (2007-11) 5 A.9.4.1 UICC.57 A.9.4.2 Generic Connection Framework.57 A.9.4.3 Descrambler57 A.9.4.3.1 Descrambler interface .57 A.9.4.3.2 DescramblerContext interface.58 A.9.5 The KDA Life
21、Cycle 59 A.9.5.1 Loading a new KDA.59 A.9.6 UICC - KMS Application Selection.59 Annex B (normative): 18Crypt .61 B.1 System Overview .61 B.1.1 General description of the system and elements.61 B.1.1.1 Selected technologies61 B.1.1.2 Overview of Operation .63 B.1.2 The End-to-End System .64 B.1.3 Mod
22、es of Operation and Types of Device65 B.1.3.1 Unconnected Devices .65 B.1.3.2 Scalability Considerations 66 B.1.4 Purchase steps 67 B.1.5 Consumption Steps.70 B.1.6 Service Protection vs. Content Protection 72 B.2 Theory of operation73 B.2.1 End-to-end architecture 73 B.2.1.1 Void 74 B.2.1.2 Special
23、 cases .74 B.2.1.2.1 Free-To-Air Services.74 B.2.1.2.2 Free-To-View Services .75 B.2.2 Electronic Service Guide and Purchase75 B.2.3 Registration 76 B.2.3.1 Concept of the RI context .76 B.2.3.2 Registration for interactive mode of operation .76 B.2.3.3 Registration for broadcast (only) mode of oper
24、ation 76 B.2.3.4 Mixed-mode registration for interactive and broadcast modes of operation.78 B.2.4 The Four Layer Model .79 B.2.4.1 Key Hierarchy.79 B.2.4.1.1 Keys on the Traffic Layer .79 B.2.4.1.2 Keys on the Key Stream Layer .79 B.2.4.1.2.1 Service based subscription.79 B.2.4.1.2.2 Pay-per view b
25、ased and service based subscription 80 B.2.4.1.2.3 Pay-per view based consumption 81 B.2.4.1.3 Keys on the Rights Management Layer (Broadcast mode).81 B.2.4.1.4 Keys on the Rights Management Layer (Interactive mode)82 B.2.4.1.5 Keys on the Registration Layer (Broadcast mode)82 B.2.4.1.6 Authenticati
26、on overview .83 B.2.4.1.6.1 Authentication keys on traffic layer 84 B.2.4.1.6.2 Authentication keys on key stream layer.84 B.2.4.1.6.3 Authentication keys on rights management layer (broadcast mode) .85 B.2.4.1.6.4 Authentication keys on registration layer (broadcast mode) .85 B.2.5 Deployment for i
27、nteractive mode of operation.85 B.2.5.1 Concept of Domains - OMA DRM 2.0 Domains .85 B.2.6 Deployment for broadcast mode of operation 85 B.2.6.1 Concept of Domains - broadcast domains 85 B.2.6.2 Addressing (group / subset / device / domain)85 B.2.6.2.1 Addressing the unique group.86 B.2.6.2.2 Addres
28、sing a subscriber group 87 B.2.6.2.3 Addressing a unique device.87 B.2.6.2.4 Addressing a broadcast domain.88 B.2.6.3 Zero Message Broadcast Encryption scheme .88 B.2.7 Interoperability with Alternative Implementations of the Functionality of Rights Management Layer and Registration Layer 90 ETSI ET
29、SI TS 102 474 V1.1.1 (2007-11) 6 B.3 The Four-Layer Model for Service and Content Protection.91 B.3.1 Traffic Layer 91 B.3.1.1 IPsec91 B.3.1.2 ISMACryp 92 B.3.1.3 SRTP.92 B.3.2 Key Stream Layer.93 B.3.2.1 Key Stream Message (KSM) 93 B.3.2.1.1 Descriptors for access_criteria_descriptor_loop .95 B.3.2
30、.1.2 Constants.97 B.3.2.1.3 Coding and Semantics of Attributes97 B.3.2.2 Key Stream Discovery102 B.3.3 Rights Management Layer .102 B.3.3.1 Requirements for Service ROs103 B.3.3.2 Requirements for Programme ROs.103 B.3.3.3 Delivery of ICROs over Interactivity Channel .104 B.3.3.4 Delivery of BCROs o
31、ver Broadcast Channel .104 B.3.3.4.1 Broadcast of BCRO Objects .104 B.3.3.4.2 Format of a Broadcast Rights Object (BCRO)104 B.3.3.4.2.1 Format of the asset object107 B.3.3.4.2.2 Format of the permission object 109 B.3.3.4.2.3 Format of the action object109 B.3.3.4.2.4 Format of the constraint object
32、110 B.3.4 Registration Layer 114 B.3.4.1 RI Context.114 B.3.4.2 Interactive mode of operation .114 B.3.4.3 Broadcast mode of operation 114 B.3.4.3.1 Protocol overview .114 B.3.4.3.2 Offline Notification of Detailed Devicedata protocol.115 B.3.4.3.3 offline Notification of Short Devicedata protocol.1
33、16 B.3.4.3.3.1 Request re-registration (only at same RI)118 B.3.4.3.3.2 Request join domain118 B.3.4.3.3.3 Request leave domain118 B.3.4.3.3.4 Token consumption report.118 B.3.4.3.3.5 Notify DRM time drift.119 B.3.4.3.3.6 Token request 119 B.3.4.3.4 1-pass binary Push Device Registration Protocol .1
34、19 B.3.4.3.5 1-pass binary Inform Registered Device Protocol.120 B.3.4.3.5.1 Force re-registration 120 B.3.4.3.5.2 Update RI certificate121 B.3.4.3.5.3 Update DRM_Time .121 B.3.4.3.5.4 Update contact number121 B.3.4.3.5.5 Force to join a domain.122 B.3.4.3.5.6 Force to leave a domain.122 B.3.4.3.5.7
35、 update a domain.122 B.3.4.3.6 Unique Device Number (UDN) protocol 122 B.3.4.3.6.1 Message syntax123 B.3.4.3.7 Binary messages124 B.3.4.3.7.1 Device data - device_data_inform() message124 B.3.4.3.7.2 Registration data - device_registration_response() message .124 B.3.4.3.7.3 (Force to) Re-register -
36、 re_register_msg() message.133 B.3.4.3.7.4 Update RI certificate - update_ri_certificate_msg() message137 B.3.4.3.7.5 Updating the DRM time - update_drmtime_msg() message .137 B.3.4.3.7.6 Update the contact number - update_contact_number_msg() message.138 B.3.4.4 Domain joining and leaving143 B.3.4.
37、4.1 Protocol overview .143 B.3.4.4.2 offline Domain Join Request.144 B.3.4.4.3 offline Domain Leave Request144 B.3.4.4.4 Binary messages144 B.3.4.4.4.1 Domain data - domain_registration_response() message 144 B.3.4.4.4.2 Updating a domain - domain_update_response() message150 B.3.4.4.4.3 (Force to)
38、Join a domain - join_domain_msg() message.153 B.3.4.4.4.4 (Force to) Leave a domain - leave_domain_msg() message .154 ETSI ETSI TS 102 474 V1.1.1 (2007-11) 7 B.3.4.5 Token handling .154 B.3.4.5.1 Protocol overview .154 B.3.4.5.2 token request protocol.155 B.3.4.5.3 token reporting protocol155 B.3.4.
39、5.4 Binary messages155 B.3.4.5.4.1 delivering tokens - token_delivery_response() message .155 B.4 Rights Issuer Services 161 B.4.1 Expected Mode of Operation161 B.4.2 Scheduled RI Stream162 B.4.3 Ad-hoc RI Stream.163 B.4.4 In-Band RI Streams within a Media Service 163 B.4.5 Broadcast Format of RI St
40、reams 163 B.4.5.1 IP Characteristics 163 B.4.5.2 RI Stream Packet Format163 B.4.5.3 Implementation notes165 B.4.5.3.1 Unreliable delivery165 B.4.5.3.2 Changes in packet order165 B.4.5.3.3 Addressing of objects165 B.4.6 Mapping of messages to RI services and streams 165 B.4.6.1 Rights issuer services
41、 with complete schedule information166 B.4.6.2 Rights issuer services without complete schedule information 166 B.4.7 Discovery of RI services, streams and schedule information.166 B.4.8 Certificate Chain Updates 166 B.4.9 Resending of BCROs .167 B.4.9.1 Resending of BCROs to interactive devices .16
42、7 B.4.9.2 Resending of BCROs to broadcast devices.167 B.4.10 Summary of requirements for Rights Issuers .168 B.4.11 Summary of Requirements for Devices168 B.5 Service Subscription and Purchase.169 B.5.1 Purchase over the interactivity channel 171 B.5.1.1 Typical purchase sequences171 B.5.1.1.1 Bulk
43、download of service and program keys 171 B.5.1.1.2 Bulk download of purchase information.172 B.5.1.1.3 Announcement of Purchase Items in Service Guide .173 B.5.1.1.4 Pricing inquiry.174 B.5.1.1.5 Unsuccessful purchase 175 B.5.1.1.6 Successful purchase 179 B.5.1.1.7 Subscription RO Renewal and Asynch
44、ronous Charging.182 B.5.1.1.8 Asynchronous Charging and Cancellation of Open-Ended Subscriptions 185 B.5.1.1.9 Purchase of Tokens for Consumption-based Charging .186 B.5.1.2 Protocol.189 B.5.1.2.1 HTTP headers .189 B.5.1.2.2 Signatures189 B.5.1.3 XML Schemas for Request and Response Messages .189 B.
45、5.1.3.1 Basic Types.189 B.5.1.3.1.1 User Data Type190 B.5.1.3.1.2 Device Data Type190 B.5.1.3.1.3 Domain Type.190 B.5.1.3.1.4 ServiceOperatorCentreType 190 B.5.1.3.1.5 PriceType.191 B.5.1.3.1.6 Purchase Item Type .191 B.5.1.3.1.7 Request Type.192 B.5.1.3.1.8 Response Type 192 B.5.1.3.2 Error Codes .
46、193 B.5.1.3.3 Pricing Request .194 B.5.1.3.3.1 XML Schema 194 B.5.1.3.3.2 Example.195 B.5.1.3.4 Pricing Response.195 B.5.1.3.4.1 XML Schema 195 B.5.1.3.4.2 Example: Successful Pricing Response .196 ETSI ETSI TS 102 474 V1.1.1 (2007-11) 8 B.5.1.3.5 Purchase Request 196 B.5.1.3.5.1 Schema 196 B.5.1.3.
47、5.2 Example.197 B.5.1.3.6 Purchase Response197 B.5.1.3.6.1 XML Schema 197 B.5.1.3.6.2 Example: Successful Purchase Response with RO Acquisition Trigger .198 B.5.1.3.6.3 Example: Unsuccessful Purchase Response with Registration Trigger.198 B.5.1.3.6.4 Example: Unsuccessful Purchase Response with Purc
48、hase-Item-specific Error.198 B.5.1.3.7 Subscription RO Renewal Request .198 B.5.1.3.7.1 XML Schema 198 B.5.1.3.7.2 Example.199 B.5.1.3.8 Subscription RO Renewal Response.199 B.5.1.3.8.1 Schema 199 B.5.1.3.8.2 Example: Successful Renewal Response with RO Acquisition Trigger200 B.5.1.3.8.3 Example: Un
49、successful Renewal Response with Registration Trigger .200 B.5.1.3.8.4 Example: Unsuccessful Renewal Response with Purchase-Item-specific Error .200 B.5.1.3.9 Subscription Cancellation Request200 B.5.1.3.9.1 XML Schema 200 B.5.1.3.9.2 Example.201 B.5.1.3.10 Subscription Cancellation Response .201 B.5.1.3.10.1 Schema 201 B.5.1.3.10.2 Example: Successful Cancellation Response 202 B.5.1.3.10.3 Example: Unsuccessful Cancellation Response With Purchase-Item-specific Error 202 B.5.1.3.11 Token Request.202 B.5.1.3.11.1 XML Schema 202 B.5.1.3.11.2 Example.203 B.5.1.3.12 Token Resp
