Energy Conservation and Emission Reduction
Energy Conservation and Emission Reduction
Reduction
Contents
8.2.1.9 Energy Conservation and Emission Reduction
eRAN
Energy Conservation and Emission
Reduction Feature Parameter
Description
Issue 03
Date 2019-10-15
HUAWEI TECHNOLOGIES CO., LTD.
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.
Website: https:/
Email: [email protected]
8.2.1.9 Contents
1 Change History
1.1 eRAN15.1 03 (2019-10-15)
1.2 eRAN15.1 02 (2019-06-29)
1.3 eRAN15.1 01 (2019-06-06)
1.4 eRAN15.1 Draft F (2019-05-10)
1.5 eRAN15.1 Draft E (2019-04-10)
1.6 eRAN15.1 Draft D (2019-03-18)
1.7 eRAN15.1 Draft C (2019-02-22)
1.8 eRAN15.1 Draft B (2019-01-10)
1.9 eRAN15.1 Draft A (2019-01-05)
3 Overview
13 Parameters
14 Counters
15 Glossary
16 Reference Documents
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 eRAN15.1 03 (2019-10-15)
Technical Changes
Added the AAU5726 into the None FDD 3900 and 5900 series
scope of RF modules that base stations
support symbol power saving.
For details, see 11.3.3 Hardware.
Added the restriction that the None FDD All base station models
AAU5726 does not support
dynamic voltage adjustment.
For details, see 6.3.3 Hardware.
Technical Changes
None
Editorial Changes
Technical Changes
Editorial Changes
Technical Changes
Added the RRU5251 into the None TDD 3900 and 5900 series
scope of RF modules that base stations
support symbol power saving.
For details, see 11.3.3 Hardware.
Editorial Changes
Technical Changes
Change Description Parameter Change RAT Base Station Model
Extended the time for UE None FDD All base station models
handovers from a capacity cell TDD
to the co-coverage neighboring
basic cells from 30s to 60s for
intelligent power-off of carriers
in the same coverage. For
details, see 9.1.3 eNodeB Actions.
Editorial Changes
Technical Changes
Added support for pRRU deep None FDD DBS3900 LampSite and
dormancy in LampSite TDD DBS5900 LampSite
DCU3900/DCU3910 networking
scenarios.
Added the AAU5614 into the None TDD 3900 and 5900 series
scope of RF modules that base stations
support symbol power saving.
For details, see 11.3.3 Hardware.
Editorial Changes
Technical Changes
Change Description Parameter Change RAT Base Station Model
Editorial Changes
Technical Changes
Editorial Changes
Technical Changes
Added the support for Added the FDD All base station
the intelligent power- CellShutdown.InterBbuCarrierShutdownSw TDD models
off of carriers in the parameter.
same coverage Modified the values of the
function in inter-BBU CellShutdown.CellShutdownSwitch
macro cells. For parameter.
details, see 9.1
Principles.
Added the Adaptive Added the CellAlgoSwitch.DynAdjVoltSwitch TDD All base station
Power Control feature. parameter. models
For details, see 6
Adaptive Power
Consumption.
Change Description Parameter Change RAT Base Station
Model
Editorial Changes
Purpose
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 the desired gains, contact Huawei
professional service engineers.
Software Interfaces
Any parameters, alarms, counters, or managed objects (MOs) described in this document apply
only to the corresponding software release. For future software releases, refer to the
corresponding updated product documentation.
Feature Differences Between RATs
Consumption Consumption
Mode Mode
3 Overview
Huawei's end-to-end solution for energy conservation and emission reduction is launched to
address the energy and environment issues worldwide and to drag down the operating expense
(OPEX) borne on operators. This solution reduces the power consumption and improves the
operating efficiency of devices like power amplifiers (PAs). Operators can use the element
management system (EMS) to monitor the power consumption of devices and related changes.
Energy conservation and emission reduction can be implemented at the device, network, and
base station levels depending on the objects involved. Table 3-1 provides the details. Among all
base station components, RF modules consume the most power. Baseband units are second to RF
modules in the amount of power consumption.
Table 3-1 Classification of energy conservation and emission reduction functions
Category Function Name
In certain indoor scenarios such as shopping malls, stadiums, and office buildings, there are no
service requirements when the venues are almost empty. With this function, some pRRUs can be
shut down and enter the deep dormancy state during periods with no services, reducing energy
consumption.
Figure 4-1 pRRU deep dormancy
4.1 Principles
If a pRRU enters the deep dormancy state, it does not transmit power. Entering a deep dormancy
period does not trigger the following alarms. If any of them is reported, it was triggered by other
causes.
ALM-29240 Cell Unavailable
ALM-29243 Cell Capability Degraded
ALM-29248 RF Out of Service
ALM-29249 eNodeB Out of Service
ALM-26787 RHUB-pRRU CPRI Interface Error
When a pRRU has entered a deep dormancy period, the following operations cannot be
performed:
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
4.1.2 pRRU Deep Dormancy in Intelligent Mode
In intelligent mode, when there is a light load in a cell, the eNodeB instructs some of the pRRUs
serving the cell to enter the deep dormancy state and uses the remaining pRRUs to ensure the
basic indoor coverage. In this way, energy consumption is reduced. The eNodeB automatically
selects which pRRUs should enter the deep dormancy state.
To ensure the basic coverage after pRRU deep dormancy takes effect, the carrier for basic
coverage must be retained based on the downlink E-UTRA absolute radio frequency channel
number (EARFCN) specified by the EnodebMpruEs.MpruDormancyDlEarfcn parameter. When
this parameter is set to a value other than –1, pRRU deep dormancy in intelligent mode is
enabled.
It is recommended that this parameter be set to an EARFCN in the 2300 MHz band for TDD and
to an EARFCN in the 1800 MHz band for FDD if multiple frequencies are configured for an
eNodeB.
pRRU deep dormancy in intelligent mode requires that the cell bandwidth be higher than 10
MHz.
4.1.2.1 pRRU Data Sampling and Processing
After pRRU deep dormancy in intelligent mode is enabled, the eNodeB collects measurement
reports (MRs) and sounding reference signal (SRS) measurement data. A maximum of 200
samples can be collected for each pRRU. When 200 samples are collected or the collection has
lasted for seven days, the eNodeB stops the initial data collection. The pRRU deep dormancy
function does not take effect before the initial data collection is complete.
If any of the following situations occurs during the initial data collection, data collection will
start over again and the time when this function takes effect will be postponed accordingly:
The baseband processing unit (BBP) serving this cell restarts up.
The optical fiber of the RHUB is disconnected intermittently.
The S1 transmission link is disconnected intermittently.
The cell is reestablished.
The eNodeB restarts up after a version upgrade.
When the initial data collection is complete, the eNodeB processes the collected data and
determines which pRRUs should enter the deep dormancy state based on the processing result.
Data update starts after the initial data collection. The data will be updated once a day. The
earliest 5% of the collected data will be overwritten for each pRRU. After seven days of data
update (which is referred to as a data update period), the eNodeB processes the data. The
processing result is used as a basis for the eNodeB to determine which pRRUs should enter the
deep dormancy state in the next period. The data is collected at the non-energy-saving time.
For FDD, the SRSCfg.SrsCfgInd and SRSCfg.FddSrsCfgMode parameters must be configured to implement SRS
measurements.
The pRRU selection principle is that the eNodeB should determine the minimum number of
pRRUs to be retained to keep the minimum downlink reference signal received power (RSRP) of
the cell greater than the value of the EnodebMpruEs.MpruDormancyMinimumRsrp parameter. All
the other pRRUs can be selected to enter the deep dormancy state.
After the sampling, the eNodeB selects pRRUs as follows:
At each sampling time, the eNodeB retains the minimum number of pRRUs that can meet the
minimum downlink RSRP requirement of the cell.
For all sampling moments, the eNodeB retains the pRRUs that most frequently meet the
preceding requirement.
The pRRUs that should enter the deep dormancy state for an eNodeB can be selected after the
eNodeB determines the pRRUs to be retained for all cells served by the eNodeB.
4.1.2.3 eNodeB Actions
If there is an excessively large temperature differential of pRRUs before and after they enter the deep dormancy
state, hardware faults may occur. To prevent such risks, the pRRUs will not enter the deep dormancy state if their
temperature differential within 24 hours exceeds a specified threshold.
The temperature differential threshold for 3000 series pRRUs is 35°C.
The temperature differential threshold for 5000 series pRRUs is 34°C. The pRRU5913 and pRRU5918 are two
exceptions, whose temperature differential threshold is 27°C.
4.1.2.4 Leaving
If any of the following conditions is met, the pRRUs in the deep dormancy state exit this state
and the eNodeB restores the CRS power of the cell to the original values:
The period specified by the EnodebMpruEs.MpruDormancyStartTime and
EnodebMpruEs.MpruDormancyStopTime parameters ends.
The downlink PRB usage of the cell is greater than the
EnodebMpruEs.MpruDormancyDlPrbUsageThld parameter value plus 5.
A retained active pRRU of the cell becomes unavailable.
When the pRRUs exit the deep dormancy state because a retained active pRRU of the cell becomes unavailable, the
eNodeB will select pRRUs again for entry into the deep dormancy state.
4.2.1 Benefits
Scheduled Mode
You are advised to enable pRRU deep dormancy in scheduled mode when there are no service
requirements at night in indoor scenarios deployed with LampSite base stations. This function
helps reduce device power consumption in such indoor space as shopping malls, office buildings,
and subway stations.
When a LampSite base station has 96 pRRUs and they all enter the deep dormancy state, 35% to
40% energy can be saved for this base station. You can monitor the eNodeB power consumption
using the counter described in Table 4-1.
Table 4-1 eNodeB power consumption counter
The overall effect of using pRRU deep dormancy depends on how long there are no services and
on the size of the area with no services.
The longer there are no services, the more power is saved.
When the area with no services is larger, more pRRUs can enter the deep dormancy state.
Intelligent Mode
You are advised to enable pRRU deep dormancy in intelligent mode when LampSite base
stations are deployed to provide indoor coverage, there is light traffic in a consecutive period of
time, and the indoor coverage integrity needs to be ensured. This function helps reduce device
power consumption in the preceding scenario.
When there are few partitions indoors, about one-third of the pRRUs of a base station can enter
the deep dormancy state and 5% to 10% energy can be saved for this base station. When there
are more partitions indoors, the signal penetration capability is poorer, fewer pRRUs can enter
the deep dormancy state, and less energy can be saved.
4.2.2 Impacts
Network Impacts
Scheduled mode
The signal strength in an area with some pRRUs in the deep dormancy state will decrease
because these pRRUs do not transmit signals. UE service quality may deteriorate, and there
may be service drops and access failures.
When normal cells are in the same carrier aggregation (CA) group as an MPRU aggregation
cell, if all of the pRRUs of the MPRU aggregation cell enter the deep dormancy state, the
normal cells will report ALM-29243 Cell Capability Degraded alarms. If this is the case, CA
cannot provide maximum gains.
Intelligent mode
When pRRU deep dormancy in intelligent mode takes effect, the downlink RSRP of indoor
coverage at certain cell edges may slightly decrease but is still greater than or equal to the
value of the EnodebMpruEs.MpruDormancyMinimumRsrp parameter. As a result, the downlink
peak throughput of the cells may decrease.
Function Impacts
intelligent mode
serves as a
candidate cell for
MLB, the load of
this cell increases
due to load
balancing. As a
result, the
probability of
exiting the deep
dormancy state
increases and the
energy saving
gains may be
affected.
pRRU deep dormancy in scheduled mode does not have impacted functions.
4.3 Requirements
4.3.1 Licenses
Scheduled Mode
If a LampSite eNodeB is RFA-capable, there are no license requirements for the RFA mode. For
example, in the LTE FDD + GSM (RFA via MERC) scenario, this function can take effect as
long as an FDD license item is available. No additional license items are required for RFA. RFA
is short for Radio Frequency Access, and MERC is short for Multi Extended Radio Frequency
Card.
Intelligent Mode
4.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.
Prerequisite Functions
None
Functions that do not work with pRRU deep dormancy in intelligent mode
All functions are compatible with pRRU deep dormancy in scheduled mode.
4.3.3 Hardware
DBS3900 and DBS5900 LampSite eNodeBs (including BBU+DCU3910 for RF signal input) are
compatible with this function.
Boards
RF Modules
Scheduled Mode
All RATs in a multimode base station must support pRRU deep dormancy for the function to
take effect for LTE. For example, for a UMTS and LTE multimode base station, pRRU deep
dormancy must also be enabled for UMTS during the same period so that this function can take
effect for LTE.
For a UMTS and LTE multimode base station, the UMTS NodeB must be upgraded to RAN20.1
or later.
In pRRU cascading scenarios, the first-level pRRUs do not support deep dormancy.
pRRU deep dormancy is not recommended if the pRRUs serve NB-IoT carriers. If this function
is used, data transmission of NB-IoT UEs may be affected.
Intelligent Mode
The following requirements must be met for pRRU deep dormancy in intelligent mode:
If an eNodeB operates on multiple LTE frequencies, cells on these frequencies must cover the
same area and the cell on the frequency providing basic coverage must be configured as a
neighboring cell of other inter-frequency cells. If an inter-frequency cell is an LAA cell or a
cell involved in downlink CA, the cell providing basic coverage does not need to be
configured as a neighboring cell of the inter-frequency cell.
The bandwidth of the cell on the frequency providing basic coverage must be 20 or 15 MHz.
pRRU deep dormancy in intelligent mode is not used for indoor, densely distributed, and
heavily loaded base stations with multiple frequencies not covering the same area.
In intelligent mode, the number of pRRUs in a sector equipment group cannot exceed 16.
For a separate-MPT UMTS and LTE multimode base station, pRRU deep dormancy in
scheduled mode for the entire base station must be configured on the UMTS side, with the
dormancy period being the same as that set for the LTE side.
In pRRU cascading scenarios, the first-level pRRUs do not support deep dormancy.
This feature does not apply to the scenario where LTE and NR share RF modules.
4.3.5 Others
You are not advised to enable both pRRU deep dormancy in scheduled mode and pRRU deep
dormancy in intelligent mode during the same period. Otherwise, indoor coverage problems may
occur.
4.4 Operation and Maintenance
Table 4-2 describes the parameters used for activation of pRRU deep dormancy in scheduled
mode.
Table 4-2 Parameters used for activation of pRRU deep dormancy in scheduled mode
Parameter Name Parameter ID Setting Notes
Dormancy Start RRU.DORMANCYSTARTTIME You are advised to set this parameter to the
Time beginning of a period when there are no
services.
Dormancy Stop RRU.DORMANCYSTOPTIME You are advised to set this parameter to the
Time end of a period when there are no services.
Table 4-3 describes the parameters used for activation of pRRU deep dormancy in intelligent
mode.
Table 4-3 Parameters used for activation of pRRU deep dormancy in intelligent mode
Parameter Parameter ID Setting Notes
Name
You can run the DSP ENODEBMPRUDORMANCY command to query which pRRUs are in
the deep dormancy state according to the selection result. The Dormancy State is ENABLED
for pRRUs in the deep dormancy state and DISABLED for pRRUs not in the deep dormancy
state.
//Querying the eNodeB-level MPRU deep dormancy status
DSP ENODEBMPRUDORMANCY:;
The result is shown as follows:
+++ HUAWEI 2018-10-16 16:32:44
O&M #806354975
%%DSP ENODEBMPRUDORMANCY:;%%
RETCODE = 0 Operation succeeded.
Display ENODEBMPRUDORMANCY State
----------------------
MPRU Cabinet Number MPRU Subrack Number MPRU Slot Number Dormancy State
0 60 0 ENABLED
0 61 0 DISABLED
...
(Number of results = xxx)
--- END
You can monitor the eNodeB power consumption using the counter described in Table 4-4. The
VS.EnergyCons.BTS.Adding.RFA counter needs to be monitored only when the eNodeB is RFA-
capable.
Table 4-4 eNodeB power consumption counter
Counter ID Counter Name Description
RF channel intelligent shutdown enables the eNodeB to shut down some of the transmit channels
in the cell when the cell has no services or has a low volume of services.
Figure 5-1 RF channel intelligent shutdown
5.1 Principles
An FDD cell will enter the RF channel intelligent shutdown state only when the cell meets all of
the following conditions:
All transmit channels of the cell work properly.
For a cell under a macro cell with a downlink bandwidth higher than 10 MHz, the number of
RRC_CONNECTED UEs in the cell is less than or equal to the CellRfShutdown.UENumThd
parameter value.
For a macro cell with a downlink bandwidth of 10 MHz or a cell under a micro cell, there are
no RRC_CONNECTED UEs in the cell.
The uplink and downlink PRB usages of the cell do not exceed their respective PRB usage
thresholds.
The uplink PRB usage threshold is specified by the CellRfShutdown.UlPrbThd parameter.
The downlink PRB usage threshold is specified by the CellRfShutdown.DlPrbThd
parameter.
No UEs are performing voice services in the cell. This requirement applies only when the
RRC_CONNECTED UE number threshold is set to a value greater than 0.
The cell-specific reference signal (CRS) transmit power can be increased.
After RF channel intelligent shutdown takes effect, CRS transmit power needs to be increased
to ensure coverage.
The cell is not in a penalty period.
To prevent ping-pong RF channel shutdown, the eNodeB starts a penalty timer of 30 minutes
when the cell meets specific conditions upon exit from the RF channel intelligent shutdown
state. The cell will not re-enter the RF channel intelligent shutdown state during this penalty
period, even if the preceding triggering conditions are met.
If the cell is a LampSite cell, the cell is not in the pRRU deep dormancy state in intelligent
mode.
The eNodeB imposes a penalty if a cell meets any of the following conditions upon exit from RF
channel intelligent shutdown state:
For a macro cell with a downlink bandwidth higher than 10 MHz, the number of
RRC_CONNECTED UEs in the cell is greater than the CellRfShutdown.UENumThd
parameter value.
For a macro cell with a downlink bandwidth of 10 MHz or a micro cell, there are
RRC_CONNECTED UEs in the cell.
The PRB usage of the cell exceeds the corresponding threshold.
The power is limited in the downlink.
UEs are performing voice services in the cell.
For micro eNodeBs, RF Channel Intelligent Shutdown takes effect only when the cell is not
processing any services.
For macro and LampSite eNodeBs, RF Channel Intelligent Shutdown can also take effect when
cell load is light. Macro and LampSite eNodeBs can identify UE service types. This feature does
not take effect when there are UEs performing voice services in the cell.
In TDD, there are two policies used to determine the conditions for entering the RF channel
intelligent shutdown state. The conditions vary with the policies specified by the
CellRfShutdown.RfShutdownJudgingPolicy parameter:
When this parameter is set to PRB, the eNodeB determines whether a cell enters or exits the
RF channel intelligent shutdown state based on the uplink and downlink PRB usages. A cell
meeting all of the following conditions will enter the RF channel intelligent shutdown state:
2T2P/4T4P cell: There are no RRC_CONNECTED UEs in the cell.
8T2P/8T4P/4T2P/64T2P cell: The uplink and downlink PRB usages of the cell do not
exceed their respective thresholds.
The uplink PRB usage threshold is specified by the CellRfShutdown.UlPrbThd
parameter.
The downlink PRB usage threshold is specified by the CellRfShutdown.DlPrbThd
parameter.
When the CellRfShutdown.RfShutdownJudgingPolicy parameter is set to
PRB_AND_UE_NUMBER, the eNodeB determines whether a cell enters or exits the RF
channel intelligent shutdown state based on the uplink and downlink PRB usages as well as
the number of RRC_CONNECTED UEs. A cell meeting all of the following conditions will
enter the RF channel intelligent shutdown state:
The number of RRC_CONNECTED UEs in the cell does not exceed the
RRC_CONNECTED UE number threshold specified by the CellRfShutdown.UENumThd
parameter.
The uplink and downlink PRB usages of the cell do not exceed their respective thresholds.
This requirement applies only when the RRC_CONNECTED UE number threshold is set
to a value greater than 0.
The uplink PRB usage threshold is specified by the CellRfShutdown.UlPrbThd
parameter.
The downlink PRB usage threshold is specified by the CellRfShutdown.DlPrbThd
parameter.
In addition to the preceding conditions, the following conditions must also be met before the
eNodeB shuts down transmit channels:
The CRS transmit power can be increased.
After RF channel intelligent shutdown takes effect, CRS transmit power needs to be increased
to ensure coverage.
The cell is not in a penalty period.
To prevent ping-pong RF channel shutdown, a penalty timer of 30 minutes is started when the
cell exits the RF channel intelligent shutdown state. The cell will not re-enter the RF channel
intelligent shutdown state during this penalty period, even if the preceding triggering
conditions are met.
If the cell is a LampSite cell, the cell is not in the pRRU deep dormancy state in intelligent
mode.
For a 2T, 4T, or 8T cell, all of the RF channels in the cell are functioning properly.
For a 64T cell, there are two CRS ports, the calibration channel is not faulty, and there are no
more than four faulty RF channels in the cell. In addition, the value of the
BFANT.CoverageScenario parameter cannot be EXPANDSCENARIO_1,
EXPANDSCENARIO_2, or EXPANDSCENARIO_3.
5.1.2 eNodeB Actions
The eNodeB shuts down some RF channels based on the following rules:
For a 2T2P cell, the eNodeB shuts down the transmit channel of Port 1. The transmit channel
of Port 0 still works.
For a 4T4P cell, the eNodeB shuts down the transmit channels of Ports 1 and 2. The transmit
channels of Ports 0 and 3 still work.
In a cell where the number of transmit channels is greater than the value of the
Cell.CrsPortNum parameter, a port corresponds to multiple transmit channels. If this is the
case, the eNodeB shuts down half of the transmit channels for each port.
After shutting down certain RF channels, the eNodeB increases the CRS transmit power to keep
the coverage area unchanged. The amount by which the CRS transmit power will be increased is
specified by the CellRfShutdown.RsPwrAdjOffset parameter. After increasing the CRS transmit
power, the eNodeB automatically changes the number of required symbols for the physical
downlink control channel (PDCCH) to 3.
5.1.3 Leaving
Cells exit the RF channel intelligent shutdown state when any of the following conditions is met:
The CellRfShutdown.RfShutdownSwitch parameter is changed to OFF.
The RF channel intelligent shutdown period specified by the CellRfShutdown.StartTime and
CellRfShutdown.StopTime parameters ends.
The eNodeB detects that the common channel transmit power is limited.
Faults occur on active RF channels.
The number of RRC_CONNECTED UEs in the cell exceeds the RRC_CONNECTED UE
number threshold.
For macro cells with a downlink bandwidth higher than 10 MHz, the RRC_CONNECTED
UE number threshold is determined by the CellRfShutdown.UENumThd parameter.
For macro cells with a downlink bandwidth higher than 5 MHz but lower than or equal to
10 MHz or micro cells, the RRC_CONNECTED UE number threshold is always 0.
A UE performing voice services accesses the cell where the RRC_CONNECTED UE number
threshold is not 0.
The uplink PRB usage of the cell is greater than the sum of the CellRfShutdown.UlPrbThd
and CellRfShutdown.UlPrbOffset parameter values.
The downlink PRB usage of the cell is greater than the sum of the CellRfShutdown.DlPrbThd
and CellRfShutdown.DlPrbOffset parameter values.
Cells exit the RF channel intelligent shutdown state when any of the following conditions is met:
The CellRfShutdown.RfShutdownSwitch parameter is changed to OFF.
The RF channel intelligent shutdown period specified by the CellRfShutdown.StartTime and
CellRfShutdown.StopTime parameters ends.
The eNodeB detects that the common channel transmit power is limited.
Faults occur on active RF channels.
When the CellRfShutdown.RfShutdownJudgingPolicy parameter is set to PRB, the leaving
conditions are as follows:
2T2P/4T4P cell: Any RRC_CONNECTED UE accesses the cell.
8T2P/8T4P/4T2P/64T2P cell: The cell exits the RF channel intelligent shutdown state
when either of the following conditions is met:
The uplink PRB usage of the cell is greater than the sum of the
CellRfShutdown.UlPrbThd and CellRfShutdown.UlPrbOffset parameter values.
The downlink PRB usage of the cell is greater than the sum of the
CellRfShutdown.DlPrbThd and CellRfShutdown.DlPrbOffset parameter values.
When the CellRfShutdown.RfShutdownJudgingPolicy parameter is set to
PRB_AND_UE_NUMBER, the leaving conditions vary with the RRC_CONNECTED UE
number threshold:
If the RRC_CONNECTED UE number threshold is 0, the cell exits the RF channel
intelligent shutdown state when a new RRC_CONNECTED UE accesses the cell.
If the RRC_CONNECTED UE number threshold is greater than 0, the cell exits the RF
channel intelligent shutdown state when any of the following conditions is met:
The number of RRC_CONNECTED UEs in the cell exceeds the RRC_CONNECTED
UE number threshold.
The uplink PRB usage of the cell is greater than the sum of the
CellRfShutdown.UlPrbThd and CellRfShutdown.UlPrbOffset parameter values.
The downlink PRB usage of the cell is greater than the sum of the
CellRfShutdown.DlPrbThd and CellRfShutdown.DlPrbOffset parameter values.
When the eNodeB exits the RF channel intelligent shutdown state, channel calibration is
immediately triggered for 8T cells, and the antenna weighting is restored to its original value.
5.2 Network Analysis
5.2.1 Benefits
RF channel intelligent shutdown reduces the power consumption of the eNodeB. For a 2T cell or
a cell with more transmit antennas, it is recommended that this feature be enabled during off-
peak hours when the cell is lightly loaded.
You are not advised to use this feature when UEs are in high-speed mobility states.
When multiple carriers share the same PA, the PA can be shut down only when all the carriers
are powered off. If RF channels are shut down only for the LTE carrier but not for other carriers
sharing the same PA, the PA cannot be shut down. In such a case, there will be no power saving
gains.
To prevent energy saving–triggered shutdown from affecting the lifespan of RF modules, the RF
modules may exit the energy saving state when their own temperature differential exceeds a
specified threshold within 24 hours. Energy saving gains decrease in this case.
5.2.2 Impacts
Network Impacts
Function Impacts
FDD Channel Joint channel calibration: MIMO For a cell in the RF chann
TDD calibration RruJointCalParaCfg.TxChnCalSwitch intelligent shutdown state
Downlink-only module channel calibration (FDD): channel calibration fails, o
RruJointCalParaCfg.AauPassivePortCalibPeriod functions that depend on
channel calibration may n
function properly. In addit
message indicating a failu
be displayed on the
maintenance and testing
used for channel calibratio
5.3 Requirements
5.3.1 Licenses
5.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.
Prerequisite Functions
None
FDD UMTS and UL_SPECTRUM_SHARING option of the UMTS and After UMTS and LTE
LTE Spectrum SpectrumCloud.SpectrumCloudSwitch LTE Spectrum Sharing is
Spectrum
Sharing (LTE parameter Sharing enabled, if the
FDD) PDSCHCfg.CellPowerLimit
parameter is set to a
value greater than 0, the
maximum transmit power
of a single channel in the
LTE cell is limited. If this
RAT Function Name Function Switch Reference Description
FDD CRS port AutoRecfgSwitch parameter in the STR MIMO When the RF channel
mapping CRSPORTOPTDET command intelligent shutdown
detection and function is enabled
reconfiguration together with the CRS
port mapping detection
and reconfiguration
function, the CRS port
detection result is
inaccurate. Enabling both
functions is not
recommended.
5.3.3 Hardware
Boards
None
RF Modules
Cells
None
5.4 Operation and Maintenance
1. Run the DSP CELL command to check the value of the Cell power save state parameter. If
it is CELL_PWRSAVE_RFSHD, this function has taken effect.
2. (Optional) If RF channel intelligent shutdown does not take effect, run the DSP
CELLRFSHUTDOWN command to query the current status of RF channel intelligent
shutdown and the cause why the cell did not enter the RF channel intelligent shutdown state
or exited this state.
5.4.4 Network Monitoring
Benefit Monitoring
You can check how long RF channel intelligent shutdown has taken effect by monitoring the
counters listed in Table 5-3.
Table 5-3 Counters related to RF channel intelligent shutdown
You can monitor eNodeB power consumption using the counter described in Table 5-4. On the
live network, you can compare one-week eNodeB power consumption before and after the
function is enabled to evaluate the energy saving gains of this function.
Table 5-4 eNodeB power consumption counter
Possible Issues
When a cell cannot enter the RF channel intelligent shutdown state as expected, perform the
following operations:
Run the DSP CELLRFSHUTDOWN command to query the current status of RF channel
intelligent shutdown and the reason why the cell did not enter the RF channel intelligent
shutdown state or exited this state. Table 5-5 and Table 5-6 describe the values of Current status
about RF intelligent shutdown and Latest exiting cause about RF intelligent shutdown in
the command output, respectively.
Table 5-5 Causes indicated by the current status about RF channel intelligent shutdown
OTHERS(Not entering because of other The cell does not enter the RF channel intelligent
reasons) shutdown state. The possible causes are as
follows:
The system time is not within the period of RF
channel intelligent shutdown.
The current cell is unavailable.
Functions that do not work with RF channel
intelligent shutdown, for example, unlimited-
service UE guarantee, are enabled.
The cell is already in another energy saving
state, for example, intelligent power-off of
carriers in the same coverage or low power
consumption mode.
QCI1_UE_EXIST(Not entering because There are UEs using voice services in the cell.
the existence of QCI=1 UEs)
RB_RATIO_EXCEED(Not entering The PRB usage does not meet the following
because the UL/DL PRB ratio exceeds the conditions:
PRB threshold) The uplink PRB usage of the cell is less than or
equal to the CellRfShutdown.UlPrbThd
parameter value.
The downlink PRB usage of the cell is less
than or equal to the CellRfShutdown.DlPrbThd
parameter value.
TIME_EXPIRES(Time expires) The system time is later than the stop time.
QCI1_UE_EXIST(The existence of There are UEs using voice services in the cell.
QCI=1 UEs)
RB_RATIO_EXCEED(The UL/DL PRB The uplink PRB usage of the cell is greater than
ratio exceeds the PRB threshold) the CellRfShutdown.UlPrbThd parameter value.
The downlink PRB usage of the cell is greater than
the CellRfShutdown.DlPrbThd parameter value.
6.1 Principles
The dynamic voltage adjustment function is enabled when the DynAdjVoltSwitch option of the
CellAlgoSwitch.DynAdjVoltSwitch parameter is selected.
Dynamic voltage adjustment can be used only in macro eNodeBs. To use dynamic voltage
adjustment, ensure that the cell parameter settings meet both of the following requirements:
The CellDlpcPdschPa.PaPcOff parameter must be set to at least –3 dB. This parameter affects
the maximum configurable TX power and the number of RBs available after dynamic voltage
adjustment takes effect.
The CellPdcchAlgo.ComSigCongregLv parameter must be set to CONGREG_LV4. This
parameter affects the amount of downlink control information (DCI) that can be transmitted
over the PDCCH.
6.1.1.1 Triggering
When this function is enabled, the eNodeB adjusts PA working voltage based on the cell load.
The cell enters the dynamic voltage adjustment mode when there are no RRC_CONNECTED
UEs for 10 minutes.
6.1.1.2 eNodeB Actions
After the cell enters the dynamic voltage adjustment mode, the power of the downlink physical
channels may be limited. To reduce the power limitation probability, the eNodeB changes the
number of PDCCH symbols in a cell to 3.
6.1.1.3 Leaving
When there are UEs in the cell, the cell exits the dynamic voltage adjustment mode. The eNodeB
restores the number of required symbols for the PDCCH and sets the PA working voltage to the
value required by the maximum transmit power.
The cell also exits the dynamic voltage adjustment mode if dynamic voltage adjustment is
disabled.
6.1.2 RF Module Regular Time Sleep Mode (FDD)
With this function, all of the RF modules of an eNodeB enter the sleep mode in specified periods
and all related cells are automatically shut down. This function can be enabled using the
eNodeBAutoPowerOff.AutoPowerOffSwitch parameter. The sleep time and wake-up time are
configured using the eNodeBAutoPowerOff.PowerOffTime and
eNodeBAutoPowerOff.PowerOnTime parameters.
RF modules can change from any other energy saving mode to the sleep mode. When RF module
regular time sleep mode takes effect, among all energy conservation and emission reduction
functions, only power consumption monitoring can take effect.
When the triggering conditions for this function and dynamic voltage adjustment are both met,
only this function will take effect.
When RF modules enter the sleep mode, cells are deactivated and the RF modules do not transmit power. When RF
modules exit the sleep mode, the cells are automatically reactivated and the RF modules transmit power is restored.
The modules do not need to be restarted.
6.1.2.1 Triggering
In specified sleep mode periods, all cells of the eNodeB are disabled and the RF modules enter
the sleep mode.
6.1.2.2 eNodeB Actions
During the specified sleep mode periods, the eNodeB shuts down all of its cells. When the
periods end, the eNodeB re-enables them.
6.1.2.3 Leaving
When the specified sleep mode periods end, the eNodeB enables all cells and the RF modules
exit the sleep mode.
6.2 Network Analysis
6.2.1 Benefits
Adaptive power consumption is recommended when there are no UEs on the network during a
specific period of time. Enabling this function reduces the power consumption of the eNodeBs.
To prevent energy saving–triggered shutdown from affecting the lifespan of RF modules, the RF
modules may exit the energy saving state when their own temperature differential exceeds a
specified threshold within 24 hours. Energy saving gains decrease in this case.
6.2.2 Impacts
Network Impacts
Function Impacts
adjustment
mode only if
load
simulation
stops.
eMTC system
information will
increase the
power
insufficiency
probability.
Dynamic
voltage
adjustment is
less likely to
be triggered,
affecting the
power saving
gains.
6.3 Requirements
6.3.1 Licenses
6.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.
Prerequisite Functions
None
6.3.3 Hardware
Boards
None
RF Modules
Ensure that the RF modules meet the following requirements before enabling dynamic voltage
adjustment:
The RF modules must be LTE-only modules or multimode modules that have been configured
for LTE only.
Each RF module works on a single carrier.
If this feature is used with the RRU3268 or RRU3260, the RF module should be configured
with the maximum power. Otherwise, this feature is not recommended.
For FDD, the RF module cannot be RRU3964 or AAU5726, which does not support dynamic
voltage adjustment.
For TDD, the RF module must be the AAU5271 working in the 2.6 GHz band (Band 38).
Only such a TDD RF module supports dynamic voltage adjustment.
Cells
Dynamic voltage adjustment requires that the cell bandwidth be higher than 5 MHz.
6.3.4 Networking
None
6.3.5 Others
None
6.4 Operation and Maintenance
Table 6-1 and Table 6-2 describe the parameters used for function activation.
Table 6-1 Parameters used for activation of dynamic voltage adjustment
RAT Parameter Parameter ID Setting Notes
Name
voltage
algorithm
switch
Table 6-2 Parameters used for activation of RF module regular time sleep mode (FDD)
Parameter Parameter ID Setting Notes
Name
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME. For
detailed operations, see CME-based Feature Configuration.
For NB-IoT, this function can be batch activated on the CME. For detailed operations, see the
following section in the CME product documentation or online help: CME Management >
CME Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
6.4.2 Activation Verification
1. Run the LST CELLALGOSWITCH command to verify that the Dynamic adjust voltage
algorithm switch parameter value is DynAdjVoltSwitch:On.
2. Check the number of users by performing a Users Statistic Monitoring task on the U2020.
Ensure that there are no RRC_CONNECTED UEs in the cell for 10 minutes.
3. Run the DSP CELL command to verify that the Cell power save state parameter value is
CELL_PWRSAVE_DYNADJVOLT.
1. Run the LST ENODEBAUTOPOWEROFF command to verify that the RF module sleep
switch parameter value is On.
2. Run the DSP TIME command to check whether the eNodeB has entered the power-off
period.
If it has, go to 3.
If it has not, wait till the specified time arrives.
3. One minute later, run the DSP ENODEBAUTOPOWEROFF command to verify that the
RF module sleep status parameter value is POWER_OFF.
4. Run the DSP TXBRANCH command to query the status of the TX channels. This function
is activated when the TX channels of all RF modules are disabled.
6.4.3 Network Monitoring
Compare the eNodeB power consumption data on the live network from one week before and
one week after a function is enabled to assess its energy saving gains.
To monitor and evaluate the performance of this function, operators can view the following data
on the U2020:
VS.EnergyCons.BTS.Adding.LTE: power consumption of a macro eNodeB
When there is no traffic in a cell, if the eNodeB power consumption drops significantly after this
function is activated, dynamic voltage adjustment is delivering the expected performance.
Otherwise, dynamic voltage adjustment is underperforming.
7.1 Principles
When the eNodeB reports a power insufficiency or power failure alarm, or user intervention is
involved, cells enter the low power consumption mode to reduce the power consumption of the
RF modules and prolong the service time of the eNodeB. This function is controlled by the
CellLowPower.LowPwrSwitch parameter.
When there is a centralized power supply, all cells with this parameter set to ON will enter the
low power consumption mode. When the power supply is distributed, only cells that are
experiencing power failures on their RF modules and have the preceding parameter set to ON
will enter this mode.
uses the BTS3900 DC (–48 V) cabinet as an example to illustrate a centralized power
Figure 7-1
supply scenario.
Figure 7-1 Centralized power supply scenario
A centralized power supply scenario is when main eNodeB components (the BBU and RFUs/RRUs) use the
same power supply system and backup power supply system. If the AC power supply becomes unavailable, the
same backup power supply system provides power for all RFUs/RRUs and BBU. The power alarms are
consistent if any.
A distributed power supply scenario is when main eNodeB components (the BBU and RFUs/RRUs) use multiple
power supply systems and backup power supply systems. If the AC power supply becomes unavailable for some
devices, the corresponding backup power supply systems provide power for these devices, but the power supply
systems of other devices remain unchanged. The power alarms may be inconsistent for different devices.
7.1.1 Triggering
An eNodeB can enter the low power consumption mode automatically or manually:
Automatically
The eNodeB enters the low power consumption mode if ALM-25622 Mains Input Out of
Range or a user-defined mains supply outage alarm is reported during a period specified by
the CellLowPower.StartTime and CellLowPower.StopTime parameters. To enable the eNodeB
to detect user-defined alarms, specify the following parameters:
MAINSALARMBIND.ISDSWITCH, MAINSALARMBIND.NMSACN,
MAINSALARMBIND.NMSASRN, MAINSALARMBIND.NMSASN, and
MAINSALARMBIND.NMSAPN.
Manually
The eNodeB can be manually made to enter the low power consumption mode by setting the
CellLowPower.LowPwrOrder parameter is set to ON. If this parameter is set to ON, the cell
enters the low power consumption mode regardless of whether the system time is within the
specified time period or whether any relevant alarms are reported.
7.1.2 eNodeB Actions
When the low power consumption mode is triggered, the eNodeB does not enter this mode
immediately. Instead, it continues working normally for a transitional period specified by the
CellLowPower.EnterTimeLen parameter. The eNodeB monitors ALM-25622 Mains Input Out of
Range, user-defined mains supply outage alarms, and any possible user intervention during this
period.
If the related alarm is cleared, or the user cancels manual intervention within this period, the
eNodeB exits the low power consumption mode.
If the related alarm persists or manual intervention continues within the transitional period,
the eNodeB will take further actions (shown in Figure 7-2) in sequence at the end of this period.
The eNodeB may take some or all of the actions until the conditions for exiting the low power
consumption mode are met.
Figure 7-2 eNodeB actions taken in low power consumption mode
The periods for lowering the transmit power for services in the cells, lowering the transmit power
for reference signals, and shutting down some transmit channels can be customized by users or
predefined by the eNodeB, according to the setting of the CellLowPower.BakPwrSavPolicy
parameter.
When the CellLowPower.BakPwrSavPolicy parameter is set to CUSTOMIZED, users can use
the CellLowPower.CellUsedPwrReduceTimeLen, CellLowPower.RsPwrReduceTimeLen, and
CellLowPower.RfShutDownTimeLen parameters to set these periods.
When the CellLowPower.BakPwrSavPolicy parameter is set to POLICY1, POLICY2, or
POLICY3, the periods are predefined by the eNodeB and not configurable. For example,
when the CellLowPower.BakPwrSavPolicy parameter is set to POLICY2, each of the periods
lasts 120 minutes.
The length of time the reference signal transmit power is lowered for can be specified by the
CellLowPower.RsPwrReduceTimeLen parameter. The decrease in the reference signal power can
be specified by the CellLowPower.RsPwrAdjOffset parameter.
During this stage, the eNodeB lowers the transmit power of the traffic channels and reference
signals simultaneously.
When the period for lowering the power of reference signals expires, the eNodeB shuts down
some of the transmit channels too.
The eNodeB lowers the transmit power of the traffic channels and reference signals and shuts
down some transmit channels. The eNodeB shuts down the transmit channels using a method
similar to RF channel intelligent shutdown. For details, see 5.1.2 eNodeB Actions.
The length of time the transmit channels are shut down for is specified by the
CellLowPower.RfShutDownTimeLen parameter.
The differences between shutting down some transmit channels in this case and RF channel
intelligent shutdown are as follows:
Shutting down some transmit channels does not take the UEs in the cell and load of the cell
into consideration. The transmit channels will be shut down even if there are UEs in the cell.
After the channels are shut down, the transmit power of other channels in the cell does not
increase.
When the shutdown period (specified by CellLowPower.RfShutDownTimeLen) expires, the
eNodeB also shuts down the carrier.
The condition for exiting low power consumption mode depends on whether the eNodeB enters
this mode automatically or forcibly:
If the eNodeB automatically enters the low power consumption mode due to an alarm, the
eNodeB exits this mode when any of the following conditions is met:
The CellLowPower.LowPwrSwitch parameter is set to OFF.
The period configured for the low power consumption mode elapses. This period is
specified by the CellLowPower.StartTime and CellLowPower.StopTime parameters.
The alarm that caused the eNodeB to enter the low power consumption mode is cleared.
If the eNodeB forcibly enters the low power consumption mode, the eNodeB exits this mode
when either of the following conditions is met:
The CellLowPower.LowPwrOrder parameter is set to OFF.
The CellLowPower.LowPwrSwitch parameter is set to OFF.
7.2 Network Analysis
7.2.1 Benefits
Low power consumption mode is recommended when the mains supply is unstable in centralized
power supply scenarios.
Power saving efficiency may decrease when two modes share the same PA. This is because the
PA can be shut down only when carriers for both modes are powered off. For example, if the
GSM and LTE modes use the same PA, the PA cannot be shut down if the LTE carrier is
powered off but the GSM carrier is not.
7.2.2 Impacts
Network Impacts
This feature has a negative impact on system capacity. If the carrier of a cell is shut down, it
cannot provide services.
This function enables an eNodeB to automatically enter the low power consumption mode when
ALM-25622 Mains Input Out of Range or a user-defined mains supply outage alarm is
generated, prolonging the eNodeB service time and the duration that the eNodeB is maintainable.
With this function, the transmit power of a cell may be lowered, or the cell may become
unavailable, affecting system capacity and network performance.
Function Impacts
performs
operations as
described in
Lowering
Transmit Power
for Services in the
Cells, services
are scheduled
based on the
configured
maximum
transmit power
for services.
the conditions
for entering
the low power
consumption
mode, the cell
enters the low
power
consumption
mode only
after exiting
the intelligent
power-off of
carriers in the
same
coverage
mode.
If any co-
coverage
neighboring
basic cell of a
capacity cell is
in the low
power
consumption
mode, the
capacity cell
does not enter
the intelligent
power-off of
carriers in the
same
coverage
mode.
FDD CRS port AutoRecfgSwitch parameter in the STR MIMO In low power
mapping CRSPORTOPTDET command consumption
RAT Function Name Function Switch Reference Description
7.3 Requirements
7.3.1 Licenses
7.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.
Prerequisite Functions
None
7.3.3 Hardware
For FDD, the following base stations are compatible with this function:
3900 and 5900 series base stations
BTS3911E
For TDD, 3900 and 5900 series base stations are compatible with this function.
Boards
None
RF Modules
None
7.4 Operation and Maintenance
For an FDD SFN cell, the entering and exiting of the low power consumption mode are triggered on a physical cell
basis in a distributed power supply scenario only when both the Cell used power reduce time length and
Reference signal power reduce time length parameters are set to 0.
If the power equipment for the eNodeB is not provided by Huawei, you must bind a user-defined
mains supply outage alarm to a specified port, as shown in Table 7-2.
Table 7-2 Parameters used for activation
RAT Parameter Parameter ID Setting Notes
Name
In distributed power supply scenarios in FDD, you must configure the power supply
relationships between RF units and power modules, as described in Table 7-3.
Table 7-3 Parameters used for activation
RAT Parameter Name Parameter ID Setting Notes
If the RRU.PSGID value is inconsistent with the actual power supply relationships in FDD, triggering the low
power consumption mode may cause the RRUs or RFUs whose power supply is normal to enter this mode. In such a
case, the capacity of the corresponding cell may degrade, or this cell may be shut down and become unavailable.
(Optional, required in distributed power supply scenarios) Configuring the power supply group
ID
MOD RRU: CN=0, SRN=60, SN=1, PSGID=1;
(Optional) Configuring a customized mains supply outage alarm for dry contacts
SET ALMPORT: CN=0, SRN=60, SN=1, PN=0, SW=ON, AID=65033, PT=BOOL, AVOL=LOW;
(Optional) Modifying the port binding relationship for the mains supply outage alarm
MOD NMSABIND: ISDSWITCH=ENABLE, NMSACN=0,NMSASRN=60, NMSASN=1, NMSAPN=0;
An eNodeB processes alarms reported by a dry contact port only after the eNodeB is bound to the dry contact port.
A user-defined dry contact port is specified by running the SET ALMPORT command. The name, severity, and
type of the alarm reported by the user-defined dry contact are specified by running the SET ENVALMPARA
command.
In the distributed power supply scenario, there are multiple user-defined dry contacts that can be used to report the
mains supply outage alarm. In this case, specify the same alarm ID for all dry-contact ports that are used to report
the mains supply outage alarm when using the SET ALMPORT command to configure dry-contact ports.
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME. For
detailed operations, see CME-based Feature Configuration.
For TDD, this function can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME product
documentation or online help: CME Management > CME Guidelines > Enhanced Feature
Management > Feature Operation and Maintenance.
7.4.2 Activation Verification
Entering the Low Power Consumption Mode Because of Abnormal Mains Supply
1. Run the LST CELLLOWPOWER command to verify that the value of the Low power
consumption mode switch parameter is On and the value of the Low power consumption
mode order parameter is Off, and to verify Start time and Stop time.
2. Run the DSP TIME command to verify that the eNodeB system time falls within the period
specified by the Start time and Stop time parameters.
3. Use storage batteries instead of AC power to provide power for the eNodeB. Verify that
ALM-25622 Mains Input Out of Range or the user-defined mains supply outage alarm has
been reported.
4. After the transitional period, run the DSP CELL command repeatedly at intervals specified
by time length parameters configured in 7.1.2 eNodeB Actions. Then, view the value of the Cell
power save state parameter each time. Low power consumption mode has been activated if
the following values are displayed in sequence:
CELL_PWRSAVE_LOWPWR_CELLUSEDPWRRDU
CELL_PWRSAVE_LOWPWR_RSPWRRDU
CELL_PWRSAVE_LOWPWR_RFSHD
CELL_PWRSAVE_LOWPWR_CELLSHD
In distributed power supply scenarios, if some of the physical cells serving an SFN cell
experience abnormal RRU or RFU power supply, the SFN cell enters the state of
CELL_PWRSAVE_LOWPWR_PHYCELLSHD.
Forcibly Entering the Low Power Consumption Mode
1. Run the LST CELLLOWPOWER command to verify that the value of the Low power
consumption mode switch parameter is On and the value of the Low power consumption
mode order parameter is On.
2. After the transitional period, run the DSP CELL command repeatedly at intervals specified
by time length parameters configured in 7.1.2 eNodeB Actions. Then, view the value of the Cell
power save state parameter each time. Low power consumption mode has been activated if
the following values are displayed in sequence:
CELL_PWRSAVE_LOWPWR_CELLUSEDPWRRDU
CELL_PWRSAVE_LOWPWR_RSPWRRDU
CELL_PWRSAVE_LOWPWR_RFSHD
CELL_PWRSAVE_LOWPWR_CELLSHD
In distributed power supply scenarios, if some of the physical cells serving an SFN cell
experience abnormal RRU or RFU power supply, the SFN cell enters the state of
CELL_PWRSAVE_LOWPWR_PHYCELLSHD.
7.4.3 Network Monitoring
Benefit Monitoring
To monitor and evaluate the performance of this function, operators can view the following data
on the U2020:
eNodeB power consumption
To monitor eNodeB power consumption, operators can check the value of the
VS.EnergyCons.BTS.Adding.LTE counter on the U2020. For the meaning of this counter, see
Performance Counter Reference of eNodeBs.
Operators can evaluate the performance of the low power consumption mode by comparing
the power consumed by an eNodeB before and after this function is enabled. The decrease in
eNodeB power consumption indicates how much energy is saved.
Duration of cell unavailability due to energy saving
To monitor the duration of cell unavailability due to energy saving in FDD, operators can
check the value of the L.Cell.Unavail.Dur.EnergySaving counter on the U2020. For the meaning of
this counter, see Performance Counter Reference of eNodeBs.
Compare the eNodeB power consumption data on the live network from one week before and
one week after the function is enabled to assess the energy saving gains.
Possible Issues
8.1 Principles
Power consumption monitoring enables the eNodeB to periodically report its power consumption
counters to the U2020. Figure 8-1 illustrates how it works.
Figure 8-1 Power consumption monitoring operational principles
Power consumption monitoring can be used to collect the overall power consumption of the
entire eNodeB, as well as the separate power consumption of the BBU and RF modules.
FDD micro eNodeBs monitor their own power consumption and report the statistics to the
U2020. However, as micro eNodeBs are integrated, they can report their overall power
consumption but not separate statistics for BBUs and RF modules.
Macro and LampSite eNodeBs perform accumulative measurements differently:
For macro eNodeBs, each RF module reports its power consumption to the BBU. The BBU
then adds up the total power consumption of RF modules, electromechanical components, and
the BBU, and reports the total to the U2020.
The RF modules used by LampSite eNodeBs are either pRRUs or RRUs. pRRUs cannot
measure their own power consumption. Therefore, the RHUB adds its own power
consumption to the total power consumption of the cascaded pRRUs (there may be one to
eight pRRUs) and reports the total result to the BBU. RRUs can measure and report their own
power consumption to the BBU. The BBU then adds its own power consumption to the total
power consumption reported by the RRUs and RHUBs, and reports the total result to the
U2020.
The power consumption statistics of the entire eNodeB can be obtained through cumulative or
PMU-assisted measurements. Neither method requires parameter configuration or engineering
deployment.
Cumulative measurement
The eNodeB periodically measures the power consumption of its components, such as the
BBU, RF modules, and fans. It adds the values together, and reports the total power
consumption to the U2020.
If a component uses a digital power supply or is capable of software-based power
consumption measurement, the component reports its own measured power consumption to
the BBU. If a component does not use a digital power supply or is incapable of software-
based power consumption measurement, the BBU finds the power consumption value of that
component from the power consumption table.
For LampSite eNodeBs configured with pRRUs, the RHUB measures pRRU power
consumption and reports the pRRU and RHUB power consumption to the BBU because
pRRUs are not capable of power consumption measurement. For LampSite eNodeBs
configured with RRUs, the RRUs and RHUB separately measure and report their own power
consumption to the BBU. The BBU then reports the total power consumption of the RRUs,
RHUB, and BBU to the U2020.
The VS.EnergyCons.BTS.Adding.LTE counter on the U2020 indicates the total power
consumption of the base station, which is the accumulated rated power consumptions of all
boards in the base station.
The VS.EnergyCons.BTS.Adding.LTE counter indicates the total power consumption of all LTE-
related components, including LTE-related boards in the BBU, RF modules configured with
LTE carriers, and fans.
For an LTE-only base station, this counter measures the power consumption of the entire
base station.
For a multimode base station supporting LTE, this counter measures the power
consumption of the LTE part. It does not accurately reflect LTE power consumption. The
information provided is for reference only. You are advised to use the power consumption
counter for the entire multimode base station.
PMU-assisted measurement
If the eNodeB is equipped with a power monitoring unit (PMU), the eNodeB uses the PMU to
monitor the total PSU power consumption of the BBU, RF modules, fans, and other modules.
The eNodeB reports the total power consumption to the U2020.
An eNodeB can report either AC or DC power consumption. The energy consumption
measurement point (specified by the ENERGYCON.MP parameter) controls whether the
eNodeB reports AC or DC power consumption.
If AC power consumption needs to be reported, the total power consumption is the amount
of power consumed before AC power is converted into DC power.
If DC power consumption needs to be reported, the total power consumption is the amount
of power consumed after AC power is converted into DC power.
The VS.EnergyCons.BTS.Measuring.LTE counter on the U2020 measures the power consumption
of the base station. The counter value is calculated by the power system based on the detected
current and voltage.
When the energy consumption measurement point is set to DC:
In an LTE-only base station, this counter measures the output power of PSUs.
In a multimode base station supporting LTE, this counter only measures part of the
output power of PSUs. For example, in dual-mode scenarios, the value of this counter is
half of the total output power of PSUs.
When the energy consumption measurement point is set to AC:
In an LTE-only base station, this counter measures the input power of PSUs.
In a multimode base station supporting LTE, this counter only measures part of the
input power of PSUs. For example, in dual-mode scenarios, the value of this counter is
half of the total input power of PSUs.
The base station can measure the power consumption of the BBU and RF modules and report the
statistics to the U2020.
The VS.EnergyCons.BU counter indicates the power consumption of all boards in a BBU. This
counter does not distinguish between RATs. When different RATs are configured in the same
BBU in a multimode base station, the counter value equals the total power consumption of the
entire BBU. If a separate-MPT BBU is used in a multimode base station, the MPT of each
RAT reports the same VS.EnergyCons.BU counter value.
The VS.EnergyCons.BTSBoard counter indicates the power consumption of RF modules. This
counter does not distinguish between RATs. When different RATs share RF modules in a
multimode base station, the counter value equals the total power consumption of the RF
modules. If a separate-MPT BBU is used in a multimode base station, the MPT of each RAT
reports the same VS.EnergyCons.BTSBoard counter value.
8.2 Network Analysis
8.2.1 Benefits
None
8.3 Requirements
8.3.1 Licenses
None
8.3.2 Software
Prerequisite Functions
None
None
8.3.3 Hardware
For FDD, all base station models are compatible with this function.
For NB-IoT, the following base stations are compatible with this function:
3900 and 5900 series base stations
DBS3900 LampSite and DBS5900 LampSite
BTS3911E
BTS3912E
For TDD, the following base stations are compatible with this function:
3900 and 5900 series base stations
DBS3900 LampSite and DBS5900 LampSite
Boards
All models of the UPEU board except for the UPEUa and UPEUb support power consumption
monitoring.
RF Modules
The eNodeB is correctly connected to the U2020 and the PowerSavingStatistic module is
enabled on the U2020.
describes the hardware and software requirements for the PMU when PMU-assisted
Table 8-1
measurement is used.
Table 8-1 Requirements for the PMU when PMU-assisted measurement is used
Power Supply System PMU Model PMU Software Version
Perform the operations listed below only when the eNodeB is equipped with a PMU. If the
eNodeB does not have a PMU, these steps are not required.
1. On the U2020 client, select the eNodeB and run the DSP BRDVER command to check
whether the PMU software version is 138 or later.
2. If the software version of the PMU is earlier than 138, run the ACT SOFTWARE command
to activate the PMU software.
3. Run the SET ECMP command to set the Energy Consumption Measurement Point
parameter to DC or AC based on site requirements.
8.4 Operation and Maintenance
Power consumption data can be obtained on the U2020 without any configuration on the
eNodeB. This function is disabled on the U2020 by default. You can refer to U2020 OSMU User
Guide to learn how to enable this function. If valid power consumption data can be obtained on
the U2020, then this function has taken effect.
For instructions on operations on the U2020, navigate to the corresponding section in U2020
MBB Network Management System Product Documentation as follows: RAN Management >
SON Management > Base Station Energy Conservation Management > Collecting and
Analyzing Statistics on Base Station Energy Consumption
8.4.1.2 Using MML Commands
N/A
8.4.2 Activation Verification
The following table describes the counters for eNodeB power consumption on the U2020.
Table 8-2 Counters for eNodeB power consumption
Counter ID Counter Name Counter Description
For an LTE-only base station, select eNodeB under LTE. For a multimode base station, select Multi-Mode
BTS under SRAN.
4. Check the eNodeB traffic volume and power consumption. (In this example, the power
consumption is calculated using the cumulative method.)
5. Click to convert the data obtained in 4 into a line graph or bar graph to view the traffic
volume and power consumption.
1. Log in to the U2020 and choose SON > Power Saving > Power Saving Statistic.
2. Double-click Energy Saving Data Subscription. In the displayed dialog box, select the NE
to observe, and click OK. Wait six hours for the U2020 to collect the information about the
eNodeB. Double-click BS Traffic and Energy Consumption Comparison.
3. Select an NE and specify different periods with the same duration.
For an LTE-only base station, select eNodeB under LTE. For a multimode base station, select Multi-Mode
BTS under SRAN.
4. Check the eNodeB traffic volume and power consumption for different periods. (In this
example, the power consumption is calculated using the cumulative method.)
5. Click to convert the data into a line graph to view the eNodeB traffic volume and power
consumption.
8.4.3 Network Monitoring
None
9.1 Principles
Macro, micro, and LampSite eNodeBs all support intelligent power-off of carriers in the same
coverage. The following lists the supported networking:
Macro-macro networking
LampSite networking
Macro-LampSite networking
Macro-micro networking
The following sections describe related concepts, as well as the triggering, execution, and
leaving of this function.
9.1.1 Related Concepts
Capacity Cell
When comparing the total uplink or downlink PRB usage of the capacity cell and basic cell with the entering
threshold, the eNodeB performs conversion on the cell bandwidth.
When the conditions for triggering intelligent power-off of carriers in the same coverage are met,
the eNodeB follows the process shown in Figure 9-3.
Figure 9-3 Procedure for intelligent power-off of carriers in the same coverage
When a capacity cell is shut down, only the corresponding carrier is powered off. The capacity cell is not
deactivated, and its baseband resources cannot be preempted. This ensures that the capacity cell can rapidly exit the
power-off state once the leaving conditions are met. When a capacity cell is shut down, its scheduling-related
performance counters are still measured.
9.1.4 Leaving
The capacity cell exits the intelligent power-off of carriers in the same coverage state and its co-
coverage neighboring basic cells are powered on again when any of the following conditions is
met:
The period for intelligent power-off of carriers in the same coverage has elapsed. This period
is determined by the CellShutdown.StartTime and CellShutdown.StopTime parameters.
The capacity cell restarts up.
The uplink PRB usage of a co-coverage neighboring basic cell is higher than the uplink PRB
usage threshold for exiting the intelligent power-off of carriers in the same coverage mode of
the capacity cell. The threshold is equal to CellShutdown.UlPrbThd plus
CellShutdown.UlPrbOffset.
The downlink PRB usage of a co-coverage neighboring basic cell is higher than the downlink
PRB usage threshold for exiting the intelligent power-off of carriers in the same coverage
mode of the capacity cell. The threshold is equal to CellShutdown.DlPrbThd plus
CellShutdown.DlPrbOffset.
One of the co-coverage neighboring basic cells is not available.
A co-coverage neighboring basic cell is added, deleted, or modified.
To prevent the impact on MLB features, the uplink and downlink PRB usage thresholds for
exiting intelligent power-off of carriers in the same coverage mode for the cell must be lower
than the threshold for triggering inter-frequency MLB. The threshold for triggering inter-
frequency MLB equals the sum of the values of the CellMLB.InterFreqMlbThd and
CellMLB.LoadOffset parameters.
9.2 Network Analysis
9.2.1 Benefits
Intelligent power-off of carriers in the same coverage is recommended in off-peak hours at night
if the eNodeB is configured with at least two frequencies.
Power saving efficiency may decrease when a capacity cell is served by an RF module where
multiple carriers share the same PA. This is because the PA can only be shut down when all the
carriers are powered off. For example, if a capacity cell is served by a GL dual-mode RF module
that provides the same PA for both GSM and LTE carriers, the PA cannot be shut down after the
LTE carrier is powered off but the GSM carrier is not.
To prevent energy saving–triggered shutdown from affecting the lifespan of RF modules, the RF
modules may exit the energy saving state when their own temperature differential exceeds a
specified threshold within 24 hours. Energy saving gains decrease in this case.
9.2.2 Impacts
Network Impacts
When network load is less than a certain threshold, this function enables the eNodeB to power
off some cells to save power. Each time a cell is powered off, total network capacity reduces by
an amount equal to the capacity of the cell powered off. Therefore, this function should be used
only when network load is light.
When intelligent power-off of carriers in the same coverage is in effect, UEs in a capacity cell
are handed over to a basic cell, causing increases in the values of the counters listed in Table 9-1
and Table 9-2.
To promptly decrease the number of UEs in the capacity cell, the eNodeB prohibits new UEs
from accessing the capacity cell and broadcasts the barred state of the capacity cell through
SIB1. However, a small number of UEs may still send RRC connection setup requests to access
the network, causing an increase in the L.RRC.SetupFail.Rej counter and a decrease in RRC Setup
Success Rate. The number of such access failures is also indicated by the
L.RRC.SetupFail.ResFail.CellBarred counter.
When MLB is triggered in a basic cell and the HoAdmitSwitch option of the
CellMlbHo.MlbMatchOtherFeatureMode parameter is selected, the basic cell rejects
incoming handover requests of UEs from the capacity cell. As a result, the handover success rate
decreases. To address this issue, the CarrierShutdownHoAdmitAllowSw option of the
CellMlbHo.MlbMatchOtherFeatureMode parameter needs to be selected in the basic cell so that the
basic cell where MLB is triggered permits incoming UE handovers from the capacity cell.
Function Impacts
FDD RAN sharing RAN sharing with common carrier: RAN Sharing In RAN sharing scenari
TDD ENodeBSharingMode.ENodeBSharingMode PLMN IDs of a capacity
parameter with the value of SHARED_FREQ be a subset of the PLM
RAN sharing with dedicated carrier: its co-coverage neighbo
basic cell. Otherwise, th
RAT Function Name Function Switch Reference Description
FDD Work mode Cell.Workmode None For FDD, a cell with the
TDD Cell.Workmode paramet
DL_ONLY or LAA cann
configured as a basic c
For TDD, a cell with the
Cell.Workmode paramet
LAA cannot be configur
basic cell.
FDD CRS port AutoRecfgSwitch parameter in the STR MIMO In intelligent power-off o
mapping CRSPORTOPTDET command in the same coverage m
detection and CRS port mapping dete
reconfiguration reconfiguration are not
supported. If the conditi
entering intelligent powe
carriers in the same cov
mode are met in a cell
undergoing CRS port m
detection, the cell will e
intelligent power-off of c
the same coverage mod
the detection will be inte
9.3 Requirements
9.3.1 Licenses
9.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.
Prerequisite Functions
No requirements
Boards
The LMPT does not support inter-BBU intelligent carrier power-off for macro cells.
The BBU3910C does not support inter-BBU intelligent carrier power-off.
RF Modules
This feature can be used in both LTE-only and multimode RF-sharing scenarios.
9.3.4 Networking
To ensure QoS during service migration, this function can be used only in the following
scenarios:
On a HetNet network where the macro eNodeB provides the basic cell to ensure basic
network coverage. Micro eNodeBs provide the capacity cells and are deployed in hotspots
across the basic cell coverage. The basic cell is configured as an inter-frequency co-coverage
neighboring cell of the capacity cells.
In LTE FDD and LTE TDD co-MPT scenarios where macro and LampSite eNodeBs allow
basic and capacity cells to work in different modes (TDD and FDD). For example, there could
be an FDD cell being used as a basic cell and a TDD cell as a capacity cell.
9.3.5 Others
All UEs in capacity cells must support the working frequency band of basic cells.
9.4 Operation and Maintenance
Table 9-4 describes the parameters that must be set to configure inter-frequency EARFCNs.
For details, see inter-frequency EARFCN configuration in Mobility Management in Connected Mode.
Table 9-5 describes the parameters that must be set to configure inter-frequency neighboring cells.
For details, see inter-frequency neighboring cell configuration in Mobility Management in Connected Mode.
Table 9-6describes parameters related to external cells that must be set in the inter-BBU
intelligent carrier power-off scenario.
Table 9-6 Parameters used for activation
RAT Parameter Parameter ID Setting Notes
Name
Inter-BBU intelligent power-off of carriers in the same coverage must be enabled on both the local and neighboring
eNodeBs for it to take effect.
In inter-BBU carrier power-off scenarios, the Globalprocswitch.X2ServedCellType parameter needs to be set to
CONFIGURED_CELL. This enables the capacity cell to exit the carrier power-off mode when the co-coverage
neighboring basic cell served by a neighboring eNodeB is deactivated.
When configuring a basic cell, note the following:
In inter-eNodeB SFN based on eNodeB coordination, it is not recommended that a cell in standby mode be
configured as a basic cell.
For FDD:
A cell with the Cell.Workmode parameter set to DL_ONLY or LAA cannot be configured as a basic cell.
A cell with the ForbidCellSiSwitch option of the Cellsimap.SiSwitch parameter selected cannot be
configured as a basic cell.
For TDD, a cell with the Cell.Workmode parameter set to LAA cannot be configured as a basic cell.
An eMTC-only cell cannot be configured as a basic cell.
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME. For
detailed operations, see CME-based Feature Configuration.
For TDD, this function can be batch activated using the Feature Operation and Maintenance
function of the CME. For detailed operations, see the following section in the CME product
documentation or online help: CME Management > CME Guidelines > Enhanced Feature
Management > Feature Operation and Maintenance.
9.4.2 Activation Verification
1. Run the DSP CELL command to check the value of the Cell power save state parameter. If
it is CELL_PWRSAVE_CARRIERPWROFF, intelligent power-off of carriers in the
same coverage has taken effect.
2. (Optional) If intelligent power-off of carriers in the same coverage does not take effect, run
the DSP CELLSHUTDOWN command to query the current status of carrier power-off and
the cause why it has not taken effect.
9.4.3 Network Monitoring
Benefit Monitoring
To monitor and evaluate the performance of this function, operators can view the following data
on the U2020:
eNodeB power consumption
You can query the VS.EnergyCons.BTS.Adding.LTE counter value on the U2020 before and after
the function activation to observe the power consumption changes of macro, micro, or
LampSite eNodeBs.
Duration when a cell is in the intelligent power-off of carriers in the same coverage or
intelligent power-off of carriers in the same coverage as UMTS networks state
You can check the L.ChMeas.DFEE.CarrierOFF.Dur counter value to learn how long the cell has
been in this state. For the meaning of this counter, see Performance Counter Reference of
eNodeBs.
Duration of cell unavailability due to energy saving
You can check the L.Cell.Unavail.Dur.EnergySaving counter value to observe how long the cell
has been unavailable.
The measurement periods of the L.ChMeas.DFEE.CarrierOFF.Dur and L.Cell.Unavail.Dur.EnergySaving
counters are different. Therefore, the values of the two counters have a maximum deviation of 5
seconds.
Compare the eNodeB power consumption data on the live network from one week before and
one week after the function is enabled to assess the energy saving gains.
Possible Issues
When a cell cannot enter the intelligent power-off of carriers in the same coverage mode as
expected, perform the following actions:
1. Verify that inter-frequency neighboring cells served by the same eNodeB as the local cell are
configured correctly. For details about how to configure inter-frequency neighboring cells,
see Mobility Management in Connected Mode.
2. Run the LST CELLSHUTDOWN command to verify that the Intelligent power-off of
carriers switch parameter is set to On for the two cells and that there are more than 5
minutes between the values of Start time and Stop time. You are advised to set the duration
to a value greater than 5 minutes. If not, the conditions for starting intelligent power-off of
carriers in the same coverage cannot all be checked before the stop time arrives, and the cell
cannot enter intelligent power-off mode.
3. Run the DSP TIME command to verify that the eNodeB system time falls within the period
of intelligent power-off of carriers in the same coverage.
4. Verify that the UEs support different frequencies.
5. On the U2020, choose Monitor > Signaling Trace > Signaling Trace Management. In the
navigation tree on the left of the displayed Signaling Trace Management window, choose
Trace Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring. Verify
that the average uplink and downlink PRB usages of the E-UTRAN cell and its inter-
frequency neighboring cells are less than the uplink and downlink PRB usage thresholds for
starting intelligent power-off of carriers in the same coverage, respectively.
10.1 Principles
PSU intelligent sleep mode enables an eNodeB equipped with AC/DC PSUs to shut down a
certain number of PSUs when system load is light. This function helps prolong PSU lifetime and
reduce power consumption. Figure 10-1 illustrates how it works. This function is controlled by the
PSUIS.PSUISS parameter.
Figure 10-1 PSU intelligent sleep mode operating principles
The PSU and PMU are the power supply and power monitoring units. The following describes
details about the PSU and PMU.
A PSU converts 110 V AC or 220 V AC power into –48 V DC power.
Generally, each AC-powered eNodeB is configured with multiple PSUs. The number of PSUs
required is determined based on the maximum power consumption of the eNodeB. This
ensures that the eNodeB operates properly, even when fully loaded. The eNodeB, however,
seldom operates at its full load. As a result, each PSU in the eNodeB usually works at partial
output power. Since the efficiency at which a PSU converts power is directly proportional to
its output power, low PSU power conversion efficiency will affect the overall eNodeB power
consumption.
When an eNodeB is configured with multiple PSUs, one or more of them can be shut down
based on the actual load, improving the conversion efficiency of PSUs.
The PSU intelligent sleep mode function reduces power consumption by maintaining high
PSU power conversion efficiency. Power consumption reduction is closely related to the PSU
power conversion efficiency changes before and after PSU intelligent sleep mode is activated.
Assuming that the overall output power of PSUs remains unchanged, and the PSU power
conversion efficiencies before and after the activation of PSU intelligent sleep mode are c0
and c1, respectively. Then the power consumption reduction proportion is (1 – c0/c1). In
addition, PSU shutdown extends the life span of the PSUs.
The PMU monitors the power system, manages batteries, tests power distribution, and reports
alarms, if any, for the eNodeB.
10.1.1 Triggering
The eNodeB enters the PSU intelligent sleep mode if the required number of PSUs is less than
the number of actually working PSUs within a period of 5 minutes.
10.1.2 eNodeB Actions
The eNodeB shuts down a certain number of PSUs based on the actual load.
10.1.3 Leaving
The eNodeB exits the PSU intelligent sleep mode if the PMU determines that the eNodeB
requires more PSUs than those in use.
10.2 Network Analysis
10.2.1 Benefits
PSU intelligent sleep mode is recommended if PSU service life is a major concern for the
operator and there are cabinets configured with a PMU, PSUs, and batteries. Enabling this
function prolongs PSU lifetime and reduces eNodeB power consumption.
10.2.2 Impacts
Network Impacts
This function enables the eNodeB to turn off some PSUs when the eNodeB load is light and to
turn them back on again when the load increases. This function has no impact on network
performance.
Function Impacts
None
10.3 Requirements
10.3.1 Licenses
RAT Feature ID Feature Name Model Sales Unit
10.3.2 Software
Prerequisite Functions
None
None
10.3.3 Hardware
3900 and 5900 series base stations are compatible with this function.
Boards
None
RF Modules
None
10.3.4 Networking
N/A
10.3.5 Others
The cabinet of an eNodeB is configured with a PMU, at least two PSUs, and storage batteries.
If the eNodeB is AC powered, use a Huawei PMU that supports this function to manage the
power system. For details about how to configure the power supply system for an eNodeB,
see the description of power management in eNodeB Initial Configuration Guide.
The PMU hardware and software versions must meet the requirements of the corresponding
power supply systems listed in Table 10-1.
Table 10-1 Requirements of PSU intelligent sleep mode on the PMU
Power Supply System PMU Model PMU Software Version
FDD PSU Intelligent PSUIS.PSUISS You are advised to turn on this switch.
TDD Shutdown Switch
For details about the PMU software upgrade, see Power Supply Management.
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME. For
detailed operations, see CME-based Feature Configuration.
For NB-IoT, this function can be batch activated on the CME. For detailed operations, see the
following section in the CME product documentation or online help: CME Management >
CME Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
10.4.2 Activation Verification
1. Run the DSP BATTERY command to verify that the status of the storage batteries is
normal.
2. Run the DSP PSU command to verify that at least two PSUs are configured and that the
value of the Running Status parameter for each PSU is Normal.
3. Run the LST PSUISS command to verify that the value of the PSU Intelligent Shutdown
Switch parameter is Enable.
4. Run the DSP PMU command to verify that the value of the PSU Intelligent Shutdown
Switch parameter is Enable.
5. Check the PSU working status based on its running indicator. If the PSU is not running, this
function has been activated.
10.4.3 Network Monitoring
Performance counters on the U2020 are used to monitor and evaluate the performance of this
function.
Compare the eNodeB power consumption data on the live network from one week before and
one week after the function is enabled to assess the energy saving gains.
How long the PSU intelligent sleep mode has been in effect
You can query the VS.PSU.ShutdownTime counter value on the U2020 to observe how long the
PSU intelligent sleep mode has been in effect. For the meaning of this counter, see
Performance Counter Reference of eNodeBs.
If the value of this counter is not 0, PSU intelligent sleep mode has taken effect. Assuming
that N is the number of PSUs, which is greater than or equal to 1. If the value of this
counter is greater than the measurement period multiplied by N–1 and less than or equal to
the measurement period multiplied by N, N PSUs are shut down.
If the value of this counter is 0, PSU intelligent sleep mode has not taken effect.
Input power of PSUs
To monitor the input power of PSUs, you can run the SET ECMP command with the Energy
Consumption Measurement Point parameter set to AC and then check the value of the
VS.EnergyCons.BTS.Measuring.LTE counter on the U2020. For the meaning of this counter, see
Performance Counter Reference of eNodeBs.
In LTE-only scenarios, the value of the counter shows the input power of the PSUs.
In multi-mode scenarios, this counter value must be added to the values of the counters
used for other RATs to find the input power of the PSUs.
Output power of PSUs
To monitor the output power of the PSUs, you can check the value of the
VS.EnergyCons.BTS.Adding.LTE counter on the U2020.
In LTE-only scenarios, the value of the counter shows the output power of the PSUs.
In multi-mode scenarios, this counter value must be added to the values of the counters
used for other RATs to find the output power of the PSUs.
If the output power of the PSUs remains unchanged, a larger input power decrease leads to
larger function performance gains. If the input power of the PSUs remains unchanged, a
larger output power decrease leads to larger function performance gains.
11.1 Principles
Symbol power saving enables the eNodeB to turn off PAs when symbols are empty. This reduces
the system power consumption.
There are two types of symbol power saving: basic and enhanced. They are shown in Figure 11-1.
Figure 11-1 Operating principles for basic and enhanced symbol power saving
Symbol power saving can be used in both LTE only and multimode RF-sharing scenarios. In a
multimode RF-sharing scenario, symbol power saving takes effect only when LTE carriers are
active and all the other carriers are in the power-off state.
In multi-RRU cells, symbol power saving is performed on a per physical RRU basis. If some
RRUs in a cell cannot enter the symbol power saving state, any other RRUs meeting the
triggering conditions can still enter this state.
11.1.1 Basic Symbol Power Saving
For each cell, the eNodeB checks in real time whether each symbol within a subframe contains
data to transmit and shuts down PAs during the symbol periods with no data to transmit. Figure 11-
2 shows the symbol pattern in a subframe transmitted in a single antenna-port scenario. In this
figure, symbols 1, 2, 3, 5, and 6 in each timeslot do not contain any data to transmit. During
these symbol periods, PAs can be turned off to save power.
Figure 11-2 Symbol pattern in a subframe (example 1)
11.1.1.1 Triggering
Basic symbol power saving is controlled by an eNodeB-level switch. When this switch is turned
on, all cells under the eNodeB enter the basic symbol power saving state.
For FDD and NB-IoT, the switch is controlled by the SymbolShutdownSwitch option of the
ENodeBAlgoSwitch.PowerSaveSwitch parameter. For TDD, the switch is controlled by the
TddSymbolShutdownSwitch option of the ENodeBAlgoSwitch.PowerSaveSwitch parameter.
11.1.1.2 eNodeB Actions
When transmitting service data in the downlink, the eNodeB checks for empty symbols and turns
off PAs for these symbols.
11.1.1.3 Leaving
LTE-only base stations will not exit the basic symbol power saving state after this function takes
effect. In a multimode base station supporting LTE, if an RF module is shared by different RATs
and a non-LTE carrier exits the power saving state, LTE cells of the base station will exit the
basic symbol power saving state.
11.1.2 Enhanced Symbol Power Saving
When enhanced symbol power saving is enabled, some subframes in which no data is
transmitted are configured as Multimedia Broadcast multicast service Single Frequency Network
(MBSFN) subframes so that PAs can be shut down for more symbols. As shown in Figure 11-3,
PAs are enabled only for symbol 0 and symbol 1 for each MBSFN subframe.
Figure 11-3 Symbol pattern in a subframe (example 2)
To implement enhanced symbol power saving, UEs must be capable of identifying and handling
MBSFN subframes. Incapable UEs will not be able to perform channel measurements or run data
services, which greatly affects network KPIs.
Enhanced symbol power saving is controlled by the MBSFNShutDownSwitch option of the
CellAlgoSwitch.DlSchSwitch parameter. This function can take effect only when basic symbol
power saving is enabled.
11.1.2.1 Triggering
If enhanced symbol power saving is enabled for a cell, it enters this state when the PRB usage of
the eNodeB drops below 50%.
11.1.2.2 eNodeB Actions
When transmitting downlink service data, the eNodeB dynamically detects which subframes do
not contain user data and configures these subframes as MBSFN subframes in accordance with
section 7.2.1 of 3GPP TR 36.927. This enables the eNodeB to turn off PAs for more symbols.
11.1.2.3 Leaving
The cells under an eNodeB exit the enhanced symbol power saving state when either of the
following conditions is met:
The downlink PRB usage of the eNodeB is at least 50%.
When an RF module is shared by multiple RATs, a non-LTE carrier exits the power saving
state.
11.2 Network Analysis
11.2.1 Benefits
Enhanced power saving is recommended when all UEs on the LTE network comply with 3GPP
R8 or later. Such UEs can identify and process MBSFN subframes to support this function. The
PAs of RF modules are shut down when symbols are empty, reducing the power consumption.
To prevent energy saving–triggered shutdown from affecting the lifespan of RF modules, the RF
modules may exit the energy saving state when their own temperature differential exceeds a
specified threshold within 24 hours. Energy saving gains decrease in this case.
11.2.2 Impacts
Network Impacts
Basic symbol power saving enables the eNodeB to dynamically check the symbols or subframes
to be transmitted and turn off PAs during empty symbols or subframes. Therefore, it has no
impact on network performance.
Enhanced symbol power saving is configured based on MBSFN subframes, which are not
updated in real time. When the data to be transmitted increases, the number of MBSFN
subframes cannot promptly decrease, causing a delay of approximately 100 seconds before the
transmission rate increases. To implement enhanced symbol power saving in LTE networks, UEs
must be capable of identifying and handling MBSFN subframes. Incapable UEs will not be able
to perform channel measurements or run data services when this function is enabled.
Enhanced symbol power saving enables the base station to schedule downlink subframes in a
centralized manner, decreasing the User Downlink Average Throughput.
Function Impacts
RAT Function Function Switch Reference Des
Name
paramete
to BOOLE
and the
SRSCfg.S
paramete
to SC3, in
the SRS r
configured
the cell an
of the SRS
configurat
enhanced
power sav
immediate
will no lon
state.
Based on
QoS
11.3 Requirements
11.3.1 Licenses
11.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.
Prerequisite Functions
11.3.3 Hardware
3900 and 5900 series base stations are compatible with this function.
Boards
None
RF Modules
For FDD, the following RF modules support symbol power saving: RRU5904w, RRU5309,
RRU5301, RRU5304W, RRU5309W, RRU3221, RRU3240, RRU3249, RRU3260, RRU3262,
RRU3268, RRU3269, RRU3281, RRU3668, RRU3832, RRU3838, RRU3952m, RRU3928,
RRU3929, RRU3938, RRU3939, RRU3942, RRU3952, RRU3952m, RRU3953, RRU3958,
RRU3959, RRU3959a, RRU3959w, RRU3962, RRU3964, RRU3971, RRU3971a, RRU3841,
RRU5905, RRU5909, RRU3832, RRU5301, MRFUc, MRFUd, MRFUdw, AAU3911,
AAU5711, AAU5711a, RRU5901w, RRU5904, RRU5501, RRU5502, RRU5505, RRU5507,
RRU5508, RRU5509t, RRU5903, AAU3920, AAU3940, AAU3961, and AAU5726
For TDD, the following RF modules support symbol power saving: AAU5281, AAU5271,
AAU5613, RRU3236E, AAU5313, RRU3232, RRU3251, RRU3252, RRU3253, RRU3256,
RRU3259, RRU3273, RRU3276, RRU3278, RRU3278u, RRU3279, RRU5251, RRU5258,
AAU5614, and RRU5254
In LTE TDD and 5G dual-mode scenarios, RF modules do not support symbol power saving.
11.3.4 Others
None
11.4 Operation and Maintenance
and Table 11-2 describe the parameters used for activation of basic and enhanced symbol
Table 11-1
power saving.
Table 11-1 Parameters used for activation of basic symbol power saving
RAT Parameter Parameter ID Setting Notes
Name
Table 11-2 Parameters used for activation of enhanced symbol power saving
RAT Parameter Parameter ID Setting Notes
Name
This function can be activated for a single eNodeB or a batch of eNodeBs on the CME. For
detailed operations, see CME-based Feature Configuration.
For NB-IoT, this function can be batch activated on the CME. For detailed operations, see the
following section in the CME product documentation or online help: CME Management >
CME Guidelines > Enhanced Feature Management > Feature Operation and Maintenance.
11.4.2 Activation Verification
1. Run the LST ENODEBALGOSWITCH command. For FDD, verify that the value of the
Power save switch parameter is Symbol shutdown switch:On. For TDD, verify that the
value of the Power save switch parameter is TDD Symbol shutdown switch:On.
2. Run the DSP CELL command and verify that the value of the Symbol shutdown state
parameter is SYMBOL_SHUTDOWN.
3. Run the LST CELLALGOSWITCH command and verify that the value of the DL
schedule switch parameter is MBSFNShutDownSwitch:Off.
Performance counters on the U2020 are used to monitor and evaluate the performance of this
function.
You can query the VS.EnergyCons.BTS.Adding.LTE counter value to observe the power
consumption of an eNodeB.
If the counter value drops significantly after this function is activated, symbol power saving is
delivering the expected performance. If it does not, symbol power saving is underperforming.
Compare the eNodeB power consumption data on the live network from one week before and
one week after the function is enabled to assess the energy saving gains.
12.1 Principles
Intelligent power-off of carriers in the same coverage as UMTS networks enables the eNodeB to
transfer UEs from an E-UTRAN cell to a neighboring UTRAN cell and power off the carrier of
the E-UTRAN cell to save power when the following conditions are met:
The E-UTRAN cell covers the same area as the neighboring UTRAN cell.
The E-UTRAN cell is serving a small number of UEs and is lightly loaded.
Figure 12-1 illustrates how it works.
Figure 12-1 Operating principles for intelligent power-off of carriers in the same coverage as UMTS networks
An E-UTRAN cell that has a co-coverage neighboring UTRAN cell enters the intelligent power-
off of carriers in the same coverage as UMTS networks state only when all of the following
conditions are met:
The InterRatCellShutdown.ShutDownType parameter is set to
BY_UTRAN_WITHOUT_LOAD.
The uplink PRB usage of the E-UTRAN cell does not exceed the value of the
InterRatCellShutdown.UlPrbThd parameter.
The downlink PRB usage of the E-UTRAN cell does not exceed the value of the
InterRatCellShutdown.DlPrbThd parameter.
The number of UEs in the E-UTRAN cell does not exceed the value of the
InterRatCellShutdown.BearNumThd parameter.
All online UEs in the E-UTRAN cell support UMTS.
To prevent this feature from affecting the inter-RAT MLB feature, the values of both the
InterRatCellShutdown.UlPrbThd and InterRatCellShutdown.DlPrbThd parameters must be less than the value
of the CellMLB.InterRATMlbThd parameter.
When a cell enters the intelligent power-off of carriers in the same coverage as UMTS networks
state, the eNodeB
1. Prohibits new UE access or non-coverage-based handovers to the cell.
2. Transfers all UEs in the local cell to a co-coverage neighboring UTRAN cell within 30
seconds. If not all UEs in the cell are transferred to the neighboring cell within 30 seconds,
the eNodeB removes the prohibition on UE access and incoming handovers and reevaluates
whether the conditions for starting the intelligent power-off of carriers in the same coverage
as UMTS networks function are met.
3. Powers off the carrier after there is no UE in the local cell.
4. Sends an eNodeB Configuration Update message over the X2 interface to each neighboring
eNodeB. The message contains the Deactivation Indication IE, indicating that the cell is
deactivated for energy conservation.
12.1.3 Leaving
An E-UTRAN cell exits the intelligent power-off of carriers in the same coverage as UMTS
networks mode when the specified end time arrives or the function switch is turned off. In this
case, the eNodeB turns on the carrier again.
12.2 Network Analysis
12.2.1 Benefits
This function is recommended when E-UTRAN cells cover the same areas as neighboring
UTRAN cells and UEs support both LTE and UMTS.
This function is used when the NodeBs or eNodeBs are not provided by Huawei. If both NodeBs
and eNodeBs are provided by Huawei, the MRFD-121133 Multi-RAT Carrier Joint Intelligent
Shutdown (eNodeB) feature is recommended.
Power saving efficiency may decrease when multiple carriers share the same PA. This is because
the PA can be shut down only when all the carriers are powered off. For example, if the GSM
and LTE carriers use the same PA, the PA cannot be shut down if the LTE carrier is powered off
but the GSM carrier is not.
To prevent energy saving–triggered shutdown from affecting the lifespan of RF modules, the RF
modules may exit the energy saving state when their own temperature differential exceeds a
specified threshold within 24 hours. Energy saving gains decrease in this case.
12.2.2 Impacts
Network Impacts
To save power, this function enables the eNodeB to power off the carrier of the E-UTRAN cell
whose load is less than the configured threshold. After an E-UTRAN cell is shut down, the cell
no longer provides services and UEs are transferred to a UTRAN cell. Each time an LTE carrier
is powered off, the total network capacity is reduced by an amount equal to the capacity of the
shut-down cell. Therefore, enable this function when the network load is light.
When the carrier of an E-UTRAN cell is shut down by this function, the eNodeB transfers UEs
to a co-coverage UTRAN cell by handovers or redirections. As a result, the following counter
values increase:
L.IRATHO.E2W.PrepAttOut: number of outgoing handover attempts from E-UTRAN to WCDMA
network
L.IRATHO.E2W.ExecAttOut: number of outgoing handover executions from E-UTRAN to
WCDMA network
L.IRATHO.E2W.ExecSuccOut: number of successful outgoing handovers from E-UTRAN to
WCDMA network
L.RRCRedirection.E2W: number of redirections from E-UTRAN to WCDMA network
To hand the UEs over quickly, the E-UTRAN cell rejects new incoming handover requests from
any neighboring cell. The source cell continues to send handover requests to other candidate
neighboring cells, for example, UTRAN cells. Therefore, the value of the
L.HHO.Prep.FailOut.PrepFailure counter increases in the source cell. This counter indicates the
number of intra-duplex-mode outgoing handover preparation failures because of the handover
preparation failure messages sent from the target cell.
Note that after an LTE carrier is powered off, UEs can initiate call services only in the co-
coverage UTRAN cell, which negatively impacts the user QoS experience. Therefore, this
function should be used only when traffic is light, for example, at night.
Function Impacts
voltage
adjustment will
not.
intelligent
power-off of
carriers in the
same
coverage as
UMTS
networks
mode and the
detection will
be interrupted.
12.3 Requirements
12.3.1 Licenses
12.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.
Prerequisite Functions
None
12.3.3 Hardware
Boards
None
RF Modules
None
12.3.4 Others
None
12.4 Operation and Maintenance
The following table describes the parameters that must be set in the InterRatCellShutdown MO
to configure intelligent power-off of carriers in the same coverage as UMTS networks.
Table 12-1 Data to prepare (InterRatCellShutdown)
Parameter Parameter ID Setting Notes
Name
The following table describes the parameters that must be set in a UtranNFreq MO to configure
a neighboring UTRAN frequency.
Table 12-2 Data to prepare (UtranNFreq)
Parameter Name Parameter ID Setting Notes
Local cell ID UtranNFreq.LocalCellId This ID must be a value that has been set in
the Cell MO.
The following table describes the parameters that must be set in a UtranExternalCell MO to
configure an external UTRAN cell.
Table 12-3 Data to prepare (UtranExternalCell)
Parameter Name Parameter ID Setting Notes
The following table describes the parameters that must be set in a UtranNCell MO to configure
the neighbor relationship with a UTRAN cell.
Table 12-4 Data to prepare (UtranNCell)
Parameter Name Parameter ID Setting Notes
Local cell ID UtranNCell.LocalCellId This ID must be a value that has been set in
the Cell MO.
RNC cell ID UtranNCell.CellId Set this parameter to the same value in the
ULOCELL MO of the peer NodeB.
1. Run the LST INTERRATCELLSHUTDOWN command and verify that the value of the
Inter-RAT cell shutdown switch parameter is On and the value of the Shut Down Type
parameter is BY_UTRAN_WITHOUT_LOAD.
2. Run the DSP TIME command to verify that the eNodeB system time falls within the period
when the intelligent power-off of carriers in the same coverage as UMTS networks function
takes effect.
3. Choose Monitor > Signaling Trace > Signaling Trace Management on the U2020. In the
navigation tree on the left of the displayed Signaling Trace Management window, choose
Trace Type > LTE > Cell Performance Monitoring > Users Statistic Monitoring. Verify
that the number of UEs in the E-UTRAN cell is less than the value of the UE number
threshold parameter.
4. Choose Monitor > Signaling Trace > Signaling Trace Management on the U2020. In the
navigation tree on the left of the displayed Signaling Trace Management window, choose
Trace Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring. Verify
that the uplink and downlink PRB usages of the E-UTRAN cell are less than the values of
the Uplink PRB threshold and Downlink PRB threshold parameters, respectively.
5. After 6 minutes, run the DSP CELL command to verify that the value of the Cell power
save state parameter is CELL_PWRSAVE_INTERRAT_CELLSHD.
12.4.3 Network Monitoring
To monitor and evaluate the performance of this function, operators can view the following data
on the U2020:
eNodeB power consumption
You can check the VS.EnergyCons.BTS.Adding.LTE counter value to observe the eNodeB power
consumption. For the meaning of this counter, see Performance Counter Reference of
eNodeBs.
If the eNodeB power consumption drops significantly after intelligent power-off of carriers in
the same coverage as UMTS networks is activated, this function is delivering the expected
performance. If it does not, this function is underperforming.
Duration when a cell is in the intelligent power-off of carriers in the same coverage or
intelligent power-off of carriers in the same coverage as UMTS networks state
You can check the L.ChMeas.DFEE.CarrierOFF.Dur counter value to learn how long the cell has
been in this state. For the meaning of this counter, see Performance Counter Reference of
eNodeBs.
Duration of cell unavailability due to energy saving
You can check the L.Cell.Unavail.Dur.EnergySaving counter value to observe how long the cell
has been unavailable.
The measurement periods of the L.ChMeas.DFEE.CarrierOFF.Dur and L.Cell.Unavail.Dur.EnergySaving
counters are different. Therefore, the values of the two counters have a maximum deviation of 5
seconds.
Compare the eNodeB power consumption data on the live network from one week before and
one week after the function is enabled to assess the energy saving gains.
13 Parameters
The following hyperlinked EXCEL files of parameter documents match the software version
with which this document is released.
Node Parameter Reference: contains device and transport parameters.
eNodeBFunction Parameter Reference:
contains all parameters related to radio access functions,
including air interface management, access control, mobility control, and radio resource
management.
eNodeBFunction Used Reserved Parameter List: contains the reserved parameters that are in use and
those that have been disused.
You can find the EXCEL files of parameter reference and used reserved parameter list for the software version used
on the live network from the product documentation delivered with that version.
FAQ 1: How do I find the parameters related to a certain feature from parameter
reference?
1. Open the EXCEL file of parameter reference.
2. On the Parameter List sheet, filter the Feature ID column. Click Text Filters and choose
Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
3. Click OK. All parameters related to the feature are displayed.
FAQ 2: How do I find the information about a certain reserved parameter from the used
reserved parameter list?
1. Open the EXCEL file of the used reserved parameter list.
2. On the Used Reserved Parameter List sheet, use the MO, Parameter ID, and BIT
columns to locate the reserved parameter, which may be only a bit of a parameter. View its
information, including the meaning, values, impacts, and product version in which it is
activated for use.
14 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.
eNodeBFunction Performance Counter Summary:
contains all counters related to radio access
functions, including air interface management, access control, mobility control, and radio
resource management.
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?
1. Open the EXCEL file of performance counter reference.
2. On the Counter Summary(En) sheet, filter the Feature ID column. Click Text Filters and
choose Contains. Enter the feature ID, for example, LOFD-001016 or TDLOFD-001016.
3. Click OK. All counters related to the feature are displayed.
15 Glossary
16 Reference Documents
3. Power Control
5. ETWS
6. CMAS