Transaction Message Correlation via Unique Identifier Headers

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In payment account transactions, tracking and tracing transactions across disparate interfaces and networks is inefficient due to the lack of uniform identification, making it difficult to determine transaction status and diagnose failures.

Innovation Solution

Implementing an enhanced remote procedure call (RPC) using gRPC to transport transaction messages with a unique identifier, appending it as a header, and serializing data with protocol buffers, ensuring transaction messages remain identifiable and traceable across different interfaces without altering the ISO standard.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If transaction messages are transmitted across disparate interfaces using different formats and standards, then interoperability between different systems is achieved, but tracking and correlating transactions becomes inefficient and difficult

Engineering Contradiction:

ImproveinteroperabilityVSAvoidtransaction tracking capability

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces a correlation identifier as an intermediary element that is added to transaction messages. This identifier acts as a universal mediator that enables tracking and correlation across disparate interfaces and networks, while allowing each interface to maintain its own message format and standards. The correlation identifier serves as the common thread that connects transactions throughout the system without requiring changes to existing interface protocols.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The correlation identifier is designed to be universally applicable across multiple different interfaces, networks, and message formats. It performs multiple functions: identifying transactions, enabling correlation, facilitating tracking, and supporting analytics. This universal element can be incorporated into various message types and interfaces without requiring interface-specific implementations, thereby maintaining interoperability while enabling unified transaction tracking.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If unique identifiers are appended to all transaction messages, then end-to-end visibility and tracking are enabled, but message format complexity increases

Engineering Contradiction:

Improvetransaction visibilityVSAvoidmessage format

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the message structure into distinct components: the original transaction message payload and the added correlation identifier. This segmentation allows the correlation identifier to be appended as a separate element without altering the core transaction message format. The identifier can be added as a header, footer, or metadata field, depending on the interface requirements, thereby maintaining message format simplicity while enabling enhanced tracking capabilities.

Inventive Principle:

Principle #1Segmentation

3Stability of the object's composition

If existing message standards like ISO 8586 are maintained, then system compatibility is preserved, but transaction correlation across different interfaces is not supported

Engineering Contradiction:

Improvemessage standard complianceVSAvoidtransaction correlation capability

Core Design Contradiction:

Stability of the object's compositionVSAdaptability or versatility

Solution Approach 1:

The patent applies the nesting principle by placing the correlation identifier within or alongside the existing message structure without replacing the core message format. The correlation identifier can be nested as metadata, wrapped around the message, or appended as an additional field, allowing it to coexist with ISO 8586 and other message standards. This nesting approach enables transaction correlation capability to be added while maintaining full compatibility with existing message standards and system protocols.

Inventive Principle:

Principle #7Nested doll (Nesting)

Data Source

PatentUS11775364B2Systems and methods for use in correlating messages across disparate interfaces

Publication Date: 2023.10.03 MASTERCARD INT INC

AI summary

Systems and methods are provided for correlating messages between disparate interfaces, channels, and/or networks. One example computer-implemented method includes receiving, at a service computing device, a request from a user relating to at least one service associated therewith and compiling a message consistent with a first message standard based on the request. The method also includes requesting a global unique identifier (GUID) for the request from a generator, where the generator compiles the GUID and returns the GUID to the service computing device, and serializing the GUID and the compiled message to form a serialized message in which the compiled message defines a first parameter and the GUID defines a second parameter. The method then includes transmitting the serialized message to a message gateway, whereby the GUID is provided with the compiled message, while maintaining the compiled message consistent with the first message standard.