Data Swap Prevention in Distributed Computing via ID Correlation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing security and data privacy products face difficulties in addressing accidental data swaps and transaction integrity issues, particularly in high-user-volumetric, concurrent transactions, and multi-threaded system environments, making it challenging to perform functional validation tests with realistic workloads.

Innovation Solution

A computer-implemented method and system that measures transaction volumes in a distributed computing environment to identify potential data swap locations, manages the correlation between thread identification and transaction header IDs, and performs data transmission interruptions when these IDs do not match to prevent data swaps.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing security and data privacy products are used, then basic security protection is provided, but they fail to address accidental data swaps and transaction integrity issues in high-concurrency environments

Engineering Contradiction:
Improvetransaction integrityVSAvoidcapability to handle concurrent transactions
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The system performs preliminary actions by establishing thread ID to transaction header ID correlations before data swaps can occur. The data swap prevention service proactively monitors and validates ID correlations throughout transaction processing, preventing integrity issues rather than detecting them after the fact.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

A data swap prevention service is introduced as an intermediary component between existing security products and the distributed computing environment. This service specifically addresses transaction integrity by managing ID correlations and blocking potential data swaps, filling the gap between general security products and specialized transaction protection needs.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If functional validation tests are performed with concurrent users and realistic workloads, then transaction integrity can be tested, but it becomes difficult to perform wide range of functional validations

Engineering Contradiction:
Improvedetection of data swapsVSAvoidtesting system complexity
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The data swap prevention functionality is extracted as a separate, standalone service that can be independently tested and validated. This allows functional validation tests to focus specifically on transaction integrity mechanisms without needing to replicate entire distributed system complexities, simplifying the testing process while maintaining detection precision.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If data transmission interruption is performed to prevent data swaps, then transaction integrity is maintained, but latency may increase

Engineering Contradiction:
Improveend-to-end transaction integrityVSAvoidtransaction latency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system implements continuous feedback by monitoring thread ID and transaction header ID correlations throughout the transaction lifecycle. This real-time feedback mechanism allows the data swap prevention service to intervene only when actual mismatches are detected, rather than continuously interrupting all transactions, thus maintaining integrity while minimizing latency impact.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The data transmission interruption is applied partially - only when ID mismatches are detected - rather than continuously for all transactions. This selective application prevents data swaps when necessary while avoiding unnecessary interruptions that would increase latency for normal, valid transactions.

Inventive Principle:
Principle #16Partial or excessive action

Data Source

PatentUS12067414B2Data swap prevention in distributed computing environments based on mapping among global user identification, correlation identification and thread identification
Publication Date: 2024.08.20 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US12067414B2 patent drawing
  • US12067414B2 patent drawing
  • US12067414B2 patent drawing

AI summary

Inadvertent data swaps can be prevented by measuring volume of transactions in distributed computing environment to determine locations for potential data swaps; and managing a correlation between a thread identification (ID) and transaction header (ID) for transactions in the distributed computing environment. In some embodiments, the prevention of data swaps can further include performing a data transmission interruption to avoid data swaps at the locations for potential data swaps. When the thread identification (ID) and transaction header (ID) do not match the potential for data swaps can be high.