Browse Prior Art Database

Input Command Disambiguation By Option Subset Provision

IP.com Disclosure Number: IPCOM000237835D
Publication Date: 2014-Jul-16
Document File: 2 page(s) / 44K

Publishing Venue

The IP.com Prior Art Database

Abstract

It is not uncommon for user interaction to result in the user pressing multiple command options at the same time, resulting in non-deterministic behaviour. Herein disclosed is a method that enables a user to disambiguate over the multiply selected command options without interrupting their workflow. In the case of hand held touch devices, this enables single handed operation and consequent increase in user experience.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 51% of the total text.

Page 01 of 2

Input Command Disambiguation By Option Subset Provision

Occasionally when a user is interacting with an input device, the user may press multiple command options (as is the case with "fat finger error" http://www.investopedia.com/terms/f/fat-finger-error.asp) or provide an ambiguous touch based command. In such cases the wrong command may be executed by the device, which can hinder work flow or at the very least provide a source of frustration.

    Mobile devices, or touch screen driven operations, have the issues of finger "roll-off" and the touch spread of a single touch interaction. Roll-off situations result in the last point of touch becoming the focus of the interaction, and touch spread can result in multiple interaction points being unintentionally interacted with. Typical scenarios here relate to:
Navigating to the wrong URL
Selecting the wrong contact
Zooming in on an area instead of rotating
Current solutions for this problem attempt to remove the possibility of the occurrence of pressing multiple items, for instance: mobile devices enable voice interaction, such as Siri (http://en.wikipedia.org/wiki/Siri), video capture gesture recognition (http://www.pointgrab.com/1304/gesture-recognition-the-next-big-thing-for- smartphones-after-touch/, http://www.researchgate.net/publication/220982825_Variations_on_a_fuzzy_logic_gesture_ recognition_algorithm),
or the installation of a "fat finger" keyboard application (https://play.google.com/store/apps/details?id=com.bobby.brennan.fatfingerskeyboard); PCs enable rebinding of keys or re-specifying control combinations to enable a user to interact with a new set of shortcut combinations that are less likely to be pressed
at the same time by mistake (http://www.microsoft.com/hardware/en-us/help/support/how-to/keyboard/reassign-keys).

    Alternative solutions provided by mobile devices enable automatic "zoom in" on a region if a number of interaction nodes within an area of the interaction screen exceeds a set limit. Again this is an example of trying to avoid the situation and not the provision of a solution in cases where a user has provided ambiguous control commands over a continuous interaction period.

    What is missing is the ability to disambiguate over a set of possible actions that may relate to the most recent command interaction with the input device, which may be in the form of keyboard inputs, touch or gesture interaction.

    It is assumed that a user is interacting with a generic device, which may or may not involve touch interactions. If a user interaction is ambiguous, in that detected user inputs...