Thin-Client Self-Service Terminal Using Custom Structured Tags
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Thick client self-service terminals require complex software implementations and individualized updates, leading to cumbersome deployment and potential security issues, as well as increased resource usage and programming difficulties due to the need for separate Java applets or Active-X controls for each client.
Innovation Solution
Implementing a thin-client self-service terminal that uses customized structured markup language tags to interact with remote servers, reducing local processing requirements and allowing standard browsers to interpret these tags, thereby simplifying maintenance and updates by performing most operations on a remote server.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If thick client self-service terminals are used with Java applets or Active-X controls, then local processing capabilities are improved, but device complexity and ease of manufacture deteriorate due to individualized software updates and testing requirements
Solution Approach 1:
The patent extracts the complex processing logic from the client terminal and relocates it to a centralized server. The client terminal is reduced to a thin client that only handles basic input/output operations, while all application logic, data processing, and business rules are executed on the server. This eliminates the need for Java applets or Active-X controls on each client, resolving the contradiction between local processing power and software complexity.
Solution Approach 2:
The patent implements a universal server-side platform that serves multiple client terminals with identical functionality. A single software deployment on the server provides services to all clients, eliminating the need for individualized software updates and testing for each client device. This universal approach resolves the complexity issue while maintaining consistent processing capabilities across all terminals.
2Adaptability or versatility
If thick client terminals are deployed with individualized software, then client functionality is improved, but ease of operation and maintenance worsen due to cumbersome updates across multiple clients
Solution Approach 1:
By extracting all application software from the client terminals and consolidating it on a centralized server, the patent eliminates the maintenance burden of updating multiple individual clients. The server becomes the single point of software management, where updates, patches, and functionality enhancements are deployed once and immediately available to all clients. This resolves the contradiction between client functionality and ease of maintenance.
Solution Approach 2:
The patent uses the server as a master copy that all client terminals access and replicate locally in memory during runtime. Rather than installing permanent software copies on each client, the thin clients dynamically load and execute software from the server, ensuring all clients always run the latest version without manual updates. This copying approach simplifies maintenance while preserving full client functionality.
3Power
If thick client implementations are used, then local processing power is improved, but resource usage increases and security concerns arise
Solution Approach 1:
The patent extracts heavy processing operations from resource-constrained client terminals and relocates them to a powerful centralized server with abundant computational resources. The thin clients only perform lightweight tasks such as displaying information and capturing user input, while all data processing, transaction processing, and complex calculations are executed on the server. This resolves the contradiction between local processing power and resource consumption by centralizing computational demands.
Data Source
AI summary
Systems and methods for processing custom structured tags at a self-service terminal are disclosed. Custom structured tags received by a self-service terminal can include information to identify one or more devices attached to the terminal and identify one or more types of data to be obtained from a user by use of the attached devices. In some embodiments, a browser can natively interpret the custom structured tags. The self-service terminal can also be configured to receive and decode structured tags identifying or more actions to be performed by the device, such as printing a transaction record or dispensing currency.