Blockchain Receipt Record for Data Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In blockchain-type ledgers, data records with the same service attribute are distributed across data blocks, making it difficult to identify correlations between them.

Innovation Solution

A method and apparatus for storing receipt data in a centralized database server using a blockchain-type ledger, where a data block includes a block header and a block body, involving obtaining a to-be-stored data record, determining execution information, obtaining a previous data record with the same service attribute, generating a receipt record with a hash value, and writing both records into the same block body to establish correlation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Quantity of substance

If data records are distributed across different data blocks in a blockchain-type ledger, then storage capacity and decentralization are improved, but the ability to identify correlations between data records deteriorates

Engineering Contradiction:
Improvestorage capacityVSAvoidcorrelation information
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent introduces a receipt record as an intermediary element that contains a hash value of a previous data record. This receipt record serves as a mediator that links distributed data records together, allowing correlation information to be preserved without compromising the distributed storage structure. The receipt record acts as a bridge between the current data record and its historical counterpart, enabling traceability while maintaining decentralization.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Productivity

If data records with the same service attribute are stored in different data blocks, then data distribution and scalability are improved, but data chain query and verification become more difficult

Engineering Contradiction:
ImprovescalabilityVSAvoidquery ease
Core Design Contradiction:
ProductivityVSEase of operation

Solution Approach 1:

The patent implements a feedback mechanism where each data record includes a receipt record containing a hash value that references its parent data record. This creates a chain of references that automatically provides verification feedback, enabling efficient data chain queries even when records are distributed across multiple blocks. The hash value acts as a feedback signal that allows systematic verification without requiring centralized coordination.

Inventive Principle:
Principle #23Feedback

3Quantity of substance

If correlation information between data records is not explicitly stored, then storage efficiency is improved, but the ability to perform data verification and tracing deteriorates

Engineering Contradiction:
Improvestorage efficiencyVSAvoidverification capability
Core Design Contradiction:
Quantity of substanceVSReliability

Solution Approach 1:

The patent uses cryptographic hash values as compact copies of reference information. Instead of storing complete correlation data, the system stores hash copies that are sufficiently small to maintain storage efficiency but sufficiently informative to enable verification. The hash value serves as a compact representation that preserves the essential verification capability without the overhead of storing full correlation information.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11223471B2Blockchain-type data storage
Publication Date: 2022.01.11 ANTCHAIN TECHNOLOGY PTE LTD
  • US11223471B2 patent drawing
  • US11223471B2 patent drawing
  • US11223471B2 patent drawing

AI summary

This disclosure relates to blockchain-type storage of receipt data. In one aspect, a method includes obtaining a to-be-stored data record including a first service attribute. Execution information of the to-be-stored data record is determined. A previous data record is obtained from a blockchain-type ledger. The previous data record includes a second service attribute that is the same as the first service attribute. Each data block in the blockchain-type ledger includes a block header and a block body. A hash value of the previous data record is determined. A receipt record is generated. The receipt record includes the hash value of the previous data record and the execution information of the to-be-stored data record. The to-be-stored data record and the receipt record are written into a same block body in the blockchain-type ledger.