Abstract

In disaster management services, the dynamic binding between roles and individuals for creating response teams across multiple organizations to act during a disaster recovery time period is an important task. Existing studies have shown that IP-based or traditional telephony solutions are not well-suited to deal with such group communication. Research has also shown the advantages of leveraging information centric networking (ICN) in providing essential communication in disaster management services. However, present studies use a centralized networking architecture for disaster management, in which disaster information is gathered and processed at a centralized management center before incident responses are made and warning messages are sent out. The centralized design can be inefficient in terms of scalability and communication. The reason is that when the network is very large (i.e., country level), the management for disaster services becomes very complicated, with a large number of organizations and offices. Disaster data are required to be transmitted over a long path before reaching the central management center. As a result, the transmission overhead and delay are high. Especially when the network is fragmented and network connectivity from a disaster-affected region to the central management center is disconnected, the service may be corrupted. In this paper, we designed and implemented a distributed edge cloud architecture based on ICN and network function virtualization (NFV) to address the above issues. In the proposed architecture, disaster management functions with predefined disaster templates were implemented at edge clouds closed to local regions to reduce the communication overhead and increase the service availability. The real implementation and performance evaluation showed that the proposed architecture achieves a significant improvement in terms of average bandwidth utilization, disaster notification delivery latency, routing convergence time, and successful request ratio compared to the existing approaches.

Highlights

  • In recent years, the outstanding growth of the Internet and the introduction of many new applications have given rise to concerns about networking architecture to support scalable content distribution, security, mobility, and so on

  • This paper presented a distributed network function virtualization (NFV)-based architecture for disaster management services to address the high overhead, long delay, and low service availability limitations of the current information-centric networking (ICN)-based centralized architecture

  • The distributed architecture was implemented with testbeds based on ICN

Read more

Summary

Introduction

The outstanding growth of the Internet and the introduction of many new applications have given rise to concerns about networking architecture to support scalable content distribution, security, mobility, and so on. With the introduction of disaster templates, CNS is implemented as a content-oriented notification service using a centralized architecture for disaster management. Disaster management functions with predefined templates were implemented at edge clouds closed to local regions to reduce the communication overhead and increase service availability in cases of fragmented network scenarios during disasters. Name-based binding and forwarding advantages of ICN as well as predefined templates are used to enable disaster information to be forwarded to correct corresponding receivers without requiring connectivity to the central management office. The real implementation and performance evaluation showed that the proposed architecture achieves a significant improvement in terms of average bandwidth utilization, disaster notification delivery latency, routing convergence time, and successful request ratio compared to the existing approaches.

Disaster Management Services
Use Cases
Requirements of the System
System Architecture
Naming Schema
Naming Schema for Local Communication
Data Structure of Central Disaster Management Center
Naming Schema for Intercloud Communication
Intercloud Protocols
Implementation and Configurations
Bandwidth Utilization
Disaster Notification Delivery Latency
Average Routing Convergence Time for Disaster Name Template Setup
The Ratio of Successful Support Requests under Fragmented Network Scenarios
Findings
Conclusions

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.