New BTS Site Integration
Drive Test Procedure & Guidelines
Prepared By:
Table of contents
Procedure Summary ... 3
1. Drive test preparation ... 4
2. Drive test ... 5
3. Drive test report... 8
Procedure Summary
The purpose of this document is to define the process flow and the drive test procedures to be followed by Huawei & Sub-Con DT and RF engineers to verify the functionality of the new sites in the rollout of WARID telecommunications network as part of the New Site Integration Process. A high level block diagram of the steps to be followed on this Drive Test Process is shown in Figure 1.
Figure 1: Drive Test Process– Steps Overview
The steps defined for this process are described below:
1. Drive test preparation
Prepare the test equipment (hardware and software) for the measurements. 2. Drive test
Actual drive test. 3. Data post processing
Post processing activities (logs post-processing, compile, filter, export to Mapinfo tables, etc).
4. Drive test report
Drive Test Report production for the site.
1 Drive test preparation 2 Drive test 3 Data post processing 4 Drive test report
DT Report Completed –
Submit for Approval
1. Drive test preparation
Some preparation activities must be initially performed in order to set up the testing equipment. This step will prepare the test equipment and set the software and hardware details for the measurements. The DT check list must be completed during this DT stage and delivered with the drive test report.
1.1 Expected results
The measurement system is set and all test cases are set The measurement team is ready for the drive test
1.2 Procedure
The drive test engineer shall use a map of the area to be driven with a “marked” route that will be provided by Huawei RF engineers, so that each site is driven thoroughly in the amount of time given. DT engineer will emphasize on the site’s coverage objective (town, village, major roads, etc).
He shall then make sure that all equipment are ready:
1. DC to AC Inverter
2. laptop with TEMS software 3. laptop power adaptor 4. TEMS dongle
5. Latest BTS/ CELL file for TEMS, which will be provided time to time from Huawei RF engineers.
6. USB hub 7. GPS receiver
8. Car cigarette lighter extension cable for phone chargers and GPS 9. TEMS test mobiles
10. USB data cables to mobiles
11. Test mobile battery chargers or a full charged backup battery per mobile
He shall make sure that TEMS mobiles are connected on hub holders and placed on the car’s dashboard.
To consider this activity completed the following deliverables must be produced: List of constrains related to this activity (if any)
The DT check list [Annex 01] must be completed The measurement team is ready for the drive test
2. Drive test
This step will perform the actual drive test defined for the site under test. Each drive test must be clearly documented. Additionally, the time of the drive test activity must be
synchronised with the RF Engineers and OMC Engineers of Huawei, so that each
drive test data set collected can be correlated with the OMC statistics in order to produce KPI snapshots.
2.1 Expected results
The drive test has been completed as planned Any issues have been documented and reported
2.2 Procedure
All test calls should be terminated to a test number. Test number should be of Warid. The drive testing scripts should be configured to provide the following test sequences:
1. MS1: configured to run on dedicated mode one continuous test call (Short calls of duration of 120 seconds. Establish the short calls as per the DT route; mean DT engineer will establish the new short call after every 120 seconds). If the call is dropped during 120 seconds the DT engineer should re-establish a new call immediately.
2. MS2: configured to run on idle mode throughout the drive test.
should coordinate with the OMC shift engineer and the DT coordinator to unlock the site.
Prior to this test, PCU, SGSN and other GPRS connectivity network elements have to be verified that are working.
During the drive tests the engineer should ensure that there are no swapped (crossed) sectors problems, all neighbours declared in the CDD are present and all RF
frequencies given are correct.
During the drive tests the DT engineer should note all major events (drop calls,
blocked calls, handover failures) and shall identify their main causes. He must have to mention the Layer 3 cause value in the report because of which the event occurred (See the report format).
To avoid the Re-drive, during the Test, if the DT engineer will find the following issues then at the same time, he must inform the DT coordinator so the DT
coordinator will inform the RF engineers so they can resolve the issue at the same time.
Handover failures, without the reason of timer expiry. Call establishment problems
Neighbour missing Call drops Blocked calls Sector swap Bad C/I Bad RX quality
Bad Rx Levels in idle mode
Intra Cell Handovers, Intra Band Handovers & Inter cell handovers problems. Call is not camping over TCH, means call is camping over BCCH only. Ping Pong Handovers means too many handovers at any interval or on whole
cell or site.
Upon completion of the DT activity the DT engineer should verify that all log files are not corrupted. In case of any log file problems the DT team should repeat the test immediately. Finally he should report to the DT coordinator the successful
completion of the drive test.
Due to the file size, upon completion of DT, DT engineer will export the log files after merging them and then plot the RX level idle and RX quality plot over Mapinfo and send it to the DT coordinator so he will ensure that there is no problem over the site regarding to sectors swap and bad quality. If DT coordinator will find any issues or not sure about that, then he must inform the RF engineer of Huawei.
Drive Test Types & Acceptance Details Sites with Urban Objective
– Radius of area to collect data for acceptance procedure: 1 km
Sites with Rural Objective
– Radius of area to collect data for acceptance procedure: 4 km
Sites with Highway Objective
– Linear Area to collect data for acceptance procedure: 7 km on each Direction of the road of the target (highway)
Note: The radius of area depends upon the height of the Antenna. As the height increase the radius area also increase.
Sites with Urban Objective
RX Level Threshold: 85% of the samples shall have greater and equal to -75dbm
RxQual Threshold: 80% of the values shall be between 0-4, where samples of value 4 shall be less than and equal to 20%. Values 6 and 7 shall be _ 10% of the total samples
C/I Threshold: 90% of the samples less are in between 12 to 30
Sites with Rural Objective
RX Level Threshold: 70% of the samples shall have greater and equal to -75dbm
RxQual Threshold: 80% of the values shall be between 0-4, where samples of value 4 shall be less than and equal to 20%. Values 6 and 7 shall be _ 10% of the total samples
C/I Threshold: 90% of the samples less are in between 12 to 30
To consider this activity completed the following deliverables must be produced: List of constrains related to this activity (if any)
Log files delivered to Huawei local office
Site Integration Report ( See the Report format below)
3. Drive test report
This step will produce the final DT report which shall contain all RF indicators, as per the report template below.
We have added few new points in the report, which are
Regarding to Handover Relationship Table, we have to strictly follow the following
We have to check the neighbor relation as per CDD, and then confirm it with the OMC that whether all the neighbor relations are defined in the OMC or not. If there is any missing relation which is not exist in OMC but exist in CDD then
we will ask the OMC guy to add it and while preparing the report we will mention that this neighbor relation wasn’t added in the OMC before, but we have added it.
If all the neighbor relations in the OMC are according to CDD then we will put all the neighbor relations in the report.
If we there is no handover occurred between any relations according to CDD then we just put "NOT OK" in front of that relation in the report and give the reason why there was no handover occurred. (See the report template for reference) In any case, we must put all the neighbor relationships according to CDD in the
report, all we need to do is to write the status in front of the relation. We write OK-(if the handover is occurred) NOT OK (If the handover is not occurred). For NOT OK, we will mention the reason that why there was no handover occurred.
If there is no road available or if there is no access to any road which is given in the route area, then we will have to take the snaps of the area that why there is no access
4. Annexes DT Check list
DT checklist.xls
Drive Test report template
