{"id":228672,"date":"2024-10-19T14:52:09","date_gmt":"2024-10-19T14:52:09","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-624552011\/"},"modified":"2024-10-25T08:58:04","modified_gmt":"2024-10-25T08:58:04","slug":"bs-en-624552011","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-624552011\/","title":{"rendered":"BS EN 62455:2011"},"content":{"rendered":"
IEC 62455:2010(E) specifies the terminal for a service purchase and protection system for digital broadcasts, called the 18Crypt system. It is applicable in all countries and regions with suitably compliant broadcasting and multimedia distribution systems. Guidelines for compatible broadcast services are given in this standard. The service purchase and protection functions operate in a pure broadcast environment that may be combined with a bi-directional interactivity channel. It is applicable to the following broadcast systems: – IP datacast over DVB-H systems; – DVB T\/C\/S systems; – MPEG2 TS-based IP systems; – Non-MPEG2 TS-based IP systems. This second edition cancels and replaces the first edition, published in 2007, and constitutes a technical revision. The main changes with respect to the previous edition are: – Recent developments in DVB and OMA standards caused some incompatibilities, which have been solved in the second edition. – Technical errors have been corrected, missing details added. – References have been updated to the newest available ones.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | 3 Terms, definitions and abbreviations 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 3.2 Symbols <\/td>\n<\/tr>\n | ||||||
27<\/td>\n | 3.3 Abbreviations <\/td>\n<\/tr>\n | ||||||
31<\/td>\n | 3.4 Identifiers assigned by external entities 4 General 4.1 Overview <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 4.2 General description of the system and elements Figures Figure 1 \u2013 System overview <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure 2 \u2013 Service protection via four-layer model <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | 4.3 End-to-end system 4.4 Supported systems and device types Figure 3 \u2013 Highly simplified view of the end-to-end system <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Tables Table 1 \u2013 Supported systems and device types <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | 4.5 Service protection versus content protection Figure 4 \u2013 Service protection versus content protection <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | 5 General specifications 5.1 End-to-end architecture Figure 5 \u2013 Service protection and purchase entities and names (broadcast architecture) <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | Figure 6 \u2013 Public key infrastructure <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | 5.2 Special cases 5.3 Service guide and purchase <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | 5.4 Four-layer model \u2013 Key hierarchy Figure 7 \u2013 Overview of service guide and purchase <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure 8 \u2013 4-layer key hierarchy \u2013 Use of SEK only <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 9 \u2013 4-layer key hierarchy \u2013 Use of PEK and SEK <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Table 2 \u2013 Keyset in the registration data <\/td>\n<\/tr>\n | ||||||
49<\/td>\n | Figure 10 \u2013 Authentication hierarchy <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | 5.5 Deployment for broadcast mode of operation <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Figure 11 \u2013 Explaining the concept of addressing <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Figure 12 \u2013 (Oversimplified) group BCRO Figure 13 \u2013 (Oversimplified) subscriber group BCRO <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Figure 14 \u2013 (Oversimplified) unique device BCRO Figure 15 \u2013 (Oversimplified) broadcast domain BCRO <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | Figure 16 \u2013 Example of a zero message tree with three nodes (keys) <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | 6 Traffic layer 6.1 General 6.2 IPsec <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Figure 17 \u2013 IPsec security association elements <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | 6.3 ISMACryp <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | 6.4 SRTP Figure 18 \u2013 ISMACryp Key Management <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Figure 19 \u2013 SRTP cryptographic context management <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 6.5 MPEG2 TS crypt <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Figure 20 \u2013 MPEG2 transport stream cryptographic context management <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Table 3 \u2013 Definition of transport_scrambling_control bits Table 4 \u2013 Definition of pes_scrambling_control field bits <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure 21 \u2013 Single-key versus dual-key TS over time <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Table 5 \u2013 Descrambling possibility matrix Table 6 \u2013 Supported ciphers for MPEG2 TS Crypt <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 7 Key stream layer 7.1 General 7.2 Format of the key stream message (KSM) <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Table 7 \u2013 Format of key stream message <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Table 8 \u2013 Descriptors for access_criteria_descriptor_loop Table 9 \u2013 Access_criteria_descriptors Table 10 \u2013 Parental_rating access criteria descriptor <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | Table 11 \u2013 Parental rating values for each parental rating type <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | Table 12 \u2013 Copy_control_information access criteria descriptor <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Table 13 \u2013 Bit assignments of copy_control_information_byte Table 14 \u2013 CCI bit assignments Table 15 \u2013 EMI values and content Table 16 \u2013 APS value definitions <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Table 17 \u2013 CIT values and application Table 18 \u2013 RCT values and application <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Table 19 \u2013 Blackout_spotbeam access criteria descriptor Table 20 \u2013 Operator field values and their meaning <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Table 21 \u2013 Constants in key stream message <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Table 22 \u2013 Content_key_index options <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Table 23 \u2013 cipher_mode options <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Table 24 \u2013 Obtaining the content key <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Table 25 \u2013 Traffic key lifetime <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Table\u00a026 \u2013 Values of permissions_category and their meaning <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | 8 Rights management layer 8.1 General 8.2 Identification of rights objects <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | 8.3 Requirements for rights objects <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | 8.4 Format of rights objects Table 27 \u2013 Format of BCRO <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Table 28 \u2013 Address_mode <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Table 29 \u2013 Asset format <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Table 30 \u2013 Asset_type Table 31 \u2013 Mapping of address_mode to keys <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Table 32 \u2013 Mapping of address_mode to keys Table 33 \u2013 Mapping of address_mode to keys <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Table 34 \u2013 Permission format <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Table 35 \u2013 Action format Table 36 \u2013 Action_type <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Table 37 \u2013 Constraint format Table 38 \u2013 Format of constraint_descriptor <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | Table 39 \u2013 Constraint_tag Table 40 \u2013 Format of count_constraint_descriptor Table 41 \u2013 Format of timed_count_constraint_descriptor <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Table 42 \u2013 Format of datetime_constraint_descriptor <\/td>\n<\/tr>\n | ||||||
100<\/td>\n | Table 43 \u2013 Format of interval_constraint_descriptor Table 44 \u2013 Format of accumulated_constraint_descriptor <\/td>\n<\/tr>\n | ||||||
101<\/td>\n | Table 45 \u2013 Format of individual_constraint_descriptor Table 46 \u2013 Id_type Table 47 \u2013 Format of system_constraint_descriptor <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Table 48 \u2013 Format of token_management_constraint_descriptor <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | 9 Registration layer 9.1 General 9.2 RI context <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | 9.3 Registration layer protocols and message specification Table 49 \u2013 Registration types <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Figure 22 \u2013 Registration for broadcast mode of operation with one ROT <\/td>\n<\/tr>\n | ||||||
106<\/td>\n | Figure 23 \u2013 Offline NDD protocol <\/td>\n<\/tr>\n | ||||||
107<\/td>\n | Figure 24 \u2013 Samples of notification displays Figure 25 \u2013 Off-line NSD protocol Figure 26 \u2013 Action request code (ARC) Table 50 \u2013 NSD action request code fields <\/td>\n<\/tr>\n | ||||||
108<\/td>\n | Table 51 \u2013 NSD action types <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Figure 27 \u2013 Samples of notification displays showing an ARC message <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Figure 28 \u2013 Sample of token consumption reporting notification display Table 52 \u2013 Token consumption data <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Figure 29 \u2013 Sample of TAA report display Table 53 \u2013 TAA report data <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Figure 30 \u2013 1-pass PDR protocol \u2013 (first) device registration Figure 31 \u2013 1-pass IRD protocol \u2013 RI initiated message to device (here re-registration) <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Table 54 \u2013 Messages of the 1-pass IRD protocol <\/td>\n<\/tr>\n | ||||||
115<\/td>\n | Figure 32 \u2013 Unique device number Table 55 \u2013 UDN explanation <\/td>\n<\/tr>\n | ||||||
116<\/td>\n | Table 56 \u2013 Major industry identifier Table 57 \u2013 longform_udn <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table 58 \u2013 Notify device data message parameters Table 59 \u2013 Device data <\/td>\n<\/tr>\n | ||||||
118<\/td>\n | Table 60 \u2013 Message fields <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Table 61 \u2013 Status values Table 62 \u2013 Fields of certificate_version parameter <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Table 63 \u2013 Allowed values for ri_certificate_counter <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table 64 \u2013 Allowed values for ocsp_response_counter Table 65 \u2013 Values for flags signalling data absent\/data present <\/td>\n<\/tr>\n | ||||||
122<\/td>\n | Table 66 \u2013 Allowed values for subscriber_group_key_flag Table 67 \u2013 Values and their meaning for signature_type_flag <\/td>\n<\/tr>\n | ||||||
125<\/td>\n | Figure 33 \u2013 Device_registration_response() message <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | Figure 34 \u2013 Structure of device_registration_response() message <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Table 68 \u2013 Message syntax <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | Table 69 \u2013 Message fields <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Table 70 \u2013 Status values Table 71 \u2013 Fields of certificate_version parameter <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Table 72 \u2013 Message syntax <\/td>\n<\/tr>\n | ||||||
133<\/td>\n | Table 73 \u2013 Message fields Table 74 \u2013 Status values <\/td>\n<\/tr>\n | ||||||
134<\/td>\n | Table 75 \u2013 Message syntax <\/td>\n<\/tr>\n | ||||||
135<\/td>\n | Table 76 \u2013 Message fields Table 77 \u2013 Status values <\/td>\n<\/tr>\n | ||||||
136<\/td>\n | Table 78 \u2013 Fields of certificate_version parameter <\/td>\n<\/tr>\n | ||||||
137<\/td>\n | Table 79 \u2013 Message syntax <\/td>\n<\/tr>\n | ||||||
138<\/td>\n | Table 80 \u2013 Format of contact object Table 81 \u2013 Contact_type <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Table 82 \u2013 Encoding rules for contactdata <\/td>\n<\/tr>\n | ||||||
140<\/td>\n | Table 83 \u2013 Off-line protocols (from device to RI) Table 84 \u2013 1-pass protocols (from RI to device) Table 85 \u2013 Protocol interrelation <\/td>\n<\/tr>\n | ||||||
141<\/td>\n | Table 86 \u2013 Message fields <\/td>\n<\/tr>\n | ||||||
142<\/td>\n | Table 87 \u2013 Status values Table 88 \u2013 Fields of certificate_version parameter <\/td>\n<\/tr>\n | ||||||
145<\/td>\n | Figure 35 \u2013 Domain_registration_response() message <\/td>\n<\/tr>\n | ||||||
146<\/td>\n | Figure 36 \u2013 Structure of domain_registration_response() message <\/td>\n<\/tr>\n | ||||||
147<\/td>\n | Table 89 \u2013 Message syntax <\/td>\n<\/tr>\n | ||||||
148<\/td>\n | Table 90 \u2013 Message fields <\/td>\n<\/tr>\n | ||||||
149<\/td>\n | Table 91 \u2013 Status values Table 92 \u2013 Fields of certificate_version parameter <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Table 93 \u2013 Message syntax <\/td>\n<\/tr>\n | ||||||
153<\/td>\n | Table 94 \u2013 Message syntax <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | Table 95 \u2013 Offline protocols (from device to RI) Table 96 \u2013 1-pass protocols (from RI to device) Table 97 \u2013 Protocol interrelation <\/td>\n<\/tr>\n | ||||||
155<\/td>\n | Table 98 \u2013 Fields of token delivery response message <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Table 99 \u2013 Address_mode for token delivery response message <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | Table 100 \u2013 Message error codes <\/td>\n<\/tr>\n | ||||||
159<\/td>\n | Table 101 \u2013 Mapping of address_mode to keys for the token delivery response message Table 102 \u2013 Mapping of address_mode to keys for the token delivery response message <\/td>\n<\/tr>\n | ||||||
160<\/td>\n | Table 103 \u2013 Syntax of token delivery response message <\/td>\n<\/tr>\n | ||||||
162<\/td>\n | 10 Signalling and service guide 10.1 General Figure 37 \u2013 Registration for mixed-mode operation with one ROT <\/td>\n<\/tr>\n | ||||||
163<\/td>\n | 10.2 Signalling requirements 10.3 Service guide requirements 10.4 Service guide recommendations <\/td>\n<\/tr>\n | ||||||
164<\/td>\n | 11 Rights issuer services and rights issuer streams 11.1 General 11.2 Rights issuer services Table 104 \u2013 Requirements for the support of RI services and streams by IPDC over DVBH devices <\/td>\n<\/tr>\n | ||||||
165<\/td>\n | 11.3 Usage of rights issuer streams and services Table 105 \u2013 Requirements for the support of rights issuer services and streams by service providers in IPDC over DVB-H systems <\/td>\n<\/tr>\n | ||||||
166<\/td>\n | Figure 38 \u2013 Relationship between RI service and RI streamsand other services and RI streams <\/td>\n<\/tr>\n | ||||||
168<\/td>\n | 12 Service subscription and purchase 12.1 General Figure 39 \u2013 Message flows for service subscription and purchase for the connected mode of operation <\/td>\n<\/tr>\n | ||||||
169<\/td>\n | 12.2 Purchase over an interactivity channel Figure 40 \u2013 Message flows for service subscription and purchase for the unconnected mode of operation <\/td>\n<\/tr>\n | ||||||
171<\/td>\n | Figure 41 \u2013 Interactions for bulk download of service and programme keys <\/td>\n<\/tr>\n | ||||||
172<\/td>\n | Figure 42 \u2013 Interactions for bulk download of purchase information <\/td>\n<\/tr>\n | ||||||
173<\/td>\n | Figure 43 \u2013 Interactions for announcement of purchase items in service guide <\/td>\n<\/tr>\n | ||||||
174<\/td>\n | Figure 44 \u2013 Interactions for pricing inquiry <\/td>\n<\/tr>\n | ||||||
178<\/td>\n | Figure 45 \u2013 Interactions for unsuccessful purchase <\/td>\n<\/tr>\n | ||||||
182<\/td>\n | Figure 46 \u2013 Interactions for successful purchase <\/td>\n<\/tr>\n | ||||||
186<\/td>\n | Figure 47 \u2013 Interactions for subscription RO renewal and asynchronous charging <\/td>\n<\/tr>\n | ||||||
187<\/td>\n | Figure 48 \u2013 Interactions for asynchronous charging and cancellation of open-ended subscriptions <\/td>\n<\/tr>\n | ||||||
191<\/td>\n | Figure 49 \u2013 Interactions for acquisition and charging of tokens <\/td>\n<\/tr>\n | ||||||
193<\/td>\n | Table 106 \u2013 Definition of mandatory SOC attributes in request\/response messages <\/td>\n<\/tr>\n | ||||||
195<\/td>\n | Table 107 \u2013 Occurrence of error codes in response messages <\/td>\n<\/tr>\n | ||||||
210<\/td>\n | 12.3 Purchase for mixed-mode devices <\/td>\n<\/tr>\n | ||||||
211<\/td>\n | 12.4 Out-of-band purchase <\/td>\n<\/tr>\n | ||||||
212<\/td>\n | Figure 50 \u2013 Samples of out-of-band purchase information displaysfor a registered device Table 108 \u2013 Data to be provided to the customer operation centre <\/td>\n<\/tr>\n | ||||||
213<\/td>\n | 12.5 Required service guide information Figure 51 \u2013 Sample of out-of-band purchase informationdisplays for an unregistered device <\/td>\n<\/tr>\n | ||||||
217<\/td>\n | 13 Protection of IPDC over DVB-H systems 13.1 General <\/td>\n<\/tr>\n | ||||||
218<\/td>\n | 13.2 Delivery of traffic layer data in IPDC over DVB-H systems 13.3 Delivery of key stream data in IPDC over DVB-H systems 13.4 Delivery of rights management data in IPDC over DVB-H systems 13.5 Delivery of registration data in IPDC over DVB-H systems Table 109 \u2013 Traffic layer options for transmission over IPDC over DVB-H <\/td>\n<\/tr>\n | ||||||
219<\/td>\n | 13.6 Signalling and service guides in IPDC over DVB-H systems <\/td>\n<\/tr>\n | ||||||
220<\/td>\n | 13.7 Format and use of RI streams over IPDC over DVB-H systems <\/td>\n<\/tr>\n | ||||||
221<\/td>\n | Figure 52 \u2013 Example mapping of objects to RI stream packets <\/td>\n<\/tr>\n | ||||||
222<\/td>\n | Table 110 \u2013 Format of the rights issuer stream <\/td>\n<\/tr>\n | ||||||
227<\/td>\n | 14 Protection of DVB T\/C\/S systems 14.1 General <\/td>\n<\/tr>\n | ||||||
228<\/td>\n | 14.2 Delivery of traffic layer data in DVB T\/C\/S systems 14.3 Delivery of key stream data in DVB T\/C\/S systems Table 111 \u2013 Traffic layer options for transmission over MPEG2 TS-based networks Table 112 \u2013 KSM table <\/td>\n<\/tr>\n | ||||||
229<\/td>\n | 14.4 Delivery of rights management data in DVB T\/C\/S systems <\/td>\n<\/tr>\n | ||||||
230<\/td>\n | 14.5 Delivery of registration data in DVB T\/C\/S systems Table 113 \u2013 BCRO table <\/td>\n<\/tr>\n | ||||||
231<\/td>\n | Table 114 \u2013 Carrying registration layer messages via MPEG sections in T\/C\/S system <\/td>\n<\/tr>\n | ||||||
232<\/td>\n | Table 115 \u2013 Syntax of registration message table (RMT) <\/td>\n<\/tr>\n | ||||||
233<\/td>\n | 14.6 Signalling and service guide in DVB T\/C\/S systems <\/td>\n<\/tr>\n | ||||||
235<\/td>\n | Figure 53 \u2013 Signalling of encrypted services and their associated key streams <\/td>\n<\/tr>\n | ||||||
236<\/td>\n | Figure 54 \u2013 Signalling of encrypted services in the SDT <\/td>\n<\/tr>\n | ||||||
237<\/td>\n | Figure 55 \u2013 Signalling of the rights issuer service in the SDT Figure 56 \u2013 Addressing of a rights issuer service <\/td>\n<\/tr>\n | ||||||
238<\/td>\n | Figure 57 \u2013 Signalling of purchase information via the SDT <\/td>\n<\/tr>\n | ||||||
239<\/td>\n | Figure 58 \u2013 Signalling of purchase information via the CA_descriptor in the CAT <\/td>\n<\/tr>\n | ||||||
240<\/td>\n | Figure 59 \u2013 Signalling of purchase information via the private data blockof the CA_descriptor in the CAT <\/td>\n<\/tr>\n | ||||||
241<\/td>\n | Figure 60 \u2013 Relationship between PCT, PIT, SBT and SDT <\/td>\n<\/tr>\n | ||||||
242<\/td>\n | Figure 61 \u2013 Alternative usage of the purchase_item_descriptor in the SDT and EIT <\/td>\n<\/tr>\n | ||||||
243<\/td>\n | Table 116 \u2013 Purchase channel table <\/td>\n<\/tr>\n | ||||||
247<\/td>\n | Table 117 \u2013 Service bundle table <\/td>\n<\/tr>\n | ||||||
250<\/td>\n | Table 118 \u2013 Purchase item table <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | Table 119 \u2013 Private descriptor tags used for 18Crypt <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | Table 120 \u2013 Possible locations of descriptors Table 121 \u2013 Service_ID_descriptor <\/td>\n<\/tr>\n | ||||||
253<\/td>\n | Table 122 \u2013 Right issuer ID descriptor <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | Table 123 \u2013 Purchase info location descriptor <\/td>\n<\/tr>\n | ||||||
256<\/td>\n | Table 124 \u2013 Purchase item descriptor <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | Table 125 \u2013 Subscription_type values <\/td>\n<\/tr>\n | ||||||
258<\/td>\n | Table 126 \u2013 Example price with different decimal point location values <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | Table 127 \u2013 Provider name descriptor Table 128 \u2013 Eurocrypt addressing descriptor <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | Table 129 \u2013 Address_mode <\/td>\n<\/tr>\n | ||||||
261<\/td>\n | Table 130 \u2013 Info URL descriptor Table 131 \u2013 Key URL descriptor <\/td>\n<\/tr>\n | ||||||
262<\/td>\n | Table 132 \u2013 Linkage descriptor <\/td>\n<\/tr>\n | ||||||
263<\/td>\n | Table 133 \u2013 Linkage type coding Table 134 \u2013 IP linkage descriptor <\/td>\n<\/tr>\n | ||||||
265<\/td>\n | 14.7 User-defined identifiers used in DVB-SI tables 14.8 Scope of identifiers used in DVB-SI tables Table 135 \u2013 User defined IDs <\/td>\n<\/tr>\n | ||||||
266<\/td>\n | 14.9 Format of RI services over DVB-T\/C\/S systems 15 Protection of MPEG2 TS-based IP systems 15.1 General <\/td>\n<\/tr>\n | ||||||
267<\/td>\n | 15.2 Encapsulation of an MPEG2 TS in IP 15.3 Delivery of traffic layer data in MPEG2 TS-based IP systems 15.4 Delivery of key stream data in MPEG2 TS-based IP systems 15.5 Delivery of rights management data in MPEG2 TS-based IP systems 15.6 Delivery of registration data in MPEG2 TS-based IP systems 15.7 Signalling and service guides in MPEG2 TS-based IP systems <\/td>\n<\/tr>\n | ||||||
268<\/td>\n | Table 136 \u2013 Additions to the broadcast discovery record <\/td>\n<\/tr>\n | ||||||
269<\/td>\n | Table 137 \u2013 Additions to the content-on-demand discovery record <\/td>\n<\/tr>\n | ||||||
270<\/td>\n | 15.8 Format of RI services over MPEG2 TS-based IP systems 15.9 Content-on-demand support <\/td>\n<\/tr>\n | ||||||
271<\/td>\n | 15.10 Use of server-side purchase interfaces Table 138 \u2013 Sequence of events for purchase and supply of a content-on-demand item <\/td>\n<\/tr>\n | ||||||
272<\/td>\n | 16 Protection of non-MPEG2 TS-based IP systems 16.1 General 16.2 Delivery of traffic layer data in non-MPEG2 TS-based IP systems Table 139 \u2013 Traffic layer options for transmission overnon-MPEG2 TS based IP networks <\/td>\n<\/tr>\n | ||||||
273<\/td>\n | 16.3 Delivery of key stream data in non-MPEG2 TS-based IP systems 16.4 Delivery of rights management data in non-MPEG2 TS-based IP systems 16.5 Delivery of registration data in non-MPEG2 TS-based IP systems 16.6 Signalling and service guides in non-MPEG2 TS-based IP systems 16.7 Format of RI services over non-MPEG2 TS-based IP systems 16.8 Content-on-demand support <\/td>\n<\/tr>\n | ||||||
274<\/td>\n | Annex A (normative) Supporting specifications <\/td>\n<\/tr>\n | ||||||
275<\/td>\n | Figure A.1 \u2013 Sample notification display <\/td>\n<\/tr>\n | ||||||
276<\/td>\n | Table A.1 \u2013 Status\/error codes <\/td>\n<\/tr>\n | ||||||
278<\/td>\n | Figure A.2 \u2013 Conversion routes between modified julian date (MJD) and coordinated universal time (UTC) <\/td>\n<\/tr>\n | ||||||
280<\/td>\n | Table A.2 \u2013 Local time offset coding <\/td>\n<\/tr>\n | ||||||
281<\/td>\n | Table A.3 \u2013 Standard keyset with RSA block size 1024 <\/td>\n<\/tr>\n | ||||||
282<\/td>\n | Table A.4 \u2013 Standard keyset with other RSA block sizes Table A.5 \u2013 Extended keyset with RSA block size 1024 <\/td>\n<\/tr>\n | ||||||
283<\/td>\n | Figure A.3 \u2013 Node numbering Table A.6 \u2013 Extended keyset with other RSA block sizes <\/td>\n<\/tr>\n | ||||||
284<\/td>\n | Figure A.4 \u2013 AES for key derivation <\/td>\n<\/tr>\n | ||||||
286<\/td>\n | Figure A.5 \u2013 Sample tree with correct node and device numbering <\/td>\n<\/tr>\n | ||||||
291<\/td>\n | Figure A.6 \u2013 Computation of the TAA_report_code Table A.7 \u2013 Error likelihood in human communication <\/td>\n<\/tr>\n | ||||||
295<\/td>\n | Table A.8 \u2013 Defined tag values <\/td>\n<\/tr>\n | ||||||
296<\/td>\n | Figure A.7 \u2013 Node numbering <\/td>\n<\/tr>\n | ||||||
297<\/td>\n | Table A.9 \u2013 Defined length values Table A.10 \u2013 Correct usage of length values <\/td>\n<\/tr>\n | ||||||
299<\/td>\n | Table A.11 \u2013 TAA descriptor syntax Table A.12 \u2013 TAA algorithm values <\/td>\n<\/tr>\n | ||||||
300<\/td>\n | Table A.13 \u2013 Message_tag overview Table A.14 \u2013 Table ID overview <\/td>\n<\/tr>\n | ||||||
301<\/td>\n | Table A.15 \u2013 Multilingual text structure <\/td>\n<\/tr>\n | ||||||
302<\/td>\n | Figure A.8 \u2013 Computation of the report_authentication_code <\/td>\n<\/tr>\n | ||||||
312<\/td>\n | Table A.16 \u2013 Mapping of required service guide data to the IPDC ESG <\/td>\n<\/tr>\n | ||||||
314<\/td>\n | Table A.17 \u2013 Mapping of required service guide data to DVB PSI\/SI tables <\/td>\n<\/tr>\n | ||||||
315<\/td>\n | Figure A.9 \u2013 Relationship between DVB-T\/C\/S PSI\/SI tables <\/td>\n<\/tr>\n | ||||||
317<\/td>\n | Figure A.10 \u2013 Relationships between the defined types Table A.18 \u2013 Mapping of required service guide data to IPI BCG\/TV anytime <\/td>\n<\/tr>\n | ||||||
319<\/td>\n | Figure A.11 \u2013 XML fragment for SOC identifier Figure A.12 \u2013 XML fragment for serviceBaseCID <\/td>\n<\/tr>\n | ||||||
320<\/td>\n | Figure A.13 \u2013 Definition of UniversalPurchaseItemType Figure A.14 \u2013 Definition of the ServiceBundleType <\/td>\n<\/tr>\n | ||||||
321<\/td>\n | Figure A.15 \u2013 Definition of UniversalServiceInformationType Figure A.16 \u2013 Definition of UniversalOnDemandServiceType <\/td>\n<\/tr>\n | ||||||
322<\/td>\n | Figure A.17 \u2013 Definition of UniversalPurchaseType <\/td>\n<\/tr>\n | ||||||
329<\/td>\n | Table A.19 \u2013 Updated permission element <\/td>\n<\/tr>\n | ||||||
331<\/td>\n | Table A.20 \u2013 Access element <\/td>\n<\/tr>\n | ||||||
332<\/td>\n | Figure A.18 \u2013 Recording and super-distributing the recorded asset <\/td>\n<\/tr>\n | ||||||
333<\/td>\n | Table A.21 \u2013 Semantics of the save element Table A.22 \u2013 Use of programme and service keys <\/td>\n<\/tr>\n | ||||||
334<\/td>\n | Table A.23 \u2013 Fields in the GroupID box Table A.24 \u2013 CommonHeaders box fields <\/td>\n<\/tr>\n | ||||||
335<\/td>\n | Figure A.19 \u2013 Format of the OMADRMRecordingTimestamp. <\/td>\n<\/tr>\n | ||||||
336<\/td>\n | Figure A.20 \u2013 Format of the OMADRMRecordingInformationBlock <\/td>\n<\/tr>\n | ||||||
337<\/td>\n | Figure A.21 \u2013 18Crypt namespace declaration <\/td>\n<\/tr>\n | ||||||
346<\/td>\n | Table A.25 \u2013 Conformance table for IPDC over DVB-H systems <\/td>\n<\/tr>\n | ||||||
350<\/td>\n | Table A.26 \u2013 Conformance table for DVB-T\/C\/S systems <\/td>\n<\/tr>\n | ||||||
353<\/td>\n | Table A.27 \u2013 Conformance table for IPTV systems <\/td>\n<\/tr>\n | ||||||
357<\/td>\n | Annex B (informative) Deployment considerations <\/td>\n<\/tr>\n | ||||||
359<\/td>\n | Figure B.1 \u2013 Rights issuer communication with various types of devices in IPDC over DVB-H systems <\/td>\n<\/tr>\n | ||||||
362<\/td>\n | Figure B.2 \u2013 Rights issuer communication with various typesof devices in DVB-T\/C\/S systems <\/td>\n<\/tr>\n | ||||||
364<\/td>\n | Figure B.3 \u2013 Rights issuer communication with various types of devices in IP systems <\/td>\n<\/tr>\n | ||||||
365<\/td>\n | Figure B.4 \u2013 Purchase steps in case of an interactive device <\/td>\n<\/tr>\n | ||||||
367<\/td>\n | Figure B.5 \u2013 Purchase steps in case of a broadcast device <\/td>\n<\/tr>\n | ||||||
369<\/td>\n | Figure B.6 \u2013 Consumption steps from the broadcaster point of view <\/td>\n<\/tr>\n | ||||||
370<\/td>\n | Figure B.7 \u2013 Consumption steps from the device point of view <\/td>\n<\/tr>\n | ||||||
379<\/td>\n | Figure B.8 \u2013 Function blocks of service protection head-end <\/td>\n<\/tr>\n | ||||||
381<\/td>\n | Figure B.9 \u2013 Systems and network elements of service protection head-end <\/td>\n<\/tr>\n | ||||||
382<\/td>\n | Table\u00a0B.1 \u2013 Messages involved in IEC T\/C\/S systems <\/td>\n<\/tr>\n | ||||||
383<\/td>\n | Figure B.10 \u2013 IEC T\/C\/S components integrated into DVB SimulCrypt head-end. <\/td>\n<\/tr>\n | ||||||
385<\/td>\n | Figure B.11 \u2013 Locating 18Crypt KSM & BCRO as well as EMM & ECM <\/td>\n<\/tr>\n | ||||||
386<\/td>\n | Table B.2 \u2013 Reference overview information <\/td>\n<\/tr>\n | ||||||
387<\/td>\n | Figure B.13 \u2013 Sample network set-ups using the location descriptors <\/td>\n<\/tr>\n | ||||||
388<\/td>\n | Figure B.14 \u2013 Expanding the IEC T\/C\/S head-end components <\/td>\n<\/tr>\n | ||||||
392<\/td>\n | Figure B.15 \u2013 Deployment option A (combining DIST Mgmt and RI in SOC) \u2013 Local scenario <\/td>\n<\/tr>\n | ||||||
394<\/td>\n | Figure B.16 \u2013 Deployment option A (combining DIST Mgmt and RI in SOC) \u2013 Roaming scenario <\/td>\n<\/tr>\n | ||||||
396<\/td>\n | Figure B.17 \u2013 Deployment option B (combining SUB Mgmt and RI in COC) \u2013 Local scenario <\/td>\n<\/tr>\n | ||||||
397<\/td>\n | Figure B.18 \u2013 Deployment option B (combining SUB Mgmt and RI in COC) \u2013 Roaming scenario <\/td>\n<\/tr>\n | ||||||
400<\/td>\n | Table B.3 \u2013 Example 1: CGF with cities and regions Table B.4 \u2013 Example 2: CGF with sports and regions (independent) <\/td>\n<\/tr>\n | ||||||
401<\/td>\n | Figure B.19 \u2013 Scenarios 1 and 2 for bosb_masks <\/td>\n<\/tr>\n | ||||||
402<\/td>\n | Table B.5 \u2013 Example 3: CGF with sports and regions (overlapping) <\/td>\n<\/tr>\n | ||||||
403<\/td>\n | Figure B.20 \u2013 Scenarios 3 and 4 for bosb_masks <\/td>\n<\/tr>\n | ||||||
404<\/td>\n | Figure B.21 \u2013 Scenarios 5 and 6 for bosb_masks <\/td>\n<\/tr>\n | ||||||
405<\/td>\n | Figure B.22 \u2013 Scenarios 7 and 8 for bosb_masks <\/td>\n<\/tr>\n | ||||||
406<\/td>\n | Figure B.23 \u2013 Scenarios 9 and 10 for bosb_masks (precedence) <\/td>\n<\/tr>\n | ||||||
408<\/td>\n | Figure B.24 \u2013 Diagram of keyset_block, sessionkey_block and surplus_block Table B.6 \u2013 Category of references <\/td>\n<\/tr>\n | ||||||
410<\/td>\n | Bibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Internet protocol (IP) and transport stream (TS) based service access<\/b><\/p>\n |