Patent Grant
10886776
The presently disclosed subject matter relates generally to power distribution. Particularly, the presently disclosed subject matter relates to power distribution systems having a bi-directional link for delivery of power between each other.
In data centers, power distributions units (PDUs) are often used to distribute electric power to servers and networking equipment via multiple outputs. A PDU may have different forms such as being a rack-mounted power strip to being a larger PDU that stands on the floor. Functions of a PDU include power filtering to improve power quality, intelligent load balancing, and remote monitoring and control.
In some instances, multiple PDUs may provide power to multiple servers and other equipment held by a server chassis. For example, in one server chassis one set of power supply units (PSUs) may be operably connected to one PDU, and another set of PSUs may be operably connected to another PDU. Each PSU may be connected to an individual server or other equipment held by the server chassis.
It is important to maintain a continuous supply of power to equipment within a data center, particularly to the servers and other equipment held by a server chassis. In an example of fault, power supplied to one PDU at a server chassis may fail, while the other continues to be supplied with power. In this scenario, unless action is taken or the system can manage the power supply failure, servers connected to the PDU no longer receiving power will also no longer receive power and thus can no longer operate. Therefore, there is a need to provide systems and techniques that can manage a power supply failure to PDU at a server chassis such that power supply to servers and other equipment at the server chassis is maintained.
Having thus described the presently disclosed subject matter in general terms, reference will now be made to the accompanying Drawings, which are not necessarily drawn to scale, and wherein:
The presently disclosed subject matter includes power distribution systems having a bi-directional link for delivery of power between each other. According to an aspect, a PDU includes a first power inlet configured to receive electric power from a power source. The PDU also includes a second power inlet configured to receive electric power from another power distribution unit. Further, the PDU includes multiple power outlets. The PDU also include an electric power router configured to determine whether the power source is in a fault condition for delivering electric power to the first power inlet. Further, the electric power router is configured to communicatively engage the other PDU for managing receipt of electric power from the other PDU in response to determining that the power source is in the fault condition. Also, the electric power router is configured to receive, at the second power inlet, electric power from the other PDU. The electric power router is also configured to route, to the power outlets, the electric power received from the other PDU.
According to another aspect, a PDU includes a power inlet configured to receive electric power from a power source. Further, the PDU includes a power outlet configured to deliver power to another PDU. The PDU also includes an electric power router configured to receive an indication from the other PDU that power is needed. The electric power router is also configured to route, to the other PDU, electric power received at the power inlet in response to receiving the indication.
According to another aspect, a power distribution system includes a power inlet configured to receive electric power from a first power source. The power distribution system also includes power outlets for distribution of the electric power received from the first power source. Further, the power distribution system includes an input/output module configured to receive from a second power distribution unit and to deliver electric power to the second power distribution unit via a bi-directional link cable operatively connecting the input/output module to a second input/output module of the second power distribution unit. The power distribution system also includes an electric power router configured to determine whether the power source is in a fault condition for delivering electric power to the power inlet. The electric power router is also configured to communicatively engage the other power distribution unit for managing receipt of electric power from the other power distribution unit in response to determining that the power source is in the fault condition. Further, the electric power router is configured to receive, at the input/output module, electric power from the other power distribution unit in response to determining that the power source is in the fault condition. The electric power router is also configured to route, to the power outlets, the electric power received from the other power distribution unit. Further, the electric power router is configured to receive an indication from the other power distribution unit that power is needed. The electric power router is also configured to route, to the other power distribution unit, electric power received at the power inlet in response to receiving the indication.
The following detailed description is made with reference to the figures. Exemplary embodiments are described to illustrate the disclosure, not to limit its scope, which is defined by the claims. Those of ordinary skill in the art will recognize a number of equivalent variations in the description that follows.
Articles “a” and “an” are used herein to refer to one or to more than one (i.e. at least one) of the grammatical object of the article. By way of example, “an element” means at least one element and can include more than one element.
“About” is used to provide flexibility to a numerical endpoint by providing that a given value may be “slightly above” or “slightly below” the endpoint without affecting the desired result.
The use herein of the terms “including,” “comprising,” or “having,” and variations thereof is meant to encompass the elements listed thereafter and equivalents thereof as well as additional elements. Embodiments recited as “including,” “comprising,” or “having” certain elements are also contemplated as “consisting essentially of” and “consisting” of those certain elements.
Recitation of ranges of values herein are merely intended to serve as a shorthand method of referring individually to each separate value falling within the range, unless otherwise indicated herein, and each separate value is incorporated into the specification as if it were individually recited herein. For example, if a range is stated as between 1%-50%, it is intended that values such as between 2%-40%, 10%-30%, or 1%-3%, etc. are expressly enumerated in this specification. These are only examples of what is specifically intended, and all possible combinations of numerical values between and including the lowest value and the highest value enumerated are to be considered to be expressly stated in this disclosure.
Unless otherwise defined, all technical terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
The functional units described in this specification have been labeled as computing devices. A computing device may be implemented in programmable hardware devices such as processors, digital signal processors, central processing units, field programmable gate arrays, programmable array logic, programmable logic devices, cloud processing systems, or the like. The computing devices may also be implemented in software for execution by various types of processors. An identified device may include executable code and may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, function, or other construct. Nevertheless, the executable of an identified device need not be physically located together but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the computing device and achieve the stated purpose of the computing device. In an example, a computing device can include a server operating in a data center. Servers and other computing devices may be operable to access the Internet (or other communications network).
An executable code of a computing device may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different applications, and across several memory devices. Similarly, operational data may be identified and illustrated herein within the computing device, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, as electronic signals on a system or network.
The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, to provide a thorough understanding of embodiments of the disclosed subject matter. One skilled in the relevant art will recognize, however, that the disclosed subject matter can be practiced without one or more of the specific details, or with other methods, components, materials, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the disclosed subject matter.
As used herein, the term “memory” is generally a storage device of a computing device. Examples include, but are not limited to, read-only memory (ROM) and random access memory (RAM).
The device or system for performing one or more operations on a memory of a computing device may be a software, hardware, firmware, or combination of these. The device or the system is further intended to include or otherwise cover all software or computer programs capable of performing the various heretofore-disclosed determinations, calculations, or the like for the disclosed purposes. For example, exemplary embodiments are intended to cover all software or computer programs capable of enabling processors to implement the disclosed processes. Exemplary embodiments are also intended to cover any and all currently known, related art or later developed non-transitory recording or storage mediums (such as a CD-ROM, DVD-ROM, hard drive, RAM, ROM, floppy disc, magnetic tape cassette, etc.) that record or store such software or computer programs. Exemplary embodiments are further intended to cover such software, computer programs, systems and/or processes provided through any other currently known, related art, or later developed medium (such as transitory mediums, carrier waves, etc.), usable for implementing the exemplary operations disclosed below.
In accordance with the exemplary embodiments, the disclosed computer programs can be executed in many exemplary ways, such as an application that is resident in the memory of a device or as a hosted application that is being executed on a server and communicating with the device application or browser via a number of standard protocols, such as TCP/IP, HTTP, XML, SOAP, REST, JSON and other sufficient protocols. The disclosed computer programs can be written in exemplary programming languages that execute from memory on the device or from a hosted server, such as BASIC, COBOL, C, C++, Java, Pascal, or scripting languages such as JavaScript, Python, Ruby, PHP, Perl, or other suitable programming languages.
As referred to herein, the terms “computing device” and “entities” should be broadly construed and should be understood to be interchangeable. They may include any type of computing device, for example, a server, a desktop computer, a laptop computer, or the like.
In operation and when fully functional or at least sufficiently functional for supplying power, power sources 108 and 110 may supply electric power to PDUs 102 and 104, respectfully, via cables, 116 and 118, respectfully. Arrows 116A and 118A show the direction of power being supplied to power inlets 1 and 2 of PDU 102 and 104, respectively. Further, the PDUs 102 and 104 may each include an electric power router 119 that is configured to route and to distribute electric power received from power sources 108 and 110, respectively, to groups of power supply units (PSUs) (numbered individually 1-6 in each group) 120 and 122, respectively. The PSUs each function as power outlets, thus in this example PDU 102 has 6 power outlets, and PDU 104 has 6 power outlets. For example, the electric power router 119 may deliver to each PSU 1-6 in group 120 AC power at 30 A. In another example, the range can be between about 20 and 63 A. The PSUs may be connected or available for connection to one or more servers and/or other network equipment held in a server chassis. For example, one or more of the PSUs in group 120 may be connected to one or more servers in a group (designated group A 124) and provide 30 A of AC power. Further, for example, one or more of the PSUs in group 122 may be connected to one or more servers in a group (designated group B 126) and provide 30 A of AC power. It is noted that PDUs 102 and 104 and groups A and B 124 and 126 of the servers and/or other network equipment may be held by a server chassis.
In accordance with embodiments, PDUs 102 and 104 may each include another power inlet 128 and 130, respectively. Each power inlet 128 and 130 is operable to receive power supplied from a power source that is an alternative to power sources 108 and 110, respectively, for distribution of electric power to groups 124 and 126, respectively. The electric power from the alternate power source may be needed in the instance of a power failure of power sources 108 or 110, or insufficient power being supplied by power sources 108 or 110. In such an instance, one of PDUs 102 and 104 may be provided electric power from the other PDU at its power inlet 112 or 114, respectively, as will be described in more detail herein.
In an example of a failure condition at power source 108, electric power router 119 may determine that the power source 108 is no longer delivering electric power to power inlet 112 of PDU 102. In response to determining that the power source 108 is in a fault condition, the electric power router 119 may communicatively engage PDU 104 for managing receipt of electric power from the PDU 104. For example, the electric power router 119 of PDU 102 may communicate to PDU 104 a signal (represented by arrow 132) indicating a fault condition or otherwise that requests provision of electric power from PDU 104. The signal 132 may be suitably communicated to PDU 104, such as via a cable 134 of the bi-directional link system 106. Subsequently, the electric power router 119 of PDU 104 may receive the indication of the fault condition, and route electric power from power source 110 to power inlet 128 of PDU 102 in response to receipt of the indication. For example, the power may be provided via cable 134. Arrow 134A depicts the direction of the flow of electric power from PDU 104 to PDU 102 via the cable 134. The electric power router 119 at PDU 102 may route and distribute the electric power received at power inlet 128 to PSUs 1-6 in group 120.
Conversely, in the event of a fault condition at power source 110, PDU 104 may similarly request power from PDU 102. Upon receipt of the request, PDU 102 may similarly provide electric power to PDU 104. In this scenario, the power may be provided via cable 134 or another cable operatively connecting PDUs 102 and 104. Arrow 134B depicts the direction of the flow of electric power from PDU 102 to PDU 104 via the cable 134. The electric power router 119 at PDU 104 may route and distribute the electric power received at power inlet 130 to PSUs 1-6 in group 122.
With continuing reference to
The provision of electric power may be handed off may be effected by any suitable technique. For example, transistor logic hardware may detect voltage signaling for determining whether to perform handoff. In this example, the cable 134 may include 3 wires in addition to high power wires, or the PDUs 102 and 104 may be separately connected by the 3 wires. The wires may include a wire for Signal 1, a wire for Signal 2, and a wire for ground. Signal 1 may be self-powered and go to Signal 2 on the other PDU. Signal 2 may be passive and go to Signal 1 on the other PDU. If a PDU senses an AC loss, it may drop voltage on Signal 1 and switch its main input to the bridge input. If a PDU senses a voltage drop on Signal 2 input, it may route part of its input power to the bridge. If both signal pins drop, there is no action as this would mean a total AC loss in both PDUs. If both signal pins are high, there is no action (i.e., no outages).
In response to determining that the primary power source is in the fault condition, the electric power router 119 may communicatively engage another PDU for managing receipt of electric power from the other PDU. For example, the electric power router 119 may include an input/output (I/O) module 404 configured to communicate to another PDU that a fault condition exists. In an example, I/O module 404 may be implemented for communicating to another PDU with transistor logic hardware described by example herein. This hardware may use, for example, protocols such as i2C, SNMP, or the like. There may be an implementation of multiple types of communications, such as direct transistor logic for the transfer controls and a slower protocol for data transit. These can be used in conjunction such as for centralized logging of power events, power balancing, statistics and remote administration/monitoring. They can be implemented through the bridge cable and also through standard ports such as Ethernet RJ45. The communication may be, for example, via a power cable, a communication cable, wireless communication, or the like. One PDU can communicate a fault condition to another PDU through, for example, the aforementioned transistor logic using AC or DC power to actuate directly over a power logic circuit, which may include capacitors, transistors, relays, and the like. In other example of “smart” functions, router 119 may include two components: one for the basic power transfer logic which is in charge of the fast switching of the high voltage part; and another component for the “smart” part, which is monitoring over network, statistics, individual port controls, manual override of the transfer logic (such as for testing or for maintenance), logging, and such. The other PDU may acknowledge receipt of the communication. Subsequently, PDU 400 and the other PDU may coordinate for the delivery of electric power from the other PDU to PDU 400 at a bi-directional link cable connector 401. Arrow 403 is representative of electric power input into connector 401, and arrow 405 is representative of electric power input into power inlet 112. Further, PDU 400 and the other PDU may be connected as shown in
PDU 400 may coordinate with another PDU to provide electric power to the other PDU. For example, the I/O module 404 may be operatively connected to another PDU for receipt of communications. The I/O module 404 may receive a message indicating that the primary power source at the other PDU is in a fault condition to thereby indicate that power is needed at the other PDU. In response to receiving the indication, the electric power router 119 can route, to the other PDU, electric power received at power inlet 112 to the other PDU.
The electric power router 119 may be configured to implement the functionality described herein. The electric power router 119 may include hardware, software, firmware, and combinations thereof. For example, the electric power router 119 may include one or more processors 406 and memory 408 for implementing the functionality described herein. The processor(s) 406 may implement software code for implementing the functions of the electric power router 119.
Referring to
At step 502, the method includes communicatively engaging another PDU for managing receipt of electric power from the other PDU. Continuing the aforementioned example, the electric power router 119 may use its I/O module 404 to signal another PDU or electronic device to provide power. The other PDU may be connected to connector 401 of PDU 400 such that it can provide electric power to the connector 401. In response to receipt of the signal, the other PDU may provide electric power via a cable to the connector 401 of PDU 400.
The method of
The method of
At step 508, the method includes signaling to the other PDU to discontinue providing electric power, and routing electric power from the primary power source to the power outlets. Continuing the aforementioned example, the electric power router 119 may signal to the other PDU to discontinue providing electric power. Further, the electric power router 119 may route power from the power inlet 112, where the primary power source is connected, to the PSUs of group 120. Subsequently, the method may return to step 500.
Referring to
The method of
In accordance with embodiments, the source of electric power supplied at a PDU, such as PDU 400, may be input into either power inlet 112 or connector 401. As described herein, there may be a switch of the power source and circuitry may be configured to suitably handle the switching of load to ensure that the switch is stable. For example, an automatic transfer switch (ATS) may handle the switch for ensuring stability. For example, the ATS may enable load transfer through a bi-directional link system, such as system 106 shown in
In accordance with embodiments, PDUs such as PDUs 102 and 104 shown in
The present subject matter may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present subject matter.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a RAM, a ROM, an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network, or Near Field Communication. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present subject matter may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++, Javascript or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present subject matter.
Aspects of the present subject matter are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the subject matter. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present subject matter. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
While the embodiments have been described in connection with the various embodiments of the various figures, it is to be understood that other similar embodiments may be used, or modifications and additions may be made to the described embodiment for performing the same function without deviating therefrom. Therefore, the disclosed embodiments should not be limited to any single embodiment, but rather should be construed in breadth and scope in accordance with the appended claims.
| Number | Name | Date | Kind |
|---|---|---|---|
| 20090031153 | Bahali et al. | Jan 2009 | A1 |
| 20160371955 | Alshinnawi et al. | Dec 2016 | A1 |
