Drive Test Analysis Procedure

Document Name:
Document ID:
Rev. #:
Date:
Drive Test Analysis Using Nemo Analyze

Prepared By: Approved By: Pages: Department:
Prashant Vasudavan
Drive Test Analysis Procedure Using Nemo Analyze
Hexamatics Servcomm Sdn Bhd Confidential
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Document History
Date 13-March-10
Version v1
Change history Initial version
Author Prashant
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Introduction
The purpose of creating the guideline is to allow engineers to have an overview and understanding on the analysis portion of the Celcom Pre and Post-rehoming reports. This guideline can be broken down to 3 parts:
Rehoming Process Creating Analyze Workspace Sample Analysis
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Pre Requisite Information

The pre requisite for this task is that the user has working capabilities to use Nemo Analyze and has a copy of the road maps. Software:
Nemo Analyze 5.04 and above (preferably Nemo Analyze 5.12)
Files:
Malaysia Road Maps Klang Valley Road Maps Cellfile (also known as BTS file)
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Rehoming Process
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Rehoming Process
Engineer performs drive test
Drive test engineer submits logfiles to analysis engineer
Drive test logs are loaded into Nemo Analyze for further analysis
If logfiles are corrupted
Analysis is included into the Pre/Post-Rehoming report for submission

Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Creating Analyze Workspace
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Introduction to Nemo Analyze

Select Nemo Analyze from Start menu: Start Nemo Tools Nemo Analyze 5
Blank workspace will appear
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

3 Go to View Organize measurements 4 An Organize Measurement window will appear
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

5
Go to View Workbook Map
Workbook with map will open
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

To add road maps, right click on mouse and go to MapX 7 Organize Layers
9 Click on Add
8 A Layer Control window will appear.

Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

Select desired road maps in MapInfo Tables (*.tab) format 1 0 Newly added routes will appear in Layer Control
1 2
Select the World.tab file and click on Remove
1 Select Open 1
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

1 3 Zoom into map area
1 4 Point cursor at Workspace tab & the workspace window will appear
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

1 6
Right click mouse and select Open
1 7 Select latest BTS file
1 5
Click on Base Stations icon

1 8
Click Open
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

1 9 Drag and drop BTS file at the Map window 2 0 Click here
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
2 1 Select desired information to display
2 2 Click on the Color tab and set a default color
2 3
Click OK
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
2 4
BTS file displayed based on selected information
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

Methods to load logfiles, join logfiles together and to store them into folders have been shown in previous guidelines. Key measurements that are used for analysis are:
RSCP (active and monitored set) Ec/No (active and monitored set) BLER Downlink Spreading Factor TX Power UL Interference RRC & L3 Messages RSCP CPICH (Scanner) Ec/No CPICH (Scanner) Call Events
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
2 5 To insert more measurements into the same workbook, Right click mouse Data View Split Horizontally/ Vertically
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

2 6 Select desired measurements 2 8
Select data view
2 7
Drag and drop desired data to view in blank workspace Hexamatics Servcomm Sdn Bhd Confidential
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

2 9 Choose graph type Loaded RSCP line graph
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

Similarly, repeat step 27 for other measurement data such as Ec/No, BLER, RRC and Layer3 messages. Use these pointers to help you:
RSCP, Ec/No, BLER, Tx Power RRC & L3 messages, Events Select Graph data view Select Grid data view
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

RSCP Active Set Plots RSCP Monitored Set
Ec/No Active Set
Ec/No Monitored Set
BLER, DL SF, Tx Pwr, UL Interference
RSCP CPICH (Scanner)
Call Events
L3 & RRC Messages

Ec/No CPICH (Scanner)
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Sample Analysis
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Call Attempt Failure

Poor Active Set RSCP Poor Active Set Ec/No
Analysis Call was attempted in poor radio condition. UE could not make cell reselection to best server in the area. UE sent RRC connection request once but no reply. This CAF is due to poor coverage that resulted in failure to connect to radio channel.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
CM_SERVICE_
REJECT sent by network Analysis All MOC process was running smoothly until network sent CM Service Reject message and then release the RRC connection. The rejection reason is due to IMSI unknown in VLR. This can be caused by corrupted VLR database, as it cannot allocate TMSI or wrong data. Suspect this is Core Network (CN) issue and further investigation is needed, using RNC and CN trace logfiles as RF environment looks fine.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Analysis No dominant server in this area. All server serves with almost similar level of RSCP and Ec/No, as detected by scanner. Network then released the connection. Suggest to down tilt unnecessary cell in the area. However, this CAF happened when UE moved to other RNC and also other VLR. Redrive for verification.
All RSCP and Ec/No at almost similar level
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
BLER increased
Numerous Measurement Report sent by UE

Analysis No request was sent by UE for RRC connection. After sending CM Service Request, UE sent Measurement Report (MR) several times to add sc423 and sc30 which are better server than current AS. No Active Set Update once MR respond from network. BLER also increased. Check SHO parameter between sc139 and sc423.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

Poor Active Set & Monitored set RSCP
Scanner detects poor RSCP
No cells serving with good RF condition in this area. RSCP is very poor, and even scanner detects poor coverage for all cells. UE sent several times request for RRC connection with no reply from network. Suggest new site to solve the coverage problem in this area.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Analysis There was no RRC connection request sent by UE to network after request for CM service. Suspect UE error or hang, or can not synchronize with Nemo Outdoor for a few seconds since there are missing signaling messages. Best current server is sc371. Check alarm history during drive test time to assure that this CAF reason is not node B problem.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan

RSCP and Ec/No value is not visible
Analysis Call Setup Request was sent when UE was forced from GSM mode to UMTS mode, resulting in call failure.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Missing signaling messages for 23 seconds

Analysis There was missing measurements for 23 seconds after last RRC connection. Suspect UE cant synchronize to the network after last request. Also, no release message appeared. This also can be caused by no available channel. Check alarm and trace logfiles for more details.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Call Drop
UE Scanner detected sc307 which is the best server but not detected in UE monitored set
Scanner
Analysis There is missing neighbor detected. UE sent e1a to add sc122 several times and also e1a for sc114 with no respond from network. However both were serving quite poorly. UE did not send e1a for sc307 which is the best server in the area. Add neighbor relation between sc259 and sc307.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Call Drop
Analysis UE sent MR e1a to add sc238, sc146 and sc406 to AS since sc238 is better server in the area, it also detected as best server by scanner. Even several times UE request to add but no ASU respond since sc350 Ec/No became very poor. UE disconnect the call and release RRC connection. Check SHO timing between sc350 and sc238 and AdjEcNoOffset.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Call Drop
Severe degradation in RF condition
Analysis UE sent e1f for sc307 and then drop that scrambling code from AS since Ec/No also degraded sharply. Network responded to the uplink message with ASU but at the same time sc114 also started to degrade. BLER also increased, resulting in CAD. There are too many server serving with quite similar RSCP and Ec/No. Reduce CPICH power sc146 to minimize pollution in this area. Hexamatics Servcomm Sdn Bhd Confidential
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Call Drop
Symptoms of pilot pollution: RSCP and Ec/No value for all serving cells are similar. No dominant server.
Analysis Measurement Reports were sent several times to replace sc197, sc221 and sc213 with sc34 and sc157 which are better than current AS. No ASU resulting in call drop. However, there are too many cells serving with similar RSCP and Ec/No. Need to do physical change/adjustment or CPICH Tx Power adjustment to reduce the pilot pollution.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
Call Drop
No monitored and detected set
The call was originated on sc58 but coverage and quality of that cell degraded, resulting in drop call. No MR was sent to add other cells. Also, there are no server in monitored and detected set list but scanner shows better server (sc90) with RSCP -64dBm and Ec/No 5.4dB. Check neighbor relation between sc58 and sc90.
Document Name:
Document ID:
Rev. #:
Date:

Prashant Vasudavan
End Of Work Instruction

Drive Test Analysis Procedure

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Drive Test Analysis Procedure

Caricato da

Copyright:

Formati disponibili

Document Name:

Drive Test Analysis Using Nemo Analyze