measurementvisualiser

8/8/2019 MeasurementVisualiser

1/50


2/50

Measurement Visualizer and OperationEnhanced Measurement Visualizer Radio Commander RC 8.5

A50023-X6009-A2-4-7619

Important Notice on Product Safety

Elevated voltages are inevitably present at specific points in this electrical equipment. Some

of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or

in property damage.

Therefore only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has

to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung.

Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu

Krperverletzungen und Sachschden fhren.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen

installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene

Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.

Trademarks:

All designations used in this document can be trademarks, the use of which by third parties

for their own purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2006Issued by the Communications GroupHofmannstrae 51D-81359 MnchenTechnical modifications possible.Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in awritten contract.


3/50

Operation Measurement Visualizer andRadio Commander RC 8.5 Enhanced Measurement Visualizer

A50023-X6009-A2-4-7619 3

Table of Contents

1 SOFTWARE SUMMARY ..................................................................................... 7

1.1 About Measurement Visualizer (MVI)................................................................... 71.1.1 Purpose ................................................................................................................ 71.2 About Enhanced Measurement Visualizer (EMV) ................................................ 71.2.1 Purpose ................................................................................................................ 71.3 Data handling ....................................................................................................... 71.4 Software Structure................................................................................................ 81.5 System Requirement ............................................................................................ 8

2 INSTALLATION AND SET UP OF SOFTWARE................................................. 9

2.1 Installation and Set-up of the Server .................................................................... 9

2.2 Installation and Set-up of the Client...................................................................... 9

3 GETTING STARTED.......................................................................................... 10

3.1 Get licence for MySQL ....................................................................................... 103.2 Import NodeB relations....................................................................................... 103.3 Set the input directory......................................................................................... 103.4 Set the import filter ............................................................................................. 103.5 Start the MVI client ............................................................................................. 11

4

SOFTWARE COMPONENTS ............................................................................ 12

4.1 The Server Part .................................................................................................. 124.1.1 Configuration of the Server................................................................................. 124.1.2 Backup and Restore Server Data....................................................................... 134.1.2.1 Backup................................................................................................................ 144.1.2.2 Restore ............................................................................................................... 144.2 The Client ........................................................................................................... 144.2.1 Measurement Visualizer menu bar..................................................................... 154.2.1.1 File menu............................................................................................................ 154.2.1.2 Edit menu ........................................................................................................... 154.2.1.2.1 Reload Object Browser....................................................................................... 15

4.2.1.2.2 Export ................................................................................................................. 154.2.1.2.3 Preferences ........................................................................................................ 164.2.1.3 Administration menu........................................................................................... 164.2.1.3.1 Define Reports.................................................................................................... 164.2.1.3.2 Define Bandfilter................................................................................................. 174.2.1.3.3 Manage Import Filters......................................................................................... 194.2.1.4 Help Menu .......................................................................................................... 194.2.1.4.1 User Manual ....................................................................................................... 194.2.1.4.2 About Measurement Visualizer........................................................................... 204.2.2 Client tool bar ..................................................................................................... 204.2.3 The Object Browser............................................................................................ 204.2.4 The Time Attributes ............................................................................................ 224.2.4.1 Start Date and End Date .................................................................................... 224.2.4.2 Band Filters ........................................................................................................ 22


4/50


4 A50023-X6009-A2-4-7619

4.2.5 Report Retrieval.................................................................................................. 234.2.6 Data table ........................................................................................................... 24

5 THE ENHANCED MEASUREMENT VISUALIZER............................................ 26

5.1 The main new features in the EMV .................................................................... 265.2 Installation and Set-up of the Server .................................................................. 265.3 Server side differences....................................................................................... 265.3.1 Threshold configuration...................................................................................... 265.3.2 Data directory prerequisite for the Import On Demand feature........................... 275.4 Client side differences ........................................................................................ 285.4.1 Main window differences .................................................................................... 285.4.2 Edit menu differences......................................................................................... 295.4.2.1 Refill Threshold Violation List ............................................................................. 295.4.2.2 Resume/Pause Threshold Violation Retrieval .................................................... 295.4.2.3 Stop Threshold Violation Retrieval ..................................................................... 30

5.4.2.4 Resume/Pause Report Retrieval ........................................................................ 305.4.2.5 Stop Report Retrieval ......................................................................................... 305.4.2.6 Reset Scalefactor to 100%................................................................................. 305.4.2.7 Modify Visibility Of Curves.................................................................................. 305.4.2.8 Export (changes) ................................................................................................ 305.4.2.9 Preferences (changes) ....................................................................................... 315.4.3 Administration menu differences ........................................................................ 315.4.3.1 Manage Import Filters (changes)........................................................................ 315.4.3.2 Define TimeBorder ............................................................................................. 325.4.4 Client tool bar differences................................................................................... 335.4.5 The Time Attributes differences.......................................................................... 345.4.5.1 The Time Check ................................................................................................. 345.4.5.2 Dynamic Report Retrieval................................................................................... 345.4.6 Upgrades in data representation ........................................................................ 345.4.6.1 Data table ........................................................................................................... 355.4.6.2 Coordinate system.............................................................................................. 365.4.7 Threshold Violation List ...................................................................................... 36

6 RESTRICTIONS................................................................................................. 39

6.1 No user and session management..................................................................... 396.2 Print limitations ................................................................................................... 396.3 Cell number limitation in reports ......................................................................... 396.4 XML input file restrictions ................................................................................... 396.5 Automatic deletion of NEs from Object Browser................................................. 39

7 TROUBLESHOOTING....................................................................................... 40

7.1 The object browser is empty right after start....................................................... 407.2 Connection to server lost.................................................................................... 407.3 Number of cells in the table is exceeded............................................................ 407.4 No data available in the MVI............................................................................... 407.5 Network problems............................................................................................... 40

8 APPENDIX ......................................................................................................... 41


5/50


A50023-X6009-A2-4-7619 5

8.1 Overview of GSM and UMTS RTPM KPIs:......................................................... 418.2 Predefined Key Performance Indicators (GERAN)............................................. 428.3 Predefined Key Performance Indicators (UTRAN) ............................................. 45

9 LIST OF ABBREVIATIONS............................................................................... 50


6/50


6 A50023-X6009-A2-4-7619

List of Figures:

Figure 1: The Measurement Visualizer main window ................................................................... 14Figure 2: The Report List dialog.................................................................................................... 16Figure 3: The Define report dialog ................................................................................................ 17Figure 4: The BandFilter List dialog .............................................................................................. 18Figure 5: The BandFilter Definition dialog..................................................................................... 18Figure 6: The Import Filter Manager dialog................................................................................... 19Figure 7: The About Measurement Visualizer dialog of the MVI................................................... 20Figure 8: The Object Browser ....................................................................................................... 21Figure 9: The start and end date selection area ........................................................................... 22Figure 10: The BandFilter selection area...................................................................................... 23Figure 11: The BandFilter Manager dialog.................................................................................... 23Figure 12: The Report selection area ........................................................................................... 24Figure 13: The Receiving Data dialog........................................................................................... 24Figure 14: The data table.............................................................................................................. 24Figure 15: The Enhanced Measurement Visualizer main window................................................ 28

Figure 16: The Threshold Violation Filter dialog ........................................................................... 29Figure 17: The Curvevisibility dialog ............................................................................................. 30Figure 18: Import On Demand dialog............................................................................................ 31Figure 19: The Time Check Interval List dialog............................................................................. 32Figure 20: The Define TimeBorder dialog..................................................................................... 33Figure 21: The TimeCheck field.................................................................................................... 34Figure 22: The Dynamic Update selection area............................................................................ 34Figure 23: The columns and headers of the data table................................................................. 35Figure 24: The graphical representation ....................................................................................... 36Figure 25: The Threshold Violation List ........................................................................................ 37


7/50


A50023-X6009-A2-4-7619 7

1 SOFTWARE SUMMARY

1.1 About Measurement Visualizer (MVI)

1.1.1 Purpose

The Measurement Visualizer (MVI) allows visualizing a limited amount of performancemeasurement data of selected network elements (NEs) within the Radio Commander. It providesa tabular presentation of the data with a history of up to 24 hours. Data from maximum 4 BSC, 50NodeB, and 2 RNC can be visualized simultaneously.

MVI is intended to offer a quick and easy status of the network performance to the user. Fordetailed analysis Siemens offers the extended version of the MVI called EMV described in thefollowing section.

1.2 About Enhanced Measurement Visualizer (EMV)

1.2.1 Purpose

The Enhanced Measurement Visualizer (EMV) is the extension of the previous application thatsupports also the graphical representation of the measurement data both historical data (pastdata) and dynamic data monitoring. The EMV also provides threshold violation list with customerdefined rules.

Please find all the additional features and their description in chapter5,THE ENHANCEDMEASUREMENT VISUALIZER. All the features described here are valid for the EMV as well.

1.3 Data handling

The MVI maintains an own data repository (indexed files). The measurement data will beretrieved from the RC file system as XML files for the BSC elements and as binary files for NodeBand RNC elements. Measurement data and objects older than 24 h are automatically removedfrom the system.

Only performance measurement data of maximum 4 BSC, 50 NodeB, and 2 RNC are uploadedinto MVI, in order to reduce the performance requirements on the RC. The NEs can bedetermined through an observing list that can be administrated through a GUI panel in MVI. TheNEs, the RC contains data of, are offered for selection in this GUI (in the Object Browser). If theselection is modified, MVI retrieves the data of the past 24 hours and starts uploading the data ofthe added NEs from that point of time on.

The data retrieval procedure is described in the following use case:

1. Start the Measurement Visualizer, seeStart the MVI client 3.5

2. Define a report, containing the required counters, see Define Reports 4.2.1.3.1.

3. Select the objects data should be retrieved for in the Object Browser, see The ObjectBrowser 4.2.3.

4. Define the start date, the end date and if desired the time, see Start Date and End Date4.2.4.1.

5. Select a predefined report (see point 1 there can be more reports defined they areoffered in a list), see Report Retrieval 4.2.5.

6. Click the Retrieve Reportbutton to get the data.


8/50


8 A50023-X6009-A2-4-7619

The data can be exported into CSV files for further evaluation in e.g. MS Excel, with a filter perNE.

1.4 Software Structure

MVI is realized as a stand-alone Java client-server application. The server and client are installedon the OMP and OMT respectively. After the installation of the server part on the OMP machine,the Measurement Visualizerbutton is available on the RC Applicationswindow. Any RC user mayaccess MVI.

1.5 System Requirement

The following hardware and software are required in order to run the MVI.

The server part has the same computer requirement as the Radio Commander OMP.


9/50


10/50


10 A50023-X6009-A2-4-7619

3 GETTING STARTED

Before the start of the MVI, it is necessary to perform a few compulsory configuration steps.These should be performed in the order of the appropriate sections below.

The home directory of the MVI is under the location:/export/local/OMC/SW/OMC/RUNNING/mvi

This directory can be reached easily by using the cd $SRE_RC/mvi command, in the following

this directory will be signed as .

3.1 Get licence for MySQL

The MySQL (http://www.mysql.com) database manager is a commercial 3rd party tool of the MVI.You need to obtain a license it in order to use the MySQL.

3.2 Import NodeB relations

Without the following step the tool has only a list of the NEs.

Import the NodeB relations to have the hierarchy of the NEs. Therefore perform the followingsteps:

1. Export the NodeB relations from RC via the Exportnodebrelations command in a CLIsession.

Detailed description of this command can be found in the RC Command Manual. The

export produces a file that has to be imported into the MVI. It is referenced

below.

2. Execute the configuration script to import the NodeB relations data into MVI:

[omc_plus@omp] > cd /scripts

[omc_plus@omp] > nbrelationsimport.pl

3.3 Set the input directory

Two input directories are needed:

1. The binary input directory to store the raw measurement data files (NodeB, RNC)

2. The XML input directory to store the XML format measurement data files (BSC)

Enter the corresponding values in the BinaryInputDirectory and XMLInputDirectory of

the configuration file /etc/visualizer.cfg.

For more details about the configuration of the tool see Configuration of the Server 4.1.1.

3.4 Set the import filter

Specify the NEs of the measurement data you are interested in by setting the import filter. Theperiodically started import server will import the data and calculate KPIs only for these NEs. Theimport filter is by default empty.

To set the import filter perform the following steps:

1. Start the MVI client, seeStart the MVI client 3.5.

2. Set the import filter, see Manage Import Filters 4.2.1.3.3.
http://www.mysql.com/http://www.mysql.com/http://www.mysql.com/


11/50


A50023-X6009-A2-4-7619 11

3.5 Start the MVI client

Click the Measurement Visualizerbutton in the RC Applicationswindow to open the MVI.

For troubleshooting see chapter7 TROUBLESHOOTING.


12/50


12 A50023-X6009-A2-4-7619

4 SOFTWARE COMPONENTS

This chapter describes the software components.

4.1 The Server PartThe main processes that make up the server part are the following:

Import server: It uses measurement data from the RC in the form of binary and XML files,stores the necessary data and calculates and stores the supported KPIs. It runspermanently.

Application server: It collects and forwards measurement data by request from the serverdatabase and binary files to the client. There will be an application server running for eachclient. On request by the user, sent via MVI client, the application server retrieves counterand KPI values, together with additional data.

4.1.1 Configuration of the Server

The /etc directory contains the configuration files of the MVI. They may be

changed as omc_plus user. After changing the configuration it will be made valid by the rerun of

particular configuration scripts or the import server depending on what has been changed:

Configuration file and the event after a change in it becomes valid

visualizer.cfg automatic rerun of import server

symboliccounterlist.cfg running configuration script symboliccounterimport.pl

symbolicnames.cfg running configuration script symbolicnameimport.pl

userdefinedviews.cfg running configuration script userviewimport.pl

The configuration scripts can be found under the directory /scripts. You may run

the .pl scripts in command line. Type simply the name of the script you want to run and it will

search in the default /etc directory for the default configuration files. You have also

the possibility to pass your own configuration file to a script by passing the filename as the firstargument.

What may be changed in the configuration is shown in the following list, where configurationparameters are represented by their default values. Lines beginning with hash mark (#) are

considered as comments, so they will be skipped and have no effect on the working of the tool atall. Be careful not to add whitespaces (space, tab, enter) before and after the name of a variable,

and after the equal sign. All configuration files can be edited as omc_plus user:

General settings in the configuration file visualizer.cfg:

o Base directories where the binary and XML files containing the raw measurement

data can be found in the [IMPORT] block.

This example contains the default input directories:

BinaryInputDirectory=

/export/local/OMC/DATA/OMP/PMG/binaryPmg

XMLInputDirectory=

/export/local/OMC/DATA/OMP/PMG/xmlPmg


13/50


A50023-X6009-A2-4-7619 13

o Base directory where the imported data files can be foundin the [GENERAL] block:

DataDirectory=/export/local/OMC/SW/OMP/RUNNING/mvi/data

o Switch on or off the pmpimport.luc (import server) and enable or disable the

import procedure.

# Switch on or off the pmpimport.lucEnableImportProcess=1

Symbolic names for counters and KPIs in the configuration filesymboliccounterlist.cfg.

In the example below the symbolic name mysymboliccountername is defined for the

counterdhtUsage.0:

#countername symbolicname

dhtUsage.0 mysymboliccountername

The symbolic names must not contain any white space character (e.g. space, tab).

Symbolic names for NEs in the configuration file symbolicnames.cfg.You can define symbolic names for UMTS MOCs (NodeB, RNC and their subnodes) andfor GSM MOCs as well (maybe different ones than the ones existing in the XML files). The

symbolic names can be exported from the RC by executing the Exportsymbolicnames

command.In the example below the symbolic names are defined for a NodeB:

NODEB:1004 "5th_District_NodeB"

NODEB:1004/LOCALCELLE:0 "CellNoOne"

NODEB:1004/LOCALCELLE:1 "CellNoTwo"

NODEB:1004/LOCALCELLE:2 "CellNoThree"

The symbolic names must not contain any white space character (e.g. space, tab).

User defined views for the object browser in the configuration fileuserdefinedviews.cfg.

You can define a view as a block in the file. The block name is the name of the view, andeach line of that block holds an object of that view.In the example below the view VIEW1 is defined with five objects:

[VIEW1]

RNC:4/STM1LINE:0.1.29.0/STM1VP:0



RNC:4/STM1LINE:0.1.29.0/STM1VP:5/STM1VC:0RNC:4/STM1LINE:0.1.29.0/STM1VP:5/STM1VC:3

After running the configuration script /scripts/userviewimport.pl as

useromc_plus the view VIEW1 will appear in the object browser containing a separate

hierarchy beside the view DEFAULT.

4.1.2 Backup and Restore Server Data

You can make a backup of the data used by the MVI server and use it again later after performinga restore. The data used by the MVI server comprises the data files containing the importedcounters and the calculated KPIs stored in the server database.


14/50


14 A50023-X6009-A2-4-7619

4.1.2.1 Backup

You can make a backup of the data used by the MVI server, if you start the following executable

as omc_plus user:

[omc_plus@omp] > /scripts/exportDataThis will collect the data into the file /export/measvis_export.tar.

4.1.2.2 Restore

To restore the previously exported data of an MVI server perform the following steps:

1. Copy the .tar file containing the data to be imported to the directory/import.

2. Start the executable /scripts/importData as omc_plus user.

After the restore your MVI server will have only the imported data. All former binary files are

removed and all database tables are dropped.

4.2 The Client

Start the Measurement Visualizerclient, see Start the MVI client 3.5.

Figure 1: The Measurement Visualizer main window


15/50


A50023-X6009-A2-4-7619 15

The Measurement Visualizermain window is divided into the following main areas:

The menu bar and the tool bar on the top

The side bar on the left

The data table for the tabular representation of reports

The data table is empty right after the start of the application. It can be filled with data bygenerating a report, see also Data handling 1.3.

The side bar contains the Object Browserand the selection areas. You can minimize, restore andmaximize the side bar by clicking on the arrows at the top of its border line. When the data tableis visible and you click on the upper arrow the side bar gets minimized, thus the data tableoccupies the whole window. If you click the lower arrow having this layout, the side bar getsrestored. By clicking the lower arrow again the Object Browseroccupies the whole window.

You can move the border line in finer steps as well by simply grabbing and moving it. The layoutchanged this way will be the one that the application returns to when the side bar is restored. Theside bar cannot be smaller than it requires for the visualization of the options it provides for the

user.

4.2.1 Measurement Visualizer menu bar

The menu bar contains the following main menus:

File

Edit

Administration

Help(on the right side)

4.2.1.1 File menu

The Filemenu contains the following menu item:

Logout

Select this menu item to close the application.

4.2.1.2 Edit menu

The Editmenu contains the following menu items:

Reload Object Browser

Export

Preferences

4.2.1.2.1 Reload Object Browser

The object tree is not refilled automatically.

Select this menu item to update the object tree. The current object tree will be downloaded anddisplayed in the Object Browser.

4.2.1.2.2 Export

Select this menu item to export data.

Export ReportSub menu item to save the tabular representation of the measurement report


16/50


16 A50023-X6009-A2-4-7619

Select this sub menu item to save the data as a CSV file (fields are separated by default with asemicolon, the customer may set the separating character in the Preferences) using a usual Savedialog.

4.2.1.2.3 Preferences

Select this menu item to set or change the preferences. Preferences

Change here the separator character of the CSV file (which is generated during the exportof the report).

4.2.1.3 Administration menu

The Administrationmenu contains the following items:

Define Reports

Define Bandfilter

Manage Import Filters

4.2.1.3.1 Define Reports

Select this menu item to list, modify, or remove already existing reports or to define a new report.The Report Listdialog opens.

Figure 2: The Report List dialog

The Report Listdialog displays the already defined reports in a tabular form. Each row representsa report. The left field of each row holds the name of the report, the right one lists the KPIs andcounters incorporate the report. The listed report may be selected in the Reportselection area in

order to narrow the retrieved values to the necessary KPIs and counters.Click the Addbutton on the right side to define a new report in the Define reportdialog.


17/50


18/50


18 A50023-X6009-A2-4-7619

Figure 4: The BandFilter List dialog

The BandFilter Listdialog displays the list of band filters already defined.

Click the Addbutton on the right side to define a new band filter in the BandFilter Definition

dialog.

Figure 5: The BandFilter Definition dialog


19/50


A50023-X6009-A2-4-7619 19

Specify the start and the end times of the band filter.

In the BandFilter Listdialog you can select only one band filter to manipulate by clicking it.Existing band filters may be removed or modified using the appropriate button on the right.Clicking the Modifybutton the same dialog opens as by clicking the Addbutton.

4.2.1.3.3 Manage Import Filters

Select this menu item to select NEs whose measurement data you are interested in. The ImportFilter Managerdialog opens containing three tabs.

Figure 6: The Import Filter Manager dialog

These tabs indicate the objects to be imported: the BSC, the NodeB and the RNC. They can befiltered separately. The NEs for which the raw data is already available but still not imported andfor which the KPIs are still not calculated are in the Outlist on the left.

Use the arrows to move the selected list item(s) from one list to the other and vice versa.

If some of them are moved to the Inlist, the next run of the import server will import the data ofthem and calculate the KPIs.

During the continuous run of the import server, reports can be retrieved for the NEs in the Inlist.

4.2.1.4 Help Menu

The Help Menu contains the following items:

User manual

About Measurement Visualizer

4.2.1.4.1 User Manual

Select this menu item to open this document. It is in the Portable Document Format, thus theAdobe Acrobat Reader is required to be installed on the machine where you are working.


20/50


20 A50023-X6009-A2-4-7619

4.2.1.4.2 About Measurement Visualizer

Select this menu item to open the About Measurement Visualizerdialog. This shows the propername and version of the client application.

Figure 7: The About Measurement Visualizer dialog of the MVI

Close this dialog by clicking the Closebutton.

4.2.2 Client tool bar

The tool bar contains shortcut icons to some of the menu items described above:

Reload Object Browser, described in4.2.1.2.1

Logout, described in4.2.1.1

Help, described in4.2.1.4

4.2.3 The Object Browser

The Object Browsercontains all the NEs for which data is contained by the measurement files. Itis an object tree that displays the type (folder or leaf) and the name of each node.

The object tree is not dynamic; to update the object tree use the Reload Object Browsercommand.


21/50


A50023-X6009-A2-4-7619 21

Note:In case of a symbolic name change or if the identifier of the XML file changes (CGID, FDN,symbolic name), it is possible that the old and new name are present in the object tree. Data areaccessible on the old object (before changing), and on the new object (after changing) as well.

Figure 8: The Object Browser

Each node that has one or more children has a folder sign ( ) before its name. You can expandthe next level of objects by clicking the switch sign ( ) before the folder. To contract a branch

you have to perform the same action on an expanded node ( ).Right after start only the root objects are visible, the level of their children or deeper levels are notexpanded. The root objects are the default and the user defined views. In the default view all theobjects are shown for which data is contained by the measurement files. In a user defined view asimplified structure may be defined having only the nodes the user needs, see also Configurationof the Server 4.1.1. It is not possible to remove nodes from any view via the Object Browser.

You can select one or more nodes the data will be retrieved for. It is possible to select singlenodes, groups of adjacently displayed nodes and sub-trees. The latter action can be performedby clicking the check box before folder nodes. By this action all descendants of the node and thenode itself get highlighted, hence selected.

The check box of a node is an indicator as well. It gives information about selected descendantsof the folder it belongs to. Three different cases can be distinguished by simply taking a look atsuch a check box:


22/50


22 A50023-X6009-A2-4-7619

If it is greyed out and selected, it means that not all, but at least one of the descendants ofthe folder are selected.

A non-greyed-out and selected check box indicates that all of the descendants areselected.

A deselected check box indicates that there is no selected node going down that branch ofthe object hierarchy.

This check box is very helpful, especially if the folder is contracted.

By clicking a non-greyed-out, selected check box, it turns to be deselected. By doing the samewith a greyed-out, selected check box, the grey-out will disappear.

4.2.4 The Time Attributes

The time period on the base of which the data will be retrieved from the server can be defined by:

The start date and the end date (defined in the Timeselection area)

A band filter (defined in the BandFilterselection area)

4.2.4.1 Start Date and End Date

After selecting one or more objects from the Object Browseryou have to select a time period inthe Timeselection area. The report about the selected nodes will be based on the date of thisperiod.

Figure 9: The start and end date selection area

Adjust the date using the calendar dialog. Adjust the time values either using the Hour/Minutedialog or by typing the proper hour and minute values.If you enter an improper value either for the hour or for the minute, the value will be set to the lastcorrect value.

4.2.4.2 Band Filters

Refine the time period on the base of which the data will be retrieved from the server in theBandFilterselection area.

Specify a time band of the previously defined time period to be considered at retrieval. Add one ormore band filters at the same time using the BandfilterManagerdialog.

Remove band filter(s) from the BandFilterselection area using the Removebutton in theBandFilterselection area.


23/50


A50023-X6009-A2-4-7619 23

Figure 10: The BandFilter selection area

Click the Addbutton to open the Bandfilter Managerdialog containing the list of all the band filtersdefined previously. For further information refer to Define Bandfilter 4.2.1.3.2.

Figure 11: The BandFilter Manager dialog

You can see the band filters already added on the right (in the Inlist) and all the others on the left(in the Outlist).


4.2.5 Report Retrieval

Select the report defining the KPIs and/or counters you are interested in from the list in the Reportselection area.


24/50


24 A50023-X6009-A2-4-7619

Figure 12: The Report selection area

The list of reports is retrieved from the server. The default selection is the first item of the reportlist. After retrieval the data table will represent the values of the KPIs and counters specified bythe selected report. For further information refer to Define Reports4.2.1.3.1.

Figure 13: The Receiving Data dialog

Click the Retrieve Reportbutton to trigger the retrieval and the report visualization

During retrieval an animated Progress Dialogopens with a counter of the already retrieved rowsand cells of the report table.

4.2.6 Data table

The data table provides a tabular representation of the report retrieved from the server. Each rowof the table shows the measurement data (KPI or counter values) of one of the previouslyselected NEs at a particular date and time.

Figure 14: The data table

The header of the table in the upper most line contains the following columns:

Date: indicates the date and time for which the KPI and counter values of the object are

shown in the rowformat: dd-mm-yyyy hh:mm:ss


25/50


A50023-X6009-A2-4-7619 25

Object:indicates the object identifier

KPIs and counters selected in the user defined reportThe counters are displayed with two digits at least, e.g. 2.00.

Note:

In the XML input file the PWRUPDW counters (SCANCHAN) are split in two lines. The data tableshows them in two lines as well.

Undefined counter values in the KPI formulas are considered as zero. A KPI may have no valueat a particular time and for a particular object, if its formula contains a division by zero. Undefinedcounter values and KPI values containing a division by zero are represented by an empty cell inthe data table.

By default the table is not sorted by the client of the MVI. The tabular representation contains allthe information in the order as it has been received from the server.

Click on of the column header right after report generation to sort the column by the values orright-click on the column header and select the sort order you want from the context menu.

Whether the direction of the sort was increasing or decreasing, it is indicated by the up or downarrow that appears at the right side of the column header. You may change the sort order anytime by clicking this arrow, or by selecting the corresponding item from the context menu thatappears after right-clicking the column header.

If you indicate the sort by either the Dateor the Objectvalues, the secondary key of the sort willbe the other one of the two. The sort order of both the primary and the secondary keys will be thesame. If you indicate the sort by any other column, there would not be any secondary key.


26/50


26 A50023-X6009-A2-4-7619

5 THE ENHANCED MEASUREMENT VISUALIZER

The Enhanced Measurement Visualizer (EMV) is the extended version of the MeasurementVisualizer. It is not installed by default to the RC, it must be ordered from Siemens AG. This partof the documentation describes all the differences between the MVI and EMV which are onlyfeature add-ons. All the features described for the MVI are valid for the EMV as well.

5.1 The main new features in the EMV

Graphical representation of measurement data

Threshold violation handling by means of user defined rules

Dynamic monitoring of data for defined objects and counters

Dynamic update of threshold violation list

Implementation of predefined KPIs

Conversion on demand of performance measurement data from the NE to a proprietaryformat

5.2 Installation and Set-up of the Server

You have to activate the EMV optional package via the CD of the EMV.

5.3 Server side differences

5.3.1 Threshold configuration

Edit the configuration file /etc/thresholdimport.cfg and run the perl script

/scripts/thresholdimport.pl to make the corresponding threshold violationsavailable:

[omc_plus@omp] > /scripts/thresholdimport.pl

At the very first run of this script the warnings may be misleading, so they have to be skipped.

User defined thresholds for generating threshold violations during import in the configuration filethresholdimport.cfg.

The format of threshold definitions can be illustrated by the following examples:

# countername thresholdvalue operator severity

dhtUsage.2 23000 GREATER major

rncUsageRatio.1 15 GREATER warning

vpvcOutgoingCells 300000 GREATER warning

vpvcIncomingCells 500000 GREATER minor

Each line is a tabular definition of a relation between a counter (in the 1st column) and a thresholdvalue (in the 2nd column). The relation operator has to be defined in the 3rd column, its possiblevalues are:

LESS

LESS_OR_EQUAL

EQUALNOT_EQUAL


27/50


A50023-X6009-A2-4-7619 27

GREATER

GREATER_OR_EQUAL

If the relation holds, a record will be generated with the severity defined in the 4th column.

Possible severity values are: warning, minor, major, critical.

You have to run the perl script /scripts/thresholdimport.pl to make thechanges available.

5.3.2 Data directory prerequisite for the Import On Demand feature

Base directories where the binary and XML files containing the raw measurement data can be

found in the [IMPORT] block The Import On Demand feature (see section5.4.3.1) works only if

the data in the input directories are also separated to subdirectories under the NODEB or RNC or

SBS directories.

For example:

.

|-- NODEB|-- RNC

`-- SBS

|-- 20050723

| |-- BR80_07.20050722234500.20050722235500-000.xml

| |-- BR80_07.20050723000000.20050723001000-000.xml

| `-- BR80_07.20050723001500.20050723002500-000.xml

`-- 20050724

|-- BR80_07.20050723234500.20050723235500-000.xml

|-- BR80_07.20050724000000.20050724001000-000.xml

`-- BR80_07.20050724001500.20050724002500-000.xml


28/50


29/50


A50023-X6009-A2-4-7619 29

5.4.2 Edit menu differences

The Editmenu contains the following new menu items:

Refill Threshold Violation List

Resume/Pause Threshold Violation Retrieval Stop Threshold Violation Retrieval

Resume/Pause Report Retrieval

Stop Report Retrieval

Reset Scalefactor to 100%

Modify Visibility Of Curves

The Editmenu contains the following changed menu item:

Export

Preferences

5.4.2.1 Refill Threshold Violation List

Select this menu item to refresh the threshold violation list. The Threshold Violation Filterdialogopens.

Figure 16: The Threshold Violation Filter dialog

You can select historical or dynamic threshold violation list retrieval.

Historical threshold violation list retrieval: Set the time interval of the historical retrieval. Thefirst 5000 records will be sent.

Dynamic threshold violation list retrieval: Select Activate Dynamic Update. The last 5000records are downloaded and displayed dynamically until you stop or pause this continuousupdate. New arrived data is shown after the import process has run by removing earlier records (ifthe 5000 limit is reached). For details see Threshold configuration 5.3.1.

5.4.2.2 Resume/Pause Threshold Violation Retrieval

Select this menu item to pause or to resume an ongoing dynamic threshold violation list retrieval.


30/50


30 A50023-X6009-A2-4-7619

5.4.2.3 Stop Threshold Violation Retrieval

Select this menu item to stop an ongoing dynamic threshold violation list retrieval.

5.4.2.4 Resume/Pause Report Retrieval

Select this menu item to pause or to resume an ongoing dynamic report retrieval.

5.4.2.5 Stop Report Retrieval

Select this menu item to stop an ongoing dynamic report retrieval.

5.4.2.6 Reset Scalefactor to 100%

Select this menu item to reset the graphical representation to its original size. The graphicalrepresentation shows the curves according to the data table again.

5.4.2.7 Modify Visibility Of Curves

Select this menu item to set which curves are visible. The Curvevisibilitydialog opens.

Figure 17: The Curvevisibility dialog

This dialog lists the names of the invisible curves on the left side (Invisiblelist) and the visibleones (Visiblelist) on the right side.


5.4.2.8 Export (changes)

Select this menu item to export data.


31/50


A50023-X6009-A2-4-7619 31

Export Threshold ViolationSub menu item to export the threshold violation list

Export CoordinationsystemSub menu item to export the graphical representation

5.4.2.9 Preferences (changes)

Select this menu item to set or change the preferences.

Legend on coordinationsystemSub menu item to show/hide the legend of the coordination system

5.4.3 Administration menu differences

The Administrationmenu contains the following changed menu item:

Manage Import Filters

The Administrationmenu contains the following new menu item: Define Timeborder

5.4.3.1 Manage Import Filters (changes)

Select this menu item to select NEs whose measurement data you are interested in for import ondemand. The Import Filter Managerdialog opens.

Figure 18: Import On Demand dialog


32/50


32 A50023-X6009-A2-4-7619

Select one object in the Outlist and click the Import on Demandbutton. The list of available filesopens. Select one or more files and click Okto save your changes. The selected files will beimported.

The Import On Demandfeature works only if the data in is stored in a directory with a specifiedform. See details Data directory prerequisite for the Import On Demand feature 5.3.2.

5.4.3.2 Define TimeBorder

Select this menu item to list, to define, to modify, or to remove the user defined time intervals forthe TimeCheck. The Time Check Interval Listopens.

Figure 19: The Time Check Interval List dialog

This dialog lists only the user defined time intervals not the predefined ones.

Click the Addbutton on the right side to define a new interval. The Define TimeBorderdialogopens.


33/50


A50023-X6009-A2-4-7619 33

Figure 20: The Define TimeBorder dialog

Specify Name, start time and end time of the interval.

In the Time Check Interval Listdialog you can select only one report to manipulate by clicking it.

Existing reports may be removed or modified using the appropriate button on the right. Clickingthe Modifybutton the same dialog opens as by clicking the Addbutton.

5.4.4 Client tool bar differences

Refill Threshold Violation List, described in5.4.2.1.

The four spots

The four spots indicate the state of the dynamic behavior.

The first two (from left) are belonging to the Dynamic Threshold Violation Retrievalthe secondtwo to the Dynamic Report Retrieval.

Note:The pairs are working the same way.

If the buttons are grey, the retrieval is historical.


34/50


34 A50023-X6009-A2-4-7619

If the first button is green, the dynamic update is ongoing (you may see the refreshing data tableor threshold violation list).

Click on the green button to pause the dynamic update (for example to export the data to CSV).The button turns to orange.

Click on the orange button to resume the dynamic update. The button turns to green again.

Click on the red button to terminate the dynamic update.

5.4.5 The Time Attributes differences

5.4.5.1 The Time Check

After selecting one or more objects from the Object Browseryou have to select a time period.You can specify the time period either manually (see 4.2.4.1) or using the TimeCheckfeaturecontaining predefined values. Without object selection the TimeCheckfield is disabled.

Figure 21: The TimeCheck field

The report data of the selected nodes will be retrieved only for the selected interval.

5.4.5.2 Dynamic Report Retrieval

This feature activates dynamic report retrieval.

Figure 22: The Dynamic Update selection area

If the Dynamic Updateis set, the TimeCheck, Start Time, End Timeand BandFiltervalues areneglected, only the last hour/minute data will be represented. If new data arrives, the values areshown after the import process has run.

5.4.6 Upgrades in data representation

After successful report retrieval it is displayed in the data table and the coordinate system. Thelatter one can be used to display only a part of the first.


35/50


A50023-X6009-A2-4-7619 35

5.4.6.1 Data table

Figure 23: The columns and headers of the data table

The column headers of the KPIs and counters have a check box, called the visibility flag, whichindicates whether their values are currently displayed in the coordination system. It is located onthe column header left to the column name. By default all KPI and counter values are shown inthe coordination system. Click this check box to remove the corresponding values from the

coordination system.

You can select the values of a particular KPI or counter to be the only visible one in thecoordination system. This is offered by an additional check box, called the solo button. The solobuttonis located on the header of each column below the visibility flag. By default the solo buttonis not set for any column. If you set it by clicking it, only the values of that KPI or counter aredisplayed in the coordination system. By clicking the solo buttonagain the graphicalrepresentation will get back to its previous state. By setting more solo buttonsone after the otherthe graphical representation will be narrowed to the values of their columns.

Right-click on the column header and select or unselect all columns you want from the contextmenu. It is the same context menu that offers the possibility to change the sort order.


36/50


36 A50023-X6009-A2-4-7619

5.4.6.2 Coordinate system

Figure 24: The graphical representation

The coordinate system provides a graphical representation of the generated report. Right afterthe data retrieval from the server it displays all the information contained in the data table.

The coordinate system displays curves based on this data. The resolution of the axes is alwaysadjusted to the prevailing minimum and maximum of the values displayed. If the visibility of thecurves is manipulated, the maximum and minimum values of the axes will be updated too. Eachpoint represents one KPI or counter value of one of the selected NEs plotted against date andtime. The points that represent values of the same KPI or counter of the same object are

interconnected with a curve.Coloring is used to make it easier to distinguish separate curves from each other. The assignmentof colors happens during retrieval, thus each curve retains its color for the time betweenconsecutive retrievals. You cannot change or influence the color of a curve. Each curve in thecoordinate system is given a different color, thus - especially having a sheer number of curves - itmay occur that few of them have very similar ones. A legend on the right side of the coordinatesystem indicates the mapping between curve names and colors.

The legend holds the relation between the colors of the curves and their names. Here you canalso change the visibility by clicking the check box on the right side.

5.4.7 Threshold Violation List

The second tab of the side bar is the Threshold Violation List. Fill the Threshold Violation Listbyusing the Refill Threshold Violation Listbutton on the client tool bar or using the correspondingitem in the Editmenu. The records are listed in a tabular form containing the following attributes:Severity, Counter, Object, Date.


37/50


A50023-X6009-A2-4-7619 37

Figure 25: The Threshold Violation List


38/50


38 A50023-X6009-A2-4-7619

The Threshold Violation Listis refreshed dynamically if the Activate Dynamic Updatecheck box isselected in the Threshold Violation Filterdialog. You can refill it any time you want. Click the RefillThreshold Violation Listbutton to open the Threshold Violation Filterdialog, see Refill ThresholdViolation List 5.4.2.1.

Select one or more records in theThreshold Violation List

to display the details in theThresholdViolation Detailsarea, but only of the 10 ones selected first. The order of the record descriptions

is the same as in the Threshold Violation List. If a threshold violation is selected and the data isavailable in the currently loaded report, the corresponding cell in the data table will be highlightedwith red.


39/50


A50023-X6009-A2-4-7619 39

6 RESTRICTIONS

The restrictions of the Measurement Visualizer are listed in the following topics.

6.1 No user and session managementThe Measurement Visualizer does not assign any IDs to client and application server pairs toidentify them as different sessions. There is no user management either.

6.2 Print limitations

Reports retrieved by Measurement Visualizer can be printed on paper only by exporting andopening them with other applications which offer the possibility for printing.For example:

Tables exported as CSV files can be printed using MS Excel

Graphical representations exported in the EMV as JPG files can be printed using an

image viewer application

No direct possibility is available in Measurement Visualizer to do it.

You have to import the exported CSV tables in MS Excel using the Data / Import menu item.Specify the field separator to the character which was set in the Preferencesdialog. For furtherdetails see Preferences 4.2.1.2.3.

6.3 Cell number limitation in reports

Not more than 100,000 cells can be displayed in the tabular representation of reports. If thenumber of cells retrieved reaches this limit the following warning message is displayed duringhistorical retrieval: The number of cells in the table is exceeded! and only the already retrieved

first 100,000 cells will be shown in the report. During dynamic update when the cell limitation isreached, the old rows are thrown out of the representation. For further details see Number of cellsin the table is exceeded section 7.3.

6.4 XML input file restrictions

The XML input files are generated normally with the RC. There is a possibility in the RC to set theformat of the object identifiers. It can be CGID, FDN or symbolic name. It is hardly recommendednot to change this setting for the XML files which should be imported together. Otherwise theobject will be represented in both names with the measured values divided according to the inputfiles which lead to inconsistencies.

6.5 Automatic deletion of NEs from Object BrowserThe MVI deletes automatically the NE from its tree representation, if no data are imported in thelast 24 hours for this NE and any of its sub-elements.

Click the Reloads Object Browserbutton in order to see the changes in the Object Browseron theclient side.


40/50


40 A50023-X6009-A2-4-7619

7 TROUBLESHOOTING

7.1 The object browser is empty right after start

The problem that may lay behind this symptom is that the connection between the client andserver of the Measurement Visualizer could not be established.

If there is a firewall or router between the client and server of the Measurement Visualizer, it hasto be configured so that the connection through the port XX is able to be used. This is the portneeded for CORBA communication.

Another circumstance that may cause the same problem is that the import of the measurementdata was not successful. Check that the configuration of the directory, where the rawmeasurement data files can be found, is correct. See details inConfiguration of the Server 4.1.1.

7.2 Connection to server lost

If the server of the Measurement Visualizer stops by some unknown reason, the following errormessage appears: The server is not accessible! In this case the client has to be restarted. Thecircumstances of the servers unexpected stop should be reported to the vendor.

7.3 Number of cells in the table is exceeded

The upper limitation for the number of cells in the tabular representation of the report is 100,000(for more details see Cell number limitation in reports 6.3). There are the following possibilities tochange the selections on the side bar to reduce the number of cells to be under limit:

1. Select less objects in the object browser

2. Select a smaller time interval

3. Select a different report with less KPIs and counters in it

7.4 No data available in the MVI

If no data are available in the MVI, check the EnableImportProcess entry in the

visualizer.cfg.

7.5 Network problems

In case of network problems starting the MVI client it may have been caused by a wrong IP filtersetting. Ask your system administrator if the machine where the MVI client runs is allowed toconnect to the one where the MVI server is running.


41/50


A50023-X6009-A2-4-7619 41

8 APPENDIX

Since all the observed RTPM indicators (KPI) are presented in ratio, it will be very useful also toprovide the absolute number of the related event to put a certain weight on the measured ratios.Therefore, it will be required also to report the number of sample value to each KPI.

8.1 Overview of GSM and UMTS RTPM KPIs:

Cate-gory

GERAN UTRAN Measurementdepth

Transmitted Carrier Power(Downlink Cell Load Rate)

per Cell

Capacity

Mean Combined Time SlotOccupation Rate for CS and POTraffic

Received Total Wideband Power(Uplnk Cell Load Rate)

per Cell

SDCCH Drop Rate RRC Connection Drop Rate per Cell

TCH Drop Rate CS Connection Drop Rate per Cell

Retain

Ability

TBF Drop Rate PS Connection Drop Rate per Cell

Assignment Failure Rate (orSDCCH Loss Rate)

RRC Connection Establ. FailureRate (or RRC Loss Rate)

per Cell

Immediate Assignment FailureRate (or TCH Loss Rate)

CS RAB Connection Establ.Failure Rate (or CS RAB LossRate)

per Cell

TBF Assignment Failure Rate (or

TBF Loss Rate)

PS RAB Connection Establ.

Failure Rate (or PS RAB LossRate)

per Cell

Accessibility

Call Setup Failure Rate Connection Setup Failure Rate(CS and PS combined)

per Cell

Hard Handover Drop Rate (intracell, intra RNC, inter RNC)

per CellHandover Drop Rate (intra cell,intra BSC, inter BSC)

Soft Handover Drop Rate (intracell, intra RNC, inter RNC)

per Cell

Hard Handover Failure Rate (intra

cell, intra RNC, inter RNC)

per CellHandover Failure Rate (intra cell,

intra BSC, inter BSC)Soft Handover Failure Rate (intracell, intra RNC, inter RNC)

per CellMo

bility

Outgoing Inter System HandoverFailure Rate

Outgoing Inter System HandoverFailure Rate

per Cell


42/50


42 A50023-X6009-A2-4-7619

8.2 Predefined Key Performance Indicators (GERAN)

The table shows the list of defined RTPM indicators sorted by categories. This table also containsthe formula of KPI calculation and the required PM sub-counters of SBS performancemeasurements.

Sub-counters of SBS performance measurements are listed in brackets with following meaning:

[1] sub-counter 1 has to be taken.

[1,2,4] sub-counters 1, 2 and 4 have to be taken.

[1..4] sub-counters 1,2,3 and 4 have to be taken.

[1..4,7..19] sub-counter 1,2,3,4,7,8,9 and 10 have to be taken.

[all] all sub-counters have to be taken.

Cate-gory

RTPMindicator(KPI)

Formula Meas.depth

Capacity

MeanCombinedTime SlotOccupationRate for CSand POTraffic

This KPI provides the mean occupation rate of those timeslots of acell, which can be assigned to users:

%100*NDefTS

NOcTSMeaOcTsC =

Number of samples = NDefTS

Where:

+

++=8/]1[2/]4,2[

]3,1[]6,3[MBUSYSDCMEBUSTCH

MEBUSTCHNALLPDCHNOcTS

+++

+=

8/]3[]1[

2/]12,6[

]9,3[]3[

NDESDCCHNDFTCHSD

NRDEFTCH

NRDEFTCHNDEFPDCH

NDefTS

perCell

SDCCHDrop Rate

This KPI provides the percentage of all drops of connections duringa SDCCH connection:

%100*]6..1[

]11,6,1[]26..23,21..19[

NSUCCHPC

TASSFAILNRCLRREQateSDCCHDropR =

Number of Samples = NSUCCHPC[1..6]

perCell

RetainAbility

TCH DropRate

This KPI provides the percentage of all TCH drops related to TCHconnection. A TCH may be seized during call setup and additonallyfor ahndover (including diracted retry):

%100*]2..1[

]18..14,12..5,3..1[

SUCTCHSE

NRCLRREQeTCHDropRat =

Number of Samples = SUCTCHSE[1..2]

perCell


43/50


A50023-X6009-A2-4-7619 43

Cate-gory

RTPMindicator(KPI)

Formula Meas.depth

TBF Drop

Rate

This KPI provides the total TBF drop rate (UL and DL combined).

Drops comprise all unsuccessful terminated TBF:

%100*]2,1[

]13..10,2,1[

SULACCEL

UNSTETBFTBFDropRat=

Number of Samples = SULACCEL[1,2]

per

Cell

SDCCHLoss Rate

This KPI provides the SDCCH traffic loss rate by meaning of therate where new SDCCH seizure attempts can not be handled,because all traffic channels (circuit groups) were occupied:

%100*]1[

]1[

NATTSDPE

ATSDCMBSateSDCCHLossR =

Number of Samples = NATTSDPE[1]

perCell

TCH LossRate

This KPI provides the TCH traffic rate by meaning of the rate wherenew TCH seizure attempts can not be handled, because all trafficchannels (circuit groups) were occupied:

%100*][

][][

allATTCHSEI

allNMSGDISQallATCHSMBSeTCHLossRat =

Number of Samples = ATTCHSEI[all]

perCell

TBF Loss

Rate

This KPI provides the TBF loss rate (UL and DL combined) by

meaning of the rate where new TBF request can not be handled,because for example no PDCHs were available:

%100*][

][

allNUACATCL

allREJPDASSeTBFLossRat =

Number of Samples = NUACATCL[all]

per

Cell

Accessibility

Call SetupFailureRate

This KPI provides the call setup failure rate by meaning the numberof call setup failure divided through the number of call setupattempts:

%100*

))100

1(*)100

1(*)100

Im1(1( eAssFailRatateSDCCHDropRtemAssFailRa

ailRateCAllSetupF

=

Number of Samples = NSUCCHPC[1..4,9..12,17..20] NSUCCHPC[8]

Where:

%100*][

]22..17,4..9,6..1[][Im

allATIMASCA

NSUCCHPCallATIMASCAtemAssFailRa =

%100*]3,2[

]22[]15,13..10,8..6[

TASSATT

NRCLRREQTASSFAILeAssFailRat =

%100*]6..1[

]11,6,1[]26..23,21..19[

NSUCCHPC

TASSFAILNRCLRREQateSDCCHDropR =

perCell


44/50


44 A50023-X6009-A2-4-7619

Cate-gory

RTPMindicator(KPI)

Formula Meas.depth

Handover

Drop Rate(intra cell,intra BSC,inter BSC,intersystemcombined)

This KPI privides the percentage of handover drops by meaning of

unsuccessful handover with loss of MS connection in specified cell:

%100*HOAtt

HODropsHODropRate =

Number of Samples = HOAtt

Where:

+

++=

][][

][][][

][]1[]1[

allUNOISHDOallSUOISHDO

allATOISHDOallNRUNINHDallSUINBHDO

allATINBHDOUNIHIRLCUNIHIALC

HODrops

+

++=][

][][][

allATOISHDO

allATINBHDOallATINHIRCallATINHIACHOAtt

per

Cell

Mobility

HandoverFailureRate (intracell, intraBSC, interBSC, intersystemcombined)

This KPI provides the percentage of handover faliures by meaningof unsuccessful handover without loss of MS connection because ofreversion to old cell in specified cell:

%100*HOAtt

HOFailsHOFailRate =

Number of Samples = HOAtt

Where:

+

++=

][

][][][

allUNOISHDO

allNRUNINHDallUNINHOIEallUNINHOIAHOFails

+

++=

][

][][][

allATOISHDO

allATINBHDOallATINHIRCallATINHIACHOAtt

perCell


45/50


46/50


46 A50023-X6009-A2-4-7619

CSConnectionDrop Rate

This KPI describes the ratio of abnormal UTRAN initiated Iuconnection releases related to the total number of CN initiatedconnection releases (per CS domain).

%100*_

__CSnInitNoofIuRelC

CSanInitalIuRelUtrNoofabnormCSIuCoDR =

Number of Samples = NoofIuRelCnInit_CS

With:

]119,62[= iuRelReqanInit_CSalIuRelUtrNoofabnorm]161[= iuRelCmdnInit_CSNoofIuRelC

Counter: iuRelReq.-iuRelCmd.-

perCell

Reta

inAbility

PSConnectionDrop Rate

This KPI describes the ratio of abnormal UTRAN initiated Iuconnection releases related to the total number of CN initiatedconnection releases (per PS domain).

%100*_

__

PSnInitNoofIuRelC

PSanInitalIuRelUtrNoofabnormPSIuCoDR =

Number of Samples = NoofIuRelCnInit_PS

With:

]2220,1716,1413[= iuRelReqanInit_PSalIuRelUtrNoofabnorm]3217[= iuRelCmdnInit_PSNoofIuRelC

Counter: iuRelReq.-iuRelCmd.-

perCell

RRCConnectionEstablish-mentFailureRate

This KPI describes the ratio of unsuccessful RRC connectionestablishments related to all RRC connection establishmentattempts.

%100*][

][

alltrrcEstabAt

allilrrcEstabFaRrcEstabFR =

Number of Samples = rrcEstabAtt[all]

Counter: rrcEstabAtt.

rrcEstabFail.

perCell

Accessibility

CS RABEstablishment FailureRate

This KPI describes the ratio of unsuccessful RAB establishmentsrelated to the total number of RAB establishment attempts (per CSdomain).

%100*]108,52[

]251[_

=

peAttrabEstabTy

peFailrabEstabTyCSpeFRRabEstabTy

Number of Samples = rabEstabTypeAtt[2-5,8-10]

Counter: rabEstabTypeAtt.rabEstabTypeFail.-

perCell


47/50


A50023-X6009-A2-4-7619 47

PS RABEstablish-mentFailure

Rate

This KPI describes the ratio of unsuccessful RAB establishmentsrelated to the total number of RAB establishment attempts (per PSdomain).

%100*]2311,7,6,1[

]5026[_= peAttrabEstabTy

peFailrabEstabTyPSpeFRRabEstabTy

Number of Samples = rabEstabTypeAtt[1,6,7,11-23]]

Counter: rabEstabTypeAtt.rabEstabTypeFail.-

perCell

Accessibility Call Setup

FailureRate

This KPI describes the ratio of unsuccessful call establishmentsderived from the procedures involved in RRC - and RAB Establishment attempts and successes (CS and PS combined).

%100*][

][*]20,18,17,15,101[

]20,18,17,15,101[1

=

allpeAttrabEstabTy

allpeSuccrabEstabTy

trrcEstabAt

ccrrcEstabSu

CSFR

Number of Samples =rrcEstabAtt[1-10,15,17,18,20]+rabEstabTypeAtt[all]]

Counter: rrcEstabAtt.rrcEstabSucc.rabEstabTypeAtt.rabEstabTypeSucc.

perCell

Mobility

HardHandoverDrop Rate

(intraNodeB,intra RNC,inter RNCvia Iurcombined)

This KPI provides the ratio between dropped outgoing hardhandovers related to the attempted outgoing hard handovers.

Handover drops describe unsuccessful handovers withoutreconnection to originating cell, i.e. with loss of call, related tohandover attempts.

%100*]9,54[

]9,54[

]9,54[

tt3hhoAllOutAtt2hhoAllOutAtt1hhoAllOutA

ail3hhoAllOutF

ail2hhoAllOutF

ail1hhoAllOutF

HHODR

++

=

Number of Samples = hhoAllOutAtt1+hhoAllOutAtt2+hhoAllOutAtt3Counter: hhoAllOutFail1.


48/50


48 A50023-X6009-A2-4-7619

SoftHandoverDrop Rate


This KPI describes the ratio of dropped branch (radio link) additionsrelated to the total number of branch (radio link) addition attempts.

Dropped branch additions describe interrupted soft handovers dueto unavailability of the existing original radio link.

%100*

][

][

][

]31,18,11[

]31,18,11[

]31,18,11[

+

+

+

+

=

allrRncAttshoAddInte

allaRncAttshoAddIntr

allaNodeBAttshoAddIntr

rRncFailshoAddInte

aRncFailshoAddIntr

aNodeBFailshoAddIntr

RBranchAddDi

i

i

Number of Samples =shoAddInraNodeBAtt[all]+shoAddIntraRncAtt[all]+shoAddInterRncAtt[all]

Counter: shoAddIntraNodeBFail.shoAddIntraRncFail.shoAddInterRncFail.shoAddIntraNodeBAtt.shoAddIntraRncAtt.shoAddInterRncAtt.

HardHandoverFailure

Rate


This KPI provides the ratio between unsuccessful outgoing hardhandovers related to the attempted outgoing hard handovers.

Handover failure describes unsuccessful handovers with the re-

connection to the originating cell.

%100*

][

][

][

tt3hhoAllOutAtt2hhoAllOutAtt1hhoAllOutA

iail3hhoAllOutF

iail2hhoAllOutF

iail1hhoAllOutF

HHOFRi

i

i

+

+

=

Number of Samples = hhoAllOutAtt1+hhoAllOutAtt2+hhoAllOutAtt3

Counter: hhoAllOutFail1.


49/50


A50023-X6009-A2-4-7619 49

SoftHandoverFailureRate


This KPI describes the ratio of unsuccessful branch (radio link)additions related to the total number of branch (radio link) additionattempts.

Unsuccessful branch additions describe failed soft handovers withavailability of the existing active link set

%100*

][

][

][

][

][

][

+

+

+

+

=

allrRncAttshoAddInte

allaRncAttshoAddIntr

allaNodeBAttshoAddIntr

irRncFailshoAddInte

iaRncFailshoAddIntr

iaNodeBFailshoAddIntr

RBranchAddFi

i

i

Number of Samples =shoAddInraNodeBAtt[all]+shoAddIntraRncAtt[all]+shoAddInterRncAtt[all]

Counter: shoAddIntraNodeBFail.shoAddIntraRncFail.shoAddInterRncFail.shoAddIntraNodeBAtt.shoAddIntraRncAtt.shoAddInterRncAtt.

perCell

Mobility

Outgoing

InterSystemHandoverfailure rate

This KPI provides the ratio between unsuccessful outgoing inter

system handovers related to the attempted outgoing inter systemhandovers.

Handover failure describes unsuccessful handovers with re-connection to originating cell

%100*][

][

alltt4hhoAllOutA

iail4hhoAllOutF

pCellISHHOOutFR i=

Number of Samples = hhoAllOutAtt4

Counter: hhoAllOutFail4.-hhoAllOutAtt4.

(4) Inter System

per

Cell


50/50


9 LIST OF ABBREVIATIONS

BSC Base Station Controller

CSV Comma Separated Value

EMV Enhanced Measurement Visualizer

GUI Graphical User Interface

JRE Java Runtime Environment

KPI Key Performance Indicator

MVI Measurement Visualizer

NE Network Element

OMP Operation and Maintenance Processor

OMT Operation and Maintenance Terminal

RC Radio Commander

measurementvisualiser

Documents