Hybrid Digital Radio (DAB, DRM, RadioDNS); SlideShow; User Application Specification

RTS/JTC-DAB-73

General Information

Status
Published
Publication Date
20-Jan-2015
Current Stage
12 - Completion
Due Date
26-Jan-2015
Completion Date
21-Jan-2015
Ref Project
Standard
ETSI TS 101 499 V3.1.1 (2015-01) - Hybrid Digital Radio (DAB, DRM, RadioDNS); SlideShow; User Application Specification
English language
43 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)


TECHNICAL SPECIFICATION
Hybrid Digital Radio (DAB, DRM, RadioDNS);
SlideShow;
User Application Specification

European Broadcasting Union Union Européenne de Radio-Télévision
EBU·UER
2 ETSI TS 101 499 V3.1.1 (2015-01)

Reference
RTS/JTC-DAB-73
Keywords
audio, broadcasting, DAB, DRM, DNS, digital,
radio
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
The present document can be downloaded from:
http://www.etsi.org
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
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 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.

© European Telecommunications Standards Institute 2015.
© European Broadcasting Union 2015.
All rights reserved.
TM TM TM
DECT , PLUGTESTS , UMTS and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members.
TM
3GPP and LTE™ are Trade Marks of ETSI registered for the benefit of its Members and
of the 3GPP Organizational Partners.
GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.
ETSI
3 ETSI TS 101 499 V3.1.1 (2015-01)
Contents
Intellectual Property Rights . 6
Foreword . 6
Modal verbs terminology . 6
1 Scope . 7
2 References . 7
2.1 Normative references . 7
2.2 Informative references . 8
3 Definitions and abbreviations . 8
3.1 Definitions . 8
3.2 Abbreviations . 8
4 Introduction . 9
5 Application behaviour . 9
5.1 Initialization . 9
5.1.1 General . 9
5.1.2 Application priority. 10
5.1.3 Fall-back behaviour . 10
5.2 Operation . 10
5.3 Common Parameters . 11
5.3.1 General . 11
5.3.2 Trigger Time . 11
5.3.3 ClickThroughURL . 12
5.3.4 Expire time. 12
5.3.5 Categorization . 12
5.3.5.1 General . 12
5.3.5.1 Category ID . 12
5.3.5.2 SlideID . 13
5.3.5.3 Category Title . 13
5.4 Termination . 13
6 Delivery of SlideShow using broadcast MOT. 13
6.1 General . 13
6.2 Parameters . 14
6.2.1 General . 14
6.2.2 ContentName . 14
6.2.3 MOT ContentTypes and ContentSubTypes . 15
6.2.4 TriggerTime . 15
6.2.5 ExpireTime . 15
6.2.6 CategoryID/SlideID . 15
6.2.7 CategoryTitle . 15
6.2.8 ClickThroughURL . 15
6.2.9 AlternativeLocationURL . 16
6.2.10 Alert . 16
6.3 Updating parameters. 16
6.4 Additional MOT Parameters . 16
7 Delivery of SlideShow over IP . 17
7.1 Application Discovery . 17
7.1.1 General . 17
7.1.2 Discovery requirements . 17
7.2 Message Bodies . 18
7.2.1 General . 18
7.2.2 TEXT message . 18
7.2.3 SHOW message . 18
ETSI
4 ETSI TS 101 499 V3.1.1 (2015-01)
7.3 Stomp transport . 18
7.3.1 General . 18
7.3.2 Subscribing to a destination . 19
7.3.3 Receiving a message . 19
7.3.3.1 General . 19
7.3.3.2 destination . 19
7.3.3.3 message-id . 20
7.3.3.4 content-length . 20
7.3.3.5 trigger-time. 20
7.3.3.6 link . 20
7.3.3.7 CategoryID . 20
7.3.3.8 SlideID . 20
7.3.3.9 CategoryTitle . 20
7.3.4 Handling errors . 20
7.4 HTTP transport . 20
7.4.1 General . 20
7.4.2 Request . 21
7.4.3 Response . 21
7.4.3.1 General . 21
7.4.3.2 RadioVIS-Message-ID . 22
7.4.3.3 RadioVIS-Destination . 22
7.4.3.4 RadioVIS-Trigger-Time . 22
7.4.3.5 RadioVIS-Link . 22
7.4.3.6 RadioVIS-CategoryID. 23
7.4.3.7 RadioVIS-SlideID . 23
7.4.3.8 RadioVIS-CategoryTitle . 23
7.4.4 Multiple Frame Response . 23
7.4.5 JSONP Response . 23
7.4.6 Implementation Requirements . 24
7.4.7 Handling Responses . 24
7.5 Topic Construction . 24
8 Implementation guidelines for Service Providers . 24
8.1 Images . 24
8.2 TriggerTime . 24
8.3 URL Handling . 25
9 Device Profiles . 25
9.1 Simple Profile . 25
9.1.1 General . 25
9.1.2 Storage and memory management . 25
9.1.3 Display . 26
9.2 Enhanced Profile . 26
9.2.1 General . 26
9.2.2 Storage and memory management . 27
9.2.3 Display . 28
9.3 Image Formats . 28
9.3.1 Image/JFIF (JPEG) . 28
9.3.2 Image/PNG . 28
9.4 URL Handling . 29
9.4.1 General . 29
9.4.2 Click-Through URL . 29
9.4.3 AlternativeLocationURL . 30
Annex A (normative): APNG 1.0 Specification - Animated Portable Network Graphics . 31
A.1 Introduction . 31
A.1.1 Terminology . 31
A.1.2 Error Handling . 31
A.2 Structure . 31
A.2.1 General . 31
A.2.2 Chunk sequence numbers . 32
ETSI
5 ETSI TS 101 499 V3.1.1 (2015-01)
A.2.3 'acTL': The Animation Control Chunk . 32
A.2.4 'fcTL': The Frame Control Chunk . 33
A.2.5 'fdAT': The Frame Data Chunk . 34
A.3 Test encoder and sample images . 35
Annex B (informative): Implementing SlideShow with time shifted audio services . 36
B.1 Introduction . 36
B.2 SlideShow in X-PAD . 36
B.3 SlideShow in Packet Mode or X-PAD . 36
B.4 Reference time and TriggerTime. 37
Annex C (informative): Use Cases . 38
C.1 AlternativeLocationURL . 38
C.1.1 General . 38
C.1.2 Faster image acquisition . 38
C.1.3 Increased image relevance . 38
C.1.4 Faster carousel rotation . 39
C.2 ClickThroughURL . 40
C.3 Categorized SlideShow . 40
Annex D (normative): Methods for synchronizing SlideShow Reference Time . 42
D.1 General . 42
D.2 Delivery of SlideShow over DAB . 42
D.3 Delivery of SlideShow over DRM . 42
D.4 Delivery of SlideShow over IP . 42
History . 43

ETSI
6 ETSI TS 101 499 V3.1.1 (2015-01)
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://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.
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: +41 22 717 21 11
Fax: +41 22 717 24 81
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 DMB, an organization with members drawn from broadcasting
organizations and telecommunication providers together with companies from the professional and consumer
electronics industry.
The RadioDNS Project was established in 2010 to standardize the combination of broadcast radio systems with
additional applications, content and meta-data delivered over fixed or mobile IP networks. The project produced a
specification using DNS to locate the broadcaster's Internet domain which is in use worldwide, and now standardized as
ETSI TS 103 270 [6]. RadioDNS operates the authoritative name servers for the radiodns.org domain, and has members
drawn from broadcasting organizations, manufacturers and service providers.
NOTE 3: "RadioDNS Hybrid Radio" and the RadioDNS Hybrid Radio logo are registered trademarks of
RadioDNS Limited, a not-for-profit company owned by its members.
Modal verbs terminology
In the present document "shall", "shall not", "should", "should not", "may", "may not", "need", "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
7 ETSI TS 101 499 V3.1.1 (2015-01)
1 Scope
The present document describes an application that provides a visual accompaniment to a radio service.
In respect to previous versions of the present document, hybrid radio provisions have been added to allow a seamless
experience for users when consuming radio services delivered by digital radio broadcasting systems (DAB, DRM) or IP
or a combination of both. The use of the present document allows content to be created once by the service provider for
delivery by both mechanisms and allows manufacturers to implement devices with many common elements.
The application can be delivered using broadcast or IP, or a combination of the two.
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
reference document (including any amendments) applies.
Referenced documents which are not found to be publicly available in the expected location might be found at
http://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: "Radio Broadcasting Systems; Digital Audio Broadcasting (DAB) to mobile,
portable and fixed receivers".
[2] ETSI TS 101 756: "Digital Audio Broadcasting (DAB); Registered Tables".
[3] ETSI EN 301 234: "Digital Audio Broadcasting (DAB); Multimedia Object Transfer (MOT)
protocol".
[4] ETSI ES 201 980: "Digital Radio Mondiale (DRM); System specification".
[5] ETSI TS 101 968: "Digital Radio Mondiale (DRM); Data applications directory".
[6] ETSI TS 103 270: "Radio DNS; Hybrid lookup for radio services".
[7] ETSI TS 102 818: "Hybrid Digital Radio (DAB, DRM, RadioDNS); XML specification for
Service and Programme Information (SPI)".
[8] ISO/IEC IS 15948: "Information technology -- Computer graphics and image processing --
Portable Network Graphics (PNG): Functional specification".
[9] ISO/IEC 10918 (all parts): "Information technology -- Digital compression and coding of
continuous-tone still images: Requirements and guidelines".
[10] ISO 8601:2004: "Data elements and interchange formats -- Information interchange --
Representation of dates and times".
[11] IETF RFC 2782: "A DNS RR for specifying the location of services (DNS SRV)".
[12] IETF RFC 4627 (2006): "The application/json Media Type for Javascript Object Notation
(JSON)".
[13] IETF RFC 4329 (2006): "Scripting Media Types".
[14] IETF RFC 2616: "Hypertext Transfer Protocol -- HTTP/1.1".
ETSI
8 ETSI TS 101 499 V3.1.1 (2015-01)
[15] IETF RFC 2818: "HTTP over TLS".
[16] IETF RFC 5246: "Transport Layer Security TLS v1.2".
[17] "Stomp Protocol Specification, Version 1.0".
NOTE: Available at http://docs.codehaus.org/display/STOMP/Protocol.
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
reference 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] ISO 3166-2:2007: "Codes for the representation of names of countries and their subdivisions --
Part 2: Country subdivision code".
[i.2] draft-daviel-http-geo-header-01.txt April 2000: "Geographic extensions for HTTP transactions".
NOTE: Available at http://geotags.com/geo/draft-daviel-http-geo-header-01.html.
[i.3] IETF RFC 5909: "Network Time Protocol Version 4: Protocol and Algorithms Specification".
3 Definitions and abbreviations
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply:
device: hardware device or software client receiving the SlideShow application
image: PNG, JPG or APNG binary data
slide: image data, along with any associated parameters
SlideShow Reference Time: time held on the device, against which application time parameters are compared
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:
APNG Animated Portable Network Graphics
DAB Digital Audio Broadcasting
DLS Dynamic Label Segment
DMB Digital Multimedia Broadcasting
DNS Domain Name Server
DRM Digital Radio Mondiale
FIG Fast Information Group
HTML Hyper Text Markup Language
HTTP Hyper Text Transfer Protocol
IP Internet Protocol
IS International Standard
ISO International Standards Organization
JFIF JPEG File Interchange Format
ETSI
9 ETSI TS 101 499 V3.1.1 (2015-01)
JPEG Joint Pictures Expert Group
JSON JavaScript Object Notation
JSONP JavaScript Object Notation with Padding
MOT Multimedia Object Transfer
MSC Main Service Channel
NTP Network Time Protocol
PAD Programme Associated Data
PNG Portable Network Graphics
PPI Pixels Per Inch
RDS Radio Data Sytsem
SDC Service Description Channel
SRV SeRVice (record)
UI User Interface
URL Universal Resource Locator
UTC Universal Time Coordinated
UTF Unicode TransForm
VGA Video Graphics Array
X-PAD eXtended Programme Associated Data
4 Introduction
SlideShow is an application for devices that enables a Service Provider to provide a sequence of images for a Service.
These may be used by the Service to visualize the audio being received, for example:
• A news programme complemented by photos from the events being reported.
• A music programme having each song accompanied by cover art of the current song.
• During an advertising break, or a promotional slot, showing images for advertising or promotional purposes.
5 Application behaviour
5.1 Initialization
5.1.1 General
The application should be automatically started when a SlideShow service is discovered for the current radio service
through any of the following means:
• for DAB, reception of a SlideShow application definition in FIG0/13 [1];
• for DRM, reception of a SlideShow application definition in SDC data entity type 5 [4];
• for IP, a specific DNS SRV record.
When the application is started, or the radio service is changed, it is recommended that a device wait for up to 1 s in
order to receive an image to show on the display. After that time, and until an image is received, the device may display
a station logo at the most appropriate size, taken from the Service and Programme Information SI document [7].
The IP transport may also provide text information, which may be the only available transport of text for some services,
whilst others may provide text via the broadcast channel (e.g. RDS Radio Text, DAB Dynamic Label, DRM text
message).
ETSI
10 ETSI TS 101 499 V3.1.1 (2015-01)
5.1.2 Application priority
The Service Provider may provide zero or more DNS SRV records, indicating that the SlideShow service can be
provided by more than one server. Each DNS SRV record has a Priority parameter, as an integer number, where a lower
value indicates a higher priority.
If a broadcast application is being signalled, it shall be assumed to have a Priority = 100.
EXAMPLE: A Service Provider advertises the SlideShow in two ways:
- A DNS SRV record with Priority = 101
- A broadcast application – assumed Priority = 100
As the broadcast application has Priority 100, the preferred method of reception is from broadcast.
IP cannot be used, unless the device is unable to receive the broadcast application.
5.1.3 Fall-back behaviour
If an error condition occurs, for instance a loss of IP connectivity or if the Service Provider indicates that a particular
stream of content is not currently being provided over IP, then receiver should use broadcast to acquire the content. .If
the IP connectivity is subsequently restored, the device should attempt a reconnection.
EXAMPLE: A DAB Service Provider advertises the SlideShow on IP.
The Device subscribes to receive TEXT information.
The Service Provider returns an error indicating that TEXT is not currently provided over IP.
The Device shall fall back to using DAB Dynamic Label for text content for the remainder of the
session.
5.2 Operation
The SlideShow user application works with one display only: it can display only one slide at a time. Two device
profiles are defined (see also clause 9):
• simple
• enhanced
Two modes of operation are defined:
• normal
• interactive
The permitted combinations of profile and modes are summarized in table 1.
Table 1: Permitted Combinations of Profiles and Modes
Profile Normal Mode Interactive Mode
Simple Yes No
Enhanced Yes Yes
In the normal mode, images are presented at the TriggerTime specified on each image without any requirement for
user interaction.
In the interactive mode, the device presents an overview of categories with titles received so far and allows the user to
choose one category out of this list. Choosing a category allows the user to view all the slides received under this
category.
ETSI
11 ETSI TS 101 499 V3.1.1 (2015-01)

Figure 1: Example of interactive mode UI for a touch screen device showing received
categories on the left and the currently selected image (informative)
The following behaviour guidance is given:
• The user shall be allowed to switch to interactive mode.
• The device shall offer a menu view where the user shall be able to get an overview about the already received
slide categories, which contain at least one displayable slide.
• When browsing through a category the user shall always know which slide (slide x of y) is currently present.
• Navigating to a certain slide may be possible via arrow keys, numbers, touchscreen (gestures), etc.
• The user shall be able to navigate into a certain category and back into the menu view.
• The user shall be allowed to leave the interactive mode (switch back to normal mode).
5.3 Common Parameters
5.3.1 General
Whilst the methods of delivery vary between broadcast and IP, there are a number of parameters common to both, as
listed below:
• Trigger time
• Click-through URL
• Expire time
• Categorization
The function of these parameters are described in the following clauses. The implementation details of how these are
signalled to a device are detailed in clause 6 for broadcast and clause 7 for IP.
5.3.2 Trigger Time
When the device is in normal mode, the presentation of each slide may be controlled by the Service Provider by using
the Trigger Time parameter, given as a datetime or as the string value 'NOW'.
Depending on the conditions, the device shall perform one of the five actions shown in table 2 for a slide sent by the
Service Provider.
ETSI
12 ETSI TS 101 499 V3.1.1 (2015-01)
Table 2: TriggerTime Values and Behaviours
Value of Trigger Time Behaviour
The image is intended for display at the specified point in the future. The device shall
Greater than current
hold the image in the holding buffer until this time is reached. When the TriggerTime
SlideShow Reference Time
equals the SlideShow Reference Time, the image shall be displayed immediately.
Equal to the current
The image shall be shown immediately on the receiver's display.
SlideShow Reference Time
Less than the current
The image shall be held in the holding buffer, but shall not be displayed.
SlideShow Reference Time
This value has special significance and indicates that the slide shall be shown
immediately on the receiver's display.
Equals the string value:
This value only applies at the instant of reception. An image in the holding buffer which
NOW
gets updated with this value should be displayed only once unless a subsequent
TriggerTime update of NOW is received.
The image shall be held in the holding buffer, but shall not be displayed. A subsequent
No TriggerTime TriggerTime update may be received for the slide, which may then apply one of the
other conditions.
If the specified TriggerTime behaviour cannot be achieved (e.g. insufficient storage for the image), then the image shall
not be displayed.
The TriggerTime has an accuracy of 1 s.
Methods for synchronizing the SlideShow Reference Time are given in annex D.
5.3.3 ClickThroughURL
This describes a URL that may be used by a device to respond to a user action (e.g. tapping the screen while the slide is
displayed) to show a linked X(HTML) resource within a capable application on the device, e.g. an integrated web
browser.
For example, a web page giving further information/content related to the slide.
The URL is specified as a string using UTF-8 encoding, up to a maximum of 512 bytes.
5.3.4 Expire time
This parameter specifies the datetime after which presentation of a slide is no longer valid. Once this is reached or
passed, the device shall remove the slide from the display and any cache.
The Expire Time has an accuracy of 1 s.
A value for this parameter may only be provided once, and any subsequent updates shall be ignored.
5.3.5 Categorization
5.3.5.1 General
Images may be categorized so they can be browsed by the user in interactive mode.
When a slide is received containing a CategoryID/SlideID parameter value which matches that of any slide already in
the Holding Buffer, the other slides with the same CategoryID/SlideID value shall be decategorized by setting their
CategoryID/SlideID parameter value to 0x0000.
5.3.5.1 Category ID
An 8-bit number that uniquely identifies a Category. CategoryID shall not be 0x00, except to remove a previously
delivered slide from a category.
ETSI
13 ETSI TS 101 499 V3.1.1 (2015-01)
5.3.5.2 SlideID
An 8-bit number in the range 0x01-0xFF that identifies the index of the slide within the Category. When browsed by the
user, slides should be presented in the order specified by the SlideID.
The value of 0x00 shall not be used, except when decategorizing a slide.
5.3.5.3 Category Title
The CategoryTitle parameter is used to provide a user readable title for each CategoryID.
A CategoryTitle is updated by providing an object with an existing CategoryID and a new value for CategoryTitle.
Categories with CategoryID but with a null CategoryTitle shall not be shown to the user.
The CategoryTitle is a string using UTF-8 encoding, up to a maximum of 128 bytes.
5.4 Termination
The SlideShow application can be terminated either by the service provider or by user action. The screen should return
to a relevant user display.
The Service Provider may signal Termination:
• For broadcast, by removal of the service/service component transporting the application.
• For IP, by expiration of the application's DNS SRV record.
NOTE: Changing services does not necessarily cause the application to terminate.
If the newly selected service has the same SlideShow as the previously selected service, the application should continue
uninterrupted.
If the new selected service has a different or no SlideShow, images from the previously selected service should be
removed from the display immediately.
6 Delivery of SlideShow using broadcast MOT
6.1 General
The SlideShow application uses the Multimedia Object Transfer (MOT) protocol [3].
The use of the SlideShow user application within a DAB ensemble shall be signalled by the use of FIG 0/13 as specified
in ETSI EN 300 401 [1]. The UserApplicationType value is given in ETSI TS 101 756 [2]. SlideShow may be
transported using an MSC packet mode data subchannel or MSC stream audio subchannel (X-PAD part).
The use of the SlideShow user application within a DRM channel shall be signalled by the use of SDC data entity
type 5 as specified in ETSI ES 201 980 [4].The application domain shall be set to "DAB" as given in ETSI
TS 101 968 [5].The UserApplicationType value is given in ETSI TS 101 756 [2]. SlideShow shall be transported using
an MSC packet mode data stream.
No user application data bytes shall be conveyed. The receiver shall discard all user application data bytes.
Each image, together with its parameters is encoded as a single MOT object. The body data of the object contains the
raw image data, and the required Header Parameters are attached to the object in order to signal parameters for the slide.
This object is then segmented and transferred as per the bro
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

Loading comments...