02.02.2018 Views

Practical_modern_SCADA_protocols_-_dnp3,_60870-5_and_Related_Systems

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

180 <strong>Practical</strong> Modern <strong>SCADA</strong> Protocols: DNP3, <strong>60870</strong>.5 <strong>and</strong> <strong>Related</strong> <strong>Systems</strong><br />

8.1.5 IEC <strong>60870</strong>-5-1 1990<br />

Link transmission procedures<br />

This section represents the four frame formats from IEC <strong>60870</strong>-5-1 <strong>and</strong> then describes the<br />

internal processes in terms of the service primitives <strong>and</strong> transmission procedures. The<br />

service primitives are the control indications passed between the link layer <strong>and</strong> its higher<br />

level user, <strong>and</strong> the transmission procedures describe the sequence of events occurring over<br />

the physical communications link. A control field is described that is transmitted over the<br />

link <strong>and</strong> is used by the link layer procedures of each side of the link in controlling the<br />

transmission process. The terms unbalanced <strong>and</strong> balanced transmission are presented <strong>and</strong><br />

used to describe whether transmission can be initiated only by a master station, or by any<br />

station. Services <strong>and</strong> transmission procedures are presented in detail for both unbalanced<br />

<strong>and</strong> balanced transmissions.<br />

8.1.6 IEC <strong>60870</strong>-5-3 1992<br />

General structure of application data<br />

This section presents two models of the structure of data at the application level. The<br />

reference model 2 version shows how application user data, for example point information<br />

to be transmitted, is encapsulated within an application protocol data unit, with or without<br />

application protocol control information added, <strong>and</strong> then passed to the underlying link<br />

layer for transmission. It also describes a general structure for application data, <strong>and</strong> rules<br />

for forming application data units in general.<br />

8.1.7 IEC <strong>60870</strong>-5-4 1993<br />

Definition <strong>and</strong> coding of application information elements<br />

This section provides rules for the definition of information elements, <strong>and</strong> defines a<br />

common set of information elements that may be used for transmission of information in<br />

telecontrol applications. These include generic elements such as signed <strong>and</strong> unsigned<br />

integers, fixed <strong>and</strong> floating point numbers, bit-strings, <strong>and</strong> time elements. The intention of<br />

this section is to provide a set of information building blocks from which a companion<br />

st<strong>and</strong>ard, or profile can utilize selectively to build a complete set of application level<br />

information objects. No such set of information objects is selected by this section,<br />

however.<br />

8.1.8 IEC <strong>60870</strong>-5-5 1995<br />

Basic application functions<br />

This section describes the highest level functions of the transmission protocol, which are<br />

those application functions above layer 7 of the OSI model. Application service primitives<br />

are the request <strong>and</strong> response indications passed between the application layer <strong>and</strong> the<br />

application user. Application functions are described.<br />

A set of basic application functions <strong>and</strong> associated service primitives, or requests<br />

<strong>and</strong> indications, are presented. These cover the highest level functions that would be<br />

required to carry out telecontrol operations. They include station initialization, methods of<br />

acquiring data, clock synchronization, transmission of comm<strong>and</strong>s, totalizer counts, <strong>and</strong> file<br />

transfer. Again, it is stated in this section that it would be the role of a specific companion<br />

st<strong>and</strong>ard to select from these functions <strong>and</strong> possibly add to them in defining a complete<br />

working protocol.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!