Flat Routing Protocols
Flat Routing Protocols
Flat Routing Protocols
• Negotiation-based routing
• Multipath-based routing
• Query-based routing
• QoS-based routing
• Coherent based routing
• Bases on flooding
• Data is only forwarded to one randomly
selected neighbor
• Saves energy
13
Address and Data-centric
14
Sensor Protocols for Information via
Negotiation ( SPIN )
15
SPIN-1 - three types of messages
• ADV
– When a SPIN node has data to share, it can advertise an
ADV message containing meta-data.
• REQ
– A SPIN node sends an REQ message when it wishes to
receive some actual data.
• DATA
– DATA messages contain actual sensor data with a meta-
data header.
C
RDAE
ADQ
ADV DARA
D B A
TV EDTQA
V
ADV
E ARD
EDA
QTV
F
A
The SPIN-2 Protocol
• When energy is plentiful, SPIN-2 nodes
communicate using the same 3-stage protocol
as SPIN-1 nodes.
– Two Parts
• Query Propagation
• Data Propagation
• It is very reactive to
changes in path quality.
51
Contd…(Agents)
• After the table
synchronization
completes, the event
table will contain
the best routs to the
event
Contd…(Agents)
• The number of agents depends on the number of event.
• Event table have expiration timestamp
• 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.
Queries
• A query can be generated at any time by any nodes
and target to an event
• If a node has a route toward target event, it forwards
the query along the route
• If it does not, forward to random neighbor and
assume the query has not exceeded its TTL
• Query employs same mechanism as the agent, keep
list of recently seen nodes
• Some queries may not reach their destination,
application must detect the failure, flooding query
again or increase the queries TTL
Rumor Routing
• Create paths leading to each event
• Event flooding creates a network-wide gradient field
• Query sent random walk until find the event path
• No flooding event across the network
• Query discovers event path, then route directly to
the event
• If path cannot be found, application reubmitting the
query, flooding it.
Algorithm Stability
• Because this algorithm relies on random
decision(agent and queries)
• Performance not vary significantly over several runs
is important
Fault Tolerance
• After the routes were established some of the
nodes were disabled
• Probability of delivery degraded slowly for 0-
20% node failure
• Over 20% node failure, the performance
degraded more severely
Summary
• The rumor routing protocol uses a set of long-lived agents to
create paths that are directed towards the events they
encounter.
• In order to join the path, the queries are first sent on a
random walk in the network.
• Each node in the network maintains a list of its neighbors and
an event table
• If there is no route available, the node transmit a query in a
random direction.
• Then, node waits to know if the query reached the
destination for a certain amount of time, after which the node
floods the network if there is no response