Live Stateful Container Migration in Information-Centric Networks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In information-centric networks, migrating a stateful application while maintaining continuous service and low latency is challenging due to high convergence times and difficulties in seamless transitions between nodes, especially for mobile edge computing devices.
Innovation Solution
The system migrates a live application container between nodes in an information-centric network using interest packets and data packets, where the application is treated as a transmittable data object, allowing it to continue serving requests during migration by using a shared forwarding plane and separate channels for migration and request paths, ensuring seamless service without packet loss.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Speed
If a stateful application is migrated between nodes in an information-centric network, then the application can maintain low latency and responsiveness for mobile users, but it becomes difficult to maintain persistent and uninterrupted service during the migration procedure
Solution Approach 1:
The patent segments the migration process into distinct phases: the origin node receives a migration request and begins transferring the application container image and state data to the destination node, while simultaneously maintaining the application container at the origin node to continue serving requests. This segmentation allows the migration to proceed without interrupting service, as the application exists in both locations during the transition.
Solution Approach 2:
The patent introduces an intermediary mechanism where the origin node acts as a temporary host for the application container during migration. The origin node receives the migration request, maintains the running container, and coordinates the transfer of container image and state data to the destination node. This intermediary role ensures seamless service continuity while enabling the migration to proceed.
2Adaptability or versatility
If the application container is transferred to a destination node, then the application can be migrated to a new location, but the convergence time increases and service disruption occurs
Solution Approach 1:
The patent applies preliminary action by receiving the migration request and initiating the transfer of the application container image and state data to the destination node before the application needs to be relocated. The origin node prepares the migration by maintaining the container and coordinating the data transfer in advance, allowing the destination node to be ready to take over service immediately without convergence delays.
Solution Approach 2:
The patent ensures continuity of useful action by maintaining the application container at the origin node throughout the migration process. The container continues to serve requests while the image and state data are transferred to the destination node. This continuous operation eliminates service disruption and reduces convergence time, as the application never stops running during the migration.
3Reliability
If the application state is synchronized during migration, then seamless service can be maintained, but network overhead increases
Solution Approach 1:
The patent applies partial action by transferring only the necessary components of the application container during migration: the container image and the current state data. Rather than transferring the entire application environment or all possible state information, the system transfers only what is needed to maintain seamless service at the destination node, reducing network overhead while ensuring service continuity.
Data Source
Figure 1A~1B
Figure 2
Figure 3
AI summary
Systems, methods, and computer-readable media for migrating an application container between nodes in a network are disclosed. An interest for an application container may be received by an origin node and, in response, the origin node may transfer a copy of the application container over the network and to a destination node. The origin node can then shut down the application container and transmit any remaining container state and received requests to the destination node. The destination node may then update a routing plane for the network to provide delivery of service requests to the migrated application.