MUSA 4.6 User Manual v2_3

Release 4.6

USER MANUAL

Version 2.3 June 2007

Copyright 2003 2007 Nokia Siemens Networks S.p.A. All Rights Reserved

Issued by Nokia Siemens Networks 20126 Viale dellInnovazione, 3 20126 MILANO (Italy) CMO WSE

MUSA 4.6 User Manual 2

Document Revision History

Status Issue Date Reason for Changes Draft 1.0 31/03/2005 First Draft Emission Release 1.0 15/04/2005 First version (MUSA Release 3.0) Release 1.1 14/06/2005 Revision Draft 1.2 30/09/2005 MUSA Release 4.0 Draft Release 1.3 08/10/2005 MUSA Release 4.0 First Version Release 1.4 24/10/2005 Revision Draft 2.0 15/09/2006 MUSA Release 4.5 Draft Release 2.1 05/10/2006 MUSA Release 4.5 First Version Release 2.2 06/10/2006 MUSA Release 4.5 Revision Release 2.3 02/07/2007 MUSA Release 4.6 Revision


CONTENTS

1. INTRODUCTION ..................................................................................... 8 2. MINIMUM REQUIREMENTS.................................................................. 9 3. INSTALLATION .................................................................................... 11

3.1 MUSA Setup Program ..................................................................... 11 3.2 Hardware Key Device Driver Setup ................................................ 11 3.3 Main Application Setup.................................................................... 13 3.4 PM Counters Module Installation (Optional) ................................... 15 3.5 Latest Update Installation ................................................................ 16 3.6 License Update ................................................................................ 17 3.7 First MUSA Run............................................................................... 18 3.8 License Details ................................................................................ 19

4. PROJECTS............................................................................................ 21 4.1 Main Toolbar Buttons Overview ...................................................... 21 4.2 New Project Preparation ................................................................. 21

4.2.1 UMTS Import Procedure from RNC Configuration File ......... 25 4.2.2 UMTS and GSM Network Import Procedure ......................... 31 4.2.3 Import Procedure from Excel files .......................................... 34 4.2.4 Network Import Results .......................................................... 44 4.2.5 MUSA Folders Description..................................................... 46

4.3 Project Selection.............................................................................. 48 4.3.1 Special cases.......................................................................... 50

4.4 Network Manager ............................................................................ 52 4.5 Cell Matching ................................................................................... 54 4.6 Cell Inversion detection ................................................................... 56

5. SCANNER DATA LOADING AND PROCESSING.............................. 59 5.1 Main Toolbar Buttons Overview ...................................................... 59 5.2 How to load a Scanner file .............................................................. 60 5.3 Load Single File ............................................................................... 61 5.4 Queue scanner files......................................................................... 67 5.5 Pixel Processing .............................................................................. 71 5.6 Area Cutting ..................................................................................... 79

5.6.1 Polygon Definition................................................................... 79 5.6.2 Measurements polygonal cutting ........................................... 83

5.7 Other Scanner Data functions ......................................................... 85 5.7.1 Export Tabbed Text ................................................................ 85 5.7.2 Main Menu SCANNER Options ............................................. 87 5.7.3 Main Menu VIEW Options ...................................................... 90 5.7.4 Main Menu TOOLS Options ................................................... 90 5.7.5 Main Menu OPTIONS............................................................. 98 5.7.6 Windows Synchronization .................................................... 100

5.8 Coverage Analysis......................................................................... 102 5.8.1 Irregular Coverage Recognition ........................................... 102 5.8.2 Pilot Pollution Analysis ......................................................... 107 5.8.3 Cell Identity Card .................................................................. 110


5.8.4 Coverage Analysis Settings ................................................. 114 5.8.5 Coverage Analysis Quality Indicators .................................. 117

5.9 UMTS Multi-Carrier Analysis ......................................................... 119 5.10 DVB-H Coverage Analysis .......................................................... 119

6. GENERAL PIXELLING PROCEDURE............................................... 123 6.1 Starting General Pixelling Procedure Processing......................... 123 6.2 Measurement Pixelling Wizard...................................................... 125

7. DAT A VIEW......................................................................................... 133 7.1 Main Toolbar Buttons Overview .................................................... 133 7.2 Time Charts ................................................................................... 133

7.2.2 Open Time Chart tool ........................................................... 133 7.2.3 Time Charts Window Description......................................... 134 7.2.4 Series Visualization in Time Charts tool .............................. 135 7.2.5 Time Charts Graph Area Functions ..................................... 139 7.2.6 Events ................................................................................... 144 7.2.7 Statistics................................................................................ 148

7.3 Route Map ..................................................................................... 150 7.3.1 Open Route Map Tool .......................................................... 150 7.3.2 Route Map Window Description........................................... 151 7.3.3 Series Visualization in Route Map Window ......................... 152 7.3.4 Route Map area functions .................................................... 157 7.3.5 Legends ................................................................................ 163 7.3.6 Events ................................................................................... 165 7.3.7 Network Data ........................................................................ 169 7.3.8 Polygon Definition................................................................. 175 7.3.9 Single Cell Visualization ....................................................... 175 7.3.10 Cell bitmaps generation...................................................... 179

8. STATISTICS........................................................................................ 180 8.1 Main Toolbar Buttons Overview .................................................... 180 8.2 Distribution and Cumulative Distribution Function ........................ 181

8.2.1 Distribution Window Description .......................................... 181 8.2.2 Using Distribution Window Functionalities ........................... 182 8.2.3 Handling of data ................................................................... 186 8.2.4 Distribution Filters................................................................. 188

8.3 Joint Distribution ............................................................................ 189 8.3.1 Joint Distribution Window Description.................................. 190 8.3.2 Using Joint Distribution Window Functionalities .................. 191

8.4 Statistical Mode ............................................................................. 196 8.4.1 Cumulative Distribution Function (CDF) .............................. 198 8.4.2 Mobile Numeric Statistics ..................................................... 201 8.4.3 Message Statistics................................................................ 202 8.4.4 Multiple files statistics updating............................................ 203 8.4.5 Statistic Editor....................................................................... 204 8.4.6 Stat.txt example .................................................................... 212

8.5 Time Chart Statistics ..................................................................... 214 8.6 Warning Objects ............................................................................ 217

8.6.1 Using Warning Messages in Statistics................................. 217 8.6.2 Using Statistic Editor to customize Warning Script.............. 217

8.7 Statistics from Mobile CS Message Flow...................................... 218 9. COVERAGE OPTIMIZATION............................................................. 219

9.1 Main Toolbar Buttons Overview .................................................... 219 9.2 Open Optimization tool .................................................................. 219 9.3 Heights information........................................................................ 221


9.4 Coverage Optimization Window Description................................. 221 9.5 Coverage Optimization adjustments ............................................. 222 9.6 Saving, Loading and Exporting Modifications ............................... 227

10. NEIGHBOURS LIST OPTIMISATION................................................ 230 10.1 Opening Neighbours Analyzer .................................................... 230 10.2 AdA Projects ................................................................................ 233 10.3 Neighbour Lists............................................................................ 234 10.4 Present List Panel Formulas ....................................................... 237

10.4.1 Present Lists Panel Functional Buttons ............................. 245 10.5 Cell Sets....................................................................................... 257 10.6 Present Cell Sets Panel Formulas .............................................. 259 10.7 Display panel ............................................................................... 263 10.8 Layers and navigation features ................................................... 269 10.9 Neighbours Number and SIB11 Monitoring ................................ 276 10.10 Formulas Management ............................................................. 278

11. STATIC LOAD SIMULATION............................................................. 280 11.1 Using Load Simulation Options ................................................... 280 11.2 Exceeding Max Power................................................................. 284 11.3 RSSI Analysis .............................................................................. 284

12. ALGORITHM SIMULATIONS............................................................. 288 12.1 Introduction .................................................................................. 288

12.1.1 Simulated Algorithms ......................................................... 288 12.1.2 The Scene Concept............................................................ 289

12.2 Measurements used in simulations............................................. 289 12.2.1 Measurements setup.......................................................... 289

12.3 SIM Module.................................................................................. 300 12.3.1 SIM Commands.................................................................. 301 12.3.2 Scene creation.................................................................... 302 12.3.3 Algorithm changes in a scene............................................ 306 12.3.4 Network changes in a scene.............................................. 311 12.3.5 Replacing Scene Neighbours using an AdA file ................ 316

12.4 Scene Analysis ............................................................................ 317 12.4.1 Views .................................................................................. 317 12.4.2 Modes ................................................................................. 323 12.4.3 Network Items..................................................................... 323 12.4.4 Indicators ............................................................................ 325 12.4.5 Analysis with Indicator Map................................................ 332 12.4.6 Analysis with Indicator Lines .............................................. 336 12.4.7 Analysis with Indicator Bars ............................................... 336 12.4.8 Analysis with Indicator Distribution .................................... 338 12.4.9 Analysis with Indicator Grid ................................................ 339

12.5 Neighbours export to ADA module.............................................. 341 13. MOBILE DATA.................................................................................... 344

13.1 Main Toolbar Buttons Overview .................................................. 344 13.2 How to Load a Mobile File ........................................................... 345 13.3 Measurement Data Columns description.................................... 351 13.4 Mobile Data Functions................................................................. 354

13.4.1 Export Tabbed Text ............................................................ 354 13.4.2 Main Menu VIEW Options.................................................. 356 13.4.3 Main Menu TOOL Options ................................................. 359

13.5 Mobile CS Statistics..................................................................... 362 13.6 Mobile CS Message Flow............................................................ 365 13.7 Mobile Data Queuing................................................................... 367


13.8 HSDPA Information ..................................................................... 371 13.9 DVB-H and Flash-OFDM support ............................................... 372 13.10 Packet Data ............................................................................... 373 13.11 Indoor Data ................................................................................ 374

14. DATA EXPORT ................................................................................... 378 14.1 Main toolbar Buttons Overview ................................................... 378 14.2 Export Tabbed Text..................................................................... 378

14.2.1 Predefined Export ............................................................... 381 14.3 Other Export Formats .................................................................. 383 14.4 KMZ Export for Google Earth .................................................. 385

15. PM COUNTERS ANALYZER ............................................................. 387 15.1 Opening PM Counter Analyzer ................................................... 388 15.2 PM Counter Analyzer toolbar ...................................................... 389 15.3 Menu PM files .............................................................................. 390

15.3.1 Import PM Results File ....................................................... 390 15.3.2 Imported Files ..................................................................... 394 15.3.3 Remove Imported Files ...................................................... 395 15.3.4 Import database.................................................................. 395 15.3.5 Export database ................................................................. 396

15.4 Menu Template............................................................................ 396 15.4.1 New Template definition ..................................................... 397 15.4.2 Edit Template...................................................................... 400 15.4.3 Delete Template ................................................................. 401 15.4.4 Export Templates ............................................................... 401 15.4.5 Import Templates................................................................ 402 15.4.6 Add Template to UMR Version .......................................... 403 15.4.7 View Template .................................................................... 404

15.5 Menu Indicator ............................................................................. 406 15.5.1 New Indicator...................................................................... 406 15.5.2 Edit Indicator....................................................................... 409 15.5.3 Delete Indicator .................................................................. 410 15.5.4 Export Indicator .................................................................. 411 15.5.5 Import Indicator................................................................... 412 15.4.6 Add Indicator to UMR Version............................................ 413 15.5.7 View Indicator ..................................................................... 414 15.5.8 Indicator Analyzer............................................................... 416

15.6 Menu Batch Analysis ................................................................... 423 15.6.1 New Analysis ...................................................................... 424 15.6.2 Edit Analysis ....................................................................... 426 15.6.3 Delete Analysis ................................................................... 427 15.6.4 Execute Analysis ................................................................ 428

15.7 Menu Area ................................................................................... 432 15.7.1 New Area ............................................................................ 432 15.7.2 Edit Area ............................................................................. 433 15.7.3 Delete Area......................................................................... 434 15.7.4 Export Area......................................................................... 435 15.7.5 Import Area......................................................................... 436 15.7.6 View Area ........................................................................... 437

15.8 Menu Task................................................................................... 438 15.8.1 New Task............................................................................ 438 15.8.2 Edit Task............................................................................. 446 15.8.3 Delete Task......................................................................... 447 15.8.4 View Task ........................................................................... 448


15.8.5 Options................................................................................ 448 15.9 Menu Tools .................................................................................. 449

15.9.1 Options................................................................................ 449 15.9.2 DB Shrink............................................................................ 451 15.9.3 Scanner Tracing ................................................................. 451

16. MAIN TOOLBAR SINGLE BUTTONS............................................... 455 17. APPENDIX........................................................................................... 458

APPENDIX A SCANMAP DATA...................................................... 459 APPENDIX B HEIGHT DATA........................................................... 461 APPENDIX C NETWORK FILES..................................................... 463 APPENDIX D SIEMENS RNC FILES .............................................. 465 APPENDIX E ANTENNA 3D PATTERN.......................................... 466 APPENDIX F CELL IDENTITY CARD LOGO FILES ...................... 468 APPENDIX G INPUT SCANNER FILES.......................................... 469 APPENDIX H INPUT MOBILE FILES.............................................. 470 APPENDIX I WARNING SCRIPT FILE............................................ 471 APPENDIX J COVERAGE ANALYSIS PIXEL FILES...................... 472 APPENDIX K PM COUNTER ANALYZER CLASSES .................... 476


1. INTRODUCTION

To meet the need of detailed investigation on UMTS network MUSA offers several tools that allow a specific analysis on data collected in field with different measurement equipment. The manual is structured to offer in every chapter a complete view of specific MUSA functionalities, starting from the creation of the workspace and the import of the available data up to the Coverage analysis and Optimization tools. MUSA functionalities depend on the kind of license owned by the user. In this manual we will follow a complete description of the options that are available only with a full license.


2. MINIMUM REQUIREMENTS

System Requirements Prerequisite software Microsoft Excel 2000 or higher (English

version) Adobe Acrobat Reader 5.0 or higher. Google Earth 4.0 or higher (to view KMZ files exported by MUSA). Not mandatory.

RAM 128 MB (recommended 1 GB or more, especially for algorithms simulation or to load large mobile data)

Hard Disk space 800 MB (required for a full installation) Processor Pentium III Compatible or higher

Minimum: 500 MHz Recommended: 1 GHz or higher

Operating System Windows XP Professional Windows XP Home Edition Windows 2000 Professional Edition Windows 2000 Server Edition Windows 2000 Advanced Edition Only O.S. English version is supported

PM Counters Analyzer Module System Requirements Prerequisite software Microsoft Internet Explorer 6.0 SP1 or later

(prerequisite for .NET Framework) RAM 512 MB (1 GB recommended) Hard Disk space 2 GB free space Processor Pentium III Compatible or higher

Minimum: 500 MHz Recommended: 1 GHz or higher

Operating System Windows XP Professional SP2 Windows XP Home Edition SP2 Windows 2000 Professional Edition SP4 Windows 2000 Server Edition SP4 Windows 2000 Advanced Edition SP4

Scanmap Data Geographic Datum More than 360 Datum supported (e.g.

WGS84, ED50, NAD27, etc.). See list in DatumID.xls contained in help subfolder

Projection Latitude/Longitude, U.T.M., Transverse Mercator, Gauss-Boaga, Pulkova 1942, Gauss-Kruger, Lambert Conformal Conic, French Coordinate System

File format MS Windows Bitmap 256 colours


Height Data Geographic Datum More than 360 Datum supported (e.g.

WGS84, ED50, NAD27, etc.) See list in DatumID.xls contained in help subfolder

Projection Latitude/Longitude, U.T.M., Transverse Mercator, Gauss-Boaga, Pulkova 1942, Gauss-Kruger, Lambert Conformal Conic, French Coordinate System

File format Binary (see Height Data Appendix for detailed description)


3. INSTALLATION

In the following chapter the installation procedure and license details will be described.

3.1 MUSA Setup Program Run MusaSetup.exe from your MUSA CD. The following installation manager will be shown:

Fig. 3.1

Before installing any program, please press the and the

buttons to read the latest Release Notes and Installation Notes. To correctly install MUSA on your PC please read the following instructions.

3.2 Hardware Key Device Driver Setup It is important to remember that to install MUSA it is necessary to have administrator privilege (in case of problem contact the system administrator).


Before starting with installation procedure please control that the MUSA Hardware Key (Dongle) is inserted in the Parallel or USB port of the computer. The Hardware Key should be always present to work with MUSA.

Press the button to launch MUSA Hardware Key Driver Setup. The Setup Options window appears:

Fig. 3.2 Select Typical, then press Next> .The MUSA Hardware Key drivers will be installed. Wait until all the operations are terminated. If you have received an additional Pixel Hardware Key, press the

button to install the MUSA Pixel Option (used in Load as Pixel function). The SmartKey Driver Installation window will be displayed:

Fig. 3.3


In the Parallel (keyp) section select Install, MUSA Pixel Hardware Key drivers will be installed.

3.3 Main Application Setup It is important to remember that to install MUSA it is necessary to have administrator privilege (in case of problem contact the system administrator) Before installing MUSA, any previous version of the application present in the system should be uninstalled: go in the Control Panel and select Add/Remove Programs. Here the user can remove the program from the computer. Please save any relevant data from the MUSA subfolders before removing them.

Press the button to launch MUSA Setup. The following window will be displayed (it could take few minutes):

Fig. 3.4 Then the MUSA InstallShield Wizard window will be ready for installation procedure.

Fig. 3.5


Select Next>. The Installation Wizard will show a new window:

Fig. 3.6 Select Change to modify the default MUSA installation folder. In order to avoid problems at run time, remember to choose a disk location where MUSA users will have full control privilege. Select Next>, the following review window will be displayed:

Fig. 3.7 To start MUSA installation in the displayed folder select Install. The Wizard window will show the following Status bar:


Fig. 3.8 When the installation procedure is finished the following window will appear:

Fig. 3.9 To terminate the installation process and exit the Installation Wizard select Finish.

3.4 PM Counters Module Installation (Optional) If you have received a License for the optional PM Counters Analyzer Module, you

need to install several extra programs by pressing button. A new setup program will be launched and if necessary the Microsoft .NET 2.0 Framework, Microsoft SQL Server 2005 database and UPA module will be installed on your system. Please verify additional system requirements needed to use the PM Counters Module before this installation step (see Chapter 2).


Wait until all operations will be terminated and remember to disable final option checks: do not run automatically any program! When the installation of the PM Counters Module is terminated go to the next step.

3.5 Latest Update Installation If the Update section

Fig. 3.10 Update section (versions of this example is not important )

is available, it is very important to execute an update of your installation. This step must be executed as the last one action that mean only after the installation of any mandatory or optional items.

Press the button to read information about the latest update

then press the button to update all your installation (MUSA, Optional modules, Projects, Resources, etc). A wizard could ask you where MUSA directory is located on your system:

Fig. 3.11 Chose the correct directory and the press the OK button.


To control the performed operations check the final log window, as shown in the following figure:

Fig. 3.12

3.6 License Update Check if shipped MUSA CD contains the program MusaLicense.exe. In this case you must perform an update of the License contained in you Hardware Key (dongle). In this case, follow the instruction below. Connect your Hardware Key to the parallel/USB port and run MusaLicense.exe program. The following window will be shown:


Fig. 3.13 Warning! License update program can be used only one time and only with the right Hardware Key. Check License ID number provided in the Update Information panel: it must agree with the current one (License ID of the connected Hardware Key) reported in the HW Key Information panel. Update is possible only for matched numbers.

Press the button to update MUSA License. Note: Update Information panel provides other useful information to solve update errors: in particular could be useful to check Driver Present, Connection Test, and Validity Test conditions.

3.7 First MUSA Run It is now possible to perform the first run of MUSA. Push windows Start button, select Program Files menu and click on MUSA icon (you can also use the shortcut link located on desktop). After few seconds the MUSA splash screen appears and after license verification MUSA is ready to work.


Fig. 3.14

3.8 License Details MUSA license details can be shown selecting

Fig. 3.15

or pressing the button on the main toolbar. The License Details window appears, as in the figure below. Many useful information can be found in the window (and must be provided in case of technical support):

Software Version: MUSA application version number.

License ID: It is your unique license number, corresponding also to the Hardware key Serial Number.

Pixel Option: it informs if the Coverage Analysis (as described in 5.8) is available.

PM Counters Option: it reports the version number of the PM Counters

Analyzer (if available).

Expiration Date and Remaining Days

Remaining Activation


Features

Radio Coverage

Load Simulation

Statistic Counters

Radio Parameter Adjustment Features

Others

Fig. 3.16 MUSA functionalities depend on the kind of license owned by the user. In this manual will follow a complete description of the options that are available only with a full license. Please check the License Details window in order to establish what the license allows, and therefore which chapters are applicable.


4. PROJECTS

This chapter provides any details about MUSA workspaces for new and existing project managing.

4.1 Main Toolbar Buttons Overview The following main toolbar buttons allow to access directly some functions connected to the argument treated in this chapter. Their working properties will be described every time it will be necessary to refer to the related function (bold type) in this chapter.

Close File, to close all previous loaded measurement files

Select Project, to open the Select Project Window to change project and/or Network Sites database file

Start Network Manager, to open the Network Manager window

Cell Matching, to open the function window for Scrambling Code, cell id, etc search.

Route Map, to open Route Map visualization tool window

4.2 New Project Preparation It follows a description of all the steps necessary to create a new project. Firstly the following data are needed to prepare the MUSA workspace:

The UMTS network site database in the Excel format described in Appendix, see Fig. 4.1

The GSM network site database in the Excel format described in Appendix, see Fig. 4.2 (optional)

The configuration files coming from the RNCs involved in the project. They could be found in the following formats:

UMTS RNC:

1. OFD

2. ACL

(see Fig. 4.3 and Fig. 4.4 for an OFD and ACL RNC file example)


Alternatively to RNC files some Excel files can be used to obtain the necessary information.

Fig. 4.1

Fig. 4.2

Fig. 4.3


Fig. 4.4

The configuration files coming from the BSCs (optionally) involved in the project. They could be found in the ASC format. An example is shown in Fig. 4.5: Alternatively to BSC file, an Excel files can be used to obtain the necessary information.

Fig. 4.5 Once MUSA is started it opens the Select Project window as displayed in Fig. 4.6


Fig. 4.6 The Select Project window is divided in two sections: Available Projects and Available Networks. As in Fig. 4.6 Utopia is an example project with the standard installation.

Press the button to generate the new project workspace. The window of Fig. 4.7 will be shown.

Fig. 4.7 Enter the Project Name and press the OK button. The window in Fig. 4.8 will appear.


Fig. 4.8

The updated situation is shown in Fig. 4.9. Note that the button on the right side of that window changes its caption property depending on the item selected into the Available Network box of the Selected Project Window.

Fig. 4.9

At this point there are several ways to get the Network, depending on the availability of the RNC configuration files or general Excel Worksheet. Remarkable examples will be described in the next sections.

4.2.1 UMTS Import Procedure from RNC Configuration File

Press the button to start the Import Network Wizard as in Fig. 4.10.


Fig. 4.10

Select the network to import (by clicking UMTS or GSM controls), choose the RNC UMR and BSC BR versions that correspond to the available Network data. Select

source format file and then push the button. The window of Fig. 4.11 appears.

Fig. 4.11

In the new window it is active only the Add RNC function to select the OFD/ACL files that come from RNC downloads.

Select button and the browser window of Fig 4.12 will be opened to allow file searching


Fig 4.12 Select the RNC file (RNC_ofd_file.txt in this example) and the log window of Fig. 4.13 appears.

Fig 4.13 This log is very important to verify if there are errors in the import RNC procedure and to check RNC statistics (UMTS, GSM, and External cells, neighbours, etc.) If the Network Sites database contains sites that belong to different RNCs it is necessary to repeat this step for every RNC OFD/ACL configuration files. Select

button until all the available RNC OFD/ACL files will be loaded.

Once the RNC import procedure is terminated press the button to go to the next section. The Wizard Window will display some information about the loaded RNC data as shown in Fig. 4.14. Selecting the plus symbol displayed beside each element shown in the Import Wizard panel it is possible to explore the tree structure


related to the selected item (up to the O&M parameters when is checked).

The button could be used to search for specific word between the elements of the Import Wizard panel. The same data are accessible using the Network Manager function. Press the next button and the window below will appear.

Fig. 4.14 Now it is possible to load the UMTS Network Site database file. Select button and choose the UMTS Excel File in the browser dialog of Fig. 4.15.

Fig. 4.15 The log window of Fig. 4.16 appears.


Fig. 4.16

Once the UMTS import operation is terminated press the button. The Wizard will display the window of Fig. 4.17.

Fig. 4.17

Press the button to load an optional Neighbours Excel file as the Wizard of Fig. 4.18 shows.


Fig. 4.18 Then the window in Fig. 4.19 appears

Fig. 4.19

Finally, push the OK button and then the button to view the window of Fig. 4.20. Here you can set the Imported Network Name.


Fig. 4.20

The updated situation is shown in Fig. 4.21

Fig. 4.21

4.2.2 UMTS and GSM Network Import Procedure

Press the button to start the Import Network Wizard as in Fig. 4.22.


Fig. 4.22

Be sure to Select both UMTS and GSM controls, choose the RNC UMR and BSC BR versions that correspond to the available Network data. Select source file format and

then push the button. UMTS import will be executed through the same steps described in the previous paragraph (see Fig. 4.11 up to Fig. 4.16). Then the window of Fig. 4.23 appears.

Fig. 4.23

Now it is possible to load the GSM configuration file: select the button and choose the desired file, as shown in the dialog of Fig. 4.24.


Fig. 4.24 Then this log window will appear:

Fig. 4.25

Check this log and the click on the button to go on. At this point the bottom part of the import Wizard window summarize the counters related to the imported files:

Fig. 4.26

In the RNCs box is reported the number of RNC files imported, just like in the BSCs box.


In the following box are reported the UMTS/GSM cells present in the RNC files that match with the cells in the UMTS/GSM Network site database files and the total number of UMTS/GSM cells present in the RNC database (eventually in brackets is reported the number of cells that are present in the RNC as neighbour declaration toward RNCs not imported in the New Project Import procedure). In the last box are reported the UMTS/GSM neighbours available in the RNC files that match with the cell in the UMTS/GSM Network sites database files and the total number of UMTS/GSM neighbours present in the RNC database (eventually in brackets is reported the number of cells that are present in the RNC as neighbour declaration toward RNCs not imported in the New Project Import procedure).

When all import operations are finished press the button to view the window of Fig. 4.27. Here you can set the Imported Network Name.

Fig. 4.27

4.2.3 Import Procedure from Excel files When the RNC configuration files are not available it is possible to import the necessary information from some Excel files. Some fundamental information are needed to build up these files. The UMTS/GSM Network sites database described in the previous section are necessary as well.

The first file corresponds to the minimum UMTS parameter database for MUSA purpose. Its structure is displayed in Fig. 4.28. The column titles name and column order are mandatory.


Fig. 4.28

Apart the first two columns which content it is very obvious, in the other columns are requested the following information:

o (iub) sc_pcpi : Primary CPICH Scrambling Code o (iub) pwr_pcpit: Maximum Primary CPICH power o (iub) max_dltp: Maximum Node Power o (iub) uarfcn_dl: Downlink channel

In the above list are considered only the mandatory column. Any other column added to the file will be considered as parameter. Be careful to use the correct title to specify other parameters, using the name reported in the Network Manager window. The filename should be:

___3GPARAM.xls

where

is the name typed in the new project box. 3GPARAM is a mandatory word

For the meaning of the terms and please refer to the equivalent terms of the UMTS Network file described in Appendix.

The second file is optional and corresponds to the UMTS parameter on RNC bases and a sample is shown below:

Fig. 4.29


In the above figure are highlighted only the mandatory column. Any other column added to the file will be considered as RNC parameter. Be careful to use the correct title to specify a parameter, as they are indicated in the Network Manager window. The filename should be:

___3GRNCPARAM.xls

where

is the name typed in the new project box. 3GRNCPARAM is a mandatory word

For the meaning of the terms and please refer to the equivalent terms of the UMTS Network file described in Appendix

The third file corresponds to the Neighbours database. Its structure is displayed

in Fig. 4.30. The column titles name and column order are mandatory.

Fig. 4.30 For every site and sector specified in the first two columns all the neighbours contained in the Network RNC Database should be reported with the displayed format: neighbour site name (column three) and Neighbour site sector (column four). The filename should be: ___NEIGHBOURS.xls where:

is the name typed in the new project box. NEIGHBOURS is a mandatory word For the meaning of the terms and please refer to the equivalent terms of the UMTS Network file described in Appendix. This file is optional but it is strictly necessary for the Neighbours Analyzer tool (AdA) that doesnt work without the information contained in it.

A fourth optional file is the equivalent of the minimum UMTS database for the GSM Network. The structure of the file is shown in Fig. 4.31.


Fig. 4.31

The name of the file should be:

___2GPARAM.xls

GSMPARAM is a mandatory word. For the meaning of the other terms refer to previous descriptions.

If the described files are available it is possible to select [Import] in the Available Networks box of Select Project window of Fig. 4.9. Press Import. The Import Excel Wizard tool starts with the window shown in Fig. 4.32.

Fig. 4.32


Select a UMR version. If measurements and Network data contained in the just described excel files are related to a not-Siemens network doesnt matter what version is chosen. Otherwise this choice should be consistent with the used data.

To continue press the button. The window of Fig. 4.33 appears.

Fig. 4.33

Select the button. It will be displayed the browser window of Fig. 4.34 to choose the UMTS Network Sites database file.

Fig. 4.34


Once the file is selected the Import Excel Wizard displays the log window of Fig. 4.35.

Fig. 4.35

The updated situation is shown in Fig. 4.36.

Fig. 4.36


Press the button. In the window of Fig. 4.37 it is possible to choose the minimum UMTS database file.

Fig. 4.37

Select the button. The browser window in Fig. 4.38 appears.

Fig. 4.38

This window will appear:


Fig. 4.39

Press the button. The Wizard displays the following window:

Fig. 4.40

If it is available a UMTS RNC parameters database file, it is possible to select it

pressing button.

Press then the button and the Wizard displays the windows of Fig. 4.41.


Fig. 4.41

If it is available a minimum GSM database file it is possible to select it pressing

button. Then just follow the steps described for the minimum UMTS database file, otherwise

select the button. The windows of Fig. 4.42 will be displayed.

Fig. 4.42

Press the button if it is available the Neighbours database file. Select it in the browser window in Fig. 4.43.


Fig. 4.43

Once the file is chosen and after having pressed the Open button on the information window, the window of Fig. 4.44 will be displayed.

Fig. 4.44

Press the button to view the window of Fig. 4.45. where you can set the Imported Network Name.


Fig. 4.45

4.2.4 Network Import Results When import phase is concluded (using one of the previous procedures) MUSA generates the new site database file

.ns file

stored in the MUSA folder

\project\\Environment\Network.

4.2.4.1 Shared Scrambling code verification After the import phase, selecting Network\Export Sharec SC Report

it is possible to generate the file

_SharedSC.xls stored in the MUSA folder

\project\\Environment\Network


This file is useful for a preliminary RNC database analysis related to the cells Scrambling Code re-use to identify before (and solve) the measurement campaign critical situation. In this file for every Scrambling Code are reported all the cells that in the UMTS network site database file are declared with that SC and the inter-cells distances. After the selection of this feature, the Tool requests to indicate a critical distance. It will be used to highlight in red color cell pairs using the identical scrambling code and with a lower distance.

A next dialog asks the user if the report will be made only by cells with shared scrambling code:

The following pictures show the report, composed by Matrix report.


and Vectorial report:

4.2.5 MUSA Folders Description MUSA folders structure it is composed by:

\Bin \Help \Projects \Resources

The \Bin folder contains some operative reserved files. The \Help folder contains this MUSA manual and other useful help files, like measurement samples and network templates. The \Resources folder contains six subfolders:

\Aerials \ExportDefs \Legends \Network \Script \Adjacents

\Resources\Aerials is the antenna database folder where all the antenna pattern files used for the optimization function are stored (see Appendix).


The directories \ExportDefs, \Legends, \Network, \Script and \Adjacents contain the default files that MUSA will copy in new project folders every time that a new project will be created. The workspace for a new project will be created in the directory \Projects\ of MUSA. In this new folder there are five main directories:

\Environment \Measurements \Results \Simulations \UserSettings

Those are the default folders that MUSA uses to store and find files useful for its several functions. User may decide to create and use any other folder if desired. In the following folders and relative subfolders meaning and operative function will be described.

\Environment

Environment\Events : default folder for user defined event files .evn Environment\ExportDefs: in this folder are saved by default the Export Data

Definition files Environment\Heights: default folder for terrain heights data Environment\Indicators: default folder for network list files .nl, saved by Network

Manager or Algorithm Simulations module Environment\Legends: default folder for legend files .leg Environment\Logo: default folder for logo image for Cell Identity Card

generation Environment\Maps: default folder for Scan Maps files Environment\Network: here the UMTS and GSM Network Sites database files

and the RNC configuration files are expected Environment\Script: here are stored the files needed to generate warnings and

statistics Environment\Vectors: default folder for vectors data (e.g. roads, railways, rivers,

coverage boundaries)

\Measurements

\Measurement\Scanner: default folder for Scanner Measurement files \Measurement\Mobile: default folder for Mobile Measurement files \Measurement\Netdata: default folder for user defined Network Data Excel files \Measurement\PM: default folder to store performance measurement files

(ASN.1 binary format) used by PM Counters Analyzer.

\Results


\Results\Adjacents: default support folder for Neighbours Analyzer function \Results\Bitmaps: default folder for every bitmap image saving operation

performed in MUSA \Results\CellBitmaps : default folder for Cell Bitmap Generation function files

saving \Results\CellIdentityCard: default folder for Cell Identity Card Generation

function files saving \Results\Exports: default folder for every Export Data operations performed in

MUSA \Results\Islands: support folder for reports and graphs image files generated by

pixelling process and Coverage Analysis Islands options \Results\Optimization: default folder for optimization parameter modification files

.op \Results\Overlapping: support folder for reports generated by Pixelling process \Results\PilotPollution: support folder for reports and graphs image files

generated by pixelling process and Coverage Analysis Pilot Pollution options \Results\PMReports : support folder for reports generated by PM Counters

Analyzer \Results\Statistics: support folder for report excel files generated by Statistical

Mode function

\Simulations

This folder keeps trace of all the scene created in the Algorithm simulations SIM module (each subfolder represents a scene). The user could copy any subfolder to transfer scenes between two projects or computers.

\UserSettings

support folder for some MUSA reserved operative files and the two user-configurable files mobile_ex.txt and mobile_col_ex.txt

4.3 Project Selection This section is dedicated to the procedures necessary to open a predefined Project. When MUSA is started, the window Select Project in Fig. 4.46 appears.


Fig. 4.46 In the left box (Available Projects) it is possible to select one existing project previously created with the procedure described in section 4.2. In the right box (Available Networks) for the selected project are shown all the Network files available.

Choose the desired Project and relative Network file then press the button to access MUSA functions. It is possible to access a different project and/or a different Network file when MUSA is still working as well. Firstly it is necessary to close all previously loaded files selecting Measurement\Close:

Fig. 4.47

Now, to access the Select Project window use Network\Select Project


Fig. 4.48 The window of Fig. 4.46 appears. At this point just follow the previously described steps. When the import Project operation is achieved two new files are generated or re-generated:

.txt _netverify_[UTM].txt

This file is stored in the MUSA subfolder: \project\\Environment\Network.

4.3.1 Special cases In the previous paragraphs we didnt stressed some particular cases. For examples, if

you select a project and then push the button in the Select Project window, all project data are correctly deleted. If a project is deleted in any other way (e.g. windows subfolder operations) MUSA will inform you as in Fig. 4.49.

Fig. 4.49


In this case, select the missing Project and click on the button to completely and correctly delete it. MUSA can also detect if you copy or rename the entire project directory. However, compressing and erasing a project is considered a valid and detected operation, as shown in figure 4.50: Berlin project is reported as .

Fig. 4.50

An other special case regards the selection of an Empty Network: it could be useful when you need to load data files or analyze PM files and it is not possible to import network information.

Click on button and the window in Fig. 4.51 will appear.

Fig. 4.51


Choose the correct UMR and BR versions and push the finish button to start to work using the Empty Network.

4.4 Network Manager MUSA Network Manager allows to read, and in same cases to modify, cell related parameters. To access this function select Network\Network Manager

Fig. 4.52

the window of Fig. 4.53 appears.

Fig. 4.53

Network Manager window description:

Net Viewer: in this box all loaded RNCs, BSCs, cells, and neighbours are listed. Selecting one RNC it is possible to explore all sites and cells that


belong to that RNC. Selecting one cell it is possible to check all the corresponding neighbours declarations and activate the information panel in the right side of Network Manager window. If a GSM network files is imported all the GMS neighbours declarations are available as well. For the GSM part only the O&M parameters of UMTS system related to 2G managing are reported.

Net Element View: when one cell is selected in the Net Viewer section, in

the Net Element View box are available some data: o Site ID: site name [modifiable] o Address: selected cell address (if available in the UMTS Network

file) [modifiable] o Cell ID: selected cell Alias name [modifiable] o Antenna: selected cell antenna model o Tilt. Elet. :selected cell electrical downtilt [modifiable] o Tilt Mec. :selected cell mechanical downtilt [modifiable] o Azimuth: selected cell azimuth [modifiable] o Ht: selected cell height referred to ground level o EIRP: selected cell EIRP (if available in the UMTS Network file) o Latitude: selected cell latitude o Longitude: selected cell latitude

Parameter Sections: depending on the selected cell in this box some

information are displayed: o Group: this field reports the list of available O&M parameter group

for the selected cell o Parameter name: in this field are listed all the O&M parameters of

the specific group selected in Group o Parameter Definition: here are reported some general information

about the O&M parameter selected in the Parameter Name drop down menu, available through the RNC files loaded (see section 4.2). In the text box a short description of the selected parameter is displayed. In the following menu it is possible to change the parameter value:

Fig. 4.54

After any modification press OK. The starting value is always reported in Old Val, the modified value will be displayed in red. The default RNC O&M parameter value (if it is defined) is reported in Default.

Remark: the content displayed in the Network Manager window is derived from the RNC configuration files. When a parameter it is not found in those files, the Network Manager reports the default value for the UMR version selected in the Import Wizard window (Fig. 4.10, Fig. 4.22).


The button at the bottom of the window permits to export a text report with all modified parameters (each row will contain the changed network element, group, parameter name, old value and new value).

The button permits to restore the original configuration, as imported by the Wizard.

4.5 Cell Matching Selecting from the main menu Network\Cell Matching

Fig. 4.55 the window reported in Fig. 4.56 will be shown.

Fig 4.56

This window is useful for a fast search of the associations between Cell Alias and Scrambling Codes (SC). Typing the Scrambling Code in the SC box or the Cell Alias in the Alias box and then pressing Match, it is possible to obtain the corresponding associated value. The SC value could be written in the decimal, hexadecimal or x16 system (Scrambling Code multiplied by 16, as reported by some trace software) in the relative dialog box. MUSA automatically converts the written number in the other systems. In Fig. 4.57 and Fig. 4.58 are shown respectively an example of SC search and Alias Search.


Fig. 4.57

Fig. 4.58

In case of an Alias search in the SC boxes is reported the value of the SC associated with the written Alias and in the Alias List all the cells that match with the SC displayed. In the example of Fig. 4.58 the typed value is UT001U. The Cell Matching function reports the SC 105 that corresponds to the cell UT001U_2 (founded in the UMTS Network Site database file) but in the Alias List is reported also the Alias UT240U_1 that has the same SC of UT001U_2. In the Alias box is possible to edit a part of the searched Cell Alias. But when the Exact Search check box is selected the written Cell Alias has to be strictly equal to the one searched, otherwise no values are obtained from the Cell Matching function.


4.6 Cell Inversion detection If some cell inversions (i.e. errors in feeders coupling) are detected it is necessary to apply the following procedure to avoid problems to identify the cells in post analysis phase. To detect if a possible cell inversion is present in the investigated network, select the Show all site cells function in the Route properties menu of the Route Map option (please refer to chapter 6 for further details):

Show all site-cells The result is that for a selected site all the samples that belong to it are displayed in the map as shown in the example of Fig. 4.59.

Fig. 4.59

Analyzing the coverage area of the site sectors with the help of the color used to distinguish the different cell, it is often possible to individuate if a specific site sector has a coverage area that clearly belongs to another cell. Observe for example the first and second sector of UT502U in Fig. 4.59. MUSA associates red samples to the first sector (see legend). In the available UMTS network site database file the relative Scrambling Code is declared for UT502U cell one. But during drive test campaign this SC is clearly measured in the second cell competence area. The inverted situation is verified also for the second cell of UT502U. This is a typical case of cell-inversion. To correct a detected inversion for post processing analysis it is necessary to access the Network Manger Window as described in section 4.4. Here it is possible to exchange cell Scrambling Codes. It is very important to remind that the situation


has to be corrected in field. The solution proposed here is useful only for radio coverage analysis purpose avoiding recollecting measurement data. Once the Network Manager window is opened apply these steps:

1. Select the first cell involved 2. In the Iub group select the parameter primary CPICH scrambling code (see

Fig. 4.60) 3. Replace the value reporting the Scrambling Code of the cell with which the

coverage area has to be exchanged, then press OK 4. repeat step 1,2 and 3 for the other cells involved

To make the modifications definitive in MUSA it is necessary to reload the project and the network file as described in section 4.3. IMPORTANT: when an inversion is corrected with the described procedure is necessary to re-generate the pixel file (see chapter 5) before starting with the post processing analysis. The result is displayed in Fig. 4.61.

Fig. 4.60


Fig. 4.61


5. SCANNER DATA LOADING AND PROCESSING

MUSA allows managing of scanner measurement files. In this chapter will be highlighted the available options dedicated to scanner data load and processing. With MUSA it is possible to manage the scanner data in different ways:

Load single scanner data file Combining several scanner files in one single file to be loaded as result Process the data on pixel base (square territory element) and load the

results Cut the samples inside polygonal areas

In next sections each possibility will be clarified.

5.1 Main Toolbar Buttons Overview The following main toolbar buttons allow to access directly some functions connected to the argument treated in this chapter. Their working properties will be described every time it will be necessary to refer to the related function (bold type) in this chapter.

Open Measurements: to open Scanner and/or Mobile files

Close File, to close all previous loaded measurement files and release memory

Export Tabbed Text, to open Data Export window

Queue Scanner Files, to combine several scanner files in a single file

Polygonal Cutting, to extract measurements falling inside a polygon

Maximum Number of Servers, to import all Servers data or a predefined number of them

Coverage Simulation, to access the Optimization tools

Load as Pixels, to perform a pixel based processing of collected data

Time Chart, to open Time Charts visualization tool window

Route Map, to open Route Map visualization tool window

Distribution and CDF, to access Distribution and CDF window

Joint Distribution, to access the Joint Distribution window

Neighbours Analyzer, to open neighbours optimization tool

Islands, to perform Island analysis


Pilot Pollution, to perform Pilot Pollution analysis

Cell Identity Card, to create Cell Identity Cards

Coverage Analysis Quality Indicators, to calculate Level and Interference, Best Server Area Fragmentation and Pilot Pollution quality indicators

Calc Between messages, to calculate how many times a sequence is repeated correctly inside the measurement.

Window Synchronization, to synchronize all the opened windows

5.2 How to load a Scanner file Once the project has been selected as described in chapter 4, to enable loading of scanner files select Scanner\Enabled.

If this function is not checked, MUSA doesnt allow Scanner Data loading. This is valid also for Mobile files (see chapter 12). Therefore, the user could decide to import only Scanner files, only Mobile files or both. In the last case, this kind of import is useful only for files recorded at the same time in order to compare the results of the two measurement systems (see chapter 12). In this chapter we concentrate only on Scanner files. The scanner data are loaded using the reference system WGS 1984, as default. It is possible to use a different system. To enable this function in the main toolbox select Measurements\Ask Datum


If the Ask Datum function is enabled, before to start the loading phase the Select the coordinates Datum window appears (Fig.5.1):

Fig.5.1 Here it is possible to select the wished datum. A complete datum list is available in the DatumID.xls file, contained in the folder \Musa\Help.

5.3 Load Single File Select Measurement\Open

to load a single Scanner file. The Open Scanner File window will be displayed (Fig.5.2):


Fig.5.2 MUSA is able to load several Scanner file types: Auto detect Scanner files ( *.se*, *.sgf, *.spx, *.txt, *.xls, *fmt, *.dat)

StangaE Measurement Files (*.se*)

Agilent E6474A export (*.txt)

Scanner General Files (*.sgf)

MapInfo Area Export (*.txt)

Pixel Files (*.spx, *.txt)

FMT (Top N Pilot) Export (*.fmt) TEMS Investigation 6.1 files

Anritsu ML8720B Unspecified Long format (*.dat)

Rohde&Schwarz Export (*.txt)

Nemo Outdoor Scanner (*.fs1, *.fs2)

CSV Scanner file (*.csv)

Flash-OFDM FMDM FMLP file (*.csv)

DVB-H LG, N77, etc. file (*.txt)

For more details about Scanner file types please refer to Appendix. Choose the wished file and file type and click Open. MUSA will show the import status bar of Fig.5.3.


Fig.5.3 If the Mobile data load is enabled another window will be displayed to select the desired Mobile file (see chapter 12). The final result of the import operation is that a new Measurement Data table is displayed as in Fig.5.4. If also a Mobile file has been loaded, the table represents a merge of the two kind of information. In this case, the table will be divided in two sections by a vertical splitter. In the left side all Scanner data are presented, on the right side there are all data related to the Mobile file (see chapter 12). At the bottom of the Measurement Data window is displayed the files loaded status:

Mobile not loaded and Packet not loaded notes on status bar indicate that only a Scanner file has been loaded. Otherwise MUSA will show the names of all files currently loaded.

Number of records loaded

Project name

Network file loaded

Scanner File Name


Fig.5.4 In the From column is indicated the source of the information for each row (S = Scanner; M = Mobile, P = Packet). In the Time column is indicated the absolute time of collected data, or a reference time used by MUSA to order on time basis scanner data and mobile data (if simultaneously present). The Marker and Remark columns could help to mark a specific point and then to display it on a map. If some markers have been inserted during the measurement campaign they will be displayed automatically in the Marker column. To modify a marker name, to insert a new one or to delete an existing one, double click in the related cell in the Measurement Data table. The window of Fig. 5.5 will be displayed to edit the marker.

Fig. 5.5

Once the name is typed, select OK. The result obtained is like the one presented in Fig. 5.6. To delete a Marker double click on the relative cell then delete the word that is automatically displayed in the window of Fig. 5.5 and press OK.


Fig. 5.6 The handling of data in the Remark column is equivalent to the one just described for the Marker column. In the Warning column are displayed warning messages as defined in the warning.txt file. This file is stored in the following folder: \Projects\\Environment\Script It allows the user to define a sequence of messages/data in order to generate a specific warning text every time the sequence defined will be found in the messages/data of the Measurement Data table (see also section 13.3) or every time a deviation from the same sequence will be encountered, as configured in the file itself. Please refer to the section 8.6.2 or in Appendix for details on warning.txt editing. Every sequence defined in the warning file has a text name, reported in Warning column of the Measurement Data table as result of the research on the defined sequence with the modality configured in the script file. The warning match and count operations are performed every time that a new measurement file is imported. If the user need to re-execute the script file after with a Measurement file already loaded (for example after a re-editing of the warning.txt file) please select Tool\Warning Generation


and the Warning Column of the Measurement Data table will be updated. In Lat and Long columns are reported indications about geographic position of data collected in terms of Latitude and Longitude. In the following columns appearing in the Measurement Data table are reported all the information related to the measurements recorded by the Scanner equipment like RSSI, SC_n, RSCP_n, EcIo_n, etc., where n indicates the nth best server. Measurement Data window buttons description:

Minimize on bottom , to minimize the window.

Apply function, to calculate functions for a specific data column. Pressing this button the following dialog appears:

The user can apply an Offset function, the Last Value function (data filling using last available value) or Same Time function (similar to Last Value, but using only values with the same timestamp).

Multiple selection, to select many cells in the table for copy & paste operation. When this button is down, the user can highlight the interested cell using mouse click. When the selection is finished right click on the table to copy all data in windows clipboard. It so possible to paste these values in other application (e.g. Microsoft Excel).

Search in Scanner, to enable search window. Type the value to search in the Measurement Data table.


Load/Save Modified Marker, selecting this two buttons it is allowed to load and save Markers inserted and/or modified by the user during the analysis section. When user chooses to save the markers, MUSA creates a new .mdm in the folder: \Projects\\Measurements\Scanner where is the same name of the loaded Scanner measurement file (e.g. UT4_201204_p1).

5.4 Queue scanner files When there are several scanner files of the same project, MUSA provides the possibility of combining all the data collected in a single file. This step could be necessary to use the pixel processing procedure on a whole network collected data and it is automatically accessed when it is selected the Load as Pixel function (see 5.5). To prepare a merged file select Queue Scanner Files in the main toolbar

In the Browse for Computer window (Fig.5.7) select the folder containing the files to merge, then press OK.


Fig.5.7

The Queue Scanners Files window will appear, as shown in Fig.5.8.

Fig.5.8 It is possible to choose:

Mode: there are two different combining modes: As Offset to start with a time

of 00:00:00.000, deleting any time gap between files, or File Date-Time to maintain the original time (and date) of each measurement point. The As Offset mode is useful when the target application will be the Algorithm Simulations (see Chapter 11). File Date-Time mode is useful for Mobile Data merging.

File type: selecting one of the supported file types, MUSA will show the Available files for the chosen format.


Pressing the (Select All files) button it is possible to select all files present in the folder listed in the Available Files list, as in Fig.5.9.

Pressing the following (Select File) button it is possible to select the available files one by one. Files candidate for the queuing process are shown on the right in the Selected Files box, accompanied by the time and date. Other available control buttons:

(Unselect All Files) helps to eliminate all selected files, clearing the Selected Files section.

(Unselect Files) eliminates the highlighted file in the Selected Files section.

Fig.5.9 The Selected Files section reports all selected items with their time and date.

Using the (Move Up, and Move Down) buttons, it is easy to move the highlighted file in Selected Files section. After a movement the Time-Date field might be to modified (see later).

In the File Date-Time combining mode it is mandatory to get a chronologically sorted list. Since the time and date information provided for each file is obtained in many different ways (depending on the instruments) it is important to check (and eventually adjust) any wrong information. The user can modify the Time-Date file information in the Selected Files to accomplish this result.


Every time the label informs about the time sorting of the selected files (it becomes red if the list is not regular).

Pressing the button, the date-time information is automatically altered (starting from the second selected file) to produce a chronologically sorted list. On the contrary, time and date information of the first file is kept valid. This button does not change the file list order, it only modifies the Time-Date field.

Pressing the button after having selected a file in the list, a drop-down calendar appears and lets the user to specify a new date:

Instead of pressing the button the user can directly double-click the Time-Date information of the highlighted file.

Selecting the button the selected files list will be sorted by Time-Date, while

pressing button the list will become sorted by Filename. Be careful: these two buttons could alter the chronological order of the selected files.

Pressing the button, the standard file dialog Locate target file will be shown, by default in the Scanner folder of the current project, as in Fig.5.10:


Fig.5.10 In this window it is possible to choose the combined filename and the folder where to save it. Press Save to confirm. Press the Queue button in the Queue scanner files window (Fig.5.9) to start the merging process. MUSA will create a Scanner General Files (*.sgf), that can be regularly re-loaded by the tool.

5.5 Pixel Processing In this subchapter the pixel processing feature for UMTS scanner data is depicted: the description of general pixel processing function is reported in the next chapter. MUSA is able to perform a pixel based processing of the collected data in order to mitigate fast fading propagation effect. This kind of averaging has several advantages and can be used to analyze coverage and interference from a statistical point of view, making distribution, cumulative distribution function (CDF), maps, etc. It is also useful to discover irregular coverage fragmentation (Islands) and pilot pollution. In this chapter it is supposed that Islands and Pilot Pollution concepts are well known to the user (see 5.8). The measurements are analyzed and processed on a regular grid: the elementary square cell of this grid is called Pixel. If the owned license comprises this feature, the Load as Pixel function is enabled. From the main menu select Option\Pixel Settings


to enter the parameters that MUSA needs in order to perform the pixel based processing.

The Pixel Options window (Fig.5.11) appears:

Fig.5.11

In the General menu it is possible to set the following general parameters:

Pixel Dim: pixel dimension in meters (default value = 10 m).

Preprocessing: if checked it enables a pre-processing of collected data on a grid with an elementary cell smaller than the final one set in Pixel Dim field (default = 1 m). All samples falling in a pixel of the dimension set in the Preprocessing field are joined to obtain a single spatial sample used by the main pixel processing. It is very useful to avoid the traffic light effect (averaging in a single spatial sample several measurement collected when waiting stopped in one point)

Min Signal: minimum RSCP level [dB] to be considered in the processing. All measurements with RSCP level less than the threshold set in this field are discarded (default = -140 dB).

Sort: criterion to define the Best Server cell in a pixel. If By count is checked, it will be elected Best Server in a pixel the cell emerging as Best Server in most samples falling in that pixel, independently of the signal level (default); if By level is checked, it will be elected Best Server in a pixel the cell with higher RSCP level, independently of the number of occurrences of the cell in that pixel. In the Island menu (Fig.5.12) it is possible to set the Islands analysis related parameters:

Sorting: Islands sorting criterion for the choice of the group of cells to be reported according to the number set in the field Cells of the Filters box. If By presence is checked, Islands will be sorted by area dimension (default). If By Distance is checked, Islands will be sorted by distance from the Best Server cell.

-140


Filters: filtering criteria on Islands

Cells: maximum reported number of nearest sites to each island, sorted by ascending distance or maximum reported number of max presence sites to each islands, sorted by area dimension; Distance: the minimum distance, in term of pixels, that is required in order to consider two or more adjacent islands related to the same serving cell as an unique big island; Surface: the minimum surface, in term of pixels, that is required in order to consider a group of adjacent pixels as an island There are 3 filtering criteria as default: 15,1,1; 15,1,2 and 15,2,2. To add a new filtering criterion, enter the wished values in Cell, Distance and Surface fields, then click on Add Filter button. To delete an existing filtering criterion, select the wished one in the Filters list, then click on Delete Filter button.

Fig. 5.12


Fig.5.13

In the Pilot Pollution menu (Fig.5.13) it is possible to set the Pilot Pollution analysis related parameters:

Number of cells: maximum number of polluter cells per Pilot Pollution class reported for each Best Server cell (default = 5).

Pilot Pollution Classes: Very strong, strong and low Pilot Pollution states. The comparison of the P-CPICH level between the Best server cell and the polluting ones is performed, then the difference between the cells is compared with three different thresholds chosen according to the Add and Del thresholds in the intra-frequency handover (default: from -4 to 4, from 4 to 9, from 9 to 20).

Fig.5.14


In the Adjacent menu (Fig.5.14) it is possible to set the parameters related to neighbours analysis. This menu is divided in 2 sections. The Add Section contains the settings to create the list of neighbours to add. The Remove Section contains the settings to create the list of neighbours to remove. In each section it is possible to define the following parameters (see also chapter 9):

RSCP: if checked, for each pixel the comparison between the Best Server cell and all the other detected cells is done on RSCP level (default for both the sections).

Ec/Io: if checked, for each pixel the comparison between the Best Server cell and all the other detected cells is done on Ec/Io level.

GAP value: minimum (Add Section) or maximum (Remove Section) difference from the Best Server cell, referred to the selected parameter (RSCP or Ec/Io), allowing an adjacent cell to enter the list of neighbour relationships to add/remove (defaults = 4 dB (min gap); 20 dB (max gap)).

Threshold value: minimum value, referred to the selected parameter (RSCP or Ec/Io), allowing a cell to be considered; in other words, all the cells with level below this threshold will be discarded (default = -115 dBm).

Max number of cells: maximum number of reported cells (default = 20). In the Overlapping menu (Fig.5.15) it is possible to set the parameters related to Overlap analysis (for each cell present in the measurements the overlap matrix reports the number of times that all the other cells have been detected in the same pixel, giving a figure of how cells overlap each other):

Overlapping Type: type of report format. The output data can be reported in a Vector form (default), or in Matrix form.

Consider value of: parameter used to evaluate the overlap. RSCP (default) or Ec/Io can be used.

Threshold Value: minimum value, referred to the selected parameter (RSCP or Ec/Io), allowing a cell to be considered; in other words, all the cells with level below this threshold will be discarded (default = -120 dBm).

Order by: sorting criterion. Output data can be sorted by Number of pixels of overlap (default) or by cell Name.


Fig.5.15 After having defined all the settings, it is possible to load the measurements performing the pixel based processing. Select Scanner\Load as Pixel from the main menu.

Pressing Yes in the Information window of Fig.5.16, an Open SGF File window (Fig.5.17) is opened to load existing queued files (*.sgf).


Fig.5.16

Fig.5.17

Clicking Open MUSA will load the selected file performing the pixel based processing in background, according to parameters values set in Option\Pixel Settings. Selecting No in the Information window (Fig.5.16), the Browse for Computer window will be opened (Fig.5.18):

Fig.5.18


Select the folder containing the files to merge, then press OK. The Pixel Queue Scanners Files window will appear, as in Fig.5.19. Repeat the procedure shown in section 5.4.

Fig.5.19 The Program in elaboration window of Fig. 5.20 shows the status of pixel based elaboration.

Fig.5.20 At the end, MUSA creates the following output files in the appropriate folder, as listed below:

\Projects\\Results\Islands

islands 15_1_1.pxl islands 15_1_2.pxl

islands 15_2_2.pxl user defined filters

(see Appendix for detailed description of these files)

\Projects\\Results\PilotPollution


PP_Polluted.pxl PP_Polluter.pxl (see Appendix for detailed description of these files)

\Projects\\Results\Overlapping

OverlappingVector.pxl (OverlappingMatrix.pxl)

\Projects\\Results\Adjacents

Add.pxl Remove.pxl ScannerDetected.txt (updated at every scanner loading)

\Projects\\Measurements\Scanner [email protected] [email protected]

...\Projects\\Environment\Network

_netverify_[UTM].txt

There will be several files describing Islands situation, one for each criterion set in Options\Pixel Settings; 2 files describing Pilot Pollution situation, one for polluter cells (interferers) and one for polluted (interfered); 1 file describing Overlapping situation, in vector or matrix format, depending on Overlapping Type set in Options\Pixel Settings; 3 files for neighbours optimization: one with information related to neighbours to add, one with information related to neighbours to remove and one containing all scanner detected cells (updated at every scanner loading). These files are used by MUSA Coverage Analysis tools (see 5.5) and MUSA Neighbours Analyzer tool (see chapter 9) to produce final reports and graphs about Island, Pilot Pollution and neighbours. Finally, there will be one *.sgf file with all the measurements files queued (if has been done the queuing procedure) and, one .*spx file obtained processing on pixel base the *.sgf file. Note: the Pixel elaboration could be performed on any Scanner measurement file already opened (selecting Scanner\Load as Pixel), but only if that file is not a pixel based data (*.spx).

5.6 Area Cutting

5.6.1 Polygon Definition After the measurements are combined in a single queued file, it could be necessary to extract a subset of collected data falling in areas of interest. This selection is made possible drawing a polygon delimiting the area under investigation and importing only the measurements inside the polygon itself.


Before the polygon definition, make sure that only the Scanner files loading is enabled (Mobile and Packet files loading must be disabled), as explained in section 5.2. Then, proceed to measurements file loading (could be a single file, a queued file or a .*spx file), as explained in section 5.3 , 5.4 and 5.5. On main menu select View\Route Map

to display the Route Map window, then select a parameter to be plotted on the map, e.g. RSCP_1s (see chapter 6 for details). Press the Polygon Definition button to activate the related toolbar in the lower side of Route Map window as shown in Fig.5.21. It follows a short description of the items available in the Polygon definition toolbar, reported in Fig. 5.22.

Polygon Definitions, to open the polygon definition tool

Load Polygon, to load a previously saved polygon

Save Polygon, to save a polygon

Clear All Polygons, to delete all the polygons drawn on the Route map

New Polygon, to draw a new polygon

Remove Points, to delete a point on the polygon border.

Edit Points, to display, add or modify the position of a point on the polygon border

Close Polygon, to close (in geometrical sense) an open polygon

New status: the tool is ready to draw a new polygon

Select status: the tool is ready to select basic points of the polygon


Edit status: the tool is ready to edit the positions of the basic points

Delete status: the tool is ready to remove a basic point

Area: indication of polygon area [Km2]

Fig.5.21

Fig.5.22 To draw a new polygon press the New Polygon button: the tool goes from a Select status to a New status and this condition will be indicated on the Polygon definition toolbar. Then, start to define the polygon perimeter fixing the basic points by means of mouse left key, as shown in Fig,5.23. The inserted points will be joined by a red line.


Fig.5.23

To close the polygon press the Close Polygon button: the first and the last point drawn will be joined to close the polygon. Consequently, the polygon area will be calculated (the result is reported on the Polygon definition toolbar) and highlighted on the map, as in Fig.5.24.

Fig.5.24 It is always possible to change the position of the basic points, and therefore the form of polygon, to remove a point and to add new points.


To change a point position, press the Edit Points button: the tool goes from a Select status to an Edit status and this condition will be still indicated on the Polygon definition toolbar. At this point, select the point to move clicking on it. The selected point becomes blue, as shown in Fig.5.25. Drag the selected point to the new position.

Fig.5.25 To delete a point, press the Remove Point button: the tool goes from a Select status to a Delete status. Then, double click on the point to remove. To add a new point, press the Edit Points button: the tool goes from a Select status to an Edit status. Then, double click on the position of the new point to add. After the polygon definition, press the Save Polygon button to save the polygon just drawn. MUSA creates a polygon.plg file in the subfolder \Projects\\UserSettings. At the moment it is possible to save only one polygon per project. All the changes done on the polygon will be re-saved on the same polygon.plg file. To reload a previously saved polygon, press the Load Polygon button. The polygon will be displayed on the Route map. Now it can be modified as described in this chapter and then re-saved. Note: the polygon can be defined also without loading any measurements (considering other criteria like cell clustering) opening the Route Map window after the project selection.

5.6.2 Measurements polygonal cutting To load only the measurements falling in a polygon previously created and saved, it is necessary first to close all the opened measurements selecting in the main menu Measurement\Close:


Then, select in the MUSA main menu Measurement\Polygon Cutting

to enable the selection of measurements contained in the polygon delimited area (i.e. inside the polygon described in the polygon.plg file). Finally, select Measurement\Open:

to load the file containing the measurements of interest. If the Polygonal Cutting button is pressed

Date post:	13-Oct-2015
Category:	Documents
Upload:	mohammad-s-chebbo
View:	105 times
Download:	2 times

MUSA 4.6 User Manual v2_3

Documents