Object-Oriented Infrastructure-as-Code for Scalable Parallel Provisioning

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional infrastructure-as-code (IAC) software tools are single-threaded and not scalable, making them inadequate for implementing Internet of Components (IoC) functionalities.

Innovation Solution

The object-oriented infrastructure-as-code platform (OOIACP) uses a declarative configuration language-based IAC software tool and a wrapper tool to implement object-oriented programming features, establishing a class hierarchy and using semaphores and hooks to control resource access and process synchronization, enabling concurrent and independent processing of lifecycle and workload events across multiple instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If conventional IAC software tools are used, then infrastructure provisioning functionality is provided, but scalability is limited due to single-threaded architecture

Engineering Contradiction:
ImprovescalabilityVSAvoidsystem architecture complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The system segments the monolithic conventional IAC tool into multiple independent OOIACP instances that can run in parallel. Each instance handles specific workload events independently, enabling scalable concurrent processing while maintaining the core IAC functionality through standardized interfaces and protocols

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary layer (the wrapper tool and event processing mechanism) between the conventional IAC tool and the workload events. This intermediary translates events into standardized formats, manages event routing, and coordinates multiple instances, thereby enabling scalability without directly modifying the core IAC tool architecture

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If multiple instances are used for parallel processing, then productivity and scalability improve, but resource access control and process synchronization become more complex

Engineering Contradiction:
Improveparallel processing capabilityVSAvoidsynchronization mechanism complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms through event-driven architecture where instances report their state and resource usage back to the coordination layer. This enables dynamic load balancing, automatic scaling decisions, and coordinated resource allocation across multiple instances without requiring complex manual synchronization protocols

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent creates a universal event processing interface and standardized event formats that work across all OOIACP instances. This universal interface handles resource access control and synchronization consistently across different instances, simplifying the complexity by providing a single pattern to follow rather than instance-specific synchronization mechanisms

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

Data Source

PatentUS12367016B2Object-oriented infrastructure-as-code platform (OOIACP)
Publication Date: 2025.07.22 CENTURYLINK INTELLECTUAL PROPERTY LLC
  • US12367016B2 patent drawing
  • US12367016B2 patent drawing
  • US12367016B2 patent drawing

AI summary

Novel tools and techniques are provided for implementing object-oriented infrastructure-as-code platform (“OOIACP”) and its functionalities. In various embodiments, when a request to process one or more lifecycle events is received, a computing system may perform: selecting and scaling across a plurality of OOIACP instances; and causing the selected plurality of OOIACP instances to process the one or more lifecycle events. In some cases, each OOIACP instance may include an infrastructure-as-code (“IAC”) command line that instantiates component infrastructure among a plurality of component infrastructure to process at least one lifecycle event among the one or more lifecycle events concurrently and independently of other OOIACP instances. In some instances, the first plurality of OOIACP instances may be located within an environment in which the plurality of component infrastructure is located.