ISO/IEC 30100-2:2016

Information technology - Home network resource management - Part 2: Architecture

ISO/IEC 30100-2:2016(E) specifies the general information model and architecture for managing the resources in a home network. Home network resources are managed objects that provide home network services. Essential home resources include device, network and service resources.

Interconnexion des équipements de technologie de l'information — Gestion du réseau domestique — Partie 2: Titre manque

General Information

• Status: Published
• Publication Date: 13-Apr-2016
• ICS: 35.110 - Networking
• ICS: 35.240.99 - IT applications in other fields
• Technical Committee: ISO/IEC JTC 1/SC 25 - Interconnection of information technology equipment
• Drafting Committee: ISO/IEC JTC 1/SC 25 - Interconnection of information technology equipment
• Current Stage: 6060 - International Standard published
• Start Date: 14-Apr-2016
• Due Date: 01-Dec-2016
• Completion Date: 01-Dec-2016

Overview - ISO/IEC 30100-2:2016 (Home network resource management - Architecture)

ISO/IEC 30100-2:2016 defines the general information model and architecture for managing resources in a home network. It is part of the ISO/IEC 30100 series and targets managed objects that provide home network services - notably device, network and service resources. The standard describes logical models, relations among resources, and basic management procedures (remote maintenance, auto-configuration, fault processing). The information model is specified as an XML-based schema (see Clause 7) and is extensible for vendor- or user-defined attributes.

Key technical topics and requirements

• Home resource model (Clause 6): Defines resource objects, domains (device, network, service, physical space), object structure, and hierarchy.
• Resource relation object: Formalizes relationships among resources (BNF notation and relation types).
• Information model and schemas (Clause 7): XML schemas describing device-specific, network-specific, physical-space and service-specific information; supports mandatory, optional and user-defined attributes.
• Architecture & process model (Clauses 5 & 4): Logical architecture including resource information providers, management applications, interfaces and the home resource management process (collection, diagnostics, configuration).
• Conformance & interfaces: Guidance on interfaces for resource management and conformance considerations.
• Security & privacy (Annex B, informative): Example models for access control (e.g., XACML), encryption and digital signatures to protect management data.
• Implementation guidance (Annexes A & C, informative): Examples for implementing XML device descriptions (IWML) and resource types.

Practical applications and who uses it

ISO/IEC 30100-2 is intended for organizations and professionals designing, deploying or operating home network management solutions:

• Service providers (management servers at provider premises) for remote maintenance and diagnostics.
• Apartment complex / building management systems for centralized residential management.
• Gateway, STB and HES device manufacturers to expose uniform management objects and attributes.
• System integrators and software developers building management applications and interfaces.
• Standards bodies and implementers needing an interoperable information model for home electronic systems (HES).

Benefits include unified fault processing, consistent auto-configuration, extensible device descriptions and improved interoperability across multi-vendor home networks.

Related standards

• ISO/IEC 30100-1 (Requirements) and ISO/IEC 30100-3 (Management application) - other parts of the series.
• ISO/IEC 14543-2-1 - Home Electronic System (HES) architecture referenced by ISO/IEC 30100.
• ISO/IEC 7498-1 - OSI basic reference model (normative reference).

Keywords: ISO/IEC 30100-2:2016, home network resource management, home network architecture, information model, HES, resource object, device/network/service resources, remote maintenance, auto-configuration, fault processing.

Standards Content (Sample)

ISO/IEC 30100-2
Edition 1.0 2016-04
INTERNATIONAL
STANDARD
colour
inside
Information technology – Home network resource management –
Part 2: Architecture
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é 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 15 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].
ISO/IEC 30100-2
Edition 1.0 2016-04
INTERNATIONAL
STANDARD
colour
inside
Information technology – Home network resource management –

Part 2: Architecture
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 35.200 ISBN 978-2-8322-3293-4

– 2 – ISO/IEC 30100-2:2016 © ISO/IEC 2016
CONTENTS
FOREWORD . 4
INTRODUCTION . 5
1 Scope . 6
2 Normative references. 6
3 Terms, definitions and abbreviations . 7
3.1 Terms and definitions . 7
3.2 Abbreviations . 9
3.3 Conventions . 10
4 Conformance . 10
5 Home network resource management . 10
5.1 Information resouce categories . 10
5.2 Architecture . 11
5.3 Resource information provider . 13
5.4 Home resource management process . 14
5.5 Management application . 14
5.6 Interface . 15
6 Home resource model . 16
6.1 Home resource model . 16
6.2 Home resource object . 16
6.2.1 Domain, class and resource object . 16
6.2.2 Resource object structure . 19
6.3 Domain-specific information . 19
6.3.1 General . 19
6.3.2 Device specific information . 20
6.3.3 Network specific information . 20
6.3.4 Physical space specific information . 20
6.3.5 Service specific information . 20
6.4 Home resource relation object . 21
6.4.1 Definition . 21
6.4.2 BNF notation of resource relation object . 22
6.5 Miscellaneous . 23
6.5.1 Relationship generation methods . 23
6.5.2 Common policy . 23
6.5.3 Privacy. 23
7 Home network resource information modeling . 24
7.1 Overview. 24
7.2 Device-specific information modelling . 24
7.3 Network specific information . 101
7.4 Physical space-specific information modelling . 116
7.5 Service-Specific Information modelling . 133
Annex A (informative) Implementation of IWML (example) . 189
A.1 Overview. 189
A.2 IWML . 189
A.2.1 General . 189
A.2.2 IWML: Device description schema . 189

Annex B (informative) Security and privacy model (examples) . 192
B.1 Overview. 192
B.2 Security and Privacy model . 192
B.2.1 General . 192
B.2.2 Access control: XACML . 192
B.2.3 Encryption: XML encryption . 193
B.2.4 Signature: XML signature . 193
Annex C (informative) Implementation of home resource model (example) . 194
C.1 Overview. 194
C.2 Resource types of resource object . 194
C.2.1 General . 194
C.2.2 Resource type of device domain . 194
C.2.3 Resource type of network domain . 195
C.2.4 Resource type of service domain . 195
C.2.5 Resource type of physical space domain . 196
Bibliography . 197

Figure 1 – Logical concept of home resource management architecture . 11
Figure 2 – Overview of the home network resource management architecture . 12
Figure 3 – Resource information provider collects data from one or more HES entities . 13
Figure 4 – Resource management process model . 14
Figure 5 – Management information . 15
Figure 6 – Interfaces of resource management process . 15
Figure 7 – Resource object hierarchy . 18
Figure 8 – Resource object structure . 19
Figure 9 – Home resource relation object . 21

Table 1 – Notations in ISO/IEC and this standard . 10
Table 2 – Definition of resource domain ID . 19
Table 3 – Resource relation types . 22
Table 4 – BNF notation of resource relation object . 23

– 4 – ISO/IEC 30100-2:2016 © ISO/IEC 2016
INFORMATION TECHNOLOGY –
HOME NETWORK RESOURCE MANAGEMENT –

Part 2: Architecture
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 30100-2 was prepared by subcommittee 25: Interconnection
of information technology equipment, of ISO/IEC joint technical committee 1: Information
technology.
A list of all currently available parts of the ISO/IEC 30100 series, published under the general
title Information technology – Home network resource management, can be found on the IEC
website.
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.

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 30100 series of standards specifies an abstract model for remote management
of home networks conforming to the Home Electronic System (HES) architecture specified in
ISO/IEC 14543-2-1. HES consists of a collection of devices that are able to interwork via a
common internal network. In a home environment several HESs may operate concurrently,
each with separate control and management methods. The Home resource management
architecture allows uniform fault processing, diagnostics and configuration management of
HES elements in a home environment.
The ISO/IEC 30100 series specifies the home network resource managment architecture and
an information model for various home network elements. The information model specifies the
minimum requirements of the functionalities that shall be provided by each HES entity. It is
specified by the XML-based schema provided in Clause 7. The information consists of the
mandatory and optional attributes including user-defined attributes. The user-defined
attributes are used for a proprietary purpose or to define attributes that are not specified in
the information model. In this part, the information model is specified to cover the physical
space, device, network and service information. This information model can be easily
extended to accommodate new types of information including user-defined attributes. These
functionalities are required to accommodate changes with minimal uploads and restructuring.
Currently, ISO/IEC 30100, Information technology – Interconnection of information technology
equipment –Home Network Resource Management, consists of the following parts:
Part 1: Requirements
Part 2: Architecture
Part 3: Management application
ISO/IEC 30100 is applicable to:
• a management server located at a home network service provider that manages home
networks;
• an apartment complex server, located in an office at the apartment complex;
• a home residential gateway or set top box (STB).

– 6 – ISO/IEC 30100-2:2016 © ISO/IEC 2016
INFORMATION TECHNOLOGY –
HOME NETWORK RESOURCE MANAGEMENT –

Part 2: Architecture
1 Scope
This part of ISO/IEC 30100 specifies the general information model and architecture for
managing the resources in a home network. Home network resources are managed objects
that provide home network services. Essential home resources include device, network and
service resources.
The objectives of this standard are to
• define terminology that describes logical resources of devices, networks and services in a
home area network;
• specify the logical information model for describing relations among resources;
• describe the basic logical functional procedures of home area networks (e.g., remote
maintenance, auto-configuration and fault processing).
2 Normative references
The following documents, in whole or in part, are normatively referenced in this document and
are indispensable for its application. For dated references, only the edition cited applies. For
undated references, the latest edition of the referenced document (including any
amendments) applies.
ISO/IEC 7498-1, Information technology – Open Systems Interconnection – Basic Reference
Model: The Basic Model
ISO/IEC 14543-2-1, Information technology – Home electronic system (HES) architecture –
Part 2-1: Introduction and device modularity
ISO/IEC 15944-8, Information technology – Business Operational View – Part 8:
Identification of privacy protection requirements as external constraints on business
transactions
ISO/IEC 18012 (all parts), Information technology – Home electronic system (HES) –
Guidelines for product interoperability
ISO/IEC 18012-2:2012, Information technology – Interconnection of information technology
equipment – Home Electronic System (HES) – Guidelines for product interoperability – Part 2:
Taxonomy and Lexicon
ISO/IEC 27000, Information technology – Security techniques – Information security
management systems – Overview and vocabulary
ISO/IEC 27001, Information technology – Security techniques – Information security
management systems – Requirements
ISO/IEC 27002, Information technology – Security techniques – Code of practice for
information security management

ISO/IEC 27003, Information technology – Security techniques – Information security
management system implementation guidance
ISO/IEC 27004, Information technology – Information security management – Measurement
ISO/IEC 27005, Information technology – Security techniques – Information security risk
management
ISO/IEC 27006, Information technology – Security techniques – Requirements for bodies
providing audit and certification of information security management systems
ISO/IEC 27007, Information technology – Security techniques – Guidelines for information
security management systems auditing
ISO/IEC TR 27008, Information technology – Security techniques – Guidelines for auditors
on information security controls
ISO/IEC 27009, Information technology – Security techniques – Sector-specific application
of ISO/IEC 27001 – Requirements
ISO/IEC 27010, Information technology – Security techniques – Information security
management system implementation guidance
ISO/IEC 27011, Information technology – Security techniques – Information security
management guidelines for telecommunications organizations based on ISO/IEC 27002
ISO/IEC 30100-1:2016, Information technology – Home network resource management –
Part 1: Requirements
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
3.1.1
apartment complex
group of two or more apartment buildings with a common manager
Note 1 to entry: A common manager provides management services for the apartment buildings. These services
may include the management of home networks in the apartments.
3.1.2
application
field of use of the home resource management process
3.1.3
class
set of instances of home resources
———————
To be published.
– 8 – ISO/IEC 30100-2:2016 © ISO/IEC 2016
3.1.4
device
distinct physical unit on a network that performs a (set of) specific function(s) in a particular
context
Note 1 to entry: A device can either be an end node on the network, or an intermediate node (as in the case of a
network gateway device connecting two distinct physical networks).
3.1.5
domain
range of validity of a resource object
3.1.6
HES entity
logical component that has a defined functionality in the HES architecture
3.1.7
HES interoperability framework
collection of standards defining device and network interoperability for homes
3.1.8
home resource
managed object that can be used for home network services
3.1.9
home resource management interface
data transfer between a management application and a home resource management process
3.1.10
home resource model
abstract, formal representation of resource objects in a home environment
Note 1 to entry: Resource objects include resource properties, relationships and the operations that can be
performed on them.
3.1.11
management application
function to be used by an apartment complex manager for suppporting the occupants
3.1.12
management information
set of components used either in a management application or in a resource management
process
3.1.13
network
devices interconnected via a common medium for communicating according the reference
model specified in ISO/IEC 7498-1
3.1.14
object
3.1.14.1
object
unit of software functionality
Note 1 to entry: This definition is traditionally used in object-oriented programming. It has properties and methods
for accessing these properties and/or interacting with other objects.

3.1.14.2
object
collection of related data (attributes) and methods (procedures) for operating on that data
Note 1 to entry: This definition implies a well-defined boundary (interface) and identity that encapsulates state
and behaviour
3.1.15
physical space
arbitrary set of reference co-ordinates of a home resource in the real world
3.1.16
resource information provider
functions for home resource management process to control HES entities
Note 1 to entry: Collects data from HES entities and transfers the collected data to the home resource
management process.
3.1.17
resource object
unit managed by the resource management process
Note 1 to entry: It has methods for accessing internal properties of the object and/or interacting with other objects.
A resource object can contain one or more HES entities.
3.1.18
resource relation object
association between resource objects
3.1.19
service
field of use of an HES
3.2 Abbreviations
AFM Automatic Fault Management
BNF Backus-Naur Form
DM Device Management
HAN Home Area Network
HES Home Electronic System
HNRM Home Network Resource Management
HRMI Home Resource Management Interface
HRPI Home Resource Provider Interface
IFC Industry Foundation Classes
IWF Inter Working Function
IWML Inter Working Markup Language
LSM Layer System Management
NM Network Management
OSI Open System Interconnection
PLC Power Line Carrier
QoS Quality of Service
RM Remote Management
STB Set Top Box
SVC Service object
– 10 – ISO/IEC 30100-2:2016 © ISO/IEC 2016
XSD XML Schema Definitions
3.3 Conventions
Table 1 shows the SI-unit equivalents of the non-SI notations used in the attributes, diagrams
and XML Schema Definitions (XSD) in Clause 7. These non-SI notations avoid syntax
conflicts with the XSD tag delimiter (“/”).
Table 1 – Notations in ISO/IEC and this standard
Notations in this standard SI units
bps bit/s
kbps kbit/s
mbps Mbit/s
gbps Gbit/s
sec s
usec µs
4 Conformance
In order to claim conformance to this standard a service provider offering management
services for home networks shall provide the following services for each home network device
as specified in ISO/IEC 14543-2-1:
• a resource management process that manages each home resource object as specified in
6.2;
• a resource management process that manages each home resource relation object as
specified in 6.4;
• a resource management process that provides the mandatory information specified in
Clause 7.
5 Home network resource management
5.1 Information resouce categories
To extend the HES interoperability architecture specified in the ISO/IEC 18012 series from
products to the management of network resources, several categories of information
resources are specified. These categories shall include devices, and may include services,
networks and physical spaces, as illustrated in Figure 1. Each category includes elements
that shall provide information resources, as described in 6.1 and Figure 2 of
ISO/IEC 30100-1:2016. For example, ISO 16739 (IFC) can act as an information resource for
the physical elements (floor plan). Also the resource management requires defined
representation models for the components of each information category and a mapping
method to represent the relations between the categories, which is explained in Clause 6. In
this standard, an information category is a synonym for domain information.

service-network relation
service-device relation
SVC LSM RM
device-network relation
LSMa SVC LSMa LSMa
NM
SVC AFM
Location Info
SVCSVC SVC
DM
Service
LonWorks
Interoperability
Device UPnP
wireless
PLC
Network
B
B B
Ethernet
Living
Porch
Kitchen Library Bedroom
Room
Physical Space
IEC
Figure 1 – Logical concept of home resource management architecture
5.2 Architecture
The HNRM system uses the HES interoperability framework (ISO/IEC 18012 series) to
integrate resource information from devices, networks and services. This integrated
information enables management services such as fault diagnosis and remote management of
HES systems.
Figure 2 illustrates the overview of the home network resource management architecture. In
Figure 2 the HES interoperability framework applies only to devices (as shown in Figure 1).
Because home network resources include more than devices, e.g. network resources or
service resources, it is reasonable to expect support in the future for the other elements
shown in Figure 1, as are services, networks, and physical spaces. However, the specification
of management services for these elements are out of scope for this standard.
The HES interoperability framework in Figure 2 includes an interworking function that
translates generic messages of the resource information provider into specific messages of
various home network technologies. For example, there is an application for device control or
configuration located in the management application in Figure 2. It requests device
information about how to control or configure the device for the home resource management
process through the HRPI (Home Resource Provider Interface). The home resource
management process sends the request from the application to the resource information
provider using HRMI (Home Resource Management Interface). The resource information
provider relays the request for the device information to the HES interoperability framework
via the framework interface. The requested message from the resource information provider
to the HES interoperability framework is called a “generic message”.

– 12 – ISO/IEC 30100-2:2016 © ISO/IEC 2016

IEC
Figure 2 – Overview of the home network resource management architecture
A generic message is sent by the resource information provider to a home application.
Devices in a home that implement the application may conform to a variety of home network
protocols and applications languages. HES specifies a choice of home network protocols in
the ISO/IEC 14543 series. The device developer is responsible for programming the device to
translate these generic HNRM messages to device-specific messages conveyed by a home
network communications protocol. The tools for this translation are specified by the
interworking function in 5.2 of ISO/IEC 18012-2:2012.
ISO/IEC 18012-2 specifies a framework for a common applicaton language using XML
structures. A device that is programmed according to ISO/IEC 18012-2 understands this XML-
based language in addition to any proprietary application language. This XML language,
based on ISO/IEC 18012-2, enables application interoperability among devices. If an
application is implemented using a proprietary language, each device or a local proxy for
these devices is responsible for translating the XML-based language to any proprietary
language. An example of the XML language is provided in Annex A.
The individual device that received the request for device information sends a response
message about device information including resource properties, functional capabilities and
status to the HES interoperability framework using its specific protocol. When the HES
interoperability framework receives the response message from the individual device, it
carries out a reverse translation from the specific message to the generic message and sends
it to the resource information provider. The translated generic response message in the
resource information provider is transmitted to the application through the reverse procedure
of that of the request. The application that received device information analyses the
information for device control, and then it sends a control request message to the individual
device through the same procedure.
An implementation of an application conformant to the HES interoperability framework
requires internal management functions to support interoperable application configuration
through the interworking function. The internal management functions are described in each
device information description. Applications read this device information to determine how to

control the device. The details of internal management functions are specific implementation
issues for each application and are outside the scope of this standard.
Thus, interoperability when components from different implementers are combined is
achieved with
• a common set of HNRM messages as specified in this standard,
• translation of these HNRM messages using ISO/IEC 18012-2 to a protocol specific for an
application that is communicated via a standardised protocol such as one of the HES
protocols.
Each implementation depends on the home network protocol and application message set
chosen by the developer. A logical connection is established between a remote server and a
local device by network management facilities during network configuration, device
installation, and service installation. The methods for establishing this connection depend on
the home networking protocol chosen.
The overall home resource management architecture consists of four parts, see description in
5.3 to 5.6.
• Resource information provider, see 5.3
• Resource management process, see 5.4
• Management application, see 5.5
• Interface, see 5.6
5.3 Resource information provider
The resource information provider shall collect all data from one or more HES entities on a
home network within a single domain (e.g. physical space, service, network and device). The
gathered information includes resource properties, functional capabilities and status.
Essentially, it requires resource identification, type and name. The information provider
transmits collected data to the home resource management process periodically or non-
periodically. The communication protocol or exchanging data format follows the standard
specifications defined by the HES interoperability framework. In addition, the resource
information provider enables direct control of the HES entities, i.e., the home resource
management process controls each HES entity via a resource information provider.
As shown in Figure 3, for a single domain, there shall be one or more resource information
providers.
Home Resource Management Process
Resource Information Provider for domain X
Resource Information Provider for Network domain
Resource Information Provider for Device domain
...
HES entity HES entity HES entity HES entity
IEC
Figure 3 – Resource information provider collects data from one or more HES entities

– 14 – ISO/IEC 30100-2:2016 © ISO/IEC 2016
5.4 Home resource management process
The home resource management process, shown in Figure 4, consists of resource objects
and the management information. The home resource management process uses HRPI to
collect the resource data from the resource information providers and to transfer control
commands back to HES entities via the resource information providers (see 5.6).
As Figure 4 illustrates, the home resource management process creates and maintains
resource objects and relation objects based on collected data from resource information
providers.
IEC
Figure 4 – Resource management process model
The home resource management process categorises resource objects by domain. Each
resource object can get an input from one or more resource information providers. Resource
objects are mapped to each other with resource relation objects. In this way, it is possible to
have one to one or one to many correspondences between the resources in different domains.
The resource object and resource relation object are described in Clause 6.
5.5 Management application
A management application is a user process that communicates with a resource management
process via HRMI. Through HRMI, a management application can execute diagnostic
functions, remote error handling and control of resources by obtaining the information from
resource objects and resource relation objects.
The interaction between a management application and the resource management process is
presented in Figure 5.
IEC
Figure 5 – Management information
As shown in Figure 5, management information comprises the application-specific
management information and common management information for resource management
process.
Application-specific management information is required by the management application to
handle user profiles, policies and application history.
Common management information includes the inter-domain relation information between
resource objects and common profile, policy and resource access rights (see 6.5).
5.6 Interface
As illustrated in Figure 6 two different interfaces are required. The first one is HRMI and the
second one is HRPI.
Operation Requirement
Management Applications
(Security Policy)
HRMI
①Access control: XACML
Resource Management Process
②Encryption: XML encryption
③Signature: XML signature
HRPI
User Requirement
Resource Information Providers
(Security Policy)
IEC
Figure 6 – Interfaces of resource management process

– 16 – ISO/IEC 30100-2:2016 © ISO/IEC 2016
In Figure 6, HRMI and HRPI shall include the data process of access control, encryption and
signature as a resource management process, and as a means for security and privacy
protection. These processes are the security countermeasures, corresponding to ①, ②, ③, as
used in an XML format. Examples of such use cases are shown in Annex B.
These processes are important, because security and privacy resource information is owned
by the resource information provider (see Clause 1 of ISO/IEC 30100-1:2016). Also those
items represented in XML data to be protected are derived from the operation requirement
(security policy) in the management application and from the usage requirement (security
policy) in resource information providers. One or more applications for managing privacy
information shall include a security standards from the ISO 27000 through ISO 27011 if the
management application collects and uses privacy information owned by resource information
providers. Also, privacy guidelines, as specified in ISO/IEC 15944-8, which include the OECD
privacy guidelines, shall be followed.
HRMI should support the functions that were described in 5.5. HRMI is used for delivering the
home resource information including resource objects and resource relation objects to
application.
HRPI is used to access resource information providers to obtain data from HES entities as
well as to control the HES entities.
6 Home resource model
6.1 Home resource model
The home resource model is an abstract, formal representation of objects in a home that shall
include object properties (specified in 6.2), relationships (specified in 6.4) and operations that
can be performed on them.
An object is the basic element in the home resource model. There are two types of objects:
resource objects and resource relation objects. A resource object represents HES entities in
one domain of a home environment. A resource relation object is an object that specifies a
relationship among resource objects between the domains.
A home resource model describes home resource information and the relationship among the
resource objects. It offers a uniform method for the management of the HES entities. A home
resource model shall be represented as a resource description schema consisting of resource
objects and resource relation objects. It is used as an input for the HRMI to exchange
resource information with other applications or systems.
A home resource model shall accommodate different systems and applications and shall
enable distribution of management information among them. Also, home resource information
may be utilised by local or remote maintenance, especially for fault diagnosis and resolution.
It may also provide means to manage quality of service (QoS) or to automate home control
tasks.
6.2 Home resource object
6.2.1 Domain, class and resource object
A home resource object is located within the resource management process in a home
environment. A resource object shall contain information from managed elements. It has three
levels of hierarchy as shown in Figure 7: (i) domain, (ii) class and (iii) object. An object
represents a basic entity in a resource hierarchy. A resource object has a one-to-one
relationship with a real-world object. This means that a resource object represents HES. The
resource objects are grouped into a class by its common functionality. For example, a light,
door lock and gas sensor all belong to the class “Automation” since these objects have a

home automating capability. Finally, the resources are grouped into a domain by the resource
type such as device, network, service and physical space. Domain information contains
domain-specific resource data of each resource object. Domain information is also utilised for
managing the intra-domain relation information of resource object. A home resource model
usually has several domains based on the number of resources it manages.
The number of the domains and classes might be added and deleted depending on the
characteristics of the resources the application manages. This specification categorises
classes by the function of the resources. Annex C illustrates an example of the classes in
domains.
– 18 – ISO/IEC 30100-2:2016 © ISO/IEC 2016

Resource
PHYSICA L_SPACE_DOMA IN DEVICE_DOMAIN NET WOR K _DOMAIN SER VICE_DOMAIN
A CCESS_NET_CLASSS
SPA CE_CLASSS HGHS_DEV_CLA SSS H_ENTERTAINMENT_CLA SSS
(ADSL, VDSL, Cable, Internet
(LivingRoom, Kitchen, (HG, HS, STB, WallPad, (Home_Theater, VOD, Game,
WiMAX,
Entrance, Balcony , etc) Home_Serv er, etc) Digital_Album, etc)
etc)
A RCHITECTURE_CLA SSS
WIRED_HAN_CLASSS
H_A utomation_CLASSS
Information_DEV_CLA SSS
(Wall, Floor, Ceiling, Safe
(Ethernet, RS485, HomePlug,
(R em ot e A ppliance_Cont rol,
Guard, Roof, Curtain Wall, (PHON E, PDA , PC, Sma rtPad , etc)
Firewire, HomePNA,, K NX,
Video_Phone, etc)
Pillar, Stairs, etc)
Echonet, etc)
FA CILITY_CLA SSS
A ppliance_DEV_CLASSS H_Security_CLA SSS
WIRELESS_HA N_CLA SSS
(Door, Windows, Tvport,
(Refrigerator, Air-Conditioner, (DISASTER_Prev ention,
(ZigBee, WLAN-a/b/g/n, BT,
LANport, Power port, Network
etc) CRIME_Prevention, etc)
UWB,
Cable, Duct, Pipe, Furniture
WiBEEM, etc)
Dev ice, Elev ator etc)
A utomation_DEV_CLASSS H_Infomation_CLASSS
(Light, Curtain, Meter, (Education, Community, Internet,
Door_Lock , Gas_Sensor, etc) etc)
A V_DEV_CLASSS H_Energy_CARE_CLA SSS
(Speak er, Camera, CamCoder, (Energy _Monitor,Energy _Control,
Printer, SmartTV, etc) Elder_Care, Health_Care, etc)
- WLAN-a/b/g/n : IE E E 802.11a/b/g/n
- ADSL : ANSI T 1.413 Issue 2 - Ethernet : ISO/IEC 8802-3 - Home PNA 3.1 : ITU G.9954
- Bl uetooth : IEEE 802.15.1
- VDSL : IT U G.993.1 - RS485 : EIA-485 - K NX : ISO/IEC 14543-3
- UWB : IEEE 802.15.3a
- Cable Internet : ITU-T J.222 - HomePlug : IEE E 1901 - Echonet - ISO/IEC 14543-4
- WiBEEM : ISO/IEC CD 29145-2
-WiMAX : IEEE 802.16e - Fi r ewi r e : IE EE 1394 - ZigBee : IEEE 802.15.4
IEC
Figure 7 – Resource object hierarchy

DOMAIN
CLASS(Object)
6.2.2 Resource object structure
As shown in Figure 8, a resource object consists of common and domain-specific object
information.
Resource object
Common information
Domain-specific object information
IEC
Figure 8 – Resou
...