Modification of terminal and service provider machines using an update server machine

What is this patent about?

'758 is related to the field of updating software on remote devices, specifically focusing on adapting transaction dialogues between a terminal and a service provider. The background involves the challenge of modifying software applications distributed across a network, especially when bandwidth is limited or physical access to devices is difficult. Traditional methods require recompiling and redistributing entire applications, which can be inefficient and costly.

The underlying idea behind '758 is to update the dialogue protocol between a terminal and a service provider by sending a small dialogue module that modifies existing code, rather than replacing the entire application. This module contains code that adapts the terminal and service provider applications to use a new sequence of prompts and data entries. Crucially, the core executable instructions of the applications remain unchanged, allowing for efficient updates even over low-bandwidth networks.

The claims of '758 focus on a method, system, and non-transitory computer readable storage medium for conducting a dialogue between a terminal and a service provider. The terminal displays a prompt using a terminal application, accepts user input, and communicates this information to the service provider. The key is receiving a dialogue module that replaces a portion of the existing code in the terminal application. This updated code then adapts the application to display a new prompt, modifying the dialogue sequence.

In practice, the terminal and service provider machines initially run applications with a set of computer-executable instructions and associated code (e.g., Java Bytecode) that define the dialogue. When an update is needed, an update server sends a dialogue module containing new code. This new code replaces or modifies the existing code on both the terminal and service provider machines, effectively changing the prompts, data entry fields, or even the graphical user interface of the transaction. The platform module, which interprets the code, remains untouched, avoiding the need for recompilation.

This approach differentiates itself from prior solutions by avoiding the need to transmit large software updates. Instead of sending an entirely new application, only the dialogue module, which is significantly smaller, needs to be transmitted. This is particularly advantageous in scenarios with limited bandwidth or high communication costs. The use of intermediate code, like Java Bytecode, allows the platform module to interpret the updated code without requiring processor-specific recompilation, making the update process more flexible and efficient.