VnicSet Operator for Kubernetes Media Throughput

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current Kubernetes-based cloud environments face limitations in providing mobile communications services, including limited media throughput, unreliable IP addresses, non-uniform ingress and egress communication paths, and inadequate failover capabilities, which hinder high-availability and scalability in communication networks.

Innovation Solution

The implementation of a custom VnicSet operator system that manages virtual network interface controllers (Vnics) within a Kubernetes environment, allowing for direct external network reachability, dynamic IP address allocation, and persistent virtual IP addressing, thereby bypassing traditional Kubernetes infrastructure limitations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional hardware-based SBC components are used, then reliability and media throughput are improved, but device complexity and cost increase

Engineering Contradiction:
Improveservice availabilityVSAvoidinfrastructure complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates virtual copies of network interface controllers (vNICs) that replicate the functionality of physical hardware SBC components. These virtual network interfaces are injected into Kubernetes pods, allowing software-based implementation that mimics hardware behavior while reducing physical infrastructure complexity and enabling easier scaling.

Inventive Principle:
Principle #26Copying

2Adaptability or versatility

If cloud-based containerized environments are used, then scalability and ease of deployment are improved, but media throughput and network reliability deteriorate

Engineering Contradiction:
Improvedeployment flexibilityVSAvoidnetwork service reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a network gateway and virtual network interface controller as intermediary components between the Kubernetes containerized environment and external networks. These intermediaries manage network traffic, provide consistent IP addressing, and ensure reliable communication paths while maintaining the scalability and deployment flexibility of cloud-based environments.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Ease of operation

If dynamic IP address allocation is implemented, then ease of operation is improved, but communication path uniformity deteriorates

Engineering Contradiction:
ImproveIP address managementVSAvoidcommunication path consistency
Core Design Contradiction:
Ease of operationVSStability of the object's composition

Solution Approach 1:

The patent implements a dual IP address system where virtual network interfaces can be assigned either static or dynamic IP addresses based on operational requirements. This parameter change capability allows the system to maintain consistent communication paths for critical services while enabling flexible IP management for other workloads, resolving the contradiction between operational ease and path uniformity.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS20250021367A1Cloud based network function
Publication Date: 2025.01.16 ORACLE INT CORP
  • US20250021367A1 patent drawing
  • US20250021367A1 patent drawing
  • US20250021367A1 patent drawing

AI summary

Systems and methods are disclosed for implementing a cloud based network function. In certain embodiments, a method may comprise operating a custom operator in a containerized software environment such as Kubernetes to manage a virtual network interface controller (Vnic) on an application pod, the Vnic being reachable directly from a network external to the containerized software environment. The method may include identifying the application pod to which to add the Vnic, determining a worker node in the containerized software environment on which the application pod is running, creating the Vnic on the worker node, and executing a job on the worker node to inject the Vnic into the application pod.