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.

19-2 Industrial Communication Systems<br />

at specific moments and other applications that impose no more than a certain delay for its signal.<br />

If these conditions are not reached simply, the client side of these applications will not work properly<br />

and we will be losing quality.<br />

Technically speaking, network QoS can be defined as the application of functionality and features<br />

to actively manage and satisfy networking requirements of applications sensitive to delay, loss, or delay<br />

variation (jitter), guarantying also the availability of bandwidth for critical application flows.<br />

Using QoS methods and technologies [2,3] several benefits are reached:<br />

• Control over resources: It can be determined which network resources (bandwidth, equipment,<br />

etc.) are being used. For example, critical traffic as voice or video over IP may consume a link and<br />

QoS helps control the use of the link by dropping low-priority packets.<br />

• More efficient use of network resources: Using network analysis management and accounting<br />

tools, it can be determined how traffic is handled, and which traffic shows latency, jitter, or packet<br />

loss. QoS tools [1] can be used to tune the handling of the traffic.<br />

• Coexistence of critical applications: By using QoS technologies, it is possible that most critical<br />

applications receive the most efficient use of the network. It is possible, for example, that time-Â<br />

sensitive multimedia, which requires bandwidth and minimized delay, get them while other applications<br />

in the same link receive fair service without interfering with critical applications traffic.<br />

These needs are directly linked with the idea of QoS, seen as a sum of value and warranty, being only<br />

a part of the framework of services management for best practices IT recommendations, as ITIL or<br />

CobIT [4]. The value of the network is what we search using a particular network, the particular <strong>communication</strong><br />

between different kind of devices. For the case of an <strong>industrial</strong> network, the value is going to<br />

be what we want to get with <strong>communication</strong> between servers and clients in our <strong>industrial</strong> network. The<br />

warranty is much more linked with the quality, meaning a defined set of features for a concrete network<br />

and can be expressed as the level of service of the network for a number of features:<br />

• Availability or how much time is guaranteed that the network is up continuously<br />

• Capacity or how many resources (dedicated bandwidth, delay, etc.) are available for each of the<br />

applications and how is the capacity to react to a change in the need of resources<br />

• Network security or the ability to protect any piece of information, following a security policy<br />

that include facts like the confidentiality, integrity, or authentication for any kind of access events<br />

in the network<br />

• Continuity as a sum of the other features, but specially thought for disaster incidents such as a<br />

fire or a flood<br />

Once the network management staff has built a Network Policy for all these features, it is necessary to<br />

know the tools for implementing each of the directives in the policy and, fortunately, we have now real<br />

technical solutions in place for these kinds of situations, and we have enough reliable standards.<br />

The rest of this chapter presents an introduction on how to manage all these features to get the best<br />

QoS for IP <strong>industrial</strong> networks, although practically every single piece of information in the chapter<br />

can be applied to any IP network. The real difference between <strong>industrial</strong> IP networks and non<strong>industrial</strong><br />

IP networks are the applications we run on them and, for IP QoS, we only need to know some general<br />

characteristic of these applications. The next section shows the important connections for QoS, previously<br />

defined, with the basics of information security topics and the efforts developed in the last years<br />

to build some standards for managing information security topics related with <strong>industrial</strong> networks.<br />

Then, we go in depth of the classical terminology, techniques, and architectures used today for getting<br />

a good QoS in any IP network, showing the two most important models: IntServ and DiffServ. Also, we<br />

analyze how the <strong>communication</strong> devices in the network can classify and mark any IP packet and how to<br />

manage the possible traffic congestion we can see in the same devices. To end, we analyze two possible<br />

situations we must manage only if our IP <strong>industrial</strong> network uses routers: the congestion avoidance and<br />

high availability solutions for routers.<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!