# US 10,871,855 B2 · Area filtering for low-latency and high-latency input event paths from a single touch sensor

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

- Number: US 10,871,855 B2
- Document ID: US10871855B2
- Status: Granted
- Kind: B2
- Application number: 16/364,145
- Filed: 2019-03-25
- Published: 2019-07-18
- Granted: 2020-12-22
- Earliest claimed: 2016-02-02
- Assignees: Tactual Labs Co.
- Applicants: Tactual Labs Co.
- Inventors: Bruno Rodrigues De Araujo; Ricardo Jorge Jota Costa; Clifton Forlines; Steven Leonard Sanders
- Web page: https://patentgrep.com/patent/US10871855B2

## CPC

- G06F 3/0416: {Control or interface arrangements specially adapted for digitisers}
- G06F 3/0418: {for error correction or compensation, e.g. based on parallax, calibration or alignment}
- G06F 3/0488: using a touch-screen or digitiser, e.g. input of commands through traced gestures
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In an embodiment, a touch surface, such as a GUI is graphically divided into two or more input regions, and based on this division, input event paths from a single sensor can be integrated within an operating system to provide application developers with the ability to easily and effectively filter there-between. The graphical division allows an application developer to specify which elements of a given GUI take one path, versus another. In an embodiment, low-latency and high-latency event paths are provided; an algorithm takes into consideration input regions and, based on those regions, handles the low- and high-latency input event paths in a computer system, directing the appropriate inputs through the appropriate processing, and directing the output to the appropriate process or queue without creating constraints on the low-latency event processing due to the presence of higher-latency event paths for a given sensor.

## Claims

### Claim 1

A device, comprising:
a computer system comprising a low-latency path for touch data and at least one other latency path for touch data;
a sensor operatively connected to an interface of the computer system, wherein the interface of the computer system is configured to receive touch-related information from the sensor, and to output touch data; and
a routing process configured to receive the touch data from the interface, and to route the touch data matching a region descriptor to the low-latency path for touch data.

### Claim 2 (depends on 1)

The device of claim 1, wherein the low-latency path is predefined.

### Claim 3 (depends on 1)

The device of claim 1, wherein the low-latency path is associated with a region descriptor.

### Claim 4 (depends on 1)

The device of claim 1, wherein the low-latency path is defined during an OS registration process performed by an application.

### Claim 5 (depends on 1)

The device of claim 1, wherein the low-latency path is predefined, and associated with an OS registration process performed by an application.

### Claim 6 (depends on 1)

The device of claim 1, wherein the low-latency path is defined by an application.

### Claim 7 (depends on 1)

The device of claim 1, wherein the low-latency path is defined by an OS running on the computer system.

### Claim 8 (depends on 1)

The device of claim 1, wherein touch data routed to at least one other latency path is further processed along with other touch data routed to the at least one other latency path.

### Claim 9 (depends on 1)

The device of claim 1, wherein touch data routed to at least one other latency path is decimated to provide a smaller number of events to a recipient of the at least one other latency processes.

### Claim 10 (depends on 1)

The device of claim 1, wherein touch data routed to at least one other latency path is aggregated to provide a smaller number of events to a recipient of the at least one other latency processes.

### Claim 11

A method of managing data from a sensor, the method comprising:
identifying a first region on a sensor based on a region descriptor, the first region comprising less than the entire sensor;
providing a low-latency path for processing data;
receiving input information from the sensor;
identifying at least one event from the input information;
determining whether the event is associated with the first region; and
routing the event to a low-latency touch path if the event is associated with the first region.

### Claim 12 (depends on 11)

The method of claim 11, wherein the low-latency path is predefined.

### Claim 13 (depends on 11)

The method of claim 11, wherein the low-latency path is associated with a region descriptor.

### Claim 14 (depends on 11)

The method of claim 11, wherein the low-latency path is defined during an OS registration process performed by an application.

### Claim 15 (depends on 11)

The method of claim 11, wherein the low-latency path is predefined, and associated with an OS registration process performed by an application.

### Claim 16 (depends on 11)

The method of claim 11, wherein the low-latency path is defined by an application.

### Claim 17 (depends on 11)

The method of claim 11, wherein the low-latency path is defined by an OS running on the computer system.

### Claim 18

A method of managing touch data from a sensor adapted to route a touch event to a low-latency touch path for processing touch data if the touch event is associated with a low-latency region and routing the touch event to another latency touch path different from the low-latency touch path for processing touch data if the touch event is associated with a second region different than the low-latency region, the method comprising:
defining at least two regions on the sensor based on at least one region descriptor such that there are defined at least the low-latency region and the second region;
providing a low-latency path for processing touch data from the low-latency region;
receiving touch-related information from the sensor;
identifying at least one touch event from the touch-related information;
routing the touch event to the low-latency touch path for processing touch data if the touch event is associated with the low-latency region.

### Claim 19 (depends on 18)

The method of claim 18, wherein the low-latency path is predefined.

### Claim 20 (depends on 18)

The method of claim 18, wherein the low-latency path is defined during an OS registration process performed by an application.