# US 2015/0177866 A1 · Multiple Hover Point Gestures

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0177866 A1
- Document ID: US20150177866A1
- Status: Published application
- Kind: A1
- Application number: 14/138,238
- Filed: 2013-12-23
- Published: 2015-06-25
- Earliest claimed: 2013-12-23
- Applicants: Microsoft Corporation
- Inventors: Dan Hwang; Scott Greenlay; Christopher Fellowes; Bob Schriver
- Web page: https://patentgrep.com/patent/US20150177866A1

## CPC

- G06F 3/042: by opto-electronic means
- G06F 3/017: {Gesture based interaction, e.g. based on a set of recognized hand gestures (interaction based on gestures traced on a digitiser G06F3/04883)}
- G06F 3/0488: using a touch-screen or digitiser, e.g. input of commands through traced gestures
- G06F 3/04883: for inputting data by handwriting, e.g. gesture or text
- G06F 2203/04101: 2.5D-digitiser, i.e. digitiser detecting the X/Y position of the input means, finger or stylus, also when it does not touch, but is proximate to the digitiser's interaction surface and also measures the distance of the input means within a short range in the Z direction, possibly with a separate measurement setup
- 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
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Example apparatus and methods concern detecting and responding to a multiple hover point gesture performed for a hover-sensitive device. An example apparatus may include a hover-sensitive input/output interface configured to detect multiple objects in a hover-space associated with the hover-sensitive input/output interface. The apparatus may include logics configured to identify an object in the hover-space, to characterize an object in the hover-space, to track an object in the hover-space, to identify a multiple hover point gesture based on the identification, characterization, and tracking, and to control a device, application, interface, or object based on the multiple hover point gesture. In different embodiments, multiple hover point gestures may be performed in one, two, three, or four dimensions. In one embodiment, the apparatus may be event driven with respect to handling gestures.

## Claims

### Claim 1

A method, comprising:
detecting a plurality of hover points in a hover-space associated with a hover sensitive input/output interface associated with an apparatus;
producing independent characterization data for members of the plurality of hover points;
producing independent tracking data for members of the plurality of hover points; and
identifying a multiple hover point gesture based, at least in part, on the characterization data and the tracking data.

### Claim 2 (depends on 1)

The method of claim 1, where the plurality of hover points includes up to ten hover points.

### Claim 3 (depends on 1)

The method of claim 1, where detecting the plurality of hover points is performed without using a camera or a touch sensor.

### Claim 4 (depends on 1)

The method of claim 1, where the characterization data for a member of the plurality of hover points describes an x position in the hover-space for the member, a y position in the hover-space for the member, a z position in the hover-space for the member, an x length measurement for the member, a y length measurement for the member, an amount of time the member has been at the x position, an amount of time the member has been at the y position, an amount of time the member has been at the z position, a likelihood that the member is a finger, a likelihood that the member is a thumb, or a likelihood that the member is a portion of a hand other than a finger or thumb.

### Claim 5 (depends on 1)

The method of claim 1, where the characterization data is produced without using a camera or a touch sensor.

### Claim 6 (depends on 1)

The method of claim 1, where the characterization data is produced without reference to an object displayed on the apparatus.

### Claim 7 (depends on 1)

The method of claim 1, where the tracking data for a member of the plurality of hover points describes an x position in the hover-space for the member, a y position in the hover-space for the member, a z position in the hover-space for the member, an x movement amount for the member, a y movement amount for the member, a z movement amount for the member, an x motion rate for the member, a y motion rate for the member, a z motion rate for the member, an x motion duration for the member, a y motion duration for the member, or a z motion duration for the member.

### Claim 8 (depends on 1)

The method of claim 1, where the tracking data for a member of the plurality of hover points describes a correlation between movement of the member and movement of one or more other members of the plurality.

### Claim 9 (depends on 1)

The method of claim 1, where the tracking data is produced without using a camera or a touch sensor and where the tracking data is produced without reference to an object displayed on the apparatus.

### Claim 10 (depends on 1)

The method of claim 1, where the multiple hover point gesture is a gather gesture, a spread gesture, a crank gesture, a roll gesture, a ratchet gesture, a poof gesture, or a sling shot gesture.

### Claim 11 (depends on 1)

The method of claim 1, comprising generating a control event based on the multiple hover point gesture.

### Claim 12 (depends on 11)

The method of claim 11, where the control event controls whether the apparatus is turned on or off, controls whether a portion of the apparatus is turned on or off, controls a volume associated with the apparatus, controls a brightness associated with the apparatus, controls whether a transmitter associated with the apparatus is turned on or off, controls whether a receiver associated with the apparatus is turned on or off, controls whether a transceiver associated with the apparatus is turned on or off, or controls whether an application running on the apparatus is on or off.

### Claim 13 (depends on 11)

The method of claim 11, where the control event controls the appearance of an object displayed on the apparatus.

### Claim 14 (depends on 11)

The method of claim 11, comprising determining a time period for which the control event is to be active based, at least in part, on a rate of motion described in the tracking data.

### Claim 15

A computer-readable storage medium storing computer-executable instructions that when executed by a computer cause the computer to perform a method, the method comprising:
detecting a plurality of hover points in a hover-space associated with a hover sensitive input/output interface associated with an apparatus, where the plurality of hover points includes up to ten hover points, and where detecting the plurality of hover points is performed without using a camera or a touch sensor;
producing independent characterization data for members of the plurality of hover points, where the characterization data for a member of the plurality of hover points describes an x position in the hover-space for the member, a y position in the hover-space for the member, a z position in the hover-space for the member, an x length measurement for the member, a y length measurement for the member, an amount of time the member has been at the x position, an amount of time the member has been at the y position, an amount of time the member has been at the z position, a likelihood that the member is a finger, a likelihood that the member is a thumb, or a likelihood that the member is a portion of a hand other than a finger or thumb, where the characterization data is produced without using a camera or a touch sensor, and where the characterization data is produced without reference to an object displayed on the apparatus;
producing independent tracking data for members of the plurality of hover points, where the tracking data for a member of the plurality of hover points describes an x position in the hover-space for the member, a y position in the hover-space for the member, a z position in the hover-space for the member, an x movement amount for the member, a y movement amount for the member, a z movement amount for the member, an x motion rate for the member, a y motion rate for the member, a z motion rate for the member, an x motion duration for the member, a y motion duration for the member, or a z motion duration for the member, where the tracking data for a member of the plurality of hover points describes a correlation between movement of the member and movement of one or more other members of the plurality, where the tracking data is produced without using a camera or a touch sensor, and where the tracking data is produced without reference to an object displayed on the apparatus;
identifying a multiple hover point gesture based, at least in part, on the characterization data and the tracking data, where the multiple hover point gesture is a gather gesture, a spread gesture, a crank gesture, a roll gesture, a ratchet gesture, a poof gesture, or a sling shot gesture; and
generating a control event based on the multiple hover point gesture, where the control event controls whether the apparatus is turned on or off, controls whether a portion of the apparatus is turned on or off, controls a volume associated with the apparatus, controls a brightness associated with the apparatus, controls whether a transmitter associated with the apparatus is turned on or off, controls whether a receiver associated with the apparatus is turned on or off, controls whether a transceiver associated with the apparatus is turned on or off, or controls whether an application running on the apparatus is on or off.

### Claim 16

An apparatus, comprising:
a processor,
a hover-sensitive input/output interface configured to produce a hover event associated with an object in a hover-space associated with the hover-sensitive input/output interface;
a memory configured to store data associated with the hover event;
a set of logics configured to process events associated with a multiple hover point gesture; and
an interface configured to connect the processor, the hover-sensitive input/output interface, the memory, and the set of logics;
the set of logics including:
a first logic configured to handle the hover event;
a second logic configured to detect a multiple hover point gesture based, at least in part, on two or more hover events generated by two or more objects in the hover-space; and
a third logic configured to generate a control event associated with the multiple hover point gesture,
where the first logic, second logic, and third logic operate without referencing touch sensor data and without referencing camera data.

### Claim 17 (depends on 16)

The apparatus of claim 16, where the first logic handles the hover event by generating data for the object that caused the hover event, the data including position data, path data, and tracking data.

### Claim 18 (depends on 17)

The apparatus of claim 17, where the second logic detects a multiple hover point gesture by correlating movements between the two or more objects, where the movements are correlated as a function of analyzing the position data, the path data, or the tracking data.

### Claim 19 (depends on 18)

The apparatus of claim 18, where the control event is a gather event, a spread event, a crank event, a roll event, a ratchet event, a poof event, or a slingshot event, and where the control event is configured to control the apparatus, a radio associated with the apparatus, a social media circle associated with a user of the apparatus, a transmitter associated with the apparatus, a receiver associated with the apparatus, or a process being performed by the apparatus, and where the control event includes a time period over which the control event is to exert control, where the time period is based, at least in part, on a rate of motion described in the path data.

### Claim 20 (depends on 19)

The apparatus of claim 19, comprising a fourth logic configured to manage a state machine associated with the multiple hover point gesture, where managing the state machine includes transitioning a process or data structure from a first multiple hover point state to a second, different multiple hover point state in response to detecting a portion of a multiple hover point gesture.
