Unified VIM Orchestrating Mixed VM and Container VNFs

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Conventional systems fail to adequately ensure that microservices are created in appropriate resource domains and provide appropriate connectivity between virtual and physical network domains, leading to inadequate SLA compliance and separate orchestration of VM-based and container-based workloads, which prevents the deployment of mixed VNFs with subparts of both types.

Innovation Solution

A system where a Virtual Infrastructure Manager (VIM) identifies and manages both VM and container-based subparts of a VNF, ensuring SLA compliance by selectively generating containers and VMs based on descriptors, and orchestrates their placement, scaling, and maintenance across an integrated network.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If separate orchestration systems are used for VM-based and container-based workloads, then each system can be optimized for its specific workload type, but the deployment of mixed VNFs with both VM and container subparts is prevented and management complexity increases

Engineering Contradiction:

Improveability to deploy mixed VNFsVSAvoidorchestration system complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges separate orchestration systems for VM-based and container-based workloads into a unified orchestration platform. This single system can manage both types of workloads simultaneously, enabling the deployment of mixed VNFs that contain both VM and container subparts while reducing overall system complexity.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The orchestration system is designed with universal capabilities to handle multiple workload types (both VM and container) through a single interface and management plane. This multi-functional approach allows the system to adapt to different workload requirements without requiring separate specialized systems.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Productivity

If microservices are deployed with high mobility across different clusters, then resource utilization improves, but ensuring appropriate resource domain placement and maintaining SLA compliance becomes difficult

Engineering Contradiction:

Improveresource utilizationVSAvoidSLA compliance

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The orchestration system implements feedback mechanisms that continuously monitor microservice deployment status, resource domain appropriateness, and SLA compliance metrics. When a microservice is relocated for resource optimization, the system receives feedback on whether the new location maintains SLA requirements and adjusts placement decisions accordingly.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The system dynamically evaluates resource domain suitability based on current network conditions, workload characteristics, and SLA requirements. This dynamic approach allows microservices to be mobility-optimized while ensuring they are placed in appropriate resource domains that can meet their specific performance and compliance requirements.

Inventive Principle:

Principle #15Dynamics

3Adaptability or versatility

If external network functions are processed and deployed separately from the originating microservice, then functional flexibility increases, but maintaining sustained communication and ensuring connectivity between virtual and physical domains becomes challenging

Engineering Contradiction:

Improvefunctional flexibilityVSAvoidconnectivity management

Core Design Contradiction:

Adaptability or versatilityVSEase of operation

Solution Approach 1:

The unified orchestration system acts as an intermediary that manages communication between externally deployed network functions and their originating microservices. It maintains the necessary connectivity information and coordinates interactions across virtual and physical domains, simplifying the management of distributed function communications.

Inventive Principle:

Principle #24Intermediary (Mediator)

4Ease of manufacture

If conventional systems orchestrate VM and container workloads separately, then each workload type can be managed with dedicated optimization, but SLA compliance between mixed VNF components cannot be ensured

Engineering Contradiction:

Improveworkload management optimizationVSAvoidSLA compliance

Core Design Contradiction:

Ease of manufactureVSReliability

Solution Approach 1:

The patent combines separate VM and container orchestration capabilities into a unified system that manages mixed VNF workloads together. This allows the system to ensure SLA compliance across all VNF components (both VM and container subparts) while maintaining the ability to apply workload-type-specific optimizations through a single coordinated management plane.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11588675B2Systems and methods for selectively implementing services on virtual machines and containers

Publication Date: 2023.02.21 VMWARE INC

AI summary

Examples of the present disclosure can include a method. The method may include (1) identifying, by a virtual infrastructure manager (“VIM”), a virtual network function (“VNF”) descriptor from information obtained from the integrated network, (2) selectively generating at least one container on the physical network based on the VNF descriptor, (3) determining, by the VIM, an integrated network requirement based on state information associated with the integrated network, (4) providing, by the VIM, to a container management platform, the integrated network requirement, and (5) causing a VNF to be generated in the container to fulfill the integrated network requirement. Corresponding systems, non-transitory computer-readable media, and methods are also disclosed.