This file is raw output from pdftotext and may not be ideal for distribution. If you are a maintainer for Hackipedia, please sit down when you have time and clean this text version up. Source PDF: /mnt/main/jmc-storage/docs/DVB/DVB A126 Allocation of identifiers and codes for Digital Video Broadcasting (DVB) systems (October 2010).pdf Like all conversions the text below should be fully readable as UTF-8 unicode text. --------------------------------------------------------------- ! ! ! ! ! ! ! ! ! ! ! ! ! ! ! Digital Video Broadcasting (DVB); Allocation of identifiers and codes for Digital Video Broadcasting (DVB) systems DVB Document A126 October 2010 Contents Logos on the front page ...................................................................................................................................... 3   Copyrights on page 2.......................................................................................................................................... 3   Intellectual Property Rights ................................................................................................................................ 5   Foreword............................................................................................................................................................. 5   Multi-part documents.......................................................................................................................................................... 5   Parts ...................................................................................................................................................................... 5   Parts (for multi-part deliverables containing different deliverable types, e.g. TSs and ENs) ............................................ 6   Sub-parts ...................................................................................................................................................................... 6   Introduction ........................................................................................................................................................ 6   1 Scope ........................................................................................................................................................ 7   2 References ................................................................................................................................................ 7   2.1 Normative references ......................................................................................................................................... 8   2.2 Informative references ....................................................................................................................................... 8   3 Definitions, symbols and abbreviations ................................................................................................... 8   3.1 Definitions ......................................................................................................................................................... 8   Definition format ................................................................................................................................................................ 9   3.2 Symbols ............................................................................................................................................................. 9   Symbol format ..................................................................................................................................................................... 9   3.3 Abbreviations ..................................................................................................................................................... 9   Abbreviation format ............................................................................................................................................................ 9   4 User defined clause(s) from here onwards ............................................................................................... 9   4.1 User defined subdivisions of clause(s) from here onwards................................................................................ 9   Proforma copyright release text block ............................................................................................................... 9   A nnex < A > (normative): T itle of normative annex ............................................................................... 10   A nnex (informative): T itle of informative annex ............................................................................. 11   B.1 First clause of the annex ......................................................................................................................... 11   B.1.1 First subdivided clause of the annex ................................................................................................................ 11   Abstract Test Suite (ATS) text block ................................................................................................................. 12   The TTCN Graphical form (TTCN.GR) ................................................................................................ 12   The TTCN Machine Processable form (TTCN.MP) .............................................................................. 12   A nnex (informative): Bibliography ................................................................................................... 13   History .............................................................................................................................................................. 14   History box entries ............................................................................................................................................................ 14   DVB BlueBook A 126 Intellectual 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 E TSI 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://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 become, essential to the present document. Foreword This Technical Specification (TS) has been produced by the Joint Technical Committee (JTC) Broadcast of the European Broadcasting Union (EBU), Comité Européen de Normalization 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 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 broadcasting organizations whose work includes the co- , 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 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 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 stakeholders 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 specifications. DVB BlueBook A 126 1 Scope The present document defines codes, and identifiers (also referred to as code points) used in DVB systems. These codes are allocated by the DVB Project Office at the request of potential service providers and once allocated, become part of EN 300 468 [1] by reference. Further details can be obtained by contacting DVB Services Sàrl. DVB Services Sàrl c/o EBU L'Ancienne Route 17a CH-1218 Grand-Saconnex Switzerland Tel: +41 22 717 27 19 Email: info@dvbservices.com Web: http://www.dvbservices.com 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. 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 guarantee their long term validity. 2.1 Informative references The following referenced documents are not essential to the use of the ETSI deliverable but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in DVB systems" [i.2] ETSI TR 101 211: "Digital Video Broadcasting (DVB); Guidelines on implementation and usage of Service Information (SI)" [i.3] ETSI EN 301 192: "Digital Video Broadcasting (DVB); DVB specification for data broadcasting" [i.4] ETSI TR 101 202: "Digital Video Broadcasting (DVB); Implementation guidelines for Data Broadcasting" DVB BlueBook A 126 [i.5] ETSI TS 101 812: "Digital Video Broadcasting (DVB); Multimedia Home Platform (MHP) Specification 1.1" [i.6] ETSI TS 102 727: "Digital Video Broadcasting (DVB); Multimedia Home Platform (MHP) Specification 1.2" [i.7] ISO 3166-1: "Codes for the representation of names of countries and their subdivisions -- Part 1: Country codes".3 Definitions and abbreviations [i.8] Broadcasting (DVB); Generic Stream [i.9] and other Digital Video Bro [i.10] Digital Video Broadcasting (DVB); Carriage and signalling of TV-Anytime information in DVB transport streams [i.11] ETSI TS 102 034 [i.12] Digital Video Broadcasting (DVB); Specification for System Software Update in DVB Systems [i.13] ETSI TS 102 771 Digital Video Broadcasting (DVB);Generic Stream Encapsulation (GSE) implementation guidelines [i.14] Digital Video Broadcasting (DVB); Carriage of Broadband Content Guide (BCG) informat [i.15] Digital Video Broadcasting (DVB); Remote Management and Firmware Up [i.16] Broadcasting (DVB); IP Datacast over DVB-H: [i.17] ETSI TS 102 611- Implementation Guidelines for Mobility; Part 1: IP Datacast over DVB- [i.18] ETSI TS 102 474 Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Service Purchase and Protection [i.19] CableLabs: "OpenCable Application Platform Specifications; OCAP 1.1 Profile; OC-SP-OCAP1.1.3-100603" http://www.cablelabs.com/specifications/OC-SP-OCAP1.1.3-100603.pdf [i.20] ATSC A/101 "Advanced Common Application Platform (ACAP)" http://www.atsc.org/cms/standards/a_101a.pdf [i.21] Open IPTV Forum OIPF Release 1 Specification Volume 3 Content Metadata http://www.oipf.tv/docs/Release1/Release1_1/OIPF-T1-R1-Specification- Volume-3-Content-Metadata-V1_1-2009-10-08.pdf DVB BlueBook A 126 [i.22] - Declarative http://www.oipf.tv/docs/Release1/Release1_1/OIPF-T1-R1-Specification- Volume-5-Declarative-Application-Environment-V1_1-2009-10-08.pdf [i.23] Procedural Application Environment http://www.oipf.tv/docs/Release1/Release1_1/OIPF-T1-R1-Specification- Volume-6-Procedural-Application-Environment-V1_1-2009-10-08.pdf [i.24] ETSI TS 102 809: "Digital Video Broadcasting (DVB); Signalling and carriage of interactive applications and services in Hybrid broadcast/broadband environments" [i.25] ETSI ES 202 181: "MHEG-5 Broadcast Profile" [i.26] ETSI TS 102 728 Digital Video Broadcasting (DVB); Globally Executable MHP (GEM) Specification 1.2.2 (including IPTV) 3 Definitions, and abbreviations 3.1 Definitions For the purposes of the present document, the following terms and definitions apply: A pplicant: an organistaion which applies for an identifier under the regime of the present document A pplication Domain: an identifier namespace constituted by a specification other than the present document Registrar : an organisation who keeps a public register of DVB-SI identifiers and assigns new values to Applicants under the regime of the present document NOTE: By default, the DVB Project Office is the only registrar for DVB-SI identifiers. The Project Office may however pass this task on to one or more third parties. Registration Domain: the identifier namespace constituted by the present document 3.2 Abbreviations For the purposes of the present document, the following abbreviations apply: AIT Application Information Table CA Conditional Access CP Copy Protection DVB Digital Video Broadcasting GEM Globally Executable MHP GSE Generic Stream Encapsulation IP Internet Protocol IPDC IP Datacast MAC Medium Access Control MHP Multimedia Home Platform SI Service Information DVB BlueBook A 126 4 Principles of registration The present document defines the allocation of identifiers pertaining to different DVB specifications (e.g. MHP, SI, Data Broadcasting, etc). It does not describe the detail or the template as to how this should be done. The aim of this document is to provide assistance to those soliciting and allocating identifiers. Each identifier has the following attributes: 1) It is defined in a DVB specification (e.g. DVB Service Information (ETSI EN 300 468)). 2) It is either: a. a binary number represented by either its hexadecimal equivalent denoted by the b. or a string constant represented by its Unicode equivalent; c. or a combination of a binary number and a string constant. 3) It has a text description. It is the table of values and descriptions which is published on www.dvb.org. 4) It is allocated to an organisation operating in the digital television space (e.g. ACME Digital Broadcasting, Inc.), or a grouping of such companies (e.g. a ACME Association of Cable/MMDS Enterprises) or an institution acting in digital television, e.g. IEEE (Institute of Electrical and Electronic Engineers). 5) It may be allocated for a given region. For terrestrial broadcasting, this is typically a sovereign country; for satellite operations, this is typically a geographical region spanning many countries, but consistent with the footprint of the satellites owned by the operators. The present document describes where to find definitions of each identifier, who to refer to when there are questions, templates for the allocations and rules governing them. In addition, and where appropriate, there are descriptions of best practice and some historical notes. The DVB Project Office shall be the only Registrar entitled to accept applications and perform registrations under the regime of the present document, and within the application areas of the specifications listed in clause 2.1. The DVB Project Office shall maintain a public, on-line register of assigned identifiers to ease quick look-up of the current assignments. NOTE: For practical reasons, the DVB Project Office may choose to delegate the operation and maintenance of the public, on-line register and the authority of receiving applications and performing registrations to one or more third parties. 4.1. Registration domain and application domains The scope of the present document shall constitute a registration domain namespace. Referred to as the registration domain for short. All identifiers defined in the present document, are assigned a name in the registration domain. Other specification documents as referenced by the present document constitute their own application domain namespaces. Each of them referred to as an application domain for short. Different names may be used for referring to the identifiers defined in the present document, in these application domains. DVB BlueBook A 126 For each of the identifiers defined in the present document, a sub-clause is provided, which lists the registration domain name, and application domain names used to refer to the respective identifier. This means that all the names listed for each identifier, refer to one and the same identifier. Consequently, all provisions made in the present document for the respective identifier, shall also apply to the application domains listed. 5 Service Information (DVB-SI) identifiers This clause and its sub-clauses cover the identifiers defined in ETSI EN 300 468 [i.1]. 5.1 Bouquet_ID Bouquet_ID values shall be allocated to broadcasters and network operators to identify bouquets within the application area of EN 300 468 [i.1], by insertion in the bouquet_id field. 5.1.1 Bouquet_ID registration template To register a Bouquet_ID, applicants shall supply at least the information labelled as the registration template below. Table 1: Bouquet_ID registration template Registration field Required Description Bouquet Name required Name of the Bouquet ( - ) Bouquet Country Code required Country code where the bouquet is unique (e.g. North America) Bouquet Operator required Name of organisation which operates Bouquet ( - ) Bouquet Legal Contact required Name and e-mail of authori Bouquet Technical Contact required Name and e-mail o Bouquet Notes optional Notes on the application, e.g. last revised and what revisions were made 5.1.2 Bouquet_ID allocation template The scheme and values given in the following table shall be used for the allocation of Bouquet_ID values. Table 2: Bouquet_id allocation template Bouquet_ID Description 0x0000 Reserved 0x0001 0xFFFF Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com) DVB BlueBook A 126 5.1.3 Bouquet_ID domain names The following table lists the names, under which the bouquet_id is used in different DVB specifications. Table 3: Bouquet_ID domain names Name Domain Description Bouquet_ID   Registration Domain Constituted by the present document bouquet_id   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] bouquet_id   DVB-DATA ETSI EN 301 192 [i.3] ETSI TR 101 202 [i.4] bouquet_id   DVB-TVA ETSI TS 102 323 [i.10] bouquetId   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 5.2 CA_System_ID CA_System_ID values shall be allocated to Conditional Access system vendors to identify CA systems within the application area of EN 300 468 [i.1], by insertion in the CA_system_id field. 5.2.1 CA_System_ID registration template in the registration template below. Table 4: CA_System_ID registration template Registration field Required Description CA System Name required Name of the organisation supplying Conditional Access services (e.g. ) CA System Legal Contact required Name and e-mail CA System Name CA System Technical Contact required Name and e-mail CA System Name CA System Notes optional Notes on the application, e.g. last revised and what revisions were made 5.2.2 CA_System_ID allocation template The scheme and values given in the following table shall be used for the allocation of CA_System_ID values. Table 5: CA_System_ID allocation template CA_System_ID CA system specifier 0x0000 Reserved 0x0001 0x00FF Reserved for registration to standardised systems through the DVB Project Office (see http://www.dvbservices.com) 0x0100 0xFFFF Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com) In the standardised systems registration range, allocations shall only be made for Conditional Access systems which are defined and/or adopted as such by DVB, and which are fully described in a publicly available document from a recognised standardisation body. DVB BlueBook A 126 In the general registration range, allocations shall only be made to bona fide Conditional Access system vendors. Applicants need to demonstrate that the vendor is proposing a registration for a legitimate Conditional Access product. 5.2.3 CA_System_ID domain names The following table lists the names, under which the CA_System_ID is used in different DVB specifications. Table 6: CA_System_ID domain names Name Domain Description CA_System_ID   Registration Domain Constituted by the present document CA_system_id   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] CA_system_id   DVB-DATA ETSI EN 301 192 [i.3] ETSI TR 101 202 [i.4] CA_system_id   DVB-TVA ETSI TS 102 323 [i.10] CASystsemId   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 5.3 CP_System_ID CP_System_ID values shall be allocated to identify Copy Protection (CP) systems to which DVB- CPCM content will be exported within the application area of EN 300 468 [i.1], by insertion in the field CP_system_id. 5.3.1 CP_System_ID registration template To in the registration template below. Table 7: CP_System_ID registration template Registration field Required Description CP System Description required Name of a Content Protection System ( 1.0 ) CP System Specifier required Name of the organisation supplying the CPS ( ) CP System Legal Contact required Name and e-mail of authorise CP System Technical Contact required Name and e-mail of CP System Notes optional Notes on the application, e.g. last revised and what revisions were made 5.3.2 CP_System_ID allocation template The scheme and values given in the following table shall be used for the allocation of CP_System_ID values. DVB BlueBook A 126 Table 8: CP_System_ID allocation template CP_System_ID CP system specifier 0x0000 0x00FF Reserved for registration to systems defined by DVB 0x0000 DVB CPCM Content Licence 0x0001 DVB CPCM Auxiliary Data 0x0002 DVB CPCM Revocation List 0x0100 0xFFFF Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com) In the general registration range, allocations shall only be made to bona fide Copy Protection system vendors. Applicants need to demonstrate that the vendor is proposing a registration for a legitimate Copy Protection product. 5.3.3 CP_System_ID domain names The following table lists the names, under which the CP_System_ID is used in different DVB specifications. Table 9: CP_system_id domain names Name Domain Description CP_System_ID   Registration Domain Constituted by the present document CP_system_id   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] 5.4 Country Code Country Code values shall be allocated to geographical areas to identify groups of countries or parts of countries within the application area of EN 300 468 [i.1]. These are supplementary to ISO 3166 [i.7]. This identifier helps in defining geographical coverage of other identifiers. 5.4.1 Country Code registration template To register a Country Code the registration template below. Table 10: Country Code registration template Registration field Required Description Geographical Area Name required Name of the geographical area ( North America ) Geographical Area Legal Contact required Name and e-mail Geographical Area Name Geographical Area Technical Contact required Name and e-mail Geographical Area Name Geographical Area Notes optional Notes on the application, e.g. last revised and what revisions were made 5.4.2 Country Code allocation template The scheme and values given in the following table shall be used for the allocation of Country Code values. DVB BlueBook A 126 Table 11: Country Code allocation template Country Code Grouping 000 899 Reserved for ISO 3166 [i.7] use 900 999 Reserved for registration through the DVB Project Office (see http://www.dvbservices.com) Since geographical areas are to be represented by this identifier, allocations of Country Code values shall only be made to bona fide organisations. Applicants need to demonstrate that they represent the geographical area in question in an appropriate way. Preferred Applicants for Country Code values are hence organisations known to be in agreement with the legal and regulatory authorities, and other determining organisations active in, or substantially affected by, the area for which a Country Code value is to be registered. 5.4.3 Country Code domain names The following table lists the names, under which the Country Code is used in different DVB specifications. Table 12: Country Code domain names Name Domain Description Country  Code   Registration Domain Constituted by the present document country_code   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] 5.5 Encoding_Type_ID Encoding_Type_ID values shall be allocated to broadcasters, network operators and content producers to identify string encodings within the application area of EN 300 468 [i.1], by insertion in the field encoding_type_id in the second byte of the string. 5.5.1 Encoding_Type_ID registration template To register an Encoding_Type_ID, applicants shall supply at least the information labelled as Table 13: Encoding_Type_ID registration template Registration field Required Description Encoding Type Description required Name of a character encoding type ( Universal Character Set 3 ) Encoding Type Specifier required Name of the organisation which is responsible for the character set described above ( ) Encoding Type Legal Contact required Name and e-mail of authorised le Encoding Type Technical Contact required Name and e-mail of tech Encoding Type Notes optional Notes on the application, e.g. last revised and what revisions were made 5.5.2 Encoding_Type_ID allocation template The scheme and values given in the following table shall be used for the allocation of Encoding_Type_ID values. DVB BlueBook A 126 Table 14: Encoding_Type_ID allocation template Encoding_Type_ID CP system specifier 0x00 Reserved 0x01 to 0xEF Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com) 0xF0 to 0xFF Reserved for future use 5.5.3 Encoding_Type_ID domain names The following table lists the names, under which the Encoding_Type_ID is used in different DVB specifications. Table 15: Encoding_type_id domain names Name Domain Description Encoding_Type_ID   Registration Domain Constituted by the present document encoding_type_id   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] 5.6 Network_ID Network_ID values shall be allocated to broadcasters and network operators to identify networks within the application area of EN 300 468 [i.1], by insertion in the network_id field. A network is defined as a collection of MPEG 2 Transport Stream (TS) multiplexes transmitted on a single delivery system, e.g. all digital channels on a specific cable system. Network_IDs are unique within the geographical region defined by the Country Code. For satellite networks, this is a region spanning many countries. For a cable network, this is a single country. For terrestrial networks, this is a single country also, but it is important that two adjacent countries shall not have the same block of Network IDs. Hence the concept of colour coding countries was introduced. 5.6.1 Network_ID registration template To register a Network_ID, applicants shall supply at least the inform the registration template below. Table 16: Network_ID registration template Registration field Required Description Network Type required Satellite, terrestrial or cable Network Name required Name of the Network ( Cable ) Network Country Code required Country code where the network is unique (e.g. North America) Network Operator required Name of organisation which operates the network ( Pay-TV, ) Network Legal Contact required Name and e-mail Network Network Technical Contact required Name and e-mail Network Network Notes optional Notes on the application, e.g. last revised and what revisions were made The rules for the allocation of Network_IDs are as follows: DVB BlueBook A 126 1) Network_ID s will be allocated on a geographical basis such that no conflict of network ids occurs in any geographical region. (Satellite network ids will be unique world-wide). 2) Network_IDs are a scarce resource and their allocation is under responsibility of DVB. Application of multiple Network_IDs is subject to exhaustive verification and is discouraged. 3) 256 Network_ID values are reserved for private/temporary use. Their allocation is not subject of the ETSI standard. 4) Network_IDs will be allocated according to the following table 5) Network_IDs for the terrestrial delivery medium will be made available to the appropriate national telecommunications regulator and their allocation in each country is under responsibility of this regulator. 6) In order to avoid the uneconomical use of Network_IDs, the values will be given in blocks of 256 values on a country by country basis. Non-allocated Network_IDs will be kept reserved. 7) The allocation of terrestrial network ids shall be based on a 4-colour-map approach (see Annex B). Two blocks of 256 values are reserved for the eventual case of collision. 8) If 256 values are not sufficient for a country, a new block of 256 colours will be allocated. This block can be used by all countries with the same colour in the colour map NOTE: Due to the re-usable allocation of all types of Network_ID values (satellite, cable and terrestrial), no link between Network_ID and Original_Network_ID exists. 5.6.2 Network_ID allocation template The scheme and values given in the following table shall be used for the allocation of Network_ID values. DVB BlueBook A 126 Table 17: Network_ID allocation template Network_ID Classification Network Country Description Type code(s) of validity 0x0000 Reserved all all Reserved 0x0001 - 0x2000 Unique satellite Satellite all 4 096 values reserved for registration through the DVB Project Office (see http://www.dvbservices.com) 0x2001 0x3000 Unique terrestrial Terrestrial all 4 096 values reserved for registration through the DVB Project Office (see http://www.dvbservices.com) 0x3001 0x3600 Re-useable terrestrial Terrestrial as 1 536 values reserved for registration registered through the DVB Project Office (see http://www.dvbservices.com) 0x3001 0x3100 Countries of colour A Terrestrial as 256 values registered 0x3101 0x3200 Countries of colour B Terrestrial as 256 values registered 0x3201 0x3300 Countries of colour C Terrestrial as 256 values registered 0x3301 0x3400 Countries of colour D Terrestrial as 256 values registered 0x3401 0x3500 Countries of colour E Terrestrial as 256 values registered (to be used only in case of collision) 0x3501 0x3600 Countries of colour F Terrestrial as 256 values registered (to be used only in case of collision) 0x3601 0xA000 Reserved for future Terrestrial to be 27 136 values reserved for registration use defined through the DVB Project Office (see http://www.dvbservices.com) 0xA001 0xB000 Re-useable cable Cable as 4 096 values reserved for registration registered through the DVB Project Office (see http://www.dvbservices.com) 0xB001 0xF000 Reserved for future Cable to be 16 384 values reserved for registration use defined through the DVB Project Office (see http://www.dvbservices.com) 0xF001 0xFF00 Unique cable Cable all 3 840 values reserved for registration through the DVB Project Office (see http://www.dvbservices.com) 0xFEC0 0xFF00 Network Interface DVB all 64 values for local use by DVB-CI modules Modules Common Interface 0xFF01 0xFFFF Temporary private Not all 255 values for temporary private use use defined 5.6.3 Network_ID domain names The following table lists the names, under which the Network_ID is used in different DVB specifications. Table 18: Network_ID domain names Name Domain Description Network_ID   Registration Domain Constituted by the present document network_id   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] network_id   DVB-DATA ETSI EN 301 192 [i.3] ETSI TR 101 202 [i.4] ETSI TS 102 006 [i.12] network_id   DVB-TVA ETSI TS 102 323 [i.10] networkId   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] DVB BlueBook A 126 5.7 Original_Network_ID Original_Network_ID values shall be allocated to broadcasters, network operators and content producers to uniquely identify networks within the application area of EN 300 468 [i.1], by insertion in the original_network_id field. 5.7.1 Original_Network_ID registration template To register an Original_Network_ID, applicants shall supply at least the information labelled as Table 19: Original_Network_ID registration template Registration field Required Description Original Network Name required Name of the ) Original Network Operator required Name of organisation which operates network ( Broadcast Corp. ) Original Network Legal Contact required Name and e-mail of authori Original Network Technical Contact required Name and e-mail o Original Network Notes optional Notes on the application, e.g. last revised and what revisions were made The rules for the allocation of Original_Network_IDs are as follows: 1) In principle only one Original_Network_ID should be assigned to each network operator, broadcaster or content producer. 2) Original_Network_IDs are a scarce resource and their allocation is under responsibility of DVB. Application of multiple Original_Network_IDs is subject to exhaustive verification and discouraged. 3) 256 Original_Network_ID values are reserved for private/temporary use. Their allocation is not subject of the present document. Since terrestrial and cable networks have in most cases a clearly identified geographical region of validity, the re-usage of Network_IDs is possible. However, Original_Network_IDs shall be unique independent of geographical region, since they are used to uniquely identify the transport streams and services. In terrestrial networks, however it is recommended that all operators within a country use the same Original_Network_ID. This implies that broadcasters and operators within a country would need to coordinate the allocation of transport_stream_ids and service_ids between them. The registrar is recommended to allocate Original_Network_ID values for terrestrial operators on the basis of Country Code + 0x2000. This will help receivers to discriminate broadcasts from multiple countries in cases where the target region descriptor is not used. Some examples on the use of Network_ID and Original_Network_ID are given in Annex A. 5.7.2 Original_Network_ID allocation template The scheme and values given in the following table shall be used for the allocation of Original_Network_ID values. DVB BlueBook A 126 Table 20: Original_Network_ID allocation template Original_Network_ID Description 0x0000 Reserved Reserved for general registration through the DVB Project Office (see 0x0001 - 0xFEBF http://www.dvbservices.com) 0xFEC0 - 0xFF00 DVB Common Interface Modules 0xFF00 - 0xFFFF Private temporary use 5.7.3 Original_Network_ID domain names The following table lists the names, under which the Original_Network_ID is used in different DVB specifications. Table 21: Original_Network_ID domain names Name Domain Description Original_Network_ID   Registration Domain Constituted by the present document original_network_id   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] original_network_id   DVB-DATA ETSI EN 301 192 [i.3] ETSI TR 101 202 [i.4] ETSI TS 102 006 [i.12] original_network_id   DVB-TVA ETSI TS 102 323 [i.10] originalNetworkId   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 5.9 Private_Data_Specifier_ID Private_Data_Specifier_ID values shall be allocated to broadcasters, manufacturers and network operators and content producers to identify private SI elements within the application area of EN 300 468 [i.1], by insertion in the private_data_specifier field. 5.9.1 Private_Data_Specifier_ID registration template To register a Private_Data_Specifier_ID, applicants shall supply at least the information labelled as Table 22: Private_Data_Specifier_ID registration template Registration field Required Description Private Data Specifier Organisation required Name of the organisation or organisation which is responsible for the private codes ( , ) Private Data Specifier Legal Contact required Name and e-mail of authorised le Private Data Specifier Organisation Private Data Specifier Contact required Name and e-mail of tech Private Data Specifier Organisation Private Data Specifier Notes optional Notes on the application, e.g. last revised and what revisions were made Since the Private_Data_Specifier_ID plays important roles in national broadcast regulations and service aggregation, being able correctly identify the origins of the private data is important. Hence, Private_Data_Specifier_ID values shall only be allocated to bona fide organisations for which there is a legal signatory. DVB BlueBook A 126 5.9.2 Private_Data_Specifier_ID allocation template The scheme and values given in the following table shall be used for the allocation of Private_Data_Specifier_ID values. Table 23: Private_Data_Specifier_ID allocation template Private_Data_Specifier_ID Description 0x00000000 Reserved 0x00000001 - 0xFFFFFFFF Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com) 5.9.3 Private_Data_Specifier_ID domain names The following table lists the names, under which the Private_Data_Specifier_ID is used in different DVB specifications. Table 24: Private_data_specifier domain names Name Domain Description Private_Data_Specifier_ID   Registration Domain Constituted by the present document private_data_specifier   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] private_data_specifier   DVB-DATA ETSI EN 301 192 [i.3] ETSI TR 101 202 [i.4] ETSI TS 102 006 [i.12] private_data_specifier   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 6 Data Broadcast (DVB-DATA) identifiers This clause and its sub-clauses cover the identifiers defined in ETSI EN 301 192 [i.3]. 6.1 Data_Broadcast_ID Data_Broadcast_ID values shall be allocated to broadcasters, Conditional Access vendors, middleware vendors and other standardisation bodies to identify the types of Data Broadcast services within the application area of EN 300 468 [i.1], by insertion in the field data_broadcast_id. 6.1.1 Data_Broadcast_ID registration template To register a Data_Broadcast_ID, applicants shall supply at least the information labelled as DVB BlueBook A 126 Table 25: Data_Broadcast_ID registration template Registration field Required Description Data Broadcast Specification Name required Name of a Data Broadcast Specification ( 1.0 ) Data Broadcast Specifier required Name of the organisation specifying the Data Broadcast Specification Name ) Data Broadcast Legal Contact required Name and e-mail of auth Broadcast Data Broadcast Technical Contact required Name and e- Broadcast Data Broadcast Notes optional Notes on the application, e.g. last revised and what revisions were made 6.1.2 Data_Broadcast_ID allocation template The scheme and values given in the following table shall be used for the allocation of Data_Broadcast_ID values. Table 26: Data_Broadcast_ID allocation template Data_Broadcast_ID Data broadcast specification 0x0000 Reserved for future use 0x0001 0x00EF Reserved for registration to DVB data broadcasting 0x0001 Data pipe 0x0002 Asynchronous data stream 0x0003 Synchronous data stream 0x0004 Synchronised data stream 0x0005 Multi protocol encapsulation 0x0006 Data Carousel 0x0007 Object Carousel 0x0008 DVB ATM streams 0x0009 Higher Protocols based on asynchronous data streams 0x000A System Software Update service [i.12] 0x000B IP/MAC Notification service [i.3] 0x00F0 0x00FF Reserved for registration to MHP data broadcasting 0x00F0 MHP Object Carousel 0x00F1 MHP Multiprotocol Encapsulation 0x00F2 MHP application presence 0x0100-0xFFFE Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com) 0xFFFF Reserved for future use In the general registration range separate allocations for different versions of the same data broadcast specification shall only be made if and when a receiver would otherwise not be able to detect the version used from the contents of the data broadcast streams themselves or from private data carried in DVB-SI descriptors bearing a data_broadcast_id field. Data broadcast specifiers should thus design their specifications such that receivers can detect the version used without the use of separate Data_Broadcast_ID values. DVB BlueBook A 126 6.1.3 Data_Broadcast_ID domain names The following table lists the names, under which the Data_Broadcast_ID is used in different DVB specifications. Table 27: Data_Broadcast_ID domain names Name Domain Description Data_Broadcast_ID   Registration Domain Constituted by the present document data_broadcast_id   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] data_broadcast_id   DVB-DATA ETSI EN 301 192 [i.3] ETSI TR 101 202 [i.4] ETSI TS 102 006 [i.12] data_broadcast_id   DVB-TVA ETSI TS 102 323 [i.10] data_broadcast_id   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 6.2 Platform_ID Platform_ID values shall be allocated to network operators and IPDC platform operators to uniquely identify the IP/MAC platform in use which is defined in EN 301 192 [i.3], by insertion in the platform_id field. 6.2.1 Platform_ID registration template To register a Platform_ID, applicants shall supply at least the informat the registration template below. Table 28: Platform_ID registration template Registration field Required Description Platform Name required Name of the IP/MAC Platform ). Platform Operator required Name of organisation which operates IP/MAC Platform ( Mobile Com, Inc. ) Platform Legal Contact required Name and e-mail of authori Platform Technical Contact required Name and e-mail o Platform Notes optional Notes on the application, e.g. last revised and what revisions were made 6.2.2 Platform_ID allocation template The scheme and values given in the following table shall be used for the allocation of Platform_ID values. DVB BlueBook A 126 Table 29: Platform_ID allocation template Platform_ID Description 0x000000 Reserved 0x000001 - 0xFFEFFF Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com). These platform_id values are globally unique. 0xFFF000 - 0xFFFFFE Managed by the network operator, and may be used for IP/MAC Platforms supporting services only within a single DVB network. These platform_id values are unique within a network_id only. 0xFFFFFF Reserved 6.2.3 Platform_ID domain names The following table lists the names, under which the Platform_ID is used in different DVB specifications. Table 30: Platform_ID domain names Name Domain Description Platform_ID   Registration Domain Constituted by the present document platform_id   DVB-SI ETSI EN 300 468 [i.1] ETSI TS 101 211 [i.2] platform_id   DVB-DATA ETSI EN 301 192 [i.3] ETSI TR 101 202 [i.4] ETSI TS 102 006 [i.12] platform_id   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 7 Generic Stream Encapsulation (DVB-GSE) identifiers This clause and its sub-clauses cover the identifiers defined in ETSI TS 102 606 [i.8]. 7.1 Protocol_Type_ID The DVB-S2, -T2 and -C2 physical layers provide Generic Stream modes for conveying arbitrary, variable length payload frames. To identify the type of payload frames, a field in the header of these physical layers is used. For example, in the case of DVB-S2 and DVB-T2, the SYNC field is used. Further details about the fields used can be found in [i.8]. 7.1.1 Protocol_Type_ID registration template To register a Protocol_Type_ID, applicants shall supply at least the information labelled as DVB BlueBook A 126 Table 31: Protocol_Type_ID registration template Registration field Required Description Protocol Type Name required Name of protocol specification ( SkyDSL ) Protocol Type Specifier required Name of the organisation or organisation which is responsible for the protocol specification above ( Sat Coms ) Protocol Type Legal Contact required Name and e-mail of authorised le Protocol Type Technical Contact required Name and e-mail of tech Protocol Type Notes optional Notes on the application, e.g. last revised and what revisions were made 7.1.2 Protocol_Type_ID allocation template The scheme and values given in the following table shall be used for the allocation of Protocol_Type_ID values. Table 32: Protocol_Type_ID allocation template Protocol_Type_ID Description 0x00 Generic Stream Encapsulation [i.8] 0x01 - 0xB8 Reserved for registration to standardised protocols through the DVB Project Office (see http://www.dvbservices.com) 0xB9 - 0xFF user private 7.1.3 Protocol_Type_ID domain names The following table lists the names, under which the Protocol_Type_ID is used in different DVB specifications. Table 33: Protocol_Type_ID domain names Name Domain Description Protocol_Type_ID   Registration Domain Constituted by the present document protocol_type_id   DVB-GSE ETSI TS 102 606 [i.8] ETSI TS 102 771 [i.13] 8 Identifiers for Globally Exectutable MHP (GEM), Multimedia Home Platform (DVB-MHP), and other technologies The Application Information Table (AIT) provides full information on the data broadcast, the required activation state of applications carried by it etc. Although first used with MHP (TS 101 812 [i.5] and TS 102 727 [i.6]), the AIT is now used with other technologies including OCAP [i.19], ACAP [i.20], MHEG-5 [i.25] and various specifications which use TS 102 809 [i.24], for example the Open IPTV Forum specifications [i.21], [i.22], and [i.23]. In many places in the present document, the identifiers retain MHP in the name to reflect their origins but this does not imply limitations on their use with other application types. DVB BlueBook A 126 8.1 MHP_AIT_Descriptor 8.1.1 MHP_AIT_Descriptor registration template To register an MHP_AIT_Descriptor, applicants shall supply at least the information labelled as Table 34: MHP_AIT_Descriptor registration template Registration field Required Description AIT Descriptor Specification Name required Name of an AIT Descriptor Specification ( InteractiveApps 1.0 ) AIT Descriptor Specifier required Name of the organisation specifying the AIT Descriptor Specification Name -Apps, ) AIT Descriptor Legal Contact required Name and e-mail of auth AIT Descriptor Specifier AIT Descriptor Technical Contact required Name and e- AIT Descriptor Specifier AIT Descriptor Notes optional Notes on the descriptor, e.g. last revised and what revisions were made 8.1.2 MHP_AIT_Descriptor allocation template The scheme and values given in the following table shall be used for the allocation of MHP_AIT_Descriptor values. Table 35: MHP_AIT_Descriptor allocation template MHP_AIT_Descriptor Description 0x00 0x5F Reserved for DVB-MHP 0x00 application_descriptor 0x01 application_name_descriptor 0x02 transport_protocol_descriptor 0x03 dvb_j_application_descriptor 0x04 dvb_j_application_location_descriptor 0x05 external_application_authorization_descriptor 0x08 dvb_html_application_descriptor 0x09 dvb_html_application_location_descriptor 0x0A dvb_html_application_boundary_descriptor 0x0B application_icons_descriptor 0x0C prefetch_descriptor 0x0D DII_location_descriptor 0x0E delegated_application_descriptor 0x0F plug-in_descriptor 0x10 application_storage_descriptor 0x11 ip_signalling_descriptor 0x12 provider_export_descriptor 0x13 provider_usage_descriptor 0x14 graphics_constraints_descriptor 0x5F private_data_specifier_descriptor 0x60 0x7F Reserved for registration to standardised descriptors through the DVB Project Office (see http://www.dvbservices.com) 0x80 0xFF Reserved for future use 8.1.3 MHP_AIT_Descriptor domain names The following table lists the names, under which the MHP_AIT_Descriptor is used in different DVB specifications. DVB BlueBook A 126 Table 36: MHP_AIT_Descriptor domain names Name Domain Description MHP_AIT_Descriptor   Registration Domain Constituted by the present document descriptor_tag   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 8.2 MHP_Application_Type_ID The MHP_Application_Type_ID identifies the type of the applications described in an AIT sub- table, i.e. the engine or plug-in on which the applications can be executed. MHP_Application_Type_ID values shall be allocated to broadcasters, Conditional Access vendors, middleware vendors, and other standardisation bodies to identify the types of interactive applications by insertion in the field application_type. 8.2.1 MHP_Application_Type_ID registration template To register an MHP_Application_Type_ID, applicants shall supply at least the information labelled Table 37: MHP_Application_Type_ID registration template Registration field Required Description Application Type Specification Name required Name of an Application Type Specification ( Goldenrod 1.0 ) Application Type Specifier required Name of the organisation specifying the Application Type Specification Name ) Application Type Legal Contact required Name and e-mail of auth Application Type Application Type Technical Contact required Name and e-mail of t Application Type Application Type Notes optional Notes on the application type, e.g. last revised and what revisions were made 8.2.2 MHP_Application_Type_ID allocation template The scheme and values given in the following table shall be used for the allocation of MHP_Application_Type_ID values. Table 38: MHP_Application_Type_ID allocation template MHP_Application_Type_ID Description 0x0000 Reserved 0x0001 DVB-J application 0x0002 DVB-HTML application 0x0003 0x7FFF Reserved for registration to standardised applications through the DVB Project Office (see http://www.dvbservices.com) 8.2.3 MHP_Application_Type_ID domain names The following table lists the names, under which the MHP_Application_Type_ID is used in different DVB specifications. DVB BlueBook A 126 Table 39: MHP_Application_Type_ID domain names Name Domain Description MHP_Application_Type_ID   Registration Domain Constituted by the present document application_type   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 8.3 MHP_Organisation_ID The MHP_Organisation_ID globally and uniquely identifies an organization that is responsible for interactive applications. MHP_Organisation_ID values shall be allocated to broadcasters, Conditional Access vendors, middleware vendors, application publishers, and other standardisation bodies to identify them as responsible for interactive applications by insertion in the field organisation_id. 8.3.1 MHP_Organisation_ID registration template To register an MHP_Organisation_ID, applicants shall supply at least the information labelled as Table 40: MHP_Organisation_ID registration template Registration field Required Description Organisation Name required Name of the organisation responsible for the interactive Applications ( ) Organisation Legal Contact required Name and e-mail of authorised legal signatory of Organisation Name Organisation Technical Contact required Name and e- Organisation Name Organisation Notes optional Notes on the organisation, e.g. legal successor for, or assignee to other Organisation ID holder 8.3.2 MHP_Organisation_ID allocation template The scheme and values given in the following table shall be used for the allocation of MHP_Organisation_ID values. Table 41: MHP_Organisation_ID allocation template MHP_Organisation_ID Description 0x000000 Reserved 0x000001 - 0xFFFFFF Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com). These MHP_Organisation_ID values are globally unique. DVB BlueBook A 126 8.3.3 MHP_Organisation_ID domain names The following table lists the names, under which the MHP_Organisation_ID is used in different DVB specifications. Table 42: MHP_Organisation_ID domain names Name Domain Description MHP_Organisation_ID   Registration Domain Constituted by the present document organisation_id   DVB-MHP ETSI TS 101 812 [i.5] organization_id   ETSI TS 102 727 [i.6] organisationId   ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 8.4 MHP_Protocol_ID The MHP_Protocol_ID identifies a protocol used for carrying interactive applications. MHP_Protocol_ID values shall be allocated to broadcasters, Conditional Access vendors, middleware vendors, and other standardisation bodies to identify protocols for carrying interactive applications by insertion in the field protocol_id. 8.4.1 MHP_Protocol_ID registration template To register an MHP_Protocol_ID, applicants shall supply at least the information labelled as Table 43: MHP_Protocol_ID registration template Registration field Required Description Protocol Specification Name required Name of a Protocol Specification ( 1.0 ) Protocol Specifier required Name of the organisation specifying the Protocol Specification Name e.g. ) Protocol Legal Contact required Name and e-mail of auth Protocol Protocol Technical Contact required Name and e- Protocol Protocol Notes optional Notes on the protocol, e.g. last revised and what revisions were made 8.4.2 MHP_Protocol_ID allocation template The scheme and values given in the following table shall be used for the allocation of MHP_Protocol_ID values. DVB BlueBook A 126 Table 44: MHP_Protocol_ID allocation template MHP_Protocol_ID Description 0x0000 Reserved 0x0001 0x00FF Reserved for protocols defined by DVB [i.5] [i.6] [i.24] [i.26] 0x0001 MHP Object Carousel 0x0002 IP via DVB Multiprotocol Encapsulation 0x0003 HTTP over the interaction channel 0x0100 0xFFFF Reserved for registration to standardised protocols through the DVB Project Office (see http://www.dvbservices.com) 8.4.3 MHP_Protocol_ID domain names The following table lists the names, under which the MHP_Organisation_ID is used in different DVB specifications. Table 45: MHP_Protocol_ID domain names Name Domain Description MHP_Protocol_ID   Registration Domain Constituted by the present document protocol_id   DVB-MHP ETSI TS 101 812 [i.5] ETSI TS 102 727 [i.6] ETSI TS 102 809 [i.24] ETSI TS 102 728 [i.26] 9 DVB services over bi-directional IP networks (DVB- IPTV) identifiers 9.1 Payload_ID For the transport of SD&S records, ETSI TS 102 034 [i.11] defines the DVBSTP protocol. The different types of SD&S information are distinguished by the Payload_ID field in the DVBSTP header. 9.1.1 Payload_ID registration template Since no registration to organisations outside DVB is possible at this time, no registration template is given. Should the Payload_ID be opened up for public registration in the future, the required registration template will appear here. 9.1.2 Payload_ID allocation template The scheme and values given in the following table shall be used for the allocation of Payload_ID values. DVB BlueBook A 126 Table 46: Payload_ID allocation template Payload_ID Description 0x00 Reserved 0x01 0EF Reserved for payload formats defined by DVB [i.11] [i.14] [i.15] 0x01 SD&S Service Provider Discovery Information 0x02 SD&S Broadcast Discovery Information 0x03 SD&S COD Discovery Information 0x04 SD&S Services from other SPs 0x05 SD&S Package Discovery Information 0x06 SD&S BCG Discovery Information 0x07 SD&S Regionalisation Discovery Information 0x08 FUS Stub file and SD&S RMS-FUS record 0xA1 0xAF BCG Payload_ID values (defined in ETSI TS 102 539 [i.14]) 0xB1 CDS XML download session description (defined in ETSI TS 102 539 [i.14]) 0xB2 RMS-FUS Firmware Update Announcements (defined in ETSI TS 102 824 [i.15]) 0xC1 Application Discovery Information 0xF0 0xFF User defined 9.1.3 Payload_ID domain names The following table lists the names, under which the Payload_ID is used in different DVB specifications. Table 47: Platform_id domain names Name Domain Description Payload_ID   Registration Domain Constituted by the present document Payload  ID   DVB-IPTV ETSI TS 102 034 [i.11] payloadId   ETSI TS 102 539 [i.14] PayloadId   ETSI TS 102 824 [i.15] 10 IP Datacast over DVB (DVB-IPDC) identifiers 10.1 IPDC_Operator_ID An IPDC Operator is a network entity managing IPDC key streams. It is uniquely identified by a pair of two DVB identifiers: an IPDC_Operator_ID value, and a CA_System_ID value (see clause 5.2). IPDC_Operator_ID values shall be allocated to IPDC operators to construct under the scope of a CA_system_ID value the unique identification of an IPDC operator [i.17]. For CA_system_ID values in the range of 0x0001 to 0x00FF (standardised CA systems), associated IPDC_Operator_ID values shall be registered through the DVB Project Office. 10.1.1 IPDC_Operator_ID registration template To register an IPDC_Operator_ID, applicants shall supply at least the information labelled as DVB BlueBook A 126 Table 48: IPDC_Operator_ID registration template Registration field Required Description IPDC Operator ID Type required Type of the IPDC Operator ID to be registered, i.e. string or numerical IPDC Operator CA System ID required The CA_System_id (see 5.2) which has already been registered to IPDC Operator IPDC Operator ID be used IPDC Operator Name required Name of the organisation supplying Conditional Access services (e.g. Mobile Serv ) IPDC Operator Legal Contact required Name and e-mail IPDC Operator Name IPDC Operator Technical Contact required Name and e-mail IPDC Operator Name IPDC Operator Notes optional Notes on the application, e.g. last revised and what revisions were made NOTE: For historical reasons, the IPDCOperatorId value actually used in IPDC signalling can either be a numerical value or a string value, depending on the CA system with which it is associated (e.g. IPDC SPP Open Security Framework is traditionally associated with IPDCOperatorId numerical values, whereas IPDC SPP 18Crypt is traditionally associated with IPDCOperatorId string values). When a string ID is to be registered, it shall be a unique text string compliant with one of the two XML built- 10.1.2 IPDC_Operator_ID allocation template The scheme and values given in the following table shall be used for the allocation of IPDC_Operator_ID values. Table 49: Numerical IPDC_Operator_ID allocation template IPDC_Operator_ID Description 0x0000 Reserved for non-encrypted services 0x0001 - 0xFFFF Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com). 10.1.3 IPDC_Operator_ID domain names The following table lists the names, under which the IPDC_Operator_ID is used in different DVB specifications. Table 50: IPDC_Operator_ID domain names Name Domain Description IPDC_Operator_ID   Registration Domain Constituted by the present document IPDC_Operator_ID   DVB-IPDC ETSI TS 102 832 [i.16] IPDCOperatorId   ETSI TS 102 611-1 [i.17]   ETSI TS 102 474 [i.18] 10.2 IPDC_Notification_Type IPDC Notification is a function by which the network provides messages about forthcoming and not predictable events of interest to the terminal or the user. An IPDC Notification may lead to subsequent interaction from the user/the terminal. The information carried in the notification messages can be related to the (DVB) network supporting the IPDC system, the IP platform, or the services described in a given ESG. Static, standardised IPDC_Notification_Type values shall be allocated to broadcasters, Conditional Access vendors, middleware vendors, and other standardisation bodies to identify the types of DVB BlueBook A 126 Notification message targeting an IPDC Notification application in the terminal or in the smartcard within the application area of TS 102 832 [i.16], by insertion in the field NotificationType. Allocations shall only be made for Notification Types which are fully described in a publicly available document from a recognized standardization body. 10.2.1 IPDC_Notification_Type registration template To register an IPDC_Notification_Type, applicants shall supply at least the information labelled as Table 51: IPDC_Notification_Type registration template Registration field Required Description IPDC Notification Type MIME Type required MIME type of the application-specific message part IPDC Notification Type Specification Name required Name of a IPDC Notification Type Specification ( InfoServ 1.0 ) IPDC Notification Type Specifier required Name of the organisation specifying the Type Specification Name ) IPDC Notification Legal Contact required Name and e-mail of auth Notification Type IPDC Notification Type Technical Contact required Name and e- Type IPDC Notification Type Notes optional Notes on the application type, e.g. last revised and what revisions were made 10.2.2 IPDC_Notification_Type allocation template The scheme and values given in the following table shall be used for the allocation of IPDC_Notification_Type values. Table 52: IPDC_Notification_Type allocation template IPDC_Notification_Type MIME Type Description 0x0000 0x00FF Reserved for registration to standardised applications through the DVB Project Office (see http://www.dvbservices.com) 0x0000   Reserved for specific IPDC signalling 0x0001 text/xml   ESG update message 0x0002 application/octet-­stream   Notification application inside the smartcard, invoked by the OMA Smart Card Web Server 0x0100 0xFFFF User defined (dynamically assigned in the scope of an IP platform) 10.2.3 IPDC_Notification_Type domain names The following table lists the names, under which the IPDC_Notification_Type is used in different DVB specifications. Table 53: IPDC_Notification_Type domain names Name Domain Description IPDC_Notification_Type   Registration Domain Constituted by the present document NotificationType   DVB-IPDC ETSI TS 102 832 [i.16] ETSI TS 102 611-1 [i.17] ETSI TS 102 474 [i.18] DVB BlueBook A 126 10.3 Root_of_Trust_ID The 18Crypt profile of DVB-IPDC Service Purchase and Protection (SPP) uses a public-key infrastructure (PKI) to manage authorisation, authentication, data integrity, and certificate revocations. The Root_of_Trust_ID globally and uniquely identifies a trust-centre organization that is responsible for issuing and managing certificates [i.18]. Root_of_Trust_ID values shall be allocated only to bona fide trust-centre organisations. Applicants need to demonstrate that the vendor is proposing a registration for a legitimate Root-of-Trust product. 10.3.1 Root_of_Trust_ID registration template To register a Root_of_Trust_ID, applicants shall supply at least the information labelled as Table 54: Root_of_Trust_ID registration template Registration field Required Description Root of Trust Name required Name of the organisation supplying trust-centre services ( Trust Centre ) Root of Trust Legal Contact required Name and e-mail Root of Trust Name Root of Trust Technical Contact required Name and e-mail Root of Trust Name Root of Trust Notes optional Notes on the application, e.g. last revised and what revisions were made 10.3.2 Root_of_Trust_ID allocation template The scheme and values given in the following table shall be used for the allocation of Root_of_Trust_ID values. Table 55: Root_of_Trust_ID allocation template Root_of_Trust_ID CA system specifier 000 001 Reserved for registration to systems defined by DVB 002 999 Reserved for general registration through the DVB Project Office (see http://www.dvbservices.com) 10.3.3 Root_of_Trust_ID domain names The following table lists the names, under which the Root_of_Trust_ID is used in different DVB specifications. Table 56: Root_of_Trust_ID domain names Name Domain Description Root_of_Trust_ID   Registration Domain Constituted by the present document rot_id   DVB-IPDC ETSI TS 102 832 [i.16] ETSI TS 102 611-1 [i.17] ETSI TS 102 474 [i.18] DVB BlueBook A 126 Annex A (informative): Example Scenarios for the Utilisation of network_id and original_network_id A.1 Re-transmission of a satellite signal in terrestrial networks A service operator A-TV transmits his transport stream to satellite X-SAT. The signal is re- transmitted by the terrestrial network A-NET in country A with modifications to the content. The signal is re-transmitted by the terrestrial network in country B without modifications to the content. A-TV has the unique original_network_id 0x1234. Another television network B-TV (original_network_id = 0x5678) is using the same satellite for the contribution to A-Net in country A and to B-Net in country B. The original_network_id of a DVB-T network is very likely to be the one given for that country according to table 1 of this TR. The originating service operator and its original_network_id in this case do not occur in the NIT of terrestrial networks. X-SAT has the network_id 0x0200 (in range of unique satellite networks) A-NET and B-Net share the re-usable terrestrial network_id range of 0x3300 - 0x334F DVB BlueBook A 126 X-SAT nw_id = 0x200 country A NIT nw_id = 0x0200 - NIT transp_stream_id=1 nw_id = 0x3322 orig_nw_id = 0x1234 - transp_stream_id=2 Service operator transp_stream_id=11 orig_nw_id = 0x5678 A-TV orig_nw_id = 0x1111 orig_nw_id = transp_stream_id=21 0x1234 orig_nw_id = 0x1111 Service operator B-TV NIT orig_nw_id = nw_id = 0x3304 0x5678 country B - transp_stream_id=12 orig_nw_id = 0x1111 transp_stream_id=22 orig_nw_id = 0x1111 NIT nw_id = 0x3304 - transp_stream_id=1 orig_nw_id = 0x1234 transp_stream_id=2 orig_nw_id = 0x5678 The satellite NIT contains the original_network_id of A-TV and the network_id of X-SAT. On the terrestrial network the original_network_id has always the value that has been allocated for a certain country as defined in clause 5.6. The network_id is replaced by one of the network_ids of country A that could be re-used in country B if it has the same colour in the colour-map (see Annex B). DVB BlueBook A 126 A.2 Re-transmission of a satellite signal in cable networks The same scheme as above applies. Cable networks generally shall use re-usable network_ids because there is no risk that IRDs are connected to two cable networks sharing the same network_id at the same time. The satellite serves different cable networks in L-Town and in E-Town. They can use the same network_id because they are physically separated. case the cable network_ids have to be in the unique range of values since a collision on other networks using the same re-usable network_id cannot be guaranteed. Note that this method is not recommended since the number of unique networ k_ids is limited. X-SAT nw_id = 0x200 country A NIT nw_id = 0x200 - transp_stream_id=1 orig_nw_id = 0x1234 transp_stream_id=2 NIT Service Operator orig_nw_id = 0x5678 nw_id = 0xA100 A-TV orig_nw_id = 0x1234 transp_stream_id=1 orig_nw_id = 0x1234 transp_stream_id=2 Service Operator orig_nw_id = 0x5678 B-TV orig_nw_id = 0x5678 NIT nw_id = 0xA100 transp_stream_id=1 orig_nw_id = 0x1234 transp_stream_id=2 orig_nw_id = 0x5678 DVB BlueBook A 126 History Document history DVB BlueBook A 126