UAE DB Optimization

Etisalat Network IOS Implementation __________________________________________________________________________
Emerging Markets Network Solutions Division
IOS Services
Database Optimisation Of the Etisalat Network

A Report
Confidential to Motorola & Etisalat
Page 0
SIGN-OFF FORM
Author: Revised: Revised: Revised: Revised: Srikanth Ramachandran Signature: Signature: Signature: Signature: Signature: Date: 21 June, 1999
Page 1
TABLE OF CONTENTS
1.0 2.0 2.1 3.0 4.0 5.0 5.1 5.2 5.3 5.4 6.0 INTRODUCTION............................................................................................................. 3 DATABASE OPTIMIZATION ......................................................................................... 4 AREA OF IMPLEMENTATION ............................................................................................. 4 DATABASE CHANGES ................................................................................................. 5 IMPLEMENTATION SCHEDULE ................................................................................... 6 BENCHMARKING .......................................................................................................... 7 OMC-R STATISTICS ...................................................................................................... 7 IOS OUTPUTS ............................................................................................................... 7 ASCOM'S QVOICE .......................................................................................................... 7 TEMS........................................................................................................................... 8 ANALYSIS OF RESULTS .............................................................................................. 9
6.1 OMC-R STATISTICS ...................................................................................................... 9 6.1.1 Traffic ....................................................................................................................... 9 6.1.2 Overall Performance .............................................................................................. 10 6.1.3 HandOver Cause Analysis..................................................................................... 11 6.1.4 Failure Analysis...................................................................................................... 12 6.2 IOS RESULTS .............................................................................................................. 13 6.2.1 Up-link and Down-link Quality................................................................................ 13 6.2.2 Up-link and Down-link RxLev................................................................................. 14 6.2.3 Up-link and Down-link Transmit Powers................................................................ 15 6.2.4 RxQual Distribution after Qual Power Control ....................................................... 16 6.3 ASCOM - QVOICE RESULTS ....................................................................................... 17 6.3.1 Speech Quality....................................................................................................... 17 6.4 TEMS DRIVE TESTS .................................................................................................... 19 6.4.1 RxQual ................................................................................................................... 19 7.0 8.0 8.1 8.2 SUMMARY.................................................................................................................... 20 ANNEXURE .................................................................................................................. 21 ANNEX I - DATABASE CHANGES.................................................................................... 21 ANNEX II - IMPLEMENTATION SCHEDULE ....................................................................... 23
Page 2
1.0
Introduction
The IOS based network optimization was initiated on two BSCs in the network, viz. BSCs 4 and 7. The analyses of the IOS outputs indicated, apart from hardware and RF issues, sub-optimal database settings and other inconsistencies. Recommendations on database optimization were put together and forwarded to Etisalat. A database changes implementation plan was drawn up and the changes implemented on BSCs 4 and 7. This report summarises the database changes that were performed and the results obtained.
Page 3
2.0
Database Optimization
An analysis of the BSS databases of BSCs 4 and 7 was carried out. The settings in the handover and power control processes were primarily looked into and a set of optimal values for them created. It was noticed that there were multiple sets of values used in the network and there wasn't any standard setting for the database parameters resulting in sub-optimal network performance. Also, this was a cause of concern to the optimizers as it wasn't possible for them to remember the varying power control and handover parameters for every cell (There were as many as 7 different power window settings in these two BSCs) and the like while performing optimization. Hence, it was planned to standardize the various database parameters, enable some of the database features, which were not in use in the network and set the parameters to optimum values. A schedule was created indicating the dates when the changes will be performed and the benchmarking activities to be carried out. A copy of the schedule is attached in the following section. 2.1
Area of Implementation
Etisalat wished to perform the changes on a small area to begin with, check the improvements obtained and then based on the results propagate the same to the rest of the network. Since the database inaccuracies were identified in BSCs 4 and 7, it was planned to perform these changes on all the cells in BSCs 4 and 7 and use this area for all the benchmarking and analyses.
Page 4
3.0
Database Changes
The database changes were planned to be performed in three phases. A list of the database changes that were planned for each phase is attached as Annex-I.
Page 5
4.0
Implementation Schedule
A copy of the schedule showing database changes implementation plan is attached as Annex-II.
Page 6
5.0
Benchmarking
The following benchmarking techniques were used. 5.1 OMC-R statistics IOS outputs Ascom's QVoice TEMS drive tests
OMC-R Statistics
A list of OMC-R statistics, that shall be monitored before and after each phase of the database changes, was created by Motorola & Etisalat and all the corresponding raw statistics were enabled. The busy traffic time in the Etisalat network is distributed over two periods, one around noon and the other at night. The busy periods are 10.00am to 2.00pm in the day and 7.00pm to 11.00pm in the night. Also, it was noticed that the evening busy period carried much more traffic than the day busy period. Since all the statistics are effectively weighed with respect to the traffic during that period it was decided, for ease of analyses, to look into daily averages for all statistics and not half-hour or busy-hour statistics. 5.2
IOS Outputs
Data collection using IOS was planned before and after each phase of changes. The peak traffic days on the Etisalat network are Wednesdays and Thursdays. Hence the IOS data collection was planned to be performed over four days in each case, going through from Tuesday to Friday. The following parameters were planned to be monitored using the IOS - The up-link & down-link rxqual, the up-link & down-link rxlevs, and the MS & BTS transmit powers. 5.3
Ascom's QVoice
To Benchmark the network with reference to speech quality, it was planned to use the QVoice equipment. The area that has to be driven with the QVoice equipment was planned and the routes that need to be driven identified. The same routes were driven before and after each set of changes. The mean call duration as calculated from the OMC-R statistics was around 75secs. Hence, the calls made using QVoice were limited to 75secs each as well. The drive
Page 7
testing was planned to be performed during the day busy hour, between 10.30am & 1.30pm. 5.4
TEMS
Drive tests using TEMS were planned to cover the same routes as the QVoice drives. However, since the rxqual, rxlev and power information obtainable from IOS is far more reliable due to the volume of data these are based on, when derived using IOS, the TEMS drive tests were used only to get a quick sample of the performance changes on each of the implementations. With the implementation of IOS, TEMS data would not be necessary for benchmarking. This report however summarises some of the TEMS results as well to help the reader compare the TEMS results with IOS.
Page 8
6.0
6.1
Analysis of Results
OMC-R Statistics
The OMC-R statistics were collected for the following period 25th May to 20th June. The database changes were implemented on the following days. Phase-I Phase-II Phase-III : : : 1st June 7th June 14th June
All the statistics discussed are daily averages over BSCs 4 and 7. 6.1.1 Traffic The graph below gives a feel for the distribution of the Call Volume, the TCH Assignments and the TCH traffic in the area of implementation of the database changes. As can be seen in the graphs the peak traffic is on Thursdays and the least traffic is on Fridays. It can be noticed that with the advent of summer, the traffic has been slowly receding on the network.
OMC-R Statistics - Network Traffic

1200000 400
1000000
350
800000
300
Erlangs
600000
250
Call Volume Alloc_TCH Traffic (Erls)
Volume
400000
200
200000
150
100
25 -M 26 ay-M 99 27 ay-M 99 28 ay-M 99 29 ay-M 99 30 ay-M 99 31 ay-M 99 01 ay-J 99 u 02 n-9 -J 9 u 03 n-9 -J 9 u 04 n-J 99 u 05 n-9 -J 9 u 06 n-9 -J 9 u 07 n-9 -J 9 u 08 n-9 -J 9 un 09 -J 99 u 10 n-9 -J 9 u 11 n-9 -J 9 un 12 -9 -J 9 u 13 n-9 -J 9 u 14 n-J 99 u 15 n-9 -J 9 u 16 n-J 99 u 17 n-9 -J 9 u 18 n-9 -J 9 u 19 n-9 -J 9 u 20 n-9 -J 9 un -9 9
Date
Page 9
6.1.2 Overall Performance The chart below shows the Call Setup Success Rate, the HandOver Success Rate, TCH Blocking Rate and the Drop Call Rate. It can be observed that there have been improvements in the Call Setup Success Rate and a slight improvement in the HandOver Success rate. The main reason for the improvement in the Call Setup Success is the reduction in the TCH blocking rate, which dropped by almost a percent. The database changes will not directly impact the Call Setup and release as the changes are mostly handover and power control related. However, they would ensure that the call is on the right cell, transmitting the required power thus improving the overall Call Setup Success. The average Call Setup success for the week after the third phase has increased to 94.17% from 92.10% for the week before the database changes. The HandOver Success Rate has shown improvements as well from an average of 95.99% to 96.69%. The Drop Call Rate, however, has been hovering around the 1.7% mark and the average for week after third phase is 1.65% compared to the 1.7% before the changes. However, the overall changes in drop call rate during this period have been fairly insignificant.
OMCR Statistics - Overall Performance

98 4.2
96
3.6
Blocking and Drop Call %
94 Success Rate %
92
2.4
90
1.8
Call Setup Succ(%) HO Succ Rate(%) TCH Block (%) Drop Call Rate (%)
88
1.2
86
0.6
84
M 26 ay-M 9 9 27 ay-M 9 9 28 ay-M 9 9 29 ay-M 9 9 30 ay-M 9 9 31 ay-M 9 9 a 0 1 y-9 -J 9 un 0 2 -9 -J 9 u 03 n-9 -J 9 u 04 n-9 -J 9 u 05 n-9 -J 9 u 06 n-9 -J 9 u 07 n-9 -J 9 u 08 n-9 -J 9 u 09 n-9 -J 9 u 10 n-9 -J 9 u 11 n-9 -J 9 u 12 n-9 -J 9 u 13 n-9 -J 9 u 14 n-9 -J 9 u 15 n-9 -J 9 u 16 n-9 -J 9 u 17 n-9 -J 9 u 18 n-9 -J 9 u 19 n-9 -J 9 u 20 n-9 -J 9 un -9 9
25 -
Date
Page 10
6.1.3 HandOver Cause Analysis The handover cause distribution as obtained from the OMC-R is shown below. The ratio of power budget handovers have shown a significant increase from around 68% to 72% after the first change and further to around 77% after the second. The up-link rxqual handovers have dropped from 11% to around 6%, while the down-link rxqual handovers have dropped from 17% to 15%. The uplink and down-link interference handovers have also shown a decline. Hence overall, the handover performance has improved in terms of maintaining call
OMC-R Statistics - HandOver Cause Distribution
20 18 16 14 HandOver Causes 12 10 8 6 4 2 0 80 78 76 74 72 70 68 66 64 62 60
Power Budget HandOvers
UL Quality DL Quality UL Intf DL Intf Congestion Pwr Budget
25 -M 26 ay-M 99 27 ay-M 99 28 ay-M 99 29 ay-M 99 30 ay-M 99 31 ay-M 99 01 ay-J 99 u 02 n-9 -J 9 u 03 n-9 -J 9 u 04 n-J 99 u 05 n-J 99 u 06 n-9 -J 9 u 07 n-9 -J 9 un 08 -J 99 u 09 n-9 -J 9 un 10 -J 99 u 11 n-9 -J 9 u 12 n-9 -J 9 un 13 -J 99 u 14 n-9 -J 9 u 15 n-J 99 u 16 n-J 99 un 17 -9 -J 9 u 18 n-J 99 u 19 n-9 -J 9 u 20 n-9 -J 9 un -9 9
Date
quality and the MSs are handed over to better cells more often.
Page 11
6.1.4 Failure Analysis The Rflosses and the HandOver Failure plots are shown below. The TCH rfloss rate hasn't shown much variation over the last four weeks, while the SDCCH rfloss rate has shown a marginal decrease which however is not significant. There has also been a marginal increase in the handover failure lost ms, while the handover failure return has dropped by over half a percent. The handover failure return indicates the handovers attempts that couldn't make it to the target cell and hence came back to the source cell.
OMC-R Statistics - Failures

4
3.5
2.5 Failures SD RF Loss(%) 2 TCH RF Loss(%) HO Fail Return(%) HO Fail Lost(%) 1.5
0.5
0
-M ay -9 -M 9 a 27 y-9 -M 9 a 28 y-9 -M 9 a 29 y-9 -M 9 a 30 y-9 -M 9 a 31 y-9 -M 9 ay 01 -99 -J un 02 -99 -J un 03 -99 -J un 04 -99 -J un 05 -99 -J un 06 -99 -J un 07 -99 -J un 08 -99 -J un 09 -99 -J un 10 -99 -J un 11 -99 -J un 12 -99 -J un 13 -99 -J un 14 -99 -J un 15 -99 -J un 16 -99 -J un 17 -99 -J un 18 -99 -J un 19 -99 -J un 20 -99 -J un -9 9 26
25
Date
Page 12
6.2
IOS Results
The IOS collection platform was used to collect data for 3 to 4 days before and after each set of database changes. All the IOS results are based on over 3 million MRs of data collected over all the cells in the BSCs 4 and 7. 6.2.1 Up-link and Down-link Quality The bar chart below indicates the overall up-link and down-link rxqual percentages for the rxqual range 0 to 4, over all the cells in BSCs 4 and 7. The 4 bars indicate the values after each phase. It can be noticed that the up-link quality on the Etisalat network is poorer than the down-link quality by over 2.5%. It can be noticed that the overall rxqual has shown consistent improvements through each phase of the database changes. However, the third phase has offered a marginal 0.02% increase in up-link rxqual over the second phase, while the down-link rxqual has dropped by around 0.06%. These minor variations could well be caused by the difference in type of weekly traffic.
IOS Results - RxQual Uplink and Downlink

98
97
96
Qual % 95
20 May - Before 6 Jun - After Phase-1 12 Jun - After Phase-2 19 Jun - After Phase-3
94
93
92 Uplink RxQual - 0 to 4 RxQual Distribution Downlink RxQual - 0 to 4
The database changes in phase-3 were the rxqual power control window, the derived handover power feature and the Enhanced power control algorithm. The derived handover power feature is up-link oriented and though this hasn't had much effect on the overall up-link rxqual, this along with the up-link rxqual
Page 13
power window have helped reduce the overall up-link Tx power and the up-link rxlev mean, which can be seen in later graphs. The mean up-link rxlev has reduced to 31 which is close to the l_rxlev_ul_p value. This is expected because of the aggressive qual power control that is being performed. However, on the down-link, though the l_rxlev_dl_p is set to 35, the mean rxlev has stayed at a value close to 38 despite the qual power control. This could indicate that the network has down-link rxqual problems at levels close to this, which is the reason why further power down is unable to take place. This could be one of the reasons for the marginal drop in down-link rxqual after the implementation of the third phase. This needs further investigation. 6.2.2
Up-link and Down-link RxLev
The bar chart below indicates the overall up-link and down-link mean rxlevs. It can be noticed that the mean up-link rxlev has shown a slight increase in the first two stages. The MS powers weren't set correctly on several cells, which were standardized in the first phase. The up-link rxlev power windows had varying settings, around seven of them, and most of them had the lower limit of rxlev power control set to 20 and 25. This was shifted up to 30 and the upper limit made 40 in the second phase which has contributed to the increase in the mean up-link rxlev, while the quality has improved as well. In the third phase, the mean up-link rxlev has dropped by 2 dBs without any deterioration in the up-link rxqual. This is due to the qual power control and the derived handover power algorithms.
IOS Results - Rxlev Mean

45
40 Receive Signal Strength - RxLev
35 20 May - Before 6 Jun - After Phase-1 12 Jun - After Phase-2 19 Jun - After Phase-3 30
25
20 Uplink Rxlev Mean Downlink Rxlev Mean - Macros & Micros Downlink Rxlev Mean - Macros
The down-link rxlev has shown a consistent drop from their earlier 40+ values. Since the micro-cells do not employ power control, the down-link rxlev for Macro's alone is shown separately. With the use of the Qual power window although more than a dB of drop in down-link rxlev has been noticed a further
Page 14
drop in the down-link rxlev bringing it closer to the l_rxlev_dl_p value of 35 was expected. However, it appears that calls suffer from poorer rxquals even at levels close to 38 and 40 on the down-link, hence the mean rxlev is still around 3 dBs above the l_rxlev_dl_p value.
6.2.3
Up-link and Down-link Transmit Powers
The mean up-link transmit power indicates an increase in the first two stages for reasons mentioned in the earlier section. However, after the third phase the Uplink TxPower has dropped by over 2dBs without any deterioration in rxqual. Apart from the lower overall interference level this would also offer much higher mobile battery life. Also indicated in the chart are the BTS transmit power mean values, one for the Macros alone and the other inclusive of the Micros. A couple dB reduction in the BTS Transmit power mean values can be noticed.
IOS Results - Tx Power Mean

40
35
30 Tx Power dBm
25
20
15
10 MS Tx Power Mean BTS Tx Pwr Mean - Macros BTS Tx Power Mean - Total
Page 15
6.2.4
RxQual Distribution after Qual Power Control
The rxqual power control window was one of the settings Etisalat wished to perform detailed analyses on. The graph attached indicates the RxQual percentage distribution on the uplink and downlink before and after the implementation of the rxqual power control window. It is worth noting that, though a few cells had an aggressive Qual power control window, quite a few cells had the upper limit of the rxqual power control set to 0, which means that there wouldn't be any power reductions ordered based on rxqual. Etisalat were concerned that setting the upper limit of rxqual to a non-zero value would highly reduce the number of good rxqual samples, although it was agreed that rxqual values till Qual of 3 or 4 would produce good quality speech. It was pointed out to Etisalat that the power down on rxqual would occur only as far as the lower limit of the level power control window would allow it and hence if the RxQual is 0 at such a level, no further power downs would occur. Also, the parameter were set such that out of the 3 sample average used for power control, if more than one sample has RxQual of 1 power downs will not be triggered.
IOS Results - RxQual Comparison
100% 3.05% 0.98% 95% 1.33% 1.88% 2.78% 90% 2.99% 0.97% 1.35% 1.96% 3.81% 2.85% 2.71% 2.91% 4.34% 4.60% 4.08% RxQual - 7 RxQual - 6 RxQual - 5 RxQual - 4 RxQual - 3 RxQual - 2 RxQual - 1 RxQual - 0 4.04% 2.62% 2.66% 0.62% 0.79% 1.48% 0.63% 0.80% 1.50%
RxQual Distribution
2.54% 2.70% 85%
4.36%
80% 84.74% 75% 84.26% 82.25% 81.42%
70% Uplink RxQual Before Phase-3 Uplink RxQual After Phase-3 Downlink RxQual Before Phase-3 Downlink RxQual After Phase-3
It can be seen that by setting the Qual power control window to 20(lower limit of Qual-1) and 80(lower limit of Qual-3) there have been less than a percent of samples that have moved out of the Qual-0 band into the Qual 1 to 3 bands. We know from the Mean Transmit Power values shown in the previous graphs that the mean transmit power has reduced by around 2.5dBs on the uplink and around 1.5dBs on the downlink. This indicates that there had been a considerable number of measurement reports wherein the power reduction occurred and the MS stayed at Qual 0 before and after the power reduction.
Page 16
6.3
ASCOM - QVoice Results
QVoice analyses the speech samples on both the up-link and down-link and generates a figure of merit for the speech quality of voice for each sample. The figure of merit is on a scale from 1 to 5, with 1 being excellent and 5 poor. Apart from the speech quality figure, QVoice also gives other down-link information similar to that of TEMS, such as rxlev, rxqual, MS transmit power and the like. Since, these information could be obtained from IOS, whose results are more accurate and reliable as they are based on a much larger number of samples, the rest of the results of QVoice weren't used for analyses. 6.3.1 Speech Quality As described earlier, QVoice generates a figure of merit for the speech quality in the range 1 to 5. The charts generated indicate the percentage samples that fall in the excellent band, that had values of 1, in both up-link and down-link. It can be noticed that the number of down-link samples falling in the excellent band is much lower than the number of up-link samples falling in the excellent band. This has been a matter of concern for Etisalat and needs further investigation.
Qvoice Results - Speech Quality

95
90
85
80 Ascom Quality %
75
70
65
60
55
50 Excellent Uplink Excellent + Good Excellent Downlink Excellent + Good
Looking at the percentage of samples falling in the Excellent and Good bands taken together, it can be inferred that the down-link has shown consistent improvements, while the up-link dropped couple percent after the second phase of changes. A reason for this could be that all the MSs were forced to use higher
Page 17
transmit powers by raising the lower limit of the uplink power window from values of 20 and 25 to 30 on several cells. This can be noticed in the Uplink Transmit Power graphs produced using IOS. This could have resulted in some cases of poorer uplink performance. Nevertheless, this was compensated in the next phase by using tighter rxqual power windows. This degradation, however, hasn't manifested itself in the other benchmarking techniques.
Page 18
6.4
TEMS Drive Tests
The TEMS drive tests were used to get a quick sample of the performance of the network. With the advent of IOS detailed benchmarking with TEMS would no longer be necessary as most of the information obtained from TEMS can be obtained from IOS. The use of IOS would eliminate the inconsistencies noticed in using TEMS for benchmarking as the TEMS results are based normally on relatively less number of calls and hence the deviation could be fairly high. However, as a transition phase it was planned to use the down-link rxqual obtained from TEMS drive tests for benchmarking. Also performed were a set of short calls, 75secs calls, to analyse the call Setup and drop call performances. These results were based on around 40 calls for each phase and the variation in values can obviously be expected to be fairly high. Hence, these results are not included in this report. 6.4.1 RxQual The rxqual graphs for rxqual 0 to 3 and rxqual 0 to 4, both for downlink are shown below. It can be noticed that the downlink rxqual percentage has improved consistently with each phase of the database changes. However, these results need to be looked at with caution as they are based on just 2 hours of drive tests. The IOS outputs are more accurate for comparison of such results. Nevertheless, during this exercise the results obtained from drive tests and those of IOS are found to match each other fairly well.
Drive Test Results - Downlink RxQual

96
94
92 Downlink RxQual %
90
88
86
84 RxQual 0 - 3 RxQual 0 - 4
Page 19
7.0
Summary
The purpose behind the implementation of these database changes was to standardize the BSS databases and set the various database parameters to optimal values. The effects of the database changes on the network performance were detailed in the previous sections. A comparison of all the key performance metrics is summarised below for convenience.
Overall Performance Comparison
100 96.45 95 93.89 94.69 92.1 90 88.93 87.68 84.84 85 Percentage 97.04 94.17 95.99 96.69
80
79.34
Before DB Changes After DB Changes
75
70
65
60 IOS - Uplink RxQual IOS - Downlink RxQual QVoice Uplink Speech Quality QVoice Downlink Speech Quality OMC-R Call SetUp Success Rate OMC-R HandOver Success Rate OMC-R Drop Call Rate 1.7 1.65
The figures for after database changes are the values taken after all the three phases of database changes were complete. It can be noticed from the charts that the quality of the call has improved quite a bit on implementation of these changes. It is hence recommended that these database changes be propagated to all other BSCs in the network.
Page 20
8.0
8.1
Sl No
Annexure
Annex I - Database Changes

Parameter Name Present Proposed Value Value Command
Database Changes - Phase I

1 HreqAve Values for Surround_cell rxlev_dl_ho rxlev_ul_ho Rxqual_dl_ho Rxqual_ul_ho rxlev_dl_pc rxlev_ul_pc Rxqual_dl_pc Rxqual_ul_pc HreqT Values for Surround_cell rxlev_dl_ho rxlev_ul_ho Rxqual_dl_ho Rxqual_ul_ho rxlev_dl_pc rxlev_ul_pc Rxqual_dl_pc Rxqual_ul_pc
4 4 and 5 3 and 4 3 and 5 4 and 5 3 and 4 3 and 4 3 and 4 5
5 5 5 5 5 3 3 3 3
chg_act_alg_data surround_cell <cell_id> 0 0 5,0 chg_act_alg_data rxlev_dl_ho <cell_id> 0 0 5,0 chg_act_alg_data rxlev_ul_ho <cell_id> 0 0 5,0 chg_act_alg_data rxqual_dl_ho <cell_id> 0 0 5,0 chg_act_alg_data rxqual_ul_ho <cell_id> 0 0 5,0 chg_act_alg_data rxlev_dl_pc <cell_id> 0 0 3,0 chg_act_alg_data rxlev_ul_pc <cell_id> 0 0 3,0 chg_act_alg_data rxqual_dl_pc <cell_id> 0 0 3,0 chg_act_alg_data rxqual_ul_pc <cell_id> 0 0 3,0
2 1 and 4 1 and 4 1 and 2 1 and 4 1 and 2 1 and 2 1 and 8 1
1 1 1 1 1 1 1 1 1
chg_act_alg_data surround_cell <cell_id> 0 0 1,1 chg_act_alg_data rxlev_dl_ho <cell_id> 0 0 1,1 chg_act_alg_data rxlev_ul_ho <cell_id> 0 0 1,1 chg_act_alg_data rxqual_dl_ho <cell_id> 0 0 1,1 chg_act_alg_data rxqual_ul_ho <cell_id> 0 0 1,1 chg_act_alg_data rxlev_dl_pc <cell_id> 0 0 1,1 chg_act_alg_data rxlev_ul_pc <cell_id> 0 0 1,1 chg_act_alg_data rxqual_dl_pc <cell_id> 0 0 1,1 chg_act_alg_data rxqual_ul_pc <cell_id> 0 0 1,1
Note : Ensure that the N and P values for all the algorithms have been set to 1. 3 Qual_margin_flag Rxqual_dl_ho Rxqual_ul_ho Adj_qual_margin Rxqual_dl_ho Rxqual_ul_ho MS Power Levels ms_txpwr_max_cc h ms_txpwr_max_def max_tx_ms Handover_power_l evel ms_txpwr_max_cell Cell_reselect_hyst erisis
0&1 0&1
1 1
chg_act_alg_data rxqual_dl_ho <cell_id> 0 0 1,4 chg_act_alg_data rxqual_ul_ho <cell_id> 0 0 1,4
0 0&5
0 0
Set all these parameters to 33dBm for Macro and 25dBm for Micro Use chg_ele command Use chg_ele command Use chg_ele command Use chg_ele command Part of the add_neighbour command 8 & 12 8 Use chg_ele command
Page 21
Database Changes - Phase II

1 Rxlev Power Window U_rxlev_dl_p L_rxlev_dl_p U_rxlev_ul_p L_rxlev_ul_p For all the cells in BSCs 4 and 7 the below values can be used. 45 35 40 30 Use chg_ele command Use chg_ele command Use chg_ele command Use chg_ele command
U_rxlev_dl_p L_rxlev_dl_p U_rxlev_ul_p L_rxlev_ul_p 2 Pow_red_step_siz e 4
For rural/less dense areas the following values can be used. 45 Use chg_ele command 30 Use chg_ele command 40 Use chg_ele command 25 Use chg_ele command 2 Use chg_ele command
RxQual Handover Thresholds l_rxqual_dl_h l_rxqual_ul_h Decision_alg_num Power Control Timers bts_p_con_interval Bts_p_con_ack ms_p_con_interval Ms_p_con_ack Qual_power_flag Rxqual_dl_ho Rxqual_ul_ho Rapid MS power down Rapid_pwr_down 0 and 1 Rpd_trigger 45 rpd_offset 8 rpd_period 2
452 452 1
Use chg_ele command Use chg_ele command Use chg_ele command
4 5
0 2 0 2
Use chg_ele command Use chg_ele command Use chg_ele command Use chg_ele command
1 1
1 45 8 4
Use chg_ele command
Use chg_ele command
Database Changes - Phase III

1 2 mspwr_alg RxQual Power Window u_rxqual_dl_p l_rxqual_dl_p u_rxqual_ul_p l_rxqual_ul_p use_derived_ho_power 0 1 Use chg_ele command
20 80 20 80 1
Use chg_ele command Use chg_ele command Use chg_ele command Use chg_ele command Use chg_ele command
Page 22
8.2
Annex II - Implementation Schedule
Separate Microsoft Project spreadsheet attached.
Page 23

UAE DB Optimization

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

UAE DB Optimization

Uploaded by

Copyright:

Available Formats

Etisalat Network IOS Implementation __________________________________________________________________________

Emerging Markets Network Solutions Division

Database Optimisation Of the Etisalat Network

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

OMC-R Statistics - Network Traffic

Call Volume Alloc_TCH Traffic (Erls)

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

OMCR Statistics - Overall Performance

Blocking and Drop Call %

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Power Budget HandOvers

UL Quality DL Quality UL Intf DL Intf Congestion Pwr Budget

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

OMC-R Statistics - Failures

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

IOS Results - RxQual Uplink and Downlink

92 Uplink RxQual - 0 to 4 RxQual Distribution Downlink RxQual - 0 to 4

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Up-link and Down-link RxLev

IOS Results - Rxlev Mean

40 Receive Signal Strength - RxLev

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

Up-link and Down-link Transmit Powers

IOS Results - Tx Power Mean

Emerging Markets Network Solutions Division

Confidential to Motorola & Etisalat

Etisalat Network IOS Implementation __________________________________________________________________________

RxQual Distribution after Qual Power Control

2.54% 2.70% 85%