Field-Based Peer Permissions in Blockchain Networks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Blockchain architectures lack secrecy between peers and effective enforcement of access permissions, as each piece of information in a block is visible to all peers, and permissions/privileges are uniform across the network, failing to provide secure and controlled data management in multi-tenant environments.

Innovation Solution

A multi-tenant server manages a peer-to-peer blockchain network by generating public and private keys for each tenant system, encrypting exchange fields based on permission levels, and using these keys to enforce permissions, allowing selective data sharing and secure data management through separate virtual spaces and blockchain services.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If blockchain architecture uses uniform permissions for all peers, then network simplicity and ease of operation are improved, but data security and access control are worsened

Engineering Contradiction:
Improvenetwork simplicityVSAvoiddata security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements field-based permissioning where different fields within blockchain data structures have different access controls assigned to different peers. This allows specific fields to be readable or writable by specific peers based on their role, while maintaining the overall simplicity of the blockchain architecture. The permission system is localized to specific data fields rather than requiring complex global permission management.

Inventive Principle:
Principle #3Local quality

2Loss of information

If all information in blockchain blocks is visible to all peers, then transparency and trust are improved, but secrecy and access control are worsened

Engineering Contradiction:
Improveinformation transparencyVSAvoidinformation secrecy
Core Design Contradiction:
Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The patent segments blockchain data into multiple fields within data structures (such as order books, inventory, shipments), and applies different visibility and access control policies to different fields. Some fields are visible to all peers for transparency, while other sensitive fields are restricted to specific peers based on permission assignments. This segmentation allows simultaneous achievement of transparency where needed and secrecy where required.

Inventive Principle:
Principle #1Segmentation

3Reliability

If blockchain provides immutable and transparent data storage, then trust and security are improved, but fine-grained access control and permission enforcement are worsened

Engineering Contradiction:
Improvedata immutabilityVSAvoidpermission control complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The blockchain nodes automatically enforce field-based permissions through built-in validation logic that checks peer permissions before allowing data reads or writes. The permission system is self-enforcing at the protocol level, eliminating the need for external permission management infrastructure. Nodes independently verify permissions based on their assigned roles, maintaining immutability while providing fine-grained access control without adding significant system complexity.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11080247B2Field-based peer permissions in a blockchain network
Publication Date: 2021.08.03 SALESFORCE INC
  • US11080247B2 patent drawing
  • US11080247B2 patent drawing
  • US11080247B2 patent drawing

AI summary

A method for a multi-tenant server to manage data in a blockchain network is described. The method includes generating an exchange object for the network, wherein the exchange object includes a set of exchange fields and a mapping between each exchange field in the set of exchange fields and a field of an object associated with each peer in the network; determining permissions for each exchange field and for each peer in the network; generating, on behalf of a first peer in the network, a transaction object using the exchange object, wherein the transaction object includes a set of field values for the set of exchange fields and one or more field values in the set of values are encrypted based on the permissions; and making the transaction object available to a second peer in the network to attempt to obtain consensus for altering an object of the first peer.