ETSI EN 301 192 V1.5.1: DVB IP数据广播标准

4星 · 超过85%的资源需积分: 9 6 浏览量更新于2024-07-23 收藏 511KB PDF 举报

ETSI EN 301 192 V1.5.1（2009-11），全称为欧洲电信标准化协会（ETSI）的行业标准，是关于数字视频广播（DVB）的数据传输规范。该标准专注于DVB MPE PROTOCOL（MPEG协议在DVB系统中的应用），它定义了如何将MPEG视频数据封装到IP数据包中进行广播。DVB是一种广泛应用于欧洲的数字电视和广播标准，它允许通过IP网络传输高质量的数字视频内容。标准编号REN/JTC-DVB-261表明这是DVB技术系列中的一个关键参考文档，关键词包括“广播”、“数据”、“数字”、“DVB”、“MPEG”和“视频”，这些词汇突出了其核心内容。标准发布于2009年11月，强调了其时效性和技术重要性。 ETSIEN301192V1.5.1文档详细阐述了如何在IP网络环境中实现高效的MPEG编码视频流的传输，确保了信号的兼容性、质量和可靠性。它可能包含有关数据包头设计、错误检测与纠正、带宽管理、以及服务质量（QoS）控制等相关技术规格。此外，文档还提醒用户，尽管此版本是官方发布，但仍可能存在修订或更新的情况，因此建议查阅最新的PDF格式版本，以获取最准确的信息。该标准的发行机构——位于法国索菲亚-安提普利斯的ETSI，是一个非盈利协会，其联系方式和版权信息也有所提及。用户在下载或引用该标准时，应意识到可能会有版本差异，但以PDF格式在ETSI内部网络驱动器上保留的版本为准。在处理任何争议时，打印版的PDF文件将是权威参考。 ETSI EN 301 192 V1.5.1（2009-11）是IT行业中的一个重要技术指南，对于那些从事DVB信号传输、MPEG视频编码和IP网络广播的工程师、运营商以及设备制造商来说，理解和遵循这个标准至关重要，因为它为构建现代数字电视和广播基础设施提供了清晰的指导。

ETSI

ETSI EN 301 192 V1.5.1 (2009

11)

Table 1: Syntax for PES_data_packet structure

Syntax

No. of bits

Mnemonic

PES_data_packet () {

data_identifier 8 uimsbf

sub_stream_id 8 uimsbf

PTS_extension_flag 1 bslbf

output_data_rate_flag 1 bslbf

Reserved 2 bslbf

PES_data_packet_header_length 4 uimsbf

if (PTS_extension_flag=="1") {

Reserved 7 bslbf

PTS_extension 9 bslbf

}

if (output_data_rate_flag=="1") {

Reserved 4 bslbf

output_data_rate 28 uimsbf

}

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

PES_data_private_data_byte 8 bslbf

}

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

PES_data_byte 8 bslbf

}

The semantics of the PES_data_packet are as follows:

data_identifier: this 8-bit field identifies the type of data carried in the PES data packet. It is coded as in Table 2

(see also TS 101 162 [3] and EN 300 472 [5]).

Table 2: Coding for data_identifier field

data_identifier

value

0x00 to 0x0F reserved for future use

0x10 to 0x1F reserved for EBU data (see EN 300 472 [5])

0x20 DVB subtitling (see EN 300 743 [12])

0x21 DVB synchronous data stream

0x22 DVB synchronized data stream

0x23 to 0x7F reserved for future use

0x80 to 0xFF user defined

The data_identifier field shall be set to the same value for each PES packet conveying data in the same data stream.

sub_stream_id: this is an 8-bit field. Its use is user private.

PTS_extension_flag: this is a 1-bit field. It shall be set to "1" for synchronous data streams. For synchronized data

streams a value of "1" indicates the presence of the PTS_extension field in the PES_data_packet. If the PTS_extension

field is not present for synchronized data streams, this flag shall be set to "0".

output_data_rate_flag: this is a 1-bit field. It shall be set to "0" for synchronized data streams. For synchronous data

streams a value of "1" indicates the presence of the output_rate field in the PES_data_packet. If the output_rate field is

not present for synchronous data streams, this flag shall be set to "0".

PES_data_packet_header_length: this is a 4-bit field. It shall specify the length of the optional fields in the packet

header including the PES_data_private_data_bytes.

PTS_extension: this is a 9-bit field. This field extends the PTS conveyed in the PES header of this PES packet. This

field contains the 9-bit Program Clock Reference (PCR) extension as defined in MPEG-2 Systems

(see ISO/IEC 13818-1 [1]) that extends the time resolution of data PTS's (synchronous or synchronized) from the

MPEG-2 standard resolution of 11,1 µs (90 kHz) to 37 ns (27 MHz).

ETSI

ETSI EN 301 192 V1.5.1 (2009

11)

output_data_rate: this is a 28-bit field that shall indicate the bit rate of the regenerated signal for a synchronous data

stream. The output data rate is encoded as a 28-bit positive integer.

PES_data_private_data_byte: the use of these bytes is service specific. DVB compliant receivers may skip over these

bytes if present.

PES_data_byte: these bytes convey the data to be broadcast.

6.2 PSI and SI specifications

The data broadcast service shall indicate the use of a synchronous or synchronized data stream by including one of more

data_broadcast_descriptors in SI (see EN 300 468 [2]). Each descriptor shall be associated with a particular stream via a

component_tag identifier. In particular, the value of the component_tag field shall be identical to the value of the

component_tag field of a stream_identifier_descriptor (see EN 300 468 [2]) that may be present in the PSI program map

section for the stream that is used as a data stream.

6.2.1 Data_broadcast_descriptor

The data broadcast descriptor is used in the following way:

data_broadcast_id: this field shall be set to 0x0003 to indicate a synchronous data stream and to 0x0004 for

synchronized data streams (see TS 101 162 [3]).

component_tag: this field shall have the same value as a component_tag field of a stream_identifier_descriptor

(if present in the PSI program map section) for the stream on which the data is broadcast.

selector_length: this field shall be set to zero.

selector_byte: this field is not present.

6.2.2 Stream type

The presence of a synchronous data stream or a synchronized data stream in a service shall be indicated in the program

map section of that service by setting the stream type of that stream to the value of 0x06 or a user defined value.

7 Multiprotocol encapsulation

7.1 Data transport specification

Datagrams are encapsulated in datagram_sections which are compliant to the DSMCC_section format for private data

(see ISO/IEC 13818-6 [4]). The mapping of the section into MPEG-2 Transport Stream packets is defined in MPEG-2

Systems ISO/IEC 13818-1 [1].

The syntax and semantics of the datagram_section are defined in Table 3.

ETSI

ETSI EN 301 192 V1.5.1 (2009

11)

Table 3: Syntax of datagram_section

Syntax

No. of bits

Mnemonic

datagram_section() {

table_id 8 uimsbf

section_syntax_indicator 1 bslbf

private_indicator 1 bslbf

reserved 2 bslbf

section_length 12 uimsbf

MAC_address_6 8 uimsbf

MAC_address_5 8 uimsbf

reserved 2 bslbf

payload_scrambling_control 2 bslbf

address_scrambling_control 2 bslbf

LLC_SNAP_flag 1 bslbf

current_next_indicator 1 bslbf

section_number 8 uimsbf

last_section_number 8 uimsbf

MAC_address_4 8 uimsbf

MAC_address_3 8 uimsbf

MAC_address_2 8 uimsbf

MAC_address_1 8 uimsbf

if (LLC_SNAP_flag == "1") {

LLC_SNAP()

} else {

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

IP_datagram_data_byte 8 bslbf

}

if (section_number == last_section_number) {

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

stuffing_byte 8 bslbf

}

if (section_syntax_indicator =="0") {

checksum 32 uimsbf

} else {

CRC_32 32 rpchof

}

The semantics of the datagram_section are as follows:

table_id: this is an 8-bit field which shall be set to 0x3E (DSM-CC sections with private data (ISO/IEC 13818-6 [4])).

section_syntax_indicator: this field shall be set as defined by ISO/IEC 13818-6 [4].

private_indicator: this field shall be set as defined by ISO/IEC 13818-6 [4].

reserved: this is a 2-bit field that shall be set to "11".

section_length: this field shall be set as defined by ISO/IEC 13818-6 [4].

MAC_address_[1..6]: this 48-bit field contains the MAC address of the destination. The MAC address is fragmented in

6 fields of 8-bits, labelled MAC_address_1 to MAC_address_6. The MAC_address_1 field contains the most

significant byte of the MAC address, while MAC_address_6 contains the least significant byte. Figure 1 illustrates the

mapping of the MAC address bytes in the section fields.

NOTE: The order of the bits in the bytes is not reversed and that the Most Significant Bit (MSB) of each byte is

still transmitted first.

ETSI

ETSI EN 301 192 V1.5.1 (2009

11)

1 2 3 4 5 6

48-bit MAC address byte:

table

....

section

length

MAC

address

reserved

last

section

number

MAC

address

MAC

address

MAC

address

MAC

address

MAC

address

.... ....

section:

MSB LSB

Figure 1: Mapping of MAC address bytes to section fields

The MAC_address fields contain either a clear or a scrambled MAC address as indicated by the

address_scrambling_control field.

payload_scrambling_control: this 2-bit field defines the scrambling mode of the payload of the section. This includes

the payload starting after the MAC_address_1 but excludes the checksum or CRC32 field (see Table 4). The scrambling

method applied is user private.

Table 4: Coding of the payload_scrambling_control field

value

payload scrambling control

00 unscrambled

01 defined by service

10 defined by service

11 defined by service

address_scrambling_control: this 2-bit field defines the scrambling mode of MAC address in this clause (see Table 5).

This field enables a dynamic change of MAC addresses. The scrambling method applied is user private.

Table 5: Coding of the address_scrambling_control field

value

address scrambling control

00 unscrambled

01 defined by service

10 defined by service

11 defined by service

LLC_SNAP_flag: this is a 1-bit flag. If this flag is set to "1" the payload carries an LLC/SNAP encapsulated datagram

following the MAC_address_1 field. The LLC/SNAP structure shall indicate the type of the datagram conveyed. If this

flag is set to "0", the section shall contain an IP datagram without LLC/SNAP encapsulation.

current_next_indicator: this is a 1-bit field. It shall be set to a value of "1".

section_number: this is an 8-bit field. If the datagram is carried in multiple sections, then this field indicates the

position of the section within the fragmentation process. Otherwise it shall be set to zero.

last_section_number: this 8-bit field shall indicate the number of the last section that is used to carry the datagram,

i.e. the number of the last section of the fragmentation process.

LLC_SNAP: this structure shall contain the datagram according to the ISO/IEC 8802-2 [11] Logical Link Control

(LLC) and ISO/IEC 8802-1 [10] a SubNetwork Attachment Point (SNAP) specifications. If the payload of the section is

scrambled (see payload_scrambling_mode), these bytes are scrambled.

IP_datagram_data_byte: these bytes contain the data of the datagram. If the payload of the section is scrambled

(see payload_scrambling_mode), these bytes are scrambled.

stuffing_byte: this is an optional 8-bit field whose value is not specified. If the payload of the section is scrambled

(see payload_scrambling_mode), these bytes are scrambled. They are to assist with block encryption and data

processing in wide bus environments. The number of stuffing_bytes used should meet the data alignment requirements

defined in the data_broadcast_descriptor.

剩余79页未读，继续阅读

mmkclub

粉丝: 6
资源: 9

ETSI EN 301 192 V1.5.1: DVB IP数据广播标准

ETSI EN 301 790 V1.5.1(2009-01 Final draft).pdf.7z

ETSI EN 301 192 v1.4.1 (2004-06, Final draft).pdf.7z

ETSI EN 301 489-1：2019（V2.2.3）电磁兼容性协调标准 - 完整英文电子版（101页）.pdf

ETSI EN 302 217-4-2 v1.5.1(2010-01)：固定无线电系统，特点和要求点至点设备和天线，第4-2部分

ETSI EN 301 790 RCS标准：DVB-RCS互动卫星广播系统详解

EN 301192 DVB数据广播规范(v1.5.1)

EN301489-23v1.3.1

en_300743v010501p

EN 300 468

ETSI EN 302 217-4-2标准：点对点设备与天线规范

最新资源