However, almost all of the key sharing schemes
in a clustered sensor network have the same
problem: since the CH has the encryption keys of all
the nodes in the cluster to perform encrypted
communication, if the CH is analyzed, these
encryption keys are revealed. Moreover, when all
the nodes are set to the CH like in LEACH, another
problem arises, which is the need for big storage to
hold the keys of all the nodes in the cluster.
On the other hand, some key sharing schemes
use (k,n) secret sharing scheme. The secret sharing
scheme makes n shares from a secret, and the secret
can be restored from k (k
≦
n) shares. In the key
sharing scheme, when CH does not have any keys, it
restores the encryption key by receiving shares from
k neighboring nodes (Bertier et al., 2010). However
in these schemes, the encryption key is leaked either
by the analysis of k neighboring nodes or k
communication paths, both of which are smaller
than the total number of child nodes. Therefore,
some schemes, e.g., that proposed in (Yiying et al.,
2013) use a public key cryptosystem to hide the
shares. However, because of the computational
complexity of a public key cryptosystem, the energy
consumption of a node is very large.
In this paper, we propose the following three
kind of key sharing schemes using secret sharing
schemes.
(1) The first scheme realizes that, even if the nodes
including the CH are analyzed, the CH does not
at all reveal the key between the nodes that are
not analyzed. This means that this scheme
realizes information theoretical security on key
analysis.
(2) The second scheme is a key sharing scheme in
which the CH does not need to save the keys or
the shares on all the nodes in a cluster, but
manages only its own key. Realization of this
scheme requires the secret sharing scheme to be
improved. This scheme achieves computational
security.
(3) The third scheme is a key sharing scheme that
does not leak the key at all even if CH or all of
the child nodes are analyzed. This scheme can
either select information theoretical security or
computational security.
The first scheme is recommended if the user
wants to focus on information theoretical security
against CH analysis and if the storage capacity of the
nodes is sufficient to hold the keys. The second
scheme is recommended for Internet of Things (IoT)
device that requires fewer calculation and memory
resources. The third scheme is suitable for group key
sharing which is used as a common key within a
cluster.
The remainder of this paper is organized as
follows: In Section II, we explain LEACH and
discuss existing research studies on LEACH with
security. Section III describes the first scheme using
an existing secret sharing scheme. Section IV
describes the improved secret sharing scheme and
the second scheme. Section V presents the third
scheme and its variations. Finally, in Section VI, we
describe the performance evaluation.
2 EXISTING RESEARCH
STUDIES
2.1 Leach
LEACH is a protocol that selects a node that, in turn,
becomes the CH and averages the energy
consumption of all nodes to extend the life of
clustered sensor networks.
LEACH has two communication phases: a setup
phase and a steady-state phase. In the setup phase,
LEACH uses a random number to choose a CH in a
cluster. The chosen node then broadcasts a message
that it has become the CH. The nodes choose the
nearest CH and send a message that they have
become child nodes. The CH then sends a time
division multiple access (TDMA) schedule for the
steady-state phase to the child nodes. In the steady-
state phase, the nodes send the sensing data to the
CH according to the TDMA schedule. The CH
compresses the data received from multiple child
nodes and transmits the combined data to the BS.
2.2 SecLEACH
In SecLEACH, an administrator sets some element
keys to each node before use at random from a key
pool, which is a set of element keys. Each element
key has a key ID. SecLEACH performs key sharing
in the setup phase as follows:
1. The CH announces the key IDs to the child
nodes.
2. Each child node selects a key ID(s) that is (are)
common to the CH.
3. Each child node transmits the common key ID(s)
to the CH.
4. Each child node and the CH generate and save
the common key, which was generated by the
common element key(s).