CNF Runtime Validation With Admission Control and Remediation

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

The challenge of adapting vendor-specific Containerized Network Function (CNF) deployments to service provider platforms and ensuring interoperability, resource requirements, and health checks during runtime is burdensome, requiring manual intervention and lacking automated validation.

Innovation Solution

Implementing a system with specialized-operator enabled admission control and Custom Resource Definition (CRD) plugins, utilizing sensors and actuators to automate CNF lifecycle management, including NFV extensions for automated remediation and validation of CNF deployments across heterogeneous cloud platforms.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual intervention is used for CNF deployment validation, then flexibility and adaptability are maintained, but operational complexity and time consumption increase

Engineering Contradiction:

ImproveCNF deployment validation processVSAvoidTime for manual validation and intervention

Core Design Contradiction:

Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary validation actions by automatically checking CNF package compliance with platform requirements before deployment occurs. The validation framework pre-verifies interoperability, resource requirements, and health check configurations, eliminating the need for manual intervention during deployment and reducing time loss.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The validation framework enables self-service by automatically validating CNF packages against platform requirements without requiring manual operator intervention. The system self-verifies compliance with policy rules, resource constraints, and health check configurations, transforming a manual process into an automated self-validating system.

Inventive Principle:

Principle #25Self-service

2Reliability

If automated validation systems are implemented, then deployment reliability and validation consistency are improved, but system complexity increases

Engineering Contradiction:

ImproveCNF deployment validationVSAvoidValidation framework structure

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The validation framework is segmented into distinct validation modules that independently check different aspects of CNF compliance: interoperability validation, resource requirement validation, and health check validation. This segmentation allows the complex validation process to be divided into manageable, independent components that can be executed systematically.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The validation framework provides universal multi-functional validation capabilities that can assess multiple CNF package attributes simultaneously - including interoperability with CaaS toolsets, sidecar injection requirements, resource allocation constraints, and health check configurations - through a single integrated framework.

Inventive Principle:

Principle #6Universality (Multi-functionality)

3Manufacturing precision

If comprehensive validation checks are performed, then CNF deployment accuracy and compliance are improved, but processing time and computational resources increase

Engineering Contradiction:

ImproveCNF deployment complianceVSAvoidDeployment processing speed

Core Design Contradiction:

Manufacturing precisionVSProductivity

Solution Approach 1:

The framework performs comprehensive validation checks as a preliminary action before CNF deployment occurs. By validating interoperability, resource requirements, and health check configurations in advance, the system ensures deployment accuracy and compliance while avoiding rework or rejection during the actual deployment process.

Inventive Principle:

Principle #10Preliminary action

Solution Approach 2:

The validation framework implements feedback mechanisms that provide immediate results of validation checks, allowing the system to quickly identify and correct compliance issues. This feedback loop enables rapid iteration and ensures that only compliant CNF packages proceed to deployment, maintaining high accuracy without excessive processing delays.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS20260044328A1Containerized network function deployment during runtime resource creation

Publication Date: 2026.02.12 VERIZON PATENT & LICENSING INC

AI summary

Systems and methods described herein provide a Specialized-Operator enabled with admission control functionalities and Custom Resource Definition (CRD) plugins responsible for improving the reliability of the CNF Lifecycle Management operations for deploying containerized workloads on any heterogeneous cloud platform or in multi-cluster environments. According to one implementation, a computing device includes a sensor Network Function Virtualization (NFV)-extension and an actuator NFV-extension. The sensor NFV-extension obtains, from a Container Infrastructure Service Manager (CISM), an event signal that indicates a deficiency with a customer Containerized Network Function (CNF) deployment; detects a current state for the CNF deployment; determines an intent for the CNF deployment; identifies, based on the intent, a desired state for the CNF deployment; and selects, from a group of available actuator NFV-extensions, the actuator NFV-extension corresponding to the desired state. The actuator NFV-extension may be configured to initiate remediation of the CNF deployment to the desired state.