Multi-Cluster Service Stitching for Cloud-Native Network Functions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems fail to enable users to easily configure and manage multi-tier network architectures across multiple clusters, particularly in cloud-based environments, lacking the ability to stitch network functions and configure routers for traffic flow between clusters.

Innovation Solution

A multi-data center automation platform (MDCAP) that automates the deployment and configuration of network service packages across multiple clusters, enabling one-click deployment and management of network functions through a dashboard, using Kubernetes® StatefulSet pods and router configurations to facilitate traffic flow between clusters.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multi-tier network architectures are deployed across multiple clusters, then redundancy and availability are improved, but configuration and implementation become difficult

Engineering Contradiction:
ImproveavailabilityVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the multi-cluster network configuration into modular service packages, where each package encapsulates a specific network service with its required clusters and routing configurations. This allows complex multi-tier architectures to be broken down into manageable, independently configurable units that can be deployed and managed separately.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary automation platform that mediates between the user and the complex multi-cluster configuration. This platform automatically generates routing rules, configures network policies, and manages service dependencies across clusters, eliminating the need for users to manually configure complex network architectures.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Adaptability or versatility

If traditional systems are used for network configuration, then existing infrastructure is maintained, but end users cannot configure or adjust multi-tier architectures during run time or design time

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoiduser accessibility
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system enables self-service configuration through automated service package generation and deployment. Users can define high-level service requirements, and the system automatically configures the underlying multi-cluster architecture, routing rules, and network policies without requiring manual intervention or deep technical expertise.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent implements dynamic configuration capabilities that allow service packages and their associated network architectures to be modified at runtime. Users can add, remove, or adjust clusters and services in deployed multi-tier architectures without requiring complete reconfiguration, enabling flexible adaptation to changing requirements.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS12609876B2Network service stitching for cloud native network functions and virtual network functions
Publication Date: 2026.04.21 RAKUTEN SYMPHONY INC
  • US12609876B2 patent drawing
  • US12609876B2 patent drawing
  • US12609876B2 patent drawing

AI summary

Systems and methods for generating and configuring network service packages includes multiple clusters for executing cloud native network functions and virtual network functions. A method includes receiving a request to generate a network service package comprising a first cluster and a second cluster. The method includes generating a dependency within the network service package such that the second cluster depends upon the first cluster. The method includes automatically configuring a first router associated with the first cluster and a second router associated with the second router such that the first router and the second router can route traffic to each other.