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.

7-4 Industrial Communication Systems<br />

quality-of-service (QoS) parameters. It supports dynamic frequency selection, transmit power control,<br />

and spectrum and energy management. Besides enhanced security measures, radio resource management<br />

is also incorporated.<br />

Bluetooth [B04] is a low-power short-range <strong>communication</strong> technology designed to connect portable<br />

electronic devices like phones, PDAs, and keyboards. Whenever two Bluetooth-enabled devices<br />

come within range of one another, they seamlessly establish a small network. Although the maximum<br />

possible data rate is only 1.Mbps, low-cost and low-power capabilities of Bluetooth have stimulated its<br />

penetration in the market.<br />

Infrared is a point-to-point, ultra low-power, ad hoc data transmission standard designed to operate<br />

over a distance of 1.m and is extendable to 2.m with high power. It can achieve data rates up to 16.Mbps.<br />

Infrared is cheaper than Bluetooth technology, and both have their own advantages and disadvantages.<br />

HomeRF is a short-range <strong>communication</strong> technology intended for small area such as homes or small<br />

buildings. HomeRF uses frequency hopping spread spectrum (FHSS) while operating at 2.4.GHz and<br />

offers data rates up to 10.Mbps.<br />

ZigBee standard is a short-range wireless <strong>communication</strong> standard for PANs. It offers data rate up<br />

to 250.kbps at 2.4.GHz, 40.kbps at 915.MHz, and 20.kbps at 868.MHz with a range of 10–100.m. ZigBee<br />

uses IEEE 802.15.4 as physical and medium access control (MAC) layers. Upper layers as well as ZigBee<br />

security architecture are defined by the ZigBee standard.<br />

7.2 Protocol Stack<br />

7.2.1 transport Layer<br />

Transport layer protocols are responsible for end-to-end delivery of data. Transmission control protocol<br />

(TCP) is a dominant transport layer protocol for wired networks. TCP is responsible for congestion and flow<br />

control, and reliable and in-order delivery of packets. The unique characteristics of wireless ad hoc networks<br />

such as lack of infrastructure, mobility, shared bandwidth [SAHS03], contention, and high bit error rate<br />

(BER) as well as the design principles of TCP motivate to design customized transport layer protocols.<br />

7.2.1.1 Why TCP Does Not Suit Ad Hoc Networks?<br />

The failure of TCP to work well in ad hoc networks is because of the following known problems:<br />

• In layered architectures, TCP implicitly assumes that packet loss is caused due to collisions.<br />

Whereas, collisions in ad hoc wireless networks are one of the possible causes of packet loss,<br />

although there are also other potential causes such as fading, varying link quality [CZWF04],<br />

interference, and noise.<br />

• Two communicating nodes as well as other nodes sharing the same medium contend for the medium.<br />

• The packet loss in wireless networks is comparatively higher, and loss of retransmitted packet<br />

further degrades the performance.<br />

7.2.1.2 transport Layer Protocols for Ad Hoc Networks<br />

Transport layer protocols for ad hoc networks can broadly be classified into two major approaches<br />

[MK04]; TCP variants and non-TCP variants.<br />

The basic idea of TCP variants is to retain TCP as a transport layer protocol, because of its global<br />

existence, and to suggest modifications in order to overcome the problems associated with wireless links<br />

and mobility. TCP feedback (TCP-f) [F94] is customized in such a way that the sender is able to differentiate<br />

between congestion and a lost link. In this way, the invocation of congestion control algorithm<br />

is restricted, which in turn stops performance degradation. In case of link failure, the sender node is<br />

explicitly notified by the network layer of the neighbor node. The sender stops sending further packets,<br />

while all other nodes listening to these notifications invalidate these routes to avoid packet loss. Explicit<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!