NFV-MANO VNF Deployment via Interface Dependency Validation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The existing NFV-MANO architecture limits the deployment of virtual network functions (VNFs) by not considering network interface dependencies and compatibilities, making it impractical to automate complex network service chains and on-demand topological changes in networks like 5G, leading to wasted resources.

Innovation Solution

The NFV-MANO system automatically packages and deploys VNFs based on network interface dependencies and compatibilities by generating testing configurations, validating proposed VNFs, deriving dependency constraints, and selecting compatible VNFs to create a new deployment layout that ensures proper interconnectivity with existing VNFs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If the NFV-MANO architecture does not consider network interface dependencies and compatibilities, then the deployment process is simpler, but the ability to automate complex network service chains and topological changes is limited, leading to wasted resources

Engineering Contradiction:

Improveautomation of VNF deploymentVSAvoiddeployment process complexity

Core Design Contradiction:

Extent of automationVSDevice complexity

Solution Approach 1:

The system performs preliminary actions by automatically generating testing configurations before VNF deployment based on network interface dependencies. The NFV-MANO creates test cases that validate interface compatibility and connectivity requirements in advance, enabling automated deployment while managing complexity through pre-computed validation rules.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent introduces an intermediary validation layer that mediates between VNF deployment requests and the actual network topology. The NFV-MANO uses dependency constraints and compatibility checks as intermediaries to ensure proper integration, automatically selecting compatible VNFs and generating appropriate testing configurations without manual intervention.

Inventive Principle:

Principle #24Intermediary (Mediator)

2Productivity

If manual methods are used to deploy VNFs, then resource consumption is lower for validation processes, but deployment time and labor requirements increase significantly

Engineering Contradiction:

Improvedeployment speedVSAvoidvalidation and testing time

Core Design Contradiction:

ProductivityVSLoss of time

Solution Approach 1:

The system enables self-service deployment where the NFV-MANO automatically generates testing configurations, validates VNF compatibility, and executes deployment based on network interface dependencies. The validation process is self-contained, using automated tools that consume minimal resources while maintaining high deployment speed and thorough validation.

Inventive Principle:

Principle #25Self-service

Solution Approach 2:

The patent changes the validation parameters from manual inspection to automated parameter-based validation. The NFV-MANO uses dependency constraints, compatibility attributes, and generated test configurations to automatically validate VNF deployments, significantly reducing validation time while maintaining comprehensive checking through parameter-driven automation.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If VNFs are deployed without considering interface dependencies, then deployment is faster, but interconnection issues occur and resource utilization efficiency decreases

Engineering Contradiction:

Improveinterconnectivity reliabilityVSAvoiddeployment configuration complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system performs preliminary validation by generating testing configurations that check interface dependencies before deployment. The NFV-MANO pre-validates compatibility between VNFs and existing network elements, ensuring reliable interconnectivity is established automatically without complex manual configuration.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The patent implements feedback mechanisms where the NFV-MANO continuously monitors and validates interface compatibility during deployment. Testing configurations provide feedback on whether VNFs properly connect to existing network elements, allowing automated adjustment or rejection of incompatible deployments to ensure reliability.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS11665081B2Systems and methods for automatically packaging and deploying virtual network functions based on network interface dependencies and compatibilities

Publication Date: 2023.05.30 VERIZON PATENT & LICENSING INC

AI summary

A device may receive information identifying existing virtual network functions (VNFs) associated with an existing virtual radio access network (VRAN), and may receive information identifying proposed VNFs to deploy with the existing VRAN, wherein the information identifying the proposed VNFs includes VNF descriptors indicating interface dependencies associated with the proposed VNFs. The device may generate testing configurations, for testing the proposed VNFs, based on the interface dependencies, and may determine that a set of the proposed VNFs are validated based on testing the proposed VNFs with the testing configurations. The device may derive dependency constraints for the set of the proposed VNFs based on the information identifying the existing VNFs, and may select a new VNF that satisfies the dependency constraints, based on the set of the proposed VNFs. The device may cause the new VNF to be deployed with the existing VRAN.