ETSI TS 101 860 V1.2.1 (2017-08)

Digital Audio Broadcasting (DAB); Distribution Interfaces; Service Transport Interface (STI); STI levels

RTS/JTC-DAB-89

General Information

• Status: Published
• Publication Date: 22-Aug-2017
• Technical Committee: BROADCAS - EBU/CENELEC/ETSI on Broadcasting
• Current Stage: 12 - Completion
• Due Date: 24-Aug-2017
• Completion Date: 23-Aug-2017

Standards Content (Sample)

ETSI TS 101 860 V1.2.1 (2017-08)






TECHNICAL SPECIFICATION
Digital Audio Broadcasting (DAB);
Distribution Interfaces;
Service Transport Interface (STI);
STI levels

---------------------- Page: 1 ----------------------
2 ETSI TS 101 860 V1.2.1 (2017-08)



Reference
RTS/JTC-DAB-89
Keywords
audio, broadcasting, DAB, data, digital, interface,
network, service, transport
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
The present document can be downloaded from:
http://www.etsi.org/standards-search
The present document may be made available in electronic versions and/or in print. The content of any electronic and/or
print versions of the present document shall not be modified without the prior written authorization of ETSI. In case of any
existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the
print of the Portable Document Format (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
https://portal.etsi.org/TB/ETSIDeliverableStatus.aspx
If you find errors in the present document, please send your comment to one of the following services:
https://portal.etsi.org/People/CommiteeSupportStaff.aspx
Copyright Notification
No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying
and microfilm except as authorized by written permission of ETSI.
The content of the PDF version shall not be modified without the written authorization of ETSI.
The copyright and the foregoing restriction extend to reproduction in all media.

© ETSI 2017.
© European Broadcasting Union 2017.
All rights reserved.

TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are trademarks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are trademarks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
oneM2M logo is protected for the benefit of its Members.
GSM® and the GSM logo are trademarks registered and owned by the GSM Association.
ETSI

---------------------- Page: 2 ----------------------
3 ETSI TS 101 860 V1.2.1 (2017-08)
Contents
Intellectual Property Rights . 5
Foreword . 5
Modal verbs terminology . 5
Introduction . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 7
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 STI Levels . 8
4.0 Introduction . 8
4.1 STI-D(LI) Stream Types . 8
4.1.0 General . 8
4.1.1 Basic Stream Types . 8
4.1.1.0 Definition . 8
4.1.1.1 MSC sub-channel streams . 9
4.1.1.2 FIC FIG stream . 9
4.1.2 Optional Stream Types . 9
4.2 STI Level 1 . 9
4.2.0 General . 9
4.2.1 STI-D(LI) requirements . 9
4.2.2 STI-C(LI) requirements . 9
4.3 STI Level 2 . 10
4.3.0 General . 10
4.3.1 STI-D(LI) requirements . 10
4.3.2 STI-C(LI) requirements . 10
4.4 STI Level 3 . 10
4.4.0 General . 10
4.4.1 STI-D(LI) requirements . 10
4.4.2 STI-C(LI) requirements . 11
4.5 Connecting entities of different STI Levels . 11
Annex A (informative): Implications of STI level definitions on device functionality . 12
A.1 Introduction . 12
A.2 Minimum STI device functionality . 13
A.2.1 Ensemble Provider (EP) . 13
A.2.1.0 General . 13
A.2.1.1 STI Level 1 . 13
A.2.1.2 STI Level 2 . 13
A.2.1.3 STI Level 3 . 14
A.2.2 Service Provider (SP) . 15
A.2.2.0 General . 15
A.2.2.1 Service Provider (upstream entity) . 15
A.2.2.1.1 STI Level 1. 15
A.2.2.1.2 STI Level 2. 15
A.2.2.1.3 STI Level 3. 16
A.2.2.2 Service Provider (downstream and upstream entity) . 16
A.2.2.2.0 General . 16
A.2.2.2.1 STI Level 1 (downstream entity) . 16
A.2.2.2.2 STI Level 2 (downstream entity) . 16
A.2.2.2.3 STI Level 3 (downstream entity) . 17
ETSI

---------------------- Page: 3 ----------------------
4 ETSI TS 101 860 V1.2.1 (2017-08)
Annex B (informative): Examples of DAB collection networks . 18
B.1 Introduction . 18
B.2 Examples . 18
B.2.1 Example 1 . 18
B.2.2 Example 2 . 19
B.2.3 Example 3 . 19
B.2.4 Example 4 . 20
B.2.5 Example 5 . 21
Annex C (normative): Using TCP/IP as Transport Mechanism for STI-C(LI) messages . 22
C.1 Introduction . 22
C.2 Motivation and Background . 22
C.3 Specification . 23
Annex D (informative): Bibliography . 24
History . 25

ETSI

---------------------- Page: 4 ----------------------
5 ETSI TS 101 860 V1.2.1 (2017-08)
Intellectual Property Rights
Essential patents
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 (https://ipr.etsi.org/).
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.
Trademarks
The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners.
ETSI claims no ownership of these except for any which are indicated as being the property of ETSI, and conveys no
right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does
not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks.
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, ETSI EN 300 401 [1], for DAB (see note 2) which now has worldwide acceptance.
NOTE 2: DAB is a registered trademark owned by one of the Eureka Project 147 partners.
The DAB family of standards is supported by World DAB, an organization with members drawn from broadcasting
organizations and telecommunication providers together with companies from the professional and consumer
electronics industry.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "need not", "will", "will not", "can" and
"cannot" are to be interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of
provisions).
"must" and "must not" are NOT allowed in ETSI deliverables except when used in direct citation.
ETSI

---------------------- Page: 5 ----------------------
6 ETSI TS 101 860 V1.2.1 (2017-08)
Introduction
The present document is one of a set associated with DAB. ETSI EN 300 401 [1] describing the transmitted signal, the
interface between the broadcaster's transmitters and the listener's receiver. The associated documents, ETSI
EN 300 797 [2], ETSI EN 300 798 [3] and ETSI ETS 300 799 [4] describe additional interfaces, which can be used by
broadcasters or network providers to build DAB collection and distribution networks. In particular the document ETSI
EN 300 797 [2] establishes a standard way for transporting Service Components, Service Information and control
messages between two entities in a DAB collection network. Because of the openness and flexibility of the Service
Transport Interface (STI) standard there is uncertainty regarding the implementation of it. This applies to
interoperability between devices from different suppliers. Practical broadcast scenarios do not always require to
implement the full standard, which creates the problem that different suppliers might implement different subsets of
ETSI EN 300 797 [2].
To overcome this problem and to fully exploit the great potential of the DAB system, the subject of the present
document is to describe implementation levels of the STI standard and to outline their usage.

ETSI

---------------------- Page: 6 ----------------------
7 ETSI TS 101 860 V1.2.1 (2017-08)
1 Scope
The present document establishes guidance in implementation and usage of the functionality described in the STI
standard ETSI EN 300 797 [2]. Subsets of the STI standard, called STI Levels, are defined in order to make
interoperable solutions possible for different suppliers of STI devices. The present document defines the minimum
functionality an upstream or downstream entity provides on each level to be considered compliant with that level.
This version of the present document is aligned with V2.1.1 of ETSI EN 300 401 [1].
2 References
2.1 Normative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
https://docbox.etsi.org/Reference/.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are necessary for the application of the present document.
[1] ETSI EN 300 401 (V2.1.1): "Radio broadcasting systems; Digital Audio Broadcasting (DAB) to
mobile, portable and fixed receivers".
[2] ETSI EN 300 797: "Digital Audio Broadcasting (DAB); Distribution interfaces; Service Transport
Interface (STI)".
[3] ETSI EN 300 798 (V1.1.1): "Digital Audio Broadcasting (DAB); Distribution interfaces; Digital
baseband In-phase and Quadrature (DIQ) interface".
[4] ETSI ETS 300 799 (1997): "Digital Audio Broadcasting (DAB); Distribution interfaces; Ensemble
Transport Interface (ETI)".
[5] Recommendation ITU-T G.704: "Synchronous frame structures used at 1544, 6312, 2048, 8448
and 44 736 kbit/s hierarchical levels".
[6] Recommendation ITU-T G.703: "Physical/electrical characteristics of hierarchical digital
interfaces".
2.2 Informative references
References are either specific (identified by date of publication and/or edition number or version number) or
non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the
referenced document (including any amendments) applies.
NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee
their long term validity.
The following referenced documents are not necessary for the application of the present document but they assist the
user with regard to a particular subject area.
[i.1] IETF RFC 1700 (October 1994): "Assigned Numbers", STD 2, Reynolds, J. and J. Postel.
ETSI

---------------------- Page: 7 ----------------------
8 ETSI TS 101 860 V1.2.1 (2017-08)
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the terms and definitions given in ETSI EN 300 401 [1], ETSI
EN 300 797 [2] and the following apply:
STI Level: subset of overall STI functionality described by ETSI EN 300 797 [2]
3.2 Abbreviations
For the purposes of the present document, the abbreviations given in ETSI EN 300 401 [1], ETSI EN 300 797 [2] and
the following apply:
API Application Programming Interface
DNS Dynamic Name Server
EP Ensemble Provider
IANA Internet Assigned Numbers Association
IP Internet Protocol
ISDN Integrated Services Digital Network
SP Service Provider
TCP Transport Control Protocol
VPN Virtual Private Network
4 STI Levels
4.0 Introduction
The STI Levels describe the STI functionality, i.e. STI-D stream types and STI-C message sets and their usage, that STI
entities shall provide to be considered STI level compliant. The levels shall be subsets of ETSI EN 300 797 [2] with
respect to STI-D(LI) and STI-C(LI) functionality.
A total of three levels is defined. The level requiring the least functionality is called level 1. Higher levels shall fully
comprise the lower ones. The levelling proposed in the present document is only valid for the logical part of ETSI
EN 300 797 [2] and does not apply to physical interfaces. Thus an STI capable device may be equipped with one or
more physical interfaces, each being capable of providing one of the STI Levels as defined in the present document.
4.1 STI-D(LI) Stream Types
4.1.0 General
The STI-D(LI) data stream types classified in ETSI EN 300 797 [2], clause 4.2, are divided into two parts, basic stream
types and optional stream types.
4.1.1 Basic Stream Types
4.1.1.0 Definition
Basic stream types are:
• MSC sub-channel audio stream service component;
• MSC sub-channel data stream service component;
ETSI

---------------------- Page: 8 ----------------------
9 ETSI TS 101 860 V1.2.1 (2017-08)
• MSC sub-channel data stream made of one or more packet mode service components (and padding);
• FIC FIG stream Service Information.
Table 1 shows which TID and TIDext shall be supported.
Table 1: TID/TIDext supported as basic stream types
TID TIDext Significance
0 0 MSC audio stream
1 MSC data stream
2 MSC packet mode stream
4 0 Service Information

4.1.1.1 MSC sub-channel streams
The basic stream types shall provide correct handling of individual MSC streams as described in ETSI EN 300 797 [2],
clause 5.9.1.
4.1.1.2 FIC FIG stream
The basic stream types shall provide correct handling of FIC FIG streams carried in STI-D(LI) as described in ETSI
EN 300 797 [2], clause 5.9.3.
4.1.2 Optional Stream Types
Other stream types than those defined as basic are optional on all STI Levels:
• MSC sub-channel contribution packet mode data service component;
• FIC FIG stream CA information;
• FIC FIB stream asynchronous FIB insertion;
• FIC FIB stream synchronous FIB insertion.
4.2 STI Level 1
4.2.0 General
This clause defines the minimum functionality required by an STI upstream or downstream entity to be considered
conformant to STI Level 1. Only STI-D(LI) basic stream types are supported. Control message exchange between
upstream and downstream entities is not included. Therefore no support of STI-C(LI) messages is required. Usage of
this level shall assume a configuration agreement between the upstream and downstream entities.
4.2.1 STI-D(LI) requirements
All basic stream types as defined in clause 4.1.1 shall be supported in downstream entities. At least one basic stream
type shall be supported in upstream entities.
4.2.2 STI-C(LI) requirements
In STI Level 1 no setup and control messages can be exchanged between an upstream and downstream entity. Therefore
no support of STI-C(LI) shall be required.
ETSI

---------------------- Page: 9 ----------------------
10 ETSI TS 101 860 V1.2.1 (2017-08)
4.3 STI Level 2
4.3.0 General
This clause defines the minimum functionality required by an STI upstream or downstream entity to be considered
conformant to STI Level 2. The minimum functionality required in level 1 shall be comprised on this level. On STI
Level 2 the possibility to exchange certain STI-C(LI) messages between upstream and downstream entities shall be
supported. Extending the functionality provided on STI Level 1, STI Level 2 supports seamless and coordinated
dynamic reconfiguration as well as the usage of FIG files.
4.3.1 STI-D(LI) requirements
The STI-D(LI) requirements of STI Level 1 shall be comprised, i.e. all basic stream types as defined in clause 4.1.1
shall be supported in downstream entities. At least one basic stream type shall be supported in upstream entities.
4.3.2 STI-C(LI) requirements
In STI Level 2 exchange of control messages shall be supported. The required functionality comprises seamless
dynamic reconfiguration of the DAB multiplex initiated by the upstream entity, the possibility to define new
configurations, exchange of error messages and frame counter information. FIG files in addition to FIG streams may be
used to provide FIC content. Therefore the following message classes, as defined in ETSI EN 300 797 [2], shall be
supported:
• Action messages, i.e. message class ACTION;
• Configuration messages, i.e. message class CONFIG;
• FIG file messages, i.e. message class FIGFILE;
• Information messages, i.e. message class INFORMATION;
• Supervision messages, i.e. message class SUPERVISION.
NOTE: Only the reconfiguration initiation by the upstream entity is mandatory. The possibility of reconfiguration
enforcement on upstream entities from the downstream entity is optional. This means that not all the
functionality of message class ACTION is required (see also annex A).
4.4 STI Level 3
4.4.0 General
This clause defines the minimum functionality required by an STI upstream or downstream entity to be considered
conformant to STI Level 3. The minimum functionality required on the lower levels shall be comprised on this level.
Extending the functionality provided on STI Level 2, STI Level 3 supports the possibility to exchange STI-C(LI)
messages of the RESOURCE class between upstream and downstream entities.
4.4.1 STI-D(LI) requirements
The STI-D(LI) requirements of STI Levels 1 and 2 shall be comprised, i.e. all basic stream types as defined in
clause 4.1.1 shall be supported in downstream entities. At least one basic stream type shall be supported in upstream
entities.
ETSI

---------------------- Page: 10 ----------------------
11 ETSI TS 101 860 V1.2.1 (2017-08)
4.4.2 STI-C(LI) requirements
In STI Level 3 exchange of control messages shall be supported. The STI-C(LI) requirements of STI Levels 1 and 2
shall be comprised. STI Level 3 shall also handle scarce DAB resources. Therefore the following message class, as
defined in ETSI EN 300 797 [2], shall be supported:
• Resource messages, i.e. message class RESOURCE.
NOTE: MSC sub-channel packet mode data contribution is an option. Therefore the PACKCON message does
not need to be supported.
4.5 Connecting entities of different STI Levels
The present document describes three levels of functionality when using ETSI EN 300 797 [2]. Because of the
hierarchical definition of levels, lower levels have limitations that shall be considered when connecting entities of
different STI Levels. These limitations are listed in table 2.
Table 2: Functional limitations of the STI Levels
STI Level Limitation
1 • co-ordination of dynamic reconfiguration is not supported
• only asynchronous SI insertion is possible
2 • DAB ensemble resource co-ordination based on RESOURCE
messages is not supported
3 • reconfiguration enforcement on an upstream entity by a
downstream entity is not supported
• FIC FIB streams are not supported
• FIC FIG stream CA are not supported
• FIB grids are not supported
• MSC packet mode data contribution is not supported
• handling of CA FIGs
NOTE: Limitations listed on a higher level also apply to lower levels.

When using STI Level 1 or 2 on an STI connection, the upstream and downstream entity shall agree on the following
items to be able to use the full functionality of these STI Levels:
• transmission channel capacity that the upstream entity can use;
• streams that the upstream entity is entitled to use;
• identifiers that the upstream entity is entitled to use;
• FIGs that the upstream entity is entitled to use;
• announcement parameters that the upstream entity is entitled to use.
ETSI

---------------------- Page: 11 ----------------------
12 ETSI TS 101 860 V1.2.1 (2017-08)
Annex A (informative):
Implications of STI level definitions on device f
...