BCI IEC60870-5-104 en
BCI IEC60870-5-104 en
BCI IEC60870-5-104 en
Revision
Contents
1 Introduction..............................................................................................................................7
1.1 Preface.................................................................................................................................... 7
1.2 References.............................................................................................................................. 7
1.3 Conventions........................................................................................................................... 7
1.4 Functions of the BCI compared to HCI and SCI............................................................ 8
2 Physical Layer...........................................................................................................................9
2.1 IP based Communication................................................................................................... 9
2.2 Host interface....................................................................................................................... 9
3 Link Layer................................................................................................................................ 11
3.1 General...................................................................................................................................11
4 Application Layer................................................................................................................... 13
4.1 General.................................................................................................................................. 13
4.2 Communication Queue Handling....................................................................................14
4.3 ASDU Type identification................................................................................................. 14
4.3.1 ASDU in monitoring direction........................................................................ 15
4.3.2 ASDU in control direction................................................................................15
4.3.3 ASDU of system information in command direction.................................16
8 Transparent Data.................................................................................................................. 43
9 File Transfer........................................................................................................................... 45
10 Internal Functions................................................................................................................. 47
12 Interoperability List.............................................................................................................. 53
12.1 System or device................................................................................................................ 53
12.2 Network configuration......................................................................................................53
12.3 Physical Layer...................................................................................................................... 53
12.3.1 Transmission speed (control direction).......................................................53
12.3.2 Transmission speed (monitor direction).....................................................54
12.4 Link Layer............................................................................................................................. 55
12.5 Application Layer................................................................................................................55
12.5.1 Transmission Mode for Application Data.................................................... 55
12.5.2 Common Address of ASDU.............................................................................55
12.5.3 Information object address............................................................................56
12.5.4 Cause of transmission.....................................................................................56
12.5.5 Length of APDU................................................................................................ 56
12.5.6 Selection of standard ASDUs.........................................................................56
12.6 Basic application functions............................................................................................. 60
12.6.1 Station initialization.........................................................................................60
12.6.2 Cyclic data transmission.................................................................................60
12.6.3 Read procedure................................................................................................. 61
12.6.4 Spontaneous transmission............................................................................. 61
12.6.5 Double transmission of information objects with cause of transmission
spontaneous.......................................................................................................61
12.6.6 Station interrogation........................................................................................61
12.6.7 Clock synchronization...................................................................................... 61
13 Glossary.................................................................................................................................. 65
1 Introduction
1.1 Preface
This document describes the functions of the bidirectional communication interface in
RTU500 series according to IEC 60870-5-104.
RTU500 series fulfills the requirements of IEC 60870-5-104 Edition 2. Detailed information can
be found in the interoperability list (see Chapter 12).
1.2 References
[1] Telecontrol equipment and systems – Part 5-104
Transmission protocols –
1.3 Conventions
In this document function codes of data types according to IEC 60870-5-104 are marked with
brackets: <Function code>
Bold fonts with the table heading "Parameter name" are references to configuration
parameters in RTUtil500. The parameter is followed by the parameter location where to
find this parameter in RTUtil500. The first element of the parameter location defines the
node in the hardware tree on the left side (e. g. RTU, CMU, line, IED) and the second element
defines selected header control tab in the parameter window on the right side (e. g. general,
interfaces, protocol).
Example:
The tables in the next chapters include lists of the functions, options and message types
supported according to the protocol structure given in IEC 60870-5 (EPA three layer model)
for
The tables in the next chapters include lists of the functions, options and message types
supported according to the protocol structure given in IEC 60870-5 (EPA three layer model)
for
• the physical layer
• the link layer
• the application layer
2 Physical Layer
3 Link Layer
3.1 General
Protection against loss and duplication of message is handled as defined in [1, 5.1].
4 Application Layer
4.1 General
The selectable parameters have to be calculated regarding the real communication
technology. All parameters preset to the default values from the IEC standard.
Highest Priority:
• Command acknowledgment queue (COT=6…10)
Priority level 1:
• Priority 1 Monitoring data queue (COT=3)
• Integrated totals queue (if configured as priority 1) (COT=3)
Priority level 2:
• Priority 2 Monitoring data queue (COT=3)
• Integrated totals queue (if configured as priority 2) (COT=3)
• Spontaneous measured value queue (COT=3)
• Requested information queue incl. file transfer (COT=37..41 and COT =13)
• SOE queue (if double transmission mode is activated)
Lowest priority:
• Interrogated data, direct from process image (COT=20…36)
• Periodic/ cyclic measured values, direct from process image (COT=1)
• Background cycle, direct from process image (COT=2)
Parameter name Default Parameter location
The column "RTU data type" shows the type of data with must be configured in RTUtil500.
The highest possible address value (255 for 1 octet common address length and 65 535 for
2 octet common address length) is reserved for broadcast calls in control direction and
therefore must not be used as station address.
All addresses must be unique within one station. The type of presentation (ASDU format) is
not part of the identification of an object.
1)It
is possible to set both parameters at the same data point. That means that the
concerning data point is directly send to the NCC on every change and additional after the
configured time period.
None
None
None
The EPI contents a elapsed time tag of the protection event with the range of 0..59 999 ms.
None
6.7.2 Values
1)It
is possible to set both parameters at the same data point. That means that the
concerning data point is directly send to the NCC on every change and additional after the
configured time period.
None
None
(Table Interface parameters - IEC 60870-5-104 in chapter Physical Layer (page "2-1"))
(1 select, 0 execute)
QL default 0 - default
Table 46: ASO - conversion of qualifier of command
(Table Interface parameters - IEC 60870-5-104 in chapter Physical Layer (page "2-1"))
Always persistent output. A new command with value 0 (all bits) has to be generated.
(Table Interface parameters - IEC 60870-5-104 in chapter Physical Layer (page "2-1"))
None
(1 select, 0 execute)
QU default 0 - no additional definition
Table 54: DCO - conversion of qualifier of command
(Table Interface parameters - IEC 60870-5-104 in chapter Physical Layer (page "2-1"))
(1 select, 0 execute)
QL default 0 - default
Table 58: DSO - conversion of qualifier of command
(Table Interface parameters - IEC 60870-5-104 in chapter Physical Layer (page "2-1"))
None
(1 select, 0 execute)
QL default 0 - default
Table 62: FSO - conversion of qualifier of command
(Table Interface parameters - IEC 60870-5-104 in chapter Physical Layer (page "2-1"))
In order to retrigger a running two step regulation command, it is not necessary to resend the
command Select.
(1 select, 0 execute)
QU default 0 - no additional definition
Table 66: RCO - conversion of qualifier of command
(Table Interface parameters - IEC 60870-5-104 in chapter Physical Layer (page "2-1"))
None
(1 select, 0 execute)
QU default 0 - no additional definition
Table 70: SCO - conversion of qualifier of command
8 Transparent Data
Transparent data communication is not supported.
9 File Transfer
File transfer is not supported.
10 Internal Functions
10.1.2 Values
20, 21 … 36
None
21 – Interrogation Group 1
22 – Interrogation Group 2
36 – Interrogation Group 16
Table 73: General Interrogation - Conversion of quality descriptors
The eight time masters have their own priority. If a higher prior master will fail, the time
master with the lower priority will synchronize the RTU. If the higher prior time master is
available again, he will continue synchronizing.
10.2.2 Values
None
The following table shows the system events available for the host interface:
This chapter describes the implementation of secured IEC 60870-5-104 BCI communication
with IEC 62351-3 in RTU500 as controlled station. RTU500 supports TLS (Transport Layer
Security) encryption and authentication by means of X.509 certificates. This option is
available with the license feature "Advanced Security".
ADVICE
In secured mode the BCI IEC 60870-5-104 can manage up to 30 substations per line.
11.4 Certificates
For a secure TLS communication, it is essential to have a mutual authentication between the
communication partners. For TLS in general, X.509 certificates are used. A digital certificate
is used to prove that someone is who they say they are. In a TLS negotiation, RTU500 uses
a server certificate to prove its identity to the control system. TLS requires that the control
system prove its identity with a client certificate as well.
Certificates are a set of keys and information. A private and a public key are needed. The
private key is a RSA key. RTU500 supports a key length of 2048 bits. The private key is used
for signature and encryptions. A corresponding public key with the same length can be
distributed to the public and is used for verifying the signature or for decrypting messages.
Version 3 of X.509 certificates are supported by RTU500 (RFC5280). One certificate per CMU
module may be configured for IEC 62351-3. RTU500 supports up to two CAs (Certificate
Authorities). RTU500 supports X.509 certificates with a size up to 8192 bytes. Certificate
revocation list handling is not implemented.
• Unsecured
• IEC 62351-3
The certificate used for authentication and encryption is selectable from a dropdown list. List
items depend on certificate store configuration. That means prior to that list selection set
an entry with descriptive text in the certificate store of the CMU module to upload external
certificates for authentication.
The upload of an external generated certificate is done via the RTU500 series Web server. In
the Web server menu the link "Certificate Management" is the entry point for the certificate
upload. This link can be found under the menu item "Management".
• Select the description of the certificate to upload in the column "Certificate description".
In the selection all in RTUtil500 configured entries of the certificate store appear. The
selection text is the descriptive name set in RTUtil500.
• Select a certificate file.
• Enter the password for the private key passphrase by pressing the lock symbol.
When all steps are finished the certificate can be uploaded by pressing the upload button.
The upload button appears not before all required information are set.
12 Interoperability List
The selected parameters are marked in the white boxes as follows:
System definition
X Controlling station definition (master)
X Controlled station definition (slave)
Point-to-point
Multiple point-to-point
Multipoint-party line
Multipoint-star
Unbalanced interchange
Circuit V.24/V.28
Standard
100bit/s
200bit/s
300bit/s
600bit/s
1 200bit/s
Unbalanced interchange
Circuit V.24/V.28
Recommended if >1 200 bit/s
2 400bit/s
4 800bit/s
9 600bit/s
Balanced interchange
Circuit X.24/X.27
2 400bit/s
4 800bit/s
9 600bit/s
19 200bit/s
38 400bit/s
56 000bit/s
64 000bit/s
Unbalanced interchange
Circuit V.24/V.28
Standard
100bit/s
200bit/s
300bit/s
600bit/s
1 200bit/s
Unbalanced interchange
Circuit V.24/V.28
Recommended if >1 200 bit/s
2 400bit/s
4 800bit/s
9 600bit/s
Balanced interchange
Circuit X.24/X.27
2 400bit/s
4 800bit/s
9 600bit/s
19 200bit/s
38 400bit/s
56 000bit/s
64 000bit/s
Frame format FT 1.2, single character 1 and the fixed time out interval are used exclusively in
this companion standard.
Frame length
Maximum length L (number of octets)
One octet
Two octets
Structured
Unstructured
When using an unbalanced link layer, the following ASDU types are returned in class 2
messages (low priority) with the indicated causes of transmission:
Mode 1 (least significant octet first), as defined in 4.10 of IEC 60870-5-4, is used exclusively in
this companion standard.
(system-specific parameter)
(system-specific parameter)
(system-specific parameter)
(system-specific parameter)
The maximum length of APDU for both directions is 253. It is a fixed system parameter.
(station-specific parameter)
In this companion standard only the use of the set <30> – <40> for ASDUs with time tag is
permitted.
(station-specific parameter)
(station-specific parameter)
(station-specific parameter)
(station-specific parameter)
(station-specific parameter)
(station-specific parameter)
<127> F_SC_NB_11 X
1 Blank or X only.
(station-specific parameter)
X Remote initialization
(station-specific parameter)
(station-specific parameter)
Read procedure
(station-specific parameter)
X Spontaneous transmission
(station-specific parameter)
The following type identifications will be transmitted in succession caused by a single status
change of an information object. The particular information object addresses for which
double transmission is enabled are defined in a project-specific list.
(station-specific parameter)
X global
X group 1 X group 7 X group 13
X group 2 X group 8 X group 14
X group 3 X group 9 X group 15
X group 4 X group 10 X group 16
X group 5 X group 11
X group 6 X group 12
Information object addresses assigned to each group must be shown in a separate table.
(station-specific parameter)
X Clock synchronization
Day of week used
RES1, GEN (time tag substituted/ not substituted) used
X SU-bit (summertime) used
(object-specific parameter)
(object-specific parameter)
Threshold value
Smoothing factor
Low limit for transmission of measured value
High limit for transmission of measured values value
(object-specific parameter)
(station-specific parameter)
Test procedure
(station-specific parameter)
Transparent file
Transmission of disturbance data of protection equipment
Transmission of sequences of events
Transmission of sequences of recorded analogue values
Transparent file
(station-specific parameter)
X Background scan
(station-specific parameter)
Long timeouts for t3 may be needed in special cases where satellite links or dialup
connections are used (for instance to establish connection and collect values only once per
day or week).
X Ethernet 802.3
Serial X.21 interface
Other selection from RFC 2200
13 Glossary
AC Alternating Current
AMI Analog Measured value Input
ASDU Application Service Data Unit
ASO Analog Setpoint command Output
BCI Bidirectional Communication Interface
BSI Bit String Input
BSO Bit String Output
CAM Central User Account Management
CMU Communication and Data Processing Unit
DCE Data Communication Equipment
DCO Double Command Output
DMI Digital Measured value Input (8, 16 bit)
DO Digital Output
DPI Double Point Input
DSO Digital Setpoint command Output (8, 16 bit)
EPI Event of Protection equipment Input (1 bit)
FSO Floating Setpoint Command Output
HCI Human Maschine Interface (here Integrated HMI function of the
RTU500 series)
IED Intelligent Electronic Device
IOA Information Object Address
ITI Integrated Totals Input
MAX Maximum
MFI Analog Measured value Floating Input
Min Minimum
MS Microsoft
NCC Network Control Center
PLC Programmable Logic Control
PRP Parallel Redundancy Protocol
RCO Regulation step Command Output
RFC Request for Comments
RTC Real Time Clock
Note:
The specifications, data, design or other information contained in this document (the
“Brochure”) - together: the “Information” - shall only be for information purposes and shall in
no respect be binding. The Brochure does not claim to be exhaustive. Technical data in the
Information are only approximate figures. We reserve the right at any time to make technical
changes or modify the contents of this document without prior notice. The user shall be
solely responsible for the use of any application example or information described within this
document. The described examples and solutions are examples only and do not represent
any comprehensive or complete solution. The user shall determine at its sole discretion, or
as the case may be, customize, program or add value to the ABB products including software
by creating solutions for the end customer and to assess whether and to what extent the
products are suitable and need to be adjusted or customized.
ABB AG shall be under no warranty whatsoever whether express or implied and assumes
no responsibility for the information contained in this document or for any errors that may
appear in this document. ABB AG's liability under or in connection with this Brochure or the
files included within the Brochure, irrespective of the legal ground towards any person or
entity, to which the Brochure has been made available, in view of any damages including
costs or losses shall be excluded. In particular ABB AG shall in no event be liable for any
indirect, consequential or special damages, such as – but not limited to – loss of profit,
loss of production, loss of revenue, loss of data, loss of use, loss of earnings, cost of capital
or cost connected with an interruption of business or operation, third party claims. The
exclusion of liability shall not apply in the case of intention or gross negligence. The present
declaration shall be governed by and construed in accordance with the laws of Switzerland
under exclusion of its conflict of laws rules and of the Vienna Convention on the International
Sale of Goods (CISG).
ABB AG reserves all rights in particular copyrights and other intellectual property rights. Any
reproduction, disclosure to third parties or utilization of its contents - in whole or in part - is
not permitted without the prior written consent of ABB AG.
ABB AG
Power Grids
P.O. Box 10 03 51
68128 Mannheim, Germany
www.abb.com/remote-terminal-units