You are on page 1of 7

CSI Network and Service Optimization

Nokia Siemens Networks


Network & Service Optimization
Field Drive Test for Optimization

2007 Nokia Siemens Networks. All rights reserved.

Field Drive Test for Optimization

Table of Content

1. FIELD DRIVE TEST FOR OPTIMIZATION


1.1 General

3
3 3 3 3

1.2 Field drive test for performance measurement 1.2.1 Prerequisites and assumptions 1.2.2 Deliverables and committed service level

2. TOOLS 3. CUSTOMER SPECIFIC ISSUES

7 7

2/7

Field Drive Test for Optimization

1.
1.1

Field Drive Test for Optimization


General
This document field Drive Test for Optimization gives a description of what is required for drive testing.

1.2

Field drive test for performance measurement


The purpose of the service item is to perform the drive tests according to the project plan. The main activities are: Drive test planning and measurement execution Drive test measurement report Drive test logs analysis Drive test analysis report

1.2.1

Prerequisites and assumptions


Testing methodology Drive test route

1.2.2
1.2.2.1

Deliverables and committed service level


Drive test measurements report The following items are the required outputs after each day of drive testing: a. Equipment Check Form This contains details of the basic checks on the drive test equipment that shall be made at the start of each day. These checks will be detailed enough to ensure that the equipment is performing as expected and that all cables and connections are secure and undamaged. b. Log Details Sheet While doing the testing the technician of the drive test makes notes of any special events into the sheet. It contains the following information: Network status on drive route before drive began Log file details Number of call attempts for all services measured (a minimum number will be expected each day and specified) Details of events, problems or anomalies that occurred or were seen during the drive test c. Scanner log file for the route in electronic format d. Raw measurement files in electronic format Drive test logs analysis For the drive test analysis report, first the drive test logs need to be analyzed. The analysis of the drive logs should be broken down as follows:
3/7

1.2.2.2

Field Drive Test for Optimization

a. Cluster Analysis / Clutter Area Analysis Calculate the cluster / clutter area performance KPIs (the required KPIs will depend upon what NSN have agreed with the customer) Identify faulty sites/cells Identify cells with crossed feeders b. RF Performance Analysis Identify areas of low RSCP (3G), low RxLev (2G) and determine the cause and possible solutions within any constraints Identify areas of low Ec/No (3G), high interference (2G) and determine the cause and possible solutions within any constraints. c. Neighbor Analysis Identify a list of potential missing neighbors (3G and 2G) over the whole of the drive. Determine whether these should be added as neighbors or not, or if they are overshooting cells that shouldnt be serving in that area. For recommended neighbor additions determine if there is the room in the neighbor lists. If not, recommend deletions as well. d. Root Cause Failure Analysis Analyze all call setup failures and all call drops. Determine the cause and suggest solutions. Analyze ISHO failures and determine the reasons for failure and for the ISHO attempt. Determine solution if possible. Analyze successful ISHO and determine the reason for the ISHO. Determine solutions if possible. The data derived from the drive test logs analysis is used in producing the drive test analysis report. 1.2.2.3 Drive test analysis report Cluster / Clutter Area Summary This is a high level summary of the cluster performance. It should contain: a. Ec/No and RSCP distributions of the route based on the scanner measurements b. OCSR per service, CSSR per service, CCSR per service c. Number of calls per service, number of setup failures per service, number of drops per service d. ISHO success rate for voice, cell change order success rate for PS e. % time on 3G, % time on 2G f. Failure categorization summary per service Separate for 3G and 2G by call setup and call drop g. Number of crossed feeder identified h. Number of possible faulty sites RF Analysis This is a report on the RF performance on the drive test route. The pages should be structured such that the higher level performance indicators are shown first followed by the detailed cell level metrics. The report should contain analysis and suggested actions/solutions. a. Quadrant plots showing RF performance with a copy of the route colored according to the quadrant. Show failures on the plot so that they can be associated to areas of poor RF.

4/7

Field Drive Test for Optimization

b. Ec/No and RSCP distributions on the drive test route based on the scanner measurements c. Interference matrix calculated based on the Ec/No measurements (in electronic format) d. RF performance metrics These are scanner plots with Ec/No (user defined thresholds), RSCP (user defined thresholds), scrambling code over the route, plot of pilot pollution over the drive based on user defined metrics. If possible, mark problem areas on the plots. e. Pilot pollution statistics from scanner (calculation methodology to be agreed with Nokia) f. Number of missing neighbors identified (3G and 2G) g. Number of possible crossed feeder identified h. Radio information overview table per service i. Table detailing 3G neighbor addition information Source, target, number 3G neighbor additions still possible, number of combined 3G/2G neighbors j. Table detailing 3G neighbor deletion information Source, target, number 3G neighbor additions still possible, number of combined 3G/2G neighbors (allow user to limit size of deletion list by specifying minimum cell to cell distance) k. Table detailing 2G neighbor addition information Source, target, number 2G neighbor additions still possible, number of combined 3G/2G neighbors l. Table detailing 2G neighbor deletion information Source, target, number 2G neighbor additions still possible, number of combined 3G/2G neighbors (allow user to limit size of deletion list by specifying minimum cell to cell distance) m. Table detailing cell level pollution information Source cell id, % inbound pollution, % outbound pollution. The user should be able to choose the pilot pollution calculation method. n. Table detailing co-scrambling code clashes Source cell id, neighbor cell id, neighbor to source cell and sc, neighbor to neighbor cell and sc. o. Table listing sites with possible crossed feeders Cell id, cells that are believed to be crossed p. Table listing possible faulty sites Cell id, cells that are believed to be faulty, column to allow user to enter action taken Service Analysis (Voice and Video) This is a report on the performance of the voice and video service. The pages should be structured so that the higher level performance indicators are shown first, followed by the detailed cell level metrics. There should be separate pages for voice and video services. The report should contain analysis and suggested actions/solutions. a. OCSR for voice and video, CSSR for voice and video, CCSR for voice and video b. Number of calls for voice and video, Number of setup fails for voice and video, Number of drops for voice and video

5/7

Field Drive Test for Optimization

c. Quadrant plots showing RF performance with a copy of the route colored according to the quadrant. Show failures on the plot so failures can be associated to areas of poor RF. d. Ec/No and RSCP distributions based on the measurements from the phone making voice/video calls e. From voice/video UE measurements: Plots of Ec/No (user defined thresholds), RSCP (user defined thresholds), scrambling code over the route, pilot pollution over the drive based on user defined metrics, UE TX power f. Soft handover overhead g. % time in compressed mode h. Number of ISHO i. ISHO success rate j. Breakdown of the compressed mode trigger reasons k. % Time on UMTS, % Time on GSM l. Protocol information m. Failure categorization summary for voice Separate for 3G and 2G by call setup and call drop n. Table showing the following for each failure (table should be editable by the user) Failure id (A way to identify the failure needs to be provided. This should also link to the failures shown on plots.) Description of failure Suggested solution Service Analysis (PS Calls) This is a report on the performance of the PS service. The pages should be structured so that the higher level performance indicators are shown first, followed by the detailed cell level metrics. The report should contain analysis and suggested actions/solutions. a. OCSR, CSSR, CCSR b. Number of calls, number of setup fails, number of drops c. Number of attach attempts, number of attach success, number where attach time > user defined threshold d. Number of PDP context attempts, number of PDP context success, number where PDP context attach time > user defined threshold e. Quadrant plots showing RF performance with a copy of the route colored according to the quadrant. Show failures on the plot so failures can be associated to areas of poor RF. f. Ec/No and RSCP distributions based on the measurements from the phone making PS calls g. From PS UE measurements plots of Ec/No (user defined thresholds), RSCP (user defined thresholds), scrambling code over the route, plot of pilot pollution over the drive route based on user defined metrics, UE TX power plot h. Soft handover overhead i. % time in compressed mode j. Number of cell changes k. Cell change success rate l. Breakdown of the compressed mode trigger reasons m. FTP download attempts, FTP download success n. FTP upload attempts, FTP upload success
6/7

Field Drive Test for Optimization

o. p. q. r. s.

Average download throughput Average upload throughput % time on UMTS, % time on GSM Protocol information Failure categorization summary for PS Separate for 3G and 2G by call setup and call drop t. Table showing the following for each failure (table should be editable by the user) Failure id (A way to identify the failure needs to be provided. This should also link to the failures shown on plots.) Description of failure Suggested solution

2.

Tools
NSN has defined the following maps, tools, test and measurement equipment that shall be used for DT: Field Measurement Tool for 2G 2G Scanner Car 2 mobiles Measurement software (e.g. NEMO) with GPS Field Measurement Tool for 3G Car 2 mobiles 1 HSDPA data card 3G scanner (capable of measuring 1 frequency) 2G Scanner Measurement software (e.g. NEMO) with GPS Post processing tool (e.g. Actix) Post-Processing E2E Drive Test Analyis Software (e.g. WAMS from Agilent) .

3.

Customer specific issues


Considering the team to perform the drive tests, two options need to be quoted: The team consists of a driver only; consequently the measurement tool needs some kind of automated script. In this case the drive test measurement report shall be limited to the raw data and major incidents only. The team consists of a driver and a technician. The technical needs to have enough technical understanding to make the drive test measurement report.

7/7