Cloud Infrastructure Rule Isolation via Configuration Externalization

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current technologies in cloud computing environments lack the ability to update computing devices implementing rule management systems (RMS) without impacting other devices, necessitating improved techniques for independent updates.

Innovation Solution

A cloud computing system that isolates and updates application rule sets independently from the software download process, separating rules, policies, and guidelines from the underlying operational functionality, allowing for modular and efficient updates without affecting other devices.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If computing devices in cloud-based RMS systems are updated, then system functionality is improved, but other devices are impacted and require simultaneous updates

Engineering Contradiction:
Improvesystem functionalityVSAvoidupdate coordination
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the RMS system into independent virtual machine instances, each capable of being updated independently. This allows individual devices to be updated without impacting others, resolving the contradiction between improving system functionality and managing update coordination complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a configuration repository and virtual machine management system as intermediaries that decouple the update process from direct device impact. Updates are staged and deployed through this intermediary layer, allowing controlled updates without forcing simultaneous changes across all devices.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If rules and software are tightly coupled, then operational functionality is maintained, but updating rules requires software downloads

Engineering Contradiction:
Improveupdate efficiencyVSAvoidsoftware dependency
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent segments rules, policies, and guidelines from the underlying software by storing them as separate configuration data in a repository. This allows rules to be updated independently without requiring software downloads, improving update efficiency while reducing software dependency.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent extracts the rule set from the software binary and stores it as external configuration data. This extraction allows rules to be modified and deployed independently from the software itself, enabling rapid rule updates without software distribution.

Inventive Principle:
Principle #2Taking out (Extraction)

3Stability of the object's composition

If configuration changes are made across all devices, then system consistency is improved, but update time and resource consumption increase

Engineering Contradiction:
Improvesystem consistencyVSAvoidupdate time
Core Design Contradiction:
Stability of the object's compositionVSLoss of time

Solution Approach 1:

The patent implements dynamic configuration deployment where virtual machine instances can be updated independently and at different times. The system maintains consistency through the centralized configuration repository while allowing flexible update timing, reducing overall update time while preserving system consistency.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent enables selective updating of individual virtual machine instances without requiring all devices to be updated simultaneously. Failed or unnecessary updates can be discarded without affecting other devices, and successful updates are recovered and propagated as needed, reducing total update time.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS12199818B2Cloud infrastructure for isolation and run-time behavioral tuning through configuration externalization
Publication Date: 2025.01.14 CAPITAL ONE SERVICES LLC
  • US12199818B2 patent drawing
  • US12199818B2 patent drawing
  • US12199818B2 patent drawing

AI summary

Embodiments generally relate to a cloud computing infrastructure and method of operating the same including at least: receiving a configuration file from a configuration repository; receiving a request from a first device to configure an application rule set of one or more nodes based on the configuration file; transmitting the request to a receiver node selected from the one or more nodes; generating a notification alerting the one or more nodes that the request is stored on a database; distributing the configuration file to a subset of the one or more nodes based on receipt of an access request from the one or more nodes; and updating the application rule set of the subset of the one or more nodes based on the configuration file.