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-6 Industrial Communication Systems<br />

End-to-end<br />

protocols<br />

7<br />

Applicationoriented<br />

protocols<br />

Point-to-point<br />

4<br />

1<br />

Transportoriented<br />

protocols<br />

FIGURE 1.4<br />

Layer build-up as blocks.<br />

1.4 Dynamic Behavior of Services and Protocols<br />

Figure 1.5 shows a common example of <strong>communication</strong> that runs over an intermediate station, e.g., a router.<br />

One side, e.g., the left side, starts transmitting a message, which is done by the application using the application<br />

layer. Communication runs vertically down to layer 1, horizontally through the router to the receiving<br />

device, and vertically up to the application in the receiving device. This <strong>communication</strong> can also be seen as<br />

parallel horizontal <strong>communication</strong>s that run between each layer as peer-to-peer <strong>communication</strong>s.<br />

Due to the modularization that the OSI model requires, all layers operate simultaneously. Consequently,<br />

the layers can operate independently, the interfaces can be defined easily and systematically, and the different<br />

tasks can be clearly assigned to the different layers.<br />

Each layer in the OSI model contains a definition of the protocol and the services. The protocol specification<br />

contains the exact number of functions and messages (protocol data units, PDUs)—so to say<br />

the “language” of the layer. The layer itself is characterized by the procedures that operate on the PDUs.<br />

The service definitions can be explained as follows: two opposing entities (the service users, SU)<br />

exchange information using protocols (peer-to-peer protocols) by using the service providers (SP). Thus,<br />

a service provider offers services to a service user, so that the service user can fulfill its task. Service<br />

<strong>communication</strong> runs vertically, where lower layers offer services to higher layers (with the exception of<br />

the lowest layer).<br />

Seen from a logical perspective, the layers of entities communicate with each other (i.e., layer n of<br />

one entity communicates with layer n′ of the other entity). In the vertical direction, service primitives<br />

are passed on using the service access points (SAP) as shown in Figure 1.6. There is no <strong>communication</strong><br />

defined between layer n − 1 and layer n + 1. The <strong>communication</strong> between two adjacent layers can<br />

be compared to master–slave <strong>communication</strong>, because a master does not communicate with a slave,<br />

Subnet a<br />

Subnet a΄<br />

7<br />

6<br />

5<br />

4<br />

3<br />

2<br />

1<br />

Application layer protocol AL<br />

Application layer protocol PL<br />

Converter<br />

3 3<br />

2 2<br />

1 1<br />

Information flew<br />

7 Application layer<br />

6 Presentation layer<br />

5 Session layer<br />

4 Transport layer<br />

3 Network layer<br />

2 Link layer<br />

1 Physical layer<br />

Internal subnet-protocol<br />

Network protocol NL<br />

Link layer protocol LL<br />

Physical layer protocol LL<br />

FIGURE 1.5<br />

Communication over subnets.<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!