Web Permission Extension via Native App Metadata

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Native applications on computing devices often require users to grant redundant permissions for location information and other device access when visiting corresponding websites, leading to a negative user experience due to the lack of permission extension from the native application to the website.

Innovation Solution

A system that accesses a website's metadata to obtain a unique identifier of a native application, determines if the application is installed and permissions are set, and verifies if the native application corresponds to the website, allowing for automatic permission setting for the website upon verification.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If permission requests are made for each website separately, then security control is improved, but user experience deteriorates due to redundant permission requests

Engineering Contradiction:
Improvesecurity controlVSAvoiduser experience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The system performs preliminary permission granting when the native application is installed or updated. The permission dialog is displayed during application installation, and once granted, the permission is automatically extended to the corresponding website without requiring separate user action. This preliminary action eliminates redundant permission requests while maintaining security control.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent merges the permission granting process for native applications with the corresponding website permissions. Instead of treating them as separate entities requiring separate permissions, the system combines them into a single permission grant operation. When a user grants permission to a native application, the same permission is automatically applied to its associated website, reducing redundancy while maintaining security.

Inventive Principle:
Principle #5Merging (Combining)

2Ease of operation

If permission extension from native application to website is implemented, then user experience is improved, but system complexity increases

Engineering Contradiction:
Improveuser experienceVSAvoidsystem complexity
Core Design Contradiction:
Ease of operationVSDevice complexity

Solution Approach 1:

The system introduces a website configuration file as an intermediary that contains a unique identifier linking the website to its corresponding native application. This intermediary enables the automatic association between websites and applications without requiring complex direct mapping logic. The configuration file acts as a simple bridge that reduces overall system complexity while enabling permission extension.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system copies the permission settings from the native application to the corresponding website. Instead of implementing a complex permission management system for websites from scratch, the patent simply replicates the permission state from the native application to the website context. This copying approach maintains consistency while avoiding the need for separate permission management infrastructure.

Inventive Principle:
Principle #26Copying

3Productivity

If automatic permission setting is implemented, then productivity is improved by eliminating redundant requests, but reliability may worsen due to potential permission mismatches

Engineering Contradiction:
ImproveefficiencyVSAvoidpermission accuracy
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback mechanisms to verify that the native application and website are properly associated before extending permissions. The website configuration file provides a unique identifier that serves as feedback to confirm the correct mapping between application and website. This feedback loop ensures permission accuracy while maintaining the efficiency of automatic permission setting.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system performs preliminary verification to ensure the native application and website are correctly associated before automatically extending permissions. By checking the unique identifier in the website configuration file against the application identity beforehand, the system ensures permission accuracy is maintained while still achieving the productivity benefits of automatic permission setting.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentEP3123386B1Granting permission in association with an application
Publication Date: 2021.09.29 GOOGLE LLC
  • EP3123386B1 patent drawingFigure 1
  • EP3123386B1 patent drawingFigure 2
  • EP3123386B1 patent drawingFigure 3

AI summary

A system and method are provided for granting permission in association with an application, the method comprising accessing a website on an application running on an electronic device, the website comprising metadata, obtaining, from the metadata, a unique identifier of a native application, determining, based on the obtained unique identifier, that the native application is installed on the electronic device and that a permission is set in the native application, verifying, in response to the determination, that the native application corresponds to the website, and setting, in response to the verification, the permission for the website, wherein both the application and the native application allow for setting of the permission.