Container-Engine Automation Without Connection Plugin Overhead

Solution Overview

Problem

Existing automation systems interfacing with container engines face high computational and storage overhead due to repeated connection establishment and maintenance of separate instances within and outside the container, leading to inefficiencies in resource usage.

Innovation Solution

A processing device executes an automation system within a container engine, generating a payload within the container instance based on a domain-specific automation file, eliminating the need for connection plugins and separate instances, thereby reducing computational and storage overhead.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If separate automation system instances are maintained inside and outside the container with connection plugins, then automation tasks can be performed, but computational overhead and storage overhead increase due to repeated connection establishment and maintenance

Engineering Contradiction:

Improveautomation task executionVSAvoidcomputational overhead

Core Design Contradiction:

ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent merges the automation system instance into the container engine itself, eliminating the need for separate instances inside and outside the container. The container engine directly executes automation tasks by generating payloads from domain-specific automation files, removing the connection plugin layer and reducing computational overhead associated with connection establishment and maintenance.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent extracts the connection plugin component from the automation architecture. By removing the connection plugin that previously mediated between separate automation instances and the container, the system eliminates the overhead of repeated connection establishment and maintenance while retaining automation functionality.

Inventive Principle:

Principle #2Taking out (Extraction)

2Productivity

If separate automation system instances are maintained inside and outside the container with connection plugins, then automation tasks can be performed, but storage overhead increases due to connection maintenance

Engineering Contradiction:

Improveautomation task executionVSAvoidstorage overhead

Core Design Contradiction:

ProductivityVSQuantity of substance

Solution Approach 1:

The patent merges the automation system instance into the container engine itself, eliminating the need for separate instances inside and outside the container. The container engine directly executes automation tasks by generating payloads from domain-specific automation files, removing the connection plugin layer and reducing computational overhead associated with connection establishment and maintenance.

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The patent extracts the connection plugin component from the automation architecture. By removing the connection plugin that previously mediated between separate automation instances and the container, the system eliminates the overhead of repeated connection establishment and maintenance while retaining automation functionality.

Inventive Principle:

Principle #2Taking out (Extraction)

3Productivity

If connection plugins are used to interface automation systems with container engines, then automation tasks can be executed, but device complexity increases due to connection establishment and teardown processes

Engineering Contradiction:

Improveautomation task executionVSAvoidconnection management complexity

Core Design Contradiction:

ProductivityVSDevice complexity

Solution Approach 1:

The patent extracts the connection plugin component from the automation architecture. By removing the connection plugin that previously mediated between separate automation instances and the container, the system eliminates the overhead of repeated connection establishment and maintenance while retaining automation functionality.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent merges the automation system instance into the container engine itself, eliminating the need for separate instances inside and outside the container. The container engine directly executes automation tasks by generating payloads from domain-specific automation files, removing the connection plugin layer and reducing computational overhead associated with connection establishment and maintenance.

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentUS20250335249A1Executing an automation system with a container engine

Publication Date: 2025.10.30 RED HAT INC

AI summary

Embodiments of the present disclosure relate to executing an automation system with a container engine. More specifically, a processing device obtains a domain-specific automation file comprising an indication of a set of tasks for automating a process. The processing device provides, via a host OS of a device, the domain-specific automation file to a container instance managed by a container engine. The processing device generates, via an automation system, a payload within the container instance based on the domain-specific automation file. The processing device outputs the payload to cause the set of tasks to be performed.