ETSI ETS 300 468 ed.1 (1995-10)

SLOVENSKI STANDARD
01-november-2005
Sistemi digitalne radiodifuzije za televizijske, zvokovne in podatkovne storitve –
Specifikacije za servisne informacije v sistemih digitalne videoradiodifuzije (DVB)
Digital broadcasting systems for television, sound and data services – Specification for
service information (SI) in digital video broadcasting (DVB) systems
Ta slovenski standard je istoveten z: ETS 300 468 Edition 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.

EUROPEAN ETS 300 468
TELECOMMUNICATION October 1995
STANDARD
Source: EBU/ETSI JTC Reference: DE/JTC-DVB-5
ICS: 33.020
digital television broadcasting, Service Information (SI), MPEG
Key words:
European B roadcasting Union Union Européenne de Radio-Télévision
EBU
UER
Digital broadcasting systems for television,
sound and data services;
Specification for Service Information (SI) in
Digital Video Broadcasting (DVB) systems
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
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 1995.
© European Broadcasting Union 1995.
All rights reserved.
New presentation - see History box

Page 2
ETS 300 468: October 1995
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 468: October 1995
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .7
3.1 Definitions .7
3.2 Abbreviations .9
4 Service Information (SI) description .10
5 The SI tables .12
5.1 SI table mechanism .12
5.1.1 Explanation.13
5.1.2 Mapping of sections into Transport Stream packets.13
5.1.3 Coding of PID and table_id fields .14
5.1.4 Repetition rates and random access.15
5.1.5 Scrambling .15
5.2 Table definitions.15
5.2.1 Network Information Table (NIT).15
5.2.2 Bouquet Association Table (BAT) .17
5.2.3 Service Description Table (SDT).19
5.2.4 Event Information Table (EIT) .21
5.2.5 Time and Date Table (TDT) .24
5.2.6 Running Status Table (RST) .25
5.2.7 Stuffing Table (ST) .26
6 Descriptors .27
6.1 Descriptor identification and location .27
6.2 Descriptor coding.27
6.2.1 Bouquet name descriptor .28
6.2.2 CA identifier descriptor.28
6.2.3 Component descriptor.29
6.2.4 Content descriptor.30
6.2.5 Country availability descriptor.33
6.2.6 Delivery system descriptors .34
6.2.6.1 Cable delivery system descriptor.34
6.2.6.2 Satellite delivery system descriptor .35
6.2.7 Extended event descriptor.37
6.2.8 Linkage descriptor.38
6.2.9 Mosaic descriptor .39
6.2.10 Near Video On Demand (NVOD) reference descriptor.42
6.2.11 Network name descriptor .43
6.2.12 Parental rating descriptor .43
6.2.13 Service descriptor.44
6.2.14 Service list descriptor .45
6.2.15 Short event descriptor .45
6.2.16 Stream identifier descriptor .46
6.2.17 Stuffing descriptor .46
6.2.18 Telephone descriptor.47
6.2.19 Teletext descriptor.48
6.2.20 Time shifted event descriptor .49
6.2.21 Time shifted service descriptor .49
Annex A (normative): Coding of text characters .50

Page 4
ETS 300 468: October 1995
A.1 Control codes. 50
A.2 Selection of character table . 50
Annex B (normative): CRC decoder model . 57
Annex C (informative): Conversion between time and date conventions . 58
Annex D (informative): Bibliography . 60
History. 61

Page 5
ETS 300 468: October 1995
Foreword
This European Telecommunication Standard (ETS) was produced under the authority of the Joint
Technical Committee (JTC) of the European Broadcasting Union (EBU) and the European
Telecommunications Standards Institute (ETSI).
This ETS for Service Information (SI) in Digital Video Broadcasting (DVB) systems has been produced by
Project Team 55V using as a basis, the DVB Steering Board approved specification TM1217 Rev 2.
NOTE: The EBU/ETSI JTC was established in 1990 to co-ordinate the drafting of ETSs in the
specific field of radio, television and data broadcasting. The EBU is a professional
association of broadcasting organisations 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
Case Postale 67
CH-1218 GRAND SACONNEX (Geneva)
Switzerland
Tel: +41 22 717 21 11
Fax: +41 22 717 24 81
Transposition dates
Date of adoption of this ETS: 1 September 1995
Date of latest announcement of this ETS (doa): 31 January 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 July 1996
Date of withdrawal of any conflicting National Standard (dow): 31 July 1996

Page 6
ETS 300 468: October 1995
Blank page
Page 7
ETS 300 468: October 1995
1 Scope
This European Telecommunication Standard (ETS) specifies the Service Information (SI) data which
forms a part of DVB bitstreams, in order that the user can be provided with information to assist in
selection of services and/or events within the bitstream, and so that the Integrated Receiver Decoder
(IRD) can automatically configure itself for the selected service. SI data for automatic configuration is
mostly specified within ISO/IEC 13818-1 [1] as Program Specific Information (PSI). The ETS specifies
additional data which complements the PSI by providing data to aid automatic tuning of IRDs, and
additional information intended for display to the user. The manner of presentation of the information is not
specified in this ETS, and IRD manufacturers have freedom to choose appropriate presentation methods.
It is expected that Electronic Programme Guides (EPGs) will be a feature of Digital TV transmissions. The
definition of an EPG is outside the scope of the SI specification, but the data contained within the SI
specified here may be used as the basis for an EPG.
2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this ETS only when incorporated in it by amendment or revision. For undated references the latest
edition of the publication referred to applies.
[1] ISO/IEC 13818-1 (1994): "Information Technology - Generic Coding of Moving
Pictures and Associated Audio Recommendation H.222.0 (systems)".
[2] ISO 3166: "Codes for the representation of names of countries".
[3] ISO 639: "Code for the representation of names of languages".
[4] EBU SPB 492 (1992): "Teletext specification (625 line Television Systems)".
[5] ISO 8859: "Information processing - 8-bit single-byte coded graphic character
sets, Latin alphabets".
[6] ETR 162: "Digital broadcasting systems for television, sound and data services;
Allocation of Service Information (SI) codes for Digital Video Broadcasting
(DVB) systems".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of this ETS, the following definitions apply:
bouquet: A collection of services marketed as a single entity.
broadcaster (service provider): An organisation which assembles a sequence of events or programmes
to be delivered to the viewer based upon a schedule.
component (elementary stream): One or more entities which together make up an event, e.g. video,
audio, teletext.
Conditional Access (CA) system: A system to control subscriber access to services, programmes and
events e.g. Videoguard, Eurocrypt.
delivery system: The physical medium by which one or more multiplexes are transmitted e.g. satellite
transponder, wide-band coaxial cable, fibre optics.

Page 8
ETS 300 468: October 1995
Entitlement Management Messages (EMM): Are private Conditional Access information which specify
the authorization levels or the services of specific decoders. They may be addressed to individual decoder
or groups of decoders.
event: A grouping of elementary broadcast data streams with a defined start and end time belonging to a
common service, e.g. first half of a football match, News Flash, first part of an entertainment show.
forbidden: The term "forbidden" when used in the clauses defining the coded bit stream, indicates that
the value shall never be used.
MPEG-2: Refers to the standard ISO/IEC 13818 [1]. Systems coding is defined in part 1. Video coding is
defined in part 2. Audio coding is defined in part 3.
multiplex: A stream of all the digital data carrying one or more services within a single physical channel.
network: A collection of MPEG-2 Transport Stream multiplexes transmitted on a single delivery system,
e.g. all digital channels on a specific cable system.
original_network_id: A unique identifier of a network.
programme: A concatenation of one or more events under the control of a broadcaster e.g. news show,
entertainment show.
reserved: The term "reserved" when used in the clause defining the coded bit stream, indicates that the
value may be used in the future for ISO defined extensions. Unless otherwise specified within this ETS all
"reserved" bits shall be set to "1".
reserved_future_use: The term "reserved_future_use", when used in the clause defining the coded bit
stream, indicates that the value may be used in the future for ETSI defined extensions. Unless otherwise
specified within this ETS all "reserved_future_use" bits shall be set to "1".
section: A section is a syntactic structure used for mapping all service information defined in this ETS into
ISO/IEC 13818 [1] Transport Stream packets.
service: A sequence of programmes under the control of a broadcaster which can be broadcast as part of
a schedule.
service_id: A unique identifier of a service within a transport stream.
Service Information (SI): Digital data describing the delivery system, content and scheduling/timing of
broadcast data streams etc. It includes MPEG-2 PSI together with independently defined extensions.
sub_table: A sub_table is collection of sections with the same value of table_id and:
for a NIT: the same table_id_extension (network_id) and version_number;
for a BAT: the same table_id_extension (bouquet_id) and version_number;
for a SDT: the same table_id_extension (transport_stream_id), the same
original_network_id and version_number;
for a EIT: the same table_id_extension (service_id), the same transport_stream_id, the
same original_network_id and version_number
The table_id_extension field is equivalent to the fourth and fifth byte of a section when the
section_syntax_indicator is set to a value of "1".
table: A table is comprised of a number of sub_tables with the same value of table_id.
Transport Stream: A Transport Stream is a data structure defined in ISO/IEC 13818-1 [1]. It is the basis
of the ETSI Digital Video Broadcasting (DVB) standards.
transport_stream_id: A unique identifier of a transport stream within an original network.

Page 9
ETS 300 468: October 1995
The relationships of some of these definitions are illustrated in the service delivery model in figure 1.
Satellite Terrestrial
Cable
Networks
Transponder Transponder Transponder Transponder
Channel Channel Channel Channel C hannel Channel
M ultiplexes
Bouquet
Service Service Service Service Service Service Service Service Service
Service
Services
Components
V ideo A udio 1 A udio 2 D ata
Figure 1: Digital broadcasting, service delivery model
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
BAT Bouquet Association Table
BCD Binary Coded Decimal
CA Conditional Access
CAT Conditional Access Table
CRC Cyclic Redundancy Check
DVB Digital Video Broadcasting
EBU European Broadcasting Union
EIT Event Information Table
EMM Entitlement Management Message
EPG Electronic Programme Guide
ETS European Telecommunication Standard
ETSI European Telecommunications Standards Institute
FEC Forward Error Correction
IEC International Electrotechnical Commission
IRD Integrated Receiver Decoder
ISO International Organisation for Standardisation
JTC Joint Technical Committee
LSB Least Significant Bit
MJD Modified Julian Date
MPEG Moving Pictures Expert Group
NIT Network Information Table
NVOD Near Video On Demand
PAT Program Association Table
PID Packet IDentifier
PMT Program Map Table
PSI Program Specific Information
PSTN Public Switched Telephone Network

Page 10
ETS 300 468: October 1995
QAM Quadrature Amplitude Modulation
QPSK Quaternary Phase Shift Keying
RS Reed Solomon
RST Running Status Table
SDT Service Description Table
SI Service Information
ST Stuffing Table
TDT Time and Date Table
UTC Universal Time, Co-ordinated
bslbf bit string, left bit first
rpchof remainder polynomial coefficients, highest order first
uimsbf unsigned integer most significant bit first
4 Service Information (SI) description
ISO/IEC 13818 [1] specifies SI which is referred to as PSI. The PSI data provides information to enable
automatic configuration of the receiver to demultiplex and decode the various streams of programs within
the multiplex.
The PSI data is structured as four types of table. The tables are transmitted in sections.
1) Program Association Table (PAT):
- for each service in the multiplex, the PAT indicates the location (the PID values of the Transport
Stream packets) of the corresponding Program Map Table (PMT). It also gives the location of the
Network Information Table (NIT).
2) Conditional Access Table (CAT):
- the CAT provides information on the Conditional Access (CA) systems used in the multiplex; the
information is private (not defined within this ETS) and dependent on the CA system, but includes
the location of the EMM stream, when applicable.
3) Program Map Table (PMT):
- the PMT identifies and indicates the locations of the streams that make up each service, and the
location of the Program Clock Reference fields for a service.
4) Network Information Table (NIT):
- the location of the NIT is defined in this ETS in compliance with ISO/IEC 13818-1 [1] specification,
but the data format is outside the scope of ISO/IEC 13818-1 [1]. It is intended to provide information
about the physical network. The syntax and semantics of the NIT are defined in this ETS.
In addition to the PSI, data is needed to provide identification of services and events for the user. The
coding of this data is defined in this ETS. In contrast with the PAT, CAT, and PMT of the PSI, which give
information only for the multiplex in which they are contained (the actual multiplex), the additional
information defined within this ETS can also provide information on services and events carried by
different multiplexes, and even on other networks. This data is structured as six tables:
1) Bouquet Association Table (BAT):
- the BAT provides information regarding bouquets. As well as giving the name of the bouquet, it
provides a list of services for each bouquet.
2) Service Description Table (SDT):
- the SDT contains data describing the services in the system e.g. names of services, the service
provider, etc.
Page 11
ETS 300 468: October 1995
3) Event Information Table (EIT):
- the EIT contains data concerning events or programmes such as event name, start time, duration,
etc.;
- the use of different descriptors allows the transmission of different kinds of event information e.g.
for different service types.
4) Running Status Table (RST):
- the RST gives the status of an event (running/not running). The RST updates this information and
allows timely automatic switching to events.
5) Time and Date Table (TDT):
- the TDT gives information relating to the present time and date. This information is given in a
separate table due to the frequent updating of this information.
6) Stuffing Table (ST):
the ST is used to invalidate existing sections, for example at delivery system boundaries.
Where applicable the use of descriptors allows a flexible approach to the organisation of the tables and
allows for future compatible extensions.

Page 12
ETS 300 468: October 1995
Figure 2: General organisation of the SI
5 The SI tables
5.1 SI table mechanism
The SI specified in this ETS and MPEG-2 PSI tables shall be segmented into one or more sections before
being inserted into Transport Stream 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 subclause 5.1.5). A
section is a syntactic structure that shall be used for mapping all MPEG-2 tables and SI tables specified in
this ETS, into Transport Stream packets. These SI syntactic structures conform to the private section
syntax defined in ISO/IEC 13818-1 [1].

Page 13
ETS 300 468: October 1995
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 subclause 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 this ETS, section numbering applies to sub_tables.
d) version_number:
When the characteristics of the Transport Stream described in the SI given in this ETS 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 this ETS, 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 packets
Sections shall be mapped directly into Transport Stream packets. Sections may start at the beginning of
the payload of a Transport Stream packet, but this is not a requirement, because the start of the first
section in the payload of a Transport Stream packet is pointed to by the pointer_field. There is never more
than one pointer_field in a Transport Stream 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
Transport Stream packet are allowed by the syntax.
Within Transport Stream 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 Transport Stream 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 Transport Stream 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 Transport Stream 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.

Page 14
ETS 300 468: October 1995
For a more detailed description of the mechanism and functionality, refer to ISO/IEC 13818-1 [1],
specifically section 2.4.4 and Annex C.
5.1.3 Coding of PID and table_id fields
Table 1 lists the PID values which shall be used for the Transport Stream packets which carry SI sections.
Table 1: PID allocation for SI
Table PID value
PAT 0x0000
CAT 0x0001
reserved 0x0002 to 0x000F
NIT, ST 0x0010
SDT, BAT, ST 0x0011
EIT, ST 0x0012
RST, ST 0x0013
TDT 0x0014
reserved for future use 0x0015 to 0x001F
Table 2 lists the values which shall be used for table_id for the service information, defined in this ETS.
Table 2: Allocation of table_id values
Value Description
0x00 program_association_section
0x01 conditional_access_section
0x02 program_map_section
0x03 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 to 0x7F reserved for future use
0x80 to 0xFE user defined
0xFF reserved
Page 15
ETS 300 468: October 1995
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 this ETS several times, even when changes do not occur in the configuration.
For SI specified within this ETS 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 milliseconds. This limit applies for Transport
Streams 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 this ETS shall not be
scrambled. One method for scrambling the EIT schedule table is given in the Bibliography 2). If a
scrambling method operating over Transport Stream 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 [1]) 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 subclauses describe the syntax and semantics of the different types of table.
NOTE: The symbols and abbreviations, and the method of describing syntax used in this ETS
are the same as those defined in sections 2.2 and 2.3 of ISO/IEC 13818-1 [1].
5.2.1 Network Information Table (NIT)
The NIT (see table 3) conveys information relating to the physical organisation of the
multiplexes/Transport Streams carried via a given network, and the characteristics of the network itself.
The combination of original_network_id and transport_stream_id allow each Transport Stream to be
uniquely identified throughout the ETS application area. Networks are assigned individual network_id
values, which serve as unique identification codes for networks. The allocation of these codes may be
found in ETR 162 [6]. In the case that the NIT is transmitted on the network on which the Transport
Stream was originated, the network_id and the original_network_id shall take the same value.
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).
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 Transport Stream packets with a PID value of 0x0010. Any
sections of the NIT which describe the actual network (that is, the network of which the Transport Stream
containing the NIT is a part) shall have the table_id value 0x40 with the network_id field taking the value
assigned to the actual network in ETR 162 [6]. 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 ETR 162 [6].

Page 16
ETS 300 468: October 1995
Table 3: Network information section
Syntax No. of Identifier
bits
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 descriptor()
}
reserved_future_use 4  bslbf
transport_stream_loop_length 12  uimsbf
for(i=0;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 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 ETR 162 [6].
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.

Page 17
ETS 300 468: October 1995
section_number: this 8-bit field gives the number of the section. The section_number of the first section
in the sub_table shall be "0x00". The section_number shall be incremented by 1 with each additional
section with the same table_id and network_id.
last_section_number: this 8-bit field specifies the number of the last section (that is, the section with the
highest section_number) of the sub_table of which this section is part.
network_descriptors_length: this 12-bit field gives the total length in bytes of the following network
descriptors.
transport_stream_loop_length: this is a 12-bit field specifying the total length in bytes of the Transport
Stream loops that follow, ending immediately before the first CRC-32 byte.
transport_stream_id: this is a 16-bit field which serves as a label for identification of this Transport
Stream from any other multiplex within the delivery system.
original_network_id: this 16-bit field gives the label identifying the network_id of the originating delivery
system.
transport_descriptors_length: this is a 12-bit field specifying the total length in bytes of Transport
Stream descriptors that follow.
CRC_32: this is a 32-bit field that contains the CRC value that gives a zero output of the registers in the
decoder defined in annex B after processing the entire section.
5.2.2 Bouquet Association Table (BAT)
The BAT (see table 4) provides information regarding bouquets. A bouquet is a collection of services,
which may traverse the boundary of a network.
The BAT shall be segmented into bouquet_association_sections using the syntax of table 4. Any sections
forming part of a BAT shall be transmitted in Transport Stream packets with a PID value of 0x0011. The
sections of a BAT sub_table describing a particular bouquet shall have the bouquet_id field taking the
value assigned to the bouquet described in ETR 162 [6]. All BAT sections shall take a table_id value of
0x4A.
Page 18
ETS 300 468: October 1995
Table 4: Bouquet association section
Syntax No. of Identifier
bits
bouquet_association_section(){
table_id 8  uimsbf
section_syntax_indicator 1  bslbf
reserved_future_use 1  bslbf
reserved 2  bslbf
section_length 12  uimsbf
bouquet_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
bouquet_descriptors_length 12  uimsbf
for(i=0;i descriptor()
}
reserved_future_use 4  bslbf
transport_stream_loop_length 12  uimsbf
for(i=0;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 descriptor()
}
}
CRC_32 32  rpchof
}
Semantics for the bouquet association 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.
bouquet_id: this is a 16-bit field which serves as a label to identify the bouquet. Allocations of the value of
this field are found in ETR 162 [6].
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 bouquet_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 bouquet_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.

Page 19
ETS 300 468: October 1995
section_number: this 8-bit field gives the number of the section. The section_number of the first section
in the sub_table shall be "0x00". The section_number shall be incremented by 1 with each additional
section with the same table_id and bouquet_id.
last_section_number: this 8-bit field specifies the number of the last section (that is, the section with the
highest section_number) of the sub_table of which this section is part.
bouquet_descriptors_length: this 12-bit field gives the total length in bytes of the following descriptors.
transport_stream_loop_length: this is a 12-bit field specifying the total length in bytes of the Transport
Stream loop that follows.
transport_stream_id: this is a 16-bit field which serves as a label for identification of this Transport
Stream from any other multiplex within the delivery system.
original_network_id: this 16-bit field gives the label identifying the network_id of the originating delivery
system.
transport_descriptors_length: this is a 12-bit field specifying the total length in bytes of Transport
Stream descriptors that follow.
CRC_32: This is a 32-bit field that contains the CRC value that gives a zero output of the registers in the
decoder defined in annex B after processing the entire private section.
5.2.3 Service Description Table (SDT)
Each sub_table of the SDT (see table 5) shall describe services that are contained within a particular
Transport Stream. The services may be part of the actual Transport Stream or part of other Transport
Streams, these being identified by means of the table_id (see table 2).
The SDT shall be segmented into service_description_sections using the syntax of table 5. Any sections
forming part of an SDT shall be transmitted in Transport Stream packets with a PID value of 0x0011. Any
sections of the SDT which describe the actual Transport Stream (that is, the Transport Stream containing
the SDT) shall have the table_id value 0x42, and any sections of an SDT which refer to a Transport
Stream other than the actual Transport Stream shall take a table_id value of 0x46.

Page 20
ETS 300 468: October 1995
Table 5: Service description section
Syntax No. of Identifier
bits
service_description_section(){
table_id 8  uimsbf
section_syntax_indicator 1  bslbf
reserved_future_use 1  bslbf
reserved 2  bslbf
section_length 12  uimsbf
transport_stream_id 16  uimsbf
reserved 2  bslbf
version_number 5  uimsbf
current_next_indicator 1  bslbf
section_number 8  uimsbf
last_section_number 8  uimsbf
original_network_id 16  uimsbf
reserved_future_use 8  bslbf
for (i=0;i service_id 16  uimsbf
reserved_future_use 6  bslbf
EIT_schedule_flag 1  bslbf
EIT_present_following_flag 1  bslbf
running_status 3  uimsbf
free_CA_mode 1  bslbf
descriptors_loop_length 12  uimsbf
for (j=0;j descriptor()
}
}
CRC_32 32  rpchof
}
Semantics for the service description 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.
transport_stream_id: this is a 16-bit field which serves as a label for identification of the Transport
Stream, about which the SDT informs, from any other multiplex within the delivery system.
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. When the current_next_indicator is set to "0", then the
version_number shall be that of the next applicable sub_table.
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.
section_number: this 8-bit field gives the number of the section. The section_number of the first section
in the sub_table shall be "0x00". The section_number shall be incremented by 1 with each additional
section with the same table_id, transport_stream_id, and original_network_id.

Page 21
ETS 300 468: October 1995
last_section_number: this 8-bit field specifies the number of the last section (that is, the section with the
highest section_number) of the sub_table of which this section is part.
original_network_id: this 16-bit field gives the label identifying the network_id of the originating delivery
system.
service_id: this is a 16-bit field which serves as a label to identify this service from any other service
within the Transport Stream. The service_id is the same as the program_number in the corresponding
program_map_section.
EIT_schedule_flag: this is a 1-bit field which when set to "1" indicates that EIT sche
...