Application Launch Restriction via Intermediary Service
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for restricting the launch of third-party applications on smart terminals either compromise system stability or lack portability, and fail to prevent applications from being launched by other applications.
Innovation Solution
A method and terminal configuration that allows users to actively manage the launch state of applications through a software-based solution, prohibiting or allowing launches without modifying the platform code, by configuring the static broadcast, service, and content provider components of the application.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If the platform code of the operation system is modified to restrict application launch, then the launch of application can be restricted, but the stability of the operation system is reduced and maintenance difficulty increases
Solution Approach 1:
The patent introduces an intermediary component (application manager or system service) that acts as a mediator between applications and the core operating system platform. This intermediary handles launch restrictions through configuration files and policy enforcement without requiring modifications to the core platform code, thereby maintaining system stability while achieving the desired application launch control.
Solution Approach 2:
The patent segments the application launch control functionality into separate, modular components such as configuration files, policy engines, and service layers. This segmentation allows restriction logic to be isolated from the core operating system, enabling independent maintenance and updates without affecting overall system stability.
2Ease of operation
If the static broadcast component of the operation system is restricted to disable application launch, then the application can be disabled to be launched by itself, but the application can still be launched by other applications
Solution Approach 1:
The patent implements a universal launch control mechanism that simultaneously handles multiple launch scenarios (self-launch, other application launch, system launch) through a single policy enforcement system. The configuration and restriction logic applies universally across all launch vectors, ensuring comprehensive control without requiring separate mechanisms for each launch type.
Solution Approach 2:
The patent employs feedback mechanisms where the system continuously monitors application launch attempts and enforces restrictions based on predefined policies. The system provides feedback to the application manager about launch requests, which then determines whether to allow or block the launch based on the current restriction state and policy rules.
3Adaptability or versatility
If third-party applications are allowed to launch secretly in the back-end, then application functionality is available, but network traffic is wasted and memory occupation increases
Solution Approach 1:
The patent implements preliminary action by establishing application launch policies and restrictions before applications can secretly launch. The system pre-configures which applications are allowed to launch and under what conditions, preventing unauthorized or secret launches before they occur. This proactive approach blocks potential waste of network traffic and memory before resources are consumed.
Solution Approach 2:
The patent enables the operating system to self-monitor and self-regulate application launches through built-in policy enforcement mechanisms. The system automatically detects and prevents unauthorized application launches without requiring external intervention, thereby preventing waste of network traffic and memory resources while maintaining application functionality for authorized launches.
Data Source
AI summary
The present disclosure provides a terminal and a method for managing launch of an application of the terminal. The method includes: receiving a first indication from a user, wherein the first indication indicates that the launch of the application needs to be banned; in response to the first indication, setting the application to a launch-restricted state, wherein the launch-restricted state means that the application is prohibited from being launched by itself or by other applications; receiving a second indication from a user, wherein the second indication indicates that the launch-restricted state needs to be removed; and in response to the second indication, setting the application to a launch-allowable state, wherein the launch-allowable state means that the application is allowed to be launched by itself or by other applications.