The described embodiments relate generally to computing input devices. More particularly, the present embodiments relate to force- and/or touch-sensitive input devices having haptic feedback.
Traditional computing input devices, such as mice, keyboards, and trackpads, tend to operate using dedicated keys or buttons. The operation of each key or button may be tied to a particular function or command. However, traditional input devices lack the flexibility to accommodate expansive features offered by newer devices, operating systems, and software. As a further drawback, the dedicated keys or buttons of traditional input devices are unable to adapt to different user needs and preferences.
Alternative input devices, such as touch-input devices, appear to offer some greater flexibility for input scenarios and customization than mechanical keyboards, mice, and similar input devices. However, touch sensitive input devices often have a flat, inflexible input surface that gives little or no tactile feedback to a user and may therefore be less desirable for many scenarios than traditional input devices.
Therefore, improved input devices are needed to provide both greater flexibility and customizability while providing feedback to a user during operation.
An input device for an electronic device may include an enclosure and a top member coupled to the enclosure and defining an input surface having multiple differentiated input regions. The input device may further include a first force sensing system associated with a first area of the top member including a first group of the differentiated input regions, the first force sensing system configured to determine a first force associated with a first force input applied within the first area, and a second force sensing system associated with a second area of the top member including a second group of the differentiated input regions, the second force sensing system configured to determine a second force associated with a second force input applied within the second area. The input device may further include a touch sensing system configured to determine which input region from the first group of the differentiated input regions corresponds to the first force input and to determine which input region from the second group of the differentiated input regions corresponds to the second force input.
The first force sensing system may be configured to determine the first force independently of the second force sensing system. The first group of the differentiated input regions may correspond to keys typically selected by a first finger of a user's hand, and the second group of the differentiated input regions may correspond to keys typically selected by a second finger of the user's hand.
The multiple differentiated input regions may correspond to keys of a keyboard. The multiple differentiated input regions may be visually differentiated on the top member. The input device may be configured to detect a key press of a particular input region by detecting, within a given group of the differentiated input regions, both a touch location and a force value satisfying a force threshold. The input device may further comprise a haptic output system configured to produce a tactile output in response to detecting the key press.
The haptic output system may include a first actuator having a first actuation axis along a first direction and a second actuator having a second actuation axis along a second direction that is not parallel to the first direction. The input device may be configured to alternate between actuating the first actuator and the second actuator in response to detecting successive key presses.
The first and the second force sensing systems may be part of a group of force sensing systems, and the group of force sensing systems may define two rows of force sensing regions on the top member. The first and second groups of the differentiated input regions may be oriented substantially diagonally with respect to a longitudinal axis of the input device.
A keyboard for an electronic device includes an enclosure and a cover coupled to the enclosure and defining an input surface. The keyboard also includes a first actuator within the enclosure and coupled to the cover and a second actuator within the enclosure and coupled to the cover. The first actuator is configured to impart, to the cover, a first force along a first axis that is substantially parallel to the input surface, and the second actuator is configured to impart, to the cover, a second force along a second axis that is perpendicular to the first axis and substantially parallel to the input surface.
The first actuator may be configured to oscillate along the first axis to impart the first force to the cover, and the second actuator may be configured to oscillate along the second axis to impart the second force to the cover. The keyboard may further include a force sensing system within the enclosure and configured to detect the successive force inputs on the input regions.
The keyboard may be incorporated into an electronic device that includes a display coupled to the enclosure, wherein the display is distinct from the keyboard. The input surface may include input regions representing character input keys, and the first actuator and the second actuator may be configured to provide haptic feedback to a user to induce a sensation representative of a mechanical key. The keyboard may be configured to alternate between actuating the first actuator and the second actuator in response to successive force inputs on the input regions. The keyboard may also or instead be configured to actuate the first and second actuator substantially simultaneously (or such that the actuations of the first and second actuators overlap in time).
A force sensing system for an electronic device may include a cover defining an input surface comprising multiple input regions each corresponding to an input key. The cover may be configured to locally deform in response to an input force applied to an input region of the multiple input regions. The force sensing system may include a capacitive sense layer below the cover, a compliant material between the cover and the capacitive sense layer and below the input regions, and a processor electrically coupled to the capacitive sense layer. The processor may be configured to determine a force value of the input force based on a change in capacitance between the capacitive sense layer and an input member applied to the input region, and determine a location of the input force based on which of a set of electrodes detected the change in capacitance. The capacitive sense layer may include a set of electrodes each having an area that is the same or smaller than an area of the input regions. The force sensing system may be configured to differentiate between force inputs having centroids about 3.0 cm apart or less.
The force sensing system may be coupled to a lower portion of an enclosure of a notebook computer and may be configured as a keyboard for the notebook computer. The multiple input regions may be visually differentiated to define a keyboard for the notebook computer. The notebook computer may include a display coupled to an upper portion of the enclosure.
The cover may be formed from a glass. The glass may have an elastic modulus in a range of about 60 to about 80 GPa. The glass may have a thickness in a range of about 0.1 to about 0.5 mm. The compliant material may have a thickness in a range of about 0.5 mm to about 2.0 mm. The compliant material may be a foam.
The force sensing system may exclude additional capacitive sense layers between the cover and the compliant material.
The input surface may include multiple input regions each corresponding to an input key, and the capacitive sense layer may include a set of electrodes each having an area that is the same or smaller than an area of the input regions.
A method of detecting a key press includes determining a number of fingers in contact with an input surface of an electronic device, and determining a force threshold indicative of a key press based at least in part on the number of fingers in contact with the input surface. The method may further include detecting a force input that satisfies the force threshold, and in response to detecting the force input, registering a selection of an input region corresponding to a text character.
The operation of determining the number of fingers in contact with the input surface may include using a touch sensing system to determine the number of fingers in contact with the input surface. The force threshold may be between about 25 and 150 grams higher than a baseline force for the determined number of fingers in contact with the input surface.
The method may further include detecting a touch input corresponding to a movement across the input surface, and in response to detecting the touch input corresponding to the movement across the input surface, changing a position of a cursor on a display of the electronic device. The operation of detecting the force input may include detecting the force input with a force sensing system, and the operation of detecting the touch input comprises detecting the touch input with a touch sensing system.
The disclosure will be readily understood by the following detailed description in conjunction with the accompanying drawings, wherein like reference numerals designate like structural elements, and in which:
The use of cross-hatching or shading in the accompanying figures is generally provided to clarify the boundaries between adjacent elements and also to facilitate legibility of the figures. Accordingly, neither the presence nor the absence of cross-hatching or shading conveys or indicates any preference or requirement for particular materials, material properties, element proportions, element dimensions, commonalities of similarly illustrated elements, or any other characteristic, attribute, or property for any element illustrated in the accompanying figures.
Additionally, it should be understood that the proportions and dimensions (either relative or absolute) of the various features and elements (and collections and groupings thereof) and the boundaries, separations, and positional relationships presented therebetween, are provided in the accompanying figures merely to facilitate an understanding of the various embodiments described herein and, accordingly, may not necessarily be presented or illustrated to scale, and are not intended to indicate any preference or requirement for an illustrated embodiment to the exclusion of embodiments described with reference thereto.
Reference will now be made in detail to representative embodiments illustrated in the accompanying drawings. It should be understood that the following descriptions are not intended to limit the embodiments to one preferred embodiment. To the contrary, it is intended to cover alternatives, modifications, and equivalents as can be included within the spirit and scope of the described embodiments as defined by the appended claims.
The following disclosure relates to an input device that uses touch and/or force sensing to detect user inputs, and uses haptic outputs to provide feedback to a user. One example of such an input device is a keyboard that does not have mechanical or movable keys. Instead, the keyboard may have a flat, keyless input surface, such as a glass or metal layer, and may include touch and/or force sensing systems to determine when a user touches and/or presses on the surface. Haptic actuators may provide physical feedback to indicate that a user has pressed the keyless surface with sufficient force to register an input. The haptic actuators may induce a physical sensation that is similar to or representative of a mechanical key. For example, when a user presses the surface of the keyboard with sufficient force, the surface may vibrate or otherwise move to indicate to the user that the intended input has been registered.
Using force sensing in addition to touch sensing may allow a user to use a keyless keyboard more similarly to a mechanical keyboard. For example, when typing, users typically rest multiple fingers on the keyboard. With only touch sensing on a keyless keyboard (e.g., without force sensing), it may be difficult or impossible to determine whether a user is attempting to select a particular key, or whether the user is merely resting a finger on that key. Force sensing, instead of or in addition to touch sensing, allows a keyless keyboard to differentiate between incidental contact and intentional key selections.
Force sensing in a keyless keyboard may be either global or local. For global force sensing, the keyboard may determine a total amount or magnitude of force applied to the surface regardless of the position or number of fingers on the surface. As noted above, however, users may rest their fingers on keys that are not being actively selected. Moreover, different users may rest different numbers of fingers on the keys, or rest them with different amounts of force. And the same user may rest different numbers of fingers on the keys at different moments while typing. Thus, the force threshold for detecting a key press may change depending on how many fingers are touching the keyboard. Accordingly, a keyboard with global force sensing may set a force threshold that determines whether a key is pressed based on the number of fingers that are in contact with the surface at a given time (as detected by a touch sensing system, for example).
For local force sensing, the keyboard may determine an amount or magnitude of force applied to a particular location or locations on the surface. One example local force sensing system uses a pixelated capacitive sense layer below the surface of the keyboard. When pressed, the user's finger may form a depression in the keyboard surface beneath the finger. The pixelated capacitive sense layer may detect the depth and/or location of the depression to determine both an amount and a location of a force. Keyboards may use either global or local force sensing alone, or they may use a combination of these techniques.
Haptic output may also be global or local. For global haptic outputs, the entire keyboard surface may move to provide a haptic output. In such cases, all of the fingers that are resting on the keyboard surface may sense the haptic output. Global haptic outputs may be produced, for example, with a haptic actuator that moves the entire surface in-plane with an input surface of the keyboard (e.g., an x- or y-direction) or out-of-plane with the input surface (e.g., a z-direction). In some embodiments, in order to provide discrete global haptic outputs for subsequent key presses, multiple haptic actuators may be provided. For example, a single haptic actuator that vibrates the input surface may not be able to produce successive, discrete haptic outputs with a key-strike frequency of a user. Accordingly, multiple haptic actuators may be used. In some cases, the actuators may produce different haptic outputs, such as vibrations in different directions. Users may be able to differentiate between such outputs, even if they are produced substantially simultaneously.
For local haptic outputs, only a portion of the keyboard may move. For example, localized haptic actuators such as piezoelectric elements may cause localized deformations in the surface that are felt only (or primarily) by a finger directly under the deformation. In another example, electrostatic elements may selectively apply an electrostatic charge to the input surface or to portions thereof. The electrostatic charge may alter or modify a tactile or touch-based stimulus that is perceived by a user. The electrostatic charge may cause an actual or perceived change in friction or surface roughness between an object (e.g., the user's finger) and the input surface by electrostatically attracting the user's finger to the surface. A keyboard may use global or local haptic outputs, alone or in combination, to provide a desired haptic output to the user.
Because the keyboard does not have mechanical keys, the keyboard may provide numerous other features and functions beyond mere keyboard input. For example, the keyboard may include an adaptive display to render visual information, such as an outline of an input region (e.g., representing a key) and an indication of its function (e.g., a glyph). In this way, the location, size, spacing and/or arrangement of the keys may vary. As another example, the input surface of the keyboard may act as a touch pad to detect touch inputs (e.g., moving a cursor, manipulating user interface elements) as well as typing inputs.
While the instant discussion uses a keyboard as an example input device that uses force sensing to detect inputs and haptic outputs to provide tactile feedback, these techniques may be used in other input devices as well. For example, where the input device includes an adaptive display, the display may present representations of varied affordances or objects that can be manipulated and for which physical feedback can be provided, such as audio mixers, buttons, musical instruments, etc. Moreover, force sensing and haptic outputs may be used in devices other than flat, keyboard-like input devices. For example, a rotating input device, such as a knob, may detect inputs with force sensing systems and provide haptic outputs to convey feedback to a user.
These and other embodiments are discussed below with reference to the figures. However, those skilled in the art will readily appreciate that the detailed description given herein with respect to these figures is for explanatory purposes only and should not be construed as limiting.
As shown in
The cover 104 (or top member) defines an input surface of the keyboard 100. In the present example, the cover 104 is positioned on a top surface of the keyboard 100, instead of physical keys. The cover 104, or top member, may be or may include any appropriate materials, such as glass, metal, plastic, etc. The cover 104 may include or be coupled to other layers, such as filters, coatings, touch-sensitive layers, liquid crystal layers, display components (e.g., organic light emitting diode (OLED) layers, light sources, light guides), and the like. Although shown without any mechanical keys, the keyboard 100 may also include one or more mechanical keys.
The cover 104 may operate as a touch-sensitive surface. For example, the cover 104 may respond to a touch input and may include or be coupled to a touch sensing system configured to determine the location of a touch input on the cover 104. The cover 104 may receive a wide variety of touch inputs, which may be used to interpret a diverse set of commands or operations.
The cover 104 may additionally or alternatively be configured to operate as a force-sensitive surface. For example, the cover 104 may include or be coupled to a force sensing system configured to detect a location and/or amount of force applied to the cover 104. The force sensing system may include (or may be operably connected to) force sensing circuitry configured to determine or estimate an amount of applied force. The force sensing circuitry may output a signal or otherwise register that an input has been detected in response to determining an amount of force that exceeds a force threshold. The force threshold may be fixed or variable, and more than one threshold may be provided corresponding to different inputs. For example, the threshold may be based on the number of fingers in contact with the cover 104.
The cover 104 may also include differentiated input regions 106. For example, at least some of the differentiated input regions 106 may correspond to character input keys (e.g., alphanumeric characters, symbolic characters, text spaces, tabs, and the like). In some cases, other keys may control other aspects of a device without necessarily resulting in a character input (e.g., to control audio volume, screen brightness, or other device functions).
The differentiated input regions 106 may be regions of a cover (or other top member that defines an input surface) that are visually and/or tactilely differentiated or distinguished from one another with paint, ink, etching, grooves, bumps, ridges, textures, or the like. Differentiated input regions 106 may correspond to character input keys (e.g., keys of an alphanumeric keyboard), buttons, or other affordances. Differentiated input regions 106 may be referred to herein simply as input regions 106.
In some cases, the differentiated input regions 106 may be differentiated from one another virtually. For example, the cover 104 may include or be part of an adaptable display. The adaptable display may be an illuminated display that is configured to display visual indicia that correspond to one or more differentiated input regions 106. Where the differentiated input region 106 is virtually defined by the adaptable display, it may be referred to as a virtual key. One or more different sets of visual indicia may be displayed, depending on the type of affordance being emulated, user preference, and/or an application being controlled by the keyboard 100.
The keyboard 100 may also include various other components or devices depicted or not depicted in
As noted above, the keyboard 100 may include haptic actuators that are configured to move or otherwise impart a force to the entire cover 104 or top member of the keyboard 100.
The first and second actuators 202, 206 may impart to the cover 104 or other top member forces along different axes or directions. For example, the first actuator 202 may impart a force along an actuation axis or direction indicated by the arrow 204, while the second actuator 206 may impart a force along an actuation axis or direction indicated by the arrow 208. These directions may be substantially perpendicular to one another, though other relative orientations are also possible (e.g., parallel, 45 degrees, 30 degrees, etc.).
A single actuator may not be capable of providing haptic outputs (or desirable haptic outputs) at a rate sufficient to keep up with some users' typing speed. For example, some typists may strike keys at a frequency of up to ten characters per second (or more), and a single haptic actuator may not be able to produce outputs at this frequency, especially haptic outputs with relatively longer durations (e.g., outputs that are longer than 100 ms). Outputs of such durations may be desirable, however, to more closely mimic the tactile sensation of clicking on a mechanical key, or to otherwise provide a desirable user experience. Accordingly, a second haptic actuator may be provided.
By positioning the first and second actuators 202, 206 so that they impart perpendicular forces on the cover 104, interference between the motions or vibrations caused by the actuators may be reduced. For example, if the first and second actuators 202, 206 imparted forces along the same axes, the motions or vibrations imparted to the cover 104 by each actuator may cancel each other out, or otherwise interfere with each other. Moreover, it may be difficult or impossible for a user to differentiate haptic outputs from the different actuators, especially when they are both active at the same time (e.g., to indicate simultaneous or overlapping key presses). By having the actuators apply force in different directions (e.g., along perpendicular or non-parallel directions), a user may be able to discern when two haptic outputs are provided, even if the outputs overlap. While the outputs may feel the same or similar to one another (e.g., a user may not be able to differentiate the direction of the haptic actuator that produced a particular output), the start and/or end of a haptic output from one actuator may be detectable to a user even when it occurs during a haptic output from the other actuator.
The first and second actuators 202, 206 may be actuated in an alternating pattern. In some cases, the first and second actuators 202, 206 may be actuated in an alternating pattern only when a typing speed (e.g., a frequency of force inputs) exceeds a certain value, such as a frequency that is above the response frequency of only a single actuator. In such cases, if the typing speed is below the value, only one of the actuators may be used (or they may be used in a pattern other than an alternating pattern). Other patterns or schemes for actuating the first and second actuators 202, 206 in response to force inputs are also contemplated.
The first and second actuators 202, 206 may be any appropriate mechanisms or systems for producing haptic outputs or otherwise imparting a force to the cover 104. Suitable actuators may include electromechanical actuators, piezoelectric actuators (e.g., piezoelectric actuators coupled directly to the cover 104, piezo benders below the cover 104 that lift or move the cover 104), linear actuators, voice coil motors, Lorentz force actuators, electro-active polymer actuators, and so on. For example, the first and second actuators 202, 206 may be linear actuators each including a coil and a corresponding magnet, where passing a current through a coil moves the corresponding magnet (or otherwise imparts a force on the magnet).
The first and second actuators 202, 206 may impart forces to the cover 104 to produce varying kinds of haptic outputs. For example, the first and second actuators 202, 206 may oscillate along their respective axes (arrows 204, 208 in
While
The first and second actuators 202, 206 may impart forces to the cover 104 (or top member) that are in plane (or substantially in plane) with the input surface defined by the cover 104 or other top member.
In embodiments where the whole cover 104 moves (e.g., as described with respect to
In some embodiments, a subset of the movements depicted in
The haptic outputs described with respect to
As shown in
As the finger 500 continues to press downward, the actuator may allow the input region 502 to move downward as depicted in
As noted above, in some embodiments, a subset of the movements depicted in
The haptic actuator 601 may be affixed to the cover 104 and a lower support, such as the enclosure 102, so that when the haptic actuator 601 retracts (e.g., is shortened vertically), the haptic actuator 601 pulls down on the cover 104 and locally deforms and/or deflects the cover 104. The haptic actuator 601 may be affixed to the cover 104 and the enclosure 102 (or any other suitable component or structure) with an adhesive, such as a pressure or heat sensitive adhesive, epoxy, glue, or the like.
The haptic actuator 601 may include electrode layers 604 (e.g., 604-1, . . . , 604-n) interleaved with compliant layers 602 (e.g., 602-1, . . . , 602-n). In order to produce haptic outputs, and in particular to retract or shorten the actuator 601, the electrode layers 604 may be selectively electrically charged such that the electrode layers (e.g., adjacent electrode layers) are attracted to one another. For example, a first electrode layer 604-1 may be positively charged and a second electrode layer 604-2 may be negatively charged, thus causing the first and second electrode layers 604-1, 604-2 to be attracted to one another. This attraction force may result in a first compliant layer 602-1 being deformed as the first and second electrode layers 604-1, 604-2 are drawn together by the attractive force between the electrodes (e.g., an electrostatic force). Similar charges may be applied to other electrode layers 604 to cause the whole haptic actuator 601 to retract. On the other hand, to extend the haptic actuator 601 to produce an upwards force on the cover 104 (e.g., to form a protrusion), the electrode layers 604 may be electrically charged with a same or similar charge, causing the electrode layers 604 to repel one another. For example, all of the electrode layers 604 may be positively charged. The resulting repulsive force (e.g., electrostatic repulsion) may cause the compliant layers 602 to stretch vertically, thus producing a localized protrusion or deformation in the cover 104.
The haptic actuator 601 may be configured to produce various types of haptic outputs. For example, the haptic actuator 601 may be repeatedly pulsed to produce a vibration, or it may be actuated once to produce a deformation in one direction followed by a return to a neutral state, producing a single “pop” type haptic output. These and other types of haptic outputs may include retractions of the haptic actuator 601, extensions of the haptic actuator, or both types of movements. For example, a vibration may be produced by cyclically applying a certain charge to the electrode layers 604 so that they are attracted to adjacent electrode layers 604, thus compressing the compliant layers 602 and retracting the actuator 601. When the charge is removed between cycles, the electrode layers 604 may produce no forces, thus letting the haptic actuator 601 return to a neutral position. Similarly, a vibration may be produced by cyclically applying a charge to the electrode layers 604 that result in the electrode layers 604 repelling one another, followed by removal of the charges to allow the haptic actuator 601 to return to the neutral position. A vibration may also be produced by alternating between attractive and repulsive charges, resulting in an alternating retraction and extension of the actuator 601. Similar modes of operation may be used to produce non-repeating haptic outputs, such as a single “pop” type output described above.
While
The gaps 610 may provide clearance around the haptic actuators 601 to allow lateral deformation of the actuators 601 when the actuators are compressed. In some cases the gaps 610 are free space (e.g., air), while in other cases another material is introduced into the gaps, such as a material that is more compliant than the compliant layers 602 (and therefore allow lateral deflection of the compliant layers 602).
The connecting elements 606 may provide several benefits. For example, they may provide additional structural support to the cover 104 by providing less unsupported area between adjacent actuators 601. Further, they may help isolate or localize deflections produced by force inputs and/or key selections, which may improve local force and/or touch sensing functions. For example, it may improve the resolution with which a force sensing system can detect the location of a force input.
As shown in
The haptic actuator 601 may be configured to produce global haptic outputs, such as those described with respect to
The haptic actuator 601 may include any suitable number of compliant layers 602 and electrode layers 604. For example, the haptic actuator 601 may include 40 compliant layers 602 and 41 electrode layers 604, with each compliant layer 602 sandwiched between two electrode layers 604. The electrode layers 604 may be formed of or include any suitable material, such as gold, aluminum, copper, indium tin oxide (ITO), or the like. The compliant layers 602 may likewise be formed of or include any suitable material such as silicone, latex, elastomers, polymers, gels, or any other compliant material. The compliant layers 602 may be any suitable thickness, such from about 10 microns to about 50 microns thick. In some case they are about 25 microns thick. When viewed from the top, the actuator 601 may have any suitable shape, such as square, rectangular, round, or the like. In some cases, when viewed from the top (e.g., through the cover 104) the actuator 601 has length and width dimensions of about 40×40 mm, about 25×25 mm, or about 15×15 mm. In some cases, the actuator 601 has substantially the same dimensions as an input region (e.g., a virtual key) that it underlies. Other dimensions are also contemplated.
Haptic actuators 601 may be arranged in a keyboard 100 (or other input device) in any suitable manner. For example,
Any of the foregoing haptic outputs may be produced in response to the keyboard 100 detecting a force input that satisfies a threshold (e.g., a force threshold). In particular, the haptic outputs may be used to indicate to a user that they have pressed the keyboard 100 with enough force to register the input. In this way, the keyboard 100 may induce a sensation that mimics or suggests the action of a mechanical keyboard, with the haptic output representing the sensation of a collapsing mechanical key. Moreover, properties of the haptic output or outputs used by the keyboard 100 may be selected or optimized to provide a tactile feeling that is similar to that of a collapsing mechanical key. In some cases, the haptic outputs may not be produced in response to inputs corresponding to incidental contact due to fingers resting on the keyboard 100, low-force inputs due to touch inputs to the keyboard 100 (e.g., when the input surface is being used as a trackpad), or the like.
As noted above, a keyless keyboard, such as the keyboard 100, may include one or more force sensing systems that facilitate detection of user inputs. As used herein, a force sensing system corresponds to any combination of mechanisms and associated processors, software, etc. that can determine an amount of force applied to a surface or to a portion thereof. force sensing systems may include one or more force sensing elements, such as piezoelectric elements, strain gauges, optical displacement sensors, or the like.
In some embodiments, a single force sensing system may be used to determine an aggregate amount of force applied to the cover 104 (e.g., global force sensing). However, this type of force sensing system may provide insufficient information to determine a location of the physical contact that is producing the detected force. (Or it may not be able to determine the location to a suitable resolution.) Accordingly, where global force sensing is used, a touch sensing system may be used to determine the location of each contact between a user's finger (or other implement or input member) and the cover 104. Accelerometers may also be used in conjunction with the touch sensing system and the force sensing system to determine the location of a force input. For example, one or more accelerometers, and associated processors, may detect vibration or motion signatures that are indicative of an input from a particular finger or at a particular location on the input surface of the keyboard 100. Together, a touch sensing system and a global force sensing system (and, optionally, accelerometers) may be used to determine when and where a user is attempting to apply an input on the surface of the keyboard 100.
In other embodiments, multiple force sensing systems (or multiple force sensing elements associated with a single force sensing system) may be used to determine an amount of force applied to discrete areas or known locations on the cover 104. For example, in some cases, each input region 106 of the keyboard 100 (e.g., corresponding to the size and/or location of a traditional key such as a character input key) is associated with its own unique force sensing system or force sensing element. In other words, each key is separately monitored to detect force inputs. In some cases, instead of monitoring the force of each individual key, the keyboard 100 is divided into multiple force sensing regions or pixels, at least some of which include multiple keys. In particular, based on typical typing patterns, there may be groups of keys that are unlikely to be contacted simultaneously. For example, a user may rest his or her fingers along a “home row” or a central row of keys, and move his or her fingers away from the home row to strike individual keys. Because of the horizontal positioning of a user's fingers relative to the keyboard, it is less likely that a user will be touching multiple keys in a single column at any given time. As a more specific example, on a traditional “QWERTY” keyboard, a user's fingers may be resting on the “a” key while striking the “f” key, but it is less likely that the user's fingers will be resting on the “a” key while striking the “q” key. Accordingly, it may be possible to increase the precision of a force-sensitive keyboard by providing force sensing pixels (as opposed to a global force sensing system, for example) without resorting to a different force sensing system or force sensing element for each key.
Such force sensing pixels may encompass different groups of input regions and may detect forces substantially independently of one another. For example, a force input applied to one force sensing pixel may be detected by a force sensing system (or element) associated with that force sensing pixel, but may not be detected by a force sensing system (or element) associated with a different force sensing pixel (or it may not satisfy a detection threshold of the second force sensing system or element). In some cases, each force sensing pixel (and/or a force sensing element associated with each force sensing pixel) produces a force value distinct from each other force value. For example, a processor may use a first force sensing system or element associated with a first force sensing pixel (independently of a second force sensing system or element that is associated with a different force sensing pixel) to determine the force applied to the first force sensing pixel. Similarly, the processor may use the second force sensing system or element associated with the second force sensing pixel (independently of the first force sensing system or element) to determine the force applied to the second force sensing pixel. Accordingly, each force sensing pixel can be independently evaluated to determine whether a force input has been applied to that particular force sensing pixel and/or the amount of force applied to the particular pixel.
In some embodiments, such as those shown in
The arrangement of the force sensing regions in
The force sensing regions 702 (
The force sensing systems or elements associated with each force sensing region (e.g., the regions 702, 704) may be configured to detect key presses in response to different force values. For example, force inputs detected in the force sensing regions may be compared against different force thresholds. Thus, force sensing regions that are typically subjected to lower forces, such as those typically struck by a user's pinky finger, may use a different (e.g., lower) force threshold than those regions typically struck with greater force, such as those typically struck by a user's index finger or thumb.
The force sensing system 800 may include a cover 802 (corresponding to the cover 104 in
The deflection and/or compression behavior of the compliant material 804 and/or the cover 104 may be modeled so that a processer associated with the force sensing system 800 can determine an amount of force of a given force input. In particular, known forces may be applied to the cover 802 in various locations to determine the change in capacitance resulting from a given amount of force applied to a given location. This information may be stored in a table, as an equation representing a force versus capacitance curve, or in any other data structure or algorithm that can be used to correlate a capacitance value with a force value.
Instead of or in addition to capacitive sensors, other types of sensors may be used to detect a change in distance between the cover 802 and a lower layer. For example, the capacitive sense layer 806 may be replaced (or may be supplemented) by an array of optical displacement sensors that detect local deformations of the cover 802. Where distance or displacement sensors are used, known forces may be applied to the cover 802 in various locations to determine the sensor values that result from a given amount of force applied to a given location. This information may be stored in a table, as an equation representing a force versus displacement curve, or in any other data structure or algorithm that can be used to correlate a change in displacement or distance (as measured by the optical displacement sensors, for example) with a force value.
The cover 802 may be formed from or include any suitable material, such as glass, metal, polycarbonate, sapphire, or the like. The dimensions and/or the material of the cover 802 may be selected to provide a suitable local deformation profile (e.g., diameter and depth). For example, the cover 802 may have an elastic modulus in a range of about 60 to 80 GPa, and a thickness in a range of about 0.1 mm to 0.5 mm.
The compliant material 804 may be formed from or include any suitable material, such as foam, gel, silicone, an array of compliant material dots or structures (e.g., formed from silicone), liquid, air, or the like. The compliant material 804 may support the cover 802 over a touch and/or force sensitive area of the cover 802, such as the area of the cover 802 that defines input regions (e.g., keys). For example, as shown in
The compliant material 804 may also provide a predictable force-versus-displacement relationship, which may be exploited by the force sensing system 800 to help determine force values for force inputs. For example, the compliant material 804 may help to improve the consistency of the force-versus-displacement response across the input surface of the cover 802, especially as compared to a force sensing system 800 that uses an air gap instead of a compliant material 804. More particularly, without the compliant material 804, a force applied near a center of the cover 802 (e.g., away from the supported edges of the cover 802) may cause more deflection of the cover 802 than the same force applied near an edge of the cover 802. The supportive effect of the compliant material 804 may help prevent or limit the amount of sagging or global deflection in response to an input force, especially away from the edges or supported areas of the cover 802. In this way, input forces applied to the center and the edges of the cover 802 (and indeed any area of the cover 802) may result in a similar deformation. Moreover, due to the large area of support provided to the cover 802 by the compliant material 804, those deformations may be more localized (e.g., smaller) than they would be without the compliant material 804, thus producing higher resolution touch and force sensing results.
The compliant material 804 may be a single continuous sheet, multiple sheet segments, or other shapes or configurations (e.g., dots, pillars, pyramids, columns, discs, or the like). The dimensions and/or the material of the compliant material 804 (or any other property, such as poisons ratio, stiffness, hardness, durometer, etc.) may be selected to provide a suitable local deformation profile in conjunction with the cover 802. For example, the compliant material 804 may have a thickness in a range of about 0.5 mm to about 2.0 mm. Where the compliant material 804 comprises multiple compliant members or materials (e.g., dots, pillars, sheets, etc.), each compliant member may have substantially the same thickness, such that the distance between the cover 802 and an underlying sense layer (e.g., the sense layer 806) is substantially the same over the area that includes input regions.
The materials and dimensions of the cover 802 and the compliant material 804 may be optimized and/or evaluated together to provide a suitable local deformation profile. In some embodiments, the cover 802 is a glass layer having a thickness of about 0.3 mm and an elastic modulus of about 70 GPa, and the compliant material 804 is a foam having a thickness of about 0.5 mm.
The local deformation characteristics of the force sensing system 800 may allow multiple adjacent force inputs to be detected and separately identified. For example, the cover 802 and the compliant material 804 may experience sufficiently distinct depressions in response to force inputs that are spaced as close as 3.0 cm (e.g., 3.0 cm or more) from each other, as measured between geometric centroids of the force inputs. In some cases, the cover 802 and the compliant material 804 may experience sufficiently distinct depressions in response to force inputs that are even closer, such as 2.5, 2.0, or even 1.0 cm from each other.
The capacitive sense layer 906 may include a substrate 910, such as a circuit board or flex-circuit material, and a group of electrodes 912. The electrodes 912 may be conductive traces applied to the substrate 910 and coupled to a processor and/or other electronic components that facilitate determining the capacitance changes due to the presence of the finger 903 (and thus the force). The locations of the electrodes 912 may be known so that the detection of a change in capacitance at a given electrode 912 can indicate, to a device, where on the cover 902 the force input is located.
The size of the electrodes 912 may define a resolution of the force sensing system 900. For example, the electrodes 912 may be the same size or smaller (e.g., in surface area or any other appropriate dimension) than an input region (e.g., a virtual key). In such cases, it may be possible to determine from the force sensing system 900 what key a user has selected. That is, if one or more electrodes 912 that are below a particular key (e.g., the input region 106,
The force sensing systems 900, 916 described above provide localized force detection, where both the location of a force input and the amount of force of the force input may be determined by the force sensing systems. Also, the resolution of the force sensing systems 900, 916 may be high enough that the locations of force inputs from individual fingers can be distinguished from one another.
The force sensing system 1001 includes strain gauges 1004 applied to or otherwise integrated with the substrate 1002. The strain gauges 1004 may be any suitable configuration and may be formed of any suitable material. For example, the strain gauges 1004 may include a conductor having a serpentine or coil pattern (or any other suitable pattern) and disposed on a film or other substrate. In some cases, the strain gauges 1004 may include at two or more substrates or films, each having a coiled or serpentine conductor and laminated with one another. This configuration may facilitate filtering or rejection of noise, interference, or other undesirable effects on the strain gauges 1004 caused by temperature, magnetic fields, or the like.
The strain gauges 1004 may have any suitable size and may be arranged on the substrate 1002 in any suitable pattern. For example, as shown, the strain gauges 1004 may all be substantially the same size and arranged in a regular grid pattern on the substrate 1002. The strain gauges 1004 may have any suitable size as viewed from the top of the substrate 1002, such as about 10×10 mm, 15×15 mm, or any other suitable size. While the strain gauges 1004 may not be mapped directly to individual keys or input regions of a keyboard, the location of a force input on the substrate 1002 may be determined by analyzing signals from multiple (e.g., all) of the strain gauges 1004 to identify an estimated location (e.g., a centroid) of the input, regardless of where the input is applied on the substrate 1002 or other associated input surface.
In some cases, however, respective strain gauges 1004 may be positioned to correspond to respective keys or input regions. For example,
Where each key or input region is associated with at least one unique strain gauge, the substrate 1003 (which may correspond to the cover 104 or a component that is disposed below a cover) may include ribs 1007 formed on or otherwise coupled to the substrate 1003. The ribs 1007 may help isolate deformations and/or deflections produced by force and/or touch inputs applied to the substrate 1003 or an overlying cover, as shown and described in greater detail with respect to
The keyboard 100 in
The keyboard 100 in
The actuator 1201 may correspond to the haptic actuator 601 described herein. In particular, the actuator 1201 may provide both haptic actuation functions, as described above, as well as force sensing functions. For example, the actuator 1201 (which may have the same construction as the haptic actuator 601) includes compliant layers 1206 sandwiched between electrode layers 1204. The electrode layers 1204 may be used as electrodes in a mutual-capacitance sensing scheme. For example, one electrode layer may be used as a drive electrode and another electrode layer may be used as a sense electrode. When the sense and drive electrodes are moved closer together, such as when a finger 1202 or other implement deforms the substrate 1208 and compresses the actuator 1201, a processor or other circuitry may detect resulting electrical changes, which can be correlated to an amount of force applied via the force input. More particularly, the force-sensing system 1200 may use a force versus capacitance (or other electrical phenomenon) correlation to determine the amount of force that corresponds to a measured capacitance value (or other electrical value).
In some embodiments, only two electrode layers of the electrode layers 1204 in the actuator 1201 are used for capacitive force sensing. In other embodiments, more electrode layers 1204 are used, such as all of the electrode layers. As described above, an actuator may include 40 compliant layers 1206 and 41 electrode layers 1204. In such cases, all 41 electrodes may be used for capacitive sensing. Fewer electrodes may also be used.
Notably, the actuator 1201 may detect applied forces and produce haptic outputs substantially simultaneously. For example, a haptic signal may have a relatively low frequency (e.g., between 2 and 200 Hz, though other frequencies are also possible), while a drive signal for a drive electrode of a capacitive sensor may have a relatively high frequency (e.g., between 100 and 200 kHz, though other frequencies are also possible). Accordingly, such frequencies may be applied to electrode layers of the actuator 1201 substantially simultaneously such that a haptic output is produced while electrical changes due to force inputs are also detected. Processors and/or circuitry of the force sensing system 1200 may compensate for any compression or extension of the compliant layers 1206 due to the haptic output when sensing force inputs in order to mitigate any contamination of the force measurement by the haptic output.
Where a keyboard 100 includes force sensing regions that may be struck or actuated by more than one finger (such as a single force sensing region covering an entire keyboard or the force sensing pixels described above), the force sensing system may adjust or select a force threshold based on the number of fingers that are in contact with the surface.
For example, a typical force input indicative of a user attempting to actuate a virtual key on a flat surface may range from about 25 to about 150 grams. Accordingly, when a force sensing system detects a force input above that value, it should register a selection of the virtual key. However, if a user is resting multiple fingers on the surface of the keyboard, the force sensing system may detect a non-zero baseline force. This variability in the baseline force may result in false positive detections of force inputs, effectively lowering the amount of force necessary to trigger an input. As one example, if the baseline force due to three fingers resting on a keyboard is 20 grams, simply resting a fourth finger on the keyboard may be enough to cause the device to falsely identify a force input.
Accordingly, the force sensing system may dynamically determine the force threshold that is indicative of a key press based on the number of fingers in contact with an input surface of the keyboard at a given time.
The baseline forces 1302, 1308, and 1314 may be determined based on the number of fingers resting on the input surface of a keyboard. For example, the baseline force corresponding to one finger resting on the surface may be determined to be 10 grams. Thus, when one finger is detected on a surface, the baseline force may be 10 grams regardless of any actual detected force applied to the surface. Similarly, when two fingers are detected on the surface, the baseline force may be 20 grams, and so on. Accordingly, the force threshold may be determined at any given time based on the number of fingers in contact with the input surface and without regard to an actual amount of force being applied to the surface by the fingers.
In operation 1402, a number of fingers in contact with an input surface of an electronic device (e.g., the surface of the cover 104,
In operation 1404, a force threshold indicative of a key press is determined. For example, the keyboard 100 determines a force threshold that, if satisfied, will result in the keyboard 100 registering a selection of an input region (e.g., a virtual key). The force threshold is determined based at least in part on the number of fingers in contact with the input surface. For example, the force threshold may be between about 25 and about 150 grams higher than a baseline force for the number of fingers determined to be in contact with the input surface. The baseline force for each finger in contact may be 10 grams. Thus, each additional finger in contact with the input surface may add another 10 grams to the baseline force. Other values are also possible. Also, the baseline force for each number of fingers may not increase linearly. For example, the baseline force for one finger may be 10 grams, and the baseline force for eight fingers may be 40 grams.
In operation 1406, a force input satisfying the force threshold is detected. The force input may be detected with a force sensing system, such as any of the force sensing systems described above.
In operation 1408, in response to detecting the force input at operation 1406, a selection of an input region may be registered. For example, if a force input satisfying the threshold is determined to have been applied to a location of a key, a selection of that key (which may correspond to a text character, for example), is registered. The keyboard 100 may communicate the selection to an electronic device, which may execute an appropriate action or response (such as inputting the text character into an application).
In some cases, a force threshold may instead or additionally be established based on the magnitude of detected force inputs. That is, different users may type or apply inputs to a keyboard with different forces. More particularly, a first user may type with a relative lower force for each key strike (e.g., with an average force of about 10 grams), while a second user may type with a relatively larger force for each key strike (e.g., with an average force of about 100 grams). Accordingly, the keyboard 100 may adapt to individual users by adjusting the force threshold after detecting a number of inputs. For example, the keyboard 100 may detect inputs that are indicative of typing inputs (e.g., key presses), such as inputs applied to key regions and/or inputs having frequencies or other patterns indicative of key presses, and may determine average forces of those inputs. The keyboard 100 may then adjust the force threshold based on the average forces of the key presses. Thus, if the force threshold is significantly below a user's average typing force as detected by the keyboard 100, the keyboard 100 may mistake lighter touches (that were not intended as key presses) as key presses. On the other hand, if the force threshold is significantly above a user's average typing force as detected by the keyboard 100, the keyboard 100 may not recognize all of the user's inputs as key presses. Accordingly, the keyboard 100 may dynamically set the force threshold based on an average detected force input. In some cases, the force threshold may be set to a predetermined amount below the average typing force, such as 1%, 5%, 10%, or 20% lower than the average typing force (or any other suitable value).
The average typing force may be detected at any suitable interval, such as on a time-based periodic basis (e.g., every 1 hour, every 5 hours, etc.), or on an event-based basis (e.g., every time a word-processing application is opened, every time a computer is restarted, etc.). Other intervals, periods, and triggering events are also contemplated.
A keyless keyboard may also include a touch sensing system that detects touch and/or motion-based inputs (e.g., swipes, pinches, rotations, or taps), similar to a trackpad. Accordingly, a touch input corresponding to a movement across the input surface may be detected. In response to detecting the touch input corresponding to the movement across the input surface, a position of a cursor on a display of an electronic device may be changed. The touch sensing system may share the same input surface as the keys of the keyboard, such that a user can interact with the surface of the flat keyboard in various ways, including typing (e.g., force inputs) and traditional trackpad inputs (e.g., swipes, pinches, rotations, taps, and the like).
As noted above, the keyboard 100 may include an adaptable display that can change the layout of the keys (e.g., virtual keys) on the surface of the keyboard 100.
For example, as described with reference to
As depicted in
In concurrence with or in response to the input regions 1506 (e.g., virtual keys) being defined on the adaptive input surface 1504, the input regions 1506 may be indicated visually. For example, a display within the input surface 1504 may visually indicate the location of the virtual keys 1506. The locations of the virtual keys 1506 may also or instead be indicated tactilely. For example, actuators (e.g., piezoelectric actuators, electrostatic elements, etc.) may provide vibrations or other outputs that may be perceived by a user as a physical boundary of the virtual keys 1506. For example, when a user places a finger directly in the center of a virtual key 1506, no haptic output may be provided. When the user moves that finger to a key boundary (or places the finger on the key boundary initially), the actuator may produce an output, thus indicating to the user that their finger is on a key boundary.
The location of the input regions and corresponding visual indicia of the input regions may further be adaptive according to user interaction. For example, the input device 1500 may further include computer-readable memory storing multiple keyboard layouts, each of which has a corresponding visual representation. The layout depicted in
As depicted in
An input device that includes force sensing, haptic outputs, and an adaptive display may be used to define user interfaces other than traditional keyboards.
The notebook computer 1642 comprises an enclosure 1602 having an upper portion with a display 1644 and a lower portion housing an input device 1600. The enclosure may further house various components, such as a processing unit (which may be shared with the processing unit of the input device 1600 or may be separate), memory, computer-readable media, input/output ports, sensors, microphones, speakers, etc. The input device 1600 may include a force sensing system, a touch sensing system, and one or more haptic actuators (not shown). Any of the force or touch sensing systems or haptic actuators described herein may be used in the input device 1600.
The input device 1600 has an adaptive input surface 1604 (which may correspond to the cover 104 in
Similarly,
The input device 1700 has an adaptive input surface 1704 (which may correspond to the cover 104 in
As illustrated in
The example devices illustrated in the above figures are intended to be illustrative in nature, and can be implemented in a number of other manners. Further, while the above examples are illustrated with flat, generally smooth input surfaces, the present invention can also be implemented using curved, bent, textured, rough, and other types of surfaces.
As shown in
The memory 2060 may include a variety of types of non-transitory computer-readable storage media, including, for example, read access memory (RAM), read-only memory (ROM), erasable programmable memory (e.g., EPROM and EEPROM), or flash memory. The memory 2060 is configured to store computer-readable instructions, sensor values, and other persistent software elements.
In this example, the processing unit 2058 is operable to read computer-readable instructions stored on the memory 2060. The computer-readable instructions may adapt the processing unit 2058 to perform the operations or functions described herein. The computer-readable instructions may be provided as a computer-program product, software application, or the like.
The device 2000 may also include a battery 2062 that is configured to provide electrical power to the components of the device 2000. The battery 2062 may include one or more power storage cells that are linked together to provide an internal supply of electrical power. The battery 2062 may be operatively coupled to power management circuitry that is configured to provide appropriate voltage and power levels for individual components or groups of components within the device 2000. The battery 2062, via power management circuitry, may receive power from an external source, such as an AC power outlet. The battery 2062 may store received power so that the device 2000 may operate without connection to an external power source for an extended period of time, which may range from several hours to several days.
The device 2000 may also include a display 2020 (or multiple displays 2020). The display 2020 may include a liquid crystal display (LCD), organic light emitting diode (OLED) display, electroluminescent (EL) display, electrophoretic ink (e-ink) display, or the like. If the display 2020 is an LCD or e-ink type display, the display 2020 may also include a backlight component that can be controlled to provide variable levels of display brightness. If the display 2020 is an OLED or EL type display, the brightness of the display 2020 may be controlled by modifying the electrical signals that are provided to display elements. The display 2020 may include a standalone display such as the display 1744 (
In some embodiments, the device 2000 includes one or more input devices 2064. The input device 2064 is a device that is configured to receive user input. The input device 2064 may include, for example, a push button, a touch-activated button, or the like. In some embodiments, the input device 2064 may provide a dedicated or primary function, including, for example, a power button, volume buttons, home buttons, scroll wheels, and camera buttons. Generally, a touch sensing system and a force sensing system may also be classified as input devices. However, for purposes of this illustrative example, the touch sensing system (touch sensing element 2018 and touch sensing circuitry 2070) and force sensing system (force sensing element 2066 and force sensing circuitry 2072) are depicted as distinct components within the device 2000.
The device 2000 may include a touch sensing system (or multiple touch sensing systems). A touch sensing system may include a touch sensing element 2018, or multiple touch sensing elements 2018, and touch sensing circuitry 2070. The touch sensing system may also include or incorporate other components of an electronic device, such as a cover or input surface of an electronic device. The touch sensing element(s) 2018 may include electrodes, electrode layers, or other components, and may be configured to operate in accordance with a mutual-capacitance or self-capacitance touch-sensing scheme, as described above. Touch sensing element(s) 2018 for other types of touch sensing schemes may additionally or alternatively be used, such as elements for surface acoustic wave sensors, resistive sensors, infrared sensors, and the like.
The device 2000 may also include touch sensing circuitry 2070. The touch sensing circuitry 2070 may be operably coupled to the touch sensing element(s) 2018 to form all or part of the touch sensing system. The touch sensing circuitry 2070, in conjunction with the touch sensing element(s) 2018, may detect and estimate the location of a touch on or near an input surface (such as an input surface of a keyless keyboard). The touch sensing circuitry 2070 may further output signals or other indicia indicating the detected location of a touch. The touch sensing circuitry 2070 may further be operably coupled to the processing unit 2058.
The device 2000 may also include a force sensing system (or multiple force sensing systems). A force sensing system may correspond to any component or group of components that detects and/or estimates an amount of force applied to an input surface. For example, a force sensing system may include a force sensing element 2066, or multiple force sensing elements 2066, and force sensing circuitry 2072. The force sensing system may also include or incorporate other components of an electronic device, such as a cover or input surface of an electronic device. Where a device includes multiple force sensing systems, each force sensing system may include its own separate components (e.g., each may have a different force sensing element and force sensing circuitry), or they may share some components (e.g., each force sensing system may each have its own force sensing element, but may share force sensing circuitry).
The force sensing element(s) 2066 may produce changes in electrical values (e.g., resistance, capacitance, voltage, etc.), detectible signals, or the like, in response to force inputs applied to the keyless keyboard (or other force-sensitive input device). The sensing element(s) 2066 may be implemented as one or more layers, such as layers of electrodes or other conductive materials. Example force sensitive elements are described above, and may include capacitive sensing elements, electrodes, piezoelectric materials, strain gauges, and the like.
The force sensing circuitry 2072 may be operably coupled to the force sensing element 2066 to form all or part of the force sensing system. The force sensing circuitry 2072, in conjunction with the force sensing element(s) 2066, may detect and estimate an amount of force applied to an input surface. In some embodiments, the force sensing circuitry 2072 may further detect a location of an applied force. The force sensing circuitry 2072 may further output signals or other indicia indicating an estimated amount of applied force. In some embodiments, the force sensing circuitry 2072 may operate using a dynamic or adjustable force threshold. The force sensing circuitry 2072 may only output signals in accordance with an applied force exceeding the force threshold. The force sensing circuitry 2072 may further be operably coupled to the processing unit 2058.
The device 2000 may also include a haptic actuator 2026 (or multiple haptic actuators 2026). The haptic actuator 2026 may be controlled by the processing unit 2058, and may provide haptic feedback to a user interacting with the device 2000, such as illustrated above with respect to
The device 2000 may also include a communication port 2068 that is configured to transmit and/or receive signals or electrical communication from an external or separate device. The communication port 2068 may couple to an external device via a cable, adaptor, or other type of electrical connector. In some embodiments, the communication port 2068 may be used to couple the device 2000 to a host computer. The communication port 2068 may receive control information from an external device, which may be used to operate and/or control the device 2000.
The foregoing description, for purposes of explanation, used specific nomenclature to provide a thorough understanding of the described embodiments. However, it will be apparent to one skilled in the art that the specific details are not required in order to practice the described embodiments. Thus, the foregoing descriptions of the specific embodiments described herein are presented for purposes of illustration and description. They are not targeted to be exhaustive or to limit the embodiments to the precise forms disclosed. It will be apparent to one of ordinary skill in the art that many modifications and variations are possible in view of the above teachings. For example, while the methods or processes disclosed herein have been described and shown with reference to particular operations performed in a particular order, these operations may be combined, sub-divided, or re-ordered to form equivalent methods or processes without departing from the teachings of the present disclosure. Moreover, structures, features, components, materials, steps, processes, or the like, that are described herein with respect to one embodiment may be omitted from that embodiment or incorporated into other embodiments.
This application is a nonprovisional patent application of and claims the benefit of U.S. Provisional Patent Application No. 62/393,989, filed Sep. 13, 2016 and titled “Keyless Keyboard with Force Sensing and Haptic Feedback,” the disclosure of which is hereby incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
3657492 | Arndt et al. | Apr 1972 | A |
3917917 | Murata | Nov 1975 | A |
3978297 | Lynn et al. | Aug 1976 | A |
4095066 | Harris | Jun 1978 | A |
4319099 | Asher | Mar 1982 | A |
4349712 | Michalski | Sep 1982 | A |
4484042 | Matsui | Nov 1984 | A |
4596905 | Fowler | Jun 1986 | A |
4598181 | Selby | Jul 1986 | A |
4670084 | Durand et al. | Jun 1987 | A |
4755645 | Naoki et al. | Jul 1988 | A |
4937408 | Hattori et al. | Jun 1990 | A |
4987275 | Miller et al. | Jan 1991 | A |
5021638 | Nopper et al. | Jun 1991 | A |
5092459 | Uljanic et al. | Mar 1992 | A |
5136131 | Komaki | Aug 1992 | A |
5278372 | Takagi et al. | Jan 1994 | A |
5280146 | Inagaki et al. | Jan 1994 | A |
5340955 | Calvillo et al. | Aug 1994 | A |
5382762 | Mochizuki | Jan 1995 | A |
5397867 | Demeo | Mar 1995 | A |
5408060 | Muurinen | Apr 1995 | A |
5421659 | Liang | Jun 1995 | A |
5422447 | Spence | Jun 1995 | A |
5457297 | Chen | Oct 1995 | A |
5477430 | LaRose et al. | Dec 1995 | A |
5481074 | English | Jan 1996 | A |
5504283 | Kako et al. | Apr 1996 | A |
5512719 | Okada et al. | Apr 1996 | A |
5625532 | Sellers | Apr 1997 | A |
5804780 | Bartha | Sep 1998 | A |
5828015 | Coulon | Oct 1998 | A |
5847337 | Chen | Dec 1998 | A |
5874700 | Hochgesang | Feb 1999 | A |
5875013 | Takahara | Feb 1999 | A |
5876106 | Kordecki et al. | Mar 1999 | A |
5878872 | Tsai | Mar 1999 | A |
5881866 | Miyajima et al. | Mar 1999 | A |
5898147 | Domzaiski et al. | Apr 1999 | A |
5924555 | Sadamori et al. | Jul 1999 | A |
5935691 | Tsai | Aug 1999 | A |
5960942 | Thornton | Oct 1999 | A |
5986227 | Hon | Nov 1999 | A |
6020565 | Pan | Feb 2000 | A |
6068416 | Kumamoto et al. | May 2000 | A |
6215420 | Harrison et al. | Apr 2001 | B1 |
6257782 | Maruyama et al. | Jul 2001 | B1 |
6259046 | Iwama et al. | Jul 2001 | B1 |
6377685 | Krishnan | Apr 2002 | B1 |
6388219 | Hsu et al. | May 2002 | B2 |
6423918 | King et al. | Jul 2002 | B1 |
6482032 | Szu et al. | Nov 2002 | B1 |
6530283 | Okada et al. | Mar 2003 | B2 |
6538801 | Jacobson et al. | Mar 2003 | B2 |
6542355 | Huang | Apr 2003 | B1 |
6552287 | Janniere | Apr 2003 | B2 |
6556112 | Van Zeeland et al. | Apr 2003 | B1 |
6559399 | Hsu et al. | May 2003 | B2 |
6560612 | Yamada et al. | May 2003 | B1 |
6563435 | Platz | May 2003 | B1 |
6572289 | Lo et al. | Jun 2003 | B2 |
6573463 | Ono | Jun 2003 | B2 |
6585435 | Fang | Jul 2003 | B2 |
6624369 | Ito et al. | Sep 2003 | B2 |
6706986 | Hsu | Mar 2004 | B2 |
6738050 | Comiskey | May 2004 | B2 |
6750414 | Sullivan | Jun 2004 | B2 |
6759614 | Yoneyama | Jul 2004 | B2 |
6762381 | Kunthady et al. | Jul 2004 | B2 |
6765503 | Chan et al. | Jul 2004 | B1 |
6788450 | Kawai et al. | Sep 2004 | B2 |
6797906 | Ohashi | Sep 2004 | B2 |
6850227 | Takahashi et al. | Feb 2005 | B2 |
6860660 | Hochgesang et al. | Mar 2005 | B2 |
6911608 | Levy | Jun 2005 | B2 |
6926418 | Ostergård et al. | Aug 2005 | B2 |
6940030 | Takeda et al. | Sep 2005 | B2 |
6977352 | Oosawa | Dec 2005 | B2 |
6979792 | Lai | Dec 2005 | B1 |
6987466 | Welch et al. | Jan 2006 | B1 |
6987503 | Inoue | Jan 2006 | B2 |
7012206 | Oikawa | Mar 2006 | B2 |
7030330 | Suda | Apr 2006 | B2 |
7038832 | Kanbe | May 2006 | B2 |
7126499 | Lin et al. | Oct 2006 | B2 |
7129930 | Cathey et al. | Oct 2006 | B1 |
7134205 | Bruennel | Nov 2006 | B2 |
7146701 | Mahoney et al. | Dec 2006 | B2 |
7151236 | Ducruet et al. | Dec 2006 | B2 |
7151237 | Mahoney et al. | Dec 2006 | B2 |
7154059 | Chou | Dec 2006 | B2 |
7161084 | Sandbach | Jan 2007 | B2 |
7166813 | Soma | Jan 2007 | B2 |
7172303 | Shipman et al. | Feb 2007 | B2 |
7189932 | Kim | Mar 2007 | B2 |
7256766 | Albert et al. | Aug 2007 | B2 |
7283119 | Kishi | Oct 2007 | B2 |
7301113 | Nishimura et al. | Nov 2007 | B2 |
7312790 | Sato et al. | Dec 2007 | B2 |
7378607 | Koyano et al. | May 2008 | B2 |
7385806 | Liao | Jun 2008 | B2 |
7391555 | Albert et al. | Jun 2008 | B2 |
7414213 | Hwang | Aug 2008 | B2 |
7429707 | Yanai et al. | Sep 2008 | B2 |
7432460 | Clegg | Oct 2008 | B2 |
7510342 | Lane et al. | Mar 2009 | B2 |
7531764 | Lev et al. | May 2009 | B1 |
7541554 | Hou | Jun 2009 | B2 |
7589292 | Jung et al. | Sep 2009 | B2 |
7639187 | Caballero et al. | Dec 2009 | B2 |
7639571 | Ishii et al. | Dec 2009 | B2 |
7651231 | Chou et al. | Jan 2010 | B2 |
7679010 | Wingett | Mar 2010 | B2 |
7724415 | Yamaguchi | May 2010 | B2 |
7781690 | Ishii | Aug 2010 | B2 |
7813774 | Perez-Noguera | Oct 2010 | B2 |
7842895 | Lee | Nov 2010 | B2 |
7847204 | Tsai | Dec 2010 | B2 |
7851819 | Shi | Dec 2010 | B2 |
7866866 | Wahlstrom | Jan 2011 | B2 |
7893376 | Chen | Feb 2011 | B2 |
7923653 | Ohsumi | Apr 2011 | B2 |
7947915 | Lee et al. | May 2011 | B2 |
7999748 | Ligtenberg et al. | Aug 2011 | B2 |
8063325 | Sung et al. | Nov 2011 | B2 |
8077096 | Chiang et al. | Dec 2011 | B2 |
8080744 | Yeh et al. | Dec 2011 | B2 |
8098228 | Shimodaira et al. | Jan 2012 | B2 |
8109650 | Chang et al. | Feb 2012 | B2 |
8119945 | Lin | Feb 2012 | B2 |
8124903 | Tatehata et al. | Feb 2012 | B2 |
8134094 | Tsao et al. | Mar 2012 | B2 |
8143982 | Lauder et al. | Mar 2012 | B1 |
8156172 | Muehl et al. | Apr 2012 | B2 |
8178808 | Strittmatter et al. | May 2012 | B2 |
8184021 | Chou | May 2012 | B2 |
8212160 | Tsao | Jul 2012 | B2 |
8212162 | Zhou | Jul 2012 | B2 |
8218301 | Lee | Jul 2012 | B2 |
8232958 | Tolbert | Jul 2012 | B2 |
8246228 | Ko et al. | Aug 2012 | B2 |
8253048 | Ozias et al. | Aug 2012 | B2 |
8253052 | Chen | Sep 2012 | B2 |
8263887 | Chen et al. | Sep 2012 | B2 |
8289280 | Travis | Oct 2012 | B2 |
8299382 | Takemae et al. | Oct 2012 | B2 |
8317384 | Chung et al. | Nov 2012 | B2 |
8319298 | Hsu | Nov 2012 | B2 |
8325141 | Marsden | Dec 2012 | B2 |
8330725 | Mahowald et al. | Dec 2012 | B2 |
8354629 | Lin | Jan 2013 | B2 |
8378857 | Pance | Feb 2013 | B2 |
8383972 | Liu | Feb 2013 | B2 |
8384566 | Bocirnea | Feb 2013 | B2 |
8404990 | Lutgring et al. | Mar 2013 | B2 |
8451146 | Mahowald et al. | Mar 2013 | B2 |
8431849 | Chen | Apr 2013 | B2 |
8436265 | Koike et al. | May 2013 | B2 |
8462514 | Myers et al. | Jun 2013 | B2 |
8500348 | Dumont et al. | Aug 2013 | B2 |
8502094 | Chen | Aug 2013 | B2 |
8542194 | Akens et al. | Sep 2013 | B2 |
8548528 | Kim et al. | Oct 2013 | B2 |
8564544 | Jobs et al. | Oct 2013 | B2 |
8569639 | Strittmatter | Oct 2013 | B2 |
8575632 | Kuramoto et al. | Nov 2013 | B2 |
8581127 | Jhuang et al. | Nov 2013 | B2 |
8592699 | Kessler et al. | Nov 2013 | B2 |
8592702 | Tsai | Nov 2013 | B2 |
8592703 | Johnson et al. | Nov 2013 | B2 |
8604370 | Chao | Dec 2013 | B2 |
8629362 | Knighton et al. | Jan 2014 | B1 |
8633916 | Bernstein et al. | Jan 2014 | B2 |
8642904 | Chiba et al. | Feb 2014 | B2 |
8651720 | Sherman et al. | Feb 2014 | B2 |
8659882 | Liang et al. | Feb 2014 | B2 |
8692784 | Cheng | Apr 2014 | B2 |
8731618 | Jarvis et al. | May 2014 | B2 |
8748767 | Ozias et al. | Jun 2014 | B2 |
8759705 | Funakoshi et al. | Jun 2014 | B2 |
8760405 | Nam | Jun 2014 | B2 |
8786548 | Oh et al. | Jul 2014 | B2 |
8791378 | Lan | Jul 2014 | B2 |
8835784 | Hirota | Sep 2014 | B2 |
8847090 | Ozaki | Sep 2014 | B2 |
8847711 | Yang et al. | Sep 2014 | B2 |
8853580 | Chen | Oct 2014 | B2 |
8854312 | Meierling | Oct 2014 | B2 |
8870477 | Merminod et al. | Oct 2014 | B2 |
8884174 | Chou et al. | Nov 2014 | B2 |
8921473 | Hyman | Dec 2014 | B1 |
8922476 | Stewart et al. | Dec 2014 | B2 |
8926111 | Weng | Jan 2015 | B2 |
8927890 | Peterson et al. | Jan 2015 | B2 |
8943427 | Heo et al. | Jan 2015 | B2 |
8963036 | Mittleman et al. | Feb 2015 | B2 |
8976117 | Krahenbuhl et al. | Mar 2015 | B2 |
8994641 | Stewart et al. | Mar 2015 | B2 |
9007297 | Stewart et al. | Apr 2015 | B2 |
9012795 | Niu et al. | Apr 2015 | B2 |
9024214 | Niu et al. | May 2015 | B2 |
9029723 | Pegg | May 2015 | B2 |
9041652 | Elias et al. | May 2015 | B2 |
9063627 | Yairi et al. | Jun 2015 | B2 |
9064642 | Welch et al. | Jun 2015 | B2 |
9086733 | Pance | Jul 2015 | B2 |
9087663 | Los | Jul 2015 | B2 |
9093229 | Leong et al. | Jul 2015 | B2 |
9189078 | Mahowald et al. | Nov 2015 | B2 |
9195314 | Sharma | Nov 2015 | B2 |
9213416 | Chen | Dec 2015 | B2 |
9223352 | Smith et al. | Dec 2015 | B2 |
9234486 | Das et al. | Jan 2016 | B2 |
9235236 | Nam | Jan 2016 | B2 |
9274654 | Slobodin et al. | Mar 2016 | B2 |
9275810 | Pance et al. | Mar 2016 | B2 |
9288373 | Xie et al. | Mar 2016 | B2 |
9298273 | Shao et al. | Mar 2016 | B2 |
9300033 | Han et al. | Mar 2016 | B2 |
9305496 | Kimura | Apr 2016 | B2 |
9348425 | Chi et al. | May 2016 | B2 |
9349551 | Nakajima | May 2016 | B2 |
9360891 | Van Der Merwe | Jun 2016 | B1 |
9405369 | Modarres et al. | Aug 2016 | B2 |
9412533 | Hendren et al. | Aug 2016 | B2 |
9443672 | Martisauskas | Sep 2016 | B2 |
9444454 | Hovden | Sep 2016 | B2 |
9448628 | Tan et al. | Sep 2016 | B2 |
9448631 | Winter et al. | Sep 2016 | B2 |
9449772 | Leong et al. | Sep 2016 | B2 |
9454239 | Elias | Sep 2016 | B2 |
9471185 | Guard | Oct 2016 | B2 |
9477382 | Hicks et al. | Oct 2016 | B2 |
9502193 | Niu et al. | Nov 2016 | B2 |
9612664 | Croisonnier | Apr 2017 | B2 |
9612674 | Degner et al. | Apr 2017 | B2 |
9640347 | Kwan et al. | May 2017 | B2 |
9704665 | Brock et al. | Jul 2017 | B2 |
9704670 | Leong | Jul 2017 | B2 |
9710069 | Leong et al. | Jul 2017 | B2 |
9715978 | Hendren | Jul 2017 | B2 |
9734965 | Martinez et al. | Aug 2017 | B2 |
9746923 | Cruz-Hernandez et al. | Aug 2017 | B2 |
9793066 | Brock | Oct 2017 | B1 |
9910211 | Kloeppel et al. | Mar 2018 | B2 |
9941879 | Lee et al. | Apr 2018 | B2 |
10001812 | Andre et al. | Jun 2018 | B2 |
10175771 | Barneron | Jan 2019 | B2 |
10284196 | Hanssen et al. | May 2019 | B2 |
10353485 | Zhang et al. | Jul 2019 | B1 |
10585493 | Elias | Mar 2020 | B2 |
10615793 | Kawaguchi et al. | Apr 2020 | B2 |
10755877 | Wang et al. | Aug 2020 | B1 |
10775850 | Wang et al. | Sep 2020 | B2 |
10796863 | Stringer et al. | Oct 2020 | B2 |
20010048837 | Parkinson | Dec 2001 | A1 |
20020079211 | Katayama et al. | Jun 2002 | A1 |
20020093436 | Lien | Jul 2002 | A1 |
20020113770 | Jacobson et al. | Aug 2002 | A1 |
20020149835 | Kanbe | Oct 2002 | A1 |
20030169232 | Ito | Sep 2003 | A1 |
20040004559 | Rast | Jan 2004 | A1 |
20040041791 | Dunker | Mar 2004 | A1 |
20040225965 | Garside et al. | Nov 2004 | A1 |
20050035950 | Daniels | Feb 2005 | A1 |
20050253801 | Kobayashi | Nov 2005 | A1 |
20060011458 | Purcocks | Jan 2006 | A1 |
20060020469 | Rast | Jan 2006 | A1 |
20060120790 | Chang | Jun 2006 | A1 |
20060181511 | Woolley | Aug 2006 | A1 |
20060243987 | Lai | Nov 2006 | A1 |
20070070052 | Westerman | Mar 2007 | A1 |
20070200823 | Bytheway et al. | Aug 2007 | A1 |
20070285393 | Ishakov | Dec 2007 | A1 |
20080131184 | Brown et al. | Jun 2008 | A1 |
20080136782 | Mundt et al. | Jun 2008 | A1 |
20080251370 | Aoki | Oct 2008 | A1 |
20090009482 | McDermid | Jan 2009 | A1 |
20090046053 | Shigehiro et al. | Feb 2009 | A1 |
20090103964 | Takagi et al. | Apr 2009 | A1 |
20090128496 | Huang | May 2009 | A1 |
20090262085 | Wassingbo et al. | Oct 2009 | A1 |
20090267892 | Faubert | Oct 2009 | A1 |
20100045705 | Vertegaal et al. | Feb 2010 | A1 |
20100066568 | Lee | Mar 2010 | A1 |
20100109921 | Annerfors | May 2010 | A1 |
20100149104 | Sim | Jun 2010 | A1 |
20100156796 | Kim et al. | Jun 2010 | A1 |
20100231508 | Cruz-Hernandez | Sep 2010 | A1 |
20100253630 | Homma et al. | Oct 2010 | A1 |
20100321298 | Tsai et al. | Dec 2010 | A1 |
20100321301 | Casparian | Dec 2010 | A1 |
20110032127 | Roush | Feb 2011 | A1 |
20110056817 | Wu | Mar 2011 | A1 |
20110056836 | Tatebe et al. | Mar 2011 | A1 |
20110115709 | Cruz-Hernandez | May 2011 | A1 |
20110205179 | Braun | Aug 2011 | A1 |
20110242029 | Kasahara | Oct 2011 | A1 |
20110261031 | Muto | Oct 2011 | A1 |
20110267272 | Meyer et al. | Nov 2011 | A1 |
20110284355 | Yang | Nov 2011 | A1 |
20120012446 | Hwa | Jan 2012 | A1 |
20120032972 | Hwang | Feb 2012 | A1 |
20120075192 | Marsden | Mar 2012 | A1 |
20120080297 | Takeuchi et al. | Apr 2012 | A1 |
20120090973 | Liu | Apr 2012 | A1 |
20120092263 | Peterson | Apr 2012 | A1 |
20120098751 | Liu | Apr 2012 | A1 |
20120286701 | Yang et al. | Nov 2012 | A1 |
20120298496 | Zhang | Nov 2012 | A1 |
20120313856 | Hsieh | Dec 2012 | A1 |
20130043115 | Yang et al. | Feb 2013 | A1 |
20130076635 | Lin | Mar 2013 | A1 |
20130093500 | Bruwer | Apr 2013 | A1 |
20130093733 | Yoshida | Apr 2013 | A1 |
20130100030 | Los et al. | Apr 2013 | A1 |
20130120265 | Horii et al. | May 2013 | A1 |
20130141396 | Lynn | Jun 2013 | A1 |
20130161170 | Fan et al. | Jun 2013 | A1 |
20130215079 | Johnson et al. | Aug 2013 | A1 |
20130228023 | Drasnin | Sep 2013 | A1 |
20130270090 | Lee | Oct 2013 | A1 |
20130275907 | Lau | Oct 2013 | A1 |
20140015777 | Park et al. | Jan 2014 | A1 |
20140027259 | Kawana et al. | Jan 2014 | A1 |
20140071654 | Chien | Mar 2014 | A1 |
20140082490 | Jung et al. | Mar 2014 | A1 |
20140090967 | Inagaki | Apr 2014 | A1 |
20140098042 | Kuo et al. | Apr 2014 | A1 |
20140151211 | Zhang | Jun 2014 | A1 |
20140184496 | Gribetz et al. | Jul 2014 | A1 |
20140191973 | Zellers et al. | Jul 2014 | A1 |
20140218640 | Chi | Aug 2014 | A1 |
20140218851 | Klein et al. | Aug 2014 | A1 |
20140247222 | Ferren | Sep 2014 | A1 |
20140252881 | Dinh et al. | Sep 2014 | A1 |
20140291133 | Fu et al. | Oct 2014 | A1 |
20140375141 | Nakajima | Dec 2014 | A1 |
20150010723 | Krishnan et al. | Jan 2015 | A1 |
20150016038 | Niu et al. | Jan 2015 | A1 |
20150083561 | Han et al. | Mar 2015 | A1 |
20150116205 | Westerman | Apr 2015 | A1 |
20150192960 | Sharma | Jul 2015 | A1 |
20150268768 | Woodhull | Sep 2015 | A1 |
20150270073 | Yarak, III et al. | Sep 2015 | A1 |
20150277504 | Odell | Oct 2015 | A1 |
20150277559 | Vescovi et al. | Oct 2015 | A1 |
20150277620 | Bulea | Oct 2015 | A1 |
20150287553 | Welch et al. | Oct 2015 | A1 |
20150309538 | Zhang | Oct 2015 | A1 |
20150370339 | Ligtenberg et al. | Dec 2015 | A1 |
20150378391 | Huitema et al. | Dec 2015 | A1 |
20160011691 | Shinkai et al. | Jan 2016 | A1 |
20160049266 | Stringer et al. | Feb 2016 | A1 |
20160093452 | Zercoe et al. | Mar 2016 | A1 |
20160096195 | Barnes et al. | Apr 2016 | A1 |
20160154464 | Croisonnier | Jun 2016 | A1 |
20160172129 | Zercoe et al. | Jun 2016 | A1 |
20160189890 | Leong et al. | Jun 2016 | A1 |
20160189891 | Zercoe et al. | Jun 2016 | A1 |
20160329166 | Hou et al. | Nov 2016 | A1 |
20160336124 | Leong et al. | Nov 2016 | A1 |
20160336127 | Leong et al. | Nov 2016 | A1 |
20160336128 | Leong et al. | Nov 2016 | A1 |
20160343523 | Hendren et al. | Nov 2016 | A1 |
20160351360 | Knopf et al. | Dec 2016 | A1 |
20160365204 | Cao et al. | Dec 2016 | A1 |
20160378234 | Ligtenberg et al. | Dec 2016 | A1 |
20160379775 | Leong et al. | Dec 2016 | A1 |
20170004937 | Leong et al. | Jan 2017 | A1 |
20170004939 | Kwan et al. | Jan 2017 | A1 |
20170011869 | Knopf et al. | Jan 2017 | A1 |
20170090104 | Cao et al. | Mar 2017 | A1 |
20170090106 | Cao et al. | Mar 2017 | A1 |
20170102809 | Son | Apr 2017 | A1 |
20170301487 | Leong et al. | Oct 2017 | A1 |
20170315624 | Leong et al. | Nov 2017 | A1 |
20170315628 | Yao | Nov 2017 | A1 |
20180029339 | Liu et al. | Feb 2018 | A1 |
20180040441 | Wu et al. | Feb 2018 | A1 |
20200379520 | Wang et al. | Dec 2020 | A1 |
Number | Date | Country |
---|---|---|
2155620 | Feb 1994 | CN |
2394309 | Aug 2000 | CN |
1533128 | Sep 2004 | CN |
1542497 | Nov 2004 | CN |
2672832 | Jan 2005 | CN |
1624842 | Jun 2005 | CN |
1812030 | Aug 2006 | CN |
1838036 | Sep 2006 | CN |
1855332 | Nov 2006 | CN |
101051569 | Oct 2007 | CN |
200961844 | Oct 2007 | CN |
200986871 | Dec 2007 | CN |
101146137 | Mar 2008 | CN |
201054315 | Apr 2008 | CN |
201084602 | Jul 2008 | CN |
201123174 | Sep 2008 | CN |
201149829 | Nov 2008 | CN |
101315841 | Dec 2008 | CN |
201210457 | Mar 2009 | CN |
101438228 | May 2009 | CN |
101465226 | Jun 2009 | CN |
101494130 | Jul 2009 | CN |
101502082 | Aug 2009 | CN |
201298481 | Aug 2009 | CN |
101546667 | Sep 2009 | CN |
101572195 | Nov 2009 | CN |
101800281 | Aug 2010 | CN |
101807482 | Aug 2010 | CN |
101868773 | Oct 2010 | CN |
201655616 | Nov 2010 | CN |
102110542 | Jun 2011 | CN |
102119430 | Jul 2011 | CN |
201904256 | Jul 2011 | CN |
102163084 | Aug 2011 | CN |
201927524 | Aug 2011 | CN |
201945951 | Aug 2011 | CN |
201945952 | Aug 2011 | CN |
201956238 | Aug 2011 | CN |
102197452 | Sep 2011 | CN |
102214038 | Oct 2011 | CN |
202008941 | Oct 2011 | CN |
202040690 | Nov 2011 | CN |
102280292 | Dec 2011 | CN |
102338348 | Feb 2012 | CN |
102375550 | Mar 2012 | CN |
202205161 | Apr 2012 | CN |
102496509 | Jun 2012 | CN |
10269527 | Aug 2012 | CN |
102622089 | Aug 2012 | CN |
102629526 | Aug 2012 | CN |
202372927 | Aug 2012 | CN |
102679239 | Sep 2012 | CN |
102683072 | Sep 2012 | CN |
202434387 | Sep 2012 | CN |
102713805 | Oct 2012 | CN |
202523007 | Nov 2012 | CN |
102832068 | Dec 2012 | CN |
102955573 | Mar 2013 | CN |
102956386 | Mar 2013 | CN |
102969183 | Mar 2013 | CN |
103000417 | Mar 2013 | CN |
103165327 | Jun 2013 | CN |
103180979 | Jun 2013 | CN |
203012648 | Jun 2013 | CN |
203135988 | Aug 2013 | CN |
103377841 | Oct 2013 | CN |
103489986 | Jan 2014 | CN |
203405773 | Jan 2014 | CN |
203414880 | Jan 2014 | CN |
103681056 | Mar 2014 | CN |
103699181 | Apr 2014 | CN |
203520312 | Apr 2014 | CN |
203588895 | May 2014 | CN |
103839715 | Jun 2014 | CN |
103839720 | Jun 2014 | CN |
103839722 | Jun 2014 | CN |
203630729 | Jun 2014 | CN |
103903891 | Jul 2014 | CN |
103956290 | Jul 2014 | CN |
203733685 | Jul 2014 | CN |
104021968 | Sep 2014 | CN |
204102769 | Jan 2015 | CN |
204117915 | Jan 2015 | CN |
104517769 | Apr 2015 | CN |
204632641 | Sep 2015 | CN |
105097341 | Nov 2015 | CN |
205028245 | Feb 2016 | CN |
105446646 | Mar 2016 | CN |
206339935 | Jul 2017 | CN |
2530176 | Jan 1977 | DE |
3002772 | Jul 1981 | DE |
29704100 | Apr 1997 | DE |
202008001970 | Aug 2008 | DE |
0441993 | Aug 1991 | EP |
1835272 | Sep 2007 | EP |
1928008 | Jun 2008 | EP |
2202606 | Jun 2010 | EP |
2426688 | Mar 2012 | EP |
2439760 | Apr 2012 | EP |
2463798 | Jun 2012 | EP |
2664979 | Nov 2013 | EP |
2147420 | Mar 1973 | FR |
2911000 | Jul 2008 | FR |
2950193 | Mar 2011 | FR |
1361459 | Jul 1974 | GB |
S50115562 | Sep 1975 | JP |
59171414 | Mar 1983 | JP |
S60055477 | Mar 1985 | JP |
S61172422 | Oct 1986 | JP |
S62072429 | Apr 1987 | JP |
62237618 | Oct 1987 | JP |
S63182024 | Nov 1988 | JP |
H0422024 | Apr 1992 | JP |
H0520963 | Jan 1993 | JP |
H0524512 | Aug 1993 | JP |
405225850 | Sep 1993 | JP |
H05342944 | Dec 1993 | JP |
H09204148 | Aug 1997 | JP |
H10312726 | Nov 1998 | JP |
H11194882 | Jul 1999 | JP |
2000010709 | Jan 2000 | JP |
2000057871 | Feb 2000 | JP |
2000339097 | Dec 2000 | JP |
2001100889 | Apr 2001 | JP |
2003114751 | Sep 2001 | JP |
2002260478 | Sep 2002 | JP |
2002298689 | Oct 2002 | JP |
2003522998 | Jul 2003 | JP |
2005108041 | Apr 2005 | JP |
2006164929 | Jun 2006 | JP |
2006185906 | Jul 2006 | JP |
2006521664 | Sep 2006 | JP |
2006269439 | Oct 2006 | JP |
2006277013 | Oct 2006 | JP |
2006344609 | Dec 2006 | JP |
2007115633 | May 2007 | JP |
2007514247 | May 2007 | JP |
2007156983 | Jun 2007 | JP |
2008021428 | Jan 2008 | JP |
2008041431 | Feb 2008 | JP |
2008100129 | May 2008 | JP |
2008191850 | Aug 2008 | JP |
2008533559 | Aug 2008 | JP |
2008293922 | Dec 2008 | JP |
2009099503 | May 2009 | JP |
2009181894 | Aug 2009 | JP |
2010061956 | Mar 2010 | JP |
2010244088 | Oct 2010 | JP |
2010244302 | Oct 2010 | JP |
2011018484 | Jan 2011 | JP |
2011065126 | Mar 2011 | JP |
2011150804 | Aug 2011 | JP |
2011165630 | Aug 2011 | JP |
2011524066 | Aug 2011 | JP |
2011187297 | Sep 2011 | JP |
2012022473 | Feb 2012 | JP |
2012043267 | Mar 2012 | JP |
2012043705 | Mar 2012 | JP |
2012063630 | Mar 2012 | JP |
2012083840 | Apr 2012 | JP |
2012088215 | May 2012 | JP |
2012098873 | May 2012 | JP |
2012134064 | Jul 2012 | JP |
2012186067 | Sep 2012 | JP |
2012230256 | Nov 2012 | JP |
2013511108 | Mar 2013 | JP |
2014017179 | Jan 2014 | JP |
2014026807 | Feb 2014 | JP |
2014216190 | Nov 2014 | JP |
2014220039 | Nov 2014 | JP |
2016053778 | Apr 2016 | JP |
2016510547 | Apr 2016 | JP |
1019990007394 | Jan 1999 | KR |
1020020001668 | Jan 2002 | KR |
100454203 | Oct 2004 | KR |
1020060083032 | Jul 2006 | KR |
1020080064116 | Jul 2008 | KR |
1020080066164 | Jul 2008 | KR |
2020110006385 | Jun 2011 | KR |
1020120062797 | Jun 2012 | KR |
1020130040131 | Apr 2013 | KR |
20150024201 | Mar 2015 | KR |
200703396 | Jan 2007 | TW |
M334397 | Jun 2008 | TW |
201108284 | Mar 2011 | TW |
201108286 | Mar 2011 | TW |
M407429 | Jul 2011 | TW |
201246251 | Nov 2012 | TW |
201403646 | Jan 2014 | TW |
WO9744946 | Nov 1997 | WO |
WO2005057320 | Jun 2005 | WO |
WO2006022313 | Mar 2006 | WO |
WO2007049253 | May 2007 | WO |
WO2008045833 | Apr 2008 | WO |
WO2009005026 | Jan 2009 | WO |
WO2012011282 | Jan 2012 | WO |
WO2012027978 | Mar 2012 | WO |
WO2013096478 | Jun 2013 | WO |
WO2014175446 | Oct 2014 | WO |
Entry |
---|
Elekson, “Reliable and Tested Wearable Electronics Embedment Solutions,” http://www.wearable.technology/our-technologies, 3 pages, at least as early as Jan. 6, 2016. |
Number | Date | Country | |
---|---|---|---|
20180074694 A1 | Mar 2018 | US |
Number | Date | Country | |
---|---|---|---|
62393989 | Sep 2016 | US |