Cloud Asynchronous Message Repository for Payment Systems

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional synchronous communication systems in electronic payment infrastructure are inefficient due to resource busy-waiting and errors caused by out-of-sequence messages, limiting the flexibility and reliability of transactions between POS terminals, PIN pads, and other components.

Innovation Solution

Implementing cloud-based asynchronous communication using an electronic message repository that allows components to send and receive messages independently, with a state management system ensuring messages are processed in sync with transaction flows, and a mailbox system for message queuing and notification, reducing errors and resource idle times.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If synchronous communication is used between POS terminal and PIN pad, then message transmission is simple and direct, but system efficiency decreases due to resources busy-waiting for responses

Engineering Contradiction:
Improvesystem efficiencyVSAvoidwaiting time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The system performs preliminary actions by sending messages to the electronic message repository in advance, allowing the sender to continue processing without waiting for responses. The message repository pre-processes and queues messages, enabling asynchronous communication where resources are not blocked waiting for replies.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If synchronous communication is used, then message transmission is straightforward, but errors occur when out of sequence messages arrive due to limited request/response pairing

Engineering Contradiction:
Improvemessage transmission reliabilityVSAvoidcommunication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The electronic message repository acts as an intermediary between the POS terminal and PIN pad, receiving, storing, and managing messages asynchronously. This mediator decouples the direct request/response relationship, allowing messages to be processed in any sequence without causing errors, as the repository maintains proper message-state associations.

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If asynchronous communication with state management is implemented, then message processing reliability improves, but system complexity increases due to state tracking requirements

Engineering Contradiction:
Improvemessage processing reliabilityVSAvoidstate management complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system implements feedback mechanisms where the electronic message repository continuously monitors message states and updates them based on processing outcomes. The state management system receives feedback about message processing status and adjusts accordingly, ensuring reliable asynchronous communication while systematically managing complexity through structured state tracking.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20220172190A1Systems and methods for cloud-based asynchronous communication
Publication Date: 2022.06.02 WORLDPAY LLC
  • US20220172190A1 patent drawing
  • US20220172190A1 patent drawing
  • US20220172190A1 patent drawing

AI summary

A method for cloud-based asynchronous communication includes receiving a transaction request message from a cloud-based application, sending the received transaction request message to a PIN pad by way of an electronic message repository, updating a current state according to the received transaction request, listening for a new incoming message event from the electronic message repository, receiving a new incoming message event from the electronic message repository, and retrieving an incoming message from the electronic message repository, determining whether the retrieved incoming message matches the current state, upon determining that the retrieved incoming message matches the current state, transmitting the retrieved incoming message to the cloud-based application, and upon determining that the retrieved incoming message does not match the current state, retaining the retrieved incoming message in the electronic message repository.