Globacom Cluster Drive Drive

Globacom Cluster Drive
Drive Test Evaluation
(BENIN CLUSTER D 2G PRE DT)
Signed by NERA Date Date Signed by Globacom Date Date Date Date

Cluster Test Date
BENIN SUB CLUSTER D 2014-09-03

Table of Content

1.0 Overview……………………………………………………………………………………………………………………………………2
1.1 Network Description ………………………………………………………………………………………………………………..5
1.2 Test Methods ………………………………………………………………………………………………………………………..5
1.3 Test Tools ……………………………………………………………………………………………………………………………5
1.4 KPI for DT …………………………………………………………………………………………………………………………..5
2.0 DT Test Results …………………………………………………………………………………………………………………………….6
2.1 BENIN Cluster D ……………………………………………………………………………………………………………………6
2.1.1a Test Route ……………………………………………………………………………………………………………………6
2.1.1b Test Route on Google Earth……………………………………………………………………………………………….6
2.1.2a Signal Strength Plot…………………………………………………………………………………………………………8
2.1.2b Signal Strength Chart………………………………………………………………………………………………………8
2.1.3a Voice Quality Plot…………………………………………………………………………………………………………..11
2.1.3b Voice Quality Chart…………………………………………………………………………………………………………8
2.1.4 Speech Quality Index Plot………………………………………………………………………………………………….14
2.1.5 BCCH Distribution Plot……………………………………………………………………………………………………..16
2.1.6 DT Events Summary Table…………………………………………………………………………………………………18
2.2 Network Issues Analysis…………………………………………………………………………………………………………..19
2.3 Network Issues Analysis Summary ……………………………………………………………………………………………..22
3.0 Conclusion …………………………………………………………………………………………………………………………………24
5.1 Events statistics of BENIN CLUSTER D …………………………………………………………………………………………24
5.2 Coverage statistics of BENIN CLUSTER D …………………………………………………………………………………….24

1 Overview
1.1 Network Description
BENIN CLUSTER D Network Distribution

SUB CLUSTER

GOOGLE SNAP SHOT

1.2
Test Methods
Vehicle test environment: The test mobile phone was installed in the vehicle, and the self-attached antenna was used at a height of about 1.5 m. Urban areas: The vehicle velocity is controlled with 40 km/h; Suburb area: The vehicle velocity is controlled with 50 km/h.
Test Sequence is as follows;
MS1: 2G locked, idle mode
MS2: 2G locked, dedicated mode: short call 120 sec with 10 sec interval
MS3: 2G locked, dedicated mode, long call 600 sec with 10 sec interval.

1.3 Test Tools
> Test instruments
Laptop, Test Terminal: Sony Ericsson C702, GPS
> Test Data Collection Tool
TEMS Investigation Data Collection, Version 11.0.4
> Post Processing Tool
TEMS Investigation Route Analysis Version 15.2, MapInfo Professional Version 8.5

1.4 KPI for DT
Basically KPI for DT should include the following items:
> Call setup failure statistics and analysis, and a conclusion;
> Call drop statistics and analysis, and a conclusion;
> Handover success rate statistics and analysis, and a conclusion;
> Signal Strength, statistics and analysis, and a conclusion;
> Voice Quality, statistics and analysis, and a conclusion;
> Cell Plot, shows the serving cells along the route of DT;
> Issues of weak Coverage, bad Quality, handover failure, overshooting;
2
DT Test Results
2.1 BENIN CLUSTER D
2.1.1 Test Route

SUB CLUSTER

2.1.2
Signal Strength

SUB CLUSTER

 
Signal Strength bar chart by Ranges

2.1.3

SUB CLUSTER
Voice Quality Bar Chart by Ranges

2.1.4
SQI DISTRIBUTION

SUB CLUSTER

2.1.5
BCCH Distribution

SUB CLUSTER

2.1.6 DT Events Summary Table

Event Name PRE-MS2 (Dedicated 2G Mode) POST-MS2 (Dedicated 2G Mode) Call Attempt 86 Blocked Call 35 %BCR 40.70% Call Setup 69 % CSSR (Accessibility) Call Established 69 %Call Established 1 Call End 45 % Good Call (Retainability) 65.22% Dropped Call 21 %DCR 30.43% Cell Reselection 29 Handover 950 Handover failure 36 %HOSR 96.35% Location Area Update 16 Location Area Update Failure 0
2.2 Network Issues Analysis
Case 1: Poor Coverage

Analysis: Dropped call due to suspected hardware issue on CI 50683..
RECOMMENDATION: Perform hardware recovery action.

Case 2: Dropped/Blocked call on BEN129_S3

Analysis: Dropped/Blocked on BEN129_S3 as a result of Hardware issue/Alarm.
RECOMMENDATION: Check BEN129_S3 for Alarm/hardware failure because it has good network coverage at time of event error.

Case 3: Hardware Issue/Alarm

Analysis: Blocked call due to No Traffic Channel Assignment.
RECOMMENDATION: Investigate CI: 52284 “BCCH:587” further in the OSS(TCH/SD Congestion). Bring up planned site in the event location.

Case 4: Inactive site

Analysis: Dropped call due to poor coverage on an inactive site area.
RECOMMENDATION: Bring up BEN044 ASAP to resolve network issue in the event location.

Case 5: No service

Analysis: Blocked call as a result of No service in the event location.
RECOMMENDATION: Bring up new site in the event location.

Case 6: Poor coverage

Analysis: Blocked/Dropped call as a result of poor coverage.
RECOMMENDATION: Bring up a new site in the event location because serving cell is far from the event and no site in the location.
4.0 Network Issues Analysis Summary
S/N Problem SITES IN AREA PROBLEM DESCRIPTION RECOMMENDATION 1 Dropped Call 50683 Poor coverage Investigate CI: 50683 “BCCH: 606” for Hardware Failure. 2 Dropped/Blocked Call BEN129_S3 Hardware issue/Alarm Check BEN129_S3 for Alarm/hardware failure because it has good network coverage at time of event error. 3 Blocked Call 52284 No Traffic Channel Assignment Investigate CI: 52284 “BCCH:587” further in the OSS(TCH/SD Congestion). Bring up planned site in the event location.. 4 Dropped Call BEN044 Inactive site Bring up BEN044 ASAP to resolve network issue in the event location 5 Dropped Call No service Bring up planned site in the event location. 6 Blocked/Dropped Call Poor coverage Bring up a new site in the event location because serving cell is far from the event and no site in the location.

5.0 CONCLUSION

5.1 Events statistics of Benin Cluster D

Handover Total Handover Success Handover Failure Call Attempt Call Setup Blocked Call Dropped Call Count 950 914 36 86 69 35 21 Rate 96.21% 80.23% 30.43%
5.2Coverage statistics of Benin Cluster D 2G PRE DT

Cluster Rx Level Sub >= -85dBm Rx Quality sub < 4 D 68.1% 63.5%
Fair network performances on CLUSTER_D RNC but poor KPI, major problems in this cluster are Hardware Failure/Alarms, Inactive site and poor network coverage on this cluster. Also need planned sites in listed location. Once resolved, the network performance will greatly improve.

A2