Multi-instance Blockchain Architecture for Trusted Network Data Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current remote network management platforms face challenges in efficiently recording and sharing transaction data across multiple enterprises due to data siloing and security concerns, particularly in multi-tenant architectures where data comingling leads to security risks and operational inefficiencies.

Innovation Solution

Integration of blockchain-based distributed ledger technology within a remote network management platform's multi-instance architecture allows enterprises to securely store and share transaction data across trusted networks, using pre-shared keys for encryption and hash functions to ensure data integrity and accessibility among trusted computational instances.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If blockchain-based distributed ledger technology is integrated into the multiinstance architecture, then data security and integrity are improved, but device complexity increases

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the blockchain implementation at the computational instance level, where each instance maintains its own ledger copy. This segmentation allows each instance to independently manage its data while contributing to the overall distributed ledger, reducing the complexity burden on any single instance while maintaining data integrity across the network.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A centralized controller acts as an intermediary to manage the blockchain integration across multiple computational instances. The controller handles coordination, validation, and synchronization tasks, which simplifies the implementation at individual instances while maintaining system-wide data integrity and security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If data is stored and shared across trusted networks using encryption, then data security is improved, but ease of operation deteriorates

Engineering Contradiction:
Improvedata securityVSAvoiddata accessibility
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

Computational instances automatically perform encryption and decryption operations using their pre-shared keys without requiring manual intervention. The system self-manages security operations, maintaining data protection while enabling seamless access for authorized instances, thus improving ease of operation despite the security measures in place.

Inventive Principle:
Principle #25Self-service

3Loss of information

If a distributed ledger is distributed across computational instances, then data transparency is improved, but loss of information increases

Engineering Contradiction:
Improvedata transparencyVSAvoiddata integrity
Core Design Contradiction:
Loss of informationVSReliability

Solution Approach 1:

Each computationalinstance maintains a local copy of the blockchain ledger with full read access, ensuring transparency and data availability. However, the local quality of data storage is enhanced by implementing selective replication and validation mechanisms that ensure each instance receives and verifies only the necessary data blocks, preventing information loss while maintaining integrity.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS10826682B2Multi-instance architecture supporting trusted blockchain-based network
Publication Date: 2020.11.03 SERVICENOW INC
  • US10826682B2 patent drawing
  • US10826682B2 patent drawing
  • US10826682B2 patent drawing

AI summary

An example embodiment performed by a scoped software application executable on a computing device of a computational instance within a trust group of computational instances of a remote network management platform may involve obtaining a representation of one or more transactions involving the computational instance. The embodiment may also involve encrypting the representation, using a pre-shared key to which at least some computational instances within the trust group have access. The embodiment may also involve placing the encrypted representation into a data block that also includes: (i) a first output generated by applying a hash function to content from a previous data block of a blockchain-based transaction ledger, and (ii) a second output generated by applying the hash function to the encrypted representation and the first output. The embodiment may also involve distributing copies of the data block to blockchain-based transaction ledgers within each computational instance of the trust group.