23.03.2017 Views

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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

53-10 Industrial Communication Systems<br />

53.3.3 time Keeping<br />

An ISA100.11a wireless network uses International Atomic Time (TAI) for its internal operation. It<br />

has been already stated that synchronization is fundamental to ensure a correct events reporting and<br />

<strong>communication</strong> protocols behavior. For this reason, devices must share a common sense of time; when<br />

a device sends a message to a clock source, it may receive a clock offset update in the acknowledge and,<br />

using this information, can correct its clock skew. Other devices could overhear and update their clocks<br />

based on the same message exchange, even if the ISA proposal does not address this issue. Obviously,<br />

each device that joins the network must specify the quality of its clock.<br />

53.3.4 the ISA100.11a Network Layer and Topologies<br />

The network layer header fields have been influenced by 6LoWPAN proposal [MG07,MKH07], and an<br />

attempt is made to facilitate future compatibility. In the ISA proposal, the concept of a network made<br />

up of ISA100 devices only (called DL subnet in the following) with respect to a backbone network has<br />

been separated; a backbone device is defined as a device interfaced to a non-ISA100 network, e.g., an<br />

<strong>industrial</strong> Ethernet or any other network within the facility interfacing to the plant’s network. The<br />

aim is to take into account power and bandwidth requirements on one side and allow for a huge variety<br />

of topologies on the other one. For this reason, several datagram formats have been considered<br />

for the network layer (e.g., using short addresses, 16 bit, for DL subnet devices and long addresses,<br />

64 bit identifier for the joining process and 128 bit addresses for backbones). In particular, three formats<br />

have been considered: the basic header is only used in a DL subnet (it is expected to be the most<br />

common format and minimizes the overhead); also the contract-enabled must be used only over a DL<br />

subnet but allows to include more information; the full header is the IPv6 header and is intended for<br />

use over the backbone. It is a network layer task to translate addresses and to manage packet fragmentation.<br />

It must be remembered that at the network layer, any device within a DL subnet is a single<br />

network hop away.<br />

53.3.5 the ISA100.11a Upper Layers<br />

A transport layer that provides connectionless services with optional security has been defined in the<br />

standard; it extends the UDP over IP version 6 and 6LoWPAN. The APL defines software objects that<br />

mimic real-world objects and also defines the <strong>communication</strong> services necessary to enable object-toobject<br />

<strong>communication</strong>.<br />

53.4 OCARI<br />

OCARI is an <strong>industrial</strong> wireless protocol specification [D08] that proposes a deterministic MAC layer<br />

for time-constrained <strong>communication</strong> and a network layer that has an energy-aware and proactive routing<br />

strategy for the non-time-constrained <strong>communication</strong> period. Its APL is based on the specification<br />

defined by the ZigBee Alliance. The following figure illustrates OCARI protocol stack architecture<br />

(Figure 53.10).<br />

53.4.1 Physical Layer<br />

The PHY of OCARI is based on IEEE 802.15.4-2006 PHY over 2.4.GHz frequency band. This RF is<br />

chosen because it is an ISM band that is usable worldwide. Moreover, there is a large choice of RF<br />

transceivers that implement IEEE 802.15.4 PHY 2.4.GHz. Major chipset makers such as TI, Freescale,<br />

Atmel, etc. propose optimized RF transceivers over this frequency band.<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!