API Permission Categorization and Real-Time Control
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Users of intelligent devices face challenges in controlling application programming interface (API) invocations, leading to privacy violations and reduced security due to lack of granular control over information access, as users often agree to broad permission lists without understanding the implications.
Innovation Solution
Categorizing APIs based on the type of user information they access and setting default permissions for each category, with real-time monitoring and user prompts for specific permissions, allowing users to control API invocations based on access, prohibition, or prompt permissions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of information
If users are presented with a comprehensive invoking permission list during application installation, then user awareness of information access is improved, but user experience deteriorates due to complexity and user neglect of the permission list
Solution Approach 1:
The patent segments the comprehensive permission list into individual permission items that are presented separately to the user during installation. Instead of showing all permissions at once, the system divides them into manageable units, allowing users to review and understand each permission's purpose before granting access. This segmentation reduces the cognitive load and improves user awareness without overwhelming them.
Solution Approach 2:
The patent performs preliminary actions by pre-analyzing and categorizing permissions before presentation to the user. The system prepares the permission information in advance, organizing it by type and importance, so that users receive structured, easy-to-understand information during installation. This preliminary organization reduces complexity and helps users make informed decisions.
2Reliability
If users are given granular control over each API permission, then security is improved by preventing malicious data access, but device complexity increases due to detailed permission management
Solution Approach 1:
The patent segments API permissions into distinct categories and individual items, allowing the system to manage and control each permission separately. This segmentation enables fine-grained security control where each permission can be independently granted, revoked, or monitored, preventing malicious applications from obtaining excessive access while maintaining manageable complexity through structured organization.
Solution Approach 2:
The patent introduces an intermediary permission management system that mediates between applications and the operating system's API access controls. This intermediary layer provides a standardized interface for permission requests, automatically analyzes permission necessity, and enforces security policies, thereby improving security without requiring complex manual configuration by users or developers.
3Ease of operation
If comprehensive permission lists are presented during installation, then user control over information access is improved, but users neglect the permission list leading to malicious information access
Solution Approach 1:
The patent performs preliminary analysis of permission requirements before presenting them to users during installation. The system pre-evaluates which permissions are necessary for the application's core functions and presents only those relevant permissions to users, rather than showing all possible permissions. This preliminary filtering helps users understand and control information access without being overwhelmed, reducing neglect and malicious access risks.
Solution Approach 2:
The patent implements feedback mechanisms that provide users with information about what each permission enables and how it will be used. The system offers explanatory feedback about permission purposes, usage contexts, and potential risks, allowing users to make informed decisions. This feedback loop improves user awareness and control while preventing malicious access through educated user choices.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A computer-implemented method for controlling invocation of application programming interface (API) is provided. The method includes categorizing a plurality of APIs according to a plurality of API categories. The API categories are categorized by an API function through which user information is obtained. The method further includes setting a default invoking permission for a respective API category, and detecting, in real time, an attempt by an application to invoke an API in the respective API category. Upon detecting the attempted invocation of the API in the API category by the application, the method further includes controlling the invoking behavior of the API by the application in accordance with the default invoking permission for the API category.