a38_dvb-si_spec

Recommendations

Info

24 The tables listed in clause 4 are conceptual in that they need never be regenerated in a specified form within an IRD. The tables, when transmitted shall not be scrambled, with the exception of the EIT, which may be scrambled if required (see clause 5.1.5). A section is a syntactic structure that shall be used for mapping all MPEG-2 tables and SI tables specified in the present document, into TS packets. These SI syntactic structures conform to the private section syntax defined in ISO/IEC 13818-1 [18]. 5.1.1 Explanation Sections may be variable in length. The sections within each table are limited to 1 024 bytes in length, except for sections within the EIT which are limited to 4 096 bytes. Each section is uniquely identified by the combination of the following elements: a) table_id: - The table_id identifies to which table the section belongs. - Some table_ids have been defined by ISO and others by ETSI. Other values of the table_id can be allocated by the user for private purposes. The list of values of table_id is contained in table 2. b) table_id_extension: - The table_id_extension is used for identification of a sub_table. - The interpretation of each sub_table is given in clause 5.2. c) section_number: - The section_number field allows the sections of a particular sub_table to be reassembled in their original order by the decoder. It is recommended, that sections are transmitted in numerical order, unless it is desired to transmit some sections of the sub_table more frequently than others, e.g. due to random access considerations. - For the SI tables as specified in the present document, section numbering applies to sub_tables. d) version_number: - When the characteristics of the TS described in the SI given in the present document change (e.g. new events start, different composition of elementary streams for a given service), then new SI data shall be sent containing the updated information. A new version of the SI data is signalled by sending a sub_table with the same identifiers as the previous sub_table containing the relevant data, but with the next value of version_number. - For the SI tables specified in the present document, the version_number applies to all sections of a sub_table. e) Current_next_indicator: DVB BlueBook A38
25 - Each section shall be numbered as valid "now" (current), or as valid in the immediate future (next). This allows the transmission of a future version of the SI in advance of the change, giving the decoder the opportunity to prepare for the change. There is however, no requirement to transmit the next version of a section in advance, but if it is transmitted, then it shall be the next correct version of that section. 5.1.2 Mapping of sections into Transport Stream (TS) packets Sections shall be mapped directly into TS packets. Sections may start at the beginning of the payload of a TS packet, but this is not a requirement, because the start of the first section in the payload of a TS packet is pointed to by the pointer_field. There is never more than one pointer_field in a TS packet, as the start of any other section can be identified by counting the length of the first and any subsequent sections, since no gaps between sections within a TS packet are allowed by the syntax. Within TS packets of any single PID value, one section is finished before the next one is allowed to be started, or else it is not possible to identify to which section header the data belongs. If a section finishes before the end of a TS packet, but it is not convenient to open another section, a stuffing mechanism may be used to fill up the space. Stuffing may be performed by filling each remaining byte of the TS packet with the value "0xFF". Consequently the value "0xFF" shall not be used for the table_id. If the byte immediately following the last byte of a section takes the value of "0xFF", then the rest of the TS packet shall be stuffed with "0xFF" bytes. These bytes may be discarded by a decoder. Stuffing may also be performed using the adaptation_field mechanism. For a more detailed description of the mechanism and functionality, specifically refer to clause 2.4.4 and annex C of ISO/IEC 13818-1 [18]. 5.1.3 Coding of PID and table_id fields Table 1 lists the PID values which shall be used for the TS packets which carry SI sections. Table 1: PID allocation for SI Table PAT CAT TSDT reserved NIT, ST SDT, BAT, ST EIT, ST, CIT (TS 102 323 [13]) RST, ST TDT, TOT, ST network synchronization RNT (TS 102 323 [13]) reserved for future use link-local inband signalling measurement DIT SIT PID value 0x0000 0x0001 0x0002 0x0003 to 0x000F 0x0010 0x0011 0x0012 0x0013 0x0014 0x0015 0x0016 0x0017 to 0x001B 0x001C 0x001D 0x001E 0x001F DVB BlueBook A38
Page 1: ! ! ! ! ! ! ! ! ! ! ! ! ! ! Digital
Page 4 and 5: 4 6.2.18 FTA content management des
Page 6 and 7: 6 J.2.3 EIT signalling ............
Page 8 and 9: 8 National transposition dates Date
Page 10 and 11: 10 [5] ETSI EN 301 210: "Digital Vi
Page 12 and 13: 12 [40] ISO 8601: "Data elements an
Page 14 and 15: 14 [i.9] [i.10] DVB BlueBook A165:
Page 16 and 17: 16 repeater: equipment which allows
Page 18 and 19: 18 NOTE: See [61] ASCII ATIS AVC Am
Page 20 and 21: 20 NBC-BS NDA NIT NVOD OFDM PAT paT
Page 22 and 23: 22 3) Program Map Table (PMT): - th
Page 26 and 27: 26 The PID value 0x001C allocated t
Page 28 and 29: 28 Table 3: Network information sec
Page 30 and 31: 30 } Syntax Number of bits Identifi
Page 32 and 33: 32 table_id: See table 2. section_s
Page 34 and 35: 34 Table 7: Event information secti
Page 36 and 37: 36 duration: A 24-bit field contain
Page 38 and 39: 38 Table 10: Running status section
Page 40 and 41: 40 Descriptor Tag value NIT BAT SDT
Page 42 and 43: 42 Table 14: Adaptation field data
Page 44 and 45: 44 Table 19: Coding of the announce
Page 46 and 47: 46 subcell_info_loop_length: This 8
Page 48 and 49: 48 stream_content field is in the r
Page 50 and 51: 50 stream_content stream_content_ex
Page 56 and 57: 56 content_nibble_level_1 content_n
Page 58 and 59: 58 Semantics for the country availa
Page 60 and 61: 60 } descriptor_tag 8 uimsbf descri
Page 62 and 63: 62 polarization: The polarization i
Page 64 and 65: 64 NOTE: The delivery system descri
Page 66 and 67: 66 guard_interval: The guard_interv
Page 68 and 69: 68 item_length: This 8-bit field sp
Page 70 and 71: 70 For cases b), c) and d), the tra
Page 72 and 73: 72 To define a content manageme
Page 74 and 75:
74 extended_event_linkage_info(): T
Page 76 and 77:
76 Table 63: Extended event linkage
Page 78 and 79:
78 Table 66: Target service matchin
Page 80 and 81:
80 local_time_offset: This 16-bit f
Page 82 and 83:
82 number_of_horizontal_elementary_
Page 84 and 85:
84 when cell_linkage_info = "0x04"
Page 86 and 87:
86 ISO_639_language_code: This 24-b
Page 88 and 89:
88 6.2.27 Network name descriptor T
Page 90 and 91:
90 } Semantics for the private data
Page 92 and 93:
92 Table 87: Service type coding se
Page 94 and 95:
94 6.2.36 Service move descriptor I
Page 96 and 97:
96 Semantics for the short smoothin
Page 98 and 99:
98 6.2.41 Subtitling descriptor In
Page 100 and 101:
100 national_area_code_length: This
Page 102 and 103:
102 reference_service_id: This 16-b
Page 104 and 105:
104 6.2.48 VBI teletext descriptor
Page 106 and 107:
106 ancillary_data_byte: This is an
Page 108 and 109:
108 Table 112: C2 tuning frequency
Page 110 and 111:
110 diversity_mode: This 4-bit fiel
Page 112 and 113:
112 Table 123: TDM symbol_rate symb
Page 114 and 115:
114 length increment in Interleavin
Page 116 and 117:
116 Table 132: Signalling format fo
Page 118 and 119:
118 } Syntax Number of bits Identif
Page 120 and 121:
120 } descriptor_length 8 uimsbf de
Page 122 and 123:
122 comparison of the old and new S
Page 124 and 125:
124 Table 143: Supplementary audio
Page 126 and 127:
126 Its use in other tables is not
Page 128 and 129:
128 structure created may have vari
Page 130 and 131:
130 pcr_iscr_common_clock_flag: A v
Page 132 and 133:
132 Table 152: range_type coding ra
Page 134 and 135:
134 The presence of the SIT in a bi
Page 136 and 137:
136 running_status: This 3 bit fiel
Page 138 and 139:
138 First byte value Character code
Page 140 and 141:
140 NOTE: This table is a superset
Page 142 and 143:
142 NOTE: This is compatible with I
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
148 Second Nibble -0 -1 -2 -3 -4 -5
Page 150 and 151:
Page 152 and 153:
152 After shifting the last bit of
Page 154 and 155:
154 a) To find Y, M, D from MJD Y'
Page 156 and 157:
156 Table D.4: Service type flags s
Page 158 and 159:
158 Table D.6: AC-3 descriptor synt
Page 160 and 161:
160 mixinfoexists: This 1-bit field
Page 162 and 163:
162 The minimum length of the AC-4
Page 164 and 165:
164 Annex E (normative): Usage of t
Page 166 and 167:
166 Annex G (normative): Service in
Page 168 and 169:
168 Table G.3: Bit Rate Table bit_r
Page 170 and 171:
170 Table G.6: DTS-HD® audio strea
Page 172 and 173:
172 sample_resolution: This 1-bit f
Page 174 and 175:
174 ISO_639_language_code: This 24-
Page 176 and 177:
176 Annex H (normative): Service in
Page 178 and 179:
178 Annex I (normative): Assignment
Page 180 and 181:
180 component. To avoid confusion t
Page 182 and 183:
182 Table I.2: Currently defined HE
Page 184 and 185:
184 Annex J (normative): Signalling
Page 186 and 187:
186 Table J.1: Receiver-mix compone
Page 188 and 189:
188 Receivers shall apply the follo
Page 190 and 191:
190 Annex K (normative) Extended ev
Page 192 and 193:
192 SFC-3DTV HEVC SFC-3DTV HEVC SFC
Page 194 and 195:
194 Table L.2: Config ID for Neural
Page 196:
196 History Document history Editio
show all

a38_dvb-si_spec

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?