An electric energy distribution system may include plural loads configured to receive electric energy from a common feed or branch. Each of the loads may be configured to operate in at least first and second modes such that it may consume current, VA or power up to a first cap when running in its first mode and up to a second cap when running in its second mode. The first cap may be higher than the second cap. A sensor component may monitor a parameter that corresponds to an aggregate amount of electric energy being consumed by all of the plural loads from the common feed or branch. A manager component may be configured, when the parameter meets or exceeds the threshold, to select one of the loads currently running in its first mode and to cause the selected load to run in its second mode.
|
8. An electric energy distribution system, comprising:
a plurality of loads configured to receive electric energy from a common feed, each respective load of the loads configured to operate in at least first and second modes such that the respective load consumes current, a volt-ampere product, or power up to a first cap when running in the respective load's first mode and up to a second cap when running in the respective load's second mode, wherein the first cap is higher than the second cap;
a sensor configured to monitor a current flowing through a circuit branch that supplies the loads from the common feed, the loads drawing current through a circuit breaker in the circuit branch; and
a manager coupled to the sensor and configured to:
compare the current to a threshold that corresponds to a trip level of the circuit breaker,
in response to the current meeting or exceeding the threshold, select, using a table, a load of the loads currently running in its first mode, the table associating an identifier of the circuit branch with each of the loads in the circuit branch, and the table indicating which mode of the first and second modes each respective load of the loads is currently operating at, and
send a command to the selected load to cause the selected load to run in its second mode.
13. An apparatus comprising:
a sensor to monitor a parameter that corresponds to an aggregate amount of current drawn by plural devices in a circuit branch from a common source, wherein each respective device of the plural devices is configured to operate in at least a first mode and a second mode such that the respective device consumes current, a volt-ampere product, or power up to a first cap when running in the respective device's first mode and up to a second cap when running in the respective device's second mode, wherein the first cap is higher than the second cap, wherein the plural devices draw current through a circuit breaker in the circuit branch; and
a manager coupled to the sensor to:
compare the parameter to a threshold that corresponds to a trip level of the circuit breaker,
select, based on a table, a device of the devices currently running in its first mode, the table associating an identifier of the circuit branch with each of the devices in the circuit branch, the table indicating which setting of the first and second modes each respective device of the devices is currently operating at, and the table further associating identifiers of other circuit branches with other devices and
send a command to the selected device to cause the selected device to run in its second mode in which the selected device draws current from the common source.
1. A method comprising:
configuring at least first and second setting for each respective device of a plurality of devices such that the respective device consumes current, a volt-ampere product, or power up to a first cap when running at the respective device's first setting and up to a second cap when running at the respective device's second setting wherein the first cap is higher than the second cap;
supplying electric energy to the devices from a common source and running each of the devices at their respective first setting, the devices drawing current through a circuit breaker;
sensing a parameter that is proportional to an aggregate amount of electric energy consumed by the devices from the common source, wherein the parameter is an electric current flowing through a circuit branch that supplies the devices, the circuit breaker connected in the circuit branch;
storing a table that associates an identifier of the circuit branch with each of the devices in the circuit branch, the table indicating which setting of the first and second setting each respective device of the devices is currently operating at;
determining that the parameter has reached or exceeded a threshold that corresponds to a trip level of the circuit breaker; and
responsive to the determining, selecting, based on the table, a device of the devices currently running at its first setting, and sending a command to the selected device to cause the selected device to operate at its second setting.
2. The method of
3. The method of
4. The method of
5. The method of
configuring the first settings such that responsive to all of the devices consuming electric energy at their first caps simultaneously, the parameter would exceed the threshold; and
configuring the second settings such that responsive to all of the devices consuming electric energy at their first caps simultaneously, the parameter would not exceed the threshold.
6. The method of
7. The method of
wherein a second entry of the table stores the identifier of the circuit branch, a value specifying which of the first and second settings a second device of the devices is operating at, and a priority value specifying a priority of the second device.
9. The system of
10. The system of
11. The system of
12. The system of
wherein a second entry of the table stores the identifier of the circuit branch, a value specifying which of the first and second settings a second load of the loads is operating at, and a priority value specifying a priority of the second load.
14. The apparatus of
15. The apparatus of
wherein a second entry of the table stores the identifier of the circuit branch, a value specifying which of the first and second settings a second device of the devices is operating at, and a priority value specifying a priority of the second device.
|
This application is a national stage application under 35 U.S.C. §371 of PCT/US2010/22473, filed Jan. 29, 2010.
It is common in a typical data center to house multiple server computers inside a rack. The rack will normally receive at least one feed from an electric utility and will distribute power from the feed to the servers housed inside. A power distribution unit (“PDU”) in the rack includes a circuit breaker for limiting the amount of current being drawn by the servers from the feed. If the circuit breaker should trip, all of the servers dependent on the feed will suffer a power loss.
Refer first to the generic example of
Sensor component 106 may be designed to sense current or voltage or both. In the latter case, the sensed values may be utilized to determine a volt-ampere product (“VA”) or may be utilized to determine a level of power. Persons having skill in the art will appreciate that VA and power are not always identically the same due to characteristics of some loads that may lead to a non-unity power factor. Any conventional technique may be used to measure the parameter of interest. For example, sense resistors, current transformers or Hall-effect devices may be used.
Sensor component 108 may be designed to sense a temperature somewhere on or near loads 104. Any conventional temperature sensing device may be employed. In embodiments that use a temperature sensor 108, it is believed that enhanced accuracy will be obtained by sensing a temperature inside an enclosure 208 that houses all of loads 104. (See
Manager component 110 may be implemented as a discrete component as shown or its functionality may instead be provided by one of loads 104. Manager 110 may be integrated with or into other components if necessary or convenient to do so.
In some embodiments, manager component 110 and sensor component 106 and/or 108 may be housed within a PDU 206 (again see
Buses 112, 114 may take any conventional form, including for example digital serial or parallel buses or one or more wires carrying analog signals. Any signaling protocol may be used. Buses 112, 114 may be different buses in some embodiments or the same bus in other embodiments.
As
It is known in the prior art for a server computer having its own power supply to be able to self-limit its current draw roughly at or below a constant cap. Specifically, a prior art server computer can be manually configured with a current cap value. In operation, such a server computer will invoke a current-reduction mode when a current value being sensed at its own power supply reaches a threshold value. In the current-reduction mode, typically the central processing unit (“CPU”) or other components within the server computer are idled according to a predetermined duty cycle. Thus the server computer can continue to do useful work during portions of the duty cycle in which the CPU is not idled, but over time will draw less current than when not in the current-reduction mode. Although the current cap value for a prior art server computer is manually reconfigurable, the current cap is constant during operation absent manual intervention.
One problem with the constant cap feature of prior art server computers is illustrated in
As
By way of example, mode 600 may correspond to cap level C1, and mode 602 may correspond to cap level C2. Cap level C2 is lower than cap level C1. Thus the maximum current a load 104 may consume when operating at cap=C2 will be less than that of a load operating at cap=C1. Cap level C1 may also correspond to a mode in which no current-reduction technique is employed at all, or equivalently to a mode in which the duty cycle of any current-reduction mechanism employed in the load is set to 100%.
Example behavior of management component 110 will now be described below in relation to
One example of step 802 is illustrated in
Referring again to
In some embodiments, step 812 may be performed such that manager 110 uses priority information 700 and state information 704 to select the lowest priority load 104 that is currently running at its first management setting C1.
In column 1000, each of the three loads is running at its first management setting C1 (as dictated by step 806) but is actually consuming an energy level less than its configured cap level C2. In column 1002, the first load experiences a need to consume more energy. So it is able to increase its consumption level up to its configured cap level C1. In column 1004, the third load also experiences a need to consume more energy. So it increases its consumption level above what would correspond to its configured cap level C2 and begins to approach its configured cap level C1. But when this happens the sensor component and/or manager component detect a breach of threshold 902. So the manager executes steps 812 and 814, this time selecting the third load because of its low priority, and instructing the third load to run at management setting C2. The consequence is that the third load constrains its energy consumption to its lower configured cap C2, as shown at column 1006. All the while, the first load is still able to consume up to its higher configured cap C1 because of its higher priority.
In column 1008, assume now that the second load experiences a need to increase its energy consumption, and that it begins consuming energy at a level higher than its configured cap C2. The result in this case is another threshold violation. So manager 110 again executes steps 812 and 814. This time it selects the second load because the second load is now the lowest priority load currently running at its first management setting C1. Manager 110 instructs the second load to run at its second management setting C2, as shown in column 1010. But in this case the result is still a threshold violation. So manager 110 executes steps 812 and 814 one more time. On this final iteration, it selects the first load because it is now the lowest priority load currently operating at its first management setting C1. It instructs the first load to run at its second management setting C2, as shown in column 1012. All three loads may now operate safely below threshold 902. But the highest priority load was allowed to operate at its highest energy consumption longer than the other two, lower-priority loads.
While the invention has been described in detail with reference to preferred embodiments thereof, the described embodiments have been presented by way of example and not by way of limitation. It will be understood by those skilled in the art and having reference to this specification that various changes may be made in the form and details of the described embodiments without deviating from the spirit and scope of the invention as defined by the appended claims.
Bemat, Mohamed Amin, Humphrey, Daniel
Patent | Priority | Assignee | Title |
10256646, | May 02 2017 | Panasonic Avionics Corporation | Seat box power management |
10763672, | Sep 25 2014 | Enatel Limited | In and relating to load balancing |
9715271, | May 06 2014 | Microchip Technology Incorporated | USB power port control |
9914548, | Feb 22 2017 | Imagik International Corporation | USB power management and load distribution system |
Patent | Priority | Assignee | Title |
5051861, | Jan 09 1990 | General Electric Company | Multiple circuit interrupter address identification system |
5495406, | Sep 14 1988 | Mitsubishi Denki Kabushiki Kaisha | Load control system |
5754445, | Dec 20 1995 | ASTRONICS ADVANCED ELECTRONIC SYSTEMS CORP | Load distribution and management system |
6330516, | Mar 27 2000 | POWER DISTRIBUTION, INC | Branch circuit monitor |
7453267, | Jan 14 2005 | SCHNEIDER ELECTRIC USA, INC | Branch circuit monitor system |
7657763, | Dec 29 2005 | PANASONIC ELECTRIC WORKS CO , LTD | Systems and methods for selectively controlling electrical outlets using power profiling |
7865272, | Jan 02 2002 | Schneider Electric IT Corporation | Method and apparatus for preventing overloads of power distribution networks |
8018348, | Feb 19 2009 | Apparatus for identifying a circuit breaker feeding a remotely disposed electrical outlet and method of using the apparatus | |
8229602, | Jan 19 2009 | 2D2C, Inc.; 2D2C, INC | Electrical power distribution system |
8324755, | Mar 06 2009 | Briggs & Stratton, LLC | Power management system and method of operating the same |
8719123, | Dec 05 2011 | Reporting circuit breaker and system | |
8850240, | Aug 25 2011 | International Business Machines Corporation | Branch circuit determination with synchronous correlation |
20030196126, | |||
20040078153, | |||
20070245161, | |||
20070300085, | |||
20080172312, | |||
20080178019, | |||
20080184230, | |||
20080221737, | |||
20080222435, | |||
20080313492, | |||
20090125737, | |||
20090187783, | |||
20090276651, | |||
20100010683, | |||
20100037077, | |||
20100070787, | |||
20100174419, | |||
20100207604, | |||
20100256934, | |||
20100332872, | |||
20110144818, | |||
CN101277200, | |||
CN101354606, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Jan 28 2010 | HUMPHREY, DANIEL | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027853 | /0070 | |
Jan 28 2010 | BEMAT, MOHAMED AMIN | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 027853 | /0070 | |
Jan 29 2010 | Hewlett Parkard Enterprise Development LP | (assignment on the face of the patent) | / | |||
Oct 27 2015 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | Hewlett Packard Enterprise Development LP | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 037079 | /0001 |
Date | Maintenance Fee Events |
Jun 24 2019 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Aug 28 2023 | REM: Maintenance Fee Reminder Mailed. |
Feb 12 2024 | EXP: Patent Expired for Failure to Pay Maintenance Fees. |
Date | Maintenance Schedule |
Jan 05 2019 | 4 years fee payment window open |
Jul 05 2019 | 6 months grace period start (w surcharge) |
Jan 05 2020 | patent expiry (for year 4) |
Jan 05 2022 | 2 years to revive unintentionally abandoned end. (for year 4) |
Jan 05 2023 | 8 years fee payment window open |
Jul 05 2023 | 6 months grace period start (w surcharge) |
Jan 05 2024 | patent expiry (for year 8) |
Jan 05 2026 | 2 years to revive unintentionally abandoned end. (for year 8) |
Jan 05 2027 | 12 years fee payment window open |
Jul 05 2027 | 6 months grace period start (w surcharge) |
Jan 05 2028 | patent expiry (for year 12) |
Jan 05 2030 | 2 years to revive unintentionally abandoned end. (for year 12) |