SIST EN 301 192 V1.1.1:2005

SLOVENSKI STANDARD
01-november-2005
Digitalna videoradiodifuzija (DVB) – Specifikacija DVB za podatkovno radiodifuzijo
Digital Video Broadcasting (DVB); DVB specification for data broadcasting
Ta slovenski standard je istoveten z: EN 301 192 Version 1.1.1
ICS:
33.170 Televizijska in radijska Television and radio
difuzija broadcasting
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EN 301 192 V1.1.1 (1997-12)
European Standard (Telecommunications series)
Digital Video Broadcasting (DVB);
DVB specification for data broadcasting
European Broadcasting Union Union Européenne de Radio-Télévision
EBU
UER
European Telecommunications Standards Institute

2 EN 301 192 V1.1.1 (1997-12)
Reference
DEN/JTC-DVB-33 (b1c00ico.PDF)
Keywords
DVB, broadcasting, digital, video, TV, MPEG,
data
ETSI Secretariat
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00  Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
X.400
c= fr; a=atlas; p=etsi; s=secretariat
Internet
secretariat@etsi.fr
http://www.etsi.fr
Copyright Notification
No part may be reproduced except as authorized by written permission.
The copyright and the foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1997.
© European Broadcasting Union 1997.
All rights reserved.
3 EN 301 192 V1.1.1 (1997-12)
Contents
Intellectual Property Rights.5
Foreword .5
1 Scope.6
2 References.7
3 Abbreviations.8
4 Data piping.9
4.1 Data transport specification . 9
4.2 PSI and SI specifications . 9
4.2.1 Data_broadcast_descriptor. 9
4.2.2 Stream type. 9
5 Asynchronous data streaming .9
5.1 Data transport specification . 9
5.2 PSI and SI specifications . 10
5.2.1 Data_broadcast_descriptor. 10
5.2.2 Stream type. 10
6 Synchronous and synchronized data streaming .10
6.1 Data transport specification . 10
6.2 PSI and SI specifications . 12
6.2.1 Data_broadcast_descriptor. 12
6.2.2 Stream type. 12
7 Multiprotocol encapsulation .12
7.1 Data transport specification . 12
7.2 PSI and SI specifications . 15
7.2.1 Data_broadcast_descriptor. 15
7.2.2 Stream type. 16
8 Data carousels .16
8.1 Data transport specification . 16
8.1.1 Structure of DVB data carousel. 17
8.1.2 DownloadServerInitiate message . 18
8.1.3 DownloadInfoIndication message . 19
8.1.4 DownloadDataBlock message. 20
8.1.5 DownloadCancel . 20
8.2 Descriptors. 20
8.2.1 Descriptor identification and location . 20
8.2.2 Type descriptor . 20
8.2.3 Name descriptor . 21
8.2.4 Info descriptor. 21
8.2.5 Module link descriptor . 22
8.2.6 CRC32 descriptor. 22
8.2.7 Location descriptor. 23
8.2.8 Estimated download time descriptor . 23
8.2.9 Group link descriptor . 23
8.2.10 Private descriptor . 24
8.3 PSI and SI specifications . 24
8.3.1 Data_broadcast_descriptor. 24
8.3.2 Stream type. 25
9 Object carousels.26
9.1 Scope of the object carousels. 26
9.2 Data transport specification . 26
9.2.1 Carousel NSAP address . 26

4 EN 301 192 V1.1.1 (1997-12)
9.3 PSI and SI specifications . 27
9.3.1 Data_broadcast_descriptor. 27
9.3.2 Deferred_association_tags_descriptor. 29
9.3.3 Stream type. 30
10 Decoder models.30
Annex A (informative): Registration of private data broadcast systems.32
History.33

5 EN 301 192 V1.1.1 (1997-12)
Intellectual Property Rights
IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in ETR 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of
ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the ETSI
Web server (http://www.etsi.fr/ipr).
Pursuant to the ETSI Interim IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No
guarantee can be given as to the existence of other IPRs not referenced in ETR 314 (or the updates on
http://www.etsi.fr/ipr) which are, or may be, or may become, essential to the present document.
Foreword
This European Standard (Telecommunications series) has been produced by the Joint Technical Committee (JTC) of the
European Broadcasting Union (EBU), Comité Européen de Normalisation ELECtrotechnique (CENELEC) and the
European Telecommunications Standards Institute (ETSI).
NOTE: The EBU/ETSI JTC was established in 1990 to co-ordinate the drafting of standards in the specific field
of broadcasting and related fields. Since 1995 the JTC became a tripartite body by including in the
Memorandum of Understanding also CENELEC, which is responsible for the standardization of radio and
television receivers. The EBU is a professional association of broadcasting organizations whose work
includes the co-ordination of its members' activities in the technical, legal, programme-making and
programme-exchange domains. The EBU has active members in about 60 countries in the European
broadcasting area; its headquarters is in Geneva *.
* European Broadcasting Union
CH-1218 GRAND SACONNEX (Geneva)
Switzerland
Tel: +41 22 717 21 11
Fax: +41 22 717 24 81
Digital Video Broadcasting (DVB) Project
Founded in September 1993, the DVB Project is a market-led consortium of public and private sector organizations in
the television industry. Its aim is to establish the framework for the introduction of MPEG-2 based digital television
services. Now comprising over 200 organizations from more than 25 countries around the world, DVB fosters
market-led systems, which meet the real needs, and economic circumstances, of the consumer electronics and the
broadcast industry.
National transposition dates
Date of adoption of this EN: 5 December 1997
Date of latest announcement of this EN (doa): 31 March 1998
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 September 1998
Date of withdrawal of any conflicting National Standard (dow): 30 September 1998

6 EN 301 192 V1.1.1 (1997-12)
1 Scope
The present document is designed to be used in conjunction with EN 300 468 [2] and ETR 211 [4]. The DVB System
provides a means of delivering MPEG-2 Transport Streams (TS) via a variety of transmission media. These TSs have
traditionally been oriented to containing MPEG-2 Video and Audio. Data broadcasting is seen as an important extension
of the MPEG-2 based DVB transmission standards. Examples for data broadcasting are the download of software over
satellite, cable or terrestrial links, the delivery of Internet services over broadcast channels (IP tunnelling), interactive
TV etc. Four different application areas with different requirements for the data transport have been identified. For each
application area a data broadcasting profile is specified in the present document. The following is a short description of
the application areas and the profiles.
Data piping
- The data broadcast specification profile for data pipes supports data broadcast services that require a simple,
asynchronous, end-to-end delivery of data through DVB compliant broadcast networks. Data broadcast according
to the data pipe specification is carried directly in the payloads of MPEG-2 TS packets
(see ISO/IEC 13818-1 [1]).
Data streaming
- The data broadcast specification profile for data streaming supports data broadcast services that require a
streaming-oriented, end-to-end delivery of data in either an asynchronous, synchronous or synchronized way
through DVB compliant broadcast networks. Data broadcast according to the data streaming specification is
carried in Program Elementary Stream (PES) packets which are defined in MPEG-2 Systems
(see ISO/IEC 13818-1 [1]).
- Asynchronous data streaming is defined as the streaming of only data without any timing requirements
(e.g. RS-232 data).
- Synchronous data streaming is defined as the streaming of data with timing requirements in the sense that the data
and clock can be regenerated at the receiver into a synchronous data stream (e.g. E1, T1). Synchronized data
streaming is defined as the streaming of data with timing requirements in the sense that the data within the stream
can be played back in synchronization with other kinds of data streams (e.g. audio, video).
Multiprotocol encapsulation
- The data broadcast specification profile for multiprotocol encapsulation supports data broadcast services that
require the transmission of datagrams of communication protocols via DVB compliant broadcast networks.
The transmission of datagrams according to the multiprotocol encapsulation specification is done by
encapsulating the datagrams in DSM-CC sections (see ISO/IEC 13818-6 [5]), which are compliant with the
MPEG-2 private section format (see ISO/IEC 13818-1 [1]).
Data carousels
- The data broadcast specification for data carousels supports data broadcast services that require the periodic
transmission of data modules through DVB compliant broadcast networks. The modules are of known sizes and
may be updated, added to, or removed from the data carousel in time. Modules can be clustered into a group of
modules if required by the service. Likewise, groups can in turn be clustered into SuperGroups.
- Data broadcast according to the data carousel specification is transmitted in a DSM-CC data carousel which is
defined in MPEG-2 DSM-CC (see ISO/IEC 13818-6 [5]). This specification defines additional structures and
descriptors to be used in DVB compliant networks. The method is such that no explicit references are made to
PIDs and timing parameters enabling preparation of the content off-line.
Object carousels
- The object carousel specification has been added in order to support data broadcast services that require the
periodic broadcasting of DSM-CC User-User (U-U) Objects through DVB compliant broadcast networks,
specifically as defined by DVB Systems for Interactive Services (SIS) (see ETS 300 802 [10]). Data broadcast
according to the DVB object carousel specification is transmitted according to the DSM-CC Object Carousel and
DSM-CC Data Carousel specification which are defined in MPEG-2 DSM-CC (see ISO/IEC 13818-6 [5]).

7 EN 301 192 V1.1.1 (1997-12)
2 References
References may be made to:
a) specific versions of publications (identified by date of publication, edition number, version number, etc.), in
which case, subsequent revisions to the referenced document do not apply; or
b) all versions up to and including the identified version (identified by "up to and including" before the version
identity); or
c) all versions subsequent to and including the identified version (identified by "onwards" following the version
identity); or
d) publications without mention of a specific version, in which case the latest version applies.
A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
[1] ISO/IEC 13818-1: "Information technology - Generic coding of moving pictures and associated
audio information - Part 1: Systems - International Standard (IS)".
[2] EN 300 468: "Digital Video Broadcasting (DVB); Specification for Service Information (SI) in
DVB systems".
[3] ETR 162: "Digital Video Broadcasting (DVB); Allocation of Service Information (SI) codes for
DVB systems".
[4] ETR 211: "Digital Video Broadcasting (DVB); DVB guidelines on implementation and usage of
Service Information (SI)".
[5] ISO/IEC 13818-6: "Information technology - Generic coding of moving pictures and associated
audio information - Part 6: Extension for Digital Storage Media Command and Control (DSM-CC)
- International Standard (IS)".
[6] EN 300 472: "Digital Video Broadcasting (DVB); Specification for conveying ITU-R System B
Teletext in DVB bitstreams".
[7] RFC 1112 (August 1988): "Host extensions for IP multicast", S. Deering, Stanford University.
[8] RFC 1521 (09/23/1993): "MIME (Multipurpose Internet Mail Extensions) Part 1: Mechanisms for
Specifying and Describing the Format of Internet Message Bodies", N. Borenstein, N. Freed.
[9] RFC 1590 (03/02/1994): "Media Type Registration Procedure", J. Postel (Updates RFC1521).
[10] ETS 300 802: "Digital Video Broadcasting (DVB); Network-independent protocols for DVB
interactive services".
[11] ISO/IEC 8802-1/2: "Information technology; Telecommunications and information exchange
between systems; Local and metropolitan area networks; Specific requirements;
Part 1: Overview of Local Area Network Standards/
Part 2: Logical link control".
[12] ETS 300 743: "Digital Video Broadcasting (DVB); DVB subtitling system".
[13] ISO 8859: "Information processing - 8-bit single-byte coded graphic character sets, Latin
alphabets".
[14] ISO 639-2: "Code for the representation of names of languages".

8 EN 301 192 V1.1.1 (1997-12)
3 Abbreviations
For the purposes of the present document, the following abbreviations apply:
AFI Authority and Format Identifier
BCD Binary Coded Decimal
bslbf bit string, left bit first
CRC Cyclic Redundancy Code
DAVIC Digital Audio VIsual Council
DDB DownloadDataBlock
DII DownloadInfoIndication
DSI DownloadServerInitiate
DSM-CC DSM-CC data carousel specification
DVB Digital Video Broadcasting
EBU European Broadcasting Union
EIT Event Information Table
ETR ETSI Technical Report
ETS European Telecommunication Standard
gi GroupInfoBytes
IEC International Electrotechnical Commission
IEEE Institute of Electrical and Electronics Engineers (USA)
IP Internet Protocol
ISO International Organization for Standardization
LLC Logical Link Control
MAC Media Access Control
mi ModuleInfoBytes
MIME Multipurpose Internet Mail Extensions
MPEG Moving Pictures Expert Group
NSAP Network Service Access Point
OUI Organizational Unique Identifier
PCR Program Clock Reference
PES Program Elementary Stream
PID Packet IDentifier
PMT Program Map Table
PSI Program Specific Information
PTS Presentation Time Stamps
RFC Request For Comment
rpchof remainder polynomial coefficients, highest order first
RS Reed Solomon
SDT Service Description Table
SI Service Information
SIS Systems for Interactive Services
SNAP SubNetwork Attachment Point
TS Transport Stream
T-STD Transport System Target Decoder
uimsbf unsigned integer most significant bit first
U-U User-User
9 EN 301 192 V1.1.1 (1997-12)
4 Data piping
4.1 Data transport specification
The data broadcast service shall insert the data to be broadcast directly in the payload of MPEG-2 TS packets.
The data broadcast service may use the payload_unit_start_indicator field and the transport_priority field of the
MPEG-2 Transport Stream packets in a service private way. The use of the adaptation_field shall be MPEG-2
compliant.
The delivery of the bits in time through a data pipe is service private and is not specified in this specification.
4.2 PSI and SI specifications
The data broadcast service shall indicate the use of a data pipe by including one or more data_broadcast_descriptors in
SI (see EN 300 468 [2]). Each descriptor shall be associated with a particular data pipe 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 pipe.
4.2.1 Data_broadcast_descriptor
The data_broadcast_descriptor is used in the following way:
data_broadcast_id: this field shall be set to 0x0001 to indicate a DVB data pipe (see ETR 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 that is used as a data pipe.
selector_length: this field shall be set to zero.
selector_byte: this field is not present.
4.2.2 Stream type
The specification of the stream_type in the program map section is not defined in the present document.
5 Asynchronous data streaming
5.1 Data transport specification
The data broadcast service shall insert the data to be broadcast in PES packets as defined by MPEG-2 Systems
ISO/IEC 13818-1 [1]. The PES packets shall be of non-zero length. The mapping of the PES packets into MPEG-2
Transport Stream packets is defined in MPEG-2 Systems ISO/IEC 13818-1 [1].
The asynchronous data streaming specification uses the standard PES packet syntax and semantics with the following
constraints:
stream_id: this field shall be set to the value of 0xBF (private_stream_2).
PES_packet_length: this is a 16-bit field which shall be set to a non-zero value.

10 EN 301 192 V1.1.1 (1997-12)
5.2 PSI and SI specifications
The data broadcast service shall indicate the use of an asynchronous 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.
5.2.1 Data_broadcast_descriptor
The data broadcast descriptor is used in the following way:
data_broadcast_id: this field shall be set to 0x0002 to indicate an asynchronous data stream (see ETR 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.
5.2.2 Stream type
The presence of an asynchronous data stream in a service shall be indicated in the program map of that service by setting
the stream type of that stream to the value of 0x06 or an user private value.
6 Synchronous and synchronized data streaming
6.1 Data transport specification
The data broadcast service shall insert the data to be broadcast in PES packets as defined by MPEG-2 Systems. The PES
packets shall be of non-zero length. The mapping of the PES packets into MPEG-2 Transport Stream packets is defined
in MPEG-2 Systems ISO/IEC 13818-1 [1].
The synchronous and synchronized data streaming specifications use the standard PES packet syntax and semantics with
the following constraints:
stream_id: this field shall be set to the value of 0xBD (private_stream_1) or 0xBF (private_stream_2) for synchronous
data streams. For synchronized data streams this value shall be set to 0xBD (private_stream_1).
PES_packet_length: this is a 16-bit field which shall be set to a non-zero value.
The data is inserted in PES packets using the PES_data_packet structure. The syntax and semantics of the
PES_data_packet structure are defined in table 1.

11 EN 301 192 V1.1.1 (1997-12)
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 uimsbf
}
if (output_data_rate_flag=="1") {
Reserved 4 bslbf
output_data_rate 28 uimsbf
}
for (i=0;i PES_data_private_data_byte 8 bslbf
}
for (i=0;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 ETR 162 [3] and EN 300 472 [6]).
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 [6])
0x20 DVB subtitling (see ETS 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 an 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 an 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.

12 EN 301 192 V1.1.1 (1997-12)
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 synchronized data PTSs from the MPEG-2 standard
resolution of 11,1 μs (90 kHz) to 37 ns (27 MHz).
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 ETR 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 an 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 [5]). 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.

13 EN 301 192 V1.1.1 (1997-12)
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 IP_datagram_data_byte 8 bslbf
}
}
if (section_number == last_section_number) {
for (j=0;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 [5])).
section_syntax_indicator: this field shall be set as defined by ISO/IEC 13818-6 [5].
private_indicator: this field shall be set as defined by ISO/IEC 13818-6 [5].
reserved: this is a 2-bit field that shall be set to "11".

14 EN 301 192 V1.1.1 (1997-12)
section_length: this field shall be set as defined by ISO/IEC 13818-6 [5].
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.
MSB LSB
48-bit MAC address byte: 1 2 3 4 5 6
section MAC MAC last MAC MAC MAC MAC
.... .... ....
table
length address address reserved section address address address address
section:
id
number
6 5 4 3 2 1
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 subclause
(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.

15 EN 301 192 V1.1.1 (1997-12)
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 [11] 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.
checksum: this field shall be set as defined by ISO/IEC 13818-6 [5]. It is calculated over the entire datagram_section.
CRC_32: this field shall be set as defined by ISO/IEC 13818-6 [5]. It is calculated over the entire datagram_section.
7.2 PSI and SI specifications
The data broadcast service shall indicate the transmission of datagrams by including one or more data broadcast
descriptors in SI (see EN 300 468 [2] and ETR 162 [3]). Each descriptor shall be associated with a 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
table for the stream that is used to transmit the datagrams.
7.2.1 Data_broadcast_descriptor
The data broadcast descriptor is used in the following way:
data_broadcast_id: this field shall be set to 0x0005 to indicate the use of the multiprotocol encapsulation specification
(see also ETR 162 [3]).
component_tag: this field shall have the same value as a component_tag field of a stream_identifier_descriptor that
may be present in the PSI program map section for the stream on which the data is broadcast.
selector_length: this field shall be set to 0x02.
selector_byte: the selector bytes shall convey the multiprotocol_encapsulation_info structure which is defined in
table 6.
Table 6: Syntax for multiprotocol_encapsulation_info structure
Syntax No. of bits Mnemonic
multiprotocol_encapsulation_info () {
MAC_address_range 3 uimsbf
MAC_IP_mapping_flag 1 bslbf
alignment_indicator 1 bslbf
reserved 3 bslbf
max_sections_per_datagram 8 uimsbf
}
16 EN 301 192 V1.1.1 (1997-12)
The semantics of the multiprotocol_encapsulation_info structure are as follows:
MAC_address_range: this 3-bit field shall indicate the number of MAC address bytes that the service uses to
differentiate the receivers according to table 7.
Table 7: Coding of the MAC_address_range field
MAC_address_range valid MAC_address bytes
0x00 reserved
0x01 6
0x02 6,5
0x03 6,5,4
0x04 6,5,4,3
0x05 6,5,4,3,2
0x06 6,5,4,3,2,1
0x07 reserved
MAC_IP_mapping_flag: this is a 1-bit flag. The service shall set this flag to "1" if it uses the IP to MAC mapping as
described in RFC 1112 [7]. If this flag is set to "0", the mapping of IP addresses to MAC addresses is done outside the
scope of this specification.
alignment_indicator: this is a 1-bit field that shall indicate the alignment that exists between the bytes of the
datagram_section and the Transport Stream bytes according to table 8.
Table 8: Coding of the alignment_indicator field
value alignment in bits
00 8 (default)
01 32
reserved: this is a 3-bit field that shall be set to "111".
max_sections_per_datagram: this is a 8-bit field that shall indicate the maximum number of sections that can be used
to carry a single datagram unit.
7.2.2 Stream type
The presence of a multiprotocol 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 0x0D (see ISO/IEC 13818-6 [5]) or a user defined value.
8 Data carousels
8.1 Data transport specification
The specification of DVB data carousels is based on the DSM-CC data carousel specification (ISO/IEC 13818-6 [5]).
The DSM-CC data carousel specification embodies the cyclic transmission of data to receivers. The data transmitted
within the data carousel is organized in "modules" which are divided into "blocks". All blocks of all modules within the
data carousel are of the same size, except for the last block of each module which may be of a smaller size. Modules are
a delineation of logically separate groups of data within the data carousel. Modules can be clustered into a group of
modules if required by the service. Likewise, groups can in turn be clustered into SuperGroups.

17 EN 301 192 V1.1.1 (1997-12)
The data carousel specification uses four messages of the DSM-CC download specification. The data is carried in
DownloadDataBlock messages, while the control over the modules is provided by DownloadInfoIndication,
DownloadServerInitiate, and DownloadCancel messages. The Download-ServerInitiate message describes the groups in
a SuperGroup, while the DownloadInfoIndication message describes the modules in a group. Based on the control
messages, the receivers may acquire a subset of the modules from the network. The syntax and semantics of these
messages are defined in (see ISO/IEC 13818-6 [5]).
The use of these messages in DVB data carousels is described in the present document.
8.1.1 Structure of DVB data carousel
one-layer data carousel two-layer data carousel
SDT/EIT SDT/EIT
data_broadcast_desc data_broadcast_desc
transaction_id
DSI
gi gi
DII transaction_id DII transaction_id DII transaction_id
mi mi mi mi mi mi mi mi mi
DDB DDB DDB DDB DDB DDB DDB DDB DDB
DDB DDB DDB DDB DDB DDB DDB DDB DDB
DDB DDB DDB DDB
DDB
DDB
Block
Block
DDB DDB DDB
Block
Module
Module
Group
Group
SuperGroup
DSI: DownloadServerInitiate
gi: GroupInfoBytes
DII: DownloadInfoIndication
mi: ModuleInfoBytes
DDB: DownloadDataBlock
: Location reference (transactionId, optional componentTag)
Figure 2: Structure of the DVB data carousel
DVB data carousels can have one or two layers of control information as illustrated in figure 2. The simplest form of
DVB data carousels is a data carousel with one control layer which describes a single group. In this case, the SDT/EIT
tables contain a data_broadcast_descriptor that points to a DownloadInfoIndication message. This message describes the
modules in the data carousel using the ModuleInfoByte field. This field contains of a loop of descriptors that may
contain miscellaneous information, e.g. a pointer to the location of the DownloadDataBlock messages.
If two layers of clustering is required, a DownloadServerInitiate message is used to describe the different groups in the
SuperGroup. The DownloadInfoIndication message is used in the same way as with the one-layer data carousel.

18 EN 301 192 V1.1.1 (1997-12)
The DownloadServerInitiate message describes the groups with the GroupInfoByte field and allows for platform
differentiation. The GroupInfoByte field consist also of a loop of descriptors that may contain miscellaneous
information.
The decoder should be able to work with both types of carousels. The service provider can choose which type of
carousel to use.
Groups and modules can be transmitted on dedicated PIDs and/or shared PIDs. If no explicit location references are
given, the location is inherited from the control message. Each arrow in figure 2 represents the access information that is
required to acquire the message(s) to which the arrow points. Within DVB data carousels this information consists of:
1) a component tag, i.e. a pointer to a particular stream in the service; and
2) a transaction/module identifier, i.e. an unique identifier of a control message or a module.
Receivers can use these values to filter the messages from the stream efficiently.
Furthermore in the DownloadServerInitiate and DownloadInfoIndication messages parameters for the sizes of modules
and blocks have been specified, based on DSM-CC.
Within this specification the use of the compatibilityDescriptor() as specified by DSM-CC has been limited to a forward
reference mechanism from the DownloadServerInitiate message to DownloadInfoIndication messages.
All DownloadDataBlock and DownloadInfoIndication messages within a SuperGroup (in the case of a two layer data
carousel) or a group (in the case of a single layer data carousel) have the same downloadId. This implies that groups can
share modules be
...