GSM KPI Optimization Process and Guide
GSM KPI Optimization Process and Guide
Page 1 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
Contents
1 KPI Optimization process Overview ........................................................................................................... 3
2 Main KPIs Optimization Processes ............................................................................................................. 4
3 GSM Timer Optimization.......................................................................................................................... 17
Thanks ................................................................................................................................................. 22
Page 2 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
This document mainly describes the Network Performance Monitoring & Optimization Process
We will first check all the main KPIs and how we will do the troubleshooting for them one by one and
will check also the environmental effect for each, and the principle for how to check the reasons. And
after that we will check the main timers and its relation to the network for both sides MS & NSS side.
Page 3 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
Definition: When From the MS SDCCH Request is sent to Base Station and if MS
Successfully gets the SDCCH in response SDCCH Assignment has done successfully.
PROCESS for Optimization:
1. Identify the Bad performing Cells for SDCCH Assignment Success Rate
2. Take the detailed report showing (Ex. Total SDCCH Assignment Request, Total SDCCH
Assignment Successful)
3. Follow the below mentioned Process after Analyzing detailed report...
4. From Report Check whether you have Idle SDCCH available in cell or not for SDCCH
Assignment; because the Main factor for lowering SDCCH Assignment success rate is
SDCCH congestion.
5. SDCCH Congestion:
a. Check The SDCCH Requests (Immediate Assignment Measurement Per Cell
Report form M200)
b. Ex. Call purpose, SMS, Location Update
c. If you find High SDCCH Request and low TCH utilization Check SDCCH
Dynamic Allocation Allow feature is enabled or not? if not enable this feature.
d. If you have very High SDCCH Request for Location Updating; optimize the LAC boundary.
e. Only For some exceptional cases you can increase the Static SDCCH Time Slots.
6. Check Hardware/Transmission alarms; Resolve if find any.
7. Audit for any parameters related discrepancies and define as per standard parameters set.
8. RF and Environmental Factors:
a. Low Coverage Areas (Try to reduce low coverage patches with physical
optimization; New sites)
b. Interference/ Bad quality/ UL-DL Imbalance;
c. Check the states for TRx on which SDCCH is configured can be issue of TRx
also; Change TRx if you found random behavior of TRx.
9. After all rectification observe the subsequent days report if you still find the problem
repeat the same process with due care to Pin Point the actual cause.
Fish bone diagram for the root cause analysis high SDCCH congestion rate
Page 4 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
Fish bone diagram for the root cause analysis for high SDCCH drop rate
Page 5 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
Fish Bone diagram for the root cause analysis of poor Random Access Success
Page 6 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
pointing the actual cause. (Ex. Assignment Per Cell Report from M2000)
12. Correct the affected area (Ex. If call is getting originated from High TA and getting failed
due improper strength ; Optimize the Site Coverage with Physical Optimization) and
check the subsequent days Report; If you still find the issue follow the same flow right
from the starting with due care to PIN Point the Actual cause..
13. TBF Success Rate
14. Average GPRS RLC throughput & Average EDGE RLC Throughput
15. Downlink Multi-slot Assignment Success Rate
16. SDCCH Assignment Success Rate
17. SDCCH DROP Rate
18. ACH (Random Access Channel) Success Rate
19. Assignment Success Rate
External
Multipath
Noise
Speech Quality Parameters
Rx-QUAL: Measured on the mid-amble.
Indicates poor speech quality due to radio interface impairments
FER : Measured on the basis of BFI ( Ping -Pong effect on speech )
Preferred under Frequency Hopping situation
Audio holes: Blank period of speech, due to malfunctioning of Trans-coder boards or
PCM circuits.
Mean Opinion Score (MOS) : ITU standard for estimating speech quality
PROCESS for Optimization:
1) Physical optimization
2) New cell dependency
3) Overshooting
4) Neighbor list tuning
5) BCCH tuning (Freq plan)
From M2000 extract Rx Quality measurement distribution counters to know the TRX-Cell Wise
RX quality.
Voice Quality
KPIs.xlsx
Page 9 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
Classification by Reason:
Emergency HO
Timing advance (TA) Emergency HO
Bad quality (BQ) Emergency HO
Rx Level Drop Emergency HO
Interference emergency HO
load HO
Normal HO
Edge HO
Layer HO
Power budget (PBGT) HO
Fast moving MS HO (Speed-sensitive HO )
PROCESS for Optimization:
Identify the Bad performing Cells for HOSR
Take the detailed report showing cause & target cell
Check congestion; hardware Alarm; Quality; Rx level
Late Handover Handover margin (like Rx level-Rx Qual etc )need to define properly.
Ping-Pong Handover A proper Hysteresis is used to prevent the Ping Pong effect. This can
be caused by fading.
Unnecessary Handover more number of handovers, higher risk of facing quality
problem and even in call drop.
Missing neighbor Best server is not in there in neighbor list
BCCH Missing
Same BCCH & BSIC combination.
One way neighbor handover.
Neighbor cell in other BSC- need to define correct CGI,BCCHNO,BSIC
Congestion on other cell.
Fish bone diagram for the root cause analysis for high handover failure rate
Page 10 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
If the counter reaches zero when the mobile is on a SDCCH then it is an SDCCH Drop.
If it happens on a TCH, it is a TCH drop.
Sometimes an attempted handover, which may in itself have been an attempt to prevent a
drop, can result in a dropped call.
Page 11 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
From U2000 extract Call drop Measurements counters to know the cause.
Figure 1: Fish bone diagram for the root cause analysis for high TCH Drop Rate
Figure 2: Fish bone diagram for the root cause analysis for high TCH Drop Rate
Page 12 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
1 Fish bone diagram for the root cause analysis of poor Paging Success Rate:
Page 13 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
Page 14 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
After all rectification observe the subsequent days report if you still find the problem repeat the
same process with due care to Pin Point the actual cause.
requests are high. If requests are high, then we need to define more PDCHs in the
cell. But before defining more PDCHs, check whether the Voice Utilization is not
high and there is no TCH Congestion in the cell.
d. Check the multiplexing thresholds and upgrade/downgrade reports.
5. Check whether it is due to poor radio conditions/interference; check C/I. Perform a drive test to
analyze the cell in more detail.
Page 16 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
And Below we will introduce a summary for the timers which it will be composed of 2
parts:
1. A summarization for the timer message.
2. Most of the timer on both the sides the MS & the NSS respectively.
Page 17 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
T3124: This timer is used in the seizure procedure during a hand-over, when the two cells are
not synchronized. Its purpose is to detect the lack of answer from the network to the special
signal. Its value is set to 675 ms if the channel type of the channel allocated in the HANDOVER
COMMAND is an SDCCH (+ SACCH); otherwise its value is set to 320 ms.
T3126:This timer is started either after sending the maximum allowed number of CHANNEL
REQUEST messages during an immediate assignment procedure. Or on receipt of an IMMEDIATE
ASSIGNMENT REJECT message, whichever occurs first. It is stopped at receipt of an IMMEDIATE
ASSIGNMENT message, or an IMMEDIATE ASSIGNMENT EXTENDED message. At its expiry, the
immediate assignment procedure is aborted. The minimum value of this timer is equal to the
time taken by T+2S slots of the mobile station's RACH. S and T. The maximum value of this
timer is 5 seconds.
Page 18 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
T3128: This timer is started when the mobile station starts the uplink investigation procedure and
the uplink is busy. It is stopped at receipt of the first UPLINK FREE message. At its expiry, the
uplink investigation procedure is aborted. The value of this timer is set to 1 second.
T3130: This timer is started after sending the first UPLINK ACCESS message during a VGCS
uplink access procedure. It is stopped at receipt of a VGCS ACCESS GRANT message. At its
expiry, the uplink access procedure is aborted. The value of this timer is set to 5 seconds.
T3110: This timer is used to delay the channel deactivation after the receipt of a (full) CHANNEL
RELEASE. Its purpose is to let some time for disconnection of the main signaling link. Its value is
set to such that the DISC frame is sent twice in case of no answer from the network. (It should
be chosen to obtain a good probability of normal termination (i.e. no time out of T3109) of the
channel release procedure.)
T3134: This timer is used in the seizure procedure during an RR network commanded cell change
order procedure. Its purpose is to detect the lack of answer from the network or the lack of
availability of the target cell. Its value is set to 5 seconds.
T3142: The timer is used during packet access on CCCH, after the receipt of an IMMEDIATE
ASSIGNMENT REJECT message. Its value is given by the network in the IMMEDIATE
ASSIGNMENT REJECT message. T3146:This timer is started either after sending the maximum
allowed number of CHANNEL REQUEST messages during a packet access procedure. Or on
receipt of an IMMEDIATE ASSIGNMENT REJECT message during a packet access procedure,
whichever occurs first. It is stopped at receipt of an IMMEDIATE ASSIGNMENT message, or an
IMMEDIATE ASSIGNMENT EXTENDED message. At its expiry, the packet access procedure is
aborted. The minimum value of this timer is equal to the time taken by T+2S slots of the mobile
station's RACH. S and T are defined in section 3.3.1.2. The maximum value of this timer is 5 Sec.
T3164: This timer is used during packet access using CCCH. It is started at the receipt of an
IMMEDIATE ASSIGNMENT message. It is stopped at the transmission of a RLC/MAC block on the
assigned temporary block flow, see GSM 04.60. At expire, the mobile station returns to the
packet idle mode. The value of the timer is 5 seconds.
T3190: The timer is used during packet downlink assignment on CCCH. It is started at the receipt
of an IMMEDIATE ASSIGNMENT message or of an PDCH ASSIGNMENT COMMAND message
when in dedicated mode. It is stopped at the receipt of a RLC/MAC block on the assigned
temporary block flow, see GSM 04.60. At expiry, the mobile station returns to the packet idle
mode. The value of the timer is 5 seconds.
T3212 (Location update timer): This timer is related with the termination of MM signaling. It
starts with the termination of MM signaling. And it timer stops when the message for the
initiation of MM signaling is sent to the MS by the BSS entity. Expiry Event: In case the timer
expires, a periodic request is sent for the LU update. The default value for this timer is 60
seconds.
Page 19 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
T3101: This timer is started when a channel is allocated with an IMMEDIATE ASSIGNMENT
message. It is stopped when the MS has correctly seized the channels. Its value is network
dependent. NOTE: It could be higher than the maximum time for a L2 establishment attempt.
T3103: This timer is started by the sending of a HANDOVER message and is normally stopped
when the MS has correctly seized the new channel. Its purpose is to keep the old channels
sufficiently long for the MS to be able to return to the old channels, and to release the channels if
the MS is lost. Its value is network dependent.
NOTE: It could be higher than the maximum transmission time of the HANDOVER COMMAND,
plus the value of T3124, plus the maximum duration of an attempt to establish a data link in
multi-frame mode.)
T3105: This timer is used for the repetition of the PHYSICAL INFORMATION message during the
hand-over procedure. Its value is network dependent. NOTE: This timer may be set to such a low
value that the message is in fact continuously transmitted.
T3107: This timer is started by the sending of an ASSIGNMENT COMMAND message and is
normally stopped when the MS has correctly seized the new channels. Its purpose is to keep the
old channel sufficiently long for the MS to be able to return to the old channels, and to release
the channels if the MS is lost. Its value is network dependent.
NOTE: It could be higher than the maximum transmission time of the ASSIGNMENT COMMAND
message plus twice the maximum duration of an attempt to establish a data link multi-frame
mode.
T3109: This timer is started when a lower layer failure is detected by the network, when it is not
engaged in a RF procedure. It is also used in the channel release procedure. Its purpose is to
release the channels in case of loss of communication. Its value is network dependent. NOTE: Its
value should be large enough to ensure that the MS detects a radio link failure.
T3111: This timer is used to delay the channel deactivation after disconnection of the main
signaling link. Its purpose is to let some time for possible repetition of the disconnection. Its
value is equal to the value of T3110.
T3113: This timer is started when the network has sent a PAGING REQUEST message and is
stopped when the network has received the PAGING RESPONSE message. Its value is network
dependent.
NOTE: The value could allow for repetitions of the Channel Request message and the
requirements associated with T3101.
T3115: This timer is used for the repetition of the VGCS UPLINK GRANT message during the
uplink access procedure. Its value is network dependent.
NOTE: This timer may be set to such a low value that the message is in fact continuously
transmitted.
T3117: This timer is started by the sending of a PDCH ASSIGNMENT COMMAND message and is
normally stopped when the MS has correctly accessed the target TBF. Its purpose is to keep the
Page 20 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
old channel sufficiently long for the MS to be able to return to the old channels, and to release
the channels if the MS is lost. Its value is network dependent.
NOTE: It could be higher than the maximum transmission time of the PDCH ASSIGNMENT
COMMAND message plus T3132 plus the maximum duration of an attempt to establish a data link
in multi-frame mode.
T3119: This timer is started by the sending of a RR-CELL CHANGE ORDER message and is
normally stopped when the MS has correctly accessed the new cell. Its purpose is to keep the old
channels sufficiently long for the MS to be able to return to the old channels, and to release the
channels if the MS is lost. Its value is network dependent.
NOTE: It could be higher than the maximum transmission time of the RR_CELL CHANGE ORDER,
plus T3134, plus the maximum duration of an attempt to establish a data link in multi-frame
mode.
T3141: This timer is started when a temporary block flow is allocated with an IMMEDIATE
ASSIGNMENT message during a packet access procedure. It is stopped when the mobile station
has correctly seized the temporary block flow. Its value is network dependent.
Page 21 of 22
Huawei Proprietary and Confidential
13-06-2016
GSM KPI Optimization Process and Guide INTERNAL
Thanks
Page 22 of 22
Huawei Proprietary and Confidential
13-06-2016