Cloud Component Migration via Mobility Enablement Layer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing cloud component migration solutions incur overhead by routing traffic from prior sessions through an anchor node, which can cause performance delays and inefficient resource usage.
Innovation Solution
Decoupling the networking control plane from the packet forwarding data plane using a mobility enablement layer (MEL) allows for the creation of forwarding rules that enable traffic to be directed within the proper address domain, eliminating the need for traffic to pass through an anchor node during migration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If traffic is tunneled through an anchor node during cloud component migration, then session continuity is maintained, but performance delays increase and resource usage becomes inefficient
Solution Approach 1:
The patent introduces a mobility enablement layer (MEL) as an intermediary between the control plane and data plane. This layer enables direct traffic forwarding between cloud components during migration without requiring tunneling through anchor nodes, thereby eliminating performance delays while maintaining session continuity through intelligent forwarding rule management.
Solution Approach 2:
The patent segments the networking function into control plane and data plane, with the mobility enablement layer acting as a bridge. This segmentation allows the control plane to manage forwarding rules while the data plane handles actual traffic forwarding, enabling seamless migration without anchor node tunneling overhead.
2Adaptability or versatility
If a new IP address is assigned during cloud component migration, then the cloud component can operate in the new address domain, but traffic from prior sessions must be tunneled through an anchor
Solution Approach 1:
The patent performs preliminary actions by pre-establishing forwarding rules in the mobility enablement layer before migration occurs. When a cloud component receives a new IP address, the forwarding rules are already in place to handle traffic directly, eliminating the need for anchor node tunneling and reducing migration complexity.
Solution Approach 2:
The patent implements dynamic forwarding rules that automatically adapt to migration events. The mobility enablement layer dynamically updates forwarding entries based on real-time migration status, allowing the system to seamlessly handle IP address changes without requiring static anchor node configurations.
3Reliability
If an anchor node is used for traffic forwarding during migration, then session continuity is maintained, but resource utilization becomes inefficient
Solution Approach 1:
The patent extracts the mobility management function from traditional anchor nodes and places it in the mobility enablement layer. This extraction eliminates the need for anchor nodes to handle migration traffic, reducing resource consumption while maintaining session continuity through direct forwarding paths.
Solution Approach 2:
The mobility enablement layer enables cloud components to self-manage their migration by implementing forwarding rules that automatically route traffic during migration events. This self-service mechanism eliminates the need for anchor node intervention, optimizing resource utilization while ensuring session continuity.
Data Source
AI summary
Various embodiments provide a method and apparatus for providing migration of cloud components across address domains without the overhead of sending traffic from prior sessions through an anchor. In particular, the networking control plane is decoupled from the packet forwarding data plane using a mobility enablement layer (MEL) that allows creating rules for forwarding elements (FEs) to forward traffic directed to an address within the proper address domain.