ISO/IEC 14543-5-102:2020

ISO/IEC 14543-5-102
Edition 1.0 2020-02
INTERNATIONAL
STANDARD
colour
inside
Information technology – Home electronic system (HES) architecture –
Part 5-102: Intelligent grouping and resource sharing for HES Class 2 and
Class 3 – Remote universal management profile

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.: +41 22 919 02 11
3, rue de Varembé info@iec.ch
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 corrigendum or an amendment might have been published.

IEC publications search - webstore.iec.ch/advsearchform Electropedia - www.electropedia.org
The advanced search enables to find IEC publications by a The world's leading online dictionary on electrotechnology,
variety of criteria (reference number, text, technical containing more than 22 000 terminological entries in English
committee,…). It also gives information on projects, replaced and French, with equivalent terms in 16 additional languages.
and withdrawn publications. Also known as the International Electrotechnical Vocabulary

(IEV) online.
IEC Just Published - webstore.iec.ch/justpublished
Stay up to date on all new IEC publications. Just Published IEC Glossary - std.iec.ch/glossary
details all new publications released. Available online and 67 000 electrotechnical terminology entries in English and
once a month by email. French extracted from the Terms and definitions clause of
IEC publications issued between 2002 and 2015. Some
IEC Customer Service Centre - webstore.iec.ch/csc entries have been collected from earlier publications of IEC
If you wish to give us your feedback on this publication or TC 37, 77, 86 and CISPR.

need further assistance, please contact the Customer Service

Centre: sales@iec.ch.
ISO/IEC 14543-5-102
Edition 1.0 2020-02
INTERNATIONAL
STANDARD
colour
inside
Information technology – Home electronic system (HES) architecture –

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

Class 3 – Remote universal management profile

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 35.240.67 ISBN 978-2-8322-7521-4

– 2 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
CONTENTS
FOREWORD . 4
INTRODUCTION . 5
1 Scope . 7
2 Normative references . 7
3 Terms, definitions and abbreviated terms . 8
3.1 Terms and definitions . 8
3.2 Abbreviated terms . 10
4 Conformance . 10
5 IGRS RUMP overview . 10
6 IGRS RA and RUMP system architecture and message exchange model overview . 11
6.1 IGRS RA system structure . 11
6.2 RUMP protocol layer hierarchy . 12
6.3 Server types . 13
6.3.1 IGRS RA message exchange model in the IRSP . 13
6.3.2 Account server . 14
6.3.3 Message server . 14
6.3.4 Application server . 15
6.3.5 IRSP external application server . 15
6.4 Message exchange between user or controlled device and message server. 15
6.4.1 Device registration management . 15
6.4.2 User/controller ↔ controlled device message exchange that needs
response (control message) . 16
6.4.3 Controlled device ↔ user/controller message exchange that does not
need response (status update) . 17
6.4.4 Controlled device ↔ user/controller message exchange that does not
need response (alarm message) . 18
6.4.5 Controlled device ↔ user/controller message exchange that that needs
response (firmware version query) . 18
6.5 Workflow . 19
6.5.1 LAN control . 19
6.5.2 WAN control . 20
7 RUMP . 21
7.1 Protocol overview . 21
7.2 Applications . 21
7.3 Logical components . 21
7.4 Device ID . 21
7.5 RUMP message format . 22
7.6 RUMP response and status message format . 23
7.7 RUMP water heater . 23
7.7.1 Water heater control message format . 23
7.7.2 Water heater response and status message format . 24
7.7.3 Water heater alarm message format . 25
7.8 RUMP air conditioner . 26
7.8.1 Air conditioner control message format . 26
7.8.2 Air conditioner response and status message format . 27
7.8.3 Air conditioner alarm message format . 27
7.9 RUMP refrigerator . 28

© ISO/IEC 2020
7.9.1 Refrigerator control message format . 28
7.9.2 Refrigerator response and status message format . 29
7.9.3 Refrigerator alarm message format . 29
7.10 RUMP microwave oven . 30
7.10.1 Microwave oven control message format . 30
7.10.2 Microwave oven response and status message format . 31
7.10.3 Microwave oven alarm message format . 31
7.11 Device status query message . 32
7.12 Device version query message . 32
Bibliography . 34

Figure 1 – IGRS RA system structure . 11
Figure 2 – RUMP protocol layer . 12
Figure 3 – RUMP message interaction flow . 13
Figure 4 – Message exchange models in IGRS RA system . 14
Figure 5 – Flow of message exchange between user/controller and controlled device
that needs response . 16
Figure 6 – Flow of message exchange between controlled device and user/controller
that does not need response . 17
Figure 7 – LAN control flow diagram . 20
Figure 8 – Controller–IRSP–device WAN interaction process . 21

Table 1 – Device ID definitions . 22
Table 2 – RUMP message format . 22
Table 3 – RUMP message identifier . 23
Table 4 – Control message body . 23
Table 5 – Water heater control message format . 24
Table 6 – Water heater response and status message format . 25
Table 7 – Water heater alarm message format . 26
Table 8 – Air conditioner control message format . 26
Table 9 – Air conditioner response and status message format . 27
Table 10 – Air conditioner alarm message format. 28
Table 11 – Refrigerator control message format . 28
Table 12 – Refrigerator response and status information format . 29
Table 13 – Refrigerator alarm message format . 30
Table 14 – Microwave oven control message format . 30
Table 15 – Microwave oven response and status message format . 31
Table 16 – Microwave oven alarm message format . 32
Table 17 – Device status query request message format . 32
Table 18 – Device version query request message format . 32
Table 19 – Device version query response message format . 33

– 4 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
INFORMATION TECHNOLOGY –
HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE –
Part 5-102: Intelligent grouping and resource sharing for HES Class 2 and
Class 3 – Remote universal management profile

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-102 was prepared by subcommittee 25:
Interconnection of information technology equipment, of ISO/IEC joint technical committee 1:
Information technology.
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 website and ISO website.
The text of this standard is based on the following documents:
FDIS Report on voting
JTC1-SC25/2898/FDIS JTC1-SC25/2908/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.
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.
© ISO/IEC 2020
INTRODUCTION
ISO/IEC 14543-5 (all parts) specifies the services and protocol of the application layer for
intelligent grouping and resource sharing (IGRS) devices and services in the home electronic
system. Some parts reference Classes 1, 2 and 3, which are HES designations specified in
the HES architecture standard, ISO/IEC 14543-2-1.
ISO/IEC 14543-5 (all parts) includes the following parts.
– ISO/IEC 14543-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.
– ISO/IEC 14543-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) ISO/IEC 14543-5-21: AV profile
ii) ISO/IEC 14543-5-22: File profile
– ISO/IEC 14543-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.
– ISO/IEC 14543-5-4: Device validation
• Defines a standard method to validate an IGRS-compliant device.
– ISO/IEC 14543-5-5: Device type
• Specifies IGRS device types used in IGRS applications.
– ISO/IEC 14543-5-6: Service type
• Specifies basic service types used in IGRS applications.
– ISO/IEC 14543-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.

– 6 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
– ISO/IEC 14543-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.
– ISO/IEC 14543-5-9: Remote access service platform
• Specifies the IGRS RA service platform (IRSP) architectures and interfaces among
servers in the service platforms.
• Based on ISO/IEC 14543-5-8: Remote access core protocol.
– ISO/IEC 14543-5-101 and ISO/IEC 14543-5-102: Remote access application profiles
• Defines a device and service interaction mechanism for various applications.
• Based on ISO/IEC 14543-5-8: Remote access core protocol.
• Two profiles have been developed:
i) ISO/IEC 14543-5-101: Remote media access profile. This part defines the common
requirements for IGRS RA media users and devices in IGRS networks.
ii) ISO/IEC 14543-5-102: Remote universal management profile. This part specifies a
mechanism for integrating devices with both relatively high and low processing
capabilities into IGRS networks. It also specifies universal remote device discovery
and a management framework.
• Additional application profiles will be specified in the future.
– ISO/IEC 14543-5-11: Remote user interface
• Specifies adaptive user interface generation and remote device control mechanisms
suitable for different remote access applications and devices.
– ISO/IEC 14543-5-12: Remote access test and verification
• Defines a standard method to test and verify IGRS-RA compliant device and service
interfaces.
© ISO/IEC 2020
INFORMATION TECHNOLOGY –
HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE –

Part 5-102: Intelligent grouping and resource sharing for HES Class 2 and
Class 3 – Remote universal management profile

1 Scope
This part of ISO/IEC 14543 specifies the system architecture and communication protocols of
remote universal management profile to achieve intelligent grouping, resource sharing and
service collaboration among different devices and controllers. The protocol features are:
a) remote universal device discovery and management framework that includes connection
methods and network architecture, device configuration interfaces, management message
formats and message exchange flows;
b) request/response message formats for four remote universal management profile device
types: water heater, refrigerator, air conditioner, microwave.
This document is applicable to remote access of water heaters, refrigerators, air conditioners,
microwave ovens at home, office or other remote environments, to achieve universal
management and interactions among these controllers and 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, 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-7, Information technology – Home electronic system (HES) architecture –
Part 5-7: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Remote
access system architecture
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 14543-5-9, Information technology – Home electronic system (HES) architecture –
Part 5-9: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Remote
access service platform
ISO/IEC 15045 (all parts), Information technology – Home electronic system (HES) gateway

– 8 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
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
3.1.1
account server
IGRS RA server that processes services related to user and device account information
3.1.2
application server
IGRS RA server or third-party server located outside of an IGRS RA system that processes
application service-related logical functions
Note 1 to entry: The application server provides the approach to access application service logical functions (also
called logics). By using the application server, IGRS RA user or device or other server can access the application
service logics.
3.1.3
controlled device
device
physical device that is accessible to the controller
3.1.4
controller
physical device that can access a controlled device in the IGRS RA system
Note 1 to entry Controller is typically a mobile device or application such as a smart phone or smart pad, which is
handled by an IGRS RA user.
3.1.5
device ID
unique identification of an IGRS RA device
EXAMPLE If the local part of a device ID is “#igrsdevice” and the domain name part of the user ID is “igrs.com”,
the device ID is “#igrsdevice@igrs.com”.
Note 1 to entry A device ID consists of a local part and a domain name part. A “@” is used to separate the two
parts. Each device ID starts with a “#”.
3.1.6
device verification code
string used to examine if the user has the authority to bind a device
Note 1 to entry: For a device without a user interface, the device verification code is used to bind a device to a
user. The device owner guarantees the safety of the device verification code.
3.1.7
IGRS AS
basic service unit composed of one or multiple IGRS servers
Note 1 to entry: Each IGRS AS provides services for a dedicated user and/or device group and constructs an
IGRS RA domain. This document defines all of the necessary requirements that allow different IGRS ASs to
exchange messages with each other.

© ISO/IEC 2020
3.1.8
IGRS RA agent
functional entity which can provide the IGRS RA service to IGRS LAN devices
Note 1 to entry: The main functionalities of the IGRS RA agent are sending instructions to and receiving
instructions from the IGRS RA service platform, and translating the instructions of local IGRS networks to and from
those of the IGRS RA networks. The IGRS RA agent provides compatibility of the local IGRS devices to the IGRS
RA devices.
3.1.9
IGRS RA device
physical device that is accessible to the IGRS RA user in the IGRS RA system
3.1.10
IGRS RA server
instantiation of a service provider that may be included in an IRSP
Note 1 to entry An IGRS RA server is deployed on the internet. It maintains relationships among IGRS RA user
and IGRS devices. It also provides re-transmission of collaborative messages. The IGRS RA user and IGRS device
can start a data connection to the IRSP and support interconnections using the data connection and re-
transmission functions of the IRSP.
3.1.11
IGRS RA service platform
IRSP
collection of multiple IGRS RA servers that are deployed on the internet to maintain the
relationships among IGRS RA user and IGRS RA device and to exchange collaborative
messages
Note 1 to entry: IGRS RA user and device can establish connections to the IRSP, can send collaborative
messages over these connections and can exchange messages in the servers of the IRSP.
3.1.12
IGRS RA user
entity that uses the IGRS RA devices and application services
Note 1 to entry Generally, an IGRS RA user is a human being. Each IGRS RA user has a unique user ID
(identification). A bundle relationship can be established between one IGRS RA user and another. A binding
relationship can be established between one IGRS RA user and one IGRS device.
3.1.13
message server
IGRS RA server that processes message exchanging logics (transmitting, receiving,
forwarding and blocking, etc.)
3.1.14
server address
ID to identify the network location of a server in IGRS RA system
EXAMPLE One IGRS RA server address could be: “www.igrslab.com:8080”.
Note 1 to entry: Server address format in IGRS RA system is “domain name of server:port”.

– 10 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
3.2 Abbreviated terms
AS autonomous system
HTTP hypertext transfer protocol
ID identification
IGRS intelligent grouping and resource sharing
IRSP IGRS RA service platform
LAN local area network
RA remote access
RUMP remote universal management profile
TCP/IP transmission control protocol/ internet protocol
UI user interface
XMPP extensible messaging and presence protocol
WAN wide area network
4 Conformance
A system that conforms to this document shall be implemented according to
Clauses 5 through 7, where the IGRS remote access capabilities including system
architecture, message exchange mechanism and work flow shall conform to Clause 6, and
the RUMP application protocol for specific device types shall conform to Clause 7.
5 IGRS RUMP overview
RUMP (remote universal management profile) protocol provides specific IGRS remote access
application scenarios based on the remote management of all devices at home, office and
other remote locations, which is applicable to not only devices with strong processing
capability such as TV, PC, set-top box, etc., but also devices with weak processing capability
such as refrigerator, microwave oven, washing machine, dishwasher, etc.
RUMP defines the configuration and interface of IP and non-IP devices, the overall system
architecture of comprehensive remote control and management of a variety of home devices.
It also defines the communication interface, message flow and message format for universal
management of devices, as well as the type of connection and network structure between
non-IP devices and IP devices.
RUMP offers an efficient solution for IP or non-IP devices to access IGRS network, as it
resolves the requirements of defining common system structure, port, message format and
message flow to enable remote access of different RUMP devices (with strong or weak
processing capabilities).
The specific protocol contents are as follows.
a) Remote universal device discovery and management framework:
– connection methods and network architecture;
– device configuration interfaces;
– management message formats;
– message exchange flows.
© ISO/IEC 2020
b) Request/response message formats for four remote universal management profile device
types:
– water heater;
– refrigerator;
– air conditioner;
– microwave.
6 IGRS RA and RUMP system architecture and message exchange model
overview
6.1 IGRS RA system structure
A logical system diagram of IGRS RA is shown in Figure 1.

Figure 1 – IGRS RA system structure
As shown in Figure 1, IGRS RA system consists of IGRS RA user/device, IGRS RA server
platform as defined in ISO/IEC 14543-5-7, ISO/IEC 14543-5-8 and ISO/IEC 14543-5-9, IGRS
LAN device and IGRS RA agent (which is used for establishing a connection between IGRS
RA user/device and IGRS LAN devices). All IGRS LAN devices and IGRS RA devices within a
subnet shall use published IGRS protocols (ISO/IEC 14543-5-1) to interconnect with each
other and establish a home IGRS subnet. That is, IGRS RA protocols are backward
compatible to the published IGRS protocols.
When any IGRS RA device enters an IGRS home subnet, it operates as an IGRS LAN device.
That IGRS RA device may not only connect to other IGRS LAN devices by the IGRS protocols,
but also access IGRS RA service platform through a connection to the IGRS RA agent. In
addition, if the IGRS RA user/device in the home LAN area is able to access the internet
directly, it may build a connection to the IGRS RA service platform and access the IGRS RA
services without any intermediary agent. For IGRS LAN device that cannot be discoverable

– 12 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
over the internet, an IGRS RA agent, which is also an HES gateway service module, shall be
used instead.
IGRS RA agent may be an independent device or an IGRS RA device embedded with agent
function. IGRS RA agent shall maintain active internet connections and may access IGRS RA
service platform by those internet connections. Through the IGRS RA agent, IGRS LAN
devices without IGRS RA functions may both access the IGRS RA service platform, and be
accessed by other IGRS RA users/devices.
The IGRS RA user/device may still keep a persistent connection to the IGRS RA service
platform if it maintains an internet access connection when it leaves home or office LAN
environment.
6.2 RUMP protocol layer hierarchy
RUMP protocol layer hierarchy is shown in Figure 2.

Figure 2 – RUMP protocol layer
RUMP application layer shall process specific RUMP command, and handle the application
data transfer in the network, which includes point-to-point and point-to-multipoint data transfer.
The physical layer, data link layer and network layer, as shown in Figure 2, may adopt any
published standard communication protocols (WiFi® , Ethernet, etc.) to deliver the actual
RUMP applications.
Figure 3 shows the message interaction flow process between two RUMP devices:
a controller and controlled device.
__________
Wi-Fi is a registered trademark of Wi-Fi Alliance. This information is given for the convenience of users of this
document and does not constitute an endorsement by ISO or IEC.

© ISO/IEC 2020
Figure 3 – RUMP message interaction flow
6.3 Server types
6.3.1 IGRS RA message exchange model in the IRSP
Different message exchange models in the IRSP are shown in Figure 4.

– 14 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
Figure 4 – Message exchange models in IGRS RA system
In IGRS RA system, different servers may exchange messages with each other directly.
6.3.2 Account server
The account server processes user and device account related contents on the IRSP.
Generally, one IRSP has only one logical account server.
The functionalities of account server are:
a) managing all user and device accounts in all ASs;
b) verifying the global uniqueness of the local part of user or device ID when the user or
device registers and when the user or device information is modified. This ensures that
the IGRS RA user or device ID is unique in IGRS system;
c) processing the deletion of user or device account.
6.3.3 Message server
The message server processes message exchange logics (transmission, receiving, forwarding
and blocking, etc.). Different from an account server, one IRSP may have multiple message
servers. One AS may also have multiple message servers.
The functionalities of message server are:

© ISO/IEC 2020
a) verifying user and device login identification;
b) verifying the message exchange security between the user or device and user or device,
and between the user or device and the IRSP;
c) managing relationships between the user or device and user or device;
d) handling message operations (transmission, receiving, storing, distribution, discarding,
etc.).
In an IGRS RA system, there are several different types of message exchanges between the
message server and account server, as well as between the message server and application
server:
1) message exchange between the message server and account server;
2) message exchange between the message server and application server in the same AS;
3) message exchange between the message server and message server in different ASs;
4) message exchange between the message server and application server in different ASs.
6.3.4 Application server
The application server processes application services logics (content service, storage service,
data analysis, etc.). Two types of application servers are considered in the IGRS RA system:
a) IRSP internal application servers shall follow application logics specified in the IGRS RA
application profiles;
b) IRSP external application servers are owned and managed by third-party service
providers.
These two types of application servers may exchange messages with each other and provide
collaborative services to the user, device or AS.
6.3.5 IRSP external application server
This is a third-party owned and managed application server that exchanges messages with
the IRSP and jointly provides collaborative services with IGRS servers.
6.4 Message exchange between user or controlled device and message server
6.4.1 Device registration management
The IGRS controlled device shall send a registration request message as in Message 1.
http(s)://Domain Name of the Account Server/register.xml?name=device ID & password=
Password&domain=Domain Name of the Message Service&verifycode=device verification
code&type=device type&vendor=device vendor&model=device model
Message 1: Device registration request message
where the “verifycode”, “type”, “vendor” and “model” are optional parameters. More
information may be requested in addition to the above information.
NOTE 1 Italics indicate where content is to be inserted; all other text in message definitions is fixed in this
document.
NOTE 2 All contents in the message definition are mandatory in this document.
NOTE 3 A device ID consists of a local part and a domain name part. A “@” is used to separate the two parts.
Each device ID starts with a “#”. For example: #01aa0101# acff036e1230@igrs.com
EXAMPLE In an air conditioner use case:
Device ID: #01aa0101#acff036e1230  model number: 01  device type: air conditioner  device manufacturer: aa
Device model number: 0101   verifycode: dc2b7c12fb

– 16 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
The request message may be shown below:
http(s)://domain name of account server /register.xml?name=#01aa0101#acff036e1230
&password=password&domain= domain name of message server &verifycode= dc2b7c12fb &type=air
conditioner&vendor=aabb&model=0101
The functions and the relative information of the account server and the message service are
specified in ISO/IEC 14543-5-9.
The service platform shall return a registration response message when it receives a
registration request message from the device.
6.4.2 User/controller ↔ controlled device message exchange that needs response
(control message)
In the IGRS RA system, the messages exchanged between users and devices shall all go
through the IRSP. The IRSP shall identify the usability of the exchange request message from
the source user or device and terminate the message exchange procedure when the following
cases happen:
a) the source user or device does not have the message exchange rights with the target;
b) relationship between the source and target does not allow message exchange between
them;
c) request message contains wrong contents.
Functional flow is shown in Figure 5.

Figure 5 – Flow of message exchange between user/controller and controlled device
that needs response
When a user/controller wants to exchange messages with another controlled device and
needs the target controlled device to return a response message, the message exchange
source shall send a message exchange request message to the IRSP as in Message 2.
type=‘get’>

request_data_base64


Message 2: Exchange request message that needs response

© ISO/IEC 2020
EXAMPLE User name is 123@163.com, controlled device ID is #01aa0101#acff036e1230
Domain name of the message server is igrs.com
See message body format in 7.7, 7.8, 7.9, 7.10
Initiator user/controller identification: 123@163.com@ igrs.com
Target controlled device identification: #01aa0101#acff036e1230@igrs.com
request_data_base64: message body coded using base64
The IRSP shall receive the exchange request message and forward the received message to
the target controlled device. The target controlled device processes according to the message
contents and sends the response message to the IRSP. The response message shall be as
shown in Message 3.
If successful:
type=‘result’>

response_data_base64


If failed:
type=‘error’>




Message 3: Exchange request response message for Message 2
EXAMPLE User name is 123@163.com, controlled device ID is #01aa0101#acff036e1230
Domain name of the message server is igrs.com
See message body format in 7.7, 7.8, 7.9, 7.10
Target controlled device identification: #01aa0101#acff036e1230@igrs.com
Initiator user/controller identification: 123@163.com@ igrs.com
response_data_base64: message body coded using base64
The IRSP shall forward the request response message to the source user/controller.
6.4.3 Controlled device ↔ user/controller message exchange that does not need
response (status update)
Whenever the controlled device detects a status change, it shall send a status update
message to IRSP. IRSP shall then forward the update message to the binding user/controller.
Functional flow is shown in Figure 6.

Figure 6 – Flow of message exchange between controlled device and user/controller
that does not need response
– 18 – ISO/IEC 14543-5-102:2020
© ISO/IEC 2020
This flow is used to exchange messages when one controlled device requests a message
exchange with another user/controller but does not need the target user/controller to respond
to the request. The source shall send Message 4 to the IRSP.
type=‘normal’>

data_base64


Message 4: Exchange request message that does not need response
EXAMPLE User name is 123@163.com, controlled device ID is #01aa0101#acff036e1230
Domain name of the message server is igrs.com
See message body format in 7.7, 7.8, 7.9, 7.10.
Initiator controlled device identification: #01aa0101#acff036e1230@igrs.com
Target user/controller identification: 123@163.com@ igrs.com
data_base64: message body coded using base64
IRSP shall receive the exchange request message and forward the message to the target
user/controller. The target user/controller does not need to respond to the request.
6.4.4 Controlled device ↔ user/controller message exchange that does not need
response (alarm message)
Whenever the controlled device detects an alarm warning, it shall send an alarm message to
IRSP. IRSP shall then forward the update message to the binding user/controller.
The source shall send Message 5 to the IRSP.
...