Token-Based Permission Control for Application Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing electronic devices face issues with applications being granted excessive permissions, leading to potential leaks of personal information and unauthorized data collection, and there is a need to regulate applications that misuse permissions.

Innovation Solution

An electronic device installs applications using an installation file that includes a permission setting token, which defines the permissions allowed, and stores this information in a database for future reference, allowing for more precise control over system resource access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If key signing is used to verify application integrity, then application security is improved, but applications are granted too much permission than needed

Engineering Contradiction:
Improveapplication securityVSAvoidexcessive permission
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the permission granting process into two independent parts: key signing for integrity verification and permission setting tokens for permission control. This segmentation allows each mechanism to focus on its specific function without interfering with the other, resolving the contradiction between security verification and permission minimization.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a permission setting token as an intermediary element between the installation file and the permission system. This token acts as a mediator that carries explicit permission information, enabling the system to grant only the necessary permissions while maintaining security through the key signing process.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If traditional permission systems are used, then application installation is simple, but it is difficult to interrupt once-given permission

Engineering Contradiction:
Improveinstallation simplicityVSAvoidpermission interruption
Core Design Contradiction:
Ease of operationVSEase of repair

Solution Approach 1:

The patent applies preliminary action by embedding the permission setting token within the installation file before installation. This allows the permission configuration to be established in advance during installation, and the same token structure enables future permission interruption by simply removing or invalidating the token without complicating the installation process.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If applications are granted broad permissions, then application functionality is improved, but personal information leakage risk increases

Engineering Contradiction:
Improveapplication functionalityVSAvoidinformation leakage risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent applies local quality by assigning specific, targeted permissions to each application through the permission setting token rather than granting broad universal permissions. Each token contains precise permission information tailored to the application's actual needs, enabling the system to maintain application functionality while minimizing information leakage risks through granular permission control.

Inventive Principle:
Principle #3Local quality

Data Source

PatentEP3809297B1Token-based scheme for granting permissions
Publication Date: 2026.03.11 SAMSUNG ELECTRONICS CO LTD
  • EP3809297B1 patent drawingFigure 1
  • EP3809297B1 patent drawingFigure 2
  • EP3809297B1 patent drawingFigure 3

AI summary

An electronic device comprising: a communication interface configured to perform a wireless communication with an external electronic device or a server; a memory; and at least one processor operatively coupled with the communication interface and the memory, and configured to: install an application by using an installation file associated with the application which is preloaded or downloaded from the external electronic device or the server; grant at least one permission to the application based on a key signing which is included in the installation file; detect whether the installation file includes a permission setting token; if the installation file includes the permission setting token, identify at least one permission associated with the permission setting token, wherein the permission setting token, which is independent of the key signing, is data that defines a permission range for the application to access resources of the electronic device; grant the at least one permission to the application based on the permission setting token; and store, in the memory, the at least one permission which is granted to the application using the permission setting token.