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.

Ultralow-Power Wireless Communication 10-5<br />

hidden-terminal problem, some protocols also neglect it and use direct channel access, assuming that collisions<br />

are unlikely due to rare wake-ups [EO08]. The resulting network protocols are quite simple from<br />

a WSN perspective, but very energy efficient for the sensor nodes, as long as the always-on coordinator<br />

is not taken into account.<br />

If the coverage area is large, then multi-hop approaches are more energy efficient than single-hop<br />

approaches [NPK06], because the signal strength falls in a logarithmic manner making short <strong>communication</strong><br />

distances significantly more energy efficient. These multi-hop approaches require specific routing<br />

approaches and coordinated wake-ups of the nodes forwarding messages. Simple CSMA protocols<br />

are not sufficient for that and more sophisticated MAC protocols need to be used, which are discussed<br />

later on in this section.<br />

Full flexibility of the network is usually reached with mesh networks. They add a topology control<br />

protocol layer allowing easy integration of mobile nodes. Other protocols provide a self-healing capability<br />

of the network often taking advantage of redundant nodes. Some approaches also consider enhancing<br />

the network lifetime through redundant nodes that mainly sleep for the first part of their life to take<br />

over the job of nodes that have used up their energy resources [TG02]. These redundancy approaches<br />

improve network reliability, but require higher hardware costs. Nonetheless, all these protocols add an<br />

overhead of management messages to the <strong>communication</strong> that require energy for transmission and keep<br />

nodes awake.<br />

A low duty-cycle is most important for ultralow-power devices. The <strong>communication</strong> needs to be coordinated<br />

in a way that still allows most of the network to be asleep. Several issues should to be avoided<br />

during <strong>communication</strong> like idle listening to the channel if no other node intents to send a message or<br />

overhearing messages not addressed to the node. Also, nodes should avoid transmitting messages to<br />

sleeping receivers (overemitting). Two or more senders should avoid sending messages at the same time<br />

on the wireless channel that causes collisions corrupting messages. As a result, an ideal <strong>communication</strong><br />

protocol ensures that sender and receiver are only awake for message transmission and sleep the rest of<br />

the time. This is manageable as long as only two nodes are involved and both work on a periodic schedule<br />

with synchronized clocks. In multi-hop networks, where a node may need to forward messages of<br />

other nodes, this requires suitable protocols that are discussed in the following paragraphs.<br />

Depending on how the wake-up intervals of nodes are coordinated in the network, the protocols<br />

can be distinguished in on-demand, asynchronous, and rendezvous-based approaches (Figure 10.5).<br />

On-demand approaches often use a second low-power, low-rate radio to wake-up a node for <strong>communication</strong><br />

[STS02]. This approach is limited in practice, due to the cost for the second radio and its range<br />

difference to the main radio as less energy is used.<br />

In asynchronous approaches, the sleep cycles of nodes are not synchronized. The common approach<br />

is that a sender waits until a receiver is awake to transmit the message. Therefore, nodes periodically<br />

wake-up and check for messages. B-MAC is the most commonly used protocol in which a sender starts<br />

with a long preamble [PHC04]. Other nodes waking up on their periodical schedule recognize this<br />

Wake-up message<br />

Preamble<br />

Synchronized<br />

wake-up<br />

Wake-up channel<br />

Sender<br />

Sender<br />

Data message<br />

Check<br />

Check<br />

(a)<br />

Data channel<br />

(b) Receiver<br />

(c) Receiver<br />

FIGURE 10.5 Illustration of typical wake-up approaches for MAC. (a) On-demand, (b) asynchronous,<br />

and (c) rendezvous based.<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!