NFV Lifecycle Management via Configuration Mediator

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The management of Virtual Network Functions (VNFs) in legacy 3GPP systems is challenging due to the complexity of network devices and the inability of proprietary physical implementations to adapt to different network conditions, leading to difficulties in activation, deactivation, and modification, which can negatively impact legacy systems.

Innovation Solution

The implementation of a Network Function Virtualization (NFV) architecture that uses a virtualized environment to provide network functions on Commercial Off-The-Shelf (COTS) servers, allowing for dynamic network optimization and lifecycle management of VNFs through a unified management system, including the creation, modification, and termination of Managed Object Instances (MOIs) to support flexible network resource allocation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If legacy 3GPP management systems are used to manage VNFs, then system compatibility is maintained, but management flexibility and adaptability deteriorate

Engineering Contradiction:

Improvemanagement flexibilityVSAvoidsystem complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent introduces a Configuration Management Function (CMF) as an intermediary layer between legacy 3GPP management systems and virtualized network functions. The CMF translates and adapts management operations, enabling flexible VNF management while maintaining compatibility with existing legacy systems. This mediator handles the complexity of NFV lifecycle management without requiring changes to the underlying legacy infrastructure.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The management system is segmented into distinct functional components: the legacy 3GPP management system, the new Configuration Management Function, and the Virtualized Network Functions. This segmentation allows each component to operate independently with well-defined interfaces, improving adaptability while isolating complexity to specific modules rather than the entire system.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If proprietary physical implementations are used, then hardware stability is maintained, but adaptability to different network conditions deteriorates

Engineering Contradiction:

Improvenetwork condition adaptabilityVSAvoidhardware modification difficulty

Core Design Contradiction:

Adaptability or versatilityVSEase of manufacture

Solution Approach 1:

The patent virtualizes network functions by creating software copies (VNFs) that can be deployed on standard hardware infrastructure. Instead of modifying proprietary physical hardware, the system uses virtualized instances that can be rapidly instantiated, configured, and adapted to different network conditions. These virtual copies provide the same functional capabilities as physical devices but with significantly improved flexibility.

Inventive Principle:

Principle #26Copying

Solution Approach 2:

The patent replaces the mechanical/physical hardware modification approach with a software-based virtualization system. Rather than physically reconfiguring or replacing proprietary hardware components, the system uses software-defined network functions that can be dynamically adjusted through configuration management, eliminating the need for physical hardware modifications.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If NFV architecture is implemented, then management flexibility is improved, but impact on legacy systems increases

Engineering Contradiction:

Improvenetwork management efficiencyVSAvoidlegacy system impact

Core Design Contradiction:

ProductivityVSObject-affected harmful factors

Solution Approach 1:

The Configuration Management Function serves as a protective intermediary that shields legacy systems from the complexities of NFV management. It handles all interactions between the virtualized environment and legacy components, ensuring that legacy systems experience minimal disruption while still benefiting from improved management capabilities through standardized interfaces and gradual migration paths.

Inventive Principle:

Principle #24Intermediary (Mediator)

Data Source

PatentEP3437254B1Device and method for NFV life cycle management using configuration management functions

Publication Date: 2024.10.16 INTEL CORP

Figure 1
Figure 2
Figure 3

AI summary

Devices and methods of providing NFV life cycle management are generally described. The NFV life cycle management of creation and deletion of one or more MOIs of a VNF instance is provided through the use of CM functions having an attribute that indicates a VNF instance and is initiated by an EM or a NM. The EM transmits to a VNFM a request to instantiate or terminate the VNF instance and receives an acknowledgement in response prior to creation or deletion of the MOIs. The EM also configures application specific parameters for creation or deletion of the MOIs after creation and before deletion of the MOIs.