Cloud-Native Microservice Bundling for Network Function Deployment

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Current network function virtualization approaches in cloud infrastructure face challenges such as long development and deployment times, complex upgrades, inefficient resource utilization, and increased operational costs due to inter-dependent network functions, which complicate fault management and resilience.

Innovation Solution

Bundling network functions as a single microservice in a cloud environment, using a service deployment manager to instantiate and manage microservices based on subscriber requirements, with Kubernetes for efficient deployment and management, and a Microservices Store for compatibility and interoperability management.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If network functions are deployed individually with static integration, then operational determinism is maintained, but development and deployment turn-around time increases

Engineering Contradiction:

Improveoperational determinismVSAvoiddevelopment and deployment turn-around time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments network functions into independent, loosely-coupled microservices that can be developed, deployed, and managed separately. Each microservice handles a specific network function (e.g., session management, mobility management) and can be updated independently without affecting other services, thus reducing development and deployment time while maintaining operational reliability through modular architecture.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements dynamic service composition where network functions are assembled on-demand based on service requirements rather than pre-configured static chains. The system dynamically selects and orchestrates appropriate microservices at runtime, enabling faster deployment of new services and features without lengthy reintegration testing, while maintaining determinism through standardized interfaces and service level agreements.

Inventive Principle:

Principle #15Dynamics

2Reliability

If network functions are statically integrated to ensure reliability, then fault resilience is maintained, but system complexity increases

Engineering Contradiction:

Improvefault resilienceVSAvoidsystem complexity

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

By segmenting the network into independent microservices with well-defined boundaries and interfaces, the patent reduces system complexity compared to tightly-coupled monolithic architectures. Each service can be developed, tested, and deployed independently, simplifying the overall system management while maintaining fault resilience through isolation - failures in one service do not propagate to others.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent introduces service orchestration and API gateway layers as intermediaries that manage communication and coordination between microservices. These intermediaries handle service discovery, load balancing, and fault isolation, reducing the complexity of direct service-to-service interactions while maintaining system reliability through centralized management of service lifecycles and dependencies.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Adaptability or versatility

If cloud infrastructure is used for network function virtualization, then deployment flexibility is improved, but reliability decreases compared to traditional servers

Engineering Contradiction:

Improvedeployment flexibilityVSAvoidinfrastructure reliability

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent implements comprehensive monitoring and feedback mechanisms that track the health, performance, and reliability of microservices deployed on cloud infrastructure. Service level agreements (SLAs) define expected performance metrics, and the system continuously monitors these metrics, triggering automatic remediation actions or failover when thresholds are breached, thus maintaining reliability comparable to traditional infrastructure while preserving cloud deployment flexibility.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent employs proactive reliability measures including redundant service deployments, pre-configured failover mechanisms, and capacity buffering in the cloud infrastructure. By provisioning backup services and resources in advance and implementing automated failover policies, the system cushions against potential failures inherent in cloud environments, maintaining high availability and reliability while leveraging the flexibility of cloud-based microservice deployment.

Inventive Principle:

Principle #11Beforehand cushioning (Prior cushioning)

Data Source

PatentUS11637761B2Systems and methods to deploy cloud-native microservices for communication services on scale

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

AI summary

A method for bundling network functions as a single microservice in a cloud environment. A service deployment manager may acquire subscriber location information associated with a subscriber or a subscriber profile associated with the subscriber. Moreover, the service deployment manager may utilize the subscriber location information or the subscriber profile to select a cloud location. For example, the cloud location may be based on load, geographical proximity, service profile, etc.