Routing Techniques in Wireless Sensor Networks
Routing Techniques in Wireless Sensor Networks
Routing Techniques in Wireless Sensor Networks
IEEE Wireless Communication Dec 2004 Jamal N. Al-Karaki, The Hashemite University Ahmed E. Kamal, Iowa State University presented by R93725047
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Introduction (1/2)
Routing protocols in WSNs Differ depending on the application and network architecture Classified into three categories based on the underlying network structure:
Flat: Nodes are assigned equal roles Hierarchical: Nodes will play different roles Location-based: Nodes positions are exploited to route data
Classified into multipath-based, query-based, negotiationbased, QoS-based, and coherent-based depending on the protocol operation Trade-offs between energy and communication overhead savings
Introduction (2/2)
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Challenges (1/2)
Due to the relatively large number of sensor nodes, it is not possible to build a global addressing scheme for the deployment of a large number of sensor nodes as the overhead of ID maintenance is high Applications of sensor networks require the few of sensed data from multiple sources to a particular BS Sensor nodes are tightly constrained in terms of energy, processing, and storage capacities
Challenges (2/2)
In most application scenarios, nodes in WSNs are generally stationary after deployment except for maybe a few mobile nodes. Sensor networks are application-specific Position awareness of sensor nodes is important since data collection is normally based on the location Data collected based on common phenomena, so there is a high probability that this data has some redundancy
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Time-driven: for application requiring periodic data monitoring Event-driven: react due to a certain event (time-critical ap) Query-driven: response to a query (time-critical ap) Hybrid
Network dynamics
Transmission media
Data aggregation
Quality of service
Sensor nodes may generate significant redundant data To reduce the number of transmissions
Network lifetime often is considered more important Bounded latency for data delivery is a condition for time-constrained applications
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Flat Routing
Each node plays the same role Data-centric routing Protocols
Due to not feasible to assign a global id to each node Save energy through data negotiation and elimination of redundant data Sensor Protocols for Information via Negotiation (SPIN) Directed diffusion (DD) Rumor routing Minimum Cost Forwarding Algorithm (MCFA) Gradient-based routing (GBR) Information-driven sensor querying/Constrained anisotropic diffusion routing (IDSQ/CADR) COUGAR ACQUIRE Energy-Aware Routing Routing protocols with random walks
SPIN Message
ADV new data advertisement REQ request for ADV data DATA actual data message
Step1
Step2
Step3
ADV
REQ
DATA
Step4
Step5
Step6
Advantage
Simplicity
Drawback
Each node performs little decision making when it receives new data Need not forwarding table
Four elements
Interest Gradient
A task description which is named by a list of attribute-value pairs that describe a task Path direction, data transmission rate
Source
Sink
High rate
Drawback
The energy of node on shortest path is drained faster than another To implement data aggregation Not easy to realize in a sensor network Increasing the cost of a sensor node
Rumor Routing
Feature
Combine query flooding and event flooding Discovering arbitrary paths instead of the shortest path Rumor routing is attractive only when
The number of queries is larger than a threshold The number of events is smaller than another threshold
Assumption
The network is composed of densely distributed nodes Only short distance transmissions Immobile nodes
Rumor Routing
Basic scheme
Each node maintain
A lists of neighbors An event table Generate an agent Let it travel on a random path The visited node form a gradient to the event Transmit a query The query meets some node which lies on the gradient
Route establishment
Rumor Routing
The node sensing an event probabilistically generates an agent. The probability of generating an agent is an algorithm parameter In order to propagate directions to the event as far as possible in the network, a straightening algorithm is used
The agent maintains a list of recently seen nodes. When picking its next hop, it will first try nodes not in the list.
Feature
Optimality Simplicity
Minimum cost path criteria : hop count, energy consumption, delay etc. Need not to maintain forwarding table Need not to know an ID for a neighbor node
Drawback
The time to set the cost field is directly proportional to the size of the network
110
Gradient-based routing
Memorize the number of hops when the interest is diffused Minimum the number of hops to reach the BS To obtain balanced traffic and prolong lifetime:
A stochastic scheme An energy-based A stream-based scheme
IDSQ:
Information-driven sensor querying and constrained anisotropic diffusion routing (IDSQ/CADR) CADR
with global knowledge of sensor positions optimal position to route query to is given by xo = argx [Mc = 0] note: Mc = Mu (1 - )Ma The routing is directly addressed to the sensor node that is closest to the optimal position
COUGAR
View the network as a huge distributed database system Use declarative queries Abstract query processing from the network layer Disadvantages
May add extra overhead query layer Synchronization Leader nodes maintenance
COUGAR
ACQUIRE
Views the network as a distributed DB where complex queries can be divided into several subqueries The BS sends a query, which is then forwarded by each node receiving the query Each node tries to respond to the query partially bye using its precached information Triggered update obtaining information from all neighborhood within a look-ahead of d hops Query is returned back to the querying node as a completed response
ACQUIRE
Energy-Aware Routing
A destination-initiated reactive protocol It maintains a set of paths Choosing paths by means of certain probability depending on how low the energy consumption is
Energy-Aware Routing
Setup Phase
Directional flooding
Local Rule
Sensor Controller
p1 = 0.75 p2 = 0.25
10 nJ
30 nJ
Energy-Aware Routing
Data Communication Phase
Each node makes a local decision
0.3 Sensor
Controller
0.6
1.0 1.0 0.4
0.7
1/3
2/3 1/2
1/2
2/3
1/3
1
2
3/4
1/4
1/3
2/3
1/2
1/2
1
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Hierarchical Routing
Nodes will play different roles Advantages related to scalability and efficient communication Mainly two-layer routing Protocols
Select cluster heads Routing
Low Energy Adaptive Clustering Hierarchy (LEACH) Power-Efficient Gathering in Sensor Information Systems (PEGASIS) Threshold-Sensitive Energy Efficient Protocols Small Minimum energy communication network (MECN) Self-organizing protocol (SOP) Virtual grid architecture routing Hierarchical power-aware routing Two Tier Data Dissemination (TTDD)
Randomly select sensor nodes as cluster-heads, so the high energy dissipation in communicating with the base station is spread to all sensor nodes in the sensor network. Set-up phase each sensor node chooses a random number between 0 and 1 If this random number is less than the threshold T(n), the sensor node is a cluster-head.
After a certain period of time spent on the steady phase, the network
goes into the set-up phase again and enters into another round of selecting the clusterheads.
Me Head !!!
(CSMA-MAC)
Advertisement
To reduce energy consumption noncluster-head nodes: Use minimal amount of energy chosen based on the strength of the cluster-head advertisement. Can turn off the radio until their allocated transmission time.
Thanks for the
time slot, Heres my data
Based on the number of nodes in the cluster, the cluster-head node creates a TDMA schedule telling each node when it can transmit. This schedule is broadcast back to the nodes in the cluster.
Heres your time slot
Data Transmission
Phase
(TDMA)
Number of clusters may not fixed in any round. To avoid the case that there is no cluster-head in a round(PE-WASUN04,
Oct. 7, 2004)
Feature
Data fusion
Problem
Feature
Cluster-based routing protocol based on LEACH Time critical application The user can control the trade-off between energy efficiency and accuracy
A smaller value of the ST
more accurate picture of the network increased energy consumption
Drawback
Cannot distinguish a node which does not sense a big change from a dead or failed node Collision occurrence in the cluster
SMECN
v u G
Sensors are divided into clusters according to their sensed signal strength Three algs: DAM, EBAM, EMLAM
To elect a leader, information exchanges between neighboring sensors
15
14
12 10 12
11 10
Provides a solution to count a targets within each sensor cluster Consider the energy level of target signal sources The energy level is estimated by computing the signal impact area, combining a weighted form of the detected target energy at each impacted sensor. To convert the energy level into the corresponding target density: assume roughly constant source energy output for the targets.
EBAM algorithm:
MLAM algorithm:
: lifetime estimate
Feature
Source
Source Data
Source Data
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Hierarchical vs. Flat Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Protocols:
Geographic Adaptive Fidelity Geographic and Energy Aware Routing MFR, DIR and GEDIR The Greedy Other Adaptive Face Routing SPAN
Whats fidelity
Uninterrupted connectivity between communicating nodes
Whats fidelity
Node ranking
Adapting to mobility
Active node wins High energy node wins With GPS information
Estimated cost
h( N , R) h( N min , R) C ( N , N min )
c( Ni , R) d ( Ni , R) (1 )e( Ni )
Closest direction
A
S B
Closest neighbor to D
Route through the sequence of faces that intersect the line segment [S,D]. Go around each face. Switch to the next face at a common edge.
D
Starting at s, GOAFR proceeds in greedy mode until reaching the local minimum n1. The algorithm switches to face routing mode and explores the boundary of face F to find n2, the node closest to t on F's boundary. GOAFR falls back to greedy mode and finally reaches t.
SPAN
Goal
Turn off nodes without significantly diminishing the capacity or connectivity of the network
Core concept
Coordinator Forwarding backbone Non-coordinator
SPAN
Rule1: periodically broadcasts HELLO message
Current Status (coordinator or not) Current coordinator Current neighbors
A node decides to volunteer to be a coordinator if it discovers that two of its neighbors cannot communicate with each other directly or via one or two coordinators Avoid coordinator contention: delayed announcement If every pair of its neighbors can reach each other either directly or via some other coordinators To archive fairness, if one node has been a coordinator for some period of time and every pair of neighbor nodes can reach each other via some other neighbors (even if they are not coordinators yet)
SPAN
Announcement contention
1 3 2 1 2 4 6 Initial configuration 7 5 3 1
Boo
2 5
4
6 7
Boo
Boo
All the nodes are eligible Coordinator contention And try to be a coordinator at the same time
SPAN
Resolving announcement contention using backoff
utility 0<R<1
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Query-Based Routing
Destination nodes propagate a query for data Usually theses queries are described in natural language or high-level query language E.g.
Directed diffusion Rumor routing protocol
QoS-based Routing
Has to balance between energy consumption and data quality E.g.
SPEED (congestion avoidance)
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Future Directions
(2/2)
Leverage data processing inside the network and exploit computation near data sources to reduce communication Time and location synchronization Localization Self-configuration and reconfiguration Secure routing Integration of sensor networks with wired networks
Outline
Introduction Challenges Design Issues Flat Routing Hierarchical Routing Flat vs. Hierarchical Location-based Routing Routing Protocols Based on Protocol Operation Future Directions Conclusions
Conclusions
They have the common objective of trying to extend the lifetime of network Trade-off energy and communication overhead There are still many challenges that need to be solved
The End
Thanks for Listening