This relates generally to touch sensitive devices, and in particular, to a touch scan mode during device charging.
Many types of input devices are presently available for performing operations in a computing system, such as buttons or keys, mice, trackballs, touch sensor panels, joysticks, touch screens and the like. Touch screens, in particular, are becoming increasingly popular because of their ease and versatility of operation as well as their declining price. Touch screens can include a touch sensor panel, which can be a clear panel with a touch-sensitive surface. The touch sensor panel can be positioned in front of a display screen so that the touch-sensitive surface covers the viewable area of the display screen. Touch screens can allow a user to make selections and move a cursor by simply touching the display screen via a finger or stylus. In general, the touch screen can recognize a touch and position of the touch on the display screen, the computing system can interpret the touch, and thereafter, perform an action based on the touch event.
One limitation of touch sensor panel technologies is that noise can adversely affect the performance of a touch sensor panel device. Noise from sources such as a power adapter or an inductive charger can influence the results of a touch sensor panel device. For example, the touch sensor panel device can be coupled to a power adapter or inductive charger to charge a battery on the device. The charger can introduce noise while charging, which can prevent a touch sensor panel from distinguishing between a touch event (e.g., a user's contact of a touch sensor panel) and noise influencing the sensors of the touch sensor panel.
This relates to time multiplexed touch detection and power charging of touch sensitive devices. A power adapter or an inductive charger can charge a battery of a device, but can also introduce or add noise during the process of charging the battery. Touch pixels of a touch sensitive device can be stimulated by noise from the charger, and can adversely affect one or more components, such as the touch sensor panel. To prevent adverse effects to the touch sensor panel, while the device is charging, the touch controller can time multiplex touch scan periods and inductive charging periods and can discard touch scans or touch images affected by the noise.
In the following description of examples, reference is made to the accompanying drawings which form a part hereof, and in which it is shown by way of illustration specific examples that can be practiced. It is to be understood that other examples can be used and structural changes can be made without departing from the scope of the disclosed examples.
Various techniques and process flow steps will be described in detail with reference to examples as illustrated in the accompanying drawings. In the following description, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects and/or features described or referenced herein. It will be apparent, however, to one skilled in the art, that one or more aspects and/or features described or referenced herein may be practiced without some or all of these specific details. In other instances, well-known process steps and/or structures have not been described in detail in order to not obscure some of the aspects and/or features described or referenced herein.
Further, although process steps or method steps can be described in a sequential order, such processes and methods can be configured to work in any suitable order. In other words, any sequence or order of steps that can be described in the disclosure does not, in and of itself, indicate a requirement that the steps be performed in that order. Further, some steps can be performed simultaneously despite being described or implied as occurring non-simultaneously (e.g., because one step is described after the other step). Moreover, the illustration of a process by its depiction in a drawing does not imply that the illustrated process is exclusive of other variations and modification thereto, does not imply that the illustrated process or any of its steps are necessary to one or more of the examples, and does not imply that the illustrated process is preferred.
Touch-sensitive screens (“touch screens” or “touchscreens”) can be used in many electronic devices to display graphics and text and to provide a user interface through which a user can interact with the devices. A touch screen can detect and respond to contact on the touch screen. A device can display one or more soft keys, menus, and other user-interface objects on the touch screen. A user can interact with the device by contacting the touch screen at locations corresponding to the user-interface object with which the user wishes to interact.
This disclosure relates to time multiplexed touch detection and power charging of touch sensitive devices. A power adapter or inductive charger can charge a battery of a device, but can also introduce or add noise during the process of charging the battery. Inductive charging can introduce a significant amount of noise due to the extremely strong carrier signal during the charging time. Touch pixels of a touch sensitive device can be stimulated by noise from the power adapter or inductive charger, and can adversely affect one or more components, such as the touch sensor panel. To prevent adverse effects to the touch sensor panel, while the device is charging, the touch controller can time multiplex touch scan periods and inductive charging periods and can discard touch scans or touch images affected by the noise.
Charge pump 215 can be used to generate the supply voltage for the transmit section. Stimulation signals 216 (Vstim) can have amplitudes higher than the maximum voltage the ASIC process can tolerate by cascading transistors. Therefore, using charge pump 215, the stimulus voltage can be higher (e.g., 6V) than the voltage level a single transistor can handle (e.g., 3.6 V). Although
Touch sensor panel 224 can include a capacitive sensing medium having a plurality of drive lines and a plurality of sense lines. The drive and sense lines can be formed from a transparent conductive medium such as Indium Tin Oxide (ITO) or Antimony Tin Oxide (ATO), although other transparent and non-transparent materials such as copper can also be used. In some examples, the drive and sense lines can be perpendicular to each other, although in other examples other non-Cartesian orientations are possible. For example, in a polar coordinate system, the sensing lines can be concentric circles and the driving lines can be radially extending lines (or vice versa). It should be understood, therefore, that the terms “drive lines” and “sense lines” as used herein are intended to encompass not only orthogonal grids, but the intersecting traces or other geometric configurations having first and second dimensions (e.g., the concentric and radial lines of a polar-coordinate arrangement). The drive and sense lines can be formed on, for example, a single side of a substantially transparent substrate.
At the “intersections” of the traces, where the drive and sense lines can pass adjacent to and above and below (cross) each other (but without making direct electrical contact with each other), the drive and sense lines can essentially form two electrodes (although more than two traces could intersect as well). Each intersection of drive and sense lines can represent a capacitive sensing node and can be viewed as touch pixel or node 226, which can be particularly useful when touch sensor panel 224 is viewed as capturing an “image” of touch. (In other words, after touch controller 206 has determined whether a touch event has been detected at each touch sensor in the touch sensor panel, the pattern of touch sensors in the multi-touch sensor panel at which a touch event occurred can be viewed as an “image” of touch (e.g., a pattern of fingers touching the panel.) The capacitance between drive and sense electrodes can appear as stray capacitance when the given row is held at direct current (DC) voltage levels and as a mutual capacitance Csig when the given row is stimulated with an alternating current (AC) signal. The presence of a finger or other object near or on the touch sensor panel can be detected by measuring changes to a signal charge Qsig present at the pixels being touched, which is a function of Csig.
Computing system 200 can also include host processor 228 for receiving outputs from processor subsystem 202 and performing actions based on the outputs that can include, but are not limited to, moving an object such as a cursor or pointer, scrolling or panning, adjusting control settings, opening a file or document, viewing a menu, making a selection, executing instructions, operating a peripheral device connected to the host device, answering a telephone call, changing the volume or audio settings, storing information related to telephone communications such as addresses, frequently dialed numbers, received calls, missed calls, logging onto a computer or a computer network, permitting authorized individuals access to restricted areas of the computer or computer network, loading a user profile associated with a user's preferred arrangement of the computer desktop, permitting access to web content, launching a particular program, encrypting or decoding a message, and/or the like.
Host processor 228 can perform additional functions that may not be related to panel processing, and can be coupled to program storage 232 and display 230, such as an LCD display, for providing a user interface to a user of the device. In some examples, host processor 228 can be a separate component from touch controller 206, as shown. In some examples, host processor 228 can be included as part of touch controller 206. In some examples, the functions of host processor 228 can be performed by processor subsystem 202 and/or distributed among other components of touch controller 206. Display 230 together with touch sensor panel 224, when located partially or entirely under the touch sensor panel 224, can form touch screen 218.
Note that one or more of the functions described above can be performed, for example, by firmware stored in memory (e.g., one of the peripherals) and executed by processor subsystem 202, or stored in program storage 232 and executed by host processor 228. The firmware can also be stored and/or transported within any non-transitory computer-readable storage medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “non-transitory computer-readable storage medium” can be any medium (excluding a signal) that can contain or store the program for use by or in connection with the instruction execution system, apparatus, or device. The non-transitory computer readable storage medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, a portable computer diskette (magnetic), a random access memory (RAM) (magnetic), a read-only memory (ROM) (magnetic), an erasable programmable read-only memory (EPROM) (magnetic), a portable optical disc such as a CD, CD-R, CD-RW, DVD, DVD-R, or DVD-RW, or flash memory such as compact flash cards, secured digital cards, USB memory devices, memory sticks and the like.
The firmware can be propagated within any transport medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a “transport medium” can be any medium that can communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The transport readable medium can include, but is not limited to, an electronic, magnetic, optical, electromagnetic, or infrared wired or wireless propagation medium.
Device 500 can include a power supply circuit 536. Power supply circuit 536 can be coupled to various components of device 500 such as host processor 528. Power supply circuit 536 can draw current from battery 534 and can supply the current to the rest of the components of device 500. Power supply circuit 536 can also include a switching voltage regulator and/or a dc-dc converter, to maintain a regulated power supply voltage needed by the components.
Power supply circuit 536 can also include a power management unit to perform various power management functions. The power management functions can include detecting whether or not device 500 is coupled to power adapter 550, monitoring available energy in battery 534, and notifying host processor 528 of a low battery state. The power supply circuit 536 can detect whether or not device 500 is coupled to power adapter 550 by monitoring an input voltage level, for example. If the input voltage level is above a predetermined value, the power supply circuit 536 can determine that device 500 is coupled to power adapter 550. If the input voltage is level is below the predetermined value, the power supply circuit 536 can determine that device 500 is not coupled to power adapter 550. In response to receiving the low notification, host processor 528 can perform any number of functions including switching to a low power consumption mode.
Power adapter 550 can introduce or add noise during the process of charging battery 534 or while power adapter 550 is coupled to device 500. A touch pixel, such as touch pixel 302 of
In some examples, the stimulating noise source can cause false touch readings for untouched locations on the touch sensor panel. This can occur when the noise source stimulates a sensor from the sensor location currently being stimulated by a drive line at an untouched location in the touch sensor panel. Since different sensors can share the same sense line in certain touch sensor panel configurations, a false touch event can be indicated when a panel-stimulated signal generated on a sense line by a sensing element at a non-touched sensor is combined with a noise-stimulated signal generated on the same sense line by a sensing element at a different touch sensor. Since a touch event is indicated at the intersection between the panel-stimulated drive line and the touch-indicating sense line, the panel can incorrectly identify a touch at the untouched location. In some examples, the stimulating noise source can cause saturation of analog touch detection circuitry, thereby preventing the circuitry from recognizing a touch event.
In some examples, the touch location can be calculated using an algorithm that utilizes detected capacitance values from multiple touch pixels. The algorithm can return a touch location with a resolution higher than the number of pixels. The stimulating noise source can lead to erroneous touch locations.
To prevent adverse effects to the touch sensor panel while the device is charging, the touch controller or processor can time multiplex touch scan periods and inductive charging periods.
One way to prevent corrupt touch signals due to noise from the charger or inductive charger can be to perform a touch scan during periods when the charger is not charging, as shown in
Another way to prevent corrupt touch signals can be to have the host processor tell the inductive charger to turn off its inductive power during touch scans. One issue with having the host processor communicate to the charger can be the processing load required to enable and execute such communication.
The touch controller (or processor) can determine whether each scan is includes noise or is noise-free (step 754). The touch controller can discard or ignore the touch scans performed during a noise period (step 756), and can keep the touch scans performed during a noise-free period (step 758). For example, touch controller can discard “bad” touch scans 722 and 724 during noise period 730, while keeping “good” touch scans 726 and 728 during noise-free period 732. In some examples, the touch controller can keep one touch scan performed during a noise-free period 732 (such as touch scan 726) and can discard any remaining touch scans performed during the same noise-free period 732 (such as touch scan 728). In some examples, touch controller can average a plurality of touch scans (such as touch scans 726 and 728) during a noise-free period 732 (step 760) by averaging the touch values of individual touch pixels in the plurality of scans.
In some examples, the scan period 734 can be decreased (i.e., less than a scan period when the device is not connected to a charger) and the number of touch scans within the touch scan period T can be increased (i.e., greater than the number of touch scans when the device battery is not connected to a power adapter or inductive charger) when the device is coupled to the power adapter or the inductive charger. For example, the number of touch scans within the touch scan time T of
In some examples, the scan period 734 and number of touch scans within the touch scan period T can be based on the total charge time (i.e., time duration or percentage charge required to reach 100% battery life) and power consumption. For example, if the battery has a 10% battery life (i.e., 90% charge required to reach 100% battery life), the power adapter or inductive charger can increase the duty cycle for inductive charging (i.e., noise-free period 732 is decreased) in order to reduce the time required to reach 100% battery life. As a result, the number of touch scans may need to be increased in order to achieve good touch scans during the noise-free period 732. In some examples, the number of touch scans within the touch scan period T can lead to a significant amount of power consumption, causing an increased time required to reach 100% battery life. If the device determines that this increased time is greater than a predetermined number, then the number of touch scans can be reduced.
Determining whether a touch scan is a bad touch scan can include performing a touch scan across the array of touch pixels and making a determination based on the scan profile.
The profile of a noise-free touch image can be exhibit a profile as shown in
In some examples, the profile of the touch image can be stored in a memory. The touch controller can compare a profile of a touch image with a history of profiles, and a determination whether a touch is corrupted by noise can be made based on the comparison. For example, the curve of an untouched surface can be flat or can exhibit characteristics of a noisy signal such as random fluctuations. In some examples, the history of profiles can include a profile with a predetermined curve. In some examples, the touch controller can keep track of the number of bad scans or percentage of bad scans relative to the number of total scans. Based on the number of bad scans or percentage of bad scans to the total scans, the touch controller can dynamically change the scan period (such as scan period 734), the touch scan frequency, the number of touch scans within a touch scan time, and/or the inductive charging frequency.
In some examples, the determination of a bad touch scan can be based on a single touch point along the array or a subset of touch pixels. In some examples, determination of a bad touch scan can be based on all of the touch points. In some examples, touch points located substantially near the edges of the touch screen or touch sensor panel can be discarded.
In some examples, the touch controller can perform multiple scans on a single pixel. Determination of a bad or good touch scan can be time based. The capacitance value from the single pixel can be compared to a capacitance value from the same pixel during a previous time. If the capacitance value at any given time is not substantially the same as the mean or median value, then the touch scan can be a bad touch scan.
By time multiplexing the touch scan periods and inductive charging periods (i.e., touch charge mode), the touch controller can receive touch images that are not corrupted by noise. However, time multiplexing can also lead to a longer charge time (i.e., the amount of time to reach 100% battery life) than when not time multiplexing (i.e., charging the entire time). As such, in some examples, the host processor can send a notification to the power supply circuit when a touch is no longer detected. In response to the notification, the power supply circuit can notify the charger, and the charger can switch to charging the entire time or a substantial amount of the entire time (i.e., a normal charge mode).
In some examples, the charger can charge using a normal charge mode. When the touch sensor panel detects a first touch, the first touch scan can be during a noise period. Instead of determining a location and/or discarding the bad touch scan, the touch controller can send a notification to the charger. In response to receiving the notification, the charger can switch to the touch charge mode. In some examples, the device can include a button, and a force on the button can generate the notification. In some examples, detection of the first touch and/or force on the button can cause the device to exit a sleep state. In some examples, the charger or dock can communicate with the device during the one or more noise periods (such as noise period 730 of
In some examples, the host processor or touch controller can determine whether a touch scan is a good touch scan or a bad touch scan. In some examples, the processing need not be performed on the device itself.
In operation, instead of processing the information on device 900 itself, device 900 can send raw data 930 over communications link 920 to host 910. Host 910 can receive raw data 930, and host 910 can process the information. Processing the information can include determining whether a touch scan is a good touch scan or a bad touch scan or dynamically changing the scan period, the touch scan frequency, the number of touch scans within a touch scan time, and/or the inductive charging frequency. In some examples, host 910 can process false touches, and can discard false touches without generating a notification to device 900. Host 910 can also include storage or memory for tracking good touch scans and bad touch scans. Host 910 can send the processed result 940 or related information back to device 900. Based on the processed result 940, device 900 can notify the user or adjust its operation accordingly. By offloading the processing and/or storage of the information, device 900 can conserve space and power enabling device 900 to remain small and portable, as space that could otherwise be required for processing logic can be freed up on the device.
In some examples, a method of scanning a touch sensor panel is disclosed. The method may comprise: acquiring data from a plurality of touch sensors; determining whether the data includes noise, the noise generated by a charger; and discarding the data when the data includes the noise. Additionally or alternatively to one or more examples disclosed above, in other examples, the determination includes: determining a curve of a touch profile from the acquired data; determining a shape of the curve; and comparing the shape of the curve to the shape of a historical touch profile. Additionally or alternatively to one or more examples disclosed above, in other examples, the curve is a Gaussian curve. Additionally or alternatively to one or more examples disclosed above, in other examples, the determination further includes determining a slope of the curve and using the slope in the comparison. Additionally or alternatively to one or more examples disclosed above, in other examples, the determination includes determining a full-width half-maximum of the curve. Additionally or alternatively to one or more examples disclosed above, in other examples, the method further comprises determining a number of scans including the noise and a total number of scans during a scan period. Additionally or alternatively to one or more examples disclosed above, in other examples, the method further comprises dynamically changing at least one of a scan period, a scan frequency, and a number of touch scans within the scan period. Additionally or alternatively to one or more examples disclosed above, in other examples, the method further comprises generating an indication of a first touch. Additionally or alternatively to one or more examples disclosed above, in other examples, the acquiring data includes acquiring data for a plurality of touch scans, and wherein the determining whether the data includes noise includes a time based method.
In some examples, a method of a first device communicating with a second device is disclosed. The method may comprise: sending, to a second device, one or more touch values from sense circuitry; and receiving, from the second device, at least one of a noise-free touch image, scan period, and a number of touch scans within a scan period.
In some examples, a touch sensor panel is disclosed. The touch sensor panel may comprise: sensing circuit configured to acquire data from a plurality of touch sensors; logic configured to determine whether the data includes noise and discard the data when the data includes noise, wherein the noise is generated by a charger. Additionally or alternatively to one or more examples disclosed above, in other examples, the logic is further configured to determine a curve of a touch profile from the acquired data, determine a shape of the curve, and compare the shape of the curve to the shape of a historical touch profile. Additionally or alternatively to one or more examples disclosed above, in other examples, the historical touch profile includes a predetermined curve. Additionally or alternatively to one or more examples disclosed above, in other examples, the logic is further configured to determine a slope of the curve and using the slope for the comparison. Additionally or alternatively to one or more examples disclosed above, in other examples, the logic is further configured to determine a full-width half-maximum of the curve. Additionally or alternatively to one or more examples disclosed above, in other examples, the logic is further configured to determine a number of scans including the noise and a total number of scans during a scan period. Additionally or alternatively to one or more examples disclosed above, in other examples, the logic is further configured to dynamically change at least one of a scan period, a scan frequency, and a number of touch scans within the scan period. Additionally or alternatively to one or more examples disclosed above, in other examples, the logic is further configured to generate an indication of a first touch.
In some examples, a charger is disclosed. The charger may comprise logic configured for dynamically changing a duty cycle of a charging period. Additionally or alternatively to one or more examples disclosed above, in other examples, the duty cycle of the charging period is less than a duty cycle of a scan period of a touch sensor panel.
While various examples have been described above, it should be understood that they have been presented by way of example only, and not by way of limitation. Although examples have been fully described with reference to the accompanying drawings, the various diagrams may depict an example architecture or other configuration for this disclosure, which is done to aid in the understanding of the features and functionality that can be included in the disclosure. The disclosure is not restricted to the illustrated exemplary architectures or configurations, but can be implemented using a variety of alternative architectures and configurations. Additionally, although the disclosure is described above in terms of various examples and implementations, it should be understood that the various features and functionality described in one or more of the examples are not limited in their applicability to the particular example with which they are described. They instead can be applied alone or in some combination, to one or more of the other examples of the disclosure, whether or not such examples are described, and whether or not such features are presented as being part of a described example. Thus, the breadth and scope of the present disclosure should not be limited by any of the above-described examples.
Number | Name | Date | Kind |
---|---|---|---|
3558917 | Crouse | Jan 1971 | A |
4163909 | Harr | Aug 1979 | A |
5223784 | Nelson et al. | Jun 1993 | A |
5287074 | Meguro et al. | Feb 1994 | A |
5483261 | Yasutake | Jan 1996 | A |
5488204 | Mead et al. | Jan 1996 | A |
5491706 | Tagawa et al. | Feb 1996 | A |
5610629 | Baur | Mar 1997 | A |
5784036 | Higuchi et al. | Jul 1998 | A |
5796256 | Fowler et al. | Aug 1998 | A |
5825352 | Bisset et al. | Oct 1998 | A |
5835079 | Shieh | Nov 1998 | A |
5880411 | Gillespie et al. | Mar 1999 | A |
5896120 | Iguchi et al. | Apr 1999 | A |
6057910 | Dunne | May 2000 | A |
6081259 | Teterwalk | Jun 2000 | A |
6188391 | Seely et al. | Feb 2001 | B1 |
6236386 | Watanabe | May 2001 | B1 |
6310610 | Beaton et al. | Oct 2001 | B1 |
6323846 | Westerman et al. | Nov 2001 | B1 |
6411250 | Oswald et al. | Jun 2002 | B1 |
6424338 | Anderson | Jul 2002 | B1 |
6476798 | Bertram et al. | Nov 2002 | B1 |
6549193 | Huang et al. | Apr 2003 | B1 |
6587800 | Parker et al. | Jul 2003 | B1 |
6657616 | Sims | Dec 2003 | B2 |
6690387 | Zimmerman et al. | Feb 2004 | B2 |
6765557 | Segal et al. | Jul 2004 | B1 |
7015894 | Morohoshi | Mar 2006 | B2 |
7024337 | Yoda | Apr 2006 | B2 |
7072804 | Weller | Jul 2006 | B2 |
7170501 | Inamori | Jan 2007 | B2 |
7184064 | Zimmerman et al. | Feb 2007 | B2 |
7367004 | Katou | Apr 2008 | B2 |
7428708 | Okamoto et al. | Sep 2008 | B2 |
7511702 | Hotelling | Mar 2009 | B2 |
7538760 | Hotelling et al. | May 2009 | B2 |
7650555 | Imming et al. | Jan 2010 | B2 |
7656168 | Mahowald et al. | Feb 2010 | B2 |
7663607 | Hotelling et al. | Feb 2010 | B2 |
8040142 | Bokma et al. | Oct 2011 | B1 |
8294687 | Ksondzyk | Oct 2012 | B1 |
8479122 | Hotelling et al. | Jul 2013 | B2 |
8874396 | Olson | Oct 2014 | B1 |
9442597 | Shih et al. | Sep 2016 | B2 |
9703422 | Shih et al. | Jul 2017 | B2 |
20020089491 | Willig | Jul 2002 | A1 |
20020135568 | Chen | Sep 2002 | A1 |
20030058929 | Cox et al. | Mar 2003 | A1 |
20030197689 | May | Oct 2003 | A1 |
20030206162 | Roberts | Nov 2003 | A1 |
20040090730 | Byrne et al. | May 2004 | A1 |
20040100450 | Choi | May 2004 | A1 |
20060197753 | Hotelling | Sep 2006 | A1 |
20060256093 | Furukawa et al. | Nov 2006 | A1 |
20070046639 | Swedin | Mar 2007 | A1 |
20080030239 | Sullivan et al. | Feb 2008 | A1 |
20080165157 | Fu | Jul 2008 | A1 |
20080179112 | Qin et al. | Jul 2008 | A1 |
20080218129 | Yun | Sep 2008 | A1 |
20080310485 | Soliman et al. | Dec 2008 | A1 |
20090085894 | Gandhi et al. | Apr 2009 | A1 |
20090202002 | Yao et al. | Aug 2009 | A1 |
20090204860 | Yao et al. | Aug 2009 | A1 |
20100026656 | Hotelling et al. | Feb 2010 | A1 |
20100201314 | Toncich | Aug 2010 | A1 |
20100253641 | Swedin | Oct 2010 | A1 |
20110069031 | Fu | Mar 2011 | A1 |
20110133700 | Martin | Jun 2011 | A1 |
20110157068 | Parker et al. | Jun 2011 | A1 |
20110157069 | Zhuang | Jun 2011 | A1 |
20110249394 | Nielsen | Oct 2011 | A1 |
20110254802 | Philipp | Oct 2011 | A1 |
20110266074 | Fan | Nov 2011 | A1 |
20120043976 | Bokma et al. | Feb 2012 | A1 |
20120062479 | Feldstein | Mar 2012 | A1 |
20120071149 | Bandyopadhyay et al. | Mar 2012 | A1 |
20120287081 | Akai | Nov 2012 | A1 |
20120293445 | Crandall | Nov 2012 | A1 |
20120306739 | Tsuda | Dec 2012 | A1 |
20130044076 | Wang | Feb 2013 | A1 |
20130076700 | Chiu | Mar 2013 | A1 |
20130113711 | Nien et al. | May 2013 | A1 |
20130141346 | Oh | Jun 2013 | A1 |
20130319137 | Grau | Dec 2013 | A1 |
20140028624 | Marsden | Jan 2014 | A1 |
20140092061 | Akai | Apr 2014 | A1 |
20140111465 | Shih | Apr 2014 | A1 |
20140111467 | Chen | Apr 2014 | A1 |
20140132559 | Kim | May 2014 | A1 |
20140168539 | Kim | Jun 2014 | A1 |
20140267059 | Deokar | Sep 2014 | A1 |
20150091865 | Funayama | Apr 2015 | A1 |
20150169108 | Ishii | Jun 2015 | A1 |
20150193070 | Tilak | Jul 2015 | A1 |
20150234519 | Gowreesunker | Aug 2015 | A1 |
20150242015 | Cho | Aug 2015 | A1 |
20150355767 | Abe | Dec 2015 | A1 |
20160378264 | Shih et al. | Dec 2016 | A1 |
Number | Date | Country |
---|---|---|
1 901 157 | Mar 2008 | EP |
2 104 023 | Sep 2009 | EP |
2 424 993 | Oct 2006 | GB |
2000-076002 | Mar 2000 | JP |
2000-163031 | Jun 2000 | JP |
2002-342033 | Nov 2002 | JP |
WO-2005036510 | Apr 2005 | WO |
WO-2008085786 | Jul 2008 | WO |
WO-2008085786 | Jul 2008 | WO |
Entry |
---|
Lee, S.K. et al. (Apr. 1985). “A Multi-Touch Three Dimensional Touch-Sensitive Tablet,” Proceedings of CHI: ACM Conference on Human Factors in Computing Systems, pp. 21-25. |
Rubine, D.H. (Dec. 1991). “The Automatic Recognition of Gestures,” CMU-CS-91-202, Submitted in Partial Fulfillment of the Requirements of the Degree of Doctor of Philosophy in Computer Science at Carnegie Mellon University, 285 pages. |
Rubine, D.H. (May 1992). “Combining Gestures and Direct Manipulation,” CHI '92, pp. 659-660. |
Westerman, W. (Spring 1999). “Hand Tracking, Finger Identification, and Chordic Manipulation on a Multi-Touch Surface,” A Dissertation Submitted to the Faculty of the University of Delaware in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy in Electrical Engineering, 364 pages. |
Anonymous. (2008). “SLIMbus™ Host Controller IP,” Arasan Chip Systems, Inc. Version 1.4, URL http://www.arasan.com/products/prod—overview/mipi/SLIMbus—Host—pb.pdf, last visited on Oct. 2, 2008, two pages. |
Boyce, K. (2008). “An Introduction to the Mobile Industry Processor Interface (MIPI) Alliance Standard; Serial Low-Power Inter-Chip Media Bus (SLIMbus™),” National Semiconductor Audio Products Group, URL https://www.national.com/appinfo/audio/files/intro—to—SLIMbus.pdf, last visited Oct. 2, 2008, 20 pages. |
Final Office Action dated May 19, 2011, for U.S. Appl. No. 12/229,685, filed Aug. 25, 2008, 16 pages. |
Final Office Action dated Nov. 26, 2012, for U.S. Appl. No. 12/954,557, filed Nov. 24, 2010, 16 pages. |
Final Office Action dated May 22, 2013, for U.S. Appl. No. 12/240,692, filed Sep. 29, 2008, 10 pages. |
Final Office Action dated Nov. 29, 2013, for U.S. Appl. No. 12/954,557, filed Nov. 24, 2010, 17 pages. |
Final Office Action dated Jun. 27, 2014, for U.S. Appl. No. 12/240,692, filed Sep. 29, 2008, 11 pages. |
Final Office Action dated Sep. 16, 2015, for U.S. Appl. No. 12/240,692, filed Sep. 29, 2008, 13 pages. |
Final Office Action dated Dec. 4, 2015, for U.S. Appl. No. 13/750,847, filed Jan. 25, 2013, 18 pages. |
International Search Report dated Dec. 23, 2008, for PCT Application No. PCT/US2007/089165, filed Dec. 28, 2007, three pages. |
Non-Final Office Action dated Mar. 19, 2010, for U.S. Appl. No. 11/620,466, 10 pages. |
Non-Final Office Action dated Dec. 7, 2010, for U.S. Appl. No. 12/229,685, filed Aug. 25, 2008, 17 pages. |
Non-Final Office Action dated Oct. 19, 2011, for U.S. Appl. No. 12/954,557, 21 pages. |
Non-Final Office Action dated Mar. 29, 2013, for U.S. Appl. No. 12/954,557, filed Nov. 24, 2010, 16 pages. |
Non-Final Office Action dated Feb. 17, 2012, for U.S. Appl. No. 12/229,685, filed Aug. 25, 2008, 18 pages. |
Non-Final Office Action dated Dec. 4, 2012, for U.S. Appl. No. 12/240,692, filed Sep. 29, 2008, 10 pages. |
Non-Final Office Action dated Feb. 13, 2014, for U.S. Appl. No. 12/240,692, filed Sep. 29, 2008, 10 pages. |
Non-Final Office Action dated Feb. 27, 2015, for U.S. Appl. No. 12/240,692, filed Sep. 29, 2008, 12 pages. |
Non-Final Office Action dated Apr. 8, 2015, for U.S. Appl. No. 13/750,847, filed Jan. 25, 2013, 15 pages. |
Notice of Allowance dated Aug. 11, 2010, for U.S. Appl. No. 11/620,466, four pages. |
Notice of Allowance dated May 19, 2016, for U.S. Appl. No. 13/750,847, filed Jan. 25, 2013, 8 pages. |
Non-Final Office Action dated Jan. 23, 2017, for U.S. Appl. No. 15/261,678, filed Sep. 9, 2016, 18 pages. |
Notice of Allowance dated Mar. 30, 2017, for U.S. Appl. No. 15/261,678, filed Sep. 9, 2016, eight pages. |
Number | Date | Country | |
---|---|---|---|
20150370410 A1 | Dec 2015 | US |