Semi-rule Permission Management via User Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current user permission management systems face inefficiencies and increased complexity as the number of users and permission types grow, leading to slow processing speeds and high computational demands, especially in batch operations where numerous target users are involved.

Innovation Solution

A semi-rule based permission management system that generates an attribute table with user metadata, filters out irrelevant users, and applies permission rules to a reduced set of users, leveraging existing user attributes to streamline permission determination and reduce processing power requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Speed

If a traditional permission management system processes all target users through complex permission rules, then permission determination accuracy is maintained, but processing speed and computational efficiency deteriorate

Engineering Contradiction:
Improveprocessing speedVSAvoidsystem complexity
Core Design Contradiction:
SpeedVSDevice complexity

Solution Approach 1:

The patent segments the user base into two distinct groups: high-value users who require full permission rule processing and low-value users who use simplified permission rules. This segmentation is achieved through user tagging and classification mechanisms that divide the originally monolithic user set into manageable subsets, allowing different processing paths for different user segments thereby improving overall processing speed while maintaining accuracy for critical users.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent applies partial action by using simplified permission rule processing for low-value users instead of applying the complete, complex permission rule set to all users. This partial processing approach reduces computational overhead for users who don't require full permission verification, while still maintaining adequate permission control. The system performs only the necessary level of processing for each user category rather than excessive full processing for everyone.

Inventive Principle:
Principle #16Partial or excessive action

2Reliability

If permission rules are applied to all target users in batch operations, then comprehensive permission control is achieved, but computational resources and processing time increase significantly

Engineering Contradiction:
Improvepermission control accuracyVSAvoidcomputational resources
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent segments users into high-value and low-value categories based on their importance to the organization, then applies different processing resource allocations to each segment. High-value users receive comprehensive permission verification using the full permission rule set, while low-value users receive streamlined processing. This segmentation allows the system to concentrate computational resources on users where accurate permission control is most critical, thereby maintaining reliability for important operations while reducing overall computational resource consumption.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements local quality by applying different levels of permission processing quality to different user groups. High-value users receive high-quality, thorough permission verification with complete rule evaluation, while low-value users receive standard-quality processing with simplified rules. This localized quality adjustment ensures that computational resources are optimized according to the actual needs of different user segments, maintaining high reliability where necessary while reducing resource usage elsewhere.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If the number of users and permission types increases in an organization, then system functionality and adaptability improve, but processing efficiency and speed deteriorate

Engineering Contradiction:
Improvesystem adaptabilityVSAvoidprocessing efficiency
Core Design Contradiction:
Adaptability or versatilityVSProductivity

Solution Approach 1:

The patent addresses the scalability problem by segmenting the user population and applying differentiated processing strategies. As the organization grows with more users and permission types, the system automatically classifies users into segments and applies appropriate processing levels. This allows the system to adapt to increasing complexity while maintaining processing efficiency, because the segmentation approach prevents the entire system from being bottlenecked by the most complex cases.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses partial action to maintain processing efficiency as the system scales. Instead of applying full permission rule processing to all users regardless of their actual needs, the system applies simplified processing to low-value users and full processing only to high-value users. This partial processing approach allows the system to handle larger numbers of users and more permission types without proportionally increasing processing time and resource consumption, thereby maintaining productivity as adaptability increases.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS11188661B2Semi-rule based high performance permission management
Publication Date: 2021.11.30 SAP SE
  • US11188661B2 patent drawing
  • US11188661B2 patent drawing
  • US11188661B2 patent drawing

AI summary

Described herein includes a permission management system that optimizes determination of whether a user has permission to perform an operation using an attribute table. The system may include a permission processor for: determining whether the requesting user has permission to perform the operation, the determining including: generating an attribute table comprising the one or more target users and one or more user attributes, the one or more user attributes comprising metadata associated with the one or more target users; storing the attribute table on the database; generating a reduced attribute table, the generating comprising removing one or more target users from the attribute table; and applying the one or more permission rules to each of the target users remaining in the reduced attribute table.