Named Data Networking Enabled WiFi in Challenged Communication Environments

Transcription

1 Named Data Networking Enabled WiFi in Challenged Communication Environments 1 Anthony Guardado, 1 Zilong Ye, 1 Huiping Guo 2 Lei Liu, 2 Liguang Xie, 2 Akira Ito 1 California State University, Los Angeles 2 Fujitsu Laboratories of America

2 National Park

3 Internet Service?

4 Use case A US National Park (No Internet, No Cellular, Limited GPS ) Hotel Data cached here Interest ( ) Only this NDN router has Internet access Interest ( ) Interest ( ) Entrance Data ( reply) Interest ( reply) Camping Area Data cached here In Repo: has some general information like Map (in every router), popular movies (in the routers in hotel and camping area), etc. Service agreement: via a mobile APP: every user who wants to use Internet services in the national park has to open some space to cache some data

5 Why IP cannot work in this scenario From the security point of view, in this scenario, users Data have to be cached in other users mobile phone o o IP s channel-based security is not attractive; NDN s packet-based security looks better; From the mobility point of view, NDN can better handle consumer mobility when the Data is returned o IP may need name resolution server Fixed IP needs a centralized server for IP management; Dynamic IP may introduce triangular routing; o NDN use name-based routing; From the network point of view, in this scenario, routers (i.e., links) are connected via vehicles (mobile apps). The connection is not stable and delays might be quite long o o Due to TCP Chatiness (e.g., 3 hours handshake and 1 min transmission time for 1MB photo), IP cannot work in this scenario because it is based on end-to-end communication; On the other hand, NDN/DTN can work well because NDN is based on hop-by-hop communication;

6 Advantages of NDN for this use case Easy to provide Internet access in the area without cellular, Internet and limited GPS (very common in sightseeing places like a US national park) It is a easy deployment as these NDN routers do NOT need to be connected via wired links: only need to place some NDN routers in the popular area, only the router at the entrance has to have the Internet access (it is quite natural as the entrance area is usually covered by Internet) Combine the advantages of NDN and DTN Outside the national park, the communication can still be based on IP (protocol translation via a gateway) Can be implemented as a mobile APP

7 System Architecture Consumer: The client that requests data by sending Interest via an Android App; Producer: The server that provides the Consumer Android App requested data on Internet; Relay: The App user that conveys both Interest and Data to NDN router, using NDN Router cache; NDN Router: An NDN router that installs NFD and can perform caching Producer Internet Relay Android App functionality;

8 Sequence Flow between Consumer and NDN Router Consumer NDN Router If data is available in CS, return data; otherwise check PIT Interest Data Check CS If there are same request, then aggregate; otherwise create new PIT entry Check PIT Aggregate or create new entry

9 Sequence Flow between NDN Router and Relay NDN Router Relay Update Neighbor Hello ACK NDN Router periodically check if there are new Relay nearby NDN Router fetch data from Relay Forward Pending Interest Data Check CS Update PIT Forward Updated Pending Interest ACK Update PIT Check CS Cache Interests not matched Notification Forward Caching Interest Data Update PIT Relay fetch data from NDN Router

10 Sequence Flow between Entrance NDN Router and Internet NDN Router (Entrance) Internet If Internet use NDN, just send Interest to get Data; otherwise Gateway is needed Interest Data

11 Consumer NDN Router Relay Internet Interest Data Check CS Consumer <--> NDN Router Check PIT Aggregate or create new entry NDN Router <--> Relay Hello Update Neighbor ACK Sequence Flow Check CS and cache Interest not matched Send Pending Interest Data Update PIT ACK Notification Interest Data Check CS Update PIT Update PIT Interest NDN Router <--> Internet Data

12 Forwarding Strategies First-Fit Flooding Hit-Aware-Multicast

13 First-Fit Strategy

14 1 First-Fit Strategy

15 First-Fit Strategy 2 1

16 First-Fit Strategy 2 1 3

17 First-Fit Strategy

18 Flooding Strategy

19 1 Flooding Strategy

20 Flooding Strategy 2 1

21 Hit-Aware-Multicast Strategy User 1 Hit Count: 6 User 2 Hit Count: 2 User 3 Hit Count: 4

22 Hit-Aware-Multicast Strategy User 1 Hit Count: 6 1 User 2 Hit Count: 2 User 3 Hit Count: 4

23 Hit-Aware-Multicast Strategy User 1 2 Hit Count: 6 1 User 2 Hit Count: 2 User 3 Hit Count: 4

24 Android Application

25 Experiment M1 M4 M0 M2 M3

26 EXPERIMENTAL RESULTS

27 EXPERIMENTAL RESULTS

28 EXPERIMENTAL RESULTS

29 Thank you!