1. SPEED: A Stateless Protocol for Real-Time Communication in Sensor Networks T. He, J. A. Stankovic, C. Lu, T. Abdelzaher

2. Motivation: Why real-time communication? Sense networks monitor the real world Real-time constraints may exist Surveillance system Battlefield monitoring Earthquake response system Smart hospitals

3. Motivation Freshness of data Promptness of Command and Control 3

4. Need for a new real-time communication method Existing real-time communication solutions are inappropriate IntServ: too expensive for sensor networks Resource reservation Per-flow information Sensor nodes are referred to by attributes rather than unique ID’s DiffServ Control Area Network Small scale (mainly local area) Many restrictions for predictability

5. Need for a new real-time communication method (cont.) MANET protocols Time insensitive Less strict energy constraints Route discovery may incur a lot of delay and energy consumption AODV DSR LAR

6. Design Goals Provide E2E delay guarantee E2E delay is proportional to the distance between the source and destination Per hop speed guarantee Probabilistic soft real-time guarantees Impossible to provide hard guarantees SPEED actually improves but does not guarantees the E2E delay Support a desired delivery speed across the sensor network

7. Design Goals Localized behavior An action by a node does not affect the whole network Contrasts to MANET protocols (e.g., AODV & DSR) Stateless architecture Only maintains immediate neighbor info.

8. Design Goals Minimum MAC layer support SPEED does not require real-time/QoS-aware MAC support Congestion Control Traffic patterns may fluctuate significantly Short-term rate adjustment via feedback control Long-term backpressure re-routing Void Avoidance Backpressure re-routing Traffic Load Balancing Non-deterministic forwarding

9. Scalability Issues Time Scalability GF (Geographic Forwarding) to avoid route discovery E2E speed is proportional to the distance between the source & destination

10. s d Background – GF Choose the node closest to the destination in FS More appropriate for real-time communication than AODV or DSR

11. Scalability Issues (Cont.) Memory Scalability No per-flow state No per-destination route cache Just keep (immediate) neighbor table Energy Scalability No network-wide flooding Nondeterministic forwarding to balance energy consumptions

12. Assumptions Each node is aware of its location Periodic beacons to exchange location info. Beaconing rate can be very low when sensor nodes are static Senor network is dense enough to supporting greedy geographic routing, while avoiding a void

13. SPEED Architecture

14. SNGF (Stateless Non-deterministic Geographic Forwarding)  Neighbor Set of Node i  NS i = {node| distance (node, node i )  R}  Forwarding Set of Node i  FS i (Destination) = {node  NS i | L – L_next > 0 }

15. Definitions Speed Set Point Desired speed toward the destination Speed Miss One hop relay speed violates the set point Miss Ratio #packet misses in a specified period

16. SNGF

17. Forward a packet to a node that is in FS i and can support the speed set point Probabilistically select one node The higher its speed, the higher its probability If no node in FS i can support the set point, reduce the relay ratio via NFL

18. NFL (MAC Layer Feedback) Delay Estimation: Delay= Round Trip Time – Receiver Side Processing Time On/Off Switch Back-Pressure Rerouting Relay Ratio Control

19. Backpressure Rerouting based on MAC Layer Feedback & SNGF 2 3 5 9 10 7 Delay 11 Boo SPEED 20 110 30 115 Node 5's NT Delay 0.5s 0.1s 0.4s 0.1s ID 9 7 10 3 Packet Source Destination

20. Backpressure Rerouting based on MAC Layer Feedback & SNGF 2 3 5 9 10 7 Delay Boo ID Delay 5 0.5S 2 0.1S 4 0.1S Node 3's NT 4 11 6 1 3 ID Delay 5 0.1S 7 0.4S Node 6's NT 12 Packet 1 Beacon Packet 2 Packet (to 4)

21. Void Avoidance In a similar way it deals with traffic congestion. Backpressure beacon (ID, Destination, Positive Infinity) Greedy: It may not find a path even if it exists in the worst case 1 2 3 4 5

22. Last Mile Process AreaMulticastSend(Center position, radius, deadline, packet) AreaAnyCastSend(Center position, radius, deadline, packet) UnicastSend(Global_ID,deadline,packet) SpeedReceive()

23. Evaluations: Simulation Setup -1 ComponentsSetting Simulator & TestBedGloMoSim & Berkeley Motes RoutingSPEED, AODV, DSR, GF (Max Progress ) SPEED-S (Max Speed ), SPEED-T ( minimum delay) MAC Layer802.11 Bandwidth200Kb/s Payload size32 Byte TERRAIN(200m, 200m) Node number100 Node PlacementUniform Radio Range40m Runs16

24. Congestion Avoidance #E2E Delay vs. Congestion-Level Delay: AODV>DSR>SPEED Delay: SPEED-T > GF,SPEED,SPEED-S (Heavy Congestion) Delay: SPEED performs best

25. Control Overhead #Control Packets vs. Congestion-Level SPEED uses periodic & on-demand beacons (Light Congestion) #Packets: DSR<GF,SPEED,SPEED-S,SPEED-T (Heavy Congestion) #Packets: DSR>SPEED>GF=SPEED-T=SPEED-S

26. Energy Consumption Energy Consumed: AODV>DSR>SPEED,GF,SPEED-S,SPEED-T Light Congestion: SPEED=GF=SPEED-S Heavy Congestion : SPEED>GF,SPEED-S When Rate<60, SPEED has more Control Packets than DSR, but consumes less energy than DSR. Why???

27. Void Avoidance Delivery Ratio vs. Node Density Delivery Rate: DSR>SPEED>SPEED-S=GF=SPEED-T

28. Reminder: RAP (Real-Time MAC) dis = 60 m; D = 2 s V = 30 m/s LOW Priority dis = 90 m; D = 2 s V = 45 m/s HIGH Priority A B D C E Velocity Monotonic Scheduling

29. RAP: Prioritized MAC Collision Avoidance (CA) Contention Channel idle  wait for (IEEE 802.11 (DCF) )Rand*DIFS (RAP) Rand*DIFS*Prio Collision (No CTS or No ACK)  (IEEE 802.11 (DCF) ) CW=CW*2 (RAP)CW=CW*(2+(Prio-1)/MAX_Prio)

30. SPEED vs. RAP Soft real-time No guarantees Ad hoc deployment Dynamic traffic Homogeneous platform Motes Soft real-time No guarantees Ad hoc deployment Dynamic traffic Homogeneous platform Motes Similarities Differences Ordinary, best-effort MAC SPEED=Distance/Delay Distance (node, neighbor) Reflect communication capacity Traffic Control SNGF MAC Layer adaptation Backpressure Rerouting Prioritized MAC Velocity=Distance/Deadline Distance (Source, Destination) Reflect local emergency Traffic Control VMS?? (No)

31. Research Issues (Possible Projects) QoS Metrics other than delay? Energy How long can a node support the desired speed or reliability? Bandwidth Reliability Data criticality Differentiated aggregation, scheduling, resource allocation … Confidence of event detection Coverage Optimal number of sensors to minimize energy consumption, while detecting events (if any)

32. Research Issues (Possible Projects) Derive feasible deadlines Admission control & adaptive deadlines Differentiated service MMSPEED: INFOCOM ’05 (Next Class) Speed differentiation & network resource conservation via data aggregation How to implement reliable area-multicast and anycast? Sensor database QoS Prediction based on current & historic sensor data