Force sensing and inadvertent input control of an input device

Information

  • Patent Grant
  • 10416799
  • Patent Number
    10,416,799
  • Date Filed
    Wednesday, June 3, 2015
    9 years ago
  • Date Issued
    Tuesday, September 17, 2019
    5 years ago
Abstract
Inadvertent input control techniques are described. In one or more implementations, techniques are described that leverage force to determine a likelihood that a user intended to provide an input, e.g., a selection input (e.g., a “click”), gesture, lift off, and so forth. This is usable to identify taps, hovers, continuation of movement of a drag operation, and so on. Implementations are also discussed that leverage an n-manifold in the product space of contact size and signal strength that is usable to define a likelihood of whether a contact includes an application of force. A variety of other examples are also described, including cursor stability techniques that leverage force in order to control movement of a cursor.
Description
BACKGROUND

Detection of touch inputs may be utilized to support a variety of functionality. For example, trackpads may be found on a variety of different devices to support cursor control and gestures, such as on a laptop, removable keyboard cover for a tablet, and so on. In some instances, the trackpads also include functionality usable to initiate a selection (e.g., a “click”) and thus movement of a cursor and selections may be made by a user without requiring a user to remove a finger from the trackpad to press a separate button. Touch functionality may also be included in a variety of other devices, such as part of a touchscreen of a mobile phone or tablet, keyboard sensor array, and so on.


In some instances, however, a user may inadvertently provide a touch input, which could interfere with the user's experience. For example, a user may type on a keyboard and “hover” a finger over the trackpad, which may then result in an inadvertent tap due to fatigue, being jostled, and so forth. In the case of composing a document, this may cause a cursor to be moved elsewhere in the document. If the user does not notice this movement, the typing may continue at that point, which may be frustrating. These frustrations may also be encountered in other situations, such as when browsing the Internet, composing a drawing, and so forth.


SUMMARY

Inadvertent input control techniques are described. In one or more implementations, techniques are described that leverage detection of applied force to determine a likelihood that a user intended to provide an input, e.g., a selection input (e.g., a “click”), gesture, lift off, and so forth. This is usable to identify taps, hovers (e.g., noncontacts or contacts that are viewed at a level below a threshold), continuation of movement of a drag operation, and so on. Implementations are also discussed that leverage a curve, surface or n-manifold in a product space of contact size and signal strength that is usable to define a likelihood of whether a contact includes an application of force. A variety of other examples are also described, including cursor stability techniques that leverage force in order to control movement of a cursor.


This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.





BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items. Entities represented in the figures may be indicative of one or more entities and thus reference may be made interchangeably to single or plural forms of the entities in the discussion.



FIG. 1 is an illustration of an environment in an example implementation that is operable to employ the inadvertent input control techniques described herein.



FIG. 2 depicts an example of a force sensor that includes a haptic feedback mechanism employing piezos to detect force and provide haptic feedback and a position sensor usable to detect a relative location of an object.



FIG. 3 depicts a system in an example implementation showing inadvertent input control for selection inputs by a force control module.



FIG. 4 depicts an implementation showing first, second, and third examples of force signatures expressed as waveforms.



FIG. 5 depicts an example implementation of control of an inadvertent input involving a hover.



FIG. 6 depicts an example implementation of control of an inadvertent input involving a long-duration hover.



FIG. 7 depicts an example implementation of control of an inadvertent input involving a selection input and movement.



FIG. 8 depicts an example implementation of control of an inadvertent input involving release of a selection input and movement.



FIG. 9 depicts a system in an example implementation showing techniques usable to control a cursor during press down using force by a force control module.



FIG. 10 depicts a system in an example implementation showing techniques usable to control a cursor during lift off using force measurements by a force control module.



FIG. 11 depicts a system in an example implementation showing techniques usable to control a cursor using measured forces by a force control module to control a gain factor that maps the velocity of an object to the velocity of an on-screen cursor.



FIG. 12 depicts a system in an example implementation usable to employ techniques regarding force curves and inadvertent input control.



FIG. 13 depicts an example implementation for a real measured operating characteristic, obtained on a manually operated mechanism over a single touch location.



FIG. 14 is a flow diagram depicting a procedure in an example implementation in which curves are used to classify whether or not reports are likely indicative of advertent or inadvertent inputs.



FIG. 15 illustrates an example system including various components of an example device that can be implemented as any type of computing device as described with reference to FIGS. 1-14 to implement embodiments of the techniques described herein.





DETAILED DESCRIPTION

Overview


Inadvertent inputs captured by touch-enabled devices may interfere with a user's experience when interacting with the devices. This may cause inadvertent selections, unintended movement of a cursor, erroneous gestures, and so forth which may be frustrating to the user.


Inadvertent input control techniques are described. In one or more implementations, force is utilized at least in part to determine a likelihood that a user intended to provide an input. In a first example, a force waveform is used to determine whether a tap is intended by a user. In a second example, a force waveform is used to determine a likelihood of whether an input detected by position sensors (e.g., by capacitive sensors) is intended by a user through verifying whether force is detected by force sensors. In a third example, contacts are ignored that occur after long-duration hovers as the likelihood is greater that a user intended to hover a finger over a trackpad than wanting to initiate the input.


Cursor stability techniques are also described. In one or more examples, force is used to cause a cursor to remain stable, such as for a press-down or lift-off of an object from a trackpad. This may be performed through detection of an amount of force, used to reduce cursor velocity gain, and so on. In this way, the effect of movements of centroids of a contact region caused by a press or release may be minimized.


Techniques are also described in which an amount of force is inferred from a position sensor without use of a dedicated force sensor. Values of a contact size (e.g., area) and signal strength (e.g., amplitude) from position sensors (e.g., capacitive sensors, sensor-in-a-pixel configurations, and so on) are compared to a curve, surface or (in general) n-manifold defined in a product space of contact size and signal strength that is usable to detect a prescribed amount of force applied to the outer surface of the position sensors. A product space is a Cartesian product of a family of topological spaces equipped with a natural topology called a product topology. For example, points above the n-manifold are considered indicative of force and points below the n-manifold are not, resulting in a zero force n-manifold. Thus, the n-manifold is also usable to determine a likelihood that a user intended to initiate an input, maintain an input (e.g., as part of a select-and-drag operation), and so forth. Further discussion of these and other examples is included in the following sections.


In the following discussion, an example environment is first described that may employ the techniques described herein. Example procedures are then described which may be performed in the example environment as well as other environments. Consequently, performance of the example procedures is not limited to the example environment and the example environment is not limited to performance of the example procedures as further described below.


Example Environment



FIG. 1 is an illustration of an environment 100 in an example implementation that is operable to employ the inadvertent input control techniques described herein. The illustrated environment 100 includes an example of a computing device 102 that is physically and communicatively coupled to an input device 104 via a flexible hinge 106. The computing device 102 may be configured in a variety of ways. For example, the computing device 102 may be configured for mobile use, such as a mobile phone, a tablet computer as illustrated, and so on. Thus, the computing device 102 may range from full resource devices with substantial memory and processor resources to a low-resource device with limited memory and/or processing resources. The computing device 102 may include software that causes the computing device 102 to perform one or more operations.


The computing device 102, for instance, is illustrated as including an input/output module 108. The input/output module 108 is representative of functionality relating to processing of inputs and rendering outputs of the computing device 102. A variety of different inputs may be processed by the input/output module 108, such as inputs relating to functions that correspond to keys of the input device 104, keys of a virtual keyboard displayed by the display device 110 to identify gestures and cause operations to be performed that correspond to the gestures that may be recognized through the input device 104 and/or touchscreen functionality of the display device 110. Thus, the input/output module 108 may support a variety of different input techniques by recognizing and leveraging a division between types of inputs including key presses, gestures, and so on.


In the illustrated example, the input device 104 is configured as having an input portion that includes a keyboard 112 having a QWERTY arrangement of keys and a track pad 114, although other arrangements of keys are also contemplated. Further, other non-conventional configurations are also contemplated, such as a game controller, a configuration to mimic a musical instrument, and so forth. Thus, the input device 104 and keys incorporated by the input device 104 may assume a variety of different configurations to support a variety of different functionality.


As previously described, the input device 104 is physically and communicatively coupled to the computing device 102 in this example through use of a flexible hinge 106. The flexible hinge 106 is flexible in that rotational movement supported by the hinge is achieved through flexing (e.g., bending) of the material forming the hinge as opposed to mechanical rotation as supported by a pin (although that embodiment is also contemplated). Further, this flexible rotation may be configured to support movement in one or more directions (e.g., vertically in the figure) yet restrict movement in other directions, such as lateral movement of the input device 104 in relation to the computing device 102. The flexible hinge 106 may be used to support consistent alignment of the input device 104 in relation to the computing device 102, such as to align sensors used to change power states, application states, and so on.


The flexible hinge 106 may be formed using one or more layers of fabric and include conductors formed as flexible traces to communicatively couple the input device 104 to the computing device 102 and vice versa. This communication may be used to communicate a result of a key press to the computing device 102, receive power from the computing device, perform authentication, provide supplemental power to the computing device 102, and so on.


The input device is also illustrated as including a force control module 116 that is representative of using force control techniques to manage inadvertent and advertent inputs. The input device 104, for instance, may include force sensors 118 and position sensors 120. Force sensors 118 are configurable in a variety of ways, such as through use of piezos, force sensitive resistors, strain gauges, and so forth. Force sensors are usable to provide a single indication of force summing of all contact forces or provide a technique to calculate an amount of force on a per sensor force reading. Position sensors 120 are configured to detect a relative location of an object, such as a finger of a user's hand, to control movement of a cursor, input gestures, and so forth. The force sensors 118 and position sensors 120 may be configured in a variety of ways for inclusion in a variety of devices, such as part of the trackpad 114, keys of a keyboard arranged in a sensor array as shown in FIG. 12, as part of touchscreen functionality of the display device 110, and so forth. Accordingly, although trackpad implementations are described in the following discussion, these implementations are equally applicable to other device and usage scenarios.



FIG. 2 depicts an example 200 of a force sensor 118 employing piezos to detect force and provide haptic feedback and a position sensor 120 usable to detect a relative location of an object. This example is illustrated using a first stage 202, a second stage 204, and a third stage 206. The mechanism includes an outer surface 208, such as the surface of a trackpad or the key of a keyboard. The outer surface 208 may be formed from a variety of different materials and combinations thereof, such as glass, plastic, a laminate structure, and a fabric outer layer.


The outer surface 208 includes the position sensors 120 of FIG. 1 that are configured to detect a relative location of an object in relation to the outer surface 208. The position sensors 120 may be formed from a variety of different sensor types, such as capacitive sensors (e.g., a capacitive array), sensor-in-a-pixel, optical sensors, resistive sensors, and acoustic sensors.


The outer surface 208 is coupled mechanically to a spacer 210 that is coupled mechanically to a backer 212. The spacer 210 is configured to channel force applied to the outer surface 210 to a central region of the backer 212 and thus to a piezo 214 connected thereto. In this way, an amount of deflection of the backer 212 and the corresponding piezo 214 is increased in response to the force, even on “off center” presses, thereby supporting a greater sensitivity to detection of an amount of force and haptic response.


The backer 212 is formed from a rigid material (e.g., steel, plastic, and the like) and is physically coupled to the piezo 214. Accordingly, as illustrated in the first stage 202, when a force is not applied to the outer surface 208 (and thus no force is applied to the backer 212), the piezo 214 is not strained and as such does not output a voltage.


At the second stage 204, an object 216 such as a finger of a user's hand (not shown in scale) applies a force as part of pressing down on the outer surface 216) that causes deflection of the backer 212 and thus strain on the piezo 214, resulting in an output voltage that is detectable by the force sensing and haptic feedback module 116. As the voltage output by the piezo 214 changes with an amount of force applied, the piezo 214 is configured to detect not just the presence or absence of force, but also an amount of force, e.g., a respective one of a plurality of levels of force. The piezo 214 is configurable in a variety of ways, such as being formed at least in part from a piezo ceramic material, PZT, an electroactive polymer, or an electromechanical polymer.


The piezo 214 is also usable to provide a haptic feedback, as shown at the third stage 206. Continuing with the previous example in the second stage 204, the piezo 214 detects an amount of force applied to the outer surface 208 by the finger of the user's hand. If the detected force is over a threshold, the force control module 116 energizes the piezo 214. This causes the piezo 214 to pull against the backer 212 and thus deflect outward back toward the object 216 applying the force, thereby providing a haptic response.


In this way, the piezo 214 is leveraged to provide both force sensing and haptic feedback. Other examples are also contemplated. For instance, force may be sensed by a force sensor that is not the piezo and then the piezo may be used to provide haptic feedback. In another instance, a first piezo may be used to detect force and a second piezo may be used to provide haptic feedback. As described above, force sensors 118 are also configurable without piezos while not departing from the spirit and scope of the techniques described herein.


Force Sensing and Inadvertent Input Control



FIG. 3 depicts a system 300 in an example implementation showing inadvertent input control for selection inputs by a force control module 116. A selection input may be thought of as a brief light tap on the outer surface 208 of an input device (e.g., trackpad), which in some instances is not strong enough to trigger a haptic response as described in relation to FIG. 2. Other examples of a selection input are also contemplated in which a “press” is controlled, such as a selection input that has sufficient strength to initiate a click and haptic response, e.g., as a button press of a mouse.


In this example, the force control module 116 is configured to control results of inadvertent inputs through use of a force signature 302 that is expressed as a waveform formed by reports obtained by the force control module 116 from the force sensors 118. The force control module 116 is configured to block further communication of reports from the force sensors 118 and the position sensors 120 that do not meet criteria for an input, e.g., repressing the associated contact such that a touch detection is not reported to the computing device 102, marking the contact as invalid (e.g., by clearing a confidence bit), and so on.


The force control module 116 obtains reports from the force sensors 118 that sample force readings continuously at a sampling rate. In one or more implementations, the reports (e.g., readings) are spaced-out by no more than one or two milliseconds. An exception may be made for simpler parameter extraction, such as to judge simple presence to distinguish from hovering. In those cases it may be permissible to sample at an even slower rate. The reports may be maintained by the force control module 116 in a buffer, such as a circular buffer, to hold approximately fifty milliseconds worth of samples.


A check is first made by the force control module 116 for proper operating conditions, such as to start with zero contacts on the trackpad for cases involving single taps. The force control module 116 waits for an indication of detection of a contact (e.g., a finger of the user's hand in the illustrated example) to arrive. There may be a delay between contact (e.g., a finger touching down) and a controller of the position sensors 120 reporting the contact. The delay may be caused by a limited frame rate of the position sensors 120 (e.g. 8 ms), noise filtering performed by the controller, and so on.


Accordingly, a leading edge of the waveform of the force signature 302 associated with a new contact by the force sensors 118 generally precedes the report from the position sensors 120. This delay is generally variable, typically varying from between five and fifteen milliseconds. When a report arrives from the position sensors 120, force reports are fetched backwards in time (e.g., up to about 15 ms) from the cache by the force control module 116 to ensure that the leading edge of the waveform of the force signature 302 is captured.


Once the force signature 302 is captured, the force control module 116 first locates a leading edge in the waveform. As discussed above, there may be some uncertainty about where this leading edge is found. Parameters from the waveform are then extracted as described below, such as a slope of leading edge and a magnitude (e.g., maximum height).


If the force signature 302 appears to satisfy an intentional selection input (e.g., a “tap”), the force control module 116 is configured to register and permit communication of this information to the input/output module 108 of the computing device 102. Thus, the computing device 102 may also make conclusions about whether the reports reflect an intentional input.


If the force signature 302 does not have a likelihood of being intentional, a variety of different actions may be performed. The force control module 116, for instance, may indicate this lack of confidence to the computing device 102. The input/output module 108 of the computing device 102 is then free to make determinations, e.g., the force signature 302 may still be treated as an intentional selection input. Other examples are also contemplated, such as to block further communication of the reports by the force control module 116 and/or input/output module 108 from proceeding onward, e.g., to the operating system or applications as inputs.


In one or more implementations, the force control module 116 is configured to monitor the contact to decide whether the contact would be interpreted by the computing device 102 as a selection input, e.g., as a tap. For example, if the contact is lifted at no more than 300 milliseconds later, then the force control module 116 is aware that the reports will be interpreted as a tap by the computing device 102. Accordingly, when the object is lifted from the outer surface 208, the confidence bit that asks the computing device 102 to repress the tap is cleared by the force control module 116.


The force control module 116 calculates a force baseline by averaging an initial plurality of the reports of the force signature 302. A rise in force is located in the force signature 302 over the baseline that meets a defined minimum value. As shown in FIG. 3, for instance, TimeMake 304 marks the beginning of the force signature 302.


The force control module 116 then locates and records a first time (e.g., TimeRise0 306) at which the amount of force in the force signature 302 reaches a first threshold value, e.g., BaselineForce plus MinForce0 308. The force control module 116 also locates and records a second time (e.g., TimeRise1 310) at which the amount of force in the force signature 302 reaches a second threshold value, e.g., BaselineForce plus MinForce1 312, which is greater than the first threshold value. A rise time is then calculated based on the recorded first and second times, e.g., TimeRise0 306 and TimeRise1 310, and thus a slope of the leading edge of the force signature 302 is known.


The force control module 116 then reviews the recorded first time to ensure that the value does not exceed a defined maximum value. The force control module 116 also reviews the slope of the attack of the leading edge of the waveform of the force signature 302 to ensure the slope meets a defined minimum threshold. If so, the force control module 116 determines that it is likely that the force signature 302 represents a valid selection input, e.g., a tap, click, and so forth. Likewise, if the slope does not meet the defined minimum threshold, the force control module 116 may determine that it is likely that the force signature 302 does not represent a valid selection input.



FIG. 4 depicts an implementation 400 showing multiple examples of force signatures expressed as waveforms. In the first example 402, the slope 408 is greater than the defined minimum threshold but the magnitude 410 has not reached the first threshold level, and therefore the force control module 116 determines that the detected object is not likely intended as a selection input. In the second example 404, the magnitude 410 has reached the first threshold level but the slope 412 is not greater than the defined minimum threshold, and therefore the force control module 116 determines that the detected object is not likely intended as a selection input. In the third example 406, the slope 414 is greater than the defined minimum threshold and the magnitude 410 has reached the first threshold level so the force control module 116 determines that the detected object likely involves an intended input.


In one or more implementations, the force control module 116 employs different modes to control determination of inadvertent inputs. The modes in the following refer to the system's inference of how a user is interacting with the input device 104 and/or the computing device 102 as a whole and define sets of parameters for the force control module 116 to determine the likelihood of an intentional input, e.g., the time and force parameters noted above. These parameters may be dynamic, providing greater or lesser defenses against taps, to provide the greatest defenses without imposing undo reductions in tap responsiveness.


In one example, the force control module 116 reverts to a “hard mode” when key presses are not detected or when the force control module 116 detects a prolonged period of input device disuse. In this way, difficulty in registering selection inputs is increased for situations in which it is suspected that the user is not using the trackpad. In the hard mode, the slope and force requirements are more stringent and thereby involve more clearly deliberate taps than when in an “easy mode.” Following this example, the force control module 116 may switch to the easy mode when a hard tap occurs in the hard mode, when the user moves a cursor a minimum distance, and so on. When the cursor is moved, for instance, the force control module 116 may be fairly certain that the user intends to interact with the trackpad and thus the defenses against inadvertent inputs (e.g., slope and magnitude) are lowered in the easy mode.



FIG. 5 depicts an example implementation 500 of control of an inadvertent input involving a hover. A hover inadvertent input typically occurs when a nearby object, such as a finger, thumb, or palm, is interpreted as intentional interaction by the input device 104. Accordingly, following the example above, the force control module 116 is configured to ignore contacts having force signatures 302 (e.g., waveforms) that do not meet prescribed criteria (e.g., force signatures 302 indicating hover inadvertent inputs).


The illustration includes a first example 502 and a second example 504. At the first example 502, reports from force sensors 118 form a waveform 506 and reports from position sensors 120 form a waveform 508. The waveform 508 from the position sensors 120 indicates that proximity of an object (e.g., a finger 510 from a user's hand) is detected. This proximity is detected without involving contact of the object with the outer surface 208, e.g., due to enhanced sensing range of capacitive sensors, infrared sensors, and so on.


However, the waveform 506 from the force sensors 118 indicates that minimal to no force is sensed by the force sensors 118, e.g., the magnitude of the waveform 506 is below a defined minimum force threshold 512. Therefore, in the first example 502 the force control module 116 readily determines that there is little to no likelihood of a user intending to initiate an input and responds accordingly, e.g., blocks communication of the reports from the position sensors 120 to the computing device 102, through use of a confidence bit.


In the second example 504, reports received by the force control module 116 from the position sensors 120 indicate proximity of the object (e.g., the finger 510 of the user's hand) through waveform 508. The waveform 508 formed from the reports received from the force sensors 118 also indicates that a force has been received that is above the minimum force threshold 512, and thus the object has contacted and applied the force to the outer surface 208. In response, the force control module 116 determines that it is likely that an input is intended, and responds accordingly as described above, e.g., communicates the reports to the input/output module 108 of the computing device 102 of FIG. 1. Thus, in this example the force control module 116 leverages force to distinguish between a deliberate contact and a hovering force.



FIG. 6 depicts an example implementation 600 of control of an inadvertent input involving a long-duration hover. One type of inadvertent input involves unwanted contact (e.g., causing a tap, cursor movement, scrolling, zooming) caused by a user's hand 602 that was hovering over a trackpad. The user may have been typing and had a thumb or palm disposed proximal to the position sensors 120 that is consequently detected by the position sensors 120, but is not in contact with the outer surface 208.


In this example, reports of detected amounts of force from the force sensors 118 are used by the force control module 116 to determine that a significant force above a threshold 614 has not been applied (as shown at example 604), and thus contact was not likely made with the outer surface 208. If a contact is subsequently detected (as shown at example 606), the force control module 116 determines the likelihood of intent to initiate an input based on an amount of time the object spent hovering above the outer surface. In this way, the force control module 116 may leverage a realization that deliberate interactions with the trackpad usually do not start out with the user hovering for an extended period of time, but rather a user typically just moves in and interacts with the trackpad, e.g., to perform clicks, drags, gestures, and so on.


This is also illustrated graphically 608 in the figure in which a waveform 610 formed from reports from the force sensors 118 and a waveform 612 formed from reports from the position sensors 120 is shown. As illustrated by the first example 604 of a hover, the waveform 612 from the position sensors 120 does detect proximity but the waveform 610 from the force sensors 118 does not and thus the reports are ignored, e.g., blocked from further processing by the force control module 116.


A period of time progresses in this state, until an application of force to the outer surface 208 is detected by the force sensors 118 (as indicated at example 606) for the waveform 612 and proximity is also detected by the position sensors 120 (as also indicated at example 606) for the waveform 610. If this application of force occurs after a threshold amount of time, the force control module 116 may act to block further processing of the reports and indicate this condition through use of a confidence bit since it is determined that it is not likely that the user intended to initiate an input. Thus, in this example, the position sensors 120 “see” proximity of the object before contact with the outer surface 208 occurs and track this pre-contact proximity. If contact with the outer surface 208 is made after a predefined period of time has passed, the force control module 116 determines that this contact has a low likelihood of being an intentional input.


In one or more implementations, detection of proximity and the amount of force by reports from the force sensors 118 and the position sensors 120 are correlated to distinguish which objects have applied force, an amount of time each object hovers, and so on. For example, the position sensors 120 may sense location as well as a relative strength when sensing the object. If that sensing strength exhibits an increase that coincides with an increase in force, the force control module 116 may assign that detection of force to that object location. Addition or removal of subsequent objects may also be assigned corresponding forces and in this way the force control module 116 may track forces and locations of multiple objects simultaneously to support multiple simultaneous inputs, differentiate amounts of force between objects and corresponding inputs, and so forth.


Additionally, techniques are contemplated in which force is recognized even on a hovering contact, e.g., a level where the force is large enough to be intentional and override and inadvertent lockout. This is performable in a variety of ways, such as through use of a threshold corresponding to a desired amount of force usable to override the lockout.



FIG. 7 depicts an example implementation 700 of control of an inadvertent input involving a selection input and subsequent movement as part of a drag operation. This implementation 700 is illustrated using a first example 702 and a second example 704. In conventional mechanical click pads a dome switch is used that mechanically activates whenever an applied force exceeds a fixed threshold. Thus, a moving finger (i.e., a finger performing a drag operation) with sufficient force may still cause an inadvertent button press.


The force control module 116, however, employs force sensing that is usable to control haptic feedback. The force sensing is also usable to determine a likelihood that a user wishes to perform an action, e.g., to initiate a click, to continue or release a drag operation as described in further detail in relation to FIG. 8 below, and so on.


At the first example 702, movement of a finger of a user's hand 706 is illustrated through use of an arrow. The force control module 116 detects movement of the object through the position sensors 120 and utilizes a corresponding threshold 708 to define an amount of force used to initiate the haptic response. Thus, if the force signature 710 remains below this threshold 708 during the movement, the selection input is not initiated, as the force control module 116 has determined that it is unlikely that the user intended to initiate the input.


At the second example 704, however, the force control module 116, through analysis of reports received from the position sensors 120, determines that the object exhibits less than a threshold 708 amount of movement from the first example 702. In response, the force control module 116 uses another threshold 714 to determine likelihood of a user desiring to initiate an input that is lower than the threshold 708 used for movement. Accordingly, if reports of a waveform 712 from a force signature of the force sensors 118 are greater than this threshold 714 (as illustrated), a selection input is initiated, which may include a haptic response (such as a “click” described in relation to FIG. 2). Thus, an inadvertent selection is made less likely yet sensitivity is still preserved through use of an additional threshold 714.



FIG. 8 depicts an example implementation 800 of control of an inadvertent input involving release of a selection input and movement. As described above, in conventional mechanical click pads a dome switch is used that mechanically activates whenever an applied force exceeds a fixed threshold. The conventional click pad is also configured to release whenever an applied force is reduced below a threshold amount, e.g., a return force of the dome switch. Thus, if a user does not maintain enough force during a drag operation of conventional devices, the operation may end before the user intended.


In this example, the force control module 116 is configured to release a haptic response (e.g., a click) for a drag operation if the object applies an amount of force below a threshold 808 and is not moving, i.e., generally stationary. Similarly, the threshold 808 used to define a release may be decreased to threshold 810 during movement in the drag operation to make inadvertent release less likely.


In the illustration of FIG. 8, a finger of a user's hand 802 is illustrated as performing a select and drag operation, movement involved in which is illustrated using arrows along with a graph 804 having a force signature 806 formed as a waveform from reports obtained from the force sensors 118 by the force control module 116. A first threshold 808 is used to determine whether the reports qualify as a selection input as described above, e.g., the “click down.”


A drag operation is then performed which involves movement along the outer surface 208 as illustrated by the arrow. During this movement, a second threshold 810 that is lower than the first threshold 808 is used to determine whether the drag operation is to be released or is considered as continuing on. A third threshold 814 is also used as a release threshold, but is used for zero movement and is thus higher than the second threshold 810. Therefore, even though a point 812 may be encountered in which the amount of force drops below the third threshold 814, as long as the force remains above the second threshold 810 and the movement continues, the drag operation also continues. Once the detected force moves below the second threshold 810, termination of the drag operation is indicated, which may be used by the force control module 116 to provide haptic feedback as described in relation to FIG. 2. In this way, an inadvertent click release is made less likely. A variety of other examples are also contemplated without departing from the spirit and scope of the techniques described herein.


For example, techniques may be employed in which a plurality of levels of rejection are used, i.e., different thresholds. Use of the different thresholds may be based on recent detected interaction with the computing device 102, e.g., whether cursor interaction, gestures, or typing has been detected within a threshold amount of time. Examples of these are referred to as “hard” or “soft” modes in the following discussion.


Force Inputs and Cursor Control



FIG. 9 depicts a system 900 in an example implementation showing techniques usable to control a cursor during push down using force by a force control module 116. When a user pushes down on a trackpad or touchscreen to select an icon, check a box, or so on a cursor may move in conventional scenarios. This effect may be caused by rolling of a fingertip on an outer surface, deformation of the pulp of a fingertip caused by the force (resulting in a shift in a calculated centroid of the contact), and so forth. To address this, techniques may be utilized to hold what is reported as a relative location of an object (e.g., a finger of a user's hand 902) steady when first contacting the outer surface 208 and report movement when a threshold amount of movement is detected, e.g., as defined by a bounding box 904. These techniques may result in decreased responsiveness.


In this implementation, the force control module 116 employs force to control a cursor in place of or in addition to using the bounding box 904 (e.g., to reduce a size of the bounding box 904 and thus decrease the threshold amount of movement detected before movement is reported). The system 900 includes first example 906 and a second example 908.


At the first example 906, a waveform 910 of a force signature is illustrated from reports of the force sensors 118. The waveform 910 in this example includes sufficient slope (as described in relation to FIG. 3) such that the reports are considered indicative of an input, e.g., a selection input as described above. In response to the force illustrated in the waveform 910, the force control module 116 is configured to override small movement reports communicated by the position sensors 120 that may be caused by deformation, rocking, and so on. As such, a cursor remains stationary while an intentional input is detected in the first example 906.


At the second example 908, a finger of a user's hand 902 is moved across the outer surface 208 as illustrated by an arrow. A corresponding waveform 912 formed by reports obtained from the force sensors 118 illustrates an amount of force at various points in time during this movement. A threshold 914 is used in this example such that if the amount of force remains below the threshold 914, movement of the cursor is permitted. Thus, if the force stays light, then a cursor is allowed to move without delay in the second example 908. However, if the force ramps-up rapidly (as illustrated by the slope of the waveform 910 of the first example 906), the force control module 116 determines that the user likely wishes to initiate an input. In this way, the force control module 116 supports increased responsiveness along with protection against inadvertent inputs. Similar techniques are also usable in regard to removal of contact (e.g., lift off), further discussion of which is included in the following and shown in a corresponding figure.



FIG. 10 depicts a system 1000 in an example implementation showing techniques usable to control a cursor during lift off using force measurements by a force control module 116. In the above example of FIG. 9, movement of a cursor that could occur in conventional instances in a press down due to rolling of a fingertip on an outer surface, deformation of pulp of a fingertip caused by the force and thus resulting in a shift in a calculated centroid of the contact, and so forth is described. A similar effect may also be observed on lift off when a finger of a user's hand 1002 is removed from contacting the outer surface 208 and thus in conventional devices could also cause inadvertent movement of a cursor.


Thus, in this example the force control module 116 is also configured to control cursor movement based on force measurements, but in this instance to use reducing force to halt contact movement on lifts. In the illustrated example, a finger of a user's hand 1002 is illustrated as performing a drag operation, which is then terminated by lifting 1004 the finger of the user's hand 1002 away from the outer surface 208 as illustrated using arrows. A waveform 1006 formed by reports obtained from the force sensors 118 indicating an amount of force over time is shown graphically.


When the finger of the user's hand 1002 is lifted 1004 from the outer surface 208, the force control module 116 detects a rapid decrease 1008 in force in the waveform 1006, e.g., a slope over a defined amount. In response, the force control module 116 determines that a user is likely terminating the drag operation and overrides any movement associated with this rapid decrease 1008 that is detected by the position sensors 120. In this way, the cursor is controlled to be relatively stationary upon lift off by using reducing force identified through slope as described above through time and corresponding intensity thresholds to halt recognized contact movement.



FIG. 11 depicts a system 1100 in an example implementation showing techniques usable to control a cursor using measured forces by a force control module 116 to control a gain factor that maps the velocity of an object to the velocity of an on-screen cursor. Like above, a centroid detected for a location of an object by the position sensors 120 shifts both when a finger is pressed and released. In typical cursor control scenarios, press and release events are performed with a stationary finger of a user's hand.


In this example, a gain factor 1002 maps the physical velocity of movement of an object that is detected by the position sensors 120 to onscreen velocity of a cursor. For example, a finger of the user's hand 1104 may move a half an inch per second and a gain factor 1002 may be used to multiply that movement velocity by a specified amount, which may be dynamically defined, to obtain the onscreen velocity of a cursor.


In the illustrated example, the gain factor 1102 is based at least in part on a rate of variation in an amount of force as detected by the force sensors 118, which is exhibited graphically by a waveform 1106. The gain factor 1102 is attenuated in proportion (e.g., directly, indirectly, dynamically) to an absolute rate of force variation as detected by the force sensors 118. Thus, the gain factor 1102 dips to low values when the waveform 1106 increases or decreases quickly, and remains stable at a nominal level when the waveform 1106 oscillates slowly. The effect is that movement of a cursor is significantly reduced and even eliminated if force applied by an object changes more than a threshold amount. In this way, increased cursor stability is achieved by the force control module 116 while still preserving responsiveness of cursor movement.


Force Curves and Inadvertent Input Control



FIG. 12 depicts a system 1200 in an example implementation usable to employ techniques regarding force curves and inadvertent input control. Conventional multi touch sensors may exhibit a variety of nonlinear behaviors that are compensated for to provide a good user experience. For example, mutual capacitance sensors work because grounded fingers disrupt fringing electrical fields. The intensity of these fields, known as electric flux density, rolls off non-linearly with distance and is dependent on electrode geometry. Additionally, sensors may have edges where uniformity assumptions break down. For example, a finger touching the middle of the touch pad is generally detected by multiple nodes, while a finger located over an edge or corner is often detected by a single node. This again produces errors and introduces biases for all measured quantities.


In the following a device model is described that is usable to infer an amount of force sensed that may be used to perform the previously described techniques without use of a dedicated force sensor 118. Rather, functionality of the force sensor 118 may be realized by the position sensor 120. The force control module 116, for instance, may convert raw sensor values into absolute force units such as grams-force (gf); produce force estimates that are independent of contact size (e.g., finger area); use automatic gain control to adapt to a wide variety of environmental and electrical changes; and correct the effects of spatial aliasing and edge effects.


Accordingly, the force control module 116 incorporates techniques to estimate a size (e.g., area, width and height, major and minor axes) and signal strength (e.g., amplitude, average value, root-mean-square value) for each contact that is used to infer an amount of force applied to the outer surface 208. Signal strength, and thus amplitude, is a quantity that changes with an amount of force, even if in a non-linear manner, and multiple contacts produce independent estimates of size and amplitude.


An example of an input device 104 that incorporates these techniques is illustrated in FIG. 12. The input device 104 is implemented as a multi-touch resistive design with a rectangular grid 1202 of force-sensitive resistive (FSR) nodes illustrated as squares in the figure (arrayed with, for example, a 5 mm pitch). Combinations of the nodes are usable to define keys, trackpad functionality, and so on, an example of which is shown for the letter “A” 1204 that includes four nodes 1206, 1208, 1210, 1212. As an example, gestures may be supported across keys of the keyboard through combinations of nodes. The amplitude reported by each node is proportional to its conductance.


Other examples include a mutual capacitance sensor, with a layer of open-cell foam laminated over the capacitive electrodes. Under a zero-force contact, the foam is relaxed and acts as a spacer with known thickness and dielectric constant. Under force, the foam is compressed, such that the gap between the finger and the sensor electrodes reduces and the foam dielectric constant increases. This produces a measurable and repeatable change in capacitance, which can be used to estimate force. For this sensor, the amplitude reported by each node is proportional to the change in mutual capacitance with respect to its baseline value.


The force control module 116 is used to estimate a centroid, amplitude and area of contact, e.g., through use of a touch controller. These values are generally computed from a matrix of resistance or capacitance deltas, where each element of the matrix corresponds to a sensor node. Amplitude is proportional to peak deltas for a region receiving the application of force. In the illustrated example of FIG. 12, area is proportional to the number of nodes under a contact made by an object.


In the following, a model is first extracted using data obtained from a set of standardized test fingers with diameters covering a range of human finger sizes. For example, if 5.0-15.0 millimeter contact sizes are of interest, a set of fingers with 2.5, 5.0, 7.5, 10.0, 15.0 and 20.0 millimeter diameters can provide sufficient granularity and some margin. Depending on the application, rigid fingers with flat bottoms or flexible fingers may be used. For capacitive systems, the finger is grounded and either made of conductive material or wrapped in a conductive fabric. A robot is used in this example with an attachment mechanically compatible with the set of fingers, capable of applying arbitrary forces over the measurement range and equipped with a two-dimensional stage capable of moving a device under test.


A set of locations receive the robot stimuli, e.g., five locations sufficiently away from the edges. The amount or force (i.e., force values) which are applied to the device under test is varied to span the sensor measurement range. A measurement routine involves moving the robot to the first test location, attaching a first test finger to the robot, and having the robot step through the force values defined above and record centroid, amplitude and area produced by the sensor. This continues for a variety of locations and uses a variety of different finger samples at each location. FIG. 13 depicts an example implementation 1300 for a real, measured operating characteristic, obtained on a manually operated mechanism over a single touch location. Sensor responses are measured at 20, 40, 60, 80, 100, 140, 180, 220, 260 and 300 gf, respectively.


To perform model fitting, for any arbitrary force value v (in grams-force), the sensor's amplitude response is modeled as “fv(Area),” which is a scalar function of its area response. One way of obtaining such a function is by fitting a least-squares polynomial to the measured data, assuming “v” grams-force is part of the force values defined above. It will be recognized that while this example uses contact area to represent contact size, a multi-dimensional quantity may be used instead. For example, contact size may be defined as contact width and height. Alternatively, contact size may be defined as the major and minor axes of the ellipse produced by a least-squares fit. In general, “fv(Size)” is not a curve but an n-manifold that partitions the product space of contact size and signal strength. Curves are used for purposes of illustration and are not intended to be limiting.


The first, second, and third curves 1302, 1304, 1306 of FIG. 13 are un-weighted least-squares second degree polynomials, fit to the responses at 20 gf, 300 gf and 100 gf, respectively. This result leads to the following observations. First, amplitude depends on finger size and may be a non-monotonic function of it. In particular, a naïve algorithm that simply sums the amplitude of all cells produces significant errors. For the force scale of interest and test conditions, the sensor response is located within the first and second curves 1302, 1304. In particular, responses significantly under the first curve 1302 are physically impossible under standard operating conditions. Responses significantly above the second curve 1304 are also impossible due to sensor saturation.


Since this sensor has two output values (i.e., amplitude and area) that are jointly correlated to force, a force threshold corresponds to a curve in the plane defined by the Cartesian product of area and amplitude. For example, the third curve 1306 serves as a threshold for 100 gf with points above the curve exceeding 100 gf, and points below under 100 gf.


Thus, the curves (or in general, n-manifolds) may be used to support a variety of functionality. As a threshold detector, for instance, the curves (or n-manifolds) may be used by the force control module 116 as a basis to determine a likelihood of whether a selection input is initiated or released as described above. In order to do so, a threshold curve (or n-manifold) is created by fitting the dataset to define a desired amount of force. For example, the third curve 1306 is an example threshold function for 100 gf.


Additionally, the first curve 1302 defines a threshold, beneath which responses are physically impossible under standard operating conditions. Accordingly, the first curve 1302 may act as a “zero force” curve in which combinations of signal strength (e.g. amplitude) and contact size (e.g., area) above the first curve 1302 likely involve an application of force and are thus “not hovering.” On the other hand, combinations of signal strength (e.g. amplitude) and contact size (e.g., area) below the first curve 1302 are likely hovering.


Thus, on position sensors 120 such as capacitive sensors described earlier, this n-manifold lies in the product space of contact size and signal strength, defined as area and amplitude in the example above. Points formed by combinations above the first curve 1302 are considered to be exerting greater than zero force, and points under this curve are considered to be hovering (not in contact with nor exerting force on the outer surface 208).


The use of a zero-force n-manifold provides better accuracy than simply using separate amplitude or area thresholds, which are the conventional techniques used to determine whether a capacitive contact is valid. Specifically, by ignoring contacts that are under the zero force n-manifold in combination with the techniques described above, the force control module 116 may accurately discriminate and ignore hovering contacts.


The use of n-manifolds in the product space of contact size and signal strength are also usable as part of control of drag operations as described above. For example, users can sometimes inadvertently release a contact during a long drag motion if the characteristics of a contact change during the drag operation, causing the contact down criteria not to be met as described in relation to FIG. 8. This can result in drag operations being interrupted or new tap and drags improperly occurring. Through use of the n-manifolds described herein, however, once a qualified contact is reported and a drag operation commences, communication of reports of contact may be maintained, thereby allowing a reduced criteria n-manifold to apply for termination of contact reporting, i.e., the end of the drag operation. For example, another n-manifold may be employed during movement that defines an amount of force to be detected that is sufficient to maintain the drag operation. The result being that a drag continues uninterrupted until a deliberate lift is encountered as defined by the reduced criteria n-manifold. As described above, force depends on contact size and amplitude. As such, the force control module 116 may be used to fit a parametric surface to a measured dataset and obtain a function mapping an area and amplitude pair into absolute force.


Example Procedures


The following discussion describes inadvertent input force control techniques that may be implemented utilizing the previously described systems and devices. Aspects of each of the procedures may be implemented in hardware, firmware, or software, or a combination thereof. The procedures are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the figures described above.


Functionality, features, and concepts described in relation to the examples of FIGS. 1-13 may be employed in the context of the procedures described herein. Further, functionality, features, and concepts described in relation to different procedures below may be interchanged among the different procedures and are not limited to implementation in the context of an individual procedure. Moreover, blocks associated with different representative procedures and corresponding figures herein may be applied together and/or combined in different ways. Thus, individual functionality, features, and concepts described in relation to different example environments, devices, components, and procedures herein may be used in any suitable combinations and are not limited to the particular combinations represented by the enumerated examples.



FIG. 14 depicts a procedure 1400 in an example implementation in which n-manifolds are used to classify whether or not reports are likely indicative of advertent or inadvertent inputs. Reports are received by a force control module implemented at least partially in hardware from one or more position sensors configured to detect proximity of an object with respect to an outer surface, the reports indicating a contact size and signal strength of the detected proximity of the object (block 1402). The reports, for instance, may be received by the force control module 116 from position sensors that are configured as capacitive sensors, arrays of nodes as shown in FIG. 12, and so on.


The reports are classified as indicative of contact of the object with the outer surface or as lack of contact of the object with the outer surface through comparison of the reports with an n-manifold that partitions the product space of contact size and signal strength and is indicative of a prescribed force applied to the outer surface (block 1404). The first curve 1302 of FIG. 13, for instance, may define a zero force 1-manifold such that reports having combinations of contact size and signal strength above the curve are considered advertent, and below inadvertent. The force control module controls whether the reports are considered inadvertent based on the classifying (block 1506), such as to block or permit further communication as described above. N-manifolds may be used for a variety of other functionality, such as to define movement in a drag operation, initiation of a selection input, and so on as described in relation to FIGS. 1-13.


Example System and Device



FIG. 15 illustrates an example system generally at 1500 that includes an example computing device 1602 that is representative of one or more computing systems and/or devices that may implement the various techniques described herein. This is illustrated through inclusion of the force control module 116. The computing device 1602 may be, for example, a server of a service provider, a device associated with a client (e.g., a client device), an on-chip system, and/or any other suitable computing device or computing system.


The example computing device 1502 as illustrated includes a processing system 1504, one or more computer-readable media 1506, and one or more I/O interface 1508 that are communicatively coupled, one to another. Although not shown, the computing device 1502 may further include a system bus or other data and command transfer system that couples the various components, one to another. A system bus can include any one or combination of different bus structures, such as a memory bus or memory controller, a peripheral bus, a universal serial bus, and/or a processor or local bus that utilizes any of a variety of bus architectures. A variety of other examples are also contemplated, such as control and data lines.


The processing system 1504 is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system 1504 is illustrated as including hardware element 1510 that may be configured as processors, functional blocks, and so forth. This may include implementation in hardware as an application specific integrated circuit or other logic device formed using one or more semiconductors. The hardware elements 1510 are not limited by the materials from which they are formed or the processing mechanisms employed therein. For example, processors may be comprised of semiconductor(s) and/or transistors (e.g., electronic integrated circuits (ICs)). In such a context, processor-executable instructions may be electronically-executable instructions.


The computer-readable storage media 1506 is illustrated as including memory/storage 1512. The memory/storage 1512 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage component 1512 may include volatile media (such as random access memory (RAM)) and/or nonvolatile media (such as read only memory (ROM), Flash memory, optical disks, magnetic disks, and so forth). The memory/storage component 1512 may include fixed media (e.g., RAM, ROM, a fixed hard drive, and so on) as well as removable media (e.g., Flash memory, a removable hard drive, an optical disc, and so forth). The computer-readable media 1506 may be configured in a variety of other ways as further described below.


Input/output interface(s) 1508 are representative of functionality to allow a user to enter commands and information to computing device 1502, and also allow information to be presented to the user and/or other components or devices using various input/output devices. Examples of input devices include a keyboard, a cursor control device (e.g., a trackpad), a microphone, a scanner, touch functionality (e.g., capacitive or other sensors that are configured to detect physical touch), a camera (e.g., which may employ visible or non-visible wavelengths such as infrared frequencies to recognize movement as gestures that do not involve touch), and so forth. Examples of output devices include a display device (e.g., a monitor or projector), speakers, a printer, a network card, tactile-response device, and so forth. Thus, the computing device 1502 may be configured in a variety of ways as further described below to support user interaction.


Various techniques may be described herein in the general context of software, hardware elements, or program modules. Generally, such modules include routines, programs, objects, elements, components, data structures, and so forth that perform particular tasks or implement particular abstract data types. The terms “module,” “functionality,” and “component” as used herein generally represent software, firmware, hardware, or a combination thereof. The features of the techniques described herein are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.


An implementation of the described modules and techniques may be stored on or transmitted across some form of computer-readable media. The computer-readable media may include a variety of media that may be accessed by the computing device 1502. By way of example, and not limitation, computer-readable media may include “computer-readable storage media” and “computer-readable signal media.”


“Computer-readable storage media” may refer to media and/or devices that enable persistent and/or non-transitory storage of information in contrast to mere signal transmission, carrier waves, or signals per se. Thus, computer-readable storage media refers to non-signal bearing media. The computer-readable storage media includes hardware such as volatile and non-volatile, removable and non-removable media and/or storage devices implemented in a method or technology suitable for storage of information such as computer readable instructions, data structures, program modules, logic elements/circuits, or other data. Examples of computer-readable storage media may include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, hard disks, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or other storage device, tangible media, or article of manufacture suitable to store the desired information and which may be accessed by a computer.


“Computer-readable signal media” may refer to a signal-bearing medium that is configured to transmit instructions to the hardware of the computing device 1502, such as via a network. Signal media typically may embody computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as carrier waves, data signals, or other transport mechanism. Signal media also include any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared, and other wireless media.


As previously described, hardware elements 1510 and computer-readable media 1506 are representative of modules, programmable device logic and/or fixed device logic implemented in a hardware form that may be employed in some embodiments to implement at least some aspects of the techniques described herein, such as to perform one or more instructions. Hardware may include components of an integrated circuit or on-chip system, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), a complex programmable logic device (CPLD), and other implementations in silicon or other hardware. In this context, hardware may operate as a processing device that performs program tasks defined by instructions and/or logic embodied by the hardware as well as a hardware utilized to store instructions for execution, e.g., the computer-readable storage media described previously.


Combinations of the foregoing may also be employed to implement various techniques described herein. Accordingly, software, hardware, or executable modules may be implemented as one or more instructions and/or logic embodied on some form of computer-readable storage media and/or by one or more hardware elements 1510. The computing device 1502 may be configured to implement particular instructions and/or functions corresponding to the software and/or hardware modules. Accordingly, implementation of a module that is executable by the computing device 1502 as software may be achieved at least partially in hardware, e.g., through use of computer-readable storage media and/or hardware elements 1510 of the processing system 1504. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices 1502 and/or processing systems 1504) to implement techniques, modules, and examples described herein.


As further illustrated in FIG. 15, the example system 1500 enables ubiquitous environments for a seamless user experience when running applications on a personal computer (PC), a television device, and/or a mobile device. Services and applications run substantially similar in all three environments for a common user experience when transitioning from one device to the next while utilizing an application, playing a video game, watching a video, and so on.


In the example system 1500, multiple devices are interconnected through a central computing device. The central computing device may be local to the multiple devices or may be located remotely from the multiple devices. In one embodiment, the central computing device may be a cloud of one or more server computers that are connected to the multiple devices through a network, the Internet, or other data communication link.


In one embodiment, this interconnection architecture enables functionality to be delivered across multiple devices to provide a common and seamless experience to a user of the multiple devices. Each of the multiple devices may have different physical requirements and capabilities, and the central computing device uses a platform to enable the delivery of an experience to the device that is both tailored to the device and yet common to all devices. In one embodiment, a class of target devices is created and experiences are tailored to the generic class of devices. A class of devices may be defined by physical features, types of usage, or other common characteristics of the devices.


In various implementations, the computing device 1502 may assume a variety of different configurations, such as for computer 1514, mobile 1515, and television 1518 uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device 1502 may be configured according to one or more of the different device classes. For instance, the computing device 1502 may be implemented as the computer 1514 class of a device that includes a personal computer, desktop computer, a multi-screen computer, laptop computer, netbook, and so on.


The computing device 1502 may also be implemented as the mobile 1515 class of device that includes mobile devices, such as a mobile phone, wearables (e.g., wrist bands, pendants, rings) portable music player, portable gaming device, a tablet computer, a multi-screen computer, and so on. The computing device 1502 may also be implemented as the television 1518 class of device that includes devices having or connected to generally larger screens in casual viewing environments. These devices include televisions, set-top boxes, gaming consoles, and so on. Other devices are also contemplated, such as appliances, thermostats and so on as part of the “Internet of Things.”


The techniques described herein may be supported by these various configurations of the computing device 1502 and are not limited to the specific examples of the techniques described herein. This functionality may also be implemented all or in part through use of a distributed system, such as over a “cloud” 1520 via a platform 1522 as described below.


The cloud 1520 includes and/or is representative of a platform 1522 for resources 1524. The platform 1522 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 1520. The resources 1524 may include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the computing device 1502. Resources 1524 can also include services provided over the Internet and/or through a subscriber network, such as a cellular or Wi-Fi network.


The platform 1522 may abstract resources and functions to connect the computing device 1502 with other computing devices. The platform 1522 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the resources 1524 that are implemented via the platform 1522. Accordingly, in an interconnected device embodiment, implementation of functionality described herein may be distributed throughout the system 1500. For example, the functionality may be implemented in part on the computing device 1502 as well as via the platform 1522 that abstracts the functionality of the cloud 1520.


CONCLUSION AND EXAMPLE IMPLEMENTATIONS

Example implementations described herein include, but are not limited to, one or any combinations of one or more of the following examples:


In one or more examples, a system includes at least one force sensor configured to detect amounts of force applied by an object to an outer surface; one or more position sensors configured to detect proximity of the object to respective locations of the outer surface; and a force control module implemented at least partially in hardware, the force control module configured to determine a likelihood that the object is intended to initiate an input based on time-domain or frequency-domain features of a force signature expressed as a waveform formed by reports from the at least one force sensor of the detected amounts of force over a period of time.


An example as described alone or in combination with any of the other examples described above or below, wherein the reports from the at least one force sensor are captured backward in time from a buffer responsive to detection of the proximity of the object by the one or more position sensors.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to block processing of the reports by a computing device responsive to a determination that it is unlikely that the object is intended to initiate the input.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to indicate to a computing device that it is unlikely that the object is intended to initiate the input responsive to a determination that it is unlikely that the object is intended to initiate the input.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to employ a plurality of threshold usable to detect the likelihood, use of the different thresholds dependent on whether user interaction has been detected within a predefined amount of time.


An example as described alone or in combination with any of the other examples described above or below, further comprising a haptic feedback mechanism and wherein the force control module is configured to initiate haptic feedback of the haptic feedback mechanism responsive to a determination that it is likely that the object is intended to initiate the input to support inadvertent input mitigation to reduce inadvertent switch occurrences or selections.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to calculate the rise time by: recording a first time at which the amount of force in the force signature reaches a first threshold value; recording a second time at which the amount of force in the force signature reaches a second threshold value that is higher than the first threshold value; and calculating the slope based on the recorded first and second times.


In one or more examples, an apparatus includes at least one force sensor configured to detect an amount of force applied by an object to an outer surface; one or more position sensors configured to detect proximity of the object to respective locations of the outer surface; and a force control module implemented at least partially in hardware, the force control module configured to determine a likelihood that the object is intended to initiate an input based on an amount of time the object is detected as proximal to the outer surface by the one or more position sensors and the force detected by the at least one force sensor is less than a force threshold.


An apparatus as described in claim 8, wherein the force control module is configured to distinguish the object from a second object and corresponding detection of proximity and the amount of force


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to distinguish the object from the second object by correlating the detection of the proximity of the object and subsequent contact by the one or more position sensors with the amount of force applied by the object to the outer surface detected by the at least at least one force sensor.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to block processing of the input by a computing device responsive to a determination that it is unlikely that the object is intended to initiate the input.


An example as described alone or in combination with any of the other examples described above or below, further comprising a haptic feedback mechanism and wherein the force control module is configured to initiate haptic feedback of the haptic feedback mechanism responsive to a determination that it is likely that the object is intended to initiate the input.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to permit processing of the input by a computing device responsive to a determination that it is likely that the object is intended to initiate the input.


In one or more examples, a system includes at least one force sensor configured to detect an amount of force applied by an object to an outer surface; one or more position sensors configured to detect a location and movement of the object with respect to the outer surface; and a force control module implemented at least partially in hardware, the force control module configured to determine a likelihood that the object is intended to initiate an input based on the amount of force applied by the object to the outer surface in relation to a predefined threshold and whether the object is moving.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module determines that it is likely that the object is intended to initiate the input when the object is not moving and the amount of force is above the predefined threshold.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module determines that it is likely that the object is intended to continue a drag operation of the input when the object is moving and the amount of force is below the predefined threshold.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module determines that it is likely that the object is intended to release a drag operation of the input when the object is not moving and the amount of force is below the predefined threshold.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to block processing of the input by a computing device responsive to a determination that it is unlikely that the object is intended to initiate the input.


An example as described alone or in combination with any of the other examples described above or below, further comprising a haptic feedback mechanism and wherein the force control module is configured to initiate haptic feedback of the haptic feedback mechanism responsive to a determination that it is likely that the object is intended to initiate the input.


An example as described alone or in combination with any of the other examples described above or below, wherein the force control module is configured to permit processing of the input by a computing device responsive to a determination that it is likely that the object is intended to initiate the input.


Although the example implementations have been described in language specific to structural features and/or methodological acts, it is to be understood that the implementations defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed features.

Claims
  • 1. A system comprising: at least one force sensor configured to detect amounts of force applied by an object to an outer surface;one or more position sensors configured to detect proximity of the object to respective locations of the outer surface; anda force control module implemented at least partially in hardware, the force control module configured to: determine a likelihood that a contact made by the object was unintentional based on an amount of time that passes after proximity is detected by the one or more position sensors before an amount of force exceeding a threshold is detected by the at least one force sensor; andblock from processing reports from the at least one force sensor for the contact made by the object responsive to the determination that initiating the contact by the object was unintentional.
  • 2. A system as described in claim 1, wherein the reports from the at least one force sensor are captured backward in time from a buffer responsive to detection of the proximity of the object by the one or more position sensors.
  • 3. A system as described in claim 1, wherein the force control module is configured to block from processing position reports from the one or more position sensors responsive to the determination that initiating the contact by the object was unintentional.
  • 4. A system as described in claim 1, wherein the force control module is configured to employ a plurality of thresholds to detect the likelihood that the contact made by the object was unintentional, use of the plurality of thresholds dependent on whether user interaction has been detected within a predefined amount of time.
  • 5. A system as described in claim 1, further comprising a haptic feedback mechanism, wherein the force control module is configured to initiate haptic feedback of the haptic feedback mechanism responsive to a determination that initiating the contact by the object was intentional, to support inadvertent input mitigation.
  • 6. A system as described in claim 1, wherein the force control module is configured to calculate a rise time by: recording a first time at which the amount of force in the force signature reaches a first threshold value;recording a second time at which the amount of force in the force signature reaches a second threshold value that is higher than the first threshold value; andcalculating a slope based on the recorded first and second times.
  • 7. An apparatus comprising: a force sensor configured to detect an amount of force applied by an object to an outer surface;a position sensor configured to detect proximity of the object to respective locations of the outer surface; anda force control module implemented at least partially in hardware, the force control module configured to: determine a likelihood that a contact made by the object was unintentional based on an amount of time that passes after the object is detected as being proximal to the outer surface by the position sensor, before the amount of force detected by the force sensor exceeds a threshold and based on whether the amount of force detected by the at least one force sensor is less than a force threshold; andblock from processing a report from the position sensor for the contact made by the object, responsive to the determination that initiating the contact by the object was unintentional.
  • 8. An apparatus as described in claim 7, wherein the force control module is configured: to distinguish the object from a second object; and to detect a corresponding proximity and a corresponding amount of force for the second object.
  • 9. An apparatus as described in claim 8, wherein the force control module is configured to distinguish the object from the second object by correlating the detection of the proximity of the object and subsequent detection of contact by the position sensors with the amount of force applied by the object to the outer surface detected by the force sensor.
  • 10. An apparatus as described in claim 7, wherein the force control module is configured to block from processing a report from the force sensor for the contact made by the object, responsive to the determination that initiating the contact by the object was unintentional.
  • 11. An apparatus as described in claim 7, further comprising a haptic feedback mechanism, wherein the force control module is configured to initiate haptic feedback of the haptic feedback mechanism responsive to a determination that initiating the contact by the object was intentional.
  • 12. An apparatus as described in claim 7, wherein the force control module is configured to permit processing of the report from the position sensor by a computing device responsive to a determination that initiating the contact by the object was intentional.
  • 13. A system comprising: a force sensor configured to detect an amount of force applied by an object to an outer surface;a position sensor configured to detect a location and movement of the object with respect to the outer surface; anda force control module implemented at least partially in hardware, the force control module configured to: determine a likelihood that a contact made by the object was unintentional based on an amount of time that passes after proximity is detected by the one or more position sensors before an amount of force exceeding a first threshold is detected by the at least one force sensorblock from processing reports from the force sensor for the contact made by the object responsive to the determination that initiating the contact by the object was unintentional.
  • 14. A system as described in claim 13, wherein the force control module determines that it is likely the object intended to initiate the contact if the object is not moving and the amount of force is above the first threshold.
  • 15. A system as described in claim 13, further comprising a haptic feedback mechanism, wherein the force control module is configured to initiate haptic feedback of the haptic feedback mechanism responsive to the amount of force being below a second threshold.
  • 16. A system as described in claim 13, further comprising a haptic feedback mechanism, wherein the force control module is configured to initiate haptic feedback of the haptic feedback mechanism responsive to a determination that initiating the contact by the object was intentional.
  • 17. A system as described in claim 13, wherein the force control module is configured to permit processing of the reports by a computing device responsive to a determination that initiating the contact by the object was intentional.
  • 18. A method for identifying an inadvertent input captured by a touch-enabled device, the method comprising: receiving a first signal indicative of proximity of an object to an outer surface of the touch-enabled device, the proximity being detected by at least one position sensor, the at least one position sensor being configured to detect proximity of the object to the outer surface before contact is made between the object and the outer surface; andreceiving a second signal indicative of an amount of force applied by the object to the outer surface of the touch-enabled device, the amount of force being detected by at least one force sensor;examining the first signal in relation to both the second signal and an amount of time during which proximity was detected before contact was made between the object and the outer surface to determine a likelihood that the contact made was an inadvertent input.
  • 19. The method of claim 18, further comprising upon determining that the contact made was an inadvertent input, blocking from processing the second signal for the inadvertent input through use of a confidence bit.
US Referenced Citations (647)
Number Name Date Kind
578325 Fleming Mar 1897 A
4046975 Seeger, Jr. Sep 1977 A
4065649 Carter et al. Dec 1977 A
4243861 Strandwitz Jan 1981 A
4279021 See et al. Jul 1981 A
4302648 Sado et al. Nov 1981 A
4317013 Larson Feb 1982 A
4326193 Markley et al. Apr 1982 A
4365130 Christensen Dec 1982 A
4492829 Rodrique Jan 1985 A
4527021 Morikawa et al. Jul 1985 A
4559426 Van Zeeland et al. Dec 1985 A
4577822 Wilkerson Mar 1986 A
4588187 Dell May 1986 A
4607147 Ono et al. Aug 1986 A
4651133 Ganesan et al. Mar 1987 A
4735394 Facco Apr 1988 A
4890832 Komaki Jan 1990 A
5220521 Kikinis Jun 1993 A
5283559 Kalendra et al. Feb 1994 A
5331443 Stanisci Jul 1994 A
5480118 Cross Jan 1996 A
5489900 Cali et al. Feb 1996 A
5510783 Findlater et al. Apr 1996 A
5546271 Gut et al. Aug 1996 A
5548477 Kumar et al. Aug 1996 A
5558577 Kato Sep 1996 A
5576981 Parker et al. Nov 1996 A
5612719 Beernink et al. Mar 1997 A
5618232 Martin Apr 1997 A
5681220 Bertram et al. Oct 1997 A
5745376 Barker et al. Apr 1998 A
5748114 Koehn May 1998 A
5781406 Hunte Jul 1998 A
5807175 Davis et al. Sep 1998 A
5818361 Acevedo Oct 1998 A
5828770 Leis et al. Oct 1998 A
5842027 Oprescu et al. Nov 1998 A
5859642 Jones Jan 1999 A
5874697 Selker et al. Feb 1999 A
5909211 Combs et al. Jun 1999 A
5912659 Rutledge et al. Jun 1999 A
5926170 Oba Jul 1999 A
5942733 Allen et al. Aug 1999 A
5971635 Wise Oct 1999 A
6002389 Kasser Dec 1999 A
6005209 Burleson et al. Dec 1999 A
6012714 Worley et al. Jan 2000 A
6040823 Seffernick et al. Mar 2000 A
6044717 Biegelsen et al. Apr 2000 A
6061644 Leis May 2000 A
6112797 Colson et al. Sep 2000 A
6147859 Abboud Nov 2000 A
6177926 Kunert Jan 2001 B1
6178443 Lin Jan 2001 B1
6239786 Burry et al. May 2001 B1
6254105 Rinde et al. Jul 2001 B1
6279060 Luke et al. Aug 2001 B1
6329617 Burgess Dec 2001 B1
6344791 Armstrong Feb 2002 B1
6380497 Hashimoto et al. Apr 2002 B1
6429846 Rosenberg et al. Aug 2002 B2
6437682 Vance Aug 2002 B1
6506983 Babb et al. Jan 2003 B1
6511378 Bhatt et al. Jan 2003 B1
6532147 Christ, Jr. Mar 2003 B1
6543949 Ritchey et al. Apr 2003 B1
6565439 Shinohara et al. May 2003 B2
6597347 Yasutake Jul 2003 B1
6600121 Olodort et al. Jul 2003 B1
6603408 Gaba Aug 2003 B1
6617536 Kawaguchi Sep 2003 B2
6651943 Cho et al. Nov 2003 B2
6685369 Lien Feb 2004 B2
6695273 Iguchi Feb 2004 B2
6704864 Philyaw Mar 2004 B1
6721019 Kono et al. Apr 2004 B2
6725318 Sherman et al. Apr 2004 B1
6738049 Kiser et al. May 2004 B2
6758615 Monney et al. Jul 2004 B2
6774888 Genduso Aug 2004 B1
6776546 Kraus et al. Aug 2004 B2
6781819 Yang et al. Aug 2004 B2
6784869 Clark et al. Aug 2004 B1
6813143 Makela Nov 2004 B2
6819316 Schulz et al. Nov 2004 B2
6856506 Doherty et al. Feb 2005 B2
6861961 Sandbach et al. Mar 2005 B2
6864573 Robertson et al. Mar 2005 B2
6898315 Guha May 2005 B2
6914197 Doherty et al. Jul 2005 B2
6950950 Sawyers et al. Sep 2005 B2
6970957 Oshins et al. Nov 2005 B1
6975302 Ausbeck et al. Dec 2005 B1
6976799 Kim et al. Dec 2005 B2
7051149 Wang et al. May 2006 B2
7083295 Hanna Aug 2006 B1
7091436 Serban Aug 2006 B2
7091955 Kramer Aug 2006 B2
7095404 Vincent et al. Aug 2006 B2
7106222 Ward et al. Sep 2006 B2
7116309 Kimura et al. Oct 2006 B1
7123292 Seeger et al. Oct 2006 B1
7194662 Do et al. Mar 2007 B2
7202837 Ihara Apr 2007 B2
7213991 Chapman et al. May 2007 B2
7224830 Nefian et al. May 2007 B2
7245292 Custy Jul 2007 B1
7277087 Hill et al. Oct 2007 B2
7301759 Hsiung Nov 2007 B2
7374312 Feng et al. May 2008 B2
7401992 Lin Jul 2008 B1
7423557 Kang Sep 2008 B2
7446276 Piesko Nov 2008 B2
7447934 Dasari et al. Nov 2008 B2
7469386 Bear et al. Dec 2008 B2
7486165 Ligtenberg et al. Feb 2009 B2
7499037 Lube Mar 2009 B2
7502803 Culter et al. Mar 2009 B2
7542052 Solomon et al. Jun 2009 B2
7557312 Clark et al. Jul 2009 B2
7558594 Wilson Jul 2009 B2
7559834 York Jul 2009 B1
RE40891 Yasutake Sep 2009 E
7602384 Rosenberg et al. Oct 2009 B2
7620244 Collier Nov 2009 B1
7622907 Vranish Nov 2009 B2
7636921 Louie Dec 2009 B2
7639876 Clary et al. Dec 2009 B2
7656392 Bolender Feb 2010 B2
7686694 Cole Mar 2010 B2
7728820 Rosenberg et al. Jun 2010 B2
7728923 Kim et al. Jun 2010 B2
7731147 Rha Jun 2010 B2
7733326 Adiseshan Jun 2010 B1
7736042 Park et al. Jun 2010 B2
7773076 Pittel et al. Aug 2010 B2
7773121 Huntsberger et al. Aug 2010 B1
7774155 Sato et al. Aug 2010 B2
7777972 Chen et al. Aug 2010 B1
7782342 Koh Aug 2010 B2
7813715 McKillop et al. Oct 2010 B2
7815358 Inditsky Oct 2010 B2
7817428 Greer, Jr. et al. Oct 2010 B2
7865639 McCoy et al. Jan 2011 B2
7884807 Hovden et al. Feb 2011 B2
7907394 Richardson et al. Mar 2011 B2
D636397 Green Apr 2011 S
7928964 Kolmykov-Zotov et al. Apr 2011 B2
7936501 Smith et al. May 2011 B2
7945717 Rivalsi May 2011 B2
7952566 Poupyrev et al. May 2011 B2
7970246 Travis et al. Jun 2011 B2
7973771 Geaghan Jul 2011 B2
7976393 Haga et al. Jul 2011 B2
7978281 Vergith et al. Jul 2011 B2
8016255 Lin Sep 2011 B2
8018386 Qi et al. Sep 2011 B2
8018579 Krah Sep 2011 B1
8022939 Hinata Sep 2011 B2
8026904 Westerman Sep 2011 B2
8053688 Conzola et al. Nov 2011 B2
8063886 Serban et al. Nov 2011 B2
8065624 Morin et al. Nov 2011 B2
8069356 Rathi et al. Nov 2011 B2
8077160 Land et al. Dec 2011 B2
8090885 Callaghan et al. Jan 2012 B2
8094134 Suzuki et al. Jan 2012 B2
8098233 Hotelling et al. Jan 2012 B2
8115499 Osoinach et al. Feb 2012 B2
8117362 Rodriguez et al. Feb 2012 B2
8118274 McClure et al. Feb 2012 B2
8118681 Mattice et al. Feb 2012 B2
8130203 Westerman Mar 2012 B2
8154524 Wilson et al. Apr 2012 B2
8162282 Hu et al. Apr 2012 B2
D659139 Gengler May 2012 S
8169421 Wright et al. May 2012 B2
8189973 Travis et al. May 2012 B2
8216074 Sakuma Jul 2012 B2
8229509 Paek et al. Jul 2012 B2
8229522 Kim et al. Jul 2012 B2
8232963 Orsley et al. Jul 2012 B2
8267368 Torii et al. Sep 2012 B2
8269093 Naik et al. Sep 2012 B2
8274784 Franz et al. Sep 2012 B2
8279589 Kim Oct 2012 B2
8279623 Idzik et al. Oct 2012 B2
8322290 Mignano Dec 2012 B1
8330061 Rothkopf et al. Dec 2012 B2
8330742 Reynolds et al. Dec 2012 B2
8378972 Pance et al. Feb 2013 B2
8403576 Merz Mar 2013 B2
8416559 Agata et al. Apr 2013 B2
8487751 Laitinen et al. Jul 2013 B2
8498100 Whitt, III et al. Jul 2013 B1
8570297 Bulea et al. Oct 2013 B2
8607651 Eventoff Dec 2013 B2
8633916 Bernstein et al. Jan 2014 B2
8638315 Algreatly Jan 2014 B2
8659555 Pihlaja Feb 2014 B2
8674961 Posamentier Mar 2014 B2
8757374 Kaiser Jun 2014 B1
8766925 Perlin et al. Jul 2014 B2
8836664 Colgate et al. Sep 2014 B2
8847895 Lim et al. Sep 2014 B2
8854331 Heubel et al. Oct 2014 B2
8928581 Braun et al. Jan 2015 B2
8970525 D Los Reyes Mar 2015 B1
9047012 Bringert et al. Jun 2015 B1
9448631 Winter et al. Sep 2016 B2
9459160 Shaw et al. Oct 2016 B2
20010035859 Kiser Nov 2001 A1
20020000977 Vranish Jan 2002 A1
20020126445 Minaguchi et al. Sep 2002 A1
20020134828 Sandbach et al. Sep 2002 A1
20020154099 Oh Oct 2002 A1
20020188721 Lemel et al. Dec 2002 A1
20030016282 Koizumi Jan 2003 A1
20030044215 Monney et al. Mar 2003 A1
20030063073 Geaghan et al. Apr 2003 A1
20030083131 Armstrong May 2003 A1
20030107557 Liebenow Jun 2003 A1
20030132916 Kramer Jul 2003 A1
20030163611 Nagao Aug 2003 A1
20030197687 Shetter Oct 2003 A1
20030201982 Iesaka Oct 2003 A1
20030206162 Roberts Nov 2003 A1
20040005184 Kim et al. Jan 2004 A1
20040100457 Mandle May 2004 A1
20040174670 Huang et al. Sep 2004 A1
20040190239 Weng et al. Sep 2004 A1
20040212598 Kraus et al. Oct 2004 A1
20040227721 Moilanen et al. Nov 2004 A1
20040258924 Berger et al. Dec 2004 A1
20040268000 Barker et al. Dec 2004 A1
20050030728 Kawashima et al. Feb 2005 A1
20050057515 Bathiche Mar 2005 A1
20050057521 Aull et al. Mar 2005 A1
20050059441 Miyashita Mar 2005 A1
20050059489 Kim Mar 2005 A1
20050146512 Hill et al. Jul 2005 A1
20050190159 Skarine Sep 2005 A1
20050240949 Liu et al. Oct 2005 A1
20050264653 Starkweather et al. Dec 2005 A1
20050264988 Nicolosi Dec 2005 A1
20050285703 Wheeler et al. Dec 2005 A1
20060028095 Maruyama et al. Feb 2006 A1
20060049993 Lin et al. Mar 2006 A1
20060063073 Kawashima et al. Mar 2006 A1
20060082973 Egbert et al. Apr 2006 A1
20060085658 Allen et al. Apr 2006 A1
20060102914 Smits et al. May 2006 A1
20060103633 Gioeli May 2006 A1
20060109252 Kolmykov-Zotov May 2006 A1
20060125799 Hillis et al. Jun 2006 A1
20060132423 Travis Jun 2006 A1
20060154725 Glaser et al. Jul 2006 A1
20060156415 Rubinstein et al. Jul 2006 A1
20060158433 Serban et al. Jul 2006 A1
20060181514 Newman Aug 2006 A1
20060181521 Perreault et al. Aug 2006 A1
20060187216 Trent, Jr. et al. Aug 2006 A1
20060195522 Miyazaki Aug 2006 A1
20060197753 Hotelling Sep 2006 A1
20060197754 Keely Sep 2006 A1
20060197755 Bawany Sep 2006 A1
20060209050 Serban Sep 2006 A1
20060238510 Panotopoulos et al. Oct 2006 A1
20060248597 Keneman Nov 2006 A1
20070043725 Hotelling et al. Feb 2007 A1
20070047221 Park Mar 2007 A1
20070051792 Wheeler et al. Mar 2007 A1
20070056385 Lorenz Mar 2007 A1
20070062089 Homer et al. Mar 2007 A1
20070069153 Pai-Paranjape et al. Mar 2007 A1
20070072474 Beasley et al. Mar 2007 A1
20070145945 McGinley et al. Jun 2007 A1
20070152983 McKillop et al. Jul 2007 A1
20070182663 Biech Aug 2007 A1
20070182722 Hotelling et al. Aug 2007 A1
20070200830 Yamamoto Aug 2007 A1
20070205995 Woolley Sep 2007 A1
20070220708 Lewis Sep 2007 A1
20070234420 Novotney et al. Oct 2007 A1
20070236408 Yamaguchi et al. Oct 2007 A1
20070236472 Bentsen Oct 2007 A1
20070236475 Wherry Oct 2007 A1
20070247338 Marchetto Oct 2007 A1
20070247432 Oakley Oct 2007 A1
20070257821 Son et al. Nov 2007 A1
20070260892 Paul et al. Nov 2007 A1
20070274094 Schultz et al. Nov 2007 A1
20070274095 Destain Nov 2007 A1
20070283179 Burnett et al. Dec 2007 A1
20080005423 Jacobs et al. Jan 2008 A1
20080012835 Rimon et al. Jan 2008 A1
20080013809 Zhu et al. Jan 2008 A1
20080018608 Serban et al. Jan 2008 A1
20080018611 Serban et al. Jan 2008 A1
20080024459 Poupyrev et al. Jan 2008 A1
20080042994 Gillespie Feb 2008 A1
20080094367 Van De Ven et al. Apr 2008 A1
20080104437 Lee May 2008 A1
20080151478 Chern Jun 2008 A1
20080158185 Westerman Jul 2008 A1
20080167832 Soss Jul 2008 A1
20080180411 Solomon et al. Jul 2008 A1
20080202251 Serban et al. Aug 2008 A1
20080202824 Philipp et al. Aug 2008 A1
20080219025 Spitzer et al. Sep 2008 A1
20080228969 Cheah et al. Sep 2008 A1
20080232061 Wang et al. Sep 2008 A1
20080238884 Harish Oct 2008 A1
20080253822 Matias Oct 2008 A1
20080297878 Brown et al. Dec 2008 A1
20080303646 Elwell et al. Dec 2008 A1
20080309636 Feng et al. Dec 2008 A1
20080316002 Brunet et al. Dec 2008 A1
20080316066 Minato et al. Dec 2008 A1
20080320190 Lydon et al. Dec 2008 A1
20090002218 Rigazio et al. Jan 2009 A1
20090007001 Morin et al. Jan 2009 A1
20090009476 Daley, III Jan 2009 A1
20090046416 Daley, III Feb 2009 A1
20090049979 Naik et al. Feb 2009 A1
20090065267 Sato Mar 2009 A1
20090073060 Shimasaki et al. Mar 2009 A1
20090073957 Newland et al. Mar 2009 A1
20090079639 Hotta et al. Mar 2009 A1
20090083562 Park et al. Mar 2009 A1
20090085878 Heubel et al. Apr 2009 A1
20090090568 Min Apr 2009 A1
20090101417 Suzuki et al. Apr 2009 A1
20090106655 Grant Apr 2009 A1
20090117955 Lo May 2009 A1
20090127005 Zachut et al. May 2009 A1
20090128374 Kurth May 2009 A1
20090135142 Fu et al. May 2009 A1
20090140985 Liu Jun 2009 A1
20090160529 Lamborghini Jun 2009 A1
20090163147 Steigerwald et al. Jun 2009 A1
20090167704 Terlizzi et al. Jul 2009 A1
20090174679 Westerman Jul 2009 A1
20090182901 Callaghan et al. Jul 2009 A1
20090195497 Fitzgerald et al. Aug 2009 A1
20090219250 Ure Sep 2009 A1
20090231019 Yeh Sep 2009 A1
20090231275 Odgers Sep 2009 A1
20090250267 Heubel et al. Oct 2009 A1
20090251008 Sugaya Oct 2009 A1
20090259865 Sheynblat et al. Oct 2009 A1
20090262492 Whitchurch et al. Oct 2009 A1
20090265670 Kim et al. Oct 2009 A1
20090267892 Faubert Oct 2009 A1
20090284397 Lee et al. Nov 2009 A1
20090303137 Kusaka et al. Dec 2009 A1
20090303204 Nasiri et al. Dec 2009 A1
20090320244 Lin Dec 2009 A1
20090321490 Groene et al. Dec 2009 A1
20100001963 Doray et al. Jan 2010 A1
20100013319 Kamiyama et al. Jan 2010 A1
20100013613 Weston Jan 2010 A1
20100026656 Hotelling et al. Feb 2010 A1
20100038821 Jenkins et al. Feb 2010 A1
20100039764 Locker et al. Feb 2010 A1
20100045609 Do et al. Feb 2010 A1
20100045633 Gettemy Feb 2010 A1
20100051356 Stern et al. Mar 2010 A1
20100051432 Lin et al. Mar 2010 A1
20100053087 Dai et al. Mar 2010 A1
20100053534 Hsieh et al. Mar 2010 A1
20100075517 Ni et al. Mar 2010 A1
20100077237 Sawyers Mar 2010 A1
20100079398 Shen et al. Apr 2010 A1
20100081377 Chatterjee et al. Apr 2010 A1
20100085321 Pundsack Apr 2010 A1
20100097198 Suzuki Apr 2010 A1
20100102182 Lin Apr 2010 A1
20100103112 Yoo et al. Apr 2010 A1
20100103131 Segal et al. Apr 2010 A1
20100123686 Klinghult et al. May 2010 A1
20100133398 Chiu et al. Jun 2010 A1
20100137033 Lee Jun 2010 A1
20100141588 Kimura et al. Jun 2010 A1
20100142130 Wang et al. Jun 2010 A1
20100149111 Olien Jun 2010 A1
20100149134 Westerman et al. Jun 2010 A1
20100156798 Archer Jun 2010 A1
20100161522 Tirpak et al. Jun 2010 A1
20100162109 Chatterjee et al. Jun 2010 A1
20100162179 Porat Jun 2010 A1
20100164857 Liu et al. Jul 2010 A1
20100171708 Chuang Jul 2010 A1
20100171891 Kaji et al. Jul 2010 A1
20100174421 Tsai et al. Jul 2010 A1
20100180063 Ananny et al. Jul 2010 A1
20100182263 Aunio et al. Jul 2010 A1
20100188299 Rinehart et al. Jul 2010 A1
20100188338 Longe Jul 2010 A1
20100206614 Park et al. Aug 2010 A1
20100206644 Yeh Aug 2010 A1
20100214257 Wussler et al. Aug 2010 A1
20100222110 Kim et al. Sep 2010 A1
20100231498 Large et al. Sep 2010 A1
20100231510 Sampsell et al. Sep 2010 A1
20100231556 Mines et al. Sep 2010 A1
20100238075 Pourseyed Sep 2010 A1
20100238119 Dubrovsky et al. Sep 2010 A1
20100238138 Goertz et al. Sep 2010 A1
20100245221 Khan Sep 2010 A1
20100250988 Okuda et al. Sep 2010 A1
20100274932 Kose Oct 2010 A1
20100279768 Huang et al. Nov 2010 A1
20100289457 Onnerud et al. Nov 2010 A1
20100289508 Joguet et al. Nov 2010 A1
20100295812 Burns et al. Nov 2010 A1
20100302378 Marks et al. Dec 2010 A1
20100304793 Kim et al. Dec 2010 A1
20100306538 Thomas et al. Dec 2010 A1
20100308778 Yamazaki et al. Dec 2010 A1
20100308844 Day et al. Dec 2010 A1
20100315267 Chung Dec 2010 A1
20100315348 Jellicoe et al. Dec 2010 A1
20100321299 Shelley et al. Dec 2010 A1
20100321301 Casparian et al. Dec 2010 A1
20100321330 Lim et al. Dec 2010 A1
20100321339 Kimmel Dec 2010 A1
20100325155 Skinner et al. Dec 2010 A1
20100331059 Apgar et al. Dec 2010 A1
20110007008 Algreatly Jan 2011 A1
20110012873 Prest et al. Jan 2011 A1
20110018556 Le et al. Jan 2011 A1
20110019123 Prest et al. Jan 2011 A1
20110031287 Le Gette et al. Feb 2011 A1
20110036965 Zhang et al. Feb 2011 A1
20110037721 Cranfill et al. Feb 2011 A1
20110043454 Modarres et al. Feb 2011 A1
20110043990 Mickey et al. Feb 2011 A1
20110050587 Natanzon et al. Mar 2011 A1
20110050630 Ikeda Mar 2011 A1
20110055407 Lydon et al. Mar 2011 A1
20110057899 Sleeman et al. Mar 2011 A1
20110060926 Brooks et al. Mar 2011 A1
20110069148 Jones et al. Mar 2011 A1
20110074688 Hull et al. Mar 2011 A1
20110080347 Steeves et al. Apr 2011 A1
20110084909 Hsieh et al. Apr 2011 A1
20110095994 Birnbaum Apr 2011 A1
20110096513 Kim Apr 2011 A1
20110102326 Casparian et al. May 2011 A1
20110102356 Kemppinen et al. May 2011 A1
20110115712 Han et al. May 2011 A1
20110115747 Powell et al. May 2011 A1
20110118025 Lukas et al. May 2011 A1
20110128227 Theimer Jun 2011 A1
20110134032 Chiu et al. Jun 2011 A1
20110134112 Koh et al. Jun 2011 A1
20110141052 Bernstein Jun 2011 A1
20110141053 Bulea et al. Jun 2011 A1
20110147398 Ahee et al. Jun 2011 A1
20110148793 Ciesla et al. Jun 2011 A1
20110157087 Kanehira et al. Jun 2011 A1
20110163955 Nasiri et al. Jul 2011 A1
20110164370 McClure et al. Jul 2011 A1
20110167181 Minoo et al. Jul 2011 A1
20110167287 Walsh et al. Jul 2011 A1
20110167391 Momeyer et al. Jul 2011 A1
20110167992 Eventoff et al. Jul 2011 A1
20110179864 Raasch et al. Jul 2011 A1
20110184646 Wong et al. Jul 2011 A1
20110193787 Morishige et al. Aug 2011 A1
20110193938 Oderwald et al. Aug 2011 A1
20110202878 Park et al. Aug 2011 A1
20110205372 Miramontes Aug 2011 A1
20110216266 Travis Sep 2011 A1
20110227913 Hyndman Sep 2011 A1
20110231682 Kakish et al. Sep 2011 A1
20110234502 Yun et al. Sep 2011 A1
20110241999 Thier Oct 2011 A1
20110242138 Tribble Oct 2011 A1
20110248152 Svajda et al. Oct 2011 A1
20110248920 Larsen Oct 2011 A1
20110248930 Kwok et al. Oct 2011 A1
20110248941 Abdo et al. Oct 2011 A1
20110261001 Liu Oct 2011 A1
20110261021 Modarres et al. Oct 2011 A1
20110261083 Wilson Oct 2011 A1
20110267294 Kildal Nov 2011 A1
20110267300 Serban et al. Nov 2011 A1
20110267757 Probst Nov 2011 A1
20110290686 Huang Dec 2011 A1
20110291922 Stewart et al. Dec 2011 A1
20110295697 Boston et al. Dec 2011 A1
20110297566 Gallagher et al. Dec 2011 A1
20110304577 Brown Dec 2011 A1
20110304962 Su Dec 2011 A1
20110306424 Kazama et al. Dec 2011 A1
20110316807 Corrion Dec 2011 A1
20120007821 Zaliva Jan 2012 A1
20120011462 Westerman et al. Jan 2012 A1
20120013519 Hakansson et al. Jan 2012 A1
20120023459 Westerman Jan 2012 A1
20120024682 Huang et al. Feb 2012 A1
20120026048 Vazquez et al. Feb 2012 A1
20120044179 Hudson Feb 2012 A1
20120047368 Chinn et al. Feb 2012 A1
20120050975 Garelli et al. Mar 2012 A1
20120055770 Chen Mar 2012 A1
20120068933 Larsen Mar 2012 A1
20120068957 Puskarich et al. Mar 2012 A1
20120072167 Cretella, Jr. et al. Mar 2012 A1
20120075221 Yasuda Mar 2012 A1
20120075249 Hoch Mar 2012 A1
20120081316 Sirpal et al. Apr 2012 A1
20120087078 Medica et al. Apr 2012 A1
20120092279 Martin Apr 2012 A1
20120092350 Ganapathi et al. Apr 2012 A1
20120094257 Pillischer et al. Apr 2012 A1
20120098751 Lin Apr 2012 A1
20120099263 Lin Apr 2012 A1
20120099749 Rubin et al. Apr 2012 A1
20120106082 Wu et al. May 2012 A1
20120113579 Agata et al. May 2012 A1
20120115553 Mahe et al. May 2012 A1
20120117409 Lee et al. May 2012 A1
20120127071 Jitkoff et al. May 2012 A1
20120127118 Nolting et al. May 2012 A1
20120139844 Ramstein et al. Jun 2012 A1
20120140396 Zeliff et al. Jun 2012 A1
20120145525 Ishikawa Jun 2012 A1
20120146938 Worfolk et al. Jun 2012 A1
20120155015 Govindasamy et al. Jun 2012 A1
20120162693 Ito Jun 2012 A1
20120175487 Goto Jul 2012 A1
20120182242 Lindahl et al. Jul 2012 A1
20120188180 Yang et al. Jul 2012 A1
20120194393 Uttermann et al. Aug 2012 A1
20120194448 Rothkopf Aug 2012 A1
20120200532 Powell et al. Aug 2012 A1
20120200802 Large Aug 2012 A1
20120206401 Lin et al. Aug 2012 A1
20120206937 Travis et al. Aug 2012 A1
20120223866 Ayala Vazquez et al. Sep 2012 A1
20120224073 Miyahara Sep 2012 A1
20120229401 Birnbaum et al. Sep 2012 A1
20120235635 Sato Sep 2012 A1
20120235921 Laubach Sep 2012 A1
20120235942 Shahoian et al. Sep 2012 A1
20120242588 Myers et al. Sep 2012 A1
20120246377 Bhesania Sep 2012 A1
20120249459 Sashida et al. Oct 2012 A1
20120256959 Ye et al. Oct 2012 A1
20120268412 Cruz-Hernandez et al. Oct 2012 A1
20120268911 Lin Oct 2012 A1
20120274811 Bakin Nov 2012 A1
20120287562 Wu et al. Nov 2012 A1
20120299866 Pao et al. Nov 2012 A1
20120300275 Vilardell et al. Nov 2012 A1
20120304199 Homma et al. Nov 2012 A1
20120312955 Randolph Dec 2012 A1
20120328349 Isaac et al. Dec 2012 A1
20130009892 Salmela et al. Jan 2013 A1
20130044059 Fu Feb 2013 A1
20130047747 Joung, II Feb 2013 A1
20130063364 Moore Mar 2013 A1
20130063389 Moore Mar 2013 A1
20130063873 Wodrich et al. Mar 2013 A1
20130076646 Krah et al. Mar 2013 A1
20130088431 Ballagas et al. Apr 2013 A1
20130088442 Lee Apr 2013 A1
20130094131 O'Donnell et al. Apr 2013 A1
20130097534 Lewin et al. Apr 2013 A1
20130106766 Yilmaz et al. May 2013 A1
20130107144 Marhefka et al. May 2013 A1
20130141370 Wang et al. Jun 2013 A1
20130167663 Eventoff Jul 2013 A1
20130194235 Zanone et al. Aug 2013 A1
20130201115 Heubel Aug 2013 A1
20130207917 Cruz-Hernandez et al. Aug 2013 A1
20130222286 Kang et al. Aug 2013 A1
20130227836 Whitt, III Sep 2013 A1
20130228433 Shaw Sep 2013 A1
20130229273 Nodar Cortizo et al. Sep 2013 A1
20130229356 Marwah et al. Sep 2013 A1
20130229386 Bathiche Sep 2013 A1
20130275058 Awad Oct 2013 A1
20130278542 Stephanou et al. Oct 2013 A1
20130278552 Kamin-Lyndgaard Oct 2013 A1
20130300683 Binbaum et al. Nov 2013 A1
20130304941 Drasnin Nov 2013 A1
20130304944 Young Nov 2013 A1
20130311881 Birnbaum et al. Nov 2013 A1
20130314341 Lee et al. Nov 2013 A1
20130321291 Sim Dec 2013 A1
20130335209 Cruz-Hernandez et al. Dec 2013 A1
20130335330 Lane Dec 2013 A1
20130335902 Campbell Dec 2013 A1
20130335903 Raken Dec 2013 A1
20130342464 Bathiche et al. Dec 2013 A1
20130342465 Bathiche Dec 2013 A1
20130346636 Bathiche Dec 2013 A1
20140008203 Nathan et al. Jan 2014 A1
20140020484 Shaw et al. Jan 2014 A1
20140022177 Shaw Jan 2014 A1
20140028624 Marsden Jan 2014 A1
20140055375 Kim et al. Feb 2014 A1
20140062933 Coulson et al. Mar 2014 A1
20140062934 Coulson et al. Mar 2014 A1
20140083207 Eventoff Mar 2014 A1
20140085247 Leung et al. Mar 2014 A1
20140098058 Baharav et al. Apr 2014 A1
20140139436 Ramstein et al. May 2014 A1
20140139472 Takenaka May 2014 A1
20140152581 Case Jun 2014 A1
20140204059 Geaghan Jul 2014 A1
20140210742 Delattre Jul 2014 A1
20140221098 Boulanger Aug 2014 A1
20140230575 Picciotto et al. Aug 2014 A1
20140232679 Whitman et al. Aug 2014 A1
20140253305 Rosenberg et al. Sep 2014 A1
20140306914 Kagayama Oct 2014 A1
20140313146 Munechika Oct 2014 A1
20140320393 Modarres et al. Oct 2014 A1
20140340356 Takahashi et al. Nov 2014 A1
20140368455 Croisonnier et al. Dec 2014 A1
20150084865 Shaw et al. Mar 2015 A1
20150084909 Worfolk et al. Mar 2015 A1
20150097786 Behles et al. Apr 2015 A1
20150130742 Chen May 2015 A1
20150153951 Kim et al. Jun 2015 A1
20150160778 Kim et al. Jun 2015 A1
20150185842 Picciotto et al. Jul 2015 A1
20150193034 Jeong et al. Jul 2015 A1
20150227207 Winter et al. Aug 2015 A1
20150242012 Petcavich et al. Aug 2015 A1
20150268827 Kim et al. Sep 2015 A1
20150301642 Hanauer et al. Oct 2015 A1
20150370376 Harley et al. Dec 2015 A1
20160018894 Yliaho et al. Jan 2016 A1
20160034087 Kim et al. Feb 2016 A1
20160070398 Worfolk Mar 2016 A1
20160195955 Picciotto et al. Jul 2016 A1
20160334912 Ribeiro Nov 2016 A1
20160357297 Picciotto et al. Dec 2016 A1
20170023418 Shaw et al. Jan 2017 A1
20170102770 Winter et al. Apr 2017 A1
Foreign Referenced Citations (17)
Number Date Country
1223722 Jul 2002 EP
1591891 Nov 2005 EP
2353978 Aug 2011 EP
2381340 Oct 2011 EP
2584432 Apr 2013 EP
2178570 Feb 1987 GB
10326124 Dec 1998 JP
1173239 Mar 1999 JP
11345041 Dec 1999 JP
1020110087178 Aug 2011 KR
1038411 May 2012 NL
WO-2010011983 Jan 2010 WO
WO-2012036717 Mar 2012 WO
WO-2012173305 Dec 2012 WO
2013104919 Jul 2013 WO
WO-2013169299 Nov 2013 WO
WO-2014098946 Jun 2014 WO
Non-Patent Literature Citations (236)
Entry
“Enhancing Your Device Design Through Tactile Feedback”, Immersion, Available at <http://www.immersion.com/docs/Enhancing-Device-Design-Through-Tactile-Feedback.pdf>, Apr. 2011, pp. 1-7.
“Final Office Action”, U.S. Appl. No. 13/655,065, dated Apr. 2, 2015, 23 pages.
“Final Office Action”, U.S. Appl. No. 13/782,137, dated May 8, 2015, 19 pages.
“Final Office Action”, U.S. Appl. No. 13/974,749, dated May 21, 2015, 19 pages.
“Final Office Action”, U.S. Appl. No. 13/974,994, dated Jun. 10, 2015, 28 pages.
“Final Office Action”, U.S. Appl. No. 13/975,087, dated Aug. 7, 2015, 16 pages.
“Final Office Action”, U.S. Appl. No. 14/033,510, dated Jun. 5, 2015, 24 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2014/016743, dated Jul. 24, 2014, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/655,065, dated Aug. 19, 2015, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/769,356, dated Oct. 19, 2015, 23 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/782,137, dated Jan. 30, 2015, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/782,137, dated Oct. 6, 2015, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/033,510, dated Oct. 7, 2015, 23 pages.
“Second Written Opinion”, Application No. PCT/US2014/056185, dated Sep. 15, 2015, 5 pages.
Boulanger,“Method and System for Controlling of an Ambient Multiple Zones Haptic Feedback on Mobile Devices (W231)”, U.S. Appl. No. 14/298,658, filed Jun. 6, 2014., 34 pages.
Poupyrev,“Tactile Interfaces for Small Touch Screens”, In Proceedings of the 16th Annual ACM Symposium on User Interface Software and Technology, Nov. 2, 2003, 4 pages.
Titus,“Give Sensors a Gentle Touch”, http://www.ecnmag.com/articles/2010/01/give-sensors-gentle-touch, Jan. 13, 2010, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/033,508, dated Dec. 3, 2015, 14 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/033,508, dated Jun. 16, 2016, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/698,318, dated Jun. 9, 2016, 2 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2015/067754, dated Apr. 7, 2016, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/025966, dated Jun. 15, 2016, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/591,704, dated Jun. 7, 2016, 32 pages.
“Notice of Allowance”, U.S. Appl. No. 14/033,508, dated May 6, 2016, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 14/698,318, dated May 6, 2016, 13 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 14/033,508, dated Sep. 9, 2016, 2 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/028191, dated Jun. 29, 2016, 14 pages.
“Supplemental Notice of Allowance”, U.S. Appl. No. 14/698,318, dated Aug. 15, 2016, 2 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2015/067754, dated Jan. 10, 2017, 10 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2016/031699, dated Feb. 22, 2017, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/591,704, dated Mar. 10, 2017, 26 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/713,723, dated Jan. 30, 2017, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/283,913, dated Feb. 10, 2017, 20 pages.
“Accessing Device Sensors”, retrieved from <https://developer.palm.com/content/api/dev-guide/pdk/accessing-device-sensors.html> on May 25, 2012, 2011, 4 pages.
“ACPI Docking for Windows Operating Systems”, Retrieved from: <http://vvvvw.scritube.com/limba/engleza/software/ACPI-Docking-for-Windows-Opera331824193.php> on Jul. 6, 2012, 2012, 10 pages.
“Advanced Configuration and Power Management Specification”, Intel Corporation, Microsoft Corporation, Toshiba Corp. Revision 1, Dec. 22, 1996, 364 pages.
“Capacitive Touch Sensors—Application Fields, Technology Overview and Implementation Example”, Fujitsu Microelectronics Europe GmbH; retrieved from http://www.fujitsu.com/downloads/MICRO/fme/articles/fujitsu-whitepaper-capacitive-touch-sensors.pdf on Jul. 20, 2011, Jan. 12, 2010, 12 pages.
“Cholesteric Liquid Crystal”, Retrieved from: <http://en.wikipedia.org/wiki/Cholesteric_liquid_crystal> on Aug. 6, 2012, Jun. 10, 2012, 2 pages.
“Cirago Slim Case®—Protective case with built-in kickstand for your iPhone 5®”, Retrieved from <http://cirago.com/wordpress/wp-content/uploads/2012/10/ipc1500brochure1.pdf> on Jan. 29, 2013, Jan. 2013, 1 page.
“Corrected Notice of Allowance”, U.S. Appl. No. 13/470,633, dated Apr. 9, 2013, 2 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 13/470,633, dated Jul. 2, 2013, 2 pages.
“Developing Next-Generation Human Interfaces using Capacitive and Infrared Proximity Sensing”, Silicon Laboratories, Inc., Available at <http://www.silabs.com/pages/DownloadDoc.aspx?FILEURL=support%20documents/technicaldocs/capacitive%20and%20proximity%20sensing_wp.pdf&src=SearchResults>, Aug. 30, 2010, pp. 1-10.
“Directional Backlighting for Display Panels”, U.S. Appl. No. 13/021,448, filed Feb. 4, 2011, 38 pages.
“DR2PA”, retrieved from <http://www.architainment.co.uk/wp-content/uploads/2012/08/DR2PA-AU-US-size-Data-Sheet-Rev-H_LOGO.pdf> on Sep. 17, 2012, Jan. 2012, 4 pages.
“Ex Parte Quayle Action”, U.S. Appl. No. 13/599,763, filed Nov. 14, 2014, 6 pages.
“Final Office Action”, U.S. Appl. No. 13/471,001, dated Jul. 25, 2013, 20 pages.
“Final Office Action”, U.S. Appl. No. 13/527,263, dated Jan. 27, 2015, 7 pages.
“Final Office Action”, U.S. Appl. No. 13/603,918, dated Mar. 21, 2014, 14 pages.
“Final Office Action”, U.S. Appl. No. 13/647,479, dated Dec. 12, 2014, 12 pages.
“Final Office Action”, U.S. Appl. No. 13/651,195, dated Apr. 18, 2013, 13 pages.
“Final Office Action”, U.S. Appl. No. 13/651,232, dated May 21, 2013, 21 pages.
“Final Office Action”, U.S. Appl. No. 13/651,287, dated May 3, 2013, 16 pages.
“Final Office Action”, U.S. Appl. No. 13/651,976, dated Jul. 25, 2013, 21 pages.
“Final Office Action”, U.S. Appl. No. 13/653,321, dated Aug. 2, 2013, 17 pages.
“Final Office Action”, U.S. Appl. No. 13/655,065, dated Aug. 8, 2014, 20 pages.
“Final Office Action”, U.S. Appl. No. 13/769,356, dated Apr. 10, 2015, 9 pages.
“Final Office Action”, U.S. Appl. No. 13/974,749, dated Sep. 5, 2014, 18 pages.
“Final Office Action”, U.S. Appl. No. 13/974,994, dated Oct. 6, 2014, 26 pages.
“Final Office Action”, U.S. Appl. No. 13/975,087, dated Sep. 10, 2014, 19 pages.
“Final Office Action”, U.S. Appl. No. 14/033,510, dated Aug. 21, 2014, 18 pages.
“First One Handed Fabric Keyboard with Bluetooth Wireless Technology”, Retrieved from: <http://press.xtvworld.com/article3817.html> on May 8, 2012, Jan. 6, 2005, 2 pages.
“Force and Position Sensing Resistors: An Emerging Technology”, Interlink Electronics, Available at <http://staff.science.uva.nl/˜vlaander/docu/FSR/An_Exploring_Technology.pdf>, Feb. 1990, pp. 1-6.
“Frogpad Introduces Weareable Fabric Keyboard with Bluetooth Technology”, Retrieved from: <http://www.geekzone.co.nz/content.asp?contentid=3898> on May 7, 2012, Jan. 7, 2005, 3 pages.
“How to Use the iPad's Onscreen Keyboard”, Retrieved from <http://www.dummies.com/how-to/content/how-to-use-the-ipads-onscreen-keyboard.html> on Aug. 28, 2012, 2012, 3 pages.
“IControlPad 2—The open source controller”, Retrieved from <http://www.kickstarter.com/projects/1703567677/icontrolpad-2-the-open-source-controller> on Nov. 20, 2012, 2012, 15 pages.
“I-Interactor electronic pen”, Retrieved from: <http://www.alibaba.com/product-gs/331004878/i_Interactor_electronic_pen.html> on Jun. 19, 2012, 2012, 5 pages.
“Incipio LG G-Slate Premium Kickstand Case—Black Nylon”, Retrieved from: <http://www.amazon.com/Incipio-G-Slate-Premium-Kickstand-Case/dp/B004ZKP916> on May 8, 2012, 2012, 4 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2014/068687, dated Mar. 18, 2015, 10 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2014/016151, dated May 16, 2014, 10 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2014/056185, dated Dec. 4, 2014, 10 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2013/028948, dated Jun. 21, 2013, 11 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2013/029461, dated Jun. 21, 2013, 11 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2013/040968, dated Sep. 5, 2013, 11 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2013/044871, dated Aug. 14, 2013, 12 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2014/014522, dated Jun. 6, 2014, 13 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2013/045283, dated Mar. 12, 2014, 19 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2013/044873, dated Nov. 22, 2013, 9 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2013/045049, dated Sep. 16, 2013, 9 pages.
“Membrane Keyboards & Membrane Keypads”, Retrieved from: <http://www.pannam.com/> on May 9, 2012, Mar. 4, 2009, 2 pages.
“Microsoft Tablet PC”, Retrieved from <http://web.archive.org/web/20120622064335/https://en.wikipedia.org/wiki/Microsoft_Tablet_PC> on Jun. 4, 2014, Jun. 21, 2012, 9 pages.
“Motion Sensors”, Android Developers—retrieved from <http://developer.android.com/guide/topics/sensors/sensors_motion.html> on May 25, 2012, 2012, 7 pages.
“MPC Fly Music Production Controller”, AKAI Professional, Retrieved from: <http://www.akaiprompc.com/mpc-fly> on Jul. 9, 2012, 4 pages.
“NI Releases New Maschine & Maschine Mikro”, Retrieved from <http://www.djbooth.net/index/dj-equipment/entry/ni-releases-new-maschine-mikro/> on Sep. 17, 2012, 19 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/021,448, dated Dec. 13, 2012, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/471,001, dated Feb. 19, 2013, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/471,139, dated Mar. 21, 2013, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/471,202, dated Feb. 11, 2013, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/471,336, dated Jan. 18, 2013, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/527,263, dated Apr. 3, 2014, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/527,263, dated Jul. 19, 2013, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/563,435, dated Jun. 14, 2013, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/564,520, dated Jun. 19, 2013, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/565,124, dated Jun. 17, 2013, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/599,763, dated May 28, 2014, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/603,918, dated Sep. 2, 2014, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/603,918, dated Dec. 19, 2013, 12 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/645,405, dated Jan. 31, 2014, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/645,405, dated Aug. 11, 2014, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/647,479, dated Jul. 3, 2014, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,195, dated Jan. 2, 2013, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,232, dated Jan. 17, 2013, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,272, dated Feb. 12, 2013, 10 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,287, dated Jan. 29, 2013, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,304, dated Mar. 22, 2013, 9 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,327, dated Mar. 22, 2013, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,726, dated Apr. 15, 2013, 6 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,871, dated Mar. 18, 2013, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,871, dated Jul. 1, 2013, 5 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/651,976, dated Feb. 22, 2013, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/653,321, dated Feb. 1, 2013, 13 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/653,682, dated Feb. 7, 2013, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/653,682, dated Jun. 3, 2013, 14 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/655,065, dated Apr. 24, 2014, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/655,065, dated Dec. 19, 2014, 24 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/656,055, dated Apr. 23, 2013, 11 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/656,520, dated Feb. 1, 2013, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/656,520, dated Jun. 5, 2013, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/759,875, dated Aug. 1, 2014, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/769,356, dated Nov. 20, 2014, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/974,749, dated Feb. 12, 2015, 15 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/974,749, dated May 8, 2014, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/974,994, dated Jan. 23, 2015, 26 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/974,994, dated Jun. 4, 2014, 24 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/975,087, dated Feb. 27, 2015, 20 pages.
“Non-Final Office Action”, U.S. Appl. No. 13/975,087, dated May 8, 2014, 18 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/033,510, dated Feb. 12, 2015, 17 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/033,510, dated Jun. 5, 2014, 16 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/144,876, dated Jun. 10, 2015, 23 pages.
“Notice of Allowance”, U.S. Appl. No. 13/470,633, dated Mar. 22, 2013, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 13/471,202, dated May 28, 2013, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 13/599,763, dated Feb. 18, 2015, 4 pages.
“Notice of Allowance”, U.S. Appl. No. 13/603,918, dated Jan. 22, 2015, 8 pages.
“Notice of Allowance”, U.S. Appl. No. 13/651,195, dated Jul. 8, 2013, 9 pages.
“Notice of Allowance”, U.S. Appl. No. 13/651,272, dated May 2, 2013, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 13/651,304, dated Jul. 1, 2013, 5 pages.
“Notice of Allowance”, U.S. Appl. No. 13/651,327, dated Jun. 11, 2013, 7 pages.
“Notice of Allowance”, U.S. Appl. No. 13/651,726, dated May 31, 2013, 5 pages.
“On-Screen Keyboard for Windows 7, Vista, XP with Touchscreen”, Retrieved from <www.comfort-software.com/on-screen-keyboard.html> on Aug. 28, 2012, Feb. 2, 2011, 3 pages.
“Optical Sensors in Smart Mobile Devices”, ON Semiconductor, TND415/D, Available at <http://www.onsemi.jp/pub_link/Collateral/TND415-D.PDF>, Nov. 2010, pp. 1-13.
“Optics for Displays: Waveguide-based Wedge Creates Collimated Display Backlight”, OptoIQ, retrieved from <http://www.optoiq.com/index/photonics-technologies-applications/Ifw-display/Ifw-article-display.articles.laser-focus-world.volume-46.issue-1.world-news.optics-for_displays.html> on Nov. 2, 2010, Jan. 1, 2010, 3 pages.
“Position Sensors”, Android Developers—retrieved from <http://developer.android.com/guide/topics/sensors/sensors_position.html> on May 25, 2012, 5 pages.
“Reflex LCD Writing Tablets”, retrieved from <http://www.kentdisplays.com/products/lcdwritingtablets.html> on Jun. 27, 2012, 3 pages.
“Restriction Requirement”, U.S. Appl. No. 13/603,918, dated Nov. 27, 2013, 8 pages.
“Restriction Requirement”, U.S. Appl. No. 13/471,139, dated Jan. 17, 2013, 7 pages.
“Restriction Requirement”, U.S. Appl. No. 13/651,304, dated Jan. 18, 2013, 7 pages.
“Restriction Requirement”, U.S. Appl. No. 13/651,726, dated Feb. 22, 2013, 6 pages.
“Restriction Requirement”, U.S. Appl. No. 13/651,871, dated Feb. 7, 2013, 6 pages.
“Restriction Requirement”, U.S. Appl. No. 13/715,229, dated Aug. 13, 2013, 7 pages.
“SMART Board™ Interactive Display Frame Pencil Pack”, Available at <http://downloads01.smarttech.com/media/sitecore/en/support/product/sbfpd/400series(interactivedisplayframes)/guides/smartboardinteractivedisplayframepencilpackv12mar09.pdf>, 2009, 2 pages.
“Snugg iPad 3 Keyboard Case—Cover Ultra Slim Bluetooth Keyboard Case for the iPad 3 & iPad 2”, Retrieved from <https://web.archive.org/web/20120810202056/http://www.amazon.com/Snugg-iPad-Keyboard-Case-Bluetooth/dp/B008CCHXJE> on Jan. 23, 2015, Aug. 10, 2012, 4 pages.
“SolRxTM E-Series Multidirectional Phototherapy ExpandableTM 2-Bulb Full Body Panel System”, Retrieved from: <http://www.solarcsystems.com/us_multidirectional_uv_light_therapy_1_intro.html > on Jul. 25, 2012, 2011, 4 pages.
“Tactile Feedback Solutions Using Piezoelectric Actuators”, Available at: http://www.eetimes.com/document.asp?doc_id=1278418, Nov. 17, 2010, 6 pages.
“The Microsoft Surface Tablets Comes With Impressive Design and Specs”, Retrieved from <http://microsofttabletreview.com/the-microsoft-surface-tablets-comes-with-impressive-design-and-specs> on Jan. 30, 2013, Jun. 2012, 2 pages.
“Tilt Shift Lenses: Perspective Control”, retrieved from http://www.cambridgeincolour.com/tutorials/tilt-shift-lenses1.htm, Mar. 28, 2008, 11 Pages.
“Virtualization Getting Started Guide”, Red Hat Enterprise Linux 6, Edition 0.2—retrieved from <http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html-single/Virtualization_Getting_Started_Guide/index.html> on Jun. 13, 2012, 24 pages.
“Visus Photonics—Visionary Technologies New Generation of Production Ready Keyboard-Keypad Illumination Systems”, Available at: <http://www.visusphotonics.com/pdf/appl_keypad_keyboard_backlights.pdf>, May 2006, pp. 1-22.
“What is Active Alignment?”, http://www.kasalis.com/active_alignment.html, retrieved on Nov. 22, 2012, Nov. 22, 2012, 2 Pages.
“Write & Learn Spellboard Advanced”, Available at <http://somemanuals.com/VTECH,WRITE%2526LEARN--SPELLBOARD--ADV--71000,JIDFHE.PDF>, 2006, 22 pages.
“Writer 1 for iPad 1 keyboard + Case (Aluminum Bluetooth Keyboard, Quick Eject and Easy Angle Function!)”, Retrieved from <https://web.archive.org/web/20120817053825/http://www.amazon.com/keyboard-Aluminum-Bluetooth-Keyboard-Function/dp/B004OQLSLG> on Jan. 23, 2015, Aug. 17, 2012, 5 pages.
Akamatsu,“Movement Characteristics Using a Mouse with Tactile and Force Feedback”, In Proceedings of International Journal of Human-Computer Studies 45, No. 4, Oct. 1996, 11 pages.
Bathiche,“Input Device with Interchangeable Surface”, U.S. Appl. No. 13/974,749, filed Aug. 23, 2013, 51 pages.
Block,“DeviceOrientation Event Specification”, W3C, Editor's Draft, retrieved from <https://developer.palm.com/content/api/dev-guide/pdk/accessing-device-sensors.html> on May 25, 2012, Jul. 12, 2011, 14 pages.
Brown,“Microsoft Shows Off Pressure-Sensitive Keyboard”, retrieved from <http://news.cnet.com/8301-17938_105-10304792-1.html> on May 7, 2012, Aug. 6, 2009, 2 pages.
Butler,“SideSight: Multi-“touch” Interaction around Small Devices”, In the proceedings of the 21st annual ACM symposium on User interface software and technology., retrieved from <http://research.microsoft.com/pubs/132534/sidesight_crv3.pdf> on May 29, 2012, Oct. 19, 2008, 4 pages.
Chu,“Design and Analysis of a Piezoelectric Material Based Touch Screen With Additional Pressure and Its Acceleration Measurement Functions”, In Proceedings of Smart Materials and Structures, vol. 22, Issue 12, Nov. 1, 2013, 2 pages.
Crider,“Sony Slate Concept Tablet “Grows” a Kickstand”, Retrieved from: <http://androidcommunity.com/sony-slate-concept-tablet-grows-a-kickstand-20120116/> on May 4, 2012, Jan. 16, 2012, 9 pages.
Das,“Study of Heat Transfer through Multilayer Clothing Assemblies: A Theoretical Prediction”, Retrieved from <http://www.autexrj.com/cms/zalaczone_pliki/5_013_11.pdf>, Jun. 2011, 7 pages.
Dietz,“A Practical Pressure Sensitive Computer Keyboard”, In Proceedings of UIST 2009, Oct. 2009, 4 pages.
Gaver,“A Virtual Window on Media Space”, retrieved from <http://www.gold.ac.uk/media/15gaver-smets-overbeeke.MediaSpaceWindow.chi95.pdf> on Jun. 1, 2012, retrieved from <http://www.gold.ac.uk/media/15gaver-smets-overbeeke.MediaSpaceWindow.chi95.pdf> on Jun. 1, 2012, May 7, 1995, 9 pages.
Glatt,“Channel and Key Pressure (Aftertouch).”, Retrieved from: <http://home.roadrunner.com/˜jgglatt/tutr/touch.htm> on Jun. 11, 2012, 2012, 2 pages.
Gong,“PrintSense: A Versatile Sensing Technique to Support Multimodal Flexible Surface Interaction”, In Proceedings of the SIGCHI Conference on Human Factors in Computing Systems; retrieved from: http://dl.acm.org/citation.cfm?id=2556288.2557173&coll=DL&dl=ACM&CFID=571580473&CFTOKEN=89752233 on Sep. 19, 2014, Apr. 26, 2014, 4 pages.
Hanlon,“ElekTex Smart Fabric Keyboard Goes Wireless”, Retrieved from: <http://www.gizmag.com/go/5048/ > on May 7, 2012, Jan. 15, 2006, 5 pages.
Harada,“VoiceDraw: A Hands-Free Voice-Driven Drawing Application for People With Motor Impairments”, In Proceedings of Ninth International ACM SIGACCESS Conference on Computers and Accessibility, retrieved from <http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.113.7211&rep=rep1&type=pdf> on Jun. 1, 2012, Oct. 15, 2007, 8 pages.
Hinckley,“Touch-Sensing Input Devices”, In Proceedings of ACM SIGCHI 1999, May 15, 1999, 8 pages.
Hughes,“Apple's haptic touch feedback concept uses actuators, senses force on iPhone, iPad”, Retrieved from: http://appleinsider.com/articles/12/03/22/apples_haptic_touch_feedback_concept_uses_actuators_senses_force_on_iphone_ipad, Mar. 22, 2012, 5 pages.
Iwase,“Multistep Sequential Batch Assembly of Three-Dimensional Ferromagnetic Microstructures with Elastic Hinges”, Retrieved at <<http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1549861>> Proceedings: Journal of Microelectromechanical Systems, Dec. 2005, 7 pages.
Kaufmann,“Hand Posture Recognition Using Real-time Artificial Evolution”, EvoApplications'09, retrieved from <http://evelyne.lutton.free.fr/Papers/KaufmannEvolASP2010.pdf> on Jan. 5, 2012, Apr. 3, 2010, 10 pages.
Kaur,“Vincent Liew's redesigned laptop satisfies ergonomic needs”, Retrieved from: <http://www.designbuzz.com/entry/vincent-liew-s-redesigned-laptop-satisfies-ergonomic-needs/> on Jul. 27, 2012, Jun. 21, 2010, 4 pages.
Khuntontong,“Fabrication of Molded Interconnection Devices by Ultrasonic Hot Embossing on Thin Polymer Films”, IEEE Transactions on Electronics Packaging Manufacturing, vol. 32, No. 3, Jul. 2009, pp. 152-156.
Kyung,“TAXEL: Initial Progress Toward Self-Morphing Visio-Haptic Interface”, Proceedings: In IEEE World Haptics Conference, Jun. 21, 2011, 6 pages.
Lane,“Media Processing Input Device”, U.S. Appl. No. 13/655,065, filed Oct. 18, 2012, 43 pages.
Li,“Characteristic Mode Based Tradeoff Analysis of Antenna-Chassis Interactions for Multiple Antenna Terminals”, In IEEE Transactions on Antennas and Propagation, Retrieved from <http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=6060882>, Feb. 2012, 13 pages.
Linderholm,“Logitech Shows Cloth Keyboard for PDAs”, Retrieved from: <http://www.pcworld.com/article/89084/logitech_shows_cloth_keyboard_for_pdas.html> on May 7, 2012, Mar. 15, 2002, 5 pages.
Mackenzie,“The Tactile Touchpad”, In Proceedings of the ACM CHI Human Factors in Computing Systems Conference Available at: <http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.150.4780&rep=rep1&type=pdf>, Mar. 22, 1997, 2 pages.
Manresa-Yee,“Experiences Using a Hands-Free Interface”, In Proceedings of the 10th International ACM SIGACCESS Conference on Computers and Accessibility, retrieved from <http://dmi.uib.es/˜cmanresay/Research/%5BMan08%5DAssets08.pdf> on Jun. 1, 2012, Oct. 13, 2008, pp. 261-262.
McLellan,“Eleksen Wireless Fabric Keyboard: a first look”, Retrieved from: <http://www.zdnetasia.com/eleksen-wireless-fabric-keyboard-a-first-look-40278954.htm> on May 7, 2012, Jul. 17, 2006, 9 pages.
McPherson,“TouchKeys: Capacitive Multi-Touch Sensing on a Physical Keyboard”, In Proceedings of NIME 2012, May 2012, 4 pages.
Miller,“MOGA gaming controller enhances the Android gaming experience”, Retrieved from <http://www.zdnet.com/moga-gaming-controller-enhances-the-android-gaming-experience-7000007550/> on Nov. 20, 2012, Nov. 18, 2012, 9 pages.
Nakanishi,“Movable Cameras Enhance Social Telepresence in Media Spaces”, In Proceedings of the 27th International Conference on Human Factors in Computing Systems, retrieved from <http://smg.ams.eng.osaka-u.ac.jp/˜nakanishi/hnp_2009_chi.pdf> on Jun. 1, 2012, Apr. 6, 2009, 10 pages.
Picciotto,“Piezo-Actuated Virtual Buttons for Touch Surfaces”, U.S. Appl. No. 13/769,356, filed Feb. 17, 2013, 31 pages.
Piltch,“ASUS Eee Pad Slider SL101 Review”, Retrieved from <http://www.laptopmag.com/review/tablets/asus-eee-pad-slider-sl101.aspx>, Sep. 22, 2011, 5 pages.
Post,“E-Broidery: Design and Fabrication of Textile-Based Computing”, IBM Systems Journal, vol. 39, Issue 3 & 4, Jul. 2000, pp. 840-860.
Poupyrev,“Ambient Touch: Designing Tactile Interfaces for Handheld Devices”, In Proceedings of the 15th Annual ACM Symposium on User Interface Software and Technology Available at: <http://www.ivanpoupyrev.com/e-library/2002/uist2002_ambientouch.pdf>, Oct. 27, 2002, 10 pages.
Purcher,“Apple is Paving the Way for a New 3D GUI for IOS Devices”, Retrieved from: <http://www.patentlyapple.com/patently-apple/2012/01/apple-is-paving-the-way-for-a-new-3d-gui-for-ios-devices.html> on Jun. 4, 2012, Retrieved from: <http://www.patentlyapple.com/patently-apple/2012/01/apple-is-paving-the-way-for-a-new-3d-gui-for-ios-devices.html> on Jun. 4, 2012, Jan. 12, 2012, 15 pages.
Qin,“pPen: Enabling Authenticated Pen and Touch Interaction on Tabletop Surfaces”, In Proceedings of ITS 2010, Available at <http://www.dfki.de/its2010/papers/pdf/po172.pdf>, Nov. 2010, pp. 283-284.
Reilink,“Endoscopic Camera Control by Head Movements for Thoracic Surgery”, In Proceedings of 3rd IEEE RAS & EMBS International Conference of Biomedical Robotics and Biomechatronics, retrieved from <http://doc.utwente.nl/74929/1/biorob_online.pdf> on Jun. 1, 2012, Sep. 26, 2010, pp. 510-515.
Rendl,“PyzoFlex: Printed Piezoelectric Pressure Sensing Foil”, In Proceedings of the 25th Annual ACM Symposium on User Interface Software and Technology, Oct. 7, 2012, 10 pages.
Shaw,“Input Device Configuration having Capacitive and Pressure Sensors”, U.S. Appl. No. 14/033,510, filed Sep. 22, 2013, 55 pages.
Staff,“Gametel Android controller turns tablets, phones into portable gaming devices”, Retrieved from <http://www.mobiletor.com/2011/11/18/gametel-android-controller-turns-tablets-phones-into-portable-gaming-devices/#> on Nov. 20, 2012, Nov. 18, 2011, 5 pages.
Sumimoto,“Touch & Write: Surface Computing With Touch and Pen Input”, Retrieved from: <http://www.gottabemobile.com/2009/08/07/touch-write-surface-computing-with-touch-and-pen-input/> on Jun. 19, 2012, Aug. 7, 2009, 4 pages.
Sundstedt,“Gazing at Games: Using Eye Tracking to Control Virtual Characters”, In ACM SIGGRAPH 2010 Courses, retrieved from <http://www.tobii.com/Global/Analysis/Training/EyeTrackAwards/veronica_sundstedtpdf> on Jun. 1, 2012, Jul. 28, 2010, 85 pages.
Takamatsu,“Flexible Fabric Keyboard with Conductive Polymer-Coated Fibers”, In Proceedings of Sensors 2011, Oct. 28, 2011, 4 pages.
Travis,“Collimated Light from a Waveguide for a Display Backlight”, Optics Express, 19714, vol. 17, No. 22, retrieved from <http://download.microsoft.com/download/D/2/E/D2E425F8-CF3C-4C71-A4A2-70F9D4081007/OpticsExpressbacklightpaper.pdf> on Oct. 15, 2009, Oct. 15, 2009, 6 pages.
Travis,“The Design of Backlights for View-Sequential 3D”, retrieved from <http://download.microsoft.com/download/D/2/E/D2E425F8-CF3C-4C71-A4A2-70F9D4081007/Backlightforviewsequentialautostereo.docx> on Nov. 1, 2010, 4 pages.
Tuite,“Haptic Feedback Chips Make Virtual-Button Applications on Handheld Devices a Snap”, Retrieved at: http://electronicdesign.com/analog/haptic-feedback-chips-make-virtual-button-applications-handheld-devices-snap, Sep. 10, 2009, 7 pages.
Valli,“Notes on Natural Interaction”, retrieved from <http://www.idemployee.id.tue.nl/g.w.m.rauterberg/lecturenotes/valli-2004.pdf> on Jan. 5, 2012, Sep. 2005, 80 pages.
Valliath,“Design of Hologram for Brightness Enhancement in Color LCDs”, Retrieved from <http://www.loreti.it/Download/PDF/LCD/44_05.pdf> on Sep. 17, 2012, May 1998, 5 pages.
Vaucelle,“Scopemate, a Robotic Microscope!”, Architectradure, retrieved from <http://architectradure.blogspot.com/2011/10/at-uist-this-monday-scopemate-robotic.html> on Jun. 6, 2012, Oct. 17, 2011, 2 pages.
Williams,“A Fourth Generation of LCD Backlight Technology”, Retrieved from <http://cds.linear.com/docs/Application%20Note/an65f.pdf>, Nov. 1995, 124 pages.
Xu,“Hand Gesture Recognition and Virtual Game Control Based on 3D Accelerometer and EMG Sensors”, IUI'09, Feb. 8-11, 2009, retrieved from <http://sclab.yonsei.ac.kr/courses/10TPR/10TPR.files/Hand%20Gesture%20Recognition%20and%20Virtual%20Game%20Control%20based%20on%203d%20accelerometer%20and%20EMG%20sensors.pdf> on Jan. 5, 2012, Feb. 8, 2009, 5 pages.
Xu,“Vision-based Detection of Dynamic Gesture”, ICTM'09, Dec. 5-6, 2009, retrieved from <http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5412956> on Jan. 5, 2012, Dec. 5, 2009, pp. 223-226.
Zhang,“Model-Based Development of Dynamically Adaptive Software”, In Proceedings of ICSE 2006, Available at <http://www.irisa.fr/lande/lande/icse-proceedings/icse/p371.pdf>, May 20, 2006, pp. 371-380.
Zhu,“Keyboard before Head Tracking Depresses User Success in Remote Camera Control”, In Proceedings of 12th IFIP TC 13 International Conference on Human-Computer Interaction, Part II, retrieved from <http://csiro.academia.edu/Departments/CSIRO_ICT_Centre/Papers?page=5> on Jun. 1, 2012, Aug. 24, 2009, 14 pages.
“Final Office Action”, U.S. Appl. No. 14/591,704, dated Nov. 25, 2016, 33 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/031700, dated Nov. 3, 2016, 20 pages.
“International Search Report and Written Opinion”, Application No. PCT/US2016/031699, dated Nov. 11, 2016, 23 pages.
“Non-Final Office Action”, U.S. Appl. No. 14/729,887, dated Dec. 22, 2016, 22 pages.
“Second Written Opinion”, Application No. PCT/US2015/067754, dated Nov. 25, 2016, 8 pages.
“Corrected Notice of Allowance”, U.S. Appl. No. 15/283,913, dated Sep. 27, 2017, 2 pages.
“Final Office Action”, U.S. Appl. No. 14/713,723, dated Jul. 21, 2017, 19 pages.
“Final Office Action”, U.S. Appl. No. 14/729,887, dated May 17, 2017, 21 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2016/031700, dated Sep. 4, 2017, 13 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2016/025966, dated May 22, 2017, 8 pages.
“International Preliminary Report on Patentability”, Application No. PCT/US2016/028191, dated Jul. 17, 2017, 8 pages.
“Non-Final Office Action”, U.S. Appl. No. 15/269,594, dated Jun. 7, 2017, 27 pages.
“Notice of Allowance”, U.S. Appl. No. 14/591,704, dated Aug. 21, 2017, 15 pages.
“Notice of Allowance”, U.S. Appl. No. 15/283,913, dated Sep. 6, 2017, 9 pages.
“Second Written Opinion”, Application No. PCT/US2016/025966, dated Mar. 14, 2017, 7 pages.
“Second Written Opinion”, Application No. PCT/US2016/028191, dated Apr. 18, 2017, 7 pages.
“Second Written Opinion”, Application No. PCT/US2016/031700, dated Jun. 27, 2017, 12 pages.
“Non Final Office Action Issued in U.S. Appl. No. 14/713,723”, dated Oct. 5, 2017, 22 Pages.
“Non Final Office Action Issued in U.S. Appl. No. 14/729,887”, dated Dec. 1, 2017, 16 Pages.
“Apple Updates 13-inch MacBook Pro with Retina Display & MacBook Air”, Retrieved from: https://www.apple.com/in/newsroom/2015/03/09Apple-Updates-13-inch-MacBook-Pro-with-Retina-Display-MacBook-Air/, Mar. 9, 2015, 3 Pages.
“Mouse and Trackpad”, Retrieved from: https://developer.apple.com/design/human-interface-guidelines/macos/user-interaction/mouse-and-trackpad/, Jun. 18, 2018, 5 Pages.
Ledet, Raleigh, “Adopting New Trackpad Features”, Retrieved from: https://developer.apple.com/videos/play/wwdc2015/217/?time=180, Jan. 2015, 168 Pages.
“Office Action Issued in European Patent Application No. 16732366.6”, dated Jul. 15, 2019, 7 Pages.
Related Publications (1)
Number Date Country
20160357296 A1 Dec 2016 US