Repeatable Network Architecture for Multi-Cloud Visibility and Control

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing cloud computing migration methods result in duplicative work and lack of visibility and control across multiple cloud service providers, leading to isolated cloud computing environments that cannot communicate or be managed from a single interface.

Innovation Solution

A repeatable network architecture with layers including cloud operations, applications, and global transit layers, utilizing a controller and gateways to deploy and manage constructs across multiple cloud service providers, enabling visibility and control over network traffic and constructs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If cloud computing environments are migrated using traditional methods, then individual cloud deployments can be established, but duplicative work must be performed for each migration and lack of visibility and control across multiple providers occurs

Engineering Contradiction:
Improvemigration efficiencyVSAvoidduplicative work time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent implements a controller that stores network architecture configurations and automatically copies/deployes the same architecture across multiple cloud service providers. This eliminates duplicative manual work by using templates that can be replicated across different clouds, directly addressing the productivity vs. time loss contradiction.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system performs preliminary actions by pre-defining network architecture configurations, policies, and constructs in a controller before actual deployment. This advance preparation enables rapid replication across multiple clouds without repeating setup work, resolving the efficiency versus time waste issue.

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If multiple cloud service providers are used for computing needs, then computing capacity and flexibility are improved, but the cloud computing environments become isolated and cannot communicate with each other

Engineering Contradiction:
Improvecloud provider flexibilityVSAvoidenvironment connectivity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The patent creates a universal network architecture that functions across multiple cloud service providers simultaneously. The controller manages constructs and establishes connections across different clouds, enabling the system to work with any cloud provider while maintaining connectivity, thus resolving the adaptability versus ease of operation contradiction.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The controller acts as an intermediary that manages connections between isolated cloud environments. It establishes network paths and manages constructs across different providers, enabling communication between previously isolated clouds while maintaining flexibility in provider selection.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Adaptability or versatility

If cloud computing environments are deployed across multiple providers, then computing resources are distributed, but unified visibility and control over network traffic and constructs is lost

Engineering Contradiction:
Improvemulti-provider deploymentVSAvoidnetwork visibility
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent merges visibility and control functions into a single centralized controller that manages all cloud environments. This unified controller provides consolidated views of network traffic and constructs across multiple providers, eliminating information loss while maintaining multi-provider deployment flexibility.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The controller provides universal visibility and control functions that work across all cloud service providers simultaneously. It consolidates network information from multiple sources into a unified interface, resolving the contradiction between adaptability and information loss.

Inventive Principle:
Principle #6Universality (Multi-functionality)

4Ease of manufacture

If traditional migration methods are used for each cloud deployment, then individual environments can be established, but scripts and automations must be re-developed for each migration

Engineering Contradiction:
Improvedeployment capabilityVSAvoidautomation reuse
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

The system stores network architecture configurations and automation scripts in a controller, allowing them to be copied and reused across multiple deployments. This eliminates the need to re-develop scripts for each migration while maintaining deployment capability, directly addressing the ease of manufacture versus productivity contradiction.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

Automation scripts and configurations are prepared in advance in the controller before deployment. This preliminary preparation enables reuse across multiple migrations without re-development, resolving the contradiction between deployment ease and automation reuse efficiency.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12355621B1Systems and methods for implementing a repeatable network architecture
Publication Date: 2025.07.08 AVIATRIX SYSTEMS INC
  • US12355621B1 patent drawing
  • US12355621B1 patent drawing
  • US12355621B1 patent drawing

AI summary

A cloud computing system built in accordance with a repeatable network architecture is disclosed that includes a controller, a first set of spoke gateways and a first transit gateway. The controller is configured to deploy the first set of spoke gateways in a first cloud thereby forming an applications layer of the repeatable network architecture, deploy the first transit gateway in the first cloud thereby forming a global transit layer of the repeatable network architecture, and establish communicative couplings between each of the first set of spoke gateways and the first transit gateway. The controller is also configured to deploy a first set of spoke VPCs within the first cloud, wherein each of the spoke VPCs has deployed therein one of the first set of spoke gateways, and a first transit VPC within the first cloud, wherein the first transit gateway is deployed in the first transit VPC.