Cell Outage Detection and Recovery (eRAN12.1 - 01)

U2000
V200R017C10
Feature Description About Cell
Outage Detection and Recovery
Issue 01
Date 2017-03-07
HUAWEI TECHNOLOGIES CO., LTD.

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

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2017-03-07) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
U2000
Feature Description About Cell Outage Detection and
Recovery Contents
Contents
1 Introduction.................................................................................................................................... 1
1.1 Scope ............................................................................................................................................................................ 1
1.2 Site Type Difference ..................................................................................................................................................... 1
1.3 Intended Audience ........................................................................................................................................................ 1
1.4 Change History ............................................................................................................................................................. 1
1.5 Overview ...................................................................................................................................................................... 3
1.6 Definition ...................................................................................................................................................................... 3
1.7 Benefits ......................................................................................................................................................................... 3
1.8 Functions ...................................................................................................................................................................... 4
2 Cell Outage Detection Techniques ............................................................................................ 5

2.1 Possible Causes of Cell Outage .................................................................................................................................... 5
2.2 Cell Outage Detection ................................................................................................................................................... 5
2.2.1 Cell Outage Detection Based on an Alarm ................................................................................................................ 5
2.2.2 Cell Outage Detection Based on a Sleeping Cell ....................................................................................................... 6
2.2.3 Cell Outage Detection Based on an Abnormal KPI ................................................................................................... 9
2.2.4 Cell Outage Detection Based on an Internal Audit by eNodeBs.............................................................................. 13
2.3 Service Adjustment for Outage Cells .......................................................................................................................... 14
2.4 Restoration of Outage Cells and RRUs ...................................................................................................................... 15
2.5 Suggestions on Handling Cell Outage ........................................................................................................................ 17
2.6 Related Features.......................................................................................................................................................... 17
2.7 Network Impact .......................................................................................................................................................... 18
3 Engineering Guidelines ............................................................................................................. 19

3.1 Preparation .................................................................................................................................................................. 19
3.2 Required Information .................................................................................................................................................. 19
3.3 Planning ...................................................................................................................................................................... 20
3.4 Deployment ................................................................................................................................................................ 20
3.5 Deployment of the Cell Outage Management Feature ................................................................................................ 20
3.5.1 Process ..................................................................................................................................................................... 20
3.5.2 Requirements ........................................................................................................................................................... 20
3.5.3 Precautions............................................................................................................................................................... 21
3.5.4 Hardware Adjustment .............................................................................................................................................. 21
3.5.5 Initial Configuration ................................................................................................................................................ 21
Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright © ii

Huawei Technologies Co., Ltd
U2000
Recovery Contents
3.5.6 Activation Observation ............................................................................................................................................ 33

3.5.7 Deactivation ............................................................................................................................................................. 36
3.6 Maintenance ................................................................................................................................................................ 36
3.7 Troubleshooting .......................................................................................................................................................... 37
4 Parameters .................................................................................................................................... 39
5 Counters ........................................................................................................................................ 44
6 Reference Documents................................................................................................................. 47
Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright © iii

Huawei Technologies Co., Ltd
U2000
Recovery 1 Introduction
1 Introduction
1.1 Scope
This document describes the Cell Outage Management feature, including principles and
functions. It also describes how to configure related parameters.
Any managed objects (MOs), parameters, alarms, or counters described in this document
correspond to the latest software release delivered with this document. In the event of updates,
the updates will be described in the product documentation delivered with the latest software
release.
1.2 Site Type Difference

 Cell outage detection
Pico base stations do not support GSM cell outage detection.
 Outage cell restoration
Pico base stations do not support outage RRU restoration or baseband board resetting.
 Log collection
Pico base stations do not support log collection.
1.3 Intended Audience

This document is intended for personnel who:
 Need to understand the Cell Outage Management feature
 Work with Huawei products
1.4 Change History

This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 1

© Huawei Technologies Co., Ltd
U2000
 Feature change: refers to a change in the sleeping cell detection and the Cell Outage
Management feature of a specific product version.
 Editorial change: refers to a change in wording or the addition of information that was
not described in the earlier version.
01 (2017-03-07)
This is the first commercial release for V200R017C10. Compared with issue Draft A (2016-
12-30) of V200R017C10, this issue does not include any changes.
Draft A (2016-12-30)
This is the Draft A release for V200R017C10. Compared with issue 01 (2016-02-25) of
V200R016C10, this issue does not include any changes.

U2000
1.5 Overview
This chapter provides an overview of Cell Outage Management. A cell may fail to provide
services properly because of issues such as environmental changes, network element (NE)
hardware or software faults, and user misoperations. In this situation, network performance
and quality of service (QoS) deteriorate notably. To prevent this problem, networks must be
monitored in real time to detect sleeping cells and outage cells.
The system determines that cells are in outage by using multiple detection methods. It also
provides functions of restoring and adjusting these outage cells.
NOTE
Pico base stations do not support log collection.
The Cell Outage Management feature involves the following features:

 Feature on the NE side:
− LOFD-002012 Cell Outage Detection and Compensation
− PLBFD-009001 Self-healing
− MLBFD-12000416 Cell Outage Detection
 Features on the element management system (EMS) side:
− WOFD-171000 Cell Outage Detection and Recovery - LTE TDD/FDD/NB-IoT
− WOFD-171200 Cell Outage Detection and Recovery - GBSS
− WOFD-171300 Cell Outage Detection and Recovery - WRAN
1.6 Definition
This section provides the definition related to the Cell Outage Management feature.
Cell outage refers to the situation in which services are inaccessible or key performance
indicators (KPIs) decrease greatly because of cell faults or alarms. It has huge impacts on the
network performance, especially, on user experiences on the single-frequency and single-RAT
networks.
The Cell Outage Management feature automatically detects the cell outage scenarios,
transfers subscribers to inter-frequency or inter-RAT neighboring cells, and forbids
subscribers from accessing or being handed over to outage cells, thereby achieving cell outage
compensation. This feature runs through the entire network lifecycle and is mainly used to
shorten the duration of serious network faults, such as cell outage.
1.7 Benefits
This section provides the benefits of the Cell Outage Management feature.
This feature can quickly detect outage cells. It reduces the loss of user experience through cell
outage compensation. It also improves the telecom operator image by shortening the cell
outage duration through recovery of the outage cells.

U2000
Cell outage compensation mechanism: The subscribers in outage cells are transferred to
normal cells during outage cell recovery and are transferred back after recovery.
1.8 Functions
The Cell Outage Management feature performs the following functions in sequence:
1. Monitors the status of cells on the network and identifies outage cells.
2. Adjusts cell services and transfers UEs performing services from an outage cell to a
functional cell, which involve barring the outage cell by setting CellAccess.CellBarred to
CELL_BARRED(Barred) and triggering handover of online UEs in the outage cell to
inter-frequency and inter-RAT neighboring cells. Barring a cell prevents new UEs from
accessing the cell and UEs in neighboring cells from being handed over to the cell.
3. Recovers an outage cell by reactivating the outage cell, restarting its base station, or
resetting its RRU or baseband board (pico base stations do not support RRU and baseband
board resetting).

U2000
Recovery 2 Cell Outage Detection Techniques
2 Cell Outage Detection Techniques
2.1 Possible Causes of Cell Outage

Possible causes of cell outage are as follows:
 NE software or hardware faults
− A fault may occur on a remote radio unit (RRU), radio frequency unit (RFU),
baseband board, common public radio interface (CPRI), feeder, or transport link of a
macro base station.
− A fault may occur on a BRU, board, feeder, or transport link of a micro base station.
NOTE
The eNodeB detects these types of faults and reports alarms. For details, see section 2.2.1 "Cell Outage
Detection Based on an Alarm."
 Unknown faults
Unknown faults are the software and hardware faults that cannot be detected by NEs and
do not trigger alarms, for example, faults on common channels or physical channels and
software and hardware defects.
2.2 Cell Outage Detection

This section describes the following four types of cell outage detection:
 Cell outage detection based on an alarm
 Cell outage detection based on a sleeping cell
 Cell outage detection based on an abnormal KPI
 Cell outage detection based on an internal audit
From SRAN9.0, the LTE supports all the four types of cell outage detection. However, the
GSM and UMTS support only Manually set sleeping cell detection (turn on adaptive
switch) in the category of cell outage detection based on a sleeping cell.
2.2.1 Cell Outage Detection Based on an Alarm

During software and hardware detection, when an eNodeB detects a fault that causes cell
unavailability, for example, a board, RF channel, or link fault, the eNodeB generates ALM-

U2000
29240 Cell Unavailable and reports a cell unavailability event to the U2000. After receiving
the event, the U2000 determines that the cell outage occurs because of cell unavailability.
In addition, the U2000 adds the cell in outage to the related list and displays the list. If the
fault causing cell unavailability has been rectified before or after a cell reset, the U2000
deletes the cell in outage from the list.
NOTE
The faults that cause cell unavailability seriously affect user experience. Therefore, to ensure reliability
of cell outage detection, the cell unavailability event and ALM-29240 Cell Unavailable are reported
through separate channels. The cell unavailability event is still reported even when ALM-29240 Cell
Unavailable is masked by O&M personnel or lost because of alarm storms. Then, the U2000 can detect
cells in outage based on the reported cell unavailability event. If ALM-29240 Cell Unavailable is
masked, O&M personnel cannot confirm and post-process information about cells in outage through the
alarm platform. Therefore, it is recommended that monitoring cell outage alarms be enabled.
In the scenario of multiple RRUs in one cell (pico base stations are not involved), if the
eNodeB finds an RRU unavailability fault (RF channel fault or link fault) when diagnosing
software and hardware, it generates ALM-29248 RF Out of Service and reports an "RRU
Unavailability Event" to the U2000. On receiving the event, the U2000 determines that the
RRU is in outage because of RRU unavailability.
The U2000 will add an RRU in outage due to RRU unavailability to a list of outage RRUs
and display the list on the GUI for user query. If the ALM-29248 RF Out of Service is cleared
before or after the RRU is reset, the U2000 deletes the RRU in outage from the list.
Table 2-1 Conditions for triggering and exiting RRU unavailability notification
Scenario Trigger Condition Exit Condition
Multi-RRU An RRU unavailability fault The RRU unavailability fault is rectified

cell occurs and the fault lasts for and the RRU functions normally for
more than 5 minutes. more than 5 minutes.
2.2.2 Cell Outage Detection Based on a Sleeping Cell

This section describes the cell outage detection based on a sleeping cell.
The U2000 determines whether a cell is a sleeping cell periodically. Table 2-2, Table 2-3, and
Table 2-4 describe the criteria for the U2000 to determine that a sleeping cell is an outage cell
during monitoring periods in different RATs.

U2000
Table 2-2 Criteria for the U2000 to determine that a sleeping cell is an outage cell during
monitoring periods (LTE)
Method KPI Outage Cell Criteria Example

Based on no- Number of For a period equal to the value of No- Detecting a
traffic period RRC traffic period threshold (h), a cell sleeping cell
connection meets the following conditions: whose no-
setup  The number of RRC connection traffic
attempts in a setup attempts is 0. period is
cell and overlong
 The number of UEs in connected
maximum
number of mode is 0.
UEs in a cell Monitoring period (s) and No-traffic
period threshold (h) (ranging from 2
hours to 168 hours) can be set by users
in the Parameters Setting window or
be calculated based on the traffic
volumes in the last three weeks and
preset parameters.
The value of the No-traffic period
threshold (h) parameter is determined
by the traffic volumes of detected cells
in the last three weeks. A small value
of the No-traffic period threshold (h)
parameter indicates a high traffic
volume in the last three weeks, and a
large value of the No-traffic period
threshold (h) parameter indicates a
low traffic volume in the last three
weeks.
Based on Number of For a consecutive traffic measurement Detecting a
abnormal RRC period (in hours), a cell meets the sleeping cell
incoming connection following conditions: without a
handovers setup  The number of RRC connection UE but with
attempts in a setup attempts and the number of neighbor
cell, the UEs in connected mode are 0. relationships
incoming and
 The incoming handover success rate
handover potential
success rate is 0 while the number of incoming incoming
in a cell, and handover attempts is not 0. handovers
maximum  The number of incoming handover
number of attempts during accumulated
UEs in a cell consecutive periods with abnormal
handovers is greater than 10.

U2000
monitoring periods (UMTS)

Based on Number of For a period specified by No-traffic period Detecting a
no-traffic RRC threshold (h) with the adaptive switch sleeping cell
period connection turned on, the number of RRC connection whose no-
setup attempts setup attempts in a cell is 0. traffic period
Values of the Monitoring period (s) and is overlong
No-traffic period threshold (h)
parameters are adaptively calculated by the
system. For details, see UMTS-related
descriptions.
monitoring periods (GSM)
Based on Number of For a period specified by No-traffic period Detecting a

no-traffic SD threshold (h) with the adaptive switch turned sleeping cell
period connection on, the number of SD connection setup whose no-
setup attempts attempts in a cell is 0. traffic period
Values of the Monitoring period (s) and No- is overlong
traffic period threshold (h) parameters are
adaptively calculated by the system. For
details, see GSM-related descriptions.
NOTE
The system adaptively calculates the monitoring period and no-traffic period for a cell. If the traffic
volume of this cell is ultra low in the last three weeks, the cell is considered as an ultra-low-traffic cell
and added in the list of ultra-low-traffic cells for users to view. Resources used for the system to monitor
cells will be wasted and incorrect detection information will be repeatedly reported if the system
monitors ultra-low-traffic cells with low or even zero traffic based on the sleeping cell detection for a
long period. In addition, cells with the low density of users and low traffic have minor impacts on
network KPIs and user experiences. Therefore, ultra-low-traffic cells are displayed in a list for users to
view.
Table 2-5 describes the scenarios where sleeping cell detection is not used for the U2000 to
determine that a cell is in outage.

U2000
Table 2-5 Scenarios where sleeping cell detection is not used for the U2000 to determine an
outage cell
Detection Method Cell Status

Sleeping cell A cell is barred.
detection In this case, UEs cannot initiate an RRC connection setup
procedure in this cell. Therefore, RRC-related KPIs are not used to
determine whether this cell is in outage.
A cell in the CellReservedForOp state is considered to be barred
during UE cell selection and reselection in some cases.
The duration in which a cell is unavailable due to manual, system,
or energy-saving reasons is not 0.
A cell has no traffic during the period that is not monitored.
The U2000 generates a list of outage cells and adds sleeping cells to the list. Then, it displays
the list on the client for users to view.
The U2000 obtains KPI data every hour. It determines whether a cell is recovered from outage
within the monitoring period. On an LTE network, if sleeping cell detection is performed
based on an adaptive traffic model, the U2000 determines whether a cell is recovered from
outage based on the calculated Monitoring period (s) and No-traffic period threshold (h)
parameter values with the adaptive switch turned on. If sleeping cell detection is performed
based on the preset Monitoring period (s) and No-traffic period threshold (h), the U2000
determines whether a cell is recovered from outage based on the user-defined Monitoring
period (s) and No-traffic period threshold (h) parameter values. On a GSM or UMTS
network, the U2000 determines whether a cell is recovered from outage based only on the
calculated Monitoring period (s) and No-traffic period threshold (h) parameter values with
the adaptive switch turned on. If the obtained data suggests that a cell is no longer a sleeping
cell, the U2000 removes the cell from the list of outage cells.
The U2000 also generates a list of ultra-low-traffic cells and adds ultra-low-traffic cells to this
list. Then, it displays the list on the client for users to view.
If the traffic in an ultra-low-traffic cell continuously increases, and based on the calculated
Monitoring period (s) and No-traffic period threshold (h) parameter values with the
adaptive switch turned on, this cell does not meet the conditions by which the system
determines a cell is an ultra-low-traffic cell, the cell is removed from the list of ultra-low-
traffic cells and monitored again.
2.2.3 Cell Outage Detection Based on an Abnormal KPI

This section describes the cell outage detection based on an abnormal KPI.
Cell Outage Detection Based on an Abnormal Basic KPI

The eNodeB detects outage cells by consecutively monitoring the same type of KPIs twice.
Especially, in the low traffic scenario, if the value of a KPI generated in one traffic
measurement period (on the eNodeB side) does not meet requirements, the system
accumulates this value and that generated in the next measurement period until the sum of the
values reaches the threshold. Then, the eNodeB performs cell outage detection. If the sum of
the values in 24 hours does not meet requirements, the eNodeB clears all data and detects

U2000
outage cells again. If any of the three types of KPIs in a cell is abnormal, the U2000 considers
this cell an outage cell until the KPIs become normal. Table 2-6 describes the three types of
KPIs and the scenarios where these KPIs are abnormal.
NOTE
The traffic measurement mentioned in this part is not dedicated for CODC.
The traffic measurement period mentioned in this section refers to the minimum traffic measurement
period other than the 5-minute period.
The eNodeB checks KPIs based only on reliable traffic statistics.
The traffic measurement period on the eNodeB is the same as that on the U2000. Therefore, you need to
calibrate the traffic measurement time when the eNodeB detects cells in outage for the first time after
this feature is activated. For example, if the subscribed minimum traffic measurement period on the
U2000 is 30 minutes, and the CODC task is subscribed at 02:12 in the morning, the eNodeB detects
cells in outage at 02:30 for the first time.
Table 2-6 Scenarios where KPIs are abnormal for outage cell detection
KPI Scenario Where KPIs Are Abnormal

RRC connection A cell meets the following conditions:
setup success rate  The number of RRC connection setup attempts is greater than
RRC Setup Number Threshold.
 The RRC connection setup success rate is lower than RRC
Setup Success Rate Threshold.
E-RAB setup success A cell meets the following conditions:
rate  The number of E-RAB connection setup attempts is greater
than E-RAB Setup Number Threshold.
 The E-RAB connection setup success rate is lower than E-RAB
Setup Success Rate Threshold.
Abnormal service A cell meets the following conditions:
drop rate  The number of E-RAB releases in the cell is greater than
Service Release Number Threshold.
 The abnormal service drop rate is greater than or equal to
Abnormal Release Rate Threshold.
The KPI calculation is based on E-RAB-level service drops. If an
E-RAB is unexpectedly released, the number of service drops is
counted once.
Users can set the thresholds for the three KPIs on the U2000 client. If any of the three KPIs of
a cell does not meet the requirements for their respective thresholds, the U2000 considers this
cell to be in outage.
Table 2-7 describes the scenarios where an abnormal KPI is not used for the U2000 to
determine that a cell is in outage according to Table 2-6.

U2000
Table 2-7 Scenarios where KPIs are not used for the U2000 to determine an outage cell
Detection Method Cell Status

Detection based on an A cell is in the state of intelligent power-off of carriers in the
abnormal KPI related to same coverage, carrier shutdown in low power consumption
RRC, E-RAB, and mode, and automatic power-off at a specified time when
abnormal service drop energy conservation and emission reduction is enabled.
rate For details, see Energy Conservation and Emission Reduction
Feature Parameter Description.
A cell is blocked.
A cell is barred.
In this case, UEs cannot initiate an RRC connection setup in
this cell. Therefore, RRC-related KPIs are not used to
determine whether this cell is in outage.
The U2000 adds outage cells whose KPIs are abnormal to the outage cell list, which is
displayed on the GUI for user to query. Before or after an outage cell is restarted, if the
counter values of a KPI within a number of consecutive measurement periods reach the
specified thresholds, the U2000 determines whether the abnormal KPI becomes normal. If the
KPI that causes the cell to be in outage becomes normal, the NE determines the cell is
restored and reports an outage cell restore event to the U2000. Then the U2000 deletes the cell
from the outage cell list. Table 2-8 describes the three types of KPIs and the scenarios where
these KPIs are abnormal.
Table 2-8 Scenarios where abnormal KPIs become normal for cell outage detection
KPI Scenario Where an Abnormal KPI Becomes Normal

RRC connection A cell meets the following conditions:
setup success rate  The number of RRC connection setup attempts is greater than
RRC Setup Number Threshold.
 The RRC connection setup success rate is higher than or equal
to the sum of RRC Setup Success Rate Threshold and 5%
(with the maximum value 100% even if the sum of RRC
Setup Success Rate Threshold and 5% is higher than 100%).
E-RAB setup A cell meets the following conditions:
success rate  The number of E-RAB connection setup attempts is greater
than E-RAB Setup Number Threshold.
 The E-RAB connection setup success rate is higher than or
equal to the sum of E-RAB Setup Success Rate Threshold
and 5% (with the maximum value 100% even if the sum of E-
RAB Setup Success Rate Threshold and 5% is higher than
100%).

U2000
KPI Scenario Where an Abnormal KPI Becomes Normal

Abnormal service A cell meets the following conditions:
drop rate  The number of E-RAB releases in the cell is greater than
Service Release Number Threshold.
 The abnormal service drop rate is lower than the difference
between Abnormal Release Rate Threshold and 5% (with
the minimum value 1% even if the difference between
Abnormal Release Rate Threshold and 5% is less than 1%).
Cell Outage Detection Based on an Abnormal Scheduled KPI

For KPIs that support customization, see chapter 5 "Counters."
In addition to the cell outage detection based on an abnormal basic KPI, the U2000 provides
the cell outage detection based on an abnormal scheduled KPI. Users can set KPI combined
rules on the U2000 such as "KPI Rules", "Abnormal KPI Duration", "Abnormal KPI
Frequency", and "Normal KPI Duration" to identify cell outage events in specific scenarios.
The U2000 lists the KPIs that can be selected on the GUI, and users can select required KPIs
and set KPI rules. Observe the following rules when you set KPI rules:
 The combined rule and calculation types include: and, or, >, <, =, >=, <=, basic operators
(+, -, x, /)
 A combined rule must not contain more than three subconditions; for example:
subcondition A and/or subcondition B and/or subcondition C.
 A combined rule must not involve more than 20 counters.
 A combined rule must not exceed 1024 characters in length with counters converted into
IDs.
 A combined rule cannot involve counters of different object types.
 Users can set up to 20 KPI combined rules on the U2000 but can activate 5 rules at most
at a time with each rule being determined independently.
 To avoid the ping-pong effect, the conditions for determining that a cell is in outage and
the conditions for determining that an outage cell is recovered are not set by simply
using the NOT operation when users set KPI combined rules. Instead, users must
independently set the conditions for determining that a cell is in outage and the
conditions for determining that an outage cell is recovered.
The eNodeB periodically reports the cell traffic statistics. On receiving the traffic statistics to
be saved in databases, the U2000 determines the cell outage status and takes actions based on
the preset combined rules:
 If a normally functioning cell meets the conditions for determining that a cell is in outage
as defined in a KPI combined rule, the U2000 determines that the cell is in outage and
displays the outage cell in the Outage Cell List window.
 If a cell in outage meets the conditions for determining that an outage cell is recovered as
defined in a KPI combined rule, the U2000 displays the cell in the Cleared Outage Cell
List window.

U2000
The calculation period for detecting abnormal user-defined KPIs is 1 hour. Users can subscribe to data of
performance measurement periods of shorter than 1 hour. The calculation period is valid only when all
data of each performance measurement period within a calculation period meets the operation rules. Due
to the system processing capability limitation, subscription to data of the 60-minute performance
measurement period is recommended.
2.2.4 Cell Outage Detection Based on an Internal Audit by

eNodeBs
This section describes the cell outage detection based on an internal audit by eNodeBs.
Based on the internal audit counters collected by eNodeBs every 5 minutes, the U2000
determines whether a cell is functional. An outage cell can be detected by monitoring the
internal audit counters for two consecutive periods based on the preset internal audit formula.
If the internal audit counters in a cell are abnormal, the U2000 considers this cell to be in
outage. The U2000 considers a cell to be in outage until the internal audit counters become
normal.
The eNodeB analyzes the internal audit counters based on the internal audit formula. The
purpose of the audit is to quickly and effectively detect outage cells based on certain
scenarios. Table 2-9 describes the scenarios where internal audit counters are abnormal for
outage cell detection.
Table 2-9 Scenarios where internal audit counters are abnormal for outage cell detection
Detection Internal Audit Scenario Where Internal Audit Counters
Method Counter Are Abnormal
Detection based  Number of The number of preambles for contention-based
on contention- preambles for access exceeds a certain amount of traffic
based access contention-based volume:
abnormalities access  More than half of the preambles are lost during
 Number of inter-layer transmission.
RARs  The number of preambles for contention-based
access is over two times that of RARs, or vice
versa.
Detection based  Number of RRC  The number of RRC Connection Request
on RRC Connection messages (excluding those for retransmissions)
connection setup Request exceeds a certain amount of traffic volume.
abnormalities messages  The number of RRC Connection Request
 Number of RRC messages is over two times that of RRC
Connection Connection Setup messages, or vice versa.
Setup messages
Users cannot modify the preceding internal audit counters for detecting outage cells in
eNodeBs on the U2000 client in non-flow-control scenarios (for details, see Flow Control)
because these counters are system-defined. If the counters of a cell in any of the preceding
two scenarios are abnormal, the U2000 considers this cell an outage cell.
The U2000 generates a list of outage cells and adds outage cells detected based on an
abnormal internal audit counter to the list. Within a complete internal auditing period before

U2000
or after the outage cell is reactivated, if the abnormal internal audit counter causing cell
outage meets the conditions described in Table 2-10, the eNodeB considers that this outage
cell becomes normal and reports an event showing the recovery of the cell to the U2000.
Then, the U2000 removes this cell from the list of outage cells. Table 2-10 describes the
counters and the scenarios where these abnormal counters become normal for outage cell
detection.
Table 2-10 Scenarios where abnormal internal audit counters become normal for outage cell
detection
Internal Audit Counter Scenario Where an Abnormal Internal Audit Counter

Becomes Normal
 Number of preambles for The number of preambles for contention-based access
contention-based access exceeds a certain traffic volume:
 Number of RARs  No more than half of the preambles are lost during inter-
layer transmission.
 The number of preambles for contention-based access is no
more than two times that of RARs, or vice versa.
 Number of RRC  The number of RRC Connection Request messages
Connection Request (excluding those for retransmissions) exceeds a certain
messages amount of traffic volume.
 Number of RRC  The number of RRC Connection Request messages is no
Connection Setup more than two times that of RRC Connection Setup
messages messages, or vice versa.
2.3 Service Adjustment for Outage Cells

Services in outage cells cannot function properly. Therefore, the U2000 must adjust the
services of the cells to prevent further performance deterioration after it determines that the
cells are in outage.
Currently, services in an outage cell are adjusted only on the LTE network but not on the
GSM and UMTS networks because the latter supports only the management of sleeping cells
which do not contain any services.
The Cell Outage Management feature adjusts services by performing the following
operations:
1. Isolating the outage cell to prevent UEs from accessing or being handed over to the cell
2. Transferring the UEs from the outage cell to its inter-frequency or inter-RAT neighboring
cells to prevent service drops or interruption
Isolating an outage cell involves the following operations:
 Preventing UEs from accessing the outage cell
 Eliminating UE mobility from neighboring cells to the outage cell
The eNodeB also retains the neighbor relationships between an outage cell and neighboring
cells to prevent ANR from incorrectly removing neighbor relationships.

U2000
The eNodeB implements the preceding operations by automatically changing parameter

values, as listed in Table 2-11.
Table 2-11 Parameter value changes for adjusting services of an outage cell
Operation Parameter ID Parameter Pre-Change Value Post-

Name (Default Value) Change
Value
Preventing UEs CellAccess.Cel Cell barring CELL_NOT_BARR CELL_BA
from accessing the lBarred state ED RRED
outage cell
Eliminating UE EutranIntraFr No PERMIT_HO_ENU FORBID_H
mobility from eqNCell.NoHo handover M O_ENUM
neighboring cells Flag indicator
to the outage cell EutranInterFr
eqNCell.NoHo
Flag
Retaining the EutranIntraFr No remove PERMIT_RMV_EN FORBID_R
neighbor eqNCell.NoRm indicator UM MV_ENU
relationships vFlag M
between the outage EutranInterFr
cell and its eqNCell.NoRm
neighboring cells vFlag
Services in an outage cell are adjusted in the following two phases:

 Before outage cell self-healing
The self-healing of an outage cell will affect services of UEs in connected mode in the
outage cell. Therefore, services in the outage cell need to be adjusted based on site
requirements.
 After outage cell self-healing
If an outage cell does not become functional for a long time after the self-healing, the
U2000 needs to adjust services of the outage cell and isolate it from other cells to prevent
further performance deterioration.
2.4 Restoration of Outage Cells and RRUs

If the outage cell list of the U2000 contains any outage cell or the outage RRU list contains
any outage RRU, the network maintenance personnel must locate the problem and try to
restore the cell or RRU promptly. Reactivating the cell, restarting the base station, or resetting
its RRU or baseband board are the commonly used methods to restore an outage cell.
Resetting the outage RRU can restore the RRU. Pico base stations are not configured with
RRUs. Therefore, no outage RRU list is provided for pico base stations, and pico base stations
do not support the reset of RRUs or baseband boards.
 Restoring outage cells
Based on the setting of the Outage cell recovery mode parameter, outage cells can be
restored or not restored as follows:

U2000
− Auto Recover: Once an outage cell is detected, the U2000 automatically reactivates
the cell to restore it.
− Recover After Manual Acknowledgement: Users need to confirm whether to
restore an outage cell by reactivating it or by resetting the base station, RRU, or
baseband board (if the fault is caused by any of them). Note that the base station,
RRU, and baseband board can be reset only manually.
Pico base stations do not support the reset of RRUs or baseband boards.
− Do Not Recover: The U2000 does not restore any outage cells.
 Restoring outage RRUs of base stations except pico base stations
Outage RRU restoration can be performed only manually through resetting.
You can reset an RRU without powering it off or by powering it off and then on.
When the outage cell is activated, you can restore it using either of the following method:
Reset the running RRU of the outage cell.
Reset the running baseband board of the outage cell.
When the outage cell is deactivated, you can restore the outage cell using either of the following
method:
Reset the RRU configured for the outage cell.
Reset the baseband board last used by the outage cell when it is activated.
When a cell is reactivated, the base station reconfigures the cell data and reapplies for cell
resources. If the cell is not restored after the reactivation, the U2000 will not reactivate the
cell again. When Auto isolate outage cells is selected, the U2000 isolates this cell, which
prohibits UEs from accessing the cell. In this case, the U2000 does not isolate this cell if the
cell restoration fails after reactivation.
Before the reactivation, the system automatically adjusts services of an outage cell because
UEs in connected mode may exist in the outage cell. After the reactivation, the system
automatically releases the cell from isolation and checks whether services in this cell can
become normal. If services are still abnormal, users can choose to isolate the cell as required,
and the system adjusts services again until the maintenance engineers manually restore this
cell. The preceding operations are available on the LTE network but unavailable on the GSM
and UMTS networks.
Resetting base stations can solve more complicated software failure problems than
reactivating cells. Therefore, users can reset base stations to restore outage cells if reactivating
the cells fails to restore them. You are advised to reset a base station only after all cells on this
base station are in outage. This ensures that services in normal cells are not affected.
Considering the large impact scope, the U2000 reactivates cells but not resets base stations in
the automatic mode. In this case, users have to reset base stations manually. In addition, the
system does not adjust services of outage cells during base station resetting.
If a base station except pico base stations encounters a cell outage problem, the possible cause
is that the RRU or baseband board of the base station is faulty. You can manually reset the
faulty RRU or baseband board to restore the outage cell. If an RRU is in outage, you can only
manually reset the RRU to restore it.

U2000
2.5 Suggestions on Handling Cell Outage

After a cell is in outage, users acknowledge information about the outage cell and handle cell
outage of different types using different methods.
 Cell in outage caused by an alarm
Users check ALM-29240 Cell Unavailable related to the outage cell by using the alarm
query function of the U2000, and acknowledge and handle the alarm. After the alarm is
cleared, users can check whether the outage cell is recovered.
 Cell in outage caused by a sleeping cell
Users need to collect and view KPIs of the past 72 or more hours within the time period
when a cell is in outage based on RATs, as described in Table 2-2, Table 2-3, and Table 2-
4. If the historical traffic became zero from the time the cell became outage, the cell is
likely to be a sleeping cell. In this case, users need to recover the cell immediately. If the
historical traffic of the cell fluctuates greatly, users need to delay the time required for
recovering the cell. After waiting for 2 to 3 hours, acknowledge traffic information again.
If there are still no services, recover the cell.
In addition, for an ultra-low-traffic cell or a cell that cannot be determined as a sleeping
cell with no traffic for a long time (where the collected historical traffic of the past 72 or
more hours fluctuates greatly and there is only a few users), perform a dialing test in the
center of the cell to determine whether services are properly accessed. If services are
accessed improperly, recover the cell immediately.
 Cell in outage caused by abnormal KPIs
Users need to collect and view related KPIs of the past 72 or more hours within the time
period when a cell is in outage based on abnormal KPIs. Table 2-6 and section 2.2.3
"Cell Outage Detection Based on an Abnormal KPI" describe the details about KPIs and
outage cell detection criteria in different scenarios. If KPIs are abnormal in the cell,
recover the cell immediately.
 Cell in outage caused by an internal audit
Users need to check KPIs related to the outage cell caused by sleeping cells and
abnormal KPIs. If KPIs fluctuate abnormally, such as the RRC setup success rate drops
suddenly and the cell status suddenly changes from with services to without services,
recover the cell immediately. If KPIs are normal, wait for 1 hour and check KPIs if the
outage cell has not been recovered. If KPIs fluctuate abnormally, recover the cell. If
KPIs are normal, contact Huawei technical support to acknowledge and locate the
problem.
Before the Cell Outage Management feature is enabled, some cells have become sleeping
cells. Therefore, their historical traffic meets the criteria for determining an ultra-low-traffic
cell. In such case, these cells are regarded as ultra-low-traffic cells when the U2000 detects
sleeping cells with the adaptive switch turned on. Therefore, besides troubleshooting outage
cells, users also need to perform routine health check on alarms, KPIs, and status of ultra-low-
traffic cells. If an ultra-low-traffic cell is determined to be in outage, users need to recover the
cell by referring to "Cell in outage caused by a sleeping cell" in this section. Otherwise, no
further operation is required.
2.6 Related Features

This section describes the prerequisite, mutually exclusive, and impacted features.

U2000
Prerequisite Features
None
Mutually Exclusive Features

None
Impacted Features
After cells are in outage on the LTE network, the Cell Outage Management feature is enabled
to adjust RRM parameters to prevent ANR from removing cells from their neighbor
relationships and to prevent UEs from being handed over to outage cells. For details about the
ANR feature, see ANR Management Feature Parameter Description.
An impacted feature is the feature affected by the Cell Outage Management feature on the LTE network
and it is not involved on the GSM and UMTS networks.
2.7 Network Impact

This section describes the impact of the Cell Outage Management feature on the network
from the perspectives of system capacity and network performance.
System Capacity
None
Network Performance
The Cell Outage Management feature allows telecom operators to detect outage cells that
affect network quality in different scenarios. In addition, this feature can automatically adjust
services of outage cells and perform recovery after an outage cell is detected. This helps
reduce the duration within which outage cells affect network services and KPIs and quickly
restore cell services.
However, this feature cannot ensure that all users are transferred out of outage cells although
it adjusts services before performing recovery to reduce the impacts on user experience and
network KPIs caused by the cell outage recovery.
Cell Outage Management transfers UEs from cells in outage using inter-frequency or inter-system
handovers. If an inter-frequency or inter-system neighboring cell is unavailable for a cell in outage, UEs
in this cell cannot be transferred. If an inter-frequency or inter-system neighboring cell is available for a
cell in outage, the UEs can be transferred only when they can detect the signals of the inter-frequency or
inter-system neighboring cells.
In this case, the triggered cell recovery such as reactivating the cell may cause a temporary
service interruption in an outage cell. This reduces the network KPIs of the outage cell.
Generally, the duration of service interruption is within 5 minutes.

U2000
Recovery 3 Engineering Guidelines
3 Engineering Guidelines
3.1 Preparation
The U2000 supports the Cell Outage Management feature on base stations of entire networks.
It is recommended that this feature be activated on the entire networks to monitor the possible
cell outage.
3.2 Required Information

This section describes the information you need to collect before network planning. The
required information is as follows:
 Network requirements for KPIs, such as RRC Setup Number, E-RAB Setup Number,
and Service Release Number
These KPIs are used as the thresholds for the U2000 to determine whether a cell is in
outage.
KPI Counter Recommended

Value
RRC Setup Number L.RRC.ConnReq.Att 20

E-RAB Setup Number L.E-RAB.AttEst 20
Service Release L.E-RAB.AbnormRel + 20
Number L.E-RAB.NormRel
 High-traffic hours, which are used to set the Monitoring period (s) and No-traffic period
threshold (h) parameters of the sleeping cell
By collecting the onsite high-traffic hours, you can manually configure parameters
related to sleeping cell detection.
You can set the thresholds and values for the preceding KPIs and parameters in the Cell
Outage Management window on the U2000 client. For details about these parameters, see
U2000 Product Documentation: Operation and Maintenance > RAN Management > SON
Management > CODR Management > CODR Reference.

U2000
3.3 Planning
N/A
3.4 Deployment
None
3.5 Deployment of the Cell Outage Management Feature

This section describes the procedure for you to deploy this feature.
3.5.1 Process
None
3.5.2 Requirements
Requirements for the Operating Environment
None
Requirements for the Transmission Topology

None
Requirements for Licenses

To use the Cell Outage Management feature, telecom operators must purchase the licenses
from Huawei. Table 3-1 lists the control items related to the licenses.
Table 3-1 License control items for Cell Outage Management
Feature ID Feature Name License Control Item NE
PLBFD-009001 Self-healing Self-healing Pico

WOFD-171000 Cell Outage Cell Outage Detection and U2000
Detection and Recovery - LTE TDD/FDD/NB-
Recovery - LTE IoT
TDD/FDD/NB-IoT
Detection and Recovery - WRAN
Recovery - WRAN
Detection and Recovery - GBSS
Recovery - GBSS

U2000
3.5.3 Precautions
Use the Auto Recover function with caution when multiple functions are used for similar
outage detection on LTE cells. Avoid the situation that an outage cell is restarted repeatedly
because cell outage is detected at different time.
For example, preset KPI detection finds an LTE cell's KPIs being abnormal using only 30
minutes while self-defined KPI detection finds the LTE cell's KPIs being abnormal using 1
hour. In this situation, the U2000 will restart the LTE cell separately for these two detections,
which affects user experience.
To avoid the preceding situation and facilitate observation, you are advised to use only one
cell outage detection method for an object to be detected such as the RRC setup success rate.
In this way, instead of being restarted repeatedly because of separate detections, the outage
cell is restarted for only once.
3.5.4 Hardware Adjustment

N/A
3.5.5 Initial Configuration

Step 1 On the U2000 client, choose SON > GSM Cell Outage Detection and Recovery, UMTS
Cell Outage Detection and Recovery, or LTE Cell Outage Detection and Recovery.
This section uses LTE Cell Outage Detection and Recovery as an example, as shown in
Figure 3-1.
Figure 3-1 LTE Cell Outage Detection and Recovery window
Step 2 Set eNodeBs you want to detect.

1. Choose Parameter Settings > Outage Cells > Base Station Monitoring.
The Select NE(s) pane is displayed, as shown in Figure 3-2.
2. Select eNodeBs for which you want to perform outage cell detection and click OK.
On an LTE network, if you select Auto monitor new eNodeBs, the U2000 automatically
monitors the added eNodeBs after the Cell Outage Detection and Recovery feature is enabled.

U2000
The Auto monitor new eNodeBs check box does not exist in the Set Base Station Monitoring dialog
box on a GSM or UMTS network because it applies only to eNodeBs.
Figure 3-2 Select NE(s) pane
Choose Parameter Settings > Outage RRU > RRU Monitoring. The Select RRU(s) pane is
displayed, as shown in Figure 3-3.

U2000
Figure 3-3 Select RRU(s) pane
On an LTE network, if you select Auto monitor all RRUs of new eNodeBs, the U2000
automatically monitors the added eNodeBs after the Cell Outage Detection and Recovery
feature is enabled.
NOTE
The Auto monitor all RRUs of new eNodeBs check box does not exist in the Select RRU(s) dialog
box on a GSM or UMTS network because it applies only to eNodeBs.
Step 3 Set parameters related to cell outage detection.

This section provides only the recommended configurations for parameters in different RATs.
For details about parameters and value ranges in different RATs, see U2000 Product
Documentation (Operation and Maintenance > RAN Management > SON Management >
CODR Management). Alternatively, you can press F1 on the U2000 client to invoke the
online help.
The recommended configurations for parameters in different RATs are as follows:
 Parameter configurations on the GSM network
Click , the Parameters Settings dialog box is displayed. After parameters are set, click
OK to enable the cell outage detection function.

U2000
Figure 3-4 shows the Parameters Settings dialog box on the GSM network.
Figure 3-4 Parameters Settings dialog box on the GSM network
Table 3-2 describes the parameters on the GSM network and recommended configurations.
Table 3-2 Recommended configurations for the parameters on the GSM network
Parameter Recommended Parameter Description

Name Configuration
Enable long- Select Enable After this parameter is selected, a cell that has no
time no-traffic long-time no- traffic for a long time is considered as a sleeping cell,
judgment traffic judgment and detection of sleeping cells in the corresponding
(Adaptive (Adaptive scenario can be enabled. Therefore, you are advised to
Setting) Setting). select this parameter.
Cell traffic Set this This parameter specifies the frequency that the U2000
model update parameter to calculates the values of parameters related to cell
period One week. outage detection, such as Monitoring period (s) and
No-traffic period threshold (h). In this parameter,
the adaptive switch is turned on and the unit is week.
In this case, a shorter update period indicates that the
calculated parameter values meet the latest traffic
condition more closely. In addition, the time that the
adaptive calculation is performed is specified based on
this parameter. In normal cases, the adaptive
calculation is performed at 00:15 on each Monday.
Therefore, the calculation operations increase in the
update period.

U2000

Name Configuration
Minimum no- Set this This parameter specifies the minimum period when a
traffic period parameter to 3. cell is determined to be a sleeping cell. A larger value
threshold (h) indicates a more accurate detection result.
Accordingly, the time required for detecting a sleeping
cell increases. A smaller value indicates a less
accurate detection result. Accordingly, the time
required for detecting a sleeping cell decreases.
Generate Deselect This parameter specifies the correlation between
alarm on cell Generate alarm outage cells and alarms. After this parameter is
outage on cell outage. selected, the U2000 generates related alarm
notification if a cell becomes in outage so that users
do not need to confirm the cell outage information
repeatedly in the CODR Management window. This
improves the operation efficiency.
Outage cell Set this This parameter specifies the outage cell recovery
recovery parameter to mode. In the automatic mode, the recovery may affect
mode Recover After user experience of UEs in connected mode in an
Manual outage cell. In this case, you are advised to manually
Acknowledgem acknowledge the cell by following the instructions
ent. provided in section 2.4 Restoration of Outage Cells
and RRUs when the cell is determined to be in outage.
 Parameter configurations on the UMTS network
Click , the Parameters Settings dialog box is displayed. After parameters are set, click
OK to enable the cell outage detection function.
Figure 3-5 shows the Parameters Settings dialog box on the UMTS network.

U2000
Figure 3-5 Parameters Settings dialog box on the UMTS network
Table 3-3 describes the parameters on the UMTS network and recommended configurations.
Table 3-3 Recommended configurations for the parameters on the UMTS network
Name Configuration
judgment traffic judgment and detection of sleeping cells in the corresponding
(Adaptive (Adaptive scenario can be enabled. Therefore, you are advised to
Setting) Setting). select this parameter.
update period.

U2000

Name Configuration
Minimum no- Set this This parameter specifies the minimum period when a
traffic period parameter to 3. cell is determined to be a sleeping cell. A larger value
threshold (h) indicates a more accurate detection result.
Accordingly, the time required for detecting a sleeping
cell increases. A smaller value indicates a less
accurate detection result. Accordingly, the time
required for detecting a sleeping cell decreases.
outage on cell outage. selected, the U2000 will notify users if a cell becomes
in outage so that users do not need to confirm the cell
outage information repeatedly in the CODR
Management window. This improves the operation
efficiency.
ent. provided in section 2.4 Restoration of Outage Cells
and RRUs when the cell is determined to be in outage.
 Parameter configurations on the LTE network

Figure 3-6 shows the basic Parameters Settings dialog box on the LTE network.

U2000
Figure 3-6 Basic Parameters node on the LTE network
Table 3-4 describes the basic parameters on the LTE network and recommended
configurations.
Table 3-4 Recommended configurations for the basic parameters on the LTE network

Name Configuration
Enable preset Select Enable This parameter specifies whether to enable preset KPI
KPI detection preset KPI detection. You are advised to select this parameter.
detection.
Enable Select Enable This parameter specifies whether to enable internal
internal audit internal audit. audit on the eNodeB side. You are advised to select
this parameter.
Enable Select Enable After this parameter is selected, a cell is considered as
incoming incoming a sleeping cell based on abnormal incoming
handover handover handovers, and detection of sleeping cells in the
abnormality abnormality corresponding scenario can be enabled. Therefore, you
judgment judgment. are advised to select this parameter.
Enable cell Select Enable This parameter specifies whether to enable alarm-
unavailability cell based cell/RRU outage detection. You are advised to
fault detection unavailability select this parameter.
fault detection.

U2000

Name Configuration
judgment traffic judgment. and detection of sleeping cells in the corresponding
scenario can be enabled. Therefore, you are advised to
select this parameter.
Adaptive Select Adaptive After this parameter is selected, the detection of
Settings Settings. sleeping cells based on long-time no traffic is
performed in adaptive mode. Users can customize the
detection parameter model based on the cell traffic
model to make the detection more accurate. Therefore,
you are advised to select this parameter. Adaptive
Settings and Manual Settings cannot be selected at
the same time. For details, see Table 2-2.
update period.
Minimum no- Set this This parameter indicates the minimum period that the
traffic period parameter to 3. U2000 detects a sleeping cell with the adaptive switch
threshold (h) turned on. On the network where traffic fluctuation
cells (cells whose traffic models change frequently)
exist, a larger value indicates a more accurate
detection result. Accordingly, the time required for
detecting a sleeping cell increases. A smaller value
indicates a less accurate detection result. Accordingly,
the time required for detecting a sleeping cell
decreases.
Manual Deselect After this parameter is selected, the detection of
Settings Manual sleeping cells based on long-time no traffic is
Settings. performed in manual mode. Users can set parameter
values in this mode. However, the U2000 detects
sleeping cells more accurately in adaptive mode.
Therefore, you are advised to deselect this parameter.
Adaptive Settings and Manual Settings cannot be
selected at the same time. For details, see Table 2-2.

U2000

Name Configuration
No-traffic Set this This parameter indicates the no-traffic period of the
period parameter to 96. outage cell in the manual setting scenario. A larger
value indicates a longer time required for detecting a
sleeping cell. Accordingly, a smaller value indicates a
shorter time that a cell is determined to be a sleeping
cell. You can configure and adjust this parameter
based on the high or low traffic period of cells on the
live network.
Monitoring Set the This parameter indicates the period that the sleeping
period (s) monitoring cell detection is performed in the manual setting
period to the scenario. Monitoring period (s) is used with No-
time from 8:00 traffic period (h) for detecting sleeping cells. You
to 20:00. can configure and adjust this parameter based on the
high or low traffic period of cells on the live network.
outage on cell outage. selected, the U2000 will notify users if a cell becomes
in outage so that users do not need to confirm the cell
outage information repeatedly in the CODR
Management window. This improves the operation
efficiency.
ent. provided in section 3.5 "Suggestions on Handling Cell
Outage" when the cell is determined to be in outage.
Auto isolate Deselect Auto This parameter specifies whether to isolate outage
outage cells isolate outage cells in the following scenarios:
cells.  Outage cells are not recovered within the estimated
cell recovery duration after Outage cell recovery
mode is set to Recover After Manual
Acknowledgement or Automatically Recover
and the cell self-healing is performed.
 Outage cell recovery mode is set to No Recovery.
For detailed operations, see section 2.3 "Service
Adjustment for Outage Cells." After this parameter is
selected, no NEs camp on or access the isolated cells.
Estimated cell Set this This parameter specifies the duration during which
recovery parameter to 2. outage cells are recovered after Outage cell recovery
duration (h) mode is set to Recover After Manual
Acknowledgement or Auto Recover. You can set
this parameter based on traffic volumes of cells on the
live network.
Value range: 2 to 168 (2 by default)

U2000
Configure preset KPI parameters on the LTE network in the LTE Cell Outage Detection and
Recovery dialog box, as shown in Figure 3-8.
Figure 3-7 Preset KPI Thresholds node on the LTE network
Table 3-5 Recommended configurations for preset KPI parameters on the LTE network

Name Configuration
RRC setup 20 This parameter indicates the number of RRC
number connection setup attempts. You are advised to set
the parameter based on the traffic measurement
period subscribed to on the eNodeB side.
 If the minimum traffic measurement period
subscribed to on the eNodeB side is 15
minutes, set this parameter to 20.
RRC setup 5% This parameter indicates the RRC connection
success rate (%) setup success rate. You are advised to set the
parameter to a value less than or equal to 10%.
E-RAB setup 20 This parameter indicates the number of E-RAB
number connection setup attempts. You are advised to set
the parameter based on the traffic measurement
period subscribed to on the eNodeB side.

U2000

Name Configuration
E-RAB setup 5% This parameter indicates the E-RAB connection
success rate (%) setup success rate. You are advised to set the
parameter to a value less than or equal to 10%.
Service release 20 This parameter indicates the number of service
number releases. You are advised to set the parameter
based on the traffic measurement period
subscribed to on the eNodeB side.
Abnormal 95% This parameter indicates the abnormal service
release rate (%) release rate. You are advised to set the parameter
to a value greater than or equal to 95%.
NOTE
For detailed operations, see RAN Management > SON Management > CODR Management > GUIs and
Parameters for CODR Management > Parameters for Adding a KPI Combination Rule in U2000
Online Help.

U2000
Figure 3-8 Settings of the abnormal scheduled KPIs for the LTE
----End
3.5.6 Activation Observation

This section describes the methods used to determine whether the Cell Outage Management
feature is effective.
The U2000 displays the detected outage cells that have not been restored in the Outage Cell
List area of the Outage Cells tab page and the restored cells in the Cleared Outage Cell List
area of the Outage Cells tab page, as shown in Figure 3-9.

U2000
When Waiting to Be Manually Started is displayed in the Task Status column of the outage
cell list, right-click a cell and choose Reactivate Cell, Reset Base Station, Reset RRU,
Reset RRU Through Power-off, Reset BBP, or Reset BBP Through Power-off as required.
(Only Reactivate Cell and Reset Base Station are available for pico base stations.)
Figure 3-9 Outage cells in the Outage Cell area
When outage cells are restored, the system automatically removes these cells from the
Outage Cell List area and adds them to the Cleared Outage Cell List area. If the system
cannot determine whether an outage cell is restored or mistakes a normal cell as an outage
cell, you can select this cell, right-click it, and choose Clear Outage Cell Info from the
shortcut menu. By doing this, this cell can be removed from the Outage Cell List area and
added to the Cleared Outage Cell List area.
 If the outage cell fails to be recovered by reactivating it, the U2000 will determine
whether to isolate the outage cell based on the setting of Auto isolate outage cells.
− If Auto isolate outage cells is selected, the U2000 isolates this cell if it is not
recovered within a specified period of time. After the cell is isolated, the U2000 no
longer determines whether the cell is recovered based on KPIs, and the cell will be
reserved in the Outage Cells area all along. After the outage cell is recovered
manually, you can right-click the cell and choose Clear Outage Cell Info from the
shortcut menu to remove the cell from the Outage Cells area.
− If Auto isolate outage cells is not selected, the U2000 will still determine whether
the cell is recovered. After the outage cell is recovered automatically or manually,
you can right-click the cell and choose Clear Outage Cell Info from the shortcut
menu to remove the cell from the Outage Cells area.
 When the system clears the task, it automatically releases the cell from isolation if the
cell has been isolated, for example, barring the cell and preventing UEs from accessing
the cell.
The U2000 does not perform sleeping cell detection for cells always with very low traffic,
because it is difficult for the U2000 to determine whether the low traffic is a normal situation
or not. Instead, the U2000 displays such cells on the Ultra-low Traffic Cells tab page, as
shown in Figure 3-10. Sleeping cell detection is performed in other cells with Manually set
sleeping cell detection (turn on adaptive switch) selected.

U2000
Figure 3-10 Ultra-low Traffic Cells tab page
The outage RRUs that have not been recovered are presented in Outage RRU List, and the
cleared outage RRUs are presented in Cleared Outage RRU List, as shown in Figure 3-11
(not involved for pico base stations).
Figure 3-11 Outage RRUs
If Generate alarm on cell outage is selected under Alarm Settings, alarm events related to
outage cells will be displayed in the Query Event Logs window.
In addition, you can view the information about Cell Outage and Restore Cell Outage events
in the SON logs. To view the LTE CODR SON logs, choose SON > SON Log and select LTE
Cell Outage Detection Log in the Log Category column, as shown in Figure 3-12.

U2000
Figure 3-12 SON logs
3.5.7 Deactivation
To deactivate the cell outage detection, perform the following steps:
Step 1 On the U2000 client, choose SON > GSM Cell Outage Detection and Recovery, UMTS
Cell Outage Detection and Recovery, or LTE Cell Outage Detection and Recovery.
The GSM Cell Outage Detection and Recovery, UMTS Cell Outage Detection and
Recovery, or LTE Cell Outage Detection and Recovery window is displayed.
Step 2 Deselect a base station
In this case, the cell outage detection is deactivated and the U2000 does not detect and handle
outage cells on this base station.
----End
3.6 Maintenance
This section provides the guidelines about how to maintain activated features.
Feature Monitoring and Evaluation

This section provides instructions on how to monitor and evaluate the Cell Outage
Management feature.
The U2000 checks the outage cells displayed in the Outage Cell area based on site
conditions. If some cells that are in outage but not detected or there is a high probability of a
normal cell being mistaken as in outage, you need to optimize and reset the improper
thresholds that cause these problems for some parameters.

U2000
Engineering Guidelines for Feature Parameters

This section provides the engineering guidelines for you to set parameters related to this
feature.
Parameters related to cell outage detection include monitoring periods, no-traffic period
thresholds, and KPI thresholds. If a cell outage decision is delayed or inaccurate (for example,
a normal cell is mistaken as in outage or some outage cells fail to be detected) due to
improper parameter settings, you need to adjust relevant parameters based on monitored base
station conditions. By default, you are advised to enable all monitor-related features to
maximize the algorithm performance.
3.7 Troubleshooting
Fault Description
No outage cells are displayed in the GSM Cell Outage Detection and Recovery, UMTS
Cell Outage Detection and Recovery, or LTE Cell Outage Detection and Recovery
window.
Fault Handling
To rectify the fault, perform the following steps:
Step 1 Check whether base stations are selected on the U2000.
Step 2 If base stations have been selected, proceed to Step 2. If not, select a base station in the GSM
Cell Outage Detection and Recovery, UMTS Cell Outage Detection and Recovery, or
LTE Cell Outage Detection and Recovery window.
Step 3 Check whether the time source of base stations is consistent with that on the U2000.
If it is consistent, proceed to Step 4. If it has not been set, set the time source of base stations
first.
Step 4 Check whether maintenance modes of the selected base stations are normal.
If yes, skip to Step 5. If no, proceed to Step 5 to set NE Mode to NORMAL.
Step 5 On the U2000 client, choose Maintenance > Maintenance Mode. In the displayed
Maintenance Mode window, click to query the maintenance modes of the selected
base stations. If maintenance modes are not NORMAL, click to set NE Mode to
NORMAL. Then, proceed to Step 6.
Step 6 Check the cell traffic.
If traffic of all cells does not meet the cell outage identification criteria, this situation is
normal. If some cells are in outage but fail to be reported, contact Huawei technical support.

U2000
Figure 3-13 Querying and setting maintenance modes
----End

U2000
Recovery 4 Parameters
4 Parameters
This chapter lists the parameters related to this feature on the U2000.
Table 4-1 describes parameters that are available on the GSM, UMTS, and LTE networks.
Table 4-1 Parameter description on the U2000 client (GSM, UMTS, and LTE)
Parameter Feature Feature Name Parameter Description

Name ID
Manually WOFD- Cell Outage Meaning: After this parameter is
set sleeping 171000 Detection and selected, the system monitors cells on
cell WOFD- Recovery - LTE the GSM, UMTS, and LTE networks
detection 171200 TDD/FDD/NB- with the adaptive switch turned on. The
(turn on IoT values of traffic models in each
adaptive WOFD- monitored cell are calculated adaptively.
171300 Cell Outage
switch) Detection and
Recovery - GBSS Manually set sleeping cell detection (turn
off adaptive switch) precedes Manually set
Cell Outage
sleeping cell detection (turn on adaptive
Detection and switch). When the former feature is enabled,
Recovery - WRAN you need to manually set the parameter for
cells on the LTE network. This does not
affect cells on the GSM and UMTS
networks.
GUI Value Range: ON (enabled), OFF
(disabled)
Actual Value Range: ON, OFF
Unit: None
Default Value: ON (enabled)

U2000

Name ID
Cell Traffic WOFD- Cell Outage Meaning: indicates the period of traffic
Model 171000 Detection and model update with the adaptive switch
Update WOFD- Recovery - LTE turned on.
interval 171200 TDD/FDD/NB- GUI Value Range: Not update, One
IoT week, Two weeks, Three weeks, and
WOFD-
171300 Cell Outage Four weeks
Detection and Actual Value Range: Not update, One
Recovery - GBSS week, Two weeks, Three weeks, and
Cell Outage Four weeks
Detection and Unit: None
Recovery - WRAN
Default Value: One week
Minimum no- WOFD- Cell Outage Meaning: The no-traffic period of traffic
traffic 171000 Detection and model with the adaptive switch turned
period WOFD- Recovery - LTE on cannot be lower than the minimum
threshold 171200 TDD/FDD/NB- no-traffic period (hour) threshold.
(h) IoT Otherwise, set the no-traffic period to
WOFD- this minimum no-traffic period
171300 Cell Outage
Detection and threshold.
Recovery - GBSS GUI Value Range: 1 to 12
Cell Outage Actual Value Range: 1 to 12
Detection and Unit: Hour
Recovery - WRAN
Default Value: 3
Generate WOFD- Cell Outage Meaning: After this parameter is
alarm on 171000 Detection and selected, the system generates an event
cell outage WOFD- Recovery - LTE alarm and displays the alarm in the
171200 TDD/FDD/NB- alarm management window when it
IoT detects an outage cell or the outage cell
WOFD- is restored.
171300 Cell Outage
Detection and GUI Value Range: ON (enabled), OFF
Recovery - GBSS (disabled)
Cell Outage Actual Value Range: ON, OFF
Detection and Unit: None
Recovery - WRAN
Default Value: OFF (disabled)

U2000

Name ID
Outage cell WOFD- Cell Outage Meaning: selects the outage cell
recovery 171000 Detection and recovery mode.
mode WOFD- Recovery - LTE GUI Value Range: Recover After
171200 TDD/FDD/NB- Manual Acknowledgement,
IoT Automatically Recover, or No
WOFD-
171300 Cell Outage Recovery
Detection and Actual Value Range: Recover After
Recovery - GBSS Manual Acknowledgement,
Cell Outage Automatically Recover, or No
Detection and Recovery
Recovery - WRAN Unit: None
Default Value: Recover After Manual
Acknowledgement
Table 4-2 describes parameters that are available only on the LTE network.
Table 4-2 Parameter description on the U2000 client (LTE only)

Name ID
Enable WOFD- Cell Outage Meaning: detects cell outage in the cell
internal 171000 Detection and you want to monitor on the LTE network
audit Recovery - LTE with the internal audit enabled.
TDD/FDD/NB- GUI Value Range: ON (enabled), OFF
IoT (disabled)
Unit: None
Enable WOFD- Cell Outage Meaning: enables preset KPI detection for
preset KPI 17100 Detection and the LTE cell you want to monitor
detection Recovery – LTE GUI Value Range: ON (enabled), OFF
(disabled)
Unit: None

U2000

Name ID
Enable cell WOFD- Cell Outage Meaning: enables alarm-based cell/RRU
unavailabilit 171000 Detection and outage detection for the LTE cell you want
y fault Recovery - LTE to monitor
detection TDD/FDD/NB- GUI Value Range: ON (enabled), OFF
IoT (disabled)
Unit: None
Enable WOFD- Cell Outage Meaning: detects outage cells in the cell
incoming 171000 Detection and you want to monitor on the LTE network
handover Recovery - LTE with the incoming handover abnormality
abnormality TDD/FDD/NB- judgment enabled.
judgment IoT GUI Value Range: ON (enabled), OFF
(disabled)
Unit: None
Manually WOFD- Cell Outage Meaning: After this parameter is selected,
set sleeping 171000 Detection and the system monitors cells on the LTE
cell Recovery - LTE network with the adaptive switch turned
detection TDD/FDD/NB- off. The values of traffic models in all
(turn off IoT monitored cells are set manually.
adaptive
switch) Manually set sleeping cell detection (turn off
adaptive switch) precedes Manually set
sleeping cell detection (turn on adaptive
switch). When this feature is enabled, you need
to manually set the parameter for cells on the
LTE network. This does not affect cells on the
GSM and UMTS networks.
GUI Value Range: ON (enabled), OFF
(disabled)
Unit: None
Default Value: OFF (disabled)
No-traffic WOFD- Cell Outage Meaning: calculates the no-traffic period
period 171000 Detection and of the monitored cell in a specified
threshold Recovery - LTE monitoring period. If the accumulated no-
(h) TDD/FDD/NB- traffic period in the cell is greater than the
IoT no-traffic period threshold, the cell is
determined to be a sleeping cell.
GUI Value Range: 1 to 720
Actual Value Range: 1 to 720
Unit: Hour
Default Value: 96

U2000

Name ID
Monitoring WOFD- Cell Outage Meaning: calculates the no-traffic period
period (s) 171000 Detection and of the monitored cell in a specified
Recovery - LTE monitoring period. If the accumulated no-
TDD/FDD/NB- traffic period in the cell is greater than the
IoT no-traffic period threshold, the cell is
determined to be a sleeping cell.
Unit: None
Default Value: 8 to 20
Estimated WOFD- Cell Outage Meaning: specifies the period of time the
cell 171000 Detection and OSS waits after the cell is automatically
recovery Recovery - LTE restarted. If the cell becomes normal
duration TDD/FDD/NB- before this timer expires, the OSS
IoT considers the cell restored. If not, the OSS
considers the cell still in outage.
Unit: hour
Default Value: 2

U2000
Recovery 5 Counters
5 Counters
The following performance counters support customization of abnormal KPIs.

<CODCCounters>
<GSM>
<Item CounterId="1278087417"
CounterName="K3100:Immediate Assignment Requests"
FunctionSubSetId="1275071435"
ObjectTypeId="1275069421" />
CounterName="R373:Cell Out-of-Service Duration"
</GSM>
<UMTS>
CounterName="Number of Processed RRC Connection Requests for Cell"
CounterName="Cell Unavailability Duration"
CounterName="Duration of Cell Unavailability Due to System Faults for
Cell"
CounterName="Duration of Cell Dynamic Shutdown Due to Automatic Shutdown
for Cell"
</UMTS>
<LTE>
CounterName="L.RRC.ConnReq.Att"
CounterName="L.RRC.ConnReq.Succ"

U2000
Recovery 5 Counters
CounterName="L.Traffic.User.Max"
CounterName="L.HHO.IntraeNB.PrepAttIn"
CounterName="L.HHO.IntereNB.PrepAttIn"
CounterName="L.Cell.Unavail.Dur.Sys"
CounterName="L.Cell.Unavail.Dur.Manual"
CounterName="L.Cell.Unavail.Dur.EnergySaving"
</LTE>
<LTERRUCounter>
CounterName="L.CellSectorEQUIP.SFN.DL.PRB.Used.Avg"
CounterName="L.CellSectorEQUIP.SFN.UL.PRB.Used.Avg"
CounterName="L.CellSectorEQUIP.SFN.UL.User.Avg"
CounterName="L.CellSectorEQUIP.SFN.DL.User.Avg"
CounterName="L.CellSectorEQUIP.SFN.E-RAB.SuccEst"
CounterName="L.CellSectorEQUIP.SFN.E-RAB.EstFail"
CounterName="L.CellSectorEQUIP.SFN.E-RAB.NormRel"

U2000
Recovery 5 Counters
CounterName="L.CellSectorEQUIP.SFN.E-RAB.AbnormRel"
CounterName="L.CellSectorEQUIP.SFN.RRC.ConnReq.Att"
CounterName="L.CellSectorEQUIP.SFN.RRC.SetupFail"
CounterName="L.CellSectorEQUIP.SFN.RRC.ConnReq.Succ"
</LTERRUCounter>
</CODCCounters>

U2000
Recovery 6 Reference Documents
6 Reference Documents
This chapter lists the reference documents related to the Cell Outage Management feature:
1. eNodeB Initial Configuration Guide
2. eNodeB KPI Reference
3. eNodeB MO Reference
4. eNodeB Performance Counter Reference
5. U2000 Product Documentation (Solaris10): Operation and Maintenance > RAN
Management > SON Management > CODR Management


Cell Outage Detection and Recovery (eRAN12.1 - 01)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Cell Outage Detection and Recovery (eRAN12.1 - 01)

Uploaded by

Copyright:

Available Formats

U2000

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2017-03-07) Huawei Proprietary and Confidential i

2 Cell Outage Detection Techniques ............................................................................................ 5

3 Engineering Guidelines ............................................................................................................. 19

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright © ii

3.5.6 Activation Observation ............................................................................................................................................ 33

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright © iii

1.2 Site Type Difference

1.3 Intended Audience

1.4 Change History

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 1

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 2

The Cell Outage Management feature involves the following features:

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 3

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 4

2 Cell Outage Detection Techniques

2.1 Possible Causes of Cell Outage

2.2 Cell Outage Detection

2.2.1 Cell Outage Detection Based on an Alarm

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 5

Scenario Trigger Condition Exit Condition

Multi-RRU An RRU unavailability fault The RRU unavailability fault is rectified

2.2.2 Cell Outage Detection Based on a Sleeping Cell

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 6

Method KPI Outage Cell Criteria Example

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 7

Method KPI Outage Cell Criteria Example

Method KPI Outage Cell Criteria Example

Based on Number of For a period specified by No-traffic period Detecting a

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 8

Detection Method Cell Status

2.2.3 Cell Outage Detection Based on an Abnormal KPI

Cell Outage Detection Based on an Abnormal Basic KPI

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 9

KPI Scenario Where KPIs Are Abnormal

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 10

Detection Method Cell Status

KPI Scenario Where an Abnormal KPI Becomes Normal

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 11

KPI Scenario Where an Abnormal KPI Becomes Normal

Cell Outage Detection Based on an Abnormal Scheduled KPI

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 12

2.2.4 Cell Outage Detection Based on an Internal Audit by

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 13

Internal Audit Counter Scenario Where an Abnormal Internal Audit Counter

2.3 Service Adjustment for Outage Cells

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 14

The eNodeB implements the preceding operations by automatically changing parameter

Operation Parameter ID Parameter Pre-Change Value Post-

Services in an outage cell are adjusted in the following two phases:

2.4 Restoration of Outage Cells and RRUs

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 15

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 16

2.5 Suggestions on Handling Cell Outage

2.6 Related Features

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 17

Mutually Exclusive Features

2.7 Network Impact

Generally, the duration of service interruption is within 5 minutes.

Issue 01 (2017-03-07) Huawei Proprietary and Confidential Copyright 18