The study of Information-Centric Network Disaster System
A thesis submitted to the Department of Computer Science and Communication Engineering,
The Graduate School of Fundamental Science and Engineering of Waseda University
In Partial Fulfillment of the Requirements for the Degree of Master of Engineering
February 1st,2016
By
Zhang Chengcheng (5114FG03-4)
of
SATO Laboratory (Professor Takuro Sato)
Abstract
Title of thesis: The Study of Information-Centric Network Disaster System
Zhang Chengcheng, 2016 Thesis directed by: Professor Takuro Sato
Information-centric networking (ICN) is one of the innovative network architecture that is being considered as one of the approach to solve various problems facing in the current IP network. In recent years, ICN has attracted increasing attention from many researchers because it based on content to communicate not like IP network which is based on address. Although many disaster study had been done by researchers, most of them are based on IP network, this study is based on ICN, we proposed a new naming scheme which come from GPS information, and use the CCNx to conduct the experimentation, then compare the performance of this system in CCN situation and TCP/IP network.
Key word: Content-centric Network, Disaster system, CCNx
Contents
Abstract ... 1
Acknowledgments ... 4
Abbreviation ... 5
List of figures ... 6
Chapter 1 ... 7
Introduction ... 7
1.1 Background ... 7
1.2 Related Work about Information-Centric Network ... 9
1.2.1 The Development of the Future Network Structure ... 9
1.2.2 Global Situation for Future Network ... 10
Chapter 2 ... 12
Information-Centric Network ... 12
2.1 Node Model ... 12
2.1.1 Types of Packets ... 12
2.1.2 Data Structure ... 13
2.2 Naming Scheme ... 14
2.3 Security ... 17
Chapter 3 ... 18
Disaster Information-Centric Network System ... 18
3.1 Disaster Scenarios ... 18
3.2 Previous Disaster System Works ... 19
3.2.1 Based on IP Network Disaster System ... 19
3.2.2 Disaster System Based on Information-centric Architecture ... 20
3.3 Information-Centric Network Disaster System ... 21
3.3.1 Naming Scheme ... 21
3.3.2 Function ... 22
Chapter 4 ... 24
Evaluation ... 24
4.1 Experimental tool: CCNx ... 24
4.1.1 Experimental Applications ... 25
4.2 Simulation ... 27
4.3 Simulation Result ... 32
Chapter 5 ... 34
Summary ... 34
5.1 Conclusion ... 34
5.2 Future work ... 35
Reference ... 36!
Acknowledgments
This research work has taken place at the Department of Computer Science and Communications Engineering, University of WASEDA, Japan.
I would like to express my sincere gratitude to all those who provided me the possibility to complete this research work, and firstly, I give a special thanks to my supervisor, Professor Sato TAKURO, who giving me an opportunity to study in Sato lab where I learned not only knowledge but also how to cooperate with other people to achieve a goal.
With his guidance, I could be able to complete this thesis. He also gives me the chance to participate in ICN disaster project, an experience that broadened my research view.
I would also like to thank to the other members of the ICN disaster project, my research would not have been possible without the support of these members, special thanks to Wen Zhen, the lead of this project. I would also like to express my thanks to my lab-mates, who have made valuable comments and suggestions to our project.
Finally, I would also like to express my thanks to my family for their support and love. Without their support, I cannot finish my master degree in Japan. There are no words I can say to express my thanks for what they have done.
Abbreviation
4WARD one of the Architecture and Design for the Future
Internet ... 11
ARPANET Advanced Research Projects Agency Network ... 7
CCNx an open source project based on ccn ... 26
CERN European Organization for Nuclear Research ... 7
FIA Application Programming Interface ... 16
ICN New Generation Network ... 14
NDN Named Data Networking ... 10
NSF National Science Foundation ... 16
NWGN New Generation Network ... 12
PIT Public Key Infrastructure ... 15
!
List of figures
Figure 1: Internet Systems Consortium[1] ... 8!
Figure 2: types of packet Modified and redraw from[2] ... 12!
Figure 3:naming structure of NDN (Modified and redraw from[9]) . 16! Figure 4:IP network disaster system ... 19!
Figure 5: global information network (modified and redraw from[14]) ... 21!
Figure 6: ICN-based disaster system application ... 23!
Figure 7: name segment in CCNx ... 25!
Figure 8: Packet transmission between proxies ... 26!
Figure 9: CCN repository ... 30!
Figure 10: ccnx packets ... 32!
Figure 11: download time in download disaster information from information-centric network and TCP network ... 33!
Chapter 1 Introduction
1.1 Background
we can see that when the development of computers began in the 1950s. the packet switching networks such as ARPANET, TELENET, were developed in the late 1960s and early 1970s with different communications protocols. In 1982, there was a suggest that the internet protocol suite(TCP/IP) should be used as the standard networking protocol.
After CERN began use TCP/IP protocol in its system, TCP/IP began to go global, for example, the Internet began to use in Asia in the late 1980s.after open the network to commerce, we can see that the number of internet hosts rose rapidly from the figure below Internet Systems Consortium 1 .
Figure 1: Internet Systems Consortium[1]
There are two-layer program in TCP/IP protocol. One is Transmission Control Protocol, the other is Internet Protocol, and gateway use to send the content to address where it should be.
In TCP/IP network, the client needs to get the IP address of server it wants to connect, it sent a request to the server in the internet, which means it communicate based on client/server model. TCP/IP communication, some researchers also call point-to-point communication, which means one point or one host sent a message to anther point or host which is decided by IP address, this client cannot get content from other host, and the server only sent the data back to that client in the same it got the request.
1.2 Related Work about Information-Centric Network
Though the TCP/IP protocol is widely used now, there are many problems, such as security, mobility, and so on. It relies on the connection between it travels, there are a lot of influence in the communication between client and server when the connect become bad.
There are also some security problems in TCP/IP protocol [2]; and also mobility problems, although currently there are some method to solve the mobility in network like Mobile IPv4 and Mobile IPv6, there are also many challenges we need to do to meet all kinds of needs in mobility. in IP network, because a packet is sent from the client to server host using the IP address protocol, so when a
l
ot of clients ask for the popular contents, in that time, the traffic explosion problem may be occurred. In this situation, many researchers have been proposing many different future network structure to fit these problems.1.2.1 The Development of the Future Network Structure
As the development of the technology, current IP network structure design seems become difficult to meet the increasing demands for bandwidth, mobility, and so on, so the future Internet structure has been proposed by some research communities.
There are already some Research programs have been set up to build the future Internet structure in different countries including the United States, the European Union (EU), China, Japan and so on.
Some programs focus on content or data oriented paradigms which is different from point-point communication scheme to content-based communication scheme, which means change from IP address to the data or content distribution. Other project based on the idea of mobility, security or cloud-computing-centric architectures.
1.2.2 Global Situation for Future Network
The Named Data Networking (NDN) [3] project is led by the University of California. in 2009 Van Jacobson give a very popular presentation about content-centric network in Bremen, Germany. And Van Jacobson also is one of the leaders of the NDN project. The idea of NDN project aim at change current host-centric IP architecture to an information-centric architecture, in this situation, the network just forward data, which we can consider that it changes from host-to-host packet delivery model to a content-centric model. The current Internet, which is known as “client-server” model, meet a lot of challenges as more and more demand on content distribution. Content-centric network structure is being considered as Future network structure, in future network model, we can see the network as “transparent”, it does not care about where data come from, where the request should be sent, it just transmit data, this model base on content to communicate in the network, it not like TCP/IP network which is based on address. The data are not named by the IP addresses. NDN project has several key
research issues should to be considered, like how the data should be named, how to make sure the data is secure enough and trustworthiness, and so on.
In European Union, there also some research projects about future internet architectures, one of famous projects is 4WARD [4] which aim at design a future Internet architecture to improve the quality of life for European citizens. In 4WARD, their use an information-centric paradigm not the node-centric paradigm. There are six work package in this project organization, architectural framework, generic paths, network of information, network virtualization, in the network management. Some of packages dear with the innovation needs, some study virtualization part, some part dear with the development and design of this architecture.
In Asian, there are also many countries have been doing some research projects on future Internet architectures, such as Japan and China. In Japan, New Generation Network (NWGN) [5], one of the future network program, which is supported by the Japan National Institute of Information and Communications Technology (NICT).
NWGN consists of many sub-projects which include architecture designs, test-bed designs, and so on. In China, there are also many programs have been down by universities and companies, like in Huawei technology, Tsinghua University. Most of these work are based on content-centric network.
Chapter 2
Information-Centric Network
In the current Internet, there are so many applications have an increasing demand for mobility and real-time communication, enough bandwidth, and so on. current IP network seems to cannot adapt it, Information-centric networking (ICN) is one of the method being proposed to solve this kind of problems.
2.1 Node Model
2.1.1 Types of Packets
there are two types of packets: one is Interest, the other is Data. The name of these two types of packets can include the information of data [2].
Figure 2: types of packet Modified and redraw from[2]
Interest packet Data packet
name
Selectors (order preference, publisher filter…….)
Nonce
Guiders (scope, interest lifetime)
Name
MetaInfo (content type, freshness period,…)
Content
Signature (signature type, key locator,……)
!
Communication in ICN is driven by issuing Interest packets. ICN routers forward Interests through hop-by-hop method. When a router received an Interest, it first checks its content store and if there is a copy of the data packet, then it forward the data packet through the face it comes, or it will go to Forwarding Information Base to conducts a longest prefix match and transfer the interest packet to the next hop according to outgoing face towards the data source.
2.1.2 Data Structure
there are three main data structures: CS (Content Store), PIT (Pending Interest Table) and the FIB (Forwarding Information Base) in the CCN nodes.
The CS is content cache which is organized for retrieval by prefix match lookup on name. the CS can store the packets it had transmit before, its different with IP packet which can use the packet just once. In this way, CCN can store Data packets as long as possible according to its replacement method.
The PIT is used to keep record of Interest packages which had been transmitted to data source. The PIT can record the face from where the interest comes in, when it consumes the PIT entry, it will discard this record in PIT table.
The FIB was considered as a strategy to forward Interest packets to potential source of Data. FIB table lookup plays a very important role in CCN routing, and when the interest is sent out from FIB, it will record the outgoing faces.
When an Interest reach a router, firstly, the router checks content store to see whether the requested content had already been stored in the CS, if there is a match in CS, it will send this data back on the same face the Interest arrives on.in this way, the router no need to forward it to next hop. If there is no content available in CS, the router will go to PIT to check whether there is an existing pending Interest. If there is a same record in PIT, PIT will just add the arrival face in the PIT entry, after that, it will drop it. If there is no match entry in PIT, the router will go to FIB to see to from which face it should send the Interest out, at the same time this Interest will be added to the PIT.
2.2 Naming Scheme
there are two main ICN naming schemes had been proposed: the first, hierarchical structure, which is human-readable, help scalability, it require a globally-agreed-upon PKI to bind names to keys. The second, self-certifying names, in this system, it uses its name as the key, so it need not use a PKI. No matter what kind of it, the name should enable a user to indicate the content of an object, it also should bind with the content object to provide content access authentication, and the name
should identify a content object with uniqueness [7]. There are many different naming schemes had been proposed by researchers. For example, Walter Wong [8] had proposed an idea to separate the security functionality in the names (or URLs) from the routing, forwarding and storage primitives, it used to verify the content. And some project focus on naming, like Networking Named Content (NDN) [9] is one of the four NSF FIA projects, we can know that naming scheme in NDN is in a hierarchy [Fig3].
Figure 3:naming structure of NDN (Modified and redraw from[9])
drft_naming.pdf srv_naming.
_v
_v _v
_s _s _s _s _s _s
~/r5ah ~/mfbar
cs.uwaterloo.c
uwaterl _v Version
_s segment Content
The NDN focus on the component structure. Names are created by users which is the same with ICN. Names include a lot of information like segment numbers and version.
2.3 Security
In future network structure, we know that the Internet will be changed from the host to the information-centric model, but the content delivery mechanism remains host-centric. So, some conflicts would be happened like content identification, trust establishment and security because we use the host- centric mechanisms in an information-centric networks. In host-centric paradigm, resources are identified by URL, in IP network, the trust relationship in the path is established using IPSEC [10] or SSL/TLS [11]. However, in ICN, the trust is based on entities, not end-hosts. In ICN, there are so many of copies of the same content in different network locations, so the security between end-hosts cannot last so long.
The current IP naming structure uses the URL to name a resource in the Internet. But, it uses IP address to deal with the authority part.
the security scheme in the IP network is to protect the communication channel between clients and servers. However, in ICN, consumers could get the content from a cope of data source. ICN focus on authenticate the content, not the channel [12].
Chapter 3
Disaster Information-Centric Network System
3.1 Disaster Scenarios
we know that on March 11, 2011, An tremendous earthquake hit Japan, and caused so many damages, especially tsunamis and nuclear crisis. When this earthquake took place, it became difficult to communicate on the internet or telephone, many people cannot connect to their families and friends in where disaster happened. When we can not get the information correctly, it would impact that where we need to conduct a rescue measure and the supply for food or other activities.
This big earthquake showed that the current network can not meet the demand of request when enormous disaster happened.
Additionally, there are also some other kinds of disasters such as a terrorist attack caused by humans may need to be considered, like this human-induced disasters, the network may be damaged without any advance warning. In current network, it is difficult to provide the timely dissemination of information generated and requested by all the affected parties. But we believe that Information Centric Networks can be suitable to provided network infrastructure capability.
3.2 Previous Disaster System Works
3.2.1 Based on IP Network Disaster System
i
n the traditional disaster system, the main propose of system is to help people easier find refuge places, Particularly, in [13], the users, who register on this disaster system, can get GPS information, upload disaster information, like a picture or videos, or even just a text content.And the others retrieved this disaster information, they can find refuge place according to this system.
Figure 4:IP network disaster system
this system is easy to use, because the map they use is google API, refuge place is also very difficult to counted and defined. And this system is based on server, so when thousands of subscribe entry this
server, it may cause deny in network.
3.2.2 Disaster System Based on Information-centric Architecture
there are also some works on adopting of an information-centric architecture used in disaster system, in [14], they proposed a global information network(GIN) [fig5] aim at support agile disaster response.
This research based on 2010/2011 Queensland Floods case, in GIN, they consider each node as a unique instance of an “entity” or a “value.” GIN architecture, like most disaster system, also use a publish/subscribe method, it operates on a graph. It says that GIN supports the basic operations of add and map function. By publishing n-tuples, Application or services can join to the GIN graph.
Figure 5: global information network (modified and redraw from[14]) They try to conduct disaster management with GIN, the real-time monitoring system use the GIN API to search disaster information and then do the analysis, after that, it will send the result back to GIN. GIN also can get other pubic comments about disaster from networking, they aim at provide a quickly reacts system to new information. We can not do any evaluate about their proposal because they did not give the result of using GIN to do any simulation.
3.3 Information-Centric Network Disaster System
3.3.1 Naming Scheme
In ICN, content unit is called Named Data Object (NDO). Any kind of content can become NDO for example, a video, an image, or other information as long as it can represent a object. The same NDO can be identified by multiple names. An NDO is designed differently in each ICN approach. ICN categorizes the naming scheme into 2 different
environment
Autonomous entity
effects
ob ser ves
Consumes information
Produces
information Global information network
types. The commonly used schemes are flat and hierarchical naming.
The naming we used consists of a disaster information sign identifier (difo), GPS information. We use the GPS receive to get the GPS information when one to upload the disaster information to our disaster system, after we got GPS information, we split latitude and longitude from GPS information, and then translate these latitude and longitude to the name of content. For example, we got coordinate of a user who want to upload a disaster information to our system, like the latitude is 36.123456789, the longitude is 139.123456789, then we would translate it to the name of ICN, like /difo/36.1234/139.1234.
3.3.2 Function
This disaster system is based on ICN, the map we used is OSM (open street map). Because this system is use pure information-centric network, its include two function. One is upload, the other is retrieve, one can upload the disaster information to ICN local repository. it can only be done in simulation environment, we use ccnx [15] repository to store the disaster information which had been uploaded to ICN. we can retrieve the whole area or a smaller area which we just interested in.
Figure 6: ICN-based disaster system application
Chapter 4 Evaluation
In this section, we analyze the the performance of ICN-based disaster system using CCNx simulator, and compare it to the performance of TCP network.
4.1 Experimental tool: CCNx
Content-Centric Networking (CCN) is a new information distribution and network-aware application architecture also developed by PARC.
CCNx is PARC's implementation of content centric networking.
CCNx defined a network protocol around Interests which means request messages and Content Objects which means response messages to move named payloads. An Interest includes the Name, the desired payload, and two optional restrictions, on the other side, Content Object. The Content Object carries a matching Name and the specified payload. The CCNx network protocol suggest that Name should be hierarchical and is used to route towards an authoritative source. The CCNx Name looks like a URI absolute path and is a composition of name segments. Each name segment carries a label identifying the purpose of the name segment, and a value. Like the graph below.
/Parc/ccnx/presentations/slide1/v=1/c=0
Figure 7: name segment in CCNx
There are three conditions when a Content Object satisfies an Interest. firstly, the Content Object name exactly matches the Interest name by the longest matching prefix, and there is no requirement that the prefix be globally routable. Secondly, Validation Algorithm KeyId of the Content Object exactly equals the Interest KeyId Restriction, and finally, the computed Content Object Hash exactly equals the Interest Content Object Hash Restriction.
4.1.1 Experimental Applications
4.1.1.1 HttpProxy
HttpProxy [16] is a HTTP proxy that used to translate http get request to CCN interests. This special proxy need to use in ccnx environment using ccndstart command to start this software. http-ccn proxy include two parts, one is HttpProxy, the other is Netfetch.
Globally
routable name segments
Application Dependent
Name segments
Protocol Dependent name segments
HttpProxy plays a role in changing the received Http request to Interest package and transferring the data packet of CCN into Http response.
Netfetch plays a role in changing the interest of CCN into http request which is used to sent to server and transfer the Http response got from server into data packet, like fig [8]
Browser HttpProxy Netfetch Server
Figure 8: Packet transmission between proxies Http request
Http request
Http request
Http response Date packet
Http response
CCN
4.1.1.2 Wireshark
Firstly, we need to download a wireshark [17] source distribution, I choose the wireshark-1.6.2, then we need copy the contents of the CCN distribution’s ccn/apps/wireshark/ccn to plugins/ccn. And just follow the instructions to configure wireshark.
4.2 Simulation
Firstly, let us give the simply explanation about CCNx command used in our simulation.
Ccnd is the main CCN daemon which forwards interest packets. we can use ccndstart command to run the ccnx.
Ccnr is a repository which can provide persistent storage of CCNx content and respond to interests in the content it has available.
Ccngetfile is a command-line tool for retrieve CCNx content and store it in file.
Ccnputfile is command-line tool to send file as CCNx data and store it in ccn repository at the same time.
Ccnexplore: it is a GUI for browsing data stored in CCNx, it likes a simple file browser.
Simulation environment:
Edit Eclipse
Os Ubuntu 14.04
Programming Java
Simulation environment CCNx
map Open Street
Before we open the ICN disaster system application, the step for prepare the simulation in CCNx situation.
we use ccnd to start the ccnx.
1)! use ccnr to build a ccn repository.
2)! we use the ccn-http proxy to help us do the pure ccn
environment, so we start the ccnx, then prepare the proxy, in one terminal, We use cd:ccnx/apps/HttpProxy command to enter the HttpProxy home.
3)! then we open the proxy use ./HttpProxy – resolveHigh >proxy.log.
4)! then in anther terminal, we also use cd:ccnx/apps/HttpProxy command to enter the HttpProxy home.
in this way, we can set up the HTTP-CCN proxy. So we have finished the prepare for the simulation.
Firstly, one user uploads a disaster information to our
information-centric network. As soon as it clicks upload button, it gets the GPS, like latitude:35.705538, longitude:139.7112118., name this file as dinfo/35.7055/139.7112.in this way, we can use ccnputfile command to upload it to information-centric network repository.
When we uploaded a disaster information to our system, we can check whether it had been correctly uploaded to the ccn repository by use the ccn explore command.
Figure 9: CCN repository
If we want to retrieve a disaster information in our information-centric network, firstly, we choose the area we care about, then, it will get the max and mix of latitude and longitude, then it will
calculate how many interests it need to send, so in this way, we can retrieve disaster information in a chose area.
in this way, we can download the disaster information that had been stored in this area. While the disaster information had been retrieved out, it will be showed out in map.
4.3 Simulation Result
we test the delay in the condition of ccn environment, use wireshark to capture the packet, one of the result is like figure 10 below.
Figure 10: ccnx packets
then add the number of clients entry into the network, we find that download time in ccn almost keep the same.
Then do the implement use tcp network. Use wireshark to capture the packages again, we find the download time increase as the clients grow.
The figure[11] below is the result.
Figure 11: download time in download disaster information from information-centric network and TCP network
from the result, we can see that, when the number of clients increasing, the network delay gets longer in TCP network situation, but ccn have almost keep the same delay even the number of clients grow, this result show that information-centric network has better tolerant than TCP/IP network.
Chapter 5 Summary
We want to finish this thesis by concluding this work and give the future research directions for our work.
5.1 Conclusion
We know that current IP network structure has appeared many problems we need to solve, like mobility, security, content distribution, and so on. so there are many research communities have been suggesting the future Internet structures all over the world. There are already some Research programs have been set up aimed at the design of the future Internet, ICN is one of the future network structure. we designed and developed a naming scheme which is based on GPS information, then we proposed a disaster system in information-centric network architecture. Most of current disaster system are based on TCP/IP. our system based on information-centric network which has good security, mobility and cashing property, then we evaluate the performance of this system by analyzing the delay different in ICN and TCP network. The result show that information-centric network has a better tolerant than TCP network as the number of clients increasing.
5.2 Future work
In our study, we considered how to combine naming scheme with our disaster system, as one of our future network, we would like to extend the ICN-based disaster system considering the case of mobility and wireless.
Reference
[1] Internet Systems Consortium, Internet host count history, Retrieved May 16,2012
[2] Karnati Hemanth, Talluri Ravikiran, Maddipati Venkat Naveen, Thumati Ravi, Security Problems and Their Defenses in TCP/IP Protocol Suite December 2012.
[3] Lixia Zhang, Deborah Estrin, Jeffrey Burke, Van Jacobson, James D.
Thornton, and Diana K. Smetters, Beichuan Zhang, Gene Tsudik, kc claffy, Dmitri Krioukov, Dan Massey; Christos Papadopoulos; Tarek Abdelzaher; Lan Wang; Patrick Crowley; Edmund Yeh Named Data Networking (NDN) Project October 2010.
[4] http://www.4ward-project.eu/
[5] Tomonori Aoyama, “A New Generation Network: Beyond the Internet and NGN” 2009.
[6] Van Jacobson et al., “Networking Named Content”, ACM CoNEXT, 2009.
[7] A. Ghodsi et al., “Naming in Content-Oriented Architectures,” Proc.
ACM SIGCOMM Wksp. Information-Centric Networking, Toronto, Canada, Aug. 2011.
[8] Walter Wong, Pekka Nikander, Secure Naming in Information-centric Networks, November, 2010
[9] V. Jacobson, D. K. Smetters, J. D. Thornton, M. F. Plass, N. H. Briggs, and R. Braynard, “Networking named content,” in CoNEXT, J. Liebeherr, G. Ventre, E. W. Biersack, and S. Keshav, Eds. ACM, 2009, pp. 1–12.
[10] S. Kent, K. Seo, “RFC 4301: Security Architecture for the Internet Protocol,” December 2005.
[11] T. Dierks, E. Rescorla, “RFC 5246: The Transport Layer Security (TLS) Protocol - Version 1.2,” August 2008.
[12] Satyajayant Misra, Reza Tourani, Nahid Ebrahimi Majd. Secure Content Delivery in Information-Centric Networks: Design, Implementation, and Analyses. 2013
[13] Na Yu, Jairo Eduardo Lopez, Aldo Maetinez, Chin Kokui, and ,Takuro Sato Study on information sharing system in widespread disaster 2013
[14] Yan Shvartzshnaider, Maximilian Ott, Design For Change:
Information-Centric Architecture to Support Agile Disaster Response, June 2013.
[15] “CCNx,” PARC, 2013. [Online]. Available: http://www.ccnx.org/
[16] Dariusz Bursztynowski, Mateusz Dzida, HTTP/CCN Gateway and Cooperative Caching Demonstrator, CCNxCon2012
[17] https://www.wireshark.org