SIST EN 61334-4-511:2002

SLOVENSKI STANDARD
01-april-2002
[Not translated]
Distribution automation using distribution line carrier systems -- Part 4-511: Data
communication protocols - Systems management - CIASE protocol
Verteilungsautomatisierung mit Hilfe von Trägersystemen auf Verteilungsleitungen -- Teil
4-511: Datenkommunikationsprotokolle - Systemverwaltung - CIASE Protokoll
Automatisation de la distribution à l'aide de systèmes de communication à courants
porteurs -- Partie 4-511: Protocoles de communication de données - Administration de
systèmes - Protocole CIASE
Ta slovenski standard je istoveten z: EN 61334-4-511:2000
ICS:
33.040.40 Podatkovna komunikacijska Data communication
omrežja networks
33.200 Daljinsko krmiljenje, daljinske Telecontrol. Telemetering
meritve (telemetrija)
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN STANDARD EN 61334-4-511
NORME EUROPÉENNE
EUROPÄISCHE NORM November 2000

ICS 33.040.40; 33.200
English version
Distribution automation using distribution line carrier systems
Part 4-511: Data communication protocols -
Systems management - CIASE protocol
(IEC 61334-4-511:2000)
Automatisation de la distribution  Verteilungsautomatisierung
à l'aide de systèmes de communication mit Hilfe von Trägersystemen
à courants porteurs auf Verteilungsleitungen
Partie 4-511: Protocoles de Teil 4-511:
communication de données - Datenkommunikationsprotokolle -
Administration de systèmes - Systemverwaltung -
Protocole CIASE CIASE Protokoll
(CEI 61334-4-511:2000) (IEC 61334-4-511:2000)

This European Standard was approved by CENELEC on 2000-08-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, Czech Republic,
Denmark, Finland, France, Germany, Greece, Iceland, Ireland, Italy, Luxembourg, Netherlands, Norway,
Portugal, Spain, Sweden, Switzerland and United Kingdom.

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

Central Secretariat: rue de Stassart 35, B - 1050 Brussels

© 2000 CENELEC - All rights of exploitation in any form and by any means reserved worldwide for CENELEC members.

Ref. No. EN 61334-4-511:2000 E

Page 2
Foreword
The text of document 57/446/FDIS, future edition 1 of IEC 61334-4-511, prepared by IEC TC 57, Power
system control and associated communications, was submitted to the IEC-CENELEC parallel vote and
was approved by CENELEC as EN 61334-4-511 on 2000-08-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) 2001-05-01
– latest date by which the national standards conflicting
with the EN have to be withdrawn (dow) 2003-08-01
Annexes designated "normative" are part of the body of the standard.
Annexes designated "informative" are given for information only.
In this standard, annex ZA is normative and annexes A, B and C are informative.
Annex ZA has been added by CENELEC.
__________
Endorsement notice
The text of the International Standard IEC 61334-4-511:2000 was approved by CENELEC as a European
Standard without any modification.
__________
Page 3
Annex ZA
(normative)
Normative references to international publications
with their corresponding European publications
This European Standard incorporates by dated or undated reference, provisions from other publications.
These normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications
apply to this European Standard only when incorporated in it by amendment or revision. For undated
references the latest edition of the publication referred to applies (including amendments).
NOTE When an international publication has been modified by common modifications, indicated by (mod), the relevant EN/HD
applies.
Publication Year Title EN/HD Year
IEC 61334-4-1 1996 Distribution automation using distribution line EN 61334-4-1 1996
carrier systems
Part 4: Data communication protocols --
Section 1: Reference model of the
communication system
IEC 61334-4-32 1996 Part 4: Data communication protocols -- EN 61334-4-32 1996
Section 32: Data link layer - Logical link
control (LLC)
IEC 61334-4-41 1996 Part 4: Data communication protocols -- EN 61334-4-41 1996
Section 41: Application protocols -
Distribution line message specification

IEC 61334-4-42 1996 Part 4: Data communication protocols -- EN 61334-4-42 1996
Section 42: Application protocols -
Application layer
1)
IEC 61334-4-512 Part 4-512: Data Communication Protocols - - -
Systems management using profile
61334-5-1-MIB
IEC 61334-5-1 1996 Part 5: Lower layer profiles -- Section 1: - -
Spread Frequency Shift Keying (S-FSK)
profile
ISO/IEC 7498 Series Information processing systems - Open - -
systems interconnection - Basic reference
model
ISO/IEC 7498-1 1994 Information technology - Open systems EN ISO/IEC 7498-1 1995
interconnection - Basic reference model: The
basic model
ISO/IEC 7498-3 1997 Part 3: Naming and addressing - -

ISO/IEC 7498-4 1989 Part 4: Management framework - -

1)
In preparation
Page 4
Publication Year Title EN/HD Year
ISO/IEC/TR 8509
1987 Information processing systems - Open - -
systems interconnection - Service
conventions
ISO/IEC 9545 1994 Information technology - Open Systems - -
Interconnection - Application Layer structure

NORME CEI
INTERNATIONALE IEC
61334-4-511
INTERNATIONAL
Première édition
STANDARD
First edition
2000-04
Automatisation de la distribution à l'aide de
systèmes de communication à courants porteurs –
Partie 4-511:
Protocoles de communication de données –
Administration de systèmes – Protocole CIASE
Distribution automation using distribution line
carrier systems –
Part 4-511:
Data communication protocols –
Systems management – CIASE protocol
 IEC 2000 Droits de reproduction réservés  Copyright - all rights reserved
Aucune partie de cette publication ne peut être reproduite ni No part of this publication may be reproduced or utilized in
utilisée sous quelque forme que ce soit et par aucun procédé, any form or by any means, electronic or mechanical,
électronique ou mécanique, y compris la photocopie et les including photocopying and microfilm, without permission in
microfilms, sans l'accord écrit de l'éditeur. writing from the publisher.
International Electrotechnical Commission 3, rue de Varembé Geneva, Switzerland
Telefax: +41 22 919 0300 e-mail: inmail@iec.ch IEC web site http://www.iec.ch
CODE PRIX
Commission Electrotechnique Internationale
V
PRICE CODE
International Electrotechnical Commission
Pour prix, voir catalogue en vigueur
For price, see current catalogue

61334-4-511 © IEC:2000 – 3 –
CONTENTS
Page
FOREWORD . 7
INTRODUCTION .9
Clause
1 Scope . 11
2 Normative references . 11
3 Definitions. 13
4 Abbreviations . 17
5 Service argument description . 19
6 Systems management overview. 21
6.1 OSI standards. 21
6.2 DCP systems management concepts. 21
6.2.1 MIB . 23
6.2.2 Alarm . 23
6.2.3 Client SMAE. 23
6.3 Use of DLMS services in management services. 23
6.4 Management VDE . 23
6.4.1 Service Conformance Block. 25
6.4.2 Mandatory DLMS Objects . 25
6.5 Specifications of types . 27
7 Configuration Initiation Application Service Element. 27
7.1 Discover service. 27
7.1.1 Purpose . 27
7.1.2 Structure . 29
7.1.3 Arguments . 29
7.1.4 Service procedure . 31
7.2 Register service . 37
7.2.1 Purpose . 37
7.2.2 Structure . 37
7.2.3 Arguments . 37
7.2.4 Service Procedure. 39
7.3 CIASE protocol . 39
7.3.1 Abstract and transfer syntax . 39
7.3.2 Mapping to underlying services. 39
7.3.3 CI-PDU description. 41
7.4 CIASE state tables . 43
7.4.1 Notations used in state tables. 43
7.4.2 States description. 49
7.4.3 Local state variables. 49
7.4.4 Event functions description. 51
7.4.5 Actions description . 53
Annex A (informative) Vocabulary and operating rules. 59
Annex B (informative) Examples of CIASE protocol use . 63
Annex C (informative) Example of CIASE Td calculation . 65

61334-4-511 © IEC:2000 – 5 –
Page
Figure 1 – The Systems Management Application Process. 21
Table 1 – The Discover service. 29
Table 2 – The Register service . 37
Table 3 – The Client CIASE state table . 45
Table 4 – The Server CIASE state table. 47

61334-4-511 © IEC:2000 – 7 –
INTERNATIONAL ELECTROTECHNICAL COMMISSION
____________
DISTRIBUTION AUTOMATION USING
DISTRIBUTION LINE CARRIER SYSTEMS –
Part 4-511: Data communication protocols –
Systems management – CIASE protocol
FOREWORD
1) The IEC (International Electrotechnical Commission) is a worldwide organization for standardization comprising
all national electrotechnical committees (IEC National Committees). The object of the IEC is to promote
international co-operation on all questions concerning standardization in the electrical and electronic fields. To
this end and in addition to other activities, the IEC publishes International Standards. Their preparation is
entrusted to technical committees; any IEC National Committee interested in the subject dealt with may
participate in this preparatory work. International, governmental and non-governmental organizations liaising
with the IEC also participate in this preparation. The IEC collaborates closely with the International Organization
for Standardization (ISO) in accordance with conditions determined by agreement between the two
organizations.
2) The formal decisions or agreements of the IEC 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 National Committees.
3) The documents produced have the form of recommendations for international use and are published in the form
of standards, technical specifications, technical reports or guides and they are accepted by the National
Committees in that sense.
4) In order to promote international unification, IEC National Committees undertake to apply IEC International
Standards transparently to the maximum extent possible in their national and regional standards. Any
divergence between the IEC Standard and the corresponding national or regional standard shall be clearly
indicated in the latter.
5) The IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with one of its standards.
6) Attention is drawn to the possibility that some of the elements of this International Standard may be the subject
of patent rights. The IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC 61334-4-511 has been prepared by IEC technical committee 57:
Power system control and associated communications.
The text of this standard is based on the following documents:
FDIS Report on voting
57/446/FDIS 57/460/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
This publication has been drafted in accordance with the ISO/IEC Directives, Part 3.
Annexes A, B and C are for information only.
The committee has decided that the contents of this publication will remain unchanged until 2004.
At this date, the publication will be
• reconfirmed;
• withdrawn;
• replaced by a revised edition, or
• amended.
61334-4-511 © IEC:2000 – 9 –
INTRODUCTION
The description of the DCP systems management given in this part of IEC 61334 is developed
in the following clauses:
Clause 1 defines the scope of this International Standard.
Clause 2 lists related ISO/IEC standards.
Clause 3 defines the terms used in this standard.
Clause 4 defines the abbreviations used in this standard.
Clause 5 specifies the conventions taken for the description of the primitives.
Clause 6 introduces general concepts related to DCP systems management.
Clause 7 specifies the Configuration Initiation Application Service Element (CIASE).

61334-4-511 © IEC:2000 – 11 –
DISTRIBUTION AUTOMATION USING
DISTRIBUTION LINE CARRIER SYSTEMS –
Part 4-511: Data communication protocols –
Systems management – CIASE protocol
1 Scope
This part of IEC 61334 specifies the DCP management requirements. It describes the manage-
ment services in an abstract way as well as the underlying protocol.
It defines terminology and describes concepts for DCP systems management, describes DCP
systems management activities and facilities, and specifies DCP services and protocol.
2 Normative references
The following normative documents contain provisions which, through reference in this text,
constitute provisions of this part of IEC 61334. For dated references, subsequent amendments
to, or revisions of, any of these publications do not apply. However, parties to agreements
based on this part of IEC 61334 are encouraged to investigate the possibility of applying the
most recent editions of the normative documents indicated below. For undated references, the
latest edition of the normative document referred to applies. Members of IEC and ISO maintain
registers of currently valid International Standards.
IEC 61334-4-1:1996, Distribution automation using distribution line carrier systems – Part 4:
Data communication protocols – Section 1: Reference model of the communication system
IEC 61334-4-32:1996, Distribution automation using distribution line carrier systems – Part 4:
Data communication protocols – Section 32: Data link layer – Logical link control (LLC)
IEC 61334-4-41:1996, Distribution automation using distribution line carrier systems – Part 4:
Data communication protocols – Section 41: Application protocols – Distribution line message
specification
IEC 61334-4-42:1996, Distribution automation using distribution line carrier systems – Part 4:
Data communication protocols – Section 42: Application protocols – Application layer
IEC 61334-4-512,  Distribution automation using distribution line carrier systems – Part 4-512:
1)
Data communication protocols – Systems management using profile 61334-5-1-MIB
IEC 61334-5-1:1996, Distribution automation using distribution line carrier systems – Part 5:
Lower layer profiles – Section 1: The spread frequency shift keying (S-FSK) profile
___________
1)
Under consideration.
61334-4-511 © IEC:2000 – 13 –
ISO/IEC 7498 (all parts), Information technology – Open systems interconnection – Basic
reference model
ISO/IEC 7498-1:1994, Information technology – Open systems interconnection – Basic
reference models – The basic model
ISO/IEC 7498-3:1997, Information technology – Open systems interconnection – Basic
reference model – Part 3: Naming and addressing
ISO/IEC 7498-4:1989, Information processing systems – Open systems interconnection – Basic
reference model – Part 4: Management framework
ISO/IEC/TR 8509:1987, Information processing systems – Open systems interconnection –
Service conventions
ISO/IEC 9545:1994, Information technology – Open systems interconnection – Application
layer structure
3 Definitions
3.1 For the purposes of this part of IEC 61334, the following terms as defined in ISO/IEC 7498
apply:
a) open system,
b) application-process,
c) (N)-layer,
d) (N)-sublayer,
e) (N)-service,
f) (N)-service-access-point,
g) (N)-protocol,
h) (N)-protocol-data-unit,
i) (N)-service-data-unit,
j) systems-management,
k) application-entity,
l) application-service-element,
m) user-element.
3.2 For the purposes of this part of IEC 61334, the following terms as defined in ISO/IEC 7498-3
apply:
a) (N)-address,
b) (N)-selector,
c) (N)-association,
d) (N)-directory-function,
e) (N)-entity,
f) (N)-entity-title,
g) system-title.
61334-4-511 © IEC:2000 – 15 –
3.3 For the purposes of this part of IEC 61334, the following terms as defined in ISO/IEC 7498-4
apply:
a) Systems management application-entity,
b) OSI Management,
c) Managed Object,
d) Management Information Base.
3.4 For the purposes of this part of IEC 61334, the following terms as defined in ISO/IEC/
TR 8509 apply:
a) primitive,
b) request,
c) indication,
d) response,
e) confirm,
f) service provider,
g) service user.
3.5 For the purposes of this part of IEC 61334, the following term as defined in ISO/IEC 9545
applies:
a) application-context.
3.6 For the purposes of this part of IEC 61334, the following terms as defined in IEC 61334-4-1
apply:
a) NEW-address,
b) AllNew-Title,
c) Source-Title,
d) AllSMAE-Title,
e) AllCIASE-Title.
3.7 For the purposes of this part of IEC 61334, the following terms as defined in IEC 61334-4-41
apply:
a) client,
b) server,
c) Virtual Distributing Equipment (VDE),
d) Task Invocation,
e) Data Set,
f) conformance.
3.8 For the purposes of this part of IEC 61334, the term "initiator" is not used as defined in
ISO/IEC 7498-3. It is redefined thus:
3.8.1
initiator
user-element of a client SMAE (it uses the CIASE and DLMS ASE and is identified by its
system title)
61334-4-511 © IEC:2000 – 17 –
3.9 For the purposes of this part of IEC 61334, the following definitions apply.
3.9.1
active initiator
initiator which issues or has last issued a CIASE Register request when the server is in the
unconfigured state
3.9.2
manager
user-element of the CIASE and DLMS ASEs that belongs to the sole SMAE of each server
system
3.9.3
new system
server system which is in the unconfigured state: its MAC address equals "NEW-address"
3.9.4
new system title
system-title of a new system
3.9.5
registered system
server system which has an individual valid MAC address (therefore, different from "NEW-
Address", see IEC 61334-5-1: Medium Access Control)
3.9.6
reporting system
server system which issues a DiscoverReport request
3.9.7
system
synonymous for real open system
4 Abbreviations
ACSE Association Control Service Element
APDU Application Protocol Data Unit
ASE Application Service Element
CIASE Configuration Initiation ASE
Conf Confirm
CRC Cyclic Redundancy Code (see IEC 61334-5-1)
DASE DLMS Application Service Element
DCP Data Communication Protocols
DLMS Distribution Line Message Specification
Ind Indication
IEC International Electrotechnical Commission
ISO International Organization for Standardization
LLC Logical Link Control
L-SAP Link Service Access Point
MAC Medium Access Control
61334-4-511 © IEC:2000 – 19 –
MIB Management Information Base
OSI Open Systems Interconnection
OSIE Open Systems Interconnection Environment
PDU Protocol Data Unit
Req Request
SAP Service Access Point
SDU Service Data Unit
SMAE Systems Management Application Entity
SMAP Systems Management Application Process
VAA Virtual Application Association
VDE Virtual Distribution Equipment
The following initials are used to specify the layers or sublayers:
a) PHY – Physical layer,
b) DL – Data_Link layer,
c) MA – MAC sublayer,
d) L – LLC sublayer,
e) CI – CIASE sublayer (application layer).
5 Service argument description
This standard uses a tabular format to describe the component arguments of the CIASE
service primitives. Each table consists of one to two columns describing the service arguments
and the request ("Req"), and confirm ("Conf") primitives. The "Conf" column is absent when the
service is not a confirmed service. The initiator (which is a CIASE-user) uses the CIASE
services.
In each table, one argument (or a part of it) is listed on each horizontal line. Under the appro-
priate service primitive columns, a code is used to specify the type of usage of the argument.
The codes used are listed below:
a) M – the argument is Mandatory for the primitive;
b) U – the argument is a User option, and may or may not be provided depending on dynamic
usage by the CIASE user;
c) S – the argument is Selected among other S-arguments;
d) C – the argument is Conditional upon other arguments or the environment of the CIASE
user;
e) (blank) – the argument is never present.
The "(=)" code following one of the M, U, C or S codes indicates that the argument is
semantically equivalent to the argument in the service primitive to its immediate left in the
table. (For instance, an "M(=)" code in the indication service primitive column and an "M" in
the request service primitive column means that the argument in the indication primitive is
semantically equivalent to the one in the request primitive.)

61334-4-511 © IEC:2000 – 23 –
Therefore, the minimal DCP SMAE contains three ASEs, represented in figure 1:
– the Configuration Initiation ASE to configure the system,
– the Application Control Service Element to support the application association required by
the DLMS environment,
– the DLMS ASE to support the DLMS environment.
The single server user-element of the SMAE is called the manager. A client user-element of a
SMAE is called initiator. Both use the CIASE and the DLMS services.
6.2.1 MIB
On a server system, a resource that is manageable by the management services is modelled
by a Managed Object. The information associated with a Managed Object that can be operated
upon is contained in the Management Information Base (MIB). This information is made visible
to other systems through DLMS objects that can be handled using the DLMS services.
6.2.2 Alarm
A server system can be in an alarm state. Several alarm states may be defined on a server
system. Each alarm is characterized by an attribute named "alarm-descriptor". The conditions
that make the system enter in an alarm state, as well as the value of the "alarm-descriptor" to
assign to each alarm state, should be specified in the companion specifications.
The discovery of systems in an alarm state is another activity of systems management.
NOTE The alarm-descriptor is coded as an Integer on 8 bits. It is then possible to characterize 256 different alarm
states on a server system.
6.2.3 Client SMAE
There is one sole system management application-entity per client system. This SMAE is
attached to one user-element called the active initiator (see ISO/IEC 7498-1).
6.3 Use of DLMS services in management services
All the DLMS services defined in the DLMS section (see IEC 61334-4-41) apply to the manage-
ment specification.
6.4 Management VDE
The present subclause defines the structure of the Management VDE required to perform
system configuration successfully. The structure of the Management VDE is described by a
minimum list of services, objects and types with which a DCP Management system must
comply.
61334-4-511 © IEC:2000 – 25 –
6.4.1 Service Conformance Block
The following services must be supported by the Management VDE:
for. services
Context Management services (ACSE) Initiate, Abort (mandatory services)
VDE support services GetStatus, simple GetNameList (mandatory services)
Variable Access services Read, Write, UnconfirmedWrite
The requested minimum value of the conformance block is then:
Conformance::= [APPLICATION 30] IMPLICIT BIT STRING (SIZE(16)) {
-- the bit is set when the corresponding service or functionality is available
get-data-set-attribute 0,
get-ti-attribute 0,
get-variable-attribute 0,
read 1, -- to configure the system
write 1, -- to configure the system
unconfirmedWrite 1, -- to configure the system
change-scope 0,
start 0,
stop-resume 0,
make-usable 0,
data-set-load 0,
selection-in-get-name-list 0,
detailed-access-low-bit 0,
detailed-access-high-bit 0,
multiple-variable-list 0,
data-set-upload 0
}
The Conformance Type is described in IEC 61334-4-41.
All the other services may be available but are not mandatory.
6.4.2 Mandatory DLMS Objects
The object classes mandatory for the systems management in the SMAE are
– VDE, for the VDE object itself,
– VAA, in order to configure the system,
– Named Variable objects for the MIB,
– The Data Set of objects of the VDE.

61334-4-511 © IEC:2000 – 27 –
6.5 Specifications of types
The CIASE PDUs are based on the built-in types of ASN1. CIASE does not make use of the
type descriptions from the DLMS protocol.
7 Configuration Initiation Application Service Element
The CIASE services provide facilities for discovering servers which are in an unconfigured
state (mac-address set to NEW) or in an alarm state (see 6.2.2).
The CIASE services also allow the assignment of an individual MAC address to unconfigured
systems. Communication can only occur after the server system has an individual MAC
address.
There are two CIASE services: the Discover service and the Register service.
7.1 Discover service
7.1.1 Purpose
The Discover service is used to discover new systems or systems which are in an alarm state.
The procedure begins with a Discover request issued by the active initiator. The Discover
service is provided by the DCP specification to inform systems that they will have a chance to
respond in the next time slots (in an allowed time range). The server systems that respond to a
DL_Data.indication containing a Discover CI-PDU are systems that match the reporting
conditions.
A server system which fits the reporting conditions is a system that is unconfigured (MAC-
address set to NEW) or in an alarm state.
The response to a DL_Data.indication containing a Discover CI-PDU is called a Discover
Report. A DiscoverReport is issued by a server system: it corresponds to the construction of a
DL_Data.request primitive containing a DiscoverReport CI-PDU.
The Discover.request specifies
– the probability that a system matching the reporting conditions responds,
– the allowed time slots available for the response,
– the credit used by the server to compute the initial credit for the response,
– the IC equal credit which says how to compute the initial credit used for the response.

61334-4-511 © IEC:2000 – 29 –
7.1.2 Structure
Table 1 – The Discover service
Discover service Req Conf
Argument M
Response Probability M
Allowed Time Slots M
DiscoverReport Credit M
ICEqualCredit M
Result(+) S
Number of received invalid frames M
List of system-titles M
List of states M
unknown
unconfigured
alarm-descriptor
Result(–) S
Argument Error(s) M
7.1.3 Arguments
The "Argument" field conveys the specific arguments of the Discover request.
The "Response Probability" argument is an unsigned integer between 0 and 100. It is the
probability in per cent that a system matching the reporting conditions responds to the
received DL_Data.indication containing the Discover CI-PDU. It then issues a DL_Data.
request primitive containing a DiscoverReport CI-PDU. When it is set to 100, all the
reporting systems respond. When it is set to 0, no system responds.
The "Allowed Time Slots" argument, of unsigned integer type, specifies to the new systems
the window (in time slots) they have at their disposal to issue a frame containing a
DiscoverReport CI-PDU (if they have to) after the end of Discover transmission. If null, no
system will respond.
The "DiscoverReport Credit" argument, of unsigned integer type, specifies to the new
systems the credit they have to use to compute the initial credit for the DiscoverReport
MA_Data request (refer to IEC 61334-5-1 for further explanations about the credit and the
repetition).
The "IC Equal Credit" argument, of unsigned integer type, specifies how to compute the
initial credit to use for the frame containing the DiscoverReport CI-PDU. If the value of this
argument is 0, IC = "DiscoverReport Credit" value. If IC Equal Credit=1, IC = MIN between
"DiscoverReport Credit" value and the "Delta credit" value associated with the received
"Discover frame plus one".
61334-4-511 © IEC:2000 – 31 –
The "Result(+)" argument indicates that the requested service has succeeded.
The "Number of received invalid frames" argument indicates to the active initiator how
many invalid MAC frames have been received between the end of the transmission of the
Discover request and the confirmation issue. The MAC sublayer of the client system
provides a function which counts the number of received invalid frames. This MAC counter
is linked to a local management variable shared by the CIASE and the MAC sublayer.
The "list of system-titles" argument carries the list of the server system titles that have
issued a DiscoverReport which has been received by the active initiator CIASE.
The "list of states" argument contains the state of each system. The values occur in the list
in the order of the system-titles specified in the "list of system-titles" parameter. Each
element specifies either the absence of an alarm (the system is unconfigured), or the
presence of an alarm on the system (the alarm-descriptor is then provided) or no
information (parameter equal to unknown).
The "Result(–)" argument indicates that the requested service has failed.
The "Argument Error(s)" specifies that at least one argument has a wrong value (Response
Probability greater than 100, DiscoverReport Credit greater than the maximum initial credit,
ICEqualCredit greater than 1) and which one. The argument values are tested separately
and in order (Response Probability, then DiscoverReport Credit and ICEqualCredit). The
first wrong value generates a confirm with the appropriate error, whatever the value of the
next parameters (if they exist).
7.1.4 Service procedure
7.1.4.1 Client system
The Discover request is issued by the active initiator to the CIASE. If the "DiscoverReport
Credit" parameter is greater than the maximal initial credit, and/or the "Response Probability" is
strictly greater than 100, and/or the "ICEqualCredit" is strictly greater than 1, a confirmation
is sent immediately with a negative result corresponding to the first wrong argument.
If not, the CIASE
– resets the CRC-Nok-counter local management variable. This action involves the resetting
of the invalid frame counting function of the MAC sublayer;
– forms a DL_Data request with the transmitted arguments. This request is sent to all the
systems (configured or not).
Once the Discover transmission is over, the CIASE waits for the DL_Data indications
containing a DiscoverReport CI-PDU of the reporting systems during the amount of time slots
corresponding to the value: Allowed Time Slots plus DiscoverReport Credit plus the CIASE Tup
which is the time, on the Client system, between the end of the physical frame transmission
and the arrival of the DL_Data.ind (CIASE-PDU) indication; Tup is defined as a whole number
of time slots as follows:
if (n time-slot < Tup <= n + 1 time-slot), Tup=n + 1 .
At the end of this time, the CIASE
– reads the local CRC-Nok-counter management variable to get the number of invalid MAC
frames received with an incorrect frame check sequence (FCS);

61334-4-511 © IEC:2000 – 33 –
– issues a Discover confirm to the active initiator, with
– the number of received invalid frames,
– the system-titles list of the reporting systems received by the CIASE in the
DL_Data.indications,
– the state of each reporting system. This state is completed during the reception phase
of the different DiscoverReport PDUs. The following rules are followed.
On reception of a DL_Data.indication containing a DiscoverReport CI-PDU, the CIASE
checks if the alarm-descriptor is present in the DiscoverReport CI-PDU. If it is not present,
it means that the reporting system that has issued the DiscoverReport PDU is
unconfigured. The CIASE then assigns to the corresponding system-title (situated at the
first position of the list of system-titles) the "unconfigured" state. If the alarm-descriptor is
present in the DiscoverReport CI-PDU, the CIASE assigns to the corresponding system-title
the value of the alarm-descriptor. If the list of system-titles received in the
DL_Data.indication contains other system-titles, the CIASE assigns to them the "unknown"
state attribute. In that case, the CIASE is not able to determine the state of the server
system.
A system-title appears only once in the Discover confirmation. The CIASE sorts the received
system-titles so that no repetition of system-titles appears in the "list of system-titles"
parameter. When two system-titles virtually appear in the list of system-titles, the state attribute
can be different. One can be equal to "unknown" whereas the other one is set to "unconfigured"
or "alarm-descriptor". In that case, the CIASE should memorize the attribute which is the more
explicit, that is to say "unconfigured" or "alarm-descriptor".
7.1.4.2 Server systems
On reception of a DL_Data indication containing a Discover CI-PDU, each CIASE tests if
– the system MAC-address is set to NEW-address,
or
– the system is in an alarm state.
If it is, the server system CIASE performs the following steps.
First, it resets the local-system-list local management variable.
It then draws a random number between 1 and 100.
If this number is smaller than, or equal to, the Response Probability argument, the CIASE
– determines the delay (in time slots) DET before the end of the Discover transmission
(this time is negative if this access moment is already over); DET is defined as a whole
number of time slots as follows:
if (n time-slot <= delay < n + 1 time-slot), DET= ±(n + 1);
– compares DET to the CIASE Td, which is the time between sending a DL_Data.req
request and the moment when the medium could be accessed (start of the physical
frame transmission). Td is defined as a whole number of time slots as follows:
if (n time-slot <= T < n + 1 time-slot), Td = n + 1
with T = time(start of the physical transmission) – time(sending DL_Data.req);

61334-4-511 © IEC:2000 – 35 –
– if DET – Td is positive
• draws a Random Time Slot between 0 and the "Allowed Time Slots" minus one,
• waits DET-Td time-slots,
otherwise, since the response window has already started,
– draws a Random Time Slot between 0 and the "Allowed Time Slots" minus (1 + Td-
DET), and
– waits during the "random time slots" chosen (which can be zero). This waiting period is
chosen so that the resulting physical frame (containing the DiscoverReport CI-PDU)
issued by the server system is transmitted before the end of the specified window.
At the end of this waiting period, the CIASE issues a DL_Data request containing a
DiscoverReport CI-PDU. This PDU is a structure which includes
– a list of system-titles made up with the own system-title of the system followed by the
content of its "local-system-list" local management variable. If the local-system-list contains
too many systems to be issued in one sole PHY-frame, only the newest reporting systems
will have their system-titles written in this list;
– the alarm-descriptor characterizing the alarm state of the system. This parameter is optional.
It is issued by the CIASE only if the system is in an alarm state. If the system is not in an
alarm state, the parameter is not included in the DiscoverReport CI-PDU.
The request is sent to all the systems (configured or not, client or server), with an initial credit
computed with the "DiscoverReport Credit" and "the ICEqualCredit" parameters of the Discover
primitive. The first system-title in the list of system-titles contained in the DiscoverReport
CI-PDU is the system-title of the reporting system. The alarm-descriptor, if present, refers to
the alarm state of the reporting system. No state description is given for the other system-titles
contained in the list.
If the server CIASE receives a negative DL_Data.confirm after having sent a DiscoverReport
CI-PDU, and if the CIASE is able to transmit another DiscoverReport CI-PDU in the remaining
window, the CIASE computes a new Random Time Slot which value is included in the
remaining time period and issues a second DiscoverReport CI-PDU. This procedure is
repeated as long as negative DL_Data.confirm primitives are returned to the CIASE and as
long as the server system is in a position to transmit the corresponding PHY-frame in the
remaining time period.
Such systems are named in the following the "reporting systems".
NOTE 1 The random function of the CIASE should be initialized differently on each system.
NOTE 2 The random function should have an uncertain behaviour, ±10 %; that is, for a significant number of
systems (greater than 10), the reporting systems number should be the Response Probability number ±10 %.
On reception of a DL_Data indication containing a DiscoverReport CI-PDU, a server system
(configured or not) updates its "local-system-list" local management variable and its "reporting-
system-list" MIB object with the list of system-titles contained in the CI-PDU. If these lists are
full, the most recent system-titles replace the older ones in the "reporting-system-list" and the
"local-system-list". The CIASE checks if a system-title is not already in the list. If it is, it writes it
at the beginning of the list and destroys the older one (see IEC 61334-4-512 for more
explanations). The "reporting-system-list" MIB object can be read (fully) later through a DLMS
read service.
61334-4-511 © IEC:2000 – 37 –
7.2 Register service
7.2.1 Purpose
The initiator enters the registering phase by issuing a Register request to the CIASE provider.
The Register service is the CIASE service provided to perform system configuration. It
specifies its MAC address to a new system identified by its system-title.
7.2.2 Structure
Table 2 – The Register service
Register service Req Conf
Argument M
List of Correspondence M
New system-title(s) M
MAC address(es) M
Result(+) S
Result(–) S
Argument Error(s) M
7.2.3 Arguments
The "List of Correspondence" provides the correspondence between the server systems
assigned MAC addresses and their system-titles.
The "New system-title(s)" argument identifies a system uniquely in the OSIE. This argument
is semantically equivalent to the system-titles of "list of system-titles" argument transmitted
in the DL_Data indication containing a DiscoverReport CI-PDU.
The "MAC address(es)" argument is required to access an LLC-entity. It is allocated to the
new system identified by its New system-title.
The "Result(+)" argument indicates that the requested service has succeeded.
The "Result(–)" argument indicates that the requested service has failed.
The "Argument Error
...