# Named Data Networking Based Disaster Response Support System over Edge Computing Infrastructure +
###### Abstract
It allows NDN consumers to fetch data from anywhere in the network storing the copy of the data that has the same name as the interest packet (the NDN request packet). This location-independent feature enables group role-based message delivery in NDN. People in the same messaging group can fetch messages by using the group's unique name prefix. Moreover, NDN location-independent feature enables native mobility support. When a user moves to a new location, data can be requested using its name instead of having to know the new location address like in an IP-based network. Although several studies [3; 4; 5; 6; 7; 8; 9; 10; 11; 12] have leveraged NDN in dealing with disaster management issues, real implementation of an NDN-based architecture over existing infrastructure during a disaster is lacking. Most works' results are limited to simulation analysis. Moreover, when deploying an NDN network in a disaster scenario, apart from role-based communication, additional challenges should be considered. First, infrastructure is normally damaged during a disaster, quick replacement time for network nodes is required. Second, despite the NDN mobility built-in support feature, only the consumer mobility issue is natively supported. Due to emergency responder high mobility, producer mobility problem is also required to be addressed. NDN needs to be enhanced so that network can automatically build routing paths to the producer's new location after moving. Another challenge is the intermittent network caused by disaster hazards. To effectively manage tasks during the disaster response phase, reported information from responders to the management center and commands from commanders to responders should ensure to be delivered without any loss. Missing information can seriously affect searching and rescue efforts. In this paper, we designed and implemented an NDN-based disaster response support system over Edge Computing infrastructure with KubeEdge as the chosen implementation edge platform to solve the above issues. In this proposed architecture, we design a deployment strategy to establish an NDN network at both one region level and multiple regions level. NDN network functions are deployed as containers from cloud to edge equipment to provide emergency communication. Each cluster contains several edge nodes to provide an NDN network for one region. Master nodes from each cluster are tunneled to connect the NDN network between two regions. In case of damaged edge nodes caused by the disaster, NDN containerized function will be deployed from the cloud to replaced nodes. With Named-data link-state protocol (NLSR) [13] enabled, the NDN network can converge quickly after replacement. We also enhance NDN with a protocol between user devices and border edge nodes to solve the mobility challenge. Finally, we utilize KubeEdge to provide reliable information sharing between cloud and edge in discontinuous network conditions. The architecture is implemented using KubeEdge on multiple servers and NUCs. For end-users, we design an exclusive NDN disaster application that provides message delivery and information exchange with the management center function. Our proof-of-concept system performance shows that the architecture obtains the following achievements:  
* A deployment architecture to provide emergency communication over NDN network and NDN device management for disaster information exchange
* Faster network convergence time after replacement in case of damaged network node caused by disaster compared to IP-based network
* Faster mobility handover duration compared to Mobile IP [14] and rendezvous mobility solution for NDN [15]* Low information exchange transmission overhead between cloud and responder devices
* Ensuring loss-free information exchange between responders and management center at cloud compared to normal NDN method without using edge platform. Compared with the preliminary version [16], this paper provides more details about the architecture design, presents implementation results and analysis.