Transaction Tagging via Row Column Hashing for Data Fidelity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing transaction batching systems face challenges in identifying and correcting corrupted or altered data during batch transmission, as it is difficult to determine which specific transaction's data has been changed or corrupted, especially when attacked by malicious actors or corrupted.

Innovation Solution

A transaction tagging computer program that generates hash values for each row and column of a transaction log, allowing for efficient comparison and identification of mismatches, and includes encryption and decryption processes to ensure data fidelity across multiple recipients.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If batch transmission is used to save transmission costs, then transmission efficiency is improved, but the ability to identify corrupted or altered data is worsened

Engineering Contradiction:
Improvetransmission efficiencyVSAvoiddifficulty to identify corrupted data
Core Design Contradiction:
ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent divides the batch transmission into individual transaction segments, each with its own hash value. This segmentation allows the system to maintain the efficiency of batch transmission while enabling identification of specific corrupted transactions through hash comparison, resolving the contradiction between transmission efficiency and corruption detection capability.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces hash values as an intermediary mechanism between the batch transmission system and the corruption detection process. These hash values serve as a mediator that enables efficient verification of data integrity without requiring detailed examination of each transaction, thus maintaining transmission efficiency while improving corruption detection.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If each transaction is tagged with a unique hash identifier, then data integrity verification is improved, but processing overhead is worsened

Engineering Contradiction:
Improvedata integrity verificationVSAvoidprocessing overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent creates simplified copies of transaction data in the form of hash values. These hash copies are much more efficient to process and compare than the full transaction data, enabling reliable data integrity verification while minimizing processing overhead. The hash acts as a compact representation that preserves verification capability without the computational burden of processing complete transactions.

Inventive Principle:
Principle #26Copying

3Loss of energy

If hashing is applied to save storage and processing power, then resource efficiency is improved, but the ability to locate specific corrupted transactions is worsened

Engineering Contradiction:
Improvestorage and processing powerVSAvoidability to locate corrupted transactions
Core Design Contradiction:
Loss of energyVSLoss of information

Solution Approach 1:

The patent applies hash values at multiple levels: individual transaction level and batch level. This multi-level application of hashing creates a hierarchical structure where local hash values enable quick identification of corrupted transactions within a batch, while maintaining overall resource efficiency. The local quality of individual transaction hashes preserves the ability to locate specific corrupted transactions without requiring full processing of all transactions.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12260404B2Hash-based transaction tagging
Publication Date: 2025.03.25 BANK OF AMERICA CORP
  • US12260404B2 patent drawing
  • US12260404B2 patent drawing
  • US12260404B2 patent drawing

AI summary

Apparatus and methods for determining transaction transmission fidelity are provided. A sender may receive a transaction log including multiple transactions in two or more rows and two or more columns. The transaction log may be encrypted. Each of the transactions may be tagged. Each row and column of the transaction log may be hashed. The encrypted transaction log and the hash values may be transmitted to a recipient. The recipient may decrypt the transaction log and hash each row and column of the decrypted transaction log. The hash values may be compared and if there is a difference, a report or alert may be generated.