lifecycle, we assumed a cluster-tree topology (Figure
1).
Figure 1: Cluster-tree wireless sensor network.
Every network cluster follows a well-defined tree
pattern formed of the following components: i) the
PAN (Personal Area Network coordinator) node at
the “zero” level; ii) the FFD nodes (Fully Functional
Device – sensing and routing or routing only) for
middle levels; and iii) optionally RFD nodes
(Restricted Functional Device – sensing only) as tree
leafs for ending levels (Koubaa, 2006).
The studied network has some important
characteristics: the network nodes are assumed to be
stationary and homogenous; the network MAC uses
special ZigBee hierarchical addressing mechanisms.
Self-organization feature is also present (Sohrabi,
2000); in-network communication type is single-hop
and multi-hop downstream (excluding RFD nodes)
and upstream; a base station controller (pc/laptop) is
used to interface with the network.
In the area of WSN applications, there are
scenarios in which these kinds of networks are used
to observe and deliver sensitive data. In these cases,
node-capturing attacks implying one or more nodes,
although it is developed after the WSN operation
stage of the lifecycle, could represent potential
threats. To overcome this type of malicious attacks,
we define a network self-destruction procedure that
will end the lifecycle for a wireless sensor network,
focusing on the in-network information destruction.
2.1 The Determination of the
Network’s Depth in a Cluster-tree
Topology
From a topological point of view, a cluster-tree
network is quantitatively characterized by the
number of nodes, the number of subtrees, the depth
(D) of each subtree and the network’s depth defined
as the maximum hop count to the PAN coordinator.
A practical solution for obtaining the network’s
depth is to use a hierarchical addressing mechanism,
at MAC level, every time a WSN self-organizing
procedure is executed (Wong, 2008). In this case,
the hierarchy already contains the network’s depth
as an implicit parameter.
Another approach for obtaining the depth of the
cluster-tree topology is based on a message
exchange technique like the one presented bellow.
The PAN station will perform an “identification”
procedure in the entire network. This procedure
assumes that the PAN knows the address and the list
of the neighbors for every sensor node within the
network. The network coordinator will send a
message to all nodes and will wait to receive
associated response messages. For each message
sent, a timestamp (starting timestamp) will be stored.
When the response message will arrive, PAN will
associate another timestamp (end timestamp) that
will specify the end of the two-message transaction.
The biggest difference between the two timestamps
values will match the farthest nodes.
2.2 Destruction Phase
After the data gathering and delivery process is
complete, the wireless sensor networks used in the
civil and military applications are usually kept into
an inactive state until further utilization or until the
hardware components are physically destroyed by
the environment. This is not a secure approach. A
possible solution for this issue is to engage a
procedure of network self-destruction immediately
after the WSN has reached the proposed scope.
Based on the already obtained value of the
network depth, the self-destruction procedure
continues with the destruction phase, divided in two
steps: the activation of node self-destruction
procedure which is started by the PAN node and it’s
performed bottom-up from the final nodes to the
base; the PAN destruction. The mechanism of self-
destruction is presented in the pseudocode depicted
in the Figure 2, which highlights the bottom-up
destruction strategy (the procedure starts with
farthest leafs of the cluster-tree and ends with PAN):
GET
m
//gets the value of the subtree’s depth
WHILE(
m
> 0){
FOR (every node A associated with
m
)
Destroy(node A) //activate self-destruction for A
GET
m
}
If(
m
<=0) Destroy(node PAN);
Figure 2: Self-destruction pseudo code description.
Besides the application’s software package, each
network node will contain, in our view, a small piece
of dedicated code – we named it node self-
WINSYS 2009 - International Conference on Wireless Information Networks and Systems
64