Energy Efficiency Testing and Modeling of a Commercial O-RAN System

This white paper presents a comprehensive energy-efficiency characterization and modeling of a commercial O-RAN system based on rigorous measurements from a production-like testbed, aiming to provide operators with the quantitative data needed to optimize energy consumption and support sustainable network operations.

N. K. Shankaranarayanan, Akash Gupta, Zhuohuan Li, Sarat Puthenpura, Jens Sohn, Ivan Seskar, Sreenidhi Parthasarathy, Wilfred Luiz, Jeffrey Williamson, VenkataReddy Varra, Prasanthi Maddala, Alex Stancu

Published 2026-03-06
📖 5 min read🧠 Deep dive

📡 The Big Picture: Why Are We Doing This?

Imagine the mobile network as a massive city of traffic. As more people use 5G (streaming videos, gaming, downloading files), the "traffic lights" and "roads" (the cell towers) have to work harder. This uses a lot of electricity, which costs money and hurts the environment.

The goal of this paper is to answer a simple question: How can we make these cell towers use less electricity without slowing down the internet for the people?

The researchers tested a brand-new type of cell tower system called O-RAN. Think of O-RAN as a "modular" or "Lego-style" network. Instead of buying one giant, pre-built tower from a single company, you can mix and match parts from different companies (like a CPU from one brand, software from another, and antennas from a third).

The problem? Because these parts are so new and mixed, nobody knew exactly how much electricity they would drink up in different situations. This paper is the "nutrition label" for that new system.


🏗️ The Setup: The "Test Kitchen"

The researchers didn't just guess; they built a full-scale "test kitchen" in a lab.

  • The Chef (O-CU): The brain of the operation, hosted in the cloud (Amazon AWS).
  • The Sous-Chef (O-DU): The local manager on a dedicated server, handling the immediate orders.
  • The Waiters (O-RUs): Six high-powered cell radio units (the actual antennas) that talk to your phone. They were set up to look exactly like a real city deployment.

They ran hundreds of different "dinner services" (test cases) to see how much energy the kitchen used when:

  • Serving a full banquet (100% traffic).
  • Serving just a few appetizers (low traffic).
  • Using different menu items (different frequency bands).
  • Having more or fewer waiters (different MIMO configurations).

🔍 Key Findings: What Did They Learn?

1. The "Idle" Problem (The Running Engine)

The Analogy: Imagine a delivery truck. Even if it's sitting in the driveway with no packages, the engine is still running, burning gas.
The Finding: The biggest energy hog in these towers isn't the data transmission; it's the idle power. Even when no one is downloading anything, the tower is "awake" and consuming about 200 Watts just to stay on.

  • Takeaway: Turning off a tower completely when traffic is low saves the most energy. Just slowing it down doesn't help much because the "engine" is still idling.

2. The "Traffic Jam" vs. "Open Highway" (Efficiency)

The Analogy: Imagine a bus.

  • Scenario A: The bus drives with 1 passenger. It burns a lot of fuel per person.
  • Scenario B: The bus drives with 50 passengers. It burns the same amount of fuel, but the cost per person is tiny.
    The Finding: The system is most energy-efficient when it is full. When the network is running at 100% capacity, it is incredibly efficient. When traffic drops to 50% or 30%, the energy efficiency crashes because the "bus" is still running at full size but carrying fewer people.
  • Takeaway: It's better to keep the network busy and efficient than to have it running half-empty.

3. The "Multi-Band" Magic (Adding More Lanes)

The Analogy: You have a highway. You can either build a new highway (add a new tower) or add more lanes to the existing highway.
The Finding: It is often more energy-efficient to activate a second "lane" (frequency band) on an existing tower than to turn on a whole new tower. The tower is already "idling" and paying the energy tax; adding a second lane just costs a little extra fuel to move more cars.

4. The "Brain" vs. The "Muscle" (Cloud vs. Hardware)

The Analogy: The "Brain" (the cloud software) uses very little electricity, even when it's working hard. The "Muscle" (the physical radio antennas) uses the vast majority of the power.
The Finding: The cloud part of the network is surprisingly efficient. The real energy savings come from managing the physical antennas, not the software servers.


📉 The "Path Loss" Surprise

The Analogy: Imagine shouting to a friend.

  • If they are close (Low Path Loss), you shout normally.
  • If they are far away or there's a wall (High Path Loss), you have to shout much louder.
    The Finding: When the signal has to travel through bad conditions (high path loss), the phone gets slower data speeds. However, the tower doesn't use less energy. It keeps shouting at full volume (or close to it) even though the data rate drops.
  • Takeaway: Bad weather or distance makes the network slower, but it doesn't automatically make it more energy-efficient. The tower keeps burning fuel to maintain the connection.

🚀 The Conclusion: What Should Operators Do?

The paper concludes that to save energy, operators shouldn't just try to "tweak" the settings. They need a smarter strategy:

  1. Sleep Mode is King: The biggest savings come from turning off parts of the tower (or the whole tower) when no one is using it, rather than just slowing it down.
  2. Fill the Bus: It's better to concentrate traffic on fewer, fully-loaded towers than to spread it out thinly across many half-empty ones.
  3. Measure Everything: You can't manage what you don't measure. This paper provides the "recipe" for how to measure energy use so companies can build better, greener networks.

In a nutshell: This paper proves that while the new "Lego-style" 5G towers are flexible, they are also hungry. To feed them less, we need to turn them off when they aren't needed and keep them busy when they are on.