Energy model

From Nsnam
Jump to: navigation, search


Network Security Lab (NSL), University of Washington, Seattle has begun work on an generic energy model for ns3. The goal is to simulate an energy source and keep track of energy consumptions of various devices in the node. Current version focuses on radio energy consumption.


Energy modeling is a key element in wireless network simulation. In several simulation scenarios, the energy consumption at a particular node, or at a particular component of a node, is of interest. Further, energy consumption is an important metric for evaluating the performance of wireless network protocols. Also, if a protocol is energy-aware, i.e. its operation depends on the energy level, it cannot be effectively simulated without an energy model. An energy model has been implemented in ns2 (ns2 energy model) but is yet to be implemented in ns3.

Project Goals

In this project, we aim to provide the basic structures for modeling energy sources and energy consumption of various devices on the node. The energy source class will enable the modeling of batteries, discharging models, etc. while the energy consumption models are used to represent the energy consumed by various components of a node. The energy model will provide the following components:

  • Energy source model.
    • Battery.
    • etc.
  • Device energy consumption model.
    • Radio.
    • etc.


  • 03/24/2011 : Paper "An Energy Framework for the Network Simulator 3 (ns-3)" presentation at the SIMUTOOLS 2011 conference.
  • 01/13/2011 : Paper "An Energy Framework for the Network Simulator 3 (ns-3)" accepted by the SIMUTOOLS 2011 conference.
  • 01/05/2011 : Code update released with ns-3.10 in src/contrib/energy
  • 08/20/2010 - 01/04/2011: Public review. Code available at:
  • 08/20/2010 : Released with ns-3.9 in src/contrib/energy.
  • 04/19/2010 - 4/23/2010: Private review of radio energy model.

Energy Model Hierarchy

Energy model information flow

The energy model consists of 2 major components:

  • Energy source.
  • Device energy model.

Only a single energy source will exist on a node, representing the total energy reserve at the node. Multiple device energy models can exist on a single node, representing different devices. Each device energy model will notify the energy source of the energy consumed by that device, and thus update the remaining energy of the source. When energy is completely drained, the energy source will notify all device energy models connected to it.

Energy Source

Energy source class structure. Classes in dotted boxes are not included in initial release.

This is an abstract base class that provides interfaces for for updating/recording total energy consumption on the node. It also issues a notification when the remaining energy goes to zero.

Child classes of the energy source class implement a specific type of energy source, eg. a battery. Some typical child classes are:

  • Basic energy source.
    • Provides basic functionalities such as keeping track of remaining energy, decrease remaining energy, notify device energy models on complete depletion of energy.
  • Rakhmatov-Vrudhula non-linear battery model.
    • Non-linear battery model capable of capturing Rate Capacity Effect and Recovery Effect.

Device Energy Model

Device energy model class structure. Classes in dotted boxes are not included in initial release.

This is a base class and its main function is to monitor the state of a device, and accordingly calculate its energy consumption. It provides interfaces for updating remaining energy in the energy source and handles the notification from the energy source when node energy is depleted. It also maintains a record of the total energy consumption of the device.

Child classes of the device energy consumption class implement energy consumption schemes of specific devices, eg. a radio device. Multiple device models can exist on a node, representing energy consumption due to its different components. Further, multiple objects of the same device model class can also be used in a node. eg. a node could have multiple radios, and hence will have multiple radio energy consumption models.

A typical child implementation of this class is the radio energy model class.

Wifi Radio Energy Model

This class represents energy model for Wifi radio devices with states:

  • IDLE
  • TX
  • RX
  • OFF

These states are defined in the WifiPhy class of ns-3.


The following code snippet installs an energy source (BasicEnergySource) and a WifiRadioEnergyModel onto each node.

 /* create some nodes */ 
 NodeContainer c;
 /* energy source */
 BasicEnergySourceHelper basicSourceHelper;
 // configure energy source
 basicSourceHelper.Set ("BasicEnergySourceInitialEnergyJ", DoubleValue (0.1));
 // install source
 EnergySourceContainer sources = basicSourceHelper.Install (c);
 /* device energy model */
 WifiRadioEnergyModelHelper radioEnergyHelper;
 // configure radio energy model
 radioEnergyHelper.Set ("TxCurrentA", DoubleValue (0.0174));
 // install device model
 DeviceEnergyModelContainer deviceModels = radioEnergyHelper.Install (devices, sources);

The WifiRadioEnergyModel class fully supports the ns-3 built-in WiFi PHY class (YansWifiPhy). A sample simulation script of using the energy model is available in the "examples/energy" folder of ns-3.10.

Expending the Energy Model

Initial release of the energy model only includes implementations of a basic energy source and a basic radio energy model. However, developers can use the interfaces provided to model a wide variety of energy sources and devices.

Energy Source

Public APIs

The energy source base class provides the following interfaces:

  • GetSupplyVoltage:
    • Returns the supply voltage of the energy source.
    • Must be implemented by child classes.
  • GetInitialEnergy:
    • Returns the initial energy (capacity) stored in the energy source.
    • The initial energy (capacity) of a energy source is specific to each implementation. Therefore we do not enforce a "SetInitialEnergy" interface in the base class.
  • GetRemainingEnergy:
    • Returns the remaining energy stored in the energy source.
  • GetEnergyFraction:
    • Returns the energy fraction [0,1] at the energy source. Energy fraction is defined as (remaining energy) / (initial energy).
  • UpdateEnergySource:
    • Notifies EnergySource of stage changes in DeviceEnergyModels. Typically called by DeviceEnergyModels to inform EnergySource of a state change.
    • This interface is used to implement non-linear energy update.
  • SetNode:
    • Sets reference (pointer) to node where EnergySource is installed on.
  • GetNode:
    • Returns reference (pointer) to node where EnergySource is installed on.
  • AppendDeviceEnergyModel:
    • Called when installing device energy models. Energy source object keeps track of every device energy models installed onto the node.
  • FindDeviceEnergyModels:
    • Returns a DeviceEnergyModelContainer containing a list of device energy models installed on the node. Useful when one wants to query certain types of devices for it energy consumption.

Protected APIs

  • CalculateTotalCurrent:
    • Returns total current draw from all DeviceEnergyModel objects.
  • NotifyEnergyDrained:
    • This function Notifies all DeviceEnergyModels installed on the node for the energy depletion event.
    • It should be called when energy is drained (remaining energy = 0) in the energy source.
  • BreakDeviceEnergyModelRefCycle:
    • This function breaks the reference cycle between EnergySource and the list of DeviceEnergyModels.
    • It should be called in DoDispose by all derived class of EnergySource.


Please see the BasicEnergySource class implementation for how the interfaces are used.

Device Energy Model

Public APIs

The device energy model base class provides the following interfaces:

  • SetEnergySource:
    • Called when installing device energy models. A device energy model can not operate without an energy source.
  • GetTotalEnergyConsumption:
    • Returns total energy consumed by the device.
  • ChangeState:
    • Notifies DeviceEnergyModel of a state change.
    • Input parameter can be the state number or a value used internally by the DeviceEnergyModel.
  • GetCurretA:
    • Returns the current draw, in Ampere of the DeviceEnergyModel, at its current state.
  • HandleEnergyDepletion:
    • Automatically called by the energy source object when energy is depleted. It's implementation is specific for each device.


Please see the WifiRadioEnergySource class implementation for how the interfaces are used.