Information Data Broadcast Application Specification. LACETEL Edition April 8 th, 2016.

Transcription

1 Information Data Broadcast Application Specification LACETEL Edition April 8 th, Page 1 of 30

2 Revision history REVISION DATE HISTORY V1 2015/08/12 Initial release (Spanish version). V2 2015/10/30 V3 2015/12/02 Second revision. (English version). - Added section 4.3 Overall structure of Data Broadcasting Service. Third revision. (English version). - Updated section 4.5 Definition of XML tags and attributes Page 2 of 30

3 CONTENTS 1 Scope References Terms, definitions and abbreviations Terms and definitions Abbrevations Data Broadcasting Service Information of Data Broadcasting Service Content of Data Broadcasting Service Overall structure of Data Broadcasting Service Overall structure of Data Broadcasting Service Elements of main page (1 st Level) Elements of second page (2 nd Level) Elements of third page (3 rd Level) Naming rules for data files of the service Definition of XML tags and attributes Size of Data Broadcasting Service Page 3 of 30

4 Information Data Broadcast Application Specification 1 Scope The present document defines all requirements of Data Broadcasting Service, which forms a part of MPEG bit streams, so that the Integrated Receiver Decoder (IRD) may receive and display data, including plain text and simple images. 2 References The following reference documents are necessary for the application of the present document. For dated references, all later amendments (excluding corrigendums) or revised versions do not apply to this requirement, however, parts which are according to this requirement should be study to define whether latest versions of these documents can be used or not. For undated reference documents, the latest versions apply to this requirement. ETSI EN ISO/IEC GD/J GD/J Digital Video Broadcasting (DVB); Specifications for Service Information (SI) in DVB systems. Information technology Generic coding of moving pictures and associated audio information: Systems. Technical requirements and measurement methods for integrated receiver decoder (basic) of satellite broadcast system (provisional). Technical requirements and measurement methods of standard definition direct broadcasting satellite integrated receiver decoder with conditional access Page 4 of 30

5 3 Terms, definitions and abbreviations 3.1 Terms and definitions bouquet: collection of services marketed as a single entity. broadcaster (service provider): organization which assembles a sequence of events or programs to be delivered to the viewer based upon a schedule. component (elementary stream): one or more entities which together make up an event (video, audio and teletext). Conditional Access (CA) system: system to control subscriber access to services, programs and events (video guard, euro crypt). delivery system: physical medium to transmit one or more streams (satellite system, wide-band coaxial cable, fiber optics, terrestrial channel of one emitting point). MPEG-2: see ISO/IEC multiplex: digital data stream carrying one or more services inside an unique physical channel. network: collection of MPEG-2 Transport Stream (TS) multiplexes that belong to a single delivery system (all digital channels on a specific cable system). original_network_id: unique identifier of a network. program: concatenation of one or more events under the control of a broadcaster (new show, entertainment show). reserved: when it is used in the clause defining the coded bit stream, indicates that the value might be used in the future when this requirement needs an extended definition. Note: unless otherwise noted, all reserved bits shall be set to 1. reserved_future_use: when it is used in the clause defining the coded bit stream, indicates that the value might be used in the future for ETSI defined extensions. Note: unless otherwise noted, all reserved bits shall be set to 1. section: syntactic structure used for mapping all service information defined in EN into ISO/IEC TS packets. service: a group (usually defined by a PMT) of one or more data streams which are offered as a whole to the viewer and it is under the control of the broadcaster. service_id: unique identifier of a service inside a TS Page 5 of 30

6 Service Information (SI): digital data describing the delivery system, content and scheduling/timing of the broadcast data streams, etc. sub_table: collection of sections with the same value of table_id and: - For NIT, the same table_id_extension (network_id) and version_number. - For BAT, the same table_id_extension (bouquet_id) and version_number. - For SDT, the same table_id_extension (transport_stream_id), the same original_network_id and version_number. - For EIT, the same table_id_extension (service_id), the same transport_stream_id, the same original_network_id and version_number. Note: the table_id_extension field is equivalent to the fourth and fifth byte of a section when the section_syntax_indicator is set to a value of "1". table: set of sub_tables with the same value of table_id. Transport Stream (TS): data structure defined in ISO/IEC transport_stream_id: unique identifier of a TS inside an original network. 3.2 Abbrevations BAT Bouquet Association Table BCD Binary Coded Decimal BMP Bitmap Picture bslbf bit stream, left bit first CA Conditional Access CRC Cyclic Redundancy Code DB Data Broadcasting DVB Digital Video Broadcasting EIT Event Information Table EPG Electronic Program Guide ES Elementary Stream FDT File Data Table IRD Integrated Receiver Decoder MPEG Moving Pictures Expert Group NIT Network Information Table Page 6 of 30

7 OSD PAT PID PMT PSI PVR RF rpchof SDT SI STB TDT TOT TS uimsbf USB XML On Screen Display Program Association Table Packet Identifier Program Map Table Program Specific Information Personal Video Recording Radio Frequency remainder polynomial coefficients, highest order first Service Description Table Service Information Set Top Box Time and Date Table Time Offset Table Transport Stream unsigned integer, most significant bit first Universal Serial Bus Extensible Markup Language Page 7 of 30

8 4 Data Broadcasting Service Data Broadcasting Service employed in Cuba have two parts: 1. Information of data broadcasting service. 2. Content of data broadcasting service. 4.1 Information of Data Broadcasting Service The Information of DB service is transmitted into BAT table, table which provides the name and the service list of bouquets. The requirements defined for the transmission of the information inside BAT table are the following: 1. bouquet_id = 0x The Information of data broadcasting service should be encapsulated into linkage_descriptor, specifically inside of linkage_type. 3. linkage_type = 0x80. This value, according to EN , is defined by user (syntax and semantic), i.e., it is proprietary. 4. Inside linkage_type, the value of table_id must be 0x90. This value, according to EN , is defined by user, i.e., it is proprietary. The linkage_descriptor is defined in EN standard to provide additional information regarding a service transmitted in the stream. The Information of DB is defined inside this descriptor, i.e., in this descriptor is defined the proprietary data format. Its syntax and semantic are defined in Table Page 8 of 30

9 Table 1. Syntax of linkage_descriptor. Syntax linkage_descriptor () { } descriptor_tag descriptor_length transport_stream_id original_network_id service_id linkage_type if (linkage_type == 0x80) { } segment_number PID table_id last_segment_number ver_num for (i = 0; i < N; i++) { { table_ext_id last_section_num Number of Bits 8 uimsbf 8 uimsbf 16 uimsbf 16 uimsbf 16 uimsbf 8 uimsbf 3 uimsbf 13 uimsbf 8 uimsbf 3 uimsbf 5 uimsbf 16 uimsbf 8 uimsbf Identifier The semantic of the linkage_descriptor for transmitting the Information of DB is explained below: descriptor_tag: 8 bits field, its value is 0x4A according to EN standard. descriptor_length: 8 bits field which defines the length of the linkage_descriptor. transport_stream_id: 16 bits field which identifies the transport stream carrying the proprietary data. original_network_id: 16 bits field which identifies the original transmission network Page 9 of 30

10 service_id: 16 bits field which identifies a unique service into the transport stream. The value is equal to program_number in the corresponding PMT section. linkage_type: 8 bits field, its value is 0x80, which means, according to EN , that data following this field is defined by user. For this reason its defined structure is employed to transmit the Information of DB. o segment_number: 3 bits field which identifies the current segment number of the associated data with linkage_type = 0x80. The value is between 0 and 7. o PID: 13 bits field which identifies packets carrying the Content of the service. The DTV receivers should look for this field to know which packets of the stream are carrying the Content of the DB service. o table_id: 8 bits field which identifies sections of FDT (File Data Table) table transmitting proprietary data. In this case, its value is equal to 0x90, which means, according to EN standard, that the structure of this table is proprietary (private), i.e., the syntax and semantic defined is proprietary. o last_segment_number: 3 bits field which identifies the last segment number of the associated data with linkage_type = 0x80. The value is between 0 and 7. o ver_num: 5 bits field which identifies the current version of proprietary data. o table_ext_id: 16 bits field which identifies different proprietary data documents, starting from 0. o last_section_number: 8 bits field which identifies the last section of proprietary data table (last FDT section). 4.2 Content of Data Broadcasting Service To transmit the Content of DB service was defined the FDT table. The Content is constituted by XML files, BMP pictures and I frames. The Content is encapsulated in the TS following the syntax of FDT table. This syntax is defined as following: Page 10 of 30

11 Table 2. Syntax of File Data Table (FDT). Syntax FILE_DATA_SECTION () { } table_id section_syntax_indicator start_indicator reserved section_lenght table_id_ext reserved version current_next_indicator section_number last_section_number file_name_lenght for (i = 0; i < file_name_lenght; i++) { } name_byte file_data_length for (i = 0; i < file_data_lenght; i++) { } CRC data_byte Numbers of bits Identifier 8 uimsbf 1 bslbf 1 bslbf 2 bslbf 12 uimsbf 12 uimsbf 6 bslbf 5 bslbf 1 bslbf 8 uimsbf 8 uimsbf 8 uimsbf 8 uimsbf 32 uimsbf 8 uimsbf rpchof Page 11 of 30

12 The semantic of the FDT section is explained below: table_id: 8 bits field which must be set to 0x90, identifying an FDT section. section_syntax_indicator: 1 bit field which must be set to 1. start_indicator: 1 bit field which must be set to 1 when the section transports the main XML file and it must be 0 for other files. reserved: 2 bits field which is reserved for future use. section_lenght: 12 bits field which identifies the length of the FDT section, i.e., the number of bytes following this field. Its maximum value is table_id_ext: 12 bits field which must be set to 0 when the section transports the main XML file and it must be a number greater than 0 for other files. reserved_future_use: 6 bits field which is reserved for future use. version: 5 bits field which identifies the version of the transmitted section. This value should be increased with each new transmitted section. current_next_indicator: 1 bit field which must be set to 1 to indicate that the section is applicable and must be set to 0 when the section is the next one to be applied. section_number: 8 bits field which identifies the current section number of the transmitted file (picture or XML file). It must begin from 0. last_section_number: 8 bits field which identifies the last section of the transmitted file (picture or XML file). file_name_lenght: 8 bits field which identifies the length (in bytes) of XML file or picture name. name_byte: 8 bits field which identifies the string name of the transmitted file (picture or XML file). file_data_length: 32 bits field which identifies the length (in bytes) of the transmitted XML file or picture. CRC_32: 32 bits field to check errors in the data of the transmitted section Page 12 of 30

13 4.3 Overall structure of Data Broadcasting Service When IRD is going to download DB Service, it must receive and process first, the information given in BAT table with bouquet_id = 0x7011 and linkage_type = 0x80, specifically in PID and table_id fields (see Table 1), to know where the content of the service is being transmitted. After knowing where the content is broadcasted, IRD must receive and process FDT table, which contains all data files. Each one of the transmitted files is encapsulated into FDT sections by following what is defined for private sections by ISO standard. When XML or picture file exceeds more than 4096 bytes, it is necessary to split it in sections before transmitting, see Error! Reference source not found., so, each one of these sections only carry 4096 bytes. After that, FDT is encapsulated into MPEG packets and multiplexed along other MPEG streams. Image 1. Splitting a file in sections. IRD has to receive all sections of a file (the last section of a file has section_number = last_section_number). Once IRD has downloaded to the RAM all sections of a files, it must display on the screen the main page of the service. The downloading process of DB Service can be performed by IRD in two ways: Page 13 of 30

14 1. Start downloading process when users ask for the service (by pressing a key on the remote control). Once all the files are received, IRD should display the content of the main XML file. Download DB Service every few minutes and store it in RAM. This way is more recommended because while users are watching a program, IRD can update the DB Service automatically and once user asks for the service, IRD has already all the files downloaded. 4.4 Overall structure of Data Broadcasting Service Data Broadcasting Service is constituted by 3 levels, as it is shown in Image 2, Image 3 and Image 4. Image 2. Main Page of Data Broadcasting Service. As it can be seen in Image 2, the first level of Data Broadcasting Service (main page) is constituted by 4 elements, which can be selected by the user using the direction keys ( ). Each one of these elements has associated a subpage (second level), where user can select between at most 9 items by using the direction keys ( ). Each one of these items has related a sub list of sub items (at the most 999), which can be selected by using the direction keys ( ). In Image 3, it can be seen the described relation Page 14 of 30

15 In the third level page the user can see the content of the selected new, which can have more than one page, that s why the user can use the Page Up / Page Down keys to switch between them. In Image 4, it can be seen the described relation. Other functions that must be implemented are: In first level user can out the service. In second level user can out the service or return to the previous page (main page). In third level user can out the service or return to the previous page (corresponding second level page). Image 3. Second Level Page of Data Broadcasting Service Page 15 of 30

16 Image 4. Third Level Page of Data Broadcasting Service Elements of main page (1 st Level) Main page of Data Broadcasting Service (first level) could include all elements related in Table 3 and displayed in Image 5: Page element Background Date information Title of main page Entrances Table 3. Elements to be included in main page. Description Show as image. Its size should be: Width: 650 pixels Height: 520 pixels Show as text. Text should display information about year, month, day and week with the following format: YYYY, MM, DD, W Its length must be at the most 16 characters. Show as image. Its size should be: Width: 127 pixels Height: 30 pixels Show as images. The size of the 4 entrances must be the same: Initial coordinate (pixel) Page 16 of 30 X: 0 Y: 0 X: 170 Y: 30 X: 265 Y:80 Entrance 1 X: 105 Y: 125 Entrance 2

17 Key hints Wight: 215 pixels Height: 143 pixels When an entrance is selected: Border: 2 pixels Color: highlighted Show as image. Its size should be: Width: 650 pixels Height: 55 pixels X: 330 Y: 125 Entrance 3 X: 105 Y: 275 Entrance 4 X: 330 Y: 275 X: 0 Y: 430 Image 5. First level page Page 17 of 30

18 4.4.2 Elements of second page (2 nd Level) Second page of Data Broadcasting Service (second level) could include all elements related in Table 4 and displayed in Image 6: Page element Background Date information Title of second page Classification title List of sub items Table 4. Elements to be included in second level pages. Description Show as image. Its size should be: Width: 650 pixels Height: 520 pixels Show as text. Text should display information about year, month, day and week with the following format: YYYY, MM, DD, W Its length must be at the most 16 characters. Show as image. Its size should be: Width: 127 pixels Height: 30 pixels Show as text. The text should be written in one line with a maximum of 21 characters. Show as text. The list should display the sub items of the selected classification. Its size should be: Width: 525 pixels Height: 270 pixels Sub items should be displayed one by one (no more than 8 items per page) using a spacing of 8 pixels. Sub item length must be at the most 21 characters. Initial coordinate (pixel) X: 0 Y: 0 X: 170 Y: 30 X: 265 Y:80 X: 65 Y: 120 X: 65 Y: Page 18 of 30

19 Page element Content table Key hints Page number Description Show the content of the table as text. Its size should be: Width: 525 pixels Height: 270 pixels Table attributes should be: Border: 2 pixels with yellow color Header text color: yellow Content Text color: white Show as image. Its size should be: Width: 650 pixels Height: 55 pixels Show as text. It should display the page number of the selected classifications and its format should be: Current page / Total pages Text length must be at the most 7 characters. Initial coordinate (pixel) X: 65 Y: 155 X: 0 Y: 430 X: 260 Y: Page 19 of 30

20 Image 6. Second level page Page 20 of 30

21 4.4.3 Elements of third page (3 rd Level) Third page of Data Broadcasting Service (third level) could include all elements related in Table 5 and displayed in Image 7: Page element Background Date information Title of the selected classification New s title Content text Table 5. Elements to be included in third level pages. Description Show as image. Its size should be: Width: 650 pixels Height: 520 pixels Show as text. Text should display information about year, month, day and week with the following format: YYYY, MM, DD, W Its length must be at the most 16 characters. Show as image. Its size should be: Width: 127 pixels Height: 30 pixels Show as text. The text should be written in one line with a maximum of 21 characters. Show as text, image or table. Only one image or table can be present by page. If the content includes an image, it should be displayed first, after it, text and a table can be displayed. In case of an image or a table, the size must be: Width: 525 pixels Height: 270 pixels In case of text, this must be constituted by 8 lines using a spacing of 8 pixels and 21 characters of length. Initial coordinate (pixel) X: 0 Y: 0 X: 170 Y: 30 X: 265 Y:80 X: 65 Y: 120 X: 65 Y: Page 21 of 30

22 Page element Key hints Page number Description Show as image. Its size should be: Width: 650 pixels Height: 55 pixels Show as text. It should display the page number of the selected classifications and its format should be: Current page / Total pages Text length must be at the most 7 characters. Image 7. Third level page. Initial coordinate (pixel) X: 0 Y: 430 X: 260 Y: Page 22 of 30

23 4.5 Naming rules for data files of the service Data files (XML files, BMP pictures and I frames) to be transmitted inside FDT sections must follow the following naming rules: The main or root file must be named as 0_index.xml. Other files must be named having in count the following rules: o The first 3 characters must be digits, which identify the table_ext_id field of FDT table. These digits must be increased by one with each new data file (001, 002, 999). o The four character must be an underline _ character. o The rest of characters conforming the file name shall depend whether the file is a XML file or an image: In case of an XML file: The rest of the name must have the format XXX_XXX, where X are digits. The first 2 digits represent the 4 entrances of the next hierarchy level, which are 21, 22, 23 and 24. The third digit represents a logic classification of the content in a specific entrance (no more than 9 classifications). The four character must be an underline _ character. The other 3 digits represent the order of the XML filenames of the third level pages. For example, XML filenames of second level pages are XXX_210_000.xml, XXX_220_000.xml, XXX_230_000.xml and XXX_240_000.xml. XML filenames of third level pages, which belong to classification 2 of entrance 1 should be XXX_212_001.xml, XXX_212_002.xml and so on. In all given example names, XXX represents the table_ext_id field of FDT table Page 23 of 30

24 In case of an image file: Background image must be an I frame and named as Background_XX.mpg, where XX are digits, such as, Background_00.mpg, Background_01.mpg and so on. Entrance images of main page must be BMP images and named as Entrance_01.bmp, Entrance_02.bmp and so on (no more than 4 entrance images). Title images must be BMP images and named as Title_01.bmp, Title_02.bmp and so on (no more than 5 titles images). Key hint images must be BMP images and named as Hints_01.bmp, Hints_02.bmp and so on (no more than 4 key hint images). Images in third level pages must be BMP images and named as a third level XML file with an underline character _ followed by 2 digits, such as, 212_001_01.bmp, 212_001_02.bmp and so on. For example, background image filename is XXX_Background_00.mpg, an entrance image filename of main page is XXX_Entrance_01.bmp, a title image filename is XXX_Title_01.bmp, a key hint image filename is XXX_Hint_01.bmp and an image filename of third level page which belongs to entrance 1 and classification 2 is XXX_212_001_01.bmp. In all given example names, XXX represents the table_ext_id field of FDT table Page 24 of 30

25 4.6 Definition of XML tags and attributes Tags and attributes which are allowed to be used inside XML files are defined below. Tags: <Text>: tag to insert text. Sometimes it could have the Href label to link another object. Image 8. <Text> tag example. <Image>: tag to insert an image. Between it must be written the file name of the image to be used. The tag must include both top_left_x and top_left_y attributes (both of them are integer type) specifying the start position (in pixels) of the image in the screen. Sometimes it could include Name and Href attributes to display text on the image or linking an object respectively. Image 9. <Image> tag example. <Table>: tag to insert a table. It is constituted of one <Title> tag and several <Content> tags. The tag must include Col attribute to specify the number of columns of the table. The quantity of <Head> tags in <Title> tag and the quantity of <Text> tags in each <Content> tag must be equal to the number of columns specified by Col attribute. This relationship can be seen in Image 10. <Title>: tag to insert the title row of a table. It is constituted by an arrange of <Head> tags. <Head>: tag to insert the head of the column. It must have the Len attribute, which specifies the number of characters allowed in the column. <Content>: tag to insert the table content. It is constituted by an arrange of <Text> tags Page 25 of 30

26 Image 10. <Table> tag structure. Image 11. example. <Table> tag Page 26 of 30

27 <Menu>: tag to insert a menu item. It is constituted of several <Image>, <Text> and <Table> tags. Its content must be only shown when the <Menu> label is selected. It must have the Name attribute, which shall be the tag title. Image 12. <Menu> tag example. <RootMenu>: tag to represent all XML files except the XML file of the first page, i.e., all XML files must start with this label. It is constituted by several <Menu>, <Image>, <Text> and <Table> tags. It could have the Name attribute as the title of the page and the Background attribute as the background image of the page. If there are several <Menu> tags inside a <RootMenu> tag, only one can be selected at the same time to display its content. Image 13. <RootMenu> tag example. <Root>: tag to represent the first page (main page). It could have the Background attribute as the background image of the page. Image 14. <Root> tag example Page 27 of 30

28 <ColorMode>: tag to define the template color. It could include more than one <Color> tag. <Color>: tag to define the RGB (Red, Green and Blue) colors of the page elements. It can only be defined in the first page (main page). It could have the ColorSelect, ColorSectionS, ColorSectionN, ColorTitleS, ColorTitleN, ColorText, ColorTableL, ColorTableH and ColorTableC attributes. Image 15. <ColorMode> tag example. Attributes: Name: string that defines the menu label name. Background: string that defines the background image name. Href: string that defines the linked object name where user can enter. Col: string that defines the columns number of a <Table> tag. It is an unsigned integer. Top_left_x: string that defines the top x started coordinate of an <Image> tag. Top_left_y: string that defines the top y started coordinate of an <Image> tag. ColorSelect: string that defines the RGB color of the selected text. ColorSectionS: string that defines the RGB color of the selected section part. ColorSectionN: string that defines the RGB color of the unselected section part. ColorTitleS: string that defines the RGB color of the selected title. ColorTitleN: string that defines the RGB color of the unselected title. ColorText: string that defines the text color Page 28 of 30

29 ColorTableL: string that defines the border color of a <Table> tag. ColorTableH: string that defines the head text color of a <Table> tag. ColorTableC: string that defines the content text color of a <Table> tag. Image 16 shows the relationship between all tags and attributes related above. Image 16. Tags and attributes relationship Page 29 of 30

30 4.7 Size of Data Broadcasting Service The maximum size of Data Broadcasting Service for each transport stream considering redundancy is 2500KB. The statistics of Data Broadcasting Service size is shown in the following table. Image Content Text Content Total Amount Table 6. Size of Data Broadcasting Service. Item Quantity/Average size Data Size/Total (KB) Background picture 1 / 650* /350 Entrance image of secondary page 4 / 215*143 34/136 Title picture 5 / 127*30 6/30 Key hint image 4 / 650*55 36/144 News picture 15 / 525*270 64/960 Text 3 200/ Page 30 of 30