This disclosure relates generally to electricity meters and more specifically to electrical meters with fault tolerant internal power supplies.
Electricity meters, typically located at an end user premises, measure power consumed by electrical loads like air conditioners, televisions, lights, and so on. Some electric meters include additional hardware that can function above and beyond metering, such as transmitting consumption information over a wireless network, performing analysis of power consumption, or detecting meter tampering. To power this additional hardware, electricity meters include an internal power supply that delivers power to both the traditional metrology systems and these additional devices.
But the additional hardware in newer meters, e.g., processors, communications devices, network cards, etc., requires additional electrical power relative to normal requirements, increasing a risk of power faults such as short-circuiting or over-consumption and causing additional heat to be generated. In existing solutions, upon detecting an electrical fault, the metering functionality is also turned off. Because power is still being delivered to an end user premises, no measurement of power consumption takes place for a period of time and billing information is lost. Hence, new solutions are needed.
Certain aspects and features relate to technical improvements for fault-tolerant power supplies for electric meters. In an example, a system converts an alternating-current (AC) voltage to an initial direct current (DC) voltage. The system further converts the initial DC voltage to a first DC voltage and a second DC voltage. The system applies the first DC voltage to a high-priority device such as a metrology device. The system applies the second DC voltage to a low-priority or peripheral device. When the initial DC voltage is outside a voltage range, the system deactivates the second DC voltage to the lower-priority device and maintains the first DC voltage to the metrology device.
These illustrative examples are mentioned not to limit or define the disclosure, but to provide examples to aid understanding thereof. Additional examples and further description are provided in the Detailed Description.
These and other features, aspects, and advantages of the present disclosure are better understood when the following Detailed Description is read with reference to the accompanying drawings, where:
Aspects of the present disclosure relate to fault-tolerant internal power supplies for electric metering systems. In addition to core metrology hardware, electric metering systems can include peripherals such as host-meter communications devices, wireless networking cards, and the like. Generally, these peripherals are considered to be secondary to metrology functions, which remain active for billing purposes. Disclosed solutions provide a fault-tolerant power supply that can detect and recover from a fault such as a short circuit or an over-current situation caused by a peripheral or an external device connected to the meter, while maintaining power to the metrology hardware.
In some aspects, disclosed systems include a processor (e.g., a host processor) that receives an indication of one or more voltages that are provided to the metrology systems and peripherals. Based on these voltages, the processor can make a determination that a power fault has occurred. Examples of faults include a hardware device failure, a short-circuit, or an over current. In response, the processor causes the power supply to deactivate the output to the peripheral while leaving the power supply to the metrology unit connected.
Turning now to the Figures,
Electric meter 101 includes one or more of power supply 115, processor 165, metrology unit 120, and peripherals 130a-n. More specifically, electric meter 101 receives power from power source 110 and provides the power via connection 102 to the metrology unit 120 and via connection 103 to the power supply 115. In a multi-phase environment, connection 102 and connection 103 include one or more phases of alternating current. Metrology unit 120 receives power via connection 102, provides power via connection 107 to customer equipment 190, and measures current consumption on each phase of connection 102. Metrology unit 120 can perform additional functions such as measuring voltage, detecting zero-crossings, and advanced analytics such as detecting peak or low demand times.
Power supply 115 provides power to both metrology unit 120 and to peripherals 130a-n. Examples of peripherals 130a-n are communications devices, Peripheral Component Interconnect (PCI) express cards, Universal Serial Bus (USB) controllers, etc. In particular, power supply 115 can provide separate power outputs to different devices. Connection 106 to metrology unit 120 can be separately switched from connections 104a-n, which provide power to peripherals 130a-n via connections 104a-n respectively. For example, power supply 115 can include a transformer that steps down the incoming voltage from power source 110 to a suitable level (e.g., 12 V or 24 V). Power supply 115 can also include additional converters such as rectifiers that convert AC to DC and other (e.g., transistor-based) switching devices that convert a first, or initial, DC voltage (e.g., 12 V) to a second, lower voltage (e.g., 3.3 V or 5 V).
Power supply 115 operates in conjunction with processor 165 to detect faults such as over-voltages, overheating, and electric noise. In response, power supply 115 can take action such as shutting down one or more peripherals for a period of time or on a permanent basis. Examples of processor 165 include microcontrollers, signal processors, and general-purpose processors. Power supply 115 connects to processor 165 via connection 105. A state of one or more voltages generated by power supply 115 is provided to processor 165 over connection 105. Additionally, connection 105 enables processor 165 to separately control power to the metrology unit 220 and peripherals 130a-n on a granular basis. For example, processor 165 can selectively deactivate or reactivate peripherals 130a-n as appropriate.
Metrology unit 220 receives power for measurement. As depicted, metrology unit 220 receives voltage 201a at a first phase and voltage 201b at a second phase, but metrology unit 220 can operate with any number of phases. Metrology unit 220 includes voltage sensors 221a-b, which detect voltages on specific phases, and current sensors 222a-n, which detect current consumed on specific phases. Voltage sensors 221a-b can sample the voltages 201a-b and current sensors and computes active energy, reactive energy, power outages and other related service information.
Metrology unit 220 also includes a metering integrated circuit (IC) 224, which can include hardware that operates in the digital or analog domain. Memory 226, which can be non-volatile, is used to store metering information, for example, before the metering information is provided to the host device 260 for transmission to another device or for extraction by a utility meter reader.
Zero-crossing detector 240 monitors voltages 201a-b, each of which represents a different phase (but any number of phases are possible). Zero-crossing detector 240 outputs a pulse 241 every time an AC voltage passes the zero-threshold. Pulse 241 is used by metrology unit for metering purposes and is also used by power supply 215 to provide an early indication that AC power is lost to the meter. Zero-crossing detector 240 can also provide single versus poly-phase detection. In some cases, this functionality is integrated into metrology unit 220, e.g., in metering IC 224.
Power supply 215 receives power and provides power to internal devices. For example, power supply 215 provides power output to metrology unit via voltage 210 and to peripherals 230a-n via voltages 211a-n respectively. Power supply 215 sends voltage monitoring signal 216, which includes information about both pulse 241 and the voltages 211a-n, to host device 260. In turn, host device 260 can determine a presence of a fault and can issue controls via control signals 262a-n to the power supply. Examples of controls include disabling power to one or more voltages 211a-n in the event of a fault. The power supply is discussed further with respect to
Host device 260 can control power supply 215 via one or more control signals. For example, host device 260 sends control signals 261 and control signals 262a-n to power supply 215. Based on control signal 261, power supply 215 can activate or deactivate power to the metrology unit 220, e.g., by controlling the output voltage 210. Based on control signals 262a-n, power supply 215 can activate or deactivate power to one or more peripherals 230a-n, e.g., by controlling voltages 211a-n. Examples of processes performed by host device 260, e.g., processor 265, are described further with respect to
Host device 260 connects to metrology unit 220 via communications interface 228. Host device 260 can receive metering and billing information across communications interface 228. Host device 260 can also control metrology unit 220 via communications interface 228, for example, by issuing a command to stop metering, shut off the power to the end user premises, or perform other functions. The host device 260 processes metering information and other information such as tampering events using processor 265 and stores the information in memory 266. Host device 260 connects to switches 244a-n. Switches 244a-n can be externally located on the meter or accessible by a user by removing a cover. Switches 244a-n provide some control, configuration, or customization of settings, for example a demand reset. In some cases, electric meter system can include a magnetically-activated switch that permits a user to read service-related information (e.g., line voltages, currents, and/or phase angles) on a display. In some cases, host device 260 connects to interfaces 245a-n, which provides connection with external devices such as computers and monitoring devices. Examples of interfaces 245a-n are Universal Serial Bus (USB) and a serial interface. In some cases, the metrology unit 220 and the host device 260 are integrated on to a single integrated circuit. An example of a host device is discussed further with respect to
In some aspects, electric meter system 200 can include temperature sensor 236. Temperature sensor 236 can be located internally to electric meter system 200 and/or form part of the electronics assembly. Temperature sensor 236 interfaces with host device 260 to provide a current temperature of electronics within electric meter system 200.
For example, processor 265 can continuously monitor a temperature inside electric meter system 200. If the temperature is outside of a safe operating temperature range, processor 265 can cause power supply 315 to shut down one or more peripherals 230a-n, while preserving power to metrology unit 220. Processor 265 can continue to monitor the temperature and when electric meter system 200 returns to a safe operating temperature range, processor 265 can cause one or more peripherals 230a-n to turn back on. In some cases, a safe operating temperature range is below approximately +80 Celsius to +85 Celsius.
Specific voltages may be required depending on the type of peripheral. For example, PCI Express can require 3.3 V, a wireless card can require 3.3 V, and a radio can require 4 V. Power converter 317 converts initial voltage 331 into voltage 332 (an example of which is 3.3 V) and provides voltage 332 to metrology unit 220. Each of power converters 318a-n can convert the initial voltage 331 to different voltages. For example, power converter 318a can convert initial voltage 331 to 3.3 V and power converter 318b can convert initial voltage 331 to 5 V. Voltages 311a-n are provided to peripherals 230a-n respectively. Examples of voltages 311a-n are 3.3 V and 5 V. In some cases, even though two peripherals 230a-n may require the same voltage, different power converters 318a-n can be used, giving power supply 315 the ability to turn on and off different peripherals on an individualized basis.
Power supply 315 provides, via A/C to D/C converter 330, an initial voltage 331 to resistors R1 and R2. For example, considering an initial voltage of +12 Volts DC, R1=82 kohms and R2=12 kohms. In this case, the range of voltage going to A/D converter 320 is approximately 1.53 VDC. Analog to Digital (A/D) converter 320 is connected between resistors R1 and R2, which can operate as a voltage divider. A/D converter 320 periodically samples the voltage measured between R1 and R2, providing a digital voltage monitoring signal 316 to host device 260. Host device 260 receives initial voltage monitoring signal 316 and pulse 241 from zero-crossing detector 240. Using initial voltage monitoring signal 316 and pulse 241, host device 260 implements fault-tolerant power management. The host device 260 uses these signals to form an early detection of an overcurrent fault or other error and to take corrective actions to maintain the metering functionality of the meter.
As discussed, one or more peripherals 230a-n can cause an over-current, short-circuit, or other failure. For example, if the AC line voltage is above a minimum line voltage threshold (e.g., 120 V), but the initial voltage 331 remains below a threshold, then either excessive consumption or a short circuit on the part of one or more peripherals 230a-n is causing the low voltage.
At block 401, process 400 involves converting an alternating-current (AC) voltage to an initial direct current (DC) voltage. For example, AC to DC converter 330 converts voltage 201a (AC) to initial voltage 331 (e.g., 12 V).
At block 402, process 400 involves converting the initial DC voltage to a first DC voltage and a second DC voltage. For example, power converter 317 converts initial voltage 331 to voltage 332 and power converter 318a converts initial voltage 331 to voltage 311a.
At block 403, process 400 involves applying the first DC voltage to a metrology device. For example, host device 260 causes power converter 317 to provide voltage 332 to metrology unit 220.
At block 404, process 400 involves applying the second DC voltage to a peripheral device. For example, host device 260 causes power converter 318a to provide voltage 311a to peripheral 230a.
At block 405, process 400 involves detecting that the initial DC voltage is outside a voltage range and deactivating the second DC voltage to the peripheral device. For example, host device 260 analyzes initial voltage monitoring signal 316. Upon detecting that initial voltage monitoring signal 316 is outside, e.g., below, a range, host device 260 causes power converter 318a to deactivate voltage 311a to peripheral 230a by issuing a control signal 262a. In some cases, host device 260 can check pulse 241 to determine whether the meter has AC power before deactivating any peripherals.
At block 406, process 400 involves maintaining the first DC voltage to the metrology device. Host device 260 maintains voltage 332 to metrology unit 220.
Upon detecting a fault, host device 260 can take one or more actions. For example, host device 260 can attempt to recover from the fault, send an alert, or disable one or more peripherals. In one example, after a threshold amount of time is met, host device 260 sends control signals 262a-n to power converters 318a-n, causing power to be provided back to all peripherals 230a-n. Different processes can be used, such as process 500 discussed with respect to
At block 501, process 500 involves applying DC power to a metrology device, a first peripheral, and a second peripheral. At block 501, process 500 involves substantially similar operations as described with respect to blocks 401-404 of process 400. For example, host device 260 causes power converter 317 to provide power to metrology unit 220, power converter 318a to provide power to peripheral 230a and power converter 318n to provide power to peripheral 230n.
At block 502, process 500 involves detecting a fault. At block 502, process 500 involves substantially similar operations as described with respect to block 405 of process 400. For example, host device 260 detects that initial voltage monitoring signal 316 is outside a range. An example of a range is 10 V-12 V for an expected 12 V initial voltage. Host device 260 causes power converter 317 to maintain power to metrology unit 220.
At block 503, process 500 involves determining that an amount of time has elapsed and reactivating the first peripheral while maintaining the second peripheral device in a deactivated state. Host device 260 waits for some time to allow the fault to potentially correct itself before reactivating power. Host device 260 then issues a control signal 262a to cause power converter 318a to reactivate voltage 311a to peripheral 230a. Host device 260 causes power converter 318n to maintain peripheral 230n in a deactivated state.
At block 504, process 500 involves determining that the initial DC voltage has decreased outside a voltage range, disabling the first peripheral. Host device 260 receives initial voltage monitoring signal 316 and determines that initial voltage monitoring signal 316 is outside a range for the second time. Host device 260 disables peripheral 230a after this second fault is detected. In other cases, host device 260 can try three or more times to bring a peripheral back online before disabling that peripheral. In some cases, host device 260 can store the fault as permanent and disable the power supply to peripheral 230a until the meter can be serviced.
At block 505, process 500 involves reactivating the second peripheral. For example, host device 260 issues control signal 262n to reactivate voltage 311b to peripheral 230n.
In some cases, different peripherals 230a-n can have different priorities. For example, a WiFi device might have a higher priority than a radio. In that case, after a failure, host device 260 attempts to reactive the WiFi device before attempting to reactivate the radio.
Various actions can be taken by host device 260 following a failure or at any point in the recovery process. For example, host device 260 can send a message to an external device or log the fault or the recovery in non-volatile memory. For example, after successfully reactivating both devices, if an overcurrent does not reappear after enabling all of the power converters 318a-n, that event can be logged. In other cases, processor can log a time and origin (e.g., which peripheral) of a malfunction and then communicate this information to an external entity such as a utility company.
Further, host device 260 can also detect whether there is a fault on power supply to the meter itself (e.g., the incoming line voltage) and take actions accordingly. For example, if the AC line voltage falls outside a range within a threshold number of line cycles, host device 260 can use energy stored in one or more capacitors 264 to sustain the operation of one or more components with the system (e.g., metrology unit 220 and/or a peripheral 230a-n) the system until all the critical information is saved in a non-volatile memory. The capacitors can be connected between initial voltage 331 and ground. Once all the critical information has been saved in the non-volatile memory, host device 260 can cease metering functions and can continue to monitor the AC line until the energy in the capacitors is depleted or the AC power outage is resolved.
The memory device 604 includes any suitable non-transitory computer-readable medium for storing data, program code, or both. A computer-readable medium can include any electronic, optical, magnetic, or other storage device capable of providing a processor with computer-readable instructions or other program code. Non-limiting examples of a computer-readable medium include a flash memory, a ROM, a RAM, an ASIC, or any other medium from which a processing device can read instructions. The instructions may include processor-specific instructions generated by a compiler or an interpreter from code written in any suitable computer-programming language, including, for example, C, C++, C#, Visual Basic, Java, or scripting language. The computing device 600 executes program code 430 that configures the processor 602 to perform one or more of the operations described herein. For example, the program code 630 causes the processor to perform the operations described in
The computing device 600 may also include a number of external or internal devices, such as input or output devices. For example, the computing device 600 is shown with interface 646. Interface 646 can receive input from input devices or provide output to output devices. One or more busses 606 are also included in the computing device 600. The bus 606 communicatively couples one or more components of a respective one of the computing device 600.
General Considerations
While the present subject matter has been described in detail with respect to specific aspects thereof, it will be appreciated that those skilled in the art, upon attaining an understanding of the foregoing, may readily produce alterations to, variations of, and equivalents to such aspects. Accordingly, it should be understood that the present disclosure has been presented for purposes of example rather than limitation and does not preclude inclusion of such modifications, variations, and/or additions to the present subject matter as would be readily apparent to one of ordinary skill in the art.
Number | Name | Date | Kind |
---|---|---|---|
4085287 | Kullmann et al. | Apr 1978 | A |
4106095 | Yarbrough | Aug 1978 | A |
4335447 | Jerrim | Jun 1982 | A |
4361838 | Mizuta | Nov 1982 | A |
4425613 | Shelly | Jan 1984 | A |
4467434 | Hurley et al. | Aug 1984 | A |
4504831 | Jahr et al. | Mar 1985 | A |
4509128 | Coppola et al. | Apr 1985 | A |
4575640 | Martin | Mar 1986 | A |
4594545 | Germer | Jun 1986 | A |
4631476 | Germer et al. | Dec 1986 | A |
4646084 | Burrowes et al. | Feb 1987 | A |
4662736 | Taniguchi et al. | May 1987 | A |
4701858 | Stokes et al. | Oct 1987 | A |
4707679 | Kennon et al. | Nov 1987 | A |
4707852 | Jahr et al. | Nov 1987 | A |
4758836 | Scuilli | Jul 1988 | A |
4845607 | Nakao et al. | Jul 1989 | A |
4881070 | Burrowes et al. | Nov 1989 | A |
4987363 | Gibbs et al. | Jan 1991 | A |
4999575 | Germer et al. | Mar 1991 | A |
5070481 | Haubner et al. | Dec 1991 | A |
5111407 | Galpern | May 1992 | A |
5181026 | Granville | Jan 1993 | A |
5216357 | Coppola et al. | Jun 1993 | A |
5345231 | Koo et al. | Sep 1994 | A |
5414861 | Horning | May 1995 | A |
5471137 | Briese et al. | Nov 1995 | A |
5488565 | Kennon et al. | Jan 1996 | A |
5523751 | Byford et al. | Jun 1996 | A |
5544089 | Hemminger et al. | Aug 1996 | A |
5619192 | Ayala | Apr 1997 | A |
5627462 | Whitehead, Jr. | May 1997 | A |
5650669 | Aldous | Jul 1997 | A |
5680294 | Stora et al. | Oct 1997 | A |
5809311 | Jones | Sep 1998 | A |
5923099 | Bilir | Jul 1999 | A |
5924051 | Provost et al. | Jul 1999 | A |
5940009 | Loy et al. | Aug 1999 | A |
5942811 | Stumfall et al. | Aug 1999 | A |
6112158 | Bond et al. | Aug 2000 | A |
6115676 | Rector et al. | Sep 2000 | A |
6476519 | Weiner | Nov 2002 | B1 |
6559631 | Balch et al. | May 2003 | B1 |
6615147 | Jonker et al. | Sep 2003 | B1 |
6816360 | Brooksby et al. | Nov 2004 | B2 |
6885185 | Makinson et al. | Apr 2005 | B1 |
6957158 | Hancock et al. | Oct 2005 | B1 |
7009379 | Ramirez | Mar 2006 | B2 |
7077317 | Longacre, Jr. et al. | Jul 2006 | B2 |
7088239 | Basinger et al. | Aug 2006 | B2 |
7124948 | Longacre, Jr. et al. | Oct 2006 | B2 |
7135850 | Ramirez | Nov 2006 | B2 |
7209840 | Petite et al. | Apr 2007 | B2 |
7239250 | Brian et al. | Jul 2007 | B2 |
7263073 | Petite et al. | Aug 2007 | B2 |
7348769 | Ramirez | Mar 2008 | B2 |
7385524 | Orlosky | Jun 2008 | B1 |
7469190 | Bickel | Dec 2008 | B2 |
7498953 | Salser, Jr. et al. | Mar 2009 | B2 |
7693670 | Durling et al. | Apr 2010 | B2 |
7847690 | Murphy | Dec 2010 | B2 |
7990806 | Chen | Aug 2011 | B2 |
8004933 | Iseli | Aug 2011 | B2 |
8121741 | Taft et al. | Feb 2012 | B2 |
8223466 | Roscoe | Jul 2012 | B2 |
8322215 | Lakich et al. | Dec 2012 | B2 |
8326554 | Caird | Dec 2012 | B2 |
8635036 | Pamulaparthy et al. | Jan 2014 | B2 |
8754634 | Chamarti et al. | Jun 2014 | B2 |
8830083 | LaFrance et al. | Sep 2014 | B2 |
8854217 | Brown et al. | Oct 2014 | B2 |
8947246 | Aiken | Feb 2015 | B2 |
8978443 | Ramirez | Mar 2015 | B2 |
8996144 | LaFrance et al. | Mar 2015 | B2 |
9099955 | Ramirez | Aug 2015 | B2 |
9110108 | Ramirez | Aug 2015 | B2 |
9146135 | Ramirez | Sep 2015 | B2 |
9164135 | Cs et al. | Oct 2015 | B2 |
9304014 | Komati et al. | Apr 2016 | B2 |
9341686 | Deak et al. | May 2016 | B2 |
9476740 | Zigovszki et al. | Oct 2016 | B2 |
9557392 | Schuhl et al. | Jan 2017 | B2 |
9602895 | Bowling et al. | Mar 2017 | B2 |
9671254 | Zigovszki et al. | Jun 2017 | B2 |
9887051 | LaFrance et al. | Feb 2018 | B2 |
9891088 | Zigovszki et al. | Feb 2018 | B2 |
10036768 | Ramirez | Jul 2018 | B2 |
10240961 | Cheng et al. | Mar 2019 | B2 |
10254315 | Higashi et al. | Apr 2019 | B2 |
10295578 | Higashi et al. | May 2019 | B2 |
20030002233 | Usui | Jan 2003 | A1 |
20030111911 | Hsu | Jun 2003 | A1 |
20040128085 | Ramirez | Jul 2004 | A1 |
20050017702 | Kernahan et al. | Jan 2005 | A1 |
20060091877 | Robinson et al. | May 2006 | A1 |
20060158177 | Ramirez | Jul 2006 | A1 |
20070016340 | Soudier et al. | Jan 2007 | A1 |
20080036447 | Slater et al. | Feb 2008 | A1 |
20080074259 | Houston | Mar 2008 | A1 |
20090015234 | Voisine et al. | Jan 2009 | A1 |
20090016549 | French et al. | Jan 2009 | A1 |
20090055031 | Slota et al. | Feb 2009 | A1 |
20090289501 | Garb | Nov 2009 | A1 |
20100020135 | Morozumi et al. | Jan 2010 | A1 |
20100052655 | King et al. | Mar 2010 | A1 |
20100315263 | Shuey | Dec 2010 | A1 |
20100321883 | Tracy et al. | Dec 2010 | A1 |
20110006748 | Jang et al. | Jan 2011 | A1 |
20110110000 | Etter | May 2011 | A1 |
20110128153 | Sims et al. | Jun 2011 | A1 |
20110163695 | Schmid et al. | Jul 2011 | A1 |
20120096373 | Aguera y Arcas et al. | Apr 2012 | A1 |
20120146529 | Campbell et al. | Jun 2012 | A1 |
20120169311 | Malmberg et al. | Jul 2012 | A1 |
20120194955 | Billingsley et al. | Aug 2012 | A1 |
20130003422 | Persson et al. | Jan 2013 | A1 |
20130018843 | Bultman et al. | Jan 2013 | A1 |
20130077359 | Lindemann et al. | Mar 2013 | A1 |
20130293219 | Ramirez et al. | Nov 2013 | A1 |
20150021996 | Augesky | Jan 2015 | A1 |
20180073910 | Deak et al. | Mar 2018 | A1 |
20180106640 | Padrones et al. | Apr 2018 | A1 |
20190094329 | Minich | Mar 2019 | A1 |
20190101411 | Davis et al. | Apr 2019 | A1 |
20190219618 | Davis et al. | Jul 2019 | A1 |
Number | Date | Country |
---|---|---|
9214300 | Aug 1992 | WO |
2012062367 | May 2012 | WO |
2018071904 | Apr 2018 | WO |
2018072030 | Apr 2018 | WO |
2018083902 | May 2018 | WO |
2019026791 | Feb 2019 | WO |
2019027706 | Feb 2019 | WO |
2019067638 | Apr 2019 | WO |
Entry |
---|
U.S. Appl. No. 10/661,114, Notice of Allowance dated Oct. 3, 2005, 4 pages. |
U.S. Appl. No. 10/661,114, Ex-Parte Quayle Action mailed on Jul. 14, 2005, 4 pages. |
U.S. Appl. No. 11/353,738, Notice of Allowance dated Aug. 14, 2006, 7 pages. |
U.S. Appl. No. 11/365,133, Notice of Allowance dated Oct. 29, 2007, 7 pages. |
U.S. Appl. No. 13/219,947, Final Office Action dated Sep. 2, 2014, 13 pages. |
U.S. Appl. No. 13/219,947, Final Office Action dated Jun. 29, 2016, 27 pages. |
U.S. Appl. No. 13/219,947, Final Office Action dated Nov. 19, 2015, 28 pages. |
U.S. Appl. No. 13/219,947, Non-Final Office Action dated Mar. 25, 2015, 21 pages. |
U.S. Appl. No. 13/219,947, Non-Final Office Action dated Oct. 28, 2013, 20 pages. |
U.S. Appl. No. 13/219,947, Non-Final Office Action dated Feb. 20, 2014, 22 pages. |
U.S. Appl. No. 13/219,947, Non-Final Office Action dated Feb. 4, 2016, 25 pages. |
U.S. Appl. No. 13/219,947, Non-Final Office Action dated Jun. 6, 2017, 33 pages. |
U.S. Appl. No. 13/219,947, Non-Final Office Action dated Oct. 25, 2017, 34 pages. |
U.S. Appl. No. 13/219,947, Notice of Allowance dated Mar. 22, 2018, 11 pages. |
U.S. Appl. No. 13/464,374, Final Office Action dated Nov. 25, 2014, 22 pages. |
U.S. Appl. No. 13/464,374, Non-Final Office Action dated May 23, 2014, 19 pages. |
U.S. Appl. No. 13/464,374, Notice of Allowance dated Apr. 3, 2015, 11 pages. |
U.S. Appl. No. 13/538,159, Notice of Allowance dated Mar. 30, 2015, 9 pages. |
U.S. Appl. No. 13/631,431, Non-Final Office Action dated Nov. 10, 2014, 17 pages. |
U.S. Appl. No. 13/631,431, Notice of Allowance dated Mar. 26, 2015, 6 pages. |
Power: Telecom/Server AC/DC Supply: Single Controller: Analog, Block Diagram (SBD). Texas Instruments, Mar. 5, 2010, 3 pages. |
PCT Patent Application No. PCT/US2020/044722, International Search Report and Written Opinion, dated Oct. 8, 2020, 13 pages. |
Number | Date | Country | |
---|---|---|---|
20210048462 A1 | Feb 2021 | US |