ISO/IEC 14543-3-3:2007

Information technology - Home electronic system (HES) architecture - Part 3-3: User process for network based control of HES Class 1

Home electronic system (HES) standards describe the architecture of home control systems including communication and interoperability aspects. This International Standard specifies the structure and functioning of servers for the group and interface objects which form the interface between the application layer and the application and management.

General Information

• Status: Published
• Publication Date: 18-Jan-2007
• ICS: 35.240.67 - IT applications in building and construction industry
• Technical Committee: ISO/IEC JTC 1/SC 25 - Interconnection of information technology equipment
• Current Stage: PPUB - Publication issued
• Start Date: 19-Jan-2007
• Completion Date: 31-Dec-2006

Overview

ISO/IEC 14543-3-3:2007 defines the user process for network‑based control of HES Class 1 within the Home Electronic System (HES) architecture. It specifies the structure and functioning of group object servers and interface object servers that form the bridge between the application layer and both application logic and management. The standard supports single‑processor and dual‑processor device designs (the latter using an External Message Interface (EMI)) and is intended as part of the ISO/IEC 14543 HES product family for home automation and smart home control.

Key topics and technical requirements

• Object models: Defines two primary object types:
  • Group objects - support a shared‑variable model and are distributed across devices; accessed via Transport layer Service Access Points (TSAPs) and mapped by the association table to Application layer Service Access Points (ASAPs).
  • Interface objects - support a client/server model and can be referenced by group objects; divided into system interface objects and application interface objects.
• Group object server (clause 6): Specifies data structures, communication flags, value transfer operations (read/write/update), and multicast access rules for group objects.
• Interface object server (clause 7): Defines address levels, interworking requirements, system interface objects (device object, group address table, association table, application object) and application interface object behavior; details application service message flows for property read/write/description services.
• Conformance: Implementations conforming to this part must support the group objects specified in clause 6; implementation of interface objects (clause 7) is optional.
• Scope boundaries: This part is a product‑family component and is not intended to be used standalone; normative references include ISO/IEC 14543‑3‑1 and 14543‑3‑4.

Applications and users

Practical uses include:

• Designing and certifying HES Class 1 devices (lighting controllers, simple actuators/sensors) for interoperable home automation.
• Implementing the application interface layer in Bus Access Units (BAU) for embedded device firmware.
• Integrating multicast group communications and client/server interfaces in smart home gateways and controllers. Primary users:
• Device manufacturers and firmware engineers
• Home automation system integrators and product designers
• Test labs and certification bodies validating HES interoperability
• Standards and protocol architects for IoT/home networks

Related standards

• ISO/IEC 14543-3-1 - Application layer for network based control (HES Class 1)
• ISO/IEC 14543-3-2 - Transport, network and data link parts
• ISO/IEC 14543-3-4 - System management for HES Class 1
• Other parts covering media (power line, twisted pair, RF) and higher HES classes

Keywords: ISO/IEC 14543-3-3, HES, home electronic system, home automation standard, group objects, interface objects, application interface layer, BAU, HES Class 1.

Standards Content (Sample)

ISO/IEC 14543-3-3
Edition 1.0 2007-01
INTERNATIONAL
STANDARD
Information technology – Home electronic system (HES) architecture –
Part 3-3: User process for network based control of HES Class 1

All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form
or by any means, electronic or mechanical, including photocopying and microfilm, without permission in writing from
either IEC or IEC's member National Committee in the country of the requester. If you have any questions about IEC
copyright or have an enquiry about obtaining additional rights to this publication, please contact the address below or
your local IEC member National Committee for further information.

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

About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a 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: [e-mail].
ISO/IEC 14543-3-3
Edition 1.0 2007-01
INTERNATIONAL
STANDARD
Information technology – Home electronic system (HES) architecture –

Part 3-3: User process for network based control of HES Class 1

INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
ICS 35.240.67 ISBN 2-8318-8906-5

– 2 – 14543-3-3 © ISO/IEC:2007(E)
CONTENTS
FOREWORD.4
INTRODUCTION.5
1 Scope.7
2 Normative references.7
3 Terms, definitions and abbreviations .7
3.1 Terms and definitions .7
3.2 Abbreviations.7
4 Conformance.7
5 Object models .8
6 Group object server .8
6.1 Overview .8
6.2 General data structure group objects .9
6.2.1 Structure.9
6.2.2 Group object description .9
6.2.3 Communication flags .10
6.2.4 Group object value.11
6.3 Group object value transfers .11
6.3.1 Overview of group object value transfers.11
6.3.2 Reading the group object value .12
6.3.3 Receiving a request to read the group object value.12
6.3.4 Writing the group object value.13
6.3.5 Receiving an update of the group object value.13
7 Interface object server .13
7.1 Overview .13
7.2 Address levels for interface objects.15
7.3 Interworking requirements for interface objects .15
7.4 System interface objects (management objects).15
7.5 Application interface objects .15
7.5.1 General .15
7.5.2 Property server for own application interface objects .15
7.5.3 Property client for accessing remote application interface objects.16
7.5.4 Message flow for interface object services .16
Bibliography .18

14543-3-3 © ISO/IEC:2007(E) – 3 –

Figure 1 – User process model.8
Figure 2 – Data structure of group objects .9
Figure 3 – Reading a group object value.12
Figure 4 – Receiving a request to read the group object value .12
Figure 5 – Writing a group object value .13
Figure 6 – Receiving an update of the group object value .13
Figure 7 – Structure of interface objects .14
Figure 8 – Message flow for the A_PropertyValue_Read-service.16
Figure 9 – Message flow for the A_PropertyValue_Write-service.16
Figure 10 – Message flow for the A_PropertyDescription_Read-service .17

Table 1 – Group object types.9

– 4 – 14543-3-3 © ISO/IEC:2007(E)
INFORMATION TECHNOLOGY -
HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE –

Part 3-3: User process for network based control of HES Class 1

FOREWORD
1) ISO (International Organization for Standardization) and IEC (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. Their preparation is entrusted to technical
committees; any ISO and IEC National Committee interested in the subject dealt with may participate in this
preparatory work. International governmental and non-governmental organizations liaising with ISO and IEC
also participate in this preparation.
2) In the field of information technology, ISO and IEC have established a joint technical 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 formal decisions or agreements of IEC or 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 National Committees.
4) IEC, ISO or ISO/IEC Publications have the form of recommendations for international use and are accepted by
IEC and ISO National Committees in that sense. While all reasonable efforts are made to ensure that the
technical content of IEC, ISO or 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 National Committees undertake to apply IEC, ISO or
ISO/IEC Publications transparently 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 or IEC provide no marking procedure to indicate their approval and cannot be rendered responsible for any
equipment declared to be in conformity with an ISO/IEC Publication.
7) All users should ensure that they have the latest edition of this publication.
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 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-3-3 was prepared by subcommittee 25: Interconnection
of information technology equipment, of ISO/IEC joint technical committee 1: Information
technology.
This International Standard is a product family standard. It is not intended to be used as a
stand-alone standard.
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 title page.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 2.

14543-3-3 © ISO/IEC:2007(E) – 5 –
INTRODUCTION
The application interface layer is the layer between the application layer and the application. It
contains the communication relevant tasks of the application. It eases the communication task
of the application by offering a communication interface that abstracts from many application
layer details.
This International Standard allows single-processor and dual-processor device designs. A dual
processor device uses additional services to communicate via a serial External Message
Interface with the external user application running in the second processor.
The following clauses specify the client and server functioning and the communication interface
of the internal user application located in the Bus Access Unit (BAU).
The application interface layer contains the following objects and the access routines to them.
– Group objects: these can be accessed via Transport layer Service Access Points
(TSAPs) on multicast communication services; see the corresponding clause in
ISO/IEC 14543-3-2. Group objects may also be references to interface objects.
– Interface objects: these can be accessed via application services on point-to-point
connectionless and point-to-point connection-oriented communication modes. The
interface objects are divided into system interface objects and application interface
objects.
• System interface objects are
− the device object,
− the group address table object,
− the association table object, and
− the application object.
• System interface objects are relevant for network management as specified in
ISO/IEC 14543-3-4.
• Application interface objects are objects defined in the user application. They may be
defined by the internal or external user application, based on interface object structure
rules defined in this document. Application interface objects may also be referenced by
a group object reference.
The following clauses specify the data structures of each of the application interface layer
objects. Additionally, they define by which application services these objects are accessible.
Both the object client and object server functioning may be implemented by the external or the
internal application interface layer. It is recommended to locate the group communication
objects, the interface objects and the resource objects in the internal application interface
layer.
– 6 – 14543-3-3 © ISO/IEC:2007(E)
Currently, ISO/IEC 14543, Information technology – Home Electronic System (HES)
architecture, consists of the following parts:
Part 2-1: Introduction and device modularity
Part 3-1: Communication layers – Application layer for network based control of HES Class 1
Part 3-2: Communication layers – Transport, network and general parts of data link layer for
network based control of HES Class 1
Part 3-3: User process for network based control of HES Class 1
Part 3-4: System management – Management procedures for network based control of HES
Class 1
Part 3-5: Media and media dependent layers – Power line for network based control of HES
Class 1
Part 3-6: Media and media dependent layers – Twisted pair for network based control of
HES Class 1
Part 3-7: Media and media dependent layers – Radio frequency for network based control of
HES Class 1
Part 4: Home and building automation in a mixed-use building (technical report)
Part 5-1: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Core
ptotocol (under consideration)
Part 5-2: Intelligent grouping and resource sharing for HES Class 2 and Class 3 – Device
certification (under consideration)
Additional parts may be added later.

14543-3-3 © ISO/IEC:2007(E) – 7 –
INFORMATION TECHNOLOGY –
HOME ELECTRONIC SYSTEM (HES) ARCHITECTURE –

Part 3-3: User process for network based control of HES Class 1

1 Scope
This part of ISO/IEC 14543 specifies the structure and functioning of servers for the objects
which form the interface between the application layer and the application and management.
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 14543-3-1, Information technology – Home Electronic System (HES) architecture –
Part 3-1: Communication layers – Application layer for network based control of HES Class 1
ISO/IEC 14543-3-4, Information technology – Home Electronic System (HES) architecture –
Part 3-4: System Management – Management procedures for network based control of HES
Class 1
3 Terms, definitions and abbreviations
3.1 Terms and definitions
For the purposes of this document the terms and definitions given in ISO/IEC 14543-3-1 apply.
3.2 Abbreviations
ASAP
Application layer Service Access Point
BAU Bus Access Unit
EMI External Message Interface
HES Class 1 refers to simple control and command
HES Class 2 refers to Class 1 plus simple voice and stable picture transmission
HES Class 3 refers to Class 2 plus complex video transfers
TSAP Transport layer Service Access Point
4 Conformance
An entity of operational exchange conforming to this International Standard shall support the
group objects specified in clause 6.
The implementation of interface objects specified in clause 7 is optional.

– 8 – 14543-3-3 © ISO/IEC:2007(E)
5 Object models
This International Standard specifies two kinds of objects for operational exchanges.
a) Group objects
group objects shall be used to support the shared variable model.
b) Interface objects
interface objects shall be used to support the client/server model and, if they are
referenced by group objects, also the shared variable model of the group objects.
An application may use each kind of object at any time; see Figure 1.

Application
Application interface layer
Application
interface
objects
Group objects
Reference
Group object Interface
server object server
A-Interface
A-Group
object services
object services
Application layer
Figure 1 – User process model
6 Group object server
6.1 Overview
Group objects can be distributed to a number of devices. Each device may be transmitter and
receiver for group object values. More than one group object can exist in an end device and a
group object in a device may be assigned to one or more group addresses. Group objects of an
end device may belong to the same or to different groups. Each group shall have a network-
wide unique group address. The group address shall be mapped to a local group index (TSAP)
by the transport layer; the group index shall be unique for the communication services of the
device. The application layer shall map the group index by the association table to the group
reference ID (Application layer Service Access Point, ASAP) that shall be used to address the
group objects.
14543-3-3 © ISO/IEC:2007(E) – 9 –
6.2 General data structure group objects
6.2.1 Structure
In the sense of the previous clause a group object shall consist of three parts as shown in
Figure 2:
a) the group object description;
b) the object value;
c) the communication flags.
communication group object
group object description
flags value
object transmission configuration

type priority flags
Figure 2 – Data structure of group objects
6.2.2 Group object description
6.2.2.1 Object type
The following value-types shall be possible:
Table 1 – Group object types
Value length / Type Value-size
Unsigned Integer (1) 1 bit
Unsigned Integer (2) 2 bit
Unsigned Integer (3) 3 bit
Unsigned Integer (4) 4 bit
Unsigned Integer (5) 5 bit
Unsigned Integer (6) 6 bit
Unsigned Integer (7) 7 bit
Unsigned Integer (8) 1 octet
Unsigned Integer (16) 2 octets
Octet (3) 3 octets
Octet (4) 4 octets
Octet (6) 6 octets
Octet (8) 8 octets
Octet (10) 10 octets
Octet (14) 14 octets
Interface object reference 4 to 14 octets
Only group objects of the same type may be linked to one group, and for interface object
references the interface object type with the same instance number shall also be the same.
6.2.2.2 Transmission priority
The priority can only be “urgent”, “normal” or “low”. The transmission priority “system” shall not
be allowed for communication using group objects.

– 10 – 14543-3-3 © ISO/IEC:2007(E)
6.2.2.3 Configuration flags
The configuration flags shall include the static configuration of the group object, as follows:
a) read enable;
b) write enable;
c) transmit enable;
d) update enable;
e) communication enable.
If the “read enable” flag is set, the user process shall allow reading the group object value. The
user process shall thus react to an A_GroupValue_Read.ind service from the application layer
as specified in ISO/IEC 14543-3-1. If the “read enable” flag is clear, the user process shall
ignore this service for this group object.
If the “write enable” flag is set, the user process shall allow setting the group object value; the
user process shall thus react to an A_GroupValue_Write.ind service from the application layer
as specified in ISO/IEC 14543-3-1. If the “write enable” flag is clear, the user process shall
ignore this service for this group object.
If the “transmit enable” flag is set, the user process shall allow transmitting the group object
value. On request by the user application the user process shall thus pass an
A_GroupValue_Write.req service to the application layer as specified in ISO/IEC 14543-3-1. If
the “transmit enable” flag is clear, the user process shall ignore this request from the user
application.
If the “update enable” flag is set, the user process shall update the communication object value
on reception of an A_GroupValue_Read.con to that group object by setting the group object
value to the contained value. If the “update enable” flag is clear, the user process shall not
react on A_GroupValue_Read.res-services to that group object.
The “communication enable” flag shall take priority over the “read enable”, “write enable”,
“transmit enable” and “update enable” flags. If the “communication enable” flag is set, these
flags shall be evaluated as specified. If the “communication enable” flag is clear, these
configuration flags shall not be evaluated; instead, all services and requests shall be ignored.
6.2.3 Communication flags
The communication flags show the state of a group communication object. The following states
are possible:
a) update;
b) read-request;
c) write-request;
d) transmitting;
e) ok-error.
The “update” flag shall be set by the user process to indicate to the user application that it has
updated the group object value. The “update” flag shall be cleared by the user application.
The “read-request” flag shall be set by the user application to indicate that it wants to obtain an
update of its group object value. As a reaction,
...