Overview of Mobile Networking

1. Overview of Mobile Networking Sam Nelson Some slides borrowed from Prof. Ray and Prof. Jain

2. Mobile, Wireless Devices Mobile wireless communication devices are becoming ubiquitous • Goals • Allow communication to and from the Internet to mobile devices • Allow mobile devices in the same area to talk without going through infrastructure Smart phones Vehicular technology Emergency response

3. Why Study Mobile Networking? • WapReview : The total number of mobile Internet users: 1.05 billion, which in 2008 for the first time surpassed the total number of PC Web users (1 billion) • DigitalStats : (June 2009) In the last six months, uploads from mobile phones to YouTube jump by 1700%. • DigitalStats : When posed with the question "Which do you access Social Network sites from more, mobile phone or computer?”(Sample size=321, Japanese survey) • Computer 14.0% • Mobile phone 70.4% • Both about the same 15.0% • Don’t know 0.6%

4. Academia • Top conferences with interests in mobile computing: • ACM MobiCom • IEEE InfoCom • ACM Sigcomm • NSDI • IEEE SECON • ICDCS

5. Challenges of Mobile Networking • Topology can change very quickly • New links form and break • Nodes leave and join the system • Mobility occurs in the wireless domain • Interference • Propagation issues • Spectrum regulation and use • End-to-end paths may not actually exist

6. Protocol Stack Layer Mobility Challenges Application Sensing / emergency response, social networking Transport Reliable, in-order delivery / congestion control Network Establishing routes / addressing Link Interference / Hidden terminal Physical Wireless propagation issues

7. Mobile Networking Topics:Lecture Outline - Communicate to/from Internet - Infrastructure in 1-hop - Addressing Problems Mobile Clients on the Internet - Communicate within network - No infrastructure - Relatively high connectivity Mobile Ad-hoc Networks (MANETs) - Communicate within network - No infrastructure - Low connectivity Delay-Tolerant Networks (DTNs)

8. Mobile Clients on the Internet

9. Mobile Host on the Internet • Goal: Maintain two-way connectivity to Internet and a mobile host. For IP_A Internet Net A Net B IP_A

10. IP Addresses • What do IP addresses really mean? 213.86.83.116 / 8 Network Host IP address is for routing purposes Hence, they must change when a node changes networks IP addresses are topologically dependent and hence are bad choices for long lasting names in mobile environments

11. Mobile Host on the Internet For IP_A Internet • Solutions? • Change IP address  Connectivity is lost… what is host’s IP? • Keep IP address  Routing will fail... host not found. Net A Net B IP_A IP_B How can S send to the moved mobile host?

12. Mobile IP Solution • Mobile host keeps it’s old IP address, and gets someone to forward messages to it • It must inform this “someone” of it’s new address • Agents to help – home agent and foreign agent Old IP Referred to as “home address” New IP Referred to as “care-of address”

13. Mobile IP Solution MH Home Address: MH’s permanent IP address, network ID of this address identifies the mobile’s home network. Home Agent: a router attached to the MH’s home network maintains current location information for the MH is responsible for forwarding packets destined for the MH when MH is away from home. HA HN Home Network: the network identified with a mobile node R1 R3 Route Optimization FN FN R2 MH CH Foreign Network: a network, other than MA’s home network, that MH is currently attached to. Mobile Host: a host or router capable of changing its point of attachment to the Internet FA Corresponding Host: a host or router communicationg with a mobile node. Foreign Agent (FA) a router in the foreign network that the MH is visiting provides routing services to the MH; may serve as default router for outgoing packet from MH

14. Route Optimization • Triangular routing • Data goes from source to Home Agent to mobile device (or foreign agent) • Reverse path is different – Data goes from mobile directly to source • Instead of constant triangular routing, inform CH of care-of address • Allows CH to directly route to mobile host

15. Mobile Ad-hoc Networks

16. Ad-hoc Networks • Each mobile device (node) can act as a router • Links form and break based on mobility and environmental factors • Connectivity (e.g., high probability of instantaneous end-to-end paths existing) is assumed

17. Ad-hoc Networks • Goal: Nodes within the network can send data between themselves. • Challenges: • No centralized coordinator to help routing • No “default route” for nodes within the network • Fast topology changes • Limited bandwidth – can’t have too much overhead S D

18. Ad-hoc Networks • Nodes that want to route messages must: • Find out about the topology of the network • Use that topology to do something with the message S D Control Plane Data Plane

19. Routing Protocol Categories Control Plane • Proactive: • Nodes actively maintain and share topology information, regardless of if there is data to send • Generally timer- or event-based • Reactive (On-demand): • “Lazy” approach: Don’t do more work then you have to • Only discover topology/routes when there is data to send

20. Routing Protocol Categories Data Plane • Local next-hop forwarding: • Consult forwarding table for a next hop • Completely local decision • Source routing: • Source node places complete path in packet header • Intermediate nodes don’t have to consult their forwarding tables S A B D A B D

21. Reactive Protocols • Names are useful hints at understanding the protocol properties: Dynamic Source Routing (DSR) MANET Source Routing Ad-hoc On-demand Distance Vector (AODV) Reactive Next-hop Forwarding MANET Distance Vector

22. Dynamic Source Routing (DSR)From Shweta Jain’s Slides • When node S wants to send a packet to node D, but does not know a route to D, node S initiates a route discovery. • Source node S floods the network with route request (RREQ) packets (also called query packets). • Each node appends its own address in the packet header when forwarding RREQ.

23. Route Discovery in DSR [S] S RREQ broadcast E F A C G D B represents a node that has received RREQ for D from S. [X,..,..] Represents list of addresses appended to RREQ. A node receiving a RREQ rebroadcasts it exactly once.

24. Route Discovery in DSR [S,E] S RREQ broadcast E [S,A] F A C G D [S,C] B represents a node that has received RREQ for D from S. [X,..,..] Represents list of addresses appended to RREQ. A node receiving a RREQ rebroadcasts it exactly once.

25. Route Discovery in DSR S RREQ broadcast E F [S,E,F] A C G D [S,A,B] B [S,C,G] Destination D receives RREQ via G and F. It does not broadcast it further.

26. Route Discovery in DSR • Destination D on receiving the first RREQ, sends a Route Reply (RREP). • RREP is sent on a route obtained by reversing the route appended to received RREQ. • RREP includes the reverse route from S to D on which RREQ was received by node D.

27. Route Reply in DSR S RREP Unicast E F A [D,F,E,S] C G D B Reverse route in the header of RREP

28. Route Caching in DSR • Node S on receiving RREP, “caches” the route included in the RREP. • When node S sends a data packet to D, the entire route is included in the packet header • Hence the name source routing. • Intermediate nodes use the source route included in a packet to determine to whom a packet should be forwarded.

29. Data Delivery in DSR DATA [S,E,F,D] Cache on S: [S,E,F,D] S E F A C DATA packet Unicast G D B Source route size grows with route length.

30. Route Error DATA [S,E,F,D] • If the next hop link is broken when a data packet is being forwarded, a Route Error (RERR) is generate and propagated backwards. Cache on S: [S,E,F,D] S E F A C DATA packet Unicast G D B

31. Route Error RERR [F,E,S] [Failed link = FD] • If the next hop link is broken when a data packet is being forwarded, a Route Error (RERR) is generated and propagated backwards. • RERR contains the failed link info. Cache on S: [S,E,F,D] S E F A C RERR is Unicast G D B

32. Route Error RERR [F,E,S] [Failed link = FD] • When S receives RERR, it erases any cached route with the failed link. Cache on S: [S,E,F,D] S E F A C RERR is Unicast G D B

33. Aggressive Route Caching • Each node caches a new route it learns by any means • When node S finds route [S,E,F,D] to node D, node S also learns route [S,E,F] to node F and so on. • When node G receives RREQ [S,C] destined for node D, node G learns route [G,C,S] to node S and so on. • When node F forwards RREP [D,F,E,S], node F learns route [F,D] to node D and so on. • Basically, when forwarding any packet, the node learns a route to all nodes in the source route contained in the packet.

34. Contents of Caches on Selected Nodes After one RREQ-RREP Cycle • [P,Q,R] represents cached route at a node P. • More than one route may be cached for the same destination. • Compact data structures may be used to implement route caches (e.g., tree). [F,E,S] [F,D] [F,G,C,S] S E F A C G D [D,F,E,S] [D,G,C,S] B

35. Use of Route Caching • Salvaging: When node S learns that a route to node D is broken, it uses another route from its local cache, if such a route to D exists in its cache. • Otherwise, node S initiates route discovery by sending a route request • Reply from Cache: Node X on receiving a RREQ for some node D can send a Route Reply if node X knows a route to node D. • Aggressive use of route cache • can speed up route discovery. • can reduce propagation of route requests.

36. Route Caching: Beware! • Stale caches can adversely affect performance. • With passage of time and host mobility, cached routes may become invalid. • All cached routes containing a failed link are not erased by route error (RERR). • Only that route is erased that is attempted to be used • A sender host may try several stale routes (obtained from local cache, or replied from cache by other nodes), before finding a valid route.

37. Dynamic Source Routing: Advantages • Source routing: no special mechanism needed to eliminate loops. • On demand routing: Routes maintained only between nodes who need to communicate • Reduces overhead of route maintenance. • Route caching can further reduce route discovery overhead. • A single route discovery may yield many routes to the destination, due to intermediate nodes replying from local caches. • Useful when route breaks.

38. Dynamic Source Routing: Disadvantages • Not scalable: Packet header size grows linearly with route length due to source routing. • Network-wide flood: Flood of route requests may potentially reach all nodes in the network. Too much overhead. • Collision: Care must be taken to avoid collisions between route requests propagated by neighboring nodes • insertion of random delays before forwarding RREQ • Reply storm problem: Increased contention if too many route replies come back due to nodes replying using their local cache • Reply storm may be eased by preventing a node from sending RREP if it hears another RREP with a shorter route.

39. Dynamic Source Routing: Disadvantages • Stale cache problem: An intermediate node may send Route Reply using a stale cached route, thus polluting other caches. • This problem can be eased if some mechanism to purge (potentially) invalid cached routes is incorporated. • Current research: how to invalidate caches effectively. • Example: Timer-based. Or propagate the route error widely.

40. Ad Hoc On-Demand Distance Vector Routing (AODV) From Shweta Jain’s Slides • AODV retains the desirable feature of DSR that routes are maintained only between nodes which need to communicate. • AODV attempts to improve on DSR by maintaining routing tables at the nodes, so that data packets do not have to contain routes. • No caches are used. • Only one route per destination in the routing table. • Only maintain the freshest route, if multiple possibilities.

41. AODV • Route Requests (RREQ) are forwarded in a manner similar to DSR. • When a node re-broadcasts a RREQ, it sets up a reverse path pointing towards the source. • This is so that the RREP can get back to the source. • When the intended destination receives a RREQ, it replies by sending a RREP. • RREP travels along the reverse path set up when RREQ is forwarded.

42. AODV Route Discovery • Source floods route request (RREQ) in the network. • Reverse paths are formed when a node hears a route request. • Each node forwards the request only once (pure flooding). S RREQ broadcast E F A C G D B

43. AODV Route Discovery • Source floods route request in the network. • Reverse paths are formed when a node hears a route request. • Each node forwards the request only once (pure flooding). S Reverse Path E F A C G D B

44. AODV Route Discovery • Uses hop-by-hop routing. • Reverse paths are formed when a node hears a route request. • Each node forwards the request only once (pure flooding). S RREQ broadcast E F A C Reverse Path G D B

45. AODV Route Discovery • Uses hop-by-hop routing. • Reverse paths are formed when a node hears a route request. • Each node forwards the request only once (pure flooding). S E F A C Reverse Path G D B

46. AODV Route Discovery • Route reply (RREP) is forwarded via the reverse path. S E F A C Reverse Path G D B

47. AODV Route Discovery • Route reply is forwarded via the reverse path … thus forming the forward path. • The forward path is used to route data packets. S Forward Path E F A C Reverse Path G D B

48. Route Expiry on Timeout • A routing table entry maintaining a reverse path is invalidated after a timeout interval • Timeout should be long enough to allow RREP to come back • A routing table entry maintaining a forward path is also invalidated if unused for certain interval. • This means unused routes are purged. • Note that the route may still be valid.

49. Route Expiry • Unused reverse paths expire based on a timer. S E F A C Forward Path G D B

50. Link Failure Detection • Hello messages: Neighboring nodes periodically exchange hello or keep-alive messages. • Absence of any hello message for some time is used as an indication of link failure. • Alternatively, failure to receive several link-layer ACK for a transmitted packet may be used as an indication of link failure. • Note DSR needs to use one of the above as well.