Ultima Mentor v6 3 Release Notes

Ultima Mentor™ v6.3

Release Notes

Copyright Notice

Due to a policy of continuous product development and refinement, Schema Ltd. reserves the right to alter the specifications and descriptions outlined in this publication without giving prior notice of any kind. In addition, no part of this publication, taken as a whole or separately, shall be deemed to be

part of any contract for equipment or services.

Schema Ltd. retains the sole proprietary rights to all information contained in this document. No part of this publication may be reproduced, stored in a retrieval system, transmitted in any form or by any

means, including but not limited to: electronic, mechanical, magnetic, photocopy, recording, or otherwise, in use now or in the future, without prior written consent from Schema Ltd.

Copyright ©2009 Schema Ltd.

Ultima Mentor™ Release Notes

Schema Confidential & Proprietary May 2009 page 2 of 39

Table of Contents

1 ............................................................................................................. 4 Overview2 ...................... 5 New and Updated Hardware Vendor Support in Client and Server

2.1 ................................................................ 5 Support for Huawei UMTS V200R0093 ........................................................................................ 6 Mentor Client Changes

3.1 ..................................................... 6 New Workflows and Workflow Enhancements3.1.1 .................................... 6 Updates to the Neighbor List Optimization Algorithm3.1.2 ........................... 7 GeoMapping Analysis Includes a “Combined Analysis” Mode3.1.3 ............................................................................... 11 Filter Legend Values3.1.4 .................................. 13 Support XML Environment Imported from Forsk Atoll

3.2 .................................................................. 14 New and Enhanced Functionalities3.2.1 ......................................................................... 14 Vendor Support Updates3.2.2 ....................................................... 15 Import/Export and Modeling Updates3.2.3 ................................................................................... 16 Analysis Updates3.2.4 ............................................................................ 17 Neighbor List Updates3.2.5 .................................................................. 19 Optimization Module Updates3.2.6 ....................................................................................... 20 Layer Updates

3.3 .......................................................................................... 22 General Updates3.3.1 ............................................ 22 Saving Sector Selections According to Cell ID3.3.2 .................................... 22 Correct Presentation of Remote Sectors on the Map3.3.3 ..................................................................... 23 Unique Carrier ID per Band3.3.4 ............................................. 23 Reports Names Include Name of Calculations3.3.5

........................................................................................................ 23 Sectors and Antenna Properties Display Vertical and Horizontal Antenna

Beamwidth3.3.6 ....................................... 23 Changes to Default Optimization Budget Settings3.3.7 ............................ 23 Traffic Reliability Indicator Includes Data Traffic Services

4 ...................................................................... 24 Mentor Server-Client Integration4.1 ......................................... 24 Indication of Running Server Tasks on Mentor Client

5 ..................................................................................... 25 Mentor Server Updates5.1 ............................................................................................ 25 Server Updates

5.1.1 ...................... 25 Engineering Task Properties can be Edited by Submitter Only5.2 .......................................................................................... 25 General Updates

5.2.1 ..... 25 Model Dates Tooltip Indicates which NEs are Available on the Specific Day5.2.2 .......................................................... 26 Timeout Period for Collection Tasks5.2.3 ...................................................................... 26 Canceling Collection Tasks

5.3 ........................................................................ 27 Advanced Parameter Changes5.4 ................................................................................ 29 Model Status Monitoring

6 ........................................................................................... 30 Product Limitations6.1 .................................. 30 Pivot Tables will not be Created under Certain Conditions6.2 ............................................................. 30 Detailed Mobile Drop Analysis Reports

7 ....................................................................................... 31 System Requirements8 ................................................................................................. 31 DocumentationA ..................................................................................................... 32 Huawei KPIsB ........................................................................... 37 Advanced Parameter Changes



List of Figures Figure 1: Huawei log-directory structure ......................................................................... 5 Figure 2: New Analysis report - Combined Analysis map type ............................................ 7 Figure 3: Creating a combined analysis to present an Ec/Io map where the traffic per bin is

over 20mErlang .................................................................................................... 8 Figure 4: Non-filtered Ec/Io map (threshold = 0) ............................................................. 8 Figure 5: Filtered Ec/Io map (threshold = 20mE) ............................................................. 9 Figure 6: Combined analysis to present traffic map where sector drop rate is over 2% .......... 9 Figure 7: The resultant traffic map and sector selection .................................................. 10 Figure 8: Threshold slider ........................................................................................... 10 Figure 9: Displaying the filtered selection set on the map ................................................ 11 Figure 10: Filtering the legend .................................................................................... 12 Figure 11: Traffic map with filtered legend .................................................................... 13 Figure 12: Preferences dialog box showing Huawei RABs ................................................. 14 Figure 13: Mobile drop tool tip showing signal strength ................................................... 17 Figure 14: Co-SC report after import (sorted by severity) ............................................... 18 ............................................................................ 20 Figure 15: Face-to-face sectors

Figure 16: Face-to-face (A and B) and back-to-back (B and C) sectors .............................. 20 Figure 17: New Folder dialog box ................................................................................ 20 Figure 18: Saving a layer in a folder ............................................................................ 21 Figure 19: Saving sector selections according to cell ID .................................................. 22 Figure 20: Remote sectors on the map ......................................................................... 22 Figure 21: Indication of running server tasks on status bar ............................................. 24 Figure 22: Tooltip showing which network elements were modeled for specific day ............. 25 Figure 23: Timeout for collection tasks ......................................................................... 26



1 Overview This document accompanies the release of Ultima Mentor v6.3. It includes information specific to Ultima Mentor v6.3 and the supported mobile technology (UMTS).

Ultima Mentor v6.3 is a an update to Ultima Mentor v6.2 The update contains a number of issue resolutions as well as the inclusion of key feature sets, as outlined below.

This document contains the following information:

New and updated hardware vendor support in the Mentor client and server Mentor client changes Mentor server-client integration changes Mentor server updates Product limitations System requirements Documentation Huawei KPIs Advanced parameter changes



2 New and Updated Hardware Vendor Support in Client and Server

2.1 Support for Huawei UMTS V200R009 Switch dump – MML

The MML file is a configuration file that contains all the NodeB parameters per RNC. It is generated by the LMT tool.

Export-related feature

• NL: The neighbor list file is an MML script that contains only neighbor list changes

• Power: The power file is an MML script that contains only power changes

• RABs: The RABs file is an MML script that contains only RAB changes

Log directory structure

Figure 1: Huawei log-directory structure

Note: KPIs and logs are mandatory folder names.

The KPIs folder contains the PM counters

The logs folder contains the IOS traces

A full list of the Huawei KPIs is displayed in appendix A.



3 Mentor Client Changes

3.1 New Workflows and Workflow Enhancements

3.1.1 Updates to the Neighbor List Optimization Algorithm The Mentor neighbor list algorithm has been improved to support a more efficient reciprocal neighbor list, using HO rates and counts, based on various constraints and rules. This new approach has enabled adding new features and enhancing existing features, including:

• Forced symmetry for non-optimized cells: When the reciprocity level in the RECIPROCITY_LEVEL advanced parameter is set at “Required”, Mentor will add neighbors to sectors outside the selection, if necessary, to force reciprocal neighbors.

• Lock unknown neighbors only: When Mentor detects an unknown neighbor in the original neighbor list, it locks only the specific unknown-neighbor entry in the original priority, enabling optimization of the rest of the neighbors. However, if the target SC is not known, the source will still be locked in order to prevent co-SC conflicts in the final neighbor list.

• Enhanced overshooting-sector detection and deletion: The overshooting score is now calculated per sector, instead of a score given at the system level. It now reflects the total rate of HOs where this sector is identified as overshooting for the target sector, relative to the total number of HOs. The user can still decide to automatically remove such neighbors based on tier only, or tier and minimal score, according to the OVERSHOOTING_TARGET_VALIDATION parameter settings:

NONE: (default) Overshooting sectors will not be removed.

TIER: High-tier neighbors will be removed based on the OVERSHOOTING_MIN_TIER parameter (default 3, maximum 5, minimum 2).

SCORE_AND_TIER: Only overshooting sectors from the same or a higher tier than OVERSHOOTING_MIN_TIER and whose score is above OVERSHOOTING_MIN_SCORE will be removed.

3.1.1.1 Reciprocity (Symmetry) Processing Changes

As in previous versions, Mentor supports 3 types of reciprocity constraints for neighbor list changes, using the RECIPROCITY_LEVEL parameter:

• None

• Recommended

• Required

Mentor 6.3 includes changes related to the “Required” option. For example, if Mentor recommends that sector A, which is in the selection, should add sector B that is not in the selection as a neighbor, according to the “required” symmetry constraints, sector B must also add sector A as a neighbor to its neighbor list. This will happen, even if sector B is outside the selection set.



3.1.1.2 Unidentified Sectors in the Neighbor List will be Locked from Optimization

When unknown neighbors are detected in the imported neighbor list, only the unknown neighbors are locked, based on the following rules:

• Unknown neighbors will be kept “as-is” in their original priority.

• If the initial priority is beyond the final NL length, meaning the desired priority no longer exists because the NL became shorter, the unknown neighbor will be added to the bottom of the NL.

• If there is no space left in the final NL, the last added neighbor will be removed, and the unknown neighbor will be added in its place.

• All the relevant flags and settings will be copied “as-is” from the original NL.

• Co-SC prevention: If the SC of the unknown neighbor is also unknown, the source sector will be locked.

• Locking: Unknown neighbors cannot be “forbidden” or “locked” in any desired priority. Mentor will give priority to the original unknown neighbors’ priority over any locked neighbors.

3.1.2 GeoMapping Analysis Includes a “Combined Analysis” Mode A widely used analysis process requires the ability to present specific Geo maps only in areas where other Geo maps or KPIs cross specific values, for example, a traffic map where the drop rate is above 0.3%.

The new "Combined analysis" feature enables these kinds of analyses, and many more.

To create a combined analysis map, select the Combined Analysis option in the Analysis wizard.

Figure 2: New Analysis report - Combined Analysis map type

Select the map that you would like to filter, and then the maps or KPls by which to filter this map, including the relevant operators and thresholds.



Figure 3: Creating a combined analysis to present an Ec/Io map where the traffic per bin is

over 20mErlang

Figure 4: Non-filtered Ec/Io map (threshold = 0)



Figure 5: Filtered Ec/Io map (threshold = 20mE)

Figure 6: Combined analysis to present traffic map where sector drop rate is over 2%



Figure 7: The resultant traffic map and sector selection

As shown in Figure 3 to Figure 7 above, the original map can be filtered by other maps, individual bin level values, and also sector-level KPI values.

When selecting KPI in the filtering condition, the original map will be created only for the sectors which cross the KPI filtering condition.

You can also create an “ad-hoc” "combined map" without using the analysis wizard. To create the combined map, select Show Combined Maps on the Network menu. The Show Combined Maps dialog box is displayed, enabling you to select the carriers for which to display the map and the maps by which to filter the selected map.

3.1.2.1 Modifying the Combined Maps Filtering Condition

After the combined map layer has been displayed, you can easily change any of the map thresholds using the threshold slider. To access the threshold slider, right-click a combined maps layer in the Layers pane and select Threshold Slider.

Figure 8: Threshold slider

Note: The threshold can be changed for Map filtering conditions only. Thresholds cannot be changed for KPI filtering conditions.



3.1.2.2 Filtered Selection Set for Combined Analyses

You can now display a filtered selection set, which highlights only those sectors that meet the criteria to be included in the combined analysis.

To display the filtered selection set, right-click the combined analysis layer, and from the shortcut menu, select Display Filtered Selection Set on Map.

Note: This option is relevant only for combined analyses that include KPI filters.

Figure 9: Displaying the filtered selection set on the map

3.1.3 Filter Legend Values By default, all the network entity values are displayed on the legend and on the map. You can now filter numeric legends to color only those entities that match your criteria. For example, you can choose to color only bins where the dropped call rate is above a specific threshold.

To filter the legend values, click the browse button in the legend, and then enter the required values in the Display field of the Layer Properties Legend tab.



Figure 10: Filtering the legend

You can select whether to color All values, or only those Above, Below, or Between specified values. If you decide to filter the legend, enter the relevant values in the fields provided. The layer values will be filtered according to your selection, and only bins with those values appear colored on the map.



Figure 11: Traffic map with filtered legend

If required, you can also edit the default legends to suit your personal preferences and requirements. To edit the default legends, on the File menu select Preferences, then select the Default Legends tab. Select the legend to be filtered then click Edit to filter the values as required.

Note: Legend filtering is not supported for text-based legends, for example, legends that show drop reasons, NL priority, etc.

3.1.4 Support XML Environment Imported from Forsk Atoll Mentor supports importing an XML environment from Forsk Atoll. In order to import a Forsk environment, you must first export the full environment to XML format. The export will include multiple files, including four mandatory files—Antennas.xml, Transmitters.xml, Sites.xml and index.xml. Please note the folder in which these files are located, as it will be used by Mentor in the import process.

In the Import wizard, use the “Import Configuration Files” option and then point the antenna configuration file path to the XML export folder, and point the antenna profiles path to the Antennas.xml file inside the XML export folder.



3.2 New and Enhanced Functionalities Ultima Mentor contains several new product features and enhancements to existing features. This section describes the new and enhanced features in this release.

3.2.1 Vendor Support Updates

3.2.1.1 Huawei UMTS – New RAB Types

Huawei networks include the following RABs, which can be accessed and edited from the RABs tab.

To access the RABs, on the File menu select Preferences, and then click the RABs tab in the Preferences dialog box.

Figure 12: Preferences dialog box showing Huawei RABs



3.2.2 Import/Export and Modeling Updates

3.2.2.1 Client Model Creation Options

modeling options in the Model wizard were renamed, enabling users to better understle options.

For analysis only: Mentor will create a model that can be used for analysis of KP

The and the three availab

• Is only, and not for optimization or GeoPositioning. The model will be created using only the

eld in the Summary page.

e is no log directory in the

g, cluding optimizing tilt, azimuth, and

aps. lied only if

twork Properties

twork properties file, which includes all the advanced parameters controlling the application and algorithm behavior. This is helpful for

ns and methodologies.

To import the network properties file, from the File menu select Import Network

the File menu select Export Network file.

3.2.2.3 Additional File Formats Supported for Importing and Exporting Maps

• layers to GRD format.

B/TIF files for raster layers.

performance pegs, and will be listed as Analysis only in the Model type fi

Note: If you do not select the analysis-only option, and therimport path specified, an analysis-only model will automatically be created.

• For analysis and optimization: (Default) Mentor will create a model that can be used for analysis, and neighbor list, power, and SC optimizations.

• For analysis, optimization, and maps: Mentor will create a model with positioninwhich can be used for analysis, all optimizations inbeamwidth, and/or creating mobile drop, traffic, drop call, performance, or arc mNote: Positioning the mobiles is a time-consuming procedure that should be appyou are sure that you want to optimize the tilt, and/or create positioning maps.

Note that when using the Mentor Server, the model is automatically created.

3.2.2.2 Partial Import and Export of Ne

Mentor enables you to import or export the ne

checking and switching between different sets of operatio

Properties, and then browse to the file to import.

To export the network properties file, on Properties, and then browse to the location to which to export the .properties

Mentor now supports the following formats:

Exporting raster

• Importing TA



3.2.2.4 New Automatically-Created Import Layers

Mentor now creates additional layers during the creation of the network and the model:

• power (validation failure)

Drop Reports

ernational Mobile Equipment Indicator (IMEI) is the identifier of a mobile device’s SI which identifies the SIM). It can be

ndors, device models, or specific units. This entifier, and its breakdown to vendors and models, is now displayed in the detailed drop

report, allowing analysis and filtering based on these properties.

t ensure that:

arameter is set to 1.

• Huawei networks: The DEDICATED_RANAP_MESSAGES option is selected in the IOS

Mentor uses the TACList.txt file to convert the first 8 digits of the IMEI to the mobiles’ vendor and model. For example, if the IMEI is 3513509417431323, according to the TACList.txt file, the first 8 digits, 35135094, represent a Nokia 6610 phone.

The TACList.txt file

C :\ Documents and Settings \> user <\ Application Data\Schema\user\Ultima can\external

or

%userprofile%\Application Data\Schema\user\Ultima Men culators\vulcan\external

n updated).

• NL Co-SCs - source to target co-SCs

• Tier2 Co-SCs - source target1 target2 where SC(source)=SC(target2)

• Tier3 Co-SCs - source target1 target2 target3 where SC(source)=SC(target3)

These layers are created in addition to the already available layers:

• Missing Data – carrier <n>. This layer now shows the missing data per sector carrier, and not per sector.

• User locked

• Locked sectors - Low traffic (reliability failed)

Locked sectors - OH

Note: These layers are created only as needed, meaning only if there is data available for presentation on the map.

3.2.3 Analysis Updates

3.2.3.1 IMEI is Presented in the Detailed

The Inthardware in GSM and UMTS systems (as opposed to IMused to distinguish between mobile device veid

In order for IMEI to be sent during call origination and termination, and to be available for use in Mentor, the user mus

• Ericsson networks: The IMEICONTROLCLLS p

Tracing dialog box.

is located in:

Mentor\KPIsAndCalculators\vul

tor\KPIsAndCal

Note: The user cathe model is crea

te the file before creating the Drop Call analysis report (even after



3.2 in the Detailed Drop Map

The Detailed Drop Map has been enhanced to include the Signal Strength, if available, in the

.3.2 Changes

tooltip.

Figure 13: Mobile drop tool tip showing signal strength

3.2.3.3 Ultima New KPIs

The following Ericsson KPIs have been added:

Name of KPI Description

Number of Total Successful Calls

Shows the total number of successful call attempts for all ca(circuit, streaming, interactive).

ll types

RBS – Frame Loss Ra e Over Iub (%)

Shows the frame loss rate of the data received by the RBS over Iub. t

RBS Level – HS Iub Shows the percentage of timeBlockage Rate (%) because of an Iub limitation

for which HS data was blocked .

3.2.4 Neighbor List Updates

3.2

During the network import process, Mentor creates reports and layers analyzing co-SC conflicts in the network.

The following SC conflicts are analyzed and presented:

• NL (tier 1) Co-SCs - source to target Co-SCs where SC(source)=SC(target)

• NL (direct) Co-SCs - source to 2 target Co-SCs where SC(target1)=SC(target2)

• Tier2 Co-SCs - source target1 target2 where SC(source)=SC(target2)

• Tier3 Co-SCs - source target1 target2 target3 where SC(source)=SC(target3)

For tier 2 and tier 3, 19 additional shortest paths are shown at the bottom of the report.

nations (source to target2 or target3)

.4.1 New SC-Conflict Analysis

the shortest path is shown on top of the report, and up to

Mentor also creates map layers for reported cases:

• NL Co-SC (target1 to target 2)

• Shortest path for tier2 and tier3 Co-SC combi

• In the report, the Type column indicates the type of co-SC that is listed, enabling the report to be filtered from tier 1 up to tier 3 co-SC problems.



Figure 14: Co-SC report after import (sorted by severity)

3.2.4.2 Changes in the SC-Conflict Thresholds

nced report, now called “Potential Co SC Targets”, is filtered by two conditions:

• CoSCRate (1 2) >= MIN_CO_SRAMBLING_CODE_RATIO (default = 10%)

HO cnt (1st CoSC) + HO cnt (2nd CoSC)

This way the report and the layers are focused on the more severe cases. The user can g the initial value will add

ear in the final NL, it uses the followin

When t MBLING_CODE_RATIO (10%):

will count.

(Thset

of r

The following changes have been introduced to better analyze and indicate potential SC problems during the NL optimization process:

The enha

• Min(CoSC1 HO cnt, CoSC2 HO cnt) >= MIN_CO_SRAMBLING_CODE_COUNT (default=50)

Where CoSCRate = HO cnt (2nd CoSC)/ (

control the reported Co-SC severity using the 2 parameters. Reducinmore cases to the report.

When Mentor has to decide which of the co-SCs will appg logic:

he Co-SC rate is above FORBIDDEN_CO_SCRA

• If FIX_CO_ SCRAMBLING_CODE _PROBLEMS=false: Both neighbors will be removed

• If FIX_CO_ SCRAMBLING_CODE _PROBLEMS=true: The locked or higher count Co SCbe favored over the one that is not locked or has a lower HO

Note that if MIN_CO_ SCRAMBLING_CODE _RATIO =< CoSCRate < FORBIDDEN_CO_ SCRAMBLING_CODE _RATIO, the decision will always be the Co SC with the higher counts.

is is possible if MIN_CO_ SCRAMBLING_CODE _RATIO is changed below the default ting.)

Filtering of low count or low rate Co SCs is disabled if a Co SC is forced into the NL as a result eciprocity, manual locking, or unknown locking.



3.2.5 Optimization Module Updates

Two layers are created for ea on plan:

• Scrambling Code Reuses Before (Optimization)

The lay the Co-SC scenarios detected by Mentor in the network before and after opti ill be reduced after optimization, con e ettings.

The a olor reflecting

• e site (distance between antennas is 200 meters or less). These cases have the highest priority n

• Nearb (5 km by default). These cases have 2nd priority, but are more likely to occur than co-located cases.

• Tier 1 HO: The 2 sectors are 1st degree neighbors, i.e. the source and the target sector have the same SC. These cases also have 2nd priority, and have the same weight as nearby-sector cases.

• Tier 2 HO sectors that have the same SC are defined as 2nd degree neighbors in at least one direction. One of t he other is the neighbor of its neighbor (source target1 target2 where SC(source)=SC(target1)). This is a 3rd

Geographi al-b

Additional impacts are based on the distance between the sectors and the relative antenna’s gain between the two sectors on the line-of-sight between them.

The impact is determined by the following formula:

Weight=100

Where:

• Loss = Average(10^-LossA/10, 10^-LossB/10) (Losses are driven from the horizontal antenna

he distance between the sectors in Km

3.2.5.1 Reuse Layers are Created for SC Optimization Plans

ch SC optimizati

• Scrambling Code Reuses After (Optimization)

ers show mization. Usually the amount and level of Co-SCs wsid ring the SC constraints and other optimization s

re re a few type impacts, sorted by severity. Each impact has a different cits severity:

Co Located: The co-SC conflict is caused by 2 sectors that are probably sharing the sam

, a d are the first to be fixed.

y Sector: The distance between the 2 sectors is below MIN_CO_SC_DISTANCE

: The 2 hem is the source sector and while t

priority Co-SC.

c ased impacts:

0*Loss /Dist^SC_DISTANCE_WEIGHT

profiles)

• Dist = t

• The parameter SC_DISTANCE_WEIGHT is equal to 2 as default



Examples:

• A and B: If A and B are 2 face-to-face sectors, 10 km away (gain loss is 0 dB, loss

weight (A B)= 1000 * 1 / 10^2 = 10

rence to estimate other impacts

value is 1):

This example can be used as a simple refe

Figure 15: Face-to-face sectors

2 back-to-back, 10 km away (gain loss is 20 dB, loss value is 0.01) B and C: :

0 * 0.01 / 10^2 = 0.1 weight (B C)= 100

•

stance

optimization engine and will not be displayed.

3.2.6.1 Layer Folders

Mentor enables you to create layer folders under the GIS category, and to drag and drop layers from one or more calculations into these folders.

To create a new folder, right-click the GIS category and select New Folder.

Figure 16: Face-to-face (A and B) and back-to-back (B and C) sectors

Notes:

Score lower than MIN_CO_SC_SCORE_FOR_LAYER (10 points as default) will not be displayed.

for all nearby sectors where the diis below MIN_CO_SC_DISTANCE (5 km).

• The same weight (Nearby sectors) will be given

• Geographical-based impacts with distances over MAX_CO_SC_DISTANCE (50 km bydefault) will not be considered by the

3.2.6 Layer Updates

Figure 17: New Folder dialog box



3.2.6.2 Drag and Drop Layers

You can move multiple layers from the same group up or down in the group hierarchy, to user-defined folders

map before they can be copied to a folder.

• Calculation layers must be from the same calculation. If you want to copy layers from multiple calculations, you must copy each calculation’s layer separately.

3.2.6.3 Saving Sector Selections in Folders

Mentor enables you to save sector selections as layers, and then to save these layers in the Layers pane, either directly under the GIS category, or in one of the folders that you created, as described in section 3.2.6.1.

To save the layer, create the selection and then from the Selection menu, select Save Selection as Layer. Enter the layer name and then select the GIS category or one of your folders in the Folder field of the Save Selection as Layer dialog box.

simultaneously. If required, you can also drag and drop these layers inunder the GIS category using the mouse.

Notes:

• Calculation layers must be displayed on the

Figure 18: Saving a layer in a folder



3.3 General Updates

3.3.1 Saving Sector Selections According to Cell ID Mentor enables you to save sector selections according to the cell ID as well as the sector name. To save the sector selection according to cell ID, in the Save Sector Selection dialog box, select Cell ID in the Files of type field.

Figure 19: Saving sector selections according to cell ID

.2 Correct Presentation of Remote Sectors on the Map 3.3

•

•

ved

Mentor has been enhanced to better display remote sectors or HUB-based cells.

The sector icon is no longer attached to specific BTSs, but to the 1st antenna serving it.

If there is a remote sector, the sector icon will be connected to the serving BTS by a thin blue line.

• If there are multiple remote antennas, antennas 2..n will be connected to the sersector by a red line.

• The following example shows a site with 3 remote sectors, where one sector has two antennas.

Figure 20: Remote sectors on the map

In Google Earth, remote sectors wi g to the location and azimuth of the 1st antenna.

ll be represented accordin



3.3 Unique Carrier ID per Band .3 The carrier ID does not have to be a unique integer anymore, but can be any string. The modeling and switch dump matching is now based on 3 fields—carrier frequency, band, and

lo rent

lusters.

reports.

3.3.5 Sectors and Antenna Properties Display Vertical and Horizontal Antenna Beamwidth

The vertical and horizontal beand Antennas pro l beamwidth on the map, as well as color the legend according to the beamwidth.

The vertical and horizontal beamwidth have also been added to the Sectors and Antennas lists, enabling you to sort these lists according to the beamwidth.

3.3.6 Changes to Default Optimization Budget Settings In order to have better control over the power optimization engine and to make power optimization more conservative, two existing parameters were changed:

• MAX_CHANGED_SECTORS_PERCENTAGE = 50% (instead 70%) – meaning that no more than 50% of the sectors in the selection can be changed. The engine will select the 50% that will offer the best impact on the network according to the optimization goals.

• MAX_POWER_UP_CHANGES_RATIO = 1.25 (instead 2). Meaning that the ratio between the number of “power up” sectors and “power down” should be 1:1.25, i.e. a ratio of 4:5. For every 4 power-down sectors there will be no more than 5 power-up sectors, and vice versa.

3.3.7 Traffic Reliability Indicator Includes Data Traffic Services In order to prevent locking sectors that have high data traffic with hardly any voice traffic, the traffic reliability formula, which appears in the model reports, has been changed and now takes into consideration both data and voice measurements.

The Traffic KPI has also been updated, and now represents the total data and voice traffic.

techno gy. This enables having two carriers called “F1” with different frequencies in diffecities.

This feature solves the problem of having to modify carrier names in the server when addingnetwork elements to c

3.3.4 Reports Names Include Name of Calculations Mentor reports now include the name of the calculation as well as the name of the

amwidth of the antenna are now also displayed in the Sectors perties, enabling you to view the actual horizontal or vertica



4 Mentor Server-Client Integration

ing Server Tasks on Mentor Client The Mentor client Status bar has been enhanced to show an indication of the user’s running

display a menu that enables you to open

the Ultima Mentor Server Admin, or either of the Task Occurrences dialog boxes.

4.1 Indication of Runn

tasks on the server.

If there are any running tasks, the number of running tasks is displayed in the Running Tasks area of the Status bar. You can double-click this area to open the Optimization TaskOccurrences dialog box, or right-click this area to

Figure 21: Indication of running server tasks on status bar



5 Mentor Server Updates

5.1 Server Updates

5.1.1 Engineering Task Properties can be Edited by Submitter Only Engineering tasks can be used by all authorized engineers, however only the submitting engineer can edit any of the task properties.

5.2 General Updates

5.2.1 Model Dates Tooltip Indicates which NEs are Available on the Specific Day

When importing a network model from the server, in addition to viewing the days for which a model was created, you can now also view the network elements for which the network was modeled. This is very important if your network contains more than one network element.

To display the network elements for which there is a model, run your mouse over any of the bolded dates in the Model Date Range dialog box. The name of the modeled network element is displayed in the tooltip.

Figure 22: Tooltip showing which network elements were modeled for specific day



5.2.2 Timeout Period for Collection Tasks ask

properties. After the specified time, the task will be terminated, and a notification will be di

To se eout period, in the Parameters area, enter the maximal task execution time, in minutes, in the Maximal task execution time field.

You can now set a timeout period for a collection task when defining or editing the t

splayed.

t the tim

Figure 23: Timeout for collectio

You can now cancel unning collection t collection task and selecting tcut menu. The collection task occurrence will be

lay in the Collection e.

n tasks

5.2.3 Canceling Collection Tasks an occurrence of a r

Stop from the shorask by right-clicking the

cancelled, and the Tasks pan

Last Occurrence Status will be disp ed as Cancelled



5 nced Para anges The advanced parameters have been added to the Ultima Mentor server:

.3 Advafollowing

meter Ch

Parameters Group

Parameter Description

Analysis O_

(Default = 11)

MAX_ANALYSIS_TASK_HISTORY_TSAVE

The number of occurrences of the same analysis task to save.

Calculations

? * *)

SCHEDULED_OPT_CRON_TRIGGER

(Default = 0 30 8

This parameter was moved from the Optimization group.

Collection MAX_COLL_TASK_HISTORY_TO_

30)

The number of occurrences of the SAVE

(Default =

same collection task to save.

MAX_DAYS_OF_RAW_DATA_TO_

30)

f days to store the

w, or has it been moved?

SAVE

(Default =

The number ocollected data.

Is this ne

Configuration IT_REPORTS_TO_ How long to save reports about DAYS_OF_SUBMSAVE

(Default = 5)

submitted data.

Devices INUTES DEVICES_RECOVERY_M

(Default = 3)

For future use.

FILE_STORAGE_TYPE

(Default = DAS)

NAS: Network-attached storage

For future use.

DAS: Direct-attached storage

SAN: Storage area network

Display VEL imum severity level to display for task details.

MIN_TASK_DETAILS_LE

(Default = WARN)

The min

General TION VERSION_IN_NOTIFICA

(Default = No)

For internal use.



Parameters Group


Import/Export EXPORT_SCRIPTS Whether to export sc

(Default = No) exporting the network element. ripts when

NUM_MODEL_DAYS_TO_EXPORT

(Default = 30)

The number of latest model days to export when exporting the network element.

RESET_LAST_COLLECTED_WHEN_ IMPORT

(Default = Yes)

Whether to reset the last collection time when importing network elements using the <internal operation> scripts.

USE_EXISTING_SCRIPTS_WHEN_ IMPORT

(Default = Yes)

Whether to search for scripts in the existing scripts folder rather than copying the ones in the network element file.

Model MAX_DAYS_OF_MODEL_REPORTS_ TO_SAVE

(Default = 30)

The number of days to save model reports.

MAX_DAYS_OF_RAW_DATA_TO_ MODEL

For future use.

MAX_DROP_SAMPLES

(Default = 1,000,000)

The maximum number of drop records in the model.

MAX_MODEL_TASK_HISTORY_TO_ SAVE

(Default = 3)

The number of occurrences of the same modeling task to save.

MAX_POWER_SAMPLES

(Default = 2,000,000)

The maximum number of downlink RF information records in the model.

MAX_ THROUGHPUT_SAMPLES

(Default = 2,000,000)

The maximum number of throughput records in the model.

MAX_UE_TX_SAMPLES

(Default = 2,000,000)

The maximum number of UE Tx power records in the model.

Optimizations MAX_OPT_TASK_HISTORY_TO_SAVE

(Default = 10)

The number of occurrences of the same optimization task to save.



5.4 Model Status Monitoring The model status monitoring has been enhanced, now enabling you to:

Tasks window.

the modeling

• View the details of the last task occurrences in the Modeling

• Schedule model tasks when defining a new modeling period or when editingtask properties.



6 Product Limitations The following section describes the known product limitations.

6.1 Pivot Tables will not be Created under Certain Conditions

Microsoft Excel pivot tables are limited to a maximum of 8,000 individual items. If the source a for the pivot tables includes additional itdat ems, the tables will not be created.

t riers analyzed, d is time frame.

obile Drop Analysis Reports epending on the network condition, Mentor may document huge amounts of individual

by the Microsoft Excel engine, Mentor will n can be used for further analysis.

In his case, the user should reduce the selection set, limit the amount of caran /or limit the analys

6.2 Detailed MDsubscriber drops in the detailed drop analysis report.

If the amount of drops cannot be presented ge erate a tab delimited TEXT file, which



7 System Requirements Each Mentor server should be configured as follows, according to the number of network elem

CPU: 1 processor is recommended for every 2 network elements (minimum Quad Core,

per processor plus an additional 2GB (Minimum 6GB)

of ce for m r

Network: 1GB Ethernet access to the MSCs and Mentor Clients, 2 ports

eader

3 Server Edition SP3, 64bit

soft Office

client shoull Core, 2.4Gh

mum, 4GB preferred

Hard Disk: 100GB, (optional: additional 250GB)

Ethern

indows XP/Vista

ice

nUltima Mentor includes an resources that help you to use the software effectively. For complete details, please refer to the application’s Online Help.

ne

elp C Click the F1 key from or Ultima Mentor Server Admin dialog box.

e

ents:

2.9GHZ)

RAM: 1GB

Hard Disk: Total supporting long-ter

800–1000GB, SAS drive, (optional: additional storage spaaw data storage)

CD/DVD r

OS: Windows 200

Micro

Each Mentor CPU: Dua

RAM: 2GB mini

d be configured as follows: z,

Network: 1GB

OS: W

et access to the Mentor Server

Microsoft Off

8 Docume tation extensive array of

You can access the Onli

Choose Help > H

Help topics from within Ultima Mentor in several ways:

ontents within any Ultima Mentor

Click th icon at t e itiv to

the topiin the different E rts, hyperlinks will open the Online Help for the specific

report.

he bottom of any dialog box in which this icon appears. The Online and leads you directly to the relevant Help topic while pointing c in the Table of Contents. xcel repo

Help is context sensthe position of

With



A Huawei KPIs ists thThe following table l e Huawei KPIs on which you can base the network analysis:


Absolute RRC DropCall (Count)

Shows the number of release RRC connections due to call drops.

Active Set Message Shows the number of messages per hour, per sector carrier, Count where the sector carrier is part of the active set.

Average DL Bandwidth Utilization on ATM(Kbps)

e average ATM backhaul utilization on up to four ATM ports in the downlink. Shows th

Average DL Bandwidth Utilization on IP (Kbps)

Shows the average IP backhaul utilization on up to four IP ports in the downlink.

Average power (Watt)

Shows the average power of the sector carrier, measured inWatts.

Average power (dBm)

Shows the average power of the sector carrier, measured in dBm.

Average Transmitted Carrier Power (dBm)

Shows the average value of all the TCP reported for a certainperiod. The RNC obtains the TCP values of the cells from the COMMON MEASUREMENT REPORT message received from the NodeB.

Average Transmitted Carrier

e HSDPA TCP of the cells from

Power - HS (dBm)

Shows the average value of all the HSDPA TCP reported for a certain period. The RNC obtains ththe COMMON MEASUREMENT REPORT message received from the NodeB.

Average r

(dBm)

eported for a certain Transmitted CarriePower - Non HS

Shows the average value of all Non-HS TCP rperiod. The RNC obtains the Non-HS TCP values of the cells from the COMMON MEASUREMENT REPORT message received from the NodeB.

Average UL Bandwidth Utilization on ATM

Shows the average ATM backhaul utilization on up to four ATM ports in the uplink.

Average UL Bandwidth

Utilization on IP

Shows the average IP backhaul utilization on up to four IP ports inthe uplink.

Average UL RSSI Shows the average values of all RTWP reported in a certain period.




Average Used DL Bandwidth on ATM (Kbps)

Shows the average bandwidth used on up to four ATM ports in the downlink.

Average Used DL Bandwidth on IP

s in the downlink.

(Kbps)

Shows the average bandwidth used on up to four IP port

Average Used UL M

)

Shows the average bandwidth used on up to four ATM ports in the Bandwidth on AT(Kbps

uplink.

Average Used UL Bandwidth on IP (Kbps)

Shows the average bandwidth used on up to four IP ports in the uplink.

Average User Throughput (bps)

is data in the cell buffers. Shows the average user throughput when there

CS Call Rejects (%) Shows the percentage of CS RABs that were unsuccessfully established due to capability failure.

CS Video Conversational

e average number of CS conversational service RBs in a cell at the downlink bit rate of 64 kbit/sec.

Service (Erlang)

Shows th

EMS Critical Count Shows the number of EMS alarm counters, per element, for alt

on as possible. critical events. These events affect the service and should be dewith as so

EMS Info Count Shows the number of EMS alarm counters, per element, forinformational event

s.

EMS Major Count Shows the number of EMS alarm counters, per element, forevents. These events

major can lead to service degradation, and may

require operator intervention.

EMS Minor Count S alarm counters, per element, for minor events. These events do not affect the service, and do not require operator intervention.

Shows the number of EM

HS RetransmisRate (%)

sion ill be taken into account.

Shows the retransmission rate by the HARQ processes. Up to 10 retransmissions w

HS Users per TTI Shows the average number of high-speed users scheduled in the cell at each 2ms transmission time interval (TTI).

HS-DSCH CoUsage

de umber of SF=16 codes used by HS-DSCH. Shows the average n




HS-SCCHs PowUsage

er is used, then the registered value is the sum of the

individual values.

Shows the HS-SCCH transmitted power per cell. If more than one HS-SCCH code

HSDPA (MB)/Drops Shows the ratio of the HSDPA payload to HSDPA drops.

HSDPA Data DiscardRatio (%

)

entage of discarded user data on HSDPA out of the total user data received. Shows the perc

HSDPA Payload (MB)

Shows the number of MBs transmitted by the MAC-d flow in a cell.

HSDPA Utilization Shows the HSDPA usage in terms of user data. (The percentage of (Data) (%) 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 Payload (MB)

Shows the number of MBs received by the MAC-d flow in a cell.

ISHO CS Success Rate (%)

CS Shows the percentage of successful IRAT handovers duringdomain.

ISHO HS Success Rate (%)

PS rvice.

Shows the percentage of successful IRAT handovers duringdomain for HSDAP se

ISHO PS Success Rate (%)

PS Shows the percentage of successful IRAT handovers duringdomain.

Max power (dBm) Shows the maximum power sampled in the sector carrier, measured in dBm.

Max power (Watt) Shows the maximum power sampled in the sector carrier, measured in Watts.

Maximum DL Bandwidth Utilization on ATM

M e downlink.

(Kbps)

Shows the maximum ATM backhaul utilization on up to four ATports in th

Maximum DL

ation on IP (Kbps)

Shows the maximum IP backhaul utilization on up to four IP ports Bandwidth Utiliz

in the downlink.

Maximum UL

ation on ATM (Kbps)

Shows the maximum ATM backhaul utilization on up to four ATM Bandwidth Utiliz

ports in the uplink.




Maximum UL Bandwidth Utilization on IP

p to four IP ports in the uplink.

(Kbps)

Shows the maximum IP backhaul utilization on u

Maximum Used DL

)

Shows the maximum bandwidth used on up to four ATM ports in Bandwidth on ATM (Kbps

the downlink.

Maximum Used DL Bandwidth on IP (Kbps)

the Shows the maximum bandwidth used on up to four IP ports indownlink.

Maximum Used UL Bandwidth on ATM

Shows the maximum bandwidth used on up to four ATM ports in the uplink.

(Kbps)

Maximum Used UL Bandwidth on IP (Kbps)

Shows the maximum bandwidth used on up to four IP ports in the uplink.

Min power (dBm) Shows the minimum power sampled in the sector carrier, measured in dBm.

Min power (Watt) rier, measured in Watts. Shows the minimum power sampled in the sector car

NACK Ratio Shows the percentage of transmitted blocks that were not acknowledged by the UE, as received by the RBS.

Primary Message Count

Shows the number of messages that were counted for the sector.

PS Call Rejects (%) e to capability failure.

Shows the percentage of PS RABs that were unsuccessfully established du

PS DL Payload – NHS, RLC Level (M

on B)

nd and interactive services. Shows the downlink PS volume of backgrou

PS UL Payload – NoHS, RLC Leve

n l (MB)

nd and interactive services. Shows the uplink PS volume of backgrou

RAB Blocking Rate (%)

unsuccessfully established due to capability failures. Shows the percentage of CS and PS domain calls that were

RAB CS DCR (%) e percentage of CS AMR drops. Shows th

RAB HSDPA DCR (%)

Shows the percentage of HSDPA drops.

RAB PS DCR (%) Shows the percentage of PS domain drops.




RAB VideoCall DCR Shows the percentage of CS 64Kbit/s services. (%)

RRC 1st Assignment %

Shows the percentage of successful RRC connections on the first here 100% indicates thatSuccess Rate ( ) time, w the first RRC was successful.

RRC Access Fail(%)

ntage of RRC acceure Shows the perce ss failures.

RRC Blocking Ra(%)

the percentage of RRC cacongestion.

te Shows lls that were rejected due to

RRC Drop Call Rate (%)

Shows the percentage of RRC ca rll d ops.

RRC IRAT Reselection Ratio (%)

Shows areas where there is a lot of traffic movinetworks towards the 3G network. Tthere are a lot of IRAT HOs from theto quality or coverage problems.

ng from the 2G his can point out areas where 3G to the 2G networks due

Sectors Per Users (%)

Shows the average number of sectors per user.

SHO Factor (%) Shows the ratio between the amoun t ount

t of channel elements thasupport the calls and the am of primary traffic.

SHO Success Ra(%)

the percentage of successnumber of successful RL deletionout of the total number of attem ons.

te Shows ful soft handovers. It shows the s and additions in soft handoffs pted RL deletions and additi

Total Average HDSCH Power

rage HS-DSC measurem

S- Shows the total avedata channel) over the

H power (power of the HSDPA ent period.

Total RAB Success (count)

Shows the number of successfully es the PS and

tablished RABs on CS domains.

Total RRC AccesFailure (count)

the number of RRC access Shows s failures.

Total RRC Success Call (count)

the number of successfulShows RRCs.

Traffic (Erlang) of UShows the average number Es in the Cell_DCH state.

Voice Traffic (Erlang)

the average number of us AMR speech service. Shows ers that use the



B AdThe following advanced

v arameter Chanparameters have been added to the Mentor client:

anced P ges

Parameters Group


Google Earth Display

SECTOR_SIZE

Default = 150 m/492 ft

Defines the are

size at which sectors displayed in Google Earth.

Huawei Provisioning

HUAWEI_MAX_MISSING_CELLIDS (%)

Default = 5.0

Defmis ew switch dump

• If the percentage is below this

warning will be displayed that

implemented

ines the threshold of sectors sing from the n

above which the script will not be used for the power changes.

threshold, the sectors will not be added to the script, and a

the sectors were removed from the power optimization results.

• If the percentage is above this threshold, the power changes will not be according to this script.

HUAWEI_NL_ENABLE_GROUPING

Default = No

Defines whether more than one neighbor-list update command should be sent at a time, in order to speed up the process of changing the neighbor list.

HUAWEI_NL_GROUP_SIZE

Default = 5

t nds to be sent per

batch.

Defines the number of neighbor-lisupdate comma

HUAWEI_SIB11IND in System

Information Block 11 (SIB11). Default = Yes

Defines whether to include neighbor relationships

HUAWEI_SIB12IND

Default = No

Defines whether to include neighbor relationships in SystemInformation Block 12 (SIB12).

HUAWEI_TPENALTYHCSRESELECT the Hierarchical Cell

Default = D0

Defines Structure (HCS) cell reselection penalty timer.



Parameters Group


Model RT_TYPE

T_BASE: Only event-based RRC measurements will

el.

model.

RRC_MEASUREMENT_REPO

Default = BOTH

Defines the type of RRC message recording.

• EVEN

be included in the model.

• PERIODIC: Only periodic RRC measurements will be included in the mod

• BOTH: All RRC measurementswill be included in the

Neighbor List Optimization

FORBIDDEN_CO_SCRAMBLING_CODE_RATIO

Default = 0.1 neighbor list.

Defines the HO count ratio below which both co-SC sectors are rejected from the

MIN_CO_SCRAMBLING_CODE_COUNT

Default = 50.0

e

Defines the minimum number of HO counts for a co-SC target conflict to be displayed in a report,enabling you to focus on the morsevere cases.

MIN_CO_SCRAMBLING_CODE_RATIO

Default = 0.1

rate between the HO counts of the two co SCs for a target co-SC conflict to be displayed in a report, enabling you to focus on the more severe cases.

The formula is HO count (lower count CoSC) / {HO count (Higher count CoSC ) + HO count (higher count CoSC)}

Defines the minimal

OVERSHOOTING_THRESHOLD_RATE (%)

Default = 20.0

Defines the threshold above which the source sector is considered an overshooting sector.

RAB Optimization

HIGH_POWER_THRESHOLD (dB)

Default = 2.0

Defines the threshold (below the current max RAB power) above which a power reading counts towards a change in the max RAB power.

MAX_POWER_LIMIT_FACTOR

Default = 0.5

Defines the multiplier of the percentage of readings above HIGH_POWER_THRESHOLD to determine change in max RAB power.



Parameters Group


MAX_POWER_R99 (dBm)

Default = 8.0

Defines the maximum offset for the R99 power, relative to the CPICH power.

MIN_DL_CODE_POWER_MEASUREMENT

Default = 2,000.0

Defines the minimal number of Downlink Code Power measurements a sector must have in order to be included in the RAB optimization.

SC Plan and Sector Identification Parameters

MIN_CO_SC_SCORE_FOR_LAYER

Default = 1

Defines the score from which co-SCs are displayed in the Scrambling Code Reuses Before and Scrambling Code Reuses After layers.

SITE_WISE_SC_STEP

Default = 8

Defines the difference between the scrambling codes that are allocated sequentially, per site. 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.