Blockchain Access Control via Role-Based Token Overlay

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional blockchain technologies lack granular control over operations and are too rigid for handling human errors and malicious users due to their immutable nature, failing to provide traceable and flexible access management.

Innovation Solution

Integration of a role-based access control (RBAC) framework with chain-based authorization, where authorization tokens are stored on the blockchain, allowing for granular governance, reduced authentication time, and scalability by managing credentials and authorizations locally within the blockchain.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional blockchain immutability is maintained, then data integrity is preserved, but flexibility and granular control over operations are lost

Engineering Contradiction:
Improvedata integrityVSAvoidflexibility and granular control
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent segments the blockchain system into multiple layers: the underlying immutable blockchain ledger and an overlay access control system. The access control system is divided into roles, permissions, and authorization tokens that can be independently managed. This segmentation allows the immutable blockchain to maintain data integrity while the overlay system provides flexible, granular control over operations without altering the core blockchain structure.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces an intermediary access control system that sits between users and the blockchain operations. This intermediary layer uses authorization tokens and role-based access control to mediate all interactions with the blockchain, allowing flexible permission management while the underlying blockchain remains immutable and maintains its data integrity guarantees.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If blockchain immutability is enforced, then security against tampering is improved, but the system becomes too rigid to handle human errors and malicious users

Engineering Contradiction:
Improvesecurity against tamperingVSAvoidability to handle errors and malicious behavior
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The patent implements preliminary anti-action by establishing an access control system that prevents unauthorized or malicious operations before they can affect the blockchain. Authorization tokens are validated and permissions are checked in advance, blocking potential harmful actions while allowing legitimate operations to proceed, thus maintaining security without the rigidity of complete immutability.

Inventive Principle:
Principle #9Preliminary anti-action

Solution Approach 2:

The patent introduces dynamics into the blockchain system through the access control layer, which can adapt permissions and authorizations based on user behavior, roles, and conditions. This dynamic system can respond to errors and malicious behavior by adjusting access rights in real-time, while the underlying blockchain maintains its immutable security guarantees.

Inventive Principle:
Principle #15Dynamics

3Ease of operation

If external authentication systems are used, then centralized control is achieved, but authentication time and vulnerability to external attacks increase

Engineering Contradiction:
Improvecentralized controlVSAvoidauthentication time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The patent implements self-service by enabling nodes to perform local authentication using authorization tokens stored on the blockchain itself. Instead of relying on external authentication systems, the blockchain network autonomously validates access requests against the distributed ledger, eliminating external communication delays and reducing vulnerability to external attacks while maintaining centralized control through the token-based permission system.

Inventive Principle:
Principle #25Self-service

4Adaptability or versatility

If access control logic is stored externally, then flexibility in managing credentials is improved, but security and authentication reliability decrease

Engineering Contradiction:
Improveflexibility in credential managementVSAvoidsecurity and authentication reliability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The patent merges the access control logic and authorization tokens directly with the blockchain structure. Permission data is embedded in the blockchain transactions and blocks, combining the flexibility of programmable access control with the security and reliability of the immutable blockchain ledger. This integration ensures that credential management remains flexible while authentication reliability is maintained through cryptographic verification on the distributed ledger.

Inventive Principle:
Principle #5Merging (Combining)

Data Source

PatentUS11201746B2Blockchain access control system
Publication Date: 2021.12.14 ACCENTURE GLOBAL SOLUTIONS LTD
  • US11201746B2 patent drawing
  • US11201746B2 patent drawing
  • US11201746B2 patent drawing

AI summary

A system may receive a credential token and an access command. The access command may identify access logic to modify a datablock stored in a blockchain. The credential token may be mapped to a role token included in a role-based access control model. The system may determine a role-based access control framework authorizes the access command by identifying an authorization token in the role-based access control model, and the system may determine the role token is mapped to the identified authorization token in the role-based access control model. The system may determine the datablock includes the identified authorization token. The system may validate the identified authorization token. The system may authorize execution of the access logic to modify the datablock in response to the access command being authorized by the role-based access control framework, and validation of the identified authorization token included in the datablock.