NFVO Resource Recognition via Reference Definition Matching

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Network Function Virtualization Orchestrators (NFVO) face challenges in recognizing and managing a wide variety of Virtualized Infrastructure Manager (VIM) resources, leading to inefficiencies in resource deployment and dependency management, as they can only recognize a subset of resource types and require manual support for new resource types, resulting in delayed query capabilities and potential errors during deletion processes.

Innovation Solution

Implementing a method to dynamically recognize and store unrecognized VIM resources as recognized resources by matching them against reference definitions, allowing for the automatic handling of new resource types and their dependencies through a generic API, thereby eliminating the need for manual support and enhancing the NFVO's ability to manage dependencies and prevent resource deletion errors.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If the NFVO only recognizes a subset of VIM resource types, then the system complexity is reduced and management is simplified, but the ability to manage diverse resource types is limited and manual support is required for new resources

Engineering Contradiction:
ImproveNFVO resource recognition complexityVSAvoidNFVO resource type coverage
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal resource recognition mechanism where the NFVO uses a reference definition framework that can accommodate multiple VIM resource types through a common API interface. The system can recognize and manage both traditional virtualized resources and cloud-native resources (Kubernetes, OpenStack, Azure) through the same generic resource representation, eliminating the need for type-specific handling logic while maintaining broad resource type coverage

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The system dynamically adapts to new resource types by changing its recognition parameters through configurable reference definitions. Instead of hardcoding support for specific resource types, the NFVO uses parameterized schemas that can be adjusted to recognize new resource types by matching their attributes against configurable criteria, allowing the system to evolve without structural changes

Inventive Principle:
Principle #35Parameter changes

2Reliability

If manual support is added for each new resource type, then the NFVO can recognize and manage that resource type, but the development and testing time increases significantly

Engineering Contradiction:
Improveresource recognition accuracyVSAvoiddevelopment and testing time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements self-service capability where the NFVO automatically recognizes new resource types by matching them against configurable reference definitions without requiring manual intervention. The generic resource synchronization process autonomously identifies unrecognized resources, compares them against reference schemas, and creates appropriate resource representations, eliminating the need for manual development and testing cycles for each new resource type

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent pre-configures reference definitions and schemas that define the structure and attributes of various resource types in advance. These reference definitions serve as templates that enable automatic recognition and classification of resources, so when new resources appear, they can be quickly matched against existing or pre-configured schemas without requiring ad-hoc development work

Inventive Principle:
Principle #10Preliminary action

3Reliability

If the NFVO stores information about recognized resources, then dependency management is improved and deletion errors are prevented, but unrecognized resources cannot benefit from these protective mechanisms

Engineering Contradiction:
Improvedependency management reliabilityVSAvoidresource type coverage
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent introduces a generic resource representation as an intermediary layer between the VIM resources and the NFVO's dependency management system. This generic representation acts as a mediator that translates diverse VIM resource types into a unified format that the NFVO can recognize and manage, allowing dependency tracking and deletion protection to be applied universally across all resource types through this intermediate representation layer

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250023798A1Configurable support for generic virtualized infrastructure manager resources
Publication Date: 2025.01.16 TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
  • US20250023798A1 patent drawing
  • US20250023798A1 patent drawing
  • US20250023798A1 patent drawing

AI summary

A network node can be configured to provide a network function virtualization orchestrator (“NFVO”) in a virtualization environment. The network node can determine that information associated with an unrecognized resource meets criteria associated with a reference definition for a type of recognized resource. The network node can, responsive to determining that the information associated with the unrecognized resource meets the criteria, store an indication of the unrecognized resource as a recognized resource.