Ultima Mentor

Network Environment and

Model Import

PRIVILEGED AND CONFIDENTIAL. The information contained in this material is privileged and confidential, and is intended only for the use
of the individual to whom it is addressed and others who have been specifically authorized to receive it. If you are not the intended recipient,
you are hereby notified that any dissemination, distribution or copying of this material is strictly prohibited. If you have received this material
in error, please destroy it immediately.
Lesson Objectives

By the end of this lesson you will be able to

import a network environment and model
from the server

Network Environment and Model Import | 2

Main Topics
 Describe the network environment and model in Mentor
 Review environment and model creation
 Introduce the Network Import Wizard
 Discuss optional import methods
 Explore the workflow for importing from the server
 Add planned sectors and sites

Network Environment and Model Import | 3

Mentor Network Environment
The network environment is a representation of the real network,
including all the relevant information required by Mentor to perform
analysis and optimization tasks:

 Hierarchy of network elements (sites, sectors, and antennas).

 Geographical information.
 Network definitions from various sources (updated according to the
latest switch-dump export files).

Network Environment and Model Import | 4

Network Modeling
Mentor analysis and optimization phases are based on the
mobile-measurement logs collected before each phase.

 Mentor uses mobile measurements and network-statistic logs to:

 Create an accurate model of the network behavior, for example,
traffic location, noise level, detected neighbors, and so on.
 Analyze the network performance.

 As these mobile measurements take up a large amount of disk space

while they are being collected, they are typically stored on a special
directory within the file server.

Network Environment and Model Import | 5

Network and Model Import
 Network environment and model can be created both locally on your
desktop or on the Mentor server.

 As part of the project installation, both the environment and the model
are created on the Mentor server by TEOCO experts.
 The network is partitioned into Clusters according to the project
definitions (per customer, per market).

 Each engineer is usually only required to import the environment and

model of the relevant cluster from the server.

Network Environment and Model Import | 6

Network Environment and Model
Creation Overview
Network Environment Creation and Import
The Mentor network environment is created by gathering and importing
the required configuration data into Mentor.

 Configuration data files include physical configuration of the

network, general environment data, and the latest switch-dump files.

 This data is organized according to the Schema Format, a format

recognized by the application.

 The creation of a full network environment is required only once

per cluster.
 Network changes can be updated when required.

Network Environment and Model Import | 8

Network Configuration Data Collection
The required files and instructions for collection are detailed in the
Required Data Inputs document delivered by TEOCO, according to
the relevant vendor.

 All required data should be organized in one folder.

 It should contain daily sub-folders for
mobile measurements.

 It is recommended that the latest switch-dump

export be used to update the files and to
locate any inconsistencies, including missing
or unnecessary sectors.

Network Environment and Model Import | 9

Configuration Files – Mandatory Files
 Profiles – directory containing the files defining the RF characteristics
of the profile of each antenna model in the network.

 Antennas – defines the physical configuration of the network,

including antennas, sites, sectors, RNCs.

 Carrier-Defs – defines the carriers in the network.

 Sector Carriers – defines the sector carriers in the network.

 Handovers – defines the current neighbor-list setting for the network.

 Network Properties – network-specific parameters of the environment.

Network Environment and Model Import | 10

Configuration Files – Optional Files
 Selections (folder)
 Antenna Constraints
 SC Constraints
 Handover Constraints
 Sector Carrier Constraints
 RAB_HHO_CLASSES
 RAB_POWER_CLASSES
 RAB-SHO-Classes
 Neighbor
 Neighbor List Locking
 Terrain

Network Environment and Model Import | 11

Mobile Measurements
 Mobiles constantly communicate with sectors and relay pertinent
information, in the form of logs, including the following information:
 Ec/Io reports.
 Neighboring-sector information.
 RSCP information (according to vendor).

 RNC logs maintain information concerning the mobile’s state in terms

of location (RTD messages) and quality characteristics of a call.

 Power measurements and event-based messages, such as change

of handover state, call attempts, and dropped call logs are
also collected.

Network Environment and Model Import | 12

Mobile Measurements – Collection
 The mobile-measurement data must be collected from all network
sectors for a period of time based on the required analysis and/or
planned optimization phases.

 Different vendors require different collection methods.

 The specific detailed requirements for collecting these logs are

described in the relevant "Required Data Inputs for <Vendor>
Infrastructure" documents.

 Mentor needs two types of logs:

 GPEH logs (Ericsson), CTR/CTUM logs (Ericsson LTE),
or CHRs/IOS trace logs (Huawei).
 Counters file (XML), which contains all the parameters of the RNC.
Network Environment and Model Import | 13
Network Project File
The existing network environment can be exported or saved into
a project file – *.opr or *mpr.

 The file includes references to mandatory and optional

configuration files.

 The project file can be shared and used when importing a new
network into the Mentor client (instead of creating one from
scratch using the configuration files).

Network Environment and Model Import | 14

Network Environment
and Model Import
The Import Wizard
The Import Wizard is used to import a network environment
into Mentor.

In this lesson we will review the workflow for importing an

environment from the server.

Network Environment and Model Import | 16

Import Wizard – General
In the General step, select the method by which to import the
network data, as well as the location of the data.

 Choose the import Method:

 OPR / MPR – Existing Mentor network file.
 Configuration Files – New network.
 Server – Retrieve configuration files from the server.

Network Environment and Model Import | 17

General – Import from Server
 Select the cluster that represents the segment you want to work
with (clusters are defined during the server setup).
 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.

 Choose whether to import

a model (you can also import
a model at a later time).

Network Environment and Model Import | 18

Import from Server – Process Flow
 Upon request for import from the server, the server builds the
environment in Schema Format, including the switch dump and
model, in a folder on the server.

 The Schema Format environment is then sent to the local desktop

client, and the import continues as with an *.opr project file.

 Once the import completes, the Schema Format environment is

deleted from the local desktop client.

Network Environment and Model Import | 19

Import – Data Completion
 Mentor matches the switch dump data to the antennas.txt data to
guarantee each sector in the switch dump has physical data.

 Sectors that appear in the switch dump but can’t be found or have
missing data in the antennas file will be marked as missing data,
and will be locked for optimization.

 Sectors that appear in the switch dump without physical data in the
Schema Format will prompt the user to complete their data, or to
skip their import.

 Neighbor relations to non-imported sectors will be marked as

unknown.

Network Environment and Model Import | 20

Import – Data Completion (cont.)
Following the initial import, if there are sectors with missing data,
you can proceed to these steps:

 Sector Initialization – export the data, update the files and reload
the updated *.opr file.
 This step is displayed only if more than 10 sectors (default) are
missing data or require configuration changes.

 Data Completion – update sector data manually in the GUI.

 This step is displayed only if less than 10 sectors (default) are
missing data or require configuration changes.

The number of sectors for these steps can be defined in the

Advanced tab of Mentor Preferences.
Network Environment and Model Import | 21
Import Wizard – Sectors Initialization
 Check which files should be updated and click Save.
 The network files are saved in Mentor format, as tab-delimited
text, and can be modified using Microsoft Excel.

 After you have modified all the files

according to the list of required
updates, click Load and select the
updated *.opr (mpr) file.

Network Environment and Model Import | 22

Import Wizard – Data Completion
The Data Completion step displays the following errors:

 Sectors missing mandatory data (appear in the left pane).

 Sectors missing antenna profile data (appear 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.

Network Environment and Model Import | 23

Completing the Network Data
 You must complete mandatory data before you can proceed
to the next step.

 In the left pane, select the sectors you would like to include in the
import process and move them to the right pane.

Network Environment and Model Import | 24

Completing the Network Data (Cont.)
 In the right pane, double-click a sector whose data you want to edit,
and enter the missing information.
 You can also select multiple sectors and click Edit, to the
properties of multiple sectors simultaneously.

Network Environment and Model Import | 25

Completing the Network Data (Cont.)
 Edited sectors are displayed in black, signifying that they
contains all the required data.

 After you’ve finished editing the sector data, click Finish

to complete the data import process.

Network Environment and Model Import | 26

Import Validation
Once the import has finished, the Import Completed
dialog box is displayed:

 Details – warning logs.

 Layers – view layers showing any sectors that are missing data or
that have co-SC or PCI conflicts between neighbors.
 Reports – detailed reports of the import process.

Network Environment and Model Import | 27

Import Validation – Network Layers
After importing a network or updating the switch dump, you can
display network-related layers on the map.

 The available layers depend on the network that has been imported,
and whether it includes a model.

 Select the layers you want to load, and click Load.

 (available layers list appear in the next slide).

Network Environment and Model Import | 28

Available Network Layers List
 Locked Sectors – The sectors are marked as locked.
 Locked Sectors - Low Traffic – The sectors have been locked
because of low traffic.
 Missing Data - Carrier <ID> – The sectors are missing mandatory
data from the switch dump, and will not be optimized.
 NL Co-SCs – Two target sectors have the same SC.
 Tier1-Co-SCs – The source and target sector have the same SC.
 Tier2-Co-SCs – The source sector has the same SC as a target's
neighbor.
 Tier3-Co-SCs – The source sector has the same SC as a target's
neighbor's neighbor.

Network Environment and Model Import | 29

Import Validation – Network Reports
The import reports show the results of
the import process in Excel format.

Available reports:

 Import Messages – summary of information and warning messages.

 Import – details of the import process, including warnings.

 GSM related reports (generated if you have a dual-technology network):

 GSM Network Import Details.
 GSM Network Import Summary.
 UMTS-GSM Discrepancy Report – all discrepancies between the
GSM and the UMTS configuration databases.

Network Environment and Model Import | 30

Import Validation – Model Reports
 Model Reports
 Model Errors and Warnings.
 Model Parsing Details – log parsing details.

 You should view all model reports to validate the current model.
 If you decide that the model is inaccurate, you can update the log
files with the required data and recreate the model.

Network Environment and Model Import | 31

Import Reports (Cont.)
 The import and model reports are saved and can be accessed at any
time through the Network Reports.

 You can Open the reports for viewing or

Save them locally to your desktop.

Network Environment and Model Import | 32

Network Management
Mentor networks can be managed in two ways:

 Through the File menu.

 Open one or more networks simultaneously.
 Save networks or save with a new name.
 Save versions of the current network (can be used for comparison
purposes in the future).
 Export the network, terrain file, model,
and saved calculations, for support purposes.

 Through the Network Manager.

Network Environment and Model Import | 33

The Network Manager
You can use the Network Manager to easily manage and organize
your networks in an efficient and convenient way:

 Open networks
 Manage folders
 Find networks
 Rename networks
 Delete network
 Compare networks

Network Environment and Model Import | 34

Planned Sites and Sectors
Planned Sites and Sectors
Mentor enables you to add new planned sites and sectors to the
map area, which allows you to visualize their affect by including
them in analyses and optimizations.

 Planned sites can be added by:

 Importing a predefined text file.
 Manually adding the sites to the map.
 You can export the planned sites to a file for backup.

Network Environment and Model Import | 36

Adding Planned Sites – Import

Network Environment and Model Import | 37

Adding Planned Sites – Manually
Change the cursor to and click on the relevant location on the
map to launch the New Site wizard:

 General – define general properties for the site.

 Sectors – define the sectors that belong to the site.

Network Environment and Model Import | 38

Adding Planned Sectors
Adding manually planned sectors to existing sites
can be done in two ways:

 From the Network menu.

 Right-clicking the relevant site on the map.

Network Environment and Model Import | 39

Submitting Network Changes to the Server
 When you submit data to the server, Mentor analyzes the data and
makes a list of discrepancies between the submitted data and the
data currently on the server.

Network Environment and Model Import | 40

Submitting Network Changes (cont.)
 You are required to accept or reject the discrepancies.
 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.

 After you click OK to submit the changes, you can view a report
showing details of the requested changes, including the old values
and the new values after the changes were submitted.

Network Environment and Model Import | 41

Lesson Summary – Q&A
 Describe the configuration files required by Mentor for
network environment import.
 What are the optional import methods.
 Describe the main network and model reports.
 What is the objective of adding planned sites?

Network Environment and Model Import | 42