Cell Outage Management (ERAN3.0 - 06)

Cell Outage Management
eRAN3.0
Feature Parameter Description
Issue 06
Date 2013-05-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2013. 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 the 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
eRAN
Cell Outage Management Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview......................................................................................................................................2-1
2.1 Overview of Sleeping Cell Detection ............................................................................................. 2-1
2.2 Overview of Cell Outage Management ......................................................................................... 2-1
2.2.1 Functions of the Cell Outage Management Feature ............................................................ 2-1
2.2.2 Possible Causes of Cell Outage ........................................................................................... 2-1
2.2.3 Cell Outage Detection Categories ........................................................................................ 2-2
3 Sleeping Cell Detection Techniques ....................................................................................3-1

3.1 Criterion for Sleeping Cell Identification ........................................................................................ 3-1
3.2 Process of Sleeping Cell Detection ............................................................................................... 3-1
3.3 Relationships with Other Features ................................................................................................ 3-2
3.4 Impact on KPIs .............................................................................................................................. 3-2
4 Cell Outage Detection Techniques .......................................................................................4-1

4.1 Cell Outage Detection ................................................................................................................... 4-1
4.1.1 Cell Outage Detection Based on an Alarm ........................................................................... 4-1
4.1.2 Cell Outage Detection Based on a Sleeping Cell ................................................................. 4-1
4.1.3 Cell Outage Detection Based on an Abnormal KPI .............................................................. 4-4
4.2 Service Adjustment for Outage Cells ............................................................................................ 4-6
4.3 Self-Healing of Outage Cells ......................................................................................................... 4-7
4.4 Relationships with Other Features ................................................................................................ 4-7
4.4.1 Load Control ......................................................................................................................... 4-7
4.4.2 ANR ...................................................................................................................................... 4-7
4.5 Impact on KPIs .............................................................................................................................. 4-7
5 Engineering Guidelines ...........................................................................................................5-1

5.1 When to Use Sleeping Cell Detection and Cell Outage Management .......................................... 5-1
5.1.1 When to Use Sleeping Cell Detection .................................................................................. 5-1
5.1.2 When to Use Cell Outage Management ............................................................................... 5-1
5.2 Information to Be Collected ........................................................................................................... 5-1
5.2.1 Sleeping Cell Detection ........................................................................................................ 5-1
5.2.2 Cell Outage Management..................................................................................................... 5-1
5.3 Network Planning .......................................................................................................................... 5-2
5.4 Overall Deployment Procedure ..................................................................................................... 5-2
5.5 Deploying Sleeping Cell Detection ................................................................................................ 5-2
5.5.1 Deployment Procedure ......................................................................................................... 5-2
5.5.2 Deployment Requirements ................................................................................................... 5-2
Issue 06 (2013-05-20) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
eRAN
Cell Outage Management Contents
5.5.3 Data Preparation................................................................................................................... 5-2

5.5.4 Precautions ........................................................................................................................... 5-3
5.5.5 Hardware Adjustment ........................................................................................................... 5-4
5.5.6 Initial Configuration ............................................................................................................... 5-4
5.5.7 Activation Observation .......................................................................................................... 5-4
5.5.8 Reconfiguration .................................................................................................................... 5-4
5.5.9 Deactivation .......................................................................................................................... 5-5
5.6 Deploying Cell Outage Management ............................................................................................ 5-5
5.6.1 Deployment Procedure ......................................................................................................... 5-5
5.6.2 Deployment Requirements ................................................................................................... 5-5
5.6.3 Data Preparation................................................................................................................... 5-5
5.6.4 Precautions ........................................................................................................................... 5-5
5.6.5 Hardware Adjustment ........................................................................................................... 5-5
5.6.6 Initial Configuration ............................................................................................................... 5-5
5.6.7 Activation Observation ........................................................................................................ 5-10
5.6.8 Reconfiguration .................................................................................................................. 5-11
5.6.9 Deactivation ........................................................................................................................ 5-11
5.7 Performance Optimization ........................................................................................................... 5-11
5.7.1 Sleeping Cell Detection ...................................................................................................... 5-11
5.7.2 Cell Outage Management................................................................................................... 5-12
5.8 Troubleshooting ........................................................................................................................... 5-12
6 Parameters..................................................................................................................................6-1
7 Counters ......................................................................................................................................7-1
8 Glossary ......................................................................................................................................8-1
9 Reference Documents .............................................................................................................9-1
Issue 06 (2013-05-20) Huawei Proprietary and Confidential ii

eRAN
Cell Outage Management 1 Introduction
1 Introduction
1.1 Scope
This document separately explains the principles and functions of sleeping cell detection and cell outage
detection. It also describes how to configure related parameters.
Any managed objects (MOs), parameters, alarms, or counters described in this document correspond to
the 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 Intended Audience

This document is intended for:
 Personnel who need to understand the sleeping cell detection feature
 Personnel who need to understand the cell outage management feature
 Personnel who work with Huawei Long Term Evolution (LTE) products
1.3 Change History

This section provides information about the changes in different document versions.
There are two types of changes, which are defined as follows:
 Feature change: refers to a change in the sleeping cell detection and cell outage management
features 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.
Document Issues
The document issues are as follows:
 06 (2013-05-20)
 05 (2012-12-29)
 04 (2012-09-20)
 03 (2012-06-30)
 02 (2012-05-11)
 01 (2012-03-30)
 Draft A (2012-01-10)
06 (2013-05-20)
Compared with issue 05 (2012-12-29) of eRAN3.0, issue 06 (2013-05-20) of eRAN3.0 includes the
following changes.
Change Change Description Parameter Change

Type
Feature None None
change
Editorial Modified the figure of M2000 Cell Outage Detection and None
Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-1

eRAN

Type
change Recovery. For details, see section 5.5.6 “Initial Configuration”.
Added the description about the value of the counters. For
details, see section 5.7.1 “Sleeping Cell Detection”.
05 (2012-12-29)
following changes.

Type
Feature Optimized cell outage detection based on a sleeping cell. For None
change details, see section 4.1.2 "Cell Outage Detection Based on a
Sleeping Cell."
Modified the initial configuration for outage cell detection, For
details, see section 5.6.6 "Initial Configuration."
Editorial Added troubleshooting. For details, see section 5.8 None
change "Troubleshooting."
04 (2012-09-20)
following changes.

Type
Feature Modified the scenarios where abnormal KPIs become normal None
change for outage cell detection. For details, see section 4.1.3 "Cell
Outage Detection Based on an Abnormal KPI."
Editorial Added descriptions for outage cell reactivation. For details, None
change see section 4.3 "Self-Healing of Outage Cells."
03 (2012-06-30)
following changes.

Type
Feature Modified the conditions for the abnormal KPIs causing cell None
change outage to become normal. For details, see section 4.1.3 "Cell
Outage Detection Based on an Abnormal KPI."

eRAN

Type
Editorial None None
change
02 (2012-05-11)
following changes.
Change Type Change Description Parameter Change

Feature change None None
Editorial change Changed the document name from Cell Outage None
Detection Feature Parameter Description to Cell
Outage Management Feature Parameter Description.
Revised the descriptions in Table 4-2 and Table 4-4. None
01 (2012-03-30)
This is the first official release.
Compared with draft A (2012-01-10) of eRAN3.0, issue 01 (2012-03-30) of eRAN3.0 includes the
following changes.

Feature change None None
Editorial change Revised chapter 5 "Engineering Guidelines." None
Draft A (2012-01-10)
This is a draft.
Compared with issue 01 (2011-09-15) of eRAN2.2, draft A (2012-01-10) of eRAN3.0 includes the
following changes.

Feature Updated the parameters displayed on the Changed parameters as follows:
change M2000 client. For details, see sections  Busy Hour has been changed to
4.1.2 "Cell Outage Detection Based on a Monitor Period NonIdleHour.
Sleeping Cell" and 4.2 "Service  Outage Cell Recovery Mode has
Adjustment for Outage Cells." been changed to Try Recovery
Strategy.
Editorial Optimized the descriptions in chapter 2 None
change "Overview."

eRAN

Optimized the organization and None
descriptions in chapter 4 "Cell Outage
Detection Techniques."

eRAN
Cell Outage Management 2 Overview
2 Overview
A cell may fail to provide services properly because of issues like environmental changes, eNodeB
hardware or software faults, and user misoperations. In this situation, network performance and service
quality deteriorate notably. To prevent this problem, networks must be monitored in real time to detect
sleeping cells and outage cells.
This document describes the following optional features:
 LOFD-002012 Cell Outage Detection and Compensation
 LOFD-002010 Sleeping Cell Detection
2.1 Overview of Sleeping Cell Detection

A sleeping cell is a cell where no traffic is carried for a continuous period because of environmental
changes, eNodeB hardware or software faults, or user misoperations. A sleeping cell is potentially a cell
that is in outage.
An eNodeB can detect sleeping cells by monitoring traffic-related counters in real time and report
sleeping cell alarms. The sleeping cell detection feature simplifies network maintenance and is critical in
maintaining the reliability and availability of LTE networks.
2.2 Overview of Cell Outage Management

This section describes the functions and categories of cell outage detection and also possible causes of
cell outage.
2.2.1 Functions of the Cell Outage Management Feature

Cell outage management performs the following functions in this sequence:
1. Monitors the status of cells in the network and identifies outage cells.
2. Transfers UEs performing services from an outage cell to a functional cell, which includes barring the
outage cell by setting CellAccess.CellBarred to CELL_BARRED(Barred).
Barring a cell prevents new UEs from accessing the cell and also prevents UEs from being handed
over to the cell.
3. Heals outage cells, which restores their services by reactivating them.
2.2.2 Possible Causes of Cell Outage

Possible causes of cell outage are as follows:
 Software or hardware faults in the eNodeB
A fault may reside in a remote radio unit (RRU), radio frequency unit (RFU), baseband board, common
public radio interface (CPRI) port, feeder, or transport link such as an S1 link.
NOTE
The eNodeB detects these types of fault and reports alarms. For details, see section 4.1.1 "Cell Outage Detection Based
on an Alarm."
 Unknown faults
Unknown faults are the software and hardware faults that cannot be detected by the eNodeB but
trigger alarms, for example, faults on common channels and physical channels and software and
hardware defects.

eRAN
Cell Outage Management 2 Overview
2.2.3 Cell Outage Detection Categories

Cell outage detection is categorized into cell outage detection based on an alarm, a sleeping cell, or an
abnormal key performance indicator (KPI). For details, see section 4.1 "Cell Outage Detection."

eRAN
Cell Outage Management 3 Sleeping Cell Detection Techniques
3 Sleeping Cell Detection Techniques

3.1 Criterion for Sleeping Cell Identification
If a cell has no traffic for a consecutive period within a specific duration, the cell is identified as a sleeping
cell. The duration is specified by the CellNoAccessAlmPara.NoAccessStartDetectTime and
CellNoAccessAlmPara.NoAccessStopDetectTime parameters, and the period is specified by the
CellNoAccessAlmPara.NoAccessDetectTimer parameter.
3.2 Process of Sleeping Cell Detection

Figure 3-1 shows the process of sleeping cell detection.
Figure 3-1 Process of sleeping cell detection
When sleeping cell detection is enabled, the eNodeB automatically performs the following operations, as
shown in Figure 3-1:

eRAN
Cell Outage Management 3 Sleeping Cell Detection Techniques
1. Starts the no-traffic detection timer when the no-traffic detection time specified by the
CellNoAccessAlmPara.NoAccessStartDetectTime parameter arrives.
The no-traffic detection timer specifies the time that the eNodeB calculates the number of UEs in a cell.
The value of the timer can be set through the CellNoAccessAlmPara.NoAccessDetectTimer
parameter.
2. Calculates the number of UEs in the cell.
The eNodeB calculates the number of UEs in the cell within the time specified by the
3. Determines whether the timer has expired.
The eNodeB determines whether the timer has expired according to the user-defined value of the
4. When the timer expires, checks whether the number of UEs within the timer length is 0, and then
performs subsequent operations as follows:
If... Then...
The number of UEs in the The eNodeB considers the cell to be a sleeping cell. In this case, the
cell is 0 eNodeB reports an ALM-29242 No Traffic Volume in the Cell alarm and
automatically reestablishes the cell.
The number of UEs in the The eNodeB does not consider the cell to be a sleeping cell. Then, the
cell is not 0 eNodeB recalculates the number of UEs in the cell and redetermines
whether the no-traffic detection timer has expired.
3.3 Relationships with Other Features

None
3.4 Impact on KPIs

The Sleeping Cell Detection feature has no impact on KPIs because there is no traffic in a sleeping cell.
In addition, an eNodeB reestablishes a cell only after detecting that there is no UE in the cell.

eRAN
Cell Outage Management 4 Cell Outage Detection Techniques
4 Cell Outage Detection Techniques

4.1 Cell Outage Detection
This section describes cell outage detection based on an alarm, a sleeping cell, or an abnormal KPI.
4.1.1 Cell Outage Detection Based on an Alarm

The eNodeB monitors the status of its hardware and software. If the eNodeB detects a fault, such as a
baseband board fault, a radio frequency (RF) channel fault, or a link fault, it reports an ALM-29240 Cell
Unavailable alarm to the M2000. The M2000 monitors this alarm at an interval of 30 minutes. If detecting
that this alarm is reported but not cleared, the M2000 considers this cell to be in outage because of an
alarm.
The M2000 generates a list of outage cells and adds outage cells detected based on an alarm to the list.
Users can view the list on the M2000 client. After the alarm is cleared, the M2000 removes this cell from
the list.
NOTE
If the M2000 cannot obtain the alarm information because an operator suppresses this alarm or due to alarm storms, the
eNodeB cannot determine an outage cell based on an alarm. If the function of cell outage detection based on an alarm is
enabled, it is recommended that the operator not suppress this alarm.
4.1.2 Cell Outage Detection Based on a Sleeping Cell

The M2000 periodically checks sleeping cells to determine whether they are outage cells. Table 4-1
describes the criteria for determining whether a sleeping cell is an outage cell.

eRAN
Table 4-1 Criteria for the M2000 to determine whether a sleeping cell is an outage cell
Method KPI Outage Cell Criteria Example
Based on traffic Number of RRC For the period specified by the Detecting a sleeping
volume connection setup No-traffic period (hours) cell whose monitoring
comparison attempts parameter with Manually set period and no-traffic
(L.RRC.ConnReq.Att) sleeping cell detection (turn period (in hours) can
and the number of on adaptive switch) selected, be calculated based on
UEs in connected a cell meets the following traffic volume
mode conditions: comparison
 The number of RRC
connection setup attempts is
0.
 The number of UEs in
connected mode is 0.
The monitoring period and
no-traffic period (in hours,
ranging from 2 hours to 168
hours) can be calculated based
on the traffic volumes in the last
three weeks and preset
parameters. A small value of
the No-traffic period (hours)
parameter indicates a high
traffic volume in the last three
weeks, and a large value of the
No-traffic period (hours)
parameter indicates a low traffic
volume in the last three weeks.
Based on Number of RRC For a period specified by the Detecting a sleeping
no-traffic period connection setup configurable No-traffic period cell based on the
attempts (hours) parameter, a cell meets preset No-traffic
(L.RRC.ConnReq.Att) the following conditions: period (hours) and
and the number of  The number of RRC Monitoring period(s)
UEs in connected connection setup attempts is parameters
mode 0.
 The number of UEs in
connected mode is 0.

eRAN
Method KPI Outage Cell Criteria Example

Based on Number of RRC For a consecutive traffic Detecting a sleeping
abnormal connection setup measurement period (in hours), cell without a UE but
incoming attempts a cell meets the following with neighboring
handovers (L.RRC.ConnReq.Att), conditions: relationships and
the number of UEs in  The number of RRC potential incoming
connected mode, and connection setup attempts is handovers
the incoming 0 and the number of UEs in
handover success connected mode is also 0.
rate
 The incoming handover
success rate is 0 while the
number of incoming handover
attempts is not 0.
 The number of incoming
handover attempts during
accumulated consecutive
periods with abnormal
handovers is greater than 10.
Without affecting the method of determining a sleeping cell based on abnormal incoming handovers, the
following limitations are imposed on the methods of determining a sleeping cell based on traffic volume
comparison and based on no-traffic periods:
 The methods of determining a sleeping cell based on traffic volume comparison and based on
no-traffic periods are mutually exclusive.
 If a cell is detected as an ultra-low-traffic cell by determining a sleeping cell based on traffic volume
comparison, this cell is added to the list of ultra-low-traffic cells. An ultra-low-traffic cell has
continuously low traffic (approximating to 0). Monitoring such a cell based on a sleeping cell for a long
period wastes system resources and results in repeated mistaken decisions. In addition, such a cell
provides a small number of services for only a few UEs, which insignificantly impacts KPIs and user
experience. Therefore, these cells are no longer monitored and added to the list of ultra-low-traffic
cells for reference.
NOTE
A cell is an ultra-low-traffic cell if this cell is a single-day low-traffic cell for consecutive seven days and the traffic empty
percentage in the last week is greater than 85%. Traffic empty percentage = Number of no-traffic hours in a week/Number
of traffic measurement hours x 100%.
A cell is a single-day low-traffic cell if the traffic in a single day of the last three weeks meets either of the following
conditions:
 The number of accumulated RRC connection setup requests is less than 48.
 The number of accumulated hours within which the number of RRC connection requests is 0 is greater than 12.
Table 4-2 describes the scenarios where an abnormal KPI is not used for determining that a cell is in
outage according to Table 4-1.

eRAN
Table 4-2 Scenarios where sleeping cell detection is not used for determining an outage cell
Detection Method Cell Status
Sleeping cell detection 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.
A cell is blocked.
A cell has no traffic during the period that is not monitored.
The M2000 generates a list of outage cells and adds sleeping cells to the list. Within the monitoring
period before or after the outage cell is reactivated, if the number of RRC connection setup requests is
not 0 or the number of UEs in connected mode is not 0, the M2000 removes the cell from the list of
outage cells.
The M2000 also generates a list of ultra-low-traffic cells and adds ultra-low-traffic cells to this list. If the
traffic of a cell continues to increase, this cell is monitored again at the next monitoring period, which is
specified by the Update interval parameter with Manually set sleeping cell detection (turn on
adaptive switch) selected.
4.1.3 Cell Outage Detection Based on an Abnormal KPI

By monitoring RRC-related counters, E-RAB-related counters, and abnormal service drop rates, the
eNodeB determines whether a cell is functional. E-RAB is short for E-UTRAN radio access bearer. The
eNodeB detects outage cells by monitoring the three types of KPI for two consecutive traffic
measurement periods. If any of the three types of KPI in a cell are abnormal, the M2000 considers this
cell to be in outage. The M2000 considers a cell to be in outage until the KPIs become normal. Table 4-3
describes the three types of KPIs and the outage cell criteria based on these KPIs.
Table 4-3 Outage cell criteria based on KPIs
KPI Outage Cell Criteria
RRC connection A cell meets the following conditions:
setup success rate  The number of successful RRC connection setup attempts
(with a large number (L.RRC.ConnReq.Att) is greater than RRC Setup Number Threshold.
of RRC connection
setup attempts)
 The RRC connection setup success rate is lower than RRC Setup Success
Rate Threshold.
RRC connection A cell meets the following conditions:
setup success rate  The number of successful RRC connection setup attempts
(with a small (L.RRC.ConnReq.Att) is less than or equal to RRC Setup Number
number of RRC Threshold.
connection setup
attempts)
 The RRC connection setup success rate is lower than RRC Setup Success
Rate Threshold.
 The number of successful RRC connection setup attempts during the
accumulated consecutive period with the preceding condition both met is
greater than twice the RRC Setup Attempt Threshold value.

eRAN
KPI Outage Cell Criteria

E-RAB setup A cell meets the following conditions:
success rate  The number of successful E-RAB setup attempts (L.E-RAB.SuccEst) is
greater than E-RAB Setup Number Threshold.
 The E-RAB 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 successful service releases (L.E-RAB.AbnormRel +
L.E-RAB.NormRel) in the cell is greater than Service Release Number
Threshold.
 The abnormal service drop rate is greater than Abnormal Release Rate
Threshold.
The KPI calculation is based on E-RAB-level service drops. If an E-RAB
experiences an abnormal service drop, the number of service drops is counted
once.
Users can set the thresholds for the three KPIs on the M2000 client. If any of the three KPIs of a cell
does not meet the requirement for their respective thresholds, the M2000 considers this cell to be in
outage.
Table 4-4 describes the scenarios where an abnormal KPI is not used for determining that a cell is in
outage according to Table 4-3.
Table 4-4 Scenarios where KPIs are not used for determining 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 same coverage,
abnormal KPI related to carrier shutdown in low power consumption mode, and automatic power-off
RRC, E-RAB, and at a specified time when energy conservation and emission reduction is
abnormal service drop 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 M2000 generates a list of outage cells and adds outage cells detected based on an abnormal KPI to
the list. Within the monitoring period before or after the outage cell is reactivated, if the abnormal KPI
causing cell outage meets the conditions specified in Table 4-5, the M2000 considers that the outage cell
becomes normal, and it removes the outage cell from the list of outage cells. Table 4-5 describes the
three types of KPI and the scenarios where these abnormal KPIs become normal.

eRAN
Table 4-5 Scenarios where abnormal KPIs become normal for outage cell detection
KPI Scenario Where an Abnormal KPI Becomes Normal
RRC connection The RRC connection setup success rate is higher than or equal to the sum of
setup success rate 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 The E-RAB setup success rate is higher than or equal to the sum of E-RAB
success rate 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%).
Abnormal service The abnormal service drop rate is lower than or equal to the difference
drop rate 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%).
4.2 Service Adjustment for Outage Cells

If a cell is displayed in the outage cell list on the M2000 client, network maintenance engineers must
identify and clear the fault. The cell outage management feature automatically adjusts the services of the
cell to prevent further performance deterioration 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 neighboring cells to prevent service
drops or interruption
NOTE
Service adjustment involves transferring UEs in connected or idle mode in outage cells and applies to only outage cells
that have been detected based on a sleeping cell or abnormal KPI. For outage cells that have been detected based on an
alarm, no such transfer is required because signals in the cells cannot be detected by any UE and no handover to the cells
can be performed.
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
 Retaining the neighbor relationships between the outage cell and its neighboring cells
To retain the neighbor relationships is to prevent ANR from mistakenly removing neighbor relationships.
The eNodeB implements the preceding operations by automatically changing parameter values, as
listed in Table 4-6.
Table 4-6 Parameter value changes for adjusting the services of an outage cell
Operation Parameter ID Parameter Pre-Change Value Post-Change Value
Name (Default Value)
Preventing UEs from CellAccess.C Cell barring CELL_NOT_BARRE CELL_BARRED
accessing the outage cell ellBarred state D

eRAN
Operation Parameter ID Parameter Pre-Change Value Post-Change Value

Name (Default Value)
Eliminating UE mobility EutranIntraFr No handover PERMIT_HO_ENUM FORBID_HO_ENUM
from the outage cell to its eqNCell.NoHo indicator
neighboring cells Flag
Retaining the neighbor EutranIntraFr No remove PERMIT_RMV_ENU FORBID_RMV_ENUM
relationships between the eqNCell.NoR indicator M
outage cell and its mvFlag
neighboring cells
After parameter values are automatically changed, users can view the new values on the M2000 client.
The M2000 provides the functions of automatic and manual service adjustment in outage cells by using
the service recover attempt policy, which can be configured by users.
4.3 Self-Healing of Outage Cells

Self-healing of outage cells involves reactivating these cells.
During cell reactivation, the eNodeB reconfigures cell data and re-requests cell resources. The M2000
attempts to restore outage cells by manually or automatically reactivating the cells. On the M2000 client,
users can configure a cell or modify the configuration of an outage cell.
After reactivating a cell, the eNodeB restores parameter settings of this cell and its neighboring cells to
its pre-isolation status and monitors this cell for cell outage detection. If the cell status is not recovered
from outage after two complete traffic measurement periods, outage cell isolation will be performed
again but cell reactivation will not be performed again. For details about outage cell isolation, see section
4.2 "Service Adjustment for Outage Cells."
When all the cells under an eNodeB are in outage, reactivate the eNodeB on an M2000 client to initialize
this eNodeB.
4.4 Relationships with Other Features

Cell outage management interacts with load control and automatic neighbor relation (ANR). Cell outage
management has the following interactions with these features:
4.4.1 Load Control

After detecting a cell outage, cell outage management adjusts radio resource management (RRM)
parameters to disable load balancing between the cell and its neighboring cells. This prevents UEs from
being handed over to the outage cell from the neighboring cells. For details about load control, see MLB
Feature Parameter Description.
4.4.2 ANR
After detecting a cell outage, cell outage management adjusts RRM parameters to prevent ANR from
removing the cell from its neighbor relationships and to prevent UE handovers to the cell. For details
about the ANR feature, see ANR Management Feature Parameter Description.
4.5 Impact on KPIs

The cell outage detection feature enables an operator to find out outage cells that affect the network
quality and to reduce the duration within which these cells affect network services and KPIs. This feature

eRAN
can detect outage cells within 30 minutes. In addition, this feature supports automatic service adjustment
and self-healing for these outage cells to quickly restore services.
However, not all UEs can be transferred out of outage cells although the feature adjusts services to
reduce the impacts on user experience and network KPIs before performing self-healing.
NOTE
The cell outage management feature transfers UEs out of outage cells through inter-frequency handovers only if UEs can
detect signals of inter-frequency neighboring cells. If a UE, for example a cell center user (CCU), cannot detect signals of
inter-frequency neighboring cells, it cannot be transferred.
Self-healing of an outage cell, such as reactivating a cell, may cause a temporary service interruption in
the outage cell. This deteriorates the network KPIs of the outage cell.
NOTE
The services are generally interrupted for 5 minutes or shorter.

eRAN
Cell Outage Management 5 Engineering Guidelines
5 Engineering Guidelines
This chapter provides engineering guidelines for sleeping cell detection and cell outage management.
5.1 When to Use Sleeping Cell Detection and Cell Outage

Management
After LOFD-002010 Sleeping Cell Detection is enabled, cells whose traffic fluctuates significantly or low
traffic cells may be considered as sleeping cells. These cells will be reactivated because of the simple
sleeping cell detection techniques.
After LOFD-002012 Cell Outage Detection and Compensation is enabled, a wider range of outage cells
including the preceding sleeping cells will be detected. Compared with sleeping cell detection techniques,
cell outage detection techniques are more accurate and apply to more outage cell detection scenarios.
Therefore, use sleeping cell detection and outage cell management as follows:
 If the conditions for enabling both sleeping cell detection and outage cell management are met, you
are advised to enable outage cell management. For details, see section 5.1.2 "When to Use Cell
Outage Management."
 If only sleeping cell detection is required, you are advised to enable sleeping cell detection. For details,
see section 5.1.1 "When to Use Sleeping Cell Detection."
5.1.1 When to Use Sleeping Cell Detection

A sleeping cell is potentially a cell that is in outage. It is recommended that this feature be activated when
cell outage detection function is disabled.
This feature is recommended when traffic volumes in the cell change slightly and the L.Traffic.User.Avg
counter is not 0.
This feature is not recommended in either of the following situations:
 Traffic volumes in the cell change significantly and the L.Traffic.User.Max counter is frequently 0.
 The cell outage management feature has been activated.
5.1.2 When to Use Cell Outage Management

All eNodeBs can be monitored for cell outage management on the M2000 client. However, to reduce
false alarms, cell outage detection is recommended for eNodeBs with heavy traffic (for example,
eNodeBs with more than 20 RRC connection setup requests per hour in average).
5.2 Information to Be Collected

5.2.1 Sleeping Cell Detection
Collect the traffic statistics of L.Traffic.User.Avg and L.Traffic.User.Max.
5.2.2 Cell Outage Management

Collect the following information for configuration:
 Network requirements for KPIs RRC Setup Success Rate, ERAB Setup Success Rate, and Service
Drop Rate
These KPIs are used as the thresholds for cell outage decisions.

eRAN
 High-traffic hours, which are used to set the Monitoring period(s) parameter
5.3 Network Planning

N/A
5.4 Overall Deployment Procedure

None
5.5 Deploying Sleeping Cell Detection

5.5.1 Deployment Procedure
None
5.5.2 Deployment Requirements

Sleeping cell detection has no requirements for the operating environment and transmission networking.
To use sleeping cell detection, operators must purchase and activate the following license.
Feature License Control Item Name

LOFD-002010 Sleeping Cell Detection Sleeping Cell Detection (FDD)
5.5.3 Data Preparation

This section describes generic data and scenario-specific data to be collected. Generic data is
necessary for all scenarios and must always be collected. Scenario-specific data is collected only when
necessary for a specific scenario.
There are three types of data sources:
 Network plan (negotiation required): Parameters are planned by operators and negotiated with the
EPC or peer transmission equipment.
 Network plan (negotiation not required): Parameters are planned and set by operators.
 User-defined: Parameters are set as required by users.
Generic Data
None
Scenario-specific Data
The following table describes the parameters that must be set in CellNoAccessAlmPara MOs to enable
no-traffic detection for cells.
Parameter Parameter ID Source Setting Description

Name
Local cell ID CellNoAccess Network plan This parameter specifies the local ID of a cell. It
AlmPara.Loca (negotiation uniquely identifies the cell within an eNodeB.
lCellId not required)

eRAN
Parameter Parameter ID Source Setting Description

Name
No access CellNoAccess Network plan This parameter specifies the timer for cell no-traffic
detect timer AlmPara.NoA (negotiation detection. If there is no traffic in the cell for the
ccessDetectTi not required) length of this timer during the period from
mer CellNoAccessAlmPara.NoAccessStartDetectTi
me to
CellNoAccessAlmPara.NoAccessStopDetectTi
me, ALM-29242 No Traffic Volume in the Cell is
reported and the cell is reset. If this parameter is
set to 0, the eNodeB does not perform cell
no-traffic detection. If this parameter is not set to 0,
the eNodeB performs cell no-traffic detection
throughout the period from the start time to the stop
time.
If the
me value equals the
CellNoAccessAlmPara.NoAccessStartDetectTi
me value, this parameter can be set to any value
within the value range of 1-72 (hours). If this
parameter is set to a valid value greater than 24, no
traffic detection can be performed for more than a
day.
No access CellNoAccess Network plan These parameters specify the start and stop time
detect start AlmPara.NoA (negotiation for cell no-traffic detection, respectively.
time ccessStartDet not required) If the
ectTime CellNoAccessAlmPara.NoAccessStopDetectTi
No access CellNoAccess Network plan me value is less than or equal to the
detect stop AlmPara.NoA (negotiation CellNoAccessAlmPara.NoAccessStartDetectTi
time ccessStopDet not required) me value, the detection ends at the time of the next
ectTime day specified by the
me parameter. No-traffic detection is performed in
the cell within the period specified by these
parameters if
CellNoAccessAlmPara.NoAccessDetectTimer is
not 0.
If the
CellNoAccessAlmPara.NoAccessStartDetectTi
me value does not equal the
me value, the difference between them must be
greater than the
CellNoAccessAlmPara.NoAccessDetectTimer
value.
5.5.4 Precautions
None

eRAN
5.5.5 Hardware Adjustment

Not involved
5.5.6 Initial Configuration

Configuring a Single eNodeB Using the GUI
Configure a single eNodeB using the Configuration Management Express (CME) graphical user
interface (GUI) based on the collected data described in section 5.5.3 "Data Preparation." For details,
see the procedure for configuring a single eNodeB on the CME GUI described in eNodeB Initial
Configuration Guide.
Configuring eNodeBs in Batches

To configure eNodeBs in batches, perform the following steps:
Step 1 On the GUI, set the parameters listed in the table for a specific scenario in this section, and save
the parameter settings as a user-defined template.
The parameters are the same as those described in section 5.5.3 "Data Preparation."
Step 2 Fill in the summary data file with the name of the user-defined template.
The parameter settings in the user-defined template will be applied to the eNodeBs after you import
the summary data file into the CME.
----End
For descriptions of the user-defined template and summary data file and also the detailed procedure for
configuring eNodeBs in batches, see eNodeB Initial Configuration Guide.
MO Parameter Group Name Parameter

CellNoAccess CELLNOACCESSALMPARA Local cell ID, No access detect start time, No
AlmPara access detect stop time, No access detect timer(h)
Configuring a Single eNodeB Using MML Commands

Run the MOD CELLNOACCESSALMPARA command to activate no-traffic detection.
5.5.7 Activation Observation

If the CellNoAccessAlmPara.NoAccessDetectTimer,
CellNoAccessAlmPara.NoAccessStartDetectTime, and
CellNoAccessAlmPara.NoAccessStopDetectTime values are valid and no UE accesses the cell
during the monitoring period, check whether the cell is reactivated. If it has been reactivated, the
sleeping cell detection feature is activated.
5.5.8 Reconfiguration
To improve accuracy of cell no-traffic detection, reconfigure
CellNoAccessAlmPara.NoAccessStartDetectTime and
CellNoAccessAlmPara.NoAccessStopDetectTime to values that fall into high-traffic periods.

eRAN
5.5.9 Deactivation
To deactivate the sleeping cell detection feature, set CellNoAccessAlmPara.NoAccessDetectTimer in
the CellNoAccessAlmPara MO to 0.
5.6 Deploying Cell Outage Management

5.6.1 Deployment Procedure
None
5.6.2 Deployment Requirements

Cell outage management has no requirements for the operating environment and transmission
networking.
To use cell outage management, operators must purchase and activate the following license.
Feature License Control Item Name

LOFD-002012 Cell Outage Detection and Cell Outage Detection and Compensation (FDD)
Compensation
5.6.3 Data Preparation

The following average counters need to be collected within a traffic measurement period for a cell in live
networks:
 Number of RRC connection setup attempts (L.RRC.ConnReq.Att)
 Number of successful E-RAB setup attempts (L.E-RAB.SuccEst)
 Number of successful service releases (L.E-RAB.AbnormRel + L.E-RAB.NormRel)
5.6.4 Precautions
None
5.6.5 Hardware Adjustment

Not involved
5.6.6 Initial Configuration

To check whether cell outage detection works correctly, perform the following steps:
Step 1 On the M2000 client, choose Maintenance > Cell Outage Detection and Recovery > Outage
Cells.
The Cell Outage Detection and Recovery Management window is displayed, as shown in Figure
5-1.

eRAN
Figure 5-1 Cell Outage Detection and Recovery Management window
Step 2 Click Set Base Station Monitoring. In the displayed dialog box as shown in Figure 5-2, select
eNodeBs where cell outage detection is to be activated, and then click OK.
Figure 5-2 Selecting eNodeBs for cell outage detection
Step 3 In the Cell Outage Detection and Recovery Management window, click Set Parameters. In
the displayed dialog box shown in Figure 5-3 and Figure 5-4, set the parameters for cell outage
detection, and click OK.
For details about these parameters, see Table 5-1 and Table 5-2.

eRAN
Figure 5-3 General tab page in the Parameters Settings dialog box
Table 5-1 Parameters on the General tab page in the Parameters Settings dialog box
Parameter Setting Description
Manually set sleeping cell After this parameter is selected, the M2000 periodically and adaptively
detection (turn on adaptive calculates the monitoring period and no-traffic period for each cell. You
switch) can also set the monitoring period and no-traffic period for each cell
manually.
To enable the monitoring period and no-traffic period to take effect, set
the following parameters:
 Select this mandatory parameter for sleeping cell detection.
 Clear Manually set sleeping cell detection (turn off adaptive
switch) on the Advanced (LTE Only) tab page.
Update interval This parameter specifies the interval for updating the traffic model for
sleeping cell detection. This parameter initially takes effect at 00:00 of
the next Monday, and then it periodically updates at 0:00 of every
Monday.
Minimum no-traffic period This parameter specifies the minimum no-traffic period that is calculated
(hour) based on adaptive sleeping cell detection.
Generate alarm on cell This parameter specifies whether an alarm is reported to the M2000 after
outage a cell in outage is detected.
Outage cell recovery Set this parameter to Automatically Recover, Recover After Manual
mode Acknowledgement, or No Recovery.

eRAN
Figure 5-4 Advanced (LTE Only) tab page in the Parameters Settings dialog box
Table 5-2 Parameters on the Advanced (LTE Only) tab page in the Parameters Settings dialog box
RRC Setup Number Increase the value of this parameter if a cell cannot be considered in
outage when both of the following conditions are met:
 The number of successful RRC connection setup attempts is
greater than the value of the RRC Setup Number Threshold
parameter.
 The RRC connection setup success rate is lower than the value of
the RRC Setup Success Rate Threshold parameter.
Otherwise, decrease the value of RRC Setup Number Threshold.
A large parameter value results in a high probability of some cell
outages failing to be detected. A small parameter value leads to a
high probability of a normal cell being mistaken as in outage.
RRC Setup Success Rate If a cell cannot be considered in outage when the RRC connection
(%) setup success rate is slightly lower than the parameter value,
decrease the value of this parameter. Otherwise, increase the value.
A large parameter value results in a high probability of a normal cell
being mistaken as in outage. A small parameter value leads to a high
probability of some cell outages failing to be detected.

eRAN

E-RAB Setup Number Increase the value of this parameter if a cell cannot be considered in
 The number of successful E-RAB setup attempts is greater than the
value of the E-RAB Setup Number Threshold parameter.
 The E-RAB setup success rate is lower than the value of the E-RAB
Setup Success Rate Threshold parameter.
Otherwise, decrease the value of E-RAB Setup Number Threshold.
E-RAB Setup Success Rate If a cell cannot be considered in outage when the E-RAB setup
(%) success rate is slightly lower than the parameter value, decrease the
value of this parameter. Otherwise, increase the value.
A large parameter value results in a high probability of a normal cell
being mistaken as in outage. A small parameter value leads to a high
probability of some cell outages failing to be detected.
Service Release Number Increase the value of this parameter if a cell cannot be considered in
 The number of normal service releases is greater than the value of
the Service Release Number Threshold parameter.
 The service drop rate is higher than the value of the Abnormal
Release Rate Threshold parameter.
Otherwise, decrease the value of Service Release Number
Threshold.
Abnormal Release Rate (%) If a cell cannot be considered in outage when the service drop rate is
slightly higher than the parameter value, decrease the value of this
parameter. Otherwise, increase the value.
Enable incoming handover This parameter specifies whether to enable detection of a sleeping
abnormality judgment cell based on abnormal incoming handovers.
Manually set sleeping cell Select this parameter to disable the adaptive monitoring period
detection (turn off adaptive algorithm and to specify the monitoring period manually.
switch) To enable the monitoring period and no-traffic period to take effect,
set the following parameters:
 Select the mandatory parameter Manually set sleeping cell
detection (turn on adaptive switch) on the General tab page for
sleeping cell detection.
 Select Manually set sleeping cell detection (turn off adaptive
switch).

eRAN

No-traffic period (hour) This parameter specifies the maximum accumulated no-traffic period
for determining an outage cell within the monitoring period.
Monitoring period(s) This parameter is valid only for cell outage detection based on a
sleeping cell.
The parameter setting is closely related to user behaviors. When
abnormal values are identified during the period that should not be
monitored but has been specified for the KPIs "Number of RRC
connection setup attempts" and "Number of UEs in connected mode,"
some cells may be mistaken as in outage. When these two KPIs are
not monitored during the period that should be monitored but fails to
be specified, some cell outages may fail to be detected or cell outage
decisions may be delayed.
Reset this parameter when non-low-traffic hours change due to a
change in the surrounding environment or user behavior.
5.6.7 Activation Observation

Cell outage detection can be observed using the list of outage cells and outage cell alarm log as follows:
 If a cell in the selected eNodeBs is considered in outage based on an alarm or an abnormal KPI, the
eNodeB sends information about the cell outage to the M2000. The outage cell will be displayed in the
Cell Outage Detection and Recovery Management window, as shown in Figure 5-5. This indicates
that cell outage detection is activated.
Figure 5-5 Reported cell outage information
If a cell in outage is detected based on an abnormal KPI, right-click this cell in the list of outage cells
and choose Reactivate Cell to reactivate this cell, the M2000 adjusts services of this outage cell. For
details, see section 4.2 "Service Adjustment for Outage Cells." You can also right-click this cell and
choose Reset BS to reset the associated eNodeB.
 If Generate alarm on cell outage is selected under Alarm Settings, cell outage will be displayed in
the Query Event Logs window for cells in outage, as shown in Figure 5-6.

eRAN
Figure 5-6 Query Event Logs window
----End
5.6.8 Reconfiguration
Reconfigure parameters according to Table 5-1 and Table 5-2.
5.6.9 Deactivation
To deactivate cell outage detection, perform the following steps:
Step 1 On the M2000 client, choose Maintenance > Cell Outage Detection and Recovery > Outage
Cells.
Step 2 In the Cell Outage Detection and Recovery Management window as shown above in Figure
5-1, click the Set Base Station Monitoring button.
Step 3 In the Set Monitored Base Station dialog box as shown above in Figure 5-2, clear the check
boxes for the eNodeBs where cell outage detection is to be deactivated, and click OK.
----End
5.7 Performance Optimization

5.7.1 Sleeping Cell Detection
Monitoring
After this feature is enabled, check the values of the two counters listed in the following table. If the
values are both 0, determine whether to adjust the related parameters.
Object Type Counter Name

Counter Cell measurement L.Traffic.User.Avg
L.Traffic.User.Max

eRAN
Parameter Optimization
If current traffic is heavy, that is, the value of the L.Traffic.User.Avg counter increases, set
CellNoAccessAlmPara.NoAccessDetectTimer to a larger value.
If current traffic is light, that is, the value of the L.Traffic.User.Avg counter decreases, set
CellNoAccessAlmPara.NoAccessDetectTimer to a smaller value.
If current traffic fluctuates, and the value of the L.Traffic.User.Max counter is frequently equal to 0, set
CellNoAccessAlmPara.NoAccessDetectTimer to 0 to disable the feature.
5.7.2 Cell Outage Management

Monitoring
With cell outage management activated, a cell is considered in outage and the eNodeB reports the
information to the M2000 if the KPIs (such as RRC Setup Success Rate, ERAB Setup Success Rate,
and Service Drop Rate) reach their respective thresholds. If some outage cells fail to be added to the
outage cell list or there is a high probability that the list contains false outage cells, some thresholds may
be configured incorrectly. To solve the problem, reconfigure the thresholds. Table 5-1 and Table 5-2
describe the thresholds, and Figure 5-3 and Figure 5-4 show the dialog boxes for configuring the
thresholds.
 Cell outage detection accuracy can be evaluated based on the changes of KPIs before and after the
cell outage detection time.
 The effectiveness of self-healing of outage cells can be evaluated based on the changes of KPIs
before and after the self-healing operation.
The KPIs to be evaluated are selected based on cell outage detection scenarios. For details, see Table
4-1 and Table 4-3.
Parameter Optimization
The parameters related to cell outage detection include monitoring periods and KPI thresholds. If a cell
outage decision is delayed or inaccurate (for example, a normal cell is mistaken as in outage or some
cell outages fail to be detected) due to improper settings of monitoring periods or KPI thresholds, adjust
the relevant parameters. Table 5-1 describes the parameters related to cell outage detection.
5.8 Troubleshooting
This section describes how to troubleshoot the problem that no outage cell is displayed in the Cell
Outage Detection and Recovery window.
Fault Description
No outage cell is displayed in the Cell Outage Detection and Recovery window.
Fault Handling
To rectify the fault, perform the following steps:
Step 1 Check whether the eNodeBs are selected on the M2000. If the eNodeB have been selected, go
to Step 2. If not, select the eNodeBs by referring to Step 2 in 5.6.6 "Initial Configuration."
Step 2 Check whether the clock sources of the eNodeBs and the M2000 client are the same. If yes, go
to Step 3. If no, set the clock sources of the eNodeBs to that of the M2000 client.
Step 3 Check whether the eNodeB maintenance modes are normal. If yes, go to Step 5. If no, perform
operations according to Step 4 to set NE Mode to NORMAL.

eRAN
Step 4 On the M2000 client, choose Maintenance > Maintenance Mode. In the displayed
Maintenance Mode window, click the Query Maintenance Mode button to query maintenance modes
of the selected eNodeBs. If the modes are not NORMAL, click the Set Maintenance Mode button to set
NE Mode to NORMAL. Then, go to Step 5.
Step 5 Check the cell traffic. If the traffic of all cells does not meet the cell outage criteria, these cells
are normal. If some cells are in outage but fail to be detected, contact Huawei technical support.
Figure 5-7 Maintenance Mode tab page

eRAN
Cell Outage Management 6 Parameters
6 Parameters
Table 6-1 Parameter description
MO Parameter ID MML Feature ID Feature Description
Command Name
CellAcces CellBarred MOD LBFD-001001 / 3GPP R8 Meaning:Indicates whether

s CELLACCESS TDLBFD-001001 Specificatio the cell is barred. If the cell is
ns barred, the UE cannot camp
LST LBFD-002009 / on the serving cell. During cell
CELLACCESS TDLBFD-002009 Broadcast reselection, the serving cell is
of system
LBFD-00201803 / information not selected as a candidate
TDLBFD-002018 cell.
03 Cell GUI Value
Selection Range:CELL_BARRED(Barre
LOFD-002012 / and
TDLOFD-002012 Reselection d), CELL_NOT_BARRED(Not
Barred)
Cell Outage Unit:None
Detection
and Actual Value
Compensat Range:CELL_BARRED,
ion CELL_NOT_BARRED
Default
Value:CELL_NOT_BARRED(
Not Barred)
CellNoAcc LocalCellId LST LOFD-002010 Sleeping Meaning:Indicates the local ID

essAlmPa CELLNOACCE Cell of the cell. It uniquely
ra SSALMPARA Detection identifies a cell within a BS.
MOD GUI Value Range:0~17
CELLNOACCE
SSALMPARA Unit:None
Actual Value Range:0~17
Default Value:None
CellNoAcc NoAccessDete MOD LOFD-002010 Sleeping Meaning:Indicates the length

essAlmPa ctTimer CELLNOACCE Cell of the timer for the cell
ra SSALMPARA Detection no-traffic detection. If there is
no traffic in the cell within the
LST duration specified by this
CELLNOACCE parameter, the eNodeB
SSALMPARA reports the no-access alarm
and resets the cell. If this
parameter is set to 0, the cell
no-traffic detection is not
performed. If the timer for
reporting the no-traffic alarm is
set to a non-zero value, the
eNodeB performs the cell
no-traffic detection from the

eRAN

Command Name
start time to the stop time.
GUI Value Range:0~72
Unit:h
Actual Value Range:0~72
Default Value:0
CellNoAcc NoAccessStart MOD LOFD-002010 Sleeping Meaning:Indicates the time

essAlmPa DetectTime CELLNOACCE Cell when the cell no-traffic
ra SSALMPARA Detection detection starts. If the stop
time is earlier than or the
LST same as the start time, the
CELLNOACCE end time is assumed to be a
SSALMPARA time of the next day. If the
timer for reporting the
no-traffic alarm is not set to 0,
the eNodeB performs the cell
GUI Value
Range:00:00:00~23:59:59
Unit:None
Actual Value
Range:00:00:00~23:59:59
Default Value:00:00:00
CellNoAcc NoAccessStop MOD LOFD-002010 Sleeping Meaning:Indicates the time

essAlmPa DetectTime CELLNOACCE Cell when the cell no-traffic
ra SSALMPARA Detection detection stops. If the stop
time is earlier than or the
LST same as the start time, the
CELLNOACCE stop time is assumed to be a
SSALMPARA time of the next day. If the
timer for reporting the
no-traffic alarm is not set to 0,
the eNodeB performs the cell
GUI Value
Range:00:00:00~23:59:59
Unit:None
Actual Value
Range:00:00:00~23:59:59
Default Value:00:00:00

eRAN

Command Name
EutranIntr NoHoFlag ADD LBFD-00201801 / Coverage Meaning:Indicates whether

aFreqNCe EUTRANINTRA TDLBFD-002018 Based handovers of UEs to the
ll FREQNCELL 01 Intra-freque neighboring cell are
ncy prohibited.
MOD LOFD-002001 / Handover
EUTRANINTRA TDLOFD-002001 GUI Value
FREQNCELL Automatic Range:PERMIT_HO_ENUM(
LOFD-002002 / Neighbour Permit Ho),
LST TDLOFD-002002 Relation FORBID_HO_ENUM(Forbid
EUTRANINTRA (ANR) Ho)
FREQNCELL LOFD-002012 /
TDLOFD-002012 Inter-RAT Unit:None
ANR
Actual Value
Cell Outage Range:PERMIT_HO_ENUM,
Detection FORBID_HO_ENUM
and
Compensat Default
ion Value:PERMIT_HO_ENUM(P
ermit Ho)
EutranIntr NoRmvFlag ADD LOFD-002001 / Automatic Meaning:Indicates whether to

aFreqNCe EUTRANINTRA TDLOFD-002001 Neighbour permit or prohibit removal of
ll FREQNCELL Relation the neighboring relationship
LOFD-002002 / (ANR) by ANR.
MOD TDLOFD-002002
EUTRANINTRA Inter-RAT GUI Value
FREQNCELL LOFD-002012 / ANR Range:PERMIT_RMV_ENUM
TDLOFD-002012 (Permit ANR Remove),
LST Cell Outage FORBID_RMV_ENUM(Forbid
EUTRANINTRA Detection ANR Remove)
FREQNCELL and
Compensat Unit:None
ion
Actual Value
Range:PERMIT_RMV_ENUM
, FORBID_RMV_ENUM
Default
Value:PERMIT_RMV_ENUM(
Permit ANR Remove)

eRAN
Cell Outage Management 7 Counters
7 Counters
There are no specific counters associated with this feature.

eRAN
Cell Outage Management 8 Glossary
8 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

eRAN
Cell Outage Management 9 Reference Documents
9 Reference Documents
This chapter lists the reference documents related to cell outage management:
[1] Connection Management Feature Parameter Description
[2] MLB Feature Parameter Description
[3] Admission and Congestion Control Feature Parameter Description
[4] ANR Management Feature Parameter Description
[5] Energy Conservation and Emission Reduction Feature Parameter Description
[6] eNodeB Performance Counter Reference
[7] eNodeB MO Reference
[8] eNodeB KPI Reference
[9] eNodeB Initial Configuration Guide


Cell Outage Management (ERAN3.0 - 06)

Uploaded by

Copyright:

Available Formats

You might also like

Cell Outage Management (ERAN3.0 - 06)

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 Management (ERAN3.0 - 06)

Uploaded by

Copyright:

Available Formats

Cell Outage Management

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

3 Sleeping Cell Detection Techniques ....................................................................................3-1

4 Cell Outage Detection Techniques .......................................................................................4-1

5 Engineering Guidelines ...........................................................................................................5-1

Issue 06 (2013-05-20) Huawei Proprietary and Confidential i

5.5.3 Data Preparation................................................................................................................... 5-2

Issue 06 (2013-05-20) Huawei Proprietary and Confidential ii

1.2 Intended Audience

1.3 Change History

Change Change Description Parameter Change

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-1

Change Change Description Parameter Change

Change Change Description Parameter Change

Change Change Description Parameter Change

Change Change Description Parameter Change

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-2

Change Change Description Parameter Change

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Change Type Change Description Parameter Change

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-3

Change Type Change Description Parameter Change

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 1-4

2.1 Overview of Sleeping Cell Detection

2.2 Overview of Cell Outage Management

2.2.1 Functions of the Cell Outage Management Feature

2.2.2 Possible Causes of Cell Outage

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 2-1

2.2.3 Cell Outage Detection Categories

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 2-2

3 Sleeping Cell Detection Techniques

3.2 Process of Sleeping Cell Detection

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 3-1

3.3 Relationships with Other Features

3.4 Impact on KPIs

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 3-2

4 Cell Outage Detection Techniques

4.1.1 Cell Outage Detection Based on an Alarm

4.1.2 Cell Outage Detection Based on a Sleeping Cell

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 4-1

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 4-2

Method KPI Outage Cell Criteria Example

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 4-3

4.1.3 Cell Outage Detection Based on an Abnormal KPI

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 4-4

KPI Outage Cell Criteria

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 4-5

4.2 Service Adjustment for Outage Cells

Isolating an outage cell involves the following operations:

Issue 06 (2013-05-20) Huawei Proprietary and Confidential 4-6

Operation Parameter ID Parameter Pre-Change Value Post-Change Value

4.3 Self-Healing of Outage Cells

4.4 Relationships with Other Features

4.4.1 Load Control

4.5 Impact on KPIs