TGCP Optimizer - Step by Step Rev.PA2 - 3GCellPro fileIn case loading (from Files->Read ... 2.2 How to import Huawei RNC TRACE CHR&MNCDT? ... SOFT_HANDOVER_EXECUTION and MISSING_NEIGBOUR

�

TGCP Optimizer

Step by step

Guide

Release 4.92

Rev.PA2 �

Manual TGCP Optimizer v.4.92 Step by Step

www.3gcellpro.com 2 of 34

Content:

1� INTRODUCTION .................................................................................................................................. 3�

2� WORK WITH TGCP OPTIMIZER FUNCTIONALITY. ................................................................. 3�

2.1� HOW TO CREATE THE PROJECT DB? ...................................................................................................... 3�2.2� HOW TO IMPORT HUAWEI RNC TRACE CHR&MNCDT? .................................................................. 6�2.3� HOW TO ANALYSE PROPAGATION DELAY DATA IN CRFAA? .............................................................. 25�2.4� HOW TO IMPORT AND ANALYSE DRIVE TESTS DATA FROM TEMS FMT FILES? .................................. 28�



1 Introduction

The purpose of this document is to guide an user step by step through TGCP optimizer functionality

2 Work with TGCP Optimizer functionality.

2.1 How to create the project DB?

At the beginning the Project DB must be created. From Files menu select New Project option.

Then select location of project Access DB file and its name.



In Tools->Options->Network tab set the Band and Channel UARFCN used in your UMTS NW

In Tools->Options->Network tab set the Band and Channel ARFCN used in your GSM/DCS(PCS) NW



In order to assign cell to proper layer (or system) TGCP Optimizer needs Cells Configuration data prepared in CSV file format described in manuals Annexes. Examples of configuration data can be found in Config folder files: “Template 5 Layes Config 2xWCDMA GSM-DCS.csv” and defined neighbours “Template Ncells UNIQUE CID.csv” and/or “Template Ncells CGI CID.csv”.

In case loading (from Files->Read Cell Config) NW data first time the appending operation will take place. Tool lets also to replace already loaded data. If data is already in DB an engineer can decide what action is needed from below options.



From Files menu select Read Defined Neighbours and chose neighbour cell file in its location. This operation is disabled before cell configuration load. CSV

Now your project is confired and ready for loading trace, drive test or statistics data.

2.2 How to import Huawei RNC TRACE CHR&MNCDT?

There are two types’ possible for Huawei TRACE: CHR.log and/or MNCDT.tmf files import via File->Import TRACE option:



The Import TRACE Wizard: Release tab leads user through different import data types:

• HUAWEI CHR.log (V200/V900 SW) or MNCDT.tmf trace up to RAN11. User must select proper UTRAN SW Release and data type.

In the Method tab – user selects Import method: module(s) or event(s)



By Modules method option, imports automatically selects events needed for chosen module in Details window. By Events method lets the user select few or all available events in Details window, to be imported into project DB. Details tab – lets user to select module or event

o HUAWEI Modules

Note: For NMCDT HUAWEI trace only SHO module is available with SOFT_HANDOVER_EXECUTION and MISSING_NEIGBOUR detection events without radio parameters for connection.

• Location tab - lets user chose Directory, including data, or File(s) for import.



Directory – imports all files from selected directory, all available events decoding will be done.

File(s) - imports selected files only, all available events decoding will be performed.



During data import the status window shows progress of data post-process on single file and all selected files, on the window bottom.

All imported data are logged into file and Details can be seen or Hide in the by buttons. Cancel button pause import process or break it.

The import process is ended by report (imp.log file is stored in log subdirectory of TGCP Optimizer installation folder). Pressing OK button ends data imports.



View menu allows displaying Files List window; user can select single file, one by one or using Select (or Unselect) All files at once.

First time opened Summary window is empty and user has to open Files window and select the files for analysis and pres Commit button

Note: Just selected files and confirmed by Commit button will be considered in the statistical calculations of chosen SHO/TRACE UNIVERSAL, HSPA or STAT module functionality. The content of window is available when relevant Summary window is active and Commit button must be pressed (NF is red in right down Summary window corner) the calculations in Summary window can be run.



SHO Summary after calculations contains statistical data for analysis (NF is grey in right down Summary window corner). Now Map window can be opened where on Relation tab user will have to choose relation types for analysis. Then SHO Charts and Details window can be opened with histograms bars for SHO Monitored Neighbours and Detected neighbours (SHO MN&DN tab).

And Detected Neighbours (DN tab).



Map window runs from Maps->Main option and Toolbox starts with map window.

Map ToolBox functions:

1. Pointer

2. Cell info – displays cell configuration info in “Cell Info” window, which appears automatically after selection a cell.

3. Move

4. Centre view

5. Distance Ruler

6. View in zoom 1:1

7. Zoom to All loaded NW elements data

8. Zoom in and out – uses right (in) and left (out) mouse buttons

9. Zoom by mouse box – zooms to the selected area

10. Zoom to all neighbours – shows all neighbours in the map window *

TRACE menu- SHO Module



SHO Module takes into consideration two events Soft Handover Execution and Missing Neighbours Detection.

SHO Summary

The calculations (Calculate button) are made for selected files only in Files window. The calculations will be done for settings in Performance Analysis criteria, set in Tools->Options->SHO window (presented at the end of this chapter).

The SHO summary window contains:

• Cell data (Cell name and/or Cell ID)

• SHO MONITORED NEIGBOURS & SHO DETECTED NEIGBOURS– statistical information about number of defined neighbour cells included in active set and not defined NCELL but involved in active set (not available for TRACE Universal.csv)

• DETECTED NIEIGBOURS - statistical information about number of detected cells reported by UE’s

• Total – sum of all calculated defined and detected neighbours. Please observe that in some cases, the same cells can exist in both types of events.



The cell row with SHO data is synchronized with Details and Map windows, what helps with quick data analysis. All columns can be sorted and window content can be modified by right mouse button.

Details – SHO events

The Chart and Details window contains of two tabs SHO MN&DN and DN.

The tab SHO MN&DN presents:


• EcNo and RSCP – average value for all active set additions*

• Samples - number of occasions in active set with given cell

• % - percent of occasions in active set related to total number of attempts in observed triggered cell

• Distance – between best serving (observed) cell and cell in active set

• Neighbours – information “yes” if cell is defined neighbour and “no” if cell is not defined a neighbour.

* not valid for Huawei MNCDT trace - TGCPO SW uses default low values

The cells involved in active set but not defined are potential neighbours and mark orange on charts bars and also the same colour is used for label box with cell name on map, what speed up the analysis part.

The EcNo or RSCP can be chosen on the bars chart.



Tab DN presents:

• SC – Primary SC Trigger, reported by UE as detected neighbour SC

• Cell - Potential neighbour Cell proposal

• EcNo and RSCP – average value for all reported values*

• Samples - number of occasions reported

• % - percent of occasions reported related to total number of attempts in observed cell

• Distance – between best serving cell and detected neighbour cell

* not valid for Huawei MNCDT trace but SW uses default low values

All reported in event DETECTED NEIGBOURS cells are potential neighbours and mark orange on charts bars and also the same colour is used for label box with cell name on map, what speed up the analysis part.

The EcNo or RSCP can be chosen on the bars chart



Note: In case missing information of some cells in cell config data, in the Summary SHO window the number of detected neigbours can be different compared to Details chats and Map, because for presenteation porpose the configuration data of all measured cells is needed.

Cell priority – SOFT HANDOVER EXECUTION

This functionality an output is list of all cells involved in soft handover (defined and not defined n-cells) sorted according to number of samples, average EcNo, RSCP values and distance. The column Priority suggests order of the neighbour cells, which can be implemented in the RNC. Moreover report contains Neighbour (defined or not info), Spare to Add S/N column (Serving/Neighbour info if there is enough spare place on list to add detected neighbour “yes”, only not defined neighbours are considered, list controlled up to 31 relations, default for SHO), information about Mutual or Single direction of detected missing SC.

The relations with zero samples can be considered for removal (in case Ericsson SHO Execution trace only).



Note: Option->SHO-> Performance Analysis->Parametres settings have impact on event SHO EXECUTION Cell Priority reports results, exluding Samples settings. Defined Neigbours Cells, which were not involved in active set are listed at the end of list. This information can be used for deletion of unused relations.

Note: For Huawei MNCDT trace this report does not contain valid RF parameters. SHO Execution is not supported for TRACE Universal.csv.

Cell priority – MISSING NEIGBOURS

This functionality an output is list of all cells reported as detected neighbours (not defined neighbours) sorted according to number of samples, average EcNo, RSCP values and distance. These reported cells can be considered as potential neighbours (Cell Trigger PCPICH, SC Trigger) of Cell Serving (Cell S). The column Priority suggests order of the neighbour cells, which can be consider with combination of event SHO EXECUTION priority list and implemented in the RNC. Moreover report contains Neighbour (defined or not info), Spare to Add S/N column (Serving/Neighbour info if there is enough spare place on list to add detected neighbour “yes”, only not defined neighbours are considered, list controlled up to 31 relations, default for SHO) and Direction, information about Mutual or Single direction of detected missing SC.



Note: Option->SHO-> Performance Analysis->Parametres settings have impact on event Cell Priority reports results, exluding Samples settings.

Note: For Huawei MNCDT trace this report does not contain valid RF parameters

Options-> SHO filtering parameters

In order to make analysis more efficient the user is able to filter parsed data in Tools->Options->SHO tab. The SHO - Performance Analysis options allow user change the defaults analysis parameters:

• Maximum allowed Distance Max between neighbour’s cells. For dense urban NW where SC are repeated this distance shall be set smaller value (e.g. 3000-5000m)



• Minim Samples of attempts SHO or reported as detected cell

• event trigger - for events 408/SHO Execution and 427/Detected Neighbours (in case none selection all trigger events will be consider for analysis -filtering). Valid for GPEH and UNIVERSAL trace, for Huawei CHR/MNCDT Add_Cell_Proposal and Event 1A are assumed during import to DB. Please keep defaults for CHR analysis.



• Minimum CPICH EcNo for evaluated cell- Valid for CHR,GPEH and UNIVERSAL trace

• Minimum CPICH RSCP for evaluated cell - Valid for CHR,GPEH and UNIVERSAL trace



• Result of RNC decision – event 408, Valid for CHR, GPEH and UNIVERSAL trace. Please keep defaults for CHR analysis.

• Action – taken by RNC for detected neighbour’s events 427. Valid for GPEH and UNIVERSAL trace, for Huawei CHR/MNCDT “No Action” is assumed during import to DB. Please keep defaults for CHR analysis.



• CPICH EcNo offset – by changing this parameter (related to connection release offset) user can simulate numbers of drops when offset between serving cell and detected neighbours is changed. This parameter helps also with finding the necessary missing neighbours.

• CPICH RSCP offset – by changing this parameter user can simulate numbers of drops when offset between serving cell and detected neighbours are changed. This parameter helps also with finding the necessary missing neighbours.



• Relation Direction – applicable only for Cell Priority report only and three options can be chosen: Single, Mutual or Both directions.

Note: Above parametres help with data filtering and influence on SHO Summary. These analysis have also impact on Cell Priority reports results, exluding Samples settings.



2.3 How to analyse propagation delay data in CRFAA?

The Cell RF And Access parameters (CRFAA) module uses HUAWEI CHR trace data or Ericsson pmPropagationDelay_PDF_counter and extracts propagation delays and EcNo data from call setups data.

Note: EcNo data for call setups are available for CHR HUAWEI trace only.

The calculations (Calculate button) are made for selected files only in Files list. First time opened Summary window is empty and user has to open Files window and select the files for analysis and pres Commit button. Then calculation can be run and after calculation below Summary window will contain below data:

The cell row with CRFAA data is synchronized with Charts & Detailed and Map windows, what helps with quick data analysis.



The Charta and Details window contains of two tabs Propagation Delay and EcNo.

Tabs present:


• Propagation Delay – PDF

• EcNo - PDF

The Max, Avr and Min range of selected cell is shown on the map what is helpful during coverage and neighbours analysis on map window.



Tools->CRFAA TAB In this option user can set unit [m] of propagation delay.



2.4 How to import and analyse Drive Tests data from TEMS FMT files?

Before import into TGCPO DB TEMS drive tests data must be exported from TEMS Data Collection via LOG->Export wizard.

The *.FMT export settings can be loaded into TEMS export window from Export subdirectory, located the main TGCP Optimizer installation folder. There are two “tex” files for different data type export:

1. Scanner 2G&3G 4 layers UE 2G-3G_data.tex – these settings are required for WCDMA and GSM scanner, UMTS/GSM/DSC and IRAT measurements analysis

2. Scanner 2G&3G 4 layers UE 2G-3G_data Extended.tex– these settings are required for WCDMA and GSM scanner (up to 50channels), UMTS (BlerDl, RssiDl, RssiUl, UeTxP)/GSM/DSC and IRAT measurements analysis

The tex_2 is recommended for export because it gives more data and provides extra information about UL AND DL parameters. Drawback – slower import and larger export files size.

In order to import drive tests data go to Files options and select Import Drive Tests:



Then Import Wizard window will appear and let, in Content tab, the user to Add from drop-down list MS (UE or Scanner) number, measured System (WCDMA or GSM/DCS) data and Mode (Scanner or Dedicated). The Remove button erases selected, already defined MS.

Note: Because some test UE’s do not report internal measurements for TEMS, thus in case TEMS FMT user can decide how often UE data will be read and imported using TEMS 3G messages time interval option. We recommend interval of 100ms.

In the Location tab of import wizard, gives user chose of two data sources type.



User can chose the source Directory or Files for Import, executed by button.

The data format will be recognized automatically. During data import the status window shows progress of data post-process on single file and all selected files, on the window bottom.

Cancel button pause import process or break it.



Note: DT Import wizard checks content of read FMT filed data and records in the log file (located in log SW folder). If 3G INTRA option is chosen and FMT with 3g and 2g measurements will be selected, just required data will be extracted from files with respect to selected MS number.

The import process is ended by a short report. Pressing OK button ends data imports.

After successful FMT Data import the Binning irequired for futher analysis and map presentation.

The binning is required for all drive tests analysis and this process must be performed at the beginning of analysis by setting coordinates of binning area and pressing Process button. This functionality lets user to define area of required analysis, what can be useful in case some coverage investigation e.g. city centre.

Note: After changes of Binning parameters in Tools->Options->Drive Tests->Binning settings binning process must be recalculated in order to observed parameters change effects. Binning Area option protect analysis from measurement equipment coordinates errors and bugs.

Note: The bins with RSCP, EcIo or RxLev below RSCPmin, EcIo min or RxLev min will be excluded from further analysis.

This SW version supports 9 resolutions of 3, 5, 10, 20, 25, 30, 50, 100 and 200m of bin.



For 3G-3G INTRA neighbours cells analysis the Active Set Window are taken into account.

For 3G-2G IRAT neighbours cells analysis the Relative Offset between 2G best server and its potential neighbours are considered. Moreover user can select if wants to analyse IRAT relations to 3G Best Servers or to All SC in active set (Tools->Options->Drive Tests -> IRAT Analysis Parameters).

The Binning Wizard leads user through three steps:

1. Content – where user can choose between single INTRA, INTER IRAT or GSM binning process. For 2G GSM (low band) and/or DCS/PCS (higher band) can be selected for binning and only these results will be available later for the analysis.

2. Parameters – configurable also in Tools->Options->Drive Tests

Note: The IRAT/GSM binning can be done for two options, with 2G Cell Config data and without cells configuration and in this case 2G Cell ID is obtained From Drive Tests data UE in dedicated mode. The New Data box must be checked if new drive test data were loaded to the DB or Cell Config was change otherwise cell configuration will be obtain from previously generated 2G Cell data.

Note: For the GSM neighbours analysis tool recommends 6dB for Relative Offset but for IRAT it can be to low value, rather around 10-16dB for RO can be considered.

INTER Offsets are used for inter frequency neighbour analysis and these offsets are added to the bin RSCP and EcIo of the A layer if user selects analysis of the layers A-B. This way one of the layers can be privileged.



3. Map Area – definition of binning area of left-upper and right-lower area points.

Note: When Binning Wizard window is displayed, user can read coordinates of the pointer in the map window



The Binning process takes from several minutes to tens minutes (depending on area size and analysed data type, chosen binning algorithm, for IRAT/GSM takes more time compared to INTRA and INTER) and is finished by below window if it was OK, otherwise Failed info is shown

Now you can work with for below analysis types and for more information please refer to Drive Tests manual below chapters:

• 4.8.3 INTRA

• 4.8.4 INTER

• 4.8.5 IRAT

• 4.8.6 GSM

Documents

TGCP Optimizer - Step by Step Rev.PA2 - 3GCellPro fileIn case loading (from Files->Read ... 2.2 How to import Huawei RNC TRACE CHR&MNCDT? ... SOFT_HANDOVER_EXECUTION and MISSING_NEIGBOUR