Patent No. US8572571 (titled "Modification of terminal and service provider machines using an update server machine") on Jul 21, 2010. The application was issued on Oct 29, 2013.
'571 is related to the field of updating software applications on remote devices, specifically focusing on adapting the dialogue between a terminal and a service provider. The background involves the challenge of modifying software on systems distributed over a wide area, where transmitting large software updates is impractical due to bandwidth limitations or logistical constraints. Existing systems require complete software application updates, which are inefficient and time-consuming, especially for devices connected via wireless networks.
The underlying idea behind '571 is to update the dialogue protocol between a terminal and a service provider by sending small 'dialogue modules' that modify only the code responsible for the user interface and data exchange, without altering the core application logic. This is achieved by separating the application into two parts: computer-executable instructions (the 'platform module') and interpretable code that defines the dialogue's prompts, data entry fields, and GUI elements. The dialogue module updates the latter, allowing for customization and adaptation of the dialogue without requiring a full software re-installation.
The claims of '571 focus on a system and method for updating a terminal machine and a service provider machine. The terminal machine runs a terminal application that displays prompts and accepts user data entries. The service provider machine runs a provider application that receives the user data entries. An update server sends a terminal dialogue module to the terminal machine and a provider dialogue module to the service provider machine. These modules modify the code responsible for the dialogue sequence, adapting the applications to use a new sequence of prompts and data entries, without modifying the underlying computer-executable instructions.
In practice, the invention allows for rapid and efficient customization of user interactions. For example, a bank could update the prompts on an ATM to reflect new services or regulatory changes without requiring a complete software update. The terminal application displays prompts to the user, accepts data entries, and communicates this information to the service provider. The service provider application receives the data, processes it, and determines the next prompt to send back to the terminal. The dialogue modules contain the updated prompts, data entry requirements, and GUI elements, which are then interpreted by the platform module to modify the user experience.
This approach differs significantly from prior solutions that require complete software updates. By only transmitting the dialogue modules, the system minimizes the amount of data transferred, making it feasible to update devices over low-bandwidth networks. Furthermore, the separation of the dialogue code from the core application logic allows for flexible customization without risking the stability of the underlying system. The use of interpretable code, such as Java Byte Code, enables the platform module to dynamically adapt the application's behavior based on the received dialogue module, providing a lightweight and efficient update mechanism.
In the late 2000s when ’571 was filed, the technical landscape was characterized by the increasing deployment of mobile devices and remote terminals at a time when software updates were typically implemented using full application re-installs. When systems commonly relied on the distribution of large, compiled executable binaries rather than granular logic updates, the limited bandwidth of wireless telecommunications networks made frequent or large-scale software modifications non-trivial. During this era, hardware and software constraints meant that updating the interaction flow between a remote device and a server generally required recompiling and redistributing the entire machine-executable codebase, as there was no standard mechanism for modifying high-level transaction dialogues without altering the underlying executable instructions.
The examiner allowed the application because the prior art did not demonstrate a system where an update server sends specific dialogue modules to both a terminal and a service provider to modify their interaction sequence. Specifically, the examiner noted that the prior art lacked the combination of a terminal application containing both executable instructions and a separate set of code, where the update module only modifies the code to change the sequence of prompts and data entries without altering the executable instructions that run directly on the processor. This distinction allows the terminal and provider to conduct a modified dialogue sequence by updating only the non-executable code components.
The patent has 31 claims, with independent claims 1, 2, and 29. These independent claims are generally directed to a method and systems for updating terminal and service provider machines to conduct dialogues, focusing on modifying code within applications on these machines via an update server. The dependent claims generally elaborate on the system components, types of code, and specific functionalities related to the dialogue updates and interactions between the terminal and service provider machines.
Definitions of key terms used in the patent claims.
US Latest litigation cases involving this patent.

The dossier documents provide a comprehensive record of the patent's prosecution history - including filings, correspondence, and decisions made by patent offices - and are crucial for understanding the patent's legal journey and any challenges it may have faced during examination.
Get instant alerts for new documents