Beruflich Dokumente
Kultur Dokumente
INTERNAL
Product Name
Confidentiality Level
GSM RNP
INTERNAL
Product Version
Total 51 Pages
1.0
Prepared by:
Date
2008-12-25
Reviewed by:
Date
2008-12-26
Approved by:
Date
2011-7-26
Huawei Confidential
Page 1 of 51
INTERNAL
Revision Record
Date
Revision
Version
Change Description
Reviewer
Author
2008-12-30
1.0
First Version.
Tao Maodi
Xu Kaiping, Guo
Hao
2011-7-26
Huawei Confidential
Page 2 of 51
INTERNAL
Contents
1 Overview......................................................................................9
2 KPI Monitoring and Improvement.................................................10
2.1 Recommended KPIs for Monitoring......................................................................................................................10
2.1 Recommended KPIs for Monitoring......................................................................................................................10
2.2 Measurements Correlating with KPI......................................................................................................................13
2.2 Measurements Correlating with KPI......................................................................................................................13
2.2.1 Measurements Related to TCH Drop Rate ......................................................................................................13
2.2.1 Measurements Related to TCH Drop Rate ......................................................................................................13
2.2.2 Measurements Related to Handover Success Rate...........................................................................................14
2.2.2 Measurements Related to Handover Success Rate...........................................................................................14
2.2.3 Measurements Related to Congestion..............................................................................................................15
2.2.3 Measurements Related to Congestion..............................................................................................................15
2.2.4 Measurements Related to TBF Call Drop Rate................................................................................................16
2.2.4 Measurements Related to TBF Call Drop Rate................................................................................................16
Huawei Confidential
Page 3 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 4 of 51
INTERNAL
7 Summary....................................................................................51
2011-7-26
Huawei Confidential
Page 5 of 51
INTERNAL
Figures
Process of KPI monitoring and optimization.....................................24
Daily report menus........................................................................35
Setting of daily report....................................................................36
Advanced setting of the daily report exporting................................37
Format of the output daily report....................................................38
Network monitoring report menus..................................................39
Basic setting of network monitoring report.....................................40
Advanced setting of the network monitoring report.........................41
Monitoring report output................................................................42
PCU monitoring report menu..........................................................43
Setting of the PCU monitoring report..............................................44
PCU monitoring report...................................................................45
Setting of enhanced traffic statistics...............................................46
Traffic statistics report output........................................................47
Setting of the network expansion report.........................................48
Setting of the query object.............................................................49
Wireless Resource Optimization Report...........................................50
2011-7-26
Huawei Confidential
Page 6 of 51
INTERNAL
Tables
Recommended KPIs for monitoring in the CS domain.......................10
Recommended KPIs for monitoring in the PS domain.......................12
Measurements related to the TCH call drop rate..............................14
Measurements related to handover success rate.............................14
Measurements related to the TCH congestion rate...........................15
Measurements related to the TBF drop rate.....................................16
Baseline values of network-level KPIs for monitoring and optimizationCS service.....................................................................................18
Baseline values of network-level KPIs for monitoring and optimizationPS service.....................................................................................19
KPIs that should be monitored........................................................20
Suggested data collection period of different KPIs...........................21
KPI parameters for selecting TopN cells...........................................26
Causes of low availability and optimization actions..........................27
2011-7-26
Huawei Confidential
Page 7 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 8 of 51
INTERNAL
Overview
With the expansion of the GSM network, the focus of routine maintenance is changing. It
becomes increasingly difficult to identify problems through drive tests (DTs), call quality tests
(CQTs), and user complaints. How to monitor the running of a network, evaluate the quality
of the network, and handle the problems on the network?
This guide describes the objectives of key performance indicators (KPIs), the method for
determining whether the quality of a network should be improved according to the KPIs, and
the method for locating a fault when a KPI is abnormal. This document also guides the
readers to determine the basic conditions and choose the required KPI Optimization Manual
according to the actual problems.
To ensure that the monitoring can be implemented properly, this document focuses on the
analysis of the monitoring and optimization of the exported KPIs. The KPIs in the DT and
CQT are not included.
Chapter 1 describes the purpose and content of the document. Chapter 2 describes the KPIs
for monitoring the network performance and the definitions. Chapter 3 describes the strategy
for monitoring and optimizing KPIs. Chapter 4 describes the KPI monitoring and
optimization flow. Chapter 5 describes the classification of KPIs for optimization and the
relevant guides. Chapter 6 describes the implementation of the KPI monitoring strategy
through the NASTAR. Chapter 7 provides the summary.
2011-7-26
Huawei Confidential
Page 9 of 51
INTERNAL
A KPI indicates the performance of the network or network element (NE) from a specific
aspect. Based on the actual value and evaluation method, you can determine whether the
performance is good and whether the performance should be optimized
KPI Formula
BSC
Level/Cell
Level
SDCCH
Availability
ZTR105A/RR300
TCH Availability
ZTR109A/RR307
SDCCH
Congestion Rate
ZTR103A/RR370
2011-7-26
Huawei Confidential
Page 10 of 51
INTERNAL
KPI
KPI Formula
BSC
Level/Cell
Level
TCH Congestion
Rate(Overflow)
ZTR106A/K3045
Immediate
Assignment
Success Rate
(CS)
ZTR110A/RA303
G
Success Rate of
TCH Assignment
ZTR102A/RCA3
13
Call Drop Rate on
SDCCH
ZTR104A/ZTR10
4C
TCH Call Drop
Rate(including
Handovers)
ZTR107A/ZTR30
4
Handover
Success Ratio per
BSC
ZK3180/RH303
Traffic
Volume(ERL)
ZK3014/K3014
Paging Success
Rate
2011-7-26
TCH Call Drop Rate (including Handovers) helps analyze the NEs of each level (BSC
and cell). Hence, it is recommended in this guide. If the standard is different from the
field standard, the field KPI definition needs to be observed.
The paging success rate is a concerned item. Monitor this item if it can be retrieved.
Huawei Confidential
Page 11 of 51
INTERNAL
2011-7-26
KPI
KPI Formula
PDCH Allocation
Success Rate
Uplink TBF
Congestion Rate
Downlink TBF
Congestion Rate
Downlink EGPRS
TBF Congestion Rate
Retransmission Rate
of RLC Uplink Data
Block
Retransmission Rate
of RLC Downlink
Data Block
Retransmission
EGPRS Rate of RLC
Uplink Data Block
Huawei Confidential
Page 12 of 51
INTERNAL
KPI
KPI Formula
Retransmission
EGPRS Rate of RLC
Downlink Data Block
The monitoring of the GPRS\EGPRS services is subject to the actual condition, that is,
whether certain services are activated.
The required KPIs must be monitored regardless of whether they are mentioned in the preceding
table or not.
If a KPI is defined in the field, use the field KPI formula. If no KPI is defined or put forward for
evaluation in the field, use the default definition of Huawei equipment. If no default definition is
available, see the suggested formula.
If the KPIs listed in the contract contain the suggested KPIs, or the performance indexes are the
same, use the KPIs listed in the contract.
The sub-performance is used to assist analysis after you find abnormal KPIs. It does not
serve as the standard for evaluation or monitoring.
Call Drops due to No MRs from MS for a Long Time (Traffic Channel)
The common call drops are classified into call drops on the radio interface in stable state and
call drops on the radio interface in handover state. During analysis, more detailed call drop
types are available, for example, error indication of call drops on the radio interface in stable
state, connection failure, and release indication. During analysis of a specific problem,
2011-7-26
Huawei Confidential
Page 13 of 51
INTERNAL
determine the call drop classification first, and then query the optimization guide to quickly
locate the problem.
Learning the general reasons of call drops before analyzing the TCH drop rate helps quickly
locate a problem.
Figure 1.3 Measurements related to the TCH call drop rate
KPI
KPI Formula
2011-7-26
KPI
KPI Formula
Success Rate of
Incoming Inter-Cell
Handover
Success Rate of
Outgoing Inter-Cell
Handover
Internal Handover
Success Ratio
Huawei Confidential
Page 14 of 51
INTERNAL
KPI
KPI Formula
Intra-BSC Radio
Handover Success
Rate
External Outgoing
Radio Handover
Success Ratio
External Outgoing
Radio Handover
Success Ratio
Success Rate of
Incoming BSC
Handover
External Incoming
Radio Handover
Success Ratio
Dual-Band Handover
Success Ratio per
cell(900/8501800/1900)
Dual-Band Handover
Success Ratio per
cell(1800/1900900/850)
(1800->900)
Success Rate of
Internal Intra-Cell
Handover (Overlay to
Underlay)
Success Rate of
Internal Intra-Cell
Handover (Underlay
to Overlay)
2011-7-26
KPI
KPI Formula
Huawei Confidential
Page 15 of 51
INTERNAL
TCH Traffic
Volume(ERL)
Null
Mean Number of
Available
Channels(TCH)
Null
2011-7-26
KPI
KPI Formula
Downlink EGPRS
TBF Drop Rate
Huawei Confidential
Page 16 of 51
INTERNAL
Huawei Confidential
Page 17 of 51
INTERNAL
2011-7-26
Type
KPI
Red Line
Availability
SDCCH Availability
90%
Huawei Confidential
Page 18 of 51
INTERNAL
Type
KPI
Red Line
TCH Availability
90%
5%
5%
96%
96%
1%
Retainability
1%
Mobility
93%
Paging
Performance
85%
Utilization
Accessibility
Figure 1.8 Baseline values of network-level KPIs for monitoring and optimization-PS service
Type
KPI
Red Line
Retainability
8%
Accessibility
90%
85%
92%
5%
5%
5%
5%
10%
10%
20%
20%
Um Interface
Transmission
2011-7-26
Huawei Confidential
Page 19 of 51
INTERNAL
The retransmission rate of GPRS/EDGE data block is heavily affected by the radio
environment and the transmission quality, the KPI for retransmission rate is fluctuating
and the evaluation requirement varies. The monitoring engineer should adjust the
standard of the red line according to the radio environment of the country. If the radio
environment and the transmission environment are good, refer to the ordinary network
standard of China: The retransmission rate of GPRS/EDGE RLC uplink data block < 5%
and the retransmission rate of RLC GPRS/EDGE downlink data block < 8%.
2011-7-26
Name of KPI
Bad
Baseli
ne
Normal
Baselin
e
Definition of KPI
RATE_TCH_CALL_
DROP_INCLUDE_H
O
1%
0.8%
xx
xx
RATE_SDCCH_Cong
estion
5%
4%
RATE_TCH_Congest
ion
5%
4%
RATE_immediately_
Assignment_Success(
CS)
96%
96.8%
RATE_Assignment_S
uccess
96%
96.8%
HO_SUCC_RATE
98%
98.4%
Huawei Confidential
Page 20 of 51
INTERNAL
2011-7-26
Objective
Heavy Traffic
Normal Traffic
Light Traffic
Networkwide level
Busy hours
Busy hours
24 hours
Huawei Confidential
Page 21 of 51
INTERNAL
Objective
Heavy Traffic
Normal Traffic
Light Traffic
Cluster-level
(beyond
BSC)
Busy hours
Busy hours
24 hours
Cluster-level
(less than 10
BSCs)
Busy hours
24 hours
24 hours
Cell level
Busy hours
24 hours
24 hours of 7 days
Analysis and
statistics of
radio
resources
To ensure the accuracy of KPI, 24-hour statistics are recommended in all cases. Comparison
of the seven records of the statistical data of seven days improves the accuracy of the KPI
analysis.
When you export the performance data by using the M2000, you can choose to export the
records with the granularity of an hour (24 hours of seven days) by cells. You can calculate
the performance of the entire network or any period (greater than an hour) by using the
EXCEL.
2011-7-26
Huawei Confidential
Page 22 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 23 of 51
INTERNAL
Network-level
KPI should be
optimized
Yes
No
The cluster-level
KPI should be
optimized
Yes
Optimize the
cluster-level KPI
Yes
Process the
TopN cells
No
2011-7-26
Huawei Confidential
Page 24 of 51
INTERNAL
If the KPI is worse than the red line, unless otherwise specified (problems in certain cells are
caused by known reasons, or the carrier specifies that the problem can be ignored, or the
problem cannot be processed because resources are limited), start the network-level KPI
optimization.
If the KPI is worse than the yellow line, you should determine whether the KPI is close to or
decreasing to the red line, whether the problem is caused by a type of problem or caused by
problems of certain NEs.
If the KPI is tending to the red line or it may be degraded, refer to the method of
processing the KPI worse than the baseline value.
If a certain problem affects the entire network, optimize KPIs that cause the problem.
If certain NEs are affected, analyze the distribution of the NEs, optimize the cluster-level
KPIs or the TopN cells.
If a special problem is detected, monitor only this KPI.
2011-7-26
1.
For the number of TopN cells, 5% of the entire network cells are recommended. The
value should not exceed 50, and no specific number is required. Do not take the cells
better than the yellow line as the TopN cells. If all cells in the network are better than the
yellow line, do not perform TopN cell handling for the KPI.
2.
If the cell KPI is worse than the red line (2X), process the KPI using TopN bad cells. For
the cells reaching the red line frequently, more attention should be paid, and the cells
must be processed in time. If the number exceeds 5% or 50, process the KPI as networkwide/cluster problems. If the number of red-line cells exceeds 5% and the number is
greater than 50, optimize the KPI as cluster/network-wide problems.
Huawei Confidential
Page 25 of 51
INTERNAL
3.
For the cells worse than the yellow line, determine the processing order according to the
weight item. Put 10 or less than 2% of the cells into the TopN bad cells. For the cells
ranking behind 20% of the weight items or ranking behind 50, if no resources are
available, do not process these cells.
In the process of cell analysis, if the number of yellow-line cells is less than 10, put
them into the TopN cells.
KPI
Weight
Utilization
TCH congestions
SDCCH Congestion
Rate(Overflow)
SDCCH congestions
Mobility
Handover failures
Retainability
TCH drops
SDCCH drops
TBF drops
Accessibility
PS Domain
2011-7-26
Huawei Confidential
Page 26 of 51
INTERNAL
2011-7-26
Availabili
ty
Problem
Cause
Lower than
the yellow
line
Huawei Confidential
Page 27 of 51
INTERNAL
Availabili
ty
Problem
Lower than
the red line
Cause
2011-7-26
Huawei Confidential
Page 28 of 51
INTERNAL
the SDCCH congestion rate does not reach the standard in the entire network, and the
measurement will not be degraded to the yellow line.
When the SDCCH congestion rate is lower than the yellow line, determine whether the
problem is common or the problem is caused by certain cells.
When the problem is common, it is caused by the traffic burst. In certain cases, the problem is
caused by the network-wide interference, the fault beyond the BSC, or the software bug. If the
problem is caused by network-wide interference or fault beyond the BSC, many severe
problems may occur in the entire network. The symptoms are indicated before the periodical
KPI monitoring analysis (such as complaints and critical alarms). To determine whether the
traffic burst exists, you should generate the trend chart of the traffic volume. Use the trend
chart of 24 hours of 7 days and every hour of each day to find the period of traffic burst. Then
determine the cause of the traffic burst.
For the congestion caused by traffic burst, you can enable the "SDCCH dynamic allocation"
and "Immediate allocate to the TCH" functions in the BSS side. If the problem persists, the
carrier should balance the traffic burst. If the traffic burst cannot be removed, allocate the
service traffic to a long period. For example, to transmit all greeting short messages in a
certain region (such as a city) in five minutes, you can increase the transmission time to one
hour or longer. For the requirements of group-sending short messages in a province, the SMS
side cannot deliver the messages consecutively by the flag bit of the area code. For the
domestic numbers, sort them by the last 4 digits or 3 digits. Extend the service of each region
(LAC) to the entire period instead of a shorter period.
If the problem is caused by certain cells, make a comparison according to the cell-level KPI
bottom line to choose the TopN cells with high SDCCH congestion rate. In the case of the
number of the TopN cells, see section 4.4 "Selection of TopN Bad Cells." First, check whether
the cells with high SDCCH congestion rate are caused by the load. If the congestion is in a
short period, enable the SDCCH dynamic allocation function. If the congestion due to load
occurs in many periods in a day, increase the SDCCHs. Enabling the immediate assignment
TCH function can release the SDCCH congestion to some extent. But the enabling of the
function may cause the waste of channels, and the evaluation KPIs defined by carriers may be
affected. This function is not recommended unless required.
After you obtain the causes of the high SDCCH congestion rate, process the problem by
referring to the GSM BSS Network KPI (SDCCH Congestion Rate) Optimization Manual.
If the SDCCH congestion rate of the entire network reaches the standard, you can process
only the cells worse than the red line in the TopN cells.
2011-7-26
Huawei Confidential
Page 29 of 51
INTERNAL
The TCH congestion rate can be classified into cell congestion rate, but considering the implementation
period of the capacity expansion, when the TCH congestion rate of the entire network reaches the yellow
line, you can suggest the network capacity expansion in the stage of overall analysis. If the entire
network cannot be expanded because the frequency resources are limited, put forward the scheme of
dual-band network and concentric cells.
If the TCH congestion rate of the entire network reaches the yellow line, except the load, the
problem is caused by the external interference of the entire network, bugs or faults of the NEs
beyond BSC. When the special cases occur, many obvious symptoms may occur in the entire
network. In this case, refer to the GSM Interference Analysis Guide
(http://support.huawei.com/Knowledge Center/Radio/Radio Performance and Network
Planning and Optimization). The GBSS engineers can also process the fault through the
workflow for major faults.
2011-7-26
Huawei Confidential
Page 30 of 51
INTERNAL
TopN bad cells according to the handover success rate of a single type (such as inter-BSC
outgoing handover, if the handover problem is on the BSC edge, the dual-band handover can
be located in the corresponding area). At the same time, you can choose the TopN cells
according to the KPIs (such as the handover success rate), and then determine the direction to
analyze the problem according to the single handover type of the cell.
If the problem of handover success rate is common, first analyze the impact of the single
handover type of the entire network. For example, the inter-BSC outgoing handover
difference causes that the network-wide KPI is lower than the bottom line, and the handover
success rate of the dual-band network is bad. If the problem is not of a certain type of
handover, you should consider whether the planning of the adjacent area is reasonable and
whether the setting of the handover timer is reasonable.
For the analysis on the handover success rate of a single cell and how to process the problem,
refer to the GSM BSS Network KPI (Handover Success Rate) Optimization Manual.
2011-7-26
Huawei Confidential
Page 31 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 32 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 33 of 51
INTERNAL
Implementation of KPI
Monitoring on NASTAR
2011-7-26
Huawei Confidential
Page 34 of 51
INTERNAL
Step 2 In the displayed setting page, you can set the path for saving the reports, the BSC to be
monitored, and the date of the report.
2011-7-26
Huawei Confidential
Page 35 of 51
INTERNAL
Step 3 On the Advanced tab page, set the TopN cells, busy cell, free cell, and the worst cell. Click
Cell Group Manage to edit the VIC cell group.
2011-7-26
Huawei Confidential
Page 36 of 51
INTERNAL
Step 4 Click OK to generate the daily report. The daily report includes the cover, KPI, TopN of BSC,
traffic trend chart in 24 hours, VIC, hot cells, busy and free cells, worst cells, and other KPI
trend pages. The font color of the abnormal counter in the report is red. For the value of the
abnormal counter, refer to the GENEX NASTAR GSM User Manual.
2011-7-26
Huawei Confidential
Page 37 of 51
INTERNAL
The operation of the weekly report and the monthly report is similar to the operation of the
daily report.
The weekly report includes the cover, KPI, TopN of the entire network or BSC, VIC, traffic
trend chart in a week, radio complete rate in a week, drop rate trend chart in a week, TCH
congestion rate trend chart in a week, SDCCH congestion rate trend chart in a week, TCH
availability trend chart in a week, SDCCH availability trend chart in a week, and the CPU
load trend chart in a week.
The monthly report includes the cover, KPI, TopN of the entire network or BSC, worst cells,
traffic trend chart in a month, radio complete rate in a month, drop rate trend chart in a month,
TCH congestion rate trend chart in a month, SDCCH congestion rate trend chart in a month,
TCH availability trend chart in a month, SDCCH availability trend chart in a month, and the
CPU load trend chart in a month.
2011-7-26
Huawei Confidential
Page 38 of 51
INTERNAL
Step 2 On the Basic Setting tab page, set the path for saving the reports, the query object, report
type, date range, and statistic time. When you create the engineer report, you should select
Engineer Report for the Report Type.
2011-7-26
Huawei Confidential
Page 39 of 51
INTERNAL
Step 3 On the Advanced Setting tab page, set the value of N in the TopN bad cells, filtering setting
for bad cells, VIC cell group, and the KPI baseline. The default value of N in TopN is 10. The
filtering conditions are not set. In practice, for the value of N, 5% (not more than 50) of the
cell quantity is recommended. At the same time, set the red line and yellow line to filter the
TopN cells.
In the KPI, set the lower threshold of the good network and the lower threshold of the normal
network to the yellow line and the red line. Mark the KPIs exceeding the red line and the
yellow line with colors in the exported report.
The current NASTAR cannot distinguish the cell baseline from the entire network baseline.
You can set the entire network baseline and the cell baseline separately, and export the report
one by one. You can also set the entire network baseline, and select the cell baseline manually.
2011-7-26
Huawei Confidential
Page 40 of 51
INTERNAL
Step 4 Click OK to generate the network monitoring report. In the network monitoring report, the
monitoring KPIs include accessibility, mobility, retainability, and the resource utilization.
2011-7-26
Huawei Confidential
Page 41 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 42 of 51
INTERNAL
Step 2 In the PCU Network Monitoring Report dialog box, set the path for saving the reports, the
query object, report type, date range, and the statistic time.
2011-7-26
Huawei Confidential
Page 43 of 51
INTERNAL
Step 3 After setting the parameters, click OK to generate the report. The PCU monitoring report
includes KPIs of the accessibility, retainability, Um interface transmission, Gb interface
transmission, and the resource utilization.
2011-7-26
Huawei Confidential
Page 44 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 45 of 51
INTERNAL
Step 3 Click Report Output to generate the traffic statistics report. In the Excel generated, choose
the TopN bad cells according to actual conditions.
2011-7-26
Huawei Confidential
Page 46 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 47 of 51
INTERNAL
Step 2 In the displayed page, set the start date, end date, BH traffic statistics mode, capa_cell
expansion figure (%), TCH margin, TCHs per TRX, Capa_cell definition, and Erl_B GOS
(%). The Erl_B GOS (%) is subject to the requirement of the carrier and the value 2 is
recommended. For other parameters, use the default values.
Step 3 In the Query Object, select the object type.
2011-7-26
Huawei Confidential
Page 48 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 49 of 51
INTERNAL
2011-7-26
Huawei Confidential
Page 50 of 51
INTERNAL
Summary
Thanks go to colleagues of each department for their support in the development of GSM KPI
Monitoring and Optimization Guide. It is the first KPI monitoring guide of the radio product.
The document intends to focus on the practical operation, but the theory still weights a lot
owing to limited foundation. Especially for the output of the monitoring report, the report
specification is not available because the plan is not implemented. The monitoring method is
not implemented onsite for long term. Hence, no complete KPI analysis case is provided in
this document.
After the guide is put into practice in the field, we plan to choose the KPI monitoring and
optimization cases based on M2000 and NASTAR (new version of 2009). Each case should
be chosen from the monitored KPI. The case describes the making of monitoring standard, the
detection of KPI problems, and the processing method. The segments of the monitoring report
about the KPI monitoring problems are added, which guides readers to master the method of
monitoring KPIs and processing the problems. As a result, comprehensive monitoring and
optimization report can be generated timely.
The improvement of the guide relies on the practice onsite. If you have any suggestions or
operation cases, please send your feedback to us. Your experience is of great importance and
is helpful for other users.
2011-7-26
Huawei Confidential
Page 51 of 51