Subject matter disclosed herein relates generally to electronic circuits and, more particularly, to driver circuits for driving light emitting diodes (LEDs) and/or other loads.
Light emitting diode (LED) driver circuits are often called upon to drive a number of series connected strings of diodes simultaneously. The strings of diodes (or “LED channels”) may be operated in parallel, with a common voltage node supplying all of the strings. A DC-DC converter (e.g., a boost converter, a buck converter, etc.) may be employed by the LED driver circuit to maintain a regulated voltage level on the various LED channels during operation so that all LED channels have adequate operational power. Feedback from the LED channels may be used to control the DC-DC converter. To reduce unnecessary power consumption, it may be desirable to keep the regulated voltage level on the voltage node to a minimum or near minimum, while still providing adequate power to all channels.
Some LED driver circuits are only capable of driving LED channels that are relatively uniform. That is, the driver circuits are only capable of driving channels having the same number of LEDs and the same current levels. In addition, some driver circuits illuminate all driven LEDs at the same time using the same dimming duty cycle. These operational constraints simplify the design of the DC-DC converter associated with the LED driver circuit. Newer LED driver circuits are being proposed that will allow more complex illumination functionality. For example, some proposed designs may allow different numbers of diodes to be used within different LED channels. Some designs may also allow different dimming duty cycles to be specified for different LED channels. In addition, some proposed designs may allow different illumination phasing in different channels (i.e., the LEDs within different channels may be permitted to turn on at different times).
As will be appreciated, any increase in the functional complexity of LED driver circuits, and/or the circuitry they drive, can complicate the design of DC-DC converters and/or converter control circuitry for the drivers. Techniques and circuits are needed that are capable of providing DC-DC voltage conversion within LED driver circuits, and/or other similar circuits, that can support this increased complexity.
In accordance with one aspect of the concepts, systems, circuits, and techniques described herein, an electronic circuit for use in driving a plurality of light emitting diode (LED) channels coupled to a common voltage node comprises: control circuitry for controlling a DC-DC converter to generate a regulated voltage on the common voltage node, the control circuitry to set a duty cycle of the DC-DC converter based on voltage requirements of a dominant LED channel; memory to store a priority queue that tracks priorities of LED channels in the plurality of LED channels, wherein a highest priority LED channel in the priority queue represents the dominant LED channel; and a queue manager to continually update the priority queue based on operating conditions associated with the plurality of LED channels, wherein the queue manager is configured to move an LED channel from a lower priority position in the priority queue to the highest priority position in the priority queue if it is determined that the LED channel requires an increase in voltage on the common voltage node.
In accordance with another aspect of the concepts, systems, circuits, and techniques described herein, an electronic circuit for use in driving a plurality of LED channels coupled to a common voltage node comprises: control circuitry for controlling a DC-DC converter to generate a regulated voltage on the common voltage node, the control circuitry to set a duty cycle of the DC-DC converter based on voltage requirements of a dominant LED channel; memory to store the identity of a dominant LED channel in the plurality of LED channels; and a controller to continually update the identity of the dominant LED channel stored in the memory based on operating conditions associated with the plurality of LED channels.
In accordance with a further aspect of the concepts, systems, circuits, and techniques described herein, a method for operating an LED driver circuit for driving a plurality of LED channels coupled to a common voltage node comprises: using a priority queue to track a dominant LED channel in the plurality of LED channels, wherein a highest priority LED channel in the priority queue represents the dominant LED channel; and setting a duty cycle of a DC-DC converter based on voltage requirements of the dominant LED channel, the DC-DC converter to generate a voltage on the common voltage node.
The foregoing features may be more fully understood from the following description of the drawings in which:
In some embodiments, LED driver circuitry 12 may be implemented as an integrated circuit (IC) and boost converter 14 may be connected externally to the IC. In other embodiments, an IC may be provided that includes both LED driver circuitry 12 and boost converter 14. In still other embodiments, system 10 may be realized using discrete circuitry. As will be appreciated, any combination of integrated circuitry and discrete circuitry may be used for system 10 in various implementations. In the discussion that follows, it will be assumed that LED driver circuitry 12 is implemented as an IC.
Boost converter 14 is a DC-DC voltage converter that is used to convert a direct current (DC) input voltage VIN to a regulated output voltage on output voltage node 20 for use in driving LEDs 16. As is well known, a boost converter is a form of switching regulator that utilizes switching techniques and energy storage elements to generate a desired output voltage. Control circuitry for boost converter 14 may be provided within LED driver circuitry 12. Although illustrated as a boost converter in
As illustrated in
In at least one embodiment, LED driver circuitry 12 may be user programmable. That is, LED driver circuitry 12 may allow a user to set various operational characteristics of system 10. One or more data storage locations may be provided within LED driver circuitry 12 to store user-provided configuration information to set operational parameters such as, for example, dimming duty cycle of different LED channels, current levels of different LED channels, illumination “on” times of different LED channels, and/or other parameters. In some implementations, a user may also be able to specify which LED channels are active and which LED channels are inactive (i.e., disabled). Default values may be used for the different parameters in the absence of user provided values.
As described above, boost converter 14 is operative for converting a DC input voltage VIN into a DC output voltage VOUT that is adequate to supply LED channels 16a, . . . , 16n. In the illustrated embodiment, boost converter 14 includes an inductor 30, a diode 32, and a capacitor 34. Other boost converter architectures may alternatively be used. The operating principles of boost converters are well known in the art. To operate properly, a switching signal having appropriate characteristics must be provided to boost converter 14. Boost control circuitry 22 of LED driver circuitry 12 is operative for providing this switching signal. As will be described in greater detail, boost control circuitry 22 may draw current from switching node 36 of boost converter 14 at a controlled duty cycle to regulate the output voltage Vout in a desired manner.
The goal of boost converter 14 and boost control circuitry 22 is to provide an adequate voltage level on voltage node 20 to support operation of all active LED channels 16a, . . . , 16n. To conserve energy, however, it may be desired that the voltage level on voltage node 20 be no higher (or only slightly higher) than a minimum level required to support operation. To achieve this, boost control circuitry 22 may rely, at least in part, on feedback from LED channels 16a, . . . , 16n. Typically, the voltage level required for a particular LED channel will be dictated by the needs of the current sink 26a, . . . , 26n associated with the channel. That is, each current sink 26a, . . . , 26n may require a minimal amount of voltage (e.g., an LEDx regulation voltage) to support operation for the corresponding LED channel.
In general, the voltage level on each current sink 26a, . . . , 26n will be equal to the difference between the voltage on voltage node 20 and the voltage drop across the LEDs in the corresponding LED channel 16a, . . . , 16n. Because each LED channel 16a, . . . , 16n may have a different number of LEDs and a different DC current, different LED channels may require different minimum voltage levels for proper operation. The LED channel that requires the highest voltage level on node 20 for proper operation will be referred to herein as the “dominant” LED channel. As will be appreciated, in some implementations, the dominant LED channel may change with time.
As shown in
As described above, in some embodiments, LED driver circuitry 12 may be partially or fully implemented as an IC. In such embodiments, boost control circuitry 50 of
With reference to
Switch 54 is operative for controllably coupling an error signal output by error amplifier 52 to capacitor 56 to charge the capacitor to an appropriate level for use as the duty cycle control signal. As described previously, in some implementations, the duty cycle of boost converter 14 may be set based upon the needs of the dominant LED channel (i.e., the channel that requires the highest voltage). In one embodiment, switch 54 may be controlled based on the dimming duty cycle of the dominant LED channel. For example, switch 54 may be closed during the “on” portion of the dimming duty cycle of the dominant LED channel and open during the “off” portion. The resulting voltage on capacitor 56 will generate a duty cycle that produces a voltage at the output of boost converter 14 that is adequate to drive the dominant LED channel. After switch 54 is opened, the voltage on capacitor 56 will remain relatively constant until the switch 54 is again closed in a subsequent cycle.
The error signal that is used to charge capacitor 56 may be generated based on feedback from LED channels 16a, . . . , 16n of
With reference to
In at least one embodiment, a mean or average voltage level across the active current sinks of the LED driver circuitry may be determined within the trans-conductance amplifier using the LED feedback. The difference between this mean or average voltage level and VREF may then be used to generate the error signal. As will be appreciated, other techniques for generating the error signal may be used in other implementations. For example, in one approach, an error signal may be generated by amplifying a difference between a feedback signal associated with only one of the LED channels (e.g., the dominant channel, the channel having the most LEDs, etc.) and a reference voltage. Other techniques may also be used. In at least one embodiment, an error amplifier may be used that generates a voltage error signal instead of a current error signal.
As described above, in some embodiments, the duty cycle of boost converter 14 of
As illustrated in
The hysteretic comparators 66, 68 each compare the boost output feedback signal on node 74 to a corresponding threshold value. That is, first comparator 66 will compare the signal to an lower threshold value (VTH−) and second comparator 68 will compare the signal to a higher threshold value (VTH+). If the boost output feedback signal transitions lower than VTH−, first comparator 66 will output a logic high value. If the boost output feedback signal transitions higher VTH+, second comparator 68 will output a logic high value. In at least one embodiment, upper threshold value (VTH+) may be equal to the allowable ripple in the boost output signal and lower threshold value (VTH−) may be equal to the LED regulation voltage. The output of first comparator 66 may be coupled to a “set” input of latch 70 and the output of second comparator 68 may be coupled to a “reset” input of latch 70. As is well known, a logic high value at the set input of a latch will transfer to the output Q of the latch. Conversely, a logic high value at the reset input of a latch will cause the latch output to reset to logic low.
In the embodiment illustrated in
Duty cycle comparator 92 is operative for generating the input signal of boost switch 94 having the desired duty cycle. To generate the input signal, duty cycle comparator 92 may compare a duty cycle control signal (e.g., VCOMP in
First and second enable switches 96, 98 are operative for allowing boost duty cycle control unit 90 to be controllably enabled and disabled. In the illustrated embodiment, the first and second enable switches 96, 98 may be controlled in a complementary fashion. Thus, to enable boost duty cycle control unit 90, switch 96 may be closed and switch 98 may be opened. To disable boost duty cycle control unit 90, switch 96 may be opened and switch 98 may be closed. It should be appreciated that boost duty cycle control unit 90 of
As shown in
As described above, in some implementations, the dominant LED channel may change with time. For example, in some implementations, a user may be permitted to disable one or more LED channels during system operation. If one of the disabled channels is the dominant channel, a new dominant channel needs to be identified. In some implementations, it may be possible to add one or more LEDs to a channel after system deployment. This can also affect the dominant LED channel. In addition, during system operation, it may be discovered that one or more of non-dominant LED channels is not receiving enough power. In this case, the underpowered channel may be made the dominant channel.
Referring back to
In some implementations, a queue manager 46 may be provided for maintaining and updating priority queue 38. Queue manager 46 may, for example, include a digital or analog controller that is capable of identifying the occurrence of certain events and/or conditions that may require a change in LED channel priority. In some implementations, for example, queue manager 46 may receive feedback from LED channels 16a . . . , 16n. This feedback may include, for example, voltage levels on the LED pins 42a, . . . , 42n of the LED driver circuitry 12, or some other feedback. If queue manager 46 detects, based on the feedback, that one of the LED channels requires more voltage (e.g., the pin voltage for the channel is below a specified regulation voltage), it may move that channel to the top of priority queue 38. When the LED channel is moved, all of the other channels may be moved down in priority. Queue manager 46 may also have access to information describing which LED channels have been disabled by a user. If the highest priority LED channel in the queue 38 is disabled, queue manager 46 may move that channel to the lowest priority position in queue 38. All other LED channels may then be moved up in priority. In one possible approach, the LED channels may initially be listed in a default order within priority queue 38. The action of queue manager 46 may then rearrange and maintain the order of the channels so that the channel in the highest priority position is the dominant LED channel.
In at least one embodiment, instead of a queue, one or more storage locations may be provided within LED driver circuitry 12 to record and track the identity of the current dominant LED channel. A controller may be provided to continually update the identity of the dominant channel stored in the storage location(s) based on events and conditions.
In some embodiments, the hysteretic control of block 136 may involve enabling and disabling a DC-DC converter duty cycle control unit based on feedback from the converter output. In one approach, the feedback from the converter output may be compared with upper and lower threshold values. The DC-DC converter duty cycle control unit may then be disabled if the feedback from the converter output transitions above the upper threshold value. After the duty cycle control unit has been disables, the output voltage of the DC-DC converter may begin to drop. The DC-DC converter duty cycle control unit may be enabled if the feedback from the converter output transitions below the lower threshold value. In one implementation, the feedback from the converter output may include a difference between a current converter output voltage and a voltage drop that existed across the LEDs of the dominant LED channel during the most recent “on” period of the channel. In this implementation, the lower threshold may include, for example, an LED regulation voltage and the upper threshold may represent a maximum desired ripple in the DC-DC output voltage, although other threshold values may be used in other embodiments.
After the initial priority queue has been established, the LED channels may be monitored to identify the occurrence of events or conditions that require an update in the priority queue (block 144). Some channel conditions may require that a new dominant LED channel be selected. For example, if it is determined that the voltage on a current sink associated with a particular LED channel is below a specified regulation voltage during the “on” portion of the dimming duty cycle of the channel, then that LED channel may be made the new dominant LED channel. If there are more than one LED strings below the regulation voltage during the “on” portion of the dimming duty cycle then the latest LED string may be considered the dominant LED channel. If such a channel condition is detected for a particular LED channel (block 146-Y), the corresponding channel may be moved to the top of the priority queue (block 148). If it is determined during monitoring that the present dominant channel has become disabled (block 150-Y), then that channel may be moved to the bottom of the priority queue (block 152). This process may be repeated in a continual fashion during driver operation to keep an updated indication of LED channel priorities and an updated indication of the dominant LED channel. As described previously, the updated dominant channel information may be used by other circuitry within the LED driver (e.g., by DC-DC converter control circuitry, etc.).
In the description above, techniques and circuits for providing control for a DC-DC converter have been discussed in the context of LED driver circuitry. It should be appreciated, however, that these techniques and circuits may also be used in other applications. For example, in some implementations, the described techniques and circuits may be used in driver circuits that drive load devices other than LEDs. The described techniques and circuits may also have application in other types of systems, components, and devices that require the generation of a regulated voltage level.
Having described exemplary embodiments of the invention, it will now become apparent to one of ordinary skill in the art that other embodiments incorporating their concepts may also be used. The embodiments contained herein should not be limited to disclosed embodiments but rather should be limited only by the spirit and scope of the appended claims. All publications and references cited herein are expressly incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
4739226 | Murata | Apr 1988 | A |
5905387 | Chinosi et al. | May 1999 | A |
6222385 | Kang | Apr 2001 | B1 |
6271693 | Shi et al. | Aug 2001 | B1 |
6400715 | Beaudoin et al. | Jun 2002 | B1 |
6621235 | Chang | Sep 2003 | B2 |
6636104 | Henry | Oct 2003 | B2 |
6690146 | Burgyan et al. | Feb 2004 | B2 |
6822403 | Horiuchi et al. | Nov 2004 | B2 |
6930679 | Wu et al. | Aug 2005 | B2 |
6963175 | Archenhold et al. | Nov 2005 | B2 |
7116086 | Burgyan et al. | Oct 2006 | B2 |
7129679 | Inaba et al. | Oct 2006 | B2 |
7148632 | Berman et al. | Dec 2006 | B2 |
7235954 | Murakami | Jun 2007 | B2 |
7291989 | Namba et al. | Nov 2007 | B2 |
7307614 | Vinn | Dec 2007 | B2 |
7317403 | Grootes et al. | Jan 2008 | B2 |
7375472 | Wong et al. | May 2008 | B2 |
7466082 | Snyder et al. | Dec 2008 | B1 |
7479743 | Namba et al. | Jan 2009 | B2 |
7482765 | Ito et al. | Jan 2009 | B2 |
7528551 | Ball | May 2009 | B2 |
7675245 | Szczeszynski et al. | Mar 2010 | B2 |
7928670 | Chen et al. | Apr 2011 | B2 |
7999487 | Szczeszynski | Aug 2011 | B2 |
8169161 | Szczeszynski et al. | May 2012 | B2 |
20030110344 | Szczepanek et al. | Jun 2003 | A1 |
20040051478 | Otake et al. | Mar 2004 | A1 |
20040080273 | Ito et al. | Apr 2004 | A1 |
20040251854 | Matsuda et al. | Dec 2004 | A1 |
20050088207 | Rader et al. | Apr 2005 | A1 |
20050104542 | Ito et al. | May 2005 | A1 |
20050110469 | Inaba et al. | May 2005 | A1 |
20050156540 | Ball | Jul 2005 | A1 |
20050243022 | Negru | Nov 2005 | A1 |
20050243041 | Vinn | Nov 2005 | A1 |
20060028147 | Shinmen et al. | Feb 2006 | A1 |
20060114954 | Wong et al. | Jun 2006 | A1 |
20060125320 | Namba et al. | Jun 2006 | A1 |
20060139299 | Tsuchiya | Jun 2006 | A1 |
20060170287 | Ito et al. | Aug 2006 | A1 |
20060250824 | Wekhande et al. | Nov 2006 | A1 |
20060259648 | Agarwala et al. | Nov 2006 | A1 |
20070120506 | Grant | May 2007 | A1 |
20070267978 | Shteynberg et al. | Nov 2007 | A1 |
20080048573 | Ferentz et al. | Feb 2008 | A1 |
20080144236 | Chiang et al. | Jun 2008 | A1 |
20080164828 | Szczeszynski et al. | Jul 2008 | A1 |
20090021384 | Jacubovski et al. | Jan 2009 | A1 |
20090212717 | Trattler | Aug 2009 | A1 |
20090289559 | Tanaka et al. | Nov 2009 | A1 |
20090302776 | Szczeszynski | Dec 2009 | A1 |
20100052552 | Kimura | Mar 2010 | A1 |
20100066255 | Roberts | Mar 2010 | A1 |
20100072922 | Szczeszynski et al. | Mar 2010 | A1 |
20100140621 | Yang et al. | Jun 2010 | A1 |
20100148691 | Kuo et al. | Jun 2010 | A1 |
20100207547 | Kuroki et al. | Aug 2010 | A1 |
20100259177 | Mednik et al. | Oct 2010 | A1 |
20100327835 | Archibald | Dec 2010 | A1 |
20110026277 | Strijker | Feb 2011 | A1 |
20110062929 | Strydom et al. | Mar 2011 | A1 |
20110133645 | Kuo et al. | Jun 2011 | A1 |
20110234122 | Yu et al. | Sep 2011 | A1 |
20110298384 | Tanigawa et al. | Dec 2011 | A1 |
20120133299 | Capodivacca et al. | May 2012 | A1 |
20120181939 | Szczeszynski et al. | Jul 2012 | A1 |
20130162152 | Lee et al. | Jun 2013 | A1 |
20130207632 | Thandi et al. | Aug 2013 | A1 |
Number | Date | Country |
---|---|---|
1 079 667 | Feb 2001 | EP |
1 079 667 | Feb 2001 | EP |
1 499 165 | Jan 2005 | EP |
3-196280 | Aug 1991 | JP |
H06-044807 | Feb 1994 | JP |
H11-507750 | Jul 1999 | JP |
2006-521659 | Sep 2000 | JP |
2002-257871 | Sep 2002 | JP |
2002-281345 | Sep 2002 | JP |
2003-063062 | Mar 2003 | JP |
2003-215534 | Jul 2003 | JP |
2004-134147 | Apr 2004 | JP |
2004-134147 | Apr 2004 | JP |
2005-116738 | Apr 2005 | JP |
2006-116738 | Apr 2005 | JP |
2006-005381 | Jan 2006 | JP |
3755770 | Mar 2006 | JP |
2006-158186 | Jun 2006 | JP |
2006-185942 | Jul 2006 | JP |
2006-318326 | Nov 2006 | JP |
2005-122979 | May 2007 | JP |
2007-129862 | May 2007 | JP |
2008-311602 | Dec 2008 | JP |
10-2005-0006042 | Jan 2005 | KR |
WO 00013310 | Mar 2000 | WO |
WO 0203087 | Jan 2002 | WO |
WO 2006136321 | Dec 2006 | WO |
WO 2007043389 | Apr 2007 | WO |
WO 2007096868 | Aug 2007 | WO |
WO 2007126630 | Nov 2007 | WO |
WO 2007126630 | Nov 2007 | WO |
WO 2008086050 | Jul 2008 | WO |
WO 2008088050 | Jul 2008 | WO |
WO 2009064682 | May 2009 | WO |
WO 2009064682 | May 2009 | WO |
WO 2000157763 | Dec 2009 | WO |
WO 2009157763 | Dec 2009 | WO |
WO 2010000475 | Jan 2010 | WO |
WO 2013006272 | Jan 2013 | WO |
Entry |
---|
“Integrated 8-Channel LED Drivers with Switch-Mode Boost and SEPIC Controller;” MAXIM; MAX16807/MAX16808; #19-6055; Oct. 2006; pp. 1-21. |
“Charge-Pump and Step-Up DC-DC Converter Solutions for Powering White LEDs in Series or Parallel Connections;” Dallas Semiconductor MAXIM; Apr. 23, 2004; 15 pages. |
“White LED Driver IC;” NPC Nippon Precision Circuits, Inc.; SM8132A; May 2005; pp. 1-18. |
“WLED Backlight Drivers with True Shutdown and OVP;” A8432 and AB433: Allegro MicroSystems, Inc. Concept Data Sheet; Jan. 25, 2005; 6 pages. |
Allegro Microsystems, Inc., Data Sheet A8500; “Flexible WLED/RGB Backlight Driver for Medium Size LCDs;” Jan. 2006-2010; pp. 1-16. |
Allegro Microsystems, Inc., Data Sheet A8501; “2MHz, 4 Channel×100 mA WLED/RGB Driver with Output Disconnect;” Jan. 2006-2010; pp. 1-24. |
Allegro Microsystems, Inc., Data Sheet A8502; “Wide Input Voltage Range, High Efficiency Fault Tolerant LED Driver;” Jan. 16, 2012; pp. 1-35. |
Allegro Microsystems, Inc., Data Sheet A8503; “High Effciency 6-Channel, 2 MHz, WLED/RGB Driver for Medium Displays, with Integrated 55 V Power Switch;” Jan. 2009; pp. 1-17. |
Allegro Microsystems, Inc., Data Sheet A8504, “WLED RGB Backlight Driver for Medium Size LCDs;” Jan. 2007-2009; pp. 1-18. |
Allegro Microsystems, Inc., Data Sheet A8508; “Wide Input Voltage Rane, High Efficiency 8-Channel Fault Tolerant LED Driver;” Jul. 9, 2012; pp. 1-28. |
Bakker et al.; “A CMOS Nested-Chopper Instrumentation Amplifier with 100-nV Offset;” IEEE Journal of Solid-State Circuits; vol. 35, No. 12; Dec. 2000; pp. 1877-1883. |
Burkhart et al.; “A Monolithically Intgrated 128 LED-Driver and its Application;” IEEE Transactions on Consumer Electronics; vol. CE-32, No. 1; Feb. 1986; pp. 26-31. |
MAXIM Data Sheet; MAX1570; “White LED Current Regulator with 1×/1.5× High-Efficiency Charge Pump;” #19-2526; Jul. 2002; pp. 1-12. |
MAXIM Data Sheet; MAX1574; “180mA, 1×/2×, White LED Charge Pump in 3mm×3mm TDFN;” #19-3117; Dec. 2003; pp. 1-9. |
MAXIM Data Sheet; MAX1576; “480mA White LED 1×/1.5×/2× Charge Pump for Backlighting and Camera Flash;” #19-3326; Aug. 2005; pp. 1-14. |
Raval, et al.; “DC-DC Converter Using Hysteric Control and Associated Methods;” U.S. Appl. No. 13/591,570, filed Aug. 22, 2012. |
Rohm, Data Sheet BD6066GU, Silicon Monolithic Integrated Circuit, Apr. 2005, pp. 1-6. |
Szczeszynski et al.; U.S. Appl. No. 12/267,645, filed Nov. 10, 2008; Entitled: “Electronic Circuits for Driving Series Connected Light Emitting Diode Strings”. |
Szczeszynski; “Electronic Circuits and Techniques for Improving a Short Duty Cycle Behavior of a DC-DC Converter Driving a Load;” U.S. Appl. No. 13/177,070, filed Jul. 6, 2011. |
Witt, Linear Technology; Design Notes; “Short-Circuit Protection for Boost Regulators;” Jan. 1997, 2 pages. |
Partial PCT Search Report received with Invitation to Pay Additional Fees in PCT/US2008/050026 dated Jun. 16, 2008, 5 pages. |
PCT International Preliminary Report on Patentability of the ISA dated May 27, 2010 for PCT/2008/082934; 14 pages. |
PCT Search Report and Written Opinion for the ISA of PCT/US2008/082934 mailed Dec. 15, 2009, 17 pages. |
PCT Search Report and Written Opinion of the ISA for PCTUS2008/050026 dated Aug. 29, 2008, 17 pages. |
Japanese Notice of Reasons of Rejection (English Translation); dated Aug. 1, 2013; for Japanese Pat. App. No. 2010-234111; 2 pages. |
Taiwan Allowance Decisions of Examination; dated Aug. 30, 2013; for Taiwanese Pat. App. No. 097144152; 2 pages. |
Email from Taiwan International Patent & Law Office; dated Sep. 5, 2013; for Taiwanese Pat. App. No. 097144152; 2 pages. |
Notice of Allowance; dated Oct. 9, 2013; for U.S. Appl. No. 13/428,654; 24 pages. |
Letter to Yuasa and Hara; dated Oct. 4, 2013; for Japanese Pat. App. No. 2010-53411; 3 pages. |
Letter from Yuasa and Hara; dated Oct. 21, 2013; for Japanese Pat. App. No. 2010-534111; 1 page. |
Japanese Response filed Oct. 4, 2013; for Japanese Pat. App. No. 2010-534111; 4 pages. |
PCT Search Report of the ISA for PCT/US2013/053165 dated Feb. 13, 2013. |
PCT Written Opinion of the ISA for PCT/US2013/053165 dated Feb. 13, 2013. |
Letter fro Yuasa and Hara dated Jul. 22, 2014; for Japanese Pat. App. No. 2013-105879; 2 pages. |
Japanese Office Action dated Jun. 4, 2014; for Japanese Pat. App. No. 2013-105879; 2 pages. |
Japanese Office Action (English translation) dated Jun. 4, 2014; for Japanese Pat. App. No. 2013-105879; 2 pages. |
JApanese Notice of Rejection; dated Feb. 21, 2013; for JP Pat. App. No. 2010-534111; 4 pages. |
Taiwan Office Action and Search Report (in Taiwanese); received Apr. 30, 2013 for TW Pat. Appl. No. 097144152; 7 pages. |
Taiwan Office Action and Search Report (in English); received Apr. 30, 2013 for TW Pat. Appl. No. 097144152; 8 pages. |
PCT Search Report and Written Opinion of the ISA for PCT/US2012/043275 dated Sep. 4, 2012. |
PCT Search Report of the ISA for PCT/US2013/053162 dated Oct. 8, 2013. |
PCT Written Opinion of the ISA for PCT/US2013/053162 dated Oct. 8, 2013. |
Office Action dated May 28, 2014 for U.S. Appl. No. 13/591,570, filed Aug. 22, 2012. |
Japanese Notice of Reasons for Rejection (English translation) dated Jan. 26, 2015; for Japanese Pat. App. No. 2014-076475 4 pages. |
Taiwan Office Action and Search Report (with English Translation) dated Jan. 28, 2015 corresponding to Taiwan Patent Appl. No. 101123896; 13 Pages. |
Response to May 28, 2014 Office Action as filed on Aug. 7, 2014 for U.S. Appl. No. 13/591,570, filed Aug. 22, 2012. |
Notice of Allowance dated Oct. 9, 2014 for U.S. Appl. No. 13/591,570, filed Aug. 22, 2012. |
Korean Notice to Submit a Response dated Nov. 19, 2014; for Korean Pat. App. No. 10-2010-7009105; 3 pages. |
Letter to 21st Century Patent & Law Firm dated Feb. 4, 2015; for Korean Pat. App. No. 10-2010-709105; 12 pages. |
Letter from 21st Century Patent & Law Firm dated Feb. 16, 2015; for Korean Pat. App. No. 10-2010-709105; 1 page. |
Korean Response and Amendment filed Feb. 16, 2015; for Korean Pat. App. No. 10-2010-7009105; 30 pages. |
International Preliminary Report on Patentability dated Mar. 5, 2015 for International PCT Application No. PCT/US2013/053165; 6 pages. |
Letter to Yuasa and Hare (including suggested claims) dated Sep. 23, 2014; for Japanese Pat. App. No. 2013-105879; 6 pages. |
Japanese Claims as filed on Oct. 3, 2014; for Japanese Pat. App. No. 2013-105879; 4 pages. |
Number | Date | Country | |
---|---|---|---|
20140055051 A1 | Feb 2014 | US |