Distributed Database Routing for Resilient Transaction Processing

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current electronic banking systems face challenges in ensuring resilient and flexible storage and management of electronic transaction messages, particularly during technology failures or natural disasters, which can lead to overpayment or underpayment between banks.

Innovation Solution

A system comprising a plurality of switches and a clustered database that generates transaction summary records, allowing for resilient processing of electronic transaction requests, with each transaction request message being routed based on a unique identifier and verified through digital signatures, ensuring data accessibility even if one database becomes non-operational.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If a single centralized database is used to store transaction messages, then data management is simplified, but the system becomes vulnerable to technology failures and natural disasters

Engineering Contradiction:
Improvedata management complexityVSAvoidsystem resilience
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent divides the centralized database into multiple distributed database nodes located at different geographic sites. Each node stores copies or partitions of transaction message data, so that if one node fails due to technology failure or natural disaster, other nodes remain operational and can continue processing transactions.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent implements site-specific database nodes with local storage capabilities, where each location has its own database infrastructure tailored to local requirements. This allows local nodes to operate independently and provides geographic distribution that enhances resilience against localized disasters while maintaining data accessibility.

Inventive Principle:
Principle #3Local quality

2Device complexity

If transaction messages are stored at a single location, then system architecture is simpler, but data accessibility is lost when the location becomes non-operational

Engineering Contradiction:
Improvesystem architecture complexityVSAvoiddata accessibility
Core Design Contradiction:
Device complexityVSLoss of information

Solution Approach 1:

The patent combines multiple database nodes at different locations into a unified distributed database system. All nodes are interconnected and maintain synchronized data, creating a merged system where data is accessible from any location. This provides both the simplicity of a unified system and the resilience of distributed architecture.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The patent creates multiple copies of transaction message data across different geographic locations through replication. Each database node maintains copies of the transaction data, ensuring that if one location becomes non-operational, data can be accessed from other locations with identical or synchronized copies.

Inventive Principle:
Principle #26Copying

3Reliability

If multiple synchronized databases are used across different locations, then system resilience is improved, but device complexity increases

Engineering Contradiction:
Improvesystem resilienceVSAvoiddistributed system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic synchronization mechanisms that automatically adjust data replication and consistency management across distributed nodes. The system dynamically routes transactions to appropriate nodes, manages replication priorities, and adapts to node availability in real-time, reducing the operational complexity of maintaining multiple databases.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent incorporates feedback mechanisms where database nodes continuously monitor each other's status and automatically adjust their operations. When nodes detect failures or maintenance activities at other locations, they receive feedback and adjust their data synchronization and transaction processing accordingly, reducing manual intervention and simplifying system management.

Inventive Principle:
Principle #23Feedback

Data Source

PatentEP4220514A1A device, system, method and computer program product for processing electronic transaction requests
Publication Date: 2023.08.02 VOCALINK LTD
  • EP4220514A1 patent drawingFigure 1
  • EP4220514A1 patent drawingFigure 2A
  • EP4220514A1 patent drawingFigure 2B

AI summary

A system for receiving electronic messages from a financial institution, the system comprising a plurality of switches configured to communicate with one another and to process the received electronic messages, wherein each switch includes processing circuitry that is configured to receive an electronic message that includes a unique identifier and, in dependence upon the unique identifier, either process the electronic message or forward the electronic message to another one of the switches for processing .