Distributed Topology Framework for Automated Software Configuration

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software configuration and automation frameworks are inefficient and error-prone, requiring extensive manual intervention, limiting parallel processing, and lacking remote execution capabilities, which leads to resource wastage and increased time in setting up complex software environments.

Innovation Solution

A distributed topology environment (DTE) framework that enables automated configuration of complex software installations through cloud computing, allowing users to create and execute reproducible topologies using building blocks, which can be executed independently across multiple machines, and includes features for debugging, quality assurance, and remote execution.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If manual configuration of software components is performed, then users can set up working environments, but time consumption and resource requirements increase significantly

Engineering Contradiction:
Improveease of configurationVSAvoidtime consumption
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent applies preliminary action by pre-configuring software environments using templates that contain pre-defined software components, dependencies, and configuration parameters. Users can select from pre-prepared templates rather than configuring everything from scratch, significantly reducing setup time while maintaining ease of operation.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system allows users to modify parameters of pre-configured templates to suit specific needs. By changing parameters such as software versions, configuration options, and component selections within the template framework, users can customize environments quickly without manual configuration of each component.

Inventive Principle:
Principle #35Parameter changes

2Ease of manufacture

If users configure each software component individually, then specific software installations can be set up, but the complexity of the configuration process increases

Engineering Contradiction:
Improveease of setupVSAvoidconfiguration complexity
Core Design Contradiction:
Ease of manufactureVSDevice complexity

Solution Approach 1:

The patent segments the configuration process into modular templates, where each template represents a complete working environment with pre-configured software components. Instead of configuring individual components separately, users work with integrated template units that can be selected and deployed as complete packages, reducing configuration complexity.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The templates serve multiple functions: they define software components, specify dependencies, set configuration parameters, and establish interconnections between components. This multi-functional approach eliminates the need for separate configuration steps for each aspect, simplifying the overall setup process.

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

3Productivity

If automated software is used to parallelize processes, then execution efficiency increases, but human control and monitoring become more difficult

Engineering Contradiction:
Improveexecution efficiencyVSAvoiduser control
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The system implements feedback mechanisms that provide real-time status information about template deployment, software installation progress, and configuration state. Users receive notifications and can monitor automated processes through a user interface, maintaining control and visibility while benefiting from automated parallel execution.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent introduces an intermediary layer (the template management system) that mediates between user commands and automated execution. Users interact with high-level template definitions rather than individual configuration commands, allowing automated parallel processing while maintaining simple user control through the intermediary interface.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Reliability

If specialized knowledge is required for configuration, then proper software environments can be set up, but the availability of configuration becomes limited to specific individuals

Engineering Contradiction:
Improveconfiguration accuracyVSAvoiduser availability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent uses templates as reusable copies of proven working environments. Instead of requiring users to recreate configurations from scratch or rely on individual expertise, validated template definitions can be copied and deployed multiple times across different systems. This preserves configuration accuracy while making it accessible to any user with access to the template library.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The system recovers and preserves configuration knowledge within template definitions that can be stored, shared, and reused. Instead of knowledge being tied to specific individuals, the essential configuration knowledge is extracted into reusable templates that can be recovered and applied by any user, making expertise broadly available while maintaining reliability.

Inventive Principle:
Principle #34Discarding and recovering

Data Source

PatentUS10430232B2Controllable workflow in software configuration automation
Publication Date: 2019.10.01 ORACLE INT CORP
  • US10430232B2 patent drawing
  • US10430232B2 patent drawing
  • US10430232B2 patent drawing

AI summary

A distributed topology system may include a distributed topology engine configured to run on a server device and define a topology consisting of one or more building blocks. Each building block may represent one or more tasks pertaining to an application. The system may also include a distributed topology application configured to run on a client device and automatically execute one or more of the building blocks. A distributed topology database may be used to store the topology. A pause/resume module may be configured to pause at least one task responsive to a pause request. The pause/resume module may also be configured to resume a previously paused task.