App Jump Permission Control for Mobile Security
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Electronic devices face security risks due to random app jumping, which can be exploited by malicious programs or advertisements, as existing static rules are inadequate for managing app interactions, especially when the target app is not pre-installed.
Innovation Solution
An application management and control method that determines management and control conditions based on application information of caller and callee applications, prompting users for permission before app jumping and allowing or forbidding the action based on predefined rules, reducing the risk of unauthorized app transitions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If app jumping is allowed without restrictions, then user convenience and app functionality are improved, but security risks increase due to malicious programs and advertisements
Solution Approach 1:
The patent implements dynamic permission management where the system adapts app jumping behavior based on real-time conditions. Different permission levels (allow, forbid, prompt) are applied dynamically depending on the target app's installation status, user history, and current context, rather than using static restrictions. This resolves the contradiction by making the system flexible enough to maintain convenience for legitimate jumps while blocking malicious ones.
Solution Approach 2:
The patent introduces a permission management module as an intermediary between the user interface and app execution system. This mediator intercepts app jumping requests, evaluates them against security criteria, and either permits or blocks the transition. The intermediary layer filters out malicious jumps while allowing legitimate ones, thus protecting security without completely restricting app functionality.
2Device complexity
If static rules are used to manage app jumping, then security control is simplified, but adaptability to different scenarios and uninstalled apps is reduced
Solution Approach 1:
The system transitions from static permission rules to dynamic evaluation that considers multiple factors including whether the target app is installed, user interaction history, app source credibility, and current device state. This dynamic approach enables the system to adapt to diverse scenarios automatically without requiring complex manual configuration for each case.
Solution Approach 2:
The patent implements self-service mechanisms where the system automatically evaluates and makes permission decisions based on pre-defined criteria and contextual information. The permission management module autonomously determines whether to allow or block app jumps without requiring continuous user intervention or complex administrative configuration, achieving both simplicity and adaptability.
3Object-affected harmful factors
If permission prompts are displayed for every app jump, then security control is improved, but user experience and operation efficiency deteriorate
Solution Approach 1:
The patent applies permission prompts selectively rather than universally. High-risk jumps (to uninstalled apps, from untrusted sources, or matching malicious patterns) trigger permission prompts, while low-risk jumps (to pre-approved apps or trusted sources) are automatically permitted without user interaction. This partial application of permission requests maintains security for critical cases while preserving user experience for routine operations.
Solution Approach 2:
Different permission management strategies are applied to different app jumping scenarios based on their risk characteristics. The system evaluates each jump context locally and applies appropriate control measures: strict verification for high-risk cases, automatic permission for low-risk cases, and selective prompting for intermediate cases. This localized quality approach optimizes both security and user experience for each specific scenario.
Data Source
Figure 1A(a)
Figure 1A(b)
Figure 1B(a)
AI summary
Embodiments of this application provide an application management and control method and an electronic device. The electronic device stores a correspondence between at least one management and control condition and a management and control result, and each management and control condition corresponds to one management and control result. In the method, when receiving a first trigger operation entered by a user in a first interface, the electronic device may determine a first management and control condition based on first application information corresponding to a first application and/or second application information corresponding to a second application. The first trigger operation indicates to jump to and display a second interface. The first interface corresponds to the first application, the second interface corresponds to the second application, and the first application is different from the second application. The electronic device may execute a corresponding response based on a management and control result corresponding to the first management and control condition, to determine whether to jump to and display the second interface. This can reduce a quantity of times that the electronic device is attacked due to app jumping, and improve security.