System, method and computer program product for capturing touch events for a virtual mobile device platform

• US 10,459,772 B2
• Filed: 03/03/2017
• Issued: 10/29/2019
• Est. Priority Date: 01/22/2013
• Status: Active Grant

• Current Assignee: Hypori LLC
• Original Assignee: Intelligent Waves LLC
• Inventors: Vetter, Brian J., Gopi, Rajesh P., Arrieta, Galib
• Primary Examiner(s): Rayan, Mihir K
• Application Number:
  US15/449,708
• Publication Number:
  US 20170177420A1
• Time in Patent Office: 970 Days
• CPC Class Codes: G06F 21/83 input devices, e.g. keyboards, mice or controllers thereof
• CPC Class Codes: G06F 3/0416 Control or interface arrangements specially adapted for digitisers
• CPC Class Codes: G06F 3/04883 for inputting data by handwriting, e.g. gesture or text
• CPC Class Codes: G06F 9/52 Program synchronisation; Mutual exclusion, e.g. by means of semaphores

Abstract

Embodiments disclosed herein can allow a user of mobile device in a network environment to switch between using public network services and using private network services. To access private network services, a virtualization cloud client application running on mobile device connects to a virtualized device hosted in virtualization cloud and brokers access to private network services as well as local device functions. Embodiments disclosed herein provide a system, method, and computer program product for capturing touch events for a virtual mobile device platform and relaying the captured touch events to the virtual mobile device platform while ensuring that movements and speed of touch events are accurately represented at the virtual mobile device platform.

Claims

1. A method for processing touch events, the method comprising:

receiving, by a server computer, a touch event message from a mobile device, the touch event message comprising touch events and timing information; and

dispatching the touch events to a software stack, the dispatching performed by a process at the server computer, wherein the process sleeps between dispatches of the touch events for a duration determined by the timing information in the touch event message to thereby construct data points that closely match a set of data points collected at the mobile device, the timing information relating to time elapsed between adjacent touch events captured at the mobile device.

2. The method according to claim 1, wherein the process creates a lock object and invokes a secondary thread and wherein once the touch event message is received, the lock object acquires a lock to prevent the secondary thread from moving past the lock and prematurely performing the dispatching.

3. The method according to claim 1, wherein the process determines whether two or more touch pointers were received for a touch event and wherein:

when the two or more touch pointers were received, the process adds the touch event to a queue and the queue is dispatched to the software stack; and

when only one touch pointer was received, the process determines whether the touch event was a touch down event.

4. The method according to claim 3, wherein if the touch event was the touch down event, the touch event is added to the queue, the queue is dispatched to the software stack, a lock is released, and the process waits for a next touch event message, and wherein if the touch event was not the touch down event, the process determines if the touch event is a touch up event.

5. The method according to claim 4, wherein if the touch event was the touch up event, the touch event is added to the queue, the queue is dispatched to the software stack, the lock is released, and the process waits for the next touch event message.

6. The method according to claim 4, wherein if the touch event was not the touch up event, the process considers the touch event is a touch move event and analyzes a speed of a touch move relative to a previous touch event, wherein if the speed is less than a threshold speed, the touch event is added to the queue, the queue is dispatched to the software stack, the lock is released, and the process waits for the next touch event message, and wherein if the speed is not less than the threshold speed, the touch event is added to the queue, the lock is released, a wake up signal is sent to a secondary thread, and the process waits for the next touch event message.

7. The method according to claim 6, wherein when the wake up signal is received, the secondary thread sleeps for a constant of milliseconds, acquires the lock, and determines a number of events in the queue, wherein if the number of events in the queue is zero, the secondary thread releases the lock and waits for another wakeup signal, wherein if the number of events in the queue is one, the secondary thread starts a dispatch subroutine to dispatch the queue to the software stack, releases the lock, and waits for another wakeup signal, and wherein if the number of events in the queue is greater than one, the process determines whether a last event was a touch up event.

8. The method according to claim 7, wherein if the last event was the touch up event, the secondary thread releases the lock and waits for another wakeup signal, and wherein if the last event was not the touch up event, the process determines a time that touch events have been captured and stored in the queue.

9. The method according to claim 8, wherein if the time determined by the process is greater than a maximum hold time, the dispatch subroutine is started to dispatch the queue to the software stack, the lock is released, and the secondary thread waits for another wakeup signal, and wherein if the time determined by the process is not greater than the maximum hold time, the secondary thread releases the lock and waits for another wakeup signal.

10. The method according to claim 1, wherein the touch event message further comprises time stamp data associated with the touch events and wherein the server computer performs a speed analysis of the touch events utilizing the time stamp data associated with the touch events.

11. A computer program product for processing touch events, the computer program product comprising at least one non-transitory computer readable medium storing instructions translatable by a computer to perform:

receiving a touch event message from a mobile device, the touch event message comprising touch events and timing information; and

dispatching the touch events to a software stack, the dispatching performed by a process at the computer, wherein the process sleeps between dispatches of the touch events for a duration determined by the timing information in the touch event message to thereby construct data points that closely match a set of data points collected at the mobile device, the timing information relating to time elapsed between adjacent touch events captured at the mobile device.

12. The computer program product of claim 11, wherein the process creates a lock object and invokes a secondary thread and wherein once the touch event message is received, the lock object acquires a lock to prevent the secondary thread from moving past the lock and prematurely performing the dispatching.

13. The computer program product of claim 11, wherein the process determines whether two or more touch pointers were received for a touch event and wherein:

when the two or more touch pointers were received, the process adds the touch event to a queue and the queue is dispatched to the software stack; and

when only one touch pointer was received, the process determines whether the touch event was a touch down event.

14. The computer program product of claim 13, wherein if the touch event was the touch down event, the touch event is added to the queue, the queue is dispatched to the software stack, a lock is released, and the process waits for a next touch event message, and wherein if the touch event was not the touch down event, the process determines if the touch event is a touch up event.

15. The computer program product of claim 14, wherein if the touch event was the touch up event, the touch event is added to the queue, the queue is dispatched to the software stack, the lock is released, and the process waits for the next touch event message.

16. The computer program product of claim 14, wherein if the touch event was not the touch up event, the process considers the touch event is a touch move event and analyzes a speed of a touch move relative to a previous touch event, wherein if the speed is less than a threshold speed, the touch event is added to the queue, the queue is dispatched to the software stack, the lock is released, and the process waits for the next touch event message, and wherein if the speed is not less than the threshold speed, the touch event is added to the queue, the lock is released, a wake up signal is sent to a secondary thread, and the process waits for the next touch event message.

17. The computer program product of claim 16, wherein when the wake up signal is received, the secondary thread sleeps for a constant of milliseconds, acquires the lock, and determines a number of events in the queue, wherein if the number of events in the queue is zero, the secondary thread releases the lock and waits for another wakeup signal, wherein if the number of events in the queue is one, the secondary thread starts a dispatch subroutine to dispatch the queue to the software stack, releases the lock, and waits for another wakeup signal, and wherein if the number of events in the queue is greater than one, the process determines whether a last event was a touch up event.

18. The computer program product of claim 17, wherein if the last event was the touch up event, the secondary thread releases the lock and waits for another wakeup signal, and wherein if the last event was not the touch up event, the process determines a time that touch events have been captured and stored in the queue.

19. The computer program product of claim 18, wherein if the time determined by the process is greater than a maximum hold time, the dispatch subroutine is started to dispatch the queue to the software stack, the lock is released, and the secondary thread waits for another wakeup signal, and wherein if the time determined by the process is not greater than the maximum hold time, the secondary thread releases the lock and waits for another wakeup signal.

20. The computer program product of claim 11, wherein the touch event message further comprises time stamp data associated with the touch events and wherein the computer performs a speed analysis of the touch events utilizing the time stamp data associated with the touch events.