Hierarchical Application Configuration for Unified Multi-App Deployment

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current software systems require manual configuration of multiple applications, leading to low efficiency and high development costs due to the need for individual installers and scripts for each application.

Innovation Solution

Establishing hierarchical relationships between structural data models and configuration information of applications to create a tree-like structure, allowing unified deployment and management of multiple applications without the need for individual installers or scripts.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual configuration is performed for each application individually, then each application can be configured independently, but the configuration efficiency is low and development costs are high

Engineering Contradiction:
Improveconfiguration efficiencyVSAvoidsystem complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The patent merges multiple application configurations into a unified hierarchical structure where a parent application can manage multiple child applications. This allows simultaneous configuration of multiple applications through a single parent configuration interface, dramatically improving configuration efficiency while reducing the need for individual installers and scripts for each application.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The parent application structure serves multiple functions: it acts as a container for child applications, provides unified configuration management, handles deployment coordination, and enables centralized control. This multi-functional design eliminates the need for separate management mechanisms for each application, reducing development costs and complexity.

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

2Ease of manufacture

If individual installers and scripts are created for each application, then each application can be deployed independently, but development costs increase and configuration efficiency decreases

Engineering Contradiction:
Improvedeployment easeVSAvoidconfiguration efficiency
Core Design Contradiction:
Ease of manufactureVSProductivity

Solution Approach 1:

Multiple application installers and deployment scripts are merged into a single parent application installer. The parent application's installation package automatically coordinates the installation of all child applications, providing unified deployment capability while eliminating the need for separate installers and scripts for each application.

Inventive Principle:
Principle #5Merging (Combining)

3Adaptability or versatility

If manual configuration is performed for each application, then configuration flexibility is maintained, but time consumption increases

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidconfiguration time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The parent application structure pre-establishes a hierarchical framework that automatically organizes and manages child applications. This preliminary structural setup enables bulk configuration operations, where configurations can be applied to multiple applications simultaneously through the parent interface, significantly reducing configuration time while maintaining flexibility through the hierarchical structure.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20250383868A1Application management method, application subscription method, and related device
Publication Date: 2025.12.18 BEIJING WELLINTECH CO LTD
  • US20250383868A1 patent drawing
  • US20250383868A1 patent drawing
  • US20250383868A1 patent drawing

AI summary

The present disclosure relates to an application management method, an application subscription method and a related device. In the present disclosure, a structural data model of a first application and a structural data model of a second application are constructed, and a hierarchical relationship between the structural data model of the first application and the structural data model of the second application is established.