Resource Permission Requests Based on Usage Data

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing resource access permission systems often result in applications being granted permissions for resources they do not actually use, leading to unnecessary permission requests and potential installation failures due to user reluctance or developer errors.

Innovation Solution

A communication system that includes an electronic device, an application server, and a usage information server, which generates resource permission requests based on actual resource usage data, allowing users to make informed decisions by providing usage information for each resource listed in the permission request.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If applications are granted permissions for all resources listed in the installation manifest, then the application can access all potentially needed resources, but users may be reluctant to grant permissions for resources the application does not actually use, leading to installation failures

Engineering Contradiction:
Improveinstallation success rateVSAvoiduser willingness to grant permissions
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary analysis of resource usage by executing the application in a controlled environment before the actual installation. This preliminary action identifies which resources the application actually uses, allowing the permission request to be customized with only the necessary resources, thereby increasing user willingness to grant permissions while ensuring installation success

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements a feedback loop where resource usage data collected from preliminary execution is used to inform the permission request generation. This feedback mechanism ensures that only resources actually used by the application are included in the permission request, aligning the requested permissions with actual needs and improving both installation reliability and user confidence

Inventive Principle:
Principle #23Feedback

2Adaptability or versatility

If the installation manifest includes all possible resources an application might access, then the application has maximum flexibility, but the permission request becomes less meaningful and users cannot make informed decisions

Engineering Contradiction:
Improveapplication resource access flexibilityVSAvoidinformation about actual resource usage
Core Design Contradiction:
Adaptability or versatilityVSLoss of information

Solution Approach 1:

The system extracts only the specific resources that the application actually uses from the complete installation manifest. By separating and selecting only the necessary resources based on preliminary execution analysis, the system maintains application flexibility while providing users with precise information about actual resource usage, enabling informed permission decisions

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The system applies local quality by customizing the permission request for each application based on its specific resource usage patterns. Instead of a generic approach for all applications, the system tailors the permission request to include only the resources relevant to that specific application, providing localized and meaningful information to users

Inventive Principle:
Principle #3Local quality

3Reliability

If developers include resources in the installation manifest to avoid future permission issues, then permission problems are prevented, but unnecessary permissions are granted for resources not actually used

Engineering Contradiction:
Improvepermission access reliabilityVSAvoidwasted permission grants
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The system performs preliminary resource usage analysis before finalizing permission requests, allowing it to distinguish between resources that are actually needed and those that are merely listed for precaution. This preliminary action prevents the waste of granting unnecessary permissions while ensuring that truly needed resources are included, optimizing both reliability and resource efficiency

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS10489134B2Requesting resource access permissions
Publication Date: 2019.11.26 MALIKIE INNOVATIONS LTD
  • US10489134B2 patent drawing
  • US10489134B2 patent drawing

AI summary

Systems, methods, and software can be used to share content. In some aspects, the electronic device receives an installation manifest for an application. The installation manifest indicates one or more resources on the electronic device that the application is configured to access. The electronic device receives resource usage information associated with the application. The resource usage information indicates how often the application uses at least one resources. A resource permission request for the application is outputted on the electronic device based on the installation manifest and the resource usage information.