Ashanti Region Optimization Report

Ashanti Region Optimization Report for Vodafone GSM Swap Project
Optimization Report for Vodafone

GSM Swap Project
(Ashanti Region)
Huawei Technologies Co., Ltd.

May.2009
All rights reserved
2009-09-29
Page1, Total93
Content
1
SUMMARY ............................................................................................................................. 1
1.1
PROGRAM SUMMARY ........................................................................................................ 1
1.2
BSC SWAP P LAN ............................................................................................................... 1
1.3
OPTIMIZATION CONTENT EXPLANATION .......................................................................... 2
TRAFFIC KPI ANALYSES.................................................................................................... 3

2.1
2.1.1
KPI summary................................................................................................................ 3
2.1.2
Main KPI Trend Line ................................................................................................... 6
2.2
TRAFFIC KPI STATISTICS SUMMARY ................................................................................ 3
TOP BAD CELL ANALYSES AND P ROCESSING .................................................................. 13
2.2.1
TCH Call Drop ........................................................................................................... 13
2.2.2
Call Setup Success Rate.............................................................................................. 23
2.2.3
Handover Success Rate............................................................................................... 24
2.2.4
TCH congestion.......................................................................................................... 29
ANALYSIS OF DRIVE TEST .............................................................................................. 31

3.1
NETWORK SUMMARY ...................................................................................................... 31
3.2
ANALYSIS OF BCCHLEVEL ............................................................................................ 33
3.3
ANALYSIS OF RX_LEVEL (SUB) ....................................................................................... 36
3.4
ANALYSIS OF RX_QUALITY (SUB) ................................................................................... 39
3.5
ISSUE ANALYSIS .............................................................................................................. 42
3.5.1
Voice Quality Issue Analysis....................................................................................... 42
3.5.2
Crossing of feeder/antenna system Issue Analysis ...................................................... 46
3.5.3
Handover Failure Issue Analysis................................................................................ 48
3.6
EVENT A NALYSIS ............................................................................................................ 49
3.7
ANALYSIS OF DATA SERVICE .......................................................................................... 50
3.7.1
GPRS performance of BUOKROM_GT1005_2 .......................................................... 52
3.7.2
GPRS performance of AHWIA1079_1........................................................................ 53
3.7.3
GPRS performance of ATIMATIM1099_1 ................................................................. 54
3.7.4
GPRS/EDGE performance of MAGAZINE_OT1009_2.............................................. 55
3.7.5
GPRS/EDGE performance of AHWIA1079_1 ............................................................ 56
3.7.6
GPRS/EDGE performance of BANTAMA1030_1 ...................................................... 57
3.7.7
GPRS/EDGE performance of PATASI_GT1002 ........................................................ 59
3.7.8
GPRS/EDGE performance of SOFOLINE_SUNTRESO_SOUTH1022 ..................... 60
3.7.9
GPRS/EDGE performance of KWADASO_NSUOM1077........................................... 62
3.7.10
GPRS/EDGE performance of ANYINAM_AS1035_3 ............................................ 63
3.7.11
GPRS/EDGE performance of SOKOBAN1048_2................................................... 64
3.7.12
GPRS/EDGE performance of NEW_AHENEMA_KOKOBEN1074_1................... 66
3.7.13
GPRS/EDGE performance of UST_GT1004_3....................................................... 67
3.7.14
GPRS/EDGE performance of FUMESUA1050_3 .................................................. 68
3.7.15
GPRS/EDGE performance of ANWOMASO1088_3............................................... 69
2009-09-29
Page2, Total93
3.7.16
GPRS/EDGE performance of NHYIAESO1075_1 ................................................. 71
3.7.17
GPRS/EDGE performance of KUMASI_GBC_TD1008_2 ..................................... 72
3.7.18
GPRS/EDGE performance of SANTASI1073_3..................................................... 74
CR TROUBLESHOOTING.................................................................................................. 76
4.1
LOW OUTGOING INTER-BSC HANDOVER SUCCESS RATE ............................................... 76
4.2
LOW CALL SUCCESS RATE FOR BSC01 FROM APR 16TH TO APR 22ND ......................... 80
4.3
CALL DROPS IN ASHANTI ................................................................................................ 83
4.4
BALANCE OF TRAFFIC BETWEEN 900M AND 1800M ....................................................... 85
THE ISSUE EXISTING IN THE NETWORK..................................................................... 87
CONCLUSION...................................................................................................................... 88
APPENDIX 1.
2009-09-29
AMR KPI STATISTICS ..................................................................................... 89
Page3, Total93
1 Summary
1.1 Program summary
The Vodafone GSM Swap Project is involved in all the 10 regions of Ghana, the BSC and
BTS swap is from Alcatel Lucent. The GSM aspect involves 11 BSCs, 370 Swap sites and
770 new sites, totaling 1140 sites. The UMTS aspect involves 3 RNCs and 400 new sites.
These sites are distributed in all the ten regions shown in Figure 1.1, Upper East region,
Upper West region, Northern region, Brong-Ahafo region, Western region, Volta region,
Ashanti region, Greater Accra region, Eastern region and Central region.
Figure 1.1 Vodafone sites distribution
1.2 BSC Swap Plan

The data shown in Table 1.1 is the schedule of the Vodafone GSM Swap and the number
of BTSs that will be swapped. Huawei has finished swapping Alcatel Kumasi BSC 21,
Kumasi BSC 22, Kumasi BSC 23 and Kumasi BSC 24 to Huawei AS_KUM BSC01 and

AS_KUM BSC 02. This was finished on the 1st of April.
Presently, there are a total of 99 Huawei sites on air in the Ashanti region which consist of
83 swapped sites and 16 new sites.
BSC_Original
Mar
May
Jun
Jul Aug Sep
Oct
Nov
Total
Accra_BSC_21
Accra_BSC_22
14
13
14
13
Accra_BSC_23
13
13
Accra_BSC_24
Koforidua_BSC_1
17
Koforidua_BSC_2
Kumasi_BSC_21
Kumasi_BSC_22
Kumasi_BSC_23
Kumasi_BSC_24
Madina_BSC_1
Madina_BSC_2
Sunyani_BSC_1
Sunyani_BSC_2
Swedru_BSC_1
Takoradi_BSC_1
Takoradi_BSC_2
Tamale_BSC_1
Tamale_BSC_2
Tema_BSC_1
Tema_BSC_2
Total
15
10
17
9
25
16
24
16
24
19
24
21
13
8
16
28
13
17
27
21
83
59
23
57
34
10
23
33
35
48
19
24
21
13
8
16
28
13
17
27
21
10
23
371
Table 1.1 Swap Schedule
1.3 Optimization Content Explanation

The purpose of this network optimization is to make the KPIs better compared to the
previous network.
In summary the whole document contains KPI analyses, KPI comparison between
previous and present network and existing problems analyses. Analyses were based on
the following:
Traffic KPI analysis
Voice Drive Test contrast analysis
Voice Call Quality Test contrast analysis
Data Call Quality Test contrast analysis
Data Drive Test contrast analysis
Customer complaining analysis
2 Traffic KPI Analyses

2.1 Traffic KPI Statistics Summary
In the tables below are the Daily KPIs of 1 particular week before the Swap and 3
consecutive weeks immediately after the Swap. The Swap ended on 30 th Mar, 2009. The
3 consecutive weeks started on the 9th day of April, 2009. Optimization was done from
April 3rd to April 22nd. We can see that after the optimization, the performance of the
network has greatly improved because the KPI statistics and the drive test performances
have improved.
2.1.1 KPI summary

CS KPI:
Date
BSC ID
Call
Handover TCH SDCCH
TCH
SDCCH
Setup
Success Drop DROP Congestio Congestio
Success
Rate
Rate Rate
n
n
Rate
TCH
ERLANG
17/02/2009 Kumasi BSCs 98.20

18/02/2009 Kumasi BSCs 98.37
19/02/2009 Kumasi BSCs 97.56
90.98
1.13
0.55
0.16
0.09
29495.04
90.27
1.22
0.57
0.19
0.38
29369.28
89.51
1.09
0.54
0.19
0.00
28973.52
20/02/2009 Kumasi BSCs 97.62

21/02/2009 Kumasi BSCs 98.46
89.15
1.09
0.56
0.13
0.01
30098.88
90.22
1.15
0.59
0.11
0.03
30694.08
22/02/2009 Kumasi BSCs 98.43

23/02/2009 Kumasi BSCs 98.57
89.36
1.27
0.58
0.17
0.03
29495.20
90.54
1.14
0.56
0.20
0.04
29568.00
Table2.1 Alcatel BSC daily KPI before Swap(Weighted values)
Date
BSC ID
Call
Handover TCH SDCCH
Setup
TCH
SDCCH
TCH
Success Drop DROP
Congestion Congestion ERLANG
Success
Rate
Rate Rate
Rate
09/04/2009 Kumasi BSCs 97.77
96.28
0.41 0.13
0.15
3.24
34308.91
10/04/2009 Kumasi BSCs 97.84
96.33
0.40 0.11
0.09
0.00
34056.22
11/04/2009 Kumasi BSCs 97.75
96.28
0.42 0.12
0.14
0.00
32633.11
12/04/2009 Kumasi BSCs 97.77
96.12
0.44 0.13
0.08
0.02
31181.42
13/04/2009 Kumasi BSCs 97.38
96.13
0.46 0.13
0.51
0.60
29879.28
14/04/2009 Kumasi BSCs 97.70
96.31
0.43 0.13
0.21
0.12
32888.14
15/04/2009 Kumasi BSCs 97.78
96.38
0.43 0.15
0.40
0.17
32416.10
Table2.2 Huawei BSC daily KPI 1 week after Swap(Weighted values)
2009-09-29
Page3, Total93
Date
BSC ID
Call
Handover TCH SDCCH
Setup
TCH
SDCCH
Success Drop DROP
Success
Congestion Congestion
Rate
Rate
Rate
Rate
TCH
ERLANG
16/04/2009 Kumasi BSCs
98.34
98.58
0.38
0.10
0.26
0.12
30711.31
98.38
98.54
0.40
0.08
0.12
0.02
34435.37
98.48
98.56
0.39
0.11
0.08
0.02
33397.44
98.49
98.59
0.40
0.09
0.11
0.02
32152.87
98.22
98.63
0.33
0.08
0.24
0.02
32989.06
98.38
98.64
0.39
0.09
0.22
0.01
33961.56
98.64
98.62
0.39
0.09
0.17
0.03
33305.02
Table2.3 Huawei BSC daily KPI 2 weeks after Swap(Weighted values)
Date
BSC ID
Call
Handover TCH SDCCH
Setup
TCH
SDCCH
Success Drop DROP
Success
Congestion Congestion
Rate
Rate
Rate
Rate
TCH
ERLANG
23/04/2009 Kumasi BSCs 98.82
98.62
0.38
0.11
0.17
0.02
33875.04
24/04/2009 Kumasi BSCs 98.73
98.65
0.39
0.09
0.30
0.05
32112.19
25/04/2009 Kumasi BSCs 98.91
98.58
0.39
0.09
0.06
0.02
34067.54
26/04/2009 Kumasi BSCs 98.82
98.61
0.41
0.12
0.15
0.02
32709.00
27/04/2009 Kumasi BSCs 98.68
98.65
0.38
0.09
0.33
0.01
34486.03
28/04/2009 Kumasi BSCs 98.82
98.64
0.39
0.10
0.15
0.03
34499.83
29/04/2009 Kumasi BSCs 98.87
98.66
0.53
0.11
0.06
0.02
34362.10
Table2.4 Huawei BSC daily KPI 3 weeks after Swap(Weighted values)

PS KPI
Date
BSC ID
DL TBF
Requests
DL %
DL % TBF
TBF
drop
estab
success
UL TBF
Requests
UL % TBF
UL %
estab
TBF drop
success
227011
95.34
7.17
587311
93.94
4.72
863039
94.73
8.06
2516364
95.16
4.96
878254
94.33
7.86
2571266
94.98
5.35
868453
94.48
8.48
2497989
94.85
5.24
898824
94.54
7.98
2655057
94.91
5.04
866594
94.83
7.48
2484471
95.13
5.00
802557
94.73
7.31
2241617
95.13
4.95
862948
94.78
6.98
2357698
95.00
5.00
Table2.5 Alcatel BSC daily PS KPI before Swap (Weighted values)
2009-09-29
Page4, Total93
Date
BSC ID
DL TBF
Requests
DL % TBF
UL % TBF
DL % TBF UL TBF
UL % TBF
estab
estab
drop
Requests
drop
success
success
09/04/2009 Kumasi BSCs 683090
99.84
4.96
1603151
99.62
1.29
10/04/2009 Kumasi BSCs 674003
99.99
4.85
1838483
99.87
1.17
11/04/2009 Kumasi BSCs 682168
99.98
4.73
1933706
99.83
1.13
12/04/2009 Kumasi BSCs 636096
99.95
5.10
1686775
99.87
1.28
13/04/2009 Kumasi BSCs 611765
99.97
5.24
1540705
99.25
1.26
14/04/2009 Kumasi BSCs 647272
99.93
4.97
1660014
99.63
1.25
15/04/2009 Kumasi BSCs 669259
99.91
4.71
1681679
99.57
1.30
Table2.6 Huawei BSC daily PS KPI 1 week after Swap (Weighted values)
Date
BSC ID
DL TBF
Requests
DL % TBF
UL % TBF
DL % TBF UL TBF
UL % TBF
estab
estab
drop
Requests
drop
success
success
16/04/2009 Kumasi BSCs 918908
99.96
4.38
2071395
99.42
1.27
17/04/2009 Kumasi BSCs 985178
99.94
4.38
2247930
99.80
1.27
18/04/2009 Kumasi BSCs 928932
99.96
4.84
2115071
99.86
1.57
19/04/2009 Kumasi BSCs 882776
99.98
4.76
2107836
99.57
1.40
20/04/2009 Kumasi BSCs 768136
99.83
4.79
1571903
99.47
1.72
21/04/2009 Kumasi BSCs 1011878
99.91
4.84
2429801
99.66
1.44
22/04/2009 Kumasi BSCs 957355
99.94
5.32
2148960
99.59
1.59
Table2.7 Huawei BSC daily KPI PS 2 weeks after Swap (Weighted values)
Date
BSC ID
DL TBF
Requests
DL % TBF
UL % TBF
DL % TBF UL TBF
UL % TBF
estab
estab
drop
Requests
drop
success
success
23/04/2009 Kumasi BSCs 910157
99.86
5.55
2165337
99.61
1.51
24/04/2009 Kumasi BSCs 950993
99.97
5.47
2151839
99.63
1.56
25/04/2009 Kumasi BSCs 915056
99.98
6.13
2014697
99.77
1.73
26/04/2009 Kumasi BSCs 956841
99.96
5.99
2138721
99.76
1.78
27/04/2009 Kumasi BSCs 985081
99.90
5.20
2215142
99.23
1.52
28/04/2009 Kumasi BSCs 976657
99.94
4.76
2164522
99.65
1.53
29/04/2009 Kumasi BSCs 982837
99.95
4.76
2218151
99.72
1.45
Table2.8 Huawei BSC daily KPI PS 3 weeks after Swap (Weighted values)
2009-09-29
Page5, Total93
2.1.2 Main KPI Trend Line

(1) TCH Drop Rate
TCH Drop Rate
TCH Drop Rate Comparison

1.40
1.30
1.20
1.10
1.00
0.90
0.80
0.70
0.60
0.50
0.40
0.30
0.20
1
before swap
after swap(2 weeks)
after swap(1 week)

after swap(3 weeks)
Figure 2.1 TCH Drop Rate Comparisons

From Figure 2.1, it is clear that the TCH Drop Rate has improved after the Swap. Between
the 1st week and 3rd week after Swap, there is no much difference in the values. Work is
still on-going to achieve even better results.
(2) Call Setup Success Rate
Call setup Success Rate Comparison
Call setup Success Rate
99.50
99.00
98.50
98.00
97.50
97.00
96.50
1
before swap
after swap(2 weeks)
after swap(1 week)

after swap(3 weeks)
Figure 3.1 Call Setup Success Rate Comparisons

2009-09-29
Page6, Total93

From Figure 2.2, we can see that the Call Setup Success Rate has improved after the
Swap. It improved greatly to an average of 98.8% in the 3rd week.
But for the second week, we can see that the Call setup Success Rate is low, and this was
caused by the bad site MILLENIUM_PLAZA.
On the 15th of April, Huawei and Vodafone re-homed BSC02 from RCP3 to RCP1, and
make the site MILLENIUM_PLAZA wrong signal point which caused low call setup
success rate of MILLENIUM_PLAZA, so the whole BSC is affected.
This issue is described in details in Chapter 4.
(3) Handover Success Rate
Handover Success Rate
Handover Success Rate Comparison

99.50
99.00
98.50
98.00
97.50
97.00
96.50
96.00
95.50
95.00
94.50
94.00
93.50
93.00
92.50
92.00
91.50
91.00
90.50
90.00
89.50
89.00
1
before swap
after swap(2 weeks)
after swap(1 week)

after swap(3 weeks)
Figure 4.1 Handover success Rate Comparisons

From Figure 2.3, we can see that the Handover Success Rate has improved after the
Swap. The first week was a little lower than the other two weeks after swap; this was
caused by an MSC issue involving inter-RCPs.
On the 15th of April, Huawei and Vodafone re-homed BSC02 from RCP3 to RCP1, and
subsequently, the Inter-BSC handover became normal, shown in the figure above.
2009-09-29
Page7, Total93

(4) TCH Traffic Erlang
TCH TRAFFIC ERLANG Comparison

35000
TCH ERLANG
34000
33000
32000
31000
30000
29000
28000
1
before swap
after swap( 2 weeks)
after swap(1 week)

after swap(3 weeks)
Figure 5.1 TCH Traffic Comparisons

From Figure 2.4, the average TCH traffic has slightly improved. This is obviously as a
result of the increased coverage provided after the Swap and the integration of new sites
in Ashanti Region.
(5) TCH Congestion Rate
TCH Congestion rate
TCH Congestion Comparison

0.60
0.50
0.40
0.30
0.20
0.10
0.00
1
before swap
after swap(2 weeks)
after swap(1 week)

after swap(3 weeks)
Figure 6.1 TCH Congestion Rate Comparisons

From Figure 2.5, we can see that the TCH congestion Rate on the 13th of April is higher
than the other days. Compared with Figure 2.4, we can see that the traffic was also low on
2009-09-29
Page8, Total93

that same day.
Tracing the alarms history, we found that there were many sites flashed down on that day
caused by LAPD Link instability. After calculating, there were 83 LAPD Faults and 270
different cells out of service (Cell out of service alarms). Details of this are contained in the
attachment.
HistoryAlarms for
BSC02 of Apr 13th.xls
And also we got the top bad cells for TCH congestion rate on that day, shown in the table
below:
Date
Cell Name
Failed TCH
Failed TCH
Seizures in TCH
TCH
Seizures due
TCH
TCH
Handovers due
Congestion
to Busy TCH
Availability Traffic
to Busy TCH
Rate
(Traffic
(Traffic
Channel)
Channel)
13/04/2009 KUMAWU_GSM_1
369
10
9.56
61.22
35.93
13/04/2009 KUMAWU_GSM_2
126
8.07
61.02
14.78
57.96
32.95
13/04/2009 KUMAWU_GSM_3
221
63
7.60
13/04/2009 EFFIDUASE_3
368
7.44
63.18
42.50
592
7.67
62.75
69.48
463
195
8.61
61.91
60.89
Table2.9 The top bad cells for TCH congestion rate on the 13th of April
From Table 2.9, we can see that the TCH availability was very low, so this was caused by
the transmission instability.
From Alarms History for BSC02, we can see these two sites alarms contain many LAPD
Faults and Cell out of service alarms.
2009-09-29
Page9, Total93

(6) SDCCH Congestion Rate
SDCCH Congestion Comparison
SDCCH Congestion rate
3.50
3.00
2.50
2.00
1.50
1.00
0.50
0.00
1
before swap
after swap(2 weeks)
after swap(1 week)

after swap(3 weeks)
Figure 7.1 SDCCH Congestion Rate Comparisons

From Figure 2.6 above, we can see that SDCCH congestion before and after swap are
fairly low except for an isolated incidence on the 9th of April one week after the swap. This
was as a result of a LAPD link being unstable. It affected a number of sites and resulted in
a number of location updates and cell reselections when the cells came back on. This
caused a strain on the SDCCH resource.
Alarm name
Alarm raised time
Cleared time
Alarm source
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
FUMESUA
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
ANYINAM_AS
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
MANSO_NKWANTA_GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
DUNKWA_RS_GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
BIBIANI_GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:06
BOKRO
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
OBUASI_SEC_TECH_OT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
KANKANFRANSIE
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
OBUASI_GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
KUNTANASE_GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
BONWIRE
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
NKAWIE
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
EFFIDUASE GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
BEKWAI_GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
NEW KOFORIDUA KASAPA
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
DCS_ASSIN_FOSU_GBC_GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
AYEDUASE
2009-09-29
Page10, Total93

LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
DCS_BONWIRE_GT
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
JUASO
LAPD OML Fault
2009-4-9 11:06
2009-4-9 11:07
BOANKRA
LAPD OML Fault
2009-4-9 12:16
2009-4-11 16:56
JACHIE PREMSU
Table2.10
LAPD OML Alarms
(7) GPRS Downlink TBF Establish Success Rate
DownLink TBF Establish Success Rate
DownLink TBF Establish Success Rate Comparison

100.50
100.00
99.50
99.00
98.50
98.00
97.50
97.00
96.50
96.00
95.50
95.00
94.50
94.00
1
before swap
after swap(2 weeks)
after swap (1week)

after swap(3 weeks)
Figure 8.1 Downlink TBF Establish Success Rate Comparison

From Figure 2.7 above, we can see that the Downlink TBF Establish Success rate has
improved after the swap. It has improved to a average of 99.93% after the swap.
2009-09-29
Page11, Total93
(8) GPRS Downlink TBF Drop Rate

Downlink TBF drop Rate Comparison
9.00
Downlink TBF drop Rate
8.50
8.00
7.50
7.00
6.50
6.00
5.50
5.00
4.50
4.00
3.50
3.00
1
before swap
after swap(2 weeks)
after swap(1week)
after swap(3 weeks)
Figure 9.1 Downlink TBF Drop Rate Comparison

From Figure 2.8 above, the downlink TBF drop rate improved generally after the swap but
increased slightly in the 3rd week.
The downlink TBF drop rate after swap is a little higher than before Swap. This is because
of the version of BSC, C12B195. The version C12B195SP05 or above will resolve this
issue. Huawei will upgrade BSC version as soon as possible.
(9) GPRS Uplink TBF Establish Success Rate

Uplink TBF Establish Success Rate
Uplink TBF Establish Success Rate Comparison

100.5
100.0
99.5
99.0
98.5
98.0
97.5
97.0
96.5
96.0
95.5
95.0
94.5
94.0
1
before swap
after swap(2 weeks)
after swap(1 week)

after swap(3 weeks)
Figure 10.1 Uplink TBF Establish Success Rate Comparison

2009-09-29
Page12, Total93

From Figure 2.9 above, the uplink TBF Establish Success rate has greatly improved after
the swap at an average of 99.6%.
(10) GPRS Uplink TBF Drop Rate
U p li nk T BF Dr op R at e C om pa ri so n
6.0
U pl in k T BF d ro p R at e
5.5
5.0
4.5
4.0
3.5
3.0
2.5
2.0
1.5
1.0
0.5
0.0
1
before swap
after swap(2 weeks)
after swap(1 week)

after swap(3 weeks)
Figure 11.1 Uplink TBF Drop Rate Comparison

From Figure 2.10 above, the uplink TBF drop rate improved greatly after the swap but has
slightly gone up in the third week. Analysis is on-going to find out the issue.
2.2 Top Bad Cell Analyses and Processing

2.2.1 TCH Call Drop
The following data is about the top bad cells, both top call Drops on TCH and top Call
Drop Rate on TCH.
Date
Period(hour)
Object Name
Cell Name
Call Drops on
TCH
Call Drop Rate

on TCH
23/04/2009
24
AS_KUM_BSC01
ATEBUBU_GT_2
164
1.26
24/04/2009
24
AS_KUM_BSC01
ATEBUBU_GT_2
118
1.04
26/04/2009
24
AS_KUM_BSC01
ATEBUBU_GT_2
154
1.33
28/04/2009
24
AS_KUM_BSC01
ATEBUBU_GT_2
134
1.10
29/04/2009
24
AS_KUM_BSC01
ATEBUBU_GT_2
137
1.10
23/04/2009
24
AS_KUM_BSC02
AWASO_2
108
1.65
26/04/2009
24
AS_KUM_BSC02
AWASO_2
138
2.00
27/04/2009
24
AS_KUM_BSC02
AWASO_2
102
1.65
2009-09-29
Page13, Total93

28/04/2009
24
AS_KUM_BSC02
AWASO_2
115
1.76
29/04/2009
24
AS_KUM_BSC02
AWASO_2
114
1.64
23/04/2009
24
AS_KUM_BSC02
AWASO_3
128
1.35
25/04/2009
24
AS_KUM_BSC02
AWASO_3
105
1.13
28/04/2009
24
AS_KUM_BSC02
AWASO_3
105
1.18
29/04/2009
24
AS_KUM_BSC02
AWASO_3
118
1.26
23/04/2009
24
AS_KUM_BSC02 DUNKWA_RS_GT_1
120
1.79
25/04/2009
24
122
1.80
26/04/2009
24
110
1.56
27/04/2009
24
103
1.43
28/04/2009
24
156
2.06
29/04/2009
24
137
1.86
23/04/2009
24
386
1.42
24/04/2009
24
298
1.24
25/04/2009
24
374
1.33
26/04/2009
24
405
1.34
27/04/2009
24
360
1.29
28/04/2009
24
318
1.16
29/04/2009
24
346
1.29
25/04/2009
24
AS_KUM_BSC01 KOFORIDUA AS_2
471
2.11
26/04/2009
24
300
1.54
27/04/2009
24
313
1.52
28/04/2009
24
270
1.25
29/04/2009
24
202
0.99
23/04/2009
24
AS_KUM_BSC02 NEW_EDUBIASE_1
173
1.26
24/04/2009
24
126
1.18
25/04/2009
24
165
1.22
26/04/2009
24
236
1.49
27/04/2009
24
180
1.25
28/04/2009
24
199
1.39
29/04/2009
24
155
1.15
Table2.11
The top bad cells for call drop
From Table 2.12 below, nearly all the call drops happened on the radio interface in stable
state while only a few in the handover state. And all the call drops on radio interface were
because by radio link failure which contains Error Indication and Connection Failure. The
procedure is as follows:
After the MS seizes a channel, the BTS sends the BSC an ERR IND message, indicating
that a call drop occurs on the Um interface because of the abnormal connection on the
radio link layer.
2009-09-29
Page14, Total93

After the MS seizes a channel, the BTS sends the BSC a CONN FAIL IND message,
indicating that a call drop occurs on the Um interface because of the abnormal connection
on the radio link layer.
Call Drops
Call Drops
on Radio
Call
on Traffic
Call
Interface in Drops
Channel in
Handover
Drops
on
Stable State
State
Radio on TCH
(Connection
(Traffic
Interface
Failure)
Channel)
Date
Period
(hour)
Cell Name
Call Drops
on Traffic
Channel in
Stable State
(Error
Indication)
23/04/2009
24
ATEBUBU_GT_2
67
90
161
164
24/04/2009
24
ATEBUBU_GT_2
46
61
11
118
118
26/04/2009
24
ATEBUBU_GT_2
80
71
154
154
28/04/2009
24
ATEBUBU_GT_2
60
69
134
134
29/04/2009
24
ATEBUBU_GT_2
58
73
137
137
23/04/2009
24
AWASO_2
46
61
108
108
26/04/2009
24
AWASO_2
48
90
138
138
27/04/2009
24
AWASO_2
33
69
102
102
28/04/2009
24
AWASO_2
48
65
115
115
29/04/2009
24
AWASO_2
47
67
114
114
23/04/2009
24
AWASO_3
53
74
128
128
25/04/2009
24
AWASO_3
44
61
105
105
28/04/2009
24
AWASO_3
45
60
105
105
29/04/2009
24
AWASO_3
51
67
118
118
23/04/2009
24
DUNKWA_RS_GT_1
53
66
120
120
25/04/2009
24
DUNKWA_RS_GT_1
55
64
122
122
26/04/2009
24
DUNKWA_RS_GT_1
54
52
106
110
27/04/2009
24
DUNKWA_RS_GT_1
67
34
103
103
28/04/2009
24
DUNKWA_RS_GT_1
54
98
156
156
29/04/2009
24
DUNKWA_RS_GT_1
63
73
137
137
23/04/2009
24
DUNKWA_RS_GT_2
209
165
12
386
386
24/04/2009
24
DUNKWA_RS_GT_2
167
119
293
298
25/04/2009
24
DUNKWA_RS_GT_2
189
175
10
374
374
26/04/2009
24
DUNKWA_RS_GT_2
199
176
13
388
405
27/04/2009
24
DUNKWA_RS_GT_2
177
170
13
360
360
28/04/2009
24
DUNKWA_RS_GT_2
162
146
10
318
318
29/04/2009
24
DUNKWA_RS_GT_2
199
138
346
346
25/04/2009
24
KOFORIDUA AS_2
137
290
44
471
471
26/04/2009
24
KOFORIDUA AS_2
90
147
14
251
300
27/04/2009
24
KOFORIDUA AS_2
94
197
22
313
313
28/04/2009
24
KOFORIDUA AS_2
81
150
12
243
270
29/04/2009
24
KOFORIDUA AS_2
61
104
11
176
202
23/04/2009
24
NEW_EDUBIASE_1
85
85
173
173
2009-09-29
Page15, Total93

24/04/2009
24
NEW_EDUBIASE_1
64
60
125
126
25/04/2009
24
NEW_EDUBIASE_1
74
91
165
165
26/04/2009
24
NEW_EDUBIASE_1
127
102
231
236
27/04/2009
24
NEW_EDUBIASE_1
89
89
180
180
28/04/2009
24
NEW_EDUBIASE_1
108
87
199
199
29/04/2009
24
NEW_EDUBIASE_1
74
78
155
155
Table2.12
The reason caused call drops
(1) ATEBUBU_GT_2
Date
TRX
Index
Mean
Mean
Mean
Mean
Downlink
Downlink
Downlink
Downlink
Mean TA
Mean TA
Level
Level
Quality
Quality
during
during
during
during
during
during
Radio Link Radio Link
Radio Link Radio Link Radio Link Radio Link
Failure
Failure
Failure
Failure
Failure
Failure
(TCHF)
(TCHH)
(TCHF)
(TCHH)
(TCHF)
(TCHH)
23/04/2009
37
1.42
2.98
6.79
6.31
12.04
12.19
23/04/2009
36
22.29
22.09
1.53
2.64
10.69
10.91
24/04/2009
37
5.26
3.04
6.17
5.96
9.51
14.11
24/04/2009
36
20.07
22.50
2.03
2.67
8.53
7.67
25/04/2009
37
4.09
5.14
5.76
5.91
10.72
12.77
25/04/2009
36
19.23
23.20
1.77
4.00
7.20
8.80
26/04/2009
37
2.86
0.97
6.40
6.76
12.35
13.97
26/04/2009
36
19.10
22.50
1.27
3.25
8.30
12.25
27/04/2009
37
4.09
3.29
5.46
5.83
9.49
13.83
27/04/2009
36
22.22
20.25
1.68
3.00
9.92
7.75
28/04/2009
37
2.83
2.89
6.30
6.54
11.70
10.97
28/04/2009
36
19.21
21.22
1.67
2.67
10.67
14.00
29/04/2009
37
3.12
1.80
6.26
6.57
11.08
12.63
29/04/2009
36
20.12
25.50
1.19
1.00
10.74
10.00
Table2.13
The Level, Quality and TA when call drop
From Table 2.13 above, we can see that there was no abnormity on the TRX 36. But for
the TRX 37, all the mean downlink quality during call drop was nearly bigger than 5, and at
the same time, the mean downlink level is lower than -100 dBm. So all the call drops
happened in ATEBUBU_GT_2 cell were caused by the poor coverage of TRX 37.
Further more, a check on the uplink and downlink balance shows that the signal of
downlink is weaker than the signal of uplink; the statistics shown below:
2009-09-29
Page16, Total93
U pli nk a nd D ow nl in k Ba la nc e
25.00
Ra te (% )
20.00
15.00
10.00
5.00
Le
ve
l
11
10
9
l
ve
Le
Le
ve
7
ve
l
Le
Le
ve
5
ve
l
Le
ve
Le
Le
ve
l
3
=
2
l
=
Le
ve
ve
l
Le
Le
ve
0.00
Figure 12.1 The uplink and downlink balance statistics for TRX 37 in 3 weeks
The problem has been reported to Huawei BSS Dept. to check feeder, cable and
hardware for this TRX.
(2) AWASO_2
Date
TRX Index
Mean Downlink Level Mean Downlink Quality Mean TA during

during Radio Link
during Radio Link
Radio Link
Failure (TCHF)
Failure (TCHF)
Failure (TCHF)
23/04/2009
6.22
4.64
39.37
23/04/2009
11.36
1.71
42.00
24/04/2009
6.90
4.23
38.04
24/04/2009
12.94
2.77
33.29
25/04/2009
6.92
3.65
39.15
25/04/2009
10.65
2.90
42.30
26/04/2009
7.39
3.72
40.42
26/04/2009
10.15
3.31
46.12
27/04/2009
7.06
4.32
38.73
27/04/2009
12.05
3.47
36.63
28/04/2009
5.82
4.41
40.88
28/04/2009
11.25
2.10
37.15
29/04/2009
5.16
4.10
38.98
29/04/2009
10.71
3.36
40.00
Table2.14
The Level, Quality and TA when call drop
From Table 2.14 above, we can see that all the mean downlink quality when call dropped
were smaller than 5, so the call quality was good. But the most of the mean downlink level
were lower than -100 dBm, and the check of the TA showed that the call drops mostly
2009-09-29
Page17, Total93

occurred at TA bigger than 40 which equals to 22 Km. So the call drops in AWASO_2
were caused by long distance.
Further checking on the location of this site shows that this site is a rural site, shown in the
map below:
Figure 13.1 The location of AWASO on the map

Problem solution for AWASO_2 is the same as AWASO_3.
(3) DUNKWA_RS_GT_1
From the below table, we can see that the mean downlink quality were no bigger than 5,
but the mean downlink level is lower than -100 dBm, and the TA is about 15 Km. So the
call drops happened at the edge of the coverage where the downlink level is not high
enough to sustain the call.
Date
TRX
Index
Mean Downlink Quality

during Radio Link Failure
(TCHF)
23/04/2009
166
4.73
4.07
27.73
23/04/2009
165
3.03
8.79
26.85
23/04/2009
164
4.89
4.85
23.91
23/04/2009
163
3.69
7.00
28.39
24/04/2009
166
5.41
4.32
24.62
24/04/2009
165
3.31
7.62
21.08
24/04/2009
164
5.40
6.76
17.63
24/04/2009
163
3.00
10.08
25.50
25/04/2009
166
5.31
3.39
24.83
25/04/2009
165
3.62
6.42
27.19
25/04/2009
164
4.70
4.41
24.78
2009-09-29
Mean Downlink Level

Mean TA during
during Radio Link Failure Radio Link Failure
(TCHF)
(TCHF)
Page18, Total93

25/04/2009
163
5.05
4.65
21.60
26/04/2009
166
5.02
3.60
28.42
26/04/2009
165
3.43
6.95
28.19
26/04/2009
164
4.98
5.03
23.18
26/04/2009
163
3.95
7.21
27.11
27/04/2009
166
4.97
3.81
27.75
27/04/2009
165
3.89
8.07
24.93
27/04/2009
164
5.28
3.67
23.04
27/04/2009
163
5.18
6.59
29.82
28/04/2009
166
4.32
5.75
27.43
28/04/2009
165
2.96
6.44
28.37
28/04/2009
164
4.61
4.36
29.64
28/04/2009
163
3.68
6.26
31.32
29/04/2009
166
5.61
4.35
20.53
29/04/2009
165
3.38
7.67
27.05
29/04/2009
164
4.87
5.23
28.49
29/04/2009
163
3.95
6.15
28.95
Table2.15
The Level, Quality and TA when call drop for DUNKWA_RS_GT_1
(4) DUNKWA_RS_GT_2
From the table below, we can see that the all the mean downlink quality during radio link
failure for TRX 168 were bigger than 5, and at the same time, the mean downlink level
were lower than -105 dBm. The mean TA when call drops happened is about 6 Km, which
means all the call drops were nearby drops.
Date
TRX
Index
Mean
Mean
Mean
Mean
Downlink Downlink Downlink Downlink Mean TA
Mean TA
Level
Level
Quality
Quality
during
during
during
during
during
during
Failure
Failure
Failure
Failure
Failure
Failure
(TCHF)
(TCHH)
(TCHF)
(TCHH)
(TCHF)
(TCHH)
23/04/2009
168
3.39
3.31
23/04/2009
167
17.88
19.06
24/04/2009
168
2.84
2.56
24/04/2009
167
21.50
16.04
25/04/2009
168
2.72
25/04/2009
167
26/04/2009
6.07
11.06
2.60
1.98
15.40
15.22
6.30
6.23
8.91
11.58
2.07
2.25
11.52
11.50
4.06
6.15
5.70
11.36
12.25
18.33
21.52
2.67
1.82
12.46
12.00
168
4.06
2.78
5.82
6.07
9.76
14.34
26/04/2009
167
19.24
20.47
1.61
1.95
13.12
14.83
27/04/2009
168
3.15
2.84
6.11
6.19
8.96
12.90
27/04/2009
167
19.80
20.98
2.57
2.11
10.55
12.89
28/04/2009
168
3.75
3.21
6.05
6.02
9.38
12.20
2009-09-29
5.92
13.63
Page19, Total93

28/04/2009
167
18.97
19.46
1.53
1.72
11.50
15.63
29/04/2009
168
2.92
3.50
6.48
6.04
11.03
11.66
29/04/2009
167
19.92
15.75
1.63
2.35
11.80
13.71
Table2.16
The Level, Quality and TA when call drop for DUNKWA_RS_GT_2
Further checking on the Uplink and Downlink balance, just as the below figure:
Uplink and Downlink Balance
Percentage(%)
25.00
20.00
15.00
10.00
5.00
Le
ve
l
=
Le
1
ve
l
=
Le
2
ve
l
=
Le
3
ve
l
=
Le
4
ve
l
=
Le
5
ve
l
=
Le
6
ve
l
=
Le
7
ve
l
=
Le
8
ve
l
=
Le
9
ve
l
=
Le
10
ve
l
=
11
0.00
Figure 14.1 The Uplink and Downlink balance statistics for TRX 168 in 3 weeks
From the Figure 2.13 above, it is easy to find that the downlink is far weaker than the
uplink.
So a report has been made to Huawei BSS check on cable, feeder and hardware for TRX
168.
(5) NEW_EDUBIASE_1
The following table shows that the mean downlink level (TCH full rate) during radio link
failure is smaller than 5, but the mean downlink level is lower than -100 dBm. And the
mean TA is about 20 which equals to 11 Km. so the call drops were caused by low
downlink level. The Half Rate TCH is the same as full rate.
So the high call drop on TCH for NEW_EDUBIASE_1 is caused by bad coverage.
The tilt of antenna and power control configurations should be checked and adjusted.
2009-09-29
Page20, Total93

Date
Mean
Mean
Mean
Mean
Downlink Downlink Downlink Downlink Mean TA
Mean TA
Level
Level
Quality
Quality
during
during
TRX Index
during
during
during
during
Failure
Failure
Failure
Failure
Failure
Failure
(TCHF)
(TCHH)
(TCHF)
(TCHH)
(TCHF)
(TCHH)
23/04/2009
196
6.48
2.00
4.09
6.00
20.48
25.00
23/04/2009
195
6.74
4.50
4.51
5.00
20.40
11.00
23/04/2009
194
3.71
19.50
5.76
1.00
19.48
8.00
23/04/2009
193
7.21
11.60
4.21
3.60
23.49
15.60
24/04/2009
196
5.15
4.55
20.15
24/04/2009
195
3.88
4.97
22.06
24/04/2009
194
4.20
5.12
19.74
24/04/2009
193
4.59
4.88
20.59
25/04/2009
196
4.85
20.00
4.98
1.00
23.00
5.00
25/04/2009
195
5.41
13.33
4.32
3.33
22.19
12.00
25/04/2009
194
4.96
4.68
21.25
25/04/2009
193
6.63
14.00
3.82
0.00
20.44
19.00
26/04/2009
196
6.94
1.00
4.90
7.00
20.16
24.00
26/04/2009
195
6.35
12.33
4.98
3.00
20.78
17.67
26/04/2009
194
5.35
4.78
20.24
26/04/2009
193
7.83
17.17
3.67
2.50
20.94
20.17
27/04/2009
196
4.27
19.00
5.00
7.00
19.81
19.00
27/04/2009
195
4.83
4.33
21.52
27/04/2009
194
6.44
3.00
4.46
7.00
19.58
25.00
27/04/2009
193
6.22
10.00
4.68
0.00
24.32
10.00
28/04/2009
196
5.33
5.00
5.33
3.00
20.10
25.00
28/04/2009
195
8.49
4.81
18.26
28/04/2009
194
4.32
5.26
19.90
28/04/2009
193
5.68
10.00
4.80
4.00
22.05
29.00
29/04/2009
196
5.39
14.00
4.33
1.00
21.54
19.50
29/04/2009
195
6.10
5.10
21.15
29/04/2009
194
5.11
5.08
21.41
29/04/2009
193
8.75
14.00
4.04
1.00
22.00
20.00
Table2.17
The Level, Quality and TA when call drop for NEW_EDUBIASE_1
(6) KOFORIDUA AS_2

The following table shows that the mean downlink level was good when the drop calls
happened. At the same time, the mean downlink quality during radio link failure is smaller
than 5, so the quality was good.
And the mean TA during radio link failure were no more than 10 which equals 5 Km, so all
2009-09-29
Page21, Total93

the call drops occurred were nearby call drops.
Start Time
Mean
Mean
Mean
Mean TA Mean TA
Downlink
Downlink Downlink
Mean Downlink
during
during
Level
Quality
Quality
TRX
Level during
Radio
Radio
during
during
during
Link
Link
Index
Radio Link
Radio Link
Failure (TCHH)
Failure
Failure
Failure
Failure
Failure
(TCHF)
(TCHH)
(TCHF)
(TCHF)
(TCHH)
23/04/2009
615
15.44
14.09
4.17
4.16
5.56
8.22
23/04/2009
614
21.22
19.74
2.80
2.97
8.16
10.21
24/04/2009
615
11.20
15.19
4.85
3.75
9.30
7.59
24/04/2009
614
17.72
19.86
2.48
2.47
7.41
5.60
25/04/2009
615
16.30
17.42
3.59
3.60
5.10
6.31
25/04/2009
614
21.18
21.62
2.24
2.24
6.26
5.87
26/04/2009
615
13.51
15.16
3.53
3.52
7.78
8.34
26/04/2009
614
18.42
21.34
3.00
2.86
7.38
7.45
27/04/2009
615
12.84
16.89
4.06
3.60
9.62
7.00
27/04/2009
614
16.29
21.20
2.44
2.57
6.61
4.71
28/04/2009
615
11.75
13.86
4.29
3.78
10.00
8.99
28/04/2009
614
19.71
18.26
2.54
2.54
8.62
6.32
29/04/2009
615
12.57
15.00
4.04
4.02
11.30
7.79
29/04/2009
614
17.63
20.88
3.05
2.70
5.35
7.62
Table2.18
The Level, Quality and TA when call drop for KOFORIDUA AS_2
Further checking on the interference band, it shows in the figure below:

Interference Band
60.00
P e rc e n ta g e (% )
50.00
40.00
TCHF
TCHH
30.00
20.00
10.00
0.00
Band 1
Band 2
Band 3
Band 4
Band 5
Figure 15.1 The interference band for TRX 614 from 10:00 to 23:00 of Apr 25th
From Figure 2.14 above, it is easy to get that there was heavy interference on TRX 614,
and this occurred on the subsequent days.
And the data shows that the interference fluctuated with the traffic, so the interference was
2009-09-29
Page22, Total93

belonging to intra-network interference.
The more checking on TRX 615 shows that the phenomenon was the same.
Apart from these, we checked the alarms for this site; there were some LAPD OML Faulty
and Cell Out of Service alarms. So the call drops were also partly influenced by Lapd link
not stable.
Alarm name
Alarm raised time
Cleared time
Alarm source
LAPD OML Fault
2009-4-26 14:49
2009-4-26 14:54
KOFORIDUA AS
Cell Out of Service
2009-4-26 14:49
2009-4-26 14:54
KOFORIDUA AS
LAPD OML Fault
2009-4-26 14:54
2009-4-26 15:14
KOFORIDUA AS
Cell Out of Service
2009-4-26 14:54
2009-4-26 15:15
KOFORIDUA AS
Cell Out of Service
2009-4-26 15:15
2009-4-26 15:16
KOFORIDUA AS
LAPD OML Fault
2009-4-26 16:14
2009-4-26 16:59
KOFORIDUA AS
Cell Out of Service
2009-4-26 16:14
2009-4-26 17:00
KOFORIDUA AS
LAPD OML Fault
2009-4-28 13:01
2009-4-28 13:13
KOFORIDUA AS
Cell Out of Service
2009-4-28 13:01
2009-4-28 13:13
KOFORIDUA AS
Cell Out of Service
2009-4-28 13:37
2009-4-28 13:50
KOFORIDUA AS
LAPD OML Fault
2009-4-28 13:37
2009-4-28 13:50
KOFORIDUA AS
LAPD OML Fault
2009-4-29 11:22
2009-4-29 11:24
KOFORIDUA AS
Cell Out of Service
2009-4-29 11:22
2009-4-29 11:24
KOFORIDUA AS
Table2.19
The history alarms for KOFORIDUA AS
2.2.2 Call Setup Success Rate

The following data is about the top bad cells, both top bad Call Setup Success Rate and
top bad Failed Assignments.
Cell Name
Failed Assignments
Failed
Call Setup
Failed
Successful
(First Assignment, Assignments
Success
Assignments
TCH
Assignment Timed
(Channel
Rate
(Um Cause)
Seizures
Out)
Unavailable)
ATEBUBU_GT_2
91.53
18
490
5415
ATEBUBU_GT_2
93.06
30
99
350
4931
ATEBUBU_GT_2
90.93
21
436
4453
ATEBUBU_GT_2
90.10
23
530
4970
ATEBUBU_GT_2
93.98
18
287
4528
ATEBUBU_GT_2
92.79
20
382
5060
ATEBUBU_GT_2
92.64
16
383
4895
DUNKWA_RS_GT_2
95.92
89
97
835
21559
DUNKWA_RS_GT_2
95.85
64
108
852
21846
DUNKWA_RS_GT_2
95.92
70
218
940
24065
DUNKWA_RS_GT_2
95.58
63
97
966
22473
DUNKWA_RS_GT_2
95.78
64
54
883
21696
2009-09-29
Page23, Total93

DUNKWA_RS_GT_2
95.49
74
48
923
21188
KOFORIDUA AS_2
90.41
273
57
1677
16798
KOFORIDUA AS_2
94.71
98
97
781
15510
KOFORIDUA AS_2
93.10
134
50
1083
15749
KOFORIDUA AS_2
93.98
113
300
1010
16832
KOFORIDUA AS_2
96.00
61
186
614
16377
Table2.20
The call setup success rate top bad cells
From Table 2.20 above, we can see that all the call drops were caused by the reasons:
Assignment Time Out, Channel unavailable and Um case, and the failed assignments
were mainly caused by Um interface.
Coincidentally, we realized that the cells with low call setup success rate are the same
ones which have a high drop call rate so solving the call drop rate would also reduce the
call setup success rate.
For ATEBUBU_GT_2 and DUNKWA_RS_GT_2, the low call setup success rate was
caused by the unbalance between uplink and downlink. (The statistics have been shown
in chapter 2.2.1)
KOFORIDUA AS_2 has the heavy interference. (The statistics have been shown in
chapter 2.2.1)
2.2.3 Handover Success Rate

The following data is about the top bad cells, both top handover failures and top bad
handover success rate.
Date
Cell
Success Success
Failed
Total Rate of Rate of
Outgoing
Inter-Cell
Ho Fail
amount
Cell
Cell
Outgoing
HO Outgoing Incoming
Reconn
Ho
Fail
Ho
Ho
Source Cell
Target Cell
25/04/2009
ABOABO A/R_2
KUMASI_GBC_TD_1
36
33
14.63
6.67
26/04/2009
ABOABO A/R_2
KUMASI_GBC_TD_1
35
28
5.41
10.53
27/04/2009
ABOABO A/R_2
KUMASI_GBC_TD_1
41
37
4.65
20.51
28/04/2009
ABOABO A/R_2
KUMASI_GBC_TD_1
43
35
0.00
5.66
28/04/2009
MAMPONG_GT_1
KUMAWU_GSM_1
16
16
0.00
24/04/2009
MAMPONG_GT_1
EJURA_RS_GT_2
123
169
27.65
59.52
25/04/2009
MAMPONG_GT_1
EJURA_RS_GT_2
135
205
35.10
91.84
26/04/2009
MAMPONG_GT_1
EJURA_RS_GT_2
139
178
22.78
72.41
27/04/2009
MAMPONG_GT_1
EJURA_RS_GT_2
94
151
38.96
96.15
28/04/2009
MAMPONG_GT_1
EJURA_RS_GT_2
107
167
36.31
92.59
29/04/2009
MAMPONG_GT_1
EJURA_RS_GT_2
97
139
31.69
92.86
23/04/2009
YEJI_GT_1
PRANG_GT_1
26
26
0.00
25/04/2009
YEJI_GT_1
PRANG_GT_1
18
18
0.00
2009-09-29
Page24, Total93

29/04/2009
YEJI_GT_1
PRANG_GT_1
26
26
0.00
25/04/2009
YEJI_GT_3
PRANG_GT_1
103
104
0.96
72.73
28/04/2009
YEJI_GT_3
PRANG_GT_1
33
34
2.94
85.71
29/04/2009
YEJI_GT_3
PRANG_GT_1
61
62
1.61
90.91
Table2.21
The top bad cells for handover success rate
From the above table, we can see that the handover fails but the MS successfully returns
to the old channel during the intra-BSC and inter-BSC outgoing cell handover. So it will
not cause call drops.
1POKUKROM_GT
From the following table, we can see that there were many failed outgoing external
inter-cell handovers caused by T7 Expired.
Start Time
Period
(hour)
BSC Name
Cell Name
Failed Outgoing External

Inter-Cell Handovers (T7
Expired) (TCHF) (Traffic
Channel)
23/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_1
13
23/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_3
91
24/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_1
11
24/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_3
64
25/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_1
17
25/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_3
81
26/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_1
18
26/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_3
60
27/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_1
14
27/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_3
66
28/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_3
64
29/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_1
21
29/04/2009
24
AS_KUM_BSC01
POKUKROM_GT_3
71
Table2.22
The reason of failed handovers for POKUKROM_GT
From the procedure of Inter-BSC handover shown in below figure, we can see that it
means BSC1 did not receive Handover Command message from MSC in the course of
T7.
2009-09-29
Page25, Total93
Figure 16.1 The procedure of Inter-BSC handover

Further analyzing, we found out a lot of failed handovers were caused by Handover
Request Rejected, just as below table.
Failed Outgoing
Failed Outgoing
External
External Inter-Cell
Inter-Cell
Handovers
Handovers
(Handover Request
(Handover
Rejected)
Request
(Equipment Failure)
Rejected)
Date
Period
(hour)
23/04/2009
24
AS_KUM_BSC01 POKUKROM_GT_1
138
128
23/04/2009
24
354
306
24/04/2009
24
210
210
25/04/2009
24
147
147
25/04/2009
24
279
279
26/04/2009
24
126
126
26/04/2009
24
168
168
27/04/2009
24
208
208
28/04/2009
24
236
236
29/04/2009
24
230
230
BSC Name
Table2.23
Cell Name
Handover Request Rejected
So after the BSC sent the Handover Required message, MSC sent Handover Required
Reject message instead of Handover Command message, so the T7 timer expired
because of not receiving the Handover Command message.
So the data and configurations on MSC should be checked.
2009-09-29
Page26, Total93

2ABOABO A/R_2
From the following table, we can see that the handover failures mainly happened on the
Radio Interface which contains many reasons, shown below:
Failed Outgoing
Abnormal
Abnormal
Protocol
External Inter-Cell Abnormal
Other
Release,
Release, No
Release,
Error
Handovers
Timer
Activity on the
Causes
Unspecified
(Reconnection to Unspecified
Expired
Radio Path
Old Channels)
Date
23/04/2009
117
17
34
17
18
31
24/04/2009
143
41
46
14
22
18
25/04/2009
159
30
49
26
35
18
26/04/2009
156
26
49
30
37
14
27/04/2009
157
32
46
32
25
21
28/04/2009
140
22
31
24
39
23
29/04/2009
144
27
46
21
26
23
Table2.24
The reasons of failed Inter-BSC handovers for ABOABO A/R_2
Date
Failed Outgoing
Internal Inter-Cell
Handovers
(Reconnection to
Old Channels)
Abnormal
Release,
Unspecified
23/04/2009
71
30
21
24/04/2009
86
35
18
25
25/04/2009
85
41
21
16
26/04/2009
53
17
21
27/04/2009
78
31
11
18
14
28/04/2009
74
32
18
14
29/04/2009
97
48
12
19
14
Table2.25
Abnormal
Abnormal
Release, No Protocol
Other
Release,
Error
Activity on
Causes
Timer
the Radio Unspecified
Expired
Path
The reasons of failed Intra-BSC handovers for ABOABO A/R_2
In the outgoing external inter-cell handover procedure, the BSC sends a HO CMD
message to the MS through the originating cell and initiates timer T8 to wait for an HO
CMP message. If the MS reconnects to the old channel and sends an HO FAIL message
on the old channel before T8 expires, the specific one of the following counters is
measured in the target cell based on the cause value.
The counter Abnormal Release, Timer Expired is measured when the cause
value carried in the HO FAIL message is Abnormal Release, Timer Expired.
The counter Abnormal Release, No Activity on the Radio Path is measured when
the cause value carried in the HO FAIL message is Abnormal Release, No
Activity on the Radio Path.
2009-09-29
Page27, Total93
The counter Protocol Error Unspecified is measured when the cause value
carried in the HO FAIL message is Protocol Error Unspecified.
So the checks on radio interface are needed.

(3) MAMPONG_GT_1
Radio Interface which contains many reasons, shown below:
Date
Failed Outgoing
Abnormal
Abnormal
Abnormal
Protocol
Internal Inter-Cell
Release, No
Other
Release,
Release,
Error
Handovers
Activity on
Causes
Timer
(Reconnection to Old Unspecified
the Radio Unspecified
Expired
Channels)
Path
23/04/2009
305
69
149
17
66
24/04/2009
259
35
149
21
49
25/04/2009
460
55
317
40
42
26/04/2009
323
41
203
27
43
27/04/2009
278
54
152
23
45
28/04/2009
295
54
157
27
43
14
29/04/2009
263
54
152
17
28
11
Table2.26
The reasons of failed Intra-BSC handovers for MAMPONG_GT_1
The reasons are the same to ABOABO A/R_2.

(4) YEJI_GT_1 and YEJI_GT_3
Radio Interface which contains many reasons shown below:
Date
Abnormal
Failed Outgoing
Release,
Internal
Abnormal
Abnormal
Protocol
No
Other
Inter-Cell
Release,
Cell Name
Release,
Activity
Error
Handovers
Causes
Timer
Unspecified
on the Unspecified
Reconnection
Expired
Radio
to Old Channels
Path
23/04/2009 YEJI_GT_3
531
60
440
21
23/04/2009 YEJI_GT_1
616
157
401
13
34
24/04/2009 YEJI_GT_3
114
18
76
18
24/04/2009 YEJI_GT_1
530
95
381
39
25/04/2009 YEJI_GT_3
264
22
221
11
25/04/2009 YEJI_GT_1
492
97
337
10
34
11
26/04/2009 YEJI_GT_3
250
15
187
40
26/04/2009 YEJI_GT_1
636
104
438
67
27/04/2009 YEJI_GT_3
236
14
164
22
34
27/04/2009 YEJI_GT_1
579
170
318
11
60
18
2009-09-29
Page28, Total93

28/04/2009 YEJI_GT_3
244
25
187
25
28/04/2009 YEJI_GT_1
581
132
392
11
22
29/04/2009 YEJI_GT_3
262
39
187
22
13
29/04/2009 YEJI_GT_1
425
89
284
11
24
14
Table2.27
Date
The reasons of failed Inter-BSC handovers for YEJI_GT

Failed Outgoing
Abnormal
External
Abnormal Abnormal
Protocol
Other
Release,
Inter-Cell
Release, Release,
Error
Cause
No Activity
Handovers
Unspecifi Timer
Unspecifie
s
on the
Reconnection to
ed
Expired
d
Radio Path
Old Channels
Cell Name
23/04/2009 YEJI_GT_1
23/04/2009 YEJI_GT_3
24/04/2009 YEJI_GT_1
24/04/2009 YEJI_GT_3
25/04/2009 YEJI_GT_1
25/04/2009 YEJI_GT_3
26/04/2009 YEJI_GT_1
26/04/2009 YEJI_GT_3
27/04/2009 YEJI_GT_1
27/04/2009 YEJI_GT_3
28/04/2009 YEJI_GT_1
28/04/2009 YEJI_GT_3
29/04/2009 YEJI_GT_1
29/04/2009 YEJI_GT_3
Table2.28
35
6
18
3
12
2
24
1
90
24
55
5
32
8
1
1
1
0
1
0
1
0
8
0
7
0
1
1
30
5
12
3
2
1
11
1
57
24
43
5
24
7
0
0
3
0
7
0
4
0
17
0
0
0
6
0
3
0
1
0
0
0
8
0
4
0
1
0
1
0
1
0
1
0
2
1
0
0
4
0
4
0
0
0
The reasons of failed Intra-BSC handovers for YEJI_GT
The reasons are the same to ABOABO A/R_2.
2.2.4 TCH congestion

The following table is the top bad cells for TCH congestion.
Failed
Failed
TCH
TCH
Seizures
Seizures
in TCH
TCH
due to
TCH
TCH
Handovers Congestion
Busy
Availability Traffic
due to
Rate
TCH
Busy TCH
(Traffic
(Traffic
Channel)
Channel)
Date
Period
(Min.)
Cell Name
23/04/2009
24
OBUASI BOETE MARKET_2
146
23/04/2009
24
23/04/2009
24
Table2.29
15.32
64.95
20.14
158
11.93
64.55
29.50
296
18
17.80
64.27
30.50
TCH congestion top bad cells
From Table 2.29 above, we can see that all the three cells of OBUASI BOETE MARKET
2009-09-29
Page29, Total93

have a high TCH congestion. So the problem is with the whole site.
We can easily see that a lot of failed TCH seizures due to busy TCH for call and handover,
so this affected the KPI a lot especially for the call setup success rate and handover
success rate.
Further analysis showed the TCH availability was very low, nearly 60 percent. So the
transmission might have broken this day.
The below data is the history alarms for OBUASI BOETE MARKET on the 23rd of April.
There were so many LAPD Fault and Cell Out of Service alarms on this day, so it was the
LAPD flash down that contributed to the high TCH congestion rate.
Alarm name
Alarm raised time
Cleared time
Alarm source
LAPD OML Fault
2009-4-23 15:04
2009-4-23 16:34
OBUASI BOETE MARKET
Cell Out of Service
2009-4-23 15:04
2009-4-23 16:52
OBUASI BOETE MARKET
LAPD OML Fault
2009-4-23 16:40
2009-4-23 16:41
OBUASI BOETE MARKET
LAPD OML Fault
2009-4-23 16:46
2009-4-23 16:52
OBUASI BOETE MARKET
Cell Out of Service
2009-4-23 17:05
2009-4-23 17:27
OBUASI BOETE MARKET
LAPD OML Fault
2009-4-23 17:05
2009-4-23 17:09
OBUASI BOETE MARKET
LAPD OML Fault
2009-4-23 17:15
2009-4-23 17:16
OBUASI BOETE MARKET
Cell Out of Service
2009-4-23 18:10
2009-4-23 18:11
OBUASI BOETE MARKET
LAPD Alarm
2009-4-23 18:11
2009-4-23 18:13
OBUASI BOETE MARKET
Cell Out of Service
2009-4-23 18:11
2009-4-23 18:16
OBUASI BOETE MARKET
LAPD Alarm
2009-4-23 18:32
2009-4-23 18:33
OBUASI BOETE MARKET
Cell Out of Service
2009-4-23 18:58
2009-4-23 18:58
OBUASI BOETE MARKET
Cell Out of Service
2009-4-23 19:10
2009-4-23 19:26
OBUASI BOETE MARKET
LAPD OML Fault
2009-4-23 19:10
2009-4-23 19:11
OBUASI BOETE MARKET
LAPD Alarm
2009-4-23 19:13
2009-4-23 19:13
OBUASI BOETE MARKET
LAPD OML Fault
2009-4-23 19:17
2009-4-23 19:18
OBUASI BOETE MARKET
Table2.30
2009-09-29
The history alarms for OBUASI BOETE MARKET on the 23rd of April
Page30, Total93
3 Analysis of Drive Test

3.1 Network Summary
The coverage area of KUMASI city is composed of 42 operational sites. City in general
relatively has a flat terrain, the network elements are 2BSC/42BTS/537TRX. The following
figure shows the site distribution in KUMASI city.
Figure 3.1 Site Distribution in KUMASI City

Drive Test route is shown below:
2009-09-29
Page31, Total93
Figure 3.2 Before/After Swap Planning Test Route in KUMASI City

In order to know more about the coverage of the radio network in KUMASI city before/after
swap, Huawei performed a drive test. We found that after the swap, the radio network
improved in many areas.
2009-09-29
Page32, Total93
3.2 Analysis of BCCHLevel

The result of the Drive Test::
Count
Legend
Percentage
Before swap
After swap
Before swap
After swap
-64dBm ~ -10dBm
25925
35560
15.54
20.12
-68dBm ~ -64dBm
13659
17990
8.19
10.18
-73dBm ~ -68dBm
17602
23215
10.55
13.14
-78dBm ~ -73dBm
33800
41664
20.26
23.58
-85dBm ~ -78dBm
36538
37017
21.90
20.95
-100dBm ~ -85dBm
39346
21267
23.58
12.03
Total
166870
176713
100.00
100.00
Table 3.26
BCCH Level Statistics
Remark: From the BCCH Level Statistics, BCCH Level improved after the Swap.
45000
40000
35000
Count
30000
25000
20000
15000
10000
5000
0
-64dBm ~ -68dBm ~ -73dBm ~ -78dBm ~ -85dBm ~ -100dBm

-10dBm -64dBm -68dBm -73dBm -78dBm ~ -85dBm
Count(Bef ore Sw ap)
25925
13659
17602
33800
36538
39346
Count(After Sw ap)
35560
17990
23215
41664
37017
21267
Percentage(Bef ore Sw ap)
15.54
8.19
10.55
20.26
21.9
23.58
Percentage(Af ter Sw ap)
20.12
10.18
13.14
23.58
20.95
12.03
100
90
80
70
60
50
40
30
20
10
0
Percent
BCCHLevel
Band
Figure 3.3 BCCH Level Statistics

The following figures show BCCHLevel distribution before/after Swap in KUMASI city.
2009-09-29
Page33, Total93
Figure 3.4 Before Swap BCCHLevel Distribution in KUMASI City(Whole)
Figure 3.5 After Swap BCCHLevel Distribution in KUMASI City (Whole)

2009-09-29
Page34, Total93
Figure 3.6 Before Swap BCCHLevel Distribution in KUMASI City Centre
Figure 3.7 After Swap BCCHLevel Distribution in KUMASI City Centre

2009-09-29
Page35, Total93
3.3 Analysis of Rx_Level (Sub)

The result of the Drive Test:
Count
Legend
Percentage
Before swap
After swap
Before swap
After swap
-64dBm ~ -10dBm
24971
30706
15.48
18.89
-68dBm ~ -64dBm
13217
15999
8.20
9.84
-73dBm ~ -68dBm
17039
21013
10.57
12.93
-78dBm ~ -73dBm
32698
39009
20.27
24.00
-85dBm ~ -78dBm
35309
35429
21.89
21.80
-100dBm ~ -85dBm
38039
20375
23.59
12.54
Total
161273
162531
100.00
100.00
Table 3.27
Rx_Level(Sub) Statistics
Remark: The Rx_Level improved after the Swap. The counts for the higher signal level
increased while the counts reduced for the bad signal levels i.e -100dBm ~ -85dBm. The
increase in the counts of the signal also shows an increase in the total coverage area.
45000
40000
35000
Count
30000
25000
20000
15000
10000
5000
0
-64dBm ~ -68dBm ~ -73dBm ~ -78dBm ~ -85dBm ~ -100dBm

-10dBm -64dBm -68dBm -73dBm -78dBm ~ -85dBm
Count(Before Sw ap)
24971
13217
17039
32698
35309
38039
Count(After Sw ap)
30706
15999
21013
39009
35429
20375
Percentage(Before Sw ap)
15.48
8.2
10.57
20.27
21.89
23.59
Percentage(After Sw ap)
18.89
9.84
12.93
24
21.8
12.54
100
90
80
70
60
50
40
30
20
10
0
Percent
RxLevel
Band
Figure 3.8 Rx_Level(Sub) Statistics

The following figures show Rx_Level(Sub) distribution of before/after swap in KUMASI.
2009-09-29
Page36, Total93
Figure 3.9 Before swap Rx_Level(Sub) Distribution in KUMASI City (Whole)
Figure 3.10 After swap Rx_Level(Sub) Distribution in KUMASI City (Whole)

2009-09-29
Page37, Total93
Figure 3.11 Before Swap Rx Level(Sub) Distribution in KUMASI City Centre
Figure 3.12 After Swap Rx Level(Sub) Distribution in KUMASI City Centre

2009-09-29
Page38, Total93
3.4 Analysis of Rx_Quality (Sub)

The result of the drive test:
Count
Legend
Percentage
Before swap
After swap
Before swap
After swap
0~4
155186
154987
95.65
95.20
4~5
2327
3993
2.02
2.45
5~7
3793
3835
2.33
2.35
Total
161306
162815
100.00
100.00
Table 3.28
Rx_Quality(Sub) Statistics
Remark: It has slightly deteriorated for Rx_Qual after swap. As some cells lack adjacent
cells, and inter-BSC handover problems between BSC01 and BSC02 do not lead to
handover in time, in this case, the weak signal can not handover to the ideal target cell,
resulting in poor voice quality. On voice quality, we carrying out further optimization to
solve this issue. See the specific issue of voice quality analysis.
180000
100
160000
90
140000
80
120000
70
60
100000
50
80000
40
60000
30
40000
20
20000
10
Percent
Count
RxQual
0~4
4~5
5~7
Count(Before Sw ap)
155186
2327
3793
Count(After Sw ap)
154987
3993
3835
Percentage(Before Sw ap)
95.65
2.02
2.33
Percentage(After Sw ap)
95.20
2.45
2.35
Band
Figure 3.13 Rx_Quality(Sub) Statistics

The following figures show Rx_Qual(Sub) distribution before/after swap in KUMASI.
2009-09-29
Page39, Total93
Figure 3.14 Before Swap Rx_Quality(Sub) Distribution in KUMASI City (Whole)
Figure 3.15 After Swap Rx_Quality(Sub) Distribution in KUMASI City (Whole)

2009-09-29
Page40, Total93
Figure 3.16 Before Swap Rx_Quality(Sub) Distribution in KUMASI City Centre
Figure 3.17 After Swap Rx_Quality(Sub) Distribution in KUMASI City Centre

2009-09-29
Page41, Total93
3.5 Issue Analysis

3.5.1 Voice Quality Issue Analysis
1. Voice quality issue analysis of DCS_MAGAZINE_OT1996
During the drive test, we realized the voice quality signal near (DCS_MAGAZINE_OT)
was worse than before swap. This is because the mobile phone camped on the signal of
DCS_ADOATO1051
and
stayed
in
it
and
never
handed-over
to
DCS_MAGAZINE_OT1996, the signal was weak and the voice quality was bad.
The following list shows site DCS_MAGAZINE_OT1996 adjacent cell adjustment:
Source
Cell ID
Source Cell
Target
Source BSC
Name
Cell ID
DCS_MAGAZINE
21996
Kumasi_New_BSC_1 11051
_OT_2
DCS_MAGAZINE
31996
Kumasi_New_BSC_1 11051
_OT_3
Table 3.29
Target Cell
Name
Target
Adjustment
BSC-HW
Type
Kumasi_New
ADOATO_1
Add
_BSC_1
Kumasi_New
ADOATO_1
Add
_BSC_1
DCS_MAGAZINE_OT1996 adjacent cell adjustment
The following figure show Rx_Quality (sub) distribution before/after optimization near site
DCS_MAGAZINE_OT1996 (black circled area improved).
Figure 3.18
Before/After Optimization Rx_Quality(Sub) Distribution near site MAGAZINE_OT1996
2. Voice Quality Issue Analysis of DESPITE1083

During the drive test, we realized the voice quality signal near (DESPITE1083) was worse
than before swap. This was because of the crossing of feeder/antenna system of the
sectors i.e. a cell has changed the direction of the normal coverage, resulting in confusion
in the adjacent cell causing some handover delay and weak coverage of the area. This
2009-09-29
Page42, Total93

resulted in a bad voice quality. After adjustment of the feeder system in accordance with
the direction of the normal coverage, we drive tested again, and the voice quality
improved.
The following figure shows Rx_Quality (sub) distribution before/after optimization near site
DESPITE1083 (black circled area was improved).
Figure 3.19
Before/After Optimization Rx_Quality(Sub) Distribution near site DESPITE1083
3. Voice Quality Issue Analysis of ASUOGYA1049

During the drive test, we realized the voice quality signal near (ASUOGYA1049) was
worse than before swap. This was because of the crossing of feeder/antenna system of
the sectors i.e. a cell has changed the direction of the normal coverage, resulting in
confusion in the adjacent cell causing some handover delay and weak coverage of the
area. This resulted in a bad voice quality. After adjustment of the feeder system in
accordance with the direction of the normal coverage, we drive tested again, and the
voice quality improved.
The following figure show Rx_Quality (sub) distribution before/after optimization near site
ASUOGYA1049 (black circled area was improved).
2009-09-29
Page43, Total93
Figure 3.20
Before/After Optimization Rx_Quality(Sub) Distribution near site ASUOGYA1049
4. Voice Quality Issue Analysis between BSC01 and BSC02

As a result of inter-BSC handover problems between BSC01 and BSC02, resulting in poor
voice quality of some of the roads, after determining the problem and adjusting the
resources and parameters effectively, we performed a drive test and realized that voice
quality has improved.
Below is Rx_Qual performance for inter-BSC sites before/after adjustment in KUMASI
(black circled area was improved).
Figure 3.21
Inter-BSC Sites Before/After Adjustment Rx_Quality(Sub) Distribution in KUMASI
Remark: After the end of the optimization of the voice quality, we drive tested the main
road of Kumasi and found out that the overall voice quality has improved.
The following figure show Rx_Quality (sub) distribution after optimization in KUMASI city.
2009-09-29
Page44, Total93
Figure 3.22 Rx_Quality (sub) distribution after optimization in KUMASI city

RxQual(sub)
Count
Percentage
Distance(km)
Percentage
0~4
56027
95.97
201.09
95.66
4~5
1336
2.29
5.200
2.47
5~7
1008
1.72
3.93
1.87
Table 3.30
2009-09-29
After Optimization Rx_Quality(Sub) Statistics in KUMASI.
Page45, Total93
RxQual
60000
100.00
55000
90.00
50000
80.00
45000
Count
35000
60.00
30000
50.00
25000
40.00
20000
Percent
70.00
40000
30.00
15000
20.00
10000
10.00
5000
0
0.00
0~4
4~5
5~7
Count
56027
1336
1008
Percentage
95.97
2.29
1.72
Band
Figure 3.23 After Optimization Rx_Quality(Sub) Statistics in KUMASI
3.5.2 Crossing of feeder/antenna system Issue Analysis

1. Crossing of feeder/antenna system issue analysis of ASUOGYA1049
After the swap drive test of ASUOGYA1049 site, it was realized that the feeder/antenna
system had been crossed, the necessary adjustments were made and a subsequent drive
test was done to confirm problem resolution.
The following figure shows the BCCH coverage distribution before/after adjusted
feeder/antenna of ASUOGYA1049 site.
Figure 3.24
Before/After Adjusted feeder/antenna of ASUOGYA1049 Site BCCH Coverage

Distribution
2009-09-29
Page46, Total93

2. Crossing Feeder/Antenna Issue Analysis of DESPITE1083
After the swap drive test of DESPITE1083 site, it was realized that the feeder/antenna
The following figure below shows the BCCH coverage distribution before/after adjusted
feeder/antenna of DESPITE1083 site.
Figure 3.25
Before/After Adjustment of feeder/antenna of DESPITE1083 Site BCCH Coverage

Distribution
3. Crossing Feeder/Antenna Issue Analysis of NHYIAESO1075

After the swap drive test of NHYIAESO1075 site, it was realized that the feeder/antenna
The following figure shows the BCCH coverage distribution before/after adjustment of
feeder/antenna of NHYIAESO1075 site.
2009-09-29
Page47, Total93
Figure 3.26
Before/After Adjustment of feeder/antenna of NHYIAESO1075 Site BCCH Coverage

Distribution
The table below shows the crossing feeder/antenna sites in KUMASI.

No.
Site Name
KUMASI_ACADEMY1017
KUMASI_POLY1034
DCS_POLLUX_HOTEL1977
Table 3.31
Remark
Before swap crossing feeder/antenna
The crossing feeder/antenna sites in KUMASI
Huawei have made all the necessary adjustments now.
3.5.3 Handover Failure Issue Analysis

1. Handover Failure analysis of ASUOGYA1049
The terrain surrounding ASUOGYA1049 site is very hilly thereby resulting in poor
coverage of the surrounding region, and also because of the crossing of its
feeder/antenna. Cells within this site changed the direction of their normally planned
coverage, causing confusion in the adjacent cell relationships which resulted in handover
delays and failures.
The following figure
ASUOGYA1049 site.
2009-09-29
shows the
handover
failure
before/after
optimization of
Page48, Total93
Figure 3.27 After Optimization of Handover Failure of ASUOGYA1049
3.6 Event Analysis

Mobility and retain ability are very important performance indicators of GSM network. We
can use handover success rate to describe mobility performance and use call drop rate to
describe retain ability. If handover success rate is high, it means that mobility of network is
good, otherwise it is bad. If there are few call drops, it means that retain ability of network
is good, otherwise it is bad.
Item
Number
calls
Call Setup
Success Rate
Handover
failure
Handover
Success Rate
Number of
drop calls
Call Drop
Rate (%)
Before swap
723
86.17
22
98.60
19
3.05
After swap
793
97.10
19
99.09
17
2.21
Table 3.32
Call Event and Performance Statistics
From the above table, we can see that 19 handover failures occurred after swap which is
better than before swap. Meanwhile, there are a total of 17 call drops after swap, also less
than before swap. The retain ability and mobility of the network is better after the swap.
The following figure shows the call event and performance statistics before/after swap.
2009-09-29
Page49, Total93
Percent
Event Statistics
98.60
97.10
100.00
90.00
80.00
70.00
60.00
50.00
40.00
30.00
20.00
10.00
0.00
99.09
86.17
3.05
2.21
Call Setup Success

Rate(%)
Call Drop Rate (%)
Handover Success Rate

(%)
Before Swap
86.17
3.05
98.60
After Swap
97.10
2.21
99.09
Band
Figure 3.28 Call Event and Performance Statistics
3.7 Analysis of Data Service

In order to know more about data service performance in KUMASI before/after swap,
Huawei made a data service CQT. We found out that after the swap, data service
download speed improved than before swap.
The result of the drive test:
Cell
Cell ID
AHWIA1079_1
11709
ANWOMASO1088_3
ANYINAM_AS1035_3
ASH_TOWN1029_2
ATIMATIM1099_1
BANTAMA1030_1
2009-09-29
31088
31035
21029
21101
11030
Test Time
Test
Type
Download
Speed(K/s)
Before swap
GPRS
After swap
GPRS
4.5
Before swap
EDGE
After swap
EDGE
20
After swap
GPRS
Before swap
EDGE
After swap
EDGE
19
After swap
GPRS
Before swap
EDGE
3.5
After swap
EDGE
20
After swap
GPRS
Before swap
GPRS
After swap
GPRS
Before swap
EDGE
2.5
Page50, Total93
BUOKROM_GT1005_2
FUMESUA1050_3
KUMASI_GBC_TD1008_2
KWADASO_NSUOM1077_1
MAGAZINE_OT1009_2
NEW_AHENEMA_KOKOBEN1074_1
NHYIAESO1075_1
PATASI_GT1002_2
SANTAS1073_3
SOFOLINE_SUNTRESO_SOUTH1022_2
SOKOBAN1048_2
UST_GT1004_3
Table 3.33
2009-09-29
21005
31050
21008
11077
21009
11074
11705
21002
11073
21022
21048
31004
After swap
EDGE
18.5
After swap
GPRS
Before swap
GPRS
After swap
GPRS
8.5
Before swap
EDGE
3.5
After swap
EDGE
20
After swap
GPRS
Before swap
EDGE
After swap
EDGE
20
After swap
GPRS
Before swap
EDGE
3.5
After swap
EDGE
21
After swap
GPRS
Before swap
EDGE
After swap
EDGE
20
After swap
GPRS
Before swap
EDGE
3.5
After swap
EDGE
17
After swap
GPRS
Before swap
EDGE
After swap
EDGE
19
After swap
GPRS
Before swap
EDGE
2.5
After swap
EDGE
10
After swap
GPRS
6.5
Before swap
EDGE
3.5
After swap
EDGE
21
After swap
GPRS
Before swap
EDGE
After swap
EDGE
18
After swap
GPRS
Before swap
EDGE
After swap
EDGE
21
After swap
GPRS
7.5
Before swap
EDGE
After swap
EDGE
19
After swap
GPRS
Data Service Performance Statistics Before/After Swap
Page51, Total93
GPRS/EDGE Dow nload Speed Statistics
23
22
21
20
19
18
17
16
15
14
13
12
11
10
9
8
7
6
5
4
3
2
1
0
21
20
20
20
19
20
21
21
20
19
19
18.5
18
17
10
9
9
7
8.5
4.5
3.5
2
3.5
2.5
3.5
3.5
7
4
3.5
2.5
7.5
6.5
7 7
3
2
11709 31088 31035 21029 21101 11030 21005 31050 21008 11077 21009 11074 11705 21002 11073 21022 21048 31004
GPRS/EDGE Dow nload Speed(K/s)(Before Sw ap)
EDGE Dow nload Speed(K/s)(Af ter Sw ap)

GPRS Dow nload Speed(K/s)(After Sw ap)
4.5
3.5
20
19
20
2.5
18.5
9
8.5
3.5
3.5
3.5
2.5
3.5
20
20
21
20
17
19
10
21
18
21
19
6.5
7.5
Figure 3.29 Data Service Performance Statistics Before/After Swap
3.7.1 GPRS performance of BUOKROM_GT1005_2

A GPRS test was implemented at BUOKROM_GT1005_2 before & after swap, the GPRS
performance is shown as follows:
Figure 3.30 Before Swap GPRS performance of BUOKROM_GT1005_2
Figure 3.31 After Swap GPRS performance of BUOKROM_GT1005_2

2009-09-29
Page52, Total93

From the above figures, we can see that there are more than 2KB/s(16Kbit/s) for GPRS
download speed in BUOKROM_GT1005_2 before swap, and there are more than 8.5KB/s
(70Kbit/s) for GPRS download speed in BUOKROM_GT1005_2 after swap. Also we can
see that the degree of fluctuations is less for the download speed after swap than before
swap.
The data service functionality validation results are as follows:
Cell
Longitude Latitude
BUOKROM_GT1005_2
-1.5889
Table 3.34
Test Time
Test
Type
Before swap
GPRS
16/03/2009 12:23
6.7457
After swap
GPRS
21/03/2009 19:46
BCCH
Level
Cell ID
C/I
-71
21005
18.00
-72
21005
19.71
Data service functionality validation results
3.7.2 GPRS performance of AHWIA1079_1

A GPRS test was implemented at AHWIA1079_1 before & after swap, the GPRS
performance is shown as follows:
Figure 3.32 Before Swap GPRS performance of AHWIA1079_1
Figure 3.33 After Swap GPRS performance of AHWIA1079_1

From the above figures, we can see that there are more than 2KB/s (16Kbit/s) for GPRS
download speed in AHWIA1079_1 before swap, and there are more than 4.5KB/s
2009-09-29
Page53, Total93

(36Kbit/s) for GPRS download speed in AHWIA1079_1 after swap. Also we can see that
the degree of fluctuations is less for the download speed after swap than before swap.
Cell
Longitude Latitude
AHWIA1079_1
-1.5961
Table 3.35
Test Time
Test
Type
Before swap
GPRS
10/03/2009 11:16
6.7574
After swap
GPRS
21/03/2009 18:38
BCCH
Level
Cell ID
C/I
-64
11709
17.74
-47
11709
20.45
Data service functionality validation results
3.7.3 GPRS performance of ATIMATIM1099_1

A GPRS test was implemented at ATIMATIM1099_1 before & after swap, the GPRS
performance is shown below:
Figure 3.34 Before Swap GPRS performance of ATIMATIM1099_1
Figure 3.35 After Swap GPRS performance of ATIMATIM1099_1

From the above figures, we can see that there is more than 2KB/s (16Kbit/s) for GPRS
download speed in ATIMATIM1099_1 before swap, and there is more than 9KB/s
(72Kbit/s) for GPRS download speed in ATIMATIM1099_1 after swap. Also we can see
that the degree of fluctuations is less for the download speed after swap than before
swap.
2009-09-29
Page54, Total93

Cell
ATIMATIM1099_1
Table 3.36
Longitude Latitude
Test Time
-1.6197 6.7574
Before swap
16/03/2009
11:30
After swap
21/03/2009
18:02
Test
Type
BCCH
Level
GPRS
-62
21101 17.40
GPRS
-59
21101 23.68
Cell ID
C/I
Data service functionality validation results for Atimatim1099_1
3.7.4 GPRS/EDGE performance of MAGAZINE_OT1009_2

A GPRS/EDGE test was implemented by MAGAZINE_OT1009_2 before/after swap, the
GPRS/EDGE performance was shown as following:
Figure 3.36 Before Swap EDGE performance of MAGAZINE_OT1009_2
Figure 3.37 After Swap EDGE performance of MAGAZINE_OT1009_2
2009-09-29
Page55, Total93
Figure 3.38 After Swap GPRS performance of MAGAZINE_OT1009_2

From the above figure, we can see that there is more than 2Kb/s (16Kbit/s) for EDGE
download speed in MAGAZINE_OT1009_2 before swap, and there is more than 20Kb/s
(160Kbit/s) for EDGE download speed in MAGAZINE_OT1009_2 after swap, and there is
more than 7Kb/s (56Kbit/s) for GPRS download speed in MAGAZINE_OT1009_2. Also
we can see that the degree of fluctuations is less for the download speed after swap than
before swap.
Cell
Longitude Latitude
Test Time
Test
Type
Before swap
16/03/2009 EDGE
13:16
MAGAZINE_OT1009_2 -1.62708 6.71346
After swap
22/03/2009 EDGE
14:57
Table 3.37
BCCH
Level
Cell ID
C/I
-61
21009 13.74
-54
21101 21.74
Data service functionality validation results for Magazine_OT1009_2
3.7.5 GPRS/EDGE performance of AHWIA1079_1

A GPRS/EDGE test was implemented at ASH_TOWN1029_2 before/after swap, the
GPRS/EDGE performance is shown below:
Figure 3.39 Before Swap EDGE performance of ASH_TOWN1029_2
2009-09-29
Page56, Total93
Figure 3.40 After Swap EDGE performance of ASH_TOWN1029_2
Figure 3.41 After Swap GPRS performance of ASH_TOWN1029_2

From the above figure, we can see that there is more than 3.5Kb/s (28Kbit/s) for EDGE
download speed in ASH_TOWN1029_2 before swap, and there is more than 20Kb/s
(160Kbit/s) for EDGE download speed in ASH_TOWN1029_2 after swap, and there is
more than 7Kb/s (56Kbit/s) for GPRS download speed in ASH_TOWN1029_2 after swap.
Also we can see that the degree of fluctuations is less for the download speed after swap
than before swap.
The data service functionality validation results are as below:
Cell
Longitude Latitude
ASH_TOWN1029_2
Table 3.38
Test Time
Test
Type
Before swap
16/03/2009 EDGE
13:03
-1.62160 6.70657
After swap
25/03/2009 EDGE
15:13
BCCH
Level
Cell ID
C/I
-84
21029 14.84
-61
21101 22.82
Data service functionality validation results for Ash_Town1029_2
3.7.6 GPRS/EDGE performance of BANTAMA1030_1

A GPRS/EDGE test was implemented at BANTAMA1030_1 before/after swap, the GPRS
performance was shown as follows:
2009-09-29
Page57, Total93
Figure 3.42 Before Swap EDGE performance of BANTAMA1030_1
Figure 3.43 After Swap EDGE performance of BANTAMA1030_1
Figure 3.44 After Swap GPRS performance of BANTAMA1030_1

From the above figure, we can see that there is more than 2.5KB/s (28Kbit/s) for EDGE
download speed in BANTAMA1030_1 before swap, and there is more than 18.5Kb/s
(148Kbits/s) for EDGE download speed in BANTAMA1030_1 after swap, and there is
more than 7Kb/s (56Kbits/s) for GPRS download speed in BANTAMA1030_1. Also we
can see that the degree of fluctuations is less for the download speed after swap than
before swap.
The data service functionality validation results are shown below:
2009-09-29
Page58, Total93
Cell
Longitude Latitude
BANTAMA1030_1
Table 3.39
Test Time
Test
Type
Before swap
16/03/2009 EDGE
13:37
-1.63131 6.70175
After swap
25/03/2009 EDGE
18:28
BCCH
Level
Cell ID
C/I
-68
11030 20.62
-55
21101 22.30
Data service functionality validation results for BANTAMA1030_1
3.7.7 GPRS/EDGE performance of PATASI_GT1002

A GPRS/EDGE test was implemented at PATASI_GT1002_2 before/after swap, the
Figure 3.45 Before Swap EDGE performance of PATASI_GT1002_2
Figure 3.46 After Swap EDGE performance of PATASI_GT1002_2
2009-09-29
Page59, Total93
Figure 3.47 After Swap GPRS performance of PATASI_GT1002_2

From the above figures, we can see that there is more than 2.5Kb/s (20Kbit/s) for EDGE
download speed in PATASI_GT1002_2 before swap, and there is more than 10Kb/s
(80Kbit/s) for EDGE download speed in PATASI_GT1002_2 after swap, and there is more
than 6.5Kb/s (48Kbit/s) for GPRS download speed in PATASI_GT1002_2. Also we can
see that the degree of fluctuations is less for the download speed after swap than before
swap.
The EDGE download speed is not high because of high traffic and the channel busy
status at the time we were testing, so nearly all the channels were used as Call Service.
Cell
Longitude Latitude
PATASI_GT1002_2
Table 3.40
Test Time
Test
Type
Before swap
16/03/2009 EDGE
15:32
-1.64237 6.67974
After swap
24/03/2009 EDGE
12:18
BCCH
Level
Cell ID
C/I
-59
21002 21.54
-52
21101 22.36
Data service functionality validation results for Patasi_GT1002_2
3.7.8 GPRS/EDGE performance of SOFOLINE_SUNTRESO_SOUTH1022

A GPRS/EDGE test was implemented at SOFOLINE_SUNTRESO_SOUTH1022_2
before/after swap, the PRS/EDGE performance is shown below:
2009-09-29
Page60, Total93
Figure 3.48 Before Swap EDGE performance of SOFOLINE_SUNTRESO_SOUTH1022
Figure 3.49 After Swap EDGE performance of SOFOLINE_SUNTRESO_SOUTH1022
Figure 3.50 After Swap GPRS performance of SOFOLINE_SUNTRESO_SOUTH1022

download speed in SOFOLINE_SUNTRESO_SOUTH1022_2 before swap, and there is
more
than
18Kb/s
(144Kbit/s)
for
EDGE
download
speed
in
SOFOLINE_SUNTRESO_SOUTH1022_2 after swap, and there is more than 7Kb/s
(56Kbit/s) for GPRS download speed in SOFOLINE_SUNTRESO_SOUTH1022_2 after
swap.
2009-09-29
Page61, Total93
Cell
Longitude Latitude
Test Time
Test
Type
Before swap
16/03/2009 EDGE
SOFOLINE_SUNTRE
15:47
-1.64630 6.69668
SO_SOUTH1022_2
After swap
24/03/2009 EDGE
10:34
Table 3.41
BCCH
Level
Cell ID
C/I
-58
21022 20.85
-63
21101 21.75
Data service functionality validation results for

Sofoline_Suntreso_South1022_2
3.7.9 GPRS/EDGE performance of KWADASO_NSUOM1077

A GPRS/EDGE test was implemented at KWADASO_NSUOM1077_1 before/after swap,
the GPRS performance is shown below:
Figure 3.51 Before Swap EDGE performance of KWADASO_NSUOM1077_1
Figure 3.52 After Swap EDGE performance ofKWADASO_NSUOM1077_1
2009-09-29
Page62, Total93
Figure 3.53 After Swap GPRS performance of KWADASO_NSUOM1077_1

download speed in KWADASO_NSUOM1077_1 before swap, and there is more than
21KB/s (168Kbit/s) for EDGE download speed in KWADASO_NSUOM1077_1 after swap,
and there is more than 9Kb/s (72Kbits/s) for GPRS download speed in
KWADASO_NSUOM1077_1. Also we can see that the degree of fluctuations is less for
the download speed after swap than before swap.
The data service functionality validation results shown below:
Cell
Longitude Latitude
Test Time
Test
Type
Before swap
16/03/2009 EDGE
16:12
KWADASO_NSUOM1077_1 -1.66029 6.69995
After swap
24/03/2009 EDGE
10:56
Table 3.42
BCCH
Cell ID
Level
C/I
-66
11077 19.37
-55
21101 22.59
Data service functionality validation results for KWADASO_NSUOM1077_1
3.7.10 GPRS/EDGE performance of ANYINAM_AS1035_3

A GPRS/EDGE test was implemented by ANYINAM_AS1035_3 before/after swap, the
Figure 3.54 Before Swap EDGE performance of ANYINAM_AS1035_3

2009-09-29
Page63, Total93
Figure 3.55 After Swap EDGE performance of ANYINAM_AS10375_3
Figure 3.56 After Swap GPRS performance of ANYINAM_AS1035_3

From the above figure, we can see that there is more than 2Kb/s (16Kbit/s) for EDGEs
download speed in ANYINAM_AS1035_3 before swap, and there is more than 19Kb/s
(152Kbit/s) for EDGEs download speed in ANYINAM_AS1035_3 after swap, and there is
more than 7Kb/s (56Kbit/s) for GPRSs download speed in ANYINAM_AS1035_3 after
swap. Also we can see that the degree of fluctuations is less for the download speed after
swap than before swap.
Cell
Longitude Latitude
ANYINAM_AS1035_3
Table 3.43
Test Time
Test
Type
Before swap
16/03/2009 EDGE
16:53
-1.64065 6.64612
After swap
01/04/2009 EDGE
15:59
BCCH
Cell ID
Level
C/I
-69
31035 22.41
-48
21101 22.75
Data service functionality validation results for ANYINAM_AS1035_3
3.7.11 GPRS/EDGE performance of SOKOBAN1048_2

A GPRS/EDGE test was implemented at SOKOBAN1048_2 before/after swap, the
2009-09-29
Page64, Total93
Figure 3.57 Before Swap EDGE performance of SOKOBAN1048_2
Figure 3.58 After Swap EDGE performance of SOKOBAN1048_2
Figure 3.59 After Swap GPRS performance of SOKOBAN1048_2

download speed in SOKOBAN1048_2 before swap, and there is more than 21Kb/s
(168Kbit/s) for EDGE download speed in SOKOBAN1048_2 after swap, and there is more
than 7.5Kb/s (60Kbit/s) for GPRS download speed in SOKOBAN1048_2 after swap. Also
before swap.
2009-09-29
Page65, Total93
Cell
Longitude Latitude
SOKOBAN1048_2
Table 3.44
Test Time
Test
Type
Before swap
16/03/2009 EDGE
17:20
-1.61869 6.63144
After swap
01/04/2009 EDGE
16:43
BCCH
Cell ID
Level
C/I
-75
21048 19.64
-58
21101 22.35
Data service functionality validation results for SOKOBAN1048_2
3.7.12 GPRS/EDGE performance of NEW_AHENEMA_KOKOBEN1074_1

A GPRS/EDGE test was implemented at NEW_AHENMA_KOKOBEN1074_1 before/after
swap, the GPRS performance is shown below:
Figure 3.60 Before Swap EDGE performance of NEW_AHENEMA_KOKOBEN1074_1
Figure 3.61 After Swap EDGE performance of NEW_AHENEMA_KOKOBEN1074_1
Figure 3.62 After Swap GPRS performance of NEW_AHENEMA_KOKOBEN1074_1

2009-09-29
Page66, Total93

download speed in NEW_AHENEMA_KOKOBEN1074_1 before swap, and there is more
than 17KB/s (136Kbit/s) for EDGE download speed in
NEW_AHENEMA_KOKOBEN1074_1 after swap, and there is more than 7Kb/s (56Kbits/s)
for GPRS download speed in NEW_AHENEMA_KOKOBEN1074_1. Also we can see that
the degree of fluctuations is less for the download speed after swap than before swap.
Cell
Longitude Latitude
NEW_AHENEMA_
KOKOBEN1074_1
Table 3.45
Test Time
Test
Type
Before swap
16/03/2009 EDGE
17:01
-1.65859 6.62932
After swap
01/04/2009 EDGE
16:21
BCCH
Cell ID
Level
C/I
-64
11074 22.50
-52
21101 23.50
Data service functionality validation results for NEW_AHENEMA_

KOKOBEN1074_1
3.7.13 GPRS/EDGE performance of UST_GT1004_3

A GPRS/EDGE test was implemented at UST_GT1004_3 before/after swap, the
Figure 3.63 Before Swap EDGE performance of UST_GT1004_3
Figure 3.64 After Swap EDGE performance of UST_GT1004_3
2009-09-29
Page67, Total93
Figure 3.65 After Swap GPRS performance of UST_GT1004_3

download speed in UST_GT1004_3 before swap, and there is more than 19Kb/s
(152Kbit/s) for EDGE download speed in UST_GT1004_3 after swap, and there is more
than 7Kb/s (56Kbit/s) for GPRS download speed in UST_GT1004_3 after swap.
Cell
Longitude Latitude
UST_GT1004_3
Table 3.46
Test Time
Test
Type
Before swap
16/03/2009 EDGE
18:34
-1.54569 6.68570
After swap
01/04/2009 EDGE
13:10
BCCH
Cell ID
Level
C/I
-56
31004 22.73
-51
21101 23.55
Data service functionality validation results for UST_GT1004_3
3.7.14 GPRS/EDGE performance of FUMESUA1050_3

A GPRS/EDGE test was implemented at FUMESUA1050_3 before/after swap, the
Figure 3.66 Before Swap EDGE performance of FUMESUA1050_3
2009-09-29
Page68, Total93
Figure 3.67 After Swap EDGE performance of FUMESUA1050_3
Figure 3.68 After Swap GPRS performance of FUMESUA1050_3

From the above figure, we can see that there is more than 3.5Kb/s (28Kbit/s) for EDGE
download speed in FUMESUA1050_3 before swap, and there is more than 20Kb/s
(160Kbit/s) for EDGE download speed in FUMESUA1050_3 after swap, and there is more
than 7Kb/s (56Kbit/s) for GPRS download speed in FUMESUA1050_3 after swap. Also
before swap.
Cell
Longitude Latitude
FUMESUA1050_3
Table 3.47
Test Time
Test
Type
Before swap
16/03/2009 EDGE
18:54
-1.51864 6.71117
After swap
01/04/2009 EDGE
14:13
BCCH
Cell ID
Level
C/I
-61
31050 19.12
-47
21101 21.91
Data service functionality validation results for FUMESUA1050_3
3.7.15 GPRS/EDGE performance of ANWOMASO1088_3

A GPRS/EDGE test was implemented at ANWOMASO1088_3 before/after swap, the
GPRS performance was shown as following:
2009-09-29
Page69, Total93
Figure 3.69 Before Swap EDGE performance of ANWOMASO1088_3
Figure 3.70 After Swap EDGE performance of ANWOMASO1088_3
Figure 3.71 After Swap GPRS performance of ANWOMASO1088_3

From the above figures, we can see that there is more than 2KB/s (16Kbit/s) for EDGE
download speed in ANWOMASO1088_3 before swap, and there is more than 20KB/s
(160Kbit/s) for EDGE download speed in ANWOMASO1088_3 after swap, and there is
more than 9Kb/s (72Kbits/s) for GPRS download speed in ANWOMASO1088_3. Also we
can see that the degree of fluctuations is less for the download speed after swap than
before swap.
2009-09-29
Page70, Total93
Cell
Longitude Latitude
ANWOMASO1088_3
Table 3.48
Test Time
Test
Type
Before swap
16/03/2009 EDGE
18:45
-1.53067 6.69036
After swap
01/04/2009 EDGE
13:38
BCCH
Cell ID
Level
C/I
-65
31088 17.00
-48
21101 23.16
Data service functionality validation results for ANWOMASO1088_3
3.7.16 GPRS/EDGE performance of NHYIAESO1075_1

A GPRS/EDGE test was implemented at NHYIAESO1075_1 before/after swap, the
Figure 3.72 Before Swap EDGE performance of NHYIAESO1075_1
Figure 3.73 After Swap EDGE performance of NHYIAESO1075_1
2009-09-29
Page71, Total93
Figure 3.74 After Swap GPRS performance of NHYIAESO1075_1

From the above figures, we can see that there is more than 4Kb/s (28Kbit/s) for EDGE
download speed in NHYIAESO1075_1 before swap, and there is more than 19Kb/s
(152Kbit/s) for EDGE download speed in NHYIAESO1075_1 after swap, and there is
more than 7Kb/s (56Kbit/s) for GPRS download speed in NHYIAESO1075_1 after swap.
Cell
Longitude Latitude
NHYIAESO1075_1
Table 3.49
Test Time
Test
Type
Before swap
16/03/2009 EDGE
14:54
-1.62264 6.66509
After swap
30/03/2009 EDGE
11:43
BCCH
Cell ID
Level
C/I
-63
11705 20.97
-62
21101 21.71
Data service functionality validation results for NHYIAESO1075_1
3.7.17 GPRS/EDGE performance of KUMASI_GBC_TD1008_2

A GPRS/EDGE test was implemented at KUMASI_GBC_TD1008_2 before/after swap,
the GPRS/EDGE performance is shown below:
Figure 3.75 Before Swap EDGE performance of KUMASI_GBC_TD1008_2
2009-09-29
Page72, Total93
Figure 3.76 After Swap EDGE performance of KUMASI_GBC_TD1008_2
Figure 3.77 After Swap GPRS performance of KUMASI_GBC_TD1008_2

From the above figures, we can see that there are more than 3Kb/s (24Kbit/s) for EDGE
download speed in KUMASI_GBC_TD1008_2 before swap, and there are more than
20Kb/s (160Kbit/s) for EDGE download speed in KUMASI_GBC_TD1008_2 after swap,
and there are more than 7Kb/s (56Kbit/s) for GPRS download speed in
KUMASI_GBC_TD1008_2 after swap.
2009-09-29
Page73, Total93

The data service functionality validation result as following:
Cell
Longitude Latitude
Test Time
Test
Type
Before swap
16/03/2009 EDGE
15:00
KUMASI_GBC_TD1008_2 -1.61017 6.67977
After swap
29/03/2009 EDGE
17:46
Table 3.50
BCCH
Cell ID
Level
C/I
-50
21008 15.49
-47
21101 23.66
Data service functionality validation result for KUMASI_GBC_TD1008_2
3.7.18 GPRS/EDGE performance of SANTASI1073_3

A GPRS/EDGE test was implemented at SANTASI1073_3 before/after swap, the GPRS
performance is shown below:
Figure 3.78 Before Swap EDGE performance of SANTASI1073_3
Figure 3.79 After Swap EDGE performance of SANTASI1073_3
2009-09-29
Page74, Total93
Figure 3.80 After Swap GPRS performance of SANTASI1073_3

From the above figures, we can see that there is more than 3.5KB/s (28Kbit/s) for EDGE
download speed in SANTAS1073_3 before swap, and there is more than 21KB/s
(168Kbit/s) for EDGE download speed in SANTAS1073_3 after swap, and there is more
than 9Kb/s (72Kbits/s) for GPRS download speed in SANTAS1073_3. Also we can see
that the degree of fluctuations is less for the download speed after swap than before
swap.
Cell
Longitude Latitude
SANTAS1073_3
Table 3.51
2009-09-29
Test Time
Test
Type
Before swap
16/03/2009 EDGE
15:17
-1.63875 6.65919
After swap
30/03/2009 EDGE
10:59
BCCH
Cell ID
Level
C/I
-50
11073 18.42
-47
21101 23.50
Data service functionality validation results for SANTAS1073_3
Page75, Total93
4 CR Troubleshooting
Up till now, Huawei have submitted 9 Change Requests which include hundreds of
configurations which have resolved lots of network issues.
HW CR N1.xls
HW CR N2.xls
HW CR N3.xls
HW CR N4.xls
HW CR N6.xls
HW CR N7.xls
HW CR N8.xls
HW CR N9.xls
HW CR N5.xls
4.1 Low Outgoing inter-BSC Handover Success Rate

Issue description:
The Outgoing Inter-BSC handover success rate From AS_KUM_BSC01 to
AS_KUM_BSC02 was very low, less than 50 percent, shown in figure 1 below.
BSC to BSC
Outgoing Inter-Cell
Handover Requests
Successful Cell
Outgoing Handovers
Success Rate of Cell

Outgoing Handovers
BSC1--BSC2
23577
11134
47.22
BSC2--BSC1
5309
4500
84.76
BSC1--BSC1
825505
807997
97.88
BSC2--BSC2
119552
117578
98.39
Table 4.1
The statistics of Inter-BSC handover
Then we got the failed outgoing handover reason statistics, shown in figure 2 below. From
figure 2, all the handover failures were caused by Handover Request Rejected.
Start Time
BSC Name
Cell Name
Failed Outgoing
Failed Success Rate
External Inter-Cell Outgoing of Outgoing
Handovers
External
External
(Handover Request Inter-Cell
Inter-Cell
Rejected)
Handovers Handover
23/03/2009
AS_KUM_BSC02
KUMAWU_GSM_1
23
23
0.0
23/03/2009
AS_KUM_BSC02
KUMAWU_GSM_3
19
19
0.0
23/03/2009
AS_KUM_BSC02
EFFIDUASE_3
164
164
1.2
23/03/2009
AS_KUM_BSC02
EFFIDUASE_1
23
23
4.2
23/03/2009
AS_KUM_BSC01
EJURA_RS_GT_2
11.1
23/03/2009
AS_KUM_BSC01
ABOASO_3
1221
1221
0.2
23/03/2009
AS_KUM_BSC01
BOAMANG_2
0.0
23/03/2009
AS_KUM_BSC01
AGONA_GT_2
63
63
0.0
23/03/2009
AS_KUM_BSC01
AGONA_GT_1
26
26
0.0
2009-09-29
Page76, Total93

23/03/2009
AS_KUM_BSC01
JAMASI_1
298
298
0.0
23/03/2009
AS_KUM_BSC01
DCS_OTEC_FM_3
81
81
31.4
24/03/2009
AS_KUM_BSC01
EJURA_RS_GT_2
22.2
24/03/2009
AS_KUM_BSC01
ABOASO_3
781
781
4.3
24/03/2009
AS_KUM_BSC01
BOAMANG_2
14
14
0.0
24/03/2009
AS_KUM_BSC01
AGONA_GT_1
14
14
39.1
24/03/2009
AS_KUM_BSC01
TANOSO_GT_1
102
102
26.6
25/03/2009
AS_KUM_BSC01
EJURA_RS_GT_2
25.0
25/03/2009
AS_KUM_BSC01
MAMPONG_GT_1
25.0
25/03/2009
AS_KUM_BSC01
KWADASO_NSUOM_1
20
20
35.5
Table 4.2
The reason KPI for handover failure
The data below is based on the tracing of the A interface of the handover from
PATASI_GT_1 (CI=11002) belonging to BSC01 to AGRIC_COLLOEGE_1 (CI=11031)
belonging to BSC02.
Figure 4.1 The message in A interface forBSC01
Figure 4.2 The reason contained in Handover Required Reject message
2009-09-29
Page77, Total93
Figure 4.3 The message in A interface for BSC02
Figure 4.4 The serving cell (CI=11002) and target cell Handover Request (CI=11031)
in Handover Request message
2009-09-29
Page78, Total93
Figure 4.5 The measurement point where handover failure happened
Analysis:
From the user tracing message on BSC01, we can see that MSC sent Handover Request
message to BSC02 after BSC01 having sent Handover required message to the MSC.
Then BSC02 sent a Handover Request Acknowledge to the MSC on the A interface, but
the MSC sent a Handover Required Reject message instead of the Handover command
message after 6 seconds. The reason contained in the Handover Required Reject
message is Equipment Failure, shown in Figure 4.
So the low rate of Outgoing Inter-BSC handover success rate is caused by the MSC data.
Proposal:
Figure 6 is the structure of the whole network.
Figure 4.6 The structure of whole network

So we re-homed BSC02 from RCP3 to RCP1 at 4:30am on 16 April, the structure is like in
Figure 7.
2009-09-29
Page79, Total93
Figure 4.7 The structure of whole network after re-homing

After the re-homing action (adjustment of BSC02 from RCP3 to RCP1), we can see that
the handover from BSC01 to BSC02 became normal, 96.31%, shown in Figure 8 below.
So the problem is an inter- Alcatel RCP issue.
DATE
SOURCE BSC
TARGET BSC
Outgoing
Inter-Cell
Handover
Requests
Successful
Cell Outgoing
Handovers
Success Rate
of Cell
Outgoing
Handovers
2009-4-18 AS_KUM_BSC01
AS_KUM_BSC01
1145768
1130633
98.68
2009-4-18 AS_KUM_BSC01
AS_KUM_BSC02
22957
22110
96.31
2009-4-18 AS_KUM_BSC01
Sunyani_BSC_2
241
88
36.51
2009-4-18 AS_KUM_BSC02
AS_KUM_BSC01
22871
21927
95.87
2009-4-18 AS_KUM_BSC02
AS_KUM_BSC02
169324
167470
98.91
2009-4-18 AS_KUM_BSC02
Sunyani_BSC_2
Table 4.3
The statistics for handover after rehoming
Remark:
Because of the inter-RCP problem, so the handover from BSC01 to Sunyani_BSC_2
(Alcatel BSC) remained at a low rate.
4.2 Low Call Success Rate for BSC01 from Apr 16th to Apr
22nd
Issue Description:
From Figure 1, we can see that the CSSR for BSC01 decreased by about 0.6 percent from
16/04/2009 to 21/04/2009.
2009-09-29
Page80, Total93
CSSR For BSC01

99.20
99.00
98.80
98.60
98.40
98.20
98.00
97.80
97.60
11
/0
4
12 /20
/0 09
4
13 /2 0
/0 09
4
14 /20
/0 09
4
15 /20
/0 09
4
16 /2 0
/0 09
4
17 /20
/0 09
4
18 /20
/0 09
4
19 /2 0
/0 09
4
20 /20
/0 09
4
21 /2 0
/0 09
4
22 /20
/0 09
4
23 /20
/0 09
4
24 /2 0
/0 09
4
25 /20
/0 09
4
26 /20
/0 09
4/
20
09
97.40
Figure 4.8 The Tend Line of CSSR for BSC01
Analysis:
(1). Figure 2 is the top bad cell for CSSR, we call see that all bad cells belong to
MILLENIUM_PLAZA site.
Date
Period(hour)
Cell Name
Call Setup Success Rate
16/04/2009
24
MILLENIUM_PLAZA_1
68.48
16/04/2009
24
MILLENIUM_PLAZA_2
67.69
16/04/2009
24
MILLENIUM_PLAZA_3
67.89
17/04/2009
24
MILLENIUM_PLAZA_1
67.11
17/04/2009
24
MILLENIUM_PLAZA_2
65.64
17/04/2009
24
MILLENIUM_PLAZA_3
66.49
18/04/2009
24
MILLENIUM_PLAZA_1
66.35
18/04/2009
24
MILLENIUM_PLAZA_2
65.98
18/04/2009
24
MILLENIUM_PLAZA_3
66.35
19/04/2009
24
MILLENIUM_PLAZA_1
62.90
19/04/2009
24
MILLENIUM_PLAZA_2
64.04
19/04/2009
24
MILLENIUM_PLAZA_3
63.82
20/04/2009
24
MILLENIUM_PLAZA_1
62.85
20/04/2009
24
MILLENIUM_PLAZA_2
63.22
20/04/2009
24
MILLENIUM_PLAZA_3
64.24
21/04/2009
24
MILLENIUM_PLAZA_1
65.83
21/04/2009
24
MILLENIUM_PLAZA_2
65.10
21/04/2009
24
MILLENIUM_PLAZA_3
65.42
Table 4.4
2009-09-29
CSSR top analyses

Page81, Total93

(2).Figure 3 is the statistics for the influence of MILLENIUM_PLAZA on the whole BSC01.
Taking the 16th April for example, we can see that there were 11501 failed assignments
for MILLENIUM_PLAZA site and 2068703 successful TCH assignments for the whole
BSC01, so we can conclude that the whole BSC01 decline rate was caused by
MILLENIUM_PLAZA by 0.56%. After getting the CSSR for the whole BSC01, current
CSSR (98.25%) and adding the influence rate (0.56% of MILLENIUM_PLAZA), we can
see that all the CSSR for BSC01 from 16/04/2009 to 21/04/2009 are normal after adding
the offset caused by MILLENIUM_PLAZA.
Whole BSC01
Call Setup
Failed
Successful
Call
Rate decline
Success
Assignments (CIC
TCH
Setup
caused by
Rate(except
Allocated)(MILLENI Seizures(Who
Succes
MILLENIUM_PLA
MILLENIUM_PLA
UM_PLAZA site)
le BSC01)
s Rate
ZA site
ZA site )
Date
16/04/2009
11501
2068703
0.56
98.25
98.81
17/04/2009
13184
2124734
0.62
98.07
98.69
18/04/2009
11781
2013851
0.58
98.14
98.73
19/04/2009
9532
1850686
0.52
98.26
98.77
20/04/2009
13831
2177480
0.64
98.13
98.76
21/04/2009
12077
2036947
0.59
98.17
98.76
Table 4.5
The influence of MILLENIUM_PLAZA on whole BSC01
(3) MILLENIUM_PLAZA issue

Figure 4 is the structure for the whole network.
The site MILLENIUM_PLAZA was re-homed from BSC02 to BSC01 on APR 16th, but the
Signal Point of MILLENIUM_PLAZA mistook Point B as Point A, shown in Figure 4. So it
caused an inconsistency for CIC between MSC and BSC01, so it was not able to assign
the CIC for this site, at the same time BSC sent Assignment Failure message to MSC
(shown in Figure 5), which contained the reason as terrestrial-circuit-already-allocated
(shown in Figure 6).
So these Assignment Failures were calculated as Failed Assignments (CIC Allocated) in
the KPI statistics, shown in Figure 3.
And after the Signal Point adjustment for MILLENIUM_PLAZA on MSC on APR 22nd, the
CSSR became normal.
2009-09-29
Page82, Total93
Figure 4.9 The structure of whole network
Figure 4.10 Assignment Failure on A interface
Figure 4.11 The reason in Assignment failure message
4.3 Call Drops in Ashanti

Issue Description:
There were more call drops when MS moved between PATASI_GT and NHYIAESO.
2009-09-29
Page83, Total93
Analysis:
When we went along the route from the location belonging to BSC01 to the place which
belongs to BSC02, the RX_level turned weaker and weaker, and at this time, nearly all the
sites around the current location were sites belonging to BSC02, so the call drop. From
Figure 1, we can see that the drop happened at the same time, the BCCH level of
NHYIAESO was about 30dB higher than the Rx_level of PATASI_GT_2 (from Figure 2),
but did not handover.
After tracing the messages on the A interface, we found that after BSC01 sent Handover
Request to the MSC but the MSC sent Handover Required Reject, shown in Figure 3.
Figure 4.12 Drive Test from PATASI_GT to NHYIAESO
Figure 4.13 The BCCH level of neighbour is far higher than PATASI_GT_2
2009-09-29
Page84, Total93
Figure 4.14 MSC sent Handover Required Reject to BSC01
Figure 4.15 The reason contained in Handover Required Reject message
Summary:
So the low rate of Outgoing Inter-BSC handover success rate was caused by the MSC
data.
After the re-homing action (adjustment of BSC02 from RCP3 to RCP1), we realized that
the handover from BSC01 to BSC02 became normal, 96.31%.
So the problem was an Alcatel inter-RCP one.
4.4 Balance of Traffic between 900M and 1800M

Issue Description:
There was a high unbalance between 900M and 1800M for The cell KUMASI_EX_GE_1
and DCS_KUMASI_EX_GT_1, shown below.
Time
Period
(Min.)
25/03/2009 09:00:00
60
25/03/2009 09:00:00
60
25/03/2009 10:00:00
60
25/03/2009 10:00:00
60
25/03/2009 11:00:00
60
25/03/2009 11:00:00
25/03/2009 12:00:00
2009-09-29
TCH Congestion
Rate
TCH Traffic
Erlang
KUMASI_EX_GT_1
0.00
16.16
DCS_KUMASI_EX_GT_1
5.32
41.74
KUMASI_EX_GT_1
0.00
17.12
DCS_KUMASI_EX_GT_1
10.88
45.22
KUMASI_EX_GT_1
0.03
17.58
60
DCS_KUMASI_EX_GT_1
8.61
44.52
60
KUMASI_EX_GT_1
0.03
15.50
Cell Name
Page85, Total93

25/03/2009 12:00:00
60
DCS_KUMASI_EX_GT_1
7.78
44.08
25/03/2009 13:00:00
60
KUMASI_EX_GT_1
0.03
16.51
25/03/2009 13:00:00
60
DCS_KUMASI_EX_GT_1
8.09
43.64
25/03/2009 14:00:00
60
KUMASI_EX_GT_1
0.00
16.84
25/03/2009 14:00:00
60
DCS_KUMASI_EX_GT_1
12.11
44.76
Table 4.6
Load Imbalance of KUMASI_EX_GE_1 and DCS_KUMASI_EX_GT_1
So Huawei submitted a Change request for the traffic imbalance. After adjusting some
configurations, the traffic became normal, details are as below.
Start Time
Period
(Min.)
TCH Congestion
Rate
TCH Traffic
Erlang
30/03/2009 09:00:00
60
KUMASI_EX_GT_1
0.00
21.19
30/03/2009 09:00:00
60
DCS_KUMASI_EX_GT_1
0.09
28.43
30/03/2009 10:00:00
30/03/2009 10:00:00
60
KUMASI_EX_GT_1
0.04
23.71
60
DCS_KUMASI_EX_GT_1
0.20
31.53
30/03/2009 11:00:00
60
KUMASI_EX_GT_1
0.02
25.40
30/03/2009 11:00:00
60
DCS_KUMASI_EX_GT_1
0.36
32.13
30/03/2009 12:00:00
60
KUMASI_EX_GT_1
0.04
23.55
30/03/2009 12:00:00
60
DCS_KUMASI_EX_GT_1
0.47
34.74
30/03/2009 13:00:00
60
KUMASI_EX_GT_1
0.00
22.82
30/03/2009 13:00:00
60
DCS_KUMASI_EX_GT_1
0.68
33.96
30/03/2009 14:00:00
60
KUMASI_EX_GT_1
0.02
24.55
30/03/2009 14:00:00
60
DCS_KUMASI_EX_GT_1
0.31
32.86
Table 4.7
2009-09-29
Cell Name
Load balance of KUMASI_EX_GE_1 and DCS_KUMASI_EX_GT_1
Page86, Total93
5 The issue existing in the network

1. There is still some interference for the network, and it affect the performance of the
network, especially for the TCH Call Drop Rate, Handover Success Rate and so on. Some
analyses should be put on this further.
2. The transmission is not stable for some sites sometimes, and it affects the network. So
some actions should be taken to improve the transmission status.
3. Because of the coverage expanding, some overshooting appeared in some cells. So
the down tilt for the antenna should be checked and adjusted properly according to the
actual situation.
2009-09-29
Page87, Total93
6 Conclusion
Based on the good cooperation of Vodafone, the swap and optimization has gone and will
continue to go on smoothly. At the moment, the status of the network is better. The test
results of the Rx_ level, Rx_ quality and GPRS are better than the previous network.
Throughout the test and optimization period, Vodafone has supported us significantly. We
owe the current status of the network to their cooperation, we greatly appreciate you all.
Thank you!
Vodafone Swap RNP&O team
12thMay, 2009
2009-09-29
Page88, Total93
Appendix 1.
AMR KPI Statistics
The table below shows the statistics about AMR utilization in Western region.
Date
BSC Name
TCH
Traffic
Erlang
Traffic Erlang
on AMR TCH
Half Rate
Traffic
Erlang on
AMR TCH
Full Rate
AMR
Traffic
Erlang
AMR
utilization
Percentage
09/22/2009
AS_KUM_BSC01
1076.17
705.47
222.10
927.58
86.19
09/22/2009
AS_KUM_BSC02
439.82
314.59
60.38
374.98
85.26
09/23/2009
AS_KUM_BSC01
1090.94
710.09
228.68
938.78
86.05
09/23/2009
AS_KUM_BSC02
433.45
315.25
55.24
370.49
85.47
09/24/2009
AS_KUM_BSC01
1109.55
727.41
229.58
956.99
86.25
09/24/2009
AS_KUM_BSC02
454.45
326.77
62.18
388.95
85.59
09/25/2009
AS_KUM_BSC01
1136.48
738.01
242.68
980.68
86.29
09/25/2009
AS_KUM_BSC02
477.73
345.11
64.58
409.70
85.76
09/26/2009
AS_KUM_BSC01
1069.23
737.46
188.56
926.02
86.61
09/26/2009
AS_KUM_BSC02
475.13
350.96
60.51
411.47
86.60
09/27/2009
AS_KUM_BSC01
997.43
707.69
157.44
865.13
86.74
09/27/2009
AS_KUM_BSC02
462.84
336.28
63.57
399.85
86.39
Table 1 AMR Traffic Statistics

From table 1, we can see that the AMR utilization percentage is around 86%, this means
that AMR utilization rate is very high in AS_KUM_BSC01&2, which will improve the voice
quality undoubtedly.
09/22/2009
AS_KUM_BSC01
Percent
age of
Uplink
FR
AMR of
4.75
kbit/s
0.45
09/22/2009
AS_KUM_BSC02
1.36
0.00
3.67
0.00
0.00
4.34
0.00
60.61
09/23/2009
AS_KUM_BSC01
0.49
0.00
2.91
0.00
0.00
1.96
0.00
58.19
09/23/2009
AS_KUM_BSC02
1.44
0.00
3.71
0.00
0.00
4.41
0.00
61.68
09/24/2009
AS_KUM_BSC01
0.49
0.00
2.91
0.00
0.00
1.94
0.00
58.57
09/24/2009
AS_KUM_BSC02
1.43
0.00
3.73
0.00
0.00
4.44
0.00
60.63
09/25/2009
AS_KUM_BSC01
0.50
0.00
2.95
0.00
0.00
1.95
0.00
57.86
09/25/2009
AS_KUM_BSC02
1.49
0.00
3.77
0.00
0.00
4.53
0.00
60.74
09/26/2009
AS_KUM_BSC01
0.51
0.00
3.06
0.00
0.00
2.03
0.00
61.92
09/26/2009
AS_KUM_BSC02
1.53
0.00
3.89
0.00
0.00
4.83
0.00
62.01
09/27/2009
AS_KUM_BSC01
0.55
0.00
3.16
0.00
0.00
2.25
0.00
63.72
09/27/2009
AS_KUM_BSC02
1.54
0.00
3.85
0.00
0.00
4.92
0.00
60.54
Date
BSC
Percent
age of
Uplink
FR
AMR of
5.15
kbit/s
0.00
Percent
age of
Uplink
FR
AMR of
5.90
kbit/s
2.94
Percent
age of
Uplink
FR
AMR of
6.70
kbit/s
0.00
Percent
age of
Uplink
FR
AMR of
7.40
kbit/s
0.00
Percent
age of
Uplink
FR
AMR of
7.95
kbit/s
1.89
Percent
age of
Uplink
FR
AMR of
10.20
kbit/s
0.00
Percenta
ge of
Uplink
FR AMR
of 12.20
kbit/s
58.74
Table 2 AMR full rate codec utilization

2009-09-29
Page89, Total93

The maximum speech coding rate for AMR is 12.2 Kbit/s, and the minimum coding rate is
4.75 Kbit/s. The counts in table 2 show the utilization situation for AMR, almost 60% of
frames are the maximum rate, which is very good for the Voice Quality.
Percent Percenta
age of
ge of
Percentage Percentage
Uplink
Uplink of Uplink of Uplink
Date
BSC
HR AMR HR AMR HR AMR of HR AMR of
of 4.75 of 5.15 5.90 kbit/s 6.70 kbit/s
kbit/s
kbit/s
09/22/2009 AS_KUM_BSC01
1.07
0.00
0.48
0.00
Percenta
Percentage ge ofn
of Uplink Uplink
HR AMR of HR AMR
7.40 kbit/s of 7.95
kbit/s
22.96
0.10
09/22/2009 AS_KUM_BSC02
0.98
0.00
0.76
0.00
15.06
0.12
09/23/2009 AS_KUM_BSC01
1.09
0.00
0.50
0.00
23.38
0.12
09/23/2009 AS_KUM_BSC02
0.89
0.00
0.70
0.00
14.03
0.12
09/24/2009 AS_KUM_BSC01
1.09
0.00
0.53
0.00
22.96
0.10
09/24/2009 AS_KUM_BSC02
0.95
0.00
0.70
0.00
15.06
0.12
09/25/2009 AS_KUM_BSC01
1.17
0.00
0.57
0.00
23.79
0.09
09/25/2009 AS_KUM_BSC02
1.03
0.00
0.76
0.00
14.76
0.09
09/26/2009 AS_KUM_BSC01
0.97
0.00
0.47
0.00
19.55
0.09
09/26/2009 AS_KUM_BSC02
0.95
0.00
0.79
0.00
13.98
0.11
09/27/2009 AS_KUM_BSC01
0.87
0.00
0.47
0.00
17.25
0.09
09/27/2009 AS_KUM_BSC02
1.01
0.00
0.82
0.00
15.06
0.12
Table 3 AMR half rate codec utilization

We can see that the AMR half rate code utilization is 4.75kbit/s, 5.90kbit/s,7.40kbit/s,
7.95kbit, just as table 3. And the most part of the calls used in AMR half rate is belonging
to 7.40kbit/s.
2009-09-29
Page90, Total93

Ashanti Region Optimization Report

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Ashanti Region Optimization Report

Transféré par

Droits d'auteur :

Formats disponibles

Ashanti Region Optimization Report for Vodafone GSM Swap Project

Optimization Report for Vodafone

Huawei Technologies Co., Ltd.