WO2006077569A1 - Rack level power management - Google Patents

Rack level power management Download PDF

Info

Publication number
WO2006077569A1
WO2006077569A1 PCT/IL2005/001135 IL2005001135W WO2006077569A1 WO 2006077569 A1 WO2006077569 A1 WO 2006077569A1 IL 2005001135 W IL2005001135 W IL 2005001135W WO 2006077569 A1 WO2006077569 A1 WO 2006077569A1
Authority
WO
WIPO (PCT)
Prior art keywords
power
modules
management module
module
managed
Prior art date
Application number
PCT/IL2005/001135
Other languages
French (fr)
Inventor
David Pincu
Roni Blaut
Alon Ferentz
Dror Korcharz
Yaniv Giat
Original Assignee
Powerdsine, Ltd.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Powerdsine, Ltd. filed Critical Powerdsine, Ltd.
Publication of WO2006077569A1 publication Critical patent/WO2006077569A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/26Power supply means, e.g. regulation thereof
    • HELECTRICITY
    • H02GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02JCIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J1/00Circuit arrangements for dc mains or dc distribution networks
    • H02J1/001Hot plugging or unplugging of load or power modules to or from power distribution networks
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/02Details
    • H04L12/10Current supply arrangements
    • HELECTRICITY
    • H02GENERATION; CONVERSION OR DISTRIBUTION OF ELECTRIC POWER
    • H02JCIRCUIT ARRANGEMENTS OR SYSTEMS FOR SUPPLYING OR DISTRIBUTING ELECTRIC POWER; SYSTEMS FOR STORING ELECTRIC ENERGY
    • H02J1/00Circuit arrangements for dc mains or dc distribution networks
    • H02J1/14Balancing the load in a network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00Packet switching elements
    • H04L49/40Constructional details, e.g. power supply, mechanical construction or backplane

Definitions

  • the present invention relates to the field of power management, and more particularly to a system providing rack level power management for a telecommunications rack utilizing a centralized DC power source.
  • Systems comprising multiple modules, such as telecommunication systems, are often rack mounted, in which a plurality of independent modules are secured to a common rack, which is typically 19" wide.
  • Each module in the rack is typically supplied with an on board power supply drawing power from a common AC mains.
  • the on board power supply of each unit thus functions to convert AC mains power to a local DC power at the appropriate voltage for the electronics in the module.
  • PoE Power over Ethernet
  • PD powered devices
  • PSE power sourcing equipment
  • PoE is a scalable technology, in which additional PDs with associated power requirements may be added by the user after an initial installation. The additional power requirements may grow to be in excess of the originally supplied power source.
  • PoE may be supplied either from a PSE associated with switch/hub equipment, known commercially as a PoE enabled switch, or from a midspan PSE module.
  • Midspan PSE modules may support one or more ports, with units of 1, 8, 12, 24 and 48 ports being commercially available. PoE enabled switches and midspan PSE modules are collectively denoted herein as PoE devices.
  • Chassis and blade telecommunication switch equipment has been designed to ensure maximum up-time.
  • the chassis comprises a housing for receiving and interconnecting by means of a backplane: blades; switch modules; management modules; power supplies; cooling fans; and other components. Chassis are expensive, however preferably are designed to provide redundancy and extremely high levels of service.
  • chassis typically supply some level of redundancy for power sources and management modules.
  • chassis are expensive, and limit the purchaser to the use of equipment compatible with the backplane of the chassis.
  • rack level equipment allows for the use of modules which are rack mounted and may be interconnected with standardized cabling.
  • the use of rack level equipment provides certain flexibility and the ability to avoid an initial high cost associated with the chassis.
  • the use of rack level equipment does not provide the levels of redundancy associated with chassis equipment.
  • U.S. Patent S/N 5,652,893 issued to Ben-Meir et al discloses a power management system for a local area network hub.
  • a power source also known as a power supply, is provided having one or more elements providing a maximum power available for the system.
  • Manageable modules are connected to the switching hub, each of the manageable modules having a memory providing information as to the power requirements of the module.
  • a controller module comprising a microprocessor calculates the power requirements of the system and enables or disables manageable modules in accordance with power availability.
  • the system only allows for two states for each module, enabled and disabled. Thus, a module may not be powered at a low or medium power state.
  • the embodiment of Ben-Meir is an example of chassis equipment.
  • a system having at least one power source, a management module and a plurality of power managed modules in communication with the management module.
  • Each of the power managed modules are arranged to be able to draw at least some power from the at least one power source.
  • Each of the power managed modules comprises a power manager operable to control the power drawn by the power managed module.
  • the management module allocates a power budget for each of the power managed modules, and the power managers of the power managed modules operate to control module operation so that power drawn is within the allocated budget.
  • Power managed modules may comprise PoE devices, switches, hubs, concentrators, computing equipment or other telecommunication modules operable at a plurality of power levels. Power managed modules may be supplied with an on board power supply, or preferably without an on board power supply. A central power source, preferably comprising at least one power supply, and further preferably comprising a plurality of power supplies, thus optimally supplies operating power for some or all of the power managed modules within the rack.
  • the management module allocates power for each of the power managed modules drawing power.
  • the power budget is dynamically allocated based on pre-defined criteria.
  • the management module directs each of the power managed modules to change their power consumption to a pre-assigned amount. In another embodiment, in the event of a failure of one or more power supplies, the management module directs each of the power managed modules to reduce their power consumption by a pre-assigned amount.
  • the power manager of at least one power managed module may sense a change in a voltage level from the at least one power source, and in response reduce power consumption. Such a response enables automatic power management by the power manager in the absence of communication from the management module.
  • the central power source comprises a plurality of power supplies, arranged in an N + M redundant arrangement.
  • the management module reserves the power of M redundant power supplies so as to provide the budgeted power in the absence of one or more failed power supplies.
  • the invention thus provides chassis functionality for distributed rack level equipment.
  • the system provides a plurality of buses, a first bus of which is used for ongoing communication of power requirements and budgets, and a second bus being used for emergency communication, such as in the event of a failure of at least one power supply of the central power source.
  • a plurality of scenarios are generated and pre-transmitted to the modules, preferably over the first bus.
  • one of the scenarios is implemented by broadcasting an implementing message, preferably over the second bus.
  • at least one of the first and second bus is arranged in a closed ring configuration, thus allowing for identifying a communication breakdown by monitoring a loop back path.
  • the invention provides for a system for rack level power management, the system comprising: at least one power source; a management module; and a plurality of power managed modules in communication with the management module and connected to draw power from the at least one power source, each of the plurality of power managed modules comprising a power manager and an operating circuit, the operating circuit being operable at a plurality of power drawing levels responsive to the power manager, the management module being operative to allocate a power budget to each of the plurality of power managed modules and communicate the allocated power budgets to the power managers, each of the power managers being operative to control the operating circuit of the power managed module to be operable at a power drawing level within the allocated budget.
  • the management module is connected to receive an indication of power availability from the at least one power source, the power budgets being allocated responsive the received indication.
  • the management module is operative to allocate power budgets on the basis of priority, each of the power managed modules being assigned a priority.
  • the plurality of power managed modules exhibits a minimum required power and an additional power level in excess of the minimum required power, the management module being operative to assign a power budget for the minimum required power for each of the plurality of power managed modules, and only in the event that additional power is available, to allocate a power budget for the additional power level of at least one of the plurality of power managed modules.
  • the power budget for the additional power level is allocated on a priority basis.
  • each of the plurality of power managers comprises a power meter, the power manager of each of the plurality of power managers receiving an indication of power drawn from the power meter.
  • at least one of the plurality of power managed modules is selected from the group consisting of power over a Ethernet enabled switch, a switch, a hub, a concentrator, a computing equipment, a power sourcing device, and a telecommunication module.
  • the operating circuit of at least one of the plurality of power managed modules comprises a power sourcing device operable for use with a power ready patch panel.
  • the at least one power source and the management module are comprised within a single equipment shelf.
  • the management module is further operative to input a total power available, the allocated power budgets being responsive to the input total available power.
  • the system further comprises at least one module not comprising a power manager, the management module being operative to reduce the power requirements of the at least one module from the input total available power.
  • the management module is further operative to transmit at least one power budget scenario, the management module being further operative to monitor a condition of the at least one power source, and in the event of a change in the monitored condition, to broadcast a command to the plurality of power managed modules, the plurality of power managed modules being operative to adhere to the at least one power budget scenario responsive to the broadcast command.
  • the system further comprises a first bus and a second bus, wherein the management module is operative to transmit the at least one power budget scenario via the first bus and to broadcast the command via the second bus.
  • at least one of the first bus and the second bus in arranged in a closed ring arrangement.
  • the system further comprises at least one communication bus arranged in a closed ring configuration, the management module being operative to communicate the allocated power budgets via the at least one communication bus.
  • the management module is further operative to monitor a loop back of the at least one communication bus, and in the event that the communicated allocated power budgets are not received via the monitored loop back, to communicate the allocated power budgets via the loop back.
  • the power manager of at least one the plurality of power managed modules is further operative to sense a reduced voltage, and responsive to sensed reduced voltage to control the operating circuit associated with the power manager to reduce power drawn.
  • the invention provides for a method of rack level power management comprising: providing at least one power source; providing a plurality of power managed modules connected to draw power from the at least one power source; allocating a power budget to each of the provided plurality of power managed modules; and transmitting the allocated power budgets to the plurality of power managed modules, each of the power managed modules controlling the drawn power to be within the transmitted allocated power budget.
  • the method further comprises receiving an indication of power availability from the at least one power source, the allocating being responsive the received indication.
  • the allocating is at least partially on the basis of priority.
  • the provided plurality of power managed modules exhibit a minimum required power and an additional power level in excess of the minimum required power, the stage of allocating comprising: allocating the minimum required power for each of the plurality of power managed modules, and in the event that additional power is available, allocating a power budget for the additional power level of at least one of the plurality of power managed modules. In one further embodiment the allocating a power budget for the additional power level is on a priority basis. [00026] In one embodiment the method further comprises for each of the plurality of provided power managed modules, receiving an indication of power drawn by the power managed module.
  • At least one of the provided plurality of power managed modules is selected from the group consisting of power over a Ethernet enabled switch, a switch, a hub, a concentrator, a computing equipment, a power sourcing device, and a telecommunication module.
  • at least one of the provided plurality of power managed modules comprises a power sourcing device operable for use with a power ready patch panel.
  • the method further comprises: inputting a total power available, the allocating a power budget being responsive to the input total available power. In one further embodiment the method comprises providing at least one module not receiving the transmitted allocated power budget; and deducting the power requirements of the at least one module from the input total available power. [00029] In one embodiment the method further comprises: monitoring a condition of the provided at least one power source; transmitting at least one power budget scenario to the provided plurality of power managed modules; and in the event of a change in the monitored condition, broadcasting a command to the plurality of power managed modules, the plurality of power managed modules adhering to the transmitted at least one power budget scenario responsive to the broadcast command.
  • the method further comprises: at least one of the provided plurality of power managed modules sensing a reduced voltage; and responsive to sensed reduced voltage, reducing power drawn by the provided power managed module. [00030] In one embodiment the method further comprises: monitoring a loop back of the transmitted allocated power budgets; and in the event that at least one of the transmitted allocated power budgets is not sensed by the monitoring, retransmitting the not sensed power budget via the loop back.
  • the method further comprises: monitoring a condition of the provided at least one power source; transmitting at least one power budget scenario to the provided plurality of power managed modules via first bus; and in the event of a change in the monitored condition, broadcasting a command to the plurality of power managed modules via a second bus different than the first bus, the plurality of power managed modules adhering to the at least one power budget scenario responsive to the broadcast command.
  • the invention provides for a system for rack level power management, the system comprising: at least one power source comprising a plurality of power supplies; a management module; and a plurality of power managed modules in communication with the management module and connected to draw power from the at least one power source, each of the plurality of power managed modules comprising a power manager and an operating circuit, the operating circuit being operable at a plurality of power drawing levels responsive to the power manager, the management module being operative to allocate a power budget to each of the plurality of power managed modules and communicate the allocated power budgets to the power managers, and being further operative to communicate a plurality of power scenarios and associated power budgets to the power managed modules, each of the power managers being operative to control the operating circuit of the power managed module to be operable at a power drawing level within the allocated budget, and in response to a communication from the management module to activate a scenario to control the operating circuit of the power managed module to be operable at a power drawing level within the power budget associated with the activated scenario.
  • FIG. 1 illustrates a high level view of rack mounted telecommunication equipment according to the teaching of the prior art
  • FIG. 2A illustrates a high level view of a first embodiment of rack mounted telecommunication equipment according the principle of the current invention
  • FIG. 2B illustrates a high level view of a second embodiment of rack mounted telecommunication equipment according the principle of the current invention
  • FIG. 3 illustrates a high level block diagram of an embodiment of a power managed module in accordance with the principle of the current invention
  • Fig. 4A illustrates a high level block diagram of an embodiment of a management module and a plurality of power supplies in communication with at least one power managed module in accordance with the principle of the current invention
  • Fig. 4B is a high level block diagram of an embodiment of the data connection of Fig. 4A exhibiting a first and second data bus in accordance with the principle of the current invention
  • Fig. 5 illustrates a high level flow chart of an embodiment of the operation of the management module to allocate power equally to all power managed modules in accordance with the principle of the current invention
  • Fig. 4A illustrates a high level block diagram of an embodiment of a management module and a plurality of power supplies in communication with at least one power managed module in accordance with the principle of the current invention
  • Fig. 4B is a high level block diagram of an embodiment of the data connection of Fig. 4A exhibiting a first and second data bus in accordance with the principle of the current invention
  • Fig. 5 illustrates a high level flow chart of an embodiment of the operation of
  • Fig. 6 illustrates a high level flow chart of an embodiment of the operation of the management module to allocate power according to priority to power managed modules in accordance with the principle of the current invention
  • Fig. 7 illustrates a high level flow chart of an embodiment of the operation of the management module to allocate a minimum power level to all power managed modules, and to allocate any additional available power according to priority in accordance with the principle of the current invention
  • Fig. 8 is a high level flow chart of an ongoing operation of the management module to maintain a potential scenario chart comprising power budgets for each power managed module according to an aspect of the invention
  • Fig. 9 is a high level flow chart of the operation of the management module, in accordance with the principle of the current invention, in the event of a change in power condition associated with one or more power supplies
  • Fig. 10 is a high level flow chart of the operation of a power manager to automatically detect a reduced power availability, and in response reduce power consumption in accordance with the principle of the current invention
  • Fig. 1 IA is a high level flow chart of the operation of the management module of Fig.
  • Fig. 1 IB is a high level flow chart of the operation of the management module of Fig. 4B to broadcast emergency messages via a main path of a second bus, and in the event of the broadcast message not being detected via a loop back path of the second bus, rebroadcasting the message via the loop back path of the second bus in accordance with the principle of the current invention; and [00049] Table I is a representation of an embodiment of the potential scenario chart produced as an outcome of the method of Fig. 8 in accordance with the principle of the invention. DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
  • the present embodiments enable a system for rack level power management having at least one power source, a management module and a plurality of power managed modules in communication with the management module.
  • Each of the power managed modules are arranged to be able to draw at least some power from the at least one power source.
  • Each of the power managed modules comprises a power manager operable to control the power drawn by the power managed module.
  • the management module allocates a power budget for each of the power managed modules, and the power managers of the power managed modules operate to control module operation so that power drawn is within the allocated budget.
  • Power managed modules may comprise PoE devices, switches, hubs, concentrators, computing equipment or other telecommunication modules operable at a plurality of power levels. Power managed modules may be supplied with an on board power supply, or preferably without an on board power supply. A central power source, preferably comprising at least one power supply, and further preferably comprising a plurality of power supplies, thus optimally supplies operating power for some or all of the power managed modules within the rack.
  • the management module allocates power for each of the power managed modules drawing power.
  • the power budget is dynamically allocated based on pre-defined criteria.
  • the management module directs each of the power managed modules to change their power consumption to a pre-assigned amount. In another embodiment, in the event of a failure of one or more power supplies, the management module directs each of the power managed modules to reduce their power consumption by a pre-assigned amount.
  • the power manager of at least one power managed module may sense a change in a voltage level from the at least one power source, and in response reduce power consumption. Such a response enables automatic power management by the power manager in the absence of communication from the management module.
  • the central power source comprises a plurality of power supplies, arranged in an N + M redundant arrangement.
  • the management module reserves the power of M redundant power supplies so as to provide the budgeted power in the absence of one or more failed power supplies.
  • the invention thus provides chassis functionality for distributed rack level equipment.
  • FIG. 1 illustrates a high level view of telecommunication equipment mounted in a rack 10 according to the teaching of the prior art.
  • Rack 10 comprises a plurality of switches 20, a plurality of patch panels 30, a modem 40, a power strip 50, and a connection to AC mains 60.
  • Each of the plurality of switches 20 and modem 40 comprises an independent on board power suppply (not shown), and thus exhibit a connection to power strip 50.
  • Patch panels 30 are unpowered, and function as interconnect points for connections to and from each of the switches 20 and user nodes (not shown).
  • a patch panel serves as a sort of static switchboard, using cables to interconnect nodes to a switch/server of the local area network.
  • a patch panel typically uses a jumper cable called a patch cord or a patch cable to create each interconnection typically between a switch port and a patch panel port representing a user node.
  • the patch cables are not shown for clarity.
  • a module such as one of switches 20 and modem 40, which is utilizing only a small amount of energy, such as when the module is off or in a standby mode, still consumes and wastes energy. Furthermore, a multiplicity of independent small power supplies is inefficient, as represented by the power supplies contained within each of switches 20 and modem 40, with the power supply in some modules outputting power at full capacity, while power supplies of other modules are at a low capacity.
  • Power supply longevity is at least partially a function of the utilization rate, in which typically a highly utilized power supply begins to exhibit an increased temperature. This increase in temperature leads to a shortened life for the power supply. Thus, certain modules in the rack may experience early failure due to power supply stress, while neighboring modules may be operating at low utilization rates.
  • FIG. 2A illustrates a high level view of a first embodiment of rack mounted telecommunication equipment according the principle of the current invention, comprising a rack 10 securing a plurality of power supplies 100, a management module 110, a power sourcing device 120, a power ready patch panel 130, a power managed module 140, a plurality of switches 150, a patch panel 30, a power strip 50 and a connection to AC mains 60.
  • the plurality of power supplies 100 are shown contained within a single shelf 160 of rack 10 as a single power source, shelf 160 further comprising management module 110.
  • Power managed module 140 may comprise a switch, hub equipment, modem, midspan PSE, computing equipment or gateway without exceeding the scope of the invention.
  • shelf 160 is no more than IU high, and is designed with a backplane such that each of the plurality of power supplies 100 may be hot swappable.
  • the backplane is further designed such that a power supply 100 may not be plugged into the slot intended to receive management module 110 and management module 110 may not be plugged into any slot intended to receive a power supply 100.
  • the plurality of power supplies 100 each exhibit a connection to power strip 50, however in contrast to the prior art configuration of Fig. 1, other modules do not exhibit a connection to power strip 50. Shelf 160 exhibits connections to power sourcing device 120, power managed module 140 and switches 150, with the connection supplying both power from the plurality of power supplies 100 and data communication with management module 110.
  • Power sourcing device 120, power managed module 140 and switches 150 are shown as not comprising an on board AC/ DC power supply, as indicated by the lack of connection to power strip 50, however this is not meant to be limiting in any way. Any one or more of power sourcing device 120, power managed module 140 and switches 150 may comprise an on board AC/DC power supply, with power supplies 100 supplying either additional or redundant power without exceeding the scope of the invention.
  • power supplies 100 are connected in a power sharing arrangement, and management module 110 is arranged to receive an indication of power output from each of power supplies 100.
  • power supplies 100 are arranged as single power source in an N + M redundant arrangement, with M power supplies 100 acting as redundant sources for N operating power supplies 100.
  • each of power supplies 100 supply an indication of power output, and in another embodiment a separate current indicator, and preferably a voltage meter, is supplied.
  • Management module 110 is in communication with each of the modules drawing power from power supplies 100, such as power sourcing device 120, power managed module 140 and switches 150, and obtains an indication of the power requirements from each of the modules.
  • Power is allocated to each of the modules according to pre-defined criteria, and the modules are operative to draw power in accordance with the allocation. In one embodiment power is allocated equally to all of the modules, in another embodiment power is allocated in accordance with priority and in another embodiment power is allocated at a minimum operating level to all modules and additional power is allocated in accordance with priority. [00062] Fig.
  • FIG. 2B illustrates a high level view of a second embodiment of rack mounted telecommunication equipment according the principle of the current invention comprising a rack 10 securing a first power shelf 210 comprising a plurality of power supplies 100 and a management module 110; a second power shelf 220 comprising a plurality of power supplies 100 and a redundant management module 110; a power sourcing device 120; a power ready patch panel 130; a power managed module 140; a switch 150; a switch having an on board power supply 200; a patch panel 30; a power strip 50; and a connection to AC mains 60.
  • Power managed module 140 may comprise a switch, hub equipment, modem, midspan PSE, computing equipment or gateway without exceeding the scope of the invention.
  • each of first power shelf 210 and second power shelf 220 is no more than IU high, and is designed with a backplane such that each of the plurality of power supplies 100 may be hot swappable.
  • Each of first power shelf 210 and second power shelf 220 thus functions as a power source comprising a plurality of power supplies 100.
  • first power shelf 210 and second power shelf 220 are arranged to function as a single power source.
  • the backplane is further designed such that a power supply 100 may not be plugged into the slot intended to receive management module 110 and management module 110 may not be plugged into any slot intended to receive a power supply 100.
  • the plurality of power supplies 100 each exhibit a connection to power strip 50, however in contrast to the prior art configuration of Fig. 1, other modules, with the exception of switch having on board power supply 200, do not exhibit a connection to power strip 50.
  • First power shelf 210 and second power shelf 220 exhibit connections to power sourcing device 120, power managed module 140, switch 150 and switch having on board power supply 200, with the connection supplying both power from the plurality of power supplies 100 and data communication with management modules 110.
  • Power sourcing device 120, power managed module 140 and switches 150 are shown as not comprising an on board power supply, as indicated by the lack of connection to power strip 50, however this is not meant to be limiting in any way.
  • power sourcing device 120, power managed module 140 and switches 150 may comprise an on board power supply, with power supplies 100 supplying either additional or redundant power without exceeding the scope of the invention.
  • power supplies 100 are connected in a power sharing arrangement, and management module 110 is arranged to receive an indication of power output from each of power supplies 100.
  • power supplies 100 are arranged as single power source in an N + M redundant arrangement, with M power supplies 100 acting as redundant sources for N operating power supplies 100.
  • First power shelf 210 acts as a first power source and second power shelf 220 acts as a second power source.
  • first power shelf 210 and second power shelf 220 are arranged to act a single unified power source.
  • each of power supplies 100 supply an indication of power output, and in another embodiment a separate current indicator, and preferably a voltage meter, is supplied.
  • Management module 110 of first power shelf 210 and management module 110 of second power shelf 220 act as redundant management modules, with a first one of the management modules 110 acting as an active module and a second one of the management modules 110 acting as a redundant module.
  • the active management module 110 is in communication with each of the modules drawing power from power supplies 100, such as power sourcing device 120, power managed module 140, switch 150 and switch having on board power supply 200, and obtains an indication of the power requirements from each of the modules. Power is allocated to each of the modules according to pre-defined criteria, and the modules are operative to draw power in accordance with the allocation.
  • Fig. 3 illustrates a high level block diagram of an embodiment of a power managed module 140 in accordance with the principle of the current invention.
  • Power managed module 140 comprises a hot swap controller 305, a DC/DC converter 300, a power meter 310, a power manager 320 and an operating circuit 330.
  • Hot swap controller is arranged to allow for hot swapping of power managed module 140.
  • DC/DC converter 300 is arranged to receive DC operating power from the plurality of power supplies 100 of Figs. 2A, 2B via hot swap controller 305.
  • the output of DC/DC converter 300 is passed through power meter 310 to operating circuit 330.
  • Power manager 320 is arranged to be in communication with management module 110, to receive an indication of power drawn by operating circuit 330 from power meter 310 and to communicate with operating circuit 330.
  • the output of DC/DC converter 300 is an intermediate operating voltage, typically on the order of 5 - 12 volts
  • operating circuit 330 comprises at least one point of load converter (not shown) operable to convert the intermediate operating voltage to the appropriate voltage as required by operating circuit 330.
  • the at least one point of load converter communicate with a CPU via an I 2 C bus and supply power at the required voltage on demand.
  • power manager 320 receives data indicative of a power allocation for power managed module 140 from management module 110.
  • Power manager 320 responsive to the received power allocation, monitors power drawn by operating circuit 330 via power meter 310.
  • power meter 310 further embodies a power limiter, and power manager 320 is operative to limit power drawn by operating circuit 330 by controlling the power limiting functionality of power meter 310.
  • power manager 320 is operative to communicate with operating circuit 330 to reduce the power drawn to be within the budget.
  • operating circuit 330 comprises computing equipment, and power drawn is reduced by lowering the speed of operation, preferably by reducing the voltage supplied by the point of load converter.
  • operating circuit 330 comprises a plurality of PoE PSEs each PSE supplying power through an output port to a PD via communication cabling, and power is disabled from at least one PD thereby reducing power drawn.
  • operating circuit 330 comprises a power sourcing device operable to supply power to a plurality of PDs via a power ready patch panel as described further in co-filed patent application entitled "System for Providing Power over Ethernet through a Patch Panel" the entire contents of which are incorporated herein by reference.
  • power manager 320 is operative to communicate with operating circuit 330 indicating the available additional power.
  • operating circuit 330 comprises computing equipment, and power drawn is increased by increasing the speed of operation, thereby improving performance.
  • operating circuit 330 comprises at least one PoE PSE, and power is enabled for at least one PSE having connected thereto a PD thereby increasing power drawn.
  • Power manager 320 preferably takes into account any losses associated with hot swap controller 305, DC/DC converter 300 and power meter 310.
  • power drawn by power manager 320 is tapped after power meter 310 (not shown), and is thus included within the power drawn indicated by power meter 310.
  • power drawn by power manager 320 is a pre-determined quantity, and the pre-determined quantity is reduced from the power allocation received.
  • the power allocation received is net of power losses associated with hot swap controller 305, DC/DC converter 300, power meter 310 and power drawn by power manager 320.
  • Fig. 4A illustrates a high level block diagram of an embodiment of a system 400 comprising management module and a plurality of power sources in communication with at least one power managed module in accordance with the principle of the current invention.
  • System 400 comprises a plurality of power supplies 100 each exhibiting a status indicator signal 405, and a current indicator 410; a management module 110; a PoE device 420; a switch having on board power supply 200; and a PoE enabled switch 450.
  • PoE device 420 comprises a hot swap controller 305, a power meter 310, a power manager 320, and an operating circuit 460 comprising a plurality of PoE managing circuits 470.
  • Switch having on board power supply 200 comprises hot swap controller 305, a DC/DC converter 300, an AC/DC converter 440, a connection to AC mains 60, a power meter 310, a power manager 320, and an operating circuit 330.
  • PoE enabled switch 450 comprises a first and second hot swap controller 305, a DC/DC converter 300, a first and second power meter 310, a first and second power manager 320, an operating circuit 330 and an operating circuit 460 comprising a plurality of PoE managing circuits 470.
  • each PoE managing circuit 470 is attached to a number of ports, and some or all of the ports have attached thereto over twisted pair communication cabling a PD.
  • Operating circuit 460 is shown as being a separate unit from power manager 320, however this is not meant to be limiting in any way. Power manager 320 may be incorporated into one or more of PoE managing circuit 470 without exceeding the scope of the invention. Power meter 310 is shown as being separate from power manager 320, however this is not meant to be limiting in any way, and power meter 310 may be integrated within power manager 320 without exceeding the scope of the invention.
  • the plurality of power supplies 100 are connected together in a power sharing arrangement, such as droop or active current sharing, illustrated herein as a common shared bus, and each of PoE device 420; switch having on board power supply 200; and PoE enabled switch 450 exhibits a connection to the common shared bus via a respective hot swap controller 305.
  • a majority of power drawn is intended for PoE applications, and thus power supplies 100 are isolated from non-PoE operating circuit 330 and the chassis.
  • DC/DC converter 300 receives power from the common shared bus via the respective hot swap controller 305, and operates to isolate and convert the power to the appropriate voltage for use with respective operating circuit 330 in accordance with isolation requirements of IEEE 802.3af.
  • a power meter 310 and a power manager 320 is respectively associated with each respective operating circuit 330, 460 and a respective power meter 310.
  • the respective power manger 320 is arranged to receive an input from the respective power meter 310, to be in communication with management module 110, and to be in communication with the respective operating circuit 330, 460.
  • the respective power meter 310 is arranged to provide the respective power manager 320 an indication of power drawn by respective operating circuit 330, 460.
  • Switch having on board power supply 200 exhibits AC/DC converter
  • each status indicator 405 comprises information regarding at least one of a power good signal of the respective power supply 100, a temperature of the respective power supply 100 and a stress level of the respective power supply 100.
  • Status indicator 405 is illustrated as a separate data connection from each power supply 100, however this is not meant to be limiting in any way.
  • the data connection is replaced with external sensors, and in another embodiment the data connection is part of a data bus arrangement.
  • Each current indicator 410 from respective power supply 100 is illustrated as a separate data connection from each power supply 100, however this is not meant to be limiting in any way.
  • the data connection is replaced with external sensors, and in another embodiment the data connection is part of a data bus arrangement.
  • a data connection is exhibited between management module 110 and each power manager 320.
  • the data connection between management module 110 and each power manger 320 is accomplished in a high speed data bus, such as an EIA 485 as defined by the Electronic Industry Alliance of Arlington, Virginia. EIA 485 is also known as RS 485.
  • the data connection between management module 110 and each power manager 320 comprises a pair of data busses: a first data bus being of a high speed, such as 1 Mbps, and carrying ongoing messages as will be described further hereinto below; and a second data bus being of a lower speed, such as 100 Kbps, and carrying emergency messages and addressing information as will be described further hereinto below.
  • the second data bus is hereinto referred to as the emergency bus.
  • management module 110 observes the bus to ensure that messages sent by management module 110 have traveled the entire bus. In the event of a sensed communication failure, messages are optionally resent in the reverse direction thereby improving communication reliability.
  • the plurality of power supplies 100 operate in a power sharing arrangement to supply power to each of PoE device 420; switch having on board power supply 200; and PoE enabled switch 450.
  • Status indicators 405 output status information regarding respective power supplies 100, and are received by management module 110.
  • Current indicators 410 output information regarding the output current of respective power supplies 100, and are received by management module 110.
  • Management module 110 is further operable to communicate with each power manger 320 of PoE device 420, switch having on board power supply 200 and PoE enabled switch 450 so as to communicate data regarding the priority and to allocate respective power budgets. In one embodiment management module 110 further receives data regarding the priority level of each port to which a PD requesting power may be attached.
  • Advantageously management module 110 thus has available an overall map of all connected PoE devices, modules and their priorities, enabling power to be allocated according to priority irrespective of the PoE managing circuit 470 to which a port is connected.
  • PoE managing circuits 470 operate under control of the respective power manager 320 to interrogate, optionally classify, and subsequently power connected PDs.
  • Management module 110 is operative in a manner that will be explained further hereinto below, to maintain a table of power scenarios indicative of potential states of the various status indicators 405.
  • management module 110 responsive to the change in the respective status indicator 405 is operable to look up the appropriate actions in the pre-stored power scenario table, and broadcast a scenario number to each power manager 320.
  • the use of a look up table and pre-transmitted scenarios enables management module 110 and power managers 320 to react in sufficient time so as to reduce consumption thereby limiting the amount of time for which an overload condition may be present.
  • Each power manager 320 is preferably operable to receive a power budget from management module 110 and to control the operation of the respective operating circuit 330, 460 in accordance with the received budget.
  • power manager 320 functions as a local power budget supervisor.
  • the priority is set by a user utilizing a host computer or controller communicating with management module 110.
  • priority may be set by a user for each PoE port powered by a PoE managing circuit 470, management module 110 communicating the received priority setting to PoE managing circuit 470 via the respective power manger 320.
  • At least one operating circuit 460 supplies power to PDs via a power ready patch panel and the PoE managing circuit 470 receives configuration information, including a priority level, from the power ready patch panel.
  • PoE managing circuit 470 receiving priority laden information from the power ready patch panel shares the priority information with management module 110 via respective power manager 320.
  • Switch having on board power supply 200 receives power from an AC mains via AC mains connection 60.
  • additional power may be drawn from the plurality of power supplies 100.
  • Total power drawn is monitored by power manager 320 of switch having on board power supply 200, and in the event that additional power has been allocated by management module 110, allows operating circuit 330 to increase power drawn in excess of power available from AC/DC converter 440.
  • power may be drawn by operating circuit 330 in the absence of AC mains power.
  • Fig. 4B is a high level block diagram of an embodiment of the data connection of Fig. 4A exhibiting a first and second data bus in accordance with the principle of the current invention comprising: a management module 110; a first and second PoE device 420; a power managed module 140; a first bus 520; and a second bus 530.
  • Management module 110 comprises a control circuit 500, a first transceiver 510, a second transceiver 512, a third transceiver 514, and a fourth transceiver 516.
  • Each of first and second PoE devices 420 comprises a first transceiver 518, a second transceiver 519 and a power manager 320.
  • Power managed module 140 comprises a first transceiver 518, a second transceiver 519 and a power manager 320.
  • Control 500 is connected to the input of the transmitter of each of first, second, third and fourth transceiver 510, 512, 514, 516 of management module 110 and to the output of the receiver of each of first, second, third and fourth transceiver 510, 512, 514, 516 of management module 110.
  • the output of the transmitter of first transceiver 510 of management module 110 is connected to the receiver of first transceiver 510 of management module 110 and by a portion of first bus 520 to both the output of the transmitter of first transceiver 518 of first PoE device 420 and the input of the receiver of first transceiver 518 of first PoE device 420.
  • the output of the transmitter of second transceiver 512 of management module 110 is connected to the receiver of second transceiver 512 of management module 110 and by a portion of second bus 530 to both the output of the transmitter of second transceiver 519 of first PoE device 420 and the input of the receiver of second transceiver 519 of first PoE device 420.
  • Power manager 320 of first PoE device 420 is connected to the output of the receiver of first transceiver 518 of first PoE device 420, to the input of the transmitter of first transceiver 518 of first PoE device 420, to the output of the receiver of second transceiver 519 of first PoE device 420, and to the input of the transmitter of second transceiver 519 of first PoE device 420.
  • the output of the transmitter of first transceiver 518 of first PoE device 420 is connected by a portion of first bus 520 to both the output of the transmitter of first transceiver 518 of second PoE device 420 and the input of the receiver of first transceiver 518 of second PoE device 420.
  • the output of the transmitter of second transceiver 519 of first PoE device 420 is connected by a portion of second bus 530 to both the output of the transmitter of second transceiver 519 of second PoE device 420 and the input of the receiver of second transceiver 519 of second PoE device 420.
  • Power manager 320 of second PoE device 420 is connected to the output of the receiver of first transceiver 518 of second PoE device 420, to the input of the transmitter of first transceiver 518 of second PoE device 420, to the output of the receiver of second transceiver 519 of second PoE device 420, and to the input of the transmitter of second transceiver 519 of second PoE device 420.
  • the output of the transmitter of first transceiver 518 of second PoE device 420 is connected by a portion of first bus 520 to both the output of the transmitter of first transceiver 518 of power managed module 140, and the input of the receiver of first transceiver 518 of power managed module 140.
  • the output of the transmitter of second transceiver 519 of second PoE device 420 is connected by a portion of second bus 530 to both the output of the transmitter of second transceiver 519 of power managed module 140 and the input of the receiver of second transceiver 519 of power managed module 140.
  • Power manager 320 of power managed module 140 is connected to the output of the receiver of first transceiver 518 of power managed module 140, to the input of the transmitter of first transceiver 518 of power managed module 140, to the output of the receiver of second transceiver 519 of power managed module 140, and to the input of the transmitter of second transceiver 519 of power managed module 140.
  • the output of the transmitter of first transceiver 518 of power managed module 140 is connected by a portion of first bus 520 to both the output of the transmitter of third transceiver 514 of management module 110 and the input of the receiver of third transceiver 514 of management module 110.
  • the output of the transmitter of second transceiver 519 of power managed module 140 is connected by a portion of second bus 530 to both the output of the transmitter of fourth transceiver 516 of management module 110 and the input of the receiver of fourth transceiver 516 of management module 110.
  • each of transceivers 510, 512, 514, 516, 518, 519 operate according to EIA-485, and in a preferred embodiment first and second transceiver 510, 512 operate as the master for first and second buses 520, 530 respectively.
  • first bus 520 and second bus 530 are connected in a daisy chain or ring arrangement, exhibiting internal direct connections in each of first, and second PoE devices 420 and power managed module 140, and first bus 520 and second bus 530 loop back to management module 110.
  • first bus 520 and second bus 530 are operational irrespective of the operation of each of first and second PoE devices 420 and power managed module 140.
  • Control 500 is operational to communicate ongoing messages to and from each of first and second PoE devices 420 and power managed module 140 via first transceiver 510 and first bus 520, and to further receive the transmitted messages via third transceiver 514 and the loop back path of first bus 520.
  • Control 500 is further operational to communicate emergency messages to each of first and second PoE devices 420 and power managed module 140 via second transceiver 512 of management module 110 and second bus 530, and to further receive the transmitted emergency messages via fourth transceiver 516 of management module 110 and the loop back path of second bus 530. [00085]
  • control 500 monitors the loop back path of first bus
  • control 500 is operational to notify a user of a communication break.
  • Control 500 is further operational to retransmit messages not received at third transceiver 514 of management module 110 via third transceiver 514 of management module 110 via the loop back path.
  • third transceiver 514 of management module 110 acts as a master for the portion of first bus 520 still connected to third transceiver 514 of management module 110 via the loop back path and first transceiver 510 of management module 110 acts as a master for the portion of first bus 520 connected to first transceiver 510 of management module 110, also called hereinafter the main path.
  • first and second PoE devices 420 and power managed module 140 are in communication with management module 110 despite a break in first bus 520.
  • control 500 further polls each of first and second PoE devices 420 and power managed module 140 via each of the main and loop back paths of first bus 520, and reports to a user an identifier of which PoE device 420 and power managed module 140 remain connected to each of the main and loop back paths of first bus 520.
  • control 500 monitors the loop back path of second bus 530, and in the event that messages transmitted by control 500 via second transceiver 512 of management module 110 are not received at fourth transceiver 516 of management module 110, control 500 is operational to notify a user of a communication break.
  • Control 500 is further operational to retransmit messages not received at fourth transceiver 516 of management module 110 via fourth transceiver 516 of management module 110 via the loop back path.
  • fourth transceiver 516 of management module 110 acts as a master for the portion of second bus 530 still connected to fourth transceiver 516 of management module 110 via the loop back path
  • second transceiver 512 of management module 110 acts as a master for the portion of second bus 530 connected to second transceiver 512 of management module 110, also called hereinafter the main path.
  • first and second PoE devices 420 and power managed module 140 are in communication with management module 110 despite a break in second bus 530.
  • control 500 further polls each of first and second PoE device 420 and power managed module 420 via each of the main and loop back paths of second bus 530, and reports to a user an identifier of which PoE device 420 and power managed module 140 remain connected to each of the main and loop back paths of second bus 530.
  • second bus 530 is held open to be available for time sensitive messages to be sent by control 500, and no time is lost by control 500 regaining control of second bus 530 due to communication from one of first and second PoE devices 420 and power managed module 140.
  • Fig. HA is a high level flow chart of the operation of management module 110 of Fig.
  • stage 5000 a message is transmitted via the main path of the first bus to a destination address, for example by utilizing first transceiver 510 of management module 110.
  • Management module 110 preferably acts as the bus master and assigns addresses to each of first and second PoE devices 420, power managed module 140 and other devices found attached thereto.
  • control 500 monitors the loop back path of first bus 520, for example via third transceiver 514 of management module 110.
  • first and second PoE devices 420, power managed module 140, and other devices which remain connected to management module 110 via the loop back path of first bus 520, receive communication irrespective of the break in first bus 520.
  • management module 110 notifies a user of the communication break.
  • identifiers of units identified in optional stages 5040, 5050 are further communicated to the user, thus indicating further information as to the location of the break.
  • the routine returns.
  • Fig. HB is a high level flow chart of the operation of management module 110 of Fig. 4B to broadcast emergency messages via a main path of second bus 530, and in the event of the broadcast message not being detected via the loop back path of second bus 530, rebroadcasting the message via the loop back path of second bus 530 in accordance with the principle of the current invention.
  • an emergency message is broadcast via the main path of the second bus to a destination address, for example by utilizing second transceiver 512 of management module 110.
  • Management module 110 preferably acts as the bus master and assigns addresses to each of firs and second PoE devices 420, power managed module 140 and or other devices found attached thereto.
  • control 500 monitors the loop back path of second bus
  • stage 6010 the emergency message broadcast in stage 6000 is not received via the loop back path, indicating that the communication ring of second bus 530 is not intact
  • stage 6030 the emergency message of stage 6000 is rebroadcast via the loop back path of second bus 530, for example by utilizing fourth transceiver 516 of management module 110.
  • first and second PoE devices 420, power managed module 140, and other devices which remain connected to management module 110 via the loop back path of second bus 530 receive emergency broadcast messages irrespective of the break in second bus 530.
  • devices are polled via the main path of second bus 530, and units responding are identified as connected via the main path to management module 110.
  • devices are polled via the loop back path of second bus 530, and units responding are identified as connected via the loop back path to management module 110.
  • management module 110 notifies a user of the communication break.
  • identifiers of units identified in optional stages 6040, 6050 are further communicated to the user, thus indicating further information as to the location of the break.
  • stage 6020 the routine returns.
  • the routines of Fig. HA and HB have been explained with second bus 530 being utilized for broadcast of emergency messages, and first bus 520 being utilized for ongoing communication; however this is not meant to be limiting in any way.
  • Second bus 530 may be utilized to assign addresses for use by first bus 520 without exceeding the scope of the invention.
  • First bus 520 and second bus 530 may proceed in a single cable, and thus a break in one of first bus 520 and second bus 530 may most likely be indicative of a break in a second one of first bus 520 and second bus 530 without exceeding the scope of the invention.
  • Fig. 5 illustrates a high level flow chart of an embodiment of the operation of management module 110 of Figs. 4A, 4B to allocate power equally to all power managed modules in accordance with the principle of the current invention.
  • stage 1000 the power requirements of all attached modules are input.
  • a minimum and a desired power requirement are supplied by the local power manager 320.
  • power manager 320 draws power irrespective of an allocated or non-allocated power budget for the associated operating circuitry 330, 460.
  • power requirements are supplied by a user utilizing a host computer or controller communicating with management module 110.
  • stage 1010 information regarding the total available power for the modules whose power requirements were input in stage 1000 is input.
  • status information 405 in combination with current indicator 410 provides information regarding power availability.
  • a host controller or computer is operable by a user to input a rated power capability of each power supply 100 exhibiting a power good signal via status information 405.
  • the rated power is discounted by an estimate of the power usage of management module 110 and other inherent losses in the system including power used by each power manager 320. In another embodiment the rated power is further discounted by inherent losses of each DC/DC converter 300. In another embodiment a maximum power usage to be allocated for non-power managed modules attached to rack and drawing power from power supplies 100 is input in stage 1000 and deducted in stage 1010. In another embodiment the power usage reported by power manger 320 for operating circuit 460 comprises power allocated by a PoE managing circuit 470 due to classification irrespective as to the amount of power actually drawn by a PD.
  • stage 1020 a power budget is allocated for each module whose power requirements were input in stage 1000 on an equal basis.
  • the desired power requirement as input in stage 1000 is fully met, no additional power is allocated to the module, and the balance of the available power is thus allocated to other modules.
  • power is allocated as a percentage of the desired power requirements, and thus power is budgeted equally on a pro-rata basis of the maximum desired power.
  • the above embodiments are not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget.
  • the power budgets determined are transmitted to power managers 320 of each of the modules.
  • stage 1030 power availability as indicated by status information 405 in combination with current indicator 410 is continuously monitored and the dynamically changing power requirements of the modules are again input. It is to be understood that the power requirement of the modules may change on a dynamic basis, for example if one module comprises a PoE device, the addition or removal of a PD changes the power requirements associated with the PoE device to which it is connected, or from which it has been removed. [000101] In stage 1040 the dynamically variable power requirements are compared with the continuously updated power availability. In the event that in stage 1040, sufficient power is available for all modules, stage 1020 as described above is executed.
  • additional power may be allocated, or budgeted, to at least one attached module without affecting the operation of other modules, as sufficient power has been determined to be available from power supplies 100.
  • power is reallocated to all attached modules. It is to be understood that at least one module may have its power budget reduced. Power is reallocated for each module on an equal basis. In one embodiment, in the event that the dynamic desired power requirement of a module as input in stage 1030 is fully met, no additional power is allocated to the module, and the balance of the available power is thus allocated to other modules.
  • power is allocated as a percentage of the dynamic desired power requirements, and thus power is budgeted equally on a pro-rata basis of the maximum desired power.
  • the above embodiments are not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget.
  • the power budgets determined are transmitted to power managers 320 of each of the modules.
  • Preferably reallocation according to stage 1050 is in accordance with the same method used for allocation in stage 1020. After the operation of stage 1050, stage 1030 as described above is again executed.
  • the method of Fig. 5 is preferably run at start up, and further preferably the loop of stages 1020 - 1050 is run continuously, or on a periodic basis, or in response to a sensed change in one of the dynamic power requirements and the power availability.
  • Fig. 6 illustrates a high level flow chart of an embodiment of the operation of management module 110 of Figs. 4A 5 4B to allocate power according to priority to power managed modules in accordance with the principle of the current invention
  • hi stage 1100 the power requirements and priority levels of all attached modules are input.
  • a minimum and a desired power requirement are supplied by the local power manager 320.
  • power manager 320 draws power irrespective of an allocated or non-allocated power budget for the associated operating circuitry 330, 460.
  • at least one of power requirements and priority levels are supplied by a user utilizing a host computer or controller communicating with management module 110.
  • stage 1110 information regarding the total available power for the modules whose power requirements were input in stage 1100 is input.
  • status information 405 in combination with current indicator 410 provides information regarding power availability.
  • a host controller or computer is operable by a user to input a rated power capability of each power supply 100 exhibiting a power good signal via status information 405.
  • the rated power is discounted by an estimate of the power usage of management module 110 and other inherent losses in the system including power used by each power manager 320. In another embodiment the rated power is further discounted by inherent losses of each DC/DC converter 300. In another embodiment a maximum power usage to be allocated for non-power managed modules attached to rack and drawing power from power supplies 100 is input in stage 1100 and deducted in stage 1110. In another embodiment the power usage reported by power manger 320 for operating circuit 460 comprises power allocated by a PoE managing circuit 470 due to classification irrespective as to the amount of power actually drawn by a PD.
  • stage 1120 a power budget is allocated for each module whose power requirements were input in stage 1100 in accordance with priority. Power requirements of modules exhibiting high priority receive a power allocation up to the power requirements prior to power being allocated to modules of a lower priority. In one embodiment power is allocated on an equal basis to modules of the same priority or as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the maximum desired power. The above is not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget. The power budgets determined are transmitted to power managers 320 of each of the modules. Once power has been allocated to the highest priority modules, power is allocated to lower priority modules in a similar fashion.
  • a module may have a minimum operating requirement at a high priority, with additional power requirements at a lower priority. Thus, the module will almost always receive a minimum operating power level, and in the event of additional power be supplied with an additional power allocation.
  • stage 1130 power availability as indicated by status information 405 in combination with current indicator 410 is continuously monitored and the dynamically variable power requirements of the modules are again input. It is to be understood that the power requirement of the modules may change on a dynamic basis, for example if one module comprises a PoE device, the addition or removal of a PD changes the power requirements associated with the PoE device to which it is connected, or from which it has been removed.
  • stage 1140 the dynamically variable power requirements are compared with the continuously update power availability.
  • stage 1120 as described above is executed. It is to be understood that additional power may be allocated, or budgeted, to at least one attached module without affecting the operation of other modules, as sufficient power has been determined to be available from power supplies 100.
  • stage 1150 power is reallocated to all attached modules. It is to be understood that at least one module may have its power budget reduced. Power is reallocated for each module in accordance with priority.
  • Power requirements of modules exhibiting high priority receive a power allocation up to the power requirements prior to power being allocated to modules of a lower priority.
  • power is reallocated on an equal basis to modules of the same priority or as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the maximum desired power.
  • the above is not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to reallocate a power budget.
  • the power budgets determined are transmitted to power managers 320 of each of the modules. Once power has been allocated to the highest priority modules, power is reallocated to lower priority modules in a similar fashion.
  • Preferably reallocation according to stage 1150 is in accordance with the same method used for allocation in stage 1120. After the operation of stage 1150, stage 1130 as described above is again executed.
  • the method of Fig. 6 is preferably run at start up, and further preferably the loop of stages 1120 - 1150 is run continuously, or on a periodic basis, or in response to a sensed change in one of the dynamic power requirements and the power availability.
  • Fig. 7 illustrates a high level flow chart of an embodiment of the operation of the management module 110 of Figs. 4A, 4B to allocate a minimum power level to all power managed modules, and to allocate any additional available power according to priority in accordance with the principle of the current invention.
  • the power requirements comprising a minimum and a desired power requirement and priority levels of all attached modules are input.
  • the minimum and desired power requirements are supplied by the local power manager 320. It is to be understood that in this embodiment, power manager 320 draws power irrespective of an allocated or non-allocated power budget for the associated operating circuitry 330, 460.
  • At least one of power requirements and priority levels are supplied by a user utilizing a host computer or controller communicating with management module 110. It is further understood, that in the event that an unmanaged module is attached which draws power from power supplies 100, information regarding the power drawn by the unmanaged module is to be input by a user utilizing a host computer or controller communicating with management module 110. The input power drawn for the unmanaged module is to be deducted from any available power budget, since the unmanaged module can not reduce consumption in response to management module 110. [000114] In stage 1210, information regarding the total available power for the modules whose power requirements were input in stage 1200 is input. In an exemplary embodiment status information 405 in combination with current indicator 410 provides information regarding power availability.
  • a host controller or computer is operable by a user to input a rated power capability of each power supply 100 exhibiting a power good signal via status information 405.
  • the rated power is discounted by an estimate of the power usage of management module 110 and other inherent losses in the system including power used by each power manager 320.
  • the rated power is further discounted by inherent losses of each DC/DC converter 300.
  • a maximum power usage to be allocated for non-power managed modules attached to rack and drawing power from power supplies 100 is input in stage 1200 and deducted in stage 1210.
  • the power usage reported by power manger 320 for operating circuit 460 comprises power allocated by a PoE managing circuit 470 due to classification irrespective as to the amount of power actually drawn by a PD.
  • stage 1220 a minimum power budget is allocated for each module whose minimum power requirements were input in stage 1200 equally.
  • power is allocated on an equal basis to all modules up to the minimum power requirement as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the minimum required power.
  • minimum power allocation is done in order of priority. The power budgets determined are transmitted to power managers 320 of each of the modules.
  • stage 1230 additional available power, in excess of the power allocated in stage 1220, is allocated for each module whose power requirements were input in stage 1200 in accordance with priority.
  • Power requirements of modules exhibiting high priority receive a power allocation up to the power requirements prior to power being allocated to modules of a lower priority.
  • power is allocated on an equal basis to modules of the same priority or as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the maximum desired power.
  • the above is not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget.
  • the additional power budgets determined are transmitted to power managers 320 of each of the modules. Once power has been allocated to the highest priority modules, power is allocated to lower priority modules in a similar fashion.
  • stage 1240 power availability as indicated by status information 405 in combination with current indicator 410 is continuously monitored and the dynamically variable power requirements of the modules are again input. It is to be understood that the power requirement of the modules may change on a dynamic basis, for example if one module comprises a PoE device, the addition or removal of a PD changes the power requirements associated with the PoE device to which it is connected, or from which it has been removed.
  • stage 1250 the dynamically variable power requirements are compared with the continuously update power availability. In the event that in stage 1250 sufficient power is available for all modules, stages 1230 and 1240 as described above is executed. It is to be understood that additional power may be allocated, or budgeted, to at least one attached module without affecting the operation of other modules, as sufficient power has been determined to be available from power supplies 100.
  • stage 1260 power is reallocated to all attached modules. It is to be understood that at least one module may have its power budget reduced. Power is reallocated for each module in accordance with priority, with a minimum required power being first allocated to all modules. Power requirements of modules exhibiting high priority receive a power allocation up to the power requirements prior to power being allocated to modules of a lower priority. In one embodiment power is reallocated on an equal basis to modules of the same priority or as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the maximum desired power.
  • stage 1260 Preferably reallocation according to stage 1260 is in accordance with the same method used for allocation in stages 1220 and 1230. After the operation of stage 1260, stage 1240 as described above is again executed.
  • the method of Fig. 7 is preferably run at start up, and further preferably the loop of stages 1230 - 1260 is run continuously, or on a periodic basis, or in response to a sensed change in one of the dynamic power requirements and the power availability.
  • Fig. 8 is a high level flow chart of an ongoing operation of management module 110 of Figs. 4A, 4B to maintain a potential scenario chart comprising power budgets for each power managed module according to an aspect of the invention.
  • stage 2000 power consumption of all attached modules is input. While stage 2000 has been described as inputting power consumption, this is not meant to be limiting in any way.
  • a minimum power requirement, or a plurality of power requirements and priorities, or an allocated power which may be called upon but not utilized, may be input without exceeding the scope of the invention.
  • management module 110 communicates with each power manager 320 and receives an indication of power consumption.
  • power consumption is input based on current indicator 410 of power supplies 100.
  • a power budget for each module is determined.
  • a power supply scenario is defined as the loss of one or more of the plurality of power supplies 100 of Fig. 4A.
  • each potential total power output of the plurality of power supplies 100 for which one of the power supplied have failed is taken as a potential scenario.
  • a revised power budget is calculated for each module.
  • the power budget determined is in accordance with stage 1050 of Fig. 5, 1150 of Fig. 6 or 1260 of Fig.
  • stage 2010 develops a potential action for each potential power source scenario.
  • Stage 2010 will be described herein as being responsive to status indicator 405 of each power supply having a binary value in which a value of 1 indicates full rated power availability and a value of 0 indicates no power. This is not meant to be limiting in any way, and a multiplicity of values, including derating due to an increased temperature or stress level is specifically intended.
  • Table I is a representation of an embodiment of the potential scenario chart produced as an outcome of stage 2010 in accordance with the principle of the invention.
  • a total power available is determined and a scenario number is assigned.
  • a total scenario available power is determined and a power budget per module is determined.
  • Table I is described as assigning an equal power budget to each module, as described above in relation to Fig. 5, however this is not meant to be limiting in any way.
  • a scenario power budget may be based on a minimum power requirement, a percentage of current power usage as input in stage 2000, or take priority into account without exceeding the scope of the invention. In one embodiment power is budgeted for all high priority power requirements first, and then subsequent power requirements of lower priority are budgeted.
  • stage 2020 the scenarios associated with the power budget for each scenario is transmitted to each of the power managers 320 of the respective attached modules.
  • management module 110 will operate to broadcast the scenario number to change to in a manner that will be further described below. In one embodiment the broadcast is done on the provided emergency bus as described above in relation to Figs. 4A, 4B, 1 IA and 1 IB.
  • the routine of Fig. 8 prepares and transmits potential power event scenarios to each connected power manager 320 associated with a potential power budget for each of the scenarios.
  • Fig. 9 is a high level flow chart of the operation of the management module 110 of Figs. 4A, 4B in accordance with the principle of the current invention, in the event of a change in power condition associated with one or more power sources.
  • a change in power status indicator is sensed.
  • the power status indicator in one embodiment presents a binary value indicating either full or no power, and in another embodiment presents a plurality of values indicative of a need to derate the power supply 100 associated with the status indicator 405.
  • stage 3010 the table generated in stage 2010 of Fig. 8 is retrieved from memory, and the scenario number associated with the current status indicators 405 is retrieved.
  • stage 3020 the scenario number retrieved in stage 3010 is broadcast to all power managers 320.
  • the scenario number is broadcast on the provided emergency bus as described above in relation to Figs. 4A, 4B, 1 IA and 1 IB.
  • power mangers 320 upon receipt of the broadcast immediately acts to update the power drawn to the amount received in stage 2020 of Fig. 8.
  • each PoE managing circuit 470 is instructed to disable ports if required, preferably observing local priority, to achieve the revised local power budget.
  • power manager 320 reduces power drawn, by reducing the clock speed or shedding other loads.
  • management module 110 may transmit an allocation reduction to each power manager for each scenario without exceeding the scope of the invention.
  • each power manager 320 responsive to the broadcast message of stage 3020, each power manager 320 is operative to reduce power drawn by the pre-transmitted amount in accordance with the scenario broadcast received.
  • stage 3030 total power consumption, preferably as determined by current indicators 410 of Fig.
  • stage 3030 is implemented using fuzzy logic. In the event that total power consumption has not stabilized stage 3030 is repeated. In the event that in stage 3030 total power consumption has stabilized, in stage 3040 a reallocation routine as described above in relation to Figs. 5 - 7 is called. Thus, the operation of stage 3020 results in a rapid reduction of power drawn, and stage 3030 allows for stabilization at the reduced power allocatoins. Reallocation in accordance with stages 1030 - 1050 of Fig. 5, 1130 - 1150 of Fig. 6 or 1240 - 1260 of Fig. 7 fine tunes the system in accordance with the available power.
  • Stage 3030 is described herein as observing the rate of change of total power consumption, however this is not meant to be limiting in any way. Stage 3030 may be replaced with a stage awaiting confirmation from each of the plurality of power managers 320 that power drawn is within budget, or with a fixed delay, without exceeding the scope of the invention.
  • Fig. 10 is a high level flow chart of the operation of a power manager 320 to automatically detect a reduced power availability, and in response reduce power consumption in accordance with the principle of the current invention. In stage 4000 the voltage at the power managed device is monitored and a reduced voltage is detected. Such a reduced voltage is indicative of an overload condition.
  • Power manager 320 in response to a sensed reduction in voltage in stage 4000, and in the absence of communication with management module 110, in stage 4010 reduces power consumption.
  • power manager 320 communicates with a respective operating circuit 330, 460 to reduce power consumption by a pre-determined amount or percentage.
  • power is consumed in levels or stages, and power is reduced to the next lower level.
  • stage 4020 voltage at the power managed device is again monitored. In the event that voltage has stabilized within tolerance, in stage 4030 the power allocation is maintained for operating circuit 330, 460 in accordance with the reduced setting of stage 4010. Thus, the reduced setting is treated as a revised power budget in the absence of communication with management module 110.
  • stage 4010 is again run to further reduce power drawn. It is to be understood that preferably the operation of stage 4010 does not reduce power below a minimum operating level.
  • the present embodiments enable a system having at least one power source, a management module and a plurality of power managed modules in communication with the management module.
  • Each of the power managed modules are arranged to be able to draw at least some power from the at least one power source.
  • Each of the power managed modules comprises a power manager operable to control the power drawn by the power managed module.
  • the management module allocates a power budget for each of the power managed modules, and the power managers of the power managed modules operate to control module operation so that power drawn is within the allocated budget.
  • Power managed modules may comprise PoE devices, switches, hubs, concentrators, computing equipment or other telecommunication modules operable at a plurality of power levels. Power managed modules may be supplied with an on board power supply, or preferably without an on board power supply. A central power source, preferably comprising at least one power supply, and further preferably comprising a plurality of power supplies, thus optimally supplies operating power for some or all of the power managed modules within the rack. The management module allocates power for each of the power managed modules drawing power. [000140] The power budget is dynamically allocated based on pre-defined criteria.
  • the management module directs each of the power managed modules to change their power consumption to a pre-assigned amount. In another embodiment, in the event of a failure of one or more power supplies, the management module directs each of the power managed modules to reduce their power consumption by a pre-assigned amount.
  • the power manager of at least one power managed module may sense a change in a voltage level from the at least one power source, and in response reduce power consumption. Such a response enables automatic power management by the power manager in the absence of communication from the management module.
  • the central power source comprises a plurality of power supplies, arranged in an N + M redundant arrangement.
  • the management module reserves the power of M redundant power supplies so as to provide the budgeted power in the absence of one or more failed power supplies.
  • the invention thus provides chassis functionality for distributed rack level equipment.
  • the system provides a plurality of buses, a first bus of which is used for ongoing communication of power requirements and budgets, and a second bus being used for emergency communication, such as in the event of a failure of at least one power supply of the central power source.
  • a plurality of scenarios are generated and pre-transmitted to the modules, preferably over the first bus.
  • one of the scenarios is implemented by broadcasting an implementing message, preferably over the second bus.
  • at least one of the first and second bus is arranged in a closed ring configuration, thus allowing for identifying a communication breakdown by monitoring a loop back path.

Abstract

A system for rack level power management, the system comprising: at least one power source; a management module; and a plurality of power managed modules in communication with the management module and connected to draw power from the at least one power source, each of the plurality of power managed modules comprising a power manager and an operating circuit, the operating circuit being operable at a plurality of power drawing levels responsive to the power manager, the management module being operative to allocate a power budget to each of the plurality of power managed modules and communicate the allocated power budgets to the power managers, each of the power managers being operative to control the operating circuit of the power managed module to be operable at a power drawing level within the allocated budget.

Description

RACK LEVEL POWER MANAGEMENT
BACKGROUND OF THE INVENTION
[0001] The present invention relates to the field of power management, and more particularly to a system providing rack level power management for a telecommunications rack utilizing a centralized DC power source. [0002] Systems comprising multiple modules, such as telecommunication systems, are often rack mounted, in which a plurality of independent modules are secured to a common rack, which is typically 19" wide. Each module in the rack is typically supplied with an on board power supply drawing power from a common AC mains. The on board power supply of each unit thus functions to convert AC mains power to a local DC power at the appropriate voltage for the electronics in the module. [0003] A module which is utilizing only a small amount of energy, such as when the module is off or in a standby mode, still consumes and wastes energy. Furthermore, a multiplicity of independent small power supplies is inefficient, with the power supply in some modules outputting power at full capacity, while power supplies of other modules are at a low capacity. Power supply longevity is at least partially a function of the utilization rate, in which typically a highly utilized power supply begins to exhibit an increased temperature. This increase in temperature leads to a shortened life for the power supply. Thus, certain modules in the rack may experience early failure due to power supply stress, while neighboring modules may be operating at low utilization rates. [0004] Power over Ethernet (PoE) is a technology enabling the delivery of power to powered devices (PD) from a power sourcing equipment (PSE) over communication cabling. A standard for PoE has been published by the Institute of Electrical and Electronics Engineers, Inc., New York, N.Y as IEEE Std. 802.3af - 2003 the entire contents of which is incorporated herein by reference. A PSE detects a PD requesting power, and in the event the PSE elects to power the PD, optionally classifies the power requirements of the detected PD, and then powers the PD within a pre-determined time after the completion of detection. PoE is a scalable technology, in which additional PDs with associated power requirements may be added by the user after an initial installation. The additional power requirements may grow to be in excess of the originally supplied power source. PoE may be supplied either from a PSE associated with switch/hub equipment, known commercially as a PoE enabled switch, or from a midspan PSE module. Midspan PSE modules may support one or more ports, with units of 1, 8, 12, 24 and 48 ports being commercially available. PoE enabled switches and midspan PSE modules are collectively denoted herein as PoE devices.
[0005] Prior art systems require a dedicated additional power source to be added as a module, feeding the additional required power. The dedicated additional power source is typically initially underutilized, and only experiences optimum utilization as the system power needs grow. This underutilized dedicated additional power source is thus unavailable in the event that one of the other modules in the system has reached maximum utilization of its on-board power supply. [0006] Chassis and blade telecommunication switch equipment has been designed to ensure maximum up-time. The chassis comprises a housing for receiving and interconnecting by means of a backplane: blades; switch modules; management modules; power supplies; cooling fans; and other components. Chassis are expensive, however preferably are designed to provide redundancy and extremely high levels of service. For example, a plurality of cooling fan blades may be supplied, one cooling fan blade providing redundancy for an operating cooling fan blade. Similarly, chassis typically supply some level of redundancy for power sources and management modules. Unfortunately, chassis are expensive, and limit the purchaser to the use of equipment compatible with the backplane of the chassis. As described above, rack level equipment allows for the use of modules which are rack mounted and may be interconnected with standardized cabling. Thus, the use of rack level equipment provides certain flexibility and the ability to avoid an initial high cost associated with the chassis. Unfortunately, the use of rack level equipment does not provide the levels of redundancy associated with chassis equipment.
[0007] U.S. Patent S/N 5,652,893 issued to Ben-Meir et al discloses a power management system for a local area network hub. A power source, also known as a power supply, is provided having one or more elements providing a maximum power available for the system. Manageable modules are connected to the switching hub, each of the manageable modules having a memory providing information as to the power requirements of the module. A controller module comprising a microprocessor calculates the power requirements of the system and enables or disables manageable modules in accordance with power availability. Unfortunately, the system only allows for two states for each module, enabled and disabled. Thus, a module may not be powered at a low or medium power state. The embodiment of Ben-Meir is an example of chassis equipment. [0008] What is needed therefore, and is not provided by the prior art, is a system providing rack level power management, in which power is allocated to rack mounted modules, with modules receiving a variable allocation of power responsive to power availability and the needs and priority levels associated with modules in the rack.
SUMMARY OF THE INVENTION
[0009] Accordingly, it is a principal object of the present invention to overcome the disadvantages of prior art. This is provided in the present invention by a system having at least one power source, a management module and a plurality of power managed modules in communication with the management module. Each of the power managed modules are arranged to be able to draw at least some power from the at least one power source. Each of the power managed modules comprises a power manager operable to control the power drawn by the power managed module. The management module allocates a power budget for each of the power managed modules, and the power managers of the power managed modules operate to control module operation so that power drawn is within the allocated budget. [00010] Power managed modules may comprise PoE devices, switches, hubs, concentrators, computing equipment or other telecommunication modules operable at a plurality of power levels. Power managed modules may be supplied with an on board power supply, or preferably without an on board power supply. A central power source, preferably comprising at least one power supply, and further preferably comprising a plurality of power supplies, thus optimally supplies operating power for some or all of the power managed modules within the rack. The management module allocates power for each of the power managed modules drawing power. [00011] The power budget is dynamically allocated based on pre-defined criteria. In the event of a failure of one or more power supplies of the central power source, in one embodiment the management module directs each of the power managed modules to change their power consumption to a pre-assigned amount. In another embodiment, in the event of a failure of one or more power supplies, the management module directs each of the power managed modules to reduce their power consumption by a pre-assigned amount.
[00012] In one embodiment, the power manager of at least one power managed module may sense a change in a voltage level from the at least one power source, and in response reduce power consumption. Such a response enables automatic power management by the power manager in the absence of communication from the management module. [00013] In one embodiment the central power source comprises a plurality of power supplies, arranged in an N + M redundant arrangement. The management module reserves the power of M redundant power supplies so as to provide the budgeted power in the absence of one or more failed power supplies. The invention thus provides chassis functionality for distributed rack level equipment. [00014] In one embodiment the system provides a plurality of buses, a first bus of which is used for ongoing communication of power requirements and budgets, and a second bus being used for emergency communication, such as in the event of a failure of at least one power supply of the central power source. A plurality of scenarios are generated and pre-transmitted to the modules, preferably over the first bus. In the event of a power event, such as the failure of one or more power supplies, one of the scenarios is implemented by broadcasting an implementing message, preferably over the second bus. Further preferably, at least one of the first and second bus is arranged in a closed ring configuration, thus allowing for identifying a communication breakdown by monitoring a loop back path. [00015] The invention provides for a system for rack level power management, the system comprising: at least one power source; a management module; and a plurality of power managed modules in communication with the management module and connected to draw power from the at least one power source, each of the plurality of power managed modules comprising a power manager and an operating circuit, the operating circuit being operable at a plurality of power drawing levels responsive to the power manager, the management module being operative to allocate a power budget to each of the plurality of power managed modules and communicate the allocated power budgets to the power managers, each of the power managers being operative to control the operating circuit of the power managed module to be operable at a power drawing level within the allocated budget.
[00016] In one embodiment the management module is connected to receive an indication of power availability from the at least one power source, the power budgets being allocated responsive the received indication. In another embodiment the management module is operative to allocate power budgets on the basis of priority, each of the power managed modules being assigned a priority. In yet another embodiment the plurality of power managed modules exhibits a minimum required power and an additional power level in excess of the minimum required power, the management module being operative to assign a power budget for the minimum required power for each of the plurality of power managed modules, and only in the event that additional power is available, to allocate a power budget for the additional power level of at least one of the plurality of power managed modules. In one further embodiment the power budget for the additional power level is allocated on a priority basis.
[00017] In one embodiment each of the plurality of power managers comprises a power meter, the power manager of each of the plurality of power managers receiving an indication of power drawn from the power meter. In another embodiment at least one of the plurality of power managed modules is selected from the group consisting of power over a Ethernet enabled switch, a switch, a hub, a concentrator, a computing equipment, a power sourcing device, and a telecommunication module.
[00018] In one embodiment the operating circuit of at least one of the plurality of power managed modules comprises a power sourcing device operable for use with a power ready patch panel. In another embodiment the at least one power source and the management module are comprised within a single equipment shelf. [00019] In one embodiment the management module is further operative to input a total power available, the allocated power budgets being responsive to the input total available power. In one further embodiment the system further comprises at least one module not comprising a power manager, the management module being operative to reduce the power requirements of the at least one module from the input total available power. [00020] In one embodiment the management module is further operative to transmit at least one power budget scenario, the management module being further operative to monitor a condition of the at least one power source, and in the event of a change in the monitored condition, to broadcast a command to the plurality of power managed modules, the plurality of power managed modules being operative to adhere to the at least one power budget scenario responsive to the broadcast command. In one further embodiment the system further comprises a first bus and a second bus, wherein the management module is operative to transmit the at least one power budget scenario via the first bus and to broadcast the command via the second bus. In another further embodiment at least one of the first bus and the second bus in arranged in a closed ring arrangement.
[00021] In one embodiment the system further comprises at least one communication bus arranged in a closed ring configuration, the management module being operative to communicate the allocated power budgets via the at least one communication bus. In one further embodiment the management module is further operative to monitor a loop back of the at least one communication bus, and in the event that the communicated allocated power budgets are not received via the monitored loop back, to communicate the allocated power budgets via the loop back. [00022] In one embodiment the power manager of at least one the plurality of power managed modules is further operative to sense a reduced voltage, and responsive to sensed reduced voltage to control the operating circuit associated with the power manager to reduce power drawn.
[00023] Independently the invention provides for a method of rack level power management comprising: providing at least one power source; providing a plurality of power managed modules connected to draw power from the at least one power source; allocating a power budget to each of the provided plurality of power managed modules; and transmitting the allocated power budgets to the plurality of power managed modules, each of the power managed modules controlling the drawn power to be within the transmitted allocated power budget. [00024] In one embodiment the method further comprises receiving an indication of power availability from the at least one power source, the allocating being responsive the received indication. In another embodiment the allocating is at least partially on the basis of priority. [00025] In one embodiment the provided plurality of power managed modules exhibit a minimum required power and an additional power level in excess of the minimum required power, the stage of allocating comprising: allocating the minimum required power for each of the plurality of power managed modules, and in the event that additional power is available, allocating a power budget for the additional power level of at least one of the plurality of power managed modules. In one further embodiment the allocating a power budget for the additional power level is on a priority basis. [00026] In one embodiment the method further comprises for each of the plurality of provided power managed modules, receiving an indication of power drawn by the power managed module. In another embodiment at least one of the provided plurality of power managed modules is selected from the group consisting of power over a Ethernet enabled switch, a switch, a hub, a concentrator, a computing equipment, a power sourcing device, and a telecommunication module. [00027] In one embodiment at least one of the provided plurality of power managed modules comprises a power sourcing device operable for use with a power ready patch panel.
[00028] In one embodiment the method further comprises: inputting a total power available, the allocating a power budget being responsive to the input total available power. In one further embodiment the method comprises providing at least one module not receiving the transmitted allocated power budget; and deducting the power requirements of the at least one module from the input total available power. [00029] In one embodiment the method further comprises: monitoring a condition of the provided at least one power source; transmitting at least one power budget scenario to the provided plurality of power managed modules; and in the event of a change in the monitored condition, broadcasting a command to the plurality of power managed modules, the plurality of power managed modules adhering to the transmitted at least one power budget scenario responsive to the broadcast command. In another embodiment the method further comprises: at least one of the provided plurality of power managed modules sensing a reduced voltage; and responsive to sensed reduced voltage, reducing power drawn by the provided power managed module. [00030] In one embodiment the method further comprises: monitoring a loop back of the transmitted allocated power budgets; and in the event that at least one of the transmitted allocated power budgets is not sensed by the monitoring, retransmitting the not sensed power budget via the loop back. In another embodiment the method further comprises: monitoring a condition of the provided at least one power source; transmitting at least one power budget scenario to the provided plurality of power managed modules via first bus; and in the event of a change in the monitored condition, broadcasting a command to the plurality of power managed modules via a second bus different than the first bus, the plurality of power managed modules adhering to the at least one power budget scenario responsive to the broadcast command.
[00031] Independently the invention provides for a system for rack level power management, the system comprising: at least one power source comprising a plurality of power supplies; a management module; and a plurality of power managed modules in communication with the management module and connected to draw power from the at least one power source, each of the plurality of power managed modules comprising a power manager and an operating circuit, the operating circuit being operable at a plurality of power drawing levels responsive to the power manager, the management module being operative to allocate a power budget to each of the plurality of power managed modules and communicate the allocated power budgets to the power managers, and being further operative to communicate a plurality of power scenarios and associated power budgets to the power managed modules, each of the power managers being operative to control the operating circuit of the power managed module to be operable at a power drawing level within the allocated budget, and in response to a communication from the management module to activate a scenario to control the operating circuit of the power managed module to be operable at a power drawing level within the power budget associated with the activated scenario. [00032] Additional features and advantages of the invention will become apparent from the following drawings and description. BRIEF DESCRIPTION OF THE DRAWINGS
[00033] For a better understanding of the invention and to show how the same may be carried into effect, reference will now be made, purely by way of example, to the accompanying drawings in which like numerals designate corresponding elements or sections throughout.
[00034] With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of the preferred embodiments of the present invention only, and are presented in the cause of providing what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the invention. In this regard, no attempt is made to show structural details of the invention in more detail than is necessary for a fundamental understanding of the invention, the description taken with the drawings making apparent to those skilled in the art how the several forms of the invention may be embodied in practice. In the accompanying drawings:
[00035] Fig. 1 illustrates a high level view of rack mounted telecommunication equipment according to the teaching of the prior art;
[00036] Fig. 2A illustrates a high level view of a first embodiment of rack mounted telecommunication equipment according the principle of the current invention;
[00037] Fig. 2B illustrates a high level view of a second embodiment of rack mounted telecommunication equipment according the principle of the current invention
[00038] Fig. 3 illustrates a high level block diagram of an embodiment of a power managed module in accordance with the principle of the current invention;
[00039] Fig. 4A illustrates a high level block diagram of an embodiment of a management module and a plurality of power supplies in communication with at least one power managed module in accordance with the principle of the current invention; [00040] Fig. 4B is a high level block diagram of an embodiment of the data connection of Fig. 4A exhibiting a first and second data bus in accordance with the principle of the current invention; [00041] Fig. 5 illustrates a high level flow chart of an embodiment of the operation of the management module to allocate power equally to all power managed modules in accordance with the principle of the current invention; [00042] Fig. 6 illustrates a high level flow chart of an embodiment of the operation of the management module to allocate power according to priority to power managed modules in accordance with the principle of the current invention; [00043] Fig. 7 illustrates a high level flow chart of an embodiment of the operation of the management module to allocate a minimum power level to all power managed modules, and to allocate any additional available power according to priority in accordance with the principle of the current invention;
[00044] Fig. 8 is a high level flow chart of an ongoing operation of the management module to maintain a potential scenario chart comprising power budgets for each power managed module according to an aspect of the invention; [00045] Fig. 9 is a high level flow chart of the operation of the management module, in accordance with the principle of the current invention, in the event of a change in power condition associated with one or more power supplies; [00046] Fig. 10 is a high level flow chart of the operation of a power manager to automatically detect a reduced power availability, and in response reduce power consumption in accordance with the principle of the current invention; [00047] Fig. 1 IA is a high level flow chart of the operation of the management module of Fig. 4B to communicate via a main path of a first bus, and in the event of the transmitted message not being detected via the loop back path of the first bus, retransmitting the message via the loop back path of the first bus in accordance with the principle of the current invention; [00048] Fig. 1 IB is a high level flow chart of the operation of the management module of Fig. 4B to broadcast emergency messages via a main path of a second bus, and in the event of the broadcast message not being detected via a loop back path of the second bus, rebroadcasting the message via the loop back path of the second bus in accordance with the principle of the current invention; and [00049] Table I is a representation of an embodiment of the potential scenario chart produced as an outcome of the method of Fig. 8 in accordance with the principle of the invention. DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
[00050] The present embodiments enable a system for rack level power management having at least one power source, a management module and a plurality of power managed modules in communication with the management module. Each of the power managed modules are arranged to be able to draw at least some power from the at least one power source. Each of the power managed modules comprises a power manager operable to control the power drawn by the power managed module. The management module allocates a power budget for each of the power managed modules, and the power managers of the power managed modules operate to control module operation so that power drawn is within the allocated budget.
[00051] Power managed modules may comprise PoE devices, switches, hubs, concentrators, computing equipment or other telecommunication modules operable at a plurality of power levels. Power managed modules may be supplied with an on board power supply, or preferably without an on board power supply. A central power source, preferably comprising at least one power supply, and further preferably comprising a plurality of power supplies, thus optimally supplies operating power for some or all of the power managed modules within the rack. The management module allocates power for each of the power managed modules drawing power. [00052] The power budget is dynamically allocated based on pre-defined criteria. In the event of a failure of one or more power supplies of the central power source, in one embodiment the management module directs each of the power managed modules to change their power consumption to a pre-assigned amount. In another embodiment, in the event of a failure of one or more power supplies, the management module directs each of the power managed modules to reduce their power consumption by a pre-assigned amount.
[00053] In one embodiment, the power manager of at least one power managed module may sense a change in a voltage level from the at least one power source, and in response reduce power consumption. Such a response enables automatic power management by the power manager in the absence of communication from the management module. [00054] In one embodiment the central power source comprises a plurality of power supplies, arranged in an N + M redundant arrangement. The management module reserves the power of M redundant power supplies so as to provide the budgeted power in the absence of one or more failed power supplies. The invention thus provides chassis functionality for distributed rack level equipment.
[00055] Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of the components set forth in the following description or illustrated in the drawings. The invention is applicable to other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.
[00056] Fig. 1 illustrates a high level view of telecommunication equipment mounted in a rack 10 according to the teaching of the prior art. Rack 10 comprises a plurality of switches 20, a plurality of patch panels 30, a modem 40, a power strip 50, and a connection to AC mains 60. Each of the plurality of switches 20 and modem 40 comprises an independent on board power suppply (not shown), and thus exhibit a connection to power strip 50. Patch panels 30 are unpowered, and function as interconnect points for connections to and from each of the switches 20 and user nodes (not shown). In a LAN, a patch panel serves as a sort of static switchboard, using cables to interconnect nodes to a switch/server of the local area network. A patch panel typically uses a jumper cable called a patch cord or a patch cable to create each interconnection typically between a switch port and a patch panel port representing a user node. The patch cables are not shown for clarity. [00057] A module, such as one of switches 20 and modem 40, which is utilizing only a small amount of energy, such as when the module is off or in a standby mode, still consumes and wastes energy. Furthermore, a multiplicity of independent small power supplies is inefficient, as represented by the power supplies contained within each of switches 20 and modem 40, with the power supply in some modules outputting power at full capacity, while power supplies of other modules are at a low capacity. Power supply longevity is at least partially a function of the utilization rate, in which typically a highly utilized power supply begins to exhibit an increased temperature. This increase in temperature leads to a shortened life for the power supply. Thus, certain modules in the rack may experience early failure due to power supply stress, while neighboring modules may be operating at low utilization rates.
[00058] Fig. 2A illustrates a high level view of a first embodiment of rack mounted telecommunication equipment according the principle of the current invention, comprising a rack 10 securing a plurality of power supplies 100, a management module 110, a power sourcing device 120, a power ready patch panel 130, a power managed module 140, a plurality of switches 150, a patch panel 30, a power strip 50 and a connection to AC mains 60. The plurality of power supplies 100 are shown contained within a single shelf 160 of rack 10 as a single power source, shelf 160 further comprising management module 110. Power managed module 140 may comprise a switch, hub equipment, modem, midspan PSE, computing equipment or gateway without exceeding the scope of the invention. [00059] In an exemplary embodiment, shelf 160 is no more than IU high, and is designed with a backplane such that each of the plurality of power supplies 100 may be hot swappable. The backplane is further designed such that a power supply 100 may not be plugged into the slot intended to receive management module 110 and management module 110 may not be plugged into any slot intended to receive a power supply 100. [00060] The plurality of power supplies 100 each exhibit a connection to power strip 50, however in contrast to the prior art configuration of Fig. 1, other modules do not exhibit a connection to power strip 50. Shelf 160 exhibits connections to power sourcing device 120, power managed module 140 and switches 150, with the connection supplying both power from the plurality of power supplies 100 and data communication with management module 110. Power sourcing device 120, power managed module 140 and switches 150 are shown as not comprising an on board AC/ DC power supply, as indicated by the lack of connection to power strip 50, however this is not meant to be limiting in any way. Any one or more of power sourcing device 120, power managed module 140 and switches 150 may comprise an on board AC/DC power supply, with power supplies 100 supplying either additional or redundant power without exceeding the scope of the invention. [00061] In operation, power supplies 100 are connected in a power sharing arrangement, and management module 110 is arranged to receive an indication of power output from each of power supplies 100. In an exemplary embodiment power supplies 100 are arranged as single power source in an N + M redundant arrangement, with M power supplies 100 acting as redundant sources for N operating power supplies 100. In one embodiment, each of power supplies 100 supply an indication of power output, and in another embodiment a separate current indicator, and preferably a voltage meter, is supplied. Management module 110 is in communication with each of the modules drawing power from power supplies 100, such as power sourcing device 120, power managed module 140 and switches 150, and obtains an indication of the power requirements from each of the modules. Power is allocated to each of the modules according to pre-defined criteria, and the modules are operative to draw power in accordance with the allocation. In one embodiment power is allocated equally to all of the modules, in another embodiment power is allocated in accordance with priority and in another embodiment power is allocated at a minimum operating level to all modules and additional power is allocated in accordance with priority. [00062] Fig. 2B illustrates a high level view of a second embodiment of rack mounted telecommunication equipment according the principle of the current invention comprising a rack 10 securing a first power shelf 210 comprising a plurality of power supplies 100 and a management module 110; a second power shelf 220 comprising a plurality of power supplies 100 and a redundant management module 110; a power sourcing device 120; a power ready patch panel 130; a power managed module 140; a switch 150; a switch having an on board power supply 200; a patch panel 30; a power strip 50; and a connection to AC mains 60. Power managed module 140 may comprise a switch, hub equipment, modem, midspan PSE, computing equipment or gateway without exceeding the scope of the invention. [00063] In an exemplary embodiment, each of first power shelf 210 and second power shelf 220 is no more than IU high, and is designed with a backplane such that each of the plurality of power supplies 100 may be hot swappable. Each of first power shelf 210 and second power shelf 220 thus functions as a power source comprising a plurality of power supplies 100. Alternatively, first power shelf 210 and second power shelf 220 are arranged to function as a single power source. The backplane is further designed such that a power supply 100 may not be plugged into the slot intended to receive management module 110 and management module 110 may not be plugged into any slot intended to receive a power supply 100. [00064] The plurality of power supplies 100 each exhibit a connection to power strip 50, however in contrast to the prior art configuration of Fig. 1, other modules, with the exception of switch having on board power supply 200, do not exhibit a connection to power strip 50. First power shelf 210 and second power shelf 220 exhibit connections to power sourcing device 120, power managed module 140, switch 150 and switch having on board power supply 200, with the connection supplying both power from the plurality of power supplies 100 and data communication with management modules 110. Power sourcing device 120, power managed module 140 and switches 150 are shown as not comprising an on board power supply, as indicated by the lack of connection to power strip 50, however this is not meant to be limiting in any way. Any one or more of power sourcing device 120, power managed module 140 and switches 150 may comprise an on board power supply, with power supplies 100 supplying either additional or redundant power without exceeding the scope of the invention. [00065] In operation, power supplies 100 are connected in a power sharing arrangement, and management module 110 is arranged to receive an indication of power output from each of power supplies 100. In an exemplary embodiment power supplies 100 are arranged as single power source in an N + M redundant arrangement, with M power supplies 100 acting as redundant sources for N operating power supplies 100. First power shelf 210 acts as a first power source and second power shelf 220 acts as a second power source. In an alternative embodiment, first power shelf 210 and second power shelf 220 are arranged to act a single unified power source. In one embodiment, each of power supplies 100 supply an indication of power output, and in another embodiment a separate current indicator, and preferably a voltage meter, is supplied. Management module 110 of first power shelf 210 and management module 110 of second power shelf 220 act as redundant management modules, with a first one of the management modules 110 acting as an active module and a second one of the management modules 110 acting as a redundant module. [00066] The active management module 110 is in communication with each of the modules drawing power from power supplies 100, such as power sourcing device 120, power managed module 140, switch 150 and switch having on board power supply 200, and obtains an indication of the power requirements from each of the modules. Power is allocated to each of the modules according to pre-defined criteria, and the modules are operative to draw power in accordance with the allocation. In one embodiment power is allocated equally to all of the modules, in another embodiment power is allocated in accordance with priority and in another embodiment power is allocated at a minimum operating level to all modules and additional power is allocated in accordance with priority. Redundant management module 110 monitors the indications received by active management module 110, and thus acts as a redundant module capable of operation in the event of a failure of active management module 110. [00067] Fig. 3 illustrates a high level block diagram of an embodiment of a power managed module 140 in accordance with the principle of the current invention. Power managed module 140 comprises a hot swap controller 305, a DC/DC converter 300, a power meter 310, a power manager 320 and an operating circuit 330. Hot swap controller is arranged to allow for hot swapping of power managed module 140. DC/DC converter 300 is arranged to receive DC operating power from the plurality of power supplies 100 of Figs. 2A, 2B via hot swap controller 305. The output of DC/DC converter 300 is passed through power meter 310 to operating circuit 330. Power manager 320 is arranged to be in communication with management module 110, to receive an indication of power drawn by operating circuit 330 from power meter 310 and to communicate with operating circuit 330. In one embodiment the output of DC/DC converter 300 is an intermediate operating voltage, typically on the order of 5 - 12 volts, and operating circuit 330 comprises at least one point of load converter (not shown) operable to convert the intermediate operating voltage to the appropriate voltage as required by operating circuit 330. In an exemplary embodiment the at least one point of load converter communicate with a CPU via an I2C bus and supply power at the required voltage on demand.
[00068] In operation, power manager 320 receives data indicative of a power allocation for power managed module 140 from management module 110. Power manager 320, responsive to the received power allocation, monitors power drawn by operating circuit 330 via power meter 310. In one embodiment power meter 310 further embodies a power limiter, and power manager 320 is operative to limit power drawn by operating circuit 330 by controlling the power limiting functionality of power meter 310. In the event that power drawn by operating circuit 330 is in excess of the received power allocation, power manager 320 is operative to communicate with operating circuit 330 to reduce the power drawn to be within the budget. In one embodiment, operating circuit 330 comprises computing equipment, and power drawn is reduced by lowering the speed of operation, preferably by reducing the voltage supplied by the point of load converter. In another embodiment operating circuit 330 comprises a plurality of PoE PSEs each PSE supplying power through an output port to a PD via communication cabling, and power is disabled from at least one PD thereby reducing power drawn. In yet another embodiment, operating circuit 330 comprises a power sourcing device operable to supply power to a plurality of PDs via a power ready patch panel as described further in co-filed patent application entitled "System for Providing Power over Ethernet through a Patch Panel" the entire contents of which are incorporated herein by reference. Conversely, in the event that power drawn by operating circuit 330 is less than the received power allocation, power manager 320 is operative to communicate with operating circuit 330 indicating the available additional power. In one embodiment, operating circuit 330 comprises computing equipment, and power drawn is increased by increasing the speed of operation, thereby improving performance. In another embodiment operating circuit 330 comprises at least one PoE PSE, and power is enabled for at least one PSE having connected thereto a PD thereby increasing power drawn. [00069] Power manager 320 preferably takes into account any losses associated with hot swap controller 305, DC/DC converter 300 and power meter 310. Preferably, power drawn by power manager 320 is tapped after power meter 310 (not shown), and is thus included within the power drawn indicated by power meter 310. In another embodiment, power drawn by power manager 320 is a pre-determined quantity, and the pre-determined quantity is reduced from the power allocation received. In yet another embodiment the power allocation received is net of power losses associated with hot swap controller 305, DC/DC converter 300, power meter 310 and power drawn by power manager 320.
[00070] Fig. 4A illustrates a high level block diagram of an embodiment of a system 400 comprising management module and a plurality of power sources in communication with at least one power managed module in accordance with the principle of the current invention. System 400 comprises a plurality of power supplies 100 each exhibiting a status indicator signal 405, and a current indicator 410; a management module 110; a PoE device 420; a switch having on board power supply 200; and a PoE enabled switch 450. PoE device 420 comprises a hot swap controller 305, a power meter 310, a power manager 320, and an operating circuit 460 comprising a plurality of PoE managing circuits 470. Switch having on board power supply 200 comprises hot swap controller 305, a DC/DC converter 300, an AC/DC converter 440, a connection to AC mains 60, a power meter 310, a power manager 320, and an operating circuit 330. PoE enabled switch 450 comprises a first and second hot swap controller 305, a DC/DC converter 300, a first and second power meter 310, a first and second power manager 320, an operating circuit 330 and an operating circuit 460 comprising a plurality of PoE managing circuits 470. In an exemplary embodiment each PoE managing circuit 470 is attached to a number of ports, and some or all of the ports have attached thereto over twisted pair communication cabling a PD. Operating circuit 460 is shown as being a separate unit from power manager 320, however this is not meant to be limiting in any way. Power manager 320 may be incorporated into one or more of PoE managing circuit 470 without exceeding the scope of the invention. Power meter 310 is shown as being separate from power manager 320, however this is not meant to be limiting in any way, and power meter 310 may be integrated within power manager 320 without exceeding the scope of the invention. [00071] The plurality of power supplies 100 are connected together in a power sharing arrangement, such as droop or active current sharing, illustrated herein as a common shared bus, and each of PoE device 420; switch having on board power supply 200; and PoE enabled switch 450 exhibits a connection to the common shared bus via a respective hot swap controller 305. In the embodiment shown, a majority of power drawn is intended for PoE applications, and thus power supplies 100 are isolated from non-PoE operating circuit 330 and the chassis. Within each of switch having on board power supply 200 and PoE enabled switch 450, DC/DC converter 300 receives power from the common shared bus via the respective hot swap controller 305, and operates to isolate and convert the power to the appropriate voltage for use with respective operating circuit 330 in accordance with isolation requirements of IEEE 802.3af. A power meter 310 and a power manager 320 is respectively associated with each respective operating circuit 330, 460 and a respective power meter 310. The respective power manger 320 is arranged to receive an input from the respective power meter 310, to be in communication with management module 110, and to be in communication with the respective operating circuit 330, 460. The respective power meter 310 is arranged to provide the respective power manager 320 an indication of power drawn by respective operating circuit 330, 460. [00072] Switch having on board power supply 200 exhibits AC/DC converter
440 which receives AC mains power from AC mains connection 60. In an exemplary embodiment AC mains connection 60 comprises a connection through power strip 50 of Figs. 2 A, 2B. [00073] Respective status indicators 405 are each connected to an input of management module 110. In an exemplary embodiment each status indicator 405 comprises information regarding at least one of a power good signal of the respective power supply 100, a temperature of the respective power supply 100 and a stress level of the respective power supply 100. Status indicator 405 is illustrated as a separate data connection from each power supply 100, however this is not meant to be limiting in any way. In one embodiment the data connection is replaced with external sensors, and in another embodiment the data connection is part of a data bus arrangement. Each current indicator 410 from respective power supply 100 is illustrated as a separate data connection from each power supply 100, however this is not meant to be limiting in any way. In one embodiment the data connection is replaced with external sensors, and in another embodiment the data connection is part of a data bus arrangement.
[00074] A data connection is exhibited between management module 110 and each power manager 320. In one embodiment the data connection between management module 110 and each power manger 320 is accomplished in a high speed data bus, such as an EIA 485 as defined by the Electronic Industry Alliance of Arlington, Virginia. EIA 485 is also known as RS 485. In another embodiment the data connection between management module 110 and each power manager 320 comprises a pair of data busses: a first data bus being of a high speed, such as 1 Mbps, and carrying ongoing messages as will be described further hereinto below; and a second data bus being of a lower speed, such as 100 Kbps, and carrying emergency messages and addressing information as will be described further hereinto below. The second data bus is hereinto referred to as the emergency bus. In an exemplary embodiment the data connection between management module 110 and each power manager 320 is accomplished via a bi-directional single twisted wire pair bus in a ring configuration. In such an embodiment management module 110 observes the bus to ensure that messages sent by management module 110 have traveled the entire bus. In the event of a sensed communication failure, messages are optionally resent in the reverse direction thereby improving communication reliability.
[00075] In operation, the plurality of power supplies 100 operate in a power sharing arrangement to supply power to each of PoE device 420; switch having on board power supply 200; and PoE enabled switch 450. Status indicators 405 output status information regarding respective power supplies 100, and are received by management module 110. Current indicators 410 output information regarding the output current of respective power supplies 100, and are received by management module 110. Management module 110 is further operable to communicate with each power manger 320 of PoE device 420, switch having on board power supply 200 and PoE enabled switch 450 so as to communicate data regarding the priority and to allocate respective power budgets. In one embodiment management module 110 further receives data regarding the priority level of each port to which a PD requesting power may be attached. Advantageously management module 110 thus has available an overall map of all connected PoE devices, modules and their priorities, enabling power to be allocated according to priority irrespective of the PoE managing circuit 470 to which a port is connected. PoE managing circuits 470 operate under control of the respective power manager 320 to interrogate, optionally classify, and subsequently power connected PDs.
[00076] Management module 110 is operative in a manner that will be explained further hereinto below, to maintain a table of power scenarios indicative of potential states of the various status indicators 405. Thus, in the event of a failure of one or more power supply 100, management module 110 responsive to the change in the respective status indicator 405 is operable to look up the appropriate actions in the pre-stored power scenario table, and broadcast a scenario number to each power manager 320. The use of a look up table and pre-transmitted scenarios enables management module 110 and power managers 320 to react in sufficient time so as to reduce consumption thereby limiting the amount of time for which an overload condition may be present. [00077] Each power manager 320 is preferably operable to receive a power budget from management module 110 and to control the operation of the respective operating circuit 330, 460 in accordance with the received budget. Thus, power manager 320 functions as a local power budget supervisor. In another embodiment the priority is set by a user utilizing a host computer or controller communicating with management module 110. In a further embodiment, priority may be set by a user for each PoE port powered by a PoE managing circuit 470, management module 110 communicating the received priority setting to PoE managing circuit 470 via the respective power manger 320. In another embodiment (not shown), further described in co-filed patent application entitled "System for Providing Power over Ethernet through a Patch Panel" whose entire contents is incorporated herein by reference, at least one operating circuit 460 supplies power to PDs via a power ready patch panel and the PoE managing circuit 470 receives configuration information, including a priority level, from the power ready patch panel. In such an embodiment, PoE managing circuit 470 receiving priority laden information from the power ready patch panel shares the priority information with management module 110 via respective power manager 320.
[00078] Switch having on board power supply 200 receives power from an AC mains via AC mains connection 60. In the event that power drawn by operating circuit 330 is in excess of the power supplied by AC/DC converter 440, additional power may be drawn from the plurality of power supplies 100. Total power drawn is monitored by power manager 320 of switch having on board power supply 200, and in the event that additional power has been allocated by management module 110, allows operating circuit 330 to increase power drawn in excess of power available from AC/DC converter 440. Additionally, in the event of a failure of AC mains power, and in the event that a battery or other source of uninterruptible power is connected as a power supply 100, power may be drawn by operating circuit 330 in the absence of AC mains power. Preferably, in such an embodiment, power manager 320 acts to minimize power consumption of operating circuit 330. [00079] Fig. 4B is a high level block diagram of an embodiment of the data connection of Fig. 4A exhibiting a first and second data bus in accordance with the principle of the current invention comprising: a management module 110; a first and second PoE device 420; a power managed module 140; a first bus 520; and a second bus 530. Management module 110 comprises a control circuit 500, a first transceiver 510, a second transceiver 512, a third transceiver 514, and a fourth transceiver 516. Each of first and second PoE devices 420 comprises a first transceiver 518, a second transceiver 519 and a power manager 320. Power managed module 140 comprises a first transceiver 518, a second transceiver 519 and a power manager 320.
[00080] Control 500 is connected to the input of the transmitter of each of first, second, third and fourth transceiver 510, 512, 514, 516 of management module 110 and to the output of the receiver of each of first, second, third and fourth transceiver 510, 512, 514, 516 of management module 110. The output of the transmitter of first transceiver 510 of management module 110 is connected to the receiver of first transceiver 510 of management module 110 and by a portion of first bus 520 to both the output of the transmitter of first transceiver 518 of first PoE device 420 and the input of the receiver of first transceiver 518 of first PoE device 420. The output of the transmitter of second transceiver 512 of management module 110 is connected to the receiver of second transceiver 512 of management module 110 and by a portion of second bus 530 to both the output of the transmitter of second transceiver 519 of first PoE device 420 and the input of the receiver of second transceiver 519 of first PoE device 420. [00081] Power manager 320 of first PoE device 420 is connected to the output of the receiver of first transceiver 518 of first PoE device 420, to the input of the transmitter of first transceiver 518 of first PoE device 420, to the output of the receiver of second transceiver 519 of first PoE device 420, and to the input of the transmitter of second transceiver 519 of first PoE device 420. The output of the transmitter of first transceiver 518 of first PoE device 420 is connected by a portion of first bus 520 to both the output of the transmitter of first transceiver 518 of second PoE device 420 and the input of the receiver of first transceiver 518 of second PoE device 420. The output of the transmitter of second transceiver 519 of first PoE device 420 is connected by a portion of second bus 530 to both the output of the transmitter of second transceiver 519 of second PoE device 420 and the input of the receiver of second transceiver 519 of second PoE device 420.
[00082] Power manager 320 of second PoE device 420 is connected to the output of the receiver of first transceiver 518 of second PoE device 420, to the input of the transmitter of first transceiver 518 of second PoE device 420, to the output of the receiver of second transceiver 519 of second PoE device 420, and to the input of the transmitter of second transceiver 519 of second PoE device 420. The output of the transmitter of first transceiver 518 of second PoE device 420 is connected by a portion of first bus 520 to both the output of the transmitter of first transceiver 518 of power managed module 140, and the input of the receiver of first transceiver 518 of power managed module 140. The output of the transmitter of second transceiver 519 of second PoE device 420 is connected by a portion of second bus 530 to both the output of the transmitter of second transceiver 519 of power managed module 140 and the input of the receiver of second transceiver 519 of power managed module 140. [00083] Power manager 320 of power managed module 140 is connected to the output of the receiver of first transceiver 518 of power managed module 140, to the input of the transmitter of first transceiver 518 of power managed module 140, to the output of the receiver of second transceiver 519 of power managed module 140, and to the input of the transmitter of second transceiver 519 of power managed module 140. The output of the transmitter of first transceiver 518 of power managed module 140 is connected by a portion of first bus 520 to both the output of the transmitter of third transceiver 514 of management module 110 and the input of the receiver of third transceiver 514 of management module 110. The output of the transmitter of second transceiver 519 of power managed module 140 is connected by a portion of second bus 530 to both the output of the transmitter of fourth transceiver 516 of management module 110 and the input of the receiver of fourth transceiver 516 of management module 110. In an exemplary embodiment each of transceivers 510, 512, 514, 516, 518, 519 operate according to EIA-485, and in a preferred embodiment first and second transceiver 510, 512 operate as the master for first and second buses 520, 530 respectively.
[00084] In operation first bus 520 and second bus 530 are connected in a daisy chain or ring arrangement, exhibiting internal direct connections in each of first, and second PoE devices 420 and power managed module 140, and first bus 520 and second bus 530 loop back to management module 110. Thus, first bus 520 and second bus 530 are operational irrespective of the operation of each of first and second PoE devices 420 and power managed module 140. Control 500 is operational to communicate ongoing messages to and from each of first and second PoE devices 420 and power managed module 140 via first transceiver 510 and first bus 520, and to further receive the transmitted messages via third transceiver 514 and the loop back path of first bus 520. Control 500 is further operational to communicate emergency messages to each of first and second PoE devices 420 and power managed module 140 via second transceiver 512 of management module 110 and second bus 530, and to further receive the transmitted emergency messages via fourth transceiver 516 of management module 110 and the loop back path of second bus 530. [00085] Advantageously, control 500 monitors the loop back path of first bus
520, and in the event that messages transmitted by control 500 via first transceiver 510 of management module 110 are not received at third transceiver 514 of management module 110, control 500 is operational to notify a user of a communication break. Control 500 is further operational to retransmit messages not received at third transceiver 514 of management module 110 via third transceiver 514 of management module 110 via the loop back path. Thus, third transceiver 514 of management module 110 acts as a master for the portion of first bus 520 still connected to third transceiver 514 of management module 110 via the loop back path and first transceiver 510 of management module 110 acts as a master for the portion of first bus 520 connected to first transceiver 510 of management module 110, also called hereinafter the main path. Thus, first and second PoE devices 420 and power managed module 140 are in communication with management module 110 despite a break in first bus 520. In one embodiment control 500 further polls each of first and second PoE devices 420 and power managed module 140 via each of the main and loop back paths of first bus 520, and reports to a user an identifier of which PoE device 420 and power managed module 140 remain connected to each of the main and loop back paths of first bus 520. [00086] Advantageously, control 500 monitors the loop back path of second bus 530, and in the event that messages transmitted by control 500 via second transceiver 512 of management module 110 are not received at fourth transceiver 516 of management module 110, control 500 is operational to notify a user of a communication break. Control 500 is further operational to retransmit messages not received at fourth transceiver 516 of management module 110 via fourth transceiver 516 of management module 110 via the loop back path. Thus, fourth transceiver 516 of management module 110 acts as a master for the portion of second bus 530 still connected to fourth transceiver 516 of management module 110 via the loop back path and second transceiver 512 of management module 110 acts as a master for the portion of second bus 530 connected to second transceiver 512 of management module 110, also called hereinafter the main path. Thus, first and second PoE devices 420 and power managed module 140 are in communication with management module 110 despite a break in second bus 530. In one embodiment control 500 further polls each of first and second PoE device 420 and power managed module 420 via each of the main and loop back paths of second bus 530, and reports to a user an identifier of which PoE device 420 and power managed module 140 remain connected to each of the main and loop back paths of second bus 530. [00087] Preferably, second bus 530 is held open to be available for time sensitive messages to be sent by control 500, and no time is lost by control 500 regaining control of second bus 530 due to communication from one of first and second PoE devices 420 and power managed module 140. [00088] Fig. HA is a high level flow chart of the operation of management module 110 of Fig. 4B to communicate via a main path of first bus 520, and in the event of the transmitted message not being detected via the loop back path of first bus 520, retransmitting the message via the loop back path of first bus 520 in accordance with the principle of the current invention. In stage 5000, a message is transmitted via the main path of the first bus to a destination address, for example by utilizing first transceiver 510 of management module 110. Management module 110 preferably acts as the bus master and assigns addresses to each of first and second PoE devices 420, power managed module 140 and other devices found attached thereto. [00089] In stage 5010, control 500 monitors the loop back path of first bus 520, for example via third transceiver 514 of management module 110. In the event that the message transmitted in stage 5000 is received via the loop back path, the communication ring of the first bus is intact, and in stage 5020 the routine returns. [00090] In the event that in stage 5010 the message transmitted in stage 5000 is not received via the loop back path, indicating that the communication ring of first bus 520 is not intact, in stage 5030 the message of stage 5000 is retransmitted via the loop back path of first bus 520, for example by utilizing third transceiver 514 of management module 110. Thus, first and second PoE devices 420, power managed module 140, and other devices, which remain connected to management module 110 via the loop back path of first bus 520, receive communication irrespective of the break in first bus 520.
[00091] In optional stage 5040, devices are polled via the main path of first bus
520, and units responding are identified as connected via the main path to management module 110. In optional stage 5050, devices are polled via the loop back path of first bus 520, and units responding are identified as connected via the loop back path to management module 110. In stage 5060, management module 110 notifies a user of the communication break. In optional stage 5070, identifiers of units identified in optional stages 5040, 5050 are further communicated to the user, thus indicating further information as to the location of the break. In stage 5020 the routine returns.
[00092] Fig. HB is a high level flow chart of the operation of management module 110 of Fig. 4B to broadcast emergency messages via a main path of second bus 530, and in the event of the broadcast message not being detected via the loop back path of second bus 530, rebroadcasting the message via the loop back path of second bus 530 in accordance with the principle of the current invention. In stage 6000, an emergency message is broadcast via the main path of the second bus to a destination address, for example by utilizing second transceiver 512 of management module 110. Management module 110 preferably acts as the bus master and assigns addresses to each of firs and second PoE devices 420, power managed module 140 and or other devices found attached thereto.
[00093] In stage 6010, control 500 monitors the loop back path of second bus
530, for example via fourth transceiver 516 of management module 110. In the event that the message broadcast in stage 6000 is received via the loop back path, the communication ring of the second bus is intact, and in stage 6020 the routine returns. [00094] In the event that in stage 6010 the emergency message broadcast in stage 6000 is not received via the loop back path, indicating that the communication ring of second bus 530 is not intact, in stage 6030 the emergency message of stage 6000 is rebroadcast via the loop back path of second bus 530, for example by utilizing fourth transceiver 516 of management module 110. Thus, first and second PoE devices 420, power managed module 140, and other devices which remain connected to management module 110 via the loop back path of second bus 530, receive emergency broadcast messages irrespective of the break in second bus 530. [00095] In optional stage 6040, devices are polled via the main path of second bus 530, and units responding are identified as connected via the main path to management module 110. In optional stage 6050, devices are polled via the loop back path of second bus 530, and units responding are identified as connected via the loop back path to management module 110. hi stage 6060, management module 110 notifies a user of the communication break. In option stage 6070, identifiers of units identified in optional stages 6040, 6050 are further communicated to the user, thus indicating further information as to the location of the break. In stage 6020 the routine returns. [00096] The routines of Fig. HA and HB have been explained with second bus 530 being utilized for broadcast of emergency messages, and first bus 520 being utilized for ongoing communication; however this is not meant to be limiting in any way. Second bus 530 may be utilized to assign addresses for use by first bus 520 without exceeding the scope of the invention. First bus 520 and second bus 530 may proceed in a single cable, and thus a break in one of first bus 520 and second bus 530 may most likely be indicative of a break in a second one of first bus 520 and second bus 530 without exceeding the scope of the invention.
[00097] Fig. 5 illustrates a high level flow chart of an embodiment of the operation of management module 110 of Figs. 4A, 4B to allocate power equally to all power managed modules in accordance with the principle of the current invention. In stage 1000 the power requirements of all attached modules are input. In an exemplary embodiment, a minimum and a desired power requirement are supplied by the local power manager 320. It is to be understood that in this embodiment, power manager 320 draws power irrespective of an allocated or non-allocated power budget for the associated operating circuitry 330, 460. In another embodiment, power requirements are supplied by a user utilizing a host computer or controller communicating with management module 110. It is further understood, that in the event that an unmanaged module is attached which draws power from power supplies 100, the power drawn by the unmanaged module is to be input by a user utilizing a host computer or controller communicating with management module 110. The input power drawn for the unmanaged module is to be deducted from any available power budget, since the unmanaged module can not reduce consumption in response to management module 110. [00098] In stage 1010 information regarding the total available power for the modules whose power requirements were input in stage 1000 is input. In an exemplary embodiment status information 405 in combination with current indicator 410 provides information regarding power availability. In another embodiment a host controller or computer is operable by a user to input a rated power capability of each power supply 100 exhibiting a power good signal via status information 405. In one embodiment the rated power is discounted by an estimate of the power usage of management module 110 and other inherent losses in the system including power used by each power manager 320. In another embodiment the rated power is further discounted by inherent losses of each DC/DC converter 300. In another embodiment a maximum power usage to be allocated for non-power managed modules attached to rack and drawing power from power supplies 100 is input in stage 1000 and deducted in stage 1010. In another embodiment the power usage reported by power manger 320 for operating circuit 460 comprises power allocated by a PoE managing circuit 470 due to classification irrespective as to the amount of power actually drawn by a PD.
[00099] In stage 1020 a power budget is allocated for each module whose power requirements were input in stage 1000 on an equal basis. In one embodiment, in the event that the desired power requirement as input in stage 1000 is fully met, no additional power is allocated to the module, and the balance of the available power is thus allocated to other modules. In another embodiment power is allocated as a percentage of the desired power requirements, and thus power is budgeted equally on a pro-rata basis of the maximum desired power. The above embodiments are not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget. The power budgets determined are transmitted to power managers 320 of each of the modules.
[000100] In stage 1030 power availability as indicated by status information 405 in combination with current indicator 410 is continuously monitored and the dynamically changing power requirements of the modules are again input. It is to be understood that the power requirement of the modules may change on a dynamic basis, for example if one module comprises a PoE device, the addition or removal of a PD changes the power requirements associated with the PoE device to which it is connected, or from which it has been removed. [000101] In stage 1040 the dynamically variable power requirements are compared with the continuously updated power availability. In the event that in stage 1040, sufficient power is available for all modules, stage 1020 as described above is executed. It is to be understood that additional power may be allocated, or budgeted, to at least one attached module without affecting the operation of other modules, as sufficient power has been determined to be available from power supplies 100. [000102] In the event that in stage 1040, sufficient power is not available for all modules, in stage 1050 power is reallocated to all attached modules. It is to be understood that at least one module may have its power budget reduced. Power is reallocated for each module on an equal basis. In one embodiment, in the event that the dynamic desired power requirement of a module as input in stage 1030 is fully met, no additional power is allocated to the module, and the balance of the available power is thus allocated to other modules. In another embodiment power is allocated as a percentage of the dynamic desired power requirements, and thus power is budgeted equally on a pro-rata basis of the maximum desired power. The above embodiments are not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget. The power budgets determined are transmitted to power managers 320 of each of the modules. Preferably reallocation according to stage 1050 is in accordance with the same method used for allocation in stage 1020. After the operation of stage 1050, stage 1030 as described above is again executed.
[000103] The method of Fig. 5 is preferably run at start up, and further preferably the loop of stages 1020 - 1050 is run continuously, or on a periodic basis, or in response to a sensed change in one of the dynamic power requirements and the power availability.
[000104] Fig. 6 illustrates a high level flow chart of an embodiment of the operation of management module 110 of Figs. 4A5 4B to allocate power according to priority to power managed modules in accordance with the principle of the current invention, hi stage 1100 the power requirements and priority levels of all attached modules are input. In an exemplary embodiment, a minimum and a desired power requirement are supplied by the local power manager 320. It is to be understood that in this embodiment, power manager 320 draws power irrespective of an allocated or non-allocated power budget for the associated operating circuitry 330, 460. In another embodiment, at least one of power requirements and priority levels are supplied by a user utilizing a host computer or controller communicating with management module 110. It is further understood, that in the event that an unmanaged module is attached which draws power from power supplies 100, the power drawn by the unmanaged module is to be input by a user utilizing a host computer or controller communicating with management module 110. The input power drawn for the unmanaged module is to be deducted from any available power budget, since the unmanaged module can not reduce consumption in response to management module 110. [000105] In stage 1110 information regarding the total available power for the modules whose power requirements were input in stage 1100 is input. In an exemplary embodiment status information 405 in combination with current indicator 410 provides information regarding power availability. In another embodiment a host controller or computer is operable by a user to input a rated power capability of each power supply 100 exhibiting a power good signal via status information 405. In one embodiment the rated power is discounted by an estimate of the power usage of management module 110 and other inherent losses in the system including power used by each power manager 320. In another embodiment the rated power is further discounted by inherent losses of each DC/DC converter 300. In another embodiment a maximum power usage to be allocated for non-power managed modules attached to rack and drawing power from power supplies 100 is input in stage 1100 and deducted in stage 1110. In another embodiment the power usage reported by power manger 320 for operating circuit 460 comprises power allocated by a PoE managing circuit 470 due to classification irrespective as to the amount of power actually drawn by a PD.
[000106] In stage 1120 a power budget is allocated for each module whose power requirements were input in stage 1100 in accordance with priority. Power requirements of modules exhibiting high priority receive a power allocation up to the power requirements prior to power being allocated to modules of a lower priority. In one embodiment power is allocated on an equal basis to modules of the same priority or as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the maximum desired power. The above is not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget. The power budgets determined are transmitted to power managers 320 of each of the modules. Once power has been allocated to the highest priority modules, power is allocated to lower priority modules in a similar fashion. [000107] The above has been described as having modules with priority, however this is not meant to be limiting in any way. In one embodiment, a module may have a minimum operating requirement at a high priority, with additional power requirements at a lower priority. Thus, the module will almost always receive a minimum operating power level, and in the event of additional power be supplied with an additional power allocation.
[000108] In stage 1130 power availability as indicated by status information 405 in combination with current indicator 410 is continuously monitored and the dynamically variable power requirements of the modules are again input. It is to be understood that the power requirement of the modules may change on a dynamic basis, for example if one module comprises a PoE device, the addition or removal of a PD changes the power requirements associated with the PoE device to which it is connected, or from which it has been removed.
[000109] In stage 1140 the dynamically variable power requirements are compared with the continuously update power availability. In the event that in stage 1140, sufficient power is available for all modules, stage 1120 as described above is executed. It is to be understood that additional power may be allocated, or budgeted, to at least one attached module without affecting the operation of other modules, as sufficient power has been determined to be available from power supplies 100. [000110] In the event that in stage 1140, sufficient power is not available for all modules, in stage 1150 power is reallocated to all attached modules. It is to be understood that at least one module may have its power budget reduced. Power is reallocated for each module in accordance with priority. Power requirements of modules exhibiting high priority receive a power allocation up to the power requirements prior to power being allocated to modules of a lower priority. In one embodiment power is reallocated on an equal basis to modules of the same priority or as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the maximum desired power. The above is not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to reallocate a power budget. The power budgets determined are transmitted to power managers 320 of each of the modules. Once power has been allocated to the highest priority modules, power is reallocated to lower priority modules in a similar fashion. [000111] Preferably reallocation according to stage 1150 is in accordance with the same method used for allocation in stage 1120. After the operation of stage 1150, stage 1130 as described above is again executed.
[000112] The method of Fig. 6 is preferably run at start up, and further preferably the loop of stages 1120 - 1150 is run continuously, or on a periodic basis, or in response to a sensed change in one of the dynamic power requirements and the power availability.
[000113] Fig. 7 illustrates a high level flow chart of an embodiment of the operation of the management module 110 of Figs. 4A, 4B to allocate a minimum power level to all power managed modules, and to allocate any additional available power according to priority in accordance with the principle of the current invention. In stage 1200 the power requirements comprising a minimum and a desired power requirement and priority levels of all attached modules are input. In an exemplary embodiment, the minimum and desired power requirements are supplied by the local power manager 320. It is to be understood that in this embodiment, power manager 320 draws power irrespective of an allocated or non-allocated power budget for the associated operating circuitry 330, 460. In another embodiment, at least one of power requirements and priority levels are supplied by a user utilizing a host computer or controller communicating with management module 110. It is further understood, that in the event that an unmanaged module is attached which draws power from power supplies 100, information regarding the power drawn by the unmanaged module is to be input by a user utilizing a host computer or controller communicating with management module 110. The input power drawn for the unmanaged module is to be deducted from any available power budget, since the unmanaged module can not reduce consumption in response to management module 110. [000114] In stage 1210, information regarding the total available power for the modules whose power requirements were input in stage 1200 is input. In an exemplary embodiment status information 405 in combination with current indicator 410 provides information regarding power availability. In another embodiment a host controller or computer is operable by a user to input a rated power capability of each power supply 100 exhibiting a power good signal via status information 405. In one embodiment the rated power is discounted by an estimate of the power usage of management module 110 and other inherent losses in the system including power used by each power manager 320. In another embodiment the rated power is further discounted by inherent losses of each DC/DC converter 300. In another embodiment a maximum power usage to be allocated for non-power managed modules attached to rack and drawing power from power supplies 100 is input in stage 1200 and deducted in stage 1210. In another embodiment the power usage reported by power manger 320 for operating circuit 460 comprises power allocated by a PoE managing circuit 470 due to classification irrespective as to the amount of power actually drawn by a PD.
[000115] In stage 1220 a minimum power budget is allocated for each module whose minimum power requirements were input in stage 1200 equally. In another embodiment power is allocated on an equal basis to all modules up to the minimum power requirement as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the minimum required power. The above embodiments are not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget. In one embodiment, minimum power allocation is done in order of priority. The power budgets determined are transmitted to power managers 320 of each of the modules.
[000116] In stage 1230 additional available power, in excess of the power allocated in stage 1220, is allocated for each module whose power requirements were input in stage 1200 in accordance with priority. Power requirements of modules exhibiting high priority receive a power allocation up to the power requirements prior to power being allocated to modules of a lower priority. In one embodiment power is allocated on an equal basis to modules of the same priority or as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the maximum desired power. The above is not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to allocate a power budget. The additional power budgets determined are transmitted to power managers 320 of each of the modules. Once power has been allocated to the highest priority modules, power is allocated to lower priority modules in a similar fashion.
[000117] In stage 1240 power availability as indicated by status information 405 in combination with current indicator 410 is continuously monitored and the dynamically variable power requirements of the modules are again input. It is to be understood that the power requirement of the modules may change on a dynamic basis, for example if one module comprises a PoE device, the addition or removal of a PD changes the power requirements associated with the PoE device to which it is connected, or from which it has been removed. [000118] In stage 1250 the dynamically variable power requirements are compared with the continuously update power availability. In the event that in stage 1250 sufficient power is available for all modules, stages 1230 and 1240 as described above is executed. It is to be understood that additional power may be allocated, or budgeted, to at least one attached module without affecting the operation of other modules, as sufficient power has been determined to be available from power supplies 100.
[000119] In the event that in stage 1250 sufficient power is not available for all modules, in stage 1260 power is reallocated to all attached modules. It is to be understood that at least one module may have its power budget reduced. Power is reallocated for each module in accordance with priority, with a minimum required power being first allocated to all modules. Power requirements of modules exhibiting high priority receive a power allocation up to the power requirements prior to power being allocated to modules of a lower priority. In one embodiment power is reallocated on an equal basis to modules of the same priority or as a percentage of the desired power requirements, and thus power is budgeted equally to modules of the same priority on a pro-rata basis of the maximum desired power. The above is not meant to be limiting in any way and are specifically meant to include utilizing a combination of factors to reallocate a power budget. The power budgets determined are transmitted to power managers 320 of each of the modules. Once power has been allocated to the highest priority modules, power is reallocated to lower priority modules in a similar fashion. [000120] Preferably reallocation according to stage 1260 is in accordance with the same method used for allocation in stages 1220 and 1230. After the operation of stage 1260, stage 1240 as described above is again executed.
[000121] The method of Fig. 7 is preferably run at start up, and further preferably the loop of stages 1230 - 1260 is run continuously, or on a periodic basis, or in response to a sensed change in one of the dynamic power requirements and the power availability.
[000122] Fig. 8 is a high level flow chart of an ongoing operation of management module 110 of Figs. 4A, 4B to maintain a potential scenario chart comprising power budgets for each power managed module according to an aspect of the invention. In stage 2000 power consumption of all attached modules is input. While stage 2000 has been described as inputting power consumption, this is not meant to be limiting in any way. A minimum power requirement, or a plurality of power requirements and priorities, or an allocated power which may be called upon but not utilized, may be input without exceeding the scope of the invention. In one embodiment management module 110 communicates with each power manager 320 and receives an indication of power consumption. In another embodiment power consumption is input based on current indicator 410 of power supplies 100. [000123] In stage 2010 for each power source scenario a power budget for each module is determined. In an exemplary embodiment a power supply scenario is defined as the loss of one or more of the plurality of power supplies 100 of Fig. 4A. In the event that all of the plurality of power supplies 100 are of the same rating, only a single scenario for each number of remaining power sources is required. In the event that some or all of the plurality of power supplies 100 exhibit different power ratings, each potential total power output of the plurality of power supplies 100 for which one of the power supplied have failed is taken as a potential scenario. For each of the potential scenarios a revised power budget is calculated for each module. Preferably, the power budget determined is in accordance with stage 1050 of Fig. 5, 1150 of Fig. 6 or 1260 of Fig. 7. Thus, while the operation of respective stages 1050, 1150 and 1260 are in response to small changes in power availability or power demand, the operation of stage 2010 develops a potential action for each potential power source scenario. [000124] Stage 2010 will be described herein as being responsive to status indicator 405 of each power supply having a binary value in which a value of 1 indicates full rated power availability and a value of 0 indicates no power. This is not meant to be limiting in any way, and a multiplicity of values, including derating due to an increased temperature or stress level is specifically intended. [000125] Table I is a representation of an embodiment of the potential scenario chart produced as an outcome of stage 2010 in accordance with the principle of the invention.
Table I
Figure imgf000038_0001
[000126] For each possible combination of power indicators 405 a total power available is determined and a scenario number is assigned. A total scenario available power is determined and a power budget per module is determined. Table I is described as assigning an equal power budget to each module, as described above in relation to Fig. 5, however this is not meant to be limiting in any way. A scenario power budget may be based on a minimum power requirement, a percentage of current power usage as input in stage 2000, or take priority into account without exceeding the scope of the invention. In one embodiment power is budgeted for all high priority power requirements first, and then subsequent power requirements of lower priority are budgeted.
[000127] In stage 2020 the scenarios associated with the power budget for each scenario is transmitted to each of the power managers 320 of the respective attached modules. In the event of a change in the value of power indicator 405 of one of power supplies 100, management module 110 will operate to broadcast the scenario number to change to in a manner that will be further described below. In one embodiment the broadcast is done on the provided emergency bus as described above in relation to Figs. 4A, 4B, 1 IA and 1 IB. [000128] Thus, the routine of Fig. 8 prepares and transmits potential power event scenarios to each connected power manager 320 associated with a potential power budget for each of the scenarios. Preferably the routine of Fig. 8 is run on a periodic basis, maintaining an update scenario chart so that failure of one or more power supplies 100 may be responded to rapidly by reducing power drawn, thereby preventing a total system crash due to overload of the remaining power supplies 100. [000129] Fig. 9 is a high level flow chart of the operation of the management module 110 of Figs. 4A, 4B in accordance with the principle of the current invention, in the event of a change in power condition associated with one or more power sources. In stage 3000 a change in power status indicator is sensed. As described above, the power status indicator in one embodiment presents a binary value indicating either full or no power, and in another embodiment presents a plurality of values indicative of a need to derate the power supply 100 associated with the status indicator 405. In stage 3010 the table generated in stage 2010 of Fig. 8 is retrieved from memory, and the scenario number associated with the current status indicators 405 is retrieved. In stage 3020 the scenario number retrieved in stage 3010 is broadcast to all power managers 320. In one embodiment the scenario number is broadcast on the provided emergency bus as described above in relation to Figs. 4A, 4B, 1 IA and 1 IB. It is to be understood that power mangers 320, upon receipt of the broadcast immediately acts to update the power drawn to the amount received in stage 2020 of Fig. 8. In an embodiment of a PoE operating circuitry, such as operating circuitry 460 of Fig. 4A, each PoE managing circuit 470 is instructed to disable ports if required, preferably observing local priority, to achieve the revised local power budget. In an embodiment of operating circuitry 330 of Fig. 4A, power manager 320 reduces power drawn, by reducing the clock speed or shedding other loads. [000130] The above has been described in relation to management module 110 transmitting power budgets for each potential scenario, however this is not meant to be limiting in any way. Alternatively, management module 110 may transmit an allocation reduction to each power manager for each scenario without exceeding the scope of the invention. In such an embodiment, responsive to the broadcast message of stage 3020, each power manager 320 is operative to reduce power drawn by the pre-transmitted amount in accordance with the scenario broadcast received. [000131] In stage 3030 total power consumption, preferably as determined by current indicators 410 of Fig. 4 A, is monitored to ensure that power has stabilized such that the rate of change of total power consumption is less than the a predetermined limit. In an exemplary embodiment stage 3030 is implemented using fuzzy logic. In the event that total power consumption has not stabilized stage 3030 is repeated. In the event that in stage 3030 total power consumption has stabilized, in stage 3040 a reallocation routine as described above in relation to Figs. 5 - 7 is called. Thus, the operation of stage 3020 results in a rapid reduction of power drawn, and stage 3030 allows for stabilization at the reduced power allocatoins. Reallocation in accordance with stages 1030 - 1050 of Fig. 5, 1130 - 1150 of Fig. 6 or 1240 - 1260 of Fig. 7 fine tunes the system in accordance with the available power.
[000132] Stage 3030 is described herein as observing the rate of change of total power consumption, however this is not meant to be limiting in any way. Stage 3030 may be replaced with a stage awaiting confirmation from each of the plurality of power managers 320 that power drawn is within budget, or with a fixed delay, without exceeding the scope of the invention.
[000133] The implementation of the methods of Figs. 8 and 9, as described above in relation to Table I, thus enable a pre-planned power reduction for power managed devices in the event that any change to the power source condition occurs. The table is updated regularly according to the method of Fig. 8, and represents a list of scenarios and allocated power budgets for each power managed device in the event that the power source condition changes from the current power source condition, to any other condition. [000134] Fig. 10 is a high level flow chart of the operation of a power manager 320 to automatically detect a reduced power availability, and in response reduce power consumption in accordance with the principle of the current invention. In stage 4000 the voltage at the power managed device is monitored and a reduced voltage is detected. Such a reduced voltage is indicative of an overload condition. In the event that communication with management module 110 was in operation, a reduced power budget for one or more power managers 320 would be transmitted by management module 110. [000135] Power manager 320, in response to a sensed reduction in voltage in stage 4000, and in the absence of communication with management module 110, in stage 4010 reduces power consumption. In an exemplary embodiment power manager 320 communicates with a respective operating circuit 330, 460 to reduce power consumption by a pre-determined amount or percentage. In another embodiment, power is consumed in levels or stages, and power is reduced to the next lower level.
[000136] In stage 4020, voltage at the power managed device is again monitored. In the event that voltage has stabilized within tolerance, in stage 4030 the power allocation is maintained for operating circuit 330, 460 in accordance with the reduced setting of stage 4010. Thus, the reduced setting is treated as a revised power budget in the absence of communication with management module 110.
[000137] In the event that in stage 4020 voltage has not stabilized to be within tolerance, stage 4010 is again run to further reduce power drawn. It is to be understood that preferably the operation of stage 4010 does not reduce power below a minimum operating level. [000138] Thus, the present embodiments enable a system having at least one power source, a management module and a plurality of power managed modules in communication with the management module. Each of the power managed modules are arranged to be able to draw at least some power from the at least one power source. Each of the power managed modules comprises a power manager operable to control the power drawn by the power managed module. The management module allocates a power budget for each of the power managed modules, and the power managers of the power managed modules operate to control module operation so that power drawn is within the allocated budget. [000139] Power managed modules may comprise PoE devices, switches, hubs, concentrators, computing equipment or other telecommunication modules operable at a plurality of power levels. Power managed modules may be supplied with an on board power supply, or preferably without an on board power supply. A central power source, preferably comprising at least one power supply, and further preferably comprising a plurality of power supplies, thus optimally supplies operating power for some or all of the power managed modules within the rack. The management module allocates power for each of the power managed modules drawing power. [000140] The power budget is dynamically allocated based on pre-defined criteria. In the event of a failure of one or more power supplies of the central power source, in one embodiment the management module directs each of the power managed modules to change their power consumption to a pre-assigned amount. In another embodiment, in the event of a failure of one or more power supplies, the management module directs each of the power managed modules to reduce their power consumption by a pre-assigned amount.
[000141] In one embodiment, the power manager of at least one power managed module may sense a change in a voltage level from the at least one power source, and in response reduce power consumption. Such a response enables automatic power management by the power manager in the absence of communication from the management module.
[000142] In one embodiment the central power source comprises a plurality of power supplies, arranged in an N + M redundant arrangement. The management module reserves the power of M redundant power supplies so as to provide the budgeted power in the absence of one or more failed power supplies. The invention thus provides chassis functionality for distributed rack level equipment.
[000143] In one embodiment the system provides a plurality of buses, a first bus of which is used for ongoing communication of power requirements and budgets, and a second bus being used for emergency communication, such as in the event of a failure of at least one power supply of the central power source. A plurality of scenarios are generated and pre-transmitted to the modules, preferably over the first bus. In the event of a power event, such as the failure of one or more power supplies, one of the scenarios is implemented by broadcasting an implementing message, preferably over the second bus. Further preferably, at least one of the first and second bus is arranged in a closed ring configuration, thus allowing for identifying a communication breakdown by monitoring a loop back path.
[000144] It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination.
[000145] Unless otherwise defined, all technical and scientific terms used herein have the same meanings as are commonly understood by one of ordinary skill in the art to which this invention belongs. Although methods similar or equivalent to those described herein can be used in the practice or testing of the present invention, suitable methods are described herein.
[000146] All publications, patent applications, patents, and other references mentioned herein are incorporated by reference in their entirety. In case of conflict, the patent specification, including definitions, will prevail. In addition, the materials, methods, and examples are illustrative only and not intended to be limiting.
[000147] It will be appreciated by persons skilled in the art that the present invention is not limited to what has been particularly shown and described hereinabove. Rather the scope of the present invention is defined by the appended claims and includes both combinations and subcombinations of the various features described hereinabove as well as variations and modifications thereof which would occur to persons skilled in the art upon reading the foregoing description and which are not in the prior art.

Claims

C L A I M S We claim:
1. A system for rack level power management, the system comprising: at least one power source; a management module; and a plurality of power managed modules in communication with said management module and connected to draw power from said at least one power source, each of said plurality of power managed modules comprising a power manager and an operating circuit, said operating circuit being operable at a plurality of power drawing levels responsive to said power manager, said management module being operative to allocate a power budget to each of said plurality of power managed modules and communicate said allocated power budgets to said power managers, each of said power managers being operative to control said operating circuit of said power managed module to be operable at a power drawing level within said allocated budget.
2. A system according to claim 1, wherein said management module is connected to receive an indication of power availability from said at least one power source, said power budgets being allocated responsive said received indication.
3. A system according to any of claims 1 and 2, wherein said management module is operative to allocate power budgets on the basis of priority, each of said power managed modules being assigned a priority.
4. A system according to any of claims 1 - 3, wherein said plurality of power managed modules exhibits a minimum required power and an additional power level in excess of said minimum required power, said management module being operative to assign a power budget for said minimum required power for each of said plurality of power managed modules, and in the event that additional power is available, to allocate a power budget for said additional power level of at least one of said plurality of power managed modules.
5. A system according to claim 4, wherein said power budget for said additional power level is allocated on a priority basis.
6. A system according to any of claims 1 - 5, wherein each of said plurality of power managers comprises a power meter, said power manager of each of said plurality of power managers receiving an indication of power drawn from said power meter.
7. A system according to any of claims 1 - 6, wherein at least one of said plurality of power managed modules is selected from the group consisting of power over a Ethernet enabled switch, a switch, a hub, a concentrator, a computing equipment, a power sourcing device, and a telecommunication module.
8. A system according to any of claims 1 - 7, wherein said operating circuit of at least one of said plurality of power managed modules comprises a power sourcing device operable for use with a power ready patch panel.
9. A system according to any of claims 1 - 8, wherein said at least one power source and said management module are comprised within a single equipment shelf.
10. A system according to any of claims 1 - 9, wherein said management module is further operative to input a total power available, said allocated power budgets being responsive to said input total available power.
11. A system according to claim 10, further comprising at least one module not comprising a power manager, said management module being operative to reduce the power requirements of said at least one module from said input total available power.
12. A system according to any of claims 1 - 11, wherein said management module is further operative to transmit at least one power budget scenario, said management module being further operative to monitor a condition of said at least one power source, and in the event of a change in said monitored condition, to broadcast a command to said plurality of power managed modules, said plurality of power managed modules being operative to adhere to said at least one power budget scenario responsive to said broadcast command.
13. A system according to claim 12, further comprising a first bus and a second bus, wherein said management module is operative to transmit said at least one power budget scenario via said first bus and to broadcast said command via said second bus.
14. A system according to claim 12, wherein at least one of said first bus and said second bus in arranged in a closed ring arrangement.
15. A system according to any of claims 1 - 12, further comprising at least one communication bus arranged in a closed ring configuration, said management module being operative to communicate said allocated power budgets via said at least one communication bus.
16. A system according to claim 15, wherein said management module is further operative to monitor a loop back of said at least one communication bus, and in the event that said communicated allocated power budgets are not received via said monitored loop back, to communicate said allocated power budgets via said loop back.
17. A system according to any of claims 1 - 16, wherein said power manager of at least one said plurality of power managed modules is further operative to sense a reduced voltage, and responsive to sensed reduced voltage to control said operating circuit associated with said power manager to reduce power drawn.
18. A method of rack level power management comprising: providing at least one power source; providing a plurality of power managed modules connected to draw power from said at least one power source; allocating a power budget to each of said provided plurality of power managed modules; and transmitting said allocated power budgets to said plurality of power managed modules, each of said power managed modules controlling said drawn power to be within said transmitted allocated power budget.
19. A method according to claim 18, further comprising: receiving an indication of power availability from said at least one power source, said allocating being responsive said received indication.
20. A method according to any of claims 18 - 19, wherein said allocating is at least partially on the basis of priority.
21. A method according to any of claims 18 - 20, wherein said provided plurality of power managed modules exhibit a minimum required power and an additional power level in excess of said minimum required power, said stage of allocating comprising: allocating said minimum required power for each of said plurality of power managed modules, and in the event that additional power is available, allocating a power budget for said additional power level of at least one of said plurality of power managed modules.
22. A method according to claim 21 , wherein said allocating a power budget for said additional power level is on a priority basis.
23. A method according to any of claims 18 - 22, further comprising for each of said plurality of provided power managed modules, receiving an indication of power drawn by said power managed module.
24. A method according to any of claims 18 - 23, wherein at least one of said provided plurality of power managed modules is selected from the group consisting of power over a Ethernet enabled switch, a switch, a hub, a concentrator, a computing equipment, a power sourcing device, and a telecommunication module.
25. A method according to any of claims 18 - 24, wherein at least one of said provided plurality of power managed modules comprises a power sourcing device operable for use with a power ready patch panel.
26. A method according to claim 18, further comprising: inputting a total power available, said allocating a power budget being responsive to said input total available power.
27. A method according to claim 26, further comprising: providing at least one module not receiving said transmitted allocated power budget; and deducting the power requirements of said at least one module from said input total available power.
28. A method according to any of claims 18 - 27, further comprising: monitoring a condition of said provided at least one power source; transmitting at least one power budget scenario to said provided plurality of power managed modules; and in the event of a change in said monitored condition, broadcasting a command to said plurality of power managed modules, said plurality of power managed modules adhering to said transmitted at least one power budget scenario responsive to said broadcast command.
29. A method according to any of claims 18 - 28, the method further comprising: at least one of said provided plurality of power managed modules sensing a reduced voltage; and responsive to sensed reduced voltage, reducing power drawn by said provided power managed module.
30. A method according to any of claim 18 - 29, further comprising: monitoring a loop back of said transmitted allocated power budgets; and in the event that at least one of said transmitted allocated power budgets is not sensed by said monitoring, retransmitting said not sensed power budget via said loop back.
31. A method according to claim 18, further comprising: monitoring a condition of said provided at least one power source; transmitting at least one power budget scenario to said provided plurality of power managed modules via first bus; and in the event of a change in said monitored condition, broadcasting a command to said plurality of power managed modules via a second bus different than said first bus, said plurality of power managed modules adhering to said at least one power budget scenario responsive to said broadcast command.
32. A system for rack level power management, the system comprising: at least one power source comprising a plurality of power supplies; a management module; and a plurality of power managed modules in communication with said management module and connected to draw power from said at least one power source, each of said plurality of power managed modules comprising a power manager and an operating circuit, said operating circuit being operable at a plurality of power drawing levels responsive to said power manager, said management module being operative to allocate a power budget to each of said plurality of power managed modules and communicate said allocated power budgets to said power managers, and being further operative to communicate a plurality of power scenarios and associated power budgets to said power managed modules, each of said power managers being operative to control said operating circuit of said power managed module to be operable at a power drawing level within said allocated budget, and in response to a communication from said management module to activate a scenario to control said operating circuit of said power managed module to be operable at a power drawing level within said power budget associated with said activated scenario.
PCT/IL2005/001135 2005-01-18 2005-10-31 Rack level power management WO2006077569A1 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US64400205P 2005-01-18 2005-01-18
US60/644,002 2005-01-18
US69519005P 2005-06-30 2005-06-30
US60/695,190 2005-06-30

Publications (1)

Publication Number Publication Date
WO2006077569A1 true WO2006077569A1 (en) 2006-07-27

Family

ID=35534923

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/IL2005/001135 WO2006077569A1 (en) 2005-01-18 2005-10-31 Rack level power management
PCT/IL2005/001136 WO2006077570A1 (en) 2005-01-18 2005-10-31 Rack level power management for power over ethernet

Family Applications After (1)

Application Number Title Priority Date Filing Date
PCT/IL2005/001136 WO2006077570A1 (en) 2005-01-18 2005-10-31 Rack level power management for power over ethernet

Country Status (2)

Country Link
TW (1) TWI436197B (en)
WO (2) WO2006077569A1 (en)

Cited By (57)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011139432A1 (en) * 2010-05-03 2011-11-10 Cisco Technology, Inc. Power-sharing network communications device
EP2394378A1 (en) * 2009-02-03 2011-12-14 Corning Cable Systems LLC Optical fiber-based distributed antenna systems, components, and related methods for monitoring and configuring thereof
US8108705B2 (en) * 2008-03-07 2012-01-31 Nec Corporation Power supplying device, power supply controlling method, power supply controlling program and network system
WO2012051227A1 (en) * 2010-10-13 2012-04-19 Ccs Technology, Inc. Local power management for remote antenna units in distributed antenna systems
WO2012051230A1 (en) * 2010-10-13 2012-04-19 Ccs Technology, Inc. Power management for remote antenna units in distributed antenna systems
US9112611B2 (en) 2009-02-03 2015-08-18 Corning Optical Communications LLC Optical fiber-based distributed antenna systems, components, and related methods for calibration thereof
US9160449B2 (en) 2010-10-13 2015-10-13 Ccs Technology, Inc. Local power management for remote antenna units in distributed antenna systems
US9178635B2 (en) 2014-01-03 2015-11-03 Corning Optical Communications Wireless Ltd Separation of communication signal sub-bands in distributed antenna systems (DASs) to reduce interference
US9184843B2 (en) 2011-04-29 2015-11-10 Corning Optical Communications LLC Determining propagation delay of communications in distributed antenna systems, and related components, systems, and methods
US9219879B2 (en) 2009-11-13 2015-12-22 Corning Optical Communications LLC Radio-over-fiber (ROF) system for protocol-independent wired and/or wireless communication
US9240835B2 (en) 2011-04-29 2016-01-19 Corning Optical Communications LLC Systems, methods, and devices for increasing radio frequency (RF) power in distributed antenna systems
US9247543B2 (en) 2013-07-23 2016-01-26 Corning Optical Communications Wireless Ltd Monitoring non-supported wireless spectrum within coverage areas of distributed antenna systems (DASs)
US9252874B2 (en) 2010-10-13 2016-02-02 Ccs Technology, Inc Power management for remote antenna units in distributed antenna systems
WO2016025489A1 (en) * 2014-08-12 2016-02-18 Avocent Huntsville Corp. System and method for rack over provisioning and intelligent power management
US9270374B2 (en) 2010-05-02 2016-02-23 Corning Optical Communications LLC Providing digital data services in optical fiber-based distributed radio frequency (RF) communications systems, and related components and methods
US9319138B2 (en) 2010-02-15 2016-04-19 Corning Optical Communications LLC Dynamic cell bonding (DCB) for radio-over-fiber (RoF)-based networks and communication systems and related methods
US9325429B2 (en) 2011-02-21 2016-04-26 Corning Optical Communications LLC Providing digital data services as electrical signals and radio-frequency (RF) communications over optical fiber in distributed communications systems, and related components and methods
US9357551B2 (en) 2014-05-30 2016-05-31 Corning Optical Communications Wireless Ltd Systems and methods for simultaneous sampling of serial digital data streams from multiple analog-to-digital converters (ADCS), including in distributed antenna systems
US9385810B2 (en) 2013-09-30 2016-07-05 Corning Optical Communications Wireless Ltd Connection mapping in distributed communication systems
US9420542B2 (en) 2014-09-25 2016-08-16 Corning Optical Communications Wireless Ltd System-wide uplink band gain control in a distributed antenna system (DAS), based on per band gain control of remote uplink paths in remote units
EP3070802A1 (en) * 2015-03-18 2016-09-21 Thales Method and system for energy management
US9455784B2 (en) 2012-10-31 2016-09-27 Corning Optical Communications Wireless Ltd Deployable wireless infrastructures and methods of deploying wireless infrastructures
US9497706B2 (en) 2013-02-20 2016-11-15 Corning Optical Communications Wireless Ltd Power management in distributed antenna systems (DASs), and related components, systems, and methods
US9509133B2 (en) 2014-06-27 2016-11-29 Corning Optical Communications Wireless Ltd Protection of distributed antenna systems
US9525488B2 (en) 2010-05-02 2016-12-20 Corning Optical Communications LLC Digital data services and/or power distribution in optical fiber-based distributed communications systems providing digital data and radio frequency (RF) communications services, and related components and methods
US9602210B2 (en) 2014-09-24 2017-03-21 Corning Optical Communications Wireless Ltd Flexible head-end chassis supporting automatic identification and interconnection of radio interface modules and optical interface modules in an optical fiber-based distributed antenna system (DAS)
US9621293B2 (en) 2012-08-07 2017-04-11 Corning Optical Communications Wireless Ltd Distribution of time-division multiplexed (TDM) management services in a distributed antenna system, and related components, systems, and methods
US9647758B2 (en) 2012-11-30 2017-05-09 Corning Optical Communications Wireless Ltd Cabling connectivity monitoring and verification
US9653861B2 (en) 2014-09-17 2017-05-16 Corning Optical Communications Wireless Ltd Interconnection of hardware components
US9661781B2 (en) 2013-07-31 2017-05-23 Corning Optical Communications Wireless Ltd Remote units for distributed communication systems and related installation methods and apparatuses
US9673904B2 (en) 2009-02-03 2017-06-06 Corning Optical Communications LLC Optical fiber-based distributed antenna systems, components, and related methods for calibration thereof
US9681313B2 (en) 2015-04-15 2017-06-13 Corning Optical Communications Wireless Ltd Optimizing remote antenna unit performance using an alternative data channel
US9685782B2 (en) 2010-11-24 2017-06-20 Corning Optical Communications LLC Power distribution module(s) capable of hot connection and/or disconnection for distributed antenna systems, and related power units, components, and methods
US9715157B2 (en) 2013-06-12 2017-07-25 Corning Optical Communications Wireless Ltd Voltage controlled optical directional coupler
US9730228B2 (en) 2014-08-29 2017-08-08 Corning Optical Communications Wireless Ltd Individualized gain control of remote uplink band paths in a remote unit in a distributed antenna system (DAS), based on combined uplink power level in the remote unit
US9729251B2 (en) 2012-07-31 2017-08-08 Corning Optical Communications LLC Cooling system control in distributed antenna systems
US9775123B2 (en) 2014-03-28 2017-09-26 Corning Optical Communications Wireless Ltd. Individualized gain control of uplink paths in remote units in a distributed antenna system (DAS) based on individual remote unit contribution to combined uplink power
US9785175B2 (en) 2015-03-27 2017-10-10 Corning Optical Communications Wireless, Ltd. Combining power from electrically isolated power paths for powering remote units in a distributed antenna system(s) (DASs)
US9807700B2 (en) 2015-02-19 2017-10-31 Corning Optical Communications Wireless Ltd Offsetting unwanted downlink interference signals in an uplink path in a distributed antenna system (DAS)
US9948349B2 (en) 2015-07-17 2018-04-17 Corning Optical Communications Wireless Ltd IOT automation and data collection system
US9974074B2 (en) 2013-06-12 2018-05-15 Corning Optical Communications Wireless Ltd Time-division duplexing (TDD) in distributed communications systems, including distributed antenna systems (DASs)
US10014944B2 (en) 2010-08-16 2018-07-03 Corning Optical Communications LLC Remote antenna clusters and related systems, components, and methods supporting digital data signal propagation between remote antenna units
US10096909B2 (en) 2014-11-03 2018-10-09 Corning Optical Communications Wireless Ltd. Multi-band monopole planar antennas configured to facilitate improved radio frequency (RF) isolation in multiple-input multiple-output (MIMO) antenna arrangement
US10110308B2 (en) 2014-12-18 2018-10-23 Corning Optical Communications Wireless Ltd Digital interface modules (DIMs) for flexibly distributing digital and/or analog communications signals in wide-area analog distributed antenna systems (DASs)
US10135533B2 (en) 2014-11-13 2018-11-20 Corning Optical Communications Wireless Ltd Analog distributed antenna systems (DASS) supporting distribution of digital communications signals interfaced from a digital signal source and analog radio frequency (RF) communications signals
US10136200B2 (en) 2012-04-25 2018-11-20 Corning Optical Communications LLC Distributed antenna system architectures
US10187151B2 (en) 2014-12-18 2019-01-22 Corning Optical Communications Wireless Ltd Digital-analog interface modules (DAIMs) for flexibly distributing digital and/or analog communications signals in wide-area analog distributed antenna systems (DASs)
US10236924B2 (en) 2016-03-31 2019-03-19 Corning Optical Communications Wireless Ltd Reducing out-of-channel noise in a wireless distribution system (WDS)
US10257056B2 (en) 2012-11-28 2019-04-09 Corning Optical Communications LLC Power management for distributed communication systems, and related components, systems, and methods
US10455497B2 (en) 2013-11-26 2019-10-22 Corning Optical Communications LLC Selective activation of communications services on power-up of a remote unit(s) in a wireless communication system (WCS) based on power consumption
US10560214B2 (en) 2015-09-28 2020-02-11 Corning Optical Communications LLC Downlink and uplink communication path switching in a time-division duplex (TDD) distributed antenna system (DAS)
EP3495913A4 (en) * 2016-08-03 2020-04-15 ZTE Corporation Power supply control method and device for communication network
US10659163B2 (en) 2014-09-25 2020-05-19 Corning Optical Communications LLC Supporting analog remote antenna units (RAUs) in digital distributed antenna systems (DASs) using analog RAU digital adaptors
US10992484B2 (en) 2013-08-28 2021-04-27 Corning Optical Communications LLC Power management for distributed communication systems, and related components, systems, and methods
EP3972194A1 (en) * 2020-09-16 2022-03-23 Schneider Electric Industries SAS Redundant power supply unit
US11296504B2 (en) 2010-11-24 2022-04-05 Corning Optical Communications LLC Power distribution module(s) capable of hot connection and/or disconnection for wireless communication systems, and related power units, components, and methods
EP4178062A1 (en) * 2021-11-08 2023-05-10 Hamilton Sundstrand Corporation Systems and methods for power transfer and load management

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
TWI425328B (en) * 2008-10-03 2014-02-01 Hon Hai Prec Ind Co Ltd Electronic device with redundant control function for fan
TWI449291B (en) * 2011-06-27 2014-08-11 Delta Electronics Inc Power management system and method thereof
EP2624428A1 (en) * 2012-02-06 2013-08-07 Siemens Aktiengesellschaft Modular DC power supply with independent output modules
TWI460955B (en) * 2012-12-24 2014-11-11 Celestica Technology Consultancy Shanghai Co Ltd Apparatus for controlling centralized power supply module of a rack and method of the same
EP3123829B1 (en) 2014-03-24 2018-12-12 Philips Lighting Holding B.V. Power-over-ethernet power distribution system
US9832028B2 (en) * 2014-09-25 2017-11-28 Texas Instruments Incorporated Automatic power budget management for power-over-Ethernet apparatus
TWI551980B (en) * 2015-02-16 2016-10-01 鋐寶科技股份有限公司 Power supply system
TWI566083B (en) * 2015-04-24 2017-01-11 台達電子工業股份有限公司 Standalone Uninterruptible Power Supply

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5483656A (en) * 1993-01-14 1996-01-09 Apple Computer, Inc. System for managing power consumption of devices coupled to a common bus
WO1996019764A1 (en) * 1994-12-22 1996-06-27 Intel Corporation Power budgeting with device specific characterization of power consumption
EP0955573A1 (en) * 1998-05-06 1999-11-10 International Business Machines Corporation Smart dasd spin-up
US6643566B1 (en) * 1999-01-12 2003-11-04 Powerdsine Ltd. System for power delivery over data communication cabling infrastructure
US6687839B1 (en) * 2000-05-31 2004-02-03 Palmone, Inc. Method and apparatus allowing a battery to regain charge in a handheld device without an applied external charge while still supplying power selected designated components

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7162650B2 (en) * 2001-09-26 2007-01-09 D-Link Corporation Network switching apparatus for supplying power to network communication equipment through twisted pair line

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5483656A (en) * 1993-01-14 1996-01-09 Apple Computer, Inc. System for managing power consumption of devices coupled to a common bus
WO1996019764A1 (en) * 1994-12-22 1996-06-27 Intel Corporation Power budgeting with device specific characterization of power consumption
EP0955573A1 (en) * 1998-05-06 1999-11-10 International Business Machines Corporation Smart dasd spin-up
US6643566B1 (en) * 1999-01-12 2003-11-04 Powerdsine Ltd. System for power delivery over data communication cabling infrastructure
US6687839B1 (en) * 2000-05-31 2004-02-03 Palmone, Inc. Method and apparatus allowing a battery to regain charge in a handheld device without an applied external charge while still supplying power selected designated components

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
DOHMANN H: "POWER OVER ETHERNET DER WEG ZUR STANDARDISIERUNG", ELEKTRONIK, WEKA FACHZEITSCHRIFTENVERLAG, POING, DE, vol. 52, no. 11, 27 May 2003 (2003-05-27), pages 58 - 61, XP001163131, ISSN: 0013-5658 *

Cited By (109)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8108705B2 (en) * 2008-03-07 2012-01-31 Nec Corporation Power supplying device, power supply controlling method, power supply controlling program and network system
US9112611B2 (en) 2009-02-03 2015-08-18 Corning Optical Communications LLC Optical fiber-based distributed antenna systems, components, and related methods for calibration thereof
EP2394378A1 (en) * 2009-02-03 2011-12-14 Corning Cable Systems LLC Optical fiber-based distributed antenna systems, components, and related methods for monitoring and configuring thereof
US9900097B2 (en) 2009-02-03 2018-02-20 Corning Optical Communications LLC Optical fiber-based distributed antenna systems, components, and related methods for calibration thereof
US10153841B2 (en) 2009-02-03 2018-12-11 Corning Optical Communications LLC Optical fiber-based distributed antenna systems, components, and related methods for calibration thereof
US9673904B2 (en) 2009-02-03 2017-06-06 Corning Optical Communications LLC Optical fiber-based distributed antenna systems, components, and related methods for calibration thereof
US10128951B2 (en) 2009-02-03 2018-11-13 Corning Optical Communications LLC Optical fiber-based distributed antenna systems, components, and related methods for monitoring and configuring thereof
US9219879B2 (en) 2009-11-13 2015-12-22 Corning Optical Communications LLC Radio-over-fiber (ROF) system for protocol-independent wired and/or wireless communication
US9729238B2 (en) 2009-11-13 2017-08-08 Corning Optical Communications LLC Radio-over-fiber (ROF) system for protocol-independent wired and/or wireless communication
US9485022B2 (en) 2009-11-13 2016-11-01 Corning Optical Communications LLC Radio-over-fiber (ROF) system for protocol-independent wired and/or wireless communication
US9319138B2 (en) 2010-02-15 2016-04-19 Corning Optical Communications LLC Dynamic cell bonding (DCB) for radio-over-fiber (RoF)-based networks and communication systems and related methods
US9853732B2 (en) 2010-05-02 2017-12-26 Corning Optical Communications LLC Digital data services and/or power distribution in optical fiber-based distributed communications systems providing digital data and radio frequency (RF) communications services, and related components and methods
US9525488B2 (en) 2010-05-02 2016-12-20 Corning Optical Communications LLC Digital data services and/or power distribution in optical fiber-based distributed communications systems providing digital data and radio frequency (RF) communications services, and related components and methods
US9270374B2 (en) 2010-05-02 2016-02-23 Corning Optical Communications LLC Providing digital data services in optical fiber-based distributed radio frequency (RF) communications systems, and related components and methods
CN102893554B (en) * 2010-05-03 2015-05-27 思科技术公司 Power-sharing network communications device, method and system
CN102893554A (en) * 2010-05-03 2013-01-23 思科技术公司 Power-sharing network communications device
US8310089B2 (en) 2010-05-03 2012-11-13 Cisco Technology, Inc. Power sharing network communications device
WO2011139432A1 (en) * 2010-05-03 2011-11-10 Cisco Technology, Inc. Power-sharing network communications device
US10014944B2 (en) 2010-08-16 2018-07-03 Corning Optical Communications LLC Remote antenna clusters and related systems, components, and methods supporting digital data signal propagation between remote antenna units
US11671914B2 (en) 2010-10-13 2023-06-06 Corning Optical Communications LLC Power management for remote antenna units in distributed antenna systems
US9160449B2 (en) 2010-10-13 2015-10-13 Ccs Technology, Inc. Local power management for remote antenna units in distributed antenna systems
WO2012051227A1 (en) * 2010-10-13 2012-04-19 Ccs Technology, Inc. Local power management for remote antenna units in distributed antenna systems
US11212745B2 (en) 2010-10-13 2021-12-28 Corning Optical Communications LLC Power management for remote antenna units in distributed antenna systems
US11178609B2 (en) 2010-10-13 2021-11-16 Corning Optical Communications LLC Power management for remote antenna units in distributed antenna systems
US9419712B2 (en) 2010-10-13 2016-08-16 Ccs Technology, Inc. Power management for remote antenna units in distributed antenna systems
WO2012051230A1 (en) * 2010-10-13 2012-04-19 Ccs Technology, Inc. Power management for remote antenna units in distributed antenna systems
US10045288B2 (en) 2010-10-13 2018-08-07 Corning Optical Communications LLC Power management for remote antenna units in distributed antenna systems
US10104610B2 (en) 2010-10-13 2018-10-16 Corning Optical Communications LLC Local power management for remote antenna units in distributed antenna systems
US10849064B2 (en) 2010-10-13 2020-11-24 Corning Optical Communications LLC Power management for remote antenna units in distributed antenna systems
US10750442B2 (en) 2010-10-13 2020-08-18 Corning Optical Communications LLC Local power management for remote antenna units in distributed antenna systems
US9252874B2 (en) 2010-10-13 2016-02-02 Ccs Technology, Inc Power management for remote antenna units in distributed antenna systems
US11224014B2 (en) 2010-10-13 2022-01-11 Corning Optical Communications LLC Power management for remote antenna units in distributed antenna systems
US10425891B2 (en) 2010-10-13 2019-09-24 Corning Optical Communications LLC Power management for remote antenna units in distributed antenna systems
US9699723B2 (en) 2010-10-13 2017-07-04 Ccs Technology, Inc. Local power management for remote antenna units in distributed antenna systems
US10420025B2 (en) 2010-10-13 2019-09-17 Corning Optical Communications LLC Local power management for remote antenna units in distributed antenna systems
US9685782B2 (en) 2010-11-24 2017-06-20 Corning Optical Communications LLC Power distribution module(s) capable of hot connection and/or disconnection for distributed antenna systems, and related power units, components, and methods
US11114852B2 (en) 2010-11-24 2021-09-07 Corning Optical Communications LLC Power distribution module(s) capable of hot connection and/or disconnection for wireless communication systems, and related power units, components, and methods
US11296504B2 (en) 2010-11-24 2022-04-05 Corning Optical Communications LLC Power distribution module(s) capable of hot connection and/or disconnection for wireless communication systems, and related power units, components, and methods
US10454270B2 (en) 2010-11-24 2019-10-22 Corning Optical Communicatons LLC Power distribution module(s) capable of hot connection and/or disconnection for wireless communication systems, and related power units, components, and methods
US11715949B2 (en) 2010-11-24 2023-08-01 Corning Optical Communications LLC Power distribution module(s) capable of hot connection and/or disconnection for wireless communication systems, and related power units, components, and methods
US9325429B2 (en) 2011-02-21 2016-04-26 Corning Optical Communications LLC Providing digital data services as electrical signals and radio-frequency (RF) communications over optical fiber in distributed communications systems, and related components and methods
US10205538B2 (en) 2011-02-21 2019-02-12 Corning Optical Communications LLC Providing digital data services as electrical signals and radio-frequency (RF) communications over optical fiber in distributed communications systems, and related components and methods
US9813164B2 (en) 2011-02-21 2017-11-07 Corning Optical Communications LLC Providing digital data services as electrical signals and radio-frequency (RF) communications over optical fiber in distributed communications systems, and related components and methods
US9806797B2 (en) 2011-04-29 2017-10-31 Corning Optical Communications LLC Systems, methods, and devices for increasing radio frequency (RF) power in distributed antenna systems
US9184843B2 (en) 2011-04-29 2015-11-10 Corning Optical Communications LLC Determining propagation delay of communications in distributed antenna systems, and related components, systems, and methods
US9240835B2 (en) 2011-04-29 2016-01-19 Corning Optical Communications LLC Systems, methods, and devices for increasing radio frequency (RF) power in distributed antenna systems
US10148347B2 (en) 2011-04-29 2018-12-04 Corning Optical Communications LLC Systems, methods, and devices for increasing radio frequency (RF) power in distributed antenna systems
US9807722B2 (en) 2011-04-29 2017-10-31 Corning Optical Communications LLC Determining propagation delay of communications in distributed antenna systems, and related components, systems, and methods
US9369222B2 (en) 2011-04-29 2016-06-14 Corning Optical Communications LLC Determining propagation delay of communications in distributed antenna systems, and related components, systems, and methods
US10349156B2 (en) 2012-04-25 2019-07-09 Corning Optical Communications LLC Distributed antenna system architectures
US10136200B2 (en) 2012-04-25 2018-11-20 Corning Optical Communications LLC Distributed antenna system architectures
US9729251B2 (en) 2012-07-31 2017-08-08 Corning Optical Communications LLC Cooling system control in distributed antenna systems
US9973968B2 (en) 2012-08-07 2018-05-15 Corning Optical Communications Wireless Ltd Distribution of time-division multiplexed (TDM) management services in a distributed antenna system, and related components, systems, and methods
US9621293B2 (en) 2012-08-07 2017-04-11 Corning Optical Communications Wireless Ltd Distribution of time-division multiplexed (TDM) management services in a distributed antenna system, and related components, systems, and methods
US9455784B2 (en) 2012-10-31 2016-09-27 Corning Optical Communications Wireless Ltd Deployable wireless infrastructures and methods of deploying wireless infrastructures
US10999166B2 (en) 2012-11-28 2021-05-04 Corning Optical Communications LLC Power management for distributed communication systems, and related components, systems, and methods
US10257056B2 (en) 2012-11-28 2019-04-09 Corning Optical Communications LLC Power management for distributed communication systems, and related components, systems, and methods
US11665069B2 (en) 2012-11-28 2023-05-30 Corning Optical Communications LLC Power management for distributed communication systems, and related components, systems, and methods
US10530670B2 (en) 2012-11-28 2020-01-07 Corning Optical Communications LLC Power management for distributed communication systems, and related components, systems, and methods
US10361782B2 (en) 2012-11-30 2019-07-23 Corning Optical Communications LLC Cabling connectivity monitoring and verification
US9647758B2 (en) 2012-11-30 2017-05-09 Corning Optical Communications Wireless Ltd Cabling connectivity monitoring and verification
US9497706B2 (en) 2013-02-20 2016-11-15 Corning Optical Communications Wireless Ltd Power management in distributed antenna systems (DASs), and related components, systems, and methods
US11792776B2 (en) 2013-06-12 2023-10-17 Corning Optical Communications LLC Time-division duplexing (TDD) in distributed communications systems, including distributed antenna systems (DASs)
US9974074B2 (en) 2013-06-12 2018-05-15 Corning Optical Communications Wireless Ltd Time-division duplexing (TDD) in distributed communications systems, including distributed antenna systems (DASs)
US9715157B2 (en) 2013-06-12 2017-07-25 Corning Optical Communications Wireless Ltd Voltage controlled optical directional coupler
US11291001B2 (en) 2013-06-12 2022-03-29 Corning Optical Communications LLC Time-division duplexing (TDD) in distributed communications systems, including distributed antenna systems (DASs)
US9247543B2 (en) 2013-07-23 2016-01-26 Corning Optical Communications Wireless Ltd Monitoring non-supported wireless spectrum within coverage areas of distributed antenna systems (DASs)
US9526020B2 (en) 2013-07-23 2016-12-20 Corning Optical Communications Wireless Ltd Monitoring non-supported wireless spectrum within coverage areas of distributed antenna systems (DASs)
US9967754B2 (en) 2013-07-23 2018-05-08 Corning Optical Communications Wireless Ltd Monitoring non-supported wireless spectrum within coverage areas of distributed antenna systems (DASs)
US10292056B2 (en) 2013-07-23 2019-05-14 Corning Optical Communications LLC Monitoring non-supported wireless spectrum within coverage areas of distributed antenna systems (DASs)
US9661781B2 (en) 2013-07-31 2017-05-23 Corning Optical Communications Wireless Ltd Remote units for distributed communication systems and related installation methods and apparatuses
US11516030B2 (en) 2013-08-28 2022-11-29 Corning Optical Communications LLC Power management for distributed communication systems, and related components, systems, and methods
US10992484B2 (en) 2013-08-28 2021-04-27 Corning Optical Communications LLC Power management for distributed communication systems, and related components, systems, and methods
US9385810B2 (en) 2013-09-30 2016-07-05 Corning Optical Communications Wireless Ltd Connection mapping in distributed communication systems
US10455497B2 (en) 2013-11-26 2019-10-22 Corning Optical Communications LLC Selective activation of communications services on power-up of a remote unit(s) in a wireless communication system (WCS) based on power consumption
US9178635B2 (en) 2014-01-03 2015-11-03 Corning Optical Communications Wireless Ltd Separation of communication signal sub-bands in distributed antenna systems (DASs) to reduce interference
US9775123B2 (en) 2014-03-28 2017-09-26 Corning Optical Communications Wireless Ltd. Individualized gain control of uplink paths in remote units in a distributed antenna system (DAS) based on individual remote unit contribution to combined uplink power
US9357551B2 (en) 2014-05-30 2016-05-31 Corning Optical Communications Wireless Ltd Systems and methods for simultaneous sampling of serial digital data streams from multiple analog-to-digital converters (ADCS), including in distributed antenna systems
US9807772B2 (en) 2014-05-30 2017-10-31 Corning Optical Communications Wireless Ltd. Systems and methods for simultaneous sampling of serial digital data streams from multiple analog-to-digital converters (ADCs), including in distributed antenna systems
US9509133B2 (en) 2014-06-27 2016-11-29 Corning Optical Communications Wireless Ltd Protection of distributed antenna systems
GB2543221A (en) * 2014-08-12 2017-04-12 Avocent Huntsville Llc System and method for rack over provisioning and intelligent power management
WO2016025489A1 (en) * 2014-08-12 2016-02-18 Avocent Huntsville Corp. System and method for rack over provisioning and intelligent power management
US9730228B2 (en) 2014-08-29 2017-08-08 Corning Optical Communications Wireless Ltd Individualized gain control of remote uplink band paths in a remote unit in a distributed antenna system (DAS), based on combined uplink power level in the remote unit
US10397929B2 (en) 2014-08-29 2019-08-27 Corning Optical Communications LLC Individualized gain control of remote uplink band paths in a remote unit in a distributed antenna system (DAS), based on combined uplink power level in the remote unit
US9653861B2 (en) 2014-09-17 2017-05-16 Corning Optical Communications Wireless Ltd Interconnection of hardware components
US9929810B2 (en) 2014-09-24 2018-03-27 Corning Optical Communications Wireless Ltd Flexible head-end chassis supporting automatic identification and interconnection of radio interface modules and optical interface modules in an optical fiber-based distributed antenna system (DAS)
US9602210B2 (en) 2014-09-24 2017-03-21 Corning Optical Communications Wireless Ltd Flexible head-end chassis supporting automatic identification and interconnection of radio interface modules and optical interface modules in an optical fiber-based distributed antenna system (DAS)
US10659163B2 (en) 2014-09-25 2020-05-19 Corning Optical Communications LLC Supporting analog remote antenna units (RAUs) in digital distributed antenna systems (DASs) using analog RAU digital adaptors
US9788279B2 (en) 2014-09-25 2017-10-10 Corning Optical Communications Wireless Ltd System-wide uplink band gain control in a distributed antenna system (DAS), based on per-band gain control of remote uplink paths in remote units
US9420542B2 (en) 2014-09-25 2016-08-16 Corning Optical Communications Wireless Ltd System-wide uplink band gain control in a distributed antenna system (DAS), based on per band gain control of remote uplink paths in remote units
US10096909B2 (en) 2014-11-03 2018-10-09 Corning Optical Communications Wireless Ltd. Multi-band monopole planar antennas configured to facilitate improved radio frequency (RF) isolation in multiple-input multiple-output (MIMO) antenna arrangement
US10523326B2 (en) 2014-11-13 2019-12-31 Corning Optical Communications LLC Analog distributed antenna systems (DASS) supporting distribution of digital communications signals interfaced from a digital signal source and analog radio frequency (RF) communications signals
US10135533B2 (en) 2014-11-13 2018-11-20 Corning Optical Communications Wireless Ltd Analog distributed antenna systems (DASS) supporting distribution of digital communications signals interfaced from a digital signal source and analog radio frequency (RF) communications signals
US10523327B2 (en) 2014-12-18 2019-12-31 Corning Optical Communications LLC Digital-analog interface modules (DAIMs) for flexibly distributing digital and/or analog communications signals in wide-area analog distributed antenna systems (DASs)
US10187151B2 (en) 2014-12-18 2019-01-22 Corning Optical Communications Wireless Ltd Digital-analog interface modules (DAIMs) for flexibly distributing digital and/or analog communications signals in wide-area analog distributed antenna systems (DASs)
US10361783B2 (en) 2014-12-18 2019-07-23 Corning Optical Communications LLC Digital interface modules (DIMs) for flexibly distributing digital and/or analog communications signals in wide-area analog distributed antenna systems (DASs)
US10110308B2 (en) 2014-12-18 2018-10-23 Corning Optical Communications Wireless Ltd Digital interface modules (DIMs) for flexibly distributing digital and/or analog communications signals in wide-area analog distributed antenna systems (DASs)
US9807700B2 (en) 2015-02-19 2017-10-31 Corning Optical Communications Wireless Ltd Offsetting unwanted downlink interference signals in an uplink path in a distributed antenna system (DAS)
US10292114B2 (en) 2015-02-19 2019-05-14 Corning Optical Communications LLC Offsetting unwanted downlink interference signals in an uplink path in a distributed antenna system (DAS)
EP3070802A1 (en) * 2015-03-18 2016-09-21 Thales Method and system for energy management
US9785175B2 (en) 2015-03-27 2017-10-10 Corning Optical Communications Wireless, Ltd. Combining power from electrically isolated power paths for powering remote units in a distributed antenna system(s) (DASs)
US9681313B2 (en) 2015-04-15 2017-06-13 Corning Optical Communications Wireless Ltd Optimizing remote antenna unit performance using an alternative data channel
US10009094B2 (en) 2015-04-15 2018-06-26 Corning Optical Communications Wireless Ltd Optimizing remote antenna unit performance using an alternative data channel
US9948349B2 (en) 2015-07-17 2018-04-17 Corning Optical Communications Wireless Ltd IOT automation and data collection system
US10560214B2 (en) 2015-09-28 2020-02-11 Corning Optical Communications LLC Downlink and uplink communication path switching in a time-division duplex (TDD) distributed antenna system (DAS)
US10236924B2 (en) 2016-03-31 2019-03-19 Corning Optical Communications Wireless Ltd Reducing out-of-channel noise in a wireless distribution system (WDS)
EP3495913A4 (en) * 2016-08-03 2020-04-15 ZTE Corporation Power supply control method and device for communication network
EP3972194A1 (en) * 2020-09-16 2022-03-23 Schneider Electric Industries SAS Redundant power supply unit
EP4178062A1 (en) * 2021-11-08 2023-05-10 Hamilton Sundstrand Corporation Systems and methods for power transfer and load management

Also Published As

Publication number Publication date
WO2006077570A1 (en) 2006-07-27
TWI436197B (en) 2014-05-01
TW200632634A (en) 2006-09-16

Similar Documents

Publication Publication Date Title
US7400062B2 (en) Rack level power management
WO2006077569A1 (en) Rack level power management
US7441133B2 (en) Rack level power management for power over Ethernet
US7142951B2 (en) Direct current power pooling for an ethernet network
US8656194B2 (en) Method and system for distributing power to networked devices
US7886165B2 (en) Power management for Power-over-Ethernet-capable switch
US7478251B1 (en) Methods and apparatus for provisioning uninterruptible power for power over Ethernet applications
EP1964309B1 (en) Providing detailed information on powered device in system for supplying power over communication link
EP1958375B1 (en) Dynamic power allocation in system for providing power over communication link
US7515526B2 (en) Dual mode power over ethernet controller
US10133648B2 (en) Power over ethernet dynamic power allocation system
EP1964308B1 (en) Power management mechanism in system for supplying power over communication link
US9568988B1 (en) Efficient power allocation for redundant power supply with system priority
US8892910B2 (en) Method and system for providing dynamic power sharing to network devices
US7436950B2 (en) Apparatus and method for real-time power distribution management
US7565555B2 (en) Uninterruptible power supply resource sharing for multiple power sourcing equipment network devices
US8676393B1 (en) Power discovery and allocation within a power sharing group
WO2005109154A2 (en) Method for rapid port power reduction
CN102510344A (en) Rack server system
JPH08509081A (en) Computer device interconnection bus power management system
CN114301176A (en) Power supply method, system, equipment and storage medium based on Ethernet

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 05800214

Country of ref document: EP

Kind code of ref document: A1

WWW Wipo information: withdrawn in national office

Ref document number: 5800214

Country of ref document: EP