Virtual button characterization engine

[0001] The present disclosure claims priority to U.S. Provisional Patent Application Ser. No. 62/937,555, filed Nov. 19, 2019, which is incorporated by reference herein in its entirety. The present disclosure also relates to U.S. patent application Ser. No. 16/267,079, filed Feb. 4, 2019, and U.S. patent application Ser. No. 16/422,543, filed May 24, 2019, both of which are incorporated by reference herein in their entireties.

[0002] The present disclosure relates in general to electronic devices with user interfaces, (e.g., mobile devices, game controllers, instrument panels, etc.), and more particularly, an integrated haptic system for use in a system for mechanical button replacement in a mobile device, for use in haptic feedback for capacitive sensors, and/or other suitable applications.

[0003] Many traditional mobile devices (e.g., mobile phones, personal digital assistants, video game controllers, etc.) include mechanical buttons to allow for interaction between a user of a mobile device and the mobile device itself. However, such mechanical buttons are susceptible to aging, wear, and tear that may reduce the useful life of a mobile device and/or may require significant repair if malfunction occurs. Also, the presence of mechanical buttons may render it difficult to manufacture mobile devices to be waterproof. Accordingly, mobile device manufacturers are increasingly looking to equip mobile devices with virtual buttons that act as a human-machine interface allowing for interaction between a user of a mobile device and the mobile device itself. Similarly, mobile device manufacturers are increasingly looking to equip mobile devices with other virtual interface areas (e.g., a virtual slider, interface areas of a body of the mobile device other than a touch screen, etc.). Ideally, for best user experience, such virtual interface areas should look and feel to a user as if a mechanical button or other mechanical interface were present instead of a virtual button or virtual interface area.

[0004] Presently, linear resonant actuators (LRAs) and other vibrational actuators (e.g., rotational actuators, vibrating motors, etc.) are increasingly being used in mobile devices to generate vibrational feedback in response to user interaction with human-machine interfaces of such devices. Typically, a sensor (traditionally a force or pressure sensor) detects user interaction with the device (e.g., a finger press on a virtual button of the device) and in response thereto, the linear resonant actuator may vibrate to provide feedback to the user. For example, a linear resonant actuator may vibrate in response to user interaction with the human-machine interface to mimic to the user the feel of a mechanical button click.

[0005] However, there is a need in the industry for sensors to detect user interaction with a human-machine interface, wherein such sensors provide acceptable levels of sensor sensitivity, power consumption, and size. For example, one challenge in the implementation of a virtual button is the accurate discrimination between actual user interaction with the virtual button and anomalous sensor inputs such as those caused by force sensor drift and/or device bending.

[0006] In accordance with the teachings of the present disclosure, the disadvantages and problems associated with use of a virtual button in a mobile device may be reduced or eliminated.

[0007] In accordance with embodiments of the present disclosure, a method may include receiving an input signal from a force sensor configured to sense a force associated with a human interaction with a virtual button, comparing the input signal to at least one behavioral model, the at least one behavioral model comprising one or more parameters associated with a valid human interaction with the virtual button, and determining whether a valid human interaction with the virtual button occurred based on the comparing.

[0008] In accordance with these and other embodiments of the present disclosure, a system may include an input for receiving an input signal from a force sensor configured to sense a force associated with a human interaction with a virtual button and a button characterization engine configured to compare the input signal to at least one behavioral model, the at least one behavioral model comprising one or more parameters associated with a valid human interaction with the virtual button and determine whether a valid human interaction with the virtual button occurred based on the comparing.

[0009] Technical advantages of the present disclosure may be readily apparent to one having ordinary skill in the art from the figures, description and claims included herein. The objects and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims.

[0010] It is to be understood that both the foregoing general description and the following detailed description are examples and explanatory and are not restrictive of the claims set forth in this disclosure.

[0024] FIG. 1 illustrates a block diagram of selected components of an example mobile device 102, in accordance with embodiments of the present disclosure. As shown in FIG. 1, mobile device 102 may comprise an enclosure 101, a controller 103, a memory 104, a force sensor 105, a microphone 106, a linear resonant actuator 107, a radio transmitter/receiver 108, a speaker 110, an integrated haptic system 112, and a resonant phase sensing system 113.

[0025] Enclosure 101 may comprise any suitable housing, casing, or other enclosure for housing the various components of mobile device 102. Enclosure 101 may be constructed from plastic, metal, and/or any other suitable materials. In addition, enclosure 101 may be adapted (e.g., sized and shaped) such that mobile device 102 is readily transported on a person of a user of mobile device 102. Accordingly, mobile device 102 may include but is not limited to a smart phone, a tablet computing device, a handheld computing device, a personal digital assistant, a notebook computer, a video game controller, or any other device that may be readily transported on a person of a user of mobile device 102.

[0026] Controller 103 may be housed within enclosure 101 and may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data, and may include, without limitation a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data. In some embodiments, controller 103 interprets and/or executes program instructions and/or processes data stored in memory 104 and/or other computer-readable media accessible to controller 103.

[0027] Memory 104 may be housed within enclosure 101, may be communicatively coupled to controller 103, and may include any system, device, or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media). Memory 104 may include random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a Personal Computer Memory Card International Association (PCMCIA) card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to mobile device 102 is turned off.

[0028] Microphone 106 may be housed at least partially within enclosure 101, may be communicatively coupled to controller 103, and may comprise any system, device, or apparatus configured to convert sound incident at microphone 106 to an electrical signal that may be processed by controller 103, wherein such sound is converted to an electrical signal using a diaphragm or membrane having an electrical capacitance that varies as based on sonic vibrations received at the diaphragm or membrane. Microphone 106 may include an electrostatic microphone, a condenser microphone, an electret microphone, a microelectromechanical systems (MEMs) microphone, or any other suitable capacitive microphone.

[0029] Radio transmitter/receiver 108 may be housed within enclosure 101, may be communicatively coupled to controller 103, and may include any system, device, or apparatus configured to, with the aid of an antenna, generate and transmit radio-frequency signals as well as receive radio-frequency signals and convert the information carried by such received signals into a form usable by controller 103. Radio transmitter/receiver 108 may be configured to transmit and/or receive various types of radio-frequency signals, including without limitation, cellular communications (e.g., 2G, 3G, 4G, LTE, etc.), short-range wireless communications (e.g., BLUETOOTH), commercial radio signals, television signals, satellite radio signals (e.g., GPS), Wireless Fidelity, etc.

[0030] A speaker 110 may be housed at least partially within enclosure 101 or may be external to enclosure 101, may be communicatively coupled to controller 103, and may comprise any system, device, or apparatus configured to produce sound in response to electrical audio signal input. In some embodiments, a speaker may comprise a dynamic loudspeaker, which employs a lightweight diaphragm mechanically coupled to a rigid frame via a flexible suspension that constrains a voice coil to move axially through a cylindrical magnetic gap. When an electrical signal is applied to the voice coil, a magnetic field is created by the electric current in the voice coil, making it a variable electromagnet. The coil and the driver's magnetic system interact, generating a mechanical force that causes the coil (and thus, the attached cone) to move back and forth, thereby reproducing sound under the control of the applied electrical signal coming from the amplifier.

[0031] Force sensor 105 may be housed within enclosure 101, and may include any suitable system, device, or apparatus for sensing a force, a pressure, or a touch (e.g., an interaction with a human finger) and generating an electrical or electronic signal in response to such force, pressure, or touch. In some embodiments, such electrical or electronic signal may be a function of a magnitude of the force, pressure, or touch applied to the force sensor. In these and other embodiments, such electronic or electrical signal may comprise a general purpose input/output signal (GPIO) associated with an input signal to which haptic feedback is given. Force sensor 105 may include, without limitation, a capacitive displacement sensor, an inductive force sensor (e.g., a resistive-inductive-capacitive sensor), a strain gauge, a piezoelectric force sensor, force sensing resistor, piezoelectric force sensor, thin film force sensor, or a quantum tunneling composite-based force sensor. For purposes of clarity and exposition in this disclosure, the term “force” as used herein may refer not only to force, but to physical quantities indicative of force or analogous to force, such as, but not limited to, pressure and touch.

[0032] Linear resonant actuator 107 may be housed within enclosure 101, and may include any suitable system, device, or apparatus for producing an oscillating mechanical force across a single axis. For example, in some embodiments, linear resonant actuator 107 may rely on an alternating current voltage to drive a voice coil pressed against a moving mass connected to a spring. When the voice coil is driven at the resonant frequency of the spring, linear resonant actuator 107 may vibrate with a perceptible force. Thus, linear resonant actuator 107 may be useful in haptic applications within a specific frequency range. While, for the purposes of clarity and exposition, this disclosure is described in relation to the use of linear resonant actuator 107, it is understood that any other type or types of vibrational actuators (e.g., eccentric rotating mass actuators) may be used in lieu of or in addition to linear resonant actuator 107. In addition, it is also understood that actuators arranged to produce an oscillating mechanical force across multiple axes may be used in lieu of or in addition to linear resonant actuator 107. As described elsewhere in this disclosure, a linear resonant actuator 107, based on a signal received from integrated haptic system 112, may render haptic feedback to a user of mobile device 102 for at least one of mechanical button replacement and capacitive sensor feedback.

[0033] Integrated haptic system 112 may be housed within enclosure 101, may be communicatively coupled to force sensor 105 and linear resonant actuator 107, and may include any system, device, or apparatus configured to receive a signal from force sensor 105 indicative of a force applied to mobile device 102 (e.g., a force applied by a human finger to a virtual button of mobile device 102) and generate an electronic signal for driving linear resonant actuator 107 in response to the force applied to mobile device 102. Detail of an example integrated haptic system in accordance with embodiments of the present disclosure is depicted in FIG. 2.

[0034] Resonant phase sensing system 113 may be housed within enclosure 101, may be communicatively coupled to force sensor 105 and linear resonant actuator 107, and may include any system, device, or apparatus configured to detect a displacement of a mechanical member (e.g., mechanical member 305 depicted in FIGS. 3A and 3B, below) indicative of a physical interaction (e.g., by a user of mobile device 102) with the human-machine interface of mobile device 102 (e.g., a force applied by a human finger to a virtual interface of mobile device 102). As described in greater detail below, resonant phase sensing system 113 may detect displacement of such mechanical member by performing resonant phase sensing of a resistive-inductive-capacitive sensor for which an impedance (e.g., inductance, capacitance, and/or resistance) of the resistive-inductive-capacitive sensor changes in response to displacement of the mechanical member. Thus, displacement of the mechanical member may cause a change in an impedance of a resistive-inductive-capacitive sensor integral to resonant phase sense system 113. Resonant phase sensing system 113 may also generate an electronic signal to integrated haptic system 112 to which integrated haptic system 112 may respond by driving linear resonant actuator 107 in response to a physical interaction associated with a human-machine interface associated with the mechanical member. Detail of an example resonant phase sensing system 113 in accordance with embodiments of the present disclosure is depicted in greater detail below.

[0035] Although specific example components are depicted above in FIG. 1 as being integral to mobile device 102 (e.g., controller 103, memory 104, force sensor 105, microphone 105, radio transmitter/receiver 108, speakers(s) 110), a mobile device 102 in accordance with this disclosure may comprise one or more components not specifically enumerated above. For example, although FIG. 1 depicts certain user interface components, mobile device 102 may include one or more other user interface components in addition to those depicted in FIG. 1 (including but not limited to a keypad, a touch screen, and a display), thus allowing a user to interact with and/or otherwise manipulate mobile device 102 and its associated components.

[0036] FIG. 2 illustrates a block diagram of selected components of an example integrated haptic system 112A, in accordance with embodiments of the present disclosure. In some embodiments, integrated haptic system 112A may be used to implement integrated haptic system 112 of FIG. 1. As shown in FIG. 2, integrated haptic system 112A may include a digital signal processor (DSP) 202, a memory 204, and an amplifier 206.

[0037] DSP 202 may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data. In some embodiments, DSP 202 may interpret and/or execute program instructions and/or process data stored in memory 204 and/or other computer-readable media accessible to DSP 202.

[0038] Memory 204 may be communicatively coupled to DSP 202, and may include any system, device, or apparatus configured to retain program instructions and/or data for a period of time (e.g., computer-readable media). Memory 204 may include random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a Personal Computer Memory Card International Association (PCMCIA) card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to mobile device 102 is turned off.

[0039] Amplifier 206 may be electrically coupled to DSP 202 and may comprise any suitable electronic system, device, or apparatus configured to increase the power of an input signal V_IN (e.g., a time-varying voltage or current) to generate an output signal V_OUT. For example, amplifier 206 may use electric power from a power supply (not explicitly shown) to increase the amplitude of a signal. Amplifier 206 may include any suitable amplifier class, including without limitation, a Class-D amplifier.

[0040] In operation, memory 204 may store one or more haptic playback waveforms. In some embodiments, each of the one or more haptic playback waveforms may define a haptic response a(t) as a desired acceleration of a linear resonant actuator (e.g., linear resonant actuator 107) as a function of time. DSP 202 may be configured to receive a force signal V_SENSE from resonant phase sensing system 113 indicative of force applied to force sensor 105. Either in response to receipt of force signal V_SENSE indicating a sensed force or independently of such receipt, DSP 202 may retrieve a haptic playback waveform from memory 204 and process such haptic playback waveform to determine a processed haptic playback signal V_IN. In embodiments in which amplifier 206 is a Class D amplifier, processed haptic playback signal V_IN may comprise a pulse-width modulated signal. In response to receipt of force signal V_SENSE indicating a sensed force, DSP 202 may cause processed haptic playback signal V_IN to be output to amplifier 206, and amplifier 206 may amplify processed haptic playback signal V_IN to generate a haptic output signal V_OUT for driving linear resonant actuator 107.

[0041] In some embodiments, integrated haptic system 112A may be formed on a single integrated circuit, thus enabling lower latency than existing approaches to haptic feedback control. By providing integrated haptic system 112A as part of a single monolithic integrated circuit, latencies between various interfaces and system components of integrated haptic system 112A may be reduced or eliminated.

[0042] FIG. 3A illustrates a mechanical member 305 embodied as a metal plate separated by a distance d from an inductive coil 302, in accordance with embodiments of the present disclosure. Mechanical member 305 may comprise any suitable system, device, or apparatus which all or a portion thereof may displace, wherein such displacement affects an electrical property (e.g., inductance, capacitance, etc.) of the mechanical member 305 or another electrical component in electrical communication (e.g., via a mutual inductance) with mechanical member 305.

[0043] FIG. 3B illustrates selected components of an inductive sensing system 300 that may be implemented by force sensor 105 and/or resonant phase sensing system 113, in accordance with embodiments of the present disclosure. As shown in FIG. 3, inductive sensing system 300 may include mechanical member 305, modeled as a variable electrical resistance 304 and a variable electrical inductance 306, and may include inductive coil 302 in physical proximity to mechanical member 305 such that inductive coil 302 has a mutual inductance with mechanical member 305 defined by a variable coupling coefficient k. As shown in FIG. 3, inductive coil 302 may be modeled as a variable electrical inductance 308 and a variable electrical resistance 310.

[0044] In operation, as a current I flows through inductive coil 302, such current may induce a magnetic field which in turn may induce an eddy current inside mechanical member 305. When a force is applied to and/or removed from mechanical member 305, which alters distance d between mechanical member 305 and inductive coil 302, the coupling coefficient k, variable electrical resistance 304, and/or variable electrical inductance 306 may also change in response to the change in distance. These changes in the various electrical parameters may, in turn, modify an effective impedance Z_L of inductive coil 302.

[0045] FIG. 4 illustrates a diagram of selected components of an example system 400 for performing resonant phase sensing, in accordance with embodiments of the present disclosure. In some embodiments, system 400 may be used to implement resonant phase sensing system 113 of FIG. 1. As shown FIG. 4, system 400 may include a resistive-inductive-capacitive sensor 402 and a processing integrated circuit (IC) 412. In some embodiments, resistive-inductive-capacitive sensor 402 may implement all or a portion of force sensor 105 and processing integrated circuit (IC) 412 may implement all or a portion of resonant phase sensing system 113.

[0046] As shown in FIG. 4, resistive-inductive-capacitive sensor 402 may include mechanical member 305, inductive coil 302, a resistor 404, and capacitor 406, wherein mechanical member 305 and inductive coil 302 have a variable coupling coefficient k. Although shown in FIG. 4 to be arranged in parallel with one another, it is understood that inductive coil 302, resistor 404, and capacitor 406 may be arranged in any other suitable manner that allows resistive-inductive-capacitive sensor 402 to act as a resonant tank. For example, in some embodiments, inductive coil 302, resistor 404, and capacitor 406 may be arranged in series with one another. In some embodiments, resistor 404 may not be implemented with a stand-alone resistor, but may instead be implemented by a parasitic resistance of inductive coil 302, a parasitic resistance of capacitor 406, and/or any other suitable parasitic resistance.

[0047] Processing IC 412 may be communicatively coupled to resistive-inductive-capacitive sensor 402 and may comprise any suitable system, device, or apparatus configured to implement a measurement circuit to measure phase information associated with resistive-inductive-capacitive sensor 402 and based on the phase information, determine a displacement of mechanical member 305 relative to resistive-inductive-capacitive sensor 402. Thus, processing IC 412 may be configured to determine an occurrence of a physical interaction (e.g., press or release of a virtual button) associated with a human-machine interface associated with mechanical member 305 based on the phase information.

[0048] As shown in FIG. 4, processing IC 412 may include a phase shifter 410, a voltage-to-current converter 408, a preamplifier 440, an intermediate frequency mixer 442, a combiner 444, a programmable gain amplifier (PGA) 414, a voltage-controlled oscillator (VCO) 416, a phase shifter 418, an amplitude and phase calculation block 431, a DSP 432, a low-pass filter 434, a combiner 450, and a button characterization engine 452. Processing IC 412 may also include a coherent incident/quadrature detector implemented with an incident channel comprising a mixer 420, a low-pass filter 424, and an analog-to-digital converter (ADC) 428, and a quadrature channel comprising a mixer 422, a low-pass filter 426, and an ADC 430 such that processing IC 412 is configured to measure the phase information using the coherent incident/quadrature detector.

[0049] Phase shifter 410 may include any system, device, or apparatus configured to detect an oscillation signal generated by processing IC 412 (as explained in greater detail below) and phase shift such oscillation signal (e.g., by 45 degrees) such that a normal operating frequency of system 400, an incident component of a sensor signal ϕ generated by pre-amplifier 440 is approximately equal to a quadrature component of sensor signal ϕ, so as to provide common mode noise rejection by a phase detector implemented by processing IC 412, as described in greater detail below.

[0050] Voltage-to-current converter 408 may receive the phase shifted oscillation signal from phase shifter 410, which may be a voltage signal, convert the voltage signal to a corresponding current signal, and drive the current signal on resistive-inductive-capacitive sensor 402 at a driving frequency with the phase-shifted oscillation signal in order to generate sensor signal ϕ which may be processed by processing IC 412, as described in greater detail below. In some embodiments, a driving frequency of the phase-shifted oscillation signal may be selected based on a resonant frequency of resistive-inductive-capacitive sensor 402 (e.g., may be approximately equal to the resonant frequency of resistive-inductive-capacitive sensor 402).

[0051] Preamplifier 440 may receive sensor signal ϕ and condition sensor signal ϕ for frequency mixing, with mixer 442, to an intermediate frequency Δf combined by combiner 444 with an oscillation frequency generated by VCO 416, as described in greater detail below, wherein intermediate frequency Δf is significantly less than the oscillation frequency. In some embodiments, preamplifier 440, mixer 442, and combiner 444 may not be present, in which case PGA 414 may receive sensor signal ϕ directly from resistive-inductive-capacitive sensor 402. However, when present, preamplifier 440, mixer 442, and combiner 444 may allow for mixing sensor signal ϕ down to a lower intermediate frequency Δf which may allow for lower-bandwidth and more efficient ADCs (e.g., ADCs 428 and 430 of FIGS. 4A and 4B and ADC 429 of FIG. 4C, described below) and/or which may allow for minimization of phase and/or gain mismatches in the incident and quadrature paths of the phase detector of processing IC 412.

[0052] In operation, PGA 414 may further amplify sensor signal ϕ to condition sensor signal ϕ for processing by the coherent incident/quadrature detector. VCO 416 may generate an oscillation signal to be used as a basis for the signal driven by voltage-to-current converter 408, as well as the oscillation signals used by mixers 420 and 422 to extract incident and quadrature components of amplified sensor signal ϕ. As shown in FIG. 4, mixer 420 of the incident channel may use an unshifted version of the oscillation signal generated by VCO 416, while mixer 422 of the quadrature channel may use a 90-degree shifted version of the oscillation signal phase shifted by phase shifter 418. As mentioned above, the oscillation frequency of the oscillation signal generated by VCO 416 may be selected based on a resonant frequency of resistive-inductive-capacitive sensor 402 (e.g., may be approximately equal to the resonant frequency of resistive-inductive-capacitive sensor 402).

[0053] In the incident channel, mixer 420 may extract the incident component of amplified sensor signal ϕ, low-pass filter 424 may filter out the oscillation signal mixed with the amplified sensor signal ϕ to generate a direct current (DC) incident component, and ADC 428 may convert such DC incident component into an equivalent incident component digital signal for processing by amplitude and phase calculation block 431. Similarly, in the quadrature channel, mixer 422 may extract the quadrature component of amplified sensor signal ϕ, low-pass filter 426 may filter out the phase-shifted oscillation signal mixed with the amplified sensor signal ϕ to generate a direct current (DC) quadrature component, and ADC 430 may convert such DC quadrature component into an equivalent quadrature component digital signal for processing by amplitude and phase calculation block 431.

[0054] Amplitude and phase calculation block 431 may include any system, device, or apparatus configured to receive phase information comprising the incident component digital signal and the quadrature component digital signal and based thereon, extract amplitude and phase information.

[0055] DSP 432 may include any system, device, or apparatus configured to interpret and/or execute program instructions and/or process data. In particular, DSP 432 may receive the phase information and the amplitude information generated by amplitude and phase calculation block 431 and based thereon, determine a displacement of mechanical member 305 relative to resistive-inductive-capacitive sensor 402, which may be indicative of an occurrence of a physical interaction (e.g., press or release of a virtual button or other interaction with a virtual interface) associated with a human-machine interface associated with mechanical member 305 based on the phase information. DSP 432 may also generate an output signal indicative of the displacement. In some embodiments, such output signal may comprise a control signal for controlling mechanical vibration of linear resonant actuator 107 in response to the displacement.

[0056] The phase information generated by amplitude and phase calculation block 431 may be subtracted from a reference phase ϕ_ref by combiner 450 in order to generate an error signal that may be received by low-pass filter 434. Low-pass filter 434 may low-pass filter the error signal, and such filtered error signal may be applied to VCO 416 to modify the frequency of the oscillation signal generated by VCO 416, in order to drive sensor signal ϕ towards reference phase ϕ_ref. As a result, sensor signal ϕ may comprise a transient decaying signal in response to a “press” of a virtual button (or other interaction with a virtual interface) associated with system 400 as well as another transient decaying signal in response to a subsequent “release” of the virtual button (or other interaction with a virtual interface). Accordingly, low-pass filter 434 in connection with VCO 416 may implement a feedback control loop that may track changes in operating parameters of system 400 by modifying the driving frequency of VCO 416.

[0057] Button characterization engine 452 may comprise any system, device, or apparatus configured to apply one or more behavior models to received force sensor information, in order to discriminate between valid user interactions with force sensor 105/mechanical member 305 and anomalous force sensor 105/mechanical member 305 inputs, such as those caused by drift of physical parameters of force sensor 105, mechanical member 305, resonant phase sensing system 113, etc., and/or due to atypical forces upon mobile device 102 such as bending or twisting. Although FIG. 4 depicts that, in some embodiments, button characterization engine 452 is external to DSP 432, in some embodiments, functionality of button characterization engine 452 may be implemented in whole or part by DSP 432.

[0058] Although the foregoing contemplates use of closed-loop feedback for sensing of displacement, the various embodiments represented by FIG. 4 may be modified to implement an open-loop system for sensing of displacement. In such an open-loop system, a processing IC may include no feedback path from amplitude and phase calculation block 431 to VCO 416 or variable phase shifter 418 and thus may also lack a feedback low-pass filter 434. Thus, a phase measurement may still be made by comparing a change in phase to a reference phase value, but the oscillation frequency driven by VCO 416 may not be modified or the phase shifted by variable phase shifter 418 may not be shifted.

[0059] Although the foregoing contemplates use of a coherent incident/quadrature detector as a phase detector for determining phase information associated with resistive-inductive-capacitive sensor 402, a resonant phase sensing system 112 may perform phase detection and/or otherwise determine phase information associated with resistive-inductive-capacitive sensor 402 in any suitable manner, including, without limitation, using only one of the incident path or quadrature path to determine phase information.

[0060] In some embodiments, an incident/quadrature detector as disclosed herein may include one or more frequency translation stages that translate the sensor signal into direct-current signal directly or into an intermediate frequency signal and then into a direct-current signal. Any of such frequency translation stages may be implemented either digitally after an analog-to-digital converter stage or in analog before an analog-to-digital converter stage.

[0061] In addition, although the foregoing contemplates measuring changes in resistance and inductance in resistive-inductive-capacitive sensor 402 caused by displacement of mechanical member 305, other embodiments may operate based on a principle that any change in impedance based on displacement of mechanical member 305 may be used to sense displacement. For example, in some embodiments, displacement of mechanical member 305 may cause a change in a capacitance of resistive-inductive-capacitive sensor 402, such as if mechanical member 305 included a metal plate implementing one of the capacitive plates of capacitor 406.

[0062] Although DSP 432 may be capable of processing phase information to make a binary determination of whether physical interaction associated with a human-machine interface associated with mechanical member 305 has occurred and/or ceased to occur, in some embodiments, DSP 432 may quantify a duration of a displacement of mechanical member 305 to more than one detection threshold, for example to detect different types of physical interactions (e.g., a short press of a virtual button versus a long press of the virtual button). In these and other embodiments, DSP 432 may quantify a magnitude of the displacement to more than one detection threshold, for example to detect different types of physical interactions (e.g., a light press of a virtual button versus a quick and hard press of the virtual button).

[0063] Although FIG. 4 and the description thereof depicts particular embodiments of a resonant phase sensing system, other architectures for force sensing may be used consistent with this disclosure, including without limitation the various resonant phase sensing system architectures described in U.S. patent application Ser. No. 16/267,079, filed Feb. 4, 2019. Thus, while button characterization engine 452 is discussed herein in relation to operation in connection with a resonant phase sensing system, button characterization engine 452 may be used with any other suitable force sensing system.

[0064] FIG. 5 illustrates a diagram of selected components of an example button characterization engine 500, in accordance with embodiments of the present disclosure. In some embodiments, button characterization engine 500 as shown in FIG. 5 may implement all or a portion of button characterization engine 452 depicted in FIG. 4.

[0065] In operation, button characterization engine 500 may receive an input comprising force sensor data from a force sensing system indicative of a force applied to a virtual button. For example, in the resonance phase sensing system described above, the input may comprise a phase measurement. Button characterization engine 500 may compare the received input against one or more stored behavioral models 502, wherein each behavioral model 502 is indicative of actual valid user interactions with a virtual button, to determine if the received input is a valid user interaction.

[0066] In some embodiments, button characterization engine 500 may, using a comparative analysis module 506, compare the received force sensor data input against a historical record 504 of received input, and against at least one stored behavioral model 502. Based on such comparative analysis, button characterization engine 500 may generate a plurality of different behavior scores 508 providing an indication of the validity of the received input, each behavior score related to a different user behavior (e.g., different type of user touch event). The different scores may be used as input to a confidence level module 510, which may combine or fuse the different scores to generate an indication of the confidence that the received input is a valid input relating to an actual user interaction or not. Based on the confidence level, which may in some embodiments be compared to a relevant threshold, result generation module 512 of button characterization engine 500 may output an indication (e.g., to DSP 432 or other processing module) whether or not a valid user interaction with a virtual button has occurred. In addition, based on the confidence level, button characterization engine 500 may perform learning and/or adaptation, in order to update or enrich at least one of the stored behavioral models 502, to provide an improved model of user interaction with a virtual button or device comprising the virtual button.

[0067] To further illustrate, confidence level module 510 may calculate a confidence score (e.g., score of 100 indicative of certain intentional user interaction; score of 0 indicative of certain user non-interaction), based on historical record 504, behavioral models 502, and/or other factors (e.g., gradient of user interaction, as described with reference to FIGS. 10 and 11, below).

[0068] As shown in FIG. 5, in some embodiments, button characterization engine 500 may receive input from other sensors of a device other than force sensor data of the virtual button, which may be used in selection of behavioral models 502 and/or comparative analysis. In some of such embodiments, the input from other sensors may include data regarding user interaction with other mechanical buttons and/or virtual buttons of the device.

[0069] Example functionality of button characterization engine 500 may be described in FIGS. 6 through 11, below.

[0070] FIG. 6 illustrates a behavioral model 502A represented by graph of phase versus time depicting a measured phase input signal being compared against a model of a window of valid phases for a user interaction event with a virtual button over time, in accordance with embodiments of the present disclosure. In behavioral model 502A, a window of between 20 and 100 milliseconds may be defined for a force sensor data input signal to reach a measured phase threshold for a valid user interaction. Thus, if the force sensor data input signal reaches such a level within the defined window of time, button characterization engine 500 may determine that a valid user interaction event has occurred, and in response output an appropriate signal or flag (e.g., to DSP 432 or other processing module) indicative of the occurrence of a valid user interaction event. An initial algorithm may specify a relatively large valid time window around a button press to accommodate a large variety of users and press preferences.

[0071] As described above, button characterization engine 500 may be configured to adaptively update one or more behavioral models 502 over time, based on, among other things, a history of valid user interaction events. For example, if user interaction events generally follow the line shown in FIG. 6, button characterization engine 500 may update stored behavior model 502A to better accommodate such user interactions.

[0072] In some embodiments, behavioral models 502 may be created on a per-user basis to track usage history for a plurality of users. For example, user identity may be determined based on a user's login credential information (e.g., biometric recognition, passcode, etc.) and historical record 504 and behavioral models 502 may be created for each particular user of a device, to individually tailor user interaction determination to each individual user.

[0073] For example, FIG. 7 illustrates updating of behavioral model 502A shown in FIG. 6, in accordance with embodiments of the present disclosure. As shown in FIG. 7, button characterization engine 500 may update behavioral model 502A to re-center the valid window of user interactions based on historical user interaction. In the particular example of FIG. 7, the valid window is updated to be defined by a window of between 15 and 40 milliseconds, which may provide a more accurate representation of a particular user's interaction with a device. Thus, button characterization engine 500 may effectively learn a user's virtual button interaction speed over time, and modify the valid window of behavioral model 502A in order to improve the button press detection margin and user experience.

[0074] Another example behavioral model 502 may be based at least in part on a derivative with respect to time of a force sensor data input signal. To that end, FIG. 8 illustrates a graph of a measured phase versus time and a behavioral model 502B, depicting a time derivative of a measured phase input signal for a valid user interaction being compared against a model of a window of valid rates of change of phases for a user interaction event with a virtual button over time, in accordance with embodiments of the present disclosure.

[0075] In the upper plot of FIG. 8, phase characteristics of an example user interaction with a virtual button may be illustrated, wherein a measured phase input signal exceeds a threshold indicative of a valid user interaction. The lower plot of FIG. 8 depicts a time derivative of such measured phase input signal, showing that a typical user interaction with a virtual button may decrease over time, allowing the time derivative of the input signal to be compared with an appropriate validity window of behavioral model 502B.

[0076] By contrast, FIG. 9 illustrates a graph of a measured phase versus time and behavioral model 502B, depicting a time derivative of a measured phase input signal for an invalid user interaction (e.g., as may occur as a result of sensor drift) being compared against a model of a window of valid rates of change of phases for a user interaction event with a virtual button over time, in accordance with embodiments of the present disclosure. In FIG. 9, while the measured phase input signal meets a relevant threshold, the time derivative of the measured phase input signal may be a constant value, and as a result can be easily seen to extend outside of the validity window of behavioral model 502B, thereby allowing button characterization engine 500 to determine that an invalid user interaction has occurred.

[0077] In these and other embodiments, button characterization engine 500 may be able to calculate any other function of an input force sensor data signal (e.g., a higher order derivative), and compare calculated values related to such function against an allowable validity window for that function.

[0078] In these and other embodiments, button characterization engine 500 may be configured to compare received force sensor data input against one or more behavioral models 502 relating to a consistency of the applied force. To illustrate, human pressure to a virtual button may not be applied with a steady force. In general, a standard deviation in a time derivative of a response due to human force may be both non-uniform and varied compared to one or more characteristic environmental factors (e.g., temperature effects).

[0079] For example, FIG. 10 depicts an example measured phase input signal that may result due to temperature effects, in accordance with embodiments of the present disclosure. As shown in FIG. 10, when accounting for system noise, the example measured phase input signal may have a uniform slope due to temperature effects on a force sensing system.

[0080] On the other hand, FIG. 11 depicts an example measured phase input signal that may result due to human interaction, in accordance with embodiments of the present disclosure. As shown in FIG. 11, the example measured phase input signal may have a slope with a non-uniform gradient in response to a valid user interaction with a virtual button.

[0081] Notably, when comparing FIGS. 10 and 11, while both measured phase input signals shown in these figures have a similar phase difference over time, button characterization engine 500 may differentiate valid human interaction from temperature and/or other environmental effects based on characteristic differences between the signals, such as the variance of slope over time. In some embodiments, button characterization engine 500 may use historical user interaction as embodied in behavioral models 502 (e.g., historical non-uniform effects related to a user) to differentiate valid human interaction from temperature and/or other environmental effects.

[0082] In addition to the various behaviors described above, button characterization engine 500 may use other behaviors, and associated behavioral models 502, to discriminate between valid and invalid user interaction events. For example, left-handed use versus right-handed use of a device with a virtual button may produce different measured responses across multiple sensors of a device. Indicia of handedness of a user may be used by button characterization engine 500 to enhance button detection and improve false reject rates. Similarly, use of different fingers (e.g., thumb versus other fingers) may also produce different sensor responses, which may also be used by button characterization engine 500 to enhance button detection.

[0083] As another example, button characterization engine 500 may use a measured phase relationship of a virtual button to other sensors to enhance button detection. For example, typical ambient conditions of a user or a device location may result in a measurable phase shift in addition to the desired phase response of a user interaction with a virtual button. Button characterization engine 500 may characterize and learn such information when compared to other sensor data. Examples of other sensors whose data may be used in conjunction with phase data may include adjacent sensor channels, temperature detected by a temperature sensor, gyroscopic forces from a gyroscopic sensor or accelerometer, capacitive sensors, and/or other sensors.

[0084] As a further example, a user may perform application-specific events with a specific rate, force, and time interval, such as a double click event. Button characterization engine 500 may detect a user's preferences related to application-specific events and update the detection criteria for enhanced user experience and/or latency for detection. Examples of application specific events may include: a single press, a double press, a long press, a multi-channel press, a force dependent threshold, a slide operation, etc.

[0085] Advantages of the systems and methods described herein are that history and behavioral models regarding a user's interaction with a device may be used to decrease a time needed to determine valid user interactions, thus potentially reducing latencies between user interactions and determination of the user interactions, thus potentially increasing user experience.

[0086] As used herein, when two or more elements are referred to as “coupled” to one another, such term indicates that such two or more elements are in electronic communication or mechanical communication, as applicable, whether connected indirectly or directly, with or without intervening elements.

[0087] This disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative. Accordingly, modifications, additions, or omissions may be made to the systems, apparatuses, and methods described herein without departing from the scope of the disclosure. For example, the components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses disclosed herein may be performed by more, fewer, or other components and the methods described may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order. As used in this document, “each” refers to each member of a set or each member of a subset of a set.

[0088] Although exemplary embodiments are illustrated in the figures and described below, the principles of the present disclosure may be implemented using any number of techniques, whether currently known or not. The present disclosure should in no way be limited to the exemplary implementations and techniques illustrated in the drawings and described above.

[0089] Unless otherwise specifically noted, articles depicted in the drawings are not necessarily drawn to scale.

[0090] All examples and conditional language recited herein are intended for pedagogical objects to aid the reader in understanding the disclosure and the concepts contributed by the inventor to furthering the art, and are construed as being without limitation to such specifically recited examples and conditions. Although embodiments of the present disclosure have been described in detail, it should be understood that various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the disclosure.

[0091] Although specific advantages have been enumerated above, various embodiments may include some, none, or all of the enumerated advantages. Additionally, other technical advantages may become readily apparent to one of ordinary skill in the art after review of the foregoing figures and description.

[0092] To aid the Patent Office and any readers of any patent issued on this application in interpreting the claims appended hereto, applicants wish to note that they do not intend any of the appended claims or claim elements to invoke 35 U.S.C. § 112(f) unless the words “means for” or “step for” are explicitly used in the particular claim.