IEC 61850

Implementation Perspective
IEC 61850 Server Implementation
 Conformance Statement (PICS and MICS)
 Selection of Logical Nodes according to Device
Functionalities
 Generation of ICD File
 Mapping of Inputs and Outputs between IEC
61850 Server and Device application
 IPC between Device Application and IEC 61850
Server Application
Server Conformance Statement
 Depends on the functionality of Server Device
BCU
Relay
Data Concentrator
Protocol Converter
 Implementation Constraints
Supporting Hardware / Software
Performance Issues
Selection of Logical Nodes
 Automatic Control – Group A
 Supervisory Control – Group C
 Generic Function References – Group G
 Interfacing and Archiving – Group I
 System Logical Nodes – Group L
 Metering and Measurement – Group M
 Protection Functions – Group P
 Protection Related Functions – Group R
Selection of Logical Nodes

 Sensors and Monitoring – Group S

 Instrument Transformers – Group T
 Switchgear – Group X
 Power Transformers and Related Functions –
Group Y
 Further Power System Equipment – Group Z
Generation of ICD File
 Communication
Subnetwork
 IED
Services
Access Point
 Server

Logical Device

 Logical Nodes
 Datasets
Generation of ICD File
 Control Blocks
 Data Objects
 Data Attributes
 Data Type Templates
Logical Nodes
Data Objects
Data Attributes
Enumeration Types
Generation of ICD File

 Validation - Conformance to SCL schema

 Detailed Capability Description
 Initialization of Data Variables
 Tool for Creating Customized ICD SCL file
Eg. SCL Manager
 Defining customized Data Objects
IEC 61850 Client Implementation

 Conformance Statement (PICS)

 Implementation of Configuration methodologies
to Configure Device information and data
 Mapping of Inputs and Outputs between IEC
61850 Client and Client User application
 IPC between Client User Application and IEC
61850 Client Application
Client Conformance Statement
 Depends on the functionality of Client Station
Remote Control Centre
Substation SCADA
Data Concentrator
Protocol Converter
 Implementation Constraints
Supporting Hardware / Software
Performance Issues
Client Configuration methodologies
 Dynamic Configuration of IED in Client using IEC
61850 Services – At Configuration time
 Dynamic Configuration of IED in Client using IEC
61850 Services – At Runtime
 Offline Configuration of IED in Client using
Server ICD File – In Configuration mode
 SCL Parser Issues
 Tag Creation and Service Triggers
IEC GOOSE Implementation

 Association management – Retransmission Time out

 Fast - Less time for parsing (if data chosen appropriately)
 Low Bandwidth consumption - No network header
overhead of different layers
 Performance
Noise in the network, network delays
Data processing capabilities of modules and hardware
involved
IPC between User Application and
IEC 61850 Application
 Sockets
 Shared Memory
 FIFOs
 Pipes / Mailslots
 Issues involved
Using IPC: Delays
Using Different OS: Unsupported IPCs
Incompatibility in data processing efficiency:
Missing of Data / Buffer Over Flow
Mapping of Data between User
and IEC 61850 Application
 Proper interpretation and exchange of data
 Mode of Configuration - Dynamic or Fixed
 Difference in Client/Subscriber and
Server/Publisher side data Initialization
SCADA Level – same data used by multiple
applications
IED Level – Consequences on device
configuration changes
Basic Conformance Statement

 Two Party Application Association

 GSE – Generic Substation Event Model
Publisher Side
Subscriber Side
 SVC – Sampled Value Control Model
Publisher Side
Subscriber Side
Models Conformance Statement
 Logical Device
 Logical Node
 Data
 Dataset
 Substitution
 Setting Group Control
Models Conformance Statement
 Reporting
Buffered Report Control
Unbuffered Report Control
 Logging
Log Control
Log
 Control
Models Conformance Statement
 GSE
GOOSE
GSSE
 SVC
Multicast
Unicast
 Time
 File Transfer
Service Conformance Statement
 Server
Server Directory
 Application Association
Associate
Abort
Release
 Logical Device
LogicalDeviceDirectory
Service Conformance Statement
 LogicalNode
LogicalNodeDirectory
GetAllDataValues
 Data
GetDataValues
SetDataValues
GetDataDirectory
GetDataDefinition
Service Conformance Statement
 Dataset
GetDataSetValues
SetDataSetValues
CreateDataSet
 Dataset
DeleteDataSet
GetDataSetDirectory
 Substitution
SetDataValues
 Setting Group Control
 SelectActiveSG
 SelectEditSG
 SetSGValues
 ConfirmEditSGValues
 GetSGValues
 GetSGCBValues
Reporting
 Buffered Report Control Block
 Report

data-change (dchg)
qchg-change (qchg)
data-update (dupd)
GetBRCBValues
 SetBRCBValues
Reporting

 Unbuffered Report Control Block

 Report

data-change (dchg)
qchg-change (qchg)
data-update (dupd)
GetBRCBValues
 SetBRCBValues
Logging

 Log control block

GetLCBValues
SetLCBValues
 Log
QueryLogByTime
QueryLogAfter
GetLogStatusValues
Generic substation event model

 GOOSE-CONTROL-BLOCK
 SendGOOSEMessage
 GetGoReference
 GetGOOSEElementNumber
 GetGoCBValues
 SetGoCBValues
Generic substation event model

 GSSE-CONTROL-BLOCK
SendGSSEMessage
GetGsReference
GetGSSEElementNumber
GetGsCBValues
SetGsCBValues
Transmission of sampled value
model
 Multicast SVC
SendMSVMessage
GetMSVCBValues
SetMSVCBValues
 Unicast SVC
SendUSVMessage
GetUSVCBValues
SetUSVCBValues
Control

 Select
 SelectWithValue
 Cancel
 Operate
 Command – Termination
 TimeActivated-Operate
Time

 Time resolution of internal clock

 Time accuracy of internal clock
 Supported TimeStamp resolution
File transfer

 GetFile
 SetFile
 DeleteFile
 GetFileAttributeValues
MMS topology in IEC 61850
Implementation

 User Application Program

 User Objects (files, domains, variables, etc.)
 MMS-EASE Virtual Machine Interface
 Lower Layer Provider (ACSE, LLP, etc.)
The VMD Model
 VMD
Real – Virtual Mapping
MMS Device and Object Modelling
Attributes and Scope (VMD, Domain and
Application Association)
Capabilities, Services and Behavior
 ASN.1 Encoding / Decoding
SISCO's MMSLITE Source Code
Library
 Easy to use libraries with simple sample
applications to start with
 High Portability over different Target
Environments
 Well defined coding methodology and directory -
file hierarchy
 Proven Stability, Quality and performance
 Proper documentation
MMS Server - SCL - IEC 61850
Server
 IEC 61850 Server protocol standard demands
the implementation of MMS Server Services
 XML Configuration will be used
 SCL - Language for IEC 61850 Server
Configuration
 Dynamic Object creation according to SCL –
XML Definitions
MMS Client - IEC 61850 Client

 IEC 61850 Client protocol standard demands the

implementation of MMS Client Services
 Easy Read – Write interfaces with respect to MMS
Standards
 Enabling of Self reporting in Server Devices to avoid
Polling mechanisms and resulting bandwidth usages
during data acquisition
 Extensive support for Controls and Command operation
CNLP Layer – IEC GOOSE
 Improved version of GSSE (Generic substation
state event)
 Enables Fast Exchange of Data / Messages
 Publisher (Send) and Subscriber (Receive)
 Direct Ethernet Interface using Lower Layer
Stack APIs
 Configurable messages using SCL XML files.
Directory Structure
 \mmslite (root MMS-EASE Lite directory)
\cmd (command files for creating binaries)
\src (source code – all .c files)
\inc include files – all .h files)
\uca (stack profiles source root)
\mvl (MMS Virtual Light)
\doc (PDF documentation)
\lib (libraries)
\osillc (OSILLC driver source code)
Supported Target Platforms
 WIN32 Development Environment
All projects are included in the main Microsoft
Developer Studio workspace, mmslite.dsw.
Individual / Grouped workspaces are provided
for other Projects
 GNU Development Environment
All makefiles are listed in the main shell file,
mkall.sh
Individual makefiles are provided for other
Projects
Compilation Options
 Makefiles and Workspaces
 Build Configurations
Release / Logging - Deployment of applications
with field diagnostics
Release / No Logging - Deployment without
diagnostics
Debug / Logging - Development and in field
diagnostics
Debug / No Logging – Trouble shooting without
logging
Libraries and Utilities

 ASN.1 encode/decode libraries - asn1

 Memory allocation library - full featured version
- mem
 Memory allocation library - Lite version - meml
 MMS operation specific logging library – mlog
 Main MMS encode/decode library – mmsl
 Extended MMS encode/decode library – mmsle
Libraries and Utilities
 MVL library - mvl
 MVL UCA library - mvlu
 TCP/IP (via RFC1006) stack library – ositcpe
 TCP/IP (via RFC1006) stack library using non-
blocking sockets – ositcps
 7 Layer OSI over Ethernet library – ositp4e
 Library that includes TCP/IP (via RFC1006) and
7 Layer OSI over Ethernet - ositpxe
Libraries and Utilities
 Library that includes TCP/IP using non-blocking
sockets and 7 Layer OSI over Ethernet – ositpxs
 Required library for compatibility with future
enhancements. - ssec0
 MMS logging library - mmslog
 SISCO logging library - full featured version - slog
 SISCO logging library - Lite version – slogl
 Memory allocation library using “pools” - smem
 SISCO utility library - util
Sample Applications
 Foundry utility application - foundry
 mbufcalc utility application - mbufcalc
 IEC GOOSE Framework sample application -
iecgoose
 Client sample applications – cosit*
 IEC-61850 Server sample application using SCL
– scl_srvr
 Server sample applications - sosit*
 UCA Server sample application – uosit*
MMS Virtual Lite
 Higher-level interface layer which provides MMS
services (communications service, incoming PDU
handling, etc.)
 Simplifies creating and using MMS objects,
working with Foundry
 Integrated with all network profiles, 7 Layer OSI,
and TCP/IP (using RFC1006).
 Full integration with the SISCO ACSE layer
 Use of the Application Association object scope for
connection oriented ACSE profiles.
Services and Features
 Initiate - Initiates a MMS connection / association
to the selected Remote Node
 Conclude – Concludes an existing MMS
connection
 Cancel - Cancels an outstanding MMS service
request
 Identify - To obtain identifying information
 Status - Allows a client to determine the general
condition or status of a server node
Services and Features
 GetNameList - Request a responding node, to return a list
of object names that exist at the VMD
 Read (Named, NamedVariableList) - Request a
responding node, to return value of object name(s)
 Write (Named) - Request a node, to replace the value of
object name(s) with a value in the request
 InformationReport (Named, NamedVariableList) - To
inform the other node of the value of one or more
specified variables, as read by the issuing node
Services and Features
 GetVariableAccessAttributes - to request a VMD to
return the attributes of a Variable object
 GetVariableList Attributes - to request a VMD to
return the attributes of a Variable List object
 DefineVariableList - to request a VMD to create a
Variable List object
 DeleteVariableList - to request a VMD to delete a
Variable List object
 FileDirectory - To obtain the name and attributes of
a file or group of files in the server’s filestore
Services and Features
 FileOpen - To identify a file to be read, and to
establish the open state
 FileRead - To transfer all or part of the contents
of an open file from a server to a client
 FileClose - To request that a specified file be
closed, and all resources associated with the file
transfer be released
 FileDelete - To delete a file from the a server
Services and Features
 ReportJournalStatus - To determine the number
of entries in a Journal object
 InitializeJournal - To request that a server
initialize all or part of an existing Journal object
by removing all or some of the journal entries
Connection Management

 Calling (Requesting) and Called (Responding)

Nodes
 Associate – Proper initialization of an MMS
connection by a Calling Node
 Abort – Abrupt Termination of an MMS
connection by a Node
 Release - Graceful Termination of an MMS
connection by a Node
MMS Object Control
 Dynamic Object Management - For adding and
deleting MMS objects (Named Types, Named
Variables, Named Variable Lists, Domains, and
Journals) at runtime
 Configured MMS Server Objects – Via XML files
or ODF files
 Manufactured MMS Server Objects – Creation of
Objects via specific function calls
 Global Structures with hierarchy of MMS Objects
 Easily accessible via MVL API functions
MMS Object Foundry
 Inputs
MVL Object Definition File – MMS Objects and
Type Definitions
Alignment Control File - Data alignment reqts.
of the primitive/complex data elements
LAP (Leaf Access Parameter) XML File – Read
and Write Indication functions
 Output
MVL Object Realization Files – Source and
Header Files
MMS Objects

 Server – Physical Device

 Domain – Logical Device
 Named Variable – IEC 61850 Data with
Functional Constraints
 Named Variable Lists – Datasets
 Data Types – TDL (Type Definition Language)
Advantages

 Interoperability in a greater extend

 Futuristic approach in terms of modularity
 Support: IEC 61850 User group and
Technical Issues
 Dynamic configuration capabilities using
SCL XML Standard