Token Profile-Based Access Control for Group Data Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional systems fail to provide adequate mechanisms for controlling access to token data across multiple groups stored in a single database, leading to unintended access by administrators of one group to data from other groups.

Innovation Solution

Implementing a token processing system with per-group role-based access control and profile-based access control modules, which assign token profiles to users specifying predefined roles, allowing access to token data based on group membership and role privileges, thereby controlling access at a group level.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If all token data for multiple groups are stored within a single database, then data management is simplified, but access control security deteriorates as administrators of one group can access data from other groups

Engineering Contradiction:
Improvedata management complexityVSAvoidaccess control security
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent segments the database structure by introducing group-specific schemas or partitions within the single database. Each group's token data is organized in separate logical units with unique identifiers, allowing the system to maintain a unified database while enforcing group-level access boundaries. This segmentation enables simplified centralized management while preventing cross-group unauthorized access.

Inventive Principle:
Principle #1Segmentation

2Quantity of substance

If conventional single database storage is used for multiple token groups, then storage efficiency is improved, but access control granularity deteriorates to group level

Engineering Contradiction:
Improvestorage efficiencyVSAvoidaccess control granularity
Core Design Contradiction:
Quantity of substanceVSAdaptability or versatility

Solution Approach 1:

The patent applies local quality by assigning different access control attributes and permissions to different groups within the same database. Each group can have customized access policies, administrator roles, and permission sets tailored to its specific security requirements. This allows the system to maintain efficient single-database storage while providing granular, group-specific access control capabilities.

Inventive Principle:
Principle #3Local quality

3Ease of operation

If administrators of different groups share the same database, then system simplicity is improved, but access control precision deteriorates allowing incidental access to other groups' data

Engineering Contradiction:
Improvesystem simplicityVSAvoidaccess control precision
Core Design Contradiction:
Ease of operationVSMeasurement precision

Solution Approach 1:

The patent introduces an intermediary access control layer between administrators and the token data. This intermediary mechanism includes group context validation, permission verification, and access logging that automatically enforces group boundaries. The system maintains simplicity by keeping a single database but adds this intermediary control plane that precisely manages which administrators can access which group's data based on their assigned roles and permissions.

Inventive Principle:
Principle #24Intermediary (Mediator)

Data Source

PatentUS8387137B2Role-based access control utilizing token profiles having predefined roles
Publication Date: 2013.02.26 RED HAT INC
  • US8387137B2 patent drawing
  • US8387137B2 patent drawing
  • US8387137B2 patent drawing

AI summary

A method and system for managing role-based access control of token data using token profiles having predefined roles is described. In one method, a token processing system (TPS) assigns a TPS client a token profile for a group of multiple tokens, the token profile being stored in a profile data structure. The token profile specifies at least one of multiple predefined roles for the TPS client, each role associated with predefined access to entries of a token database. The TPS receives a request from the TPS client over a network to perform an operation on the entries of the token database that correspond to the group, and allows the TPS client access to the token database to perform the operation when permitted by the predefined roles specified in the token profile on the entries of the token database that correspond to the group identified by the token profile.