Energy Conservation and Emission Reduction

5G RAN
Energy Conservation and Emission

Reduction Feature Parameter
Description
Issue 06
Date 2021-09-29
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2021. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://www.huawei.com
Email: support@huawei.com
Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. i

5G RAN
Energy Conservation and Emission Reduction
Feature Parameter Description Contents
Contents
1 Change History.........................................................................................................................1
1.1 5G RAN5.1 06 (2021-09-29)............................................................................................................................................... 1
1.2 5G RAN5.1 05 (2021-09-02)............................................................................................................................................... 2
1.3 5G RAN5.1 04 (2021-06-26)............................................................................................................................................... 3
1.4 5G RAN5.1 03 (2021-05-29)............................................................................................................................................... 4
1.5 5G RAN5.1 02 (2021-04-30)............................................................................................................................................... 5
1.6 5G RAN5.1 01 (2021-03-05)............................................................................................................................................... 6
1.7 5G RAN5.1 Draft A (2020-12-29)...................................................................................................................................... 7
2 About This Document...........................................................................................................14

2.1 General Statements..............................................................................................................................................................14
2.2 Features in This Document................................................................................................................................................ 14
2.3 Differences Between NR FDD and NR TDD.................................................................................................................15
2.4 Differences Between NSA and SA................................................................................................................................... 16
2.5 Differences Between High Frequency Bands and Low Frequency Bands..........................................................17
3 Overview................................................................................................................................. 19
4 Device Level Energy Saving................................................................................................ 21
4.1 Symbol Power Saving.......................................................................................................................................................... 21
4.1.1 Principles.............................................................................................................................................................................. 21
4.1.2 Network Analysis............................................................................................................................................................... 21
4.1.2.1 Benefits.............................................................................................................................................................................. 21
4.1.2.2 Impacts.............................................................................................................................................................................. 22
4.1.3 Requirements...................................................................................................................................................................... 24
4.1.3.1 Licenses.............................................................................................................................................................................. 24
4.1.3.2 Software............................................................................................................................................................................ 24
4.1.3.3 Hardware.......................................................................................................................................................................... 24
4.1.3.4 Networking...................................................................................................................................................................... 25
4.1.3.5 Others................................................................................................................................................................................ 25
4.1.4 Operation and Maintenance......................................................................................................................................... 25
4.1.4.1 Data Configuration........................................................................................................................................................ 25
4.1.4.1.1 Data Preparation.........................................................................................................................................................25
4.1.4.1.2 Using MML Commands............................................................................................................................................ 26
4.1.4.1.3 Using the MAE-Deployment................................................................................................................................... 26
Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. ii

5G RAN
4.1.4.2 Activation Verification.................................................................................................................................................. 26

4.1.4.3 Network Monitoring..................................................................................................................................................... 27
4.2 Intelligent Scheduling for Power Saving....................................................................................................................... 27
4.2.1 Principles.............................................................................................................................................................................. 27
4.2.1.1 Power Saving Scheduling............................................................................................................................................ 28
4.2.1.2 Deep Symbol Power Saving........................................................................................................................................32
4.2.2.1 Benefits.............................................................................................................................................................................. 33
4.2.2.2 Impacts.............................................................................................................................................................................. 33
4.2.3 Requirements...................................................................................................................................................................... 39
4.2.3.1 Licenses.............................................................................................................................................................................. 39
4.2.3.2 Software............................................................................................................................................................................ 39
4.2.3.3 Hardware.......................................................................................................................................................................... 41
4.2.3.4 Others................................................................................................................................................................................ 41
4.3 Timing Carrier Shutdown................................................................................................................................................... 49
4.3.1 Principles.............................................................................................................................................................................. 49
4.3.2 Energy Saving Procedure................................................................................................................................................ 50
4.3.3.1 Benefits.............................................................................................................................................................................. 51
4.3.3.2 Impacts.............................................................................................................................................................................. 51
4.3.4 Requirements...................................................................................................................................................................... 58
4.3.4.1 Licenses.............................................................................................................................................................................. 58
4.3.4.2 Software............................................................................................................................................................................ 58
4.3.4.3 Hardware.......................................................................................................................................................................... 60
4.3.4.4 Others................................................................................................................................................................................ 61
4.4 pRRU Deep Dormancy........................................................................................................................................................ 65
4.4.1 Principles.............................................................................................................................................................................. 65
Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. iii

5G RAN
4.4.2.1 Benefits.............................................................................................................................................................................. 71
4.4.2.2 Impacts.............................................................................................................................................................................. 71
4.4.3 Requirements...................................................................................................................................................................... 72
4.4.3.1 Licenses.............................................................................................................................................................................. 72
4.4.3.2 Software............................................................................................................................................................................ 73
4.4.3.3 Hardware.......................................................................................................................................................................... 73
4.4.3.4 Networking...................................................................................................................................................................... 73
4.4.3.5 Others................................................................................................................................................................................ 73
4.5 RF Channel Intelligent Shutdown................................................................................................................................... 77
4.5.1 Principles.............................................................................................................................................................................. 77
4.5.2.1 Benefits.............................................................................................................................................................................. 79
4.5.2.2 Impacts.............................................................................................................................................................................. 80
4.5.3 Requirements...................................................................................................................................................................... 89
4.5.3.1 Licenses.............................................................................................................................................................................. 89
4.5.3.2 Software............................................................................................................................................................................ 89
4.5.3.3 Hardware.......................................................................................................................................................................... 92
4.5.3.4 Others................................................................................................................................................................................ 94
4.5.4.3 Network Monitoring................................................................................................................................................... 100
5 Network Level Energy Saving.......................................................................................... 102

5.1 Intelligent Carrier Shutdown.......................................................................................................................................... 102
5.1.1 Principles............................................................................................................................................................................ 102
5.1.1.1 Energy Saving Principles............................................................................................................................................102
5.1.1.2 Energy Saving Procedure...........................................................................................................................................104
5.1.2 Network Analysis............................................................................................................................................................ 108
5.1.2.1 Benefits............................................................................................................................................................................108
5.1.2.2 Impacts............................................................................................................................................................................ 108
5.1.3 Requirements.................................................................................................................................................................... 117
5.1.3.1 Licenses........................................................................................................................................................................... 117
Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. iv

5G RAN
5.1.3.2 Software.......................................................................................................................................................................... 118

5.1.3.3 Hardware........................................................................................................................................................................ 118
5.1.3.4 Others.............................................................................................................................................................................. 119
5.1.4 Operation and Maintenance....................................................................................................................................... 119
5.1.4.1 Data Configuration..................................................................................................................................................... 119
5.1.4.1.1 Data Preparation...................................................................................................................................................... 119
5.1.4.1.2 Using MML Commands......................................................................................................................................... 121
5.1.4.1.3 Using the MAE-Deployment.................................................................................................................................123
5.1.4.2 Activation Verification................................................................................................................................................123
6 Site Level Energy Saving................................................................................................... 126

6.1 Low Power Consumption Mode.................................................................................................................................... 126
6.1.1 Principles............................................................................................................................................................................ 126
6.1.2.1 Benefits............................................................................................................................................................................130
6.1.2.2 Impacts............................................................................................................................................................................ 130
6.1.3 Requirements.................................................................................................................................................................... 134
6.1.3.1 Licenses........................................................................................................................................................................... 134
6.1.3.2 Software.......................................................................................................................................................................... 134
6.1.3.3 Hardware........................................................................................................................................................................ 135
6.1.3.4 Others.............................................................................................................................................................................. 135
6.1.4.2 Using the MAE-Deployment.................................................................................................................................... 140
6.2 Baseband Chip Shutdown................................................................................................................................................ 143
6.2.1 Principles............................................................................................................................................................................ 143
6.2.2.1 Benefits............................................................................................................................................................................144
6.2.2.2 Impacts............................................................................................................................................................................ 144
6.2.3 Requirements.................................................................................................................................................................... 145
6.2.3.1 Licenses........................................................................................................................................................................... 145
6.2.3.2 Software.......................................................................................................................................................................... 145
6.2.3.3 Hardware........................................................................................................................................................................ 146
6.2.3.4 Others.............................................................................................................................................................................. 147
Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. v

5G RAN

6.3 PSU Intelligent Shutdown................................................................................................................................................149
6.3.1 Principles............................................................................................................................................................................ 149
6.3.2.1 Benefits............................................................................................................................................................................150
6.3.2.2 Impacts............................................................................................................................................................................ 150
6.3.3 Requirements.................................................................................................................................................................... 150
6.3.3.1 Licenses........................................................................................................................................................................... 150
6.3.3.2 Software.......................................................................................................................................................................... 150
6.3.3.3 Hardware........................................................................................................................................................................ 150
6.3.3.4 Others.............................................................................................................................................................................. 151
7 Energy Consumption Monitoring.................................................................................... 155

7.1 Principles............................................................................................................................................................................... 155
7.2 Network Analysis................................................................................................................................................................ 158
7.2.1 Benefits............................................................................................................................................................................... 158
7.2.2 Impacts............................................................................................................................................................................... 158
7.3 Requirements....................................................................................................................................................................... 159
7.3.1 Licenses............................................................................................................................................................................... 159
7.3.2 Software............................................................................................................................................................................. 159
7.3.3 Hardware........................................................................................................................................................................... 159
7.3.4 Others................................................................................................................................................................................. 159
7.4 Operation and Maintenance.......................................................................................................................................... 160
7.4.1 Data Configuration......................................................................................................................................................... 161
7.4.2 Activation Verification................................................................................................................................................... 161
7.4.3 Network Monitoring...................................................................................................................................................... 161
8 Parameters............................................................................................................................162
9 Counters................................................................................................................................ 163
10 Glossary............................................................................................................................... 164
11 Reference Documents...................................................................................................... 165
Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. vi

5G RAN
Feature Parameter Description 1 Change History
1 Change History
This chapter describes changes not included in the "Parameters", "Counters",

"Glossary", and "Reference Documents" chapters. These changes include:
● Technical changes
Changes in functions and their corresponding parameters
● Editorial changes
Improvements or revisions to the documentation
1.1 5G RAN5.1 06 (2021-09-29)

This issue includes the following changes.
Technical Changes
Change Description Parameter RAT Base Station
Change Model
Added a parameter to None FDD 3900 and

ensure that the coverage Low- 5900 series
remains basically the frequency base stations
same before and after RF TDD DBS3900
channel intelligent LampSite and
shutdown is enabled. For DBS5900
details, see: LampSite
4.5.1 Principles
4.5.4.1.1 Data
Preparation
4.5.4.1.2 Using MML
Commands
Editorial Changes
Revised descriptions in this document.
Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 1

5G RAN
1.2 5G RAN5.1 05 (2021-09-02)

Technical Changes
Change Model
Added support for the Modified FDD 3900 and

function of non-first parameter: Low- 5900 series
packet scheduling Activated frequency base stations
optimization for data RSVDSWPARAM2 TDD DBS3900
convergence in slots. For _BIT10 of the LampSite and
details, see 4.2.1.1 Power NRDUCellRsvdEx DBS5900
Saving Scheduling, t02.RsvdSwPara LampSite
4.2.4.1 Data m2 parameter.
Configuration, and
4.2.4.1.2 Using MML
Commands.
Optimized the carrier None FDD 3900 and

shutdown procedure. For Low- 5900 series
details, see 4.3.2 Energy frequency base stations
Saving Procedure and TDD DBS3900
6.1.1 Principles. LampSite and
DBS5900
LampSite
Added support for license None FDD DBS3900

reliability protection Low- LampSite and
during deep dormancy. frequency DBS5900
For details, see 4.4.1 TDD LampSite
Principles.
Canceled automatic None FDD DBS3900

triggering of deep Low- LampSite and
dormancy pending when frequency DBS5900
deep dormancy-related TDD LampSite
parameters are being
configured. For details, see
4.4.1 Principles.

5G RAN

Change Model
Activated a bit of a Modified Low- 3900 and

reserved parameter to parameter: frequency 5900 series
control the power Activated TDD base stations
aggregation enhancement RSVDSWPARAM1
function for a TDD cell _BIT21 of the
where RF channel NRDUCellRsvdEx
intelligent shutdown is t02.RsvdSwPara
enabled and the transmit m1 parameter.
power compensated for
common channels is
automatically determined.
For details, see 4.5.1
Principles, 4.5.4.1 Data
Configuration, and
4.5.4.1.2 Using MML
Commands.
Editorial Changes
Added the impact relationship between RF channel intelligent shutdown and UL
CoMP. For details, see Function Impacts.
Added the impact relationship between RF channel intelligent shutdown and basic
beam management. For details, see Function Impacts.
1.3 5G RAN5.1 04 (2021-06-26)

Technical Changes
Change Model
Added the function None FDD 3900 and

impacts of beam-level Low- 5900 series
adjustment of the RMSI frequency base stations
broadcast interval in TDD
power saving scheduling.
For details, see 4.2.2.2
Impacts.

5G RAN

Change Model
Activated a reserved Activated the FDD 3900 and

parameter to specify the NRDUCellRsvdEx Low- 5900 series
RLC first packet delay t02.RsvdParam7 frequency base stations
threshold for data parameter. TDD DBS3900
convergence in slots in LampSite and
power saving scheduling. DBS5900
For details, see 4.2.1.1 LampSite
Power Saving Scheduling
and 4.2.4.1 Data
Configuration.
Modified the network None FDD 3900 and

impacts of RF channel Low- 5900 series
intelligent shutdown and frequency base stations
the supported beam TDD DBS3900
coverage scenarios when LampSite and
automatic coverage DBS5900
compensation mode is LampSite
used. For details, see 4.5.1
Principles, 4.5.2.2
Impacts, and 4.5.3.3
Hardware.
Added support for None FDD DBS3900

configuration reliability Low- LampSite and
protection during pRRU frequency DBS5900
deep dormancy. For TDD LampSite
details, see 4.4.1
Principles and 4.4.2.2
Impacts.
Editorial Changes
Combined the descriptions of deep symbol power saving and power saving
scheduling in the Intelligent Scheduling for Power Saving feature into one section
4.2 Intelligent Scheduling for Power Saving.
1.4 5G RAN5.1 03 (2021-05-29)


5G RAN
Technical Changes
Change Model
Activated a reserved Modified FDD 3900 and

parameter to control data parameters: Low- 5900 series
convergence in symbols Activated frequency base stations
for power saving RSVDSWPARAM0 TDD DBS3900
scheduling. For details, see _BIT26 of the LampSite and
4.2.1.1 Power Saving NRDUCellRsvdEx DBS5900
Scheduling and 4.2.4.1 t02.RsvdSwPara LampSite
Data Configuration. m0 parameter.
parameter to control data parameters: Low- 5900 series
convergence in slots for Activated frequency base stations
power saving scheduling. RSVDSWPARAM0 TDD DBS3900
For details, see 4.2.1.1 _BIT27 of the LampSite and
Power Saving Scheduling NRDUCellRsvdEx DBS5900
and 4.2.4.1 Data t02.RsvdSwPara LampSite
Configuration. m0 parameter.
Editorial Changes
Revised the descriptions of baseband chip shutdown. For details, see 6.2 Baseband
Chip Shutdown.
Added the description that RF channel intelligent shutdown is not recommended
in distributed antenna coverage scenarios. For details, see 4.5.4.1.1 Data
Preparation.
Revised the descriptions of the impacts of power saving scheduling. For details,
see 4.2.2.2 Impacts.
1.5 5G RAN5.1 02 (2021-04-30)


5G RAN
Technical Changes
Change Model

parameter to control the parameters: Low- 5900 series
dynamic adjustment of Activated frequency base stations
the number of paging RSVDSWPARAM0 TDD DBS3900
frames (PFs) for power _BIT14 of the LampSite and
saving scheduling. For NRDUCellRsvdEx DBS5900
details, see 4.2.1.1 Power t02.RsvdSwPara LampSite
Saving Scheduling and m0 parameter.
4.2.4.1 Data
Configuration.
Added an impact None FDD 3900 and

relationship between Low- 5900 series
symbol power saving and frequency base stations
LTE and NR intelligent TDD DBS3900
carrier shutdown. For LampSite and
details, see 4.1.2.2 DBS5900
Impacts. LampSite
Added support for None FDD DBS3900

querying the pRRU deep Low- LampSite and
dormancy status with the frequency DBS5900
DSP BRDDORMANCY TDD LampSite
command. For details, see
4.4.4.2 Activation
Verification.
Editorial Changes
Added descriptions of the impact relationships between antenna port detection
and the following functions:
● Symbol power saving: For details, see Function Impacts.
● Deep symbol power saving: For details, see Function Impacts.
● Timing carrier shutdown: For details, see Function Impacts.
● RF channel intelligent shutdown: For details, see Function Impacts.
● Intelligent carrier shutdown: For details, see Function Impacts.
Added descriptions of the impact relationship between RF channel intelligent
shutdown and power saving BWP. For details, see Function Impacts.
1.6 5G RAN5.1 01 (2021-03-05)


5G RAN
Technical Changes
Change Model
Added a mutually None Low- DBS3900

exclusive relationship frequency LampSite and
between distributed TDD DBS5900
massive MIMO and RF LampSite
channel intelligent
shutdown. For details, see
Mutually Exclusive
Functions.
None None FDD None
Editorial Changes
Added descriptions of scenarios where a cell in the carrier shutdown state exits
this state and scenarios where the cell enters the carrier shutdown state again
after exiting. For details, see 4.3.1 Principles and 5.1.1.2 Energy Saving
Procedure.
1.7 5G RAN5.1 Draft A (2020-12-29)

This issue introduces the following changes to 5G RAN3.1 02 (2020-07-03).
Technical Changes
Change Model
Removed the mutually None FDD 3900 and

exclusive relationships Low- 5900 series
between symbol power frequency base stations
saving/deep symbol power TDD
saving and Hyper Cell/Cell
Combination. For details,
see Mutually Exclusive
Functions and Mutually
Exclusive Functions.

5G RAN

Change Model
Added the Power Saving None FDD 3900 and

State parameter to the Low- 5900 series
DSP NRDUCELLTRP frequency base stations
command output to TDD
indicate the status of
symbol power saving,
deep symbol power
saving, and multi-RAT
symbol power saving. For
details, see 4.1.4.2
Activation Verification
and 4.2.4.2 Activation
Verification.
Added protection for CSI- Modified FDD 3900 and

RS symbols against parameter: Added Low- 5900 series
symbol power saving. For the frequency base stations
details, see 4.1.4 SYM_SHUTDOW TDD DBS3900
Operation and N_CSIRS_PROTEC LampSite and
Maintenance. T_SW option to DBS5900
the LampSite
NRDUCellAlgoSw
itch.PowerSaving
Switch parameter.
Added support for Added the FDD 3900 and
converging the PDSCH NRDUCellPowerS Low- 5900 series
data in at least four aving.SymbolCo frequency base stations
symbols used for PDSCH mpressLength TDD DBS3900
data transmission within a parameter. LampSite and
slot over more frequency- DBS5900
domain resources. For LampSite
details, see Data
Convergence in Symbols
and 4.2.4.1 Data
Configuration.

5G RAN

Change Model
Modified the following Added FDD 3900 and

aspects of RF channel parameters: Low- 5900 series
intelligent shutdown. For ● NRDUCellPow frequency base stations
details, see 4.5 RF erSaving.CovC TDD DBS3900
Channel Intelligent ompensation LampSite and
Shutdown. Mode DBS5900
● Used a parameter to ● NRDUCellPow LampSite
specify whether the erSaving.CovC
transmit power ompensationP
compensated for the wrOffset
common channels of a
cell is automatically ● NRDUCellPow
determined or erSaving.User
manually configured. NumOffset
Added another
parameter to specify
the transmit power to
be compensated for
the common channels
of the cell if manual
configuration is
required.
● Added the threshold of
the number of
RRC_CONNECTED UEs
for determining
whether to enter or
exit RF channel
intelligent shutdown.
● Added support for RF
channel intelligent
shutdown by NR TDD
8T8R RF modules.
● Added support for RF
channel intelligent
shutdown by NR FDD
8T8R/4T4R/2T2R/2T4R
RF modules.
Removed the mutually None Low- DBS3900

exclusive relationship frequency LampSite and
between distributed TDD DBS5900
massive MIMO and RF LampSite
channel intelligent
shutdown. For details, see
Mutually Exclusive
Functions.

5G RAN

Change Model
Removed the mutually None FDD 3900 and

exclusive relationship Low- 5900 series
between timing carrier frequency base stations
shutdown and RF channel TDD DBS3900
intelligent shutdown. For LampSite and
details, see Mutually DBS5900
Exclusive Functions and LampSite
Mutually Exclusive
Functions.
Enabled the configuration Added the FDD 3900 and

of the period for NRDUCellPowerS Low- 5900 series
determining whether to aving.ShutdownT frequency base stations
trigger intelligent carrier rigJudgePeriod TDD DBS3900
shutdown. For details, see parameter. LampSite and
5.1.1.2 Energy Saving DBS5900
Procedure, 5.1.4.1 Data LampSite
Configuration, and
5.1.4.2 Activation
Verification.
Enabled low power None FDD 3900 and

consumption mode to Low- 5900 series
support the scenario frequency base stations
where a non-Huawei TDD
power supply system
connects to a Huawei
base station through a dry
contact port. For details,
see 6.1.1 Principles,
6.1.3.4 Others, 6.1.4.1
Data Configuration, and
6.1.4.3 Activation
Verification.
Added support for SA None High- 3900 and

networking in high- frequency 5900 series
frequency FWA scenarios. TDD base stations
For details, see 2.5
Differences Between
High Frequency Bands
and Low Frequency
Bands.

5G RAN

Change Model
Enabled the compatibility Modified Low- 3900 and

between beams and parameters: frequency 5900 series
symbol power saving to Added TDD base stations
take effect by default and BEAM_SYMSHUT DBS3900
added the switch that is DOWN_ALGO_S LampSite and
previously used to control W of the DBS5900
this compatibility to the NRDUCellAlgoSw LampSite
disuse list. For details, see itch.AlgoCompati
4.1.4.1 Data bilitySwitch
Configuration. parameter and
RSVDSWPARAM0
_BIT18 of the
NRDUCellRsvdEx
t00.RsvdSwPara
m0 parameter to
the disuse list.
Added the intelligent Added the FDD 3900 and

carrier shutdown function. NRCellRelation.P Low- 5900 series
For details, see 5.1 owerSavingCellFl frequency base stations
Intelligent Carrier ag parameter. TDD DBS3900
Shutdown. Modified LampSite and
parameters: DBS5900
● Added the LampSite
INTRA_GNB_M
ULTI_CARR_SD
_SW and
INTER_GNB_M
ULTI_CARR_SD
_SW options to
the
NRDUCellAlgo
Switch.PowerS
avingSwitch
parameter.
● Added the
values
INTRA_GNB_M
ULTI_CARR_SD
and
INTER_GNB_M
ULTI_CARR_SD
to the
NRDUCellPow
erSaving.Powe
rSavingType
parameter.

5G RAN

Change Model
Added support for timing None FDD 3900 and

carrier shutdown by NR 5900 series
FDD. For details, see 4.3 base stations
Timing Carrier DBS3900
Shutdown. LampSite and
DBS5900
LampSite
Added support for timing None Low- 3900 and

carrier shutdown by hyper frequency 5900 series
cells. For details, see 4.3 TDD base stations
Timing Carrier DBS3900
Shutdown. LampSite and
DBS5900
LampSite
Added support for low Added the FDD 3900 and

power consumption mode. NRDUCellPowerS Low- 5900 series
For details, see 6.1 Low aving.BackupPwr frequency base stations
Power Consumption SavingPolicy TDD
Mode. parameter.
Modified
parameters:
● Added the
LOW_PWR_M
ODE_SW
option to the
NRDUCellAlgo
Switch.PowerS
avingSwitch
parameter.
● Added the
LOW_PWR_M
ODE value to
the
NRDUCellPow
erSaving.Powe
rSavingType
parameter.
Added support for Added the FDD 3900 and

dynamic adjustment of NRDUCellPowerS Low- 5900 series
the RMSI broadcast aving.RmsiAdjust frequency base stations
interval at the cell and Mode parameter. TDD DBS3900
beam levels. For details, LampSite and
see Dynamic Adjustment DBS5900
of the RMSI Broadcast LampSite
Interval and 4.2.4.1 Data
Configuration.

5G RAN

Change Model
Added support for RF None Low- DBS3900

channel intelligent frequency LampSite and
shutdown in LampSite TDD DBS5900
2T2R scenarios. For LampSite
details, see RF Modules.
Added support for NR None FDD DBS3900

FDD by LampSite base LampSite and
stations. For details, see DBS5900
hardware requirement LampSite
sections for individual
functions.
Editorial Changes
Revised descriptions in this document, and deleted the descriptions about
intelligent dynamic SSB adjustment.

5G RAN
Feature Parameter Description 2 About This Document
2 About This Document
2.1 General Statements

Purpose
Feature Parameter Description documents are intended to acquaint readers with:
● The technical principles of features and their related parameters
● The scenarios where these features are used, the benefits they provide, and
the impact they have on networks and functions
● Requirements of the operating environment that must be met before feature
activation
● Parameter configuration required for feature activation, verification of feature
activation, and monitoring of feature performance
NOTE
This document only provides guidance for feature activation. Feature deployment and
feature gains depend on the specifics of the network scenario where the feature is
deployed. To achieve optimal gains, contact Huawei professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
2.2 Features in This Document

This document describes the following features.

5G RAN
Feature ID Feature Name Chapter/Section
FOFD-021203 gNodeB Power Saving 4.1 Symbol Power

Saving
4.3 Timing Carrier
Shutdown
6.1 Low Power
Consumption
Mode
FOFD-031204 Intelligent Scheduling for Power 4.2 Intelligent

Saving Scheduling for
Power Saving
FOFD-030216 pRRU Deep Dormancy 4.4 pRRU Deep

Dormancy
FOFD-031205 RF Channel Intelligent Shutdown 4.5 RF Channel

Intelligent
Shutdown
FOFD-050203 Intelligent Carrier Shutdown 5.1 Intelligent

Carrier Shutdown
FBFD-031003 PSU Intelligent Shutdown 6.3 PSU Intelligent

Shutdown
FBFD-010025 Basic O&M Package 7 Energy

Consumption
Monitoring
2.3 Differences Between NR FDD and NR TDD

Function Name Difference Chapter/Section
Symbol power Macro base station: None 4.1 Symbol Power

saving LampSite base station: Supported Saving
only in NR TDD
Intelligent None 4.2 Intelligent

scheduling for Scheduling for
power saving Power Saving
Timing carrier None 4.3 Timing Carrier

shutdown Shutdown
pRRU deep None 4.4 pRRU Deep

dormancy Dormancy

5G RAN
RF channel Macro base station: Supported in 4.5 RF Channel

intelligent both NR FDD and NR TDD. Intelligent
shutdown However, the RF modules, beam Shutdown
coverage scenarios, cell bandwidths
supporting RF channel intelligent
shutdown differ between NR FDD
and NR TDD. For details, see RF
Modules and Cells.
LampSite base station: Supported
only in NR TDD
Intelligent carrier None 5.1 Intelligent

shutdown Carrier Shutdown
Low power None 6.1 Low Power

consumption mode Consumption
Mode
Baseband chip None 6.2 Baseband Chip

shutdown Shutdown
PSU intelligent None 6.3 PSU Intelligent

shutdown Shutdown
Energy None 7 Energy

consumption Consumption
monitoring Monitoring
2.4 Differences Between NSA and SA

Symbol power None 4.1 Symbol Power

saving Saving
Intelligent None 4.2 Intelligent

scheduling for Scheduling for
Timing carrier None 4.3 Timing Carrier

shutdown Shutdown
pRRU deep None 4.4 pRRU Deep

dormancy Dormancy
RF channel None 4.5 RF Channel

intelligent Intelligent
shutdown Shutdown

5G RAN
Intelligent carrier Supported in SA networking as well 5.1 Intelligent

shutdown as NSA and SA hybrid networking, Carrier Shutdown
but not in NSA networking.
Low power None 6.1 Low Power

consumption mode Consumption
Mode
Baseband chip None 6.2 Baseband Chip

shutdown Shutdown
PSU intelligent None 6.3 PSU Intelligent

shutdown Shutdown
Energy None 7 Energy

consumption Consumption
monitoring Monitoring
NOTE
More common messages are involved on the gNodeB side in SA networking than in NSA
networking. Therefore, when the network architecture is changed from NSA to SA, the basic
energy consumption of RF modules may increase.
2.5 Differences Between High Frequency Bands and

Low Frequency Bands
This document refers to frequency bands belonging to FR1 (410–7125 MHz) as
low frequency bands, and those belonging to FR2 (24250–52600 MHz) as high
frequency bands. For details about FR1 and FR2, see section 5.1 "General" in 3GPP
TS 38.104 V15.5.0.
Symbol power Supported only in low frequency 4.1 Symbol Power

saving bands Saving
Intelligent Supported only in low frequency 4.2 Intelligent

scheduling for bands Scheduling for
Timing carrier Supported only in low frequency 4.3 Timing Carrier

shutdown bands Shutdown
pRRU deep Supported only in low frequency 4.4 pRRU Deep

dormancy bands Dormancy
RF channel Supported only in low frequency 4.5 RF Channel

intelligent bands Intelligent
shutdown Shutdown

5G RAN
Intelligent carrier Supported only in low frequency 5.1 Intelligent

shutdown bands Carrier Shutdown
Low power Supported only in low frequency 6.1 Low Power

consumption mode bands Consumption
Mode
Baseband chip Supported only in low frequency 6.2 Baseband Chip

shutdown bands Shutdown
PSU intelligent Supported in both high and low 6.3 PSU Intelligent
shutdown frequency bands, with the Shutdown
following differences:
Both SA networking and NSA
networking are supported in low
frequency bands, but only SA
networking in FWA scenarios and
NSA networking are supported in
high frequency bands.
Energy Supported in both high and low 7 Energy

consumption frequency bands, with the Consumption
monitoring following differences: Monitoring
Both SA networking and NSA
networking are supported in low
frequency bands, but only SA
networking in FWA scenarios and
NSA networking are supported in
high frequency bands.

5G RAN
Feature Parameter Description 3 Overview
3 Overview
The expanding wireless services add to network scale and increase the overall
equipment energy consumption. The resulting growth of base station energy
consumption is a major contributor to the increasing operating expense (OPEX) of
telecom operators. Huawei's energy saving solutions are launched against this
background, and they help operators improve equipment operating efficiency,
reduce equipment energy consumption and OPEX, as well as enhance product
competitiveness. The solutions can be implemented at the site, network, and
device levels.
● Device level
The energy saving solutions at this level are implemented on RF modules
from the following dimensions and involve individual cells:
– Time domain
When there is no data to be transmitted in symbols, power amplifiers
(PAs) and radio-on-a-chip (RoC) systems are shut down to reduce the
energy consumption of RF modules.
– Frequency domain
In light-load scenarios, certain carriers of RF modules or the entire RF
modules are shut down to reduce their energy consumption.
– Space domain
In light-load scenarios, certain RF channels of RF modules are shut down
to reduce RF module energy consumption.
● Network level
The energy saving solutions at this level are implemented on RF modules and
require inter-cell coordination.
● Site level
The energy saving solutions at this level are implemented on power supply
systems, baseband equipment, and others.

5G RAN
Feature Parameter Description 3 Overview
Table 3-1 Category of energy saving solutions

Category Sub- Energy Saving Solution
Category
Device Time 4.1 Symbol Power Saving

level domain 4.2 Intelligent Scheduling for Power Saving
Frequency 4.3 Timing Carrier Shutdown

domain 4.4 pRRU Deep Dormancy
Space 4.5 RF Channel Intelligent Shutdown

domain
Network N/A 5.1 Intelligent Carrier Shutdown

level
Site level N/A 6.1 Low Power Consumption Mode

6.2 Baseband Chip Shutdown
6.3 PSU Intelligent Shutdown
Operators can query base stations' or base station equipment's energy

consumption distribution and changes through the MAE-Access. For details, see 7
Energy Consumption Monitoring.

5G RAN
Feature Parameter Description 4 Device Level Energy Saving
4 Device Level Energy Saving
4.1 Symbol Power Saving
4.1.1 Principles
Among all devices within a base station, PAs of RF modules have the highest
power consumption and consume power even when there is no signal output.
Symbol power saving is introduced to reduce energy consumption while ensuring
data transmission integrity, as shown in Figure 4-1.
● When the base station detects that no data needs to be transmitted in a

downlink symbol, it shuts down the PAs of RF modules in real time to reduce
energy consumption.
● When the base station detects that data needs to be transmitted in a
downlink symbol, it starts the PAs in real time to ensure data transmission
integrity.
Figure 4-1 Working principles of symbol power saving
Symbol power saving can be enabled by setting the

NRDUCellAlgoSwitch.SymbolShutdownSwitch parameter to ON.
4.1.2 Network Analysis
4.1.2.1 Benefits
When no data is transmitted in some symbols, the PAs of the RF modules are shut
down for these symbols in real time to reduce energy consumption.

5G RAN
However, when the temperature differential of RF modules is excessively large,

energy saving gains may decrease. This is to prevent energy saving–triggered
shutdown from affecting the lifespan of RF modules.
4.1.2.2 Impacts
Network Impacts
None
Function Impacts
RAT Function Function Switch Reference Description
Name
FDD Intelligent INTRA_GNB_MUL Energy When intelligent

Low- carrier TI_CARR_SD_SW Conservation carrier shutdown
frequency shutdown or and Emission takes effect for a
TDD INTER_GNB_MUL Reduction carrier:
TI_CARR_SD_SW ● If the RF
option of the module is not
NRDUCellAlgoSw serving any
itch.PowerSaving other NR
Switch parameter carrier, symbol
power saving
does not take
effect.
● If the RF
module is
serving other
NR carriers, the
status of
symbol power
saving for
these carriers is
not affected.

5G RAN

Name
FDD Timing TIMING_CARRIER Energy When timing

Low- carrier _SHUTDOWN_S Conservation carrier shutdown
frequency shutdown W option of the and Emission takes effect for a
TDD NRDUCellAlgoSw Reduction carrier:
itch.PowerSaving ● If the RF
Switch parameter module is not
serving any
other NR
carrier, symbol
power saving
does not take
effect.
● If the RF
module is
serving other
NR carriers, the
status of
symbol power
saving for
these carriers is
not affected.
Low- RF RRU.DORMANCY RF Module Symbol power

frequency module SW (LTE eNodeB, Deep saving does not
TDD deep 5G gNodeB) Dormancy take effect when
dormancy RF module deep
dormancy is in
effect.
FDD Antenna STR MIMO The number of

port ANTENNAPORTO times symbol
detection PTDET power saving
takes effect
decreases during
antenna port
detection.
FDD LTE and NR: LTE and NR Symbol power

Low- NR LNR_SMART_CAR Intelligent saving does not
frequency intelligent RIER_SHUTDOW Carrier take effect when
TDD carrier N_SW option of Shutdown LTE and NR
shutdown the intelligent carrier
NRDUCellAlgoSw shutdown is in
itch.PowerSaving effect.
Switch parameter
LTE:
CellAlgoExtSwitc
h.LnrSmartCarrie
rShutdownSw

5G RAN
4.1.3 Requirements
4.1.3.1 Licenses
Feature ID Feature Name Model Sales Unit
FOFD-021203 gNodeB Power NR0S0GNBPS00 per Cell

Saving
4.1.3.2 Software
Prerequisite Functions
None
Mutually Exclusive Functions

None
4.1.3.3 Hardware
Base Station Models

3900 and 5900 series base stations. 3900 series base stations must be configured
with the BBU3910.
DBS3900 LampSite and DBS5900 LampSite. DBS3900 LampSite must be
configured with the BBU3910.
Boards
All NR-capable main control boards and baseband processing units support this
function. For details, see the BBU technical specifications in 3900 & 5900 Series
Base Station Product Documentation.
RF Modules
All NR-capable AAUs/RRUs that work in low frequency bands and are configured
only with NR carriers, except those for which the Description parameter value
includes "V3" in the command output of DSP BRDMFRINFO, support this
function. For details about such RF modules, see technical specifications of the
related RF modules in 3900 & 5900 Series Base Station Product Documentation.
All NR TDD-capable pRRU596x modules that are configured only with NR carriers
support this function. For details about such RF modules, see technical
specifications of the related RF modules in 3900 & 5900 Series Base Station
Product Documentation.

5G RAN
4.1.3.4 Networking
When multiple RATs share an RF module, the NR cells enter the symbol power
saving state only when this function takes effect for activated cells of all RATs
sharing the same channel. The NR cells exit the symbol power saving state if any
cell of any RAT exits this state.
4.1.3.5 Others
None
4.1.4 Operation and Maintenance
4.1.4.1 Data Configuration
4.1.4.1.1 Data Preparation

Table 4-1 describes the parameters used for function activation. Function
optimization configurations are not involved. This section does not describe
parameters related to cell establishment.
Table 4-1 Parameters used for activation

Parameter Name Parameter ID Setting Notes
Symbol Shutdown NRDUCellAlgoSwitch.Symb It is recommended that

Switch olShutdownSwitch this switch be turned on.
If an RF module serves
multiple NR cells, it is
recommended that the
same setting for this
switch be used across all
NR cells.
Power Saving Switch NRDUCellAlgoSwitch.Powe It is recommended that

rSavingSwitch the
SYM_SHUTDOWN_CSIRS
_PROTECT_SW option of
this parameter be
selected to enable
protection for CSI-RS
symbols against symbol
power saving. This
prevents possible CSI-RS
transmission failures. This
option is selected by
default.

5G RAN
NOTE
This function applies to an NR TDD or NR FDD cell. That is, the NRDUCell.DuplexMode
parameter must be set to CELL_TDD or CELL_FDD. This function is configurable but does
not take effect in a cell with the NRDUCell.DuplexMode parameter set to CELL_SUL.
4.1.4.1.2 Using MML Commands

Before using MML commands, refer to 4.1.2.2 Impacts and complete the
parameter configurations for related functions based on the impact relationships
between the functions, as well as the actual network scenario.
Activation Command Examples

//Enabling symbol power saving
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, SymbolShutdownSwitch=ON;
//(Optional) Enabling protection for CSI-RS symbols against symbol power saving
MOD NRDUCELLALGOSWITCH: NrDuCellId=0,
PowerSavingSwitch=SYM_SHUTDOWN_CSIRS_PROTECT_SW-1;
Optimization Command Examples

N/A
Deactivation Command Examples

//Disabling symbol power saving
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, SymbolShutdownSwitch=OFF;
//(Optional) Disabling protection for CSI-RS symbols against symbol power saving
PowerSavingSwitch=SYM_SHUTDOWN_CSIRS_PROTECT_SW-0;
4.1.4.1.3 Using the MAE-Deployment

For detailed operations, see Feature Configuration Using the MAE-Deployment.
4.1.4.2 Activation Verification

1. Run the LST NRDUCELLALGOSWITCH command. If the value of the Symbol
Shutdown Switch parameter is On in the command output, symbol power
saving has been enabled.
2. Run the DSP NRDUCELL command to check the symbol power saving state of
the cell.
– If the value of the Symbol Shutdown State parameter is Symbol Power
Saving, symbol power saving has taken effect in at least one TRP of the
cell.
– If the value of the Symbol Shutdown State parameter is Not Started,
symbol power saving has not taken effect in the cell. The possible reasons
are as follows:
▪ The RF module does not support symbol power saving. For details
about the requirements on RF modules, see RF Modules.
▪ The license item "gNodeB Power Saving" has not been acquired.
▪ The NRDUCell.DuplexMode parameter is set to CELL_SUL.

5G RAN
3. (Optional) For a hyper cell or combined cell, run the DSP NRDUCELLTRP
command to query the symbol power saving state of each TRP in the cell.
– If the value of the Power Saving State parameter is Symbol Power
Saving:Enabled for a TRP, symbol power saving has taken effect in the
TRP.
– If the value of the Power Saving State parameter is Symbol Power
Saving:Disabled for a TRP, symbol power saving has not taken effect in
the TRP. The possible reasons are as follows:
▪ The RF module does not support symbol power saving. For details
about the requirements on RF modules, see RF Modules.
▪ The license items "gNodeB Power Saving" are insufficient.
NOTE
For details about the consumption principles of feature license items in hyper
cells or combined cells, see Hyper Cell (Low-Frequency TDD) or Cell
Combination.
4.1.4.3 Network Monitoring

● Energy consumption data for base stations can be obtained by using the
counter VS.EnergyCons.BTS.Adding.NR (for a base station) or
VS.EnergyCons.BTSBoard (for RF modules) on the MAE-Access.
On the live network, the one-week base station energy consumption data
obtained before and after symbol power saving is enabled can be compared
to assess the energy saving gains of this function. It is expected that the base
station energy consumption decreases significantly after this function is
enabled.
● The time that a cell spends in the symbol power saving state can be obtained
by using the N.PowerSaving.SymbolShutdown.Dur counter on the MAE-
Access.
4.2 Intelligent Scheduling for Power Saving
4.2.1 Principles
In symbols without data transmission, symbol power saving enables the base
station to shut down the PAs of RF modules in real time. This reduces power
consumption. Intelligent scheduling for power saving increases the number of or
adds shutdown depth to symbols without data transmission. This further reduces
power consumption on the basis of symbol power saving. Intelligent scheduling
for power saving has two functions: power saving scheduling and deep symbol
power saving.
● Power saving scheduling: Intelligent time-domain scheduling frees more

symbols from data transmission, allowing symbol power saving to take effect
for a longer period, and ultimately saving more power.
● Deep symbol power saving: The components shut down for symbol power
saving are intelligently adjusted based on the capabilities of RF modules,

5G RAN
allowing symbol power saving to take effect at a deeper level, again, saving
more power.
4.2.1.1 Power Saving Scheduling

Power saving scheduling uses the following four methods to free more symbols
from data transmission: dynamic adjustment of the RMSI broadcast interval,
dynamic adjustment of the number of paging frames (PFs), data convergence in
symbols, and data convergence in slots. Power saving scheduling can be enabled
by selecting the POWER_SAVING_SCHEDULE_SW option of the
NRDUCellAlgoSwitch.PowerSavingSwitch parameter. The effective period, load
threshold, and other information under an energy saving policy for power saving
scheduling are specified by the parameters in the NRDUCellPowerSaving MO.
● The NRDUCellPowerSaving.PowerSavingPolicyIndex parameter specifies an
energy saving policy index. It uniquely identifies an energy saving policy
within the local cell. With the index specified, the corresponding policy can be
added, modified, queried, or removed for the local cell.
● The NRDUCellPowerSaving.PowerSavingType parameter specifies the
energy saving type indicated by an energy saving policy index. Power saving
scheduling requires that this parameter be set to
POWER_SAVING_SCHEDULE.
● The NRDUCellPowerSaving.StartTime and
NRDUCellPowerSaving.StopTime parameters specify the energy saving start
time and stop time indicated by an energy saving policy index, respectively.
Power saving scheduling takes effect every day within the configured period.
● The NRDUCellPowerSaving.DlPrbThld parameter specifies the downlink PRB
usage threshold indicated by an energy saving policy index.
Within the specified power saving scheduling periods, if the downlink PRB usage
of a cell (which equals N.PRB.DL.DrbUsed.Avg divided by
N.PRB.DL.Actual.Avail.Avg) is less than or equal to the downlink PRB usage
threshold for starting power saving scheduling (specified by the
NRDUCellPowerSaving.DlPrbThld parameter), the cell automatically enters the
power saving scheduling state. Dynamic Adjustment of the RMSI Broadcast
Interval, Dynamic Adjustment of the Number of PFs, Data Convergence in
Symbols, or Data Convergence in Slots is performed to free more symbols from
data transmission. A cell in the power saving scheduling state automatically exits
this state if any of the following conditions is met:
● The current time is not within the power saving scheduling period specified by
the NRDUCellPowerSaving.StartTime and
NRDUCellPowerSaving.StopTime parameters.
● The downlink PRB usage of the cell is greater than the
NRDUCellPowerSaving.DlPrbThld parameter value plus 5%.
Dynamic Adjustment of the RMSI Broadcast Interval

When the base station detects the network is under light or no load, it prolongs
the RMSI broadcast interval to increase the number of symbols with no data
transmission. When the base station detects that the network load is normal, it
restores the RMSI broadcast interval. As shown in Figure 4-2, the RMSI broadcast
interval can be extended to a maximum of 160 ms.

5G RAN
Figure 4-2 Dynamic adjustment of the RMSI broadcast interval
The RMSI broadcast interval can be dynamically adjusted at the cell or beam level,
depending on the setting of the NRDUCellPowerSaving.RmsiAdjustMode
parameter.
● If this parameter is set to CELL, the RMSI broadcast interval is dynamically
adjusted at the cell level. The base station dynamically adjusts the RMSI
broadcast interval for all synchronization signal and PBCH block (SSB) beams
when the number of RRC_CONNECTED UEs in the cell (indicated by
N.User.RRCConn.Avg) is less than or equal to the
NRDUCellPowerSaving.UserNumThld parameter value.
● If this parameter is set to BEAM, the RMSI broadcast interval is dynamically
adjusted at the beam level. The base station dynamically adjusts the RMSI
broadcast intervals for individual SSB beams when the number of
RRC_CONNECTED UEs in each beam (indicated by N.User.RRCConn.Avg) is
less than or equal to the NRDUCellPowerSaving.UserNumThld parameter
value.
Dynamic Adjustment of the Number of PFs

When the base station detects that the network is lightly loaded or unloaded, it
reduces the number of PFs sent within a paging cycle (referred to as T) to increase
the number of symbols with no data transmission. When the base station detects
that the network load is normal, it restores the number of PFs sent within T.
Dynamic adjustment of the number of PFs does not take effect by default. This
function takes effect, as shown in Figure 4-3, only when power saving scheduling
is in effect and RSVDSWPARAM0_BIT14 of the
NRDUCellRsvdExt02.RsvdSwParam0 parameter is set to 1.
Figure 4-3 Dynamic adjustment of the number of PFs

5G RAN
Data Convergence in Symbols

Based on the size of the physical downlink shared channel (PDSCH) data to be
transmitted, the base station converges the PDSCH data to be transmitted in
certain symbols into other symbols used for PDSCH data transmission within the
same slot over more frequency-domain resources. This way, PDSCH data occupies
fewer time-domain resources but more frequency-domain resources, thereby
increasing the number of symbols with no data transmission. Data convergence in
symbols takes effect only when power saving scheduling is in effect and
RSVDSWPARAM0_BIT26 of the NRDUCellRsvdExt02.RsvdSwParam0 parameter
is set to 0. The number of occupied symbols after convergence is specified by the
NRDUCellPowerSaving.SymbolCompressLength parameter.
● If this parameter is set to 7SYMBOL, PDSCH data is converged in at least
seven symbols used for PDSCH data transmission within a slot over more
frequency-domain resources, as shown in Figure 4-4.
Figure 4-4 Data convergence in seven symbols
● If this parameter is set to 4SYMBOL, PDSCH data is converged in at least four

symbols used for PDSCH data transmission within a slot over more frequency-
domain resources, as shown in Figure 4-5.

5G RAN
Figure 4-5 Data convergence in four symbols
Data Convergence in Slots

As shown in Figure 4-6, the base station converges and sends PDSCH data in the
slots corresponding to the master information block (MIB), system information
block 1 (SIB1), other system information (OSI), or paging. This centralizes PDSCH
data scheduling in the time domain and increases the number of symbols with no
data transmission. This process also increases the scheduling delay to a certain
extent. Data convergence in slots takes effect only when power saving scheduling
is in effect and RSVDSWPARAM0_BIT27 of the
NRDUCellRsvdExt02.RsvdSwParam0 parameter is set to 0.
The NRDUCellRsvdExt02.RsvdParam7 parameter specifies the RLC first packet

delay threshold for data convergence in slots. If the first packet delay of UEs is less
than or equal to this threshold, the data to be scheduled is converged before
transmission. If the first packet delay of UEs is greater than this threshold, the
data is directly scheduled for UEs. A lower threshold results in a lower degree of
data convergence, lower energy saving gains, and a smaller decrease in the
downlink user-perceived rate. A higher threshold results in the opposite effects.
The function of non-first packet scheduling optimization for data convergence in

slots is controlled by RSVDSWPARAM2_BIT10 of the
NRDUCellRsvdExt02.RsvdSwParam2 parameter. If this bit is set to 0, the
scheduling optimization takes effect. In this case, scheduling is performed in slots

5G RAN
where there are non-first packets. If this bit is set to 1, the scheduling optimization
does not take effect.
Figure 4-6 Data convergence in slots
4.2.1.2 Deep Symbol Power Saving

Among base station devices, RoC systems of RF modules consume much power.
They consume power even when there is no signal output. Deep symbol power
saving is introduced to reduce energy consumption while ensuring data
transmission integrity, as shown in Figure 4-7.
● When the base station detects that no data needs to be transmitted in a
downlink symbol, it shuts down the RoC systems of RF modules in real time
to reduce energy consumption.
● When the base station detects that data needs to be transmitted in a
downlink symbol, it starts the RoC systems in real time to ensure data
transmission integrity.

5G RAN
Figure 4-7 Working principles of deep symbol power saving
Deep symbol power saving can be enabled by selecting the

DEEP_SYMBOL_SHUTDOWN_SW option of the
NRDUCellAlgoSwitch.PowerSavingSwitch parameter.
4.2.2.1 Benefits
When the network is under light or no load, enabling intelligent scheduling for
power saving can further increase energy saving gains and reduce power
consumption on the basis of Symbol Power Saving.
Dynamic adjustment of the RMSI broadcast interval provides no energy saving
gains if no RMSI is broadcast on SSB beams or the RMSI broadcast interval has
been set to 160 ms.
4.2.2.2 Impacts
Network Impacts
Deep symbol power saving has no impact on the network. Power saving
scheduling has the following impacts on the network:
● The access delay of UEs camping on this cell in idle mode increases slightly.
For UEs in connected mode in the cell, the maximum waiting delay reaches
10% of the packet delay budget (PDB) corresponding to the QoS class
identifier (QCI) of the bearer carrying the data packets, and the uplink ping
delay increases.
● If the gNBPdcpParamGroup.DlDataPdcpSplitMode parameter is set to
SCG_AND_MCG in LTE FDD and NR Flash Dynamic Spectrum Sharing
scenarios, the downlink throughput of the NR cell decreases.
● As common messages may be sent at longer intervals, the following changes
may occur:
– The number of random accesses decreases.
– The average CCE aggregation level decreases.
– The CCE usage decreases.
– The PRB usage decreases.
● When dynamic adjustment of the number of PFs takes effect, UEs are
informed of the changes in the number of PFs through updated system
information. If the UEs do not receive the updated system information due to
poor signal quality, paging failures may occur.
● When data convergence in symbols takes effect, fewer time-domain resources
but more frequency-domain resources are occupied, which may lead to an
increase in the PRB usage. The downlink PRB usage of the cell (indicated by

5G RAN
N.PRB.DL.DrbUsed.Avg divided by N.PRB.DL.Actual.Avail.Avg) is higher

when the NRDUCellPowerSaving.SymbolCompressLength parameter is set
to 4SYMBOL than when this parameter is set to 7SYMBOL.
● With data convergence in slots enabled, small packets are aggregated into
large packets and the MU-MIMO pairing probability increases after downlink
bundled scheduling. This may increase the interference, bit error rate, number
of retransmissions, delay, and PRB usage, and may decrease the user-
perceived rate. In addition, the number of PDSCH scheduling times decreases
after downlink bundled scheduling, possibly reducing interference to the
channel state information reference signals (CSI-RSs). This may increase the
values of certain channel quality indicator (CQI) counters
(N.ChMeas.CQI.SingleCW.0 to N.ChMeas.CQI.SingleCW.15), possibly
increasing the MCS index and the user-perceived rate and decreasing the PRB
usage. Therefore, it is difficult to determine the actual changes to the user-
perceived rate.
Function Impacts
Name

Switch parameter carrier, power
saving
scheduling and
deep symbol
power saving
do not take
effect.
● If the RF
module is
serving other
NR carriers, the
status of
power saving
scheduling and
that of deep
symbol power
saving for
these carriers
are not
affected.

5G RAN

Name
FDD CMAS gNBSibConfig.Sib CMAS When power

Low- Type set to saving scheduling
frequency SIB_TYPE_8 takes effect, the
TDD interval at which
system
information is
sent changes,
occasionally
resulting in some
incoming CMAS
warning
notifications being
missed by UEs.
However, CMAS
warning
notifications are
usually sent on
the CBC side
multiple times,
increasing the
probability for
UEs to receive
them in power
saving scheduling
scenarios.

5G RAN

Name
Low- RF RF_SHUTDOWN_ Energy If power saving

frequency channel SW option of the Conservation scheduling has
TDD intelligent NRDUCellAlgoSw and Emission taken effect and
shutdown itch.PowerSaving Reduction RF channel
Switch parameter intelligent
shutdown is
enabled in the
scenarios listed in
Table 4-12, power
saving scheduling
may stop. It is
recommended
that a larger
downlink PRB
usage threshold
be configured for
power saving
scheduling in the
period intended
for both RF
channel
intelligent
shutdown and
power saving
scheduling to take
effect.
For 8T8R RF
modules, when RF
channel
intelligent
shutdown takes
effect, beam-level
adjustment of the
RMSI broadcast
interval in power
saving scheduling
does not take
effect. Therefore,
cell-level
adjustment of the
RMSI broadcast
interval is
recommended in
such cases.

5G RAN

Name
Low- RF RRU.DORMANCY RF Module Power saving

frequency module SW (LTE eNodeB, Deep scheduling and
TDD deep 5G gNodeB) Dormancy deep symbol
dormancy power saving do
not take effect
when RF module
deep dormancy is
in effect.
FDD Downlink RB_ESTIMATE_O Scheduling If data

Low- RB PT_SW option of convergence in
frequency estimatio the symbols takes
TDD n NRDUCellPdsch. effect but
optimizati DlPdschAlgoSwit downlink RB
on ch parameter estimation
optimization does
not take effect,
the user-perceived
rate may
decrease. It is
recommended
that downlink RB
estimation
optimization be
enabled when
data convergence
in symbols is in
effect.

5G RAN

Name
FDD Common SSB_INTRF_AVOI Interference Assume that cell

Low- channel D_SW option of Avoidance B is a neighboring
frequency interferen the cell of cell A. If
TDD ce NRDUCellAlgoSw the RMSI
avoidance itch.CommChnInt broadcast interval
rfAvoidSwitch of cell A is
parameter adjusted,
interference may
occur between
the PDSCH of cell
A and common
messages of cell
B, possibly
decreasing the
downlink
throughput of cell
A. It is
recommended
that common
channel
interference
avoidance be
enabled in both
cell A and cell B.

serving any
other NR
carrier, deep
symbol power
saving does
not take effect.
● If the RF
module is
serving other
NR carriers, the
status of deep
symbol power
saving for
these carriers is
not affected.

5G RAN

Name
FDD Antenna STR MIMO The number of

port ANTENNAPORTO times deep
detection PTDET symbol power
saving takes
effect decreases
during antenna
port detection.
4.2.3 Requirements
4.2.3.1 Licenses
FOFD-031204 Intelligent NR0S000PSS00 per Cell

Scheduling for
Power Saving
4.2.3.2 Software
Before activating this function, ensure that its prerequisite functions have been
activated and mutually exclusive functions have been deactivated. For detailed
operations, see the relevant feature documents.
Name
FDD Symbol NRDUCellAlgoSw Energy Power saving

Low- power itch.SymbolShut Conservation scheduling and
frequency saving downSwitch and Emission deep symbol
TDD Reduction power saving
depend on symbol
power saving.

5G RAN

RAT Function Function Reference Description
Name Switch
Low- Hyper Cell NRDUCell.N Hyper Cell Power saving

frequency rDuCellNet (Low- scheduling cannot
TDD workingMod Frequency be enabled for a
e set to TDD) hyper cell served
HYPER_CELL by a macro base
station.
Power saving
scheduling can be
enabled for a
hyper cell served
by a LampSite
base station.
FDD Cell NRDUCell.N Cell Power saving

Low- Combination rDuCellNet Combination scheduling cannot
frequency workingMod be enabled for a
TDD e set to combined cell
HYPER_CELL served by a macro
_COMBINE_ base station.
MODE Power saving
scheduling can be
enabled for a
combined cell
served by a
LampSite base
station.
FDD Timing TIMING_CAR Energy The periods

Low- carrier RIER_SHUTD Conservation configured for
frequency shutdown OWN_SW and Emission power saving
TDD option of the Reduction scheduling cannot
NRDUCellAl overlap with
goSwitch.Po those configured
werSavingS for timing carrier
witch shutdown of the
parameter same cell. You are
advised to
preferentially plan
the periods during
which timing
carrier shutdown
takes effect.

5G RAN
4.2.3.3 Hardware
Base Station Models

with the BBU3910.

NOTE
LampSite base stations do not support the beam-level adjustment of the RMSI broadcast
interval or deep symbol power saving.
Boards
RF Modules
For dynamic adjustment of beam-level RMSI broadcast interval, all NR-capable RF
modules that work in 8T8R or a higher specification and in low frequency bands,
except those for which the Description parameter value includes "V3" in the
command output of DSP BRDMFRINFO, support this function. For details about
such RF modules, see technical specifications of the related RF modules in 3900 &
5900 Series Base Station Product Documentation.
For the deep symbol power saving function and the power saving scheduling
functions except dynamic adjustment of beam-level RMSI broadcast interval, all
NR-capable RF modules that work in low frequency bands, except those for which
the Description parameter value includes "V3" in the command output of DSP
BRDMFRINFO, support these functions. For details about such RF modules, see
technical specifications of the related RF modules in 3900 & 5900 Series Base
Station Product Documentation.
4.2.3.4 Others
None

Table 4-2 and Table 4-3 describe the parameters used for function activation and
optimization, respectively. This section does not describe parameters related to cell
establishment.

5G RAN

Paramet Parameter ID Option Setting Notes
er Name
NR DU NRDUCellAlgoSwitch None Set this parameter based on

Cell ID .NrDuCellId the network plan.
Power NRDUCellAlgoSwitch None ● Select the

Saving .PowerSavingSwitch POWER_SAVING_SCHED
Switch ULE_SW option of this
parameter to enable
● Select the
DEEP_SYMBOL_SHUTDO
WN_SW option of this
parameter to enable deep
symbol power saving.
Power NRDUCellPowerSav- None Set this parameter based on

Saving ing.PowerSavingPoli- the network plan.
Policy cyIndex
Index
Start NRDUCellPowerSav- None Set this parameter based on

Time ing.StartTime the network plan and the
following requirements:
● For a policy of an energy
saving function, the
interval between the stop
time and start time must
be longer than 20
minutes.
If the stop time is earlier
than or the same as the
start time, it is assumed
that the stop time refers
to the next day. For
example:
If the start time is set to
08:00 and the stop time is
set to 07:00, the period for
enabling the related
energy saving function is
from 08:00 to 07:00 the
next day.
● For different policies of an
energy saving function,
the interval between the
stop time of one policy
and the start time of
another must be longer
than 5 minutes. For

5G RAN

er Name
Stop NRDUCellPowerSav- None example, if policy B of an

Time ing.StopTime energy saving function
needs to be enabled after
policy A of this function
has been enabled, the
start time of policy B must
be 5 minutes later than
the stop time of policy A.
Power NRDUCellPowerSav- None Set this parameter to

Saving ing.PowerSavingType POWER_SAVING_SCHEDULE
Type .
Downlink NRDUCellPowerSav- None You are advised to set this

PRB ing.DlPrbThld parameter to its
Threshold recommended value.
If RF channel intelligent
shutdown is enabled in the
scenarios listed in Table 4-12
and a power saving
scheduling policy is
configured in the same
period, it is recommended
that this parameter be set to
a large value. This setting
prevents power saving
scheduling from being
stopped when RF channel
intelligent shutdown takes
effect.
UE NRDUCellPowerSav- None You are advised to set this

Number ing.UserNumThld parameter to its
Threshold recommended value.
RMSI NRDUCellPowerSav- None The value BEAM is

Adjust ing.RmsiAdjustMode recommended.
Mode
Symbol NRDUCellPowerSav- None The value 4SYMBOL is

Compress ing.SymbolCompress recommended.
Length Length

5G RAN

er Name
Reserved NRDUCellRsvdExt02. None Dynamic adjustment of the

Switch RsvdSwParam0 number of PFs does not take
Paramete effect by default. To obtain
r0 more energy saving gains, set
RSVDSWPARAM0_BIT14 of
this reserved parameter to 1
to enable this function.
RSVDSWPARAM0_BIT26 and
RSVDSWPARAM0_BIT27 are
set to 0 by default, which
means that data convergence
in symbols and data
convergence in slots take
effect by default.
The settings of the preceding
three bits take effect only
when the
POWER_SAVING_SCHEDULE
_SW option of the
NRDUCellAlgoSwitch.Power
SavingSwitch parameter is
selected.
Reserved NRDUCellRsvdExt02. None You are advised to set this

Paramete RsvdParam7 parameter to its
r7 recommended value. This
reserved parameter indicates
the RLC first packet delay
threshold for data
convergence in slots in power
saving scheduling.
Reserved NRDUCellRsvdExt02. RSVDSWPA You are advised to set this bit

Switch RsvdSwParam2 RAM2_BIT1 to its recommended value.
Paramete 0 This bit is used to control the
r2 function of non-first packet
scheduling optimization for
data convergence in slots.
Table 4-3 Parameters used for optimization

Parameter Parameter ID Setting Notes
Name
Downlink NRDUCellPdsch.Dl Select the RB_ESTIMATE_OPT_SW

PDSCH PdschAlgoSwitch option of this parameter to enable
Algorithm downlink RB estimation optimization.
Switch

5G RAN

Name
Common NRDUCellAlgoSwi Select the SSB_INTRF_AVOID_SW

Channel tch.CommChnIntr option of this parameter to enable SSB
Interference fAvoidSwitch interference avoidance.
Avoid Switch
NOTE
Power saving scheduling and deep symbol power saving apply to an NR TDD or NR FDD
cell. That is, the NRDUCell.DuplexMode parameter must be set to CELL_TDD or
CELL_FDD. These functions are configurable but do not take effect in a cell with this
parameter set to CELL_SUL.
A larger value of the NRDUCellPowerSaving.UserNumThld parameter results in a higher
probability of triggering dynamic adjustment of the RMSI broadcast interval after a cell
enters the power saving scheduling state but a possible decrease in the
N.User.RRCConn.Avg counter.

Before using MML commands, refer to 4.2.2.2 Impacts and 4.2.3.2 Software and
complete the parameter configurations for related functions based on the impact,
dependency, and mutually exclusive relationships between the functions, as well
as the actual network scenario.

//Enabling power saving scheduling
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=POWER_SAVING_SCHEDULE_SW-1;
//Enabling dynamic adjustment of the number of PFs
MOD NRDUCellRsvdExt02: NrDuCellId=0, RsvdSwParam0=RSVDSWPARAM0_BIT14-1;
//Enabling data convergence in symbols
//Enabling data convergence in slots and setting the RLC first packet delay threshold
MOD NRDUCELLRSVDEXT02: NrDuCellId=0, RsvdParam7=0, RsvdSwParam0=RSVDSWPARAM0_BIT27-0;
//Enabling the function of non-first packet scheduling optimization for data convergence in slots
MOD NRDUCELLRSVDEXT02: NrDuCellId=0, RsvdSwParam2=RSVDSWPARAM2_BIT10-0;
//Setting an energy saving policy of power saving scheduling
ADD NRDUCELLPOWERSAVING: NrDuCellId=0, PowerSavingPolicyIndex=0, StartTime=01&00&00,
StopTime=03&00&00, PowerSavingType=POWER_SAVING_SCHEDULE, DlPrbThld=10,
RmsiAdjustMode=BEAM, UserNumThld=20, SymbolCompressLength=4SYMBOL;
//(Optional) Setting another energy saving policy of power saving scheduling
StopTime=05&00&00, PowerSavingType=POWER_SAVING_SCHEDULE, DlPrbThld=10,
RmsiAdjustMode=BEAM, UserNumThld=20, SymbolCompressLength=4SYMBOL;
//Enabling deep symbol power saving
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=DEEP_SYMBOL_SHUTDOWN_SW-1;

//Enabling downlink RB estimation optimization
MOD NRDUCELLPDSCH: NrDuCellId=0, DlPdschAlgoSwitch=RB_ESTIMATE_OPT_SW-1;
//Enabling SSB interference avoidance
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, CommChnIntrfAvoidSwitch=SSB_INTRF_AVOID_SW-1;

5G RAN

The following provides only deactivation command examples. You can determine
whether to restore the settings of other parameters based on actual network
conditions.
//Disabling power saving scheduling
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=POWER_SAVING_SCHEDULE_SW-0;
//Disabling dynamic adjustment of the number of PFs
//Disabling data convergence in symbols
//Disabling data convergence in slots
//Disabling the function of non-first packet scheduling optimization for data convergence in slots
//Removing an energy saving policy of power saving scheduling
RMV NRDUCELLPOWERSAVING: NrDuCellId=0, PowerSavingPolicyIndex=0;
//(Optional) Removing the other energy saving policy of power saving scheduling
//Disabling deep symbol power saving
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=DEEP_SYMBOL_SHUTDOWN_SW-0;


Activation Verification for Power Saving Scheduling and Activation
Verification for Deep Symbol Power Saving describe how to check whether
power saving scheduling and deep symbol power saving have taken effect.
Activation Verification for Power Saving Scheduling

After the power saving scheduling function is activated, use either of the following
methods to check whether the function has taken effect:
● Method 1:
a. Run the LST NRDUCELLALGOSWITCH command. If the value of the
Power Saving Switch parameter is Power Saving Scheduling Switch:On
in the command output, power saving scheduling has been enabled.
b. Run the LST NRDUCELLPOWERSAVING command. Verify that there is at
least one record with Power Saving Type being Power Saving
Scheduling.
NOTE
If there are two or more records with Power Saving Type being Power Saving
Scheduling, power saving scheduling has been enabled in two or more time
periods.
c. Run the DSP TIME command. Check whether the system time is within a
power saving scheduling period.
▪ If it is, go to d.
▪ If it is not, wait until the start time of power saving scheduling

arrives.

5G RAN
d. Check whether the downlink PRB usage of the cell (which equals
N.PRB.DL.DrbUsed.Avg divided by N.PRB.DL.Actual.Avail.Avg) is less
than or equal to the downlink PRB usage threshold for starting power
saving scheduling (specified by the NRDUCellPowerSaving.DlPrbThld
parameter).
▪ If it is, go to e.
▪ If it is not, wait until the downlink PRB usage of the local cell is less
than or equal to the downlink PRB usage threshold for starting
e. Wait 5 minutes and then run the DSP NRDUCELL command. Verify that
the value of the Power Saving State parameter is Power Saving
Scheduling:Enabled, which indicates that power saving scheduling has
taken effect.
● Method 2:
Run the DSP NRDUCELLPOWERSAVING command to query the status of
– If the value of Power Saving Type is Power Saving Schedule and the
value of Current State is Enabled, power saving scheduling has taken
effect.
– If the value of Power Saving Type is Power Saving Schedule and the
value of Current State is Disabled, check the Current Disabled Cause
parameter value to determine the reason why power saving scheduling
does not take effect. Table 4-4 lists possible reasons.
Table 4-4 Possible reasons why power saving scheduling does not take
effect
Reason Description
Insufficient License No license for this function is

available.
Switch Turned Off None
Cell Unavailable The cell is blocked or deactivated,

fails to be set up, or is unavailable
due to other reasons.
Triggering Time Not Reached The current time is not within the
range specified for power saving
scheduling.
Prerequisite Feature Not Taken Symbol power saving has not

Effect taken effect.
Downlink PRB Threshold Not None

Reached
In Penalty State A penalty is being imposed upon

an exit from the power saving
scheduling state.

5G RAN
Reason Description
Impacted Feature Taken Effect None
Others ● The current time is within the

time range specified for power
saving scheduling, but this
function is in its detection
period, which lasts for 5
minutes.
● None of the counters is
subscribed to.
● Internal software or other
reasons cause the function to
fail.
Activation Verification for Deep Symbol Power Saving

1. Run the LST NRDUCELLALGOSWITCH command. If the value of the Power
Saving Switch parameter is Deep Symbol Power Saving Switch:On in the
command output, deep symbol power saving has been enabled.
2. Run the DSP NRDUCELL command to check the deep symbol power saving
state of the cell.
– If the value of the Power Saving State parameter is Deep Symbol
Power Saving:Enabled, deep symbol power saving has taken effect in at
least one TRP of the cell.
Power Saving:Disabled, deep symbol power saving has not taken effect
in the cell. The possible reasons are as follows:
▪ The license item "Intelligent Scheduling for Power Saving" has not
been acquired.
▪ Symbol power saving has not taken effect.

3. (Optional) For a hyper cell or combined cell, run the DSP NRDUCELLTRP
command to query the deep symbol power saving state of each TRP in the
cell.
Power Saving:Enabled for a TRP, deep symbol power saving has taken
effect in the TRP.
Power Saving:Disabled for a TRP, deep symbol power saving has not
taken effect in the TRP. The possible reasons are as follows:
▪ The license items "Intelligent Scheduling for Power Saving" are

insufficient.
▪ Symbol power saving has not taken effect.

5G RAN
NOTE
For details about the consumption principles of feature license items in hyper
cells or combined cells, see Hyper Cell (Low-Frequency TDD) or Cell
Combination.

obtained before and after intelligent scheduling for power saving is enabled
can be compared to assess the energy saving gains of this feature. It is
expected that the base station energy consumption decreases significantly
after this feature is enabled.
● The time that a cell spends in the symbol power saving state can be obtained
by using the N.PowerSaving.SymbolShutdown.Dur counter on the MAE-
Access. It is expected that the time increases after intelligent scheduling for
power saving is enabled.
4.3 Timing Carrier Shutdown

4.3.1 Principles
Maintaining all PAs of RF modules in the operational state when the network is
under no load wastes base station energy. Timing carrier shutdown enables
carriers to be shut down within specified periods, as shown in Figure 4-8. If the PA
(of an RF module) serving a shut-down carrier is not serving any other operating
carrier, the PA will also be shut down to save energy.
Figure 4-8 Working principles of timing carrier shutdown
Timing carrier shutdown can be enabled by selecting the

TIMING_CARRIER_SHUTDOWN_SW option of the
NRDUCellAlgoSwitch.PowerSavingSwitch parameter. The information under an
energy saving policy of timing carrier shutdown is specified by the parameters in
the NRDUCellPowerSaving MO.

5G RAN

energy saving type indicated by an energy saving policy index. Timing carrier
shutdown requires that this parameter be set to
TIMING_CARRIER_SHUTDOWN, meaning that under the corresponding
energy saving policy, the carrier is shut down in the specified period.
● The NRDUCellPowerSaving.StartTime and
NRDUCellPowerSaving.StopTime parameters specify the energy saving start
time and stop time indicated by an energy saving policy index. Timing carrier
shutdown takes effect every day within the configured period.
NOTE
● If timing carrier shutdown takes effect for a hyper cell or combined cell, carriers of all
TRPs are shut down.
● A cell in the carrier shutdown state exits this state if it is deactivated and then
reactivated or the base station software version is upgraded. Once either action is
complete, the cell re-enters the carrier shutdown state if the current time is still within
the period during which timing carrier shutdown takes effect.
4.3.2 Energy Saving Procedure

Figure 4-9 shows the procedure for timing carrier shutdown.
Figure 4-9 Timing carrier shutdown procedure
1. Determining whether the current time is within the periods specified by the
NRDUCellPowerSaving.StartTime and NRDUCellPowerSaving.StopTime
parameters.

5G RAN
2. Performing UE transfer as follows:

– In SA networking, UEs are transferred to inter-frequency or inter-RAT cells
through blind redirections.
– In NSA networking, UE connections on the NR side are released.
– For UEs that treat the cell served by the NR carrier as a secondary cell
(SCell) in carrier aggregation (CA), the SCell is removed. For UEs that
treat the preceding cell as the primary cell (PCell) in CA, they are
transferred to inter-frequency or inter-RAT cells through blind
redirections.
Proceeding to 3 ten seconds after the UE transfer procedure starts.
3. Shutting down the NR carrier.
4.3.3.1 Benefits
Timing carrier shutdown reduces energy consumption when the network is under
no load. However, the energy saving gains are limited in the following scenarios:
● When multiple carriers share the same PA of an RF module, the PA cannot be

shut down if an NR carrier is shut down while the other carriers are still
working. Energy saving gains decrease in this case.
● To prevent energy saving–triggered shutdown from affecting the lifespan of
RF modules and prevent possible hardware faults caused by an excessively
large temperature differential, this function may not take effect or may be
terminated when the temperature differential of RF modules is excessively
large. Energy saving gains may decrease in this case.
4.3.3.2 Impacts
Network Impacts
● Before timing carrier shutdown takes effect, the gNodeB transfers SA UEs to
NR or LTE cells through blind redirections. This impacts related counters
described in Table 4-5.
Table 4-5 Impacts on counters related to blind redirections
RA Counter Name Impact

T
NR N.RRCRedirection.Blind The value of this counter may increase

when SA UEs are transferred to NR cells
NR N.RRCRedirection.N2E.Bli The value of this counter may increase

nd when SA UEs are transferred to LTE cells

5G RAN

T
NR N.RRCRedirection.N2E.Bli The value of this counter may increase

nd.PowerSaving when SA UEs are transferred to LTE cells
through blind redirections for energy
saving purposes.
● After timing carrier shutdown takes effect in a cell:

– Existing UEs in the cell cannot perform services, slightly increasing the
service drop rate.
– New UEs in the cell coverage cannot access the network.
– During NR carrier shutdown, new UEs are prohibited from accessing an
NR cell. If UEs attempt to be handed over to the NR cell, the values of
the counters related to handover preparation failures (such as
N.HO.IntraFreq.FailOut.PrepFailure) slightly increase. Such counters are
not used for calculating Huawei-defined KPIs outgoing intra- and inter-
frequency handover success rates, but may be used for calculating user-
defined KPIs. When carrier shutdown is set to take effect on the hour, no
UEs can be handed over to the deactivated NR cell. Therefore, even slight
increases in the counter values may significantly affect the user-defined
outgoing handover success rates. If carrier shutdown is scheduled to take
effect on the hour, you are advised to set the start time to 5 minutes
earlier and the lengths of penalty timers applied to handover failures to
30s (using the MOD GNBMOBILITYCOMMPARAM command).
● This function saves energy by shutting down carriers, but the cells remain
activated. As such, when this function takes effect, the performance counters
and KPIs listed in Table 4-6 are still in measurement, which has no impact on
the energy saving effect. The exact time when carrier shutdown actually starts
taking effect may not be synchronized with that when related performance
counters are reported. Consequently, if carrier shutdown starts taking effect in
a measurement period, there will be a measurement error of less than 5
minutes between the reported results and the actual results for the shut-
down cell in the measurement period.

5G RAN
Table 4-6 Related performance counters and KPIs

Function Subset Performance Counter and KPI
● PRB Measurement ● Counters related to the number of used

● Hyper Cell TRP PRB PRBs
Measurement ● Counters related to the number of
● DU Cell Operator PRB available PRBs
physical downlink control channel
(PDCCH) control channel elements
(CCEs)
● Counters related to the number of
PDCCH resource allocation times
● PRB usage
DU Cell Algorithm ● Counters related to the total number of

Measurement physical uplink shared channel (PUSCH)
transmission time intervals (TTIs)
● Counters related to the total number of
PDSCH TTIs
DU Cell SI Message Number of SI transmissions

Measurement
● Channel Quality ● Counters related to interference and

Measurement noise received in the uplink
● DU Cell TRP Channel ● Counters related to uplink received
Quality Measurement signal strength indicator (RSSI)
● Uplink Interference ● Counters related to uplink and downlink
Measurement on PRB 0 to power
PRB 99 ● Counters related to average interference
● Uplink Interference and noise detected on a single PRB
Measurement on PRB 100 ● Counters related to the maximum
to PRB 199 interference and noise detected on a
● Uplink Interference single PRB
Measurement on PRB 200
to PRB 272
● In the case of false physical random access channel (PRACH) detection where
the base station mistakenly regards interference or noise as the random
access preambles of UEs, measurement for the following counters and KPIs
will continue:
– Counters related to the number of random preamble receptions
– Counters related to the number of random preamble responses
– Counters related to the number of UEs scheduled in the uplink and
downlink in a cell
– Counters related to uplink data transmission duration
– Counters related to the number of transport blocks (TBs) used for uplink
data transmission

5G RAN
– Counters related to modulation and coding scheme (MCS) index

distribution for scheduling on the PUSCH
– Counters related to the number of resource blocks (RBs) used for
scheduling on the PUSCH
– PUSCH RB usage
Function Impacts
Name Switch
FDD Symbol NRDUCellAl Energy When timing

Low- power saving goSwitch.Sy Conservation carrier shutdown
frequency mbolShutdo and Emission takes effect for a
TDD wnSwitch Reduction carrier:
● If the RF
module is not
serving any
other NR
carrier, symbol
power saving
does not take
effect.
● If the RF
module is
serving other
NR carriers, the
status of
symbol power
saving for
these carriers is
not affected.

5G RAN

Name Switch
FDD Deep symbol DEEP_SYMB Energy When timing

Low- power saving OL_SHUTDO Conservation carrier shutdown
frequency WN_SW and Emission takes effect for a
TDD option of the Reduction carrier:
NRDUCellAl ● If the RF
goSwitch.Po module is not
werSavingS serving any
witch other NR
parameter carrier, deep
symbol power
saving does
not take effect.
● If the RF
module is
serving other
NR carriers, the
status of deep
symbol power
saving for
these carriers is
not affected.
FDD Multi-RAT MULTI_RAT_ Multi-RAT When timing

Low- coordinated SYMBOL_SH Coordinated carrier shutdown
frequency symbol UTDOWN_S Symbol takes effect for a
TDD power saving W option of Power Saving carrier:
the ● If the RF
NRDUCellAl module is not
goSwitch.Po serving any
werSavingS other NR
witch carrier, multi-
parameter RAT
coordinated
symbol power
saving does
not take effect.
● If the RF
module is
serving other
NR carriers, the
status of multi-
RAT
coordinated
symbol power
saving for
these carriers is
not affected.

5G RAN

Name Switch
Low- RF module RRU.DORMA RF Module Timing carrier

frequency deep NCYSW (LTE Deep shutdown does
TDD dormancy eNodeB, 5G Dormancy not take effect
gNodeB) when RF module
deep dormancy is
in effect.
FDD CMAS gNBSibConfi CMAS When an NR

Low- g.SibType carrier is shut
frequency set to down, the
TDD SIB_TYPE_8 corresponding NR
cell is blocked and
CMAS warning
notifications
cannot be
properly sent in
this cell. However,
UEs can still
receive CMAS
warning
notifications from
other carriers.
Low- RF channel RF_SHUTDO Energy If timing carrier

frequency intelligent WN_SW Conservation shutdown has
TDD shutdown option of the and Emission taken effect, RF
NRDUCellAl Reduction channel
goSwitch.Po intelligent
werSavingS shutdown cannot
witch take effect in the
parameter scenarios listed in
Table 4-12.
Low- Super uplink FLEX_SUPER Super Uplink After an NR FDD

frequency with SUL and _UPLINK_S carrier is shut
TDD NR FDD co- W option of down, SUL
deployment the scheduling cannot
NRDUCellAl be performed for
goSwitch.Su super uplink UEs.
perUplinkS
witch
parameter

5G RAN

Name Switch
Low- Network- GAP_BASED_ Synchronizati If sequence

frequency wide SYNC_DIFF_ on detection is
TDD synchronizati DET_SW performed on all
on deviation option of the cells of a to-be-
detection gNodeBPara detected base
m.SyncDiffD station during the
etectSwitch period when
parameter timing carrier
shutdown takes
effect, the
sequence
detection fails. In
this case, the
possible clock
fault of the base
station may fail to
be detected.
FDD Cell load STR None Cell load

Low- simulation NRDUCELLSI simulation cannot
frequency MULATELOA be started when
TDD D timing carrier
shutdown is
enabled. If cell
load simulation
has started, it will
stop when timing
carrier shutdown
is enabled.
Therefore,
enabling both
functions is not
recommended.
FDD Antenna port STR MIMO If carrier

detection ANTENNAP shutdown takes
ORTOPTDET effect before
antenna port
detection is
completed, the
detection results
will show that the
detection fails.

5G RAN

Name Switch
Low- Low latency HIGH_RELIA URLLC After timing

frequency and high BILITY_BASI carrier shutdown
TDD reliability C_SW option is enabled, a cell
of the enters the carrier
NRDUCellAl shutdown state,
goSwitch.Hi which may cause
ghReliability UEs performing
Switch high-reliability
parameter services to
experience
network
disconnections.
4.3.4 Requirements
4.3.4.1 Licenses

Saving
4.3.4.2 Software
None

5G RAN

Name Switch
FDD Intelligent INTRA_GNB_ Energy The periods

Low- carrier MULTI_CARR Conservation configured for
frequency shutdown _SD_SW or and Emission timing carrier
TDD INTER_GNB_ Reduction shutdown cannot
MULTI_CARR overlap with
_SD_SW those configured
option of the for intelligent
NRDUCellAl carrier shutdown
goSwitch.Po of the same cell.
werSavingS You are advised to
witch preferentially plan
parameter the periods during
which timing
carrier shutdown
takes effect.
FDD Power saving POWER_SAV Energy The periods

Low- scheduling ING_SCHED Conservation configured for
frequency ULE_SW and Emission timing carrier
TDD option of the Reduction shutdown cannot
werSavingS for power saving
witch scheduling of the
advised to
preferentially plan
the periods during
which timing
carrier shutdown
takes effect.
FDD LTE and NR LNR_SMART LTE and NR The periods

Low- intelligent _CARRIER_S Intelligent configured for
frequency carrier HUTDOWN_ Carrier timing carrier
TDD shutdown SW option of Shutdown shutdown cannot
the overlap with
NRDUCellAl those configured
goSwitch.Po for LTE and NR
werSavingS intelligent carrier
witch shutdown of the
advised to
preferentially plan
the periods during
which timing
carrier shutdown
takes effect.

5G RAN

Name Switch
FDD LTE and NR LNR_BUNDL Multi-RAT The periods

Low- bundled ED_SCHEDU Coordinated configured for
frequency scheduling LING_SW Symbol timing carrier
TDD option of the Power Saving shutdown cannot
werSavingS for LTE and NR
witch bundled
parameter scheduling of the
same cell. You are
advised to
preferentially plan
the periods during
which timing
carrier shutdown
takes effect.
FDD LNR NR: Multi-RAT The periods

Low- coordinated MULTI_RAT_ Coordinated configured for
frequency channel RF_SHUTDO Channel timing carrier
TDD shutdown WN_SW Shutdown shutdown cannot
option of the overlap with
NRDUCellAl those configured
goSwitch.Po for LNR
werSavingS coordinated
witch channel shutdown
parameter of the same cell.
LTE: You are advised to
CellRfShutd preferentially plan
own.MultiRa the periods during
tJointChnSh which timing
utdownSw carrier shutdown
takes effect.
4.3.4.3 Hardware
Base Station Models

with the BBU3910.
Boards

5G RAN
RF Modules
All NR-capable RF modules that work in low frequency bands support this
function. For details, see the technical specifications of RF modules in 3900 & 5900
Series Base Station Product Documentation.
4.3.4.4 Others
None


Name
NR DU NRDUCellAlgoSwitch.NrDuCell Set this parameter based on the

Cell ID Id network plan.
Power NRDUCellAlgoSwitch.PowerSa Select the

Saving vingSwitch TIMING_CARRIER_SHUTDOWN
Switch _SW option of this parameter.
Power NRDUCellPowerSav- Set this parameter based on the

Saving ing.PowerSavingPolicyIndex network plan.
Policy
Index
Start Time NRDUCellPowerSav- Set this parameter based on the

ing.StartTime network plan and the following
requirements:
● For a policy of an energy
saving function, the interval
between the stop time and
start time must be longer
than 20 minutes.
than or the same as the start
time, it is assumed that the
stop time refers to the next
day. For example:

5G RAN

Name
Stop Time NRDUCellPowerSav- If the start time is set to

ing.StopTime 08:00 and the stop time is
enabling the related energy
saving function is from 08:00
to 07:00 the next day.
energy saving function, the
time of one policy and the
start time of another must
be longer than 5 minutes.
For example, if policy B of an
energy saving function needs
to be enabled after policy A
of this function has been
enabled, the start time of
policy B must be 5 minutes
later than the stop time of
policy A.
If timing carrier shutdown is
scheduled to take effect on the
hour, you are advised to set the
start time to 5 minutes earlier
to prevent the values of the
counters related to handover
preparation failures (such as
N.HO.IntraFreq.FailOut.PrepFa
ilure) from increasing.
For example, if timing carrier
shutdown is scheduled to take
effect at 00:00:00, you are
advised to set the
NRDUCellPowerSav-
ing.StartTime parameter to
23:55:00.
Power NRDUCellPowerSav- Set this parameter to

Saving ing.PowerSavingType TIMING_CARRIER_SHUTDOWN
Type .
Necessary gNBMobilityCommPar- The value 30 is recommended.

HO am.NecHoPrepFailPunishTimer
Prepare
Fail Punish
Timer

5G RAN

Name
Optimized gNBMobilityCommPar- The value 30 is recommended.

HO am.OptHoPrepFailPunishTimer
Prepare
Fail Punish
Timer

complete the parameter configurations for related functions based on the impact
and mutually exclusive relationships between the functions, as well as the actual
network scenario.

//Setting an energy saving policy of timing carrier shutdown
StopTime=03&00&00, PowerSavingType=TIMING_CARRIER_SHUTDOWN;
//(Optional) Setting another energy saving policy of timing carrier shutdown
StopTime=05&00&00, PowerSavingType=TIMING_CARRIER_SHUTDOWN;
//Enabling timing carrier shutdown
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=TIMING_CARRIER_SHUTDOWN_SW-1;
//(Optional) Setting the lengths of penalty timers applied to handover failures to 30s
MOD GNBMOBILITYCOMMPARAM: NecHoPrepFailPunishTimer=30, OptHoPrepFailPunishTimer=30;

N/A

//Disabling timing carrier shutdown
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=TIMING_CARRIER_SHUTDOWN_SW-0;
//Removing an energy saving policy of timing carrier shutdown
//(Optional) Removing the other energy saving policy of timing carrier shutdown


After the timing carrier shutdown function is activated, use either of the following
● Method 1:
Power Saving Switch parameter is Scheduled Carrier Shutdown
Switch:On in the command output, timing carrier shutdown has been
enabled.

5G RAN

least one record with Power Saving Type being Scheduled Carrier
Shutdown.
NOTE
If there are two or more records with Power Saving Type being Scheduled
Carrier Shutdown, timing carrier shutdown has been enabled in two or more
time periods.
timing carrier shutdown period.
▪ If it is not, wait until the start time of timing carrier shutdown

arrives.
d. Wait 3 minutes and then run the DSP NRDUCELL command. Verify that
the value of the Power Saving State parameter is Scheduled Carrier
Shutdown:Enabled, which indicates that timing carrier shutdown has
taken effect.
● Method 2:
timing carrier shutdown.
– If the value of Power Saving Type is Scheduled Carrier Shutdown and
the value of Current State is Enabled, timing carrier shutdown has taken
effect.
– If the value of Power Saving Type is Scheduled Carrier Shutdown and
the value of Current State is Disabled, check the Current Disabled
Cause parameter value to determine the reason why timing carrier
shutdown does not take effect. Table 4-8 lists possible reasons.
Table 4-8 Possible reasons why timing carrier shutdown does not take
effect
Reason Description

available.

Triggering Time Not Reached The current time is not within the
range specified for timing carrier
shutdown.
Impacted Feature Taken Effect None
In Penalty State A penalty is being imposed upon

an exit from the timing carrier
shutdown state.

5G RAN
Reason Description
RF Hardware Capability Not None

Supported
Others ● The current time is within the

range specified for timing
carrier shutdown, but this
function is in its detection
period, which lasts for 3
minutes.
fail.

obtained before and after timing carrier shutdown is enabled can be
compared to assess the energy saving gains of this function. It is expected
that the base station energy consumption decreases significantly after this
function is enabled.
● The duration of cell unavailability due to timing carrier shutdown can be
obtained using the N.Cell.Unavail.Dur.EnergySaving counter on the MAE-
Access.
There is delay in making decisions on whether to enter or exit the timing
carrier shutdown state. Therefore, the duration measured by the
N.Cell.Unavail.Dur.EnergySaving counter has an approximately 1 minute
deviation from the timing carrier shutdown period set by the operator.
4.4 pRRU Deep Dormancy
4.4.1 Principles
In certain indoor scenarios such as shopping malls, stadiums, metro stations, and
office buildings, there are no service requirements at fixed periods. Keeping RF
modules active during these periods wastes energy of the base stations. With
pRRU deep dormancy, some pRRUs can be shut down and enter the deep
dormancy state during the specified no-service periods, reducing energy
consumption. Figure 4-10 shows the working principles of pRRU deep dormancy.

5G RAN
Figure 4-10 Working principles of pRRU deep dormancy
Entering and Exiting the Deep Dormancy State

pRRU deep dormancy is controlled by the RRU.DORMANCYSW parameter.
● Specific pRRUs enter the deep dormancy state two minutes after the
dormancy start time specified by the RRU.DORMANCYSTARTTIME parameter
arrives. The two minutes is referred to as the transitional period, during which
the pRRUs can work properly after pRRU deep dormancy is triggered.
● These pRRUs exit the deep dormancy state when the dormancy stop time
specified by the RRU.DORMANCYSTOPTIME parameter arrives. The pRRUs
restart when exiting the deep dormancy state. After restarting, they return to
the normal state.
CAUTION
It is recommended that base station reconfiguration, license installation and

activation, and software version download not be performed during the specified
dormancy period. If the preceding operations are required, pRRU deep dormancy
should be first disabled.
After pRRUs enter the deep dormancy state:

● pRRUs in the deep dormancy state do not transmit signals. The following
alarms are not reported unless they are caused by other causes:
– ALM-29840 gNodeB Out of Service
– ALM-29841 NR Cell Unavailable
– ALM-29870 NR DU Cell TRP Unavailable
– ALM-29871 NR DU Cell TRP Capability Degraded
● The following operations are not supported:
– Fast Fourier Transform (FFT) spectrum scanning by using the Web LMT
– Hardware test using the STR HWTST command
– Introduction of a new RAT to the base station or a version upgrade
Enabling or Canceling Deep Dormancy Pending

When deep dormancy is pending, none of the RF modules of the base station
enter the deep dormancy state. This function can be enabled for the base station
using any of the following methods:

5G RAN
● Run the PND DORMANCY command with the OPERATIONTYPE parameter

set to PENDING. In this case, deep dormancy is pending and RF modules
cannot enter the deep dormancy state within a duration specified by the
PENDINGDURATION parameter. In LNR separate-MPT scenarios, if the main
control boards of two sides are configured with different pending durations,
the longer one takes effect for the base station.
● Set the EQUIPMENT.DEEPDORMANCYCFGCHKSW parameter to ON. Under
this setting, deep dormancy is automatically pending for 30 minutes for the
base station if the base station is restarted, the gNodeBFunction MML
commands that affect cell setup are executed, or Node MML commands
(except the MOD RRU command with only parameters related to RF module
deep dormancy specified) are executed.
● In separate-MPT co-RF-module scenarios, if deep dormancy is enabled on the
local side and cell reestablishment is triggered (by configuration modification,
exiting from the dormancy state, CPRI link intermittent disconnection, BBP
reset, license update, or other reasons) on the peer side, deep dormancy will
be automatically pending for 30 minutes on the local side.
Deep dormancy pending enabled in the preceding scenarios can be canceled by
running the PND DORMANCY command with the OPERATIONTYPE parameter
set to UNPENDING. In LNR separate-MPT scenarios, this command can be used to
cancel deep dormancy pending only on the local NE. The deep dormancy function
of the local NE is also affected by the deep dormancy pending states of intra-
base-station NEs.
During the specified pending duration, the base station does not enter the deep
dormancy state. If the base station is in the deep dormancy state, it automatically
exits this state. The pending duration can be queried using the DSP
BRDDORMANCY command.
License Reliability Protection During Deep Dormancy

To improve the license key file (LKF) installation reliability, the base station is
woken up and deep dormancy is pending when the LKF is installed during RF
module deep dormancy.
● If there is no error in the LKF to be installed, exit from deep dormancy is
triggered for the base station after the LKF is successfully installed.
● If there is a minor error in the LKF to be installed, the LKF installation fails
and exit from deep dormancy is triggered for the base station. After the exit is
complete, the LKF can be installed again.
● If there is a major error in the LKF to be installed, the LKF installation fails
and exit from deep dormancy is triggered for the base station.
NOTE
● In all scenarios, deep dormancy is pending for 30 minutes when the base station exits
the deep dormancy state.
● The LKF installation will fail during the exit from RF module deep dormancy.
● For details about minor and major errors during LKF installation, see License
Management.
If there is a license insufficiency that may cause a cell establishment failure after
the exit from deep dormancy, the base station does not enter the deep dormancy
state until the insufficiency is solved.

5G RAN
If ALM-26817 License on Trial or ALM-26815 Licensed Feature Entering Keep-Alive

Period is reported and the involved license item may cause a cell establishment
failure after the exit from deep dormancy, the base station does not enter the
deep dormancy state until the license insufficiency is solved when the remaining
grace period is less than 24 hours.
Configuration Reliability Protection During Deep Dormancy

NOTE
Configuration reliability protection during deep dormancy requires the OSS and NEs to
coordinate; both must be upgraded to versions supporting this function.
Delivering configuration data during RF module deep dormancy may cause the
following issues:
● The dynamic verification before configurations are imported into the database
becomes invalid, and therefore the accuracy of configuration data cannot be
ensured.
● The alarms generated when the configuration data fails to take effect cannot
be reported in time.
Configuration reliability protection during deep dormancy is introduced to avoid
the issues listed above. With this function, the base station is woken up and deep
dormancy is pending before or during configuration delivery. In this case, dynamic
verification can be performed before configurations are imported into the
database, and the alarms generated when the configurations fail to take effect
can be reported in time. Details for different configuration scenarios are described
as follows:
● A single MML command
– If the base station receives a power-related command and an NE of the
base station is in the deep dormancy state, the base station first exits the
deep dormancy state (deep dormancy is forcibly pending for 15 minutes).
After exiting the deep dormancy state, the base station executes the
command. The execution progress is reported throughout the process, as
shown in Figure 4-11. After the command is executed, the base station
automatically triggers a common 30-minute pending period.

5G RAN
Figure 4-11 Example of execution progress reporting
– If the base station receives a gNodeBFunction MML command that

affects cell setup or a Node MML command (except power-related
commands) and an NE of the base station is in the deep dormancy state,
the base station directly executes the command and starts to exit the
deep dormancy state. After the command is executed, the base station
automatically triggers a common 30-minute pending period.

5G RAN
NOTE
● The base station first exits the deep dormancy state and then executes a
power-related command received during deep dormancy. If the command
execution times out, the output of this command indicates that the command
execution has failed, displaying "The system is busy performing a time-
consuming operation. Please try again later." If another command is delivered
during this process, it needs to be queued. If the command execution times
out, the output of this command indicates that the command execution has
failed, displaying "The system is busy performing a time-consuming
operation. Please try again later."
● The PND DORMANCY command cannot be used to cancel forcible deep
dormancy pending. Common deep dormancy pending (triggered by the PND
DORMANCY command or other reasons) can be canceled by running the
PND DORMANCY command.
● If only forcible deep dormancy pending is performed for the base station and
the PND DORMANCY command is executed with the OPERATIONTYPE
parameter set to UNPENDING to cancel deep dormancy pending, the
command output indicates a cancellation failure, displaying "The system is
forced to suspend deep dormancy, and the suspension cannot be canceled by
running this command."
● If both forcible deep dormancy pending and common deep dormancy
pending are performed for the base station, and the PND DORMANCY
command is executed with the OPERATIONTYPE parameter set to
UNPENDING to cancel deep dormancy pending, the command output
indicates a cancellation failure, displaying "The common suspension of deep
dormancy has been canceled successfully. The forcible suspension of deep
dormancy cannot be canceled by running this command."
● An XML configuration file
If the base station receives an XML script file, it checks whether the file
contains a gNodeBFunction MML command that affects cell setup or a Node
MML command (except the MOD RRU command with only parameters
related to RF module deep dormancy specified).
– If not, the base station directly executes the commands in the XML script
file.
– If yes, the base station first exits the deep dormancy state (deep
dormancy is forcibly pending for 15 minutes) and then executes the
commands in the XML script file. After the commands are executed,
common deep dormancy pending for 30 minutes is automatically
triggered for the base station.
● Batch processing (batch scripts, batch configurations, or incremental
configurations)
The MAE-Access or MAE-Deployment checks whether there are
gNodeBFunction MML commands that affect cell setup or Node MML
commands (for the MAE-Deployment, except the MOD RRU command with
only parameters related to RF module deep dormancy specified) in the batch
scripts, batch configurations, or incremental configurations.
– If not, the batch scripts, batch configurations, or incremental
configurations are directly executed.
– If yes, the MAE-Access or MAE-Deployment wakes up the base station in
advance. After the base station exits the deep dormancy state and deep
dormancy is forcibly pending for eight hours, the MAE-Access or MAE-
Deployment performs batch processing. Common deep dormancy

5G RAN
pending for 30 minutes is automatically triggered when the base station

executes the gNodeBFunction MML commands that affect cell
reestablishment or Node MML commands.
After batch processing is complete, the MAE-Access or MAE-Deployment
instructs the base station to cancel forcible deep dormancy pending.
4.4.2.1 Benefits
pRRU deep dormancy reduces energy consumption when the network is under no
load.
To prevent energy saving–triggered shutdown from affecting the lifespan of RF
modules and prevent possible hardware faults caused by an excessively large
temperature differential, this function may not take effect or may be terminated
when the temperature differential of RF modules is excessively large. Energy
saving gains may decrease in this case.
4.4.2.2 Impacts
Network Impacts
● pRRUs in the deep dormancy state do not transmit signals. This weakens
radio signals in their coverage area, leading to possible deteriorating service
quality, service drops, and access failures.
● If the batch processing tasks of the OSS contain gNodeBFunction MML
commands that affect cell setup or Node MML commands, and the base
station is in the deep dormancy state, the OSS executes related configurations
after the base station exits the deep dormancy state. This increases the
waiting time before configuration execution.
● Assume that an XML configuration file contains a gNodeBFunction MML
command that affects cell setup or a Node MML command (including a
single power-related command), and the base station is in the deep dormancy
state. The base station automatically exits the deep dormancy state and then
executes the command.

5G RAN
Function Impacts
Name Switch
Low- Distributed DM_MIMO_ MIMO If pRRU deep

frequency massive SERVICE_SW dormancy is
TDD MIMO ITCH option enabled in a
of the distributed
NRDUCellAl massive MIMO
goSwitch.D cell and all pRRUs
mMimoSwit serving a TRP
ch parameter enter the
dormancy state,
the TRP becomes
unavailable and
ALM-29870 NR
DU Cell TRP
Unavailable is
reported.
Low- Low latency HIGH_RELIA URLLC If pRRUs enter the

frequency and high BILITY_BASI deep dormancy
TDD reliability C_SW option state after pRRU
of the deep dormancy is
NRDUCellAl enabled, UEs
goSwitch.Hi performing high-
ghReliability reliability services
Switch may be
parameter disconnected from
the network.
High- None None None None

frequency
TDD
FDD None None None None
4.4.3 Requirements
4.4.3.1 Licenses
FOFD-030216 pRRU Deep NR0SDORMAN10 per pRRU

Dormancy

5G RAN
4.4.3.2 Software
None

None
4.4.3.3 Hardware
Base Station Models

Boards
RF Modules
All NR-capable pRRUs support this function. For details, see the technical
specifications of RF modules in 3900 & 5900 Series Base Station Product
Documentation.
4.4.3.4 Networking
● All RATs in a separate-MPT multimode LampSite base station must be
enabled with pRRU deep dormancy for the function to take effect. For
example:
– For a multimode LampSite base station where LTE and NR use separate
MPTs but share RF modules, pRRU deep dormancy must be enabled for
both NR and LTE with the same start time and stop time so that this
function can take effect.
– For a multimode LampSite base station where LTE and NR use separate
MPTs and RF modules, when CPRI MUX networking is used, pRRU deep
dormancy must be enabled for both NR and LTE with the same start time
and stop time so that this function can take effect.
● pRRU deep dormancy is not recommended for first-level pRRUs in pRRU
cascading scenarios. This is because such pRRUs do not support deep
dormancy.
4.4.3.5 Others
None

5G RAN

optimization configurations are not involved.

Name
Dormancy RRU.DORMANCYSW You are advised to turn on this

Switch switch.
Dormancy RRU.DORMANCYSTARTTIME Set this parameter based on the

Start Time no-service hours on the live
network.
Dormancy RRU.DORMANCYSTOPTIME Set this parameter based on the

Stop Time no-service hours on the live
network. It takes some time for
a pRRU in the deep dormancy
state to restore its working
state. To ensure that the
network resumes normal
services at the time point A, you
are advised to set the dormancy
stop time to 3 minutes earlier
than A. For example, if the
network is expected to restore
services at 06:00:00, you are
advised to set the dormancy
stop time to 05:57:00.
Operation OPERATIONTYPE The value PENDING is

Type recommended.
Pending PENDINGDURATION Set this parameter based on the

Duration network plan.
Deep EQUIPMENT.DEEPDORMANCY Set this parameter based on the

Dormancy CFGCHKSW network plan.
Config
Check
Switch

Before using MML commands, refer to 4.4.2.2 Impacts and complete the
parameter configurations for related functions based on the impact relationships
between the functions, as well as the actual network scenario.

5G RAN

//Activating pRRU deep dormancy
MOD RRU: CN=0, SRN=60, SN=0, DORMANCYSW=ON, DORMANCYSTARTTIME=22&00&00,
DORMANCYSTOPTIME=08&00&00;
//(Optional) Enabling deep dormancy pending in manual mode
PND DORMANCY: OPERATIONTYPE=PENDING, PENDINGDURATION=30;
//(Optional) Enabling deep dormancy pending in automatic mode
SET EQUIPMENT: DEEPDORMANCYCFGCHKSW=ON;

N/A

conditions.
//Deactivating pRRU deep dormancy
MOD RRU: CN=0, SRN=60, SN=0, DORMANCYSW=OFF;


Check whether pRRU deep dormancy has taken effect by using any of the
following methods:
● Use MML commands to query the RRU dormancy status to check whether
pRRU deep dormancy has taken effect:
//Querying the RRU dormancy status
DSP BRDDORMANCY: QUERYTYPE=BOARD;
If the value of Board Dormancy State is DORMANCY or

ENHANCED_DORMANCY in the output of the preceding command, pRRU
deep dormancy has taken effect.
● Use MML commands to query the NR DU cell status to check whether pRRU
deep dormancy has taken effect:
Run the DSP NRDUCELL command. If the value of the Power Saving State
parameter is Dormancy of All RF Modules:Enabled or Dormancy of Some
RF Modules:Enabled, pRRU deep dormancy has taken effect.

5G RAN
NOTE
Within 10 minutes after the pRRUs exit the deep dormancy state:
● The value of the Power Saving State parameter is still Dormancy of All RF
Modules:Enabled or Dormancy of Some RF Modules:Enabled in the command
output of DSP NRDUCELL.
● The following alarms are still not reported unless they are caused by other faults:
● ALM-29840 gNodeB Out of Service
● ALM-29841 NR Cell Unavailable
● ALM-29870 NR DU Cell TRP Unavailable
● ALM-29871 NR DU Cell TRP Capability Degraded
10 minutes after the pRRUs exit the deep dormancy state, the value of the Power
Saving State parameter is Dormancy of All RF Modules:Disabled or Dormancy of
Some RF Modules:Disabled in the command output of DSP NRDUCELL.
● Use MML commands to query the working status of RF modules serving an
NR DU cell to check whether pRRU deep dormancy has taken effect:
Run the DSP NRDUCELLANTENNA command. If the value of the RF Work
State parameter is Deep Dormancy for a pRRU serving the cell, pRRU deep
dormancy has taken effect.
● Use MML commands to query the power saving status to check whether deep
dormancy is pending for the base station:
If the value of NE Dormancy Pending Status is PENDING in the command
output, deep dormancy is pending for the NE. If the value of Site Dormancy
Pending Status is PENDING in the command output, deep dormancy is
pending for an NE of the base station.
//Querying the power saving status
DSP BRDDORMANCY: QUERYTYPE=SITE;

obtained before and after pRRU deep dormancy is enabled can be compared
to assess the energy saving gains of this function. It is expected that the base
station energy consumption decreases significantly after this function is
enabled.
NOTE
For multimode LampSite base stations supporting NR, the VS.EnergyCons.BTSBoard

counter is recommended for the evaluation of energy conservation gains.
● The duration of cell unavailability due to pRRU deep dormancy can be
obtained by using the N.Cell.Unavail.Dur.EnergySaving counter on the MAE-
Access.
The duration measured by the N.Cell.Unavail.Dur.EnergySaving counter has
a deviation of less than 3 minutes from the pRRU deep dormancy period set
by the operator. This is because entering the pRRU deep dormancy state
requires determining whether the time and other trigger conditions are met
and exiting this state involves such operations as pRRU restart and cell
reestablishment.

5G RAN
4.5 RF Channel Intelligent Shutdown

4.5.1 Principles
RF channel intelligent shutdown enables a base station to shut down some
transmit channels of a cell when the network is under light or no load during
preset periods, as shown in Figure 4-12. This helps save energy.
Figure 4-12 Working principles of RF channel intelligent shutdown
RF channel intelligent shutdown can be enabled by selecting the

RF_SHUTDOWN_SW option of the NRDUCellAlgoSwitch.PowerSavingSwitch
parameter.
This function takes effect every day within the configured RF channel intelligent
shutdown periods under certain conditions. The periods, load threshold, and other
information under an energy saving policy are specified by the parameters in the
NRDUCellPowerSaving MO.
energy saving type indicated by an energy saving policy index. RF channel
intelligent shutdown requires that this parameter be set to RF_SHUTDOWN,
meaning that under the corresponding energy saving policy, RF channels are
shut down in the specified period under certain load conditions.
During an RF channel intelligent shutdown period, a cell automatically enters the
RF channel intelligent shutdown state if its downlink PRB usage (which equals
N.PRB.DL.DrbUsed.Avg divided by N.PRB.DL.Avail.Avg) is less than or equal to
the NRDUCellPowerSaving.DlPrbThld parameter value and the number of
RRC_CONNECTED UEs in the cell (indicated by N.User.RRCConn.Avg) is less than
or equal to the NRDUCellPowerSaving.UserNumThld parameter value.
When a cell enters the RF channel shutdown state, transmit power is compensated
for the common channels of the cell to ensure the base station coverage and

5G RAN
service provisioning. The compensated power can be automatically determined or

manually configured, depending on the setting of the
NRDUCellPowerSaving.CovCompensationMode parameter.
● If this parameter is set to AUTO, a macro base station automatically
compensates for the transmit power of common channels in the cell, but a
LampSite base station does not. When the transmit power compensated for
common channels in the cell is automatically determined by a macro base
station, power aggregation enhancement can be enabled by setting
RSVDSWPARAM1_BIT21 of the NRDUCellRsvdExt02.RsvdSwParam1
parameter to 1. This allows RF channel intelligent shutdown to take effect in
more scenarios.
● If this parameter is set to MANUAL, the transmit power to be compensated
for the common channels of the cell served by a macro or LampSite base
station is manually configured using the
NRDUCellPowerSaving.CovCompensationPwrOffset parameter. However,
the compensated power cannot exceed the RF module's maximum capability
of aggregating the cell common channel transmit power. If the configured
compensated power exceeds the RF module's maximum capability, the latter
takes effect.
During the period when RF channel intelligent shutdown takes effect,
RSVDSWPARAM0_BIT28 of the NRDUCellRsvdExt02.RsvdSwParam0 parameter
can be set to 0 to ensure that the vertical beam width remains unchanged after
this function takes effect. In this way, the cell coverage remains basically the same
before and after RF channel intelligent shutdown takes effect.
A macro base station shuts down half of the transmit channels of a cell by default.
A LampSite base station can shut down three out of four RF channels of a 4T cell
or one out of two RF channels of a 2T cell. A cell automatically exits the RF
channel intelligent shutdown state if any of the following conditions is met:
● The current time is not within the RF channel intelligent shutdown period
specified by the NRDUCellPowerSaving.StartTime and
NRDUCellPowerSaving.StopTime parameters.
● The number of RRC_CONNECTED UEs in the cell is greater than the sum of
the NRDUCellPowerSaving.UserNumThld and
NRDUCellPowerSaving.UserNumOffset parameter values. The
NRDUCellPowerSaving.UserNumOffset parameter indicates the offset of the
number of RRC_CONNECTED UEs and is used to prevent a cell from
frequently entering and exiting the RF channel intelligent shutdown state.
● The downlink PRB usage of the cell is greater than the sum of the
NRDUCellPowerSaving.DlPrbThld and NRDUCellPowerSaving.DlPrbOffset
parameter values. The NRDUCellPowerSaving.DlPrbOffset parameter
indicates the offset of the downlink PRB usage threshold and is used to
prevent a cell from frequently entering and exiting the RF channel intelligent
shutdown state.
– A cell may fail to exit the RF channel intelligent shutdown state if the
sum of the NRDUCellPowerSaving.DlPrbThld and
NRDUCellPowerSaving.DlPrbOffset parameter values exceeds 35 in the
scenarios listed in Table 4-10.

5G RAN
Table 4-10 RF channel intelligent shutdown scenario 1 for certain NR

TDD low-frequency AAUs in automatic coverage compensation mode
Model TX/RX Mode Supported Beam

Coverage Scenario
AAU531x 32T32R DEFAULT/

SCENARIO_1/
SCENARIO_6/
SCENARIO_12/
SCENARIO_13
AAU561x 64T64R DEFAULT/

SCENARIO_1/
SCENARIO_3/
SCENARIO_6/
SCENARIO_12/
SCENARIO_13
RRU5xxx 8T8R DEFAULT/

SCENARIO_3
– A cell fails to exit the RF channel intelligent shutdown state if the sum of
the NRDUCellPowerSaving.DlPrbThld and
NRDUCellPowerSaving.DlPrbOffset parameter values exceeds 80 in the
scenarios other than those listed in Table 4-10.
4.5.2.1 Benefits
RF channel intelligent shutdown reduces energy consumption when the network is
under light or no load. However, the energy saving gains are limited in the
following scenarios:
● If an RF module is configured with multiple carriers, RF channel intelligent

shutdown must be configured for all carriers and the effective duration and
coverage compensation mode must be the same among these carriers.
Otherwise, RF channel intelligent shutdown cannot take effect for a macro
base station, decreasing the energy saving gains. For a LampSite base station,
RF channel intelligent shutdown can still take effect, but delivers reduced
energy saving gains.
Assume that RF channel intelligent shutdown has taken effect in single-carrier
scenarios and another carrier needs to be added for capacity expansion. To
enable this function to continue to work after capacity expansion, RF channel
intelligent shutdown should be configured for the new carrier with the same
effective duration and coverage compensation mode as the existing carrier.
Otherwise, RF channel intelligent shutdown no longer takes effect for the
existing carrier after capacity expansion for a macro base station, decreasing
the energy saving gains after capacity expansion. For a LampSite base station,
RF channel intelligent shutdown can still take effect for the existing carrier
after capacity expansion, but delivers reduced energy saving gains.

5G RAN

4.5.2.2 Impacts
Network Impacts
When RF channel intelligent shutdown starts or stops, the UE data rate may
decrease and the service drop rate may increase for approximately 3 minutes.
After RF channel intelligent shutdown takes effect in a cell, the following occurs:
● As the array and power gains decrease:
– For a macro base station:
The rank may decrease or remain unchanged.
▪ If the rank remains unchanged, the modulation and coding scheme

(MCS) index used for downlink scheduling decreases.
▪ If the rank decreases, the MCS index used for downlink scheduling
may decrease or increase.
The channel quality indicator (CQI) may decrease or increase. The initial
block error rate (IBLER) may decrease or increase depending on the MCS
index change.
– For a LampSite base station, the rank is downgraded to rank 1.
– The peak cell rate, peak UE rate, and user-perceived rate decrease; the
scheduling delay increases. Given the same load, more downlink PRBs are
required for transmitting the same amount of data, increasing the
downlink PRB usage.
– The mapping between the CSI-RS and SSB or PRACH may change after
shutdown, increasing the number of reconfigurations of the optimal
beam for sending CSI-RSs.
● When the NRDUCellPowerSaving.CovCompensationMode parameter is set
to AUTO, the cell coverage may be affected, causing the access success rate
to decrease and the service drop rate to increase, though power is
automatically compensated for common channels to ensure that the coverage
after RF channel shutdown is aligned as much as possible with the coverage
before RF channel shutdown. In addition, the power compensation for
common channels may increase the interference between inter-base-station
common channels when the inter-base-station distance is small.
● When the NRDUCellPowerSaving.CovCompensationMode parameter is set
to MANUAL, the coverage after RF channel shutdown may be still poorer
than that before RF channel shutdown, even if the
NRDUCellPowerSaving.CovCompensationPwrOffset parameter has been set
to the maximum. In this case, the access success rate decreases, and the
service drop rate increases.
● For NR TDD 8T8R and NR FDD 8T8R/4T4R/2T2R/2T4R RF modules, the cell
throughput in multi-carrier scenarios may be lower than that in single-carrier
scenarios.

5G RAN
● In NR FDD scenarios, as RRUs have a small number of channels, shutting

down half of the channels for the RRUs decreases the rank used, causing a
significant increase in the PRB usage and affecting the energy saving gains. To
cope with this situation, it is recommended that the downlink PRB usage
threshold be set to 5 and the downlink PRB usage offset be set to 15.
● In medium-load or heavy-load scenarios, the DRB usage may decrease. In
addition, if MU-MIMO Basic Pairing takes effect, the number of paired layers
may increase, the average uplink CCE usage and average downlink CCE usage
may increase, and the CCE aggregation level may decrease. In light-load
scenarios, the CCE usage and the uplink and downlink DCI allocation success
rates may decrease.
● When the proportion of small packets is high:
– The user-perceived rate may fluctuate.
– The cell throughput may fluctuate when the total duration of data
transmission becomes shorter due to insufficient CCE resources.
● The processing delay increases, and the uplink cell throughput and uplink UE
throughput decrease by up to 50%. Table 4-11 shows the decrease in the
downlink cell throughput and downlink UE throughput. The longer the
distance between the UE and the base station, the greater the decrease in the
uplink throughput and downlink throughput. The larger the value of
NRDUCellTrpBeam.MaxSsbPwrOffset,
NRDUCellChnPwr.MaxCommonDciPwrOffset,
NRDUCellChnPwr.PagingMaxPwrOffset,
NRDUCellChnPwr.OsiMaxPwrOffset, or
NRDUCELLCHNPWR.RmsiMaxPwrOffset, the greater the decrease in the
downlink throughput.
Table 4-11 Impacts on the downlink cell throughput and UE throughput in

different scenarios
Scenario Decrease in the
Downlink Cell
Throughput and UE
Throughput
Single base station networking 0% to 70%
Continuous networking except scenarios listed in 0% to 50%

Table 4-10
Scenarios listed in Table 4-10 in single base 60% to 70%

station or continuous networking
● The uplink cell throughput and UE throughput may decrease in the scenarios
listed in Table 4-12.

5G RAN
Table 4-12 RF channel intelligent shutdown scenario for certain NR TDD low-
frequency AAUs/RRUs in automatic coverage compensation mode
Model TX/RX Mode Power Supported Beam
Offset Coverage Scenario
Value
Range
AAU531x/ 64T64R/32T32R [0,3] DEFAULT/

AAU561x/ SCENARIO_1/
AAU581x SCENARIO_3
SCENARIO_6/
SCENARIO_12/
SCENARIO_13
AAU531x/ 64T64R/32T32R (3,6] EXPAND_SCENARIO_1

AAU561x/
AAU581x
AAU533x/ 64T64R/32T32R [0,6] DEFAULT/

AAU5649 SCENARIO_6/
SCENARIO_12/
SCENARIO_13
AAU533x/ 64T64R/32T32R (3,9] EXPAND_SCENARIO_1

AAU563x/
AAU583x/
AAU5649
RRU5xxx 8T8R Any DEFAULT/SCENARIO_3

value
Note: The "Power Offset Value Range" in the table refers to the value range
of any of the following parameters: NRDUCellTrpBeam.MaxSsbPwrOffset,
NRDUCellChnPwr.MaxCommonDciPwrOffset,
NRDUCellChnPwr.PagingMaxPwrOffset,
NRDUCellChnPwr.OsiMaxPwrOffset, and
NRDUCELLCHNPWR.RmsiMaxPwrOffset.

5G RAN
Function Impacts
Name Switch
Low- Remote RIM_ADAPT_ Remote RF channel

frequency interference AVOID_SW Interference intelligent
TDD adaptive option of the Management shutdown does
avoidance NRDUCellAl (Low- not take effect
goSwitch.Ri Frequency when remote
mAlgoSwitc TDD) interference
h parameter adaptive
avoidance is in
effect.
Low- RF module RRU.DORMA RF Module RF channel

frequency deep NCYSW (LTE Deep intelligent
TDD dormancy eNodeB, 5G Dormancy shutdown does
gNodeB) not take effect
when RF module
deep dormancy is
in effect.
FDD UL CoMP INTRA_GNB_ CoMP When RF channel

Low- UL_COMP_S intelligent
frequency W option of shutdown takes
TDD the effect, the TX/RX
NRDUCellAl combinations of
goSwitch.Co the serving and
mpSwitch cooperating cells
parameter for UL CoMP may
not be supported
by CoMP. In this
case, UL CoMP
does not take
effect.

5G RAN

Name Switch
FDD Intra-base- INTRA_GNB_ CoMP If RF channel

Low- station joint DL_JT_SW intelligent
frequency transmission option of the shutdown takes
TDD for DL CoMP NRDUCellAl effect in a cell,
goSwitch.Co intra-base-station
mpSwitch joint transmission
parameter will become
invalid for CoMP
UEs that have
been involved in
intra-base-station
joint transmission
in the cell and will
not take effect on
UEs that are
newly admitted to
the cell. After the
cell exits the RF
channel
intelligent
shutdown state,
intra-base-station
joint transmission
takes effect again.
FDD Channel Macro base MIMO If channel

Low- calibration station: None calibration starts
frequency LampSite before RF channel
TDD base station: intelligent
INTER_RRU_ shutdown takes
CHN_CALIB_ effect, RF channel
SW option of intelligent
the shutdown cannot
NRDUCellAl take effect.
goSwitch.Ch If channel
nCalibSwitc calibration starts
h parameter when RF channel
intelligent
shutdown is in
effect, the RF
channel
intelligent
shutdown status
is not affected.

5G RAN

Name Switch
FDD Antenna port STR MIMO If channel

detection ANTENNAP shutdown has
ORTOPTDET taken effect
before antenna
port detection
starts, the
detection results
will show that the
detection fails.
If channel
shutdown takes
effect during
antenna port
detection, the
channel shutdown
duration is
shortened.
FDD DL 256QAM NRDUCellAl Modulation FDD 2T2R/2T4R/

Low- goSwitch.Dl Schemes 4T4R/8T8R and
frequency 256QamSwi TDD 8T8R RF
TDD tch modules do not
support DL
256QAM after RF
channel
intelligent
shutdown takes
effect.
Low- Low latency HIGH_RELIA URLLC After RF channel

frequency and high BILITY_BASI intelligent
TDD reliability C_SW option shutdown is
of the enabled, transmit
NRDUCellAl channels are shut
goSwitch.Hi down for fixed
ghReliability periods when the
Switch network is under
parameter light load,
affecting the
performance of
UEs performing
high-reliability
services.

5G RAN

Name Switch
Low- NR DU cell RB_DYNAMI Network If NR DU cell

frequency resource C_CONTROL Slicing resource
TDD management _SW option management
between of the between network
network NRDUCellAl slices has taken
slices goSwitch.Ne effect, RF channel
tworkSliceAl intelligent
goSwitch shutdown cannot
parameter take effect in the
and scenarios listed in
ENHANCED_ Table 4-12.
NETWORKS
LICE_SW
option of the
NRCellAlgoS
witch.Netwo
rkSliceAlgoS
witch
parameter
Low- Rate- PDCCH_RAT Scheduling If rate-matching-

frequency matching- EMATCH_S pattern-
TDD pattern- W option of configuration-
configuration the based PDCCH rate
-based NRDUCellPd matching is in
PDCCH rate sch.RateMat effect, RF channel
matching chSwitch intelligent
parameter shutdown cannot
take effect in the
scenarios listed in
Table 4-12.
Low- TRS rate TRS_RATEM Scheduling When the switch

frequency matching ATCH_SW for TRS rate
TDD option of the matching is
NRDUCellPd turned off (that is,
sch.RateMat PDSCH data is
chSwitch transmitted in TRS
parameter symbols), RF
channel
intelligent
shutdown cannot
take effect in the
scenarios listed in
Table 4-12.

5G RAN

Name Switch
Low- Timing TIMING_CAR Energy If timing carrier

frequency carrier RIER_SHUTD Conservation shutdown is in
TDD shutdown OWN_SW and Emission effect, RF channel
option of the Reduction intelligent
NRDUCellAl shutdown cannot
goSwitch.Po take effect in the
werSavingS scenarios listed in
witch Table 4-12.
parameter
Low- Intelligent INTRA_GNB_ Energy When intelligent

frequency carrier MULTI_CARR Conservation carrier shutdown
TDD shutdown _SD_SW or and Emission is in effect:
INTER_GNB_ Reduction ● If the local cell
MULTI_CARR is a capacity-
_SD_SW layer cell, RF
option of the channel
NRDUCellAl intelligent
goSwitch.Po shutdown
werSavingS cannot take
witch effect in the
parameter scenarios listed
in Table 4-12.
● If the local cell
is a basic-layer
cell and RF
channel
intelligent
shutdown
takes effect in
the scenarios
listed in Table
4-12, the
related
capacity-layer
cells may exit
the intelligent
carrier
shutdown
state.

5G RAN

Name Switch
Low- LTE and NR NR: LTE and NR If LTE and NR

frequency intelligent LNR_SMART Intelligent intelligent carrier
TDD carrier _CARRIER_S Carrier shutdown is in
shutdown HUTDOWN_ Shutdown effect, RF channel
SW option of intelligent
the shutdown cannot
NRDUCellAl take effect in the
goSwitch.Po scenarios listed in
werSavingS Table 4-12.
witch
parameter
LTE:
CellAlgoExtS
witch.LnrSm
artCarrierSh
utdownSw
FDD Power saving POWER_SAV Energy If power saving
Low- scheduling ING_SCHED Conservation scheduling has
frequency ULE_SW and Emission taken effect and
TDD option of the Reduction RF channel
NRDUCellAl intelligent
goSwitch.Po shutdown is
werSavingS enabled in the
witch scenarios listed in
parameter Table 4-12, power
saving scheduling
may stop.
For 8T8R RF
modules, when RF
channel
intelligent
shutdown takes
effect, beam-level
adjustment of the
RMSI broadcast
interval in power
saving scheduling
does not take
effect. Therefore,
cell-level
adjustment of the
RMSI broadcast
interval is
recommended in
such cases.

5G RAN

Name Switch
Low- Power saving BWP2_SWIT UE Power If RF channel

frequency BWP CH option of Saving intelligent
TDD the shutdown is
NRDUCellUe enabled in the
PwrSaving.B scenarios listed in
wpPwrSavin Table 4-12, UEs
gSw switch from BWP2
parameter to BWP1.
Low- Basic beam DL_INITIAL_ Beam You are advised to

frequency management BEAM_SELEC Management select the
TDD T_SW option DL_INITIAL_BEA
of the M_SELECT_SW
NRDUCellAl option of the
goSwitch.Be NRDUCellAlgoSw
amOptSwitc itch.BeamOptSwi
h parameter tch parameter
before enabling
RF channel
intelligent
shutdown.
Otherwise, the
RRC connection
setup success rate
decreases.
4.5.3 Requirements
4.5.3.1 Licenses
FOFD-031205 RF Channel NR0S00RCIS00 per Cell

Intelligent
Shutdown
4.5.3.2 Software
None

5G RAN

Name Switch
Low- Hyper Cell NRDUCell.N Hyper Cell RF channel

frequency rDuCellNet (Low- intelligent
TDD workingMod Frequency shutdown cannot
e set to TDD) be enabled for a
HYPER_CELL hyper cell served
by a macro base
station.
RF channel
intelligent
shutdown can be
enabled for a
hyper cell served
by a LampSite
base station.
FDD Cell NRDUCell.N Cell RF channel

Low- Combination rDuCellNet Combination intelligent
frequency workingMod shutdown cannot
TDD e set to be enabled for a
HYPER_CELL combined cell
_COMBINE_ served by a macro
MODE base station.
RF channel
intelligent
shutdown can be
enabled for a
combined cell
served by a
LampSite base
station.
Low- Extended NRDUCell.C Extended 8T8R NR TDD-

frequency Cell Range ellRadius set Cell Range capable RF
TDD (TDD) to a value modules do not
greater than support RF
14500 channel
intelligent
shutdown when
Extended Cell
Range (TDD)
takes effect.

5G RAN

Name Switch
FDD Extended NRDUCell.C Extended 2T2R or 2T4R NR

Cell Range ellRadius set Cell Range FDD-capable RF
(FDD) to a value modules do not
greater than support RF
14500 channel
intelligent
shutdown when
Extended Cell
Range (FDD)
takes effect.
FDD Hybrid DSS LTE_NR_FDD LTE FDD and RF channel

Based on _SPCT_SHR_ NR Spectrum intelligent
Asymmetric SW option of Sharing shutdown and
Bandwidth the Hybrid DSS Based
NRDUCellAl on Asymmetric
goSwitch.Sp Bandwidth cannot
ectrumClou be both enabled.
dSwitch
parameter
and
LTE_NR_FDD
_SPCT_SHR_
ASYM_SW
option of the
NRDUCellAl
goSwitch.Sp
ectrumClou
dEnhSwitch
parameter
FDD LTE FDD and LTE: LTE FDD and LTE FDD and NR
NR Flash SpectrumClo NR Spectrum Flash Dynamic
Dynamic ud.Spectrum Sharing Spectrum Sharing
Spectrum CloudSwitch and RF channel
Sharing set to intelligent
LTE_NR_SPE shutdown cannot
CTRUM_SHR be both enabled.
NR:
LTE_NR_FDD
_SPCT_SHR_
SW option of
the
NRDUCellAl
goSwitch.Sp
ectrumClou
dSwitch
parameter

5G RAN

Name Switch
Low- Distributed DM_MIMO_ MIMO RF channel

frequency massive SERVICE_SW intelligent
TDD MIMO ITCH option shutdown is not
of the supported in a
NRDUCellAl distributed
goSwitch.D massive MIMO
mMimoSwit cell.
ch parameter
4.5.3.3 Hardware
Base Station Models

with the BBU3910.
Boards
RF Modules
All AAUs/RRUs that meet the requirements listed in Table 4-13 support this
Table 4-13 Requirements of RF channel intelligent shutdown for AAUs/RRUs

RAT Model TX/RX Coverage Supported Beam
Mode Compensation Coverage Scenario
Mode
Low- AAU533x/ 64T64R Automatic or DEFAULT/

frequency AAU563x/ / manual SCENARIO_1/
TDD AAU583x/ 32T32R SCENARIO_3/
AAU5649 SCENARIO_6/
SCENARIO_12/
SCENARIO_13/
EXPAND_SCENARIO_1

5G RAN
RAT Model TX/RX Coverage Supported Beam

Mode Compensation Coverage Scenario
Mode
Low- AAU5639 64T64R Automatic or DEFAULT/

frequency operating in manual SCENARIO_1/
TDD n78 SCENARIO_3/
SCENARIO_6/
SCENARIO_12/
SCENARIO_13/
EXPAND_SCENARIO_1
Low- AAU5639 64T64R Automatic or DEFAULT

frequency operating in manual
TDD n40
Low- AAU531x/ 64T64R Automatic or DEFAULT/

frequency AAU561xa/ / manual SCENARIO_1/
TDD AAU581x 32T32R SCENARIO_3/
SCENARIO_6/
SCENARIO_12/
SCENARIO_13/
EXPAND_SCENARIO_1
Low- RRU5xxx 8T8R Automatic or DEFAULT/

frequency manual SCENARIO_3/
TDD EXPAND_SCENARIO_1
FDD RRU5xxx/ 8T8R Automatic DEFAULT/

AAU5972/ SCENARIO_201
AAU5973/
AAU5973e 4T4R/ Automatic DEFAULT
2T2R/
2T4R
FDD RRU5xxx/ 8T8R Manual DEFAULT/

AAU5972/ SCENARIO_201/
AAU5973/ SCENARIO_202
AAU5973e
4T4R Manual DEFAULT/
SCENARIO_201
2T2R/ Manual DEFAULT

2T4R
a: RF channel intelligent shutdown is not supported by the AAU5613 with the

value of Item in the command output of DSP ELABEL being 02312CHM.

5G RAN
NOTE
● This function requires two or less carriers to be configured for each of the NR TDD 8T8R
and NR FDD 8T8R/4T4R/2T2R/2T4R RF modules.
● The beam coverage scenario supported by an NR TDD RF module is specified by the
NRDUCellTrpBeam.CoverageScenario parameter.
● The beam coverage scenario supported by an NR FDD RF module is specified by the
NRDUFddCellTrpBeam.CoverageScenario parameter.
All NR TDD-capable 4T4R or 2T2R pRRUs support this function. For details about
such pRRUs, see technical specifications of the related pRRUs in 3900 & 5900
Cells
Macro base station: For an NR FDD cell, the downlink bandwidth (specified by
NRDUCell.DlBandwidth) must be 15 MHz or higher, and there is no requirement
for the uplink bandwidth (specified by NRDUCell.UlBandwidth). When the
NRDUCellPowerSaving.CovCompensationMode parameter is set to AUTO, both
the uplink and downlink bandwidths of an NR TDD cell must be 80 MHz or higher.
NOTE
RF channel intelligent shutdown is also supported if an NR FDD cell has a downlink

bandwidth of 15 MHz and a customized downlink bandwidth (specified by
NRDUCell.CustomizedDlBandwidth) of 14.6 MHz or 14.8 MHz.
LampSite base station: There is no requirement for the uplink and downlink cell
bandwidths.
4.5.3.4 Others
None


Name


5G RAN

Name
Power NRDUCellAlgoSwitch.PowerSa Select the RF_SHUTDOWN_SW

Saving vingSwitch option of this parameter.
Switch RF channel intelligent shutdown
is not recommended in
distributed antenna coverage
scenarios, as enabling this
function may affect the
coverage on some floors.

Policy
Index

requirements:
Stop Time NRDUCellPowerSav-
ing.StopTime ● For a policy of an energy
saving function, the interval
between the stop time and
start time must be longer
than 20 minutes.
stop time refers to the next
day. For example:
to be enabled after policy A
of this function has been
policy A.

5G RAN

Name

Saving ing.PowerSavingType RF_SHUTDOWN.
Type
Downlink NRDUCellPowerSav- You are advised to set this

PRB ing.DlPrbThld parameter to its recommended
Threshold value.

PRB Offset ing.DlPrbOffset parameter to its recommended
value.
UE NRDUCellPowerSav- You are advised to set this

Number ing.UserNumThld parameter to its recommended
Threshold value.
User NRDUCellPowerSav- You are advised to set this

Number ing.UserNumOffset parameter to its recommended
Offset value.
Coverage NRDUCellPowerSav- The value AUTO is

Compensa ing.CovCompensationMode recommended.
tion Mode
Coverage NRDUCellPowerSav- Set this parameter based on the

Compensa ing.CovCompensationPwrOff- network plan and the RF
tion Power set module's maximum capability
Offset of aggregating the cell common
channel transmit power.
Reserved NRDUCellRsvdExt02.RsvdSwPa Set RSVDSWPARAM1_BIT21

Switch ram1 based on the network plan.
Parameter
1
Reserved NRDUCellRsvdExt02.RsvdSwPa You are advised to set

Switch ram0 RSVDSWPARAM0_BIT28 to 0.
Parameter
0
NOTE
parameter must be set to CELL_TDD or CELL_FDD. This function is configurable but does
not take effect in a cell with this parameter set to CELL_SUL.
When RF channel intelligent shutdown is enabled, it is recommended that the PDCCH
symbol number adaptation switch (specified by the UE_PDCCH_SYM_NUM_ADAPT_SW
option of the NRDUCellPdcch.PdcchAlgoExtSwitch parameter) be turned on to reduce the
impact on user-perceived rates. For details about PDCCH symbol number adaptation, see
Channel Management.

5G RAN

network scenario.

Examples for an NR TDD cell
//Enabling RF channel intelligent shutdown
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=RF_SHUTDOWN_SW-1;
//Setting an energy saving policy of RF channel intelligent shutdown for an NR TDD cell
StopTime=03&00&00, PowerSavingType=RF_SHUTDOWN, DlPrbThld=10, DlPrbOffset=15, UserNumThld=20,
UserNumOffset=20, CovCompensationMode=AUTO;
//(Optional) Enabling the power aggregation enhancement function when the transmit power
compensated for common channels in the cell is automatically determined by a macro base station
//Configuring the beam weight after RF channel intelligent shutdown takes effect to ensure that the
coverage remains basically the same before and after this function is enabled
MOD NRDUCELLRSVDEXT02: NrDuCellId=0, RsvdSwParam0=RSVDSWPARAM1_BIT28-0
//(Optional) Setting another energy saving policy of RF channel intelligent shutdown for the NR TDD cell
UserNumOffset=20, CovCompensationMode=MANUAL, CovCompensationPwrOffset=6;
Examples for an NR FDD cell

//Enabling RF channel intelligent shutdown
//Setting an energy saving policy of RF channel intelligent shutdown for an NR FDD cell
UserNumOffset=20, CovCompensationMode=AUTO;
//(Optional) Enabling the power aggregation enhancement function when the transmit power
//(Optional) Setting another energy saving policy of RF channel intelligent shutdown for the NR FDD cell
UserNumOffset=20, CovCompensationMode=MANUAL, CovCompensationPwrOffset=6;

N/A

conditions.
//Disabling RF channel intelligent shutdown
//Removing an energy saving policy of RF channel intelligent shutdown
//(Optional) Removing the other energy saving policy of RF channel intelligent shutdown
//(Optional) Disabling the power aggregation enhancement function when the transmit power

5G RAN


After RF channel intelligent shutdown is activated, use either of the following
● Method 1:
Power Saving Switch parameter is RF Channel Power Saving
Switch:On in the command output, RF channel intelligent shutdown has
been enabled.
least one record with Power Saving Type being RF Channel Power
Saving.
NOTE
If there are two or more records with Power Saving Type being RF Channel
Power Saving, RF channel intelligent shutdown has been enabled in two or more
time periods.
period for RF channel intelligent shutdown.
▪ If it is not, wait until the start time of RF channel intelligent

shutdown arrives.
d. Check whether the downlink PRB usage of the cell (which equals
N.PRB.DL.DrbUsed.Avg divided by N.PRB.DL.Avail.Avg) is less than or
equal to the downlink PRB usage threshold for starting RF channel
intelligent shutdown (specified by the NRDUCellPowerSaving.DlPrbThld
parameter). In addition, check whether the number of RRC_CONNECTED
UEs in the cell (indicated by N.User.RRCConn.Avg) is less than or equal
to the UE number threshold for starting this function (specified by the
NRDUCellPowerSaving.UserNumThld parameter).
▪ If they are, go to e.
▪ If one or both are not, wait until the downlink PRB usage of the cell
is less than or equal to the downlink PRB usage threshold for starting
RF channel intelligent shutdown and the number of
RRC_CONNECTED UEs in the cell is less than or equal to the UE
number threshold for starting this function.
e. Wait 5 minutes in single-carrier scenarios and about 5–20 minutes in
multi-carrier scenarios.
Then, run the DSP NRDUCELL command. Verify that the value of the
Power Saving State parameter is RF Channel Power Saving:Enabled,
which indicates that RF channel intelligent shutdown has taken effect.
● Method 2:
Run the DSP NRDUCELLPOWERSAVING command to query the status of RF
channel intelligent shutdown.

5G RAN
– If the value of Power Saving Type is RF Channel Power Saving and the
value of Current State is Enabled, RF channel intelligent shutdown has
taken effect.
– If the value of Power Saving Type is RF Channel Power Saving and the
value of Current State is Disabled, check the Current Disabled Cause
parameter value to determine the reason why RF channel intelligent
shutdown does not take effect. Table 4-15 lists possible reasons.
Table 4-15 Possible reasons why RF channel intelligent shutdown does

not take effect
Reason Description
Insufficient License No license for this function is available.
Cell Unavailable The cell is blocked or deactivated, fails to be

set up, or is unavailable due to other reasons.
Triggering Time Not The current time is not within the range
Reached specified for RF channel intelligent shutdown.
Impacted Feature None

Taken Effect
Downlink PRB None

Threshold Not
Reached
UE Number Threshold None

Not Reached
In Penalty State A penalty is being imposed upon an exit from

the RF channel intelligent shutdown state.
RF Hardware ● The RF module is configured to work in TN

Capability Not mode, RF channel intelligent shutdown is
Supported enabled, LTE carriers are activated, but LNR
coordinated channel shutdown is disabled.
● The RF module is configured to work in LN
mode, RF channel intelligent shutdown is
enabled, but LNR coordinated channel
shutdown is disabled.
● The power aggregation capability of the RF
module is insufficient.
● The temperature differential of the RF
module is too large.
● The channels of the RF module are faulty.
● Other hardware faults occur.
Shared Channel Not In multi-carrier co-PA scenarios, not all

Coordinated carriers meet the conditions for entering RF
channel intelligent shutdown.

5G RAN
Reason Description
Multi-Carrier Not ● In multi-carrier co-RF module scenarios:

Coordinated – The effective durations of RF channel
shutdown under energy saving policies
for different carriers do not overlap.
– The effective durations for different
carriers overlap, but the configurations
of coverage compensation mode are
inconsistent among these carriers.
● The compensated power required by
different carriers is inconsistent.
● An activated carrier is added in the
scenarios listed in Table 4-12.
Channel Calibration in None

Progress
Channel Calibration None

Info Being Queried
Detecting for Port None

Mapping Optimization
Others ● The current time is within the range

specified for RF channel intelligent
shutdown, but this function is in its
detection period, which lasts for 5 minutes.
● The RF module is configured to work in
multiple RATs. In addition, RF channel
intelligent shutdown and LNR coordinated
channel shutdown are both enabled or
disabled.
● RRC connection reconfiguration fails for a
batch of UEs.
● None of the counters is subscribed to.
● Internal software or other reasons cause
the function to fail.

obtained before and after RF channel intelligent shutdown is enabled can be

5G RAN
● The RF channel shutdown duration caused by the activation of this function

can be obtained by using the N.PowerSaving.RFShutdown.Dur counter on
the MAE-Access.

5G RAN
Feature Parameter Description 5 Network Level Energy Saving
5 Network Level Energy Saving
5.1 Intelligent Carrier Shutdown
5.1.1 Principles
5.1.1.1 Energy Saving Principles

Unlike single-carrier networking, multi-carrier co-coverage networking provides
larger network capacity as well as a higher data throughput when the network is
heavily loaded. However, such networking wastes base station energy when the
network is under light or no load.
Intelligent carrier shutdown is introduced to address this issue. Intelligent carrier
shutdown enables the base station to transfer UEs from capacity-layer cells to
basic-layer cells and to dynamically shut down capacity-layer carriers when the
network is under light or no load within specified periods. In addition, if the PA (of
an RF module) serving a shut-down capacity-layer carrier is not serving any other
operating carrier, the PA will also be shut down. Figure 5-1 shows how this
function works.
Figure 5-1 Working principles of intelligent carrier shutdown

5G RAN
Related Concepts
● Basic-layer carriers provide basic coverage for the network and will not be
shut down by the intelligent carrier shutdown function. For example, F1 in
Figure 5-1 is a basic-layer carrier. The cells served by basic-layer carriers are
referred to as basic-layer cells.
● Capacity-layer carriers support large traffic volumes during peak hours and
can be shut down by the intelligent carrier shutdown function. For example,
F2 in Figure 5-1 is a capacity-layer carrier. The cells served by capacity-layer
carriers are referred to as capacity-layer cells.
NOTE
Intelligent carrier shutdown is enabled in capacity-layer cells. One capacity-layer cell can
correspond to one or more basic-layer cells. Basic-layer cells and capacity-layer cells must
be inter-frequency neighboring cells of each other.
Basic-layer and capacity-layer cells are relative concepts identified by the

NRCellRelation.PowerSavingCellFlag parameter during neighbor relationship
configuration.
● If this parameter is set to COVERAGE, the neighboring cell is a basic-layer cell
and the serving cell is a capacity-layer cell.
● If this parameter is set to CAPACITY, the neighboring cell is a capacity-layer
cell and the serving cell is a basic-layer cell.
● If this parameter is set to NOT_CONFIG, neither the serving cell nor the
neighboring cell is defined as a capacity-layer or basic-layer cell. The
neighboring cell is not considered in intelligent carrier shutdown.
Take the carriers in Figure 5-1 as an example:
● For a capacity-layer cell operating in F2, the
NRCellRelation.PowerSavingCellFlag parameter needs to be set to
COVERAGE for the neighbor relationship with a basic-layer cell operating in
F1.
● For the basic-layer cell operating in F1, the
NRCellRelation.PowerSavingCellFlag parameter needs to be set to
CAPACITY for the neighbor relationship with the capacity-layer cell operating
in F2.
In NR multi-carrier networking scenarios, it is recommended that capacity-layer
and basic-layer cells be configured based on the descriptions in Table 5-1.
Table 5-1 Setting notes for capacity-layer and basic-layer cells

Networking Scenario Capacity-Layer Cell Basic-Layer Cell
NR TDD and NR FDD NR TDD cells NR FDD cells

coordinated networking
NR TDD sub-6 GHz and NR TDD sub-6 GHz cells NR TDD sub-3 GHz cells
NR TDD sub-3 GHz
coordinated networking
Inter-band NR FDD Cells with a high Cells with a low

coordinated networking frequency frequency

5G RAN
Networking Scenario Capacity-Layer Cell Basic-Layer Cell
Intra-band multi-carrier Cells with a high Cells with a low

networking frequency frequency
5.1.1.2 Energy Saving Procedure

Intelligent carrier shutdown can be enabled by selecting the
INTRA_GNB_MULTI_CARR_SD_SW or INTER_GNB_MULTI_CARR_SD_SW option
of the NRDUCellAlgoSwitch.PowerSavingSwitch parameter for a capacity-layer
cell.
● The INTRA_GNB_MULTI_CARR_SD_SW option specifies whether to enable
intra-base-station multi-carrier shutdown.
● The INTER_GNB_MULTI_CARR_SD_SW option specifies whether to enable
inter-base-station multi-carrier shutdown.
This function takes effect every day within the configured intelligent carrier
shutdown periods under certain conditions. The periods, load threshold, and other
information under an energy saving policy are specified by the parameters in the
energy saving type indicated by an energy saving policy index. Intelligent
carrier shutdown requires that this parameter be set to
INTRA_GNB_MULTI_CARR_SD or INTER_GNB_MULTI_CARR_SD, meaning
that under the corresponding energy saving policy, the carrier of the local cell
will be shut down in the specified period under certain load conditions in
intra- or inter-base-station multi-carrier scenarios.
After intelligent carrier shutdown is enabled, the base station checks whether the
conditions for entering intelligent carrier shutdown are met throughout a period
specified by the NRDUCellPowerSaving.ShutdownTrigJudgePeriod parameter.
After intelligent carrier shutdown takes effect for a capacity-layer cell, the base
station checks whether the conditions for exiting intelligent carrier shutdown are
met at a period of 1 minute. Figure 5-2 shows the procedure for intelligent carrier
shutdown in a capacity-layer cell.

5G RAN
Figure 5-2 Intelligent carrier shutdown procedure
Conditions for Entering Intelligent Carrier Shutdown

If all of the conditions listed below are met, a UE transfer procedure starts in a
capacity-layer cell. If one of the conditions is not met, the base station waits for
the next carrier shutdown decision period.
● The capacity-layer cell must meet all of the following conditions:

– The current time is within the range specified for intelligent carrier
shutdown (determined by the NRDUCellPowerSaving.StartTime and
NRDUCellPowerSaving.StopTime parameters).

5G RAN
– The capacity-layer cell is not in any energy saving penalty state.

● The basic-layer cells corresponding to the capacity-layer cell must meet one
of the following conditions:
– All basic-layer carriers are available.
– Some basic-layer carriers are available, while others, functioning as
capacity-layer carriers of other basic-layer carriers, are in the intelligent
carrier shutdown state. Alternatively, some basic-layer carriers are
available, while others are in the LTE and NR intelligent carrier shutdown
state.
● The capacity-layer cell and the corresponding basic-layer cells must meet all
the following conditions:
– The total downlink physical resource block (PRB) usage of the capacity-
layer carrier and basic-layer carriers is less than or equal to the downlink
PRB usage threshold specified by the NRDUCellPowerSaving.DlPrbThld
parameter, where
Total downlink PRB usage of the capacity-layer carrier and basic-layer
carriers = (Number of PRBs used by PDSCH DRBs of the capacity-layer
carrier + Number of downlink PRBs used by the basic-layer carriers)/
Number of available downlink PRBs of the basic-layer carriers
NOTE
The base station automatically obtains the number of PRBs used by PDSCH DRBs
of the capacity-layer carrier, the number of downlink PRBs used by the basic-
layer carriers, and the number of available downlink PRBs of the basic-layer
carriers. It then calculates the total downlink PRB usage of the capacity-layer
carrier and basic-layer carriers.
If multiple basic-layer carriers correspond to one capacity-layer carrier,
the sum of PRBs of these basic-layer carriers are used in the preceding
formula.
– The total number of RRC_CONNECTED UEs on the capacity-layer carrier
and a basic-layer carrier is less than or equal to the UE number threshold
specified by the NRDUCellPowerSaving.UserNumThld parameter.
If multiple basic-layer carriers correspond to one capacity-layer carrier,
each combination of the basic-layer and capacity-layer carriers must
meet this condition.
– The Xn interface is in the normal state in multi-carrier inter-base-station
scenarios.
NOTE
If the capacity-layer cell is a hyper cell or combined cell:

● The total downlink PRB usage of the capacity-layer carrier and basic-layer
carriers is calculated based on the maximum number of used PRBs among all
TRPs. When intelligent carrier shutdown takes effect, carriers of all TRPs are
shut down.
● It is recommended that basic-layer cells also be hyper cells or combined cells.
It is not recommended to configure common cells as basic-layer cells.
UE Transfer
UEs are transferred from the capacity-layer cell as follows:

5G RAN
● In SA networking, UEs are transferred from the capacity-layer cell to basic-

layer cells through inter-frequency handovers, and those that cannot be
handed over are transferred to basic-layer cells through redirection.
● In NSA networking, UE connections on the NR side are released.
● For UEs that treat the capacity-layer cell as a secondary cell (SCell) in carrier
aggregation (CA), the SCell is removed. For UEs that treat the capacity-layer
cell as the primary cell (PCell) in CA, they are transferred to basic-layer cells in
the same way as SA UEs.
If UEs cannot be transferred out of the capacity-layer cell 30s after the UE transfer
procedure starts (for example, they do not support the RAT or band of the basic-
layer cell), the intelligent carrier shutdown procedure stops and cannot be
triggered for the capacity-layer cell again within 30 minutes.
NOTE
If the RAT/Frequency Selection Priority (RFSP)-based handover policy conflicts with that
related to intelligent carrier shutdown, only the former takes effect.
Entering Intelligent Carrier Shutdown

Once all UEs are transferred out of the capacity-layer cell, no RRC_CONNECTED
UEs remain in the cell, and the cell enters the intelligent carrier shutdown state. If
the PA (of an RF module) serving the shut-down carrier is not serving any other
operating carrier, the PA will also be shut down to save energy.
Conditions for Exiting Intelligent Carrier Shutdown

A capacity-layer cell automatically exits the intelligent carrier shutdown state and
cannot enter this state again within 30 minutes if any of the conditions listed
below is met. If none of these conditions is met, the cell remains in the intelligent
carrier shutdown state.
● The current time is not within the range specified for intelligent carrier
shutdown.
● The total downlink PRB usage of basic-layer carriers is greater than the sum
of the NRDUCellPowerSaving.DlPrbThld and
NRDUCellPowerSaving.DlPrbOffset parameter values.
● The number of RRC_CONNECTED UEs served by the basic-layer carriers is
greater than 1.5 times the value of the
NRDUCellPowerSaving.UserNumThld parameter.
● A basic-layer neighboring cell is added for the capacity-layer cell.
● The Xn interface is in the abnormal state in multi-carrier inter-base-station
scenarios.
● Any of the basic-layer carriers becomes unavailable, excluding when a carrier
becomes unavailable due to entering the intelligent carrier shutdown state or
LTE and NR intelligent carrier shutdown state.

5G RAN
NOTE
● When one basic-layer carrier becomes unavailable in inter-base-station scenarios, there

may be a minute-level delay for the wake-up of the capacity-layer cell. This is because
the messages need to be frequently transmitted over the Xn interface to indicate the
energy saving status and capacity-layer cell wake-up notifications, leading to possible
flow control.
● If a basic-layer cell is a hyper cell or combined cell and some of its TRP carriers become
unavailable, the capacity-layer cell also automatically exits the intelligent carrier
shutdown state.
● The 30-minute penalty is not imposed if the capacity-layer cell exits the intelligent
carrier shutdown state because the function switch is turned off or because the cell is
deactivated and then reactivated.
● The 30-minute penalty is not imposed if the capacity-layer cell exits the intelligent
carrier shutdown state because the function switch is turned off, the cell is deactivated
and then reactivated, or the base station software version is upgraded. After the
capacity-layer cell is deactivated and then reactivated or the base station software
version upgrade is complete, the base station determines whether the cell enters the
intelligent carrier shutdown state again based on related entering conditions.
5.1.2.1 Benefits
In multi-frequency multi-carrier co-coverage scenarios, enabling intelligent carrier
shutdown reduces energy consumption when the network is under light or no
load. However, the energy saving gains are limited in the following scenarios:
● When multiple carriers share the same PA of an RF module, the PA cannot be
shut down if an NR carrier is shut down while the other carriers are still
working. Energy saving gains decrease in this case.
5.1.2.2 Impacts
Network Impacts
● When intelligent carrier shutdown takes effect, the values of counters related
to inter-frequency handovers and redirections change.
If a UE attempts to be handed over to a capacity-layer cell whose carrier is to
be shut down when a UE transfer process (which lasts 30s at most) is ongoing
for this cell, the source cell does not initiate the handover. In this case, the
values of counters related to outgoing and incoming handover attempts
increase in the source and capacity-layer cell, respectively. However, the
values of counters related to handover executions and successful handovers
do not increase. As Huawei-defined KPIs Inter-Frequency Handover Out
Success Rate (CU) and Intra-RAT Handover In Success Rate (CU) are
calculated using the number of outgoing/incoming handover executions as
the denominator, these KPIs are not affected in this scenario. However, if the

5G RAN
user-defined KPIs are calculated using the number of outgoing/incoming

handover attempts as the denominator, these KPIs may be slightly affected in
this scenario.
● During NR carrier shutdown, new UEs are prohibited from accessing an NR
cell. If UEs attempt to be handed over to the NR cell, the values of the
counters related to handover preparation failures (such as
N.HO.IntraFreq.FailOut.PrepFailure) slightly increase.
● This function saves energy by shutting down carriers, but the cells remain
activated. As such, when this function takes effect, the performance counters
and KPIs listed in Table 5-2 are still in measurement, which has no impact on
the energy saving effect. The exact time when carrier shutdown actually starts
taking effect may not be synchronized with that when related performance
counters are reported. Consequently, if carrier shutdown starts taking effect in
a measurement period, there will be a measurement error of less than 5
minutes between the reported results and the actual results for the shut-
down cell in the measurement period.
Table 5-2 Related performance counters and KPIs

● PRB Measurement ● Counters related to the number of used

● Hyper Cell TRP PRB PRBs
● DU Cell Operator PRB available PRBs
physical downlink control channel
(PDCCH) control channel elements
(CCEs)
● Counters related to the number of
PDCCH resource allocation times
● PRB usage
DU Cell Algorithm ● Counters related to the total number of

Measurement physical uplink shared channel (PUSCH)
transmission time intervals (TTIs)
● Counters related to the total number of
PDSCH TTIs
DU Cell SI Message Number of SI transmissions

Measurement

5G RAN
● Channel Quality ● Counters related to interference and

Measurement noise received in the uplink
● DU Cell TRP Channel ● Counters related to uplink received
Quality Measurement signal strength indicator (RSSI)
● Uplink Interference ● Counters related to uplink and downlink
Measurement on PRB 0 to power
PRB 99 ● Counters related to average interference
● Uplink Interference and noise detected on a single PRB
Measurement on PRB 100 ● Counters related to the maximum
to PRB 199 interference and noise detected on a
● Uplink Interference single PRB
Measurement on PRB 200
to PRB 272
● In the case of false physical random access channel (PRACH) detection where
the base station mistakenly regards interference or noise as the random
access preambles of UEs, measurement for the following counters and KPIs
will continue:
– Counters related to the number of random preamble receptions
– Counters related to the number of random preamble responses
– Counters related to the number of UEs scheduled in the uplink and
downlink in a cell
– Counters related to uplink data transmission duration
– Counters related to the number of transport blocks (TBs) used for uplink
data transmission
– Counters related to modulation and coding scheme (MCS) index
distribution for scheduling on the PUSCH
– Counters related to the number of resource blocks (RBs) used for
scheduling on the PUSCH
– PUSCH RB usage
Function Impacts
Name Switch
FDD Downlink INTRA_BAN Carrier After intelligent

Low- intra-band D_CA_SW Aggregation carrier shutdown
frequency CA option of the takes effect, the
TDD NRDUCellAl capacity-layer
goSwitch.Ca cells that have
AlgoSwitch been shut down
parameter cannot be
configured as
SCells for UEs.

5G RAN

Name Switch
FDD Downlink INTRA_FR_I Carrier After intelligent

Low- intra-FR NTER_BAND Aggregation carrier shutdown
frequency inter-band _CA_SW takes effect, the
TDD CA option of the capacity-layer
NRDUCellAl cells that have
goSwitch.Ca been shut down
AlgoSwitch cannot be
parameter configured as
SCells for UEs.
FDD Inter-gNodeB INTER_GNO Carrier After intelligent

Low- CA DEB_CA_SW Aggregation carrier shutdown
frequency option of the takes effect, the
TDD NRDUCellAl capacity-layer
goSwitch.Ca cells that have
AlgoSwitch been shut down
parameter cannot be
configured as
SCells for UEs.
FDD Symbol NRDUCellAl Energy When intelligent

Low- power saving goSwitch.Sy Conservation carrier shutdown
frequency mbolShutdo and Emission takes effect for a
TDD wnSwitch Reduction carrier:
● If the RF
module is not
serving any
other NR
carrier, symbol
power saving
does not take
effect.
● If the RF
module is
serving other
NR carriers, the
status of
symbol power
saving for
these carriers is
not affected.

5G RAN

Name Switch
FDD Deep symbol DEEP_SYMB Energy When intelligent

Low- power saving OL_SHUTDO Conservation carrier shutdown
frequency WN_SW and Emission takes effect for a
witch other NR
parameter carrier, deep
symbol power
saving does
not take effect.
● If the RF
module is
serving other
NR carriers, the
status of deep
symbol power
saving for
these carriers is
not affected.
FDD Power saving POWER_SAV Energy When intelligent

Low- scheduling ING_SCHED Conservation carrier shutdown
frequency ULE_SW and Emission takes effect for a
witch other NR
parameter carrier, power
saving
scheduling
does not take
effect.
● If the RF
module is
serving other
NR carriers, the
status of
power saving
scheduling for
these carriers is
not affected.

5G RAN

Name Switch
FDD Multi-RAT MULTI_RAT_ Multi-RAT When intelligent

Low- coordinated SYMBOL_SH Coordinated carrier shutdown
frequency symbol UTDOWN_S Symbol takes effect for a
TDD power saving W option of Power Saving carrier:
the ● If the RF
NRDUCellAl module is not
goSwitch.Po serving any
werSavingS other NR
witch carrier, multi-
parameter RAT
coordinated
symbol power
saving does
not take effect.
● If the RF
module is
serving other
NR carriers, the
status of multi-
RAT
coordinated
symbol power
saving for
these carriers is
not affected.

5G RAN

Name Switch
FDD LTE and NR LNR_BUNDL Multi-RAT When intelligent

Low- bundled ED_SCHEDU Coordinated carrier shutdown
frequency scheduling LING_SW Symbol takes effect for a
TDD option of the Power Saving carrier:
witch other NR
parameter carrier, LTE and
NR bundled
scheduling
does not take
effect.
● If the RF
module is
serving other
NR carriers, the
status of LTE
and NR
bundled
scheduling for
these carriers is
not affected.
Low- RF module RRU.DORMA RF Module Intelligent carrier

frequency deep NCYSW (LTE Deep shutdown does
TDD dormancy eNodeB, 5G Dormancy not take effect
gNodeB) when RF module
deep dormancy is
in effect.
FDD Cell load STR None Cell load

Low- simulation NRDUCELLSI simulation cannot
frequency MULATELOA be started when
TDD D intelligent carrier
shutdown is
enabled. If cell
load simulation
has started, it will
stop when
intelligent carrier
shutdown is
enabled.
Therefore,
enabling both
functions is not
recommended.

5G RAN

Name Switch
FDD ANR NR_NR_ANR ANR When automatic

Low- _DEL_SW removal of
frequency option of the neighboring cells
TDD NRCellAlgoS in ANR takes
witch.AnrSw effect, intelligent
itch carrier shutdown
parameter does not take
effect if the
neighbor
relationships with
the basic-layer
cells are
automatically
removed for
capacity-layer
cells.
FDD CMAS gNBSibConfi CMAS When an NR

Low- g.SibType carrier is shut
frequency set to down, the
TDD SIB_TYPE_8 corresponding NR
cell is blocked and
commercial
mobile alert
system (CMAS)
warning
notifications
cannot be
properly sent in
this cell. However,
UEs can still
receive CMAS
warning
notifications from
other carriers.

5G RAN

Name Switch
Low- RF channel RF_SHUTDO Energy When intelligent

frequency intelligent WN_SW Conservation carrier shutdown
TDD shutdown option of the and Emission takes effect:
NRDUCellAl Reduction ● If the local cell
goSwitch.Po is a capacity-
werSavingS layer cell, RF
witch channel
parameter intelligent
shutdown
cannot take
effect in the
scenarios listed
in Table 4-12.
● If the local cell
is a basic-layer
cell and RF
channel
intelligent
shutdown
takes effect in
the scenarios
listed in Table
4-12, the
related
capacity-layer
cells may exit
the intelligent
carrier
shutdown
state.
Low- Super uplink FLEX_SUPER Super Uplink After an NR FDD

frequency with SUL and _UPLINK_S carrier is shut
TDD NR FDD co- W option of down, SUL
deployment the scheduling cannot
NRDUCellAl be performed for
goSwitch.Su super uplink UEs.
perUplinkS
witch
parameter

5G RAN

Name Switch
FDD Antenna port STR MIMO If carrier

detection ANTENNAP shutdown takes
ORTOPTDET effect before
antenna port
detection is
completed, the
detection results
will show that the
detection fails.
Low- Low latency HIGH_RELIA URLLC After intelligent

frequency and high BILITY_BASI carrier shutdown
TDD reliability C_SW option is enabled, a cell
of the enters the carrier
NRDUCellAl shutdown state,
goSwitch.Hi which may cause
ghReliability UEs performing
Switch high-reliability
parameter services to
experience
network
disconnections.
5.1.3 Requirements
5.1.3.1 Licenses
For 3900 and 5900 series base stations, the license requirements are as follows.
FOFD-050203 Intelligent Carrier NR0S00ICSC00 per Cell

Shutdown
For DBS3900 and DBS5900 LampSite base stations, the license requirements are as
follows.
FOFD-050203 Intelligent Carrier NR0SSHUTDW00 per Carrier per

Shutdown pRRU

5G RAN
5.1.3.2 Software
None

Name
FDD Timing TIMING_CARRIER Energy The periods

Low- carrier _SHUTDOWN_S Conservation configured for
frequency shutdown W option of the and Emission intelligent carrier
TDD NRDUCellAlgoSw Reduction shutdown cannot
itch.PowerSaving overlap with
Switch parameter those configured
for timing carrier
shutdown of the
same cell. You are
advised to
preferentially plan
the periods during
which timing
carrier shutdown
takes effect.
5.1.3.3 Hardware
Base Station Models

with the BBU3910.
Boards
RF Modules
All NR-capable RF modules that work in low frequency bands support this

5G RAN
5.1.3.4 Others
None


Name

Power NRDUCellAlgoSwitch.PowerSa ● In multi-carrier intra-base-

Saving vingSwitch station scenarios, select the
Switch INTRA_GNB_MULTI_CARR_S
D_SW option of this
parameter for capacity-layer
cells.
● In multi-carrier inter-base-
station scenarios, select the
INTER_GNB_MULTI_CARR_S
D_SW option of this
parameter for capacity-layer
cells.

Policy
Index

requirements:
● Within the same policy of an
time and start time must be
longer than 20 minutes.

5G RAN

Name
Stop Time NRDUCellPowerSav- stop time refers to the next

ing.StopTime day. For example:
to be configured after policy
A of this function has been
policy A.
Power NRDUCellPowerSav- ● In multi-carrier intra-base-

Saving ing.PowerSavingType station scenarios, set this
Type parameter to
INTRA_GNB_MULTI_CARR_S
D for capacity-layer cells.
● In multi-carrier inter-base-
station scenarios, set this
parameter to
INTER_GNB_MULTI_CARR_S
D for capacity-layer cells.

PRB ing.DlPrbThld parameter to its recommended
Threshold value.

PRB Offset ing.DlPrbOffset parameter to its recommended
value.
UE NRDUCellPowerSav- You are advised to set this

Number ing.UserNumThld parameter to its recommended
Threshold value.
Shutdown NRDUCellPowerSav- You are advised to set this

Trigger ing.ShutdownTrigJudgePeriod parameter to its recommended
Judge value.
Period

5G RAN

Name
Power NRCellRelation.PowerSavingC This parameter indicates the

Saving Cell ellFlag flag of intelligent carrier
Flag shutdown for a neighboring cell.
Set this parameter based on the
network plan.
No NRCellRelation.NoRmvFlag When automatic removal of

Removal neighboring cells in ANR is
Flag enabled (with the
NR_NR_ANR_DEL_SW option of
the
NRCellAlgoSwitch.AnrSwitch
parameter selected), it is
recommended that the
NRCellRelation.NoRmvFlag
parameter be set to
FORBID_ANR_RMV for the
bidirectional neighbor
relationships between capacity-
layer and basic-layer cells.
NOTE
parameter must be set to CELL_TDD or CELL_FDD. This function cannot be configured for a
cell with this parameter set to CELL_SUL.

network scenario.

● Multi-carrier intra-base-station scenario
Assume that a cell with NrCellId 0 is a capacity-layer cell and another cell
with NrCellId 10 is a basic-layer cell in a multi-carrier intra-base-station
scenario. The PowerSavingCellFlag parameters in both NRCellRelation MOs
for the bidirectional neighbor relationships between capacity-layer and basic-
layer cells need to be set for intelligent carrier shutdown. For details about
configuring intra-base-station neighboring cells, see Mobility Management.
//Enabling intelligent carrier shutdown
PowerSavingSwitch=INTRA_GNB_MULTI_CARR_SD_SW-1;
//Setting an energy saving policy of intelligent carrier shutdown
ADD NRDUCELLPOWERSAVING: NrDuCellId=0, PowerSavingPolicyIndex=0,
PowerSavingType=INTRA_GNB_MULTI_CARR_SD, StartTime=00&00&00, StopTime=06&00&00,
DlPrbThld=25, DlPrbOffset=25, UserNumThld=20, ShutdownTrigJudgePeriod=1;
//(Optional) Setting another energy saving policy of intelligent carrier shutdown

5G RAN

PowerSavingType=INTRA_GNB_MULTI_CARR_SD, StartTime=12&00&00, StopTime=14&00&00,
//Setting Power Saving Cell Flag on the local base station, and (recommended) setting No Removal
Flag to FORBID_ANR_RMV for the bidirectional neighbor relationships between capacity-layer and
basic-layer cells when automatic removal of neighboring cells in ANR takes effect
MOD NRCELLRELATION: NrCellId=0, Mcc="302", Mnc="220", gNBId=0, CellId=10,
PowerSavingCellFlag=COVERAGE, NoRmvFlag=FORBID_ANR_RMV;
PowerSavingCellFlag=CAPACITY, NoRmvFlag=FORBID_ANR_RMV;
● Multi-carrier inter-base-station scenario

Assume that, in a multi-carrier inter-base-station scenario, a cell with NrCellId
1 is a capacity-layer cell served by a base station with gNBId 0 and another
cell with NrCellId 11 is a basic-layer cell served by a base station with gNBId
1. The PowerSavingCellFlag parameters in both NRCellRelation MOs for the
bidirectional neighbor relationships between capacity-layer and basic-layer
cells need to be set for intelligent carrier shutdown. For details about
configuring inter-base-station neighboring cells, see Mobility Management.
//Enabling intelligent carrier shutdown
PowerSavingSwitch=INTER_GNB_MULTI_CARR_SD_SW-1;
//Setting an energy saving policy of intelligent carrier shutdown
PowerSavingType=INTER_GNB_MULTI_CARR_SD, StartTime=00&00&00, StopTime=06&00&00,
//(Optional) Setting another energy saving policy of intelligent carrier shutdown
PowerSavingType=INTER_GNB_MULTI_CARR_SD, StartTime=12&00&00, StopTime=14&00&00,
//Setting Power Saving Cell Flag on the local base station, and (recommended) setting No Removal
Flag to FORBID_ANR_RMV for the neighbor relationships with the basic-layer cell when automatic
removal of neighboring cells in ANR takes effect
PowerSavingCellFlag=COVERAGE, NoRmvFlag=FORBID_ANR_RMV;
//Setting Power Saving Cell Flag on the peer base station, and (recommended) setting No Removal
Flag to FORBID_ANR_RMV for the neighbor relationships with the capacity-layer cell when automatic
removal of neighboring cells in ANR takes effect
PowerSavingCellFlag=CAPACITY, NoRmvFlag=FORBID_ANR_RMV;

N/A

● Multi-carrier intra-base-station scenario
//Disabling intelligent carrier shutdown
PowerSavingSwitch=INTRA_GNB_MULTI_CARR_SD_SW-0;
//Removing an energy saving policy of intelligent carrier shutdown
//(Optional) Removing the other energy saving policy of intelligent carrier shutdown
● Multi-carrier inter-base-station scenario

//Disabling intelligent carrier shutdown
PowerSavingSwitch=INTER_GNB_MULTI_CARR_SD_SW-0;
//Removing an energy saving policy of intelligent carrier shutdown
//(Optional) Removing the other energy saving policy of intelligent carrier shutdown

5G RAN


As activation verification for intelligent carrier shutdown in multi-carrier intra-
base-station scenarios is similar to that in multi-carrier inter-base-station
scenarios, the following uses the activation in the former scenarios as an example,
which can be verified using either of the following methods:
● Method 1:
Power Saving Switch parameter is Intra-gNodeB Multi-Carrier
Shutdown Sw:On in the command output, intelligent carrier shutdown
has been enabled.
least one record with Power Saving Type being Intra-gNodeB Multi-
Carrier Shutdown.
NOTE
If there are two or more records with Power Saving Type being Intra-gNodeB
Multi-Carrier Shutdown, intelligent carrier shutdown has been enabled in two
or more time periods.
c. Run the DSP TIME command. Check whether the system time is within
the periods for this function to take effect.
▪ If it is not, wait until the start time arrives.

d. Wait for a period equal to
NRDUCellPowerSaving.ShutdownTrigJudgePeriod plus 3 (in the unit of
minutes) and then run the DSP NRDUCELL command. If the value of the
Power Saving State parameter is Intra-gNodeB Multi-Carrier
Shutdown:Enabled in the command output, this function has taken
effect.
● Method 2:
intelligent carrier shutdown and the reason why it does not take effect.
– If the value of Power Saving Type is Intra-gNodeB Multi-Carrier
Shutdown and the value of Current State is Enabled, intelligent carrier
shutdown has taken effect.
– If the value of Power Saving Type is Intra-gNodeB Multi-Carrier
Shutdown and the value of Current State is Disabled, check the
Current Disabled Cause parameter value to determine the reason why
intelligent carrier shutdown does not take effect. Table 5-4 lists possible
reasons. As the displayed value of the Current Disabled Cause
parameter is updated every minute, the value displayed in the command
output may be the result less than 1 minute ago.

5G RAN
Table 5-4 Possible reasons why intelligent carrier shutdown does not take
effect
Reason Description
Insufficient License No license for this function is available.
Neighboring Cell Not ● No inter-frequency neighboring cells

Configured are configured for the current serving
cell.
● Inter-frequency neighboring cells are
configured for the current serving
cell, but there is no neighboring cell
for which Power Saving Cell Flag is
set to COVERAGE.
Cell Unavailable The cell is blocked or deactivated, fails

to be set up, or is unavailable due to
other reasons.
Triggering Time Not The current time is not within the range
Reached specified for intelligent carrier shutdown.
Neighboring Cell ● A neighboring cell for which Power

Unavailable Saving Cell Flag is set to COVERAGE
is unavailable.
● A neighboring cell for which Power
Saving Cell Flag is set to COVERAGE
is a hyper cell or combined cell, and
some TRPs of this cell are
unavailable.
Xn Interface Unavailable The Xn interface is in the abnormal state

in multi-carrier inter-base-station
scenarios.
Impacted Feature Taken None

Effect
Downlink PRB Threshold None

Not Reached
UE Number Threshold Not None

Reached
UE Transfer or Transfer ● The current serving cell meets the

Failure load conditions for carrier shutdown,
and UEs are being transferred.
● The current serving cell meets the
load conditions for carrier shutdown,
but some UEs fail to be transferred
from the cell.

5G RAN
Reason Description
Triggering Decision Period The current time is within the periods

Not Met specified for intelligent carrier shutdown
to take effect and is not within the first
detection period (lasting 1 minute).
However, it is within the determination
period for triggering intelligent carrier
shutdown (specified by the
NRDUCellPowerSav-
ing.ShutdownTrigJudgePeriod
parameter).
In Penalty State The cell is in the penalty state after it

exits the intelligent carrier shutdown
state or UEs fail to be transferred out of
the cell. The penalty lasts 30 minutes.
RF Hardware Capability Not None

Supported
Others ● The current time is within the periods

specified for intelligent carrier
shutdown to take effect as well as
the first detection period (lasting 1
minute).
● Internal software or other reasons
cause the function to fail.

obtained before and after intelligent carrier shutdown is enabled can be
● The duration of cell unavailability due to intelligent carrier shutdown can be
obtained using the N.Cell.Unavail.Dur.EnergySaving counter on the MAE-
Access.

5G RAN
Feature Parameter Description 6 Site Level Energy Saving
6 Site Level Energy Saving
6.1 Low Power Consumption Mode
6.1.1 Principles
In the scenario where both a power supply system and batteries are configured,
the available duration of backup power for basic coverage services will be
impacted if the power supply system becomes faulty while the deployed batteries
are insufficient. Low power consumption mode can be used to prolong the
duration of basic coverage service provisioning in this scenario. When an alarm
indicating power supply insufficiency or failures is reported, cells with high power
consumption enter low power consumption mode to reduce the power consumed
by RF modules.
Methods of Connecting a Power Supply System to a Huawei Base Station

The power supply system can be provided by Huawei or another vendor.
● The Huawei power supply system can be connected to a Huawei base station
through the two RS485 signal input ports on the universal power and
environment interface unit (UPEU) or universal environment interface unit
(UEIU). They can also be connected through the RS485 signal input port or
the power cable on the RRU.
● A non-Huawei power supply system can be connected to a Huawei base
station through the Boolean signal input ports on the UPEU, UEIU, or RRU.
That is, they are connected through a dry contact port.
In this case, you need to configure the ALMPORT MO to set information
about the dry contact port and configure the MAINSALARMBIND MO to
define the alarms generated by this port as mains supply failure alarms.
Under this setting, a mains supply failure alarm will be reported to the
Huawei base station through the port if the non-Huawei power supply system
experiences a mains supply failure. Upon detection of this alarm, the Huawei
base station can start low power consumption mode to prolong the duration
of basic coverage service provisioning.

5G RAN
NOTE
The name and severity of the alarms reported by the dry contact port can be
customized by running the SET ENVALMPARA command.
Parameters Used for Low Power Consumption Mode Activation

Low power consumption mode can be enabled by selecting the
LOW_PWR_MODE_SW option of the NRDUCellAlgoSwitch.PowerSavingSwitch
parameter.
The energy saving type, backup power saving policy, and other information under
an energy saving policy are specified by the parameters in the
energy saving type indicated by an energy saving policy index. Low power
consumption mode requires that this parameter be set to LOW_PWR_MODE,
meaning that under the corresponding energy saving policy, the local cell will
enter low power consumption mode based on the backup power saving
policy.
● The NRDUCellPowerSaving.BackupPwrSavingPolicy parameter specifies the
backup power saving policy of the cell.
– If this parameter is set to PRECISE_BACKUP_POLICY1, the carrier of the
cell is shut down when the mains supply fails for a period longer than the
transitional period (the base station works properly in this transitional
period after entering low power consumption mode).
– If this parameter is set to PRECISE_BACKUP_POLICY2, symbol power
saving is performed for the cell when the mains supply fails for a period
longer than the transitional period.
– If this parameter is set to PRECISE_BACKUP_POLICY3, the operations
performed for the cell vary with the power supply system and the
batteries used when the mains supply fails for a period longer than the
transitional period:
▪ If the Huawei power supply system is used in conjunction with

Huawei lithium batteries, symbol power saving is first performed for
the cell. When the battery power (which equals the remaining
battery capacity multiplied by the battery efficiency) drops below
60%, carrier shutdown is then performed for the cell.
▪ If the Huawei power supply system is used in conjunction with non-

Huawei lithium batteries, or a non-Huawei power supply system is
used (regardless of whether the lithium batteries are provided by
Huawei), symbol power saving is performed for the cell.
NOTE
UEs need to be transferred before carrier shutdown. For details, see 4.3.2 Energy
Saving Procedure of Timing Carrier Shutdown.

5G RAN
Application Scenarios of Low Power Consumption Mode

The low power consumption mode can be used in centralized and distributed
power supply scenarios.
● A centralized power supply scenario is when main base station components
(including the BBU and AAUs/RRUs) use the same power supply system and
backup power supply system. If the mains supply fails, the same backup
power supply system provides power for all main components, and the same
power alarms are reported if any. Figure 6-1 illustrates the centralized power
supply scenario.
In this scenario, all cells enabled with this function will enter low power
consumption mode if the mains supply fails for a period longer than the
transitional period.
Figure 6-1 Centralized power supply scenario
● A distributed power supply scenario is when main base station components

(including the BBU and AAUs/RRUs) use multiple power supply systems and
backup power supply systems. If the mains supply of a power supply system
fails, the corresponding backup power supply system provides power for the
related main components, but the power supply systems of other components
remain unchanged, and different power alarms may be reported for different
components. Figure 6-2 illustrates the distributed power supply scenario.
In this scenario, only cells that are enabled with this function and served by
AAUs/RRUs experiencing power supply failures will enter low power
consumption mode if the mains supply fails for a period longer than the
transitional period.
NOTE
In the distributed power supply scenario, multiple dry contact ports may report alarms
indicating mains supply failures that occur in non-Huawei power supply systems. If
this is the case, the same alarm ID (specified by the ALMPORT.AID parameter) must
be set for all these dry contact ports.

5G RAN
Figure 6-2 Distributed power supply scenario
To ensure that only cells served by AAUs/RRUs experiencing power supply

failures enter low power consumption mode in the distributed power supply
scenario, power supply group IDs must be correctly configured for AAUs/RRUs
before low power consumption mode is enabled. A power supply group ID
identifies a group of AAUs/RRUs (a single AAU/RRU may exist in the group)
using the same power supply system, and is specified by the RRU.PSGID
parameter. When configuring this parameter, comply with the following
principles:
– One power supply group ID is configured for AAUs/RRUs using the same
power supply system, whereas different power supply group IDs are
configured for AAUs/RRUs using different power supply systems.
– The power supply group ID of the AAUs/RRUs using the same power
supply system as the BBU is 0.
As shown in Figure 6-2, the power supply group ID of the RRUs in subracks
60, 61, and 62 must be set to 0, and that of the RRUs in subracks 63, 64, and
65 can be set to 1.
If the mains supply fails for a period longer than the transitional period for
the power supply system whose monitoring is managed by the BBU, the NR
cells that are enabled with low power consumption mode and served by
AAUs/RRUs with the RRU.PSGID parameter set to 0 will enter the low power
consumption mode.
If the mains supply fails for a period longer than the transitional period for
the power supply system whose monitoring is managed by an AAU/RRU, the
NR cells that are enabled with low power consumption mode and served by
the AAU/RRU or AAUs/RRUs having the same RRU.PSGID setting as the
preceding AAU/RRU will enter the low power consumption mode.

5G RAN
NOTICE
● If a BBU monitors multiple power supplies that use different AC input

sources or are controlled by separate circuit breakers, the mains input
exception status of these power supplies may be inconsistent if the mains
supply is abnormal. If the inconsistency lasts for more than 5 minutes, low
power consumption mode cannot work properly.
● If the mains supply is abnormal, the base station reports ALM-25622 Mains
Input Out of Range. In this case, rectify the fault onsite as soon as possible
(for example, by restoring the mains supply or resetting the circuit
breaker).
● If the RRU.PSGID parameter value is inconsistent with actual power supply
relationships, AAUs/RRUs with normal power supplies may enter low
power consumption mode when this function is triggered. As a result, the
cells served by these AAUs/RRUs may experience capability degradation or
become unavailable due to shutdown.
6.1.2.1 Benefits
Low power consumption mode prolongs the backup power use duration of basic
services when the mains supply fails. In LTE and NR co-RF module scenarios, it is
recommended that this function be enabled for both LTE and NR cells and the
same backup power saving policy be configured for these cells.
Energy saving gains may decrease when the temperature differential of RF
modules is excessively large. This is to prevent energy saving–triggered shutdown
from affecting the lifespan of RF modules.
6.1.2.2 Impacts
Network Impacts
If the backup power saving policy configured by the operator includes carrier
shutdown, the following will occur after low power consumption mode takes
effect:
● Existing UEs in the cells whose carriers are shut down cannot perform
services, slightly increasing the service drop rate.
● New UEs within the coverage of the cells whose carriers are shut down
cannot access the network.
● During NR carrier shutdown, new UEs are prohibited from accessing an NR
cell. If UEs attempt to be handed over to the NR cell, the values of the
counters related to handover preparation failures (such as
N.HO.IntraFreq.FailOut.PrepFailure) slightly increase.
The exact time when carrier shutdown actually starts taking effect may not be
synchronized with that when related performance counters are reported.
Consequently, if carrier shutdown starts taking effect in a measurement period,

5G RAN
there will be a measurement error of less than 5 minutes between the reported
results and the actual results for the shut-down cell in the measurement period.
Before carrier shutdown takes effect, the gNodeB transfers SA UEs to NR or LTE
cells through blind redirections. This impacts related counters described in Table
6-1.
Table 6-1 Impacts on counters related to blind redirections

T
NR N.RRCRedirection.Blind The value of this counter may increase

when SA UEs are transferred to NR cells
NR N.RRCRedirection.N2E.Blin The value of this counter may increase

d when SA UEs are transferred to LTE cells
NR N.RRCRedirection.N2E.Blin The value of this counter may increase

d.PowerSaving when SA UEs are transferred to LTE cells
through blind redirections for energy saving
purposes.

5G RAN
Function Impacts
Name

Switch parameter carrier, symbol
power saving
in low power
consumption
mode does not
take effect.
● If the RF
module is
serving other
NR carriers, the
status of
symbol power
saving in low
power
consumption
mode for these
carriers is not
affected.

5G RAN

Name

serving any
other NR
carrier, symbol
power saving
in low power
consumption
mode does not
take effect.
● If the RF
module is
serving other
NR carriers, the
status of
symbol power
saving in low
power
consumption
mode for these
carriers is not
affected.
Low- RF RRU.DORMANCY RF Module Low power

frequency module SW (LTE eNodeB, Deep consumption
TDD deep 5G gNodeB) Dormancy mode does not
dormancy take effect when
RF module deep
dormancy is in
effect.
Low- Low HIGH_RELIABILIT URLLC After low power

frequency latency Y_BASIC_SW consumption
TDD and high option of the mode is enabled,
reliability NRDUCellAlgoSw this power-saving
itch.HighReliabili feature is
tySwitch activated for cells
parameter based on actual
conditions,
affecting the
performance of
UEs performing
high-reliability
services.

5G RAN
6.1.3 Requirements
6.1.3.1 Licenses

Saving
6.1.3.2 Software
Low power consumption mode depends on the function listed in Table 6-2 when
the NRDUCellPowerSaving.BackupPwrSavingPolicy parameter is set to
PRECISE_BACKUP_POLICY2 or PRECISE_BACKUP_POLICY3 and the multimode RF
module serving the NR cell serves both LTE and NR carriers. In other scenarios,
low power consumption mode does not depend on other functions.
Table 6-2 Prerequisite functions of low power consumption mode

RAT Function Name Function Switch Reference
FDD Multi-RAT LTE: Multi-RAT

Low- coordinated SymbolPwrSaving.M Coordinated Symbol
frequency symbol power ultiRatSymbolShut- Power Saving
TDD saving downSw
NR:
MULTI_RAT_SYMBOL
_SHUTDOWN_SW
option of the
NRDUCellAlgoSwitch
.PowerSavingSwitch
parameter

None

5G RAN
6.1.3.3 Hardware
Base Station Models

with the BBU3910.
Boards
RF Modules
All NR-capable AAUs/RRUs that work in low frequency bands support this
6.1.3.4 Others
● When low power consumption mode is used with the Huawei power supply
system and Huawei lithium batteries, a power monitoring unit (PMU) must
be configured on the base station. Table 6-3 lists the requirements for the
PMU.
Table 6-3 PMU requirements of low power consumption mode

Power PMU Model PMU Software Version
Supply
System Type
ETP APM5930 If the hardware version is PMU.19, the PMU

(CCUC) software version must be 219 or later.
If the hardware version is PMU.22, the PMU
software version must be 213 or later.
OPM200 The PMU software version must be 177 or

later.

5G RAN
NOTE
● Low power consumption mode can be used for a base station only when Battery
Type is Li-Ion Battery and Number Of Lithium Batteries is at least 1 in the
command output of DSP BATTERY. For details about the power supply
configurations, lithium battery configurations, and mapping between power
supplies and lithium batteries, see Power Supply Management.
● You can query the software version of the PMU by selecting the corresponding
gNodeB in the MML command window of the MAE-Access and running the DSP
BRDVER command.
● If the software version meets the requirements listed in Table 6-3, software
activation is not required.
● If the software version does not meet the requirements listed in Table 6-3,
run the ACT SOFTWARE command to activate the software.
● If communication between the lithium batteries and the PMU is faulty, low power
consumption mode cannot run properly. In this case, the base station maintains
the current energy saving status in low power consumption mode until
communication recovers.
● When low power consumption mode is used with the Huawei power supply
system and non-Huawei lithium batteries, a PMU must be configured on the
base station. However, there are no requirements for the PMU.
● When low power consumption mode is used with a non-Huawei power supply
system (regardless of whether the lithium batteries are provided by Huawei),
the non-Huawei power supply system must support connection through a dry
contact port. In addition, this system must send the change of at least one
analog value (external environment with continuous change features) or
Boolean value (external environment with switch and discrete features) to the
dry contact port when the mains supply fails.

Table 6-4 and Table 6-5 describe the parameters used for function activation and
optimization, respectively. This section does not describe parameters related to cell
establishment.

5G RAN

Name
Power RRU.PSGID One power supply group ID is

Supply configured for AAUs/RRUs using
Group ID the same power supply system,
whereas different power supply
group IDs are configured for
AAUs/RRUs using different
power supply systems.
The power supply group ID of
the AAUs/RRUs using the same
power supply system as the BBU
is 0.

Power NRDUCellAlgoSwitch.PowerSa Select the

Saving vingSwitch LOW_PWR_MODE_SW option
Switch of this parameter.

Policy
Index

Saving ing.PowerSavingType LOW_PWR_MODE.
Type

5G RAN

Name
Backup NRDUCellPowerSav- If a multimode base station

Power ing.BackupPwrSavingPolicy uses the same set of storage
Saving batteries to support the services
Policy of all RATs:
● The value
PRECISE_BACKUP_POLICY1
is recommended if the
services of the local cell
require a low priority and the
rated power of this cell needs
to be decreased to save
power for cells of other RATs
in the case of mains supply
failures.
● The value
require a high priority in the
case of mains supply failures.
● The value
require a medium priority in
the case of mains supply
failures.
Switch ALMPORT.SW Set this parameter to ON if a

non-Huawei power supply
system is connected to the base
station through a dry contact
port.
Cabinet ALMPORT.CN Set this parameter based on the

No. network plan.
Subrack ALMPORT.SRN Set this parameter based on the

No. network plan.
Slot No. ALMPORT.SN Set this parameter based on the

network plan.
Port No. ALMPORT.PN Set this parameter based on the

network plan.
Alarm ID ALMPORT.AID Set this parameter based on the

network plan.

5G RAN

Name
Port Type ALMPORT.PT Set this parameter based on the

analog or Boolean value output
by the non-Huawei power
supply system when the mains
supply fails.
Alarm ALMPORT.AVOL Set this parameter based on the

Voltage Boolean value output by the
non-Huawei power supply
system when the mains supply
fails.
Base MAINSALARMBIND.ISDSWITC Set this parameter to ENABLE if

Station H the alarms generated by the dry
Almport contact port are defined as
Switch mains supply failure alarms.
Almport MAINSALARMBIND.NMSACN Set this parameter based on the

Cabinet network plan.
No.
Almport MAINSALARMBIND.NMSASRN Set this parameter based on the

Subrack network plan.
No.
Almport MAINSALARMBIND.NMSASN Set this parameter based on the

Slot No. network plan.
Almport MAINSALARMBIND.NMSAPN Set this parameter based on the

Port No. network plan.
NOTE
The parameters in the ALMPORT MO must be set based on the analog or Boolean value
output by the non-Huawei power supply system when the mains supply fails.
Table 6-5 Parameters used for optimization

Name
Alarm ID ALMCURCFG.ALMID Set this parameter based on the

network plan.
Alarm ALMCURCFG.ANM Set this parameter based on the

Name network plan.
Alarm ALMCURCFG.ALVL Set this parameter based on the

Level network plan.

5G RAN

and dependency relationships between the functions, as well as the actual
network scenario.

//(Optional) Running the SET ALMPORT command to turn on the port switch and configure the
information about the dry contact port and running the MOD NMSABIND command to define the alarms
generated by the dry contact port as mains supply failure alarms, if low power consumption mode is used
with a non-Huawei power supply system
SET ALMPORT: CN=0, SRN=0, SN=19, PN=0, SW=ON, AID=65033, PT=BOOL, AVOL=LOW;
MOD NMSABIND: ISDSWITCH=ENABLE, NMSACN=0, NMSASRN=0, NMSASN=19, NMSAPN=0;
//(Optional, required in distributed power supply scenarios) Setting a power supply group ID
MOD RRU: CN=0,SRN=60,SN=0,PSGID=0;
//Enabling low power consumption mode
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=LOW_PWR_MODE_SW-1;
//Setting an energy saving policy of low power consumption mode
PowerSavingType=LOW_PWR_MODE, BackupPwrSavingPolicy=PRECISE_BACKUP_POLICY1;

//(Optional) Customizing the name, severity, and other information of the alarms reported by the dry
contact port, if low power consumption mode is used with a non-Huawei power supply system
SET ENVALMPARA: ALMID=65033, ANM="Non-Huawei power supply system mains fault", ALVL=MAJOR,
ASS=HARDWARE;

//(Optional) Running the SET ALMPORT command to turn off the port switch and running the MOD
NMSABIND command to set ISDSWITCH to DISABLE, if low power consumption mode does not need to be
used with a non-Huawei power supply system
SET ALMPORT: CN=0, SRN=0, SN=19, PN=0, SW=OFF;
MOD NMSABIND: ISDSWITCH=DISABLE;
//Disabling low power consumption mode
MOD NRDUCELLALGOSWITCH: NrDuCellId=0, PowerSavingSwitch=LOW_PWR_MODE_SW-0;
//Removing the energy saving policy of low power consumption mode
6.1.4.2 Using the MAE-Deployment


After the low power consumption mode function is activated, use either of the
following methods to check whether the function has taken effect:
● Method 1:
When low power consumption mode is used with the Huawei power supply
system:
Power Saving Switch parameter is Low Power Consumption Mode
Switch:On in the command output, low power consumption mode has
been enabled.

5G RAN

least one record with Power Saving Type being Low Power
Consumption Mode.
c. After a mains supply failure occurs, wait 5 minutes and then run the DSP
NRDUCELL command. Verify that the value of the Power Saving State
parameter is Low Power Consumption Mode:Enabled, which indicates
that low power consumption mode has taken effect.
When low power consumption mode is used with a non-Huawei power supply
system:
a. Run the LST ALMPORT command. Verify that the parameter settings in
the ALMPORT MO are consistent with the analog or Boolean value
output by the non-Huawei power supply system when the mains supply
fails.
b. Run the LST NMSABIND command. Verify that the value of the Base
Station Almport Switch parameter is ENABLE.
c. Run the LST NRDUCELLALGOSWITCH command. Verify that the value of
the Power Saving Switch parameter is Low Power Consumption Mode
Switch:On in the command output.
d. Run the LST NRDUCELLPOWERSAVING command. Verify that there is at
least one record with Power Saving Type being Low Power
Consumption Mode.
e. After a mains supply failure occurs, wait 5 minutes and then run the DSP
NRDUCELL command. Verify that the value of the Power Saving State
parameter is Low Power Consumption Mode:Enabled, which indicates
that low power consumption mode has taken effect.
● Method 2:
Run the DSP NRDUCELLPOWERSAVING command to query the status of low
power consumption mode.
– If the value of Power Saving Type is Low Power Consumption Mode
and the value of Current State is Symbol Power Saving Enabled in LPC
Mode or Carrier Shutdown Enabled in LPC Mode, low power
consumption mode has taken effect.
and the value of Current State is Symbol Power Saving Disabled in LPC
Mode or Carrier Shutdown Disabled in LPC Mode, then the cell should
have entered low power consumption mode with symbol power saving or
carrier shutdown performed, but for some reason has not. You can check
the Current Disabled Cause parameter value to determine the reason
why low power consumption mode does not take effect. Table 6-6 lists
possible reasons.
and the value of Current State is Disabled, check the Current Disabled
Cause parameter value to determine the reason why low power
consumption mode does not take effect. Table 6-6 lists possible reasons.

5G RAN
Table 6-6 Possible reasons why low power consumption mode does not
take effect
Reason Description

available.

Normal Power or in Transitional ● If low power consumption

Period mode is used with the Huawei
power supply system, the mains
supply is normal or a
transitional period is ongoing.
● If low power consumption
mode is used with a non-
Huawei power supply system,
the mains supply is normal, a
transitional period is ongoing,
or the MOD NMSABIND
command has not been
executed to define the alarms
generated by the dry contact
port as mains supply failure
alarms.
Others ● A multimode RF module serves

both LTE and NR carriers, and
multi-RAT coordinated symbol
power saving is not enabled for
the LTE and NR cells.
● Intelligent carrier shutdown or
timing carrier shutdown takes
effect for a carrier, and the RF
module does not serve any
other NR carrier.
fail.

Energy consumption data for base stations can be obtained by using the counter
VS.EnergyCons.BTS.Adding.NR (for a base station) or VS.EnergyCons.BTSBoard
(for RF modules) on the MAE-Access.
In the case of a mains supply failure on the live network, the base station energy
consumption data obtained before and after low power consumption mode is

5G RAN
enabled can be compared to assess the backup power usage extension provided
by this function.
6.2 Baseband Chip Shutdown
6.2.1 Principles
Baseband processing resource blocks are deployed on the BBP in CPRI networking
and on the BBP and AAU in eCPRI networking, as shown in Figure 6-3.
Figure 6-3 Baseband processing resource block deployment
Carrier shutdown functions (including timing carrier shutdown, intelligent carrier

shutdown, and LTE and NR intelligent carrier shutdown) can only shut down the
carriers of RF modules to save energy. There is energy waste if baseband
processing resource blocks continue to work when they are not serving any other
activated cells except the cells in the carrier shutdown state, other activated cells
on these baseband processing resource blocks are manually deactivated, or no
cells are deployed on these baseband processing resource blocks. Baseband chip
shutdown enables a baseband processing resource block to enter the low power
consumption mode to save energy when no cells are activated on the baseband
processing resource block. A BBP or an AAU may have one or more baseband
processing resource blocks. There are energy saving gains as long as one of the
baseband processing resource blocks is idle.
This function can be enabled by selecting the

BB_SHUTDOWN_POWERSAVING_SW option of the
gNodeBParam.BaseStationDeepDormancySw parameter. With this function
enabled, baseband processing resource blocks are dynamically shut down to
reduce energy consumption in any of the following scenarios:
● Assume that there are activated cells on the baseband processing resource
blocks and the baseband chip shutdown switch is turned on. The baseband
processing resource blocks (on the BBP in CPRI networking and on both the
BBP and AAU in eCPRI networking) enter the shutdown state 10 minutes after
all activated cells are deactivated, either manually or because of entering the
carrier shutdown state. Baseband processing resource blocks cannot be shut
down when they still serve activated cells.

5G RAN
NOTE
If other carrier shutdown functions are enabled after the baseband chip shutdown
function takes effect, the base station does not update the effective status of these
carrier shutdown functions because cell resources have been released. That is, the
values of Current State corresponding to these carrier shutdown functions are
Disabled in the command output of DSP NRDUCELLPOWERSAVING.
● Assume that there are no activated cells on the baseband processing resource
blocks. The baseband processing resource blocks (on the BBP in CPRI
networking and on both the BBP and AAU in eCPRI networking) enter the
shutdown state 10 minutes after the baseband chip shutdown switch is
turned on.
After the baseband processing resource blocks enter the shutdown state, they
dynamically exit this state if a cell they serve is re-activated.
6.2.2.1 Benefits
Baseband chip shutdown reduces energy consumption in any of the following
scenarios. The energy saving gains depend on the shutdown duration and board
type of baseband processing resource blocks. The number of baseband processing
resource blocks may vary with the board type, and the energy saving gains after
each baseband processing resource block is shut down may also be different.
● All the activated cells on the baseband processing resource blocks are
deactivated, either manually or because of entering the carrier shutdown
state.
● There are no activated cells on the baseband processing resource blocks.
To prevent energy saving–triggered shutdown from affecting the lifespan of RF
modules and prevent possible hardware faults caused by an excessively large
temperature differential, baseband chips on the AAU may not enter the shutdown
state or may exit the shutdown state when the temperature differential of RF
modules is excessively large. Energy saving gains may decrease in this case.
To ensure AAU reliability, if the baseband chips on an AAU are shut down
repeatedly at an interval less than 30 minutes, the energy saving gains will
decrease.
6.2.2.2 Impacts
Network Impacts
If the baseband chip shutdown switch is turned off when baseband chip shutdown
is in effect, the baseband processing resource blocks exit the shutdown state and
automatically restart. The startup duration is generally 2 minutes and does not
exceed 5 minutes.

5G RAN
Function Impacts
Name
Low- Hyper NRDUCell.NrDuC Hyper Cell Baseband

frequency Cell ellNetworkingM (Low- processing
TDD ode set to Frequency resource blocks
HYPER_CELL TDD) serving the TRPs
of a hyper cell
cannot be shut
down.
FDD Cell NRDUCell.NrDuC Cell Baseband

Low- Combinat ellNetworkingM Combination processing
frequency ion ode set to resource blocks
TDD HYPER_CELL_CO serving the TRPs
MBINE_MODE of a combined cell
cannot be shut
down.
6.2.3 Requirements
6.2.3.1 Licenses
None
6.2.3.2 Software
● Baseband chip shutdown does not depend on other functions when there are
no activated cells on the baseband processing resource blocks.
● Baseband chip shutdown depends on one of the functions listed in Table 6-7
when there are activated cells on the baseband processing resource blocks.

5G RAN
Table 6-7 Prerequisite functions of baseband chip shutdown
RAT Function Name Function Switch Reference
FDD Intelligent INTRA_GNB_MULTI Energy Conservation

Low- carrier _CARR_SD_SW or and Emission
frequency shutdown INTER_GNB_MULTI Reduction
TDD _CARR_SD_SW
option of the
NRDUCellAlgoSwit
ch.PowerSavingSwi
tch parameter
FDD Timing carrier TIMING_CARRIER_ Energy Conservation
Low- shutdown SHUTDOWN_SW and Emission
frequency option of the Reduction
TDD NRDUCellAlgoSwit
ch.PowerSavingSwi
tch parameter
FDD LTE and NR LNR_SMART_CARRI LTE and NR
Low- intelligent ER_SHUTDOWN_S Intelligent Carrier
frequency carrier W option of the Shutdown
TDD shutdown NRDUCellAlgoSwit
ch.PowerSavingSwi
tch parameter
FDD RF module deep RRU.DORMANCYS RF Module Deep
Low- dormancy W Dormancy
frequency
TDD

None
6.2.3.3 Hardware
Base Station Models

with the BBU3910.

Boards
All NR-capable main control boards and all NR-capable baseband processing units
except the UBBPg1 support this function. To learn which main control boards and
baseband processing units are NR-capable, see the related BBU technical
specifications in 3900 & 5900 Series Base Station Product Documentation.

5G RAN
However, if a BBP works in multiple RATs, the baseband processing resource blocks
deployed with multiple RATs such as LTE TDD and NR will not be shut down.
RF Modules
For baseband chip shutdown on the BBP, all NR-capable RF modules that work in
low frequency bands support this function. For details, see the technical
Documentation.
For baseband chip shutdown on the AAU, all NR-capable AAUs that comply with
the eCPRI protocol, work in low frequency bands, and are configured with NR
carriers support this function. For details, see the technical specifications of RF
modules in 3900 & 5900 Series Base Station Product Documentation.
If an RF module works in multiple RATs, the baseband processing resource blocks

deployed with multiple RATs such as LTE TDD and NR will not be shut down.
6.2.3.4 Others
None


Name
Base gNodeBParam.BaseStationDee It is recommended that the

Station pDormancySw BB_SHUTDOWN_POWERSAVI
Deep NG_SW option of this
Dormancy parameter be selected when the
Switch baseband processing resource
blocks corresponding to the
cells in the carrier shutdown
state do not have other
activated cells.


5G RAN
and dependency relationships between the functions, as well as the actual

network scenario.
NOTE
Before enabling baseband chip shutdown, ensure that no ALM-26819 Data Configuration
Exceeding Licensed Limit is reported. If such an alarm is reported, the cell may fail to be set
up due to license insufficiency after baseband chips exit the shutdown state.

//Enabling baseband chip shutdown
MOD GNODEBPARAM: BaseStationDeepDormancySw=BB_SHUTDOWN_POWERSAVING_SW-1;

N/A

//Disabling baseband chip shutdown
MOD GNODEBPARAM: BaseStationDeepDormancySw=BB_SHUTDOWN_POWERSAVING_SW-0;


Run the LST GNODEBPARAM command. If the value of the Base Station Deep
Dormancy Switch parameter is Baseband Shutdown Energy Saving Switch:On
in the command output, baseband chip shutdown has been activated.
NOTE
Run the DSP BRDDORMANCY command. The value of the Baseband Shutdown State
parameter depends on whether RF module deep dormancy and baseband chip shutdown
have taken effect:
● If RF module deep dormancy has taken effect, the value of the Baseband Shutdown
State parameter is Enable regardless of whether baseband chip shutdown takes effect.
● If RF module deep dormancy has not taken effect:
● If baseband chip shutdown has taken effect, the value of the Baseband Shutdown
State parameter is Enable.
● If baseband chip shutdown has not taken effect, the value of the Baseband
Shutdown State parameter is Disable.

Energy consumption data for base stations can be obtained by using the counter
VS.EnergyCons.BTS.Adding.NR (for a base station), VS.EnergyCons.BTSBoard
(for RF modules), or VS.EnergyCons.BU (for BBUs) on the MAE-Access.
obtained before and after baseband chip shutdown is enabled can be compared to
assess the energy saving gains of this function. It is expected that the base station
energy consumption decreases significantly after this function is enabled.

5G RAN
6.3 PSU Intelligent Shutdown
6.3.1 Principles
A PSU converts 110 V or 220 V alternating current (AC) power into –48 V direct
current (DC) power. Generally, an AC-powered base station is configured with
multiple PSUs. The number of PSUs required is determined based on the
maximum energy consumption of the base station. This ensures that the base
station operates properly, even when it is fully loaded.
However, a base station seldom operates at its full load. As a result, the PSUs
usually work at partial output power. The power conversion efficiency of PSUs is
directly proportional to their output power, meaning that efficiency decreases as
output power reduces, increasing the energy consumption of the base station.
The PSU intelligent shutdown function is introduced to maintain proper operation
of the base station at reduced energy consumption. Figure 6-4 shows its working
principles.
Figure 6-4 Working principles of PSU intelligent shutdown
PSU intelligent shutdown can be enabled by turning on the switch specified by the
PSUIS.PSUISS parameter. If a base station is configured with multiple PSUs for
power supply:
● When the network is lightly loaded, the base station dynamically shuts down
one or more PSUs and accommodates the network load with a minimum
number of PSUs. This enables PSUs to maintain high power conversion
efficiency, reducing the energy consumption of the base station and
prolonging the PSU lifetime.

5G RAN
● When the network load becomes heavy, the base station dynamically
activates one or more PSUs to ensure its proper operation.
6.3.2.1 Benefits
When a base station is configured with multiple PSUs for power supply and the
network load is light, PSU intelligent shutdown reduces the base station energy
consumption and prolongs the PSU lifetime.
The energy reduced by this function is closely related to the difference in the PSU
power conversion efficiency before and after this function is activated. Assuming
that the output power remains unchanged, and the PSU power conversion
efficiencies before and after the function activation are C0 and C1, respectively,
energy is reduced by (1 – C0/C1).
6.3.2.2 Impacts
Network Impacts
None
Function Impacts
None
6.3.3 Requirements
6.3.3.1 Licenses
None
6.3.3.2 Software
None

None
6.3.3.3 Hardware
Base Station Models

with the BBU3910.

5G RAN
Boards
RF Modules
This function does not depend on RF modules.
6.3.3.4 Others
● The cabinet of a base station is configured with a power monitoring unit
(PMU), at least two PSUs, and storage batteries. The storage batteries are
properly configured and are not in equalized charging mode. No battery
alarms are generated.
● The base station is AC powered. The mains supply is normal. A Huawei PMU
that supports this function is used to manage the power system. Table 6-9
describes the requirements of PSU intelligent shutdown on the PMU. For
details about how to configure the PMU, see Power Supply Management.
Table 6-9 Requirements of PSU intelligent shutdown on the PMU
Power Supply System PMU Model PMU Software Version

Type
ETP PMU 11A No requirements
PMU 11B No requirements
APM5930 (CCUC) No requirements
OPM200 (PMU 16A) No requirements
CCUB No requirements
PMU 15A Not supported
OPM50M Not supported
OPM30A Not supported
APM30 PMU 01B No requirements
PMU 11A No requirements
CCUC No requirements
EPMU01 138 or later
EPS4890 PMU 01B No requirements

5G RAN

Type
EPMU01 138 or later
EPS4815 PMU 11A No requirements
EPMU03 Not supported
EPU None Not supported
SC48200 None Not supported
NOTE
You can query the software version of the PMU by selecting the corresponding
gNodeB in the MML command window of the MAE-Access and running the DSP
BRDVER command.
For the EPMU01:
● If the software version is 138 or later, you do not need to re-activate the
software.
● If the software version is earlier than 138, run the ACT SOFTWARE command to
activate the software.


Name
Energy ENERGYCON.M Set this parameter to AC.

Consumption P
Measurement
Point
PSU Intelligent PSUIS.PSUISS It is recommended that this switch be

Shutdown turned on when a base station configured
Switch with multiple PSUs is lightly loaded.

5G RAN

//Setting the energy consumption measurement point to AC
SET ECMP: MP=AC;
//Enabling PSU intelligent shutdown
SET PSUISS: PSUISS=ENABLE;

N/A

//Disabling PSU intelligent shutdown
SET PSUISS: PSUISS=DISABLE;


● Using MML commands
a. Run the DSP BATTERY command to query the status of storage batteries.
b. Run the LST PSU command to verify that at least two PSUs are
configured.
c. Run the LST PSUISS command to verify that the value of the PSU
Intelligent Shutdown Switch parameter is Enable.
d. Run the DSP PMU command to verify that the value of the PSU
Intelligent Shutdown Switch parameter is Enable.
e. Run the DSP PSU command. If the value of the Running Status
parameter is Dormancy for a PSU, PSU intelligent shutdown has taken
effect.
Alternatively, check the PSU indicators locally to determine its working
status. If a PSU is in the shutdown state, PSU intelligent shutdown has
taken effect. For details about the indicator status, see PSU in 3900 &
5900 Series Base Station Product Documentation.
● Using performance counters
Check the PSU shutdown duration through the VS.PSU.ShutdownTime
counter on the MAE-Access to determine whether PSU intelligent shutdown
has taken effect.
– If the value of this counter is not 0, PSU intelligent shutdown has taken
effect. If the value of this counter is greater than the measurement
period multiplied by a factor of N minus 1 and less than or equal to the
measurement period multiplied by N, the number of PSUs that are shut
down is N, which is greater than or equal to 1.
– If the value of this counter is 0, PSU intelligent shutdown has not taken
effect.

5G RAN

On the live network, the one-week PSU input and output power obtained before
and after PSU intelligent shutdown is enabled can be compared to assess the
energy saving gains of this function.
● Given the same PSU output power, if the PSU input power before function
activation is much higher than that after function activation, greater gains are
provided.
● Given the same PSU input power, if the PSU output power before function
activation is much higher than that after function activation, greater gains are
provided.
The following provides methods for observing PSU input and output power. The
observation result may be inaccurate. The performance counter data on the MAE-
Access is for reference only.
● PSU input power
The PSU input power can be indirectly obtained using the
VS.EnergyCons.BTS.Measuring.NR counter on the MAE-Access.
– In NR-only scenarios, the value of the counter equals the PSU input
power.
– In multimode scenarios, this counter indicates the energy consumption of
the NR part of the base station. The PSU input power equals the counter
value plus the values of counters for other RATs.
● PSU output power
The PSU output power can be indirectly obtained using the
VS.EnergyCons.BTS.Adding.NR counter on the MAE-Access.
– In NR-only scenarios, the value of the counter equals the PSU output
power.
– In multimode scenarios, this counter indicates the energy consumption of
the NR part of the base station. The PSU output power equals the
counter value plus the values of counters for other RATs.

5G RAN
Feature Parameter Description 7 Energy Consumption Monitoring
7 Energy Consumption Monitoring
7.1 Principles
Energy consumption monitoring enables a base station to periodically measure its
energy consumption and report the statistics to the MAE-Access, making it easy
for operators to monitor the base station's energy consumption. The MAE-Access
can perform further statistical analysis on the energy consumption data, as shown
in Figure 7-1. For related descriptions on the MAE-Access, see the corresponding
section in the MAE-Access online help: RAN Management > SON Management >
Base Station Energy Conservation Management.
Figure 7-1 Working principles of energy consumption monitoring
The energy consumption of the BBU and RF modules, as well as that of the entire
base station, can be monitored.
NOTE
This section describes only the energy consumption measurement method on the base
station side.
Energy Consumption Statistics of the Entire Base Station

The energy consumption statistics of the entire base station can be obtained
through cumulative or direct measurements. Cumulative measurement is the most
common, whereas direct measurement applies only to the base stations
configured with the PMU. Neither method requires parameter configuration or
engineering deployment.

5G RAN
● Cumulative measurement
The base station measures the energy consumption of modules, such as the
BBU, RF modules, and fans, on a scheduled basis. All the values add up to the
total energy consumption to be reported to the MAE-Access.
– The modules with digital power supply in the base station automatically
report their energy consumption to the BBU.
– For macro base stations, RRUs or AAUs report their energy consumption,
including that of the remote electrical tilt devices, to the BBU on a
scheduled basis.
For LampSite base stations, pRRUs do not support energy consumption
measurement but RHUBs and RRUs do. If pRRUs are used, the RHUBs
measure the energy consumption of pRRUs, add it up with their own
energy consumption, and report the total value to the BBU on a
scheduled basis. If RRUs are used, the RRUs and RHUBs separately
measure and report their own energy consumption to the BBU on a
scheduled basis. The BBU then reports the total energy consumption of
the RRUs, RHUBs, and the BBU to the MAE-Access.
– For electromechanical devices (such as the EMU, FMU, TCU, PMU, CCU,
MEB, PSU, and BDU) configured in a base station, their energy
consumption data is obtained by the BBU on a scheduled basis.
The VS.EnergyCons.BTS.Adding.NR counter on the MAE-Access indicates the
NR-related energy consumption of a base station. This counter adds up the
NR energy consumption of related units, including BBU boards, RF modules
configured with NR carriers, and fans.
– For an NR-only base station, this counter indicates the energy
consumption of the entire base station.
– For a multimode macro base station supporting NR, this counter
measures the energy consumption of the NR part of the base station, and
its value equals the sum of NR energy consumption of all physical
devices. The NR energy consumption of a single physical device is
calculated using the following formula:
NR energy consumption of a single physical device = (Energy
consumption of a single physical device/Number of main control boards
that manage this physical device)/Number of RATs on the local end that
use this physical device
In the preceding formula, "Number of RATs on the local end that use this
physical device" refers to the number of RATs served by the main control
board that provides NR services and manages the physical device.
For example:
▪ In G+LNR separate-MPT scenarios where G and LNR share the same

RRU: NR RRU energy consumption = (RRU energy consumption/2)/2
= 1/4 RRU energy consumption
▪ In GL+NR separate-MPT scenarios where GL and NR share the same

RRU: NR RRU energy consumption = (RRU energy consumption/2)/1
= 1/2 RRU energy consumption

5G RAN
NOTE
Because a multimode base station serves multiple RATs, the

VS.EnergyCons.BTS.Adding.NR counter does not reflect the exact NR energy
consumption and should therefore be used for reference only. In addition, this
counter does not apply to multimode LampSite base stations supporting NR. For
details about the energy consumption measurement of such base stations, see
Energy Consumption Statistics of the BBU and RF Modules.
● Direct measurement
The energy consumption of a base station configured with a PMU can also be
measured based on the PSUs. The measured energy consumption is the total
value of all devices (including but not limited to the BBU, RF units, and
electromechanical devices) powered by the PSUs. The base station obtains the
total energy consumption from the PMU and reports the value to the MAE-
Access.
The base station can report either AC or DC energy consumption (as shown in
Figure 7-2), depending on the setting of the ENERGYCON.MP parameter in
the SET ECMP command.
– If the ENERGYCON.MP parameter is set to AC, the total AC energy
consumption before PSUs perform AC-to-DC conversion is reported.
– If the ENERGYCON.MP parameter is set to DC, the total DC energy
consumption after PSUs perform AC-to-DC conversion is reported.
Figure 7-2 Direct measurement
The VS.EnergyCons.BTS.Measuring.NR counter on the MAE-Access indicates

the energy consumption of the NR base station calculated based on the
current and voltage of the power supply system.
– If ENERGYCON.MP is set to AC:
▪ For an NR-only base station, this counter indicates the input power
of PSUs calculated by the power supply system.
▪ For a multimode base station supporting NR, this counter indicates

partial input power of PSUs. For example, in dual-mode scenarios,
the value of this counter is half of the total input power of PSUs.
– If ENERGYCON.MP is set to DC:
▪ For an NR-only base station, this counter indicates the output power
of PSUs calculated by the power supply system.

5G RAN
▪ For a multimode base station supporting NR, this counter indicates

partial output power of PSUs. For example, in dual-mode scenarios,
the value of this counter is half of the total output power of PSUs.
Energy Consumption Statistics of the BBU and RF Modules

The base station can also measure the energy consumption of the BBU and RF
modules and report the statistics to the MAE-Access.
● The VS.EnergyCons.BU counter indicates the energy consumption of all

boards in a BBU.
● The VS.EnergyCons.BTSBoard counter indicates the energy consumption of
RF modules.
NOTE
For LampSite base stations, the RHUB measures pRRU energy consumption and reports the
total result to the BBU. This is because pRRUs are not capable of measuring energy
consumption. In such cases, the VS.EnergyCons.BTSBoard counter value adds up the
energy consumption of the RHUB and that of the RHUB-powered pRRUs.
The counters measuring the energy consumption of the BBU and RF modules do
not distinguish between RATs. The energy consumption of a multimode base
station supporting NR is the total energy consumption of the BBU and RF modules
in this base station. In a separate-MPT multimode base station, the energy
consumption of common devices is separately reported by each main control
board. Therefore, when adding up the values of the reported energy consumption
counters, note the following:
● For the BBU, only one counter needs to be added up among all reported
counters with the same cabinet number and subrack number.
● For RF modules, only one counter needs to be added up among all reported
counters with the same cabinet number, subrack number, and slot number.
In a separate-MPT multimode base station, the sampling period and reporting

period of the counters may not be synchronized between different main control
boards. Therefore, a deviation of one sampling period (5 minutes) may exist.
7.2 Network Analysis
7.2.1 Benefits
Although energy consumption monitoring does not provide energy saving gains, it
provides a straightforward method of monitoring the base station energy
consumption. You can use this function to evaluate the energy saving gains
achieved after an energy-saving function is enabled.
7.2.2 Impacts
Network Impacts
None

5G RAN
Function Impacts
None
7.3 Requirements
7.3.1 Licenses
None
7.3.2 Software
None

None
7.3.3 Hardware
Base Station Models
with the BBU3910.
Boards
All NR-capable main control boards and power supply boards support this
function. To learn which main control boards and power supply boards are NR-
capable, see the related BBU technical specifications and hardware description in
3900 & 5900 Series Base Station Product Documentation.
RF Modules
All NR-capable RF modules support this function. For details, see the technical
Documentation.
7.3.4 Others
● The base station is correctly connected to the MAE, the MAE-Access supports
energy consumption monitoring, and the PowerSavingStatistic module is
enabled.
● Table 7-1 describes the PMU requirements of direct measurement of energy
consumption for the entire base station. For details about the PMU, see Power
Supply Management.

5G RAN
Table 7-1 PMU requirements of direct measurement

Type
ETP PMU 11A No requirements
APM5930 (CCUC) No requirements
OPM200 (PMU 16A) No requirements
CCUB Not supported
PMU 15A Not supported
OPM30A Not supported
APM30 PMU 01B No requirements
CCUC No requirements
EPS4890 PMU 01B No requirements
EPS4815 PMU 11A No requirements
EPU None Not supported
SC48200 None Not supported
7.4 Operation and Maintenance

5G RAN
7.4.1 Data Configuration

Energy consumption data can be observed on the MAE-Access without any
configuration on the base station. If the energy consumption data of the base
station needs to be further summarized and analyzed by the MAE-Access, enable
the PowerSavingStatistic component by following instructions in "Managing
Components" in OSS Management of MAE Product Documentation(EulerOS,
TaiShan).
7.4.2 Activation Verification

The energy consumption of the base station can be observed by subscribing to
counters listed in Table 7-2 on the MAE-Access.
Table 7-2 Counters for measuring energy consumption of the NR base station
Counter Name Description
VS.EnergyCons.BTS.Addin This counter provides the NR-specific energy

g.NR consumption of the base station by adding up the
energy consumption of all modules working in NR
mode (cumulative measurement).
VS.EnergyCons.BTS.Meas This counter provides the NR-specific energy

uring.NR consumption of the base station by using the
energy consumption measured by the power
system (direct measurement).
VS.EnergyCons.BU This counter measures the energy consumption of

the BBU.
VS.EnergyCons.BTSBoard This counter measures the energy consumption of

RF modules.
7.4.3 Network Monitoring

None

5G RAN
Feature Parameter Description 8 Parameters
8 Parameters
The following hyperlinked EXCEL files of parameter reference match the software
version with which this document is released.
● Node Parameter Reference: contains device and transport parameters.
● gNodeBFunction Parameter Reference: contains all parameters related to
radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of parameter reference for the software version used on the
live network from the product documentation delivered with that version.
FAQ: How do I find the parameters related to a certain feature from

parameter reference?
Step 1 Open the EXCEL file of parameter reference.

Step 2 On the Parameter List sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All parameters related to the feature are displayed.
----End

5G RAN
Feature Parameter Description 9 Counters
9 Counters
The following hyperlinked EXCEL files of performance counter reference match the
software version with which this document is released.
● Node Performance Counter Summary: contains device and transport counters.
● gNodeBFunction Performance Counter Summary: contains all counters related
to radio access functions, including air interface management, access control,
mobility control, and radio resource management.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
FAQ: How do I find the counters related to a certain feature from

performance counter reference?
Step 1 Open the EXCEL file of performance counter reference.

Step 2 On the Counter Summary(En) sheet, filter the Feature ID column. Click Text
Filters and choose Contains. Enter the feature ID, for example, FBFD-020100.
Step 3 Click OK. All counters related to the feature are displayed.
----End

5G RAN
Feature Parameter Description 10 Glossary
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

5G RAN
Feature Parameter Description 11 Reference Documents
11 Reference Documents
● 3GPP TS 38.104: "NR; Base Station (BS) radio transmission and reception"
● RF Module Deep Dormancy
● Hyper Cell (Low-Frequency TDD)
● Cell Combination
● CMAS
● Remote Interference Management (Low-Frequency TDD)
● Super Uplink
● Synchronization
● Multi-RAT Coordinated Symbol Power Saving
● LTE and NR Intelligent Carrier Shutdown
● Multi-RAT Coordinated Channel Shutdown
● MIMO
● CoMP
● URLLC
● Network Slicing
● Scheduling
● Extended Cell Range
● LTE FDD and NR Spectrum Sharing
● Modulation Schemes
● Channel Management
● Carrier Aggregation
● ANR
● Mobility Management
● Power Supply Management
● UE Power Saving
● License Management
● OSS Management in MAE Product Documentation (EulerOS, TaiShan)
● PSU in 3900 & 5900 Series Base Station Product Documentation

5G RAN
Feature Parameter Description 11 Reference Documents
● Technical Specifications in 3900 & 5900 Series Base Station Product

Documentation

Energy Conservation and Emission Reduction

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Energy Conservation and Emission Reduction

Uploaded by

Copyright:

Available Formats

5G RAN

Energy Conservation and Emission

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. i

2 About This Document...........................................................................................................14

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. ii

4.1.4.2 Activation Verification.................................................................................................................................................. 26

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. iii

5 Network Level Energy Saving.......................................................................................... 102

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. iv

5.1.3.2 Software.......................................................................................................................................................................... 118

6 Site Level Energy Saving................................................................................................... 126

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. v

6.2.4.1.3 Using the MAE-Deployment.................................................................................................................................148

7 Energy Consumption Monitoring.................................................................................... 155

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. vi

This chapter describes changes not included in the "Parameters", "Counters",

1.1 5G RAN5.1 06 (2021-09-29)

Added a parameter to None FDD 3900 and

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 1

1.2 5G RAN5.1 05 (2021-09-02)

Added support for the Modified FDD 3900 and

Optimized the carrier None FDD 3900 and

Added support for license None FDD DBS3900

Canceled automatic None FDD DBS3900

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 2

Change Description Parameter RAT Base Station

Activated a bit of a Modified Low- 3900 and

1.3 5G RAN5.1 04 (2021-06-26)

Added the function None FDD 3900 and

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 3

Change Description Parameter RAT Base Station

Activated a reserved Activated the FDD 3900 and

Modified the network None FDD 3900 and

Added support for None FDD DBS3900

1.4 5G RAN5.1 03 (2021-05-29)

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 4

Activated a reserved Modified FDD 3900 and

1.5 5G RAN5.1 02 (2021-04-30)

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 5

Activated a reserved Modified FDD 3900 and

Added an impact None FDD 3900 and

Added support for None FDD DBS3900

1.6 5G RAN5.1 01 (2021-03-05)

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 6

Added a mutually None Low- DBS3900

None None FDD None

1.7 5G RAN5.1 Draft A (2020-12-29)

Removed the mutually None FDD 3900 and

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 7

Change Description Parameter RAT Base Station

Added the Power Saving None FDD 3900 and

Added protection for CSI- Modified FDD 3900 and

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 8

Change Description Parameter RAT Base Station

Modified the following Added FDD 3900 and

Removed the mutually None Low- DBS3900

Issue 06 (2021-09-29) Copyright © Huawei Technologies Co., Ltd. 9

Change Description Parameter RAT Base Station

Removed the mutually None FDD 3900 and

Enabled the configuration Added the FDD 3900 and

Enabled low power None FDD 3900 and