MUSA 4.6 User Manual v2_3

5/24/2018

MUSA 4.6 Use r Ma nua l v2_3 - slide pdf.c om

Release 4.6

USER MANUA L

Version 2.3 June 2007

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

Issued by Nokia Siemens Networks 20126 – Viale dell’Innovazione, 3 – 20126 MILANO (Italy)

CMO WSE

http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

1/480

5/24/2018


Docum ent Revision Histor y Status

Issue

Date

Draft Release Release Draft Release Release Draft Release Release Release

1.0 1.0 1.1 1.2 1.3 1.4 2.0 2.1 2.2 2.3

31/03/2005 15/04/2005 14/06/2005 30/09/2005 08/10/2005 24/10/2005 15/09/2006 05/10/2006 06/10/2006 02/07/2007

MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

Reason for Changes First Draft Emission First version (MUSA Release 3.0) Revision MUSA Release 4.0 – Draft MUSA Release 4.0 – First Version Revision MUSA Release 4.5 – Draft MUSA Release 4.5 – First Version MUSA Release 4.5 – Revision MUSA Release 4.6 – Revision

2 2/480

5/24/2018


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


3 3/480

5/24/2018


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 PROCEDURE............................................... 6.1 StartingPIXELLING General Pixelling Procedure Processing......................... 123 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


4 4/480

5/24/2018


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 with Indicator Indicator Grid................................................ Distribution .................................... 338 12.4.9 Analysis 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


5 5/480

5/24/2018


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 14.1 Main toolbar................................................................................... Buttons Overview ................................................... 378 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 ................................................................... 15.6.4 Delete ExecuteAnalysis Analysis ................................................................ 427 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


6 6/480

5/24/2018


15.8.5 Options................................................................................ 448 15.9 Menu Tools .................................................................................. 449 15.9.1 Options................................................................................ 449 15.9.2 DB Shrink............................................................................ 451 15.9.3 ScannerSINGLE Tracing BUTTONS............................................... ................................................................. 451 16. MAIN TOOLBAR 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


7 7/480

5/24/2018


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.


8 8/480

5/24/2018


2. MINIMUM REQUIREMENTS System Requirements Prerequisite software

RAM

Hard Disk space Processor

Operating System

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. 128 MB (recommended 1 GB or more, especially for algorithms simulation or to load large mobile data) 800 MB (required for a full installation) Pentium III Compatible or higher Minimum: 500 MHz Recommended: 1 GHz or higher 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 RAM Hard Disk space Processor

Operating System

Microsoft Internet Explorer 6.0 SP1 or later (prerequisite for .NET Framework) 512 MB (1 GB recommended) 2 GB free space Pentium III Compatible or higher Minimum: 500 MHz Recommended: 1 GHz or higher 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

Projection

File format


More than 360 Datum supported (e.g. WGS84, ED50, NAD27, etc.). See list in DatumID.xls contai ned in help subfolder Latitude/Longitude, U.T.M., Transverse Mercator, Gauss-Boaga, Pulkova 1942, Gauss-Kruger, Lambert Conformal Conic, French Coordinate System MS Windows Bitmap 256 colours

9 9/480

5/24/2018


Height Data Geographic Datum

Projection

File format


More than 360 Datum supported (e.g. WGS84, ED50, NAD27, etc.) See list in DatumID.xls contained in help subfolder Latitude/Longitude, U.T.M., Transverse Mercator, Gauss-Boaga, Pulkova 1942, Gauss-Kruger, Lambert Conformal Conic, French Coordinate System Binary (see Height Data Appendix for detailed description)

10 10/480

5/24/2018


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

3.1 MUSA Setup Pro gram 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).


11 11/480

5/24/2018


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


12 12/480

5/24/2018


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

3.3 Main Ap plication 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 MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

13 13/480

5/24/2018


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:


14 14/480

5/24/2018


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 Cou nters Modu le 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).


15 15/480

5/24/2018


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 L atest 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.


16 16/480

5/24/2018


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

Fig . 3.12

3.6 L icen se Upd ate 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:


17 17/480

5/24/2018


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.


18 18/480

5/24/2018


Fig . 3.14

3.8 Lic ense 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


19 19/480

5/24/2018


• 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.


20 20/480

5/24/2018


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

4.1 Main Toolbar B utton s 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.

Clos e 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 Netwo rk Manager , to open the Network Manager window Cell Matchin g , 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)


21 21/480

5/24/2018


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

Fig. 4.1

Fig. 4.2

Fig. 4.3


22 22/480

5/24/2018


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


23 23/480

5/24/2018


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.


24 24/480

5/24/2018


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.


25 25/480

5/24/2018


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 file searching

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


26 26/480

5/24/2018


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

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

Fig.Import 4.14 data as shown shown in in the . Wizard Selecting theit plus symbolto explore displayed beside each element panel is possible the tree structure


27 27/480

5/24/2018


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 Fig. 4.15 .

of

Fig. 4.15

The log window of Fig . 4.16 appears.


28 28/480

5/24/2018


Fig. 4.16

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

button. The Wizard

Fig. 4.17

Press the of Fig. 4.18 shows.

button to load an optional Neighbours Excel file as the Wizard


29 29/480

5/24/2018


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. . Here you can set the Imported Network Name. 4.20


30 30/480

5/24/2018


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.


31 31/480

5/24/2018


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 choose the desired file, as shown in the dialog of Fig . 4.24.


button and

32 32/480

5/24/2018


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.


33 33/480

5/24/2018


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 theUMTS/GSM New Projectneighbours Import procedure). In the last boxnot areimported reportedinthe 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.


34 34/480

5/24/2018


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


35 35/480

5/24/2018


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: ___3G RNCPARAM.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 doesn’t 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 .


36 36/480

5/24/2018


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 .


37 37/480

5/24/2018


Select a UMR version. If measurements and Network data contained in the just described excel files are related to a not-Siemens network doesn’t 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


38 38/480

5/24/2018


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


39 39/480

5/24/2018


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:


40 40/480

5/24/2018


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.


41 41/480

5/24/2018


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 .


42 42/480

5/24/2018


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.


43 43/480

5/24/2018


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


44 44/480

5/24/2018


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.


45 45/480

5/24/2018


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).


46 46/480

5/24/2018


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 In will in are the five directory \Projects\ of MUSA. this be new created folder there 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


47 47/480

5/24/2018


• \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 by pixelling support process and Coverage Analysis Pilot Pollution • generated \Results\PMReports: folder for reports generated by PMoptions 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 Selectio n This to window the procedures necessary to open a predefined Project. Whensection MUSAisisdedicated started, the Select Project in Fig. 4 .46 appears.


48 48/480

5/24/2018


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 access MUSA functions.

button to

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…


49 49/480

5/24/2018


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 regenerated: • .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 didn’t 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


50 50/480

5/24/2018


In this case, select the missing Project and click on the completely and correctly delete it.

button to

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


51 51/480

5/24/2018


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

4.4 Netwo rk 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 in this all it loaded RNCs,toBSCs, cells, are Viewer: listed. Selecting onebox RNC is possible explore all and sitesneighbours and cells that


52 52/480

5/24/2018


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 are only the O&M parameters of UMTS system related to 2G managing 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 ).


53 53/480

5/24/2018


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 Wizard.

button permits to restore the original configuration, as imported by the

4.5 Cell Match ing Selecting from the main menu N e tw o r k \Cell Matchin g

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 Fi g . 4.57 and Fig. 4.58 are shown respectively an example of SC search and Alias Search.


54 54/480

5/24/2018


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.


55 55/480

5/24/2018


4.6 Cell Inv ersion d etection 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 Window as Itdescribed in sectionto4.4 . Herethat it isthe possible to exchange cell Manger Scrambling Codes. is very important remind situation


56 56/480

5/24/2018


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. the first cellselect involved 2. Select In the Iub group 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


57 57/480

5/24/2018


Fig . 4.61


58 58/480

5/24/2018


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 Too lbar Bu ttons 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 Measurem ents : to open Scanner and/or Mobile files Clos e File, to close all previous loaded measurement files and release memory , to open Data Export window Export Tabbed Text

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 Simu lation, to access the Optimization tools Load as Pixels , to perform a pixel based processing of collected data , to open Time Charts visualization tool window Time Chart

Route Map , to open Route Map visualization tool window Distrib ution and CDF, to access Distribution and CDF window Joint Distribution, to access the Joint Distribution window Neighb ou rs Analyzer , to open neighbours optimization tool Islands , to perform Island analysis MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

59 59/480

5/24/2018


Pilot Pollution , to perform Pilot Pollution analysis Cell Identi ty Card , to create Cell Identity Cards Coverage An alysis Quality Indic ators , to calculate Level and Interference, Best Server Area Fragmentation and Pilot Pollution quality indicators , to calculate how many times a sequence is repeated Calc Between messages correctly inside the measurement. , to synchronize all the opened windows Window Sync hronization

5.2 How to lo ad 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 doesn’t 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


60 60/480

5/24/2018


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 Lo ad Single File Select Measurement\Open…

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


61 61/480

5/24/2018


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 .


62 62/480

5/24/2018


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 m i port 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:

Project name Network file loaded

Number of records loaded

Scanner File Name

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.


63 63/480

5/24/2018


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.


64 64/480

5/24/2018


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


65 65/480

5/24/2018


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 th RSSI, SC_n, RSCP_n, EcIo_n, etc., where n indicates the n best server. Measurement Data window buttons description: • •

Minimize on bottom , to minimize the window. , to calculate functions for a specific data column. Pressing Ap p ly fu n ctio n 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).

•

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


66 66/480

5/24/2018


•

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 sc anner 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 Scann er 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.


67 67/480

5/24/2018


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-Tim e 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:files selecting one of format. the supported file types, MUSA will show the • Available for the chosen


68 68/480

5/24/2018


Pressing the (Select A ll 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 available files one by one.

(Select File ) button it is possible to select the

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 Mo ve D o w n ) 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.


69 69/480

5/24/2018


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 TimeDate 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 :


70 70/480

5/24/2018


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 Processin g 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 Optio n\Pixel Settings


71 71/480

5/24/2018


to enter the parameters that MUSA needs in order to perform the pixel based processing. The Pixel Options window (Fig.5.11 ) appears:

-140

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.


72 72/480

5/24/2018


•

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


73 73/480

5/24/2018


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 intrafrequency handover (default: from -4 to 4, from 4 to 9, from 9 to 20).

Fig.5.14


74 74/480

5/24/2018


In the Adjacent ) it is possible to set the parameters related to menu (Fig.5.14 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 used. Ec/Io can be 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). of Order by: sorting criterion. Output data can be sorted by Numb er of pixels overlap (default) or by cell N a m e.


75 75/480

5/24/2018


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 Y , an Open SGF File window es in the Information window of Fig.5.16 (Fig.5.17 ) is opened to load existing queued files (*.sgf ).


76 76/480

5/24/2018


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 Optio n\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


77 77/480

5/24/2018


Select the folder containing the files to merge, then press OK. The Pixel Queue . Repeat the procedure shown in Scanners Files window will appear, as in Fig.5.19 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


78 78/480

5/24/2018


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

_Scanner@.spx _scanner@.sgf • ...\Projects\\Environment\Network

_netverify_[UTM].txt

There will be several files describing Islands situation, one for each criterion set in Option s\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 Optio ns\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. : the Pixel (selecting elaboration could be performed on),any Scanner file Note already opened Scanner\Load as Pixel… but only if thatmeasurement file is not a pixel based data (*.spx).

5.6 Area Cuttin g 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 inside polygon the area under investigation and importing only the measurements thedelimiting polygon itself.


79 79/480

5/24/2018


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 M ap

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 Polygo n , to save a polygon Clear All Polygon s , to delete all the polygons drawn on the Route map New Polygo n , to draw a new polygon Remo ve 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 : the tool is ready to select basic points of the polygon Select s tatus


80 80/480

5/24/2018


Edit status : the tool is ready to edit the positions of the basic points Delete statu s : the tool is ready to remove a basic point : indication of polygon area [Km 2] Area

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.


81 81/480

5/24/2018


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 always possible theto position of points. the basic points, and therefore the “form” ofispolygon, to removetoachange point and add new


82 82/480

5/24/2018


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 Polygo n button to save the polygon just drawn. MUSA creates a file in the subfolder polygon.plg \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 :


83 83/480

5/24/2018


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 Polygon al Cutting button is pressed, only the data falling in the polygon will be loaded. To prove it, on main menu select View \Route Map to display the Route window, then select a parameter to be plotted on the map area, e.g. RSCP_1s (see chapter 6 for details). Only the cut measurements will be displayed, as in Fig.5.26 .


84 84/480

5/24/2018


Fig.5.26 Note : if the user has drawn many polygons, they are in any case considered as a single polygon made by the union of the single elements. Measurements are cut in each sub polygon.

5.7 Other Scann er Data func tion s This section is an overview of the some functions that could be used when Scanner files are loaded.

5.7.1 Export Tabbed Text MUSA gives the possibility to export the information displayed in the Measurement Data table in a text file selecting from the main menu Measurem ent\Exported Tabbed Text


85 85/480

5/24/2018


The Export Tabbed Text File window will be displayed as shown in Fig . 5.27. In this window user could choose the Items that have to be exported from Scanner side selecting them in the relative check boxes.

Fig.5.27 If the user needs to export the same information for more files, it is possible to open and edit an export configuration file .ed in the folder: \Projects\\Resources\ExportDefs. (see Chapter 11 for further details). From the window in Fig.5.27 press the button to load an existing configuration file. After the loading phase is completed all the configured items will be selected in the relative check boxes. Press to start the export of the selected items in a text file: the window in Fig.5.28 will be displayed to edit the desired filename and to choose the destination folder:


86 86/480

5/24/2018


Fig . 5.28

5.7.2 Main Menu S C A N N E R Options In this section will follow a short description of the options available in the menu Scanner before a Scanner file import. There is the possibility to insert a time shift in the collected data by selecting from the main menu Scanner\Time Offset…

Insert the wished time offset in the Scanner Time Offset window (Fig. 5.29 ), then press OK.


87 87/480

5/24/2018


The option Time Averaging is enabled by default. It is accessible selecting Scanner\Time A veraging (1sec)

When this option is enabled, a time average on a 1 sec long interval is performed on measurements. The result is that there will be 1 sample per second (the mean value of all the samples collected in that second). By default MUSA reports the data related to all the measured serving cells. Anyway, the tool gives the possibility to limit the number of serving cells to report by selecting Scanner\Maximum Number of Servers…

This option is useful to limit the memory usage in presence of large amount of data to be load. Insert the wished number of serving cells in the Maximum Number of Servers window (Fig . 5.30 ), then press OK.


88 88/480

5/24/2018


Fig . 5.30 Selecting Scanner\SGF filtering it is possible to process an .sgf file to remove up to three consecutive samples with no data measured (holes), replacing them with an average value computed with the valid value available immediately before and after the missing measurements.

After the measurements have been loaded MUSA gives also the possibility to export the information displayed in Measurement Data table in a SGF (standard scanner MUSA file format) or SEM file (the file format of NSN StangaE acquisition tool), selecting Scanner\Export SGF File… or Scanner\Expo rt SEM File…


89 89/480

5/24/2018


In the same manner it is possible to export the information displayed in Measurement Data table in a DAT file, compatible with output file format of Anritsu ML8720B (Unspecified Short Format), scanner, selecting Scanner\Export ML8720B File…

5.7.3 Main Menu VIEW Options In this section will follow a short description of the options available in the View menu after a Scanner file import.

Selecting View \Tim e Chart or View \Route Map the related data graphic visualization windows will be shown. For further details see section 7.2 and section 7.3. The other options are related to the mobile data analysis and will be described in chapter 13.

5.7.4 Main Menu T O O L S Options In this section will follow a short description of the options available after a Scanner file import accessing the Tools menu.


90 90/480

5/24/2018


Selecting Tools\Statistics

two statistic functions (see chapter 7) are available. These functions can be enabled directly pressing Distribution and CDF button and Joint Distribution button on main toolbar. Once one of the Statistic function is activated, in the Series field it is possible to select one of the Scanner Data columns item. MUSA will calculate the statistic on the selected series. Statistics function s i also available for mobile part (if it has been loaded).

Selecting Tools\Neighbo urs Analyzer

it is possible to access the neighbours optimization tool. For details see chapter 10.


91 91/480

5/24/2018


Selecting Tools\Coverage Analys is

it is possible to access the coverage analysis tools (Islands, Pilot Pollution and Cell Identity Cards) and related settings. For further details see section 5.8.

Selecting Tools\Calc Duration

it is activated a function that gives the possibility to count the time between two messages in the Measurement Data table. When this option is enabled the Duration Between Messages window in Fig. 5.31 is displayed. In the New Column Name field it is possible to edit the default name of the column in Measurement Data table and the filename where the results will be saved. This file will be created in the folder \Projects\\Results\Statistics .


92 92/480

5/24/2018


Fig. 5.31

In the file it will be reported the start and end time of the sequence and the time difference between the two selected messages. Use the drop down menu Start Msg in the Column box to define the column title (Marker , Remark or Warning and many other for the mobile part ) in which a specific message has to be searched and then select the starting sequence message between the ones available in the list of the relative Message menu. Similarly, use the drop down menu Stop Msg in the Column box to define the column title in which a specific message has to be searched and then select the ending sequence message between the ones available in the list of the relative Message menu. To start the sequence counting press Calc. MUSA shows some information: • the number of correct sequences • the number of incorrect sequences • details about the time in which the failed sequences start.

Only the correct sequences are saved in the file. A sequence is considered incorrect if after the message selected in the Start Msg menu it is not encountered the message selected in the Stop Msg menu. In section 13.4.3 is shown a complete example applied to Mobile data.

Selecting Tools\Coverage Simu lation


93 93/480

5/24/2018


the related Coverage Optimization Parameters window will be shown. This window contains the parameters table for RF optimization. For more details see chapter 9.

Selecting Tools\Alg orithm s Simulation

the SIM window will be shown. This window permits to define scenes and give access to the 3GPP algorithms simulations function. For more details see chapter 12.


94 94/480

5/24/2018


Selecting Tools\2G Conv ersion

it is possible to access to a small GSM file conversion utility:

Using this window the user can select one or more .scn GSM file and convert them into equivalent UMTS .sgf file. This operation provides an estimation of UMTS coverage in terms of computed RSCP values, starting from GSM RxLevel measurements. It uses frequency corrections and transmitter offsets. This function can also compute the Ec/Io and RSSI.


95 95/480

5/24/2018


Warning This approximation is valid only if each GSM cell is replaced with the UMTS one. Resulting files could not be enough accurate (especially for the RSSI and Ec/Io values). Selecting Tools\Warning Generation

it is possible to execute the warning generation as defined in the warning.txt file stored in the folder: \Projects\\Environment\Script It allows the user to define a sequence of messages/data to generate a specific warning every time that the sequence will be found in the messages/data of the Measurement Data table Scanner and/or Mobile section (see also section 13.3 and section 13.4.3) or every time that a deviation in the defined sequence will be encountered, as configured in the file itself. Please refer to section 8.6.2 or to Appendix for details on warning.txt editing. Every sequence defined in the warning.txt file has a name. In the column Warning of the Measurement Data table are reported those names as result of the research on the defined sequence with the modality configured in the Warning file. The warning match and count operations are performed every time that a new measurement file is imported.

Selecting Tools\PM Counters An alyzer


96 96/480

5/24/2018


the PM Counters Analyzer window will be shown. This window permits to process Statistical counters. For more details see chapter 15.

Selecting Tools\Export to Google Earth

it is possible to create a KMZ file for Google Earth™ containing network sites, measurement, etc. The first time you choose this option a configuration window will be shown, as in the following picture:


97 97/480

5/24/2018


By means of this window the user can decide to save a file or to start it automatically in Google Earth client. There are several option concerning antennas style, measurement aspect, and camera point of view.

5.7.5 Main Menu OP T IONS In this section will follow a short description of the options available after a Scanner file import accessing the menu Options . Selecting Options \Show Time and Date


98 98/480

5/24/2018


it is possible to enable the data information in the Measurement Data window , as in the figure below:

Selecting Options \Scram blin g Code as Cell ID

it is possible to enable or disable the visualization of Cell ID Alias in the Measurement Data table.

Warning: many MUSA tasks required that Scrambling Codes are represented as Cell ID in the Measurement Data table. Selecting Optio ns\Undefined Cell Distance

it is possible to edit the distance (default = 400 m) in the Undefined Cell Distance ). Threshold window opened (Fig.5.32

Fig.5.32


99 99/480

5/24/2018


This option allows to establish the association Scrambling Code ⇔ Cell ID when more than one cell have the same SC. Suppose that cell A and cell B have the same SC . When this SC is detected in a measured sample, MUSA has to decide its association to A or B. Let d A and d B be, respectively, the distance between the sample and cell A and cell B. MUSA calculates d x = (d A – d B). If dx = 0, no association it is possible and in the Cells menu of the Route Properties window there will be the symbol “?” followed by a SC number to indicate missing association. If d x > TH (d A > d B), where TH is the threshold set in Fig.5.32 , then the association will be B ⇔ SC; If d x < TH (d A < d B), then the association will be A ⇔ SC. Remember that, if in the UMTS Network Site database file (see Appendix) there is no cell associated to the SC measured, in the Cells menu of the Route Properties window there will be a Symbol “# followed by a SC number. Selecting Optio ns\Au to create Cell Legend

it is possible to use a user defined legend for all the SC_# series. If this option is enabled MUSA automatically assign a color to the plotted SC, otherwise MUSA will use the std_SC.leg legend file.

5.7.6 Windows Synchronization MUSA gives the possibility to open more windows at the same time and to synchronize them with the Window Synchronization function selecting in the main menu Window \Window Sync hronization


100 100/480

5/24/2018


When the Window Synchronization function is enabled, all events and messages in Measurement Data table and in the other windows are synchronized. After a double click on one cell of the Time column in the Measurement Data table a star pointer is

Fig.5.33 displayed inTime the Route likeininFig.5.34 orvice viceversa. versa, and/or a vertical line is shown In Chart Map graphwindow area like , or

Fig . 5.33

Fig . 5.34


101 101/480

5/24/2018


5.8 Coverage An alysis MUSA by means of Coverage Analysis tools allows a deep investigation of Best Server behaviour. This study can be performed only on Scanner measurements after the pixelling procedure (see 5.5) Two methods are available: • Irregular Coverage Recognition (“Islands” investigation) • Pilot Pollution

In the next sections will follow a detailed description.

5.8.1 Irregular Coverage Recognition The Best Server cell irregular coverage analysis target is to identify how the best server cell coverage is homogeneous and not split in several standalone “Island”. So the “Island” is a fragment of Best Server coverage area isolated from others, detected in the scanner recorded measurements. The Islands analysis can be conducted only on a scanner measurement file treated with the Load as Pixel procedure. In general an Island is composed of pixels that have a minimum Distance between each other of D and an Area of at least A To start Islands calculation Analysis\Islands\Calc…

select

in

the

main

menu

Tools\Coverage

MUSA automatically calculates Islands that responds to the following criteria: • D=1 A=1 • D=1 A=2


102 102/480

5/24/2018


• D=2 A=2

Other possible configurations can be set adding a Filter in the Pixel Settings window (see 5.5). A histogram charts is produced for each configuration as displayed in Fig. 5.35.

Fig . 5.35 Moreover in the Created Report List window shown in Fig. 5.35 are listed all the text report files that MUSA generates in the folder: \Projects\\Results\Islands. In case of standard configuration, the available standard reports are: • Basic report file:

Report_Islands 15-1-1.txt Report_Islands 15-1-2.txt Report_Islands 15-2-2.txt Basic information on the available series • Difference files:

Islands 15-2-2 – Islands 15-1-2.txt Islands 15-2-2 – Islands 15-1-1.txt Islands 15-1-2 – Islands 15-1-2.txt MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

103 103/480

5/24/2018


Useful reports to analyze Islands number changing • Comparison files:

Comparison – Islands 15-1-1 – Islands – 15-1-2 Islands 15-2-2.txt Global Comparison – Islands 15-1-1 – Islands – 15-1-2 Islands 15-2-2.txt Critical Cells – Islands 15-1-1 – Islands – 15-1-2 Islands 15-2-2.txt Useful reports for global Islands behaviour analysis. In Fig. 5.36 a histogram chart is reported as example. The series plotted in this charts are the default series that MUSA offers when the Islands Function is activated.

Fig . 5.36 Every different chart window reports Islands with different filtering criteria. In any window in the Series drop down menu it is possible to choose between the following series: : number of Islands per cell • Islands • Islands over mean distance: number of Islands per serving cell that are over the mean value of distance (distance of the Islands from the relative serving cell) • Islands over mean distance excluded bigg est : it is similar to the series above but in this case it is excluded from the count the biggest Island • Islands over mean distance weighted on Surface : number of Islands per serving cell that are over the “weighted distance”, defined as:

D≡

∑ D * A i

i

∑

Ai

i

[m]

i


104 104/480

5/24/2018


Where: Di is the distance of the “Island i” from the serving cell Ai is the surface, in terms of number of pixels of the “Islandi” : it is • Islands o ver mean distance weighted on Surface exclu ded biggest similar to the series above but in this case it is excluded from the count the biggest Island • Islands over mean distance [weighted on Surface] and Surface : number of Islands per serving cell that are over the “weighted distance” AND that are over the mean value of surface (Surface of the Islands of the considered serving cell) • Islands over mean distance [weighted on Surface] and Surface excluded biggest : it is similar to the series above but in this case it is excluded from the count the biggest Island Once the desired series is selected press the button

Ac tivate Series to plot it on the chart area.

To manage the charts area the following options are available: • On the top of chart window:

Series Color, to change the color used to plot the series Sort Series, to enable the sort options for the current series (only one series can be sorted) Sort Series by Cell Name , to sort the selected series in alphabetical order considering the alphabetical part of the cell names , to sort the selected series in numerical order Sort Series by Cell Value considering the values of the series chosen with the Sort Series button

Sorting Series in Ascending Ord er , to apply the selected sort method in ascending order Sorting Series in Descend ing Order , to apply the selected sort method in descending order Show Series Mean , to show on charts area the mean value of the selected series • In the bottom of the window:


105 105/480

5/24/2018


Save Page as B itmap , to save current chart page in a file as a bitmap image. Once it is selected the browser window in Fig . 5.37 will be opened to allow filename and subfolder choice

Fig. 5.37 Save All Pages as B itmap , to save all charts pages automatically as bitmap images, one file for each page. The filenames will be set equal to the chart windows name with a progressive number for each chart page. The subfolder in which the files are stored is by default \Results\Islands , to edit the chart title. Insert the new title in the dialog Change Chart Title box displayed in Fig . 5.38

Fig . 5.38 in this box it is possible to set the maximum number of cells displayed in one chart page this group of buttons allow to select the chart page to display

Difference Bar , depending on the selected series this button is active or not. It changes the visualization of the series on the chart grouping in one bar for every cell the different series available (stacked series). In Fig. 5.39 is shown an example of the effect of this option on two series.


106 106/480

5/24/2018


Fig. 5.39 , to enable or disable legend visualization on chart area Show Legend To exit the Islands function press again the button in the main toolbar. All opened charts windows will be closed. Once the Islands function will be re-activated, MUSA recalculates everything and all the report files will be updated.

5.8.2 Pilot Pollution Analysis The Pilot Pollution condition it is verified when, in a pixel, more than three different scrambling codes are detected by the UMTS scanner. Basically Pilot Pollution analysis it is an interference state analysis. The Pilot Pollution analysis can be conducted only on a scanner measurement file treated with the Load as Pixel procedure, and it is based on the definition of the following three ranges: 1. Very strong pilot pollution state : (Best server P-CPICH level – INT. server P-CPICH level) < 4 dB 2. Strong pilot pollution state : 4 dB = (Best server P-CPICH level – INT. server P-CPICH level) < 9 dB 3. Low pilot pollution state : 9 dB< (Best server P-CPICH level – INT. server P-CPICH level) < 20 dB where th

INT. server = Interfering server, cell measured as 4 server or higher.


107 107/480

5/24/2018


The thresholds of 4 and 9 dB could be changed through Pixel Settings window (see 5.5) Moreover the Pilot Pollution analysis is performed taking into account two aspects: • From interfering cells point of view (polluter side) • From interfered cells point of view (polluted side)

To start Pilot Pollution calculation, select in the main menu Tools\Coverage Analysis\Pilot Pollution\Calc…

Different histogram charts are produced as displayed in Fig. 5.40

Fig. 5.40 MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

108 108/480

5/24/2018


Moreover in the Created Report List window shown in Fig. 5.40 are listed all the text report files that MUSA generates in the folder: \Projects\\Results\PilotPollution. The available report files are all related to Polluter side analysis: • Number of cell polluted per polluter per pollution class:

Polluter Side_PCN1.txt Polluter Side_PCN2.txt Polluter Side_PCN3.txt • Pollution percentage and information on the first 5 polluted cell per polluter per

pollution class

Polluter Side_PPN1.txt Polluter Side_PPN2.txt Polluter Side_PPN3.txt The available charts are: • POLLUTED CELLS DISTRIBUTION PER POLLUTER CELL

It reports the number of polluted cell for each polluter per pollution class • POLLUTED PIXELS DISTRIBUTION PER POLLUTER CELL •

• •

•

It reports the percentage of pollution per class for every polluter cell POLLUTED AND MEASURED PIXEL PER POLLUTER CELL It reports the number of measured pixels and the number of polluted pixels for every polluter cell POLLUTED CELLS PER POLLUTER CELL It reports the number of polluted cell for every polluter cell POLLUTED PIXEL PER POLLUTED CELL It reports the number of measured best server pixels and the number of polluted pixels for every Best Server (polluted) cell POLLUTED PIXEL DISTRIBUTION PER POLLUTED CELL It reports the percentage of pollution for every Best Server (polluted) cell per class

The charts area managing is similar to one described in the Island paragraph, therefore please refer to section 5.8.2. Note that in this case the folder for the automatic charts saving is Results\PilotPollution. To exit the Pollution function press again the button in the main toolbar. All opened charts windows will be closed. Once the Pilot pollution function will be re-activated, MUSA recalculates everything and all the report files will be updated.


109 109/480

5/24/2018


5.8.3 Cell Identity Card MUSA offers an automatic procedure to generate for every single cell of a selected list an Excel file with a set of information about the coverage behaviour. To start this procedure select in the main menu Tools\Coverage Analysis\Cell Identity Card…

The Coverage Analysis Options window of Fig. 5 .47 will be automatically displayed to configure the necessary information if something is missing. Please refer to section 5.8.4 for further details. If everything is configured in the right way a status bar like the one presented in Fig 5 .41 is shown.

Fig . 5.41 Depending on how many cells are to be processed the operation could take several minutes. It is possible to stop the automatic Cell Identity Card generation in any instant pressing the button

in the main toolbar.

The files created will be stored in the subfolder: Projects\\Results\CellIdentityCard .


110 110/480

5/24/2018


Observe in Fig. 5.42 ,Fig. 5.43 and Fig . 5.44 . an example of the different sections of a Cell Identity Card file.


111 111/480

5/24/2018


Fig . 5.43


112 112/480

5/24/2018


Fig . 5.44


113 113/480

5/24/2018


The section shown in Fig . 5.44 is optional. If the bitmap images are not available the warning message shown in Fig. 5.45. will be displayed.

Fig . 5.45 Selecting Yes the files generation could be continued. Also the Logo image file is optional so if it is not available the warning of Fig . 5.46 it will be shown.

Fig . 5.46 Selecting Yes the files generation could be continued.

5.8.4 Coverage Analysis Settings Selecting in the main menu Tools\Coverage Analysis\Coverage Analysis settings

it will be shown the Coverage Analysis Option window in Fig. 5.47


114 114/480

5/24/2018


Fig . 5.47 In the Islands/Pilot pollution menu are displayed by default the subfolders in which MUSA stores the results of the last performed pixelling procedure: 1. \Projects\\Results\Islands 2. \Projects\\Results\PilotPollution This indication is mandatory to activate Islands and Pilot Pollution analysis. It is possible to change those subfolders for example to access previously created files. In the Cell Identity Card menu reported in Fig. 5.48 it is requested to specify the files necessary to perform the Cell Identity Card function (see 5.8.3).

Fig . 5.48


115 115/480

5/24/2018


Fields description: • Island: after that the Load as Pixel function has been previously performed,

here ti is indicated the island file used to generated Cell Identity Card. By default MUSA uses Island_5_2_2.txt in the folder \Projects\\Results\Islands It is possible to change this file for example to access a previously created file, using

.

• Polluted Side: when the Load as Pixel function has been previously performed

here it is reported the file PP_Polluted.txt generated by MUSA in the default subfolder \Projects\\Results\PilotPollution It is possible to change this file for example to access another previously created files, using

.

• Polluter Side: when the Load as Pixel function has been previously performed

here it is reported the file PP_Polluter.txt generated by MUSA in the default subfolder \Projects\\Results\PilotPollution It is possible to change this file for example to access another previously created file, using

.

• Bitmap Folder: by default MUSA sets here the subfolder

\Projects\\Results\CellBitmaps In this subfolder are stored the files produced with the Autom atic Bitmap button in the Route Generation procedure accessible through the Properties window (see section 7.3.10). To use different cell image files for the Cell Identity Card generation select in this field the subfolder in which they are stored, clicking

.

• Logo Folder: here it is displayed the default folder for the Nokia Siemens

Networks and Customer Logo image files used for the generation of the Cell Identity Cards \Projects\\Results\CellBitmaps To use a different Logo image files for the Cell Identity Card generation select in this field the subfolder in which they are stored, clicking . Please refer to Appendix for details about the Logo image format.


116 116/480

5/24/2018


• Pilot Pollution box: MUSA Pilot Pollution analysis is based on the definition of

three ranges to differentiate the weight of Pollution. In Class 1, Class 2 and Class 3 it is possible to define the ranges used in the Cell Identity Card procedure to produce Pilot Pollution charts and reports.

Remark: in all the From fields the selected value is considered not included. • Distribution box: the three values fixed here correspond to the origin of the

three RSCP and Ec/Io distribution graphs reported in the Cell Identity Card and in Coverage Quality Indicators window. • Threshold: it is the threshold used by the Active Set admission algorithm

In the Cell Filters menu reported in Fig. 5.49 it is possible to define the list of cells included in the Islands, Pilot Pollution and Cell Identity Card. By default all the Scanner Detected cells are listed and selected, but using the relative check box any modifications could be done. The two buttons Select All and Unselect All as obvious have effect on the whole list.

Fig. 5.49 Once all the desired changes have been done in the Coverage Analysis Options window, select OK, and if necessary carry out again the Islands, Pilot Pollution and Cell Identity Card analysis .

5.8.5 Coverage Analysis Quality Indicators MUSA offers an automatic procedure to generate a report about some coverage quality indicators.


117 117/480

5/24/2018


To start this procedure select in the main menu Tools\Coverage Analysis\Quality Indicators...

The Coverage Analysis Options window of Fig. 5.47 will be automatically displayed to configure the necessary information if something is missing. Please refer to section 5.8.4 for further details. If everything is configured in the right way a window like the one presented in Fig 5.50 is shown.

Fig 5.50

Indicators Descriptions • Level and Interference


118 118/480

5/24/2018


The three indicators report the percentage of pixel, compared to the total, that fall in the first quadrant according to the three quadrants' origins. The quadrant origins are set in the Distribution section of the Coverage Analysis Options' Cell Identity Card menu. • Best Server Area Fragmentation

Reports for every island filter the average number of islands for cell. • Pilot Pollution

Reports the percentage of pixels suffered from the effect of Pilot Pollution for every critical class defined in the Pilot Pollution section of the Coverage Analysis Options' Cell Identity Card menu. Pressing

It is possible to save a report in the current project Export folder.

5.9 UMTS Multi -Carrier A nalysis If measurement file contains information belonging to different frequency carriers MUSA permits to choose the frequency layer during the loading phase, as shown in the following figure:

Fig 5.51 To avoid cell identification errors it is highly advisable to create a Network database for each frequency layer (using different excel worksheet files during network import procedure). In this case be sure to select the correct network database before loading scanner measurement file.

5.10 DVB-H Cov erage An alysis Digital Video Broadcasting - Handheld (DVB-H) measurement files can be loaded in MUSA. At the moment it is supported only NSN StangaE files (.se2) traced using the Anritsu MS8911A (Digital Broadcast Field Analyzer for DVB-T/H). Specific DVB-H scanner measurement quantities that can be analyzed: • DVB-H Channel power [dBm] • MER (Modulation Error Rate) [dB] • MER (TPS) • MER (data)


[dB] [dB] 119 119/480

5/24/2018


• Frequency Offset • Modulation faults

[Hz]

Examples of DVB-H analysis are reported in the following figures (for details about how to create maps, CDF, etc. see Chapter 6 and 7): • Modulation Error Rate maps with legend distribution:

Fig 5.52 • RF Power Level (Coverage) map with legend distribution:


120 120/480

5/24/2018


Fig 5.53 • RF Power Statistics: CDF, average value, standard deviation, percentile and

coverage probabilities in different scenarios (indoor, in-car, outdoor)

Fig 5.54 • MER vs RF Power Average value (blue) with standard deviation (red)


121 121/480

5/24/2018


Fig 5.55


122 122/480

5/24/2018


6. GENERAL PIXELLING PROCEDURE The aim of this chapter is to describe the general pixelling processing function; in the subchapter 5.5 it is reported the way to process only UMTS scanner data and the relative UMTS coverage analysis. The general data pixel processing allows to elaborate on pixel base all kind of data that MUSA can manage, in terms of several technologies (like UMTS, GSM, DVB-H …), both scanner and mobile data. The minimum requisite to process data on pixel base is that at least one sample has to be geo-referenced; samples without coordinates that precede the first geo-referenced one will be excluded, while samples without coordinates that follow the geo-referenced one will be considered in the same position of this one.

6.1 Starting General Pixelling Proc edure Proces sing In order to process on pixel base the loaded data in the toolbar (main MUSA window) select: General Pixelling Procedure A remember of measurement loading is reported using as scanner as mobile data (UMTS data will be used) In the main MUSA window select:

Open Measurements, The following window will be opened: Open SCANNER file


123 123/480

5/24/2018


In the window it will be possible select the queued data scanner file (.sgf), or the single route data file (.se2), then press Open button.

Open MOBILE file


124 124/480

5/24/2018


In the window it is possible to select the queued mobile file (.mgf), or single route. (.dt1 o .dt2), then press Open; the Mobile Data Selection Window will be open:

Mobile Data Selection

For a detailed explanation of this window please refer to the chapter 12. At this point MUSA will load the data.

To proceed with processing on pixel base, the loaded data select:

General Pixelling Procedure,

6.2 Measur ement Pixelling W izard After selected for General pixelling procedure “wizard” will be opened to help the user inthe thebutton procedure. This wizard is composed byaseveral pages:


125 125/480

5/24/2018


Measurement Pixelling Wizard – 1 Pixeling Options

In this window the following parameters can be set: §

Pixel Dimension: the pixel size in meters that will be used during the elaboration of data (default 10 meters) § 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 Dimension field (default = 1 m eter). 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. This feature 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: this value is the lower threshold under that the data will be not considered (default -140 dB). § Consider data as ungrouped: In the case of this check is enabled the data will not be grouped. Grouped Data : set of columns that contain data with the same meaning and that can be referred to a cell. For example in UMTS technology SC, RSCP, and Ec/Io can be considered a group, that is a set of information that can be referred to a server. §

Sorting: 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


126 126/480

5/24/2018


(default); if By level is checked, it will be elected Best Server in a pixel the cell with higher power level, independently of the number of occurrences of the cell in that pixel. then press

to go to the next step of wizard.

Measurement Pixelling Wizard – 2 Unrepeatable section

In this window the data columns that are not repeatable (that is “grouped”) are reported. The unrepeatable columns are the columns present only once in the data structure like scanner RSSI scanner, AS Size, Layer-3 messages, etc. In the Available columns section it is possible to select the data that will elaborated on pixel base using:

to select only one column, the same effect will be obtained using double click on the item. to select all columns The chosen columns will be available in the window Selected columns. then press



127 127/480

5/24/2018


Measurement Pixelling Wizard – 3 Repeatable section

To enable this step of wizard task the Enabled box has to be checked. The list of repeatable groups appears on the left grid and the data of the same group are printed using the same background color. The user has the chance to choose only one group of data to be processed by pixel, the choice can be performed by the Selected group function In the chosen group at least two columns have to be selected: one represents the ID column and the other is the relative quantity (Level). At this point it is possible to add the remaining columns in the box available columns using

.

In the example of the previous picture the SC group has been selected, than automatically the columns identifying the cell ID (SC) and the relative Signal (RSCP) data will be selected for the pixel processing At this point two more quantities can be added (EcIo e SIR ), as shown in the section available columns.


128 128/480

5/24/2018


then press


Measurement Pixelling Wizard – 4 Preprocessing functions


129 129/480

5/24/2018


During this wizard step the selected function will affect only the pre processing phase, at most only one function can be selected. In the Column section all chosen quantities for the pixel process have been reported;

Class Group Type Column

M = Mobile data, S = scanner data U = unrepeatable, R = repeatable the data in the column can be a string ( Text) or numeric (Num) quantities to be elaborated on pixel basis

At this stage the user can specify the way to elaborate the data, otherwise the default one will be applied.

Test Type

§

Most present means the string most present in the pixel will be chosen as representative of the whole pixel § Less present the opposite of the previous one § Concatenate the result will be the string concatenation obtained using all strings in the pixel

Num Type

§

Mean: means that a statistic mean will be applied to all samples present in the pixel. § Median: means that a statistic median will be applied to all samples present in the pixel. § §

result in in the the pixel pixel will will be be the the minimum maximumvalue valuepresent presentininthe thepixel pixel Max: Min: the the result


130 130/480

5/24/2018


§

Range: the result in the pixel will be the difference between the max and the min values present in the pixel § Sum: the result in the pixel will be the sum of all values present in the pixel § DBM Mean: means that a mean in the dBm domain will be applied to all §

samples in the pixel. will be the standard deviation of values present the result in the pixel Std. Dev.present in the pixel. Three different types are available: respect to the mean, median, or respect to DBM mean.

then press


Measurement Pixelling Wizard – 5 Processing functions

During this wizard step the selected function will affect the pixel processing phase and at least one function has to be selected. th The way to select functions is the same already described in the previous step (the 4 ).

Selecting the following pictures.


button the real processing phase will begin, as shown in the

131 131/480

5/24/2018


At the end of elaboration a file with extension .sgf will be saved in the project directory, at the same point where the scanner data file was stored. The output file name is created adding _GENERIC_< pixeldimension>PIXEL.SGF to the project name. Finally, the created file will be loaded automatically in MUSA.


132 132/480

5/24/2018


7. DATA VIEW MUSA offers the possibility to plot measurement data loaded, in order to perform a graphical investigation. Two kinds of visualizations are available: • Time Charts • Maps

7.1 M ain Toolbar Bu ttons 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 a Scanner and/or Mobile measurement file Time Chart, to open Time Charts visualization tool window Route Map, to open Route Map visualization tool window Window Synch ronization, to synchronize all opened windows

7.2 Tim e Charts 7.2.2 Open Time Chart tool If a Scanner and/or Mobile file is previously loaded selecting Measurement\Open

the Time Charts option is available selecting in the main menu View \Tim e Charts


133 133/480

5/24/2018


MUSA then displays the window of Fig. 7.1 .

Fig . 7.1

7.2.3 Time Charts Window Description What follows is a short description of the items available in the toolbar of the Time Charts window of Fig . 7.1.

Scanner, to open the Scanner control menu Mobile, to open the Mobile control menu Color by Scrambling Code, to plot line charts with different colors for the samples belonging to different Scrambling Code


134 134/480

5/24/2018


Active Set Comp osition, to plot the series Mobile Active Set with different colors for the different cells that compose it Re-calc Legend, to recalculate legend counters on the basis of the zoom performed in the chart area Insert Titl e, to give a title to the graph area Add Figure, to add a user-made figure on the graph Clear A ll Figures, to remove every user-made figure on the graph X-Axis Up, to move the X axis up in the graph area X-Axis Dow n, to move the X axis down in the graph area Save as Bitm ap, to save the current view as a Bitmap file Close, to close Time Charts tool Au to zo o m , to set auto zoom on or off Zoom in, to increment zoom in the graph area Zo o m o u t, to decrement zoom in the graph area Scroll Left, to move graph area left Scroll Right, to move graph area right Scroll Up, to move graph area up Scroll Down, to move graph area down Erase curr ent position , to remove time position line on the graph area Move Legend, to enable/disable embedded legend movements Legend Counters, to switch on/off legend counters

7.2.4 Series Visualization in Time Charts tool To plot a series in the graph area it is necessary to access the control part with one of the following options: • right click on the blank area of the window of Fig . 7.1 • select

Scanner or


Mobile in the toolbar 135 135/480

5/24/2018


As a result at the right side of the window of Fig . 7.1 new features are accessible as displayed in Fig. 7.2 .

Fig . 7.2 When a Scanner and/or Mobile file is loaded the respective menu series are available. It is possible to make the choice between the series already listed in the right bottom part of Fig . 7.2 . They represent the numeric columns of the Measurement Data table (see Chapter 5 and 11). More than one series is selectable either from Scanner or from Mobile list. The chosen series will be plotted together in the graph area. Fig . 7.3 shows a possible result with one Mobile and one Scanner series.

Fig . 7.3


136 136/480

5/24/2018


With the visualization functions menus it is possible to change the graphical line layout and the color for each selected series. It is necessary first to select the series to be changed in the drop down menu:

If Scanner or Mobile is selected the series list change accordingly. At this point several options are available: • to change the line color, selecting • to change the line type between the predefined set, using

• to change sample representation style between the predefined set, using

(The symbol

means no pointer)

• to set the line or pointer width, using •

Stairs Line Mode, to decide how to manage not measured interval between two samples. If this option is enabled MUSA plots the line chart joining the samples values. See Fig 7.4 . If this option is not enabled MUSA plots the lines chart keeping the sample value valid until the new sample. See Fig 7 .5 .

Fig . 7.4


137 137/480

5/24/2018


Fig 7.5 •

Draw Null Point, to avoid the drawing of the lines connecting different separated regions, as in the figure below:

Fig . 7.7 shows the results of the changes reported in Fig 7.6 for the m_RSCP_1 series of Fig 7.3.

Fig 7.6


138 138/480

5/24/2018


Fig 7.7

7.2.5 Time Charts Graph Area Functions The toolbar of the Time Charts window of Fig . 7.2 offers several options to setup the graph area in the more suitable way. MUSA by default displays all the samples of the selected series, so the time interval reported in the X axis of the graph in Fig 7.2 corresponds to the measurement file duration. If necessary it is possible to use the zoom features to explore with more details some specific area: •

Zoom in, to increment zoom in the graph area

•

Zo o m o u t, to decrement zoom in the graph area

An alternative way to zoom on a specific area is to left click on the desired starting point and then to drag the mouse to the right side to define on the chart the new zoom window. After a left click, dragging the mouse toward the left side a zoom back to the entire series is performed. Once the zoom operation is concluded it is possible to scroll the chart area in the desired directions using:

Scroll Up

Scroll Down,

Scroll Left

Scroll Right

For the right/left directions the scroll bar (see Fig . 7.7 ) could be useful as well.


139 139/480

5/24/2018


To help investigation MUSA makes possible to plot the series in the graph area with a different color for all the samples that belong to a specific Scrambling Code (i.e. cell) selecting

(Color by Scrambling Code ). See Fig 7.8 .

Fig . 7.8 In the legend they will be reported all the Scrambling Codes (i.e. cells) measured in the time interval displayed, whether the corresponding samples are plotted or not in the chart lines depending on the selected series. When the Color by Scrambling Code option is selected also the (Activ e Set ) feature is enabled. This function has effect only on the Mobile Active C o mp o sitio n Set Series (usually m_#AS Series). If this option is active the series will be plotted with a different color for every Scrambling Code (i.e. cell) that composes the Active Set in a certain instant. The upper series of Fig . 7.9 shows an example.

Fig 7.9 MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

140 140/480

5/24/2018


After a zoom is performed, selecting (Re-calc Legend ) the legend will be recalculated showing only the colors related to the samples of the time interval now displayed. Fig . 7.10 shows the result of a zoom performed on the window of Fig 7.8 with a renewed legend.

Fig. 7.10 If the following button is enabled the legend over the graph area.

(Move Legend ) it is possible to drag and drop

With (Legend Counters ) the user may decide to enable in the legend the samples counters. If this option is active a selection of the Re-Calc function will automatically update the legend counters. With the option (Insert Title ) it is possible to give to the graph a title editing it in the dialog box of Fig . 7.13.

Fig . 7.11 With the function

(Ad d Fig u r e) MUSA allows drawing on the chart area a user-

made figure. When the


button is selected the window of Fig . 7.12 is displayed: 141 141/480

5/24/2018


Fig . 7.12 User may choose between three options • Lines •

Circle

• Text

Once the type of predefined item and the desired layout are selected press . The graph area is then editable and with a left click it is possible to draw the selected item. When the Text option is chosen the dialog box of Fig 7.12 is active to edit the desired text and then it is possible to paste it on the chart with a left click. To remove all the figure drawn on the graph area select

(Clear All Fig ures )

Selecting the buttons (X-Axis Up ) or (X-Axis Dow n ) it is allowed to set the position of the X axis on the graph. The default position is on the bottom side of the Chart area. Fig 7.13 shows an example of X axis change of position.


142 142/480

5/24/2018


When is selected Window \Window Synchronization

all the opened windows in MUSA are synchronized. So if any time instant is selected in one window user will find it highlighted in any other opened window with a specific time pointer/marker. In the Time Charts the time is a black on the selected series with awindow label reporting thepointer corresponding timevertical instant.line Seeplotted Fig . 7.14. User could define a desired time instant in the Time Charts window with a left click on a plotted series but only if windows synchronization is enabled. To remove time cursor visualization select

(Erase current p osition ).

Fig . 7.14

Selecting (Save as Bitm ap ) the current view in the graph area is stored in a file as a bitmap image. To edit the desired file name the window of Fig . 7.15 is displayed.


143 143/480

5/24/2018


Fig . 7.15

7.2.6 Events It could be useful to report a particular event on the line charts to identify the time instants in which a specific condition is verified. MUSA lets the user manage event-reporting with the Events menu options displayed in Fig . 7.16 . Every occurrence of a defined event will be plotted on the graph area as a vertical line with the layout set in Fig 7.16 .

Fig . 7.16 In the dialog box


144 144/480

5/24/2018


is requested to edit a name for the desired event. This name will be reported in the label plotted in the chart. The labels are shown only if is selected the Labels Check box:

.

To select the color of the event line to be drawn choose between the predefined set in

If the available colors are not suitable user may define a color by himself. To do this select custom… on the color drop down menu, the window of Fig. 7.17 appears to bring about the modifications.

Fig 7.17 To select the thickness of the lines use Two general sets of categories/series are available depending on the selection in the following check box

• If Numeric is selected, in the menu Field

a specific list of numeric series is available. Then in the following active dialog box

it is necessary to set the range of values to be reported in the chart for the desired series. • If Numeric is not selected, in the menu Field


145 145/480

5/24/2018


user may define a specific category of items (like mobile RRC messages, Connection states, etc). Then in the menu Value

is possible to select the desired item of the chosen category. Users can also write directly the wished item, using one or more jolly “*” characters, as listed in the following table:

Valid jo lly “*” character usage Cases #0** _ALERTING

Descriptions all items containing any character in third and fourth position, such as #001_ALERTING, #002_ALERTING, etc.

* ALERTING

all items beginning with any combination of character but terminating with ALERTING

ALERTING *

all items terminating with any combination of character but beginning with ALERTING

In any case when the event has been selected and the desired line layout configured to show it on the chart press

.

Fig . 7.18 and Fig. 7.19 display respectively an example of Numeric and not Numeric events


146 146/480

5/24/2018


Fig . 7.19 The list of the defined events is shown in the Events menu window, see Fig . 7.20 .

Fig . 7.20 To switch the visualization on or off in the charts area for a particular event without loosing the configured options use the relative check box. To delete a previously created event select it in the list (it will appear highlighted in light grey) then press

.

To clear all the defined events select

.

To make some modifications to one event line layout select first the series in the drop down menus of Fig . 7.16 then modify the desired options. To show them on the chart area select Once a list of events is defined, it is possible to save it on a file selecting


. 147 147/480

5/24/2018


The browser window of Fig. 7.21 appears to choose the appropriate filename. The default extension for the event list files is .evn whereas the default folder is: \Projects\\Environment\Events.

Fig . 7.21 To load a previous saved event list file press

.

The browser window of Fig . 7.22 will be displayed to find the desired file.

Fig . 7.22

7.2.7 Statistics In the Statistics menu reported in Fig. 7.23 MUSA offers some specific statistical information for a selected series in the time interval set in the graph area (readable on the X axis and reported in the statistic box). Please refer to Chapter 7 for further details .


148 148/480

5/24/2018


Fig . 7.23


149 149/480

5/24/2018


7.3 Rou te M ap 7.3.1 Open Route Map Tool To access this option select in the main menu View \Route Map

MUSA displays the window in Fig . 7.24 .

Fig . 7.24

The Network cells stored in the UMTS network site database file (see Chapter 4 and Appendix) are reported as shown in Fig. 7.24.


150 150/480

5/24/2018


7.3.2 Route Map Window Description The following section is a short description of the items available in the toolbar of the Route Map Window of Fig . 7.24.

Series…, to open the Route Properties Window Scan Map , to show the scan maps in the map area Show Height-Map , to show on the map area the territory height information stored in the height files , to plot a vector file on the map area Vectors

Add New Vectors Layer , to add more vector layers Enable 3G Cells , to enable the visualization of the UMTS cells Enable 2G Cells , to enable the visualization of the GSM cells. Network Data , to select the appropriate Network data file Replay Route , to reproduce the sample temporal sequence of the measurement data displayed Connect to site on click , to display in the map the connection to the serving cells measured in the selected point , to display the information for a specific point in the route Information on click map.

Info window on click , to display the information window Re-calc Legend, to recalculate legend counters on the basis of the zoom performed in the map area Insert Titl e, to give a title to the map area Add Figure, to add a user-made figure on the graph Clear A ll Figures, to remove every user-made figure on the map , to enlarge the image size in order to create large bitmap for Enlarge Bitmap saving or printing purpose.

Save as B itmap, to save the current view in the graph area in a file as a Bitmap image Close, to close Time Charts tool Pa n , to scroll map with mouse (right button)


151 151/480

5/24/2018


Au to zo o m , to set auto zoom on or off Zoom in, to increment zoom in the map area Zo o m o u t, to decrement zoom in the map area Center on site , to find and center the map on the desired cell Scroll Left, to move map area left Scroll Right, to move map area right Scroll Up, to move map area up Scroll Down, to move map area down Erase curr ent position , to remove time position marker on the map area Move Legend, to enable/disable embedded legend movements Hide legend , to disable legend visualization in the map area Legend Counters, to switch on/off legend counters , to show grid on the map area Grid , to find the distance (in meters) between two points on the map Distance

Polygon Definitions , to open the polygon definition tool

7.3.3 Series Visualization in Route Map Window Firstly user should open a Scanner and/or Mobile measurement file selecting Measurement\Open


152 152/480

5/24/2018


To plot a series in the map area it is necessary to access the control window Route Properties with one of the following options: • right click on the map area of the window of Fig . 7.24 • selecting Series… in the toolbar (if Pan button is pressed this is the only acceptable method) As a result the window in Fig. 7.25 is displayed.

Fig . 7.25 In Fig. 7.25 cells have different colors. This kind of visualization is available only if the file loaded is a Scanner measurement file. In this case MUSA checks if there is at least one sample belonging to one of the plotted cells, so two conditions could be encountered: 1. no sample is found (not scanner detected condition) 2. at least one sample is found (scanner detected condition) The cells will be drawn with a specific user-configurable color (see Fig. 7.31 ) depending on which of the two conditions they satisfy. The Scanner and/or Mobile series are available depending on the type of measurement files loaded selecting Measurement\Open . The series Dist_#s and Pilot Pollution are available only if a file generated by means of the Load as Pixel function (see section 5.3) is previously loaded. To plot a series click on the series name in the available menu. The available series represent the Measurement Data table columns titles (see Chapter 5 and 11).


153 153/480

5/24/2018


In Fig . 7.26 is reported an example of Best Server CPICH RSCP (Rscp_1s) map.

Fig . 7.26

Selecting (Scan Map ) it is possible to plot a scan map (if available) in the Route Map window as shown in Fig . 7.26. MUSA needs an index file (see Appendix) to geographically locate the scan map, then the browser window of Fig . 7.27 is displayed to load the appropriate file.

Fig . 7.27 Selecting

(Vectors ) a vectorial format image file (e.g. roads, rivers, boundaries,

etc.) could be plotted on the Route Map area as shown in Fig . 7.29 . The browser window of Fig. 7.28 is displayed to choose the desired vectors file.


154 154/480

5/24/2018


Fig . 7.28 Two kind of vector file can be loaded (by changing Files of type control) located by default in the \environment\vectors folder: • Tornado Vector files (*.vec) • MapInfo Exchange vector files (*.mif )

They are substantially text files. By default it is assumed they are referred to a WGS 1984 datum system. If necessary, please add the appropriate geographical header (see Appendix to understand how to build a valid header).

Fig . 7.29


155 155/480

5/24/2018


With the option (Show Height-Map ) it is possible to display the terrain height information (if available) on the map area. MUSA needs an index file (see Appendix) to geographically locate the height files. The result is similar to the one presented in Fig . 7.30 .

Fig . 7.30 In the Options menu of the Route Properties window reported in Fig. 7.31 it is possible to setup the layout of the items shown in the Route map area.


156 156/480

5/24/2018


Options window description: • Points: to define the style and the dimension of the plotted series point • Vectors: to define color and thickness of the displayed vectors (choose the

layer in the list and then change color and width using the proper controls). • Cell:

o o o o o o o

Scanner Detected: to define the color of the scanner detected cells Not Detected : to define the color of the not scanner detected cells Triangle: to draw the cell as a triangle instead that an arrow Length: to define the length of cell triangle/arrow Background: to plot cell names with a white/transparent background Width: to define the thickness of cell triangle/arrow Font: to choose the font used to draw cell labels on the map

• Height Boundaries: to set the range of the displayed height values when the

Show Height-map function is active

7.3.4 Route Map area functions The toolbar of the Route Map window of Fig . 7.25 offers several options to setup the map area in the more suitable way. If necessary it is possible to use the zoom features to explore with more details some specific area: •

Zoom in, to increment zoom in the graph area

•

Zo o m o u t, to decrement zoom in the graph area

An alternative way to zoom on a specific area is to left click on the desired starting point and then to drag the mouse to the right side to define on the chart the new zoom window. After a left click, dragging the mouse toward the left side a step back to the previous zoom is performed. It is possible to scroll the chart area in the desired directions using:

Scroll Up

Scroll Down,

Scroll Left

Scroll Right

An alternative way is to select (Pa n ) then after a right click to drag the map area until the desired zone is displayed.


157 157/480

5/24/2018


Clicking

(Center on sit e ) MUSA displays the following dialog box

After Ok selection the map will be automatically centered on the edited site. When is selected Window \Window Synchronization

all the opened windows in MUSA are synchronized. So if any time instant is selected in one window user will find it highlighted in any other opened window with a specific time pointer/marker. In the Route Map window the time pointer is a black star plotted on the selected series with a label reporting the corresponding time instant. See Fig . 7.32. User could define a desired time instant in the Route Map window with a left click on a plotted series but only if windows synchronization is enabled .

Fig . 7.32 To remove time cursor visualization select

(Erase current p osition )

Selecting ( G rid ) the grid on the map area is plotted. Unselecting this button the grid will be removed.


158 158/480

5/24/2018


The option (Distance ) is designed to calculate the distance (in meters) between two points on the map area. When this option is active it is possible to select the starting point with a left click. Then moving the mouse cursor on the area is possible to read the value of the distance from the fixed point. See Fig . 7.33 .

Fig . 7.33 The option (Connect to site on click ) allows to show all the serving cells measured in one data route point with a red or black line that link the measurement point to the cell. The red line is used for the nth Server cell depending of the type of series selected (e.g. for the series RSCP_2s the red line is dedicated to the cell that is the second server in the selected point). See Fig . 7.34 .

Fig . 7.34 The function

(Information on click ) allows to obtain time and series value

information about one data route point with just a left click. The effect is that a flying window is displayed as shown in Fig . 7.35 .


159 159/480

5/24/2018


Fig . 7.35 If it is selected (In fo w in d o w o n click ) an information window is always shown on the top of the map. See Fig . 7.36 . The data listed are related to a narrow area around the coordinate selected with the mouse pointer. Depending on the window zoom size more than one sample/pixel information could be displayed

Fig . 7.36


160 160/480

5/24/2018


The option (Play Route ) used in combination with allow to follow the sample temporal sequence studying the serving cells distribution. A black star cursor will be displayed to simulate a replay effect.

Selecting (Insert Title ) it is possible to give to the graph a title editing it in the following dialog box:

With the function

(Ad d Fig u r e) MUSA allows drawing on the map area a user-

made figure. When the

button is selected the window of Fig . 7.37 is displayed:

Fig . 7.37

User may choose between three options • Lines • Circle • Text

Once the type of predefined item and the desired layout are selected press . The graph area is then editable and with a left click it is possible to draw the selected item. When the Text option is chosen the dialog box of Fig 7.37 is active to edit the desired then shown intext . it is possible to paste it on the map with a left click. An example is Figand . 7.38


161 161/480

5/24/2018


Fig . 7.38 To remove all the figure drawn on the map area select

(Clear All Fig ures )

The option (Enlarge B itmap ) it is designed to enlarge the map image size for example to save it with a greater detail. When this option is selected the dialog box of Fig . 7.39 is displayed to edit the desired pixel dimension (the map window has a square shape)

Fig . 7.39 For example to create an ISO A0 page format with good quality a value of 3000 pixels could be a good choice.

Warning: the maximum width value depends on many factors such as Video Adapter memory, System memory and Windows settings. Value greater then 3500 pixels may require to change color depth to 16 bits or less (go in Control Panel -> Display, Settings Tab, Color Quality control). Value greater then 5000 pixels may be not reachable.

Selecting

(Save as Bitm ap ) the current view in the graph area is stored in a file as a bitmap image. To edit the desired file name the window of Fig . 7.40 is displayed.


162 162/480

5/24/2018


Fig . 7.40

7.3.5 Legends Once displayed legend could be managed with different tools. Firstly, user may decide to show the legend on the map selecting or deselecting (Hide legend ). If is enabled the button on the map area. With

(Move Legend ) it is possible to drag and drop the legend

(Legend Counters ) the user may decide to enable in the legend the samples

counters. If this option is activated a selection of (Re-calc Legend ) will automatically update the legend counters depending on the zoom performed in the map area. The Legend menu in the Route Properties window, see Fig . 7.41, offers other legend configuration options allowing the definitions of the ranges to be reported in the series plotted in the map.

Fig. 7.41 MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

163 163/480

5/24/2018


In

it is possible to edit the legend title. In

user should define the range of the plotted series values that are to be drawn with the selected color. In Text it is allowed to assign a title to a defined range which will be reported in the legend. If the available colors are not suitable user could define a color by himself. To do this select custom… on the color drop down menu, the window of Fig. 7.42 appears to bring about the modifications.

Fig . 7.42

Once the range is defined, if it is not present in the range list, to add it select . If the range is already present to make some modifications simply select it in the list (it will be highlighted in blue and the correspondent characteristic reported, see Fig. 7.41 ). Once it will be modify select visualization and the legend. Selecting

to update the map

all the previously created ranges will be erased.

Once a list of ranges for a specific series are defined, it is possible to save it on a file selecting

.

The browser window of Fig . 7.42 appears to choose the appropriate file name. The default extension for the legend files is .leg whereas the default folder is:


164 164/480

5/24/2018


\Projects\\Environment\Legends.

Fig . 7.42

To load a previous saved legend file press

.

The browser window of Fig . 7.42 will be displayed to find the desired file.

Fig . 7.42 In the legend folder for several series are available the default legend files with the format std_.leg. To modify the default visualization of a series it is necessary to modify the relative std file.

7.3.6 Events It could be useful to report a particular event on the map to identify the time instants in which a specific condition is verified.


165 165/480

5/24/2018


MUSA lets the user manage event-reporting with the Events menu options displayed in . Every occurrence of a defined event will be plotted on the graph area with a Fig . 7.43 user-configured pointer.

Fig . 7.43

In

It is possible to choose the desired pointer style and width. If the check box Brd is selected the chosen shape will be drawn with a black border. The pointer color could be assigned in . If the available colors are not suitable user could define a color by himself. To do this select custom… on the color drop down menu, the window of Fig . 7.42 appears to let user make the modifications. If a name is edited in the events name dialog box, in the map area the pointer will be represented with a label reporting the written name but only if the Lab Check box is selected. Two general sets of categories/series are available depending on the selection in the Numeric (Num) check box

• If Num is selected, in the menu Field

a specific list of numeric series is available. Then in the following active dialog box


166 166/480

5/24/2018


it is necessary to set the range of values to be reported in the chart for the desired series. • If Num is not selected, the menu Field

allows to define a specific category of items (like RRC messages or connection state). Then in the Value menu

it is possible to select the desired item of the chosen category. Users can also write directly the wished item, using one or more jolly “*” characters, as listed in the following table:

Valid jo lly “*” character usage Cases #0** _ALERTING

Descriptions all items containing any character in third and fourth position, such as #001_ALERTING, #002_ALERTING, etc.

* ALERTING

all items beginning with any combination of character but terminating with ALERTING

ALERTING*

all items terminating with any combination of character but beginning with ALERTING

In any case after the event has been selected and the desired line layout configured to show it on the chart press

.

Fig . 7.44 and Fig. 7.45 display respectively an example of Numeric and not Numeric events.


167 167/480

5/24/2018


Fig . 7.44

Fig . 7.45 The list of the defined events is showed in the Events menu window, see Fig . 7.46 .


168 168/480

5/24/2018


In the map area, to switch for a particular event the visualization on or off without loosing the configured options, use the relative check box. For a detailed explanation of the following buttons please refer to section 7.2.6:

7.3.7 Network Data With the Network Data function it is possible to plot on the map user-made information stored in a specific Excel file. The Excel file has a format similar to the example of Fig. 7.47 .


169 169/480

5/24/2018


The Columns SITE and SECTOR are mandatory and they have to keep the format displayed in Fig. 7.47 . All following columns are user-configurable. Thethe edited column titles become the category indicator. The information in the excel file represents the data that it is possible to plot on sites. The user-modifiable data could be of two species: 1. Single 2. Step The columns ‘RNC’ , ‘Optimized’ and ‘Out Of Order’ in Fig . 7.47 are of the first type. In this case for a site cell only a single data per category (column) is available.

The columns ‘rrcEstabAtt ’, ‘rrcEstabSr ’ and ‘rrcEstabDrop’ in Fig 7.47 are of the second type. For the data column of the second case it is mandatory the column ‘STEP’ that always has to come before any other Step type column. The data in the column ‘STEP’ could be hours (as in Fig. 7.47 ), day indications (e.g. Monday, Tuesday, etc), month indications (e.g. January, February, etc.) or any other useful reference. It is possible to reproduce Step data as a temporal sequence on the map, as described in the following paragraph. To load a previously created Network Data excel file select window of Fig . 7.48 it is requested to make the file choice.

(Network Data ) in the

Fig . 7.48

Once this operation is done in the map area the sites visualization will be forced to “triangle” type. To access the Network Data map options select Network in the Route Properties Menu, see Fig . 7.49.


170 170/480

5/24/2018


Fig . 7.49

The Network Data excel file column titles are represented in the Network Item list of the . Network menu window in Fig 7.49 In the field Step type.

a marker (i.e. ‘o’) is found if the corresponding Network item is of the

To plot a specific item in the map two possibilities are available: 1. double click in the (Draw As Area) field of the desired item. In this case the triangle area of the cell representation will be drawn with colors according to the defined legend for the selected item 2. double click in the (Draw As Border ) field of the desired item. In this case the triangle border of the cell representation will be drawn with colors according to the defined legend for the selected item 3. double click in the (Draw as Label) field of the desired item. In this case a number close to the triangle representing the cell will be shown, according to the item value. If no legend is defined for an item after the double click message will be displayed:


or

the following

171 171/480

5/24/2018


When this happens it is necessary to create a specific legend as described in section 7.3.5. If the legend is stored in a file with the format std_.leg it will become the default legend for that item representation. In the figure below a Network item (defined in the excel file of Fig. 7.47) is displayed as “label”, while in Fig. 7.50 other Network items are displayed as “area” and “border”.


172 172/480

5/24/2018


Fig . 7.50 The Step Network items allow getting a dynamic representation. In the section

it is possible to set the Step object defined in the Network Excel file (Fig . 7.47 ). For the selected item will be plotted only the values corresponding to the fixed Step value with a color according to the ranges set in the legend. In Fig . 7.51 it is represented an example for the performance measurement counter ‘rrcEstabAtt’. The visualization type chosen is “Border”. The Step selection is “hr 10”, so for all the sites are displayed the ‘rrcEstabAtt’ data of the Network excel file that correspond to that STEP value according to the range and color of the reported legend.


173 173/480

5/24/2018


Fig . 7.51

With the option it is possible to see Step data changes in sequence. The slider allows to set the replay velocity.

7.3.7.1 Statistics Plot The Network Data function can also be used to display MUSA Statistics (see Chapter 7). A copy of Mobile Numeric Statistic and of all defined Tables are stored in \Projects\\Measurements\Netdata. in a MS Excel readable format report_.xls ).


(respectively

as

report_numeric.xls and

174 174/480

5/24/2018


7.3.8 Polygon Definition Selecting (Polygon Definitions ) it is possible to access the Polygon definition toolbar of Fig . 7.52.

Fig . 7.52 For a detailed description of this option please refer to Chapter 5 .

7.3.9 Single Cell Visualization MUSA lets to isolate and plot on the map area the Scanner Measurement file samples belonging to a specific detected cell. The single cell visualization options are available in the Cells Menu in the Route properties window, see Fig 7.53

Fig . 7.53 In the window of Fig 7.53 are listed all the cell alias of the cells detected during the measurement campaign and contained in the measurement file currently loaded. If MUSA is unable to associate the Scrambling Code to a specific cell alias for a lack of information in the UMTS Network Site database Excel File (see Chapter 4 and


175 175/480

5/24/2018


Appendix) in the list it will be reported the symbol # followed simply by the Scrambling Code number. The association Cell Alias <=> Scrambling Code in case of Scrambling Code reuse is based on a difference distance criteria. In the assignment procedure there is a modifiable indecision threshold, i.e. a distance so when allocation of a sample doesn’t make decision value, if a value minorMUSA of thatevaluates thresholdthe is encountered. In this case in the cell list will be reported the symbol ? followed by the Scrambling Code number. The threshold could be defined selecting Options\Undefined Cell Distance Threshold…

and editing the desired value in

Once the cell is selected in the list of Fig 7.53 three series are available for the drawing: 1. to see for every sample which order of server the cell represents in that point select

Server Order Information 2. to see the RSCP values related to the selected cell click

RSCP Information 3. to see the Ec/Io values related to the selected cell click

Ec/Io Information If any change in the Cells menu window has been done or in general to plot a new cell it is necessary to select

to see the result in the map window. Fig. 7.54

shows an example.


176 176/480

5/24/2018


Fig . 7.54 Selecting (zoom on cell-data ) It is possible to center the map windows on displayed measurements, an auto zoom is performed. Selecting the option (Center on Cell ) the data will be displayed with the selected cell in the center of the map area. The combination of the two described options forces the map zoom to contain the whole available measurements for the selected cells and the cell itself. With the option (Sh o w w h o le r o u te ) it is possible to plot on the map area the entire route of the available measures. For the samples not related to the selected cell the route is displayed using black color. See Fig . 7.55

Fig . 7.55


177 177/480

5/24/2018


Selecting (Show all site-cells ) all the measurement data of the site corresponding to the selected cell will be plotted, using a shaded red, green and blue color (one for each sector). The results is similar to the one shown in Fig . 7.56

Fig . 7.56 Selecting Show all site-cells(only B S) the result is quite similar to the one produced by the previous option. In this case only the samples that are detected as Best server for the selected site will be plotted. The option (Save Scanner Detected lis t ) allows to save in a text file the list of the detected cells showed in the Cell menu window. The browser window of Fig . 7.57 is displayed to edit the desired file name.


178 178/480

5/24/2018


7.3.10 Cell bitmaps generation It is possible to generate with an automatic procedure the Server Order, RSCP and Ec/Io bitmap image files for every selected cell. Once the desired cell are selected as shown in Fig. 7.58 it is necessary to press (Automatic Bitm ap Generation ).

Fig . 7.58

If the button is pressed all the maps will be generated with the route displayed as described in the previous section. All the files are stored by default in the following folder: Projects\\Results\CellBitmaps

7.4 WARNING Objects The file warning.txt is stored in the folder: \Projects\\Environment\Script allows the user to define a sequence of messages/data to generate a specific warning every time that the sequence will be found in the messages/data of the Measurement Data table Scanner and/or Mobile section (see Chapter 5 and 11) or every time that a deviation in the defined sequence will be encountered, as configured in the script file itself. Please refer to Appendix for details on warning.txt editing. Every sequence defined in the warning.txt file has a name. These names are also available in the Field and Value menu of the Events menus described in section 7.2.6 and 7.3.6.


179 179/480

5/24/2018


8. STATISTICS MUSA offers mainly two formats of statistical information: graphical and numerical.

Graphical fo rmat With the Statistic Function options it is possible to obtain in a graphical format some information about the statistical behaviour of one series or the combination of two. In case of one series: • Distribution Function • Cumulative Distribution Function

In case of two series: • Joint Distribution • Tri-dimensional Histogram Distribution

Numerical format With the Statistical Mode function MUSA offers the possibility to obtain some Excel files in which information about statistical behaviour of one or more variables are available in numerical format according to user definitions stored in a script file. However, numerical statistics can be plotted on a map, as described in section 7.3.7.1. Specific statistical information are available when the T i m e Chart option is active as well.

8.1 Main Too lbar Bu ttons 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. , to enable Statistical Mode Function Statistical Mode

Load previous Statistic , to continue the updating of previous reports , to prepare script file used by statistics and warning Statistics Editor

Open Measurement, to load Scanner and/or Mobile files Distrib ution and CDF, to open the Distribution and CDF window Joint Distribution, to open the Joint Distribution window Clos e File, to close all previous loaded measurement files Time Charts , to access Charts option window MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

180 180/480

5/24/2018


8.2 Distribution and Cum ulative Distribution Function To access this option select Tools\Statistics\Distribu tion and CDF

the window in Fig. 8.1 appears

Fig . 8.1

8.2.1 Distribution Window Description This is a short description of the options available in the toolbar of the Distribution and CDF window of Fig . 8.1


181 181/480

5/24/2018


Save Bitm ap, to save the graph as Bitmap image in a file Expo rt Statistic, to export data plotted in the graph in a Text File Edit Title, to change the title of the graph Statis tic Series/Data Series, to switch between the standard series and the series defined in the user-configurable Stat.txt file Enable Filter, to apply a filtering condition to the current data Add Filter , to consider more than one filter. The new filter condition is applied to the already filtered data set obtained from previous filters. Series Selection , to select between the available series the variable to be plotted in the graph Interval, to set the interval width in which the values of the selected variable are regrouped Cumulative Distribution Function, to graphically represent the Cumulative Distribution Function for the selected variable Distribution Function, to graphically represent the Distribution Function for the selected variable Pie Distribu tion, to represent in a pie graph the percentage distribution of values of the selected variable % or Count Values , to switch vertical axes representation between percentage and count values % Activation, to show the percentile on the curve % Value, to set the value of percentile plotted on the curve Enable Mean Value, to show the Mean Value of the selected variable on the graph area in the relative test box Enable Std Dev Value, to show the Standard Deviation Value of the selected variable on the graph area in the relative test box

8.2.2 Using Distribution Window Functionalities In the drop down menu it is possible to select between the available series the variable of which the statistical information is wished (The series represent the Measurement Data table columns titles, see Chapter 5 and 12).


182 182/480

5/24/2018


Selecting (Cumulative Distribution Function ) in the graph area is shown the Cumulative Distribution Function of the chosen series, see Fig . 8.2.

Fig . 8.2 Clicking the button (Distribution Function ) the graph window shows the Distribution Function of the selected variable, see Fig. 8.3 .

Fig . 8.3 With the button (Pie Distribution ) the values percentage distribution of the selected variable is plotted on the graph. See Fig. 8.4 as example, in this case the chosen series is the Mobile Active Set.


183 183/480

5/24/2018


Fig . 8.4 In the graphs of Fig . 8.2 and Fig. 8.3 are reported the Mean value and the Standard Deviation Value for the chosen variable. By clicking on the area of the graph in which the two values are plotted it is possible to drag and drop the box that contains both. In the toolbar of the Distribution and CDF window (Fig . 8.1 ) selecting the two function buttons

Enable Mean Value Enable Std Dev Value it is possible to set which value to plot on the graph area. By typing a new number in the dialog box user may modify the width of the intervals in which the values of the variable are subdivided to build up the distribution. Fig . 8.5 and Fig. 8.6 show an example of Distribution Function with Interval set respectively to 1 and 5.


184 184/480

5/24/2018


Fig . 8.6 Selecting the two buttons

% Activation % Value user could decide to plot the percentile on the curve fixing the desired value. In Fig . 8.7 the percentile is fixed to 5%.

Fig . 8.7


185 185/480

5/24/2018


8.2.3 Handling of data The following Distribution and CDF window options allow to modify, to save and to export what is represented in the graph area. MUSA offers the possibility to change the title of one graph clicking

(Edit Title )

The dialog box of Fig . 8.8 will be opened to edit the new title.

Fig . 8.8

Selecting (Save Bitmap ) it is possible to store in a file a bitmap image of the graph area. The window of Fig . 8.9 appears to edit the desired file name.

Fig . 8.9 If necessary it is possible to export the data used to plot the curve of the desired series in an Excel File, selecting

(Export Statistic ).

The window of Fig . 8.10 appears to edit the desired file name.


186 186/480

5/24/2018


Fig . 8.10 The file stored has a format similar to the one presented in Fig . 8.13. Some general statistical information about the chosen variable are calculated and reported in the first part of the Excel file obtained.

Fig . 8.11


187 187/480

5/24/2018


8.2.4 Distribution Filters With the

option (Enable Filter ), it is possible to activate filtering functions.

Filter: In this frame, It is possible to set a single condition or two conditions (using And connector), in order to filter the distribution series. Single Condition: Set Filter Mode, Filter Column, Operation and Value (or a set of values if Operation is “IN” or “NOT IN”). The distribution values will be automatically filtered by this condition. Double Condition: Set all the filter fields as in the Single Condition, then click the “And” checkbox and set Operation and Value (or a set of values if Operation is “IN” or “NOT IN”). The two conditions should be both respected.

Filtering Mode Value, Same Time.

: there are three possible values: Same Record, Last

• Same Record: The distribution values will be filtered according to the filter

conditions and if a value is not available for the filtered series this record is discarded. • Last Value: The distribution values will be filtered according to the filter

conditions and if a value is not available for the filtered series, the last not null value is used. • Same Time: The distribution values will be filtered according to the filter

conditions and if a value is not available for the filtered series, the last not null value with the same timestamp is used.

Filter Column

: choose a Column for filtering the distribution series.

Operation: choose an Operation to apply at the Filter Column.


188 188/480

5/24/2018


Possible values are: • =: the Filter column value must be equal to the filter value. • <>: the Filter column value and filter value must be different. • >, >= , <, <=: to specify other kind of condition • IN: the Filter column value must be one or more values in the filter values list. • NOT IN: the Filter column value must not be one or more values in the filter

values list

Value

: choose a Value for the Filter Column.

Note: All the possible values are extracted from Measurement Data Filter column and are listed in this control. However, the user can type any wished value.

Values

: if the selected Operation is ‘IN’ or ‘NOT IN’, choose or

type one or more values using the Value control and then click the order to insert them in the current values list.

button in

And : click this checkbox to set a double filter condition, setting another operation and value (or values) for the second filter condition. With the button ( Add Filter ) it is possible to open a new filter frame. Setting new fields, the distribution values are filtered to respect simultaneously all the filters.

8.3 Joint Distribu tion Selecting Tools\Statistics\Joint Distribu tion

MUSA displays the window of Fig . 8.12 :


189

189/480

5/24/2018


Fig . 8.12

8.3.1 Joint Distribution Window Description This is a short description of the options available in the Joint Distribution window of Fig . 8.14.

X Variable , to choose the first variable and to set the width of the interval in which the chosen series values are regrouped to build up the Joint Distribution function

Y Variable , to choose the second variable and to set the width of the interval in which the chosen series values are regrouped to build up the Joint Distribution function Mean Variable, to select the variable of which the mean value is desired S h o w , to see the results on the graph area Save Bitmap, to save the graph area in a file as bitmap image More, to access the tri-dimensional histogram functions


190

190/480

5/24/2018


8.3.2 Using Joint Distribution Window Functionalities The first step is to choose the two variables of which the joint distribution is to be plotted, selecting them between the series available in these two drop down menus:

X Variable

Y Variable

The available series represent the Measurement Data table numeric columns titles (see Chapter 5 and 11). To see the relative curves plotted in the graph area is then necessary to select the button. An example of the possible result is shown in Fig. 8.13 .

Fig . 8.13 Referring to Fig . 8.13, for each value of Best Server CPICH Ec/Io (EcIo_1s) the blue curve reports the Mean value of Best Server CPICH RSCP (RSCP_1s) of all the measurement samples with that specific Ec/Io value. If it is enabled the Std Dev Option in not only the Mean value but also the Standard Deviation value is plotted on the graph area in a red curve. By default the X Variable selected in the corresponding dialog box is the one for which the Mean values and/or the Standard Deviation values are calculated. It is possible to decide that the Y Variable selected in the corresponding dialog box

Mean Variable becomes the one for which the Mean values and/or the Standard Deviation values are plotted, as shown in Fig . 8.14 .


191

191/480

5/24/2018


Fig . 8.14

As described before the dialog box permits to set the interval width in which the values of the selected variables are regrouped to build the distribution. Fig. 8.15 shows how the graph of Fig. 8.14 changes if for X Variable the interval width is set to 5 and for the Y Variable is set to 3.

Fig . 8.15

Selecting image.

(Save Bitmap ) the graph area will be saved in a file as a bitmap


192

192/480

5/24/2018


As always a window appears to edit the desired file name. See Fig . 8.16

Fig . 8.16

When the button (M o r e) is selected the Joint Distribution Window changes offering new features, see Fig . 8.17 .

Fig . 8.17


193

193/480

5/24/2018


Now, in the new part on the right side it is plotted a tri-dimensional histogram that represents the distribution of values of the X Variable and the Y Variable selected in the corresponding dialog box, see Fig . 8.18

Fig . 8.18

In the bottom taskbar are available some items to handle the graphical visualization. In Fig . 8.19 and Fig . 8.20 the function of every single item is defined.

Save 3D bitm ap

Rotation

Elevation

Fig . 8.19


194

194/480

5/24/2018


Zoom

Move Left/Right Move Up/down

Fig . 8.20 Two other charts are also available on the left side of the new part activated selecting the button . They represent a section of the tri-dimensional histogram of Fig. 8.18 , cut along the X axis or the Y axis. See Fig. 8.21 .

Fig . 8.21 The following options are available: • Selecting X or Y in the

Section user defines along which axis of the XY plane of the tri-dimensional graph the section will be cut. In the example of Fig . 8.21 the X axis is selected, i.e. the variable Best Server CPICH RSCP ( RSCP_1s).


195

195/480

5/24/2018


•

Sliding Change Section it is possible to define at which value of the selected axis the section will be cut. The value is reported on the right side of the slider and also on the graph titles.

• Clicking the button

or Dist CDF it is possible to save in a file the bitmap image of the Distribution graph section or the Cumulative Distribution Function graph section.

8.4 Statistic al Mode It is possible to activate this modality only before any Open measurement operation. If some measurements have been previously loaded it is necessary to close all files before starting Statistical Mode using Measurement\Close :

IMPORTANT: before accessing the Statistical Mode function please enable the option Options \Scramblin g co de as Cell ID

If this option is not enabled the Statistical Mode function will not produce any result.


196

196/480

5/24/2018


To activate Statistical Mode Measurem ent\Statistical Mode

select

the

following

main

menu

option

Now, when a Mobile and/or Scanner measurement file is loaded with the menu option Measurement\Open

MUSA produces a series of Excel report files in which are provided several statistical numerical information for the variables defined by user in the Stat.txt script file. This file is by default stored in: \Projects\\Environment\Script. All the Excel report files are saved in the folder: \Projects\\Results\Statistics. Every time warning:

(Statistical Mode ) option is selected MUSA generates the following


197

197/480

5/24/2018


If the user press the NO button, MUSA resets all the information stored in the Excel files generated before (report files will be erased). Only pressing YES button will be possible to continue the updating of statistic data (the showing the

button will change,

icon).

Three sceneries are available so the Stat.txt file is divided in 3 parts: 1. Cumulative Distribution Function (CDF) 2. Mobile Numeric Statistics 3. Messages Statistics In the following sections it will be described how to configure Stat.txt sections.

Important Following pages describe statistics details in terms of Stat.txt script file. Section . It permits the compilation of Stat.txt files, 8.4.5 introduce the Statistic Editor without any direct file editing.

8.4.1 Cumulative Distribution Function (CDF) 8.4.1.1 Scanner CDF This section begins with §SCANNER_CDF word followed by several scanner column names (written as in MUSA Measurement Data table reported in Fig . 8.22 , scanner left part) and the reserved word INTERVAL with the interval value used to build distribution.

Fig . 8.22 Example: §SCANNER_CDF RSCP_1s INTERVAL 1 ECIO_1s INTERVAL 1

For any column indicated here it will be automatically created a an example of report file is shown for the _SCANNER.xls file. In Fig . 8.23 EcIo_1s Scanner variable.


198

198/480

5/24/2018


Fig . 8.23 The corresponding Distribution Function or the Cumulative Distribution Function could be plotted opening the MUSA Distribution and CDF option (see 8.2 ) and selecting

in the window of Fig . 8.1 to access the series defined in this section.

The button in the Distribution and CDF window is active only if the Statistical Mo d e option is selected.

8.4.1.2 Mobile CDF This section begins with §MOBILE_CDF word followed by several mobile column names (written as in MUSA Measurement Data table reported in Fig . 8.22 , Mobile Data right part) and the reserved word INTERVAL with the interval value used to build distribution Example: §MOBILE_CDF ARSCP_1 INTERVAL 1 AECIO_1 INTERVAL 1

For any column indicated here it will be automatically created a _MOBILE.xls file. The structure of this file is very similar to the one presented in the example of Fig . 8.23 . The corresponding Distribution Function or the Cumulative Distribution Function could be plotted opening the MUSA Distribution and CDF option (see 8.2 ) and selecting

in the window of Fig . 8.1 to access the series defined in this section.


199

199/480

5/24/2018


The button in the Distribution and CDF window is active only if the Statistical Mo d e option is selected.

8.4.1.3 Joint Distribution This section begins with §JOINT_DISTRIBUTION word followed by several definitions in the following form: < NAME DEFINITION> = : INTERVAL , : INTERVAL

The left part could be any user defined name. The right part contains two columnvariable (written as in MUSA Measurement Data table reported in Fig . 8.22 , with SCANNER or MOBILE indication) and the reserved word INTERVAL with the interval value used to build distribution. Example: §JOINT_DISTRIBUTION DL_TROUGHPUT_vs_ECIO = MOBILE:ASRCP_1 INTERVAL 30,SCANNER:ECIO_1s INTERVAL 2

For any row defined here it will be automatically created a _vs_.xls file. An example of the file structure in case the variables selected were ARSCP_1 and ECIO_1s is shown in Fig . 8.24.

Fig . 8.24 When the Statistical mo de is enabled a new menu option is available in the Joint Distribution window of Fig. 8.13 : Full Statistic. See Fig . 8.25.


200

200/480

5/24/2018


Fig . 8.25 In the drop down menu of Fig . 8.25 it is possible to select one of the Joint Distribution defined previously in the Stat.txt file in the Joint Distribution section. It is possible to plot them as described in section 8.3 .

8.4.2 Mobile Numeric Statistics This section begins with §MOBILE_COL word followed by several mobile column names (written as in MUSA Measurement Data table, Mobile Data right part of the window of Fig . 8.22 ). Example: §MOBILE_COL DLThp BLER

The report_numeric.xls file will be automatically created, containing the following information for any mobile columns: • • • • •

samples count minimum maximum mean standard deviation

Fig. 8.26 displays an example of a report_numeric.xls file format in case the selected mobile columns were DLThp and BLER.


201

201/480

5/24/2018


Fig . 8.26

8.4.3 Message Statistics 8.4.3.1 Message declaration It is denoted by §MESSAGES word and it is composed by several lines with the following format:

= : Remark : as written in the MUSA Measurement Data table reported in Fig. 8.22 (column title), as written in MUSA Measurement Data Table (It is possible to right click on Measurement Data table to Copy values in the windows clipboard) Example: §MESSAGES MYVAR = L3MSG:rrcConnectionRequest CU = L3MSG:CellUpdate

8.4.3.2 Table definition It is composed by several tables. Each table begins with §TABLE: and it is composed by several lines with the following format:

= where could be:

a) single variable b) ,, c) RPN expression, like this: ,,,,,..

and could be: +, -, *, /, %, %C (%C = 100-%)

Example: §TABLE:MY STATISTICS A = VAR1 B = VAR1, VAR2, + [ VAR1 + VAR2 ]


202

202/480

5/24/2018


C = VAR1, VAR2, % C [ 100 - (VAR1/VAR2)*100 ] D = VAR1, VAR2, +, VAR3, * [ (VAR1 + VAR2) * VAR3 ] E = VAR1, VAR2, +, VAR3, VAR4, +, / [(VAR1 + VAR2) /(VAR3 + VAR4) ]

Each table definition provides MUSA all the information to produce an output report file report_

.xls with the following general format: *** TABLE *** Cell Name | SC #A #TOT col_name_1 col_name_2 .. col_name_N -------------------------------------------------------------------Cell 1 | Cell 2 | .... | Cell N |

where SC is the Scrambling Code, #A is the number of cell-in-active-set samples, #TOT is the total number of sample (Active Set + Monitor). In Fig . 8.27 an example is reported.

Fig . 8.27

8.4.4 Multiple files statistics updating Once the Stat.txt file is defined and the Statistical Mode option is kept active, it is possible to load and close several Mobile and/or Scanner measurement files. Every time a new measurement file is loaded MUSA updates the Excel report files, described in section 8.4.1, 8.4.2 and 8.4.3, with the new information corresponding to the defined conditions and variables in the Stat.txt sections. It is very important to remember that every time the Statistical Mode option the corresponding menu item)


(or

203

203/480

5/24/2018


is deactivated, selecting

again, the following dialog window will be shown:

If the user press the NO button, MUSA resets all the information stored in the Excel report files generated before. Only pressing YES button will be possible to continue the updating of statistic data (the the

button or the menu item will change, showing

icon).

Once this option is selected it is possible to load new measurements files knowing that the relative information will update the Excel report files already present in the folder Projects\\Results\Statistics.

8.4.5 Statistic Editor MUSA Statistic Mode function offers the possibility to obtain some Excel files in which the information about statistical behavior of one or more variables are available in numeric format according to user definitions stored in user-configurable Stat.txt script file.


204

204/480

5/24/2018


With the Statistic Editor function MUSA offers the possibility to configure the Stat.txt and Warning.txt files. These files are by default stored in: \Projects\\Environment\Script. All the Excel report files are saved in the folder: \Projects\\Results\Statistics. Common controls, available in the Statistic Editor: to clear all the columns in the Scanner or Mobile column list. These lists are calculated and updated every time the Statistic Editor is opened with a measurement file loaded in MUSA. These list are context-sensitive and are grouped by: (Scanner column) (Mobile column). There is also a sub grouping by file type: (Scanner sub grouping) (Mobile sub grouping)

to save the current configuration as a copy of the Statistic and Warning script files. to load in the Statistic Editor a previous copy of the Statistic and Warning script files. to apply all the changes (maintained in memory) to the Statistic and Warning script files, overwriting any previous Stat.txt and Warning.txt files. to discard all the changes to the Statistic and Warning script files. Three options are available then the Stat.txt file is divided in 3 parts: 1. Mobile Numeric Statistics 2. Messages Statistics 3. Cumulative Distribution Function (CDF) In the following sections will be described how to configure Stat.txt sections.

8.4.5.1 Mobile Numeric Statistics


205

205/480

5/24/2018


For each “Mobile Cell Stat” Definition will be created a report file named "REPORT_NUMERIC.XLS" containing the following information: • • • • •

samples count minimum maximum mean value standard deviation

Click on the

button to obtain the Mobile column list.

The button permits to add a Mobile Cell Stat Definition. With the (Insert Mode) Button down, click the column button in the Mobile column list or write the column name and press ENTER (the column will be added to the Mobile column list if not already existing). To delete a Mobile Cell Stat Definition, select it and then press the button.


(Delete)

206

206/480

5/24/2018


To modify the Mobile Cell Stat Definition’s column name, press the (Modify Mode button), click the new column or write a new column name and press ENTER.

Fig. 8.26 displays an example of a report_numeric.xls file format in case the selected mobile columns were DLThp and BLER.

8.4.5.2 Message Statistics The Editor permits the definition of Message Statistics using two parts: Messages, where the user define the variables to be counted, and Table, where it is possible the construction of tables composed of several variable formulas.

Messages

Click

to obtain the Scanner column list.

Click

to obtain the Mobile column list.


207

207/480

5/24/2018


To add a Message Definition, write the variable name, click a column button in the Scanner or Mobile column list and choose the corresponding message and then press the

(Add) button.

To delete a Message Definition, select it and then press the

(Delete) button.

To modify a Message Definition, after the changes to the variable name or a column or a message, press the

(Modify Message) button.

Tables

After the definition of least one Message, it is possible to proceed with the definition of a Table. For each Table Definition will be created a XLS report, as shown in Fig . 8.27 . Click

to obtain the Scanner column list.


208

208/480

5/24/2018


Click


To add a Table Definition, choose the table name, write the column name, write the expression (click Ok or press ENTER to apply it) and then press the button. To delete a Table Definition, select it and then press the

(Add)

(Delete) button.

To modify a Table Definition, modify the table name or the column name or change the expression (click Ok or press ENTER to apply it) and then press the Message) button.

(Modify

8.4.5.3 Scanner CDF

For each Scanner CDF Definition will be created a _SCANNER.xls report Click

to obtain the scanner column list.


209

209/480

5/24/2018


To add a Scanner CDF Definition in Insert Mode ( Insert Mode button down) choose the interval, click the column button in the Scanner column list or write the column name and press ENTER (the column will be add to the Mobile column list if not already existing). The Interval control permits the setting of the interval width in which the values of the selected variable are regrouped (binning process). To delete a Scanner CDF Definition, select it and then press the

button.

To modify a Scanner CDF Definition in Modify Mode ( Modify Mode button down) choose a different interval or click the column button in the Scanner column list (or write the column name and press ENTER). The Fig. 8.23 shows an example report that can be automatically save in the statistic output folder.

8.4.5.4 Mobile CDF

For each Mobile CDF Definition will be created a _ MOBILE.xls report.


210

210/480

5/24/2018


Click


To add a Mobile CDF Definition in Insert Mode ( Insert Mode button down) choose the interval, click the column button in the Mobile column list or write the column name and press ENTER (the column will be add to the Mobile column list if not already existing). The Interval control permits the setting of the interval width in which the values of the selected variable are regrouped (binning process). To delete a Mobile CDF Definition, select it and then press the To modify a Mobile CDF Definition in Modify Mode (

button.

Modify Mode button down)

choose different interval clickENTER). the column button in the Mobile column list (or write theacolumn name and or press The Fig . 8.23 shows an example report that can be automatically saved in the statistic output folder.

8.4.5.5 Joint Distribution


211

211/480

5/24/2018


For each Joint CDF Definition will be created a _vs_.xls report.

Press the Click

to obtain the Scanner column list. to obtain the Mobile column list.

To add a Joint CDF Definition, in Insert Mode (

Insert Mode button down), write

the name for the definition (it must be unique), with the (First Column) button down, choose an interval and a column name (click the column button in the Scanner or Mobile column list or write the column name and press ENTER) for the First Column and with the (Second Column) button down, choose an interval and a column name (click the column button in the Scanner or Mobile column list or write the column name and press ENTER) for the Second column. To delete a Joint CDF Definition, select it and then press the

button.

To modify a Joint CDF Definition, in Modify Mode (Modify Mode button down

),

choose a different name for the definition (press ENTER), with the (First Column) button down, choose an different interval or a column name (click the column button in the Scanner or Mobile column list or write the column name and press ENTER) for the First Column and with the

(Second Column) button down,

choose a different interval or a column name (click the column button in the Scanner or Mobile column list or write the column name and press ENTER) for the Second column.

8.4.6 Stat.txt example # 1.1) ********************************************************************* §SCANNER_CDF RSCP_1s INTERVAL 1 ECIO_1s INTERVAL 1

# 1.2) ********************************************************************* §MOBILE_CDF ARSCP_1 INTERVAL 1 AECIO_1 INTERVAL 1 UeTxP INTERVAL 1 DLThp INTERVAL 10 # 1.3) ********************************************************************* §JOINT_DISTRIBUTION RSCP1_vs_ECIO1 = SCANNER:RSCP_1s INTERVAL 1, SCANNER:ECIO_1s INTERVAL 2 ARSCP1_vs_AECIO1 = MOBILE:ARSCP_1 INTERVAL 1, MOBILE:AECIO_1 INTERVAL 2 DL_TROUGHPUT_vs_AECIO1 = MOBILE:DLThp INTERVAL 30,


212

212/480

5/24/2018


MOBILE:AECIO_1 INTERVAL 2 # 2) ********************************************************************* §MOBILE_COL DLThp BLER # 3.1) ********************************************************************* §MESSAGES #GENERAL OLD STAT #CMserv = NASMsg:MM CM SERVICE REQUEST #CCconn = NASMsg:CC CONNECT #CCdiscn = NASMsg:CC DISCONNECT #Active Set Size AS1=#AS:1 AS2=#AS:2 AS3=#AS:3 #AGILENT RaBS_A=RRCMsg:Radio Bearer Setup HO3g_2g_A=RRCMsg:Handover From UTRANCommand GSM T_3_A=Warning:T_3_A Sok_3_A=Warning:Sok_3_A F_3_A=Warning:F_3_A T_2_A=Warning:T_2_A Sok_2_A=Warning:Sok_2_A F_2_A=Warning:F_2_A #NEMO RaBS_N=RRCMsg:RADIO_BEARER_SETUP HO3g_2g_N=RRCMsg:HANDOVER_FROM_UTRAN_COMMAND_GSM T_3_N=Warning:T_3_N Sok_3_N=Warning:Sok_3_N F_3_N=Warning:F_3_N T_2_N=Warning:T_2_N Sok_2_N=Warning:Sok_2_N F_2_N=Warning:F_2_N # 3.2) ********************************************************************* # # Association rules # §TABLE:TEST MEASUREMENTS # #AGILENT 3G # Attempts_3g_AGILENT=T_3_A Setup_ok_3g_AGILENT=Sok_3_A Call_ok_3g_AGILENT=F_3_A HO 3g->2g_AGILENT=HO3g_2g_A AccessRate_3g_AGILENT=Sok_3_A,T_3_A,% DropRate_3g_AGILENT=F_3_A,Sok_3_A,HO3g_2g_A,-,%C # #AGILENT 2G # Attempts_2g_AGILENT=T_2_A Setup_ok_2g_AGILENT=Sok_2_A Call_ok_2g_AGILENT=F_2_A AccessRate_2g_AGILENT=Sok_2_A,T_2_A,% DropRate_2g_AGILENT=F_2_A,Sok_2_A,HO3g_2g_A,+,%C # #AGILENT TOT # Attempts_TOT_AGILENT=T_3_A,T_2_A,+ Setup_ok_TOT_AGILENT=Sok_3_A,Sok_2_A,+ AccessRate_TOT_AGILENT=Sok_3_A,Sok_2_A,+,T_2_A,T_3_A,+,% DropRate_TOT_AGILENT=F_3_A,F_2_A,+,Sok_3_A,Sok_2_A,+,%C #


213

213/480

5/24/2018


#NEMO 3G # Attempts_3g_NEMO=T_3_N Setup_ok_3g_NEMO=Sok_3_N Call_ok_3g_NEMO=F_3_N HO 3g->2g_NEMO=HO3g_2g_N AccessRate_3g_NEMO=Sok_3_N,T_3_N,% DropRate_3g_NEMO=F_3_N,Sok_3_N,HO3g_2g_N,-,%C # #NEMO 2G # Attempts_2g_NEMO=T_2_N Setup_ok_2g_NEMO=Sok_2_N Call_ok_2g_NEMO=F_2_N AccessRate_2g_NEMO=Sok_2_N,T_2_N,% DropRate_2g_NEMO=F_2_N,Sok_2_N,HO3g_2g_N,+,%C # #NEMO TOTALE # Attempts_TOT_NEMO=T_3_N,T_2_N,+ Setup_ok_TOT_NEMO=Sok_3_N,Sok_2_N,+ AccessRate_TOT_NEMO=Sok_3_N,Sok_2_N,+,T_2_N,T_3_N,+,% DropRate_TOT_NEMO=F_3_N,F_2_N,+,Sok_3_N,Sok_2_N,+,%C # #ASS STAT # ASS1=AS1 ASS2=AS2 ASS3=AS3

8.5 Time Chart Statistics When the Time Charts window option is open (see section 7.1), it is possible to select the Statistics menu as shown in Fig . 8.28 .

Fig . 8.28


214

214/480

5/24/2018


In the drop down menu of Fig. 8.28 user should choose the series on which to calculate statistics. Pressing , for the selected series it is possible to read in the right part of the window some statistical information calculated only for the visible samples of the current time interval in the graph area of Fig . 8.28. In Fig . 8.29 is shown the result obtained for the Scanner RSCP_1s series of Fig . 8.28.

Fig . 8.29 For the selected series it will be reported: • Time interval start time • Time interval stop time • Number of samples of the series in the time interval • Minimum Value of the series in the time interval • Maximum Value of the series in the time interval • Mean Value of the series in the time interval • Standard Deviation Value of the series in the time interval • All correlation factors with the other available series


215

215/480

5/24/2018


If a different zoom is performed new results will be available. In Fig . 8.30 a new time interval has been defined zooming on the series of Fig . 8.28 .

In Fig . 8.31 results after a new click on

are displayed.

Fig . 8.30

Fig . 8.31


216

216/480

5/24/2018


8.6 Warning Objects 8.6.1 Using Warning Messages in Statistics The file warning.txt stored in the folder: \Projects\\Environment\Script allows the user to define a sequence of messages/data to generate a specific warning every time that the sequence will be found in the messages/data of the Measurement Data table Scanner and/or Mobile section (see Chapter 5 and 12) or every time that a deviation in the defined sequence will be encountered, as configured in the file itself. Please refer to the next paragraph or to the Appendix for details on warning.txt editing. Every script has a name. Through these warning.txt object sequence names it isdefined possibleintothe make a reference to a file specific sequence in the Stat.txt file with the procedure described in section 8.4. In this way it is possible to obtain a statistic of the occurrences of a desired sequence.

8.6.2 Using Statistic Editor to customize Warning Script The Warnings page in the Statistic Editor can be used to prepare the warning.txt file. This is not actually a statistical object, but warning messages can be defined as Message Variables, as described in 8.4.5.2.


217

217/480

5/24/2018


Press the

to obtain the scanner column list.

Click

to obtain the mobile column list.

To add a Warning Definition, choose a warning message then set position and logic, after that clic k the column button in the Scanner or Mobile column list or write the column name and press ENTER (the column will be added to the Scanner or Mobile column list if not already existing), choose the corresponding message, so it is possible to add Cols/Messages pressing ENTER or then press the

(Add Col/Message) button,

(Insert) button.

To delete a Warning Definition, select it and then press the

(Delete) button.

To modify a Warning Definition, choose different definition settings and then press the Click

(Modify) button. to delete the selected column

8.7 Statistics from Mob ile CS Message Flo w MUSA is able to get automatic statistics and KPI analyzing the mobile CS message flow. To enable this function, after mobile data loading, select the menu View \Mobile CS Tables :

or press the Mobile CS Tables button on the main tool bar:

Please see Chapter 12 for a detailed description of this feature.


218

218/480

5/24/2018


9. COVERAGE OPTIMIZATION With the Optimization option it is possible to simulate the effect that a change in a particular parameter of a cell (within a predefined set) produces on field. It is important to keep in mind that the results that are shown affect only the measurements loaded and only the portion in which at least one sample for the cell “optimized” is found. No predictions are available.

9.1 Main Toolb ar Butto ns 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.

Clos e File, to close all previous loaded measurement files Route, to open Route map visualization window Coverage Simu lation, to load the parameter table for optimization and enable Optimization options Open Measurements, to load Scanner and/or Mobile files

9.2 Op en Optim ization tool If some measurements have been previously opened it is necessary to close all files before starting with the optimization tool, using Measurement\Close :


219

219/480

5/24/2018


This is due to the fact that MUSA has to load the parameter table before measurement loading. Now it is possible to select Scanner\Load for Optimization :

If everything is set in the right way the Coverage Optimization window is displayed, as shown in Table 9.1 :

Table 9.1


220

220/480

5/24/2018


Next step is to open the measurement file using Measurement\Open :

When loading operations are terminated, in the Coverage Optimization window ( T able 8 .1 ) all function buttons are active.

Note : when optimization tool is activated it is possible to load only scanner data.

9.3 Heights inform ation To perform simulations MUSA uses data contained in the territory height information files expected available in the folder: \Projects\\Environment\Heights. Those files describe the territory height of the area that contains the measurements that are to be analyzed. An index file is needed in order to give a geographical reference to all the territory height maps. This file has to be named h_index.txt (see Appendix) If no heights files are available, MUSA presumes that the territory is an ideal plane at height of 0 m a.s.l.

9.4 Coverage Optimization Window Description What follows is a short description of the fields of the Coverage Optimization table (Table 8 .1 ) and of the options available in the relative window. For every row of the table it is possible to find the items listed below: Cell alias name Antenna Height a.s.l. [m] (in brackets the height referred to soil level) Cell azimuth [degree] Electrical Downtilt [degree]


221

221/480

5/24/2018


Mechanical Downtilt [degree] CPICH power [dBm] CPICH power Attenuation [dB] Percentage of power expected on control channel, expressed as a percentage of CPICH power Percentage of power expected on dedicated channel, expressed as a percentage of max Cell Irradiated Power Max Cell Irradiated Power [dBm] Model of Antenna of the cell Only parameters in light yellow and green columns are modifiable. Specifically: Az, ET , MT, CPICH, Control_Pwr and Traffic_Pwr . The function buttons available are: , to export table data in a Text file format Expo rt Parameters , to load a parameter configuration file .op previously saved Load Delta , to save the parameter modifications in a .op file Save Delta

Change Parameter , to change the value of a parameter selected in the table Mobi le Height , to set the expected handset antenna height referred to ground level (1.5 m default) Delta Color , to set in which color the modifications are to be painted in the map Network Load , to change the parameter Traffic_Pwr for all the cells in the Coverage Optimization Table Redo Pixelling…, to perform again pixel process after some parameter change Close Optim izer, to close the optimization tool

9.5 Coverage Optim ization adjustm ents To change the value of a settable parameter on the Coverage Optimization table there are two ways. 1. click on the parameter and then select the following button:

Change Parameter 2. double click on the parameter itself.


222

222/480

5/24/2018


In any case it appears a window similar to the following one:

At this point it is possible to write the new value for the chosen parameter. After OK selection, changes are presented in the table highlighted with the color selected in

Delta Color The new value is coupled with the old one as shown in Fig . 9.1 :

Fig . 9.1 When the Route map option is activated in

for the cell on which some parameters have been modified the name is plotted with the color chosen in Delta Color as the picture in Fig. 9.2 shows:


223

223/480

5/24/2018


Fig . 9.2 Moreover, depending on the type of parameter adjusted, a specific sign is shown on cell arrow as described below:

o For an Azimu th clockwise change

For an Azimu th anti clockwise change o

o For a Tilt change:

o For a CPICH power change:

o For a Control_Pwr or Traffic_Pwr change:


224

224/480

5/24/2018


In the Route Map window is possible also to observe MUSA simulation results after modifications i.e. to check how a change takes effect on the measurements, as the and Fig . 9.4 shows: Fig. 9.3

Fig . 9.3

Fig . 9.4 In the dialog box


225

225/480

5/24/2018


Mobile Height it is possible to set the estimated average mobile height during measurement campaign. This affects the coverage simulation algorithm. The (Global Attenuation) button permits the application of an attenuation value (dB) to all the cells. It could require few minutes to be executed. For a detailed description of the load parameter options • •

and the button manual.

are related to the Load Simulation Features described in this

When at least one change is made in Coverage Optimization table the pixel procedure (see Chapter 5) could be performed again to compare the results in term of pollution, islands, etc. obtained from the simulations on measurements data. Select (Redo Pixelling… ) to start the new pixel procedure. MUSA saves in the relative folders a new version of the report files (see Chapter 5) with the suffix “_opt”. Once the pixel procedure is terminated selecting one of the options of the Coverage Analysis menu:

it is possible to investigate the effect of the parameter changes. If the button is deselected after a Redo Pixelling process a new access to a Coverage Analysis menu function will report the pre-optimization results.


226

226/480

5/24/2018


9.6 Saving, Loading and Exporting M odifications User can save all changes made in Table 9.1 using the button

(Save Delta ).

The parameter modifications are saved in a .op file where all the differences between the starting situation are stored. The browser window in Fig . 9.5 appears to allow filename choice:

Fig . 9.5 Selecting the button (Load Delta ) MUSA permits to load a previous saved .op file. The browser window in Fig. 9.6 is displayed:

Fig . 9.6 MUSA sets by default the folder Projects\\Results\Optimization as the folder for .op files. Selecting the option (Export Parameters ) the content of the Coverage ) is exported in a Text file. User should choose folder Optimization table ( Table 9.1 and filename in the window of Fig . 9.7 :


227

227/480

5/24/2018


Fig . 9.7 The file saved has the format showed in Fig . 9.8 :

Fig . 9.8 Selecting Measurement\close


228

228/480

5/24/2018


MUSA generates in any case the warning displayed in Fig . 9.9 , whether or not the button was previously selected, to remind that every changes in parameters will be lost if not saved.

Fig . 9.9 If Yes is selected the Scanner Measurement file loaded for optimization will be closed.


229

229/480

5/24/2018


10. NEIGHBOURS LIST OPTIMISATION Neighbours Analyzer (AdA module) is a Nokia Siemens Networks tool for the neighbour relationships analysis, based on the current radio conditions monitored by means of radio measurements. Starting from the knowledge of the Network under investigation, in terms of RNC information (OFD/ALC files), cells information (location, azimuth, etc.), and the relative RF environment (RSCP and Ec/Io collected data), AdA provides the lists of potential neighbours to be added or removed.

The implemented method consists of the following steps: -

-

-

-

-

averaging of the collected measurement on pixel basis; for each pixel a Best server cell is defined (the cell emerging as Best Server in the most samples falling in a pixel, will be elected Best Server for that pixel); for each pixel all the other detected cells are considered, and the level of these cells is compared with the Best Server cell level (cells with a level below a fixed threshold will be discarded); using two different values, minimum and maximum gap from the Best Server, two different lists are defined (one for adjacent cell addition and one for removal, respectively); the addition/deletion lists could be compared with the neighbour lists defined in the RNC database to arrive to a final proposal for the neighbours to be added and removed; the lists could be checked on the map cell by cell with respect to the starting RNC database neighbouring cells definitions.

For more details about the pixel-based analysis and relative options (pixel dimensions, max and min gaps, threshold, etc.) please refer to section 5.5.

10.1 Opening Neighbou rs A nalyzer To start AdA, select Neighbours Analyzer from Tools menu, Tools\Neighbours Analyzer (Fig . 10.1 ).


230

230/480

5/24/2018


Fig . 10.1

Alternatively, click Neighbours Analyzer button on MUSA toolbar (Fig . 10.2 ).

Fig . 10.2

AdA uses the Network currently opened in MUSA so it is a good rule to verify always that the Project and the Network opened in MUSA are the right ones (Fig . 10.3 ).

Fig.10.3 To create a new Project, a new Network file or simply to select a previously created Projects/Network please refer to chapter 4. Apart from the networks information, three files are necessary to make AdA works properly: • Scanner Detected cells file (ScannerDetected.txt):

as could be dangerous to change neighbour relationships involving cells not measured at all, it is advisable adding/removing neighbours regarding only cells measured by the scanner (i.e. scanner detected). • Minimum Gap from Best Server file ( Add.pxl):

this file contains the list of cells measured in a pixel and with the minimum dB gap from Best Server cell RSCP and Ec/Io. • Maximum Gap from Best Server file ( Remove.pxl ):

this file contains the list of cells measured in a pixel and with the maximum dB gap from Best Server cell RSCP and Ec/Io. Make sure to have these files before the beginning of neighbour lists optimization. Starting AdA a window like the one displayed in Fig.10.4 appears:


231

231/480

5/24/2018


Fig.10.4 This is a list of all the neighbours discarded in the files mentioned before because AdA has found some Scrambling Codes with no cells Alias associated in the UMTS Network Site Database file. Any fault occurred during the initial loading procedure will be reported here. Press OK, AdA window appears as shown in Fig.10.5 . In the main window it is possible to recognize seven sections: -

AdA main toolbar

-

Present Lists panel

-

Present Cell Sets panel

-

Present Layers panel

-

Navigation panel

-

Exceeding Cells panel

-

Display panel


232

232/480

5/24/2018


Fig.10.5 Each panel is resizable. The respective features will be described in the following.

10.2 Ad A Projects The term “Neighbours Analyzer project” will be used in the following to refer to the “current state” of the tool, included all the actions undertaken (i.e. neighbour relationships added or removed) from the opening up to the current instant. All the info characterizing this state could be saved in an AdA Project File (.apf ). In the main toolbar of AdA (Fig.10.6 ) there are 4 specific functional buttons for AdA projects management.

Fig.10.6

•

Re-impo rt Network , to reload the data of the Network currently opened in MUSA. Scanner Detected Cells, Minimum Gap from Best Server and Maximum Gap from Best Server files will be also reloaded if stored in the folder: \Projects\\Results\Adjacents


233

233/480

5/24/2018


•

Open Project , to open a previously saved AdA project ( .apf ). Once an .apf file is opened, AdA exactly restarts from the state previously saved.

•

Save Project , to save an AdA project (.apf ). The whole current state of the tool, as specified above, will be saved. In any case, closing the application in whatever moment (also without saving), AdA automatically saves in the folder \Projects\\UserSettings

• an .apf file with the same name of the Network currently opened in MUSA

(.apf ). At the next opening, if no project is loaded by means of Open Project function, AdA will restart from the state saved in this .apf file. •

Form ula Manager , to enable formulas management functions. See section 10.10 for further details.

10.3 Neighbo ur Lists The Present Lists panel shows all the neighbour lists loaded by the tool. Each element belonging to a list in this section represents a single neighbour relationship (Fig.10.7 ).

Elements of a Cell Set

Cell B (target cell)

Adj[ A,B]

Element of a List

Cell A

(source cell)

Fig.10.7

At AdA starting at least one list is loaded, called as the Network file currently opened in MUSA. It contains all the neighbours stored in the RNCs database related to this Network file (Fig.10.8 ).


234

234/480

5/24/2018


Fig.10.8 If a “pixel-based” processing of scanner collected data was previously done (see section 5.5), AdA is able to recognize the Minimum Gap from Best Server and Maximum Gap from Best Server files (Add.pxl and Remove.pxl ) saved by MUSA in the folder: \Projects\\Results\Adjacents. The neighbours declared in these files will be loaded in the Present Lists panel automatically at the start (Fig.10.9 ). In any case, it is possible to load them using the Load button.

Fig.10.9


235

235/480

5/24/2018


On the right side of the Present Lists panel there are the following functional buttons: •

Load , to re-import network data and load files. The following option are available:

o Imp o r t N e tw o r k , to reload the data of the Network currently opened in MUSA. o ADA File , to load files previously exported by AdA ( .txt files) , to load Minimum Gap from Best Server and Maximum Gap o Pixel File from Best Server files (Add.pxl and Remove.pxl) from a folder different from the default one (Projects\\Results\Adjacents)

o Tornado , to load neighbour lists in Tornado/Planet format (up to V2.8) o X M L , to load neighbour lists in TornadoN format •

Save , to save neighbour lists. In particular the following options are available: , to save a neighbour list selected from Present Lists panel in o ADA File a text file with the following format: [ADJS PROPERTIES] … [ADJS] [Cell]-[Adjt Cell added/removed; distance]-[Adj Cell added/removed; distance]-[…

[Cell]-[Adjt Cell added/removed; distance]-[Adj Cell added/removed; distance]-[… …

These files can be re-opened by AdA.

o ADA Simple List , to save a neighbour list selected from Present Lists panel in a text file with the following format: [Cell]-[Adjt Cell to add/rem] [Cell]-[Adjt Cell to add/rem] …

, to save a neighbour list selected from Present Lists o ADA Cellid List panel in a text file with the following format: [Cell]-[Adjt Cell added/removed; cellid]-[Adj Cell added/removed; cellid]-[Network… [Cell]-[Adjt Cell added/removed; cellid]-[Adj Cell added/removed; cellid]-[ Network…

•

R e n a me, to rename a neighbour list selected from Present Lists panel.

•

Delete , to delete a neighbour list selected from Present Lists panel.


236

236/480

5/24/2018


•

Fo r mu la , to execute formulas on neighbour lists selected from Present Lists panel. The resultant lists will appear in Present Lists panel (see 10.4)

IMPORTANT: the meaning of the options available pressing the button

described above is valid also for the different windows described in the whole chapter when the reference is Load an Adj List button. When the reference is Load Cell set button please refer to section 10.5 for the respective meaning explanation.

10.4 Present L ist Panel Form ulas Once the Present List Formula button is selected, AdA shows the Select A Formula window (Fig.10.10 ). Here it is possible to select one of 7 built in formulas already available.

Fig.10.10 It follows a detailed description of the formulas.

CLOSE WITH RECIPROCAL ADJS (CLOSING function) Let A be a neighbour list in Present Lists panel, the result of this function is

(

[ ] U A)

RESULT = MISSING A

This function allows addition of missing reciprocal neighbour relationship to the starting list (list A). This means that if in the list A there is the relation Adj[ x ,y ] between cell x and cell y , but the reciprocal relation Adj[y ,x ] is missing, the resultant list will contain both Adj[ x ,y ] and Adj[y ,x ]. (See also MISSING ADJS function). Selecting the CLOSE WITH RECIPROCAL ADJS formula, the Formula window in Fig.10.11 is activated.


237

237/480

5/24/2018


Fig.10.11 Enter the desired name for the resultant list in List Name (default name: CLOSE WITH RECIPROCAL ADJSn). Until there is no argument selected in List to close , a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Formula arguments can be selected from Present Lists clicking Select an Adj List button ( ), or from another folder clicking Load an Adj List button ( the argument is selected, the R EAD Y message (in green) appears. Click OK to execute the formula.

). When

The resultant list can be considered a “CLOSED” (in terms of reciprocal relationships) list and this function can be defined as “CLOSING” function. It is used implicitly in ADD LIST TO BE VERIFIED and REMOVE LIST TO BE VERIFIED formulas. This function will be used from the user only for new formulas building.

CLOSE W ITH MISSING INTRA-SITE A DJS (SITE-CLOSING function) Let A be a neighbour list in Present Lists panel, then the result of this function is:

RESULT = MISSING _ SITE [ A] U A This function ensures that all the cells belonging to the same site are mutual neighbours. (See also SITE MISSING ADJS). Selecting the CLOSE WITH MISSING INTRA-SITE ADJS formula, the Formula window in Fig.10.12 is activated.


238

238/480

5/24/2018


Fig.10.12 Enter the desired name for the resultant list in List Name (default name: CLOSE WITH MISSING INTRA-SITE ADJSn). Until there is no argument selected in the List warning (in red) is displayed in the bottom part of the to close field, a NOT READY Formula window. Formula arguments can be selected from Present Lists clicking Select an Adj List button (

), or from another folder clicking Load an Adj List

button ( ). Once the argument is chosen, the READY message (in green) appears. Click OK to execute the formula. This formula can be defined as “SITE-CLOSING” function and is used implicitly in FINAL NETWORK formula. This function will be used from the user only for new formulas building.

ADD L IST TO BE VERIFIED Selecting this formula it is possible to obtain the following result:

[NET ])SCNDET RESULT = ((CLOSING [GAPMIN FILTERED ]) − CLOSING

Where: NET list is the Network list containing all the neighbours stored in the RNCs database of the Network itself. GAPMIN list is the Minimum Gap from Best Server list SCNDET list is the Scanner Detected Cells list

This formula returns the list of neighbour relationships missing in the Network list, but present in the Minimum Gap from Best Server list. Firstly, the Minimum Gap from Best Server list is filtered to extract neighbour relationships matching at the same time the conditions on minimum gap & threshold


239

239/480

5/24/2018


set in the Adjacent menu in the Pixel Option Window (see section 5.5). The filtering criterion cannot be modified from the user. This list and the Network list are “closed” to ensure the reciprocity properties (Adj[ x ,y ] ⇔ Adj[y ,x ]). Finally, the difference between these two lists is calculated. The neighbour relationships that could be added to the Network neighbour list are the ones that match the conditions on min gap and threshold and that are missing in the Network list. In this operation, only the scanner detected cells are considered. Selecting the ADD LIST TO BE VERIF IED formula, the Formula window in Fig.10.13 is activated.

Fig.10.13

Enter the desired name for the resultant list in List Name (default name: ADD LIST TO BE VERIFIEDn). Until no arguments are selected in Pixel Add List, Network List and Scanner De tected Cell Set, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Formula arguments can be selected from Present Lists/Cell Sets clicking the Select an Adj List/Cell Set button ( from another folder clicking Load an Adj List/Cell Set button ( arguments are selected, the READY message (in green) appears. Click OK to execute the formula.

/

), or

). When all the

Typical formula arguments for standard Neighbours optimization process are: • In Pixel Add List: PIXELS_ADD list of Present Lists panel • Network List of Present Lists panel • In Scanner Detected Cell Set: SCANNER_DETECTED set in Present Cell

Sets panel.

REMOVE LIST TO B E VERIFIED Selecting this formula the following result is obtained:


240

240/480

5/24/2018


RESULT = {((CLOSING [NET ]) − CLOSING [GAPMAX FILTERED ])SCNDET }DISTANCEFI LTERED

Where: NET list is the Network list containing all the neighbours stored in the RNCs database forming the Network itself GAPMAX list is the Maximum Gap from Best Server list SCNDET list is the Scanner Detected Cells list This formula returns the list of neighbour relationships present in the Network list, but missing in the Maximum Gap from Best Server list. Firstly, the Maximum Gap from Best Server list is filtered to extract neighbour relationships matching at the same time the conditions on maximum gap & threshold set in the Adjacent menu in the Pixel Option Window (see section 5.5). The filtering criterion cannot be modified from the user. This list and the Network list are “closed” to ensure the reciprocity properties (Adj[ x ,y ] ⇔ Adj[y ,x ]). Then the difference between these two lists is calculated. The neighbours that could be removed from the Network neighbour list are the ones that match the conditions on min gap and threshold and that are missing in the Network list. In this operation, only the scanner detected cells are considered. Finally, the filtering by distance operation returns, cell by cell, a neighbour relationship only when the source-to-target cell distance is greater than the mean distance calculated on all the neighbours of the cell itself. Selecting the REMOVE LIST TO BE VERIFIED formula, the Formula window in Fig.10.14 is activated.

Fig.10.14 Enter the desired name for the resultant list in List Name (default name: REMOVE LIST TO BE VERIFIEDn). Until no arguments are selected in Network List, Pixel

Remove List and Scanner Detected Cell Set, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Formula arguments can be MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

241

241/480

5/24/2018


selected from Present Lists/Cell Sets clicking Select an Adj List/Cell Set button ( ), or from another folder clicking Load an Adj List/Cell Set button ( all the arguments are selected, the READY message (in green) appears.

/

). When

Click OK to execute the formula. Typical formula arguments for standard Neighbours optimization process are: • Network List in Present Lists panel • In Pixel Remove List :PIXELS_REMOVE list in Present Lists panel • In Scanner Detected Cell Set: SCANNER_DETECTED set in Present Cell Sets panel.

FINAL NETWORK Let A be a neighbour list in the Present Lists panel, this formula lead to the following result:

RESULT = SITE _ CLOSING[CLOSING[ A] ] The formula performs CLOSING and SITE-CLOSING operations on a given list. Selecting the FINAL NETWORK formula, the Formula window in Fig.10.15 is activated.

Fig.10.15 Enter the desired name for the resultant list in List Name (default name: FINAL NETWORKn). Until no argument is selected in the Verified Network List, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Formula arguments can be selected from Present Lists clicking Select an Adj List


242

242/480

5/24/2018


button ( ), or from another folder clicking Load an Adj List button ( all the arguments are selected, the READY message (in green) appears. Click OK to execute the formula.

). When

Typical formula argument in Verified Network List for standard Neighbours optimization process is the list obtained clicking Backup a copy of “To Edit” List button (

) after neighbours addition and removal (see 10.7)

FINAL ADD LIST The final result of this formula is:

RESULT = VERIFIED _ NET − NET Where: VERIFIED_NET is the verified network list NET the initial network list The formula calculates the difference between the two lists and returns the added neighbour list (see also DIFFERENCE function). The resultant list is “closed”.

Selecting the FINAL ADD LIST formula, the Formula window in Fig.10.16 is activated.

Fig.10.16


243

243/480

5/24/2018


Enter the desired name for the resultant list in List Name (default name: FINAL ADD LISTn). Until no arguments are selected in Verified Network List and Initial Network List, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Arguments can be selected from Present Lists clicking Select an Adj List button ( ), or from another folder clicking Load an Adj List button ( ). When all the arguments are selected, the READY message (in green) appears. Click OK to execute the formula.

FINAL REMOVE LIST

The final result of this formula is:

RESULT = NET − VERIFIED _ NET

Where: VERIFIED_NET is the verified network list NET the initial network list The formula calculates the difference between the two lists and returns the removed neighbour list (see also DIFFERENCE function). The resultant list is “closed”. Selecting the FINAL REMOVE LIST formula, the Formula window in Fig.10.17 is activated.

Fig.10.17 Enter the desired name for the resultant list in List Name (default name: FINAL REMOVE LISTn). Until no arguments are selected in Verified Network List and Initial Network List, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Arguments can be selected from Present Lists clicking Select


244

244/480

5/24/2018


an Adj List button ( ), or from another folder clicking Load an Adj List button ( ). When all the arguments are selected, the READY message (in green) appears. Click OK to execute the formula.

10.4.1 Present Lists Panel Functional Buttons Using the following elementary functions the user could implement new formulas on Present Lists panel element. •

UNION Let A and B be two lists, ( A U B) returns all and only the members belonging to A or to B. From a logical point of view, it acts as an OR function. Clicking the Union button the Formula window in Fig.10.18 is activated.

Fig.10.18 Enter the desired name for the resultant list in List Name (default name: UNIONn). Until no arguments are selected in List A and List B, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Arguments can be selected from Present Lists clicking Select an Adj List button (

), or from another folder clicking Load an Adj List button

( ). When all the arguments are selected, the READY message (in green) appears. Click OK to execute the formula. •

INTERSECTION Let A and B be two lists, ( A n B) returns the elements common to A and B. From a logical point of view, it acts as an AND function. Clicking the Intersection button the Formula window in Fig.10.19 is activated.


245

245/480

5/24/2018


Fig.10.19 Enter the desired name for the resultant list in List Name (default name: INTERSECTIONn). Until no arguments are selected in List A and List B, a warning (in red) is displayed in the bottom part of the Formula NOT READY window. Arguments can be selected from Present Lists clicking Select an Adj List button (



DIFFERENCE Let A and B be two lists, (A - B) returns the elements belonging to A and not present in B. Note that the difference function doesn’t benefit of the commutative property, that means ( A - B) ≠ (B - A). Clicking the Difference button the Formula window in Fig.10.20 is activated.

Fig.10.20


246

246/480

5/24/2018


Enter the desired name for the resultant list in List Name (default name: DIFFERENCEn). Until no arguments are selected in List A and List B, a warning (in red) is displayed in the bottom part of the Formula NOT READY window. Arguments can be selected from Present Lists clicking Select an Adj ), or from another folder clicking Load an Adj List button ( List button ( ). When all the arguments are selected, the READY message (in green) appears. Click OK to execute the formula.

•

L O N E AD JS Let x and y be two cells contained in a neighbour list. If the relation Adj[ x ,y ] exists, but does not exist the relation Adj[y ,x ], then Adj[ x ,y ] is called Lone Neighbouring Relationship (Fig.10.21 ). This function extracts all the lone neighbouring relationships from a list.

Cell y

LONE Adj[ x ,y] Adj[y ,x]

MISSING

Cell x

Fig.10.21

Clicking the Lone Adjs button the Formula window in Fig.10.22 is activated.

Fig.10.22 MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

247

247/480

5/24/2018


Enter the desired name for the resultant list in List Name (default name: LONE ADJSn). Until there is no argument selected in List A, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Arguments can be selected from Present Lists clicking Select an Adj List button ( ), or from another folder clicking Load an Adj List button ( ). When all the arguments are selected, the READY message (in green) appears. Click OK to execute the formula. •

MISSING ADJ S Let x and y be two cells contained in a neighbour list. If the relation Adj[ x ,y ] exists, but does not exist the relation Adj[y ,x ], then Adj[y ,x] is called Missing Neighbouring Relationship (Fig.10.21 ). This function extracts all the missing neighbouring relationships from a list. Clicking the Missing Adjs button the Formula window in Fig.10.23 is activated.

Fig.10.23 Enter the desired name for the resultant list in List Name (default name: MISSING ADJSn). Until there is no argument selected in List A, a NOT

READY warning (in red) is displayed in the bottom part of the Formula window. Arguments can be selected from Present Lists clicking Select an Adj List button (



SITE LONE A DJS It‘s applicable only to list element. Let x,y and z be cells of the same site. If the relations Adj[ x ,y ] and Adj[z ,x ] exists, but does not exist the relation Adj[y ,z ], then Adj[ x ,y ] and Adj[z ,x ] are called Site Lone Neighbour


248

248/480

5/24/2018


relationships (Fig.10.24 ). This function extracts all the site lone neighbour relationships from a list.

Cell x MISSING

LONE Adj[z,x]

Cell z

Adj[ x ,y]

Adj[y,z]

Cell y

Fig.10.24 Clicking the Site Lone Adjs button the Formula window in Fig.10.25 is activated.

Fig.10.25 Enter the desired name for the resultant list in List Name (default name: SITE ADJSn). Until there is no argument selected in List A, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Arguments can be selected from Present Lists clicking Select an Adj List button ( ), or from another folder clicking Load an Adj List button ( ). When all the arguments are selected, the READY message (in green) appears. Click OK to execute the formula.

•

SITE MISSING ADJ S


249

249/480

5/24/2018


Let x ,y and z be cells of the same site. If the relations Adj[ x ,y ] and Adj[z ,x ] exists, but does not exist the relation Adj[y ,z ], then Adj[y ,z ] is called Missing Site Neighbour Relationship (Fig.10.24 ). This function extracts all the site missing neighbour relationships from a list. Clicking is activated.the Site Missing Adjs button the Formula window in Fig.10.26

Fig.10.26 Enter the desired name for the resultant list in List Name (default name: MISSING SITE ADJSn). Until there is no argument selected in List A, a NOT warning (in red) is displayed in the bottom part of the Formula READY window. Arguments can be selected from Present Lists clicking Select an Adj List button (


( ). When all the arguments are selected, the READY message (in green) appears. Click OK to execute the formula.

•

FILTER Enables filtering by list properties. The available properties depend on list type. They are: Ø Ø

ADJACENT CELLS NUMBER: number of neighbours per cell; DISTANCE: distance (in meter) between two neighbouring cells; Ø GAP PERC: number of pixels compliant with gap criterion (set in the Adjacent menu in the Pixel Option Window); Ø THRESHOLD PERC: number of pixels compliant with threshold criterion (set in the Adjacent menu in the Pixel Option Window); Ø GAP & THRESHOLD PERC : number of pixels compliant with gap and threshold criteria (set in the Adjacent menu in the Pixel Option Window) at the same time. Clicking the Filter button, the Formula window in Fig.10.27 is activated.


250

250/480

5/24/2018


Fig.10.27 Enter the name of the filtered list in List Name (default name: PROPERTY FILTERn). Until there is no argument selected in the List A and no filtering criterion in Adj Property, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Arguments can be selected from Present Lists clicking Select an Adj List button (

), or from another folder clicking

Load an Adj List button ( ). Filtering criteria can be set in the form: [property] com parison operator [n] or [property] com parison operator [n*MEAN ] where n is an integer and MEAN is the property value averaged on whole list. The filter returns a list in which elements are in accordance with the chosen criterion. Click the first Adj Property field, as displayed in Fig.10.28 , and select the list property.

Fig.10.28 NONE means ‘no property’ and COUNT simply refers to ADJACENT CELLS NUMBER.


251

251/480

5/24/2018


Click the second field, as shown in Fig.10.29 , and select the comparison operator.

Fig.10.29 Enter an integer in the next field and NONE in the last one, as shown in , if you want to compare the property value with an integer. Fig.10.30

Fig.10.30 In the example of Fig . 10.30 the filter counts cell by cell the number of neighbouring cells and returns a list with only neighbour relationships of cells with more than 15 neighbours. Enter an integer in the third field and MEAN in the last one to compare the property value with a multiple of its mean value.

Fig.10.31 In the example in Fig.10.31 the filter returns a list with all the neighbour relationships between cells with mutual distance less than mean distance. After having chosen the argument and fixed the filtering criterion, the READY message (in green) appears. Click OK to apply the filter.

•

ORDER It allows list sorting in ascending/descending order based on the values of the selected property. Clicking the Order button the Formula window in Fig.10.32 is activated.


252

252/480

5/24/2018


Fig.10.32 Enter a name for the desired sorted list in the List Name (default name: PROPERTY SORTn). Until there is no argument selected in List A and no sorting criterion in Adj Property, a NOT READY warning (in red) is displayed in the bottom part of the Formula window. Arguments can be selected from Present Lists clicking Select an Adj List button ( clicking Load an Adj List button (

), or from another folder

).

Click the first Adj Property field, as in Fig.10.33 , and select the desired list property.

Fig.10.33 Click the last field, as in Fig.10.34 , and select the sorting criterion.

Fig.10.34 After having chosen the argument and fixed the sorting criterion, a READY message (in green) appears. Click OK to apply the function.

•

CELL SET FILTER


253

253/480

5/24/2018


SOURCE CELL SET FILTER To enable list filtering by Cell Set. These functions extract from a chosen list a new list containing only the neighbours of cells belonging to a specified cell set. Clicking the Cell Set Filter button the Formula window in Fig.10.35 is activated.

Fig.10.35 Enter the desired name for the filtered list in List Name (default name: CELLSET FILTERn). Until no arguments are selected in List A and Cell Set, a warning red)be is displayed in thePresent bottom part ofpressing the Formula NOT READY window. The list to filter(incan selected from Lists the Select an Adj List button ( List button (

), or from another folder clicking Load an Adj

). The cell set can be selected from Present Cell Sets

clicking Select a Cell Set button (

), or from another folder clicking Load a

Cell Set button ( ). When all arguments are selected, a READY message (in green) appears. Click OK to apply the function. There are two kind of Cell Set filter: it requires that both cells in the neighbour list must belong to the selected Cell Set. it requires that only the starting cell of the neighbour must belong to the selected Cell Set. •

COLOCATED ADJ CELL To enable list filtering by Colocated Cell Adj.


254

254/480

5/24/2018


These functions create a new list containing only the neighbours of cells from cell set A cell set B only for collocated cells. Clicking the Colocated Cell Adj button the Formula window in Fig.10.36 is activated.

Fig.10.36 •

COLOCA TED ADJ SITE To enable list filtering by Colocated Site Adj. These functions create a new list containing only the neighbours of cells from cell set A to cell set B intra-site only for collocated sites . Clicking the Colocated Site Adj button the Formula window in Fig.10.37 is activated.

Fig.10.37 •

COLOCATED A DJ COPY To enable list filtering by Colocated Copy Adj. These functions extract from a chosen present list A a new list containing only the neighbours of cells belonging to cell set A and copy those relationships to


255

255/480

5/24/2018


cell set only for collocated sites, the result is in present list CellsetB->CellsetA neighbours . Clicking the Colocated Copy Adj button the Formula window in Fig.10.38 is activated.

Fig.10.38

•

COLOCATED ADJ To enable list filtering by Colocated Adj. These functions extract from a chosen present list A a new list containing only the neighbors of cells belonging to cell set A and copy those relationships to cell set B only for collocated sites. The result is to copy the relations CellsetA<->CellsetA in present listA to CellsetB<->CellB for collocated sites. Clicking the Colocated Adj button the Formula window in Fig.10.39 is activated.

Fig.10.39


256

256/480

5/24/2018


10.5 Cell Sets The Present Cell Sets panel shows all available cell sets. The elements belonging to a set are cells (Fig.10.7 ). At the beginning AdA has loaded at least six sets (Fig.10.36 ): • the Global cell set, containing all the cells “viewed” by AdA since it has been

started, that can be also considered as the union of all the other sets appearing in the panel. • the ALL_ Network cell set, containing all the cells, UMTS and GSM, present in the Network loaded. • The GSM_ Network cell set, containing only the GSM cells present in the Network loaded. • The UMTS_ Network cell set, containing only the UMTS cells present in the Network loaded.

• The L1 UMTS_ Network cell set, containing only the UMTS cells present in

the Network loaded on layer1. • The L2 UMTS_ Network cell set, containing only the UMTS cells present in

the Network loaded on layer2. • The EXT_ Network cell set, containing all the cells measured during the data

acquisition campaign belonging to RNCs different from RNCs involved in the Network under investigation. • The OUTSERVICE_ Network cell set, containing all the cells declared “out of service” in the UMTS Network excel file with radio network planning information (see Appendix). For each set in brackets (see Fig. 10.40 ) is indicated the number of composing cells. Selecting one set S from the Present Cell Sets panel (the set will be highlighted in blue), in all related lists Ln in the Present Lists panel (i.e. lists containing neighbours of cells belonging to S) will be updated the N 1 /N 2 indication in brackets, where: N 1 = number of neighbours, present in the Ln list, related to all cells belonging to selected set S; N 2 = total of neighbours declared in the Ln list

Fig.10.40


257

257/480

5/24/2018


If a “pixel-based” processing of scanner collected data was previously done (Scanner >> Load as pixel , see Chapter 5), AdA is able to recognize the Scanner Detected Cells, Minimum Gap from Best Server and Maximum Gap from Best Server files (ScannerDetected.txt , Add.pxl and Remove.pxl ) saved by MUSA in the folder Projects\\Results\Adjacents. Theautomatically cell sets declared in these files will be loaded in the Present Cell Sets panel at the first start (Fig.10.37 ). In any case, it is possible to load them using the Load button ( ). Every time that a scanner measurements file is opened, automatically MUSA extracts the related Scanner Detected Cells List (ScannerDetected.txt) and saves it in the folder Projects\\Results\Adjacents. The first time you open AdA (or at every re-import) AdA is able to recognize the Scanner Detected cells file and the related Scanner Detected cell set will be loaded in the Present Cell Sets panel. Anyway, the Scanner Detected Cells List (ScannerDetected.txt ) stored in the folder Projects\\Results\Adjacents is related to the last scanner measurements file opened in MUSA. To be confident of the measurements file version imported AdA, re-open it before window and pressthe thelast reimport button. Thein ScannerDetected.txt filestarting will bethe updated considering scanner measurements file loaded.

Fig.10.41 On the right side of the Present Cell Sets panel there are the following functional buttons:

•

Load , to load Scanner Detected Cells Set if not in the folder Projects\\Results\Adjacents. It’s possible to use this button also to load other user defined cell set (a cell set file is a simple list of cells saved in a text file format).

•

Save , to save a cell set selected in the Present Cell Sets panel.

•

R e n a me, to rename a cell set selected in the Present Cell Sets panel.


258

258/480

5/24/2018


•

•

, to delete a cell set selected in the Present Cell Sets panel. Delete

Fo r mu la , to execute formulas on cell sets selected in the Present Cell Sets panel (see 10.6).

10.6 Present Cell Sets Panel Form ulas Clicking the Formula button, the Select a Formula window appears (Fig.10.38 ). There are no built in formulas for cell sets. Only new cell sets formulas implemented by the user will appear. The resultant cell set will be displayed in Present Cell Sets panel.

Fig.10.38 Using the following elementary functions the user could implement new formulas on cell sets: •

UNION Let A and B be two cell sets, (A U B) returns all and only the cells belonging to A or to B. From a logical point of view, it acts as an OR function. Clicking the Union button the Formula window in Fig.10.39 is activated.


259

259/480

5/24/2018


Fig.10.39 Enter the desired name for the resultant cell set in Cell Set Name (default name: UNIONn). Until no arguments are selected in Cell Set A and Cell Set B, a NOT READY warning (in red) will be displayed in the bottom part of the Formula window. Formula arguments can be selected from Present Cell Sets clicking Select a Cell Set button (

), or from another folder clicking Load a

). When all arguments are selected, a READY message Cell Set button ( (in green) appears. Click OK to execute the formula.

•

INTERSECTION Let A and B be two cell sets, ( A n B) returns the cells common to A and B. From a logical point of view, it acts as an AND function. Clicking the Intersection button the Formula window in Fig.10.40 is activated.

Fig.10.40


260

260/480

5/24/2018


Enter the desired name for the resultant cell set in Cell Set Name (default name: INTERSECTIONn). Until no arguments are selected in Cell Set A and Cell Set B, a NOT READY warning (in red) will be displayed in the bottom part of the Formula window. Formula arguments can be selected from Present Cell Sets clicking Select a Cell Set button (

), or from another

folder clicking Load a Cell Set button ( ). When all arguments are selected, a READY message (in green) appears. Click OK to execute the formula. •

DIFFERENCE Let A and B be two cell sets, (A - B) returns the cells belonging to A but not belonging to B. Note that the difference function does not benefit of the commutative property, that means ( A - B) ≠ (B - A). Clicking the Difference button the Formula window in Fig.10.41 is activated.

Fig.10.41 Enter the desired name for the resultant cell set in Cell Set Name (default name: DIFFERENCEn). Until no arguments are selected in Cell Set A and Cell Set B, a NOT READY warning (in red) will be displayed in the bottom part of the Formula window. Formula arguments can be selected from Present Cell Sets clicking Select a Cell Set button (

), or from another

folder clicking Load a Cell Set button ( ). When all arguments are selected, a READY message (in green) appears. Click OK to execute the formula. •

CEL L SET FROM LIST CELL SET FROM SOURCE CELL LIST

This functions create a new cell set containing cells involved in the neighbour relationships present in a specified list. Clicking the Cell Set from List button the Formula window in Fig.10.42 is activated.


261

261/480

5/24/2018


Fig.10.42 Enter the desired name for the resultant cell set in Cell Set Name (default name: FROMADJLISTn). Until there is no argument selected in List A, a NOT READY warning (in red) will be displayed in the bottom part of the Formula window. The source list can be selected from Present Lists clicking Select an Adj List button (

), or from another folder clicking Load an Adj List button (

). After having chosen the argument, a READY message (in green) appears. Click OK to execute the formula. There are two kind of operation: for each neighbour of the list, it creates a Cell Set made of both cells of a neighbour (the starting and the ending one). for each neighbour of the list, it creates a Cell Set made of only the starting cell of the neighbour. •

CO-LOCATED

These functions create a new cell set containing cells that are collocated from CellsetA to CellsetB within the distance for Site co-location. Clicking the Collocated button the Formula window in Fig.10.43 is activated.


262

262/480

5/24/2018


Fig.10.43

10.7 Display panel The Display panel represents the core of AdA graphic environment (Fig.10.44 ). On this panel it is possible to add and remove neighbour relationships from a list.

Fig.10.44


263

263/480

5/24/2018


On the top of the Display panel there are the following functional buttons:

•

Zoom In , to increase the scale of the displayed area to focus the attention on a specific zone.

•

Z o o m O u t , to decrease the scale of the displayed area in order to have a larger view.

•

Mous e Wheel Zoom , to enable Zoom In and Zoom Out functions using the mouse wheel.

•

•

•

Z o o m m o d e , to perform Zoom In function on a selected area.

Pan mo d e , to move the viewing window up, down or sideways in order to display areas which lie outside the viewing window.

area.

Show/Hide Grid , to make visible or to hide the grid on the displayed

•

Show/Hide Measurements , to make visible or to hide the route where measurements have been collected (Fig.10.44 ). This operation is possible if the scanner measurements file is currently opened in MUSA. If the Show/Hide Measurements button is disabled open first the scanner measurements file of interest in MUSA ( Measurement\Open… from the main menu).

•

, to calculate distances (in meters) between two points on the Distance map. With the first mouse click the user establishes the reference point; moving around the mouse pointer, a label will show the distance of the current point from the reference one.


264

264/480

5/24/2018


Fig.10.44

In the Present Layers panel (Fig.10.45 ) will be added the new Measurements layer. Clicking the Measurements Draw Settings button (Fig.10.46 ) it is possible to change the style of the symbol used to draw the route.

Fig.10.45


265

265/480

5/24/2018


Fig.10.46 •

Maps , to make visible or hide a geographic map of the Show/Hide displayed area (Fig.10.47 ) if available in the folder: \Projects\\Environment\Maps. To show the map load the related index file (see Appendix).

Fig.10.47


266

266/480

5/24/2018


•

Show /Hide Heights , to make visible or to hide heights profile of the displayed area (Fig.10.48 ), if available in the folder: \Projects\\Environment\Heights.

Fig.10.48

•

, to make a cell “active” (i.e. to be the current cell) simply Select Cell clicking on the cell itself (when the pointer becomes a ‘+’).

•

Add Adjs , to enable the addition of the displayed neighbour relationships with a left click from the current cell and the selected one (when the pointer becomes a ‘+’).

•

D r o p Ad js , to enable the removal of the displayed neighbour relationships with a right click from the current cell and the selected one (when the pointer becomes a ‘+’).


267

267/480

5/24/2018


•

Ad d /D r o p Ad js , to enable addition/removal of a neighbour relationship clicking the left/right key of the mouse when the pointer becomes a ‘+’ on the cell adjacent to active one.

•

Add /Drop Ad js without reciprocal , to enable addition/removal of a neighbour relationship without reciprocal.

•

Add/Drop Adjs with reciprocal , to enable addition/removal of a neighbour relationship with reciprocal.

•

” list , to save the current list included all Back up a Copy of ”TO EDIT added/removed neighbor relationships, giving it a new name. The list saved will appear in the Present Lists panel.

•

” list , to save the current list Bac ku p a Cop y o f ”Selected Cell included all added/removed neighbor relationships, giving it a new name, for the selected cell. The list saved will appear in the Present Lists panel.

• • •

Save a Bitm ap , to save the current view as a bitmap image in a file. Auto matic Bitm aps Generation , to create in batch mode bitmaps showing cells and the corresponding neighbours. It works for each cell contained in the current navigation cell set. This button could be hide depending on the screen resolution: please enlarge the display panel in order to show it.

For each cell selected, is possible to have the SIB11 information displayed in the following picture:


268

268/480

5/24/2018


Fig . 10.49

10.8 Layers and nav igation f eatures In the Present Layers panel it is possible to find the functions allowing the creation of the layers on the Display panel. When AdA is started no layer is present ( Fig.10.50 ).


269

269/480

5/24/2018


Fig . 10.50 On the left side of the Present Layers panel there are the following functional buttons: •

Select “To Edit” Lis t , to display the neighbour list to be edited. This is the list to be updated with neighbour relationships addition/removal. It is possible to select one of the Present Lists. The typical “To Edit” list for the standard neighbour list optimization process is the Network list. The selected list will appear in the Present Layers panel (Fig.10.50 ) and all the cells involved will appear in the Display panel (Fig.10.51 )

Fig.10.50


270

270/480

5/24/2018


Fig . 10.51 Cells and neighbours declared in the list “TO EDIT” are displayed in blue by default. It is always possible to change visualization properties clicking Cell and/or Adj Draw settings . Make the desired Draw settings changes in the two windows in Fig.10.52 and Fig.10.53. The “active” cell, i.e. the current cell under investigation on the Display panel, is highlighted in yellow. In the bottom part of the Display panel are listed some information about the active cell, such as the total number of neighbours and the neighbour list. For each neighbouring cell are reported the values of related properties (distance, gap perc., threshold perc., gap & threshold perc., if present in the list).


271

271/480

5/24/2018


Fig.10.52

Fig.10.53

In the Draw settings above, is possible to draw the neighbors relationships based on the different target layer. •

Select “To Add” List , to display the list of neighbours to be potentially added. It is possible to select one of the Present Lists. The typical “To Add” list in the standard neighbour list optimization process is the list resulting from the ADD LIST TO BE VERIFIED formula application, that is the list of neighbours that could be added. The selected list will appear in the Present Layers panel (Fig.10.54 ).

Fig.10.54 Neighbour relationships to add are displayed in red by default ( Fig.10.55 ). It is always possible to change visualization properties as explained above.


272

272/480

5/24/2018


Fig.10.55 •

, to display the list of neighbours to be Select “To Remo ve” List potentially removed. It is possible to select one of the Present Lists. The typical “To Remove” list in the standard neighbour list optimization process is the list resulting from the REMOVE LIST TO BE VERIFIED formula application, that is the list of neighbours that could be removed. The selected list will appear in the Present Layers panel (Fig.10.56 ).

Fig.10.56


273

273/480

5/24/2018


Neighbour relationships to remove are displayed in green by default (Fig.10.57 ). It is always possible to change the visualization properties as explained above.

Fig.10.57 •

Select a L ist , to display neighbour relationships declared in a list selected from the Present Lists panel.

•

Select a Cell Set , to display cells belonging to a cell set selected from the Present Cell Sets panel.

•

Remove Layer , to delete a layer selected from the Present Layers panel.

•

, to move up a layer selected from the Present Layers panel, Move Up changing the layers order. The selected order has influence on visualization of layers in the Display panel.


274

274/480

5/24/2018


•

Move Down , to move down a layer selected from the Present Layers panel, changing the layers order. The selected order has influence on visualization of layers in the Display panel.

Note that, after the processing of data collected on the current radio conditions of the network, AdA only suggests additions/removals of neighbour relationships. If user decides that a neighbour addition has to be confirmed, left click on the final cell of the neighbour under investigation while Ad d /D ro p A d js button is active. The red line representing that relationship becomes blue: this relationship will enter in the Network neighbour list. If user decides that a neighbour removal has to be confirmed right click on the final cell of the neighbour under investigation, while Ad d /Dr o p A d js button is active. The green line representing that relationship vanishes: this relationship will be removed from the Network neighbour list. By this graphic procedure a new Network neighbour list comes out. When all the additions and removals are performed, to save the obtained Network list click Backup a Copy of “To Edit” list button ( ), giving a new name to the new Verified Network List (“verified” means: all the added and removed neighbours have been checked and eventually confirmed). Just created Network list will appear in the Present Lists panel. Neighbour relationships neither added nor removed are not altered and remains unchanged in the new Network list. When the on-map graphic analysis of the neighbour relationships is terminated, the Verified Network List should be “closed” (see FINAL NETWORK function). The list, verified closed, will be the Final Network , that is the final result of theNetwork whole neighbour listand optimization. The Navigation panel, reported in Fig.10.58 , allows the “navigation” through displayed cells. In other words, if list A is the “To Edit” list and list/cell set B is the list/cell set selected in the Navigation panel, then all the cells belonging to the list A will be displayed on the Display panel, but only the cells present in B will be “visited” during the optimization phase (neighbours addition/removal).

Fig.10.58

It is possible to select a list from the Present Lists ( Select Adj L ist button) or a cell set from the Present Cell Sets (Select Cell Set button) as the navigation cell set. Typically, in the standard neighbour list optimization process the cells to visit are the Scanner Detected ones (Fig.10.59 ).


275

275/480

5/24/2018


Fig.10.59

In the Navigation Panel there are different options:

•

Next Cell , to move to the next cell of the selected list.

•

Prev Cell , to move to previous cell of the selected list.

•

Navigation slider, to do quick movements between cells.

•

Activ e Cell indicator , to show the active cell, i.e. the current cell under investigation. This cell is yellow highlighted on the Display panel. In this drop down menu it is possible to select directly a cell from the list/cell set chosen for navigation (Fig.10.60 ).

Fig.10.60

•

Center on Ac tive Cell , in order to center the displayed area on the active cell.

10.9 Neighbo urs Numb er and SIB11 Monitoring The Exceeding Cells panel (Fig.10.61 ) makes possible the monitoring of cells with a number of neighbours exceeding a user-fixed number (default = 20). This maximum value could come out from a specific customer requirement or from the System capacity.


276

276/480

5/24/2018


Fig.10.61 Insert the maximum number of adjacent cells allowed in Adj Count and press Enter Key to view all cells that exceed that value. A possible result is shown in Fig.10.62 :

Fig.10.62 Selecting

Backu p a Copy of Exceeding Cell Set , it is possible to create in the Present Cell Sets panel a new cell set containing all the cells listed in Exceeding Cells panel (i.e. all the cells exceeding the number entered in Adj Count). In the Fig.10.63, it is possible to select/create/delete worksheets in order to monitor the cell that exceeds the SIB11 threshold with and without HCS. In fact is possible to select the layer to monitor (e.g. UMTS Layer 1, UMTS Layer 2) and the result is listed below.


277

277/480

5/24/2018


Fig.10.63

10.10 Form ulas Manag emen t Neighbours Analyzer provides some functions for formulas management. Clicking button on AdA main toolbar ( Fig.10.6 ), the Formulas window Formu la Manager appears (Fig.10.63 ). In the Formulas window are listed all the AdA built in formulas, separated in Present List Formulas and Cell Set Formulas. In the Present List Formulas section there are the formulas explained in section 10.4. In the Present Cell Set Formulas section there are no formulas, because there are no built in formulas in AdA for cell sets. In this section will appear only user-made formulas. All the data related to AdA built in formulas are stored in a file with a proprietor format called AdA Formulas File (formulas.aff ).

Fig.10.63 MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

278

278/480

5/24/2018


On the right side of the Formulas window there are the following functional buttons:

•

Load , to load an AdA Formula File (.aff ).

•

Save , to save an AdA Formula File ( .aff ), i.e. after a formula creation/deletion.

•

R e n a me, to rename a formula selected from Present List Formulas.

•

Delete , to delete a formula selected from Present List Formulas. The formula will be deleted permanently.

•

Select an Adj Lis t , to extract from a list the formula used to obtain it in order to customize the formula itself.

•

Select a Cell Set , to extract from a cell set the formula used to obtain it in order to customize the formula itself.


279

279/480

5/24/2018


11. STATIC LOAD SIMULATION MUSA offers the possibility to simulate the influence of a static load change in the network in term of quality. As described before, the results that MUSA shows affect only the measurements loaded and only the portion in which at least one sample for the modified cell is found. No predictions are available.

11.1 Using Lo ad Simulation Option s To access the Load Options it is necessary firstly to open the Optimization Parameters Table reported in Fig . 11.1 . Please refer to chapter 8 for the open procedure description.

Fig . 11.1 Once the table is available it is possible to load a scanner measurement file selecting in the main menu Measurement\Open :


280

280/480

5/24/2018


When loading operations are terminated, in the Coverage Optimization window ( F ig . 10 .1 ) all function buttons are active. To have an idea of how an increment in network traffic modifies the quality of the network itself, it is possible to change the parameter Traffic_Pwr (see Chapter 8 to know how to modify a parameter in the table) to set an extra amount of power on dedicated channel and then observe simulation results. Selecting the button

(Network Load ) the following dialog box will be displayed:

Here it is allowed to edit a percentage of Traffic_Pwr that will be applied in one step on every cell in the Optimization Parameters table. Fig. 11.2 and Fig. 11.3 show how an increment of 35% in Traffic_Pwr affects the Best Server Ec/Io (EcIo_1) in the network used as example.


281

281/480

5/24/2018


Fig . 11.2

Fig . 11.3 A modification of the Control_Pwr parameter will change the estimated average CPICH power percentage assigned to control channels. MUSA can simulate the effect that a change of this parameter produces on measurements. If it is known the amount of average power on control channels during the measurement campaign, it is possible to set this value modifying the default Control_Pwr parameter. To set the default Control_Pwr value select in the main menu Options\Sum of Channel Offset…


282

282/480

5/24/2018


This option is available only if the Optimization tool is not active. The following dialog box will be displayed

This value represents the sum of all the control channel CPICH power offsets declared in RNC O&M parameter database, averaged on time usage basis. It has influence on the algorithm used to recalculate the Scanner measured parameters. A change of this value supposes the knowledge of how to estimate the amount of power expected on the control channels. Next table reports an example of which contributes could be considered in the sum of control channel CPICH offsets for a network with a negligible load:

Channel P-SCH S-SCH BCH (P-CCPCH)

Offset (dB) -2 dB -2 dB -3 dB

Offset (Numeric) 0.6310 0.6310 0.5012

Time Usage 10% 10% 90%

Value contributes 0.0631 0.0631 0.4511

The final result is a value of 0.577 from which is derived the default value of 0.5 used by MUSA. In a network with a certain percentage of traffic load the situation presented in the next table could be considered as more realistic:

Physical Channel CPICH

Transport Channel -

Weight

Remark

-

Common Pilot Channel

P_SCH

-

0.1

S_SCH

-

0.1

P-CCPCH

BCH

0.9

Primary Synchronization Channel Secondary Synchronization Channel Broadcast Channel


283

283/480

5/24/2018


S-CCPCH S-CCPCH PICH

PCH FACH -

0.5 0.5 1

Paging Channel Forward Access Channel Paging Indicator Channel

11.2 Exceeding Max Pow er When modifications of the Traffic_Pwr or Control_Pwr parameter overtake the maximum cell power (reported in the P_Max column of the Optimization Parameter table) MUSA displays the Warning message shown in Fig . 11.4 .

Fig . 11.4

11.3 RSSI Analysis RSSI Analysis is a useful tool to better understand the impact of load simulation changes, or to find the heavy loaded cells. In the main menu select View \RSSI Analysis to open RSSI Analysis tool window (available if a Scanner measurement file is loaded).

The window shown in Fig . 11.5 will appear.


284

284/480

5/24/2018


Fig . 11.5 If you use the zoom buttons, you can also push the (Re-calc Legend) button to re-calculate the legend thus showing only the samples colors in the time interval displayed just like in Fig . 11.6.


285

285/480

5/24/2018


With the option (Insert Title ) it is possible to give to the graph a title editing it in the dialog box of Fig.11.7 .

Fig . 11.7

d Fig u the r e) button Click (Ad the area a user made figure. Whenon thethe button is selected windowtoofdraw Fig. on 11 .8 is chart displayed:

Fig . 11.8 User may choose between three options: • Lines • Circle • Text

Once predefined item and the desired layout are selected press

button.

With a left click it is possible to draw the selected item. Press to go back to . Fig. 11.5 When the Text option is chosen the dialog box of Fig . 11.8 becomes active to edit the desired text. It is possible to paste it on the chart with a left click. To remove all the figure drawn on the graph area select button.

(Clear All Figures )

Through the Noise factor you can increment or decrement the Noise Factor used by MUSA to estimate the Thermal Noise part of the RSSI (F x kT x B). Please set this parameter according your instrument specification.


286

286/480

5/24/2018


When the (Window Synchronization) button is selected all the opened windows in MUSA are synchronized. So if any time instant is selected in one window then user will find it highlighted in any other opened window with a specific time pointer/marker. In the RSSI Analysis window the time pointer is a black vertical line plotted on the selected series with a label reporting the corresponding time instant as shown in Fig.11.6 . The user could define a desired time instant in the RSSI Analysis window with a left click on a plotted series but only if windows synchronization is enabled. To move the time position use (Move Left ) or (Move Right ) buttons. When a time position line is visible, clicking on the chart, the Pie Chart on the right shows the RSSI composition for that time position. Selecting (Save as B itmap ) button it is possible to save the Area and the Pie graph (if visible) in two Bitmap files. Click on the

(Autozoom ) button to set Autozoom On or Off. Push the

(Zo o m in ) button to increment zoom or the zoom in the graph area. To move graph area press the move to the right.

(Z o o m o u t ) button to decrement

button to move to the left or the

button to

Press the Erase current p osition button to remove time position line on the graph area. Also the Pie Chart showing the RSSI for that time position will be removed. To close RSSI Analysis tool window push the


(Close ) button.

287

287/480

5/24/2018


12. ALGORITHM SIMULATIONS

12.1 Introd uc tion 12.1.1 Simulated Algorithms MUSA offers the Algorithm Simulations function to estimate the behaviour of Mobile Equipment in the UMTS network. Simulations can help to analyze the effect of a parameter change and provide possibilities to optimize the network. Algorithm Simulations are based on the UMTS and GSM measurements TS 25.331, 3GPPscanner TS 25.922, and 3GPPand TS comply with 3GPP specifications ( 3GPP 25.304 documents). The user can analyze measurements and algorithm indications to highlight network parameter problems and can also optimize network using an iterative procedure. Currently, MUSA can handle the following algorithms: • Soft Handover • Inter System Handover • Cell Selections and Reselection

12.1.1.1 Soft Handover (SHO) This simulator essentially determines the composition of the Active Set, based on the specified parameters that are generally on RNC and Cell basis (there are important exception such as the Cell Individual Offset (CIO) that is defined on Neighbour basis). The user can evaluate the number of cells in Active Set Active ( Set Size indicator) and its composition (Cell identity, RSCP and Ec/Io). The simulator also builds a further series of Indicators that help in the handover analysis, like the number of Event 1A and 1B (counted on Neighbour basis), the difference between the level of the Best Server cell (RSCP or Ec/Io) and the new added cell in Active Set, and so on.

12.1.1.2 Inter System Handover (ISHO) This simulation is an extension of the previous SHO simulator, and is useful when the Best Server measurements are available for the GSM system. In this case ISHO simulation supplies further indications that allow the study and optimization of the interaction between UMTS and GSM. An example of a useful indicators is the Status indicator, reporting one of the following condition: • • • •

Network Searching (at the beginning of simulation) UMTS GSM Compressed Mode (divided in two sub conditions, depending on the availability of one sufficient GSM cell)


288

288/480

5/24/2018


• No network

There are also other indicators, that provide an estimation of the 2D and 3A events, with their corresponding measured values.

12.1.1.3 Cell Selection and Reselection(CSRS) Purpose of this simulated algorithm is the determination of the Camped Cell. Other indicators are also supplied to help in the selection and reselection tuning process, like the differences between RSCP and Ec/Io levels at the reselection time, or the Status indicator (GSM, UMTS, No Network, Network Searching).

12.1.2 The Scene Concept In MUSA the simulations are carried out inside a “scene”. The user can create as many scenes as he wants therefore many simulations can be performed at the same time. A scene is composed of the following four elements: • Measurements: the scanner file of UMTS measurements (if necessary

combined with the GSM measurements) • Simulators: algorithms which are enabled to work and all their parameters:

they define the operation mode, or the chosen approximation degree. • Network parameters: the parameter configuration on RNC, Cell or Neighbour

based, that are used by the algorithms. • An optional Neighbours List to replace the original one imported by MUSA.

The optional Neighbours list must be an export file obtained from AdA module. The user can freely create and edit as many scenes as he wants. As a first step, it is logical to define a special scene, which is a basic scene, without any alterations in the network configuration. Such a scene, called the “Original Scene” of the project, supplies a photograph of the situation: its indicators could be used as comparison elements for all other indicators generated by subsequent scenes. In this way it is possible to create and change parameters, searching for a particular configuration that allows the optimization of network performance. This approach is also used in this manual to explain the simulation features.

12.2 Measurements used in s imu lations 12.2.1 Measurements setup In order to obtain good simulation results, it is important to acquire measurements using the following basic rules:


289

289/480

5/24/2018


• measurements should be collected using the shortest time period (avoid any

kind of averaging or post-processing). • Start each acquisition close to the previous collected file. Each Simulator

resets itself if it detects a distance of 250 meters between subsequent measurements.

• For the UMTS scanner acquisition an external antenna located on the roof of

the car should be used (if possible). For the acquisition of the GSM measurements (using terminals connected to the TEMS or NEMO tracer), the antenna should be located in the same conditions of the UMTS antenna (on the roof of the car). If with the acquisition set it is not possible to obtain equivalent conditions between the two antennas, MUSA allows the introduction of an offset to be added to the RxLevel, balancing the different radio environments. This feature is also useful to simulate algorithms in special situations (in-car, indoor). The first operation that a user must execute before any scene simulation is indicated as data queuing: many collected files must be combined to build a single continuous file, as described below. It is possible to queue only UMTS files or UMTS-GSM merged files.

12.2.1.1 Data queuing for a UMTS simulation To access this function, please select Scanner->Queue Scanner… from the MUSA main menu, as shown in the following figure:


290

290/480

5/24/2018


The standard Browse dialog window appears asking the user to select the folder containing the UMTS scanner measurement files, as shown in following figure:

By default MUSA highlights the current project Scanner Measurement directory. After the user choice, the Queue scanner files window will be shown:

The first step is to choose the measurement files type, clicking one of the supported instrument in the File Type panel. The Available Files section will be updated in order to show the full list of the available files for the selected type. Pressing the (Select A ll files ) button it is possible to select all files present in the folder listed in the Available Files list. Pressing the following


291

291/480

5/24/2018


(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. Two combining process are provided in the Mode panel: As Offset and File Date-Time . If the user wants to queue files for the algorithm simulations only the As Offset option is useful (as shown in the previous figure). In this way the resulting file will be created starting from 00:00:00.000 time without time gaps. It is important to remember that any simulator resets itself if the time between subsequent measurements is greater than two seconds. The As Offset option avoids any time gap, providing a more continuous simulation. Since simulators reset itself also for distance gap of 250 meters, the user has to take care of selecting the files in the correct order, avoiding as much as possible any route interruptions. On the contrary, the File Date-Time option preserves time (and date) for each measurement point, so it is useful to combining scanner files for the merge with Mobile traces. 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 (please see later). Other available control buttons: (Unselect All Files ) helps the user to eliminate all selected files, clearing the Selected Files section. (Uns elect Files ) eliminates the highlighted file in the Selected Files section. (Mov e Up, and Mo ve D o w n ). These buttons are useful to easily move the highlighted file in the Selected Files section. After a movement the Time-Date field might be modified (see later).


292

292/480

5/24/2018


In the File Date-Time combining it is mandatory to get a chronologically sorted list. 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) producing 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. The following figure shows the result of this operation (please compare this figure with the previous one):


293

293/480

5/24/2018


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


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.


294

294/480

5/24/2018


Pressing the button, the standard file dialog “Locate target file” will be opened, showing by default the Scanner folder of the current project:

Here, the user can specify the destination filename of the combined file. Pressing the Queue button, the combining process will start. After few seconds, at the end of the process, MUSA will show the following window:

The saved file (Solaria_total.sgf in this example) can now be used by every scenes with the Algorithm Simulations function.

12.2.1.2 Data queuing for a UMTS+GSM simulation To access this function, please select Scanner->Queue Scanner (UMTS+GSM)… from the MUSA main menu, as shown in the following figure:


295

295/480

5/24/2018


The standard Browse dialog appears asking the user to select the folder containing the UMTS scanner measurement files, as shown in following figure:

By default MUSA highlights the current project Scanner Measurement directory. After the user choice, an other standard Browse dialog appears asking the user to select the folder containing the GSM measurement files, as shown in the following figure (by default MUSA highlights the current project GSM measurement directory):


296

296/480

5/24/2018


After the selection the Queue scanner files window will be shown:

This window is an extension of the one described in the previous paragraph. In the UMTS File Type and GSM File Type sections the user has to specify the instrument employed to collect measurement data. The UMTS Available files and GSM Available files will be updated, listing all the available files (see previous figure).

These control buttons and work exactly as described in the previous paragraph, and can be used to select or move files in the Selected Files sections but before pressing


297

297/480

5/24/2018


or buttons the user has to highlight two items, one in the UMTS Available Files section, the other in the GSM Available Files section.

Two combining process are provided in the Combining Mode panel: As Offset and File Date -T i m e. If the user wants to queue files for the algorithm simulations only the As Offset option is useful (as shown in the previous figure). In this way the resulting file will be created starting from 00:00:00.000 time without time gaps. It is important to remember that any simulator resets itself if the time between subsequent measurements is greater than two seconds. The As Offset option avoids any time gap, providing a more continuous simulation. Since simulators reset itself also for distance gap of 250 meters, the user has to take care of select the files in the correct order, avoiding as much as possible any route interruptions.

On the contrary, the File Date-Time option preserves time (and date) for each measurement point, so it is useful to combine scanner files for the merge with Mobile traces. 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 (as shown in the following figure):

A quick way to adjust time information involves the use of the button (for details please see previous paragraph) and results in this case are shown in the next figure:


298

298/480

5/24/2018


Alternatively the user can press the highlighted file.

button to manually adjust the

Other available buttons:

to sort the Selected Files list by UMTS filename

to sort the Selected Files list by GSM filename to sort the Selected Files list by Time-Date field Consider that the Selected Files list must be chronologically sorted in File Date-Time mode. Do not care about it in the As Offset mode. To correct GSM measurement, in case of different positioning between UMTS and GSM antennas or to simulate other environment conditions (such as in-car or indoor), it is possible to add an offset to the RxLevel, by specifying a value in the GSM Offset section on the Queue scanner files window, as in the following figure:

Pressing the

button, the standard file dialog “Locate target file” will be shown,

by default in the Scanner folder of the current project:


299

299/480

5/24/2018


Here, the user can specify the destination filename of the combined file. Pressing the Queue button, the combining process will start. After few seconds, at the end of the operation, MUSA will show the following window:

The saved file (Solaria_total.sgf in this example) can now be used by every scenes with the Algorithm Simulations function.

12.3 SIM Mod ule From the MUSA main toolbar, press the button to start the Algorithm Simulations function: a new window, named SIM , will be shown. Moreover on the right part of the screen a new panel will appear with many new graphical buttons (described later):


300

300/480

5/24/2018


The SIM window is a sort of scene manager that permits to create, rename, delete, load and simulate one or more scenes.

12.3.1 SIM Commands The SIM window contains the following functional buttons:

(Add Scene ): it permits the creation of a new scene in the current project (Copy Scene ): it permits cloning the highlighted scene, obtaining a new scene with all the same settings of the starting one. (Delete Scene ): it permits erasing the highlighted scene in the current project. (Rename Scene ): it permits renaming the selected scene. (Load Scene ): after a measurement file has been specified for the current scene, this button permits loading it. All the scenes connected to the same measurement file share the same memory space. For that reason the user has to wait the loading only for the first scene, while the measurement file is instantaneously loaded for the others. (Save & Close Scene ): it permits saving and unloading the selected scene, discarding all simulated results. (Simulation Ready ): it enables scene simulation (and switches the scene to the read-only state).


301

301/480

5/24/2018


(Run Simulation ): it starts simulation for all enabled scenes (see previous command button) ( S top Simulation ): it stops the running simulation. ( E xp o r t Ad j L ist ): it permits the transfer of adjacent lists coming from neighbours based indicators to the ADA module. Example of usable adjacent lists generated by simulations are SHO_Add , SHO_Drop, SHO_Replace, ISHO_3A, CSRS_Reselection.

12.3.2 Scene creation

Press the (Add Scene ) button on the SIM window. The Scene Name dialog box will ask the user for the scene name:

As first scene, it is common to specify a name like Scene_Original , or Scene_0 , etc. This first scene, in our intention, will be used as reference for all other scenes in the project. For that reason, no changes will be applied to the network configuration. After the scene name specification press OK. A new scene will appear in SIM window, in the Present Scenes section, as shown in the following figure:

After the scene creation, it is necessary to specify a measurement file: it will be a combined “.sgf” file, obtained with the UMTS or UMTS+GSM queue process (see

12.2.1.1 and 12.2.1.2 sections). Press the Browse… button in the Measurements section and the Select a Measurement File dialog will be shown: MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

302

302/480

5/24/2018


Select the combined “.sgf” file and then press the measurement file in the “Scene_Original” scene, as shown:

button to load the

Before the effective measurement loading, it is possible to define a polygon to cut points outside the interested area. See Chapter 5.6.1 for details. To enable this function for the Algorithm Simulation select Measurements\Polygon Cutting


303

303/480

5/24/2018


It also possible to define a maximum number of servers (especially to save memory), selecting:

At the end of the loading process the (Simulation Ready ) button can be pressed to enable the scene for the simulation. The Scene_Original status becomes waiting , as shown in the following figure:

Selecting the (Run Simulation ) button, the Scene_Original simulation will begin, as displayed in the following picture:


304

304/480

5/24/2018


When the simulation has finished, the Indicators Calculation will begin, as shown in this image:

The following picture shows the Ready status of the Scene_Original in the Present Scenes, at the end of the process:

Remembering that first scene has the original parameters configuration, to proceed with the optimization it is necessary to create a copy of the Scene_Original. From the SIM toolbar, select the (Copy Scene ) button. A new name can be inserted for the new scene (Scene_1 in this example ).

This new scene (Scene_1), identical to the original, is added in the Present Scenes section in order to be modified and then to operate a new simulation, as highlighted in the following picture:


305

305/480

5/24/2018


In order to change the Scene_1 parameters, the (Simulation Ready ) button should be unselected; the following Confirm window will appear:

After confirming, with the

(Load Scene ) button is possible to load measurement

file in the Scene_1, as shown in the following picture:

It is possible to apply changes to the following parameters categories: • Algorithm parameters (divided by simulator, Cell Selection and Reselection,

Soft Handover and Inter System handover ) • Network parameters.

The first kind of changes allows to establish the approximation degree used by simulators (for example simulators have to use neighbour relationships or to redefine them). In order to study how to improve the network performances, it is instead possible to apply the second kind of changes (for example the Event 1A Time-to-trigger parameter to speed up the addition of a cell in the SHO algorithm).

12.3.3 Algorithm changes in a scene As first step, select Scene_1 in the SIM window, then expand the tree structure present in the Algorithms central section, selecting the Soft Handover (SHO) item.


306

306/480

5/24/2018


The specific available SHO parameters will appear. For example, now it is possible to change the RNC Elaboration Delay 1A, that is the estimated delay between Measurement Report message sent by UE and the Active Set Update message transmitted by RNC. In the right panel, the user can insert a new value (500 ms in this that becomes red after the is pressed, to highlight that this new example) value is different from the original one.OK At button this point the situation will be similar to the following figure:

Press the

button to enable the modified scene for the simulation, then press

button to proceed.

At the end of the simulation, it will be possible to graphically analyze, in many different ways, the resulting indicators. It will be also possible to compare indicators between both scenes, using the first one as reference to calculate improvements. These topics will be deeply described in the next paragraph. Here, a sample of graphical analysis will be presented to conclude this section.


307

307/480

5/24/2018


Select the ( Indicator Distribution ) button in the Views section of the right screen panel (see the next figure). A new window, named Indicator Distribution 1, will be shown. In the Modes section, also present in the right panel, press the

(New

Route ) button. In the Indicators section press the (Add Indicator ) button, then from the popup menus choose the following options in this order: Scene_Original -> SHO -> SHO_AS_Size:

Press the

(Pie Distribution ) button on the Indicator Distribution 1 window, then

the (Edit Title ) button to insert a new title (AS_Size_Scene_Original in this example):


308

308/480

5/24/2018


Repeat the previous steps for the Scene_1, opening the new Indicator Distribution 2 window, and obviously specifying a different title (Scene_1 SHO_AS_Size)

At end, the resulting Active Set Size between the original scene and thethe modified one (with 500 ms RNC delaycomparison for 1A event ) will appear like the following figure:


309

309/480

5/24/2018


Here a short description of all the available CSRS algorithm parameters is provided:

CSRS simulator OnOff

Neighbours Redefinition

MaxPowerUE BSC Qsearch Mode BSC Qsearch BSC FDD_Qoffset BSC FDD_Qmin_Eff

To switch on/off the simulator If set to No the simulator uses the neighbour relation as defined in the imported network. If set to Yes the simulator will consider each cell adjacent to each others, producing a new neighbour list with each effective relation encountered during the process. Specifies the mobile classes. BSC Parameters for the 2G to 3G reselection. Since MUSA at the moment does not import the BSC network database, these parameters are supposed to be used by each GSM cells.

Here a short description of all the available SHO algorithm parameters is provided:

SHO simulator OnOff


Drop Measurement quantity Drop Threshold RNC Elaboration Delay 1A RNC Elaboration Delay 1B RNC Elaboration Delay 1C

To switch on/off the simulator If set to No the simulator uses the neighbour relation as defined in the imported network. If set to Yes the simulator will consider each cell adjacent to each others, producing a new neighbour list with each effective relation encountered during the process. If the measurement quantity (Ec/Io or RSCP) level is less than the Drop Threshold the algorithm simulate a Call Drop event. It is possible to consider an effective delay due to the messages handshake and elaboration delay with the serving RNC. Typical value are respectively 500, 300 and 800 ms. MUSA permits to estimate these delays through the Calc Duration feature applied to a mobile trace.

Here a short description of all the available ISHO algorithm parameters is provided:


310

310/480

5/24/2018


ISHO simulator OnOff


GSM Drop Threshold

RNC Elaboration Delay 2D

RNC Elaboration Delay 3A

To switch on/off the simulator If set to No the simulator uses the neighbour relation as defined in the imported network. If set to Yes the simulator will consider each cell adjacent to each others, producing a new neighbour list with each effective relation encountered during the process. If the RX Level is less than the Drop Threshold the algorithm simulate a Call Drop event. It is possible to consider an effective delay due to the messages elaboration delay withhandshake the servingand RNC. Typical value are respectively 600, 1200ms. MUSA permits to estimate these delays through the Calc Duration feature applied to a mobile trace.

12.3.4 Network changes in a scene Select the scene to be modified, clicking Scene_1 in the Present Scenes section of the SIM window. In the bottom Net section (see the next figure) press the button.


311

311/480

5/24/2018


The well known Network Manager window will be shown to provide a support for network parameter changes.

With a focus to the present chapter, the following topics are relevant: • Net Viewer: it contains information about the UMR release, Network

composition, GSM cells, etc. • Net Element View: it contains information regarding the selected cell, such

as Site ID, Latitude and Longitude, antenna type, direction, tilt, etc. • Group: Siemens internal names of the parameter groups, as specified in OFD or ACL network file. • Parameter Name: Siemens internal name of the selected parameter. • Parameter Definition: general parameter definition, name, alias, group, original value, default value (if no value is provided), modified value, short description.

12.3.4.1 Network parameters changes To show how a parameter could be modified, a procedure regarding the Time to trigger 1a parameter and affecting all cells belonging to the same RNC, will be presented in this paragraph, as example. In the Network Manager window, with a right-click of the mouse, expand the UMTS network present in the Net Viewer section to identify the involved RNC. After selecting the specified the right of the window is possible to choose the parameter categoryRNC, namein(ifmrms inpanel this example) in the it Group section.


312

312/480

5/24/2018


Select Time to trigger 1a in the Parameter Name section. Apply a new value of 320 ms in the Parameter Definition section (Value control). Finally confirm this change, pressing the OK button immediately on the right of the Value box. All previous elements, selected to reach the parameter, become yellow and the new value be shownall in red. MUSAwillhighlights applied changes in yellow to easily identify any modified parameter.

At the bottom of the Network Manager window, the button is available to export a list of all modified parameters. At the opening of the Save Net Difference File dialog specify the wanted filename:


313

313/480

5/24/2018


It is so possible to save a report (in text format) containing all the changes applied to the network. By default, it is stored in the Results/Export folder of the current project. The following figure shows an example:

Moreover, with the applied to the network.

button it is always possible to clear any change

12.3.4.2 Network Global Editor MUSA offers the possibility to apply a change to a set of network elements, at the same time. To explain this feature a change to the Maximum DL transmission power parameter will be applied to a set of sites and single cells. From the Network Manager window press the

button and the

following panel will be shown immediately on the right:

By default the panel shows all networks present in the current project (the UMTS# and GSM# are dummy networks created to take into account any UMTS scrambling code or GSM CGI not imported with the Import Net Wizard ). Selecting each items and pressing the

button it is possible to delete them.

When the panel has been cleared, press the

and the Select Net Element dialog

will be activated:


314

314/480

5/24/2018


Here, the user can identify any useful element, and pressing the OK button it will be added to the previous panel, building the desired network set. In this example, the SO02U, SO16U and SO21 sites and the SO24U_2 cell have been selected. The final appearance of the panel will be as shown in the following image:

With the and buttons the user can also save and restore the selected network list for any further use. Until the button remains pressed down, all the changes applied to a parameter on the network will be applied to the whole selected network set. In the Net Viewer section of the Network Manager window, expand the network tree structure at the UMTS network level. Select then the RNC element and finally the first site inserted in the network list. Expand the site element and select the first cell. In the right part of the window select the iub topic in the Group section, and finally the Maximum DL transmission power parameter in the Parameter Name section. Now it is possible to change the transmission power with a new value (41 dBm in this example). Remember to press the OK button to effectively apply the change. All elements present in the Global Editor panel will be highlighted, together with the hierarchical items used to reach modified parameters.


315

315/480

5/24/2018


To close Network Manager window and to proceed with a new simulation for this scene press the main OK button (at the bottom of the window).

12.3.5 Replacing Scene Neighbours using an AdA file Choosing an AdA File in the Neighbours File section of a Scene it is possible to override the Network Neighbours list. This could be useful to direc tly consider new conditions after a neighbours optimization, without re-importing configuration files.


316

316/480

5/24/2018


12.4 Scene An alysis The simulator produces two kind of results: indicators and Neighbours lists. In this chapter the first category will be used to begin the scene analysis. Indicators can be used to build detailed reports or can be graphically plotted on maps, time-charts, distributions, bars, and so on. Generally any MUSA graphical window can show simultaneously many indicators, also coming from different scenes, and this helps to trace problems or to optimize parameters. Currently the indicators offered by MUSA are grouped by algorithms and are summarized below: • Cell Selection and Reselection (CSRS): the main result is the Camped Cell

(UMTS or GSM) and its measurements, such as Camped RSCP value, Camped Camped Rx Level. There is the alsoUMTS a Status indicator, Ec/Io useful interference to plot on theormap or to make a statistic about and GSM areas. Other indicators are the Reselection events, with the measured levels at the event instant. • Soft Handover (SHO): the user can evaluate the number of cells

simultaneously present in Active Set (Active Set Size Indicator) with all relevant details (Active Set Composition, RSCP and Ec/Io of each cell). The simulator builds also a series of neighbours based indicators, recorded at the event 1A, 1B and 1C instant. They consist of levels and differences between entering or exiting cell and the best server cell in Active Set, etc. • Inter System Handover (ISHO): this simulator adds a series of new indicators,

mainly to study the interworking between systems during the handover. They are related to 2D and 3A events, the UE status (Network searching, UMTS, GSM, Compressed Mode – distinguishing if it is due to a no-GSM condition – No Network), and obviously measured levels.

Moreover the measurement entities present in the loaded file are available as indicators: so it is possible to mix simulation indicators and measurement indicators, to better understanding results from a measurement point of view. The user can build a map representation using for example the Active Set Size trace, the RSCP of the Best Server in Active Set trace, and the RSCP1 or RSSI measurement trace.

12.4.1 Views MUSA simulation features offer a series of graphical windows to study indicators. They are accessible in the Views panel on the right of the screen:

(Indicator Map ), to represent indicators on scanmaps, height-maps, vectors, etc. It permits studying indicators point by point, or aggregated by cells or neighbours. (Indicator Lines ), to represent indicators during their time evolution.


317

317/480

5/24/2018


(Indicator Bar s ), to represent indicators like histogram bars, aggregated by networks, controllers (BSC or RNC), sites, cells, neighbours or as global value. becomeIndicators disabled. that have no values for the selected network level will (Indicator Distributions ), to represent the statistical behaviour of the selected indicators, such as distributions, mean values, standard deviations, pies, cumulative functions, percentiles, etc. Statistics can be computed point by point or aggregated by network element. (Indicator Grids ), to build report mixing several indicators coming from the same or different scenes. The user can also mix measurement indicators to customize the desired reports. It permits creating point by point or network aggregated report, saving it in a text file format or opening it in an MS Excel® environment. To show a panorama about all these views, a short description is reported below.

Press the Map.

( Indicator Map ) button in the Views sections to open an Indicator

To create an example of Indicator Map press the (Add Indicator ) button in the Indicators section and select an indicator from measurement group (RSCP_1s in the above figure). After few seconds the geographical trace will appear. All buttons present in in theChapter Indicator7.3 Map have same function theaspect standard MUSA map described . After thethe scanmap loading,ofthe of the window should be the same represented in the above figure.


318

318/480

5/24/2018


Press the (Indicators Lines ) button on the Views section to open an Indicator Lines window. With the same procedure described in the previous paragraph, it is possible to add two indicators (EcIo_1s e RSCP_1s) as shown in the following figure:

Press the (Indicator Bars ) button on the Views section to open an Indicators Bars window. For example it is possible to show the comparison between two scenes, using several CSRS indicators .

The Scene_1 presents a change in the Qrxlevmin parameter (from -100 dBm to -80 dBm) applied with the Global Editor to all the cells in the network. Select the Site level in the Network Items section to specify a site aggregation. Press the button and add the following indicators: Scene_Original -> CSRS Reselection and Scene_1 -> CSRS Reselection. It is possible to select the (Show Legend ) button, present at the bottom of the window, to enable the legend. The resulting view should be as the following:


319

319/480

5/24/2018


Press the (Indicator Distribution ) button on the Views section to show the Indicator Distribution window: it will appear graphically showing the percentage distribution. Adding the ISHO Status indicator and pressing the Distribution ) the chart will be plotted as shown:

(Pie

MUSA 4.6 User Manual

320


320/480

5/24/2018


Pressing the (Distribution function ) button the previous indicator will be plotted in a histogram form:

For numerical indicators, like SHO_AS_RSCP1, press the (Cumulative ) to plot the cumulative function with the possibility to show a Distribution Function percentile value.


321

321/480

5/24/2018


Press the (Indicators Grid ) button to open the window that represents results in a table format, adding one or more indicators depending on the wanted report.

On the same window, press the (Expor t Tabbed Text File ) button to open the following Export Data dialog and to save results as text file in the default directory \\Project\Results\Export :


322

322/480

5/24/2018


In the same window press the (Open in Excel ) to send the report directly in a MS Excel® window, for further elaborations.

Press the

(Close ) button to close the window, without saving data.

12.4.2 Modes In the Modes panel the user can choose the indicators visualization mode. The available modes are context-sensitive and they depend on the active view:

Network mode, where indicators are aggregated and showed by network elements (see section 12.4.3). It is available in several views such as bars, distributions, grids.

Cells mode, a sub case of the previous one, that permits the items aggregation only on a cell basis; it is used only by Indicators Map View. Neighbours mode, a sub case of Network mode, that permits the items aggregation only on a Neighbours basis; it is used only by Indicators Map View.

Route mode, that graphically represents indicators in a point by point view. There is a particular Route mode for each measurement file loaded in the SIM Module.

New Route mode, this option is available to create a route mode for a new measurement files; an “empty” route is always available. See also the above description.

12.4.3 Network Items In the Network Items panel it is possible to choose different levels for grouping indicators in Network (and cell/neighbours sub cases) mode:


323

323/480

5/24/2018


For example, the following image shows the indicators aggregation by site:

As example of grouping by cells, the following image is provided:


324

324/480

5/24/2018


In the Route mode, on the contrary, the Network Items panel works like a network filter: only points belonging to the selected items are shown.

12.4.4 Indicators 12.4.4.1. Indicator Panel The Indicator section contains the following controls: it permits the addition of an indicator to selected mode of the current view (active graphical window). it permits the deletion of the selected indicator from the mode of the current view. it permits renaming the selected indicator.

it permits the access to the Indicator Manager window to manage indicators, creating, renaming or deleting groups, and moving indicators among them:


325

325/480

5/24/2018


it permits moving up the selected indicator. This allows to control the draw order of several indicators in the same view (the items are drawn from the bottom up to the top of the list). it permits moving down, changing the drawing order. In the Indicators panels, for each item added with the associated, as shown in the following:

Pressing the

button, a small frame is

button, it is possible to graphically hide the indicator.

Pressing the button, a new window containing several (and context sensitive) graphical controls will appear; for example the following figure shows the window available for the Indicator Bars view:


326

326/480

5/24/2018


The General Tab contains the following sections:

it permits changing the color used to plot indicator when the legend controls are disabled (see below). it permits the legend enabling, the computation of the legend hits (legend intervals distribution), and the hiding of the legend image.

it permits the specification of different origins for bars y-axis.

it permits plotting the mean value of the indicator.

it permits the sort enabling, choosing between alphabetical or numerical order, and selecting between ascending or descending sorting.

it permits to show nullif values, that is the x-axis label is present even the corresponding y-axis value is not present.

it permits writing the indicators with the full name, that is in the format scene->indicator . It is useful when the window contains indicators of the same kind calculated from different scenes.

Moreover, other View windows contain further graphical options:

it permits modifying the point symbol. Several symbols are available. It is for example used in Indicator Map.

It permits setting the point size. The button enables the visualization of empty points (points without a corresponding value).


327

327/480

5/24/2018


it permits the specification of an offset across the X and Y axis (in pixels), to slightly translate two overlapping indicators. It is very useful for showing multiple indicators on a map.

it permits showing a label representing the indicator value close to each point.

It permits deciding line aspect (solid, dashed, dotted, and so on). The button specifies the line behaviour: connecting line between points or stairs. It is for example available in the Indicator Lines window.

It permits specifying the width of the line connecting subsequent points.

The following image shows the Legend Editor Tab: it permits to manage legend applied to indicators. It contains standard buttons already described in the previous chapter of this manual (see for example Section 7.3).


328

328/480

5/24/2018


12.4.4.2 Measurement Indicators

Measurements are also provided as indicators and can be mixed with simulations indicators in any views window. Depending on the scanner file loaded in a scene, Indicators panel gives the possibility to choose which item (RSSI, RSCP, Ec/Io, etc.) could be used:

12.4.4.3 CSRS Indicators Cell Selection and Reselection available indicators are shown in the figure below:


329

329/480

5/24/2018


•

CSRS_Status, indicating the UE selection state (Network Searching, No Network, UMTS, GSM)

•

CSRS_Delta_BSRS_RSCP and EcIo, indicating the difference between the Best server and the reselected cell, in terms of RSCP and Ec/Io. It is very useful when the selected cell is different from the best server cell.

•

CSRS_Camped_Cell, RSCP, EcIo, RxLevel, and Rank, indicating the selected cell and the corresponding measured quantities. Rank represents the serving order in the measurement set.

•

CSRS_Reselection, indicating the reselection events (or reselection count in aggregated views)

•

CSRS_Delta_RSCP and EcIo, indicating the difference between previous and present selected cells, at the reselection instant.

•

CSRS_OldLevel_RSCP, EcIo, and RxLevel, indicating the level of the older selected cell at the reselection instant, in terms of RSCP or Ec/Io or the GSM Rx Level.

12.4.4.4 SHO Indicators Soft Handover available indicators are shown in the figure below:


330

330/480

5/24/2018


•

SHO_AS_Size, indicating the Active Set size.

•

SHO_AS_Cell1, Cell2, Cell3, indicating the Active Set composition.

•

SHO_AS_RSCP1, RSCP2, RSCP3, indicating the RSPC value of each cell

•

in the Active Set. SHO_AS_EcIo1, EcIo2, EcIo3, indicating the Ec/Io value of each cell in the Active Set.

•

SHO_Call_Drops, indicating the Call Drop events (or Call Drop count in aggregated views).

•

SHO_Add, Drop and Replace , indicating the 1A, 1B, and 1C events (or the event count in aggregated views).

•

SHO_Delta_Add_RSCP and EcIo, indicating the difference between the added cell and the Best Server in the Active Set at the 1A event instant, in

•

terms of RSCP or Ec/Io. SHO_Delta_Drop_RSCP and EcIo, indicating the difference between the Best Server in the Active Set and the dropped cell at the 1B event instant, in terms of RSCP or Ec/Io.

•

SHO_Level_Add_RSCP and EcIo, indicating the level of the added cell at the 1A instant, in terms of RSCP or Ec/Io.

•

SHO_Level_Drop_RSCP and EcIo, indicating the level of the dropped cell at the 1B instant, in terms of RSCP or Ec/Io.

•

SHO_BSLevel_Add_RSCP and EcIo, indicating the level of the Best Server in the Active Set at the 1A instant, in terms of RSCP or Ec/Io.

•

SHO_BSLevel_Drop_RSCP and EcIo, indicating the level of the Best Server in the Active Set at the 1B instant, in terms of RSCP or Ec/Io.

•

SHO_BSLevel_Replace_RSCP and EcIo, indicating the level of the Best Server in the Active Set at the 1C instant, in terms of RSCP or Ec/Io.

12.4.4.5 ISHO Indicators Inter System Handover available indicators are shown in the figure below:


331

331/480

5/24/2018


•

ISHO_Status, indicating the UE status (UMTS, Compressed Mode, Compressed Mode No-GSM, GSM, and No Network).

•

ISHO_2D, indicating the 2D event (or event count in aggregated views).

•

ISHO_CELL_2D , indicating del Best Server in the Active Set at the 2D event instant.

•

ISHO_3A, indicating the 3A event (or event count in aggregated views).

•

ISHO_Level_3A_RSCP, EcIo, and RxLevel, indicating the level of the new system at the Handover instant, in terms of RSCP or Ec/Io, or the GSM Rx Level of the serving cell.

12.4.5 Analysis with Indicator Map in this paragraph an example of indicator analysis between two scenes will be described. The CSRS_Status indicator will be used. Select from the Views panel to open an Indicator Map window, then press button in the Indicators panel. Select the Scene_1 group and add the CSRS_Status item.

The following frame panel.

will be added in the Indicators

Repeat the previous steps and add the same indicator for the Scene_Original .


332

332/480

5/24/2018


The following frame panel. Press the figure below:

will be added in the Indicators

to show the graphical properties and select them as shown in the

Select the Legend Editor Tab and edit the title as in the following figure:


333

333/480

5/24/2018


Edit the legend title also for the Scene_1 > CSRS_Status indicator. The comparison between the two indicators can now be easily appreciated in the Indicator Map view, as shown:


334

334/480

5/24/2018


Most of the buttons present in this window correspond to functions already described in this manual (see section 7.3).

Press the

button to customize some specific map properties:

Several controls can be chosen to graphically adapt general aspect of the window. Available Cell options: •

(Font ), to set the label aspect used to indicate cells on the map.

• Length, to set the length of the triangle representing the cell.

• Border , to set the thickness of the triangle border.

• Center ID, to place the cell label in the center of the site.

• Frame ID, to add a frame around the cell label.

• Transparent ID, to make the label background transparent.

Vectors and Height Boundaries options work as the same options described in previous Section 7.3. MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

335

335/480

5/24/2018


12.4.6 Analysis with Indicator Lines A sample of Indicator Lines analysis is provided. The following image shows several SHO indicators (SHO AS Size, SHO AS EcIo_1, SHO Drop, and SHO Add). It is worth underlining the vertical lines representing the 1A and 1B events.

12.4.7 Analysis with Indicator Bars A sample of Indicator Bars analysis is provided. The following image shows the SHO_Level_Add_EcIo and SHO_Delta_Add_EcIO indicators. Bars are sorted by the delta indicators showing on the left the cell with higher delta.


336

336/480

5/24/2018


The following picture provides another example using SHO_AS_RSCP_1 and SHO_AS_EcIo_1; the Ec/Io and RSCP cells mean values are also plotted.


337

337/480

5/24/2018


12.4.8 Analysis with Indicator Distribution In the following image an example of Indicator Distribution analysis is provided. In the (Cumulative Distribution Function ) visualization mode the CSRS_Camped_RSCP is shown with its mean value, standard deviation, and 50th percentile.

The

(Distribution Function ) permits studying the whole distribution.


338

338/480

5/24/2018


Finally, another example using ISHO_Status is given to show the Distribution ) visualization mode.

(Pie

12.4.9 Analysis with Indicator Grid Indicator can befollowing used to indicators, easily buildincustom reports. The aggregating following example is generatedGrid using the the Network Mode, them by cells: •

SHO_AS_RSCP_1 Scene_1

•

SHO_AS_RSCP_1 Scene_Original

•

SHO_Add_1 Scene_1

•

SHO_Add_1 Scene_Original

•

SHO_BSLevel_Add_RSCP_1 Scene_1

•

SHO_BSLevel_Add_RSCP_1 Scene_Original


339

339/480

5/24/2018


Another possibility permits building a point by point report (Route Mode). The following figure shows the result using these indicators: • SHO_AS_Size_Scene_1 • ISHO_CELL_2D_Scene_1 • ISHO_2D_Scene_1 • ISHO_Status_Scene_1 • SHO_Add_Scene_1

Clicking with left mouse button on a column title, it is possible to activate a special filter that eliminates all rows having null value in that column. When this special filter is enabled column title and filtered rows become blue as in the following picture:


340

340/480

5/24/2018


More complex data filters can be applied pressing the send the report directly in a MS Excel® window.

(Open in Excel ) button to

The and buttons permit changing the column order, moving data from left to right and vice versa. When the report reaches the desired appearance, it could be exported using the (Export Tabbed Text File).

12.5 Neighbo urs exp ort to A DA m odu le As already described, the simulator produces two kind of results: indicators and neighbours lists. In this chapter the second category will be explained. All neighbour based indicators can generate a neighbour list, pressing the (Exp o r t Ad j L ist ) button on the SIM window, when a scene is selected. The Neighbours Redefinition option could also be used to create further neighbour lists, as described in Section 12.3.3. If this algorithm parameter is set to Yes the simulator will consider each cell adjacent to each others, producing a new Neighbours list with each effective relation encountered during the process. To create the neighbour list from the reselection events:


341

341/480

5/24/2018


• Press the

(Neighb ou rs Analyzer ) button to open AdA module (this module must be opened before any export operation)

• press

and select Scene_Original>CSRS>CSRS_Reselection as shown in the following figure:

Other neighbour lists can be created from SHO Add, Drop, Replace, and ISHO 3A events (be sure AdA module is opened):

Scene_Original>SHO>SHO_Add

Scene_Original >SHO>SHO_Drop

Scene_Original >SHO>SHO_Replace


342

342/480

5/24/2018


Scene_Original >ISHO>ISHO_A3

The created neighbour lists are available for the optimization in the AdA module. Selecting the AdA window the user can find the exported list as shown in the following picture:

For details about neighbours operations see Chapter 10.


343

343/480

5/24/2018


13. MOBILE DATA MUSA allows managing of mobile measurement files. In this chapter will be highlighted the available options dedicated to Mobile Data investigation.

13.1 Main Toolbar B utton s Ov erview 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 chapter. it will be necessary to refer to the related function (bold type) in this

Open Measurem ents : to open Scanner and/or Mobile files Close File, to close all previous loaded measurement files and release memory Cell Matchin g , to enable a window for Scrambling code alias decoding Export Tabbed Text… , to create an export in Scrambling Code as Text , to switch from Cell ID Alias to Scrambling code and vice versa Time Charts : to open Time Charts tool Route Map , to open a Map Route tool Distribu tion and CDF, to access Distribution and CDF window Joint Distribution, to access the Joint Distribution window Mobile , to show the entire messages inside a mobile measurement log file. Log File Adjacent , to show all the cell neighbours relationships read in the loaded Mobile measurement file Mobile CS Table , to show automatic CS statistics and flow chart from the loaded Mobile measurement file : to calculate how many times a sequence is Calc Between messages repeated correctly inside the measurement.

Window Synch ronization , to synchronize all the opened windows


344

344/480

5/24/2018


13.2 How to Lo ad a Mob ile File MUSA gives the possibility to import: • Only Scanner files • Only Mobile Files • Scanner and Mobile files together.

The complete procedure and further information about “How to Load a Scanner file” is explained in chapter 5. Once the project is selected as described in chapter 4, from the main menu Scanner and Mobile it is possible to choose to enable or disable the relative import options as shown in Fig 13.1 and Fig 13.2.

Fig . 13.1

Fig . 13.2 It is possible to import one Scanner and one Mobile measurement files simultaneously. In this case it is important to remember that this kind of import is useful only for files recorded at the same time to compare the results of the two measurement systems. MUSA presumes that the file name of a Scanner file and a Mobile file recorded at the same time is perfectly identical (except for the file


345

345/480

5/24/2018


extension). If this condition is not verified the following warning message will be displayed:

Be sure that the files selected for the import have been recorded at the same time, then press YES. Otherwise select NO. To start the imports from the main menu select Measurement\Open

The following window will be displayed:


346

346/480

5/24/2018


MUSA can import several kinds of scanner files (please refer to chapter 5 and Appendix for further information), choose the wished file and press Open. If the Mobile import is enabled another window will be displayed to select the desired Mobile file, see Fig . can import several kinds of Mobile files (see Appendix): As for Scanner files. 13.4 MUSA Ø

Mobile files ( *.mgf, *.txt, *.dt*)

Ø

Nemo Outdoor UMTS Export file (*.txt)

Ø

Nemo Outdoor UMTS & HSDPA (*.dt*)

Ø

Nemo Handy Indoor file (*.dt*. *.mrk)

Ø

Aska E616 VTB Log file (*.txt)

Ø

Aska E606 VTX Log file ver 42&71 (*.txt)

Ø

Aska E606 Log file ver 1&2 (*.txt) Ø Agilent E6474A UMTS & HSDPA Mobile Export (*.txt) Ø

Mobile General File Format (*.mgf)

Fig . 13.4 Choose the wished file and press Open.


347

347/480

5/24/2018


If the Mobile import is enabled after few seconds the Mobile Data Selection window will be displayed (see Fig . 13.5 ) to give the possibility to choose the mobile items to import. In the box Groups are visible all the available groups of information, while in the box Data are detailed the data available for the selected group (in Fig. 13.5 for example the reduce data for the the group Active Set are listed). User could number of imported items to limit the memory usage in presence of large amount of data to be load. Selecting Continue the import operation will continue and a progress bar will be displayed (see Fig . 13.6 ) to give information about the import status of the selected file types.

Fig . 13.5 If the date of the mobile file is different from the scanner one, the File Synchronization window will be shown:

There are three possibilities: MUSA changes the date of the Mobile file according the Scanner File. Files can be merged basing on the time information. No changes are made. Probably the files can not be merged. The user can edit both Scanner and Mobile file dates (see figure below), then can press the


button to load and merge files. 348

348/480

5/24/2018


The final result of the import operation is that a new Measurement Data table is displayed as in Fig . 13.7 . This table is divided in two sections by a vertical splitter. In the left side all Scanner data are presented, on the right side the data selected in the check boxes of Mobile Data Selection window and contained in the Mobile measurement file will be shown.

Fig . 13.6 It is possible to avoid that MUSA checks by default some Groups elements and/or some Data elements in the Mobile Data Selection window of Fig . 13.5 for the import operation. To do this it is necessary to edit a text file named mobile_ex.txt in the folder: \Projects\\UserSettings. It is simply requested to edit the Group item names or Data item names not to be loaded by default. The file has this structure [GROUPS] List of Groups items [COLS] . . .

Words in brackets are mandatory.


349

349/480

5/24/2018


Any row element of the list of Groups items has to be typed as written in the lists of Fig. 13.5 has to be written as the column titles of the Measurement Data table (theserver same related format of Data section the ColumnNAME_# Mobile Data Selection window). For the column titles initems the in form there are two possibilities: 1. Indicate a specific Server number after the underscore, e.g. RSCP_1s 2. Keep the column name general without any Server number specifications after the underscore, e.g. RSCP_ In the first case only the RSCP_1s column (RSCP values of the Best Server CPICH) will be excluded. In the second case all the RSCP columns (RSCP_1s, RSCP_2s, RSCP_3s, etc.) will be discarded for the import operation.

mobile_ex.txt example: [GROUPS] DETECTED [COLS] FREQ_ RRCDATA NASDATA

With the settings of this example MUSA doesn’t consider for Mobile loading procedure the Group DETECTED and the Data (Columns) FREQ_, RRCDATA and NASDATA. In any case the user can re-select these items by means of Mobile Data Selection window.

Fig . 13.7


350

350/480

5/24/2018


At the bottom of the MUSA window is displayed the completed file loaded status: Project name Mobile File Name Network file loaded

Number of records loaded

Scanner File Name

13.3 Measurement Data C olum ns d escription

Fig . 13.8 Starting from the Scanner side ( Fig . 13.8 ), the first column From indicates the source of the information in each raw ( S = Scanner; M = Mobile, P = Packet). At the end of the import operation MUSA creates a data grid combining information from Scanner and from Mobile file. This data grid is a sequence of data ordered accordingly to the time basis reported in the Time column. The Marker and Remark columns could help to mark a specific point and then to display it on the map. A detailed description will be given later on in this section. In the column Warning are displayed the warning message sequence names defined in the warning.txt script file (see 13.4.3). In Lat and Long columns are reported indications about geographic position in terms of Latitude and Longitude. In the following columns are reported all the information related to the measurements recorded by the Scanner equipment like RSSI, SC_1, RSCP_1, EcIo_1 etc…( Fig. 13.8 ). In the Mobile Data section are reported all the information recorded by mobile tracking tools during measurement campaign such as Active Set Composition, threshold of RSCP, EcIo (Fig . 13.9 ) Status of mobile (Fig . 13.10 ) RRC status, RRC Messages, NAS Messages (Fig . 13.11 ) and more.

Fig . 13.9


351

351/480

5/24/2018


Fig . 13.10

Fig . 13.11 When a Scanner or a Mobile file is imported, if some markers have been inserted during the measurement campaign they will be displayed automatically in the column Marker . To modify a marker name, to insert a new one or to delete an existing one, double click in the related cell in Measurement Data table. The window of Fig . 13.12 will be displayed to edit the marker.

Fig . 13.12 Once the name is typed, select OK. The result obtained is like the one presented in Fig . 13.14.


352

352/480

5/24/2018


To delete a Marker double click on the relative cell then delete the word that is automatically displayed in the window of Fig . 13.12 and press OK. The handling of data in the Remark column is equivalent to the one just described for the Marker column.

Fig . 13.13 It’ possible to change the column order of the Mobile Section selecting a column and dragging it to the new position.

Measurement Data window buttons description: • •

Minimize on bo ttom , to minimize the window. , to calculate functions for a specific data column. Ap p ly fu n ctio n 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


353

353/480

5/24/2018


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 / Mobile , to enable search window in the relative section. Type the word to search in the Measurement Data table Scanner or Mobile section. This function is KEY SENSITIVE.

•

Load/Save Mod ified 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).

•

Save Selected Colum ns or der , to save modifications in columns order. After a change in columns order it is possible to save the new configuration as MUSA default pressing this button. The modifications will be saved in the file mobile_col_order.txt in the folder: \Projects\\UserSettings.

13.4 Mobile Data Function s This section is an overview of some functions that could be used when a Mobile file is loaded.

13.4.1 Export Tabbed Text MUSA gives the possibility to export the information displayed in Measurement Data table in a text file by selecting from the main menu Measurement\Exported Tabbed Text…


354

354/480

5/24/2018


The Export Tabbed Text File window will be displayed as shown in Fig . 13.14 . In this window user should choose the Items that have to be exported from Scanner and/or Mobile side selecting them in the relative check box.

Fig . 13.14 If the user needs to export the same information for more files, it is possible to open and edit an export configuration file .ed in the folder: \Project\\Resources \ExportDefs From the window in Fig. 13.14 press the button to load an existing configuration file, after the loading phase is completed all the configured items will be selected in the relative check boxes. Press to start the export of the selected items in a text file, the following window will be displayed to edit the desired file name and to choose the destination folder:


355

355/480

5/24/2018


13.4.2 Main Menu VIEW Options In this section will follow a short description of the option available in the menu View after a Mobile file import. Selecting View\Time Chart or View\Route Map the relative data graphical visualization windows will be shown as reported in the examples of Fig . 13.15 and Fig. 13.16 . For further details see chapter 7.

Fig . 13.15


356

356/480

5/24/2018


MUSA gives the possibility to open more windows at the same time and to synchronize them with the Window Synchronization function located in the Window\Window Synchronization

When the Window Synchronization function is enabled all events and messages in Measurement Data table and in the other windows are synchronized. After a double click on one cell of the Time column in the Measurement Data table a star pointer is displayed in the Route Map window like in Fig . 13.15 and/or a vertical line is shown In Time Chart graph area like in Fig . 13.16 .

The Window Synchronization option allows the synchronization also of the Mobile Log File option windows. and Mobile Neighbo urs

Selecting View\ Mobile Log File

the Mobile Messages window displayed in Fig .13.17 will be opened. In this window is reported the network control messages flow recorded by the Mobile tracking software/tool.


357

357/480

5/24/2018


Fig . 13.17

To see the content of a specific message double click on the time related to that message in the Measurement Data table Time column. Thanks to synchronization option the corresponding message content will be highlighted on the Mobile Messages Window as shown in Fig . 13.17 .

Selecting View\Mobile Neighbours

it will be opened a window with a complete list of the neighbours cells derived from the Sysinfo or Measurement Control messages contained in the mobile messages flow (Fig . 13.18 ). As previously described this function is affected by the Window Synchronization option.


358

358/480

5/24/2018


Fig . 13.18

13.4.3 Main Menu TOOL Options In this section will follow a short description of the option available after a Mobile file import accessing the menu Tool. Selecting Tool\Statistics

two functions (see Chapter 7) are available.


359

359/480

5/24/2018


Once one of the Statistic function is activated in the relative series menu the Mobile Data columns are available between the selectable series. Selecting Tool\Calc Duration

is activated a function that gives the possibility to count the time between two messages in the Measurement Data table. When this option is enabled the window in Fig . 13.19 is displayed. In the dialog box New Column Name is possible to edit the name of column in the Measurement Data table and the file name where the results will be saved. This file will be created in the folder: \Projects\\Results\Statistics.

Fig . 13.19 In the column or in that between file it willthe be two reported the start and end time of the sequence and the time difference selected messages.


360

360/480

5/24/2018


Use the drop down menu Start Msg in the Column box to define the column title in which a specific message has to be searched and then select the starting sequence message between the ones available in the list of the relative Message menu. Similarly, use drop down menu box to select define the the Stophas Msg Column column title in the which a specific message to in bethe searched and then ending sequence message between the ones available in the list of the relative Message menu. To start the sequence counting, press Calc. MUSA shows some information: • the number of correct sequences • the number of incorrect sequences • details about the time in which the failed sequences start.

Only the correct sequences are saved in the file. A sequence is considered incorrect if after the message selected in the Start Msg menu it is not encountered the message selected in the Stop Msg menu. In Fig. 13.20 it is shown an example of this function. It is allowed to choose messages from different columns. In the example all the sequences starting with a “RRC Connection Attempt” RRC message and ending with a “ALERTING” NAS message are counted.

Fig . 13.20 Until a selection of the button Clear File all the results generated by this function will be appended at the end of the existing file. The file warning.txt stored in the folder \Projects\\Environment\Script


361

361/480

5/24/2018


allows the user to define a sequence of messages/data to generate a specific warning every time that the sequence will be found in the messages/data of the Measurement Data table Scanner and/or Mobile section (see Chapter 5 and 13.3) or every time inthat deviation in the defined will8.6.2 be or encountered, as configured the ascript file itself. Please refersequence to Section Appendix for details on warning.txt editing. Every sequence defined in the warning.txt file has a name. In the column Warning of the Measurement Data table are reported those names as result of the research on the defined sequence with the modality configured in the Warning file. The warning match and count operations are performed every time that a new measurement file is imported. When a Measurement file is already loaded selecting Tool\Warning Generation

after a re-editing of the warning.txt file, the Column Warning of the Measurement Data table will be updated.

13.5 Mo bile CS Statistics MUSA is able to get automatic statistics and KPI, analyzing the mobile CS message flow (RRCState, Layer 3, NAS messages, etc). To enable this function, after mobile data loading, select the menu View \Mobile CS Tables :


362

362/480

5/24/2018



The following window will be shown:

Fig.13.21 This window is divided in several part: the upper side contains UMTS statistics, GSM statistics, UMTS failures, and KPI. The lower side is composed by call message flow charts (for details about this feature see next paragraph).

The user can select each tab and then press the selected table.


(export) button to save the

363

363/480

5/24/2018


UMTS counters sheet

This table contains several counters related to the UMTS part of CS calls. A sample is shown in the figure above. It contains total and cell based values.

GSM counters sheet

This table contains several counters related to the GSM part of CS calls. A sample is shown in the figure above. It contains total and cell based values (cell identification is ARFCN:BSIC).

UMTS failures sheet

This table contains a list of all setup failures and drops present in the current loaded trace with time and position information. If the user click on the Date-Time information all the other synchronized windows will be updated to show the selected failure event.


364

364/480

5/24/2018


KPI sheet

This table contains a predefined list of KPI based on UMTS and GSM counters. This sheet also reports formulas and units used in KPI.

13.6 Mo bile CS Mess age Flow Mobile CS message flow charts can be shown using MUSA. To activate this function, after mobile data loading, select the menu View \Mobile CS Tables :


The following window will be shown:


365

365/480

5/24/2018


Fig.13.22 Mobile CS Message Flow is visible in the bottom part of the window. Select UMTS or GSM counters sheet and then use navigation buttons to explore each call present in the current loaded trace. Mobile CS Message Flow chart graphically represent transition between different phases. Final transitions are drawn using green (call ok) or red (failure) colors. Using these chats the user can understand how messages evolve call by call.

Fig.13.23 –UMTS CS call co rrec tly term inated . MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

366

366/480

5/24/2018


Fig.13.24 – UMTS CS c all f ailu re

Fig.13.25 –UMTS CS call c orr ectly term inat ed in GSM.

13.7 Mob ile Data Queuing When there are several mobile files of the same project, MUSA provides the possibility of combining all data collected in a single file. This step could be useful to compute statistics (as described in Chapter 7) on a whole collected data. To prepare a merged file select Queue Mob ile Files in the main toolbar


367

367/480

5/24/2018


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

Fig.13.26

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


368

368/480

5/24/2018


Fig.13.27 The File type panel permits selecting one of the supported file types: MUSA will show the Available files for the chosen format. Pressing the (Select A ll files ) button it is possible to select all files present in the folder listed in the Available Files list, as in Fig.13.27 . Pressing the following available files one by one.

(Select File ) button it is possible to select the

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. The Selected Files section reports all the selected items with their time and date. Using the (Move Up , and Mo ve D o w n ) 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 below). Every time the label informs the user 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


369

369/480

5/24/2018


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 after a file in the list, a drop-down calendar appears and letbutton the user to having specifyselected a new date:

Fig.13.28


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 opened, showing by default in the Mobile folder of the current project, as in Fig.13.29 :


370

370/480

5/24/2018


Fig . 13.29 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 to start the merging process. MUSA will create a Mobile General Files (*.mg f ), that can be regularly re-loaded by the tool.

13.8 HSDPA Inform ation MUSA can handle contained in mobile traces acquired using Nemo Outdoor (.DT*HSDPA files) or information Agilent E6474A.

Available data from Nemo Outdoor: PacketState HSDPA_SampleDur HSDPA_PhReqThp HSDPA_CQIRepFact HSDPA_CQICycle HSDPA_CQI HSDPA_CQIMin HSDPA_CQIMax HSDPA_CQIDist HSDPA_Category HSDPA_SC HSDPA_RSCP HSDPA_EcIo HSDPA_NumMonHSSCCH HSDPA_PowerOffset HSDPA_AckNackRep HSDPA HRNTI


(already present, now it is updated with the HSDPA State) Sample Duration [ms] Physical layer requested throughput [bps] CQI repetition factor, from 1 to 4 CQI feedback cycle [ms], from 0 to 160. CQI Mean Value CQI Min Value CQI Max Value CQI Distribution HSDPA Category 1-12, HS-DSCH primary scrambling code (0-512) RSCP measurement for scrambling code in HSDPA-SC Ec/Io measurement for scrambling code in HSDPA-SC Monitored HS-SCCH channels (0-4). 0 when HSDPA is not used. Measurement power offset: (–6 dB to 13dB) ACK/NACK repetition factor (1-4). H-RNTI Identifies a UE having a HS-PDSCH assignment within a cell (0-65535)

371

371/480

5/24/2018


Available data from Agilent E6474A: HSDPA_HARQpacketcount Packets sum (for each process ID - downlink direction) HSDPA_DLThp HSDPA_HSPDSCHBLER HSDPA_ValidRxSCCH HSDPA_HARQProcCount HSDPA_NewProcTx HSDPA_BlockErrors HSDPA_RxBitRate HSDPA_BLER HSDPA_HSDSCHprimSC HSDPA_CQISampleCount HSDPA_CQI HSDPA_AckCount

Total Downlink HS-PDSCH HSDPA Throughput (kbits/sec) Total Downlink BLER (%) % Valid SCCH Received H-ARQ process count New Transmission for Process Block Errors Received Bit Rate (bits/sec) BLER(%) Primary Scrambling Code CQI Total Sample Count CQI Average Ack Count

HSDPA_NackCount HSDPA_HsSCCH

Nack Count Channelization Code array

13.9 DVB-H and Flash -OFDM su pp or t Using MUSA it is possible to load and analyze DVB-H files collected by NSN StangaE tool, Nemo, N77, etc. Please see Appendix G and H for a list of all supported sources. In the following picture an example of Flash-OFDM analysis is shown.


372

372/480

5/24/2018


13.10 Packet Data A third import option is available in MUSA. If with a specific tracking tool some data related to the packet transmission are recorded in a measurement session, it is possible to load them in the Measurement Data Table. It is requested that the collected data are ordered on a time basis and stored in a Microsoft CSV format. Alternatively, MUSA can load “.wlan” files collected by NSN StangaE tool in outdoor or indoor mode. In this way it possible to analyze WI-FI networks with MUSA.

In the following picture an example of a WI-FI network measurement is shown (“.wlan” file).


373

373/480

5/24/2018


13.11 Indo o r Data MUSA can manage indoor file collected by NSN StangaE tool or Nemo (Nemo Handy). In the following pages, an example of indoor loading will be shown (the user can find these example files in Help/Indo or Exam ple subfolder). The first step is to open the Nemo Indoor file (as mobile data):

As you can see in the following picture, no coordinate are available in MUSA at this moment:


374

374/480

5/24/2018


Selecting Coordinate By Markers from Measurement menu:

it is possible to import pixel (or geographical) coordinate:

If the user answers YES the file will be adjusted in pixel coordinate, otherwise it is possible to create an outdoor file. Push the YES button. A window will ask you to specify a bitmap file containing the floor map.


375

375/480

5/24/2018


A new window asks for a “.mrk” file created by Nemo and containing indoor marker references.

As you can see in the next picture, now MUSA has calculated indoor coordinate (pixel-coordinate):


376

376/480

5/24/2018


It is now possible to analyze collected data as for normal outdoor file, for example using a map, as shown in the following figure.


377

377/480

5/24/2018


14. DATA EXPORT

With the MUSA export options it is possible to store in a file the desired fields of the measurement data previously loaded.

14.1 Main to olbar B utton s Ov erview 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 chapter. it will be necessary to refer to the related function (bold type) in this

Expo rt Tabbed Text… , to open Data Export window , to create a KMZ file containing Network, Export to Google Earth™ … measurement, etc.

14.2 Expo rt Tabb ed Text Through this option it is possible to save in a text file the content of the desired columns of the Measurement Data table reported in Fig . 14.1 .


378

378/480

5/24/2018


Once a Mobile and/or Scanner file is loaded, selecting in the main menu Measurement\Export Tabbed Text…

the Export Tabbed Text File window of Fig . 14.2 is shown.

Fig . 14.2

Export Tabbed Text File window options description: • Scanner

Settings: all the Scanner section column names of the Measurement Data table are reported. In the relative check box it is possible to select the items to export. Selecting the All button the complete list of available items will be exported. Pressing the Clear button all the previous selections are removed.


379

379/480

5/24/2018


• Mobile Settings: all the Mobile Data section column names of the

Measurement Data table are reported. In the relative check box it is possible to select the items to export. Selecting the All button the complete list of available items will be exported. Pressing the Clear button all the previous selections are removed. • Global Settings: the following options are available

o Export Header: to export an header with the item title reported o Lon before Lat: to swap the Latitude and Longitude columns in the exported file o Export Time : to export the Measurement Data table Time column. If As offset is selected in this column the time is exported in step of 1 sec instead that the specific sample time o Export Source : to export the Measurement Data table From column o Geo System: to allow the conversion of the exported coordinates. It is possible to force the system to WGS 84 or ED 50. o Invalid Value: Ø Ignore if Not Lat/Long : to discard any row with invalid coordinates data Ø Scanner Null -> 999.9: to force not measured scanner value to 999.9 o Export Numeric SC: to export the numeric Scrambling Code instead of Cell Alias Name as cell definition

Once the desired items are selected it is possible to start the export procedure pressing

OK

The browser window of Fig. 14.3 is displayed to edit export filename and to select destination folder.

Fig . 14.3


380

380/480

5/24/2018


14.2.1 Predefined Export User could create a support file to list the types of items to export, subsequently available as predefined configurations for further export operations. Selecting the Open Export Definition File window of Fig . 14.4 will be shown to choose an export definition file with the mandatory extension .ed in the default folder: \Projects\\Environment\ExportDefs.

Fig . 14.4 Once the file is opened, in the Export Tabbed Text window all the check boxes of the configured items will result selected. The export definition file ExportDef.ed is the default configuration file loaded by MUSA opening the export function. The structure of the export definition file has to be the following: [GLOBAL SETTINGS] Items activation: YES/NO [END] [SCANNER SETTINGS] ... [END] [MOBILE SETTINGS] ... [END]

Words in brackets are mandatory. They are used to distinguish the three different sections of the Export Tabbed Text window.


381

381/480

5/24/2018


In the Global settings section for every element displayed in the window of Fig . 14.2 the user has to specify a YES or NO, except for the Global System part. In this case it has to be set 1 for WGS 84, 2 for ED 50, 3 for “as in data”. In the Mobile and Scanner Settings sections it is possible to list the name of the desired items. to becolumn the same ofin the column titles of the Measurement Data table. ForThe the name serverhas related titles the form ColumnNAME_# there are two possibilities: 1. Indicate a specific Server number after the underscore, e.g. RSCP_1s 2. Keep the column name general without any Server number specifications after the underscore, e.g. RSCP_ In the first case only the RSCP_1s (RSCP values of the Best Server CPICH) will result selected and then exported. In the second case all the RSCP columns (RSCP_1s, RSCP_2s, RSCP_3s, etc.) will be selected and then exported. It follows an example of an export definition file: [GLOBAL SETTINGS] NO YES NO NO NO 1 YES NO YES [END] [SCANNER SETTINGS] Lat Lon RSSI SC_ RSCP_ EcIo_ [END] [MOBILE SETTINGS] [END]

In Fig . 14.5 the result after the loading of the export definition file of the example is shown.


382

382/480

5/24/2018


Fig . 14.5

14.3 Other Exp ort Form ats Two other types of export are available for a Scanner Measurement file:

1. Selecting Scanner\Export SGF file…

it is possible to export the current scanner data loaded into .sgf Scanner file format. Warning: some column information present in the Measurement Data window might be not saved.


383

383/480

5/24/2018


2. Selecting Scanner\Export SEM file…

it is possible to export a .spx or .sgf Scanner file format in a .sem format to be used with the NSN StangaE tool.

3. Selecting Mobile\export MGF…

it is possible to export the current Mobile data loaded into .mgf file format. MGF file format can be quickly loaded in MUSA. 4. Selecting Scanner\export ML87208 file…


384

384/480

5/24/2018


it is possible to export a .sem Scanner file in the Anritsu ML8720B .dat format (for example to load data in Actix Analyzer). The Unspecified Short format will be used.

14.4 K MZ Export for Go ogle Earth™ It is possible to create a KMZ file for Google Earth™ containing network sites, measurement, etc., selecting Tool\Export for Google Earth…

The first time you choose this option a configuration window will be shown, as in the following picture:


385

385/480

5/24/2018


By means of this window the user can decide to save a file or to start it automatically in Google Earth client. There are several option concerning antennas style, measurement aspect, and camera point of view.


386

386/480

5/24/2018


15. PM COUNTERS ANALYZER PM Counter Analyzer (UPA) is a NSN tool for the PM Counter analysis that runs embedded in MUSA. The PM Counter Analyzer module provides the following functionalities: -

Import of the RNC and NodeB PM binary files (ASN.1 format)

-

“Selective Import” of the RNC and NodeB PM binary files (the user can select a subset of counters to import – e.g. only accessibility and soft handover counters). It allows to speed file up import, to reduce the amount of disk space needed for storage andup to the speed database queries

-

Support of UMR releases 3.5, 4.0, 5.0 and 6.0. The support of future UMR releases (including the relevant KPIs and Aggregates) is guaranteed in the upgrade to new MUSA releases

-

Availability of a pre-defined set of KPIs and Aggregates (sum of raw counters) according to the Siemens Customer Documentation

-

KPI and Aggregate definition: full editing capabilities of pre-defined KPIs and Aggregate

-

KPI and Aggregate definition: KPI editor available for user-defined KPIs definition and modification of pre-defined KPIs

-

Report definition: the report structure is fully customizable and the user can select which KPIs, Aggregates and raw counters shall be present in the report (report updating functions are provided). The user shall select also the Network element aggregation (e.g., cell, nodeB, RNC) and the Time aggregation (e.g., hour, day, week) and can decided to restrict the analysis to a specified timeframe (consecutive hours or days). A set of pre-defined reports is also available for the most common analysis

-

Report analysis: by default the report is generated with the default Aggregation options, but the user has the possibility to modify them in the Analysis window

-

Report analysis: analysis of the the ATM counters at line, VP, VC level with the complete information of the TNL network structure derived from the PM files

-

Report export: all generated reports can be saved in Excel or CSV format

-

Area report: it is possible to define, save and modify areas (cluster of cells) and to generate reports only for the cells of the area or for the area as a whole


387

387/480

5/24/2018


-

Batch analysis: this functionality allows the user to automate the generation of reports by specifying an import directory (where PM binary files shall be put), an export directory (where the generated reports will be saved) and the list of reports that shall be generated

-

Scheduling: this functionality will allow to schedule at a predefined time and with a predefined periodicity the operation of file import, report generation and batch analysis

-

Export/Import: users can share the same report structure, areas and userdefined KPIs and aggregates thanks to the Export and Import functions that are available for these kind of data. Moreover users can export/import the database containing the imported PM counters and easily share or handover the PM counters analysis tasks

-

Handling of a new releases: facilities for the import from a UMR release to another UMR release of user-defined reports and KPIs

-

Scanner tracing: by selecting a PM binary file a CSV file is generated reporting the list of all the active counters with their aggregation in scanners and the correspondent granularity period

-

Suspect flag: invalid measurements (Suspect Flag = 1) can be filtered out from the analysis

-

Busy hour: the users can choose a busy hour indicator among the available ones and can generate report with the KPIs and aggregates for the hour when the selected indicator reaches the maximum during the day

A description of all of these functionalities will be provided in the next paragraph of this section.

15.1 Openin g PM Coun ter An alyzer To start the PM Counter Analyzer, select PM Counter Analyzer from Tools menu, (Fig. 15.1 ). Tools\PM Coun ter Analyzer

Fig . 15.1 Alternatively, click the PM Counter Analyzer button on MUSA toolbar ( ). Fig . 15.2


388

388/480

5/24/2018


Fig . 15.2 MUSA will show the DB connection status bar ( Fig . 15.3 ).

Fig . 15.3 At the end of the DB connection operation the PM Counter Analyzer window is displayed as in Fig . 15.4.

Fig . 15.4

15.2 PM Counter An alyzer to olbar In the main toolbar of PM Counter Analyzer ( Fig.15.5 ) there are 7 specific functional buttons.

Fig . 15.5 The toolbar buttons allow accessing the functions described in this chapter.


389

389/480

5/24/2018


•

Menu PM Files , to import and to delete the counter files. To export and import the PM counters database

•

Menu Template , to create, to modify, to delete and to work with a template

•

, to define, to modify, to delete and to work with Menu Indicator KPIs and aggregate

•

, to create, to delete and to modify a Batch Menu Batch Analysis Analysis for automatically importing the counters and generating reports

•

Menu Area , to create, to delete and to modify a cluster of cells on which it will be possible to restrict the analysis

•

, to schedule a files import, a templates generation or a Menu Task batch analysis

•

, to optimize the database’s dimension, set the general Menu Tools options of the tools and perform the Scanner Tracing

15.3 Menu PM files By clicking on the down-arrow besides the PM Files icon (Fig . 15.6 ) it is possible to access to the operation available within the PM files menu.

Fig . 15.6

15.3.1 Import PM Results File This operation allows importing new counter files. In the Files Selection Tab (Fig.

15.7 ) it is possible to choose to import a single file or a group of files after pressing


390

390/480

5/24/2018


the button

. Besides, it is possible to choose a whole folder if is clicked. The files must be in binary format in both cases.

Before pressing the 15.8 .

button select the Import Mode as shown in Fig.

Fig . 15.7 In the Import Mode Tab it is possible to choose the File Type (All PM File Types, RNC PM File Type, NodeB PM File Type) and to select: - to import all the indicators contained in the PM result files or -

to import only the indicators of the selected classes. In this case flag the particular class or classes that are needed. As a result, the database will be lighter and the query faster

In case a “selective import” is chosen the first time a PM binary file is loaded for that project, the tool remember this configuration and present it as a default the next time a PM binary file is imported in the same project. It is possible to modify the initial choices by clicking on the button ;a warning message will appear indicating that you are changing the default import mode and by clicking “Yes” you will be allowed to modify the selective import settings.


391

391/480

5/24/2018


In case the user choose to import a PM binary file that has been already imported in the database, only the PM counter classes that have not yet been imported will be loaded in the database.

Fig . 15.8 In this window, by right-clicking with the mouse on a particular class the button will appear (Fig . 15.9 ). See Appendix K for the complete list of the raw counters contained in each Class. By clicking this button a new window will be opened listing all the indicators that belong to the selected class ( Fig . 15.10 ).


392

392/480

5/24/2018


Fig . 15.9

Fig . 15.10


393

393/480

5/24/2018


After having pushed the button, in the Log Window Tab all the files selected will be listed and the import process will start. The result of the import process will also be shown ( Fig . 15.11 ) The button allows stopping the import process; when pressed the program will stop the import process after having finished to import the file that is being currently loaded.

Fig . 15.11

15.3.2 Imported Files This operation allows seeing all the loaded files (Fig. 15.12 ) listing the following information: -

PM filename

-

Date of collection

-

Sender Name: ID of the Network Element that has collected the file

-

Sender Type: the type of Network Element (RNC or NodeB) that has collected the file

-

UMR version

By clicking on the + the list of all the imported classes for each PM binary file will be displayed.


394

394/480

5/24/2018


Fig . 15.12

15.3.3 Remove Imported Files This operation allows deleting a file, a group of files or all the files ( Fig . 15.13 ). In the first case select the check box near UMR version. In the second case flag the check box related to a particular row or a group of rows and push the button

.

Fig . 15.13

15.3.4 Import database This operation allows to import a PM counter database created on another MUSA installation into an its own MUSA project, so allowing users to share data already


395

395/480

5/24/2018


processed and avoiding waste of time in repeating the PM binary files import operation for users that are working on the same project. From the Menu PM Files select Import Database. The import process will start, a progress bar will be displayed and a message will be displayed when the import will be completed (Fig . 15.14 ).

Fig . 15.14

15.3.5 Export database This operation allows exporting a PM counter database from a MUSA project, in order to make it available for other MUSA users on another MUSA installation. From the Menu PM Files select Export Database. The export process will start, a progress bar will be displayed and a message will be displayed when the export will be completed (Fig . 15.15 ). As specified in the Export complete” message three files are saved in a predefined directory.

Fig . 15.15

15.4 Menu Tem plate By clicking on the down-arrow besides the Template icon (Fig . 15.16 ) it is possible to access to the operation available within the Template menu.


396

396/480

5/24/2018


Fig . 15.16

15.4.1 New Template definition This operation allows defining a new report. It is the first operation that the user should make after having imported the files. In this way it is possible to execute queries on the imported data. When selected, the window displayed in Fig. 15.17 will appear. In the Parameters Tab the general information of the template shall be provided. First of all, write the name of the new template (field Name , this operation is necessary otherwise the template will not be saved) then choose the UMR version (field UMR version) and eventually describe the template (field Description). The field Class is always fixed to User defined . In the Aggregation parameters area, select the Network Element, the File Type (RNC PM File or NodeB PM File) and the Time Aggregation. The Network Element can be one of the following (in brackets are reported the allowed “upper level” aggregations): -

RNC RNC Adjacent (? RNC) NodeB (? RNC) Cell (? RNC) Adjacent (? Cell ? RNC) ATM Line ATM VP ATM VC

The Time Aggregation allows to aggregate per granularity (maximum detail provided by the PM counters), hour, day or week. After having fixed those two aggregations, in the template generation it will be anyway possible to aggregate samples also by all the allowed upper lever aggregation. For example, if the aggregation for Cell-Hour is chosen in the template definition, then in the Indicator Analyzer window (see section 15.5.7) it will be possible to dynamically modify the aggregation by choosing for instance RNC-Day, Cell-Day, etc. At the end, in the Filter Definition area optionally define a time filter on the data. The Filter Type can be Hour or Day . In case Hour is selected a time range shall be defined in the fields Filter Start and Filter End. Only data included in this filter range (extreme included) will be considered in the indicators computation.


397

397/480

5/24/2018


In case Day is selected a day range shall be defined in the fields Filter Start and Filter End. Only data included in this filter range (extreme included) will be considered in the indicators computation.

Fig . 15.17 Before saving the new template, it is necessary to decide the indicators that will be calculated in the template by selecting them in the Indicators Tab (Fig . 15.18 ). It allows choosing: • in the Raw tab among all the raw counters • in the Aggregate Tab among all the indicators originated from a sum or

subtraction between two or more raw counters or aggregates • in the KPI Tab among all the indicators obtained with any mathematical

operation (sum, subtraction, multiplication, division) on aggregates or raw counters or KPIs


398

398/480

5/24/2018


Fig . 15.18 Select the desired raw counters, aggregates and KPIs and push the Left or Right Arrows to exclude/include them in the template definition (multiple selection is allowed). The selected ones will be listed in the right section of the window; press the Up or Down Arrows to change their order in the template. At the end, push the button . Raw counters, aggregates and KPIs are organized according to the Class they belong to (refer to the Import section for details). In the selection menu only the raw counters, aggregates and KPIs that is possible to aggregate according to the selected aggregation parameters will be displayed.

NOTE: in case the Network Element aggregation chosen is ATM Line, ATM VP or ATM VC the Time aggregation allowed will be only Granularity Period and a new field Visualization Mode will be displayed (see Fig 15.19 ). In case Objects ID on columns is chosen it will be possible to insert only one indicator per template and the ATM Object ID will be reported on column (this visualization is useful to analyze the trend over time of a single indicator for all the ATM objects). In case Counters on columns is chosen it will be possible to insert as many indicator as you want in the report and the ATM objects ID will be reported in each row of the report (this visualization is useful to analyze the trend over time of more than one ATM counter contemporarily)


399

399/480

5/24/2018


Fig . 15.19

15.4.2 Edit Template This operation allows seeing the list of all the defined templates with the following information (Fig . 15.20 ): -

UMR version

-

File Type (RNC PM File or NodeB PM File)

-

Template name

-

Template description (if filled during Template definition)

Choose the template you want to modify and open it by double-clicking on it with the mouse or pressing the button

. Then modify and/or correct it in the same

way as described in paragraph 15.4.1. Finally press the button choose if overwrite or not the old template.

and

MUSA 4.6 User Manual

400


400/480

5/24/2018


Fig . 15.20

15.4.3 Delete Template This operation allows deleting report templates previously created. When selected, the window displayed in Fig . 15.21 will appear. Select the templates you want to delete and push the button

.

Fig . 15.21

15.4.4 Export Templates This operation allows exporting templates defined in a MUSA installation to another MUSA installation. When selected, the window displayed in Fig . 15.22 will appear.


401

401/480

5/24/2018


Select the Templates that you want to export and push the button. Choose the path where you want to save the templates definition and two files with extension .upa will be created. You can then copy these files on another PC and import the template definition in another MUSA installation running on this PC (see section 15.4.5). In case the template contains indicators that are “User defined” it is recommended to save them separately.

Fig . 15.22

15.4.5 Import Templates This function allows importing in a MUSA installation Templates that have been defined on another MUSA installation. When selected, the window displayed in Fig.

15.23 will appear. Push the button and a new window will be opened. Find the path where the exported templates have been saved (that is, the files – with extension .upa - previously generated with the Export Template function) and select the folder. The Import window will be populated with all the templates available for the import (see Fig 15.24 ). You can tick the Templates that you want to import among all the available ones and finally push the button


.

402

402/480

5/24/2018


Fig . 15.23

Fig . 15.24

15.4.6 Add Template to UMR Version This operation allows copying the structure of a template (aggregation options, indicators) defined for a certain UMR version in another UMR version. When selected, the window displayed in Fig . 15.25 will appear.


403

403/480

5/24/2018


Fig . 15.25 Here you have to choose the Start UMR Version (where the template already exists) and the New UMR Version (where you want to create a copy of the template). Then tick all the templates that you want to copy and push the button . After the copying operation remember to check the indicators present in the template since some of them may be changed from a release to another one.

15.4.7 View Template This operation allows viewing all the characteristics of a system template, that is of a template provided with the MUSA installation and that cannot be modified by the user maintaining the same name. When selected, the window displayed in Fig . 15.26 will appear. By double-clicking on the template name or by selecting the template and pushing the window displayed in Fig. 15.27 will be opened. In the tab General are reported the general info on the template, in the tab Aggregations Parameters are reported the Network Element and Time Aggregation settings and eventual Filter definition, in the tab Indicators are listed all the indicators that compose the Template columns.


404

404/480

5/24/2018


Fig . 15.26

By pushing the button (see Fig . 15.27 ) the template name will be modified as TemplateName_Usr and it will be possible to modify and save the characteristics of the template.

Fig . 15.27 For the description of the procedure for the modification of the template please refer to section 15.4.1.


405

405/480

5/24/2018


15.5 Menu Ind icator By clicking on the down-arrow besides the Indicator icon (Fig . 15.28 ) it is possible to access to the operation available within the Indicator menu.

Fig . 15.28

15.5.1 New Indicator This operation allows to define a new indicator (aggregate or KPI). When selected, the window displayed in Fig. 15.29 will appear. The meaning of the fields that must be filled is the following: -

Name : is the name of the new indicator

-

Group: you can choose between KPI and Aggregate. In the first case it is possible to use all the mathematic operations using all the raw counters and all the aggregates and KPIs already created. In the second case only sums and subtractions are allowed using raw counters and aggregates

-

UMR version: select the UMR version the new indicator will refer to

-

Category: only User Defined can be chosen. System Defined indicators will be provided only with a new MUSA installation or update

-

Type : indicates the format of the number saved in the database (it is suggest to indicate INT for Aggregates and DECIMAL for KPI)

-

Priority: is present for future uses

-

Description: you can optionally insert a short description for the new indicator

-

Busy Hour Indicator : when the tick-box is checked the indicator will be displayed among the available ones for the evaluation of the Busy Hour


406

406/480

5/24/2018


Fig . 15.29

An important voice is represented by the pressed the window displayed in Fig . 15.30 will appear.

button. When

Fig . 15.30


407

407/480

5/24/2018


In this window you have to flag the allowed Network element aggregation and Time aggregation with the same principle illustrated in the section 15.4.1. When finished push the button

.

NOTE: this operation is very important since it will have impact on the list of indicators that will be displayed in the template definition. As a rule of thumb, the following guidelines should be followed: -

-

for the Time Aggregation checks all the available ones except for ATM related aggregates or KPIs where only Granularity Period shall be checked; in case of ATM counters, checks only the Network Element to which the raw counters that will be used for the aggregate or KPI definition belong to (ATM Line, ATM VP or ATM VC) in case the raw counters used in the aggregate or KPI definition are ALL measurements Adjacent Cell checks Adjacent , Cell and RNC in case the raw on counters used in base, the aggregate or KPI definition are ALL measurements on Cell base, checks Cell and RNC in case the raw counters used in the aggregate or KPI definition are ALL measurements on NodeB base, checks NodeB and RNC in case the raw counters used in the aggregate or KPI definition are ALL measurements on adjacent RNC base, checks Adjacent RNC and RNC

After this operation, it will be possible to insert the new indicator formula. Search in the lists below the KPI, Aggregate or Raw that is needed for the formula definition (push the + button to open the indicator sub-causes) and click twice the mouse. The selected indicator will be added in the Formula window and mathematical operation can be done by clicking on the desired button. In case you want to sum all the subcauses of a raw counter you can double-click on the root of the raw counter and they will be summed up in the Formula window. When finished, and “Test” is created.

the formula

it. In the example in Fig . 15.31 a new indicator with the name


408

408/480

5/24/2018


Fig . 15.31

15.5.2 Edit Indicator This operation allows modifying an indicator created as User Defined. When selected the window displayed in Fig . 15.32 will appear containing the list of all the UserDefined indicators. By default the latest UMR version will be displayed, in order to list User-Defined indicator that belongs to an older UMR release select the appropriate one in the field UMR Release . After having double-clicked on the indicator you want to modify or having pushed the button , you can correct it (refer to section 15.5.1) and then decide to overwrite the old indicator or not.


409

409/480

5/24/2018


Fig . 15.32

15.5.3 Delete Indicator This operation allows deleting User Defined indicators previously created. When selected, the window displayed in Fig. 15.33 will appear. Select the indicators you want to delete by flagging the checkbox and move them in the right section with the arrow; then push the button


.

410

410/480

5/24/2018


Fig . 15.33

15.5.4 Export Indicator This operation allows exporting indicators defined in a MUSA installation to another MUSA installation. When selected, the window displayed in Fig . 15.34 will appear. Select the indicators that you want to export and push the

button.

Choose the pathwill where you want to save the indicators definition four files extension .upa be created. You can then copy these files onand another PC with and import the indicator definition in another MUSA installation running on this PC (see section 15.5.5).


411

411/480

5/24/2018


Fig . 15.34

15.5.5 Import Indicator This function allows importing in a MUSA installation Indicators that have been defined on another MUSA installation. When selected, the window displayed in Fig.

15.35 will appear. Push the button and a new window will be opened. Find the path where the exported Indicators have been saved (that is, the files – with extension .upa - previously generated with the Export Indicators function) and select the folder. The Import window will be populated with all the Indicators available for the import (see Fig 15.36 ). You can tick the Indicators that you want to import among all the available ones and finally push the button


.

412

412/480

5/24/2018


Fig . 15.35

Fig . 15.36

15.4.6 Add Indicator to UMR Version This operation allows copying an indicator (KPI or Aggregate) defined for a certain UMR version in another UMR version. When selected, the window displayed in Fig. 15.37 will appear.


413

413/480

5/24/2018


Fig . 15.37 Here you have to choose the Start UMR Version (where the indicators already exists) and the New UMR Version (where you want to create a copy of the indicator). Then tick all the indicators that you want to copy in the left window, push the right arrow to move them in the right window and finally push the button . After the copying operation remember to check the indicators formulas since some of them may be changed from a release to another one.

15.5.7 View Indicator This operation allows to view all the characteristics of a system indicator, that is of an indicator (KPI or aggregate) provided with the MUSA installation and that cannot be modified by the user maintaining the same name. When selected, the window displayed in Fig . 15.38 will appear. By double-clicking on the indicator name or by selecting the indicator and pushing the window displayed in Fig . 15.39 will be opened. All the information on the indicator are shown in this window, included the indicator formula. The information on the allowed aggregations are accessible by pushing the button


.

414

414/480

5/24/2018


Fig . 15.38

Fig . 15.39


415

415/480

5/24/2018


By pushing the button (see Fig . 15.40 ) the indicator name will be modified as IndicatorName_Usr and it will be possible to modify and save the characteristics of the indicator.

Fig . 15.40 For the description of the procedure for the modification of the indicator please refer to section 15.5.1.

15.5.8 Indicator Analyzer This function is the core module of the PM Counter Analyzer and allows to generate the reports according to a selected template. When selected, the window displayed in Fig. 15.41 will appear. Select the template that you want to generate. A new window will be opened (see Fig . 15.42 ).


416

416/480

5/24/2018


Fig . 15.41 The section on the upper right side (General ) resumes the main information of the selected template (name, version, default aggregations, eventual filters). The field Area will be filled up in case the Network Element aggregation will be changed to area (see section 15.7 for defining the area aggregation), whereas the fields Start Time and End Time allows to restrict the investigation on a limited period of time. By default the Start Time is the start time of the oldest measurement imported and the End Time is the actual date. The checkbox “Only data with Suspect Flag 0” will be checked in case the proper option is chosen in the Aggregation Options panel or in the general Options panel. The field Busy Hour Indicators will be filled up with the name of the indicator chosen as Busy Hour Indicator in case a Busy Hour Report will be generated (see the Aggregation Options section further in this paragraph on how to obtain a Busy Hour Report). Moreover, by clicking on the pin on the top-right corner of the General window it is possible to activate an auto-hide function in order to enlarge the window space available for displaying data. The section on the left side (Network Elements ) shows the network structure in a “tree” format where the root are always the RNCs and the “leaves” can be cells, NodeBs, adjacent RNCs, ATM Line (→ ATM VP → ATM VC) depending on the type of template selected. Again, by clicking on the pin on the top-right corner of the Network Elements window it is possible to activate an auto-hide function in order to enlarge the window space available for displaying data. The Error List window is normally hidden and is activated in case an error occurred during the report generation,


417

417/480

5/24/2018


Fig . 15.42 Finally, on the top of the described windows there is a bar with the nine icons reported in Fig . 15.43 .

Fig . 15.43 The function of each icon is as follows: •

: to close the Indicator Analyzer window Close

•

: to select another template Change Tem plate

•

Aggregation Options: to modify the Aggregation Options of the template

•

Calculate : to launch the query on the data

•

Next data: in order to earn calculation time, if the report exceeds 5000 rows, the first 5000 rows will be calculated and visualized. The next 5000 rows will be calculated and visualized only after pushing this button. The button is grayed out if the number of rows in the report is less than 5000.

•

Previous data: to calculate and visualize the previous 5000 rows

•

Excel Export: to export the result of the query in Excel format


418

418/480

5/24/2018


•

CSV Export: to export the result of the query in CSV format

•

Stop: to stop in any moment the query on the data

NOTE: In Excel and CSV export there isn’t the 5000 rows limitation. Anyway, in case the number of rows will exceed 60000, the Excel export will be split in more than one file with a three digit increasing suffix. This icon is very important since it allows modifying in “real-time” the Time and/or Network Element aggregations without defining a new template. When you click on the icon a new window is opened in which there are tree tab menu: -

the Current aggregations tab menu (Fig. 15.44 ): it allows to modify the default Network element aggregations and the Time aggregations. Note that Network Element aggregations it is of possible to choose Area in orderintothe limit the analysis to particular clusters cells that will be selected through the Area tab menu. In case the Time Aggregation None is chosen an average value obtained considered all the data present in the database will be returned. After having modified the aggregation options the user is requested to save it and shall click on icon (query launch) in order to obtain the new report. When a report on an Area basis is generated, it will appear the name of the Area in the area field with green color and in the right side of the window will appear only the cell id that composes this cluster;


419

419/480

5/24/2018


-

the Current Filter tab menu (Fig . 15.45 ): it allows modifying the default time filtering in order to exclude from the calculation some hours of the day or some days of the week. It allows also generating a Busy Hour Report by selecting a proper Busy available Busy Hour report will return forHour eachindicator Network among Elementthe selected theones. valuesA of the KPIs/Aggregates calculated in the hour of the day when the Busy Hour indicator reaches the maximum value for each network element (in case the maximum value is reached in more than one hour, the busy hour is selected as the closest to 24:00). Finally, in this window the user can decide to include in the calculation performed by the query only the valid data (Suspect Flag = 0; it’s a flag that is set to 1 by the RNC if during the granularity period a cell restart occurs) or all the data. The default setting will include all the data.

Fig . 15.45 -

the Area tab menu (Fig. 15.46 ): it allows defining on which area the query will be executed (see 15.7 for defining the area aggregation ).


420

420/480

5/24/2018


Fig . 15.46 NOTE: when the Area aggregation is chosen each line of the generated report will contain the indicators aggregated considering all the cells that compose the area. It is possible also to have the values of the indicators for each cell that compose the area, by changing back the Aggregation Options to Cell while keeping the area filter active (the Field Area will have a green background and the area name will be displayed inside it). It is possible to visualize an area already created and to define a new area directly in this window. In the first case, click on the area name with the mouse right button ( Fig . 15.47 ) and choose View Area. It will appear the list of the NodeB that compose this area.


421

421/480

5/24/2018


Fig . 15.47 In the second case click anywhere inside the window with the mouse right button and choose New Area. The window displayed in Fig . 15.48 will appear. Create the New Area selecting the cell(s) that should be included in the new area from the Network Elements displayed on the right, assign a Name to the new area and click the button .


422

422/480

5/24/2018


Fig . 15.48 As an example, in Fig 15.49 is shown the Busy Hour report generated for a subset of cells belonging to the Area named “Manual” having chosen as a Busy Hour indicator the KPI trafLoad_CS.

Fig . 15.49

15.6 Menu Batch A nalysis By clicking on the down-arrow besides the Batch Analysis icon (Fig . 15.50 ) it is possible to access to the operation available within the Batch analysis menu.


423

423/480

5/24/2018


Fig . 15.50

15.6.1 New Analysis This operation allows defining a new Batch analysis. A Batch Analysis is an automatic process that imports counters from a specified directory and generates automatically selected of reports. It is useful for athe bigwindow amountdisplayed of data that can be processed aduring the set night’s hours. When selected, in Fig. 15.51 will appear. It is necessary to specify the Batch Analysis Name , the File Type of the binary files that will be imported, the UMR version it refers to, an optional Description and the Import Mode .

Fig . 15.51 It is possible to choose between two different Import Modes; if Import only the indicators o f the selected class (Fig. 1 5.52) is selected a new tab menu that allows to choose the classes to import will be displayed; on the other hand all the classes will be imported.


424

424/480

5/24/2018


Fig . 15.52 Finally, the tab menu Templates Selection (Fig. 15.53) allows selecting the templates that will be generated automatically.

Fig . 15.53


425

425/480

5/24/2018


Push the button

and the Batch Analysis will be saved.

15.6.2 Edit Analysis This operation allows to see the list of all the defined Batch Analysis with the following information (Fig . 15.54 ): -

UMR version

-

File Type

-

Batch Analysis name

-

Batch Analysis description (if filled during the creation)

Choose the Batch Analysis you want to modify and open it by double-clicking on it with the mouse or pressing the button

.

Fig . 15.54 Then modify and/or correct it in the same way as described in paragraph 15.6.1 (see

Fig. 15.55 ). Finally press the button


to save the changes applied.

426

426/480

5/24/2018


Fig . 15.55

15.6.3 Delete Analysis This operation allows to delete Batch Analysis previously created. When selected, the window displayed in Fig . 15.56 will appear. Select the Batch Analysis you want to delete and push the button


.

427

427/480

5/24/2018


Fig . 15.56

15.6.4 Execute Analysis This function allows defining a sequence of Batch Analysis that has to be executed.

15.57 When selected, the the window displayed in Fig. will appear. Initially, it is necessary to specify file format of the report (.xls or .csv).

Fig . 15.57


428

428/480

5/24/2018


By clicking anywhere inside the white part of the window with the mouse right button it is possible: -

to define e New Batch Execution

-

to update an existing one (if there is any existing)

-

to delete an existing one (if there is any existing)

When “New Batch Execution” is selected the window in Fig . 15.58 is displayed. The fields that shall be filled up are: -

UMR Version: the UMR version the Batch Analysis refers to; Project: all the available projects for the specified UMR version will be shown in a drop-down menu (the Project must have been created previously). Choose the Project on which you want to run the Batch Analysis

-

Batch Analysis: all the available Batch Analysis (that will specify the modality of import and the reports that must be generated) created for the selected UMR Version will be shown in a drop-down menu. Choose the Batch Analysis you want to run. Input Folder: the directory where the binary files that will be imported are located Output Folder: the directory where the generated reports will be saved

-

The fields that can be optionally filled up are: -

-

-

Area: all the available areas will be shown in a drop-down menu (the Areas must have been created previously, see section 15.7 for defining the area aggregation). Choose the Area on which you want to run the Batch Analysis. If an Area is selected but the Area Aggregation checkbox is not ticked the report will be generated on a cell basis considering only the cells that belong to the specified area Area Aggregation: you must check the checkbox in case you want that the report is generated aggregating the data on an area basis. In this case it is also necessary to specify the Area in the field Area Generate templates only in Busy Hour: when the checkbox is ticked a Busy Hour report will be generated. In this case it is also necessary to select the Busy Hour indicator among the available ones in the Indicator drop-down menu


429

429/480

5/24/2018


Fig . 15.58 Push the button to include the Batch Analysis Execution in the list of the ones that you want to run (see Fig . 15.59 ).


430

430/480

5/24/2018


Fig . 15.59 After having selected an existing Batch Execution, by clicking on it with the mouse right button it is now possible to update it (the window in Fig . 15.60 will be opened) or to delete it (a confirm message will be displayed).


431

431/480

5/24/2018


After having completed the list of all the Batch Analysis that you want to run, push the button and the Batch Analysis are launched. The progress and the results will be shown in the Log window (Fig. 15.61 ).

Fig . 15.61

15.7 Menu Area By clicking on the down-arrow besides the Area icon (Fig . 15.62 ) it is possible to access to the operation available within the Area menu.

Fig . 15.62

15.7.1 New Area This function allows defining a cluster of cells on which it will be possible to restrict the analysis. When selected, the window displayed in Fig . 15.63 will appear. The fields that must be filled up are:


432

432/480

5/24/2018


-

Name : is the name of the new area (mandatory) File Type : RNC or NodeB PM File

-

Description: you can optionally insert a short description for the new area

-

Class: in the actual MUSA release only areas of Cells can be created

A txt file with the list of the cells that will compose the cluster must have been previously prepared. The structure of the txt file for area definition is a sequence of rows containing the fields rncId and CellId separated by a comma. The following example shows the content of the txt file for a cluster of three cells (cellid: 1268, 1269, 1270) belonging to rncid=3: 3,1268 3,1269 3,1270 By pressing the button a new window will allow to choose the txt file with the area definition. After having selected it the list of the cells that compose the area are displayed in a tree structure in the right side of the window of Fig . 15.63 .

Fig . 15.63 Finally click on

button for saving the Area.

NOTE: It is possible to define a New Area also directly from Indicator Analyzer (see section 15.5.7).

15.7.2 Edit Area This operation allows seeing the list of all the defined Areas with the following information (Fig . 15.64 ):


433

433/480

5/24/2018


-

Class

-

File Type

-

Area Name

-

Area description (if filled during the creation)

Choose the Area you want to modify and open it by double-clicking on it with the mouse or pressing the button . The same window as in Fig . 15.63 will be opened. After having modified the area definition, click on

button.

Fig . 15.64

15.7.3 Delete Area This operation allows deleting Areas previously created. When selected, the window displayed in Fig . 15.65 will appear. Select the Areas you want to delete and push the button

.


434

434/480

5/24/2018


Fig . 15.65

15.7.4 Export Area This operation allows exporting Areas defined in a MUSA installation to another MUSA installation. When selected, the window displayed in Fig . 15.66 will appear. Select the Areas that you want to export and push the

button. Choose

the path You where you want to save and two extension .upa will be created. can then copy thesethe filesAreas on another PCfiles andwith import the Area definition in another MUSA installation running on this PC (see section 15.7.5).


435

435/480

5/24/2018


15.7.5 Import Area This function allows importing in a MUSA installation Areas that have been defined on another MUSA installation. When selected, the window displayed in Fig. 15.67 will appear. Push the button and a new window will be opened. Find the path where the exported Areas have been saved (that is, the files – with extension .upa previously generated with the Export Areas function) and select the folder. The Import window will be populated with all the Areas available for the import (see Fig 15.68 ). You can tick the Areas that you want to import among all the available ones and finally push the button

.

Fig . 15.67


436

436/480

5/24/2018


Fig . 15.68

15.7.6 View Area This operation allows seeing the list of all the defined Areas with the following information (Fig . 15.69 ): -

Area name

-

Area description (if filled during the creation)

-

Class

By clicking on one row with the right mouse button a new window will be opened displaying in a tree view the cells that compose the area (see Fig . 15.70 ).


437

437/480

5/24/2018


Fig . 15.70

15.8 Menu Task By clicking on the down-arrow besides the Task icon (Fig . 15.71 ) it is possible to access to the operation available within the Task menu.

Fig . 15.71

15.8.1 New Task This operation allows defining a new Task. A Task is a scheduled operation that is executed automatically at a pre-defined time frame, provided that the MUSA PM Counter Analyzer module is running. When selected, the window displayed in Fig. 15.72 will appear. The fields that must be filled are: -

Name: the name that is assigned to the new Task

-

Description: an optional description of the Task

-

UMR version: the UMR version the Task is referred to


438

438/480

5/24/2018


-

Project: the name of the Project on which the Task will work

-

Type: the type of Task that will be created (the available ones in the dropdown menuonare: Files selected, Import, Templates Generation or displayed Batch Analysis ). Depending the Type different Tab menu will be

-

Start time: it’s the time when the scheduled Task will be executed for the first time

-

Schedule Task: allows to define the frequency with which the Task will be executed (the available ones in the drop-down menu are: Once, Every hour, Every day )

Fig . 15.72 In case Files import is chosen, MUSA will import automatically all the PM counter files in binary format contained in the specified input folder. In the Tab menu Import, select the input folder where the files are located (see Fig. 15.73). Also select the File Type of the PM counter binary files that will be imported (RNC PM files, NodeB PM files or both types) and the Import Mode (all the indicator classes or a selected subgroup of classes). In case a selective import is chosen, a


439

439/480

5/24/2018


new Tab menu is displayed (Classes Selection). In this window you can select the classes you want to import (see Fig . 15.74 ).

Fig . 15.73


440

440/480

5/24/2018


Fig . 15.74 Finally click on the

button to save the new defined Task.

In case Templates generation is chosen, MUSA will automatically generate the reports provided that some PM counter files have been already imported in the database. When Templates generation in the field Type is chosen, two new Tab menus will appear (see Fig . 15.75 ): -

Templates generation

-

Templates selection


441

441/480

5/24/2018


Fig . 15.75 In the Templates Generation Tab menu (Fig . 15.76 ) you have to select the Export mode (if Microsoft Excel or CSV format), the Output folder where the files will be saved, the File Type and optionally the Area (if you want to generate reports on a cluster of cells). In this case you can and choose the Area among all the ones listed in the drop-down menu Area and optionally tick the voice Area Aggregation in order to aggregate the results on an Area basis (otherwise the reports will be generated only for the cells of the Area). For the definition of an Area, see section 15.7. It is also possible to generate Busy Hour reports by ticking the checkbox Generate templates only in busy hours and selecting in the drop-down menu Indicator the Busy Hour Indicator.


442

442/480

5/24/2018


Fig . 15.76 In the Templates Selection Tab menu (Fig . 15.77 ) you must select the templates that MUSA will have to generate automatically.


443

443/480

5/24/2018


Fig . 15.77

Finally click on the


In case Batch Analysis is chosen, MUSA will execute both the operations described previously (Files Import and Report generation). When Batch analysis in the field ) Type is chosen, a new Tab menu Batch Analysis will appear (see Fig . 15.78


444

444/480

5/24/2018


Fig . 15.78 In the Batch Analysis tab menu (Fig . 15.79 ), select the Export mode (if Microsoft Excel or CSV format), the Batch Analysys that MUSA has to execute (a drop-down menu will list all the available ones for the previously selected UMR version), the File Type, the Input Folder where the PM counter binary files that must be imported are located, the Output folder where the files will be saved and optionally the Area (if you want to generate reports on a cluster of cells). In this case you can and choose the Area among all the ones listed in the drop-down menu Area and optionally tick the voice Area Aggregation in order to aggregate the results on an Area basis (otherwise the reports will be generated only for the cells of the Area). For the definition of an Area, see section 15.7. It is also possible to generate Busy Hour reports by ticking the checkbox Generate templates only in busy hours and selecting in the drop-down menu Indicator the Busy Hour Indicator.


445

445/480

5/24/2018


Fig . 15.79

Finally click on the


15.8.2 Edit Task This operation allows to see the list of all the defined Tasks with the following information (Fig . 15.80 ): -

UMR version

-

Task Type

-

Task Name

-

Description (if filled during Task definition)

-

Start Time

Choose the Task you want to modify and open it by double-clicking on it with the mouse or pressing the button . Depending on the Task Type, the same window as in Fig . 15.72, Fig. 15.75 or Fig. 15.78 will be opened. After having modified the Task definition, click on button.


446

446/480

5/24/2018


Fig . 15.80

15.8.3 Delete Task This operation allows deleting Tasks previously created. When selected, the window displayed in Fig . 15.81 will appear. Select the Tasks you want to delete and push the button

.


447

447/480

5/24/2018


15.8.4 View Task This operation allows seeing the list of all the defined Tasks with the following information (Fig . 15.82 ): -

UMR version

-

Task Type

-

Task Name

-

Description (if filled during Task definition)

-

Start Time

Fig . 15.82 Choose the Task you want to view and open it by double-clicking on it with the mouse or pressing the button . Depending on the Task Type, the same window as in Fig . 15.72, Fig . 15.75 or Fig. 15.78 will be opened, without the possibility to make any change in the settings.

15.8.5 Options In order to allow to MUSA to execute automatically a task it is necessary to check the flag Enable Scheduling (see Fig. 15.83 ). In the drop-down menu it is necessary to specify the frequency with which the scheduler will check if a new task shall be


448

448/480

5/24/2018


executed. If, after having enabled the scheduler, a task should already have been started the operation will be immediately executed, excluded the case where Once is selected in the task definition. In this case, if hour is selected, every hour will be checked the input folder and if there are some new file, all the tasks scheduled will be launched.

Fig . 15.83

15.9 Menu Tools By clicking on the down-arrow besides the Tools icon (Fig . 15.84 ) it is possible to access to the operation available within the Tools menu.

Fig . 15.84

15.9.1 Options This operation allows modifying General Settingsinfor the MUSA Counter Analyzer module. When selected,some the window displayed Fig. 15.85 will PM appear. This window has two Tab Menus: General and Visualization. In the General Tab Menu there are three areas: -

Working Folders: it is possible to set the default path for the PM binary files (Measurement report files path) and for the Excel/CSV reports (Microsoft Excel reports path);

-

Suspect Flag: it’s a radio button that allow to choose if either only PM Measurements with Suspect Flag = 0 shall be used for the query evaluation or all the measurements shall be used. This setting will be always applied for the report generation in the Batch Analysis and in the task type Templates Generation. It will also be used as a default in the Indicator Analyzer window


449

449/480

5/24/2018


but in this case it will be possible to modify the setting in the Aggregation Options window (see section 15.5.8) -

Scanner Tracing: by ticking the checkbox the Scanner Tracing function (see section 15.9.3) be itexecuted on the binary operation. In thiswill case is necessary to PM specify thefiles pathduring wherethe the File PM import binary files are located. Since this operation slow down the file import process (additional processing is needed on the binary files) it is strongly recommended to enable it only in case of need.

Fig . 15.85 In the Visualization Tab Menu there is only one area (see Fig . 15.86 ): -

Frozen Columns: by ticking the checkbox it is possible to fix the date and hour columns in the Indicator Analyzer window when scrolling it with the horizontal bar. As a result the first columns of the report (up to the column Hour To) will be always displayed even when many KPIs/Aggregate are calculated.


450

450/480

5/24/2018


Fig . 15.86

15.9.2 DB Shrink It allows reducing the project’s database dimensions. It is suggested to execute it regularly. When selected, the message displayed in Fig . 15.87 will appear.

Fig . 15.87

Push the button

for executing the operation.

15.9.3 Scanner Tracing This operation allows checking which PM counters are active by parsing the PM binary files. As a result a CSV file with the list of all the active scanners (PM


451

451/480

5/24/2018


measurement processes) will be generated. When selected, the window displayed in Fig. 15.88 will appear.

Fig . 15.88 Click on the button

to select the folder where the PM binary files

are located and on the button to select the folder where the CSV file will be saved. When the Input Folder is selected the window is populated with all the files present in the directory. All PM binary files named according to the 3GPP naming convention are displayed first and the most recent file that contains measurements end at midnight automatically formatted bold) if present that as displayed in Fig .is15.89 . In fact itselected is more(checked likely thatand a PM binary files that ends at midnight contains all the active measurements in case different granularity periods are chosen for different measurements. After clicking on the button the Scanner Tracing process is started and as a result a CSV file is generated. The CSV filename has the following naming convention:

__._ScL ist.cs v Where: -

: it can be RNC or NODEB depending on the PM binary File Type


452

452/480

5/24/2018


-

: is the Unique Id (according to 3GPP specifications) used in the PM binary filename to identify the Network Element

-

are the andbinary hour filename when the measurement .: collection is ended and extracted fromdate the PM

Fig . 15.89 In the Log Window tab is recorded the result of the Trace process. The CSV file contains a row for each scanner (measurement process) with the following fields: -

NE Id: Network Element ID, it can be the RNC Id or the NodeB Id

-

Timestamp: the End Date and End Time in the format YYYYMMDDHHMM

-

Granularity: the granularity period of the scanner; possible values are: 5, 15, 30, 60, 360, 720, 1440

-

Scanner Id: a progressive number associated to the measurement process. It is automatically assigned by the PM Counter Analyzer module and does not correspond to the ones used by the RNC in the scanner definition


453

453/480

5/24/2018


-

Scanner Type: the administrative object class. Possible values are: RNC, RNC CP, NODEB, CELL, ADJRNC, LINE, VP, VC

-

theare: ATM Line type; E1_MDTI it applies only to ATM measurements. Line Type: Possible values ST1, E1_DTI,

-

Line Unit: the ATM Line Unit; it applies only to ATM Measurements

-

VPI: the VPI value inside the ATM Line; it applies only to ATM measurements

-

Num Obj: the number of objects (i.e. number of cells, number of NodeBs, number of ATM VC) on which the measurement process is counting

-

Num Subcounters: the number of single raw measurements (subcounters) collected by the measurement process

-

MeasTypeNN: columns from MeasType1 to MeasType16 (16 is the maximum number of different measurement that a scanner can collect) contain the Short Name of the PM counters

In Fig 15.90 is reported an example of the CSV file opened with Excel.

Fig . 15.90


454

454/480

5/24/2018


16. MAIN TOOLBAR SINGLE BUTTONS It follows a short description of the MUSA main toolbar buttons: in Fig . 15.1 . it is shown the toolbar before any data loading..

Fig . 15.1 Fig. 15.2 shows the toolbar after the Scanner and Mobile measurements loading

Fig. 15.2 MUSA Main Toolbar buttons

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

Start Netwo rk Manger , to open the Network Manager window Cell Matchin g , to open the function window for Scrambling code alias decoding

Open Measurements , to open a Scanner and/or Mobile measurement file Export Tabbed Text… , to open Data Export window Clos e File, to close all previous loaded measurement files

Polygonal Cutting , to load only the Scanner and/or Mobile files data relative to the area delimited in a polygon previously created and saved for the selected project Maximum Number of Server , to limit the maximum number of detected server cells that could be loaded Load as Pixel , to start pixel processing for 3G files and 3G networks. General Pixelling proc edure , to start pixel processing for all kind of measurement files and systems. MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

455

455/480

5/24/2018


Statistical Mode , to enable Statistical Mode function Statistic Editor , to edit MUSA script files ( stat.txt and warning.txt files)

Time Charts, to open Time Charts tool window RSSI An alysis , to open RSSI Analysis time and pie charts Route Map, to open Route Map tool window Distribu tion and CDF, to open the Distribution and CDF window Joint Distribution, to open the Joint Distribution window Mobile Log File , to show the entire messages inside a mobile measurement log file. , to show all the cell neighbours relationships read in the Mobile Neighbo urs loaded Mobile measurement file

Mobile CS Table , to show automatic CS statistics and flow chart from the loaded Mobile measurement file

PM Counters A nalyzer, to load and analyze Network PM Counters binary files Coverage Simu lation, to load the parameter table for optimization and enable Optimization options Algorithms Simulations, to enable the SIM window and access the possibility to simulate network parameter changes in different scenes Neighb ou rs Analyzer , to open the Neighbours Analyzer tool Islands , to generate islands reports and graphs Pilot Pollution , to generate pilot pollution reports and graphs Cell Identity Card , to start the automatic Cell Identity Card generation procedure Coverage An alysis 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. Export to Google Earth , to create a KMZ file containing network sites, measurement, legend, etc.

, to synchronize all the opened windows Window Synch ronization , to display the opened windows with the Tile Horizontal format Tile Horizontal


456

456/480

5/24/2018


Tile Vertical , to display the opened windows with the Tile Vertical format , to display the opened windows with the Cascade format Cascade

License details. Details, to display license number, activated features and other A b o u t , to show Information about MUSA version Exit , to close MUSA


457

457/480

5/24/2018


17. APPENDIX


458

458/480

5/24/2018


APPENDIX A – SCANMAP DATA MUSA is able to manage geographic tables saved as scanmap files with the following properties: Datum:

See list in DatumID.xls contained in help subfolder

Projection:

Latitude/Longitude Universal Transverse Mercator (UTM) Transverse Mercator Gauss-Boaga Pulkova 1942 Gauss-Kruger Lambert Conformal Conic French Coordinate System

File format:

MS Windows Bitmap (plain or RLE) - 256 colors (8 bit depth)

Scanmaps are accessed through an index file (stored as ASCII text file). To correctly create this index file, the user could use GeoConverter tool.

UTM Example:

# Scanmap of Utopia # ED 1950 mean orientation referred to Postdam, UTM Zone: 32 DATUM 74 SYSTEM TM 32T METHOD 0 50225102.bmp 510000.0 50225142.bmp 514000.0 50225182.bmp 518000.0 50225222.bmp 522000.0 50265022.bmp 502000.0 50265062.bmp 506000.0 50265102.bmp 510000.0 50265142.bmp 514000.0 50265182.bmp 518000.0 50265222.bmp 522000.0 50265262.bmp 526000.0 50265302.bmp 530000.0 50305022.bmp 502000.0

514000.0 518000.0 522000.0 526000.0 506000.0 510000.0 514000.0 518000.0 522000.0 526000.0 530000.0 534000.0 506000.0

5022000.0 5022000.0 5022000.0 5022000.0 5026000.0 5026000.0 5026000.0 5026000.0 5026000.0 5026000.0 5026000.0 5026000.0 5030000.0

5026000.0 5026000.0 5026000.0 5026000.0 5030000.0 5030000.0 5030000.0 5030000.0 5030000.0 5030000.0 5030000.0 5030000.0 5034000.0

2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0 2.0

Index file may contain remarks beginning with the # character. It also may contain blank lines. The header section consists of the following reserved words: DATUM

followed by the Datum ID number. It indicates the geographic ellipsoid and its reference point. See list in DatumID.xls file contained in Help subfolder to identify the correct value to be used. Common values are: 1 for WGS 1984 or 74 for ED 1950 mean orientation. SYSTEM TM followed by a number and one character. The number indicates the UTM Zone (valid range: 1 to 60) and the letter indicates the UTM Designator (relevant only for the South Hemisphere, it can be omitted for the North) METHOD 0 Transformation Method (keep always to 0)


459

459/480

5/24/2018


Each field of the section uses a space character (ASCII code 32) as separator. After the header section there will be a row for each scanmap file with the following structure: Filename Minimum East Maximum East Minimum North Maximum North Meters per pixel

the scanmap bitmap file name without directory path. Minimum UTM East coordinate in meters. Maximum UTM East coordinates in meters. Minimum UTM North coordinates Maximum UTM North coordinates Resolution of the scanmap in meters per pixel (optional)

UTM North coordinates must be always positive: be sure to add the 10’000’000 false northing in the South Hemisphere.

Note about UTM System: UTM Zone from 1 to 60, valid latitude from -80 to +84 degrees


460

460/480

5/24/2018


APPENDIX B – HEIGHT DATA MUSA is able to manage height data saved in binary files with the following properties: Datum:

See list in DatumID.xls contained in help subfolder

Projection:

Latitude/Longitude Universal Transverse Mercator (UTM) Transverse Mercator Gauss-Boaga Pulkova 1942 Gauss-Kruger Lambert Conformal Conic French Coordinate System

Each file contains height of the ground above the mean sea level of a rectangular area. Data are stored in a binary array format, with each word of the array being 2 bytes in size. The most significant byte is stored first. Internally, the height data are arranged in a single continuous array: the first word read is the North West corner and the last element in the South East corner of the area. Words are ordered West to East and represent a square territory element, i.e. 50x50 or 25x25 meters. Binary files are accessed through an index file always named h_index.txt . To correctly create this index file, the user could use GeoConverter tool.

UTM Example: # Height of the ground above mean sea level # ED 1950 mean orientation referred to Postdam, UTM Zone: 32 DATUM 74 SYSTEM TM 32T METHOD 0 3246498t.bin 3250498t.bin 3246502t.bin 3250502t.bin

460000.0 500000.0 460000.0 500000.0

500000.0 540000.0 500000.0 540000.0

4980000.0 4980000.0 5020000.0 5020000.0

5020000.0 5020000.0 5060000.0 5060000.0

50 50 50 50

Index file may contain remarks beginning with the # character. It may contain also blank lines. The header section consists of the following reserved words: DATUM

followed by the Datum ID number. It indicates the geographic ellipsoid and its reference point. See list in DatumID.xls file contained in Help subfolder to identify the correct value to use . Common values are: 1 for WGS 1984 or 74 for ED 1950 mean orientation. SYSTEM TM followed by a number and one character. The number indicates the UTM Zone (valid range: 1 to 60) and the letter indicates the UTM Designator (relevant only for the South Hemisphere, it can be omitted for the North) METHOD 0

Transformation Method (keep always to 0)

Each field of the section uses a space character (ASCII code 32) as separator.


461

461/480

5/24/2018


After the header section there will be a row for each height file with the following structure: Filename Minimum East Maximum East Minimum North Maximum North Meters per pixel

the binaryUTM file name directory path. Minimum East without coordinates in meters. Maximum UTM East coordinates in meters. Minimum UTM North coordinates Maximum UTM North coordinates Resolution of the height square element (in meters)

UTM North coordinates must be always positive: be sure to add the 10’000’000 false northing in the South Hemisphere.

Note about UTM System: UTM Zone from 1 to 60, valid latitude from -80 to +84 degrees


462

462/480

5/24/2018


APPENDIX C – NETWORK FILES In order to create the network environment used by MUSA the user has to compile an UMTS excel file and optionally a GSM worksheet.

UMTS Network Excel File

Worksheet description Black-title-columns are mandatory. Blue-title-columns can be ignored. MUSA checks the column titles while the column order is not important. Data must start from the third row (second line is ignored by the program). RNC_ID and CELL_ID column data should match with internal OFD/ACL files entities (See Siemens RNC Files Appendix). Coordinates can be inserted as latitude and longitude in decimal degrees (i.e. 45.875954) or in degrees, minutes and seconds separated by space character (i.e. 45 32 24.872) or in UTM North and East coordinates. Heights should be inserted in meters from the ground level. Antenna names must be inserted with reference to the files contained in Resources\Aerials subfolder (see Aerial 3D Pattern Appendix). The correct name to be used in the excel files is in any case the filename without the final “_TE.3dd”.

Filename rules User should create the filename of the UMTS network file using the following format: ___ 3G __TM where YYYY MM DD Operator Town 3G

represent the Year (indicated with four characters) represent the Month (with two characters) represent the Day (with two characters) the operator name the town or area fixed reserved word


463

463/480

5/24/2018


Datum

WGS84, ED50, or the Datum numeric ID (See list in DatumID.xls contained in help subfolder). reserved word used to indicate UTMZone (mandatory only with UTM coordinates)

TM UTMZone

a number one 1character. Thethe number indicates the the UTM UTM Zone (validand range: to 60) and letter indicates Designator (relevant only for the South Hemisphere, it can be omitted for the North). It is mandatory only with UTM coordinates.

GSM network file uses the same rules but it is necessary to replace UMTS reserved word with GSM. Examples of valid filenames: 20050321_3GOP_UTOPIA_3G_WGS84.xls 20050321_3GOP_UTOPIA_3G_ED50_TM32T.xls 20050321_3GOP_UTOPIA_2G_169.xls

GSM Network Excel File

File Templates are included in MUSA Help\Network Templates subfolder.


464

464/480

5/24/2018


APPENDIX D – SIEMENS RNC FILES MUSA is able to manage Siemens RNC files stored in two formats: • OFD Files (UMR 2.0, 3.0, 3.5, 5.0, and 6.0): it can be saved from RNC

terminal with the view align dk command. • ACL Files (UMR 3.0, 3.5, 5.0, and 6.0): it can be saved from Siemens Radio

commander. Refer to Siemens Customer Documentation for more information.

Example of Siemens OFD File

Example of Siemens ACL File


465

465/480

5/24/2018


APPENDIX E – ANTENNA 3D PATTERN MUSA uses 3D aerial pattern for coverage simulation and optimization, created by NSN CoSite© 2.0 tool. Due to the high complexity of the 3D aerial pattern building, antennas files are managed only by Nokia Siemens Networks.

3D pattern aerial created by NSN CoSite © 2.0 tool

At the moment, the available 3D aerial patterns are: 18-65-C-VT-LSL 738445 738454 739489 741571 741784 741790 741794 741989 742149 742211 742212 742213 742215 742223 742226 742233 742234 742236 742241LS

742265 742266 742270 742271 742272 742290 80010137 80010270-2140-X-CO-M45 80010270-2140-X-CO-P45 A010UMTS Allgon7540 Allgon7580 Allgon7721 Allgon7750 Allgon7780 Allgon7785 APX15G215D215W2B APX15G215W2B APX206513 APX206515

742241US 742264

APX206516 APX18206515


BGD3800TV CMA6521 CSA-W3X72-14DBP 3G HBX6516DSVTM2110 MGD3800TV SA-2000-65-17MET-DS V50500-C1-A4172140-P45 YGI-T01381902 Racal2292 Isotropic

466

466/480

5/24/2018


Aerials are stored in Resources\Aerials subfolder as a “3dd” file format. There are several files for each model, one for each electrical tilt degree. For example: for Kathrein 741989 are available all this pattern files: 741989_TE0.3dd 741989_TE1.3dd 741989_TE2.3dd 741989_TE3.3dd 741989_TE4.3dd 741989_TE5.3dd 741989_TE6.3dd 741989_TE7.3dd 741989_TE8.3dd The correct name to be used in UMTS or GSM network excel file is in any case the string without the final “_TE.3dd” (See Network Files Appendix). In case new aerials will be [email protected].


required

by

the

projects

please

contact

467

467/480

5/24/2018


APPENDIX F – CELL IDENTITY CARD LOGO FILES For the creation of the Cell Identity Cards the application requires two bitmap logos: • Nokia Siemens Networks Logo (top left image) • Customer Logo (top right image)

170x60 pixels 140x25 pixels

Logo files must be bitmap with the above size, located under the \Environment\Logo subfolder of the current project. Logo files must be named NSNLogo.bmp and Customer.bmp


468

468/480

5/24/2018


APPENDIX G – INPUT SCANNER FILES MUSA is able to manage files coming from the following Scanner Equipment or Acquisition Software:

File type

Acquisition Software / Instrument

SGF (*.sgf)

MUSA dedicated scanner format

Pixel Files (*.pxl)

MUSA dedicated scanner format

StangaE files (*.se*)

NSN StangaE Tool (any version)

Agilent E6474A Export (*.txt)

Agilent E6474A (version: 6.0 to 9.2) Export can be made using the configuration file AgilentScannerForMUSA.epf contained in \Help\Agilent EPF subfolder.

Anritsu ML8720B (*.dat)

Anritsu ML8720B “Unspecified Long” format

Rohde&Schwarz export (*.txt)

See files contained in \Help\Scanner Examples folder.

Nemo Outdoor Scanner (*.fs*)

See files contained in \Help\Scanner Examples folder (version 4.14 – 4.19)

MapInfo Export (*.txt)

See files contained in Help\Scanner Examples folder.

TEMS Investigation 6.1 export (*.fmt) Only scanner events (UMTS data from rows with "Message Type" = "TOP N PILOT SCAN DATA MESSAGE", GSM data from rows with "Message Type" = "COLOR CODE AND CONTROL CHANNEL DATA MESSAGE"). Export can be made using the configuration file TEMS_Investigation61_Scanner+Mobile_U contained in MTS+GSMMusa_final.tex \Help\TEMS Investigation TEX subfolder. CSV Scanner file (*.csv)

csv file containing at least Time, Date, Lat, Lon columns. See files contained in Help\Scanner Examples folder.

Flash-OFDM FMDM/FMLP file(*.csv) See files contained in Help\Scanner Examples folder. DVB-H LG, N77, etc. File (*.txt)


See files contained in Help\Scanner Examples folder.

469

469/480

5/24/2018


APPENDIX H – INPUT MOBILE FILES MUSA is able to manage files coming from the following Mobile equipment or Acquisition Software:

File type

Acquisition Software / Instrument

Nemo Outdoor (*.dt*)

All Mobile Equipment traced with Nemo Outdoor (file format version 1.86)

Nemo Outdoor export (*.txt)

All Mobile Equipment traced with Nemo Outdoor (version 4.14 – 4.19). See files contained in \Help\Mobile Examples folder.

Nemo Handy Indoor file (*.dt*, *.mrk) Indoor measurement collected by Nemo Indoor. Agilent E6474A export (*.txt)

All Mobile Equipment traced with Agilent E6474A (version 6 to 8). Export can be made using the configuration file AgilentMobileHSDPAForMUS.epf contained in \Help\Agilent EPF subfolder.

ASKA export (*.txt)

NEC 606 VTX and 616 VTB equipment. See files contained in Help\Scanner Examples folder

MGF (*.mgf)


MUSA dedicated scanner format.

470

470/480

5/24/2018


APPENDIX I – WARNING SCRIPT FILE After measurement loading, MUSA executes the script file Warning.txt contained in the \Environment\Script subfolder of the current Project. By means of this file the Warning column of the MUSA data table is filled with the user defined messages. Each file row defines a warning message. It consists of POSITION field, LOGIC field, WARNING TEXT field, one or more DATA MESSAGE fields, separated by a TAB character. A “#” character can be used at the row beginning to include remarks. Blank lines are ignored.

Field Descrip tion POSITION: it can be • B = Begin, the warning message will be put at the beginning of the sequence • E = End, the warning message will be put at the end of the sequence

LOGIC: It can be • M = Match, the warning message will be inserted only if the sequence was

detected in the correct order • D = Deviation, the warning message will be inserted when a deviation from

the correct sequence was detected WARNING TEXT: the string inserted in the Warning field of the MUSA data table DATA MESSAGES: specify the sequence in the format : : .... where specify in which column the subsequent string must be found. Column name must be written as it is shown in the MUSA Measurement Data table specify the string value that must be found in the columns , as it can be read in the MUSA Measurement Data table. Example of Warning.txt file: #POS LOGIC WARNING_MSG COLS/STRINGS #------------------------------------------------------------------------------------#AGILENT 3G B M B M B M B M

T_3_A RRCMsg:RRCConnection Request Call Mode:UMTS 2T_3_A Cause:Originating Conversational Call Sok_3_A NASMsg:CC CONNECT ACKNOWLEDGE Mode:UMTS F_3_A Cause:Normal call clearing NASMsg:CC RELEASE

Mode:UMTS

#AGILENT 2G B M B M B M

T_2_A NASMsg:MM CM Service Request Mode:GSM Sok_2_A NASMsg:CC CONNECT ACKNOWLEDGE Mode:GSM F_2_A Cause:Normal call clearing NASMsg:CC RELEASE

Mode:GSM


471

471/480

5/24/2018


APPENDIX J – COVERAGE ANALYSIS PIXEL FILES This appendix gives a description of each column of the following .pxl files, resulting from the pixelling process (see Section 5.5): • Islands files (saved in …\\Results\Islands)

Sample of these files are:

islands 15_1_1.pxl islands 15_1_2.pxl islands 15_2_2.pxl • Polluted files (\\Results\PilotPollution\PP_Polluted.pxl) • Polluter files (\\Results\PilotPollution\PP_Polluter.pxl)

Islands Files Island .pxl files can be opened in MS Excel®, as shown in the figure below:

Prog Cell Prog Cell

The progressive pixel number Cell owner of the current island, written as : Island progressive number for the previous cell (it counts the island per cell)

The previous picture shows three islands belonging to the AL005U sector 3 cell.

Pixel dim Min_Join_Dist Min_Surface

Pixel dimension (in meters), as chosen by the user. Filter Distance criterion, as chosen by the user. Filter Surface criterion, as chosen by the user.

Surface dBm

Surface of the current island (in pixel units). RSCP island average value (in dBm).


472

472/480

5/24/2018


Centroid X Centroid Y Distance

UTM East Coordinate of the island center (meters). UTM North Coordinate of the island center (meters). Distance between island center and the Cell (owner).

PresCell1 PresCell1_Dist PresCell1_Recip_Dist

PresCell1_Diff PresCell1_NDiff PresCell1_NDiff_Perc

1st more present cell. Distance between PresCell1 and the current island Distance ratio: PresCell1_Dist and the distance between the Island and Cell (owner). A value < 1 indicates that PresCell1 does not correspond to Cell. Difference from Cell (owner) - average value in dBm. Difference Number: number of pixels where the PresCell1 is found in the island. Percentage of the previous value respect the island surface.

This group of columns are repeated several times, according to the user’s choice (Filter Cells parameter).

Polluted Files PP_Polluted.pxl file can be opened in MS Excel®, as shown in the figure below:

Prog Cell Scr Code Pixel dim Tot Pixel BS TotPixel_PP TotPixel_PP_Perc TotDifference_PP

Num_Tot_Cell_PP

Progressive pixel number. Polluted cell. Scrambling Code of the polluted Cell. Pixel dimension (in meters), as chosen by the user. Number of pixels where Cell is Best Server. Number of pixels where Cell is polluted (three or more other cells). Percentage ratio between TotPixel_PP and Tot Pixel . Differences, sum of the differences of each class; BS Total If two cells have an equal number of polluted pixels, the worst cell can be define using the highest Total_Difference _PP value. Number of polluter cells for this polluted Cell.

Class 1 Pilot Pollution information:

PP_fromM4_to4 PP_fromM4_to4_Perc MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

Differences in class 1 (usually from -4 to 4 dB) Previous value divided by TotDifference_PP , in %. 473

473/480

5/24/2018


PP_fromM4_to4_NumCell Polluter cells in class 1 PP_fromM4_to4_NumPixel Number of pixels where Cell is polluted in class 1. This section is also repeated for Class 2 (titles use 4 to 9 indication) and Class 3 (titles use 9 to 20 indication).

PP_fromM4_to4_Name_1 PP_fromM4_to4_Num_1 PP_fromM4_to4_Num_1_Perc PP_fromM4_to4_Dif_1

1st polluter cell in class 1 Differences due the previous cell in class 1 Previous value divided by TotDifference_PP , in percentage. Mean difference respect the Best Server (in dB).

This section is repeated for all polluter cells in Class1. After the Class 2 Pilot Pollution Information s ection, it is also repeated for all polluter cells in Class 2. Finally, after the Class 3 Pilot Pollution Information section, it repeated for all polluter cells in Class 3.

Polluter Files PP_Polluter.pxl file can be opened in MS Excel®, as shown in the figure below:

Prog Cell Scr Code Pixel dim Tot Pixel TotPixel_PP TotPixel_PP_Perc Num_Tot_Cell_PP

Progressive pixel number. Polluter cell. Scrambling Code of the polluter Cell. Pixel dimension (in meters), as chosen by the user. Number of pixels where Cell is measured. Number of pixels where Cell is polluter (the Cell is the fourth o more serving cell). Percentage ratio between TotPixel_PP and Tot Pixel. Number of Best Server cells polluted by this polluter Cell.

Class 1 Pilot Pollution information:

PP_fromM4_to4

Number of polluted pixels by Cell in class 1 (usually

PP_fromM4_to4_Perc

from -4 to 4 dB). Previous value divided by TotPixel_PP, in percentage.


474

474/480

5/24/2018


PP_fromM4_to4_NumCell Polluted cells, that is other Best Server cells polluted by this polluter Cell, in class 1 This section is also repeated for Class 2 (titles use 4 to 9 indication) and Class 3 (titles use 9 to 20 indication).

PP_fromM4_to4_Name_1 PP_fromM4_to4_Num_1 PP_fromM4_to4_Num_1_Perc PP_fromM4_to4_Dif_1

1st polluted cell in class 1 Number of pixels where the previous cell is polluted in class 1 Previous value divided by TotPixel_PP, in percentage. Average difference respect the Cell (in dB).

This section is repeated for all polluted cells in Class1. After the Class 2 Pilot Pollution Information section, it is also repeated for all polluted cells in Class 2. Finally, after the Class 3 Pilot Pollution Information section, it repeated for all polluted cells in Class 3.


475

475/480

5/24/2018


APPENDIX K – PM COUNTER ANALYZER CLASSES This appendix provides the list of the PM raw counters contained in each Class defined in the PM Counter Analyzer module. The list refers to UMR5.0, new counters added in UMR6.0 are highlighted in blue. The Classes defined are the following: -

Accessibility

-

ATM counters

-

CP counters

-

Drop

-

GSM Adjacent (inter-RAT)

-

Hard Handover

-

Iu Measurements

-

Iub Measurements

-

Iur Measurements

-

Other procedures

-

RAB Estab Fail (x RAB)

-

RAB Release Cn (x RAB)

-

RAB Release Utran (x RAB)

-

RL Estab Fail (x SF)

-

RNC Resources

-

Soft Handover

-

Traffic

-

UMTS Incoming Adjacent (intra-freq)

-

UMTS Outgoing Adjacent (inter-freq)

-

UMTS Outgoing Adjacent (intra-freq)

-

NodeB Counters (NODEB)

-

NodeB Counters (CELL)


476

476/480

5/24/2018


-

NodeB Counters (ATM)

-

NodeB Counters (HSDPA)

For counters naming that have the same the following convention is short used:name even if activated on different Objects -

-

-

if the measurement object can be CELL or ADJRNC: no modification are applied to the Short Name for the CELL measurements, whereas the suffix _R n c is appended to the Short Name for the ADJRNC measurements if the measurement object can be NODEB, ADJRNC or RNC: the suffix _Iu b is appended to the Short Name for the NODEB measurements, the suffix _ Iur is appended to the Short Name for the ADJRNC measurements, the suffix _Iu is appended to the Short Name for the RNC measurements

if the measurement object can be ATM LINE, ATM VP or ATM VC: the suffix _L ine is appended to the Short Name for the ATM LINE measurements, the suffix _VP is appended to the Short Name for the ATM VP measurements, the suffix _VC is appended to the Short Name for the ATM VC measurements

The complete list or the Short Name of the raw counters belonging to each Class is summarized in the following tables.

Accessibility1 paging1Cn rabEstabTypeFail rrcReEstabSucc paging1CnSucc paging2Cn rrcReEstabFail paging1UraUtran paging2CnSucc rbSetupFail pagingUraFail rrcEstabAtt rbReconfFail sigConnEstabReq rrcEstabSucc paging1CellUtran rcRejections rrcEstabFail pagingCellFail rabEstabTypeAtt rrcEstabdetailFail acRejections rabEstabTypeSucc rrcReEstabAtt ccTrigger rrcRepeatEstabAtt rbSetupAtt sigConnEstabSucc

lineIncomingCells lineOutgoingCells vpvcIncomingCells vpvcOutgoingCells

rlEstabAtt rlEstabSucc rlEstabFail rlReconfFail hsEstabAtt hsEstabFail cellUpdate uraUpdate

ATM Counters2 discardedCellsHecViolatio vcOutCells discardedCellsCongestion linevpdiscCellsCMP congestionOfVP vcMeasActCid linevpOutCellsCMP CP Counters3 rncUsageRatio Drop1

1 2 Counters

activated both on CELL objects and ADJRNC objects are considered All ATM counters activated on either ATM Line, ATM VP or ATM VC are considered The counters for all the RNC processors active are considered

3


477

477/480

5/24/2018


iuRelReq iuRelCmd rabRelUtranOrigin

rabRelCnOrigin rrcRelDcch rabRel

rrcRelCcch sigConnRelReq sigConnRelNotif

GMS adjacent (Inter-RAT) interRatHoOutRelocAtt interRatHoOutRelocFail interRatHoOutAtt interRatHoOutSucc interRatHoOutFail

hhoAllOutAtt hhoAllOutSucc

Hard Handover intraRNCHhoAttInc intraRNCHhoSuccInc

hhoAllOutFail

intraRNCHhoFailInc

interRatHhoSuccInc iRatHoPSUEOutSucc

Iu Measurements userThroughputIu hsprlcThroughputRate hsdstThroughputRate

lineAllocAtt lineAllocSucc alcapEstabFail

Iub Measurements userThroughputDCIub

lineAllocAtt

buildBandwidthIub bearerServiceusageIub

lineAllocSucc alcapEstabFail

Iur Measurements userThroughputDCIur

lineAllocAtt

alcapEstabFail

lineAllocSucc

transFromUraPchAtt transFromUraPchFail relocOutAtt relocOutSucc relocOutFail relocIncAtt relocIncSucc hsOutMobilityAtt hsServCellChgFail

Other Procedures transFromCellDchAtt transFromCellDchFail transFromCellFachAtt transFromCellFachFail transFromCellPchAtt transFromCellPchFail hsTranstoFachAtt hsOutMobilityFail

hsTranstoFachFail hsTransFromFachAtt hsTransFromFachFail phyChReconfAtt traChReconfSucc traChReconfFail radioLinkFail hsServCellChgAtt

RAB Estab Fail (x RAB)1 rabEstabFailpRab MUSA 4.6 User Manual http://slide pdf.c om/re a de r/full/musa -46-use r-ma nua l-v23

478

478/480

5/24/2018


RAB Release Cn (x RAB)1 rabRelUCnOrigpRAB

RAB Release Utran (x RAB) 1 rabRelUtranOrigpRAB

RL Estab Fail (x SF) rlEstabFailSF

RNC resources dhtUsage dhtAllocAtt dhtAllocSucc dhtBusyRate hsprlcUsageRate

dhtBusyTime prlcUsage prlcAllocAtt prlcAllocSucc hsdstUsageRate

shoAddInterRncAtt shoAddInterRncSucc shoAddInterRncFail shoAddDriftingUeSucc

uuTransmCarrierPwr uuRecTotalWbPwr transmrecPwrperRL uuCodeReqAtt uuCodeReqSucc

prlcBusyRate prlcBusyTime m2cAllocAtt m2cAllocSucc

hsprlcAllocAtt hsprlcAllocSucc hsdstAllocAtt hsdstAllocSucc

Soft Handover 1 shoAddIntraNodeBAtt shoAddIntraNodeBSucc shoAddIntraNodeBFail shoAddIntraRncAtt

shoAddIntraRncSucc shoAddIntraRncFail shoDelAtt shoDelSucc

Traffic uuCodesUsed uesPerActiveLinkSetSize bearerServiceperCell brsEstabSuccperCell pchUsageRate

pchDiscardRate fachUsageRate fachDiscardRate fachTrafficPs uuNonHSDPATCPwr

UMTS Incoming adjacent (intra-freq) cellUpdateInc UMTS Outgoing adjacent (inter-freq) HhoOutAttACM HhoOutSuccACM HhoOutFailACM

UMTS Ougoing adjacent (intra-freq) shoMoveOutAtt shoMoveOutSucc shoMoveOutFail


479

479/480

5/24/2018


NodeB Counters (NODEB) cpUsageRatio bbUsageRatioHw

restOfCallCapacity bbUsageRatioLicense

NodeB Counters (CELL) sccpchUsageRatio

prachUsageRatio

prachMessages numberOfReceivingPreambles

prachCRCIFailures

NodeB Counters (ATM) egressCells

ingressCells

NodeB Counters (HSDPA) hsCodeUsageRatio hsNackRatio

hsCellThroughput hsBbUsageRatio

hsCqiReport

hsMacDiscardPdu

hsUserThroughput


480/480

Report "MUSA 4.6 User Manual v2_3"

Your name

Email

Reason

Description

Copyright © 2025 IDOC.TIPS. All rights reserved.
About Us | Privacy Policy | Terms of Service | Copyright | Contact Us | Cookie Policy

Sign In

Email

Password

Remember me Forgot password?

Our partners will collect data and use cookies for ad personalization and measurement. Learn how we and our ad partner Google, collect and use data. Agree & close

MUSA 4.6 User Manual v2_3

Recommend Documents