欧洲电信标准协会（ETSI）EN300468：DVB系统中服务信息（SI）规范

5星 · 超过95%的资源需积分: 9 29 浏览量更新于2024-07-29 收藏 1.3MB PDF 举报

"欧洲电信标准协会(ETSI)制定的EN 300468 V1.10.1(2009-07)标准，详细规定了数字电视传输流（TS流）中的服务信息（SI）规范，适用于DVB（数字视频广播）系统。该文档由欧洲广播联盟（EBU）和欧洲电信标准协会（ETSI）共同发布，包含了与广播、数字电视、DVB、MPEG、服务和视频相关的关键词。" 在数字电视领域，服务信息（Service Information, SI）是至关重要的组成部分，它提供了关于频道、节目和服务的元数据，帮助接收端解码和呈现电视内容。EN 300468标准详细定义了这些信息如何在DVB系统中组织和传输，确保不同设备能正确解析并显示节目信息。 1. **DVB系统**：DVB代表数字视频广播，是一个国际性的标准，用于地面、卫星和有线电视广播。它涵盖了视频、音频的编码方式，以及传输和接收这些信号的方法。 2. **TS流**：传输流（Transport Stream, TS）是DVB中用于传输多路数字电视信号的数据格式。TS流包含多个独立的节目，每个节目有自己的视频、音频和字幕流，以及相关的服务信息。 3. **服务信息（SI）**：SI包括节目指南（EPG）、频道名称、服务类型、加密状态等，这些信息使得用户可以浏览和选择他们想要观看的节目。SI通过特定的表格和消息在TS流中传递。 4. **MPEG**：MPEG是运动图像专家组的缩写，负责制定视频和音频压缩标准，如MPEG-2，这是DVB系统中常用的视频编码标准。 5. **结构**：EN 300468详细规定了SI的结构，如节目关联表（PAT）、服务描述表（SDT）、网络信息表（NIT）等，这些表格定义了TS流中的节目关系和网络配置。 6. **协议和格式**：标准还涉及了如何使用特定的协议和数据格式来编码和解码SI，确保兼容性和互操作性。 7. **版本更新**：EN 300468 V1.10.1（2009-07）是该标准的一个版本，随着时间的推移，标准可能会进行更新以适应技术进步和市场需求。了解并遵循EN 300468标准对于设计、制造和维护数字电视接收设备至关重要，因为它确保了不同设备之间的互操作性和用户友好性。该标准的实施促进了全球范围内数字电视服务的广泛采用和发展。

ETSI

Final draft ETSI EN 300 468 V1.10.1 (2

009

07)

6) Time Offset Table (TOT):

- the TOT gives information relating to the present time and date and local time offset. This information is

given in a separate table due to the frequent updating of the time information.

7) Stuffing Table (ST):

- the ST is used to invalidate existing sections, for example at delivery system boundaries.

8) Selection Information Table (SIT):

- the SIT is used only in "partial" (i.e. recorded) bitstreams. It carries a summary of the SI information

required to describe the streams in the partial bitstream.

9) Discontinuity Information Table (DIT):

- the DIT is used only in "partial" (i.e. recorded) bitstreams. It is inserted where the SI information in the

partial bitstream may be discontinuous.

Where applicable the use of descriptors allows a flexible approach to the organization of the tables and allows for future

compatible extensions.

ETSI

Final draft ETSI EN 300 468 V1.10.1 (2009

07)

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:

- 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.

ETSI

Final draft ETSI EN 300 468 V1.10.1 (2009

07)

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

PID value

PAT 0x0000

CAT 0x0001

TSDT 0x0002

reserved 0x0003 to 0x000F

NIT, ST 0x0010

SDT, BAT, ST 0x0011

EIT, ST CIT (TS 102 323 [13])

0x0012

RST, ST 0x0013

TDT, TOT, ST 0x0014

network synchronization 0x0015

RNT (TS 102 323 [13]) 0x0016

reserved for future use 0x0017 to 0x001B

inband signalling 0x001C

measurement 0x001D

DIT 0x001E

SIT 0x001F

Table 2 lists the values which shall be used for table_id for the service information, defined in the present document.

Table 2: Allocation of table_id values

Value

Description

0x00 program_association_section

0x01 conditional_access_section

0x02 program_map_section

0x03 transport_stream_description_section

0x04 to 0x3F reserved

0x40 network_information_section - actual_network

0x41 network_information_section - other_network

0x42 service_description_section - actual_transport_stream

0x43 to 0x45 reserved for future use

0x46 service_description_section - other_transport_stream

0x47 to 0x49 reserved for future use

0x4A bouquet_association_section

0x4B to 0x4D reserved for future use

0x4E event_information_section - actual_transport_stream, present/following

0x4F event_information_section - other_transport_stream, present/following

0x50 to 0x5F event_information_section - actual_transport_stream, schedule

0x60 to 0x6F event_information_section - other_transport_stream, schedule

0x70 time_date_section

0x71 running_status_section

0x72 stuffing_section

0x73 time_offset_section

0x74 application information section (TS 102 812 [15])

0x75 container section (TS 102 323 [13])

0x76 related content section (TS 102 323 [13])

0x77 content identifier section (TS 102 323 [13])

ETSI

Final draft ETSI EN 300 468 V1.10.1 (2009

07)

Value

Description

0x78 MPE-FEC section (EN 301 192 [4])

0x79 resolution notification section (TS 102 323 [13])

0x7A MPE-IFEC section (TS 102 772 [i.7])

0x7B to 0x7D reserved for future use

0x7E discontinuity_information_section

0x7F selection_information_section

0x80 to 0xFE user defined

0xFF reserved

5.1.4 Repetition rates and random access

In systems where random access is a consideration, it is recommended to re-transmit SI sections specified within the

present document several times, even when changes do not occur in the configuration.

For SI specified within the present document the minimum time interval between the arrival of the last byte of a section

to the first byte of the next transmitted section with the same PID, table_id and table_id_extension and with the same or

different section_number shall be 25 ms. This limit applies for TSs with a total data rate of up to 100 Mbit/s.

5.1.5 Scrambling

With the exception of the EIT carrying schedule information, all tables specified in the present document shall not be

scrambled. One method for scrambling the EIT schedule table is given in annex E (Usage of the

Scrambling_descriptor). If a scrambling method operating over TS packets is used, it may be necessary to use a stuffing

mechanism to fill from the end of a section to the end of a packet so that any transitions between scrambled and

unscrambled data occur at packet boundaries.

In order to identify the CA streams which control the descrambling of the EIT data, a scrambled EIT schedule table

shall be identified in the PSI. Service_id value 0xFFFF is allocated to identifying a scrambled EIT, and the program

map section for this service shall describe the EIT as a private stream and shall include one or more CA_descriptors

(defined in ISO/IEC 13818-1 [18]) which give the PID values and optionally, other private data to identify the

associated CA streams. Service_id value 0xFFFF shall not be used for any other service.

5.2 Table definitions

The following clauses describe the syntax and semantics of the different types of table.

NOTE: The symbols and abbreviations, and the method of describing syntax used in the present document are the

same as those defined in clauses 2.2 and 2.3 of ISO/IEC 13818-1 [18].

5.2.1 Network Information Table (NIT)

The NIT (see table 3) conveys information relating to the physical organization of the multiplexes/TSs carried via a

given network, and the characteristics of the network itself. The combination of original_network_id and

transport_stream_id allow each TS to be uniquely identified throughout the application area of the present document.

Networks are assigned individual network_id values, which serve as unique identification codes for networks. The

allocation of these codes may be found in TS 101 162 [i.1]. The network_id and the original_network_id can take the

same value, or may have to take different values subject to the allocation constraints for original_network_id and

network_id as per TS 101 162 [i.1].

Guidelines for the processing of SI at transitions between delivery media boundaries, e.g. from satellite to cable or

SMATV systems, can be found in TR 101 211 [i.2].

IRDs may be able to store the NIT information in non-volatile memory in order to minimize the access time when

switching between channels ("channel hopping"). It is also possible to transmit a NIT for other networks in addition to

the actual network. Differentiation between the NIT for the actual network and the NIT for other networks is achieved

using different table_id values (see table 2).

剩余131页未读，继续阅读

yonxinlpp

粉丝: 0
资源: 3

欧洲电信标准协会（ETSI）EN300468：DVB系统中服务信息（SI）规范

en_300468v010601o.pdf

en_300468v010701o.pdf

GD32F10x_User_Manual_EN_V2.3-3.pdf

let{apiUrl:T,siteId:W,siteModel:L}=s(E(D));i("data-v-fff4ca96");const O=["href"],J=[p("img",{src:"/assets/en_3.fd6317bf.png",class:"kefu"},null,-1)];怎么修改这段代码的href跳转链接地址

let{apiUrl:T,siteId:W,siteModel:L}=s(E(D));i("data-v-fff4ca96");const O=["href"],J=[p("img",{src:"/assets/en_3.fd6317bf.png",class:"kefu"},null,-1)];

在stm32f10怎样使用LCD1602A

ld3320a初始化代码

写一个51单片机lcd1602显示iloveyou的代码

最新资源