LISP-Based Integrated Control Plane Framework for Service Function Chaining in Distributed Edge Clouds

Abstract

Service function chaining, which provides a sequential set of multiple services in an end-toend communication path, is a key technology for providing better service quality to users and efficient management of the network. Recently, as the services traditionally deployed in the data center have become more proximate to the user using a distributed cloud environment, the management of the service chain has become more complex for connecting services between clouds at a distance. In particular, when a user moves and resumes end-to-end communication at a new location, these complexities may lead to an increase in service downtime, which results in network performance degradation. In this paper, we propose an integrated control system to quickly recover the path to the service chain along with mobility management. The proposed system is based on the locator/identifier separation protocol to provide cost-effective mobility management by integrating the location information of users and services into the service chain mapping system. Based on the analysis of the operating cost and handover delay, it was determined that the proposed system can quickly restore a service chain path between distributed clouds with less signaling exchange and minimum delay when compared to previous approaches.

SRv6-Based Edge Service Continuity in 5G Mobile Networks

“…Another network-layer solution is provided by the work in [28], where the Locator/Identifier Separation Protocol (LISP) is used in conjunction with SRv6. The approach allows the managing of the path migration for the Service Function Chains (SFCs) in a distributed edge environment, with the aim of facilitating user mobility.…”

LISP-Based Control Plane for Service Connectivity in Multi-Cluster Cloud Systems

“…The traditional method to solve this problem is to adapt IP mobility management to service mobility management, which maintains service IP addresses even when the service location is changed [2][3][4][5], however the traffic path cannot be optimized by anchoring the address at the edge cloud, where the service is initially instantiated. To solve this problem, several methods have been researched to separate the IP context into the ID and location [6][7][8][9][10]. In particular, in our previous studies [9][10] the location/ID separation protocol (LISP) [11] was used to assign a unique service regardless of its location.…”

“…To solve this problem, several methods have been researched to separate the IP context into the ID and location [6][7][8][9][10]. In particular, in our previous studies [9][10] the location/ID separation protocol (LISP) [11] was used to assign a unique service regardless of its location. With the enhanced mapping system of the service ID and its locator, our work verified that the nearest service is always accessed while minimizing the service downtime even when the mobile user is rapidly roaming across multiple edge clouds.…”