Computers, mobile phones, tablets, and other computing and communication devices include a variety of input interfaces. For example, computers include keyboard and mouse input interfaces. Using a mouse, a user may navigate to an area of the display and make a selection. For various reasons, a mouse or equivalent input interface is not practical for handheld devices such as tablets and mobile phones. One of those reasons is that a handheld device is generally not used on a flat, stable surface to accommodate mouse operation. Most tablets and many mobile devices include capacitive touch sensors built under the screen that are used as a primary navigation and data input method. These touch sensors require users to navigate the display with their finger, thereby potentially obstructing the screen as they try to make a selection and leaving finger prints and smudges on the screen over time.
For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
It should be understood at the outset that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
As noted above, many input interfaces are available for computation and communication devices. Embodiments of the system and method described herein relate to touch-less gesture detection as a user interface. Additional embodiments relate to a light source and calibration based on the light source to facilitate the gesture detection.
Through the inclusion of two or more ALSs 110 (e.g., three ALSs 110x, 110y, 110z), the device 100 shown in
A touch-free gesture may mimic a swipe, also known as a flick, which can be a particular type of touch on a touch-sensitive display. The swipe or flick may begin at an origin point and continue to an end point, for example, a concluding end of the gesture. A gesture may be identified by attributes or characteristics of the gesture as discussed further below. These attributes may include the origin point (of detection by an ALS 110), the end point, the distance travelled by the object 240, the duration, the velocity, and the direction, for example. A gesture may be long or short in distance and/or duration. Two points of the gesture may be utilized to determine a direction of the gesture. A gesture may also include a hover. A hover may be non-movement of the object 240 at a location that is generally unchanged over a period of time.
In the arrangement of ALSs 110 shown in
Another distance that must be considered is the distance between the object 240 and the ALS 110 (e.g., distance 250 between the object 240 and ALS 110z). First, as
An input to the system 500 is the light intensity 115 measured from each of the ALSs 110. The measurements are received by a data collection engine 510, which includes both memory and processor functionalities. As the light intensity 115 measurement data is received from each of the ALSs 110, the data collection engine 510 outputs a frame of data 520 for each time instant. That is, each frame of data 520 includes the light intensity 115 measurement for every ALS 110 at a given time instant. While each frame of data 520 may generally be discussed as including the light intensity 115 measurement for each ALS 110 at an instant of time, the ALSs 110 may instead sample light intensity 115 in turn (rather than simultaneously) such that a frame of data 520 includes light intensity 115 measurements for a period of time for one cycle of the ALSs 110. A processor functioning as a gesture identifier 530 receives each frame of data 520. The gesture identifier 530 may operate according to one of several embodiments as discussed below.
In order to identify a movement of the object 240 as a particular (known) gesture, the gesture identifier 530 uses a comparison of light intensity 115 measurements of the ALSs 110, as discussed below, along with a comparison with a gesture template 537 stored in a template memory device 535. A dynamically adjusted minimum change in light intensity 115 may be set based on expected noise and errors. That is, a threshold percentage of change in detected light intensity 115 may be required before it is interpreted as a true variation in ambient light. Based on the light intensity 115 measurements among the ALSs 110 within a frame of data 520 (for a single time instant or measurement cycle), the gesture identifier 530 may ascertain a position of the object 240. For example, for a given frame of data 520, if the light intensity 115 measurements of ALSs 110d and 110f are higher (by a defined threshold) than the light intensity 115 measurement output by ALS 110e, then the object 240 may be determined to be over the ALS 110e and, thereby, blocking some of the light from the light source 210. Based on the light intensity 115 measurements among two or more frames of data 520 (two or more time instants or measurement cycles), the gesture identifier 530 may ascertain characteristics of the (movement) gesture such as a direction of the movement, speed of the movement, and whether the movement is accelerating or decelerating. For example, if the light intensity 115 measurements of ALSs 110d and 110f are higher (by a defined threshold) than the light intensity 115 measurement output by ALS 110e in one frame of data 520 and the light intensity 115 measurement of ALS 110e is higher (by a defined threshold) than the light intensity 115 measurements output by ALSs 110d and 110f in the next frame of data 520, the gesture identifier 530 may ascertain that the object 240 moved from a direction of the ALS 110e toward a direction of the ALSs 110d and 110f. If the change in light intensity 115 measurements occurred over several frames of data 520, then the movement of the object 240 may be ascertained as being relatively slower than if the change occurred over the course of one frame of data 240. Based on the ascertained characteristics of the gesture, the gesture identifier 530 may identify the gesture among a set of known gestures based on the gesture template 537.
The gesture template 537 facilitates the association of a movement of the object 240 discerned by the gesture identifier 530 with a particular known gesture. The gesture template 537 may be regarded as a sample of ideal light intensity 115 measurement data corresponding with each known gesture. More specifically, the gesture template 537 may be regarded as providing the ideal relative light intensity 115 among the ALSs 110 or frames of data 520 or both for a given known gesture. Thus, by comparing the input light intensity 115 measurements (in the frames of data 520) or comparisons of light intensity measurements 115 with the ideal measurements in the gesture template 537, the gesture identifier 530 identifies the object 240 movement as a known gesture. This identification of the gesture may be done by a process of elimination of the known gestures in the gesture template 537. Thus, the gesture identifier 530 may identify the gesture using the gesture template 537, through a process of elimination of available known gestures, before the object 240 movement is complete. In this case, the gesture identifier 530 may continue to process frames of data 520 to verify the detected gesture or, in alternate embodiments, the gesture identifier 530 may stop processing additional frames of data 520 after identifying the gesture and wait for a trigger signal 540 discussed below. Each of the ALSs 110 may be programmable to provide 10, 20, 50, 10, 125, 15, 200 and 250 samples of light intensity 115 (frames of data 520) a second. The ALS 110 scanning rate is a factor in determining the speed at which a gesture may be made in order to be recognized. That is, when the ALSs 110 are sampling at a rate of 10 light intensity 115 samples per second, the fastest identifiable gesture is much slower than the fastest identifiable gesture that may be made when the ALSs 110 are sampling at a rate of 250 light intensity 115 samples per second. The ALSs 115 sampling at a rate of 10 frames of data 520 per second (10 light intensity 115 samples per second each) may translate to an object 240 travelling 10 cm in 1.5 seconds in order to be recognized and processed properly. The system 610 (
Another input to the gesture identifier 530 is one of the gesture libraries 555 stored in a gesture library storage 550. Each gesture library 555 is associated with an application, and the gesture identifier 530 selects the gesture library 555 associated with the application currently being executed by the device 100. A given gesture library 555 associated with a given application may not include every known gesture in the gesture template 537. Thus, based on the application currently being executed by the device 100, the gesture identifier 530 may narrow down the set of known gestures within the gesture template 537 to compare against the frames of data 520 output by the data collection engine 510 in order to identify the gesture. A gesture library 555 indicates an action output 560 corresponding with a set of gestures. Thus, when the gesture identifier 530 identifies a known gesture based on the movement of the object 240 and the gesture template 537, and the gesture identifier 530 finds that known gesture among the set of gestures in a gesture library 555 associated with the application currently being run by the device 100, then the gesture identifier 530 outputs the corresponding action output 560 stemming from the object 240 movement. The action output 560 of the gesture identifier 530 acts as a command to the application being executed. For example, when the application being executed is a document editing session, the gestures identified by the gesture identifier 530 may correspond with action outputs 560 such as “next page” (wave down), “previous page” (wave up), “zoom in” (bringing fingers together), and “zoom out” (spreading fingers apart). If the device 100 is currently not executing any application or if the application currently being executed by the device 100 does not have a gesture library 555 associated with it, then, even if the gesture identifier 530 uses the gesture template 537 to identify a known gesture based on the movement of the object 240, no action is taken by the gesture identifier 530 based on identifying the gesture. That is, there is no action output 560 corresponding with the identified gesture, because there is no gesture library 555 to look up.
According to one embodiment, the gesture identifier 530 may not use the gesture template 537 to identify a gesture when no application is being executed by the device 100 or when an application without an associated gesture library 555 is being executed by the device 100. According to another embodiment, the gesture identifier 530 may not begin to process any frames of data 520 before receiving a trigger signal 540. The trigger signal 540 is detailed below with reference to
Regardless of the behavior of the gesture identifier 530 based on the trigger signal 540, the lack of an associated gesture library 555, or the lack of an application being executed at all, the data collection engine 510 still outputs the frames of data 520. This is because the light intensity 115 measurements may be used for background functions such as adjustment of the screen 120 backlighting, for example, based on the detected ambient light, even if gesture detection is not to be performed. Some of these background functions are detailed below with reference to
Based on the light intensity 115 measurements (directly or in the form of frames of data 520) and the additional information 620, the system 610 adjusts the sensitivity or wavelength band or range or both for each ALS 110. For example, based on the available light (measured ambient light intensity 115), the system 610 may change the wavelength range for the ALSs 110 via a control signal 630 from the system 610 to one or more of the ALSs 110. The change (adjustment of wavelength range) may ensure that the ALSs 110 are focused in the correct wavelength (frequency) band for the current conditions. As another example, based on a change in available light (e.g., based on switching a light on or off), the system 610 may change the sensitivity of the ALSs 110. Any order of switching lights produces a new range of change in light intensity 115 to which the ALSs 110 must adapt. For example, the range of change of light intensity 115 to which the ALSs 110 are sensitive may be 50-250 lux. In a darker environment (e.g., a conference room during a presentation) the range of change of light intensity 115 to which the ALSs 110 are sensitive may be 2-15 lux. The adjustment of the ALSs 110 through the control signal 630 may be done continuously, periodically, or based on a trigger event such as, for example, a change in the application being executed by the device 100. For example, sensitivity adjustment may be done automatically once for every 5 frames of data 520. The system 610 may also adjust the order and frequency of light intensity 115 measurements by the ALSs 110. For example, based on additional information 620 indicating that a particular application is being executed by the device 100, the system 610 may send control signals 630 to have the ALSs 110 collect light intensity 115 samples for each cycle (frame of data 520) in a particular order and with a particular frequency.
In addition to controlling the ALSs 110, the system 610 may provide the trigger signal 540 to the gesture identifier 530 (see
In various embodiments, the DSP 801 or some other form of controller or central processing unit (CPU) operates to control the various components of the device 100 in accordance with embedded software or firmware stored in memory 802 or stored in memory contained within the DSP 801 itself. In addition to the embedded software or firmware, the DSP 801 may execute other applications stored in the memory 802 or made available via information media such as portable data storage media like the removable memory card 810 or via wired or wireless network communications. The application software may comprise a compiled set of machine-readable instructions that configure the DSP 801 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 801.
The antenna and front-end unit 803 may be provided to convert between wireless signals and electrical signals, enabling the device 100 to send and receive information from a cellular network or some other available wireless communications network or from a peer device 100. In an embodiment, the antenna and front-end unit 803 may include multiple antennas to support beam forming and/or multiple input multiple output (MIMO) operations. As is known to those skilled in the art, MIMO operations may provide spatial diversity, which can be used to overcome difficult channel conditions or to increase channel throughput. Likewise, the antenna and front-end unit 803 may include antenna tuning or impedance matching components, RF power amplifiers, or low noise amplifiers.
In various embodiments, the RF transceiver 804 facilitates frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF. In some descriptions a radio transceiver or RF transceiver may be understood to include other signal processing functionality such as modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions. For the purposes of clarity, the description here separates the description of this signal processing from the RF and/or radio stage and conceptually allocates that signal processing to the analog baseband processing unit 805 or the DSP 801 or other central processing unit. In some embodiments, the RF Transceiver 804, portions of the antenna and front-end unit 803, and the analog base band processing unit 805 may be combined in one or more processing units and/or application specific integrated circuits (ASICs).
Note that, in this diagram, the radio access technology (RAT) RAT1 and RAT2 transceivers 821, 822, the IXRF 823, the IRSL 824 and Multi-RAT subsystem 825 are operably coupled to the RF transceiver 804 and analog baseband processing unit 805 and then also coupled to the antenna and front-end unit 803 via the RF transceiver 804. As there may be multiple RAT transceivers, there will typically be multiple antennas or front ends 803 or RF transceivers 804, one for each RAT or band of operation.
The analog baseband processing unit 805 may provide various analog processing of inputs and outputs for the RF transceivers 804 and the speech interfaces (806, 807, 808). For example, the analog baseband processing unit 805 receives inputs from the microphone 806 and the headset 808 and provides outputs to the earpiece 807 and the headset 808. To that end, the analog baseband processing unit 805 may have ports for connecting to the built-in microphone 806 and the earpiece speaker 807 that enable the device 100 to be used as a cell phone. The analog baseband processing unit 805 may further include a port for connecting to a headset or other hands-free microphone and speaker configuration. The analog baseband processing unit 805 may provide digital-to-analog conversion in one signal direction and analog-to-digital conversion in the opposing signal direction. In various embodiments, at least some of the functionality of the analog baseband processing unit 805 may be provided by digital processing components, for example by the DSP 801 or by other central processing units.
The DSP 801 may perform modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions associated with wireless communications. In an embodiment, for example in a code division multiple access (CDMA) technology application, for a transmitter function the DSP 801 may perform modulation, coding, interleaving, and spreading, and for a receiver function the DSP 801 may perform despreading, deinterleaving, decoding, and demodulation. In another embodiment, for example in an orthogonal frequency division multiplex access (OFDMA) technology application, for the transmitter function the DSP 801 may perform modulation, coding, interleaving, inverse fast Fourier transforming, and cyclic prefix appending, and for a receiver function the DSP 801 may perform cyclic prefix removal, fast Fourier transforming, deinterleaving, decoding, and demodulation. In other wireless technology applications, yet other signal processing functions and combinations of signal processing functions may be performed by the DSP 801.
The DSP 801 may communicate with a wireless network via the analog baseband processing unit 805. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages. The input/output interface (“Bus”) 809 interconnects the DSP 801 and various memories and interfaces. The memory 802 and the removable memory card 810 may provide software and data to configure the operation of the DSP 801. Among the interfaces may be the USB interface 811 and the short range wireless communication sub-system 814. The USB interface 811 may be used to charge the device 100 and may also enable the device 100 to function as a peripheral device to exchange information with a personal computer or other computer system. The short range wireless communication sub-system 814 may include an infrared port, a Bluetooth interface, an IEEE 802.11 compliant wireless interface, or any other short range wireless communication sub-system, which may enable the device to communicate wirelessly with other nearby client nodes and access nodes. The short-range wireless communication sub-system 814 may also include suitable RF Transceiver, Antenna and Front End subsystems.
The input/output interface (“Bus”) 809 may further connect the DSP 801 to the alert 812 that, when triggered, causes the device 100 to provide a notice to the user, for example, by ringing, playing a melody, or vibrating. The alert 812 may serve as a mechanism for alerting the user to any of various events such as an incoming call, a new text message, and an appointment reminder by silently vibrating, or by playing a specific pre-assigned melody for a particular caller.
The keypad 813 couples to the DSP 801 via the I/O interface (“Bus”) 809 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the device 100. The keypad 813 may be a full or reduced alphanumeric keyboard such as QWERTY, DVORAK, AZERTY and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may likewise include a track wheel, track pad, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. Another input mechanism may be the LCD 815, which may include touch screen capability and also display text and/or graphics to the user. The LCD controller 816 couples the DSP 801 to the LCD 815.
The CCD camera 817, if equipped, enables the device 100 to make digital pictures. The DSP 801 communicates with the CCD camera 817 via the camera controller 818. In another embodiment, a camera operating according to a technology other than Charge Coupled Device cameras may be employed. The GPS sensor 819 is coupled to the DSP 801 to decode global positioning system signals or other navigational signals, thereby enabling the device 100 to determine its position. The GPS sensor 819 may be coupled to an antenna and front end (not shown) suitable for its band of operation. Various other peripherals may also be included to provide additional functions, such as radio and television reception.
In various embodiments, device 100 comprises a first Radio Access Technology (RAT) transceiver 821 and a second RAT transceiver 822. As shown in
As noted above in the discussion of the system 610, the sensitivity of the ALSs 110 may be adjusted based on the available light. When the available light drops below a minimum threshold (e.g., the device 100 is in a completely dark room with no windows as an extreme example), embodiments of the device 100 described below supply the ambient light (backlight) in order to facilitate gesture detection. Calibration of the ALSs 110 based on the backlight is also detailed below.
When the ambient lighting conditions dictate that the backlight sources 910 are needed, a calibration is performed for the ALSs 110. An exemplary calibration is discussed with reference to Table 1 below.
Table 1 indicates an on (“1”) or off (“0”) state for each backlight source 910a, 910b, 910c shown in
To address potential false alarms, caused by a temporary obstruction to the light source 210 for example, operation of the backlight sources 910 may not begin until the light intensity 115 measurements of all the ALSs 110 are below the minimum threshold value for a certain period of time. In this way, the backlight sources 910 are not likely to be activated based on either a momentary reduction in ambient light level below the minimum threshold or a gesture that includes blocking one or more of the ALSs 110 from the light source 210. A user preference may be selected to prevent the backlight sources 910 from being operated, as well. For example, a user who leaves the device 100 on while sleeping in a dark room will not be disturbed by the backlight sources 910 based on selecting a setting in the device 100. The backlight sources 910 may override the existing screen 120 backlight of a device 100 that facilitates reading the device 120 screen in a dark environment. Thus, during a slide presentation in a dark conference room, for example, if the user wishes to use touch-less gestures to control the slide navigation, he or she may disable the screen 120 backlight and enable the backlight sources 910 based on settings selected in the device 100. When the backlight sources 910 are operational (have been turned on due to ambient light level dropping below the minimum threshold) and the ambient light level then exceeds another threshold representing a maximum acceptable ambient light level for gesture detection, one or more of the backlight sources 910 may be turned off. This maximum threshold value may have to be exceeded for a certain period of time before any of the backlight sources 910 is turned off to ensure that the backlight sources 910 are not disabled based on a temporary flash. This period of time may be the same as or different from the period of time for which the ambient light level must be below the minimum threshold to initiate operation of the backlight sources 910. Based on the maximum threshold, the backlight sources 910 are not left operational after ambient light sources (210) external to the device 100 have begun to provide sufficient light for gesture detection. This may happen because the device 100 is moved to a more well-lit area or because a light source 210 is turned on or restored, for example. Phase synchronization between the ALSs 110 and the backlight sources 910 (matching a frequency of when the ALSs 110 sense light intensity 115 with a frequency of the backlight sources 910) ensures sufficient sensitivity of the ALSs 110 to detect movements that make up gestures.
While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.
Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.
Number | Name | Date | Kind |
---|---|---|---|
5252951 | Tannenbaum et al. | Oct 1993 | A |
5554912 | Thayer et al. | Sep 1996 | A |
5594469 | Freeman et al. | Jan 1997 | A |
6693612 | Matsumoto et al. | Feb 2004 | B1 |
6699093 | Cacciola et al. | Mar 2004 | B1 |
7618323 | Rothschild et al. | Nov 2009 | B2 |
7620316 | Boillot | Nov 2009 | B2 |
8035614 | Bell et al. | Oct 2011 | B2 |
8363157 | Han | Jan 2013 | B1 |
8694062 | Omerovic | Apr 2014 | B2 |
8964062 | Neglur | Feb 2015 | B1 |
9063574 | Ivanchenko | Jun 2015 | B1 |
20020093491 | Gillespie et al. | Jul 2002 | A1 |
20030112228 | Gillespie et al. | Jun 2003 | A1 |
20030156100 | Gettemy | Aug 2003 | A1 |
20040178997 | Gillespie et al. | Sep 2004 | A1 |
20040190776 | Higaki et al. | Sep 2004 | A1 |
20060013440 | Cohen et al. | Jan 2006 | A1 |
20060092142 | Gillespie et al. | May 2006 | A1 |
20060139185 | Bonnat et al. | Jun 2006 | A1 |
20060187214 | Gillespie et al. | Aug 2006 | A1 |
20060279548 | Geaghan | Dec 2006 | A1 |
20070075965 | Huppi et al. | Apr 2007 | A1 |
20070120996 | Boillot | May 2007 | A1 |
20070130547 | Boillot | Jun 2007 | A1 |
20070259716 | Mattice et al. | Nov 2007 | A1 |
20070259717 | Mattice et al. | Nov 2007 | A1 |
20070296867 | Park | Dec 2007 | A1 |
20080005703 | Radivojevic et al. | Jan 2008 | A1 |
20080041640 | Gillespie et al. | Feb 2008 | A1 |
20080042994 | Gillespie et al. | Feb 2008 | A1 |
20080048997 | Gillespie et al. | Feb 2008 | A1 |
20080122803 | Izadi et al. | May 2008 | A1 |
20080134102 | Movold et al. | Jun 2008 | A1 |
20080165145 | Herz et al. | Jul 2008 | A1 |
20080165160 | Kocienda et al. | Jul 2008 | A1 |
20080167834 | Herz et al. | Jul 2008 | A1 |
20080168402 | Blumenberg | Jul 2008 | A1 |
20080266083 | Midholt et al. | Oct 2008 | A1 |
20090031258 | Arrasvuori et al. | Jan 2009 | A1 |
20090051648 | Shamaie et al. | Feb 2009 | A1 |
20090058830 | Herz et al. | Mar 2009 | A1 |
20090074248 | Cohen et al. | Mar 2009 | A1 |
20090077504 | Bell et al. | Mar 2009 | A1 |
20090100383 | Sunday et al. | Apr 2009 | A1 |
20090139778 | Butler et al. | Jun 2009 | A1 |
20090146982 | Thielman et al. | Jun 2009 | A1 |
20090189858 | Lev et al. | Jul 2009 | A1 |
20090195497 | Fitzgerald et al. | Aug 2009 | A1 |
20100027843 | Wilson | Feb 2010 | A1 |
20100060611 | Nie | Mar 2010 | A1 |
20100090947 | Underkoffler et al. | Apr 2010 | A1 |
20100150399 | Svajda et al. | Jun 2010 | A1 |
20100153996 | Migos et al. | Jun 2010 | A1 |
20100156676 | Mooring et al. | Jun 2010 | A1 |
20100177060 | Han | Jul 2010 | A1 |
20100188328 | Dodge et al. | Jul 2010 | A1 |
20100192105 | Kim et al. | Jul 2010 | A1 |
20100244751 | Van Endert | Sep 2010 | A1 |
20100245289 | Svajda | Sep 2010 | A1 |
20100253241 | Van Endert | Oct 2010 | A1 |
20100277073 | Van Endert | Nov 2010 | A1 |
20100313050 | Harrat et al. | Dec 2010 | A1 |
20100325575 | Platzer et al. | Dec 2010 | A1 |
20110010626 | Fino et al. | Jan 2011 | A1 |
20110029913 | Boillot et al. | Feb 2011 | A1 |
20110096009 | Kurokawa et al. | Apr 2011 | A1 |
20110140610 | Van Endert | Jun 2011 | A1 |
20110157016 | Chang | Jun 2011 | A1 |
20110163947 | Shaw et al. | Jul 2011 | A1 |
20110167391 | Momeyer et al. | Jul 2011 | A1 |
20110180709 | Craddock et al. | Jul 2011 | A1 |
20110182519 | Craddock et al. | Jul 2011 | A1 |
20110185309 | Challinor et al. | Jul 2011 | A1 |
20110187640 | Jacobsen et al. | Aug 2011 | A1 |
20110205186 | Newton et al. | Aug 2011 | A1 |
20110211073 | Foster | Sep 2011 | A1 |
20110215733 | Van Endert | Sep 2011 | A1 |
20110221666 | Newton et al. | Sep 2011 | A1 |
20110221669 | Shams et al. | Sep 2011 | A1 |
20110248151 | Holcombe et al. | Oct 2011 | A1 |
20110248961 | Svajda et al. | Oct 2011 | A1 |
20110254864 | Tsuchikawa et al. | Oct 2011 | A1 |
20110291988 | Bamji et al. | Dec 2011 | A1 |
20110296353 | Ahmed et al. | Dec 2011 | A1 |
20110298754 | Bove et al. | Dec 2011 | A1 |
20110306304 | Forutanpour et al. | Dec 2011 | A1 |
20110310005 | Chen et al. | Dec 2011 | A1 |
20110314429 | Blumenberg | Dec 2011 | A1 |
20110314430 | Blumenberg | Dec 2011 | A1 |
20120007821 | Zaliva | Jan 2012 | A1 |
20120007833 | Liu et al. | Jan 2012 | A1 |
20120013529 | McGibney et al. | Jan 2012 | A1 |
20120013539 | Hogan et al. | Jan 2012 | A1 |
20120013540 | Hogan | Jan 2012 | A1 |
20120023443 | Blumenberg | Jan 2012 | A1 |
20120023460 | Blumenberg | Jan 2012 | A1 |
20120023461 | Blumenberg | Jan 2012 | A1 |
20120023509 | Blumenberg | Jan 2012 | A1 |
20120050007 | Forutanpour et al. | Mar 2012 | A1 |
20120056804 | Radivojevic et al. | Mar 2012 | A1 |
20120089948 | Lim et al. | Apr 2012 | A1 |
20120133580 | Kirby et al. | May 2012 | A1 |
20120162636 | Sy | Jun 2012 | A1 |
20120176303 | Miyake | Jul 2012 | A1 |
20120176401 | Hayward et al. | Jul 2012 | A1 |
20120200486 | Meinel et al. | Aug 2012 | A1 |
20120206339 | Dahl | Aug 2012 | A1 |
20120242584 | Tuli | Sep 2012 | A1 |
20120242852 | Hayward et al. | Sep 2012 | A1 |
20120245886 | Zhang et al. | Sep 2012 | A1 |
20120280107 | Skurnik et al. | Nov 2012 | A1 |
20120280900 | Wang et al. | Nov 2012 | A1 |
20120280904 | Skurnik et al. | Nov 2012 | A1 |
20120280905 | Vonog et al. | Nov 2012 | A1 |
20120281129 | Wang et al. | Nov 2012 | A1 |
20120282974 | Green et al. | Nov 2012 | A1 |
20120287044 | Bell et al. | Nov 2012 | A1 |
20120293404 | Federico et al. | Nov 2012 | A1 |
20120306815 | Su et al. | Dec 2012 | A1 |
20120312956 | Chang et al. | Dec 2012 | A1 |
20120317511 | Bell | Dec 2012 | A1 |
20130002538 | Mooring et al. | Jan 2013 | A1 |
20130002601 | McCracken | Jan 2013 | A1 |
20130004016 | Karakotsios et al. | Jan 2013 | A1 |
20130009896 | Zaliva | Jan 2013 | A1 |
20130022214 | Dickins et al. | Jan 2013 | A1 |
20130033418 | Bevilacqua et al. | Feb 2013 | A1 |
20130034265 | Nakasu et al. | Feb 2013 | A1 |
20130053007 | Cosman et al. | Feb 2013 | A1 |
20130067419 | Eltoft | Mar 2013 | A1 |
20130083252 | Boyes | Apr 2013 | A1 |
20130091561 | Bruso et al. | Apr 2013 | A1 |
20130093727 | Eriksson et al. | Apr 2013 | A1 |
20130100036 | Papakipos et al. | Apr 2013 | A1 |
20130102366 | Teng et al. | Apr 2013 | A1 |
20130145535 | Parsons et al. | Jun 2013 | A1 |
20130167221 | Vukoszavlyev et al. | Jun 2013 | A1 |
20130182246 | Tanase | Jul 2013 | A1 |
20130307949 | Zhang et al. | Nov 2013 | A1 |
20130328761 | Boulanger et al. | Dec 2013 | A1 |
20130328842 | Barnhoefer et al. | Dec 2013 | A1 |
20140118257 | Baldwin | May 2014 | A1 |
20140237432 | Geurts et al. | Aug 2014 | A1 |
20140253427 | Gruhlke et al. | Sep 2014 | A1 |
20140306877 | Katz et al. | Oct 2014 | A1 |
20150009290 | Mankowski et al. | Jan 2015 | A1 |
Number | Date | Country |
---|---|---|
0538705 | Apr 1993 | EP |
2226710 | Sep 2010 | EP |
2012140593 | Oct 2012 | WO |
Entry |
---|
Cheng et al., “Contactless gesture recognition system using proximity sensors” Consumer Electronics (ICCE), IEEE International Conference, DOI: 10.1109/ICCE.2011.5722510 pp. 149-150, Feb. 2011. |
EE Times, “Ambient light sensors adjust LCD brightness to save battery power”, pp. 1-2, retrieved Jul. 24, 2013, from http://www.eetimes.com/document.asp?doc—id=1302779&print=yes. |
Pyreos, “Pioneering Low Power Gesture Sensor Enabling Touchless Control for Mobile Devices” [online]; retrieved Jun. 27, 2013; retrieved from http://www.pyreos.com/images/downloads/Applications/Touchless%20Gesture%20Control/Gesture%20Sensor%20FAQs.pdf pp. 1-2. |
Rohm Semiconductor, “Ambient Light Sensor (ALS) Applications in Portable Electronics”, pp. 1-9, retrieved Jul. 24, 2013 from http://www.rohm.com/documents/11303/41217/CNA09016—wp.pdf. |
Silicon Labs, “Touchless Gesturing Brings New Innovation to Electronic Product Designs” [online]; retrieved Jun. 27, 2013; retrieved from http://www.silabs.com/Support%20Documents/TechnicalDocs/TouchlessSensorIC-WP.pdf pp. 1-4. |
Taos, “Light-to-Digital Converter” The Lumenology Company, TAOS132, Mar. 2012, pp. 1-24. |
Liao et al., “Pacer: Fine-grained Interactive Paper via Camera-touch Hybrid Gestures on a Cell Phone”, CHI 2010: Displays Where You Least Expect Them, Apr. 10-15, 2010, pp. 1-10. |
Extended European Search Report for EP Application No. 13174561.4-1960, dated Jan. 3, 2014, pp. 1-8. |
Extended European Search Report for EP Application No. 13174558.0-1960, dated Jan. 3, 2014, pp. 1-10. |
Extended European Search Report for EP Application No. 13174576.2-1960, dated Jan. 3, 2014, pp. 1-12. |
Extended European Search Report for EP Application No. 13174560.6-1960, dated Jan. 3, 2014, pp. 1-10. |
Extended European Search Report for EP Application No. 13174575.4-1960, dated Jan. 3, 2014, pp. 1-9. |
Extended European Search Report for EP Application No. 13175807.0-1960, dated Jan. 15, 2014, pp. 1-7. |
Extended European Search Report for EP Application No. 13174565.5-1959, dated Dec. 6, 2013, pp. 1-7. |
Extended European Search Report for EP Application No. 13174557.2-1956, dated Dec. 13, 2013, pp. 1-7. |
Extended European Search Report for EP Application No. 13174577.0-1560 dated Dec. 13, 2013, pp. 1-7. |
Mankowski, Peter, et al.; U.S. Appl. No. 13/932,470, filed Jul. 1, 2013; Title: Gesture Detection Using Ambient Light Sensors. |
Mankowski, Peter, et al.; U.S. Appl. No. 13/932,235, filed Jul. 1, 2013; Title: Performance Control of Ambient Light Sensors. |
Mankowski, Peter; U.S. Appl. No. 13/932,243, filed Jul. 1, 2013; Title: Password by Touch-Less Gesture. |
Mankowski, Peter; U.S. Appl. No. 13/932,250, filed Jul. 1, 2013; Title: Touch-Less User Interface Using Ambient Light Sensors. |
Mankowski, Peter, et al.; U.S. Appl. No. 13/932,487, filed Jul. 1, 2013; Title: Gesture Detection Using Ambient Light Sensors. |
Mankowski, Peter; U.S. Appl. No. 13/932,260, filed Jul. 1, 2013; Title: Camera Control Using Ambient Light Sensors. |
Mankowski, Peter, et al.; U.S. Appl. No. 13/932,271, filed Jul. 1, 2013; Title: Display Navigation Using Touch-Less Gestures. |
Mankowski, Peter; U.S. Appl. No. 13/932,280, filed Jul. 1, 2013; Title: Alarm Operation by Touch-Less Gesture. |
Mankowski, Peter, et al.; U.S. Appl. No. 13/937,444, filed Jul. 9, 2013; Title: Operating a Device Using Touchless and Touchscreen Gestures. |
Mankowski, Peter, et al.; U.S. Appl. No. 13/949,748, filed Jul. 24, 2013; Title: Backlight for Touchless Gesture Detection. |
Carmel-Veilleux, Tennessee; U.S. Appl. No. 14/019,740, filed Sep. 6, 2013; Title: Device Having Light Intensity Measurement in Presence of Shadows; 27 pages. |
Holenarsipur, Prashanth, et al.; “Ambient-Light Sensing Optimizes Visibility and Battery Life of Portable Displays”; Maxim; Application Note 5051; Jun. 20, 2011; 7 pages. |
Office Action dated Dec. 15, 2014; U.S. Appl. No. 13/932,243, filed Jul. 1, 2013; 29 pages. |
Office Action dated Sep. 3, 2014; U.S. Appl. No. 13/932,260, filed Jul. 1, 2013; 48 pages. |
Office Action dated Nov. 20, 2014; U.S. Appl. No. 13/932,271, filed Jul. 1, 2013; 35 pages. |
Office Action dated Oct. 29, 2014; U.S. Appl. No. 13/937,444, filed Jul. 9, 2013; 28 pages. |
European Extended Search Report; Application No. 14178207.8; Dec. 23, 2014; 6 pages. |
European Extended Search Report; Application No. 14183709.6; Jan. 26, 2015; 7 pages. |
Office Action dated Jun. 2, 2015; U.S. Appl. No. 13/932,487, filed Jul. 1, 2013; 47 pages. |
Final Office Action dated Mar. 4, 2015; U.S. Appl. No. 13/932,260, filed Jul. 1, 2013; 55 pages. |
Final Office Action dated Mar. 31, 2015; U.S. Appl. No. 13/937,444, filed Jul. 9, 2013; 20 pages. |
Office Action dated May 14, 2015; U.S. Appl. No. 13/949,748, filed Jul. 24, 2013; 50 pages. |
Notice of Allowance dated Nov. 6, 2015; U.S. Appl. No. 13/932,470, filed Jul. 1, 2013; 13 pages. |
Final Office Action dated Sep. 8, 2015; U.S. Appl. No. 13/932,243, filed Jul. 1, 2013; 14 pages. |
Notice of Allowance dated Sep. 29, 2015; U.S. Appl. No. 13/932,487, filed Jul. 1, 2013; 16 pages. |
Final Office Action dated Nov. 24, 2015; U.S. Appl. No. 13/932,260, filed Jul. 1, 2013; 36 pages. |
Advisory Action dated Sep. 10, 2015; U.S. Appl. No. 13/932,271, filed Jul. 1, 2013; 3 pages. |
Office Action dated Nov. 4, 2015; U.S. Appl. No. 13/932,271, filed Jul. 1, 2013; 21 pages. |
Office Action dated Oct. 9, 2015; U.S. Appl. No. 13/932,280, filed Jul. 1, 2013; 13 pages. |
Office Action dated Sep. 18, 2015; U.S. Appl. No. 13/937,444, filed Jul. 9, 2013; 18 pages. |
Final Office Action dated Nov. 20, 2015; U.S. Appl. No. 13/949,748, filed Jul. 24, 2013; 19 pages. |
Office Action dated Jun. 30, 2015; U.S. Appl. No. 13/932,470, filed Jul. 1, 2013; 51 pages. |
Office Action dated Jun. 18, 2015; U.S. Appl. No. 13/932,235, filed Jul. 1, 2013; 41 pages. |
Final Office Action dated Jun. 5, 2015; U.S. Appl. No. 13/932,243, filed Jul. 1, 2013; 10 pages. |
Office Action dated Jun. 11, 2015; U.S. Appl. No. 13/932,250, filed Jul. 1, 2013; 53 pages. |
Office Action dated Jul. 27, 2015; U.S. Appl. No. 13/932,260, filed Jul. 1, 2013; 70 pages. |
Final Office Action dated Jun. 18, 2015; U.S. Appl. No. 13/932,271, filed Jul. 1, 2013; 34 pages. |
Office Action dated Jun. 29, 2015; U.S. Appl. No. 13/932,280, filed Jul. 1, 2013; 45 pages. |
Advisory Action dated Jun. 8, 2015; U.S. Appl. No. 13/937,444, filed Jul. 9, 2013; 6 pages. |
Notice of Allowance dated Jul. 22, 2015; U.S. Appl. No. 14/019,740, filed Sep. 6, 2013; 39 pages. |
Final Office Action dated Jan. 20, 2016; U.S. Appl. No. 13/932,235, filed Jul. 1, 2013; 16 pages. |
Notice of Allowance dated Jan. 11, 2016; U.S. Appl. No. 13/932,243, filed Jul. 1, 2013; 25 pages. |
Final Office Action dated Dec. 21, 2015; U.S. Appl. No. 13/932,250, filed Jul. 1, 2013; 31 pages. |
Advisory Action dated Mar. 2, 2016; U.S. Appl. No. 13/932,250, filed Jul. 1, 2013; 3 pages. |
Advisory Action dated Feb. 9, 2016; U.S. Appl. No. 13/932,260, filed Jul. 1, 2013; 8 pages. |
Notice of Allowance dated Feb. 17, 2016; U.S. Appl. No. 13/932,280, filed Jul. 1, 2013; 12 pages. |
Notice of Allowance dated Mar. 18, 2016; U.S. Appl. No. 13/937,444, filed Jul. 9, 2013; 15 pages. |
Notice of Allowance dated Feb. 1, 2016; U.S. Appl. No. 13/949,748, filed Jul. 24, 2013; 13 pages. |
European Examination Report; Application No. 13174565.5; Feb. 18, 2016; 8 pages. |
Mankowski, Peter; U.S. Appl. No. 15/142,944, filed Apr. 29, 2016; Title: Password by Touch-Less Gesture; 47 pages. |
Notice of Allowance dated Apr. 5, 2016; U.S. Appl. No. 13/932,235, filed Jul. 1, 2013; 8 pages. |
Advisory Action dated Apr. 26, 2016; U.S. Appl. No. 13/932,250, filed Jul. 1, 2013; 5 pages. |
Notice of Allowance dated Mar. 21, 2016; U.S. Appl. No. 13/932,260, filed Jul. 1, 2013; 68 pages. |
Mankowski, Peter, et al.; U.S. Appl. No. 15/243,567, filed Aug. 22; Title: Performance Control of Ambient Light Sensors; 45 pages. |
Office Action dated Jun. 23, 2016; U.S. Appl. No. 13/932,250, filed Jul. 1, 2013; 38 pages. |
Notice of Allowance dated Jun. 20, 2016; U.S Appl. No. 13/932,271, filed Jul. 1, 2013; 16 pages. |
Number | Date | Country | |
---|---|---|---|
20150028186 A1 | Jan 2015 | US |