Download 5 Home network resource management

ISO/IEC JTC 1/SC 25/WG 1 N 1487
Date 2010-11-01
Committee Draft ISO/IEC CD 30100-2
Date:2010-11-01
Reference number: ISO/IEC JTC 1/SC 25 N xxxx
Supersedes document [NONE]
THIS DOCUMENT IS STILL UNDER STUDY AND SUBJECT TO CHANGE. IT SHOULD NOT
BE USED FOR REFERENCE PURPOSES.
ISO/IEC JTC 1/SC 25
INTERCONNECTION OF
INFORMATION TECHNOLOGY
EQUIPMENT
Secretariat: Germany (DIN)
Circulated to P- and O-members, and to
technical committees and organisations in
liaison for: - voting by (P-members only)
2010-12-XX
Please return all votes and comments in
electronic form using the attached
template directly to the SC 25 Secretariat
by the due date indicated.
ISO/IEC 30100-2
Title: Information technology – Home Electronic System (HES) Home
Network Resource Management: Part 2: Architecture
Project: 1.25.01.20.02
Introductory note:
This WD is distributed for approval as CD.
The NWIP has been distributed with the SC 25 N xxxx and JTC
1 N xxxx. It has been approved as recorded in SC 25 N xxxx.
REQUESTED: National Member Bodies of ISO/IEC JTC 1/SC 25 are
ACTION
requested to vote on this document.
Recipients of this draft are invited to submit, with their comments,
notification of any relevant patent rights (not listed in the draft) of
which they are aware and to provide supporting documentation.
Medium: Defined
No. of pages: XXX
Address Reply to: Secretariat, ISO/IEC JTC 1/SC 25, Dr. -Ing. Walter P. von Pattay
Member of ZVEI FV 7 & FV 8, Germany
Tel.: +49/89/923 967 57 ¸ Tfx.: +49/89/923 967 59 (only on request)
EM: [email protected]
Home page: “http://www.iec.ch/sc25”
ISO/IEC CD 30100-2
Information technology –
Home Electronic System (HES)
Home Network Resource Management: Part 2:
Architecture
CONTENTS
Page
1
Scope ............................................................................................................................... 3
2
Normative references ....................................................................................................... 3
3
Terms, definitions and abbreviations ................................................................................ 4
4
3.1 Terms and definitions .............................................................................................. 4
3.2 Abbreviations .......................................................................................................... 5
Conformance .................................................................................................................... 6
5
Home network resource management ............................................................................... 6
6
5.1 Architecture ............................................................................................................. 6
5.2 Resource information provider ................................................................................. 7
5.3 Home resource management process ...................................................................... 8
5.4 Management application .......................................................................................... 9
5.5 Interface ................................................................................................................ 10
Home resource model .................................................................................................... 11
6.1
6.2
Home resource model ........................................................................................... 11
Home resource object ........................................................................................... 11
6.2.1 Domain, class and resource object ............................................................ 11
6.2.2 Resource object structure .......................................................................... 12
6.3 Home resource relation object ............................................................................... 18
6.3.1 Definition ................................................................................................... 18
6.3.2 BNF notation of resource relation object .................................................... 19
6.4 Miscellaneous ....................................................................................................... 20
6.4.1 Relationship generation methods ............................................................... 20
6.4.2 Common policy .......................................................................................... 20
Annex A (informative) Implementation of home resource model (example) ........................... 21
A.1
Resource types of resource object ........................................................................ 21
A.1.1 Resource type of device domain ................................................................ 21
A.1.2 Resource type of network domain .............................................................. 21
A.1.3 Resource type of service domain ............................................................... 22
A.1.4 Resource type of physical space domain ................................................... 22
Figure 1 – Logical concept of home resource management architecture .................................. 6
Figure 2 – Overview of the home network resource management architecture ........................ 7
Figure 3 – Resource information provider collects data from one or more HES entities ........... 8
Figure 4 – Resource management process model ................................................................... 8
Figure 5 – Management information ........................................................................................ 9
Figure 6 – Interfaces of resource management process ........................................................ 10
Figure 7 – Resource object hierarchy .................................................................................... 12
Figure 8 – Resource object structure .................................................................................... 12
Figure 9 - Hierarchy of relation types ....................................... Error! Bookmark not defined.
2
Table 1 – BNF notation of home resource object ................................................................... 15
Table 2 – Resource relation types ......................................................................................... 18
Table 3 – BNF notation of resource relation object ................................................................ 19
3
Information technology –
Home Electronic System (HES)
Home Network Resource Management: Part 2: Architecture
FOREWORD
1) ISO (International Organisation for Standardisation) and IEC (International Electrotechnical Commission) form the
specialised system for worldwide standardisation. Natio nal bodies that are members of ISO or IEC participate in
the development of International Standards through technical committees established by the respective
organisation to deal with particular fields of technical activity. ISO and IEC technical committe es collaborate in
fields of mutual interest. Other international organisations, governmental and non -governmental, in liaison with
ISO and IEC, also take part in the work.
2) In the field of information technology, ISO and IEC have established a joint tech nical committee, ISO/IEC JTC 1.
Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting.
Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote.
3) The former 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 and ISO member bodies.
4) IEC, ISO and ISO/IEC publications have the form of recommendations for international use and are accepted
by IEC and ISO member bodies in that sense. Why on 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.
5) In order to promote international uniformity, IEC and ISO member bodies undertake to apply IEC, ISO an d
ISO/IEC publications transparency to the maximum extent possible in their national and regional publications.
Any divergence between any ISO/IEC publication and the corresponding national or regional publication should
be clearly indicated in the latter.
6) ISO and IEC provide no marking procedure to indicate their approval and cannot be rendered responsible for any
equipment declared to be in conformity with and ISO/IEC publication.
7) All users should ensure that they have the latest edition of this publicati on.
8) 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 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.
9) 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.
10) Attention is drawn to the possibility that some of the elements of this International Standard may be the su bject 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 t echnical 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 accordanc e with the ISO/IEC Directives, Part 2.
INTRODUCTION
Home Electronic System (HES) is a collection of devices that that are able to interwork via a
common internal network. In the home environment several HES can operate concurrently
with their individual own control and management methods. This part of ISO/IEC 30100
International Standard specifies the architecture and the base methodology to support
applicationsthat extend over different HES. Home resource management allows uniform fault
processing, diagnostics and configuration management of HES elements in home
environment.
The following clauses specify the home network resource management architecture and home
resource model for transparent system configuration and diagnostic processing in the home
network.
Currently, ISO/IEC 30100, Information technology – Interconnection of information technology
equipment – Home electronic system – Home Network Resource Management, consists of the
following parts:
Part 1:
Requirements
Part 2:
Architecture
Part 3:
Management application (under development)
ISO/IEC 30100 is applicable to:

Management server in home network service provider.

Apartment complex server of apartment complex office.

Home residential gateway or set top box (STB).
2
Information technology — Home Electronic System — Home Network
Resource Management — Part 2: Architecture
1 Scope
This part of ISO/IEC 30100 defines the general information model and architecture for
managing the resources in the home network. Home network resources are managed objects,
which can be used to accomplish home network services. Essential home resources include
device, network and service resources.
This part of ISO/IEC 30100
 defines terminology to describe logical resources of devices, networks and services in
home area network,
 specifies the logical information model for describing relation s between resources and
 describes the basic logical functional procedures of home area network ( e.g. remote
maintenance, auto-configuration, fault processing)
2 Normative references
The following referenced documents are indispensable for the application 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 18012-1, Information technology – Interconnection of information technology
equipment – Home electronic system(HES) – Guidelines for product interoperability – Part 1:
Introduction
ISO/IEC 14543-2-1, Information technology – Home Electronic System (HES) Architecture –
Part 2-1: Introduction and device modularity
ISO/IEC 30100-1, Information technology – Interconnection of information technology
equipment – Home electronic system(HES) – Home Network Resource Management – Part 1:
Requirements
3
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this International Standard, the following definitions are applicable.
3.1.1
application
field of use of home resource management process
3.1.2
class
set of instances of home resource
3.1.3
device
distinct physical unit on a network, that performs a (set of) specific function(s) in a particular
context
NOTE 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 netwo rks).
3.1.4
domain
range of validity of a resource object
3.1.5
HES entity
logical component that has a defined functionality in the HES architecture
NOTE the HES architecture is specified in ISO/IEC 14543 -2-1.
3.1.6
HES interoperability framework
collection of standards defining device and network interoperability for homes
3.1.7
home resource
managed object that can be used for home network services
3.1.8
home resource management interface
data transfer between management application and home resource management process
3.1.9
home resource management process
element that performs information processing for a particular management application
3.1.10
home resource model
abstract, formal representation of resource objects in a home environment
NOTE Resource objects include resource properties, relationships and the operations that can be performed on
them.
4
3.1.11
home resource provider interface
data transfer between resource information provider and home resource management process
3.1.12
management information
set of components used either in a management application or in a resource management
process
3.1.13
network
distinct interconnection of devices that share a single physical layer implementation in terms
of the OSI layered network model
3.1.14
object
a) unit of software functionality
NOTE This definition is traditionally used in object-oriented programming. It has properties and methods for
accessing these properties and/or interacting with other objects.
b) collection of related data (attributes) and methods (procedures) for operating on that data
NOTE This definition implies a well-defined boundary (interface) and identity that encapsulates state and behaviour
3.1.15
physical space
some arbitrary set of reference coordinates 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 Collects data from HES entities and transfers the collected data to home resource management process.
3.1.17
resource object
managed unit located within the resource management process defined by home resource
model
NOTE It has methods for accessing its own properties and/or interacting with other objects. A resource object can
contain one or more HES entities.
3.1.18
resource relation object
managing unit located within the resource management process by home resource mod el
3.1.19
service
field of use of an HES
3.2 Abbreviations
HAN
HES
HNRM
HRPI
HRMI
BNF
Home Area Network
Home Electronic System
Home Network Resource Management
Home Resource Provider Interface
Home Resource Management Interface
Backus-Naur Form
5
STB
OSGi
OSI
UPnP
HGI
PIR
QoS
IFC
Set Top Box
Open Service Gateway initiative
Open System Interconnection
Universal Plug and Play
Home Gateway Initiative
Passive Infra-Red
Quality of Service
Industry Foundation Classes
4 Conformance
An entity of operational exchange conforming to this International Standard shall implement
clauses 5 and 6.
5 Home network resource management
To extend the HES interoperability architecture to the application level, several information
layers shall be defined. These layers include the service information layer, device information
layer, network information layer and physical space information layer, which are illustrated in
Figure 1. Each layer consists of information sources, for example ISO/PAS 16739 (IFC) ca n
act as an information source for physical layer (floor plan). Also the resource management
requires defined representation models for the components in each layer and a mapping
method to represent the relations between the layers, which is explained in c lause 6. In this
document, an information layer is a synonym for domain information.
Figure 1 – Logical concept of home resource management architecture
5.1 Architecture
The Home network resource management architecture is operated on top of the HES
interoperability framework. The interoperability framework abstracts the heterogeneity of
various home networks or middleware technologies. In some cases, the HES interoperability
framework may be null and directly have an interface with OSI application layer. Also some of
the OSI layers may be null or some particular implementation can have little or no
functionality at one or more of the following layers: transport, session and presentation layer.
6
Figure 2 illustrates the overview of the name network resource management architecture. In
the figure HES interoperability framework (specified in ISO/IEC 18012 -1) is targeting only the
device layer. Because home network resources can be other than devices, e.g. networ k
resources or service resources, it is reasonable to expect support for different layers in the
future. However, this is not further discussed, as it is out of scope of this document.
Management Application
Management Application
Home Resource Management Process
Resource Information Provider
Resource Information Provider
Resource Information Provider
OSI Layers 1-7
HES Interoperability Framework
{
Home Network
Middleware 1
Home Network
Middleware 2
Home Network
Middleware 3
...
Home Network
Middleware N
Figure 2 – Overview of the home network resource management architecture
The overall home resource management architecture consists of three parts as specified in5.2,
5.3 and 5.4:

Resource information provider;

Resource management process;

Management application;

Interface.
5.2 Resource information provider
The Resource information provider shall collect all data from one or more HES entities from
the home network within a single domain (e.g. physical space, service, network, device) . The
gathered information includes resource properties, functional capabilities, and status.
Essentially, it requires resource identification, type, and name. The information provider
transmits these collected data to home resource management process periodically or nonperiodically. The communication protocol or exchanging data format follows the standard
specification defined by the HES interoperability framework. In addition, the resource
information provider enables direct control to the HES entities. That is, the home resource
management process controls each HES entity via resource information provider.
As shown in Figure 3, for a single domain, there can be one or more resource information
providers.
7
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
Figure 3 – Resource information provider collects data from one or more HES entities
5.3 Home resource management process
The Home resource management process, whose structure is sho wn in Figure 4, shall consist
of resource objects and the management information. The Home resource management
process uses HRPI (Home Resource Provider Interface) 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 the interface specified in 5.5).
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.
Figure 4 – Resource management process model
Resource objects are categorised by domain and 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. 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 specified in Clause 6.
8
5.4 Management application
A management application is a user process that communicates with resource management
process via HRMI (Home Resource Management Interface) . Through HRMI, a management
application can execute diagnostics 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 resour ce management process is
presented in Figure 5.
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.4).
9
5.5 Interface
As illustrated in Figure 6 two different interfaces are required. The first one is HRMI (Home
Resource Management Interface), and the second one is HRPI (Home Resource Provider
Interface).
Figure 6 – Interfaces of resource management process
HRMI shall support the functions that are s pecified in 5.4. HRMI is used for delivering the
home resource information including resource- 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.
10
6 Home resource model
6.1 Home resource model
The Home resource model is specified as an abstract, formal representation of objects in
home that includes their properties, relationships and the operations that can be pe rformed 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 its relationship. 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 the 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 a 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 the home
environment. A resource object shall contain information from managed elements and 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 ha s 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, light,
door lock, gas sensor belong to the class “Automation” since all those 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 domainspecific 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 application manages. This specification categorises classes
by the function of the resources. Annex A illustrates an example of the classes in domains.
11
Figure 7 – Resource object hierarchy
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
Figure 8 – Resource object structure
Common information of resource object shall include following information

resource identifier
A resource identifier is a unique identifier to identify an object in a resource
management process. It consist of a couple, <domain id, object i d>, as shown in the
Table 1. A domain id is a domain identifier where the resource object belongs to. An
object id is a unique identifier to identify an object in a domain.
Domain Name
DEVICE_DOMAIN
Domain
ID
0x01
0x02
Description
NETWORK_DOMAIN
0x03
Domain ID for device resources
Domain ID for physical space
resources
Domain ID for network resources
SERVICE_DOMAIN
0x04
Domain ID for service resources
PHYSICAL_SPACE_DOMAIN
12
Figure 9 Definition of Resource Domain ID

resource name
The name of the resource object. It is a character string.

resource type
The type of a resource. It is a hexadecimal number. The Resource type is created
using the class and the sub-class of the resource object. A resource object can only
have one class. The sub-classes are defined on the basis of the class es described in
6.2.1. A sub-class is a more specific description of the resource object. The
classification of the resource types for each domain is explained in A.1.
Domain-specific information shall contain the domain-related data. The domain-related data
varies depending on the domain type. Based on the domain id in the common information, the
format of the domain specific information is determined.
The device domain specific information has following information.

device id
Device identifier. Alpha-numeric string.

device name
The name of device. Alpha-numeric string.

physical address
The physical address of the device.

status
Current status of device

version
Device version

manufacturer
Device manufacturer name

device description
Device description with user-defined format

function list
The list of functions device supports.

intra-device-domain relation
The list of intra-device-relation relation objects
The physical space domain specific information includes the following information.

object id
Physical space object identifier. Alpha-numeric string.

coordinates
Position, scale, rotation, minimum and maximum x, y, z for the physical space object
rendering

Intra-relation
13
Intra-relation with its upper class objects according to the type of object itself. Figure
10 shows the hierarchical relation between physical space object classes. By the
intra-relation information, it identifies the location of the physical space object. For
example, “Architecture” class object such as wall or floor shall contain intra-relation
information to space and address class object. “Facility” class object such as door or
power port shall contain relations to architecture, space and address class object.
Figure 10 Hierarchical intra-relation between physical space object classes

physical space object property list
List of properties consisting of property no, name and value

drawing file information
Drawing file name, size, location URI for management applications
For the network domain specific information, it is defined the following properties.

link id
Network link identifier. Alpha-numeric string.

link type
Network link type defined as Annex A.1.2.

network link topology
Node connecting information of the network link. It consists of one parent and one or
more child nodes. Node is a device.

network link status
Current status of network link

link bandwidth
Total bandwidth of the network link .

response time
The response time of network link. Its time unit shall be one of seconds, milliseconds
or micro-seconds.

loss rate
Data loss rate of network link. Its unit is percent.
The service domain specific information has following information.

service id
14
Service identifier. Alpha-numeric string.

version
Service version

vendor
Service vendor name. Alpha-numeric string.

execution environment
Environment information for service executing.

binding object list
The list of binding object for service


status
The status of service
service description
Service description with user-defined format
The structure of the resource object is also described by the BNF (Backus-Naur Form)
notation. Table 1 illustrates some properties of home resource objects.
Table 1 – BNF notation of home resource object
ResourceObject :: = <common_info> {<domain_specific_object_info>} +
<common_info> ::= <resource_id><resource_type><resourc e_name>
<resource_id> ::= <domain_id><object_id>
<domain_id>::=<identifier>
<object_id>::=<domain_specific_object_id>
<resource_type>::=<resource_class >
<resource_class>::=<<hexadecimal>
<resource_name>::=<string>
<domain_specific_object_info>::=<device_domain_info>
| <physical_space_domain_info>
| <network_domain_info>
| <service_domain_info>
<domain_specific_object_id>::=<device_id> | <netlink_id>|<service_id>|<physical_id>|,…
//Device domain-specific information
<device_domain_info>::=<device_id><device_name><physical_address>[<status>][<version>]
[<manufacturer>][<function_list>]{<intra_device_domain_relation>}*
<device_id>::=<identifier>
<device_name>::=<string>
<physical_address>::=<string>
<status>::=<string>
<version>::=<string>
<manufacturer::<string>
<function_list>::={<object_id><object_info>} *
<object_info>::=<object_name><object_id><object_category>
<input_list_size><input_list><output_list_size><output_list>
<object_name>::=<string>
<object_category>::=<string>
<input_list_size>::=<integer>
15
<output_list_size>::=<integer>
<input_list>::={<inout_info>} *
<output_list >::={<inout_info>} *
<inout_info>::= <inout_data_type><inout_name><inout_min><inout_max><inout_default_value>
<inout_description><inout_value>
<intra_device_domain_relation>::=<intra_relation_id><intra_relation_name>
<intra_relation_type><src_device_id>{<target_device_id>} +
<intra_relation_id>: := <identifier>
<intra_relation_name>::= <string>
<intra_relation_type> ::= <string>
<src_device_id> ::= <device_id>
<target_device_id> ::= {< device_id>}*
//Physical space domain-specific information
<physical_space_domain_info>::=<object_id><object_name><object_type>[<coordicates>]
[<property_list>][drawing_file_info][intra_relation_info]
<object_id>::=<identifier>
<object_name>::=<string>
<object_type>::=<physical_space_object_type>
<coordinates>::=[<position>][scale][rotate][min][max]
<position>::=<pos_x><pos_y><pos_z>
<pos_x>::=<integer>
<pos_y>::=<integer>
<pos_z>::=<integer>
<scale>::=<scale_x><scale_y><scale_z>
<scale_x>::=<integer>
<scale_y>::=<integer>
<scale_z>::=<integer>
<rotate>::=<rot_x><rot_y><rot_z>
<rot_x>::=<integer>
<rot_y>::=<integer>
<rot_z>::=<integer>
<min>::=< min_x>< min_y>< min_z>
<min _x>::=<integer>
<min _y>::=<integer>
<min _z>::=<integer>
<max>::=<max_x><max_y><max_z>
<max_x>::=<integer>
<max_y>::=<integer>
<max_z>::=<integer>
<property_list>::<number_of_property>{<property>}*
<number_of_property>::=<integer>
<property>::=<property_no><property_name><property_value>
<property_no>::=<integer>
<property_name>::=<string>
<property_value>::=<string>
<drawing_file_info>::=<file_name><location_uri><file_size>
<file_name>::=<string>
<location_uri>::=<string>
<file_size>::=<integer>
<intra_relation_info>::=<address_info>{<space_relation>|<architecture_relation>
|<facility_relation>}
<address_info>::=<string>
<space_relation>::=<space_obj_id>
<space_obj_id>::=<identifier>
<architecture_relation>::=<space_relation><architecture_obj_id>
<architecture_obj_id>::=<identifier>
<facility_relation>::=<space_relation><architecture_relation><facility_obj_id>
<facility_id>::=<identifier>
16
//Network domain-specific information
<network_domain_info>::=<netlink_id><netlink_name> <netlink_type><total_bandwidth>
[<link_topology>][<link_traffic>][<link_description>]{<intra_network_do
main_relation>}*
<netlink_id>::=<identifier>
<netlink_name>::=<string>
<netlink_address>::=<string>
<total_bandwidth>::=<bw_unit><string>
<bw_unit>::=”bps”|”kbps”|”mbps”|”gbps”
<link_topology>::=<parent_node>{<child_node>} *
<parent_node>::=<node_info>
<child_node>::=<node_info>
<node_info>::=[<node_name>]<node_id><node_addr>
<node_name>::=<string>
<node_id>::=<string>
<node_addr>::=<string>
<link_traffic>::=[<link_status>][<response_time>][<loss_rate>]
<link_status>::=<string>
<response_time>::=[<time_unit>]<string>
<time_unit>::=”sec”|”msec”|”usec”
<loss_rate>::=<string>
<link_description>::= <string>
<intra_network_domain_relation>::=<intra_relation_id><intra_relation_name><intra_relation_typ
e>
<src_netlink_id>{<target_netlink_id>} +
<src_netlink_id> ::= <netlink_id>
<target_netlink_id> ::= {< netlink_id>}*
// Service domain-specific information
<service_domain_info>::=<service_id><service_name>[<service_status>]
[<binding_obj_list>][<execution_environment>][<service_property>]
[<service_operation>][<service_description>]{<intra_service_domain_rela
tion>}*
<service_id>::=<identifier>
<service_name>::=<string>
<service_status>::=<string>
<binding_obj_list>::=[<binding_obj_id>] *
<binding_obj_id>::=<resource_id>
<execution_environment>::=<string>
<service_property>::=<string>
<service_operation>::=<string>
<service_desctiption>::=<string>
<intra_service_domain_relation>::=<intra_relation_id><intra_relation_name><intra_relation_typ
e>
<src_service_id>{<target_service_id>} +
<src_ service _id> ::= <service_id>
<target_ service _id> ::= {<service_id>}*
<string>::= {<alpha-numeric>} +
<identifier>::=<alpha> {<alpha_numeric>} *
<hexadecimal>::=0{x|X}{<hexadecimal digit> } +
<integer>::={+ | - } {<numeric> } +
<alpha_numeric>::=<alpha> | <numeric>
<hexadecimal digit>::=<numeric>|A|B|C|D|E|F|a|b|c|d|e|f
<alpha>::=any alphabetic character a through z or A through Z
<numeric>::=any digit 0 through 9
17
6.3 Home resource relation object
6.3.1 Definition
The home resource relation object is an object that specifies a relationship among resource
objects. The home resource relation object only deals with the inter -domain relationships. The
intra-domain relationships among resource objects are covered by the domain-specific
information stored in resource objects.
A relation object shall be represented as <relation_id, relation_name, relation_type,
src_resource_id, a list of target resource id >
Figure 11 Home resource relation object

relation id
A unique identifier of the relation in a resource management process.

relation name
The name of the relation. It consist of the character string

relation type
Type of the relation. This represents the relationship between domains of resource
objects. The relation types are summarized in TABLE 2.

source resource object
The resource identifier of the source object.

a list of target resource id
This is a list of target resource id.
Table 2 – Resource relation types
Physical Space
Domain
Device
Domain
Network
Domain
Service
Domain
Physical Space
Domain
Device
Domain
Network
Domain
Service
Domain
-
Locate
Install
Run
Locate
-
Connect
Bind
Install
Connect
-
Execute
Run
Bind
Execute
-
18
6.3.2 BNF notation of resource relation object
The resource relation object is also represented as a BNF notation. Table 3 illustrates a BNF
notation of the relation resource object.
Table 3 – BNF notation of resource relation object
RelationObject ::= <relation_id><relation_name><relation_type><src_resource_id>
{<target_resource_id>} +
<relation_id>: := <identifier>
<relation_name>: := <string>
<relation_type> ::= <inter_domain_relation>
<inter_domain_relation> ::= <hexadecimal number>
<src_resource_id> ::= <resource_id>
<target_resource_id> ::= < resource_id>
<string>::= {alpha-numeric} +
<identifier>::=alpha {<alpha_numeric>} *
<hexadecimal number>::=0{x|X}{<hexadecimal digit> } +
<integer>::={+ | - } {<numeric> } +
<alpha_numeric>::=<alpha> | <numeric>
<hexadecimal digit>::=<numeric>|A|B|C|D|E|F|a|b|c|d|e|f
<alpha>::=any alphabetic character a through z or A through Z
<numeric>::=any digit 0 through 0
19
6.4 Miscellaneous
6.4.1 Relationship generation methods
The relationships among the home resources must be defined for the management process.
There are three methods for generating relationships among resource objects. First, users or
a home network administrator inputs the relationship information explicitly in a pre-defined
format. They set some basic relationships for the resource management. Second, the
resource information providers provide the relationship data. The resource information
provider may provide the additional relationships since it is able to gather more detailed
resource information using various applications such as a location-positioning agent. Third, an
automatic generation method might be used. The automatic method is achieved by the
analysis of internal events or messages in resource management process. In this case,
intelligent algorithms may be applied.
6.4.2 Common policy
A home network administrator or user may limit the usage of the home resources. A common
policy is a policy used in the resource management process. It describes the basic principles
of the home resource usage and management. A common policy shall be applied whenever
someone accesses any home resources in a home network environment. A common policy
includes at least an administrative policy and a user policy.
An administrative policy specifies the rules for the relationship generation between the home
resources. It contains the conditions for the relationship generation and provides the priority
of relationship generation rules when relationships , which are generated as specified in 6.4.1,
may conflict with each other. Also, it specifies the mapping rules for the generation of interdomain relationships and conditions.
A user policy describes the personal information and preferences of the home network users
including account information. It also includes an access right s control. Access rights
determine who can access to a home resource and what functions are allowed in a home
resource management process.
20
Annex A
(informative)
Implementation of home resource model (example)
Annex A defines an example of relation instances that implement a home resource model.
A.1
Resource types of resource object
The following resource types of each domain are the instances of home resources that are
defined on the basis of Korean industry classification of home network.
A.1.1
Resource type of device domain
These are the instances of resource types in device domain.
A.1.2
Resource type of network domain
21
A.1.3
Resource type of service domain
A.1.4
Resource type of physical space domain
22
Bibliography
ISO/IEC 14543-3-1, Information technology – Home Electronic Systems (HES) Architecture –
Part 3-1: Communication layers – Application layer for network based control of HES Class 1
ISO/IEC 14543-4-1, Information technology – Home electronic system (HES) architecture –
Part 4-1: Communication layers – Application layer for network enhanced control devices of
HES Class 1
ISO/IEC 14543-5-1, Information technology – Home electronic system (HES) architecture –
Part 5-1: Intelligent grouping and resource sharing for Class 2 and Class 3 – Core protocol
ISO/IEC 14908-1, Open Data Communication in Building Automation, Controls and Building
Management – Control Network Protocol – Part 1: Protocol Stack
ISO/IEC 29341-1, Information technology – UPnP Device Architecture – Part 1: UPnP Device
Architecture Version 1.0
ISO/PAS 16739:2005, Industry Foundation Classes, Release 2x, Platform Specification
(IFC2x Platform)
23