ETSI TS 102 371 V1.3.1 (2008-07)

Digital Audio Broadcasting (DAB); Digital Radio Mondiale (DRM); Transportation and Binary Encoding Specification for Electronic Programme Guide (EPG)

RTS/JTC-DAB-58

General Information

• Status: Published
• Publication Date: 02-Jul-2008
• Technical Committee: BROADCAS - EBU/CENELEC/ETSI on Broadcasting
• Current Stage: 12 - Completion
• Due Date: 10-Jul-2008
• Completion Date: 03-Jul-2008

Standards Content (Sample)

Technical Specification
Digital Audio Broadcasting (DAB);
Digital Radio Mondiale (DRM);
Transportation and Binary Encoding Specification for
Electronic Programme Guide (EPG)

European Broadcasting Union Union Européenne de Radio-Télévision
EBU·UER
2 ETSI TS 102 371 V1.3.1 (2008-07)

Reference
RTS/JTC-DAB-58
Keywords
audio, broadcasting, DAB, DRM, digital, EPG
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

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

Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org
The present document may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive
within ETSI Secretariat.
Users of the present document should be aware that the document may be subject to revision or change of status.
Information on the current status of this and other ETSI documents is available at
http://portal.etsi.org/tb/status/status.asp
If you find errors in the present document, please send your comment to one of the following services:
http://portal.etsi.org/chaircor/ETSI_support.asp
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 2008.
© European Broadcasting Union 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI TS 102 371 V1.3.1 (2008-07)
Contents
Intellectual Property Rights.5
Foreword.5
Introduction .5
1 Scope.6
2 References.6
2.1 Normative references.6
2.2 Informative references.7
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.7
4 Encoding.8
4.1 Syntax specification.8
4.2 Binary objects.9
4.3 Elements.9
4.3.1 Top-level elements.10
4.4 Attributes.10
4.4.1 Default attributes.11
4.5 CDATA and strings.11
4.5.1 Character sets.11
4.6 Enumerated data values.12
4.7 Common data types.12
4.7.1 Date and time.12
4.7.2 Duration.13
4.7.3 CRIDs.13
4.7.4 Short CRIDs.13
4.7.5 Genres.13
4.7.6 contentID.14
4.7.6.1 DAB EPG.14
4.7.6.2 DRM EPG.15
4.7.7 ensembleID.16
4.7.7.1 DAB EPG.16
4.7.7.2 DRM EPG.16
4.7.8 triggerType/PNum.16
4.7.9 URL.16
4.7.10 MIME type.16
4.8 Miscellaneous fields.16
4.8.1 xml:lang.16
4.8.2 index.16
4.8.3 version.17
4.8.4 bitrate.17
4.8.5 kHz.17
4.8.6 numOfItems.17
4.8.7 width and height.17
4.8.8 extFormat.17
4.8.8.1 DAB EPG.17
4.8.8.2 DRM EPG.17
4.9 Token table element .18
4.9.1 Tokens.18
4.10 Default contentID.19
4.11 Default language.19
5 Profiling.19
5.1 Profiles.19
5.1.1 Basic profile.19
ETSI
4 ETSI TS 102 371 V1.3.1 (2008-07)
5.1.2 Advanced profile.19
5.2 Fragmentation of the profile data into objects.20
5.2.1 Service Information (SI) .20
5.2.2 Programme Information (PI).20
5.2.3 Group Information (GI) .20
5.3 Scheme to combine the profile data .21
5.4 Attributes required for merging.21
5.4.1 Service Information.21
5.4.2 Programme Information.21
5.4.3 Group Information.21
6 Transportation.22
6.1 Transport mechanism.22
6.2 Maximum object size .22
6.3 Maximum channel size.22
6.4 MOT parameters.22
6.4.1 MOT header core.23
6.4.2 ProfileSubset.23
6.4.3 ContentName.23
6.4.4 CompressionType.24
6.4.5 CAInfo .24
6.4.6 ScopeStart.24
6.4.7 ScopeEnd.24
6.4.8 ScopeID.24
6.5 Transportation of other objects.25
7 Signalling.25
7.1 DAB.25
7.1.1 FIG 0/13 (application type) signalling.25
7.1.2 FIG0/9 and FIG 0/10 (Reference time) signalling .25
7.1.3 FIG 0/16 (PNum) signalling .25
7.2 DRM.26
7.2.1 Data entity type 5 (data application) signalling .26
7.2.2 Data entity type 8 (reference time) signalling.26
7.2.3 FAC data application signalling.26
Annex A (normative): Profiling tables .27
A.1 Elements and attributes that are transmitted in the "Basic" profile.27
A.1.1 Service Information (SI).28
A.1.2 Programme Information (PI) .29
A.1.3 Group Information (GI).29
A.2 Elements and attributes that are transmitted in the "Advanced" profile.30
Annex B (informative): Profiling examples.31
B.1 Profiling/fragmenting example 1.31
B.2 Profiling/fragmenting example 2.32
Annex C (informative): Binary encoding example .34
Annex D (normative): Element tags .35
Annex E (normative): Attribute tags.36
Annex F (normative): Enumerated types .38
History .39

ETSI
5 ETSI TS 102 371 V1.3.1 (2008-07)
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 ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in
respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web
server (http://webapp.etsi.org/IPR/home.asp).
Pursuant to the ETSI 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 ETSI SR 000 314 (or the updates on the ETSI Web
server) which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by Joint Technical Committee (JTC) Broadcast of the European
Broadcasting Union (EBU), Comité Européen de Normalisation ELECtrotechnique (CENELEC) and the European
Telecommunications Standards Institute (ETSI).
NOTE 1: The EBU/ETSI JTC Broadcast was established in 1990 to co-ordinate the drafting of standards in the
specific field of broadcasting and related fields. Since 1995 the JTC Broadcast 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: [phone]
Fax: [phone]
The Eureka Project 147 was established in 1987, with funding from the European Commission, to develop a system for
the broadcasting of audio and data to fixed, portable or mobile receivers. Their work resulted in the publication of
European Standard, EN 300 401 [3], for DAB (see note 2) which now has worldwide acceptance. The members of the
Eureka Project 147 are drawn from broadcasting organizations and telecommunication providers together with
companies from the professional and consumer electronics industry.
NOTE 2: DAB is a registered trademark owned by one of the Eureka Project 147 partners.
Introduction
The present document defines how the EPG data will be transported, compressed and profiled such that a good user
experience can be achieved using limited broadcast capacity. Using a combination of EPG profiles it is possible that a
range of features could be supported in receivers, including:
• The display of schedules at varying levels of detail for programmes from a range of services.
• The display of schedules, with programmes and events ordered into particular groups.
• Navigation and selection of services and programmes.
• Searching through current and future programme listings.
• Timed recording of individual programmes, or of groups of programmes and themed or similar programming.
• Accurate timed recording of programmes and events using PNum signalling.
ETSI
6 ETSI TS 102 371 V1.3.1 (2008-07)
1 Scope
The present document defines how the XML schema data model for an Electronic Programme Guide (EPG)
(TS 102 818 [1]) should be compressed, profiled and broadcast. Within the present document the term "DAB" is used to
refer to the Eureka-147 Digital Audio Broadcasting standard (EN 300 401 [3]) and "DRM" is used to refer to the Digital
Radio Mondiale standard (ES 201 980 [6]).
2 References
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• Non-specific reference may be made only to a complete document or a part thereof and only in the following
cases:
- if it is accepted that it will be possible to use all future changes of the referenced document for the
purposes of the referring document;
- for informative references.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://docbox.etsi.org/Reference.
For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably,
the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the
reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the
method of access to the referenced document and the full network address, with the same punctuation and use of upper
case and lower case letters.
NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee
their long term validity.
2.1 Normative references
The following referenced documents are indispensable for the application of the present document. For dated
references, only the edition cited applies. For non-specific references, the latest edition of the referenced document
(including any amendments) applies.
[1] ETSI TS 102 818: "Digital Audio Broadcasting (DAB); Digital Radio Mondial (DRM); XML
Specification for DAB Electronic Programme Guide (EPG)".
[2] ETSI EN 301 234: "Digital Audio Broadcasting (DAB); Multimedia Object Transfer (MOT)
Protocol".
[3] ETSI EN 300 401: "Radio broadcasting systems; Digital Audio Broadcasting (DAB) to mobile,
portable and fixed receivers".
[4] ISO/IEC 10646: "Information technology - Universal Multiple-Octet Coded Character Set (UCS)".
[5] ETSI TS 101 756: "Digital Audio Broadcasting (DAB); Registered Tables".
[6] ETSI ES 201 980: "Digital Radio Mondiale (DRM); System specification".
[7] ETSI TS 101 968: "Digital Radio Mondiale (DRM); Data applications directory".
ETSI
7 ETSI TS 102 371 V1.3.1 (2008-07)
2.2 Informative references
The following referenced documents are not essential to the use of the present document but they assist the user with
regard to a particular subject area. For non-specific references, the latest version of the referenced document (including
any amendments) applies.
Not applicable.
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
Conditional Access (CA): mechanism by which the user access to service components can be restricted
data service: service which comprises a non-audio primary service component and optionally secondary service
components
entity reference: a group of characters used in text strings as a substitute for a single specific character, e.g. &
ensemble: transmitted signal, comprising a set of regularly and closely-spaced orthogonal carriers
NOTE: The ensemble is the entity that is received and processed. In general, it contains audio and data services.
Ensemble Identifier (EId): unique 16-bit code, allocated to an ensemble and intended to allow unambiguous
worldwide identification of that ensemble
Extended Programme Associated Data (X-PAD): extended part of the PAD carried towards the end of the DAB
audio frame, immediately before the Scale Factor Cyclic Redundancy Check (CRC), its length is variable
Programme Associated Data (PAD): information that is related to the audio data in terms of contents and
synchronization
NOTE: The PAD field is located at the end of the DAB audio frame.
secondary service component: in the case where a service contains more than the primary service component, the
additional service components are secondary service components
service: in TS 102 371 the term "service" is used to refer to a "radio station" such as BBC Radio 4 or Oneword. In strict
DAB terms this is actually a service component of a service
service component: part of a service which carries either audio (including PAD) or data
NOTE: The service components of a given service are linked together by the Multiplex Configuration
Information. Each service component is carried either in a sub-channel or in the Fast Information Data
Channel.
Service Identifier (SId): 16-bit, 24-bit or 32-bit code used to identify a particular service
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
CA Conditional Access
CRC Cyclic Redundancy Check
CRID Content Reference ID
DAB Digital Audio Broadcasting
DRM Digital Radio Mondiale
ECC Extended Country Code
EId Ensemble Identifier
ETSI
8 ETSI TS 102 371 V1.3.1 (2008-07)
EPG Electronic Programme Guide
FAC Fast Access Channel (DRM Multiplex Component)
GI Group Information
GZIP GnuZIP
ISO International Organization for Standardization
LTO Local Time Offset
MIME Multipurpose Internet Mail Extensions
MJD Modified Julian Date
MOT Multimedia Object Transfer
PAD Programme Associated Data
PI Programme Information
PNum Programme Number
Rfa Reserved for future addition
Rfu Reserved for future use
SCIdS Service Component Identifier within the Service
SI Service Information
SId Service Identifier
URL Uniform Resource Location
UTC Co-ordinated Universal Time
XML eXtensible Markup Language
X-PAD eXtended - Programme Associated Data
4 Encoding
There will be no transmission of the raw EPG XML data (TS 102 818 [1]). The XML specification should still be used
to construct the valid information; this binary specification is then used to encode this information in a compact binary
form.
The binary encoding described here uses a tag-length-value encoding. Each element or attribute is encoded using a
unique tag value, a length value (indicating the length of the data contained within this element or attribute) and the
actual data value(s). This enables receivers to easily skip elements that are not wanted or were undefined.

Tag Length Value Tag Length
Figure 1: Tag-length-value encoding scheme
XML elements are all encoded in these binary structures as described in clause 4.2. Attributes are coded in a similar
way (see clause 4.4). The hierarchical nature of the EPG XML is generally preserved in these binary structures, but the
structure is not necessarily identical. Various common data types have been assigned efficient binary encodings as
described in clause 4.7. For an example of a binary encoded XML object, see annex C.
Note that although the length of certain data types can be worked out from their encoding, there shall still be a length
field in the attribute encoding (see clause 4.4).
4.1 Syntax specification
The specifications of syntax that appear in the present document are written using a form of pseudo-code that is similar
to the procedural language "C"; this provides for easy specification of loops and conditional data structures. Within
these specifications, the type of individual data fields is expressed using the mnemonics given in table 1.
Table 1: Data type mnemonics for syntax specification
Mnemonic Description
Uimsbf Unsigned integer, most significant bit first

ETSI
9 ETSI TS 102 371 V1.3.1 (2008-07)
4.2 Binary objects
The basic binary objects defined by the present document are defined in table 2. Each binary object carries a single top
level element and shall be carried within a single MOT object.
Table 2: Structure of a binary object
Syntax Size Type
binary_object() {
top_level_element()
top_level_element: A top level element as defined in clause 4.3.1.
4.3 Elements
All elements use basically the same encoding, as defined here.
Table 3: Structure of an element
Syntax Size Type
element() {
element_tag
8 bits uimsbf
element_length
8 bits uimsbf
If (element_length == 0xFE) {
extended_element_length
16 bits uimsbf
}
If (element_length == 0xFF) {
extended_element_length
24 bits uimsbf
}
for (i=0; I
element_data_byte
8 bits uimsbf
}
}
element_tag: This byte identifies the element. The tag uniquely identifies the element - i.e. there is a one to one
mapping between a tag and an element. If new elements are required in the future then they will use new tag values.
The possible values are defined in annex D. Elements with tags that are not defined here are reserved for future use; the
tags and their associated content shall not be processed by receivers.
element_length: This field indicates the number of data bytes contained in this element, i.e. the number of bytes that
follow the length byte up to the end of the element. The range of this is 0x00 to 0xFD (i.e. 0 to 253). If this value is
either 0xFE or 0xFF then the additional extended_element_length field defines the element length.
extended_element_length: When used, this field indicates the number of data bytes contained in this element, i.e. the
number of bytes that follow the last extended length byte up to the end of the element.
element_data_byte: These bytes contain the element's attributes, CDATA (i.e. string data) and child elements. They
shall be encoded in the following order:
1) Attributes.
2) Child elements.
3) CDATA content.
ETSI
10 ETSI TS 102 371 V1.3.1 (2008-07)
4.3.1 Top-level elements
There are two top-level elements defined in the present document; epg and serviceInformation. A top-level element
shall be carried within a binary object (see clause 4.2) and it shall be the only element (apart from its nested children) in
that object. The possible values of the element_tag for top-level elements are defined in table 4. Top-level elements
with tags that are not defined here are reserved for future use; these tags and their associated content shall not be
processed by receivers.
Table 4: Top-level element tags
Element Tag
epg 0x02
serviceInformation 0x03
As well as the appropriate elements defined by the EPG XML specification the top-level elements may also, optionally,
contain a string token table (see clause 4.9), a default contentID (see clause 4.10) and a default language
(see clause 4.11). If present, these elements shall be the first elements to occur in the top-level element after the
attributes.
A top-level element is encoded in the same way as a normal element (see clause 4.3) with the exception that the
element_data_bytes shall be encoded in the following order:
1) Attributes.
2) String token table (if present).
3) Default contentID (if present).
4) Default language (if present).
5) Child elements.
6) CDATA content.
4.4 Attributes
All attributes use basically the same encoding, as defined here.
Table 5: Structure of an attribute
Syntax Size Type
attribute() {
attribute_tag
8 bits uimsbf
attribute_length
8 bits uimsbf
if (attribute_length == 0xFE) {

extended_attribute_length
16 bits uimsbf
}
if (attribute_length == 0xFF) {

extended_attribute_length
24 bits uimsbf
}
for (i=0; i
extended_attribute_length; i++) {
attribute_data_byte
8 bits uimsbf
}
}
attribute_tag: This byte uniquely identifies the attribute within the parent element. The possible values are defined in
annex E.
Attributes with tags that are not defined here are reserved for future use and should not be processed by receivers.
ETSI
11 ETSI TS 102 371 V1.3.1 (2008-07)
attribute_length: This field indicates the number of data bytes contained in this attribute, i.e. the number of bytes that
follow the length byte up to the end of the attribute. The range of this is 0x00 to 0xFD (i.e. 0 to 253). If this value is
either 0xFE or 0xFF then the additional extended_attribute_length field defines the attribute length.
extended_attribute_length: When used, this field indicates the number of data bytes contained in this attribute, i.e. the
number of bytes that follow the last extended length byte up to the end of the attribute.
attribute_data_byte: These bytes contain either a string (clause 4.5.1) or an enumerated data value (see clause 4.6) or a
common data type (clause 4.7).
NOTE: Any entity references should be expanded.
4.4.1 Default attributes
Where an attribute has a default value there is no need for it to be present in the binary encoding as the receiver shall
always automatically use the default value.
4.5 CDATA and strings
All CDATA or text strings apart from textual attributes shall be encoded as detailed in table 6.
Table 6: Structure of a CDATA element
Syntax Size Type
cdata() {
cdata_tag
8 bits uimsbf
cdata_length
8 bits uimsbf
If (cdata_length == 0xFE) {
extended_cdata_length
16 bits uimsbf
}
If (cdata_length == 0xFF) {
extended_cdata_length
24 bits uimsbf
}
for (i=0; i
cdata_data_byte
8 bits uimsbf
}
}
cdata_tag: This shall always be 0x01.
cdata_length: This field indicates the number of data bytes contained in this string. The range of this is 0x00 to 0xFD
(i.e. 0 to 253). If this value is either 0xFE or 0xFF then the additional extended_cdata_length field defines the attribute
length.
extended_cdata_length: When used, this field indicates the number of data bytes contained in this string.
cdata_data_byte: These bytes contain the characters for this CDATA element.
NOTE 1: Attributes with text values are encoded as an attribute (see clause 4.4) with the attribute_data_bytes being
the character data bytes only.
NOTE 2: Any entity references should be expanded.
4.5.1 Character sets
All CDATA and other strings shall use ISO/IEC 10646 [4] with UTF-8 encoding. The ISO/IEC 10646 [4] characters
0xE000 to 0xF8FF shall not be included within any binary encoded strings.
ETSI
12 ETSI TS 102 371 V1.3.1 (2008-07)
4.6 Enumerated data values
Those attributes that are enumerated types are encoded by a single byte; the value of this byte is specific to that
particular attribute and is defined in table F.1.
4.7 Common data types
Various common data types within the EPG specification (TS 102 818 [1]) have been identified and the specific
encodings to be used are defined in clause 4.7.
4.7.1 Date and time
All elements defined as timePointType are encoded as follows:

1 bit 17 bits 1 bit 1 bit 1 bit 11 or 27 bits 8 bits
Rfa Date Rfa UTC LTO
LTO UTC
flag flag
5 bits 6 bits 6 bits 10 bits 2 bits 1 bits 5 bits
Long form
Hours Minutes Seconds Rfa Rfa Sign Half-hours
(UTC flag = 1)
5 bits 6 bits
Short form
Hours Minutes
(UTC flag = 0)
Figure 2: Date and time encoding (LTO flag == 1)

1 bit 17 bits 1 bit 1 bit 1 bit 11 or 27 bits
Rfa Date Rfa LTO UTC UTC
flag flag
Figure 3: Date and time encoding (LTO flag == 0)
Rfa: This 1-bit field shall be reserved for future additions. The bit shall be set to zero for the currently specified
definition of this field. Receivers shall ignore this bit.
Date: This 17-bit unsigned binary number shall define the current date according to the Modified Julian Date (MJD)
coding strategy (EN 300 401 [3]). This number increments daily at 00:00 UTC and extends over the range 0 to 99 999.
th
As an example MJD 50 000 corresponds to October 10 , 1995.
Rfa: This 1-bit field shall be reserved for future additions. The bit shall be set to zero for the currently specified
definition of this field. Receivers shall ignore this bit.
LTO flag: This 1-bit field indicates whether the LTO field (see below) is present or not, as follows:
• 0: LTO not present, local time is UTC (LTO = 0).
• 1: LTO present, local time is UTC plus LTO.
ETSI
13 ETSI TS 102 371 V1.3.1 (2008-07)
UTC flag: This 1-bit field indicates whether the UTC (see below) takes the short form or the long form, as follows:
• 0: UTC short form.
• 1: UTC long form.
UTC (Co-ordinated Universal Time): Two forms are available depending upon the state of the UTC flag. They are
defined as follows:
• Short form: This 11-bit field contains two sub-fields, coded as unsigned binary numbers. The first sub-field is
a 5-bit field which shall define the hours and the other sub-field is a 6-bit field which shall define the minutes.
• Long form: In addition to the hours and minutes fields defined in the short form, this 27-bit field shall contain
one further sub-field which shall be encoded as an unsigned binary number. This is a 6-bit field which shall
define the seconds. The following 10-bits shall be reserved for future additions. These bits shall be set to zero
for the currently specified definition of this field.
LTO (Local Time Offset): This 8-bit field shall give the Local Time Offset (LTO) for the time given. It is only present
if the LTO flag is set to 1. The first two bits are reserved for future additions, they shall be set to zero for the currently
specified definition and shall be ignored by receivers. The next bit shall give the sense of the LTO, as follows:
• 0: Positive offset.
• 1: Negative offset.
The final 5 bits define the offset in multiples of half-hours in the range 0 to 14 hours.
For example, a programme broadcast at 05:00 in the UK during Daylight Savings time would have a UTC of 04:00 and
an LTO of +1 hour.
4.7.2 Duration
All attributes defined as durationType are encoded as a 16-bit unsigned integer, representing the duration in seconds
from 0 to 65 535 (just over 18 hours).
4.7.3 CRIDs
All attributes defined as CRIDType are encoded as a string attribute (see clause 4.4).
4.7.4 Short CRIDs
All attributes defined as shortCRIDType are encoded as a 24-bit unsigned integer.
4.7.5 Genres
All elements that are defined as genreType shall be encoded as follows. Only the href attribute is encoded (the CS and
the levels) together with the (optional) type attribute. The name and definition elements are not encoded.
Genre href
The href attribute of the genre element shall be encoded as follows:

4 bits 4 bits 0 or 8 bits 0 or 8 bits 0 or 8 bits
Rfu CS Level 1 Level 2 Level 3

Figure 4: Genre href encoding
Rfu: This 4-bit field shall be reserved for future use of the remainder of the structure. The four bits shall be set to zero
for the currently specified definition of this field.
ETSI
14 ETSI TS 102 371 V1.3.1 (2008-07)
CS field: This 4-bit field shall indicate which classification scheme (CS, e.g. the 1 of "1.2.3.4") this genre is a member
of, as follows:
• 0: Undefined. Genres with this CS shall be ignored.
• 1: Intention CS.
• 2: Format CS.
• 3: Content CS.
• 4: Intended audience CS.
• 5: Origination CS.
• 6: Content alert CS.
• 7: Media type CS.
• 8: Atmosphere CS.
• 9 to 15: Undefined. Genres with this CS shall be ignored.
Level 1 field: This 8-bit field shall indicate the genre value for the first (i.e. highest) level after the CS (e.g. the 2 of
"1.2.3.4"). If this value is not present then this and subsequent genre bytes should not be present.
Level 2 field: This 8-bit field shall indicate the genre value for the second level after the CS (e.g. the 3 of "1.2.3.4"). If
this value is not present then this and subsequent genre bytes should not be present.
Level 3 field: This 8-bit field shall indicate the genre value for the third level after the CS (e.g. the 4 of "1.2.3.4"). If
this value is not present then this and subsequent genre bytes should not be present.
Genre type: The type attribute of the genre element shall be encoded as an enumerated attribute as described in
clause 4.6.
4.7.6 contentID
4.7.6.1 DAB EPG
All elements defined as contentIDType are encoded as follows:

1 bit 1 bit 1 bit 1 bit 4 bits 0 or 8 bits 0 or 16 bits 16 or 32 bits 0 or 8 bits
Rfa Ens X-PAD SId SCIdS ECC EId SId X-PAD
flag flag flag extension
3 bits 5 bits
Rfu X-PAD
App type
Figure 5: contentID encoding for DAB

1 bit 1 bit 1 bit 1 bit 4 bits 8 bits 16 bits 16 or 32 bits
Rfa 1 0 SId SCIdS ECC EId SId
flag
Figure 6: Example contentID encoding (Ens flag == 1 and X-PAD flag == 0)
ETSI
15 ETSI TS 102 371 V1.3.1 (2008-07)

1 bit 1 bit 1 bit 1 bit 4 bits 16 or 32 bits
Rfa 0 0 SId SCIdS SId
flag
Figure 7: Example contentID encoding (Ens flag == 0 and X-PAD flag == 0)
Rfa: This 1-bit field shall be reserved for future additions. This bit shall be set to zero for the currently specified
definition of this field. Receivers shall ignore this bit.
Ens flag: This 1-bit flag shall indicate whether the ECC and EId are contained within the contentID, as follows:
• 0: ECC and EId are not present. The service that is referenced within the contentID is transmitted on the
same ensemble as this EPG service.
• 1: ECC and EId are present.
X-PAD flag: This 1-bit flag shall indicate whether the addressed component is carried in an X-PAD channel, as
follows:
• 0: Is not carried in an X-PAD channel; X-PAD extension is not present.
• 1: Is carried in an X-PAD channel; X-PAD extension is present.
SId flag: This 1-bit flag shall indicate how the SId field is encoded, as follows:
• 0: SId is encoded as a 16-bit service identifier (i.e. audio service).
• 1: SId is encoded as a 32-bit service identifier (i.e. data service).
SCIdS: This 4-bit field defines the Service Component Id within the Service (SCIdS).
ECC: This optional 8-bit field defines the Extended Country Code (ECC) of the ensemble on which the service is
broadcast and is only present if the Ens flag is set to 1.
EId: This optional 16-bit field defines the Ensemble Id (EId) of the ensemble on which the service is broadcast and is
only present if the Ens flag is set to 1.
SId: This 16-bit or 32-bit field (indicated by the SId flag) defines the service identifier.
X-PAD extension: This optional data field is only present if the X-PAD flag is set to 1.
Rfu: This 3-bit field
...