Distributed Group Transaction Processing With Temporary Files

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing systems face challenges in efficiently processing group transactions, particularly in scenarios where partial payments or authentications are required, leading to inefficiencies and susceptibility to fraudulent activities due to the lack of robust tracking and verification mechanisms.

Innovation Solution

A distributed computer system comprising an application server and an auxiliary server that creates and manages temporary files to store partial transaction values, integrates with an electronic banking system for flexible payment handling, and issues designated files only after verifying the target value and entity identification, enabling secure and flexible group transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Device complexity

If partial payments are stored in a centralized system, then payment tracking is simplified, but the system becomes vulnerable to fraudulent activities and single points of failure

Engineering Contradiction:
Improvepayment tracking mechanismVSAvoidfraud resistance
Core Design Contradiction:
Device complexityVSReliability

Solution Approach 1:

The patent divides the centralized payment storage system into multiple distributed storage locations (temporary files on different servers). Each server stores portions of payment data independently, eliminating the single point of failure while maintaining trackability through systematic file references and transaction identifiers.

Inventive Principle:
Principle #1Segmentation

2Reliability

If ticket issuance is coupled with payment verification, then fraud is reduced, but operational efficiency decreases due to sequential processing requirements

Engineering Contradiction:
Improvefraud preventionVSAvoidtransaction processing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent performs preliminary payment verification and stores validation results in temporary files before the actual ticket issuance process. This allows the ticketing system to issue tickets efficiently while the payment status has already been pre-verified and recorded, enabling parallel processing without compromising fraud prevention.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent introduces temporary files as intermediary storage between payment verification and ticket issuance. These files act as a buffer that decouples the two processes, allowing ticket issuance to proceed based on pre-verified payment data without requiring real-time payment system availability, thus improving operational efficiency while maintaining security.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If a robust verification system is implemented, then transaction security is improved, but system complexity increases

Engineering Contradiction:
Improvetransaction securityVSAvoidverification mechanism
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements self-service verification mechanisms where the system automatically validates transactions against stored criteria and generates verification records without requiring complex external validation systems. The temporary files contain all necessary verification data, allowing the system to autonomously verify transaction legitimacy through systematic file checking and validation rules.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS12423625B2Distributed computer system for delivering data
Publication Date: 2025.09.23 AMADEUS SAS
  • US12423625B2 patent drawing
  • US12423625B2 patent drawing
  • US12423625B2 patent drawing

AI summary

Distributed computer system with an application server and an auxiliary server for processing a group transaction with entities in the group. The group transaction, requiring a target value to be received, includes first and second transactions. The application server is configured to receive the first transaction including a first value, interface the auxiliary server to create and access a temporary file to store the first value in which temporary file is associated with the group transaction, receive the second transaction including a second value after the first transaction in which the second value to reach a target value when combined with the first value, and receive identification information associated with the group transaction for each group entity independently from the first and second transactions. In response to receiving the first and second values as well as the identification information for each group, designated files are issued for each entity.