Blockchain Service Data Digest for Readability and Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain-based data storage systems face challenges with poor readability of service data due to its ciphertext form, making it difficult to trace and understand the processing procedures of service data across nodes.

Innovation Solution

The implementation of a smart contract in a blockchain that generates service data digest information based on a unified digest data structure, allowing for the storage of this information in plaintext form alongside the service data, enhancing readability and traceability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If service data is stored in blockchain in ciphertext form for security, then data security is improved, but readability of service data deteriorates

Engineering Contradiction:
Improvedata securityVSAvoidreadability
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent segments service data into two parts: ciphertext form for security and plaintext digest information for readability. The digest information contains key features extracted from the original service data and is stored separately in plaintext form, allowing users to read and understand service processing procedures without compromising the security of the complete ciphertext data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces digest information as an intermediary between the ciphertext service data and users. This digest information serves as a mediator that provides readable summaries of service data contents without exposing the complete original data, thus bridging the gap between security requirements and readability needs.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If service data is stored in ciphertext form in blockchain, then data security is improved, but traceability of service data processing procedures deteriorates

Engineering Contradiction:
Improvedata securityVSAvoidtraceability information
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent segments traceability information from the complete service data and stores it separately as digest information in plaintext form. This segmentation allows traceability features such as service processing procedures, node information, and timestamps to be readily accessible while the complete service data remains securely stored in ciphertext form.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent performs preliminary extraction of traceability information from service data before storage. By pre-extracting and storing digest information containing key traceability features, the system enables quick traceability without requiring decryption or complex queries of the complete ciphertext data later.

Inventive Principle:
Principle #10Preliminary action

3Quantity of substance

If complete service data is stored in blockchain, then data completeness is improved, but storage efficiency deteriorates

Engineering Contradiction:
Improvedata completenessVSAvoidstorage efficiency
Core Design Contradiction:
Quantity of substanceVSProductivity

Solution Approach 1:

The patent extracts digest information from complete service data and stores only the essential features in plaintext form in the blockchain, while the complete service data is stored separately. This extraction reduces the amount of data stored in the blockchain, improving storage efficiency and transaction processing speed while maintaining data completeness through the separate storage of the full service data.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentEP3975474B1Methods and apparatuses for chaining service data
Publication Date: 2024.02.07 ALIPAY (HANGZHOU) INFORMATION TECH CO LTD
  • EP3975474B1 patent drawingFigure 1
  • EP3975474B1 patent drawingFigure 2
  • EP3975474B1 patent drawingFigure 3

AI summary

One or more embodiments of the present specification provide methods and apparatuses for chaining service data. The methods include the following: Service data to be chained that is generated for each service processing node for a target service is obtained, where the service data to be chained includes feature values corresponding to a plurality of service data fields. A smart contract deployed in a blockchain is invoked to generate, based on the feature values corresponding to the plurality of service data fields and at least one predetermined digest information field, service data digest information corresponding to each service processing node, where the at least one predetermined digest information field includes at least one specified data field in a unified digest data structure built for a plurality of service processing nodes. The service data digest information generated for each service processing node and the corresponding service data to be chained are stored in the blockchain.