Container Orchestration Templates for Daemon and Batch Applications

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Container orchestration management is complicated for general users and difficult to share applications, especially in cloud environments using platforms like Kubernetes, Docker Swarm, and Apache Mesos.

Innovation Solution

A container orchestration management device that includes an application template managing device to create and manage templates for application deployment, a daemon application managing device for continuous execution, and a batch application managing device for temporary execution, along with a data storage device to store user and application information, facilitating easy sharing and management of applications through container orchestration.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If container orchestration platforms (Kubernetes, Docker Swarm, Apache Mesos) are used to manage and deploy containerized applications, then application deployment capability and resource management are improved, but system complexity and difficulty of operation increase significantly for general users

Engineering Contradiction:
Improveapplication deployment capabilityVSAvoiddifficulty of setup and management
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent introduces a container orchestration management device as an intermediary layer between users and the container orchestration platform. This mediator handles complex orchestration tasks, template management, and deployment processes, shielding users from the underlying complexity while maintaining high deployment capability. The management device translates simple user requests into complex orchestration commands.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent implements template-based application management where application configurations are copied and reused through templates. Instead of manually configuring each application deployment, users can create templates once and replicate them across multiple deployments. This copying mechanism simplifies operations while maintaining consistent deployment practices.

Inventive Principle:
Principle #26Copying

2Productivity

If container orchestration platforms are implemented to manage multiple microservice applications, then application management capability is improved, but ease of sharing applications between users deteriorates

Engineering Contradiction:
Improveapplication management capabilityVSAvoiddifficulty of sharing applications
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent creates a universal template management system that serves multiple functions: storing application templates, managing user permissions, enabling sharing between users, and facilitating deployment. This multi-functional approach allows the same infrastructure to support both complex management capabilities and simple sharing operations, resolving the contradiction between management power and sharing ease.

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

Solution Approach 2:

The management device acts as an intermediary that handles sharing operations between users. It manages template visibility, access permissions, and sharing requests, thereby enabling easy application sharing while maintaining secure and organized multi-user management capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS20250240300A1Container orchestration management device and method of operating the same
Publication Date: 2025.07.24 ELECTRONICS & TELECOMM RES INST
  • US20250240300A1 patent drawing
  • US20250240300A1 patent drawing
  • US20250240300A1 patent drawing

AI summary

Disclosed is a container orchestration management device including an application template managing device that creates first execution information including a container image, which are required for deployment of a first application, as a first template based on a request signal of a first user including the first execution information, creates second execution information including a container image, which are required for deployment of a second application, as a second template based on a request signal of the first user including the second execution information, and manages the first template and the second template, a daemon application managing device that creates the first application through container orchestration, continuously executes the first application, and deploys and manages the first application, based on the first template, and a batch application managing device that creates the second application through the container orchestration, and manages the second application, based on the second template.