{'fraction_non_alphanumeric': 0.013705851344227728, 'fraction_numerical': 0.0, 'mean_word_length': 5.369127516778524, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
LISP-Based Control Plane for Service Connectivity in Multi-Cluster Cloud Systems

In mobile networks, the edge cloud environment has emerged to provide various services to users. When the mobile user moves to another location while connecting the edge cloud service, to maintain an optimal service path, it is necessary to migrate the service to a new edge cloud close to the location where the user is newly connected. Several methods have been proposed to integrate edge cloud service migration technology with existing mobility management protocols in mobile networks, and a location/ID separation protocol (LISP)-based service optimal path management method between edge clouds was recently proposed. However, for real implementation of edge cloud with existing platform specified to containerized infrastructure, where the address of service is allocated randomly and locally, it is hard to discover appropriate service from the external client as well as maintain service connectivity when service location is changed. To solve that, this paper proposed the LISP-based service ID management system which provides uniform access for equivalent services running on different edge clouds. To apply the proposed ID management system on real distributed edge cloud systems, the mobility management and edge cloud networking systems were integrated as shown in the testbed implementation. This shows the possibility of combining the isolated mobility management for mobile users and internal identification of edge services using LISP for reducing the interruption and delay of edge service for mobile users. As a result of the experiments conducted on a real testbed, our proposed system was verified to enable a change in the routing path while maintaining a single service ID between different edge clouds, and the delay time for path reconfiguration is reduced compared to the existing method.