Information technology -- Terminology for intelligent homes

ISO/IEC/TR 29108:2013(E) specifies the terminology recommended for future use in International Standards and other specifications for intelligent homes. In addition, it provides a collection of terms and definitions as already used and defined in relevant International Standards, Technical Specifications, Technical Reports and Recommendations developed by ISO, IEC, and ITU-T.

Technologies de l'informations -- Terminologie des maisons intelligentes

General Information

Status
Published
Publication Date
21-Mar-2013
Current Stage
6000 - International Standard under publication
Start Date
22-Mar-2013
Ref Project

Buy Standard

Technical report
ISO/IEC TR 29108:2013 - Information technology -- Terminology for intelligent homes
English language
71 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (sample)

ISO/IEC/TR 29108
Edition 1.0 2013-03
TECHNICAL
REPORT
Information technology – Terminology for intelligent homes
ISO/IEC/TR 29108:2013(E)
---------------------- Page: 1 ----------------------
THIS PUBLICATION IS COPYRIGHT PROTECTED
Copyright © 2013 ISO/IEC, Geneva, Switzerland

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.: +41 22 919 02 11
3, rue de Varembé Fax: +41 22 919 03 00
CH-1211 Geneva 20 info@iec.ch
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.
Useful links:

IEC publications search - www.iec.ch/searchpub Electropedia - www.electropedia.org

The advanced search enables you to find IEC publications The world's leading online dictionary of electronic and

by a variety of criteria (reference number, text, technical electrical terms containing more than 30 000 terms and

committee,…). definitions in English and French, with equivalent terms in

It also gives information on projects, replaced and additional languages. Also known as the International

withdrawn publications. Electrotechnical Vocabulary (IEV) on-line.

IEC Just Published - webstore.iec.ch/justpublished Customer Service Centre - webstore.iec.ch/csc

Stay up to date on all new IEC publications. Just Published If you wish to give us your feedback on this publication

details all new publications released. Available on-line and or need further assistance, please contact the

also once a month by email. Customer Service Centre: csc@iec.ch.
---------------------- Page: 2 ----------------------
ISO/IEC/TR 29108
Edition 1.0 2013-03
TECHNICAL
REPORT
Information technology – Terminology for intelligent homes
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
ICS 35.200 ISBN 978-2-83220-691-1

Warning! Make sure that you obtained this publication from an authorized distributor.

---------------------- Page: 3 ----------------------
– 2 – TR 29108 © ISO/IEC:2013(E)
CONTENTS

FOREWORD ........................................................................................................................... 3

INTRODUCTION ..................................................................................................................... 4

1 Scope ............................................................................................................................... 5

2 Structure .......................................................................................................................... 5

3 Terms, definitions and abbreviations ................................................................................ 5

3.1 Terms and definitions .............................................................................................. 5

3.2 Abbreviations ........................................................................................................ 70

Bibliography .......................................................................................................................... 73

Figure 1 – Individual address ................................................................................................ 19

Figure 2 – Group address ..................................................................................................... 26

---------------------- Page: 4 ----------------------
TR 29108 © ISO/IEC:2013(E) – 3 –
INFORMATION TECHNOLOGY –
TERMINOLOGY FOR INTELLIGENT HOMES
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 member body 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 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. 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.

5) In order to promote international uniformity, IEC 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 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 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 Technical Report, may be the subject of

patent rights. ISO and IEC shall not be held responsible for identifying any or all such patent rights.

The main task of ISO/IEC technical committees is to prepare International Standards.

However, a technical committee may propose the publication of a technical report when it has

collected data of a different kind from that which is normally published as an International

Standard, for example "state of the art".

ISO/IEC TR 29108, which is a technical report, has been prepared by subcommittee 25:

Interconnection of information technology equipment, of ISO/IEC joint technical committee 1:

Information technology. It is intended that future versions of this technical report will be

developed in collaboration with ITU-T.

This Technical Report 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.

---------------------- Page: 5 ----------------------
– 4 – TR 29108 © ISO/IEC:2013(E)
INTRODUCTION

ISO/IEC TR 29108 contains the recommended as well as other existing definitions of terms

used in standards and technical reports relevant to intelligent homes. Existing definitions use

the exact wording of the source and may thus be both formally incorrect as well as contain

spelling mistakes.

In addition, necessary information that is not in the SOURCE has been added in brackets.

Also Notes # to entry below the [SOURCE reference] are additions of this Technical Report.

---------------------- Page: 6 ----------------------
TR 29108 © ISO/IEC:2013(E) – 5 –
INFORMATION TECHNOLOGY –
TERMINOLOGY FOR INTELLIGENT HOMES
1 Scope

ISO/IEC TR 29108 specifies the terminology recommended for future use in International

Standards and other specifications for intelligent homes. In addition, it provides a collection of

terms and definitions as already used and defined in relevant International Standards,

Technical Specifications, Technical Reports and Recommendations developed by ISO, IEC,

and ITU-T.
2 Structure

The first definition of each term, i.e. the one with the number 3.1.n.1 is the definition

recommended by this Technical Report. This can either be one from an International Standard

or other specification, or one defined by this Technical Report. If more than one definition for

a term exists, they are ordered hierarchically, in decreasing order of preference. Note that a

definition may apply to a very specific environment, but not be preferred, since it is not

generic.

The source of the definition is indicated at the bottom of each entry, if applicable. If no source

is provided the term and definition is being defined by this Technical Report. Cited definitions

use the same wording as the source, so they may contain both formal and spelling errors. A

source given at the last, but one line of the definition is part of the citation.

The Bibliography at the end of the document consists of two parts. The first part lists

International Standards from which terms and definitions are cited in Clause 3 below. The

second part contains related International Standards and other specifications.
3 Terms, definitions and abbreviations
3.1 Terms and definitions

The following terms and definitions have been compiled in the field of intelligent homes for the

convenience of standards' writers and users.
3.1.1 Action
3.1.1.1
action

Command exposed by a service. Takes one or more input or output arguments. May have a

return value. For more information, see clauses on description and control (in
ISO/IEC 29341-1).
[SOURCE: ISO/IEC 29341-1:2011, definition in Clause 6]
3.1.2 Action primitive
3.1.2.1
action primitive

fundamental unit of software invocation that results in a single defined and observable state

change of the object on which it is invoked
[SOURCE: ISO/IEC 18012-2:2012, definition 3.1.1]
---------------------- Page: 7 ----------------------
– 6 – TR 29108 © ISO/IEC:2013(E)
3.1.3 Application
3.1.3.1
application
field of use of an HES
Note 1 to entry: An HES may support more than one application.
[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.2.1]
3.1.3.2
application
field of use of an HES. An HES may support more than one application
[SOURCE: ISO/IEC TR 15044:2000, definition 2.1]
3.1.3.3
application (in the sense of network application)
system, including its associated transmission method, which is supported by
telecommunications cabling
[SOURCE: ISO/IEC 11801:2002, definition 3.1.2]
[SOURCE: ISO/IEC 14543-3-1:2006, definition 3.1.1]
3.1.4 Application Data (ADATA)
3.1.4.1
application data
ADATA
data region for messages exchanged by communication middleware
Note 1 to entry: Maximum size is 256 bytes.

[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.1; ISO/IEC 14543-4-2:2008, definition

3.1.1]
3.1.5 Application Data Counter (ADC)
3.1.5.1
application data counter
ADC
indicates the size of the ADATA region
Note 1 to entry: The size is variable in 1-byte increments.

[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.2; ISO/IEC 14543-4-2:2008, definition

3.1.2]
3.1.6 Application entity
3.1.6.1
application entity

active element, within the application process, ambodying a set of capabilities which is

pertinent to OSI and which is defined for the application layer, that corresponds to a specific

application-entity type (without any extra capabilities being used)
[SOURCE: ISO/IEC 7498-1, 7.1.1.1]
[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.1.1]
---------------------- Page: 8 ----------------------
TR 29108 © ISO/IEC:2013(E) – 7 –
3.1.7 Application interoperability model
3.1.7.1
application interoperability model
AIM
application model specified this standard (in ISO/IEC 18012-2)
[SOURCE: ISO/IEC 18012-2:2012, definition 3.1.3]
3.1.8 Application model
3.1.8.1
application model

representation of the components, structure and interactions of a system focused on a

particular domain of use
[SOURCE: ISO/IEC 18012-2:2012, definition 3.1.2]
3.1.9 Application object
3.1.9.1
application object
HES object located within the HES device application process
3.1.9.2
application object
an HES object located within the HES device application process

[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.2.2; ISO/IEC TR 15044:2000, definition 2.2]

3.1.9.3
application object
AOJ

model of information to be disclosed to the network from information owned by the

communications processing block, or an access procedure model

Note 1 to entry: The information or control target owned by each device is specified as a property and the

operating method (setting, browsing) for this is specified as a service.
Note 2 to entry: AOJs are used when class or instance is not considered.
[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.3]
3.1.9.4
application object
AOJ

model of information to be disclosed to the network from information owned by the

communications processing block, or an access procedure model

Note 1 to entry: The information or control target owned by each device is specified as a property and the

operating method (setting, browsing) for this is specified as a service. AOJs are used when class or instance is not

considered.
[SOURCE: ISO/IEC 14543-4-2:2008, definition 3.1.3]
3.1.10 Application process
3.1.10.1
application process

element within an HES which performs the information processing for a particular application

---------------------- Page: 9 ----------------------
– 8 – TR 29108 © ISO/IEC:2013(E)
3.1.10.2
application process

element within an HES which performs the information processing for a particular application

[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.2.3; ISO/IEC TR 15044:2000, definition 2.3]

3.1.10.3
application process

element within a real open system which performs the information processing for a particular

application
[SOURCE: ISO/IEC 7498-1, 4.1.4]
[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.1.2]
3.1.11 Application program
3.1.11.1
application program

element within an installed system (i.e. in a device) which performs information processing for

a particular application and ensures the operations needed to execute the application

[SOURCE: ISO/IEC 14543-3-4:2007, definition 3.1.12]
3.1.12 Application Programming Interface (API)
3.1.12.1
application programming interface
API

boundary across which application software uses facilites of programming languages to

invoke services

Note 1 to entry: See ISO/IEC JTC 1 Standing Document "Guidelines for API Standardization" for a complete

discussion of application programming interfaces.
[SOURCE: ISO/IEC 18012-2:2012, definition 3.1.4]
3.1.12.2
API
application programming interface

collection of invocation methods and associated parameters used by one piece of software to

request actions from another piece of software
[SOURCE: ISO/IEC 18012-1:2004, definition 3.1.1]
3.1.12.3
application programming interface
API
assembly of interface functions for middleware
Note 1 to entry: API makes it easy to operate middleware for designers.

[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.4; ISO/IEC 14543-4-2:2008, definition

3.1.4]
---------------------- Page: 10 ----------------------
TR 29108 © ISO/IEC:2013(E) – 9 –
3.1.13 Application Property Code (APC)
3.1.13.1
application property code
APC
code value related to application property
[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.5]
3.1.14 Application Property value Data (APD)
3.1.14.1
application property value data
APD

data value related to application property code (APC), such as status notification or specific

setting and control by an application service code (ASC)

Note 1 to entry: Detailed specifications are provided for the size, code value, etc. of the APD for each APC.

[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.6]
3.1.14.2
application property value data
APD

is a data value related to application property code (APC), such as a status notification or

specific setting and control by an application service code (ASC)

Note 1 to entry: Detailed specifications are provided for the size, code value, etc. of the APD for each APC.

[SOURCE: ISO/IEC 14543-4-2:2008, definition 3.1.5]
3.1.15 Application protocol
3.1.15.1
application protocol

standardized protocol for the exchange of information between application processes in an

HES; it is transported without interpretation by the home network resources

[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.2.4; ISO/IEC TR 15044:2000, definition 2.4]

3.1.16 Application Service Code (ASC)
3.1.16.1
application service code
ASC
code value related to application service
[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.7]
3.1.17 Architecture
3.1.17.1
architecture
conceptual structure of a system

Note 1 to entry: A system may consist of several interacting subsystems, each with its own architecture.

3.1.17.2
architecture
conceptual structure of systems that are to communicate with each another
[SOURCE: ISO/IEC TR 15044:2000, definition 2.5]
---------------------- Page: 11 ----------------------
– 10 – TR 29108 © ISO/IEC:2013(E)
3.1.17.3
architecture
specific configuration of hardware and software elements in a system
[SOURCE: IEC 61508-4:2010, definition 3.3.4]
[SOURCE: ISO/IEC 14762:2009, definition 3.1.1]
3.1.18 Area address
3.1.18.1
area address

part of the individual address that specifies the area in which the device is mounted

[SOURCE: ISO/IEC 14543-3-2:2006, definition 3.1.3]
3.1.19 Argument
3.1.19.1
argument

Parameter for action exposed by a service. May be in xor out. For more information, see

clauses on Description and Control (in ISO/IEC 29341-1).
[SOURCE: ISO/IEC 29341-1:2011, definition in Clause 6]
3.1.20 Authentication
3.1.20.1
authentication

means for certifying that the entity sending a message is what or who it purports to be and

confirmation that the message is identical to that which was sent
[SOURCE: ISO/IEC 14762:2009, definition 3.1.2]
3.1.21 Authorization
3.1.21.1
authorization

mechanism to ensure that the entity or person accessing information, functions or services

has the authority to do so
[SOURCE: ISO/IEC 14762:2009, definition 3.1.3]
3.1.22 Bridge
3.1.22.1
bridge
interface between dissimilar lower layer networks

Note 1 to entry: A bridge may provide services at layer 1 (physical layer) or layer 2 (data link layer).

[SOURCE: ISO/IEC 15045-2:2012, definition 3.1.2]
3.1.22.2
bridge

functional unit interconnecting two home network systems that use the same network layer

protocol but where there may be some differences in the link layer protocol
[SOURCE: ISO/IEC TR 15044:2000, definition 2.6]
---------------------- Page: 12 ----------------------
TR 29108 © ISO/IEC:2013(E) – 11 –
3.1.23 Brown goods
3.1.23.1
brown goods

A/V devices that are mainly used for entertainment, for example, television or DVD recorder

[SOURCE: ISO/IEC 24767-1:2008, definition 2.1.1]
3.1.24 Bus
3.1.24.1
bus
common or shared communication path or highway

Note 1 to entry: A means of interconnecting devices under a single administration, such as a LAN comprising

devices sharing a common set of pathways

Note 2 to entry: A distinction may be drawn between “logical” and “physical” buses when bus topologies are

considered.
[SOURCE: ISO/IEC 15045-2:2012, definition 3.1.3]
3.1.25 Bus access unit (BAU)
3.1.25.1
bus access unit
BAU
contains all protocol layers plus the optional internal user application
[SOURCE: ISO/IEC 14543-3-4:2007, definition 3.1.2]
3.1.26 Centralised device group
3.1.26.1
centralised device group
set of IGRS Devices with one IGRS device acting as the master

Note 1 to entry: The master is responsible for managing the setup, for dismissing a device group, and for

processing a join request from other devices.

Note 2 to entry: The master device and other IGRS devices in such a device group form a centralised or master-

slave relationship.

[SOURCE: ISO/IEC 14543-5-1:2010, definition 3.1.1; ISO/IEC 14543-5-4:2010, definition 3.2]

3.1.27 Classes of home control systems
3.1.27.1
classes of home control systems
characterization of home control systems based on their transport capabilities
[SOURCE: ISO/IEC TR 15044:2000, definition 2.7]
3.1.28 Client identifier
3.1.28.1
client identifier

unique identifier associated with a Client on an IGRS device to which that Client belongs

[SOURCE: ISO/IEC 14543-5-1:2010, definition 3.1.2; ISO/IEC 14543-5-4:2010, definition 3.3]

---------------------- Page: 13 ----------------------
– 12 – TR 29108 © ISO/IEC:2013(E)
3.1.29 Co-existence
3.1.29.1
co-existence

two or more home networking systems co-exist when they can be used and operate without

interfering with one-another
[SOURCE: ISO/IEC 18012-2:2012, definition 3.1.7]
3.1.29.2
co-existence
two or more networks within premises that do not interfere with one another
[SOURCE: ISO/IEC 18012-1:2004, definition 3.1.2]
3.1.29.3
co-existence
no interference between different pieces of equipment on the premises

Specifically, the operation of one RG does not interfere with the operation of another RG

[SOURCE: ISO/IEC 15045-1:2004, definition 3.1.1]
3.1.30 Common Interoperability Framework (CIF)
3.1.30.1
common interoperability framework
CIF

abstract intermediate language expressions for tranlating HAN or WAN-specifid messages

Note 1 to entry: A common interoperability framework includes
a) an HES-AIL (Abstract Intermediate Language), and

b) a set of network-specific Generic Interworking Function (GIWF) processes to express (i.e., translate) any

message to or from any specific HAN or WAN message.
[SOURCE: ISO/IEC 15045-2:2012, definition 3.1.4]
3.1.31 Communication middleware block
3.1.31.1
communication middleware block

this middleware is arranged from data link layer to application layer and performs

communications processing according to the protocol specified in ISO/IEC 14543-4-1 and

ISO/IEC 14543-4-2

Note 1 to entry: The major features of ISO/IEC 14543-4 are implemented by communications middleware.

[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.8]
3.1.32 Communication mode
3.1.32.1
communication mode
mode describing the relationship between communication points upon which the

communication relies: one-to-many connectionless (multicast), one-to-all connectionless

(broadcast), one-to-one connectionless, one-to-one connection-oriented
[SOURCE: ISO/IEC 14543-3-4:2007, definition 3.1.9]
---------------------- Page: 14 ----------------------
TR 29108 © ISO/IEC:2013(E) – 13 –
3.1.33 Communication processing block
3.1.33.1
communication processing block

one processing block for the communications middleware; this block performs communication

protocol processing to facilitate remote device control/monitoring processing for application

software, stores information for the above and controls various information on the self-device

as well as other device statuses
[SOURCE: ISO/IEC 14543-4-1:2008, definition 3.1.9]
3.1.34 Communications middleware block
3.1.34.1
communications middleware block

this middleware is arranged from data link layer to application layer and performs

communications processing according to ISO/IEC 14543-4

Note 1 to entry: The major features of ISO/IEC 14543-4 are implemented by communications middleware.

[SOURCE: ISO/IEC 14543-4-2:2008, definition 3.1.6]
3.1.35 Communications processing block
3.1.35.1
communications processing block

one processing block for the communications middleware; this block performs communication

protocol processing to facilitate remote device control/monitoring processing for application

software, stores information for the above and controls various information on the self-device

as well as other device statuses
[SOURCE: ISO/IEC 14543-4-2:2008, definition 3.1.7]
3.1.36 Compatibility
3.1.36.1
compatibility

ability of two or more networks within premises to be mutually tolerant and not interfere with

one another

Note 1 to entry: The networks as co-existent, but they not necessarily interoperable.

[SOURCE: ISO/IEC 15045-2:2012, definition 3.1.5]
3.1.37 Component
3.1.37.1
component
logical subunit of a larger, encompassing concept
[SOURCE: ISO/IEC 18012-2:2012, definition 3.1.8]
3.1.37.2
component
logical subunit of a larger, encompassing concept

Note 1 to entry: For example, the concept of Interoperability is subdivided into constituent components such as

safety, management, and operation. These constituent components are further subdivided within their respective

sections. In the context of the HES-gateway, the term component is also used to refer to logical subunits of system

architecture concepts, such as the components of a networking implementation (e.g., addressing)

[SOURCE: ISO/IEC 15045-2:2012, definition 3.1.6]
---------------------- Page: 15 ----------------------
– 14 – TR 29108 © ISO/IEC:2013(E)
3.1.37.3
component
logical subunit of a larger, encompassing concept

Note 1 to entry: The concept of interoperability is broken down into constituent components such as safety,

management and operation. These constituent components are further broken down within their respective

sections. The term component is also used to refer to logical subunits of system architecture concepts, such as the

components of a networking implementation (for example, addressing).
[SOURCE: ISO/IEC 18012-1:2004, definition 3.1.3]
3.1.38 Concurrent events
3.1.38.1
concurrent events

two or more events queued for processing in the interval between any two scheduled input

processing or output processing operations of an application object
[SOURCE: ISO/IEC 18012-2:2012, definition 3.1.9]
3.1.39 Confidentiality
3.1.39.1
confidentiality

property that information is not made available or disclosed to unauthorized individuals,

entities or processes

[SOURCE: ISO/IEC 24767-1:2008, definition 2.1.2; ISO/IEC 24767-2:2009, definition 3.1.1]

3.1.40 Connection
3.1.40.1
connection

association established between functional units for data transmission across a network (or

part of a network) for the purpose of communication between the units; the association is

explicitly established at some point in time and exists until explicitly ended

Note 1 to entry: Data transmission includes, in this context, audio, video and other information in either analogue

or digital form.
[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.2.5]
3.1.40.2
connection

association established between two peer entities across a network (or part of a network) for

the purpose of communication between the entities. The association is explicitly established

at some point in time, and exists until explicitly ended
[SOURCE: ISO/IEC TR 15044:2000, definition 2.8]
3.1.41 Connection-mode service
3.1.41.1
connection-mode service

service providing communication between two entities within the context of a connection

established between the entities
[SOURCE: ISO/IEC TR 15044:2000, definition 2.9]
---------------------- Page: 16 ----------------------
TR 29108 © ISO/IEC:2013(E) – 15 –
3.1.42 Connection-mode transmission
3.1.42.1
connection-mode transmission
(N)-data-transmission in the context of an (N)-connection
[SOURCE: ISO/IEC 7498-1, 5.3.1.17]
[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.1.3]
3.1.43 Connectionless-mode service
3.1.43.1
connectionless-mode service

service providing communication between two entities not within the context of a connection

established between the entities
[SOURCE: ISO/IEC TR 15044:2000, definition 2.10]
3.1.44 Connectionless-mode transmission
3.1.44.1
connectionless-mode transmission

(N)-data-transmission not in the context of an (N)-connection and not required to maintain any

logical relationship between (N)-service-data-units
[SOURCE: ISO/IEC 7498-1, 5.3.1.18]
[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.1.4]
3.1.45 Control channel
3.1.45.1
control channel

communication channel that is established between two or more entities for the primary

purpose of exchange of HES control and monitoring messages
[SOURCE: ISO/IEC 14543-2-1:2006, definition 3.2.6]
3.1.45.2
control channel

communication channel that is established between two or more entities for the primary

purpose of exchange of HES control
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.