The present disclosure relates generally to a tactile haptic switch panel and, more particularly, to force-based touch interfaces with integrated audible, haptic, and visual feedback.
The recent widespread growth of feature-rich, relatively portable, and user-friendly consumer electronic devices has sparked a corresponding consumer demand for implementation of similar functionality in conventional appliances and utilitarian devices. For example, more consumers are demanding modern touchscreen interfaces in utility appliances like televisions, refrigerators, dishwashers, and washing machines. Even modern thermostats are integrating gesture-controllable, fully-networked and remotely accessible user interfaces (UIs). Even the automobile, often thought of as the quintessential utilitarian machine, has not been impervious to recent trends to incorporate as many options and features accessible to the driver as possible—from mechanical switch controls for climate, navigation, and radio systems integrated into the steering wheel, to touchscreen interfaces and camera displays integrated into the dashboard.
Although consumer demand for incorporating greater functionality into the automotive driving experience is growing rapidly, there are a number of problems with meeting such demand. First, conventional capacitive sense touchscreen technologies, such as those used in smartphones and tablet devices, while ideal for incorporating a large amount of functionality in a relatively limited space, require significant visual engagement by the driver and are therefore too distracting to be implemented safely. Second, while the conventional mechanical switches and knobs that are currently in use are less distracting because they can be safely used without requiring the driver to remove his eyes from the road, they tend to have limited flexibility, with each switch controlling a single function or feature.
One solution for combining the flexibility and versatility of touchscreen technologies while still allowing the driver to remain attentive for safely operating the vehicle involves the use of force-based haptic human-machine interfaces (HMIs). Force-based haptic HMIs typically include a sensor surface that is responsive to touch and an actuator for generating a responsive vibration (often simulating the response provided by a mechanical switch) that provides the driver with a tactile confirmation of an input on the touchscreen. These systems incorporate the haptic feedback that drivers have come to rely on of mechanical switches with the multi-touch, multifunction flexibility of touchscreen controls.
One problem with force-based haptic HMIs, particularly in automobiles and other mechanical systems, is that accidental or inadvertent touches are much more common due to the inability of the driver to continuously view with the touch interface while driving. As a result, conventional interfaces that rely exclusively on a single sensory feedback response (e.g., visible displays) tend to be ineffective in situations where a user is unable to completely focus on the HMI. Furthermore, packaging issues associated with including multiple sensory feedback capabilities tend to require a significant amount of packaging area to accommodate the hardware needed to support multiple sensory output. Thus, a switch panel for including capabilities for stimulating multiple senses, while limiting packaging size would be particular advantageous.
The presently disclosed force-based touch interface with integrated multi-sensory feedback are directed to overcoming one or more of the problems set forth above and/or other problems in the art.
According to one aspect, the present disclosure is directed to a force-based haptic switch panel, comprising a touch plate having first and second surfaces, the first surface comprising a touch surface and the second surface opposing the first surface. The force-based haptic switch panel may also include a circuit board having a plurality of force sensors electrically coupled thereto, the force sensors disposed between the circuit board and the second surface of the touch plate, wherein each force sensor is configured to measure a respective portion of a force applied to the touch surface of the touch plate. The force-based haptic switch panel may also include an acoustic actuator disposed proximate a second surface of the touch plate and configured to generate a haptic output and an audible output responsive to the force applied to the touch surface.
In accordance with another aspect, the present disclosure is directed to a steering wheel, comprising a force-based haptic switch panel embedded within at least a portion of the steering wheel. The force-based haptic switch panel may comprise a touch plate having first and second surfaces, the first surface comprising a touch surface and the second surface opposing the first surface. The first surface of the touch plate is substantially flush with a surface of the steering wheel. The force-based haptic switch panel may also comprise a circuit board having a plurality of force sensors electrically coupled thereto, the force sensors disposed between the circuit board and the second surface of the touch plate, wherein each force sensor is configured to measure a respective portion of a force applied to the touch surface of the touch plate. The force-based haptic switch panel may further comprise an acoustic actuator disposed proximate a second surface of the touch plate and configured to generate a haptic output and an audible output responsive to the force applied to the touch surface.
In accordance with another aspect, the present disclosure is directed to a vehicle comprising one or more ground-engaging devices and a steering interface, coupled to one or more ground-engaging devices and comprising a rim portion and a hub portion, the rim portion configured for grasping by an operator of a vehicle. The vehicle may also comprise a touch plate having first and second surfaces, the first surface comprising a touch surface and the second surface opposing the first surface. The vehicle may further comprise a circuit board having a plurality of force sensors electrically coupled thereto, the force sensors disposed between the circuit board and the second surface of the touch plate, wherein each force sensor is configured to measure a respective portion of a force applied to the touch surface of the touch plate. The vehicle may also comprise an acoustic actuator disposed proximate a second surface of the touch plate and configured to generate a haptic output and an audible output responsive to the force applied to the touch surface. The vehicle may further comprise a processor, communicatively coupled to the actuator and the plurality of force sensors. The processor may be configured to provide a plurality of different control signals for causing the acoustic actuator to generate the haptic and audible outputs, each haptic control signal associated with a respective force value applied to the touch surface.
In accordance with one aspect, the present disclosure is directed to a force-based haptic switch panel that is configured to limit or lock the input area of a touch panel surface around an area associated with an initial touch detected at the surface. Accordingly, systems and methods consistent with the disclosed embodiments are configured to limit inadvertent or accidental touches by localizing the input area around an initial touch area. In certain exemplary embodiments, areas or regions that are not associated with initial touch area may be disabled, ensuring that stray or accidental touch inputs are not registered as inputs to the touch panel.
Methods and systems consistent with the disclosed embodiments may be particularly applicable in situations in which distractions divert the user's visual attention to the touch interface. Indeed, in certain disclosed embodiments, the present disclosure is directed to switch panel user interfaces that provide multi-sensory confirmations of user interactions with the switch panel. In certain other embodiments, features consistent with the present disclosure provide a solution for limiting the functional detection area to a smaller, more localized area surrounding an initial touch event.
Coupling force-based switch panels 120 to the steering interface 110 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 in response to the detected input.
For example, as illustrated in
Those skilled in the art will recognize that one of the advantages of a force-based switch panel consistent with the disclosed embodiments is the flexibility of functionality that they provide. Specifically, by providing a relatively large touch sensitive area, particularly when compared with conventional mechanical switches which have a comparatively small functional footprint, the system can be customized to provide a large amount of functionality on the steering interface. Additionally, by providing haptic and audible feedback to the user in response to detection/recognition of the touch event, operator distraction is minimized.
Although not shown in
It should be noted that, although
A force-based switch panel 120 can be any user interface device that includes a sensor configured to change at least one electrical property in response to a touch or force applied to a touch surface of the switch panel 120. 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 switch panel 120. A force-based switch panel 120, 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.
As will be explained in further detail below, the force-based switch panel 120 can include a two-dimensional array of force sensors, where each force sensor includes conductors and electrodes and is in at least partial contact with a touch surface positioned over the array. In one embodiment the force-based switch panel 120 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.
For example,
Both embodiments provide a force-based switch panel 510 (or 520) that includes a two-dimensional array of force sensors 516a-516d (or 523a-523d) arranged to have a geometric shape having a width and a length. For example, the array of force sensors 516a-516d (or 523a-523d) may have a width or length that is 8 mm or larger. In another example, the array of force sensors 516a-516d (or 523a-523d) may have a width or length that is less than 8 mm. In one embodiment, force-based switch panel 510 (or 520) can have a depth that is 0.5 mm or less. In another example, the force-based switch panel 510 (or 520) can have a depth that is greater than 0.5 mm. While the array of force sensors 523a-523d that is shown in the force-based switch panel 520 of
Both of force-based switch panels 510, 520 shown in
According to various implementations, the touch interface plate 512 (or 524) can embody any touch-sensitive deformable member that can pass at least part of the forces from a user through the touch interface plate 512 (or 524) to one or more force sensors 516a-516d (or 523a-523d) of the array of force sensors and allows light to pass through at least a portion of the interface plate 512 (or 524). For example, the touch interface plate 512 (or 524) 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 516a-516d (or 523a-523d) are connected to or integrated with a lower housing 511 (or base surface 523). For example, the lower housing 511 (or base surface 523) may include a printed circuit board (PCB) used to electronically communicate information or power to and from the force sensors 516a-516d (or 523a-523d) in the form of electrical signals. In various embodiments, the lower housing 511 (or base surface or 523) can further include electronic circuit components such as resistors, capacitors, diodes, LEDs, transmitters, receivers, and the like, alone with electrical interconnects for connecting the various components together. And, in one embodiment, the lower housing 511 (or base surface or 523) includes the printed circuit board on which the processor (not shown in
It is contemplated that additional and/or different components may be included as part of the force-based switch panel 510 (or 520). For example, force-based switch panel 510 (or 520) may include one or more components for packaging the touch interface plate 512 (or 524), one or more force sensors 516a-516d (or 523a-523d), lower housing 511 (or base surface 523), and feedback actuator 516 (or 522) together as part of a single user-interface component. In one embodiment, force-based switch panel 510 may include upper and lower housing components 515 and 511, respectively, for securing the force-based switch panel 510 within a hub of a steering interface 110. Alternatively, force-based switch panel 520 may include upper and lower housing components 525 and 521, respectively, for packaging the force-based switch panel 520 as part of a single user-interface input device.
In certain embodiments consistent with the present disclosure, the force-based switch panel may be constructed so as to provide haptic and/or audible feedback in response to a detected input signal.
The force-based haptic switch panel may also include a circuit board 523 having a plurality of force sensors 523a, 523b electrically coupled thereto. As shown in
The force-based haptic switch panel may include an actuator 522 that is affixed to the second (underside) surface of the touch plate 524. The actuator 522 may be configured to deliver a mechanical output to the touch plate. Non-limiting examples of mechanical outputs may include any mechanical output, such as a vibration, that may can be delivered to a surface of the touch plate 524 and perceived by the user.
Actuator 522 may include or embody any suitable device for converting electrical energy to a mechanical output, including those that can be perceived by a user of force-based switch panel. Non-limiting examples of such actuators include acoustic actuators, rotational motors, vibrational actuators, piezoelectric resonators, linear resonant actuators, or eccentric rotating mass motors. IN certain embodiments, acoustic actuators may be used to provide both mechanical vibration and audible outputs simultaneously.
According to the embodiment illustrated in
Force-based switch panel 120 may also include a controller or processor-based computing system that is configured to receive values indicative of applied force from the force sensors and determine, based on the magnitude and location of the applied force (relative to the touch surface) which function of the vehicle that the user is trying to control. Indeed, force-based switch panel may include one or more hardware and/or software components configured to execute software programs.
Such a controller device may include one or more hardware components such as, for example, a central processing unit (CPU) or microprocessor, a random access memory (RAM) module, a read-only memory (ROM) module, a memory or data storage module, a database, one or more input/output (I/O) devices, and an interface. Alternatively and/or additionally, controller may include one or more software media components such as, for example, a computer-readable medium including computer-executable instructions for performing methods consistent with certain disclosed embodiments. It is contemplated that one or more of the hardware components listed above may be implemented using software. For example, storage may include a software partition associated with one or more other hardware components of controller. The controller may include additional, fewer, and/or different components than those listed above. It is understood that the components listed above are exemplary only and not intended to be limiting.
CPU may include one or more processors, each configured to execute instructions and process data to perform one or more functions associated with controller. CPU may be communicatively coupled to RAM, ROM, storage, database, I/O devices, and interface. CPU may be configured to execute sequences of computer program instructions to perform various processes, which will be described in detail below. The computer program instructions may be loaded into RAM for execution by CPU.
RAM and ROM may each include one or more devices for storing information associated with an operation of networking device and/or CPU. For example, ROM may include a memory device configured to access and store information associated with the controller, such as force threshold levels associated with the force-based switch panel. RAM may include a memory device for storing data associated with one or more operations of CPU. For example, ROM may load instructions into RAM for execution by CPU.
Storage may include any type of mass storage device configured to store information that CPU may need to perform processes consistent with the disclosed embodiments. For example, storage may include one or more magnetic and/or optical disk devices, such as hard drives, CD-ROMs, DVD-ROMs, or any other type of mass media device. Alternatively or additionally, storage may include flash memory mass media storage or other semiconductor-based storage medium.
Database may include one or more software and/or hardware components that cooperate to store, organize, sort, filter, and/or arrange data used by controller and/or CPU. CPU may access the information stored in database to in order to identify, for example, a particular function associated with a force input value. It is contemplated that database may store additional and/or different information than that listed above.
I/O devices may include one or more components configured to communicate information with a component or user associated with controller. For example, I/O devices may include a console with an integrated keyboard and mouse to allow a user to input parameters associated with the controller. I/O devices may also include a display including a graphical user interface (GUI) for providing a network management console for network administrators to configure networking device. I/O devices may also include peripheral devices such as, for example, a printer for printing information associated with networking device, a user-accessible disk drive (e.g., a USB port, a floppy, CD-ROM, or DVD-ROM drive, etc.) to allow a user to input data stored on a portable media device, a microphone, a speaker system, or any other suitable type of interface device. I/O devices may be configured to output network performance results.
Interface may include one or more components configured to transmit and receive data via a communication network, such as the Internet, a local area network, a workstation peer-to-peer network, a direct link network, a wireless network, or any other suitable communication platform. For example, interface may include one or more modulators, demodulators, multiplexers, demultiplexers, network communication devices, wireless devices, antennas, modems, and any other type of device configured to enable data communication via a communication network. According to one embodiment, interface may be coupled to or include wireless communication devices, such as a module or modules configured to transmit information wirelessly using Wi-Fi or Bluetooth wireless protocols.
As illustrated in
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.
It will be apparent to those skilled in the art that various modifications and variations can be made to the disclosed systems and methods for locking detected touch location in a force-based haptic multifunction switch panel. Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the present disclosure. It is intended that the specification and examples be considered as exemplary only, with a true scope of the present disclosure being indicated by the following claims and their equivalents.
This application is a continuation application of U.S. application Ser. No. 14/509,493 filed Oct. 8, 2014, now U.S. Pat. No. 9,898,087 issued Feb. 20, 2018, which claims the benefit of U.S. Provisional Application No. 61/888,322, filed Oct. 8, 2013, and U.S. Provisional Application No. 61/891,231, filed Oct. 15, 2013, each of which are incorporated herein by reference in their entireties.
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 |
6067077 | Martin | May 2000 | 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 | Goldberg 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 |
7258026 | Papakostas et al. | Aug 2007 | B2 |
7336260 | Martin et al. | Feb 2008 | B2 |
7649278 | Yoshida et al. | Jan 2010 | B2 |
7808488 | Martin et al. | Oct 2010 | B2 |
7952498 | Higa | May 2011 | B2 |
7952566 | Poupyrev | May 2011 | B2 |
8022933 | Hardacker | Sep 2011 | B2 |
8059104 | Shahoian et al. | Nov 2011 | B2 |
8073501 | Tierling | Dec 2011 | B2 |
8188981 | Shahoian et al. | May 2012 | B2 |
8203454 | Knight et al. | Jun 2012 | B2 |
8204547 | Jang | 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 |
8330590 | Poupyrev et al. | Dec 2012 | B2 |
8368566 | Higa | Feb 2013 | B2 |
8384679 | Paleczny et al. | Feb 2013 | B2 |
8384680 | Paleczny et al. | Feb 2013 | B2 |
8427441 | Paleczny et al. | Apr 2013 | B2 |
8614683 | Ng et al. | Dec 2013 | B2 |
8633916 | Bernstein | Jan 2014 | B2 |
8638308 | Cunningham et al. | Jan 2014 | B2 |
8686952 | Burrough et al. | Apr 2014 | B2 |
8698764 | Karakotsios | Apr 2014 | B1 |
8723810 | Kim | May 2014 | B2 |
9244562 | Rosenberg et al. | Jan 2016 | B1 |
9337832 | Buttolo | May 2016 | B2 |
9864507 | Cheng et al. | Jan 2018 | B2 |
9898087 | Lisseman | Feb 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 et al. | Oct 2004 | A1 |
20050021190 | Worrell et al. | Jan 2005 | A1 |
20050052426 | Hagermoser et al. | Mar 2005 | A1 |
20050063757 | Sugimura | 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 | Mar 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 | 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 |
20080150911 | Harrison | Jun 2008 | A1 |
20080202912 | Boddie et al. | Aug 2008 | A1 |
20080230283 | Yoon | Sep 2008 | A1 |
20090001855 | Lipton | Jan 2009 | A1 |
20090020343 | Rothkopf et al. | Jan 2009 | A1 |
20090051667 | Park et al. | Feb 2009 | A1 |
20090114518 | Lin et al. | 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 |
20100141410 | Aono et al. | Jun 2010 | A1 |
20100141606 | Bae et al. | Jun 2010 | A1 |
20100156814 | Weber et al. | Jun 2010 | A1 |
20100156823 | Paleczny et al. | Jun 2010 | A1 |
20100168998 | Matsunaga | Jul 2010 | A1 |
20100200375 | Han et al. | Aug 2010 | A1 |
20100226075 | Jahge | Sep 2010 | A1 |
20100231540 | Cruz-Hernandez et al. | Sep 2010 | A1 |
20100236911 | Wild 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 |
20100321335 | Lim 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 et al. | Jun 2011 | A1 |
20110175844 | Berggren | Jul 2011 | A1 |
20110205081 | Chen | Aug 2011 | A1 |
20110210926 | Pasquero | Sep 2011 | A1 |
20110216015 | Edwards | Sep 2011 | A1 |
20110216027 | Kim et al. | 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 |
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 |
20120038468 | Provancher | Feb 2012 | A1 |
20120039494 | Ellis | Feb 2012 | A1 |
20120062491 | Coni et al. | Mar 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 et al. | Sep 2012 | A1 |
20120229424 | Behles | Sep 2012 | A1 |
20120267221 | Gohng et al. | 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 |
20130128587 | Lisseman et al. | May 2013 | A1 |
20130141396 | Lynn et al. | Jun 2013 | A1 |
20130147284 | Chun | Jun 2013 | A1 |
20130154938 | Arthur et al. | Jun 2013 | A1 |
20130181931 | Kinoshita | Jul 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 |
20130250502 | Tossavainen | Sep 2013 | A1 |
20130257776 | Tissot | Oct 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 |
20140090505 | Okuyama et al. | Apr 2014 | A1 |
20140092025 | Pala et al. | 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 |
20150009164 | Shinozaki et al. | Jan 2015 | A1 |
20150009168 | Olien et al. | Jan 2015 | A1 |
20150046825 | Li | Feb 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 |
---|---|---|
1607850 | Dec 2005 | EP |
06-037056 | May 1994 | JP |
2005-175815 | Jun 2005 | JP |
2000-71809 | Mar 2007 | JP |
2008-181709 | Aug 2008 | JP |
2011-3188 | Jan 2011 | JP |
2012-064210 | Mar 2012 | JP |
2012-73785 | Apr 2012 | JP |
2012-150833 | Aug 2012 | JP |
2012176640 | Sep 2012 | JP |
1020060047110 | May 2006 | KR |
1020100129424 | Dec 2010 | KR |
0188935 | Nov 2001 | WO |
2011008292 | Jan 2011 | WO |
2012052635 | Apr 2012 | WO |
2012169229 | Dec 2012 | WO |
2013082293 | Jun 2013 | WO |
2015054354 | Apr 2015 | WO |
2015054364 | Apr 2015 | WO |
2015054369 | Apr 2015 | WO |
2015054373 | Apr 2015 | WO |
2014194192 | Dec 2015 | WO |
Entry |
---|
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/059652 dated Dec. 22, 2014. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059652. |
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/059673 dated Jan. 9, 2015. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059673. |
International Search Report and Written Opinion issued in related International Application No. PCT/2014/059669 dated Jan. 23, 2015. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 21, 2016, received in connection with International Patent Application No. PCT/US2014/059669. |
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/059657 dated Feb. 16, 2015. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059657. |
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/059639 dated Feb. 24, 2015. |
International Preliminary Report on Patentability and Written Opinion, dated Apr. 12, 2016, received in connection with International Patent Application No. PCT/US2014/059639. |
International Search Report and Written Opinion issued in related International Application No. PCT/US2014/040224 dated Sep. 24, 2014. |
International Preliminary Report on Patentability and Written Opinion, issued in related Application No. PCT/US2014/040224 dated Dec. 10, 2015. |
Office Action dated Dec. 17, 2015, received in connection with U.S. Appl. No. 14/211,475. |
Office Action dated Dec. 15, 2015, received in connection with U.S. Appl. No. 14/211,665. |
Office Action dated Apr. 21, 2016, received in connection with U.S. Appl. No. 14/028,798. |
Office Action dated Oct. 8, 2015, received in connection with U.S. Appl. No. 14/028,798. |
Co-pending Utility U.S. Appl. No. 14/509,535, filed Oct. 8, 2014, and its prosecution history. Issued as U.S. Pat. No. 9,513,707 on Dec. 6, 2016. |
Office Action dated Feb. 11, 2016, received in connection with U.S. Appl. No. 14/509,535. |
Notice of Allowance received in connection with U.S. Appl. No. 14/509,535, dated Aug. 3, 2016. |
Co-pending Utility U.S. Appl. No. 14/509,332, filed Oct. 8, 2014, and its prosecution history. |
Office Action dated May 3, 2016, received in connection with U.S. Appl. No. 14/509,332. |
Office Action dated Oct. 27, 2016, received in connection with U.S. Appl. No. 14/509,332. |
Office Action dated Feb. 8, 2018, received in connection with U.S. Appl. No. 14/509,332. |
Office Action dated Jun. 14, 2016, received in connection with U.S. Appl. No. 14/509,462, filed Oct. 8, 2014 and its prosecution history. |
Office Action issued in co-pending U.S. Appl. No. 14/509,462, dated Dec. 28, 2016. |
Office Action issued in co-pending U.S. Appl. No. 14/509,462, dated Jun. 9, 2017. |
Office Action issued in co-pending U.S. Appl. No. 14/509,462, dated Nov. 24, 2017. |
Notice of Allowance issued in co-pending U.S. Appl. No. 14/509,462, dated Feb. 22, 2018. |
Co-pending Utility U.S. Appl. No. 14/509,560, filed Oct. 8, 2014, and its prosecution history. Issued as U.S. Pat. No. 9,829,980 on Nov. 28, 2017. |
Office Action issued in U.S. Appl. No. 14/509,560, dated Feb. 10, 2017. |
Corrected Notice of Allowance issued in U.S. Appl. No. 14/509,560, dated Aug. 22, 2017. |
Notice of Allowance issued in U.S. Appl. No. 14/509,560, dated Aug. 10, 2017. |
Co-pending Utility U.S. Appl. No. 15/822,868, filed Nov. 27, 2017. |
Office Action issued in U.S. Appl. No. 15/230,786, dated Feb. 7, 2017. |
Office Action issued in U.S. Appl. No. 15/230,786, dated Aug. 24, 2017. |
Co-pending Utility U.S. Appl. No. 14/509,598, filed Oct. 8, 2014 and its prosecution history. |
Office Action issued in U.S. Appl. No. 14/509,598, dated Jan. 6, 2017. |
Office Action issued in U.S. Appl. No. 14/509,598, dated Oct. 17, 2017. |
Office Action dated Nov. 4, 2014, received in connection with JP Patent Application No. 2011-075258. (English Translation attached). |
U.S. Appl. No. 13/076,226, filed Mar. 30, 2011, and issued as U.S. Pat. No. 9,007,190 on Apr. 14, 2015, and its file history. |
Office Action dated Mar. 11, 2013 in U.S. Appl. No. 13/076,226, now U.S. Pat. No. 9,007,190 on Apr. 14, 2015. |
Office Action dated Feb. 13, 2014 in U.S. Appl. No. 13/076,226, now U.S. Pat. No. 9,007,190 on Apr. 14, 2015. |
Office Action dated Sep. 11, 2014 in U.S. Appl. No. 13/076,226, now U.S. Pat. No. 9,007,190 on Apr. 14, 2015. |
Co-pending Utility U.S. Appl. No. 14/291,845, filed May 30, 2014 and its prosecution history. |
Office Action dated Sep. 24, 2015 in U.S. Appl. No. 14/291,845. |
Office Action dated Feb. 24, 2016, received in connection with U.S. Appl. No. 14/291,845. |
Office Action dated Feb. 3, 2017, received in connection with U.S. Appl. No. 14/291,845. |
Office Action dated Aug. 24, 2017, received in connection with U.S. Appl. No. 14/291,845. |
Office Action dated Feb. 26, 2018, received in connection with Chinese Application No. 201480030786. (English Translation attached). |
First Office Action issued for Chinese Application No. 201480055484.8, dated May 31, 2018. |
First Office Action issued for Japanese Application No. 2016-517039, dated Jun. 26, 2018. |
First Office Action issued for Japanese Application No. 2016-520148, dated Jul. 3, 2018. |
Notice of allowance issued in co-pending U.S. Appl. No. 14/509,493, dated Oct. 10, 2017. |
Non-Final Office Action, dated May 17, 2017, in connection to U.S. Appl. No. 14/509,598. |
Notice of Allowance issued for U.S. Appl. No. 14/509,332, dated Sep. 7, 2018. |
Applicant-Initiated Interview Summary issued for U.S. Appl. No. 14/509,598, dated Sep. 18, 2018, 5 pages. |
Office Action issued for U.S. Appl. No. 14/509,598, dated Jan. 18, 2019. |
Number | Date | Country | |
---|---|---|---|
20180203511 A1 | Jul 2018 | US |
Number | Date | Country | |
---|---|---|---|
61888322 | Oct 2013 | US | |
61891231 | Oct 2013 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 14509493 | Oct 2014 | US |
Child | 15867226 | US |