Draft IEC 61850-9-1  IEC:1999 – 1 / 67 – 57/XXX/CD

IEC 61850-9-1

Communication Networks and Systems in Substations

Part 9-1: Specific Communication Service Mapping (SCSM) –

Serial Unidirectional Multidrop Point to Point Link

th
Committee Draft: Revision 1.0, May 04 , 1999

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 2 / 67 – 57/XXX/CD

List of Contents

FOREWORD 8
INTRODUCTION 9
1 Scope 11
1.1 General 12
1.2 General block diagram of electronic transducers 12
1.3 General block diagram of electronic transducers with a digital output 13
2 Normative References 14
3 Definitions 15
4 Abbreviations 16
5 Principal of Mapping to serial unidirectional multidrop point to point link 17
5.1 Communication Stack 17
5.1.1 Physical Layer 18
5.1.2 Link Layer 18
5.1.3 Network Layer 19
5.1.4 Transport Layer 19
5.1.5 Session Layer 19
5.1.6 Presentation Layer 19
5.1.7 Application Layer 19
5.2 Restrictions 23
6 Mapping of the Device Model 24
6.1 Overview 24
6.2 Mapping of the objects 24
6.3 Additional definitions for the device model 24
7 Mapping of the server class 25
7.1 Mapping of the server class structure 25
7.2 Mapping of the server class services 25
7.3 Additional definitions for the server class 25
8 Mapping of the association model 26
8.1 Mapping of the association class definition 26
8.2 Mapping of the association services 26
8.3 Additional definitions for association model 26
9 Mapping of the basic data class 27
9.1 Mapping of the basic data class description 27
9.2 Mapping of the basic data object access services 27
9.3 Mapping of the basic data types 28
th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 3 / 67 – 57/XXX/CD

9.3.1 OSTRi 28
9.3.2 Printable ASCII text string 28
9.3.3 SET OF BOOLEAN 28
9.3.4 Unsigned Integer 29
9.3.5 Integer 30
9.3.6 Unsigned Fixed Point Number 31
9.3.7 Fixed Point Number 31
9.3.8 Short Real IEEE Std 754 31
9.3.9 Real IEEE Std 754 31
9.3.10 Time 31
9.3.11 ENUM 32
9.4 Mapping of the structured data types 33
9.4.1 Structure 33
9.4.2 Array 33
9.4.3 SI units 33
9.5 Data object Names 33
9.5.1 Data object Names: Scope designator 33
9.6 Additional definitions for the basic data types 33
10 Mapping of the data set class 34
10.1 Mapping of the data set class definition 34
10.2 Mapping of the data set access services 34
10.3 Additional definitions for the data set class 34
11 Mapping of the subscribed data transfer model 35
11.1 Mapping of the event control model 35
11.1.1 Mapping of the event control services 35
11.1.2 Additional definitions for the event control model 35
11.2 Mapping of the report model 35
11.2.1 Mapping of the report services 35
11.2.2 Additional definitions for the report model 35
11.3 Mapping of the log model 35
11.3.1 Mapping of the log services 35
11.3.2 Additional definitions for the log model 35
12 Mapping of the control class 36
12.1 Mapping of the direct control without enhanced security 36
12.2 Mapping of the direct control with enhanced security 36
12.3 Mapping of the SBO with enhanced security 36
th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 4 / 67 – 57/XXX/CD

12.4 Mapping of the control object services 36

12.5 Additional definitions for the control model 36
13 Mapping of the substitution model 37
13.1 Mapping of the services on indication objects 37
13.2 Additional definitions for the substitution model 37
14 Mapping of the fast transmission of binary status model 38
14.1 Mapping of the fast transmission of binary status services 38
14.1.1 Mapping of the ActivateOutput service 38
14.1.2 Mapping of the DeactivateOutput service 38
14.2 Additional definitions for the fast control of binary outputs model 38
15 Mapping of the transmission of sampled values model 39
15.1 Mapping of the transmission of sampled values services 39
15.1.1 Mapping of the Subscribe Sampled Values Service 39
15.1.2 Mapping of the Unsubscribe Sampled Values Service 39
15.1.3 Mapping of the Report Sampled Values Service 40
15.2 Additional definitions for the transmission of sampled values model 40
16 Mapping of the Time model 41
16.1 Additional definitions for the time model 41
17 Mapping of the file transfer model 42
17.1 Mapping of the file transfer services 42
18 Mapping of the common attribute classes 43
18.1 Mapping of the Command Qualifier Attribute 43
18.2 Mapping of the Description Attribute 43
18.3 Mapping of the Originator Attribute 43
18.4 Mapping of the Quality Attribute 43
18.5 Mapping of the Time Stamp Quality Attribute 43
18.6 Mapping of the Reason for Status Change Attribute 44
18.7 Mapping of the Sampling Rate Attribute 44
18.8 Mapping of the TimeStamp Attribute 44
18.9 Mapping of the Units Attribute 44
18.10 Mapping of the Tag Type Attribute 44
18.11 Mapping of the Analog Value Attribute 45
18.12 Mapping of the Configuration of Scaled Analog Value (SVC) 45
19 Mapping of the Common Data Class Specifications 46
19.1 Mapping of the Data Class Specification for Status Information 46
19.1.1 Mapping of the Single Point Status 46
19.1.2 Mapping of the Double Point Status 46
th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 5 / 67 – 57/XXX/CD

19.1.3 Mapping of the Step Position Information 46

19.1.4 Mapping of the Status Indication Group 46
19.2 Mapping of the Attribute Class Specifications for Control Information 47
19.2.1 Mapping of the Single Point Control 47
19.2.2 Mapping of the Double Point Control 47
19.3 Mapping of the Attribute Class Specifications for Measurands Information 47
19.3.1 Mapping of the Measured Value Class 47
19.3.2 Mapping of the Binary Counter Reading Class 47
19.3.3 Mapping of the Harmonic Value Class 47
19.3.4 Mapping of the WYE Class 48
19.3.5 Mapping of the Delta Class 49
19.3.6 Mapping of the Sequence Class 49
19.3.7 Mapping of the Phase Class 49
19.4 Mapping of the Attribute Class Specifications for Setpoint Information 50
19.4.1 Mapping of the Setpoint Class 50
20 Mapping of Compatible Logical Node and Data Object-Addressing 51
20.1 Supported logical nodes 51
20.2 Data Object Reference 51
20.2.1 Measurand Identification 51
20.3 Measurand Groups 51
20.4 Single Point Status Groups 52
20.5 Supplementary Technological References 52
Annex A (normative) 53
Definition of datasets 53
Dataset for universal use (defined by IEC 60044-8) 53
Dataset for Current Samples 56
Dataset for voltage samples 58
Dataset for Busbar Voltage Samples 60
Dataset for Binary Status Information 62
ANNEX B (informative) 63
Introduction to Ethernet 63
Overview of Ethernet Frame Structure 63
Introduction to Ethernet Switching 65

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 6 / 67 – 57/XXX/CD

List of Figures

Figure 1 - Relative position of this part of the standard 9

Figure 2 - Example for the use of the serial unidirectional multidrop point to point link 11
Figure 3 - General block diagram of an single-phase electronic transducer 12
Figure 4 - Example for electronic transducer configuration 13
Figure 5 - Communication Stack 17
Figure 6 – Data frame (DF) for the blocking of ALPDUs 19
Figure 7 – ALPDU – Application Layer Protocol Data Unit 20
Figure 8 – Process Data Group 21
Figure 9 – Data Set Group 22
Figure 10 – Serialization of sample data with a switch 23
Figure 11 – DataSet for Universal Use 55
Figure 12 – Dataset for current samples 57
Figure 13 – Dataset for voltage samples 59
Figure 14 – Dataset for Busbar Voltage Samples 61
Figure 15 – Dataset for Binary Status Information 62
Figure 16 - Ethernet Frame Format 63

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 7 / 67 – 57/XXX/CD

List of Tables

Table 1 – Selection guide for Ethernet link layer (receiving node) 18

Table 2 – Selection guide for Ethernet link layer (sending node) 18
Table 3 – Enumeration of DataGroup Identifier 21
Table 4 – Enumeration of CommonDataClassIdentifier 21
Table 5 – Enumeration of reserved DataSetIdentifier values 23
Table 6 – Mapping of the device model 24
Table 7 – Mapping of the physical device 24
Table 8 – Mapping of the server class definition 25
Table 9 – Mapping of the basic data class definition 27
Table 10 – Mapping of the basic data object access services 27
Table 11 – Mapping of the octet string data type 28
Table 12 – Mapping of the ASCII text string data type 28
Table 13 – Mapping of the Boolean data type 28
Table 14 – Mapping of the unsigned integer data type 29
Table 15 – Mapping of the integer data type 30
Table 16 – Mapping of the unsigned fixed point number data type 31
Table 17 – Mapping of the fixed point number data type 31
Table 18 – Mapping of the short real IEEE Std 754 data type 31
Table 19 – Mapping of the real IEEE Std 754 data type 31
Table 20 – Mapping of the time data type 31
Table 21 – Mapping of the enum data type 32
Table 22 – Mapping of the structure data type 33
Table 23 – Mapping of the array data type 33
Table 24 – Mapping of the data set class definition 34
Table 25 – Mapping of the data set access services 34
Table 26 – Mapping of the fast transmission of binary status services 38
Table 27 – Mapping of the ActivateOutput service 38
Table 28 – Mapping of the DeactivateOutput service 38
Table 29 – Mapping of the transmission of sampled values services 39
Table 30 – Mapping of the transmission of sampled values services 39
Table 31 – Mapping of the unsubscribe sampled values services 39
Table 32 – Mapping of the report sampled values services 40
Table 33 – Logical Node Identification 51
Table 34 - ISO/IEC 8802.3 Physical Characteristics 64

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 8 / 67 – 57/XXX/CD

INTERNATIONAL ELECTROTECHNICAL COMMISSION

____________

Substation Communication -

Part 9-1: Specific Communication Service Mapping (SCSM) for a serial

unidirectional multidrop point to point link

FOREWORD
1) The IEC (International Electrotechnical Commission) is a world-wide 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
liasing 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 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 61850-9-1 has been prepared by working group 12, of IEC
technical committee 57:

The text of this standard is based on the following documents:

FDIS Report on voting

Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 9 / 67 – 57/XXX/CD

INTRODUCTION

This part defines a specific communication service mapping for the serial unidirectional
multidrop point to point link. Figure 1 shows the general structure of the documents of
IEC 61850 as well as the position of the part defined in this document.

Part 7-2 of this standard defines the abstract communication service interface (ACSI). Part 7-
3 defines common data classes and attributes. Part 7-4 defines the compatible logical nodes
and the data object Addressing. Part 9-1 defines, how the abstract services and the data
object classes are mapped on a serial unidirectional multidrop point to point link.
Functionality, that is not covered by this link is defined within this part in order to fulfil the
abstract specifications of parts 7-1 to 7-4.

61850-9-1
Specific Communication
Service Mapping
61850-7-4
Compatible Logical Node and
Data Object Addressing
61850-7-3
Common Data Classes
and Attibutes
61850-7-2
Abstract Communication
Service Interface (ACSI)
61850-7-1
Communication Reference
Model
61850-5
Communication Requirements

Figure 1 - Relative position of this part of the standard

The definitions in this part are based on the following revisions of part 7:

th
CD IEC 61850-7-1: Rev. 1.0, February 27 , 1999, COMMUNICATION NETWORKS AND
SYSTEMS IN SUBSTATIONS - Part 7-1: Basic Communication Structure for substation and
feeder equipment - Communication Reference Model

th
CD IEC 61850-7-2: Rev. 1, February 6 , 1999, COMMUNICATION NETWORKS AND
SYSTEMS IN SUBSTATIONS - Part 7-2: Basic Communication Structure for substation and
feeder equipment - Abstract Communication Services Interface (ACSI)

th
CD IEC 61850-7-3: Rev. 1, February 6 , 1999, COMMUNICATION NETWORKS AND
SYSTEMS IN SUBSTATIONS – Part7-3: Basic Communication Structure for substation and
feeder equipment – Common Data Classes and Attributes

th
CD IEC 61850-7-4: Rev. 1, February 6 , 1999, COMMUNICATION NETWORKS AND
SYSTEMS IN SUBSTATIONS - Part 7-4: Basic Communication Structure for substation and
feeder equipment – Compatible Logical Node and Data Object Addressing

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 10 / 67 – 57/XXX/CD

Reading Guide

• For the understanding of this document it is absolutely required that the content of the
parts 7-1, 7-2, 7-3 and 7-4 of this standard is known and understood.

• The outline of this part follows the structure of the appropriate part 7-x documents.

• No explanations to the ACSI services are given in this part of the standard. For detailed
information about the use of the ACSI services refer to part 7-2.

• Behind every ACSI Service the appropriate Ethernet Service is defined. If a service is not
supported, this is also indicated.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 11 / 67 – 57/XXX/CD

COMMUNICATION NETWORKS AND SYSTEMS IN SUBSTATIONS

Part 9-1: Specific Communication Service Mapping (SCSM) serial

unidirectional multidrop point to point link

1 Scope

This part of IEC 61850 specifies the specific communication service mappings for the
communication between bay and process level and specially it specifies a mapping on a serial
unidirectional multidrop point to point link. The scope of this part is for the use in substations
as a link between electronic current- (ECT) or voltage-transducers (EVT) and bay devices
such as protection, meter or bay controller. The intended use of this mapping is for low cost
applications with simple protection schemes and retrofitting in existing substations only. If
higher requirements on sampling rate, inter-bay communication and synchronization apply
these will be covered by the process bus. Figure 2 shows the schematics of this interface.

Line Protection Bay Controller

Ethernet Ethernet
Controller Controller

Serial unidirectional
Multidrop point to point link

Multiple
diodes

Proprietary Ethernet
Controller
Synchronisation, monitoring, test
Link and configuration interfaces
Merging Unit
Proprietary
Link
Binary Inputs

Figure 2 - Example for the use of the serial unidirectional multidrop point to point link

In case of multiple merging units being installed in a substation they can be synchronized via
the synchronization interface. The synchronization source can either be a real-time clock or
another common source. The synchronization interface is specified in IEC 60044-8.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 12 / 67 – 57/XXX/CD

1.1 General

This part of IEC 61850 applies to newly manufactured electrical current and voltage
transducers (ECT and EVT) having a digital output, for use with electrical measuring
instruments and electrical protective devices.

The transducer technology can base on optical arrangements equipped with electronic
components, on air core coils (with or without a built-in integrator) or, on iron core coils with
integrated burden and use as a current to voltage converter, alone or equipped with electronic
components.

For digital output, this standard takes into account a point to point connection from the
electronic transducer to electrical measuring instruments and electrical devices.

This mapping allows interoperability between devices from different manufacturers.

This standard does not specify individual implementations or products, nor does it constrain
the implementation of entities and interfaces within a computer system. This standard
specifies the externally visible functionality of implementations together with conformance
requirements for such functionality’s.

Process bus communication and the final position of the point-to-point link definition within
the IEC standards are under consideration by TC 38 and TC 57.

1.2 General block diagram of electronic transducers

The applied technology decides which parts are necessary for realization of an electronic
transducer, i.e. not all described parts are needed, absolutely, to be in the transducer.

P1
Secondary S
Primary Primary Transmitting converter for use
sensor converter system with a merging
unit
P2 (digital output)

MR EF
Primary power
supply

Secondary S1
converter with
an analogue
EF: Equipment failure
voltage output
S2
MR: Maintenance request
MR EF

Secondary
power supply

Figure 3 - General block diagram of an single-phase electronic transducer

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 13 / 67 – 57/XXX/CD

1.3 General block diagram of electronic transducers with a digital output

Electronic transducers with digital output can be composed of any set of voltage transducers
and/or current transducers. Figure 4 gives an example for the configuration of an electronic
transducer.

SC of ECTa

SC of ECTb

SC of ECTc

SC of ECTd
Serial Link
Merging unit

SC of EVTa

and configuration
Synchronization,
test, monitoring
SC of EVTb
Power Supply

interfaces
SC of EVTc

SC of EVTd

SC of EVTe

Figure 4 - Example for electronic transducer configuration

Note : SC of EVTa is the secondary converter of the electronic voltage transducer of phase a (see IEC60044-7).
SC of ECTa is the secondary converter of the electronic current transducer of phase a (see IEC60044-8).

It is also allowed to create a merging unit with only one secondary converter of a transducer
attached.

The implementation of the merging unit as a standalone device is not a mandatory part in the
design of the ECT or EVT. It is also possible, that the merging unit is part of the ECT or EVT
electronics.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 14 / 67 – 57/XXX/CD

2 Normative References

The following normative documents contain provisions which, through reference in this text,
constitute provisions of this International Standard. At the time of publication, the editions
indicated were valid. All normative documents are subject to revision, and parties to
agreements based on this International Standard are encouraged to investigate the possibility
of applying the most recent editions of the normative documents indicated below. Members of
IEC and ISO maintain registers of currently valid International Standards.

IEC 60050(371): 1984, International Electrotechnical Vocabulary – Chapter 371: Telecontrol

IEC 60794-1: 1996, Optical fiber cables – Part 1: Generic specification

IEC 60794-2: 1989, Optical fiber cables – Part 2: Product specifications

IEC 870-5-3: 1992, Telecontrol equipment and systems - Part 5: Transmission protocols -
Section 3: General structure of application data

IEC 870-5-4: 1993, Telecontrol equipment and systems - Part 5: Transmission protocols -
Section 4: Definition and coding of application information elements

IEC 870-5-101: 1995, Telecontrol equipment and systems - Part 5: Transmission protocols -
Section 101: Companion standard for basic telecontrol tasks

IEC 60870-5-103: 1997, Telecontrol equipment and systems - Part 5: Transmission protocols
- Section 103: Companion standard for the informative interface of protection equipment

ISO/IEC 8802.2: 1998, Information technology--Telecommunications and information

exchange between systems--Local and Metropolitan area networks--Specific requirements--
Part 2: Logical link control

Note: See also http://standards.ieee.org/catalog/index.html

IEEE 802.3: 1998, Information technology--Telecommunications and information exchange

between systems--Local and metropolitan area networks--Specific requirements--Part 3:
Carrier sense multiple access with collision detection (CSMA/CD) access method and
physical layer specifications.
Note: This edition includes all contents of the 8802-3:1996 Edition, plus IEEE Std 802.3aa-1998, IEEE Std 802.3r-
1996, IEEE Std 802.3u-1995, IEEE Std 802.3x&y-1997, and IEEE802.3z-1998.

Note: See also http://standards.ieee.org/catalog/index.html

IEC 60874 - 2 : 1993, Connectors for optical fibers and cables - Part 2 : Sectional
specification for fiber optic connector - Type FSMA

IEC 60874 - 10 : 1992, Connectors for optical fibers and cables - Part 10 : Sectional
specification for fiber optic connector - Type BFOC/2,5

RFC894: Standard for the transmission of IP datagrams over Ethernet networks. C. Hornig.
Apr-01-1984. (Status: STANDARD)

ISO/IEC 7498-1: 1994, Information technology – Open Systems Interconnection – Basic

Reference Model: The Basic Model

CD IEC 60044-8 (38/225/CD) : 1998 , Instrument Transformers – Part 8: Electronic current

transducers

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 15 / 67 – 57/XXX/CD

3 Definitions

For the purpose of this International Standard, the definitions of IEC 61850-2, IEC 60044-7
and IEC 60044-8 apply.

Hub
A Hub is a active network component. Each port of a hub links individual
Ethernet media segments together to create a larger network that operates as a
single Ethernet LAN. Collisions in the network are possible

Switch
A switch is a active network component. Switches connect two or more sub
networks, which themselves could be built of several segments connected by
repeaters. Switches build up the borders for so called collision domains.
Collisions can not take place between networks divided by switches, and data
packets destined to a specific sub network do not appear on the other sub
networks. To achieve this switches must have a knowledge of the hardware
addresses of the connected stations. In cases where only one active network
component is connected to a switch port collisions on the network can be
avoided.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 16 / 67 – 57/XXX/CD

4 Abbreviations

ACSI Abstract Communication Service Interface

ALPDU Application Layer Protocol Data Unit
ASDU Application Specific Data Unit
AUI Attachment Unit Interface
CSMA / CD Carrier Sense Multiple Access / Collision Detection
DF Data Frame
DO Data Object
ECT Electronic Current Transducer
EVT Electronic Voltage Transducer
LLC Logical Link Control
LSDU Link Layer Service Data Unit
MAC Media Access Control
PDU Protocol Data Unit
SBO Select Before Operate
SC Secondary Converter
SCSM Specific Communication Services Mapping
SI Status Indication

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 17 / 67 – 57/XXX/CD

5 Principal of Mapping to serial unidirectional multidrop point to point link

This chapter gives an overview of the mapping to serial unidirectional multidrop point to point
link. It defines the communication stack and where additional definitions are defined by this
document. Restrictions to the application that are a consequence of this mapping are defined
as well.

5.1 Communication Stack

Figure 5 gives an overview of the communication stack. The link layer is conforming to
ISO/IEC 8802.2 standard. This standard is usually referred to as Ethernet. In the following
Ethernet will be used instead of ISO/IEC 8802.3 CSMA/CD.

SCSM for ISO/IEC 8802.2:

Definition of ASDU's Application Layer

Empty
Presentation Layer

Empty
Session Layer

Empty
Transport Layer

Empty
Network Layer

LLC - Sublayer
ISO/IEC 8802.2

MAC - Sublayer Link Layer

IEEE 802.3

AUI -Interface
IEEE 802.3

100BaseFX 10BaseFL Physical Layer

IEEE 802.3 IEEE 802.3

Figure 5 - Communication Stack

In Annex B a short introduction to Ethernet is given. Whether 100BaseFX or 10BaseFL shall

be used will be specified by the relevant device standards, depending on the application.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 18 / 67 – 57/XXX/CD

The following tables can be used as a guideline for the selection of the appropriate link layer:

Table 1 – Selection guide for Ethernet link layer (receiving node)

Sampling Rate Number of connected transducers

1 2 3 3–5
10 x f r 10 Mbps 10 Mbps 10 Mbps 10 Mbps
20 x f r 10 Mbps 10 Mbps 10 Mbps 10 Mbps
40 x f r 10 Mbps 10 Mbps 10 Mbps 100 Mbps
80 x f r 10 Mbps 100 Mbps 100 Mbps 100 Mbps
200 x f r 100 Mbps 100 Mbps 100 Mbps 100 Mbps
400 x f r 100 Mbps 100 Mbps 100 Mbps n/a

Note: The available bandwidth of 100 Mbps Ethernet is not sufficient to allow three or more transducers transmit
their samples to one receiving device

Table 2 – Selection guide for Ethernet link layer (sending node)

Sampling Rate 1
10 x f r 10 Mbps
20 x f r 10 Mbps
40 x f r 10 Mbps
80 x f r 10 Mbps
200 x f r 100 Mbps
400 x f r 100 Mbps

5.1.1 Physical Layer

5.1.1.1 Specifications for the Medium Attachment Unit (MAU)

The connection of the merging unit to the secondary equipment is shall be a fiber optic
transmission system. A copper based transmission system is not covered by this standard
due to the electromagnetic environment.

5.1.1.2 Fiber optic transmission system

The preferred version of the fiber optic transmission system is according to ISO/IEC 8802.3
the 10BaseFL. In addition to that the 100BaseFX fiber optic transmission system according to
ISO/IEC 8802.3 is possible. This interface shall be used for applications where this media
interface is already used for other communication links.

Editors Note: The selection of allowed connectors should be discussed

5.1.2 Link Layer

ISO/IEC 8802.2 is used as link layer for the serial unidirectional multidrop point to point link.
Conformance Class 1 is used for the Link Layer.

As destination address the Ethernet broadcast address shall to be used, which is all ones in
the destination address field. As source address a unique Ethernet address shall be used.

Note: The Ethernet address (also called MAC address) is often already coded into the Ethernet controller.
th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 19 / 67 – 57/XXX/CD

If the length of the data link protocol data unit is less then 46 bytes, pad bytes must be added
to guarantee the minimum frame length.

Note: Pad bytes are usually added by the Ethernet controller.

5.1.3 Network Layer

This layer is intentionally left empty

5.1.4 Transport Layer

This layer is intentionally left empty

5.1.5 Session Layer

This layer is intentionally left empty

5.1.6 Presentation Layer

This layer is intentionally left empty

5.1.7 Application Layer

The behavior as well as the data formats and data structures of the application layer are
described in the following clause.

All application layer protocol data units (ALPDU) shall be blocked in a data frame (DF) as
shown in Figure 6. A data frame consists of one or more ALPDUs.

8 7 6 5 4 3 2 1

msb
Header No. of blocks
lsb

Process
Block 1
data

*
*
*

Process
Block n
data

Figure 6 – Data frame (DF) for the blocking of ALPDUs

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 20 / 67 – 57/XXX/CD

The data frame starts with a header containing the number of data blocks to be transmitted
within this frame.

For the No. of blocks the following definitions apply.

No. of blocks := UI16[1..16] <1..71>

The total size of the data blocks and the header shall not exceed 1500 octets, as defined in
IEEE 802.3. The minimum length of an ALPDU is 19 octets. Therefore the maximum No. of
blocks is 71.

5.1.7.1 Application Layer Protocol Data Unit (ALPDU)

The ACSI describes abstract services. They create objects with different attributes which
shall be transported via the link described in this mapping. The objects applicable for this
mapping are set apart in Statusindications, Measurands and Current and Voltage Transducer
Samples. The ACSI data objects and Common Data Classes are mapped to an application
protocol data unit inside the point to point link. The structure of the application layer protocol
data unit (ALPDU) is given in Figure 7:

Octets 8 7 6 5 4 3 2 1

1 msb
Length
2 lsb
Header
3 msb Data Group lsb

4 msb Reserved lsb

Data

Figure 7 – ALPDU – Application Layer Protocol Data Unit

ALPDU := STRUCT{
Length := UI16[1..16],
DataGroup := ENUM8[17..24],
Reserved := UI8[25..32],
Data := OSTRI
}

The length field contains the length of the ALPDU. The length is given in octets and is
calculated as the length of one ALPDU without the Header (Length, Data Group and
Reserved). The length 0 is reserved.

The DataGroup fields contains the description of the type of data contained in the ALPDU.
Allowed values are given in Table 3.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 21 / 67 – 57/XXX/CD

Table 3 – Enumeration of DataGroup Identifier

Value Description Comment

0 Invalid
1 Process Data Group For future use only
2 Data Set Group
3 – 255 Reserved for future use

The Process Data Group is already defined for future extensions of the standard, but shall not
be used for the transmission of sampled values.

5.1.7.2 Description of the Process Data Group

The Process Data Group shall be used for the transmission one and only one data object,
represented by a common data class. The length of the DataObject file may vary according to
the length of the common data class. The common data classes are specified in chapter 19.

1 msb CommonDataClassIdent lsb

2 msb Reserved lsb

DataObject

Figure 8 – Process Data Group

PDG := STRUCT{
CommonDataClassIdent := UI8[1..8],
Reserved := UI8[9..16],
DataObject := OSTRI
}

The CommonDataClassIdent field contains the description of the data object type. Possible
values are given in Table 4.

Table 4 – Enumeration of CommonDataClassIdentifier

Value Description Value Description

0 Invalid 9 Binary Counter Reading
1 Single Point Status 10 Harmonic Value
2 Double Point Status 11 WYE
3 Step Position Information 12 Delta
4 Status Indication Group 13 Sequence
5 Integer Status 14 Phase
6 Single Point Control 15 Analogue Setpoint
7 Double Point Control 16 Integer Setpoint
8 Measured Value
th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 22 / 67 – 57/XXX/CD

5.1.7.3 Description of the Data Set Group

The structure of the data group for data sets is shown in Figure 9.

Octets 8 7 6 5 4 3 2 1

1 msb DataSetIdentifier lsb

2 msb Number of Data Objects lsb

3 lsb
Reserved
4 msb

DataObjects

lsb

TimeStamp

msb

msb TimeQuality lsb

Figure 9 – Data Set Group

DSG := STRUCT{
DataSetIdentifier := UI8[1..8],
NumberOfDataObjects := UI8[9..16],
Reserved := UI16[17..32],
DataObjects := OSTRI
TimeStamp := 40BitBinaryTime
TimeQuality := TimeStampQuality
}

The DataSetIdentifier is a unique number for the structure of the dataset. For the purpose of
this standard the data sets are predefined. The enumeration of the indexes is given in
Annex A.

Additional data sets can be specified user specific by parameterization. These data sets are
only valid in the communication system they are specified for. The use of such data sets
does not guarantee interoperability between different vendors.

The NumberOfDataObjects specifies the number of Data Objects in the data set.

All DataObjects of a data set shall have the same TimeStamp. Therefore the individual
TimeStamps of the DataObjects shall not be transmitted.

The Table 5 specifies the reserved DataSetIdentifier values.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 23 / 67 – 57/XXX/CD

Table 5 – Enumeration of reserved DataSetIdentifier values

Value Description
0 Invalid
1 Universal Use (IEC 60044-8)
2 Current Samples
3 Voltage Samples
4 Busbar voltages
5 Binary Statusinformation
6– 127 Reserved for future use
128 – 255 user specific extensions

5.2 Restrictions

The use of this interface is restricted to the communication between the ECT/EVT related
merging unit and devices on bay level which need raw data of ECT and/or EVT for their
algorithms. The main purpose of this interface is to communicate sampled analogue values
including quality and time tag.

Using the mapping to the serial unidirectional multidrop point to point link implies some
restrictions to the application:

• In a network segment using this mapping only one server is allowed. This server is part
of the merging unit.

• The use of the synchronization interface is optional. The synchronization interface shall
only be used in cases, where data from different merging units are computed together in
an algorithm that requires coherent data.

• As far as possible the station bus defined in part 8 of this standard shall be used for the
synchronization of the merging units.

• In applications where a device receives data from more than one merging unit network
switches shall be used to serialize the data and to avoid the need for more than one
communication interface in the device. In this case the MAC–address of the merging unit
in the source address field shall be used to identify the source of the data.

Bay device

Switch

Merging Unit Merging Unit Merging Unit

Figure 10 – Serialization of sample data with a switch

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 24 / 67 – 57/XXX/CD

6 Mapping of the Device Model

6.1 Overview

The table below shows the mapping of the elements of the ACSI device model on the data
structure.

Table 6 – Mapping of the device model

ACSI Object Ethernet Object

Physical Device Node

Server Implicit
Logical Device Not accessible
LD0 Not supported
Logical Node Class Not accessible
LN0 Not supported
Data Object Class Data Link Protocol Data Unit

6.2 Mapping of the objects

Table 7 – Mapping of the physical device

ACSI Object: Physical Device Ethernet Object: Physical Device

&PDReference Source Address

&ListOfServerObjects Not supported

6.3 Additional definitions for the device model

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 25 / 67 – 57/XXX/CD

7 Mapping of the server class

The server class comprises the externally visible behavior of an application process. A
server represents the real device to the client by providing capabilities that may be used by
the client in order to effect some control or monitoring (or both) activity through the server.

7.1 Mapping of the server class structure

Table 8 – Mapping of the server class definition

ACSI: Server Class Structure Ethernet: Server Class Structure

specificCommunicationServiceMapping Serial Unidirectional Multidrop Point to Point Link

associationModel FALSE
basicDataObjectModel TRUE
subsribedDataTransferModel FALSE
dataSetObjectmodel TRUE
deviceControlServiceModel FALSE
fileTransferModel FALSE
timeModel FALSE
TransmissionOfSampledValuesModel TRUE
fastControlOfBinaryOutputsModel TRUE
substitutionModel FALSE
listOfCapabilities Not accessible
listOfScopes Not accessible
listOfBasicDataObjects Not accessible
listOfDataSetObjects Not accessible
listOfLogObjects Not accessible
clientAssociations Not accessible

7.2 Mapping of the server class services

Not supported

7.3 Additional definitions for the server class

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 26 / 67 – 57/XXX/CD

8 Mapping of the association model

The association model defines the environment of the communication interface, as well as
the services and capabilities provided for managing connections between clients and
servers.

For the point to point link an explicit association model is not needed, since all information
are transmitted connectionless, using broadcast services.

8.1 Mapping of the association class definition

Not supported

8.2 Mapping of the association services

Not supported

8.3 Additional definitions for association model

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 27 / 67 – 57/XXX/CD

9 Mapping of the basic data class

A basic data class is an element of a real system which is capable of providing and/or
accepting (get and set service) a typed data value. A basic data class is defined to
represent one or many data elements each with (1) no substructure (i.e., one very simple
measurement point such as a voltage value), or (2) a hierarchical data structure.

9.1 Mapping of the basic data class description

Table 9 – Mapping of the basic data class definition

ACSI Object: Data Object Ethernet: Data Object

dataObjectName InformationObjectAddress
readable FALSE
writeable FALSE
reportable TRUE
substitutable FALSE
deletable FALSE
scope Null
dataType DataObjectClass
accessControl Not supported
value Value
localResource Not supported

9.2 Mapping of the basic data object access services

Table 10 – Mapping of the basic data object access services

ACSI: basic data object access services Ethernet: LLC-Service

GetDataObjectValues Not supported
SetDataObjectValues Not supported
UnsolicitedDataObjectValuesReport Not supported
SetDataObjectValues(Unconfirmed) Not supported
GetDataObjectAttributes Not supported
CreateDataObject Not supported
DeleteDataObject Not supported
GetDataObjectNames Not supported

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 28 / 67 – 57/XXX/CD

9.3 Mapping of the basic data types

9.3.1 OSTRi

Table 11 – Mapping of the octet string data type

ACSI data type Ethernet: Data Type

OSTRi Octet String 1 to i length Not supported

9.3.2 Printable ASCII text string

Table 12 – Mapping of the ASCII text string data type

ACSI data type Ethernet: Data Type

VSTR8 - 8 characters Not supported
VSTR16 - 16 characters Not supported
VSTR32 - 32 characters Not supported
VSTRi – 1 to i characters Not supported
VSTR – null terminated Not supported
IDENT Not supported

9.3.3 SET OF BOOLEAN

Table 13 – Mapping of the Boolean data type

ACSI data type Ethernet: Data Type

BOOL – Boolean – 1 bit, True (1) or False (0) Not supported
BS2 – Set of Boolean 2 bits Not supported
BS8 – Set of Boolean 8 bits Not supported
BS16 – Set of Boolean 16 bits BS16
BS32 – Set of Boolean 32 bits Not supported
BSi – Set of Boolean 1 to i bits Not supported

9.3.3.1 Bitstring16 (BS16) (assembly of independent bits)

BS16 := BS16[1..16] = status register of size 16

BS16[n] := S n <0..1> = status bit in position n

Octets 8 7 6 5 4 3 2 1

1 S7 S6 S5 S4 S3 S2 S1 S0

2 S 15 S 14 S 13 S 12 S 11 S 10 S9 S8

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 29 / 67 – 57/XXX/CD

9.3.4 Unsigned Integer

Table 14 – Mapping of the unsigned integer data type

ACSI data type Ethernet: Data Type

UI8 – Unsigned Integer 8 bits, 0 to 255 UI8
UI16 – Unsigned Integer 16 bits, 0 to 65,535 UI16
UI32 – Unsigned Integer 32 bits, 0 to 4,294,967,295 UI32
UIi – Unsigned Integer i bits, 0 to 255 (IEC 870-5-4, Not supported
clause 5.2.1)

9.3.4.1 Unsigned Integer 8 bits (UI8) (positive whole number)

UI8 := UI8[1..8] <0..2 8 -1>

Octets 8 7 6 5 4 3 2 1

1 27 26 25 24 23 22 21 20

9.3.4.2 Unsigned Integer 16 bits (UI16) (positive whole number)

UI16 := UI16[1..16] <0..2 16 -1>

Octets 8 7 6 5 4 3 2 1

1 27 26 25 24 23 22 21 20

2 2 15 2 14 2 13 2 12 2 11 2 10 29 28

9.3.4.3 Unsigned Integer 32 bits (UI32) (positive whole number)

UI32 := UI32[1..32] <0..2 32 -1>

Octets 8 7 6 5 4 3 2 1

1 27 26 25 24 23 22 21 20

2 2 15 2 14 2 13 2 12 2 11 2 10 29 28

3 2 23 2 22 2 21 2 20 2 19 2 18 2 17 2 16

4 2 31 2 20 2 29 2 28 2 27 2 26 2 25 2 24

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 30 / 67 – 57/XXX/CD

9.3.5 Integer

Table 15 – Mapping of the integer data type

ACSI data type Ethernet: Data Type

I8 – Signed Integer 8 bits, -128 to +127 I8
I16 – Signed Integer 16 bits, -32,768 to + 32,767 I16
I32 – Signed Integer 32 bits, -2,147,483,648 to I32
+2,147,483,647
Ii – Signed Integer i bits (IEC 870-5-4, clause 5.2.1) Not supported

9.3.5.1 Integer 8 bits (I8) (negative or positive whole number)

I8 := I8[1..8] <-2 7 ..2 7 -1>

Octets 8 7 6 5 4 3 2 1

1 S 26 25 24 23 22 21 20

9.3.5.2 Integer 16 bits (I16) (negative or positive whole number)

I16 := I16[1..16] <-2 -15 ..2 15 -1>

Octets 8 7 6 5 4 3 2 1

1 27 26 25 24 23 22 21 20

2 S 2 14 2 13 2 12 2 11 2 10 29 28

9.3.5.3 Integer 32 bits (I32) (negative or positive whole number)

I32 := I32[1..32] <-2 31 ..2 31 -1>

Octets 8 7 6 5 4 3 2 1

1 27 26 25 24 23 22 21 20

2 2 15 2 14 2 13 2 12 2 11 2 10 29 28

3 2 23 2 22 2 21 2 20 2 19 2 18 2 17 2 16

4 S 2 20 2 29 2 28 2 27 2 26 2 25 2 24

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 31 / 67 – 57/XXX/CD

9.3.6 Unsigned Fixed Point Number

Table 16 – Mapping of the unsigned fixed point number data type

ACSI data type Ethernet: Data Type

UF8 - IEC 870-5-4, clause 5.3.1 Not supported
UF16 - IEC 870-5-4, clause 5.3.1. Not supported
UF32 - IEC 870-5-4, clause 5.3.1. Not supported
UFi -IEC 870-5-4, clause 5.3.1. Not supported

9.3.7 Fixed Point Number

Table 17 – Mapping of the fixed point number data type

ACSI data type Ethernet: Data Type

F8 - IEC 870-5-4, clause 5.4.1. Not supported
F16 - IEC 870-5-4, clause 5.4.1. Not supported
F32 - IEC 870-5-4, clause 5.4.1. Not supported
Fi - IEC 870-5-4, clause 5.4.1. Not supported

9.3.8 Short Real IEEE Std 754

Table 18 – Mapping of the short real IEEE Std 754 data type

ACSI data type Ethernet: Data Type

R32.23 - IEC 870-5-4, clause 6.5. Not supported

9.3.9 Real IEEE Std 754

Table 19 – Mapping of the real IEEE Std 754 data type

ACSI data type Ethernet: Data Type

R64.53 Not supported

9.3.10 Time

Table 20 – Mapping of the time data type

ACSI data type Ethernet: Data Type

Time_Type_1 Not supported
Time_Type_2 Not supported
Time_Type_3 40BitBinaryTime
Time_Type_4 Not supported

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 32 / 67 – 57/XXX/CD

9.3.10.1 40BitBinaryTime

Relative time in 1 microseconds since midnight (UTC). The ACSI Time_Type_3 maps to to
the 40 Bit Binary Time, which allows the transmission of time tags down to the
microseconds.

40BitBinaryTime := UI40[1..40] <0..2 40 -1>

Octets 8 7 6 5 4 3 2 1

1 27 20

2 2 15 28

3 2 23 1 Microseconds 2 16

4 2 31 2 24

5 2 39 2
32

9.3.11 ENUM

Table 21 – Mapping of the enum data type

ACSI data type Ethernet: Data Type

ENUM8 - Enumerated value, 8 bits, signed – Well known ENUM8
values positive, 0 always reserved and unused
ENUM16 – Enumerated value, 16 bits, signed – Well Not supported
known values positive, 0 always reserved and unused

9.3.11.1 Enumeration 8 bits (ENUM8)

ENUM8 := I8[1..8] <-2 7 ..2 7 -1>

Octets 8 7 6 5 4 3 2 1

1 27 26 25 24 23 22 21 20

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 33 / 67 – 57/XXX/CD

9.4 Mapping of the structured data types

9.4.1 Structure

Table 22 – Mapping of the structure data type

ACSI data type Ethernet: Data Type

STRUCT – Structure of 1 to many components Not supported

9.4.2 Array

Table 23 – Mapping of the array data type

ACSI data type Ethernet: Data Type

ARRAY - <TYPE>[I][j][k] ..ARRAY elements for three Not supported
dimensions of TYPE

9.4.3 SI units

Not supported

9.5 Data object Names

Data object names are not supported in the mapping. The incidence between the
DataObjectIdentifier and the data object name shall be ensured by the engineering tool or
by agreement between the vendors of the client and server.

9.5.1 Data object Names: Scope designator

The basic data object class definition is contained in the server model, therefore the scope
of the data object names is null.

9.6 Additional definitions for the basic data types

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 34 / 67 – 57/XXX/CD

10 Mapping of the data set class

Some of the communication services require a mechanism to specify arbitrary, although

ordered, groups of data objects. A common example is when the same groups of arbitrary
data objects are required to be transmitted to one or more clients over and over again,
possibly on an exception basis. It is convenient to establish a single name for the collection,
with a mutual understanding of its definition by both client and server.

A data set is an ordered grouping of data objects, organized as a single collection for the
convenience of the client. It references different data objects. The data objects referenced
within a data set can be from anywhere in the object hierarchy (i.e., substructures contained
in more complex objects). The membership and order of the data objects in a data set are
known to both the client and the server, so that only the name of the data set plus the actual
values of the referenced data objects need to be transmitted. This capability thus permits
more efficient use of the communications bandwidth. Data sets may be pre-defined by the
server, or may be defined through requests by the client.

The grouping of data objects into one or more data sets is not constrained by the type
description of the data object. Any basic data object may have membership in one or more
data sets. A data set may refer to the same basic data object one or more times.

10.1 Mapping of the data set class definition

Table 24 – Mapping of the data set class definition

ACSI data set class Ethernet: Data Set

DataSetName InformationObjectAddress
Readable FALSE
Writeable FALSE
Reportable TRUE
Substitutable FALSE
Deletable FALSE
Scope Null
AccessControl Not supported
ListOfbasicDataObjectNames Supplied by local configuration

10.2 Mapping of the data set access services

Table 25 – Mapping of the data set access services

ACSI: Data Set Access Services Ethernet: Data Set Access Services
GetDataSetValues Not supported
UnsolicitedDataObjectValuesReport Not supported
GetDataSetElementNames Not supported
CreateDataSet Implicit (parameterization tool)
DeleteDataSet Not supported

10.3 Additional definitions for the data set class

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 35 / 67 – 57/XXX/CD

11 Mapping of the subscribed data transfer model

The subscribed data transfer service model provides a filter (that reduces the amount of
data to be sent) of transferring data from the server to the client. The subscribed data
transfer service model permits the client to perform a single transaction to set up report
configuration parameters. The server repeatedly reports data or data set object values
without further client actions.

For the point to point link it is not possible to perform a subscription due to the unidirectional
character of the interface.

11.1 Mapping of the event control model

Not supported

11.1.1 Mapping of the event control services

Not supported

11.1.2 Additional definitions for the event control model

No definitions

11.2 Mapping of the report model

Not supported

11.2.1 Mapping of the report services

Not supported

11.2.2 Additional definitions for the report model

No definitions

11.3 Mapping of the log model

Not supported

11.3.1 Mapping of the log services

Not supported

11.3.2 Additional definitions for the log model

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 36 / 67 – 57/XXX/CD

12 Mapping of the control class

The control class is a specialization of the basic data class. The behavior of the basic data
class is improved by adding

• specification of specific services

• a behavior described with a state machine
• configuration attributes

The control class defines the services to control the primary process ( e.g. Trip and Close of
a circuit breaker ).

For the point to point link it is not possible to perform a control due to the unidirectional
character of the interface.

12.1 Mapping of the direct control without enhanced security

Not supported

12.2 Mapping of the direct control with enhanced security

Not supported

12.3 Mapping of the SBO with enhanced security

Not supported

12.4 Mapping of the control object services

Not supported

12.5 Additional definitions for the control model

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 37 / 67 – 57/XXX/CD

13 Mapping of the substitution model

The substitution model allows for the manual substitution of values of status or measurand
data objects that are used for reporting controlled by a report control object.

For the point to point link it is not possible to perform a substitution due to the unidirectional
character of the interface.

13.1 Mapping of the services on indication objects

Not supported

13.2 Additional definitions for the substitution model

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 38 / 67 – 57/XXX/CD

14 Mapping of the fast transmission of binary status model

This model provides the possibility for a fast distribution of binary signals. The client has the
possibility to activate and to deactivate a binary output. The transmission delay is less than
10 ms. The model shall be used for the distribution of general purpose I/O information.

The state is transmitted with a timestamp that indicates the time, when the client generated
the signal. When the server receives a frame, he can use the timestamp to decide, if it is
still valid. This enables the detection of old frames that have been stored in the
communication network.

14.1 Mapping of the fast transmission of binary status services

Table 26 – Mapping of the fast transmission of binary status services

ACSI services Ethernet services

ActivateOutput Supported by local configuration
DeactivateOutput Not Supported

14.1.1 Mapping of the ActivateOutput service

Table 27 – Mapping of the ActivateOutput service

ACSI services Ethernet services

Request L_DATA.request (server)
DataObjectIdentification DataSetIdentifier
Value StatusIndicationGroup

14.1.2 Mapping of the DeactivateOutput service

Table 28 – Mapping of the DeactivateOutput service

ACSI services Ethernet services

Request Not supported
DataObjectIdentification Not supported
Value Not supported

14.2 Additional definitions for the fast control of binary outputs model

The transmission of binary outputs shall be configured before startup of the device. The
transmission will be cyclical with a configured cycle time. When a status changes this will be
indicated by setting the change bit in the status indication group. The change bit shall be
reset after the transmission of the actual value of the status indication group.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 39 / 67 – 57/XXX/CD

15 Mapping of the transmission of sampled values model

This model offers the possibility, to transmit sequences of sampled values. The purpose is,
to transmit sampled analogue values from digital instrumental transformers.

15.1 Mapping of the transmission of sampled values services

Table 29 – Mapping of the transmission of sampled values services

ACSI services Ethernet services

SubscribeSampledValue Implicit
UnsubscribeSampledValues Not Supported
ReportSampledValues L_DATA.request (server)

15.1.1 Mapping of the Subscribe Sampled Values Service

Table 30 – Mapping of the transmission of sampled values services

ACSI services Ethernet services

Request Implicit
DatasetIdentification DataSetIdentifier
SamplingRate Fixed (by parameterization)
Response+ Implicit
Response- Not Supported
ErrorType Not Supported
SamplingRateNotSupported Not Supported
MaxSamplingRate Not Supported

The allowed sampling rates are specified in IEC 60044-8.

15.1.2 Mapping of the Unsubscribe Sampled Values Service

Table 31 – Mapping of the unsubscribe sampled values services

ACSI services Ethernet services

Request Not Supported
DatasetIdentification Not Supported
Response+ Not Supported
Response- Not Supported
ErrorType Not Supported

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 40 / 67 – 57/XXX/CD

15.1.3 Mapping of the Report Sampled Values Service

Table 32 – Mapping of the report sampled values services

ACSI services Ethernet services

Request L_DATA.request (server) / L_DATA.indication (client )
DatasetIdentification DataSetIdentifier
NumberOfSetOfDatasetValues Not supported
SequenceOfDatasetValues Data Set Group
TimeStamp TimeStamp

15.2 Additional definitions for the transmission of sampled values model

No definitions

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 41 / 67 – 57/XXX/CD

16 Mapping of the Time model

Not specified in IEC 61850-7-2.

16.1 Additional definitions for the time model

In applications where the synchronization interface is used, the synchronization source must
be able to provide sufficient accuracy for the application.

In cases where no synchronization source is available, or synchronization is done without a

real-time clock, a wrap around counter value shall be transmitted instead of the time tag.
The counter value shall be incremented by one in every frame sent. The counter shall be set
to zero, when a synchronization pulse arises.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 42 / 67 – 57/XXX/CD

17 Mapping of the file transfer model

File transfer is used, to transfer files between a client and a server. The splitting of the file
into different sections that may be handled by the communication link is a task of the
communication layers.

For the point to point link it is not possible to perform a file transfer due to the unidirectional
character of the interface.

17.1 Mapping of the file transfer services

Not supported

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 43 / 67 – 57/XXX/CD

18 Mapping of the common attribute classes

18.1 Mapping of the Command Qualifier Attribute

In the context of this mapping commands are not supported, therefore the command
qualifier attribute is not mapped-

18.2 Mapping of the Description Attribute

Not supported

18.3 Mapping of the Originator Attribute

In the context of this mapping the originator is always “Process”. This means that the
originator is implicitly known and it is not necessary o transmit the originator attribute.

18.4 Mapping of the Quality Attribute

The quality attribute maps to the following structure:

Quality := STRUCT{
Reserved := BS1[1],
externalError := BS1[2],
notTopical := BS1[3],
substituted := BS1[4],
Reserved := BS1[5],
blocked := BS1[6],
invalid := BS1[7],
overFlow := BS1[8],
}

Octets 8 7 6 5 4 3 2 1

1 OF IV BL RE SU NT EE RE

18.5 Mapping of the Time Stamp Quality Attribute

The TimeStampQuality Attribute maps to the following structure:

TimeStampQuality := STRUCT{
Counter := BS1[1],
StandardTime := BS1[2],
Synchronized := BS1[3],
Invalid := BS1[4],
Reserved := BS4[5..8],
}

Octets 8 7 6 5 4 3 2 1

1 Reserved IV SY ST CO

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 44 / 67 – 57/XXX/CD

18.6 Mapping of the Reason for Status Change Attribute

In the context of this mapping the Reason for Status Change is always “SPONTANEOUS”,
therefore the attribute is not mapped.

18.7 Mapping of the Sampling Rate Attribute

In the context of this mapping the sampling rate can not be changed during operation,
therefore the Sampling Rate Attribute will not be transmitted with each sample and is
therefore not mapped.

18.8 Mapping of the TimeStamp Attribute

The TimeStamp Attribute maps to the following:

TimeStamp := 40BitBinaryTime

Octets 8 7 6 5 4 3 2 1

1 27 20

2 2 15 28

3 2 23 1 Microseconds 2 16

4 2 31 2 24

5 2 39 2
32

The TimeStamp always refers to UTC and contains the number of microseconds since
midnight. If time is not standard time, or the time zone is not UTC, then this shall be handled
in the HMI. The TimeStamp shall not be changed when time changes between standard
time and daylight saving time.

18.9 Mapping of the Units Attribute

Units := ENUM8

Octets 8 7 6 5 4 3 2 1

1 27 26 25 24 23 22 21 20

The enumeration of allowed values for the units attribute is given in part 7-2.

18.10 Mapping of the Tag Type Attribute

Not supported

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 45 / 67 – 57/XXX/CD

18.11 Mapping of the Analog Value Attribute

The Analog Value Attribute maps to the following:

31 31
AnalogValue := I32[1..32] <-2 ..2 -1>

Octets 8 7 6 5 4 3 2 1

1 27 26 25 24 23 22 21 20

2 2 15 2 14 2 13 2 12 2 11 2 10 29 28

3 2 23 2 22 2 21 2 20 2 19 2 18 2 17 2 16

4 S 2 30 2 29 2 28 2 27 2 26 2 25 2 24

This type is defined for the transmission of technological values such as current and voltage
as sampled analogue values.

The rated value of the samples is defined in IEC 60044-8.

18.12 Mapping of the Configuration of Scaled Analog Value (SVC)

In the context of this mapping the Configuration of Scaled Analogue Values is given by local
configuration and therefore is not mapped here.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 46 / 67 – 57/XXX/CD

19 Mapping of the Common Data Class Specifications

19.1 Mapping of the Data Class Specification for Status Information

19.1.1 Mapping of the Single Point Status

Not supported

19.1.2 Mapping of the Double Point Status

Not supported

19.1.3 Mapping of the Step Position Information

Not supported

19.1.4 Mapping of the Status Indication Group

The Status Indication Group maps to the following:

SIG : = STRUCT{
GroupValue := BS1[1..16], <0 : OFF> <1 : ON>
ChangeIndication := BS1[17..32] <0 : No Change> <1 : Change>
q := Quality[33..40]
Reserved := BS8[41..48]
t := TimeStamp[49..88] Optional
tq := TimeStampQuality[89..96] Optional
}

Octets 8 7 6 5 4 3 2 1

1 Group S8 S7 S6 S5 S4 S3 S2 S1

2 Value S16 S15 S14 S13 S12 S11 S10 S9

3 Change C8 C7 C6 C5 C4 C3 C2 C1

4 Indicat. C16 C15 C14 C13 C12 C11 C10 C9

5 q OF IV BL RE SU NT EE RE

6 Reserv Reserved

7 27 20

8 2 15 28

9 t 2 23 1 Microseconds 2 16

10 2 31 2 24

11 2 39 2 32

12 tq Re Re Re Re IV SY ST CO

A description is not supported. There is a one to one relationship between the position of the
status information and the position of the change bit in the status word.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 47 / 67 – 57/XXX/CD

19.2 Mapping of the Attribute Class Specifications for Control Information

19.2.1 Mapping of the Single Point Control

Not supported

19.2.2 Mapping of the Double Point Control

Not Supported

19.3 Mapping of the Attribute Class Specifications for Measurands Information

19.3.1 Mapping of the Measured Value Class

The Measured Value class maps to the following structure:

MeasuredValue := STRUCT{
value := AnalogValue [1..32];
q := Quality [33..40];
Reserved := BS8 [41..48] Optional;
t := TimeStamp [49..88] Optional;
tq := TimeStampQuality [89..96] Optional;
}

Octets 8 7 6 5 4 3 2 1

1 27 20

2 2 15 28
value AnalogValue
3 2 23 2 16

4 S 2 24

5 q OF IV BL RE SU NT EE RE

6 Reserv Reserved

7 27 20

8 2 15 28

9 t 2 23 1 Microseconds 2 16

10 2 31 2 24

11 2 39 2 32

12 tq Re Re Re Re IV SY ST CO

19.3.2 Mapping of the Binary Counter Reading Class

Not supported

19.3.3 Mapping of the Harmonic Value Class

Not supported

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 48 / 67 – 57/XXX/CD

19.3.4 Mapping of the WYE Class

The WYE class maps to the following structure:

WYE := STRUCT{
phsA := MeasuredValue [1..40],
phsB := MeasuredValue [41..80],
phsC := MeasuredValue [81..120],
neut := MeasuredValue [121..160] Optional,
t := TimeStamp [161..200] Optional,
tq := TimeStampQuality [201..208] Optional
}

Octets 8 7 6 5 4 3 2 1

1 27 20

2 2 15 28
phsA phsA
3 2 23 2 16

4 S 2 24

5 q OF IV BL RE SU NT EE RE
7
6 2 20

7 2 15 28
phsB phsB
8 2 23 2 16

9 S 2 24

10 q OF IV BL RE SU NT EE RE

11 27 20

12 2 15 28
phsC phsC
13 2 23 2 16

14 S 2 24

15 q OF IV BL RE SU NT EE RE
7
16 2 20

17 2 15 28
neut neut
18 2 23 2 16

19 S 2 24

20 q OF IV BL RE SU NT EE RE
7
21 2 20

22 2 15 28

23 t 2 23 1 Microseconds 2 16

24 2 31 2 24

25 2 39 2 32

26 tq Re Re Re Re IV SY ST CO

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 49 / 67 – 57/XXX/CD

19.3.5 Mapping of the Delta Class

In the context of this mapping all samples shall be transmitted as Phase to ground
measurements. Therefore the Delta Class is not supported.

19.3.6 Mapping of the Sequence Class

Not supported.

19.3.7 Mapping of the Phase Class

The Phase Class maps to the following structure:

Phase := STRUCT{
VphsA := MeasuredValue [1..40],
VPhsB := MeasuredValue [41..80],
VPhsC := MeasuredValue [81..120],
Vneut := MeasuredValue [121..160] Optional,
IphsA := MeasuredValue [161..200],
IPhsB := MeasuredValue [201..240],
IPhsC := MeasuredValue [241..280],
Ineut := MeasuredValue [281..320] Optional,
t := TimeStamp [321..360] Optional,
tq := TimeStampQuality [361..368] Optional
}

Octets 8 7 6 5 4 3 2 1

1 27 20

2 2 15 28
VphsA VphsA
3 2 23 2 16

4 S 2 24

5 q OF IV BL RE SU NT EE RE

6 27 20

7 2 15 28
VphsB VphsB
8 2 23 2 16

9 S 2 24

10 q OF IV BL RE SU NT EE RE
7
11 2 20

12 2 15 28
VphsC VphsC
13 2 23 2 16

14 S 2 24

15 q OF IV BL RE SU NT EE RE

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 50 / 67 – 57/XXX/CD

Octets 8 7 6 5 4 3 2 1

16 27 20

17 2 15 28
Vneut Vneut
18 2 23 2 16

19 S 2 24

20 q OF IV BL RE SU NT EE RE

21 27 20

22 2 15 28
IphsA IphsA
23 2 23 2 16

24 S 2 24

25 q OF IV BL RE SU NT EE RE
7
26 2 20

27 2 15 28
IphsB IphsB
28 2 23 2 16

29 S 2 24

30 q OF IV BL RE SU NT EE RE

31 27 20

32 2 15 28
IphsC IphsC
35 2 23 2 16

36 S 2 24

37 q OF IV BL RE SU NT EE RE
7
38 2 20

39 2 15 28
Ineut Ineut
40 2 23 2 16

41 S 2 24

42 q OF IV BL RE SU NT EE RE
7
43 2 20

44 2 15 28

45 t 2 23 1 Microseconds 2 16

46 2 31 2 24

47 2 39 2 32

48 tq Re Re Re Re IV SY ST CO

19.4 Mapping of the Attribute Class Specifications for Setpoint Information

19.4.1 Mapping of the Setpoint Class

Not supported

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 51 / 67 – 57/XXX/CD

20 Mapping of Compatible Logical Node and Data Object-Addressing

20.1 Supported logical nodes

In the context of this mapping only the following logical nodes are supported:

Table 33 – Logical Node Identification

General IO GGIO
Current transformer TCTR
Current transformer one Phase TCTP
Voltage transformer TVTR
Voltage transformer one Phase TVTP

20.2 Data Object Reference

20.2.1 Measurand Identification

In the context of this mapping only the following data objects are supported.

DO Reference
Currents IL1 AphsA
IL2 AphsB
IL3 AphsC
INP Aneut
Voltages VL1E VphsA
VL2E VPhsB
VL3E VPhsC
VNEP Vneut

20.2.1.1 Extension of Measurand Identification

The table below defines the physical basic semantic of the measurands used in the context
of this mapping. All measurands shall have the measurand category reference as an
additional supplementary technological reference.

Measurand category Reference

Instantaneous Inst
RMS present value RMS

20.3 Measurand Groups

In the context of this mapping of this mapping only the following measurand groups are
supported.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 52 / 67 – 57/XXX/CD

DO Reference
Phase to ground voltages V
Phase to ground currents A
all phase to ground voltages and currents AV

20.4 Single Point Status Groups

In the context of this mapping only the following Status Indication Groups are supported.

DO Reference
General Purpose Binary Inputs GPBI

20.5 Supplementary Technological References

In the context of this mapping only the following Supplementary Technological References
shall be used to distinguish between instantaneous analogue values used for protection and
metering.

STR Reference
Analogue value for protection Prot
Analogue value for metering Metr
BusBar 1 BB1
BusBar 2 BB2
BusBar 3 BB3

In cases where a differentiation more by the given Supplementary Technological References

is not possible, a number shall be added to the DataObjectReference.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 53 / 67 – 57/XXX/CD

Annex A (normative)

Definition of datasets

Dataset for universal use (defined by IEC 60044-8)

Octets 8 7 6 5 4 3 2 1

1 msb
Length = 80
2 lsb
Header
3 msb Data Group = 2 lsb
4 msb Reserved lsb
5 msb DataSetIdentifier = 1 lsb
6 msb Number of Data Objects = 14 lsb
DSG
7 lsb
Reserved
8 msb
7 0
9 2 2
15 8
10 2 2
Data Rated Current
23 16
11 Object 2 2
1 24
12 S 2
13 OF IV BL RE SU NT EE RE
7 0
14 2 2
15 8
15 2 2
Data Rated Voltage
23 16
16 Object 2 2
2 24
17 S 2
18 OF IV BL RE SU NT EE RE
7 0
19 2 2
15 8
20 2 2
Data TCTP.Inst.AphsA.Prot
23 16
21 Object 2 2
3 24
22 S 2
23 OF IV BL RE SU NT EE RE
7 0
24 2 2
15 8
25 2 2
Data TCTP.Inst.AphsB.Prot
23 16
26 Object 2 2
4 24
27 S 2
28 OF IV BL RE SU NT EE RE
7 0
29 2 2
15 8
30 2 2
Data TCTP.Inst.AphsC.Prot
23 16
31 Object 2 2
5 24
32 S 2
33 OF IV BL RE SU NT EE RE

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 54 / 67 – 57/XXX/CD

Octets 8 7 6 5 4 3 2 1
7 0
34 2 2
15 8
35 2 2
Data TCTP.Inst.Aphsneut.Prot
23 16
36 Object 2 2
6 24
37 S 2
38 OF IV BL RE SU NT EE RE
7 0
39 2 2
15 8
40 2 2
Data TVTP.Inst.VphsA
23 16
41 Object 2 2
7 24
42 S 2
43 OF IV BL RE SU NT EE RE
7 0
44 2 2
15 8
45 2 2
Data TVTP.Inst.VphsB
23 16
46 Object 2 2
8 24
47 S 2
48 OF IV BL RE SU NT EE RE
7 0
49 2 2
15 8
50 2 2
Data TVTP.Inst.VphsC
23 16
51 Object 2 2
9 24
52 S 2
53 OF IV BL RE SU NT EE RE
7 0
54 2 2
15 8
55 2 2
Data TVTP.Inst.Vphsneut
23 16
56 Object 2 2
10 24
57 S 2
58 OF IV BL RE SU NT EE RE
7 0
59 2 2
15 8
60 2 2
Data TCTP.Inst.AphsA.Meas
23 16
61 Object 2 2
11 24
62 S 2
63 OF IV BL RE SU NT EE RE
7 0
64 2 2
15 8
65 2 2
Data TCTP.Inst.AphsB.Meas
23 16
66 Object 2 2
12 24
67 S 2
68 OF IV BL RE SU NT EE RE
7 0
69 2 2
15 8
70 2 2
Data TCTP.Inst.Aphsneut.Meas
23 16
71 Object 2 2
13 24
72 S 2
73 SY DV BR OR OF NT CF IV
th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 55 / 67 – 57/XXX/CD

Octets 8 7 6 5 4 3 2 1
7 0
74 2 2
15 8
75 2 2
Data TVTP.Inst.VphsA.BB1
23 16
76 Object 2 2
14 24
77 S 2
78 OF IV BL RE SU NT EE RE
7 0
79 2 2
15 8
80 2 2
23 16
81 Time 2 1 Microseconds 2
82 Stamp 2
31
2
24

39 32
83 2 2
84 Re Re Re Re IV SY ST CO

Figure 11 – DataSet for Universal Use

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 56 / 67 – 57/XXX/CD

Dataset for Current Samples

Octets 8 7 6 5 4 3 2 1

1 msb
Length = 55
2 lsb
Header
3 msb Data Group = 2 lsb
4 msb Reserved lsb
5 msb DataSetIdentifier = 2 lsb
6 msb Number of Data Objects = 9 lsb
DSG
7 lsb
Reserved
8 msb
7 0
9 2 2
15 8
10 2 2
Data Rated Current
23 16
11 Object 2 2
1 24
12 S 2
13 OF IV BL RE SU NT EE RE
7 0
14 2 2
15 8
15 2 2
Data TCTP.Inst.AphsA.Prot
23 16
16 Object 2 2
2 24
17 S 2
18 OF IV BL RE SU NT EE RE
7 0
19 2 2
15 8
20 2 2
Data TCTP.Inst.AphsB.Prot
23 16
21 Object 2 2
3 24
22 S 2
23 OF IV BL RE SU NT EE RE
7 0
24 2 2
15 8
25 2 2
Data TCTP.Inst.AphsC.Prot
23 16
26 Object 2 2
4 24
27 S 2
28 OF IV BL RE SU NT EE RE
7 0
29 2 2
15 8
30 2 2
Data TCTP.Inst.Aphsneut.Prot
23 16
31 Object 2 2
5 24
32 S 2
33 OF IV BL RE SU NT EE RE
7 0
34 2 2
15 8
35 2 2
Data TCTP.Inst.AphsA.Meas
23 16
36 Object 2 2
6 24
37 S 2
38 OF IV BL RE SU NT EE RE

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 57 / 67 – 57/XXX/CD

Octets 8 7 6 5 4 3 2 1
7 0
39 2 2
15 8
40 2 2
Data TCTP.Inst.AphsB.Meas
23 16
41 Object 2 2
7 24
42 S 2
43 OF IV BL RE SU NT EE RE
7 0
44 2 2
15 8
45 2 2
Data TCTP.Inst.AphsC.Meas
23 16
46 Object 2 2
8 24
47 S 2
48 OF IV BL RE SU NT EE RE
7 0
49 2 2
15 8
50 2 2
Data TCTP.Inst.Aphsneut.Meas
23 16
51 Object 2 2
9 24
52 S 2
53 SY DV BR OR OF NT CF IV
7 0
54 2 2
15 8
55 2 2
23 16
56 Time 2 1 Microseconds 2
57 Stamp 2
31
2
24

39 32
58 2 2
59 Re Re Re Re IV SY ST CO

Figure 12 – Dataset for current samples

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 58 / 67 – 57/XXX/CD

Dataset for voltage samples

Octets 8 7 6 5 4 3 2 1

1 msb
Length = 35
2 lsb
Header
3 msb Data Group = 2 lsb
4 msb Reserved lsb
5 msb DataSetIdentifier = 3 lsb
6 msb Number of Data Objects = 5 lsb
DSG
7 lsb
Reserved
8 msb
7 0
9 2 2
15 8
10 2 2
Data Rated Voltage
23 16
11 Object 2 2
1 24
12 S 2
13 OF IV BL RE SU NT EE RE
7 0
14 2 2
15 8
15 2 2
Data TVTP.Inst.VphsA
23 16
16 Object 2 2
2 24
17 S 2
18 OF IV BL RE SU NT EE RE
7 0
19 2 2
15 8
20 2 2
Data TVTP.Inst.VphsB
23 16
21 Object 2 2
3 24
22 S 2
23 OF IV BL RE SU NT EE RE
7 0
24 2 2
15 8
25 2 2
Data TVTP.Inst.VphsC
23 16
26 Object 2 2
4 24
27 S 2
28 OF IV BL RE SU NT EE RE
7 0
29 2 2
15 8
30 2 2
Data TVTP.Inst.Vphsneut
23 16
31 Object 2 2
5 24
32 S 2
33 OF IV BL RE SU NT EE RE

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 59 / 67 – 57/XXX/CD

Octets 8 7 6 5 4 3 2 1
7 0
34 2 2
15 8
35 2 2
23 16
36 Time 2 1 Microseconds 2
37 Stamp 2
31
2
24

39 32
38 2 2
39 Re Re Re Re IV SY ST CO

Figure 13 – Dataset for voltage samples

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 60 / 67 – 57/XXX/CD

Dataset for Busbar Voltage Samples

Octets 8 7 6 5 4 3 2 1

1 msb
Length = 60
2 lsb
Header
3 msb Data Group = 2 lsb
4 msb Reserved lsb
5 msb DataSetIdentifier = 4 lsb
6 msb Number of Data Objects = 10 lsb
DSG
7 lsb
Reserved
8 msb
7 0
9 2 2
15 8
10 2 2
Data Rated Voltage
23 16
11 Object 2 2
1 24
12 S 2
13 OF IV BL RE SU NT EE RE
7 0
14 2 2
15 8
15 2 2
Data TVTP.Inst.VphsA.BB1
23 16
16 Object 2 2
2 24
17 S 2
18 OF IV BL RE SU NT EE RE
7 0
19 2 2
15 8
20 2 2
Data TVTP.Inst.VphsB.BB1
23 16
21 Object 2 2
3 24
22 S 2
23 OF IV BL RE SU NT EE RE
7 0
24 2 2
15 8
25 2 2
Data TVTP.Inst.VphsC.BB1
23 16
26 Object 2 2
4 24
27 S 2
28 OF IV BL RE SU NT EE RE
7 0
29 2 2
15 8
30 2 2
Data TVTP.Inst.VphsA.BB2
23 16
31 Object 2 2
5 24
32 S 2
33 OF IV BL RE SU NT EE RE
7 0
34 2 2
15 8
35 2 2
Data TVTP.Inst.VphsB.BB2
23 16
36 Object 2 2
6 24
37 S 2
38 OF IV BL RE SU NT EE RE

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 61 / 67 – 57/XXX/CD

Octets 8 7 6 5 4 3 2 1
7 0
39 2 2
15 8
40 2 2
Data TVTP.Inst.VphsC.BB2
23 16
41 Object 2 2
7 24
42 S 2
43 OF IV BL RE SU NT EE RE
7 0
44 2 2
15 8
45 2 2
Data TVTP.Inst.VphsA.BB3
23 16
46 Object 2 2
8 24
47 S 2
48 OF IV BL RE SU NT EE RE
7 0
49 2 2
15 8
50 2 2
Data TVTP.Inst.VphsB.BB3
23 16
51 Object 2 2
9 24
52 S 2
53 OF IV BL RE SU NT EE RE
7 0
54 2 2
15 8
55 2 2
Data TVTP.Inst.VphsC.BB3
23 16
56 Object 2 2
10 24
57 S 2
58 OF IV BL RE SU NT EE RE
7 0
59 2 2
15 8
60 2 2
23 16
61 Time 2 1 Microseconds 2
62 Stamp 2
31
2
24

39 32
63 2 2
64 Re Re Re Re IV SY ST CO

Figure 14 – Dataset for Busbar Voltage Samples

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 62 / 67 – 57/XXX/CD

Dataset for Binary Status Information

Octets 8 7 6 5 4 3 2 1

1 msb
Length = 15
2 lsb
Header
3 msb Data Group = 2 lsb
4 msb Reserved lsb
5 msb DataSetIdentifier = 5 lsb
6 msb Number of Data Objects = 1 lsb
DSG
7 lsb
Reserved
8 msb
9 S8 S7 S6 S5 S4 S3 S2 S1
10 S16 S15 S14 S13 S12 S11 S10 S9
11 SIG C8 C7 C6 C5 C4 C3 C2 C1
12 C16 C15 C14 C13 C12 C11 C10 C9
13 OF IV BL RE SU NT EE RE
7 0
14 2 2
15 8
15 2 2
23 16
16 Time 2 1 Microseconds 2
17 Stamp 2
31
2
24

39 32
18 2 2
19 Re Re Re Re IV SY ST CO

Figure 15 – Dataset for Binary Status Information

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 63 / 67 – 57/XXX/CD

ANNEX B (informative)

Introduction to Ethernet
Overview of Ethernet Frame Structure
The Ethernet frame format is shown in Figure 16:

27 26 25 24 23 22 21 20

7 Octets Preamble

1 Octet Start of frame

Destination address

Header
14 Octets

Source address

Length of data

Data
Pay load
46 Octets
minimum

(Pad bytes if necessary)

Footer
Frame check sequence
4 Octets

1 Octet End of frame

Figure 16 - Ethernet Frame Format

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 64 / 67 – 57/XXX/CD

Ethernet frames begin with an alternating pattern of ones and zeros called a preamble . The
preamble tells receiving stations that a frame is coming.

The byte before the destination address is a start-of-frame (SOF) delimiter . This byte ends
with two consecutive one bits, which serve to synchronize the frame reception portions of all
stations on the LAN.

Immediately following the preamble are the destination and source address fields. Ethernet
addresses are 6 bytes long. Addresses are contained in hardware on the Ethernet interface
cards. The first 3 bytes of the addresses are specified by the ISO/IEC on a manufacturer-
dependent basis, while the last 3 bytes are specified by the Ethernet vendor. The source
address is always a unicast (single node) address, while the destination address may be
unicast, multicast (group), or broadcast (all nodes). The broadcast address is a predefined
group address that always denotes the set of all end nodes on a given local area network.
All 1's in the destination address is predefined to be the broadcast address.

In this case the 2-byte field following the source address is a length field, which indicates
the number of bytes of data that follow this field and precede the frame check sequence
(FCS) field.

Following the type/length field is the actual data contained in the frame. After physical-layer
and link-layer processing is complete, this data will eventually be sent to an upper-layer
protocol. If data in the frame is insufficient to fill the frame to its minimum 64-byte size,
padding bytes are inserted to ensure at least a 64-byte frame.

After the data field is a 4-byte FCS field containing a cyclic redundancy check (CRC) value.
The CRC is created by the sending device and recalculated by the receiving device to check
for damage that might have occurred to the frame in transit.

For additional information on the use of these fields refer to ISO/IEC 8802.3 standard.

A summary of ISO/IEC 8802.3 characteristics appears in Table 34.

Table 34 - ISO/IEC 8802.3 Physical Characteristics

ISO/IEC 8802.3 Values

10BaseT 10BaseFL
Data rate (Mbps) 10 10
Signaling method Baseband Baseband
Maximum segment length (m) 250 [TBD]
Media Unshielded twisted-pair wire Graded index 62,5/125µm
Topology Bus Star Star

Ethernet is most similar to ISO/IEC 8802.3 10Base5. Both of these protocols specify a bus
topology network with a connecting cable between the end stations and the actual network
medium. In the case of Ethernet, that cable is called a transceiver cable . The transceiver
cable connects to a transceiver device attached to the physical network medium. The
ISO/IEC 8802.3 configuration is much the same, except that the connecting cable is referred
to as an attachment unit interface (AUI), and the transceiver is called a medium attachment
unit (MAU). In both cases, the connecting cable attaches to an interface board (or interface
circuitry) within the end station.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 65 / 67 – 57/XXX/CD

Introduction to Ethernet Switching

When Ethernet was invented 20 years ago, nobody could imagine that 20 to 50 stations per
segment and a maximum cable length of 185m (thin Ethernet) or 500m (thick Ethernet)
could not be sufficient for the rest of the time. The tremendous success of network
technologies quickly lead to the situation that network dimension grew dramatically. So
called repeaters, connecting several cable segments solved the dimension, but not all
problems. The next problem arising was the bandwidth problem, because all stations
connected to the network had to share the medium connected via repeaters. Data packets
and frames still crossed the whole network. The more stations were connected to the
network the lower became the bandwidth dedicated to each station. Data volumes in the
network raised without increasing the bandwidth of the network.

One solution is to subdivide the network by a device that is able to forward only the data
packets to another sub network when it is explicitly dedicated to a station in the other sub
network. By this means it is possible to reduce the data volume in the sub networks. These
devices are called bridges. Bridges connect two or more sub networks, which themselves
could be built of several segments connected by repeaters. Bridges build up the borders for
so called collision domains. Collisions can not take place between networks divided by
bridges, and data packets destined to a specific sub network do not appear on the other sub
networks. To achieve this bridges must have a knowledge of the hardware addresses of the
connected stations.

By the use of bridges it is not possible to provide communication between sub networks that
are not directly connected to the same bridge. For this purpose routers have to be used.

A switch is in principle a bridge with several ports, which has the ability to connects several
sub networks. The first switch was not much more than a multiport bridge, which was
renamed for marketing means.

In difference to a bridge a switch allows the parallel data exchange between connected sub
networks or stations. Therefor a switch has to be equipped with equivalent hardware. Data
transfer within the switch has to be possible with a speed which is equivalent to the
bandwidth of the network multiplied with the number of ports.

In principal a switch builds a direct point to point connection between two connected
stations. By this the whole bandwidth is available for them. The connection between the
switch and the network device (which can be a workstation, another switch or a hub) builds
up an own network segment. Data traffic will only be forwarded to that segment, whose
devices have a hardware address that fits the hardware address included in the data frame.

This basic functionality has consequences on the abilities of the switch. It is obvious that the
switching engine has to be very fast. If the switch wouldn’t have the capability to forward the
frame with the speed of the connection (wire speed) the switch himself would be a
bottleneck. In addition to that, the switch must have the capability to read the hardware
addresses (MAC addresses) from the frame and distinguish the port for the forwarding of
the frame. A MAC address must be supplied by every network device. The MAC address of
the source and destination device are included in the data frame. It is not sufficient that the
switch reads out the MAC address of the destination node and afterwards asks where to find
this node. Doing this the switch would probably run into trouble forwarding the frame in a
sufficient time. To avoid this switches can learn the MAC addresses of the connected
devices and store them in an internal table. Usually modern switches are designed to store
several MAC addresses for every port (segment switch). More rarely you can find devices
that can store only one MAC address per port (Port switch)- Nowadays nearly all switches
forward data on a frame basis. Another method would be to split up the frames into cells of
a predefined length internally, forward them to the destination port and reassemble them to
the original frame. The advantage of this method is that the transmission time within the
switch is defined and the same for each and every cell. Frames on the other hand can have
th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 66 / 67 – 57/XXX/CD

a length of 64 to 1518 byte and therefore need different times within the switch. In a frame
switch the switch engine must have the ability to forward the frame so quickly that there is
no bottleneck. Cell switches on the other hand need additional logic to split up and
reassemble the frames, which may also not influence the performance of the switch.

There are no official standards for Ethernet switches available, but there is no need for a
special standard, because these devices have to fulfil the standards IEEE 802.2 and IEEE
802.3, which are the basic Ethernet standards. The way the switch works internally is
transparent to the network. Beneath the frame and cell switching technologies, different
ways for the forwarding of the frames have been established.

Cut-through reads only the first 14 byte of the frame to identify the source and destination
address. It is not possible to use error detection and/or correction with this method, because
the CRC field will be read after the forwarding of the frame. This is the fastest method of
forwarding a frame, the delay is typically less than 11µs using fast Ethernet.

An extension to Cut-Through switching is Fragment Free switching, which is not very

popular up to now. The switch will read the first 64 byte of the frame to detect collided frame
fragments, so called Runt. A Runt is a data frame with a length of less than 64 byte. An
error detection of complete frames is not performed. A typical delay is less than 60µs.
Fragment free switching has only minor meanings in modern installations, where switching
and full duplex communication is combined. In this mode no collisions will appear. The
advantages of Cut-Through switching appear in mixed or pure half duplex environments.
Here this method can avoid unneeded traffic within the switch. It is common to Fragment
Free and Cut-Through switching that the source and destination port have to work with the
same speed.

The third method of forwarding frames is Store and Forward . All frames are read completely
and store in the switch. By this the switch can detect defect frames and forward data
between networks with different bandwidth. Depending on the frame size the delay time can
be 100µs and more. Store and Forward is the method originally used in bridges. Nowadays
switches are made of customized Asics’s realizing all the functionality of a switch in
hardware. By this means the performance of switching engines could be raised dramatically.
Throughput rates of 1Gbit/s and above are usual. By this Ethernet switches with several
ports can be built easily.

Most of the modern switches use store and forward technology. Pure Cut-Through switches
are very rare to find, because they lack flexibility. The development goes into the direction to
support all three switching methods within one device. The ideal case is, that the switch can
decide itself, which switching technology to use. If he doesn’t have this possibility the
network administrator has to decide, by an analysis of the data flow and the error rate in the
network, which method to choose.

In some cases switches can cause problems. If, for example, a great number of
workstations try to send data to a server, which is connected to one port of the same switch
this can result in a blockade. Modern switches try to avoid such a situation by means of flow
control. If a port is overloaded he will signal this to the source ports. The source ports will
then reduce the speed for the forwarding of data to the destination port. This will lead to the
situation that all devices connected to the source ports have less bandwidth available, even
if the don’t want to communicate with the overloaded port.

In addition to all that switches must have the ability to avoid dead lock loops in a network of
several active switches. Without this feature broadcast messages would loop in the network
for ever and ever, because they are forwarded from one switch to the next. Usually this
problem is solved by the use of the spanning tree algorithm. The spanning tree algorithm is
defined in IEEE 802.ID.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99
Draft IEC 61850-9-1  IEC:1999 – 67 / 67 – 57/XXX/CD

The ability to build so called virtual LANs is one of the features of modern switches. Virtual
LANs group devices by a logical grouping and not by their connection to a network segment.
Data traffic will then be forwarded according to these virtual networks.

th
Version 1.0, May 04 , 1999
Version 1.0 sent to IEC CO / TC 57 secretary on 03 May 99