ISO/IEC 14543-5-11:2018

Information technology - Home electronic system (HES) architecture - Part 5-11: Intelligent grouping and resource sharing for HES Class 2 and Class 3 - Remote user interface

ISO/IEC 14543-5-11:2018 specifies a remote user interface (RUI) for the ISO/IEC 14543-5 series on intelligent grouping and resource sharing (IGRS) for home electronic systems (HES) Class 2 and Class 3. It defines the mechanisms necessary for allowing an adaptive user interface to be displayed on and controlled by devices or control points from a remote location.

General Information

• Status: Published
• Publication Date: 27-Mar-2018
• ICS: 35.240.67 - IT applications in building and construction industry
• Technical Committee: ISO/IEC JTC 1/SC 25 - Interconnection of information technology equipment
• Current Stage: PPUB - Publication issued
• Start Date: 28-Mar-2018
• Completion Date: 26-Apr-2018

Standards Content (Sample)

ISO/IEC 14543-5-11
Edition 1.0 2018-03
INTERNATIONAL
STANDARD
colour
inside
Information technology – Home electronic system (HES) architecture –
Part 5-11: Intelligent grouping and resource sharing for HES Class 2 and
Class 3 – Remote user interface

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
ISO/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é [e-mail]
CH-1211 Geneva 20 www.iec.ch
Switzerland
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 21 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 - webstore.iec.ch/advsearchform IEC Glossary - std.iec.ch/glossary
The advanced search enables to find IEC publications by a 67 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].
ISO/IEC 14543-5-11
Edition 1.0 2018-03
INTERNATIONAL
STANDARD
colour
inside
Information technology – Home electronic system (HES) architecture –

Part 5-11: Intelligent grouping and resource sharing for HES Class 2 and

Class 3 – Remote user interface

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 35.240.67 ISBN 978-2-8322-5531-5

– 2 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
CONTENTS
FOREWORD . 5
INTRODUCTION . 7
1 Scope . 9
2 Normative references . 9
3 Terms, definitions and abbreviated terms . 9
3.1 Terms and definitions . 9
3.2 Abbreviated terms . 10
4 Conformance . 10
5 IGRS RUI overview . 11
5.1 IGRS RUI features . 11
5.2 RUI configuration models . 11
5.2.1 Overview . 11
5.2.2 Internet RUI configuration model . 11
5.2.3 2-tier RUI configuration model . 11
5.2.4 3-tier RUI configuration model . 12
5.3 RUIS and RUIC types . 12
5.4 RUI architecture . 12
5.4.1 Detailed RUI architecture . 12
5.4.2 RUIC architecture . 13
5.4.3 RUI Server architecture . 14
6 IGRS type definitions for RUIS and RUIC . 15
6.1 Overview. 15
6.2 IGRS device types for RUIS and RUIC . 15
6.3 IGRS service types for RUIS and RUIC . 16
6.4 IGRS invocation interfaces for RUIC service . 16
6.5 IGRS invocation interface for RUIS service . 16
6.6 IGRS RUI operation scenarios . 16
6.6.1 Overview . 16
6.6.2 Discovery and retrieval of server information . 16
6.6.3 Connecting . 16
6.6.4 Controlling IGRS devices using IGRS RUI . 17
7 Abstract entity in IGRS RUI . 18
8 RUI Description Language (RDL) . 21
8.1 Overview. 21
8.2 RDL element . 21
8.3 RDLPackage element . 22
8.4 RDLInfo element . 23
8.5 Declaration element . 23
8.6 Package element . 24
8.7 LayoutContainer element . 24
8.8 SceneContainer element . 25
8.9 Item element . 25
8.10 Layout element . 26
8.11 Scene element . 27
8.12 Group element . 28
8.13 Asset element . 28

8.14 ItemRef element . 29
8.15 LayoutRef element . 29
8.16 SceneNavigation element . 30
8.17 Annotation element . 30
8.18 Descriptor element . 30
8.19 Condition element . 31
8.20 Choice element . 32
8.21 Selection element . 32
8.22 Statement element . 33
8.23 DCCondition element . 34
Annex A (normative) RDL schema . 35
Bibliography . 43

Figure 1 – Internet RUI configuration model . 11
Figure 2 – 2-tier RUI configuration model . 12
Figure 3 – 3-tier RUI configuration model . 12
Figure 4 – Detailed RUI architecture . 13
Figure 5 – RUIC architecture . 14
Figure 6 – RUIS architecture . 15
Figure 7 – RUI retrieval from Internet RUIS . 17
Figure 8 – Example configuration of controlling IGRS device with RUI . 17
Figure 9 – Structures of major entities in an IGRS RUI application . 20
Figure 10 – RDL namespace declaration . 21
Figure 11 – RDL element definition . 22
Figure 12 – RDLPackage element definition . 22
Figure 13 – Example of an RDLPackage element. 23
Figure 14 – RDLInfo element definition . 23
Figure 15 – Declaration element definition . 23
Figure 16 – Package element definition . 24
Figure 17 – LayoutContainer element definition . 24
Figure 18 – SceneContainer element definition . 25
Figure 19 – Item element definition . 26
Figure 20 – Layout element definition . 27
Figure 21 – Scene element definition . 27
Figure 22 – Group element definition . 28
Figure 23 – Asset element definition . 29
Figure 24 – ItemRef element definition . 29
Figure 25 – LayoutRef element definition . 30
Figure 26 – SceneNavigation element definition . 30
Figure 27 – Annotation element definition . 30
Figure 28 – Descriptor element definition . 31
Figure 29 – Condition element definition . 31
Figure 30 – Choice element definition . 32
Figure 31 – Selection element definition . 33

– 4 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
Figure 32 – Statement element definition . 34
Figure 33 – DCCondition element definition . 34

Table 1 – RUI device type definitions . 15
Table 2 – RUI service type definitions . 16
Table 3 – Definitions of abstract entities in an IGRS RUI . 18

INFORMATION TECHNOLOGY –
HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE –

Part 5-11: Intelligent grouping and resource sharing
for HES Class 2 and Class 3 – Remote user interface

FOREWORD
1) ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission)
form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC
participate in the development of International Standards through technical committees established by the
respective organization to deal with particular fields of technical activity. ISO and IEC technical committees
collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in
liaison with ISO and IEC, also take part in the work. In the field of information technology, ISO and IEC have
established a joint technical committee, ISO/IEC JTC 1.
2) The formal decisions or agreements of IEC and ISO 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 and ISO member bodies.
3) IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted
by IEC National Committees and ISO member bodies in that sense. While all reasonable efforts are made to
ensure that the technical content of IEC, ISO and ISO/IEC publications is accurate, IEC or ISO 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 and ISO member bodies undertake to
apply IEC, ISO and ISO/IEC publications transparently to the maximum extent possible in their national and
regional publications. Any divergence between any ISO, IEC or ISO/IEC publication and the corresponding
national or regional publication should be clearly indicated in the latter.
5) ISO and IEC do not provide any attestation of conformity. Independent certification bodies provide conformity
assessment services and, in some areas, access to IEC marks of conformity. ISO or IEC are 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 ISO or its directors, employees, servants or agents including individual experts
and members of their technical committees and IEC National Committees or ISO member bodies 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 of, use of, or reliance upon, this ISO/IEC
publication or any other IEC, ISO or ISO/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 ISO/IEC publication may be the subject of
patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.
International Standard ISO/IEC 14543-5-11 was prepared by subcommittee 25:
Interconnection of information technology equipment, of ISO/IEC joint technical committee 1:
Information technology.
This International Standard has been approved by vote of the member bodies, and the voting
results may be obtained from the address given on the second title page.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
The list of all currently available parts of the ISO/IEC 14543 series, under the general title
Information technology – Home electronic system (HES) architecture, can be found on the
IEC and ISO websites.
– 6 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
In this document, the following print types are used:
• CAPITAL LETTERS: for special functions or terms
• italics: for abstract entity names in the IGRS RUI model

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.
INTRODUCTION
The ISO/IEC 14543-5 series of standards specifies the services and protocol of the
application layer for Intelligent Grouping and Resource Sharing (IGRS) devices and services
in the Home Electronic System.
The ISO/IEC 14543-5 series includes the following parts.
• IGRS Part 5-1: Core protocol
– Specifies the TCP/IP protocol stack as the basis and the HTTP protocol as the
message-exchange framework among devices.
– Specifies a series of device and service interaction/invocation standards, including
device and service discovery protocol, device and service description, service
invocation, security mechanisms, etc.
– Specifies core protocols for a type of home network that supports streaming media and
other high-speed data transports within a home.
• IGRS Parts 5-2#: Application profile
– Based on the IGRS Core Protocol.
– Specifies a device and service interaction mechanism, as well as application interfaces
used in IGRS basic applications.
– Multiple application profiles are specified, including:
i) Part 5-21: AV profile
ii) Part 5-22: File profile
• IGRS Part 5-3: Basic application
– Includes an IGRS basic application list.
– Specifies a basic application framework.
– Specifies operation details (device grouping, service description template, etc.),
function definitions and service invocation interfaces.
• IGRS Part 5-4: Device validation
– Defines a standard method to validate an IGRS-compliant device.
• IGRS Part 5-5: Device type
– Specifies IGRS Device types used in IGRS applications.
• IGRS Part 5-6: Service type
– Specifies basic service types used in IGRS applications.
• IGRS Part 5-7: Remote access system architecture
– Specifies the architecture and framework for the remote access of IGRS devices and
services in the Home Electronic System. The remote access communications protocol
and application profiles are specified in the following parts of ISO/IEC 14543-5:
i) ISO/IEC 14543-5-8: Remote access core protocol
ii) ISO/IEC 14543-5-9: Remote access service platform
iii) ISO/IEC 14543-5-101: Remote media access profile
iv) ISO/IEC 14543-5-102: Remote universal management profile
v) ISO/IEC 14543-5-11: Remote user interface
vi) ISO/IEC 14543-5-12: Remote access test and verification
– The relationships among these parts are specified in Part 5-7.

– 8 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
• IGRS Part 5-8: Remote access core protocol
– Provides detailed system components, system function modules, basic concepts of
IGRS remote access elements and their relationships, message exchange mechanisms
and security related specifications.
– Specifies interfaces between IGRS Remote Access (RA) client and service platforms.
Defines co-operative procedures among IGRS RA clients.
• IGRS Part 5-9: Remote access service platform
– Specifies the IGRS RA service platform (IRSP) architectures and interfaces among
servers in the service platforms.
– Based on Part 5-8: Remote access core protocol.
• IGRS Part 5-10#: Remote access application profiles
– Defines a device and service interaction mechanism for various applications
– Based on Part 5-8: Remote access core protocol
– The following profile is under development:
i) Part 5-101: Remote media access profile. This part defines the common
requirements for IGRS RA media users and devices in IGRS networks.
– Remote universal management profile will form the subject of a future Part 5-102. This
part will specify a mechanism for integrating devices with both relatively high and low
processing capabilities into IGRS networks. It will also specify universal remote device
discovery and a management framework.
– Additional application profiles will be specified in the future.
• IGRS Part 5-11: Remote user interface
– Specifies adaptive user interface generation and remote device control mechanisms
suitable for different remote access applications and devices.
• IGRS Part 5-12: Remote access test and verification
– Defines a standard method to test and verify IGRS-RA compliant device and service
interfaces.
__________
Under preparation. Stage at the time of publication: ISO/IEC DIS 14543-5-101:2017.
Under preparation. Stage at the time of publication: ISO/IEC DIS 14543-5-12:2017.

INFORMATION TECHNOLOGY –
HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE –

Part 5-11: Intelligent grouping and resource sharing
for HES Class 2 and Class 3 – Remote user interface

1 Scope
This part of ISO/IEC 14543-5 specifies a remote user interface (RUI) for the ISO/IEC 14543-5
series on IGRS for HES Class 2 and Class 3. It defines the mechanisms necessary for
allowing an adaptive user interface to be displayed on and controlled by devices or control
points from a remote location.
This document is applicable to IGRS local and remote access (RA) devices.
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.
ISO/IEC 14543-5-1:2010, Information technology – Home electronic system (HES)
architecture – Part 5-1: Intelligent grouping and resource sharing for HES Class 2 and
Class 3 – Core protocol
ISO/IEC 14543-5-8, Information technology – Home electronic system (HES) architecture –
Part 5-8: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Remote
access core protocol
ISO/IEC 15045 (all parts), Information technology – Home electronic system (HES) gateway
IETF RFC 2045, Multipurpose Internet Mail Extensions (MIME) – Part 1: Format of Internet
Message Bodies
IETF RFC 2616, Hypertext Transfer Protocol – HTTP/1.1
IETF RFC 4648, The Base16, Base32, and Base64 Data Encodings
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
For the purposes of this document the following terms and definitions 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

– 10 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
3.1.1
remote user interface
RUI
interface that is used for remote interaction with IGRS users
Note 1 to entry: The IGRS RUI can display information, play multimedia contents to the users or receive users’
inputs.
3.1.2
RUI Client
RUIC
logical device in an IGRS network that possesses RUI retrieval, rendering capabilities and
provides a user input interface to acquire messages for the RUIS
Note 1 to entry: An RUIC device may be physically a PC, a TV, a mobile phone, etc.
3.1.3
RUI Server
RUIS
logical device in an IGRS network that possesses capabilities for RUI contents storage and
for providing RUI contents to the RUICs
Note 1 to entry: An RUIS device may be physically a PC, a set-top-box, a server, etc.
3.1.4
RUI Control Point
RUICP
logical device in an IGRS network that possesses RUI discovery and control capabilities.
Note 1 to entry: An RUICP device may be physically integrated into an RUIC or RUIS, or may be a stand-alone
device.
3.2 Abbreviated terms
DC Delivery Context
IGRS Intelligent Grouping and Resource Sharing
RA Remote Access
RDL RUI Description Language
RUI Remote User Interface
RUIS RUI Server
RUIC RUI Client
RUICP RUI Control Point
SSDP Simple Service Discovery Protocol
UI User Interface
4 Conformance
For conformance to this document the following applies.
• The IGRS RUI system architecture shall conform to Clause 5.
• The device and service types of RUI Server (RUIS) and RUI Client (RUIC) shall conform to
Clause 6.
• The abstract entities in IGRS RUI shall conform to Clause 7.
• The RUI Description Language (RDL) shall conform to Clause 8.

5 IGRS RUI overview
5.1 IGRS RUI features
The IGRS RUI supports the following features.
a) Discovery of an RUI: the RUIS lists available UIs for the user and exposes capabilities that
it requires and supports.
b) Connecting to an RUI: the RUIC can connect to an RUIS and retrieve a matching RUI.
A separate RUI Control Point (RUICP) can also set up or control this connection.
c) Presenting RUI content: an RUIS presents RUI contents to an RUIC. The condition of an
RUIC is described in RDL. This enables the RUI device to adjust the RUI contents
according to the condition of the RUIC.
5.2 RUI configuration models
5.2.1 Overview
Three basic models for RUI configuration are defined:
a) Internet RUI configuration model;
b) 2-tier RUI configuration model;
c) 3-tier RUI configuration model.
5.2.2 Internet RUI configuration model
In this configuration, the RUIS is on the Internet. An RUIC may be discoverable (stand-alone
RUICP) or non-discoverable (RUICP and RUIC in the same box). The Internet RUI
configuration model is shown in Figure 1.
LAN
HES Internet
Gateway
RUIC
with or
RUS
without SSDP
RUICP
RUICP
IEC
Figure 1 – Internet RUI configuration model
The HES gateway is specified in the ISO/IEC 15045 series (ISO/IEC 15045-1 and
ISO/IEC 15045-2 are published). The HES gateway shall be used to connect the RUIC on the
LAN and the Internet.
NOTE ISO/IEC 15045-3, under development, is expected to address privacy and security of data passing through
the HES gateway.
5.2.3 2-tier RUI configuration model
In this configuration, all the RUI entities are on the same LAN, and the RUIS is discoverable.
The RUIC is not discoverable in this configuration, so it needs to have a RUICP in it. The
2-tier RUI configuration model is shown in Figure 2.

– 12 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
IGRS Local Network
RUIC
without SSDP
RUIS
with SSDP
RUICP
IEC
Figure 2 – 2-tier RUI configuration model
5.2.4 3-tier RUI configuration model
In this configuration, all the RUI entities are on the same LAN. The RUIS and RUIC are both
discoverable. The RUICP can be stand-alone or reside in the RUIS or RUIC. The 3-tier RUI
configuration model is shown in Figure 3.
IGRS Local Network
RUIS
RUIC
with SSDP
with SSDP
RUICP
RUICP RUICP
IEC
Figure 3 – 3-tier RUI configuration model
5.3 RUIS and RUIC types
Two types are defined for RUIS and RUIC.
a) Internet-type: the RUIC or RUIS is not discoverable on an IGRS network.
b) IGRS-type: the RUIC or RUIS is discoverable on an IGRS network, and shall be controlled
by an RUICP using the IGRS invocation interface specified in ISO/IEC 14543-5-1 and
ISO/IEC 14543-5-8.
5.4 RUI architecture
5.4.1 Detailed RUI architecture
The detailed RUI architecture is shown in Figure 4.

RUICP
Discovery Discovery
Control Control
Protocol Matching
UI Content
RUIC RUIS
Event Notifications
UI Download
IEC
Figure 4 – Detailed RUI architecture
The IGRS RUI consists of one RUICP and two RUI devices: RUIC and RUIS. The RUIS
provides RUI contents, which are described using RDL. The RUIC retrieves RDL or HTML
documents from the RUIS, renders them and provides a UI.
5.4.2 RUIC architecture
The architecture of an RUIC is shown in Figure 5 and consists of following components.
a) Discovery Manager: Optional component – Supports the IGRS discovery protocol (see
ISO/IEC 14543-5-1:2010, Clause 9).
b) IGRS RUI Browser: Retrieves and renders RUI contents from server. These contents may
be described in HTML or RDL. If described in RDL, an internal RDL Parser parses the
RDL document and generates HTML content.
c) IGRS Control: Optional component – Controls other IGRS devices according to the user
action on the RUI.
– 14 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
IGRS Discovery Message
Discovery
Manager
RDL Parser
RUI Contents
RUI Browser
IGRS
IGRS Control Invocation Interface
IGRS
Handler
IGRS
Handler
IGRS Control
Devices
IEC
Figure 5 – RUIC architecture
5.4.3 RUI Server architecture
The architecture of an RUIS is shown in Figure 6 and consists of following components:
a) Discovery Manager: Optional component – Supports the IGRS discovery protocol.
b) IGRS RUIS: Serves RUI contents.
c) RDL Contents Storage: Repository for contents described in RDL.

IGRS Discovery Message
Discovery
Manager
RUIS
RUI Contents
RDL Parser
RDL Contents
Storage
IEC
Figure 6 – RUIS architecture
6 IGRS type definitions for RUIS and RUIC
6.1 Overview
Clause 6 describes IGRS type definitions for RUIS and RUIC, including the device type
definition and service type definition. The functions of the IGRS RUIS and RUIC are to find
and match the most suitable RDL UI between RUIS and RUIC. RDL information exchange is
processed on the RDL UI, and is not within the scope of Clause 6.
6.2 IGRS device types for RUIS and RUIC
The device types for RUIS and RUIC are shown in Table 1.
Table 1 – RUI device type definitions
Device type name Functional device type Identifier Field explanation
RUIServer urn:IGRS:Device:DeviceType:RUIServerDevice Device that provides UI contents
RUIClient urn:IGRS:Device:DeviceType:RUIClientDevice Device that renders UI contents

– 16 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
6.3 IGRS service types for RUIS and RUIC
The service types for RUIS and RUIC are shown in Table 2.
Table 2 – RUI service type definitions
Service type name Service type identifier Field explanation
RUIS Service urn:IGRS:Service:ServiceType:RUIServer:1 Service that provides UI contents
RUI Client Service urn:IGRS:Service:ServiceType: RUICelinet:1 Service that renders UI contents

6.4 IGRS invocation interfaces for RUIC service
There are two invocation interfaces for RUIC service:
a) Interface name: Connect
Description: Connect to an RUIS
b) Interface name: Disconnect
Description: Close connection to an RUIS
6.5 IGRS invocation interface for RUIS service
There is only one invocation interface specified for RUIS service:
Interface name: GetRuiUri
Description: Returns URI of RUI Content Location
6.6 IGRS RUI operation scenarios
6.6.1 Overview
Subclause 6.6 shows IGRS RUI scenarios based on an IGRS invocation interface, and these
are valid for IGRS devices for 2-tier or 3-tier RUI configuration. The purpose of the IGRS
specification for an RUI is to find a server and to match a suitable UI (application) between an
RUIS and RUIC. For Internet-type devices, the RUIC knows information about the RUIS and
does not require an IGRS invocation interface.
6.6.2 Discovery and retrieval of server information
RUISs and RUICs each issue a Simple Service Discovery Protocol (SSDP) packet for the
corresponding server.
6.6.3 Connecting
The RUICP may display a list of RUICs and RUISs. If the user selects RUIS–UI–RUIC, the
RUICP issues a Connect() invocation interface to the RUIC. In this case, the argument of the
Connect() invocation interface is the URL of the selected UI.
Also, matching can be done on the RUIC. In this case, the RUICP issues a Connect()
invocation interface with the URL of the RUIS. When the RUIC receives this invocation
interface, it chooses the most suitable UI from the list and connects.
This scenario is shown on Figure 7. For the RUIC to receive the RUI from the RUIS, it needs
the address of the RUI content. This RUI content address can be set by using the internal
user interface of RUI (e.g. address bar of Browser of a smart TV), or by using the RUICP.
Once the address of the RUI content is given by either an internal UI or RUICP, the RUIC
retrieves the contents and renders it on the device.

RUIC Internet RUIS
RUICP
RUIS
Address
SSDP
Connect()
In : RUIS Address
RUIS
Address
HTTP GET
RUI Contents
RUI contents
Rendering
IEC
Figure 7 – RUI retrieval from Internet RUIS
6.6.4 Controlling IGRS devices using IGRS RUI
To control IGRS devices using IGRS RUI, IGRS RUIC shall have an IGRS Control module
that is bound to an IGRS CP. Figure 8 shows a configuration example for controlling an IGRS
device using an IGRS RUI, where the RUIC is set as an Internet RUI configuration model. The
RUI Browser in the RUIC handles RUI retrieval, rendering and user interaction. The IGRS
Control handles IGRS control messages between the RUIC and IGRS device. The RUI
Browser and IGRS Control are bound to each other using JavaScript.
IGRS
Device RUIC
RUIS
IGRS RUI
Control Browser
HTTP GET
RUI Contents
RUI contents
Rendering
User
Interaction
Script Call
Browse()
Contents List
Script Return
Contents List
Rendering
IEC
Figure 8 – Example configuration of controlling IGRS device with RUI

– 18 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018
The detailed scenario is as follows:
a) The RUI Browser retrieves the RUI (which is prepared for an IGRS device) from the RUIS.
b) The RUI Browser renders the RUI contents. If information about the IGRS device is
needed, it calls IGRS Control using JavaScript binding.
c) The RUI Browser receives user commands using RUI contents. If it needs to control an
IGRS device, it calls IGRS Control using JavaScript binding.
7 Abstract entity in IGRS RUI
16 abstract entities in an IGRS RUI model are defined in italics in Table 3.
Table 3 – Definitions of abstract entities in an IGRS RUI
Entity name Definition
A structure that allows Items to be grouped. These groupings of Items can be used to form
Package
logical Packages (for organization).
A structure that allows Layouts to be grouped. These groupings of Layouts can be used to
LayoutContainer
form logical Packages.
A structure that allows Scenes to be grouped. These groupings of scenes can be used to
SceneContainer
form logical packages.
A group or groups of sub-items that are bound to relevant Descriptors. Descriptors contain
Item information about the Item, as a representation of an Asset. Items may contain Choices,
which allow them to be customized or configured. Items may be conditional.
A Layout is a grouping of sub-layouts and/or layouts that are bound to relevant ItemRefs.
Layout Layouts may contain Conditions and Choices which allow them to be customized or
configured.
Scene A Scene is the binding of scene itself and corresponding LayoutRef.
A Group is the binding of an Asset to a set of Descriptors. These descriptors are
information concerning all or part of the specific Asset instance. Such descriptors will
Group typically contain control or structural information about the Asset (such as bit rate,
character set, start points or encryption information) but not information describing the
“content” within.
An Asset is an individually identifiable Asset such as a video or audio clip, an image, or a
Asset
textual Asset. An Asset may also potentially be a physical object.
SceneNavigation A SceneNavigation associates information about navigation within a Scene.
Annotation An Annotation associates brief description with the enclosing entity.
A Descriptor associates information with the enclosing entity. This information may be a
Descriptor
Group (such as a thumbnail of an image, or a text component), or a textual statement.
A Condition describes the enclosing entity as being optional and links it to the Selection(s)
that affect its inclusion. Multiple predicates within a Condition are combined as a
Condition conjunction (an AND relationship). Any predicate may be negated within a Condition.
Multiple Conditions associated with a given entity are combined as a disjunction (an OR
relationship) when determining whether to include the entity.
A Choice describes a set of related Selections that can affect the configuration of an Item.
Choice The Selections within a choice are either exclusive (choose exactly one) or inclusive
(choose any number, including all or none).
A Selection describes a specific decision that will affect one or more Conditions somewhere
Selection within an Item. If the Selection is chosen, its predicate becomes true; if it is not chosen, its
predicate becomes false; if it is left unresolved, its predicate is undecided.
Statement A Statement is a literal textual value that contains information.
A DCCondition describes Conditions using Delivery Context (DC) that can influence the
scalability of Scalable Remote User Interfaces and the adaptation of services. It use the
DCCondition Reverse Polish Notation, which can be easily implemented using stack-based function to
express complex conditions based on mathematical expressions such as Boolean
expressions, comparison expressions or arithmetic expressions.

Figure 9 shows the structures of the major entities in an IGRS RUI model. The major entities
include Package, LayoutContainer and SceneContainer.
Figure 9 a) shows the structure of a Package, which is the top entity and is composed of a
combination of Items. An Item can be composed of sub-Items and/or Groups. A Group is a
binding of an Asset to a set of Descriptors. Each Item and/or Group shall have a Descriptor to
describe itself.
Figure 9 b) shows the structure of a LayoutContainer, which is composed of multiple Layouts.
A Layout is composed of ItemRefs and/or sub-Layouts, where the ItemRef is a pointer to an
Item.
Figure 9 c) shows the structure of a SceneContainer, which is composed of multiple Scenes.
A Scene is composed of LayoutRefs and SceneNavigations, where the LayoutRef is a pointer
to a Layout and the SceneNavigation contains navigational information between Scenes.

– 20 – ISO/IEC 14543-5-11:2018 © ISO/IEC 2018

IEC
a) Structure of Package
IEC
b) Structure of LayoutContainer

IEC
c) Structure of SceneContainer
Figure 9 – Structures of major entities in an IGRS RUI application

8 RUI Description Language (RDL)
8.1 Overview
RDL is a description language in the form of an XML schema. RDL describes functions of
selecting and filtering RUI documents, fragments of an RUI document, or multimedia contents
of the IGRS service based on the factors such as device capabilities, user information, user
viewing environment and service policies. In addition, RDL supports efficient version
management of the RUI documents and fragments of an RUI document or multimedia
contents of the IGRS service, which are defined as digital Items of an RUI. The RDL schema
is specified in Annex A. The elements of this schema are explained in the following sub-
clauses.
8.2 RDL element
An RDL element is the root element of the RDL instance document. An RDL root element can
be either an RDL or an RDLPackage. RDL root elements have a Declarations element and/or
more than one Package, LayoutContainer or SceneContainer. RDL elements can be used for
moving or transporting Package, LayoutContainer and SceneContainer, which are described
in an RDL document.
An RDL element shall include the namespace declaration to declare the RDL namespace of
the RDL element and its contents. Applications are responsible for recognizing RDL
documents. The namespace can be described as either “default namespace declaration” or
“prefix-specific namespace declaration”.
The RDL namespace declaration is given in Figure 10. The definition of the RDL element is
shown in Figure 11.


...

or


...

IEC
Figure 10 – RDL namespace declaration
...