Professional Documents
Culture Documents
I. I NTRODUCTION
Following the recent advances in micro-electromechanical
technology, wireless communications, and digital electronics,
it is technically and economically practical to manufacture a
large number of small and low cost sensors [1][4]. These
tiny sensor nodes consist of sensing, data processing, and
communicating components. It is possible to deploy these
sensor nodes inside or close to the inspected phenomenon,
and to organize them as a wireless sensor network (WSN).
These sensors measure ambient conditions in the environment
surrounding them and then transform these measurements into
signals that can be processed to reveal some characteristics
about phenomena located in the area around these sensors.
WSNs may consist of many different types of sensors,
such as seismic, low sampling rate magnetic, thermal, visual,
infrared, acoustic, and radar, which can monitor temperature,
humidity, vehicular movement, lighting condition, pressure,
soil makeup, noise levels, etc., and therefore they have a wide
range applications. For example, WSN is the key technology
for home automation, commercial building automation, ehealth, smart energy management (or smart grid), etc. Fig.
1 shows a number of target markets typically discussed for
WSNs. Deployment of a sensor network in these applications
can be in random fashion (e.g., dropped from an airplane
in a disaster management application) or manual (e.g., re
alarm sensors in a facility or sensors planted underground for
precision agriculture). Creating a network of these sensors can
assist rescue operations by locating survivors, identifying risky
areas, and making the rescue team more aware of the overall
situation in a disaster area.
Typically, WSNs contain a large number of sensor nodes
that have the ability to communicate either among each
978-0-7695-4041-2/10 $26.00 2010 IEEE
DOI 10.1109/CNSR.2010.71
Fig. 2.
Fig. 3.
Fig. 4.
305
latency and lower end-to-end performance. Besides, meshrouting requires more complex network protocols. This means
the routers require more embedded resources, which can result
in increased power consumption and costs.
Fig. 5.
B. Network Topologies
Topology refers to the conguration of the hardware components and how the data is transmitted through that conguration. Our testbed has been designed to support different
network topologies: star, mesh, and star-mesh hybrid.
1) Star Topology: In a star topology, all devices are within
direct communication range to the gateway, through which all
messages are routed, as can be seen in Fig. 5.a. A device
sends a message to the gateway, which then passes it on to
the destination device. Direct communication between the end
devices is not supported.
Advantage: its simplicity means that this topology does not
require a complex network layer or routing protocols. Also,
performance is generally high, with packets taking a maximum
of two hops to reach their destination.
Disadvantage: rst, there are no alternative paths between
the device and coordinator, so if a path becomes obstructed,
communication is lost between the device and coordinator.
Second, the radius of the network is limited by the radio range
between the coordinator and child devices (typically from 30
to 100 meters). Finally, networks must be carefully planned
to ensure good connections with no obstacles or interference
between the coordinator and child devices.
2) Mesh Topology: Mesh topology consists of a mesh
of interconnected routers and end devices. Each router is
typically connected through at least two pathways, and can
relay messages for its neighbors, as can be seen in Fig. 5.b.
Mesh topology supports multi-hop communications, through
which data is passed by hopping from device to device using
the most reliable communication links and most cost-effective
path until its destination is reached. The multi-hop ability also
helps to provide fault tolerance, in that if one device fails or
experiences interference, the network can reroute itself using
the remaining devices.
Advantage: rst, this topology is highly reliable and robust.
Should any individual router become inaccessible, alternative
routes can be discovered and used. Next, the use of intermediary devices in relaying data means that the range of the
network can be signicantly increased, making this topology
highly scalable. Last, weak signals and dead zones can be
eliminated by simply adding more routers to the network.
Disadvantage: this topology has a higher communications
overhead than the star topology, which can result in increased
A. Flooding Routing
Several sensor network applications rely heavily on a
network-wide broadcast service for disseminating information.
For example, sink nodes may often need to broadcast codeupdates, TAG-type queries, alarms, etc., to sensor nodes.
Flooding is considered as the simplest means of broadcasting.
A node initiates the transmission by broadcasting its message
to all of its neighbors and other nodes do the same thing upon
receiving the message until the message is delivered to its nal
destination.
This kind of routing is very simple and does not need to
maintain any routing information. However, the drawbacks
of ooding include implosion and resource blindness [6],
[7]. Implosion is caused by duplicate messages sent to the
same node, overlap when two nodes sensing the same region
send similar packets to the same neighbor. Flooding does not
consider network resources and thus results in large energy
consumption. Meanwhile, the main goal of a sensor broadcast
service is to deliver a single copy of the broadcast packet to
each sensor, while minimizing the number of transmissions.
Flooding is implemented in our testbed because it is employed for neighbor detection and/or route discovery in other
advanced routing protocols.
B. Gossip Routing
Gossiping avoids the problem of implosion introduced by
ooding by just selecting a random node to which to send
the message rather than broadcasting the message blindly [8],
[9]. In gossip-based protocols, each node contacts one or a
few nodes in each round (usually chosen at random), and
exchanges information with these nodes. The dynamics of
information spread bear a resemblance to the spread of an epidemic [10], [11], and lead to high fault-tolerance and selfstabilization [11][13]. Gossip-based protocols usually do not
306
Fig. 6.
Fig. 7.
that detects this break may locally repair the route if the
destination is close in number of hops to the node. If local
repair cannot be completed successfully or the option is not
supported, the node that detects the link break creates a Route
Error (RERR) message which reports the set of destinations
that are now unreachable and sends it to precursor nodes.
Then, the source of the active path starts a new route discovery
phase if a route to the destination is still needed. Data packets
waiting for a route should be buffered during route discovery.
An AODV node that belongs to an active route may
periodically broadcast local Hello messages for connectivity
management. After reception of a Hello message from a
neighbor, if no packet is received from that neighbor for more
than a given time, the node should assume that the link is
currently broken. Other link failure detection strategies include
link and network layer mechanisms. For example, unsuccessful
layer two transmissions may be used as an indication of a
link break for AODV. This method is known as Link Layer
Notication (LLN). The AODV specication does not mandate
whether the unsuccessfully transmitted packet triggering a link
failure detection should be buffered or not in this case.
In order to implement the AODV protocol in a very small
footprint, TinyAODV makes various simplications as listed
below:
RREP messages are only generated by the destination.
Routes never expire.
Only the hop count metric is used.
No messages are generated to keep routes active because
routes never expire. Route errors are generated when a
data message can no longer be sent over the path. This
is detected using link level acknowledgements.
There exists a major difference between the two latest
Fig. 8.
E-health application.
C. E-health
E-health refers to healthcare practice which is supported
by electronic processes and communication. Our testbed is
used to prototype an e-health application that can be deployed
in an emergency room or intensive care unit in a hospital.
As can be seen in Fig. 8, the patients vital signs (e.g., heart
rate, temperature) and disease-specic indicators (e.g., blood
pressure, EKG, EEG) are monitored on a continuous basis
by a number of sensors attached on the patients body. The
data collected by the medical sensors is time-stamped and
securely forwarded to a sensor gateway. The gateway then
securely forwards the aggregated information to a central
monitoring/managing system over a WiFi mesh network and
wired backbone network.
At pre-determined settings, alarms are issued and responses/actions could be triggered automatically. For example,
if during the monitoring of a diabetic patient the blood glucose
level falls below a certain threshold, an alert can be sent to
the patients, physicians and/or medical personnel. Fig. 8 also
highlights that the WSN cooperates with an indoor localization
308
309