Menu
Latest
12 meetings · Prague, Jeju · 12–16 Oct
Reports
RAN1#126-bis · SA2#177

Glossary term · Management

notEnergySaving state

notEnergySaving state

Management →

notEnergySaving state is the default operational state of a network entity where no energy saving measures are active and full resources are available for normal, peak-traffic operation.

Introduced
Rel-10
Where
Management
Specifications
2 specs
notEnergySaving state Description Purpose What changed Neighbours Specifications

Description

The notEnergySaving state is a fundamental concept in 3GPP energy efficiency management, defined in specifications such as TS 28.310 (Energy Efficiency of 5G) and TS 32.551 (Energy Efficiency of 5G). It represents the baseline operational mode of a network function or network element when no energy saving features are engaged. In this state, the network operates at full capacity, prioritizing service availability and performance over energy consumption. This is the default state that a cell, gNB, or other managed entity assumes when energy saving policies are not actively reducing its capabilities.

Architecturally, the notEnergySaving state is one of several energy saving states defined within the 3GPP management framework. The Management Data Analytics Function (MDAF) and the Energy Saving Management (ESM) function within the Operations, Administration, and Maintenance (OAM) system monitor network load and trigger transitions between states. When traffic demand is high, the network remains in notEnergySaving state to ensure adequate quality of service. When traffic decreases, the network may transition to an energySaving state, where certain resources are deactivated or put into sleep mode. The notEnergySaving state thus serves as the reference point for measuring energy savings and for defining control policies.

The state is typically controlled through the Energy Saving Management (ESM) procedures. The OAM system configures energy saving policies that specify thresholds and conditions for entering and leaving the notEnergySaving state. For example, a policy might dictate that a cell enters energy saving when its load falls below a certain percentage for a specified duration, and returns to notEnergySaving when load exceeds another threshold. The state information is exchanged between network elements and the management system using protocols such as the Network Resource Model (NRM) and the Integration Reference Point (IRP) mechanisms.

In multi-RAT and multi-layer deployments, the notEnergySaving state is crucial for coordinating energy saving across different radio access technologies and frequency layers. For instance, when a 5G NR cell enters energy saving, it may offload traffic to LTE or to other NR carriers, which must be in notEnergySaving state to handle the additional load. The management system ensures that coverage and capacity requirements are met by keeping a sufficient set of cells in notEnergySaving state. This coordination prevents coverage holes and service degradation.

The notEnergySaving state also plays a role in the broader context of network slicing and QoS management. When energy saving is active, the network must ensure that service level agreements (SLAs) for different slices are still met. The notEnergySaving state provides a fallback to guarantee that critical services can be supported when energy saving would otherwise compromise them. As networks evolve towards higher automation, the transition between notEnergySaving and energySaving states is increasingly driven by AI/ML algorithms that predict traffic patterns and optimize energy consumption while maintaining performance.

Purpose & Motivation

The notEnergySaving state exists to provide a clear, standardized baseline for energy saving management in cellular networks. Before its introduction, energy saving mechanisms were vendor-specific and lacked a common framework for coordination and measurement. The 3GPP defined this state to enable interoperable energy saving features across multi-vendor networks, allowing operators to reduce operational expenditure (OPEX) by lowering energy consumption during low-traffic periods without sacrificing service quality during peak hours.

The concept addresses the growing need for energy efficiency in mobile networks, which contribute significantly to operational costs and environmental impact. By defining a default state where no energy saving is active, the standard ensures that network performance is not compromised when traffic demands are high. It also provides a reference for calculating energy savings: the difference between energy consumption in notEnergySaving state and energySaving state quantifies the benefit of energy saving features.

Furthermore, the notEnergySaving state facilitates coordination among different network functions and domains. It allows the management system to know when a network element is operating at full capacity, which is essential for load balancing, mobility management, and ensuring end-to-end service continuity. As networks become more complex with the introduction of 5G and beyond, the notEnergySaving state remains a cornerstone for automated energy saving solutions that balance efficiency with performance.

What changed in its specifications

The latest release-to-release comparison of specifications that define notEnergySaving state. Each summary describes the whole specification, not only this term.

TS 28.310Rel-18 → Rel-19

Rel-19 adds an energy-related information model to TS 28.310, covering energy supply sources, supply modes and energy groups. It also adds energy efficiency KPI and terminology text.

Full comparison in TS 28.310 →
TS 32.551Rel-10 → Rel-11

Added distributed ES switch off, probing procedure, and inter-RAT exclusions for energy saving management.

Full comparison in TS 32.551 →

Release Timeline

Evolution Across Releases

An overview written from the defining specifications, not a verified change history. For the exact text, open the specifications listed below.

Rel-10 Initial

Initial definition introduced as 'the default state in peak-traffic situation, with no specific energy saving in progress.' This established the baseline for energy saving management in 3GPP networks.

Definition carried over unchanged from Rel-10, maintaining the same baseline concept for energy saving management.

Definition carried over unchanged from Rel-11, with no modifications to the core concept.

Definition carried over unchanged from Rel-12, continuing to serve as the default state reference.

Definition carried over unchanged from Rel-13, with no changes to the wording or meaning.

Definition carried over unchanged from Rel-14, maintaining consistency for 5G energy saving frameworks.

Definition carried over unchanged from Rel-15, supporting enhanced energy efficiency features in 5G.

Definition carried over unchanged from Rel-16, with minor formatting adjustments but no semantic change.

Definition carried over unchanged from Rel-17, continuing to be the reference state for energy saving.

Definition carried over unchanged from Rel-18, with no modifications to the core definition.

Wording changed to 'state when no energy saving is in progress.' This simplified the definition while retaining the same meaning, removing the explicit reference to peak-traffic situation to make it more general.

Defining Specifications

3GPP specifications that define or reference notEnergySaving state, with the latest known release. Sourced from the 3GPP document catalog — see methodology.

SpecificationTitleRelease
TS 28.310 vk10 5G Network Energy Efficiency Management Rel-20 read
TS 32.551 vj00 Energy Savings Management Concepts and Requirements Rel-19 read