Cloud-Native VNF API Translation for Decentralized Infrastructure

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing cloud-native network function management systems, such as ETSI NFV MANO, are inefficient and cumbersome, particularly when managing decentralized infrastructure, and lack support for modern cloud-native application management solutions like Kubernetes and Helm charts, leading to scalability issues and inefficiencies in managing cloud-native virtual network functions.

Innovation Solution

A cloud-native management system (CNSM) that translates between standardized 3GPP APIs and infrastructure-specific APIs, enabling seamless integration with various cloud-native management solutions while minimizing impact on existing 5G OAM systems, and supports scalable and efficient management of cloud-native virtual network functions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If ETSI NFV MANO is used to manage cloud-native virtual network functions, then management coverage is provided, but management efficiency deteriorates and system becomes cumbersome

Engineering Contradiction:

Improvemanagement efficiencyVSAvoidsystem complexity

Core Design Contradiction:

Ease of operationVSDevice complexity

Solution Approach 1:

The patent introduces an API translation service as an intermediary component that sits between the existing ETSI NFV MANO system and cloud-native infrastructure. This translation service converts standardized 3GPP APIs into infrastructure-specific APIs, allowing the legacy management system to interact with modern cloud-native components without direct integration. The intermediary handles the complexity of multiple API formats, shielding the upper management layers from implementation details while enabling efficient cloud-native function management.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the management system into distinct functional layers: the existing ETSI NFV MANO orchestration layer, a new API translation service layer, and the cloud-native infrastructure layer. This segmentation allows each layer to operate independently with its own optimization - the orchestration layer maintains standardized processes, the translation layer handles API conversion efficiently, and the infrastructure layer leverages cloud-native capabilities. This modular approach reduces overall system complexity while improving management efficiency.

Inventive Principle:

Principle #1Segmentation

2Adaptability or versatility

If standardized 3GPP APIs are enforced across all infrastructure, then compatibility is improved, but adaptability to specific infrastructure solutions deteriorates

Engineering Contradiction:

Improveinfrastructure compatibilityVSAvoidAPI translation overhead

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The API translation service acts as a mediator that receives standardized 3GPP API requests and translates them into infrastructure-specific API calls. This allows the system to maintain compatibility with standardized interfaces at the management layer while adapting to the specific requirements of different cloud-native infrastructures at the implementation layer. The translation service dynamically selects and applies appropriate translation rules based on the target infrastructure type.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The translation service dynamically changes API parameters based on the target infrastructure. When a standardized 3GPP API request is received, the service modifies the request parameters, data formats, and communication protocols to match the specific requirements of the underlying infrastructure. This parameter transformation enables seamless adaptation to different infrastructure solutions without changing the standardized interface contract.

Inventive Principle:

Principle #35Parameter changes

3Productivity

If cloud-native infrastructure is decentralized, then scalability is improved, but management coordination deteriorates

Engineering Contradiction:

ImprovescalabilityVSAvoidmanagement coordination

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The API translation service implements a universal translation framework that can handle multiple infrastructure types and API formats through a single unified system. This multi-functional approach allows the same translation service to manage diverse decentralized cloud-native infrastructures without requiring separate management systems for each component. The universal interface standardizes coordination protocols, enabling efficient management of distributed resources while maintaining scalability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Data Source

PatentUS20250310205A1Managing cloud-native virtual network functions

Publication Date: 2025.10.02 MICROSOFT TECHNOLOGY LICENSING LLC

AI summary

The present disclosure generally relates to systems, methods, and computer-readable media for managing cloud-native virtual network functions (CNFs) in a telecommunication network environment. The systems described herein involve receiving a request and determining or otherwise identifying a specific infrastructure solution based at least in part on attributes of the request. After determining the infrastructure solution, the systems described herein facilitate translating requests between a standardized API and solution-specific APIs to facilitate integration with a variety of cloud-native management solutions while also minimizing impact to existing service-based management architectures (SBMA) of fifth generation (5G) operations administration and management (OAM) systems.