SYSTEM AND METHOD FOR PROVIDING A USER INTERACTION INTERFACE USING A MULTI-TOUCH GESTURE RECOGNITION ENGINE

• US 20140002394A1
• Filed: 06/25/2013
• Published: 01/02/2014
• Est. Priority Date: 07/02/2012
• Status: Active Grant

• Current Assignee: Datapath Limited (Datapath Holdings Ltd.)
• Original Assignee: Datapath Limited (Datapath Holdings Ltd.)
• Inventors: Nancke-Krogh, Anders, Nancke-Krogh, Nina
• Granted Patent: US 9,785,338 B2
• Time in Patent Office: Days
• US Class Current: 345/173
• CPC Class Codes: G06F 2203/04808 Several contacts: gestures triggering a specific function, e.g. scrolling, zooming, right-click, when the user establishes several contacts with the surface simultaneously; e.g. using several fingers or a combination of fingers and pen
• CPC Class Codes: G06F 3/0488 using a touch-screen or digitiser, e.g. input of commands through traced gestures
• CPC Class Codes: G06F 3/04883 for inputting data by handwriting, e.g. gesture or text

Abstract

Described herein are systems and methods for enabling a multi-touch gesture recognition engine, where gesture recognition can be made based on touch or motion detection. In accordance with an embodiment the system include a hardware input list delivered from the hardware sensor(s), a touchobject list delivered from the application(s)/OS and logic to calculate and determine gestures based on mapping touchpoints from the sensor(s) with touchobjects from the application(s) in a time perspective. The engine can use a generic state machine in each gestureobject to keep track of the status of the gestureobject independently. Additional embodiments are also described herein.

Claims

1. A system for enabling a gesture recognition engine, comprising:

a computer system, including one or more processors;

a display having a computer desktop area; and

one or more components or logic for collecting and/or calculating one or more touch, motion, or other input points, delivered from a hardware sensor, wherein the system then transforms the input points to gestures that are delivered to an application layer for rendering.

2. The claim 1, wherein the input points are touch points.

3. The claim 1, wherein the input points are motion points.

4. The system of claim 1, wherein the system calculates one or more touch, motion or other input points, and

wherein the calculation can use coordinates delivered from the hardware sensor as inputs to the calculation, and/or include a time perspective to the calculation, and/or wherein inputs can be received with the speed of the hardware sensor, and

wherein the logic can determine, based on the input points, the order they were received and/or factors such as velocity, acceleration and/or angle, a path/direction which can be used for additional calculations, to predict where input points will show up over time, and/or to link input points that the hardware sensor was unable to link.

5. The system of claim 1, wherein information about application objects is collected from the application layer, wherein the application layer defines each application object including information such as its area, layer and/or which gesture objects it subscribes to, and wherein the system stores the information in a list for use in calculation, and wherein the application layer can inform the system about updated positions, change of area or layer and the system updates the list accordingly.

6. The system of claim 1, wherein one or more touch, motion, or other input points can be grouped based on a set of rules, where the assumed distance between a user'"'"'s fingers, and the assumed maximum time between a user'"'"'s finger touching an object can be taken into account.

7. The system of claim 1, wherein the system calculates which gesture object is created, and what state each gesture object has, and wherein each gesture object runs through a generic state machine, and some gesture objects run through additional defined state machines depending on the definition of the gesture object, and wherein the logic can then map a gesture object with an application object, and, depending on the state of the gesture object, the logic sends events to the application layer.

8. A method for enabling a multi-touch gesture recognition engine, comprising:

providing a display having a computer desktop area; and

providing one or more components or logic for collecting and/or calculating one or more touch, motion, or other input points, delivered from a hardware sensor, and transforming the input points to gestures that are delivered to an application layer for rendering.

9. The method of claim 8, wherein the input points are touch points.

10. The method of claim 8, wherein the input points are motion points.

11. The method of claim 8, including calculating one or more touch, motion or other input points, and

wherein the calculation can use coordinates delivered from the hardware sensor as inputs to the calculation, and/or include a time perspective to the calculation, and/or wherein inputs can be received with the speed of the hardware sensor, and

wherein the logic can determine, based on the input points, the order they were received and/or factors such as velocity, acceleration and/or angle, a path/direction which can be used for additional calculations, to predict where input points will show up over time, and/or to link input points that the hardware sensor was unable to link.

12. The method of claim 8, wherein information about application objects is collected from the application layer, wherein the application layer defines each application object including information such as its area, layer and/or which gesture objects it subscribes to, and wherein the method includes storing the information in a list for use in calculation, and wherein the application layer can inform about updated positions, change of area or layer and the list updated accordingly.

13. The method of claim 8, wherein one or more touch, motion, or other input points can be grouped based on a set of rules, where the assumed distance between a user'"'"'s fingers, and the assumed maximum time between a user'"'"'s finger touching an object can be taken into account.

14. The method of claim 8, including calculating which gesture object is created, and what state each gesture object has, and wherein each gesture object runs through a generic state machine, and some gesture objects run through additional defined state machines depending on the definition of the gesture object, and wherein the logic can then map a gesture object with an application object, and, depending on the state of the gesture object, the logic sends events to the application layer.

15. A non-transitory computer readable medium, including instructions stored thereon which when read and executed by one or more computers cause the one or more computers to perform the steps comprising:

providing a display having a computer desktop area; and

providing one or more components or logic for collecting and/or calculating one or more touch, motion, or other input points, delivered from a hardware sensor, and transforming the input points to gestures that are delivered to an application layer for rendering.