US8990599B2 - Power control optimization in a communication network - Google Patents
Power control optimization in a communication network Download PDFInfo
- Publication number
- US8990599B2 US8990599B2 US12/747,898 US74789810A US8990599B2 US 8990599 B2 US8990599 B2 US 8990599B2 US 74789810 A US74789810 A US 74789810A US 8990599 B2 US8990599 B2 US 8990599B2
- Authority
- US
- United States
- Prior art keywords
- power control
- network node
- recommendation
- operational state
- state information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/18—TPC being performed according to specific parameters
- H04W52/28—TPC being performed according to specific parameters using user profile, e.g. mobile speed, priority or network state, e.g. standby, idle or non transmission
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
- H04W52/04—TPC
- H04W52/38—TPC being performed in particular situations
- H04W52/386—TPC being performed in particular situations centralized, e.g. when the radio network controller or equivalent takes part in the power control
Definitions
- the present invention relates to power control optimization in a communication network, in particular to a method of operating a power control module for optimizing power consumption of a network node operated in a communication system, to a method of controlling power consumption of the network node, and a related power control module and network node.
- WO 02/07464 A1 there is described an adaptive power management for a network node operated in a cellular communication network.
- Equipment and/or functions at the network node of the cellular communication network are turned off or put into sleep mode during periods of low traffic in order to reduce power consumption of the network node.
- the equipment and/or functions are then turned back on again during periods of high traffic load in order to provide the required functionality to the user.
- the power control needs to fulfill real time and dynamic requirements.
- the technical problem of the present invention is to increase flexibility for controlling the power consumption in the network node.
- this technical object is achieved by a method of operating a power control module for optimizing power consumption of a network node operated in a communication system.
- a first step there is received operational state information from the network node at the power control module.
- a second step there is generated a power control recommendation at the power control module through evaluation of operational state information of the network node as a proposal for the power control configuration of the network node to optimize power consumption thereof.
- the power control recommendation is then forwarded in a third step from the power control module to the network node.
- An important advantage of the present invention is that controlling of power consumption is not based on power control commands to be strictly followed at the network node but on power control recommendations.
- a power control recommendation will be used for optimization of power consumption at the network node if the operative state of the network node at the time of receiving the power control recommendation is in line with the operative state information forwarded to the power control module. Otherwise, power control at the network node is not restricted to the power control recommendation if during generation of the power control recommendation the operative state of the network node has changed significantly.
- the operational state information is related to the state of at least one service provided by the network node, to the state of at least one software module executed in the network node, and/or to the state of at least one hardware unit of the network node.
- operative state of the network node is interpreted in its broadest sense and not only restricted, e.g., the turn on or off of hardware components of the network node.
- the operative state of functional components on a higher operative level in the network node is considered, e.g., the operative state of software modules on the runtime environment or application level or the operative state of services like real time voice services, real time data links, etc.
- the power control recommendation is a full power control recommendation covering a full set of parameters being related to the controlling of the power consumption of the network node, or is a partial power control recommendation covering a subset of parameters being related to the controlling of the power consumption of the network node.
- the differentiation between the full power control recommendation and the partial power recommendation allows to further increase flexibility for optimized controlling of power consumption of the network node.
- the full power control recommendation supports maximum impact on the power control of the network node.
- the use of a partial power control recommendation reduces the computational complexity for generation of the power control recommendation at the power control module.
- the partial power control recommendation suits a constellation where it is known per se that only specific sub-components on any operative level of the network node are either per se or according to a current operative state of the network node open to power consumption optimization.
- the present invention it is suggested to develop an operational state diagram reflecting operational states of the network node and transitions between the operational states. Then, the received operational state information is used for prediction of a future operational state on the basis of the operational state diagram for generation of the power control recommendation.
- a further option for the processing of received operational state information at the power control module is to map received operational state information into reference load profile data.
- the reference load profile data reflects typical load constellations of the network node, e.g., over time or with respect to typical operative requirements. Then, received operational state information of the network node may be used for prediction of a future operational load on the basis of the reference load profile and for generation of the power control recommendation.
- both options offer the possibility for repeated update and adaptation to changing operative conditions in the communication system. Also, both options are flexible enough to accommodate any type of state information, e.g., with respect to services, software, and/or hardware.
- a first step serves to determine operational state information according to the operational state of the network node.
- the operational state information is forwarded from the network node to a power control module for generation of a power control recommendation.
- the power control recommendation is received at the network node from the power control module as a proposal for the power control configuration of the network node to optimize power consumption thereof.
- power control is executed for the network node in consideration of the power control recommendation.
- the non-binding character of the power control recommendation for optimization of power consumption at the network node allows to cope with constellations where the operational state information underlying the generation of the power control recommendation no longer matches the operative state of the network node at a later time when the power control recommendation is received at the network node.
- the interrogation of operative states according to a pre-determined timing is of particular advantage when the operative states of the network node vary over time.
- the incorporation of timing into operative state interrogation improves accuracy of controlling power consumption of the network node.
- the power control recommendation is a full power control recommendation covering a full set of parameters being related to the controlling of the power consumption of the network node or a partial power control recommendation covering a subset of parameters being related to the controlling of the power consumption of the network node.
- the determination of applicability may be achieved through consideration of a set of pre-determined power control rules and/or a set of pre-determined power control constrains for the network node.
- an important advantage of considering the applicability of the power control recommendation is that power consumption optimization cannot lead to malfunction in the network node, e.g., due to a turn off of a functional unit aiming at reduced power consumption according to a power control commendation being overturned by a later load constellation where the functional unit actually needs to stay in operation.
- the power control recommendation is implemented upon applicability thereof.
- the indication of non-applicability of the power control recommendation from the network node to the power control module is of particular advantage in case, e.g., power consumption optimization becomes obsolete in sub-systems of the network node, e.g., due to maintenance or renewal of the sub-systems. In other words, upon non-applicability of power control recommendations any waste of processing resources is avoided at the power control module.
- a computer program product directly loadable into the internal memory of a power control module and/or a network node comprising software code portions for performing the inventive power control recommendation and implementation process when the product is run on a processor of the power control module and/or network node.
- the present invention is also provided to achieve an implementation of the inventive method steps on computer or processor systems.
- such implementation leads to the provision of computer program products for use with a computer system or more specifically a processor comprised in e.g., a power control module and/or a network node.
- This programs defining the functions of the present invention can be delivered to a computer/processor in many forms, including, but not limited to information permanently stored on non-writable storage media, e.g., read only memory devices such as ROM or CD ROM discs readable by processors or computer I/O attachments; information stored on writable storage media, i.e. floppy discs and hard-drives; or information convey to a computer/processor through communication media such as network and/or telephone networks via modems or other interface devices. It should be understood that such media, when carrying processor readable instructions implementing the inventive concept represent alternate embodiments of the present invention.
- the implementation of the power control for controlling the power consumption in network nodes as outlined above will help to significantly reduce the power consumption of the entire communication network as well as individual sub-systems of the communication network which implement the power control according to the present invention.
- a reduction of energy consumption within the communication system will have a beneficial impact on CO 2 consumption, usage of natural, non-replenishing resource, and finally on operator costs for operating the communication system.
- FIG. 1 shows a schematic diagram of a network node according to the present invention
- FIG. 2 shows a schematic diagram of a power control module according to the present invention
- FIG. 3 shows a flowchart of operation for the network node shown in FIG. 1 and a flowchart of operation of the power control module shown in FIG. 2 ;
- FIG. 4 shows a further detailed schematic diagram of the network node shown in FIG. 1 and a further detailed schematic diagram of the power control module shown in FIG. 2 ;
- FIG. 5 shows a further detailed flowchart of operation for the power control unit comprises in the network node shown in FIG. 1 ;
- FIG. 6 shows a flowchart of operation for the operational state diagram unit comprised in the power control module shown in FIG. 4 ;
- FIG. 7 shows a flowchart of operation for the reference load profile unit comprised in the power control module shown in FIG. 4 ;
- FIG. 8 shows an example of an operational state diagram as used within the power control module
- FIG. 9 shows an example of a reference load profile as used within the power control module
- FIG. 10 shows a hierarchy for structuring the operation of services and software in the network node.
- FIG. 11 shows a hierarchy of hardware components in the network node.
- the basic idea underlying the present invention is to provide options to reduce the overall power consumption by putting well defined Service/Software/Hardware components fully or partially into a no-, or very-low-power mode during predicted time frames dynamically learned by the power control system and/or through means of parameter definition.
- the present invention relates to a power control system which allows for a controlled dynamic power reduction of the complete system and/or sub-systems by controlling the power consumption of individual components on a functional service, software level and/or a hardware level with respect, e.g., to blade cluster implementing hardware in a modular way and hardware built in a hierarchical manner using cabinets, magazines, circuit boards, and functional entities, e.g., DSP blocks.
- a power control system which allows for a controlled dynamic power reduction of the complete system and/or sub-systems by controlling the power consumption of individual components on a functional service, software level and/or a hardware level with respect, e.g., to blade cluster implementing hardware in a modular way and hardware built in a hierarchical manner using cabinets, magazines, circuit boards, and functional entities, e.g., DSP blocks.
- FIG. 1 shows a schematic diagram of a network node 10 according to the present invention.
- the network node 10 comprises an operation state determining unit 12 , a power control unit 14 , and a communication unit 16 .
- FIG. 2 shows a schematic diagram of a power control module 18 according to the present invention.
- the power control module 18 comprises a power control optimization unit 20 and a communication unit 22 .
- the network node 10 may be any functional unit in a communication system, e.g., a base station in a wireless communication system or a base station controller.
- the power control module 18 may be implemented as a separate power control module or integrated into the communication network infrastructure, e.g., into a base station controller, a radio network controller, or a mobile switching centre of a wireless communication network.
- FIG. 3 shows a flowchart of operation for the network node 10 shown in FIG. 1 and a flowchart of operation of the power control module 18 shown in FIG. 2 .
- the network node 10 operatively executes a method of controlling and optimizing power consumption in the network node.
- a step S 10 operatively executed by the operational state determining unit 12 , serves to determine operational state information according to the operational state of the network node 10 .
- an operational state may be related to any service, software, and/or hardware operation executed in the network node 10 .
- Typical examples for the determination of operational states are, e.g., an evaluation of ongoing services and corresponding resources used by the ongoing services.
- typical examples are consideration of executed programs, active processes, active software tasks, working memory occupation, interrogation of software status registers, etc.
- typical examples are evaluation of working memory occupation rate, clocking frequencies of processors, etc. It should be noted that the examples given above are illustrative only and of non-restricting nature regarding the scope of the present invention.
- a step S 12 operatively executed by the communication unit 16 , serves to forward the operational state information from the network node 10 to the power control module 18 for generation of a power control recommendation.
- this step may be executed continuously, periodically, on request from either a user of the network node or from the power control module 18 , and/or according to a service, software, and/or hardware change event in the network node 10 .
- a step S 14 operatively executed by the communication unit 16 , serves to receive the power control recommendation from the power control module 18 as a proposal for the power control configuration of the network node 10 to optimize power consumption thereof.
- the power control recommendation is a full power control recommendation covering a full set of parameters being related to the controlling of the power consumption of the network node 10 or a partial power control recommendation covering a subset of parameters being related to the controlling of the power consumption of the network node 10 .
- the power control recommendation can be an absolute power control recommendation.
- the recommendation indicates one or more absolute values, e.g., parameter values for the power configuration.
- the power control recommendation can be a differential power control recommendation.
- the recommendation indicates a recommended change or a difference from a current value, e.g., in terms of a percentage or of an absolute value.
- the power control recommendation can be a direction power control recommendation. In this case the recommendation whether to increase, to keep unchanged, or to decrease one or more parameters relevant for the power consumption. Any combination of the mentioned types of power control recommendations is possible.
- a step S 16 operatively executed by the power control unit 14 , serves to execute the power control for the network node 10 in consideration of the power control recommendation.
- the power control module 18 operatively executes a method for optimizing power consumption of a network node 10 .
- a step S 18 operatively executed by the communication unit 22 , serves to receive operational state information from the network node 10 .
- a step S 20 operatively executed by the power control optimizer unit 20 , serves to generate the power control recommendation through evaluation of operational state information of the network node 10 as a proposal for the power control configuration of the network node 10 to optimize power consumption thereof.
- a step S 22 operatively executed by the communication unit 22 , serves to forward the power control recommendation to the network node 10 .
- FIG. 4 shows a further detailed schematic diagram of the network node 10 shown in FIG. 1 and a further detailed schematic diagram of the power control module 18 shown in FIG. 2 .
- the network node 10 shown in FIG. 1 further comprises a service unit 24 , a software unit 26 , and a hardware unit 28 .
- the power control unit 18 shown in FIG. 2 further comprises an operational state diagram unit 30 , a reference load profile unit 32 , a power control rule unit 34 , and a power control constraint unit 36 .
- the operational state determining unit 12 is adapted to determine operational state information with respect to at least one service provided by a service unit 24 , further to determine operational state information with respect at least one software executed in a software unit 26 , and still further to determine operational state information with respect at least one hardware unit 28 of the network node 10 .
- operational state information may be determined according to a pre-determined timing.
- operational state information determined by the operational state determining unit 12 may then be exchanged either with the power control unit 14 for local processing within the network node or with the communication unit 16 for subsequent forwarding to the power control module 18 .
- FIG. 5 shows a further detailed flowchart of operation for the power control unit 14 in the network node 10 shown in FIG. 1 .
- a step S 24 operatively executed by the power control module 14 , serves to determine applicability of the power control recommendation in view of the current operative state of the network node 10 .
- applicability of the power control recommendation is determined through consideration of a current operative state of the network node.
- pre-determined power control rules and/or constraints for optimization of the power consumption of the network node may be considered.
- a step S 26 operatively executed by the power control module 14 , serves to interrogate applicability of the power control recommendation.
- a step S 28 operatively executed by the power control module 14 , so as to consider the power control recommendation during power control of the network node.
- a step S 30 executed by the communication unit 16 of the network node, to forward a non-applicability indication with respect to the power control recommendation to the power control module 18 .
- step S 28 there follows a step S 32 , operatively executed by the power control module 14 , to implement power control in the network node 10 .
- a power control recommendation that is indicated to be not applicable according to step S 30 is not implemented.
- FIG. 6 shows a flowchart of operation for the operational state diagram unit 30 comprised in the power control module 18 shown in FIG. 4 .
- a step S 34 operatively executed by the operational state diagram unit 30 , serves to develop and/or update an operational state diagram using operation state information received over time from the network node 10 .
- an operational state diagram reflecting operational states of the network node and transitions between the operational states.
- this step S 34 needs not be executed with respect to each generation of a power control recommendation but may be executed according to, e.g., pre-determined periods of time or pre-determined point in time.
- a step S 36 operatively executed by the operational state diagram unit 30 , serves to predict a next operational state on the basis of the operational state diagram and a current received operational state information.
- a step S 38 operatively executed by the operational state diagram unit 30 , serves to optionally consider power control rules maintained in the power control rule unit 34 and/or power control constraints maintained in the power control constraint unit 36 .
- a step S 40 operatively executed by the power control optimization unit 20 , serves to generate the power control recommendation on the basis of the outcome of the steps S 34 to S 38 .
- the power control recommendation is a full power control recommendation covering a full set of parameters being related to the controlling of the power consumption of the network node 10 or a partial power control recommendation covering a subset of parameters being related to the controlling of the power consumption of the network node 10 .
- FIG. 7 shows a further detailed flowchart of operation for the reference load profile unit comprised in the power control module 18 shown in FIG. 4 .
- a step S 42 operatively executed by the reference load profile unit 32 , serves to develop/update a reference load profile in view of operational state information received from the network node over time.
- this step S 42 needs not be executed with respect to each generation of a power control recommendation but may be executed according to, e.g., pre-determined periods of time or pre-determined point in time.
- a step S 44 operatively executed by the reference load profile unit 32 , serves to predict a next operational load on the basis of the reference load profile and a current received operational state information.
- a step S 46 operatively executed by the reference load profile unit 32 , serves to optionally consider power control rules maintained in the power control rule unit 34 and/or power control constraints maintained in the power control constraint unit 36 .
- a step S 48 operatively executed by the reference load profile unit 32 , serves to generate the power control recommendation on the basis of the outcome of the steps S 34 to S 38 .
- FIG. 8 shows an example of an operation state diagram as used within the power control module.
- the operational state diagram reflects different operational states, e.g., s 1 to s 4 , of the network node and transitions there between. It should be noted that the operational state and related transitions may dynamically change over time, e.g., due to a modified hardware or software configuration of the network node 10 .
- FIG. 9 shows an example of a reference load profile as used within the power control module.
- the reference load profile may be used to predict a future operational load of the network node 10 and for generation of a power control recommendation covering such a future operational load.
- the reference load profile unit 32 may monitor the traffic load of the network node 10 for a predefined period of time to develop a reference load profile. Based on the reference load profile, the power control optimization unit 20 predicts the required capacity and creates an on/off profile for the network node 10 . This on/off profile can be corrected by a defined factor to secure sufficient capacity up to a certain relative overload. Following this on/off profile, the power control unit 14 of the network node 10 then shuts down or (re-)starts components in the service unit 24 , the software unit 26 , and/or the hardware unit 28 as described by the reference load profile.
- the monitoring behaviour of the reference load profile may be defined according to multiple instantiations to address seasonal variations like, for example, Christmas, New Year's Eve or Mother's Day events, which cannot be considered by a single reference load profile.
- Reference load profiles can be used for the whole network node 10 , for its individual hardware components, for its individual services, and/or for its individual software programs executed in the network node 10 .
- the reference load profile unit 32 may execute a learning phase according to step S 42 shown in FIG. 7 .
- the reference load profile unit 32 gathers information about the load situation in each power controllable entity in the network node 10 .
- the load information is collected for defined intervals and the peak values are registered per entity.
- the reference load profile unit 32 may collect the peak load values from all entities and summarize the peak load values, e.g., per functional group, e.g., speech codec, conference call device.
- a defined overload factor may be applied, with the result being the needed capacity per service, software or hardware component subject to optimized power control.
- This required capacity per service, software or hardware component may be divided by the maximum possible capacity of a single entity of this service, software or hardware component, and thereby yielding the number of required entities to be available during a particular time period.
- the power control optimization unit 20 may take the number of required entities and inform the power control unit 14 in the network node 10 about an upcoming change in entity configuration after a pre-warning time has elapsed.
- the actual pre-warning time may be user configurable per service, software or hardware component.
- the power control optimization unit 20 of the power control module 18 will verify with the power control unit 14 of the network node 10 that the entities which are planned for power down are in fact no longer used, see step S 24 shown in FIG. 5 . If this is the case, the power control unit 14 of the network node 10 powers down the entities scheduled for power down.
- re-instantiation of dormant entities shall be achieved, e.g., by simply re-applying power—or cranking up the operating frequency of hardware components.
- the power control unit 14 of the network node 10 is informed about the availability of the respective entities. It is optional to measure the time from this wake-up call to full performance as an optimization of the wake up time.
- FIG. 10 shows a hierarchy for structuring the operation of services and software in the network node.
- the view on services and/or software running in the network node may be, in a non-binding manner for the scope of the present invention, structured in a hierarchical manner.
- Typical examples for services are ongoing call traffic, data traffic or data links.
- type of software module which may form part of, e.g., either one if an application layer, a platform layer and/or the runtime environment of the network node.
- FIG. 11 shows a blade cluster reflecting a hierarchy of hardware components in the network node.
- the network node 10 divides from a hardware perspective into at least one cabinet. Each cabinet itself is constructed from at least one magazine, each magazine again is constructed using at least one board, and each board is constructed using at least one functional hardware entity, e.g., a DSP block.
- a cabinet is a housing unit which can house multiple magazines with a common power and signal distribution, containing one or more functionally identical or functionally different magazines.
- a magazine is a housing unit which can house multiple boards (as defined above) with a common power and signal distribution, containing one or more functionally identical or functionally different boards.
- a board is an electronic circuit contained on a single PCB, or group of PCBs, with a single power inlet (piggy back construction), containing one or more functionally identical functional entities.
- a functional entity is a group of electronic components which perform a well defined task and of which there are multiple installed in the system to perform the defined task in parallel, independent from each other.
- An entity is as such only functional in view of this task if all components in this entity are functional.
- a single functional entity can be powered down without impacting the overall function of the system due to the multiplicity.
- a typical power control recommendation would be power down referring to a state of no power consumption or extremely low power consumption (typically less than 1% of the power up energy consumption).
- a partial power down can be applied to hardware which implements a redundant function through multiple, functionally identical entities.
- pools of Digital Signal Processors used, for example, in media gateways MGWs—can be segmented and individual segments of this matrix can then be completely switched off.
- a full power down can be applied to complete functional entities contained on a single board, in a single magazine and/or a complete cabinet.
- power reduction can be achieved through controlled reduction of operating frequencies of the involved electronic circuits, mainly microprocessors of all sorts, including general purpose CPUs and Digital Signal Processors.
- the reduction of operating frequency is implemented by means of voltage controlled oscillators or by feeding the normal clock (Clock with frequency of x G(M/K)Hz) signal into a divider chain which allows the usage of Clock, Clock/2, Clock/4, Clock/8, etc., by selecting through a logical (hardware) NAND operation.
- the method which best suits the need is application dependent and can be chosen accordingly.
- a blade cluster architecture of a network node In a preferred embodiment of the present invention is applied to a blade cluster architecture of a network node.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Small-Scale Networks (AREA)
- Supply And Distribution Of Alternating Current (AREA)
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/EP2007/011028 WO2009076979A1 (fr) | 2007-12-14 | 2007-12-14 | Optimisation de la commande de puissance dans un réseau de communication |
Publications (2)
Publication Number | Publication Date |
---|---|
US20110154070A1 US20110154070A1 (en) | 2011-06-23 |
US8990599B2 true US8990599B2 (en) | 2015-03-24 |
Family
ID=39749219
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/747,898 Active 2031-04-30 US8990599B2 (en) | 2007-12-14 | 2007-12-14 | Power control optimization in a communication network |
Country Status (3)
Country | Link |
---|---|
US (1) | US8990599B2 (fr) |
EP (1) | EP2232721B1 (fr) |
WO (1) | WO2009076979A1 (fr) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9690354B1 (en) * | 2013-05-06 | 2017-06-27 | AGGIOS, Inc. | Automatic energy design and management system for assessing system components' energy consumption, compiling energy management control and optimizing energy usage |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2388951B1 (fr) * | 2010-05-17 | 2017-08-09 | Nxp B.V. | Réseau |
WO2012001772A1 (fr) * | 2010-06-29 | 2012-01-05 | 富士通株式会社 | Dispositif et procédé de commande, et dispositif de nœud |
EP2515586B1 (fr) * | 2011-04-21 | 2014-05-14 | Alcatel Lucent | Method to control power consumption in a mobile network |
US20130061072A1 (en) * | 2011-09-06 | 2013-03-07 | Alcatel-Lucent Canada Inc. | Power saving node controller |
WO2013043091A1 (fr) * | 2011-09-22 | 2013-03-28 | Telefonaktiebolaget L M Ericsson (Publ) | Mesure de puissance retour |
Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002007464A1 (fr) | 2000-07-18 | 2002-01-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Gestion de puissance adaptative d'un noeud d'un reseau cellulaire de telecommunications |
GB2396523A (en) | 2002-12-17 | 2004-06-23 | Motorola Inc | Power control for a transmitter in a cellular communication system |
US20060079297A1 (en) | 2003-03-12 | 2006-04-13 | Berndt Pilgram | Apparatus and method for controlling the power consumption of a combined UMTS/GSM/EDGE radio station |
US20070066329A1 (en) | 2005-09-19 | 2007-03-22 | Rajiv Laroia | Methods and apparatus for use in a wireless communications system that uses a multi-mode base station |
US7337334B2 (en) * | 2003-02-14 | 2008-02-26 | International Business Machines Corporation | Network processor power management |
US7581125B2 (en) * | 2005-09-22 | 2009-08-25 | Hewlett-Packard Development Company, L.P. | Agent for managing power among electronic systems |
US7831843B2 (en) * | 2006-09-26 | 2010-11-09 | Dell Products L.P. | Apparatus and methods for managing power in an information handling system |
US8250382B2 (en) * | 2007-08-22 | 2012-08-21 | International Business Machines Corporation | Power control of servers using advanced configuration and power interface (ACPI) states |
-
2007
- 2007-12-14 EP EP07856766.6A patent/EP2232721B1/fr active Active
- 2007-12-14 WO PCT/EP2007/011028 patent/WO2009076979A1/fr active Application Filing
- 2007-12-14 US US12/747,898 patent/US8990599B2/en active Active
Patent Citations (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2002007464A1 (fr) | 2000-07-18 | 2002-01-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Gestion de puissance adaptative d'un noeud d'un reseau cellulaire de telecommunications |
GB2396523A (en) | 2002-12-17 | 2004-06-23 | Motorola Inc | Power control for a transmitter in a cellular communication system |
US7337334B2 (en) * | 2003-02-14 | 2008-02-26 | International Business Machines Corporation | Network processor power management |
US20060079297A1 (en) | 2003-03-12 | 2006-04-13 | Berndt Pilgram | Apparatus and method for controlling the power consumption of a combined UMTS/GSM/EDGE radio station |
US20070066329A1 (en) | 2005-09-19 | 2007-03-22 | Rajiv Laroia | Methods and apparatus for use in a wireless communications system that uses a multi-mode base station |
US7581125B2 (en) * | 2005-09-22 | 2009-08-25 | Hewlett-Packard Development Company, L.P. | Agent for managing power among electronic systems |
US7831843B2 (en) * | 2006-09-26 | 2010-11-09 | Dell Products L.P. | Apparatus and methods for managing power in an information handling system |
US8250382B2 (en) * | 2007-08-22 | 2012-08-21 | International Business Machines Corporation | Power control of servers using advanced configuration and power interface (ACPI) states |
Non-Patent Citations (3)
Title |
---|
Daub, Microsoft could save 45 million tons of CO2 emissions with a few lines of computer code, Blog, Nov. 15, 2006, pp. 1-4, Carnegie Endowment for International Peace, Washington, DC. |
Sinha et al., JouleTrack-A Web Based Tool for Software Energy Profiling, Jun. 18-22, 2001, 6 Pages, Proceedings of Design Automation Conference, 2001, ACM, Las Vegas, NV. |
Sinha et al., JouleTrack—A Web Based Tool for Software Energy Profiling, Jun. 18-22, 2001, 6 Pages, Proceedings of Design Automation Conference, 2001, ACM, Las Vegas, NV. |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9690354B1 (en) * | 2013-05-06 | 2017-06-27 | AGGIOS, Inc. | Automatic energy design and management system for assessing system components' energy consumption, compiling energy management control and optimizing energy usage |
Also Published As
Publication number | Publication date |
---|---|
EP2232721A1 (fr) | 2010-09-29 |
EP2232721B1 (fr) | 2014-08-13 |
US20110154070A1 (en) | 2011-06-23 |
WO2009076979A1 (fr) | 2009-06-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8990599B2 (en) | Power control optimization in a communication network | |
US8225119B2 (en) | Energy-aware server management | |
US8286013B2 (en) | Portable communication device with multi-tiered power save operation | |
CN103348744B (zh) | 使用功率阈值对移动通信终端进行智能功率管理的方法和装置 | |
JP4822165B2 (ja) | 大規模データセンターまたはitインフラにおけるエネルギー消費の確定および動的制御方法 | |
US8112642B2 (en) | Method and system for controlling power in a chip through a power-performance monitor and control unit | |
US20120210150A1 (en) | Method And Apparatus Of Smart Power Management For Mobile Communication Terminals | |
US8041970B2 (en) | Cluster system with reduced power consumption and power management method thereof | |
CN104094191A (zh) | 实时系统中的动态功率管理 | |
CN104781753A (zh) | 功率选通高速缓存存储器的一部分 | |
WO2013091442A1 (fr) | Système et procédé de gestion d'énergie orientée instance de service efficace dans l'internet des objets | |
Cho et al. | A battery lifetime guarantee scheme for selective applications in smart mobile devices | |
Liu et al. | eSENSE: energy efficient stochastic sensing framework scheme for wireless sensor platforms | |
Nithi et al. | Smart power management for mobile handsets | |
Arabas | Modeling and simulation of hierarchical task allocation system for energy-aware HPC clouds | |
Kargahi et al. | Stochastic DVS-based dynamic power management for soft real-time systems | |
Medhat et al. | Energy-efficient multiple producer-consumer | |
Alwasel et al. | Dominating sets-based approach for maximizing Lifetime of IoT-based heterogeneous WSNs enabled sustainable smart city applications | |
Ellis | Controlling Energy Demand in Mobile Computing Systems | |
Iranli et al. | System-level power management: An overview | |
Yao | Low-cost Techniques for Enhancing Energy Efficiency and Information Security in Next Generation Multi-core Server System Design | |
Hughes et al. | A wireless sensor network based green marketplace for electrical appliances | |
Devadas | System-Level Energy Management for Real-Time Systems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL), SWEDEN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:WELTER, KARL-HEINZ;REEL/FRAME:025089/0503 Effective date: 20100918 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 8 |