Measurement Visualiser

s
Operation
Radio Commander RC 8.5
Measurement Visualizer and

Enhanced Measurement Visualizer
A50023-X6009-A2-4-7619
Measurement Visualizer and Operation
Enhanced Measurement Visualizer Radio Commander RC 8.5
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 zwangsläufig bestimmte Teile der Geräte unter Spannung.
Einige Teile können auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu
Körperverletzungen und Sachschäden führen.
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
Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.
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 2006

Issued by the Communications Group
Hofmannstraße 51
D-81359 München
Technical modifications possible.
Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a
written contract.
A50023-X6009-A2-4-7619
Operation Measurement Visualizer and
Radio Commander RC 8.5 Enhanced Measurement Visualizer
Table of Contents
1 SOFTWARE SUMMARY ..................................................................................... 7
1.1 About Measurement Visualizer (MVI) ................................................................... 7

1.1.1 Purpose ................................................................................................................ 7
1.2 About Enhanced Measurement Visualizer (EMV) ................................................ 7
1.2.1 Purpose ................................................................................................................ 7
1.3 Data handling ....................................................................................................... 7
1.4 Software Structure................................................................................................ 8
1.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 ....................................................................................... 10

3.2 Import NodeB relations....................................................................................... 10
3.3 Set the input directory......................................................................................... 10
3.4 Set the import filter ............................................................................................. 10
3.5 Start the MVI client ............................................................................................. 11
4 SOFTWARE COMPONENTS ............................................................................ 12
4.1 The Server Part .................................................................................................. 12

4.1.1 Configuration of the Server................................................................................. 12
4.1.2 Backup and Restore Server Data ....................................................................... 13
4.1.2.1 Backup................................................................................................................ 14
4.1.2.2 Restore ............................................................................................................... 14
4.2 The Client ........................................................................................................... 14
4.2.1 Measurement Visualizer menu bar ..................................................................... 15
4.2.1.1 File menu............................................................................................................ 15
4.2.1.2 Edit menu ........................................................................................................... 15
4.2.1.2.1 Reload Object Browser....................................................................................... 15
4.2.1.2.2 Export ................................................................................................................. 15
4.2.1.2.3 Preferences ........................................................................................................ 16
4.2.1.3 Administration menu........................................................................................... 16
4.2.1.3.1 Define Reports.................................................................................................... 16
4.2.1.3.2 Define Bandfilter ................................................................................................. 17
4.2.1.3.3 Manage Import Filters......................................................................................... 19
4.2.1.4 Help Menu .......................................................................................................... 19
4.2.1.4.1 User Manual ....................................................................................................... 19
4.2.1.4.2 About Measurement Visualizer........................................................................... 20
4.2.2 Client tool bar ..................................................................................................... 20
4.2.3 The Object Browser............................................................................................ 20
4.2.4 The Time Attributes ............................................................................................ 22
4.2.4.1 Start Date and End Date .................................................................................... 22
4.2.4.2 Band Filters ........................................................................................................ 22
A50023-X6009-A2-4-7619 3
4.2.5 Report Retrieval.................................................................................................. 23

4.2.6 Data table ........................................................................................................... 24
5 THE ENHANCED MEASUREMENT VISUALIZER............................................ 26
5.1 The main new features in the EMV .................................................................... 26

5.2 Installation and Set-up of the Server .................................................................. 26
5.3 Server side differences....................................................................................... 26
5.3.1 Threshold configuration ...................................................................................... 26
5.3.2 Data directory prerequisite for the Import On Demand feature........................... 27
5.4 Client side differences ........................................................................................ 28
5.4.1 Main window differences .................................................................................... 28
5.4.2 Edit menu differences......................................................................................... 29
5.4.2.1 Refill Threshold Violation List ............................................................................. 29
5.4.2.2 Resume/Pause Threshold Violation Retrieval .................................................... 29
5.4.2.3 Stop Threshold Violation Retrieval ..................................................................... 30
5.4.2.4 Resume/Pause Report Retrieval ........................................................................ 30
5.4.2.5 Stop Report Retrieval ......................................................................................... 30
5.4.2.6 Reset Scalefactor to 100% ................................................................................. 30
5.4.2.7 Modify Visibility Of Curves .................................................................................. 30
5.4.2.8 Export (changes) ................................................................................................ 30
5.4.2.9 Preferences (changes) ....................................................................................... 31
5.4.3 Administration menu differences ........................................................................ 31
5.4.3.1 Manage Import Filters (changes)........................................................................ 31
5.4.3.2 Define TimeBorder ............................................................................................. 32
5.4.4 Client tool bar differences ................................................................................... 33
5.4.5 The Time Attributes differences.......................................................................... 34
5.4.5.1 The Time Check ................................................................................................. 34
5.4.5.2 Dynamic Report Retrieval................................................................................... 34
5.4.6 Upgrades in data representation ........................................................................ 34
5.4.6.1 Data table ........................................................................................................... 35
5.4.6.2 Coordinate system.............................................................................................. 36
5.4.7 Threshold Violation List ...................................................................................... 36
6 RESTRICTIONS ................................................................................................. 39
6.1 No user and session management ..................................................................... 39

6.2 Print limitations ................................................................................................... 39
6.3 Cell number limitation in reports ......................................................................... 39
6.4 XML input file restrictions ................................................................................... 39
6.5 Automatic deletion of NEs from Object Browser................................................. 39
7 TROUBLESHOOTING ....................................................................................... 40
7.1 The object browser is empty right after start....................................................... 40

7.2 Connection to server lost .................................................................................... 40
7.3 Number of cells in the table is exceeded ............................................................ 40
7.4 No data available in the MVI............................................................................... 40
7.5 Network problems............................................................................................... 40
8 APPENDIX ......................................................................................................... 41
4 A50023-X6009-A2-4-7619
8.1 Overview of GSM and UMTS RTPM KPIs:......................................................... 41

8.2 Predefined Key Performance Indicators (GERAN)............................................. 42
8.3 Predefined Key Performance Indicators (UTRAN) ............................................. 45
9 LIST OF ABBREVIATIONS ............................................................................... 50
A50023-X6009-A2-4-7619 5
List of Figures:
Figure 1: The Measurement Visualizer main window ................................................................... 14
Figure 2: The Report List dialog.................................................................................................... 16
Figure 3: The Define report dialog ................................................................................................ 17
Figure 4: The BandFilter List dialog .............................................................................................. 18
Figure 5: The BandFilter Definition dialog..................................................................................... 18
Figure 6: The Import Filter Manager dialog................................................................................... 19
Figure 7: The About Measurement Visualizer dialog of the MVI................................................... 20
Figure 8: The Object Browser ....................................................................................................... 21
Figure 9: The start and end date selection area ........................................................................... 22
Figure 10: The BandFilter selection area ...................................................................................... 23
Figure 11: The BandFilter Manager dialog.................................................................................... 23
Figure 12: The Report selection area ........................................................................................... 24
Figure 13: The Receiving Data dialog........................................................................................... 24
Figure 14: The data table .............................................................................................................. 24
Figure 15: The Enhanced Measurement Visualizer main window ................................................ 28
Figure 16: The Threshold Violation Filter dialog ........................................................................... 29
Figure 17: The Curvevisibility dialog ............................................................................................. 30
Figure 18: Import On Demand dialog............................................................................................ 31
Figure 19: The Time Check Interval List dialog............................................................................. 32
Figure 20: The Define TimeBorder dialog ..................................................................................... 33
Figure 21: The TimeCheck field.................................................................................................... 34
Figure 22: The Dynamic Update selection area............................................................................ 34
Figure 23: The columns and headers of the data table................................................................. 35
Figure 24: The graphical representation ....................................................................................... 36
Figure 25: The Threshold Violation List ........................................................................................ 37
6 A50023-X6009-A2-4-7619
1 SOFTWARE SUMMARY
1.1 About Measurement Visualizer (MVI)
1.1.1 Purpose
The Measurement Visualizer (MVI) allows visualizing a limited amount of performance
measurement data of selected network elements (NEs) within the Radio Commander. It provides
a tabular presentation of the data with a history of up to 24 hours. Data from maximum 4 BSC, 50
NodeB, and 2 RNC can be visualized simultaneously.
MVI is intended to offer a quick and easy status of the network performance to the user. For
detailed analysis Siemens offers the extended version of the MVI called EMV described in the
following section.
1.2 About Enhanced Measurement Visualizer (EMV)

1.2.1 Purpose
The Enhanced Measurement Visualizer (EMV) is the extension of the previous application that
supports also the graphical representation of the measurement data both historical data (past
data) and dynamic data monitoring. The EMV also provides threshold violation list with customer
defined rules.
Please find all the additional features and their description in chapter 5, THE ENHANCED
MEASUREMENT 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 be
retrieved from the RC file system as XML files for the BSC elements and as binary files for NodeB
and RNC elements. Measurement data and objects older than 24 h are automatically removed
from the system.
Only performance measurement data of maximum 4 BSC, 50 NodeB, and 2 RNC are uploaded
into MVI, in order to reduce the performance requirements on the RC. The NEs can be
determined through an observing list that can be administrated through a GUI panel in MVI. The
NEs, the RC contains data of, are offered for selection in this GUI (in the Object Browser). If the
selection is modified, MVI retrieves the data of the past 24 hours and starts uploading the data of
the added NEs from that point of time on.
The data retrieval procedure is described in the following use case:
1. Start the Measurement Visualizer, see Start 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 Object
Browser 4.2.3.
4. Define the start date, the end date and if desired the time, see Start Date and End Date
4.2.4.1.
5. Select a predefined report (see point 1 – there can be more reports defined – they are
offered in a list), see Report Retrieval 4.2.5.
6. Click the Retrieve Report button to get the data.
A50023-X6009-A2-4-7619 7
The data can be exported into CSV files for further evaluation in e.g. MS Excel, with a filter per
NE.
1.4 Software Structure

MVI is realized as a stand-alone Java client-server application. The server and client are installed
on the OMP and OMT respectively. After the installation of the server part on the OMP machine,
the Measurement Visualizer button is available on the RC Applications window. Any RC user may
access 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.
8 A50023-X6009-A2-4-7619
2 INSTALLATION AND SET UP OF SOFTWARE

2.1 Installation and Set-up of the Server
The MVI is delivered to the customer together with the package RC OMP. It will be installed with
the basic installation of the OMP package.
2.2 Installation and Set-up of the Client

The client application will always be installed on an MVI server. It is downloaded to and started on
the machine you would like to. Only five clients can be started simultaneously from one machine.
A50023-X6009-A2-4-7619 9
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 <mvi_home>.
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 following
steps:
1. Export the NodeB relations from RC via the Exportnodebrelations command in a CLI
session.
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 <nbrelfile>
below.
2. Execute the configuration script to import the NodeB relations data into MVI:
[omc_plus@omp] > cd <mvi_home>/scripts
[omc_plus@omp] > nbrelationsimport.pl <nbrelfile>
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 <mvi_home>/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. The
periodically started import server will import the data and calculate KPIs only for these NEs. The
import filter is by default empty.
To set the import filter perform the following steps:
1. Start the MVI client, see Start the MVI client 3.5.
2. Set the import filter, see Manage Import Filters 4.2.1.3.3.
10 A50023-X6009-A2-4-7619
3.5 Start the MVI client

● Click the Measurement Visualizer button in the RC Applications window to open the MVI.
For troubleshooting see chapter 7 TROUBLESHOOTING.
A50023-X6009-A2-4-7619 11
4 SOFTWARE COMPONENTS
This chapter describes the software components.
4.1 The Server Part

The 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 runs
permanently.
● Application server: It collects and forwards measurement data by request from the server
database and binary files to the client. There will be an application server running for each
client. On request by the user, sent via MVI client, the application server retrieves counter
and KPI values, together with additional data.
4.1.1 Configuration of the Server

The <mvi_home>/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 <mvi_home>/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 <mvi_home>/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 first
argument.
What may be changed in the configuration is shown in the following list, where configuration
parameters 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 at
all. 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
12 A50023-X6009-A2-4-7619
o Base directory where the imported data files can be found

in 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.luc
EnableImportProcess=1
● Symbolic names for counters and KPIs in the configuration file
symboliccounterlist.cfg.
In the example below the symbolic name mysymboliccountername is defined for the
counter dhtUsage.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) and
for 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 file
userdefinedviews.cfg.
You can define a view as a block in the file. The block name is the name of the view, and
each 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:0
RNC:4/STM1LINE:0.1.29.0/STM1VP:5/STM1VC:3
After running the configuration script <mvi_home>/scripts/userviewimport.pl as
user omc_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 performing
a restore. The data used by the MVI server comprises the data files containing the imported
counters and the calculated KPIs stored in the server database.
A50023-X6009-A2-4-7619 13
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] > <mvi_home>/scripts/exportData
This will collect the data into the file <mvi_home>/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
<mvi_home>/import.
2. Start the executable <mvi_home>/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 Visualizer client, see Start the MVI client 3.5.
Figure 1: The Measurement Visualizer main window
14 A50023-X6009-A2-4-7619
The Measurement Visualizer main 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 by
generating a report, see also Data handling 1.3.
The side bar contains the Object Browser and the selection areas. You can minimize, restore and
maximize the side bar by clicking on the arrows at the top of its border line. When the data table
is visible and you click on the upper arrow the side bar gets minimized, thus the data table
occupies the whole window. If you click the lower arrow having this layout, the side bar gets
restored. By clicking the lower arrow again the Object Browser occupies the whole window.
You can move the border line in finer steps as well by simply grabbing and moving it. The layout
changed this way will be the one that the application returns to when the side bar is restored. The
side 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 File menu contains the following menu item:

● Logout
Select this menu item to close the application.
4.2.1.2 Edit menu
The Edit menu 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 and
displayed in the Object Browser.
4.2.1.2.2 Export
Select this menu item to export data.
● Export Report
Sub menu item to save the tabular representation of the measurement report
A50023-X6009-A2-4-7619 15
Select this sub menu item to save the data as a CSV file (fields are separated by default with a
semicolon, the customer may set the separating character in the Preferences) using a usual Save
dialog.
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 export
of the report).
4.2.1.3 Administration menu
The Administration menu 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 List dialog opens.
Figure 2: The Report List dialog

The Report List dialog displays the already defined reports in a tabular form. Each row represents
a report. The left field of each row holds the name of the report, the right one lists the KPIs and
counters incorporate the report. The listed report may be selected in the Report selection area in
order to narrow the retrieved values to the necessary KPIs and counters.
Click the Add button on the right side to define a new report in the Define report dialog.
16 A50023-X6009-A2-4-7619
Figure 3: The Define report dialog

On the top of the dialog define the name of the new report in the Report Name field. Below this
field all the KPIs and counters included by the report are listed on the right (Selected
KPI(s)/Counters), on the left side all the others (Deselected KPI(s)/Counters).
Use the arrows to move the selected list item(s) from one list to the other and vice versa.
Change the order of the items only in the Selected KPI(s)/Counters list. Their top-down order
represents the left-to-right order in the tabular representation of the report.
In the Report List dialog 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. Clicking the Modify
button the same dialog opens as by clicking the Add button.
Note:
KPIs are calculated only in case of the Enhanced Measurement Visualizer.
4.2.1.3.2 Define Bandfilter

Select this menu item to list, modify, or remove already existing band filters or to define a new
band filter. The BandFilter List dialog opens.
A50023-X6009-A2-4-7619 17
Figure 4: The BandFilter List dialog

The BandFilter List dialog displays the list of band filters already defined.
Click the Add button on the right side to define a new band filter in the BandFilter Definition
dialog.
Figure 5: The BandFilter Definition dialog
18 A50023-X6009-A2-4-7619
Specify the start and the end times of the band filter.
In the BandFilter List dialog 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 Modify button the same dialog opens as by clicking the Add button.
4.2.1.3.3 Manage Import Filters

Select this menu item to select NEs whose measurement data you are interested in. The Import
Filter Manager dialog 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 be
filtered separately. The NEs for which the raw data is already available but still not imported and
for which the KPIs are still not calculated are in the Out list on the left.
If some of them are moved to the In list, the next run of the import server will import the data of
them and calculate the KPIs.
During the continuous run of the import server, reports can be retrieved for the NEs in the In list.
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 the
Adobe Acrobat Reader is required to be installed on the machine where you are working.
A50023-X6009-A2-4-7619 19
4.2.1.4.2 About Measurement Visualizer

Select this menu item to open the About Measurement Visualizer dialog. This shows the proper
name and version of the client application.
Figure 7: The About Measurement Visualizer dialog of the MVI

Close this dialog by clicking the Close button.
4.2.2 Client tool bar

The tool bar contains shortcut icons to some of the menu items described above:
Reload Object Browser, described in 4.2.1.2.1
Logout, described in 4.2.1.1
Help, described in 4.2.1.4
4.2.3 The Object Browser

The Object Browser contains all the NEs for which data is contained by the measurement files. It
is 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 Browser
command.
20 A50023-X6009-A2-4-7619
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 are
accessible 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 expand
the 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 not
expanded. The root objects are the default and the user defined views. In the default view all the
objects are shown for which data is contained by the measurement files. In a user defined view a
simplified structure may be defined having only the nodes the user needs, see also Configuration
of 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 single
nodes, groups of adjacently displayed nodes and sub-trees. The latter action can be performed
by clicking the check box before folder nodes. By this action all descendants of the node and the
node itself get highlighted, hence selected.
The check box of a node is an indicator as well. It gives information about selected descendants
of the folder it belongs to. Three different cases can be distinguished by simply taking a look at
such a check box:
A50023-X6009-A2-4-7619 21
● If it is greyed out and selected, it means that not all, but at least one of the descendants of
the folder are selected.
● A non-greyed-out and selected check box indicates that all of the descendants are
selected.
● A deselected check box indicates that there is no selected node going down that branch of
the 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 same
with 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 Time selection area)
● A band filter (defined in the BandFilter selection area)
4.2.4.1 Start Date and End Date
After selecting one or more objects from the Object Browser you have to select a time period in
the Time selection area. The report about the selected nodes will be based on the date of this
period.
Figure 9: The start and end date selection area

Adjust the date using the calendar dialog. Adjust the time values either using the Hour/Minute
dialog 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 last
correct 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 the
BandFilter selection area.
Specify a time band of the previously defined time period to be considered at retrieval. Add one or
more band filters at the same time using the Bandfilter Manager dialog.
Remove band filter(s) from the BandFilter selection area using the Remove button in the
BandFilter selection area.
22 A50023-X6009-A2-4-7619
Figure 10: The BandFilter selection area

Click the Add button to open the Bandfilter Manager dialog containing the list of all the band filters
defined 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 In list) and all the others on the left
(in the Out list).
4.2.5 Report Retrieval

Select the report defining the KPIs and/or counters you are interested in from the list in the Report
selection area.
A50023-X6009-A2-4-7619 23
Figure 12: The Report selection area

The list of reports is retrieved from the server. The default selection is the first item of the report
list. After retrieval the data table will represent the values of the KPIs and counters specified by
the selected report. For further information refer to Define Reports 4.2.1.3.1.
Figure 13: The Receiving Data dialog

Click the Retrieve Report button to trigger the retrieval and the report visualization
During retrieval an animated Progress Dialog opens with a counter of the already retrieved rows
and 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 row
of the table shows the measurement data (KPI or counter values) of one of the previously
selected 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 row
format: dd-mm-yyyy hh:mm:ss
24 A50023-X6009-A2-4-7619
● Object: indicates the object identifier

● KPIs and counters selected in the user defined report
The 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 table
shows them in two lines as well.
Undefined counter values in the KPI formulas are considered as zero. A KPI may have no value
at a particular time and for a particular object, if its formula contains a division by zero. Undefined
counter values and KPI values containing a division by zero are represented by an empty cell in
the data table.
By default the table is not sorted by the client of the MVI. The tabular representation contains all
the 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 or
right-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 down
arrow that appears at the right side of the column header. You may change the sort order any
time by clicking this arrow, or by selecting the corresponding item from the context menu that
appears after right-clicking the column header.
If you indicate the sort by either the Date or the Object values, the secondary key of the sort will
be the other one of the two. The sort order of both the primary and the secondary keys will be the
same. If you indicate the sort by any other column, there would not be any secondary key.
A50023-X6009-A2-4-7619 25
5 THE ENHANCED MEASUREMENT VISUALIZER

The Enhanced Measurement Visualizer (EMV) is the extended version of the Measurement
Visualizer. It is not installed by default to the RC, it must be ordered from Siemens AG. This part
of the documentation describes all the differences between the MVI and EMV which are only
feature 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 proprietary
format
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 <mvi_home>/etc/thresholdimport.cfg and run the perl script
<mvi_home>/scripts/thresholdimport.pl to make the corresponding threshold violations
available:
[omc_plus@omp] > <mvi_home>/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 file
thresholdimport.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 threshold
value (in the 2nd column). The relation operator has to be defined in the 3rd column, its possible
values are:
LESS
LESS_OR_EQUAL
EQUAL
NOT_EQUAL
26 A50023-X6009-A2-4-7619
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 <mvi_home>/scripts/thresholdimport.pl to make the
changes 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 section 5.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
A50023-X6009-A2-4-7619 27
5.4 Client side differences

5.4.1 Main window differences
Figure 15: The Enhanced Measurement Visualizer main window

● The window of the EMV application is extended with a graphical area and a legend table,
which is located on the right just above the data table. The graphical area shows the
graphical representation of a report after a successful retrieval. See also Coordinate
system 5.4.6.2.
● The Threshold Violation List tab is added to the side bar which contains the Object
Browser. See also Threshold Violation List 5.4.7.
● An additional field TimeCheck is inserted in the Time selection area, see The Time Check
5.4.5.1.
● The Dynamic Update selection area is inserted below the Time selection area, see
Dynamic Report Retrieval 5.4.5.2.
28 A50023-X6009-A2-4-7619
5.4.2 Edit menu differences

The Edit menu 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 Edit menu 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 Filter dialog
opens.
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. The
first 5000 records will be sent.
Dynamic threshold violation list retrieval: Select Activate Dynamic Update. The last 5000
records are downloaded and displayed dynamically until you stop or pause this continuous
update. New arrived data is shown after the import process has run by removing earlier records (if
the 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.
A50023-X6009-A2-4-7619 29
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 graphical
representation 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 Curvevisibility dialog opens.
Figure 17: The Curvevisibility dialog

This dialog lists the names of the invisible curves on the left side (Invisible list) and the visible
ones (Visible list) on the right side.
5.4.2.8 Export (changes)
Select this menu item to export data.
30 A50023-X6009-A2-4-7619
● Export Threshold Violation

Sub menu item to export the threshold violation list
● Export Coordinationsystem
Sub 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 coordinationsystem
Sub menu item to show/hide the legend of the coordination system
5.4.3 Administration menu differences

The Administration menu contains the following changed menu item:
● Manage Import Filters
The Administration menu 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 on
demand. The Import Filter Manager dialog opens.
Figure 18: Import On Demand dialog
A50023-X6009-A2-4-7619 31
Select one object in the Out list and click the Import on Demand button. The list of available files
opens. Select one or more files and click Ok to save your changes. The selected files will be
imported.
The Import On Demand feature works only if the data in is stored in a directory with a specified
form. 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 for
the TimeCheck. The Time Check Interval List opens.
Figure 19: The Time Check Interval List dialog

This dialog lists only the user defined time intervals not the predefined ones.
Click the Add button on the right side to define a new interval. The Define TimeBorder dialog
opens.
32 A50023-X6009-A2-4-7619
Figure 20: The Define TimeBorder dialog

Specify Name, start time and end time of the interval.
In the Time Check Interval List dialog 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. Clicking
the Modify button the same dialog opens as by clicking the Add button.
5.4.4 Client tool bar differences
Refill Threshold Violation List, described in 5.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 Retrieval the second
two to the Dynamic Report Retrieval.
Note:
The pairs are working the same way.
If the buttons are grey, the retrieval is historical.
A50023-X6009-A2-4-7619 33
If the first button is green, the dynamic update is ongoing (you may see the refreshing data table
or 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 Browser you have to select a time period.
You can specify the time period either manually (see 4.2.4.1) or using the TimeCheck feature
containing predefined values. Without object selection the TimeCheck field 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 Update is set, the TimeCheck, Start Time, End Time and BandFilter values are
neglected, only the last hour/minute data will be represented. If new data arrives, the values are
shown 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. The
latter one can be used to display only a part of the first.
34 A50023-X6009-A2-4-7619
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, which
indicates whether their values are currently displayed in the coordination system. It is located on
the column header left to the column name. By default all KPI and counter values are shown in
the 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 the
coordination system. This is offered by an additional check box, called the solo button. The solo
button is located on the header of each column below the visibility flag. By default the solo button
is not set for any column. If you set it by clicking it, only the values of that KPI or counter are
displayed in the coordination system. By clicking the solo button again the graphical
representation will get back to its previous state. By setting more solo buttons one after the other
the 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 context
menu. It is the same context menu that offers the possibility to change the sort order.
A50023-X6009-A2-4-7619 35
5.4.6.2 Coordinate system
Figure 24: The graphical representation

The coordinate system provides a graphical representation of the generated report. Right after
the 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 always
adjusted to the prevailing minimum and maximum of the values displayed. If the visibility of the
curves is manipulated, the maximum and minimum values of the axes will be updated too. Each
point represents one KPI or counter value of one of the selected NEs plotted against date and
time. 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 assignment
of colors happens during retrieval, thus each curve retains its color for the time between
consecutive retrievals. You cannot change or influence the color of a curve. Each curve in the
coordinate system is given a different color, thus - especially having a sheer number of curves - it
may occur that few of them have very similar ones. A legend on the right side of the coordinate
system indicates the mapping between curve names and colors.
The legend holds the relation between the colors of the curves and their names. Here you can
also 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 List by
using the Refill Threshold Violation List button on the client tool bar or using the corresponding
item in the Edit menu. The records are listed in a tabular form containing the following attributes:
Severity, Counter, Object, Date.
36 A50023-X6009-A2-4-7619
Figure 25: The Threshold Violation List
A50023-X6009-A2-4-7619 37
The Threshold Violation List is refreshed dynamically if the Activate Dynamic Update check box is
selected in the Threshold Violation Filter dialog. You can refill it any time you want. Click the Refill
Threshold Violation List button to open the Threshold Violation Filter dialog, see Refill Threshold
Violation List 5.4.2.1.
Select one or more records in the Threshold Violation List to display the details in the Threshold
Violation Details area, 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 is
available in the currently loaded report, the corresponding cell in the data table will be highlighted
with red.
38 A50023-X6009-A2-4-7619
6 RESTRICTIONS
The restrictions of the Measurement Visualizer are listed in the following topics.
6.1 No user and session management

The Measurement Visualizer does not assign any IDs to client and application server pairs to
identify 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 and
opening 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 Preferences dialog. For further
details 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 the
number of cells retrieved reaches this limit the following warning message is displayed during
historical 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 is
reached, the old rows are thrown out of the representation. For further details see Number of cells
in 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 the
format of the object identifiers. It can be CGID, FDN or symbolic name. It is hardly recommended
not to change this setting for the XML files which should be imported together. Otherwise the
object will be represented in both names with the measured values divided according to the input
files which lead to inconsistencies.
6.5 Automatic deletion of NEs from Object Browser

The MVI deletes automatically the NE from its tree representation, if no data are imported in the
last 24 hours for this NE and any of its sub-elements.
Click the Reloads Object Browser button in order to see the changes in the Object Browser on the
client side.
A50023-X6009-A2-4-7619 39
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 and
server 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 has
to be configured so that the connection through the port XX is able to be used. This is the port
needed for CORBA communication.
Another circumstance that may cause the same problem is that the import of the measurement
data was not successful. Check that the configuration of the directory, where the raw
measurement data files can be found, is correct. See details in Configuration 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 error
message appears: “The server is not accessible!” In this case the client has to be restarted. The
circumstances of the server’s 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 to
change 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 filter
setting. Ask your system administrator if the machine where the MVI client runs is allowed to
connect to the one where the MVI server is running.
40 A50023-X6009-A2-4-7619
8 APPENDIX
Since all the observed RTPM indicators (KPI) are presented in ratio, it will be very useful also to
provide 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- GERAN UTRAN Measurement

gory depth
Mean Combined Time Slot Transmitted Carrier Power per Cell
Capacity
Occupation Rate for CS and PO (Downlink Cell Load Rate)

Traffic
Received Total Wideband Power per Cell
(Uplnk Cell Load Rate)
SDCCH Drop Rate RRC Connection Drop Rate per Cell
Retain
Ability
TCH Drop Rate CS Connection Drop Rate per Cell

TBF Drop Rate PS Connection Drop Rate per Cell
Assignment Failure Rate (or RRC Connection Establ. Failure per Cell
SDCCH Loss Rate) Rate (or RRC Loss Rate)
Immediate Assignment Failure CS RAB Connection Establ. per Cell
Accessibility
Rate (or TCH Loss Rate) Failure Rate (or CS RAB Loss
Rate)
TBF Assignment Failure Rate (or PS RAB Connection Establ. per Cell
TBF Loss Rate) Failure Rate (or PS RAB Loss
Rate)
Call Setup Failure Rate Connection Setup Failure Rate per Cell
(CS and PS combined)
Handover Drop Rate (intra cell, Hard Handover Drop Rate (intra per Cell
intra BSC, inter BSC) cell, intra RNC, inter RNC)
Soft Handover Drop Rate (intra per Cell
cell, intra RNC, inter RNC)
Mobility
Handover Failure Rate (intra cell, Hard Handover Failure Rate (intra per Cell
intra BSC, inter BSC) cell, intra RNC, inter RNC)
Soft Handover Failure Rate (intra per Cell
cell, intra RNC, inter RNC)
Outgoing Inter System Handover Outgoing Inter System Handover per Cell
Failure Rate Failure Rate
A50023-X6009-A2-4-7619 41
8.2 Predefined Key Performance Indicators (GERAN)

The table shows the list of defined RTPM indicators sorted by categories. This table also contains
the formula of KPI calculation and the required PM sub-counters of SBS performance
measurements.
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- RTPM Formula Meas.

gory indicator depth
(KPI)
Mean This KPI provides the mean occupation rate of those timeslots of a per
Combined cell, which can be assigned to users: Cell
Time Slot
Occupation NOcTS
MeaOcTsC = * 100 %
Rate for CS NDefTS
and PO
Traffic Number of samples = NDefTS
Capacity
Where:
⎧ NALLPDCH [3,6 ] + MEBUSTCH [1,3] + ⎫
NOcTS = ⎨ ⎬
⎩ MEBUSTCH [ 2 , 4 ] / 2 + MBUSYSDC [1] / 8 ⎭
⎧ NDEFPDCH [ 3] + NRDEFTCH [ 3,9 ] ⎫
⎪ ⎪
NDefTS = ⎨ + NRDEFTCH [ 6,12 ] / 2 ⎬
⎪ + NDFTCHSD [1] + NDESDCCH [3] / 8 ⎪
⎩ ⎭
SDCCH This KPI provides the percentage of all drops of connections during per
Drop Rate a SDCCH connection: Cell
NRCLRREQ[19..21,23..26] + TASSFAIL[1,6,11]
SDCCHDropRate = *100%
NSUCCHPC[1..6]
Retain Ability
Number of Samples = NSUCCHPC[1..6]
TCH Drop This KPI provides the percentage of all TCH drops related to TCH per
Rate connection. A TCH may be seized during call setup and additonally Cell
for ahndover (including diracted retry):
NRCLRREQ[1..3,5..12,14..18]
TCHDropRat e = * 100%
SUCTCHSE[1..2]
Number of Samples = SUCTCHSE[1..2]
42 A50023-X6009-A2-4-7619

(KPI)
TBF Drop This KPI provides the total TBF drop rate (UL and DL combined). per
Rate Drops comprise all unsuccessful terminated TBF: Cell
UNSTETBF [1,2,10..13]
TBFDropRat = *100%
SULACCEL[1,2]
Number of Samples = SULACCEL[1,2]
SDCCH This KPI provides the SDCCH traffic loss rate by meaning of the per
Loss Rate rate where new SDCCH seizure attempts can not be handled, Cell
because all traffic channels (circuit groups) were occupied:
ATSDCMBS [1]
SDCCHLossR ate = * 100%
NATTSDPE [1]
Number of Samples = NATTSDPE[1]
TCH Loss This KPI provides the TCH traffic rate by meaning of the rate where per
Rate new TCH seizure attempts can not be handled, because all traffic Cell
channels (circuit groups) were occupied:
ATCHSMBS[all ] + NMSGDISQ[all ]
TCHLossRate = * 100%
ATTCHSEI[all ]
Number of Samples = ATTCHSEI[all]
TBF Loss This KPI provides the TBF loss rate (UL and DL combined) by per
Rate meaning of the rate where new TBF request can not be handled, Cell
because for example no PDCHs were available:
Accessibility
REJPDASS [all ]
TBFLossRat e = *100%
NUACATCL[all ]
Number of Samples = NUACATCL[all]
Call Setup This KPI provides the call setup failure rate by meaning the number per
Failure of call setup failure divided through the number of call setup Cell
Rate attempts:
CAllSetupFailRate =
Im mAssFailRate SDCCHDropRate AssFailRate
(1 − (1 − ) * (1 − ) * (1 − ))
100 100 100
* 100%
Number of Samples = NSUCCHPC[1..4,9..12,17..20] – NSUCCHPC[8]
Where:
ATIMASCA[all ] − NSUCCHPC[1..6,9..4,17..22]
Im mAssFailRate = *100%
ATIMASCA[all ]
TASSFAIL[6..8,10..13,15] + NRCLRREQ[22]
AssFailRate = * 100%
TASSATT [2,3]
NRCLRREQ[19..21,23..26] + TASSFAIL[1,6,11]
SDCCHDropRate = * 100%
NSUCCHPC [1..6]
A50023-X6009-A2-4-7619 43

(KPI)
Handover This KPI privides the percentage of handover drops by meaning of per
Drop Rate unsuccessful handover with loss of MS connection in specified cell: Cell
(intra cell,
intra BSC, HODrops
HODropRate = * 100%
inter BSC, HOAtt
inter Number of Samples = HOAtt
system
combined) Where:
⎧UNIHIALC [1] + UNIHIRLC [1] + ATINBHDO [all ] − ⎫
⎪ ⎪
HODrops = ⎨ SUINBHDO [all ] − NRUNINHD [ all ] + ATOISHDO [ all ] − ⎬
⎪ SUOISHDO[ all ] − UNOISHDO [all ] ⎪
⎩ ⎭
⎧ ATINHIAC[all ] + ATINHIRC[all ] + ATINBHDO[all ]⎫

HOAtt = ⎨ ⎬
⎩+ ATOISHDO[ all ]
Mobility
⎭
Handover This KPI provides the percentage of handover faliures by meaning per
Failure of unsuccessful handover without loss of MS connection because of Cell
Rate (intra reversion to old cell in specified cell:
cell, intra
BSC, inter HOFails
HOFailRate = * 100%
BSC, inter HOAtt
system Number of Samples = HOAtt
combined)
Where:
⎧UNINHOIA[all ] + UNINHOIE[all ] + NRUNINHD[all ]⎫
HOFails = ⎨ ⎬
⎩+ UNOISHDO[all ] ⎭
⎧ ATINHIAC[all ] + ATINHIRC[all ] + ATINBHDO[all ]⎫
HOAtt = ⎨ ⎬
⎩+ ATOISHDO[ all ] ⎭
44 A50023-X6009-A2-4-7619
8.3 Predefined Key Performance Indicators (UTRAN)

(KPI)
Trasnmitted This indicator provides the mean, max or min downlink cell load per
Carrier indicated by the transmitted carrier power: Cell
Power
(Downlink
DlCellLoad ( MMM ) = uuTransmCarrierPwr[ MMM ]
Cell Load) Counter: uuTransmCarrierPwr.<MMM>
Remark: The measured value already provides a percentage value.
Received This indicator provides the mean, max or min uplink cell load per
Capacity
Total indicated by the received total wide band power: Cell

Wideband
Power N _ UL
UlCellLoad ( MMM ) = 1 − *100%
uu Re cTotalWbPwr[ MMM ]
(Uplink Cell
Load) Counter: uuRecTotalWbPwr.<MMM>
Remark: N_UL is an initial configuration parameter for thermal
noise. The configured initial value shall be used = -105dBm. Note,
that this value will change during operation, that the Uplink cell load
is just a rough indication.
RRC This KPI describes the ratio between the number of abnormal RRC per
Connection connection releases and the total number of released RRC Cell
Drop Rate connections.
NoofabnormalRRCRel
RRCDR = *100%
Retain Ability
NoofRRCRel
Number of Samples = NoofRRCRel
With:
NoofabnormalRRCRel = rrcRelDcch[2 − 5,8] + rrcRelCcch[2 − 5,8]
NoofRRCRel = rrcRelDcch[all ] + rrcRelCcch[all ]
Counter: rrcRelDcch.<rrcRelCause>
rrcRelCcch.<rrcRelCause>
A50023-X6009-A2-4-7619 45
CS This KPI describes the ratio of abnormal UTRAN initiated Iu per

Connection connection releases related to the total number of CN initiated Cell
Drop Rate connection releases (per CS domain).
NoofabnormalIuRelUtranInit _ CS
IuCoDR _ CS = *100%
NoofIuRelCnInit _ CS
Number of Samples = NoofIuRelCnInit_CS
With:
NoofabnormalIuRelUtranInit_CS = iuRelReq[2 − 6,9 − 11]
NoofIuRelCnInit_CS = iuRelCmd [1 − 16]
Retain Ability
Counter: iuRelReq.<CSPS>-<relReqCause>
iuRelCmd.<CSPS>-<relCmdCause>
PS This KPI describes the ratio of abnormal UTRAN initiated Iu per
Connection connection releases related to the total number of CN initiated Cell
Drop Rate connection releases (per PS domain).
NoofabnormalIuRelUtranInit _ PS
IuCoDR _ PS = *100%
NoofIuRelCnInit _ PS
Number of Samples = NoofIuRelCnInit_PS
With:
NoofabnormalIuRelUtranInit_PS = iuRelReq[13 − 14,16 − 17,20 − 22]
NoofIuRelCnInit_PS = iuRelCmd[17 − 32]
Counter: iuRelReq.<CSPS>-<relReqCause>
iuRelCmd.<CSPS>-<relCmdCause>
RRC This KPI describes the ratio of unsuccessful RRC connection per
Connection establishments related to all RRC connection establishment Cell
Establish- attempts.
ment
Failure rrcEstabFail[all ]
RrcEstabFR = *100%
Rate rrcEstabAtt[all ]
Number of Samples = rrcEstabAtt[all]
Accessibility
Counter: rrcEstabAtt.<rrcEstabCause>
rrcEstabFail.<rrcEstabFail>
CS RAB This KPI describes the ratio of unsuccessful RAB establishments per
Establishm related to the total number of RAB establishment attempts (per CS Cell
ent Failure domain).
Rate
rabEstabTypeFail[1 − 25]
RabEstabTypeFR _ CS = *100%
rabEstabTypeAtt[2 − 5,8 − 10]
Number of Samples = rabEstabTypeAtt[2-5,8-10]
Counter: rabEstabTypeAtt.<rabType>
rabEstabTypeFail.<CSPS>-<rabFail>
46 A50023-X6009-A2-4-7619
PS RAB This KPI describes the ratio of unsuccessful RAB establishments per
Establish- related to the total number of RAB establishment attempts (per PS Cell
ment domain).
Failure
Rate rabEstabTypeFail[26 − 50]
RabEstabTypeFR _ PS = *100%
rabEstabTypeAtt[1,6,7,11 − 23]
Number of Samples = rabEstabTypeAtt[1,6,7,11-23]]
Counter: rabEstabTypeAtt.<rabType>
rabEstabTypeFail.<CSPS>-<rabFail>
Call Setup This KPI describes the ratio of unsuccessful call establishments per
Accessibility
Failure derived from the procedures involved in RRC - and RAB – Cell
Rate Establishment attempts and successes (CS and PS combined).
CSFR =
⎛ rrcEstabSucc[1 − 10,15,17,18,20] rabEstabTypeSucc[all ] ⎞
⎜⎜1 − * ⎟ *100%
⎝ rrcEstabAtt[1 − 10,15,17,18,20] rabEstabTypeAtt[all ] ⎟⎠
Number of Samples =
rrcEstabAtt[1-10,15,17,18,20]+rabEstabTypeAtt[all]]
Counter: rrcEstabAtt.<rrcEstabCause>
rrcEstabSucc.<rrcEstabCause>
rabEstabTypeAtt.<rabType>
rabEstabTypeSucc.<rabType>
Hard This KPI provides the ratio between dropped outgoing hard
Handover handovers related to the attempted outgoing hard handovers.
Drop Rate
“Handover drops” describe unsuccessful handovers without
reconnection to originating cell, i.e. with loss of call, related to
handover attempts.
(intra
NodeB, ⎧hhoAllOutFail1[4 − 5,9] + ⎫
intra RNC, ⎪ ⎪
inter RNC ⎨hhoAllOutFail2[4 − 5,9] + ⎬
via Iur ⎪hhoAllOutFail3[4 − 5,9] ⎪
HHODR = ⎩ ⎭ *100%
combined)
Mobility
hhoAllOutAtt1 + hhoAllOutAtt2 + hhoAllOutAtt3

Number of Samples = hhoAllOutAtt1+hhoAllOutAtt2+hhoAllOutAtt3
Counter: hhoAllOutFail1.<hhoFail
hhoAllOutFail2.<hhoFail>
hhoAllOutAtt1
hhoAllOutAtt2
hhoAllOutAtt3
(1) IntraNodeB
(2) IntraRNC,
(3) InterRNCviaIur
A50023-X6009-A2-4-7619 47
Soft This KPI describes the ratio of dropped branch (radio link) additions
Handover related to the total number of branch (radio link) addition attempts.
Drop Rate
“Dropped branch additions” describe interrupted soft handovers due
to unavailability of the existing original radio link.
(intra ⎧ ⎫
NodeB, ⎪∑ shoAddIntraNodeBFail[11,18,31] + ⎪
intra RNC, ⎪⎪ i ⎪⎪
inter RNC ⎨∑ shoAddIntraRncFail[11,18,31] + ⎬
via Iur ⎪ i ⎪
combined) ⎪∑ shoAddInterRncFail[11,18,31] ⎪
⎪ i
⎩ ⎭⎪ *100%
BranchAddDR =
⎧shoAddIntraNodeBAtt[all ] + ⎫
⎪ ⎪
⎨shoAddIntraRncAtt[all ] + ⎬
⎪shoAddInterRncAtt[all ] ⎪
⎩ ⎭
Number of Samples =
shoAddInraNodeBAtt[all]+shoAddIntraRncAtt[all]+shoAddInterRncAtt[all]
Counter: shoAddIntraNodeBFail.<shoAddFail>
shoAddIntraRncFail.<shoAddFail>
shoAddInterRncFail.<shoAddFail>
shoAddIntraNodeBAtt.<shoAddCause>
shoAddIntraRncAtt.<shoAddCause>
shoAddInterRncAtt.<shoAddCause>
Hard This KPI provides the ratio between unsuccessful outgoing hard per
Handover handovers related to the attempted outgoing hard handovers. Cell
Failure
“Handover failure” describes unsuccessful handovers with the re-
Rate
connection to the originating cell.
⎧ ⎫
(intra ⎪∑ hhoAllOutFail1[i ] + ⎪
NodeB, ⎪⎪ i ⎪⎪
intra RNC, ⎨∑ hhoAllOutF ail2[i ] + ⎬
inter RNC ⎪ i ⎪
via Iur ⎪∑ hhoAllOutFail3[i ] ⎪
combined) ⎪⎩ i ⎪⎭
HHOFR = *100%
hhoAllOutAtt1 + hhoAllOutAtt2 + hhoAllOutAtt3
Number of Samples = hhoAllOutAtt1+hhoAllOutAtt2+hhoAllOutAtt3
Counter: hhoAllOutFail1.<hhoFail
hhoAllOutAtt1,
hhoAllOutAtt2
hhoAllOutAtt3
(1) IntraNodeB
(2) IntraRNC
(3) InterRNCviaIur
48 A50023-X6009-A2-4-7619
Soft This KPI describes the ratio of unsuccessful branch (radio link) per
Handover additions related to the total number of branch (radio link) addition Cell
Failure attempts.
Rate
“Unsuccessful branch additions” describe failed soft handovers with
availability of the existing active link set
(intra ⎧ ⎫
NodeB, ⎪∑ shoAddIntraNodeBFail[i ] + ⎪
intra RNC, ⎪⎪ i ⎪⎪
inter RNC ⎨∑ shoAddIntr aRncFail[ i ] + ⎬
via Iur ⎪ i ⎪
combined) ⎪∑ shoAddInterRncFail[i ] ⎪
⎪ i
⎩ ⎭⎪ *100%
BranchAddFR =
⎧shoAddIntraNodeBAtt[all ] + ⎫
⎪ ⎪
⎨shoAddIntraRncAtt[all ] + ⎬
⎪shoAddInterRncAtt[all ] ⎪
⎩ ⎭
Number of Samples =
shoAddInraNodeBAtt[all]+shoAddIntraRncAtt[all]+shoAddInterRncAtt[all]
Mobility
Counter: shoAddIntraNodeBFail.<shoAddFail>
shoAddIntraRncFail.<shoAddFail>
shoAddInterRncFail.<shoAddFail>
shoAddIntraNodeBAtt.<shoAddCause>
shoAddIntraRncAtt.<shoAddCause>
shoAddInterRncAtt.<shoAddCause>
Outgoing This KPI provides the ratio between unsuccessful outgoing inter per
Inter system handovers related to the attempted outgoing inter system Cell
System handovers.
Handover
“Handover failure” describes unsuccessful handovers with re-
failure rate
connection to originating cell
∑ hhoAllOutFail4[i ]
ISHHOOutFRpCell = i
*100%
hhoAllOutAtt4[all ]
Number of Samples = hhoAllOutAtt4
Counter: hhoAllOutFail4.<CSPS>-<irhoFail>
hhoAllOutAtt4.<CSPS>
(4) Inter System
A50023-X6009-A2-4-7619 49
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
50 A50023-X6009-A2-4-7619

Measurement Visualiser

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Measurement Visualiser

Uploaded by

Copyright:

Available Formats

s

Measurement Visualizer and

Important Notice on Product Safety

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

Copyright (C) Siemens AG 2006

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

1.1 About Measurement Visualizer (MVI) ................................................................... 7

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

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

3.1 Get licence for MySQL ....................................................................................... 10

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

4.1 The Server Part .................................................................................................. 12

4.2.5 Report Retrieval.................................................................................................. 23

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

5.1 The main new features in the EMV .................................................................... 26

6.1 No user and session management ..................................................................... 39

7.1 The object browser is empty right after start....................................................... 40

8.1 Overview of GSM and UMTS RTPM KPIs:......................................................... 41

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

1.2 About Enhanced Measurement Visualizer (EMV)

1.3 Data handling

1.4 Software Structure

1.5 System Requirement

2 INSTALLATION AND SET UP OF SOFTWARE

2.2 Installation and Set-up of the Client

3.1 Get licence for MySQL

3.2 Import NodeB relations

3.3 Set the input directory

3.4 Set the import filter

3.5 Start the MVI client

4.1 The Server Part

4.1.1 Configuration of the Server

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

o Base directory where the imported data files can be found

4.1.2 Backup and Restore Server Data

4.2 The Client

Figure 1: The Measurement Visualizer main window

4.2.1 Measurement Visualizer menu bar

4.2.1.1 File menu

The File menu contains the following menu item:

4.2.1.2 Edit menu

The Edit menu contains the following menu items:

4.2.1.2.1 Reload Object Browser

4.2.1.3 Administration menu

The Administration menu contains the following items:

4.2.1.3.1 Define Reports

Figure 2: The Report List dialog

Figure 3: The Define report dialog

4.2.1.3.2 Define Bandfilter

Figure 4: The BandFilter List dialog

Figure 5: The BandFilter Definition dialog

4.2.1.3.3 Manage Import Filters

Figure 6: The Import Filter Manager dialog

4.2.1.4 Help Menu

The Help Menu contains the following items:

4.2.1.4.1 User Manual

4.2.1.4.2 About Measurement Visualizer

Figure 7: The About Measurement Visualizer dialog of the MVI

4.2.2 Client tool bar

Reload Object Browser, described in 4.2.1.2.1

Logout, described in 4.2.1.1