Cell Switch-Off Based On Automatic Co-Coverage Identification Feature Parameter Description
Cell Switch-Off Based On Automatic Co-Coverage Identification Feature Parameter Description
Cell Switch-Off Based On Automatic Co-Coverage Identification Feature Parameter Description
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://www.huawei.com
Email: support@huawei.com
Contents
1 Change History.........................................................................................................................1
1.1 SRAN17.1 Draft A (2020-12-29)........................................................................................................................................ 1
3 Overview....................................................................................................................................5
4 Cell Switch-off Based on Automatic Co-coverage Identification (GSM)................... 7
4.1 Principles.................................................................................................................................................................................... 7
4.1.1 Co-coverage Neighboring Cell Learning...................................................................................................................... 7
4.1.2 Cell Shutdown and Restart............................................................................................................................................... 8
4.2 Network Analysis..................................................................................................................................................................... 9
4.2.1 Benefits.................................................................................................................................................................................... 9
4.2.2 Impacts.................................................................................................................................................................................... 9
4.3 Requirements......................................................................................................................................................................... 13
4.3.1 Licenses................................................................................................................................................................................. 13
4.3.2 Software................................................................................................................................................................................13
4.3.3 Hardware.............................................................................................................................................................................. 14
4.3.4 Others.................................................................................................................................................................................... 14
4.4 Operation and Maintenance............................................................................................................................................. 14
4.4.1 When to Use....................................................................................................................................................................... 14
4.4.2 Precautions.......................................................................................................................................................................... 14
4.4.3 Data Configuration........................................................................................................................................................... 14
4.4.3.1 Data Preparation............................................................................................................................................................ 15
4.4.3.2 Using MML Commands............................................................................................................................................... 15
4.4.3.3 Using the MAE-Deployment...................................................................................................................................... 15
4.4.4 Activation Verification..................................................................................................................................................... 16
4.4.5 Network Monitoring......................................................................................................................................................... 16
7 Parameters.............................................................................................................................. 54
8 Counters.................................................................................................................................. 55
9 Glossary................................................................................................................................... 56
10 Reference Documents........................................................................................................ 57
1 Change History
Technical Changes
Change Description Parameter Change Base Station Model
Added the function of exit Added the following 3900 and 5900 series
from carrier shutdown based options to the base stations
on acceleration guarantee and ENodeBAlgoSwitch.P
the function of fast SCC owerSaveSwitch
addition after the exit from parameter:
carrier shutdown. For details, ● AccGteeBasedCell-
see 6 Cell Switch-off Based ShutdnExSw
on Automatic Co-coverage
Identification (LTE). ● FastSccAddAftCell
ShutdownExSw
Editorial Changes
● Added the impact relationship with UL coordinated channel shutdown. For
details, see 6.2.2 Impacts.
● Revised the requirements on LTE capacity cells. For details, see 6.1.1 Related
Concepts.
● Added the description that the BBU3910C does not support Cell Switch-off
Based on Automatic Co-coverage Identification on the LTE side. For details,
see 6.3.3 Hardware.
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 Feature
Parameter Description documents apply only to the corresponding software
release. For future software releases, refer to the corresponding updated product
documentation.
For definitions of base stations described in this document, see section "Base
Station Products" in SRAN Networking and Evolution Overview.
3 Overview
● This feature identifies co-coverage cells accurately, compared with the manual
configuration of co-coverage cells.
● This feature can recognize network topology changes, and supports periodic
updates of the co-coverage relationship.
On multimode base stations where the RF module is shared between different
radio access technologies (RATs), it is recommended that this feature be enabled
for each RAT of the multimode base stations to allow the shutdown of cells of
different RATs during off-peak hours. In this way, the RF module can enter the
sleep mode to further reduce power consumption.
4.1 Principles
In densely-populated urban areas, the coverage areas of cells tend to overlap with
each other. The overlapping coverage of a cell can be determined based on the
measurement reports (MRs) reported by MSs. If the most traffic of a cell can be
absorbed by its neighboring cells, the cell can be shut down during off-peak hours
to reduce power consumption.
NOTE
● When co-coverage cells are identified based on MRs, only common MRs are supported.
Pre-processed MRs and enhanced MRs are not supported.
● To adapt to changes in coverage, the overlapping coverage is recalculated every seven
days.
● When a cell is deactivated and then reactivated, the co-coverage neighboring cell
learning needs to be performed again for the cell. After the learning, the cell shutdown
status may change.
● The duration between the current time and the previous cell restart is longer
than the period specified by GCELLDYNTURNOFF.PROTECTTIME.
● The number of activated channels (Number of activated TCHs + Number of
activated PDCHs) in the cell is less than the value of
GCELLDYNTURNOFF.TURNOFFCELLCHANNUM.
● The BSC detects the load of co-coverage cells every minute. After a number of
consecutive detections specified by
GCELLDYNTURNOFF.SAMECVGCELLLOADSTATTM, the load of all co-
coverage cells is lower than the value of
GCELLDYNTURNOFF.SAMECVGCELLLOADTHRD.
The BSC determines that the cell that has been shut down can be powered on
again when either of the following conditions is met:
● The current time is not within the period specified by
GCELLDYNTURNOFF.TURNOFFCELLSTRTIME and
GCELLDYNTURNOFF.TURNOFFCELLSTPTIME.
● The BSC detects the load of the co-coverage cells of a shut-down cell every
minute. After a number of consecutive detections specified by
GCELLDYNTURNOFF.SAMECVGCELLLOADSTATTM, the load of each co-
coverage cell is greater than or equal to the value of
GCELLDYNTURNOFF.TURNONCELLLOADTHRD. In addition, the duration
between the current time and the previous cell shutdown is greater than the
value of GCELLDYNTURNOFF.PROTECTTIME.
The cell load is indicated by the percentage of the channel resource
occupation in the cell. When calculating the load of the co-coverage cell, the
BSC determines whether to include dynamic PDCHs in the load statistics
based on the setting of GCELLCHMGAD.TurnOffLoadType.
4.2.1 Benefits
If the base station is configured with two frequency bands (900 MHz and 1800
MHz), and the network load is low during off-peak hours at night, the
deployment of this feature on the high frequency band allows the shutdown of
the cell served by the RF module working on the high frequency band. This
reduces the power consumption of the network.
4.2.2 Impacts
In dual-band networks, the 900 MHz frequency band provides basic coverage. The
shutdown of 1800 MHz cells does not affect coverage. However, after 1800 MHz
cells are shut down, the traffic is migrated to 900 MHz cells, and the GSM
performance deteriorates by 2%–10%.
In 900 MHz single-band networks, if cells working on the 900 MHz frequency
band are shut down, coverage holes may occur in some edge areas, affecting GSM
KPIs. The cell shutdown percentage is about 0–10%, and the GSM performance
relatively deteriorates by 0–10%.
The affected GSM KPIs are as follows:
● The values of the following KPIs increase: TCH call drop rate (including
handover), TCH call drop rate (excluding handover), TCH congestion rate (all
busy), SDCCH call drop rate, uplink TBF call drop rate, downlink TBF call drop
rate, uplink EGPRS TBF call drop rate, downlink EGPRS TBF call drop rate,
uplink EGPRS TBF congestion rate, downlink EGPRS TBF congestion rate,
uplink TBF congestion rate, and downlink TBF congestion rate.
● The values of the following KPIs may decrease: handover success rate, radio
handover success rate, call setup success rate, immediate assignment success
rate, assignment success rate, uplink TBF setup success rate, downlink TBF
setup success rate, uplink EGPRS TBF setup success rate, and downlink EGPRS
TBF setup success rate.
After cells are shut down, UMTS-to-GSM handovers, and LTE CS fallback and
SRVCC handovers may be affected.
Function Impacts
Function Name Function Switch Reference Description
Shutdown
function to reduce
the load of the
cell. When the cell
load decreases to
a certain level,
Cell Switch-off
Based on
Automatic Co-
coverage
Identification
shuts down the
BCCH TRX of the
cell to further
reduce the power
consumption of
the BTS.
4.3 Requirements
4.3.1 Licenses
Feature ID Feature Name Model NE Sales Unit
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
4.3.3 Hardware
The following base stations do not support this feature: BTS30, BTS312, BTS3001C,
BTS3001CP, BTS3002C, BTS3012A, BTS3006A, BTS3012, BTS3006C, BTS3002E,
BTS3012AE, BTS3012_II, BTS3900B_GSM, and BTS3900E_GSM.
Boards
No requirements
RF Modules
No requirements
4.3.4 Others
None
4.4.2 Precautions
When enabled in 900 MHz cells, this feature affects KPIs.
NOTE
In typical live network scenarios, the co-coverage neighboring cell learning is expected to
be completed within 24 hours.
Whether a cell can be shut down is determined every minute. Therefore, a 60s
deviation may exist between the actual cell shutdown time and the configured time.
Table 4-2 Counters used for measuring the power consumption of GSM base
stations
Counter ID Counter Name NE Description
5.1 Principles
This feature applies to multi-band scenarios in which a NodeB is configured with
multiple frequency bands, such as 2100 MHz and 900 MHz. Different frequency
bands are configured on different RF modules. In multi-band scenarios, this
feature automatically learns the co-coverage neighboring cells of a cell to be shut
down. When the load of the cell to be shut down and its co-coverage neighboring
cells meets certain requirements, this feature automatically shuts down the cell
working on a high frequency band.
Cell Switch-off Based on Automatic Co-coverage Identification (UMTS) takes
effect only when the related cell-level parameters are set as follows:
● On the RNC: The UCELLDYNSHUTDOWN.DynShutDownType parameter is
set to CCISHUTDOWN.
● On the NodeB: The ULOCELLALGPARA.CELLSWITCHOFFBSDONCCISW
parameter is set to ON.
UEs are considered as low activity UEs if they meet the trigger conditions of any of the
following:
● Common CELL_DCH to CELL_FACH (D2F) state transitions
● Throughput-based CELL_DCH to CELL_PCH or URA_PCH (D2P) or D2F state
transitions
● Inactivity-based D2P state transitions
● Enhanced fast dormancy
The time required by co-coverage neighboring cell learning is related to the load of
the source cell and the number of D2F or D2P state transitions.
When the number of inter-frequency measurement configuration delivery
times delivered for a frequency on a frequency band different from that of the
source cell is greater than or equal to the value of the
UCOCOVERAGE.CoCovCellLearnMaxMcNum parameter, inter-frequency
measurement in compressed mode is terminated in the source cell.
Flow control is enabled by default for co-coverage neighboring cell
identification, to avoid affecting the RNC functions. If the RNC load is greater
than the flow control threshold, which is specified by the
FCCPUTHD.DCCCTHD parameter, the RNC terminates the measurement for
co-coverage neighboring cell identification. After the measurement is
terminated, the RNC restarts the measurement only when its load falls below
the flow control clearance threshold, which is specified by the
FCCPUTHD.DCCCRSTTHD parameter.
For example, if this feature is activated during the daytime on 1 March, the RNC
determines that the duration is zero days in the early morning on 2 March, and the
RNC determines that the duration is one day in the early morning on 3 March. The
rest can be deduced by analogy and the RNC determines that the duration is seven
days in the early morning on 9 March. That is, after this feature is activated, the RNC
finishes co-coverage neighboring cell identification for the source cell within seven
whole days.
3. Collects statistics on MRs.
Upon receiving an MR, the RNC checks, for each involved frequency, whether
the received signal code power (RSCP) in the best neighboring cell is greater
than or equal to the value of the
UCOCOVERAGE.DynShutFlagLearnMinRscpThd parameter. If yes, the RNC
increments the number of MRs by one for the neighboring cell. If not, the
RNC keeps the number of MRs for the neighboring cell unchanged. Similarly,
the RNC counts the number of MRs for all best neighboring cells by
frequency.
4. Selects the neighboring cells with a high measurement success rate as co-
coverage neighboring cells.
The RNC calculates the measurement success rates of all neighboring cells on
each frequency. Measurement success rate = Number of MRs for a
neighboring cell/Number of measurement control messages delivered for the
operating frequency of the neighboring cell x 100%
The RNC sorts neighboring cells in descending order of the measurement
success rate, and determines whether the highest measurement success rate
for cells at a specific frequency is greater than or equal to the value of the
UCOCOVERAGE.DynShutFlagLearnMcSucRatio parameter. If the highest
measurement success rate is less than this parameter value, the RNC
continues to check whether the sum of the highest and second highest
measurement success rates for cells at the frequency is greater than or equal
to this parameter value. If the sum does not meet the requirement, the RNC
continues the check. If the requirement is still not met, the RNC will
eventually determine whether the sum of the measurement success rates of
all neighboring cells at the frequency meets the requirement.
– If the sum of the top six measurement success rates of neighboring cells
meets this requirement, the RNC sets the
UINTRAFREQNCELL.DynCellShutDownFlag parameter to TRUE for
these six neighboring cells.
– If the sum of the top n (n > 6) measurement success rates of neighboring
cells meets this requirement, the RNC sets the
UINTRAFREQNCELL.DynCellShutDownFlag parameter to TRUE for only
the neighboring cells whose measurement success rate is among top six.
– If the sum of the measurement success rates of all neighboring cells at a
frequency does not meet the requirement, the RNC sets the
UINTRAFREQNCELL.DynCellShutDownFlag parameter to FALSE for all
neighboring cells at the frequency. This indicates that no neighboring
cells at the frequency are a co-coverage neighboring cell of the source
cell.
After the calculation is performed on all neighboring cells at each frequency,
the RNC considers that the neighboring cells with the
UINTRAFREQNCELL.DynCellShutDownFlag parameter set to TRUE are the
co-coverage neighboring cells of the source cell.
NOTE
The HSDPA UEs include SC-HSDPA UEs and multi-carrier HSDPA UEs (including
DC-HSDPA, DB-HSDPA, 3C-HSDPA, and 4C-HSDPA UEs). The multi-carrier UEs
include only those whose primary cell is the serving cell to be shut down.
– For a multi-carrier HSDPA cell to be shut down, the number of multi-
carrier HSDPA UEs whose primary cell is the serving cell to be shut down
is less than or equal to the value of the
UCELLDYNSHUTDOWN.McHsdpaUserNumThd parameter.
– The number of HSUPA UEs is less than or equal to the value of the
UCELLDYNSHUTDOWN.HsupaUserNumThd parameter.
The HSUPA UEs include SC-HSUPA and multi-carrier HSUPA UEs.
– All the neighboring cells of the serving cell with their
UINTERFREQNCELL.DynCellShutDownFlag parameters set to TRUE are
available and not in the load reshuffling (LDR) or overload control (OLC)
state, and their power load meets the remaining power load condition.
That is, the power load of each neighboring cell in both the uplink and
downlink is less than the difference between the LDR threshold and the
value of the UCELLDYNSHUTDOWN.NcellLdrRemainThd parameter.
The uplink and downlink LDR thresholds are specified by the
UCELLLDM.UlLdrTrigThd and UCELLLDM.DlLdrTrigThd parameters.
– If the UCELLDYNSHUTDOWN.RefUeBandAccessCapabSwitch
parameter is set to ON, the proportion of UEs in the CELL_DCH state
supporting a frequency band different from that of the serving cell within
the previous day is greater than or equal to the value of the
UCELLDYNSHUTDOWN.InterBandUeThd parameter.
– The noise floor of all neighboring cells of the current cell with the
UINTERFREQNCELL.DynCellShutDownFlag parameter set to TRUE is
less than the value of the
UCELLDYNSHUTDOWN.InterBandNCellInterfereThd parameter.
– The co-site intra-band cells that consider the current cell as a neighboring
cell for blind handovers are shut down.
If all conditions for a specific networking scenario are satisfied, the RNC
performs the operations in 2. Otherwise, the RNC continues the check.
2. User migration is performed based on pilot power adjustment. The
UCELLDYNSHUTDOWN.UserMigrationType parameter must be set to
PCPICHPOWERADJUST.
a. The NodeB gradually reduces the pilot power of the serving cell by a step
specified by the UCELLDYNSHUTDOWN.PCPICHPowerAdjStep
parameter. After the pilot power is reduced to a certain value, the RNC
hands over the UEs from the serving cell to a neighboring cell.
b. After the period specified by the
UCELLDYNSHUTDOWN.PCPICHPowerAdjPeriod parameter elapses, the
RNC checks whether there are UEs in the local cell.
If there are no UEs in the local cell, or there are only UEs in the
Cell_FACH state in the local cell with the
UCELLDYNSHUTDOWN.DynShutDownCchUserSwitch parameter set to
OFF, and the power load of neighboring cells is normal, the RNC sends a
cell shutdown indication to the NodeB. Otherwise, the RNC continues to
check whether the cell shutdown conditions are met. If the conditions are
met, the RNC continues to reduce the pilot power. If the conditions are
not met, the RNC restores the pilot power.
c. If there are still CELL_DCH UEs when the pilot power is reduced to -10
dBm, the NodeB retains the pilot power of -10 dBm and checks the
number of online UEs at an interval specified by the
UCELLDYNSHUTDOWN.PCPICHPowerAdjPeriod parameter to
determine whether the online UEs are handed over to a neighboring cell
or whether the services are released until the shutdown period ends.
NOTE
5.2.1 Benefits
If the base station is configured with two frequency bands (for example, 900 MHz
and 2100 MHz), and the network load is low during off-peak hours at night, the
deployment of this feature on the high frequency band allows the shutdown of all
the carriers on the RF module working on the high frequency band. This reduces
the power consumption of the network.
5.2.2 Impacts
Network Impacts
Enabling this feature has a slight impact on network performance.
Function Impacts
Function Function Reference Description
Name Switch
5.3 Requirements
5.3.1 Licenses
Feature ID Feature Name Model NE Sales Unit
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
Forced Cell Set the Green BTS For a cell, cell shutdown can
Shutdown DynShutDow be implemented by using the
nType Cell Switch-off Based on
parameter to Automatic Co-coverage
FORCESHUT Identification feature or using
DOWN one of these features listed in
this table.
Multi-Carrier Set the Green BTS
Switch off DynShutDow
Based on nType
Traffic Load parameter to
CONDITIONA
LSHUTDOW
N
5.3.3 Hardware
Boards
No requirements
RF Modules
No requirements
5.3.4 Networking
● The NodeB is configured with frequencies of different frequency bands (for
example, 2100 MHz and 900 MHz). One or multiple frequencies of the high
frequency band are configured, and these inter-frequency cells are co-
coverage cells, and are configured as inter-frequency neighboring cells of each
other. At least one frequency of the low frequency band provides continuous
network coverage.
● More than 90% of UEs on the network support the low frequency band.
● GSM network coverage is required to ensure the service provisioning for UEs
that do not support the UMTS low frequency band.
5.3.5 Others
None
//(Optional) Configuring the blind handover relationship between carrier F1 and other carriers working on
the high frequency band (skip this step if there is only one carrier working on the high frequency band)
ADD UINTERFREQNCELL: RNCId=110, CellId=1, NCellRncId=110, NCellId=0, SIB11Ind=TRUE,
SIB12Ind=FALSE, TpenaltyHcsReselect=D0, BlindHoFlag=TRUE, NPrioFlag=FALSE,
InterNCellQualReqFlag=FALSE;
//Configuring cell-level dynamic cell shutdown parameters for the cell working on the high-frequency F1
ADD UCELLDYNSHUTDOWN: CellId=0, DynShutdownSwitch=ON_1, StartTime1=00&00, EndTime1=06&00,
DynShutDownType=CCISHUTDOWN, CoCovNCellType=INTERBAND, TotalUserNumThd=8,
HsdpaUserNumThd=6, HsupaUserNumThd=6, NCellLdrRemainThd=20, CellStartUpType=IMMEDIATELY,
RefUeBandAccessCapabSwitch=ON, InterBandUeThd=90, InterBandNCellInterfereThd=-95,
BlindHOLimitSwitch=ON, UserMigrationType=PCPICHPOWERADJUST;
//Turning on the dynamic cell shutdown optimization switch and the neighboring cell state optimization
switch for the dynamic cell shutdown algorithm
SET UNBMPARA: PerfEnhanceSwitch2=PERFENH_DYNSHUTDOWN_OPT_SWITCH-1,
PerfEnhanceSwitch3=PERFENH_CELL_DYN_CLOSE_NCELL_STAT_SWITCH-1;
//Configuring the parameters for identifying co-coverage neighboring cells
SET UCOCOVERAGE: CoCovCellLearnCMUeNumThld=2, CoCovCellLearnMaxMcNum=1000,
CoCovCellLearnMinMcNum=700, DynShutFlagLearnMcSucRatio=90, DynShutFlagLearnMinRscpThd=-100,
CoCovCellLearnMode=PERIODICAL_LEARN, CoCovCellLearnPeriod=D30;
//(Optional) Configuring the co-coverage neighboring cell for the carrier working on the high-frequency F1
(Skip this step if the co-coverage neighboring cell learning mode is not NOT_LEARN)
MOD UINTERFREQNCELL: RNCId=110, CellId=0, NCellRncId=110, NCellId=10, DynCellShutDownFlag=TRUE;
NOTE
In typical scenarios (the average TCP load of a cell greater than or equal to 30%), the co-
coverage neighboring cell learning can be completed within three days. The average TCP
load of a cell can be measured by the VS.TCP.Usage.Mean counter.
In an extremely lightly loaded cell, if the number of MRs collected within seven days is less
than the value of the UCOCOVERAGE.CoCovCellLearnMinMcNum parameter, the co-
coverage neighboring cell learning does not apply. You are advised to manually configure
co-coverage neighboring cells.
In multiband scenarios, after the high frequency band is shut down, some UEs are
likely to experience call drops if they do not support the low frequency band. The
negative gains of this feature can be evaluated using the following KPIs:
● CS call drop rate
● AMR call drop rate
● PS call drop rate
● PS R99 call drop rate
● HSDPA service drop rate
● HSUPA service drop rate
6.1 Principles
In inter-frequency co-coverage scenarios, the inter-frequency co-coverage
relationship between capacity and basic cells is automatically identified through
co-coverage learning based on inter-frequency MRs. When the load is light, the
traffic of the capacity cell is migrated to the co-coverage basic cells that can
handle the added load, and then the capacity cell is shut down to reduce the base
station power consumption.
When a basic cell serves as the neighboring cell of a capacity cell, the basic cell is
called the neighboring basic cell of the capacity cell. When the neighboring basic
cell has a large coverage overlap with the capacity cell, the neighboring basic cell
is called the co-coverage neighboring basic cell of the capacity cell. Before the
learning of co-coverage neighboring cells is complete, the co-coverage
neighboring basic cells can be identified based on parameter configuration. When
the EutranInterFreqNCell.OverlapInd parameter for a neighboring basic cell is
set to YES, the cell is considered as the co-coverage neighboring basic cell of the
capacity cell. If the EutranInterFreqNCell.OverlapInd parameter is set to NO for
all neighboring basic cells of a capacity cell, all neighboring basic cells are
considered as the co-coverage neighboring basic cells of the capacity cell. After
the learning of the co-coverage neighboring cells is complete, the eNodeB
determines the co-coverage neighboring basic cells based on the learning results.
When the X2 link between the eNodeB serving the basic cell and the eNodeB
serving the capacity cell is faulty, the configuration information about the inter-
eNodeB neighboring cell cannot be obtained over the X2 interface. In this case,
the inter-eNodeB neighboring cell over the X2 interface cannot be identified as co-
coverage neighboring basic cells of the current capacity cell before the X2 fault is
rectified.
Capacity Cell
In an inter-frequency co-coverage network, the cells working on the frequency
that is for capacity improvement are called capacity cells. Capacity cells are
generally high-band cells and can be shut down when the network load is low. To
enable UE handover from capacity cells to basic cells, the basic cells need to be
configured as neighboring cells of the capacity cells.
In NSA networking, ensure that at least one anchor frequency is not used as the
frequency where capacity cells operate.
cells of the capacity cell. The eNodeB selects a UE every 30s, and does not
select high-priority UEs.
2. The eNodeB performs co-coverage learning.
– If the eNodeB receives at least 1000 valid MRs within a learning period,
which lasts one week, the eNodeB stops inter-frequency measurement.
The eNodeB calculates the value of
EutranInterFreqNCell.CoverageOverlapProportion, which indicates the
overlapping coverage proportions between the capacity cell and all
neighboring basic cells, and the value of
CellShutdown.CoverageHoleProportion, which indicates the coverage
hole proportion that is caused by the shutdown of the capacity cell.
▪ EutranInterFreqNCell.CoverageOverlapProportion = Number of
times that the neighboring basic cell is the strongest cell/Number of
times measurement control messages are delivered for the frequency
of the neighboring basic cell
After the configurations of basic cells and capacity cells change, the eNodeB does not
immediately restart the learning of co-coverage neighboring cells. Instead, it starts learning
in the next learning period.
If you want to restart the learning of co-coverage neighboring cells immediately, turn off
CellShutdown.CellShutdownSwitch, and then set it to ON_CO_COV_AUTO_IDENT.
Entry Conditions
If co-coverage neighboring cell learning results are available, the eNodeB
periodically (specified by the CellShutdown.CarrShutdownTrigJudgePrd
parameter) determines whether a capacity cell meets the following conditions
within the period specified by CellShutdown.StartTime and
CellShutdown.StopTime. The cell enters the co-coverage carrier shutdown state
when all of the following conditions are met:
● The local cell and all its co-coverage neighboring basic cells meet the
following conditions:
– Uplink PRB usage of the local cell + Uplink PRB usage of a co-coverage
neighboring basic cell < Uplink PRB usage threshold for the local cell to
start intelligent shutdown of carriers in the same coverage (specified by
the CellShutdown.UlPrbThd parameter)
– Downlink PRB usage of the local cell + Downlink PRB usage of a co-
coverage neighboring basic cell < Downlink PRB usage threshold for the
local cell to start intelligent shutdown of carriers in the same coverage
(specified by the CellShutdown.DlPrbThd parameter)
– The number of UEs in RRC_CONNECTED mode in the local cell is less
than the value of CellShutdown.UENumThd.
● The proportion of coverage holes (specified by
CellShutdown.CoverageHoleProportion) that may be caused by the
shutdown of capacity cells is less than or equal to 10%.
● In LTE FDD, the local cell is not in the trigger state of the low power
consumption mode or the inter-RAT cell shutdown mode. In LTE TDD, the cell
is not in the trigger state of the low power consumption mode.
● There is at least one co-coverage neighboring basic cell, and all co-coverage
neighboring basic cells are available.
If co-coverage neighboring cell learning results are unavailable, the capacity cell
enters the co-coverage carrier shutdown mode within the period specified by
CellShutdown.StartTime and CellShutdown.StopTime when the following
conditions are met:
● The local cell and all its co-coverage neighboring basic cells meet the
following conditions (details about co-coverage neighboring basic cells can be
found in "Basic Cell" in 6.1.1 Related Concepts):
– Uplink PRB usage of the local cell + Uplink PRB usage of a co-coverage
neighboring basic cell < Uplink PRB usage threshold for the local cell to
start intelligent shutdown of carriers in the same coverage (specified by
the CellShutdown.UlPrbThd)
– Downlink PRB usage of the local cell + Downlink PRB usage of a co-
coverage neighboring basic cell < Downlink PRB usage threshold for the
local cell to start intelligent shutdown of carriers in the same coverage
(specified by the CellShutdown.DlPrbThd parameter)
– The number of UEs in RRC_CONNECTED mode in the local cell is less
than the value of CellShutdown.UENumThd.
● In LTE FDD, the local cell is not in the trigger state of the low power
consumption mode or the inter-RAT cell shutdown mode. In LTE TDD, the cell
is not in the trigger state of the low power consumption mode.
To avoid the impact on the MLB feature, the uplink and downlink PRB thresholds
for starting intelligent shutdown of carriers in the same coverage must be less
than the value of CellMLB.InterFreqMlbThd.
Shutdown Process
After detecting that the co-coverage shutdown entry conditions are met and the
number of UEs in RRC_CONNECTED mode in a capacity cell is 0, the eNodeB
directly blocks the cell, and notifies adjacent eNodeBs and neighboring cells. If the
number of UEs in RRC_CONNECTED mode in a capacity cell is not 0, the eNodeB
performs the following operations:
● Broadcasts the barred state of the local cell through SIB1. In addition, the
eNodeB sends an eNodeB configuration update message (carrying
deactivation indication) to the neighboring eNodeB over the X2 interface to
prevent handovers from other cells to the local cell. After the barred
indication takes effect, new UEs cannot access the local cell.
● Prohibits the local cell from being configured as a secondary cell. The related
secondary cell configurations need to be removed from carrier aggregation
(CA) UEs.
● Attempts to hand over all UEs in the local cell to the co-coverage neighboring
basic cells within 60s. If some UEs fail to be handed over and carrier
shutdown cannot be forcibly performed, the eNodeB cancels the barred state
and informs all neighboring eNodeBs over the X2 interface that the local cell
has exited the energy saving state. The eNodeB checks the trigger conditions
again after the penalty duration specified by CellShutdown.PunishTime
elapses.
● Checks the number of UEs in the local cell once every 5s within the period of
60 seconds. If the number of RRC_CONNECTED UEs is less than or equal to
the value of CellShutdown.ForceShutdownUENumThd and there are no UEs
performing QCI1 services in the cell after 60s elapse, the carrier of the local
cell is shut down and the local cell is blocked.
NOTE
When a capacity cell is shut down, only its carrier is shut down. The cell itself is not
deactivated. Its baseband resources will not be preempted and the scheduling-related
performance counters are still measured. In this way, the capacity cell can quickly exit the
shutdown mode when it meets the exiting conditions.
Leaving Conditions
When any of the following conditions is met, the eNodeB exits the automatic co-
coverage identification-based cell shutdown mode, restarts the shutdown carrier,
and notifies neighboring eNodeBs and neighboring cells:
● The uplink PRB usage of a co-coverage neighboring basic cell is higher than
the uplink PRB threshold for exiting the co-coverage-based intelligent carrier
shutdown of the capacity cell. The threshold is equal to the sum of
CellShutdown.UlPrbThd and CellShutdown.UlPrbOffset.
● The downlink PRB usage of a co-coverage neighboring basic cell is higher
than the downlink PRB threshold for exiting the co-coverage-based intelligent
carrier shutdown of the capacity cell. The threshold is equal to the sum of
CellShutdown.DlPrbThd and CellShutdown.DlPrbOffset.
If the function of fast exit from the co-coverage carrier shutdown state for specific
network services (for example, access to a specific DNS server or IP address) is
required, the operations below can be performed. If this function is enabled, all
capacity cells under the eNodeB immediately exit the co-coverage carrier
shutdown state once the eNodeB detects an acceleration guarantee UE
performing specific network services.
● Select the AccGteeBasedCellShutdnExSw option of the
ENodeBAlgoSwitch.PowerSaveSwitch parameter, to enable the base station
to exit from carrier shutdown based on acceleration guarantee.
● Use the SCAPPPARACFG MO to configure air interface acceleration guarantee
for the DNS server or IP address requiring guarantee. For details, see Video
Experience Optimization.
Assume that fast SCC addition (specified by the
FastSccAddAftCellShutdownExSw option of the
ENodeBAlgoSwitch.PowerSaveSwitch parameter) is enabled and a capacity cell
exits the co-coverage carrier shutdown state. If SCell configuration is required
immediately after the exit for UEs in the intra-base-station basic cells of the
capacity cell, the following conditions must be met in addition to the basic
triggering conditions for SCell configuration:
Note: Assume that both the function of exit from carrier shutdown based on acceleration
guarantee (specified by the AccGteeBasedCellShutdnExSw option of the
ENodeBAlgoSwitch.PowerSaveSwitch parameter) and the fast SCC addition function
(specified by the FastSccAddAftCellShutdownExSw option of the
ENodeBAlgoSwitch.PowerSaveSwitch parameter) are enabled. SCell configuration is
triggered immediately after a capacity cell exits the co-coverage carrier shutdown state for
acceleration guarantee UEs served by the base station regardless of whether the traffic
volume exceeds the SCell activation threshold.
To avoid the impact on the MLB feature, the uplink and downlink PRB thresholds
for exiting intelligent shutdown of carriers in the same coverage must be less than
the sum of CellMLB.InterFreqMlbThd and CellMLB.LoadOffset.
6.2.1 Benefits
This feature is recommended if the base station is configured with at least two
frequencies and the network load is low during off-peak hours at night, for
example, the uplink and downlink PRB usage of capacity cells and basic cells are
lower than 20%.
For a capacity cell that is served by a multimode RF module where the power
amplifier (PA) is shared between carriers, for example, GL PA sharing, GSM
carriers still work after the LTE cell is shut down. In this case, the PA cannot be
shut down, and the power saving gain is limited.
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
To save power, Cell Switch-off Based on Automatic Co-coverage Identification
shuts down some carriers when the network load is less than a configured
threshold. When a carrier is shut down, the capacity of the cell corresponding to
the carrier is lost and the capacity of the entire network is reduced. Therefore, this
feature can be used only when the network load is relatively light.
● Before the capacity cell is shut down, UEs in the capacity cell are handed over
to a basic cell, causing an increase in the values of counters measuring inter-
frequency handovers in a period of time.
● When some capacity cells are shut down, intra-frequency handovers between
capacity cells may be affected. As a result, the values of counters measuring
intra-frequency handovers decrease while the values of counters measuring
inter-frequency handovers increase.
● When CellShutdown.ForceShutdownUENumThd is set to a non-zero value
and the triggering conditions for forced shutdown are met, the UEs that fail
to be handed over from capacity cells to basic cells experience service drops
because capacity cells are forcibly shut down. As a result, Service Drop Rate
increases.
● To ensure that UEs are handed over to target cells at the earliest time
possible, new UEs are prohibited from accessing the capacity cell. In addition,
the SIB1 message is used to broadcast the barred state of the cell. However, a
small number of UEs may still send RRC connection requests to access the
network, and consequently the value of the L.RRC.SetupFail.Rej counter
increases. The number of such access failures is indicated by the
L.RRC.SetupFail.ResFail.CellBarred counter.
● When UEs in a capacity cell are being handed over to a basic cell, if the
CellMLB.InterFreqMlbThd parameter for the basic cell is set to a small value
(for example, a value smaller than the default value), the basic cell rejects the
incoming handover attempts of these UEs due to a heavy cell load. As a
result, the value of Inter-Frequency Handover Out Success Rate decreases.
Function Impacts
RAT Function Function Reference Description
Name Switch
6.3 Requirements
6.3.1 Licenses
RA Feature ID Feature Name Model NE Sales Unit
T
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
RAT Function Function Reference Description
Name Switch
6.3.3 Hardware
Base Station Models
3900 and 5900 series base stations
DBS3900 LampSite and DBS5900 LampSite
Boards
All BBUs except the BookBBU5901 support this feature.
RF Modules
None
6.3.4 Networking
● This feature applies to inter-frequency co-coverage scenarios and requires one
or more frequencies at the capacity layer.
● The frequency of basic cells can ensure continuous coverage.
6.3.5 Others
None
NOTE
Step 2 On the MAE-Access, choose Monitor > Signaling Trace > Signaling Trace
Management. In the left navigation tree of the displayed window, choose Trace
Type > LTE > Cell Performance Monitoring > Usage of RB Monitoring. Verify
that the uplink and downlink PRB usage of the serving cell and its co-coverage
inter-frequency neighboring cells are lower than the uplink and downlink PRB
thresholds for starting co-coverage-based intelligent carrier shutdown. In this case,
the cell enters the co-coverage-based intelligent carrier shutdown mode.
Step 3 Two minutes later, run the MML command DSP CELL to check the value of Cell
power save state. If the value is RF intelligent shutdown mode, the cell is shut
down.
----End
Benefit Monitoring
Operators can monitor and evaluate the performance of this feature by observing
the counters on the MAE-Access. After activating this feature, check the following
counters to evaluate the gains produced by this feature:
You can compare the eNodeB power consumption data on the live network one
week before and after the feature is enabled to evaluate the energy saving gains
of the feature.
Troubleshooting Procedure
When a cell cannot enter the carrier shutdown mode as expected, perform the
following operations:
Step 1 Verify that inter-frequency neighboring cells are configured correctly. For details
about how to configure inter-frequency neighboring cells, see Mobility
Management in Connected Mode.
Step 2 Run the DSP CELLSHUTDOWN command to query the current status and cause
values of carrier shutdown. Table 6-2 lists the details.
----End
7 Parameters
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.
Step 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.
Step 3 Click OK. All parameters related to the feature are displayed.
----End
Step 1 Open the EXCEL file of the used reserved parameter list.
Step 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.
----End
8 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.
NOTE
You can find the EXCEL files of performance counter reference for the software version used
on the live network from the product documentation delivered with that version.
----End
9 Glossary
10 Reference Documents