Thin Client Rules Engine for Payment Transaction Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

High latency in communication networks, such as 2G mobile communication networks, leads to significant time delays due to multiple rounds of communication between remote computers and portable devices, affecting transaction processing efficiency.

Innovation Solution

A thin client equipped with a rules engine that processes transactions by receiving messages from a remote computer, communicating directly with a portable device, and transmitting messages without involving the remote computer, thereby reducing the number of message exchanges and optimizing transaction processing.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If multiple rounds of communication are used between remote computer and portable device, then transaction processing completeness is improved, but communication time delay increases

Engineering Contradiction:
Improvetransaction processing completenessVSAvoidcommunication time delay
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the communication process into two channels: a simplified command channel for transaction initiation and a direct data channel between thin client and portable device. This segmentation allows transaction completeness to be maintained through the command channel while reducing delays by enabling direct peer-to-peer communication for data exchange, eliminating intermediate relay delays.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The thin client acts as an intermediary that establishes a direct communication channel between the portable device and the network, bypassing the need for multiple round trips through the remote computer. The thin client receives commands from the remote computer and directly communicates with the portable device, reducing communication hops and latency.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If the thin client communicates with the remote computer for every message exchange, then transaction accuracy is improved, but communication overhead increases

Engineering Contradiction:
Improvetransaction accuracyVSAvoidcommunication overhead
Core Design Contradiction:
Measurement precisionVSDevice complexity

Solution Approach 1:

The thin client performs preliminary actions by establishing direct communication channels and caching transaction data locally. It pre-configures communication paths and stores necessary transaction information, enabling it to process messages accurately without requiring the remote computer for every single message exchange, thus reducing communication overhead while maintaining accuracy.

Inventive Principle:
Principle #10Preliminary action

3Productivity

If the thin client makes local decisions without remote computer communication, then transaction processing speed is improved, but system control decreases

Engineering Contradiction:
Improvetransaction processing speedVSAvoidsystem control
Core Design Contradiction:
ProductivityVSExtent of automation

Solution Approach 1:

The system implements local quality by enabling the thin client to make autonomous decisions for routine transaction processing based on pre-configured rules and cached data. The thin client can independently communicate with portable devices and process transactions locally, improving speed. Meanwhile, the remote computer retains overall system control by managing configuration, security policies, and exception handling, thus balancing local autonomy with centralized control.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS12106278B2Rules engine for communication round trips optimization of kernel-in-cloud payment transaction
Publication Date: 2024.10.01 VISA INTERNATIONAL SERVICE ASSOCIATION
  • US12106278B2 patent drawing
  • US12106278B2 patent drawing
  • US12106278B2 patent drawing

AI summary

A thin client may be utilized to facilitate data exchanges between two devices (e.g., a remote computer and a portable device). In some embodiments, the two devices may utilize differing communications protocols. The thin client may further be configured with a rules engine that determines one or more actions to be performed in response to one or more stimuli. The thin client may manage the processing flow between the two devices according to one or more predefined rules that are interpretable by the rules engine. The rules may be pushed to the thin client via any suitable device enabling the functionality of the thin client to be configured and/or modified without having to update the hardware and/or software of the thin client.