Conventional control systems present operators with a combination of controls such as switches, buttons, levers, knobs, dials, etc. The operators interact with these control systems by manipulating the presented controls in order to execute various control functions. Recently, control systems have become increasingly complex due to the growing number of controllable features. As control systems increase in complexity, control panels become cluttered with switches, buttons, levers, knobs and/or dials. Accordingly, the control systems become more difficult to operate. In addition, it becomes difficult for engineers to design control panels that are capable of accommodating all of the necessary controls within a confined space.
Track pad devices have been developed to address the problems in the related art. These devices are generally two-dimensional (X-Y) and include, for example, capacitive and optical sensing systems. For example, some smart phone devices include optical track pads for navigating the graphical user interface (GUI) of the smart phone. The optical track pads have a pleasant tactile feel, provide an audible “tick” for each move and, unlike capacitive touch screens, can be used without direct skin contact or without the need for special gloves. Some optical track pads work with gloves, such as those that include a mechanical contact that is separate from the track pad for accept or select functions. Furthermore, optical track pads generally have a fairly low resolution infrared camera susceptible to moisture (sweat) interferences and are limited to measurements in two (X-Y) dimensions.
Embodiments of the present invention relate to force based track pads for human-machine interfaces (HMI) and in particular track pads capable of sensing forces as well as position and providing tactile and audible feedback. For example, various implementations of a track pad system include an array of force sensors disposed between a base surface and a touch interface plate. The touch interface plate passes touch forces incident on an upper surface thereof to one or more of the force sensors in the array.
In many HMI systems, illumination is expected as a method to provide the human with a visual marker as to where to activate/deactivate a system. The illumination method typically involves utilizing an LED to direct light through a graphical icon. There are several methods for providing illumination when a touch interface plate is utilized. The first two methods described below involve directing light vertically into the touch interface plate. The third method described below involves directing light horizontally into the touch interface plate. In particular, according to one method, holes in the touch interface plate are provided vertically below the areas where illumination is needed and through which light can shine. A second method includes making the touch interface plate out of a transparent/translucent material and directing light through the lower surface to illuminate the upper surface. And, a third method includes using the touch interface plate as a light guide by directing light through one or more side surfaces of the touch interface plate. With this method, a single light source or multiple light sources are disposed on the same side, adjacent sides, or opposing sides of the touch interface plate such that the light from the light sources is directed through the touch interface plate to illuminate at least a portion of the upper surface of the touch interface plate. In certain implementations, one or more icons may be disposed adjacent the illuminated portion of the touch interface plate.
According to various implementations, a track pad system includes a two-dimensional array of force sensors arranged to have a length and a width and disposed over a base surface, a touch interface plate disposed over the array, and at least one light source. The touch interface plate includes a lower surface disposed facing the array of force sensors and an upper surface opposite the lower surface. The touch interface plate passes touch forces incident on the upper surface through to one or more of the force sensors of the array of force sensors. The light source is disposed adjacent one side of the two dimensional array and is configured for directing light through the touch interface plate to illuminate at least a portion of the upper surface of the touch interface plate. The light may be directed through the lower surface of the touch interface plate and/or through a side surface of the touch interface plate. The side surfaces of the touch interface place extend between the upper and lower surfaces thereof. In another implementation, the light source is a first light source and is disposed adjacent a first side of the two-dimensional array, and the system includes a second light source that is disposed adjacent a second side of the two-dimensional array. The second side may be adjacent to or opposite the first side of the two dimensional array, for example.
The illuminated portion of the touch interface plate may be transparent or translucent, for example. In addition, in some implementations, one or more icons may be disposed adjacent the illuminated portion. For example, the one or more icons may be disposed on an overlay that is disposed adjacent the illuminated portion of the touch interface plate or etched adjacent the illuminated portion of the touch interface plate.
The track pad system may also include one or more light altering films disposed adjacent one of the surfaces of the touch interface plate, according to some implementations. For example, the light altering films may include brightness enhancing films, light diffusing films, or light turning films.
The system may also include a processor in electronic communication with the array of force sensors. The processor is configured for: receiving force information from one or more force sensors; determining from the force information a force position along the width and length and a corresponding force magnitude, the force position identifying the location of the touch force on the upper surface of the touch interface plate; and adjusting an intensity of the light source(s) in response to ambient lighting conditions. The track pad system may also include a feedback generator that generates at least one of a tactile or audible feedback, according to certain implementations. In addition, the base surface may be a printed circuit board that includes the processor. Furthermore, in some implementations, the base surface comprises a reflective material, and the reflective material is configured for directing light from the light source(s) through the illuminated portion of the touch interface plate. In other implementations, an adhesive film having a reflective surface is disposed on the lower surface of the touch interface plate such that the reflective material faces the upper surface of the touch interface plate and is configured for directing light from the light source to the illuminated portion of the touch interface plate.
The light source(s) may include one or more light emitting diodes. In addition, in some implementations, the force sensors include MEMS force sensors, such as structure-based piezo-resistive sensors.
It should be understood that the above-described subject matter may also be implemented as a computer-controlled apparatus (e.g., a human machine interface for a system), a computing system, or an article of manufacture, such as a computer-readable storage medium.
Other systems, methods, features and/or advantages will be or may become apparent to one with skill in the art upon examination of the following drawings and detailed description. It is intended that all such additional systems, methods, features and/or advantages be included within this description and be protected by the accompanying claims.
The components in the drawings are not necessarily to scale relative to each other and like reference numerals designate corresponding parts throughout the several views:
Described herein are various implementations of a track pad system for recording multi-dimensional data including an X-Y direction and a force magnitude. Various implementations of a track pad system include an array of force sensors disposed between a base surface and a touch interface plate. The touch interface plate passes touch forces incident on an upper surface thereof to one or more of the force sensors in the array. At least one light source is disposed on one side of the array of force sensors such that the light from the light source is directed through the touch interface plate to illuminate at least a portion of the upper surface of the touch interface plate. One or more icons may be disposed adjacent the illuminated portion of the touch interface plate.
The terminology used herein is for the purpose of describing particular implementations only and is not intended to be limiting of the invention. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The implementation was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various implementations with various modifications as are suited to the particular use contemplated.
Any combination of one or more computer readable medium(s) may be utilized. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
Aspects of the present invention are described below with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to implementations of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
Coupling a force-based track pad sensor 106 to the steering grip 102 of a steering apparatus 100 provides a driver with a human-machine interface that can be configured to detect a touch or force provided by a user and determine if a switch function should or should not be activated, for example. In one embodiment, the user can be provided with a tactile or audible feedback response.
A force-based track pad sensor 106 can be any sensor configured to change at least one electrical property in response to a touch or force applied to the sensor 106. A touch, also known as a touch event, can be for example a physical contact that occurs when a driver in a vehicle uses their hand (gloved or ungloved) to apply a force to force-based track pad sensor 106. A force-based track pad sensor 106, can be any suitable tactile sensor including, a mechanical sensor, a resistive sensor, a capacitive sensor, a magnetic sensor, an optical fiber sensor, a piezoelectric sensor, a silicon sensor, and/or a temperature sensor.
The force-based track pad sensor 106 can include a two-dimensional array of force sensors arranged to have a width and a length, where each force sensor includes conductors and electrodes and is in at least partial contact with a touch interface positioned over the array. In one embodiment the track pad sensor 106 can further comprise a base that is in at least partial contact with each of the force sensors. In one aspect, the base can comprise a printed circuit board. The touch interface passes touch forces to one or more force sensors of the array of force sensors. The touch interface can embody any touch-sensitive deformable member that can pass at least part of the forces from a user through the touch interface to one or more force sensors of the array of force sensors. In one embodiment, the touch interface can be used to provide haptic feedback to the user.
Referring to
In addition, the sensor system 200 may include one or more force sensors 210 that can change at least one electrical property (e.g., resistance) in response to forces applied to the sensor system 200. The force sensor 210 is an example of a pressure sensitive input device as discussed in further detail below. Further, the sensor system 200 may include communication hardware 212 that interfaces with the force sensor 210 and receives/measures the sensed changes in the at least one electrical property of the force sensor 210. Additionally, the sensor system 200 may include a system clock 208. The processor 202 may be configured to associate the sensed changes in the at least one electrical property of the force sensor 210 with a time from the system clock 208 and store the sensed changes and corresponding time to the system memory 204. Optionally, the processor 202 may be configured to analyze the stored data and associate measured changes in the at least one electrical property of the force sensor 210 with various control messages for controlling system functions.
In many HMI systems, illumination is expected as a method to provide the human with a visual marker as to where to activate/deactivate a system. The illumination method typically involves utilizing an LED to direct light through a graphical icon. There are several methods for providing illumination when a touch interface plate is utilized.
The force-based track pad 300 shown in
According to various implementations, the touch interface plate 308 can embody any touch-sensitive deformable member that can pass at least part of the forces from a user through the touch interface plate 308 to one or more force sensors 302 of the array of force sensors 302 and allows light to pass through at least a portion of the interface plate 308. For example, the touch interface plate 308 can be comprised of polycarbonate (PC), acrylic, PC-acrylonitrile butadiene styrene (ABS), or other plastic material, glass, rubber, other suitable materials, or combinations thereof. According to certain implementations, the thickness of the material is selected to provide a low mass but provide sufficient thickness to allow light to pass through efficiently and provide sufficient coupling to the light source(s). The material should also be sufficiently stiff to withstand the forces being applied to the upper surface without too much distortion. For example, the thickness of the material for the touch interface plate may be at least about 0.2 mm. In some implementations, the thickness of the touch interface plate may be reduced (e.g., at least about 0.1 mm) when a light altering film is disposed on a surface thereof to assist with directing the light through the material and provide some structural stiffness.
Generally, the force sensors 302 are connected to or integrated with a base surface 310. For example, the base surface 310 may include a printed circuit board (PCB) used to electronically communicate information or power to and from the force sensors 302 in the form of electrical signals. In various embodiments, the base surface 310 can further include electronic circuit components such as resistors, capacitors, diodes, LEDs, transmitters, receivers, and the like. And, in one embodiment, the base surface 310 includes the printed circuit board on which the processor 202 is disposed, thus electrically connecting the force sensors 302 with the processor 202 through the base surface 310.
As noted above in relation to
However, various implementations, such as those shown in
In particular, according to certain implementations, such as those shown in
Furthermore, in implementations in which the icons are displayed via the active matrix display, such as in
In implementations in which the icons are to be illuminated, at least a portion of the touch interface surface 308 above or below each icon is transparent or translucent to allow light to pass through. However, in implementations in which the icons do not allow light to pass through them, the area around the icons is transparent or translucent to allow light to pass through the plate adjacent the icons such that the icons may be backlit. In another implementation, the colors of the translucent material adjacent the icons and the icons are selected to blend in with the structure on which the track pad system is mounted. In one example in which the track pad system is mounted onto a steering wheel of a vehicle, the translucent material and the icons may be a black or brown color to match the black or brown outer material of the steering wheel. This provides a “black panel” effect when the icons are not being illuminated, which means the icons are not readily visible when not illuminated. This effect avoids distracting the driver unnecessarily.
First light source 605 and second light source 607 are disposed adjacent opposite sides of the array 302 and direct light through the touch interface plate 308. For example, the light may be directed toward a side surface 305 of the touch interface plate 308 adjacent each light source 605, 607 and then guided horizontally through the touch interface plate 308 to the upper surface 307. The side surfaces 305 extend between the upper 307 and lower surfaces 309 of the touch interface plate 308. In addition or as an alternative as shown in
In addition, in one implementation, at least a portion of the base surface 310 may be coated with a reflective material configured for reflecting light from the light sources toward the lower surface of the touch interface plate 308. For example, the base surface 310 may be a white PCB material (white FR4 material) or coated with a white paint or medium, glass bead ball paint, a reflective polymeric film, or other suitable reflective medium. In other implementations, such as shown in
In the implementations shown in
The amount of power used by the LEDs as compared to previous systems is reduced according to the implementations described above in relation to
In certain implementations, the upper surface 307, lower surface 309, and/or side surfaces 305 of the touch interface plate 308 may include one or more light altering films disposed thereon. The light altering films may include, for example, one or more of a brightness enhancing film, a light diffusing film, and/or a light turning film. The light altering film may also block light from passing through it.
The force sensors 302 are arranged such that the position of a force on the touch interface plate 308 can be detected by one or more of the force sensors 302 of the array of force sensors 302. In this manner, by the force sensors 302 affected by the force on the touch interface 308 and the magnitude of the force on each of the affected force sensors 302, the position (X, Y) of the force on the touch interface plate 308 can be determined. For example, force information from the array of force sensors can be transmitted to a processor such as the processor 202 shown in
In various implementations, the processor 202 may be configured for activating/deactivating (or turning on/off) the track pad system 300 in response to receiving a force input over a certain threshold to the track pad system 300. Activation may include turning on the light sources 605, 607 and/or the processor 202 responding to input received after the activation force input. Deactivation may include turning off the light sources 605, 607 and/or the processor 202 ceasing to respond to input received after the deactivation force input. By requiring the force input to meet a certain threshold, the track pad system 300 is not inadvertently activated or deactivated, which could be a distraction to or frustrating for the operator.
As another example, while the system 300 is activated, the processor 202 may be configured for responding to the force input in relation to the force magnitude and/or force duration detected. For example, the volume of an audio system may be increased by first increment in response to a first force magnitude, and the volume may be increased by a second increment in response to a second force magnitude, wherein the second increment is twice as large as the first increment and the second force magnitude is twice as large as the second force magnitude.
Referring back to
In one embodiment, the feedback generator 312 can be integrated into the structure that comprises the force-based track pad 300. For example, in one embodiment the feedback generator 312 can be integrated into the base 310 and coupled to the touch interface plate 308. In such an implementation, audible and/or tactile feedback may be amplified by the touch interface plate 308. In another embodiment, the feedback generator 312 is a structural part of the structure-based piezo-resistive sensors, as described herein. In yet another embodiment, the feedback generator 312 is a haptic generator used to generate the tactile and audible feedback. In one embodiment, the haptic generator can be a coneless coil and magnet assembly such as that described in U.S. Pat. App. Pub. No. 2012/0039494 entitled “LOUDSPEAKERS” and filed on Feb. 16, 2010, which is fully incorporated herein by reference and made a part hereof.
The embodiments of a force-based track pad 300 described herein can be used to control one or more systems. For example, embodiments of a force-based track pad 300 described herein can be used to control the systems of a vehicle such as environmental (HVAC), audio, telephone, cruise control, windshield wipers, lighting, window and mirrors, and the like. For example, instructions stored in the memory 204 can further cause the processor 202 to send a control message to a system selected from a plurality of systems, wherein the control message is selected from a plurality of control messages by the processor 202. The selection of system and control message can be made depending upon one or more of the force position along the width and length and the corresponding force magnitude. For example, in one embodiment the system can be selected from the plurality of systems depending upon the force magnitude and the control message is selected from the plurality of control messages depending at least partially upon the force position along the width and length.
Consider this example, the force-based track pad 300 can have a plurality of force thresholds that can be used to select the system from the plurality of systems. For example, the force-based track pad 300 can have at least three thresholds that correlate to a different system for each threshold. In one example, the force thresholds are in increments of one Newton (N) or one ounce, two N or two ounces, and the like. For example, the first threshold may be at a force of one Newton (N) or one ounce and correlate to the audio system of a vehicle. The second threshold can be at two N or two ounces of force that correlates to the HVAC system for the vehicle. The third threshold can be at three N or three ounces of force that correlates to the cruise control system for the vehicle. In other words, the track pad 300 can recognize force magnitude of at least three thresholds and the system is selected from the plurality of systems depending upon the force magnitude exceeding one or more of the thresholds.
In one embodiment, once the system is selected from the plurality of systems based on the force magnitude, a control message for sending to that selected system can be selected from a plurality of control messages based at least in part on the force position along the width and length of the track pad 300. For example, if the HVAC system is selected based on the force magnitude, then a control message such as turn on/off the heat, turn up/down the fan, adjust the temperature, etc., can be selected based at least in part on the force position along the width and length of the track pad 300. For example, control messages to send to the selected system can be selected based on one or more of the time the force is applied to the track pad 300 at a certain location, the change of the location of the applied force to the track pad 300, the rate of the change of the location of the applied force to the track pad 300 (e.g., quickly swiping a thumb across the track pad results in one action being taken while slowly swiping the thumb across the track pad 300 results in a different action being taken), the direction of the change of the location of the applied force to the track pad 300, the length from a first touch point to a second touch point on the track pad 300, the length or distance that a digit is moved across the track pad 300 after a first touch point, the direction that a digit is moved across the track pad 300 after a first touch point, changes in the magnitude of the force applied to the track pad 300, changes in the magnitude of the force applied to the track pad 300, rate of change in the magnitude of the force applied to the track pad 300, combinations of any of the above, and the like.
In one embodiment, the feedback generator 312 can provide an audible tick or other sound when the control message is selected from the plurality of control messages depending at least partially upon the force position along the width and length and provide the tactile feedback for each selection made depending on the force magnitude. Alternatively, the feedback generator 312 can provide an audible tick for each selection made depending on the force magnitude and provide tactile feedback when the control message is selected from the plurality of control messages depending at least partially upon the force position along the width and length of the track pad 300.
As noted herein, the force-based track pad can be used to select and control a plurality of systems. The table 400 of
Similarly, a second force threshold can be correlated with a second system, such as an audio system of a vehicle. In one embodiment, the second threshold is at a force greater than the first threshold. In another embodiment, the second threshold can be at a force less than the first threshold. Similar to the above, once the audio system is selected using force on the track pad 300, control messages can be sent to the audio system using gestures or other actions using the track pad 300 that are at least partially dependent upon the position along the width and length of the track pad 300. For the audio system such messages can be, for example: Turn on/off; Adjust sound level; Adjust fade, balance, bass, treble, etc.; Adjust mode (e.g., radio, satellite radio, CD, auxiliary, etc.); and the like. Other systems, such as those shown in
The track pad system 300 disclosed herein may be particularly applicable to distracted environments, such as in automobile operation, wherein the human needs additional feedback to properly operate a machine. For example, the driver of an automobile is usually best visually focused on his or her surroundings during the driving task. The ability of the track pad system 300 to provide haptic and audible feedback makes for more sure and satisfying operation of various automobile systems. As described herein, the track pad system 300 may be used, for example, to operate stereo and/or climate controls. Each change of a station or degree could generate haptic and audible feedback. In addition, the provision of force sensitivity—and in particular thresholds—allows multiple layers of functionality from a single button. The advantage of this implementation is that the track pad 300 can replace a large number of controls and shrink the necessary reach range (and the amount of distraction) for the driver.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various implementations of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The implementation was chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various implementations with various modifications as are suited to the particular use contemplated.
Number | Name | Date | Kind |
---|---|---|---|
4484026 | Thornburg | Nov 1984 | A |
4540979 | Gerger et al. | Sep 1985 | A |
4801771 | Mizuguchi et al. | Jan 1989 | A |
4929934 | Ueda et al. | May 1990 | A |
5398962 | Kropp | Mar 1995 | A |
5408873 | Schmidt et al. | Apr 1995 | A |
5423569 | Reighard et al. | Jun 1995 | A |
5453941 | Yoshikawa | Sep 1995 | A |
5463258 | Filion et al. | Oct 1995 | A |
5539259 | Filion et al. | Jul 1996 | A |
5793297 | Takeuchi et al. | Aug 1998 | A |
5855144 | Parada | Jan 1999 | A |
5871063 | Young | Feb 1999 | A |
5914658 | Arakawa | Jun 1999 | A |
5943044 | Martinelli | Aug 1999 | A |
5965952 | Podoloff et al. | Oct 1999 | A |
6333736 | Sandbach | Dec 2001 | B1 |
6378384 | Atkinson et al. | Apr 2002 | B1 |
6429846 | Rosenberg et al. | Aug 2002 | B2 |
6501463 | Dahley et al. | Dec 2002 | B1 |
6636197 | Goldenberg et al. | Oct 2003 | B1 |
6809462 | Pelrine et al. | Oct 2004 | B2 |
6906700 | Armstrong | Jun 2005 | B1 |
6933920 | Lacroix et al. | Aug 2005 | B2 |
7126583 | Breed | Oct 2006 | B1 |
7136051 | Hein | Nov 2006 | B2 |
7258026 | Papakostas et al. | Aug 2007 | B2 |
7649278 | Yoshida et al. | Jan 2010 | B2 |
8052293 | Hurwitz | Nov 2011 | B2 |
8203454 | Knight et al. | Jun 2012 | B2 |
8214105 | Daly et al. | Jul 2012 | B2 |
8222799 | Polyakov et al. | Jul 2012 | B2 |
8237324 | Pei et al. | Aug 2012 | B2 |
8269731 | Molne | Sep 2012 | B2 |
8633916 | Bernstein | Jan 2014 | B2 |
8698764 | Karakotsios et al. | Apr 2014 | B1 |
9244562 | Rosenberg | Jan 2016 | B1 |
9337832 | Buttolol | May 2016 | B2 |
9864507 | Cheng et al. | Jan 2018 | B2 |
9898087 | Lissennan | Feb 2018 | B2 |
10007342 | Lisseman | Jun 2018 | B2 |
10067567 | Andrews | Sep 2018 | B2 |
20020041164 | Kim | Apr 2002 | A1 |
20020054060 | Schena | May 2002 | A1 |
20030043014 | Nakazawa et al. | Mar 2003 | A1 |
20030076968 | Rast | Apr 2003 | A1 |
20030083131 | Armstrong | May 2003 | A1 |
20030206162 | Roberts | Nov 2003 | A1 |
20040021643 | Hoshino et al. | Feb 2004 | A1 |
20040195031 | Nagasaka | Oct 2004 | A1 |
20040207605 | MacKey | Oct 2004 | A1 |
20050021190 | Worrell et al. | Jan 2005 | A1 |
20050052426 | Hagermoser et al. | Mar 2005 | A1 |
20050063757 | Sugimura et al. | Mar 2005 | A1 |
20050067889 | Chernoff | Mar 2005 | A1 |
20050110769 | DaCosta et al. | May 2005 | A1 |
20050156892 | Grant | Jul 2005 | A1 |
20050273218 | Breed et al. | Dec 2005 | A1 |
20060025897 | Shostak et al. | Feb 2006 | A1 |
20060054479 | Iisaka et al. | Mar 2006 | A1 |
20060076855 | Eriksen et al. | Apr 2006 | A1 |
20060109256 | Grant | May 2006 | A1 |
20060113880 | Pei et al. | Jun 2006 | A1 |
20060177212 | Lamborghini et al. | Aug 2006 | A1 |
20060248478 | Liau | Nov 2006 | A1 |
20060262103 | Hu | Nov 2006 | A1 |
20060284839 | Breed | Dec 2006 | A1 |
20070062753 | Yoshida et al. | Mar 2007 | A1 |
20070097073 | Takashima et al. | May 2007 | A1 |
20070100523 | Trachte | May 2007 | A1 |
20070129046 | Soh et al. | Jun 2007 | A1 |
20070287494 | You et al. | Dec 2007 | A1 |
20080012837 | Marriott et al. | Jan 2008 | A1 |
20080062145 | Shahoian | Mar 2008 | A1 |
20080079604 | Madonna et al. | Apr 2008 | A1 |
20080202912 | Boddie et al. | Aug 2008 | A1 |
20080230283 | Yoon et al. | Sep 2008 | A1 |
20080264183 | Graham et al. | Oct 2008 | A1 |
20080289887 | Flint et al. | Nov 2008 | A1 |
20090001855 | Lipton | Jan 2009 | A1 |
20090020343 | Rothkopf et al. | Jan 2009 | A1 |
20090114518 | Lin | May 2009 | A1 |
20090125811 | Bethurum | May 2009 | A1 |
20090140994 | Tanaka et al. | Jun 2009 | A1 |
20090140996 | Takashima et al. | Jun 2009 | A1 |
20090151447 | Jin et al. | Jun 2009 | A1 |
20090153340 | Pinder et al. | Jun 2009 | A1 |
20090160529 | Lamborghini | Jun 2009 | A1 |
20090189749 | Salada | Jul 2009 | A1 |
20090228791 | Kim et al. | Sep 2009 | A1 |
20090237374 | Li et al. | Sep 2009 | A1 |
20090241378 | Ellis | Oct 2009 | A1 |
20100001974 | Su et al. | Jan 2010 | A1 |
20100045612 | Molne | Feb 2010 | A1 |
20100053087 | Dai | Mar 2010 | A1 |
20100066512 | Rank | Mar 2010 | A1 |
20100141606 | Bae | Jun 2010 | A1 |
20100168998 | Matsunaga | Jul 2010 | A1 |
20100200375 | Han et al. | Aug 2010 | A1 |
20100226075 | Jahge | Sep 2010 | A1 |
20100236911 | Kim et al. | Sep 2010 | A1 |
20100250066 | Eckstein et al. | Sep 2010 | A1 |
20100250071 | Pala et al. | Sep 2010 | A1 |
20100268426 | Pathak | Oct 2010 | A1 |
20100302177 | Kim et al. | Dec 2010 | A1 |
20100315267 | Chung et al. | Dec 2010 | A1 |
20100321310 | Kim et al. | Dec 2010 | A1 |
20100328112 | Liu | Dec 2010 | A1 |
20110037721 | Cranfill et al. | Feb 2011 | A1 |
20110046788 | Daly et al. | Feb 2011 | A1 |
20110054359 | Sazonov et al. | Mar 2011 | A1 |
20110069021 | Hill | Mar 2011 | A1 |
20110109552 | Yasutake | May 2011 | A1 |
20110141052 | Bernstein et al. | Jun 2011 | A1 |
20110148608 | Grant | Jun 2011 | A1 |
20110175844 | Berggren | Jul 2011 | A1 |
20110210926 | Pasquero et al. | Sep 2011 | A1 |
20110216015 | Edwards | Sep 2011 | A1 |
20110227872 | Huska | Sep 2011 | A1 |
20110241850 | Bosch et al. | Oct 2011 | A1 |
20110245992 | Stahlin et al. | Oct 2011 | A1 |
20110248728 | Maruyama | Oct 2011 | A1 |
20110255023 | Doyle | Oct 2011 | A1 |
20110260983 | Pertuit et al. | Oct 2011 | A1 |
20110267181 | Kildal | Nov 2011 | A1 |
20110279380 | Weber et al. | Nov 2011 | A1 |
20110290038 | Hoshino et al. | Dec 2011 | A1 |
20120013573 | Liu et al. | Jan 2012 | A1 |
20120038468 | Provancher | Feb 2012 | A1 |
20120039494 | Ellis | Feb 2012 | A1 |
20120105367 | Son et al. | May 2012 | A1 |
20120120009 | Lussey et al. | May 2012 | A1 |
20120126959 | Zarrabi et al. | May 2012 | A1 |
20120127115 | Gannon | May 2012 | A1 |
20120169663 | Kim et al. | Jul 2012 | A1 |
20120223900 | Jiyama | Sep 2012 | A1 |
20120229424 | Behles et al. | Sep 2012 | A1 |
20120267221 | Gohng | Oct 2012 | A1 |
20120267222 | Gohng et al. | Oct 2012 | A1 |
20120296528 | Wellhoefer et al. | Nov 2012 | A1 |
20120299856 | Hasui | Nov 2012 | A1 |
20130016053 | Jung et al. | Jan 2013 | A1 |
20130063380 | Wang et al. | Mar 2013 | A1 |
20130063389 | Moore | Mar 2013 | A1 |
20130093679 | Dickinson et al. | Apr 2013 | A1 |
20130096849 | Campbell et al. | Apr 2013 | A1 |
20130106691 | Rank | May 2013 | A1 |
20130113715 | Grant et al. | May 2013 | A1 |
20130113717 | Van Eerd et al. | May 2013 | A1 |
20130122857 | Karaogu et al. | May 2013 | A1 |
20130128587 | Lisseman | May 2013 | A1 |
20130141396 | Lynn et al. | Jun 2013 | A1 |
20130147284 | Chun | Jun 2013 | A1 |
20130154938 | Arthur et al. | Jun 2013 | A1 |
20130218488 | Grandemanage et al. | Aug 2013 | A1 |
20130222287 | Bae et al. | Aug 2013 | A1 |
20130222310 | Birnbaum et al. | Aug 2013 | A1 |
20130228023 | Drasnin et al. | Sep 2013 | A1 |
20130250213 | Tomomasa | Sep 2013 | A1 |
20130250502 | Tossavainen | Sep 2013 | A1 |
20130250613 | Kamada | Sep 2013 | A1 |
20130265273 | Marsden et al. | Oct 2013 | A1 |
20130307788 | Rao et al. | Nov 2013 | A1 |
20130342337 | Kiefer et al. | Dec 2013 | A1 |
20140071060 | Santos-Gomez | Mar 2014 | A1 |
20140092025 | Pala et al. | Apr 2014 | A1 |
20140114624 | Buchanan | Apr 2014 | A1 |
20140191973 | Zellers | Jul 2014 | A1 |
20140267076 | Birnbaum et al. | Sep 2014 | A1 |
20140267113 | Lisseman et al. | Sep 2014 | A1 |
20140267114 | Lisseman et al. | Sep 2014 | A1 |
20140347176 | Modarres et al. | Nov 2014 | A1 |
20140354568 | Andrews et al. | Dec 2014 | A1 |
20150009164 | Shinozaki et al. | Jan 2015 | A1 |
20150009168 | Olien et al. | Jan 2015 | A1 |
20150046825 | Li | Feb 2015 | A1 |
20150097791 | Lisseman et al. | Apr 2015 | A1 |
20150097793 | Lisseman et al. | Apr 2015 | A1 |
20150097794 | Lisseman et al. | Apr 2015 | A1 |
20150097795 | Lisseman et al. | Apr 2015 | A1 |
20150097796 | Lisseman et al. | Apr 2015 | A1 |
20150116205 | Westerman et al. | Apr 2015 | A1 |
20150212571 | Kitada | Jul 2015 | A1 |
20150309576 | Tissot | Oct 2015 | A1 |
20160109949 | Park | Apr 2016 | A1 |
20160216764 | Morrell | Jul 2016 | A1 |
20170075424 | Bernstein | Mar 2017 | A1 |
Number | Date | Country |
---|---|---|
102713805 | Oct 2012 | CN |
1607850 | Dec 2005 | EP |
58-141835 | Sep 1983 | JP |
64-66522 | Mar 1989 | JP |
7-247869 | Sep 1995 | JP |
2005-175815 | Jun 2005 | JP |
2006-129893 | May 2006 | JP |
2008-181709 | Aug 2008 | JP |
2009-008613 | Jan 2009 | JP |
2009-521006 | May 2009 | JP |
2009-186452 | Aug 2009 | JP |
2009-244931 | Oct 2009 | JP |
2010-511916 | Apr 2010 | JP |
2012176640 | Sep 2012 | JP |
1020060047110 | May 2006 | KR |
1020100129424 | Dec 2010 | KR |
1020110042924 | Apr 2011 | KR |
0188935 | Nov 2001 | WO |
2006123616 | Nov 2006 | WO |
2011008292 | Jan 2011 | WO |
2011045929 | Apr 2011 | WO |
2013082293 | Jun 2013 | WO |
Entry |
---|
Co-pending U.S. Appl. No. 14/509,560, filed Oct. 8, 2014, and its file history. |
Co-pending U.S. Appl. No. 14/509,493, filed Oct. 8, 2014, and its file history. |
Office Action dated Jun. 16, 2016, received in connection with U.S. Appl. No. 14/509,493. |
Co-pending U.S. Appl. No. 14/509,462, filed Oct. 8, 2014, and its file history. |
Co-pending U.S. Appl. No. 14/509,332, filed Oct. 8, 2014, and its file history. |
Office Action dated May 3, 2016, received in connection with U.S. Appl. No. 14/509,332. |
Co-pending U.S. Appl. No. 14/509,535, filed Oct. 8, 2014, and its file history. |
Office Action dated Feb. 11, 2016, received in connection with U.S. Appl. No. 14/509,535. |
Co-pending U.S. Appl. No. 14/291,845, filed May 30, 2014, and its file history. |
Office Action dated Feb. 24, 2016, received in connection with U.S. Appl. No. 14/291,845. |
Office Action dated Sep. 24, 2015, received in connection with U.S. Appl. No. 14/291,845. |
Office Action dated Jun. 14, 2016, received in connection with U.S. Appl. No. 14/509,462. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059639. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059652. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059657. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059669. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059673. |
International Preliminary Report on Patentability and Written Opinion, dated Dec. 10, 2015, received in connection with International Patent Application No. PCT/US2014/040224. |
International Search Report and Written Opinion, dated Sep. 24, 2014, received in connection with International Application No. PCT/US2014/040224. |
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/059652 dated Dec. 22, 2014. |
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/059673 dated Jan. 9, 2015. |
International Search Report and Written Opinion issued in related International Application No. PCT/2014/059669 dated Jan. 23, 2015. |
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/059657 dated Feb. 16, 2015. |
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/059639 dated Feb. 24, 2015. |
Office Action dated Sep. 30, 2015 in U.S. Appl. No. 14/509,493, filed Oct. 8, 2014. |
Notice of Allowance issued for U.S. Appl. No. 14/509,535 dated Aug. 3, 2016. |
Office Action issued in U.S. Appl. No. 14/509,332, dated Oct. 27, 2016. |
Office Action issued in U.S. Appl. No. 14/509,462, dated Dec. 28, 2016. |
Office Action issued in U.S. Appl. No. 14/509,493, dated Dec. 28, 2016. |
Office Action received in connection with U.S. Appl. No. 2011-075258. (English Translation attached) dated Nov. 4, 2014. |
Office Action in U.S. Appl. No. 13/076,226, which issued as U.S. Pat. No. 9,007,190 on Apr. 14, 2015, dated Mar. 11, 2013. |
Office Action in U.S. Appl. No. 13/076,226, which issued as U.S. Pat. No. 9,007,190 on Apr. 14, 2015, dated Feb. 13, 2014. |
Office Action in U.S. Appl. No. 13/076,226, which issued as U.S. Pat. No. 9,007,190 on Apr. 14, 2015, dated Sep. 11, 2014. |
Office Action issued in U.S. Appl. No, 14/509,560, dated Feb. 10, 2017. |
Office Action issued in U.S. Appl. No. 14/291,845, dated Feb. 3, 2017. |
Office Action issued in U.S. Appl. No. 13/863,363, dated Nov. 10, 2015. |
Office Action issued in U.S. Appl. No. 14/211,475, dated Dec. 17, 2015. |
Office Action issued in U.S. Appl. No. 14/211,665, dated Dec. 15, 2015. |
International Search Report and Written Opinion for International Patent Application No. PCT/US2013/030417, dated Jun. 21, 2013. |
Office Action in U.S. Appl. No. 15/230,786 dated Feb. 7, 2017. |
Office Action issued in related U.S. Appl. No. 13/673,463, dated Feb. 18, 2015. |
Office Action issued in related U.S. Appl. No. 13/673,463, dated Aug. 20, 2015. |
Office Action issued in related U.S. Appl. No. 13/673,463, dated Jan. 21, 2016. |
Office Action issued in related U.S. Appl. No. 13/673,463, dated Aug. 24, 2016. |
Office Action issued in related U.S. Appl. No. 14/028,798, dated Apr. 21, 2016. |
Office Action issued in related U.S. Appl. No. 14/028,798, dated Oct. 8, 2015. |
Office Action dated Mar. 11, 2013 in U.S. Appl. No. 13/076,226, which issued as U.S. Pat. No. 9,007,190 on Apr. 14, 2015. |
Office Action for U.S. Appl. No. 14/509,332, dated Oct. 27, 2016. |
Notice of Allowance for U.S. Appl. No. 14/509,535, dated Aug. 3, 2016. |
Office Action for JP Application No. 2014-541319 dated Oct. 18, 2016. |
Co-pending U.S. Appl. No. 15/230,786, filed Aug. 8, 2016 and its file history. |
Co-Pending U.S. Appl. No. 15/391,013, filed Dec. 27, 2016 and its file history. |
Co-Pending U.S. Appl. No. 13/673,463, filed Nov. 9, 2012, and its file history. |
Co-Pending U.S. Appl. No. 13/863,363, filed Apr. 15, 2013 and its file history. |
Interview Summary dated Mar. 23, 2017 in U.S. Appl. No. 14/509,493. |
Non-Final Office Action issued in U.S. Appl. No. 14/509,462, dated Jun. 9, 2017. |
Notice of Allowance issued in U.S. Appl. No. 14/291,845, dated Sep. 29, 2016. |
Office Action issued in co-pending U.S. Appl. No. 14/509,462, dated Nov. 24, 2017. |
Office Action issued in co-pending U.S. Appl. No. 14/509,332, dated Feb. 8, 2018. |
Notice of Allowance issued in co-pending U.S. Appl. No. 14/509,462, dated Feb. 22, 2018. |
Notice of allowance issued in co-pending U.S. Appl. No. 14/509,560, dated Aug. 10, 2017. |
Corrected notice of allowance issued in co-pending U.S. Appl. No. 14/509,560, dated Aug. 22, 2017. |
Notice of allowance issued in co-pending U.S. Appl. No. 14/509,493, dated Oct. 10, 2017. |
Notice of Allowance issued for U.S. Appl. No. 14/509,332, dated Sep. 7, 2018. |
Office Action received in Chinese Application No. 2014800030786, dated Feb. 26, 2018. |
Supplemental Notice of Allowance, dated May 29, 2018, in connection with U.S. Appl. No. 14/509,462. |
Office Action issued for U.S. Appl. No. 15/867,226, dated Jun. 29, 2018. |
Number | Date | Country | |
---|---|---|---|
20160103541 A1 | Apr 2016 | US |