Cloud Network Management Architecture for Isolated Remote Deployment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Large enterprises face challenges in integrating and streamlining their operations due to the proliferation of siloed custom software applications, which hinder innovation, regulatory compliance, and operational efficiency.
Innovation Solution
A remotely-hosted Application Platform as a Service (aPaaS) system that automates workflows, supports MVC applications, provides standardized components, and ensures enterprise-grade security, enabling efficient development and integration of custom applications across the enterprise.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If a remote network management platform hosts services on public cloud network resources, then infrastructure provisioning time is reduced and operational focus can shift to service development, but the platform loses control over its own infrastructure configuration and update processes
Solution Approach 1:
The system segments infrastructure management into distinct functional components: infrastructure-as-code templates define desired states, deployment pipelines execute updates, and quarantine systems isolate changes. This segmentation allows the platform to maintain control over configuration while leveraging cloud resources, resolving the contradiction between reduced provisioning time and retained configuration control.
Solution Approach 2:
The patent introduces intermediary components including infrastructure-as-code platforms that act as mediators between the management platform and cloud infrastructure, deployment pipelines that mediate update processes, and quarantine systems that mediate between approved and unapproved configurations. These intermediaries enable controlled infrastructure management without requiring direct cloud provider involvement in configuration decisions.
2Ease of manufacture
If the platform uses public cloud network infrastructure, then hardware provisioning is simplified, but the platform cannot isolate its management traffic from external network access
Solution Approach 1:
The system segments network operations into isolated functional zones: management virtual machines operate in isolated network segments, deployment pipelines execute in controlled environments, and quarantine systems create isolated containment zones for unapproved changes. This network segmentation maintains reliability and isolation while leveraging cloud hardware provisioning capabilities.
Solution Approach 2:
The patent applies local quality by creating specialized network environments with specific isolation properties for different functions: management VMs receive enhanced network isolation, deployment pipelines operate in controlled network zones, and quarantine systems implement strict access controls. Each component receives tailored network qualities appropriate to its function, maintaining reliability while using cloud infrastructure.
3Productivity
If the platform deploys updates directly to production environments, then deployment speed increases, but the risk of introducing errors or security vulnerabilities increases
Solution Approach 1:
The system implements preliminary action through infrastructure-as-code templates that define desired states before deployment, pre-validation mechanisms that check configurations before application, and quarantine systems that isolate updates before production release. These preliminary actions enable rapid deployment while maintaining safety through pre-execution validation and isolation.
Solution Approach 2:
The patent introduces deployment pipelines as intermediary systems that mediate between development and production environments, and quarantine systems that act as intermediaries between approved and unapproved configurations. These intermediaries enable fast deployment by automating validation and isolation processes, maintaining reliability without sacrificing speed.
4Ease of operation
If the platform hosts all infrastructure services within the public cloud network, then operational simplicity increases, but security control and compliance flexibility decrease
Solution Approach 1:
The system segments infrastructure services into manageable functional components that can be independently configured and deployed. Infrastructure-as-code templates segment configuration management, deployment pipelines segment update processes, and quarantine systems segment approval workflows. This segmentation maintains operational simplicity while enabling flexible security controls through modular, independently configurable components.
Solution Approach 2:
The patent implements dynamics by creating adaptable infrastructure configurations that can change based on security requirements. Infrastructure-as-code templates enable dynamic configuration updates, deployment pipelines provide dynamic deployment control, and quarantine systems offer dynamic approval mechanisms. These dynamic capabilities maintain operational simplicity while providing flexible security adaptability.
Data Source
AI summary
A software architecture within a public cloud network may include units of: (i) a plurality of computational instances respectively related to managed networks, (ii) a plurality of servers configurable as load simulators, (iii) administrative components configured to deploy and update the software architecture, and (iv) shared infrastructure services, wherein the units of the software architecture are implemented on virtual machines of the public cloud network and are connected to but logically isolated from one another by way of different access controls or policies. A provider network, coupled to the software architecture by way of network gateways within the shared infrastructure services, may be configured to deliver the configuration, software packages, and database schema to the infrastructure-as-code platform.