Beruflich Dokumente
Kultur Dokumente
Revision Record
Date Revision Change Description Reviewer Author
Version
2008-12-30 1.0 First Version. Tao Maodi Xu Kaiping, Guo
Hao
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
7 Summary....................................................................................51
Figures
Tables
Abstract: The GSM KPI monitoring and optimization guide is intended to guide the field engineers and
cooperation engineers through KPI monitoring, judgment, and problem sorting. For further analysis,
this document also provides the optimization manual name for reference based on the problem type.
1 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.
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
Traffic None
Volume(ERL)
ZK3014/K3014
Paging Success Paging Success Rate = ((Number of Responses Upon First Paging +
Rate Number of Responses Upon Second Paging) × 100%)/Number of First
Pagings. The statistics of this measurement are collected on the MSC.
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.
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.
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.7 Baseline values of network-level KPIs for monitoring and optimization-CS service
Figure 1.8 Baseline values of network-level KPIs for monitoring and optimization-PS service
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%.
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.
No Assignment success
rate increased
TCH drop rate
The cluster-level Optimize the decreased
Yes
KPI should be PS performance
cluster-level KPI improved
optimized
Congestion
problem solved
No
No
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.
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.
The processing method is as follows:
For example, when you select the TopN bad cells based on the TCH drop rate, determine
whether the bad cells should be processed with priority according to the ratio of call drops to
call drops on the entire network. If the rank by the call drop rate is in TopN, but the number of
call drops is one, do not process the cell.
According to the principle of from the entire cell and major KPIs to the secondary KPIs, when
you perform the entire analysis of the KPIs, the analysis order of the CS domain based on the
impact of different KPI is as follows: availability, congestion rate (utilization), call drop rate
(retainability), handover success rate (mobility), and accessibility. As an independent item, the
paging success rate should be monitored independently or should not be monitored. The
analysis order of the PS domain is as follows: access performance, TBF drop rate,
retransmission rate of TBF.
For each analysis, the order is monitoring KPI first and the related KPI second. Finally,
correlate the analysis with the optimization operation guide.
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.
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.
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.
6 Implementation of KPI
Monitoring on NASTAR
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.
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.
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.
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.
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.
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.
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.
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.
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.
Step 3 Click Report Output to generate the traffic statistics report. In the Excel generated, choose
the TopN bad cells according to actual conditions.
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.
7 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.