21.08.2013 Views

Protocols for Secure Communication in Wireless Sensor Networks

Protocols for Secure Communication in Wireless Sensor Networks

Protocols for Secure Communication in Wireless Sensor Networks

SHOW MORE
SHOW LESS

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

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

200 Chapter 6. Integrity-Preserv<strong>in</strong>g <strong>Communication</strong>s<br />

cluded <strong>in</strong> the process of shortcut assignment. By add<strong>in</strong>g some tolerance to<br />

the number of hops the token travels between assignments, the assignment can<br />

be balanced such that all nodes will eventually serve as shortcuts to the same<br />

number of other nodes.<br />

There are two major problems with this approach. First, the number of messages<br />

that have to travel through the network is very big. A r<strong>in</strong>g can be easily<br />

constructed based on a spann<strong>in</strong>g tree, <strong>for</strong> example us<strong>in</strong>g an Echo algorithm,<br />

which however leads to a rather <strong>in</strong>efficient r<strong>in</strong>g structure. For n nodes <strong>in</strong> the<br />

network, such a spann<strong>in</strong>g tree conta<strong>in</strong>s n − 1 edges and there<strong>for</strong>e the correspond<strong>in</strong>g<br />

r<strong>in</strong>g conta<strong>in</strong>s approximately 2n edges. In the optimal case, the r<strong>in</strong>g<br />

has n − 1 edges, but such a r<strong>in</strong>g is hard to construct. S<strong>in</strong>ce each token has to<br />

travel along each edge once, <strong>in</strong> total between roughly n 2 and 2n 2 messages have<br />

to be transmitted. A related problem is the fact that each node has to process<br />

at least n messages <strong>in</strong> total. The second problem is the distribution of shortcut<br />

nodes. With the described approach, an even distribution of shortcut nodes<br />

cannot be guaranteed.<br />

A more efficient assignment of shorcut nodes, which also provides an even<br />

shortcut node distribution, is based on a controlled selection process. Each<br />

node X partitions the network <strong>in</strong> nS geographical regions and sends a request to<br />

the center of each of these regions. The regions have to be constructed <strong>in</strong> a way<br />

such that with one shortcut node <strong>in</strong> each region, full coverage is provided. By<br />

construction, this approach provides an even distribution of the shortcut nodes.<br />

Its scalability is also improved compared to the token r<strong>in</strong>g approach. Each node<br />

sends nS request messages, receives the same amount of responses, and each<br />

message travels about L hops (average path length <strong>in</strong> the network). Thus, <strong>in</strong><br />

total 2nnSL messages are sent.<br />

6.5.3 Long-Range Interleav<strong>in</strong>gs<br />

In very large networks, it may be impossible to achieve full coverage with a<br />

limited number nS of shortcuts and a given δ as a message may not be able to<br />

reach the δ-neighbourhood of its dest<strong>in</strong>ation with a s<strong>in</strong>gle shortcut. However,<br />

there might be another node, which is already part of the message path, that has<br />

a shortcut <strong>in</strong> the δ area of the target, or at least closer to it than the previous one.<br />

Thus, while a message travels on its path to its dest<strong>in</strong>ation, additional shortcuts<br />

can be used to span the complete distance to the δ-region of the dest<strong>in</strong>ation.<br />

This idea is depicted <strong>in</strong> Figure 6.22. Here, two additional shortcuts are be<strong>in</strong>g<br />

used <strong>in</strong> order to get the message closer to the target G. The authentication l<strong>in</strong>ks<br />

“monitor” each other: The l<strong>in</strong>k between B and E ensures that the message is

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!