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.

5.3. Properties of Tree Paths 143<br />

area would yield an <strong>in</strong>tersection.<br />

When the deployment area is a square, we can roughly approximate the<br />

probability with which an <strong>in</strong>tersection between two trees occurs <strong>in</strong> the follow<strong>in</strong>g<br />

way. The “grey” zone occurs only on the side of l<strong>in</strong>e AB on which C is<br />

located. The closer C is to one node, the smaller the grey zone on this node’s<br />

side will be, but it will be larger on the other’s (this can be seen <strong>in</strong> Figure 5.3,<br />

where the shaded area close to B is much smaller than that close to A). In the extreme<br />

case, the grey zone will fill out the whole upper area almost completely.<br />

The other extreme is C be<strong>in</strong>g close to the l<strong>in</strong>e AB, and placed between A and B;<br />

<strong>in</strong> this case, the grey zone will be rather small <strong>in</strong> total. For a rough estimation,<br />

we may assume that one half of the upper area will be grey. In total, this means<br />

that <strong>in</strong> about one quarter of all pairs of tree paths, there will be an <strong>in</strong>tersection.<br />

Figure 5.4: Paths cross<strong>in</strong>g each other without an <strong>in</strong>tersection node<br />

This estimate is based on an ideal, cont<strong>in</strong>uous model. A real WSN is a<br />

discrete system, communication paths are not straight l<strong>in</strong>es, and their density<br />

is limited. This leads to a number of differences to the ideal model:<br />

• Paths that <strong>in</strong>tersect <strong>in</strong> the model do not necessarily <strong>in</strong>tersect <strong>in</strong> a real deployment.<br />

An example is shown <strong>in</strong> Figure 5.4. Note that if a Gabriel<br />

graph would be used, which is not necessary <strong>for</strong> tree rout<strong>in</strong>g, a situation<br />

as <strong>in</strong> this example cannot occur and the paths will def<strong>in</strong>itely <strong>in</strong>tersect.<br />

• In the real world, it is likely that paths <strong>in</strong>tersect <strong>in</strong> a location close to the<br />

communication endpo<strong>in</strong>ts s<strong>in</strong>ce paths are closer to each other and, s<strong>in</strong>ce<br />

there are only f<strong>in</strong>itely many nodes to choose from, it is more likely that<br />

they have one or more nodes <strong>in</strong> common.<br />

• An <strong>in</strong>tersection need not be restricted to one common node. It is possible<br />

that two paths have a segment <strong>in</strong> common, especially close to the<br />

endpo<strong>in</strong>ts. An example is shown <strong>in</strong> figure 5.6.<br />

These considerations lead us to the conclusion that the fraction of tree paths<br />

that <strong>in</strong>tersect should be roughly above one-quarter, but below one-half. In order<br />

to validate this assessment, we per<strong>for</strong>med a simulation experiment. Simulation<br />

runs were executed <strong>for</strong> ten different networks, 30 spann<strong>in</strong>g tree pairs <strong>for</strong> each

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

Saved successfully!

Ooh no, something went wrong!