Automated Application Permission Establishment via Table Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current data permission systems in data centers rely on manual reviews, leading to increased time expenditure and potential data security risks due to inefficiencies and lack of automation.

Innovation Solution

An automated and systematic application permission establishment method and system that utilizes a computing device to request, determine, and obtain permissions from a permission table, with a review process for non-existent permissions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual review is used to establish data permissions, then data security can be maintained through human oversight, but time expenditure increases and productivity decreases

Engineering Contradiction:
Improvedata securityVSAvoidpermission establishment efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The permission establishment process is segmented into automated verification (checking against permission table) and manual review (for non-existent permissions), allowing routine operations to be automated while maintaining human oversight for exceptional cases

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system enables self-service permission establishment by automatically verifying requests against the permission table, allowing the system to handle routine permission grants without human intervention and freeing personnel for higher-value tasks

Inventive Principle:
Principle #25Self-service

2Reliability

If manual review processes are implemented for permission management, then potential security risks can be identified, but the complexity of the system increases and automation level decreases

Engineering Contradiction:
Improvesecurity risk detectionVSAvoidpermission establishment automation
Core Design Contradiction:
ReliabilityVSExtent of automation

Solution Approach 1:

The system segments permission management into automated routine verification and manual review for non-standard cases, achieving both automation and security oversight without requiring full manual processing

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The permission table acts as an intermediary data structure that enables automated verification, serving as a bridge between automated systems and security requirements by encoding approved permissions in advance

Inventive Principle:
Principle #24Intermediary (Mediator)

3Productivity

If automated permission granting is implemented, then productivity increases and time expenditure decreases, but system complexity increases

Engineering Contradiction:
Improvepermission establishment speedVSAvoidsystem structure complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The permission table is prepared in advance with pre-defined valid permissions, allowing the automated system to simply verify requests against this predetermined structure rather than making complex security decisions in real-time

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system uses a simplified permission table structure that copies and stores approved permission configurations, allowing automated verification to proceed with simple data matching rather than complex security policy evaluation

Inventive Principle:
Principle #26Copying

Data Source

PatentUS20250165652A1Application permission establishment method and application permission establishment system
Publication Date: 2025.05.22 INVENTEC PUDONG TECH CORPOARTION
  • US20250165652A1 patent drawing
  • US20250165652A1 patent drawing
  • US20250165652A1 patent drawing

AI summary

A method of establishing application permissions includes utilizing a computing device to execute the following steps: requesting a first permission; determining whether the first permission exists in a plurality of application permissions in a permission table; obtaining the first permission when the first permission exists in the plurality of application permissions in the permission table; and reviewing the first permission when the first permission does not exist in the plurality of application permissions in the permission table.