MD VNF Migration Across Software Instances for HA Resource Sharing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing high availability (HA) systems in cable networks rely on redundancy to ensure no single point of failure, but this approach inefficiently allocates computational resources and can lead to wasted resources due to standby instances being fully synchronized and allocated the same resources as active instances, even when not actively working.
Innovation Solution
Implement dynamic, seamless management of Virtual Network Functions (VNFs) by allowing individual MD VNFs to be migrated between software instances without disrupting operation, enabling active and standby VNFs to share resources dynamically and optimizing resource allocation based on demand.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If standby software instances are fully synchronized and allocated the same resources as active instances to ensure high availability, then system reliability is improved, but computational resource utilization deteriorates
Solution Approach 1:
The patent implements dynamic resource allocation where standby software instances can request additional computational resources from the resource pool when needed, rather than being statically allocated fixed resources. This allows the system to adapt resource distribution based on actual demand while maintaining reliability through the standby instances' ability to assume active roles when necessary.
Solution Approach 2:
The system changes the resource allocation parameter from fixed equal distribution to variable distribution based on demand. Standby instances can dynamically adjust their resource allocation status, requesting more resources when needed and releasing them when not required, thereby optimizing the balance between reliability and resource utilization.
2Reliability
If standby software instances are allocated the same computational resources as active instances, then high availability is ensured, but operational costs worsen
Solution Approach 1:
The patent enables dynamic resource sharing where standby instances can access the resource pool on-demand rather than being permanently allocated fixed resources. This dynamic approach allows the system to maintain high availability capability while reducing operational costs by allocating resources only when actually needed by standby instances.
Solution Approach 2:
Standby software instances can self-manage their resource requirements by requesting additional computational resources from the resource pool when needed, rather than being passively allocated fixed resources. This self-service mechanism optimizes cost efficiency while ensuring standby instances remain capable of assuming active roles when necessary.
3Productivity
If individual MD VNFs are migrated between software instances dynamically, then resource allocation efficiency is improved, but system complexity worsens
Solution Approach 1:
The patent segments the VNF management function by introducing a separate VNF manager component that independently handles migration decisions and execution. This segmentation allows the migration mechanism to be encapsulated in a dedicated manager, reducing the complexity burden on individual software instances while enabling efficient dynamic resource allocation through coordinated VNF movements.
Data Source
AI summary
Dynamic, seamless management of virtual network function (VNF) in a highly available (HA) environment. An instance management program instantiates software instances in which a plurality of VNFs reside. A type of VNF is a MAC Domain (MD) VNF, which is a virtual network function that implements the DOCSIS CMTS MAC layer for a particular MAC domain. Upon determining that a particular VNF executing within a first software instance managed by an instance management program should be moved to a second software instance, the particular VNF is moved from the first software instance to the second software instance without ceasing operation of any other VNF also executing in the first software instance. A software instance may have both active and standby VNFs comprised therein. Failover operations of a particular VNF may be performed during runtime without ceasing operation of any of software instance or VNF not associated with the failed VNF.