NFaaS Controller Scheduler Balancing Cloud Network Functions

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Communication networks face challenges in integrating third-party virtual machines into carrier networks, particularly in achieving telecommunications service provider-grade reliability and availability, while also managing costs and flexibility in software-defined networks (SDNs).

Innovation Solution

A system and method for providing Network Function as a Service (NFaaS) that combines virtual network resources with physical resources, utilizing a scheduler and load balancer to dynamically configure and balance resources, ensuring high availability and elasticity, and accommodating varying usage levels.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If vendor's network functions are operated in a cloud environment, then flexibility and elasticity are improved, but reliability deteriorates (from 99.999% to 99.9% availability)

Engineering Contradiction:

Improveflexibility and elasticityVSAvoidavailability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent introduces a carrier network as an intermediary layer between third-party vendor network functions and end customers. The carrier network provides telco-grade reliability (99.999% availability) while allowing vendors to deploy their flexible cloud-based network functions. This mediator absorbs the reliability requirements, allowing vendors to operate at lower availability levels while maintaining customer-facing service quality.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the network function deployment into two distinct layers: the carrier network infrastructure layer that ensures high reliability and availability, and the vendor network function layer that provides flexibility and elasticity. This segmentation allows each layer to optimize for its specific requirements without compromising the other.

Inventive Principle:

Principle #1Segmentation

2Reliability

If hardware solutions are used to achieve target availability, then reliability is improved, but capital expenditures and operational costs increase significantly

Engineering Contradiction:

ImproveavailabilityVSAvoidcapital expenditures and operational costs

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent makes the carrier network infrastructure universal by allowing it to host multiple third-party vendor network functions simultaneously. The same carrier network resources provide reliability for different vendors' network functions, spreading the cost burden and avoiding the need for each vendor to invest in separate hardware infrastructure to achieve telco-grade availability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Instead of requiring each vendor to purchase and deploy their own hardware infrastructure to achieve high availability, the patent allows vendors to copy their network functions to the carrier's existing reliable infrastructure. The carrier's proven hardware platform is replicated or shared across multiple vendors, eliminating redundant capital expenditures.

Inventive Principle:

Principle #26Copying

3Adaptability or versatility

If multiple vendors provide different solutions to the same cloud management requirements, then adaptability is improved, but operational costs increase by a factor of ten

Engineering Contradiction:

Improvevendor solution diversityVSAvoidoperational costs

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges multiple vendors' network function management under a single carrier network management framework. Instead of each vendor requiring separate management infrastructure and operations teams, the carrier consolidates the management of diverse vendor solutions into unified operational procedures, reducing operational costs while maintaining support for multiple vendor-specific functionalities.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS11467881B2Framework, method and apparatus for network function as a service for hosted network functions in a cloud environment

Publication Date: 2022.10.11 AT&T INTELLECTUAL PROPERTY I L P

AI summary

A system for providing network function as a service includes a combination of virtual network resources hosted on physical network resources, wherein the virtual network resources are communicatively chained to provide a dynamically configurable set of processing resources and a configurable controller in communication with the combination of virtual network resources, wherein the controller includes a scheduler and load balancer. The controller is configured to receive a request to provide network function as a service functionality, retrieve policies associated with the request, schedule the virtual network resources to be assigned in response to the request, instantiate the virtual network resources and balance the virtual network resources across one or more physical resources.