0% found this document useful (0 votes)
4 views5 pages

Overview of ICCP Protocol Features

The ICCP protocol allows real-time data exchange between SCADA control centers using MMS. It operates on a client-server model and defines bilateral tables that specify the data, permissions, and transmission formats. The implementation requires the configuration of communication links, nodes, variables, and security parameters such as digital signatures.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views5 pages

Overview of ICCP Protocol Features

The ICCP protocol allows real-time data exchange between SCADA control centers using MMS. It operates on a client-server model and defines bilateral tables that specify the data, permissions, and transmission formats. The implementation requires the configuration of communication links, nodes, variables, and security parameters such as digital signatures.
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

Chapter 5: ICCP PROTOCOL

5.1 Introduction
The ICCP (Inter Control Center Protocol) is a protocol designed for the
real-time data transfer between control centers (on-line) is considered
also as an open protocol.

The ICCP protocol specifies the use of MMS (Manufacturing Messages


Specification that defines the nomenclature, listing, and addressing of the variables and
the interpretation of messages [Sisco, 2009].

The ICCP protocol is based on client-server concepts; it is perhaps one of the


main objectives to achieve the implementation of software interoperability
different suppliers.

In figure 5.1, the operation of the ICCP protocol is observed, with the example of
two SCADA control centers (A and B), which exchange information from each of
their substations (D and C).

Figure 5.1 - Operation of ICCP Protocol [Sisco, 2009]


In our country, this protocol is being used more and more in applications.
electric, as there are standards that establish the ICCP as an integration protocol
for the real-time information exchange between supervisory bodies and the
electric companies.

For the implementation of this protocol, the following is needed:

Implementation of a robust communication medium.

Definition of nodes and configuration of the client and server.

Definition of variables to be transmitted or received.

5.2 Characteristics of the ICCP protocol


Among the main features that we can name of this protocol are:
[Sisco, 2009]

The use of MMS (Manufacturing Messages Specification), which is a


international standard for data transfer for real-time processes
real.

Based on the concepts of client - server (slave - master).

Use bilateral tables in which the necessary characteristics are defined.


for data transfer between the master and the slave, in summary these
tables provide all the necessary permissions for their operation.

The ICCP protocol uses objects for the connection between two ICCP instances.
for data selection and dataset transfer.

The ICCP protocol is a protocol designed to be modular, it uses blocks


which represents a function or set of functions, which means that
The control centers must define which blocks are needed.
Among the most commonly used blocks we find:

Block 1 is the basic block, it allows for the exchange of data from:

Digital states.

Analog measurements.

Quality codes.
Timestamps.

Protection equipment events.

Block 2 corresponds to the exception report of each of the data. In this block
The points that will be reported when a state change occurs can be defined.
or if they exceed the deadband limits of the analog points.

Block 3 corresponds to the exception report of a block of data.

Block 4 corresponds to informational messages and is used for exchange.


of more complex information.

Block 5, device control, what it does is communicate the request to the server
client to control a device, is characterized by being only a
request for execution, no direct control implementation.

Block 6 allows the remote execution of a program, this is done prior to an agreement.
between the control centers and using the properties of the MMS.

Block 7 allows for the reporting of events, incorporates registration events and events
of condition.

Block 8 allows the use of additional objects that are required by the
user.

Block 9, related to time series data, can be collected data.


as historical information.

5.3 Implementation of SCADA data transfer -


SCADA through the ICCP protocol
For the implementation of data transfer between control centers (SCADA -
SCADA), the following guidelines must be taken into account.

We verified that in each of the Control Centers, the data acquisition is being
correctly carrying out, then perform a review of the necessary data in each
control center so that, in this way, we can ensure good
operation of the ICCP system.
We checked the connection between the control centers, verifying the speeds.
acceptable minimums for this type of data transmission (minimum 64 kbps).

Creation of the Bilateral Table, in this way we control access to the information and
the access to each of the data objects.

The bilateral table must be approved by both parties, this way we ensure that
both the server and the client exchange only the same information that was
defined in the table.

In the following table, an example of a bilateral table is shown, in which we can


observe the following fields:

Name is the designation given to points.

Periodicity is the time interval in which they will be exchanged.


points.

Permissions are the options that can be made for each point.

Format is the type of the point format.

Name Periodicity Permissions Format

Analog1 10 s Reading real value

Analog2 10 s reading/writing real value with quality data

real value with quality data

Analog3 4s reading/writing and time stamp

real value with quality data

State1 by exception reading/writing/execution and timestamping

State2 60 s reading/writing/execution timestamp

State3 by exception Writing timestamp

Table 5.1 – Example of Bilateral Table

Then the tuning parameters of the ICCP links are configured, such as:
Domain name.

Name of the bilateral table.

IP addresses of the ICCP servers.

TSEL, transport selector.

SSEL, session selector.

PSEL, presentation selector.

application process title

Finally, the respective tests for sending and receiving the data are conducted.
bilateral table.

5.4 Security in ICCP links


Due to hacker issues presented in various countries, electric companies
they are increasingly common targets for these attacks, due to the information that
found collected in a control center (SCADA) and therefore in some
servers, from which controls can be read, written, and executed for any
Electrical Substation that is reporting to the SCADA.

The ICCP protocol allows data to be encrypted so that only the two centers of
linked controls can decipher this information, for this use a schema of
authentication, through digital signatures (is a cryptographic method that associates the
identity of a person or a computer system to the message or document
[The given text is a URL and does not require translation.].

It should also be considered that all SCADA systems must be protected against
any hacking threat, that is why the recommendation for the implementation of
firewalls and maintenance of ethical hacking (professional certification for the
conducting hacking tests) [[Link]

You might also like