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<br />

ISO/OSI Model<br />

Gerhard Zucker<br />

Vienna University<br />

of Technology<br />

Dietmar Dietrich<br />

Vienna University<br />

of Technology<br />

1.1 Introduction....................................................................................... 1-1<br />

1.2 Open Standard................................................................................... 1-3<br />

Layer Functionalities<br />

1.3 Vertical and Horizontal Communication..................................... 1-5<br />

1.4 Dynamic Behavior of Services and Protocols............................... 1-6<br />

1.5 Extensions, Benefits, and Discussion............................................. 1-9<br />

References...................................................................................................... 1-9<br />

1.1 Introduction<br />

The ISO/OSI model was developed and standardized in the late 1970s by the International Organization<br />

for Standardization as the standard ISO IS 7498. It supports designers by easing the definition of <strong>communication</strong><br />

protocols in a way that they operate correctly and are easy to maintain [Hay 88]. The name<br />

OSI originates from open <strong>systems</strong> interconnection. The model is not intended as strict implementation<br />

rules, because a real system will always have to adapt to requirements of price, economy, and flexibility.<br />

Instead, the ISO/OSI model represents an abstract definition (independent from hardware or software<br />

implementation) consisting of hierarchical layers. Related functions are grouped together in layers<br />

with strict separation between horizontal and vertical <strong>communication</strong>. The standard defines services,<br />

protocols, and interfaces. The original intention was to define a model for connecting computers for data<br />

transfer, logging into remote computers, and so on. Requirements like real-time, protocols for embedded<br />

microcontrollers or protocols for field buses were of no concern, which has to be considered when<br />

applying the ISO/OSI model to such <strong>systems</strong>.<br />

In a first step, all subfunctions that contributed to <strong>communication</strong>s were collected as shown in<br />

Figure 1.1 in the top right cloud, where each subfunction is represented by a circle. These subfunctions<br />

were then assigned to separate layers. The fact that the model consists of seven layers does not have technical<br />

reasons, but represents the common agreement between the participants of the workgroup that<br />

was responsible for the definition of the model. In this way, each layer was assigned to have a dedicated<br />

function, which consists of subfunctions.<br />

The protocol stacks (i.e., the <strong>systems</strong> that are designed based on this model) shall contain evenly<br />

distributed subfunctions over all layers. Subfunctions that are too different shall not be included in<br />

the same layer and the interfaces shall be designed toward a low amount of information that has to be<br />

exchanged between the layers (in order to keep the overhead low).<br />

The standard defines many more rules that shall encourage a uniform and logical structure. The use<br />

of specific description language (SDL) is required to avoid endless sequences of unstructured code as<br />

well as flow diagram, which in the end lead to the SDL and its corresponding tools [Ols 92] that are used<br />

in tele<strong>communication</strong>s.<br />

The ISO/OSI model was a great leap forward in the design of protocols. It created orderliness and a<br />

uniform structure that builds a commonly approved base for the standardization of protocols and<br />

1-1<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!