Source: https://patents.google.com/patent/US9582122B2/en
Timestamp: 2019-04-19 10:03:51+00:00

Document:
Touch-sensitive bezel techniques are described. In one or more implementations, touch sensors located in a display portion and a bezel portion detect a touch input and determine, based on one or more characteristics of the touch input, a likelihood that a user intends or does not intend to interact with the computing device. A location of a centroid of an area of the touch input is on such characteristic that can be utilized. In at least some implementations, the bezel portion has display capabilities such that when a touch input is detected, the display capabilities in a region of the bezel portion can be made active to cause a menu to be displayed in the region of the bezel.
Various mobile devices, such as tablet PCs, hand-held devices, and small multi-screen devices, include wide bezels to enable a user to hold the device without accidentally touching the combined display and touch screen. Even with the inclusion of a wide bezel, however, accidental touches can occur. When a user accidentally touches the screen, for instance, the device may perform undesired actions because it is unable to distinguish between an intentional touch by the user and an accidental touch by the user while the user is holding the device.
For example, when a user's thumb accidentally touches the display while the user is holding the device, the device can open or close an application or take another action in response to the touch. This can result in user frustration as undesired actions are performed because a small portion of the user's thumb has contacted the display. Consequently, these undesired actions may force device designer to sacrifice display size for a wider bezel.
Touch-sensitive bezel techniques are described. Touch sensors are located in a bezel portion and a display portion of a display device of a computing device. The touch sensors detect a touch input and are used to determine, based on characteristics of the touch input, a likelihood that a user does not intend to interact with the computing device. Various factors can be used in determining the likelihood that the user does not intend to interact with the computing device. The location of a centroid of the touch input is one such factor.
In one or more implementations, a device includes touch sensors in a display portion of a display device and in a bezel portion of the display device. The touch sensors detect a touch input. One or more modules of the device determine a likelihood of whether the touch input is indicative of a user's intention to interact with a user interface displayed by the display device of the device or a user's intention to not interact with the user interface displayed by the display device of the device.
In one or more implementations, one or more touch sensors located in a bezel portion and a display portion of a display device detect a touch input while display capabilities of a region of the bezel portion are inactive. Responsive to detection of the touch input, the display capabilities of the region of the bezel portion are made active to cause a menu to be displayed in the region bezel.
FIG. 1 is an illustration of an environment having a device including touch sensors in a bezel portion and a display portion of a display device to implement the techniques described herein.
FIG. 2 is an illustration of a display device having a bezel portion and a display portion in accordance with one or more implementations.
FIG. 3 is an illustration of an example centroid of a touch input in accordance with one or more implementations.
FIG. 4 is an illustration of an example centroid of another touch input in accordance with one or more embodiments.
FIG. 5 illustrates an example implementation of a display device displaying a menu in a region of the bezel portion.
FIG. 6 is a flowchart illustrating an example procedure for determining a likelihood that a user does not intend to interact with a computing device in accordance with one or more embodiments.
FIG. 7 is a flowchart illustrating another example procedure for determining a likelihood that a user intends or does not intend to interact with a computing device based on a location of a centroid of the touch input in accordance with one or more embodiments.
FIG. 8 is a flowchart illustrating another example procedure for implementing the techniques described herein in a device in which the bezel portion includes display capabilities in accordance with one or more embodiments.
FIG. 9 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-8 to implement embodiments of the techniques described herein.
Conventional mobile computing devices often perform undesired actions because they are unable to distinguish between an intentional touch by a user and an accidental touch by the user while the user is holding the device. For example, touch sensors in a display of the computing device typically detect touch inputs and perform an action based on the input. Accordingly, accidental touches of the display by the user can result in the device performing undesired actions. Thus, conventional devices typically include wide bezels, which can hinder mobility and design of the device.
Techniques described herein enable touch sensors located both in a bezel portion of a display device and in a display portion of a display device to detect a touch input, such as from a user's finger, and use this to determine whether the user intends to interact with the computing device. For example, when a user is holding the device and the user's thumb accidentally touches the display, a determination may be made that the user's thumb likely touched the display by accident. In such an instance, the computing device can ignore the input rather than perform an undesired action. Because the device can differentiate between an accidental touch and a touch intended to interact with the display, bezel width can be reduced in favor of a larger display area.
Additionally, techniques may be employed to display a menu in a region of the bezel. For instance, a menu or status bar can be displayed in a region of the bezel along the top of the display device. Consequently, the menu does not interfere with or overlap other objects being displayed on the display device or otherwise lessen the amount of usable space on the display device.
In the following discussion, an example environment is first described that may employ the techniques herein. Example procedures are then described which may be performed in the example environment as well as other environments. Thus, performance of the example procedures is not limited to the example environment and the example environment is not limited to the performance of the example procedures. Finally, an example device is described. The example device can be utilized to implement one or more embodiments.
FIG. 1 is an illustration of an environment 100 in an example implementation that is operable to employ techniques described herein. The illustrated environment 100 includes a computing device 102 that has a display device 104. The display device 104 includes a display portion 106 and a bezel portion 108. The computing device 102 may be configured in a variety of ways.
For example, a computing device may be configured as a desktop computer, a mobile station, an entertainment appliance, a set-top box communicatively coupled to a display device, a wireless phone, a game console, and so forth. Thus, the computing device 102 may range from a full resource device with substantial memory and processor resources (e.g., personal computers, game consoles) to a low-resource device with limited memory and/or processing resources (e.g., traditional set-top boxes, hand-held game consoles). Additionally, although a single computing device 102 is shown, the computing device 102 may be representative of a plurality of different devices, such as multiple servers, a remote control and set-top box combination, an image capture device and a game console configured to capture gestures, and so on.
During interaction with a device, a user may provide a variety of touch inputs, including some touch inputs that may be unintentional. For example, as shown in FIG. 1, the user may hold the computing device 102 between a thumb and index finger of a left hand 110 while interacting with the device using fingers of a right hand 112. While the user's thumb is located substantially in the bezel portion 108, the user may occasionally, and accidentally, touch display portion 106 with the thumb. Touch sensors in the display portion 106 can detect this touch input. Touch sensors in the display portion 106 also detect touch inputs that result from the user touching the screen with right hand 112. In some instances, gesture module 114 causes operations to be performed that correspond to a detected touch input.
In a conventional device, an operation may be performed when touch sensors in the display portion detect touch inputs from the user's left hand 110 and/or the user's right hand 112. Consequently, conventional devices may perform operations responsive to touch inputs regardless of the user's intention to interact with the device. However, by including touch sensors in the bezel portion 108, touch inputs to the bezel portion 108 can be detected and used by gesture module 114 to determine whether or not a user intended to interact with the computing device 102. For example, though the touches by both the left hand 110 and the right hand 112 are detected by touch sensors in the display portion 106, touch sensors located in the bezel portion 108 enable gesture module 114 to determine that the touch input by the left hand 110 is likely indicative that the user is holding the computing device 102.
FIG. 2 illustrates an example implementation 200 of the computing device 102 of FIG. 1. As shown in FIG. 2, the display device 104 includes a display portion 106 and a bezel portion 108 and touch sensors are located in both display portion 106 and bezel portion 108.
The touch sensors can take a variety of forms. For example, the touch sensor can be implemented as a digitizer or sensing elements associated with the display device 104 that can sense the user's input on the display portion 106 or the bezel portion 108. Technologies such as capacitive field technologies, resistive technologies, pressure sensing technologies, and other input sensing technologies can also be utilized to detect the touch input.
Touch sensors in the display portion 106 and in the bezel portion 108 can detect touch inputs to display device 104. In some implementations, touch sensors may be located in the display portion or in the bezel portion. In other implementations, touch sensors may extend from the display portion into the bezel portion. Either arrangement of touch sensors can enable the computing device 102 in FIG. 1 to differentiate between an accidental touch by left hand 110 and a touch by right hand 112 intended to interact with the device.
Various factors can be used in determining a likelihood that the user does not intend to interact with the computing device. In some implementations, a determination that a user intends or does not intend to interact with the device is made according to a location of a centroid of the touch input. FIGS. 3 and 4 illustrate example implementations in which a centroid is used to determine a user's intention.
FIG. 3 illustrates a magnified view 300 of a display device 304 that includes touch sensors in a display portion 306 and a bezel portion 308. Assume that a user is holding the device in such a way that the thumb of the user's hand is mostly on the bezel portion 308, but is also partially on the display portion 306. For example, assume that the user is holding the device such as is illustrated by left hand 110 in FIG. 1. The area of this touch input is shown at 310.
The centroid (denoted “+”) of the area of the touch input 310 is also shown in FIG. 3. A variety of suitable methods can be used to calculate the centroid. For example, any algorithm operating to determine the geometric center of the area of the touch input can be used. The centroid calculation can be a simple calculation or a weighted calculation that depends on the position and shape of the touch input. Based on the centroid, the device determines a likelihood that the user intends or does not intend to interact with the device. In various implementations, when the location of the centroid is within the bezel portion 308, as shown in FIG. 3, the device determines that the user is touching mostly the bezel portion 308. Consequently, the device may determine that the user does not intend to interact with the device. Thus, the device can ignore the touch input.
Now, assume that a user is using a single finger to make a selection on a user interface being displayed. FIG. 4 illustrates a magnified view 400 of a display device 404 in which a user intends to interact with the device. As above, the display device 404 includes touch sensors in a display portion 406 and in a bezel portion 408. However, in FIG. 4, the area of the touch input 410 does not extend into the bezel portion 408. Instead, the area of the touch input 410 is entirely within display portion 406 and the centroid (denoted “+”) is within the display portion 406. Because the centroid of the area of the touch input 410 is located within the display portion 406, the device can determine that the user intended to interact with the device. The device may then perform an operation based on the touch input.
Although in FIGS. 1-4, the bezel portion was described as not including display capabilities, the techniques described may also be employed in implementations in which the bezel portion can act as an extension of the display portion. An example of such an implementation is described with reference to FIG. 5.
FIG. 5 illustrates an example computing device 502 having a display 504 that includes a display portion 506 and a bezel portion 508. The bezel portion 508 includes display capabilities. Though in some implementations the display capabilities of the bezel portion 508 are inactive, these capabilities can be made active in response to the detection of a touch input.
For example, touch sensors in the display portion 506 and the bezel portion 508 can detect touch inputs while the display capabilities of the bezel portion are inactive, such as described above in relation to FIGS. 1-4. However, when a touch input is detected within a region 510 of the bezel portion 508, rather than ignoring the touch input, the display capabilities of the region 510 can be made active. For example, a menu bar can be displayed in the region 510. Although reference is made to a menu bar, it should be noted that other types of user interfaces may be displayed in the region.
In some implementations, the computing device 502 can differentiate between a user intending to interact with the device and a user not intending to interact with the device based on an amount of time of the touch input. In such implementations, the duration of time of the touch input can be utilized to determine whether the touch input detected within the region 510 of the bezel portion 508 corresponds to a user intending to interact with the device or to a user not intending to interact with the device. For example, the computing device 502 can determine that a touch input to the region 510 that lasts longer than 0.25 seconds is likely indicative of a user holding the device whereas a touch input to the region 510 that lasts about 0.25 seconds or less is likely indicative of a user tapping within the region 510. It should be noted that although 0.25 seconds is used as an example threshold duration of the touch input, other durations are contemplated.
Once the display capabilities of the region 510 have been made active, a subsequent touch detected in the region 510 can be analyzed much the way a touch within the display portion is analyzed. In other words, if the centroid of the area of a touch input falls within the region 510, the device can determine that the user intended to interact with the region and can perform a corresponding operation. For example, if a centroid of the area of a touch input falls within the region 510 while a menu is displayed, the device can determine that the user intended to interact with the menu and can perform an associated function.
FIG. 6 is a flowchart illustrating an example procedure 600 for implementing the techniques described in accordance with one or more embodiments. Procedure 600 can be carried out by a gesture module, such as gesture module 114 of FIG. 1. The procedure can be implemented in software, firmware, hardware, or combinations thereof. Procedure 600 is shown as a set of blocks and is not limited to the order shown for performing the operations of the various blocks. Procedure 600 is an example procedure for implementing the techniques described herein; additional discussions of implementing the techniques described herein are included herein with reference to different figures.
Assume, as above, that a user holds computing device 102 with a left hand 110 and rests a thumb of the left hand on the display device 104. At least one touch sensor detects a touch input (block 602). The touch sensor can be associated with the display portion 106 or the bezel portion 108 of the display device 104 of FIG. 1, for example. As previously described, in some instances, such as when the user's thumb accidentally touches the display portion, a touch sensor located in the display portion 106 and a touch sensor located in the bezel portion 108 detect the touch input.
Based on the obtained touch information, the computing device 102 determines a likelihood that the user does not intend to interact with the computing device (block 604). For example, the gesture module 114 can determine that the user's thumb is located mostly in the bezel and that the user is likely holding the computing device. The gesture module 114 can make this determination based, for example, on the location of a centroid of the area of the touch input. FIG. 7 illustrates an example procedure for making this determination.
FIG. 7 is a flowchart illustrating another example procedure 700 for implementing the techniques described in accordance with one or more embodiments. As above, procedure 700 can be carried out by a gesture module, such as gesture module 114 of FIG. 1, and can be implemented in software, firmware, hardware, or combinations thereof. Procedure 700 is shown as a set of blocks and is not limited to the order shown for performing the operations of the various blocks.
In procedure 700, a touch sensor detects a touch input (block 702). The touch input can be, for example, a thumb of a user's left hand 110 when the user is holding computing device 102 or a finger of the user's right hand 112 when the user is interacting with a user interface.
The gesture module 114 calculates a centroid that corresponds to the touch input (block 704). Gesture module 114 can calculate the centroid based on a capacitor signal from a capacitive digitizer associated with the display device 104 or based on analogous signals received using other touch-sensing technologies. A variety of algorithms can be used to calculate the centroid.
The gesture module 114 then determines a location of the centroid relative to the display portion 106 (block 706). The gesture module 114 can map the centroid to its location on the display device 104. Such mapping to the display device can enable the gesture module 114 to determine if the centroid is located in an area corresponding to the display portion 106 or an area corresponding to the bezel portion 108. For example, gesture module 114 may determine that touch input from the thumb of the user's left hand 110 has a centroid located within the bezel portion 108 while the touch input from the finger of the user's right hand 112 has a centroid located within the display portion 106.
Next, the gesture module 114 performs a check to determine if the centroid is located in the display portion (block 708). If the centroid is located within an area corresponding to the display portion 106, the gesture module 114 determines that the user likely intends to interact with a user interface displayed by the display device 104 (block 710). If, however, the centroid is not located within an area corresponding to the display portion 106, gesture module 114 determines that the user likely does not intend to interact with the computing device 102 (block 712). For example, since the centroid of the touch input from the thumb of the user's left hand 110 is located within an area of the display device 104 that corresponds to the bezel portion 108, the gesture module 114 can determine that the touch input is likely indicative of the user holding the computing device. However, since the centroid of the touch input from the finger of the user's right hand 112 is located within an area of the display device 104 that corresponds to the display portion 106, the gesture module 114 can determine that the touch input is likely indicative that the user intends to interact with the user interface being displayed.
In various implementations, the bezel portion includes display capabilities, such as is shown in FIG. 5. FIG. 8 illustrates an example procedure 800 for implementing the techniques in a device in which the bezel portion includes such display capabilities. Procedure 800 can be implemented in software, firmware, hardware, or combinations thereof. Procedure 800 is shown as a set of blocks and is not limited to the order shown for performing the operations of the various blocks.
As in the previously described procedures, touch sensors detect a touch input (block 802). The touch sensors may be located in the display portion 106 or the bezel portion 108 of the display device 104. In various implementations, the display capabilities of the bezel portion 108 are inactive when the touch input is detected.
Next, the computing device 102 makes display capabilities in a region of the bezel portion 108 active based on the touch input (block 804). Display capabilities in region 510 in FIG. 5, for example, can be made active effective to cause a menu to be displayed in the region. This may be performed responsive to a determination that a centroid of the touch input is located within an area corresponding to the bezel portion 108. In some implementations, the display capabilities of the region can be made active responsive to a determination that a centroid of the touch input is located within an area corresponding to the display portion or another area of the bezel portion. Subsequent touch inputs detected in the region while the display capabilities are active can be determined to be indicative of a user's intention to interact with the menu that is displayed in the region.
Although the use of a centroid was described in the above discussion, intention or lack thereof may be indicated by a variety of other characteristics, such as a size of the touch input, a shape of the touch input, a location of the touch input, a velocity of the touch input, a distance the touch input travels, or a lifetime of the touch input.
Having described various techniques and procedures, consider the following description of an example system and device that may be used to implement one or more techniques or procedures.
FIG. 9 illustrates an example system generally at 900 that includes an example computing device 902 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 gesture module 114, which as before may be executed on the computing device 902, as part of the platform 922 “over the cloud 920,” and so on. The computing device 902 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 902 as illustrated includes a processing system 904, one or more computer-readable media 906, and one or more I/O interface 908 that are communicatively coupled, one to another. The computing device 902 also includes a gesture module 114 that functions as described above. Although not shown, the computing device 902 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 904 is representative of functionality to perform one or more operations using hardware. Accordingly, the processing system 904 is illustrated as including hardware elements 910 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 910 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 media 906 is illustrated as including memory/storage 912. The memory/storage 912 represents memory/storage capacity associated with one or more computer-readable media. The memory/storage component 912 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 912 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 906 may be configured in a variety of other ways as further described below.
Input/output interface(s) 908 are representative of functionality to allow a user to enter commands and information to computing device 902, 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 mouse), a microphone, a scanner, a display device including 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 902 may be configured in a variety of ways as further described below to support user interaction.
“Computer-readable storage media” may refer to media and/or devices that enable persistent 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 902, 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 910 and computer-readable media 906 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 910. The computing device 902 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 902 as software may be achieved at least partially in hardware, e.g., through use of computer-readable storage media and/or hardware elements 910 of the processing system 904. The instructions and/or functions may be executable/operable by one or more articles of manufacture (for example, one or more computing devices 902 and/or processing systems 904) to implement techniques, modules, and examples described herein.
As further illustrated in FIG. 9, the example system 900 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 900, 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 various implementations, the computing device 902 may assume a variety of different configurations, such as for computer 914, mobile 916, and television 918 uses. Each of these configurations includes devices that may have generally different constructs and capabilities, and thus the computing device 902 may be configured according to one or more of the different device classes. For instance, the computing device 902 may be implemented as the computer 914 class of a device that includes a personal computer, desktop computer, a multi-screen computer, laptop computer, netbook, and so on.
The computing device 902 may also be implemented as the mobile 916 class of device that includes mobile devices, such as a mobile phone, portable music player, portable gaming device, a tablet computer, a multi-screen computer, and so on. The computing device 902 may also be implemented as the television 918 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.
The techniques described herein may be supported by these various configurations of the computing device 902 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” 920 via a platform 922 as described below.
The cloud 920 includes and/or is representative of a platform 922 for resources 924. The platform 922 abstracts underlying functionality of hardware (e.g., servers) and software resources of the cloud 920. The resources 924 may include applications and/or data that can be utilized while computer processing is executed on servers that are remote from the computing device 902. Resources 924 can also include services provided over the Internet and/or through a subscriber network, such as a cellular or Wi-Fi network.
The platform 922 may abstract resources and functions to connect the computing device 902 with other computing devices. The platform 922 may also serve to abstract scaling of resources to provide a corresponding level of scale to encountered demand for the resources 924 that are implemented via the platform 922. Accordingly, in an interconnected device embodiment, implementation of functionality described herein may be distributed throughout the system 900. For example, the functionality may be implemented in part on the computing device 902 as well as via the platform 922 that abstracts the functionality of the cloud 920.
determining, based on a centroid of the touch input being detected within the display capable bezel portion, that a user intends the touch input to cause a display to occur in the display capable bezel portion and that the user does not intend to interact with the main display portion as a result of the touch input while the computing device is in an operational mode in which the computing device is configured to recognize and respond to a variety of touch inputs.
2. The method of claim 1, the determining further based on one or more characteristics of the touch input comprising a size of the touch input, a shape of the touch input, a location of the touch input, a velocity of the touch input, a distance the touch input travels, or a lifetime of the touch input.
determining that the location of the centroid is within the bezel portion of the display device.
4. The method of claim 3, wherein the determining that the user intends the touch input further comprises mapping the centroid of the touch input to its location on the bezel portion.
5. The method of claim 3, wherein the calculating the centroid of the touch input is weighted in part based on a shape of the touch input.
6. The method of claim 3, wherein the calculating the centroid is based in part on a signal from a capacitive digitizer.
7. The method of claim 1, wherein the one or more touch sensors are pressure sensitive touch sensors.
executing one or more software modules on a processor of the computing device to perform the determining that the user intends the touch input to interact with the computing device.
enabling one or more circuits of the computing device to perform the determining that the user intends the touch input to interact with the computing device.
10. The method of claim 1, the determining comprising determining that the touch input is not likely indicative of a user holding the computing device.
11. The method of claim 1, wherein at least a portion of the touch input is detected using one or more touch sensors located in the display portion.
12. The method of claim 1, the one or more touch sensors comprising one or more capacitive touch sensors.
one or more circuits configured to determine a likelihood that the touch input is indicative of a user's intention to cause the bezel portion of the display device to turn on and display a menu and that the user does not intend to interact with the display portion of the display device as a result of determining that a location of a centroid of the touch input is within an area corresponding to the bezel portion of the display device.
14. The device of claim 13, wherein the one or more circuits are configured to determine the likelihood by determining the location of the centroid of the touch input relative to the display portion or the bezel portion of the display device.
15. The device of claim 14, wherein the one or more circuits are configured to determine the likelihood by determining that the touch input is likely indicative of the user's intention to cause the menu to be displayed when the location of the centroid falls within the area corresponding to the bezel portion of the display device.
16. The device of claim 14, wherein the one or more circuits are configured to determine the likelihood by mapping the centroid of the touch input to its location relative to the display portion or the bezel portion of the display device.
17. The device of claim 14, wherein the one or more circuits are configured to determine the likelihood by calculating the centroid of the touch input weighted in part based on a shape of the touch input.
18. The device of claim 13, wherein the one or more circuits are configured to determine the likelihood by determining that the touch input is not likely indicative of a user holding the device.
19. The device of claim 13, wherein the one or more touch sensors included in the bezel portion extends from the display portion into the bezel portion.
20. The device of claim 19, wherein the one or more touch sensors extending from the display portion into the bezel portion comprise one or more capacitive touch sensors.
responsive to a location of a centroid of the detected touch input being within an area corresponding to the bezel portion, making the display capabilities of the region of the bezel portion active effective to cause the region of the bezel portion to act as an extension of the display portion of the display device.
22. The method of claim 21, wherein at least a portion of the touch input is within an area corresponding to the display portion.
determining a likelihood that the subsequent touch input is indicative of a user's intention to interact with the extension of the display portion of the display device.
24. The method of claim 23, the determining comprising determining that a location of a centroid of the subsequent touch input is within an area corresponding to the region.
25. The method of claim 21, wherein the making the display capabilities of the region is performed responsive to determining that the touch input is indicative of a user's intention to interact with the computing device.
26. The method of claim 21, wherein the making the display capabilities of the region is performed responsive to the touch input lasting about 0.25 seconds or less.
"3M Touch Systems, Inc. Announces Shipment of Dispersive Signal Technology Product", Datasheet, 3M Corporation, retrieved from <http://solutions.3m.com/wps/portal/3M/en-US/TouchSystems/TouchScreen/Informatio/Media/PressReleases/Archive/?PC-7-RJH9U52300FA602N9RSR991OI3000000-asset Id=1114287537178<, (Sep. 6, 2005), 3 pages.
"3M TouchWare TM Software for Windows User Guide", In White Paper of 3M Touch Systems-Retrieved at: <<http://multimedia.3m.com/mws/mediawebserver?6666660Zjcf6IVs6EVs66SS0LCOrrrrQ- >>, Aug. 9, 2013, 65 pages.
"AccuScribe Touchscreens", Datasheet, Elo TouchSystem, (Aug. 2005), 2 pages.
"Advisory Action", U.S. Appl. No. 12/709,376, Dec. 19, 2013, 2 pages.
"Apple Unibody MacBook Pro #MB991LL/A 2.53 GHz Intel Core 2 Duo", Retrieved from: <http://www.themacstore.com/parts/show/c-nmb3-mb991II a>on Nov. 10, 2009, (2009), 12 pages.
"Apple Unibody MacBook Pro #MB991LL/A 2.53 GHz Intel Core 2 Duo", Retrieved from: on Nov. 10, 2009, (2009), 12 pages.
"Corrected Notice of Allowance", U.S. Appl. No. 14/212,916, Mar. 3, 2016, 2 pages.
"Corrected Notice of Allowance", U.S. Appl. No. 14/212,916, May 26, 2016, 6 pages.
"Corrected Notice of Allowance", U.S. Appl. No. 14/212,916, May 9, 2016, 2 pages.
"Decision on Reexamination", CN Application No. 201110044285.5, Mar. 26, 2015, 14 Pages.
"Dell and Windows 7-The Wait Is Over", Retrieved from: <http://content.dell.com/us/en/corp/d/press-releases/2009-10-22-Dell-and-Windows-7.aspx> on Nov. 10, 2009, (Oct. 22, 2009),2 pages.
"Dell and Windows 7-The Wait Is Over", Retrieved from: on Nov. 10, 2009, (Oct. 22, 2009),2 pages.
"Ex Parte Mewherter, PTAB precedential decision", U.S. Appl. No. 10/685,192, May 8, 2013, 22 pages.
"Final Office Action", U.S. Appl. No. 11/324,157, (Jun. 24, 2009), 14 pages.
"Final Office Action", U.S. Appl. No. 11/324,157, (Oct. 15, 2010), 18 pages.
"Final Office Action", U.S. Appl. No. 12/472,699, (Feb. 15, 2012), 12 pages.
"Final Office Action", U.S. Appl. No. 12/472,699, (Jul. 29, 2013), 12 pages.
"Final Office Action", U.S. Appl. No. 12/695,842, Dec. 2, 2013, 17 pages.
"Final Office Action", U.S. Appl. No. 12/695,842, Feb. 12, 2015, 20 pages.
"Final Office Action", U.S. Appl. No. 12/695,937, (Jul. 26, 2012), 13 pages.
"Final Office Action", U.S. Appl. No. 12/695,937, Apr. 2, 2015, 14 pages.
"Final Office Action", U.S. Appl. No. 12/695,937, Nov. 10, 2014, 13 pages.
"Final Office Action", U.S. Appl. No. 12/695,976, (Nov. 21, 2012), 10 pages.
"Final Office Action", U.S. Appl. No. 12/695,976, Jul. 23, 2014, 12 pages.
"Final Office Action", U.S. Appl. No. 12/700,357, (Oct. 24, 2012), 13 pages.
"Final Office Action", U.S. Appl. No. 12/700,357, Nov. 20, 2014, 12 pages.
"Final Office Action", U.S. Appl. No. 12/700,460, (Aug. 28, 2012), 26 pages.
"Final Office Action", U.S. Appl. No. 12/700,510, (Oct. 10, 2012), 23 pages.
"Final Office Action", U.S. Appl. No. 12/700,510, Feb. 3, 2015, 28 pages.
"Final Office Action", U.S. Appl. No. 12/709,204, (Oct. 3, 2012), 24 pages.
"Final Office Action", U.S. Appl. No. 12/709,204, Apr. 11, 2014, 24 pages.
"Final Office Action", U.S. Appl. No. 12/709,204, Jan. 12, 2015, 29 pages.
"Final Office Action", U.S. Appl. No. 12/709,204, Sep. 12, 2013, 24 pages.
"Final Office Action", U.S. Appl. No. 12/709,245, (Jan. 6, 2012), 13 pages.
"Final Office Action", U.S. Appl. No. 12/709,245, (Mar. 15, 2013), 16 pages.
"Final Office Action", U.S. Appl. No. 12/709,245, Nov. 14, 2014, 6 pages.
"Final Office Action", U.S. Appl. No. 12/709,282, (Dec. 24, 2012), 11 pages.
"Final Office Action", U.S. Appl. No. 12/709,282, (Jul. 16, 2013), 11 pages.
"Final Office Action", U.S. Appl. No. 12/709,282, May 9, 2014, 17 pages.
"Final Office Action", U.S. Appl. No. 12/709,301, (Jan. 7, 2013), 14 pages.
"Final Office Action", U.S. Appl. No. 12/709,301, (Mar. 1, 2012), 11 pages.
"Final Office Action", U.S. Appl. No. 12/709,301, (Sep. 3, 2013), 12 pages.
"Final Office Action", U.S. Appl. No. 12/709,348, (Feb. 17, 2012), 13 pages.
"Final Office Action", U.S. Appl. No. 12/709,348, (Jan. 7, 2013), 15 pages.
"Final Office Action", U.S. Appl. No. 12/709,348, Sep. 12, 2013, 12 pages.
"Final Office Action", U.S. Appl. No. 12/709,376, (Mar. 30, 2012), 16 pages.
"Final Office Action", U.S. Appl. No. 12/709,376, (Nov. 8, 2012), 20 pages.
"Final Office Action", U.S. Appl. No. 12/709,376, Sep. 10, 2013, 12 pages.
"Final Office Action", U.S. Appl. No. 12/713,053, (Aug. 17, 2012), 10 pages.
"Final Office Action", U.S. Appl. No. 12/713,081, (May 9, 2012), 19 pages.
"Final Office Action", U.S. Appl. No. 12/713,096, (Feb. 15, 2013), 7 pages.
"Final Office Action", U.S. Appl. No. 12/713,110, (Jan. 17, 2013), 10 pages.
"Final Office Action", U.S. Appl. No. 12/713,113, (Jun. 4, 2012), 18 pages.
"Final Office Action", U.S. Appl. No. 12/713,113, Oct. 8, 2013, 21 pages.
"Final Office Action", U.S. Appl. No. 12/713,113, Oct. 8, 2014, 12 pages.
"Final Office Action", U.S. Appl. No. 12/713,118, (Oct. 26, 2012), 10 pages.
"Final Office Action", U.S. Appl. No. 12/713,127, (Jun. 6, 2012), 18 pages.
"Final Office Action", U.S. Appl. No. 12/713,127, Aug. 14, 2014, 15 pages.
"Final Office Action", U.S. Appl. No. 12/713,130, (Jun. 29, 2012), 8 pages.
"Final Office Action", U.S. Appl. No. 12/713,133, (Jul. 2, 2012), 8 pages.
"Final Office Action", U.S. Appl. No. 12/713,133, (May 20, 2013), 10 pages.
"Final Office Action", U.S. Appl. No. 13/352,193, Jan. 12, 2015, 22 pages.
"Final Office Action", U.S. Appl. No. 13/352,193, May 23, 2014, 23 pages.
"Final Office Action", U.S. Appl. No. 13/484,075, (May 21, 2013), 10 pages.
"Final Office Action", U.S. Appl. No. 13/484,075, Feb. 4, 2015, 12 pages.
"Final Office Action", U.S. Appl. No. 13/898,452, Jun. 9, 2014, 26 pages.
"Final Office Action", U.S. Appl. No. 13/898,452, Mar. 10, 2016, 25 pages.
"Final Office Action", U.S. Appl. No. 13/898,452, Mar. 27, 2015, 23 pages.
"Final Office Action", U.S. Appl. No. 14/099,798, Nov. 25, 2015, 19 pages.
"Foreign Notice of Allowance", CN Application No. 201110046510.9, Feb. 12, 2015, 6 Pages.
"Foreign Notice of Allowance", CN Application No. 201110046519.X, Aug. 2, 2016, 4 pages.
"Foreign Notice of Allowance", CN Application No. 201110050506.X, Nov. 2, 2014, 4 Pages.
"Foreign Notice of Allowance", JP Application No. 2012-555062, Mar. 3, 2015, 4 Pages.
"Foreign Office Action", Chinese Application 201110044285.5, (Apr. 24, 2013), 8 pages.
"Foreign Office Action", Chinese Application 201110044285.5, (Jun. 20, 2012), 12 pages.
"Foreign Office Action", Chinese Application No. 201110044285.5, (Jan. 4, 2013), 13 pages.
"Foreign Office Action", Chinese Application No. 201110046510.9, (May 31, 2013), 11 pages.
"Foreign Office Action", Chinese Application No. 201110046519.X, (Aug. 2, 2012), 13 pages.
"Foreign Office Action", Chinese Application No. 201110046519.X, (Aug. 6, 2013), 11 pages.
"Foreign Office Action", Chinese Application No. 201110046519.X, (Mar. 19, 2013), 12 pages.
"Foreign Office Action", Chinese Application No. 201110046529.3, (Aug. 16, 2012), 14 pages.
"Foreign Office Action", Chinese Application No. 201110046529.3, (Aug. 6, 2013), 10 pages.
"Foreign Office Action", Chinese Application No. 201110046529.3, (Feb. 4, 2013), 9 pages.
"Foreign Office Action", Chinese Application No. 201110050499.3, (Aug. 3, 2012), 8 pages.
"Foreign Office Action", Chinese Application No. 201110050499.3, (Nov. 27, 2012), 8 pages.
"Foreign Office Action", Chinese Application No. 201110050506.X, (Apr. 2, 2013), 11 pages.
"Foreign Office Action", Chinese Application No. 201110050508.9, (Aug. 3, 2012), 8 pages.
"Foreign Office Action", Chinese Application No. 201110050508.9, (Mar. 7, 2013), 8 pages.
"Foreign Office Action", Chinese Application No. 201110050852.8, (Mar. 26, 2013), 10 pages.
"Foreign Office Action", CN Application No. 201110044285.5, Dec. 22, 2014, 8 Pages.
"Foreign Office Action", CN Application No. 201110046510.9, Feb. 12, 2014, 9 Pages.
"Foreign Office Action", CN Application No. 201110046510.9, Jul. 25, 2014, 11 Pages.
"Foreign Office Action", CN Application No. 201110046519.X, Sep. 21, 2015, 16 Pages.
"Foreign Office Action", CN Application No. 201110050506.X, Feb. 26, 2014, 6 pages.
"Foreign Office Action", CN Application No. 201110050852.8, Nov. 1, 2013, 8 Pages.
"Foreign Office Action", CN Application No. 201180007100.1, May 15, 2015, 20 Pages.
"Foreign Office Action", CN Application No. 201180007100.1, Sep. 10, 2014, 22 pages.
"Foreign Office Action", CN Application No. 201180009579.2, Nov. 4, 2014, 16 pages.
"Foreign Office Action", CN Application No. 201180009579.2, Sep. 6, 2015, 19 pages.
"Foreign Office Action", CN Application No. 201180010692.2, Jun. 26, 2014, 13 pages.
"Foreign Office Action", CN Application No. 201180010692.2, Mar. 10, 20105, 9 Pages.
"Foreign Office Action", CN Application No. 201180010769.6, Sep. 3, 2014, 12 Pages.
"Foreign Office Action", CN Application No. 201180011020.3, Jan. 15, 2015, 9 Pages.
"Foreign Office Action", CN Application No. 201180011020.3, May 4, 2014, 12 Pages.
"Foreign Office Action", CN Application No. 201180011039.8, Feb. 17, 2015, 17 Pages.
"Foreign Office Action", CN Application No. 201180011039.8, Jun. 5, 2014, 16 Pages.
"Foreign Office Action", CN Application No. 201380059094.3, Dec. 1, 2016, 15 pages.
"Foreign Office Action", European Patent Application No. 11747907.1, (Jan. 28, 2013), 5 pages.
"Foreign Office Action", European Patent Application No. 11748026.9, (Jan. 16, 2013), 5 pages.
"Foreign Office Action", European Patent Application No. 11748027.7, (Jan. 18, 2013), 5 pages.
"Foreign Office Action", European Patent Application No. 11748028.5, (Jan. 28, 2013), 5 pages.
"Foreign Office Action", European Patent Application No. 11748029.3, (Jan. 16, 2013), 5 pages.
"Foreign Office Action", JP Application No. 2012-554008, Jun. 25, 2015, 13 pages.
"Foreign Office Action", JP Application No. 2012-554008, Nov. 25, 2014, 7 pages.
"In touch with new opportunities-Dispersive Signal Technology", DataSheet, NXT, (2005), 1 page.
"International Preliminary Report on Patentability", Application No. PCT/US2014/067804, Feb. 22, 2016, 9 pages.
"International Search Report and Written Opinion", Application No. PCT/US2014/067804, Jul. 24, 2015, 19 Pages.
"International Search Report and Written Opinion", Application No. PCT/US2015/019811, Jul. 8, 2015, 11 pages.
"iQuery & Css Example-Dropdown Menu", DesignReviver, Retrieved from: on Nov. 22, 2011,(Oct. 7, 2008), 30 pages.
"iQuery & Css Example-Dropdown Menu", DesignReviver, Retrieved from:<http://designreviver.com/tutorials/jquery-css-example-dropdown-menu/> on Nov. 22, 2011,(Oct. 7, 2008), 30 pages.
"New MS Courier Leak Details Multi-Touch Interface", Retrieved from: <http://www.electronista.com/articles/09/11/04/courier.gestures.ui.explained/> on Nov. 10, 2009 (Nov. 4, 2009), 9 pages.
"New MS Courier Leak Details Multi-Touch Interface", Retrieved from: on Nov. 10, 2009 (Nov. 4, 2009), 9 pages.
"Non-Final Office Action", U.S. Appl. No. 11/324,157, (Apr. 28, 2010), 16 pages.
"Non-Final Office Action", U.S. Appl. No. 11/324,157, (Dec. 11, 2008), 12 pages.
"Non-Final Office Action", U.S. Appl. No. 11/324,157, (Sep. 28, 2009), 17 pages.
"Non-Final Office Action", U.S. Appl. No. 12/472,699, (Mar. 28, 2013), 10 pages.
"Non-Final Office Action", U.S. Appl. No. 12/472,699, (Sep. 12, 2011), 12 pages.
"Non-Final Office Action", U.S. Appl. No. 12/472,699, Oct. 23, 2013, 14 pages.
"Non-Final Office Action", U.S. Appl. No. 12/695,842, (May 22, 2013), 16 pages.
"Non-Final Office Action", U.S. Appl. No. 12/695,842, (Oct. 3, 2012), 16 pages.
"Non-Final Office Action", U.S. Appl. No. 12/695,842, Aug. 18, 2014, 21 pages.
"Non-Final Office Action", U.S. Appl. No. 12/695,937, (Apr. 25, 2012), 14 pages.
"Non-Final Office Action", U.S. Appl. No. 12/695,937, May 7, 2014, 11 pages.
"Non-Final Office Action", U.S. Appl. No. 12/695,976, (Sep. 11, 2012), 8 pages.
"Non-Final Office Action", U.S. Appl. No. 12/695,976, Mar. 25, 2015, 10 pages.
"Non-Final Office Action", U.S. Appl. No. 12/700,357, (Jul. 2, 2012), 10 pages.
"Non-Final Office Action", U.S. Appl. No. 12/700,357, Apr. 2, 2015, 12 pages.
"Non-Final Office Action", U.S. Appl. No. 12/700,357, Jun. 26, 2014, 11 pages.
"Non-Final Office Action", U.S. Appl. No. 12/700,460, (Jan. 13, 2012), 21 pages.
"Non-Final Office Action", U.S. Appl. No. 12/700,510, (Feb. 7, 2012), 20 pages.
"Non-Final Office Action", U.S. Appl. No. 12/700,510, Jun. 12, 2014, 26 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,204, (Jun. 6, 2013), 27 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,204, (May 10, 2012), 20 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,204, Aug. 13, 2014, 25 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,204, Nov. 20, 2013, 31 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,245, (Mar. 21, 2012), 14 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,245, (May 30, 2013), 15 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,245, (Nov. 30, 2011), 11 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,245, Mar. 20, 2014, 16 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,282, (Apr. 12, 2012), 9 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,282, (Feb. 28, 2013), 11 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,282, Jan. 29, 2015, 22 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,282, Oct. 10, 2013, 12 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,301, (May 14, 2013), 14 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,301, (Nov. 28, 2011), 9 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,301, (Sep. 13, 2012), 13 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,301, Jan. 16, 2015, 5 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,301, Jul. 14, 2015, 11 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,301, May 23, 2014, 12 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,301, Nov. 19, 2015, 8 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,301, Oct. 24, 2013, 11 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,348, (Apr. 25, 2013), 15 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,348, (Aug. 2, 2012), 14 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,348, (Dec. 7, 2011), 12 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,348, Dec. 20, 2013, 9 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,376, (Aug. 17, 2012), 17 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,376, (Jan. 23, 2012), 14 pages.
"Non-Final Office Action", U.S. Appl. No. 12/709,376, (May 23, 2013), 17 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,053, (Feb. 3, 2012), 8 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,053, (Nov. 23, 2012), 13 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,081, (Dec. 23, 2011), 18 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,081, (Nov. 29, 2012), 9 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,096, (Jun. 26, 2013), 8 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,096, (Jun. 6, 2012), 9 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,096, Jan. 30, 2014, 23 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,110, (Jun. 21, 2012), 21 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,110, (May 3, 2013), 10 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,113, (Apr. 23, 2013), 18 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,113, (Dec. 22, 2011), 20 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,113, Feb. 12, 2015, 24 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,113, Jun. 4, 2014, 11 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,118, (Jun. 8, 2012), 7 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,118, Jan. 29, 2015, 11 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,127, (Dec. 27, 2011), 22 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,127, Jan. 31, 2014, 21 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,127, Mar. 26, 2015, 18 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,130, (Jan. 16, 2013), 5 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,130, (Jan. 23, 2012), 7 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,133, (Jan. 14, 2013), 8 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,133, (Jan. 31, 2012), 7 pages.
"Non-Final Office Action", U.S. Appl. No. 12/713,133, Dec. 10, 2013, 8 pages.
"Non-Final Office Action", U.S. Appl. No. 13/352,193, Apr. 9, 2015, 21 pages.
"Non-Final Office Action", U.S. Appl. No. 13/352,193, Aug. 20, 2014, 19 pages.
"Non-Final Office Action", U.S. Appl. No. 13/352,193, Jan. 31, 2014, 22 pages.
"Non-Final Office Action", U.S. Appl. No. 13/484,075, (Jan. 15, 2013), 9 pages.
"Non-Final Office Action", U.S. Appl. No. 13/484,075, Sep. 5, 2014, 11 pages.
"Non-Final Office Action", U.S. Appl. No. 13/657,662, Apr. 5, 2013, 10 pages.
"Non-Final Office Action", U.S. Appl. No. 13/898,452, Feb. 24, 2014, 24 pages.
"Non-Final Office Action", U.S. Appl. No. 13/898,452, Jul. 28, 2016, 26 pages.
"Non-Final Office Action", U.S. Appl. No. 13/898,452, Sep. 14, 2015, 23 pages.
"Non-Final Office Action", U.S. Appl. No. 13/898,452, Sep. 26, 2014, 21 pages.
"Non-Final Office Action", U.S. Appl. No. 14/099,798, Jun. 9, 2015, 15 pages.
"Non-Final Office Action", U.S. Appl. No. 14/099,798, Mar. 31, 2016, 18 pages.
"Non-Final Office Action", U.S. Appl. No. 14/145,204, Feb. 24, 2015, 9 Pages.
"Non-Final Office Action", U.S. Appl. No. 14/145,204, Feb. 5, 2014, 5 pages.
"Non-Final Office Action", U.S. Appl. No. 14/212,916, Aug. 7, 2015, 10 pages.
"Non-Final Office Action", U.S. Appl. No. 14/979,910, Feb. 22, 2016, 4 pages.
"Notice of Allowance", U.S. Appl. No. 11/324,157, (May 9, 2011), 8 pages.
"Notice of Allowance", U.S. Appl. No. 12/472,699, May 2, 2014, 6 pages.
"Notice of Allowance", U.S. Appl. No. 12/695,064, (Mar. 28, 2012), 12 pages.
"Notice of Allowance", U.S. Appl. No. 12/695,959, (Apr. 17, 2012), 13 pages.
"Notice of Allowance", U.S. Appl. No. 12/709,245, Apr. 28, 2015, 4 pages.
"Notice of Allowance", U.S. Appl. No. 12/709,245, Jan. 30, 2015, 4 pages.
"Notice of Allowance", U.S. Appl. No. 12/709,301, Feb. 24, 2016, 7 pages.
"Notice of Allowance", U.S. Appl. No. 12/709,301, Sep. 8, 2015, 6 pages.
"Notice of Allowance", U.S. Appl. No. 12/709,376, Mar. 17, 2014, 6 pages.
"Notice of Allowance", U.S. Appl. No. 12/713,053, (Jun. 7, 2013), 7 pages.
"Notice of Allowance", U.S. Appl. No. 12/713,096, Aug. 29, 2014, 14 pages.
"Notice of Allowance", U.S. Appl. No. 12/713,096, Jan. 9, 2015, 14 pages.
"Notice of Allowance", U.S. Appl. No. 12/713,110, Dec. 4, 2013, 13 pages.
"Notice of Allowance", U.S. Appl. No. 12/713,118, Mar. 5, 2015, 4 pages.
"Notice of Allowance", U.S. Appl. No. 12/713,130, (Feb. 19, 2013), 5 pages.
"Notice of Allowance", U.S. Appl. No. 12/713,133, Jan. 17, 2014, 4 pages.
"Notice of Allowance", U.S. Appl. No. 13/230,700, Jun. 21, 2012, 8 pages.
"Notice of Allowance", U.S. Appl. No. 13/230,700, May 15, 2012, 8 pages.
"Notice of Allowance", U.S. Appl. No. 13/657,662, Oct. 11, 2013, 7 pages.
"Notice of Allowance", U.S. Appl. No. 14/145,204, Sep. 25, 2015, 5 pages.
"Notice of Allowance", U.S. Appl. No. 14/212,916, Dec. 24, 2015, 8 pages.
"Notice of Allowance", U.S. Appl. No. 14/979,910, Aug. 31, 2016, 7 pages.
"Notice of Allowance", U.S. Appl. No. 14/979,910, Nov. 1, 2016, 7 pages.
"Notice on Reexamination", CN Application No. 201110044285.5, Jul. 23, 2014, 8 Pages.
"PCT Search Report and Written Opinion", Application No. PCT/US/2011025972, (Sep. 30, 2011), 14 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/020410, (Sep. 27, 2011), 9 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/020412, (Aug. 31, 2011), 9 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/020417, (Oct. 20, 2011), 8 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/025131, (Oct. 31, 2011), 10 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/025132, (Oct. 26, 2011), 10 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/025575, (Sep. 30, 2011), 14 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/025971, (Oct. 31, 2011), 15 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/025973, (Oct. 27, 2011), 13 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2011/025974, (Oct. 26, 2011), 8 pages.
"PCT Search Report and Written Opinion", Application No. PCT/US2013/020413, (Apr. 8, 2013), 10 pages.
"Second Written Opinion", Application No. PCT/US2014/067804, Nov. 24, 2015, 8 Pages.
"Supplemental Notice of Allowance", U.S. Appl. No. 12/713,096, Nov. 4, 2014, 2 pages.
"Supplemental Notice of Allowance", U.S. Appl. No. 12/713,118, Mar. 19, 2015, 2 pages.
"Supplemental Notice of Allowance", U.S. Appl. No. 12/713,133, Feb. 3, 2014, 2 pages.
"Supplementary European Search Report", European Patent Application No. 11747907.1, (Nov. 7, 2012), 3 pages.
"Supplementary European Search Report", European Patent Application Number 11748027.7, (Nov. 29, 2012), 3 pages.
"Supplementary European Search Report", European Patent Application Number 11748028.5, (Nov. 7, 2012), 3 pages.
"Touch Screen is available in .36-50.8 mm thickness", ThomasNet Industrial News Room (Jul. 29, 2003), 2 pages.
"TouchSystems-Innovation Touch Screen Solution", Retrieved at <<http://www.touchsystems.com/article.aspx?id=16>>, Aug. 14, 2012, p. 1.
"UI Guidelines", Retrieved from: http://na.blackberry.com/eng/deliverables/6622/BlackBerry-Smarphones-US.pdf., 76 Pages.
Appleinsider, "Special Report: Apple's Touch-Sensitive iPod Ambitions Disclosed in Filing", Retrieved from: <http://www.appleinsider.com/articles/06/10/26/special-report-apples-touch-sensitive-ipod-ambitions-disclosed-in-filing.html> on Nov. 11, 2009, (Oct. 26, 2006), 10 pages.
Boudreaux, Toby "Touch Patterns: Chapter 6-Programming the iPhone User Experience", retrieved from <http://oreilly.com/iphone/excerpts/iphone-programming-user/touch-patterns.html> on Oct. 25, 2011,12 pages.
Brandl, Peter et al., "Combining and Measuring the Benefits of Bimanual Pen and Direct-Touch Interaction on Horizontal Interfaces", Retrieved from: <http://www.merl.com/papers/docs/TR2008-054.pdf> on Nov. 5, 2009, Mitsubishi Electric Research Laboratories,(May 2008),10 pages.
Daniels, Martyn "Brave New World", Retrieved from: <http://bookseller-association.blogspot.com/2009-03 -01 -archive.html> on Nov. 10, 2009, (Mar. 2009), 54 pages.
Elliott, Technology "First Dell, Then HP: What's Next for N-trig's Multitouch Screen Technology", Retrieved from: <http://news.cnet.com/8301-17938-105-10107886-1.html> on Nov. 11, 2009, (Nov. 25, 2008), 5 pages.
Emigh, Jacqueline "Lenovo Launches Windows 7 ThinkPads with Multitouch and Outdoor Screens", Retrieved from: <http://www.betanews.com/article/Lenovo-launches-Windows-7-ThinkPads-with-multitouch-and-outdoor-screens/1253017166> on Nov. 11, 2009, (Sep. 15, 2009), 3 pages.
Findlater, et al., "Personalized Input: Improving Ten-Finger Touchscreen Typing through Automatic Adaptation", Proceedings of the SIGCHI Conference on Human Factors in Computing Systems, Available at <http://terpconnect.umd.edu/˜leahkf/pubs/CHI2012-findlater-PersonalizedTyping.pdf>,(May 5, 2012), 10 pages.
Fonseca, "New Apple Patent Hints at Touch Enabled Bezels for Future Devices", Retrieved from: <http://vr-zone.com/articles/new-apple-patent-hints-at-touch-enabled-bezels-for-future-devices/42928.html?utm-source=rss&utm-medium=rss&utm-campaign=new-apple-patent-hints-at-touch-enabled-bezels-for-future-devices> Jan. 31, 2014, Jul. 3, 2013, 6 Pages.
Goel, et al., "GripSense: Using Built-In Sensors to Detect Hand Posture and Pressure on Commodity Mobile Phones", Proceedings of the 25th Annual ACM Symposium on User Interface Software and Technology, (Oct. 7, 2012), pp. 545-554.
Gross, Mark D., "Stretch-A-Sketch: A Dynamic Diagrammer", IEEE Symposium on Visual Languages, Available at <http://depts.washington.edu/dmachine/PAPER/VL94/vl.html>, (Oct. 1994), 11 pages.
Hinckley, Ken et al., "Codex: A Dual Screen Tablet Computer", Conference on Human Factors in Computing Systems, (Apr. 9, 2009), 10 pages.
Hinckley, Ken et al., "Sensor Synaesthesia: Touch in Motion, and Motion in Touch", CHI 2011, May 7-12, 2011, available at <http://research.microsoft.com/en-us/um/people/kenh/papers/touch-motion-camera-ready-final.pdf>,(May 7, 2011), 10 pages.
Hinckley, Ken et al., "Stitching: Pen Gestures that Span Multiple Displays", CHI 2004, Available at <http://www.cs.cornell.edu/˜francois/Papers/2004-Hinckley-AVI04-Stitching.>, (2004), pp. 1-8.
Hirche, et al., "Adaptive Interface for Text Input on Large-Scale Interactive Surfaces", 3rd IEEE International Workshop on Horizontal Interactive Human Computer System, (Oct. 1, 2008), pp. 153-156.
Hotelling, "Multi-functional hand-held device", U.S. Appl. No. 60/658,777, filed Mar. 4, 2015, 117 pages.
Hotelling, "Multi-functional hand-held device", U.S. Appl. No. 60/663,345, filed Mar. 16, 2005, 76 pages.
Kim, et al., "Hand Grip Pattern Recognition for Mobile User Interfaces", Interaction Lab / Samsung Advanced Institute of Technology, Available at ,2006, pp. 1789-1794.
Kim, et al., "Hand Grip Pattern Recognition for Mobile User Interfaces", Interaction Lab / Samsung Advanced Institute of Technology, Available at <http://www.alice.org/stage3/pubs/uistsensing.pdf>,2006, pp. 1789-1794.
Krazit, Tom "Has Apple Found the Magic Touch?", Retrieved from: <http://news.cnet.com/8301-13579-3-9879471-37.html> on Nov. 10, 2009, (Feb. 26, 2008), 2 pages.
Lee, Tyler "The TypeWay iPad app is an adaptive on-screen keyboard", Retrieved from <http://www.ubergizmo.com/2012/02/the-typeway-ipad-app-is-an-adaptive-on-screen-keyboard/> on Mar. 7, 2013, (Feb. 1, 2012), 2 pages.
Maxwell, Kenneth G., "Writing drivers for common touch-screen interface hardware", Industrial Control Design Line, (Jun. 15, 2005), 9 pages.
Minsky, Margaret R., "Manipulating SImulated Objects with Real-world Gestures using a Force and Position Sensitive Screen", Computer Graphics, vol. 18, No. 3, Available at <http://delivery.acm.org/10.1145/810000/808598/p195-minsky.pdf?key1=808598&key2=2244955521&coll=GUIDE&dl=GUIDE&CFID=57828830&CFTOKEN=43421964>,(Jul. 1984), pp. 195-203.
Moore, Charles "TypeWay Adaptive Keyboard for iPad Review", Retrieved from <http://www.technologytell.com/apple/89378/typeway-adaptive-keyboard-for-ipad-review/> on Mar. 6, 2013, Feb. 5, 2012, 10 pages.
Nick T., "Smartphone displays need a bezel. Here's why", Retrieved at <<http://www.phonearena.com/news/Smartphone-displays-need-a-bezel.-Heres-why-id27670>>, Mar. 12, 2012, pp. 4.
Nordgren, Peder "Development of a Touch Screen Interface for Scania Interactor", Master's Thesis in Computing Science, UMEA University, Available at <http://www.cs.umu.se/education/examina/Rapporter/PederNordgren.pdf>, (Apr. 10, 2007), pp. 1-59.
Olwal, Alex et al., "Rubbing and Tapping for Precise and Rapid Selection on Touch-Screen Displays", Conference on Human Factors in Computing SystemsAvailable at <http://www.csc.kth.se/˜alx/projects/research/rubbing/olwal-rubbing-tapping-chi-2008.pdf>,(Apr. 2008), 10 pages.
Panzarino, Matthew., "Apple's iPad Mini Should have a Widescreen Display", Retrieved at <<http://thenextweb.com/apple/2012/08/15/what-ipad-mini-169-instead-431>>, Aug. 15, 2012, pp. 6.
Pierce, Jeffrey S., et al., "Toolspaces and Glances: Storing, Accessing, and Retrieving Objects in 3D Desktop Applications", 1999 Symposium on Interactive 3D Graphics, Available at <http://delivery.acm.org/10.1145/310000/3000545/p163-pierce.pdf?key1=300545&key2=8792497521&coll=GUIDE&dl=GUIDE&CFID=61004073&CFTOKEN=28819248>,(Apr. 1999), pp. 163-168.
Roth, et al., "Bezel Swipe: Conflict-Free Scrolling and Multiple Selection on Mobile Touch Screen Devices", Retrieved at <<http://www.volkerroth.com/download/Roth2009a.pdf>>, In 27th International Conference on Human Factors in Computing Systems, Apr. 4, 2009, pp. 4.
Roth, Volker et al., "Bezel Swipe: Conflict-Free Scrolling and Multiple Selection on Mobile Touch Screen Devices", CHI 2009, Available at <http://www.volkerroth.com/download/Roth2009a.pdf>,(Apr. 2009), 4 pages.
Roudaut, et al., "Leaf Menus: Linear Menus with Stroke Shortcuts for Small Handheld Devices", Proceedings of the 12th IFIP TC 13 International Conference on Human-Computer Interaction: Part I, Aug. 2009, 4 pages.
Saini, Kalpana et al., "Designing of a Virtual System with Fingerprint Security by considering many Security Threats", International Journal of Computer Application, vol. 3-No. 2, available at <http://www.ijcaonline.org/volume3/number2/pxc387995.pdf>,(Jun. 2010), pp. 25-31.
Sajid, Uzair "Microsoft Patent a Futuristic Virtual Multitouch Keyboard", Retrieved from <http://thetechnopath.com/microsoft-patent-futuristic-virtual-multitouch-keyboard/857/> on Mar. 6, 2013, (Sep. 27, 2009), 8 pages.
Sax, et al., "LiquidKeyboard: An Ergonomic, Adaptive QWERTY Keyboard for Touchscreens", Proceedings of Fifth International COnference on Digital Society, (Feb. 23, 2011), pp. 117-122.
Serrano, et al., "Bezel-Tap Gestures: Quick Activation of Commands from Sleep Mode on Tablets", n Proceedings of the SIGCHI Conference on Human Factors in IComputing Systems, (Apr. 27, 2013), 10 pages.
Vallerio, Keith S., et al., "Energy-Efficient Graphical User Interface Design", Retrieved from: <http://www.cc.gatech.edu/classes/AY2007/cs7470-fall/zhong-energy-efficient-user-interface.pdf>, (Jun. 10, 2004), pp. 1-13.
Vigil, Jose M., "Methods for Controlling a Floating Cursor on a Multi-touch Mobile Phone or Tablet in Conjunction with Selection Gestures and Content Gestures", U.S. Appl. No. 61/304,972,(Feb. 16, 2010), 54 pages.
Yee, Ka-Ping "Two-Handed Interaction on a Tablet Display", Retrieved from: <http://zesty.ca/tht/yee-tht-chi2004-short.pdf>, Conference on Human Factors in Computing Systems,(Apr. 2004), 4 pages.

References: in casu
 Application No. 201110044285
 Application No. 201110046510
 Application No. 201110046519
 Application No. 201110050506
 Application No. 2012
 Application No. 201110044285
 Application No. 201110046510
 Application No. 201110046519
 Application No. 201110046519
 Application No. 201110046519
 Application No. 201110046529
 Application No. 201110046529
 Application No. 201110046529
 Application No. 201110050499
 Application No. 201110050499
 Application No. 201110050506
 Application No. 201110050508
 Application No. 201110050508
 Application No. 201110050852
 Application No. 201110044285
 Application No. 201110046510
 Application No. 201110046510
 Application No. 201110046519
 Application No. 201110050506
 Application No. 201110050852
 Application No. 201180007100
 Application No. 201180007100
 Application No. 201180009579
 Application No. 201180009579
 Application No. 201180010692
 Application No. 201180010692
 Application No. 201180010769
 Application No. 201180011020
 Application No. 201180011020
 Application No. 201180011039
 Application No. 201180011039
 Application No. 201380059094
 Application No. 11747907
 Application No. 11748026
 Application No. 11748027
 Application No. 11748028
 Application No. 11748029
 Application No. 2012
 Application No. 2012
 Application No. 201110044285
 Application No. 11747907