Household appliances interworking -- Part 1: Functional specification

This European Standard focuses on interworking of household appliances and describes the necessary control and monitoring. It defines a set of functions of household and similar electrical appliances which are connected together and to other devices by a network in the home. This European Standard does not deal with safety requirements.

Geräte für den Hausgebrauch - Interworking -- Teil 1: Funktionsspezifikation

Diese Europäische Norm befasst sich mit dem Interworking von Haushaltsgeräten und beschreibt die dafür notwendigen Steuerungs-, Regelungs- und Überwachungsmaßnahmen. Sie legt eine Reihe von Funktionen fest, über die Haushaltsgeräte und ähnliche Elektrogeräte verfügen müssen, die über ein hausinternes Netz¬werk sowohl untereinander als auch mit anderen Geräten zusammengeschaltet werden. Diese Europäische Norm enthält keine Sicherheitsanforderungen.

Interfonctionnement des appareils électrodomestiques -- Partie 1: Spécifications fonctionnelles

La présente Norme Européenne est axée sur l'interfonctionnement des appareils domestiques et décrit la commande et la surveillance nécessaires à cet effet. Elle définit un ensemble de fonctions des appareils électriques domestiques et appareils similaires qui sont reliés entre eux et à d'autres dispositifs par un réseau dans le domicile. La présente Norme Européenne ne traite pas des exigences relatives à la sécurité.

Medsebojno delovanje gospodinjskih aparatov - 1. del: Funkcionalne specifikacije

Ta evropski standard se osredotoča na medsebojno delovanje gospodinjskih aparatov in opisuje potrebni nadzor in spremljanje. Opredeljuje set funkcij gospodinjskih in podobnih električnih aparatov, ki se povezujejo med sabo in z drugimi napravami v domačem omrežju. Ta evropski standard ne obravnava varnostnih zahtev.

General Information

Status
Published
Publication Date
30-Nov-2009
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
09-Nov-2009
Due Date
14-Jan-2010
Completion Date
01-Dec-2009
Standard
SIST EN 50523-1:2010
English language
78 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)


SLOVENSKI STANDARD
01-januar-2010
Medsebojno delovanje gospodinjskih aparatov - 1. del: Funkcionalne specifikacije
Household appliances interworking -- Part 1: Functional specification
Geräte für den Hausgebrauch - Interworking -- Teil 1: Funktionsspezifikation
Interfonctionnement des appareils électrodomestiques -- Partie 1: Spécifications
fonctionnelles
Ta slovenski standard je istoveten z: EN 50523-1:2009
ICS:
97.120 Avtomatske krmilne naprave Automatic controls for
za dom household use
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD
EN 50523-1
NORME EUROPÉENNE
July 2009
EUROPÄISCHE NORM
ICS 97.120
English version
Household appliances interworking -
Part 1: Functional specification

Interfonctionnement  Geräte für den Hausgebrauch -
des appareils électrodomestiques - Interworking -
Partie 1: Spécifications fonctionnelles Teil 1: Funktionsspezifikation

This European Standard was approved by CENELEC on 2009-06-01. CENELEC members are bound to comply
with the CEN/CENELEC Internal Regulations which stipulate the conditions for giving this European Standard
the status of a national standard without any alteration.

Up-to-date lists and bibliographical references concerning such national standards may be obtained on
application to the Central Secretariat or to any CENELEC member.

This European Standard exists in three official versions (English, French, German). A version in any other
language made by translation under the responsibility of a CENELEC member into its own language and notified
to the Central Secretariat has the same status as the official versions.

CENELEC members are the national electrotechnical committees of Austria, Belgium, Bulgaria, Cyprus, the
Czech Republic, Denmark, Estonia, Finland, France, Germany, Greece, Hungary, Iceland, Ireland, Italy, Latvia,
Lithuania, Luxembourg, Malta, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Slovenia, Spain,
Sweden, Switzerland and the United Kingdom.

CENELEC
European Committee for Electrotechnical Standardization
Comité Européen de Normalisation Electrotechnique
Europäisches Komitee für Elektrotechnische Normung

Central Secretariat: Avenue Marnix 17, B - 1000 Brussels

© 2009 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.
Ref. No. EN 50523-1:2009 E
Foreword
This European Standard was prepared by the WG 7 of Technical Committee CENELEC TC 59X, Consumer
information related to household electrical appliances.
The text of the draft was submitted to the formal vote and was approved by CENELEC as EN 50523-1 on
2009-06-01.
The following dates were fixed:
– latest date by which the EN has to be implemented

at national level by publication of an identical

national standard or by endorsement
(dop) 2010-06-01
– latest date by which the national standards conflicting

with the EN have to be withdrawn
(dow) 2012-06-01
The Working Group CLC/TC 59X/WG 7, Smart house, was initiated by CECED and installed by the decision
of the CLC/TC 59 meeting on 2004-09-14/15.
This European Standard has been based on documents developed and provided by the CECED
Convergence Working Group.
This Part 1 of EN 50523 defines the interoperability requirements for installation, control and monitoring of
household appliances.
__________
– 3 – EN 50523-1:2009
Contents
Introduction . 6
1 Scope . 7
2 Terms, definitions and abbreviations . 7
2.1 Terms and definitions . 7
2.2 Abbreviations . 9
3 Installation of a system . 10
3.1 Definitions . 10
3.2 Rationale for Installation in WG Appliances . 10
3.3 Key Installation Events and related User Functions . 12
3.4 Guidelines on Installation Procedures . 14
4 Household Appliances Application Domain . 18
4.1 Application Scenario . 18
4.2 Access Rights for Control Modes . 19
4.3 Types of Appliances . 19
5 Household Appliances Interworking . 20
5.1 Concepts and Rules for Interworking . 20
5.2 Functional Blocks Specification . 36
5.3 Network Management Functions . 62
5.4 Appliance Description . 62
Annex A (informative) Examples of Appliances State Diagrams . 64
A.1 Introduction . 64
A.2 Washing Machine State Diagram . 65
A.3 Tumble Dryer State Diagram . 66
A.4 Dishwasher State Diagram . 67
A.5 Microwave Oven State Diagram . 68
A.6 Electric Oven State Diagram . 69
A.7 Gas Cooktop State Diagram . 70
A.8 Gas Oven State Diagram . 71
A.9 Refrigerator State Diagram . 72
A.10 Freezer State Diagram . 72
A.11 Winecabinet State Diagram . 73
A.12 Refrigerator-Freezer State Diagram. 73
A.13 Hobs and Induction Hobs State Diagram . 74
A.14 Hood State Diagram . 75
A.15 Air conditioner State Diagram . 75
A.16 Instantaneous Water Heater State Diagram . 77
A.17 Storage Water Heater State Diagram . 77
Bibliography . 78

Figures
Figure 1 – Dependencies of interworking . 6
Figure 2 – Expected Interactions during Installation . 11
Figure 3 – Interactions during Installation . 17
Figure 4 – Interactions upon Switch On . 17
Figure 5 – Example of Household Appliances Installation System . 18
Figure 6 – Functional Block Structure of Household Appliance . 22
Figure 7 – Graphic Shapes for Profile Items . 30
Figure 8 – Elements involved in a profile . 30
Figure 9 – Graphic Shade / Letter Notation . 31
Figure 10 – Generic State Diagram . 44

Figure A.1 – Washing Machine State Diagram . 65
Figure A.2 – Tumble Dryer State Diagram . 66
Figure A.3 – Dish Washer State Diagram . 67
Figure A.4 – Microwave Oven State Diagram . 68
Figure A.5 – Electric Oven State Diagram . 69
Figure A.6 – Gas Cooktop State Diagram. 70
Figure A.7 – Gas Oven State Diagram . 71
Figure A.8 – Refrigerator State Diagram. 72
Figure A.9 – Freezer State Diagram . 72
Figure A.10 – Winecabinet State Diagram . 73
Figure A.11 – Refrigerator-Freezer State Diagram . 73
Figure A.12 – Hobs State Diagram . 74
Figure A.13 – Hood State Diagram . 75
Figure A.14 – Air Conditioner State Diagram . 76
Figure A.15 – Instantaneous Water Heater State Diagram . 77
Figure A.16 – Storage Water Heater State Diagram . 77

Tables
Table 1 – Abbreviations . 9
Table 2 – Key Installation Events . 13
Table 3 – User functions associated with Key installation events . 13
Table 4 – Installation Functions . 15
Table 5 – Installation functions involved in User Functions . 16
Table 6 – Application Interworking Concepts . 20
Table 7 – Primitives . 23
Table 8 – Addressing . 23
Table 9 – Possible Combinations of Primitives and Addressing . 24
Table 10 – Allowed data in case of no use of OID Fields . 24
Table 11 – Allowed data in case of use of OID Fields . 25
Table 12 – Application errors . 25
Table 13 – Reaction on Application errors . 25
Table 14 – Profile Items . 27
Table 15 – Application interworking rules . 28
Table 16 – EXECUTE COMMAND MIDs . 38
Table 17 – Execution of a Command MID Commands . 39
Table 18 – MID Flow for MID “Execution of a Command” . 39
Table 19 – MID Flow for other EXECUTE COMMAND MID . 40
Table 20 – MID Flow upon operation not in conformance with appliance remote control status . 40
Table 21 – MID Flow upon operation not in conformance with appliance state machine . 40
Table 22 – MID Flow upon use of invalid Application Data . 41
Table 23 – MID Flow upon no response received from the appliance for MID “Execution of a Command” . 41
Table 24 – MID Flow upon no response from the appliance for other EXECUTE COMMAND MIDs. 41
Table 25 – EXECUTE COMMAND MIDs Profile . 42
Table 26 – Execution of a Command MID Profile . 42
Table 27 – Execution of a Command MID Enabling Profile . 43

– 5 – EN 50523-1:2009
Table 28 – EXECUTE COMMAND MIDs Enabling Profile . 43
Table 29 – SIGNAL STATE MIDs . 45
Table 30 – Device Status MID States . 46
Table 31 – MID Flow for SIGNAL STATUS MIDs without data Fields. 47
Table 32 – MID Flow for SIGNAL STATUS MIDs with data Fields. 47
Table 33 – MID Flow for SIGNAL STATUS MIDs upon use of invalid data Fields . 47
Table 34 – MID Flow upon no message received from the appliance . 48
Table 35 – SIGNAL STATE MID Profiles . 48
Table 36 – SIGNAL STATE State Profiles . 49
Table 37 – SIGNAL EVENT MIDs . 50
Table 38 – MID Flow for SIGNAL EVENT MID . 51
Table 39 – MID Flow for SIGNAL EVENT MID “Normal Event” . 51
Table 40 – MID Flow for SIGNAL EVENT MID “Normal Event” with value “Wrong data” . 51
Table 41 – MID Flow for SIGNAL EVENT MID “Application Error” . 51
Table 42 – SIGNAL EVENT MID Profiles . 52
Table 43 – Normal Event MID Events Profile . 52
Table 44 – IDENTIFY PRODUCT MIDs . 53
Table 45 – MID Flow for Basic Identification MID . 53
Table 46 – MID Flow for Extended Identification MID . 54
Table 47 – MID Flow for IDENTIFY PRODUCT MIDs upon use of invalid data . 54
Table 48 – MID Flow upon no message received from the appliance . 54
Table 49 – IDENTIFY PRODUCT MID Profiles . 54
Table 50 – COLLECT DIAGNOSIS DATA MIDs . 55
Table 51 – MID Flow for Diagnosis Data MID . 56
Table 52 – MID Flow for Diagnosis Data MID . 56
Table 53 – MID Flow for Diagnosis Data MID . 56
Table 54 – MID Flow for Diagnosis Operation MID . 57
Table 55 – MID Flow for Diagnosis Operation MID . 57
Table 56 – COLLECT DIAGNOSIS DATA MID Profiles . 57
Table 57 – MANAGE TIME MIDS . 58
Table 58 – MID Flow for Time MID . 59
Table 59 – MID Flow for Time MID . 59
Table 60 – MID Flow for Time MID . 59
Table 61 – MID Flow for Date MID . 59
Table 62 – MID Flow for Date MID . 59
Table 63 – MANAGE TIME MID Profiles . 60
Table 64 – MID Flow for Application Error MID with error code “Invalid OID” . 60
Table 65 – MID Flow for Application Error MID with error code “Not implemented Operation” . 60
Table 66 – MID Flow for Application Error MID with error code “Not implemented Operation” . 61
Table 67 – MID Flow for Application Error MID with error code “Invalid Field”. 61
Table 68 – MID Flow for Application Error MID with error code “Invalid Data” . 61
Table 69 – MID Flow for Application Error MID with error code “Invalid Transition” . 61
Table 70 – MID Flow for Application Error MID with error code “Command Refused” . 62

Introduction
The objective of this European Standard is to specify how sets of products from multiple manufacturers are
able to interoperate and be installed with or without the use of a special tool, in the most automatic manner.
By meeting this standard, future household appliances will be able to enjoy a significantly larger market.
Figure 1 shows what it takes to obtain interworking between household appliances:
• the Household Appliances Interworking standard. It is highly independent of the underlying protocol;
• a protocol for communication between devices in the home;
• a mapping scheme from the Household Appliances Interworking standard to each selected protocol.
EN 50523-1 Functional specification
EN50XXX-1 Functional specification
Household Appliances
Household Appliances
Interworking Standard
Interworking Standard
EN 50523-2 Data structures
EN50XXX-2 Data structures
Mapping to protocol
Mapping to protocol Protocol Mapping specification
Protocol Mapping specification
Protocol Protocol specification
Protocol Protocol specification

Figure 1 – Dependencies of interworking
EN 50523-1 defines the functionality required for appliances to ensure interoperability.
EN 50523-2 defines the data structures used to implement the interoperable functionality.
The Protocol Mapping specification is a document that describes the mapping of the defined interoperable
functionality in terms of a selected protocol that satisfies the requirements of EN 50523-1.
The Protocol specification defines a communication protocol suitable for communication between devices in
the home.
– 7 – EN 50523-1:2009
1 Scope
This European Standard focuses on interworking of household appliances and describes the necessary
control and monitoring. It defines a set of functions of household and similar electrical appliances which are
connected together and to other devices by a network in the home.
This European Standard does not deal with safety requirements.
2 Terms, definitions and abbreviations
2.1 Terms and definitions
For the purposes of this document, the following terms and definitions apply.
2.1.1
domain address
identification of a logical network on an open network such as power-line. Domain addresses are used in a
frame to insulate it from neighbouring networks
2.1.2
house address
see definition 2.1.1 for domain address
2.1.3
network address
identification of a device in a network
2.1.4
fixed addressing scheme
fixed addressing schemes are used when the network address is a unique identification assigned through an
agreement between manufacturers so that no two communicating devices have the same identification,
hence the same address
2.1.5
communication link
logical application link between two devices exchanging messages
2.1.6
installation
installation of all networked devices within a given home unit
2.1.7
configuration data
set of data including network protocol data (domain address and network address) and communication link
data
2.1.8
message
application message
2.1.9
local control
direct control of a device through its panel

2.1.10
remote control
control of device through a network
2.1.11
indoor remote control
control of device from a device connected to the home network
2.1.12
outdoor remote control
control of device from a device connected to a residential gateway itself connected to the home network
2.1.13
enable / disable remote control
authorisation to control a device through a network
2.1.14
Functional Block
logical grouping of device functions. Consists of one or more functions that belong together and that cannot
be separated across two devices. A Functional Block has a well-defined black-box behaviour
2.1.15
wet white goods
washing machine, dish washer, tumble dryer
2.1.16
hot white goods
oven, hobs, hood
2.1.17
cold white goods
refrigerator, freezer, refrigerator-freezer, winecabinet
2.1.18
air conditioner
this document refers to HVAC mobile devices which can be directly installed by the consumer
2.1.19
water heater
storage water heater (boiler) or instantaneous water heater
2.1.20
short time
term used to identify short-length time period in messaging and installation procedures. Equal to 5 s
2.1.21
medium time
term used to identify medium-length time period in messaging and installation procedures. Equal to 30 s
2.1.22
long time
term used to identify long-length time period in messaging and installation procedures. More than 30 s
2.1.23
home controller
home controller is a controller providing the capability for remote control on the household appliances

– 9 – EN 50523-1:2009
2.1.24
residential gateway
residential gateway is a home controller providing also internet access. It usually provides also the capability
for remote control on the household appliances from networks outside the home. Also referred as gateway in
this document
2.2 Abbreviations
For the purposes of this document, the abbreviations included in Table 1 apply.
Table 1 – Abbreviations
AC HVAC mobile device Air Conditioner
DW Dishwasher
FB Functional Block
FR Refrigerator-Freezer
FZ Freezer
CB Combi
GO Gas Oven
GT Gas Cooktop
HB Hobs
HBES Home and Building Electronic Systems
HD Hood
HVAC Heating, Ventilation, Air Conditioning
IH Induction Hobs
MID Message Interaction Descriptor
MW Microwave Oven
OID [Communication] Object Identifier
OV Electric Oven
RE Refrigerator
RG Range Cooker
ST Steam Oven
TD Tumble Dryer
WC Winecabinet
WD Washer Dryer
WG White Good, appliance, white good appliance, household appliance
WHI Instantaneous Water Heater
WHS Storage Water Heater
WM Washing Machine
3 Installation of a system
3.1 Definitions
3.1.1 Phases of Installation
Installation of WG appliances with home networking capability consists of two main phases:
• initialising specific network protocol data:
- house address or domain address. This value is used on open media (e.g. power-line or RF) to
recognise network messages within the same home unit. It is necessary to make sure appliances do
not receive messages coming from different homes;
- network address of the appliance being installed. A network address serves as a "unique" identifier
for an appliance on a network. Appliances can determine the addresses of other appliances on the
network and use these addresses to send messages to each other;
• initialising communication links data, basically consisting of the network address of remote devices.
3.1.2 Plug & Play Installation
An installation which is fully automatic, i.e. which does not require user intervention is said to Plug & Play.
3.1.3 Plug, Touch & Play Installation
An installation, which is based on a limited sequence of simple user actions (i.e. Plug, Touch & Play).
3.2 Rationale for Installation in WG Appliances
3.2.1 Installation Approach for Household Appliances
In general, it is expected that WG appliances installation will be simple, protected and secure. The installation
procedures should be such that the user without the intervention of a specialised installer can perform it. In
particular, it could be either fully automatic (i.e. Plug & Play), or explicitly started and handled in a simple way
by the user, for example using a combination of buttons to start the procedure and relying on some LED
feedback (i.e. Plug, Touch & Play).
The limited sequence of user actions will typically be used for two purposes:
• getting the domain address. To this end, a touch sequence or another interaction will be typically
available to the user. The objective of the touch sequence is to direct another appliance to provide the
domain address information. In principle any already installed appliance can provide this information. In
practice, a dedicated appliance such as a gateway will be used for this purpose;
• handling the case of more than one WG appliance of the same type in the same home (e.g. two washing
machines). When such a case happens, there is a need to distinguish the appliances from a networking
point of view, in order to allow a home controller to access individually. This function is called "Instance
Identification". To this end, a touch sequence will be typically available to the user or another mechanism
in order to indicate it.
The figure below shows the interactions which are expected during installation. To achieve installation, the
appliance is interacting with another cooperating device. It will be involved in four phases, shown in
rectangles:
1) getting the domain address;
2) automatic installation phase;
3) optional instance identification;
4) providing installation feedback.

– 11 – EN 50523-1:2009
CoopCooperateratiinngg
AApplppliiancancee
DeviDeviccee (s (s))
DomDomaaiinn DomDomaaiinn
AAddresddresss AAddresddresss
ActActiioonn
ActActiioonn
AuAutotommaatitic c
AuAutotommaatitic c
PPhashasee
PPhashasee
IInnssttancancee IInnssttancancee
IIdentdentiiffiiccatatiioonn IIdentdentiiffiiccatatiioonn
ActActiioonn ActActiioonn
InInstastallallatiotionn
FFeedeedbacbackk
Figure 2 – Expected Interactions during Installation
The implementation of these four phases is completely open to the manufacturer. It is recommended that
• the sequence of actions to get the domain address should conform to the related protocol (interaction 1
in Figure 2),
• the automatic part should conform to the related protocol (interaction 2 in Figure 2). Note that the figure
was simplified as the automatic procedure could also take place before and after the sequence of
actions,
• the section of actions to implement instance identification should conform to the related protocol
(interaction 3 in Figure 2),
• the semantics of the feedback display should conform to the semantics of the installation protocol.
Therefore, it is expected that in practice there will still be many different approaches used for installation:
• the way to accomplish the installation actions at the level of the appliance could change from one
appliance to another, as long as the objective of such actions and the related protocol are the same (e.g.
a different combination of touch buttons is used);
• the actions to take at the level of other devices could be very different. They could involve different
devices from one installation to another (e.g. a specific controlling device with a user interface, a
gateway with specific installation buttons, a specific temporary tool), as long as the achieved objective
and the involved protocol are the same. For instance, it is possible that within the home system an
Installer device can be used to supervise installation and operations of other appliances. This specific
device could then be responsible for domain address provision, for the handling of multiple appliances of
the same kind (for example two washing machines on the same system). It could further support some
routine to verify that a new appliance is not installed on different or wrong environments (for example an
appliance being installed on the neighbour system).

Consequently, even though user intervention could be different for each manufacturer, it should use the same
network management protocol. This will ensure that interoperability can be insured.
3.2.2 Constraints
It is expected that a number of constraints related to installation procedures will be typically met in order to
put Household Appliances with networking capability on the market.
• Appliances with networking capability should also work even when they are used as autonomous system
without communication during their lifetime. The transition from and to autonomous modes must be
transparent to the user and should not require user interventions.
• Installation procedures
- should not depend on specific communication technology aspects,
- should be clearly presented (for instance in the case of combination of buttons),
- should allow the manufacturer to be free in the choice in their implementation,
- should support domain address acquisition. Without this capability, a filter separating
1)
communication would be needed in each home ,
- should give a chance to every appliance to be linked,
- should have a duration that is minimised,
- should take into account appliances that may be switched off (such as washing machines).
• User interfaces for installation procedures
- should be easily accessible,
- should have minimised costs. As an example, a solution based on one push button and one LED
seems to be correct from the point of view of the price.
• Regular checking of communication links integrity is expected in order to maintain consistent
configuration data upon events such as appliance removal, switch on or communication failure (note that
it is not obvious to distinguish such events). This point is particularly difficult because it is application
related and therefore seems to be difficult to standardise.
3.3 Key Installation Events and related User Functions
Household Appliance installation procedures shall follow a common scenario and common rules. More
precisely, the procedures shall be described through the same list of key events concerning the whole
installation. Each key event shall be associated with user functions.
The following table defines the key events concerning the whole installation.

1)
Even then, cross talking could happen.

– 13 – EN 50523-1:2009
Table 2 – Key Installation Events
Key event Description
First installation First time communicating appliances are installed in a home. For instance,
a gateway and a washing machine are installed.
Power Up Powering up one or several appliances (e.g. powering up the whole
installation after power failure).
Appliance is added A new appliance is added to the home installation. In some cases the
appliance could have been used in an autonomous mode (i.e. without
networking capability) for some time.
Appliance is removed An existing appliance is removed from the home installation (this could be
because the appliance is physically removed or because the appliance gets
back in an autonomous mode without networking capability).
Appliance Part of the installation is re-installed.
Re-installation
Re-installation The whole home installation is re-installed.
De-installation The home installation is de-installed. This could take place when persons
are moving out from their home.
Monitoring of A verification of the communication links is performed.
Communication Links
The following user functions in Table 3 are associated with each key event. In the following configuration,
data refer to network protocol data and configuration links data.
Table 3 – User Functions associated with Key Installation Events
Key event User function
First installation
Installation creation
The overall installation is created and personalised (i.e. a domain address
is assigned). An installation feedback is provided to the user.
Communication function is enabled with optional feedback to the user.
Power Up Automatic power up verification
After power up of one or several appliances, a short automatic start-up
phase takes place, involving the verification of its configuration.
Appliance is added Adding an appliance
The installation configuration is updated with a new communicating
appliance (i.e. configuration data of appliances are updated).
Appliance is removed
Removing an appliance
The installation configuration is updated to take into account removal (i.e.
configuration data of appliances are updated).
Re-installation
Re-installation
Network configuration data is changed in all the appliances or in a subset
(i.e. get domain address and dependent data).
De-installation De-installation
Network configuration data are removed from all appliances in the
installation (i.e. remove domain address and dependent data).
Monitoring of the Verification of configuration data
Communication links
Configuration data are verified.
Removing a specific communication link
In some cases, communication links might be considered as frozen once
they are set (this would be the case of an appliance that is usually switched
off). It is therefore necessary to specifically indicate when an actual removal
has taken place (e.g. with an appliance that is switched off).

3.4 Guidelines on Installation Procedures
3.4.1 Requirements
The following requirements are defined concerning installation procedures.
• Requirements on user functions. The following user functions shall be supported:
- installation creation;
- communication function enabling;
- automatic power up verification;
- adding an appliance;
- removing an appliance;
- re-installation;
- de-installation;
- verification of configuration data;
- removing a communication link.
• Requirements on installation actions. While each manufacturer will have the choice of their
implementations, such actions shall use as many existing elements of appliances as possible (e.g.
button, LED), except if the desired element does not exist. The minimum shall be the following: one
Boolean actuator such as a button (to perform the actions) and one Boolean display LED (to visualise
the status). Note that using a combination of buttons is considered reasonable.
• Requirements on feedback. The display of the status of each WG appliance in terms of installation shall
be mandatory. Each manufacturer will have the choice of its implementation.
• Requirements at the interworking level. WG appliances shall interwork at the installation level.
• Requirements at the installation level. Installers will have the choice of the installation scheme in terms
of involved devices, installation action and user interface. The minimum shall be an installation without
any tool.
3.4.2 Installation Functions
Installation functions are the procedures required to carry out user functions. Two types of such procedures
are defined:
• automatic: These procedures shall be supported by the network management part of the underlying
protocol as shown in Figure 2. As a result, this document only provides a functional description of these
procedures, while the protocol part is being described in specification documents related to the selected
underlying protocol.
• user: These procedures involve user action and a protocol part. Similarly to automatic procedures, the
automatic part of the user procedures shall be supported by the network management part of the
underlying protocol. The user action part shall be supported by the WG appliances through an
appropriate
...

Questions, Comments and Discussion

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

Loading comments...