IEC 62481-6-1:2017

Digital living network alliance (DLNA) home networked device interoperability guidelines - Part 6-1: Remote User Interface - HTML5

IEC 62481-6-1:2017(E) specifies guidelines that define HTML5 Remote User Interface (RUI-H). HTML5 allows operators to develop "write once, play anywhere" content applications across a broad range of browsers and platforms. Through native integration, HTML5 enables the repurposing of single codebases, resulting in reduced development costs and the provision of a unique UI for every device.

General Information

• Status: Published
• Publication Date: 26-Jul-2017
• ICS: 33.160 - Audio, video and audiovisual engineering
• ICS: 35.100.05 - Multilayer applications
• ICS: 35.110 - Networking
• Technical Committee: TC 100 - Audio, video and multimedia systems and equipment
• Current Stage: PPUB - Publication issued
• Start Date: 04-Aug-2017
• Completion Date: 27-Jul-2017

Standards Content (Sample)

IEC 62481-6-1 ®
Edition 1.0 2017-07
INTERNATIONAL
STANDARD
colour
inside
Digital living network alliance (DLNA) home networked device interoperability
guidelines –
Part 6-1: Remote User Interface – HTML5
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

IEC Central Office Tel.: [phone]
3, rue de Varembé Fax: [phone]
CH-1211 Geneva 20 [e-mail]
Switzerland www.iec.ch
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.

IEC Catalogue - webstore.iec.ch/catalogue Electropedia - www.electropedia.org
The stand-alone application for consulting the entire The world's leading online dictionary of electronic and
bibliographical information on IEC International Standards, electrical terms containing 20 000 terms and definitions in
Technical Specifications, Technical Reports and other English and French, with equivalent terms in 16 additional
documents. Available for PC, Mac OS, Android Tablets and languages. Also known as the International Electrotechnical
iPad. Vocabulary (IEV) online.

IEC publications search - www.iec.ch/searchpub IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 65 000 electrotechnical terminology entries in English and
variety of criteria (reference number, text, technical French extracted from the Terms and Definitions clause of
committee,…). It also gives information on projects, replaced IEC publications issued since 2002. Some entries have been
and withdrawn publications. collected from earlier publications of IEC TC 37, 77, 86 and

CISPR.
IEC Just Published - webstore.iec.ch/justpublished

Stay up to date on all new IEC publications. Just Published IEC Customer Service Centre - webstore.iec.ch/csc
details all new publications released. Available online and If you wish to give us your feedback on this publication or
also once a month by email. need further assistance, please contact the Customer Service
Centre: [e-mail].
IEC 62481-6-1 ®
Edition 1.0 2017-07
INTERNATIONAL
STANDARD
colour
inside
Digital living network alliance (DLNA) home networked device interoperability

guidelines –
Part 6-1: Remote User Interface – HTML5

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 33.160; 35.100.05; 35.110 ISBN 978-2-8322-4628-3

– 2 – IEC 62481-6-1:2017 © IEC 2017

CONTENTS
FOREWORD . 4
INTRODUCTION . 6
1 Scope . 7
2 Normative references . 7
3 Terms, definitions and conventions . 9
3.2 Conventions . 9
4 Networking architecture, device models and guideline conventions . 9
4.1 DLNA home networking architecture . 9
4.2 Document conventions and conventions . 9
4.3 Guideline structure and layout . 9
5 DLNA Device Model. 10
5.1 General . 10
5.2 HTML5 RUI Device Functions . 10
5.3 Device Capabilities . 10
5.4 System usages . 11
5.4.1 General . 11
5.4.2 2-box RUI-H Pull with/without A/V system usage . 12
5.4.3 3-box UI-only system usage . 13
5.4.4 3-box UI with A/V system usage . 16
6 HTML5 RUI guideline . 17
6.1 General . 17
6.2 Architecture and protocols . 17
6.3 HTML5 Remote User Interfaces . 18
6.3.1 General . 18
6.3.2 Discovery of HTML5 Remote UI devices . 18
6.3.3 RUI-H transport . 21
6.3.4 Media Formats and AV metadata . 23
6.3.5 Media Transport and control . 27
6.3.6 Content Protection guidelines . 31
6.3.7 HTML5 presentation and control: General . 31
6.3.8 HTML5 presentation and control: HTML and DOM . 32
6.3.9 HTML5 presentation and control: CSS . 33
6.3.10 HTML5 presentation and control: Image and Font Formats . 35
6.3.11 HTML5 presentation and control: JavaScript and JavaScript APIs . 36
6.3.12 HTML5 presentation and control: Cross Origin Resource Sharing . 41
6.3.13 Quality of Service . 42
6.3.14 Presentation of MPEG-2 TS Elementary Streams . 42
6.3.15 DLNA-HTML5-1.0 protocolInfo value . 45
6.3.16 RUI-H service location caching . 47
Annex A (informative) HTML5 RUI client capability detection . 49
A.1 HTML5 client capability detection . 49
A.2 CSS client capability detection . 49
Annex B (informative) RUI-H updates . 51
Annex C (informative) Web content authoring guidelines . 52
C.1 General . 52

C.2 Subtitles . 52
C.3 Ad insertion . 52
C.4 Media synchronized web content . 52
C.5 Alternate audio program . 52
C.6 Descriptive video service . 52
C.7 Discovery of DLNA devices . 53
C.8 In order to support 3-box AV scenario . 53
C.9 Filtering DLNA AV content in the UI page. 53
Annex D (informative) Combining RUI-H with AV . 54
D.1 2-box AV scenario using 2-box HTML5 RUI . 54
D.2 3-box AV scenario using 2-box HTML5 RUI . 54
Annex E (informative) HTML5 input events . 55
E.1 General . 55
E.2 Key input . 55
E.2.1 General . 55
E.2.2 Key values set . 56
E.3 Mouse . 56
E.3.1 General . 56
E.3.2 Event synthesis . 56
E.3.3 Mouse order . 56
E.3.4 Wheel . 57
E.4 Touch . 57
Annex F (normative) DLNA-HTML5-1.0 Extended XSD Schema . 58
Annex G (informative) Examples of DLNA RUI-H service UIListing . 59
G.1 Example of tw o RUI-H services . 59
G.2 Example of single RUI-H service . 60
G.3 Example of single RUI-H service with two URIs . 60
Bibliography . 62

Figure 1 — Relationship of RUI-H components . 11
Figure 2 – RUI-H Pull without A/V system usage interaction model . 12
Figure 3 – RUI-H Pull with A/V system usage interaction model . 13
Figure 4 – 3-box UI-only system usage interaction model . 14
Figure 5 – Physical configuration for 3-box UI-only system usage model . 14
Figure 6 – Physical configuration for 3-box UI-only system usage model . 15
Figure 7 – Combining 2 instances of 3-box UI-only system usage . 15
Figure 8 – 3-box UI with 3-box A/V system usage interaction model . 17

Table 1 – Collocation possibilities of +RUIHPL+ and +RUIHSRC+ capabilities for A/V. 13
Table 2 – Collocation possibilities of +RUIHSRC+ and +RUIHSINK+ capabilities for A/V
Table A.1 – HTML5 client capability detection . 49
Table A.2 – CSS client capability detection . 50

– 4 – IEC 62481-6-1:2017 © IEC 2017
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
DIGITAL LIVING NETWORK ALLIANCE (DLNA) HOME
NETWORKED DEVICE INTEROPERABILITY GUIDELINES –

Part 6-1: Remote User Interface – HTML5

FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international
co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and in
addition to other activities, IEC publishes International Standards, Technical Specifications, Technical Reports,
Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their
preparation is entrusted to technical committees; any IEC National Committee interested in the subject dealt with
may participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for
Standardization (ISO) in accordance with conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international
consensus of opinion on the relevant subjects since each technical committee has representation from all
interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence between
any IEC Publication and the corresponding national or regional publication shall be clearly indicated in the latter.
5) IEC itself does not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. IEC is not responsible for any
services carried out by independent certification bodies.
6) All users should ensure that they have the latest edition of this publication.
7) No liability shall attach to IEC or its directors, employees, servants or agents including individual experts and
members of its technical committees and IEC National Committees for any personal injury, property damage or
other damage of any nature whatsoever, whether direct or indirect, or for costs (including legal fees) and expenses
arising out of the publication, use of, or reliance upon, this IEC Publication or any other IEC Publications.
8) Attention is drawn to the Normative references cited in this publication. Use of the referenced publications is
indispensable for the correct application of this publication.
9) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of patent
rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 62481-6-1 has been prepared under technical area 8: Multimedia
home systems and applications for end-user network, of IEC technical committee 100: Audio,
video and multimedia systems and equipment.
The text of this International Standard is based on the following documents:
CDV Report on voting
100/2740/CDV 100/2887/RVC
Full information on the voting for the approval of this International Standard can be found in the
report on voting indicated in the above table.
This document has been drafted in accordance with the ISO/IEC Directives, Part 2.
A list of all parts of IEC 62481 series, published under the general title Digital Living Network
Alliance (DLNA) home networked device interoperability guidelines, can be found on the IEC
website.
The committee has decided that the contents of this document will remain unchanged until the
stability date indicated on the IEC website under "http://webstore.iec.ch" in the data related to
the specific document. At this date, the document will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
A bilingual version of this publication may be issued at a later date.

IMPORTANT – The 'colour inside' logo on the cover page of this publication indicates
that it contains colours which are considered to be useful for the correct
understanding of its contents. Users should therefore print this document using a
colour printer.
– 6 – IEC 62481-6-1:2017 © IEC 2017
INTRODUCTION
Consumers are acquiring, viewing, and managing an increasing amount of digital media (photos,
music, and video) on devices in the consumer electronics (CE), mobile, and personal computer
(PC) domains. As such, they want to conveniently enjoy the content, regardless of the source,
across different devices and locations in the home. The digital home vision integrates the
Internet, mobile, and broadcast networks through a seamless, interoperable network, which will
provide a unique opportunity for manufacturers and consumers alike. In order to deliver on this
vision, a common set of industry design guidelines is needed that allows vendors to participate
in a growing marketplace, leading to more innovation, simplicity, and value for consumers. This
document serves that purpose and provides vendors with the information needed to build
interoperable networked platforms and devices for the digital home.

DIGITAL LIVING NETWORK ALLIANCE (DLNA) HOME
NETWORKED DEVICE INTEROPERABILITY GUIDELINES –

Part 6-1: Remote User Interface – HTML5

1 Scope
This part of IEC 62481-6 specifies guidelines that define HTML5 Remote User Interface (RUI-H).
HTML5 allows operators to develop "write once, play anywhere" content applications across a
broad range of browsers and platforms. Through native integration, HTML5 enables the
repurposing of single codebases, resulting in reduced development costs and the provision of a
unique UI for every device.
2 Normative references
The following documents are referred to in the text in such a way that some or all of their content
constitutes requirements of this document. For dated references, only the edition cited applies.
For undated references, the latest edition of the referenced document (including any
amendments) applies.
IEC 62481-1-1:2017, Digital living network alliance (DLNA) home networked device
interoperability guidelines – Part 1-1: Architecture and protocols
IEC 62481-2:2017, Digital living network alliance (DLNA) home networked device
interoperability guidelines – Part 2: Media Format Profiles
IEC 62481-3:2017, Digital living network alliance (DLNA) guidelines – Part 3: Link protection
ISO/IEC 14496-22, Information technology – Coding of audio-visual objects – Part 22: Open
Font Format
http://www.iso.org/iso/catalogue_detail.htm?csnumber=52136
ISO/IEC 29341-1, Information Technology – UPnP Device Architecture – Part 1-1: UPnP Device
Architecture
ISO/IEC 29341-12-1, Information Technology – UPnP Device Architecture – Part 12-1: Remote
User Interface Device Control Protocol – Remote User Interface Client Device
ISO/IEC 29341-12-2, Information Technology – UPnP Device Architecture – Part 12-2: Remote
User Interface Device Control Protocol – Remote User Interface Server Device
ISO/IEC 29341-12-11, Information Technology – UPnP Device Architecture – Part 12-11:
Remote User Interface Device Control Protocol – Remote User Interface Server Service
ISO/IEC 29341-12-10, Information Technology – UPnP Device Architecture – Part 12-10:
Remote User Interface Device Control Protocol – Remote User Interface Client Service
ANSI/SCTE 35, Digital Program Insertion Cueing Message for Cable
http://www.scte.org/documents/pdf/standards/ANSI_SCTE%2035%202007%20Digital%20Prog
ram%20Insertion%20Cueing%20Message%20for%20Cable.pdf
or J.181
http://www.itu.int/rec/T-REC-J.181/en

– 8 – IEC 62481-6-1:2017 © IEC 2017
IETF RFC 1983, Internet Users' Glossary
https://tools.ietf.org/html/rfc1983
IETF RFC 2246 TLS Protocol Version 1.0
http://tools.ietf.org/html/rfc2246
IETF RFC 3986, Uniform Resource Identifier (URI): General Syntax
https://tools.ietf.org/html/rfc3986
IETF RFC 4346 Transport Layer Security (TLS) Protocol Version 1.1
http://tools.ietf.org/html/rfc4346
IETF RFC 5246 Transport Layer Security (TLS) Protocol Version 1.2
http://tools.ietf.org/html/rfc5246
W3C CSS Background CSS Backgrounds and Borders Module Level 3
http://www.w3.org/TR/css3-background/
W3C CSS Multicolumn, CSS Multi-column Layout Module
http://www.w3.org/TR/css3-multicol/
W3C CSS Namespaces CSS Namespaces Module
http://www.w3.org/TR/css3-namespace/
W3C CSS Text CSS Text Module Level 3
http://www.w3.org/TR/css3-text/
W3C CSS Transforms CSS Transforms Module Level 1
http://www.w3.org/TR/css-transforms-1/
W3C HTML5, Specification, A vocabulary and associated APIs for HTML and XHTML
http://www.w3.org/TR/html5/
W3C Touch Events, Touch Events
http://www.w3.org/TR/touch-events/
W3C Key Values, W3C DOM Level 3 KeyboardEvent key Values
https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3Events-key.html
W3C WOFF File Format
http://www.w3.org/TR/WOFF/
W3C MSE, Media Source Extensions
http://www.w3.org/TR/media-source/
W3C EME, Encrypted Media Extensions
http://www.w3.org/TR/encrypted-media/
W3C Crypto, Web Cryptography API
http://www.w3.org/TR/WebCryptoAPI/
W3C HTML Sourcing Inband Tracks, Sourcing In-band Media Resource Tracks from Media
Containers into HTML
http://dev.w3.org/html5/html-sourcing-inband-tracks/
W3C XML Schema Part 2, Datatypes Second Edition
http://www.w3.org/TR/xmlschema-2/

W3C WebSocket, The WebSocket API
http://www.w3.org/TR/websockets/
3 Terms, definitions and conventions
For the purposes of this document, the terms and definitions given in IEC 62481-1-1:2017 and
the following apply.
ISO and IEC maintain terminological databases for use in standardization at the following
addresses:
• IEC Electropedia: available at http://www.electropedia.org/
• ISO Online browsing platform: available at http://www.iso.org/obp
3.1.1
RUI
Remote UI
Remote User Interface
user interface provided by an application on a server device that can be rendered by one or more
client devices
3.1.2
RUI-H Content
HTML documents containing user interface elements such as Images, JavaScript, CSS, and
fonts
Note 1 to entry: This does not include Audio and A/V resources associated with HTML5MediaElement.
3.1.3
RUI-H
HTML5 Remote User Interface
HTML5-based user interface provided on a serving device that can be rendered by one or more
client devices
3.2 Conventions
In IEC 62481-1-1:2017 and this document, a number of terms, conditions, mechanisms,
sequences, parameters, events, states, or similar terms are printed with the first letter of each
word in uppercase and the rest in lowercase (e.g., Move). Any lowercase uses of these words
have the normal technical English meanings.
4 Networking architecture, device models and guideline conventions
4.1 DLNA home networking architecture
This specification extends the DLNA home networking architecture that is defined in Clause 4 of
IEC 62481-1-1:2017.
4.2 Document conventions and conventions
See Clause 6 of IEC 62481-1-1:2017 for a full description of the DLNA document conventions.
4.3 Guideline structure and layout
See 7.1 of IEC 62481-1-1:2017 for guideline and attribute table layout descriptions.

– 10 – IEC 62481-6-1:2017 © IEC 2017
5 DLNA Device Model
5.1 General
See Clause 5 of IEC 62481-1-1:2017 for detailed descriptions of the existing DLNA Device
Model. This document extends the existing DLNA devices and system usages.
5.2 HTML5 RUI Device Functions
For the HTML5 Remote User Interface Interoperability guidelines and system usages, the
following Device Functions are defined. HTML5 Remote User Interfaces (Subclause 6.3)
incorporates functionality for control, transport and rendering of remote user interfaces in the
network based on HTML5 to support the HTML5 Remote UI related system usages defined in
5.4.
• RUI-H Server (RUIHS): an RUIHS provides UPnP RUI Server Device functionality to offer
one or more remote user interfaces based on HTML5 and handling of UPnP RUI Server
Service actions.
• RUI-H Server Control Point (RUIHS-CP): an RUIHS-CP is a controller for browsing and
selecting an HTML5 remote UI offered by a RUI-H server.
• RUI-H Client (RUIHC): an RUIHC provides UPnP RUI Client device functionality for exposing
HTML5-based RUI capabilities and handling UPnP RUI Client Service actions.
• RUI-H Client Control Point (RUIHC-CP): an RUIHC-CP is a controller for setting up the
connection between an RUI-H Client and an HTML5 remote UI offered by an RUI-H Server.
• RUI-H Transport Server (RUIHTS) & RUI-H Transport Client (RUIHTC): an RUI-H Transport
Server and an RUI-H Transport Client are the device functions for transport of the RUI-H
content between a client and a server.
• RUI-H User Agent (RUIHUA): an RUI-H User Agent functionality on an RUI-H client is
responsible for retrieving, decoding, presenting and interacting with the RUI-H content
received from the RUI-H server.
5.3 Device Capabilities
In these interoperability guidelines, the following Device Capabilities are defined.
• An RUI-H Pull Controller (+RUIHPL+) with the role of finding and loading RUI-H content
exposed by a +RUIHSRC+ capability and rendering the UI content and interacting with it.
RUI-H Pull Controller includes the the following functions defined in 5.4: RUI-H Server
Control Point (RUIHS-CP), RUI-H Transport Client, RUI-H User Agent and optional DLNA
Media Transport Client.
• An RUI-H Source capability (+RUIHSRC+) with the role of exposing and sourcing RUI-H
content. RUI-H Source capability includes the following functions defined in 5.4: RUI-H
Server (RUIHS), RUI-H Transport Server and optional DLNA Media Transport Server.
• An RUI-H Sink capability (+RUIHSINK+) with the role of exposing HTML5 remote UI
functionality and rendering RUI-H content it receives from a +RUIHSRC+ capability. RUI-H
Sink capability includes the following functions defined in 5.4: RUI-H Client (RUIHC), RUI-H
Transport Client, RUI-H User Agent and optional DLNA Media Transport Client.
• An RUI-H Controller (+RUIHCTRL+) with the role of finding +RUIHSRC+ and +RUIHSINK+
capabilities, and setting up the connection between the +RUIHSINK and +RUIHSRC+.
RUI-H Controller capability includes the following functions defined in 5.4: RUI-H Server
Control Point (RUIHS-CP), RUI-H Client Control Point (RUIHC-CP).
The Device Functions that are incorporated in these Device Capabilities are illustrated in
Figure 1, which provides the details for system usages and their respective device interaction
models in 5.4.
IEC
Figure 1 — Relationship of RUI-H components
5.4 System usages
5.4.1 General
In these interoperability guidelines, the following three system usages are defined that map to all
of the use case scenarios being enabled by the detailed guidelines.
• 2-box RUI-H Pull with/without AV system usage
This usage involves a user at an RUI-H Pull Controller (+RUIHPL+), which enables a user to
find and interact with a user interface that is offered by a RUI-H Source (+RUIHSRC+), but
which is rendered by the RUI-H Pull Controller. A user interface may control AV content that
may be rendered inside the user interface.
• 3-box RUI-H only system usage
This usage involves a user at an RUI-H Controller (+RUIHCTRL+), which enables a user to
set up a remote UI connection between an RUI-H Sink (+RUIHSINK+) and a remote UI

– 12 – IEC 62481-6-1:2017 © IEC 2017
offered by an RUI-H Source (+RUIHSRC+). This system usage does not include control of
AV content that is rendered inside the user interface.
• 3-box RUI-H with AV system usage
This usage involves a user at an RUI-H Controller (+RUIHCTRL+), which enables a user to
set up a remote UI connection between an RUI-H Sink (+RUIHSINK+) and a remote UI
offered by an RUI-H Source (+RUIHSRC+), that includes control of AV content that is
rendered inside the user interface.
Subclauses 5.4.2, 5.4.3 and 5.4.4 briefly describe each of the system usages and their
respective device interaction models. Annex D provides scenarios for combining RUI-H with AV
5.4.2 2-box RUI-H Pull with/without A/V system usage
This usage enables DLNA compliant remote UI content to be pulled from a RUI-H Source
capability (+RUIHSRC+) in order to be rendered locally by a RUI-H Pull Controller (+RUIHPL+).
Figure 2 illustrates this device interaction model without A/V. The following steps are performed
in this system usage.
1) Invoke actions to find remote UI content.
2) Request UI content.
3) Transport UI content to +RUIHPL+.
4) Interaction between +RUIHPL+ and +RUIHSRC+ via Remote UI connection.
Note that the +RUIHSRC+ capability includes a UPnP Device Function in order to make the
capability discoverable in the network irrespective of the Device Class to which the capability is
added. This means that capability can be added not only to discoverable Device Classes, but
also to non-discoverable Device Classes, such as a (M-)DMC or (M-)DMP. There are no
restrictions with which Device Class the +RUIHPL+ and +RUIHSRC+ capabilities can be
co-located, unless explicitly stated in the guidelines.

IEC
Figure 2 – RUI-H Pull without A/V system usage
interaction model
This system usage can be extended to control, transport and render A/V content inside the UI.
This is enabled through co-location of the +RUIHPL+ and +RUIHSRC+ capability with the
appropriate Media Transport Client/Server device functions of existing Device Classes to which
the capabilities are added. Table 1 below shows the possibilities for co-location.
NOTE For the RUI-H Pull without an A/V system usage as stated above, there are no restrictions on co-location.

Table 1 – Collocation possibilities of +RUIHPL+ and
+RUIHSRC+ capabilities for A/V
Capability Required A/V components for Existing Device Classes/Capabilities
collocation with the required A/V components
• MT Client • DMR
+RUIHPL+
• (M-)DMP
• Content • (M-)DMS
+RUIHSRC+
• MT Server • +PU+ (Push Controller)

Graphically, the RUI-H Pull system usage with A/V rendering and control can be presented as
shown in Figure 3, whereby the +RUIHPL+ and +RUIHSRC+ capabilities are displayed together
with a hosting device class that will offer the appropriate Media Transport components.

IEC
Figure 3 – RUI-H Pull with A/V system usage
interaction model
The +RUIHPL+ and +RUIHSRC+ capabilities and Steps 1 to 4 are the same as shown in
Figure 2 and described in 5.4.2. Steps 5 and 6 are defined as follows.
5) Request associated A/V content.
6) Transport the A/V content to the Rendering Endpoint.
5.4.3 3-box UI-only system usage
This usage enables an RUI-H Controller (+RUIHCTRL+) to set up a connection between an
RUI-H Sink (+RUIHSINK+) and a remote UI offered by an RUI-H Source (+RUIHSRC+). This
only pertains to the initial setup phase from a remote UI point of view. After this point, it is
unspecified where the user is located, i.e. for interacting with the remote UI and setting up the
A/V. This can, for example, be done by using some means of user input on the +RUIHSINK+ or
+RUIHSRC+ or by pairing the +RUIHCTRL+ and the +RUIHSINK+ using an out-of-band
mechanism to provide user input (e.g. using infra-red). In the 3-box UI-only case, the system
usage does not include A/V content that is rendered as part of the user interface. Including A/V
content in the 3-box case is discussed in 5.4.4.
Figure 4 illustrates this device interaction model. The following steps are performed in this
system usage.
1) Discover and match RUI-H.
2) Instruct +RUIHSINK+ to set up a remote UI connection to +RUIHSRC+.

– 14 – IEC 62481-6-1:2017 © IEC 2017
3) Request UI content.
4) Transport UI content to +RUIHSINK+.
5) Interaction between +RUIHSINK+ and +RUIHSRC+ via Remote UI connection.

IEC
Figure 4 – 3-box UI-only system usage
interaction model
Note that the 3-box model actually refers to having three logical entities and not necessarily
three physical entities. As shown in Figure 5 and Figure 6, it is possible to combine the logical
components (i.e. +RUIHSINK+, +RUIHSRC+ and +RUIHCTRL+ capabilities) of the 3-box model
into two physical entities. In this case, certain use cases (such as remote device configuration
and setup) can be implemented either by using the 2-box RUI-H Pull model defined in the
previous subclauses, or by using such a 3-box model.

IEC
Figure 5 – Physical configuration for 3-box UI-only
system usage model
IEC
Figure 6 – Physical configuration for 3-box UI-only system usage model
As with any system usage, it is possible to combine different system usages together, or use
multiple instances of the same system usage to implement a certain use case. For example,
Figure 7 describes a more complicated usage model that is derived from a use case whereby a
mobile phone is interacting with a remote UI server, after which the remote UI gets transferred to
a large TV set. This use case can be implemented either by combining a 2-box RUI-H Pull with
a 3-box RUI-H model simultaneously, or by combining/using two instances of the 3-box RUI-H
model.
IEC
Figure 7 – Combining 2 instances of 3-box UI-only
system usage
This system usage model consists of the following steps.
1) Discover and match RUI-H.
2) Instruct +RUIHSINK+ to connect to +RUIHSRC+ (might be done internally, not via the
network.
3) Request UI content from +RUIHSRC+.
4) Transport UI content to +RUIHSINK+.
5) Interaction between +RUIHSINK+ and +RUIHSRC+ via Remote UI connection.
6) Discover and match RUI-H.
7) Instruct +RUIHSINK+ to connect to +RUIHSRC+ (can be done internally, not via the
network).
– 16 – IEC 62481-6-1:2017 © IEC 2017
8) Request UI content from +RUIHSRC+.
9) Transport UI content to +RUIHSINK+.
10) Interaction between +RUIHSINK+ and +RUIHSRC+ via remote UI connection.
5.4.4 3-box UI with A/V system usage
Rendering A/V in the 3-box model is enabled through the co-location of the +RUIHSRC+ and
+RUIHSINK+ Device Capabilities with existing Device Classes that offer the appropriate A/V
serving and rendering components, in a similar way as is done for the 2-box RUI-H Pull model
with A/V (as defined in 5.4.2). If 3-box RUI-H needs to be combined with A/V, the content of
Table 2 holds.
Table 2 – Collocation possibilities of +RUIHSRC+ and
+RUIHSINK+ capabilities for A/V
Capability Required A/V components Existing Device Classes/Capabilities
for collocation with the required A/V components
• Content • (M-)DMS
+RUIHSRC+
• MT Server • +PU+ (Push Controller)
• MT Client • DMR
+RUIHSINK+
• (M-)DMP
However, this only deals with a 2-box like A/V model, while the RUI-H is using a 3-box model.
Another 3-box case is whereby the A/V is set up by using a 3-box model. This is for example the
case when a proxy server is used to serve a remote UI for a non-remote UI enabled DMS device,
whereby the remote UI is used to control A/V content coming from the DMS device. Figure 8
illustrates such a device interaction model whereby a 3-box Remote UI model is combined with
a 3-box A/V model. In this case, the +RUIHSINK+ capability is co-located with a DMR, and the
+RUIHSRC+ capability is co-located with a (M-)DMC (could also be a DMS itself) that has a
control point to discover a DMS in the network. The following steps are performed in this system
usage.
1) Discover and match RUI-H.
2) Instruct +RUIHSINK+ to connect to +RUIHSRC+ (can be done internally, not via the network
if on the same device).
3) Request UI content.
4) Transport UI content to +RUIHSINK+.
5) Interaction between +RUIHSINK+ and (M)-DMC via Remote UI connection.
6) Browse and select A/V content.
7) Invoke actions to setup connection between DMR and (M)-DMS.
8) Request and control A/V content.
9) Transport the A/V content to the Rendering Endpoint.

IEC
Figure 8 – 3-box UI with 3-box A/V system
usage interaction model
6 HTML5 RUI guideline
6.1 General
See Clause 6 of IEC 62481-1-1:2017 for a full description of the DLNA document conventions.
Clause 6 contains guidelines for Device Functions that are elements of DLNA HTML5 RUI
capabilities.
6.2 Architecture and protocols
6.2.1
[GUIDELINE] RUI-H capabilities shall conform to all Requirements defined in 9.2 of
IEC 62481-1-1:2017 for UPnP endpoints.
[ATTRIBUTES]
M R +RUIHPL+, +RUIHSINK+ n/a n/a IEC 62481-1-1: 99SDQ
+RUIHCTRL+ 2017
+RUIHSRC+
6.2.2
[GUIDELINE] DLNA Device Classes and Device Capabilities shall fully support the applicable
mandatory portions of ISO/IEC 29341-1 for discovery, description, control, eventing, and
presentation.
[ATTRIBUTES]
M R +RUIHPL+ +RUIHSINK+ n/a n/a IEC 62481-1-1: WPUS6
+RUIHCTRL+ 2017
+RUIHSRC+
[COMMENT] DLNA specifies UPnP Device Architecture 1.0 as the basic protocol framework for
Device Classes.
– 18 – IEC 62481-6-1:2017 © IEC 2017
6.2.3
[GUIDELINE] DLNA Device Classes and Device Capabilities shall fully support the mandatory
portions of ISO/IEC 29341-1 ref_UPnP_Device_Arch for the GENURL Device Function as well
as 10.1.3.11 in IEC 62481-1-1:2017.
[ATTRIBUTES]
M A +RUIHPL+ n/a n/a ISO/IEC 29341-1 SMCEI N

6.2.4
[GUIDELINE] A RUI-H Source capability shall use the value of "+RUIHSRC+" for the
dlna-dev-capability field as defined in Guideline 9.2.10.2 (GUN 8CA7M) in IEC 62481-1-1:2017.
A RUI-H Sink capability shall use the value of “+RUIHSINK+” for the dlna-dev-capability field as
defined in guidelines 9.2.10.2 (GUN 8CA7M) in IEC 62481-1-1:2017.
[ATTRIBUTES]
M A +RUIHSRC+ n/a n/a IEC 62481-1-1: FFA55
+RUIHSINK+
6.3 HTML5 Remote User Interfaces
6.3.1 General
Subclause 6.3 covers the guidelines for implementing DLNA HTML5 Remote User Interfaces
based on W3C HTML5, Specification and related W3C specifications. The RUI-H protocol used
between RUI-H User Agents and RUI-H Servers compliant with the guidelines in 6.3 is referred
to as the DLNA-HTML5-1.0 protocol.
6.3.2 Discovery of HTML5 Remote UI devices
6.3.2.1
[GUIDELINE] A RUI-H Source capability (+RUIHSRC+) shall implement a UPnP
RemoteUIServerDevice device and a UPnP RemoteUIServer service with XML device
description as defined in ISO/IEC 29341-12-2 and XML service description as defined in
ISO/IEC 29341-12-11.
[ATTRIBUTES]
M A +RUIHSRC+ n/a n/a ISO/IEC 29341- 5O8LQ
12-11
ISO/IEC 29341-
12-2
6.3.2.2
[GUIDELINE] A RUI-H Pull Controller capability (+RUIHPL+) shall implement a UPnP
RemoteUIServerDevice control point that calls the required actions of the UPnP
RemoteUIServer service.
[ATTRIBUTES]
M A +RUIHPL+ n/a n/a ISO/IEC 29341- O9F92
12-11
ISO/IEC 29341-
12-2
6.3.2.3
[GUIDELINE] A RUI-H Sink capability (+RUIHSINK+) shall implement a UPnP
RemoteUIClientDevice device and a UPnP RemoteUIClient service with XML device description
as defined in ISO/IEC 29341-12-1 and XML service description as defined in
ISO/IEC 29341-12-10.
[ATTRIBUTES]
M A +RUIHSINK+ n/a n/a ISO/IEC 29341- G94BE
12-1
ISO/IEC 29341-
12-10
6.3.2.4
[GUIDELINE] A RUI-H Controller capability (+RUIHCTRL+) shall implement a UPnP
RemoteUIServerDevice control point that calls the required actions of the UPnP
RemoteUIServer service.
[ATTRIBUTES]
M A +RUIHCTRL+ n/a n/a ISO/IEC 29341- MK65T
12-11
ISO/IEC 29341-
12-2
6.3.2.5
[GUIDELINE] A RUI-H Controller capability (+RUIHCTRL+) shall implement a UPnP
RemoteUIClientDevice control point that calls the required actions of the UPnP RemoteUIClient
service.
[ATTRIBUTES]
M A +RUIHCTRL+ n/a n/a ISO/IEC 29341- U4CFX
12-1
ISO/IEC 29341-
12-10
6.3.2.6
[GUIDELINE] A RUI-H Client shall include a protocol element with the shortName attribute of
"DLNA-HTML5-1.0" in the RemoteUIClient.DeviceProfile state variable.
[ATTRIBUTES]
M A +RUIHSINK+ n/a n/a ISO/IEC 29341- 2SED2
12-10
– 20 – IEC 62481-6-1:2017 © IEC 2017
6.3.2.7
[GUIDELINE] If a RUI-H Client implements RemoteUIClient:GetUIListing action, then it shall
include a UI element that contains a protocol element with the shortName attribute of
"DLNA-HTML5-1.0" in a CompatibleUIList output argument of the action.
[ATTRIBUTES]
M A +RUIHSINK+ n/a n/a ISO/IEC 29341- W9IKW
12-10
6.3.2.8
[GUIDELINE] A RUI-H Client Control Point that discovers a RUI-H Client shall do so as
described in ISO/IEC 29341-1 and shall access the RUI-H Client as described in Guidelines
6.3.2.6 and 6.3.2.7.
[ATTRIBUTES]
M A +RUIHCTRL+ n/a n/a ISO/IEC 29341-1 7ZZKT

[COMMENT] The RUI-H Client Control Point discovers the RUI-H Clients based on the
properties advertised using Guidelines 6.3.2.6 to 6.3.2.7.
6.3.2.9
[GUIDELINE] A RUI-H Server serving one or more HTML5 RUIs shall include one or more UI
elements that each contains at least one URI sub-element for each protocol sub-element with a
short name of "DLNA-HTML5-1.0" in the UIListing output argument of
RemoteUIServer:GetCompatibleUIs action, when the InputDeviceProfile input argument
contains a protocol element with the shortName attribute set to "DLNA-HTML5-1.0".
[ATTRIBUTES]
M A +RUIHSRC+ n/a n/a ISO/IEC 29341- 57UEI
12-11
[COMMENT] A RUI-H Server can support more than one HTML5 RUI by using multiple UI
elements in its service descripti
...