Patent Grant
12073710
Embodiments relate generally to an electronic watch or other electronic device. More particularly, the described embodiments relate to haptic button assemblies configured to receive inputs and provide haptic outputs at an electronic device.
Typically, electronic devices include various buttons or input devices that are used to control the device or provide user input. However, traditional electromagnetic buttons may require a significant amount of space and provide limited functionality. The input devices and techniques described herein are directed to an input device that includes an integrated haptic mechanism that is configured to produce a tactile or perceptible feedback to a user when operating the input device.
Embodiments of the systems, devices, methods, and apparatuses described in the present disclosure are directed to haptic button assemblies configured to receive inputs and provide haptic outputs at an electronic device.
One embodiment may take the form of an electronic device. The electronic device may include an enclosure, a haptic button assembly, and a processing unit. The enclosure may include a sidewall that defines an opening. The haptic button assembly may include an input member positioned within the opening and defining an input surface. The haptic button assembly may further include an input sensor configured to detect an input applied to the input surface. The haptic button assembly may further include a magnetic component positioned in the enclosure and coupled to the input member. The magnetic component may be configured to generate a magnetic flux. The haptic button assembly may further include a conduction loop having a conductive segment configured to conduct an electrical current through the magnetic flux in a direction that is transverse to a local flux direction of the magnetic flux. The processing unit may be positioned in the enclosure and configured to, in response to the input sensor detecting the input, cause the electrical current to conduct through the conduction loop, causing a lateral translation of the input member in a translation direction that is substantially parallel to the input surface, thereby producing a haptic output.
Another embodiment may take the form of a haptic button assembly for an electronic device. The haptic button assembly may include an input member defining an input surface and configured to translate along a first translation direction that is substantially parallel to the input surface and a second translation direction opposite to the first translation direction. The haptic button assembly may further include a support member coupled to the input member and configured to extend through a hole defined in an enclosure of the electronic device. The haptic button assembly may further include a magnetic component attached to the support member and configured to generate a magnetic flux. The haptic button assembly may further include a first conductive segment configured to pass a first electrical signal through the magnetic flux thereby causing the input member to move in the first translation direction to produce a first component of a haptic output. The haptic button assembly may further include a second conductive segment configured to pass a second electrical signal through the magnetic flux thereby causing the input member to move in the second translation direction to produce a second component of the haptic output.
Another embodiment may take the form of an electronic device comprising an enclosure, a haptic button assembly and a processing unit. The enclosure may include a sidewall that defines an opening. The haptic button assembly may include an input member positioned within the opening and defining an input surface. The haptic button assembly may further include a contact member coupled to the input member and positioned inward of the input surface. The haptic button assembly may further include a spring member positioned along a side of the contact member. The haptic button assembly may further include a conductive coil positioned along a side of the spring member opposite to the contact member. The processing unit may be configured to cause an electrical current to be applied to the conductive coil, thereby deflecting the spring member away from the contact member. The processing unit may be further configured to cause the electrical current applied to the conductive coil to be reduced or cease thereby causing the spring member to contact the contact member resulting in a haptic output at the input surface.
In addition to the example aspects and embodiments described above, further aspects and embodiments will become apparent by reference to the drawings and by study of the following description.
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 description is 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 a haptic button assembly for detecting inputs and providing haptic outputs at an electronic device. The haptic outputs may be provided in response to detected inputs or in response to other conditions at the electronic device. The haptic button assembly may define an input surface along an exterior of the electronic device. Inputs may be provided to the input surface of the haptic button assembly. An input may include a touch input on or along the input surface and/or a force input directed substantially perpendicularly to the input surface. The haptic button assembly may provide a haptic output by causing a lateral translation of an input member of the haptic button assembly.
As used herein, a “lateral translation” generally refers to side-to-side motion and/or motion that is substantially parallel to an input surface. As used herein, items, surfaces, directions, and the like are “substantially parallel” to one another if they are parallel or within a threshold amount (e.g., 5 degrees, 10 degrees, etc.) of being parallel to one another. As used herein, items, directions, surfaces, and the like are “substantially perpendicular” to one another if they are perpendicular or within a threshold amount (e.g., 5 degrees, 10 degrees, etc.) of being perpendicular to one another.
As used herein, the term “haptic output” may refer to outputs produced by the electronic device that may be perceived through user touch. Without limitation, a haptic output may include an impulse, a vibration, or other type of movement of a surface of the electronic device that may be perceived through a touch of the user. In some cases, a haptic button assembly may vibrate, displace, and/or deflect a device component (e.g., an enclosure, a cover, or an input device) to produce a haptic output at an external surface of the device defined by the device component. In some cases, haptic outputs may be produced by relative movement of one or more device components with respect to one or more additional device components. As one example, a haptic button assembly may cause a first device component (for example, an input member) to vibrate, oscillate, rotate and/or translate relative to another device component (for example, a device enclosure) to produce a haptic output that may be perceived by a user.
Whereas traditional buttons and similar input devices may have an translating member that translates in response to an input, the haptic button assemblies described herein may not actually translate inward in response to the input, or may translate inward a very small amount that would not normally be perceivable by a user (e.g., less than 10 microns). In some cases, the haptic outputs provided by the haptic button assembly may simulate the feeling of providing input to a traditional input device. For example, the haptic button assembly may provide a haptic output in response to detecting an input to mimic the downward and/or upward travel of a traditional button press operation. To provide haptic outputs, the input member of the haptic button assembly may translate laterally a distance that is perceptible to a user (e.g., greater than 50 microns, greater than 100 microns, or more).
The haptic button assemblies described herein may include a haptic engine for providing haptic outputs by causing the input member to move or vibrate. The haptic engine may include electromagnetic components such as conduction loops and magnetic components, vibrating motors, such as eccentric rotating mass vibration motors, piezoelectric elements, and other suitable mechanisms for providing haptic outputs by causing the input member to move or vibrate.
The haptic button assembly may include one or more conduction loops and one or more magnetic components for providing haptic outputs by generating electromagnetic forces that cause the input member to move. The magnetic components or the conduction loops may be coupled to the input member. A processing unit of the electronic device may cause electrical signals (e.g., electrical current, electromagnetic signals, drive signals, and the like) to pass through the conduction loops. The electrical signals induced in the conduction loops may result in a Lorentz force that can cause the conduction loops and/or the magnetic components to move, thereby causing the input member to move. The term conduction loop may be used generally to refer to various implementations that may also be described as a coil, wire coil, conductive winding, spool, or the like. The conduction loops may include electromagnetic coils, electrically conductive coils, wire loops, other electrically conductive materials, and the like. The magnetic components may include permanent magnets, electromagnets, and the like.
The conduction loops may be attached or coupled to an enclosure of the electronic device, and the magnetic components may be attached or coupled to an actuation member that moves with the input member. In other embodiments, the magnetic components may be attached or coupled to an enclosure of the electronic device, and the conduction loops may be attached or coupled to an actuation member that moves with the input member.
Each magnetic component generates a magnetic flux. A pole of a magnetic component may be directed toward a conductive segment of a conduction loop such that the conductive segment passes through a portion of a magnetic field produced by or emanating from the pole of the magnetic component. The portion of the magnetic field that the conductive segment passes through may predominantly be composed of magnetic flux directed in a single direction (a “local flux direction”). The conductive segment may pass an electrical current through the magnetic flux in a direction that is transverse to the local flux direction. As used herein, the term “transverse” refers to directions, surfaces, lines, and the like that are not parallel and/or that extend across one another. The conductive segment may pass an electrical current through the magnetic flux in a direction that is substantially perpendicular to the local flux direction.
According to the Lorentz force law, for each conduction loop, the electrical current conducted through the magnetic flux in a direction that is transverse to the local flux direction of the magnetic flux produces a Lorentz force that is substantially perpendicular to the electrical current and the local flux direction. This Lorentz force may cause the magnetic components and/or the conduction loops to move laterally with respect to one another, thereby causing lateral translation of the input member in a direction that is substantially perpendicular to both the electrical current flowing through the segment and the magnetic flux and substantially parallel to the input surface.
The term “attached,” as used herein, may be used to refer to two or more elements, structures, objects, components, parts or the like that are physically affixed, fastened, and/or retained to one another. The term “coupled,” as used herein, may be used to refer to two or more elements, structures, objects, components, parts or the like that are physically attached to one another, operate with one another, communicate with one another, are in electrical connection with one another, and/or otherwise interact with one another. Accordingly, while elements attached to one another are coupled to one another, the reverse is not required. As used herein, “operably coupled” or “electrically coupled” may be used to refer to two or more devices that are coupled in any suitable manner for operation and/or communication, including wiredly, wirelessly, or some combination thereof. As used herein, the term “abutting” means that two elements share a common boundary or otherwise contact one another, while the term “adjacent” means that two elements are near one another and may (or may not) contact one another. Thus, elements that are abutting are also adjacent, although the reverse is not necessarily true.
These and other embodiments are discussed with reference to
The haptic button assembly 110 may receive inputs and provide haptic outputs. The haptic button assembly 110 may extend at least partially through an opening 103 in the enclosure 102, such as an opening in a sidewall of the enclosure 102. The haptic button assembly 110 may be positioned beneath and/or define an input surface 113 of the electronic device 100. The haptic button assembly 110 may include an input member 112 that defines the input surface 113. The haptic button assembly 110 may further include a haptic engine 114 for producing haptic outputs at the input surface 113 and an input sensor 116 for detecting inputs to the haptic button assembly 110.
Inputs may be provided to the input surface 113 of the haptic button assembly 110. An input (e.g., input I shown in
The input sensor 116 is operably coupled to the input surface 113 and configured to output a signal in response to detecting the input I. In various embodiments, the input sensor 116 may measure inputs using a variety of methods and techniques, including strain sensing, piezoresistive strain gauge, capacitive touch sensing, capacitive force sensing, contact sensing, electromechanical switch, electromagnetic, piezoelectric, optical, potentiometric, and so on.
The haptic engine 114 may provide haptic outputs by moving the input member 112. In some cases, the haptic engine 114 may provide a haptic output by causing a lateral translation of the input member in one or more translation directions that are substantially parallel to the input surface 113 (indicated by the line M). This motion may be substantially perpendicular to an input force applied to the input surface 113.
The haptic engine 114 may provide a first haptic output component of a haptic output by moving the input member 112 in a first direction substantially parallel to the input surface 113 and a second haptic output component of the haptic output by moving the input member in a second direction, opposite the first direction, and substantially parallel to the input surface 113. Additionally or alternatively, the haptic engine 114 may provide a haptic output by moving the input member 112 inward and/or outward substantially perpendicularly to the input surface 113, vibrating the input member 112, rotating the input member 112, oscillating the input member, and the like.
As noted herein, the haptic engine 114 may provide haptic outputs in response to inputs received at the input surface 113. The haptic engine 114 may provide different haptic outputs for different levels of input. For example, if the input is a touch input, the haptic output may be provided by moving the input member 112 in one direction. Additionally or alternatively, if the input is a force input, the haptic output may be provided by moving the input member 112 in two or more directions (e.g., back and forth) and/or vibrating the input member 112. In some cases, if the force input is below a force threshold, the haptic output may be provided by moving the input member in two or more directions, and if the force input is at or above a force threshold, the haptic output may be provided by vibrating the input member 112. The different inputs received at the input surface 113 may correspond to different functions, which may each result in operational changes of the electronic device 100, including different graphical outputs, user interface changes, and the like. The haptic outputs provided by the haptic button assembly 110 may correspond to these operational changes of the electronic device 100.
The haptic engine 114 may produce haptic outputs by generating electromagnetic forces that cause the input member 112 to move. The haptic engine 114 may include one or more conduction loops and one or more magnetic components for providing haptic outputs by generating electromagnetic forces that cause the input member 112 to move. The magnetic components or the conduction loops may be coupled to the input member 112. Electrical signals (e.g., electrical current, electromagnetic signals, drive signals, and the like) induced in and carried by the conduction loops result in a Lorentz force that can cause the conduction loops and/or the magnetic components to move, thereby causing the input member 112 to move. The conduction loops may include electromagnetic coils, electrically conductive coils, wire loops, other electrically conductive materials, and the like. The magnetic components may include permanent magnets, electromagnets, and the like. Embodiments using conduction loops and/or magnetic components are discussed in more detail with respect to
The haptic engine 114 may include a motor, an actuator, or the like for providing haptic outputs. In some cases, the haptic engine 114 may include a vibration motor, such as an eccentric rotating mass vibration motor. The motor may be positioned at least partially within or otherwise coupled to the input member 112, and may cause the input member to vibrate to provide a haptic output. Embodiments using motors are discussed in more detail with respect to
The haptic button assembly 110 may produce haptic outputs in response to receiving one or more signals from the processing unit 126. In some cases, the haptic outputs may correspond to inputs received by the electronic device 100 and/or outputs provided by the electronic device. The haptic outputs may correspond to operational states, events, or other conditions at the electronic device 100, including inputs received at the electronic device (e.g., touch inputs, rotational inputs, translational inputs), outputs of the electronic device (e.g., graphical outputs, audio outputs, haptic outputs), applications and processes executing on the electronic device, predetermined sequences, user interface commands (e.g., volume, zoom, or brightness controls, audio or video controls, scrolling on a list or page, and the like), and the like. The haptic button assembly 110 may be operably coupled to the processing unit 126 via a connector 128a and/or via one or more additional components of the electronic device 100.
Haptic outputs produced by the haptic button assembly 110 may be coordinated with an audio output of a speaker or another audio device of the electronic device 100. In some cases, the haptic button assembly 110 may produce audio outputs in addition to or as an alternative to producing haptic outputs. For example, actuation of the haptic button assembly 110 may produce a sound. Audio outputs may be produced in response to any of the conditions, inputs, or the like discussed above with respect to haptic outputs. In some cases, audio outputs and haptic outputs are produced by the same actuation or actuations of the haptic button assembly 110.
The display 124 may be positioned at least partially within the enclosure 102. The display 124 provides a graphical output, for example associated with an operating system, user interface, and/or applications of the electronic device 100. In one embodiment, the display 124 includes one or more sensors and is configured as a touch-sensitive (e.g., single-touch, multi-touch) and/or force-sensitive display to receive inputs from a user. The display 124 is operably coupled to the processing unit 126 of the electronic device 100, for example by a connector 128b. In some cases, the graphical output of the display 124 is visible along at least a portion of an external surface of the electronic device 100.
In various embodiments, a graphical output of the display 124 is responsive to inputs provided at the display and one or more additional input devices 120. For example, the processing unit 126 may be configured to modify the graphical output of the display 124 in response to receiving rotational inputs, receiving translational inputs, or receiving touch inputs. In some cases, a haptic output provided by the haptic button assembly 110 corresponds to the graphical output of the display 124. The haptic button assembly 110 may receive an input, and a graphical output of the display 124 may be changed and a haptic output may be provided in response to the input. In some cases, the haptic button assembly 110 may produce a haptic output that is coordinated with a change in the graphical output of the display 124. For example, the haptic output may be produced at or near the same time as the change in the graphical output of the display 124. In some cases, a time that the haptic output is produced overlaps a time that the graphical output of the display 124 changes.
The display 124 can be implemented with any suitable technology, including, but not limited to liquid crystal display (LCD) technology, light emitting diode (LED) technology, organic light-emitting display (OLED) technology, organic electroluminescence (OEL) technology, or another type of display technology. In some cases, the display 124 is positioned beneath and viewable through the cover.
Broadly, the input devices 120 may detect various types of input, and the output devices 122 may provide various types of output. While the haptic button assembly 110 may be an example of an input device 120 and/or an output device 122, the input devices 120 may generally refer to buttons, sensors, crowns, and the like, and the output devices 122 may generally refer to speakers, other haptic engines, and the like.
The processing unit 126 may be operably coupled to the input devices 120 and the output devices 122, for example by connectors 128c and 128d. The processing unit 126 may receive input signals from the input devices 120, in response to inputs detected by the input devices. The processing unit 126 may interpret input signals received from one or more of the input devices 120 and transmit output signals to one or more of the output devices 122. The output signals may cause the output devices 122 to provide one or more outputs. Detected input at one or more of the input devices 120 may be used to control one or more functions of the electronic device 100. In some cases, one or more of the output devices 122 may be configured to provide outputs that are dependent on, or manipulated in response to, the input detected by one or more of the input devices 120. The outputs provided by one or more of the output devices 122 may also be responsive to, or initiated by, a program or application executed by the processing unit 126 and/or an associated companion device. In some cases, the output devices 122 may include a speaker, and the processing unit 126 may cause the speaker to produce an audio output in conjunction with a haptic output provided using the haptic button assembly 110. Examples of suitable processing units, input devices, output devices, and displays, are discussed in more detail below with respect to
The watch body 204 may include an enclosure 202. The enclosure 202 may include a front side enclosure member that faces away from a user's skin when the watch 200 is worn by a user, and a back side enclosure member that faces toward the user's skin. Alternatively, the enclosure 202 may include a singular enclosure member, or more than two enclosure members. The one or more enclosure members may be metallic, plastic, ceramic, glass, or other types of enclosure members (or combinations of such materials).
The enclosure 202 may include a cover sheet 234 mounted to a front side of the watch body 204 (i.e., facing away from a user's skin) and may protect a display 224 mounted within the enclosure 102. The display 224 may produce graphical output that may be viewable by a user through the cover sheet 234. In some cases, the cover sheet 234 may be part of a display stack, which display stack may include a touch sensing or force sensing capability. The display may be configured to depict a graphical output of the watch 200, and a user may interact with the graphical output (e.g., using a finger, stylus, or other pointer). As one example, the user may select (or otherwise interact with) a graphic, icon, or the like presented on the display by touching or pressing (e.g., providing touch input) on the cover sheet 234 at the location of the graphic. As used herein, the term “cover sheet” may be used to refer to any transparent, semi-transparent, or translucent surface made out of glass, a crystalline material (such as sapphire or zirconia), plastic, or the like. Thus, it should be appreciated that the term “cover sheet,” as used herein, encompasses amorphous solids as well as crystalline solids. The cover sheet 234 may form a part of the enclosure 202. In some examples, the cover sheet 234 may be a sapphire cover sheet. The cover sheet 234 may also be formed of glass, plastic, or other materials.
In some embodiments, the watch body 204 may include an additional cover sheet (not shown) that forms a part of the enclosure 202. The additional cover sheet may have one or more electrodes thereon. For example, the watch body 204 may include an additional cover sheet mounted to a back side of the watch body 204 (i.e., facing toward a user's skin). The one or more electrodes on the additional cover sheet may be used to determine a biological parameter, such as a heart rate, an electrocardiogram, or the like. In some cases, the electrodes are used in combination with one or more additional electrodes, such as a surface of a crown assembly or other input device.
The watch body 204 may include at least one input device or selection device, such as a haptic button assembly, button, crown, scroll wheel, knob, dial, or the like, which input device may be operated by a user of the watch 200.
The watch 200 may include a haptic button assembly 210 similar to the haptic button assemblies described herein. The haptic button assembly 210 may be used to provide inputs to the watch 200 and to provide haptic outputs at the watch. The haptic button assembly 210 may be positioned along a portion of the enclosure 202, for example along a sidewall of the enclosure as shown in
In some embodiments, the watch 200 includes a crown 208. The enclosure 202 may define an opening through which a portion of the crown 208 extends. The crown 208 may be user-rotatable, and may be manipulated (e.g., rotated, pressed) by a user. The crown 208 may be mechanically, electrically, magnetically, and/or optically coupled to components within the enclosure 202, as one example. A user's manipulation of the crown 208 may be used, in turn, to manipulate or select various elements displayed on the display, to adjust a volume of a speaker, to turn the watch 200 on or off, and so on.
In some embodiments, the haptic button assembly 210, the crown 208, scroll wheel, knob, dial, or the like may be touch sensitive, conductive, and/or have a conductive surface, and a signal route may be provided between the conductive portion and a circuit within the watch body 204, such as a processing unit.
The enclosure 202 may include structures for attaching the watch band 206 to the watch body 204. In some cases, the structures may include elongate recesses or openings through which ends of the watch band 206 may be inserted and attached to the watch body 204. In other cases (not shown), the structures may include indents (e.g., dimples or depressions) in the enclosure 202, which indents may receive ends of spring pins that are attached to or threaded through ends of a watch band to attach the watch band to the watch body. The watch band 206 may be used to secure the watch 200 to a user, another device, a retaining mechanism, and so on.
In some examples, the watch 200 may lack any or all of the cover sheet 234, the display 224, the haptic button assembly 210, or the crown 208. For example, the watch 200 may include an audio input or output interface, a touch input interface, a force input or haptic output interface, or other input or output interface that does not require the display 224, the haptic button assembly 210, or the crown 208. The watch 200 may also include the aforementioned input or output interfaces in addition to the display 224, the haptic button assembly 210, or the crown 208. When the watch 200 lacks the display, the front side of the watch 200 may be covered by the cover sheet 234, or by a metallic or other type of enclosure member.
As noted herein, the haptic button assemblies described herein may produce haptic outputs by generating electromagnetic forces that cause the input member to move.
The conduction loops 340a-d may be fixed with respect to the enclosure. For example, the conduction loops 340a-d may be positioned in a pocket 336 (e.g., a recessed region) of the enclosure 332. The conduction loops 340a-d may be positioned within and/or at least partially surrounded by a loop housing 342. The conduction loops 340a-d may be at least partially encapsulated within the loop housing 342. As used herein, “encapsulated” may refer to a component that is contacted by and partially or completely surrounded by another component. For example, the conduction loops 340a-d may be encapsulated within the loop housing 342 by injection molding.
The actuation member 350 may be coupled to the input member 312 such that when the input member moves with the actuation member and vice versa. The input member 312 may include or be coupled to support members 332a, 332b that extend through holes 303a, 303b defined in of an enclosure 302 of the electronic device 300. The support members 332a, 332b may be attached or otherwise coupled to the actuation member 350. The support members 332a, 332b may extend at least partially through holes 356a, 356b defined in the actuation member 350.
Turning to
The electronic device 300 may register an input in response to a force or touch applied to the input surface 313. The haptic button assembly 310 may further include one or more input sensors 316a, 316b for detecting the inputs applied to the input surface 313. As shown in FIG. 3B, the input sensors 316a, 316b may be attached to the actuation member 350, and may be capable of detecting an input I applied to the input surface 313 (e.g., substantially perpendicular to the input surface). The input I may cause the input member 312 to move inward (e.g., downward with respect to
In some cases, the input sensors 316a, 316b may be configured to detect an input in response to contact between electrodes. The actuation member 350 may include a first electrode, and a second electrode may be attached to the enclosure. One or more input sensors 316a, 316b may detect the input in response to a contact between the first electrode and the second electrode.
Once an input (e.g., an input force) is removed from the input member 312, the input member 312 may return to an unactuated position. The haptic button assembly 310 may include a restoring member for applying a restorative force to the input member 312. As one example, the haptic button assembly 310 may include a restoring member 358 positioned between the actuation member 350 and the conduction loops 340a-d. The restoring member 358 may include a spring or a compliant material that allows the actuation member 350 to move laterally, while being able to provide an upward biasing force (e.g., a restorative force) on the input member 312. The input I on the input surface 313 may cause the restoring member 358 to expand as the actuation member 350, and therefore the input sensors 316a, 316b, move away from the enclosure 302. The input sensors 316a, 316b may register this change in the position of the actuation member 350 as an input. Upon removal of the input I, the restorative force exerted by the restoring member 358 may cause the actuation member 350 and the input member 312 to return to an undepressed position. The restoring member 358 is described by way of example, and is not meant to be limiting. In other embodiments, the restoring member 358 may be positioned between the input member 312 and the enclosure 302, and may be compressed in response to the input I. Additionally or alternatively, the restoring member 358 may be positioned similarly to and/or integrated with the sealing members 338a-b discussed below.
One or more magnetic components (e.g., magnetic components 352a, 352b) may be attached or otherwise coupled to the actuation member 350. The conduction loops 340a-d and the magnetic components 352a, 352b may be used to generate a haptic output by moving the input member 312. In some cases, a haptic output may be provided in response to detecting an input at the input surface 313.
As noted above, the input member 312 may be moved laterally in one or more directions that are substantially parallel to at least a portion of the input surface 313 (e.g., left and/or right with respect to
To provide haptic outputs using the haptic button assembly 310, a processing unit of the electronic device 300 may cause electrical signals (e.g., electrical current, electromagnetic signals, drive signals, and the like) to be induced in and carried by the conduction loops 340a-d, for example by a processing unit. The electrical signals in the conduction loops 340a-d and the magnetic flux generated by the magnetic components 352a, 352b may interact to cause a resulting force, such as a Lorenz force. This force may generate a haptic output by causing the actuation member 350, and therefore the input member 312, to translate laterally.
A pole of each magnetic component 352a, 352b may face (e.g., be directed toward) one or more conductive segments 344a-d of the conduction loops 340a-d such that each conductive segment passes through a portion of a magnetic field produced by or emanating from the pole of the magnetic component. The portion of the magnetic field that the conductive segment 344a-d passes through may predominantly be composed of a localized region of magnetic flux directed in a single direction (a “local flux direction”). The local flux direction may be oriented toward the conductive segment 344a-d or away from the conductive segment and/or input surface 313, depending on the polarity of the magnetic components 352a-b. As one example, shown in
The conductive segments 344a-d may pass electrical signals through the localized regions of magnetic flux B1 and B2 in a direction that is transverse to the local flux direction. The conductive segments 344a-d may pass electrical signals through the localized regions of magnetic flux B1 and B2 in a direction that is substantially perpendicular to the local flux direction. The electrical signals may be carried in a direction that is substantially parallel to at least a portion of the input surface 313. For example, as shown in
According to the Lorentz force law, for each conductive segment 344a-d, the electrical current conducted through the localized region of magnetic flux B1 and B2 of the magnetic components 352a, 352b in a direction that is transverse to the local flux direction produces a Lorentz force that is substantially perpendicular to the electrical current and the local flux direction. This Lorentz force may be substantially parallel to at least a portion of the input surface 313 (e.g., left or right with respect to
The Lorentz force may cause the magnetic components 352a, 352b and/or the conduction loops 340a-d to move laterally with respect to one another, thereby causing lateral translation of the input member 312 in a direction that is transverse to both the electrical current flowing through the conductive segment and the magnetic flux and substantially parallel to the input surface 313. As shown in
As used herein, a “conductive segment” may refer to a portion of a conduction loop that may extend more than 5 degrees but less than 180 degrees around the conduction loop. While the conductive segments 344a-d are shown as solid blocks, the conductive segments may be formed from multiple round conductive elements (wires or strands) that are wrapped or wound to define the conduction loop.
The conduction loops 340a-d may be positioned relative to the magnetic components 352a, 352b such that the localized regions of magnetic flux B1 and B2 primarily interact with current flowing through the conductive segments 344a-d, and do not interact substantially with current flowing through other portions 346a-d of the conduction loops. Each magnetic component 352a, 352b may define a magnetic axis extending between the poles (e.g., up and down with respect to
As shown in
For each of the conduction loops 340a-d, all or a substantial portion of the electrical current flowing through the conductive segments 344 through the localized region of the magnetic flux may be flowing in substantially the same direction. For example, as shown in
The magnetic flux generated by the magnetic components 352a, 352b may be oriented predominantly in a single direction in the areas near the conductive segments 344a-d. For example, as shown in
In some cases, each conduction loop 340a-d may have electrical current induced only in one direction. Alternatively, each conduction loop 340a-d may have electrical current induced in both directions at different times or in different operational states. As such, each conduction loop 340a-d may be used to move the actuation member 350 in either direction depending on the direction of the induced electrical current. All four conduction loops 340a-d may be used to move the actuation member 350 in both directions.
The directions of electrical current and localized flux directions of the magnetic flux described with respect to
In the embodiments described above, the conduction loops are fixed with respect to the enclosure and the magnetic components move with the input member. However, this is not meant to be limiting, and in other embodiments, the magnetic components may be fixed with respect to the enclosure and the conduction loops may move with the input member. For example, the conduction loops may be attached to or coupled to the actuation member and configured to move in response to the force resulting from the magnetic flux of the magnetic components interacting with the electrical current flowing through the conduction loops.
As shown in
The haptic engine 414 may include an electromagnet 448 and a magnetic component 452. The magnetic component 452 may be coupled to an actuation member 450 that is coupled to the input member (e.g., by support members 432a, 432b). The electromagnet 448 may include a ferromagnetic core 448b that extends left to right with respect to
In response to an electrical current induced in the electromagnet, the electromagnet 448 may generate a local magnetic flux that interacts with the magnetic component 452 to cause the input member 412 to move laterally (e.g., substantially parallel to the input surface 413 or left and/or right with respect to
The electromagnet 448 may be coupled to the enclosure 402 via a bracket 460 and fasteners 462a, 462b. The haptic button assembly 410 may include one or more input sensors 416 configured to detect an input I on the input surface 413 of the input member 412. The input sensor 416 may detect inputs by detecting displacement of the actuation member 450 up and down with respect to
Similar to the haptic button assembly 310, the support members 432a, 432b may extend through holes in the enclosure 402 of the electronic device 400. The haptic button assembly 410 may include one or more sealing members 438a, 438b for preventing the ingress of contaminants into the electronic device 400. The sealing members 438a, 438b may extend around the support members 432a, 432b and form a seal between the support members and the enclosure 402 when the support members are positioned in the holes. The sealing members 438a, 438b may be formed of a compliant material that allows the input member 412 to translate relative to the enclosure 402 to provide haptic outputs.
The haptic button assemblies 310, 410 provide haptic outputs by causing lateral translation of the input members 312, 412 in one or more translation directions that are substantially parallel to the input surfaces 313, 413, respectively. Additionally or alternatively, the haptic button assemblies described herein may provide haptic outputs by moving the input member inward and/or outward, or substantially perpendicular to the input surface.
As shown in
The input member 512 may include or be coupled to a contact member 570 positioned inward of the input surface 513 and/or within the enclosure 502. The contact member 570 may couple the input member to the enclosure 502. The support members 532a, 532b may be attached or otherwise coupled to the contact member 570, for example by fasteners 572a, 572b. At least a portion of the contact member 570 may extend between the support member 532a, 532b, and the contact member may limit an outward translation of the input member 512 by contacting the enclosure 502 or another component of the electronic device 500. The haptic button assembly 510 may include one or more input sensors 516a, 516b for detecting the inputs (e.g., an input I) applied to the input surface 513. As noted herein, the haptic outputs produced by the haptic engine 514 may be produced in response to detecting inputs on the input surface 513.
The haptic engine 514 may include a conduction loop (e.g., a conductive coil 540) and a spring member 550. Turning to
The spring member 550 may include a mass element 552, for example in a middle portion of the spring member 550 between the first and second ends. The mass element 552 may be a portion of the spring member 550 itself or a separate component attached to the spring member. The mass element 552 may be or include a permanent magnet (e.g., formed of or including a magnetic material), an electromagnet, or it may be or include a ferromagnetic element (e.g., formed of or including ferromagnetic material) that does not produce a magnetic field absent the influence of another magnetic field. Example magnetic materials include, but are not limited to, magnetized iron, nickel, and/or cobalt alloys (e.g., steel), ferrite, or other suitable materials. Example ferromagnetic materials include, but are not limited to, unmagnetized iron, nickel, and/or cobalt alloys (e.g., steel), ferrite, or other suitable materials.
The conductive coil 540 may be capable of attracting a portion of the spring member 550 toward the conductive coil 540 (e.g., away from the input surface, downward with respect to
Attracting the spring member 550 toward the conductive coil 540 may load the spring member 550 by moving at least a portion of the spring member 550 towards the conductive coil 540 and away from the contact member 570. In the embodiment shown in
To provide a haptic output using the haptic button assembly 510, the processing unit of the electronic device 500 may cause the electrical current being applied to the conductive coil 540 to cease or be reduced. When the electrical current being applied to the conductive coil (and therefore the reluctance force) is reduced sufficiently or ceased, the spring member 550 may release from the loaded configuration and at least a portion of the spring member 550 (e.g., the middle portion) may move toward the contact member 570. Releasing the spring member may cause the potential energy stored by the spring member 550 to be converted to kinetic energy. The spring member 550 may contact the contact member 570 and apply a force to the contact member 570 by transferring at least a portion of the kinetic energy to the contact member 570. This force may cause an impulse, vibration, or other movement of the contact member 570, and therefore the input member 512, to produce a haptic output at the input surface 513. The force may cause an outward translation of the input member 512 with respect to the enclosure 502 (e.g., upward with respect to
The input sensors 516a, 516b may be positioned between the contact member 570 and the bracket 560, such that the input Ion the input surface 513 exerts a compressive force on the input sensors 516a, 516b that is equal or proportional to a force of the input I applied to the input surface 513. The input sensors 516a, 516b may be any suitable type of sensor, including capacitive sensors, contact sensors, strain sensors, optical sensors, electromagnetic sensors, piezoelectric sensors, and the like.
The haptic button assembly 510 may include one or more sealing members 538a, 538b for preventing the ingress of contaminants into the electronic device 500. The sealing members 538a, 538b may extend around the support members 532a, 532b and form a seal between the support members and the enclosure 502 when the support members are positioned in the holes 503a, 503b. The sealing members 538a, 538b may be formed of a compliant material that allows the input member 512 to move relative to the enclosure 502 to provide haptic outputs.
As noted above, the haptic engine of the haptic button assemblies described herein may include a vibration motor, such as an eccentric rotating mass vibration motor.
The haptic button assembly 610 may include an input member 612 and a haptic engine 614. The haptic engine 614 may include an eccentric rotating mass vibration motor for providing haptic outputs at an input surface of the input member. The haptic engine 614 may cause the input member 612 to vibrate to provide haptic outputs at the input surface 613. The haptic engine 614 may be positioned in a recess 615 in the input member 612. The input member 612 may extend at least partially through an opening 636 in an enclosure 602 of the electronic device 600. The input member 612 may be retained in the opening 636 by a bracket 660, for example using fasteners 662a, 662b.
The haptic button assembly 610 may include one or more input sensors 616 for detecting the inputs applied to the input surface 613. The input sensor 616 may detect an input I applied to the input surface 613. The input sensor 616 may be positioned between the input member 612 and the bracket 660, such that the input I on the input surface 613 exerts a compressive force on the input sensor 616 that is equal or proportional to a force of the input I applied to the input surface 613. The input sensor 616 may be any suitable type of sensor, including capacitive sensors, contact sensors, strain sensors, optical sensors, electromagnetic sensors, piezoelectric sensors, and the like.
The haptic button assembly 610 may include one or more sealing members 638 for preventing the ingress of contaminants into the electronic device 600. The sealing member 638 may extend around the input member 612 and form a seal between the input member and the enclosure 602 when the input member is positioned in the opening 636. The sealing member 638 may be formed of a compliant material that allows the input member 612 to vibrate relative to the enclosure 602 to provide haptic outputs.
As noted above, the haptic engine of the haptic button assemblies described herein may include a piezoelectric element for providing haptic outputs.
The actuation member 750 may be coupled to the input member 712 such that when the input member moves with the actuation member and vice versa. The input member 712 may include or be coupled to support members 732a, 732b that extend through holes defined in an enclosure 702 of the electronic device 700. The support members 732a, 732b may be attached or otherwise coupled to the actuation member 750. The support members 732a, 732b may extend at least partially through holes defined in the actuation member 750.
The piezoelectric element 780 may be attached or otherwise coupled to the enclosure 702. The piezoelectric element 780 may be configured to actuate in response to an electrical signal (e.g., a voltage) being applied to the piezoelectric element. The piezoelectric element 780 may be attached or otherwise coupled to the actuation member 750 such that actuation of the piezoelectric element 780 causes the actuation member 750, and therefore the input member 712 to move, thereby producing a haptic output at the input surface 713.
The piezoelectric element 780 may actuate in a variety of ways to produce haptic outputs at the input surface 713. The piezoelectric element may define a longitudinal axis that is substantially parallel to the input surface 713 (e.g., left to right with respect to
In other embodiments, the piezoelectric element 780 may elongate and/or contract along the longitudinal axis to provide haptic outputs. In response to a voltage applied along the longitudinal axis of the piezoelectric element 780, the piezoelectric element may elongate and/or contract along a direction that is substantially parallel to the longitudinal axis, which may result in movement of the input member 712 that is substantially parallel to the input surface 713 (e.g., left and/or right with respect to
The processing unit 802 can control some or all of the operations of the electronic device 800. The processing unit 802 can communicate, either directly or indirectly, with some or all of the components of the electronic device 800. For example, a system bus or other communication mechanism 816 can provide communication between the processing unit 802, the power source 814, the memory 804, the input device(s) 806, and the output device(s) 810.
The processing unit 802 can be implemented as any electronic device capable of processing, receiving, or transmitting data or instructions. For example, the processing unit 802 can be a microprocessor, a central processing unit (CPU), an application-specific integrated circuit (ASIC), a digital signal processor (DSP), or combinations of such devices. As described herein, the term “processing unit” is meant to encompass a single processor or processing unit, multiple processors, multiple processing units, or other suitably configured computing element or elements.
It should be noted that the components of the electronic device 800 can be controlled by multiple processing units. For example, select components of the electronic device 800 (e.g., an input device 806) may be controlled by a first processing unit and other components of the electronic device 800 (e.g., the display 812) may be controlled by a second processing unit, where the first and second processing units may or may not be in communication with each other. In some cases, the processing unit 802 may determine a biological parameter of a user of the electronic device, such as an ECG for the user.
The power source 814 can be implemented with any device capable of providing energy to the electronic device 800. For example, the power source 814 may be one or more batteries or rechargeable batteries. Additionally or alternatively, the power source 814 can be a power connector or power cord that connects the electronic device 800 to another power source, such as a wall outlet.
The memory 804 can store electronic data that can be used by the electronic device 800. For example, the memory 804 can store electrical data or content such as, for example, audio and video files, documents and applications, device settings and user preferences, timing signals, control signals, and data structures or databases. The memory 804 can be configured as any type of memory. By way of example only, the memory 804 can be implemented as random access memory, read-only memory, Flash memory, removable memory, other types of storage elements, or combinations of such devices.
In various embodiments, the display 812 provides a graphical output, for example associated with an operating system, user interface, and/or applications of the electronic device 800. In one embodiment, the display 812 includes one or more sensors and is configured as a touch-sensitive (e.g., single-touch, multi-touch) and/or force-sensitive display to receive inputs from a user. For example, the display 812 may be integrated with a touch sensor (e.g., a capacitive touch sensor) and/or a force sensor to provide a touch- and/or force-sensitive display. The display 812 is operably coupled to the processing unit 802 of the electronic device 800.
The display 812 can be implemented with any suitable technology, including, but not limited to liquid crystal display (LCD) technology, light emitting diode (LED) technology, organic light-emitting display (OLED) technology, organic electroluminescence (OEL) technology, or another type of display technology. In some cases, the display 812 is positioned beneath and viewable through a cover that forms at least a portion of an enclosure of the electronic device 800.
In various embodiments, the input devices 806 may include any suitable components for detecting inputs. Examples of input devices 806 include audio sensors (e.g., microphones), optical or visual sensors (e.g., cameras, visible light sensors, or invisible light sensors), proximity sensors, touch sensors, force sensors, mechanical devices (e.g., crowns, switches, buttons, or keys), vibration sensors, orientation sensors, motion sensors (e.g., accelerometers or velocity sensors), location sensors (e.g., global positioning system (GPS) devices), thermal sensors, communication devices (e.g., wired or wireless communication devices), resistive sensors, magnetic sensors, electroactive polymers (EAPs), strain gauges, electrodes, and so on, or some combination thereof. Each input device 806 may be configured to detect one or more particular types of input and provide a signal (e.g., an input signal) corresponding to the detected input. The signal may be provided, for example, to the processing unit 802.
As discussed above, in some cases, the input device(s) 806 include a touch sensor (e.g., a capacitive touch sensor) integrated with the display 812 to provide a touch-sensitive display. Similarly, in some cases, the input device(s) 806 include a force sensor (e.g., a capacitive force sensor) integrated with the display 812 to provide a force-sensitive display.
The output devices 810 may include any suitable components for providing outputs. Examples of output devices 810 include audio output devices (e.g., speakers), visual output devices (e.g., lights or displays), haptic output devices (e.g., haptic output devices), communication devices (e.g., wired or wireless communication devices), and so on, or some combination thereof. Each output device 810 may be configured to receive one or more signals (e.g., an output signal provided by the processing unit 802) and provide an output corresponding to the signal.
In some cases, input devices 806 and output devices 810 are implemented together as a single device. For example, an input/output device or port can transmit electronic signals via a communications network, such as a wireless and/or wired network connection. Examples of wireless and wired network connections include, but are not limited to, cellular, Wi-Fi, Bluetooth, IR, and Ethernet connections.
The processing unit 802 may be operably coupled to the input devices 806 and the output devices 810. The processing unit 802 may be adapted to exchange signals with the input devices 806 and the output devices 810. For example, the processing unit 802 may receive an input signal from an input device 806 that corresponds to an input detected by the input device 806. The processing unit 802 may interpret the received input signal to determine whether to provide and/or change one or more outputs in response to the input signal. The processing unit 802 may then send an output signal to one or more of the output devices 810, to provide and/or change outputs as appropriate.
The foregoing description, for purposes of explanation, uses 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.
Although the disclosure above is described in terms of various exemplary embodiments and implementations, it should be understood that the various features, aspects and functionality described in one or more of the individual embodiments are not limited in their applicability to the particular embodiment with which they are described, but instead can be applied, alone or in various combinations, to one or more of the some embodiments of the invention, whether or not such embodiments are described and whether or not such features are presented as being a part of a described embodiment. Thus, the breadth and scope of the present invention should not be limited by any of the above-described exemplary embodiments but is instead defined by the claims herein presented.
One may appreciate that although many embodiments are disclosed above, that the operations and steps presented with respect to methods and techniques described herein are meant as exemplary and accordingly are not exhaustive. One may further appreciate that alternate step order or fewer or additional operations may be required or desired for particular embodiments.
As used herein, the phrase “at least one of” preceding a series of items, with the term “and” or “or” to separate any of the items, modifies the list as a whole, rather than each member of the list. The phrase “at least one of” does not require selection of at least one of each item listed; rather, the phrase allows a meaning that includes at a minimum one of any of the items, and/or at a minimum one of any combination of the items, and/or at a minimum one of each of the items. By way of example, the phrases “at least one of A, B, and C” or “at least one of A, B, or C” each refer to only A, only B, or only C; any combination of A, B, and C; and/or one or more of each of A, B, and C. Similarly, it may be appreciated that an order of elements presented for a conjunctive or disjunctive list provided herein should not be construed as limiting the disclosure to only that order provided.
The present disclosure recognizes that personal information data, including biometric data, in the present technology, can be used to the benefit of users. For example, the use of biometric authentication data can be used for convenient access to device features without the use of passwords. In other examples, user biometric data is collected for providing users with feedback about their health or fitness levels. Further, other uses for personal information data, including biometric data, that benefit the user are also contemplated by the present disclosure.
The present disclosure further contemplates that the entities responsible for the collection, analysis, disclosure, transfer, storage, or other use of such personal information data will comply with well-established privacy policies and/or privacy practices. In particular, such entities should implement and consistently use privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining personal information data private and secure, including the use of data encryption and security methods that meets or exceeds industry or government standards. For example, personal information from users should be collected for legitimate and reasonable uses of the entity and not shared or sold outside of those legitimate uses. Further, such collection should occur only after receiving the informed consent of the users. Additionally, such entities would take any needed steps for safeguarding and securing access to such personal information data and ensuring that others with access to the personal information data adhere to their privacy policies and procedures. Further, such entities can subject themselves to evaluation by third parties to certify their adherence to widely accepted privacy policies and practices.
Despite the foregoing, the present disclosure also contemplates embodiments in which users selectively block the use of, or access to, personal information data, including biometric data. That is, the present disclosure contemplates that hardware and/or software elements can be provided to prevent or block access to such personal information data. For example, in the case of biometric authentication methods, the present technology can be configured to allow users to optionally bypass biometric authentication steps by providing secure information such as passwords, personal identification numbers (PINS), touch gestures, or other authentication methods, alone or in combination, known to those of skill in the art. In another example, users can select to remove, disable, or restrict access to certain health-related applications collecting users' personal health or fitness data.
This application is a continuation of U.S. patent application Ser. No. 17/332,795, filed May 27, 2021, now U.S. Pat. No. 11,756,392, which is a continuation of U.S. patent application Ser. No. 16/904,409, filed Jun. 17, 2020, now U.S. Pat. No. 11,024,135, the contents of which are incorporated herein by reference as if fully disclosed herein.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5196745 | Trumper et al. | Mar 1993 | A |
| 5293161 | MacDonald et al. | Mar 1994 | A |
| 5424756 | Ho et al. | Jun 1995 | A |
| 5434549 | Hirabayashi et al. | Jul 1995 | A |
| 5436622 | Gutman et al. | Jul 1995 | A |
| 5668423 | You et al. | Sep 1997 | A |
| 5842967 | Kroll | Jan 1998 | A |
| 5739759 | Nakazawa et al. | Apr 1998 | A |
| 6084319 | Kamata et al. | Jul 2000 | A |
| 6342880 | Rosenberg et al. | Jan 2002 | B2 |
| 6373465 | Jolly et al. | Apr 2002 | B2 |
| 6388789 | Bernstein | May 2002 | B1 |
| 6438393 | Surronen | Aug 2002 | B1 |
| 6445093 | Binnard | Sep 2002 | B1 |
| 6493612 | Bisset et al. | Dec 2002 | B1 |
| 6554191 | Yoneya | Apr 2003 | B2 |
| 6693622 | Shahoian et al. | Feb 2004 | B1 |
| 6777895 | Shimoda et al. | Aug 2004 | B2 |
| 6822635 | Shahoian | Nov 2004 | B2 |
| 6864877 | Braun et al. | Mar 2005 | B2 |
| 6952203 | Banerjee et al. | Oct 2005 | B2 |
| 6988414 | Ruhrig et al. | Jan 2006 | B2 |
| 7068168 | Girshovich et al. | Jun 2006 | B2 |
| 7080271 | Kardach et al. | Jul 2006 | B2 |
| 7126254 | Nanataki et al. | Oct 2006 | B2 |
| 7130664 | Williams | Oct 2006 | B1 |
| 7196688 | Shena et al. | Mar 2007 | B2 |
| 7202851 | Cunningham | Apr 2007 | B2 |
| 7234379 | Claesson et al. | Jun 2007 | B2 |
| 7253350 | Noro et al. | Aug 2007 | B2 |
| 7276907 | Kitagawa et al. | Oct 2007 | B2 |
| 7321180 | Takeuchi et al. | Jan 2008 | B2 |
| 7323959 | Naka et al. | Jan 2008 | B2 |
| 7336006 | Watanabe et al. | Feb 2008 | B2 |
| 7339572 | Schena | Mar 2008 | B2 |
| 7355305 | Nakamura et al. | Apr 2008 | B2 |
| 7360446 | Dai et al. | Apr 2008 | B2 |
| 7370289 | Ebert et al. | May 2008 | B1 |
| 7385874 | Vuilleumier | Jun 2008 | B2 |
| 7392066 | Hapamas | Jun 2008 | B2 |
| 7423631 | Shahoian et al. | Sep 2008 | B2 |
| 7508382 | Denoue et al. | Mar 2009 | B2 |
| 7570254 | Suzuki et al. | Aug 2009 | B2 |
| 7576477 | Koizumi | Aug 2009 | B2 |
| 7656388 | Schena et al. | Feb 2010 | B2 |
| 7667371 | Sadler et al. | Feb 2010 | B2 |
| 7667691 | Boss et al. | Feb 2010 | B2 |
| 7675414 | Ray | Mar 2010 | B2 |
| 7710397 | Krah et al. | May 2010 | B2 |
| 7710399 | Bruneau et al. | May 2010 | B2 |
| 7741938 | Kramlich | Jun 2010 | B2 |
| 7755605 | Daniel et al. | Jul 2010 | B2 |
| 7798982 | Zets et al. | Sep 2010 | B2 |
| 7825903 | Anastas et al. | Nov 2010 | B2 |
| 7855657 | Doemens et al. | Dec 2010 | B2 |
| 7890863 | Grant et al. | Feb 2011 | B2 |
| 7893922 | Klinghult et al. | Feb 2011 | B2 |
| 7904210 | Pfau et al. | Mar 2011 | B2 |
| 7911328 | Luden et al. | Mar 2011 | B2 |
| 7919945 | Houston et al. | Apr 2011 | B2 |
| 7952261 | Lipton et al. | May 2011 | B2 |
| 7952566 | Poupyrev et al. | May 2011 | B2 |
| 7956770 | Klinghult et al. | Jun 2011 | B2 |
| 7976230 | Ryynanen et al. | Jul 2011 | B2 |
| 8002089 | Jasso et al. | Aug 2011 | B2 |
| 8020266 | Ulm et al. | Sep 2011 | B2 |
| 8040224 | Hwang | Oct 2011 | B2 |
| 8053688 | Conzola et al. | Nov 2011 | B2 |
| 8063892 | Shahoian | Nov 2011 | B2 |
| 8072418 | Crawford et al. | Dec 2011 | B2 |
| 8081156 | Ruettiger | Dec 2011 | B2 |
| 8125453 | Shahoian et al. | Feb 2012 | B2 |
| 8154537 | Olien et al. | Apr 2012 | B2 |
| 8174495 | Takashima et al. | May 2012 | B2 |
| 8174512 | Ramstein et al. | May 2012 | B2 |
| 8188989 | Levin | May 2012 | B2 |
| 8169402 | Shahoian et al. | Jun 2012 | B2 |
| 8217892 | Meadors | Jul 2012 | B2 |
| 8217910 | Stallings et al. | Jul 2012 | B2 |
| 8232494 | Purcocks | Jul 2012 | B2 |
| 8248386 | Harrison | Aug 2012 | B2 |
| 8253686 | Kyung | Aug 2012 | B2 |
| 8262480 | Cohen et al. | Sep 2012 | B2 |
| 8264465 | Grant et al. | Sep 2012 | B2 |
| 8265292 | Leichter | Sep 2012 | B2 |
| 8265308 | Gitzinger et al. | Sep 2012 | B2 |
| 8344834 | Niiyama | Jan 2013 | B2 |
| 8345025 | Seibert et al. | Jan 2013 | B2 |
| 8351104 | Zaifrani et al. | Jan 2013 | B2 |
| 8378797 | Pance et al. | Feb 2013 | B2 |
| 8378965 | Gregorio et al. | Feb 2013 | B2 |
| 8384316 | Houston et al. | Feb 2013 | B2 |
| 8390218 | Houston et al. | Mar 2013 | B2 |
| 8390572 | Marsden et al. | Mar 2013 | B2 |
| 8390594 | Modarres et al. | Mar 2013 | B2 |
| 8400027 | Dong et al. | Mar 2013 | B2 |
| 8405618 | Colgate et al. | Mar 2013 | B2 |
| 8421609 | Kim et al. | Apr 2013 | B2 |
| 8432365 | Kim et al. | Apr 2013 | B2 |
| 8469806 | Grant et al. | Jun 2013 | B2 |
| 8471690 | Hennig et al. | Jun 2013 | B2 |
| 8493177 | Flaherty et al. | Jul 2013 | B2 |
| 8493189 | Suzuki | Jul 2013 | B2 |
| 8562489 | Burton | Oct 2013 | B2 |
| 8576171 | Grant | Nov 2013 | B2 |
| 8598750 | Park | Dec 2013 | B2 |
| 8598972 | Cho et al. | Dec 2013 | B2 |
| 8604670 | Mahameed et al. | Dec 2013 | B2 |
| 8605141 | Dialameh et al. | Dec 2013 | B2 |
| 8614431 | Huppi et al. | Dec 2013 | B2 |
| 8619031 | Hayward | Dec 2013 | B2 |
| 8624448 | Kaiser et al. | Jan 2014 | B2 |
| 8628173 | Stephens et al. | Jan 2014 | B2 |
| 8633916 | Bernstein et al. | Jan 2014 | B2 |
| 8639485 | Connacher et al. | Jan 2014 | B2 |
| 8643480 | Maier et al. | Feb 2014 | B2 |
| 8648829 | Shahoian et al. | Feb 2014 | B2 |
| 8653785 | Collopy | Feb 2014 | B2 |
| 8654524 | Pance et al. | Feb 2014 | B2 |
| 8681130 | Adhikari | Mar 2014 | B2 |
| 8686952 | Burrough et al. | Apr 2014 | B2 |
| 8717151 | Forutanpour et al. | May 2014 | B2 |
| 8730182 | Modarres et al. | May 2014 | B2 |
| 8749495 | Grant et al. | Jun 2014 | B2 |
| 8754759 | Fadell et al. | Jun 2014 | B2 |
| 8760037 | Eshed et al. | Jun 2014 | B2 |
| 8773247 | Ullrich | Jul 2014 | B2 |
| 8780074 | Castillo et al. | Jul 2014 | B2 |
| 8797153 | Vanhelle et al. | Aug 2014 | B2 |
| 8797295 | Bernstein et al. | Aug 2014 | B2 |
| 8803670 | Steckel et al. | Aug 2014 | B2 |
| 8834390 | Couvillon | Sep 2014 | B2 |
| 8836502 | Culbert et al. | Sep 2014 | B2 |
| 8836643 | Jolliff et al. | Sep 2014 | B2 |
| 8867757 | Ooi | Oct 2014 | B1 |
| 8872448 | Boldyrev et al. | Oct 2014 | B2 |
| 8878401 | Lee | Nov 2014 | B2 |
| 8890824 | Guard | Nov 2014 | B2 |
| 8907661 | Maier et al. | Dec 2014 | B2 |
| 8976139 | Koga et al. | Mar 2015 | B2 |
| 8976141 | Myers et al. | Mar 2015 | B2 |
| 8977376 | Lin et al. | Mar 2015 | B1 |
| 8981682 | Delson et al. | Mar 2015 | B2 |
| 8987951 | Park | Mar 2015 | B2 |
| 9008730 | Kim et al. | Apr 2015 | B2 |
| 9024738 | Van Schyndel et al. | May 2015 | B2 |
| 9046947 | Takeda | Jun 2015 | B2 |
| 9049339 | Muench | Jun 2015 | B2 |
| 9052785 | Horie | Jun 2015 | B2 |
| 9054605 | Jung et al. | Jun 2015 | B2 |
| 9058077 | Lazaridis et al. | Jun 2015 | B2 |
| 9086727 | Tidemand et al. | Jul 2015 | B2 |
| 9092056 | Myers et al. | Jul 2015 | B2 |
| 9094762 | Wong et al. | Jul 2015 | B2 |
| 9104285 | Colgate et al. | Aug 2015 | B2 |
| 9116570 | Lee et al. | Aug 2015 | B2 |
| 9122330 | Bau et al. | Sep 2015 | B2 |
| 9134796 | Lemmons et al. | Sep 2015 | B2 |
| 9172669 | Swink et al. | Oct 2015 | B2 |
| 9182837 | Day | Nov 2015 | B2 |
| 9218727 | Rothkopf et al. | Dec 2015 | B2 |
| 9228908 | Aliane et al. | Jan 2016 | B2 |
| 9245704 | Maharjan et al. | Jan 2016 | B2 |
| 9256287 | Shinozaki et al. | Feb 2016 | B2 |
| 9274601 | Faubert et al. | Mar 2016 | B2 |
| 9280205 | Rosenberg et al. | Mar 2016 | B2 |
| 9285905 | Buuck et al. | Mar 2016 | B1 |
| 9286907 | Yang et al. | Mar 2016 | B2 |
| 9304587 | Wright et al. | Apr 2016 | B2 |
| 9319150 | Peeler et al. | Apr 2016 | B2 |
| 9348414 | Kagayama | May 2016 | B2 |
| 9348473 | Ando | May 2016 | B2 |
| 9361018 | Pasquero et al. | Jun 2016 | B2 |
| 9396629 | Weber et al. | Jul 2016 | B1 |
| 9430042 | Levin | Aug 2016 | B2 |
| 9436280 | Tartz et al. | Sep 2016 | B2 |
| 9442570 | Slonneger | Sep 2016 | B2 |
| 9448631 | Winter et al. | Sep 2016 | B2 |
| 9448713 | Cruz-Hernandez et al. | Sep 2016 | B2 |
| 9449476 | Lynn et al. | Sep 2016 | B2 |
| 9459734 | Day | Oct 2016 | B2 |
| 9466783 | Olien et al. | Oct 2016 | B2 |
| 9489049 | Li | Nov 2016 | B2 |
| 9496777 | Jung | Nov 2016 | B2 |
| 9501149 | Burnbaum et al. | Nov 2016 | B2 |
| 9513704 | Heubel et al. | Dec 2016 | B2 |
| 9519346 | Lacroix et al. | Dec 2016 | B2 |
| 9535500 | Pasquero et al. | Jan 2017 | B2 |
| 9539164 | Sanders et al. | Jan 2017 | B2 |
| 9542028 | Filiz et al. | Jan 2017 | B2 |
| 9557830 | Grant | Jan 2017 | B2 |
| 9557857 | Schediwy | Jan 2017 | B2 |
| 9563274 | Senanayake | Feb 2017 | B2 |
| 9564029 | Morrell et al. | Feb 2017 | B2 |
| 9594429 | Bard et al. | Mar 2017 | B2 |
| 9600037 | Pance et al. | Mar 2017 | B2 |
| 9600071 | Rothkopf | Mar 2017 | B2 |
| 9607491 | Mortimer et al. | Mar 2017 | B1 |
| 9627163 | Ely et al. | Apr 2017 | B2 |
| 9632583 | Virtanen et al. | Apr 2017 | B2 |
| 9639158 | Levesque et al. | May 2017 | B2 |
| 9666040 | Flaherty et al. | May 2017 | B2 |
| 9690379 | Tremblay | Jun 2017 | B2 |
| 9707593 | Berte | Jul 2017 | B2 |
| 9710061 | Pance et al. | Jul 2017 | B2 |
| 9727238 | Peh et al. | Aug 2017 | B2 |
| 9733704 | Cruz-Hernandez et al. | Aug 2017 | B2 |
| 9762236 | Chen et al. | Sep 2017 | B2 |
| 9823828 | Zambetti et al. | Nov 2017 | B2 |
| 9829981 | Ji | Nov 2017 | B1 |
| 9830782 | Morrell et al. | Nov 2017 | B2 |
| 9857872 | Terlizzi et al. | Jan 2018 | B2 |
| 9870053 | Modarres et al. | Jan 2018 | B2 |
| 9874980 | Brunet et al. | Jan 2018 | B2 |
| 9875625 | Khoshkava et al. | Jan 2018 | B2 |
| 9878239 | Heubel et al. | Jan 2018 | B2 |
| 9886057 | Bushnell et al. | Feb 2018 | B2 |
| 9886090 | Silvanto et al. | Feb 2018 | B2 |
| 9902186 | Whiteman et al. | Feb 2018 | B2 |
| 9904393 | Frey et al. | Feb 2018 | B2 |
| 9921649 | Grant et al. | Mar 2018 | B2 |
| 9927887 | Bulea | Mar 2018 | B2 |
| 9927902 | Burr et al. | Mar 2018 | B2 |
| 9928950 | Lubinski et al. | Mar 2018 | B2 |
| 9940013 | Choi et al. | Apr 2018 | B2 |
| 9971407 | Holenarsipur et al. | May 2018 | B2 |
| 9977499 | Westerman et al. | May 2018 | B2 |
| 9990040 | Levesque | Jun 2018 | B2 |
| 9996199 | Park et al. | Jun 2018 | B2 |
| 10025399 | Kim et al. | Jul 2018 | B2 |
| 10032550 | Zhang et al. | Jul 2018 | B1 |
| 10037660 | Khoshkava et al. | Jul 2018 | B2 |
| 10061385 | Churikov et al. | Aug 2018 | B2 |
| 10069392 | Degner et al. | Sep 2018 | B2 |
| 10078483 | Finnan et al. | Sep 2018 | B2 |
| 10082873 | Zhang | Sep 2018 | B2 |
| 10108265 | Harley et al. | Oct 2018 | B2 |
| 10110986 | Min | Oct 2018 | B1 |
| 10120446 | Pance et al. | Nov 2018 | B2 |
| 10120478 | Filiz et al. | Nov 2018 | B2 |
| 10120484 | Endo et al. | Nov 2018 | B2 |
| 10122184 | Smadi et al. | Nov 2018 | B2 |
| 10133351 | Weber et al. | Nov 2018 | B2 |
| 10139976 | Iuchi et al. | Nov 2018 | B2 |
| 10146336 | Lee et al. | Dec 2018 | B2 |
| 10152131 | Grant et al. | Dec 2018 | B2 |
| 10152182 | Haran et al. | Dec 2018 | B2 |
| 10203762 | Bradski et al. | Feb 2019 | B2 |
| 10209821 | Roberts-Hoffman et al. | Feb 2019 | B2 |
| 10232714 | Wachinger | Mar 2019 | B2 |
| 10235034 | Jitkoff et al. | Mar 2019 | B2 |
| 10235849 | Levesque | Mar 2019 | B1 |
| 10248221 | Pance et al. | Apr 2019 | B2 |
| 10254840 | Weinraub | Apr 2019 | B2 |
| 10261585 | Bard et al. | Apr 2019 | B2 |
| 10275075 | Hwang et al. | Apr 2019 | B2 |
| 10282014 | Butler et al. | May 2019 | B2 |
| 10284935 | Miyoshi | May 2019 | B2 |
| 10289199 | Hoellwarth | May 2019 | B2 |
| 10343061 | Billington et al. | Jul 2019 | B2 |
| 10346117 | Sylvan et al. | Jul 2019 | B2 |
| 10372214 | Gleeson et al. | Aug 2019 | B1 |
| 10373381 | Nuernberger et al. | Aug 2019 | B2 |
| 10382866 | Min | Aug 2019 | B2 |
| 10390139 | Biggs | Aug 2019 | B2 |
| 10394326 | Ono et al. | Aug 2019 | B2 |
| 10397686 | Forstner et al. | Aug 2019 | B2 |
| 10430077 | Lee | Oct 2019 | B2 |
| 10437359 | Wang et al. | Oct 2019 | B1 |
| 10459226 | Leppanen et al. | Oct 2019 | B2 |
| 10531191 | Macours | Jan 2020 | B2 |
| 10556252 | Tsang et al. | Feb 2020 | B2 |
| 10564721 | Cruz-Hernandez et al. | Feb 2020 | B2 |
| 10585480 | Bushnell et al. | Mar 2020 | B1 |
| 10591993 | Lehmann et al. | Mar 2020 | B2 |
| 10599223 | Amin-Shahidi et al. | Mar 2020 | B1 |
| 10622538 | Zhang et al. | Apr 2020 | B2 |
| 10649529 | Nekimken et al. | May 2020 | B1 |
| 10685626 | Kim et al. | Jun 2020 | B2 |
| 10691211 | Amin-Shahidi et al. | Jun 2020 | B2 |
| 10768738 | Wang et al. | Sep 2020 | B1 |
| 10768747 | Wang et al. | Sep 2020 | B2 |
| 10775889 | Lehmann et al. | Sep 2020 | B1 |
| 10809830 | Kim et al. | Oct 2020 | B2 |
| 10845220 | Song et al. | Nov 2020 | B2 |
| 10845878 | Zhao et al. | Nov 2020 | B1 |
| 10890978 | Bushnell et al. | Jan 2021 | B2 |
| 10936071 | Pandya et al. | Mar 2021 | B2 |
| 10942571 | Hendren et al. | Mar 2021 | B2 |
| 10963117 | Morrell et al. | Mar 2021 | B2 |
| 10996007 | Fenner et al. | Mar 2021 | B2 |
| 11024135 | Ostdiek et al. | Jun 2021 | B1 |
| 11054932 | Xu et al. | Jul 2021 | B2 |
| 11073712 | Yeke Yazdandoost et al. | Jul 2021 | B2 |
| 11086509 | Lapp | Aug 2021 | B2 |
| 11188151 | Bushnell et al. | Nov 2021 | B2 |
| 11460946 | Xu et al. | Oct 2022 | B2 |
| 20030117132 | Klinghult | Jun 2003 | A1 |
| 20050036603 | Hughes | Feb 2005 | A1 |
| 20050191604 | Allen | Sep 2005 | A1 |
| 20050230594 | Sato et al. | Oct 2005 | A1 |
| 20060017691 | Cruz-Hernandez et al. | Jan 2006 | A1 |
| 20060209037 | Wang et al. | Sep 2006 | A1 |
| 20060223547 | Chin et al. | Oct 2006 | A1 |
| 20060252463 | Liao | Nov 2006 | A1 |
| 20070106457 | Rosenberg | May 2007 | A1 |
| 20070152974 | Kim et al. | Jul 2007 | A1 |
| 20080062145 | Shahoian | Mar 2008 | A1 |
| 20080062624 | Regen | Mar 2008 | A1 |
| 20080084384 | Gregorio et al. | Apr 2008 | A1 |
| 20080111791 | Nikittin | May 2008 | A1 |
| 20090085879 | Dai et al. | Apr 2009 | A1 |
| 20090115734 | Fredriksson et al. | May 2009 | A1 |
| 20090166098 | Sunder | Jul 2009 | A1 |
| 20090167702 | Nurmi | Jul 2009 | A1 |
| 20090174672 | Schmidt | Jul 2009 | A1 |
| 20090207129 | Ullrich et al. | Aug 2009 | A1 |
| 20090225046 | Kim et al. | Sep 2009 | A1 |
| 20090243404 | Kim et al. | Oct 2009 | A1 |
| 20090267892 | Faubert | Oct 2009 | A1 |
| 20100116629 | Borissov et al. | May 2010 | A1 |
| 20100225600 | Dai et al. | Sep 2010 | A1 |
| 20100313425 | Hawes | Dec 2010 | A1 |
| 20100328229 | Weber et al. | Dec 2010 | A1 |
| 20110115754 | Cruz-Hernandez | May 2011 | A1 |
| 20110128239 | Polyakov et al. | Jun 2011 | A1 |
| 20110132114 | Siotis | Jun 2011 | A1 |
| 20110169347 | Miyamoto et al. | Jul 2011 | A1 |
| 20110205038 | Drouin et al. | Aug 2011 | A1 |
| 20110261021 | Modarres et al. | Oct 2011 | A1 |
| 20110267181 | Kildal | Nov 2011 | A1 |
| 20110267294 | Kildal | Nov 2011 | A1 |
| 20120038469 | Dehmoubed et al. | Feb 2012 | A1 |
| 20120038471 | Kim et al. | Feb 2012 | A1 |
| 20120056825 | Ramsay et al. | Mar 2012 | A1 |
| 20120062491 | Coni et al. | Mar 2012 | A1 |
| 20120113008 | Makinen et al. | May 2012 | A1 |
| 20120235942 | Shahoian | Sep 2012 | A1 |
| 20120249474 | Pratt et al. | Oct 2012 | A1 |
| 20120327006 | Israr et al. | Dec 2012 | A1 |
| 20130016042 | Makinen et al. | Jan 2013 | A1 |
| 20130021296 | Min et al. | Jan 2013 | A1 |
| 20130043670 | Holmes | Feb 2013 | A1 |
| 20130044049 | Biggs et al. | Feb 2013 | A1 |
| 20130076635 | Lin | Mar 2013 | A1 |
| 20130154996 | Trend et al. | Jun 2013 | A1 |
| 20130207793 | Weaber et al. | Aug 2013 | A1 |
| 20140118419 | Wu et al. | May 2014 | A1 |
| 20140125470 | Rosenberg | May 2014 | A1 |
| 20140168175 | Mercea et al. | Jun 2014 | A1 |
| 20150084909 | Worfolk et al. | Mar 2015 | A1 |
| 20150126070 | Candelore | May 2015 | A1 |
| 20150182113 | Utter, II | Jul 2015 | A1 |
| 20150185842 | Picciotto et al. | Jul 2015 | A1 |
| 20150186609 | Utter, II | Jul 2015 | A1 |
| 20150234493 | Parivar et al. | Aug 2015 | A1 |
| 20150293592 | Cheong et al. | Oct 2015 | A1 |
| 20160171767 | Anderson | Jun 2016 | A1 |
| 20160253019 | Geaghan | Sep 2016 | A1 |
| 20160293829 | Maharjan et al. | Oct 2016 | A1 |
| 20160327911 | Eim et al. | Nov 2016 | A1 |
| 20160328930 | Weber et al. | Nov 2016 | A1 |
| 20160334901 | Rihn | Nov 2016 | A1 |
| 20160379776 | Oakley | Dec 2016 | A1 |
| 20170024010 | Weinraub | Jan 2017 | A1 |
| 20170083096 | Rihn et al. | Mar 2017 | A1 |
| 20170090655 | Zhang et al. | Mar 2017 | A1 |
| 20170249024 | Jackson et al. | Aug 2017 | A1 |
| 20170336273 | Elangovan et al. | Nov 2017 | A1 |
| 20170357325 | Yang et al. | Dec 2017 | A1 |
| 20170364158 | Wen et al. | Dec 2017 | A1 |
| 20180005496 | Dogiamis et al. | Jan 2018 | A1 |
| 20180015362 | Terahata | Jan 2018 | A1 |
| 20180029078 | Park et al. | Feb 2018 | A1 |
| 20180284894 | Raut et al. | Oct 2018 | A1 |
| 20180335883 | Choi et al. | Nov 2018 | A1 |
| 20190278232 | Ely et al. | Sep 2019 | A1 |
| 20200251648 | Fukumoto | Aug 2020 | A1 |
| 20210157411 | Bushnell et al. | May 2021 | A1 |
| 20210176548 | Fenner et al. | Jun 2021 | A1 |
| 20210319894 | Sobol | Oct 2021 | A1 |
| 20210398403 | Ostdiek et al. | Dec 2021 | A1 |
| 20230142264 | Lehmann et al. | May 2023 | A1 |
| Number | Date | Country |
|---|---|---|
| 1846179 | Oct 2006 | CN |
| 101036105 | Sep 2007 | CN |
| 201044066 | Apr 2008 | CN |
| 101409164 | Apr 2009 | CN |
| 101436099 | May 2009 | CN |
| 101663104 | Mar 2010 | CN |
| 101872257 | Oct 2010 | CN |
| 201897778 | Jul 2011 | CN |
| 201945951 | Aug 2011 | CN |
| 102349039 | Feb 2012 | CN |
| 102448555 | May 2012 | CN |
| 203405773 | Jan 2014 | CN |
| 203630729 | Jun 2014 | CN |
| 104679233 | Jun 2015 | CN |
| 105144052 | Dec 2015 | CN |
| 106133650 | Nov 2016 | CN |
| 106354203 | Jan 2017 | CN |
| 206339935 | Jul 2017 | CN |
| 107305452 | Oct 2017 | CN |
| 207115337 | Mar 2018 | CN |
| 214030 | Mar 1983 | DE |
| 1686776 | Aug 2006 | EP |
| 2743798 | Jun 2014 | EP |
| 3098690 | Nov 2016 | EP |
| 2004129120 | Apr 2004 | JP |
| 2004236202 | Aug 2004 | JP |
| 2010537279 | Dec 2010 | JP |
| 2010540320 | Dec 2010 | JP |
| 2012048378 | Mar 2012 | JP |
| 20050033909 | Apr 2005 | KR |
| 101016208 | Feb 2011 | KR |
| 20130137124 | Dec 2013 | KR |
| 2010035805 | Oct 2010 | TW |
| 201430623 | Aug 2014 | TW |
| WO 02073587 | Sep 2002 | WO |
| WO 06091494 | Aug 2006 | WO |
| WO 07049253 | May 2007 | WO |
| WO 07114631 | Oct 2007 | WO |
| WO 09038862 | Mar 2009 | WO |
| WO 09156145 | Dec 2009 | WO |
| WO 10129221 | Nov 2010 | WO |
| WO 10129892 | Nov 2010 | WO |
| WO 12173818 | Dec 2012 | WO |
| WO 13169303 | Nov 2013 | WO |
| WO 14066516 | May 2014 | WO |
| WO 14200766 | Dec 2014 | WO |
| WO 16091944 | Jun 2016 | WO |
| WO 16144563 | Sep 2016 | WO |
| WO 19003254 | Jan 2019 | WO |
| Entry |
|---|
| Author Unknown, “3D Printed Mini Haptic Actuator,” Autodesk, Inc., 16 pages, 2016. |
| Hasser et al., “Preliminary Evaluation of a Shape-Memory Alloy Tactile Feedback Display,” Advances in Robotics, Mechantronics, and Haptic Interfaces, ASME, DSC—vol. 49, pp. 73-80, 1993. |
| Hill et al., “Real-time Estimation of Human Impedance for Haptic Interfaces,” Stanford Telerobotics Laboratory, Department of Mechanical Engineering, Stanford University, 6 pages, at least as early as Sep. 30, 2009. |
| Lee et al., “Haptic Pen: Tactile Feedback Stylus for Touch Screens,” Mitsubishi Electric Research Laboratories, http://wwwlmerl.com, 6 pages, Oct. 2004. |
| Stein et al., “A process chain for integrating piezoelectric transducers into aluminum die castings to generate smart lightweight structures,” Results in Physics 7, pp. 2534-2539, 2017. |
| “Lofelt at Smart Haptics 2017,” Auto-generated transcript from YouTube video clip, uploaded on Jun. 12, 2018 by user “Lofelt,” Retrieved from Internet: <https://www.youtube.com/watch?v=3w7LTQKS430>, 3 pages. |
| “Tutorial: Haptic Feedback Using Music and Audio—Precision Microdrives,” Retrieved from Internet Nov. 13, 2019: https://www.precisionmicrodrives.com/haptic-feedback/tutorial-haptic-feedback-using-music-and-audio/, 9 pages. |
| “Feel what you hear: haptic feedback as an accompaniment to mobile music playback,” Retrieved from Internet Nov. 13, 2019: https://dl.acm.org/citation.cfm?id=2019336, 2 pages. |
| “Auto Haptic Widget for Android,” Retrieved from Internet Nov. 13, 2019, https://apkpure.com/auto-haptic-widget/com.immersion.android.autohaptic, 3 pages. |
| D-BOX Home, Retrieved from Internet Nov. 12, 2019: https://web.archive.org/web/20180922193345/https://www.d-box.com/en, 4 pages. |
| U.S. Appl. No. 17/845,872, filed Jun. 21, 2022, Liang et al. |
| Number | Date | Country | |
|---|---|---|---|
| 20230377430 A1 | Nov 2023 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 17332795 | May 2021 | US |
| Child | 18228831 | US | |
| Parent | 16904409 | Jun 2020 | US |
| Child | 17332795 | US |
