Practical_modern_SCADA_protocols_-_dnp3,_60870-5_and_Related_Systems

58 Practical Modern SCADA Protocols: DNP3, 60870.5 and Related Systems
The actual functions within each layer are provided by entities such as programs,
functions, or protocols, and implement the services for a particular layer on a single
machine. Several entities, for example a protocol entity and a management entity, may
exist at a given layer. Entities in adjacent layers interact through the common upper and
lower boundaries by passing physical information through service access points (SAPs).
A SAP could be compared to a pre-defined ‘postbox’ where one layer would collect data
from the previous layer. The relationship between layers, entities, functions and SAPs
is shown in Figure 2.39.
In the OSI model, the entity in the next higher layer is referred to as the N+1 entity and
the entity in the next lower layer as N-1. The services available to the higher layers are
the result of the services provided by all the lower layers.
The functions and capabilities expected at each layer are specified in the model. However,
the model does not prescribe how this functionality should be implemented. The
focus in the model is on the ‘interconnection’ and on the information that can be passed
over this connection. The OSI model does not concern itself with the internal operations
of the systems involved.
The diagram below shows the seven layers of the OSI model.
Figure 2.40
The OSI reference model
Typically, each layer on the transmitting side adds header information, or protocol control
information (PCI), to the data before passing it on to the next lower layer. In some
cases, especially at the lowest level, a trailer may also be added. At each level, this
combined data and header ‘packet’ is termed a protocol data unit or PDU. The headers are
used to establish the peer-to-peer sessions across the sites and some layer implementations
use the headers to invoke functions and services at the layers adjacent to the destination
layer.
At the receiving site, the opposite occurs with the headers being stripped from the data
as it is passed up through the layers. These header and control messages invoke services
and a peer-to-peer logical interaction of entities across the sites. Generally, layers in the
same site (i.e. within the same host) communicate in software with parameters passed
through primitives, whilst peer layers at different sites communicate with the use of the
protocol control information, or headers.