Graphical Interface for Automated Distributed Job Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In distributed systems, the manual deployment and configuration of software agents on remote network devices is time-consuming and expensive, requiring physical interaction and intensive programming, and job configuration is cumbersome, often necessitating dedicated interfaces or loading entire agents for configuration.

Innovation Solution

A method and apparatus that utilize a graphical user interface to receive and display job-configuration parameters, store them in a database, and perform computer-implemented jobs on remote computers, allowing synchronous or asynchronous communication of results, enabling remote execution and monitoring of jobs without the need for physical interaction or extensive programming.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual deployment of agents is used, then system control and configuration capability is maintained, but deployment time and cost increase significantly

Engineering Contradiction:
Improvedeployment speedVSAvoiddeployment process complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent uses template-based deployment files that contain pre-configured agent definitions, job configurations, and parameter specifications. These templates serve as reusable copies that can be instantiated multiple times across different target systems, eliminating the need for manual configuration each time and significantly speeding up deployment while maintaining consistency.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The deployment files are prepared in advance with all necessary agent configurations, job definitions, and parameter settings. This preliminary preparation allows the actual deployment process to simply involve transferring and executing the pre-configured files, rather than performing complex manual configuration during deployment, thus improving productivity without sacrificing control capability.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If dedicated application interface is used for job configuration, then configuration precision is improved, but system complexity and operation difficulty increase

Engineering Contradiction:
Improvejob configuration easeVSAvoidconfiguration interface complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The patent combines multiple configuration functions into a single integrated deployment file format. The deployment file simultaneously contains agent definitions, job configurations, parameter specifications, and execution instructions. This merging eliminates the need for separate dedicated interfaces for different configuration tasks, simplifying operation while maintaining precision through the structured file format.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The deployment file serves multiple functions: it defines agents, configures jobs, specifies parameters, and provides execution instructions. This universal configuration mechanism replaces the need for multiple specialized interfaces, making the system easier to operate while maintaining comprehensive control capability through the multi-functional file structure.

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

3Productivity

If separate agents are required for every task, then task specialization and precision are improved, but development complexity and time increase

Engineering Contradiction:
Improvedevelopment efficiencyVSAvoidagent functionality
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent segments the agent configuration into modular components within the deployment file: agent definitions, job configurations, parameter specifications, and execution instructions are all separate but interconnected elements. This segmentation allows individual tasks to be defined independently while maintaining the ability to combine them in various configurations, improving development efficiency without sacrificing adaptability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The deployment file structure allows dynamic configuration where agents can be defined once and then assigned to multiple different jobs and tasks through parameter specifications. This dynamic approach enables a single agent definition to serve multiple purposes through configuration variations, reducing development time while maintaining task specialization and adaptability.

Inventive Principle:
Principle #15Dynamics

4Ease of operation

If physical interaction with remote devices is required, then direct system access and control are maintained, but time consumption and operational cost increase

Engineering Contradiction:
Improveremote configuration easeVSAvoidconfiguration time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent replaces the mechanical process of physical interaction with remote devices (travel, manual connection, hands-on configuration) with an automated electronic file transfer and execution system. The deployment files are transferred electronically and executed automatically on target systems, substituting physical mechanical operations with automated digital processes, thereby eliminating time consumption and operational costs associated with physical presence while maintaining direct system access and control.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS9424016B2Methods, apparatuses, and systems relating to automation in distributed systems
Publication Date: 2016.08.23 AUTOMIC SOFTWARE
  • US9424016B2 patent drawing
  • US9424016B2 patent drawing
  • US9424016B2 patent drawing

AI summary

Apparatuses, systems and methods are presented. In one embodiment, the method includes receiving a graphical user interface part of a deployment file on a first computer, the deployment file configured to cause a second computer to perform a computer-implemented job. The method may also include loading the graphical user interface part of the deployment file on the first computer. Additionally, the method may include displaying an interactive graphical user interface on a display device in data communication with the first computer.