Privacy Metadata for Application Permission Granularity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Software developers lack a mechanism to inform users about the specific data needed and obtain meaningful permissions for data collection, as existing platforms use broad predefined categories that may deter users from installing applications.

Innovation Solution

Implementing methods for application developers to receive and store user permissions and associated information, providing users with a detailed interface to grant consents for specific application functions, and ensuring that applications are only installed after necessary consents are obtained.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If broad predefined permission categories are used, then application development is simplified, but user trust and installation rates decrease due to lack of transparency

Engineering Contradiction:
Improveease of application developmentVSAvoidinformation transparency to users
Core Design Contradiction:
Ease of manufactureVSLoss of information

Solution Approach 1:

The patent segments broad permission categories into fine-grained, specific permission items. Instead of presenting users with a single broad category like 'Access all of your data on the web,' the system breaks it down into specific data types (e.g., screenshots, location, contacts) that the application actually needs. This segmentation allows developers to maintain simplified development processes while providing users with transparent, detailed information about specific data usage purposes.

Inventive Principle:
Principle #1Segmentation

2Reliability

If detailed permission information is provided to users, then user trust and informed consent improve, but application complexity and development effort increase

Engineering Contradiction:
Improveuser consent validityVSAvoidpermission management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal permission metadata structure that serves multiple functions: it provides detailed information to users, enables automated permission management, supports various consent scenarios, and maintains compatibility with existing application frameworks. This multi-functional approach allows detailed permission tracking without proportionally increasing complexity, as the same metadata structure handles diverse permission scenarios.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces permission metadata as an intermediary layer between the application code and the user interface. This metadata structure automatically bridges the gap between technical permission requirements and user-friendly presentations, reducing the burden on developers to manually create detailed permission interfaces while still providing comprehensive information to users.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Manufacturing precision

If fine-grained permission tracking is implemented, then data usage control and compliance improve, but processing overhead and system resource usage increase

Engineering Contradiction:
Improvepermission granularityVSAvoidsystem processing energy
Core Design Contradiction:
Manufacturing precisionVSUse of energy by moving object

Solution Approach 1:

The patent performs permission segmentation and metadata generation in advance during application compilation or submission, rather than in real-time during execution. By pre-processing permission information and organizing it into structured metadata, the system reduces the computational burden during runtime, allowing fine-grained permission tracking with minimal additional processing energy consumption.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS9230134B1Privacy setting metadata for application developers
Publication Date: 2016.01.05 GOOGLE LLC
  • US9230134B1 patent drawing
  • US9230134B1 patent drawing
  • US9230134B1 patent drawing

AI summary

Privacy setting metadata for application developers is described, including receiving, from a user, a request to submit an application; requesting, from the user, identification of one or more permissions and information associated with the one or more permissions; receiving the application, the one or more permissions, and the information associated with the one or more permissions, wherein the one or more permissions are associated with one or more functions of the application; storing the application, the permissions, and the information associated with the permissions; receiving a request to install the application to a device of another user; providing the application, the one or more permissions, and the information associated with the one or more permissions to the device; and receiving, from the device, one or more consents to the one or more permissions, the one or more consents indicate activation of the one or more functions of the application.