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.

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

3,4,6,7,8,9,10,11<br />

7<br />

4<br />

8<br />

2,4,5,6<br />

2<br />

1<br />

3<br />

3,5,6,7,8,<br />

9,10,11 2,6,8,9,10,11<br />

2,5,8,9,<br />

10,11<br />

5<br />

6<br />

9<br />

(a)<br />

3,5,6<br />

10<br />

11<br />

7<br />

4,7,8<br />

4<br />

8<br />

2,4,5<br />

2<br />

9<br />

5<br />

1<br />

5,6,9,10,11<br />

Figure 6.4: Canvas message overhead on the l<strong>in</strong>k level. Left: Authentication codes <strong>for</strong><br />

broadcast-based flood<strong>in</strong>g. Right: Authentication codes <strong>for</strong> a tree structure. Us<strong>in</strong>g a tree is<br />

much more economical<br />

<strong>in</strong> a subtree will receive the message. Nodes that become a member of multiple<br />

subtrees, which is likely to happen <strong>for</strong> many nodes, will receive the message<br />

multiple times. As root, such a node will construct its own subtree as the union<br />

of all subtrees it is part of. This ensures that all nodes will eventually receive<br />

the message.<br />

Compared to simple flood<strong>in</strong>g, the number of authentication codes that are<br />

transmitted is significantly reduced. This can be seen by look<strong>in</strong>g at a simple<br />

example. Figure 6.4 shows a network where nodes are labelled with numbers.<br />

Node number 1 is the source and floods a message to its neighbours. It adds<br />

authentication codes <strong>for</strong> its 1-hop and 2-hop neighbours (the l<strong>in</strong>ks are labelled<br />

with the target nodes of these codes; the message flow is from top to bottom). In<br />

Figure 6.4(a), simple flood<strong>in</strong>g is shown. In addition to the authentication code<br />

<strong>for</strong> its immediate neighbour, a node adds authentication codes <strong>for</strong> all of its 2hop<br />

neighbours to each outgo<strong>in</strong>g l<strong>in</strong>k. This is necessary s<strong>in</strong>ce simple flood<strong>in</strong>g<br />

is not aware of the topology beyond s<strong>in</strong>gle-hop neighbourhood. Figure 6.4(b)<br />

shows a similar graph with some edges miss<strong>in</strong>g. S<strong>in</strong>ce a node constructs a<br />

tree be<strong>for</strong>e it <strong>for</strong>wards a message, not all l<strong>in</strong>ks will be used to transmit the<br />

message. Nodes are now aware of their 2-hop neighbourhood and thus they<br />

can limit the set of authentication codes that have to be sent over a certa<strong>in</strong><br />

l<strong>in</strong>k. Thereby, a significant amount of data can be saved. This is confirmed<br />

by a large-scale simulation (500 nodes on a 1000 × 1000 plane with vary<strong>in</strong>g<br />

transmission range and there<strong>for</strong>e vary<strong>in</strong>g number of neighbours per node). As<br />

Figure 6.5 shows, the difference between simple flood<strong>in</strong>g and the structured<br />

approach is approximately 10-fold.<br />

(b)<br />

3,6<br />

3<br />

10<br />

5,6,11<br />

6<br />

11

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

Saved successfully!

Ooh no, something went wrong!