Wireless Sensor Networks : Technology, Protocols, and Applications
Wireless Sensor Networks : Technology, Protocols, and Applications
Wireless Sensor Networks : Technology, Protocols, and Applications
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
EXISTING MIDDLEWARE 257<br />
tools <strong>and</strong> services to create WSN applications. Em* tools can be used to support<br />
deployment, simulation, emulation, <strong>and</strong> visualization of live systems, <strong>and</strong> its<br />
services include link <strong>and</strong> neighborhood estimation, time synchronization, <strong>and</strong><br />
routing. Em* supports flooding-based, geographical, <strong>and</strong> quad-tree-based routing<br />
protocols, <strong>and</strong> supports many devices <strong>and</strong> a variety of radio hardware. It does not<br />
provide information on how to adapt or manage network resources while utilizing<br />
application knowledge.<br />
8.4.8 Impala<br />
Impala [8.10] is lightweight middleware <strong>and</strong> an API for sensor application<br />
adaptation <strong>and</strong> update which can improve system reliability <strong>and</strong> energy efficiency.<br />
It is event-driven middleware that achieves effective application adaptation.<br />
It is intended to act as an operating system, resource manager, <strong>and</strong> event filter<br />
on top of which specific applications can be installed <strong>and</strong> run. This WSN middleware<br />
contains three middleware agents: an application adapter, an application<br />
updater, <strong>and</strong> an event filter. The application adapter adapts applications to various<br />
runtime conditions in order to improve performance, energy efficiency, <strong>and</strong><br />
robustness. The application updater receives <strong>and</strong> propagates software updates<br />
through the wireless transceiver <strong>and</strong> installs them on the sensor node. The<br />
event filter captures <strong>and</strong> dispatches events to the application adapter <strong>and</strong> updater,<br />
<strong>and</strong> initiates chains of processing. Impala has five types of events: timer, packet,<br />
send done, data, <strong>and</strong> device failure. <strong>Applications</strong>, the application adapter, <strong>and</strong><br />
the application updater are all programmed into a set of event h<strong>and</strong>lers which<br />
are invoked by the event filter when events are received. Impala supports both<br />
parameter- <strong>and</strong> device-based adaptations. An example of the application adapter<br />
is: When a device failure is detected, history-based protocol is switched to<br />
flooding protocol.<br />
8.4.9 DFuse<br />
DFuse [8.11] is proposed for programming fusion applications, <strong>and</strong> it is middleware<br />
only for data fusion. Data fusion focuses on decision making based on data <strong>and</strong><br />
information that is acquired, filtered, <strong>and</strong> correlated with other relevant information.<br />
That process would involve information conversion into an appropriate format,<br />
which may be acquired from one or multiple sources. Data fusion of multiple<br />
sources usually reduces uncertainty, improves the reliability of event detection,<br />
<strong>and</strong> enhances system tolerance <strong>and</strong> robustness. When performed systematically<br />
with an appropriate application in mind, it reduces volume, improves QoS, <strong>and</strong><br />
reduces energy consumption. In WSNs, data fusion may occur in the sink or sensor<br />
nodes. If the fusion point is closer to the geographical area where the data have been<br />
generated, the data filtering/aggregation efficiency could be higher. If the data<br />
fusion point is too close to the area, the fusion operation will be limited to a few<br />
sources <strong>and</strong> therefore will be less immune to undetected errors. Therefore, the data