GSM RF Optimization Handbook 603G Section: 220

Lucent Technologies Date: 04/01/01

RFEC Global Platform Group Issue: 1.0
http://rfec.wh.lucent.com

NETWORK WIRELESS SYSTEMS

METHODS AND PROCEDURES FOR

GSM RF OPTIMIZATION

PERFORMANCE MEASUREMENTS

TABLE OF CONTENTS

1 INTRODUCTION ..................................................................................................................................................2
2 BSS PERFORMANCE MEASUREMENT DATA ................................................................................................2
2.1 Measurement Counter .....................................................................................................................................2
2.2 Global Definitions...........................................................................................................................................2
2.3 PM Systems and Measurement Reports ..........................................................................................................2
2.4 Network Data Analyzer...................................................................................................................................2
2.5 Backup of Performance Measurement Data....................................................................................................2
3 BSS PERFORMANCE ANALYSIS.......................................................................................................................3
3.1 General Approach ...........................................................................................................................................3
3.2 Area Performance............................................................................................................................................3
3.3 Region Performance........................................................................................................................................3
3.4 Cell Performance.............................................................................................................................................4
REFERENCES ..............................................................................................................................................................6

Lucent Technologies - PROPRIETARY

Use pursuant to Company Instructions
Handbook 603 Section 220
Performance Measurements
1 INTRODUCTION
Various Key Performance Indicators (KPI) describe
the network performance, such as Drop Call Rate
(DCR), Traffic and Congestion. KPIs are calculated
using performance measurement data provided by a
Performance Measurement System (PMS) or
Performance Measurement raw counter (PM raw
counter). The results from an evaluation of the KPIs
at different network element levels will help to
uncover major problems in the network, for example,
overall network design and configuration problems,
to identify problem areas, and to reveal problems in
individual cells.
This section provides a strategy guideline to perform
an efficient network performance analysis. The
analysis results will be statistical overviews and an
interpretation of the GSM network performance at
different network element levels. Problem areas will
be highlighted and possible root causes will be
elaborated.
Note: While the details below apply to all size
networks, the RF Optimization team needs to exercise
judgment on the results in case of low network usage
where statistics may be misleading. Furthermore the
analysis should also consider the outcome of drive
and cluster tests performed during the optimization
work.
2 BSS PERFORMANCE MEASUREMENT
DATA
2.1 Measurement Counter
A measurement counter represents a value that is
pegged or calculated by a network element when a
pre-defined condition occurs within the system. For
example, a traffic channel seizure causes the
Successful TCH seizure measurement counter to
increment. A counter is the smallest performance
management data entity.
The measurement counters could be activated on BSS
level. Each BSS calculates the counters and uploads
the data to the OMC. The data are collected in
intervals of 15, 30 or 60 minutes depending on the
measurement recording period chosen by the operator
(default setting: 15 minutes).
An overview about the different counters could be
found in Reference 1.
Example:
Lucent Technologies - PROPRIETARY
Use pursuant to Company Instructions
GSM
2 Date: 01/04/01
noSuccessfTCHSeiz (m23c0) counts the number of
successfully performed TCH Seizures.
2.2 Global Definitions
Global definitions represent frequently used counter
combinations within the Key Performance Indicator
(KPI) definitions. Generally the global definitions
represent performance indicators and have meaning
in themselves but are not considered KPIs.
Example:
TCH Drops = noRadioFreqLosses+noMiscLoss.TCH
= m3c0 + m96c0
2.3 PM Systems and Measurement Reports
The OMC-2000 may include the optional Enhanced
Basic Performance Management Feature System (E-
PMS). The E-PMS provides a set of fundamental
reports based on BSS data that can be used to monitor
and gauge BSS performance. This tool can also store
and export data from the OMC-2000. The E-PMS is
introduced in detail in Reference 2.
As an example the TCH report generated by the E-
PMS includes measures like TCH attempts and TCH
Seizures, TCH Drop Call Rate [%] and TCH
Blocking Rate [%] etc.
Other PM systems like Metrica can also use the
interface of the OMC-2000. Each operator can decide
to use third vendor products or the E-PMS.
2.4 Network Data Analyzer
Performance data (and in addition other data like
parameter, configuration data etc.) from several
networks can be downloaded from the Network Data
Analyzer (NDA) in the Lucent intranet at http://www-
ncms.cb.lucent.com/nda. Also performance data from
other networks could be analyzed to have a
comparison with other networks. Downloading of
data requires an account with password.
2.5 Backup of Performance Measurement
Data
Performance Measurement data and post-processed
reports should be continuously collected and stored
on a system drive. An additional database should
track single events that could cause fluctuation in the
statistic like outages, single public events with high
traffic, network re-configuration etc. By monitoring
the network over several months it is possible to
predict the network growth, but also detect a possible
continuous degradation of the network performance.
PM systems like Metrica have special tools to analyze
Handbook 603 Section 220
Performance Measurements
or visualize trends. The current version of the E-PMS
only offers some basic tasks and reports to analyze
trends.
3 BSS PERFORMANCE ANALYSIS
3.1 General Approach
Key Performance Indicators (KPI) are calculated
using PM raw data or PM reports. The KPIs should
be calculated for the whole area of the network to be
analyzed (Area Performance), different regions of the
network (Region Performance) and on cell level
(Cell Performance). Applying a top-down approach
from network level to cell level for the data analysis
helps to narrow down problem areas and/or problems
in individual cells. For details see the following
subsections.
To calculate the KPIs on the different levels it is
necessary to collect the PM data for five consecutive
business days. This will reduce the impact of
temporarily statistically fluctuation and will make the
PM statistic more reliable.
The PM data of the cells are taken from the Cell Busy
Hour of each day (the Cell Busy Hour of each cell
may vary). The average values over the five days
form the basis for calculating the KPI.
For the Area and Region Performance the KPIs are
calculated by aggregating the cell performance data.
Example: The TCH Congestion Rate is calculated by
applying the following formula: 100 * Sum of TCH
blocks of all cells / Sum of TCH attempts of all cells.
3.2 Area Performance
The investigation of the Area Performance should
include the whole area to be investigated. The
measures calculated on area level gives an indication
of "how good the chosen area performs". These
measures will give an overall overview about the
network performance.
3.2.1 Area Performance - TCH
The statistical overview of the TCH Area
Performance should include the following items:
• Number of cells
• Total TCH Traffic [Erlang]
• Average TCH Traffic/Cell [Erlang]
• Average TCH Traffic Congestion [%]
• Average TCH Drop Call Rate [%]
Lucent Technologies - PROPRIETARY
Use pursuant to Company Instructions
GSM
3 Date: 01/04/01
• Average TCH Availability [%]
3.2.2 Area Performance - SDCCH
The statistical overview of the SDCCH Area
Performance should include the following items:
• Total SDCCH Traffic [Erlang]
• Average SDCCH Traffic/Cell [Erlang]
• Average SDCCH Mean Holding Time/Cell [s]
• Average SDCCH Traffic Congestion [%]
• Average SDCCH Drop Call Rate [%]
• Average SDCCH Availability [%]
3.2.3 Area Performance - Handover
The statistical overview of the HO Area Performance
should include the following items:
• Handover Success Rate [%]
• Handover Success Rate including successful HO
reversions [%]
• Handover Distribution [%]
¾ UL Quality [%]
¾ DL Quality [%]
¾ UL Level [%]
¾ DL Level [%]
¾ Powerbudget [%]
¾ Distance [%]
3.3 Region Performance
It is possible to group different sites to a region and
calculate the KPIs for this region. A region could be
a group of cells belonging to the same MSC or BSC
or the cells could be grouped according to the
geographical areas like Downtown, Airport, etc. in
order to focus on important areas.
The results of the analysis on region level will help to
identify problem areas, which will be investigated in
more detail on cell level.
3.3.1 Region Performance - TCH
The statistical overview should be done in the same
way as described in subsection 3.2.1.
3.3.2 Region Performance - SDCCH
The statistical overview should be done in the same
way as described in subsection 3.2.2.
Handbook 603 Section 220 GSM
Performance Measurements 4 Date: 01/04/01
3.3.3 Region Performance - SDCCH/TCH Ratio • Number of drops
(STR)
• TCH Drop Call Rate [%]
The statistical overview should only include the
following item: • Mean Time Between Drops (MTBD) [min]

• SDCCH-TCH Ratio (STR) • Traffic [Erlang]

Remark: STR is the relation between the signaling
traffic and carried traffic. This measure will show if
there is excess signaling in the network and it can be
used as an early warning signal for SDCCH
Congestion. For more details see Reference 3. The
STR in a network should be between 0.12 and 0.18.
3.3.4 Region Performance - Handover
The statistical overview should be done in the same
way as described in subsection 3.2.3.
The data should be imported in a table and sorted by
the worst performing cells with low MTBD.
For analyzing dropped calls MTBD should be used
instead of the TCH Drop Call Rate. The reason for
using this formula is that MTBD better reflects the
‘subscriber point of view’ because it shows the time
between two dropped calls. MTBD uses a
combination of the carried TCH traffic and the
number of dropped calls in a cell to categorize the
cells in a network. Its definition is (TCH Traffic*60
Minutes)/Drops.

3.4 Cell Performance 3.4.3 Cell Performance – SDCCH Congestion

In order to identify bad performing cells it is The statistical overview should include the following
necessary to analyze the performance of each cell items:
separately. For this purposes the worst performing • Cell name
cells concerning the different KPIs are listed (e.g. 10
worst cells). Possible Reason for the bad performance • Region (if applicable)
of the cells is discussed in Reference 3. • Number of radios (RTs)

3.4.1 Cell Performance – TCH Congestion • Number of SDCCH Channels

The statistical overview should include the following • SDCCH Congestion [%]
items:
• SDCCH Traffic [Erlang]
• Cell name
• SDCCH-TCH Traffic Ratio (STR)
• Region (if applicable)
• SDCCH Availability [%]
• Number of radios (RTs) The data should be imported in a table and sorted by
• Number of TCH Channels the worst performing cells with high SDCCH
congestion.
• TCH Traffic [Erlang]
• TCH Traffic/RT [Erlang] 3.4.4 Cell Performance - SDCCH Drop Rate

• TCH Traffic Congestion [%] The statistical overview should include the following
items:
• TCH Availability [%]
• Cell name
The data should be imported in a table and sorted by
the worst performing cells with high TCH congestion. • Region
• Number of drops
3.4.2 Cell Performance – TCH Drop Call Rate
• SDCCH Drop Rate [%]
The statistical overview should include the following
items: • SDCCH Traffic [Erlang]
• Cell name • SDCCH Mean Holding Time (SDCCH MHT) [s]
• Region

Lucent Technologies - PROPRIETARY

Use pursuant to Company Instructions
Handbook 603 Section 220 GSM
Performance Measurements 5 Date: 01/04/01
The data should be imported in a table and sorted by
the worst performing cells with high SDCCH Drop
Rate.

3.4.5 Cell Performance – Handover

The statistical overview should include the following
items:
• Cell name
• Region
• Handover Success Rate [%]
• Handover Success Rate including successful HO
reversions [%]
• Handover Distribution [%]
¾ UL Quality [%]
¾ DL Quality [%]
¾ UL Level [%]
¾ DL Level [%]
¾ Powerbudget [%]
¾ Distance [%]
• Intracell HO [%]
The data should be imported in a table and sorted by the worst performing
cells with low Handover Success Rate.

Lucent Technologies - PROPRIETARY

Use pursuant to Company Instructions
Handbook 603 Section 220 GSM
Performance Measurements 6 Date: 01/04/01

REFERENCES

Reference 1: "OMC 2000 - Performance Measurement Definitions Guide",

http://en0033svr06.uk.lucent.com/product/docloc.htm#OMC-2000

Reference 2: "OMC 2000 - System Operator's Guide",

http://ong.de.lucent.com/~dok_atlk/ctip_nbg/ctip_gsm/docweb/bss/nbg/webdocs-enus/libfiles/index.html

Reference 3: "GSM Optimization Handbook section 230"

Lucent Technologies - PROPRIETARY

Use pursuant to Company Instructions