Energy-Aware Slice Selection is a policy-driven function within the 5G core that dynamically steers user equipment (UE) to the most energy-efficient Network Slicing Instance available. It operates by evaluating candidate slices against both the UE's requested NSSAI and real-time power consumption metrics derived from a Slice-Level Energy Model, ensuring service requirements are met while minimizing the network's carbon footprint.
Glossary
Energy-Aware Slice Selection

What is Energy-Aware Slice Selection?
A policy-driven network function that steers user equipment to the most energy-efficient network slice instance capable of satisfying requested service requirements, minimizing the overall network power footprint.
This mechanism extends standard slice selection by incorporating sustainability metrics from the Network Data Analytics Function (NWDAF) and coordinating with Sleep Mode Coordination strategies. By prioritizing slices operating with Cell DTX or those hosted on infrastructure with a low Power Usage Effectiveness (PUE), the function enables Closed-Loop Slice Optimization that balances performance guarantees with aggressive energy conservation targets.
Key Features of Energy-Aware Slice Selection
The core components and decision-making logic that enable a 5G network to steer user equipment to the most power-efficient slice instance without violating service requirements.
Multi-Objective Policy Engine
The central decision logic that balances energy efficiency against SLA compliance. It evaluates candidate slices by computing a weighted utility function that considers:
- Current power consumption per slice (kW/Gbps)
- Requested QoS profile (5QI, GBR, latency budget)
- Slice load and remaining capacity
- Carbon intensity of the underlying power grid The engine enforces hard constraints—a URLLC slice will never be selected for an eMBB session, even if it is idle—while optimizing soft targets like minimizing the aggregate Power Usage Effectiveness (PUE) across the RAN.
Real-Time Slice Energy Telemetry
Energy-aware selection depends on a continuous feed of granular power metrics from the Network Data Analytics Function (NWDAF) and O-RAN Service Management and Orchestration (SMO) framework. Key inputs include:
- Per-slice Resource Block utilization and muting ratios
- Base station Cell DTX and Sleep Mode Coordination states
- Dynamic Voltage and Frequency Scaling (DVFS) states of virtualized network functions
- Accelerator offloading status for L1 processing This telemetry pipeline enables the selection function to build an accurate, sub-second Slice-Level Energy Model that reflects the true marginal cost of admitting a new PDU session.
Slice Remapping Triggers
Energy-aware selection is not a one-time event at session establishment. The function continuously monitors active sessions and initiates Slice Remapping when:
- A GBR slice enters a low-utilization period, allowing sessions to be consolidated onto fewer, higher-efficiency slices
- The carbon intensity of the local grid spikes, triggering a temporary migration to slices hosted on infrastructure powered by greener energy sources
- A slice's Adaptive Bandwidth Part (BWP) configuration changes, altering its power profile Remapping is executed via standard 5G procedures with session continuity preserved, ensuring no perceptible impact on the user.
Slice Carbon Footprint Integration
Beyond instantaneous power draw, the selection function incorporates the Slice Carbon Footprint as a decision metric. This requires integration with external grid intensity APIs (e.g., Electricity Maps) and internal data center PUE monitoring. The function can:
- Apply a carbon penalty factor to slices running in high-emission regions
- Prioritize Edge Slices powered by on-site renewables during peak grid carbon intensity
- Generate per-tenant carbon accounting reports for ESG compliance This transforms slice selection from a pure energy play into a verifiable sustainability mechanism aligned with corporate net-zero targets.
Closed-Loop Slice Optimization
Energy-aware selection operates within a broader Closed-Loop Slice Optimization framework. The selection decisions feed into an O-RAN Non-Real-Time RIC (Non-RT RIC) that:
- Adjusts slice resource allocations and Resource Overbooking ratios based on long-term selection patterns
- Recommends Slice Decommissioning for chronically underutilized instances
- Tunes the weights of the multi-objective policy engine using reinforcement learning to adapt to seasonal traffic patterns This ensures that the selection function's decisions actively reshape the network's energy posture over hours and days, not just milliseconds.
Frequently Asked Questions
Clear answers to the most common technical questions about the policy-driven mechanisms that steer user equipment to the most energy-efficient network slice instance without violating service requirements.
Energy-Aware Slice Selection (EASS) is a policy-driven network function that dynamically steers user equipment (UE) to the most power-efficient network slice instance capable of satisfying the requested service requirements. It operates by continuously evaluating the Slice-Level Energy Model of each available slice instance, which quantifies power consumption as a function of allocated resources, traffic load, and configured SLA parameters. When a UE initiates a session or a handover event, the EASS function cross-references the device's NSSAI (Network Slice Selection Assistance Information) request against a ranked list of candidate slices, prioritizing those with the lowest projected energy footprint. The selection decision integrates real-time telemetry from the NWDAF (Network Data Analytics Function) to predict load conditions and avoid slices approaching congestion, ensuring that energy optimization never violates Guaranteed Bit Rate (GBR) or URLLC latency budgets. This closed-loop mechanism enables mobile network operators to minimize the overall RAN power footprint while maintaining strict QoS guarantees.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Explore the core mechanisms and adjacent concepts that enable energy-aware slice selection in 5G networks.
Slice Remapping
The process of dynamically reassigning an active user equipment session from one network slice instance to another to optimize for changing service requirements, load conditions, or energy efficiency targets. This is the direct execution mechanism triggered by the energy-aware selection function. Key considerations include:
Closed-Loop Slice Optimization
An automation framework where a policy-driven controller continuously monitors slice KPIs, analyzes deviations from the desired state using AI, and automatically executes corrective reconfiguration actions without human intervention. Energy-aware slice selection operates as a critical decision-making component within this broader closed loop, translating sustainability policies into real-time steering actions that balance performance with power consumption targets.
Network Data Analytics Function (NWDAF)
A 5G core network function that collects and analyzes network data from various sources using machine learning to provide predictive analytics on slice load, performance, and user behavior. The NWDAF supplies the energy-aware slice selection function with predictive insights on future slice utilization and energy consumption trends, enabling proactive rather than reactive steering decisions that preempt congestion and power spikes.
Slice SLA
A formal contract between a slice tenant and a network operator that defines the quantifiable performance metrics a network slice instance must deliver. The energy-aware selection function must operate within the strict boundaries of these SLAs, ensuring that steering a user to a more energy-efficient slice does not violate guaranteed bit rate, latency, or reliability commitments. This creates a constrained optimization problem balancing sustainability with contractual obligations.
Sleep Mode Coordination
A centralized control strategy that synchronizes the activation of low-power states across multiple network components within a slice to maximize energy savings. Energy-aware slice selection complements this by consolidating users onto fewer slices, enabling the decommissioned or emptied slices to enter deep sleep modes or cell discontinuous transmission states, amplifying the total network energy reduction.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us