Notification Permission Control for Background App Efficiency
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The increasing number of third-party applications on terminal devices self-starting in the background leads to reduced system operation efficiency and increased power consumption, with some applications secretly recording user data and waking up other apps, posing security risks.
Innovation Solution
A system notification service control method that detects application registration for notification permissions and prohibits unauthorized applications from registering by using whitelists and blacklists based on usage records and frequency analysis to determine if an application meets registration conditions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If applications are allowed to self-start in the background freely, then application functionality and user convenience are improved, but system operation efficiency deteriorates and power consumption increases
Solution Approach 1:
The system performs preliminary analysis during application installation to determine whether the application should be allowed to self-start. Usage records are collected and analyzed beforehand to establish a baseline of normal behavior, enabling the system to make authorization decisions before the application can cause harm. This preliminary action prevents unnecessary restrictions on legitimate applications while blocking potentially malicious ones.
Solution Approach 2:
The system continuously monitors application behavior and compares it against established usage records to detect anomalies. When suspicious behavior is detected, the system provides feedback by restricting the application's self-start capability. This feedback mechanism allows the system to adapt to new threats while maintaining functionality for legitimate applications, resolving the contradiction between operational freedom and system efficiency.
2Adaptability or versatility
If applications are allowed to access system notifications, then application notification functionality is improved, but security deteriorates due to potential data leakage and unauthorized access
Solution Approach 1:
The system applies different authorization levels to different applications based on their individual usage records and behavior patterns. Rather than a blanket restriction or permission approach, each application receives tailored authorization decisions. Legitimate applications with normal usage patterns receive full notification access, while applications exhibiting suspicious behavior are restricted, thus maintaining security without compromising the functionality of trusted applications.
Solution Approach 2:
The system introduces an intermediary authorization mechanism that sits between applications and system notifications. This intermediary layer analyzes application behavior against usage records and mediates access requests, allowing legitimate applications to access notifications while blocking potentially malicious ones. This intermediary resolves the security-functionality contradiction by providing intelligent, context-aware authorization.
3Loss of energy
If background application startup is restricted, then power consumption is reduced, but application responsiveness and user experience deteriorate
Solution Approach 1:
The system dynamically adjusts application startup restrictions based on real-time behavior analysis and usage records. Rather than static restrictions, the system continuously evaluates application behavior and modifies authorization decisions accordingly. This dynamic approach ensures that legitimate applications maintain responsiveness while preventing power-consuming background activity from malicious or unnecessary applications, resolving the contradiction between energy savings and user experience.
Data Source
Figure 1~2
Figure 3
Figure 4~5
AI summary
A system notification service control method, apparatus, a terminal device, and a storage medium are described. The system notification service control method may include detecting whether an application initiates a registration for a system notification reading permission; in response to detecting that the application initiates the registration for the system notification reading permission, determining whether the application meets a registration condition; and prohibiting the application from registering for the system notification reading permission when the application does not meet the registration condition.