ETSI TS 103 177 V1.1.1 (2013-08)

ETSI TS 103 177 V1.1.1 (2013-08)
Technical Specification
Digital Audio Broadcasting (DAB);
Filecasting;
User application specification
European Broadcasting Union Union Européenne de Radio-Télévision
EBU·UER
---------------------- Page: 1 ----------------------
2 ETSI TS 103 177 V1.1.1 (2013-08)
Reference
DTS/JTC-DAB-67
Keywords
audio, broadcasting, coding, DAB, digital
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - 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
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

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

If you find errors in the present document, please send your comment to one of the following services:

DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.

3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and

GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

Intellectual Property Rights ................................................................................................................................ 5

Foreword ............................................................................................................................................................. 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 Introduction .............................................................................................................................................. 8

5 Filecast channel ........................................................................................................................................ 9

5.1 Transport mechanism ......................................................................................................................................... 9

5.2 Filecast MOT carousel ....................................................................................................................................... 9

5.2.1 MOT header core ........................................................................................................................................ 10

5.2.2 ContentName .............................................................................................................................................. 10

5.2.3 CompressionType ....................................................................................................................................... 10

5.2.4 CAInfo ........................................................................................................................................................ 11

5.2.5 AvailabilityStart .......................................................................................................................................... 11

5.2.6 PresentationPriority .................................................................................................................................... 11

5.2.7 MemberOf................................................................................................................................................... 11

5.2.8 ClickThroughURL ...................................................................................................................................... 11

5.2.9 AlternativeLocationURL ............................................................................................................................ 11

5.2.10 Location ...................................................................................................................................................... 12

5.2.11 ContentDescription ..................................................................................................................................... 12

5.2.12 ContentCategory ......................................................................................................................................... 12

5.2.13 ParentService .............................................................................................................................................. 12

5.2.14 MOT caching parameters ............................................................................................................................ 12

5.3 Recommended signalling for updated and dynamic content ............................................................................ 12

5.4 Rebroadcasting media files............................................................................................................................... 13

5.5 Supported content types ................................................................................................................................... 13

5.5.1 Audio .......................................................................................................................................................... 13

5.5.2 Text ............................................................................................................................................................. 13

5.5.3 Video .......................................................................................................................................................... 13

6 Signalling ............................................................................................................................................... 13

6.1 Application type, FIG0/13 ................................................................................................................................ 13

6.2 Secondary component signalling ...................................................................................................................... 13

6.3 Time and date, FIG0/9 and FIG 0/10 ............................................................................................................... 14

7 Receiver functionality ............................................................................................................................ 14

7.1 General functionality ........................................................................................................................................ 14

7.2 Presentation of the content to the user .............................................................................................................. 14

7.3 Downloading content ....................................................................................................................................... 15

7.4 File management .............................................................................................................................................. 15

7.5 URL Handling .................................................................................................................................................. 16

7.5.1 AlternativeLocationURL ............................................................................................................................ 16

7.5.2 ClickThroughURL ...................................................................................................................................... 17

Annex A (informative): Filecast example services and experiences ................................................... 18

A.1 Scheduling downloads of specific content ............................................................................................. 18

A.2 Scheduling downloads of content categories ......................................................................................... 18

A.3 Download conflicts................................................................................................................................. 18

A.4 Part-downloaded ..................................................................................................................................... 18

A.5 DAB WiFi radio ..................................................................................................................................... 18

A.6 Frequently updated content .................................................................................................................... 19

A.7 Download whilst listening to live radio ................................................................................................. 19

A.8 Accompanying live radio ....................................................................................................................... 19

A.9 Location based services .......................................................................................................................... 19

History .............................................................................................................................................................. 20

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

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

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

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

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 [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 DMB, an organization with members drawn from broadcasting

organizations and telecommunication providers together with companies from the professional and consumer

The present document specifies the Filecasting user application which permits the non-linear delivery of multimedia

content using DAB. Whilst the main focus of the present document is the delivery of audio files over a broadcast

network, it is also applicable to other media formats too, such as video files and documents which may contain a

Filecasting can be used by broadcasters with existing DAB linear audio services to deliver additional content associated

(but not necessarily directly linked) with these audio services. Equally it can be used to create standalone Filecast

services. This content could be an entire programme (podcast), additional short-form content relating to a linear radio

Whilst Filecasting is defined as a DAB user application, it can equally be carried over Digital Radio Mondiale (DRM),

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 documents which are not found to be publicly available in the expected location might be found at

NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee

The following referenced documents are necessary for the application of the present document.

[1] ETSI EN 300 401: "Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile,

[2] ETSI EN 301 234: "Digital Audio Broadcasting (DAB); Multimedia Object Transfer (MOT)

[4] ETSI TS 101 499: "Digital Audio Broadcasting (DAB); MOT SlideShow; User application

[5] ETSI TS 102 371: "Digital Audio Broadcasting (DAB); Digital Radio Mondiale (DRM);

Transportation and Binary Encoding Specification for Electronic Programme Guide (EPG)".

[6] ISO EN 62106: "Specification of the radio data system (RDS) for VHF/FM sound broadcasting in

[7] ISO/IEC 10646: "Information technology -- Universal Coded Character Set (UCS)".

[8] ISO 3166-2: "Codes for the representation of names of countries and their subdivisions -- Part 2:

[10] draft-daviel-http-geo-header-01: "Geographic extensions for HTTP transactions".

The following referenced documents are not necessary for the application of the present document but they assist the

[i.2] ETSI TS 102 818: "Digital Audio Broadcasting (DAB); Digital Radio Mondiale (DRM); XML

For the purposes of the present document, the terms and definitions given in EN 300 401 [1] and the following apply:

dynamic broadcast information: Broadcast information relating to the media files and basic presentational

information for receivers that do not support the ability to decode the EPG channel

dynamic content: media file that contains content that is frequently updated (e.g. "Latest News")

NOTE: There will typically be several versions of this media file broadcast, and so it is not always essential that a

EPG channel: DAB data stream containing service and schedule information that relates to audio services, Filecast

filecast channel: DAB data stream containing the Dynamic Broadcast Information and media files

filecast service: collection of media files that are all contained within a particular service-brand, whether linked to a

linear audio channel (e.g. the "BBC Radio 1 On Demand" Filecast Service contains content related to BBC Radio 1), or

scheduled content: media file that contains a single programme, and is scheduled to be broadcast at some point in the

For the purposes of the present document, the abbreviations given in EN 300 401 [1] and the following apply:

2) Dynamic broadcast information: This provides signalling information that aids a receiver in downloading

When broadcast on a DAB multiplex, the media files and dynamic broadcast information are transported within the

same data stream, called the "Filecast channel". Additionally more detailed schedule and presentational information

may be transported within an EPG channel, using the DAB EPG standard [i.2]. However the specification of this

enhanced schedule and presentational information is out of the scope of the present document. Figure 1 shows an

example multiplex configuration, where the DAB Multiplex contains multiple audio services, a Filecast service

transported within PAD, a Filecast Service within a packet mode data sub-channel and an additional EPG Service.

1) Basic Filecast Receiver: This receiver is only able to decode the Filecast channel. It uses the basic

information within the Dynamic Broadcast Information object to allow a user to select content which they

wish to store. It cannot decode the additional information contained within the EPG channel. Consequently it

will only be able to present limited information about the individual media files.

2) Full Filecast Receiver: This receiver can also decode the additional information contained within the EPG

The Filecasting specification allows for two different configurations of Filecasting-related channels on a single

Where a Filecast channel contains content that is linked to an existing audio service on the multiplex, and is not

transported in that audio channel's PAD capacity, the Filecast channel is signalled as a secondary component of the

NOTE 2: It is possible for a single multiplex to contain multiple Filecast channels.

The Filecast channel may be transported in either a packet mode sub-channel with FEC applied or in the PAD of an

MOT in Directory Mode [2] shall be used to transport the Filecast channels. The MOT Directory within the Filecast

For any carousels containing Filecasting objects, the data rate for MOT transported in packet mode is limited to a

maximum of 256 kbps. For packet mode transport, the overall size of the subchannel including the Filecast channel is

When using PAD for filecast object delivery it is important for service providers to be able to continue to deliver

SlideShow and Dynamic Label in a timely manner. If the Filecast channel is transported in PAD a mixture of file

objects in Directory Mode and other Header mode objects shall be able to be received. Ideally the PAD server will

The service provider should choose a segmentation size for the filecast objects which allow appropriate time granularity

dependant on the capacity of the PAD channel to ensure timely delivery of other PAD objects.

The media files are broadcast as MOT objects within the Filecast channel. They are referenced from the MOT

Directory. The MOT Directory is also used as a means of transporting the Dynamic Broadcast Information that is

The scope of the MOT Directory is set by the service provider, but it is recommended that it includes all media files that

are currently being broadcast and planned to be broadcast within that MOT carousel for several days into the future.

This is due to the reason that a Basic Filecast Receiver will only be able to decode and display listings information from

the MOT Directory, and not the EPG. Providing information within the MOT Directory only on the currently

transmitted files will restrict the selection choice of media files for users of these receivers.

• The MOT Directory shall be transmitted at a minimum repetition rate of once per 60 seconds.

• Compression of the MOT Directory is permitted (as defined in the MOT specification [2]).

• As a minimum, the MOT Directory shall list the file or files currently in the MOT carousel. It may also list

files that are planned to be broadcast, for a service provider-defined period of time into the future.

• The directory entries of the MOT Directory shall be sorted in ascending order of the ContentName parameter

at the service provider side, using the SortedHeaderInformation parameter (as defined in the MOT

• The MOT Directory shall have a maximum uncompressed size of 16 kbytes (16 384 bytes).

MOT parameters that are to be applied to individual MOT objects are carried within the MOT header information of

each directory entry in the MOT Directory. A summary of the MOT parameters for individual objects that apply to the

Filecast application are given in table 1, and are specified in detail by the following clauses. The MOT parameters

detailed in the table below will be used to identify the content of the individual objects.

NOTE: Any parameters that are encountered that are not understood by a given receiver will be ignored.

ParentService 0x29 The present No (but the parameter shall be Yes (for basic Multiple

The ContentType and ContentSubType parameters shall be set according to the MOT specification [2].

This mandatory MOT parameter uniquely identifies the object within the MOT carousel The ContentName parameter is

To permit receiver interoperability, the character set for the ContentName of Filecast objects shall be ISO Latin

Alphabet No 1, see TS 101 756 [3]. The permitted characters are restricted to a subset of this character set as follows:

the lowercase Latin letters, the digits, the hyphen, the forward slash and the underscore ("a".."z", "0".."9", "-", "/", "_").

This parameter is used if conditional access on the MOT level is applied to the MOT data. The CAInfo parameter is

If this parameter is present a non CA-capable device shall discard this MOT object.

This is the date and time from which the media file is transmitted on this Filecast channel.

• If the AvailabilityStart has a value in the future then this parameter indicates that the media file (and updates to

the media file in the case of dynamic content) is not part of the current carousel. It informs the receiver when

the next broadcast of a media file will begin, to enable a receiver to tune in to the Filecast channel at the

• If the AvailabilityStart has a value in the past or is omitted then it indicates that the media file (and updates to

the media file in the case of dynamic content) is in the current carousel of media files being broadcast.

The value of the parameter field is coded using the same format at the Binary EPG date & time parameter, see

The use of this Filecast parameter for each MOT object is optional. This MOT parameter carries a presentation priority

value for this MOT object. This parameter enables the broadcaster to define the presentation ordering of multiple items.

If this parameter is specified then where multiple items are displayed they shall be listed according t