INTRODUCTION ..........................................................................................................................5 1. DRIVE TEST PREPARATION .............................................................................................5 1.1. TEST EQUIPMENT SETUP ...............................................................................................5 1.2. DRIVE TEST ROUTES .................................................................................................... 10 2. NETWORK COVERAGE PREDICTION FOR 46 3G SITES IN HAU GIANG .................. 11 2.1. RSCP PLOT PREDICTION FOR HAU GIANG ..................................................................... 11 2.2. ECIO PLOT PREDICTION FOR HAU GIANG ..................................................................... 12 2.3. PILOT POLUTION PREDICTION FOR HAU GIANG ............................................................ 13 3. SITE AUDIT HARDWARE CHECK AND ALARM HANDLING........................................ 13 3.1. SITE DATABASE AUDIT ................................................................................................ 14 3.2. HARDWARE CHECK AND ALARM HANDLING................................................................. 14 3.3. ANTENNA TILT/AZIMUTH RECOMMENDATION CHANGE REQUEST ................................ 14 3.4. NEIGHBOR LIST ADD/DEL RECOMMENDATION: ............................................................ 15 4. DATABASE PARAMETERS CHECK AND OPTIMIZATION RECOMMENDED............. 17 4.1. PARAMETER GROUPS IN RNC DATABASE:..................................................................... 17 4.2. PARAMETER GROUPS IN CATEGORIZE.......................................................................... 18 4.3. IDLE MODE PARAMETERS............................................................................................ 18 4.3.1. Idle Mode WCDMA Parameters ................................................................................... 18 4.3.2. Idle Mode GSM Parameters ........................................................................................ 21 4.4. SHO PARAMETERS ...................................................................................................... 22 4.5. INTER-SYSTEM HANDOVER PARAMETERS .................................................................... 23 4.6. INTER-FREQUENCY HANDOVER PARAMETERS .............................................................. 26 4.7. POWER CONTROL PARAMETERS .................................................................................. 27 4.8. PACKAGE SCHEDULING PARAMETERS .......................................................................... 28 4.9. TELECOM PARAMETERS .............................................................................................. 30 4.10. OTHERS PARAMETERS................................................................................................. 32 4.11. HSPDA RELATED PARAMETERS .................................................................................... 33
Drive Test Report 3
4.11.1. HSPDA Power Parameters ........................................................................................... 33 4.11.2. HSPDA Dynamic Code Allocation ................................................................................. 34 4.11.3. Other Recommended HSDPA Parameters .................................................................... 35 4.11.4. Recommended HSUPA Parameters .............................................................................. 38 5. NETWORK DRIVE TEST RESULT BEFORE AND AFTER OPTIMIZATION.................. 39 5.1. NETWORK PERFORMANCE OVERVIEW BEFORE AND AFTER OPTIMIZATION.. 39 5.2. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM SCANNER 40 5.2.1. RSCP Scan distribution result before and after optimization .......................................... 40 5.2.2. RSCP Scan Coverage plot result before and after optimization....................................... 40 5.2.3. EcIo Scan distribution result before and after optimization ........................................... 41 5.2.4. EcIo Scan Coverage plot result before and after optimization ........................................ 42 5.2.5. Pilot Polution Scan distribution result before and after optimization ............................. 43 5.2.6. Pilot Polution Scan result before and after optimization................................................ 43 5.3. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM SHORT CALL 44 5.3.1. RSCP shortcall distribution result before and after optimization .................................... 44 5.3.2. RSCP shortcall coverage plot result before and after optimization ................................. 45 5.3.3. EcIo shortcall distribution result before and after optimization ..................................... 46 5.3.4. EcIo shortcall coverage plot result before and after optimization .................................. 46 5.4. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM IDLE MODE 47 5.4.1. RSCP Idle distribution result before and after optimization ........................................... 47 5.4.2. RSCP Idle coverage plot result before and after optimization ........................................ 48 5.4.3. EcIo Idle distribution result before and after optimization............................................. 49 5.4.4. EcIo Idle coverage plot result before and after optimization.......................................... 49 5.5. NETWORK SPEECH QUALITY MOS BEFORE AND AFTER OPTIMIZATION ......... 50 5.5.1. MOS distribution result before and after optimization .................................................. 50 5.5.2. MOS coverage plot result before and after optimization ............................................... 51 5.6. DATA THROUGHPUT BEFORE AND AFTER OPTIMIZATION .................................. 52 5.6.1. HSDPA coverage plot result before and after optimization ............................................ 52 5.6.2. HSUPA coverage plot result before and after optimization ............................................ 53
Drive Test Report 4
5.6.3. PING coverage plot result before and after optimization............................................... 54 6. CONCLUSION AND RECOMMENDATION ...................................................................... 55 7. APPENDIX .......................................................................................................................... 56
Drive Test Report 5
INTRODUCTION
This report is the result of the drive test optimization for 46 sites 3G in Hau Giang province to evaluate network performance KPI.The drive test analysis provides the good information to establish key requirements in terms of network coverage for the nominal design. This report will show the detailed coverage analysis, network quality and network performance for the agreed drive test routes.The network coverage (Scan Mode & Idle Mode ), Call Setup Success Rate (CSSR), Drop Call Rate (DCR) speech voice quality (MOS) ,data through put both uplink & downlink for HSDPA ,HSUPA and time delay (PING) are the main Key Performance Indicators (KPIs) during the test. VTC had been assigned 46 sites in Hau Giang province with main scope of work includes Pre-drivetest with 05 UEs (02 UEs for Idle & dedicated ) and 03 UEs for Data card cover all accessible route with car,bike & boat 01 Scanner to verify Coverage and Pilot Polution for main road where car can accessible only MOS speech quality test for main road where car can accessible only OSS/OMC Statistics collection & Analysis for worse cell KPI Evaluation of drive test logs Site Audit & replacement of Faulty Hardware,VSWR Physical antenna tilt/azimuth optimization recommendation & implementation of change request Neighbor audit,Scrambling Code tuning,Parameters tunning recommended Final report with comparasion pre & post drivetest performance
1. DRIVE TEST PREPARATION 1.1. TEST EQUIPMENT SETUP The engineers will be able to monitor the performance of the network and provide solutions to problems encountered. Therefore, main objectives of drive tests are to: check network coverage,Call Setup Success Rate (CSSR), Drop Call Rate (DCR) speech voice quality (MOS) ,data through put
Drive Test Report 6
both downlink & uplink for HSDPA ,HSUPA and time delay (PING), monitor if blocked ,call set up failure or drop call exists, check if actual signal strength coverage in accordance to the planned, check orientation/tilt/height of antennas, check engineering sites audit and parameters feature defined in the CDD, check signal quality received and data throughput. Prior to the actual drive testing of the network, there are some initial preparation tasks that need to be accomplished. Create Tems Cell File Create digital map (e.g.. MapInfo tab file) Drive Test Route (final routes in Hau Giang) All major and accessible roads within the intended coverage areas of the concerned site are required to drive tested. All major and accessible roads in the area of the site being tested including neighbour cells as defined in nemo/TEMS cell file. Equipments Check & Setup (per team) o 1 Laptop o 1 GPS (Global Positioning System) o 1 External antenna for the GPS o 3 Tems Mobile Phones for short +Idle Call o 2 Nemo Mobile Phone for MOS Mobile to Mobile Call o 1 Scanner + External antenna for the GPS o 3 Data card for HSDPA,HSUPA and PING o 8 Test SIM Cards o 1 Power Inverter Starting
Drive Test Report 7
Before opening the computer, make sure that all equipments are connected for them to be easily detected Engineers should ensure that the TEMS/NEMO Phone setting is always in WCDMA mode (Except Idle mode must be set to DualMode GSM/WCDMA). Engineers should ensure that the TEMS/NEMO phone is properly mounted in such a way that the phone cable will not be disconnected. Engineers should ensure that the GPS/SCANNER external antenna is properly mounted on top of the drive test vehicle. Engineers should ensure that the Command Sequence is ended before stopping the logfile recording. Engineers should ensure that during drive test, they cannot pause the recording of the logfile. Following the command sequence settings for the TEMS mobile phones MS1: Short call with call duration at 60s and 10s for idle duration between 2 calls.
Drive Test Report 8
MS2: Idle to measure CPICH & BCCH Coverage Following the command sequence settings for the NEMO mobile phones MS1: Make call with call duration at 60s and 10s for idle duration between 2 calls MS2: Receive Call Following the command sequence settings for t he TEMS Data card DC1: Data card Download DC2: Data card Upload DC3: Data card PING
Drive Test Report 9
Drive Test Report 10
1.2. DRIVE TEST ROUTES The drive test routes for Hau Giang Province have been agreed between VMS4 and VTC. The drive test results ONLY cover for 46 cells of VMS4 provide to VTC in this area.
Hau Giang Drive Test Routes
Drive Test Report 11
2. NETWORK COVERAGE PREDICTION FOR 46 3G SITES IN HAU GIANG The following is network coverage base on prediction for 46 sites in Hau Giang in order to comapare with real drive test result 2.1. RSCP PLOT PREDICTION FOR HAU GIANG
Drive Test Report 12
2.2. ECIO PLOT PREDICTION FOR HAU GIANG
Drive Test Report 13
2.3. PILOT POLUTION PREDICTION FOR HAU GIANG
3. SITE AUDIT HARDWARE CHECK AND ALARM HANDLING The following information sites database was checked and action done before and during optimization activites carried out by VTC
Drive Test Report 14
Items #No Percent (%) HW Check 21 15.22% Antenna Tunning 25 18.12% Cells Audit 138 100.00% Total Cells 138 3.1. SITE DATABASE AUDIT Data collected for sites audit includes Sites Address ( Include details sites address,commune,district & Province) Sites GPS Coordinate longtitude/Latitude Antenna information (Antenna type/Height/Available Antenna Height,Antenna tilt& Azimuth)
All 46 sites (138 cells) was checked & audited. Please refer to more details information in APPENDIX 3.2. HARDWARE CHECK AND ALARM HANDLING Total 21 cells was checked for worse cell KPI & HW issues.Please refer to more details information in APPENDIX 3.3. ANTENNA TILT/AZIMUTH RECOMMENDATION CHANGE REQUEST Total 25/138 cells was request to change antenna tilt & azimuth to improve coverage.Please refer to more details information in APPENDIX
Drive Test Report 15
3.4. NEIGHBOR LIST ADD/DEL RECOMMENDATION: The following list is recommendation for Add/Del neighbor cells. SourceCell_Name Source_CI Source_SC NB Cell_Name NB_CI N_SC Recommedation KGGQ09A 46891 289 HGVT17A 18681 215 Add NB Both 2 way KGGQ09A 46891 289 HGVT17B 18682 213 Add NB Both 2 way KGGQ09A 46891 289 HGVT17C 18683 214 Add NB Both 2 way KGGQ09A 46891 289 HGVT12A 17211 336 Add NB Both 2 way KGGQ09A 46891 289 HGVT12C 17213 338 Add NB Both 2 way KGGQ09A 46891 289 HGVY06C 17793 275 Add NB Both 2 way KGGQ09B 46892 297 HGVT17B 18682 213 Add NB Both 2 way KGGQ09B 46892 297 HGVT17C 18683 214 Add NB Both 2 way KGGQ09B 46892 297 HGVT12A 17211 336 Add NB Both 2 way KGGQ09B 46892 297 HGVT12C 17213 338 Add NB Both 2 way KGGQ04A 46771 96 HGVT12A 17211 336 Add NB Both 2 way KGGQ04A 46771 96 KGGQ09B 46892 297 Add NB Both 2 way HGVY06C 17793 275 HGVT04B 17532 377 Add NB Both 2 way HGVT04B 17532 377 HGVT17B 18682 213 Add NB Both 2 way HGVY07A 17711 41 HGVY21B 18452 73 Add NB Both 2 way HGVY07A 17711 41 HGVY21C 18453 75 Add NB Both 2 way HGVY07B 17712 42 HGVY09C 17783 10 Add NB Both 2 way HGVT03B 17392 379 HGVY06C 17793 275 Add NB Both 2 way HGVY03A 17771 16 HGVY15A 18551 290 Add NB Both 2 way HGVY03A 17771 16 HGVY15C 18553 291 Add NB Both 2 way HGVY03C 17773 18 HGVY09B 17782 9 Add NB Both 2 way HGVY15B 18552 291 HGLM02A 17271 323 Add NB Both 2 way HGVY15B 18552 291 HGPH03C 17133 87 Add NB Both 2 way HGVY15B 18552 291 HGLM05A 17231 61 Add NB Both 2 way HGVY15C 18553 293 HGVY03C 17773 18 Add NB Both 2 way HGVY15C 18553 293 HGVY09B 17782 9 Add NB Both 2 way HGLM05A 17231 61 HGVY15B 18552 291 Add NB Both 2 way HGLM05C 17233 63 HGVY09C 17783 10 Add NB Both 2 way HGLM02A 17271 323 HGVY15B 18552 291 Add NB Both 2 way HGCA05A 17011 176 HGPH11C 18523 188 Add NB Both 2 way HGCA05B 17012 176 HGPH11C 18523 188 Add NB Both 2 way HGPH08C 17623 319 CTPD15C 10973 314 Add NB Both 2 way HGPH08C 17623 319 HGCA01C 17063 22 Add NB Both 2 way HGPH17C 18623 415 HGCA16B 17932 328 Add NB Both 2 way HGPH17C 18623 415 HGCA16A 17931 320 Add NB Both 2 way HGPH15C 17343 431 HGPH17B 18622 414 Add NB Both 2 way HGNB04B 17612 237 HGNB10A 18251 35 Add NB Both 2 way HGNB04B 17612 237 HGNB10B 18252 36 Add NB Both 2 way HGNB04B 17612 237 HGNB06A 17831 23 Add NB Both 2 way HGNB04C 17613 238 HGNB10A 18251 35 Add NB Both 2 way HGNB10A 18251 35 HGNB04B 17612 237 Add NB Both 2 way HGNB10B 18252 36 HGNB04B 17612 237 Add NB Both 2 way
Drive Test Report 16
HGNB06A 17831 23 HGNB04B 17612 237 Add NB Both 2 way HGNB10A 18251 35 HGNB04C 17613 238 Add NB Both 2 way HGNB10A 18251 35 HGNB03B 17462 329 Add NB Both 2 way HGNB10A 18251 35 STKS10B 60512 37 Add NB Both 2 way HGNB10A 18251 35 STKS07C 60013 47 Add NB Both 2 way HGNB10B 18252 36 STKS07C 60013 47 Add NB Both 2 way HGNB03B 17462 329 HGNB10A 18251 35 Add NB Both 2 way HGNB03B 17462 329 HGNB10B 18252 36 Add NB Both 2 way HGNB03B 17462 329 HGNB06A 17831 23 Add NB Both 2 way HGNB03B 17462 329 HGNB06C 17833 25 Add NB Both 2 way HGNB03C 17463 337 HGNB08A 18231 29 Add NB Both 2 way HGNB03C 17463 337 HGNB08C 18233 31 Add NB Both 2 way HGNB12A 18281 322 HGNB10C 18253 37 Add NB Both 2 way HGNB12B 18282 330 HGNB08A 18231 29 Add NB Both 2 way HGNB06A 17831 23 HGNB04B 17612 237 Add NB Both 2 way HGNB06A 17831 23 HGNB12A 18281 322 Add NB Both 2 way HGNB06A 17831 23 STKS07C 60013 47 Add NB Both 2 way HGNB06A 17831 23 STKS10B 60512 37 Add NB Both 2 way HGNB06C 17833 25 HGPH24A 17581 224 Add NB Both 2 way HGPH24A 17581 224 HGNB06C 17833 25 Add NB Both 2 way HGNB08A 18231 29 HGNB12A 18281 322 Add NB Both 2 way HGNB08A 18231 29 HGNB12B 18282 330 Add NB Both 2 way HGNB08A 18231 29 HGNB12C 18283 338 Add NB Both 2 way HGNB08A 18231 29 HGNB03B 17462 329 Add NB Both 2 way HGNB08A 18231 29 HGNB03C 17463 337 Add NB Both 2 way HGNB08A 18231 29 HGNB06C 17833 25 Add NB Both 2 way HGNB08B 18232 30 HGPH01A 17041 500 Add NB Both 2 way HGNB08B 18232 30 HGPH01B 17042 501 Add NB Both 2 way HGNB08B 18232 30 HGPH01C 17043 502 Add NB Both 2 way HGNB08B 18232 30 HGPH30A 18091 492 Add NB Both 2 way HGNB08B 18232 30 HGPH30B 18092 493 Add NB Both 2 way HGNB08C 18233 31 HGPH30A 18091 492 Add NB Both 2 way HGNB08C 18233 31 HGPH30B 18092 493 Add NB Both 2 way HGPH30A 18091 492 HGNB08B 18232 30 Add NB Both 2 way HGPH30B 18092 493 HGNB08B 18232 30 Add NB Both 2 way HGPH30A 18091 492 HGNB08C 18233 31 Add NB Both 2 way HGPH30B 18092 493 HGNB08C 18233 31 Add NB Both 2 way HGNB08C 18233 31 HGPH15B 17342 430 Add NB Both 2 way HGNB08C 18233 31 HGNB05B 17512 287 Add NB Both 2 way HGNB08C 18233 31 HGNB05C 17513 280 Add NB Both 2 way HGNB08C 18233 31 HGNB03C 17463 337 Add NB Both 2 way HGPH31B 18102 27 HGPH40B 18162 201 Add NB Both 2 way HGPH31B 18102 27 HGPH05C 17453 390 Add NB Both 2 way HGCT04C 17473 111 HGNB04A 17611 232 Add NB Both 2 way HGNB04A 17611 232 HGCT04C 17473 111 Add NB Both 2 way
Drive Test Report 17
4. DATABASE PARAMETERS CHECK AND OPTIMIZATION RECOMMENDED This part of the document shows the main parameters for optimization purpose. Its also recommended to check the lastest release of the WCDMA RAS_XX Parameter Dictionary from system documentation.
Its also recommended to create a database change control procedure, including that, for any parameter change, it has to be approved, documented and the effect verified afterwards. Any parameters not described here should not be changed, and always follows the recommended ones. 4.1. PARAMETER GROUPS IN RNC DATABASE: All the parameters in the database are organized in groups. There are some specific effects in changing parameters regarding this kind of organization. The groups and the effects are described below: RNC: these parameters controls all procedures in an RNC level, which means that all cells, users, calls, NodeBs, etc. will be affected by change these kind of parameter. COCO: these parameters refer to Connection Configuration in the RNC. WANE and WGS: these parameters are related to IMSI based HO. WLCSE and WSMLC: these parameters are related to Location Based Services. WBTS: these parameters are related to the NodeB configuration. Changing parameters in this group will affect all WCELs related to this WBTS. WCEL: these parameters are related to the cells configuration in the NodeB. FMCSF, MCI and FMCG: these parameters are related to Frequency Measurements for Intra-System, Inter-Frequency and Inter-RAT (GSM) Handovers respectively. It configures the UE to how /when do the measurements for RNC HO decision. These parameters are sent to UE via BCCH SIB messages and DCH Measurement Control Messages. FMCxs objects are created in the RNC and then associated to the WCELs, which means that changing FMCxs parameters Will affect all WCELs associated to them. There are 8 FMCxs defaults values created in the database depending on service type and NodeB output power: RT_40W, NRT_40W, HSDPA_40W, RT_HSDPA_40W, RT_20W, NRT_20W, HSDPA_20W and RT_HSDPA_20W. Its possible to created new FMCxs, and the parameters have to be analyzed and approved by the Parameter Experts. ADJS, ADJI and ADJG: these are the neighbour relations between the NodeB cells for Intra-System Handovers, Inter-Frequency Handovers and Inter-RAT Handovers (GSM) respectively. HOPS, HOPI and HOPG: these parameters are related to Handover Paths. They are used for configuring the UE for Cell Reselection procedures and used by RNC for Handover decisions for Intra-System, Inter-Frequency and Inter-RAT (GSM) neighbours respectively. These parameters are sent to UE via BCCH SIB messages. HOPxs objects are created in the RNC and then associated to the ADJxs, which means that changing HOPxs parameters
Drive Test Report 18
will affect all ADJxs associated to them. There are 4 HOPxs defaults values created in the database depending on service type: RT, NRT, HSDPA and RT_HSDPA. Its possible to created new HOPxs, and the parameters have to be analyzed and approved by the Parameter Experts. Pls be noted that each modification should be evaluated on a case-by-case basis, taking into account the local environnement and target network configuration
4.2. PARAMETER GROUPS IN CATEGORIZE Idle more WCDMA/GSM parameters Mobility o Soft HO Parameters o Inter-System handover parameters o Inter-Frequency handover parameters RRM o Admission control parameters o Packet Scheduling parameters o Telecom Parameters o Power Control parameters HSDPA (RAS05 onwards) and HSUPA (RAS06 onwards) parameters It is possible to view/modify all listed 3G parameters using RNC RNW Object Browser. There are also some GSM parameters which have to be modified from BSC (MML commands). 3G network topology is varying a lot which means that the radio network optimization activities will be needed anyway to improve the radio network performance. Thus these parameters are only better defaults to start the optimization
4.3. IDLE MODE PARAMETERS 4.3.1. Idle Mode WCDMA Parameters Idle mode parameters should be optimized to improve the call setup success rate. Parameter Object Default values Optimized values Comments
Drive Test Report 19
QqualMin WCEL -18dB -18dB The minimum required quality level in the cell (Ec/No) for UE cell reselection. This parameter has also impact to initial cell selection if its set with low value. With high value unnecessary cell selection can start. This parameter is sent to UE over the BCCH SIB messages. QrxlevMin WCEL -115dBm -115dBm The minimum required RX level in the cell (RSCP) for UE cell reselection. This parameter is also used to create value for the parameter DeltaQrxlevmin to be sent in SIB3/4 when the used value is < - 115dBm. This parameter is sent to UE over the BCCH SIB messages. Qhyst2 (Cell resection hysteresis 2) WCEL 2 dB
4 dB
2 dB
0 dB 4dB for WCDMA cells near different LA can be used to avoide ping-pong effect and also for low mobility UEs unless compensated by AdjsQoffset2 (per adj)
2 dB hysteresis between WCDMA cells can be used in Urban environment to avoid ping pong. 2dB (or less) enables faster cell reselection, which can contribute to improve HSDPA accessability.
0 dB hysteresis can be used in the area of high mobility.
Cell reselection triggering time (Treselection) WCEL 2 s
2 s
0 s 2s reselection time helps avoid too many cell reselections between cells and hence LA/RA updates when crossing LA/RA border. Thus there are less signaling and less call failures at LA/RA border due to LA/RA update. 0s can be used in areas having high mobility like in highways.
Drive Test Report 20
AdjsQoffset1 HOPS 0dB This parameter is used in the cell re-selection and ranking between WCDMA cells. The value of this parameter is subtracted from the measured CPICH RSCP of the neighbour cell before the UE compares the quality measure with the cell re-selection/ranking criteria. AdjsQoffset2 HOPS 0dB This parameter is used in the cell re-selection and ranking between WCDMA cells. The value of this parameter is subtracted from the measured CPICH RSCP of the neighbour cell before the UE compares the quality measure with the cell re-selection/ranking criteria. AdjsQqualMin HOPS -18dB Determines the minimum required CPICH Ec/No level which must be exceeded by the measurement result of the neighboring cell before the cell re-selection becomes possible. AdjsQrxlevMin HOPS -115dBm Determines the minimum required CPICH RSCP level which must be exceeded by the measurement result of the neighboring cell before the cell re-selection becomes possible
Drive Test Report 21
AdjgRxLevMinH O HOPG -95dBm This parameter determines the minimum required GSM RSSI level which the averaged RSSI value of the GSM neighbour cell must exceed before the coverage (or quality) reason handover to GSM is possible AdjgQrxlevMin HOPG -101dBm Determines the minimum required RSSI level which the measurement result of the GSM neighbour cell must exceed before the cell re-selection becomes possible AdjgQoffset1 HOPG 0dB This parameter is used in the cell re-selection and ranking between WCDMA and GSM cells. The value of this parameter is subtracted from the measured GSM carrier RSSI of the neighboring cell before the UE compares the quality measure with the cell re-selection/ ranking criteria AdjSSIB
AdjGSIB
AdjISIB ADJS
ADJG
ADJI 1
1
1 0
0
0 All the neighbour cells are included into syst em information block (SIB11/12) by default. The parameters are set by the system to the default value 1 (yes). The value must be set to 0 for marginally used adjacencies if the total amout of neighbours for a given cell exceeds the SIB11 limit (typically 47 adjacencies).
It is preferable to avoid removing intra-frequency adjancencies 4.3.2. Idle Mode GSM Parameters
Drive Test Report 22
Parameter Object Default Recommended value Comments MINIMUM FDD THRESHOLD (Fdd_Qmin)
BTS 0 (-20 dB)
-6..-10 dB
Should be balanced with QqualMin and SsearchRAT to reduce ping-pong. 6-8 dB hysteresis recommended (if Qqualmin+ SsearchRAT=-16, Fdd_Qmin= -8 dB,
Note: actual value based on UE interpretation. Non GPRS Multi RAT MS Qual (QsearchI) (GSM), QSRI
GPRS Multi RAT MS Qual (QsearchP) (GSM), QSRP BTS 15 (no meas) 7 (=always) UE will measure always 3G cells if they are defined neighbours. On the other hand this will have effect to the UE battery life time. Multi RAT MS Qual (QsearchC), QSRC HOC 15 (no meas) 7 (=always) If set to 15 Measurement Information (MI) is send anyway (even though UE should not measure 3G neighbours with that value 15), if ISHO_SUPPORT_IN_BSC or EMR_SUPPORT_IN_BSC features are used.
Note: In case ISHO_SUPPORT_IN_BSC or EMR_SUPPORT_IN_BSC features are used the paramet er values set with QSRI, QSRP or QSRC do not affect to the Measurement Info message and MI is always send by Mobile. This is valid in S10.5, S10.5 ED and S11. Only if both features are not used, MI info is not send.
4.4. SHO PARAMETERS Note: From RAS05 onwards, the default system value for FMCS parameters is equivalent to the optimal recommendation. However in there are some modifications needed.
Drive Test Report 23
Several customers use 4 FMCS sets: for RT, NRT traffic, HSPA and AMR+ HSPA. RT traffic uses default set of values of (4,6,2) dB for (Addition, Drop and Replacement Window) values, respectively NRT traffic uses default set of values of (2.5,4,2) dB for (Addition, Drop and Replacement Window) values, respectively Parameter Object Default values Recommended values Comments DropreportingInterval FMCS 0.5s 1s This is to related to first observations about SRB blocking -> decrease signaling with this change ReplacementReporting Interval FMCS 0.5s 1s This is to related to first observations about SRB blocking -> decrease signaling with this change ReplacementWindow FMCS 2 dB 4-6 dB priorizes branch additions over branch deletions to enable fast addition of new cell and decrease call drop rate, Current default trigger setting of SHO event 1C causes plenty of events to be reported -> SRB blocking ReplacementTime FMCS 100ms 640ms SRB Blocking, see above.
4.5. INTER-SYSTEM HANDOVER PARAMETERS Parameter Object Default values Recommended values Comments GSM HO caused by CPICH Ec/No
FMCG Disabled Enabled GSM HO caused by CPICH RSCP
FMCG Disabled Enabled GSM HO caused by UE Tx Power FMCG Disabled Enabled
Drive Test Report 24
UE TX Power Filter Coefficient FMCG 10 ms 60 ms In case GSM HO caused by UE Tx Power is enabled. 10 ms, too short delay to trigger ISHO. Consider using longer period, at least 60 ms. GSM HO caused by DL DPCH TX Power FMCG Disabled Enabled Some Ues are performing ISHO under good RF conditions due to peaks of high BLER, so DL power should be enabled to avoid dropped call.
Maximum Measurement Period FMCG 6 measurement reports 12 measurement reports to 20 measurement reports ISHO delays of 5 s has been measured, also the delay depends on the length of neighbour list.
Decreases the probability for no cell found in ISHO.
6 is often too low in environment where 2G BCCH reuse is high. It is recommended to use at least 12. Handover of NRT PS Service to GSM RNC/H C&PC No Yes In case PS ISHO is activated FMCG needs to be added in cell parameter window.
Drive Test Report 25
Maximum Allowed UL User Bitrate in HHO WCEL 32 kbits/s
384 kbits/s
Used only with high UE TX power level (RT&NRT) or bad uplink DCH quality triggers.
In case of bad uplink DCH quality, the bitrate threshold concerns only RT data (CS or PS) connections.
This parameter value should be aligned with MaxBitRateULPSNRT, which is by default 384 kbits/s in RAN04 / RAS05.
The RNC is not aware of which TF the UE is using. CPICH Ec/No HHO Threshold, CPICH Ec/No HHO Cancel, CPICH RSCP HHO Threshold, CPICH RSCP HHO Cancel for NRT Services FMCS NRT, FMCS HSDPA -12dB, -9dB, -105dBm, -102dBm -16..-18 dB, -12..-14 dB, -115dBm, -110dBm Lower values for for NRT services to increase the coverage area, valid for HSDPA also.
Due the signalling delays at inter-system change caused by LU and RAU, and due to the low bit rate available in GPRS network without EDGE, it is beneficial to leave UMTS as late as possible CPICH Ec/No HHO Threshold, CPICH Ec/No HHO Cancel, CPICH RSCP HHO Threshold, CPICH RSCP HHO Cancel for NRT Services FMCS RT -12dB, -9dB, -105dBm, -102dBm -14..-16 dB -10..-12 dB -108..-110 dBm -105..-18 dBm Lower values for RT to have more coverage. Absolute Isho number (and ISHO) drops will be decreased.
Drive Test Report 26
DedicatedMeasReportPeri od WBTS 2.5 s 0.5 s This parameter determines the reporting interval that Node B should use (by default, when initialized) for sending dedicated measurement reports to the RNC related the power on DCH channel. When ISHO Downlink Link Power trigger is in use, reducing this parameter to 0.5 seconds allows faster ISHO and can help reduce drop rate. Requires cell locking prior to change.
FMCI Disabled Enabled IFHO caused by UE TxPower FMCI Disabled Enabled UE TX Power Filter Coefficient FMCI 10 ms 60 ms In case IFHO caused by UE Tx Power is enabled (see above). 10 ms, too short delay to trigger IFHO. Consider using longer period, at least 60 ms. Maximum Measurement Period FMCI 20 meas report
12 meas report This should be in line with ISHO delay.
Drive Test Report 27
4.7. POWER CONTROL PARAMETERS Parameter Object Default Recommended value Comments PtxPrimaryCPICH WCEL 33dB 20W 36dB -40W This is the transmission power of the primary common pilot channel and its defined as 10% of the total NodeB Tx Power. . For 20W NodeB is configured as 33dBm, and for 40W NodeB is configured as 36dBm. The P-CPICH physical channel carries the common pilots of the cell, which is defined in the cell setup. The transmission power of the CPICH physical channel defines the actual cell size, so for optimization purpose like solving Pilot Pollution problems and CPICH Imbalance problems this parameter could be changed 0-3dB maximum range. This parameter is used, for example, for neighbour measurements, critical for the network performance. All other control and signaling channels transmission power parameters are related to PtxPrimaryCPICH. CPICHtoRefRABoffset (Offset of the P-CPICH and reference service powers) WCEL 2 dB 0 dB
-1-2 dB (with high HSDPA traffic) This change means that the maximum link power for a connection is increased by 2 dB to improve the DL coverage. This change means also that the minimum power is increased as well (as the minimum power is Max power DL PC Range) which might lead to the situation where too high powers are allocated even in the good coverage conditions as a result power is wasted.
Drive Test Report 28
With high HSDPA traffic the increased interference will decrease the EcNo level, which could mean increased peak power for AMR, thus max radio link power for AMR should be increased also. PcrangeDL (Radio link downlink power control range) RNC 15 dB 20 dB
This change is needed to compesate the increase of CPICHtoRefRABoffset mentioned above. 21-22 dB can be used with negative CPICHtoRefRABOffset Required received C/I on PRACH at WCDMA BTS WCEL -25 dB -20..-18 dB With increased traffic and the fluctuation of noise levels the default value -25 just leads to unnecessary unanswered RRC connections or pages i.e. no response from BTS to RRC Connection Request (i.e. no AICH). This can be avoided by adjusting the parameter to - 20dB. This has not any negative impact such as increased noise level or spikes.
(Time supervision of user inactivity (for NRT RBs)) RNC 29 min 15 min MSActivitySupervision timer is used in Cell_PCH state for supervising the inactivity of NRT RAB(s). If the parameter value is set to zero: state transition to Cell_PCH is not allowed when inactivity is detected in Cell_FACH state and the MS will be switched to the Idle Mode.
Drive Test Report 29
PtxDLabsMax (Planned maximum downlink transmission power of a radio link) WCEL 37 dBm 35-37 dBm This parameter is related to the Dynamic Link Optimization feature. It will limit the planned maximum limit for the radio link.
Bitrate downgrade due to DyLo happens if the current link power is 2 dB (fixed value) less than maximum link power. However with this parameter it is possible to optimize the NRT usage in different bitrates. The optimised value for PtxDLAbsMax is between 35- 37dBm based on the various measurements. Offset for activation time
StandAloneDCCHBitRate
RNC
RNC 300ms 500..700 ms
13.6kbps
The RB setup success is better with longer time in bad coverage areas. As Signalling Delay Improvement is implemented in RAS5, shorter Activation Time Offset can potentially be used. Configuring to 300ms would decrease the setup time by 400ms for each leg, but declines the Call Setup Success Rate of 0.2-0.4%. So in case this parameter is changed the effects to call setup time and call setup success rate has to be observed from counters.
For full improvement in call setup time the SRB size should be set to 13.6 kbps. SRB 13.6 gives approximately 1-2 sec faster call setup time and gives 30% faster GPRS attach time and PDP activation time than SRB 3.4, but also requires more capacity on Iub during
Drive Test Report 30
500 ms
the call setup phase
500 ms has been tested with success in some cases. Needs to be evaluated case-by-case based on Ue mix in network. Can impact Packet RAB drop rate and AMR/Video RAB setup success rate. MinAllowedBitRateDL/UL (Initial and minimum allowed bit rate in DL/UL) WCEL Uplink 8 kbit/s Downlink 8 kbit/s
UL/DL 8..32 kbit/s
Optionally consider using recommended values: UL/DL = 32/32 kbits/s. This is due to low throughput on FTP type of services by using TCP. If there are some TCP re- transmissions, these can cause large queue of TCP frames buffered in RLC and then pushed to higher layer. Since downlink TCP frames are received faster than feedback channel is able to transmits TCP acks, throughput will suffer. Initial bit rate in downlink/uplink WCEL 64 kbits/s
8 or 16 kbits/s In loaded networks it may be useful to use lower initial bitrates 4.9. TELECOM PARAMETERS Parameter Object Default Recommended value Comments Cell range WCEL Default value is not possible 10 km or 20 km
The maximum cell range can be 20 km when using two antennas and AICH Transmission Timing has value 1. If AICH Transmission Timing has value 0 or four antennas are used the maximum value can be 10 km.
Drive Test Report 31
PRACH Preamble Retrans Max WCEL 8 7 These parameters makes RACH procedure slightly longer, giving the BTS more time to catch the RACH, at the same time decreasing the maximum power used in PRACH power ramping. If this change is not made, there may be a risk for excessive peaks in the uplink cell load when operating at a high load (>40 AMR calls) RACH maximum number of preamble cycles WCEL 8 16 Wait Time RRC registration RNC 1s 5s The time indicates the how long UE shall wait before sending the same RRC connection request message to the same cell.This change means to decrease the number of RRC pollution, useful with high load cells also. Wait Time RRC interactive/background RNC 5s 8s This is similar to above indicating the RRC wait time due to NRT blocking. When AC has rejected call, PS is the lowest priority with the most consuming resource. Minimise the chance for NRT call to attempt is recommended.
T3212 RNC 0 decihours 6h The value depens how it is set in VLR/CN. It is recommended to be half of the value of VLR/CN. Default value in VLR is 12 h. T313 WCEL 3s 6-8s In some case, can reduce NRT call drop rate (in OSS KPI) by allowing more time before Ue sends Radio Link Failure indication. Note that end user experience is likely not improved.
Drive Test Report 32
N313 WCEL 20 50 In some case, can reduce NRT call drop rate (in OSS KPI) by allowing more time before Ue sends Radio Link Failure indication. Note that end user experience is likely not improved. T315 WCEL 4 (180 s) 1 (10 s) It has been observed that a few terminals were in some case unable to perform a 2G reselection before the expiry of timer T315. Reducing timer to 10s minimizes the impact while maintaining PS drop performance.
4.10. OTHERS PARAMETERS Parameter Object Default Recommended value Comments StandAloneDC CHBitRate (Signalling radio bearer bit rate at RRC connection establishment) RNC 34 (3.4 kbps), 136 (13.6 kbps) The parameter UsedSRBALCSet (Used SRB ALC set) allows to use StandAloneDCCHBitRate=13.6 kbit/s to reduce call setup delays without impact on Iub AAL capacity by defining an activity factor. Default value for UsedSRBALCSet is 3, which corresponds to an activity factor of 7.5% for a StandAloneDCCHBitRate of 13.6 kbps.
Parameter Object Default Recommended Value Comments DRRCprxMargin WCEL -0.5 dB 0 dB Directed RRC connection Setup parameter ; based on field measurements, target cell does not need to be at lower load in UL DRRCptxMargin WCEL - 2 dB -0.5 dB Directed RRC connection Setup parameter ; based on field measurements, easier access to another frequency especially in the case for 384 kbits/s service
Drive Test Report 33
NbrofSCCPCHs WCEL 1 3 3 is the value if Service Area Broadcast (SAB) is used NforCTCH WCEL 2 4 This value should be used here if NbrofSCCPCHs is 3. ConfAreaLevel WSMLC 0100% 67 % This is related to LCS (=location based services. There is no default value mentioned for this, but 67 % is given value from product line. Note: All other LCS parameters should be carefully set, for example all those Antenna related parameters, to have accurate LCS results.
4.11. HSPDA RELATED PARAMETERS 4.11.1. HSPDA Power Parameters The most important BTS power related parameters are summarized in the table below for 8, 20 and 40W PA per cell configuration. Target values are given with and without optional feature HSDPA Dynamic Resource Allocation. Default PtxCellMax 43 43 46 39 43 46 39 dBm 20.0 20.0 39.8 7.9 20.0 39.8 7.9 W PtxCPICH, dBm 33 33 36 29 33 36 29 dBm PtxTarget 40 42 45 38 42 45 38 dBm PtxTarget (in Watts) 10.0 15.8 31.6 6.3 15.8 31.6 6.3 W PtxOffset 1.0 0.8 0.8 0.8 0.8 0.8 0.8 dBm PtxTarget+PtxOffset (in Watts) 12.6 19.1 38.0 7.6 19.1 38.0 7.6 W Dynamic resource allocation (RAS06) PtxTargetPSMin 36 36 39 32 36 39 32 dBm PtxTargetPSMin (in Watts) 4.0 4.0 7.9 1.6 4.0 7.9 1.6 W PtxTargetPSMax 40 42 45 38 40 43 36 dBm PtxTargetPSMax (in Watts) 10.0 15.8 31.6 6.3 10.0 20.0 4.0 W Min. power available for HSDPA 10.0 4.1 8.2 1.6 10.0 19.9 4.0 W PtxHighHSDPAPwr 42 42.5 45.5 38.5 42 45 38 dBm PtxHighHSDPAPwr (in Watts) 15.8 17.8 35.5 7.1 15.8 31.6 6.3 W Dynamic Power allocation (RAS5.1-RAS06) PtxMaxHSDPA 38.5 42.0 45.0 38.0 42.0 45.0 38.0 dBm PtxMaxHSDPA (in Watts) 7.1 15.8 31.6 6.3 15.8 31.6 6.3 W PtxTargetHSDPA 37.8 40 43 37 40 43 37 dBm PtxTargetHSDPA (in Watts) 6.0 10.0 20.0 5.0 10.0 20.0 5.0 W PtxOffsetHSDPA 0.8 0.8 2 0.8 0.8 2 0.8 dBm PtxTargetHSDPA+PtxOffsetHSDPA (in Watts) 7.2 12.0 31.6 6.0 12.0 31.6 6.0 W Min. power available for HSDPA 7.1 7.9 8.2 1.9 7.9 8.2 1.9 W Shared HSDPA carrier Dedicated HSDPA carrier
Figure 1: Recommended HSDPA power setting for different PA powers.
Drive Test Report 34
Note 1. The full BTS Power Amplifier power can be allocated in downlink without margin, for optimal capacity performance. However, some operators privilege more conservative allocation. Parameter WCEL:PtxCellMax has a default value of 43 dBm, and it MUST be adapted to the BTS PAs. In case of Metrosite BTS, the value MUST be set to 39dBm (or less), as it will not be set automatically by the system. The same rule applies to Ultrasite and Flexi BTS with 40W PAs: the PtxCellMax value must be set to 46dBm to benefit from the full PA power range. In RU10 BTS link adaptation reduces HS-PDSCH power for low data rate users and users who are in good radio conditions.
Note2. PtxMaxHSDPA parameter in RAS06 does have an impact on Dynamic Resource allocation also, so it should be set higher value or even equal to PtxCellMax, to allow all left over power for HSDPA with DRA. If Dynamic Resouce Allocation feature is activated, default values for parameter PSPtxTargetPSMin and PSPtxTargetPSMax is 40dB and must be lowered in case of Metrosite BTS or Flexi 8W license to respect the maximal value for these configurations (39dBm). In case of Dedicated carrier configuration, RRC layering must be activated. 4.11.2. HSPDA Dynamic Code Allocation Parameter Object Default Recommended Value Comments HSPDSCHMarginSF128
WCEL 8 0-4
This parameter will be used only with HSDPA 10 or 15 code feature. The parameter defines the required number of free SF128 channelisation codes left for DPCHs. The number of free DPCH codes after the HS- PDSCH code upgrade has to be equal or higher than the parameter value, otherwise the HS-PDSCH code upgrade is not allowed. Also, if the number of free DPCH codes is lower than the value of the parameter, periodical HS-PDSCH code downgrade can be initiated.
Minimum margin of 5 SF128 codes allows the allocation of up to 14 HS-PDSCH codes.
Drive Test Report 35
HSUPA + 15 codes is possible with value 0 and with 2 HS- SCCH. If HSPA with high throughput is favoured instead of PS NRT value 0 can be used. DPCHOverHSPDSCHThreshold
WCEL 0 1-4 NRT DCH connections can pre- empt codes allocated to HSDPA but in this case, the pre-emption can happen in case there is room in codes: # HS-PDSCH codes > Maximum code set- DPCHOverHSPDSCHThreshold parameter. This parameter is applied if there are active HSDPA connections in the cell. If this is set to zero thre will be more RRC setups with RT over NRT pre-emption which causes then BTS to be frozen and during the pre-emption all new requests to be queued which in turn can cause some delays to RRC setups and queue overflow and therefore rejections.
HSPDSCHAdjustPeriod RNC 10s 5s Faster adjustement period allows faster code allocation to HSDPA users.
4.11.3. Other Recommended HSDPA Parameters Parameter Object Default Recommended Value Comments HSDPARRCdiversity (SHO of HSDPA capable UE) RNC Allowed Not allowed Only if HSDPA Serving Cell Change is disabled. When Not Allowed, parameters ReleaseMarginAverageEcNo and ReleaseMarginPeakEcNo are used to
Drive Test Report 36
define threshold for neighbouring cell to be added in to active set while having only SRB AdditionTime FMCS (HSDPA Id) 6 (100ms) 13 (1280ms) Only if HSDPA Serving Cell Change is disabled. AdditionWindow FMCS (HSDPA Id)
2.5 dB
0 dB
If HSDPA Serving Cell Change is enabled, it is beneficial to delay the measurement report in order to maintain HSDPA service longer. Also due to capacity reasons it is recommended to set window as 0 dB to to save BTS WSPC capacity in the target cell. This does not have impact to the HSDPA throughput degradation during SCC. EnableRRCRelease HOPS (HSDPA Id) 0 (No) 1 (Yes) With this parameter (with HSDPA on also) it is possible to see PS dropped calls due to BTS: lack of WSPC CE. ReleaseMarginAverageE cNo HOPS (HSDPA Id) 2.5dB 2dB This set will allow shorter time before RRC release: WSPC CE savings. DynUsageHSDPAReturn Channel RNC 0 (Disabled) 1 (Enabled) In case of high UL Channel Element usage, it is recommended to allow the use of ThroughputBasedOptimization for the HSDPA UL return channel. Note that both Throughput Based Optimization and Flexible Uprade features need to be enabled. HSDPA16KBPSReturnCh annel
RNC 0 (disabled) 1 (Enabled) This parameter change will improve HSPDA accessibility and maintain the RAB with lower throughput (RB downgrade) without releasing it in case of capacity problems. Initial bitrate for HSDPA associated UL DCH RNC 64 kbits/s 16 kbits/s In loaded networks it is recommended to use lower Initial bitrate in order to save capacity. HSDPAminAllowedBitrate U RNC 64 kbits/s 16 kbits/s In loaded networks it is recommended to use lower Initial bitrate in order to save capacity. MaxBitRateNRTMACDFl ow RNC 3456 kbps 3456kbps For basic HSDPA 5 Codes (QPSK/16QAM),
Drive Test Report 37
6784kbps 9600 kbps MaxBitRateNRTMACDFlow=3456kbps For basic HSDPA 10/15 Codes, MaxBitRateNRTMACDFlow=6784kbps For HSDPA 10Mbps per User, MaxBitRateNRTMACDFlow=9600 kbps. Code Tree Usage WCEL 40 % 60 % This is the default without HSDPA feature. With HSDPA enabled in the cell the code tree usage is already about 38 %. The recommendation is to use 60 %. AM RLC maxRST transmissions for PS NRT with HS-DSCH (the amount of RESET PDUs)
RNC 12 24 This parameter defines the value of the RLC protocol parameter MaxRST for the AM RLC entity of the PS interactive and background radio bearers when data is transferred over HS-DSCH. It has been hidden parameter before RAS06. The change will have less RL failures and improved HSDPA retainability.
RLC unrecoverable error with new settings = 15*300ms+24*300ms = 11.7s RLC unrecoverable error with old settings = 15*200ms+12*200ms = 5.4s
The reason for increasing the timer values for PS NRT is to reduce the propability that the RLC does the unrecoverable error due to the retransmissions by reducing the RLC polling frequency.
AM RLC status period max for PS NRT with HS- DSCH (periodic polling and reset polling repeat interval from 200 to 300ms) RNC 133 % 300 % This parameter defines the maximum status reporting period of the AM RLC in relation to the RLC round trip time for the PS interactive and background radio bearers when the data is transferred over HS-DSCH. It has been hidden parameter before RAS06.
Drive Test Report 38
The change will have less RL failures and improved HSDPA retainability. AM RLC status period max for PS NRT with DCH (periodic polling and reset polling repeat interval from 200- >300/400/500 ms depending on TTI length, 300ms in HSDPA return channel case)
RNC 140 % 300 % This parameter defines the maximum AM RLC status reporting period of the AM RLC in relation to the RLC round trip time for the PS interactive and background radio bearers when data is transferred with DCH. Hidden parameter before RAS06. AM RLC MaxRST transmissions for PS NRT with DCH (the amount of RESET PDUs)
RNC 12 24 This parameter defines the value of the RLC protocol parameter MaxRST for the AM RLC entity of the PS interactive and background radio bearers when data is transferred with DCH. Hidden parameter before RAS06. AM RLC maxRST transmissions for PS NRT with E-DCH RNC 12 24 RLC parameter for HSUPA AM RLC status period max for PS NRT with E- DCH RNC 133 % 300 % RLC parameter for HSUPA
4.11.4. Recommended HSUPA Parameters Parameter Object Default Recommended Value Comments MaxTotalUplinkSymbolRa te WCEL 1920 kbps 3840 kbps In case HSUPA2.0 is used FactorEDCHMaxBitRate RNC 1.5 5 In case HSUPA2.0 is used, to avoid having HLR as limiting factor in HSUPA throughput NumberEDCHReservedS HOBranchAdditions WCEL 2 0-1 With default of 2 used with 3 HSUPA license only it is not possible to have more than one HSUPA connection in the cell in case of HSUPA SHO.
Drive Test Report 39
Delay ThresholdMax RNC 8 ms 100 ms HSUPA cong. Control. Delay ThresholdMid RNC 4 ms 70 ms HSUPA cong. Control. Delay ThresholdMin RNC 1 ms 50 ms HSUPA cong. Control. ProbabilityFactorMax RNC 0.8 0.1 HSUPA cong. Control.
5. NETWORK DRIVE TEST RESULT BEFORE AND AFTER OPTIMIZATION 5.1. NETWORK PERFORMANCE OVERVIEW BEFORE AND AFTER OPTIMIZATION Table below summarizes main drive test KPIs for Hau Giang province before and after optimization activities ITEMS BEFORE AFTER STATISTICS DATA #Call Attempts 2224 1467 #Call Setup Successes 2203 1463 #Dropped Calls 17 1 KPI BEFORE AFTER CSSR(%) 99.06% 99.73% DCR(%) 0.77% 0.07% MOS 3.16 3.52 PILOT POLLUTION (COUNT >=4) 5.59% 5.52% RSCP Scan (dBm) -85.69 -73.88 RSCP Shortcall (dBm) -86.16 -84.00 EcIo Scan (dBm) -7.11 -6.93 EcIo Shortcall (dBm) -5.63 -5.77 HSDPA (Kbit/s) 3010 3002 HSUPA (Kbit/s) 619 916 PING (ms) 200 197
Drive Test Report 40
5.2. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM SCANNER 5.2.1. RSCP Scan distribution result before and after optimization
Scan RSCP Before After Average Coverage (dBm) -85.69 -72.65 5.2.2. RSCP Scan Coverage plot result before and after optimization
RSCP Scan before
Drive Test Report 41
RSCP Scan After
5.2.3. EcIo Scan distribution result before and after optimization
Scan EcIo Before After Average Coverage (dBm) -7.11 -6.9
Drive Test Report 42
5.2.4. EcIo Scan Coverage plot result before and after optimization
EcIo Scan before
EcIo Scan After
Drive Test Report 43
5.2.5. Pilot Polution Scan distribution result before and after optimization
Pilot Pollution Before After Pilot Pollution count >=4 5.59% 5.52%
5.2.6. Pilot Polution Scan result before and after optimization
Drive Test Report 44
Pilot Polution before
Pilot Polution After 5.3. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM SHORT CALL 5.3.1. RSCP shortcall distribution result before and after optimization
ShortCall RSCP Before After Average Coverage (dBm) -86.16 -84
Drive Test Report 45
5.3.2. RSCP shortcall coverage plot result before and after optimization
RSCP Shortcall before
RSCP Shortcall After
Drive Test Report 46
5.3.3. EcIo shortcall distribution result before and after optimization
ShortCall EcIo Before After Average Coverage (dBm) -5.63 -5.77
5.3.4. EcIo shortcall coverage plot result before and after optimization
EcIo Shortcall before
Drive Test Report 47
EcIo Shortcall After 5.4. NETWORK COVERAGE BEFORE AND AFTER OPTIMIZATION FROM IDLE MODE 5.4.1. RSCP Idle distribution result before and after optimization
Idle RSCP Before After Average Coverage (dBm) -86.21 -81.82
Drive Test Report 48
5.4.2. RSCP Idle coverage plot result before and after optimization
RSCP Idle Before
RSCP Idle After
Drive Test Report 49
5.4.3. EcIo Idle distribution result before and after optimization
Idle EcIo Before After Average Coverage (dBm) -5.67 5.7
5.4.4. EcIo Idle coverage plot result before and after optimization
EcIo Idle Before
Drive Test Report 50
EcIo Idle After
5.5. NETWORK SPEECH QUALITY MOS BEFORE AND AFTER OPTIMIZATION 5.5.1. MOS distribution result before and after optimization
MOS Before After Speech Quality 3.16 3.52
Drive Test Report 51
5.5.2. MOS coverage plot result before and after optimization
Speech Quality MOS before
Speech Quality MOS After
Drive Test Report 52
5.6. DATA THROUGHPUT BEFORE AND AFTER OPTIMIZATION 5.6.1. HSDPA coverage plot result before and after optimization
HSDPA Throughput Before
HSDPA Throughput After
Drive Test Report 53
5.6.2. HSUPA coverage plot result before and after optimization
HSUPA Throughput Before
HSUPA Throughput After
Drive Test Report 54
5.6.3. PING coverage plot result before and after optimization
PING Time delay Before
PING Time delay After
Drive Test Report 55
6. CONCLUSION AND RECOMMENDATION The result has indicated that network KPIs are improved significantly,however there are some areas need to add more 3G sites to improve network coverage,capacity and data throughput.The detail sites name and location is summarized in figure below.These areas had already 2G sites installed. STT TN TRM ID TNH QUN/HUYN X/PHN G/TH TRN LONG LAT 11 11 11 11 11 11 11 11 1 HG Ci Tc 3 HGCA03 Hu Giang Chu Thnh A Ci Tc 105.72584 9.92432 2 HG Chu Thnh A HGCA04 Hu Giang Chu Thnh A Mt ngn 105.63409 9.92165 3 Hu Giang 87 HGCA15 Hu Giang Chu Thnh A Tn Ph Thnh 105.73108 9.94604 4 Hu Giang 95 HGCA16 Hu Giang Chu Thnh A Tn Phc Thnh 105.72021 9.92373 5 HG Long Bnh HGLM05 Hu Giang Long M Long Bnh 105.57704 9.73863 6 HG Ng By 1 HGNB01 Hu Giang Ng By Li Hiu 105.81017 9.80585 7 Hu Giang 157 HGNB14 Hu Giang Ng By Hip Li 105.78732 9.84835 8 HG Tn Long 2 HGPH12 Hu Giang Phng Hip Tn Long 105.76601 9.88304 9 HG V Thanh 8 HGVT08 Hu Giang TP.V Thanh Phng 3 105.46001 9.77503 10 HG Hu Giang 97 HGCA17 Hu Giang Chu Thnh A Tn Thun 105.60487 9.90286 11 HG Hu Giang 151 NGNB09 Hu Giang TX Ng By Phng Ng By 105.82861 9.80847