Transaction Management Layer for Channel Format Conversion

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Transaction processing systems face inefficiencies due to the need for additional software applications to convert channel-specific formats of transaction requests into a processing format, which is time-consuming and resource-intensive.

Innovation Solution

A transaction management layer that transforms transaction requests from channel-specific formats into an internal specific format and then into a transaction processing format using stored mappings, eliminating the need for additional software applications and conserving computing resources.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If additional software applications are used to convert channel-specific formats to processing format, then format conversion capability is improved, but processing time and resource consumption increase

Engineering Contradiction:
Improveformat conversion capabilityVSAvoidprocessing time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent merges multiple format conversion functions into a single integrated transaction management layer. Instead of using separate software applications for each format conversion, the system consolidates all channel-specific format transformations into one unified component that directly interfaces with the downstream processing system, eliminating the need for multiple intermediate conversion applications and reducing processing time.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The transaction management layer is designed as a universal component that handles format conversion for multiple different channel-specific formats simultaneously. This multi-functional layer can process requests from various channels with different formats without requiring separate dedicated conversion software for each channel, thereby reducing overall processing time and resource consumption.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Adaptability or versatility

If additional software applications are used to convert channel-specific formats to processing format, then format conversion capability is improved, but resource consumption increases

Engineering Contradiction:
Improveformat conversion capabilityVSAvoidcomputing resources
Core Design Contradiction:
Adaptability or versatilityVSUse of energy by moving object

Solution Approach 1:

The patent merges multiple format conversion functions into a single integrated transaction management layer. Instead of using separate software applications for each format conversion, the system consolidates all channel-specific format transformations into one unified component that directly interfaces with the downstream processing system, eliminating the need for multiple intermediate conversion applications and reducing processing time.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The transaction management layer is designed as a universal component that handles format conversion for multiple different channel-specific formats simultaneously. This multi-functional layer can process requests from various channels with different formats without requiring separate dedicated conversion software for each channel, thereby reducing overall processing time and resource consumption.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Adaptability or versatility

If manual format conversion is performed, then flexibility in handling different formats is improved, but automation level decreases

Engineering Contradiction:
Improveformat transformation flexibilityVSAvoidautomatic format transformation
Core Design Contradiction:
Adaptability or versatilityVSExtent of automation

Solution Approach 1:

The transaction management layer automatically performs format conversion based on pre-configured mappings between channel-specific formats and the downstream processing system format. The system serves itself by maintaining a repository of format mappings and autonomously selecting and applying the appropriate transformation rules without requiring manual intervention, thus achieving both automation and flexibility.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The system performs preliminary configuration of format mappings between various channel-specific formats and the downstream processing system format. These mappings are established in advance and stored in the transaction management layer, enabling automatic format transformation without manual input during actual transaction processing, thereby achieving both automation and adaptability.

Inventive Principle:
Principle #10Preliminary action

Data Source

PatentUS20240273481A1Integration of channels in transaction systems
Publication Date: 2024.08.15 TRUIST BANK
  • US20240273481A1 patent drawing
  • US20240273481A1 patent drawing
  • US20240273481A1 patent drawing

AI summary

Transaction requests in a channel-specific format can be automatically transformed into a transaction processing format in transaction systems. For example, a system can receive, by a transaction management layer, a transaction request from a transaction channel in a channel-specific format associated with the transaction channel. The system can transform the transaction request into an internal specific format of the transaction management layer based on a first mapping from the channel-specific format to the internal specific format. Additionally, the system can transform the transaction request into a transaction processing format of a downstream transaction processing system based on a second mapping from the internal specific format to the transaction processing format. The system can send the transaction request in the transaction processing format to the downstream transaction processing system. The downstream transaction processing system can be configured to execute the transaction request in response to receiving the transaction request.