Blockchain Object Tracing Across Multiple Parties

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing database management systems fail to reliably control and trace the flow of objects across different parties due to differences in data formats, schemas, and synchronization frequencies, making it challenging to ensure consistency and security in object transfer.

Innovation Solution

A blockchain database is used to store records of object operations, with a rule set defining constraints on these operations, allowing parties to verify and record transactions securely and immutably, ensuring traceability and control across multiple parties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a centralized database is used to store all records, then data consistency and traceability are improved, but system security and reliability deteriorate due to single point of failure

Engineering Contradiction:
Improvedata consistencyVSAvoidsecurity vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent divides the centralized database into a distributed blockchain network where multiple nodes store copies of the ledger. Each node independently maintains the database, eliminating the single point of failure while ensuring data consistency through distributed consensus mechanisms.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a smart contract as an intermediary mechanism that automatically executes and verifies transactions according to predefined rules. This intermediary layer ensures data consistency without requiring a centralized authority, thereby improving reliability while reducing security vulnerabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Object-affected harmful factors

If each party maintains their own database, then system security and autonomy are improved, but data consistency and traceability across parties deteriorate

Engineering Contradiction:
Improvesecurity autonomyVSAvoiddata consistency
Core Design Contradiction:
Object-affected harmful factorsVSReliability

Solution Approach 1:

The patent merges the autonomy of individual party databases with a shared blockchain ledger. Each party maintains their own database for local operations while simultaneously accessing the shared blockchain for cross-party transactions, achieving both security autonomy and data consistency.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent implements real-time feedback mechanisms where transactions are verified by multiple parties through consensus algorithms. This feedback loop ensures that all parties agree on the current state of data, maintaining consistency across distributed databases while preserving each party's security and autonomy.

Inventive Principle:
Principle #23Feedback

3Reliability

If frequent data synchronization is performed, then data consistency is improved, but system complexity and processing overhead increase

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

Solution Approach 1:

The patent performs preliminary actions by pre-defining business rules and validation logic in smart contracts before transactions occur. This preliminary setup eliminates the need for complex real-time synchronization protocols, as transactions are automatically validated against predefined rules, reducing system complexity while maintaining consistency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent replaces complex mechanical synchronization mechanisms with cryptographic verification and consensus algorithms. Instead of frequent mechanical data exchange and reconciliation, the system uses cryptographic proofs and distributed consensus to achieve consistency, significantly reducing processing overhead and system complexity.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Data Source

PatentUS11210426B2Tracing objects across different parties
Publication Date: 2021.12.28 MICROSOFT TECHNOLOGY LICENSING LLC
  • US11210426B2 patent drawing
  • US11210426B2 patent drawing
  • US11210426B2 patent drawing

AI summary

In implementations of the subject matter described herein, a new approach for controlling and tracing an object across a plurality of parties is proposed. A rule set may be enabled by the confirmation of a plurality of parties. The rule set may define constraints on operations related to the object. Upon receipt of a request for an operation related to the object, the requested operation may be verified based on the rule set agreed by the plurality of parties. In response to verifying that requested operation is valid, the requested operation may be performed, and a record for the operation may be created and stored in a blockchain database accessible to the plurality of parties.