ETSI EN 300 468 V1.8.1: DVB数字电视服务信息规范

4星 · 超过85%的资源需积分: 9 127 浏览量更新于2024-08-02 收藏 1.08MB PDF 举报

ETSI EN 300 468 V1.8.1，全称为《欧洲电信标准化协会（ETSI）关于数字视频广播 (DVB) 系统中的服务信息 (SI) 规范》，是一个专门针对数字电视广播领域制定的标准。该标准主要关注的是在DVB（Digital Video Broadcasting）系统中，如何有效地提供服务信息和服务数据，这些信息对于电视广播服务的运营、管理和用户交互至关重要。在这个标准中，DVB是欧洲广播联盟 (EBU) 和欧洲电视联合研究组 (UER) 合作开发的项目，旨在实现高质量的数字电视传输，包括MPEG2技术的应用。MPEG2是一种广泛应用于数字视频压缩编码的国际标准，它能够高效地压缩视频数据，同时保持良好的图像质量和音频质量。服务信息 (SI) 是DVB系统的核心组成部分，它包括了如电子节目指南 (EPG，Electronic Programme Guide)、预告片、广告、字幕、互动服务等与电视内容相关的附加信息。这些信息不仅增强了观众的观看体验，也支持了付费电视、vod（视频点播）、交互式电视等多种服务模式。此外，标准还涉及到电视节目的元数据管理，确保了服务信息的一致性和准确性。它规定了SI的数据格式、编码、传输方法以及与接收设备的交互方式，使得不同供应商的设备能无缝对接，提供统一的服务体验。值得注意的是，ETSI EN 300 468 V1.8.1是一个最终草案，发布日期为2007年10月，这意味着它可能会在后续版本中进行更新和完善。对于用户来说，获取最新版本的信息可以从ETSI官方网站下载，以便获得最准确和最新的规范内容。这个标准对于广播行业的发展有着深远影响，它确保了数字电视服务的质量、兼容性和可扩展性，推动了整个行业的标准化进程。通过遵循ETSI EN 300 468 V1.8.1，服务提供商能够更好地向用户提供个性化的电视体验，促进电视行业的创新和进步。

ETSI

Final draft ETSI EN 300 468 V1.8.1 (2007

10)

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

compatible extensions.

MPEG

-2 defined Defined in the present document

Actual Network

Other Network

Figure 2: General organization of the Service Information (SI)

5 Service Information (SI) tables

5.1 SI table mechanism

The SI specified in the present document and MPEG-2 PSI tables shall be segmented into one or more sections before

being inserted into TS packets.

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

ETSI

Final draft ETSI EN 300 468 V1.8.1 (2007

10)

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 [19].

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.8.1 (2007

10)

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 [19].

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 [14])

0x0012

RST, ST 0x0013

TDT, TOT, ST 0x0014

network synchronization 0x0015

RNT (TS 102 323 [14]) 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 [16])

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

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

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

ETSI

Final draft ETSI EN 300 468 V1.8.1 (2007

10)

Value Description

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

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

0x79 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 D, Bibliography. 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 [19]) 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 [19].

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

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

allocation of these codes may be found in TR 101 162 [46]. In the case that the NIT is transmitted on the network on

which the TS was originated, the network_id and the original_network_id shall take the same value.

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 [10].

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

ETSI

Final draft ETSI EN 300 468 V1.8.1 (2007

10)

The NIT shall be segmented into network_information_sections using the syntax of table 3. Any sections forming part

of an NIT shall be transmitted in TS packets with a PID value of 0x0010. Any sections of the NIT which describe the

actual network (that is, the network of which the TS containing the NIT is a part) shall have the table_id 0x40 with the

same table_id_extension (network_id). The network_id field takes the value assigned to the actual network in

TR 101 162 [46]. Any sections of an NIT which refer to a network other than the actual network shall take a table_id

value of 0x41 and the network_id shall take the value allocated to the other network in TR 101 162 [46].

Table 3: Network information section

Syntax Number of bits

Identifier

network_information_section(){

table_id

8 uimsbf

section_syntax_indicator

1 bslbf

reserved_future_use

1 bslbf

reserved

2 bslbf

section_length

12 uimsbf

network_id

16 uimsbf

reserved

2 bslbf

version_number

5 uimsbf

current_next_indicator

1 bslbf

section_number

8 uimsbf

last_section_number

8 uimsbf

reserved_future_use

4 bslbf

network_descriptors_length

12 uimsbf

for(i=0;i<N;i++){

descriptor()

}

reserved_future_use

4 bslbf

transport_stream_loop_length

12 uimsbf

for(i=0;i<N;i++){

transport_stream_id

16 uimsbf

original_network_id

16 uimsbf

reserved_future_use

4 bslbf

transport_descriptors_length

12 uimsbf

for(j=0;j<N;j++){

descriptor()

}

CRC_32

32 rpchof

}

Semantics for the network information section:

table_id: See table 2.

section_syntax_indicator: The section_syntax_indicator is a 1-bit field which shall be set to "1".

section_length: This is a 12-bit field, the first two bits of which shall be "00". It specifies the number of bytes of the

section, starting immediately following the section_length field and including the CRC. The section_length shall not

exceed 1 021 so that the entire section has a maximum length of 1 024 bytes.

network_id: This is a 16-bit field which serves as a label to identify the delivery system, about which the NIT informs,

from any other delivery system. Allocations of the value of this field are found in TR 101 162 [46].

version_number: This 5-bit field is the version number of the sub_table. The version_number shall be incremented by

1 when a change in the information carried within the sub_table occurs. When it reaches value 31, it wraps around to 0.

When the current_next_indicator is set to "1", then the version_number shall be that of the currently applicable

sub_table defined by the table_id and network_id. When the current_next_indicator is set to "0", then the

version_number shall be that of the next applicable sub_table defined by the table_id and network_id.

current_next_indicator: This 1-bit indicator, when set to "1" indicates that the sub_table is the currently applicable

sub_table. When the bit is set to "0", it indicates that the sub_table sent is not yet applicable and shall be the next

sub_table to be valid.

剩余110页未读，继续阅读

peacecraft

粉丝: 1
资源: 3

ETSI EN 300 468 V1.8.1: DVB数字电视服务信息规范

EN 300 468 V1.15.1

EN-300-468-V191-200903_decrypted.pdf

ETSI EN 300-468标准培训_300_ETSIEN300-468标准培训_

ETSI EN 300 468 v1.8.1 (2007-10 Final draft)

ETSI en_300328v1.8.1

ETSI EN 300 328 V1.8.1：2.4GHz ISM频段宽带传输设备的电磁兼容与法规要求

ETSI EN 300468 V1.8.1：DVB数字电视EPG开发关键文档

epg开发文档En300468.V1.8.1

EN300328 V 1.8.1 测试标准

EN301489-1V1.8.1

最新资源