Presentation is loading. Please wait.

Presentation is loading. Please wait.

2012.1.12 Review of the literature : DMND:Collecting Data from Mobiles Using Named Data Takashima Daiki Park Lab, Waseda University, Japan 1/15.

Similar presentations


Presentation on theme: "2012.1.12 Review of the literature : DMND:Collecting Data from Mobiles Using Named Data Takashima Daiki Park Lab, Waseda University, Japan 1/15."— Presentation transcript:

1 2012.1.12 Review of the literature : DMND:Collecting Data from Mobiles Using Named Data Takashima Daiki Park Lab, Waseda University, Japan 1/15

2 Outline 1. Introduction 2. Background - ICN 3. System design of DMND 4. Simulation -compared to MobileIP 5. Conclusions 6. Reference 2/15

3 Vehicle manufactures desire to monitor the operation conditions of their released cars in order to 1) detect any potential problems. 2)collect information from cars for traffic congestion maps and weather maps. Introduction(1) Nowadays, more and more mobile devices get connected to the Internet, bringing great opportunities for new Internet applications. What kind of architecture is suitable for collecting date from mobile nodes? 3/15

4 NDN (Named Data Networking) architecture Introduction(2) TCP/IP architecture Each host is assigned an IP address; when a host moves, it must obtain a new IP address from its new location. Within the network, routing protocols build single best pass between any pair of communication hosts. Problem When end-hosts are mobile, their network connectivities tend to become intermittent. So, the traditional session-based communication is no longer the most appropriate model for networking and information sharing. A new proposal for a new Internet architecture has emerged. 4/15

5 Introduction(3) ICN (Information Centric Networking) architecture ICN assigns each piece of data a name that can be directly used by the applications. The network can use the application names directly for data communication, eliminating any mapping system between application names and flat identifiers. Advantage of naming data Applications can request data that may or may not have been produced yet, and request will be honored as soon as desired data becomes available[2]. [2]B. Ahlgren, M. D’Ambrosio, C. Dannewitz, M. Marchisio, I. Marsh, and B. Ohlman, “Design Consideraton for a Network of Information,”in ReArch 08, Madrid, SPAIN. ICN can eliminates the requirement that (1)each mobile must obtain an IP address in order to be connected. (2) requesters and data publishers must be online simultaneously for a network communication to happen. 5/15

6 Background(1) Simple ICN topology Data communication in ICN follows a 3-step process ・ routing announcement from data sources ・ forwarding of interest packets which are originated by data requesters ・ data flow from the data source to the requester R1-R4: ICN routers B1 and B2: Base station m1 and m2: two vehicles within the communication range of B1 and B2 6/15

7 Background(2) R1-R4: ICN routers B1 and B2: Base station m1 and m2: two vehicles within the communication range of B1 and B2 Simple ICN topology The whole system starts by base stations B1 and B2 announcing name prefix icn:/vehicle-data/ to the network in anticipation of passing by mobiles that produces data. R1 and R3 receive the name announcements and forward to their neighbors. As a result, in R1 adds to its FIB the name prefix associated with interfaces f0 and f2. 7/15

8 Background(3) R1-R4: ICN routers B1 and B2: Base station m1 and m2: two vehicles within the communication range of B1 and B2 Simple ICN topology The data base server sends out an Interest message with the name icn:/vihicle-data/v1 to the network. After R2 receives the interest packet, it would first look up its Content Store to see whether there is already cached data with the same name. If the router finds one, a response will be issued immediately. 8/15

9 Background(4) R1-R4: ICN routers B1 and B2: Base station m1 and m2: two vehicles within the communication range of B1 and B2 Simple ICN topology Otherwise, the router checks its PIT to see whether it has already forwarded an interest with the same name. If yes, the incoming interface of interest will be inserted into the matching name entry in the PIT table, to wait for requested content by previously forwarded interest. Interest message would be forwarded along paths R2-R1-B1-m1 and R2-R4-R3-B2-m2 9/15

10 System design of DMND Long-lived interest In the DMND design, authors propose to 1)increase the timer for PIT entries in intermediate routers and 2)have base stations broadcast a pending Interest several times before timing it out. Security Additionally in the DMND system, authors require all content to be encrypted using the public key of database server before being back from mobiles. And they assume the data collector has access to each mobile’s public key. 10/15

11 Simulation(1) Simulation topology node1-16: AP node17: publisher node18: data base server ・ Node 18 (data base server ) periodically send requests to the network in order to collect data from mobiles. ・ The following metric is used to quantify data collection efficiency(dte) of MobileIP and DMND 11/15 450m

12 Simulation ~MobileIP~(2) ・ Home agent(HA) of device is coined to be Node 1. ・ UDP is used to deliver request and replay packets. ・ The number of request packets sent by requester was 500. SpeedRequests sent by requester Requests received by publisher Replies received by requester dte 0500489.7 97.94% 0-10500227.4219.8543.97% 10-2050060.6548.19.62% Table1: Average number of packets sent and received in MobileIP HA 12/15 Reason for low dte of MobileIP in handling mobility While the mobile publisher moves from base station to another, there is a delay before it can be connected to the Internet again. The delay includes the time of assigning an new IP address.

13 Simulation~DMND~(3) SpeedRequests sent by requester Requests received by publisher Replies received by requester dte 0500496.4495.999.18% 0-10500495.6491.798.34% 10-20500497.3491.698.32% 20-30500496.3490.1598.03% 30-40500496.6489.6597.93% 40-50500497489.3597.87% Table1: Average number of packets sent and received in DMND ・ The requester(Node 18) sends out a total number of 500 interest messages. ・ Because the publisher is within transmission range of three APs(7,8,11), It’s likely to receive the same interest message multiple times. The total number of interest messages is more than that sent from node 18. 13/15

14 Conclusions ・ Caching of Interest and being able to be broadcasted from multiple base stations solves the problem of high-speed mobility, and masks intermittent connectivity from the application layer collection process. ・ Evaluation of the DMND design in Qualnet shows high data collection even when mobile devices are moving at a high speed. 14/15

15 Reference [1]W.Jiangzhe, W. Ryuji, Z. Lixia, “DMND: Collectiong Data from Mobiles Using Named Data,p49-p56” 2010 IEEE Vihicular Networking Conference. [2]B. Ahlgren, M. D’Ambrosio, C. Dannewitz, M. Marchisio, I. Marsh, and B. Ohlman, “Design Consideraton for a Network of Information,” in ReArch 08, Madrid, SPAIN. 15/15


Download ppt "2012.1.12 Review of the literature : DMND:Collecting Data from Mobiles Using Named Data Takashima Daiki Park Lab, Waseda University, Japan 1/15."

Similar presentations


Ads by Google