Thin Client Transaction System with Security Gateway

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional EFTPOS terminals are bulky, expensive, and limited in functionality, making them unaffordable and difficult to use for small merchants and mobile professionals, and they do not support secure transactions across multiple locales or various types of transactions beyond payment acquisition.

Innovation Solution

A system comprising a thin client device (TCD) and a system server that enables secure transactions using a first and second security scheme, allowing identity validation, transaction requests, and data storage, with compatibility across multiple communication links and card types, including magnetic stripe, smart cards, and near-field communication, while being compliant with banking industry standards for security and interoperability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If conventional EFTPOS terminals are used, then secure payment transactions can be processed, but the devices become bulky, expensive, and complex

Engineering Contradiction:
Improvesecure payment transaction processingVSAvoidterminal complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a security gateway as an intermediary component that mediates between the thin client device and the payment processing system. The gateway handles complex security protocols, card validation, and transaction routing, allowing the thin client to remain simple while maintaining secure transaction processing capabilities through the gateway's intermediary functions

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical complexity of conventional EFTPOS terminals with a software-based security model. Instead of embedding complex hardware security mechanisms in the terminal, the system uses software security protocols, encryption, and validation mechanisms that run on the security gateway and server, substituting physical complexity with computational security

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If conventional EFTPOS terminals are used, then payment transactions can be processed, but the devices become expensive and unaffordable for small merchants

Engineering Contradiction:
Improvepayment transaction processingVSAvoidaffordability for small merchants
Core Design Contradiction:
ReliabilityVSEase of manufacture

Solution Approach 1:

The patent segments the payment processing system into separate functional components: a simple thin client device for the merchant, a security gateway for processing, and a server for management. This segmentation allows the merchant to purchase only the inexpensive thin client hardware while the gateway and server infrastructure is maintained separately, making the solution affordable for small merchants

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent uses a thin client architecture that copies only the essential display and input functions to the merchant's device, while the processing intelligence is copied to the security gateway and server. This allows the merchant to have a simple, low-cost device that connects to a centralized processing system, reducing hardware costs significantly

Inventive Principle:
Principle #26Copying

3Productivity

If conventional EFTPOS terminals are used, then payment acquisition can be performed, but the devices are limited in functionality and cannot support other secure transactions

Engineering Contradiction:
Improvepayment acquisition capabilityVSAvoidtransaction type flexibility
Core Design Contradiction:
ProductivityVSAdaptability or versatility

Solution Approach 1:

The patent implements a universal thin client device that can perform multiple functions beyond payment processing. The device can conduct EFTPOS transactions, access personal financial accounts, view medical and insurance information, and engage in online gaming and auctions, all through a single interface that connects to various services via the security gateway, providing multi-functionality without requiring separate specialized devices

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

4Reliability

If conventional EFTPOS terminals are used, then local compliance can be enforced, but the terminals cannot operate in multiple countries

Engineering Contradiction:
Improvelocal regulation complianceVSAvoidmulti-locale operability
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The security gateway acts as an intermediary that enforces local compliance regulations while maintaining universal operability. The gateway translates and adapts transaction protocols to meet different country-specific requirements, allowing the thin client to operate in multiple locales without requiring device-specific configuration for each region

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The system uses dynamic protocol adaptation where the security gateway can change its behavior and communication protocols based on the detected location and local regulations. The thin client maintains a consistent interface while the gateway dynamically adjusts security protocols, validation rules, and communication methods to comply with different country requirements, enabling multi-locale operability

Inventive Principle:
Principle #15Dynamics

Data Source

PatentEP2212842B1System and method for secure management of transactions
Publication Date: 2014.06.18 GMX
  • EP2212842B1 patent drawingFigure 1a~1b
  • EP2212842B1 patent drawingFigure 2a~2b
  • EP2212842B1 patent drawingFigure 3

AI summary

Secure management of electronic transactions is provided by a system server that is communicatively coupled to terminals configured as thin client devices (TCD) and to one or more application servers. A TCD completes a secure communications link with the system server, and transfers information concerning the identity of a user and account information from a secure transaction card (STC). Upon authentication, the system server drives the display of available applications at the TCD, allowing the user to select and engage in a desired transaction with the application server hosting the selected application. During the transaction, the system server brokers communications according to the different security schemes used by the TCD and the application server and, ultimately, stores a transaction ticket that memorializes the transaction. The transaction ticket can later be retrieved by presenting appropriate authentication information.