US20170220089A1 - Systems and methods for management controller enhanced power supply unit current sharing - Google Patents
Systems and methods for management controller enhanced power supply unit current sharing Download PDFInfo
- Publication number
- US20170220089A1 US20170220089A1 US15/014,766 US201615014766A US2017220089A1 US 20170220089 A1 US20170220089 A1 US 20170220089A1 US 201615014766 A US201615014766 A US 201615014766A US 2017220089 A1 US2017220089 A1 US 2017220089A1
- Authority
- US
- United States
- Prior art keywords
- power supply
- current
- bus
- supply unit
- current share
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/266—Arrangements to supply power to external peripherals either directly from the computer or under computer control, e.g. supply of power through the communication port, computer controlled power-strips
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
- G06F1/26—Power supply means, e.g. regulation thereof
- G06F1/263—Arrangements for using multiple switchable power supplies, e.g. battery and AC
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
- G06F13/36—Handling requests for interconnection or transfer for access to common bus or bus system
- G06F13/362—Handling requests for interconnection or transfer for access to common bus or bus system with centralised access control
Definitions
- the present disclosure relates in general to information handling systems, and more particularly to systems and methods for current sharing between power supply units in an information handling system.
- An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information.
- information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated.
- the variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications.
- information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
- An information handling system may include one or more power supply units for providing electrical energy to components of the information handling system.
- a power supply unit is configured to operate from an input alternating current (AC) source of electrical energy, which the power supply unit converts to a direct current (DC) output.
- AC alternating current
- DC direct current
- a power supply unit may include a rectifier and/or power factor correction stage to receive the input AC source and rectify the input AC waveform to charge a bulk capacitor to a desired voltage.
- a direct-current-to-direct-current (DC-DC) stage may convert the voltage on the bulk capacitor to a DC output voltage which may be used to power components of the information handling system.
- an information handling system may include a processor, a management controller communicatively coupled to the processor, and a plurality of power supply units communicatively coupled to the management controller for supplying electrical energy to one or more information handling resources of the information handling system via a power bus.
- Each of the plurality of power supply units may be configured to, when the management controller is able to control the plurality of power supply units: (i) receive an indication from the management controller whether such power supply unit is selected as a master of a current share bus; (ii) if such power supply unit is selected as the master, drive a current share signal on the current share bus, the current share signal indicative of an output current driven by such power supply unit on the power bus; and (iii) if such power supply unit is not selected as the master, monitor the current share signal and drive the output current to the power bus in accordance with the current share signal.
- Each of the plurality of power supply units may be also be configured to, when the management controller is unable to control the plurality of power supply units: (i) attempt to drive the current share signal on the current share bus; and (ii) monitor the current share signal and drive the output current to the power bus in accordance with the current share signal.
- a power supply unit may include a power train and a controller communicatively coupled to the power train and configured to receive an indication whether a management controller is able to control the power supply unit.
- the controller may further be configured to: (i) receive an indication from the management controller whether the power supply unit is selected as a master of a current share bus; (ii) if the power supply unit is selected as the master, drive a current share signal on the current share bus, the current share signal indicative of an output current driven by the power train on a power bus; and (iii) if the power supply unit is not selected as the master, monitor the current share signal and drive the output current to the power bus in accordance with the current share signal.
- the controller may further be configured to: (i) attempt to drive the current share signal on the current share bus; and (ii) monitor the current share signal and drive the output current to the power bus in accordance with the current share signal.
- a method may include determining whether a management controller is able to control a plurality of power supply units. The method may also include, when the management controller is able to control the plurality of power supply units: (i) selecting a power supply unit of the plurality of power supply units as a master of a current share bus; (ii) driving, by the power supply unit selected as the master, a current share signal on the current share bus, the current share signal indicative of an output current driven by the power supply unit selected as the master; and (iii) monitoring, by power supply units other than the power supply unit selected as the master, the current share signal and driving, by power supply units other than the power supply unit selected as the master, respective output currents to the power bus in accordance with the current share signal.
- the method may also include, when the management controller is unable to control the plurality of power supply units: (i) attempting, by each of the plurality of power supply units, to drive the current share signal on the current share bus; and (ii) monitoring, by each of the power supply units, the current share signal and driving, by each of the power supply units, the output current to the power bus in accordance with the current share signal.
- FIGS. 1A-1C illustrates a block diagram of an example information handling system, in accordance with embodiments of the present disclosure
- FIG. 2 illustrates a flow chart of an example method for current sharing in a normal mode of a power system, in accordance with embodiments of the present disclosure
- FIG. 3 illustrates a flow chart of an example method for current sharing in a master fault mode of a power system, in accordance with embodiments of the present disclosure
- FIG. 4 illustrates a flow chart of an example method for current sharing in a swap mode of a power system, in accordance with embodiments of the present disclosure.
- FIGS. 1A through 4 Preferred embodiments and their advantages are best understood by reference to FIGS. 1A through 4 , wherein like numbers are used to indicate like and corresponding parts.
- an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes.
- an information handling system may be a personal computer, a personal data assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price.
- the information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic.
- Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display.
- the information handling system may also include one or more buses operable to transmit communication between the various hardware components.
- Computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time.
- Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.
- storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-
- information handling resources may broadly refer to any component system, device or apparatus of an information handling system, including without limitation processors, service processors, basic input/output systems (BIOSs), buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, power supplies, air movers (e.g., fans and blowers) and/or any other components and/or elements of an information handling system.
- processors service processors, basic input/output systems (BIOSs), buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, power supplies, air movers (e.g., fans and blowers) and/or any other components and/or elements of an information handling system.
- BIOSs basic input/output systems
- FIGS. 1A-1C (which may collectively be referred to herein as “ FIG. 1 ”) illustrate a block diagram of an example of an information handling system 102 .
- information handling system 102 may include one or more power supply units (PSUs) 110 , a motherboard 101 , and one or more other information handling resources.
- PSUs power supply units
- Motherboard 101 may include a circuit board configured to provide structural support for one or more information handling resources of information handling system 102 and/or electrically couple one or more of such information handling resources to each other and/or to other electric or electronic components external to information handling system 102 .
- motherboard 101 may include a processor 103 , a memory 104 , a management controller 106 , and one or more other information handling resources.
- Processor 103 may comprise any system, device, or apparatus operable to interpret and/or execute program instructions and/or process data, and may include, without limitation a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data.
- processor 103 may interpret and/or execute program instructions and/or process data stored in memory 104 and/or another component of information handling system 102 .
- Memory 104 may be communicatively coupled to processor 103 and may comprise any system, device, or apparatus operable to retain program instructions or data for a period of time.
- Memory 104 may comprise random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to information handling system 102 is turned off.
- RAM random access memory
- EEPROM electrically erasable programmable read-only memory
- PCMCIA card PCMCIA card
- flash memory magnetic storage
- opto-magnetic storage or any suitable selection and/or array of volatile or non-volatile memory that retains data after power to information handling system 102 is turned off.
- memory 104 may comprise a non-volatile memory comprising one or more non-volatile dual-inline memory modules (NVDIMMs).
- NVDIMMs non-vol
- Management controller 106 may be configured to provide out-of-band management facilities for management of information handling system 102 . Such management may be made by management controller 106 even if a host system of information handling system 102 is powered off or powered to a standby state. Management controller 106 may include a processor, memory, an out-of-band network interface separate from and physically isolated from an in-band network interface of information handling system 102 , and/or other embedded information handling resources. In certain embodiments, management controller 106 may include or may be an integral part of a baseboard management controller (BMC) or a remote access controller (e.g., a Dell Remote Access Controller or Integrated Dell Remote Access Controller). In other embodiments, management controller 106 may include or may be an integral part of a chassis management controller (CMC).
- BMC baseboard management controller
- CMC chassis management controller
- management controller 106 may be configured to communicate with PSUs 110 to control which PSUs 110 are enabled to operate as a master (as opposed to a slave) of a current share bus and/or which PSU 110 is set as a dedicated master of the current share bus, as described in greater detail below.
- a PSU 110 may include any system, device, or apparatus configured to supply electrical current to one or more information handling resources of information handling system 102 .
- a PSU 110 may include a controller 112 and a power train 114 .
- Each power train 114 may be coupled at its outputs to a power bus configured to deliver electrical energy to motherboard 101 and other components of information handling system 102 .
- Controller 112 may comprise a microprocessor, DSP, ASIC, FPGA, EEPROM, or any combination thereof, or any other device, system, or apparatus for controlling operation of PSU 110 .
- controller 112 may comprise firmware, logic, and/or data for controlling functionality of PSU 110 .
- controller 112 may couple to a current share bus (as labeled with “V share BUS” in FIG. 1 ) with PSUs 110 in order to establish a current share for the various currents delivered to the power bus by PSUs 110 .
- V share BUS current share bus
- each controller 112 may comprise a current monitor 118 , a current aggregator 120 , a PSU location indicator 122 , a master/slave gate 124 , a current share bus voltage computation block 126 , and a current share bus driver 128 .
- Each current monitor 118 may comprise any suitable system, device, or apparatus for sensing a current delivered by a power train 114 of a PSU 110 to the power bus and generating a signal I mon indicative of such current.
- such current monitor 118 may include a resistor which generates a voltage indicative of the current, in accordance with Ohm's law.
- Each current aggregator 120 may comprise any suitable system, device, or apparatus for sensing an aggregate current delivered by all PSUs 110 of information handling system 102 and generating a signal I Total indicative of such aggregate current.
- such current aggregator 120 may include a resistor which generates a voltage indicative of the aggregate current, in accordance with Ohm's law.
- a PSU location indicator 122 may comprise any suitable system, device, or apparatus for determining, out of a plurality of multiple PSU bays in information handling system 102 , in which PSU bay a PSU 110 is located. In some embodiments, such determination may be made based on information communicated from an Inter-Integrated Circuit (I2C) bus or other communications bus of information handling system 102 .
- I2C Inter-Integrated Circuit
- a master/slave gate 124 may comprise any system, device, or apparatus configured to receive information regarding a voltage V share present on a current share bus, a monitored current I mon generated by a power train 114 , an aggregate current I Total generated by PSUs 110 , a location of a PSU 110 , and/or control variable settings of PSU 110 , and based on such received information, determine whether a PSU 110 is to drive a voltage on the current share bus.
- Control variable settings may be set by management controller 106 when management controller 106 is active (e.g., via a bus labeled as “CONTROL BUS” in FIG. 1 ), or in the event that management controller 106 is not active or experiences a fault, may be set to default values of such control variable settings.
- control settings may include a dedicated master variable DED_MASTER and a current share bus drive variable DRIVE.
- a current share bus drive variable DRIVE of a PSU 110 controls whether a PSU 110 drives the current share bus
- dedicated master variable DED_MASTER controls whether a PSU 110 is set by management controller 106 to be a dedicated master of the current share bus.
- dedicated master variable DED_MASTER may be implemented using a single bit (e.g., a value of logic “1” to set a PSU 110 to be the dedicated master of the current share bus and a value of logic “0” to indicate that the PSU 110 is not the dedicated master).
- current share bus drive variable DRIVE may be implemented using a single bit (e.g., a value of logic “1” to cause PSU 110 to drive the current share bus and a value of logic “0” to disable a PSU 110 from driving the current share bus).
- DED_MASTER DRIVE EFFECT 0 0 PSU 110 acts as a slave with respect to current share bus; controls power train 114 based on voltage read from current share bus 1 0 PSU 110 acts as a slave with respect to current share bus; controls power train 114 based on voltage read from current share bus 0 1 PSU 110 drives current share bus and attempts to become master; if not master (e.g., if voltage driven to current share bus is not the highest of all voltages driven to current share bus), controls power train 114 based on voltage read from current share bus 1 1 PSU 110 is dedicated master and drives current share bus
- Each current share bus voltage computation block 126 may comprise any suitable system, device, or apparatus for computing, for a PSU 110 enabled to drive the current share bus (e.g., those PSUs 110 with a current share bus drive variable DRIVE of logic “1”), a voltage to be driven by the PSU 110 on the current share bus.
- a voltage to be driven by the PSU 110 on the current share bus may be based on the aggregate current I Total and the number of active PSUs 110 (which may be estimated based on the aggregate current I Total and the monitored current I mon for the particular PSU 110 ).
- a signal indicative of such voltage to be driven may be communicated by current share bus voltage computation block 126 to a current share bus driver 128 of the PSU 110 .
- Each current share bus driver 128 may comprise any suitable system, device, or apparatus (e.g., electronic or electrical circuit) for driving a voltage on the current share bus based on a signal communicated to such current share bus driver 128 by its associated current share bus voltage computation block 126 .
- a current share bus driver 128 may include circuitry (e.g., an output diode), such that a current share bus driver 128 drives the current share bus only if such current share bus driver 128 is attempting to drive a voltage larger than that driven by the current share bus drivers 128 of other PSUs 110 .
- Power train 114 may include any suitable system, device, or apparatus for converting electrical energy received by PSU 110 (e.g., a 120-volt alternating current or 240-volt alternating current voltage waveform, a 48-volt DC or 240-volt DC or 380-volt DC direct current voltage waveform) from an input source into electrical energy usable to information handling resources of information handling system 102 (e.g., 12-volt direct current voltage source).
- power train 114 may comprise a rectifier, a power factor correction circuit, and/or a direct-current-to-direct-current converter.
- power train 114 may comprise a voltage regulator (e.g., a multi-phase voltage regulator).
- one or more PSUs 110 may share an input source.
- a power train 114 may deliver an amount of electrical current to the power bus in accordance with a control signal communicated from controller 112 indicative of a desired amount of electrical current to be delivered.
- control signal may comprise the voltage V share present on the current share bus or a control signal indicative of the voltage V share present on the current share bus, such that the power train 114 is controlled by the voltage V share present on the current share bus.
- information handling system 102 may include one or more other information handling resources.
- information handling system 102 may include a number of PSUs 110 other than three.
- FIG. 2 illustrates a flow chart of an example method 200 for current sharing in a normal mode of a power system, in accordance with embodiments of the present disclosure.
- start-up mode may occur during an initial powering on of the power system comprising PSUs 110 during which management controller 106 may itself be initializing and not yet able to provide active control of PSUs 110 .
- method 200 may begin at step 202 .
- teachings of the present disclosure may be implemented in a variety of configurations of information handling system 102 . As such, the preferred initialization point for method 200 and the order of the steps comprising method 200 may depend on the implementation chosen.
- management controller 106 may not be able to set control variable settings for PSUs 110 and accordingly, such control variable settings may assume default values.
- PSUs 110 may assume default values such that their respective dedicated master variables DED_MASTER are set to logic “0” and their respective current share bus drive variables DRIVE are set to logic “1.” With such default settings, each PSU 110 may drive or attempt to drive the current share bus and may attempt to become a master of the current share bus.
- the PSU 110 driving the highest voltage to the current share bus may become the master of the current share bus. Accordingly, at step 206 , all other PSUs 110 may act as slaves, and may attempt to “catch up” to the master by increasing their respective output currents.
- PSUs 110 may determine if management controller 106 has completed initialization such that it is able to control PSUs 110 . Such determination may be made by reading information communicated from management controller 106 indicative of its status (e.g., by communicating appropriate signals over the control bus indicated in FIG. 1 ). If management controller 106 is able to control PSUs 110 , method 200 may proceed to step 210 . Otherwise, method 200 may proceed again to step 204 .
- management controller 106 may select a PSU 110 to act as the master of the current share bus. Such selection may be made in any suitable manner (e.g., based on one or more parameters associated with PSUs 110 ) and mechanisms for making such selection are beyond the scope of this disclosure.
- management controller 106 may (e.g., by communicating appropriate signals over the control bus indicated in FIG. 1 ) set the dedicated master variable DED_MASTER for the selected master to logic “1” and set the current share bus drive variable DRIVE for all PSUs 110 other than the selected master (i.e., the slave PSUs 110 ) to logic “0.” Accordingly, at step 214 , only the selected master PSU 110 may drive the current share bus, and all other PSUs 110 will follow the voltage V share driven on the current share bus in generating their own output currents.
- management controller 106 may determine if a fault condition exists in the master PSU 110 .
- Such fault condition may include a loss of input source or any other condition compromising the ability of the master PSU 110 to generate an output current. If a fault condition exists in the master PSU 110 , operation may proceed to a master fault mode, as described in greater detail below with respect to method 300 . If no fault condition exists in master PSU 110 , method 200 may proceed to step 218 .
- one or more PSUs 110 may determine if a fault condition exists in management controller 106 .
- Such fault condition may include any condition in which management controller 106 ceases operation or loses its ability to control PSUs 110 (e.g., a communication link between management controller 106 and PSUs 110 goes down). In some embodiments, such determination may be made by reading information communicated from management controller 106 indicative of its status (e.g., by communicating appropriate signals over the control bus indicated in FIG. 1 ). If a fault condition exists in the management controller 106 , operation may proceed again to step 202 . If no fault condition exists in management controller 106 , method 200 may proceed again to step 214 .
- FIG. 2 discloses a particular number of steps to be taken with respect to method 200
- method 200 may be executed with greater or fewer steps than those depicted in FIG. 2 .
- FIG. 2 discloses a certain order of steps to be taken with respect to method 200
- the steps comprising method 200 may be completed in any suitable order.
- Method 200 may be implemented using information handling system 102 or any other system operable to implement method 200 .
- method 200 may be implemented partially or fully in software and/or firmware embodied in computer-readable media.
- FIG. 3 illustrates a flow chart of an example method 300 for current sharing in a master fault mode of a power system, in accordance with embodiments of the present disclosure.
- method 300 may begin at step 302 .
- teachings of the present disclosure may be implemented in a variety of configurations of information handling system 102 . As such, the preferred initialization point for method 300 and the order of the steps comprising method 300 may depend on the implementation chosen.
- a fault may occur in a PSU 110 selected (e.g., by management controller 106 ) as master of the current share bus.
- Such fault condition may include a loss of input source or any other condition compromising the ability of the master PSU 110 to generate an output current.
- the master PSU 110 may set the current share bus drive variable DRIVE for the master PSU 110 to logic “0,” thus disabling the master PSU 110 from driving the voltage share bus. At such point, all active PSUs 110 may be current share slave PSUs 110 .
- the faulted master PSU 110 may ignore the monitored current I mon received by its master/slave gate 124 , and thus, its computation of voltage V share may effectively not be driven to the V share bus. Accordingly, remaining PSUs 110 may compete to determine a new master PSU 110 .
- the new master PSU 110 may determine if management controller 106 is able to control PSUs 110 (e.g., determine whether management controller 106 is in reset or not ready). Such determination may be made by reading information communicated from management controller 106 indicative of its status (e.g., by communicating appropriate signals over the control bus indicated in FIG. 1 ). If management controller 106 is able to control PSUs 110 , method 300 may proceed to step 312 . Otherwise, method 300 may proceed to step 310 .
- master PSU 110 may wait for a period of time (e.g., 100 milliseconds) and proceed again to step 308 .
- the faulted master PSU 110 may notify management controller 106 of the fault condition. Such notification may be made by communicating appropriate signals over the control bus indicated in FIG. 1 .
- management controller 106 may select a new master PSU 110 for the current share bus, and the number of active PSUs, and communicate a notification to each PSU 110 .
- management controller 106 may set the dedicated master variable DED_MASTER for the selected master to logic “1” and set the current share bus drive variable DRIVE for all active PSUs 110 to logic “0,” thus causing all active PSUs 110 other than the dedicated selected master PSU 110 to act as slave devices
- management controller 106 may determine if current share bus drive variable DRIVE is logic “0” on all slave PSUs 110 . If the current share bus drive variable DRIVE is logic “0” on all slave PSUs 110 , then method 300 may proceed to step 324 . Otherwise, method 300 may proceed to step 320 .
- the PSU 110 driving the highest voltage to the current share bus may become the master of the current share bus. Accordingly, at step 322 , all other PSUs 110 may act as slaves, and may attempt to “catch up” to the master by increasing their respective output currents. After completion of step 322 , method 300 may proceed again to step 318 .
- step 324 in response to current share bus drive variable DRIVE being logic “0” on all slave PSUs 110 , the selected master PSU 110 may drive a voltage V share on the current share bus based on an average current generated by the active PSUs 110 (e.g., the aggregate current I total divided by the number of active PSUs 110 ).
- the power system may return to normal operation (e.g., as in step 214 of method 200 ).
- FIG. 3 discloses a particular number of steps to be taken with respect to method 300
- method 300 may be executed with greater or fewer steps than those depicted in FIG. 3 .
- FIG. 3 discloses a certain order of steps to be taken with respect to method 300
- the steps comprising method 300 may be completed in any suitable order.
- Method 300 may be implemented using information handling system 102 or any other system operable to implement method 300 .
- method 300 may be implemented partially or fully in software and/or firmware embodied in computer-readable media.
- FIG. 4 illustrates a flow chart of an example method 400 for current sharing in a swap mode of a power system, in accordance with embodiments of the present disclosure.
- the swap mode may occur in response to a change in number of active PSUs, either due to a removal or an addition of a PSU 110 .
- method 400 may begin at step 402 .
- teachings of the present disclosure may be implemented in a variety of configurations of information handling system 102 . As such, the preferred initialization point for method 400 and the order of the steps comprising method 400 may depend on the implementation chosen.
- management controller 106 may set control variable settings of active PSUs 110 such that their respective dedicated master variables DED_MASTER are set to logic “0” and their respective current share bus drive variables DRIVE are set to logic “1.” With such default settings, each PSU 110 may drive or attempt to drive the current share bus and may attempt to become a master of the current share bus.
- the PSU 110 driving the highest voltage to the current share bus may become the master of the current share bus. Accordingly, at step 406 , all other PSUs 110 may act as slaves, and may attempt to “catch up” to the master by increasing their respective output currents.
- management controller 106 may select a PSU 110 to act as the master of the current share bus. Such selection may be made in any suitable manner (e.g., based on one or more parameters associated with PSUs 110 ) and mechanisms for making such selection are beyond the scope of this disclosure.
- management controller 106 may (e.g., by communicating appropriate signals over the control bus indicated in FIG. 1 ) set the dedicated master variable DED_MASTER for the selected master to logic “1” and set the current share bus drive variable DRIVE for all PSUs 110 other than the selected master (i.e., the slave PSUs 110 ) to logic “0.” Accordingly, at step 412 , only the selected master PSU 110 may drive the current share bus, and all other PSUs 110 will follow the voltage V share driven on the current share bus in generating their own output currents.
- FIG. 4 discloses a particular number of steps to be taken with respect to method 400
- method 400 may be executed with greater or fewer steps than those depicted in FIG. 4 .
- FIG. 4 discloses a certain order of steps to be taken with respect to method 400
- the steps comprising method 400 may be completed in any suitable order.
- Method 400 may be implemented using information handling system 102 or any other system operable to implement method 400 .
- method 400 may be implemented partially or fully in software and/or firmware embodied in computer-readable media.
- references in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Power Engineering (AREA)
- Direct Current Feeding And Distribution (AREA)
Abstract
Description
- The present disclosure relates in general to information handling systems, and more particularly to systems and methods for current sharing between power supply units in an information handling system.
- As the value and use of information continues to increase, individuals and businesses seek additional ways to process and store information. One option available to users is information handling systems. An information handling system generally processes, compiles, stores, and/or communicates information or data for business, personal, or other purposes thereby allowing users to take advantage of the value of the information. Because technology and information handling needs and requirements vary between different users or applications, information handling systems may also vary regarding what information is handled, how the information is handled, how much information is processed, stored, or communicated, and how quickly and efficiently the information may be processed, stored, or communicated. The variations in information handling systems allow for information handling systems to be general or configured for a specific user or specific use such as financial transaction processing, airline reservations, enterprise data storage, or global communications. In addition, information handling systems may include a variety of hardware and software components that may be configured to process, store, and communicate information and may include one or more computer systems, data storage systems, and networking systems.
- An information handling system may include one or more power supply units for providing electrical energy to components of the information handling system. Typically, a power supply unit is configured to operate from an input alternating current (AC) source of electrical energy, which the power supply unit converts to a direct current (DC) output. Thus, typically a power supply unit may include a rectifier and/or power factor correction stage to receive the input AC source and rectify the input AC waveform to charge a bulk capacitor to a desired voltage. A direct-current-to-direct-current (DC-DC) stage may convert the voltage on the bulk capacitor to a DC output voltage which may be used to power components of the information handling system.
- When two or more power supply units operate in parallel to meet power requirements of an information handling system, it is often desirable to maintain a current balance among the power supply units within acceptable tolerances to prevent one of such power supply units from taking up a disproportionate share of the current load, which could cause a power supply unit to reach over-current limits, over-voltage limits, oscillations on a power bus, and/or other negative effects.
- In accordance with the teachings of the present disclosure, the disadvantages and problems associated with existing approaches to current sharing among power supply units may be reduced or eliminated.
- In accordance with embodiments of the present disclosure, an information handling system may include a processor, a management controller communicatively coupled to the processor, and a plurality of power supply units communicatively coupled to the management controller for supplying electrical energy to one or more information handling resources of the information handling system via a power bus. Each of the plurality of power supply units may be configured to, when the management controller is able to control the plurality of power supply units: (i) receive an indication from the management controller whether such power supply unit is selected as a master of a current share bus; (ii) if such power supply unit is selected as the master, drive a current share signal on the current share bus, the current share signal indicative of an output current driven by such power supply unit on the power bus; and (iii) if such power supply unit is not selected as the master, monitor the current share signal and drive the output current to the power bus in accordance with the current share signal. Each of the plurality of power supply units may be also be configured to, when the management controller is unable to control the plurality of power supply units: (i) attempt to drive the current share signal on the current share bus; and (ii) monitor the current share signal and drive the output current to the power bus in accordance with the current share signal.
- In accordance with these and other embodiments of the present disclosure, a power supply unit may include a power train and a controller communicatively coupled to the power train and configured to receive an indication whether a management controller is able to control the power supply unit. When the indication indicates the management controller is able to control the power supply unit, the controller may further be configured to: (i) receive an indication from the management controller whether the power supply unit is selected as a master of a current share bus; (ii) if the power supply unit is selected as the master, drive a current share signal on the current share bus, the current share signal indicative of an output current driven by the power train on a power bus; and (iii) if the power supply unit is not selected as the master, monitor the current share signal and drive the output current to the power bus in accordance with the current share signal. When the indication indicates that the management controller is unable to control the power supply unit, the controller may further be configured to: (i) attempt to drive the current share signal on the current share bus; and (ii) monitor the current share signal and drive the output current to the power bus in accordance with the current share signal.
- In accordance with these and other embodiments of the present disclosure, a method may include determining whether a management controller is able to control a plurality of power supply units. The method may also include, when the management controller is able to control the plurality of power supply units: (i) selecting a power supply unit of the plurality of power supply units as a master of a current share bus; (ii) driving, by the power supply unit selected as the master, a current share signal on the current share bus, the current share signal indicative of an output current driven by the power supply unit selected as the master; and (iii) monitoring, by power supply units other than the power supply unit selected as the master, the current share signal and driving, by power supply units other than the power supply unit selected as the master, respective output currents to the power bus in accordance with the current share signal. The method may also include, when the management controller is unable to control the plurality of power supply units: (i) attempting, by each of the plurality of power supply units, to drive the current share signal on the current share bus; and (ii) monitoring, by each of the power supply units, the current share signal and driving, by each of the power supply units, the output current to the power bus in accordance with the current share signal.
- Technical advantages of the present disclosure may be readily apparent to one skilled in the art from the figures, description and claims included herein. The objects and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims.
- It is to be understood that both the foregoing general description and the following detailed description are examples and explanatory and are not restrictive of the claims set forth in this disclosure.
- A more complete understanding of the present embodiments and advantages thereof may be acquired by referring to the following description taken in conjunction with the accompanying drawings, in which like reference numbers indicate like features, and wherein:
-
FIGS. 1A-1C illustrates a block diagram of an example information handling system, in accordance with embodiments of the present disclosure; -
FIG. 2 illustrates a flow chart of an example method for current sharing in a normal mode of a power system, in accordance with embodiments of the present disclosure; -
FIG. 3 illustrates a flow chart of an example method for current sharing in a master fault mode of a power system, in accordance with embodiments of the present disclosure; and -
FIG. 4 illustrates a flow chart of an example method for current sharing in a swap mode of a power system, in accordance with embodiments of the present disclosure. - Preferred embodiments and their advantages are best understood by reference to
FIGS. 1A through 4 , wherein like numbers are used to indicate like and corresponding parts. - For the purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a personal data assistant (PDA), a consumer electronic device, a network storage device, or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include memory, one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the information handling system may include one or more storage devices, one or more communications ports for communicating with external devices as well as various input and output (I/O) devices, such as a keyboard, a mouse, and a video display. The information handling system may also include one or more buses operable to transmit communication between the various hardware components.
- For the purposes of this disclosure, computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or floppy disk), a sequential access storage device (e.g., a tape disk drive), compact disk, CD-ROM, DVD, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.
- For the purposes of this disclosure, information handling resources may broadly refer to any component system, device or apparatus of an information handling system, including without limitation processors, service processors, basic input/output systems (BIOSs), buses, memories, I/O devices and/or interfaces, storage resources, network interfaces, motherboards, power supplies, air movers (e.g., fans and blowers) and/or any other components and/or elements of an information handling system.
-
FIGS. 1A-1C (which may collectively be referred to herein as “FIG. 1 ”) illustrate a block diagram of an example of aninformation handling system 102. As depicted,information handling system 102 may include one or more power supply units (PSUs) 110, amotherboard 101, and one or more other information handling resources. - Motherboard 101 may include a circuit board configured to provide structural support for one or more information handling resources of
information handling system 102 and/or electrically couple one or more of such information handling resources to each other and/or to other electric or electronic components external toinformation handling system 102. As shown inFIG. 1 ,motherboard 101 may include aprocessor 103, amemory 104, amanagement controller 106, and one or more other information handling resources. -
Processor 103 may comprise any system, device, or apparatus operable to interpret and/or execute program instructions and/or process data, and may include, without limitation a microprocessor, microcontroller, digital signal processor (DSP), application specific integrated circuit (ASIC), or any other digital or analog circuitry configured to interpret and/or execute program instructions and/or process data. In some embodiments,processor 103 may interpret and/or execute program instructions and/or process data stored inmemory 104 and/or another component ofinformation handling system 102. -
Memory 104 may be communicatively coupled toprocessor 103 and may comprise any system, device, or apparatus operable to retain program instructions or data for a period of time.Memory 104 may comprise random access memory (RAM), electrically erasable programmable read-only memory (EEPROM), a PCMCIA card, flash memory, magnetic storage, opto-magnetic storage, or any suitable selection and/or array of volatile or non-volatile memory that retains data after power toinformation handling system 102 is turned off. In particular embodiments,memory 104 may comprise a non-volatile memory comprising one or more non-volatile dual-inline memory modules (NVDIMMs). -
Management controller 106 may be configured to provide out-of-band management facilities for management ofinformation handling system 102. Such management may be made bymanagement controller 106 even if a host system ofinformation handling system 102 is powered off or powered to a standby state.Management controller 106 may include a processor, memory, an out-of-band network interface separate from and physically isolated from an in-band network interface ofinformation handling system 102, and/or other embedded information handling resources. In certain embodiments,management controller 106 may include or may be an integral part of a baseboard management controller (BMC) or a remote access controller (e.g., a Dell Remote Access Controller or Integrated Dell Remote Access Controller). In other embodiments,management controller 106 may include or may be an integral part of a chassis management controller (CMC). In some embodiments,management controller 106 may be configured to communicate withPSUs 110 to control whichPSUs 110 are enabled to operate as a master (as opposed to a slave) of a current share bus and/or whichPSU 110 is set as a dedicated master of the current share bus, as described in greater detail below. - Generally speaking, a
PSU 110 may include any system, device, or apparatus configured to supply electrical current to one or more information handling resources ofinformation handling system 102. As shown inFIG. 1 , a PSU 110 may include acontroller 112 and apower train 114. Eachpower train 114 may be coupled at its outputs to a power bus configured to deliver electrical energy tomotherboard 101 and other components ofinformation handling system 102. -
Controller 112 may comprise a microprocessor, DSP, ASIC, FPGA, EEPROM, or any combination thereof, or any other device, system, or apparatus for controlling operation ofPSU 110. As such,controller 112 may comprise firmware, logic, and/or data for controlling functionality ofPSU 110. As shown inFIG. 1 ,controller 112 may couple to a current share bus (as labeled with “Vshare BUS” inFIG. 1 ) withPSUs 110 in order to establish a current share for the various currents delivered to the power bus byPSUs 110. As shown inFIG. 1 , eachcontroller 112 may comprise acurrent monitor 118, acurrent aggregator 120, aPSU location indicator 122, a master/slave gate 124, a current share busvoltage computation block 126, and a currentshare bus driver 128. - Each
current monitor 118 may comprise any suitable system, device, or apparatus for sensing a current delivered by apower train 114 of aPSU 110 to the power bus and generating a signal Imon indicative of such current. For example, in some embodiments, suchcurrent monitor 118 may include a resistor which generates a voltage indicative of the current, in accordance with Ohm's law. - Each
current aggregator 120 may comprise any suitable system, device, or apparatus for sensing an aggregate current delivered by allPSUs 110 ofinformation handling system 102 and generating a signal ITotal indicative of such aggregate current. For example, in some embodiments, suchcurrent aggregator 120 may include a resistor which generates a voltage indicative of the aggregate current, in accordance with Ohm's law. - A
PSU location indicator 122 may comprise any suitable system, device, or apparatus for determining, out of a plurality of multiple PSU bays ininformation handling system 102, in which PSU bay aPSU 110 is located. In some embodiments, such determination may be made based on information communicated from an Inter-Integrated Circuit (I2C) bus or other communications bus ofinformation handling system 102. - A master/
slave gate 124 may comprise any system, device, or apparatus configured to receive information regarding a voltage Vshare present on a current share bus, a monitored current Imon generated by apower train 114, an aggregate current ITotal generated byPSUs 110, a location of aPSU 110, and/or control variable settings ofPSU 110, and based on such received information, determine whether aPSU 110 is to drive a voltage on the current share bus. - Control variable settings may be set by
management controller 106 whenmanagement controller 106 is active (e.g., via a bus labeled as “CONTROL BUS” inFIG. 1 ), or in the event thatmanagement controller 106 is not active or experiences a fault, may be set to default values of such control variable settings. In some embodiments, such control settings may include a dedicated master variable DED_MASTER and a current share bus drive variable DRIVE. In such embodiments, a current share bus drive variable DRIVE of aPSU 110 controls whether aPSU 110 drives the current share bus and dedicated master variable DED_MASTER controls whether aPSU 110 is set bymanagement controller 106 to be a dedicated master of the current share bus. In some of such embodiments, dedicated master variable DED_MASTER may be implemented using a single bit (e.g., a value of logic “1” to set aPSU 110 to be the dedicated master of the current share bus and a value of logic “0” to indicate that thePSU 110 is not the dedicated master). In these and other embodiments, current share bus drive variable DRIVE may be implemented using a single bit (e.g., a value of logic “1” to causePSU 110 to drive the current share bus and a value of logic “0” to disable aPSU 110 from driving the current share bus). To further illustrate control of aPSU 110 by control variable settings, the following truth table is provided: -
DED_MASTER DRIVE EFFECT 0 0 PSU 110 acts as a slave with respect tocurrent share bus; controls power train 114 based on voltage read from current share bus 1 0 PSU 110 acts as a slave with respect tocurrent share bus; controls power train 114 based on voltage read from current share bus 0 1 PSU 110 drives current share bus andattempts to become master; if not master (e.g., if voltage driven to current share bus is not the highest of all voltages driven to current share bus), controls power train 114 based onvoltage read from current share bus 1 1 PSU 110 is dedicated master and drivescurrent share bus - Each current share bus
voltage computation block 126 may comprise any suitable system, device, or apparatus for computing, for aPSU 110 enabled to drive the current share bus (e.g., thosePSUs 110 with a current share bus drive variable DRIVE of logic “1”), a voltage to be driven by thePSU 110 on the current share bus. For example, in some embodiments, such computation may be based on the aggregate current ITotal and the number of active PSUs 110 (which may be estimated based on the aggregate current ITotal and the monitored current Imon for the particular PSU 110). A signal indicative of such voltage to be driven may be communicated by current share busvoltage computation block 126 to a currentshare bus driver 128 of thePSU 110. - Each current
share bus driver 128 may comprise any suitable system, device, or apparatus (e.g., electronic or electrical circuit) for driving a voltage on the current share bus based on a signal communicated to such currentshare bus driver 128 by its associated current share busvoltage computation block 126. In some embodiments, a currentshare bus driver 128 may include circuitry (e.g., an output diode), such that a currentshare bus driver 128 drives the current share bus only if such currentshare bus driver 128 is attempting to drive a voltage larger than that driven by the currentshare bus drivers 128 ofother PSUs 110. -
Power train 114 may include any suitable system, device, or apparatus for converting electrical energy received by PSU 110 (e.g., a 120-volt alternating current or 240-volt alternating current voltage waveform, a 48-volt DC or 240-volt DC or 380-volt DC direct current voltage waveform) from an input source into electrical energy usable to information handling resources of information handling system 102 (e.g., 12-volt direct current voltage source). In some embodiments,power train 114 may comprise a rectifier, a power factor correction circuit, and/or a direct-current-to-direct-current converter. In these and other embodiments,power train 114 may comprise a voltage regulator (e.g., a multi-phase voltage regulator). In some embodiments, one ormore PSUs 110 may share an input source. In operation, apower train 114 may deliver an amount of electrical current to the power bus in accordance with a control signal communicated fromcontroller 112 indicative of a desired amount of electrical current to be delivered. In some embodiments, such control signal may comprise the voltage Vshare present on the current share bus or a control signal indicative of the voltage Vshare present on the current share bus, such that thepower train 114 is controlled by the voltage Vshare present on the current share bus. - In addition to
motherboard 101,processor 103,memory 104,management controller 106, andPSUs 110,information handling system 102 may include one or more other information handling resources. For example, in some embodiments,information handling system 102 may include a number ofPSUs 110 other than three. -
FIG. 2 illustrates a flow chart of anexample method 200 for current sharing in a normal mode of a power system, in accordance with embodiments of the present disclosure. Such start-up mode may occur during an initial powering on of the powersystem comprising PSUs 110 during whichmanagement controller 106 may itself be initializing and not yet able to provide active control ofPSUs 110. According to some embodiments,method 200 may begin atstep 202. As noted above, teachings of the present disclosure may be implemented in a variety of configurations ofinformation handling system 102. As such, the preferred initialization point formethod 200 and the order of thesteps comprising method 200 may depend on the implementation chosen. - At
step 202, during start-up mode of the powersystem comprising PSUs 110 or if a fault exists inmanagement controller 106,management controller 106 may not be able to set control variable settings forPSUs 110 and accordingly, such control variable settings may assume default values. For example,PSUs 110 may assume default values such that their respective dedicated master variables DED_MASTER are set to logic “0” and their respective current share bus drive variables DRIVE are set to logic “1.” With such default settings, eachPSU 110 may drive or attempt to drive the current share bus and may attempt to become a master of the current share bus. - At
step 204, thePSU 110 driving the highest voltage to the current share bus may become the master of the current share bus. Accordingly, atstep 206, allother PSUs 110 may act as slaves, and may attempt to “catch up” to the master by increasing their respective output currents. - At
step 208,PSUs 110 may determine ifmanagement controller 106 has completed initialization such that it is able to controlPSUs 110. Such determination may be made by reading information communicated frommanagement controller 106 indicative of its status (e.g., by communicating appropriate signals over the control bus indicated inFIG. 1 ). Ifmanagement controller 106 is able to controlPSUs 110,method 200 may proceed to step 210. Otherwise,method 200 may proceed again to step 204. - At
step 210,management controller 106 may select aPSU 110 to act as the master of the current share bus. Such selection may be made in any suitable manner (e.g., based on one or more parameters associated with PSUs 110) and mechanisms for making such selection are beyond the scope of this disclosure. - At
step 212,management controller 106 may (e.g., by communicating appropriate signals over the control bus indicated inFIG. 1 ) set the dedicated master variable DED_MASTER for the selected master to logic “1” and set the current share bus drive variable DRIVE for allPSUs 110 other than the selected master (i.e., the slave PSUs 110) to logic “0.” Accordingly, atstep 214, only the selectedmaster PSU 110 may drive the current share bus, and allother PSUs 110 will follow the voltage Vshare driven on the current share bus in generating their own output currents. - At
step 216,management controller 106 may determine if a fault condition exists in themaster PSU 110. Such fault condition may include a loss of input source or any other condition compromising the ability of themaster PSU 110 to generate an output current. If a fault condition exists in themaster PSU 110, operation may proceed to a master fault mode, as described in greater detail below with respect tomethod 300. If no fault condition exists inmaster PSU 110,method 200 may proceed to step 218. - At
step 218, one ormore PSUs 110 may determine if a fault condition exists inmanagement controller 106. Such fault condition may include any condition in whichmanagement controller 106 ceases operation or loses its ability to control PSUs 110 (e.g., a communication link betweenmanagement controller 106 andPSUs 110 goes down). In some embodiments, such determination may be made by reading information communicated frommanagement controller 106 indicative of its status (e.g., by communicating appropriate signals over the control bus indicated inFIG. 1 ). If a fault condition exists in themanagement controller 106, operation may proceed again to step 202. If no fault condition exists inmanagement controller 106,method 200 may proceed again to step 214. - Although
FIG. 2 discloses a particular number of steps to be taken with respect tomethod 200,method 200 may be executed with greater or fewer steps than those depicted inFIG. 2 . In addition, althoughFIG. 2 discloses a certain order of steps to be taken with respect tomethod 200, thesteps comprising method 200 may be completed in any suitable order. -
Method 200 may be implemented usinginformation handling system 102 or any other system operable to implementmethod 200. In certain embodiments,method 200 may be implemented partially or fully in software and/or firmware embodied in computer-readable media. -
FIG. 3 illustrates a flow chart of anexample method 300 for current sharing in a master fault mode of a power system, in accordance with embodiments of the present disclosure. According to some embodiments,method 300 may begin atstep 302. As noted above, teachings of the present disclosure may be implemented in a variety of configurations ofinformation handling system 102. As such, the preferred initialization point formethod 300 and the order of thesteps comprising method 300 may depend on the implementation chosen. - At
step 302, a fault may occur in aPSU 110 selected (e.g., by management controller 106) as master of the current share bus. Such fault condition may include a loss of input source or any other condition compromising the ability of themaster PSU 110 to generate an output current. - At
step 304, in response to the fault in themaster PSU 110, themaster PSU 110 may set the current share bus drive variable DRIVE for themaster PSU 110 to logic “0,” thus disabling themaster PSU 110 from driving the voltage share bus. At such point, allactive PSUs 110 may be currentshare slave PSUs 110. - At
step 306, the faultedmaster PSU 110 may ignore the monitored current Imon received by its master/slave gate 124, and thus, its computation of voltage Vshare may effectively not be driven to the Vshare bus. Accordingly, remainingPSUs 110 may compete to determine anew master PSU 110. - At
step 308, thenew master PSU 110 may determine ifmanagement controller 106 is able to control PSUs 110 (e.g., determine whethermanagement controller 106 is in reset or not ready). Such determination may be made by reading information communicated frommanagement controller 106 indicative of its status (e.g., by communicating appropriate signals over the control bus indicated inFIG. 1 ). Ifmanagement controller 106 is able to controlPSUs 110,method 300 may proceed to step 312. Otherwise,method 300 may proceed to step 310. - At
step 310, in response to a determination thatmanagement controller 106 is unable to control PSUs 110 (e.g.,management controller 106 is in reset or is not ready),master PSU 110 may wait for a period of time (e.g., 100 milliseconds) and proceed again to step 308. - At
step 312, in response to a determination thatmanagement controller 106 is able to controlPSUs 110, the faultedmaster PSU 110 may notifymanagement controller 106 of the fault condition. Such notification may be made by communicating appropriate signals over the control bus indicated inFIG. 1 . - At
step 314, in response to the notification,management controller 106 may select anew master PSU 110 for the current share bus, and the number of active PSUs, and communicate a notification to eachPSU 110. - At
step 316,management controller 106 may set the dedicated master variable DED_MASTER for the selected master to logic “1” and set the current share bus drive variable DRIVE for allactive PSUs 110 to logic “0,” thus causing allactive PSUs 110 other than the dedicated selectedmaster PSU 110 to act as slave devices - At
step 318,management controller 106 may determine if current share bus drive variable DRIVE is logic “0” on allslave PSUs 110. If the current share bus drive variable DRIVE is logic “0” on allslave PSUs 110, thenmethod 300 may proceed to step 324. Otherwise,method 300 may proceed to step 320. - At
step 320, thePSU 110 driving the highest voltage to the current share bus may become the master of the current share bus. Accordingly, atstep 322, allother PSUs 110 may act as slaves, and may attempt to “catch up” to the master by increasing their respective output currents. After completion ofstep 322,method 300 may proceed again to step 318. - At
step 324, in response to current share bus drive variable DRIVE being logic “0” on allslave PSUs 110, the selectedmaster PSU 110 may drive a voltage Vshare on the current share bus based on an average current generated by the active PSUs 110 (e.g., the aggregate current Itotal divided by the number of active PSUs 110). After completion ofstep 324, the power system may return to normal operation (e.g., as instep 214 of method 200). - Although
FIG. 3 discloses a particular number of steps to be taken with respect tomethod 300,method 300 may be executed with greater or fewer steps than those depicted inFIG. 3 . In addition, althoughFIG. 3 discloses a certain order of steps to be taken with respect tomethod 300, thesteps comprising method 300 may be completed in any suitable order. -
Method 300 may be implemented usinginformation handling system 102 or any other system operable to implementmethod 300. In certain embodiments,method 300 may be implemented partially or fully in software and/or firmware embodied in computer-readable media. -
FIG. 4 illustrates a flow chart of anexample method 400 for current sharing in a swap mode of a power system, in accordance with embodiments of the present disclosure. The swap mode may occur in response to a change in number of active PSUs, either due to a removal or an addition of aPSU 110. According to some embodiments,method 400 may begin atstep 402. As noted above, teachings of the present disclosure may be implemented in a variety of configurations ofinformation handling system 102. As such, the preferred initialization point formethod 400 and the order of thesteps comprising method 400 may depend on the implementation chosen. - At
step 402, in response to a change in the number of active PSUs,management controller 106 may set control variable settings ofactive PSUs 110 such that their respective dedicated master variables DED_MASTER are set to logic “0” and their respective current share bus drive variables DRIVE are set to logic “1.” With such default settings, eachPSU 110 may drive or attempt to drive the current share bus and may attempt to become a master of the current share bus. - At
step 404, thePSU 110 driving the highest voltage to the current share bus may become the master of the current share bus. Accordingly, atstep 406, allother PSUs 110 may act as slaves, and may attempt to “catch up” to the master by increasing their respective output currents. - At
step 408, based on the updated inventory ofPSUs 110,management controller 106 may select aPSU 110 to act as the master of the current share bus. Such selection may be made in any suitable manner (e.g., based on one or more parameters associated with PSUs 110) and mechanisms for making such selection are beyond the scope of this disclosure. - At
step 410,management controller 106 may (e.g., by communicating appropriate signals over the control bus indicated inFIG. 1 ) set the dedicated master variable DED_MASTER for the selected master to logic “1” and set the current share bus drive variable DRIVE for allPSUs 110 other than the selected master (i.e., the slave PSUs 110) to logic “0.” Accordingly, atstep 412, only the selectedmaster PSU 110 may drive the current share bus, and allother PSUs 110 will follow the voltage Vshare driven on the current share bus in generating their own output currents. - Although
FIG. 4 discloses a particular number of steps to be taken with respect tomethod 400,method 400 may be executed with greater or fewer steps than those depicted inFIG. 4 . In addition, althoughFIG. 4 discloses a certain order of steps to be taken with respect tomethod 400, thesteps comprising method 400 may be completed in any suitable order. -
Method 400 may be implemented usinginformation handling system 102 or any other system operable to implementmethod 400. In certain embodiments,method 400 may be implemented partially or fully in software and/or firmware embodied in computer-readable media. - As used herein, when two or more elements are referred to as “coupled” to one another, such term indicates that such two or more elements are in electronic communication or mechanical communication, as applicable, whether connected indirectly or directly, with or without intervening elements.
- This disclosure encompasses all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Similarly, where appropriate, the appended claims encompass all changes, substitutions, variations, alterations, and modifications to the example embodiments herein that a person having ordinary skill in the art would comprehend. Moreover, reference in the appended claims to an apparatus or system or a component of an apparatus or system being adapted to, arranged to, capable of, configured to, enabled to, operable to, or operative to perform a particular function encompasses that apparatus, system, or component, whether or not it or that particular function is activated, turned on, or unlocked, as long as that apparatus, system, or component is so adapted, arranged, capable, configured, enabled, operable, or operative.
- All examples and conditional language recited herein are intended for pedagogical objects to aid the reader in understanding the disclosure and the concepts contributed by the inventor to furthering the art, and are construed as being without limitation to such specifically recited examples and conditions. Although embodiments of the present disclosure have been described in detail, it should be understood that various changes, substitutions, and alterations could be made hereto without departing from the spirit and scope of the disclosure.
Claims (30)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/014,766 US9733686B1 (en) | 2016-02-03 | 2016-02-03 | Systems and methods for management controller enhanced power supply unit current sharing |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US15/014,766 US9733686B1 (en) | 2016-02-03 | 2016-02-03 | Systems and methods for management controller enhanced power supply unit current sharing |
Publications (2)
Publication Number | Publication Date |
---|---|
US20170220089A1 true US20170220089A1 (en) | 2017-08-03 |
US9733686B1 US9733686B1 (en) | 2017-08-15 |
Family
ID=59386663
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US15/014,766 Active US9733686B1 (en) | 2016-02-03 | 2016-02-03 | Systems and methods for management controller enhanced power supply unit current sharing |
Country Status (1)
Country | Link |
---|---|
US (1) | US9733686B1 (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10082856B1 (en) * | 2016-09-29 | 2018-09-25 | Juniper Networks, Inc. | Performing a health check on power supply modules that operate in a current sharing mode |
US10948959B2 (en) * | 2018-10-31 | 2021-03-16 | Dell Products, L.P. | Method and apparatus to control power assist unit |
US11199894B2 (en) | 2018-10-30 | 2021-12-14 | Dell Products L.P. | Method and apparatus for providing high bandwidth capacitor circuit in power assist unit |
US20230068583A1 (en) * | 2021-07-20 | 2023-03-02 | Siliconch Systems Pvt Ltd | System and method for fault identification and fault handling in a multiport power sourcing device |
US20230136454A1 (en) * | 2021-11-04 | 2023-05-04 | Rockwell Automation Technologies, Inc. | Concurrent operation of input/output (io) modules in a duplex configuration |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6493243B1 (en) * | 1999-12-01 | 2002-12-10 | Acme Electric Corporation | Redundant power system and power supply therefor |
US7541793B2 (en) | 2005-06-07 | 2009-06-02 | Delta Electronics, Inc. | Parallel power supply with active droop current sharing circuit having current limiting function |
US8120203B2 (en) * | 2008-07-18 | 2012-02-21 | Intersil Americas Inc. | Intelligent management of current sharing group |
KR101023336B1 (en) | 2009-07-03 | 2011-03-18 | 삼성전기주식회사 | Load sharing device and parallel power supply therewith |
US8400795B2 (en) * | 2010-02-19 | 2013-03-19 | International Business Machines Corporation | Power sharing method and system for two-stage power supplies |
US8513831B2 (en) | 2010-09-21 | 2013-08-20 | Oracle International Corporation | Autonomous control in current share power supplies |
US9306417B2 (en) * | 2011-12-05 | 2016-04-05 | Utc Fire & Security Americas Corporation, Inc. | Load-sharing and boost voltage for notification appliance circuits |
US9312745B2 (en) * | 2012-12-08 | 2016-04-12 | Acbel Polytech Inc. | Universal power supply system |
US9401627B2 (en) * | 2014-10-09 | 2016-07-26 | Zippy Technology Corp. | Redundant power supply system providing alternate standby |
-
2016
- 2016-02-03 US US15/014,766 patent/US9733686B1/en active Active
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10082856B1 (en) * | 2016-09-29 | 2018-09-25 | Juniper Networks, Inc. | Performing a health check on power supply modules that operate in a current sharing mode |
US11199894B2 (en) | 2018-10-30 | 2021-12-14 | Dell Products L.P. | Method and apparatus for providing high bandwidth capacitor circuit in power assist unit |
US10948959B2 (en) * | 2018-10-31 | 2021-03-16 | Dell Products, L.P. | Method and apparatus to control power assist unit |
US20230068583A1 (en) * | 2021-07-20 | 2023-03-02 | Siliconch Systems Pvt Ltd | System and method for fault identification and fault handling in a multiport power sourcing device |
US11669399B2 (en) * | 2021-07-20 | 2023-06-06 | Siliconch Systems Pvt Ltd | System and method for fault identification and fault handling in a multiport power sourcing device |
US20230136454A1 (en) * | 2021-11-04 | 2023-05-04 | Rockwell Automation Technologies, Inc. | Concurrent operation of input/output (io) modules in a duplex configuration |
US11994962B2 (en) * | 2021-11-04 | 2024-05-28 | Rockwell Automation Technologies, Inc. | Concurrent operation of input/output (IO) modules in a duplex configuration |
Also Published As
Publication number | Publication date |
---|---|
US9733686B1 (en) | 2017-08-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9733686B1 (en) | Systems and methods for management controller enhanced power supply unit current sharing | |
US8006112B2 (en) | System and method for managing blades after a power supply unit failure | |
US20210208650A1 (en) | Systems and methods for graceful termination of applications in response to power event | |
US9735590B2 (en) | Systems and methods for hidden battery cell charging and conditioning | |
US9921629B2 (en) | Systems and methods for a multi-rail voltage regulator with configurable phase allocation | |
US9690349B2 (en) | Systems and methods for enhancing system hold up time using reverse charging of power supply unit | |
WO2017019361A1 (en) | Systems and methods for programmable system ride-through and hold-up | |
US10069309B2 (en) | Controlling redundant power supplies in an information handling system | |
US11594870B2 (en) | Systems and methods for extending fault timer to prevent overcurrent protection shutdown during powering on of information handling system | |
US11157060B2 (en) | Systems and methods for chassis-level persistent memory sequencing and safety | |
US9645634B2 (en) | Systems and methods for non-uniform power supply unit load sharing | |
US9852485B2 (en) | Systems and methods for power topology mapping | |
US9811140B2 (en) | Systems and methods for configurable power supply under-voltage setting | |
US11226665B2 (en) | Systems and methods for optimizing fault tolerant redundancy for an information handling system with multiple power supply units | |
US9612638B1 (en) | Systems and methods for automatic detection and configuration of voltage regulator phases in a multi-rail voltage regulator | |
US11422617B2 (en) | Systems and methods for providing peak current assistance to a voltage regulator using a switched capacitor converter | |
US9910476B2 (en) | Systems and methods for power supply current share auto-tuning | |
US10365705B2 (en) | System and methods for prioritized multi-node server and infrastructure availability during power capacity loss | |
US9703348B2 (en) | Systems and methods for virtual current sharing between a power supply unit and a battery back-up unit | |
US7190267B2 (en) | System and method for managing power control and data communication among devices | |
US11243590B2 (en) | Systems and methods for minimizing system hardware throttling due to power supply unit environmental effective capacity | |
US10560015B1 (en) | Systems and methods for optimizations and field configurations of power converters for a power supply unit | |
US20240126358A1 (en) | Low power management for erp6 compliance | |
US11726547B1 (en) | Information handling system power supply input voltage operation management systems and methods | |
CN112912819A (en) | Method and apparatus for providing high bandwidth capacitor circuit in power assist unit |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: DELL PRODUCTS L.P., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MATHEW, ABEY K.;GHARPURE, PADMANABH R.;BERKE, STUART ALLEN;SIGNING DATES FROM 20160202 TO 20160203;REEL/FRAME:037663/0272 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NORTH CAROLINA Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (ABL);ASSIGNORS:DELL PRODUCTS L.P.;DELL SOFTWARE INC.;WYSE TECHNOLOGY, L.L.C.;REEL/FRAME:038665/0001 Effective date: 20160511 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS FIRST LIEN COLLATERAL AGENT, TEXAS Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (NOTES);ASSIGNORS:DELL SOFTWARE INC.;WYSE TECHNOLOGY, L.L.C.;DELL PRODUCTS L.P.;REEL/FRAME:038664/0908 Effective date: 20160511 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (TERM LOAN);ASSIGNORS:DELL PRODUCTS L.P.;DELL SOFTWARE INC.;WYSE TECHNOLOGY, L.L.C.;REEL/FRAME:038665/0041 Effective date: 20160511 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (NOTES);ASSIGNORS:DELL SOFTWARE INC.;WYSE TECHNOLOGY, L.L.C.;DELL PRODUCTS L.P.;REEL/FRAME:038664/0908 Effective date: 20160511 Owner name: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT, NO Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (ABL);ASSIGNORS:DELL PRODUCTS L.P.;DELL SOFTWARE INC.;WYSE TECHNOLOGY, L.L.C.;REEL/FRAME:038665/0001 Effective date: 20160511 Owner name: BANK OF AMERICA, N.A., AS COLLATERAL AGENT, NORTH Free format text: SUPPLEMENT TO PATENT SECURITY AGREEMENT (TERM LOAN);ASSIGNORS:DELL PRODUCTS L.P.;DELL SOFTWARE INC.;WYSE TECHNOLOGY, L.L.C.;REEL/FRAME:038665/0041 Effective date: 20160511 |
|
AS | Assignment |
Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE OF REEL 038665 FRAME 0001 (ABL);ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040021/0348 Effective date: 20160907 Owner name: SECUREWORKS, CORP., GEORGIA Free format text: RELEASE OF REEL 038665 FRAME 0001 (ABL);ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040021/0348 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF REEL 038665 FRAME 0001 (ABL);ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040021/0348 Effective date: 20160907 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE OF REEL 038665 FRAME 0001 (ABL);ASSIGNOR:BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT;REEL/FRAME:040021/0348 Effective date: 20160907 |
|
AS | Assignment |
Owner name: SECUREWORKS, CORP., GEORGIA Free format text: RELEASE OF REEL 038664 FRAME 0908 (NOTE);ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040027/0390 Effective date: 20160907 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE OF REEL 038664 FRAME 0908 (NOTE);ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040027/0390 Effective date: 20160907 Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE OF REEL 038665 FRAME 0041 (TL);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040028/0375 Effective date: 20160907 Owner name: SECUREWORKS, CORP., GEORGIA Free format text: RELEASE OF REEL 038665 FRAME 0041 (TL);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040028/0375 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF REEL 038664 FRAME 0908 (NOTE);ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040027/0390 Effective date: 20160907 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE OF REEL 038664 FRAME 0908 (NOTE);ASSIGNOR:BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS COLLATERAL AGENT;REEL/FRAME:040027/0390 Effective date: 20160907 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE OF REEL 038665 FRAME 0041 (TL);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040028/0375 Effective date: 20160907 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF REEL 038665 FRAME 0041 (TL);ASSIGNOR:BANK OF AMERICA, N.A., AS COLLATERAL AGENT;REEL/FRAME:040028/0375 Effective date: 20160907 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLATERAL AGENT, NORTH CAROLINA Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT, TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, AS COLLAT Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040134/0001 Effective date: 20160907 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., A Free format text: SECURITY AGREEMENT;ASSIGNORS:ASAP SOFTWARE EXPRESS, INC.;AVENTAIL LLC;CREDANT TECHNOLOGIES, INC.;AND OTHERS;REEL/FRAME:040136/0001 Effective date: 20160907 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., T Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES, INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:049452/0223 Effective date: 20190320 |
|
AS | Assignment |
Owner name: THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., TEXAS Free format text: SECURITY AGREEMENT;ASSIGNORS:CREDANT TECHNOLOGIES INC.;DELL INTERNATIONAL L.L.C.;DELL MARKETING L.P.;AND OTHERS;REEL/FRAME:053546/0001 Effective date: 20200409 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
AS | Assignment |
Owner name: WYSE TECHNOLOGY L.L.C., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MOZY, INC., WASHINGTON Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: MAGINATICS LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: FORCE10 NETWORKS, INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC IP HOLDING COMPANY LLC, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: EMC CORPORATION, MASSACHUSETTS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SYSTEMS CORPORATION, TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL SOFTWARE INC., CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL MARKETING L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL INTERNATIONAL, L.L.C., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: CREDANT TECHNOLOGIES, INC., TEXAS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: AVENTAIL LLC, CALIFORNIA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 Owner name: ASAP SOFTWARE EXPRESS, INC., ILLINOIS Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH;REEL/FRAME:058216/0001 Effective date: 20211101 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (040136/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061324/0001 Effective date: 20220329 |
|
AS | Assignment |
Owner name: SCALEIO LLC, MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC IP HOLDING COMPANY LLC (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MOZY, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: EMC CORPORATION (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO MAGINATICS LLC), MASSACHUSETTS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO FORCE10 NETWORKS, INC. AND WYSE TECHNOLOGY L.L.C.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL PRODUCTS L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL INTERNATIONAL L.L.C., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL USA L.P., TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING L.P. (ON BEHALF OF ITSELF AND AS SUCCESSOR-IN-INTEREST TO CREDANT TECHNOLOGIES, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 Owner name: DELL MARKETING CORPORATION (SUCCESSOR-IN-INTEREST TO ASAP SOFTWARE EXPRESS, INC.), TEXAS Free format text: RELEASE OF SECURITY INTEREST IN PATENTS PREVIOUSLY RECORDED AT REEL/FRAME (045455/0001);ASSIGNOR:THE BANK OF NEW YORK MELLON TRUST COMPANY, N.A., AS NOTES COLLATERAL AGENT;REEL/FRAME:061753/0001 Effective date: 20220329 |