Ultima Mentor V 6.7

Ultima Mentor v9.
7
User Guide
Ultima Mentor User Guide
Confidentiality, Copyright Notice & Disclaimer

Due to a policy of continuous product development and refinement, TEOCO Ltd. (and its
affiliates, together “TEOCO”) reserves the right to alter the specifications, representation,
descriptions and all other matters outlined in this publication without prior notice. No part of
this document, taken as a whole or separately, shall be deemed to be part of any contract for
a product or commitment of any kind. Furthermore, this document is provided “As Is” and
without any warranty.
This document is the property of TEOCO, which owns the sole and full rights including
copyright. TEOCO retains the sole property rights to all information contained in this
document, and without the written consent of TEOCO given by contract or otherwise in
writing, the document must not be copied, reprinted or reproduced in any manner or form, nor
transmitted in any form or by any means: electronic, mechanical, magnetic or otherwise,
either wholly or in part.
The information herein is designated highly confidential and is subject to all restrictions in any
law regarding such matters and the relevant confidentiality and non-disclosure clauses or
agreements issued with TEOCO prior to or after the disclosure. All the information in this
document is to be safeguarded and all steps must be taken to prevent it from being disclosed
to any person or entity other than the direct entity that received it directly from TEOCO.
TEOCO and Netrac® are trademarks of TEOCO.
All other company, brand or product names are trademarks or service marks of their
respective holders.
This is a legal notice and may not be removed or altered in any way.
COPYRIGHT © 2017 TEOCO LTD.
ALL RIGHTS RESERVED.
Your feedback is important to us: The TEOCO Documentation team takes many measures
in order to ensure that our work is of the highest quality.
If you found errors or feel that information is missing, please send your documentation-related
feedback to Documentation@teoco.com
Thank you,
The TEOCO Documentation team
i
Table of Contents
Objective of this User Guide .......................................................................................... 1
Introduction to Ultima Mentor ........................................................................................ 2
Standard Optimization Workflow ................................................................................................ 3
Detailed Optimization Workflow for Voice .................................................................................. 5
Detailed Optimization Workflow for Data ................................................................................... 6
Installation ...................................................................................................................... 7
System Requirements ................................................................................................................ 7
Installing Ultima Mentor.............................................................................................................. 7
Licensing Mentor ........................................................................................................................ 9
Obtaining a License Using a .c2v File ......................................................................................11
Updating Your License .............................................................................................................13
Upgrading Ultima Mentor .........................................................................................................14
Uninstalling Ultima Mentor .......................................................................................................16
Getting Started.............................................................................................................. 17
Launching Ultima Mentor for the First Time .............................................................................17
Ultima Mentor User Interface ....................................................................................... 18
Menus.......................................................................................................................................19
File Menu.............................................................................................................................19
Edit Menu ............................................................................................................................21
View Menu...........................................................................................................................22
Selection Menu ...................................................................................................................23
Network Menu .....................................................................................................................25
Layer Menu .........................................................................................................................28
Calculation Menu ................................................................................................................28
Tools Menu..........................................................................................................................30
Server Menu ........................................................................................................................30
Window Menu .....................................................................................................................31
Help Menu ...........................................................................................................................32
Keyboard Shortcuts .............................................................................................................32
Toolbars ...................................................................................................................................33
Standard Toolbar ................................................................................................................33
Workflow Toolbar ................................................................................................................35
Annotations Toolbar ............................................................................................................36
Panes .......................................................................................................................................36
Layers Pane ........................................................................................................................37
Calculations Pane ...............................................................................................................39
Sector Property Viewer Pane ..............................................................................................39
Neighbor List Viewer Pane..................................................................................................41
Statistics Viewer Pane ........................................................................................................43
Detailed Table Pane ............................................................................................................48
Event Viewer Pane ..............................................................................................................50
Legend Pane .......................................................................................................................54
Map Area ..................................................................................................................................55
Showing Incoming Neighbors .............................................................................................57
Showing Outgoing Neighbors .............................................................................................58
Showing Neighbor List Tier Numbers .................................................................................60
Viewing Neighbor List Changes ..........................................................................................61
Removing Lines Connecting Associated Sectors ...............................................................64
ii
Status Bar ................................................................................................................................65

Customizing the Display...........................................................................................................68
Displaying Panes ................................................................................................................68
Resizing Panes ...................................................................................................................73
Showing or Moving Toolbars...............................................................................................74
Showing or Hiding the Status Bar .......................................................................................74
Displaying Table Columns ..................................................................................................74
Setting Mentor Preferences .....................................................................................................76
Setting Default Legend Preferences ...................................................................................77
Time Filter per Available Data Source .....................................................................................80
Building the Mentor Network Environment................................................................. 81
Importing Network Data into Mentor ........................................................................................81
Selecting the General Import Parameters ...........................................................................82
Step 2 of the Import Wizard ................................................................................................85
Initializing the Imported Sectors ..........................................................................................85
Completing the Network Data .............................................................................................87
Synchronizing the Network with Updates from the Mentor Server .....................................93
Displaying Network Layers..................................................................................................94
Working with the Mentor Server .................................................................................. 95
Logging On to the Mentor Server .............................................................................................95
Submitting Network Changes to the Mentor Server ................................................................99
Synchronizing Network Updates from the Mentor Server......................................................101
Displaying Notifications ..........................................................................................................104
Importing Task Occurrences into Mentor ...............................................................................106
Viewing the Status of Server Tasks .......................................................................................107
Running Pending Tasks .........................................................................................................107
Working with Optimization Task Occurrences .......................................................................108
Scheduling Recurring Optimization Tasks ........................................................................108
Displaying Optimization Task Occurrences ......................................................................112
Editing Optimization Task Properties ................................................................................113
Viewing the Optimization Task History .............................................................................115
Working with Analysis Task Occurrences ..............................................................................118
Scheduling Recurring Analysis Tasks ...............................................................................118
Displaying Analysis Task Occurrences .............................................................................121
Editing Analysis Task Properties ......................................................................................122
Viewing Analysis Task History ..........................................................................................124
Working with APD Task Occurrences ....................................................................................126
Displaying APD Task Occurrences ...................................................................................127
Editing APD Task Properties.............................................................................................128
Viewing the APD Task History ..........................................................................................130
Viewing the APD Task Reports .........................................................................................133
Antenna Model Database ......................................................................................................135
Displaying the Antenna Models ........................................................................................135
Displaying the Antenna Model Properties .........................................................................138
Exporting Antenna Models ................................................................................................139
Collecting Call-Trace Data ......................................................................................... 140
Defining the UMTS/GSM Measurement Plan ........................................................................140
Viewing the Measurement Plan Reports ...........................................................................142
Modeling the Network ................................................................................................ 144
Importing a Model ..................................................................................................................144
Importing a Model File .......................................................................................................144
Importing a Model from the Mentor Server .......................................................................145
Exporting a Model ..................................................................................................................147
iii
Working with Selections ............................................................................................ 148

Creating Sector Selections ....................................................................................................148
Saving Sector Selections .......................................................................................................148
Saving Selections as a Layer .................................................................................................149
Loading Sector Selections .....................................................................................................150
Creating the Calculation Set ..................................................................................................150
Creating an Area Selection ....................................................................................................152
Saving an Area Selection .......................................................................................................152
Saving an Area Selection as a Layer .....................................................................................152
Loading an Area Selection .....................................................................................................153
Pasting Selections ..................................................................................................................154
Exporting Selected Sectors ....................................................................................................154
Displaying the Combined-Analysis Selection Set ..................................................................154
Modifying the Sector Selection ..............................................................................................154
Adding Keywords ...................................................................................................................155
Associating Sector Selections with Keywords .......................................................................155
Displaying Sector Selections by Keyword ..............................................................................157
Working with Layers ................................................................................................... 158
Mentor Layer System .............................................................................................................158
GIS Layers ........................................................................................................................159
Displaying Layers in the Detailed Table .................................................................................163
Showing/Hiding Layers ..........................................................................................................163
Moving Layers Up or Down ....................................................................................................165
Importing Layers ....................................................................................................................166
Exporting Layers ....................................................................................................................166
Defining Layer Properties.......................................................................................................167
Filtering the Detailed Table Pane Display ..............................................................................169
Displaying Histograms ...........................................................................................................172
Displaying the Layer Legend .................................................................................................173
Map Analysis ..........................................................................................................................175
Converting Raw Data into Text Format..................................................................................175
Working with Calculations ......................................................................................... 179
Scheduling Recurring Calculations ........................................................................................180
Loading Calculation Result Layers ........................................................................................180
Viewing the Calculation Layers in the Detailed Table ............................................................181
Opening Calculation Reports .................................................................................................182
Exporting the Optimization Plan to the Planning Tool ...........................................................183
Validating the Plan Implementation .......................................................................................184
Viewing the Optimization Progress ........................................................................................185
iv
Network Properties ..................................................................................................... 187

Defining Advanced Network Properties .................................................................................188
Access Distance Parameters ............................................................................................191
Antenna Sectors Optimization Parameters .......................................................................192
Area Code Optimization Parameters ................................................................................193
Defining Cell Footprint Report Parameters .......................................................................193
Ericsson Provisioning Parameters ....................................................................................194
Google Earth Display Parameters ....................................................................................196
GSM Positioning Parameters ............................................................................................197
HSDPA Optimization Parameters .....................................................................................197
Huawei Provisioning Parameters ......................................................................................197
Huawei SHOQualMin Optimization Parameters ...............................................................199
Import Parameters ............................................................................................................199
Inter-Frequency Neighbor List Optimization Parameters ..................................................200
IRAT Neighbor List Optimization Parameters ...................................................................202
LTE Log Processing Parameters ......................................................................................205
Map Parameters ................................................................................................................205
Neighbor List Editor Parameters .......................................................................................207
Neighbor List Optimization Parameters ............................................................................208
Neighbor List Optimization Parameters for Inactive Sectors ............................................218
Neighbor List Optimization Parameters for Indoor Sectors ..............................................219
Neighbor List Parameters for LTE Sectors .......................................................................221
NSN Provisioning Parameters ..........................................................................................228
Optimization Budget Parameters ......................................................................................232
PCI Plan and Sector Identification Parameters.................................................................233
Positioning Parameters .....................................................................................................234
Power Optimization Parameters .......................................................................................234
RAB Optimization Parameters ..........................................................................................235
Reports Parameters ..........................................................................................................236
Roaming Parameters ........................................................................................................236
SC Plan and Sector Identification Parameters..................................................................237
Time Zone Parameters .....................................................................................................238
UMTS GSM Measurement Plan Parameters ....................................................................238
UMTS Goals Parameters ..................................................................................................239
Virtual Drive Test Parameters ...........................................................................................239
Defining ZTE Provisioning Parameters .............................................................................240
Site Properties ............................................................................................................ 241
Displaying the Site Properties ................................................................................................241
Sector Properties ........................................................................................................ 244
Displaying UMTS Sector Properties ......................................................................................244
Displaying LTE Sector Properties ..........................................................................................246
Displaying GSM Sector Properties ........................................................................................247
Displaying Multi-selection Sector Properties..........................................................................248
Associating Sector Selections with Keywords ..................................................................248
Displaying Multi-Selection UMTS Sector Properties ..............................................................249
Displaying Multi-Selection LTE Sector Properties .................................................................252
Displaying Multi-selection GSM Sector Properties ................................................................254
Displaying Multi-Selection GSM Keyword Properties .......................................................255
Searching for Sectors .............................................................................................................258
Viewing Sectors in Google Earth ...........................................................................................259
v
Working with Planned Sites and Sectors .................................................................. 261

Importing Planned Sites .........................................................................................................261
Defining General Site Properties ......................................................................................262
Completing the Planned Site Data ....................................................................................262
Launching the New Site Wizard .............................................................................................268
Defining the General Site Properties ................................................................................269
Defining Sectors ................................................................................................................271
Adding Planned Sectors to Existing Sites ..............................................................................273
Exporting Planned Sites .........................................................................................................274
Deleting Planned Sectors.......................................................................................................275
Antenna Properties..................................................................................................... 276
Threshold-Crossing Alarms (TCA) ............................................................................ 277
Defining Threshold-Crossing Alarm Maps .............................................................................277
Viewing Alarm Reports...........................................................................................................281
Analyzing the Network ............................................................................................... 282
Launching the Analysis Wizard ..............................................................................................282
Defining General Analysis Properties ...............................................................................284
Defining Analysis Reports, Layers, and Statistics ............................................................286
Viewing the Analysis Summary .........................................................................................298
Duplicating Existing Analysis Calculations.............................................................................300
Analysis Reports ....................................................................................................................300
KPIs ........................................................................................................................................302
Ericsson UMTS KPIs .........................................................................................................302
Ericsson LTE KPIs ............................................................................................................314
Huawei UMTS KPIs ..........................................................................................................317
Huawei LTE KPIs ..............................................................................................................327
NSN UMTS KPIs ...............................................................................................................330
NSN LTE KPIs ..................................................................................................................340
ZTE UMTS KPIs ................................................................................................................340
ZTE LTE KPIs ...................................................................................................................350
Positioning-based Maps .........................................................................................................357
Displaying KPI Maps .........................................................................................................358
Displaying Performance Maps ..........................................................................................360
Displaying Drop Maps (UMTS and LTE) ...........................................................................366
Displaying Traffic Maps .....................................................................................................368
Displaying Server and Polluter Maps ................................................................................371
Displaying Arc Maps .........................................................................................................374
Displaying Combined Maps ..............................................................................................377
Using the Threshold Selector ............................................................................................382
Displaying Virtual Drive Test Maps ...................................................................................382
Displaying Mobile Drop Maps ...........................................................................................395
Displaying Access Failure Maps .......................................................................................399
Displaying Mobile IRAT Maps ...........................................................................................403
Displaying CSFB Maps .....................................................................................................406
Displaying Additional Maps ...............................................................................................413
GSM Maps .............................................................................................................................416
Displaying GSM Performance Maps .................................................................................416
Displaying GSM Server and Candidate Maps ..................................................................419
Displaying GSM Traffic Maps............................................................................................421
Displaying GSM Virtual Drive Test Maps ..........................................................................423
vi
Sector and Area Selection Statistics ......................................................................................426

Displaying UMTS and LTE Mobile Drop Statistics ............................................................427
Displaying UMTS and LTE Performance Statistics ..........................................................432
Displaying UMTS and LTE Server and Polluter Statistics ................................................438
Displaying GSM Mobile Drop Statistics ............................................................................445
Displaying GSM Performance Statistics ...........................................................................449
Displaying GSM Server and Candidate Statistics .............................................................454
Filtering the Map, Report, and Statistics Date and Time .......................................................460
Working with Map and Statistics Filters .................................................................................461
RAB Group ........................................................................................................................462
Profile ................................................................................................................................463
Mobility ..............................................................................................................................463
Release Cause ..................................................................................................................464
Networks ...........................................................................................................................465
Select Mobiles ...................................................................................................................466
Device Type ......................................................................................................................467
Device Capabilities ............................................................................................................468
Establishment Cause ........................................................................................................469
BCCH Frequency ..............................................................................................................470
Automatic Problem Detection (APD) ......................................................................... 471
Importing APD Task Occurrences into Mentor ......................................................................471
Viewing the APD Layers ........................................................................................................472
Viewing the APD Results in the Detailed Table .....................................................................475
Viewing the APD Results in the APD Problem Viewer ..........................................................478
Duplicating Existing APD Calculations ...................................................................................480
Resolving UMTS/GSM Discrepancies ....................................................................... 481
Resolve UMTS-GSM Discrepancies Report ..........................................................................483
SC Plan Optimization ................................................................................................. 484
Defining Advanced SC Plan Parameters ...............................................................................484
Launching the SC Optimization Wizard .................................................................................485
Defining General SC Properties ........................................................................................486
Defining SC Optimization Constraints ...............................................................................488
Viewing the SC Optimization Summary ............................................................................489
SC Report ..............................................................................................................................490
Scrambling Code Layers ........................................................................................................491
Exporting the SC Plan Changes ............................................................................................495
Displaying Potential Co-SC Conflicts .....................................................................................497
PCI Plan Optimization ................................................................................................ 499
Pre-Conditions for PCI Optimization ......................................................................................499
Defining Advanced PCI Plan Parameters ..............................................................................499
Launching the PCI Optimization Wizard ................................................................................500
Defining General PCI Properties .......................................................................................501
Defining PCI Optimization Constraints ..............................................................................502
Viewing the PCI Optimization Summary ...........................................................................503
Running the PCI Optimization Plan ..................................................................................504
PCI Report .............................................................................................................................505
PCI Layers .............................................................................................................................507
Displaying Potential Co-PCI Conflicts ....................................................................................510
vii
Area Code Optimization ............................................................................................. 512

Launching the Area Code Optimization Wizard .....................................................................512
Defining the General Area Code Properties .....................................................................514
Viewing the Area Code Optimization Summary and Running the Plan ............................515
Area Code Layers ..................................................................................................................516
Area Code Optimization Reports ...........................................................................................518
Scheduling Recurring Optimization Tasks .............................................................................520
Neighbor List Optimization ........................................................................................ 521
Neighbor List Overview ..........................................................................................................522
Neighbor List Optimization Workflow .....................................................................................523
Optimizing IRAT Networks .....................................................................................................523
Optimizing Inter-Frequency Networks....................................................................................523
Optimizing Multi-Vendor Networks.........................................................................................524
Defining the Neighbor List Optimization Parameters .............................................................526
Launching the Neighbor List Optimization Wizard .................................................................526
Defining General Neighbor List Properties .......................................................................527
Viewing the Neighbor List Optimization Summary ............................................................530
Neighbor List Layers ..............................................................................................................531
Viewing Neighbor List Changes .............................................................................................535
Showing Neighbor List Tier Numbers ....................................................................................538
Neighbor List Reports ............................................................................................................539
Implementing the Neighbor List Plan .....................................................................................540
Reviewing the Neighbor List Implementation Plan ...........................................................541
Exporting the Neighbor List Changes (UMTS Only) .........................................................541
Exporting the IRAT Neighbor List Changes ......................................................................544
Exporting the Optimization Plan to the Planning Tool ......................................................546
Validating the Plan Implementation ..................................................................................546
Submitting Network Changes to the Mentor Server ..............................................................548
Manual Neighbor List Optimization ........................................................................... 551
Using the Neighbor List Editor ...............................................................................................551
Editing the Neighbor List Plan ................................................................................................552
Editing the Original Neighbor List Plan from the Switch ........................................................554
Editing the Manual Neighbor List Plan ...................................................................................555
Neighbor List Editor Interface ................................................................................................557
Neighbor List Editor User Interface ...................................................................................558
Toolbar ..............................................................................................................................558
Neighbor List Viewer Pane (in Neighbor List Editor) ........................................................558
Summary Pane .................................................................................................................559
Status Bar..........................................................................................................................559
Viewing the Manual Neighbor List on the Map ......................................................................560
Adding Neighbors to the Neighbor List Plan ..........................................................................561
Removing Neighbors from the Neighbor List Plan .................................................................563
Changing the Neighbor Priority ..............................................................................................564
Adding and Using Network Constraints .................................................................................564
Saving Manual Changes as Constraints ...........................................................................564
Using New Network Constraints in the Current Plan ........................................................565
Reverting to the Original or Baseline Neighbor List Plan .......................................................566
Manual Neighbor List Report .................................................................................................567
Exporting the Neighbor List Changes (UMTS Only) ..............................................................567
Validating the Plan Implementation .......................................................................................570
viii
Antenna Sectors Optimization (UMTS Only) ............................................................. 572

Goals ......................................................................................................................................573
Sub-goals ..........................................................................................................................573
Tuning RF Optimization Strategy ...........................................................................................575
Launching the Antenna Sectors Optimization Wizard ...........................................................576
Defining General Optimization Properties .........................................................................577
Defining the Optimization Goals .......................................................................................579
Setting Optimization Constraints .......................................................................................583
Setting the Optimization Budget .......................................................................................585
Viewing the Optimization Summary ..................................................................................586
Antenna Sectors Optimization Layers ....................................................................................588
Viewing the Optimization Progress ........................................................................................591
Viewing the Optimized Changes .......................................................................................592
Viewing the Optimization Reports .....................................................................................593
Viewing the Best Solutions................................................................................................594
Viewing the Improvement Progress ..................................................................................594
Viewing the Optimization Reports ..........................................................................................596
Implementing the Antenna Sectors Optimization Plan ..........................................................597
Exporting the Power Plan ..................................................................................................597
Exporting the Antenna Sectors Plan .................................................................................598
Exporting the Optimization Plan to the Planning Tool ......................................................600
Validating the Plan Implementation ..................................................................................600
Parameters Plan Optimization ................................................................................... 602
Launching the Parameters Optimization Wizard ...................................................................602
Defining General Parameter Plan Properties....................................................................604
Selecting the Parameters to be Optimized (Ericsson Networks) ......................................605
Defining the Parameters to be Optimized (Huawei Networks) .........................................606
Viewing the Parameter Plan Optimization Summary ........................................................607
Viewing the Parameter Plan Reports .....................................................................................609
Exporting the Parameter Changes .........................................................................................610
Overshooter Resolution Optimization....................................................................... 612
Launching the Overshooter Resolution Wizard .....................................................................612
Defining General Overshooter Resolution Properties .......................................................613
Viewing the Overshooter Resolution Summary ................................................................615
Updating the Mentor Network Environment ............................................................. 618
Updating the Switch Dump Files ............................................................................................618
Importing the Latest UMTS Switch Dump Files ................................................................619
Importing the Switch Dump Data from the Mentor Server ................................................621
Completing the Switch Dump Data ...................................................................................622
ix
Network Reports ......................................................................................................... 628

GSM Network Import Details Report ......................................................................................629
GSM Network Import Details - Summary Tab...................................................................629
GSM Network Import Details - Messages Tab..................................................................629
GSM Network Import Summary Report .................................................................................630
Import Report .........................................................................................................................630
Import Tab .........................................................................................................................631
Import Warnings Tab .........................................................................................................632
Rejected NEs from Physical Antenna File Tab .................................................................632
Sector Carriers Rejected from Switch Tab ........................................................................633
LTE Cells Rejected from Switch Tab ................................................................................633
Sector Carriers Missing Switch Data Tab .........................................................................633
New Added from Switch Tab.............................................................................................634
New Added from LTE Switch Tab .....................................................................................634
Rejected Neighbors Tab ...................................................................................................634
Inactive Sectors Tab .........................................................................................................635
Unknown Neighbors Tab...................................................................................................635
Unknown Neighbors LTE Tab ...........................................................................................636
Neighbors Errors and Warnings Tab ................................................................................636
Sectors with Default Antenna Model Tab ..........................................................................637
Sectors with Different Power Settings Per Carrier Tab (Warnings) ..................................637
Co-SCs in Neighbor List Tab ............................................................................................638
Co-PCIs in Neighbor List Tab ...........................................................................................639
Import Details Tab .............................................................................................................640
Import Messages Report ........................................................................................................640
Import Warnings Report .........................................................................................................643
Model Errors and Warnings Report (UMTS) ..........................................................................644
General Information Tab ...................................................................................................644
Unidentified Legs in RRC Messages Tab .........................................................................646
Logged Errors and Warnings Tab .....................................................................................646
Sectors with Low Message Duration Tab .........................................................................647
Sectors with Low Traffic Reliability Tab (Warnings) .........................................................647
Locked Sector Carriers Tab ..............................................................................................648
Model Parsing Details Report (UMTS) ...................................................................................648
Sector Count Summary Table Tab ...................................................................................650
Hourly Data Statistics Tab.................................................................................................650
BH Data Statistics Tab ......................................................................................................651
BH Sector Data Statistics Tab ..........................................................................................652
Sector Carrier Data Statistics Tab ....................................................................................653
Traced Cells Tab ...............................................................................................................654
Model Errors and Warnings Report (LTE) .............................................................................655
Unidentified Legs in RRC Messages ................................................................................657
Sectors with Low Message Duration Tab .........................................................................658
Sectors with Low Volume Reliability Rate Tab .................................................................658
Model Parsing Details Report (LTE) ......................................................................................659
Busy Hours Table Tab ......................................................................................................661
Sector Count Summary Table Tab (LTE) .........................................................................661
Hourly Data Statistics Tab (LTE) ......................................................................................662
BH Data Statistics Tab (LTE) ............................................................................................663
BH Sector Data Statistics Tab (LTE) ................................................................................664
Sector Data Statistics Tab (LTE) ......................................................................................665
x
Objective of this User Guide

The objective of this user guide is to give the user a quick reference guide to start working
with Ultima Mentor. It assumes that the Mentor server is being used.
To use Ultima Mentor as a standalone unit, please refer to the Ultima Mentor Help and the
relevant "Required Data Inputs for <Vendor> Infrastructure" document.
1
Introduction to Ultima Mentor

TEOCO Ultima Mentor is a tool that enables mobile operators maximize network quality,
capacity, and coverage automatically for both voice and data using call trace–based mobile
measurements instead of prediction-based models. The optimization capabilities offered by
Mentor yield significant CapEx and OpEx savings. Mentor makes it possible to meet target
KPIs in an environment of fast growth and rapidly changing usage patterns typical of these
networks. Through an advanced process of data retrieval, parsing, and analysis, Mentor
builds an accurate and comprehensive view of the network performance and service quality.
Mentor streamlines the complex and time-consuming processes of analysis, troubleshooting,
and optimization by automatically providing solutions to problems that are identified in the
network.
When subscribers use their mobile handsets, the UEs constantly engage in complex
interactions with the network. As part of this interaction, the UEs provide specialized quality of
service reports that reflect the subscribers' quality of experience (QoE). Mentor builds upon
these mobile measurements to deliver analysis and supporting optimization functionality.
By using mobile measurements with Mentor, the concept of tedious and expensive prediction-
creation and calibration becomes obsolete. Mentor provides recommendations for network
tuning on an hourly basis, based on up-to-date traffic and user-experience information from
the network, resulting in engineers being able to keep their network at top performance levels.
Service providers can therefore commit to aggressive KPIs and be confident that they will
meet those goals. Mentor enables carriers to sustain peak performance levels continuously
over time.
Mentor puts the engineers in a position of proactive control, significantly reducing problems
that could lead to churn, revenue loss and reduced MOU (minutes of use).
2
Standard Optimization Workflow

The following shows the Mentor optimization workflow.
The Mentor workflow comprises the following steps:
Step 1: Construct the network environment

The Mentor network environment must accurately represent the relevant entities from the real
network. This is done by gathering the required data, meaning the site, sector, and antenna
configuration, updated neighbor lists, and specific network parameters from the OSS. After
creating the network environment, it can be imported automatically into the Mentor application
from the Mentor server, or by using the .mpr project files, or by importing the relevant
configuration files.
Step 2: Collect the call-trace data

The call-trace data is collected automatically from the OSS and is used as input for:
 Analyzing the network performance before starting the optimization phases
 Creating an accurate mobile-measurements-based model of the network for
optimization purposes (neighbor list, antenna sectors, and so on).
Step 3: Create a network model

Mentor requires the user to create or import a mobile-measurements model of the network
environment before analyzing or optimizing the network. The model must include all the
processed data required for the network analyses and optimizations, taken from the call trace
and KPI data.
You will be able to perform different levels of analysis in Mentor depending on the amount
and type of information in the model. For example, if the model includes positioning data, you
will be able to create traffic and drop call maps.
Step 4: Analyze the network performance before implementing changes

The network performance and quality indicators should be analyzed before optimizations are
executed so that you can identify problematic areas and define specific optimization goals for
each cluster. You can do this by analyzing the main performance KPIs of the network to
identify problems such as overloaded sectors, high drop rates, and other resource problems.
3
Step 5: Check whether the neighbor list should be optimized. If so, move to
step 6. If not, proceed to step 7.
It is very important that the neighbor list is optimized across the entire network before running
the antenna sectors optimization. If the neighbor list is not properly planned, the network
performance may be degraded.
In general, the neighbor list optimization is a very cost-effective process. It takes only a few
minutes to run, and combined with the automatic creation of the implementation script, it is
easy to implement, making its benefits potentially high.
Note: It is possible to use the neighbor list optimization feature just for validating whether
updating the neighbor list is necessary. If all the sectors are optimized and there are no
missing neighbors with high priorities, and most of the problems are minor priority issues, it
may be possible to skip the neighbor list optimization before or after the antenna sectors
optimization.
Step 6: Optimize the neighbor list plan

The network neighbor list plan is optimized within the application, based on RNC call-trace
data model and predefined constraints.
The recommended workflow should include two neighbor-list optimizations—before and after
the antenna sectors optimization—to optimize the neighbor list according to the new power or
tilt settings, which may cause a different level of interaction between the sectors. In any event,
prior to any optimization phase, you should collect new call-trace data and update the
environment and the model with the latest parameter and configuration settings.
Note: You should always ensure that no major configuration changes were made before
implementing an optimization plan otherwise you may be implementing a plan that is based
on outdated information.
Proceed to step 8.
Step 7: Optimize the antenna sectors plan

The network antenna sectors plan can be optimized within the application, based on a model
consisting of data retrieved from call-trace data and KPIs. The optimized solution is created
by the GA algorithm that is controlled by predefined sub-goals. This provides noise and
interference reduction, traffic balancing, and optimal power consumption in the cluster.
implementing an optimization plan, otherwise you may be implementing a plan that is based
on outdated information.
Step 8: Implement the neighbor list or antenna sectors optimization plan

After running an optimization plan within Mentor, use the Export Plan command to create a
script file containing the export results in a vendor-compatible format. The scripts should be
implemented in the network using vendor-specific tools.
Step 9: Validate the plan implementation
After you have implemented the optimized plan, validate that your changes have been
implemented. Review entries that were not implemented to identify the reason for this, and
then re-implement the plan, if required.
4
Step 10: Update the network environment

After validating that all the required changes were implemented correctly, you should update
the environment with the latest network configuration changes, by loading the latest switch
dump files from the network.
Detailed Optimization Workflow for Voice

The following shows the detailed workflow for voice optimization, assuming you are using the
Mentor server.
5
Detailed Optimization Workflow for Data

The following shows the detailed workflow for data optimization, assuming you are using the
Mentor server.
6
Installation
Ultima Mentor is a Windows-based standalone application that can be run on your PC.
Installing Ultima Mentor is simple and easy, and the Ultima Mentor Setup wizard guides you
through the entire installation process.
This chapter contains the following sections:
 System Requirements
 Installing Ultima Mentor
 Licensing Mentor
 Obtaining a License Using a c2v File
 Updating Your License
 Upgrading Ultima Mentor
 Uninstalling Ultima Mentor
System Requirements
Mentor is a Windows-based application that can be installed on any PC with the following
recommended system requirements:
 2 GHz dual-core processor
 Windows OS: 10/8.1/7/XP
 Microsoft Office (Excel): 2013/2010/2007/2003/2002/2000 – required for viewing
reports
 8GB RAM for optimized performance (4GB RAM minimum for client operation)
 Storage:
o 20GBs for client operation
o 180GBs for Mentor internal network-information storage (for typical/common
storage)
Storage may need to be increased, based on the number of networks stored on
the client.
 Monitor resolution: 1024*768
 Optional: Available USB port for security dongle
Installing Ultima Mentor

You can install Ultima Mentor on any computer that meets the minimum system requirements.
After you have installed Mentor, you can upgrade it whenever there are new versions, or
remove it from your computer.
To install Mentor for the first time

1. Close any running TEOCO applications.
2. Insert the provided CD, browse to the Ultima Mentor installation package, and click
the Ultima Mentor-9.7bxxx-Setup.exe file. The installation process is launched and
the Welcome to the Ultima Mentor Setup Wizard page opens.
3. Click Next. The License Agreement page opens.
4. Read the license agreement, and then click I accept the agreement to agree to the
terms of the agreement.
7
5. Click Next. The Installation Directory page opens, prompting you to select a
location in which to install Mentor.
6. Click Next to install Mentor in the default location. If you want to change the default
location, click Browse, and then select the folder in which to install Mentor from the
Select Directory dialog box, and click OK and then click Next to install Mentor in the
selected location. The Ultima Mentor Shortcuts page opens.
7. If required, clear the relevant check boxes to prevent the installation from adding the
Ultima Mentor shortcut icon to the desktop or to the Quick Launch bar.
8. Click Next to start the installation. The Installing page opens, displaying a progress
bar of the installation process. A shortcut to the Ultima Mentor application is
displayed on your desktop if required, and Ultima Mentor is added to the

Mentor Ultima group in the Start menu.
When the installation is complete, the Installation Completed Successfully page
opens informing you that the setup process was completed successfully.
9. If required, clear the Launch Ultima Mentor now check box to prevent Mentor from
starting automatically after installation.
10. Click Finish to complete the installation and close the wizard. If you selected to
launch Mentor, the Welcome to Ultima Mentor dialog box is displayed, enabling you
to license your version of Ultima Mentor.
After you have licensed Mentor, the TEOCO Ultima Mentor window is displayed,
showing no information, as no networks are available. The Connection dialog box is
also displayed, enabling you to define the path to the directory in which the Mentor
data files are to be stored.
The project data, analysis, optimization, and other calculation results, as well as any
other data that is imported into Mentor will be saved in this directory on your hard
disk. This data is saved in an internal format required by the database, and cannot be
manipulated.
11. Accept the default directory, or browse to the required directory.
12. Click OK.
8
Licensing Mentor
Upon starting Mentor for the first time on a new computer or after a major version upgrade,
you need to activate the product with a valid license.
You can also update your license any time in the future, for example, before it expires, or to
include additional features such as positioning-based maps, mobile drop reports, neighbor list
optimization, power and/or tilt optimization.
To activate the Mentor license

1. Ensure that you have an active internet connection.
2. In the Welcome to Ultima Mentor dialog box, select one of the following options for
activating your license:
o Enter the product key: Enter the product key received from Customer Support,
and click OK.
The License Activation Number dialog box is displayed.
 Enter the activation number you received from Customer Support in the field
provided.
9
 If proxy authentication is required, click Advanced, and then enter your proxy
user name and password in the fields provided.
 Click OK.
o Connect the dongle to any available USB port: Insert the supplied dongle in an
available USB port.
Note: Due to a security upgrade, the old dongles used in previous versions will
not work anymore.
o Select the license manager server from the network: Enter the name or IP
address of the license server.
3. Click OK. Mentor is launched, and you can now start using the application.
Note: In some cases, the methods described above may not work, and you will have to obtain
the license manually by sending a c2v file to Customer Support.
10
Obtaining a License Using a .c2v File

If you cannot activate your license automatically, you can manually activate the license by
sending a .c2v file to Customer Support, who will send you a .v2c file in return with the license
details.
To generate a .c2v file

1. From the Start menu, browse to Programs > Mentor Ultima > Utilities > Mentor
License Registration. The HASP SRM RUS dialog box is displayed.
2. In the Collect Key Status Information tab, click the Collect information button. A
standard Windows Save dialog box is displayed.
3. Browse to the location in which to create and save the file, and then enter the file
name in the File name field, for example, license_request, and click Save.
11
A license request confirmation is displayed.
4. Send the .c2v file to Customer Support via email or through the Customer Support
web site. TEOCO Customer Support will send you a *.v2c file in return, for example,
hasp_update.v2c.
5. Save the .v2c file in a temporary location on your disk.
6. In the HASP SRM RUS dialog box, click the Apply License Update tab.
7. In the Update file path, click the browse button . The Select the update file
for new license dialog box is displayed, enabling you to browse to the path of the
saved .v2c file received from customer support.
8. Click Apply update. As soon as you receive a successful action confirmation, the
license is activated, and you can use Mentor.
Note: If this procedure does not work, please contact Customer Support.
12
Updating Your License

Shortly before your Mentor license expires, you will receive a warning notifying you of this.
You can then either update the license immediately, or any time before the license expires.
To update your license

1. Ensure that you have an active internet connection.
2. On the Help menu, click License Update. The Welcome to Ultima Mentor dialog
box is displayed.
3. If you received a product key from Customer Support, select the Enter a product
key option, and then click OK. The License Activation Number dialog box is
displayed.
o Enter your product key.
13
o If proxy authentication is required, click Advanced, and then enter your proxy
user name and password in the fields provided.
o Click OK.
4. If you are working with a network dongle, ensure that your dongle is connected, and
then select the Connect the dongle to any available USB port option.
Note: Due to a security upgrade, the old dongles used in previous versions will not
work anymore.
5. If you are working with a network license, select the Select the license manager
server from the network option, and then enter the name or IP address of the
license server in the field provided.
6. Click OK. A confirmation message is displayed, notifying that Mentor must be
restarted in order for the license changes to be applied.
7. Click OK.
Upgrading Ultima Mentor

In order for the Mentor client and the Mentor server to be compatible and work together, they
have to be from the same version and build. A typical upgrade is initiated when the Mentor
client tries to establish a connection with a Mentor server that has been upgraded, making the
versions incompatible. If required, you can also manually upgrade Mentor.
There are 2 methods by which Mentor can be upgraded:
 Full Installation: The old build is uninstalled during the installation process, and the
new build or version is automatically installed in the same location as the previous
version. If Mentor is being upgraded to a new version, all existing networks created in
the previous two versions of Mentor are upgraded automatically the first time they are
opened in the new version.
 Quick Upgrade: Involves a much shorter file transfer and installation mechanism,
thereby reducing the time required to upgrade the product.
By default, the full installation is required for a new version release, while a quick upgrade is
run when a new build for the same version becomes available. However, this may change
depending on the nature of the changes within the different product builds, as decided by the
network administrator and defined in the Upgrade parameters in the Server Admin.
14
To upgrade Mentor while connecting to the Mentor server

1. On the Server menu, or in any dialog box prompting you to log on to the server, click
Log On. If your current version of Mentor is not compatible with the server version,
the Server Connection Failed dialog box is displayed:
2. Click Yes to download the compatible client version.

3. If only a quick upgrade is required, you will be prompted to save any unsaved
networks. Mentor will close, a command prompt window with a script execution will
appear for a few seconds, and then Mentor will reopen with the same build as the
server and a message notifying you of the successful upgrade.
4. If a full installation is required, a warning is displayed. Click Run and then click Run
again. The Welcome to the Ultima Mentor Setup Wizard page is displayed,
enabling you to install the compatible version of Mentor.
5. Follow the wizard's instructions, from step 3, below.
To manually upgrade to a later version of Mentor

1. Close any open TEOCO or Windows applications.
2. Locate the Ultima Mentor installation package on the provided CD, and click the
Ultima Mentor-Mentor-<build>-Setup.exe file. The Welcome to the Ultima Mentor
Setup Wizard page is displayed.
3. Click Next. The License Agreement page opens.
4. Read the license agreement, and then click I accept the agreement to agree to the
terms of the agreement.
5. Click Next. The Application Update page is displayed, enabling you to uninstall the
previous version of Mentor.
6. Ensure that the check box is selected, and click Next to uninstall the previous
version. The Installation Directory page opens, prompting you to select a location in
which to install Mentor.
7. Click Next to install Mentor in the default location. If you want to change the default
location, click Browse, and then select the folder in which to install Mentor from the
Select Directory dialog box, and click OK and then click Next to install Mentor in the
selected location. The Ultima Mentor Shortcuts page opens.
8. If required, clear the relevant check boxes to prevent the installation from adding the
Ultima Mentor shortcut icon to the desktop or to the Quick Launch bar.
15
9. Click Next to start the installation. The Installing page opens, displaying a progress
bar of the installation process. A shortcut to the Ultima Mentor application is
displayed on your desktop if required, and Ultima Mentor is added to the

Mentor Ultima group in the Start menu.
When the installation is complete, the Installation Completed Successfully page
opens informing you that the setup process was completed successfully.
10. If required, clear the Launch Ultima Mentor now check box to prevent Mentor from
starting automatically after installation.
11. Click Finish to complete the installation and launch the application. If a network was
open in the previous version, a progress bar is displayed while it is upgraded to the
new version, and displayed.
Uninstalling Ultima Mentor

You can uninstall Mentor at any time, if required. When you uninstall Mentor, the networks,
calculations, folders and so on are not removed, and can be used when you reinstall Mentor.
Note: Mentor is automatically uninstalled when upgrading to a later version.
To uninstall Ultima Mentor

1. Close Mentor.
2. On the Start menu, click Programs > Mentor Ultima > Utilities > Uninstall Ultima
Mentor.
-Or-
In the Ultima Mentor application folder, double-click Uninstall.exe. The Ultima
Mentor Uninstall page opens, displaying a confirmation message about removing
Mentor from your computer.
3. Click Next. The uninstallation process is launched, and a progress bar is displayed
while Mentor is being removed.
4. When the uninstallation has completed, click Finish to close the Ultima Mentor
Uninstall wizard. Mentor is removed from the Programs group in the Start menu, and
the shortcut is removed from your desktop and Quick Launch bar.
16
Getting Started
Launching Ultima Mentor for the First Time
When you launch Mentor for the first time, you must define the path in which the data files are
to be stored, and import the network on which to work. On subsequent launches, the
application automatically opens the last network on which you were working.
To launch Mentor for the first time
1. Double-click the Ultima Mentor shortcut on your desktop.

-OR-
From the Start menu, click Programs > Mentor Ultima > Ultima Mentor.
The TEOCO Ultima Mentor window is displayed, showing no information, as no
networks are available. The Connection dialog box is also displayed, enabling you to
define the path to the directory in which the Mentor data files are to be stored.
The project data, analysis, optimization, and other calculation results, as well as any
data that is imported to Mentor will be saved in this directory on your hard disk. This
data is saved in an internal format required by the database, and cannot be
manipulated.
2. Click OK to save the directory in the default path, or click the browse button to
select a new location and then click OK.
Note: It is recommended to keep the default location. However, you must ensure that
there is enough disk space.
3. Import a network into Mentor (or open an existing network if this is not the first time
you are launching Mentor).
Note: If this is the first time you are launching the current version of Mentor, all
existing networks that were created in the previous version are automatically
upgraded the first time they are opened in the new version of Mentor.
4. Create or import a model of the environment.
17
Ultima Mentor User Interface

The Mentor graphical user interface (GUI) is based on a flexible GIS product.
All Mentor functions are performed through the TEOCO Ultima Mentor main window, which is
made up of the following window elements:
 Menu Bar: Enables you to access the various Mentor menus, and their options.
 Toolbars: Enables you to access the various Mentor toolbars, and their options.
 Panes: Enables you to view the Layers, Calculations, Sector Properties, Neighbor
List, and Statistics details on the left of the main window, and the Detailed Table at
the bottom of the main window.
 Map Area: Enables you to view a two-dimensional map of the network. You can right-
click any network element in the map area to display related data, such as neighbors,
site, sector, antenna element properties, and so on.
 Status Bar: Displays information about the network, and the current sector selection.
If required, you can customize the display in the main window. For example, you can show or
hide any of the window elements, or dock or float the panes.
You can also set various GUI preferences, for example, the information displayed in the
status bar, how the legends are displayed, the path to the database files, and the application
used for comparing networks.
Note: All dates and times displayed in the user interface and in the reports are based on the
settings of your local machine.
18
Menus
The Mentor menu bar is located at the top of the main window.
The menu bar contains the following menus:

 File menu
 Edit menu
 View menu
 Selection menu
 Network menu
 Layer menu
 Calculation menu
 Tools menu
 Server menu
 Window menu
 Help menu
Most of the menu options can also be accessed from the toolbar buttons or by using keyboard
shortcuts.
File Menu
The File menu contains the following menu options:
Menu Option Description
New Network Enables you to import a new network into Mentor.
Open Network Enables you to open an existing network in Mentor.
Close Network Closes the currently open network.
Save Network Saves the current network.
Save Network Enables you to save the current network with a new name, or in a
As different location.
Versions Enables you to save different versions of the current network, which
can be used for comparison purposes.
19
Import Displays a sub-menu with the following options:

 Network Updates: Enables you to synchronize your network with
the latest changes on the server.
 Network Properties: Enables you to import a previously exported
file that includes all the advanced parameters controlling the
application and algorithm behavior.
 UMTS Switch Dump: Enables you to import the latest UMTS
switch dump files, after the network creation. This option deletes
the current model and all calculations in the network.
 Model: Enables you to import a model into Mentor.
 Planned Sites: Enables you to import a file containing the planned
sites.
 Neighbor Constraints: Enables you to import a previously
exported .txt file containing the neighbor list locking constraints.
Note: This option is enabled only once there is a model.
 Antenna Constraints: Enables you to import a previously exported
.txt file containing the antenna constraints.
 Sector Constraints: Enables you to import a previously exported
.txt file containing the sector constraints.
 SC Constraints: Enables you to import a previously exported .txt
file containing the scrambling code constraints.
 Terrain: Enables you to import a terrain file separately from the
Mentor environment.
Additionally, if you are using an external terrain file found on a
network or a remote storage device, and the file's remote
destination has changed, importing the terrain file will update the
Mentor environment with the new location of the remote file.
If required, you can embed the external terrain file, so that it can be
used when you are not connected to the external device.
Note: The new terrain file will overwrite the current terrain file.
 GSM KPIs: Enables you to import the KPI data for the selected
sectors.
20
Export Displays a sub-menu with the following options:

 Network: Enables you to export the network data to Mentor Format
files.
 Network to Planning Tool: Enables you to export the network
data to the planning tool.
 Network Properties: Enables you to export the current network
property settings to a .txt file.
 Model: Enables you to export the current model so that it can be
used in other environments with the same network configuration.
 Planned Sites: Enables you to export the planned sites to a .txt
file.
 Neighbor Constraints: Enables you to export the current neighbor
list locking constraints to a .txt file.
 Antenna Constraints: Enables you to export the current antenna
constraints to a .txt file.
 Sector Constraints: Enables you to export the current sector
constraints to a .txt file.
 SC Constraints: Enables you to export the current SC constraints
to a .txt file.
Print Enables you to print the current network display.
Preferences Enables you to define the various preferences regarding measurement

units, status bar display, legends, and so on. Note that these settings
influence all the networks.
<network Displays the last four Mentor networks that were opened.
name>
Exit Exits the application.
Edit Menu
The Edit menu contains the following menu options:
Undo Undoes the previous operation.
Redo Redoes the previously undone operation.
Copy Copies the selected annotation or layer and stores it on the clipboard.
Paste Pastes a selected annotation over the original annotation, or pastes a

selected layer in the required GIS folder.
21
Duplicate and Enables you to duplicate and edit a selected analysis calculation.
Edit
Delete Enables you to delete a selected calculation entity.
Find Enables you to search for a specific sector.
View Menu
The View menu contains the following menu options:
Legend Shows or hides the Legend pane.
Threshold Shows or hides the Threshold Selector, which enables you to change
Selector any of the map thresholds in a combined analysis.
Layers Shows or hides the Layers pane on the left of the main window.
Calculations Shows or hides the Calculations pane on the left of the main window.
Sector Shows or hides the Sector Property Viewer pane on the left of the
Property main window, which enables you to view the properties of a selected
Viewer sector on the map.
Neighbor List Shows or hides the Neighbor List Viewer pane on the left of the main
Viewer window. The Neighbor List Viewer pane enables you to view the
neighbor list of a selected sector on the map.
Statistics Shows or hides the Statistics Viewer window, which enables you to
Viewer view various RF-related network statistics on an area or sector
selection.
Event Viewer Shows or hides the Event Viewer pane at the bottom of the map area.
The Event Viewer pane enables you to view the events of a selected
mobile drop.
Toolbars Displays a sub-menu that enables you to select the toolbars to be

displayed in the application.
Status Bar Shows or hides the status bar at the bottom of the main window.
Previous/Next Toggles the zoom display between the last-used zoom scales.
Zoom
22
Map Scale Enables you to select the scale at which the map is displayed.
Fit to Network Adjusts the zoom scale to the size of the network, so that all the
available sectors are displayed on the map.
Fit to Adjusts the zoom scale to the size of the area or sector selection, so
Selection that the selection fills the map area.
Fit to Layer Adjusts the zoom scale to the size of the selected layer, so that the
layer fills the map area.
Properties Enables you to view the properties of the selected network entities.
Selection Menu
The Selection menu contains the following menu options:
Select None Cancels the previous selection so that no sectors are selected.
Select All Selects all the sectors in the network.

Sectors
Display Displays the selection set of the currently selected calculation on the
Selection Set map area.
on Map
Display Displays the calculation set of the currently selected calculation on the
Calculation map area.
Set on Map
Display Displays the optimized sectors outside of the selection set on the map
Additional area.
Affected
Sectors on
Map
Display Model Displays the model's selection set on the map area.
Selection Set
on Map
Display Model Displays the model's calculation set on the map area.
Calculation
Set on Map
Keyword Enables you to create new keywords or remove existing keywords.

Management
23
Select Sectors Enables you to select all the sectors that are associated with a
by Keyword specified keyword.
Save Enables you to save the current selection as a layer, which will then be
Selection as displayed in the list of GIS layers in the Layers pane.
Layer
Load Enables you to load a saved sector selection.

Selection
Save Saves the sector selection so that you can load it in the future.
Selection
Load Area Enables you to load a saved area selection.

Selection
Save Area Saves the area selection so that you can load it in the future.
Selection
Copy Selected Copies the selected sectors to the clipboard.

Sectors to
Clipboard
Select Sectors Displays the sectors from the clipboard as a selection on the map area.
from
Clipboard on
Map
<selection The last four selections that were saved or loaded.

name>
24
Network Menu
The Network menu contains the following menu options:
Planned Sites Displays a sub-menu with the following options:

 New Site: Enables you to add a new site at a selected location on
the map.
 New Sector: Enables you to add a new sector to an existing or
planned site.
Show Displays a sub-menu with the following options:

Neighbors
 Show Outgoing Neighbors: Enables you to display the outgoing
handovers of a selected UMTS sector, and save the neighbors as
a layer.
 Show Incoming Neighbors: Enables you to display the incoming
handovers of a selected UMTS sector, and save the neighbors as
a layer.
 Show Inter-frequency Outgoing Neighbors: Enables you to
display the outgoing handovers of a selected sector to a different
carrier, and save the neighbors as a layer.
 Show Inter-frequency Incoming Neighbors: Enables you to
display the incoming handovers of a selected sector from a
different carrier, and save the neighbors as a layer.
 UMTS/GSM Neighbors, which displays a sub-menu with the
following options:
o Show Outgoing Neighbors: Enables you to display the
outgoing GSM neighbors of a selected UMTS sector, and save
the neighbors as a layer.
o Show Incoming Neighbors: Enables you to view the
incoming GSM neighbors of a selected UMTS sector, and save
the neighbors as a layer.

Neighbor List
 To UMTS: Enables you to view the neighbor list changes for
Changes
handovers to UMTS sectors, and save the changes as a layer.
 To UMTS Inter Freq: Enables you to view the neighbor list
changes for handovers to UMTS sectors from a different carrier,
and to save the changes as a layer.
 To GSM: Enables you to view the neighbor list changes for
handovers to neighboring GSM sectors, and save the changes as
a layer.
Show Enables you to view the relationship between the source and target
Neighbor List sectors. For example, natural source and target sectors are Tier1
Tier Numbers neighbors, and the source sector and the neighbor of the target sector
are Tier2 neighbors, and so on. You can save the tier numbers as a
layer.
25
Model Enables you to launch the Model wizard to create a model of the
environment.
Show Model Displays the model's properties.

Properties
Show Model Displays the Model progress bar, showing the progress of the model
Progress creation. This option is available only if you have previously minimized
the progress bar.
Show Potential Enables you to display potential co-SC conflicts on the map area.
Co-SC
Show KPIs Enables you to display and save a layer showing selected KPIs, as
well as to view the KPIs in the Detailed Table.
Note: This option is available only if your license supports positioning-
based maps, and your model includes positioning.
Show Maps Displays a sub-menu with the following RF-map options:

 Performance: Enables you to display performance-type layers on
the map.
 Drop: Enables you to display drop-type layers on the map.
 Traffic: Enables you to display traffic-type layers on the map.
 Server and Polluter: Enables you to display server and polluter–
type layers on the map.
 Arc: Enables you to display arcs showing selected KPIs at either
predefined distance increments from selected sectors, or according
to predefined percentages.
 Combined: Enables you to display a layer showing a selected map
that has been filtered by one or more maps with specific
thresholds.
 GSM Maps: Displays a sub-menu with the following map options:
o Performance: Enables you to display GSM performance-type
layers on the map.
o Best Server: Enables you to display best server–type layers on
the map.
o Traffic: Enables you to display GSM traffic-type layers on the
map.
Note: These options are available only if your license supports
positioning-based maps, and your model includes positioning.
26
Show Event Displays a sub-menu with the following event map options:
Maps
 Virtual Drive Test: Enables you to display an immediate
visualization of call flow events associated with specific sectors and
terminals, for a specific time.
 Drop: Enables you to display mobile drops, according to the IMSIs
or IMEIs of the mobile handsets, on the map.
 Access Failure: Enables you to display a layer showing calls that
dropped due to access failure.
 IRAT: Enables you to display a layer showing the reported
handover events from the UMTS to the GSM network, per mobile
handset.
 GSM Maps: Displays a sub-menu with the following map option:
o Virtual Drive Test Map: Enables you to display an immediate
visualization of GSM call flow events associated with specific
sectors and terminals, for a specific time.
Note: These options are available only if your license supports
positioning-based maps, and your model includes positioning.

Statistics
 Show Mobile Drop Statistics: Enables you to display the drop
reasons for the area or sector selection in the Statistics viewer.
 Show Performance Statistics: Enables you to display selected
performance statistics for the area or sector selection in the
Statistics viewer.
 Show Server and Polluter Statistics: Enables you to display
selected server and polluter statistics for the area or sector
selection in the Statistics viewer.
Save Map as Enables you to save the current map as a layer.

Layer
Open Network Enables you to select the network report to be displayed.

Reports
Load Network Enables you to display network-related layers, for example sectors
Layers with missing data, or sectors that are locked for optimization.
Network Displays the properties of the current network.

Properties
27
Layer Menu
The Layer menu contains the following menu options.
Move Up Moves the selected layer one step up in the Layers list.
Move Down Moves the selected layer one step down in the Layers list.
Reset to Resets all the settings (legend, label, and symbol) in the selected layer
Default to their factory default settings. If required you can reset only selected
Settings settings.
Import Layer Enables you to import a selected layer from an external source.
Export Layer Enables you to export the selected layer to an external source.
New Folder Enables you to create a new folder under the GIS category, into which
you can copy or move GIS or calculation layers.
Detailed Table Displays the Detailed Table pane, which shows the properties of the
selected network or calculation layer.
Histogram Displays a histogram of the selected map layer.
Calculation Menu
The Calculation menu contains the following menu options:
New Displays a sub-menu with the following options:

 Analysis: Enables you to start a new analysis calculation.
 Neighbor List Plan: Enables you to start a new neighbor list
optimization calculation.
 Manual Neighbor List Plan: Enables you to edit an existing
neighbor list plan.
 Parameters Plan: Enables you to start a new parameter
Note: This feature is currently supported for Ericsson and Huawei
networks only.
 SC Plan: Enables you to start a new SC optimization calculation.
 PCI Plan: Enables you to start a new PCI optimization calculation.
 Antenna Sectors Plan: Enables you to start a new antenna
 Overshooter Resolution Plan: Enables you to start a new
overshooter optimization calculation.
 Area Code Plan: Enables you to start a new area code
28
Load Layers Enables you to load selected layers onto the map.
Open Reports Enables you to open the selected calculation's reports.
Run Restarts an antenna sectors calculation that has been stopped.
Stop Stops a running calculation.
Save Template Enables you to save all the user-defined calculation settings, such as
filters, reports, goals, constraints, etc. that were used in the
calculation, as a template for future runs.
Show Change Displays the values of each sector, before and after the optimization.
List
Export Plan Enables you to export the parameters plan, neighbor list plan, or the
power plan in an antenna sectors plan.
Export Plan to Enables you to export the neighbor list plan or the power optimization
Planning Tool plan to a planning tool, for example ASSET.
Validate Plan Enables you to verify whether the recommended optimization changes
Implementation were implemented.
Open Enables you to run or stop the optimization, as well as monitor the
Optimization progress of the antenna sectors optimization process.
Progress
Dialog
Schedule as Enables you to schedule the Mentor server to run a selected

Optimization optimization automatically at a specific time.
Task
Schedule as Enables you to schedule the Mentor server to run a selected analysis
Analysis Task automatically at a specific time.
29
Tools Menu
The Tools menu contains the following menu options:
Network Enables you to manage the networks saved in the system.

Manager
Show in Displays the location of the selected site in Google Earth.

Google Earth
Convert Raw Enables you to convert raw data from a selected area into text format
Data to Text so that it can be imported into other applications, for example ASSET
Format Design.
Resolve Creates a script that automatically resolves all UMTS/GSM

UMTS/GSM discrepancies.
Discrepancies
Note: This option is enabled only if you have a multi-technology
network that includes GSM.
UMTS/GSM Enables you to generate an optimized plan to record mobile

Measurement measurements for selected UMTS sectors in neighboring GSM
Plan networks.
Note: This option is enabled only if you have a multi-technology
network that includes GSM.
Map Analysis Launches the Map Analysis wizard that enables you to carry out
mathematical operations on the values of up to eight loaded raster
map layers.
Server Menu
The Server menu contains the following menu options:
Submit Enables you to submit the recommended changes directly to the

Network Mentor server.
Changes to
Server
Run Automatic Enables you to manually check for and download updates from the
Updates server immediately, without waiting for the configured time.
Stop Automatic Enables you to stop downloading updates from the server.
Updates
30
Server Admin Launches the Server Admin application.

Note: If you have installed the Server Admin application locally, you
will have to navigate to the executable file the first time you launch the
application.
Notifications Displays the server notifications relevant to the clusters assigned to

you.
Optimization Displays the optimization task occurrences relevant to the clusters

Task assigned to you.
Occurrences
Analysis Task Displays the analysis task occurrences relevant to the clusters
Occurrences assigned to you.
APD Task Displays the APD task occurrences relevant to the clusters assigned
Occurrences to you.
Antenna Displays a list of antenna models relevant to the clusters assigned to

Models you.
Save Switch Enables you to save switch dump files from the server in a local
Dump in a folder.
Local Folder
Log On Enables you to log on to the Mentor server.
Log Off Enables you to log off from the Mentor server.
Window Menu
The Window menu enables you to select the network to display from a list of currently open
networks.
To display a network on the map, click its name. A is displayed next to the name of the
currently displayed network.
31
Help Menu
The Help menu contains the following menu options:
Help Contents Displays this Help file.
TEOCO on the Displays the TEOCO Web site.

Web
TEOCO Enables you to log in to the TEOCO Support Center in the TEOCO
Support Web site.
License Update Enables you to update your license with a license key from Customer
Support, or using a license manager on the network.
About TEOCO Displays information about the currently installed version, and the
Ultima Mentor license agreement.
Keyboard Shortcuts
The following hotkeys are available in Mentor:
Ctrl+N — New Network (File menu)
Ctrl+O — Open Network (File menu)
Ctrl+S — Save Network (File menu)
Ctrl+P — Print (File menu)
Ctrl+Q — Exit (File menu)
Ctrl+Z — Undo (Edit menu)
Ctrl+Y — Redo (Edit menu)
Ctrl+C — Copy (Edit menu)
Ctrl+V — Paste (Edit menu)
Delete — Delete (Edit menu)
Ctrl+F — Find (Edit menu)
F2 — Display Legend (View menu)
Shift+F2 — Display Threshold Selector (View menu)
F3 — Sector Property Viewer (View menu)
F4 — Display Properties (View menu)
F7 — Neighbor List Viewer (View menu)
Ctrl+H — Statistics Viewer (View menu)
Ctrl+D — Select None (Selection menu)
Ctrl+A — Select All Sectors (Selection menu)
Ctrl+Alt+C — Copy Selected Sectors to Clipboard (Selection menu)
32
Ctrl+Alt+V — Select Sectors from Clipboard on Map (Selection menu)

Ctrl+Alt+F — Show Mobile Drop Maps (Network menu)
Ctrl+H — Display Histogram (Layer menu)
F1 — Display Help (Help menu)
Alt+Shift+C — Increase Symbol Size (Right-click relevant GIS Layer menu)
Alt+Shift+D — Decrease Symbol Size (Right-click relevant GIS Layer menu)
Toolbars
The Mentor toolbars enable you to perform the most common Mentor operations.
Mentor displays the following toolbars in the toolbar section of the main window:
 Standard toolbar
 Workflow toolbar
There is also an Annotations toolbar, which can be accessed from the Layers pane, and
which is displayed at the bottom of the map area of the main window.
Standard Toolbar
The Standard toolbar contains the following options:
New Network: Enables you to import a network into Mentor.
Open Network: Enables you to open and load an existing Mentor

network.
Save Network: Saves the current network.
Find: Enables you to search for a specific sector.
Properties: Enables you to view the properties of the selected

network entity.
Legend: Displays the layer legend on the map.
Displays a sub-menu that enables you to select one of the following

options:
 Sector Selection: Enables you to select network entities on the
map, including creating a sector selection.
 Area Selection: Enables you to create an area selection on the
map.
33
Displays a sub-menu that enables you to select one of the following

options:
 Sector Lasso: Enables you to trace a non-rectangular area
around selected sectors. Double-click to select the sectors in the
lasso area.
 Area Lasso: Enables you to create a non-rectangular area.
Pan: Enables you to move the entire map in a specified direction.
Zoom In: Zooms in to a selected area, by increments.
Zoom Out: Zooms out of a selected area, by increments.
Previous/Next Zoom: Toggles the zoom display between the last-

used zoom scales.
Fit to Network: Adjusts the zoom scale to the size of the network, so
that all the available sectors are displayed in the map area.
Measurements: Measures the distance between two map elements.
Increase Sector Size: Magnifies the sites and sectors without

modifying the size of the area.
Decrease Sector Size: Decreases the size of the sites and sectors
without modifying the size of the area.
Show Threshold-Crossing Alarm Map: Enables you to display

alarms on the map for sectors with KPI values that cross predefined
thresholds.
Show KPIs: Enables you to select the KPIs to show in the map area.
Show Maps: Displays a sub-menu that enables you to select the call
trace–based map you would like to display in the map area:
 Performance
 Drop
 Traffic
 Server and Polluter
 Arc
 Combined
 GSM Maps: Displays a sub-menu that enables you to select the
GSM map you would like to display in the map area:
o Performance
o Best Server
o Traffic
34
Show Event Maps: Displays a sub-menu that enables you to select

the call trace–based event map you would like to display in the map
area.
 Virtual Drive Test
 Drop
 Access Failure
 IRAT
 CSFB
 Additional Maps
 GSM Maps: Displays a sub-menu that enables you to select the
GSM map to display in the map area.
o Virtual Drive Test Map
Computed Maps: Enables you to perform operations on selected

binned maps.
Show Statistics: Displays a sub-menu that enables you to select the

statistics to be displayed in the Statistics Viewer pane.
Show Neighbors: Displays a sub-menu that enables you to select

whether to show the incoming or outgoing neighbors for a selected
sector on the map, and save the neighbors as a layer. If you have a
multi-carrier network, you can show the inter-frequency incoming or
outgoing neighbors on the map. In addition, if you have a multi-
technology network that includes GSM, you can also show the IRAT
neighbors on the map.
Show Neighbor List Changes: Enables you view the changes made
to the neighbor list of a selected sector, and save it as a layer. If you
have a multi-carrier network, you can show the changes from a
neighbor from a different carrier, and if you have a multi-technology
network that includes GSM, you can also show the changes from a
GSM neighbor.
Workflow Toolbar
35
The Workflow toolbar contains the following options:
Enables you to create a new model.
Starts a new Analysis calculation.
Enables you to start a new Neighbor List Plan, Manual Neighbor List
Plan, Parameters Plan, SC Plan, PCI Plan, Area Code Plan, Antenna
Sectors Plan, or Overshooter Resolution Plan optimization.
Annotations Toolbar
You can add annotations to the map using the Annotations toolbar, which is displayed at the
bottom of the Mentor map. You can save these annotations on the map, and you can print the
annotation layer. By default, the Annotations toolbar is not displayed. For more information
about the Annotations toolbar, refer to the Ultima Mentor Help.
Panes
By default, the Ultima Mentor window displays two panes on the left of the main window.
 Layers Pane, which enables you to display or hide various layers on the map.
 Calculations Pane, which lists the calculations in the network, and their status.
If required, you can also display the following additional panes:
 Sector Property Viewer, which lists the properties of a selected UMTS sector on the
map.
 Neighbor List Viewer, which lists the sectors in the neighbor list of the selected
sector.
 Statistics Viewer, which displays a histogram showing KPI statistics of the sector or
area selection.
 Event Viewer, which lists the events of selected dropped calls.
 Detailed Table, which displays the properties of a selected layer.
 Legend, which displays the legend of the currently displayed map layer.
Note: The Event Viewer pane and the Detailed Table pane, which are both displayed at the
bottom of the map area, cannot be displayed simultaneously.
You can customize the way panes are displayed. For example, you can collapse or expand
panes, or float or dock them. Your preferences are saved and are applied each time you open
a network.
36
Layers Pane
The Layers pane is displayed on the top left of the main window. It enables you to display or
hide various layers on the map, as required.
Note: In order to display a layer on the map, you must also select the category to which it
belongs. For example, to display sites on the map, you must also select the Network
category.
The Layers pane displays the following layer categories:

 Annotations: Contains the Annotations layer.
 Network: Contains the Sites, Sectors and Antennas layers.
o If you have a multi-technology network, the technology of the sites and sectors is
also displayed.
37
o If your network contains multiple carriers and bands, a separate layer is displayed
for each one, and you can select whether to perform tasks such as exporting the
layer, displaying properties, and so on, for the entire sector layer or for each
carrier layer separately.
 Calculation Results: Contains any calculation layers that are loaded through the
Calculations pane or the Calculation menu. A branch is displayed for each
calculation.
 GIS: Contains the Terrain layer, which is imported by default with the network
environment, as well as any other GIS layers that are imported manually. You can
also create folders under the GIS category, containing layers from different
calculations.
 Web Maps: Enables you to display a Web map layer as a background on the map
area, enabling you to visualize the location of the affected area. If required, you can
define your web map preferences, such as the quality and transparency of the maps,
in the Web Maps tab of the Preferences dialog box. By default, you are connected to
the Web map server, and each action on the map downloads a new map image. If
required, you can disconnect from the Web map server, meaning that only cached
maps can be viewed.
Note: If you connect to the Internet using a proxy server, enter the proxy server
details in the Web Maps tab.
38
Calculations Pane
The Calculations pane lists the calculations that have taken place in the network, and their
current status.
While a calculation is running, its progress is displayed. As soon as it has successfully
completed running, its status changes to Valid. If a calculation is stopped, its status is
displayed as Stopped.
Note: Antenna sector optimizations are listed as Running while they search for the best
solutions, and Valid when they are stopped. If you stop the optimization before the best
solution is found, they are listed as Stopped.
To work with a calculation in the Calculations pane:

 Right-click the selected calculation, and then select the required option on the
shortcut menu.
Sector Property Viewer Pane

The Sector Property Viewer pane enables you to view the basic properties of a selected
sector. If required, you can also view the neighbor list of this sector in the Neighbor List
Viewer pane.
In order to view all available sector properties, and or edit these properties, open the UMTS,
LTE, or GSM Sector Properties dialog box.
Note: If you have a multi-technology network, only the UMTS or LTE sectors can be
displayed in the Sector Property Viewer pane.
39
To display the Sector Property Viewer pane

1. On the View menu, click Sector Property Viewer. The Sector Property Viewer
pane is displayed on the left side of the main window, under the Calculations pane.
2. Select a sector on the map. The sector's properties are displayed in the Sector
Property Viewer pane.
40
3. If required, you can filter the displayed properties by adding or removing property
fields.
o To remove a property, right-click the property and then click Remove this Field.
The selected property will be hidden, and will not be displayed in the Sector
o To display or hide multiple properties, right-click in the property area and then
click Customize. The relevant Customize Fields dialog box is displayed,
enabling you to select the properties that should be displayed.
For a description of the fields, refer to the Ultima Mentor Help.
Neighbor List Viewer Pane

The Neighbor List Viewer pane enables you to view the incoming or outgoing neighbor list of
a selected sector. It also enables you to display the neighbor list of one of the currently
selected sector's neighbors, or to flag a neighbor on the map.
By default, the Neighbor List Viewer pane is not displayed when you open Mentor for the first
time.
Note: If you have a multi-technology network, only the neighbors of UMTS and LTE sectors
can be viewed in the Neighbor List Viewer pane.
41
To use the Neighbor List Viewer pane

1. On the View menu, click Neighbor List Viewer. The Neighbor List Viewer pane is
displayed on the bottom left side of the main window.
2. To display a selected sector's neighbor list, select the sector on the map. The sector's
incoming or outgoing neighbor list, as well as the number of neighbors in each, is
displayed in the Neighbor List Viewer pane.
42
If required, you can:

o Change the fields that are displayed in the Neighbor List Viewer pane by
right-clicking the column header, and then selecting the required fields from the
list of available fields.
o Display the intra-frequency incoming or outgoing neighbors, the inter-frequency

incoming or outgoing neighbors, or the inter-RAT UMTS handovers (to or from
GSM neighbors).
o Flag a neighboring sector on the map by double-clicking the neighbor in the list, or
by selecting the neighbor in the list and then clicking Options and then Find
Neighbor. The display zooms in to display both the sector and its flagged
neighbor.
o Display the neighbor list of one of the current neighbors by selecting the neighbor
in the list, clicking Options and then Go to Neighbor. The display zooms in to the
selected sector, and its neighbor list is displayed in the Neighbor List Viewer
pane.
o Move between the previously selected sectors and their neighbor lists by clicking
the and buttons. You can also click the arrow to display a list of
previously selected sectors, and then select the required sector to display. To
zoom in to each selected sector, select Zoom In to Selected Sector.
Statistics Viewer Pane

If your model includes positioning, you can analyze an area or sector selection by displaying
the relevant RF statistics for the busy hour. Once the statistics are displayed in the Statistics
Viewer, you can select or display the associated sectors on the map, add or remove statistics,
set the axis range, as well as import or export the statistics.
Mentor supports three types of statistics:
 Mobile Drop
 Performance
 Server and Polluter
For each set of statistics you can view the serving sectors as well as view the influence of
specific sectors on the overall area statistics.
By default, the Statistics Viewer is a floating pane, but you can dock it to the left of the main
window, if required.
43
To view the Statistics Viewer pane

1. On the Network menu, click Show Statistics and then select the statistics category
to display on the map area.
-OR-
On the toolbar, click and then select the map type whose statistics you want to
view in the map area.
The relevant Statistics dialog box is displayed.
44
2. Filter the options as required and click OK. A progress bar is displayed while the
statistics are being created, and then the number of serving sectors and their
statistics are displayed in graph format in the Statistics Viewer.
Note: If there are more than 100 serving sectors, only the top 100 statistics will be
displayed.
3. If required, you can select previously saved statistics from the drop-down list. By
default, you can save up to 50 different statistics, but you can change this number in
the network Preferences.
4. You can right-click any sector in the Statistics Viewer pane, and then on the drop-
down menu, select or flag the sector on the map, or reset the Y-axis range. You can
also copy the statistics as an image, save the statistics as an image file, or print the
statistics.
45
5. Click the Statistics tab to view the statistics for the entire selection, and if relevant,
for a current selection, in text format.
6. If required, you can perform the following actions from the Options menu, depending
on whether the statistics are based on an area or sector selection:
o Rename Statistics: Displays the Rename Statistics dialog box, which enables
you to enter a new name for the statistics.
o Select Serving Sectors on Map: The sectors that affect the area or sector
selection are selected on the map. If the Zoom In to Selected or Displayed
Sectors option has been selected, the map zooms in to these sectors.
o Display Serving Sectors on Map: The sectors that affect the area or serving
selection are colored according to the legend. If the Zoom In to Selected or
Displayed Sectors option has been selected, the map zooms in to these sectors.
o Select Sector Selection on Map: The sector selection is selected on the map. If
the Zoom In to Selected Sectors option has been selected, the map zooms in to
these sectors.
46
o Display Sector Selection on Map: The sector selection is colored according to

the legend.
o Select Area Selection on Map: The area selection is selected on the map.
o Display Area Selection on Map: When selected, keeps the area selection
displayed on the map. To remove the selection, clear the check box.
o Add Statistics: Displays a sub-menu, enabling you to select additional statistics
types to display.
o Delete Statistics: Displays the Delete Statistics dialog box, showing all available
statistics. Select the statistics you want to delete and click Delete. Click OK to
close the dialog box.
o Axis Range: Enables you to select the range of values for the y-axis.
o Reset Axis Range: Resets the default axis range.

o Export Statistics: Enables you to export the statistics to a .txt file.
o Import Statistics: Enables you to import previously exported statistics.
o Zoom In to Selected or Displayed Sectors: Automatically zooms in to the
selected or displayed sectors on the map.
47
Detailed Table Pane

The Detailed Table pane enables you to view the properties of selected network and GIS
layers. It also enables you to view the properties of selected calculation layers, showing
similar information to the relevant reports. By default, all network elements are displayed, but
you can filter the table to display only those network elements that match your filter criteria.
You can also customize the table to display only selected property columns.
Note: You can display the Detailed Table for only for network layers and for calculation layers
that are displayed as vectors.
To view the Detailed Table pane

1. In the Layers pane, right-click the layer for which to display the Detailed Table, and
on the shortcut menu, click Detailed Table.
-OR-
In the Layers pane, select the layer for which to display the Detailed Table and on
the Layer menu, click Detailed Table.
The Detailed Table - <layer> pane is displayed at the bottom of the map area,
showing all the network elements in the selected layer.
2. If required, filter the displayed properties by adding or removing columns.

o To remove a column, right-click the header of the column you want to remove and
then click Remove this Column. The selected column will be hidden, and will not
be displayed in the Detailed Table.
o To display or hide multiple columns, right-click the column header and then click
Customize.
48
The relevant Customize Columns dialog box is displayed, enabling you to select
the columns to be displayed.
3. If required, you can perform the following actions by clicking on the Options menu.
Note: The menu options may change according to the layer displayed.
o Select Sectors on Map: Enables you to display the selected sectors on the map.
o Display Drops on Map: Displays a flag on each of the selected drops.
Note: This option is displayed for Mobile Drop maps only.
o Save Selection as Layer: Enables you to save the selected rows as a layer,
under the GIS category in the Layers pane. The new layer will be displayed in the
detailed table with the same legend and properties as the original layer.
Note: Currently this option is available for vector layers only.
o Filter: Enables you to filter the items displayed in the table.
o Clear Filter: Clears the previously defined filter. All the network elements in the
layer will be displayed in the table.
49
o Select All: Selects all the entities in the table.

o Show in Event Viewer: Enables you to display a selected call in the Event
Viewer pane.
Note: This option is displayed for Mobile Drop Maps only.
o Properties: Displays the Properties dialog box of the selected network element.
Note: This option is available for network layers only.
o Find: Enables you to search for selected text in the table.
o Export: Enables you to export the selected items to a .txt file.
o Zoom In to Selected Sectors: Displays all the selected sectors on the map, at
maximum zoom.
4. Click to close the Detailed Table pane.
Event Viewer Pane

The Event Viewer pane enables you to investigate and troubleshoot RAN conditions and
protocol messages exchanged right before abnormal failure events (drop calls, abnormal
disconnection from data sessions, access failures) as well as the events leading up to any
selected release causes for all types of services (voice and data) and technologies (UMTS
and GSM).
For example, you can create a mobile drop map, and then view the events of selected voice
or data failures in the Event Viewer, as well as the contents of each event. You can display
the events for a single call failure only, or add events for additional selected failures.
You can also create a virtual drive test map, and then view the events leading up to the
release of any type of session. When viewing a virtual drive test map in the Event Viewer, an
additional pane is displayed on the left of the Event Viewer, enabling you to filter the events
by call-related parameters such as IMSI, operator, roaming, etc.
Notes:
 You must have a valid license for the Event Viewer in order to view failures displayed
in the Mobile Drops report, as well as a license for the call database in order to
display virtual drive tests.
 You must be connected to the Mentor server to view calls in the Event Viewer.
Limited functionality is available for offline use, via the export/import functionality.
To view the Event Viewer pane

1. On the Mobile Drop map, right-click the mobile drop whose events you want to view,
and then click Show in Event Viewer. You will be prompted to log on to the Mentor
server if you have not already done so. The Show in Event Viewer dialog box is
displayed, enabling you to save the drop as a layer.
50
2. Select the Save as Layer check box, enter a new name for the layer if required, and
click OK. The Event Viewer pane is displayed at the bottom of the map area,
showing all the events for the selected mobile drop.
Tip: If you have previously saved a list of exported events, you can display the Event
Viewer from the View menu, and then import the events into the Event Viewer
without logging in to the server.
The following event properties can be displayed in the Event Viewer pane, depending
on the technology of the network (LTE/UMTS):
Property Description
Event Date & Time The date and time of each event.
No. The number of the event, for mapping purposes. Only

events with positioning data are given a number. All other
events are associated with the number closest to the time
of the event.
Event The type of event within the relevant domain: RRC,

NBAP, and RANAP.
Direction The direction of the event—Sent or Received.

The actual mapping of network components that are
involved in the process depends on the event's protocol:
 RRC protocol indicates an event is from/to the UE,
from the point of view of the RNC.
 NBAP protocol indicates an event that is from/to the
NodeB, from the point of view of the RNC.
 RANAP protocol indicates an event that is from/to the
RNC, from the point of view of the Core Network.
Active RNC 1..6 The RNCs to which the active sectors belong.
Active Sector 1...6 The names of the sectors that were assigned at the time
of the event.
Active Carrier 1...6 The carriers of the active sectors at the time of the event.
Active PCI/SC 1...6 The PCI/SC of the active sectors at the time of the event.
51
Active RSRP/RSCP The RSRP/RSCP of the active sectors at the time of the
1...6 event.
Active RSRQ/ECIO The RSRQ/ECIO of the active sectors at the time of the
1...6 event.
Candidate RNC The RNCs to which the candidate sectors belong.

1...6
Candidate Sector The names of the candidate sectors at the time of the
1...6 event.
Candidate Carrier The carriers of the candidate sectors at the time of the
1...6 event.
Candidate PCI/SC The PCI/SC of the candidate sectors at the time of the
1...6 event.
Candidate The RSRP/RSCP of the candidate sectors at the time of

RSRP/RSCP 1...6 the event.
Candidate The RSRQ/ECIO of the candidate sectors at the time of

RSRQ/ECIO 1...6 the event.
Downlink The RLC throughput in the downlink.

Throughput (Kbps)
Uplink Throughput The RLC throughput on the uplink.

(Kbps)
Latitude The latitude coordinate of the event.
Longitude The longitude coordinate of the event.

be displayed in the Event Viewer pane.
Customize.
52
The relevant Customize Columns dialog box is displayed, enabling you to select
the columns to be displayed or hidden.
o Display Drop on Map: Flags on the map the mobile drop to which the selected
event belongs. (This operation, which is also available by right-clicking on the
event, is available only if you have logged in to the server.)
o Filter: Enables you to filter the items displayed in the Event Viewer or in the event
contents.
o Clear Filter: Clears the previously defined filter. All events for the selected drops
will be displayed in the Event Viewer.
o Find: Enables you to search for selected text in the Event Viewer.
o Import Events: Enables you to import previously exported events, and display
them in the Event Viewer.
Note: Not all actions are available for events that were imported into the Event
Viewer.
o Export Events: Enables you to export the events list to a selected folder. The
events are saved as a .zip file and a properties file. You can later import the .zip
file into the viewer.
Note: This option is enabled only if you have permission to view IMSIs.
o Export: Enables you to export only the currently displayed events to a .txt file. For
example, if you performed a search operation or filtered the list, only those events
that matched the search or filter criteria and are displayed are exported.
53
o Show Contents: Opens a pane that displays the actual contents of the selected
event. Once the pane is open, it automatically displays the contents of any other
selected event. (You can also view the contents by double-clicking the event.)
Tip: You can search for text in the contents pane by pressing Ctrl+F.
5. If you want to add call events from additional failures, right-click the required failures
on the map and then click Add to Event Viewer. The events for these calls are
added to the events already displayed in the Event Viewer.
Legend Pane
The Legend pane enables you to view the legend of the currently displayed layer. Once the
legend is displayed, you can edit it as required, as well as set the transparency level of the
layer.
By default, the legend is a floating pane, which means it can be moved around the desktop,
but you can dock it to the right side of the main window, if required.
To display the legend

1. In the Layers pane, select the check box next to the layer whose legend you want to
display.
2. On the toolbar, click the Legend button .

-OR-
On the View menu, click Legend.
-OR-
Right-click the layer and then click Show Legend.
54
The layer legend is displayed on the map.
3. To dock the pane, right-click the title bar and then click Dock.
Map Area
The map area occupies the major part of the Mentor window. It displays a two-dimensional
map of the network, according to your selection in the Layers pane. For example, you can
display only the sites and sectors, without antennas, or you can display selected map layers.
You can right-click network elements to display network related data, for example, neighbors,
properties, and so on.
 If you hover over a sector on the map, a tooltip is displayed with the names of the site
and the antenna, and details of all loaded layers.
55
 If your network contains multiple carriers, each carrier is displayed as a sector. If

required, you can display the name of the carriers to which the sectors belong. For
example, 1, 2 and so on.
 If you have a multi-technology network, the sectors from each network are displayed
with a different symbol.
 If you selected to display the names of the carriers on the map, GSM sectors will be
marked with a G. If more than one band is present, the upper and lower bands are
displayed accordingly, with G-L for lower bands, and G-U for upper bands.
Single bands:
Multiple bands:
By default, the size and shape of the sectors is based on the beamwidth. If required, you can
change the appearance of the network elements when defining the layer properties.
56
Showing Incoming Neighbors

You can display the incoming neighbors of a selected sector on the map, before optimization,
or after a selected optimization plan. If you have a multi-carrier network you can display the
incoming neighbors from different carriers, and if you have a multi-technology network that
includes GSM, you can display the incoming GSM neighbors. Mentor displays lines
connecting the sector to its incoming neighbors, and colors these lines and the incoming
neighbors according to their priority. For example, neighbors with an incoming priority of 1-6
and the lines connecting them to the sector are displayed in blue, and those with an incoming
priority of 7-12 are displayed in green. You can remove the lines, if required, and you can
save the incoming neighbors as a layer that can be loaded at any time.
To show incoming neighbors

1. On the Network menu, click Show Neighbors, then Show Incoming Neighbors.
-OR-
On the toolbar, click the arrow next to the Show Neighbors button and then
select Show Incoming Neighbors.
Depending on your network, you can also select Show Inter-frequency Incoming
Neighbors to display handovers from other carriers, or UMTS/GSM Neighbors, and
then Show Incoming Neighbors to display the handovers from GSM neighbors.
Your cursor changes to enabling you to select the sector whose incoming
neighbors you want to view.
2. Select the required sector.
-OR-
Right-click the sector whose incoming neighbors you want to view, and on the
shortcut menu, click Show Neighbors then select Show Incoming Neighbors.
The Show Incoming Neighbors dialog box is displayed.
3. In the Neighbor plan field, select the neighbor list optimization according to which
the incoming neighbors will be displayed. By default, the neighbors are shown
according to the original neighbor list plan from the switch, before optimization.
4. In the Carrier field, select the carrier to which the incoming neighboring sectors
should belong.
5. Select the Save as layer check box to save the temporary layer to your disk. A
default name is displayed, which you can change if required.
Note: If you do not save the layer, it will disappear as soon as you click anywhere in
the map.
57
6. Click OK. The referenced sector is flagged, and the incoming neighbors are
highlighted on the map, according to their priority. Lines, the same color as the
highlighted neighbors, are displayed connecting the flagged sector to each of its
incoming neighbors. If there are no incoming neighbors, a message is displayed.
7. If required, remove the lines connecting the sectors.
Showing Outgoing Neighbors

You can view the outgoing neighbors of a selected sector on the map, before optimization, or
after a selected optimization plan. If you have a multi-carrier network, you can display the
outgoing neighbors to different carriers, and if you have a multi-technology network that
includes GSM, you can display the outgoing GSM neighbors. Mentor displays lines
connecting the sector to its outgoing neighbors, and colors these lines and the outgoing
neighbors according to their priority. For example, neighbors with an outgoing priority of 1-6
and the lines connecting them to the sector are displayed in blue, and those with an outgoing
priority of 7-12 are displayed in green. You can remove the lines, if required, and you can
save the outgoing neighbors as a layer that can be loaded at any time.
To show outgoing neighbors

1. On the Network menu, click Show Neighbors, then Show Outgoing Neighbors.
-OR-
On the toolbar, click the arrow next to the Show Neighbors button and then
click Show Outgoing Neighbors.
Depending on your network, you can also select Show Inter-frequency Outgoing
Neighbors to display handovers to other carriers, or UMTS/GSM Neighbors and
then Show Outgoing Neighbors to display handovers to GSM neighbors.
The cursor changes to enabling you to select the sector whose outgoing
58
2. Select the required sector.

-OR-
Right-click the sector whose outgoing neighbors you want to view, and on the
shortcut menu, click Show Neighbors then select Show Outgoing Neighbors.
The Show Outgoing Neighbors dialog box is displayed.
3. In the Neighbor plan field, select the neighbor list optimization according to which
the outgoing neighbors will be displayed. By default, the neighbors are shown
according to the original neighbor list plan from the switch, before optimization.
the map.
5. Click OK. The referenced sector is flagged, and the outgoing neighbors are
outgoing neighbors. If there are no outgoing neighbors, a message is displayed.
59
Showing Neighbor List Tier Numbers

The neighbor list tier numbers are used to show the relationship between the source and
target sectors, where the most natural neighbors are considered Tier1 neighbors. Mentor
determines the tier numbers based on arguments such as HO rate and distance from
neighboring sectors. For example, softer neighbors or the closest neighbors facing the source
sector are considered Tier1 neighbors, and the source sector and the neighbor of the target
sector are considered Tier2 neighbors, and so on.
You can display the tier numbers of a selected sector's neighbors on the map, and save the
tier numbers as a layer that can be loaded at any time.
To show the neighbor list tier numbers

1. On the map, right-click the sector whose neighbor list tier numbers you want to view,
and from the shortcut menu, click Show Neighbor List Tier Numbers. The
Neighbor List Tier Number dialog box is displayed.
the map.
60
3. Click OK. A progress bar is displayed while the tier numbers are being calculated,
and then the selected sector is flagged, and its neighbors are colored according to
the legend, enabling you to see the relationship between the source and its target
sectors.
Viewing Neighbor List Changes

After you have run a neighbor list optimization, you can view the recommended changes to
the neighbor list on the map. Mentor displays lines connecting a selected sector to all its
neighbors, and colors these lines and the neighbors according to the recommended changes.
For example, neighbors that are to be added to the neighbor list are displayed in green, and
those to be deleted from the neighbor list are displayed in red. You can remove the lines, if
required, and you can save the changes as a layer that can be loaded at any time.
If you have a multi-technology network that includes GSM, you can view the neighbor list
changes for handovers to either the UMTS or the neighboring GSM sectors. If you have a
multi-carrier network, you can also display the changes for handovers to neighbors from other
carriers.
To show the neighbor list changes

1. On the Network menu, click Show Neighbor List Changes and then select To
UMTS, To UMTS Inter Freq, or To GSM.
-OR-
On the toolbar, click the Show Neighbor List Changes button , and then select
either To UMTS, To UMTS Inter Freq, or To GSM.
The cursor changes to .
61
2. In the map area, click the sector whose recommended neighbor list changes you
want to view. The Neighbor List Changes dialog box is displayed.
3. In the Neighbor plan field, select the name of the neighbor list optimization for which
to display the relevant recommended changes.
the map.
5. Click OK. A progress bar is displayed during the layer creation, and while the layer is
being saved and loaded. The layer is displayed in the Layers pane, under the GIS
category, and on the map. The referenced sector is connected to its neighboring
sectors, which are colored according to their recommended changes, by a line in the
same color.
Neighbors can be added or removed, undergo no major changes meaning their

position in the neighbor list did not change by at least six positions, undergo major
changes up or down meaning their position in the neighbor list went up or down by at
least six positions, undergo no changes, or have a priority added or removed.
62
6. If required, you can change the legend by clicking the browse button . The
Legend dialog box is displayed, enabling you to change the legend as required.
7. If required, you can remove the lines connecting the sectors.
63
Removing Lines Connecting Associated Sectors

By default, Mentor displays lines connecting a selected sector to its incoming and outgoing
neighbors, as well as lines showing the recommended changes to the neighbor list. These
lines are displayed in the same colors as the highlighted sectors they are connecting to the
selected sector. If required, you can remove these lines.
To remove lines connecting a selected sector to its associated sectors

1. On the Network menu, click Network Properties. The Network Properties dialog
box is displayed.
2. Select the Advanced tab.
3. Click the button next to the Maps group. The group is expanded, showing the
default map values, per sector.
4. Edit the LINES_TO_NEIGHBORS parameter value by double-clicking in the Value
field, and then selecting No.
5. Click OK to save your changes and close the Network Properties dialog box.
64
Status Bar
The status bar, which is located at the bottom of the main window, displays information about
the current network.
To display/hide the status bar

 On the View menu, click Status Bar to toggle the status bar display.
According to the status of a running process and your preferences, the following information
can be displayed:
 A currently running process, for example, caching the Web maps.
Note: This information is displayed in a temporary cell that is displayed only while the
process is running.
 The status of the server connection. If Mentor is connected to the Mentor server, the
name of the server is displayed. If there are unread notifications from the server, an
icon is displayed. You can double-click to display the notifications.
 The status of the automatic update process that enables you to sync your network
with the latest Mentor server changes.
o Automatic Updates Disabled: Updates are not checked and retrieved
automatically. Possible reasons for this may be that the feature is disabled, you
are not logged in to the server, or the network name has changed.
o Automatic Updates Active: The automatic update mechanism is on and idle.
Mentor periodically checks in the background whether new updates are available.
o Downloading Updates: The automatic updates mechanism is currently retrieving
data from the server. Double-click the area to display a progress bar showing the
status of the import process.
o Automatic Updates Pending: Mentor has downloaded updates from the server,
and they can be integrated into your network by clicking Import in the dialog box
that is displayed, or by right-clicking the automatic updates area and then clicking
Import Updates.
65
You can right-click this area of the status bar to display a menu that enables you to
import the downloaded updates, run or stop the sync process, or activate/deactivate
the automatic update process.
 The number of running server tasks. You can hover over this area to display a tooltip
showing the number of each type of task that is running, or right-click this area to
display a menu that enables you to open the Server Admin, or the Optimization Task
Occurrences or the Analysis Task Occurrences dialog boxes. Double-click this area
to open the relevant running task's occurrences dialog box. (If you have both types of
tasks running simultaneously, the Optimization Task Occurrences dialog box will be
displayed.)
Note: This field is displayed only if you are connected to the Mentor server.
 The name of the cluster to which the network belongs, if it was imported from the
server. If the network was imported from an .mpr file or created using the
configuration files, Unknown is displayed.
66
 The status of the model. If a model exists, Model Exists, and the modeling period
and the date range of the call-trace data, are displayed. Double-click the Model
Exists area to display the model properties.
 The total number of selected sectors—active and not active—in both the UMTS and
LTE, or UMTS and GSM networks, if applicable. If an area was selected, Area
Selected is displayed.
 The distribution of the UMTS and GSM sectors selected. This field is displayed only
in networks containing GSM sectors as well.
 The map scale.
 The map coordinates at the cursor location.
If any of the status bar fields are cut off, you can hover over the field to display the information
in a tooltip.
67
Customizing the Display

The Mentor main window is made up of a menu bar, toolbars, panes, map area, and a status
bar.
You can customize the Mentor display to:
 Show or hide panes
 Collapse or expand panes
 Maximize a selected pane
 Minimize panes
 Dock or float panes
 Resize panes and windows
 Show and move toolbars
 Show or hide the status bar
Many of the panes and dialog boxes include tables. If required, you can select the columns to
be displayed in each table.
Displaying Panes
By default, the Calculations and Layers panes are displayed when you open Mentor for the
first time, but you can also add the Sector Property Viewer, Neighbor List Viewer, Statistics
Viewer, Detailed Table, and Legend.
Panes can be collapsed or expanded, floated or docked, as well as minimized to the side of
the map area. If required, you can maximize the viewing area in a selected pane by collapsing
all the other panes.
68
By default, all panes except the legend and the Statistics Viewer are docked, meaning they
are attached to the edge of the main window, but you can float them if required and then
move them around the desktop.
Your preferences will be saved and will be applied each time you open a network.
Note: The Detailed Table is docked at the bottom of the main window, and cannot be
collapsed or floated. If required, you can drag the top border of the pane to enlarge or
decrease its size, or you can click to close the pane.
69
To show a pane
 On the View menu, click the name of the pane to be displayed. The pane is docked
on the left side of the main window.
Note: To display the Detailed Table pane, select the layer to be displayed, and on
the Layers menu, click Detailed Table, or right-click the layer and then select
Detailed Table.
To hide a pane
 Right-click the pane header, and then click Hide. The pane closes, and the pane that
was above it is enlarged accordingly.
To collapse/expand a pane
 To collapse a pane, click on the top right corner of the pane, or right-click the pane
header and then click Collapse. The pane collapses, and only the pane header is
displayed. The pane above it is enlarged accordingly. If the top pane collapses, the
pane below it is enlarged.
 To expand a collapsed pane, click on the top right corner of the pane, or right-click
the pane header and then click Expand. The pane expands to show its contents.
70
To maximize a selected pane

 To maximize a pane, double-click the header of the pane you want to enlarge. All
other panes are collapsed, and the selected pane is expanded to fill the entire
available pane area.
71
To minimize/show all panes on the side of the window

 To minimize all the panes, click the button on the right corner of the top pane. All
panes are minimized to the side of the window, increasing the size of the map area.
 To show all previously minimized panes, click to redisplay the panes.

Note: The legend will be minimized to the right side of the main window, therefore the
direction of the arrows is reversed.
72
To float/dock a pane
 To float a docked pane, right-click the pane header and then click Float. The pane is
released from the side of the main window and can be dragged to any position on the
desktop.
 To dock a floating pane, right-click the pane header and then click Dock. The pane
returns to its default position on the side of the main window.
To change the width of a pane

 Drag the inner border of the pane until the pane is the required width.
Resizing Panes
You can resize the Mentor window, as well as the panes or the map view area.
To resize a pane or window

 Move the cursor over the border of the area you want to make bigger or smaller. The
cursor changes to a , enabling you to drag the border until the window, map area
or pane is the required size.
73
Showing or Moving Toolbars

You can show, hide, or move Mentor toolbars.
To display a toolbar
 On the View menu, click Toolbars and then select the toolbar you want to display.
The toolbar appears in the toolbar area at the top of the window.
To hide a toolbar
 On the View menu, click Toolbars and then deselect the toolbar you want to hide.
The toolbar disappears from the toolbar area.
To move a toolbar
 Click the left edge of the toolbar you want to move, and then drag the toolbar to the
required location in the toolbar area.
Showing or Hiding the Status Bar

By default, the Status bar is displayed when you start the Mentor application, but you can hide
it, if required.
To hide or show the Status bar

 On the View menu, click Status Bar to toggle the Status bar display.
Displaying Table Columns

Mentor enables you to select the table columns to be displayed in all relevant panes or dialog
boxes.
Note: In the Sector Property Viewer pane, you can select the fields to be displayed.
Depending on the number of columns in each table, you can right-click the table header and
then do the following:
 Up to 4 columns: Select or clear the checkboxes next to the names of the columns
to be displayed.
 4–8 columns: Select or clear the checkboxes next to the names of the columns to be
displayed, or hide a specific column, or customize the display by showing or hiding
multiple columns.
 Over 8 columns: Hide the selected column, or customize the display by showing or
hiding multiple columns.
74
To hide a column
1. In the relevant table, right-click a column in the column header. Depending on the
number of columns in the table, a menu is displayed:
2. Click Remove this Column, or clear the check boxes next to the columns to be
hidden. The selected column is hidden.
To hide or show multiple columns

1. In the relevant table, right-click the column header and then click Customize. The
Customize Columns dialog box is displayed:
2. Using the arrows, move the columns to be displayed to the Show these columns
pane, and the columns to be hidden to the Available columns pane.
3. Click OK to save your changes and close the Customize Columns dialog box.
75
Setting Mentor Preferences

You can set various GUI preferences, for example, the information displayed in the status bar,
how the legends are displayed, the path to the database files, and the application used for
comparing networks.
To set the Mentor preferences

1. On the File menu, click Preferences. The Preferences dialog box is displayed,
showing the General tab:
The Preferences dialog box displays the following tabs:

o General, which enables you to set general preferences, such as the units that are
used in measurements, and the fields that are displayed on the status bar.
o Default Legends, which enables you to customize the default legends of the
various Mentor layer maps.
o RABs, which enables you to customize the groups into which the RABs are
divided, and edit the RAB values.
o Directories, which enables you to select the location of the Mentor database and
files.
76
o External Tools, which enables you to enter the paths for the application used for
comparing networks, the Google Earth application, and the version of Excel used,
as well as to activate the planning tool option and define the connection settings.
o Web Maps, which enables you to define the way Web maps are displayed on the
map area. For example, the quality of the map, and the transparency level.
o Advanced, which enables you to define the settings that should be taken into
consideration during the import process, for example, the maximum number of
sectors with missing data before displaying the Sector Initialization step in the
Import wizard. You can also define the settings for reconnecting to the Mentor
server if the connection was lost. If you have a multi-carrier network, you can
display the names of the carriers to which the sectors belong, and if you have a
multi-technology network that includes GSM, you can define how to display the
GSM reports, if relevant.
For a detailed description of the Preferences dialog box and its tabs, refer to the Ultima
Mentor Help.
Setting Default Legend Preferences

You can customize the default legend of the various Mentor layer maps according to your
personal preferences.
To set the default legends

1. On the File menu, click Preferences. The Preferences dialog box is displayed.
2. Click the Default Legends tab.
77
A list of available layer maps is displayed in the left pane of the dialog box, and their
default legends in the right pane.
78
3. Select the layer map whose legend you want to customize and click Edit. The Edit
<name of layer> Legend dialog box is displayed.
You can do the following:

o Filter the legend display for number-based legends
o Select the type of legend to display
o Add a value to the legend
o Remove a value from the legend
o Load a legend definition file
o Save a legend definition file
o Reset a legend to its default factory values
For more information on legends, refer to the Ultima Mentor Help.
79
Time Filter per Available Data Source

Depending on the feature and data source you are using, the following time-range options are
available.
Available Data Sources

Feature
Client Model Rich Data Client Model and Rich Data
Binned Maps Busy Hour Hours Busy Hour

Hours
Arc Maps Busy Hour — Busy Hour
Number of Distinct — Hours Hours

Users
Drop Event Maps Busy Hour — Busy Hour

Hours Hours
Access Failure Busy Hour — Busy Hour

Event Maps
Hours Hours
IRAT Event Maps Busy Hour Hours Busy Hour

Hours Hours
CSFB Event Maps — Hours Hours

(LTE)
Drop Statistics Busy Hour Hours Busy Hour

Hours Hours
Performance Busy Hour Hours Busy Hour

Statistics
Hours
Server and Polluter Busy Hour Hours Busy Hour

Statistics
Hours
KPI Maps Busy Hour — Busy Hour

Hours Hours
80
Building the Mentor Network Environment

Importing Network Data into Mentor
You can import the latest configuration files directly from the Mentor server, which is the
recommended and easiest option. The Import wizard automatically compares the site data in
Mentor Format to the information in the new switch dump file, and if necessary enables you to
complete any missing data or make configuration changes.
To launch the Import wizard

 On the toolbar, click the New Network button to import a new network.
-OR-
On the File menu, click New Network.
The first step of the Import wizard is displayed, enabling you to select the method by
which to import the data.
The Import wizard contains the following steps:

 Step 1 General, enables you to select the method by which to import the network
data, as well as the location of the data. (Importing from the server is the
recommended option, and the one that is described in this User Guide.)
 Step 2 Sector Initialization, enables you to complete any missing data by exporting
it to Mentor Format, editing it, and then reimporting it.
Note: By default, this step is displayed only if there are more than 10 sectors missing
data. You can change this number, if required.
 Step 3 Data Completion, enables you to complete any missing data or make
configuration changes directly in the GUI without exporting the data to Mentor
Format, if required.
Note: If the Sector Initialization page is not displayed, the Data Completion page is
listed as Step 2.
81
Selecting the General Import Parameters

The General page of the Import wizard enables you to select the method for importing the
network data.
You can select one of the following methods:

 Import MPR: Enables you to import the project file in which the network data is
saved.
 Import Configuration Files: Enables you to import the network data from the files
and folders in which it is saved. If required, you can also import a configuration file
that was exported from a planning tool, for example, ASSET.
 Import from Server: Enables you to import the latest network data, including a
model, directly from the Mentor server. This is the recommended method.
 Import from Planning Tool: Enables you to import the network data from a planning
tool or the planning tool data.
Note: This option is displayed only if you have enabled integration with the planning
tool.
This User Guide focuses on the third option, Import from Server.
82
Importing the Network Data from the Mentor Server

If you are connected to the Mentor server, you can import the most up-to-date network
configuration data, including a model with selected model data, directly from the server. You
can also select whether to import the GSM sectors in the cluster, if relevant.
To import the network data from the Mentor server

1. In the Method field, select Import from Server. You will be prompted to log on to the
Mentor server if you have not already done so. A progress bar is displayed while
Mentor connects to the server.
The General page changes as follows:
2. In the Cluster field, select the cluster that represents the area you want to work with.
Clusters, which contain the network elements of an area, for example, RNCs, are
defined during the server setup. You can view details about the selected cluster in the
Cluster Information area at the bottom of the page.
3. By default, the date of the latest data is displayed in the Date field, but you can select
to import data from a different day by selecting a date from the drop-down calendar.
Note: The dates for which network data was collected are displayed in bold.
4. Select the Include terrain check box if you need the terrain file, for example, for
maps or positioning.
Note: Importing the terrain file is required only the first time the cluster is imported.
83
5. Select the Include GSM check box if you would like to import the GSM network as
well.
Note: This option is available only if the network being imported contains a GSM
configuration.
6. Select the Include Model check box to import a model at the same time that you
import the network.
7. By default, the model is imported for the entire cluster. To import a model for a
specific network element only, select the network element in the Network elements
field.
8. In the Modeling period field, select the hours for which to import the model.
9. By default, all dates for which there is model data are displayed in the Date range
field, but you can select specific days by clicking the browse button and then
selecting the required days in the Date Range dialog box. If the network contains
more than one network element, you can run your mouse over a bolded date to
display a tooltip showing which network elements were modeled on that day. Select
the dates to be included in the model using standard Windows functionality, and click
OK.
The first and last days selected are displayed in the Date range field, and the number
of actual days for which there is model data and the date of the latest data, are
displayed in the field below this.
10. Select the Include weekends check box if you want weekend data to be included in
the model. By default, only weekday data is included in the model.
11. If you require the model for neighbor list optimization and partial analysis only, select
the Quick model import check box. The imported model will be based on
performance counters only.
84
12. Click Next. A progress bar is displayed while the selected files are being imported
from the server. You can click the Details button to view a log of any warnings
generated during the import process.
Note: If there are any errors, the import process stops, and you can view a list of
errors by clicking the Details button. You must correct these errors, and then re-
import the network.
Step 2 of the Import Wizard

Depending on the numbers of sectors with missing data from the planning tool, the second
step of the Import wizard may be displayed as follows:
 If more than 10 sectors are missing data, or require configuration changes, the Sector
Initialization page is displayed, enabling you to export the network, complete the
network data in Mentor Format, and then import the .mpr file.
Note: By default, the Sector Initialization page is displayed only if there are more
than 10 sectors with missing data, but you can change this number in the Advanced
tab of the Preferences dialog box.
 If 10 or less sectors are missing data or require configuration changes, the Data
Completion page is displayed, enabling you to complete the network data directly in
the GUI, if required.
Note: By default, the Sector Initialization page is not displayed if there are 10 or
less sectors with missing data, but you can change this number in the Advanced tab
of the Preferences dialog box.
 If none of the sectors have incomplete data or require configuration changes, the
Data Completion page is displayed, enabling you to import the network.
Initializing the Imported Sectors

The Sector Initialization page enables you to view the number of each type of network
element that is missing information, and of the files that should be updated with this
information. If required, you can export the data to Mentor Format, update the relevant files
using an external text editor, and then reload the updated .mpr file to continue the import
process, or you can proceed directly to the Data Completion page and update specific
sectors directly in the GUI.
Note: By default, the Sector Initialization step is displayed only if more than 10 sectors are
missing data, but you can change this number in the Advanced tab of the Preferences
dialog box.
85
To initialize the sectors with missing data

1. In the first section of the Sector Initialization page, check which files should be
updated.
2. In the second section, click Save. The Save dialog box is displayed, enabling you to
browse to the folder in which to save the current network in Mentor Format, which is
in tab-delimited text, and can be modified using Microsoft Excel.
3. Open the folder in which the network files were saved, and then correct the files
according to the list of required updates in the first section of the page.
4. After you have updated all the required files, click Load. The Select Mentor Project
File Location dialog box is displayed, enabling you to browse to the updated .mpr
file.
5. Double-click the .mpr file. A progress bar is displayed while the updated network is
being imported.
6. Click Next to proceed to the Data Completion page.
86
Completing the Network Data

Once you have entered the path of the project file or the network data, and there are no errors
or sectors with missing data, you can import the network. Note that you can ignore some of
the errors or missing data if not relevant, for example, toy cells, etc.
Note: The Import wizard automatically handles the following situations, without notifying you:
 If a sector exists in Mentor Format, but part or all of its data is missing from the switch
dump, it will be listed as having missing data.
 If a sector does not exist in Mentor Format, but does appear in the switch dump, it
will be automatically added to the network.
Completing the Import Process - No Missing Data

If there is no missing data, you can import the network.
To complete the import process if there is no missing network data

1. In the Data Completion page, if required click Details to view any warnings that may
have been generated during the import process.
87
2. Click Finish to complete the data import process. A progress bar is displayed while
the data is validated and the reports are created, and then the Import Completed
dialog box is displayed.
3. Click Details to view the details of the import process, including any data
inconsistencies displayed in the Data Completion page. These messages can also be
viewed in the Import Messages report.
4. Click Layers to view layers showing any sectors that are missing data or that have
co-SC conflicts between neighbors. If you have imported a network that includes a
model, you can also view layers showing any sectors that are marked as locked, or
those that are locked due to low traffic. For more information, refer to the Ultima
Mentor Help.
5. Click Reports to view detailed reports of the import process. The Import report
Summary tab, which displays a summary of the network elements that were
imported into or rejected from the network database, is always displayed, while other
tabs are displayed only when relevant. For a detailed description of the tabs and
fields in the reports, refer to the Ultima Mentor Help.
6. Click Close to close the Import Completed dialog box, and to display the main
window, showing the imported network.
Note: Network data can be manipulated by exporting the network and manipulating the
Mentor Format files using a simple text editor.
Completing the Network Data

If you selected to skip the Sector Initialization step, or if there are less than 10 sectors with
missing data, meaning these sectors appear in the switch, but not all their mandatory data is
found in the Mentor Format, the sectors are displayed in red with in the Excluded sectors
pane in the Data Completion page. You can import the network without these sectors, or you
can complete the data directly in the GUI so that these sectors will also be included with the
imported data.
If there are any sectors that are missing antenna profile data, they are displayed as warnings
in the right pane. These sectors will be included in the import process with an
automatically assigned default profile, unless you enter the correct data.
88
To complete the network data

1. In the Data Completion page, select the sectors you would like to include in the
import process and click the right arrow button , or right-click the sectors and then
click Move.
The selected sectors move to the Excluded sectors to be edited and imported
pane.
89
The number of sectors with missing data to be completed and then imported is
displayed at the top of the pane.
2. In the Excluded sectors to be edited and imported pane, select a sector whose
data you want to complete, and click Edit.
90
The Sector Properties <name of sector> dialog box is displayed, enabling you to
enter the missing information. Tabs with missing information are displayed in red, with
an asterisk. Fields with missing information are highlighted in red.
91
Tip: If required, you can select multiple sectors and click Edit. The Sector
Properties (Multi-selection) dialog box is displayed, enabling you to edit the
properties of multiple sectors simultaneously.
3. Enter the missing information, and click OK to close the Sector Properties dialog
box. The name of the edited sector is now displayed in black, signifying that it
contains all the required data.
4. Repeat steps 2 to 3 for each sector you want to include in the import process.
the data is validated and the reports are created, and then the Import Completed
92
6. Click Details to view a log of the warnings generated during the import process,
including warnings notifying of differences in power settings between sectors in
different carriers.
co-SC conflicts between neighbors. If you have imported a network that includes a
model, you can also view layers showing any sectors that are marked as locked, or
those that are locked due to low traffic. For more information, refer to the Ultima
Mentor Help.
8. Click Reports to view a list of the reports generated during the import process. For
more information on the tabs and fields in each report, refer to the Ultima Mentor
Help.
9. Click Close to close the Import Completed dialog box, and to display the main
window, showing the imported network.
Synchronizing the Network with Updates from the Mentor Server

After the network has been imported, you can enable Mentor to automatically download
updates from the server for the currently open and active network. These updates, which
contain only new and changed data, include model days, switch dump updates, physical
configuration updates, for example new sites, and so on. This process is fully automated and
runs in the background without any user intervention. When Mentor has downloaded the
updates, they are copied to your computer so that you can import them and integrate them
into you environment.
For more information, see Synchronizing Network Updates from the Mentor Server.
93
Displaying Network Layers

After importing a network or updating the switch dump, you can display network-related layers
on the map, and in Google Earth. The available layers depend on the network that has been
imported, and whether it includes a model. For example, you can display layers showing
sectors with co-SC conflicts, sectors that have missing data, or sectors that are locked
because of their low traffic.
Network layers can be displayed as follows:
 On the map
 In Google Earth
 In the Detailed Table pane
94
Working with the Mentor Server

Mentor has been enhanced to work in conjunction with a server module that enables shorter
optimization cycles by supporting periodic automated data collection, generation of up-to-date
network traffic models, and recurring optimization plans.
This appendix describes how to work with the Mentor server. For more information, refer to
the Ultima Mentor Help and the Mentor Server Admin Help.
Logging On to the Mentor Server

Before you can access any information from the Mentor server, or use any of its features, you
must first log on to the server, using the Server Admin. The first time you log on to the server,
you will be prompted to specify a host server.
Note: If the server to which you wish to connect is not compatible with your current Mentor
version, a notification of such is displayed, enabling you to upgrade to the compatible version
of Mentor.
If you close the Server Admin while you are connected to a server, you will automatically be
reconnected to the same server the next time you access the Server Admin.
To log on to the Mentor server

1. On the Server menu, click Log On. The splash screen is displayed while the
application is loading.
Note: If this is the first time you are logging on to the server, the New Server dialog
box is displayed.
o In the Server name field, enter a nickname or alias to provide a logical name for
the system. The default name is Mentor Server.
o In the Host field, specify the name of an existing server. If you have a front-end
cluster, enter the name of one of the relevant hosts.
o Click OK.
95
The Log On to Mentor Server dialog box is displayed.
Note for Administrator Users: The first time you log in, you will be prompted to
change your password.
2. In the User name field, enter your user name, as defined by the system
administrator.
3. In the Password field, enter your password, as defined by the system administrator.
4. Depending on whether you have a single server or a front-end clustering server, in
the Server name drop-down list, select the server/server front-end clustering name to
which you want to connect.
Note: The server name represents all the hosts in this cluster, and you will
automatically be connected to any one of them.
5. Click the Advanced button if you want to add a new server group, remove a server
group, or edit the hosts within a server group. The window changes as follows:
96
6. To add a new server group, which can contain multiple servers, click New. The
following dialog box is displayed:
o Enter the name of the new server group in the Server name field.
o For each host you want to add to the group, enter the name of the host in the
Host name field.
o Click Add. The host is added to the list in the Hosts area, as shown below:
97
o Click OK. The server group is displayed in the Server area.
o Click OK to save your settings and exit the window.

7. To remove a server group, select the server group and then click Delete.
8. To add or remove the hosts in a server group, click Edit. The Server Properties
o To add a host to the server group, enter the name of the host to add to the group
in the Host name field and then click Add. The server is added to the list in the
Hosts area.
o To remove a host from a server group, select the host and then click Remove.
The host is removed from the server group.
o Click OK to save your settings and exit the window.
98
9. Click OK. The name of the server to which you connected is displayed in the status
bar, and you can now access the server data and use the server features.
Note: If your current version of Mentor is not compatible with the server version, the
Server Connection Failed dialog box is displayed notifying you of such, and
enabling you to upgrade to a compatible version of Mentor.
Submitting Network Changes to the Mentor Server

When you submit data to the server for the first time, or after you have imported the network
configuration from the server, modified it and then submitted your changes back to the server,
Mentor analyzes the data, and makes a list of discrepancies between the submitted data and
the data currently on the server, which you then have to accept or reject. The accepted
changes to the server network are sent to the server and divided up according to the clusters
to which they belong. All the users assigned to the relevant clusters will receive notification of
the submission, as well as a link to the report listing the changes to the server network,
enabling them to sync their networks with the updated network on the server.
To submit changes to the Mentor server

1. On the Server menu, click Submit Network Changes to Server. You will be
prompted to log on to the Mentor server if you have not already done so. A progress
bar is displayed while the data being submitted is compared to the existing data in the
server.
Notes:
o If there is more than one cluster defined in the network, the Select a Cluster
dialog box is displayed. Select the cluster to which the changes should be made,
and click OK. If required, you can also submit changes for additional clusters
directly from the Submit Network Changes to Server <date> dialog box, which
is displayed after all the submitted data has been compared.
o If the network contains network elements that are not part of the selected cluster,
a message is displayed notifying you that any changes made to these network
elements will be ignored and will not be submitted. Click OK to continue.
o The first time a network is submitted to the server, it must include the terrain file.
99
The Submit Network Changes to Server <date> dialog box is displayed, showing
all the discrepancies between the network data being submitted, and the data
currently in the server network, for the selected cluster.
Note: If you are submitting your changes to a multi-technology network, and have
permission for only one of the technologies, your submission will be ignored.
2. Review each of the differences, and then click Accept Change or Ignore Change at
the top of the screen, to accept or ignore the proposed change to the network data on
the server. Accept or Ignore is displayed in the Accept/Reject column. If required,
you can use standard Windows functionality to select multiple or all listed differences.
Note: If there are changes to the advanced network properties, you will have to
accept the changes for each of the required network elements, as well as for the
cluster.
3. Click OK. A confirmation message is displayed.
100
4. Click Yes to submit the accepted changes to the server. A progress bar is displayed
while these changes are being submitted to the server and then the Submit Network
Changes to Server dialog box is displayed, notifying whether the cluster was
updated successfully.
All relevant cluster users will receive notification of the changes, as well as a list of
the changes, enabling them to sync their networks with the updated network on the
server.
5. Click Details to view any errors or warnings.
6. Click Reports to view a report showing details of the requested changes, including
the old values and the new values after the changes were submitted.
Synchronizing Network Updates from the Mentor Server

When the automatic updates feature is activated, Mentor automatically downloads updates
such as new model days, switch dump updates, physical configuration updates such as new
sites, and so on from the server, for the currently open and active network. This process is
fully automated, and runs in the background without any user intervention.
These updates, which include only the new and changed data, are copied to your computer
so that you can import them and integrate them into your environment. As soon as the
updates have been copied to your computer, a dialog box is displayed, enabling you to import
them and synchronize your network with the latest changes on the server. For example, if a
new model day is available, only the new day will be sent to Mentor, which will discard the
oldest model day, and replace it with the newest day received from the server. Similarly, if an
updated switch dump is available, Mentor will replace its configuration information with the
most updated information.
Notes:
 In order to use the automatic updates feature, you must be connected to the Mentor
server and the mechanism must be activated.
 Network names must be kept the same as when imported from the server. If a
network is saved with a different name, it can no longer be updated automatically.
 Only the currently active network, which is the network in focus by Mentor, is
automatically updated. When you switch between active networks, the automatic
updates feature is activated for the relevant network.
 The automatic updates feature does not support networks that were imported with
“special period” models.
101
To synchronize your network with the server

1. Ensure that the automatic updates feature has been activated. The status of this
feature can be viewed on the status bar.
Possible status options include:
o Automatic Updates Disabled: Updates are not checked and retrieved
automatically. Possible reasons for this may be that the feature is disabled, you
are not logged in to the server, or the network name has changed.
o Automatic Updates Active: The automatic update mechanism is on and idle.
Mentor periodically checks in the background whether new updates are available.
o Downloading Updates: The automatic updates mechanism is currently retrieving
data from the server. Double-click this area to view a progress bar showing the
status of the import process.
o Automatic Updates Pending: Mentor has downloaded updates from the server,
and they can be integrated into your network by clicking Import in the dialog box
that is displayed, or by right-clicking this area on the status bar and clicking
Import Updates.
You can right-click the automatic updates area of the status bar to display a menu
that enables you to import the updates, view the progress of the import process, run
or stop the update process, or activate/deactivate the automatic update process.
2. To run the update process without waiting for the configured time to elapse, on the
Server menu click Run Automatic Updates. The status of the automatic updates
feature on the status bar changes to Downloading Updates. Double-click the area to
display a progress bar showing the status of the import process.
102
3. If you selected to view a message when the updates are ready to be imported, a
dialog box is displayed when network updates are available, and the status on the
status bar changes to Automatic Updates Pending.
o Click Reports to view the reports showing the updates that will be imported.
Note: After you have imported the updates, the import update reports are saved
with the Network reports (Network -> Open Network Reports).
o Click Import to import the updates. A progress bar is displayed while the updates
are being imported.
o Click Close to ignore the message and close the dialog box. You can import the
updates at a later stage by right-clicking the automatic updates area of the status
bar, and clicking Import Updates.
As soon as the import process is complete, a dialog box is displayed, and the status
of the automatic update process returns to Automatic Updates Active.
4. Click Details to view a list of any errors and warnings.

5. Click Reports to view a report of the import process and the imported updates.
Note: After you have imported the updates, the update reports are saved with the
Network reports.
103
Displaying Notifications
If you are connected to the Mentor server, you can view notifications sent from the server,
about activities in the server. For example, you can view messages about the model
completion, tasks that failed or succeeded, cluster removals, licensing problems, updates to
the network configuration, and so on. Depending on your user permissions, you can view all
the messages that have been sent, or only those for the clusters to which you are assigned.
To display server notifications

1. Ensure that you are logged on to the Mentor server.
2. On the status bar, double-click the icon. This icon is displayed only if you have
selected to display the server status on the status bar, and there are new unread
notifications.
-OR-
On the Server menu, click Notifications.
The Server Admin - Notifications window is displayed.
The Notifications window displays a list of all the notifications that you have
received. It contains the following fields:
Field Description
Priority The importance of the notification.

- Error or failed task
Status The status of the notification.

- Read
- Unread
Server The server to which the notification refers.
Type The item for which the notification was sent, for example, Model
Task, Collection, License, and so on.
104
Field Description
Subject A brief description of the contents of the notification.
Received The date and time the notification was received.
Region The region to which the notification refers.
Object The cluster or network element to which the notification refers. If

the notification is general, and not for a specific cluster or
network element, N/A is displayed.
Note: By default, some fields are hidden.
You can filter the displayed fields by adding or removing columns:

Customize. The Customize Columns dialog box is displayed, enabling you to
select the columns to be displayed or hidden.
After you have received a notification, you can open it, copy parts of it to the clipboard, print it,
delete it, or change its status to read or unread. If the notification is about an optimization task
or analysis task, you can click the links to view the task or the reports in Mentor.
105
Importing Task Occurrences into Mentor

You can import selected optimization, analysis, or APD task occurrences from the Mentor
server as new networks, or as calculations in the current network.
To import task occurrences

1. On the Server menu, click Optimization Task Occurrences, Analysis Task
Occurrences, or APD Task Occurrences to view a list of the relevant tasks. The
Server Admin - <Recurrence tasks> window is displayed.
2. Right-click the task occurrence you want to import into Mentor, and then select one of
the following options on the shortcut menu:
o Open in New Network: Opens the task occurrence in a new network.
o Open in Current Network - <network>: Opens the task occurrence as a
calculation in the current network.
A progress bar is displayed while the task occurrence is imported into Mentor, and
then a dialog box is displayed notifying whether the import was successful.
3. Click Details to view the details of the import process.

4. Click Layers to view the network-related layers of the imported occurrence.
5. Click Reports to view the Model and Import reports for the imported occurrence.
6. Click Close to close the Import Task Occurrence dialog box.
106
Viewing the Status of Server Tasks

You can view, on the status bar, the number of engineering tasks that are currently running in
the server, and if required access the relevant optimization occurrence dialog box.
To view the server tasks

1. If there are any currently running tasks, hover over the Running Tasks field to
display a tooltip showing the number of each type of task that is running.
2. To view either the Optimization Task Occurrences or Analysis Task Occurrences

dialog box, right-click the Running Tasks field, and on the menu, click the relevant
task occurrence.
Tip: If there is only 1 task running, you can double-click the area to display the
relevant dialog box. If both types are running simultaneously, the Optimization Task
Occurrences dialog box will be displayed.
To launch the Server Admin from the status bar

 On the status bar, right-click the Running Tasks field, and on the menu, click Server
Admin.
Running Pending Tasks

You can run a pending task occurrence at any time, without waiting for the scheduled run
time.
To run a pending task occurrence

1. On the Server menu, click Optimization/Analysis Task Occurrences to view a list
of all the scheduled task occurrences. The Server Admin - <Recurrence tasks>
window is displayed.
2. Right-click the pending task occurrence you want to run immediately, without waiting
for its scheduled time, and click Run Task. The status of the task changes from
Pending to Running. As soon as the task has finished running, a new Pending task
occurrence is created.
107
Working with Optimization Task Occurrences

Optimizations can be scheduled directly from Mentor or from the Server Admin using the
optimization template. If the optimization is recurring, you can view the details of each of the
optimization task occurrences in the Server Admin - Optimizations window.
 Schedule recurring optimization tasks
 Display optimization task occurrences
 Delete optimization task occurrences
 Edit optimization task properties
 View the optimization task history
 View the optimization task reports
 Import the task occurrence into Mentor
If you are an administrator user, you can view and edit the tasks of all the users in the
network. If you are an engineer user, you can view and edit the tasks only in the clusters
assigned to you.
Scheduling Recurring Optimization Tasks

After you have run an optimization in Mentor, you can use the same template to schedule
additional optimization tasks in the server. If required, you can schedule multiple optimization
tasks simultaneously by adding one or more templates from other optimizations.
To schedule a recurring optimization task

1. In the Calculations pane, select the optimization you would like to schedule to be run
automatically by the Mentor server.
2. On the Calculation menu, click Schedule as Optimization Task.
-OR-
Right-click the optimization, and on the shortcut menu, click Schedule as
Optimization Task.
You will be prompted to log on to the Mentor server if you have not already done so.
A progress bar is displayed while the optimization details are submitted to the server,
and then the New Optimization Task wizard is displayed, enabling you to schedule
the recurrence of the task.
The New Optimization Task wizard contains three steps:
 Step 1 - General, enables you to define the general properties for the new
optimization task, for example, the cluster to be optimized, and the optimization
template to be used.
 Step 2 - Modeling Data, enables you to define the modeling data that should be used.
 Step 3 - Schedule, enables you to define when the task will run.
108
Defining General Optimization Task Properties

The General page enables you to define the general properties for the task, for example, the
name of the task, the cluster and sectors to be optimized, and the optimization template to be
used. If required, you can add multiple optimization templates in the same task.
Note for SON optimization tasks: Currently the server supports SON tasks for Ericsson
neighbor list optimization plans. Each SON cluster must have two optimization tasks—a
regular neighbor list plan and a partial plan for new sectors only.
To define the general optimization properties

1. In the Task name field, enter a new name for the task, if required. If you do not enter
a new name, the default name will be used.
2. If you would like to run a SON neighbor list optimization, select the SON Task check
box, and then select the task type from the drop-down list:
o Partial NL for new cells: The optimization will run automatically in the server or
only on new cells when they are detected.
o Full NL plan: The network selection will be optimized in the server, based on the
switch dump and the model.
Note: You must run both task types for each cluster.
3. In the Cluster field, select the cluster to be optimized.
4. Select the sectors to be optimized:
o All sectors in the cluster: Select this option to optimize all the sectors in the
cluster.
o Network elements: By default, the sectors in all the network elements in the
cluster will be optimized, but you can select a specific network element from the
drop-down list, or click the browse button and then select multiple network
elements from the Add Network Elements dialog box.
o Selection: Select this to load a previously saved sector selection, or area

selection if you are running a neighbor list or antenna sectors optimization, and
then click the browse button to select the required selection file.
109
5. The template used in the current optimization is displayed in the Calculations area. If
required, click Add to add an additional optimization template. The Template dialog
box is displayed, enabling you to browse to the required template.
6. Select the optimization template to use, and click Open. The new optimization
template is displayed in the Calculations area.
7. If required, you can add, remove, or edit templates, as well as change the order in
which each optimization will run.
8. Click Next to proceed to the Modeling Data page.
Defining Optimization Task Modeling Data

The Modeling Data page enables you to define the modeling period for the task, and the
modeling days that will be included in the task.
To define the modeling data for the task

1. In the Period field, select the modeling period to include in the optimization. By
default, the daily busy hours are used, but you can select to use a different modeling
period, if one has been defined.
2. In the Number of Modeling Days field, specify or select the number of model days
to use in the optimization.
3. In the Week days area, select one or both of the following check boxes, if required:
o Excluded days: Select this check box to ignore the days that were defined for
exclusion from engineering tasks, such as special days or holidays. This data will
not be included in the task.
o Ignore weekends: Select this check box to ignore weekends in the optimization.
This data will not be included in the task.
110
4. Click Next to proceed to the Schedule page.
Scheduling Optimization Tasks

In the Schedule page, you can define the recurrence of the task. You can also define
whether the task data should be collected and written to the dashboard.
To define the optimization schedule

1. By default, optimization tasks are scheduled to run daily at 08.30. If required, click
Recurrence and then define the task recurrence.
2. Select the Set as dashboard for analysis check box in order for relevant data about
this task to be written to the dashboard database whenever the task is executed.
3. In the Dashboard Market Name field, specify the name of the task, as defined on the
dashboard.
4. Select the Activate in Layer Management application (Neighbor List dashboard)
check box to display the tasks in the dashboard.
5. By default, e-mail notifications regarding the task are sent to the relevant users. Clear
the E-mail notifications check box to prevent sending notifications.
6. Click Finish. A progress bar is displayed while the optimization task is submitted to
the server, and then the new task is displayed in the Server Admin Optimizations
window, with the status Pending.
111
Displaying Optimization Task Occurrences

If you are connected to the Mentor server, you can view a list of optimization task occurrences
affecting the clusters to which you are assigned. If there are any tasks currently running, this
is displayed in the Running Tasks area of the status bar.
You can view the properties of a selected task occurrence, edit pending and future task
occurrences, run a selected pending task occurrence without waiting for the scheduled time,
stop a running task, as well as import the task as a calculation into the current Mentor
network, or as a calculation in a new network.
To display the optimization task occurrences

2. On the Server menu, click Optimization Task Occurrences.
-OR-
Right-click the Running Tasks area on the status bar and select Optimization Task
Occurrences.
The Server Admin - Optimizations window is displayed.
The Server Admin - Optimizations window displays a list of all the optimization task
occurrences affecting the clusters to which you are assigned. For more information
on the fields in the window, refer to the Ultima Mentor Help.
112
Editing Optimization Task Properties

You can view the properties of a selected optimization task any time after it has been defined.
If required, you can edit the properties of any pending or recurring tasks. The changes will
affect all future occurrences of the task.
To edit the task properties

1. In the Server Admin - Optimizations window, right-click the optimization task whose
properties you want to edit, and then click Properties. If the occurrence has already
been run, meaning its status is not Pending, the Open Recurring Item dialog box is
displayed, and you will have to select whether to open the current occurrence, or all
occurrences of the task.
113
A progress bar is displayed while the task details are downloaded, and then the
Optimization Task Properties dialog box is displayed, showing the General tab.
Note: The Agents and History tabs are displayed only when viewing the properties
of the task series, and not for a specific occurrence.
2. Edit the fields in the General, Modeling Data, Schedule and Agents tabs, as
required.
3. Click OK to save your changes and close the Optimization Task Properties dialog
box. A progress bar is displayed while the changes are submitted to the server. The
updated properties are displayed in the Server Admin - Optimizations window, and
will be used for all future task occurrences.
114
Viewing the Optimization Task History

You can view the date, time, and status of each optimization task occurrence, as well as the
details of each operation in a selected occurrence. If required, you can also view the reports
that are relevant to the task.
To view the optimization task history

1. In the Server Admin - Optimizations window, right-click the optimization task
occurrence whose history you want to view, and then click Properties. If the
occurrence has already been run, meaning its status is not Pending, the Open
Recurring Item dialog box is displayed, prompting you to select whether to open the
current occurrence, or all occurrences of the task.
Optimization Task Properties dialog box is displayed, showing the General tab.
115
2. Click the History tab. The date, time, and status of each occurrence of the task are
displayed.
3. Select the occurrence whose details you want to view, and click Details. The Details
dialog box is displayed, showing each operation that took place during the task
occurrence.
116
The Details dialog box enables you to view the following information for each
operation in the selected optimization task:
Field Description
Information
Warning
Error
Date and The date and time the operation was executed.
Time
Type The type of operation, for example, model, collection, antenna sector plan
optimization, importing environment and model, sanity check, download
started, and so on.
Event Whether the operation started, stopped, or was in process.
Source The name of the network element, optimization, model and so on.
Results The outcome of the operation:

 Succeeded: The operation completed successfully.
 Failed: The operation failed, and therefore the task has failed.
Details A description of the operation.
117
Working with Analysis Task Occurrences

Analyses can be scheduled directly from Mentor or from the Server Admin using the analysis
template. If the analysis is recurring, you can view the details of each of the analysis task
occurrences in the Server Admin - Analysis window.
 Schedule recurring analysis tasks
 Display analysis task occurrences
 Delete analysis task occurrences
 Edit analysis task properties
 View the analysis task history
assigned to you.
Scheduling Recurring Analysis Tasks

After you have run an analysis in Mentor, you can use the same template to schedule
additional analysis tasks in the server. If required, you can schedule multiple analysis tasks
simultaneously by adding one or more templates from other analyses.
To schedule a recurring analysis task

1. In the Calculations pane, select the analysis you would like to schedule to be run
2. On the Calculation menu, click Schedule as Analysis Task.
-OR-
Right-click the analysis, and on the shortcut menu, click Schedule as Analysis Task.
A progress bar is displayed while the analysis details are submitted to the server, and
then the New Analysis Task wizard is displayed, enabling you to schedule the
recurrence of the task.
The New Analysis Task wizard contains three steps:
 Step 1 - General, enables you to define the general properties for the new analysis
task, for example, the cluster to be analyzed, and the analysis template to be used.
118
Defining General Analysis Task Properties

The General page enables you to define the general properties for the task, for example, the
name of the task, the cluster and sectors to be analyzed, the model period, and the analysis
template to be used. If required, you can add multiple templates in the same task.
To define the general analysis properties

1. In the Task name field, enter a new name for the task, if required. If you do not enter
a new name, the default name will be used.
2. In the Cluster field, select the cluster to be analyzed.
3. Select the sectors to be analyzed:
o All sectors in the cluster: Select this option to analyze all the sectors in the
cluster.
o Network elements: By default, the sectors in all the network elements in the
cluster will be analyzed, but you can select a specific network element from the
drop-down list, or click the browse button and then select multiple network
elements from the Add Network Elements dialog box.
o Selection: Select this to load a previously saved sector or area selection, and
then click the browse button to select the required selection file.
4. The template used in the current analysis is displayed in the Analysis area. If
required, click Add to add an additional analysis template. The Template dialog box
is displayed, enabling you to browse to the required template.
5. Select the analysis template to use, and click Open. The new analysis template is
displayed in the Analysis area.
6. If required, you can add, remove, or edit templates, as well as change the order in
which each analysis will be run.
7. Click Next to proceed to the Modeling Data page.
119
Defining Analysis Task Modeling Data

The Modeling Data page enables you to define the modeling period for the task, and the
modeling days that will be included in the analysis task.
To define the modeling data for the task

1. In the Period field, select the modeling period to include in the analysis. By default,
the daily busy hours are used, but you can select to use a different modeling period, if
one has been defined.
2. In the Number of Modeling Days field, specify or select the number of model days
to use in the analysis.
3. In the Week days area, select one or both of the following check boxes, if required:
o Excluded days: Select this check box to ignore the days that were defined for
exclusion from analysis tasks, such as special days or holidays. This data will not
be included in the task.
o Ignore weekends: Select this check box to ignore weekends in the analysis. This
data will not be included in the task.
4. In the Time Range area, select whether the calculation should use data for 24 hours,
busy hour only, or for specific hours.
5. Click Next to proceed to the Schedule page.
120
Scheduling Analysis Tasks

In the Schedule page, you can define the recurrence of the task as well as whether to send
notifications about the task to the relevant users.
To define the analysis schedule

1. By default, analyses are scheduled to run daily at 08.30. If required, click
Recurrence and then define the task recurrence.
2. By default, e-mail notifications regarding the task are sent to the relevant users. Clear
the E-mail notification check box to prevent sending notifications.
3. Click Finish. A progress bar is displayed while the analysis task is submitted to the
server. The new task is displayed in the Server Admin Analysis window, with the
status Pending.
Displaying Analysis Task Occurrences

If you are connected to the Mentor server, you can view a list of analysis task occurrences
You can view the properties of a selected task occurrence, run a selected pending task
occurrence without waiting for the scheduled time, stop a running task, as well as import the
task as a calculation into the current Mentor network, or as a calculation in a new network.
121
To display the analysis task occurrences

2. On the Server menu, click Analysis Task Occurrences.
-OR-
Right-click the Running Tasks area on the status bar and select Analysis Task
Occurrences.
The Server Admin - Analysis window is displayed.
The Server Admin - Analysis window displays a list of all the analysis task
occurrences affecting the clusters to which you are assigned. For more information
on the fields in the window, refer to the Ultima Mentor Help.
Editing Analysis Task Properties

You can view the properties of a selected analysis task any time after it has been defined. If
required, you can edit the properties of any pending or recurring tasks. The changes will
To edit the analysis task properties

1. In the Server Admin - Analysis window, right-click the analysis task whose
properties you want to edit, and then click Properties. If the analysis has already
displayed, and you will have to select whether to open the current occurrence, or all
occurrences of the task.
122
Analysis Task Properties dialog box is displayed, showing the General tab.
2. Edit the fields in the General, Modeling Data, Schedule, and Agents tabs, as
required.
3. Click OK to save your changes and close the Analysis Task Properties dialog box. A
progress bar is displayed while the changes are submitted to the server. The updated
properties are displayed in the Server Admin - Analysis window, and will be used
for all future task occurrences.
123
Viewing Analysis Task History

You can view the date, time, and status of each analysis task occurrence, as well as the
details of each operation in a selected occurrence.
To view the analysis task history

1. In the Server Admin - Analysis window, right-click the analysis task occurrence
whose history you want to view, and then click Properties. If the occurrence has
already been run, meaning its status is not Pending, the Open Recurring Item
dialog box is displayed, and you will have to select whether to open the current
occurrence, or all occurrences of the task.
Analysis Task Properties dialog box is displayed, showing the General tab.
124
displayed.
occurrence.
125
operation in the selected analysis task:
Field Description
Information
Warning
Error
Date and Time The date and time the operation was executed.
Type The type of operation, for example, model, collection, antenna

sector plan optimization, importing environment and model,
sanity check, download started, and so on.
Source The name of the network element, optimization, model and so

on.

 Failed: The operation failed, and therefore the task has
failed.
Working with APD Task Occurrences

APD tasks can be scheduled from the Server Admin using the APD template. If the APD task
is recurring, you can view the details of each of the task occurrences in the Server Admin -
APD window.
 Display APD task occurrences
 Delete APD task occurrences
 Edit APD task properties
 View the APD task history
 View the APD task reports
assigned to you.
126
Displaying APD Task Occurrences

If you are connected to the Mentor server, you can view a list of APD task occurrences
You can view the properties of a selected task occurrence, edit pending and future task
occurrences, run a selected pending task occurrence without waiting for the scheduled time,
stop a running task, as well as import the task as a calculation into the current Mentor
network, or as a calculation in a new network.
To display the APD task occurrences

2. On the Server menu, click APD Task Occurrences.
-OR-
Right-click the Running Tasks area on the status bar and select APD Task
Occurrences.
The Server Admin - APD window is displayed.
The Server Admin - APD window displays a list of all the APD task occurrences
affecting the clusters to which you are assigned. For more information on the fields in
the window, refer to the Ultima Mentor Help.
127
Editing APD Task Properties

You can view the properties of a selected APD task any time after it has been defined. If
required, you can edit the properties of any pending or recurring tasks. The changes will
To edit the task properties

1. In the Server Admin - APD window, right-click the APD task whose properties you
want to edit, and then click Properties.
If the occurrence has already been run, meaning its status is not Pending, the Open
Recurring Item dialog box is displayed, and you will have to select whether to open
the current occurrence, or all occurrences of the task.
128
A progress bar is displayed while the task details are downloaded, and then the APD
Task Properties dialog box is displayed, showing the General tab.
2. Edit the fields in the General, Modeling Data, Schedule and Agents tabs, as
required.
3. Click OK to save your changes and close the APD Task Properties dialog box. A
progress bar is displayed while the changes are submitted to the server. The updated
properties are displayed in the Server Admin - APD window, and will be used for all
future task occurrences.
129
Viewing the APD Task History

You can view the date, time, and status of each APD task occurrence, as well as the details
of each operation in a selected occurrence. If required, you can also view the reports that are
relevant to the task.
To view the APD task history

1. In the Server Admin - APD window, right-click the APD task occurrence whose
history you want to view, and then click Properties. If the occurrence has already
displayed, prompting you to select whether to open the current occurrence, or all
occurrences of the task. A progress bar is displayed while the task details are
downloaded, and then the APD Task Properties dialog box is displayed, showing
the General tab.
130
displayed.
131
occurrence.
operation in the selected APD task:
Field Description
Information
Warning
Error
Date and The date and time the operation was executed.
Time
Type The type of operation, for example, model, collection, antenna sector plan
optimization, importing environment and model, sanity check, download
started, and so on.
Source The name of the network element, optimization, model and so on.

 Failed: The operation failed, and therefore the task has failed.
132
Viewing the APD Task Reports

You can view the reports relevant to a selected task, including tasks relating to the network
import and the model.
To view the APD task reports

1. In the Server Admin - APD window, right-click the optimization task occurrence
whose reports you want to view, and then click Properties.
If the occurrence has already been run, meaning its status is not Pending, the Open
Recurring Item dialog box is displayed, prompting you to select whether to open the
current occurrence, or all occurrences of the task.
A progress bar is displayed while the task details are downloaded, and then the APD
Task Properties dialog box is displayed, showing the General tab.
133
displayed.
134
3. Select the occurrence whose details you want to view and then click Reports. A
progress bar is displayed while the reports are being loaded, and then the Reports
dialog box is displayed showing all reports that are relevant to the selected task
occurrence, including the import and model reports.
4. Select the report you want to view and click Open.
Antenna Model Database

If you are connected to the Mentor server, you can access a built-in antenna model database
that contains ready-made profiles and radiation patterns for hundreds of commonly used
antenna models. This enables you to access a large resource of profiles in one location within
Mentor, rather than have to collect the profiles you use and then import them into Mentor.
 Display the antenna model database
 Display the antenna model properties
 Display the antenna model profile properties
 Search for existing antenna models
 Export the antenna model database
Displaying the Antenna Models

If you are connected to the Mentor server, you can access the built-in antenna model
database that contains ready-made profiles and radiation patterns for hundreds of commonly
used antenna models.
135
To display the antenna model database

2. On the Server menu, click Antenna Models. The Server Admin - Antenna Models
window is displayed.
The Server Admin - Antenna Models window contains a list of all antenna models in
the database. It contains the following fields:
Field Description
Name The name of the antenna model.
Manufacturer The antenna model manufacturer.
Min. Electrical Tilt The minimum electrical tilt of the antenna model.
(deg)
Max. Electrical Tilt The maximum electrical tilt of the antenna model.
(deg)
Nominal Gain (dBi) The average gain of the antenna profiles.
Nominal V The average vertical beamwidth of the antenna profiles.

Beamwidth (deg)
Nominal H The average horizontal beamwidth of the antenna

Beamwidth (deg) profiles.
136
Field Description
Support E Tilt Whether the antenna model supports electrical tilt.
Support E Whether the antenna model supports electrical

Beamwidth beamwidth.
Note: By default, some fields are hidden.

You can filter the displayed fields by adding or removing columns:
then click Remove this Column. The selected column will be hidden.
137
Displaying the Antenna Model Properties

You can display the properties of a selected antenna model, for example, the name and
manufacturer of the model, as well as the profiles included in the antenna model.
To display the antenna model properties
1. In the Antennas window, select the required antenna and on the toolbar, click .
-OR-
Right-click the required antenna model, and then click Properties.
The Antenna Model Properties dialog box is displayed, enabling you to view the
general properties as well as the profiles included in the antenna model.
The Antenna Model Properties dialog box contains two tabs:

o General, which displays properties such as the name and manufacturer of the
antenna model.
o Profiles, which displays a list of antenna profiles belonging to the selected
antenna model. You can also view the properties a selected antenna profile.
138
Exporting Antenna Models

You can export antenna models to your local computer so that they can be imported into the
client, or for any other use.
To export antenna models

1. In the Antennas window, right-click the antenna models that you would like to export,
and then click Export. The Export Antenna Models dialog box is displayed.
2. Browse to the location to which to export the antenna models, and then click Save. A
dialog box is displayed notifying whether the antenna models were successfully
exported.
139
Collecting Call-Trace Data

Defining the UMTS/GSM Measurement Plan
The Measurement-Plan tool functionality ensures that reliable mobile-measurement data is
collected for the network modeling. If you have a multi-technology network that includes GSM,
the measurement-plan tool enables you to generate an optimized plan to record mobile
measurements for selected UMTS sectors in neighboring GSM networks.
Due to an inherent limitation in the UMTS standard, undefined GSM neighbors cannot be
detected by the UEs and reported to the RNCs. The measurement plan process is the only
way to force the UEs in compressed mode to scan and report the BCCHs/BSICs of previously
undefined IRAT GSM neighbors.
Each mobile measurement plan generates the following output:
 XML provisioning scripts to be sent to the switch
 Reports to be considered by the user
For more information on these outputs, refer to the Ultima Mentor Help.
Note: Any discrepancies between the definitions of the GSM network in the UMTS network
should be resolved before running the measurement plan.
To define the measurement plan

1. In the map area, select the UMTS source sectors on which the measurements should
be carried out.
2. On the Tools menu, click UMTS/GSM Measurement Plan. The UMTS/GSM
Measurement Plan dialog box is displayed.
140
3. In the Location field, select the location of the switch dump data for the relevant
network.
o Local:
 In the <vendor> configuration field, browse to the location of the .xml file
containing the most updated UMTS switch dump data for the relevant network.
In the GSM configuration field, browse to the location of the .txt file
containing the most updated GSM switch dump data.
o Server: (The fields in the dialog box change accordingly)
4. In the Cluster field, select the cluster from which to import the switch dump data.
Note: The selected cluster must contain both UMTS and GSM switch dumps.
5. In the Results directory field, browse to the directory in which to save the XML
provisioning scripts generated for each day of the measurement plan.
Note: All existing data in the output folder is deleted each time you run the
measurement plan.
6. In the Maximal number of neighbors field, enter the maximal number of neighbors
allowed for a UMTS sector that can be measured on each day of the measurement
plan. This number includes the sectors in the live network as well as the sectors in
the measurement plan.
7. In the Number of days field, enter the number of recording days.
8. If the GSM network contains more than one band, you can select the band to be used
in the GSM band field. By default, all bands are used.
141
9. Click OK. If this is not the first time that you are running a measurement plan, a
confirmation message is displayed notifying that all existing files in the output
directory will be deleted. Click Yes to continue. A progress bar is displayed while the
networks are being imported, and then the UMTS/GSM Measurement Plan dialog
box is displayed, notifying you about the success of the plan.
10. Click Details to view details of the errors and/or warnings generated during the
recording process.
11. Click Reports to view the reports generated during the recording process. For details
about these reports, refer to the Ultima Mentor Help.
12. Click Close to close the UMTS/GSM Measurement Plan dialog box.
Viewing the Measurement Plan Reports

The Measurement Plan reports show the mobile-measurement recordings of selected UMTS
sectors in neighboring GSM networks.
To view the measurement plan reports

1. After you have generated the measurement plan, and it has completed successfully,
the UMTS/GSM Measurement Plan dialog box is displayed.
Click Reports. The Reports dialog box is displayed, showing the available reports.
142
There are five available reports:

o Measurement Plan Co-BCCH-BSIC, which displays the GSM sectors that were
not included in the measurement plan in order to prevent Co-BCCH-BSIC clashes
with existing GSM neighbors.
o Measurement Plan Details, which displays details of the measurement plan.
o Measurement Plan IRAT NL Plan Summary, which displays a summary of the
IRAT neighbor list plan.
o Plan Summary, which displays a summary of the measurement plan.
o Measurement Plan UMTS-GSM Discrepancy, which shows discrepancies
between the way the UMTS network is listed in the IRAT adjacency definition in
the GSM network, and the actual values, as defined in the UMTS network.
For more information about these reports, refer to the Ultima Mentor Help.
143
Modeling the Network

Importing a Model
If required, you can import a previously created model of the network instead of creating a
new model. You can either import a model file, or if you are connected to the Mentor server,
you can select the model data to be imported and used. After you have imported a model, you
can view the model reports, or layers showing any sectors that are marked as locked, or that
are locked due to low traffic.
Note: If you are importing a model file, the model must have been created for the same
network configuration on which you are currently working.
Importing a Model File

To import a model file
1. On the File menu, click Import then Model. If a model already exists, a confirmation
message is displayed notifying you that the existing model will be replaced. Click Yes
to continue. The Import Model dialog box is displayed.
2. By default, if you are not connected to the server, the Import file option is selected. If
not, select the Import file option.
144
3. Select the file you want to import from the drop-down list, or click the browse button
to browse to the location of the file you want to import. The Import Model dialog
box is displayed.
4. Select the required *.mdl file, and click Open.
5. Click OK. A progress bar is displayed while the model is being imported, and then the
Import Model dialog box is displayed, notifying you whether the model was imported
successfully, or whether the import failed, and the number of errors and warnings that
were found.
6. Click Details to view any warnings or errors that occurred during the import process.
7. Click Layers to view layers showing sectors that are marked as locked, or that are
locked due to low traffic.
8. If the model was imported successfully, click Reports to view the imported model's
reports.
9. Click Close to close the Import Model dialog box.
Importing a Model from the Mentor Server

To import a model from the Mentor server
1. On the File menu, click Import then Model. If a model already exists, a confirmation
message is displayed notifying you that the existing model will be replaced. Click Yes
to continue. The Import Model dialog box is displayed.
145
2. By default, if you are connected to the server, the Import from server option is
selected. If not, select Import from server. You will be prompted to log on to the
server.
3. In the Cluster field, select the cluster for which to import the model. You can view
details about the selected cluster in the Cluster Information area at the bottom of
the dialog box.
4. By default, the model is imported with all its modeled network elements. If required,
can select to import the model for a specific network element from the Network
Elements drop-down list or you can click the browse button to select multiple
network elements.
5. In the Modeling period field, select the hours for which to import the model.
6. In the Model date range field, select the dates to include in the model from the drop-
down list, or click the browse button to choose the dates to include. The Model
Date Range dialog box is displayed, with dates for which there is modeling data
displayed in bold. If the network contains more than one network element, you can
run your mouse over a bolded date to display a tooltip showing which network
elements were modeled on that day.
Select the dates to be included in the model using standard Windows functionality,
and click OK. The first and last days selected are displayed in the Model date range
field, and the number of actual days for which there is model data, and the date of the
latest data, is displayed in the field below this.
7. If you want weekend data to be included in the model, select the Include weekends
check box. By default, only weekday data is included in the model.
8. If you require the model for neighbor list optimization and partial analysis only, select
the Quick model import check box. The imported model will be based on
performance counters only.
9. Click OK. A progress bar is displayed while the model is being imported, and then the
Import Completed dialog box is displayed, notifying you whether the model was
imported successfully, or whether the import failed, and the number of errors and
warnings that were found.
10. Click Details to view any warnings or errors that occurred during the import process.
11. Click Layers to view layers showing sectors that are marked as locked, or that are
locked due to low traffic.
12. If the model was imported successfully, click Reports to view the imported model's
reports.
13. Click Close to close the Import Model dialog box.
146
Exporting a Model
You can export the existing model so that it can be imported and used by other users.
To export a model
1. On the File menu, click Export then Model. The Export Model dialog box is
displayed, enabling you to select a location to which to export the model.
2. Browse to the required location.
3. In the File name field, enter a name for the model file.
4. Click Save. A progress bar is displayed while the model is exported to the selected
location.
147
Working with Selections

Mentor enables you to work with 2 kinds of selections:
 Sector selections: A sector selection, or selection set, is a set of sectors that you
have selected on which to create a model, or run an analysis or optimization. Mentor
treats this selection as a single entity when creating the model or performing analysis
or optimization tasks. Selections can be saved in the system, and then loaded for use
in various calculations, as required. After you have created the selection set, Mentor
automatically calculates a wider cluster, based on the neighbor list of the selection
set, called the calculation set. If the neighbor list is optimized, the calculation set
accurately reflects the sectors that may be influenced by power changes in the
selection set.
 Area selections: An area selection is an area you have selected on which to run an
analysis or optimization (neighbor list or antenna sectors), or show maps and
statistics. For example, you can view the coverage of the selected area by displaying
the serving sectors for the area. This will enable you to pinpoint the sectors that affect
the area. Area selections can be saved as layers and then loaded as required.
Creating Sector Selections

A sector selection is a group of selected sectors. A selection set is a group of sectors that you
have selected on which to create a model, or run an analysis or optimization. After you have
created the selection set, Mentor automatically creates the calculation set, which contains all
the sectors in the selection set plus a surrounding buffer of sectors that are the neighbors of
the sectors in the selection set.
You can create a sector selection in the following ways:
 By drawing a rectangle around the required sectors on the map using the Pointer tool
 By selecting the required sectors on the map using the Sector Lasso tool
 By pasting the required sectors on the map
 By loading a previously saved .txt file with the names of the sectors
Note: You should not select all the sectors in the map for the selection set, as Mentor
requires additional sectors to be used as neighbors. These sectors will be included in the
Calculation set.
Saving Sector Selections

You can save a selection as a .txt file, which can be loaded in future sessions. If required, you
can also save the selection as a layer.
Note for Huawei users: If required, you can save the selection in the IOS Traces format,
according to cell ID, which can be used to copy the cell IDs to the LMT tool. You can also load
the IOS Traces format to Mentor to see which sectors were traced.
148
To save a sector selection

1. Select the sectors you want to include in the selection.
2. On the Selection menu, click Save Selection.
-OR-
Right-click the selection, and on the shortcut menu, click Save Selection.
The Save Sector Selection dialog box is displayed.

3. Browse to the required location in which to save the selection.
4. In the File name field, enter a name for the new selection.
5. In the Files of type field, select whether to save the selection according to sector
name or cell ID.
6. Click Save. The selection is saved in the selected location, and can be loaded in the
future.
Saving Selections as a Layer

You can save a selection as a GIS layer so that it can be used it in future calculations or
sessions. If you are saving selected rows in the Detailed Table as a layer, the new layer will
be displayed with the same legend and properties as the original layer, which is useful when
selecting important data from a very dense layer.
If you have created layer folders, you can save the layer to a selected folder. If you have not
created folders, the selection layer is automatically saved under the GIS category. If required,
you can also save a selection as a .txt file.
To save a selection as a layer

1. Select the sectors you want to include in the layer.
2. On the Selection menu, click Save Selection as Layer.
-OR-
Right-click the selection, and on the shortcut menu, click Save Selection as Layer.
The Save Selection as Layer dialog box is displayed.
3. Enter a new name for the layer, if required.
149
4. In the Folder field, select the GIS category or the folder in which to save the layer,
and click OK.
A progress bar is displayed while the layer is being saved to the selected location,
and then it is displayed in the Layers pane under the GIS category, and on the map.
Loading Sector Selections

You can load previously saved selections at any time. If the selections are saved in the
current network, you can also see the number of sectors included in each selection.
To load a selection
1. On the Selection menu, click Load Sector Selection. The Load Selection dialog
box is displayed.
Tip: If you are in the Current Network folder, you can display the number of
sectors included in each of the selections by clicking the button at the top right of
the dialog box.
2. Select the selection you want to load. The selected selection is displayed in the File
name field.
3. Click Open. The selection is displayed on the map.
Creating the Calculation Set

After you have created the selection set, Mentor automatically calculates a wider cluster,
based on the neighbor list of the selection set, called the calculation set. If the neighbor list is
optimized, the calculation set accurately reflects the sectors that may be influenced by power
changes in the selection set.
The difference between the selection set and the calculation set is that the optimization
parameters, such as sector power, can be changed in the selection set only. Sectors in the
calculation set can be affected in terms of traffic load, traffic channels power, noise level, and
so on.
The calculation set is usually two to three tiers beyond the boundary of the selection set. In
rural areas, the calculation set includes only one or two tiers due to the low interaction rate
with sectors far from the selection set. However, in dense urban areas with high levels of
interaction between sectors, as reflected by high handover factors and long neighbor lists,
there is usually a much wider calculation set.
150
The optimization sub-goals are checked for the entire calculation set, as it contains all the
sectors that are affected by the planned antenna sectors optimization. Note that sectors in the
selection set and in the calculation set carry the same weight in the sub-goals, meaning
power, traffic, and handover factors. Mentor tries to improve all the sectors, no matter whether
they belong to the selection set or the calculation set. Obviously sectors within the selection
set are more influenced by the power changes, therefore the expected improvement is higher
in the selection set. The effect of the changes on sectors belonging to the calculation set
decreases the further away the sectors are from the selection set.
The following picture shows a user-defined selection set made up of 33 sectors. The
calculation set is made up of an additional 114 sectors that interact with the selection set,
totaling 147 sectors. It is easy to see that some sectors close to the selection set will probably
be highly affected by changes in the selection set. Some changes are indirect, for example, in
sectors A, B and C, where sector A is in the selection set, sector B is a nearby sector in the
calculation set, and sector C is a neighbor of sector B. Decreasing the power on A may add
traffic to B, which will increase its traffic power and therefore increase the noise levels on C,
and increase C’s power consumption.
151
Creating an Area Selection

You can create an area selection on which to run analyses and optimizations (neighbor list
and antenna sectors), and for which to generate maps. If required, you can convert a selected
area into text format so that it can be imported into other applications, such as ASSET
Design.
The selection is created based on the geographic co-ordinates of the points in the selected
area, and all sectors whose co-ordinates fall within this range are automatically included in
the selection.
You can create an area selection in the following ways:
 By drawing a rectangle around the required area on the map using the Area Selection
tool
 By selecting the required area on the map using the Area Lasso tool
 By loading a previously saved file
Saving an Area Selection

You can save an area selection as a .txt file, which can be loaded in future sessions. If
required, you can also save the selection as a layer.
To save an area selection

1. Select the sectors you want to include in the selection.
2. On the Selection menu, click Save Area Selection. The Save Area Selection
3. Browse to the required location in which to save the selection.
4. In the File name field, enter a name for the new selection. If you do not enter a new
name, the default name will be used.
5. Click Save. The selection is saved in the selected location, and can be loaded in the
future.
Saving an Area Selection as a Layer

You can save an area selection as a GIS layer so that it can be used it in future calculations
or sessions.
If you have created layer folders, you can save the layer to a selected folder. If you have not
created folders, the selection layer is automatically saved under the GIS category. If required,
you can also save a selection as a .txt file.
Note: If you have a multi-technology network, the selection set can include either only UMTS
sectors or only GSM sectors.
To save an area selection as a layer

1. Select the area you want to include in the layer.
2. On the Selection menu, click Save Selection as Layer.
-OR-
Right-click the selection, and on the shortcut menu, click Save Selection as Layer.
152
The Save Selection as Layer dialog box is displayed.
3. Enter a new name for the layer, if required.

4. In the Folder field, select the GIS category or the folder in which to save the layer,
and click OK. A progress bar is displayed while the layer is being saved to the
selected location, and then it is displayed in the Layers pane under the GIS category,
and on the map.
Loading an Area Selection

You can load previously saved area selections at any time.
To load an area selection

1. On the Selection menu, click Load Area Selection. The Load Area Selection
2. Select the selection you want to load. The selected selection is displayed in the File
name field.
3. Click Open. The selection is displayed on the map.
153
Pasting Selections
You can paste sector names from the Windows clipboard into Mentor and view them in the
map area. For example, you can sort a Mentor report according to the number of dropped
calls per sector, and then paste the sectors with the most dropped calls into Mentor to be
displayed as a new selection in the map area. If required, you can save the selection to be
used for future reference.
To paste a new selection

1. Copy the sectors you want to include in the selection and view on the map, using
standard Windows functionality.
2. In Mentor, press <Ctrl+Alt+V>. Mentor automatically adjusts the zoom to display all
the possible sectors in the new selection in the map area.
Exporting Selected Sectors

You can export selected sectors from the map to your Windows clipboard, and then paste
them into an editor such as Microsoft Excel.
To export sectors from the map

1. On the map, select the sectors you want to export.
2. Press <Ctrl+Alt+C> to copy the selected sectors to the Windows clipboard.
3. Paste the sectors in your editor using standard Windows functionality.
Displaying the Combined-Analysis Selection Set

After you have created a combined analysis that filters a selected map according to specific
KPI values, you can display only those sectors that meet the criteria to be included in the
combined analysis. This filtered selection set can then be used as the selection set for
additional analyses or optimizations.
To display the combined-analysis selection set

 In the Layers pane, right-click the combined analysis layer, and on the menu, click
Display Combined Selection Set on Map. Only the sectors that meet the filter
requirements are highlighted on the map, and can be used for additional calculations.
The number of sectors in the selection is displayed on the status bar at the bottom of
the window.
Modifying the Sector Selection

After you have displayed a selection on the map, or you have loaded a saved selection, you
can add or remove one or more sectors to or from the selection, and save it, or you can save
the selection as a new selection, with a new name.
To modify the current selection

1. To add additional sectors, press the <Shift> or <Ctrl> key on your keyboard and click
the sectors you want to add. You can also drag the cursor to create an additional
selection. The selected sectors are combined with the previously selected sectors to
form a new selection.
154
2. To remove sectors from the selection, press the <Ctrl> key on your keyboard and
click the sectors you want to remove. You can also drag the cursor to remove
multiple sectors.
3. On the Selection menu, click Save Sector Selection. The name of the selected or
currently displayed selection is displayed in the Name field.
4. Click Save, or enter a new name for the selection, and click Save. The new selection
is saved.
Adding Keywords
You can add keywords to Mentor, which afterwards can be associated with one or more
sectors.
To add a keyword
1. On the Selection menu, click Keyword Management. The Keyword Management
dialog box is displayed, enabling you to add keywords to the list of existing keywords.
2. Enter new keyword in the available field. The Add button is enabled.
3. Click Add. The new keyword is added to the list of existing keywords, and can be
associated with a sector or a selection.
Associating Sector Selections with Keywords

You can associate a sector selection with a previously defined keyword, or you can define
new keywords during the association process. After you have associated a keyword with a
sector selection, you can select the sectors using the associated keyword. If required, you
can remove the association.
To associate the selection with a keyword

1. Select the required sectors on the map.
2. Right-click any of the sectors in the selection, and on the shortcut menu, click
Properties. The Sector Properties (Multi-selection) dialog box is displayed.
155
3. Select the Keywords tab.
4. From the Select keyword drop-down list, select the keyword to associate with the
selection and click Add. The keyword is displayed in the Keywords associated with
sectors area.
5. Repeat this step to associate the selection with additional keywords.
6. If a specific keyword is not defined for the selection, you can define a new one by
clicking New. The New Keyword dialog box is displayed.
7. In the Keyword field, enter the new keyword, and click OK. The new keyword is
displayed in the Select keyword drop-down list.
8. Click OK to save your changes and close the Sector Properties (Multi-selection)
dialog box.
156
To remove an association:
1. In the Keywords associated with sectors area, select the keyword association you
want to remove, and click Remove. The keyword is removed from the list of
associated keywords, and cannot be used to display the selected selection.
dialog box.
Displaying Sector Selections by Keyword

You can display sector selections according to the keyword with which they are associated.
To display a selection according to its associated keywords

1. On the Selection menu, click Select Sectors by Keyword. The Select by Keyword
dialog box is displayed, showing a list of the defined keywords, and the number of
sectors associated with them.
2. Select the keyword associated with the sectors you want to display, and click OK.
The zoom factor is automatically adjusted to fit the selection, which is highlighted on
the map.
157
Working with Layers

Mentor enables you to work with both vector and raster layers in the map view.
Vector layers: Vector layers consist of a text file with coordinates describing the various
points and curves on the map. When they are loaded into a mapping program, that data is
used to generate a map image. Vector maps scale up and down without any loss of clarity,
enabling you to zoom in to see specific areas, or to zoom out and still have readability.
Examples of vector maps include individual drop maps, and sector layers.
Raster layers: Raster layers are based on conventional image files, such as .gif or .png
formats, which show all the detail of the original topography. However, raster maps do not
scale well, and if you zoom in too far the images become pixilated and fuzzy and if you zoom
out too far, the text on the map becomes unreadable. Examples of raster maps include Ec/Io
maps, traffic maps, and terrain maps.
You can:
 Display selected layers on the map
 Create layer folders
 Show or hide layers
 Move layers up and down
 Copy and paste layers to GIS layer folders
 Import layers
 Export layers
 Define layer display properties
 Display a layer histogram
 Display layers in the Detailed Table
 Zoom to fit the layer on the map
 Delete layers
 Show the layer legend
 Carry out mathematical operations on the values of up to eight raster map layers
 Convert raw data into text format
Mentor Layer System

Mentor uses the GIS layer approach, which allows data to be input as separate themes and
overlaid, based on analysis requirements. Using Mentor you can display and work with the
following layers on the map area:
158
 Annotations: Enables you to draw lines, shapes, text boxes, insert callouts, pictures
and text annotations, and display them as a layer in your network, mainly for printing
purposes or for presentations. You can show or hide this layer according to your
requirements and preferences.
 Network: Enables you to show or hide the sites, sectors, and antennas in your
network, according to their actual coordinates in the real network. If you have a multi-
technology network, the technology of the sites and sectors is also displayed. If you
network contains multiple carriers and bands, a separate layer is displayed for each.
You can display all network layers at the same time, or selected layers only.
Note: You must select the Network category before you can display any of the
selected layers.
 Calculation Results: Enables you to view the calculation layers on the map. For
example, you can view the HO-rate changes, KPIs, and neighbor list and power
changes.
Note: You must select the Calculation Results category, and the name of the
calculation, before you can display any of the selected calculation layers.
 GIS: Enables you to import and display any Mentor-supported GIS layer on the map,
for example, Terrain. If your model contains positioning, you can also display saved
positioning-based maps, for example, mobile drop, traffic, drop, arc, and performance
maps on the map area, and in Google Earth.
 Web Maps: Enables you to display road maps of the area on the Mentor map area.
After you have displayed the layers on the map area, you can view a list of the elements in
the selected layer, as well as their properties, in the Detailed Table pane.
GIS Layers
Displaying a Layer in Google Earth

After you have loaded and selected a GIS layer, you can display it on a topographical map in
the Google Earth application. To do so, Google Earth must be installed on the PC on which
Mentor is installed. If it is not already installed, you can download it from the Google Earth
website.
Note: If the layer has been filtered in Mentor, only the filtered data is displayed in Google
Earth.
If required, you can also export a layer to Google Earth .kml format, or view the layer on a
Web map in the map area.
To display a layer in Google Earth

 In the Layers pane, right-click the layer you want to display, and from the shortcut
menu, select Show Layer in Google Earth.
159
A progress bar is displayed while the layer is exported to Google Earth, and then the
geographic information of the location is displayed on the satellite map on your
desktop, according to the Google Earth parameter settings.
Saving GIS Maps as Layers

GIS map layers are temporary layers that must be saved if you want to use them in the future.
If these layers were not saved when they were created, they can be saved after they have
been loaded. If you have created layer folders, you can save the maps to a selected folder. If
you have not created folders, the map layers are automatically saved under the GIS category.
Saving a GIS map as a layer

1. Right-click the relevant GIS map, and on the shortcut menu, click Save Map as
Layer. The Save Map as Layer dialog box is displayed.
2. If required, enter a new name for the layer.

3. In the Folder field, select the GIS category or the folder under the GIS category in
which to save the map layer.
160
4. Click OK. A progress bar is displayed while the map layer is saved and loaded, and
then it is displayed in the Layers pane, in the selected location under the GIS
category.
Working with GIS Layer Folders

You can save specific layers in folders under the GIS layer. For example, you can create a
folder of dropped calls from multiple analyses, or a folder containing layers from one or more
calculation types. After you have created the folder, it is saved in the same directory as all the
other Mentor folders, as specified in the network Preferences.
If required, after you have created the folders, you can rename or delete them, or add sub-
folders.
Note: Raster layers must be displayed on the map before they can be copied to a folder.
To save GIS layers in folders

1. In the Layers pane, right-click the GIS category, and from the shortcut menu, click
New Folder. The New Folder dialog box is displayed.
2. Enter a descriptive name for the folder, if required.
161
3. Click OK. The new folder is displayed under the GIS category in the Layers pane,
and is saved in the path specified in the network preferences.
4. Copy the required layers from the Calculation Results layers to the relevant folders,
or move layers from one folder to another, by dragging them using standard Windows
functionality.
Notes:
o Calculation layers must be from the same calculation. If you want to copy layers
from multiple calculations, you must repeat this step for each calculation.
o Dragging the layers from one GIS folder to another will move the layers, not copy
them. To copy the layers from one folder to another, right-click the layers you
want to copy and select Copy, then right-click the folder to which to paste them
and select Paste. (Only layers that are displayed on the map can be copied from
folder to folder.)
To rename or delete folders, or add sub-folders

 Right-click the folder you want to rename or delete, or to which to add a sub-folder,
and then select the required action from the shortcut menu.
162
Displaying Layers in the Detailed Table

You can view the properties of a selected layer in the Detailed Table pane. By default, all the
elements in the layer are displayed, but you can filter the table if required to display only those
elements that match your filter criteria. You can also customize the table to display only
selected property columns.
Note: You can display the Detailed Table for only for network layers and for calculation layers
that are displayed as vectors.
To display the a layer in the detailed table

1. In the Layers pane, right-click the layer for which to display the Detailed Table, and
on the shortcut menu, click Detailed Table. The Detailed Table <Layer> pane is
displayed at the bottom of the map area.
Showing/Hiding Layers
You can show or hide the following types of layers on your map:
 GIS layers
 Annotations layer
 Network layers
 Calculation result layers
Before you can show layers on the map, they must first be loaded in the Layers pane. Some
layers are imported with the network, for example the Terrain layer, while others can be
created with the model, for example the Drop Map and Traffic Map layers. You can also
import layers, or load calculation layers after you have run a calculation.
Once the layers are loaded in the Layers pane, you must select the check boxes next to the
layers to display the relevant layers on the map, or clear the check boxes to remove the
layers from the map. If you have more than one layer in the same group, you can
simultaneously show or hide multiple layers by selecting them using standard Windows
functionality, and then selecting Show/Hide.
Note: The layers are displayed in a hierarchy in the Layers pane, and each layer can be
displayed only if the layer above it has been selected. For example, in order to display the HO
Rate Change - Carrier 1 layer, you must ensure that the relevant neighbor list optimization, as
well as the Calculation Results category are selected.
163
Examples of how layers are displayed or hidden:

 If you select the HO Rate Change - Carrier 1 check box in the Layers pane, and on
the View menu, click Fit to Layer, the map zoom will be adjusted to display all
sectors included in this layer at maximum zoom.
 If you clear all the entries in the Layers pane, the map view appears empty.
 If you select Network and Sites in the Layers pane, only the sites appear on the
map.
164
 If you select Network, Sites, Sectors, and Antennas, the sites, sectors, and
antennas appear on the map.
Moving Layers Up or Down

Layers can be set to be in front of or behind other layers in the same group. If required, you
can move multiple selected layers, simultaneously. The visibility of the layers on the map also
depends on the level of transparency defined for each layer in the Layer Properties.
Note: If you want to change the order in which layers from different groups are displayed, you
can create a folder for the layers from each of the relevant groups, and then arrange these
layers in any order.
To move layers up in the group hierarchy

1. In the Layers pane, select the layers that you want to move up in the group
hierarchy.
2. On the Layer menu, click Move Up.
-Or-
Right-click the layers, and on the shortcut menu, click Move Up.
The selected layers will moved up one position in the group.
Note: If the selected layers are not sequential, meaning they are not one after the
other in the group, they will first all be moved under the uppermost selected layer.
3. Click Move Up until the layers are in their desired position.
To move layers down in the group hierarchy

1. In the Layers pane, select the layers that you want to move down in the group
hierarchy.
2. On the Layer menu, click Move Down.
-Or-
Right-click the selected layers, and on the shortcut menu, click Move Down.
The selected layers will be moved down one position in the group.
Note: If the selected layers are not sequential, meaning they are not one after the
other in the group, they will all first be moved above the lowest selected layer.
3. Click Move Down until the layers are in the desired position.
165
Importing Layers
By default, Mentor includes the Terrain layer, but you can import or drag additional GIS or
other layers from various sources, as long as Mentor supports their format.
Currently Mentor supports importing the following formats:
 ArcView: *.shp
 MapInfo: *.mif, *tab
 Proprietary Format: *.stb
 Text: *.txt
 GeoTIFF: *.tif, *.tiff
 Image: *.gif, *.jpg, *.jpeg, *.bmp, *. wbmp, *.png
To drag a layer into Mentor

 Drag the required layer files into the map area of Mentor. A progress bar is displayed
while the file(s) are downloaded to the map, and then the layers are displayed under
the GIS category in the Layers pane.
To import a layer
1. In the Layers pane, select the GIS category.
2. On the Layer menu, click Import Layer. A standard Windows Open dialog box is
displayed.
3. If required, filter the available files by selecting the desired file type in the Files of
type drop-down list.
4. Browse to and select the desired source map file(s). The names of the files are
displayed in the File name field.
5. Select the desired layer(s) and click Import. A progress bar is displayed while the
file(s) are downloaded to the map, and the layers are displayed under the GIS
category in the Layers pane.
Exporting Layers
Mentor supports exporting layers so that they can be imported to another tool or another
network. For example, Mentor enables you to convert geo-positioning maps from raster to
vector format, as MIF and TAB files.
Note: If the layer data has been filtered, only the filtered data is exported.
 Vector layers can be exported to the following formats:
o ArcView: *.shp
o MapInfo: *.mif, *.tab
Note: Mentor is unable to export more than 1 million bins to .tab format.
o Proprietary Format: *.stb
o Google Earth File: *.kml
166
 Raster layers can be exported to the following formats:

o Image: *.jpg, *.jpeg, *.bmp, *. wbmp, *.png
o GeoTIFF: *.tif, *.tiff
o MapInfo: *.mif, *.tab
Note: Mentor is unable to export more than 1 million bins to .tab format.
o Planet: *.grd
o Asset File: *.tri/*.trr (traffic), *.3ga (coverage)
o Text: *.txt
To export a layer
1. On the Layers pane, select the check boxes next to the layers to be exported. The
layers are displayed on the map.
2. Right-click the layers, and on the shortcut menu, click Export Layer. A standard
Windows Save dialog box is displayed.
3. Browse to the location to which to export the layers.
4. In the File name field, enter a name for the layer file.
5. In the Files of type field, select the file format to which to export the layer.
6. Click Save. A progress bar is displayed while the layers are being exported to the
selected location and format. A confirmation message is displayed notifying whether
the layers were successfully exported.
7. Click OK to close the confirmation dialog box.
Defining Layer Properties

You can define the appearance of the different layers on the map, for example, whether they
are visible on the map, the colors in the legend, the shape of the symbols, and so on.
Note: If you have a multi-carrier network, you can display and edit the properties of the
Sectors layer per carrier, or you can simultaneously display and edit the General, Legend,
and Labels tabs for all the sectors in the network.
You can reset the layer properties to the factory defaults at any time by clicking the Reset to
Defaults button.
167
To define layer properties

1. In the Layers pane, right-click a layer, and on the shortcut menu, click Properties.
The Layer Properties <Layer> dialog box is displayed.
The Layer Properties dialog box includes three to five tabs, according to whether
you selected a vector or raster layer.
o General: Enables you to rename the layer, and view general layer properties. You
can also reset the layer properties by clicking Reset to Defaults, and then select
the check boxes next to the tabs whose properties you want to reset.
o Display: Enables you to define the layer display, for example whether the layer is
visible, and its level of transparency.
Note: If you have a multi-carrier network, this tab is displayed in the Sectors layer
properties only if you have selected to display the properties of the required
carrier.
o Legend: Enables you to define the layer's legend, and determine how the layers
will appear on the map.
168
o Labels: Enables you to define how labels will appear on the map. This tab is
displayed for vector layers only.
o Symbols: Enables you to define the shape of the symbols displayed on the map.
This tab is displayed for vector layers only.
Note: If you have a multi-carrier network, this tab is displayed in the Sectors layer
properties only if you have selected to display the properties of the required
carrier.
2. Edit the fields in each of the tabs, as required.
3. Click OK to save your changes and close the Layer Properties dialog box.
Filtering the Detailed Table Pane Display

The Detailed Table pane displays all the network elements in a selected layer, as well as their
properties. You can customize the table to display only selected property columns, or you can
filter the table to display only network elements that match your filter criteria.
Note: You can display the Detailed Table for vector layers only.
To filter the Detailed Table display

1. In the Layers pane, right-click the required layer and then select Detailed Table. The
network elements contained in the selected layer are displayed in the Detailed Table
pane, at the bottom of the map area.

169
select the columns to be displayed.
3. By default, all the network elements in the selected layer are displayed in the Detailed
Table. To filter the list of network elements according to specific properties, click
Options, and then click Filter. The <Network element> Filter dialog box is
displayed.
170
4. In the Column field, select the column to be filtered from the drop-down list.
5. In the Condition field, select the operator. For example, contains, does not
contain, and so on.
6. In the Value field, enter the value by which to filter the table.
Tip: When filtering the Detailed Table according to Sector Name, you can display
sectors that were previously saved as a selection, or display all sectors besides the
sectors in the selection. In the Condition field, select is in list or is not in list, and
then click . The Load Selection dialog box is displayed, enabling you to browse
to the file containing the required list of sectors.
7. Click Add. The current filter is displayed in the Filter By area.
8. If required, repeat steps 4–7 for each additional filter condition to apply.
9. Click OK to filter the Detailed Table according to the selected filter. The Detailed
Table displays only those network elements and properties that meet your filter
criteria. After the Detailed Table has been filtered, the word Filtered is displayed in
parentheses, including the number of items that matched the criteria and the total
number of items in the list. For example, the following Detailed Table shows that 6
out of a possible 5680 sectors have a SC of 502.
10. To clear the filter, click Options and then click Clear Filter.
171
Displaying Histograms
You can display a histogram of the map layers in order to view a graphical display of the
values in the layer. Each bar in the histogram is in proportion to the value of the data items it
represents. The histogram displays the values for 100% of the data in the selected layer, but
you can run a query to calculate the percentage of items between a range of values, as well
as set the range of values to be displayed in the histogram.
To display a histogram
1. In the Layers pane, right-click the layer whose histogram you want to display and on
the shortcut menu, click Histogram.
-OR-
Select the layer whose histogram you want to display, and on the Layer menu, click
Histogram.
-OR-
In the legend, click the browse button to open the Legends tab, and then click
Histogram.
The Histogram - <layer> dialog box is displayed, showing the histogram of the
selected layer.
172
The following information is displayed in the Statistics area of the histogram:

o Min: The lowest value displayed in the histogram.
o Max: The highest value displayed in the histogram.
o Sum: The sum of all the values measured in the histogram.
o Average: The average value displayed in the histogram.
o STD: The standard deviation of values in the histogram.
o No. of bins: The number of bins in which values were measured.
2. To define a query, in the Min and Max fields, enter the range of values to query. The
percentage of items that is between these values is displayed in the Percentage
field.
3. To limit the range of the x-axis displayed in the histogram, enter the required
minimum and maximum values in the From and To fields. The scale of the x-axis is
changed accordingly, and only those values between the required range are
displayed in the histogram.
4. Click to close the histogram.
Displaying the Layer Legend

You can display the legend of any layer that is displayed on the map. Once the legend is
displayed, you can edit it as required, as well as set the transparency level of the layer.
By default, the legend is a floating pane, which means it can be moved around the desktop,
but you can dock it to the right side of the main window, if required.
To display the layer legend

1. In the Layers pane, select the check box next to the layer whose legend you want to
display.
2. On the toolbar, click the Legend button .

-OR-
Press F2.
-OR-
Right-click the layer and on the menu, click Show Legend.
-OR-
On the View menu, click Legend.
173
The layer legend is displayed on the map.
3. If you have loaded more than one layer, select the legend to display from the drop-
down list.
4. To edit the legend, click the browse button . The Legend (<name of layer>)
174
5. By default, layers are not transparent. To adjust the transparency level of the layer,
move the transparency slider on the legend as required.
Map Analysis
The Map Analysis wizard enables you to carry out mathematical operations on the values of
up to eight raster map layers, provided that these layers have been loaded onto the Layers
pane, even if they are not currently displayed on the map. The analyses are carried out on the
value of each bin in the map, and the results are added as a layer under the GIS category, in
the Layers pane.
You can use the Map Analysis wizard to add a constant to all the map values or subtract the
values of one map from another to see the difference between the values of the two maps,
before and after optimization. You can define conditions for areas to be displayed, and you
can define thresholds. For example, you can take a regular Ec/Io or RSRQ map, and then use
the Map Analysis option to display only bins where the Ec/Io or RSRQ value is below a
defined threshold. You can also use the Map Analysis wizard to convert the map's units, for
example, from milliwatts to dBm.
Note: If you select a polygon on the map before you start the map analysis, the calculation
will be performed on the selected area only.
For more information on the Map Analysis wizard, refer to the Ultima Mentor Help.
Converting Raw Data into Text Format

You can export geo-located measurement-report data in any area selection on the map into
.txt or .csv format, which can then be imported and loaded into external tools such as ASSET
Design.
To convert raw data into text format

1. Create an area selection on the map.
2. On the Tools menu, select Convert Raw Data to Text Format.
175
If your selection contains both UMTS and LTE sectors, the Map Technology
Selection dialog box will be displayed, enabling you to select the required
technology.
The Convert Raw Data to Text Format dialog box is displayed.
3. In the Data source field, select one of the following options:

o Client Model: Data will be taken from the network model on your client.
o Rich Data: Rich data will be taken from the call database, via the server.
176
4. In the Export Directory field, click the browse button to select the directory to which
to export the converted raw data. A standard Windows save dialog box is displayed.
o In the Files of type field, select whether to convert the raw data to .txt or .csv
format. Both formats can be opened by Microsoft Excel.
o Click Save.
5. By default, the dates of all the available model days are displayed in the Time Filter
field, but you can filter the dates by clicking the browse button and then selecting
the required dates from the Date and Time Range dialog box.
 Select the required dates, and click OK to save your changes and close the dialog
box.
177
6. Click OK. A confirmation message is displayed notifying that the conversion

completed successfully.
178
Working with Calculations

While a calculation is running, its status is displayed in the Calculations pane. Once the
calculation is completed, its status changes to Valid, and you can perform actions on it.
The following calculations are supported:
 Analysis
 Neighbor List Plan
 Manual Neighbor List Plan
 Parameters Plan
 SC Plan
 PCI Plan
 Antenna Sectors Plan
 Overshooter Resolution Plan
To work with a calculation
1. Select the required calculation in the Calculations pane on the left of the main
window.
2. Right-click the selected calculation and then select the required option on the shortcut
menu.
-Or-
On the relevant menu, click the required option. Only the options that are applicable
to the selected calculation are enabled.
Note: The main and shortcut menus do not display the same actions.
This section describes the following actions:
 Loading Calculation Result Layers
 Viewing the Calculation Layers in the Detailed Table
 Opening Calculation Reports
 Displaying the Selection or Calculation Set on the Map
 Scheduling Recurring Calculations
For more information on working with calculations, refer to the Ultima Mentor Help.
179
Scheduling Recurring Calculations

After you have run an analysis or optimization in Mentor, you can use the same template to
schedule additional calculation tasks in the server.
To schedule a recurring calculation task

1. In the Calculations pane, select the analysis or optimization you would like to
schedule to be run automatically by the Mentor server.
2. On the Calculation menu, click Schedule as <Calculation> Task.
-OR-
Right-click the calculation, and on the shortcut menu, click Schedule as
<Calculation> Task.
and then the New <Calculation> Task wizard is displayed, enabling you to schedule
Loading Calculation Result Layers

After analysis or optimization calculations have finished running, you can display the
calculation layers on the map. For example, you can display the bad call rate layer for
analysis calculations, the HO-rate change layer for neighbor list optimizations, and the current
best power changes per carrier, for the antenna sectors optimizations.
To load a calculation results layer

1. In the Calculations pane, select the calculation for which you want to display a layer.
2. Right-click the calculation, and on the shortcut menu, click Load Layers.
-OR-
On the Calculation menu, click Load Layers.
The Layers dialog box is displayed, listing all the available layers for the selected
calculation.
180
3. In the Layers dialog box, select the layer(s) you want to load, and then click Load.
The layer is displayed in the Layers pane, with the name of the calculation, under the
Calculation Results category. For example, the following shows the Daily Speech
KPIs - Traffic and BH Speech KPIs - Traffic layers for Analysis1.
4. Click Close to close the Layers dialog box.

5. Select the check boxes next to the layers you want to display on the map. A progress
bar is displayed while the layers are loaded and displayed on the map.
Viewing the Calculation Layers in the Detailed Table

You can view the properties of a selected calculation layer in the Detailed Table pane. For
example, you can display a list of HO-rate changes for all the sectors in carrier 4.
If required, you can view multiple analysis layers that are in the same analysis report.
Note: You can display the Detailed Table only for calculation layers that are displayed as
vectors.
To view a calculation layer in the Detailed Table pane:

1. In the Layers pane, right-click the layer you want to display, and on the shortcut
menu, click Detailed Table. The layer is displayed in the Detailed Table -
Calculation Results\<calculation:layer> pane at the bottom of the map area.
181

Opening Calculation Reports

You can view the calculation reports as soon as the calculation has finished running, or any
time afterwards.
To open calculation reports

1. In the Calculations pane, select the calculation for which to view reports.
2. Right-click the calculation, and select Open Reports from the shortcut menu.
-OR-
On the Calculation menu, click Open Reports.
The <name of calculation> Reports dialog box is displayed, listing all the available
reports. By default, the reports are displayed in alphabetical order, but you can
182
change the order by sorting them in ascending order or according to size by clicking
Report Name or Size.
3. In the Report Name area, double-click the report you want to view, or select the
report and then click Open. The selected report is displayed in Excel format.
(Depending on your Excel security settings, you may be prompted to disable or
enable macros. Click Enable Macros.) The name of the report, the name of the
network, and the name of the calculation are displayed in the title bar of the report.
4. If the report contains tabs, select the relevant tab to view the different reports within
the report.
5. Click Close to close the <name of calculation> Reports dialog box.
For a detailed description of the tabs and fields in the calculation reports, refer to the Ultima
Mentor Help.
Exporting the Optimization Plan to the Planning Tool

You can export all neighbor list or antenna sectors optimization results to a planning tool such
as ASSET, and save them for later use from within the planning tool.
To export the optimization plan to the planning tool

1. In the Calculations pane, right click the neighbor list or power optimization that you
would like to export to the planning tool, and then click Export Plan to Planning
Tool. The Export dialog box is displayed showing a list of projects.
2. Select the project to which to export the optimization results and click Export. A
progress bar is displayed while the optimization plan is being exported, and then a
dialog box is displayed notifying whether the action was successful.
183
Validating the Plan Implementation

After the switch has executed the scripts, you should validate that the changes have been
fully implemented, as recommended. Review entries that were not implemented to identify the
reason for this, and then re-implement the plan, if required. You can check the new
configuration file on your local client, or in the Mentor server.
To validate the plan implementation

1. In the Calculations pane, select the optimization whose changes you want to
validate.
2. Right-click the calculation, and on the shortcut menu, click Validate Plan
Implementation.
-OR-
On the Calculation menu, click Validate Plan Implementation.
The relevant Validate Plan Implementation dialog box is displayed.
3. In the Location field, select the location of the current switch dump information. This
information will be used to ensure that the most recent parameters are used for the
validation. Mentor will compare the switch dump information to the neighbor list or
power plan, and validate its implementation.
o If you are using information stored on your local client, select Local, and then
click the browse button in the <Vendor> configuration field to browse to the
location of the latest switch dump data. If you have a multi-vendor environment,
browse to the location of the switch dump data for both vendors.
o If you are using an optimization from the Mentor server, select Server, and then
select the cluster to which the optimization belongs.
184
4. Click OK. A progress bar is displayed during the implementation validation, and then
the Validate Plan Implementation dialog box is displayed. If there are any
inconsistencies between the number of required changes, and the number of
implemented changes, this is displayed in the dialog box.
o Click Details to view any warnings.

o Click Reports to view the implementation validation reports.
5. Click Close to close the Validate Plan Implementation dialog box.
Note: The implementation validation reports are saved with the Network reports.
Viewing the Optimization Progress

As soon as the antenna sectors optimization starts running, the Optimization Progress
dialog box is displayed, enabling you to view the current progress of the optimization process.
If you have restarted an optimization, it shows the progress from the point at which the
optimization was stopped. By default, the Optimization Progress dialog box is displayed in its
compact format, but you can expand it to view more details. You can also close the
Optimization Progress dialog box at any time during the optimization, without stopping it.
To view the optimization progress
1. In the Calculations pane, right-click the antenna sectors optimization whose
progress you want to display, and on the shortcut menu, click Open Optimization
Progress Dialog.
185
The Optimization Progress dialog box is displayed.
From the Optimization Progress dialog box, you can do the following:
o Stop or Start the optimization. When you restart the optimization, it continues
looking for a better solution from the same point at which it was stopped.
o Click Properties to view the optimization properties.
o Click Changes to view the recommended changes and their optimized values.
o Click Reports to display a list of available reports.
o Click Details to display two tabs with additional information about the optimization
progress:
 Best Solution: Shows the best solution reached so far, showing the
improvement of each of the selected sub-goals.
 Improvement Progress: Shows a graph displaying the improvement progress
for each sub-goal, and the total improvement.
2. Click Close to close the Optimization Progress dialog box.
186
Network Properties
You can view general network properties, for example, geographical information or network
statistics, as well as carrier properties in the Network Properties dialog box. You can also
manage the hard handover, soft handover, and power configurations, as well as configure
advanced network properties, for example, neighbor list or antenna sectors optimization
properties.
To view or configure network properties

box is displayed.
187
The Network Properties dialog box contains the following tabs:

o General: Enables you to set the default time zone for the network, and to view
general network properties, for example, the name of the network and the
equipment vendor, and the number of network elements per type and technology.
o Carriers: Enables you to view the properties of each of the carriers in the
network, for example, the frequency upon which the carrier transmits. You can
also edit the carrier name that is displayed under the Sectors branch in the
Layers pane. This name is displayed only if the network contains more than one
carrier.
o Hard Handover: Enables you to manage the hard handover configurations
available in the network.
o Soft Handover: Enables you to manage the soft handover configurations
available in the network.
o Power: Enables you to manage the power configurations available in the network.
o Automatic Updates: Enables you to activate the Automatic Updates feature
that automatically downloads updates from the server, and define its settings.
o Advanced: Enables you to configure the various parameters that should be taken
into consideration when creating the model, and running the neighbor list and
antenna sectors optimizations.
2. Click the tabs you want to edit, and edit the fields as required.
Defining Advanced Network Properties

In the Advanced tab of the Network Properties dialog box, you can configure various
parameters that will be taken into consideration when creating the model, and running
analyses and optimizations. After running optimizations, you can view the parameters used,
and their current values, in the Network Properties report.
Note: By default, the advanced properties are preconfigured to their optimal values. You
should consult TEOCO Customer Support before making changes to these parameters in
order to fully understand the impact.
To configure the advanced properties

1. Open the Network Properties dialog box.
2. Select the Advanced tab. The Advanced tab shows all the parameters that are
taken into consideration when creating the model, and optimizing the neighbor list
and the antenna sectors. By default, the parameters are displayed according to
parameter group, but you can display them alphabetically, if required.
188
o Click to display the parameters alphabetically. Click the column header to sort
the parameters according to parameter name, or value.
o Click to display the parameters according to groups.
Depending on the vendor, the following groups of parameters, and their default
values, are displayed:
o Access Distance: Enables you to define the criteria for valid distance to the
access sector.
o Antenna Sectors Optimization: Enables you to define the settings that are taken
into consideration when running an antenna sectors optimization.
o Area Code Optimization: Enables you to define the settings that are taken into
consideration when running an area code optimization.
o Cell Footprint Report: Enables you to define the thresholds for good cell coverage
and quality.
189
o Ericsson Provisioning: Enables you to define the settings that are used in the
Ericsson implementation script, when exporting the network.
o Google Earth Display: Enables you to define how sectors are displayed in Google
Earth.
o GSM Positioning: Enables you to define the settings for GSM sectors in
positioning maps.
o HSDPA Optimization: Enables you to define the parameters that are taken into
consideration when running an HSDPA optimization.
o Huawei Provisioning: Enables you to define the settings that are used in the
Huawei implementation script, when exporting the network.
o Huawei SHOQualMin Optimization: Enables you to define the Huawei parameters
that are taken into consideration when running a parameters plan optimization.
o Import: Enables you to define the parameters that are taken into consideration
when importing the network.
o Inter-Frequency Neighbor List Optimization: Enables you to define the parameters
that are taken into consideration when optimizing the neighbor list between
sectors in different carriers.
o IRAT Neighbor List Optimization: Enables you to define the settings that are taken
into consideration when running an IRAT neighbor list optimization.
o LTE Log Processing: Enables you to define the settings that are taken into
consideration when processing logs in LTE networks.
o Maps: Enables you to define how the maps will be displayed in Mentor.
o Neighbor List Editor: Enables you to define the method by which the maximum
neighbor-list length for manual optimization is determined.
o Neighbor List Optimization: Enables you to define the settings that are taken into
consideration when running a neighbor list optimization on a UMTS sector
selection.
o Neighbor List Optimization - Inactive: Enables you to define the settings that are
taken into consideration when running a neighbor list optimization on a selection
that includes inactive sectors.
o Neighbor List Optimization - Indoor: Enables you to define the settings that are
taken into consideration when running a neighbor list optimization on a selection
that includes indoor sectors.
o Neighbor List Optimization - LTE: Enables you to define the settings that are
taken into consideration when running a neighbor list optimization on an LTE
sector selection.
o NSN Provisioning: Enables you to define the settings that are used in the NSN
implementation script, when exporting the network.
o Optimization Budget: Enables you to define the percentage of sectors to be
optimized, as well as the ratio of sectors whose power will be increased compared
to those whose power will be decreased.
o PCI Plan and Sector Identification: Enables you to define the parameters that are
taken into consideration when running a PCI plan optimization.
o Positioning: Enables you to define the parameters that are taken into
consideration when positioning the mobiles.
o Power Optimization: Enables you to define the settings that are taken into
consideration when running a power optimization.
o RAB Optimization: Enables you to define the settings that are taken into
consideration when running a RAB optimization.
190
o Reports: Enables you to define the parameters that are required for building
reports.
o Roaming: Enables you to define the parameters that are required for identifying
roaming mobiles in the network.
o SC Plan and Sector Identification: Enables you to define the parameters that are
taken into consideration when running a SC plan optimization.
o Time Zone: Enables you to set the time zone for the KPIs and the server where
the call-trace data files used in the model are stored.
o UMTS GSM Measurement Plan: Enables you to define the parameters used in
the UMTS-GSM measurement plan.
o UMTS Goals: Enables you to define the target thresholds for the antenna sectors
optimization sub-goals.
o Virtual Drive Test: Enables you to define the parameters used in virtual drive test
maps.
o ZTE Provisioning: Enables you to define the settings that are used in the ZTE
implementation script, when exporting the network.
3. Click the button next to the group of parameters you want to edit. The group is
expanded.
4. Hover over any parameter for a few seconds to display a tooltip that clarifies the
parameter's purpose.
5. Double click in the Value field next to the parameter you want to change, and enter
the new value.
Access Distance Parameters

Parameter Description
AVERAGE_NEIGHBOR_DISTANCE_FACTOR Defines the factor by which to multiply the

average distance to a sector's neighbors.
Default = 0.5
In order for a sector to be defined as having
access-distance issues, the weighted average
of the access distance must be larger than the
average distance to the sector's neighbors,
multiplied by this factor.
MIN_AVERAGE_DISTANCE_THRESHOLD Defines the minimum required average

distance between a sector and its neighbors.
Default = 500 m/1,640.5 ft
MIN_TOTAL_ACCESS_THRESHOLD Defines the minimum required number of call

setup attempts to a sector.
Default = 1,000.0
191
Antenna Sectors Optimization Parameters

IN_BUILDING_LOCK_POWER Defines whether in-building sectors should be

locked for power optimization.
Default = Yes
LOW_DURATION_THRESHOLD (second) Defines the message duration threshold below

which sectors will be locked for optimization.
Default = 100
The message duration statistics, per sector,
are displayed in the following Errors and
Warnings reports: Sectors with Low Message
Duration (UMTS) and Sectors with Low
Message Duration (LTE).
MAX_CPICH_LOCK_PWR_TILT_UP (dBm) Defines the CPICH threshold above which

sectors are locked for power and tilt up
Default = 35.5
optimization.
MAX_NBRS_LOCK_PWR_TILT_UP Defines the maximum allowed number of

neighbors allowed before sectors are locked
Default = 100
for power or tilt up optimization.
MAX_RELIABILITY Defines the reliability threshold above which

sectors will be locked for optimization, as they
Default = 5.0
are over sampled.
The reliability factor is displayed in the
following Model Errors and Warnings reports:
Sectors with Low Traffic Reliability (UMTS)
and Sectors with Low Volume Reliability Rate
(LTE).
MIN_CPICH_LOCK_PWR_TILT_DOWN (dBm) Defines the CPICH threshold below which

sectors are locked for power and tilt down
Default = 27.0
optimization.
MIN_RELIABILITY Defines the reliability threshold below which

sectors will be locked for optimization, as they
Default = 0.2
are under sampled.
The reliability factor is displayed in the
following Model Errors and Warnings reports:
Sectors with Low Traffic Reliability (UMTS)
and Sectors with Low Volume Reliability Rate
(LTE).
192
SECTOR_MAX_POWER_PERCENTAGE (%) Defines the maximum percentage of the

maximal transmit power allowed in order to
Default = 70
increase the power or electrical tilt of a sector
during optimization. If this limit is exceeded,
the power and tilt will be set at the current
value.
SURROUNDING_LOCK_RANGE Defines the distance within which sectors

(Meters/Feet) surrounding a sector with low message
duration or low reliability are locked.
Default = 1,000/3,281
Area Code Optimization Parameters

BORDER_ISSUES_NBRS_RATIO_TH The minimum ratio of adjacent sites with

different codes for a site to be considered a
Default = 0.5
Border site.
ISOLATED_NBRS_RATIO_TH The minimum ratio of adjacent cites with a

different code for a site to be considered an
Default = 0.85
Isolated site.
SAME_VS_DIFF_TH_RATIO The ratio between the closest adjacent site

with a different area code and the closest
Default = -95.0
adjacent site with the same area code, used to
determine Border sites.
Defining Cell Footprint Report Parameters

GOOD_ECIO_VALUE (dB) The threshold above which the quality is

considered good.
Default = -10.0
Note: This parameter is displayed for UMTS
networks only.
GOOD_RSCP_VALUE (dBm) The threshold above which the cell coverage

is considered good.
Default = -85.0
Note: This parameter is displayed for UMTS
networks only.
193
GOOD_RSRP_VALUE (dBm) The threshold above which the cell coverage

is considered good.
Default = -95.0
Note: This parameter is displayed for LTE
networks only.
GOOD_RSRQ_VALUE (dB) The threshold above which the quality is

considered good.
Default = -15.0
Note: This parameter is displayed for LTE
networks only.
Ericsson Provisioning Parameters

ASSET_XML_VERSION Defines the version of ASSET to which to

export the optimization plan.
CREATE_ASSET_XML_FILE Defines whether the optimization plan should

be exported in ASSET format.
Default = No
 Yes: The provisioning script is exported in
both ASSET and OSS formats.
 No: The provisioning script is exported in
OSS format only.
ERICSSON_E-TILT_ENABLE_GROUPING Defines whether more than one E-tilt update

command should be sent at a time, in order to
Default = No
speed up the process of changing the E-tilt
plan.
ERICSSON_E-TILT_ENABLE_ROLLBACK Defines whether the output of the E-tilt

provisioning will include a rollback script,
Default = Yes
enabling a rollback to the original E-tilt plan.
ERICSSON_E-TILT_GROUP_SIZE Defines the number of sectors that can be

included in each E-tilt update command.
Default = 6
ERICSSON_INTER_FREQ_NL_qOFFSET1SN Defines the default value for the

qOFFSET1SN parameter for new inter-
Default = 0
frequency neighbors.
ERICSSON_INTER_FREQ_NL_qOFFSET2SN Defines the default value for the

qOFFSET2SN parameter for new inter-
Default = 0
frequency neighbors.
194
ERICSSON_NL_ENABLE_GROUPING Defines whether more than one neighbor-list

update command should be sent at a time, in
Default = No
order to speed up the process of changing the
neighbor list.
ERICSSON_NL_ENABLE_ROLLBACK Defines whether the output of the neighbor-list

Default = Yes
enabling a rollback to the original neighbor list
plan.
ERICSSON_NL_GROUP_SIZE Defines the number of sectors that can be

included in each neighbor-list update
Default = 5
command.
ERICSSON_NL_SPLIT_DELETE_ADD Defines whether there should be separate

batches for neighbors that are added, and
Default = Yes
those that are deleted.
ERICSSON_NL_qOFFSET1SN Defines the default value for the

qOFFSET1SN parameter for new neighbors.
Default = 0
ERICSSON_NL_qOFFSET2SN Defines the default value for the

qOFFSET2SN parameter for new neighbors.
Default = 0
ERICSSON_PARAMETERS_ENABLE_ Defines whether the output of the parameters

ROLLBACK provisioning will include a rollback script,
enabling a rollback to the original parameters
Default = Yes
plan.
ERICSSON_POWER_ENABLE_GROUPING Defines whether more than one power-update

command should be sent at a time, in order to
Default = No
speed up the process of changing the power
plan.
ERICSSON_POWER_ENABLE_ROLLBACK Defines whether the output of the power

Default = Yes
enabling a rollback to the original power plan.
ERICSSON_POWER_GROUP_SIZE Defines the number of sectors that can be

included in each power-update command.
Default = 5
ERICSSON_SC_ENABLE_ROLLBACK Defines whether the output of the SC

optimization will include a rollback script,
Default = Yes
enabling a rollback to the original SC plan.
195
UMTS_GSM_HO_ID_TEMPLATE Defines the naming convention for UMTS-

GSM handover identifiers.
Default = ${TARGET_ID}
 ${SOURCE_NAME}
 ${SOURCE_ID}
 ${TARGET_NAME}
 ${TARGET_ID}
UMTS_UMTS_HO_ID_TEMPLATE Defines the naming convention for UMTS

handover identifiers.
Default = ${TARGET_NAME}
 ${SOURCE_NAME}
 ${SOURCE_ID}
 ${TARGET_NAME}
 ${TARGET_ID}
Google Earth Display Parameters

EXTEND_SIDES_TO_GROUND Defines whether the sectors should be

displayed on the ground. If not, they will be
Default = No
elevated so that they do not obscure buildings
and so on.
GOOGLE_EXPORT_TILE_SIZE Defines the size of each section of the map, to

prevent distortion.
Default = 100,000
SECTOR_SIZE (Meters/Feet) Defines the size at which sectors are

displayed on the Google Earth map.
Default = 150/492
TRANSPARENCY Defines the transparency at which the sectors

are displayed on the Google Earth map,
Default = 255
where 0 is transparent, and 255 is opaque.
WRITE_GIS_LABELS Defines whether to export and display the GIS

layer labels on the Google Earth map.
Default = Yes
WRITE_SECTOR_NAMES Defines whether to export and display the

sector names on the Google Earth map.
Default = Yes
WRITE_SITE_NAMES Defines whether to export and display the site

names on the Google Earth map.
Default = Yes
196
GSM Positioning Parameters

COLOR_MEASURED_NBRS_BY_RX_LEVEL Defines whether to color measured neighbors

in the virtual drive test maps according to
Default = No
RxLevel.
CONCATENATE_CALL_FROM_MULTIPLE_ Defines whether to enable concatenating a

BSCS call that was served by multiple BSCs.
Default = No
DISPLAY_MTR_HEADER Defines whether to display header fields for

Ericsson MTR records in the Detailed Table.
Default = No
ENABLE_GSM_TRACE_POSITIONING Defines whether to enable using GSM Call

Traces for virtual drive test maps.
Default = No
HSDPA Optimization Parameters

NACK_TARGET_RATIO_THRESHOLD (%) Defines the NACK-ratio threshold above which

the CqiAdjustmentOn parameter should be
Default = 10
turned on, which enables Mentor to
dynamically correct the CQI.
Huawei Provisioning Parameters

HUAWEI_MAX_MISSING_CELLIDS (%) Defines the threshold of sectors missing from

the new switch dump above which the script
Default = 5.0
will not be used for the power changes.
 If the percentage is below this threshold,
the sectors will not be added to the script,
and a warning will be displayed that the
sectors were removed from the power
optimization results.
 If the percentage is above this threshold,
the power changes will not be
implemented according to this script.
HUAWEI_PARAMETERS_ENABLE_ Defines whether the output of the parameters

ROLLBACK plan provisioning will include a rollback script,
enabling a rollback to the original parameters
Default = Yes
plan.
197
HUAWEI_PRIORITY_FLAG Defines whether to enable the priority flag in

the neighbor list provisioning script, and show
Default = Yes
the priority of the optimized neighbors in the
script.
HUAWEI_SC_ENABLE_ROLLBACK Defines whether the output of the SC

Default = Yes
HUAWEI_SIB11IND Defines whether to include neighbor

relationships in System Information Block 11
Default = Yes
(SIB11).
HUAWEI_SIB12IND Defines whether to include neighbor

relationships in System Information Block 12
Default = No
(SIB12).
HUAWEI_TPENALTYHCSRESELECT Defines the Hierarchical Cell Structure (HCS)

cell reselection penalty timer.
Default = D0
HUAWEI_UMTS_NL_ENABLE_GROUPING Defines whether more than one neighbor-list

Default = No
neighbor list.
HUAWEI_UMTS_NL_ENABLE_ROLLBACK Defines whether the output of the neighbor-list

Default = Yes
plan.
HUAWEI_UMTS_ NL_GROUP_SIZE Defines the number of sectors that can be

included in each neighbor-list update
Default = 5
command.
HUAWEI_UMTS_POWER_ENABLE_ Defines whether the output of the power

ROLLBACK provisioning will include a rollback script,
Default = Yes
198
Huawei SHOQualMin Optimization Parameters

MIN_RLCRST_DROPS (%) Defines the minimum percentage of RLCRst

drops allowed. Below this, the sector is locked
Default = 10.0
for optimization.
SHOQUALMIN_SCORE_THRESHOLD (%) Defines the threshold below which the sector

will be locked for optimization.
Default = 0.0
Import Parameters
GROUP_SITES_BY_DISTANCE Defines whether the sites should be grouped

by distance.
Default = Yes
IMP_EXP_IN_UTM Defines whether the network should be

Default = No exported in UTM format.
 Yes: The network will be exported in
Easting/Northing format.
 No: The network will be exported in
Lat/Long format.
MAX_CO_SC_PATHS_COUNT Defines the maximum number of co-SC paths

Default = 100 for tier 2 or tier 3 handovers, as displayed in
the tab of the Import Report.
MAX_SITES_GROUP_DISTANCE Defines the maximum distance for grouping

(Meters/Feet) sites, if the GROUP_SITES_BY_DISTANCE
parameter is set to Yes.
Default = (5/16)
NOKIA_WCEL_FIELD_FOR_SECTOR_NAME Defines the field from which to take the name

of the Nokia sectors when importing the
Default = id
network:
 id: The sector name will be a
concatenation of the NodeB name and the
WCEL ID.
 Cell Additional Info: The sector name will
be taken from the CellAdditionalInfo field.
 name: The sector name will be taken from
the name field.
199
SECTORS_GROUPING_METHOD Defines the method used for grouping sectors.

Default = Default method  By azimuth
 By switch ID
 By scrambling code
 Default: The default setting per vendor, as
follows: Ericsson - by switch ID, Huawei
and NSN - by scrambling code.
Inter-Frequency Neighbor List Optimization Parameters

ALLOW_INDOOR_INTER_BAND Defines whether to allow inter-frequency

handovers for indoor sectors.
Default = No
INTER_FREQ_CO_SITE_HANDOVERS Defines whether to lock the co-site handovers

at the top of the neighbor list, even if they do
Default = Yes
not have enough handovers.
INTER_FREQ_IN_BUILDING_LOCK_NL Defines whether in-building sectors should be

locked for neighbor-list optimization.
Default = Yes
INTER_FREQ_MAX_NEIGHBORS Defines the maximum allowed number of

neighbors for the neighbor list optimization.
Default = 20
INTER_FREQ_MAX_NEIGHBOR_RANGE Defines the maximum distance within which

(Meters/Feet) sectors can be selected for the neighbor list.
Any neighbors that are located further than this
Default = 15,000/49,215
range are deleted from the neighbor list, unless
they have been locked for optimization.
Note: This parameter can be overridden per
sector, in the Sector Properties dialog box.
INTER_FREQ_MINIMIZE_DELETIONS Defines whether neighbors that existed in the

original neighbor list should be kept in new
Default = No
neighbor list.
Note: This parameter should be changed to
Yes only when you want to run a very
conservative neighbor list optimization, while
trying not to remove any of the existing
neighbors. For example, when new temporary
sectors are activated, and you want to add
them to the neighbor list while trying not to
remove any existing neighbors.
200
INTER_FREQ_MIN_HO_COUNT Defines the minimum number of handovers

from source to target, for sectors to be in the
Default = 10
neighbor list.
INTER_FREQ_MIN_NEIGHBOR_RATE Defines the minimal handover rate from source

to target, for a sector to be in the neighbor list.
Default = 0.5
The HO rate is calculated based on the HO
count between a specific source and target,
divided by the total number of HO counts from
the source sector.
All neighbors in the neighbor list topology
whose handover rate is less than this value will
be deleted from the neighbor list.
All non-neighbors (detected sectors) whose
potential HO rate is more than this value will be
added to the neighbor list.
INTER_FREQ_MIN_TOTAL_HO_COUNT Defines the minimum total handover counts for

all possible neighbors, per source sector. Any
Default = 500
source sector with fewer handover counts will
not be optimized. These sectors will be
reported in a special report for sectors with low
handover statistics.
If you define the INTER_FREQ_MIN_TOTAL
HO_COUNT below 500, the neighbor list will
have a weak statistical base. If there are not
enough messages available, you can make a
special optimization plan for the specific low-
count sectors using the
INTER_FREQUENCY_MINIMIZE_DELETIONS
parameter and the lock feature, which will
prevent the old neighbors from being deleted or
having their priority changed.
201
IRAT Neighbor List Optimization Parameters

IRAT_CANCEL_CO_BCCH_BSIC Defines whether to fix Co-BCCH/BSIC

problems by adding the neighbor with the
Default = No
higher handover count to the neighbor list. Co-
BCCH/BSIC problems are caused when two
GSM neighbors with the same BCCH/BSIC
combination are identified for the same UMTS
source sector.
 No: Mentor will not optimize the neighbor
list for the UMTS source sector even if one
of the GSM neighbors has enough
handover counts to be added to the
neighbor list. The co-BCCH/BSIC problem
is displayed in the Co-BCCH-BSIC report,
but a script will not be created for the
sector.
 Yes: Mentor will decide which co-
BCCH/BSIC neighbor to add to the
neighbor list, based on the higher handover
count. The co-BCCH/BSIC problem will be
listed in the Co-BCCH-BSIC report, and a
neighbor list script will be created.
IRAT_FORCE_CO_LOCATED Defines whether to lock the IRAT neighbor to a

co-located GSM sector in the neighbor list,
Default = Yes
even if they do not have enough handover
counts. See
IRAT_MAX_DISTANCE_FOR_CO_
LOCATED_NBRS.
IRAT_HUAWEI_COUNT_FACTOR_FOR_ Defines the factor used when calculating the

NON_NBR number of HO counts for each pair of IRAT
neighbors. HO counts are multiplied using this
Default = 10.0
factor only when the measured GSM sector is
not in the neighbor list of the reference sector.
Note: This parameter is relevant for Huawei
networks only.
IRAT_IN_BUILDING_LOCK_NL Defines whether in-building sectors should be

Default = Yes
IRAT_LOW_COUNT Defines the minimum number of handovers

from source to target, for a GSM sector to be in
Default = 5
the IRAT neighbor list.
202
IRAT_MAXIMAL_NEIGHBOR_RANGE Defines the maximum distance within which

(Meters/Feet) GSM sectors can be included in the IRAT
neighbor list. Any GSM neighbors that are
Default = 15,000/49,215
located further than this threshold are deleted
from the IRAT neighbor list, unless they have
been locked for optimization.
IRAT_MAX_DISTANCE_FOR_CO_LOCATED_ Defines the maximum distance between UMTS

NBRS (Meters/Feet) and GSM sectors for them to be defined as
being co-located (belonging to the same site).
Default = 150/492
IRAT_MAX_NEIGHBORS Defines the maximum number of UMTS to

GSM neighbors in an IRAT neighbor list. This
Default = 18
parameter should never exceed the hardware
limit.
IRAT_MINIMAL_NEIGHBOR_RATE (%) Defines the minimum handover rate from

source to target, for a GSM sector to be in the
Default = 1.0
IRAT neighbor list. The HO rate is calculated
based on the HO count between a specific
source and target, divided by the total number
of HO counts from the source sector.
IRAT_MINIMIZE_DELETIONS Defines whether the IRAT optimization

algorithm should be modified in order to try and
Default = No
keep all existing neighbors in the neighbor list.
IRAT_MIN_TOTAL_HO_COUNT Defines the minimum total IRAT handover

counts for all possible neighbors, per UMTS
Default = 50
source sector. Any source sector with fewer
handover counts will not be optimized. These
sectors will be reported in a special report for
sectors with low handover statistics.
IRAT_NBR_OPT_HUAWEI_USE_KPI Defines whether the IRAT optimization will be

run using KPIs or logs.
Default =No
 Yes: The IRAT optimization will be run
using the KPIs.
 No: The IRAT optimization will be run using
the logs.
203
IRAT_RECIPROCITY_LEVEL Defines the level of reciprocity (symmetry)

between incoming and outgoing IRAT
Default = Recommended
neighbors.
 None: Mentor will not try forcing neighbors
to be reciprocal. Reciprocal neighbors are
two sectors that exist in each other's
neighbor lists.
 Recommended: Neighbors will be added
to the bottom of the list if there is room,
based on the IRAT_MAX_NEIGHBORS
parameter. For example, if the neighbor-list
algorithm decides that a reciprocal neighbor
should be deleted from the neighbor list
due to a low HO count, the Recommended
option will restore it to the bottom of the
neighbor list, if there is room.
By default, Mentor will add neighbors to
sectors outside the selection set to enable
reciprocity, based on the
RECIPROCITY_CHANGES_IN_CALC_
SET parameter.
 Required: Reciprocity is mandatory.
Mentor will add neighbors to sectors
outside the selection set, if necessary, to
force reciprocity, and all neighbor relations
in the optimized plan that are not reciprocal
will be deleted.
For example, if there is not enough room
for sector A to be part of sector B's
neighbor list, based on the
IRAT_MAX_NEIGHBORS parameter,
sector B will be removed from sector A's
neighbor list to maintain reciprocity.
Note: This option is not recommended as it
imposes a strong limitation on the neighbor
list.
MAX_GSM_TO_UMTS_RELATIONS Defines the maximum allowed number of GSM

to UMTS neighbors.
Default = 18
MAX_TOTAL_GSM_RELATIONS Defines the maximum allowed number of GSM

neighbors.
Default = 18
RECIPROCITY_CHANGES_IN_IRAT_CALC_ Defines whether to add neighbors to sectors

SET outside the selection set in order to enable
reciprocity when the
Default = Add only
IRAT_RECIPROCITY_LEVEL parameter is set
to "Recommended".
204
LTE Log Processing Parameters

ERICSSON_LTE_MAX_INTERVAL_ Defines the maximum time, in milliseconds,

BETWEEN_EVENTS between events in Ericsson LTE sessions.
After this time, it is assumed the session has
Default = 60,000
ended.
Map Parameters
ARC_MAPS_DISTANCE_MAX (Km/Miles) Defines the maximum distance between the

arcs in the Arc map.
Default = 32.0/19.8848
ARC_MAPS_DISTANCE_MIN (Km/Miles) Defines the minimum distance between the

arcs in the Arc map.
Default = 1.6/0.99424
ARC_MAPS_DISTANCE_STEP (Km/Miles) Defines the distance between the arcs in the

Arc map.
Default = 1.6/0.99424
ARC_MAPS_LINES_THICKNESS Defines the thickness of the arcs displayed in

(Meters/Feet) the Arc map.
Default = 100/328
ARC_MAPS_PERCENT_STEP (%) Defines the distribution of traffic between each

arc in the Arc map.
Default = 20
DEFAULT_BUSY_HOUR Defines the busy hour for maps that are

generated without a model, from the call
Default = 17
database.
EVENT_MAP_MAX_RECORDS_FROM_ Defines the maximum number of records to

CALL_DB fetch from the call database for Additional
Event maps.
Default = 1000
FILTER_UNSPECIFIED_DROPS Defines whether Mentor should filter out

unspecified events in the Drop map.
Default = No
LINES_TO_NEIGHBORS Defines whether Mentor should display lines

between associated neighbors.
Default = Yes
205
LTE_OVERLAPPING_RSRP_DELTA (dB) Defines the difference in power between

candidates and the serving cell in order for
Default = 6.0
overlapping samples to be displayed on the
map.
MAPS_BIN_SIZE (Meters/Feet) Defines the default bin size used for any map
displayed.
Default = 50/164
MAPS_SPREAD_STD_FOR_UMTS Defines the spreading parameter for drop

maps displayed for UMTS networks.
Default = 100.0
MAP_EXTENDED_AREA_RANGE Defines the additional area, beyond the

(Meters/Feet) rectangle bounding the selected sectors, for
which any map is shown.
Default = 10,000/32,810
MAXIMAL_RECOMMENDED_MAP_SIZE Defines the maximum recommended map

area that a sector selection should cover when
Default = 500 000/310,686 the data source is Rich Data. If this
recommendation is exceeded, a message will
be displayed warning of performance
degradation.
MAX_DISTANCE_PER_SECTOR_CO_PCI_ Defines the maximum distance between two

LAYER (Km) co-PCI sectors.
Default = 50
MAX_DISTANCE_PER_SECTOR_CO_SC_ Defines the maximum distance between two

LAYER (Km) co-SC sectors.
Default = 50
MAX_NMB_OF_PER_SECTOR_MAPS Defines the maximum numbers of sectors for

which you can create a separate map during
Default = 50
the network analysis.
MAX_NUMBER_OF_BINS Defines the maximum number of bins in a

map.
Default = 4,000,000
MAX_RECORDS_FROM_CALLS_DB Defines the maximum number of records to

retrieve from the call database.
Default = 1,000,000
MAX_UMTS_INDOOR_OMNI_SHAPES_TO_ Defines the maximum number of shapes that

SHOW will be displayed for indoor omni antennas in
the same position.
Default = 1
Note: This is only relevant for auto-scaled
shapes.
206
MAX_UMTS_SHAPES_TO_SHOW Defines the maximum number of shapes that

will be displayed for sectors in the same
Default = 12
position with the same azimuth. For example,
indoor sectors.
Note: This is only relevant for auto-scaled
shapes.
PILOT_DOMINANCE_DELTA_UMTS (dB) Defines the minimum difference in power

required between the first and second pilots in
Default = 6.0
each bin, in order for the sample to display
pilot dominance on the map.
POLLUTING_PILOT_THRESHOLD (dB) Defines the difference in dB between the best

serving pilot's Ec/Io and all other detected
Default = 5.0
pilots, below which a pilot is considered a
polluter.
VDT_LASSO_MAX_NUMBER_OF_BINS Defines the maximum allowed number of bins

in a lasso area selection for virtual drive test
Default = 10,000
maps.
Neighbor List Editor Parameters

UMTS_NL_LIMIT_TYPE Defines how the maximum neighbor-list length

is determined:
Default = Limit
 Hard Limit: The maximum neighbor-list
length as defined by the hardware vendor.
A message is displayed if the soft limit is
exceeded.
 Soft Limit: The maximum neighbor-list
length as defined by the user in Mentor.
207
Neighbor List Optimization Parameters

AS_COUNT_FACTOR_FOR_NEIGHBOR Defines the factor used when calculating the

number of HO counts for each pair whenever a
Default = 1.0
sector within a specific range ((1a+1b)/2) is
measured and reported in the call-trace data.
HO counts are multiplied by this factor only
when the measured sector is in the neighbor
list of the reference sector.
When this parameter is set to 1, the HO count
is the exact number of HO counts between the
two neighbors, without any factoring. For
example, if sector A is added 100 times per
day as a soft handover to sector B, the HO
count both in Mentor and the OSS will be 100.
AS_COUNT_FACTOR_FOR_NON_ Defines the factor used when calculating the

NEIGHBOR number of HO counts for each pair whenever a
sector within a specific range ((1a+1b)/2) is
Default = 1.0
measured and reported in the call-trace data.
when the measured sector is not in the
neighbor list of the reference sector.
For example, if sector A is detected 100 times
per day above the specific range by sector B,
the potential HO count in Mentor will be 100.
This means that if sector A would be added as
a neighbor to sector B, there would be 100 HO
counts between these two sectors.
FIX_CO_SCRAMBLING_CODE_PROBLEMS Defines whether to fix co-SC problems by

adding the co-SC neighbor with the higher
Default = Yes
handover count to the neighbor list. Co-SC
problems are caused when two neighbors with
the same scrambling code are identified for the
same source sector.
 Yes: Mentor will decide which Co-SC
neighbor to add to the neighbor list, based
on the higher handover count. The Co-SC
problem will be listed in the Potential Co-
SC Targets report, and a neighbor list
script will be created.
 No: Mentor will not include either of the
neighbors in the source sector neighbor
list, even if one of the neighbors has
enough handover counts to be added. The
Co-SC problem will be displayed in the
Potential Co-SC Targets report, but a script
will not be created for this sector.
208
IN_BUILDING_LOCK_NL Defines whether in-building sectors should be

Default = Yes
KEEP_FIRST_TIER Defines whether to keep tier 1 neighbors in the

neighbor list.
Default = No
Mentor automatically calculates the tiers for
each sector, where the most natural neighbors
are considered tier1 neighbors, for example
softer neighbors or the nearest neighbors
facing the source sector.
The algorithm that determines the tier number
considers arguments such as HO rate and
distance from the neighboring sectors.
MAXIMAL_NEIGHBOR_RANGE (Meters/Feet) Defines the maximum distance within which

sectors can be selected for the neighbor list.
Default = 25,000/82,025
MAXIMUM_TOTAL_NUMBER_OF_ Defines the maximum allowed number of

NEIGHBORS neighbors (Intra-frequency, Inter-frequency,
and IRAT) for the neighbor list optimization.
Default = 72
These neighbors will be saved during the
switch dump import, for further use during the
neighbor list optimization.
MAX_HO_DELETE_RATE_FROM_KPIS (%) Defines the threshold below which to delete

handovers, even if the HO rate from the call-
Default = 0.0
trace data is high.
209
MINIMAL_NEIGHBOR_RATE (%) Defines the minimal handover rate from source

Default = 0.5
The HO rate is calculated according to the HO
count between a specific source and target as
a percentage of the total number of HO counts
from the source sector.
 If the parameter USE_HYSTERESIS_
FOR_EXISTING_NBRS is set to No:
o All neighbors in the neighbor list
topology whose handover rate is less
than this value will be deleted from the
neighbor list.
o All non-neighbors (detected sectors)
whose potential HO rate is more than
this value will be added to the neighbor
list.
 If the parameter USE_HYSTERESIS_
FOR_EXISTING_NBRS is set to Yes, All
non-neighbors (detected sectors) whose
potential HO rate is more than this value
will be added to the neighbor list.
MINIMAL_NEIGHBOR_RATE_DELETION (%) Defines the minimal handover rate from source

Default = 0.3
If the parameter
USE_HYSTERESIS_FOR_EXISTING_NBRS
is set to Yes, all neighbors in the neighbor list
topology whose handover rate is less than this
value will be deleted from the neighbor list.
MINIMIZE_DELETIONS Defines whether neighbors that existed in the

Default = No
neighbor list.
MIN_DISTANCE_REMOVE_EXISTING_ Defines the distance below which neighbors

HANDOVERS should not be deleted.
Default = 0
210
MIN_HO_ADD_RATE_FROM_KPIS (%) Defines the threshold above which HOs will be

considered, even if the rate from the call-trace
Default = 4.0
data is low.
MIN_HO_COUNT Defines the minimum number of handovers

Default = 10
neighbor list.
MIN_HO_COUNT_DELETION Defines the handover from source to target

threshold, below which sectors will be removed
Default = 6
from neighbor list.
MIN_HO_RATE_PRIORITY_FOR_ Defines the minimum HO rate for neighbors to

GROUP1 (%) be added to priority group 1.
Default = 5.0 Note: This parameter is relevant only when the
UMTS_NL_GROUPING parameter is defined
as Minimal HO rate.

as Minimal HO rate.

as Minimal HO rate.

as Minimal HO rate.
211
MIN_TOTAL_HO_COUNT Defines the minimum total handover counts for

Default = 500
If you define the MIN_TOTAL_HO_COUNT
below 500, the neighbor list will have a weak
statistical base. If there are not enough
messages available, you can make a special
optimization plan for the specific low-count
sectors using the MINIMIZE_DELETIONS
parameter and the lock feature, which will
prevent the old neighbors from being deleted
or having their priority changed.
NSN_AS_COUNT_FACTOR_FOR_NON_ Defines the factor used in NSN networks when

NEIGHBOR calculating the number of HO counts for each
pair whenever a sector within a specific range
Default = 1.0
((1a+1b)/2) is measured and reported in the
call-trace data.
when the measured sector is not in the
neighbor list of the reference sector.
NSN_KPI_FACTOR_FOR_ACTIVE_SET Defines the factor that is applied on the NSN

active set counter.
Default = 1.0
NSN_KPI_FACTOR_FOR_DETECTED Defines the factor that is applied on the NSN

detected cells counter.
Default = 0.017
NSN_KPI_FACTOR_FOR_FAILURE Defines the negative factor that is applied on

the NSN active set counter.
Default = 0.0
NSN_SWITCH_COUNT_FACTOR_FOR_ Defines the factor by which to multiply the

NEIGHBOR number of potential HO counts to sectors that
appear in the neighbor list. HO counts are
Default = 1.0
multiplied by this factor only when the
measured sector is in the neighbor list of the
reference sector.
212
NSN_SWITCH_COUNT_FACTOR_FOR_ Defines the factor by which to multiply the

NON_NEIGHBOR number of potential HO counts to non-
neighboring sectors. The number of potential
Default = 2.0
HO counts from a source sector to a target
sector not currently defined as a neighbor is
based on the number of times the SC of the
non-neighbor was detected.
By default, this value is factored by 2 to take
into account the fact that an SC belonging to
the detected set has a lower chance of being
measured than the SC of a defined neighbor
belonging to the monitored set.
RECIPROCITY_CHANGES_IN_CALC_SET Defines whether to add neighbors to sectors

outside the selection set, or add and delete
Default = Add only
neighbors, in order to enable reciprocity when
the RECIPROCITY_LEVEL parameter is set to
"Recommended".
RECIPROCITY_CHANGES_IN_CALC_SET_ Defines whether to add neighbors to inactive

INACTIVE sectors outside the selection set, or add and
delete neighbors, in order to enable reciprocity
Default = Add only
when the RECIPROCITY_LEVEL parameter is
set to "Recommended".
RECIPROCITY_CHANGES_IN_CALC_SET_ Defines whether to add neighbors to indoor

INDOOR sectors outside the selection set, or add and
Default = Add only
when the RECIPROCITY_LEVEL parameter is
213
RECIPROCITY_LEVEL Defines the level of reciprocity (symmetry)

between incoming and outgoing neighbors.
Default = Recommended
neighbor lists.
based on the UMTS_MAX_NEIGHBORS
algorithm decides that a reciprocal
neighbor should be deleted from the
neighbor list due to a low HO count, the
Recommended option will restore it to the
bottom of the neighbor list, if there is room.
SET parameter.
will be deleted.
UMTS_MAX_NEIGHBORS parameter,
Notes:
o This option is not recommended,
except in specific cases such as indoor
sites, as it imposes a strong limitation
on the neighbor list.
o If the target sector's neighbor list is full,
but the handover rate to this sector is
above a predefined threshold,
reciprocity will be relaxed and the
handover will be added without forcing
reciprocity.
SOFTER_HANDOVERS Defines whether to lock the softer handovers at

the top of the neighbor list, even if they do not
Default = Yes
have enough handovers.
214
SON_SELECTION_TYPE Defines the cell selection upon which the

optimization should run.
Default = BOTH
 ACTIVE: Run the optimization only upon
the active cells within the selection.
 NON_ACTIVE: Run the optimization only
upon the non-active cells within the
selection.
 BOTH: Run the optimization upon both
active and non-active cells within the
selection.
SWITCH_COUNT_FACTOR_FOR_NEIGHBOR Defines the factor by which to multiply the

number of potential HO counts to sectors that
Default = 1.0
appear in the neighbor list. HO counts are
multiplied by this factor only when the
measured sector is in the neighbor list of the
reference sector.
SWITCH_COUNT_FACTOR_FOR_NON_ Defines the factor by which to multiply the

NEIGHBOR number of potential HO counts to non-
neighboring sectors. The number of potential
Default = 2.0
HO counts from a source sector to a target
sector not currently defined as a neighbor is
based on the number of times the SC of the
non-neighbor was detected.
By default, this value is factored by 2 to take
into account the fact that an SC belonging to
the detected set has a lower chance of being
measured than the SC of a defined neighbor
belonging to the monitored set.
UMTS_MAX_NEIGHBORS Defines the maximum number of neighbors

allowed in the optimized neighbor list. This
Default = 26
limit.
If you want to reduce the number of neighbors
to make a compact neighbor list, you should do
so using the MIN_HO_COUNT,
MIN_TOTAL_HO_COUNT, and
MINIMAL_NEIGHBOR_RATE parameters.
UMTS_MAX_NEIGHBORS_HUAWEI Defines the maximum number of neighbors

allowed in the optimized Huawei neighbor list.
Default = 31
This parameter should never exceed the
hardware limit.
215
UMTS_NL_GROUPING Defines the method used to group neighbors in

order to reduce the number of script
Default = Disabled
commands due to priority changes.
 Disabled: This feature is disabled and
there is no grouping of neighbors.
 Minimal HO rate: Mentor divides
neighbors into groups based on the
MIN_HO_RATE_PRIORITY_
FOR_GROUP parameter. Each neighbor
will be assigned to a group based on it HO
rate compared to the minimal HO rate of
this group.
 Fixed size: Grouping based on
UMTS_NL_GROUP_SIZE parameter.
UMTS_NL_GROUP_SIZE Defines the maximum number of neighbors in

each priority group. All neighbors in the group
Default = 10
will have the same priority.
For example, if there are 24 neighbors there
would be 10 neighbors with priority 1 in group
1, 10 neighbors with priority 2 in group 2, and 4
neighbors with priority 3 in group 3. Group 4
would not be created.
216
USE_HYSTERESIS_FOR_EXISTING_NBRS Defines whether to activate hysteresis

thresholds in the neighbor list optimization.
Default = No
 Yes:
than the value in the
MINIMAL_NEIGHBOR_RATE
_DELETION parameter will be deleted
from the neighbor list.
the value in the
parameter will be added to the
neighbor list.
 No:
than the value in the
parameter will be deleted from the
neighbor list.
the value in the
parameter will be added to the
neighbor list.
ZTE_NL_HIGH_PRIORITY_THRESHOLD (%) Defines the minimum HO rate for neighbors to

be added to priority group 1.
Default = 5.0
ZTE_NL_LOW_PRIORITY_THRESHOLD (%) Defines the minimum HO rate for neighbors to

be added to priority group 2. All neighbors with
Default = 1.0
an HO rate below this threshold will be added
to priority group 3.
217
Neighbor List Optimization Parameters for Inactive Sectors

FIX_CO_SCRAMBLING_CODE_PROBLEMS_ Defines whether to fix co-SC problems by

INACTIVE adding the co-SC neighbor with the higher
handover count to the neighbor list. Co-SC
Default = Yes
the same scrambling code are identified for the
same source sector.
 Yes: Mentor will decide which Co-SC
on the higher handover count. The Co-SC
SC Targets report, and a neighbor list
Co-SC problem will be displayed in the
Potential Co-SC Targets report, but a script
will not be created for this sector.
IN_BUILDING_LOCK_NL_INACTIVE Defines whether in-building inactive sectors

should be locked for neighbor-list optimization.
Default = No
MAXIMAL_NEIGHBOR_RANGE_INACTIVE Defines the maximum distance within which

(Meters/Feet) inactive sectors can be selected for the
neighbor list. Any neighbors that are located
Default = 10,000/32,810
further than this range are deleted from the
neighbor list, unless they have been locked for
optimization.
MAXIMUM_TOTAL_NUMBER_OF_ Defines the maximum allowed number of

NEIGHBORS_INACTIVE inactive neighbors (Intra-frequency, Inter-
frequency, and IRAT) for the neighbor list
Default = 127
optimization.
MIN_DISTANCE_REMOVE_EXISTING_ Defines the distance below which inactive

HANDOVERS_INACTIVE neighbors should not be deleted.
Default = 0
MIN_NBR_GEO_OPT Defines the minimum required number of

existing neighbors for an inactive sector to be
Default = 5
locked for geometrical optimization.
218
MIN_NBR_GEO_OPT_ID Defines the minimum required number of

existing neighbors for an indoor inactive sector
Default = 5
to be locked for geometrical optimization.
UMTS_MAX_NEIGHBORS_INACTIVE Defines the maximum number of neighbors

Default = 26
limit.
UMTS_MAX_NEIGHBORS_INACTIVE_ Defines the maximum number of Huawei

HUAWEI neighbors allowed in the optimized neighbor
list. This parameter should never exceed the
Default = 26
hardware limit.
Neighbor List Optimization Parameters for Indoor Sectors

MAXIMAL_NEIGHBOR_RANGE_INDOOR Defines the maximum distance within which

(Meters/Feet) sectors can be selected for the neighbor list.
Default = 10,000/32,810
MAX_HO_DELETE_RATE_FROM_KPIS_ Defines the threshold below which to delete

INDOOR (%) handovers, even if the HO rate from the call-
trace data is high.
Default = 0.2
MINIMAL_NEIGHBOR_RATE_DELETION_ Defines the minimal handover rate from source

INDOOR (%) to target, for a sector to be in the neighbor list.
Default = 0.5
MINIMAL_NEIGHBOR_RATE_INDOOR (%) Defines the minimal handover rate from source

Default = 2.0
219
MIN_HO_ADD_RATE_FROM_KPIS_INDOOR Defines the threshold above which HOs will be

(%) considered, even if the rate from the call-trace
data is low.
Default = 4.0
MIN_HO_COUNT_DELETION_INDOOR Defines the handover from source to target

threshold, below which sectors will be removed
Default = 6
from neighbor list.
MIN_HO_COUNT_INDOOR Defines the minimum number of handovers

Default = 40
neighbor list.
RECIPROCITY_LEVEL_INDOOR Defines the level of reciprocity (symmetry)

Default = Required
neighbor lists.
based on the UMTS_MAX_NEIGHBORS
SET parameter.
will be deleted.
UMTS_MAX_NEIGHBORS parameter,
Note: If the target sector's neighbor list is
full, but the handover rate to this sector is
above a predefined threshold, reciprocity
will be relaxed and the handover will be
added without forcing reciprocity.
220
USE_HYSTERESIS_FOR_EXISTING_NBRS_ Defines whether to activate hysteresis

INDOOR thresholds in the neighbor list optimization.
Default = Yes
Neighbor List Parameters for LTE Sectors

INDOOR_LTE_MAX_HO_COUNT_DELETION Defines the maximum handover count from

source to target for sectors to be removed from
Default = 20
the neighbor list. Above this number of HOs,
sectors will not be removed.
INDOOR_LTE_MAX_HO_RATE_DELETION Defines the maximum handover rate from

(%) source to target, for a sector to be removed
from the neighbor list. The HO rate is
Default = 0.5
calculated according to the HO count between
a specific source and target as a percentage of
the total number of HO counts from the source
sector.
INDOOR_LTE_MAX_HO_RATE_DELETION_ Defines the indoor handover threshold below

FROM_KPS (%) which to delete neighbors, even if the HO rate
from the call-trace data is high.
Default = 0.1
INDOOR_LTE_MAX_NEIGHBOR_ Defines the maximum distance within which

RANGE (Meters/Feet) indoor sectors can be selected for the neighbor
list. Any neighbors that are located further than
Default = 5,000/16,405
this range are deleted from the neighbor list,
unless they have been locked for optimization.
INDOOR_LTE_MIN_HO_COUNT_ADDITION Defines the minimum number of indoor

handovers from source to target, for sectors to
Default = 40
be added to the neighbor list.
INDOOR_LTE_MIN_HO_RATE_ADDITION (%) Defines the minimal handover rate from source

to target, for a sector to be added to the
Default = 0.5
neighbor list. The HO rate is calculated
according to the HO count between a specific
source and target as a percentage of the total
number of HO counts from the source sector.
221
INDOOR_LTE_MIN_HO_RATE_ADDITION_ Defines the threshold above which HOs will be

FROM_KPIS (%) considered, even if the rate from the call-trace
data is low.
Default = 0.5
INDOOR_LTE_MIN_TOTAL_HO_COUNT Defines the minimum total handover counts for

Default = 200
If you define the
INDOOR_MIN_TOTAL_HO_COUNT below
200, the neighbor list will have a weak
statistical base. If there are not enough
messages available, you can make a special
optimization plan for the specific low-count
sectors using the
LTE_MINIMIZE_DELETIONS parameter and
the lock feature, which will prevent the old
neighbors from being deleted or having their
priority changed.
INDOOR_LTE_RECIPROCITY_CHANGES_IN_ Defines whether to add neighbors to indoor

CALC_SET sectors outside the selection set, or add and
Default = None
when the
INDOOR_LTE_RECIPROCITY_LEVEL
parameter is set to "Recommended".
222
INDOOR_LTE_RECIPROCITY_LEVEL Defines the level of reciprocity (symmetry)

between incoming and outgoing indoor
Default = None
neighbors.
neighbor lists.
based on the LTE_MAX_NEIGHBORS
INDOOR_LTE_RECIPROCITY_
CHANGES_IN_CALC_SET parameter.
will be deleted.
LTE_MAX_NEIGHBORS parameter, sector
B will be removed from sector A's neighbor
list to maintain reciprocity.
Note: If the target sector's neighbor list is
full, but the handover rate to this sector is
above a predefined threshold, reciprocity
will be relaxed and the handover will be
added without forcing reciprocity.
223
LTE_FIX_CO_PCI_PROBLEMS Defines whether to fix co-PCI problems by

adding the co-PCI neighbor with the higher
Default = Yes
handover count to the neighbor list. Co-PCI
the same PCI are identified for the same
source sector.
 Yes: Mentor will decide which co-PCI
on the higher handover count. The co-PCI
PCI Targets report, and a neighbor list
co-PCI problem will be displayed in the
Potential Co-PCI Targets report, but a
script will not be created for this sector.
LTE_LOCK_INDOORS Defines whether in-building sectors should be

Default = No
LTE_MAX_HO_COUNT_DELETION Defines the maximum handover count from

source to target for sectors to be deleted from
Default = 40
the neighbor list. Above this number of HOs,
sectors will not be removed.
LTE_MAX_HO_RATE_DELETION (%) Defines the maximum handover rate from

source to target, for a sector to be deleted from
Default = 0.25
the neighbor list. The HO rate is calculated
LTE_MAX_HO_RATE_DELETION_FROM_ Defines the threshold below which to delete

KPIS (%) handovers, even if the HO rate from the call-
trace data is high.
Default = 0.1
LTE_MAX_NEIGHBORS Defines the maximum number of neighbors

Default = 128
limit.
If you want to reduce the number of neighbors
to make a compact neighbor list, you should do
so using the MIN_HO_COUNT_ADDITION,
LTE_MIN_TOTAL_HO_COUNT, and
LTE_MAX_HO_RATE_DELETION
parameters.
224
LTE_MAX_NEIGHBOR_RANGE (Meters) Defines the maximum distance within which

sectors can be selected for the neighbor list.
Default = 25,000
LTE_MAX_TOTAL_NEIGHBORS Defines the maximum allowed number of

neighbors for the neighbor list optimization.
Default = 256
LTE_MINIMIZE_DELETIONS Defines whether neighbors that existed in the

Default = No
neighbor list.
LTE_MIN_HO_COUNT_ADDITION Defines the minimum number of handovers

from source to target, for sectors to be added
Default = 50
to the neighbor list.
LTE_MIN_HO_RATE_ADDITION (%) Defines the minimum HO rate for neighbors to

be added to the neighbor list.
Default = 1.0
LTE_MIN_HO_RATE_ADDITION_FROM_ Defines the threshold above which HOs will be

KPIS (%) considered for the neighbor list, even if the HO
rate from the call-trace data is low.
Default = 1.0
225
LTE_MIN_TOTAL_HO_COUNT Defines the minimum total handover counts for

Default = 500
If you define the
LTE_MIN_TOTAL_HO_COUNT below 500,
the neighbor list will have a weak statistical
base. If there are not enough messages
available, you can make a special optimization
plan for the specific low-count sectors using
the LTE_MINIMIZE_DELETIONS parameter
and the lock feature, which will prevent the old
neighbors from being deleted or having their
priority changed.
LTE_RECIPROCITY_CHANGES_IN_CALC_ Defines whether to add neighbors to sectors

SET outside the selection set, or add and delete
neighbors, in order to enable reciprocity when
Default = None
the LTE_RECIPROCITY_LEVEL parameter is
226
LTE_RECIPROCITY_LEVEL Defines the level of reciprocity (symmetry)

Default = None
neighbor lists.
based on the LTE_MAX_NEIGHBORS
LTE_RECIPROCITY_CHANGES_IN_CAL
C_SET parameter.
will be deleted.
LTE_MAX_NEIGHBORS parameter, sector
B will be removed from sector A's neighbor
list to maintain reciprocity.
Notes:
o This option is not recommended,
except in specific cases such as indoor
sites, as it imposes a strong limitation
on the neighbor list.
o If the target sector's neighbor list is full,
but the handover rate to this sector is
above a predefined threshold,
reciprocity will be relaxed and the
handover will be added without forcing
reciprocity.
LTE_SOFTER_HANDOVERS Defines whether to lock the softer handovers at

the top of the neighbor list, even if they do not
Default = Yes
have enough handovers.
227
NSN Provisioning Parameters

ADJGID-0_PREFERRED_BAND Defines which GSM sectors should get priority

0 if there are at least 2 co-site and co-azimuth
Default = LOWER
GSM cells.
 LOWER: Sectors belonging to the lower
band (850 or 900) should be created with
ADJGID-0.
 UPPER: Sectors belonging to the upper
band (1800 and 1900) be created with
ADJGID-0.
Note: If there are more than 1 GSM sectors
belonging to the same band, select which
sector should be used.
DEFAULT_ADJIECNOOFFSETNCHO_ Defines the CPICH EcNo offset for the non-

IDENTIFIER critical inter-frequency handover procedures.
Non-critical handovers are, for example,
Default = 0.0
service and UE capability-type handovers.
If the measured frequency includes a cell that
is blocked in the non-critical handover
procedure, the handover to the selected target
cell can be done if the blocked cell is not inside
the soft handover range of the target cell. (A
cell is not inside the soft handover range if the
measured EcNo of the best target cell
subtracted from the value of this parameter is
higher than the measured EcNo value of the
blocked cell.) The EcNo offset of the target cell
is used in the calculation.
This parameter is used by service and load-
based handovers.
DEFAULT_ADJSDERR_IDENTIFIER Defines whether the neighboring cell is

forbidden to affect the reporting range
Default = 0.0
(addition/drop window) calculation if it belongs
to the active set.
DEFAULT_ADJSECNOOFFSET_IDENTIFIER The CPICH Ec/No Offset determines an offset

value that the UE adds to the CPICH Ec/No
Default = 0.0
measurement result of the neighboring cell
before it compares the Ec/No value with the
reporting criteria.
DEFAULT_HSDPA_HOPS_IDENTIFIER Defines the parameter set (HOPS object) that

controls the intra-frequency handovers of a
Default = 7
user having HS-DSCH allocated.
228
DEFAULT_NRT_HOPS_IDENTIFIER Defines the parameter set (HOPS object) that

controls the intra-frequency handover of a non-
Default = 1
real time (NRT) radio bearer to the neighboring
cell.
DEFAULT_RT_HOPS_IDENTIFIER Defines the parameter set (HOPS object) that

controls the intra-frequency handover of a real
Default = 2
time (RT) radio bearer to the neighboring cell.
DEFAULT_RT_WITH_HSDPA_HOPS_ Defines the parameter set (HOPS object) that

IDENTIFIER controls the intra-frequency handovers of users
having HS-DSCH allocated simultaneously
Default = 1
with AMR speech CS RAB.
NSN_ADJG_TX_PWR_MAX_RACH_LOWER_ Defines the maximum transmission power level

BAND a UE can use when accessing a lower band
GSM neighbor cell on the RACH. The UE uses
Default = 33
the parameter in the cell re-selection
procedure. If the maximum output power of the
UE is lower than the value of the parameter,
the UE adds the power difference (dB value) to
the minimum required GSM RSSI level, which
the measurement result of the GSM neighbor
cell must exceed before the cell re-selection is
possible. The parameter value is set by the
system for the GAN neighbor cell.
Note: Any changes to this parameter must be
done before running the neighbor list
optimization.
NSN_ADJG_TX_PWR_MAX_RACH_UPPER_ Defines the maximum transmission power level

BAND a UE can use when accessing an upper band
GSM neighbor cell on the RACH. The UE uses
Default = 33
the parameter in the cell re-selection
procedure. If the maximum output power of the
UE is lower than the value of the parameter,
the UE adds the power difference (dB value) to
the minimum required GSM RSSI level, which
the measurement result of the GSM neighbor
cell must exceed before the cell re-selection is
possible. The parameter value is set by the
system for the GAN neighbor cell.
optimization.
229
NSN_ADJG_TX_PWR_MAX_TCH_LOWER_ Defines the maximum transmission power level

BAND that a UE may use on a TCH in a lower band
GSM neighbor cell. The RNC uses the
Default = 33
parameter in the decision algorithm of the
inter-RAT (GSM) handover. If the maximum
output power of the UE is lower than the value
of the parameter, the RNC adds the power
difference (dB value) to the minimum required
GSM RSSI level, which the measurement
result of the GSM neighbor cell must exceed
before the handover is possible. The
parameter value is set by the system for the
GAN neighbor cell.
optimization.
NSN_ADJG_TX_PWR_MAX_TCH_UPPER_ Defines the maximum transmission power level

BAND that a UE may use on a TCH in an upper band
GSM neighbor cell. The RNC uses the
Default = 33
parameter in the decision algorithm of the
inter-RAT (GSM) handover. If the maximum
output power of the UE is lower than the value
of the parameter, the RNC adds the power
difference (dB value) to the minimum required
GSM RSSI level, which the measurement
result of the GSM neighbor cell must exceed
before the handover is possible. The
parameter value is set by the system for the
GAN neighbor cell.
optimization.
NSN_APPLY_ADJGID-0_TO_CO-SITE_ Defines whether a GSM neighbor with the

CO_AZIMUTH same azimuth, based on the
MAX_SECTORS_GROUP_ANGLE parameter,
Default = Yes
should always get priority 0 even if there is
another GSM neighbor with a higher HO
ranking in the proposed neighbor list plan, or if
there is an existing GSM neighbor with
ADJGID-0 in the dump (in which case the ID
should be deleted and replaced with a different
ADJGID).
Note that the GSM sector is considered co-site
based on the GROUP_SITES_BY_DISTANCE
and MAX_SITES_GROUP_DISTANCE
parameters.
230
NSN_MAX_NUM_SIB1_INTER_NEIGHBORS Defines the maximum allowed number of inter-

frequency neighbors included in SIB1. Any
Default = 15
additional inter-frequency neighbors will be
included in SIB2.
NSN_MAX_NUM_SIB1_INTRA_NEIGHBORS Defines the maximum allowed number of intra-

frequency neighbors included in SIB1. Any
Default = 15
additional intra-frequency neighbors will be
included in SIB2.
NSN_MAX_NUM_SIB1_IRAT_NEIGHBORS Defines the maximum allowed number of IRAT

neighbors included in SIB1. Any additional
Default = 15
IRAT neighbors will be included in SIB2.
NSN_MAX_NUM_SIB1_TOTAL_NEIGHBORS Defines the maximum allowed number of

neighbors (inter-frequency, intra-frequency,
Default = 45
and IRAT) included in SIB1. All additional
neighbors will be included in SIB2.
NSN_NL_ENABLE_GROUPING Defines whether more than one neighbor-list

Default = No
neighbor list.
NSN_NL_GROUP_SIZE Defines the number of neighbor-list update

commands to be sent per batch.
Default = 5
NSN_NL_SPLIT_DELETE_ADD Defines whether there should be separate

batches for neighbors that are added, and
Default = No
those that are deleted.
NSN_NRT_HOPG_IDENTIFIER_LOWER_ Defines the parameter set (HOPG object) that

BAND controls the inter-RAT handover of a non-real
time (NRT) radio bearer to a lower band GSM
Default = 1
neighbor cell. The parameter value is set by
the system for the GAN neighbor cell.
optimization.
NSN_NRT_HOPG_IDENTIFIER_UPPER_ Defines the parameter set (HOPG object) that

BAND controls the inter-RAT handover of a non-real
time (NRT) radio bearer to an upper band
Default = 1
GSM neighbor cell. The parameter value is set
by the system for the GAN neighbor cell.
optimization.
231
NSN_RT_HOPG_IDENTIFIER_LOWER_BAND Defines the parameter set (HOPG object) that

controls the inter-RAT handover of a real time
Default = 1
(RT) radio bearer to a lower band GSM
optimization.
NSN_RT_HOPG_IDENTIFIER_UPPER_BAND Defines the parameter set (HOPG object) that

controls the inter-RAT handover of a real time
Default = 1
(RT) radio bearer to an upper band GSM
optimization.
NSN_UMTS_NL_ENABLE_ROLLBACK Defines whether the output of the neighbor-list

Default = Yes
plan.
NSN_UMTS_POWER_ENABLE_ROLLBACK Defines whether the output of the power

Default = Yes
NSN_UMTS_SC_ENABLE_ROLLBACK Defines whether the output of the SC

Default = Yes
Optimization Budget Parameters

MAX_CHANGED_SECTORS_PERCENTAGE Defines the maximum percentage of sectors

that can be optimized.
Default = 30
232
PCI Plan and Sector Identification Parameters

FORCE_SAME_PCI_PER_SECTOR Defines whether to use the same PCI for all

carriers in the same sector.
Default = Yes
Note: If Yes is selected, locking one cell will
lock all cells in the same sector.
MAX_CO_PCI_DISTANCE (Km/Miles) Defines the maximum allowed physical

distance between sectors with the same PCIs
Default = 50.0/31.07
to be considered and reported as co-PCIs.
MAX_NEIGHBOR_RANGE_LTE (Meters/Feet) Defines the maximum distance within which

LTE sectors can be selected for the neighbor
Default = 35000/114835
list. Any neighbors that are located further than
this range are deleted from the neighbor list,
unless they have been locked for optimization.
MIN_CO_PCI_DISTANCE (Km/Miles) Defines the threshold for sectors with co-PCIs

to be considered nearby sectors.
Default = 1.0/0.6214
MIN_HO_COUNT_LTE Defines the minimum number of handovers

from source to target, for LTE sectors to be in
Default = 100
the neighbor list.
MIN_HO_RATE_LTE (%) Defines the minimal handover rate from source

to target, for an LTE sector to be in the
Default = 0.04
neighbor list. The HO rate is calculated
MIN_TOTAL_HO_COUNT_LTE Defines the minimum total handover counts for

all possible LTE neighbors, per source sector.
Default =500
Any source sector with fewer handover counts
will not be optimized. These sectors will be
OMNI_PCI_POLICY Defines the way omni sectors are handled.

Default = Free  Free: Any PCI is allowed. This applies only
when the sector ID =0.
 Sector1: If the site is a pure omni cell with
only one sector, it will be handled as sector
1.
PCI_DISTANCE_WEIGHT Defines the weight of the distance in a distance

and angle-based formula.
Default = 2.0
233
ZERO_BASED_DIRECTIONS Defines whether the numbering for sector

identification in a site starts at 0, in which case
Default = No
the ID would include 0, 1, or 2. By default, the
numbering starts at 1—sector ID includes 1, 2,
or 3.
Positioning Parameters
MOBILE_TRACKING Defines whether the mobiles should be

tracked.
Default = No
MOBILE_TRACKING_ID_FILTER Defines the set of IMSIs whose calls are geo-

positioned and whose message positions are
written in the
MOBILE_TRACKING_OUTPUT_FILE
parameter. This should be a list (delimited by
space, tab, ";" or ",") or a filename containing
such a list. For example, 293872798478;
33987983247 91327448379.
MOBILE_TRACKING_OUTPUT_FILE Defines the name of the output file that

contains the positioning of messages in calls
for which the IMSIs are defined in the
MOBILE_TRACKING_ID_FILTER parameter.
STATIC_CALLS Defines whether to geo-position calls in a

single position.
Default = No
Power Optimization Parameters

MULTI_LEG_ORTH_FACTOR Defines the orthogonality factor for multiple

legs.
Default = 0.5F
SINGLE_LEG_ORTH_FACTOR Defines the orthogonality factor for single legs.

Default = 0.9F
234
RAB Optimization Parameters

DYNAMIC_RAB (dB) Defines the difference in power that should be

preserved between the Max and Min power.
Default = 15.0
Note: This limitation is relevant for Huawei
only.
HIGH_POWER_THRESHOLD (dB) Defines the threshold (below the current max

RAB power) above which a power reading
Default = 2.0
counts towards a change in the max RAB
power.
MAX_POWER_LIMIT_FACTOR Defines the multiplier of the percentage of

readings above
Default = 0.5
HIGH_POWER_THRESHOLD to determine
change in max RAB power.
MAX_POWER_LOWER_LIMIT_FOR_ Defines the maximum offset for Voice power,

VOICE (dB) relative to the CPICH power.
Default = –3.0
MAX_POWER_R99 (dB) Defines the maximum offset for the R99

power, relative to the CPICH power.
Default = 8.0
MAX_POWER_UPPER_LIMIT_FOR_ Defines the maximum offset for Voice power,

VOICE (dB) relative to the CPICH power.
Default = 3.0
MINIMUM_POWER_THRESH (dBm) Defines the minimum allowed power.

Default = 11.0
MINIMUM_RL_DISCARD (%) Defines the extent of the lower end

percentage of RAB power samples to discard
Default = 10.0
for calculating the correct MinPwrRl value.
MIN_DL_CODE_POWER_MEASUREMENT Defines the threshold below which sectors

should be locked for RAB optimization.
Default = 2,000.0
RAB_POWER_SIGMA Defines the number of standard deviations to

open the range of RAB power settings.
Default = 2.0
SPEECH_REQUIRED_EBNO (dB) Defines the required Eb/No for speech

service.
Default = 5.0
235
Reports Parameters
LOW_COVERAGE_THRESHOLD (dBm) Defines the RSCP threshold below which the

frame will be regarded as having low
Default = –100
coverage.
LOW_QUALITY_THRESHOLD (dB) Defines the Ec/Io threshold below which the

frame will be regarded as having low quality.
Default = –10
LTE_OVERLAPPING_LEGS_THRESHOLD Defines the number of candidates required for

overlapping samples. This data is required for
Default = 3
the Overlapping map.
LTE_OVERLAPPING_RSRP_THRESHOLD Defines the minimum power of the serving cell

(dBm) in order to be considered an overlapping
sample. This data is required for the
Default = -110
Overlapping map.
PILOT_POLLUTION_AS_THRESHOLD Defines the minimum number of sectors that

must be in the active set in order for the frame
Default = 3
to be regarded as having pilot pollution.
Note: The ECNO of the strongest pilot must
also be weaker than the threshold determined
by the
PILOT_POLLUTION_ECNO_THRESHOLD
parameter.
PILOT_POLLUTION_ECNO_THRESHOLD Defines the ECNO threshold of the strongest

(dB) pilot in order for pilot pollution to be
considered.
Default = –10.0
Note: The minimum number of sectors in the
active set must also be according to the
threshold determined by the
PILOT_POLLUTION_AS_THRESHOLD
parameter.
Roaming Parameters
OPERATOR_MCC_MNC_PAIRS Defines the Mobile Country Code and Mobile

Network Code pairs assigned to the operator.
For example, 310:200, 310:210. Subscribers
not represented by these pairs will be
identified as roaming subscribers.
236
SC Plan and Sector Identification Parameters

DISTANCE_WEIGHT Defines the weight of the distance in a

distance and angle-based formula.
Default = 2.0
FORCE_SAME_SC_PER_SECTOR Defines whether to use the same SC for all

carriers in the same sector.
Default = Yes
Note: If Yes is selected, locking one cell will
lock all cells in the same sector.
MAX_CO_SC_DISTANCE (Km/Miles) Defines the maximum allowed physical

distance between sectors with the same SCs
Default = 50.0/31.07
to be considered and reported as co-SCs.
MIN_CO_SC_DISTANCE (Km/Miles) Defines the threshold for sectors with co-SCs

to be considered nearby sectors.
Default = 1.0/0.6214
OMNI_SC_POLICY Defines the way omni sectors are handled.

Default = FREE  Free: Any SC is allowed. This applies only
when the sector ID = 0.
 Sector1: If the site is a pure omni cell with
only one sector, it will be handled as sector
1.
SECTOR_WISE_SC_DELTA Defines the difference in the scrambling codes

between sectors 1, 2, and 3 for the sector-wise
Default = 168
methods.
For example, if the SC of sector 1 is 3, then
the SC of sector 2 will be 3+168 meaning 171,
and the SC of sector 3 will be 171+168,
meaning 339.
SITE_WISE_SC_STEP Defines the difference between the scrambling

codes that are allocated sequentially, per site.
Default = 8
For example, if the step is 8, the sectors in the
first site will have SCs 1, 9, and 17, and in the
second site the sectors will have SCs of 25,
33, and 41, and so on.
237
USE_LOGS_BASED Defines whether to use an algorithm that

includes calculations from call traces as well
Default = Yes
as from the switch dump.
 Yes: Data from both the call traces and the
switch dump is used.
 No: Only switch dump data is used.
ZERO_BASED_DIRECTIONS Defines whether the numbering for sector

identification in a site starts at 0, in which case
Default = No
the ID would include 0, 1, or 2.
By default, the numbering starts at 1—sector
ID includes 1, 2, or 3.
Time Zone Parameters

KPI_TIMEZONE_REF Defines whether the time zone used for the

KPIs is according to the vendor, the call-trace
Default = VENDORDEFAULT
data, or the network.
MODEL_TIMEZONE_ID Defines the default time zone for the server

containing the call-trace data used in the
Default = GMT
model.
UMTS GSM Measurement Plan Parameters

MAX_PERCENT_FOR_REMOVAL (%) Defines the maximum weight of an existing

neighbor in relation to all the other neighbors
Default = 1.0
of a source sector, below which it will be
considered for deletion in order to make room
for potential neighbors to be measured. (Also
see MIN_NBRS_TO_RECORD)
MAX_RADIUS (Meters/Feet) Defines the radius within which potential

neighbors will be measured.
Default = 25,000/82,025
MIN_DAYS_FOR_IRAT_REMOVAL Defines the minimum number of model days

required, per source sector, in order to remove
Default = 3
low-rate targets during the measurement plan.
238
MIN_NBRS_TO_RECORD Defines the minimum number of potential

neighbors to be recorded in a measurement
Default = 48
plan, for each source sector. If this minimum is
not reached, redundant existing neighbors of
the source sector (as determined by the
MAX_PERCENT_FOR_REMOVAL
parameter) should be deleted, to make room
in the neighbor list for potential neighbors.
MIN_PART_DAY_FOR_IRAT_REMOVAL (%) Defines the minimum percentage of hours in

the day required in order to consider the
Default = 75
removal of low-rated targets for that day.
UMTS Goals Parameters

CODE_USAGE_THRESHOLD_UMTS (%) Defines the default target value for the

Reduce Code Usage sub-goal.
Default = 35.0
ECIO_THRESHOLD_UMTS (dB) Defines the default target value for the

Improve Ec/Io sub-goal.
Default = –10.0
POWER_USAGE_THRESHOLD_UMTS (%) Defines the default target value for the

Reduce Power Usage sub-goal.
Default = 70.0
RSCP_THRESHOLD_UMTS (dBm) Defines the default target value for the

Improve RSCP sub-goal.
Default = –100.0
Virtual Drive Test Parameters

MAX_VIRTUAL_DRIVE_TEST_CALLS_TO_ Defines the maximum number of virtual drive

SHOW test calls to display on the map and in the
Event Viewer.
Default = 100
239
Defining ZTE Provisioning Parameters

ZTE_SC_ENABLE_ROLLBACK Defines whether the output of the SC

optimization will include a rollback script,
Default = Yes
ZTE_UMTS_NL_ENABLE_ROLLBACK Defines whether the output of the neighbor-list

Default = Yes
plan.
ZTE_UMTS_POWER_ENABLE_ROLLBACK Defines whether the output of the power-

Default = Yes
240
Site Properties
Displaying the Site Properties
You can view the properties of a selected UMTS, LTE, or GSM site and the sectors belonging
to the site, and edit certain properties, for example the name of the site, the RNC to which the
site belongs, and the longitude and latitude coordinates of the site.
To display the site properties

1. In the map, right-click a site, and then select Properties on the shortcut menu. The
Site Properties dialog box is displayed, according to the technology of the selected
site.
o UMTS
241
o LTE
242
o GSM
2. If required, you can enter a new name for the UMTS and LTE site and UMTS RNC,
or change the latitude and longitude coordinates.
3. If required, you can edit the properties of a selected sector belonging to the site. In
the Sectors area, select a sector, and then click Properties. The Sector Properties
dialog box is displayed, showing the properties of the selected sector.
o Edit the sector properties as required.
o Click OK to save your changes and close the Sector Properties dialog box.
4. Click OK to save your changes and close the Site Properties dialog box.
243
Sector Properties
You can view the properties of a single selected sector, or the properties that are common to
a selection. If required, you can also edit certain properties, as well as search for sectors,
display sectors of a certain technology on the map, and view the selected sectors in Google
Earth.
If you have a multi-technology network, you can view the properties of the UMTS, LTE, and
GSM sectors.
This chapter describes how to:
 Display UMTS Sector Properties
 Display LTE Sector Properties
 Display GSM Sector Properties
 Display Multi-selection Sector Properties
 Displaying Multi-Selection UMTS Sector Properties
 Display Multi-selection GSM Sector Properties
 Displaying Multi-Selection LTE Sector Properties
 Search for Sectors
 View Sectors in Google Earth
Displaying UMTS Sector Properties

The UMTS Sector Properties dialog box displays information relevant to a selected UMTS
sector. If required, you can edit any fields that are not read-only.
For your convenience, you can also view the basic sector properties in the Sector Property
Viewer pane.
To display sector properties

1. On the map, select the sector whose properties you want to view, and on View menu,
click Properties.
-OR-
Right-click the sector whose properties you want to view, and on the shortcut menu,
click Properties.
-OR-
Double-click the sector whose properties you want to view.
244
The Sector Properties <name of sector> dialog box is displayed, showing the
General tab.
The Sector Properties dialog box contains the following tabs:

o General, which enables you to view and edit general information about the
selected sector, for example its name and the site to which it belongs. You can
also set neighbor list constraints, and view the advanced sector properties, such
as power and cell parameters.
o Antenna, which enables you to view and edit antenna-related information relevant
to the selected sector.
o Neighbor List, which enables you to view and edit neighbor list properties. For
example, you can lock the priority of selected neighbors, or add neighbors.
o Constraints, which enables you to select the parameters that should be
optimized, as well as set the minimum and maximum constraints for these
parameters.
o Keywords, which enables you to view the keywords associated to the selected
sector, and associate the selected sector with additional keywords.
2. Select the relevant tabs to view or edit the sector properties.
3. Click OK to save your changes and close the Sector Properties dialog box.
245
Displaying LTE Sector Properties

The Sector Properties dialog box displays information relevant to a selected LTE sector. If
required, you can edit any fields that are not read-only.
For your convenience, you can also view the basic LTE sector properties in the Sector
To display LTE sector properties

1. On the map, select the LTE sector whose properties you want to view, and on the
View menu, click Properties.
-OR-
Right-click the LTE sector whose properties you want to view, and on the shortcut
menu, click Properties.
-OR-
Double-click the LTE sector whose properties you want to view.
General tab.
The Sector Properties dialog box contains the following tabs:

o General, which enables you to view and edit general information about the
selected sector, for example its name and the site to which it belongs.
o Antenna, which enables you to view and edit antenna-related information relevant
to the selected sector.
o Neighbor List, which enables you to view the neighbor list properties of the
selected sector.
o Keywords, which enables you to view the keywords associated to the selected
sector, and associate the selected sector with additional keywords.
246
2. Select the relevant tabs to view or edit the sector properties.

3. Click OK to save your changes and close the Sector Properties dialog box.
Displaying GSM Sector Properties

You can view the properties of a selected GSM sector.
To display the GSM sector properties

1. On the map, select the GSM sector whose properties you want to view, and on View
-OR-
Right-click the GSM sector whose properties you want to view, and on the shortcut
-OR-
Double-click the GSM sector whose properties you want to view.
General tab.
The GSM Sector Properties dialog box contains the following tabs:
o General, which enables you to view general sector information, for example, the
name of the site and of the BSC.
o GSM, which enables you to view GSM-related sector information, for example, the
allocation priority, and whether half rate is enabled.
o Frequencies, which enables you to view information related to the sector’s
subcells.
247
o Subcells, which enables you to view serving threshold and transmission power
information.
o Handovers, which enables you to view a list of sectors to and from which there
were handovers.
o KPIs, which enables you to view KPI information for the sector.
o Keywords, which enables you to view the keywords associated to the sector, as
well as define new associations and keywords.
2. Select the relevant tabs to view the sector properties.
3. Click OK to close the Sector Properties dialog box.
Displaying Multi-selection Sector Properties


248
sectors area.
dialog box.
dialog box.
Displaying Multi-Selection UMTS Sector Properties

You can display the sector properties of multiple sectors at the same time, and edit them, if
required. You can also display the properties of a specific sector in the selection. If you have
a multi-technology network, you can also view the properties of multiple LTE or GSM sectors.
To display multiple-sector properties

1. On the map, select the sectors whose properties you want to view. If you have a
multi-technology network, in the Layers pane, under Sectors, select UMTS to
display only the UMTS sectors in the network.
2. Right-click the selection, and from the shortcut menu, click Properties.
249
The Sector Properties (Multi-selection) dialog box is displayed, showing the

properties that are common to all the selected sectors. If there is a value that is
common to all the selected sectors, this value is displayed. If not, the fields are left
blank.
The Sector Properties (Multi-selection) dialog box contains the following tabs:
o General, which enables you to specify whether the selected sectors are active,
and select the configurations to which the selected sectors belong. It also enables
you to lock the neighbor list.
o Constraints, which enables you to set constraints for the selected sectors, as
well as lock the neighbor list.
o Keywords, which enables you to view keywords associated with the selected
sectors, and associate new keywords.
3. Edit the fields as required. The edited values will apply to all the sectors in the
selection.
dialog box.
250
To view the properties of a specific sector

 Right-click the sector whose properties you want to view, and from the shortcut menu,
click Sector Properties. The Sector Properties dialog box is displayed, showing the
properties of the selected sector.


sectors area.
251
dialog box.
dialog box.
Displaying Multi-Selection LTE Sector Properties

You can display the keyword properties of multiple LTE sectors at the same time, and
associate new ones, if required. You can also display the properties of a specific sector in the
selection. If you have a multi-technology network, you can also view the properties of multiple
UMTS or GSM sectors.

1. On the map, select the LTE sectors whose properties you want to view. If you have a
multi-technology network, in the Layers pane, under Sectors, select LTE to display
only the LTE sectors in the network.
2. Right-click the selection, and from the shortcut menu, click Properties.
252
The Sector Properties (Multi-selection) dialog box is displayed, showing the

keywords that are common to all the selected sectors.
The following table describes the fields and buttons in the Keywords tab:
Field Description
Select Keyword Select the keyword to associate with the selected sectors
from the drop-down list of existing keywords.
Add Click this button to add the selected keyword to the list of
keywords associated with the selected sectors.
New Click this button to define new keywords to add to the list of
existing keywords.
Keywords associated The list of keywords associated with the selected sectors.
with sectors
Remove Click this button to remove a selected keyword from the list
of associated keywords.
If a keyword is common to all the selected sectors, it is displayed. If not, the fields are
left blank.
253
3. Edit the keywords as required. The edited values will apply to all the sectors in the
selection.
dialog box.

 Right-click the sector whose properties you want to view, and from the shortcut menu,
Displaying Multi-selection GSM Sector Properties

If you have a multi-technology network that includes GSM, you can view the sector properties
of multiple GSM sectors at the same time. You can also display the properties of a specific
GSM sector in the selection.

1. In the Layers pane, under Sectors, select GSM. Only the GSM sectors in the
network are displayed.
2. Select the sectors whose properties you want to view.
3. Right-click the selection and then click Properties. The Sector Properties (Multi-
Select) dialog box is displayed, showing the properties that are common to all the
selected sectors. If there is a value that is common to all the selected sectors, this
value is displayed. If not, the fields are left blank.
254
The Sector Properties (Multi-Select) dialog box contains the following tabs:
o General, which enables you to view general sector information for the selected
sectors.
o GSM, which enables you to view GSM-related sector information for the selected
sectors.
o Keywords, which enables you to view keywords associated with the selected
sectors, and associate new keywords.
4. Edit the fields as required. The edited values will apply to all the sectors in the
selection.
5. Click OK to save your changes and close the Sector Properties (Multi-Select) dialog
box.

 Right-click the sector whose properties you want to view, and on the shortcut menu,
Displaying Multi-Selection GSM Keyword Properties

In the Keywords tab, you can view all the keywords associated with the selected GSM
sectors. If required, you can associate additional keywords to the sector or define new
keywords, as well as remove associated keywords.
255
The following table describes the fields and buttons in the Keywords tab:
Field Description
Select Keyword Select the keyword to associate with the selected sectors
from the drop-down list of existing keywords.
Add Click this button to add the selected keyword to the list of
keywords associated with the selected sectors.
New Click this button to define new keywords to add to the list of
existing keywords.
Keywords associated The list of keywords associated with the selected sectors.
with sectors
Remove Click this button to remove a selected keyword from the list
of associated keywords.


256
sectors area.
dialog box.
257
dialog box.
Searching for Sectors

You can search for any available sectors in the current network, according to the sector name
or part thereof, or according to the cell identification. Mentor lists the number of sectors that
match your search criteria, and enables you to navigate through the list of matching sectors.
By default, Mentor zooms in on each found sector.
Note: Only sectors currently displayed on the map will be taken into consideration.
To search for a specific sector

1. On the Edit menu, click Find.
-OR-
On the Standard toolbar, click the Find button .
The Find dialog box is displayed.
2. In the Sector name field, enter the name or part thereof, of the sector for which you
are searching. For example, searching for ora will return multiple results, including
Orange/1, Orange/2, Orange/3, Coral/1, Coral/2 and Coral/3.
3. Select the Exact match check box if you know the exact name of the sector, for
example, Orange/3.
4. Clear the Zoom check box to prevent Mentor from zooming in on found sectors.
5. Click Next. The number of sectors that match your search criteria is displayed in the
title of the dialog box, and the first sector is flagged.
258
6. Click Next until you find the sector for which you are searching.
7. Click Close to close the Find dialog box.
Viewing Sectors in Google Earth

You can view a sector or selection of sectors, and their azimuth, on a topographical map in
the Google Earth application. To do so, Google Earth must be installed on the PC on which
Mentor is installed. Access the Google Earth website to download the application, if it is not
already installed.
The sites of the selected sectors are automatically loaded to the Temporary Places folder in
the Places pane in Google Earth. The name of the Mentor network is displayed under this
folder in the Places pane.
If required, define the way the sectors should be displayed in the Google Earth Display
parameters.
To display a sector in Google Earth

 Right-click a sector and on the shortcut menu, click Show in Google Earth. The
Google Earth application opens, displaying the selected sector on the map, with the
corresponding site name on the map and in the Places pane, on the left.
To display a group of sectors in Google Earth:

1. Select the sectors you want to view.
2. Right-click the sectors and select Show in Google Earth.
-OR-
On the Tools menu, click Show in Google Earth.
259
The Google Earth application opens, displaying the selected sectors on the map, with
the corresponding site names on the map and in the Places pane on the left. You can
click on any of the site names to zoom in to the sector.
260
Working with Planned Sites and Sectors

Mentor enables you to add new planned UMTS sites and sectors to the map area, which
allows you to visualize their affect by including them in analyses and optimizations.
You can import a network including a predefined file containing planned sites, or you can add
planned sites to the existing network by importing a file containing the details of all planned
sites. You can also manually add the sites and sectors to the map area. Once these sites and
sectors have been added to the network, you can optimize the planned neighbor list.
Note: Planned sites and sectors are currently supported for UMTS networks only.
 Importing Planned Sites
 Adding a New Site on the Map Area
 Adding Planned Sectors
 Exporting Planned Sites
 Deleting Planned Sites or Sectors
For more information on planned sites and sectors, refer to the Ultima Mentor Help.
Importing Planned Sites

You can import planned UMTS sites from a file containing all the site details. After you have
imported the sites, you can complete any missing data.
To launch the Import Planned Sites wizard

 On the File menu, click Import and then Planned Sites. The first step of the Import
Planned Sites wizard is displayed, enabling you to browse to the file to be imported.
The Import Planned Sites wizard contains the following steps:
 Step 1 General, enables you to browse to the file containing the sites to be imported.
configuration changes directly in the GUI.
261
Defining General Site Properties

You can import the planned sites from a file containing details of all the planned sites.
To define the general properties

1. In the Planned Sites File field, select or browse to the file containing the details of all
the planned sites.
2. Click Next to proceed to the Data Completion page.
Completing the Planned Site Data

After you have entered the path of the file containing the planned site data, and there are no
errors or sectors with missing data, you can import the sites.
If sectors are missing mandatory data, they will be displayed in red with in the Excluded
sectors pane, in the Data Completion page. You can select to import the rest of the sectors,
or you can complete the data directly in the GUI so that these sectors will also be imported.
If there are any sectors that are missing antenna profile data, they will be displayed as
warnings in the right pane. These sectors will be included in the import process with an
automatically assigned default profile, unless you enter the correct data.
262
To complete the import process if there is no missing data

1. In the Data Completion page, if required click Details to view any warnings that may
have been generated during the import process.
the data is validated and reports are created, and then the Import Planned Sites
Completed dialog box is displayed.
263
3. Click Details to view details of the import process, including any data
inconsistencies displayed in the Data Completion page. These messages can also
be viewed in the Import Messages tab.
co-SC conflicts between neighbors.
5. Click Reports to view detailed reports of the import process.

6. Click Close to close the Import Planned Sites Completed dialog box.
264
To complete the site data

1. In the Data Completion page, sectors that appear in the switch but will not be
imported as they have missing data are displayed in red and with in the Excluded
sectors pane on the left. The number of sectors with missing data is displayed at the
top of the pane. If there are any sectors that are missing antenna profile data, they
are displayed as warnings in the right pane. These sectors will be included in the
import process with an automatically assigned default profile, unless you enter the
correct data.
If required, in the left pane, select the sectors you would like to include in the import
process and click the right arrow button , or right-click the sectors and then click
Move. The selected sectors move to the Excluded sectors to be edited and
imported pane. The number of sectors with missing data to be completed and then
imported is displayed at the top of the pane.
265
enter the missing information or edit the antenna details. Tabs with missing
information are displayed in red, with an asterisk. Fields with missing information are
highlighted in red.
4. Repeat steps 2 to 3 for each sector you want to include in the import process.
266
the data is validated and the reports are created, and then the Import Planned Sites
including warnings notifying about sectors using default antenna profiles.
267
7. Click Layers to view layers showing any sectors that have co-SC conflicts between
neighbors.
8. Click Reports to view detailed reports of the import process.

9. Click Close to close the Import Planned Sites Completed dialog box, and to display
the main window, showing the imported network.
Launching the New Site Wizard

You can manually add new planned UMTS sites directly on the Mentor map. After you have
added the new site, you must add at least one planned sector.
To launch the New Site wizard

1. On the Network menu, click Planned Sites and then New Site. The cursor changes
to .
268
2. Click on the location on the map to which to add the site. Step 1 of the New Site
wizard is displayed.
The New Site wizard contains two steps:

 Step 1 General, enables you to define general properties for the site, for example, its
name and the RNC to which it should belong.
 Step 2 Sectors, enables you to define the sectors that belong to the site.
Defining the General Site Properties

You can define the location of the new site by clicking on the required location on the map
area, and then editing the property fields, if required.
To add a planned site directly in the Mentor map area

1. On the Network menu, click Planned Sites and then New Site. The cursor changes
to .
269
2. Click on the location to which to add the site. Step 1 of the New Site wizard is
displayed.
3. If required, enter a new name for the site.

4. Select the RNC to which the site belongs from the RNC name list.
5. If required, change the latitude and longitude coordinates.
6. Click Next to proceed to the Sectors page.
270
Defining Sectors
After you have defined a new site, you must add at least one sector, and define its properties.
To define sectors for the new planned site

1. In the Sectors page, in the Carrier field, select the carrier to which to add the sector.
2. In the Cell ID, Scrambling code, and Azimuth fields, enter the details for the new
sector, and then click Add. The new sector is displayed in the sector area.
3. Repeat this procedure for each sector carrier you want to add.
271
4. If required, click Properties to display the Properties dialog box, which enables you
to add additional properties, for example constraints, keywords, and so on.
5. Click Finish. The selected site and its sectors are displayed on the map.
272
Adding Planned Sectors to Existing Sites

You can add a new sector to an existing UMTS site, or to a planned UMTS site while creating
the site, or anytime afterwards.
To add a planned sector

1. On the Network menu, click Planned Sites and then New Sector. The cursor
changes to .
Click the site to which to add the new sector.
-OR-
Right-click the required site and then click New Sector.
The relevant Sector Properties dialog box is displayed, with the required missing
fields displayed in red.
2. Enter the Cell ID, SC, and azimuth for the new sector.
3. If required, edit any other fields. For example, the new sector will use the default
antenna profile, but you can change this in the Antenna tab.
273
4. Click OK. The new sector is added to the site.
Exporting Planned Sites

You can export the planned UMTS sites to a file so that, for example, they can be backed up.
To export the planned sites

1. On the File menu, click Export and then Planned Sites. The Export Planned Sites
2. Browse to the location to which to export the file, and enter a name for the file.
274
3. Click Save. The sites are exported to the selected location, and the Export
Completed dialog box is displayed, notifying whether the sites were exported
successfully.
Deleting Planned Sectors

You can delete one or more planned sectors at any time.
Note: If you delete the only sector in a planned site, the site is deleted as well.
To delete a planned sector

1. Select and right-click the planned sectors you want to delete and then click Delete. A
confirmation message is displayed.
2. Click Yes. The selected sectors are deleted.
275
Antenna Properties
The Antenna Properties dialog box displays information relevant to a selected antenna. If
required, you can edit any fields that are not read-only.
To display the antenna properties

1. On the map, right-click an antenna, and on the shortcut menu, click Properties. The
Antenna Properties - <name of antenna> dialog box is displayed, showing the
General tab.
The Antenna Properties dialog box contains the following tabs:

o General, which enables you to view and edit information about the antenna and
installation parameters.
o Antenna Constraints, which enables you to select whether to optimize the
mechanical or electrical tilt of the selected antenna, as well as the constraints for
these changes.
2. Select the relevant tabs to view or edit the antenna properties.
3. Click OK to save your changes and close the Antenna Properties dialog box.
276
Threshold-Crossing Alarms (TCA)

If your license supports threshold-crossing alarms, you can focus on problematic cells in the
network by displaying a report and layers that show sectors with KPI values that have violated
predefined rules.
These rules are created by the system administrator via the web interface of TEOCO
TrafficGuard and saved in the Helix FM database. The Mentor server generates KPI data in
hourly resolution. TrafficGuard analyzes the KPI data and based on the user-defined rules,
creates alarms that are saved for a predefined retention period.
Note: Threshold-crossing alarms are currently supported for UMTS only, for Ericsson,
Huawei, and NSN networks.
Defining Threshold-Crossing Alarm Maps

You can define a map to show all sectors that have KPI values that cross predefined
thresholds. In addition, you can generate a report that displays the sectors and sites for which
alarms were raised, as well as details about the alarm. The selected alarm layers can also be
displayed in the Detailed Table.
To define a threshold-crossing alarm map and report
1. On the toolbar, click .
If you are not already connected to the Mentor server, you will be prompted to do so.
277
The Threshold-Crossing Alarm Map dialog box is displayed.
2. In the All Rules pane on the left, select the rules for which to display alarms, and
then click . The selected rules are moved to the Selected Rules pane on the
right. A description of the selected rules is displayed in the Selected Rule
Description area.
278
3. By default, all days for which there is data in the call database are displayed in the
Date and Time area, but you can filter the dates and the time range for which to
display the raised alarms by clicking the browse button to display the Date and
Time Range dialog box.
o In the Date Range area, select the dates to include. Dates for which there is data
in the call database are displayed in bold.
If you select a sub-set of the available days, the word Filtered is displayed in the
Date and time field.
o In the Time Range area, select one of the following options, depending on the
feature and the data source used:
 24 Hours: All hours in the selected days will be used.
 Busy Hours: The busy hour of the selected days will be used.
 Hours (from/to): Select the start and end times. The selected time range will
be used for the selected days.
o Click OK.
4. Select the Create a report from selected rules check box to create an alarm report.
279
5. In the Folder name field, enter a name for the folder in which to save the alarm
layers in the Layers pane. If you do not enter a name, the default name will be used.
6. Click OK. A progress bar is displayed while the selected layers and report are
created. In addition, two layers are created by default—the Alarm Count layer, which
shows the number of alarms generated for each sector, and the Alarm Summary
layer, which shows the highest severity of all alarms generated for each sector.
If you selected to create a report, the Reports dialog box is displayed.
280
Viewing Alarm Reports

The Alarm report includes the sectors and sites for which alarms were raised, as well as
details about the alarm.
To view the Alarm report

 In the Reports dialog box that is displayed after generating the threshold-crossing
report and alarms, double-click Alarm Report or select the report and then click
Open.
The Alarm report is displayed, showing the following tabs:

o Alarms, which displays details of the alarms, including the sites and sectors for
which the alarms were generated.
o Details, which shows the name of the network, the time and date the report was
generated, as well as the version and build of the Mentor application.
For a detailed description of the tabs and fields in the reports, refer to the Ultima Mentor Help.
281
Analyzing the Network

Before making any changes to the network, you should analyze the main KPIs to identify
service degradations and traffic hot spots within the network. For example, you can identify
overloaded sectors, low handover rates, high drop rates or low throughput, areas with pilot
pollution, and so on. You can also check for alarms to ensure that the problem is not
hardware-related. Once you have identified the problematic areas, you will be able to define
specific optimization goals for each cluster.
After you have run the analysis calculation, you can analyze the network by viewing the
analysis reports, as well as the analysis layers on the map and the analysis statistics in the
Statistics Viewer pane. You can also analyze multiple networks, after optimization, to
compare pre- and post-optimized networks to see the extent of the network changes. If
required you can make changes to an existing analysis run by duplicating the analysis and
then editing it as required.
If you are connected to the Mentor server, you can schedule analyses to be run automatically
at a specific time.
 Analysis Wizard
 Duplicating Existing Analysis Calculations
 Positioning-based Maps
 Sector and Area Selection Statistics
Launching the Analysis Wizard

After you have imported the model, or if you are connected to the call database via the
Mentor server, you can launch the Analysis wizard. The Analysis wizard guides you through
the process of analyzing the network performance based on selected maps, statistics, and/or
KPIs. If required, you can also present specific combined maps only in areas where other
maps or KPIs cross specific values.
By default, the analysis is carried out on the selection set used in the model or for which there
is data in the call database, but you can change this by selecting a sub-set of the original
selection set, or selecting an area.
Notes:
 Only sectors for which there is a model or data in the call database can be included in
the analysis.
 If you are connected to the Mentor server and the call database is available, binned
maps will be created using rich data if the selected time range is for 24 hours or for
time from/to.
 If you do not have a model, but are connected to the call database, only binned maps
can be included in the analysis.
282
To launch the Analysis wizard

1. If required, select the sectors or the area on which to run the analysis. Note that the
sectors must be included in the model's selection set. If your selection includes
sectors for which there is no model, you will be able to continue with the analysis only
for the sectors for which there is a model.
2. On the Calculation menu, click New > Analysis.
-OR-
On the Workflow toolbar, click the button.
3. If your selection contains both UMTS and LTE sectors, the Technology Selection
dialog box will be displayed, enabling you to select the required technology.
4. Click Yes if you are prompted to save the network.

The first step of the Analysis wizard is displayed, enabling you to define the general
properties of the analysis.
The Analysis wizard contains three steps:
 Step 1 General, enables you to define general properties for the analysis, for
example, the name of the analysis, and the template used.
 Step 2 Reports, enables you to select or define the analysis reports, layers, and
statistics to be generated.
 Step 3 Summary, enables you to view a summary of the data consistency check, and
enables you to go back and change any parameters that are causing the consistency
check to fail.
283
Defining General Analysis Properties

The General page of the Analysis wizard enables you to define general properties for the
network analysis, for example, the name of the analysis and the template to be used. It also
enables you to select the date and time that will be used for all maps, reports, and statistics
created for the analysis.
If you are connected to the Mentor server, the binned maps will automatically be calculated
using the rich data.
To define the General properties of the network analysis

1. In the Name field, enter a name for the new analysis.
2. In the Template field, select a predefined template, if required and available.
284
3. By default, all days for which there is a model or the latest day for which there is data
in the call database are displayed in the Date and time field, but you can filter the
dates and the time range that are used by clicking the browse button to display
the Date and Time Range dialog box. The selected date and time options will be
used for all maps and reports created for the analysis.
o In the Date Range area, select the dates to include. Dates for which there is a
model or for which there is data in the call database are displayed in bold.
o In the Time Range area, select one of the following options, depending on the
 24 Hours: All hours in the selected days will be used.
 Busy Hours: The busy hour of the selected days will be used.
 Hours (from/to): Select the start and end times. The selected time range will
be used for the selected days.
o Click OK.
4. Click Next to proceed to the Reports page, where you can select or define the
reports, layers, and statistics charts to be generated.
285
Defining Analysis Reports, Layers, and Statistics

After you have defined the time period for which to run the analysis, you can define the
reports, layers, and statistics that will be generated as a result of the analysis. By default, the
analysis reports are based on selected KPIs that show the network performance, for example
the CS drop rate, and traffic. The Reports page shows the reports that are generated by
default, and that can be removed. You can add additional reports and/or layers and statistics
charts, according to your specific analysis requirements. You can also edit any of the report
properties, save reports, or load previously defined reports.
Note: The Access Distance Histograms report is displayed for Ericsson networks only.
To define the analysis reports, layers, and statistics

1. Verify that the default reports and layers that are displayed at the top of the Reports
page are the reports and layers you want to run. You can select an item in the list,
and then view its details in the area below the list of reports and layers.
2. If required:
o Define new reports, layers, and statistics
New reports, layers, and statistics charts can also be defined manually at any time
via the Network menu or toolbar, or by right-clicking a sector or area selection and
then selecting the relevant map type.
o Load previously saved report templates
o Save edited reports to be used as a template for further analyses
o Duplicate selected reports
o Remove reports from the list of reports to be run
o Edit the report properties
286
3. Click Next to proceed to the Summary page, which shows a summary of the analysis,
including data inconsistency errors and warnings. A progress bar is displayed while
the data consistency is checked.
Defining New Analysis Reports, Layers, and Statistics

The default analysis reports are generated when you run the analysis. If required you can
remove these reports, or create additional analysis reports, layers, and statistics charts, each
based on the selected KPIs, abnormal release reports, carrier statistics, and
call trace–based histograms, or map layers. You can also create a threshold-based
Combined map made up of a combination of selected maps and KPIs.
After you have selected all the reports and layers to be generated and displayed, you can
duplicate a selected report or layer, or save your selection as a template.
Note: If a report cannot be generated, a message is displayed in the Details dialog box in the
Summary page.
To define a new analysis report, layer, or statistics histogram

1. On the toolbar in the Reports page, click the button relevant to the type of report or
layer you want to add.
New KPI Analysis Report/Layer: Enables you to generate

the report according to selected KPIs. KPI reports show the
aggregated data, with the time resolution ranging from 1 hour
up to all the dates included in the model.
New Map Analysis Layer: Enables you to create a call

trace–based map layer for specified thresholds and RAB
groups.
Note: This option is available only if your license supports
positioning-based maps, and your model contains positioning.
New Event Map Analysis Layer: Enables you to create a call

trace–based map for specified thresholds and RAB groups.
Note: This option is available only if your license supports
positioning-based maps, and your model contains positioning.
New Detailed Analysis Report: Enables you to generate a

report that shows the detailed data derived from the call-trace
data. For example, you can you can generate a detailed list of
drops or abnormal releases recorded on the network.
New Statistics Histogram: Enables you to generate statistics

charts for the selected area or sector selection.
New Computed Map: Enables you to carry out mathematical

operations on selected binned maps.
Note: This option is enabled only after you have selected a
map layer to analyze.
2. Edit the fields as required, for each map, layer, or statistics histogram you want to
create.
287
3. Click OK. The new report or layer is displayed in the Reports dialog box with the rest
of the reports to be generated.
Note: If a report cannot be generated, a message is displayed in the Details dialog
box, in the Summary page.
Defining New KPI Reports

The KPI report shows the aggregated data, based on selected KPIs, for a time resolution
ranging from 1 hour up to all the dates included in the model.
To define a new KPI report

1. On the toolbar in the Reports page, click the New KPI Analysis Report/Layer
button . The New KPI Analysis Report/Layer dialog box is displayed.
2. In the Name field, enter a new name for the report, if required. If you do not enter a
new name, the default name is used.
288
3. In the KPIs area, the available KPIs are displayed in the All KPIs pane on the left.
Note: The KPIs vary according to the network vendor.
o Ericsson UMTS KPIs
o Ericsson LTE KPIs
o Huawei UMTS KPIs
o Huawei LTE KPIs
o NSN UMTS KPIs
o ZTE UMTS KPIs
By default, the KPIs are sorted by group, but you can display them alphabetically, if
required.
o Click to display the KPIs alphabetically. Click the column headers to sort the
KPIs according to Name or Group.
o Click to display the KPIs according to groups.

4. Click the button next to the group of KPIs you want to use. The group is expanded
to show the available KPIs.
5. Select one or more KPIs using standard Windows functionality and then click to
move the selected KPIs to the Selected KPIs pane on the right.
Tip: Double-click required KPIs to move them to the Selected KPIs pane.
289
6. In the Network element field, select the aggregation level for the Detailed report
tabs from the drop-down list. By default, the report is displayed per sector.
7. In the Time field, select the resolution level (x-axis) of the report. The resolution level
also determines the level of detail that will be displayed in the Detailed tab of the
report.
For example:
o Hour will provide an hourly analysis of the selected KPIs, per hour.
o Day will provide the average daily analysis of the selected KPIs, per day.
o Week will provide the average daily analysis of the selected KPIs, per week.
o Model dates will provide the average daily analysis of the selected KPIs, for the
entire modeling period. This option is typically used in the following cases:
 Comparing the status of the networks, before and after optimization, in the
multi-network analysis mode. A single entry is displayed for each network
selected.
 Presenting an overall summary of the network statistics without using specific
days.
8. By default, layers and graphs are automatically generated for each new report, but
you can change this by clearing the relevant check box in the Graphics area.
9. Click OK. The report is listed in the Reports page with the rest of the reports to be
generated.
Defining New Map Layers

If your model contains positioning, you can create selected map layers. If you do not create
the map layers in the wizard during the network analysis, you can generate them manually
from the network menu at any time.
To define a new map layer

1. On the toolbar in the Reports page, click the New Map Analysis Layer button
, and then select the map to create:
o Performance: Enables you to display selected performance layers on your map,
and in the Google Earth application, based on the busy-hour call-trace data. For
example, you can display the areas with the most pilot pollution, or the
RSRP/RSRQ for the busy hour.
o Drop: Enables you to display the distribution of the drop calls, or more generally
any abnormal releases such as data session disconnection, on your map, and in
the Google Earth application.
o Traffic: Enables you to display the distribution of the busy-hour traffic on your
map, and in the Google Earth application.
o Server and Polluter: Enables you to display the coverage area of selected
sectors on the map when they served as the best, second best and up-to fifth best
servers, as well as the worst polluters.
o Arc: Enables you to display arc maps showing selected KPIs at either predefined
distance increments from selected sectors, or according to predefined
percentages.
o Combined: Enables you to display a selected map that has been filtered by one
or more maps with specific thresholds.
290
2. In the Name field, enter a new name for the map layer, if required. If you do not enter
a new name, the default name will be displayed.
3. In the Map type field, select the type of map to display. By default, the map will be
displayed as a binned map, but if required, you can select the Sector-level map
option to display the map aggregated to cell level.
4. Select the Map per sector check box to display a separate map layer for each sector
in the selection.
5. By default, the map is filtered to show all the available RABs, but you can filter the
RABs or select additional data filters from the Add New Filter drop-down list. After
you have selected a filter, it is displayed in the filter area.
Click Add New Filter to add a new filter.
6. Click OK. The map is listed in the Reports page with the rest of the reports, maps,
and statistics to be generated.
Defining New Event Map Layers

If your model contains positioning, you can create selected call trace–based layers. If you do
not create the map layers in the wizard during the network analysis, you can generate them
manually from the network menu at any time.
To define a new event map layer

1. On the toolbar in the Reports page, click the New Event Map Analysis Layer button
, and then select the map to create:
o Drop: Enables you to display a positioned visual indication of any abnormal
releases reported, per mobile handset, on the map and in Google Earth. If
required, you can also view the different session legs at the time of the release,
for each selected abnormal disconnection.
Note: Currently Mentor supports maps only for the first 50,000 abnormal releases
that pass the filter criteria.
o Access Failure: Enables you to display a positioned visual indication of the
access failures reported, per mobile handset, on the map and in Google Earth. If
required you can also view the different session legs at the time of the failure, for
each selected access failure.
Note: Currently Mentor supports maps for layers of up to 250,000 failures only.
o IRAT: Enables you to display a positioned visual indication of the IRAT handover
events, per mobile handset, on the map and in Google Earth. If required, you can
also view the different servers for each handover.
Note: Currently this feature is supported for Ericsson and Huawei networks only,
and limited to the first 100,000 events.
o CSFB: Enables you to display circuit-switch fallback events from an LTE network
to a UMTS network.
o Additional Maps: Enables you to display additional event maps based on the
information found in the raw CTR/GPEH data.
Note: The Additional Event maps require a special license.
The relevant dialog box is displayed. The following fields may be displayed, according
to the map selected.
2. In the Name field, enter a new name for the layer, if required.
291
4. Click OK. The map is listed in the Reports page with th e rest of the reports, maps,
and statistics to be generated.
Defining New Detailed Reports

The Detailed reports show the detailed data derived from the call-trace data (not KPI-based).
For example, you can generate a detailed list of drops or data failures recorded on the
network, or the various statistics for each of the carriers in the network before the
optimization.
To define a new Detailed report
1. In the Reports page, click the New Detailed Analysis Report button
and then selected whether to create a Mobile Event report or a Network Analysis
report. The relevant New Detailed Report dialog box is displayed.
Or
2. In the Name field, enter a new name for the report, if required. If you do not enter a
name, the default name will be used.
292
3. In the Report field, select the type of report to generate:

Mobile Event Reports:
o Access Failure: Displays the number of UMTS abnormal releases due to access
failure.
o IRAT Events: Displays the details of the IRAT (UMTS to GSM) handovers for
voice calls and reselection for data sessions in the UMTS network.
Note: This report is displayed for Ericsson and Huawei UMTS networks only.
o Mobile Drop: Displays a detailed report of the UMTS abnormal releases recorded
in the selection set, for all mobiles or filtered according to the mobiles' IMEIs or
IMSIs, the release reason, or RAB group. This report is defined by default.
Mobile Event Reports:

o APN Histograms: Displays the details of the APNs found in the network data.
Note: This report is displayed for Ericsson UMTS networks only.
o Access Distance Histograms: Displays the number of UMTS calls or data
sessions initiated at specified distances from the access sector.
o Carrier Statistics: Displays various statistics for each of the carriers in the
network.
o CQI Histograms: Displays histograms relating to CQI statistics, on a sector and
network level.
o Cell Footprint: Displays an indication of the cell coverage, range, and quality,
based on the number of appearances of a specific leg in the power records,
according to its SC or PCI.
o Data Performance: Displays data performance statistics for each UMTS sector,
based on user experience and network statistics.
o HSDPA Histograms: Displays various histograms relating to HSDPA and other
RBS-based UMTS statistics.
o Power Histograms: Displays the distribution of various UMTS power
measurements.
o Swapped Sectors: Displays all UMTS sectors that are suspected of having been
swapped with other sectors, as well as the co-located sectors they are suspected
of having been swapped with.
o Timing Advance Histograms: Displays histograms relating to the TA statistics.
4. Mobile Event Reports: By default, the report is filtered to show all the available
RABs, but you can filter the RABs or select additional data filters from the Add New
Filter drop-down list. After you have selected a filter, it is displayed in the filter area.
5. Click OK. The report is listed in the Reports page with the rest of the reports to be
generated.
Defining New Statistics Charts

During the network analysis you can create relevant RF and traffic statistics for the busy hour.
These statistics can also be generated at any time from the Network menu or the toolbar.
Note: The Statistics option is available only if your license supports positioning-based maps.
293
To define new statistics charts

1. On the toolbar in the Reports page, click the New Analysis Statistics button
, and then select the statistics charts to create:
o Mobile Drops
o Performance
o Servers and Polluters
The relevant dialog box is displayed.
2. In the Statistics name field, enter a new name for the layer, if required. If you do not
enter a new name, the default name will be used.
3. In the Statistics type field, select the type of statistics to display.
4. By default, the statistics are filtered to show all the available RABs, but you can filter
the RABs or select additional data filters from the Add New Filter drop-down list.
After you have selected a filter, it is displayed in the filter area.
5. Click OK. The selected statistics type is listed in the Reports page with the rest of the
reports, layers, and statistics charts to be generated.
Defining New Computed Maps

During the network analysis you can perform mathematical operations on binned maps, which
can be displayed on the map area and in Google Earth. For example, you can display the
difference in RSCP coverage between indoor and outdoor calls.
These computed maps can also be generated at any time from the Network menu or the
toolbar.
Note: The Computed Maps option is available only if your license supports positioning-
based maps.
To create a computed map

1. In the Reports page, select the binned maps on which to perform mathematical
operations.
294
2. On the toolbar in the Reports page, click the Computed Maps button . The New
Computed Map dialog box is displayed, showing the selected maps in the Maps
area.
3. Double-click a map in the Maps area to move it to the Expression area.

4. Type the required expression or use the supplied keypad for the required numbers
and operators.
5. To use a predefined function, click Functions. The Functions Browser window is
displayed.
o In the Functions Browser window, select a function and click OK.
o In the Expression area, replace the variables with actual values or map numbers.
6. Click Validate to check whether the expression is valid. A message appears either
indicating that the expression is valid, or with a list of errors.
7. Click OK, and correct the expression if required.
8. Click OK. The new computed map is listed in the Reports page with the rest of the
reports, layers, and statistics histograms to be generated.
295
Loading Saved Analysis Report Templates

In order to save time, you can load a previously saved analysis report template. After you
have loaded the report template, you can edit the reports, if required.
To load a previously saved report template

1. In the Reports page, click Load. A standard Windows Open dialog box is displayed.
2. Browse to the report template you want to load, and click Open. The reports in the
template are displayed in the list of reports to be generated, in the Reports page.
3. Edit the report properties, if required.
Saving Analysis Reports and Layers as a Template

You can save selected analysis reports and layers as a template, to be used for future
analyses. Once the file has been saved, it can be loaded at any time.
To save a report or layer as a template for use in future analyses

1. In the Reports page, select the reports or layers you want to save as a template, and
on the Reports toolbar click . A standard Windows Save dialog box is displayed,
enabling you to save the selected reports and layers as a .rep template file.
2. Browse to the location in which to save the file, enter a name for the file, and click
Save.
Note: If you do not enter a new name, the default name will be used. A file containing
a single report or layer will be named according to the layer or report, and a file that
contains multiple reports or layers will be named Report Multi Selection.
Duplicating Analysis Reports

You can duplicate existing analysis reports and then edit their values accordingly. Once you
have duplicated a report, you can save it for future analyses.
Note: The Carrier Statistics report cannot be duplicated.
296
To duplicate a report
1. In the Reports page, select the analysis report you want to duplicate, and on the
Reports toolbar, click the Duplicate button . The Duplicate dialog box is
displayed, showing the fields selected in the original report.
2. In the Name field, enter a new name for the report, if required.
3. Edit the fields as required.
4. Click OK to save the duplicated report.
297
Viewing the Analysis Summary

The Summary page enables you to view a summary of the analysis, including the data
consistency check, which shows the data inconsistency errors and warnings. You can go
back and change any parameters, if required. You can view the details of the inconsistencies,
and save these details for analyzing at a later stage. If there are any data inconsistency
warnings, you are required to approve them before running the analysis.
Note: If you are running the analysis on a sector selection, the number of sectors included in
the analysis is displayed in the Selection field. If you are running the analysis on an area
selection, Area Selection is displayed in the Selection field.
298
To view the data inconsistency error and warning details

1. If there are data inconsistencies, click the Details button.
The Overview dialog box is displayed, showing a list of errors and warnings.
Error: You must go back and correct the parameters set in the General, or Filter
pages before you can run the analysis.
Warning: You must approve the warnings before you can run the analysis.
o Click Save if you want to save the errors and warnings. A standard Windows
Save dialog box is displayed, enabling you to enter a name for the file, and to
browse to the location in which to save it. Click Save.
o Click Close to close the Details dialog box.
2. To save the analysis template for future use, click Save. A standard Save dialog box
is displayed.
o Browse to the location in which to save the template.
o Enter a name for the template in the File name field.
o Click Save. The template is saved and can be used as a template in further
analyses.
3. Click Finish to run the analysis. The status of the analysis is displayed at the top of
the Calculations pane.
299
4. As soon as the analysis run has completed, its status changes to Valid, and the
Analysis Completed dialog box is displayed.
o Click Details to view details of the error and warning messages. Note that the
Details button is enabled only if there are errors or warnings found in the analysis.
o Click Layers to view the layers created during the analysis, and load selected
layers. The selected layers are displayed in the Layers pane, and can be
selected and viewed on the map.
o Click Reports to view a list of analysis reports that can be displayed. For a
detailed description of the analysis reports, refer to the Ultima Mentor Help.
o Click Statistics to view a list of analysis statistics that can be displayed.
5. Click Close to close the Analysis Completed dialog box.
Duplicating Existing Analysis Calculations

For your convenience, you can duplicate an existing analysis calculation, and then edit it as
required.
To duplicate an analysis calculation

1. In the Calculations pane, right-click the analysis calculation you want to copy, and
on the shortcut menu, click Duplicate and Edit. The first step of the Analysis wizard
is displayed, showing the data from the original calculation.
2. Edit the fields in the wizard pages as required, and then click Finish. The status of
the analysis is displayed at the top of the Calculations pane.
Analysis Reports
The Analysis reports show the status of the network. You can view the default reports, which
are generated with a graph for each KPI, and a layer that can be displayed on the map, or
you can view the reports that you defined.
If you performed a multi-network analysis, the reports will show separate fields for each
network, enabling you to compare the networks.
If required, you can save selected reports.
300
To view the analysis reports

1. In the Calculations pane, right-click the analysis whose reports you want to view,
and then click Open Reports on the shortcut menu.
-OR-
In the Calculations pane, select the analysis whose reports you want to view, and
then on the Calculation menu, click Open Reports.
The <name of analysis> Reports dialog box is displayed, showing the reports
according to the options selected in the Reports page.
Depending on the network vendor, the following reports are generated by default:
o Access Distance Histograms, which displays the number of calls initiated at
specified distances from the access sector.
o Analysis Messages, which displays any errors or warnings that are generated
during the analysis.
Note: This report is displayed only if needed.
o BH DL Power, which displays a summary of the busy-hour downlink power KPIs
for the selection set, and for each sector in the selection set.
This report is displayed for NSN networks only.
o BH Drops, which displays a summary of the busy-hour calls that dropped or were
disconnected, for the selection set, and for each sector in the selection set.
o BH Speech KPIs, which displays a summary of the busy-hour speech KPIs for
the selection set, and for each sector in the selection set.
This report is displayed for Ericsson and Huawei networks only.
o BH Traffic, which displays a summary of the busy-hour traffic for the selection
set, and for each sector in the selection set.
o Daily Drops, which displays a summary of the daily drops or abnormal releases
for the selection set, and for each sector in the selection set.
o Daily HSDPA KPIs, which displays a summary of the daily high-speed downlink
packet-access KPIs for the selection set, and for each sector in the selection set.
This report is displayed for Ericsson and Huawei networks only.
301
o Daily Speech KPIs, which displays a summary of the daily speech KPIs for the
selection set, and for each sector in the selection set.
This report is displayed for Huawei and Ericsson networks only.
o Daily Traffic, which displays a summary of the daily traffic for the selection set,
and for each sector in the selection set.
o Mobile Drop, which displays regular and PivotTable reports for all abnormal
disconnections in the selection set, per user, phone type, etc..
For a detailed description of the tabs and fields in the analysis reports, refer to the
Ultima Mentor Help.
KPIs
Depending on your network vendor, you can run an analysis based on the following KPIs:
 Ericsson UMTS KPIs
 Ericsson LTE KPIs
 Huawei UMTS KPIs
 Huawei LTE KPIs
 NSN UMTS KPIs
 ZTE UMTS KPIs
Ericsson UMTS KPIs

The following table lists the Ericsson UMTS KPIs on which you can base the network
analysis.
Name of UMTS KPI Description
Active Set Addition Failure Shows the failure rate of attempted additions of sectors into
Rate the active set.
Active Set Message Count Shows the number of messages per hour, per sector, where
the sector is part of the active set.
This KPI, which is a breakdown of the neighbor-list model to
sectors and hours, is very useful for analyzing time-zone
problems and other mismatches between call-trace data and
KPIs.
Average IRAT Outgoing Cell Shows the number of outgoing IRAT (to GSM) cell change
Changes Per Session attempts.
Average IRAT Outgoing Shows the average number of outgoing IRAT (to GSM)
Handovers Per Call handover attempts per call.
Average Number of CS Shows the average number of downlink OVSF codes

Speech Links (SF=128) occupied by speech users.
Average Number of HSDPA Shows the number of active high-speed users on a sector, via
Users (Erlang) the number of A-DCHs allocated.
302
Average Power (dBm) Shows the average power of the sector, measured in dBm.
Average Power (Watt) Shows the average power of the sector, measured in Watts.
Average User Bit Rate Mean Shows the mean of the average user bit rate histogram
(Kbps) collected from RBS counters.
Average User Bit Rate STDev Shows the standard deviation of the average user bit rate
(Kbps) histogram collected from RBS counters.
Cell Activity (%) Shows the percentage of hours for which the sector was
active. This KPI is taken into consideration when deciding on
the sectors to include in the model selection set.
Compressed Mode Shows the number of initiation attempts in compressed mode.

Activations Per Call Per
Session
CQI 64 QAM Distribution Shows the mean of the CQI distribution for 64QAM HSDPA
Mean (CQI) links.
CQI 64 QAM Distribution Shows the standard deviation of the CQI distribution for
STDev (CQI) 64QAM HSDPA links.
CQI Distribution Mean (CQI) Shows the mean of the CQI distribution histogram collected
from RBS counters.
CQI Distribution STDev (CQI) Shows the standard deviation of the CQI distribution
histogram collected from RBS counters.
CS 57 Accessibility Transport Shows the failure rate of RAB connection setup attempts due
Layer (%) to transport blocking, for CS 57 calls.
CS 64 Access Failure (%) Shows the number of failed CS 64 calls as a percentage of

the total number of attempted CS 64 calls. The calls failed due
to RF or network problems.
CS 64 Accessibility Transport Shows the failure rate of RAB connection setup attempts due
Layer (%) to transport blocking, for CS 64 calls.
CS 64 CCSR (%) Shows the call completion success rate for CS 64 calls.
(Approximation from user perspective.)
CS 64 DL Code Utilization (%) Shows the average number of downlink OVSF codes (SF=32)
occupied by CS 64 users.
CS 64 Drop Rate (%) Shows the number of dropped CS 64 calls, per sector, as a
percentage of the total number of CS 64 calls for the sector.
303
CS 64 Erlang (Erlang) Shows the CS 64 service traffic.
CS 64 GoS (%) Shows the grade of service of the CS 64 service.
CS 64 Users Shows the number of CS 64 users in a sector.
CS Access Attempts Shows the number of attempted CS access calls.
CS Access Fails Shows the number of failed CS access calls.
CS Drop Count Shows the number of dropped CS calls, per sector.
CS Drop Rate (%) Shows the number of dropped CS calls, per sector, as a
percentage of the total number of CS calls for the sector.
CS RRC Connection Success Shows the failure rate of RRC connection setup attempts due
Rate Transport Layer (%) to transport blocking, for CS domain.
CS Speech Access Failure (%) Shows the number of failed CS speech calls as a percentage
of the total number of attempted CS speech calls. The calls
failed due to RF or network problems.
CS Speech Accessibility (%) Shows the number of CS speech calls that were successfully
established, as a percentage of the total number of attempted
CS speech calls.
CS Speech Accessibility Shows the failure rate of RAB connection setup attempts due
Transport Layer (%) to transport blocking, for speech calls.
CS Speech Calls Completed Shows the number of CS speech calls that were successfully
completed.
CS Speech CCSR (%) Shows the call-completion success rate for speech users.
(Approximation from user perspective.)
CS Speech Drop Shows the number of dropped CS speech calls, per sector.
CS Speech Drop Rate (%) Shows the number of dropped CS speech calls, per sector, as
a percentage of the total number of attempted CS speech
calls.
CS Speech GoS (%) Shows the grade of service of the CS speech service.
CS Speech Traffic (Erlang) Shows the speech traffic.
CS Speech Users Shows the number of CS speech users in a sector.
CS Streaming CCSR (%) Shows the call-completion success rate for CS streaming
users. (Approximation from user perspective.)
304
CS Streaming DL Code Shows the average number of downlink OVSF codes

Utilization (%) occupied by CS streaming users.
CS Streaming Drop Rate (%) Shows the number of dropped CS streaming calls, per sector,
as a percentage of the total number of CS streaming calls.
CS Streaming Failure (%) Shows the number of failed CS streaming calls as a

percentage of the total number of attempted CS streaming
calls.
CS Streaming Traffic (Erlang) Shows the CS streaming traffic.
CS Streaming Users Shows the average number of CS streaming users in a sector.
DL R99 Data Traffic (MB) Shows the payload traffic (kbits) in the downlink for R99
Interactive, Background, and Streaming traffic after macro
diversity.
Drops due to Missing Shows the number of dropped calls due to a detected
Neighbor neighbor missing from the neighbor list. (Valid for speech
users only.)
Drops due to SHO Shows the number of dropped calls due to soft handover
issues (Including missing neighbor). Valid for speech users
only.
EMS Critical Count Shows the number of EMS alarm counters, per element, for
critical events. These events affect the service and should be
dealt with as soon as possible.
EMS Info Count Shows the number of EMS alarm counters, per element, for
informational events.
EMS Major Count Shows the number of EMS alarm counters, per element, for
major events. These events can lead to service degradation,
and may require operator intervention.
EMS Minor Count Shows the number of EMS alarm counters, per element, for
minor events. These events do not affect the service, and do
not require operator intervention.
Ericsson Downlink Volume Shows the volume of RLC data received by the UE.
(KBytes)
Ericsson Uplink Volume Shows the volume of RLC data transferred from the UE.
(KBytes)
Eul Traffic (MB) Shows the volume of traffic on the enhanced uplink RAB, in
MB.
305
HS A-DCH Users (Erlang) Shows the number of active high-speed users on a sector, via
the number of A-DCHs allocated.
HS Cell Change Failure Rate Shows the failure rate of HS-DSCH cell change.
(%)
HS PDSCH Code Shortage Shows the number of TTIs in which HSDPA data in the RBS’s
buffer was not fully transmitted to the users due to OVSF code
shortage for HS-PDSCH.
HS PDSCH Code Shortage Shows the number of TTIs in which HSDPA data in the RBS’s
Rate (%) buffer was not fully transmitted to the users due to OVSF code
shortage for HS-PDSCH, as a percentage of the total number
of TTIs in which data transmission was attempted.
HS PDSCH Power Shortage Shows the number of TTIs in which HSDPA data in the RBS’s
buffer was not fully transmitted to the users due to power
shortage for HS-PDSCH.
HS PDSCH Power Shortage Shows the number of TTIs in which HSDPA data in the RBS’s
Rate (%) buffer was not fully transmitted to the users due to power
shortage for HS-PDSCH, as a percentage of the total number
HS Retransmission Rate (%) Shows the retransmission rate (division of bits) on HS-DSCH
by the HARQ processes.
HS SCCH Code Shortage Shows the number of TTIs in which HSDPA data in the RBS’s
buffer was not fully transmitted to the users due to OVSF code
shortage for HS-SCCH.
HS SCCH Code Shortage Rate Shows the number of TTIs in which HSDPA data in the RBS’s
(%) buffer was not fully transmitted to the users due to OVSF code
shortage for HS-SCCH, as a percentage of the total number
HS SCCHs Power Usage Mean Shows the mean of the HS-SCCH power usage histogram
(Watt) collected from RBS counters.
HS SCCHs Power Usage Shows the standard deviation of the HS-SCCH power usage
STDev (Watt) histogram collected from RBS counters.
HS-DSCH Code Usage Shows the distribution of code usage by HS-DSCH when
dynamic code allocation is implemented.
HS-DSCH Empty Subframe Shows the empty subframe rate of the HS-DSCH (ratio of
Rate (%) number of subframes). "Empty subframe" means that data
was not transmitted over HS-DSCH, even though data was
scheduled on a priority queue.
306
HSDPA 16QAM Transmission Shows the percentage of HSDPA blocks that were transmitted
Block Percentage (%) using 16QAM modulation.
HSDPA 64QAM Transmission Shows the percentage of HSDPA blocks that were transmitted
Block Percentage (%) using 64QAM modulation.
HSDPA Interactive Traffic Shows the volume of traffic on the HSDPA interactive RAB
Volume (MB) (downlink), in MB.
HSDPA Net Payload (KBytes) Shows the net payload on all HSDPA RABs.
HSDPA QPSK Transmission Shows the percentage of HSDPA blocks that were transmitted
Block Percentage (%) using QPSK modulation.
Max Power (dBm) Shows the maximum power sampled in the sector, measured
in dBm.
Max Power (Watt) Shows the maximum power sampled in the sector, measured
in Watts.
Min Power (dBm) Shows the minimum power sampled in the sector, measured
in dBm.
Min Power (Watt) Shows the minimum power sampled in the sector, measured
in Watts.
NACK Ratio (%) Shows the percentage of transmitted blocks that were not
acknowledged by the UE, as received by the RBS.
NodeB Available Channel Shows the number of available channel elements of the
Elements DL nodeB in the downlink.
NodeB Available Channel Shows the number of available channel elements of the
Elements UL nodeB in the uplink.
NodeB Used Channel Shows the maximum number of used channel elements in the
Elements DL Max downlink during the measurement period.
NodeB Used Channel Shows the average number of used channel elements in the
Elements DL Mean downlink during the measurement period.
NodeB Used Channel Shows the minimum number of used channel elements in the
Elements DL Min downlink during the measurement period.
NodeB Used Channel Shows the standard deviation of the number of used channel
Elements DL STDev elements in the downlink during the measurement period.
NodeB Used Channel Shows the maximum number of used channel elements in the
Elements UL Max uplink during the measurement period.
307
NodeB Used Channel Shows the average number of used channel elements in the
Elements UL Mean uplink during the measurement period.
NodeB Used Channel Shows the minimum number of used channel elements in the
Elements UL Min uplink during the measurement period.
NodeB Used Channel Shows the standard deviation of the number of used channel
Elements UL STDev elements in the uplink during the measurement period.
Number of Total Successful Shows the total number of successful call attempts for all call
Calls types (circuit, streaming, interactive).
OVSF Code Usage Max (%) Shows the maximum usage of the OVSF code tree.
OVSF Code Usage Mean (%) Shows the average usage of the OVSF code tree.
OVSF Code Usage Min (%) Shows the minimum usage of the OVSF code tree.
OVSF Code Usage STDev (%) Shows the standard deviation of the OVSF code tree usage.
Primary Message Count Shows the number of messages that were counted for the
sector.
PS Average User Throughput Shows the average throughput on all PS RABs (including
Downlink (Kbps) HSDPA) for the downlink.
PS Average User Throughput Shows the average throughput on all PS RABs (including
Uplink (Kbps) HSUPA) for the uplink.
PS Data Interactive Access Shows the number of failed PS data interactive calls as a
Failure (%) percentage of the total number of attempted PS data
interactive calls. The calls failed due to RF or network
problems. Includes high-speed RAB establishment failure
ratio.
PS Data Interactive CCSR (%) Shows the call completion success rate for PS data interactive
users (approximation from user perspective).
PS Data Interactive DCH Shows the access failure rate for PS data interactive calls,
FACH Access Failure (%) including RAB establishment failures on DCH or FACH. Does
not include high-speed RAB establishment failure ratio.
PS Data Interactive DCH Shows the number of successfully completed PS data

FACH CCSR (%) interactive calls, per sector, as a percentage of the total
number of PS data interactive calls for the sector (on DCH or
FACH only, not including HS).
PS Data Interactive DCH Shows the drop rate for PS data interactive calls on DCH or
FACH Drop Rate (%) FACH (HS not included).
308
PS Data Interactive DCH Shows the average number of users of PS interactive services
Users on DCH or FACH (HS not included).
PS Data Interactive Drop Rate Shows the number of dropped PS data interactive calls, per
(%) sector, as a percentage of the total number of attempted PS
data interactive calls.
PS Data Interactive GoS (%) Shows the grade of service of PS data interactive services.
Blocking due to admission can be based on downlink power,
downlink channelization code, downlink Air-interface Speech
Equivalent (ASE), and uplink Air-interface Speech Equivalent.
PS Data Interactive HS Shows the number of failed PS data interactive high-speed

Access Failure (%) calls as a percentage of the total number of attempted PS
data interactive high-speed calls. The calls failed due to RF or
network problems.
PS Data Interactive HS CCSR Shows the call completion success rate for high-speed
(%) interactive users (approximation from user perspective).
PS Data Interactive HS Drop Shows the number of dropped PS data interactive high-speed
Rate (%) calls, per sector, as a percentage of the total number of PS
data interactive high-speed calls.
PS Data Interactive Users Shows the average number of PS data interactive users in a
sector.
PS Data Streaming Access Shows the number of failed PS data streaming calls as a
Failure (%) percentage of the total number of attempted PS data
streaming calls. The calls failed due to RF or network
problems.
PS Data Streaming CCSR (%) Shows the call completion success rate for Packet-switched
data streaming services (approximation from user
perspective).
PS Data Streaming Drop Rate Shows the drop rate for Packet-switched data streaming
(%) services.
PS Data Streaming GoS (%) Shows the grade of service for Packet-switched streaming
services.
PS Data Streaming Users Shows the average number of PS data streaming users in a
sector.
PS Drop Count Shows the number of dropped PS calls, per sector.
PS Drop Rate (%) Shows the number of dropped PS calls, per sector, as a
percentage of the total number of attempted PS calls.
309
PS HSDPA MAC-hs User Shows the average user throughput for PS HSDPA
Throughput On Demand (streaming and interactive, at MAC-hs level), HS user data
only – without retransmissions, padding, etc.
PS Interactive Average Total Shows the average total throughput on the downlink, including
Throughput (KBps) headers, retransmissions, etc.
PS Interactive Average User Shows the average net user throughput on the downlink.
Throughput Downlink (KBps)
PS Interactive Average User Shows the average net user throughput on the uplink.
Throughput Uplink (KBps)
PS Interactive DCH Shows the access blockage rate for PS interactive DCH calls
Accessibility Transport Layer on the transport layer.
(%)
PS Interactive DCH DCH Shows the latency (as averaged in the RNC) on DCH/DCH
Downlink Latency (ms) RABs.
PS Interactive HS Average Shows the average net user throughput for HSDPA RABs.
Throughput (KBps)
PS Interactive HS Average Shows the average total throughput for HSDPA RABs,
Total Throughput (KBps) including headers, retransmissions, etc.
PS Interactive HS Hard Shows the PS interactive high-speed hard handover incoming

Incoming Success (%) success rate as a percentage of the attempted incoming hard
handovers.
PS Interactive HS Hard Shows the PS interactive high-speed hard handover outgoing

Outgoing Success (%) success rate as a percentage of the attempted outgoing hard
handovers.
PS Interactive HS Users Shows the average number of PS interactive HS users per

sector.
PS Interactive HSDPA Shows the access blockage rate for PS interactive HSDPA
Accessibility Transport Layer calls on the transport layer.
(%)
PS Interactive HSDPA DCH Shows the latency (as averaged in the RNC) on HSDPA/DCH
Downlink Latency (ms) RABs.
PS Interactive HSDPA HSUPA Shows the latency (as averaged in the RNC) on
Downlink Latency (ms) HSDPA/HSUPA RABs.
310
PS Interactive HSUPA (EUL) Shows the number of dropped PS data interactive HSUPA
Drop Rate (%) (Enhanced Uplink) calls, per sector, as a percentage of the
total number of attempted PS data interactive HSUPA calls.
PS Interactive Users FACH Shows the average number of PS Interactive users on FACH
per sector.
PS RRC Connection Success Shows the RRC connection failure rate on the transport layer.
Rate Transport Layer (%)
PS Streaming and Packet 8 Shows the average number of users, per sector, on PS
Users streaming plus PS 8kbps/8kbps interactive multi-RAB.
PS Streaming DCH Shows the access blockage rate for PS streaming DCH calls
Accessibility Transport Layer on the transport layer.
(%)
PS Streaming HSDPA Shows the access blockage rate for PS streaming HSDPA
Accessibility Transport Layer calls on the transport layer.
(%)
RAB Failure ADM EUL Shows the number of EUL calls blocked (EDCH part) due to a
lack of resources.
RAB Failure ADM HS Shows the number of HS calls blocked (ADCH part) due to a
lack of resources.
RAB Failure ADM Interactive Shows the number of PS (Non-HS) calls blocked due to a lack
of resources.
RAB Failure ADM Speech Shows the number of CS-speech calls blocked due to a lack
of resources.
RAB Failure Conn Limit Shows the number of PS RAB establishment attempts that
failed due to exceeding the configured connection limit when
allocating Spreading Factors.
RAB Failure DL ASE Shows the number of RAB establishment attempts that failed
due to a lack of downlink ASE.
RAB Failure DL Code Shows the number of RAB establishment attempts that failed
due to a lack of downlink channelization codes.
RAB Failure DL HW Shows the number of RAB establishment attempts that failed
due to a lack of downlink hardware resources.
RAB Failure DL Power Shows the number of RAB establishment attempts that failed
due to a lack of downlink power.
311
RAB Failure EUL Congestion Shows the number of RAB establishment attempts that failed
due to EUL congestion.
RAB Failure UL ASE Shows the number of RAB establishment attempts that failed
due to a lack of uplink ASE.
RAB Failure UL HW Shows the number of RAB establishment attempts that failed
due to a lack of uplink hardware resources.
Radio Procedure Shows the radio procedure admission and congestion failures
Admission/Congestion due to transport layer impact.
Failures
RBS Level - Frame Loss Rate Shows the frame loss rate of the data received by the RBS
Over Iub (%) over Iub.
RBS Level - HS Iub Blockage Shows the percentage of time for which HS data was blocked
Rate (%) because of an Iub limitation.
Soft/Softer Handover Shows the capacity overhead of soft/softer handovers.

Overhead
Speech Drop Call Rate (%) Shows the number of dropped speech calls, per sector, as a
percentage of the total number of attempted speech calls.
Total Average HS DSCH Shows the average transmitted power for all HS-PDSCH
Power (dBm) codes.
Total CQI Distribution Mean Shows the total mean distribution. (CQI Distribution Mean +
(CQI) CQI 64 QAM Distribution Mean)
Total CQI Distribution STDev Shows the total STDev distribution. (CQI Distribution STDev +
(CQI) CQI 64 QAM Distribution STDev)
Total Transmitted Carrier Shows the mean of the total transmitted carrier power
Power Mean (Watt) histogram.
Total Transmitted Carrier Shows the standard deviation of the total transmitted carrier
Power STDev (Watt) power histogram.
Total Transmitted Non HS Shows the mean of the total transmitted non-HS carrier power
Carrier Power Mean (Watt) histogram.
Total Transmitted Non HS Shows the standard deviation of the total transmitted non-HS
Carrier Power STDev (Watt) carrier power histogram.
312
Traffic (Erlang) Shows the amount of traffic, measured in Erlang.

Formula: pmSumBestCs12Establish /
pmSamplesBestCs12Establish + pmSumBestCs57Establish /
pmSamplesBestCs57Establish + pmSumBestCs64Establish /
pmSamplesBestCs64Establish +
pmSumBestAmr12200RabEstablish /
pmSamplesBestAmr12200RabEstablish +
pmSumBestPsHsAdchRabEstablish /
pmSamplesBestPsHsAdchRabEstablish +
pmSumBestPsStr64Ps8RabEstablish /
pmSamplesBestPsStr64Ps8RabEstablish +
pmSumBestPsStr128Ps8RabEstablish /
pmSamplesBestPsStr128Ps8RabEstablish +
pmSumBestDchPsIntRabEstablish /
pmSamplesBestDchPsIntRabEstablish +
pmSumBestPsStreamHsRabEst /
pmSamplesBestPsStreamHsRabEst
UL R99 Data Traffic (MB) Shows the payload traffic (kbits) in the uplink for R99
Interactive, Background, and Streaming traffic before macro
diversity.
Uplink RSSI Mean (dBm) Shows the mean of the uplink RSSI histogram.
Uplink RSSI STDev (dBm) Shows the standard deviation of the uplink RSSI histogram.
313
Ericsson LTE KPIs

The following table lists the Ericsson LTE KPIs on which you can base the network analysis.
Name of LTE KPI Description
Average Number of Shows the mean number of users in a cell.

Connected Users (count)
Formula: Sum(pmLicConnectedUsersLevSum)/
Sum(pmLicConnectedUsersLevSamp)
Average Power (Watt) Shows the average power of a cell, measured in Watts.
AVG UE DL Throughput (kbps) Shows the mean downlink throughput of the cell.
Formula: (Sum(pmPdcpVolDlDrb) +
Sum(pmPdcpVolDlDrbTransUm) -
Sum(pmPdcpVolDlDrbLastTTI))/Sum(pmUeThpTimeDl)/1000
AVG UE UL Throughput (kbps) Shows the mean uplink throughput of the cell.
Formula: Sum(pmUeThpVolUl)/Sum(pmUeThpTimeUl)/1000
DL Available PRBs (count) Shows the total number of Physical Resource Block (PRB)
pairs available for transmission in the downlink.
Formula: AVG(pmPrbAvailDl)
DL Latency (ms) Shows the mean time delay for packets in a cell.
Formula:
Sum(pmPdcpLatTimeDl)/Sum(pmPdcpLatPktTransDl)
DL Payload (MBytes) Shows the total downlink volume on the PDCP layer in a cell.
Formula: Sum(pmPdcpVolDlDrbTrans)/8000
E-RAB Drop, Cell Down Time Shows the total number of abnormal E-RAB releases in a cell
(count) due to cell down time.
Formula: Sum(pmErabRelAbnormalEnbActCdt)
E-RAB Drop, EUtran Shows the total of abnormal E-RAB releases in a cell due to
Generated Reason (count) EUtran-generated reasons.
Formula: Sum(pmErabRelMmeActEutra)
E-RAB Drop, HO Execution Shows the total number of abnormal E-RAB releases in a cell
Failure (count) due to handover-execution failure.
Formula: Sum(pmErabRelAbnormalEnbActHo)
E-RAB Drop, HO Preparation Shows the total number of abnormal E-RAB releases in a cell
(count) during handover preparation.
Formula: Sum(pmErabRelAbnormalEnbActHpr)
314
E-RAB Drop, License Reject Shows the total number of abnormal UE Context Releases in
(count) the cell initiated by the RBS due to license rejection.
Formula: Sum(pmErabRelAbnormalEnbLic)
E-RAB Drop, Transmission Shows the total number of abnormal E-RAB releases in a cell
(count) due to the following reasons: S1 Interface Down, X2 Interface
Down, or Transport Resource Unavailable.
Formula: Sum(pmErabRelAbnormalEnbActTnFail)
E-RAB Drop, UE Lost (count) Shows the total number of abnormal E-RAB releases in a cell
due to lost contact with the UE.
Formula: Sum(pmErabRelAbnormalEnbActUeLost)
E-RAB Drop, UE Pre-Emption Shows the total number of abnormal E-RAB releases in a cell
(count) due to pre-emption.
Formula: Sum(pmErabRelAbnormalEnbActPe)
E-RAB Drop, Unspecified Shows the total number of abnormal E-RAB releases by the
(count) MME in a cell.
Formula: Sum(pmErabRelMmeActUnspecified)
E-RAB Drop, User Inactivity Shows the total number of abnormal E-RAB releases in a cell
(count) due to user inactivity.
Formula: Sum(pmErabRelMmeActUserInactivity)
E-RAB Failure, DL GBR Shows the total number of failed E-RAB setup attempts in a
Overload (count) cell due to downlink GBR overload for resources common to
the eNodeB.
Formula: Sum(pmErabEstabFailGbrDlEnb)
E-RAB Failure, UL GBR Shows the total number of failed E-RAB setup attempts in a
Overload (count) cell due to uplink GBR overload for resources common to the
eNodeB.
Formula: pmErabEstabFailGbrUlEnb
E-RAB Retainability (1/s) Shows the rate of abnormal E-RAB releases in a cell.
Formula: (Sum(pmErabRelAbnormalEnbAct) +
Sum(pmErabRelAbnormalMmeAct))/
Sum(pmSessionTimeUe)
315
E-RAB Retainability (%) Shows the percentage of E-RAB abnormal release out of all
E-RAB releases in a cell.
Formula: 100*(Sum(pmErabRelAbnormalEnbAct) +
Sum(pmErabRelAbnormalMmeAct))/(Sum(pmErabRelAbnor
malEnb) + Sum(pmErabRelNormalEnb) +
Sum(pmErabRelMme))
Initial E-RAB Establishment Shows the percentage of successful E-RAB Establishments

SR (%) in a cell.
Formula: 100*
((Sum(pmRrcConnEstabSucc)/(Sum(pmRrcConnEstabAtt) -
Sum(pmRrcConnEstabAttReatt)) *
(Sum(pmS1SigConnEstabSucc) /
Sum(pmRrcConnEstabSucc)) * (Sum(pmErabEstabSuccInit)/
Sum(pmErabEstabAttInit)))
Peak Number of Connected Shows the maximum allowed number of connected users in a
Users (count) cell.
Formula: Max(pmLicConnectedUsersMax)
RRC Failure, Admission Shows the total number of failed establishment of RRC
(count) Connections in a cell due to all UE bearers being rejected
during bearer admission.
Formula: Sum(pmRrcConnEstabFailBearerAdmissionRej)
RRC Failure, Exceed License Shows the total number of failed RRC Connection
Limit (count) Establishments in a cell due to the valid user license limit
being exceeded.
Formula: Sum(pmRrcConnEstabFailLic)
RRC Failure, High Load Shows the total number of failed RRC Connection
(count) Establishments in a cell due to high load.
Note: This KPI has been removed in version L15A.
Formula: Sum(pmRrcConnEstabFailHighLoad)
RRC Failure, Overload (count) Shows the total number of failed RRC Connection
Establishments in a cell due to cell overload.
Note: This KPI has been removed in version L15A.
Formula: Sum(pmRrcConnEstabFailOverload)
UL Available PRBs (count) Shows the total number of Physical Resource Block (PRB)
pairs available for transmission in the uplink.
Formula: AVG(pmPrbAvailUl)
316
UL Payload (MBytes) Shows the total UL volume on the PDCP layer in a cell.
Formula: Sum(pmPdcpVolUlDrb)/8000
VoIP Integrity (%) Shows the percentage of UEs in a cell that satisfied VoIP call
criteria. (Enough packets for measurements, with 99% of
them within the packet delay budget.)
Formula: 100 * Sum(pmVoipQualityUeUlOk) /
Sum(pmVoipQualityUeUlNok) + Sum
(pmVoipQualityUeUlOk)
Huawei UMTS KPIs

The following table lists the Huawei UMTS KPIs on which you can base the network analysis.
Absolute HSDPA Drops Shows the number of released HSDPA connections due to
(Count) call drops.
Absolute RRC Drop Call Shows the number of released RRC connections due to call
(Count) drops.
Access Failure Rate (%) Shows the number of failed calls as a percentage of the total
number of attempted calls. The calls failed as the mobiles
could not access the traffic channel due to RF or network
problems.
Average HSDPA User Shows the mean downlink throughput for one HSDPA UE in
Throughput (Kbps) a cell.
Average HSUPA User Shows the mean uplink throughput for one HSUPA UE in a
Throughput (Kbps) cell.
Average Number of HSDPA Shows the average number of HSDPA 64QAM UEs in an
64QAM Users HSDPA cell.
Average. Number of HSDPA Shows the average number of HSDPA MIMO UEs in an
MIMO Users HSDPA cell.
Average Number of HSDPA Shows the mean number of HSDPA UEs in an HSDPA
Users serving cell.
Average Number of HSUPA Shows the average number of HSUPA 16QAM UEs in an
16QAM Users HSUPA cell.
317
Average Number of HSUPA Shows the mean number of HSUPA UEs in an HSUPA
Users serving cell.
Average Power (Watt) Shows the average power of the sector, measured in Watts.
Average Power (dBm) Shows the average power of the sector, measured in dBm.
Average Transmitted Carrier Shows the average value of all the TCP reported for a certain
Power (dBm) period. The RNC obtains the TCP values of the cells from the
COMMON MEASUREMENT REPORT message received
from the NodeB.
Average Transmitted Carrier Shows the average value of all the HSDPA TCP reported for
Power - HS (dBm) a certain period. The RNC obtains the HSDPA TCP of the
cells from the COMMON MEASUREMENT REPORT
message received from the NodeB.
Average Transmitted Carrier Shows the average value of all Non-HS TCP reported for a
Power - Non HS (dBm) certain period. The RNC obtains the Non-HS TCP values of
the cells from the COMMON MEASUREMENT REPORT
message received from the NodeB.
Average UL RSSI Shows the average values of all RTWP reported in a certain
period.
Average User Throughput Shows the average user throughput when there is data in the
(bps) cell buffers.
Cell Update RF Loss Attempts Shows the number of cell update messages (due to RF loss)
Rate (%) from the UE as a percentage of the total number of
successful RAB calls.
Cell Update RF Loss Failure Shows the number of times the call origination failed after a
Rate (%) cell update event.
CS Call Rejects (%) Shows the percentage of CS RABs that were unsuccessfully
established due to capability failure.
CS Video Conversational Shows the average number of CS conversational service

Service (Erlang) RBs in a cell at the downlink bit rate of 64 kbit/sec.
DL Non-HS OVSF Code Usage Shows the usage of the OVSF code tree by non-HS
(%) channels.
Drop Rate All RABs (%) Shows the total number of calls for all RABs that were
terminated by other than the calling or called parties, as a
percentage of the total number of attempted calls.
Note: This measurement is taken from the call-trace data.
318
Drop Rate CS (%) Shows the number of CS calls that were terminated by other
than the calling or called parties, as a percentage of the total
number of attempted CS calls.
Drop Rate CS Video Call (%) Shows the number of CS video calls that were terminated by
other than the calling or called parties, as a percentage of the
total number of attempted CS video calls.
Drop Rate HSDPA (%) Shows the number of HSDPA calls that were terminated by
total number of attempted HSDPA calls.
Drop Rate PS (%) Shows the number of PS calls that were terminated by other
than the calling or called parties, as a percentage of the total
number of attempted PS calls.
Drop Rate PS R99 (%) Shows the number of PS R99 calls that were terminated by
total number of attempted PS R99 calls.
Drop Rate Speech (%) Shows the number of speech calls that were terminated by
total number of attempted speech calls.
HS Retransmission Rate (%) Shows the retransmission rate by the HARQ processes. Up
to 10 retransmissions will be taken into consideration.
HS Users per TTI Shows the average number of high-speed users scheduled in
the cell at each 2ms transmission time interval (TTI).
319
HS-DSCH Code Usage Shows the average number of SF=16 codes used by HS-
DSCH.
HS-SCCHs Power Usage Shows the HS-SCCH transmitted power per cell. If more than
one HS-SCCH code is used, then the registered value is the
sum of the individual values.
HSDPA (Mbytes)/Drops Shows the ratio of the HSDPA payload to HSDPA drops.
HSDPA Data Discard Ratio (%) Shows the percentage of discarded user data on HSDPA out
of the total user data received.
HSDPA Payload (MB) Shows the number of MBs transmitted by the MAC-d flow in a
cell.
HSDPA Payload (Byte) Shows the total downlink bytes of all the HSDPA MAC-d
flows in a cell.
HSDPA Utilization (Data) (%) Shows the HSDPA usage in terms of user data. (The
percentage of time the user data was queued on HSDPA.)
HSDPA Utilization (Users) (%) Shows the HSDPA usage in terms of users. (The percentage
of time at least one user was camped on HSDPA.)
HSUPA Load Limited Users Shows the ratio of HSUPA users whose bit rate was limited
Ratio (%) due to uplink load.
HSUPA Payload (MB) Shows the number of MBs received by the MAC-d flow in a
cell.
HSUPA Payload (Byte) Shows the total uplink bytes of all the HSUPA MAC-d flows in
a cell.
HSUPA Unhappy Users Ratio Shows the rate of HSUPA "unhappy" users, as determined by
(%) the "happy bit" of each user.
ISHO CS Success Rate (%) Shows the percentage of successful IRAT handovers during
CS domain.
ISHO HS Success Rate (%) Shows the percentage of successful IRAT handovers during
PS domain for HSDAP service.
ISHO PS Success Rate (%) Shows the percentage of successful IRAT handovers during
PS domain.
Max Number of HSDPA Users Shows the maximum number of HSDPA UEs in an HSDPA
serving cell.
320
Max Number of HSUPA Users Shows the maximum number of HSUPA UEs in an HSUPA
serving cell.
Max Power (dBm) Shows the maximum power sampled in the sector, measured
in dBm.
Max Power (Watt) Shows the maximum power sampled in the sector, measured
in Watts.
Maximum DL Bandwidth Shows the maximum ATM backhaul utilization on up to four

Utilization on ATM (Kbps) ATM ports in the downlink.
Maximum DL Bandwidth Shows the maximum IP backhaul utilization on up to four IP

Utilization on IP (Kbps) ports in the downlink.
Maximum UL Bandwidth Shows the maximum ATM backhaul utilization on up to four

Utilization on ATM (Kbps) ATM ports in the uplink.
Maximum UL Bandwidth Shows the maximum IP backhaul utilization on up to four IP

Utilization on IP (Kbps) ports in the uplink.
Maximum Used DL Bandwidth Shows the maximum bandwidth used on up to four ATM
on ATM (Kbps) ports in the downlink.
Maximum Used DL Bandwidth Shows the maximum bandwidth used on up to four IP ports in
on IP (Kbps) the downlink.
Maximum Used UL Bandwidth Shows the maximum bandwidth used on up to four ATM
on ATM (Kbps) ports in the uplink.
Maximum Used UL Bandwidth Shows the maximum bandwidth used on up to four IP ports in
on IP (Kbps) the uplink.
Min Power (dBm) Shows the minimum power sampled in the sector, measured
in dBm.
Min Power (Watt) Shows the minimum power sampled in the sector, measured
in Watts.
NACK Ratio (%) Shows the percentage of transmitted blocks that were not
acknowledged by the UE, as received by the RBS.
Num Bad Quality Calls All Shows the total number of calls for all RABs that were
RABs (Count) successfully completed, but in bad RF conditions.
Num Bad Quality Calls CS Shows the number of CS calls that were successfully
(Count) completed, but in bad RF conditions.
321
Num Bad Quality Calls CS Shows the number of CS video calls that were successfully
Video Call (Count) completed, but in bad RF conditions.
Num Bad Quality Calls HSDPA Shows the number of HSDPA calls that were successfully
Num Bad Quality Calls PS Shows the number of PS calls that were successfully
Num Bad Quality Calls PS R99 Shows the number of PS R99 calls that were successfully
Num Bad Quality Calls Speech Shows the number of speech calls that were successfully
(Count) completed, but with bad RF conditions.
sector.
PS Call Rejects (%) Shows the percentage of PS RABs that were unsuccessfully
established due to capability failure.
PS DL Payload – Non HS, RLC Shows the downlink PS volume of background and
Level (MB) interactive services.
PS UL Payload – Non HS, RLC Shows the uplink PS volume of background and interactive
Level (MB) services.
RAB Blocking Rate (%) Shows the percentage of CS and PS domain calls that were
unsuccessfully established due to capability failures.
RAB CS DCR (%) Shows the percentage of CS AMR drops.
RAB CS Speech Accessibility Shows the number of CS speech calls that were successfully
(%) established, as a percentage of the total number of attempted
CS speech calls.
RAB CS Speech Drop Count Shows the number of CS speech calls that were dropped.
(Count)
RAB HSDPA DCR (%) Shows the percentage of HSDPA drops.
RAB PS DCR (%) Shows the percentage of PS domain drops.
RAB Video Call DCR (%) Shows the percentage of CS 64Kbit/s services.
322
RRC 1st Assignment Success Shows the call setup time, where 100% indicates that the first
Rate (%) RRC was successful.
RRC Access Failure (%) Shows the percentage of RRC access failures.
RRC Blocking Rate (%) Shows the percentage of RRC calls that were rejected due to
congestion.
RRC Drop Call Rate (%) Shows the percentage of RRC call drops.
RRC IRAT Reselection Ratio Shows areas where there is a lot of traffic moving from the
(%) 2G networks towards the 3G network.
This can point out areas where there are a lot of IRAT HOs
from the 3G to the 2G networks due to quality or coverage
problems.
Sectors Per Users (%) Shows the average number of sectors per user.
SHO Factor (%) Shows the ratio between the amount of channel elements
that support the calls and the amount of primary traffic.
SHO Success Rate (%) Shows the percentage of successful soft handovers. It shows
the number of successful RL deletions and additions in soft
handovers out of the total number of attempted RL deletions.
Total Average HS-DSCH Shows the total average HS-DSCH power (power of the
Power HSDPA data channel) over the measurement period.
Total Best Con Rel Offset All Shows the total number of cases for all RABS in which this
RABs (Count) cell as source cell was 12dB lower than another cell that was
not part of the monitored set.
Note: This measurement is taken from the call-trace data,
and is counted once per cell per conversation.
Total Best Con Rel Offset CS Shows the number of CS calls in which this cell as source cell
(Count) was 12dB lower than another cell that was not part of the
monitored set.
Total Best Con Rel Offset CS Shows the number of CS video calls in which this cell as
Video Call (Count) source cell was 12dB lower than another cell that was not
part of the monitored set.
Total Best Con Rel Offset Shows the number of HSDPA calls in which this cell as
HSDPA (Count) source cell was 12dB lower than another cell that was not
323
Total Best Con Rel Offset PS Shows the number of PS calls in which this cell as source cell
(Count) was 12dB lower than another cell that was not part of the
monitored set.
Total Best Con Rel Offset PS Shows the number of PS R99 calls in which this cell as
R99 (Count) source cell was 12dB lower than another cell that was not
Total Best Con Rel Offset Shows the number of speech calls in which this cell as
Speech (Count) source cell was 12dB lower than another cell that was not
Total Cell Update Attempts - Shows the total number of cell update attempts due to radio
RF Loss (Count) link failures.
Total Calls All RABs (Count) Shows the total number of attempted calls for all RABs.
Total Calls CS (Count) Shows the total number of attempted CS calls.

Total Calls CS Video Call Shows the total number of attempted CS video calls.
(Count) Note: This measurement is taken from the call-trace data.
Total Calls HSDPA (Count) Shows the total number of attempted HSDPA calls.
Total Calls PS (Count) Shows the total number of attempted PS calls.

Total Calls PS R99 (Count) Shows the total number of attempted PS 99 calls.
Total Calls Speech (Count) Shows the total number of attempted speech calls.
Total Cell Update Attempts Shows the total number of cell update attempts due to RLC
with RLC Unrecoverable Error with unrecoverable errors.
(Count)
Total Cell Update Success Shows the total number of established cell updates due to
Established (Count) radio link failure.
Total Cell Update Success Shows the total number of successful cell updates due to
with RLC Unrecoverable Error RLC unrecoverable errors.
(Count)
324
Total CS Success Calls Shows the number of successfully established RABs on the
(Count) CS domain.
Total Drops All RABs (Count) Shows the total number of calls for all RABs that were
terminated by other than the calling or called parties.
Total Drops CS (Count) Shows the number of CS calls that were terminated by other
than the calling or called parties.
Total Drops CS Video Call Shows the number of CS video calls that were terminated by
(Count) other than the calling or called parties.
Total Drops HSDPA (Count) Shows the number of HSDPA calls that were terminated by
other than the calling or called parties.
Total Drops PS (Count) Shows the number of PS calls that were terminated by other
than the calling or called parties.
Total Drops PS R99 (Count) Shows the number of PS R99 calls that were terminated by
Total Drops Speech (Count) Shows the number of speech calls that were terminated by
Total Fail of Cell Update with Shows the number of times the RNC failed to receive the
No Reply (Count) physical channel reconfiguration message from the UE, due
to the expiry of the relevant timer.
Total HSDPA Success Calls Shows the number of successfully established RABs on the
(Count) HSDPA domain.
Total Mon Con Rel Offset All Shows the total number of cases for all RABs in which this
RABs (Count) cell was 12dB higher than the source cell, while not being in
the monitored set.
Note: This measurement is taken from the call-trace data,
and is counted once per cell per conversation.
Total Mon Con Rel Offset CS Shows the number of CS calls in which this cell was 12dB
(Count) higher than the source cell, while not being in the monitored
set.
325
Total Mon Con Rel Offset CS Shows the number of CS video calls in which this cell was
Video Call (Count) 12dB higher than the source cell, while not being in the
monitored set.
Total Mon Con Rel Offset Shows the number of HSDPA calls in which this cell was
HSDPA (Count) 12dB higher than the source cell, while not being in the
monitored set.
Total Mon Con Rel Offset PS Shows the number of PS calls in which this cell was 12dB
(Count) higher than the source cell, while not being in the monitored
set.
Total Mon Con Rel Offset PS Shows the number of PS R99 calls in which this cell was
R99 (Count) 12dB higher than the source cell, while not being in the
monitored set.
Total Mon Con Rel Offset Shows the number of speech calls in which this cell was
Speech (Count) 12dB higher than the source cell, while not being in the
monitored set.
Total PS Success Calls Shows the number of successfully established RABs on the
(Count) PS domain.
Total RAB Success (Count) Shows the number of successfully established RABs on the
PS (including HS) and CS domains.
Total RRC Access Failure Shows the number of RRC access failures.
(Count)
Total RRC Success Call Shows the number of successful RRCs.

(Count)

Formula: VS.CellDCHUEs
Version V900R011 only: Number of UEs in CELL_DCH
state for cell
Uplink Noise Rise (dB) Shows the average of the uplink noise rise.
Voice Traffic (Erlang) Shows the amount of voice traffic, measured in Erlang.
326
Huawei LTE KPIs

The following table lists the Huawei LTE KPIs on which you can base the network analysis.
Average Number of Users Shows the average number of users in RRC Connected
(decimal) mode in a cell. The eNodeB records the number of users in
the cell to be sampled every second, and then calculates the
average value of these samples throughout the measurement
period.
Formula: AvgUserNumber = AVG(L.Traffic.User.Avg)
Average Power (Watt) Shows the average value of the transmit power of the
PDSCH, in Watt, within the reporting interval.
Formula: Avg((10^((L.DLPwr.Avg)/10)/1000)
Average transmit power (dBm) Shows the average value of the transmit power of the
PDSCH, in dBm, within the reporting interval.
Formula: Avg (L.DLPwr.Avg)
Cell Downlink Data Volume Shows the total downlink traffic volume in the cell, measured
(MBytes) at the PDCP layer and excluding the PDCP header.
Formula: CellDLTrafficVolume = SUM(L.Thrp.bits.DL)
Cell Downlink Data Volume - Shows the downlink traffic volume in a cell for QCI1 to QCI9,
QCI1 (VoIP)...QCI9 (MBytes) according to the QCI levels defined in the QoS information,
measured at the PDCP layer and excluding the PDCP
header.
Formula: SUM(L.Thrp.bits.DL.QCI.1)
Cell Uplink Data Volume Shows the total uplink traffic volume in the cell, measured at
(MBytes) the PDCP layer and excluding the PDCP header.
Formula: CellULTrafficVolume = SUM(L.Thrp.bits.UL)
327
Cell Uplink Data Volume - Shows the uplink traffic volume in a cell for CQI1 to QCI9,
QCI1 (VoIP)...QCI9 (MBytes) according to the QCI levels defined in the QoS information,
measured at the PDCP layer and excluding the PDCP
header.
Formula: SUM(L.Thrp.bits.UL.QCI.1)
DL Average PDSCH RB usage Shows the average number of resource blocks (RBs) used in
(decimal) the downlink within the reporting interval.
Formula: avg (RB_UsedDL)
Maximal Number of Users Shows the maximum number of users in RRC Connected
(decimal) mode in a cell. The eNodeB records the number of users in
the cell to be sampled every second and then calculates the
maximum value of these samples throughout the
measurement period.
Formula: MaxUserNumber = MAX(L.Traffic.User.Max)
Maximal transmit power (dBm) Shows the maximum transmit power of the PDSCH, in dBm,
within the reporting interval.
Formula: Max (L.DLPwr.Max)
Number of DRBs in a cell Shows the total number of radio bearers in the cell, based on
(decimal) the number of active RRC connections.
Formula: RadioBearers = SUM(L.Traffic.DRB)
328
Number of DRBs in a cell - Shows the number of radio bearers for QCI1 to QCI9,
QCI1 (VoIP)...QCI9 (decimal) according to the QCI level defined in the QoS information,
based on the number of active RRC connections.
Formula: RadioBearers_QCI_1 = SUM(L.Traffic.DRB.QCI.1)
Traffic (Erlang) Shows the traffic, in Erlang, based on average number of

users in the cell.
Formula: SUM (L.Traffic.User.Avg)
UL average PDSCH RB usage Shows the average number of resource blocks (RBs) used in
(decimal) the uplink within the reporting interval.
Formula: avg (RB_UsedUL)
329
NSN UMTS KPIs

The following table lists the NSN UMTS KPIs on which you can base the network analysis.
AMR Call Setup Success Ratio Shows the AMR Call Setup Success Ratio [%] over the
(%) reporting period.
Formula: 100 *(M1001C22 - M1001C23 + M1001C32 -
M1001C33 + M1001C40 - M1001C41 - M1001C562 -
M1001C553- M1001C558 ) / (M1001C22 + M1001C32 +
M1001C40 - M1001C573 - M1001C578 - M1001C582 -
M1001C562 - M1001C553- M1001C558 - M1001C617) *
(M1001C115 / M1001C66) %
AMR Voice Drop Rate (%) Shows the number of AMR voice calls that dropped as a
percentage of the number of attempted AMR voice calls.
Formula: 100 * (M1001C144 + M1001C145 + M1001C146 +
M1001C147 + M1001C148 + M1001C150 + M1001C392) /
(M1001C136 + M1001C143 + M1001C144 + M1001C145 +
M1001C146 + M1001C147 + M1001C148 + M1001C150 +
M1001C392)
Average DL Tx Power (dBm) Shows the average downlink transmit power, measured in
dBm.
Formula: milliWattToDbm (M1000C15*dbmToMilliWatt
(M1000C14/100) +
M1000C17*dbmToMilliWatt(M1000C16/100) +
M1000C19*dbmToMilliWatt (M1000C18/100) +
M1000C21*dbmToMilliWatt (M1000C20/100) +
M1000C23*dbmToMilliWatt (M1000C22/100)) / (M1000C15
+M1000C17 + M1000C19 + M1000C21 + M1000C23)
Average HSPA DL Power Shows the average HSPA downlink power.

(dBm)
Formula: M1000C238
Average Noise floor of the Shows the average noise floor of the system.
system (dBm)
Formula: milliWattToDbm(M1000C11 /
dbmToMilliWatt(M1000C10)/M1000C11)
Average Noise Rise (dBm) Shows the average noise rise.

Formula: milliWattToDbm(M1000C11 /
dbmToMilliWatt(M1000C10)/M1000C11) + 107
Average Non HSPA DL power Shows the average non-HSPA downlink power.
(dBm)
Formula: Average DL Tx Power – Average HSPA DL Power
330
Average Usage of Code Shows the average code usage, in percentage, in a

Capacity measurement period. Average code usage is calculated as the
ratio between the number of unavailable SFx codes and the
number of all (available and unavailable) SFx codes, where
SFx refers to the highest spreading factor.
Note that the SFx codes may be unavailable due to two
reasons — the code is allocated, or the code is unavailable
because another code is allocated in the same code tree
branch and thus prevents the use of the SFx code.
Formula: M1000C72 / M1000C73
CS Conversational Drop Rate Shows the number of dropped CS conversation calls at

(64Kbps) (%) 64Kbps, per sector, as a percentage of the total number of
attempted 64Kbps CS conversational calls for the sector.
Formula: 100*(CS Conversational Drops (64Kbps)) /
(M1001C152 + M1001C151 + M1001C648 + M1001C645 +
M1001C137 + M1001C155 + M1001C156 + M1001C157 +
M1001C158 + M1001C160 + M1001C393 + M1001C691)
CS Conversational Drops Shows the number of CS conversational calls at 64Kbps that

(64Kbps) (Count) dropped.
Formula: M1001C152 + M1001C155 + M1001C156 +
M1001C157 + M1001C158 + M1001C160 + M1001C393 +
M1001C691
CS Conversational Traffic Shows the amount of CS conversational traffic at 64Kbps, in

(64Kbps) (Erlang) Erlang.
Formula: M1001C368 / (100 * 60 * 60)
CS Streaming Drop Rate (%) Shows the number of CS streaming calls that dropped, as a
percentage of the total number of attempted CS streaming
calls.
Formula: (CS Streaming RAB Drops) / (M1001C138 +
M1001C153 + M1001C154 + M1001C646 + M1001C649 +
M1001C161 + M1001C162 + M1001C163 + M1001C164 +
M1001C166 + M1001C394 + M1001C692)
CS Streaming Drops (Count) Shows the number of SC streaming calls that dropped.
Formula: M1001C154 + M1001C161 + M1001C162 +
M1001C163 + M1001C164 + M1001C166 + M1001C394 +
M1001C692
CS Streaming Traffic Shows the amount of CS streaming traffic, at 14.4 Kbps.

(14.4Kbps) (Erlang)
Formula: M1001C370/(100*60*60)
331
CS Streaming Traffic Shows the amount of CS streaming traffic, at 57.6 Kbps.

(57.6Kbps) (Erlang)
Formula: M1001C372/(100*60*60)
CS Total Traffic (Erlang) Shows the total amount of CS traffic, in Erlang.

Formula: (M1001C199 + M1001C368 + M1001C370 +
M1001C372) / (100*60*60)
CS Voice Drop Rate (%) Shows the number of CS voice calls that dropped, as a
percentage of the total number of attempted CS voice calls.
Formula: (M1001C144 + M1001C145 + M1001C146 +
M1001C147 + M1001C148 + M1001C150 + M1001C392 +
M1001C690) / (M1001C136 + M1001C143 + M1001C144 +
M1001C145 + M1001C146 + M1001C147 + M1001C148 +
M1001C150 + M1001C392 + M1001C644 + M1001C647 +
M1001C690)
CS Voice Drops (Count) Shows the number of CS voice calls that dropped.
Formula: M1001C144+M1001C145 + M1001C146 +
M1001C147 + M1001C148 + M1001C150 + M1001C392 +
M1001C690
CS Voice Traffic (Erlang) Shows the amount of CS voice traffic, in Erlang.

Formula: M1001C199 / (100 * 60 * 60)
DL R99 Traffic Volume (MB) Shows the volume of downlink release 99 data, in MB.
Formula: M1026C31 / (1024*1024) for DL R99
Drops AMR Shows the RAB Success ratio for AMR Voice [%] over the
reporting period. Covers RAB Active Phase of a call.
Formula: ( M1001C144 + M1001C145 + M1001C146 +
M1001C147 + M1001C148 + M1001C150 + M1001C392)
332
HSDPA Average Throughput Shows the average throughput for HSDPA traffic.
(KBps)
Formula: 8 * (M1026C31_PS_HSDPA_streaming +
M1026C31_PS_HSDPA_interactive +
M1026C31_PS_HSDPA_background +
M1026C31_CS_HSDPA_streaming +
M1026C31_CS_HSDPA_interactive +
M1026C31_CS_HSDPA_background) /
(M1026C29_PS_HSDPA_streaming +
M1026C29_PS_HSDPA_interactive +
M1026C29_PS_HSDPA_background +
M1026C29_CS_HSDPA_streaming +
M1026C29_CS_HSDPA_interactive +
M1026C29_CS_HSDPA_background)
HSDPA MAC-d average net Shows the HSDPA MAC-d net throughput, meaning the
throughput at BTS (kbps) successfully delivered MAC-d PDUs to HSDPA-capable UEs
assuming that MAC-hs is capable of delivering the PDUs.
Formula: (M5000C126 - M5000C127) / (" PERIOD
DURATION IN SECONDS ")
HSDPA received data (MBit) Shows the HSDPA received data (Mbit) in RAN access points
(=WCELLs). This is based on the received MAC-d PDUs in
HS-DSCH data frames at the BTS.
Formula: (M5000C126 / 1000 ) MBit
HSDPA Resource Retainability Shows the retainability of all successfully allocated HS-DSCH
for NRT Traffic (%) resources for NRT traffic.
Formula: 100*((M1002C407 + M1002C410) / ( M1002C407 +
M1002C410 + M1002C408 + M1002C411 + M1002C479 +
M1002C482))
HSDPA Serving Cell Change Shows the HSDPA serving cell change success rate over the
Success Rate (%) reporting period in the source cell.
Formula: ((M1008C222+ M1008C223) / (M1008C213+
M1008C214+ M1008C215 + M1008C216))
HSDPA Setup Success Ratio Shows the HSDPA setup success ratio [%] over the reporting
from user perspective (%) period from the end-user perspective. Note that this KPI is
affected by all HSDPA setup attempts by the user, including
cases where the cell is not configured to support HSDPA.
Formula: ((M1022C21 + M1022C22 + M1022C23 +
M1022C24 + M1022C25 + M1022C26 / ( M1022C3 +
M1022C4 + M1022C5 + M1022C6))
HSDPA Traffic (Erlang) Shows the amount of HSDPA traffic, in Erlang.

Formula: M1022C153 / (60*60)
333
HSDPA Traffic Volume (MB) Shows the volume of HSDPA data, in MB.
Formula: M1026C31 / (1024*1024) for HSDPA
HSUPA resource Retainability Shows the accessibility of all started resource allocations for
for NRT Traffic (%) E-DCH for NRT traffic. The number of times the E-DCH
channel has been established is divided by the number of
times the HS-DSCH channel has been selected by the cell
specific PS.
Formula: ((M1002C535 + M1002C536 +
M1002C537+M1002C538) / (M1002C535 + M1002C536 +
M1002C537 + M1002C538 + M1002C539 + M1002C540+
M1002C541 + M1002C542))
HSUPA Traffic (Erlang) Shows the amount of HSUPA traffic, in Erlang.

Formula: M1022C155/(60*60)
HSUPA Traffic Volume (MB) Shows the volume of HSUPA data, in MB.
Formula: M1026C30 / (1024*1024) for HSUPA
Inter System RT Hard Shows the inter-system real time user hard handover success
Handover Success Ratio (%) ratio [%] for the reporting period in the source cell of the hard
handover.
Formula: ((M1010C19 + M1010C23 + M1010C27 +
M1010C31 + M1010C35 + M1010C77 + M1010C98 +
M1010C198 + M1010C197+ M1010C154 + M1010C149 +
M1010C150 + M1010C152 + M1010C151 + M1010C153 +
M1010C186) /(M1010C18 + M1010C22 + M1010C26 +
M1010C30 + M1010C34 + M1010C76 + M1010C97 +
M1010C196 + M1010C195 + M1010C137 + M1010C138 +
M1010C140 + M1010C139 + M1010C141 + M1010C185))
Packet Session Success Ratio Shows the Packet Session Success ratio for Interactive and
(SSR) (%) Background RABs.
Formula: 1-((M1022C57 + M1022C58 + M1022C59 +
M1022C60 + M1022C61 + M1022C62 + M1022C63 +
M1022C64 + M1022C65 + M1022C66 + M1022C67 +
M1022C68) / (M1022C57 + M1022C58 + M1022C59 +
M1022C60 + M1022C61 + M1022C62 + M1022C63 +
M1022C64 + M1022C65 + M1022C66 + M1022C67 +
M1022C68 + M1022C45 + M1022C46 + M1022C47 +
M1022C48 + M1022C49 + M1022C50))
sector.
334
PS Background Drop Rate (%) Shows the number of PS background calls that dropped, as a
percentage of the number of attempted PS background
sessions.
Formula: (M1001C191 + M1001C192 + M1001C193 +
M1001C194 + M1001C196 + M1001C398 + M1001C695 -
M1001C594) / (M1001C191 + M1001C192 + M1001C193 +
M1001C194 + M1001C196 + M1001C398 + M1001C695 +
M1001C142 + M1001C172 + M1001C802 + M1001C805)
PS Background Drops (Count) Shows the number of PS background calls that dropped.
Formula: M1001C191 + M1001C192 + M1001C193 +
M1001C194 + M1001C196 + M1001C398 + M1001C695 -
M1001C594
PS Background Traffic Shows the amount of PS background traffic, in Erlang.

(Erlang)
Formula: M1001C211 / (100 * 60 * 60)
PS DL Background Volume Shows the volume of PS background data for the downlink, in
(MB) MB.
Formula: M1026C31 / (1024*1024) for PS DL Background
PS DL Interactive Volume (MB) Shows the volume of PS interactive data for the downlink, in
MB.
Formula: M1026C31 / (1024*1024) for PS DL Interactive
PS DL Streaming Volume (MB) Shows the volume of PS streaming data for the downlink, in
MB.
Formula: M1026C31 / (1024*1024) for PS DL Streaming
PS Drop Rate (%) Shows the number of PS calls that dropped, as a percentage
of the number of attempted PS call sessions.
Formula: (PS Interactive RAB Drops + PS Streaming RAB
Drops + PS Background RAB Drops) / (M1001C185 +
M1001C186 + M1001C187 + M1001C188 + M1001C190 +
M1001C397 + M1001C694 + M1001C141 + M1001C171 +
M1001C801 + M1001C804 + M1001C191 + M1001C192 +
M1001C193 + M1001C194 + M1001C196 + M1001C398 +
M1001C695 + M1001C142 + M1001C172 + M1001C802 +
M1001C805 + M1001C170 + M1001C179 + M1001C180 +
M1001C181 + M1001C182 + M1001C184 + M1001C396 +
M1001C140 + M1001C169 + M1001C806 + M1001C807 +
M1001C693)
335
PS Interactive Drop Rate (%) Shows the number of interactive PS calls that dropped, as a
percentage of the number of attempted interactive PS call
sessions.
Formula: (M1001C185 + M1001C186 + M1001C187 +
M1001C188 + M1001C190 + M1001C397+M1001C694-
M1001C593) / (M1001C185 + M1001C186 + M1001C187 +
M1001C188 + M1001C190 + M1001C397 + M1001C694 +
M1001C141 + M1001C171 + M1001C801 + M1001C804)
PS Interactive Drops (Count) Shows the number of interactive PS calls that dropped.
Formula: (M1001C185 + M1001C186 + M1001C187 +
M1001C188 + M1001C190 + M1001C397 + M1001C694 -
M1001C593)
PS Interactive Traffic (Erlang) Shows the amount of PS interactive traffic, in Erlang.

Formula: M1001C209 / (100 * 60 * 60)
PS Streaming Drop Rate (%) Shows the number of PS streaming calls that dropped, as a
percentage of the number of attempted PS streaming call
sessions.
Formula: (PS Streaming RAB Drops) / (M1001C170 +
M1001C179 + M1001C180 + M1001C181 + M1001C182 +
M1001C184 + M1001C396 + M1001C140 + M1001C169 +
M1001C806 + M1001C807 + M1001C693)
PS Streaming Drops (count) Shows the number of PS streaming calls that dropped.
Formula: M1001C170 + M1001C179 + M1001C180 +
M1001C181 + M1001C182 + M1001C184 + M1001C396 +
M1001C693
PS Streaming Traffic (Erlang) Shows the amount of PS streaming traffic, in Erlang.

Formula: M1001C207 / (100 * 60 * 60)
PS UL Background Volume Shows the volume of PS background calls for the uplink, in
(MB) MB.
Formula: M1026C30 / (1024*1024) for PS UL Background
PS UL Interactive Volume (MB) Shows the volume of PS interactive calls for the uplink, in MB.
Formula: M1026C30 / (1024*1024) for PS UL Interactive
PS UL Streaming Volume (MB) Shows the volume of PS streaming calls for the uplink, in MB.
Formula: M1026C30/ (1024*1024) for PS UL Streaming
336
RAB Setup and Access Shows the RAB Setup and Access Complete Ratio [%] for
Complete Ratio for AMR Voice voice calls over the reporting period. Covers RAB Setup and
(%) Access phases (From RAB Assignment Request to Radio
Bearer Setup Complete).
Formula: (M1001C115)/ (M1001C66)
RAB Setup and Access Shows the RAB Setup and Access Complete ratio [%] for NRT
Complete Ratio for NRT services over the reporting period. Covers RAB Setup and
Service from user perspective Access phases (From RAB Assignment Request to Radio
(%) Bearer Setup Complete).
Formula: ((M1001C120 + M1001C121) / (M1001C71 +
M1001C72))
RAB Success Ratio AMR Shows the RAB Success Ratio for AMR Voice [%] over the
Voice from network reporting period. Covers RAB Active Phase of a call.
perspective (%)
Formula: 1-(( M1001C145 + M1001C146 + M1001C147 +
M1001C148 + M1001C150) / (M1001C136 + M1001C143 +
M1001C144 + M1001C145 + M1001C146 + M1001C147 +
M1001C148 + M1001C150 + M1001C392))
RAB Success Ratio AMR Shows the RAB Success Ratio for AMR Voice [%] over the
Voice from user perspective reporting period. Covers RAB Active Phase of a call.
(%)
Formula: 1-((M1001C144 + M1001C145 + M1001C146 +
M1001C147 + M1001C148 + M1001C150 + M1001C392) /
(M1001C136 + M1001C143 + M1001C144 + M1001C145 +
M1001C146 + M1001C147 + M1001C148 + M1001C150 +
M1001C392))
RRC Setup and Access Shows the RRC Setup and Access Complete ratio [%] over
Complete Ratio (%) the reporting period. Covers RRC Setup and Access phases
(From RRC Connection Request to RRC Connection Setup
Complete).
Formula: (M1001C8 + M1001C260)/ (M1001C0 +
M1001C259 - M1001C617)
RRC Success Ratio from user Shows the RRC Setup and Access Complete ratio [%] over
perspective (%) the reporting period. Covers RRC Setup and Access phases
(From RRC Connection Request to RRC Connection Setup
Complete).
Formula: 1-(( M1001C14 + M1001C15 + M1001C16 +
M1001C17 + M1001C18 + M1001C21 + M1001C391) /
(M1001C12 + M1001C13 + M1001C14 + M1001C15 +
M1001C16 + M1001C17 + M1001C18 + M1001C21 +
M1001C391)
337
Total Calls (all RABs) (Count) Shows the total number of call for all RABs.
Formula: {Total Setup Attempts (all RABs)} - {Total Drops (all
RABs)}
Total CS voice calls (Count) Shows the total number of CS voice calls.
Formula: M1001C136 + M1001C143 + M1001C144 +
M1001C145 + M1001C146 + M1001C147 + M1001C148 +
M1001C150 + M1001C392 + M1001C644 + M1001C647 +
M1001C690
Total DL Volume (MB) Shows the volume of downlink calls, in MB.

Formula: (DL R99 Traffic Volume + HSDPA Traffic
Volume)/(1024*1024)
Total Drop Rate (all RABs) (%) Shows the total number of dropped calls for all RABs, as a
percentage of the total number of attempted RAB call
sessions.
Formula: Total Drops (all RABs) / Total Setup Attempts (all
RABs)
Total Drops (all RABs) (Count) Shows the total number of dropped calls for all RABs.
Formula: M1001C144 + M1001C145 + M1001C146 +
M1001C147 + M1001C148 + M1001C150 + M1001C392 +
M1001C690 + M1001C152 + M1001C155 + M1001C156 +
M1001C157 + M1001C158 + M1001C160 + M1001C393 +
M1001C691 + M1001C154 + M1001C161 + M1001C162 +
M1001C163 + M1001C164 + M1001C166 + M1001C394 +
M1001C692 + M1001C170 + M1001C179 + M1001C180 +
M1001C181 + M1001C182 + M1001C184 + M1001C396 +
M1001C693 + M1001C191 + M1001C192 + M1001C193 +
M1001C194 + M1001C196 + M1001C398 + M1001C695 -
M1001C594 + M1001C185 + M1001C186 + M1001C187 +
M1001C188 + M1001C190 + M1001C397 + M1001C694 -
M1001C593
Total UL Volume (MB) Shows the total volume of the R99 and HSUPA traffic for the
uplink, in MB.
Formula: (UL R99 Traffic Volume + HSUPA Traffic Volume) /
(1024*1024)

Formula: (M1001C199 + M1001C207 + M1001C209 + M1001C211
+ M1001C368 + M1001C370 + M1001C372) / 360000
UL R99 Traffic Volume (MB) Shows the volume of R99 traffic for the uplink.
Formula: M1026C30 / (1024*1024) for UL R99
338
Voice Drops due to bts Shows the number of voice calls that dropped due to BTS
(Count) failures.
Formula: M1001C147
Voice Drops due to Iu (Count) Shows the number of voice calls that dropped due to Iu
failures.
Formula: M1001C145
Voice Drops due to iuR Shows the number of voice calls that dropped due to iuR
(Count) failures.
Formula: M1001C148
Voice Drops due to RAB pre- Shows the number of voice calls that dropped due to RAB pre-
empted (Count) empted failures.
Formula: M1001C144
Voice Drops due to radio Shows the number of voice calls that dropped due to radio
interface (Count) interface failures.
Formula: M1001C146
Voice Drops due to RNC Shows the number of voice calls that dropped due to RNC
(Count) failures.
Formula: M1001C150
Voice Drops due to Shows the number of voice calls that dropped due to
transmission (Count) transmission failures.
Formula: M1001C690
Voice Drops due to ue (Count) Shows the number of voice calls that dropped due to UE
failures.
Formula: M1001C392
339
NSN LTE KPIs

Mentor supports over 400 NSN LTE KPIs. For a full list of KPIs and their formulas, please
refer to the Ultima Mentor Online Help.
ZTE UMTS KPIs

The following table lists the ZTE UMTS KPIs on which you can base the network analysis.
Average Cell Code Resource Shows the average availability of the cell code resources.
Availability (%)
Formula: C310424230/C310424231
Average Cell Freq RTWP Shows the average power of totally received bandwidth for
(dBm) the cell. (This is also referred to as Average UL RSSI.)
Formula: (C310444466/C310444467) – 112
Average Cell TCP Utilization Shows the average total code–power utilization of the cell.
Ratio (%)
Formula: C310444439/C310444444
Average HSDPA Code Shows the average HSDPA code resource utilization.
Resource Utilization (%)
Formula: C310434424/C310434425/16 +
C310434429/C310434425/128
Average Non-HS Power (dBm) Shows the average total code-power for non-HS traffic.
Formula: C310454493/C310456517
Average non-HSDPA TCP Shows the average total code-power utilization ratio for non-
Utilization Ratio (%) HSDPA traffic.
Formula: C310454489/C310456517
Average Power (dBm) Shows the average transmitted power of the cell within the
reporting period, measured in dBm.
Formula: C310444443/C310444444
Average Power (Watt) Shows the average transmitted power of the cell within the
reporting period, measured in Watts.
Formula: 10^((C310444443/C310444444)/10)
Best cell average HSDPA Shows the average number of HSDPA users in the best cell.
Users (Includes users that use only HSDPA as well as users that
use both HSDPA and HSUPA.)
Formula: SUM(C310030460 + C310030462)
340
Best cell average HSUPA Shows the average number of HSUPA users in the best cell.
Users (Includes users that use only HSUPA as well as users that
use both HSDPA and HSUPA.)
Formula: SUM(C310030461 + C310030462)
Cell average HSDPA Shows the average HSDPA throughput in the cell.
Throughput (Kbps)
Formula: (SUM(C310010158 + C310010159 +
C310010160)*8)/C312116604
Cell average HSUPA Shows the average HSUPA throughput in the cell.
Throughput (Kbps)
Formula: (SUM(C310010154 + C310010155 +
C310010156)*8)/C312116603
Cell average R99 DL Shows the average R99 downlink throughput, per user, in the
Throughput per user (Kbps) cell, dividing the sum of the transmitted R99 DL data by the
related transmission times.
Formula: (SUM(C310010289 + C310010290 + C310010291)
*8)/SUM(C311920812 + C311920813 + C311920814 +
C311920815 + C311920816 + C311920817 + C311920818 +
C311920819 + C311920828 + C311920829 + C311920830 +
C311920831 + C311920832 + C311920833 + C311920834 +
C311920835 + C311920844 + C311920845 + C311920846 +
C311920847 + C311920848 + C311920849 + C311920850 +
C311920851)
Cell average R99 UL Shows the average R99 uplink throughput, per user, in the
Throughput per user (Kbps) cell.
Formula: (SUM(C310010285 + C310010286 +
C310010287)*8)/SUM(C311920804 + C311920805 +
C311920806 + C311920807 + C311920808 + C311920809 +
C311920810 + C311920811 + C311920820 + C311920821 +
C311920822 + C311920823 + C311920824 + C311920825 +
C311920826 + C311920827 + C311920836 + C311920837 +
C311920838 + C311920839 + C311920840 + C311920841 +
C311920842 + C311920843)
Cell Inter-RAT CS Outgoing Shows the number of successful outgoing CS IRAT

Handover Success Rate (%) handovers as a percentage of the total number of attempted
outgoing CS inter-RAT handovers.
Formula: {SUM(C310352945 – C310352946 – C310352947
– C310352948 – C310352949 – C310352950 –
C310352951)/C310352945}*100 [%]
341
Cell Inter-RAT PS Incoming Shows the number of successful incoming PS IRAT

Handover Success Rate (%) handovers (GPRS to UMTS) divided by the total number of
attempted incoming PS Inter-RAT handovers.
Formula: {(SUM(C310352897 + C310352898 + C310352899
+ C310352900 + C310352901 + C310352902 + C310352903
+ C310352910 – SUM(C310352904 + C310352905 +
C310352906 + C310352907 +
C310352908))/SUM(C310352909 + C310352897 +
C310352898 + C310352899 + C310352900 + C310352901 +
C310352902 + C310352903)}*100 [%]
Cell Inter-RAT PS Outgoing Shows the number of successful outgoing PS IRAT

Handover Success Rate (%) handovers (number of attempted outgoing PS Inter-RAT
handovers minus the number of failed outgoing PS Inter-RAT
handovers due to various reasons, also including Cell
Change Order) divided by the total number of attempted
outgoing PS IRAT handovers.
Formula: {(SUM(C310352952 + C310352959) –
SUM(C310352953 + C310352954 + C310352955 +
C310352956 + C310352957 + C310352958 + C310352960 +
C310352961 + C310352962 + C310352963 +
C310352964))/SUM(C310352952 + C310352959)}*100 [%]
CS and Video RAB Setup Shows all successful RAB assignment setups in the CS
Success Rate (%) domain (including video telephony), divided by the sum of
attempted RAB assignment setups in the CS domain.
Formula: {SUM(C310100711 + C310100733 + C310100734
+ C310100735)/SUM(C310090252 + C310090274 +
C310090275 + C310090276)}*100 [%]
CS IRAT attempts per call rate Shows the number of outgoing CS IRAT attempts to the total
(%) number of Voice calls (CS RAB releases for Voice).
Formula: {C310352945/SUM(C310231185 + C310231186 +
C310231187 + C310231188 + C310231189 + C310231190 +
C310231191 + C310231192 + C310231193 + C310231194 +
C310231195 + C310231196 + C310231197 + C310231198 +
C310231199 + C310231200 + C310231201)}*100 [%]
CS RRC Setup and Access Shows the number of successful CS RRC connections
Completion Rate (%) divided by the number of CS RRC connection requests (total
attempts minus repeated attempts).
Formula: {SUM(C310080170 + C310080177 +
C310080185)/SUM(C310080001 + C310080008 +
C310080016 – C310080023 – C310080030 –
C310080038)}*100 [%]
342
Directed Retry Attempts Shows the number of DCH to HSDPA direct attempts — R99
cell to HSDPA cell.
Formula: C310514818
HS Drop Call Rate (%) Shows the sum of HSDPA and HSUPA abnormal RAB
releases for different Ue categories and traffic classes,
divided by the total number of RAB releases for HSDPA and
HSUPA. (RAB releases during setup and radio bearer
reconfiguration and due to timer expiries are excluded and
subtracted from the total sum of abnormal releases).
Formula: (SUM(C310251431 + C310251432 + C310251433
+ C310251434 + C310251435 + C310251436 + C310251437
+ C310251438 + C310251439 + C310251440 + C310251441
+ C310251442 + C310251443 + C310251444 + C310251445
+ C310251446 + C310251447 + C310251448 + C310251449
+ C310251450 + C310251451 + C310251452 + C310251453
+ C310251454 + C310251455 + C310251456 + C310251457
+ C310251458 + C310251459 + C310251460 + C310251461
+ C310251462 + C310251463 + C310251464 + C310251465
+ C310251466 + C310251467 + C310251468 + C310251469
+ C310251470 – C310286363 – C310286364 – C310286365
– C310286366 – C310286367 – C310286368 – C310286369
– C310286370 – C310286371 – C310286372 – C310286373
– C310286374 – C310286379) + SUM(C310251515 +
C310251516 + C310251517 + C310251518 + C310251519 +
C310251520 + C310251521 + C310251522 + C310251523 +
C310251524 + C310251525 + C310251526 + C310251527 +
C310251528 + C310251529 + C310251530 + C310251531 +
C310251532 + C310251533 + C310251534 + C310251535 +
C310251536 + C310251537 + C310251538 + C310251539 +
C310251540 + C310251541 + C310251542 – C310286381 –
C310286382 – C310286383 – C310286384 – C310286385 –
C310286386 – C310286387 – C310286388 – C310286389 –
C310286390 – C310286391 – C310286392 –
C310286397))/(SUM(C311866338 + C311866339 +
C311866340 + C311866341) + SUM(C311866352 +
C311866353 + C311866354 + C311866355))*100 [%]
Max Power (dBm) Shows the maximum value of the transmitted carrier power of
the cell within the reporting period, measured in dBm.
Formula: C310444441
Max Power (Watt) Shows maximum value of the transmitted carrier power of the
cell within the reporting period, measured in Watts.
Formula: 10^((C310444441)/10)
Maximum Cell Freq RTWP Shows the maximum power of totally received bandwidth for
(dBm) the cell.
Formula: C310444464
343
Min Power (dBm) Shows the minimum value of the transmitted carrier power of
the cell within the reporting period, measured in dBm.
Formula: C310446510
Min Power (Watt) Shows the minimum value of the transmitted carrier power of
the cell within the reporting period, measured in Watts.
Formula: 10^((C310446510)/10)
Primary Traffic Calls (Erlang) Shows all traffic where the call was served by the cell as
primary — meaning the traffic created on the best cell.
Formula: SUM(C310040001 + C310040002 + C310040003 +
C310040004 + C310040005 + C310040006 + C310040007 +
C310040008 + C310040009 + C310040010 +C310040011 +
C310040012 + C310040013 + C310040014 + C310040015 +
C310040016 + C310040017 + C310040018 + C310040019 +
C310040020 + C310040021 + C310040022 + C310040023 +
C310040024 +C310040025 + C310040026+C310040027 +
C310040028 + C310040029 + C310040030 + C310040031 +
C310040032 + C310040033 + C310040034 + C310040035 +
C310040036 + C310040037 + C310040038 + C310040039 +
C310040040 + C310040041 + C310040042 + C310040043 +
C310040044 + C310040045 + C310040046 + C310040047 +
C310040048 + C310040049 + C310040050 + C310040051 +
C310040052 + C310040053 + C310040054 + C310040055 +
C310040056 + C310040057 + C310040058 + C310040059 +
C310040060 + C310040061 + C310040062 + C310040063 +
C310040064 + C310040065 + C310040066 + C310040067 +
C310040068 + C310040069 + C310040070 + C310040071 +
C310040072 + C310040073 + C310040074 + C310040864 +
C310040865 + C310040866 + C310040867)/3600
PS and HS RAB Setup Shows all successful RAB assignment setups in the PS
Success Rate (%) domain, divided by the sum of attempted RAB assignment
setups in the PS domain.
Formula: {SUM(C310100736 + C310100739 + C310100752
+ C310100768)/SUM(C310090277 + C310090280 +
C310090293 + C310090309)}*100 [%]
344
PS Drop Call Rate (R99) (%) Shows all R99 PS RAB drops in relation to the total number
of R99 PS RAB releases.
Formula: {SUM(C310261648 + C310261649 + C310261650
+ C310261651 + C310261652 + C310261653 + C310261654
+ C310261655 + C310261656 + C310261657 + C310261658
+ C310261659 + C310261660 + C310261661 + C310261662
+ C310261663 + C310261664 + C310261665 + C310261666
+ C310261667 + C310261668 + C310261669 + C310261670
+ C310261671 + C310261672 + C310261673 + C310261674
+ C310261675 + C310261676 + C310261677 + C310261678
+ C310261679 + C310261680 + C310261681 + C310261682
+ C310261683 + C310261684 + C310261685 – C310286565
– C310286566 – C310286567 – C310286568 – C310286569
– C310286570 – C310286571 – C310286572 – C310286573
– C310286574 –C310286575 – C310286576 –
C310286581)} / {SUM(C311866917 + C311866919 +
C311866920 + C311866921 + C311866922 + C311866923 +
C311866924 + C311866925 + C311866926 + C311866927 +
C311866928 + C311866930 + C311866931 + C311866932 +
C311866933 + C311866934 + C311866935 + C311866936 +
C311866937 + C311866938 + C311866939 + C311866940 +
C311866941 + C311866942 + C311866944 + C311866945 +
C311866946 + C311866947 + C311866948 + C311866949 +
C311866950 + C311866951 + C311866952 + C311866953 +
C311866954 + C311866955 + C311866956)}*100 [%]
PS RRC Setup and Access Shows all successful PS RRC connection setups divided by
Completion Rate (%) the number of PS RRC connection requests (total attempts
minus repeated attempts).
Formula: {SUM(C310080171 + C310080172 + C310080173
+ C310080175 + C310080176 + C310080178 + C310080179
+ C310080180 + C310080181 + C310080182) /
(SUM(C310080002 + C310080003 + C310080004 +
C310080009 + C310080010 + C310080011 + C310080006 +
C310080007 + C310080012 + C310080013) –
SUM(C310080024 + C310080025 + C310080026 +
C310080031 + C310080032 + C310080033 + C310080028 +
C310080029 + C310080034 + C310080035))}*100 [%]
RAB Setup Blocking Rate (CS Shows call blocking due to Call Admission Control for all
& PS) (%) bearers. It specifically includes all failed RAB assignment
setups due to congestion divided by the total number of
attempted RAB assignment setups.
Formula: {SUM(C310110334 + C310110351 + C310110359
+ C310110365 + C310110391 + C310110408 + C310110416
+ C310110422)/ SUM(C310090252 + C310090274 +
C310090275 + C310090276 + C310090277 + C310090280 +
C310090293 + C310090309)}*100 [%]
345
Soft Handover Success Rate Shows all soft and softer handovers, Intra/Inter cell, Node B
(%) to Node B counting all attempted active set updates to add or
delete a cell, reduced by the failed active set updates due to
various reasons.
Formula: {(SUM(C310322216 + C310322217 + C310322218
+ C310322232 + C310322233 + C310322234) -
SUM(C310322222 + C310322223 + C310322224 +
C310322225 + C310322226 + C310322227 + C310322230 +
C310322231 + C310322235 + C310322236 + C310322237 +
C310322238 + C310322239 + C310322240 + C310322243 +
C310322244))/ SUM(C310322216 + C310322217 +
C310322218 + C310322232 + C310322233 +
C310322234)}*100 [%]
Successful Directed Retry Shows the number of successful directed retry attempts out of
Attempts the total number of attempts, including failed attempts.
Formula: SUM(C310514818 – C310514819 – C310514820 –
C310514821 – C310514822 – C310514823 – C310514824 –
C310514825 – C310514826 C310514827 – C310514828)
Total CS Traffic (Erlang) Shows the total CS traffic volume transmitted in the cell. It
summarizes the holding times of the different CS RABs
during the measured time interval.
Formula: SUM(C310040001 + C310040002 + C310040003 +
C310040004 + C310040005 + C310040006 + C310040007 +
C310040008 + C310040009 + C310040010 + C310040011 +
C310040012 + C310040013 + C310040014 + C310040015 +
C310040016 + C310040017 + C310040018 + C310040019 +
C310040020 + C310040021 + C310040022 + C310040075 +
C310040076 + C310040077 + C310040078 + C310040079 +
C310040080 + C310040081 + C310040082 + C310040083 +
C310040084 + C310040085 + C310040086 + C310040087 +
C310040088 + C310040089 + C310040090 + C310040091 +
C310040092 + C310040093 + C310040094 + C310040095 +
C310040096)/3600
Total Drops (all RABs) count Shows the number of abnormally terminated calls,
independent of the RAB.
Formula: sumN({C310231162}, {C310231163},
{C310231164}, {C310231165}, {C310231166},
{C310231167}, {C310231168}, {C310231169},
{C310231170}, {C310231171}, {C310231172},
{C310231173}, {C310231174}, {C310231175},
{C310231176}, {C310231177}, {C310231178},
{C310261648}, {C310261649}, {C310261650},
{C310261651}, {C310261652}, {C310261653},
{C310261654}, {C310261655}, {C310261656},
{C310261657}, {C310261658}, {C310261659},
{C310261660}, {C310261661}, {C310261662},
{C310261663}, {C310261664}, {C310261665},
346

{C310261666}, {C310261667}, {C310261668},
{C310261669}, {C310261670}, {C310261671},
{C310261672}, {C310261673}, {C310261674},
{C310261675}, {C310261676}, {C310261677},
{C310261678}, {C310261679}, {C310261680},
{C310261681}, {C310261682}, {C310261683},
{C310261684}, {C310261685}, – {C310286565}, –
{C310286566}, – {C310286567}, – {C310286568}, –
{C310286569}, – {C310286570}, – {C310286571}, –
{C310286572}, – {C310286573}, – {C310286574},–
{C310286575}, – {C310286576}, – {C310286581},
{C310251431}, {C310251432}, {C310251433},
{C310251434}, {C310251435}, {C310251436},
{C310251437}, {C310251438}, {C310251439},
{C310251440}, {C310251441}, {C310251442},
{C310251443}, {C310251444}, {C310251445},
{C310251446}, {C310251447}, {C310251448},
{C310251449}, {C310251450}, {C310251451},
{C310251452}, {C310251453}, {C310251454},
{C310251455}, {C310251456}, {C310251457},
{C310251458}, {C310251459}, {C310251460},
{C310251461}, {C310251462}, {C310251463},
{C310251464}, {C310251465}, {C310251466},
{C310251467}, {C310251468}, {C310251469},
{C310251470}, – {C310286363}, – {C310286364}, –
{C310286365}, – {C310286366}, – {C310286367}, –
{C310286368}, – {C310286369} , – {C310286370}, –
{C310286371}, – {C310286372}, – {C310286373}, –
{C310286374}, – {C310286379}, {C310251515},
{C310251516}, {C310251517}, {C310251518},
{C310251519}, {C310251520}, {C310251521},
{C310251522}, {C310251523}, {C310251524},
{C310251525}, {C310251526}, {C310251527},
{C310251528}, {C310251529}, {C310251530},
{C310251531},{C310251532}, {C310251533}, {C310251534},
{C310251535}, {C310251536}, {C310251537},
{C310251538}, {C310251539}, {C310251540},
{C310251541}, {C310251542}, – {C310286381}, –
{C310286382}, – {C310286383}, – {C310286384}, –
{C310286385}, – {C310286386}, – {C310286387}, –
{C310286388}, – {C310286389}, – {C310286390}, –
{C310286391}, – {C310286392}, – {C310286397})
Total HSDPA Traffic (MB) Shows the total HSDPA data volume transmitted in the cell.
Formula: SUM(C310010157 + C310010158 + C310010159 +
C310010160)/1024
Total HSUPA Traffic (MB) Shows the total HSUPA data volume transmitted in the cell.
Formula: SUM(C310010153 + C310010154 + C310010155 +
C310010156)/1024
347
Total PS R99 DL Traffic (MB) Shows the total PS R99 downlink data volume transmitted in
the cell.
Formula: SUM(C310010194 + C310010195 + C310010196 +
C310010197 + C310010198 + C310010199 + C310010200 +
C310010201 + C310010209 + C310010210 + C310010211 +
C310010212 + C310010213 + C310010214 + C310010215 +
C310010216 + C310010224 + C310010225 + C310010226 +
C310010227 + C310010228 + C310010229 + C310010230 +
C310010231)/1024
Total PS R99 UL Traffic (MB) Shows the total PS R99 uplink data volume transmitted in the
cell.
Formula: SUM(C310010188 + C310010189 + C310010190 +
C310010191 + C310010192 + C310010193 + C310010202 +
C310010203 + C310010204 + C310010205 + C310010206 +
C310010207 + C310010208 + C310010217 + C310010218 +
C310010219 + C310010220 + C310010221 + C310010222 +
C310010223)/1024
Total PS Traffic (MB) Shows the total PS data volume transmitted in the cell,
including both R99 traffic and HSPA traffic. The separate
counters are in kB.
Formula: (SUM(C310010157 + C310010158 + C310010159
+ C310010160 + C310010153 + C310010154 + C310010155
+ C310010156)/1024) + (SUM(C310010188 + C310010189 +
C310010190 + C310010191 + C310010192 + C310010193 +
C310010202 + C310010203 + C310010204 + C310010205 +
C310010206 + C310010207 + C310010208 + C310010217 +
C310010218 + C310010219 + C310010220 + C310010221 +
C310010222 + C310010223 + C310010194 + C310010195 +
C310010196 + C310010197 + C310010198 + C310010199 +
C310010200 + C310010201 + C310010209 + C310010210 +
C310010211 + C310010212 + C310010213 + C310010214 +
C310010215 + C310010216 + C310010224 + C310010225 +
C310010226 + C310010227 + C310010228 + C310010229 +
C310010230 + C310010231)/1024)
Total RAB Success Shows the total number of successful RAB establishments in
a cell. The main purpose of this KPI is to normalize the Traffic
maps.
Formula: SUM(C310100711 + C310100733 + C310100734 +
C310100735 + C310100736 + C310100739 + C310100752 +
C310100768)
Total Video Traffic (Erlang) Shows the total video traffic volume transmitted in the cell.
Formula: SUM(C310040018 + C310040092)/3600
348
Total Voice Traffic (Erlang) Shows the total CS voice traffic volume transmitted in the cell.
Formula: SUM(C310040001 + C310040002 + C310040003 +
C310040004 + C310040005 + C310040006 + C310040007 +
C310040008 + C310040009 + C310040010 + C310040011 +
C310040012 + C310040013 + C310040014 + C310040015 +
C310040016 + C310040017 + C310040075 + C310040076 +
C310040077 + C310040078 + C310040079 + C310040080 +
C310040081 + C310040082 + C310040083 + C310040084 +
C310040085 + C310040086 + C310040087 + C310040088 +
C310040089 + C310040090 + C310040091)/3600
Traffic (Erlang) Shows the amount of traffic in the cell.
Uplink Noise Rise (dB) Shows the increase in the wideband interference level over
the thermal noise in the base station reception. It is calculated
by subtracting the minimum RTWP from the average RTWP.
The minimum RTWP should be the minimum value for an
hour during a day, if counters for multiple hours are available.
If the counters are not in 1-hour granularity, but in 15 or 30
minutes, the values must be converted into Watt, averaged
for the hour, and converted back to dBm.
Formula: [(C310444466/C310444467) – 112] – C310446512
Video Drop Call Rate (%) Shows the number of abnormal RAB releases for the CS
64k/64k Bearer (Videotelephony) as a percentage of the total
number of RAB releases for the CS 64k/64k Bearer.
Formula: SUM(C310231180)/SUM(C310231203)*100 [%]
Voice Drop Call Rate (%) Shows all CS voice RAB drops (with respect to the total
number of calls ending in 3G), counting only the drops on the
best serving cell and including all AMR drops.
Formula: {SUM(C310231162 + C310231163 + C310231164
+ C310231165 + C310231166 + C310231167 + C310231168
+ C310231169 + C310231170 + C310231171 + C310231172
+ C310231173 + C310231174 + C310231175 + C310231176
+ C310231177 + C310231178)} / {SUM(C310231185 +
C310231186 + C310231187 + C310231188 + C310231189 +
C310231190 + C310231191 + C310231192 + C310231193 +
C310231194 + C310231195 + C310231196 + C310231197 +
C310231198 + C310231199 + C310231200 +
C310231201)}*100 [%]
349
ZTE LTE KPIs

The following table lists the ZTE LTE KPIs on which you can base the network analysis.
Average Active User Number (count) Shows the average number of UEs that have DTCH
data queued on the downlink and uplink (100ms
sampling time).
Formula: AVG(C373384349)
Average DL Transmit Power Per Cell Shows the average downlink transmission power of the
(mW) cell. The eNodeB collects the DL power at each
sampling time (1ms sampling period) and calculates the
average among the sampling points.
Average SINR (dB) Shows the average uplink SINR, weighted with the
PRB allocation percentage.
Call Drop Rate (VoIP) (%) Shows the VoIP ERAB abnormal release rate.
Formula: SUM(C373210372 + C373210382 +
C373210432 + C373210442 + C373210502
+C373210512 + C373505345) / SUM(C373210200 +
C373210254 + C373210452 +C373240809 +
C373546248)
Call Setup Success Rate (%) Shows the call setup success rate of all services
including the VoIP service. It is calculated based on
multiplying the KPI of RRC Setup Success Rate
(Service) and the KPI of ERAB Setup Success Rate
(All).
Formula: [SUM(C373200000+ C373200008+
C373200012+ C373200016) / SUM(C373200000 +
C373200001 + C373200002 + C373200003 +
C373200008 + C373200009 + C373200010 +
C373200011 + C373200012 + C373200013 +
C373200014 + C373200015 +C373200016 +
C373200017 + C373200018 + C373200019)] * [
SUM(C373505473 + C373505481) / SUM(C373505473
+ C373505474 + C373505475 +C373505476 +
C373505477 + C373505478 + C373505479 +
C373505481 +C373505482 + C373505483 +
C373505484 + C373505485 + C373505486 +
C373505487)]
Cell Availability Rate (%) Shows the percentage of time a cell is available.
Formula: SUM(C373230700) / (Gr*NO) where Gr*NO
is the measurement period (e.g. 3600s for 1h meas)
350
Cell Downlink Average Aggregated Shows the cell aggregated throughput on the MAC
Throughput (Mbps) layer on the downlink, i.e. the ratio of successfully
received data bits to the number of TTIs with DL data
transmission (retransmissions are excluded).
Formula: SUM(C373343726 + C373343727)*1000 /
SUM(C373343730)
Cell Uplink Average Aggregated Shows the cell aggregated throughput on the MAC
Throughput (Mbps) layer on the uplink, i.e. the ratio of successfully
received data bits to the number of TTIs with UL data
transmission (retransmissions are excluded).
Formula: SUM(C373343728 + C373343729)*1000 /
SUM(C373343731)
CSFB Success Rate (%) Shows the relation between the successful handover
preparations for CSFB from the E-UTRAN to inter-RAT
networks in relation to the number of handover
preparation attempts for CSFB.
Formula: SUM(C373485141)/ SUM(C373485133)
DLAveragePDCPThroughput (kbps) Shows the overall average downlink PDCP throughput.

Formula: AVG(C373343602)*1000
DLAveragePDCPThroughput_QCI_1...9 Shows the average downlink PDCP throughput for

(kbps) each QCI.
Formula: QCI_1 = AVG(C373343608)*1000
Formula: QCI_2 = AVG(C373343614)*1000
Formula: QCI_3 = AVG(C373343620)*1000
Formula: QCI_4 = AVG(C373343626)*1000
Formula: QCI_5 = AVG(C373343632)*1000
Formula: QCI_6 = AVG(C373343638)*1000
Formula: QCI_7 = AVG(C373343644)*1000
Formula: QCI_8 = AVG(C373343650)*1000
Formula: QCI_9 = AVG(C373343656)*1000
351
DLTrafficVolume_QCI_1...9 (Kb) Shows the downlink traffic volume in a cell, measured

at the PDCP layer for each QCI.
Formula: QCI_1 = SUM(C373343608)*1024*3600
Formula: QCI_2 = SUM(C373343614)*1024*3600
Formula: QCI_3 = SUM(C373343620)*1024*3600
Formula: QCI_4 = SUM(C373343626)*1024*3600
Formula: QCI_5 = SUM(C373343632)*1024*3600
Formula: QCI_6 = SUM(C373343638)*1024*3600
Formula: QCI_7 = SUM(C373343644)*1024*3600
Formula: QCI_8 = SUM(C373343650)*1024*3600
Formula: QCI_9 = SUM(C373343656)*1024*3600
E-RAB Setup Success Rate (All) (%) Shows the E-RAB Setup Success Rate of all services,
including the VoIP service.
Formula: SUM(C373505473 + C373505481) /
SUM(C373505473 + C373505474 + C373505475 +
C373505476 + C373505477 + C373505478 +
C373505479 + C373505481 + C373505482 +
C373505483 + C373505484 + C373505485 +
C373505486 + C373505487)
E-RAB Setup Success Rate (VOIP) (%) Shows the E-RAB Setup Success Rate for VoIP
services.
Formula: SUM(C373210200 + C373210254) /
SUM(C373210200 + C373210201 + C373210202 +
C373505375 + C373210203 + C373210204 +
C373210205 + C373210254 + C373210255 +
C373210256 + C373505384 + C373210257 +
C373210258 + C373210259)
Inter-Frequency Handover In Success Shows the inter/intra-eNodeB inter-frequency incoming

Rate (%) handover success rate.
Formula: SUM(C373281884 + C373292184 +
C373302484) / SUM(C373281840 + C373281841 +
C373281842 + C373281843 + C373292190 +
C373302440 + C373302441 + C373302442 +
C373302443 + C373302489)
352
Inter-Frequency Handover Out Success Shows the inter/intra-eNodeB inter-frequency outgoing

Formula: SUM(C373281880 + C373292180 +
C373302480) / SUM(C373281800 + C373281801 +
C373281802 + C373281803 + C373281888 +
C373292100 + C373292101 + C373292102 +
C373292103 + C373292104 + C373292189 +
C373302400 + C373302401 + C373302402 +
C373302403 + C373302404 + C373302488)
Inter-RAT Handover Out Success Rate Shows the inter-eNodeB inter-RAT outgoing handover
(LTE to CDMA2000) (%) success rate (LTE to CDMA2000).
Formula: SUM(C373323012) / SUM(C373323012 +
C373323013 + C373323014 + C373323015)
(LTE to GSM) (%) success rate (LTE to GSM).
C373333313 + C373333314 + C373333315)
(LTE to WCDMA) (%) success rate (LTE to WCDMA).
C373312713 + C373312714 + C373312715)
Intra-Frequency Handover In Success Shows the inter/intra-eNodeB intra-frequency incoming

Formula: SUM(C373250984 + C373261284 +
C373271584) / SUM(C373250940 + C373250941 +
C373250942 + C373250943 + C373261284 +
C373261240 + C373261241 + C373261242 +
C373261243 + C373261290 + C373271540 +
C373271541 + C373271542 + C373271543 +
C373271589)
Intra-Frequency Handover Out Success Shows the inter/intra-eNodeB intra-frequency outgoing

Formula: SUM(C373250980 + C373261280 +
C373271580)/ SUM(C373250900 + C373250901 +
C373250902 + C373250903 +C373250988 +
C373261200 + C373261201 + C373261202 +
C373261203 + C373261204 + C373261289 +
C373271500 + C373271501 + C373271502 +
C373271503 + C373271504 + C373271588)
353
Maximum Active User Number (count) Shows the maximum number of UEs that have DTCH
data queued on the downlink and uplink (100ms
sampling time).
Formula: MAX(C373384348)
Maximum Cell Downlink PDCP Shows the maximum cell throughput of PDCP PDUs on
Throughput (kbps) the downlink each second.
Formula: MAX(C373343600)*1000
Maximum Cell Uplink PDCP Throughput Shows the maximum cell throughput of PDCP PDUs on
(kbps) the uplink each second.
Formula: MAX(C373343603)*1000
Maximum Timing Advance Shows the highest timing advance value (distance from
the UE to the eNodeB) reported by the eNodeB within
the reporting period.
Formula: C373556414
Message Volume (MBytes) Shows the Transport Blocks (TBs) transmitted by the
eNodeB to the UE in the downlink. Retransmissions are
not taken into consideration.
Formula: C373343726+C373343727
PDSCH Physical Resource Block Shows the average cell downlink PRB usage for
Utilization Rate (%) PDSCH, in percentage of PRBs.
Formula: SUM(C373424602) / SUM(C373424603)
PUSCH Physical Resource Block Shows the average cell uplink PRB usage for PUSCH,
Utilization Rate (%) in percentage of PRBs.
Formula: SUM(C373424600) / SUM(C373424601)
RRC Drop Rate (%) Shows the probability for an end-user to lose the RRC
Connection. It is the relation of the number of RRC
connections released abnormally by the eNodeB
divided by the number of successful RRC
establishments.
Formula: SUM(C373200022 + C373200023 +
C373200024 + C373200049 + C373200051
+C373200052 + C373200053) / SUM(C373200000 +
C373200004 + C373200008 +C373200012 +
C373200016 + C373200031 + C373200060 +
C373200066 +C373200072 + C373250984 +
C373261284 + C373271584 + C373281884
+C373292184 + C373302484 + C373312704 +
C373323004 + C373333304)
354
RRC Setup Success Rate (Service) (%) Shows the probability for an end-user to be provided
with an RRC connection at request. The RRC Setup
Success Rate (Service) includes all RRC connection
setup procedures triggered by service-related causes,
specifically emergency access, high priority access,
mobile terminating access and mobile originating data.
Formula: SUM(C373200000 + C373200008 +
C373200012 + C373200016) / SUM(C373200000 +
C373200001 + C373200002 + C373200003 +
C373200008 + C373200009 + C373200010 +
C373200011 + C373200012 + C373200013 +
C373200014 + C373200015 +C373200016 +
C373200017 + C373200018 + C373200019)
RRC Setup Success Rate (Signaling) Shows the probability for an end-user to be provided
(%) with an RRC connection at request. The RRC Setup
Success Rate (Signaling) includes the RRC Connection
Setups with establishment cause "Mobile originating
Signaling".
C373200005 + C373200006 + C373200007)
Service Drop Rate (All) (%) Shows the abnormal release of the E-RAB at the
eNodeB, for all QCIs. (Similar to Call Drop Rate (VoIP),
but for all CQIs.)
Formula: SUM(C373210381 + C373210391 +
C373210441 + C373210451 + C373210511 +
C373210521 + C373505354) / SUM(C373210461 +
C373240828 + C373505473 + C373505481 +
C373546257)
TA Report Message Count Shows the total number of TA report messages sent to
the UE.
Total DLTrafficVolume (Kb) Shows the downlink traffic volume in a cell, which is
measured at the PDCP layer.
Formula: SUM(C373343602)*1024*3600
Total ULTrafficVolume (Kb) Shows the uplink traffic volume in a cell, which is
measured at the PDCP layer.
Formula: SUM(C373343605)*1024*3600
Traffic (Erlang) Shows the number of PRBs (Physical Resource

Blocks) that were used in the downlink relative to the
number of available PRBs, which represents the traffic
in Erlang.
Formula: C373424602/C373424603
355
ULAveragePDCPThroughput (kbps) Shows the overall average uplink PDCP throughput.

Formula: AVG (C373343605)*1000
ULAveragePDCPThroughput_QCI_1...9 Shows the average uplink PDCP throughput for each

(kbps) CQI.
Formula: QCI_1 = AVG(C373343611)*1000
Formula: QCI_2 = AVG (C373343617)*1000
Formula: QCI_3 = AVG (C373343623)*1000
Formula: QCI_4 = AVG (C373343629)*1000
Formula: QCI_5 = AVG (C373343635)*1000
Formula: QCI_6 = AVG (C373343641)*1000
Formula: QCI_7 = AVG (C373343647)*1000
Formula: QCI_8 = AVG (C373343653)*1000
Formula: QCI_9 = AVG (C373343659)*1000
ULTrafficVolume_QCI_1...9 (Kb) Shows the uplink traffic volume in a cell, measured at

the PDCP layer, for each QCI.
Formula: QCI_1 = SUM(C373343611)*1024*3600
Formula: QCI_2 = SUM(C373343617)*1024*3600
Formula: QCI_3 = SUM(C373343623)*1024*3600
Formula: QCI_4 = SUM(C373343629)*1024*3600
Formula: QCI_5 = SUM(C373343635)*1024*3600
Formula: QCI_6 = SUM(C373343641)*1024*3600
Formula: QCI_7 = SUM(C373343647)*1024*3600
Formula: QCI_8 = SUM(C373343653)*1024*3600
Formula: QCI_9 = SUM(C373343659)*1024*3600
356
Positioning-based Maps
Mentor uses measurements and special algorithms to generate positioning-based map layers
that can be displayed in Mentor and in Google Earth. Positioning-based maps can be created
during the network analysis, or generated at any time from the Network menu, toolbar, or by
right-clicking an area or sector selection.
You can create and view these maps only if:
 Your license supports positioning-based maps and the model on your client includes
positioning.
This enables you to view binned or sector-level maps for the busy hour only, as well
as event maps (for abnormal releases such as drop calls, access failure, and data
disconnection) for all hours included in your model.
-OR-
 Your license enables you to view rich data from the Call Database, and you are
connected to the Mentor server.
Using rich data, binned maps can be created for any hours of any days saved in the
database, in near real time. These maps can be filtered according to additional filters,
such as mobile IMEIs or IMSIs, networks, terminal types, and release causes.
 Your license supports working with the model on the server.
Currently Mentor supports the following maps for the entire network, or a specific area or
sector selection:
 KPI Maps
Note: KPI maps can be displayed only for the network or a sector selection, not for
an area selection.
 Call Trace–based Maps:
o Performance Maps
o Drop Maps
o Traffic Maps
o Server and Polluter Maps
o Arc Maps
Note: Arc maps can be displayed only for the network or a sector selection, not
for an area selection. (UMTS only)
o Combined Maps
o GSM Maps:
 Performance Maps
 Best Server Maps
 Traffic Maps
 Call Trace–based Event Maps:
o Virtual Drive Test Maps
o Mobile Drop Maps
o Access Failure Maps
o Mobile IRAT Maps
o CSFB Maps
o Additional Maps
o GSM Virtual Drive Test Maps
357
Displaying KPI Maps

You can generate map layers based on selected KPIs, showing aggregated data for a time
resolution ranging from 1 hour up to all the dates included in the model. Each selected KPI
will be saved as a separate layer in a specified folder under the GIS layer in the Layers pane.
These layers can be displayed in the map area and in Google Earth. You can also view all the
KPIs for each of the sectors in the selection in the Detailed Table.
Note: The KPI map is similar to the KPI layer created in the Analysis wizard, but is supported
at a sector-level resolution only.
To display a KPI map layer

1. On the Network menu, click Show KPIs to show selected KPIs in the network or in a
sector selection.
-OR-
On the toolbar, click .
-OR-
Right-click a sector selection, and on the shortcut menu, click Show KPIs.
The Show KPIs dialog box is displayed, showing the available KPIs in the All KPIs
pane on the left.
358
Note: The KPIs vary according to the network vendor.
By default, the KPIs are sorted by group, but you can display them alphabetically, if
required.
o Ericsson UMTS KPIs
o Ericsson LTE KPIs
o Huawei UMTS KPIs
o Huawei LTE KPIs
o NSN UMTS KPIs
o ZTE UMTS KPIs
o Click to display the KPIs alphabetically. Click the column headers to sort the
KPIs according to Name or Group.
o Click to display the KPIs according to groups.

2. Click the button next to the group of KPIs you want to use. The group is expanded
to show the available KPIs.
3. Select one or more KPIs and then click to move the selected KPIs to the
Selected KPIs pane on the right.
Tip: Double-click required KPIs to move them to the Selected KPIs pane.
dates and the time range that are used by clicking the browse button .
5. Select the Save as Layer check box to save the temporary layers to your disk. By
default, the layers are saved to a default KPIs folder under the GIS category, but you
can change the name of the folder if required.
Note: If you do not choose to save the layers, they cannot be displayed in the map
area, only in the Detailed Table.
6. Click OK. A progress bar is displayed during the KPI map creation, and while the
layers are being saved. Each selected KPI layer is displayed in the Layers pane, in
the default KPIs folder under the GIS category.
359
A dialog box is displayed once the map has been created.
o Click Details to view any warnings generated during the map creation. If there are
no warnings, the Details button is not enabled.
o Click Detailed Table to view all the selected KPIs for each sector in the selection
in the Detailed Table.
o Click Close to close the dialog box.
7. To view the layer in Google Earth, right-click the layer and then select Show Layer in
Google Earth.
Displaying Performance Maps

If your model contains positioning, you can display selected performance layers based on the
busy-hour call-trace data. For example, you can display the areas with the most pilot pollution
or Ec/Io coverage for the busy hour.
If you have a license for the call database, you can display these layers for all hours, and if
required for specific mobiles, terminal models, and release causes.
Note: You must be connected to the Mentor server in order to access the data from the call
database.
If your selection contains both LTE and UMTS sectors, you will be prompted to select whether
to create the map for UMTS, LTE, or both technologies.
Once the map layer has been created, you can display it in the Detailed Table, or in Google
Earth.
To display a performance map layer

1. On the Network menu, click Show Maps and then Performance to show the
performance of the network or an area or sector selection.
-OR-
Right-click a sector selection, and on the shortcut menu, click Show Maps and then
Performance.
technology. You can display the map for UMTS, LTE, or both technologies.
360
The Show Performance Map dialog box is displayed.
361
3. In the Map type field, select the type of performance map to display. By default, the
map will be displayed as a binned map, but if required, you can select the
Sector-level map option to display the map aggregated to cell level.
You can select one of the following map types, depending on the data source
selected, and the network technology:
UMTS selection:
o Downlink Throughput: Displays the RLC throughput on the downlink.
o Downlink Throughput Peak: Displays the highest RLC throughput on the
downlink.
o Downlink Volume: Displays the volume of RLC data, in KB, received by the UE.
o Ec/Io Best Server: Displays the value of the average best server Ec/Io
measurements, per bin. Displays only samples in which the best server is in the
selection. The best Ec/Io value is taken from each sample, and the average of all
the samples is displayed for each bin.
o Ec/Io Coverage: Displays samples with at least one leg in the selection. For each
sample, the best Ec/Io values of the legs in the selection are used, even if they
are lower than the sample's best Ec/Io value. The average of all the samples is
displayed for each bin.
o Ec/Io Coverage Peak: Displays the highest Ec/Io reported per bin. If only 1 sector
is selected, the map will show the peak Ec/Io for each bin in the selected sector. If
more than 1 sector is selected, Mentor will consider the peak Ec/Io out of all the
legs that are part of the selection.
o IRAT Density: Displays the concentration of IRAT events in the selection.
o Number of Polluting Pilots: Displays only samples in which the best server is in
the selection. The number of polluting pilots is taken from each sample, and the
average of all the samples is displayed for each bin. (The difference (in dB) from
the best serving pilot’s Ec/Io at or below which a pilot is considered a polluter is
based on the value of the POLLUTING_PILOT_THRESHOLD parameter, in the
Advanced Network Properties.)
Note: The number displayed does not include the best server.
o Pilot Dominance: Displays the percentage of samples in the bin that have pilot
dominance. Mentor checks all samples associated with the bin, and classifies
samples as having pilot dominance if there is a difference of at least 6dB between
the strongest and second strongest legs in the active set. (This value is defined in
the PILOT_DOMINANCE_DELTA_UMTS parameter, in the Advanced Network
Properties.)
o Pilot Pollution: Displays the percentage of samples in the bin that have pilot
pollution. Mentor checks all measurements that are associated with the bin, and
have at least three legs in the active set, and classifies measurements as polluted
if the Ec/Io level of the best leg is less than -10 dB.
o RRC Setup Time: Displays the average RRC setup time.
o RSCP Best Server: Displays only samples in which the best server is in the
selection. The best RSCP value is taken from each sample, and the average of all
the samples is displayed for each bin.
o RSCP Coverage: Displays samples with at least one leg in the selection. For
each sample, the best RSCP values of the legs in the selection are used, even if
they are lower than the sample's best RSCP value. The average of all the
samples is displayed for each bin.
362
o RSCP Coverage Peak: Displays the maximum RSCP value for the strongest leg
in each record. If only one sector is selected, the map will display the peak RSCP
of each bin in the selected sector, for any leg in which the sector appears. If more
than 1 sector is selected, for each sample Mentor considers the peak RSCP
reported for all the legs that are part of the selection.
o Soft HO Factor: Displays the average potential number of serving BTSs per bin,
meaning the number of NodeBs in the active set as well as the ones that should
have been added to the active set, based on the 1a threshold.
o UE TX Power: Displays only samples in which the best server is in the selection.
The UE Tx power value is taken from each sample, and the average of all the
o Uplink Throughput: Displays the RLC throughput on the uplink in Kbps.
o Uplink Throughput Peak: Displays the highest RLC throughput on the uplink.
o Uplink Volume: Displays the volume of RLC data, in KB, transferred from the UE.
LTE selection:
o CQI Index: Displays the reported CQI index value per bin for all positioned
throughput events. The weighted average CQI index value is calculated using the
weight given for each CQI KPI event. For example, if there are 2 throughput
records per bin and one has a higher duration, it will have a higher weighted
average.
o Downlink Throughput: Displays the RLC throughput in the downlink.
o Downlink Volume: Displays the volume of RLC data, in KB, received by the UE.
o IRAT Density: Displays the number of IRAT events.
o Overlapping: Displays the percentage of samples in the bin that are overlapping,
based on several advanced properties. By default, a sample is considered
overlapping if the power of the serving cell is above -110 dBm, and it has at least
three candidates with a difference of up to 6 dB from the serving cell.
o PHR: Displays the power remaining for the UE after allocation of the uplink power.
o PUSCH UL SINR: Displays the average value of the PUSCH SINR in the uplink.
o RRC Setup Time: Displays the average RRC setup time.
o RSRP Best Server: Displays the RSRP value per power record for the best
server.
o RSRP Best Server Peak: Displays the best RSRP value per power record for the
best server.
o RSRP Coverage: Displays samples with at least one leg in the selection. For
each sample, the best RSRP values of the legs in the selection are used, even if
they are lower than the sample's best RSRP value. The average of all the
o RSRQ Best Server: Displays the quality value per power record for the best
server.
o RSRQ Best Server Peak: Displays the best quality value per power record for the
best server.
o RSRQ Coverage: Displays samples with at least one leg in the selection. For
each sample, the best RSRQ values of the legs in the selection are used, even if
they are lower than the sample's best RSRQ value. The average of all the
o UL Power Restriction Rate: Displays the rate of power restriction situations per
bin, reported by the UE in the uplink.
363
o Uplink Throughput: Displays the RLC throughput on the uplink in Kbps.

o Uplink Volume: Displays the volume of RLC data, in KB, transferred from the UE.
o User Downlink Throughput: Displays the actual user downlink throughput.
(Ericsson only)
o User Uplink Throughput: Displays the actual user uplink throughput. (Ericsson
only)
Multi RAT selection:

o Best Technology (Throughput): Displays the technology of the better sector,
based on the average throughput.
o Downlink Volume: Displays the sum of MB per bin for both LTE and UMTS, sent
on the downlink and received by the UE.
o LTE Volume Ratio: Displays the ratio between the LTE volume downlink per bin
and the total downlink volume for both LTE and UMTS for the selected period and
time selection.
o Client Model: Busy-hour data will be taken from the network model on your client.
o Rich Data: Rich data will be taken from the call database, via the Mentor server.
7. Click OK. A progress bar is displayed during the performance map creation, and
while the layer is being saved and loaded. The layer is displayed in the Layers pane,
under the GIS category, and on the map.
364
The following example shows the Pilot Dominance map of a cluster.
The following map shows the Pilot Pollution in the area between the two sites.
Usually there is no pilot pollution close to the sector, as shown by the blue bins, but in
the border between the sectors, a higher rate of pilot pollution exists, as can be seen
by the red bins.
Google Earth.
365
Displaying Drop Maps (UMTS and LTE)

If your model contains positioning, you can display a layer showing the geographical
distribution of the average number of drop calls or any abnormal disconnection (data
session), per bin, for the busy hour.
If you have a license for the call database, you can display this layer for all hours, and if
required, for selected mobiles, terminal models, or release causes.
database.
If your selection contains both LTE and UMTS sectors, you will be prompted to select the
technology to use.
Earth.
To display a drop map layer

1. On the Network menu, click Show Maps and then Drop to show the distribution of
dropped calls or disconnected data sessions in the network or in an area or sector
selection.
-OR-
Drop.
technology.
366
The Show Drop Map dialog box is displayed.
3. In the Map type field, select the type of drop map to display. By default, the map will
be displayed as a binned map, but you can select the Sector-level map option to
display the map aggregated to cell level, if required.
o Rich Data: Rich data will be taken from the call database, via the Mentor server.
367
7. Click OK. A progress bar is displayed during the map creation, and while the layer is
category, and on the map.
Google Earth.
Displaying Traffic Maps

If your model contains positioning, you can display the distribution of the busy-hour traffic
layer for the best server.
If you have a license for the call database, you can display the distribution of the total traffic
for the best server for all hours, for selected mobiles, terminal models, or release causes.
database.
technology to use.
Earth.
368
To display a traffic map layer

1. On the Network menu, click Show Maps and then Traffic to show the traffic
distribution for the best server in the network or in an area or sector selection.
-OR-
Traffic.
technology.
The Show Traffic Map dialog box is displayed.
369
3. In the Map type field, select the type of traffic map to display. By default, the map will
be displayed as a binned map, but you can select the Sector-level map option to
display the map aggregated to cell level, if required.
You can select one of the following map types, depending on the data source
selected, and the network technology:
o Busy Hour: (UMTS only)
 Busy Hour Call Origination: Displays the first message in each call for the
busy-hour traffic, measured in calls.
 Busy Hour Minutes of Use: Displays the busy-hour traffic, in minutes.
 Busy Hour Total Number of Users: Displays the total number of users, over
time, that generated successful calls or data sessions for all RAB types
(circuit, streaming, interactive). The calls/data sessions are counted on the
best server only.
Busy Hour Traffic: Displays the daily busy-hour traffic, in milliErlangs, for
open connections.
o Rich Data (UMTS):
 Busy Hour Number of Calls: Displays the number of calls in the busy hour.
 Number of Distinct Users: Displays the number of different users who
created traffic.
 Total Traffic: Displays the duration of the sessions, in Erlangs.
o Busy Hour (LTE)
Traffic: Displays the duration of the LTE calls in traffic units. (This report can
be created using the busy hour from the client or using rich data from the call
database.)
o Rich Data (LTE):
 DL Traffic (Throughput Events): Displays the downlink throughput duration,
in seconds.
 Number of Distinct Users: Displays the number of different users who
created traffic.
 Number of Sessions: Displays the number of LTE data sessions released,
per bin.
 Traffic: Displays the duration of the LTE sessions, in Erlang. (This report can
also be created by using the busy-hour data from the model on the client.)
 UL Traffic (Throughput Events): Displays the uplink throughput duration, in
seconds.
370
6. Click OK. A progress bar is displayed during the traffic map creation, and while the
layer is being saved and loaded. The layer is displayed in the Layers pane, under the
GIS category, and on the map.
Google Earth.
Displaying Server and Polluter Maps

If your model contains positioning, you can display sectors that served as the best server,
second best and up to fifth best server, as well as the worst polluter, for the busy hour.
If you have a license for the call database, you can display sectors that served as the best up
to 5th best server, as well as the worst polluter, for all hours, for selected mobiles, terminal
models, or release causes.
database.
If your selection contains both LTE and UMTS sectors, you will be prompted to select whether
to create the map for UMTS, LTE, or both technologies.
Earth.
371
To display a server and polluter layer

1. On the Network menu, click Show Maps and then Show Server and Polluter Map
to show the best servers or the worst polluter in the network or in an area or sector
selection.
-OR-
Show Server and Polluter Map.
technology. You can display the map for UMTS, LTE, or both technologies.
The Show Server and Polluter Map dialog box is displayed.
372
3. In the Map type field, select one of the following options, depending on your network
vendor and technology:
UMTS selection:
o Best Server: Displays the coverage area of each selected sector as the best
server. The best server is considered as the serving sector with the highest
number of measurements as the sector with the best Ec/Io in the bin.
o Penetration Loss: Displays the difference in Best Server RSCP between the
outdoor traffic and the indoor traffic carried in each bin.
o Second Strongest Leg: Displays the coverage area of each sector as the
second strongest server. All bins where this sector is detected as the sector with
the highest number of counts as the second strongest pilot are colored on the
map with the sector's unique color.
o Third Strongest Leg: Displays the coverage area of each sector as the third
strongest server. All bins where this sector is detected as the sector with the
highest number of counts as the third strongest pilot are colored on the map with
the sector's unique color.
o Fourth Strongest Leg: Displays the coverage area of each sector as the fourth
highest number of counts as the fourth strongest pilot are colored on the map with
o Fifth Strongest Leg: Displays the coverage area of each sector as the fifth
highest number of counts as the fifth strongest pilot are colored on the map with
o Worst Polluter: Displays the worst polluting sector per bin. The worst polluting
sector is the sector that has the highest number of cases per bin where pilot
pollution conditions are declared, and it is the weakest sector in the active set.
(Too many pilots in the active set while the best server is relatively weak.) From
the RF perspective, the weakest sector in the active set in cases of pilot pollution
means the most unnecessary sector and hence the worst polluting pilot. Note that
the worst polluting sector can be reported only in cases where pilot pollution
conditions are fulfilled.
LTE selection:
o Best Server Cell Name: Display the coverage area of each sector in a different
color and the corresponding cell name.
Multi RAT selection:
o Best Technology Cell (Throughput): Displays the technology with the best
throughput.
373
Google Earth.
Displaying Arc Maps

If your model contains positioning, you can display arc maps showing selected KPIs at either
predefined distance increments from selected sectors, or according to predefined
percentages on the map area and in Google Earth. The arcs are drawn based on each
sector's azimuth, meaning that for Omni sectors, the arcs will create circles. The color of the
arcs is defined by the average value of the selected KPI within the arc range.
The arc-map format is more useful than geo-position traffic maps for rural sites, because one-
way and two-way scenarios are common, and standard positioning maps offer limited
accuracy.
Note: Arc maps are supported for UMTS networks only.
To display an arc map layer

1. On the Network menu, click Show Maps and then Arc to show the value of a
selected KPI as an arc map.
-OR-
Right-click a sector selection, and on the shortcut menu click Show Maps and then
Arc.
374
The Show Arc Map dialog box is displayed.
375
3. In the Map type field, select the type of arc map to display. The color of the arc is
defined by the average value of the selected KPI within the arc range. For example,
in fixed distance traffic maps, the arc at 100m represents all traffic between 0-100m,
the 200m arc represents all traffic between 100-200m, and so on.
You can select one of the following options:
o Ec/Io: Displays arcs showing the average best server Ec/Io at user-defined
distances from a selected sector, according to the ARC_MAP_DISTANCE_STEP
parameter.
o Fixed Distance Busy Hour Traffic: Displays arcs showing daily busy-hour traffic
at user-defined distances from a selected sector, according to the
ARC_MAP_DISTANCE_STEP parameter.
o Fixed Distance Drop Call: Displays arcs showing the average number of
abnormal disconnections (including dropped calls or abnormal data releases) per
day at user-defined distances from a selected sector, according to the
ARC_MAP_DISTANCE_STEP parameter.
o Fixed Percentage Busy Hour Traffic: Displays arcs showing a predefined
percentage of the daily busy-hour traffic per arc, according to the
ARC_MAP_PERCENT_STEP parameter.
o Pilot Dominance: Displays arcs showing the percentage of samples serving
mobiles within the arc range that have pilot dominance, according to the
PILOT_DOMINANCE_DELTA_UMTS parameter.
o Pilot Pollution: Displays arcs showing the percentage of samples serving
mobiles within the arc range that have pilot pollution.
o Soft HO Factor: Displays arcs showing the average soft HO factor, per bin,
based on the average number of BTSs serving mobiles within the arc range.
o Softer HO Factor: Displays arcs showing the average softer HO factor, per bin,
based on the average number of sectors serving mobiles within the arc range.
376
The following arc map shows the traffic between each arch, which is 20% by default,
as well as a traffic map showing the actual traffic bins.
Google Earth.
Displaying Combined Maps

If your model contains positioning, you can display a layer showing a selected map that has
been filtered by one or more maps with specific thresholds. For example, you can display a
drop call map showing the drop rate when the average busy hour has less than 100 users. If
required, you can change the thresholds after the layer has been displayed on the map area.
Note: If any of the maps included in the combination could not be created, the whole map
fails.
If you have a license for the call database, you can display a combined map for all hours.
database.
technology to use.
To display a combined map

1. On the Network menu, click Show Maps and then Combined to show a map layer
filtered by one or more additional maps.
-OR-
Combined.
technology.
377
The Show Combined Map dialog box is displayed.

o Client Model: Busy-hour data will be taken from the network model on the client.
(UMTS only)
o Rich Data: Rich data will be taken from the call database, via the server. This
option is displayed only if you have a license for the call database.
378
3. In the Filter map field, select whether to display a Drop, Performance, Server and
Polluter, or Traffic map, and then click the browse button to filter the map
according to your requirements. The Show <Name of Map> dialog box is displayed,
according to the Data source selected.
o In the Map type field, select the details you want to display for the selected map.
o By default, the map is filtered to show all the available RABs, but you can filter the
RABs or select additional data filters from the Add New Filter drop-down list.
o Click OK. The first filter field is enabled, allowing you to select the filter options for
the selected map.
379
4. In the Where field, select the first map by which to filter the map selected above, and
then click the browse button to select the map type, etc. The Show <Name of
Map> dialog box is displayed.
5. Select the options for the map, as described in step 3.
6. Select the relevant operators and enter the thresholds for the filter in the relevant
fields. For example, you can select to display values less than a specified threshold,
or values equal to or greater than a specified threshold.
7. If required, enter the requirements for additional maps, as well as the Boolean
operator defining whether to filter the original map according to both filters (And), or
either one of them (Or).
Notes:
o You must first select Map from the drop-down list and then the Boolean operator.
o When filtering maps using more than one Boolean operator, first the And
operations are taken into consideration, then the Or operations.
9. Select the Save as Layer check box to save the temporary layer to your disk. A
default name is displayed in the Layer Name field, which you can change if required.
380
10. Click OK. A progress bar is displayed while the map layer is saved and loaded, and
then it is displayed in the Layers pane, under the GIS category.
11. If required, use one of the following methods to change the map thresholds:
o On the legend, click the browse button . The Legend (<name of layer>)
dialog box is displayed, enabling you to edit the filter properties for the map
thresholds.
o In the Layers pane, right-click the layer and on the menu, click Threshold
Selector. The Threshold Selector dialog box is displayed, enabling you to edit
the threshold values.
381
Using the Threshold Selector

After you have created a combined analysis map, and loaded it, you can edit the values of the
map thresholds using the Threshold Selector.
Note: The threshold can be changed for map filtering conditions only. Thresholds cannot be
changed for KPI filtering conditions.
To display the Threshold Selector

1. Load the combined layer on the map.
2. In the Layers pane, right-click the layer and on the menu, click Threshold Selector.
The Threshold Selector dialog box is displayed, with a line for each map filtering
condition selected in the analysis.
Tip: Drag the right edge of the dialog box to resize it to show the full name of the
filters, if required.
3. For each map filter you want to edit, select the relevant operators from the drop-down
list, and/or enter a new value in the value field.
4. Click to close the Threshold Selector dialog box.
Displaying Virtual Drive Test Maps

The virtual drive test map enables you to display an immediate visualization of all call flow
events associated with specific sectors and terminal handsets, according to a specific time.
You can view this virtual drive test on the map area, in the Event Viewer, Detailed Table, and
in Google Earth.
Notes:
 In order to display a virtual drive test map, your license must support the all call
database, and you must be connected to the Mentor server.
 If you have an UMTS/GSM network, you can view the virtual drive test map based on
GSM call traces by setting the ENABLE_GSM_TRACE_POSITIONING parameter to
Yes. Call traces are not dependent on the call database, therefore you do not need a
license, or to be connected to the Mentor server.
To display a virtual drive test map layer

1. On the Network menu, click Show Event Maps and then Virtual Drive Test
-OR-
On the toolbar, click and then click Virtual Drive Test.
-OR-
Right-click a sector selection, and on the shortcut menu, click Show Event Maps and
then Virtual Drive Test.
382
The Show Virtual Drive Test Map dialog box is displayed.
383
5. Click OK. A progress bar is displayed during the virtual drive test map creation, and
A message is displayed notifying you whether the map completed successfully. If

there are more results than defined in the
MAX_VIRTUAL_DRIVE_TEST_CALLS_TO_SHOW parameter, only the predefined
number of results will be retrieved, and you will be notified of such.
6. Click Event Viewer to the display the details of the virtual drive test in the Event
Viewer.
7. Click Close to close the dialog box and view the virtual drive test on the map area.
384
Displaying the Virtual Drive Test Event Viewer

You can view the details of any of the call or data sessions in the Virtual Drive Test map in the
Event Viewer as soon as you have created the map, or anytime afterwards.
The Event Viewer is displayed with 2 panes. The left pane contains call-related details, for
example IMSI, call start time, etc. and the right pane contains event-related details, for
example, the type of event, the active sectors at the time of the event, and so on. You can
filter the list of sessions that are displayed, save selected sessions as a layer, and export the
session events.
To view a virtual drive test in the Event Viewer

1. In the Layers pane, right-click the virtual drive test you want to display in the Event
Viewer, and then click Event Viewer.
-OR-
In the dialog box that is displayed as soon as the Virtual Drive Test map completes,
click Event Viewer.
The Event Viewer pane is displayed, with the phone numbers of all mobiles that took
part in the virtual drive test, as well as the date and time of the sessions, in the Calls
column on the left of the Event Viewer. By default, the details of the first call or data
session are displayed.
In addition, an icon is displayed according to the type of call or data session:
- Normal call
- Drop call
- Access failure call
385
2. Select a call in the left pane to display its details in the right pane. In addition, Mentor
will automatically zoom in to the relevant call or data session on the map, while still
showing all serving sectors. You can also select an event in the right pane and
Mentor will automatically zoom in to the event on the map.
The following call properties can be displayed in the left pane of the Event Viewer,
depending on the technology of the network:
IMSI The IMSI of the mobile device.
IMEI The IMEI of the mobile device.
SV The software version of the UE.

Note: This field is displayed only for Ericsson, NSN, and
ZTE networks.
Call Start Date & The date and time the call or data session was initiated.
Time
Duration (s) The duration of the call or data session, in seconds, based
on the difference between the start and end time.
Release Cause The cause of an abnormal release, if relevant.
RAB The type of RAB, for example, HSPA or voice call.
Call End Date The date and time the call or data session ended.
and Time
Roaming Whether the mobile device is from a roaming network.
Country The subscriber's country.
Operator The subscriber's network operator.
Technology The technology of the network.
Device Type The make of the mobile device, for example, Apple or
Huawei.
Device Model The model of the mobile device, for example, Galaxy S5.
386
Latitude The latitude coordinate of the mobile device at the time of

the event.
Longitude The longitude coordinate of the mobile device at the time of

the event.
The following event properties can be displayed in the right pane of the Event Viewer,
depending on the technology of the network:
Property Technology Description
Event Date & Time All The date and time of each
event.
No. All The number of the event, for

mapping purposes. Only events
with positioning data are given
a number. All other events are
associated with the number
closest to the time of the event.
Event All The type of event within the

relevant domain: RRC, NBAP,
and RANAP.
Direction All The direction of the event—

Sent or Received.
The actual mapping of network
components that are involved in
the process depends on the
event's protocol:
 RRC protocol indicates an
event is from/to the UE,
from the point of view of the
RNC.
 NBAP protocol indicates
an event that is from/to the
NodeB, from the point of
view of the RNC.
 RANAP protocol indicates
an event that is from/to the
RNC, from the point of view
of the Core Network.
Active RNC/BSC 1 UMTS/GSM The RNCs/BSCs to which the

active sectors belong.
Active RNC 2...6 UMTS
387
Active Sector 1 All The names of the sectors that

were assigned at the time of the
Active Sector 2...6 UMTS event.
Active Carrier/BCCH 1 LTE and The carriers/BCCH of the active

UMTS/GSM sectors at the time of the event.
Active Carrier 2...6 UMTS
Active PCI/SC/BSIC 1 LTE/UMTS/GSM The PCI/SC/BSIC of the active

sectors at the time of the event.
Active SC 2...6 UMTS
Active RSRP/RSCP DL LTE/UMTS/GSM The RSRP/RSCP/DL RxLevel

RxLevel 1 of the active sectors at the time
of the event.
Active RSCP 2...6 UMTS
Active RSRQ/ECIO/DL LTE/UMTS/GSM The RSRQ/ECIO/DL RxQual of

RxQual 1 the active sectors at the time of
the event.
Active ECIO 2...6 UMTS
Active UL RxLevel 1 GSM The UL RxLevel of the active

Active UL RxQual 1 GSM The UL RxQual of the active

Timing Advance GSM The distance between the

(Meters) mobile and the transmitting
antenna.
Candidate RNC/BSC UMTS/GSM The RNCs to which the

1...6 candidate sectors belong.
Candidate Sector 1...6 All The names of the candidate

Candidate LTE and The carriers/BCCH of the

Carrier/BCCH 1...6 UMTS/GSM candidate sectors at the time of
the event.
Candidate LTE/UMTS/GSM The PCI/SC/BSIC of the

PCI/SC/BSIC 1...6 candidate sectors at the time of
the event.
388
Candidate LTE/UMTS/GSM The RSRP/RSCP/RxLevel of

RSRP/RSCP/RxLevel the candidate sectors at the
1...6 time of the event.
Candidate RSRQ/ECIO LTE/UMTS The RSRQ/ECIO of the

1...6 candidate sectors at the time of
the event.
Downlink Throughput LTE and UMTS The RLC throughput in the

(Kbps) downlink.
Uplink Throughput LTE and UMTS The RLC throughput on the

(Kbps) uplink.
Latitude All The latitude coordinate of the

event.
Longitude All The longitude coordinate of the

event.

389
4. To save the events of a specific call as a layer, in the Calls pane, right click the
required call or data session and then click Save as Layer.
o Filter: Enables you to filter the items displayed in the Event Viewer or in the event
contents.
o Clear Filter: Clears the previously defined filter. All events will be displayed in the
Event Viewer.
o Filter Calls: Enables you to filter the list of calls or data sessions displayed in the
left pane of the Event Viewer, when viewing a virtual drive test map.
o Clear Call Filter: Clears the previously defined call filter. All call and data
sessions for the selected events will be displayed in the Event Viewer.
o Find: Enables you to search for selected text in the Event Viewer.
o Import Events: Enables you to import previously exported events, and display
them in the Event Viewer.
Note: Not all actions are available for events that were imported into the Event
Viewer.
o Export Events: Enables you to export the events list to a selected folder. The
events are saved as a .zip file and a properties file. You can later import the .zip
file into the viewer.
Note: This option is enabled only if you have permission to view IMSIs.
o Export: Enables you to export only the currently displayed events to a .txt file. For
example, if you performed a search operation or filtered the list, only those events
that matched the search or filter criteria and are displayed are exported.
390
o Show Contents: Opens a pane that displays the actual contents of the selected
event. Once the pane is open, it automatically displays the contents of any other
selected event. (You can also view the contents by double-clicking the event.)
Tip: You can search for text in the contents pane by pressing Ctrl+F.
o Zoom In to Displayed Events: Displays all the mobiles associated with the
selected calls at maximum zoom.
Filtering the Event Viewer Display

The Event Viewer pane displays the events of one or more selected abnormal
disconnections (dropped call or data sessions), as well as the properties of the sectors that
were assigned to the session when it dropped. You can filter the Event Viewer to display only
selected columns, or only events that match your filter criteria.
If you are displaying a virtual drive test in the Event Viewer, you can also filter the display to
show only details from specific calls/data sessions.
To filter the Event Viewer display

1. On the Mobile Drop map, right-click the required drop and then select Show in
Event Viewer. The Show in Event Viewer dialog box is displayed, enabling you to
save the drop as a layer.
391
2. Select the Save as Layer check box, enter a new name for the layer if required, and
click OK. The events contained in the selected drop are displayed in the Event
Viewer pane, at the bottom of the map area.
o If required, add events from additional drops by right-clicking the required drops
on the map and then clicking Add to Event Viewer.
392
4. By default, all the events in the selected drop are displayed in the Event Viewer. To
filter the list of events according to specific properties, click Options, and then click
Filter. The Event Filter dialog box is displayed.
5. In the Column field, select the column to be filtered from the drop-down list. You can
also filter the display according to the actual contents of an event by selecting Event
Contents.
6. In the Condition field, select the operator. For example, contains, does not
contain, and so on.
7. In the Value field, enter the value by which to filter the column or contents.
8. Click Add. The current filter is displayed at the bottom of the dialog box.
9. If required, repeat steps 5–8 for each additional filter condition to apply.
10. Click OK to filter the Event Viewer according to the selected filter. The Event Viewer
displays only those events and properties that meet your filter criteria. After the Event
Viewer has been filtered, the word Filtered is displayed in parentheses, including the
number of items that matched the criteria and the total number of items in the list. For
example, the following Event Viewer pane shows that 4 out of a possible 11 events
are RRC_MEASUREMENT_REPORT events.
11. To clear the filter, click Options and then click Clear Filter.
393
Filtering Virtual Drive Test Calls in the Event Viewer

The Event Viewer pane displays the events of all call and data sessions that took part in the
virtual drive test, based on your filters when creating the virtual drive test map. You can filter
the Event Viewer to display events from selected sessions only, based on the mobile number,
the terminal type, or the time of the session.
You can also filter the Event Viewer to display only selected columns, as well as only events
that match your filter criteria.
To filter the calls in the Event Viewer

1. In the Event Viewer pane, click the Options menu and then click Filter Calls. The
Event Viewer Call Filter dialog box is displayed.
2. Filter the date and time as required.
394
3. Click Add New Filter and then filter the table as required.
4. Click OK. Only the calls that match the filter criteria are displayed in the left pane of
the Event Viewer. The word Filtered is displayed in parentheses, as well as the
number of calls that matched the criteria out of the total number of calls in the list.
5. To clear the filter, on the Options menu, click Clear Call Filter.
Displaying Mobile Drop Maps

If your model contains positioning, you can display a positioned visual indication of abnormal
disconnections reported in the network or in an area or sector selection, per mobile handset,
on the map area and in Google Earth. You can also view the different session legs at the time
of the release, for each selected release. If your license supports it, you can also view the
events in each session in the Event Viewer.
In addition, during the network analysis, you can create a Mobile Drops report, which provides
detailed information regarding the abnormal disconnections recorded for sectors in the
selection set.
Notes:
 Mentor displays maps only for the first 50,000 abnormal disconnections that pass the
filter criteria.
 Abnormal disconnections caused by access failures are displayed in the Access
Failure map and report.
To display a mobile drop layer

1. On the Network menu, click Show Event Maps and then Drop.
-OR-
On the toolbar, click Event Maps and then click Drop.
-OR-
then click Drop.
395
The Show Mobile Drop Map dialog box is displayed.
4. By default, the map is filtered to show all the available release causes, but you can
filter the release causes or select additional data filters from the Add New Filter
drop-down list. After you have selected a filter, it is displayed in the filter area.
396
5. Click OK. A progress bar is displayed during the mobile drops map creation, and
Each abnormal release on the map is colored according to the drop reason, shown in
the legend.
6. To display the serving sectors, click an icon.

Note: If a specific location contains more than one abnormal release, a menu will be
displayed enabling you to select the reason for the release, and then you can select
to show the drop servers.
If the Detailed Table is open, the drop is automatically selected in the table.
According to the selected release, the different active legs at the time of the release
are displayed as follows:
397
7. Tip: You can view the legs of multiple releases by pressing CTRL and the required
releases.
The following table describes the line types displayed.
Line Description
Thick solid line Reference active leg
Thin solid line Other active legs
Thick dashed line Primary candidate leg (monitored or

detected)
Thin dashed line Other candidate legs
8. To view the drop events, right-click the drop and then click Show in Event Viewer.
9. To view the drop details, right-click the drop and then click Show in Detailed Table.
The drop is selected in the Detailed Table.
Google Earth.
398
Displaying Access Failure Maps

If your model contains positioning, you can display a positioned visual indication of the access
failures reported, per mobile handset, on the map area and in Google Earth. You can also
view the different session legs at the time of the failure, for each selected access failure. If
you have an Ericsson network, you can also view the events for each access failure in the
Event Viewer.
In addition, during the network analysis, you can create an Access Failure Report, which
provides detailed information regarding the access failure drops recorded for sectors in the
selection set.
Note: Currently Mentor supports maps for layers of up to 250,000 access failures only.
To display an access failure map layer

1. On the Network menu, click Show Event Maps and then Access Failure to show
the location of the access failures in the network or in an area or sector selection.
-OR-
Access Failure.
399
The Show Access Failure Map dialog box is displayed.
400
5. Click OK. A progress bar is displayed during the access failure map creation, and
Each access failure on the map is colored according to the access failure reason,
shown in the legend.
6. To display the serving sectors, click an access failure.

Note: If a specific location contains more than one access failure, a menu will be
displayed enabling you to select the reason for the access failure, and then you can
select to show the access failure servers.
According to the selected access failure, the different active legs at the time of the
access failure are displayed as follows:
401
Tip: You can view the legs of multiple access failures by pressing CTRL and the
required mobile access failures.
The following table describes the line types displayed.
Line Description
Thick solid Reference active leg

line
Thin solid line Other active legs
Thick dashed Primary candidate leg (monitored or detected)

line
Thin dashed Other candidate legs

line
Google Earth.
402
Displaying Mobile IRAT Maps

IRAT events indicate the shift from the LTE network to the UMTS network or from the UMTS
network to the GSM network. If your model contains positioning, you can display a positioned
visual indication of the IRAT handover or cell reselection events reported for the busy hour,
per mobile handset, on the map area and in Google Earth.
If you have a license for the call database, you can display data for all hours.
technology to use.
Note: This map is currently limited to 100,000 events.
To display an IRAT handover layer

1. On the Network menu, click Show Event Maps and then IRAT to show the location
of the IRAT handovers or cell reselection events in the network or in an area or sector
selection.
-OR-
then IRAT.
technology.
403
The Show Mobile IRAT Map dialog box is displayed.
404
category, and on the map with a icon for each IRAT handover or cell reselection.
7. To display the active and target servers of a selected handover/reselection, click the
, or right-click the handover/reselection and then select the server to display from
the menu.
8. To hide the displayed servers, click the , or right-click the handover and then click
Hide Servers.
Google Earth.
405
Displaying CSFB Maps

In order to support CS (voice or video) calls, mobiles in LTE networks must move to the
underlying UMTS or GSM network.
If you have a license for the call database, you can display a layer showing the circuit-switch
fallback (CSFB) events to a UMTS network. The LTE and UMTS sessions will be connected
based on the IMSI and the timestamp.
Notes:
 You must be connected to the Mentor server in order to access the data from the call
database. To enable visualization of target UMTS sectors and comprehensive geo-
location of these events, UMTS data including network configuration and logs should
also be collected.
 There may be a time difference between the LTE and UMTS networks. This can be
solved using the NETWORKS_TIME_DIFF parameter, in the Server Admin.
To display a mobile CSFB map layer

1. On the Network menu, click Show Event Maps and then CSFB to show the fallback
events in the network or an area or sector selection.
-OR-
then CSFB.
If your selection includes UMTS sectors, you will receive a notification that only the
LTE sectors will be selected. Click OK.
406
The Show Mobile CSFB Map dialog box is displayed.
407
5. Click OK. A progress bar is displayed during the CSFB map creation, and while the
Each fallback event is displayed on the map.
6. To display the serving sectors, right-click a fallback event and click Show Servers.
The different active legs at the time of the fallback event are displayed as follows:
408
Tip: You can view the legs of multiple fallback events by pressing CTRL and the
required mobile fallback events.
Google Earth.
8. To display the layer in the Detailed Table, right-click the layer and then select
Detailed Table.
409
Displaying the CSFB Detailed Table

You can view the properties of a selected CSFB layer in the Detailed Table pane. By default,
all the events in the map area are displayed, but you can filter the table to display only calls
that match your filter criteria. You can also customize the table to display only selected
property columns.
To display the CSFB detailed table

1. In the Layers pane, right-click the CSFB layer, and on the shortcut menu, click
Detailed Table. The Detailed Table - GIS: Mobile CSFB Map pane is displayed at
the bottom of the map area, listing all the CSFB events in the map area.

o To display or hide multiple columns, right-click the column header, and then click
410
The following properties can be displayed in the Detailed Table pane, depending on
the technology of the network:
Time The time of the event.
Release RAB The type of RAB, for example, QC18-Video
Latitude The latitude coordinate of the mobile device at the time of

the event.
Longitude The longitude coordinate of the mobile device at the time

of the event.
IMEI The IMEI of the mobile device.
SV The software version of the UE.

Note: This field is displayed only for Ericsson, NSN, and
ZTE networks.
IMSI The IMSI of the mobile device.
Carrier The carrier to which the LTE sector belongs.
LTE Serving Cell The name of the LTE serving cell.
Target Sector The name of the target sector.
3. If required, you can perform the following actions by clicking the Options menu:
411
o Display on Map: Displays a flag on each of the selected calls.
o Save Selection as Layer: Enables you to save the selected rows as a layer. The
new layer will be displayed in the detailed table with the same legend and
properties as the original layer.
o Clear Filter: Clears the previously defined filter. All the calls will be displayed in
the table.
o Select All: Selects all the calls in the table.
To search for entries in the table:

1. Click Options and on the menu, click Find. The Find dialog box is displayed.
2. Enter the name, or part thereof, of the entity for which you are searching, and click
Next. The first item in the table that matches your search is highlighted.
Tip: If you are sure of the exact name of the entity, you can select the Exact match
check box, and then only those entities that match exactly what you have entered are
highlighted.
3. Click Next until you find the text you were looking for.
o Export: Enables you to export selected calls to a .txt file.
o Zoom In to Displayed Rows: Displays all the flagged calls, at maximum zoom.
412
Displaying Additional Maps

Depending on your license, you can display additional event maps, such as HO Events,
Registration Events, etc. based on the information found in the raw CTR/GPEH data.
Note: In order to display an Additional Events map, your license must support the call
To display an Additional Events map layer

1. On the Network menu, click Show Event Maps and then Additional Maps to show
events in the network or an area or sector selection.
-OR-
then Additional Maps.
technology.
413
The Show Additional Events Map dialog box is displayed.
3. In the Map type field, select the required map type.
414
7. To display the servers of a selected event, click the , or right-click the event and
then select the server to display from the menu.
The servers are displayed as follows:
415
8. To hide the displayed servers, click the , or right-click the event and then click
Hide Servers.
Google Earth.
GSM Maps
If you have an IRAT network and a license for the call database, you can display GSM
positioning maps that are based on the output of the Ericsson Real-Time Performance
Monitoring (RPMO) application in *.ASCI format, and the Huawei GCHR log files. The Mentor
Server collects these files, parses them, and then stores them in the call database.
Note: You must be connected to the Mentor server in order to access data from the call
database.
The following GSM maps are supported:
 Performance maps
 Server and Candidate maps
 Traffic maps
 Virtual Drive Test maps
Displaying GSM Performance Maps

The GSM Performance maps enable you to display the received signal and quality level for
downlink for the best server, and uplink for users of the best server.
If you have a license for the call database, you can display selected performance layers for all
hours, for selected mobiles, terminal models, release causes, and BCCH frequencies.
Note: You must be connected to the Mentor server in order to use the data from the call
database.
Once the map layer has been created, you can display or select the serving sectors on the
map, as well as display the map in Google Earth.
To display a GSM performance map layer

1. On the Network menu, click Show Maps, GSM Maps, and then Performance to
show the performance of the network or a sector selection.
-OR-
Right-click a GSM sector selection, and on the shortcut menu click Show GSM Maps
and then Performance.
416
The Show Performance Map dialog box is displayed.
3. In the Map type field, select the type of performance map to display. You can select
one of the following options:
o Downlink RxLevel Best Server: Displays the downlink received signal level of
the best server.
o Downlink RxQual Best Server: Displays the downlink received signal quality of
the best server.
o GSM MS Power: Displays the mobile station transmitted power.
o Uplink RxLevel Best Server: Displays the uplink received signal level of the
users served by the best server.
o Uplink RxQual Best Server: Displays the uplink received signal quality of the
users served by the best server.
417
6. Click OK. A progress bar is displayed during the performance map creation, and
Google Earth.
418
Displaying GSM Server and Candidate Maps

The Server and Candidate map represents the coverage area of each sector based on the
best server ID stored in a specific parameter. On the map, each cell name will be displayed in
a different color.
You can display the coverage area of each sector based on the best server ID for all hours,
for selected mobiles, terminal models, release causes, and BCCH frequencies.
database.
To display a server and candidate layer

1. On the Network menu, click Show Maps, GSM Maps, and then Server and
Candidate to show the coverage area of each sector based on the best server ID.
-OR-
and then Server and Candidate.
419
The Show Best Server Cell Name Map dialog box is displayed.
420
5. Click OK. A progress bar is displayed during the best server map creation, and while
the layer is being saved and loaded. The layer is displayed in the Layers pane, under
the GIS category, and on the map.
Google Earth.
Displaying GSM Traffic Maps

The GSM Traffic map is based on the number of power records, which are displayed as
Erlang per user for all selected sites.
If you have a license for the call database, you can display the distribution of the total traffic
for the best server for all hours, for selected mobiles, terminal models, release causes, and
BCCH frequencies.
database.
To display a GSM traffic map layer

1. On the Network menu, click Show Maps, GSM Maps, and then Traffic to show the
traffic distribution in the network or sector selection.
-OR-
and then Traffic.
421
The Show Traffic Map dialog box is displayed.
422
5. Click OK. A progress bar is displayed during the traffic map creation, and while the
Google Earth.
Displaying GSM Virtual Drive Test Maps

The virtual drive test map enables you to display an immediate visualization of all call flow
events associated with specific sectors and terminal handsets, according to a specific time.
You can view this virtual drive test on the map area, in the Event Viewer, Detailed Table, and
in Google Earth.
Note: In order to display a virtual drive test map, your license must support the all call
423
To display a virtual drive test map layer

1. On the Network menu, click Show Event Maps, GSM Maps, and then Virtual Drive
Test.
-OR-
On the toolbar, click , GSM Maps, and then click Virtual Drive Test.
-OR-
Right-click a sector selection, and on the shortcut menu, click Show GSM Maps and
then Virtual Drive Test.
The Show Virtual Drive Test Map dialog box is displayed.
424
5. Click OK. A progress bar is displayed during the virtual drive test map creation, and
A message is displayed notifying you whether the map completed successfully. If

there are more results than defined in the
MAX_VIRTUAL_DRIVE_TEST_CALLS_TO_SHOW parameter, only the predefined
number of results will be retrieved, and you will be notified of such.
6. Click Event Viewer to the display the details of the virtual drive test in the Event
Viewer.
425
7. Click Close to close the dialog box and view the virtual drive test on the map area.
Sector and Area Selection Statistics

Mentor enables you to analyze an area or sector selection by displaying the relevant RF and
traffic statistics for the busy hour in the Statistics viewer.
Note: You can view the sector or area statistics only if your model contains positioning or if
you have a license for the call database.
Once the statistics are displayed in the Statistics Viewer, you can select or display the
associated sectors on the map area, add or remove statistics, set the axis range, as well as
import or export the statistics.
Currently, Mentor supports analyzing statistics for:
 UMTS and LTE:
o Mobile Drops
o Performance
o Servers and Polluters
 GSM:
o Mobile Drops
o Performance
o Server and Candidate
426
To display the sector or area statistics in the Statistics Viewer

1. On the Network menu, click Show Statistics and then type of statistics you want to
display.
-OR-
On the toolbar, click and from the drop down menu select the relevant
statistics you want to display.
-OR-
Right-click a UMTS or LTE sector selection, and on the shortcut menu, click Show
Statistics and then the relevant type of statistics. To display the GSM statistics, right-
click a GSM sector selection and on the shortcut menu click Show GSM Maps, GSM
Statistics and then the relevant type of statistics.
The relevant dialog box is displayed enabling you to select the properties to be
displayed in the Statistics Viewer. If your selection contains both UMTS and LTE
sectors, you will be prompted to select the technology to display.
2. Enter your required data and click OK. The selected information is displayed in the
Statistics Viewer.
Displaying UMTS and LTE Mobile Drop Statistics

If your model contains positioning or if you have a license for the call database, you can
display mobile drop statistics for the entire network, or only for an area or sector selection for
the busy hour. For example, you can display a Mobile Drops map on the map area, and then
display statistics for a problematic area.
Once the statistics are displayed in the Statistics Viewer pane, you can add additional statistic
types for the same selection, or you can view the statistics for a sub-selection. You can also
select a bar in the Statistics Viewer pane to flag the associated sector on the map, or select
one or more sectors in a selection to highlight the associated bars in the Statistics Viewer
pane.
technology to use. If required, you can also view the mobile drop statistics for selected GSM
sectors.
To display the mobile drop statistics in the Statistics Viewer pane

1. Create an area or sector selection.
2. On the Network menu, click Show Statistics and then Show Mobile Drop
Statistics.
technology.
427
The Show Mobile Drop Statistics dialog box is displayed.
3. In the Statistics name field, enter a name for the new statistics chart. If you do not
enter a name, the default name will be used.
4. In the Statistics type field, select the type of statistics to display. Currently only
Mobile Drop statistics are supported (voice and data abnormal release).
428
8. Click OK. A progress bar is displayed while the statistics are being created, and then
the number of serving sectors and their statistics are displayed in graph format in the
Statistics Viewer.
displayed.
statistics.
429
430
these sectors.
the legend.
types to display.
431

Displaying UMTS and LTE Performance Statistics

analyze the performance by displaying statistics such as Ec/Io of the best server for the entire
network, or only for an area or sector selection for the busy hour. For example, you can
display a Performance map on the map area, and then display the statistics for a problematic
area.
Once the statistics are displayed in the Statistics Viewer, you can add additional statistic
pane.
technology to use. If required, you can also view the performance statistics for selected GSM
sectors.
To display the performance statistics in the Statistics Viewer pane

2. On the Network menu, click Show Statistics and then Show Performance
Statistics.
Selection dialog box will be displayed, enabling you to select the required technology.
432
The Show Performance Statistics dialog box is displayed.
4. In the Statistics type field, select one of the following options:
o UMTS:
 Downlink Throughput: Shows the distribution of the downlink throughput on
the area or sector selection.
 Downlink Volume: Shows the distribution of the volume on the area or sector
selection.
 Ec/Io Best Server: Shows the distribution of the Ec/Io on the area or sector
selection.
433
 Ec/Io Coverage: Shows the distribution of the Ec/Io coverage on the area or
sector selection.
 RRC Setup Time: Shows the distribution of the RRC setup time (PDF).
 RSCP Best Server: Shows the distribution of the RSCP on the area or sector
selection.
 RSCP Coverage: Shows the distribution of the RSCP coverage on the area or
sector selection.
 Uplink Throughput: Shows the distribution of the uplink throughput on the
area or sector selection.
Uplink Volume: Shows the distribution of the uplink volume on the area or
sector selection.
o LTE:
 Downlink Throughput: Shows the distribution of the downlink throughput on
the area or sector selection.
 Downlink Volume: Shows the distribution of the volume on the area or sector
selection.
 RRC Setup Time: Shows the distribution of the RRC setup time (PDF).
 RSRP Best Server: Shows the distribution of the RSRP on the area or sector
selection.
 RSRQ Best Server: Shows the distribution of the RSRQ on the area or sector
selection.
 Uplink Throughput: Shows the distribution of the uplink throughput on the
area or selector selection.
434
Statistics Viewer.
displayed.
statistics.
435
436
these sectors.
the legend.
types to display.
437

Displaying UMTS and LTE Server and Polluter Statistics

analyze the network by displaying statistics such as best server and number of reported legs
for the entire network, or for an area or sector selection. For example, you can display a
Server and Polluter map on the map area and then display the statistics for a problematic
area.
pane.
technology to use. If required, you can also view the server and polluter statistics for selected
GSM sectors.
438
To display the server and polluter statistics in the Statistics Viewer pane
2. On the Network menu, click Show Statistics and then Show Server and Polluter
Statistics.
technology.
The Show Server and Polluter Statistics dialog box is displayed.
439
o UMTS:
 Best Server: Shows the distribution of the best server sectors on the selected
area, where the x-axis is the sector name, and the y-axis is the percentage of
times the sector served as the best server in an active call.
 Number of Legs in AS: Shows the percentage of time that calls had the
specific active set size in the selected area. The x-axis represents the number
of legs in the active set (1-6 legs) and the y-axis represents the percentage of
time for each state.
 Polluter Sectors: Shows the distribution of the polluter sectors in the selected
sectors or area.
Serving Cell Dominance: Shows the distribution of the serving sectors on the
selected area. Each server is rated as either the best server, or up to the sixth
best server. The x-axis shows the sector name, and the y-axis displays the
percentage of time each sector served as the best to 6th best server.
o LTE:
 Best Server: Shows the distribution of the best server sectors on the selected
area, where the x-axis is the sector name, and the y-axis is the percentage of
times the sector served as the best server in an active call.
 Serving Cell Dominance: Shows the distribution of the serving sectors on the
selected area. Each server is rated as either the best server, or up to the sixth
best server. The x-axis shows the sector name, and the y-axis displays the
percentage of time each sector served as the best to 6th best server.
5. Select one of the following options from the Data source field:
440
Statistics Viewer.
displayed.
10. You can right-click any sector in the Statistics Viewer pane, and then on the
drop-down menu, select or flag the sector on the map, or reset the Y-axis range. You
can also copy the statistics as an image, save the statistics as an image file, or print
the statistics.
441
442
these sectors.
the legend.
types to display.
443

444
Displaying GSM Mobile Drop Statistics

If you have a license for the call database, you can display mobile drop statistics for the entire
GSM network, or only for an area or sector selection. For example, you can display a Mobile
Drop map on the map area, and then display statistics for a problematic area.
pane.
To display the mobile drop statistics in the Statistics Viewer pane

1. Create a GSM area or sector selection.
2. On the Network menu, click Show Statistics, GSM Statistics and then Mobile
Drop. The Mobile Drop dialog box is displayed.
445
4. In the Statistics type field, select the type of statistics to display. Currently only
Mobile Drop statistics are supported (voice and data abnormal release).
Statistics Viewer.
displayed.
446
statistics.
447
these sectors.
the legend.
types to display.
448

Displaying GSM Performance Statistics

analyze the performance by displaying statistics such as the GSM traffic for the entire
network, or only for an area or sector selection for the busy hour. For example, you can
display a Performance map on the map area, and then display the statistics for a problematic
area.
pane.
449
To display the GSM performance statistics in the Statistics Viewer pane

2. On the Network menu, click Show Statistics, GSM Statistics and then
Performance Statistics. You will be prompted to log on to the server if you are not
already connected.
The Performance dialog box is displayed.
o Downlink RxLevel Best: Shows the distribution of the downlink received signal
level of the best server on the area or sector selection.
o Downlink RxQual Best: Shows the distribution of the downlink received signal
quality of the best server on the area or sector selection.
450
o GSM MS Power: Shows the distribution of the mobile station transmitted power
on the area or sector selection.
o GSM Traffic: Shows the distribution of the traffic on the area or sector selection.
o Uplink RxLevel Best: Shows the distribution of the uplink received signal level of
the users served by the best server on the area or sector selection.
o Uplink RxQual Best: Shows the distribution of the uplink received signal quality
of the users served by the best server on the area or sector selection.
Statistics Viewer.
displayed.
451
statistics.
452
these sectors.
the legend.
types to display.
453

Displaying GSM Server and Candidate Statistics

If you have a license for the call database, you can display the server and candidate statistics
for the entire GSM network, or only for an area or sector selection. For example, you can
display a Best Server map on the map area, and then display statistics for a problematic
area.
pane.
454
To display the server and candidate statistics in the Statistics Viewer pane
2. On the Network menu, click Show Statistics, GSM Statistics and then Server and
Candidate. The Server and Candidate dialog box is displayed.
o GSM Best Server: Shows the coverage area of each selected GSM sector as the
best server in the selected area or sector selection.
o GSM Candidate Sectors: Shows the distribution of the candidate sectors in the
selected area or sector selection.
455
Statistics Viewer.
displayed.
456
statistics.
457
these sectors.
the legend.
types to display.
458

459
Filtering the Map, Report, and Statistics Date and Time

To filter the date and time
in the call database are displayed in the Date and time field in the relevant dialog
box, but you can filter the dates and the time range that is used by clicking the
browse button to display the Date and Time Range dialog box.
2. In the Date Range area, select the dates to include. Dates for which there is a model
or data in the call database are displayed in bold.
3. In the Time Range area, select one of the following options, depending on the
o 24 Hours: All hours in the selected days will be used.
o Busy Hours: The busy hour of the selected days will be used.
o Hours (from/to): Select the start and end times. The selected time range will be
used for the selected days.
4. Click OK.
460
Working with Map and Statistics Filters

By default, when creating maps and statistics charts, all data is displayed for all sectors and
all days, but you can filter the data as required.
To filter the map and statistics data

 In the relevant dialog box, click Add New Filter.
Depending on your data source and the network technology, you can select one of
the following filters:
o RAB Group
o Profile
o Mobility
o Release Cause
o Networks
o Select Mobiles
o Device Type
o Device Capabilities
o Establishment Cause
o BCCH Frequency
The selected filter is displayed in the filter area.
461
RAB Group
In the RAB Group field, select the type of traffic to display.
You can select all or a single RAB from the drop-down list, or you can select multiple RABs by
clicking the browse button and then selecting the required RABs in the Add RABs dialog
box.
Note: For Downlink Throughput and Downlink Throughput Peak maps, only HSDPA traffic is
supported.
462
Profile
In the Profile field, select whether to display the map for indoor or outdoor calls/data
sessions, or for all calls/data sessions including those not identified as being indoor or
outdoor.
Mobility
In the Mobility field, select whether to display the map for static or moving calls/data
sessions, or for all calls/data sessions including those not identified as being static or moving.
463
Release Cause
1. In the Add Reasons dialog box, select one or more causes for the call release and
click OK.
The Release Cause field is displayed in the filter area, showing the selected release
causes.
2. If required, select a different release cause from the drop-down list, or select multiple
causes by clicking the browse button and then selecting the required reasons in
the Add Reasons dialog box.
464
Networks
1. In the Add Networks dialog box, select one or more subscriber networks by which to
filter the map and then click OK.

The Networks field is displayed in the filter area, showing the selected subscriber
networks.
2. If required, you can select a different network from the drop-down list, or you can
select multiple networks by clicking the browse button and then selecting the
required networks in the Add Networks dialog box.
465
Select Mobiles
1. In the Select mobiles field, select whether to filter the data according to specific
IMEIs or IMSIs.
2. In the Numbers/File field, enter the relevant numbers, or click the browse button to
browse to the file containing the required numbers.
Tip: To display IMSIs that do NOT start with specific numbers, add not to the
beginning of the expression. For example, not345* will find all IDs that do not start
with the numbers 345.
466
Device Type
1. In the Add Models dialog box, use the arrows to select the device models by which
to filter the data, and click OK.
The Device Type and Models/File fields are displayed in the filter area.
2. In the Device Type field, you can filter the devices according to a file or an
expression, if required.
o From file: Enter the path of the file containing the required device types in the
Models/Files field, or click the browse button to browse to the file.
o By expression: Enter a regular expression in the Models/Files field to filter the
device types. For example, iPhone* will take into consideration all models of
iPhone.
467
Device Capabilities
1. In the Add Device Capabilities dialog box, use the arrows to select the capabilities
by which to filter the data.

2. In the Function area, select whether to add the filter for all the conditions or one of
them.
3. Click OK. The Device Capabilities field is displayed in the filter area, showing the
selected capabilities.
4. If required, select a different device capability from the drop-down list, or select
multiple capabilities by clicking the browse button and then selecting the required
reasons in the Add Device Capabilities dialog box.
468
Establishment Cause
1. In the Add Establishment Causes dialog box, select one or more causes for the call
establishment and then click OK.

The Establishment Cause field is displayed in the filter area.
2. If required, you can select a different establishment cause from the drop-down list, or
you can select multiple establishment causes by clicking the browse button and
then selecting the required causes in the Add Establishment Causes dialog box.
469
BCCH Frequency
1. In the Frequency Selector dialog box, select one or more frequencies.
The BCCH Frequency field is displayed in the filter area.

2. If required, you can select a different frequency from the drop-down list, or you can
select multiple frequencies by clicking the browse button and then selecting the
required frequencies in the Frequency Selector dialog box.
470
Automatic Problem Detection (APD)

The Mentor Automatic Problem Detection (APD) feature identifies and displays problematic
areas (polygons) on the map area, based on a list of predefined problems in the APD
template.
Note: The APD module is enabled only if your license supports it.
After you have imported an APD calculation, you can analyze the network by viewing the APD
layer on the map. If required you can make changes to an existing APD task by duplicating
the task and then editing it as required.
If you are connected to the Mentor server, you can schedule APD tasks to be run
automatically at a specific time.
 Importing APD Task Occurrences into Mentor
 Duplicating Existing APD Calculations
 Viewing the APD Layers
 Viewing the APD Results in the Detailed Table
 Viewing the APD Results in the APD Problem Viewer
Importing APD Task Occurrences into Mentor

You can import selected APD task occurrences from the Mentor server as new networks, or
as APD calculations in the current network.
To import an APD task occurrence

1. On the Server menu, click APD Task Occurrences to view a list of the relevant
tasks. The Server Admin - APD window is displayed.
2. Right-click the task occurrence you want to import into Mentor, and then select one of
the following options on the shortcut menu:
o Open in New Network: Opens the task occurrence in a new network.
o Open in Current Network - <network>: Opens the task occurrence as a
calculation in the current network.
471
A progress bar is displayed while the task occurrence is imported into Mentor, and
then a dialog box is displayed notifying whether the import was successful.
3. Click Details to view the details of the import process.

4. Click Layers to view the network-related layers of the imported occurrence.
5. Click Reports to view the Model and Import reports for the imported occurrence.
6. Click Close to close the Import Task Occurrence dialog box.
Viewing the APD Layers

The APD layers include a Detected Problems layer that shows areas with problems listed in
the template as well as the KPIs that were included in the template.
To load the detected problem layers

1. In the Calculations pane, right-click the APD calculation whose layers you want to
load. On the shortcut menu, click Load Layers.
-OR-
In the Calculations pane, select the APD calculation whose layers you want to load,
and then from the Calculation menu, click Load Layers.
The Layers dialog box is displayed, showing a list of the available layers for the
selected APD task.
2. Select the Detected Problems layer. The Load button is enabled.
472
3. Click Load. The selected layer is listed in the Layers pane, with the name of the APD
calculation, under the Calculation Results node.
4. In the Layers pane, select the check box next to the name of the layer to be
displayed. A progress bar is displayed while the layer is loaded. As soon as the layer
is loaded, it is displayed on the map.
5. To view the legend of a loaded layer, right-click the layer in the Layers pane and then
click Show Legend. The relevant layer legend is displayed.
473
6. You can edit the legend by clicking the browse button . The relevant Legend
7. Change the legend as required.
To hide the APD layers

 Clear the APD layer check box in the Layers pane. The layer is not displayed on the
map, and the check box next to the name of the layer is cleared.
474
Viewing the APD Results in the Detailed Table

You can view the properties of a selected APD layer in the Detailed Table pane. By default,
all the problems in the map area are displayed, but you can filter the table to display only the
problems that match your filter criteria. You can also customize the table to display only
selected property columns.
To view the APD layer in the Detailed Table pane

1. In the Layers pane, right-click the APD layer, and on the shortcut menu, click
Detailed Table. The Detailed Table is displayed at the bottom of the map area, listing
all the detected problems in the selected layer on the map area.

475
o To display or hide multiple columns, right-click the column header, and then click
The following properties can be displayed in the Detailed Table pane:
Problem The detected problem.
Cause The cause of the problem.
Severity The severity of the problem, in percentage.
Polygon ID The identification of the polygon.
KPI Name 1...10 The KPI name.
KPI Value 1...10 The KPI value.
Dominant Sectors The sectors that serve the problematic area.
476
o Display on Map: Displays a flag on each of the selected problem polygon areas.
o Save Selection as Layer: Enables you to save the selected rows as a layer. The
new layer will be displayed in the map area and detailed table with the same
legend and properties as the original layer.
o Clear Filter: Clears the previously defined filter. All APD problem polygons will be
displayed in the table.
o Select All: Selects all the problems in the table.
To search for entries in the table:

1. Click Options and on the menu, click Find. The Find dialog box is displayed.
477
2. Enter the name, or part thereof, of the entity for which you are searching, and click
Next. The first item in the table that matches your search is highlighted.
Tip: If you are sure of the exact name of the entity, you can select the Exact match
check box, and then only those entities that match exactly what you have entered are
highlighted.
3. Click Next until you find the text you were looking for.
o Export: Enables you to export selected problems to a .txt file.
o Zoom In to Displayed Rows: Displays all the flagged problems, at maximum
zoom.
Viewing the APD Results in the APD Problem Viewer

The APD Problem Viewer enables you to view a list of detected problems as well as details
about these problems.
The APD Problem Viewer is made up of two panes. The left pane displays a list of the
detected problems, and the right pane displays details about the polygons in each selected
problem.
By default, all the problems in the map are displayed in the APD Problem Viewer, but you can
customize the panes to display only selected property columns, and you can filter the panes
to display only problems that match your filter criteria.
To view the APD layer in the Detailed Table pane

1. In the Layers pane, right-click the Detected Problems layer, and on the shortcut
menu, click APD Viewer. The APD Problem Viewer is displayed at the bottom of the
map area, listing all the detected problems in the selected layer on the map area.

3. To remove a column, right-click the header of the column you want to remove and
then click Remove this Column. The selected column will be hidden, and will not be
displayed in the APD Problem Viewer.
4. To display or hide multiple columns, right-click the column header, and then click
Customize. The Customize Columns dialog box is displayed, enabling you to select
the columns to be displayed.
478
The following properties can be displayed in the left pane of the Problem Viewer:
Problem The detected problem.
Cause The cause of the problem.
Total No. of Polygons The total number of polygons affected.
High Severity The number of polygons with high severity

problems.
Medium Severity The number of polygons with medium severity

problems.
Low Severity The number of polygons with low severity

problems.
The following properties can be displayed in the right pane of the Problem Viewer:
Polygon ID The ID of the selected polygon
Severity The severity of the selected polygon.
Area The area of the selected polygon.
o Display on Map: Displays a flag on each of the selected problem polygon areas.
o Select on Map: Displays the selected polygons on the map.
o Save Problem as Layer: Enables you to save the selected rows as a layer. The
new layer will be displayed in the map area and Problem Viewer with the same
legend and properties as the original layer.
o Run as Analysis Task: Opens the Analysis wizard for the selected polygon.
o Show in Google Earth: Displays the selected polygons in Google Earth.
o Show KPIs: Opens the Detailed Table and displays the KPIs that were used for
the calculation.
o Filter: Enables you to filter the items displayed.
o Clear Filter: Clears the previously defined filter. All APD problem polygons will be
displayed in the table.
o Select All: Selects all the problems in the table.
o Export: Enables you to export selected problems to a .txt file.
o Zoom In to Polygons: Displays all the flagged problems, at maximum zoom.
6. Click to close the APD Problem Viewer pane.
479
Duplicating Existing APD Calculations

For your convenience, you can duplicate an existing APD calculation, and then edit it as
required.
To duplicate an APD calculation

1. In the Calculations pane, right-click the APD calculation you want to copy, and on
the shortcut menu, click Duplicate and Edit. The first step of the APD wizard is
displayed, showing the data from the original calculation.
2. Edit the fields in the wizard pages as required, and then click Finish. The status of
the calculation is displayed at the top of the Calculations pane.
480
Resolving UMTS/GSM Discrepancies

Mentor can generate a script that automatically resolves all UMTS/GSM discrepancies in the
network.
To resolve the UMTS/GSM discrepancies

1. Ensure that you are using the latest UMTS configuration files.
2. On the Tools menu, click Resolve UMTS/GSM Discrepancies. The Resolve
UMTS/GSM Discrepancies dialog box is displayed.
3. In the Location field, select the location of the switch dump data.
o Local:
 In the <vendor> configuration field, select or browse to the location of the
.xml file containing the most updated UMTS switch dump data for the relevant
network.
 In the GSM configuration field, select or browse to the location of the .txt file
containing the most updated GSM switch dump data.
481
o Server: (The fields in the dialog box change accordingly)
 In the Cluster field, select the cluster from which to import the switch dump
data.
Note: The selected cluster must contain both UMTS and GSM switch dumps.
4. In the Results Directory field, browse to the directory in which to save the
discrepancy script.
Note: All existing data in the output folder is deleted each time you run the
discrepancy script.
5. Click OK. If this is not the first time you are running the discrepancy script, a
confirmation message is displayed notifying that all existing files in the output
directory will be deleted.
6. Click Yes to continue. A progress bar is displayed while the configuration is imported
and the discrepancy script is created, and then a dialog box is displayed notifying you
whether the process completed successfully.
7. Click Details to view details of errors and/or warnings generated during the
discrepancy resolution.
8. Click Reports to view the report generated during the discrepancy resolution
process. The report shows the way the GSM network is listed in the IRAT adjacency
definition in the UMTS network, and the actual values, as defined in the GSM
network.
9. Click Close to close the Resolve UMTS/GSM Discrepancies dialog box.
482
Resolve UMTS-GSM Discrepancies Report

The Resolve UMTS-GSM Discrepancies report shows the way the GSM network is listed in
the IRAT adjacency definition in the UMTS network, and the actual values, as defined in the
GSM network.
For a detailed description of the report, refer to the Ultima Mentor Help.
483
SC Plan Optimization
Mentor's SC plan optimization presents an automatic solution for SC optimization in all wide-
band technologies, taking into consideration the physical array of cell sites and antennas, the
neighbor list definition, and various constraints and planning rules.
SC optimization should be performed to resolve co-SC conflicts before running any other
optimization, for example, the neighbor list optimization.
Note that Mentor uses the original imported neighbor list to find any co-SC conflicts, and not
the optimized neighbor list.
SC planning is required in the following cases:
 Optimizing existing sites - resolving co-SC conflicts or reserving SCs for future sites
 New site planning - selecting the best SCs for new sites
 Redefining pilots for large clusters, which can be the result of reserving SCs for new
sites
The SC optimization flow supports both active and non-active sectors.
 Defining Advanced SC Plan Parameters
 Launching the SC Optimization Wizard
 Scrambling Code Layers
 SC Report
 Displaying Potential Co-SC Conflicts
Defining Advanced SC Plan Parameters

If required, you can configure the advanced parameters that control the SC optimization.
Note: You should consult TEOCO Customer Support before making changes to these
parameters in order to fully understand the impact.
To define the SC optimization parameters

box is displayed.
2. Select the Advanced tab. A list of the parameter groups is displayed.
3. Click the button next to the SC Plan and Sector Identification group to view the
parameters.
4. Edit the parameters as required.
5. Click OK to save your changes.
484
Launching the SC Optimization Wizard

After you have imported the network, you can launch the SC Optimization wizard, which
guides you through the process of planning the SCs. By default, the SC optimization is carried
out on all the sectors in the network, but you can create a selection set if required.
Note for Windows 32-bit users: If your selection set contains over 5,000 sectors, there is a
possibility that the calculation may fail or that the system will crash.
After you have run the optimization, you can use the same template to schedule SC
optimizations to be run automatically at a specific time.
To launch the SC Optimization wizard
1. On the Workflow toolbar, click the button and then select SC Plan
from the drop-down menu.
2. Click Yes if you are prompted to save the network. The first step of the SC
Optimization wizard is displayed, enabling you to define the general properties of the
SC plan.
The SC Optimization wizard contains three steps:
 Step 1 General, enables you to define general properties for the plan, for example,
the name of the plan and the way in which to optimize the selected sectors.
 Step 2 Constraints, enables you to set the global and sector-level constraints for the
optimization.
check to fail.
485
Defining General SC Properties

The General page of the SC Optimization wizard enables you to define general properties
for the SC plan, such as the name of the plan and the goal of the optimization.
To define the general properties of the SC plan

1. In the Name field, enter a name for the new SC plan.
3. In the Goal area, select the goal for the SC optimization plan:
o Recreate global SC plan (within the selection): Mentor will provide a global Co-
SC solution for the entire selection, enabling you to plan as well as reserve SCs
for new sites. (This is the default option.)
o Resolve severe co-SCs for active sites (within the selection): Mentor will
detect severe co-SC conflicts in the selection and assign new SCs. If required,
Mentor will replace SCs of other sites as well, in order to reach the best solution.
Sectors that are missing data or that are defined as non-active will not be included
in the optimization.
o Plan SCs for new sites: Mentor will detect manually created sectors/sites and
sites that were listed as inactive, and assign them new SCs to reduce the
possibility of co-SC conflicts with the neighboring sectors.
Note: If you will be using the site-wise constraint method (selected in step 2 of the
wizard), all sectors in the site should be selected.
486
o Plan SCs for new sites and resolve severe co-SCs for active sites: Mentor
will assign different SCs to new sites and solve co-SC conflicts for active sites.
This goal is a combination of the two previous goals, above.
Note: If you will be using the site-wise constraint method (selected in step 2 of the
wizard), all sectors in the site should be selected.
selecting the required days in the Date Range dialog box.
Note: This field is displayed only if you have enabled the USE_LOGS_BASED
parameter, which instructs Mentor to use an algorithm that takes log-based data into
consideration as well as the data from the switch dump.
5. Click Next to proceed to the Constraints page, where you can define the constraints
used in the optimization.
487
Defining SC Optimization Constraints

The Constraints page enables you to define global and sector-level constraints for the SC
optimization.
To set the SC constraints

1. In the Global SC Allocation area, select one of the following methods to define the
SC allocation policy.
o Sector Wise: The SC range is divided into groups according to the
SECTOR_WISE_SC_DELTA parameter, and then allocated accordingly to the
sectors in a site. For example, if the delta is 168, the SCs will be allocated as
follows, according to the azimuth:
 The first sector in each site will be allocated SCs ranging from 1 to 168.
 The second sector in each site will be allocated SCs ranging from 169 to 336.
 The third sector in each site will be allocated SCs ranging from 337 to 511.
o Site Wise: The SCs are allocated sequentially per site, with the delta based on
the SITE_WISE_SC_STEP parameter. For example, if the step is 8, possible
allocations would be 1-9-17, or 25-33-41 and so on.
Note: All sectors in the site should be selected.
o Best Available: SCs are allocated randomly from within the range of valid SCs.
2. If required, in the Global Allowed SCs area, enter the global allowed SC range in the
SCs field. This enables you to reserve SCs for new sectors, or for future sites. For
example, if you allow only SCs 1-200, and 205, as shown in the example below the
field, all other SCs will be reserved for new sectors and Femtocells.
488
3. Click Constraints Analysis to generate a report showing the number of sectors that
can be optimized, and the sectors that are locked for optimization.
4. Click Next to proceed to the Summary page, which displays a summary of the
optimization, including the number of data inconsistency errors and warnings. A
progress bar is displayed while the data consistency is checked.
Viewing the SC Optimization Summary

The Summary page enables you to view a summary of the optimization, including the data
and save these details for analyzing at a later stage.
If there are any data inconsistency warnings, you are required to approve them before
running the SC optimization.

1. If there are data inconsistencies, click the Details button. The Details window is
displayed, showing a list of the errors and warnings.
2. To save the SC optimization template for further use, click Save. A standard Save
489
3. Click Finish to run the SC optimization. The status of the optimization is displayed at
the top of the Calculations pane.
4. As soon as the optimization has finished running, its status changes to Valid, and the
SC Optimization Completed dialog box is displayed.
o Click Layers to view the SC layers.

o Click Reports to view the SC optimization report.
5. Click Close to close the SC Optimization Completed dialog box.
SC Report
The SC report shows details of the SC changes, as well as of the SC reuses before and after
the optimization.
To view the SC report

1. In the SC Optimization Completed dialog box, click Reports.
-OR-
In the Calculations pane, right-click the SC plan optimization whose reports you
want to view, and then select Open Reports on the shortcut menu.
The <name of SC optimization> Reports dialog box is displayed.
490
2. In the Report Name area, double-click the report or select the report and then click
Open. The report is displayed in Excel format, showing the following tabs:
o Summary, which shows general information about the optimization, for example,
the number of sectors that were optimized, and the number of sectors that were
locked for optimization.
o SC Changes, which shows a list of sectors whose SCs were changed, as well as
their SCs before and after the optimization.
o SC Reuses Before, which shows the SC weighted relations before the SC
optimization.
o SC Reuses After, which shows the SC weighted relations after the SC
optimization.
o Carrier Summary, which shows per carrier and in total, the number of sectors
that were optimized and the severity before and after the optimization.
o Network Properties, which shows the advanced network properties that were
taken into consideration during the optimization.
3. To save the report, click Save As. The Save Reports to Folder dialog box is
displayed, enabling you to browse to the folder in which to save the selected report.
For a detailed description of the tabs and fields in the SC report, refer to the Ultima Mentor
Help.
Scrambling Code Layers

Mentor creates three layers for each SC Optimization plan. A layer of SC reuses before the
optimization and a layer of SC reuses after the optimization, showing SC-reuse pairs
connected by a line whose color reflects the severity of the reuse, as well as a layer that
shows all the sectors whose SC was changed.
Depending on the severity of the SC reuse, the following can be displayed in the layers:
 Co-located sectors: The SC reuse is created by two sectors that probably share the
same site, or the distance between the antennas is 200 meters or less. Co-located
sector reuses are the most severe, and are therefore Mentor's top priority to fix.
 Nearby sectors: The distance between the SC-reuse pair is below the distance
defined by the MIN_CO_PN_DISTANCEMIN_CO_SC_DISTANCE parameter. (By
default, this distance is 1 km.) Nearby-sector reuses, which are more likely to occur
than instances of co-located sector reuses, are also considered severe, and are
Mentor's second priority to fix.
 Tier 1 HO: The SC-reuse pair are first tier neighbors, meaning the source and the
target sectors have the same SC. Tier 1 HO reuses are also a second priority
problem, with the same weight as nearby-sector reuses.
 Tier 2 HO: The SC-reuse pair are defined as 2nd tier neighbors in at least one
direction. One of them is the source sector and the other is the neighbor of its
neighbor (source -> target1 -> target2 where SC (source) = SC (target1)). Tier 2 HO-
reuse pairs are Mentor's third priority to fix.
 <number>: The calculated severity of the SC-reuse before optimization, based on
the angle, antenna profile, and distance between the sectors in the SC-reuse pair.
This indication is displayed only when the reuse sectors are not co-located, nearby,
or tier 1 or tier 2 neighbors, and the distance between them is less than the distances
defined in the MAX_CO_PN_DISTANCEMAX_CO_SC_DISTANCE and
MIN_CO_PN_DISTANCEMIN_CO_SC_DISTANCE parameters.
491
You can load and display the SC plan layers on the map immediately after running the SC
optimization, or any time afterwards.
If required, you can hide the layers after they have been loaded.
To load the SC layers

1. When the SC optimization is completed, click Layers in the SC Optimization
Completed dialog box.
-OR-
In the Calculations pane, right-click the SC optimization whose layers you want to
load, and on the shortcut menu, click Load Layers.
selected optimization.
2. Select the layers to be loaded using standard Windows functionality. The Load
button is enabled.
3. Click Load. The selected layers are listed in the Layers pane, with the name of the
optimization, under the Calculation Results node.
492
4. After you have loaded the selected layers, click Close to close the Layers dialog box.
5. In the Calculations pane, select the check box next to the name of the layers to be
displayed. A progress bar is displayed while each layer is loaded. As soon as the
layer is loaded, it is displayed on the map.
493
7. You can edit the legend by clicking the browse button . The Legend dialog box is
displayed.
To hide the SC layers:

 Deselect the layer in the Layers pane. The layer is not displayed on the map, and the
check box next to the name of the layer is cleared.
494
Exporting the SC Plan Changes

Once you have run the SC optimization and are satisfied with the results, you can export the
changes to be implemented in the network. Before the plan is exported, the switch dumps are
read to ensure that the most recent parameters are used.
To export the SC plan changes

1. On the Calculations pane, select the SC plan whose changes you want to export.
2. Right-click the SC plan, and on the shortcut menu, click Export Plan.
-OR-
On the Calculation menu, click Export Plan.
The Export Scrambling Code Plan dialog box is displayed, enabling you to select
the location of the latest switch dump data, and the directory to which to export the
SC change files.
If you have a multi-vendor environment, a field per vendor is displayed for the location
of the configuration files.
495
information will be used to ensure that the most recent parameters are used in the
exported SC plan. Also, some information required for provisioning is available only in
the switch dumps, and is not saved to the environment during the import process.
4. In the Results Directory field, click the browse button to browse to the directory
to which to export the files.
5. Click OK. If you have previously exported the neighbor list files, a confirmation
message is displayed warning that existing files may be overwritten. Click Yes to
continue. A progress bar is displayed while the SC plan is exported, and then a dialog
box is displayed notifying whether the export process was successful.
6. If required, click Open Folder to view the exported files as well as the rollback file. If
you have a multi-vendor network, a folder is displayed for each vendor.
Ericsson and Nokia networks: An .xml file is created for the SC changes.
Huawei networks: A .txt file is created for the SC changes.
496
Displaying Potential Co-SC Conflicts

You can display potential co-SC conflicts by highlighting and displaying links to all sectors
sharing the same SC as the selected sector.
Note that in order to limit the number of possible conflicts, Mentor will show potential co-SC
conflicts only within the range specified by the MAX_CO_SC_DISTANCE parameter (default
is 50km/30.07 miles) or within a range 4-times the average neighbor distance (not including
softer or unknown neighbors).
To display a potential co-SC conflict

1. Right-click the sector for which you want to display potential conflicts and then click
Show Potential Co-SC.
-OR-
On the Network menu, select Show Potential Co-SC. The cursor changes to
enabling you to select the sector whose potential co-SC conflicts you want to view.
Select the required sector.
The Show Potential Co-SC dialog box is displayed.
2. Select the Save as Layer check box to save the layer under the GIS category in the
Layers pane.
3. If required, enter a new name for the layer. By default, the name of the sector, the
carrier to which it belongs, as well as its SC are included in the layer name.
497
4. Click OK. If there are any co-SC conflicts, the selected sector is flagged on the map,
and links are displayed to all sectors with the same SC.
5. To display the layer in the Detailed Table, right-click the layer in the Layers pane and
then click Detailed Table.
498
PCI Plan Optimization

Mentor's PCI plan optimization presents an automatic solution for PCI optimization for LTE,
taking into consideration the physical array of cell sites and antennas, the neighbor list
definition, and various constraints and planning rules.
PCI optimization should be performed to resolve co-PCI conflicts before running any analysis.
PCI planning is required in the following cases:
 Optimizing existing sites - resolving co-PCI conflicts or reserving PCIs for future sites
 Redefining PCIs for large clusters, which can be the result of reserving PCIs for new
sites
 Pre-Conditions for PCI Optimization
 Defining Advanced PCI Plan Parameters
 Launching the PCI Optimization Wizard
 PCI Layers
 PCI Report
 Displaying Potential Co-PCI Conflicts
Pre-Conditions for PCI Optimization

Ensure the following before running the PCI Optimization:
 Use the updated setting of the network in terms of physical sites and antenna array
(especially location, azimuth, and antenna profiles).
 Include non-active sites (sites that will be activated in the future and should to be
taken into account).
 Update Mentor with the latest switch dump, including an accurate and current PCI
plan and neighbor list.
st nd
 Using the current neighbor list, Mentor can detect 1 or 2 tier co-PCIs and co-PCIs
in the neighbor list.
Defining Advanced PCI Plan Parameters

If required, you can configure the advanced parameters that control the PCI optimization.
parameters in order to fully understand the impact.
To define the PCI optimization parameters

box is displayed.
3. Click the button next to the PCI Plan and Sector Identification group to view the
parameters.
499
Launching the PCI Optimization Wizard

After you have imported the network, you can launch the PCI Optimization wizard, which
guides you through the process of planning the PCIs. By default, the PCI optimization is
carried out on all the sectors in the network, but you can create a selection set if required.
After you have run the optimization, you can use the same template to schedule PCI
optimizations to be run automatically at a specific time.
To launch the PCI Optimization wizard
1. On the Workflow toolbar, click the button and then select PCI Plan
from the drop-down menu.
2. Click Yes if you are prompted to save the network. The first step of the PCI
PCI plan.
The PCI Optimization wizard contains three steps:
the name of the plan and the way in which to optimize the selected sectors.
 Step 2 Constraints, enables you to set the global and sector-level constraints for the
optimization.
check to fail.
500
Defining General PCI Properties

The General page of the PCI Optimization wizard enables you to define general properties
for the PCI plan, such as the name of the plan and the goal of the optimization.
To define the general properties of the PCI plan

1. In the Name field, enter a name for the new PCI plan.
3. In the Goal area, select the goal for the PCI optimization plan:
o Recreate global PCI plan (within the selection): Mentor will provide a global co-
PCI solution for the entire selection, enabling you to plan as well as reserve PCIs
for new sites. (This is the default option.)
o Resolve severe co-PCIs for active sites (within the selection): Mentor will
detect severe co-PCI conflicts in the selection and assign new PCIs. If required,
Mentor will replace PCIs of other sites as well, in order to reach the best solution.
Sectors that are missing data or that are defined as non-active will not be included
in the optimization.
4. Click Next to proceed to the Constraints page, where you can define the constraints
used in the optimization.
501
Defining PCI Optimization Constraints

The Constraints page enables you to define global and sector-level constraints for the PCI
optimization.
To set the PCI constraints

1. In the Global PCI Allocation area, select one of the following methods to define the
PCI allocation policy.
o Force CID group per site and sub-ID per sector: Assign both CID groups and
also have a fixed assignment of sub-CIDs per sector (based on the sector
number, where sector 1 gets 0, sector 2 gets 1, and so on). This is the default
option.
o Force sub-CIDs per sector: Use a fixed assignment of sub-CIDs per sector (no
groups are forced per site).
o Force CID group per site: Force all the cells within a single site to have the
same Cell ID group. Each cell can have a free unique sub-CID (unlike the
previous two options, where sub-CIS is matched with the sector number).
o Best Available: PCIs are allocated randomly from within the range of valid PCIs.
2. If required, in the Global Allowed PCIs area, enter the global allowed PCI range in
the PCIs field. This enables you to reserve PCIs for new sectors, or for future sites.
For example, if you allow only PCIs 1-200, and 205, as shown in the example below
the field, all other PCIs will be reserved for new sectors and Femtocells.
3. Click Constraints Analysis to generate a report showing the number of sectors that
can be optimized, and the sectors that are locked for optimization.
502
Viewing the PCI Optimization Summary

running the PCI optimization.

2. To save the PCI optimization template for further use, click Save. A standard Save
3. Click Finish to run the PCI optimization. The status of the optimization is displayed at
the top of the Calculations pane.
503
PCI Optimization Completed dialog box is displayed.
o Click Layers to view the PCI layers.

o Click Reports to view the PCI optimization report.
5. Click Close to close the PCI Optimization Completed dialog box.
Running the PCI Optimization Plan

To run the PCI optimization plan
1. In the Summary page, click Finish.
504
The status of the optimization is displayed at the top of the Calculations pane.
PCI Optimization Completed dialog box is displayed.
o Click Layers to view the PCI layers.

o Click Reports to view the PCI optimization report.
3. Click Close to close the PCI Optimization Completed dialog box.
PCI Report
The PCI Plan report shows details of the PCI changes, as well as of the PCI reuses before
and after the optimization.
To view the PCI report

1. In the PCI Optimization Completed dialog box, click Reports.
-OR-
In the Calculations pane, right-click the PCI plan optimization whose reports you
505
The <name of PCI optimization> Reports dialog box is displayed.
2. In the Report Name area, double-click the report or select the report and then click
Open. The report is displayed in Excel format, showing the following tabs:
o Summary, which shows general information about the optimization, for example,
the number of sectors that were optimized, and the number of sectors that were
locked for optimization.
o PCI Changes, which shows a list of sectors whose PCIs were changed, as well
as their PCIs before and after the optimization.
o PCI Reuses Before, which shows the PCI weighted relations before the PCI
optimization.
o PCI Reuses After, which shows the PCI weighted relations after the PCI
optimization.
o Carrier Summary, which shows per carrier and in total, the number of sectors
that were optimized and the severity before and after the optimization.
o Reuses Summary, which shows a summary of the PCI reuses, and the result of
the optimization.
3. To save the report, click Save As. The Save Reports to Folder dialog box is
displayed, enabling you to browse to the folder in which to save the selected report.
For a detailed description of the tabs and fields in the PCI report, refer to the Ultima Mentor
Help.
506
PCI Layers
Mentor creates up to three layers for each PCI Optimization plan—A layer that shows all the
sectors whose PCI was changed, a layer of PCI reuses before the optimization, and a layer of
PCI reuses after the optimization. The PCI-reuse pairs are connected by a line whose color
reflects the severity of the reuse.
Depending on the severity of the PCI reuse, the following can be displayed in the layers:
 Co-located sectors: The PCI reuse is created by two sectors that probably share the
same site, or the distance between the antennas is 200 meters or less. Co-located
sector reuses are the most severe, and are therefore Mentor's top priority to fix.
 Nearby sectors: The distance between the PCI-reuse pair is below the distance
defined by the MIN_CO_PCI_DISTANCE parameter. (By default, this distance is 1
km.) Nearby-sector reuses, which are more likely to occur than instances of co-
located sector reuses, are also considered severe, and are Mentor's second priority
to fix.
 Tier 1 HO: The PCI-reuse pair are first tier neighbors, meaning the source and the
target sectors have the same PCI. Tier 1 HO reuses are also a second priority
problem, with the same weight as nearby-sector reuses.
 Tier 2 HO: The PCI-reuse pair are defined as 2nd tier neighbors in at least one
direction. One of them is the source sector and the other is the neighbor of its
neighbor (source -> target1 -> target2 where PCI (source) = PCI (target1)). Tier 2
HO-reuse pairs are Mentor's third priority to fix.
 <number>: The calculated severity of the PCI-reuse before optimization, based on
the angle, antenna profile, and distance between the sectors in the PCI-reuse pair.
This indication is displayed only when the reuse sectors are not co-located, nearby,
or tier 1 or tier 2 neighbors, and the distance between them is less than the distances
defined in the MAX_CO_PCI_DISTANCE and MIN_CO_PCI_DISTANCE parameters.
You can load and display the PCI plan layers on the map immediately after running the PCI
optimization, or any time afterwards.
If required, you can hide the layers after they have been loaded.
To load the PCI layers

1. When the PCI optimization is completed, click Layers in the PCI Optimization
Completed dialog box.
-OR-
In the Calculations pane, right-click the PCI optimization whose layers you want to
load, and on the shortcut menu, click Load Layers.
507
button is enabled.
508
7. You can edit the legend by clicking the browse button . The Legend dialog box is
displayed.

509
To hide the PCI layers:

Displaying Potential Co-PCI Conflicts

You can display potential co-PCI conflicts by highlighting and displaying links to all sectors
sharing the same PCI as the selected sector.
Note that in order to limit the number of possible conflicts, Mentor will show potential co-PCI
conflicts only within the range specified by the MAX_CO_PCI_DISTANCE parameter (default
is 50km/30.07 miles) or within a range 4-times the average neighbor distance (not including
softer or unknown neighbors).
To display a potential co-PCI conflict

1. Right-click the sector for which you want to display potential conflicts and then click
Show Potential Co-PCI.
-OR-
On the Network menu, select Show Potential Co-PCI. The cursor changes to
enabling you to select the sector whose potential co-PCI conflicts you want to view.
Select the required sector.
The Show Potential Co-PCI dialog box is displayed.
2. Select the Save as Layer check box to save the layer under the GIS category in the
Layers pane.
3. If required, enter a new name for the layer. By default, the name of the sector, the
carrier to which it belongs, as well as its PCI are included in the layer name.
510
4. Click OK. If there are any co-PCI conflicts, the selected sector is flagged on the map,
and links are displayed to all sectors with the same PCI.
5. To display the layer in the Detailed Table, right-click the layer in the Layers pane and
then click Detailed Table.
511
Area Code Optimization

The Area Code optimization plan enables you to detect problems in the Location Area Code
(LAC), Tracking Area Code (TAC), and Routing Area Code (RAC) planning, and suggest
recommendations in order to reduce signaling traffic.
The network requires the location of the mobile phones so that they can be reached it in case
of incoming calls. If a mobile does not have an active connection to the network, which
enables the network to know which site the mobile is currently connected to, the network
needs to know which location area the mobile is in, in order to send Paging messages to all
sites within that location area to reach the mobile. Therefore, each time a mobile changes its
location area it performs a location area update, which produces signaling traffic.
The planning of the location area topology directly affects the signaling load on the sites.
Therefore, it is important to avoid cases where sites within a certain location area are
assigned to a different location area, as mobiles passing these sites will perform location
updates when coming into the coverage area of the site and again when leaving its coverage
area. Additionally, sites at the border of a location area usually experience more signaling
traffic due to location updates, so the planning of the location area border also has a direct
impact on the number of location updates. For example, setting a location area border along a
street with high traffic will cause many location updates since the mobiles move from sites on
one side of the street to sites on the other side, which causes location updates if the sites
belong to different location areas.
Notes:
 UMTS:
o A location area can exist within one RNC area only. However, one RNC can
include multiple location areas.
o A routing area can exist within one location area only. However, one location area
can contain multiple routing areas.
 LTE: Each TAC is unique within a PLMN. Therefore, TACs must not be reused within
the same PLMN, even if there are multiple vendors.
 Launching the Area Code Optimization Wizard
 Area Code Layers
 Area Code Optimization Reports
 Scheduling Recurring Optimization Tasks
Launching the Area Code Optimization Wizard

The Area Code Optimization wizard guides you through the process of planning and
optimizing the area codes. By default, the Area Code optimization is carried out on all the
sectors in the network, but you can create a selection set if required.
If your selection contains both UMTS and LTE sectors, you will be required to select the
technology on which to run the optimization.
512
To launch the Area Code Optimization wizard

1. On the Calculation menu, click New and then select Area Code Plan.
-OR-
On the Workflow toolbar, click the button and then select Area Code
Plan from the drop-down menu.
2. If your selection contains both UMTS and LTE sectors, the Technology Selection
dialog box will be displayed, enabling you to select the required technology.
3. Click Yes if you are prompted to save the network. The first step of the Area Code
Area Code plan.
The Area Code Optimization wizard contains two steps:
the name of the plan and the template to use.
 Step 2 Summary, enables you to view a summary of the optimization and run the
optimization plan.
513
Defining the General Area Code Properties

The General page of the Area Code Optimization enables you to define general properties for
the Area Code plan, such as the name of the plan and the template to be used.
To define the general properties of the Area Code plan

1. In the Name field, enter a name for the new Area Code plan.
optimization.
514
Viewing the Area Code Optimization Summary and Running the

Plan
The Summary page enables you to view a summary of the optimization, including the
number of sectors selected and the technology used. If required, you can save the template
to be used in the future optimizations.
To view the area code optimization summary and run the plan
1. To save the Area Code optimization template for further use, click Save. A standard
Save dialog box is displayed.
2. Browse to the location in which to save the template.
3. Enter a name for the template in the File name field.
4. Click Save. The template is saved and can be used as a template in further Area
Code optimizations.
515
5. Click Finish to run the Area Code optimization. The status of the optimization is
displayed at the top of the Calculations pane.
As soon as the optimization has finished running, its status changes to Valid, and the
Area Code Optimization Completed dialog box is displayed.
6. Click Layers to view the available area code layers, and load the selected layers.
The selected layers are displayed in the Layers pane, and can be selected and
viewed on the map.
7. Click Reports to view a list of area code optimization reports that can be displayed.
8. Click Close to close the Area Code Planning Completed dialog box.
Area Code Layers

The Area Code Issues layer displays the isolated and border sites on the map.
Isolated cells: Sites that are located within a Location Area but are assigned to a different Location Area.
Border cells: Sites that are located on the border of the Location Area.
To load the Area Code layers

1. When the Area Code optimization is completed, click Layers in the Area Code
Optimization Completed dialog box.
-OR-
In the Calculations pane, right-click the area code optimization whose layers you
want to load, and on the shortcut menu, click Load Layers.
516
The Layers dialog box is displayed, showing the available layers for the selected
optimization.
2. Select the layer to be loaded and then click Load. The layer is listed in the Layers
pane, with the name of the optimization, under the Calculation Results node.
517
The layer is displayed on the map area.
3. After you have loaded the layer, click Close to close the Layers dialog box.
To hide the Area Code layers:

Area Code Optimization Reports

The Area Code Plan report shows details about the optimization, including recommendations
on how to fix area code issues.
518
To view the Area Code Plan report

1. In the Calculations pane, right-click the optimization whose reports you want to view,
and then click Open Reports on the shortcut menu.
-OR-
In the Calculations pane, select the optimization whose reports you want to view,
and then on the Calculation menu, click Open Reports.
The <name of calculation> Reports dialog box is displayed, showing the available
report.
2. Select the report and click Open.
The Area Code Plan report is displayed, showing the following tabs:
o Area Analysis Details, which displays details about the sectors in the selection,
including the sectors that were identified as belonging to isolated or border sites,
and Mentor's recommendation for fixing these issues.
For a detailed description of the tabs and fields in the analysis reports, refer to the
Ultima Mentor Online Help.
519


-OR-
Optimization Task.
520
Neighbor List Optimization

The neighbor list contains the sectors that are most likely to participate in the handovers. The
neighbor list optimization helps ensure that the neighbor list is as accurate as possible. If the
neighbor list is not properly planned, pilots that are missing from the neighbor list will not be
identified by the mobiles, and therefore will not appear in the PSMM and RTD messages,
resulting in a less accurate RF model of the network.
The recommended workflow should include two neighbor list optimizations—before and after
the RF shaping optimization—for example, to optimize the neighbor list according to the new
power settings, which may cause a different level of interaction between the sectors. In any
event, prior to the optimization phase, you should import a new model and update the
environment with the latest parameter and configuration settings.
implementing an optimization, otherwise you may be implementing a plan that is based on
outdated information.
There are two types of neighbor lists:
 Original Neighbor List - the currently implemented neighbor list, which was imported
from the switch dump.
 Optimized Neighbor List - the planned neighbor list, meaning the result of the
neighbor list optimization process. You must implement this neighbor list and then
import it in order for it to become the current neighbor list.
The current neighbor list can be viewed in the Sector Properties Neighbor List tab, and in the
Neighbor List Viewer pane.
If required, you can manually fine tune the neighbor list by adding or removing neighbors, or
by changing the priority of existing neighbors.
 Neighbor List Overview
 Neighbor List Optimization Workflow
 Defining the Neighbor List Optimization Parameters
 Launching the Neighbor List Optimization Wizard
 Neighbor List Layers
 Neighbor List Reports
 Showing Incoming Neighbors
 Showing Outgoing Neighbors
 Showing Neighbor List Tier Numbers
 Viewing Neighbor List Changes
 Removing Lines Connecting Associated Sectors
 Implementing the Neighbor List Plan
 Manual Neighbor List Optimization
If you have a multi-technology network, IRAT handover optimization from UMTS to GSM can
be performed.
521
Neighbor List Overview

Mobile phones continuously scan the network, during active and idle modes, searching for
scrambling codes (SCs)/PCIs that may be strong candidates for handovers. To reduce the
processing time required to find these SC/PCIs, the RNC provides each mobile with a
"neighbor list message", or "neighbor list update message" containing a list of up to
20 SC/PCIs that should be scanned. This list, known as the neighbor list, contains only
the SC/PCIs of the sectors serving the area around the current sector, and which are
therefore potential candidates for handovers. The RNC enables handovers only to target
sectors that appear in the neighbor list. Handovers to sectors that do not appear in the
neighbor list are usually rejected.
An optimal neighbor list makes the scanning procedure more effective and improves the call
quality and system performance. For example, missing SC/PCIs can lead to interference or
even dropped calls, and unnecessary SC/PCIs lengthen the scanning process.
Another important aspect of the neighbor list scanning is the priority of the neighbor sectors in
the neighbor list. Mentor counts the handover attempts from each source sector to its
potential neighbors, known as the handover count, and then assigns a priority according to
this number. Mentor sorts the neighbor list according to handover count, which is actually the
main basis for the neighbor list optimization. The priority of the sectors in the neighbor list is
very important, as it ensures that the sectors are arranged according to the probability that
they will participate in the handover. When the mobile is in a 2-way soft handover, the RNC
creates a combined list of the top SCs from the neighbor lists from each source sector
participating in the soft handover. Sorting the neighbor list by priority is very important, as it
ensures that the SCs with a higher chance of being included in the handover are included in
the combined list.
Source sectors with an absolute low handover count are removed from the optimization plan,
as their statistical significance is low. Target neighboring sectors with absolute or relative low
handover counts are removed from the neighbor list for the same reason, giving higher
priority to neighbors with higher handover counts.
An optimized neighbor list represents the most realistic level of interaction between sectors.
Neighbors with a high interaction level with the source sector are candidates for higher
priorities, while sectors with lower interaction levels will be given lower priorities, or even
removed from the neighbor list.
Note that in the following cases, Mentor can use special optimization rules to keep neighbors
in the list, or to give them a higher priority than they would normally be assigned.
 Missing neighbors - sectors that do not appear in the original neighbor list.
 Locked neighbors - you can give minimal priority to special sectors or temporary
sectors and they will not be removed from the neighbor list.
 Co-SC/PCI neighbors - source sectors with two possible neighbors with the same
SC/PCI. Mentor decides whether to optimize these sectors, and which sectors to use
as the neighbor. Note that co-SC/PCI problems may be serious RF planning
problems that should be solved separately by correct SC/PCI planning. Mentor
provides a special report for potential co-SC or co-PCI issues.
 Softer neighbors - target sectors sharing the same site usually receive the highest
priority, no matter what their handover count.
If required, you can add new neighbors to the neighbor list, or you can prevent certain sectors
or selection from taking part in the neighbor list optimization by adding them to the neighbor
list, and then defining them as forbidden neighbors.
For more details, refer to the Ultima Mentor Help.
522
Neighbor List Optimization Workflow

The neighbor list optimization workflow includes the following steps:
Step 1: Configure the neighbor list parameters, if required
Step 2: Run the neighbor list optimization
Step 3: Review the neighbor list optimization reports and layers
Step 4: If required, manually fine tune the neighbor list plan
Step 5: Select a neighbor list plan to implement
Step 6: Implement the selected neighbor list plan
Step 7: Validate the plan implementation
The neighbor list optimization should be performed before and after every antenna sectors
optimization if necessary, based on the HO-rate change, which shows the number of neighbor
list problems. Before each optimization, you should collect new call-trace data and update the
environment with the latest parameter settings.
Optimizing IRAT Networks

An IRAT neighbor list is needed for a smooth transition to GSM, allowing subscribers to move
between UMTS and GSM radio access networks without losing service. Mentor optimizes the
IRAT handovers list if the GSM network is defined in the environment and a measurement
plan has been run.
Note: The measurement plan is optional. It is required for addition only.
 Resolving GSM/UMTS Discrepancies
 UMTS/GSM Discrepancy Report
 Defining IRAT Neighbor List Optimization Parameters
 Defining the UMTS/GSM Measurement Plan
 Running an IRAT Handover Optimization
 Implementing the IRAT Neighbor List Plan
Optimizing Inter-Frequency Networks

As systems with multiple carriers become more common and users move between carriers to
improve coverage, to enable load sharing, or for service-based transition, for example,
dedicated carriers for HSPA users, it is vital to maintain an optimized inter-frequency neighbor
list in the network configuration to prevent call dragging, call drops, bad quality, and inefficient
use of resources.
Mentor enables you to create an optimal IFHO neighbor list, with the correct priorities, so that
the transition between carriers will be more reliable and efficient. Speech and data calls can
handover between carriers during a conversation or session. An idle phone or modem can
also move to camp on a different carrier, in a reselection process.
 Defining Inter-Frequency Neighbor List Optimization Parameters
 Launching the Neighbor List Optimization Wizard
523
Optimizing Multi-Vendor Networks

You can import and display environments that are made up of multiple vendors, for example,
Ericsson and Huawei together in the same environment. Multi-vendor networks must be
created in the Mentor server, and can then be imported into Mentor. The network model is
created for a single vendor only, called the primary vendor.
You can view the network vendors and the primary vendor in the Network Properties dialog
box.
524
You can view the vendor to which a sector belongs in the relevant Sector Properties dialog
box.
Mentor enables you to create a neighbor list that includes neighbors from multiple vendors.
However, only the sectors belonging to the primary vendor are included in the model and can
be optimized, but sectors from the neighboring vendor are also taken into consideration. This
improves accuracy and sector associations, as well as the map accuracy at the borders. The
neighbor list script in the provisioning task should match the neighbor list plan, and include
sectors from both vendors.
525
Defining the Neighbor List Optimization Parameters

If required, you can configure the advanced parameters that control the neighbor list
optimization.
parameters to prevent optimization degradation.
To define the neighbor list optimization parameters

box is displayed.
3. Click the button next to the Neighbor List Optimization, Neighbor List Optimization
- Inactive, Neighbor List Optimization - Indoor or Neighbor List Optimization - LTE
group to view the parameters.
Launching the Neighbor List Optimization Wizard

After you have analyzed the network, and configured the neighbor list parameters (if
required), you can launch the Neighbor List Optimization wizard, which guides you through
the process of planning and optimizing the neighbor list. By default, the neighbor list
optimization is carried out on the selection set used in the model, but you can change this by
selecting a sub-set of the original selection set.
Notes:
 Only sectors for which there is a model can be included in the optimization. If your
selection includes sectors for which there is no model, you will be able to run the
optimization on the rest of the sectors in the selection, which are included in the
model.
 If your selection contains both LTE and UMTS sectors, the optimization will be run
according to the model technology.
To launch the Neighbor List Optimization wizard

1. On the Calculation menu, click New > Neighbor List Plan.
-OR-
On the Workflow toolbar, click the button and then select Neighbor
List Plan from the drop-down menu.
526

The first step of the Neighbor List Optimization wizard is displayed, enabling you to
define the general properties of the neighbor list plan.
The Neighbor List Optimization wizard contains two steps:

 Step 1 General, enables you to define general properties for the neighbor list plan, for
example the name of the plan and the type of neighbor list to optimize.
check to fail.
Defining General Neighbor List Properties

The General page of the Neighbor List Optimization wizard enables you to define general
properties for the neighbor list plan, for example the name of the plan, and the type of
neighbor list to optimize. It also enables you to select whether to run the optimization on the
existing sectors or the planned sectors.
Note: The fields in the General page change according to your network vendor and
technology.
527
To define the general properties of the neighbor list plan

1. In the Name field, enter a name for the new neighbor list plan.
4. In the Sector Type area, select whether the optimization should be run on the
existing network sectors or on the planned sectors.
5. If you selected to run the optimization on the existing sectors, select to run whether
the optimization on active sectors, inactive sectors, or all sectors.
6. In the Neighbor List Type area, select the type of neighbor list to optimize.
Depending on your network environment, the following options are available:
o LTE to LTE
o UMTS Intra-frequency: Enables you to optimize the neighbor list for sectors
belonging to the same carrier.
o UMTS Inter-frequency: Enables you to optimize the neighbor list for sectors
belonging to different carriers.
o UMTS/GSM: Enables you to optimize the neighbor list for 3G to 2G sectors,
based on the call-trace data and PM counters. By default, reciprocity is
recommended, based on the value of the IRAT_RECIPROCITY_LEVEL
parameter in the Advanced network properties.
528
7. If you selected UMTS Inter-frequency:

o In the Directions field, select the source and target carriers. If required, you can
define the maximum number of neighbors allowed, per source and target carrier
pair.
By default, all possible carrier directions are optimized, but you can select a single
direction from the drop-down list, or click the browse button to display the Add
From Carrier - To Carrier dialog box, which enables you to select multiple
directions.
 To select multiple directions, double-click the required carrier directions in the

left pane to move them to the right pane.
 Click OK. The selected carriers will be displayed in the Directions field.
o In the Inter-frequency rule file field, click the View Rules button to display the
rules that were defined for inter-frequency handovers, based on the configuration
of the source and target carriers.
8. If you selected UMTS/GSM, select the GSM band to be optimized from the drop-
down list. By default, all existing bands are optimized.
529
Viewing the Neighbor List Optimization Summary

running the neighbor list optimization.

2. To save the neighbor list template for future use, click Save. A standard Save dialog
box is displayed.
neighbor list optimizations.
530
3. Click Finish to run the neighbor list optimization plan. The status of the optimization
is displayed at the top of the Calculations pane.
Neighbor List Optimization Completed dialog box is displayed.
o Click Details to view details of the errors or warning messages. Note that the
Details button is enabled only if there are errors or warnings found in the
optimization.
o Click Layers to view the available neighbor list layers, and load the selected
layers. The selected layers are displayed in the Layers pane, and can be
selected and viewed on the map.
o Click Reports to view a list of neighbor list optimization reports that can be
displayed.
5. Click Close to close the Neighbor List Planning Completed dialog box.
Neighbor List Layers

You can load and display the neighbor list layers on the map immediately after running the
neighbor list optimization, or any time afterwards. Depending on the environment, you can
display the following neighbor list layers:
 HO Rate Change, which shows the difference in the HO rate between the new and
the old neighbor list, per sector.
 HO Count Change, which shows the difference in the number of HO counts between
the new and the old neighbor list, per sector.
 Source Co-SCs, which shows cases where two sectors with a common neighbor
have the same SC.
 Target Co-SCs, which shows cases where a single sector has two neighbors with the
same SC.
 Impact Rate Change, which shows the difference in the impact rate between the
new neighbor list and the original neighbor list. The impact rate is the projected
handover rate between the planned source sector and the existing target sector.
Note: This layer is displayed for planned sectors only.
531
To load the neighbor list layers

1. When the neighbor list optimization is completed, click Layers in the Neighbor List
Optimization Completed dialog box.
-OR-
In the Calculations pane, right-click the neighbor list optimization whose layers you
want to load. On the shortcut menu, click Load Layers.
-OR-
In the Calculations pane, select the neighbor list optimization whose layers you want
to load, and then from the Calculation menu, click Load Layers.
button is enabled.
532
533
7. You can edit the legend by clicking the browse button . The relevant Legend
To hide the neighbor list layers

534
Viewing Neighbor List Changes

After you have run a neighbor list optimization, you can view the recommended changes to
the neighbor list on the map. Mentor displays lines connecting a selected sector to all its
neighbors, and colors these lines and the neighbors according to the recommended changes.
For example, neighbors that are to be added to the neighbor list are displayed in green, and
those to be deleted from the neighbor list are displayed in red. You can remove the lines, if
required, and you can save the changes as a layer that can be loaded at any time.
If you have a multi-technology network that includes GSM, you can view the neighbor list
changes for handovers to either the UMTS or the neighboring GSM sectors. If you have a
multi-carrier network, you can also display the changes for handovers to neighbors from other
carriers.
To show the neighbor list changes

1. On the Network menu, click Show Neighbor List Changes and then select To
UMTS, To UMTS Inter Freq, or To GSM.
-OR-
On the toolbar, click the Show Neighbor List Changes button , and then select
either To UMTS, To UMTS Inter Freq, or To GSM.
The cursor changes to .

2. In the map area, click the sector whose recommended neighbor list changes you
want to view. The Neighbor List Changes dialog box is displayed.
3. In the Neighbor plan field, select the name of the neighbor list optimization for which
to display the relevant recommended changes.
the map.
535
5. Click OK. A progress bar is displayed during the layer creation, and while the layer is
category, and on the map. The referenced sector is connected to its neighboring
sectors, which are colored according to their recommended changes, by a line in the
same color.
Neighbors can be added or removed, undergo no major changes meaning their

position in the neighbor list did not change by at least six positions, undergo major
changes up or down meaning their position in the neighbor list went up or down by at
least six positions, undergo no changes, or have a priority added or removed.
536
6. If required, you can change the legend by clicking the browse button . The
Legend dialog box is displayed, enabling you to change the legend as required.
7. If required, you can remove the lines connecting the sectors.
537
Showing Neighbor List Tier Numbers

The neighbor list tier numbers are used to show the relationship between the source and
target sectors, where the most natural neighbors are considered Tier1 neighbors. Mentor
determines the tier numbers based on arguments such as HO rate and distance from
neighboring sectors. For example, softer neighbors or the closest neighbors facing the source
sector are considered Tier1 neighbors, and the source sector and the neighbor of the target
sector are considered Tier2 neighbors, and so on.
You can display the tier numbers of a selected sector's neighbors on the map, and save the
tier numbers as a layer that can be loaded at any time.
To show the neighbor list tier numbers

1. On the map, right-click the sector whose neighbor list tier numbers you want to view,
and from the shortcut menu, click Show Neighbor List Tier Numbers. The
Neighbor List Tier Number dialog box is displayed.
the map.
538
3. Click OK. A progress bar is displayed while the tier numbers are being calculated,
and then the selected sector is flagged, and its neighbors are colored according to
the legend, enabling you to see the relationship between the source and its target
sectors.
Neighbor List Reports

The Neighbor List reports show the results of the neighbor list optimization. You can view
and save selected reports.
To view a neighbor list report

1. In the Neighbor List Optimization Completed dialog box, click Reports.
-OR-
In the Calculations pane, right-click the neighbor list optimization whose reports you
-OR-
In the Calculations pane, select the neighbor list optimization whose reports you
want to view, and then from the Calculation menu, click Open Reports.
539
The <name of optimization> Reports dialog box is displayed, showing a list of

available reports:
There are four available reports:

o Neighbor List Errors and Warnings Report, which summarizes all errors and
warnings, including co-SC conflicts.
o Neighbor List Reciprocity Report, which summarizes the level of non-reciprocal
handover cases per source sector.
o Neighbor List Report, which lists the new neighbor list for all sectors. (If there
are no changes, the original neighbor list is displayed.)
o Neighbor List Summary Report, which summarizes the results of the
optimization process.
For a detailed description of the tabs and fields in each report, refer to the Ultima Mentor
Help.
Implementing the Neighbor List Plan

After you have run the neighbor list optimization, you should do the following when
implementing the neighbor list plan:
 Review the neighbor list implementation plan, to ensure that the neighbor list is
properly optimized.
 Export the neighbor list changes (UMTS only)
 Exporting the IRAT neighbor list changes
 Validate the plan implementation
 View the Neighbor List Implementation Validation report
540
Reviewing the Neighbor List Implementation Plan

After reviewing the neighbor list HO Rate Change tab, and assessing the number of sectors
that need to be optimized, it is recommended to implement all the changes at the same time
to achieve the maximum improvement.
If required, you can reduce the number of optimized sectors by selecting the option to
optimize only those sectors with the most significant changes, and then exporting their
neighbor list optimization plan.
In the case of a multi-carrier network:
 By default, Mentor optimizes all the carriers the same way. This option should not be
changed, unless it is clearly required to create different plans per carrier.
 If a single carrier was optimized and all carriers are the same, the single carrier
neighbor list plan can be manually copied to the other carriers.
 If a single carrier was optimized, but the rest of the carriers are not the same,
meaning they do not share the same antennas and traffic load, the neighbor list
should be implemented for the optimized carrier only, and you should create a new
optimization plan for the other carriers.
Exporting the Neighbor List Changes (UMTS Only)

Once you have run the neighbor list optimization and are satisfied with the results, or fined-
tuned the results using the Neighbor List Editor, you can export the changes to be
implemented in the network. Before the plan is exported, the switch dumps are read to ensure
that the most recent parameters are used.
You can export all the neighbor list entries, or select the number of most significantly changed
entries to export.
Note for ASSET: Ensure that the CREATE_ASSET_XML_FILE parameter is set to

Yes.
To export the neighbor list changes

1. In the Calculations pane, select the neighbor list plan whose changes you want to
export.
2. Right-click the neighbor list plan, and on the shortcut menu, click Export Plan.
-OR-
541
The Export Neighbor List Plan dialog box is displayed, enabling you to select the
location of the latest switch dump data, and the directory to which to export the
neighbor list change files.
542
exported neighbor list plan. Also, some information required for provisioning is
available only in the switch dumps, and is not saved to the environment during the
import process.
5. If required, you can limit the number of lists to export by selecting the No. of most
significantly changed neighbor lists to export check box in the Filter area, and
then entering a value in the field provided. Mentor will export the selected number of
neighbor lists with the most significant changes.
543
6. If required, in the Carrier area, select the check boxes next to the numbers of the
carriers that you want to include in or exclude from the export process.
continue. A progress bar is displayed while the neighbor list is exported, and then a
dialog box is displayed, notifying whether the export process was successful.
8. If required, click Open Folder to open the folder containing the exported files. If you
have a multi-vendor network, a folder is displayed for each network.
Ericsson and Nokia networks: An .xml file is created for the sectors that have been
deleted from the neighbor list, and for those that have been added.
Huawei networks: A .txt file is created for the sectors that have been deleted from
the neighbor list, and for those that have been added.
Exporting the IRAT Neighbor List Changes

Once you have run the IRAT neighbor list optimization and are satisfied with the results, or
fined-tuned the results using the Neighbor List Editor, you can export the changes to be
implemented in the network. Before the plan is exported, both the UMTS and the GSM switch
dumps are read to ensure that the most recent parameters are used.

1. In the Calculations pane, select the IRAT neighbor list plan whose changes you
want to export.
-OR-
544
neighbor list changes files.
import process.
click the browse button in the <UMTS vendor> configuration files and GSM
configuration files fields to browse to the location of the files containing the latest
UMTS and GSM switch dump data.
6. If required, click Open Folder to open the folder containing the exported files.
545




validate.
Implementation.
-OR-
546



-OR-
Optimization Task.
547
Submitting Network Changes to the Mentor Server

When you submit data to the server for the first time, or after you have imported the network
configuration from the server, modified it and then submitted your changes back to the server,
Mentor analyzes the data, and makes a list of discrepancies between the submitted data and
the data currently on the server, which you then have to accept or reject. The accepted
changes to the server network are sent to the server and divided up according to the clusters
to which they belong. All the users assigned to the relevant clusters will receive notification of
the submission, as well as a link to the report listing the changes to the server network,
enabling them to sync their networks with the updated network on the server.
To submit changes to the Mentor server

1. On the Server menu, click Submit Network Changes to Server. You will be
prompted to log on to the Mentor server if you have not already done so. A progress
bar is displayed while the data being submitted is compared to the existing data in the
server.
Notes:
o If there is more than one cluster defined in the network, the Select a Cluster
dialog box is displayed. Select the cluster to which the changes should be made,
and click OK. If required, you can also submit changes for additional clusters
directly from the Submit Network Changes to Server <date> dialog box, which
is displayed after all the submitted data has been compared.
o If the network contains network elements that are not part of the selected cluster,
a message is displayed notifying you that any changes made to these network
elements will be ignored and will not be submitted. Click OK to continue.
o The first time a network is submitted to the server, it must include the terrain file.
548
The Submit Network Changes to Server <date> dialog box is displayed, showing
all the discrepancies between the network data being submitted, and the data
currently in the server network, for the selected cluster.
Note: If you are submitting your changes to a multi-technology network, and have
permission for only one of the technologies, your submission will be ignored.
2. Review each of the differences, and then click Accept Change or Ignore Change at
the top of the screen, to accept or ignore the proposed change to the network data on
the server. Accept or Ignore is displayed in the Accept/Reject column. If required,
you can use standard Windows functionality to select multiple or all listed differences.
Note: If there are changes to the advanced network properties, you will have to
accept the changes for each of the required network elements, as well as for the
cluster.
3. Click OK. A confirmation message is displayed.
549
4. Click Yes to submit the accepted changes to the server. A progress bar is displayed
while these changes are being submitted to the server and then the Submit Network
Changes to Server dialog box is displayed, notifying whether the cluster was
updated successfully.
All relevant cluster users will receive notification of the changes, as well as a list of
the changes, enabling them to sync their networks with the updated network on the
server.
5. Click Details to view any errors or warnings.
6. Click Reports to view a report showing details of the requested changes, including
the old values and the new values after the changes were submitted.
550
Manual Neighbor List Optimization

The Neighbor List Editor enables you to:
 Easily and graphically plan and provision neighbor lists for planned or new sites that
do not have sufficient data to create a model that is reliable enough to be used for
automatic optimization.
 Easily modify and tweak Mentor’s automatically generated plans to reflect operational
and local constraints. These modifications are maintained as server-side constraints,
and will be used in future automatic optimization plans.
You can see the original neighbor list and also view all changes made to the neighbor list by
Mentor, in the Neighbor List Viewer pane. You can drill down to understand the reasoning
behind these changes, and if required, fine-tune the neighbor list by overriding the changes
and restoring deleted neighbors, adding or removing neighbors, or changing the neighbor
priority.
Using the Neighbor List Editor

You can use the Neighbor List Editor to manually create a new neighbor list plan, edit the
original neighbor list plan from the switch, or edit an existing neighbor list plan created by
Mentor. If required, you can revert the neighbor list plan to the original neighbor list plan from
the switch, or to the baseline plan.
To open the Neighbor List Editor

1. To edit an existing neighbor list plan, in the Calculations pane, right-click the
calculation you want to edit and then click Duplicate and Edit.
To edit the original neighbor list from the switch, on the Calculation menu, click New
> Manual Neighbor List Plan.
-OR-
On the Workflow toolbar, click the button and then select Manual
Neighbor List Plan on the drop-down menu.
551

Depending on the network and the type of manual neighbor list selected, the New
Manual Neighbor List Plan dialog box is displayed.
3. If required, enter a new name for the network, select the neighbor list type, and click
OK. The Neighbor List Editor is displayed.
Note: The tabs in the Neighbor List Viewer pane differ according to the optimization mode
selected.
Editing the Neighbor List Plan

The Neighbor List Editor enables you to manually fine-tune the original neighbor list from the
switch, as well as Mentor's recommended changes to an optimized neighbor list plan.
You can see the original neighbor list, and also view all changes made to the neighbor list by
Mentor, in the Neighbor List Editor pane. You can drill down to understand the reasoning
behind these changes, and if required, fine-tune the neighbor list by overriding the changes
and restoring deleted neighbors, adding or removing neighbors, or changing the neighbor
priority.
After you have made and saved your changes, you can export them to be implemented in the
switch.
To edit an existing optimized neighbor list plan

1. In the Calculations pane, right-click the neighbor list plan you want to edit and then
click Duplicate and Edit. The current plan will be left "as-is", and all changes will be
made to the new manual neighbor list.
552
2. Click Yes if you are prompted to save the network. The New Manual Neighbor List
Plan dialog box is displayed.
3. If required, enter a new name for the manual neighbor list plan, and click OK. The
Neighbor List Editor is displayed, with the Summary pane showing a list of all sectors
that were worked on in the neighbor list optimization. The details in the Summary
pane are based on the data that is also displayed in the HO Rate Change report.
553
4. Edit the neighbor list as required.

o Add neighbors
o Remove neighbors
o Change the neighbor priority
Any sectors that are affected by the manual optimization will be added to the list of
sectors in the Summary pane, and their statuses will be changed to Yes in the
Manually Changed column. In addition, the sector that is currently being edited will
be marked with in the first column, and all other sectors that are affected by this
change will be marked with .
5. Drill down into the Summary pane, reports, and legends to understand why a change
was made.
6. Click Save to save your changes and continue editing the neighbor list, or click the
drop-down arrow and then click Save and Close to save your changes and close the
Neighbor List Editor.
Editing the Original Neighbor List Plan from the Switch

The Neighbor List Editor enables you to manually fine-tune the original neighbor list from
the switch, as well as Mentor's recommended changes to an optimized neighbor list plan.
You can select the type of neighbor list to edit, and fine-tune the neighbor list by adding or
removing neighbors, or changing the neighbor priority.
After you have made and saved your changes, you can export them to be implemented in the
switch.
To edit the original neighbor list plan
1. On the Workflow toolbar, click the button and then select Manual
Neighbor List Plan from the drop-down menu. The New Manual Neighbor List Plan
2. If required, enter a new name for manual neighbor list.
554
3. If required, select the type of neighbor list to create, depending on your network and
the technology used.
o UMTS Intra-frequency: Neighbor list between neighbors in the same carrier
o UMTS Inter-frequency: Neighbor list between neighbors in different carriers
o UMTS/GSM: IRAT neighbor list
o Add neighbors
o Remove neighbors
Editing the Manual Neighbor List Plan

After you have created a manual neighbor list plan, you can make changes either directly to
the same plan, or you can duplicate the plan and then make your changes to the duplicated
plan.
To edit the manual neighbor list plan

1. In the Calculations pane, right-click the manual neighbor list plan you want to edit,
and then click:
o Edit to make your changes to the same plan
o Duplicate and Edit to make your changes to the duplicated plan
3. If you selected to first duplicate the network before editing the plan, the New Manual
Neighbor List Plan dialog box is displayed, enabling you to enter a new name for the
manual neighbor list. Click OK.
555
The Neighbor List Editor is displayed, with the Summary pane showing a list of all
sectors that were worked on in both the automatic and the manual neighbor list
optimizations.

o Add neighbors
o Remove neighbors
556
Neighbor List Editor Interface

The Neighbor List Editor contains the following window elements:
 Toolbar: Enables you to access the various Neighbor List Editor tools and their
options. For example, adding and removing neighbors, setting the reciprocity
methodology, and saving the plan. It also enables you to perform general operations,
such as searching for sectors and so on, on the sectors in the map display.
 Neighbor List Viewer pane: The Neighbor List Viewer pane contains two tabs:
o Final List: Contains the final neighbor list for this plan for a selected UMTS
sector, which will be provisioned to the switch if the neighbor list is exported.
o Detailed List: Shows the details of all possible and considered neighbors, with all
their available details. The neighbors include all neighbors that Mentor identified
as having more than zero handover counts from the source sector, even if they
are not in the neighbor list. The Detailed List tab also includes indications of
whether the neighbors were manually added, added through reciprocity rules, or
removed from the neighbor list. It also enables you to change the priority of
existing neighbors, or remove neighbors.
 Map area: Displays a two-dimensional map of the network, showing all sectors in
their actual geographical location. You can right-click any network element in the map
area to display related data, such as neighbors, site, sector, antenna element
properties, and so on.
 Summary pane: Summarizes the current changes for each sector in the network. In
case of a fully manual plan, only the manual edits are displayed.
 Status Bar: Displays information and messages relevant only to the current editing
activities. For example, when you try adding a neighbor and it fails, the reason will be
displayed in the status bar. You can double-click the status bar to get a full list of
errors and warnings received during the editing session.
If required, you can also display the Legend, Layers, and Sector Property Viewer panes by
clicking on the toolbar.
To display selected sectors in the Summary pane, open the Manual Neighbor List Editor,
right-click the sectors on the map, and then click Select Sector(s) in Summary. The relevant
sectors are selected and displayed at the top of the Summary pane.
557
Neighbor List Editor User Interface

The Neighbor List Editor is made up of the following GUI components:
 Toolbar
 Neighbor List Viewer Pane
 Summary Pane
 Status Bar
 Layers and Sector Property Viewer Panes
Toolbar
The toolbar enables you to define the manual changes to the neighbor list, such as adding
and removing neighbors, setting the neighboring reciprocity methodology, saving the plan,
and so on. It also enables you to perform various other operations, such as searching for
sectors.
Neighbor List Viewer Pane (in Neighbor List Editor)

The Neighbor List Editor contains an enhanced Neighbor List Viewer pane that enables you
to view details about the neighbor list of the sector that is currently selected on the map.
Note: If you have a multi-technology network, only the neighbors of UMTS sectors can be
viewed in the Neighbor List Viewer pane.
The Neighbor List Viewer pane contains two tabs:

 Final List: Contains the final neighbor list for this plan, which will be provisioned to
the switch if this neighbor list is exported.
 Detailed List: Displays a detailed list of possible neighbors that have at least 1
handover count from the source sector, even if they are not in the neighbor list. It also
includes indications of whether neighbors were manually added, added due to
reciprocity rules, or removed from the neighbor list.
558
Summary Pane
The Summary pane is displayed at the bottom of the Neighbor List Editor window. It displays
similar data to that in the HO Rate Change tab of the Neighbor List Summary report,
enabling you to view all sectors in the selection that were worked on during both the regular
and the manual neighbor list optimization (selection set).
The sector that is currently being edited is marked with in the first column, and all other
sectors that are affected by this change are marked with .
Any sectors that were edited during the manual neighbor list optimization are listed as such in
the Manually Changed column.
To highlight one or more sectors from the map in the Summary pane, right-click the sectors
and then click Select Sector(s) in Summary.
Status Bar
The status bar is displayed at the bottom of the Neighbor List Editor pane. If there are any
problems with the action you are currently trying to implement, an error or warning message
will be displayed on the status bar.
You can double-click in the status bar to display a list of all previous messages.
559
Viewing the Manual Neighbor List on the Map

You can view the manually edited neighbor list of a selected sector in the Final List tab in the
Neighbor List Viewer pane, or display it graphically by showing the outgoing neighbors on
the map. Mentor displays lines connecting the sector to its outgoing neighbors, and colors
these lines and the outgoing neighbors according to their priority.
To display the outgoing neighbors on the map
1. On the toolbar, click the arrow next to the Show Neighbors button and then
click Show Outgoing Neighbors.
The cursor changes to enabling you to select the sector whose outgoing
-OR-
Right-click the required sector and on the shortcut menu, click Show Neighbors and
then click Show Outgoing Neighbors.
The Show Outgoing Neighbors dialog box is displayed.
2. In the Neighbor plan field, select the plan according to which to display the outgoing
neighbors. By default, the neighbors will be shown according to the final plan, which
is the plan currently being edited. You can also select to view the baseline plan as
suggested by Mentor and on which the final plan is based, or the original plan from
the switch.
the map.
560
4. Click OK. The referenced sector is flagged, and the outgoing neighbors are
outgoing neighbors. If there are no outgoing neighbors, a message is displayed.
Adding Neighbors to the Neighbor List Plan

After you have reviewed the neighbor list plan, you can fine tune it by adding neighbors to the
plan. Any neighbors that are added are marked as manually added in the Neighbor List
Viewer pane and in the Final Changes legend, if displayed.
Notes:
 If Reciprocity required is selected in the toolbar, the new neighbor will be added to
the neighbor list only if an incoming handover from this sector can be added as well.
 The length of the manual neighbor list is defined by the UMTS_NL_LIMIT_TYPE
parameter.
 It is possible to add neighbors from different carriers, with the same SC.
To add a neighbor to the neighbor list

1. In the map area, click the sector to whose neighbor list you want to add a neighbor.
The sector is highlighted, its current neighbor list is displayed in the Neighbor List
Viewer pane, and a list of all sectors that were affected by the optimization is
displayed in the Summary pane.
561
2. On the toolbar, click . The cursor changes to , the sector is flagged and lines
are displayed to all its neighbors, colored according to outgoing priority.
3. Click each sector you wish to add as a neighbor. By default, the new neighbor will be
given the lowest available priority. In the Summary pane, the sector as well as the
incoming sector (if reciprocity is required or recommended) will be listed as manually
changed. The sector that is currently being edited is marked with in the first
column, and all other sectors that are affected by this change are marked with .
Note: If the sector cannot be added to the neighbor list, the reason is displayed in the
status bar at the bottom of the Neighbor List Editor. For example, adding the neighbor
will exceed the neighbor-list length limit.
562
Removing Neighbors from the Neighbor List Plan

After you have reviewed the neighbor list plan, you can fine tune it by removing neighbors
from the plan. Any neighbors that are removed are marked as manually removed in the
Neighbor List Viewer pane and in the Final Changes legend, if displayed.
Note: If Reciprocity required is selected in the toolbar, the incoming handover from this
neighbor will be removed as well.
To remove a neighbor from the neighbor list plan

1. In the map area, click the sector from whose neighbor list to remove a neighbor. The
sector is highlighted, and its current neighbor list is displayed in the Neighbor List
Viewer pane.
2. In the Neighbor List Viewer pane, right-click the sector you would like to remove
from the neighbor list, and then click Remove Neighbor.
-OR
On the toolbar, click . The cursor changes to , the sector is flagged and lines
are displayed to all its neighbors, colored according to outgoing priority.
3. Click the neighbor you want to remove. The neighbor is displayed as Removed on
the map and in the Final Changes legend, if displayed.
563
Changing the Neighbor Priority

You can change the incoming and outgoing priority of a selected sector in the Neighbor List
Viewer pane and in the map area.
To change the neighbor priority

1. In the Neighbor List Viewer pane, right-click the neighbor whose priority you want to
change, and then click Change Priority. The Change Priority dialog box is
displayed, showing the current outgoing and incoming priorities of the neighbor.
2. Change the incoming and/or outgoing priority, as required, and then click OK. The
neighbor appears with its new priority in the Neighbor List Viewer pane, and the
sector is listed as manually changed in the Summary pane. The priority of all other
neighbors affected by the change in priority is changed accordingly in the Neighbor
List Viewer pane.
Adding and Using Network Constraints

Any neighbor list constraints that were added during the manual neighbor list optimization can
be saved as constraints in the network to be used in all further optimization runs.
For example, you may want to define a specific COW (cell on wheels) site as always available
in the neighbor lists of specific sectors in the network. By default, Mentor's automatic neighbor
list plan will remove these sectors as they are not active and therefore do not have a
substantial handover count. Using the manual neighbor list editor, you can add the relevant
relations once, and then be assured that they will be maintained.
Saving Manual Changes as Constraints

To save a manual change as a constraint
1. Open the Neighbor List Editor.
o If you would like to edit an existing neighbor list plan, in the Calculations pane
right-click the existing calculation you want to edit, and then click Duplicate and
Edit.
o If you would like to edit the original neighbor list from the switch, on the toolbar
click the button and then select Manual Neighbor List Plan from
the drop-down menu.
564
2. In the Summary pane, select the sectors for which to add the constraints, and from
the Options menu click Add as Network Constraints. A confirmation message is
displayed.
3. Click Yes to save the changes as constraints.

4. If required, submit the changes to the server.
Using New Network Constraints in the Current Plan

To use the new network constraints in the current plan
1. In the Summary pane, on the Options menu, click Use Network Constraints in
Plan. A confirmation message is displayed.
2. Click Yes. A progress bar is displayed while the constraints are applied to the plan,
and then a dialog box is displayed notifying you about the success of this process.
565
3. If required, click Details to view a list of reasons for not importing or applying the
changes as constraints.
Reverting to the Original or Baseline Neighbor List Plan

You can cancel the proposed neighbor list changes for specific sectors by reverting to their
original neighbor lists from the switch, or if manual changes were made, to the baseline plan
calculated by Mentor.
To revert neighbor lists to the original neighbor plan

1. In the Neighbor List Editor Summary pane, select the sectors whose neighbor lists
you want to revert, and on the Options menu click Revert to Original Plan (from
Switch). A confirmation message is displayed.
2. Click Yes. The neighbor lists will be reverted to their pre-optimized state.
To revert manually edited neighbor lists to the baseline neighbor list plan
1. In the Neighbor List Editor Summary pane, select the sectors whose manually
changed neighbor lists you want to revert, and on the Options menu, click Revert to
Baseline Plan (<name>). A confirmation message is displayed.
2. Click Yes. The neighbor lists will be reverted to their optimized state, before the
manual changes.
566
Manual Neighbor List Report

The Manual Neighbor List report enables you to view the changes made to the neighbor list,
both by the Neighbor List optimization wizard and manually in the Neighbor List Editor. The
report is generated as soon as you save your manual changes to the neighbor list.
The manual neighbor list plan reports are the same as the automatic neighbor list reports, but
also include an additional column indicating whether or not the change was introduced by a
manual edit.
To view the manual neighbor list reports

 In the Calculations pane, right-click the manual neighbor list plan whose reports you
want to view, and then click Open Reports. The Manual Neighbor List report is
displayed.
The Manual Neighbor List report contains the following tabs:
 HO Rate Change, which summarizes the neighbor list optimization process for each
sector, and shows the calculated difference in the HO rate between the final neighbor
list and the original neighbor list. Sectors that were manually changed in the Neighbor
List Editor are marked as such in the Manually Changed column.
 Carrier <#>, which contains a detailed analysis of the new neighbor list plan, and can
be used to trace all neighbor list issues, for example, missing neighbors, Co-SCs,
locked priorities, and so on. This tab includes all the source sectors, including the
sectors that were not optimized due to a low handover count, unidentified neighbors,
or Co-SCs. Sectors that were manually changed in the Neighbor List Editor are
marked as such in the Manually Changed column.
 Details, which shows the name of the network, the date and time the report was
For a detailed description of the tabs and fields in the manual neighbor list reports, refer to the
Ultima Mentor Help.
Exporting the Neighbor List Changes (UMTS Only)

Once you have run the neighbor list optimization and are satisfied with the results, or fined-
tuned the results using the Neighbor List Editor, you can export the changes to be
implemented in the network. Before the plan is exported, the switch dumps are read to ensure
that the most recent parameters are used.
You can export all the neighbor list entries, or select the number of most significantly changed
entries to export.
Note for ASSET: Ensure that the CREATE_ASSET_XML_FILE parameter is set to

Yes.

1. In the Calculations pane, select the neighbor list plan whose changes you want to
export.
-OR-
567
neighbor list change files.
568
import process.
5. If required, you can limit the number of lists to export by selecting the No. of most
significantly changed neighbor lists to export check box in the Filter area, and
then entering a value in the field provided. Mentor will export the selected number of
neighbor lists with the most significant changes.
569
8. If required, click Open Folder to open the folder containing the exported files. If you
have a multi-vendor network, a folder is displayed for each network.
Ericsson and Nokia networks: An .xml file is created for the sectors that have been
deleted from the neighbor list, and for those that have been added.
Huawei networks: A .txt file is created for the sectors that have been deleted from
the neighbor list, and for those that have been added.


validate.
Implementation.
-OR-
570

571
Antenna Sectors Optimization (UMTS Only)

The network antenna sectors plan is optimized within Mentor, based on a model consisting of
data retrieved from RNC call-trace data and KPIs. Mentor uses the Genetic Algorithm (GA) to
find the best solution, according to predefined goals. This provides noise and interference
reduction, balanced traffic, and optimal power consumption in the cluster.
Note for NSN networks: You can run the Antenna Sectors Optimization only if your license
supports call trace–based modeling.
The pilot channel is the main overhead channel of each sector. It enables the mobile to
acquire the network, it triggers the handover procedure, and it indicates the serving range of
the sector. The mobile uses the pilot’s received power vs. the noise level (Ec/Io) to assess its
chances of successfully using the signals from the sector transmitting that pilot.
In order to improve the quality of the network, you can change (increase/decrease) the power
in some of the sectors. This is usually carried out in several sessions by the field engineer,
who looks for the best local power solution among several sectors and power settings.
However, as sectors usually have a high level of mutual interaction between them, optimizing
one area may cause degradation in other areas, making it very difficult to find the best
combination of changes.
The following examples show how optimizing the power and tilt can improve your network:
 Increasing the CPICH power can increase the pilot dominance in areas where this is
necessary. Reducing the CPICH power can reduce the influence of polluting sectors
that pollute wide areas of the cluster, for example, "umbrella sectors".
 CPICH power optimization can be used for load sharing or load balancing between
neighboring sectors. It can be used for balancing or saving traffic resources, for
example, RF resources such as OVSF Codes, or physical resources such as channel
elements.
 CPICH optimization can be used for reducing the power consumption in power-
overloaded sectors. Because the traffic-power control mechanism responds to the
overhead channel power and interference level from other sectors, reducing the
CPICH power usually reduces the traffic power levels as well.
 CPICH optimization reduces the handover factor. Reducing the pilot pollution and
improving the pilot dominance reduces the handover zones and the interfering zones.
Note: It is very important that the neighbor list is well optimized across the entire network
before running the antenna sectors plan optimization. Mentor uses a model, based mainly on
PSMM/RU messages, for the antenna sectors optimization. If the neighbor list is not properly
planned, pilots that are missing from the neighbor list will not be identified by the mobiles, and
therefore will not appear in the PSMM and RTD messages, resulting in a less accurate RF
model of the network.
572
Goals
By defining optimization goals, you "steer" the Optimizer engine to optimize the network in a
certain direction, to help you locate the best solutions for solving specific network issues and
achieving specific targets.
Mentor includes two predefined goals—Coverage and Quality, and Capacity—each with
their own sub-goals, which represent the KPIs in the network. You can choose to optimize the
network using these predefined goals, or you can define your own goal, with sub-goals that
you choose and define. Mentor will find the best possible solutions for optimizing the network,
based on the selected goals.
 Optimizing Coverage and Quality: The aim of the Coverage and Quality goal is to
minimize the number of UEs that will not be able to initiate or sustain a conversation.
It instructs Mentor to find the best possible solutions for improving the network, while
giving emphasis on improving the network coverage and quality.
This goal uses message-based sub-goals, which consider messages from the RF
Message Model (messages with a leg to a sector in the calculation set).
 Optimizing Capacity: The aim of the Capacity goal is to reduce the network-
resource utilization (power usage) while maintaining quality of service, thereby freeing
up capacity for more traffic, especially HSDPA traffic. It instructs Mentor to find the
best possible solutions for improving the network, while giving emphasis on improving
the network capacity.
This goal uses sector-based sub-goals, which consider the sectors in the calculation
set.
Sectors outside the selected areas are also considered in order to prevent creating a negative
impact on the surrounding area.
If you prefer to customize your own goals, you can set the thresholds for the selected sub-
goals. The sub-goals that appear in the Sub-Goals area are inherited from sub-goals that
were defined in the past. If the new user-defined goal is based on an existing goal, you can
edit it.
Note: There is always a trade-off between network performance metrics when optimizing the
network. Because sectors usually have a high level of mutual interaction between them,
optimizing one area may cause degradation in other areas. Traditionally, there has been a
trade-off between optimization sub-goals but Mentor can, for example, improve capacity while
maintaining the current coverage and quality levels.
Sub-goals
Mentor can optimize more than one sub-goal simultaneously. Based on the targets that you
set, Mentor creates a network that concurrently meets your mix of coverage and quality, and
capacity needs. Traditionally, there has been a trade-off between optimization sub-goals but
Mentor can, for example, improve capacity while maintaining the current coverage and quality
levels.
Coverage and quality sub-goals
The aim of the Coverage and quality goal is to minimize the number of UEs that will not be
able to initiate or sustain a conversation. This goal instructs Mentor to find the best possible
solutions for improving the network, while taking into consideration the Coverage and quality
goals.
573
Capacity sub-goals
The aim of the Capacity goal is to reduce the network resource utilization (power usage, soft
handover factor) while maintaining coverage and quality, thereby freeing up capacity for more
traffic, especially HSDPA traffic. This goal instructs Mentor to find the best possible solutions
for improving the network, while taking into consideration the Capacity goal.
The following table describes the sub-goals used in the Coverage and quality goal, and the
Capacity goal:
Goal Sub-goal Description
Coverage Improve RSCP The aim of the Improve RSCP sub-goal is to

and quality (dBm) improve the RSCP values of the messages in
the RF Messages model that refer to a sector
(Default threshold: -
in the optimization's calculation set.
100)
The RSCP sub-goal defines a target
threshold, and the Optimizer engine optimizes
the network so that the RSCP values of a
maximum number of terminals will be above
this value.
Reduce Service The aim of the Reduce Service Denied sub-

Denied (%) goal is to reduce the amount of traffic that is
rejected due to lack of resources.
(Default threshold:
Medium)
Improve Ec/Io (dB) The aim of the Improve Ec/Io sub-goal is to

improve the Ec/Io values of the messages in
10)
The Ec/Io sub-goal defines a target threshold,
and the Optimizer engine optimizes the
network so that the Ec/Io values of a
this value.
574
Goal Sub-goal Description
Capacity Improve RSCP The aim of the Improve RSCP sub-goal is to

(dBm) improve the RSCP values of the messages in
100)
The RSCP sub-goal defines a target
threshold, and the Optimizer engine optimizes
the network so that the RSCP values of a
this value.
Improve Ec/Io (dB) The aim of the Improve Ec/Io sub-goal is to

improve the Ec/Io values of the messages in
10)
The Ec/Io sub-goal defines a target threshold,
and the Optimizer engine optimizes the
network so that the Ec/Io values of a
this value.
Reduce Power The aim of the Reduce Power Usage sub-

Usage (%) goal is to reduce the percentage of sectors
with average transmitted power above the
(Default threshold:
sub-goal target threshold, where the average
70)
transmitted power after change is according
to Mentor's predictions.
The target threshold is set as a fraction of the
maximal PA power for each sector.
Tuning RF Optimization Strategy

Mentor optimization parameters are preconfigured using the most common RF optimization
strategy. You should evaluate the following key parameters to consider whether they need
adjustment for your specific environment.
 Total Power: Mentor automatically verifies that the total sector power does not
exceed the MAX_PA_POWER parameter, defined in the Carriers.txt file in Mentor
Format.
 OVSF Usage: When changing the power you can increase the coverage area of the
sector. Mentor verifies that the OVSF usage limits are not exceeded.
 Network-wide CPICH Power Change Range: When running an optimization, you
should define a range of possible power changes per sector, -3 to +2dB (default =
1dB) and the step increase, 0.06 to 2dB (default = 0.5 dB). In addition, you should
define the absolute minimum and maximum CPICH power, 15dBm to 46dBm (default
= 27.2 to 35.7 dBm), based on CPICH-power limits derived from the TPTLTPO range
of typical values.
 Local Power Limitations: You should define the maximal and minimal power for
specific sectors based on known local constraints, for example, in-building sectors,
strategic customers and so on.
575
Launching the Antenna Sectors Optimization Wizard

After you have created a model based on the call-trace data recorded after the
implementation of the optimized neighbor list plan, you can run the Antenna Sectors
Optimization wizard to optimize the network power. If your model contains positioning, and
there is terrain data for all the antennas in the calculation set, you can also optimize the tilt.
By default, the antenna sectors optimization is run on the selection set used in the model, but
if required, you can select a sub-set of these sectors to be used for the optimization.
To launch the Antenna Sectors Optimization wizard

1. On the Calculation menu, click New > Antenna Sectors Plan.
-OR-
On the Workflow toolbar, click the button and then select Antenna
Sectors Plan from the drop-down menu.

The first step of the Antenna Sectors Optimization wizard is displayed, enabling you
to define the general properties of the antenna sectors plan.
The Antenna Sectors Optimization wizard contains the following steps:

 Step 1 General, enables you to define general properties for the optimization, for
example, the name of the optimization.
 Step 2 Goals, enables you to define the goal of the optimization.
 Step 3 Constraints, enables you to set constraints for the CPICH power parameters,
and to generate the Constraints report, which enables you to view the constraints
Mentor will consider during the optimization process. If your model includes
positioning, and there is a terrain map for all the antennas in the selection set, you
can also set the tilt.
 Step 4 Budget, enables you to set a budget for the tilt optimization.
check to fail.
576
Defining General Optimization Properties

The General page of the Antenna Sectors Optimization wizard enables you to define
general properties for the antenna sectors plan, as well as to select the model date range to
be used.
To define the general properties of the antenna sectors optimization plan

1. In the Name field, enter a name for the new optimization plan. If you do not enter a
name, the default name is used.
2. If you are using a specific template you can browse to it by clicking the browse button
in the Template field. If you have used a template in a previous optimization, you
can select the template from the Template drop-down list.
577
4. Click Next to proceed to the Goals page, where you can define the goals of the
antenna sectors optimization.
578
Defining the Optimization Goals

The Goals page enables you to define the major objectives of the antenna sectors
optimization. These objectives are comprised of several sub-goals. It is important to note that
since there is always a trade-off between network performance, quality, and capacity, defining
very aggressive targets for some metrics may result in the degradation of others.
When defining the goals, you can decide whether to optimize the coverage and quality, or
capacity functionality of the network using predefined default goals, or define your own
customized optimization goals according to your specific requirements.
To use predefined default goals

1. Select the main goal of the optimization: Coverage and quality or Capacity. The
respective predefined sub-goals and their threshold and are listed in the Sub-Goals
area.
579
2. If required, click Edit to change the properties of a selected sub-goal, or click Save to
save the sub-goal.
3. Click Next to proceed to the Constraints page, where you can define limitations for
the CPICH power, RAB power, and tilt.
580
To customize the optimization goals

1. Select Customized goal. You are prompted to add the sub-goals for the
optimization.
2. Click Add to add a sub-goal. The Add Sub-Goal dialog box is displayed.
3. From the Sub-Goal drop-down list, select a sub-goal for the optimization. You can
select one or more of the following sub-goals:
o Improve RSCP (dBm)
o Reduce Service Denied
o Improve Ec/Io (dB)
o Reduce Power Usage (%)
4. If required, select the Maintain check box to ensure that the original value of a sub-
goal is maintained.
Note: If you select the Maintain option for all the sub-goals, none of them will be
optimized, and the Optimizer will not find any best solutions. A warning for this will be
displayed when you view the details of the errors or warnings, in the Summary page.
5. From the Priority drop-down list, select a priority for the selected sub-goal.
Note: When you have selected a number of sub-goals, check the priorities that have
been assigned and adjust them if necessary. If the priorities of all the sub-goals are
the same, for example Medium, the priority has no effect on the optimization.
6. Enter a target threshold for the optimization in the Parameters area.
7. Click OK. The sub-goal is added to the list of sub-goals to be optimized in the Sub
Goals area.
8. Repeat this procedure for each sub-goal you want to add.
581
9. If required, you can also:

o Edit a sub-goal
o Remove a sub-goal
o Save a sub-goal
o Load a sub-goal
Editing Sub-Goals
When customizing the sub-goals, you can edit any previously-defined or previously-loaded
sub-goals.
To edit a customized sub-goal

1. Select the sub-goal to be edited.
2. Click Edit. The Edit Sub-Goal dialog box is displayed.
3. Edit the fields as required:

o Select the Maintain check box to ensure that the original value of a sub-goal is
maintained.
Note: If you select the Maintain option for all the sub-goals, none of them will be
optimized, and the Optimizer will not find any best solutions. A warning for this will
be displayed when you view the details of the errors or warnings, in the Summary
page.
o From the Priority drop-down list, select a priority for the selected sub-goal.
Note: When you have selected a number of sub-goals, check the priorities that
have been assigned and adjust them if necessary. If the priorities of all the sub-
goals are the same, for example Medium, the priority has no effect on the
optimization.
o Enter a target threshold for the optimization in the Parameters area.
582
4. Click OK.
5. Repeat this procedure for each sub-goal you want to edit.
Setting Optimization Constraints

The Constraints page enables you to define the permitted constraints for the CPICH and
RAB power parameters, for all the sectors included in the selection set. If your model contains
positioning and you have terrain data for all the antennas in the calculation set, you can also
set the tilt constraints.
Note: Tilt parameters are displayed only for KMW and Powerwave antenna profiles.
If there are sectors and antennas that do not conform to the global settings and have unique
ranges and restrictions, they can be defined specifically for individual sectors or a selection of
sectors. All these specific restrictions can also be exported to a file and later used in other
networks.
Note: When there is a conflict between the constraints set in the Antenna Sectors
Optimization wizard and those set in the sector's properties, the range of common values is
used.
If required, you can generate a Constraints analysis report that states the final constraints that
Mentor will consider during the optimization process. These limits are provided in terms of
minimum and maximum values for each sector.
By default, Mentor applies the same relative power changes to all the carriers being
optimized, both underlay and overlay, taking into account all the mobile measurements, and
providing the best possible plan for all the carriers.
583
To set the power and tilt constraints:

1. In the CPICH Power (dBm) area, set the following power parameters, as required:
o Clear the Optimize check box if you do not want to optimize the power.
o In the Absolute min field, enter the minimum power at which the pilot can
transmit.
o In the Absolute max field, enter the maximum power at which the pilot can
transmit.
o In the Max increase field, enter the maximum power by which the power can
increase on a single sector.
o In the Max decrease field, enter the maximum power by which the power can
decrease on a single sector.
o In the Step field, enter the size, in dB, in which the incremental increase or
decrease adjustments are made. For example, enter 0.5 to define that the power
can be increased or decreased by a multiplication of 0.5 dB at a time. (0.5 dB, 1.0
dB, 1.5 dB, 2.0 dB, and so on.)
o If you do not want Mentor to apply the same relative power changes to all sectors
belonging to the same antenna, clear the Apply same power changes to all
associated sectors check box.
Notes:
 If you have selected to optimize only one carrier, this option is disabled.
 This option should not be changed, unless it is clear that different plans per
carrier must be created.
2. In the RAB Power area, select the Optimize check box if you want to optimize the
RAB power settings for the sectors in the selection set. Optimizing the RAB power
improves network performance by allowing more power for mobiles in problem areas,
and improves network capacity by reducing sector power.
3. In the Tilt (deg) area, set the following parameters, as required:
o Select the Mechanical tilt Optimize check box to enable optimization of the
mechanical tilt, and then in the Step field, enter the size, in degrees, in which the
incremental increase or decrease adjustments are made. For example, enter 1 to
define that the tilt can be increased or decreased by steps of 1 degree at a time.
(1 degree, 2 degrees, 3 degrees, and so on.)
o Select the Electrical tilt Optimize check box to enable optimization of the electrical
tilt.
o In the Total tilt area, in the Absolute min field, enter the minimum value by which
the total (mechanical and electrical) tilt can be changed.
o In the Absolute max field, enter the maximum value by which the total
(mechanical and electrical) tilt can be changed.
o In the Max uptilt field, enter the maximum value by which an antenna can be
lifted.
o In the Max downtilt field, enter the maximum value by which an antenna can be
lowered.
4. Click Constraints Analysis to generate a Constraints report that shows the
aggregated constraints that Mentor will consider during the optimization process. A
progress bar is displayed while the report is being generated.
5. Click Next to proceed to the Budget page, where you can set a budget for the
optimization parameters.
Note: The Budget page is disabled if you have selected to optimize only the power.
584
Setting the Optimization Budget

In the Budget page you can define whether to set a budget for the tilt optimization, and if so,
the factors by which it is determined. You can also specify the cost of accessing each site,
and of changing the mechanical and/or electrical tilt, per antenna.
To set the optimization budget

1. In the Budget area, select the Limit budget check box.
2. Select whether to limit the budget according to the number of sites that are accessed,
or according to the total cost incurred for the changes.
3. In the Cost area, in the Access to site field, enter the cost for accessing a single
site. This is required for all changes per site, except power.
4. In the Mechanical tilt change field, enter the cost for changing the mechanical tilt,
per antenna. (If the profile does not specify TILT ELECTRICAL in the header, the tilt
is mechanical.)
5. In the Electrical tilt change field, enter the cost for changing the electrical tilt, per
antenna.
585
Viewing the Optimization Summary

The Summary page enables you to view a summary of the optimization. It shows the number
of sectors included in the optimization selection set, as well as the actual number of sectors
that will be optimized. It also includes the data consistency check, which shows the data
inconsistency errors and warnings. You can go back and change any parameters, if required.
You can view the details of the inconsistencies, and save these details for analyzing at a later
stage.
running the antenna sectors optimization.

1. If there are data inconsistencies, click the Details button. The Details dialog box is
displayed, showing a list of errors and warnings.
2. To save the antenna sectors optimization template for future use, click Save. A
standard Save dialog box is displayed.
optimizations.
586
3. Click Finish to run the optimization. The status of the optimization is displayed as
Running at the top of the Calculations pane.
The Optimization Progress dialog box is displayed, enabling you to view the details
and progress of the optimization.
4. Click Stop to stop the optimization. A confirmation dialog box is displayed. Click Yes
to stop the optimization.
Note: Stopping the optimization stops the search for a better solution, and the current
best solution is the one that should be reviewed, and then implemented.
-OR-
Click Close to close the Optimization Progress dialog box, and continue running the
optimization in the background.
587
Antenna Sectors Optimization Layers

The antenna sectors optimization layers show the optimization changes, per carrier, for the
current best solution. You can load and display the layers on the map immediately after
stopping the optimization, or any time afterwards.
To load the antenna sectors optimization layers

1. In the Calculations pane, right-click the antenna sectors optimization whose layers
you want to load. On the shortcut menu, click Load Layers.
-OR-
In the Calculations pane, select the antenna sectors optimization whose layers you
want to load, and then from the Calculation menu, click Load Layers.
The <Optimization> Layers dialog box is displayed, showing a list of the available
layers, according to the carriers and parameters that were optimized.
Depending on the environment and the selected optimization type, you can display
the following layers for the current best solution:
o Best Server Cell Name, which enables you to view the existing or current
coverage area of the best server sectors before optimization.
Note: This layer cannot be displayed for a network that has been upgraded.
o Electrical Tilt Changes, which enables you to view the sectors with electrical tilt
changes, and the extent of the changes.
o Max Power RAB Changes, which enables you to view changes to the maximum
allowed speech RAB power.
o Max Power RAB New Values, which enables you to view the new values
suggested for the maximum speech RAB power.
o Mechanical Tilt Changes, which enables you to view the sectors with
mechanical tilt changes, and the extent of the changes.
o Min Power RAB Changes, which enables you to view changes to the minimum
allowed RAB power.
o Min Power RAB New Values, which enables you to view the new values
suggested for the minimum RAB power.
o Power Changes, which enables you to view the sectors with power changes, and
the extent of the changes.
588
o Predicted Best Server Map, which enables you to view the predicted coverage
area, after the optimization.
o Predicted RSCP Changes Map, which enables you to view the predicted power
changes, after the optimization.
button is enabled.
4. After you have loaded the selected layers, click Close to close the <Optimization>
Layers dialog box.
5. In the Layers pane, select the check box next to the name of the layers to be
589
7. You can edit the legend by clicking the browse button . The Legend Layer dialog
box is displayed.
To hide the optimization layers

590
Viewing the Optimization Progress

As soon as the antenna sectors optimization starts running, the Optimization Progress
dialog box is displayed, enabling you to view the current progress of the optimization process.
If you have restarted an optimization, it shows the progress from the point at which the
optimization was stopped. By default, the Optimization Progress dialog box is displayed in its
compact format, but you can expand it to view more details. You can also close the
Optimization Progress dialog box at any time during the optimization, without stopping it.
To view the optimization progress

progress you want to display, and on the shortcut menu, click Open Optimization
Progress Dialog. The Optimization Progress dialog box is displayed.
From the Optimization Progress dialog box, you can do the following:
o Stop or Start the optimization. When you restart the optimization, it continues
looking for a better solution from the same point at which it was stopped.
o Click Properties to view the optimization properties.
o Click Changes to view the recommended changes and their optimized values.
o Click Reports to display a list of available reports.
591
o Click Details to display two tabs with additional information about the optimization
progress:
 Best Solution: Shows the best solution reached so far, showing the
improvement of each of the selected sub-goals.
 Improvement Progress: Shows a graph displaying the improvement progress
for each sub-goal, and the total improvement.
Viewing the Optimized Changes

You can view a list of network elements to which Mentor recommends applying changes, as
well as the optimized value of these elements both before and after the changes
recommended in the current best solution. If required, you can save the list to analyze in the
future.
To view the recommended changes

1. In the Optimization Progress dialog box, click Changes in the Best Solution area.
The Optimized Values dialog box is displayed, showing a list of network elements to
which Mentor recommends making changes, and their values before and after the
current best solution.
2. Click Export to save the list of changes to analyze it at a later stage. The Save Plan
3. Browse to the location in which to save the file, and click Save. A confirmation
message is displayed, notifying that the plan was successfully saved.
Note: Exporting the changes converts the changes to a *.txt or *.xls file for analysis
purposes only. This does not export the antenna sectors plan for implementation.
4. Click OK to close the dialog box.
592
Viewing the Optimization Reports

The optimization reports show the results of the antenna sectors optimization. You can view
the reports as soon as a best solution has been found, and you can save the reports.
To view an antenna sectors report

1. In the Optimization Progress dialog box, click Reports.
-OR-
In the Calculations pane, right-click the antenna sectors optimization whose reports
you want to view, and then select Open Reports on the shortcut menu.
-OR-
In the Calculations pane, select the antenna sectors optimization whose reports you
available reports, depending on the optimization:
There are five available reports, two reports that are generated for each carrier in the
selection set, and three general reports:
o Carrier <ID> Calculation Set Statistics, which displays statistics for the sectors
included in the calculation set.
o Carrier <ID> Selection Set Statistics, which displays statistics for the sectors
included in the selection set.
o Constraints Analysis, which displays the constraints that Mentor will consider
during the optimization process.
o Summary, which displays a summary of the optimization process, including the
changes in the power and tilt.
o Sector Analysis, which displays all statistics aspects related to the optimization.
Help.
593
Viewing the Best Solutions

You can view the best solution reached so far, as well as the percentage of improvement, for
each of the sub-goals you selected in the Goals page of the Optimization wizard.
To view the best solutions

1. In the Optimization Progress dialog box, click Details. The dialog box expands, and
by default, the Best Solution tab is displayed.
Each sub-goal's name incorporates the sub-goal’s parameters. For example, if the
sub-goal is Improve Ec/Io and the target value is -10 dB, the sub-goal is displayed
as Mobiles with Ec/Io > -10 dB.
You can compare the pre-optimization value with the latest value based on the
current best solution, as well as see the percentage by which the sub-goal has
improved.
Each sub-goal is color-coded, so that you can follow the improvement progress on
the graph in the Improvement Progress tab.
2. Click Hide to return to the compact display.
Viewing the Improvement Progress

You can view the improvement progress of the optimization in the Improvement Progress
tab. By default, the overall improvement is displayed, but you can also display the progress
for each of the selected sub-goals.
To view the improvement progress

1. In the Optimization Progress dialog box, click Details. The dialog box expands, and
by default, the Best Solution tab is displayed.
594
2. Click the Improvement Progress tab. By default, the overall improvement of the
antenna sectors optimization is displayed.
3. Select the check box next to the sub-goals whose optimization you want to view. A
color-coded graph is displayed, enabling you to see the progress of each sub-goal.
4. By default, all the best solutions are displayed, but you can limit the number of best
solutions to view by selecting the number of solutions from the View no. of best
solutions drop-down list.
5. By default, the graphs show the progress in terms of best solutions, but you can also
view the progress according to the number of evaluations by selecting this from the
Display progress by drop-down list.
6. Click Hide to return to the compact display.
595
Viewing the Optimization Reports

The optimization reports show the results of the antenna sectors optimization. You can view
the reports as soon as a best solution has been found, and you can save the reports.
To view an antenna sectors report

1. In the Optimization Progress dialog box, click Reports.
-OR-
In the Calculations pane, right-click the antenna sectors optimization whose reports
you want to view, and then select Open Reports on the shortcut menu.
-OR-
In the Calculations pane, select the antenna sectors optimization whose reports you
available reports, depending on the optimization:
There are five available reports, two reports that are generated for each carrier in the
selection set, and three general reports:
o Carrier <ID> Calculation Set Statistics, which displays statistics for the sectors
included in the calculation set.
o Carrier <ID> Selection Set Statistics, which displays statistics for the sectors
included in the selection set.
o Constraints Analysis, which displays the constraints that Mentor will consider
during the optimization process.
o Summary, which displays a summary of the optimization process, including the
changes in the power and tilt.
o Sector Analysis, which displays all statistics aspects related to the optimization.
Help.
596
Implementing the Antenna Sectors Optimization Plan

After you are satisfied with the antenna sectors plan optimization results, you can export the
files so that the optimized plan can be implemented. These files include only the sectors that
have been changed.
Note: After the optimized plan has been implemented, you should collect the call-trace data
and then re-analyze the network to ascertain whether the neighbor list should be optimized
again, according to the new data.
Exporting the Power Plan

You can export the power plan files so that the optimized power plan can be implemented.
These files include only the sectors that have been changed. Before the plan is exported, the
switch dumps are read to ensure that the most recent parameters are used.
In Ericsson networks, you can also export the E-Tilt files so that the optimized E-Tilt can be
implemented.
Note: After the optimized power plan has been implemented, you should collect the call-trace
data and then re-analyze the network to ascertain whether the neighbor list should be
optimized again, according to the new data.
To export the power plan files

changes you want to export, and on the shortcut menu, click Export Plan.
-OR-
Select the antenna sectors optimization, and on the Calculation menu, click Export
Plan.
The Export Power Plan dialog box is displayed, enabling you to select the location of
the latest switch dump data, and the directory to which to export the power plan files.
597
exported power plan. Also, some information required for provisioning is available
only in the switch dumps, and is not saved to the environment during the import
process.
which to export the power plan results.
4. Click OK. If you have previously exported the power files, a confirmation message is
displayed warning that existing files may be overwritten. Click Yes to continue. A
progress bar is displayed while the power plan is validated, and then the Export Plan
A text file is created for each of the RNCs in the network, listing the details of the
sectors in the Node B, as well as the optimized power changes (in the TPTLTPO
column) and the CBTH and MPTTPR values. These files are in an executable format
that can be processed by the network elements. A rollback script is also created,
enabling you to roll back to the original power plan if required.
Exporting the Antenna Sectors Plan

You can export the power and E-Tilt plan files so that the optimized plans can be
implemented. These files include only the sectors that have been changed. Before the plan is
exported, the switch dumps are read to ensure that the most recent parameters are used.
Notes:
 This is relevant for Ericsson networks only.
 After the optimized plans have been implemented, you should collect the call-trace
data and then re-analyze the network to ascertain whether the neighbor list should be
optimized again, according to the new data.
598
To export the antenna sector plan files

changes you want to export, and on the shortcut menu, click Export Plan.
-OR-
Select the antenna sectors optimization, and on the Calculation menu, click Export
Plan.
The Export Plan dialog box is displayed, enabling you to select the location of the
latest switch dump data, and the directory to which to export the plan files.
exported plan. Also, some information required for provisioning is available only in the
switch dumps, and is not saved to the environment during the import process.
click the browse button in the Ericsson configuration field to browse to the
location of the latest switch dump data.
which to export the power plan results.
4. Click OK. If you have previously exported the power files, a confirmation message is
displayed warning that existing files may be overwritten. Click Yes to continue. A
progress bar is displayed while the power plan is validated, and then the Export Plan
A text file is created for each of the RNCs in the network, listing the details of the
sectors in the Node B, as well as the optimized power and E-tilt changes. These files
are in an executable format that can be processed by the network elements. A
rollback script is also created, enabling you to roll back to the original plan if required.
599




validate.
Implementation.
-OR-
600



-OR-
Optimization Task.
601
Parameters Plan Optimization

Depending on your network vendor, Mentor enables you to optimize certain parameters to
improve the network.
 Ericsson Networks: Optimizing the CQI Parameters
The Channel Quality Indicator (CQI) is a 5-bit number between 0 and 30 that
indicates to the system the level of coding and modulation the user equipment (UE)
can handle in its present RF conditions. Mentor enables you to optimize this
parameter statically or dynamically to improve its precision and utilize its entire range,
in order to improve the feedback the HSDPA UE gives the sector to which it is
connected. By improving the quality of the CQI, both the UE's and the system's
HSDPA throughput can be improved, as well as the system's resource consumption
and efficiency.
The parameters plan optimization enables you to optimize the following HSDPA
parameters:
o hsMeasurementPower: CQI correction based on HS-DSCH power resources
o CqiAdjustmentOn: Dynamic CQI correction based on ACK/NACK
o deltaCqi1: CQI Tx power offset with uplink DPCCH in single or softer handover
o deltaCqi2: CQI Tx power offset with uplink DPCCH in soft handover
 Huawei Networks: Optimizing the SHO Quality Threshold Parameters
The SHOQualMin parameter defines the minimum Ec/Io quality required for a target
sector to be included in a soft handover. Below this threshold, the RNC will not
receive the ACK message from the UE, and therefore the handover will be rejected
and the call will be dropped.
The parameters plan optimization reduces the number of unacknowledged handover
requests by preventing links with bad quality from being added or requesting to be
added to the active set. It sets the minimum quality required for any leg requesting to
be added to the active set, based on the Ec/No distribution and the RF loss.
The optimization enables you to optimize the minimum and maximum range for the
SHOQualMin parameter threshold—Min. SHO quality threshold and Max. SHO
quality threshold.
 NSN Networks: This feature is currently not supported.
Launching the Parameters Optimization Wizard

You can launch the Parameters Optimization wizard, which guides you through the process of
planning and optimizing the parameters, at any time during the network optimization phase.
By default, the optimization is carried out on the selection set used in the model, but you can
change this by selecting a sub-set of the original selection set.
Note: Only sectors for which there is a model can be included in the optimization. If your
selection includes sectors for which there is no model, you will be able to run the optimization
on the rest of the sectors in the selection, which are included in the model.
602
To launch the Parameters Optimization wizard

1. On the Calculation menu, click New > Parameters Plan.
-OR-
On the Workflow toolbar, click the button and then select Parameters
Plan from the drop-down menu.

The first step of the Parameters Optimization wizard is displayed, enabling you to
define the general properties of the parameters plan.
The Parameters Optimization wizard contains three steps:

 Step 1 General, enables you to define general properties for the parameters plan, for
 Step 2 Parameters, enables you to select the Ericsson or Huawei parameters to be
optimized.
 Step 3 Summary, enables you to view a summary of the data consistency check,
and enables you to go back and change any parameters that are causing the
consistency check to fail.
603
Defining General Parameter Plan Properties

The General page of the Parameters Optimization wizard enables you to define general
properties for the parameters plan, as well as to filter the call-trace data used.
To define the general properties of the parameters plan

1. In the Name field, enter a name for the new parameters plan.
604
4. Click Next to proceed to the Parameters page, which enables you to select the
Ericsson parameters, or define the Huawei parameters, to be optimized.
Selecting the Parameters to be Optimized (Ericsson Networks)

The Parameters page enables you to select the parameters to be optimized. Currently, for
Ericsson networks, Mentor supports the optimization of the following CQI parameters:
605
To select the parameters to be optimized

1. Select the check box next to the parameters to be optimized:
o CQI offset: In channel quality estimation, the total received HS-PDSCH power
can be different from the available HS-PDSCH power calculated by the DSDPA
scheduler. The CQI offset parameter enables Mentor to correct the CQI reading
and use the entire range of CQI values. (Parameter to be optimized:
hsMeasurementPowerOffset)
o CQI dynamic adjustment: Enables Mentor to dynamically correct the CQI, based
on the NACK_TARGET_RATIO_THRESHOLD parameter. If this ratio is at the
10% threshold, or lower, the parameter should not be optimized. (Parameter to be
optimized: CqiAdjustmentOn)
o CQI transmission power: Enables Mentor to define the power at which to
transmit the CQI, relative to the pilot. (Parameters to be optimized: deltaCqi1 and
deltaCqi2)
Defining the Parameters to be Optimized (Huawei Networks)

The Parameters page enables you to define the threshold for the minimum SHO quality, for
Huawei networks.
606
To define the SHO quality threshold

1. In the Min. SHO quality threshold field, enter the minimum Ec/Io value for the
threshold.
2. In the Max. SHO quality threshold field, enter the maximum value for the threshold.
Viewing the Parameter Plan Optimization Summary

The Summary page enables you to view a summary of the parameter optimization, including
the data consistency check, which shows the data inconsistency errors and warnings. You
can go back and change any parameters, if required. You can view the details of the
inconsistencies, and save these details for analyzing at a later stage.
running the parameter optimization.
607

2. To save the parameter optimization template for future use, click Save. A standard
Save dialog box is displayed.
parameter optimizations.
3. Click Finish to run the parameter optimization plan. The status of the optimization is
displayed at the top of the Calculations pane.
608
Parameters Optimization Completed dialog box is displayed.
5. Click Layers to view the available Parameter Plan layers.

6. Click Reports to open the Parameter Plan reports.
7. Click Close to close the Parameters Optimization Completed dialog box.
Viewing the Parameter Plan Reports

The Parameters Optimization report contains the following tabs, depending on the vendor:
Ericsson networks:
 CQI Offset Changes, which displays the CQI transmission power for each sector in
the selection set, before and after the parameter optimization.
 CQI Dynamic Adjustment, which displays for each sector in the selection set
whether the CQI dynamic adjustment feature was turned on before and after the
optimization, and whether there was sufficient data to optimize the CQI parameter.
 CQI Transmission Power, which displays the strength of the CQI transmission
power before and after the optimization.
 Details, which shows the name of the network, the time and date the report was
Huawei networks:
 SHO Quality Threshold Changes, which displays the minimum SHO quality of each
sector in the selection, before and after the optimization.
 Optimization Constraints, which displays a list of the sectors that were not
optimized, and the reasons why.
 Ec/Io Carrier <number>, which displays the Ec/Io histogram for each sector.
 Details, which shows the name of the network, the time and date the report was
For a detailed description of the tabs and fields in the Parameter Plan reports, refer to the
Ultima Mentor Help.
609
Exporting the Parameter Changes

After you have run the parameter plan optimization and are satisfied with the results, you can
export the changes to be implemented in the network. Before the plan is exported, the switch
dumps are read to ensure that the most recent parameters are used.
To export the parameter plan changes

1. In the Calculations pane, select the parameter plan whose changes you want to
export.
2. Right-click the parameter plan, and on the shortcut menu, click Export Parameters
Plan.
-OR-
The Export Parameters Plan dialog box is displayed, enabling you to select the
latest configuration files, and the directory to which to export the files containing the
parameter changes.
610
3. In the Location field, select the location of the switch dump information. This
exported parameters plan.
click the browse button to browse to the location of the latest switch dump
data.
o If you are using an optimization from the Mentor server, Server, and then select
the cluster to which the optimization belongs.
6. Click OK. If you have previously exported the parameter files, a confirmation
continue. A progress bar is displayed while the details of the updated sectors are
exported, and then a dialog box is displayed, notifying whether the export process
was successful.
7. Click Close to close the notification.
611
Overshooter Resolution Optimization

The Overshooter Resolution Plan wizard features a specialized algorithm that identifies
overshooting as well as undershooting sectors, and suggests appropriate tilt changes to
improve their RF footprint.
After you have run the overshooter resolution optimization, you can view Mentor's suggested
changes as well as the sectors that were not optimized in the Overshooter Resolution report.
Launching the Overshooter Resolution Wizard

The Overshooter Resolution wizard identifies the overshooting and undershooting sectors,
and suggests appropriate tilt changes to improve their RF footprint. By default, the
optimization is run on the selection set used in the model, but if required, you can select a
sub-set of these sectors to be used for the optimization.
To launch the Overshooter Resolution wizard

1. On the Calculation menu, click New > Overshooter Resolution Plan.
-OR-
On the Workflow toolbar, click the button and then select
Overshooter Resolution Plan from the drop-down menu.

The first step of the Overshooter Resolution wizard is displayed, enabling you to
define the general properties of the overshooter resolution plan.
The Overshooter Resolution wizard contains the following steps:
 Step 1 General, enables you to define general properties for the optimization, for
check to fail.
612
Defining General Overshooter Resolution Properties

The General page of the Overshooter Resolution wizard enables you to define a name for
the plan, as well as to select the time filter to be used.
If your model is for LTE technology, an additional field is displayed, enabling you to select the
technology on which to run the optimization.
To define the general properties of the overshooter resolution plan

1. In the Name field, enter a name for the new plan. If you do not enter a name, the
default name is used.
613
2. If your model is for LTE, in the Technology field, choose the technology on which to
run the optimization.
614
Viewing the Overshooter Resolution Summary

running the overshooter resolution optimization.
615

1. If there are data inconsistencies, click the Details button. The Details dialog box is
2. Click Finish to run the overshooter resolution optimization plan. The status of the
optimization is displayed at the top of the Calculations pane.
616
Overshooter Resolution Completed dialog box is displayed.
o Click Details to view details of the errors or warning messages. Note that the
Details button is enabled only if there are errors or warnings found in the
optimization.
o Click Layers to view the available layers, and load the selected layers. The
selected layers are displayed in the Layers pane, and can be selected and
viewed on the map.
o Click Reports to view the Overshooter Resolution Changes report. For more
information on the report, refer to the Ultima Mentor Help.
4. Click Close to close the Overshooter Resolution Completed dialog box.
617
Updating the Mentor Network Environment

After each neighbor list or RF shaping optimization phase where an optimization plan was
provisioned into the network, you should update the network environment so that Mentor will
reflect the new configuration of your network and the latest parameter settings. Ensuring that
Mentor uses the latest and most accurate network configuration is critical to guarantee its
analysis and optimization accuracy.
You can update the network environment in the following ways:
 Saving the network with a new name, and then updating the switch dump files. This
will enable you to keep the original network for future reference, for example, to
compare the network performance to previous networks.
 Modifying the project .mpr file to point to a new configuration file, and then
reimporting the network as a new network.
 Updating the switch dump files or the model. You will overwrite the current network
and will not be able to compare the network performance to previous networks.
 Enabling automatic updates.
Updating the Switch Dump Files

You can update the network at any time by importing the latest switch dump files. Importing
the switch dump files deletes the current model and all network calculations. If required, you
can save the network with a new name so that it can be used for comparison purposes in the
future.
To import the latest switch dump files

1. If required, save the network with a new name.
 On the File menu, click Save Network As. The Save Network As window is
displayed, showing the name of the current network in the Network name field.
 Enter a new name for the network.
 Click OK. The current network is saved with its new name.
2. On the File menu, click Import and then Switch Dump. A confirmation message is
displayed warning that the model and all network calculations will be deleted.
3. Click Yes to continue. The first step of the Import Switch Dump wizard is displayed.
The Import Switch Dump wizard contains two steps:
 Step 1 General, enables you to select the method by which to import the switch
dump data:
o Importing the latest switch dump files
o Importing the latest switch dump files from the Mentor server - This is the
preferred option
configuration changes directly in the GUI, if required.
618
Importing the Latest UMTS Switch Dump Files

In the General page of the Import Switch Dump wizard, you can select to import the switch
dump data from the switch dump files, and define the location of the data.
If you are connected to the Mentor server, you can also select to import the switch dump data
directly from the server.
To import the latest switch dump data from the switch dump files
1. On the File menu, click Import and then UMTS Switch Dump. A confirmation
message is displayed warning that the model and all network calculations will be
deleted.
3. In the Method field, select Import Switch Dump Files. The General page is
displayed as follows, enabling you to browse to the location of the latest switch dump
files.
619
4. In the Switch dump path field, enter the location of the switch dump files, or click the
browse button . The Select Switch Dump Path dialog box is displayed, enabling
you to browse to the latest switch dump files.
5. Browse to the required directory, and click Open. The selected file is displayed in the
Switch dump path field, and can be selected in the future by clicking the drop-down
arrow.
6. Click Next. A progress bar is displayed while the selected switch dump files are being
imported. You can click the Details button to view a log of any warnings generated
during the import process.
import the switch dump files.
The Data Completion page is displayed, enabling you to complete any missing
network data directly in the GUI, if required, or to import the network.
620
Importing the Switch Dump Data from the Mentor Server

If you are connected to the Mentor server, you can import the most up-to-date switch dump
data directly from the server. If you are not connected to the server, you can import the latest
switch dump data from the switch dump files.
To import the switch dump data from the Mentor server

1. On the File menu, click Import and then Switch Dump. A confirmation message is
displayed warning that the model and all network calculations will be deleted.
3. In the Method field, select Import from Server. You will be prompted to log on to the
Mentor server if you have not already done so. A progress bar is displayed while
Mentor connects to the server.
The General page changes as follows:
4. In the Clusters field, select the cluster to which the optimization belongs. The date of
the latest available configuration is displayed under the field.
5. Click Next. A progress bar is displayed while the selected switch dump files are being
imported from the server. You can click the Details button to view a log of any
warnings generated during the import process.
import the switch dump files.
The Data Completion page is displayed, enabling you to complete any missing
network data directly in the GUI, if required, or to import the network.
621
Completing the Switch Dump Data

Once you have entered the path of the switch dump files, or selected the required cluster in
the server, and there are no errors or sectors with missing data, you can import the network.
If there are sectors with missing data, meaning these sectors appear in the switch, but not all
their mandatory data is found in Mentor Format, the sectors are displayed in red in the
Excluded sectors pane. You can import the network without these sectors, or you can
complete the data directly in the GUI so that these sectors will be included with the imported
data.
Note: Carriers that do not exist in Mentor Format, but do appear in the switch dump, will be
automatically added to the network. For example, if the sector data appears in the
antennas.txt file but one or more of the sectors do not appear in the switch dump, the data will
be completed automatically, and the sector will be added to the network.
To complete the import process if there is no missing switch dump data

1. In the Data Completion page, click Details to view any warnings that may have
been generated during the import process.
622
the data is validated and the reports are created, and then the Import Switch Dump
3. Click Details to view the details of the import process, including any data
inconsistencies displayed in the General page.
4. Click Layers to view a layer showing any sectors that are missing data or that have
5. Click Reports to view detailed reports of the import process. The Summary report is
always generated, while other reports may be displayed only when relevant.
6. Click Close to close the Import Switch Dump Completed dialog box, and to display
the main window, showing the imported network.
To complete the switch dump data

1. In the Data Completion page, sectors that appear in the switch but which will not be
imported as they have missing data are displayed in red in the Excluded sectors
pane. The number of sectors with missing data is displayed at the top of the pane.
623
Select the sectors you would like to include in the import process and click the right
arrow button , or right-click the sectors and then click Move. The selected sectors
move to the Excluded sectors to be edited and imported pane.
The number of sectors with missing data to be completed and imported is displayed
at the top of the pane.
624
enter the missing information. Tabs with missing information are displayed in red, with
an asterisk. Fields with missing information are highlighted in red.
625
4. Repeat steps 2 and 3 for each sector you want to include in the import process.
the data is validated and the reports are created, and then the Import Switch Dump
626
including warnings notifying of differences in power settings between sectors in
different carriers.
7. Click Layers to view a layer showing any sectors that are missing data or that have
8. Click Reports to view detailed reports of the import process. The Summary report is
always generated, while other reports are displayed only when relevant. The sectors
whose data was manually completed are displayed in the New Added from Switch
report.
9. Click Close to close the Import Switch Dump Completed dialog box, and to display
the imported network.
627
Network Reports
The Network reports display the state of the current network.
The Import reports show the results of the import process. If you have imported updates from
the TEOCO server, these reports are displayed as well. It is very important to review the
network reports, as they provide vital information on the network and model status, for
example, whether the network is complete, if the models contain enough good data to be
used for optimization, as well as any dates that should be "filtered" during the optimization
process in case there is an issue with that day's data.
The Model reports show any errors and warnings, and the parsing details generated during
the model creation. You should review all the model reports to validate the current model. If
you decide that the model is inaccurate, for example, if it is missing legs in messages, or if
data is affecting the accuracy of the model, you should contact your Mentor server
administrator for assistance.
To open the network reports

1. On the Network menu, click Open Network Reports. The Network Reports dialog
box is displayed. If a model does not exist, the Import report is opened.
The following reports are available, depending on whether there were any warnings
when you imported the network and whether you created or imported a model
o GSM Network Import Details
o GSM Network Import Summary
o Import
o Import Messages
o Import Warnings
o Model Errors and Warnings (UMTS)
o Model Parsing Details (UMTS)
o Model Errors and Warnings (LTE)
o Model Parsing Details (LTE)
628
By default, the reports are displayed in alphabetical order, but you can change the
order by sorting them in ascending order or according to size by clicking Report
Name or Size.
2. In the Report Name area, double-click the report you want to view, or select the
report and then click Open. The selected report is displayed in Excel format.
(Depending on your Excel security settings, you may be prompted to disable or
enable macros. Click Enable Macros.)The name of the report and the name of the
network are displayed in the title bar of the report.
o If the report contains tabs, select the relevant tab to view the different reports
within the report.
3. To save reports, select the reports you want to save and then click Save As.
GSM Network Import Details Report

The GSM Network Import Details report displays details of the GSM import process. It
contains the following tabs:
 Summary, which displays a summary of the messages that were generated during
the import process.
 Messages, which shows details of the messages that were generated during the
import process.
 Details, which displays the name of the network being imported, the date and time
the reports were generated, and the version of Mentor being used.
GSM Network Import Details - Summary Tab

The GSM Network Import Details - Summary tab displays a summary of all the messages
that were generated during the import process.
The following table describes the fields in the GSM Network Import Details - Summary tab:
Field Description
Severity The severity of the message—Information or Warning.
Message The text of the information or warning message. For example, the
total number of warning messages, or the number of handovers that
violate BCCH reuse.
GSM Network Import Details - Messages Tab

The GSM Network Import Details - Messages tab displays the details of each message.
The following table describes the fields in the GSM Network Import Details - Messages tab:
Field Description
Severity The severity of the message—Information or Warning.
BSC The name of the BSC to which the affected sectors belong.
Count The number of occurrences of the specific message.
629
Field Description
Message The text of the information or warning message.
File Name The name of the file from which the application data is taken.
Row The row in which the data error appears.
GSM Network Import Summary Report

The GSM Network Import Summary report displays a summary of the GSM import process.
It contains the following tabs:
 GSM Import Summary, which displays the number of imported GSM sectors, the
number of imported channel groups, and the number of sectors that were deleted as
they do not have coordinates or azimuth readings, channel groups, or more than one
channel group contains BCCH.
 Details, which displays the name of the network being imported, the date and time
the reports were generated, and the version of Mentor being used.
Import Report
The Import report displays a detailed summary of the import process, as well as any
warnings that were generated during this process, for example, due to missing or unknown
sectors, missing sites, rejected neighbors, and so on. It also lists further details regarding the
warnings listed in the Import Messages report.
The Import report can include the following tabs, according to the network technology and the
warnings generated:
 Summary, which displays a summary of the network elements that were imported
into or rejected from the network database.
 Import Warnings, which displays a detailed list of each warning that was generated
during the import process.
 Rej. from Physical Antenna File, which displays a list of the network elements that
were rejected from the antennas.txt file or the planning database (for example,
ASSET), and the reason why.
 Rej. from Switch, which displays a list of sector carriers from the switch that were
rejected as they are missing from the antennas.txt file or the planning database (for
example, ASSET).
 Rej from LTE Switch, which displays a list of cells that are missing or were rejected
from Mentor Format, and the reason why.
 Sector Carriers Missing Switch Data, which displays a list of all sector carriers, per
RNC, that are missing switch data.
 New Added, which displays details of the sector carriers whose mandatory data was
completed or automatically corrected so that they could be imported into the network.
 New Added LTE, which displays details of the cells whose mandatory data was
 Rej. Neighbors, which lists the neighbors found in the switch dumps that are not
recognized by the antennas.txt file or the planning database (for example, ASSET).
 Inactive Sectors, which lists the sectors that are defined as being inactive prior to
being imported.
630
 Unknown Neighbors, which lists the sectors that are near the selection set, but are
not defined in the antennas.txt file or the planning database (for example, ASSET).
 Unknown Neighbors LTE, which lists the sectors that are near the selection set, but
not defined in the antennas.txt file or the planning database (for example, ASSET).
 Neighbors Errors and Warnings, which lists the errors and warnings that were
generated during the import process.
 Default Antenna Model, which lists the sectors that will be using the default antenna
model, as well as the original and default antenna models and tilts used.
 Power Dif. Sectors, which lists the sectors that do not have the same overhead
channel power or power limits in all the carriers.
 Co-SCs in Neighbor List Tab, which lists the source sectors in the neighbor list that
contain target sectors with the same SC.
 Co-PCIs in Neighbor List Tab, which lists the source sectors in the neighbor list that
contain target sectors with the same PCI.
 Import Details, which lists the path of the imported .mpr file.
Import Tab
The Import tab shows a summary of the network elements that were imported into or rejected
from the network database.
The following table describes the fields in the Import tab:
Field Description
Field The network element that was imported or rejected, including

sites, sectors, antennas, antenna profiles, antenna models,
carriers, neighbors, and neighbor constraints.
The total number of network elements from Mentor Format
Imported Total
and/or switch dumps that were imported into the network
database.
The number of network elements from the physical antenna
From
file that were imported into the network database.
Physical
Antenna
File
The number of network elements from the switch dumps that
From
were imported into the network database. This field includes
Switch
the sectors that were missing data during the import process,
Dump
and for which you completed the data.
Only
The number of network elements from the physical antenna
Rejected From
file that were rejected from the network database due to
Physical
Mentor Format errors, missing information in the switch
Antenna
dump, or because they had no SC.
File
Details about each network element that was rejected is listed
in the Rejected NEs from Physical Antenna File tab.
The number of network elements from the switch dumps that
From
were rejected from the network database. This field includes
Switch
the sectors that were missing data such as location
Dump
information, during the import process, and for which you did
Only
not manually complete the data.
631
Import Warnings Tab

The Import Warnings tab shows the detailed information of each warning that was generated
during the import process. This corresponds to the Import Messages report, which provides a
summary of the warnings.
The following table describes the fields in the Import Warnings tab:
Field Description
Description A summary of the import warning.
File The name of the file from which the application data is taken.
Line The line in which the data error appears.
Column The column in which the data error appears.
Rejected NEs from Physical Antenna File Tab

The Rejected NEs from Physical Antenna File tab displays a list of the network elements
that were rejected from the antennas.txt file or the planning database (Atoll or Planet), and the
reason why. This information corresponds to the information in the Import tab.
This tab helps differentiate between Mentor Format errors and switch-dump synchronization.
The following table describes the fields in the Rejected NEs from Physical Antenna File tab:
Field Description
Network Element The type of network element that was rejected, for example,
Antenna Profile.
Name The name of the network element.
Cause The reason the network element was rejected.
Full Description A full description of the reason why the network element was
rejected.
632
Sector Carriers Rejected from Switch Tab

The Sector Carriers Rejected from Switch tab displays a list of sector carriers from the
switch dumps that were rejected because they are missing physical parameter information,
which was not found in the Mentor Format antennas.txt file or the planning database (for
example, ASSET or Atoll). This information corresponds to the information in the Import tab.
Field Description
RNC Name The name of the RNC to which the sector carrier belongs.
Sector Carrier Name The name of the sector carrier that was rejected.
Carrier The carrier to which the rejected sector belongs.

Cause The reason the sector carrier was rejected from the switch
dump.
LTE Cells Rejected from Switch Tab

The LTE Cells Rejected from Switch tab displays a list of the cells that are missing or were
rejected from Mentor Format, and the reason why. This information corresponds to the
information in the Import tab.
This tab helps differentiate between Mentor Format errors and switch-dump synchronization.
The following table describes the fields in the Rejected from LTE Cells Rejected from the
Switch tab:
Field Description
eNB ID The name of the eNB to which the rejected cell belongs.
Cell ID The switch dump identity of the unknown cell.
Cause The reason the cell was rejected.
Sector Carriers Missing Switch Data Tab

The Sectors Missing Switch Data tab shows a list of all sector carriers, per RNC, that are
missing switch data. This corresponds to the Import Messages report, which provides a
summary of the warnings generated during the import process.
The following table describes the fields in the Sectors Missing Switch Data tab:
Field Description
RNC Name The name of the RNC to which the sector belongs.
Sector Name The name of the sector that is missing switch dump data.
Carrier The carrier to which the sector belongs.
Cause A description of the missing data.
633
New Added from Switch Tab

The New Added from Switch tab displays details of the sectors whose mandatory data was
The following table describes the fields in the New Added from Switch tab:
Field Description
RNC Name The name of the RNC of the site to which the added sector
belongs.
Sector Name The name of the sector that was added.
Carrier The carrier to which the added sector belongs.
New Added from LTE Switch Tab

The New Added from LTE Switch tab displays details of the LTE cells whose mandatory
data was completed or automatically corrected so that they could be imported into the
network.
The following table describes the fields in the New Added from LTE Switch tab:
Field Description
eNB ID The name of the eNB of the site to which the added cell
belongs.
Cell Name The name of the cell that was added.
Carrier The carrier to which the added cell belongs.
Rejected Neighbors Tab

The Rejected Neighbors tab lists the neighbors found in the switch dump files that are not
recognized by the Mentor Format antennas.txt file or the planning database (Atoll or Planet).
The following table describes the fields in the Rejected Neighbors tab:
Field Description
Source Sector Name The name of the source sector.
Target Sector Name The name of the target sector.
Cause The reason the sector was rejected.
634
Inactive Sectors Tab

The Inactive Sectors tab lists the sectors that are defined as being inactive prior to being
imported.
The following table describes the fields in the Inactive Sectors tab:
Field Description
Sector Name The name of the inactive sector.
Cause The reason for the sector's inactivity. For example, the sector
may have been predefined as inactive by the user, or all the
sectors are inactive.
Unknown Neighbors Tab

The Unknown Neighbors tab displays a list of target sectors that are near the selection set,
but that are not identified by the Mentor Format antennas.txt file or the planning database
(Atoll or Planet).
The following table describes the fields in the Unknown Neighbors tab:
Field Description
Target RNC The name of the RNC to which the unknown target sector
belongs.
Target Sector Name The switch dump identity of the unknown target sector.
Target Frequency The frequency upon which the unknown target sector
transmits.
Source RNC The name of the RNC to which the source sector belongs.
Carrier The carrier to which the unknown sector belongs.
Priority The priority of the neighbor.
Cause The reason the sector is unknown.
635
Unknown Neighbors LTE Tab

The Unknown Neighbors LTE tab displays a list of target sectors that are near the selection
set, but that are not identified by the Mentor Format antennas.txt file or the planning database
(for example, ASSET).
The following table describes the fields in the Unknown Neighbors LTE tab:
Field Description
Target Macro eNB ID The name of the eNodeB to which the unknown target sector
belongs.
Target Sector ID The switch dump identity of the unknown target sector.
MCC The mobile country code of the unknown sector.
MNC The mobile network code of the unknown sector.
TAC The tracking area code of the unknown sector.
PCI The PCI of the unknown target sector.
Target Cell Identifier The identifier of the unknown target sector.
Source eNB The name of the eNB to which the source sector belongs.
Source Cell The name of the source sector.
Carrier The carrier to which the unknown sector belongs.
Cause The reason the sector is unknown.
Neighbors Errors and Warnings Tab

The Neighbors Errors and Warnings tab lists the neighbor-related errors and warnings that
are generated when importing the network.
The following table describes the fields in the Neighbors Errors and Warnings tab:
Field Description
Target Sector The name of the target sector.
Carrier The carrier to which the source sector belongs.
Cause The reason for the error or warning. For example, the target
sector may be unknown, the sector may have no neighbor list,
or there may be no softer handovers between the neighbors.
636
Sectors with Default Antenna Model Tab

The Sectors with Default Antenna Model tab displays the sectors that were missing
antenna data, as well as the original antenna model and tilt and the new default antenna
model and tilt.
The following table describes the fields in the Sectors with Default Antenna Model tab:
Field Description
Sector The name of the sector that is missing antenna data and that
will be assigned a default antenna profile.
Antenna The name of the antenna that is missing data, and that will be
assigned a default profile.
Rejected Antenna The original antenna model used, before assigning the default
Model profile.
Electrical The original electrical tilt, before assigning the default profile.
Tilt
Used Antenna The default antenna profile that will be used.

Model
Electrical The default tilt for the antenna profile.
Tilt
Sectors with Different Power Settings Per Carrier Tab (Warnings)

The Sectors with Different Power Settings per Carrier tab lists the sectors that do not have
the same overhead channel power or power limits in all the carriers.
Note: The differences in the power values are taken into consideration only if they are above
0.2 dB.
The following table describes the fields in the Sectors with Different Power Settings per
Carrier tab:
Field Description
Sector Name The name of the sector whose power is not the same in all the
carriers.
Parameter The overhead channels power or the power limits (Call

blocking threshold, HO blocking threshold, and Max PA power)
in which there are differences between the sectors.
Value (dBm) The power of the sector in the selected carrier.
Delta (dB) The difference in power between the first carrier, and the
specific carrier.
637
Co-SCs in Neighbor List Tab

The Co-SCs in Neighbor List tab lists the sectors in the neighbor list that contain target
sectors, up to tier 3, with the same SC.
The following table describes the fields in the Co-SCs in Neighbor List tab:
Field Description
Type The type of co-SC conflict, enabling the tab to be filtered from
tier1 up to tier 3 conflicts.
SC The SC number of the source and target sectors.
Source RNC The RNC to which the source sector belongs.
Carrier ID The ID of the carrier to which the source sector belongs.
Distance (Km) The distance between the source sector and the tier1 target
sector.
Target RNC 1 The RNC to which the target sector belongs.
Target Sector 1 The name of the target sector.
Target RNC 2 The RNC to which the tier2 target sector belongs.
Target Sector 2 The name of the tier2 target sector.
Target RNC 3 The RNC to which the tier3 target sector belongs.
Target Sector 3 The name of the tier3 target sector.
Path Priority The path of the source to the target sector. The tab shows up to
100 possible paths, if relevant, based on the
MAX_COSC_PATHS_COUNT parameter, with the shortest
path between the sectors listed first.
 Single path: Displayed if there is only one path, for
example, Tier1 co-SC and Co-SC in NL conflicts.
 Shortest path: Displayed first, indicating the shortest path
between the source and tier2 or tier3 sectors.
 <2...100>: Displays the priority of the path, based on the
distance between the sectors, if it is not the shortest path or
the only path.
638
Co-PCIs in Neighbor List Tab

The Co-PCIs in Neighbor List tab lists the sectors in the neighbor list that contain target
sectors, up to tier 3, with the same PCI.
The following table describes the fields in the Co-PCIs in Neighbor List tab:
Field Description
Type The type of co-PCI conflict, enabling the tab to be filtered from
tier1 up to tier 3 conflicts.
PCI The PCI number of the source and target sectors.
Source Cell The name of the source sector.
Carrier ID The ID of the carrier to which the source sector belongs.
Distance The distance between the source sector and the tier1 target
sector.
Target eNB 1 The eNB to which the target sector belongs.
Target Cell 1 The name of the target sector.
Target eNB 2 The eNB to which the tier2 target sector belongs.
Target Cell 2 The name of the tier2 target sector.
Target eNB 3 The eNB to which the tier3 target sector belongs.
Target Cell 3 The name of the tier3 target sector.
Path Priority The path of the source cell to the target cell. The tab shows up
to 100 possible paths, if relevant, based on a predefined
parameter, with the shortest path between the sectors listed
first.
 Single path: Displayed if there is only one path, for
example, Tier1 co-PCI and Co-PCI in NL conflicts.
 Shortest path: Displayed first, indicating the shortest path
between the source and tier2 or tier3 sectors.
 <2...100>: Displays the priority of the path, based on the
distance between the sectors, if it is not the shortest path or
the only path.
639
Import Details Tab

The Import Details tab lists the method used for importing the network, as well as the
location of the relevant .mpr file.
The following table describes the fields in the Import Details tab:
Field Description
Method The method used to import the network.
Location The location of the imported .mpr file, or the name of the
cluster if the network was imported from the server.
Import Messages Report

The Import Messages report provides a summary of the information and warning messages
that were generated while importing the new network. For example, if there were differences
in the overhead power settings between the same sectors in each carrier, which will cause
problems when applying the same power changes to all the carriers.
This report shows the same information as in the Import Network Configuration dialog box,
which is displayed when you view the import details.
The following table describes the fields in the Import Messages report:
Field Description
Date The date and time the message was generated.
Level The severity of the message—Information or Warning.
Message The text of the information or warning message. If applicable,

the report in which the problem is described is listed.
For example:
 KPI file loaded (Mentor Format/kpis.txt)
 <Number> antenna profiles were rejected from the
network database.
The number of antenna profiles that were rejected from the
network database as they could not be parsed.
For example, antenna profiles could have been rejected as
they had missing attributes, or invalid gain values.
You can view a list of the antenna profiles, and the reason
they were rejected, in the Rej. from Physical Antenna File
tab in the Import report.
 <Number> sector carriers were rejected from the
network database.
The number of sector carriers that were rejected from the
network database as they were not recognized by Mentor
Format, or were not found in the switch dump.
You can view a list of the sector carriers, and the reason
they were rejected, in the Rej. from Physical Antenna File
tab in the Import report.
640
Field Description
 <Number> neighbors are missing from the network
database.
The number of target sectors that are near the selection set,
but were not recognized by Mentor Format. You can rectify
this by defining these sectors in the Antennas and Carriers
files.
You can view a list of the sectors, and the reason they are
not recognized by Mentor Format, in the Unknown
Neighbors tab in the Import report.
 <Number> sector carriers are missing data.
The number of sector carriers that are missing switch data,
and therefore will not be optimized.
You can view a list of the sector carriers with missing data
in the Sector Carriers Missing Switch Data tab in the
Import Report.
 <Number> sector object(s) were not loaded to
<selection name> selection.
The number of unidentified sectors in the selection file.
 <Number> sectors do not have the same Sync power in
all the carriers.
The number of sectors where the Sync power is not the
same in all the sector carriers.
You can view a list of the sectors with different Sync power
in the different carriers, and the actual Sync power of each
sector, in the Power Dif. Sectors tab in the Import report.
If you try running an optimization that applies the same
relative changes to all the carriers being optimized, you will
have to approve the warning to continue with the
optimization.
 <Number> sectors do not have the same CPICH power
in all the carriers.
The number of sectors where the CPICH power is not the
same in all the sector carriers.
You can view a list of the sectors with different CPICH
power in the different carriers, and the actual CPICH power
of each sector, in the Power Dif. Sectors tab in the Import
report.
optimization.
641
Field Description
 <Number> sectors do not have the same Call blocking
threshold in all the carriers.
The number of sectors where the Call blocking threshold is
not the same in all the sector carriers.
You can view a list of the sectors with different Call blocking
thresholds in the different carriers, and the actual Call
blocking threshold of each sector, in the Power Dif.
Sectors tab in the Import report.
optimization.
 <Number> sectors do not have the same HO blocking
threshold in all the carriers.
The number of sectors where the HO blocking threshold is
not the same in all the sector carriers.
You can view a list of the sectors with different HO blocking
thresholds in the different carriers, and the actual HO
blocking thresholds of each sector, in the Power Dif.
Sectors tab in the Import report.
optimization.
 <Number> sectors do not have the same Paging power
in all the carriers.
The number of sectors where the Paging power is not the
same in all the carriers.
You can view a list of the sectors with different Paging
power in the different carriers, and the actual Paging power
of each sector, in the Power Dif. Sectors tab in the Import
report.
optimization.
 Name of profile: <name> does not match the file name.
The file name is used.
There was an inconsistency between the name of the
profile and the file name, therefore the file name was used.
 Neighbors contain <number> warnings.
The number of errors that were generated during the import
process. For example, the sector may have no neighbor list,
or there may be no softer handovers between the
neighbors.
You can view a list of the neighbors with warnings, and the
reason for the warning, in the Neighbors Errors and
Warnings tab in the Import report.
642
Field Description
 CPICH power for <sector> <CPICH power> is expected
to be lower than max CPICH power constraint
<maximum CPICH power>.
The CPICH power of the specific sector is higher than the
permitted maximum power.
 CPICH power for <sector> <CPICH power> is expected
to be higher than min CPICH power constraint
<minimum CPICH power>.
The CPICH power of the specific sector is lower than the
minimum permitted power.
 Profile <name> does not have an electrical tilt.
The profile does not have any electrical tilt information
specified.
 Switch dump was not detected.
The network does not include any switch dump data. If
required, you can import the switch dump data.
Import Warnings Report

The Import Warnings report displays the warnings that are generated when importing a
model that contains only selected network elements, from the server.
The following table describes the fields in the Import Warnings report:
Field Description
Description The import warning, for example, parsing errors due to

unknown sectors.
Line The line in which the warning appears.
Column The column in which the warning occurs, for example, To

Sector Carrier or From Sector Carrier.
643
Model Errors and Warnings Report (UMTS)

The Model Errors and Warnings report includes the errors and warnings generated during
the UMTS model creation. Errors must be rectified in order for the model to be created
successfully.
The Model Errors and Warnings report includes the following tabs:
 General Information, which displays a summary of the model, for example the
technology used, and the number of unidentified sectors in the messages.
 Unidentified Legs, which lists any unidentified sectors relating to the calculation set
that are reported in RRC messages.
 Logged Errors & Warnings, which lists a summary of the errors and warnings that
were generated during the model creation.
 Low Message Duration, which lists the sectors that do not have sufficient weighted
messages.
 Low Traffic Reliability, which lists sectors that have a low correlation between the
number of weighted messages reflecting the traffic, and the traffic usage from KPIs
for the same busy-hour period.
 Locked Sector Carriers, which lists the sector carriers that are locked for optimization,
and the reason why.
General Information Tab

The General Information tab displays a summary of the model, for example the number of
sectors in the model, and the number of unidentified legs in the messages.
The following table describes the fields in the General Information tab:
Field Description
Creation date The date and time the model was created.
Last updated The date and time the model was last updated.
Model name The name of the model.
Technology The technology used in the model.
Carriers The list of carriers included in the model.
Positioning Whether the model includes positioning. Models with

positioning can be used for creating maps, and for tilt
optimizations.
First performance The date of the earliest call-trace data used in the model.
counters date
Last performance The date of the most recent call-trace data used in the model.
counters date
644
Field Description
No. of log days The number of days for which call-trace data was collected,
according to the filter settings selected in the wizard.
Note: This number represents the days for which call-trace
data for all events was collected, including those not listed in
the various report tabs.
No. of messages The duration of the active calls, in seconds, according to the
sampling rate.
No of active-set legs The total number of active legs in all the PSMM messages.
Unidentified legs in The number of PSMM legs that are reported in messages, but
messages are not identified by Mentor as they are not defined in Mentor
Format.
Note: As these legs are ignored in the model, the impact of
their changes on their source is also ignored. If you think that
their changes will influence the calculation set, define them in
the environment.
Selected sectors The number of sectors included in the model.
Sectors in the The number of sectors in the calculation set that have low call
calculation set with duration.
low duration
Unidentified The number of neighbors that appeared in the log file, but were
neighbors not identified by Mentor as they are not defined in Mentor
Format.
Sectors with low The number of sectors with a low correlation between the
traffic reliability number of weighted messages reflecting the traffic, and traffic
usage from KPIs for the same busy-hour period.
645
Unidentified Legs in RRC Messages Tab

The Unidentified Legs in RRC Messages tab lists the sectors relating to the calculation set
that are reported in the RRC messages, but are not defined in the environment. A sector is
listed as unidentified even if only one leg in the message is related to the calculation set.
According to the missing data, you can decide whether the model is accurate enough, or
whether to add the missing sectors to the network, and then create a new model.
The following table describes the fields in the Unidentified Legs in RRC Messages tab:
Field Description
RNC The name of the RNC to which the site belongs.
Sector Name The name of the primary sector.
Cell ID The cell identification of the sector.
In Selection Set Whether the primary sector is in the selection set.
Missing SC The scrambling code of the sector in the unidentified leg.
Missing RNC The RNC to which the sector in the unidentified leg belongs.
Missing Cell ID The cell identification of the sector in the unidentified leg.
Message Count The number of cases in which the unidentified sector

appeared in the RRC messages.
Logged Errors and Warnings Tab

The Logged Errors and Warnings tab lists a summary of the errors and warnings that were
generated during the model creation.
The following table describes the fields in the Logged Errors and Warnings tab:
Field Description
Date The data and time the log was generated.
Level The severity of the log—Error or Warning.
Message A summary of the error or warning. For example, the number of

sectors in which the insertion loss was corrected, or if the
selection set is too large for a valid optimization.
646
Sectors with Low Message Duration Tab

The Sectors with Low Message Duration tab lists the sectors that do not have sufficient
weighted messages.
The following table describes the fields in the Sectors with Low Message Duration tab:
Field Description
Sector Name The name of the sector with low message duration.
In Selection Set Whether the sector belongs to the selection set.
BH Primary Traffic The number of active links between the cellular switch and the
(Erlang*Hour) PSTN, measured in Erlang.
Message Duration The total duration of messages collected, in seconds, in which

(sec) the sector was the primary server.
Sectors with Low Traffic Reliability Tab (Warnings)

The Sectors with Low Traffic Reliability tab includes details of the sectors that have a low
correlation between the number of weighted messages reflecting the traffic, and the traffic
usage from counters for the same busy-hour period.
The following table describes the fields in the Sectors with Low Traffic Reliability tab:
Field Description
Sector Name The name of the sector with the low reliability.
Carrier The carrier to which the specific sector belongs.
In Selection Set Whether the sector belongs to the selection set.
BH Primary Traffic The number of active links between the cellular switch and the

the sector was the primary server.
Reliability Rate The rate of correlation between the number of messages and
the OVSF code usage.
647
Locked Sector Carriers Tab

The Locked Sector Carriers tab displays the sectors carriers that are locked for optimization,
and the reason why.
The following table describes the fields in the Locked Sector Carriers tab:
Field Description
Sector Name The name of the locked sector.
Carrier The carrier to which the locked sector belongs.
Locked Reason(s) The reasons the sector is locked. For example, the sector may
be locked due to low traffic reliability.
Model Parsing Details Report (UMTS)

The Model Parsing Details report includes the details of the log parsing generated during the
model creation.
The Model Parsing Details report includes the following tabs:
 Sector Count Summary Table, which displays a summary of the sector count per
carrier for the calculation set.
 Hourly Data Statistics, which displays the amount and rate of data per hour, for the
calculation set.
 BH Data Statistics, which displays the amount and rate of data in the calculation set,
for the busy hour.
 BH Sector Data Statistics, which displays rate of data missing in the calculation set,
per sector, for the busy hour.
 Sector Carrier Data Statistics, which displays a summary of the counters that were
successfully recorded, as well as the number of messages in which each sector
carrier was the primary server.
 Traced Cells, which displays a summary of the sectors that were traced, based on the
IOS trace files.
Note: This report is displayed for Huawei networks only.
648

The General Information tab displays a summary of the model, for example the number of
sectors in the model, and the number of unidentified legs in the messages.
Field Description

positioning can be used for creating maps, and for tilt
optimizations.
counters date
counters date
No. of messages The duration of the active calls, in seconds, according to the
sampling rate.
No of active-set legs The total number of active legs in all the PSMM messages.
Unidentified legs in The number of PSMM legs that are reported in messages, but
messages are not identified by Mentor as they are not defined in Mentor
Format.
Note: As these legs are ignored in the model, the impact of
their changes on their source is also ignored. If you think that
their changes will influence the calculation set, define them in
the environment.
Selected sectors The number of sectors included in the model.
649
Field Description
Sectors in the The number of sectors in the calculation set that have low call
calculation set with duration.
low duration
Unidentified The number of neighbors that appeared in the log file, but
neighbors were not identified by Mentor as they are not defined in
Mentor Format.
Sectors with low The number of sectors with a low correlation between the
traffic reliability number of weighted messages reflecting the traffic, and traffic
usage from KPIs for the same busy-hour period.
Sector Count Summary Table Tab

The Sector Count Summary Table tab displays a summary of the sector count, per carrier.
The following table describes the fields in the Sector Count Summary Table tab:
Field Description
Carrier The list of carriers included in the model.
Selection Set The number of sectors in the selection set, and that can be
optimized.
Calculation Set The number of sectors that Mentor selected to be in the

calculation set, which can be influenced by changes in the
selection set due to optimization.
Hourly Data Statistics Tab

The Hourly Data Statistics tab lists both the amount and the rate of data gathered for all
sectors in the calculation.
The following table describes the fields in the Hourly Data Statistics tab:
Field Description
Date The date of the call-trace data.

Note: Only days for which there are power-related events are
listed.
Hour The time of the call-trace data.
BH The busy hour, based on the hourly sum of OVSF traffic

derived from the RNC counters for the whole calculation set.
Primary Traffic (Erlang) The number of active links between the cellular switch and the
PSTN, measured in Erlang.
650
Field Description
Message Count The number of messages collected in which the sector was
the primary server. This column is essential for the verification
of the call-trace data collection hours.
Sectors Rate (%) The percentage of expected power counters received.

with
Power Count The number of sectors in the calculation set with reported
Counters power in the BSM counters for this hour.
Sectors Rate (%) The percentage of expected traffic counters received.

with
Traffic Count The number of sectors in the calculation with reported traffic in
Counters the BSM counters for this hour.
Sectors with Rate (%) The percentage of expected performance counters received.
Performance
Counters Count The number of sectors in the calculation set with reported
performance in the MTX counters for this hour.
BH Data Statistics Tab

The BH Data Statistics tab lists both the amount and the rate of busy-hour data gathered for
all sectors in the calculation.
Note: The busy hour is determined according to the maximal traffic for each day. If there is a
mismatch between the primary traffic yielded from the KPIs, and the message duration
yielded from the call-trace data, there may be a time-zone, recording, or data problem.
The following table describes the fields in the BH Data Statistics tab:
Field Description

listed.
BH The busy hour, based on the hourly sum of OVSF traffic

derived from the RNC counters for the whole calculation set.
Primary Traffic (Erlang) The number of active links between the cellular switch and the
PSTN, measured in Erlang.

(sec) the sector was the primary server.
651
Field Description
Sectors Rate (%) The percentage of expected power counters received.

with
Power Count The number of sectors in the calculation set with reported
Counters power in the BSM counters for this hour.
Sectors Rate (%) The percentage of expected traffic counters received.

with
Traffic Count The number of sectors in the calculation set with reported
Counters traffic in the BSM counters for this hour.
Sectors Rate (%) The percentage of expected performance counters received

with for this hour.
Performa
nce Count The number of sectors in the calculation set with reported
Counters performance in the BSM counters for this hour.
BH Sector Data Statistics Tab

The BH Sector Data Statistics tab contains a summary of the data missing from the
network, per sector, for the busy hour. It enables you to check whether you have all the
required call-trace data for each busy hour, and to view the average traffic as well as the
traffic reliability for the busy hour.
mismatch between the primary traffic yielded from the KPIs, and the message duration or
message count yielded from the call-trace data, there might be a time-zone, recording, or
data problem.
The following table describes the fields in the BH Sector Data Statistics tab:
Field Description
Sector Name The name of the sector.
Cell ID The identification of the cell.
In Selection Set Whether the sector is in the selection set.
Primary Traffic The number of active links between the cellular switch and the
Message Duration The total duration, in seconds, of messages in which the

(sec) sector was the primary server.
Traffic Reliability The correlation between the message duration and the OVSF
usage.
652
Field Description
BHs with Rate The percentage of expected busy hours for which power
Power (%) counters were received.
Counters
Count The number of busy hours for which there are power counters
for the sector.
BHs with Rate The percentage of expected busy hours for which traffic
Traffic (%) counters were received.
Counters
Count The number of busy hours for which there are traffic counters
for the sector.
BHs with Rate The percentage of expected busy hours for which performance
Performan (%) counters were received.
ce
Counters Count The number of busy hours for which there are performance
counters for the sector.
Sector Carrier Data Statistics Tab

The Sector Carrier Data Statistics tab enables you to view a summary of the counters that
were successfully recorded, as well as the number of messages in which the sector was the
primary server.
The following table describes the fields in the Sector Carrier Data Statistics tab:
Field Description
Primary Traffic The number of active links between the cellular switch and the
HO Count The total number of HO counts from the source sector.
653
Field Description
Message Count The number of messages in which the sector was the primary
server. This column is essential for the verification of the call-
trace data collection hours.
Hours Rate (%) The percentage of expected hours for which power counters
with were received.
Power
Counters Count The number of hours for which there are power counters for
the sector.
Hours Rate (%) The percentage of expected hours for which traffic counters
with were received.
Traffic
Counters Count The number of hours for which there are traffic counters for
the sector.
Hours Rate (%) The percentage of expected hours for which performance
with counters were received.
Performa
nce Count The number of hours for which there are performance
Counters counters for the sector.
Traced Cells Tab

The Traced Cells tab displays a summary of the sectors that were traced, based on the IOS
trace files.
Note: This report is displayed for Huawei networks only.
The following table describes the fields in the Traced Cells tab:
Field Description
RNC ID The ID of the RNC to which the sector belongs.
654
Model Errors and Warnings Report (LTE)

The Model Errors and Warnings report includes the errors and warnings generated during
the LTE model creation. Errors must be rectified in order for the model to be created
successfully.
The Model Errors and Warnings report includes the following tabs:
 Unidentified Sectors, which lists any unidentified sectors relating to the calculation set
that are reported in RRC messages.
 Low Message Duration, which lists the sectors that do not have sufficient weighted
messages.
 Low Volume Reliability Rate, which lists the sectors whose volume reliability relative
to the whole network is low.

The General Information tab displays a summary of the LTE model, for example the number
of sectors in the model, and the number of unidentified legs in the messages.
Field Description
Vendor The network vendor.
TACs The TACs of the sectors used in the model.

positioning can be used for creating maps.
counters date
counters date
655
Field Description
No. of sectors with The number of sectors, as primary servers, with

measurement events measurements.
No. of measurement The total number of power records (measurement reports) for
events all days.
No. of measured The total number of measured sectors in the power records for
sectors all days. For example, if a measurement report reports
measurements on 4 sectors, 4 is added to this total.
Average number of The average number of measured sectors per measurement

measured sectors per event.
measurement event
events in BHs all busy hours.
No. of measured The total number of measured sectors in the power records for
sectors in BHs all busy hours. For example, if a measurement report reports

measured sectors per event for the busy hours.
measurement event in
BHs
Unidentified The total number of measured sectors in the measurement

measured sectors in events that were not identified in the environment. For
measurement events example, if a measurement report reports measurements on 2
unidentified sectors, 2 is added to this total.
Percentage of The percentage of measured sectors in that are unidentified.

unidentified measured
sectors in measured
sectors
No. of sectors without The number of sectors in the model without any KPI data.
KPI data
No. of sectors with The number of sectors in the calculation set that have low call
low duration duration. A sector has low duration if the total message
duration of the sector in the busy hours is below the threshold
defined in the LOW_DURATION_THRESHOLD parameter.
656
Field Description
No. of unidentified The number of target sectors (non primary) in measurement

neighbors events that were not identified in the environment.
No. of sectors with The number of sectors whose volume reliability rate falls
low volume reliability outside of the thresholds defined in the MIN_RELIABILITY and
rate MAX_RELIABILITY parameters. Volume reliability defines the
reliability of the sector's data relative to the whole network.
Unidentified Legs in RRC Messages

The Unidentified Legs in RRC Messages tab lists the sectors relating to the calculation set
that are reported in the RRC messages, but are not defined in the environment. A sector is
listed as unidentified even if only one leg in the message is related to the calculation set.
According to the missing data, you can decide whether the model is accurate enough, or
whether to add the missing sectors to the network, and then create a new model.
The following table describes the fields in the Unidentified Legs in RRC Messages tab:
Field Description
TAC Group The name of the TAC group to which the site belongs.
Sector Name The name of the primary sector.
Missing PCI The PCI of the sector in the unidentified leg.
Missing Global Cell ID The global cell identification of the sector in the unidentified leg.
Measurement Reports The number of messages in which the sector was the primary
Message Count server.
657
Sectors with Low Message Duration Tab

The Sectors with Low Message Duration tab lists the LTE sectors that do not have
sufficient message duration. A sector has low duration if the total message duration of the
sector in the busy hours is below the threshold defined in the
LOW_DURATION_THRESHOLD parameter.
The following table describes the fields in the Sectors with Low Message Duration tab:
Field Description
TAC The name of the TAC to which the sector belongs.
Sector Name The name of the sector with low message duration.
Primary Radio Blocks The average utilization of the primary radio blocks.
Load (%)
Message Duration The total duration of messages, in seconds, in which the sector
(sec) was the primary server.
Sectors with Low Volume Reliability Rate Tab

The Sectors with Low Volume Reliability tab includes details of the sectors whose volume
reliability rate falls outside of the thresholds defined in the MIN_RELIABILITY and
MAX_RELIABILITY parameters.
The following table describes the fields in the Sectors with Low Volume Reliability tab:
Field Description
TAC Group The name of the TAC group to which the sector belongs.
Sector Name The name of the sector with the low reliability.
Carrier The carrier to which the specific sector belongs.
Load (%)
Message Duration The total duration of messages, in seconds, in which the

sector was the primary server.
Reliability Rate The sector data reliability relative to the whole network.
Compared to Network
658
Model Parsing Details Report (LTE)

The Model Parsing Details report includes the details of the log parsing generated during the
model creation.
The Model Parsing Details report includes the following tabs:
 Busy Hours, which displays the busy hour for each date.
 Sector Count Summary Table, which displays a summary of the sector count per
carrier for the calculation set.
 Hourly Data Statistics, which displays the amount and rate of data per hour, for the
calculation set.
 BH Data Statistics, which displays the amount and rate of data in the calculation set,
for the busy hour.
 BH Sector Data Statistics, which displays rate of data missing in the calculation set,
per sector, for the busy hour.
 Sector Data Statistics, which displays a summary of the counters that were
successfully recorded, as well as the number of messages in which each sector
carrier was the primary server.

The General Information tab displays a summary of the LTE model, for example the number
of sectors in the model, and the number of unidentified legs in the messages.
Field Description
Vendor The network vendor.
TACs The TACs of the sectors used in the model.

positioning can be used for creating maps.
counters date
counters date
659
Field Description
No. of sectors with The number of sectors, as primary servers, with

measurement events measurements.
events all days.
No. of measured The total number of measured sectors in the power records
sectors for all days. For example, if a measurement report reports

measured sectors per event.
measurement event
events in BHs all busy hours.
No. of measured The total number of measured sectors in the power records
sectors in BHs for all busy hours. For example, if a measurement report
reports measurements on 4 sectors, 4 is added to this total.

measured sectors per event for the busy hours.
measurement event in
BHs
Unidentified measured The total number of measured sectors in the measurement

sectors in events that were not identified in the environment. For
measurement events example, if a measurement report reports measurements on 2
unidentified sectors, 2 is added to this total.
Percentage of The percentage of measured sectors in that are unidentified.

unidentified measured
sectors in measured
sectors
No. of sectors without The number of sectors in the model without any KPI data.
KPI data
No. of sectors with The number of sectors in the calculation set that have low call
low duration duration. A sector has low duration if the total message
duration of the sector in the busy hours is below the threshold
defined in the LOW_DURATION_THRESHOLD parameter.
660
Field Description
No. of unidentified The number of target sectors (non primary) in measurement

neighbors events that were not identified in the environment.
No. of sectors with The number of sectors whose volume reliability rate falls
low volume reliability outside of the thresholds defined in the MIN_RELIABILITY
rate and MAX_RELIABILITY parameters. Volume reliability defines
the reliability of the sector's data relative to the whole network.
Busy Hours Table Tab

The Busy Hours Table tab displays a list of the busy hours for each date.
The following table describes the fields in the Busy Hours Table tab:
Field Description
Date The date for which the busy hour is displayed.
Busy Hour The busy hour for the specific date.
Sector Count Summary Table Tab (LTE)

The Sector Count Summary Table tab displays a summary of the sector count, per carrier.
The following table describes the fields in the Sector Count Summary Table tab:
Field Description
Carrier The list of carriers included in the model.
Selection Set The number of sectors in the selection set, and that can be
optimized.
Calculation Set The number of sectors that Mentor selected to be in the

calculation set, which can be influenced by changes in the
selection set due to optimization.
661
Hourly Data Statistics Tab (LTE)

The Hourly Data Statistics tab lists both the amount and the rate of data gathered for all
sectors in the calculation.
The following table describes the fields in the Hourly Data Statistics tab:
Description
Field

Note: Only days for which there are relevant events are
listed.
Hour The time of the call-trace data.
Load (%)
Measurements Report The number of messages in which the sector was the primary
Sectors Rate (%) The percentage of expected noise rise counters received.
with
Noise Count The number of sectors in the calculation with reported noise
Rise rise counters for this hour.
Counters
Sectors Rate (%) The percentage of expected downlink volume counters

with DL received.
Volume
Counters Count The number of sectors in the calculation with reported
downlink volume counters for this hour.
662
BH Data Statistics Tab (LTE)

The BH Data Statistics tab lists both the amount and the rate of busy-hour data gathered for
all LTE sectors in the calculation.
mismatch between the primary traffic yielded from the KPIs, and the message duration
yielded from the call-trace data, there may be a time-zone, recording, or data problem.
The following table describes the fields in the BH Data Statistics tab:
Field Description

listed.
Load (%)
Measurement Reports The number of messages in which the sector was the primary
TA Reports Message The number of timing advance events for all sectors for each
Count busy hour.
Message Duration (sec) The total duration of messages, in seconds, in which the
Message Volume The total downlink volume in all sessions for all sectors for
(MBytes) each busy hour.
Sectors Rate (%) The percentage of expected noise rise counters received.
with
Noise Count The number of sectors in the calculation with reported noise
Rise rise counters for this hour.
Counters
Sectors Rate (%) The percentage of expected downlink volume counters

with DL received.
Volume
Counters Count The number of sectors in the calculation with reported
downlink volume counters for this hour.
663
BH Sector Data Statistics Tab (LTE)

The BH Sector Data Statistics tab contains a summary of the data missing from the
network, per sector, for the busy hour. It enables you to check whether you have all the
required call-trace data for each busy hour, and to view the average traffic as well as the
traffic reliability and interaction rate for the busy hour.
mismatch between the primary traffic yielded from the KPIs, and the message duration or
message count yielded from the call-trace data, there might be a time-zone, recording, or
data problem.
The following table describes the fields in the BH Sector Data Statistics tab:
Field Description
Load (%)
Measurement Reports The number of messages in which the sector was the
Message Count primary server.
TA Reports Message The number of timing advance events for all sectors for each
Count busy hour.
Message Duration (sec) The total duration of messages, in seconds, in which the
Message Volume The total downlink volume in all sessions for all sectors for
(MBytes) each busy hour.
664
Field Description
Data Volume Reliability The downlink volume reliability of the messages based on
the downlink volume KPI.
BHs with Rate (%) The percentage of expected busy hours for which there are
Noise noise rise counters for the sector.
Rise
Counters Count The number of busy hours for which there are noise rise
BHs with Rate (%) The percentage of expected busy hours for which downlink
DL volume counters were received.
Volume
Counters Count The number of busy hours for which there are downlink
volume counters for the sector.
Sector Data Statistics Tab (LTE)

The Sector Data Statistics tab enables you to view a summary of the counters that were
successfully recorded, as well as the number of messages in which the LTE sector was the
primary server.
The following table describes the fields in the Sector Data Statistics tab:
Field Description
Load (%)
Measurements Report The number of messages in which the sector was the
Message Count primary server.
665
Field Description
HO Count The number of non-primary measured sectors for which the

sector is primary.
Hours Rate (%) The percentage of expected hours for which there are noise
with Noise rise counters for the sector.
Rise
Counters Count The number of hours for which there are noise rise counters
for the sector.
Hours Rate (%) The percentage of expected hours for which downlink
with DL volume counters were received.
Volume
Counters Count The number of hours for which there are downlink volume
666

Ultima Mentor V 6.7

Uploaded by

Copyright:

Available Formats

Ultima Mentor V 6.7

Uploaded by

Document Information

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

Ultima Mentor V 6.7

Uploaded by

Copyright:

Available Formats

Ultima Mentor v9.

Confidentiality, Copyright Notice & Disclaimer

Status Bar ................................................................................................................................65

Working with Selections ............................................................................................ 148

Network Properties ..................................................................................................... 187

Working with Planned Sites and Sectors .................................................................. 261

Sector and Area Selection Statistics ......................................................................................426

Area Code Optimization ............................................................................................. 512

Antenna Sectors Optimization (UMTS Only) ............................................................. 572

Network Reports ......................................................................................................... 628

Objective of this User Guide

Introduction to Ultima Mentor

Standard Optimization Workflow

The Mentor workflow comprises the following steps:

Step 1: Construct the network environment

Step 2: Collect the call-trace data

Step 3: Create a network model

Step 4: Analyze the network performance before implementing changes

Step 6: Optimize the neighbor list plan

Step 7: Optimize the antenna sectors plan

Step 8: Implement the neighbor list or antenna sectors optimization plan

Step 10: Update the network environment

Detailed Optimization Workflow for Voice

Detailed Optimization Workflow for Data

Installing Ultima Mentor

To install Mentor for the first time

displayed on your desktop if required, and Ultima Mentor is added to the

To activate the Mentor license

Obtaining a License Using a .c2v File

To generate a .c2v file

A license request confirmation is displayed.

Updating Your License

To update your license

o Enter your product key.

Upgrading Ultima Mentor

To upgrade Mentor while connecting to the Mentor server

2. Click Yes to download the compatible client version.

To manually upgrade to a later version of Mentor

displayed on your desktop if required, and Ultima Mentor is added to the

Uninstalling Ultima Mentor

To uninstall Ultima Mentor

To launch Mentor for the first time

1. Double-click the Ultima Mentor shortcut on your desktop.

Ultima Mentor User Interface

The menu bar contains the following menus:

Menu Option Description

New Network Enables you to import a new network into Mentor.

Open Network Enables you to open an existing network in Mentor.

Close Network Closes the currently open network.

Save Network Saves the current network.

Menu Option Description

Import Displays a sub-menu with the following options:

Menu Option Description

Export Displays a sub-menu with the following options:

Print Enables you to print the current network display.

Preferences Enables you to define the various preferences regarding measurement

Exit Exits the application.

Menu Option Description

Undo Undoes the previous operation.