Trace Context in File Transfer Communications

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In distributed computing environments, particularly in financial transactions, the propagation of global context identifiers is disrupted during file transfers, leading to fragmented transaction traces and the inability to observe entire distributed transactions, as existing solutions only address HTTP and message queue-based protocols, not file transfer protocols.

Innovation Solution

A method where a first subsystem embeds a global context identifier alongside data content for transmission to a second subsystem using file transfer communication, allowing the second subsystem to extract and associate the identifier with further data, ensuring trace continuity across subsystems.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If file transfer communication is used between subsystems, then data can be transmitted between systems, but global context identifier propagation is disrupted and transaction traces become fragmented

Engineering Contradiction:

Improvetransaction trace continuityVSAvoidglobal context identifier propagation

Core Design Contradiction:

ReliabilityVSLoss of information

Solution Approach 1:

The patent segments the file transfer process into distinct phases: file generation, file transfer, and file processing. By embedding the global context identifier in the file metadata during generation and extracting it during processing, the system maintains trace continuity across these segmented operations despite the file transfer protocol's lack of native support for context propagation.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent applies preliminary action by embedding the global context identifier into the file metadata before the file transfer occurs. This pre-embedding ensures that the identifier is already present in the file when transferred, eliminating the need for complex real-time communication protocols during the actual file transfer and ensuring trace continuity is maintained.

Inventive Principle:

Principle #10Preliminary action

2Adaptability or versatility

If existing HTTP and message queue protocols are used for distributed transactions, then context identifiers can be propagated, but file transfer protocols cannot be addressed

Engineering Contradiction:

Improveprotocol support coverageVSAvoidtrace continuity in file transfers

Core Design Contradiction:

Adaptability or versatilityVSReliability

Solution Approach 1:

The patent creates a universal solution that works across multiple file transfer protocols (FTP, SFTP, SCP,/rsync) by implementing a protocol-agnostic approach. The system embeds context identifiers in file metadata and extracts them during processing, a method that functions independently of the specific transfer protocol used, thereby achieving both versatility and reliability.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces an intermediary mechanism in the form of file metadata that acts as a carrier for the global context identifier. This metadata intermediary allows context information to be transported through file transfer protocols that otherwise lack native context propagation capabilities, bridging the gap between different protocol requirements.

Inventive Principle:

Principle #24Intermediary (Mediator)

3Productivity

If file transfers are executed without embedding context identifiers, then simple data transmission occurs, but complete transaction tracing and troubleshooting become impossible

Engineering Contradiction:

Improvefile transfer efficiencyVSAvoidtransaction observation capability

Core Design Contradiction:

ProductivityVSDifficulty of detecting and measuring

Solution Approach 1:

The patent extracts the global context identifier from the file metadata during the file processing phase, separating the context information extraction from the file transfer operation itself. This extraction mechanism enables complete transaction tracing without interfering with the efficiency of the file transfer, as the identifier is simply read from existing metadata rather than adding transfer overhead.

Inventive Principle:

Principle #2Taking out (Extraction)

Data Source

PatentUS20240314195A1Trace context over file transfer communications

Publication Date: 2024.09.19 CAPITAL ONE FINANCIAL CORP

AI summary

A computing system is configured to (i) receive, from an upstream computing system, a message including (a) data content related to a distributed financial transaction that spans the upstream computing system, the computing system, and a downstream computing system, and (b) a global context identifier that identifies the distributed financial transaction, (ii) decide to execute, as part of the distributed financial transaction, a file transfer of a file from the computing system to the downstream computing system, the file including the data content, (iii) extract, from the message, the global context identifier, (iv) generate a data element that includes the global context identifier for association with the file transfer, (v) associate the data element with the file such that the data element is isolated from the data content, and (vi) execute the file transfer by transmitting the file and the associated data element for receipt by the downstream computing system.