Container Engine Automation Without Connection Plugins

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for interfacing automation systems with container engines incur high computational and storage overhead due to the need for connection plugins and separate instances of automation systems within and outside containers, leading to inefficient resource usage.

Innovation Solution

A processing device generates a payload within a container instance using a domain-specific automation file, leveraging the container engine to eliminate the need for connection plugins and separate instances, thereby conserving storage and processing resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If connection plugins and separate instances of automation systems are used within and outside containers, then automation tasks can be executed, but computational and storage overhead increases significantly

Engineering Contradiction:

Improveautomation task executionVSAvoidcomputational overhead

Core Design Contradiction:

Extent of automationVSLoss of energy

Solution Approach 1:

The patent merges the automation system with the container engine into a single integrated system. Instead of running separate automation system instances inside and outside containers with connection plugins, the automation functionality is built directly into the container engine, eliminating redundant components and reducing computational overhead while maintaining full automation capability

Inventive Principle:

Principle #5Merging (Combining)

Solution Approach 2:

The container engine is enhanced to perform both container management and automation system functions universally. The single integrated system can execute both container operations and automation tasks without requiring separate specialized instances, thereby reducing resource consumption while preserving comprehensive functionality

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Extent of automation

If connection plugins and separate instances of automation systems are used within and outside containers, then automation tasks can be executed, but storage overhead increases

Engineering Contradiction:

Improveautomation task executionVSAvoidstorage overhead

Core Design Contradiction:

Extent of automationVSLoss of substance

Solution Approach 1:

By combining the automation system with the container engine, the patent eliminates the need for separate storage resources required by connection plugins and multiple automation system instances. The integrated architecture shares common storage infrastructure, reducing duplicate storage overhead while maintaining full automation functionality

Inventive Principle:

Principle #5Merging (Combining)

3Adaptability or versatility

If connection plugins are used to interface automation systems with container engines, then automation tasks can be executed across contexts, but device complexity increases

Engineering Contradiction:

Improvecontext translation capabilityVSAvoidsystem architecture complexity

Core Design Contradiction:

Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent merges the automation system with the container engine to create a unified architecture that eliminates the need for connection plugins. The integrated system handles context translation and cross-context communication internally through shared data structures and memory, reducing architectural complexity while maintaining adaptability across different execution contexts

Inventive Principle:

Principle #5Merging (Combining)

Data Source

PatentEP4645078A1Executing an automation system with a container engine

Publication Date: 2025.11.05 RED HAT LLC

Figure 1
Figure 2A~2B
Figure 3

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.