VNF Configuration Generation for Service Availability

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Designing highly available Virtual Network Functions (VNFs) in Network Function Virtualization (NFV) is challenging due to the need for balancing service availability with resource optimization, especially in virtual environments where collocation of entities can lead to interference and increased resource requirements.

Innovation Solution

The method generates Availability Management Framework (AMF) configurations for VNFs, optimizing resource utilization and service availability by determining the number of AMF entities and VNFC instances, and grouping them into fault isolation units to minimize interference, using extended Configuration Requirements and Entity Types Files that account for virtual infrastructure characteristics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If VNFs are deployed with high service availability requirements, then reliability is improved, but resource usage increases due to redundancy and fault isolation requirements

Engineering Contradiction:

Improveservice availabilityVSAvoidresource usage

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The system segments VNFs into multiple VNFC (Virtual Network Function Component) instances distributed across different VMs (Virtual Machines). This segmentation allows fault isolation where a failure in one VNFC does not propagate to others, improving service availability while optimizing resource utilization by allowing selective replication only where needed for fault tolerance.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The system dynamically adjusts configuration parameters such as the number of VNFC instances, replication factors, and placement constraints based on the required service availability levels. By changing these parameters adaptively, the system achieves high reliability when needed while minimizing resource consumption when lower availability suffices, resolving the contradiction between reliability and resource usage.

Inventive Principle:

Principle #35Parameter changes

2Reliability

If multiple VNFC instances are deployed for high availability, then service continuity is improved, but device complexity increases due to coordination and management overhead

Engineering Contradiction:

Improveservice continuityVSAvoidconfiguration management complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system employs a universal configuration management framework that handles multiple VNF types and availability requirements through a single automated orchestration mechanism. This multi-functional approach simplifies complexity by providing standardized procedures for instance deployment, coordination, and management across diverse VNF scenarios, rather than requiring separate complex management systems for each case.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system implements self-service capabilities where VNFC instances automatically coordinate their own deployment, scaling, and failover operations through embedded orchestration logic. This self-organization reduces the management overhead and coordination complexity that would otherwise require extensive external control mechanisms, maintaining service continuity while simplifying the overall system complexity.

Inventive Principle:

Principle #25Self-service

3Reliability

If VNFC instances are distributed across multiple VMs for fault isolation, then service resilience is improved, but infrastructure requirements increase

Engineering Contradiction:

Improveservice resilienceVSAvoidinfrastructure configuration

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system distributes VNFC instances across multiple dimensions including different VMs, physical hosts, and geographic locations. By adding these dimensional layers of distribution, the system achieves enhanced fault isolation and service resilience without linearly increasing infrastructure complexity, as the same infrastructure resources serve multiple distribution dimensions simultaneously.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

Solution Approach 2:

The system merges multiple infrastructure management functions into unified configuration templates and orchestration policies. By combining host selection, VM placement, and fault isolation strategies into integrated configurations, the system reduces the apparent infrastructure complexity while maintaining the distributed resilient architecture needed for high service availability.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11349708B2Configuration generation for virtual network functions (VNFs) with requested service availability

Publication Date: 2022.05.31 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)

AI summary

A Virtual Network Function (VNF) is provided for deployment in a Network Function Virtualization Infrastructure (NFVI). First, an input is obtained that includes a description of available software components, configuration requirements specifying service types to be provided by the VNF, and infrastructure information specifying resources provided by the NFVI. The infrastructure information includes characteristics of virtual machines (VMs). For each service type, a VNF component (VNFC) configuration is generated. The generated VNFC configuration optimizes usage of the resources and satisfies requested service availability. A VNF configuration is formed that includes a collection of VNFC configurations created for the service types. The VNF configuration is delivered to a Network Function Virtualization (NFV) system for the deployment of VNFC instances on the VMs thereby providing the VNF.