Multi-Module Software Installation with Continuous Administrator Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In some operating systems, installing multiple functional modules in a program requires multiple password inputs, increasing operation complexity and reducing user experience.

Innovation Solution

An installation method that executes a first command to run a second startup program with administrator permission, allowing subsequent installation modules to be executed without repeated password prompts, using a combination of commands to maintain administrator access throughout the process.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If multiple installation modules are installed in one program installation process, then installation efficiency is improved, but multiple password input requests pop up, increasing operation complexity

Engineering Contradiction:
Improveinstallation efficiencyVSAvoidoperation complexity
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent applies preliminary action by obtaining administrator permission before the installation process begins and maintaining this permission state throughout the entire multi-module installation. The first startup program acquires administrator rights upfront, and subsequent installation modules execute within this established permission context, preventing repeated password prompts and simplifying user operations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If administrator permission is obtained for each installation module, then installation security is improved, but multiple password input requests increase operation complexity

Engineering Contradiction:
Improveinstallation securityVSAvoidoperation complexity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent implements continuity of useful action by maintaining the administrator permission state continuously throughout the entire installation process. Instead of repeatedly obtaining and losing permission, the system establishes a continuous administrator context that persists across all installation modules, ensuring both security and operational simplicity.

Inventive Principle:
Principle #20Continuity of useful action

Solution Approach 2:

The patent merges multiple separate permission acquisition operations into a single unified permission establishment. By combining all installation modules under one continuous administrator session, the system eliminates the need for separate password inputs for each module while maintaining security through the unified permission framework.

Inventive Principle:
Principle #5Merging (Combining)

3Device complexity

If a single startup program is used for installation, then device complexity is reduced, but repeated password prompts reduce user experience

Engineering Contradiction:
Improveprogram structure complexityVSAvoiduser experience
Core Design Contradiction:
Device complexityVSEase of operation

Solution Approach 1:

The patent applies segmentation by dividing the installation system into distinct functional components: a first startup program responsible for initial permission acquisition, and multiple installation modules that execute within the established permission context. This segmentation allows the single startup program to maintain simplicity while internally managing the complex permission state required for seamless multi-module installation.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS12430113B2Installation method needless of multiple requests for permissions, electronic device, and computer readable storage medium
Publication Date: 2025.09.30 ZHUHAI PANTUM ELECTRONICS CO LTD
  • US12430113B2 patent drawing
  • US12430113B2 patent drawing
  • US12430113B2 patent drawing

AI summary

An installation method needless of multiple requests for permissions includes executing a first command after a first startup program is run under a non-administrator permission, and starting at least one installation module through a second command after a second startup program is run. The first command is configured to run the second startup program with an administrator permission, and the second command is configured to execute the startup programs with the administrator permission.