23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

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

1-4 Industrial Communication Systems<br />

following sections will show that this is still an insufficient requirement for connecting devices. This can<br />

only be achieved by profiles, which have been introduced as an additional layer on top of the ISO/OSI<br />

model during the development of field buses (virtually an additional layer 8). If it can be proven that<br />

devices cooperate, we have reached interoperability.<br />

1.2.1 Layer Functionalities<br />

The OSI model defines seven layers, each of which has dedicated functions. A brief description of these<br />

functions is given in the following.<br />

1.2.1.1 Layer 1: Physical Layer<br />

This layer covers the physical part of the <strong>communication</strong>. It contains all hardware specification data,<br />

including the signals used, the electrical and mechanical characteristics of the connection, and all functional<br />

parameters that are necessary, which include tasks like activating, maintaining, and terminating<br />

the physical connection.<br />

1.2.1.2 Layer 2: Link Layer<br />

The link layer is responsible for providing an error-free connection from one node to another node in<br />

the same network segment (point-to-point <strong>communication</strong>). It has to correct errors that occur during<br />

the physical transmission by using, for example, error-correction codes. For that, it needs error-correction<br />

algorithms and redundant information in the received data. It also adds source and destination address<br />

to the packets that are transmitted.<br />

1.2.1.3 Layer 3: Network Layer<br />

The network layer defines the path that packets take on their way through the network. A packet that is<br />

addressed to a destination address will not always be transmitted directly to its receiver but will rather<br />

be passed from one part of the network to the other until it reaches its destination. This is done by routing<br />

the packets, an algorithm that can be implemented in different ways, depending on the capabilities<br />

of the components. Layer 3 defines addresses, which are not related to the addresses on layer 2 (if they<br />

are implemented). The network layer also is responsible for establishing and terminating network<br />

connections and reestablishing broken network connections.<br />

1.2.1.4 Layer 4: Transport Layer<br />

The transport layer is responsible for the flow control of data that is sent from one end user to the other<br />

(end-to-end connection) and for assigning logical addresses to the physical addresses that are used by<br />

the network layer. It uses the network layers’ ability to establish network connections in order to guarantee<br />

that messages really reach their end users, which also includes retransmission of lost packets.<br />

1.2.1.5 Layer 5: Session Layer<br />

In order to establish a session, the session layer has to make sure that all the end users agree on the same<br />

session protocol; therefore, the participants first have to negotiate a common protocol, which is then<br />

used throughout the session. The session layer defines how a session is started and terminated, describes<br />

how data-exchange is established, and is responsible for end-user identification (e.g., by password).<br />

1.2.1.6 Layer 6: Presentation Layer<br />

The presentation layer defines how the information shall be formatted in order to make it understandable<br />

for the end user. If, for example, an integer number is transmitted, the presentation layer knows<br />

how to interpret the bytes that make up the number and is able to provide a mathematical value to the<br />

application layer (e.g., by first converting big endian to little endian). Conversion of data is covered here<br />

as well as optional encryption of information.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

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

Saved successfully!

Ooh no, something went wrong!