Nested Transaction Data Objects for Fast Tamper-Proof Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional transaction processing techniques for configurable technologies, such as as-a-service technologies, are resource-intensive and slow, failing to efficiently manage ongoing changes, tamper-proof transactions, provide fast access, enable quick updates, and verify authenticity.

Innovation Solution

The use of nested data objects that encapsulate transaction data, each layer of which includes hash values and private keys, allowing for encryption based on user access types, enabling fast and resource-efficient verification and management of transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If conventional transaction processing techniques are used for configurable technologies, then transactions can be processed and verified, but the process becomes resource-intensive and slow

Engineering Contradiction:
Improvetransaction processing speedVSAvoidcomputational resources
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent segments transaction data into hierarchical layers (first layer with file hash and basic transaction data, second layer with detailed transaction information). This segmentation allows selective processing and verification of different transaction components, improving processing speed while reducing overall computational resources required compared to processing complete transaction records conventionally.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates hash copies (first hash value of file contents, second hash value of transaction data) that serve as verification tokens. These cryptographic copies enable fast verification of transaction authenticity without processing the entire original file and transaction data, significantly improving verification speed while minimizing computational resources.

Inventive Principle:
Principle #26Copying

2Reliability

If complete transaction data is transmitted for verification, then verification accuracy is maintained, but transmission time and network resources increase

Engineering Contradiction:
Improvetransaction verification accuracyVSAvoidtransmission time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent extracts only the essential verification elements (hash values, digital signatures, layer identifiers) from complete transaction data and transmits these extracted components for verification. This extraction maintains verification accuracy by preserving cryptographic proof elements while dramatically reducing transmission time and network resource consumption.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent transforms transaction data into different representational forms through cryptographic hashing, changing the 'color' or format of data from raw transaction records to condensed hash values. This transformation maintains verification reliability through cryptographic properties while enabling faster transmission and processing.

Inventive Principle:
Principle #32Color changes

3Adaptability or versatility

If multiple layers of transaction data are added to nested data objects, then transaction history and configurability are preserved, but data structure complexity increases

Engineering Contradiction:
Improvetransaction history trackingVSAvoiddata structure complexity
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a nested data structure where a second layer (containing detailed transaction information) is embedded within a first layer (containing file hash and basic transaction data). This nesting preserves complete transaction history and enables flexible configurability while managing complexity through hierarchical organization, allowing verification of different transaction aspects at different levels.

Inventive Principle:
Principle #7Nested doll (Nesting)

Solution Approach 2:

The patent adds a temporal dimension to transaction data by organizing layers chronologically (first layer created initially, second layer added subsequently). This dimensional organization preserves transaction history and enables adaptability for different verification scenarios while managing complexity through structured layering rather than unstructured data growth.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

4Reliability

If cryptographic verification is performed on all transaction data, then tamper-proofness is ensured, but processing time increases

Engineering Contradiction:
Improvetamper-proofnessVSAvoidverification time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary cryptographic actions by computing hash values (first hash of file contents, second hash of transaction data) and digital signatures during transaction creation. These preliminary cryptographic preparations ensure tamper-proofness is established upfront, enabling faster subsequent verification without repeated heavy cryptographic computations on entire transaction datasets.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS12353581B2Processing transactions using nested data objects
Publication Date: 2025.07.08 DELL PROD LP
  • US12353581B2 patent drawing
  • US12353581B2 patent drawing
  • US12353581B2 patent drawing

AI summary

Methods, apparatus, and processor-readable storage media for processing transactions using nested data objects are provided herein. An example computer-implemented method includes: generating a nested data object corresponding to a file, where the nested data object includes a first layer for a first transaction related to the file; adding, for each of one or more additional transactions related to the file, a corresponding additional layer to the nested data object, where each layer of the nested data object include one or more respective hash values and one or more respective private keys; and transmitting the nested data object to a user device, where each layer of the nested object are encrypted based on a type of access specified for a user of the user device, and wherein each of the transactions is verifiable based at last in part on the one or more hash values of the corresponding layer.