optimizer principles for 2.2 cd2

Optimizer Principles

DN0196638Issue 12 en

# Nokia Siemens Networks 1 (112)

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2009. All rights reserved.

2 (112) # Nokia Siemens Networks DN0196638Issue 12 en


Contents

Contents 3

List of tables 6

List of figures 7

1 About this document 91.1 NetAct compatibility and capacity information 91.2 Terms 9

2 Introduction to Optimizer 132.1 Radio network optimization process in NetAct 142.2 Permission management 152.3 Administration 162.3.1 Map administration 162.3.2 Antenna Data Editor 162.3.3 Task management 162.3.4 Polygon area management 17

3 Basic optimization functionalities 193.1 Optimizer main user interface 193.1.1 Navigator 203.1.2 Cell Groups tool view 213.1.3 Scopes tool view 213.1.4 Map 213.1.5 Browser 223.2 Optimization plans 223.3 Network statistics 243.3.1 KPI retrieval 243.4 Threshold sets 253.5 Manual configuration management parameter tuning 253.6 Open interfaces 263.7 Use Cases tool view 27

4 Visualization 29

5 Adjacency management 315.1 Adjacency types 315.2 Adjacency templates 325.2.1 Template assignment rules 325.3 Adjacency constraint management 345.3.1 Adjacency constraint import 345.4 Automated adjacency management 365.4.1 Restrictions for adjacency optimization 365.4.2 Adjacency creation based on distance and antenna bearing 405.4.3 List length reduction in automated adjacency optimization 425.4.4 Distance and measurement based adjacency optimization 43



Contents

6 GSM interference matrix generation 476.1 BCCH Allocation (BA) lists 486.1.1 Temporary BA lists 486.1.2 The number of BCCH frequencies 496.1.2.1 Adjacency ranking when using MBAL 496.2 GSM interference measurements 516.2.1 Measurements needed for Optimizer 516.2.2 Measurements and NetAct capacity 526.2.3 Measurement period 536.3 Retrieving measurements 536.3.1 External and foreign interferers 546.4 Predictions 546.4.1 Basic assumptions behind simple link loss calculations 54

7 WCDMA interference matrix generation 57

8 Measurement-based automated adjacency optimization 598.1 Measurements related to automated optimization 598.1.1 GSM interference data 608.1.2 Detected Set Reporting 608.2 Adjacency-optimization-related KPIs 618.2.1 Fitness value 648.3 WCDMA adjacency KPI retrieval and optimization 66

9 Automated frequency planning 719.1 Allocation scopes 729.1.1 Allocating frequencies for a part of the network 739.1.2 Allocating missing frequencies 739.2 Frequency optimization cases 739.2.1 Full allocation 749.2.2 Allocating planned objects only 759.3 Structure of the allocation algorithms 759.3.1 Algorithm Logic 769.3.2 Channel Assignment 769.3.3 Cost Function Calculation 769.4 User settings to guide the algorithms 779.4.1 Forbidden channels 779.4.2 Passive intermodulation 779.4.3 Frequency groups 779.4.4 Manual separations 789.4.5 MA lists 789.5 BSIC planning 789.6 Interpreting frequency optimization results 78

10 Primary downlink scrambling code management 81

11 Dominance areas in visualization 8511.1 Calculation area 85

12 Multi-PLMN support in Optimizer 87

13 Multi-vendor support in Optimizer 89



13.1 Multi-vendor data 8913.2 Multi-vendor visualization 9013.3 Multi vendor GSM Interference Matrix Creation 9113.4 Multi-vendor restrictions 91

14 Where to find more information 93

Appendix A Supported KPIs 95A.1 ADCE KPIs 95A.2 ADJG KPIs 95A.3 ADJS KPIs 95A.4 ADJD KPIs 96A.5 ADJI KPIs 96A.6 BTS KPIs 96A.7 Cell KPIs 98A.8 TRX KPIs 98A.9 KPIs shown with the 3G_OPTIMIZER license 99

Appendix B Parameters read and optimized by Optimizer Tools 102

Appendix C Default optimization profiles in Browser 107C.1 Object-specific default profiles 107C.2 Default optimization-case-specific profiles 107C.2.1 RNC-WCEL Default Area Codes Analysis 107C.2.2 Other optimization-case-specific profiles 108

Index 112



Contents

List of tables

Table 1. Terms 9

Table 2. Supported CM objects in Optimizer 22

Table 3. ADCE-related KPIs 61

Table 4. ADJG-related KPIs 61

Table 5. ADJS-related KPIs 62

Table 6. ADJI-related KPIs 63

Table 7. Parameters read and optimized by Adjacency Management 102

Table 8. Parameters read and optimized by Frequency Allocation 103



List of figures

Figure 1. Optimization cycle in NetAct 15

Figure 2. Optimizer main user interface 20

Figure 3. The relation between antenna directions and the positions of the sourceand destination sector 41

Figure 4. Priority equation in Equation 2-1 41

Figure 5. Antenna factor 42

Figure 6. Cost function for fitness 64

Figure 7. Mapping a KPI to the fitness value 65

Figure 8. Example of calculating the fitness value 66

Figure 9. Basic List and Rotation slots 68

Figure 10. Summarization level and measurement set 69



List of figures

1 About this document

This document gives an overall picture of Nokia Siemens Networks NetActOptimizer. It describes the principles behind Optimizer’s functionalities,giving you background information you may need when using them.

1.1 NetAct compatibility and capacity information

For information on NetAct system and capacity, and the compatibilitybetween NetAct and network element releases, see the NetActCompatibility and Capacity Information document.

1.2 Terms

The following table explains the terms and abbreviations used in thisdocument.

Table 1. Terms

Term Explanation

3GPP Third Generation Partnership Project

AC Admission Control

ADCE An adjacency between BTSs

ADJG An adjacency from a WCEL to a BTS

ADJI An adjacency between WCELs, inter-frequency

ADJS An adjacency between WCELs, intra-frequency

ADJD An adjacency between WCELs, intra-frequency (Soft HandoverBased on Detected Set Reporting)

ADJW An adjacency from a BTS to a WCEL

AVG Average



About this document

Table 1. Terms (cont.)

Term Explanation

AFP Automatic Frequency Planning

ARP Average Received Power or Allocation/Retention Priority

APN Access Point Name

BA list (or: BAL) BCCH Allocation List

BCC Base station Color Code

BCCH Broadcast Control Channel

BCF Base Control Function

BSC Base Station Controller

BSIC Base Station Identity Code

BSS Base Station Subsystem

BSSGP BSS GPRS Protocol

BTS Base Transceiver Station

C/I Carrier to Interferer Ratio

C/Ia Adjacent Channel Carrier to Interferer Ratio

C/Ic Co-channel Carrier to Interferer Ratio

CIP Carrier over Interferer Probability

CIR Carrier to Interference Power Ratio

CDEF Current Default Territory Setting

CM Configuration Management

CS, CSW Circuit Switched

CSV Comma-separated values

DCN Data Communication Network

DL Downlink

EGPRS Enhanced General Packet Radio Service

EWCE External WCDMA cell

EXCC External cell collection

FEP Frame Erasure Probability

FMCG Inter-system measurement control

FMCI Inter-frequency measurement control

FMCS Intra-frequency measurement control

FR Frame Relay

GIS Geographic Information System




Term Explanation

GGSN Gateway GPRS Support Node

GPC GPRS Control

GPRS General Packet Radio Service

HLR Home Location Register

HO Handover

HOC, HC Handover Control

HOPG Inter-system Handover Path

HOPI Inter-frequency Handover Path

HOPS Intra-frequency Handover Path

HOSR Handover Success Ratio

HSCSD High Speed Circuit Switched Data

HSDPA High Speed Downlink Packet Access

HSN Hopping Sequence Number

ICR Interferer over Carrier Ratio

ID Identifier

IP Internet Protocol

IRP Integration Reference Point

KPI Key Performance Indicator

LAC Location Area Code

LLC Logical Link Control

MAIO Mobile Allocation Index Offset

MAL (or: MA list) Mobile Allocation List

MBAL Measurement BCCH Allocation (BA) List

MML Man-machine Language

MS Mobile Station

NCC Network Color Code

NCL Neighbor Cell List

NE Network Element

NRT Non-real time

NSEI Network Service Entity Identifier

NSVC Network Service Virtual Connection

QoS Quality of Service



About this document


Term Explanation

PAPU Packet Processing Unit

PCU Packet Control Unit

PDU Power Distribution Unit

PI Performance Indicator

PLMN Public Land Mobile Network

PM Performance Management

POC Power Control

PS, PSW Packet Switched

RAC Routing Area Code

RF Radio Frequency

RNC Radio Network Controller

RRM Radio Resource Management

RXLEV Received Signal Level

SAC Service Area Code

SACB Service Area Code for Broadcast

SACCH Slow Associated Control Channel, bi-directional

SDCCH Stand Alone Dedicated Control Channel

SGSN Serving GPRS Support Node

SMS Short Message Service

TBF Temporary Block Flow

TCH Traffic Channel

TREC Treatment Class

TRX Transceiver

SSS Scheduling Step Size

TSL Timeslot

UE User Equipment

UL Uplink

UTM Universal Transverse Mercator

WAP Wireless Access Protocol

WBTS WCDMA Base Station

WCDMA Wideband Code Division Multiple Access

WCEL WCDMA Cell



2 Introduction to Optimizer

NetAct Optimizer is used in the statistical network-wide optimizationprocess in NetAct. Optimizer provides visibility to current network behaviorby combining the actual GSM and WCDMA network configurationparameters and measured performance statistics with advancedvisualization and analysis functionality. Parameters can be optimizedmanually for small changes or automatically by choosing from the rangeof optimization solutions provided by Optimizer. Optimizer can be used fora single cell or for a whole region, or even across multiple regions.

The result of optimization algorithms can be visualized on a geographicalmap before downloading the optimization plan to the network. The planwith the changed parameters is sent to the NetAct Configurator where it isvalidated and provisioned to the network.

The advantages of the solution are:

. Optimizer uses statistical performance measurement data

As the input data for algorithms is accurate (measurements of a realnetwork), the output is also more accurate than with a signal-propagation-estimate-based process in a planning tool.

. Using measurements makes the tuning process faster

Instead of heavy calculations based on raster map - where, forexample, the interference matrix is calculated by considering signalstrengths in each map pixel - a mobile measurement report is used.When the data is processed in Optimizer, only some analysis isneeded.

. Increased level of automation

With Optimizer, the whole optimization cycle is faster than withplanning tools. As Optimizer is implemented in the NetActFramework, the actual configuration data and measurement reportsare available for processing. The network topology in Optimizer is



Introduction to Optimizer

always consistent with the actual network data. When runningOptimizer for the first time, some customizing is needed, such asparameters needed to guide the generation algorithms. Once theparameters are set, the next optimization round is more effortless.

Optimizer obtains performance data from the BSC release S11.5 and S12measurements. On top of OSS4 CD Set 3, S11 is also supported. Data isalso obtained from RNC via an interface to the database. Any preferredexternal tool can be used for monitoring performance before and afteroptimization.

The Optimizer solution is composed of basic and licensed functionalities.Visualization based on geographical map and manual adjacency andparameter management are basic optimization functionalities. Thefollowing functionalities are optional:

. Advanced visualization

. GSM automated adjacency optimization

. WCDMA automated adjacency optimization

. GSM Performance Optimization

. WCDMA Performance Optimization

2.1 Radio network optimization process in NetAct

The optimization process usually takes place when the monitoredperformance drops below the set targets, when a periodical tuning task isto be started or when there is need to optimize the behavior of newnetwork elements in the network.

Measurements are used for analyzing the network and serviceperformance development against set targets. A detailed analysis isperformed to find the reasons behind decreased performance and toselect the right corrective actions. In this phase, the relations betweenperformance indicators and element parameters are analyzed. After theanalysis phase, the configuration parameter settings are optimized and theset quality criteria are checked. When the corrections are verified andimplemented into the network, the quality monitoring cycle starts from thebeginning.



Figure 1. Optimization cycle in NetAct

Optimization can be targeted to improve the radio resource usage rate(optimization) by changing the operating point on the capacity-coverage-cost trade-off curve. Statistical optimization also sets the limits andoperation targets for real time optimization loops, such as radio resourcemanagement (RRM) in network elements.

Optimization is also involved when the network is enhanced with new cellsor new services, or changes are made in the service provisioning, and soon. As soon as elements are activated in the network and they can bemeasured, they can be optimized as well.

2.2 Permission management

Optimizer provides the means to restrict some users from performingcertain tasks. When Optimizer has been installed, only users who have theNetwork Administrator role have all the permissions. For example, to startWCDMA measurements (for RAS06), you either need to have the NetworkAdministrator role or the permission operation RUN_RNC_MEASUREMENTSincluded in the role assigned to you.

The user permissions can be granted by using the NetAct PermissionManager tool. For instructions, see NetAct Permission Manager Help.

For more information on user management in general, see ManagingUsers.

Optimisationin

NetAct

MeasureAnalysewith

Reporter

TuneImprovewith

Optimizer

Analysewith

Optimizer

Implementwith

NetActConfigurator




2.3 Administration

There are some administrative tasks that need to be done, eitheroccasionally or during the roll-out phase of the network, to keep Optimizerworking the optimal way. Some tasks are carried out by the administratoruser and some tasks can be executed by any Optimizer user.

2.3.1 Map administration

Optimizer uses Geographic Information System (GIS) to visualize digitalmap data. The map data needs to be initialized before optimization can bestarted even if Optimizer is used without any map data. Only maps that aremade using Universal Transverse Mercator (UTM) projection can be used,and the UTM zone needs to be defined even if map data is not used. Also,individual tiles must be rectangular in the UTM coordinate system. Thismeans that each edge of the tile must be either in the North-South or East-West direction exactly.

The Map Administrator tool is used to define the basic settings for GIS. Formore information on GIS, see Geographic Information System Principles,and on managing GIS settings, see Map Administrator Help.

2.3.2 Antenna Data Editor

Optimizer includes an administration tool, Antenna Data Editor, for fastimport and synchronization of non-network data, that is, the site andantenna relations to the cells and (W)BTSs of the actual network. This toolis run by the administrator user whenever new sites and antennas, andrelations to the cells in the network need to be updated. Antenna DataEditor supports data import from any external system producing a CSVdata input file that complies with the import format definition.

Antenna Data Editor is a stand-alone administration application that isincluded in the basic Optimizer installation package. For more information,see Checking site and antenna data in Optimising a Network UsingOptimizer. For instructions on using the tool, see Antenna Data EditorHelp.

2.3.3 Task management

Every Optimizer user can monitor the ongoing task executions in the TaskManagement view in Optimizer. You can check task status reports, removetasks, and view the task configurations during normal operations.



For more information on the Task Management tool view, see TaskManagement tool view in Optimizer Help.

2.3.4 Polygon area management

Optimizer Map supports the selection of sites by polygon area. You candefine polygon areas on top of a geographical map for private use and alsodefine the polygons as public (seen by all users), if necessary. Forinstructions, see Creating and managing polygons in Optimizer Help.




3 Basic optimization functionalities

The following sections describe the basic functionalities available inOptimizer by default. The main application user interface is also presentedwith some details of the interface components to give an idea howOptimizer works in general.

3.1 Optimizer main user interface

The Optimizer main user interface consists of the following panes: theNavigator Pane, the Scope pane, the Map/Tool Pane, and the BrowserPane. The tool views open into these panes. If several tool views open intothe same pane, each tool view has its own tab that you can close ifneeded. In addition, the main user interface also contains the main menubar and the main toolbar.

The availability of a tool view depends on the purchased Optimizersoftware license. The tool views can be accessed from the Tools menu ofthe main menu bar or by using the Navigator pop-up menu.

The practical optimization and analysis work happens always in thecontext of tool view(s) and with the defined optimization scope (target).The optimization scope is selected from the main window, which opens bydefault when Optimizer is started. It is the core workspace for objectbrowsing, navigation, and manual optimization. Each tool view may havedifferent scope selected for optimization at the same time.

The following figure shows the panes in the Optimizer main user interface:



Basic optimization functionalities

Figure 2. Optimizer main user interface

1. The Navigator Pane. By default, Navigator opens into this pane. Formore information, see section 3.1.1 Navigator.

2. The Map/Tool Pane. By default, Map opens into this pane. For moreinformation, see section 3.1.4 Map.

3. The Cell Groups/Scopes Pane. By default, the Scopes tool view andthe Cell Groups tool view open into this pane. For more information,see sections 3.1.3 Scopes tool view and Cell Groups tool view.

4. The Browser Pane. By default, Browser and the Use Cases tool viewopen into this pane. Note that Browser is not open when Optimizer isstarted but only when an element or elements are listed to Browser.For more information, see sections 3.1.5 Browser and 3.7 UseCases tool view.

3.1.1 Navigator

Navigator offers three tree views that are suitable for different optimizationpurposes: the Default view, the Hardware Topology view, and theAdjacency Management view. For example, you can use a different treeview presentation depending on whether you optimise adjacencies, orbrowse or tune objects of the hardware topology. For more information,see Navigator in Optimizer Help.



3.1.2 Cell Groups tool view

Note

To be able to manage cell groups, you need either the OptimizerAdministrator role or the Optimizer Provisioning User role assigned toyou.

The Cell Groups tool view helps in visualizing and managing cell groups.You can create, modify, delete, hide, unhide and rename cell groups,revert to default cell groups and change the generality of the cell groups.For more information on how to manage the cell groups, see Cell Groupstool view and Managing cell groups in Optimizer Help.

The cell groups are arranged in a particular order both in the Cell Groupspane and in the Visualization pane, the most general cell group beinghighest on the list and the least general cell group lowest on the list. Thegenerality of the cell groups can be modified using the Move cell group upand Move cell group down icons in the Cell Groups pane toolbar. For moreinformation on visualizing cell groups on Map, see Cell groups in OptimizerPrinciples

3.1.3 Scopes tool view

In the Scopes tool view, you can create, modify, and delete tailoredscopes. You can use the tailored scope as a starting point for differentoptimization tools. Scopes are always global. For more information, seeScopes tool view and for related instructions, see Managing scopes inOptimizer Help.

3.1.4 Map

Map is used to show the network objects and related configuration andperformance data, and optimization results on a geographical (scannedand/or digital) map. Map can also be used for manual adjacencymanagement. For more information, see Map in Optimizer Help.




3.1.5 Browser

Browser is not open when Optimizer is started but only when an elementor elements are listed to Browser. In Browser, you can visualize any CM,PM, and any combination of CM and PM data. With Browser, you canbrowse and edit objects in a table view. Object filtering and mass editingare supported. From Browser, you can export data to a CSV file.

Also, with powerful Browser profile management you can customize theview of the object parameters and the object relations for your ownpurposes, or you can share your profiles with other users. The Browserprofiles support object hierarchy but are always determined according tothe parent object. The lower level (child) objects can be freely selected.Browser has a set of default profiles (for each object type) that all userscan always use when Optimizer is open. For more information, seeBrowser in Optimizer Help.

3.2 Optimization plans

All parameter tuning and optimization in Optimizer happens viaoptimization plans. If you optimize only on top of an actual (live) networkconfiguration, the optimization plans do not depend on NetActConfigurator configuration management plans (planned networkconfigurations). For more information and instructions, see Managingoptimization plans in Optimising a Network Using Optimizer.

Sometimes you also need to take the planned network configurations intoaccount in the optimization process (for example, network due to networkroll-out preparation). For this, Optimizer supports the import of plannedobjects from the Configurator configuration management plan. You canuse this feature before starting the actual optimization work. Configuratorconfiguration management plans are made using CM Editor or they areimported from some other tool (such as Plan Editor) using CM OperationsManager.

Optimizer supports the following NetAct Configuration Management (CM)and topology CM objects:

Table 2. Supported CM objects in Optimizer

ADCE

ADJG

ADJI



Table 2. Supported CM objects in Optimizer (cont.)

ADJS

ADJD

ADJW

ANTE

BAL

BCF

BSC

Cell

FMCG

FMCI

FMCS

GCAL

HOC

HOPG

HOPI

HOPS

POC

RNC

SGSN

TRX

WBTS

WCAL

WCEL

In addition, GSM cells are modelled as Cell objects.

For a list of the parameters of these objects that are read and optimized byOptimizer, see Appendix B Parameters read and optimized by OptimizerTools.

When you are ready with the optimization plan and the changes can beapplied to the actual network, the optimization plan that contains themodifications to the actual network configuration is exported to theConfigurator plan database. When the optimization plan has beenexported to Configurator, its consistency must be checked. Checking theconsistency of the plan and provisioning the plan to the network are doneby using CM Analyser and CM Operations Manager. The only exception is




instant adjacency provisioning, in which changes to adjacencies can beprovisioned to the network directly from Optimizer. The changes are savedinto a plan as usual, but the provisioning phase is automated. For moreinformation on provisioning the plan to the network, see chapterTransferring the optimization plan to the network in Optimising a NetworkUsing Optimizer. If the versions of network elements change inConfigurator, this data can be updated in Optimizer by running themetadata refresh process. See Refreshing metadata in Optimizer Help fordetails.

For plan management (create, delete, import, export, and merge),Optimizer has simple user interface tools, Open Plan dialog and CM DataExchange dialog, which are included in its basic functionality. You canaccess these dialogs from the main menu and the toolbar under it. For adescription of the dialogs, see Open Plan dialog and CM Data Exchangedialog in Optimizer Help.

3.3 Network statistics

Optimizer has the following tool views where you can view networkstatistics:

. The Key Performance Indicators tool view

. The Interference Matrices for GSM tool view

. The Interference Matrices for WCDMA tool view

In addition, the Preparing GSM IM creation wizard displays networkstatistics and also guides through all the steps needed in preparing forGSM Interference Matrix creation.

For more information, see Tool views and Preparing GSM IM creationwizard in Optimizer Help. See also Managing network statistics inOptimising a Network Using Optimizer.

3.3.1 KPI retrieval

Key performance indicators (KPI) are the most important indicators ofnetwork performance. KPI reports allow the operator to detect the firstsigns of performance degradation and prevent the development of criticalnetwork problems. KPIs on the regional level can be used for analyzingperformance trends, on the RNC level for locating problems, and on thecell level for troubleshooting specific cells.



You can select the KPIs summarization level in the Optimizer main toolbar.For busy hour, you can select Daily Busy Hour or Weekly Busy Hour. Busyhour is the hour when there is most traffic. The time of the busy hour canvary from week to week and from day to day. Optimizer calculates the busyhour on-the-fly for every BTS.

Custom Measurement combines several Daily level measurements as onemeasurement. Those are the result of WCDMA Measurements but theycan be also manually created by combined from Daily level WCDMAMeasurements. See more in WCDMA adjacency KPI retrieval andoptimization, and Viewing and combining KPIs and Starting WCDMAmeasurements in Optimizer Help.

For a list of KPIs, see Appendix A Supported KPIs. See also sectionRetrieving KPI data in Optimising a Network Using Optimizer.

3.4 Threshold sets

A threshold set is an ordered set of threshold ranges. Threshold sets canbe defined for KPIs (Key Performance Indicators) and CM parameters forvisualization. Threshold sets are global, which means that they are visibleto all users, and therefore, they are not plan specific or user specific.

Threshold sets can be created, edited, and deleted in the Threshold Setsdialog. For instructions, see Editing threshold sets in Optimizer Help.

KPIs and CM parameters are classified according to the network hierarchyin the Threshold Sets dialog, where they can be found undercorresponding network elements.

The colors used with the threshold sets for visualizing parameters andKPIs are defined in the Select Gradient dialog.

3.5 Manual configuration management parametertuning

You can optimise parameters either manually for small, occasionalchanges or automatically by using the optimization algorithms provided byOptimizer. For more information, see Editing network object parameters inOptimising a Network Using Optimizer.




Object parameters can be edited manually in Browser when a plan isopen. You can create a profile for the network elements shown in Browser.The profile defines which child elements are shown beneath the profiledelement and which parameters and KPIs are shown for these elements.For example, in this way you can select possible child elements related toa BTS. Parameter-related problems can be better visualized using profiles.For instructions, see Managing a visualization profile in Optimizer Help.For a list of profiles, see Appendix C Default optimization profiles inBrowser. See also chapter Visualization.

3.6 Open interfaces

To complete the optimization process, some additional data handling isrequired. Optimizer contains open interfaces to handle information. Inaddition, optimization results can be transferred in a table view to externaltools, and forbidden channels can be imported from a CSV file to aselected BSC.

Interference Matrix open interface

Optimizer generates an Interference Matrix based on mobile measurementinformation collected to Reporter via BSCs. The matrix is used whengenerating adjacency lists and in allocating frequencies. Themeasurement-based Interference Matrix is more accurate than anyprediction-based Interference Matrix and it enables more accuratefrequency optimization. Predicted interference can be generated to newcells or cells where measurements are missing otherwise, for example,because of so called blind spots. Predicted interferences are based onantenna directions and distances between cells. You need to assign auser-specific non-zero priority number for each interference set that is tobe included in the Interference Matrix. For instructions, see Creating aninterference matrix for GSM in Optimizer Help.

With the Interference Matrix open interface you can export the InterferenceMatrix from Optimizer to use it with an external tool, for example, anotherallocation tool. It is also possible to import Interference Matrices fromexternal systems to Optimizer, if, for example, measurements areinsufficient in some BTSs to enable accurate Interference Matrix creationand the matrix is completed manually or based on estimates outsideOptimizer.

The interference data is stored in the Optimizer database. When youexport the interference matrix, it is saved to a specified location in CSVformat. A more accurate description of the format can be found in theInterference Matrix Open Interface document.



Browser export

A selected area or all Browser data can be exported with an export file.Exported Browser data can be used in other tools (for example, MicrosoftExcel).

Import of forbidden channels

Forbidden channels can be imported from a CSV file into Optimizer forselected BSCs or cells to be used in frequency allocation. The CSV fileshould have the following columns: Mode, BscId, LAC, CI, and ForbiddenChannels. The values are separated with commas and the records withline feeds. The mode column attributes are the following: ADD, REP, andDEL. For more information, see Importing forbidden channels inOptimising a Network Using Optimizer. For instructions, see Importingforbidden channels in Optimizer Help.

Import of intermodulation groups

It is possible to import intermodulation groups into Optimizer and to assignthe groups to cells. In frequency allocation it is possible to take intoaccount the channels that cause and suffer from intermodulation.Intermodulation is caused by poor antennas or otherwise faulty hardware.For instructions, see Importing intermodulation groups in FrequencyAllocation Help.

Import of adjacency constraints

You can import adjacency constraints to Optimizer from a CSV file. Formore information on this, see Import of adjacency constraints.

3.7 Use Cases tool view

By default, the Use Cases tool view opens to the Browser pane (the lowerright pane) in the Optimizer user interface. The tool view providesguidance on performing different workflows or use cases. When you clickthe name of the use case, the use case opens displaying a check list of thedifferent phases the steps you need to follow to complete the workflow.Based on what you want to do, you can choose the desired path byselecting from different options using check boxes or radio buttons. Whenyou have selected the desired path, the relevant steps are displayed.




4 VisualizationBrowser

In Browser, you can visualize any CM, PM, and any combination of CMand PM data. The default optimization profiles in Browser serve asexamples on how to use the Browser Profile Editor to create optimization-case-specific profiles and how to use them for optimization or visualization.You can freely combine CM and PM data to form the profiles. For moreinformation on Browser, see section 3.1.5 Browser. For more informationon Browser profiles, see Appendix C Default optimization profiles inBrowser. See also section 3.5 Manual configuration managementparameter tuning.

Map

On Map, you can use the cell visualization settings (Dominance Area, CellIcon, Cell Size, Cell Label, and Border Color), the site visualization settings(Site Icon, Site Size, and Site Label), the adjacency visualization settings(Adjacency Line, thickness, and label), the interference visualizationsettings (Interference Line), and the distance visualization settings(Distance Color) to visualize CM parameters or KPIs. The Distance KPIsettings can show Propagation Delay and Timing Advance which are cell-specific and can be visualized as arcs on the map and as histograms. Forinstructions, see Visualizing Propagation Delay on Map and VisualizingTiming Advance on Map in Optimizer Help. Using Threshold Sets, it ispossible to create user-specific threshold profiles. You can also calculateinterference based on the interference matrix and visualize it on Map ascolored interference lines. In cell and BTS level visualization, Optimizeralways uses master BTS values. For more information, see section 3.1.4Map. See also Map in Optimizer Help. For instructions, see Changing anobject’s visualization settings and Calculating interference for visualizationin Optimizer Help.



Visualization

Cell groups

Cell groups can be used for identifying different cell types on Map. Cellgroups can be customized based on object parameters. Cell groups areused as the Default quality indicator (color) in the Visualizations pane forboth Cell icon and Dominance area. The cell groups are divided intoActual, Planned and Foreign cell groups. In the Visualization pane legendvisible cell groups can be selected by selecting and unselecting the checkboxes for relevant cell groups. If the cell belongs to multiple cell groups,the coloring is based on the most specific cell group.

If you select the quality indicator other than Default in Cell Icon, the cellson Map are visualized such that they belong to the active cell groupcontaining the selected quality indicator's parameters. The cells on Mapare colored according to the color swatches next to the legends.

You can also find the Cell Groups parameter field in the Browser pane.When a Cell/WCEL is listed to Browser, this field lists the cell groups of theselected Cell/WCEL. If the Cell/WCEL belongs to multiple cell groups, allthose cell groups are listed under the Cell Groups field in Browser.

Multi-vendor

Multi-vendor data can be visualized on Map and in Browser. For details,see Multi-vendor visualization.

Profiles

User-specific visualization settings can be stored in Visualization Profiles,including the KPIs and CM parameters selected for visualization. A newprofile is a copy of the current profile, and public profiles are copies of theprivate profiles. The visualization settings take effect immediately but arenot automatically saved. Public profiles can be edited and deleted by otherusers. For more information and instructions, see Managing a visualizationprofile in Optimizer Help.



5 Adjacency management

Adjacencies define the relationship to allow mobile call handover (HO)between cells. Adjacencies can be created, modified, and deletedmanually either on Map, in Navigator, or in Browser. For instructions, seeOptimizing adjacencies in Optimising a Network Using Optimizer. Forinformation on measurement-based automated adjacency optimization,see chapter 8 Measurement-based automated adjacency optimization.

5.1 Adjacency types

Depending on the type of cells for which the relationship is defined, thereare different types of adjacencies:

. ADCE, an adjacency between Master BTSs

. ADJW, an adjacency from a Master BTS to a WCEL

. ADJG, an adjacency from a WCEL to a Master BTS

. ADJS, an adjacency between WCELs, intra-frequency

. ADJD, an adjacency between WCELs, intra-frequency (SoftHandover Based on Detected Set Reporting).

. ADJI, an adjacency between WCELs, inter-frequency

All adjacency types can be displayed on Map at the same time orseparately. The adjacencies may have different coloring depending ontheir type. The direction of the adjacency is also visualized. Adjacencystate (deleted/actual/planned/in provision) can also be used as filteringcriteria of the visible objects. All these settings can be customized peruser. An adjacency can be visible on Map only if the target cells are visible.



Adjacency management

Note

ADJS and ADJD KPIs are combined under one object type.

The adjacency target cell can also be a foreign BTS (GSM) or external cell(WCDMA).

5.2 Adjacency templates

Optimizer shows the available adjacency templates that have beencreated in CM Editor. Templates contain default parameter values foradjacency creation. You can select the templates to be used for differentadjacency types and create the rules for each source and target cellcombination according to which these templates are assigned. Templatescan be assigned per cluster, or individual controllers (BSC or RNC) orgroup of controllers can be selected for a template assignment. If nomatching adjacency template is found, Optimizer assigns the Systemtemplate by default. This should be avoided because the System templateparameter values do not work properly in a real network.

For more information, see section Creating adjacency and cell templatesin Optimising a Network Using Optimizer.

5.2.1 Template assignment rules

There are two kinds of adjacency template assignment rules: cluster-specific assignment rules and controller-specific rules. The rules consist ofsource and target categories. The source and target categories canconsist of the following items:

. GSM. Cell Types. The value of the Cell Type parameter in BTS is

mapped as one category.. Frequency Band In Use. The value of the Frequency Band In

Use parameter in BTS is used.

. WCDMA. Frequency. UARFCN is mapped as one category.



. Both WCDMA and GSM. A parent template assigned to BTS or a WCEL. The parent

template assignment can be either actual or planned. Thetemplate assignment can be seen in Browser in the OriginalTemplate column. Planned template assignment can be usedif the plan has been imported from Configurator.

. * symbol. The category does not have to match with the data in the

source cell.

Both the source and the target cell can belong to several categories. In thiscase, the AND operation is applied between the rules. The rule isapplicable to adjacency if both the source and the target categories matchwith the source and target cell data. If there are several applicable rules foradjacency, the following priorities are used:

. The controller-specific rule is always more important than thecluster-specific assignment rule.

. The source category is more important than the target categorywhen there is the same priority level of categories in the source andtarget categories.

. In general, rules are applied with priority from the more precise tomore general.

The priorities are the following (in the order of importance):

1. Templates (WCDMA and GSM)

2. Cell Type (GSM)

3. Frequency Band In Use (GSM)

4. Frequency (WCDMA)

5. * symbol (WCDMA and GSM)

For instructions on creating, assigning, and deleting template assignmentrules, see Managing template assignment rules in Optimizer Help.




5.3 Adjacency constraint management

There are adjacency constraints only in actuals as globals. Adjacencyconstraints are not network objects that could be provisioned. You cancreate two types of adjacency constraints in Optimizer: mandatory andforbidden adjacency constraints.

The automated adjacency creation algorithms always check adjacencyconstraints when adjacencies are deleted or created. If there are forbiddenadjacency constraints, the adjacency cannot be created or it can bedeleted by the automated adjacency optimization. If there are mandatoryadjacency constraints, the adjacency cannot be deleted or it can becreated (if it does not exist) by the automated adjacency optimization.

In manual adjacency creation, forbidden adjacencies are checked and ifthey exist, the adjacency cannot be created before the constraint isremoved. In addition, mandatory constraints are checked and if they exist,the adjacency cannot be deleted before the constraint is removed.

For instructions on managing adjacency constraints, see Managingadjacency constraints in Optimising a Network Using Optimizer, andCreating adjacency constraints and Deleting adjacency constraints inOptimizer Help.

5.3.1 Adjacency constraint import

You can import adjacency constraints to Optimizer from a CSV file. Youcan import constraints to an empty database, or to a database whichalready contains constraints. The import operation overwrites existingconstraints in the database with the same source and target cellidentification. Furthermore, if the import file contains overlappingconstraints with the same source and target identification, only the lastconstraint is imported. The constraints to be imported can be defined asmandatory, forbidden, or removed (in other words, the old constraint isremoved from the database).

In Adjacency Constraint Import, identification of cells is:

GSM Cells:

. MCC

. MNC

. LAC

. Cell ID



WCDMA Cells:

. MCC

. MNC

. RNC Identifier

. Cell Identifier

The format of the import file is CSV (Comma Separated Values) and thecolumns have headers in this order:

Parameter name,Type,Possible values:

ADJACENCY_TYPE, string, [ADCE, ADJW, ADJS,ADJI, ADJG]

S_MCC, string S_MNC, string

S_RNC_ID, string, Empty for GSM Cells

S_GSM_LAC, integer, Empty for WCDMA Cells

S_CELL_CI, integer

T_MCC, string

T_MNC, string

T_RNC_ID, string, Empty for GSM Cells

T_GSM_LAC, integer, Empty for WCDMA Cells

T_CELL_CI, integer

ACTION, string, [MANDATORY, FORBIDDEN, REMOVE]

INFO, string, [the range is limited by the database

column to less than 512 characters], Note that if the

length in import file is longer it is cut from the end.

Can be empty.

All columns must exist no matter what the adjacency type is. In the case ofGSM Cells, the *_RNC ID column can be empty. In case of WCDMA Cellsthe *_GSM_LAC columns can be empty. In the following, an example ofthe import file is provided:

ADJACENCY_TYPE,S_MCC,S_MNC,S_RNC_ID,S_GSM_LAC,S_CELL_CI,

T_MCC,T_MNC,T_RNC_ID,T_GSM_LAC,T_CELL_CI,ACTION,INFO ADJG,

244,5,4,,11891,244,5,,9112,62076,MANDATORY,Must be mandatory

ADCE,244,5,,9112,63265,244,5,,9112,13,MANDATORY,Must be

mandatory ADJS,244,5,4,,11733,244,5,4,,11732,FORBIDDEN,Should

not ever be created ADJW,244,5,,9112,9540,244,5,4,,11889,

MANDATORY,Must be mandatory ADCE,244,5,,9112,9540,244,5,,9112,

256,REMOVE,Constraint not anymore needed

The INFO column can be used for free format info text which can be madevisible on Map, in Browser and in the Adjacency Optimization tool inAdjacency Browser. On Map the info text is only visible as a tooltip of aconstraint object but not with adjacency. In Browser, info text is visible onlywith constraint object. In the Adjacency Optimization tool, the info text isvisible with the adjacency object itself.




In Adjacency Optimization, rules can be run after import to deleteadjacencies where forbidden adjacency constraint exist and to createadjacencies where mandatory adjacency constraints exist.

Tip

In Adjacency Optimization Tool in Adjacency Browser there are allcolumns available for import. Data can be copied to a file which can beimported.

For instructions, see Importing adjacency constraints in Optimizer Help.

5.4 Automated adjacency management

Optimizer provides two methods for creating adjacencies automatically:

. Adjacency creation based on distance and antenna direction forGSM, WCDMA, and between the systems.

. Measurement-based adjacency creation and deletion. For moreinformation, see chapter 8 Measurement-based automatedadjacency optimization.

For more information and instructions, see section Optimizing adjacenciesautomatically in Optimising a Network Using Optimizer.

5.4.1 Restrictions for adjacency optimization

In unidirectional adjacency creation, an adjacency is created only if allthresholds are met, that is, each optimization value is better than thecorresponding threshold. An adjacency is deleted if all of the thresholdsare not met, that is, at least one optimization value is worse than thecorresponding threshold. Optimization value means KPI value, distance,or any value that defines how good an adjacency is.

For information on bidirectional adjacency creation, see AdjacencyOptimization tool view in Optimizer Help.

There are also restrictions for the algorithm. For some algorithms, the usercan decide whether to ignore them or take them into account (controllablerestrictions), but the rest of them cannot be exceeded (restrictionsuncontrollable for the user).



Restrictions controllable by the user

By default, the optimization algorithm does not create or deleteadjacencies (bi-directional or unidirectional) to an Indoor Cell, but the usercan enable creation or deletion in the user interface. A cell is defined asindoor if any of the antennas related to the cell has an indoor antenna. Anantenna is indoor if the user defined state parameter contains the stringindoor. The string is case insensitive. There can be other strings in theparameter. In/Out Gateway Cells should not be defined as indoor cells ifthey are wanted to be included in optimization without enablingoptimization of all indoor cells.

The optimization algorithm enables the creation or deletion of adjacenciesto or from a foreign BTS or EWCE (External WCDMA cell).

According to the "Technical Note TN 046 Restriction on number of cells inSIB11/12 due to inconsistency problem in 3GPP TS 25.331", themaximum number of neighbors (of WCDMA WCELs) with anyconfiguration is guaranteed to be 47 (35 if HCS is used) for RAS06 orbefore . You can change the value in the Preferences dialog. Forinstructions, see Managing preferences in Optimizer Help.

RU10 (3GPP R6, Correction target RU10: RAN1323 Extension of SIB11(SIB11bis) implements SIB11bis which enables the SIB11+SIB11bis toaccommondate all 96 cells and solves the contradiction in the earlierspecification. SIB11bis is included as standard feature in RU10. It shouldbe noted that only R6 and later UEs are capable of decoding SIB11bis.RAN Parameters AdjsSIB, AdjiSIB and AdjgSIB can be used to disable thetransmission of a neighbour info in SIB11/12. In Addition, in RU10 RNC theneighbours can be selected for SIB11bis with these Adjx parameters.Values for these are:

. 0, No = does not belong to SIB11 or SIB11bis

. 1, SIB= belongs to SIB11

. 2, SIB= belongs to SIB11bis

It should be noted also that limitation still remains with the SIB12, which isused for connected mode (not CELL_DCH) neighbor info.

The following rules apply to GSM dual band adjacency creation:

. BTS in PGSM900 band can have maximum 18 adjacencies to BTSsin bands EGSM900+GSM1800.

. BTS in GSM1800 band can have maximum 16 adjacencies to BTSsin band GSM900.




. BTS in 850 band can have maximum 18 adjacencies to BTSs in1900 band.

. BTS in 1900 band can have maximum 22 adjacencies to BTSs in850 band.

For more information on restrictions that can be controlled, see AdjacencyOptimization tool view in Optimizer Help.

Restrictions uncontrollable by the user

The cases when adjacencies are never created and/or deleted by theoptimization algorithm are the following:

. Adjacency optimization does not delete adjacencies that have amandatory adjacency constraint. Mandatory adjacency constraintsare defined on Map or in the Browser.

. The user can create forbidden adjacency constraints between cellsin Navigator and on Map. Adjacency optimization does not create anadjacency where it is forbidden.

Collision types

In addition to restrictions for the algorithm, also collisions can occur inadjacency optimization. The collisions types are the following:

. Same BCCH in source and target cells and Same BCCH BSICcombination in ADCE NCL (Neighbor Cell List). The ADCE NCL has more than one cell with the same BCCH-

BSIC combination or the source and target cell have the sameBCCH BSIC.

. Same Scrambling Code and UARFCN Combination in ADJW NCL. The ADJW NCL has more than one cell with the same

scrambling code-UARFCN combination

. Same Scrambling Code and UARFCN Combination in ADJS NCL. The ADJS NCL has more than one cell with the same

scrambling code-UARFCN combination or the source and thetarget cell have the same scrambling code-UARFCNcombination.

. Same Scrambling Code and UARFCN Combination in ADJI NCL. ADJI NCL has more than one cell with the same scrambling

code-UARFCN combination.

. Same Scrambling Code and UARFCN Combination in 3 Cells SHOADJS and ADJI NCL



. The combined ADJS and ADJI NCL in three cells’ SHO hasmore than one cell with the same scrambling code-UARFCNcombination (in other words, this means neighbors andneighbor’s neighbors of WCELs).

. Same BCCH BSIC Combination in ADJG NCL. The ADJG NCL has more than one cell with the same BCCH-

BSIC combination.

. Same BCCH BSIC Combination in 2 Cells SHO ADJG NCL. The ADJG NCL in two cells’ SHO has more than one cell with

the same BCCH-BSIC combination.

. Same BCCH BSIC Combination in 3 Cells SHO ADJG NCL. The ADJG NCL in three cells’ SHO has more than one cell

with the same BCCH-BSIC combination.

If collisions are created for ADCEs, it is recommended that FrequencyAllocation is performed after Adjacency Optimization. If collisions arecreated for ADJSs, it is recommended that Scrambling Code Allocation isperformed after Adjacency Optimization. Collisions created for ADJI,ADJW, and ADJG can be corrected only manually in Optimizer. Therefore,it is not recommended to create these collisions.

If ADJSs or ADJG are to be created to several rotation plans, all thecreated adjacencies in all the rotation plans are checked. For example, ifcollisions are not allowed, all the created adjacencies can be in thenetwork at the same time without new collisions occurring. The restriction"Same BCCH BSIC combination in 3 Cells SHO ADJG NCL" may be tootight in practise. Therefore, it is also possible to only restrict collisions intwo cells in SHO.

Note

No scrambling code collision checking is done for ADJD adjacencies.




Note

The following rule is applied to all collisions (except to "ADCEs to TargetCell with Same BCCH as Source Cell"): if the actual data or a plancontains cells which already have an existing collision and if you havenot enabled the creation of corresponding collisions, new adjacenciesare not created for those cells even if the creation of new adjacencieswould not result in new collisions. Note that if the adjacencies whichcaused collisions are deleted by the algorithm before running thecreation algorithm, new adjacencies can be created. For example, ifyou have not enabled the creation of ADJGs which cause the sameBCCH-BSIC combination in the ADJG NCL and if the WCEL hasADJGs which have the same BCCH BSIC in the target cells, ADJGsare not created to that WCEL until the BCCH BSIC collision is correctedin that WCEL.

5.4.2 Adjacency creation based on distance and antenna bearing

Adjacency creation based on distance and antenna direction allowscreating and deleting of adjacencies by using distance and/or bearing ascriteria. This method can be used for initial adjacency creation when thenetwork objects are not yet in the air, but it provides also means for fastmass creation or deletion of actual objects. This is useful, especially whenmanaging WCDMA adjacencies.

Creating adjacencies based on distance and antenna bearing includes thefollowing steps:

1. User defines the maximum distance D for the adjacency to becreated.

2. User defines the maximum angle q (Maximum Theta Angle). In thefollowing figure, theta1 is the angle between the antenna bearingand the direction of the vector joining the source and destinationsites, similar to theta2. Theta angle is theta1 + theta2. Theta1 andtheta2 are always positive (>=0).



Figure 3. The relation between antenna directions and the positions of thesource and destination sector

3. The algorithm creates adjacencies between all sectors that belongto the same site.

4. The algorithm filters all sites that have distance lower than (d < D)and (theta 1 + theta 2 < Maximum Theta Angle) and createsoutgoing adjacency from that sector to all sectors within the range.

5. The highest priority is assigned to each adjacency created in Step 3,while adjacencies created in Step 4 are prioritised according to thevalue of the adjacency creation factor P. The higher the value of P,the higher the priority of the adjacency in that site.

Figure 4. Priority equation in Equation 2-1

In the Priority equation in Equation 2-1,. d is the distance between sites. D is the Maximum Distance. O1 is the “Omni Antenna Correction Factor” for the source cell

(X2,Y2)

(X1,Y1)

1

2 d 1

2




. O2 is the “Omni Antenna Correction Factor” for the target cell

. A is Antenna Factor

The higher the value of P the higher the priority of the adjacency is inthat sight.

Omni Antenna Correction Factor (O1 or O2) is 1 if the antenna is notomni. Omni Antennas have smaller antenna gain than normalantennas. Therefore, using the Omni Antenna Correction Factor, weget more equal results. The smaller the value, the smaller the priorityvalue when the source and/or target cell's antenna is omni. Thedefault is 0.8.

When the source or the target cell have multiple antennas/powerdivider, the priority is calculated for all antenna combinations. Theantenna combination which results highest Priority is used.

Figure 5. Antenna factor

In the antenna factor A,. F (Antenna Correction Factor) has the range [1…0]. The

default value is 0.99.. For omni antennas, O1 or O2 are 0.. If the distance is 0, there is no connecting line between sites

and Theta1 and Theta2 are defined differently:

Theta1 = Theta2 = │ │SourceAntennaBearing1 │ - ││SourceAntennaBearing1││The Antenna Correction Factor and Omni Antenna CorrectionFactor can be adjusted in the Preferences dialog underAdjacency Optimization. For instructions, see Managingpreferences in Optimizer Help.

5.4.3 List length reduction in automated adjacency optimization

Automated adjacency optimization tries to reduce the Neighbor Cell List(NCL) so that the NCL length is not longer than the Maximum NCL length.Reducing the list length is started from the poorest adjacencies.

Adjacency poorness is defined as follows:



If no measurements are involved, Priority defines poorness (Priority heremeans distance and antenna angle based priority). This applies for alladjacency types.

If measurements are involved, the definitions for poorness are as follows:

. For existing remaining adjacencies (ACTUAL,UPDATED). ADCE: HO Attempts [N]. ADJS, ADJG, or ADJI: Fitness

. New adjacencies (CREATED. ADCE: FEP, CIP or ARP. ADJS: If Final list is selected: Fitness; if DSR is selected: DSR

Priority. ADJG or ADJI: Fitness

Maximum NCL length is defined as follows: The smallest from the listlengths in Options → Preferences →Adjacency Management→Maximum Amount of ADxx and the adjacency type specific Max listlengths defined in the Adjacency Optimization tool view (Common tab→Adjacency list lengths) are used, and the smaller one is selected. Inthe case of ADCE, a Cell specific BTS Constraint "Maximum length ofADCE Adjacency List" is also considered and the smallest of the three isused.

The algorithm to reduce the list length is as follows:

1. If adjacency type is selected for creation, remove the poorestCREATED adjacencies from the plan, until the NCL length is smallerthan the maximum NCL length.

2. If adjacency type is selected for deletion, remove the poorestACTUAL/UPDATED adjacencies from the plan, until the NCL lengthis smaller than the maximum NCL length.

5.4.4 Distance and measurement based adjacency optimization

Adjacencies can be optimized based on distance only (see cases 1-3below), or measurements can be used (see case 4).

If both deletion and creation of adjacencies are selected and nomeasurements are used, the creation can undelete adjacencies anddeletion can remove created adjacencies from the plan. Undeletion isdone using the parameters under the Creation tab in the AdjacencyOptimization tool view. Removing of adjacencies from the plan is done




based on parameters under the Deletion tab in the Adjacency Optimizationtool view. In this case created and undeleted adjacencies are optimized atthe same time, so that an optimal solution is found (see Case 3 below). Formore information, see Adjacency Optimization tool view in Optimizer Help.

Four different cases of distance based adjacency optimization aredescribed below.

1. Only deletion is selected and no measurement are used:. Deletion is done based on the deletion thresholds for

ACTUAL, UPDATED, CREATED. Undeletion is done based on the deletion thresholds for

DELETED adjacencies. List length reduction is done for ACTUAL and UPDATED

adjacencies

2. Only creation is selected and no measurements are used:. Created adjacencies are removed from the plan based on

creation thresholds. Optimizer tries to add DELETED adjacencies and created

adjacencies based on creation thresholds. List length reduction is done for CREATED adjacencies

3. Both deletion and creation are selected and no measurements areused :. Deletion is done based on deletion thresholds for ACTUAL,

UPDATED, CREATED adjacencies. Created adjacencies are deleted based on creation thresholds. Optimizer tries to add DELETED adjacencies and created

adjacencies to the plan based on creation thresholds. List length reduction is done for ACTUAL, UPDATED, and

CREATED adjacencies

4. Either deletion or creation is using measurements:. If deletion is used, ACTUAL and UPDATED adjacencies are

deleted based on deletion thresholds. If creation is used, CREATED adjacencies are removed from

the plan based on creation thresholds. If deletion is used, DELETED adjacencies are undeleted

based on deletion thresholds. If creation is used, new adjacencies are created based on

creation thresholds



. If creation is used, list length reduction is done for CREATEDadjacencies

. If deletion is used, list length reduction is done for ACTUALand UPDATED adjacencies




6 GSM interference matrix generation

Interference Matrix (IM), which is primarily based on interference-relatedmeasurements but which can also be complemented with predictions,provides interference data for adjacency management and frequencyplanning -related algorithms.

An interference matrix represents the interference relations between cellsif they use the same frequency (co-channel) or adjacent frequency(adjacent channel). Interference can be computed or expressed withdifferent mathematical methods such as ARP (Average Received Power),CIP (Carrier over Interferer Probability), or FEP (Frame ErasureProbability).

In Optimizer, Interference Matrix for Nokia NEs are created from the mobilemeasurement reports (MMR) that have been collected from a live network.For Siemens, measurements are in binary format and for other vendorsmeasurements are in CSV file format.

Predicted interference can be calculated for new planned cells, or cellswhere measurements are missing otherwise, for example, because ofblind spots. Note that blind spot cells have the same BCCH frequency asthe serving cell and as a result, the mobile phone cannot measure them.To remove the blind spot cells from the IM, measured interference sets canbe combined with sets which have been measured earlier and withpredicted sets. To create a new interference matrix, you need to define apriority value for all the sets that are to be included in the IM. Prioritydefines the importance of an interference set. Usually, the highest priorityis given to the set that is based on the new measurements. A measuredset has more importance even if the predicted set has equal priority. Apriority must be given to sets of each interference type (CIP, ARP, andFEP).

It is recommended to use Optimizer with dedicated BCCH frequencies.The BCCH block does not need to be a continuous band: you can also useseveral slots if they are dedicated to BCCH use only. It is possible tomeasure a mixed band as well, but that requires more manual work. Notethat in the case of dedicated BCCH, the number of TCH frequencies is not



GSM interference matrix generation

limited and even if only the BCCHs are measured, the inter-celldependency is also applicable to TCH frequencies. As the signal strengthsof the surrounding cells are studied in the measurement period, theinformation is also valid for TCH frequencies. In the frequency allocationphase, different interference thresholds are given to TCH frequencies andBCCHs, thus achieving tighter reuse for TCH frequencies with a higherlevel of expected interference.

The structure and contents of an interference matrix are described in moredetail in the document Interference Matrix Open Interface. For informationon interference matrix generation, see sections Pre-requirements forinterference matrix creation and Creating an Interference Matrix for GSMin Optimising a Network Using Optimizer. For detailed instructions, seeCreating an interference matrix for GSM in Optimizer Help. For moreinformation on predicted interference, see section 6.4 Predictions.

6.1 BCCH Allocation (BA) lists

Normally, the BCCH Allocation (BA) lists of a BTS contain BCCHfrequencies of the adjacent cells. During the measurements, the BA listsmust contain every BCCH frequency used in the network. The BA listsmust be changed for every BTS in the BSC before measurements arestarted.

6.1.1 Temporary BA lists

The idea of having a temporary BA list for measurements is to have a list ofthe BCCHs of all the cells, including cells that are not defined asneighbors. Before connecting to a neighbor cell, mobile phones first listento the BCCH in the BA list to verify sufficient signal strength and quality. Byadding all possible BCCHs to the BA list for the duration of themeasurement period and measuring all surrounding cells, all the requireddata for correct adjacencies and frequency planning can be collected. Ifthere are fewer than 32 BCCHs, both the current and possible adjacentcell BCCHs are included in the BA list.

The temporary BA list is defined for the measurement period and you needto return the original BA list to the network once the measurements arecompleted. You can change the BA list as well as measurementscheduling using MML commands.



To enable the BTS to receive the BA list, the double BCCH Allocationfeature must be activated in the BTS. Furthermore, configuration shouldnot be changed during the measurement period because then themeasurements no longer correspond to reality. The original BA listtogether with other parameter data is returned when the measurementsare ready.

6.1.2 The number of BCCH frequencies

The procedure for creating temporary BA lists depends on the number ofBCCH frequencies:

. If there are 32 or fewer BCCH frequencies, the plan for the BA listchanges can be created in CM Editor or in Optimizer using thePreparing GSM IM creation wizard. For instructions, see Activatingmeasurements with 32 or fewer BCCH frequencies in Optimising aNetwork Using Optimizer.

You can set the common restriction for the maximum amount ofADCEs in the Preferences dialog under Adjacency Management.For instructions, see Managing preferences in Optimizer Help. Youcan also set the same parameter optimization case specifically in theCommon tab of the Adjacency Optimization tool view. For moreinformation, see Adjacency Optimization tool view in Optimizer Help.

. If there are more than 32 BCCH frequencies in the network, themeasurements need to be run in several cycles of equal length butwith different BA lists. Rotating frequencies in BA lists can be done inthe following ways:. automatically in BSC S11 (or newer) by using the

Measurement BA List (MBAL) feature and Total FEPmeasurements, or

. using the BAL Rotation tool for rotation of BA lists in S10.5 (ornewer) and with CF and DAC measurements

For instructions, see Using the BAL Rotation tool for measuringmore than 32 frequencies or Using MBAL and total FEPmeasurement of BSC S11 to measure more than 32 frequencies inOptimising a Network Using Optimizer.

6.1.2.1 Adjacency ranking when using MBAL

Adjacency ranking is needed if the S11-level MBAL is used and thenumber of adjacencies needs to be reduced during the measurements. Torun Interference Measurements using MBAL rotation, ADCEs for everyBTS must be ranked according to their importance.




You can define parameters for adjacency ranking algorithm and startadjacency ranking using the Start Adjacency Ranking dialog. In the dialogyou can choose if HO Attempts to ADCE or HO Traffic Share are used inadjacency ranking. The algorithm sets the value for Neighbor Cell Rankingfor ADCEs in BTS if the ADCE is not ranked or if the old ranking isinadequate. The value for the most important adjacency is 1 and for theleast important 32 (thirty-two is the maximum number of adjacencies forone BTS).

Note that if a large number of adjacencies are ranked, the plan size grows.With the Neighbor Cell Ranking Change Threshold parameter, you canminimise the number of changes needed in the network and thus minimisethe plan size. Mandatory adjacencies are ranked first.

Adjacency ranking algorithm

Ranking is performed for one BTS at a time. Only outgoing ADCEs areranked. Deleted adjacencies are not taken into account. Ranking isperformed in four different ranking groups in the following order:

1. Adjacencies with mandatory adjacency constraint and KPIs

2. Adjacencies with mandatory adjacency constrains but without KPIs

3. Adjacencies with KPIs

4. Adjacencies without KPIs. Note that if there are no KPIs, the newranking is arbitrary.

Each group has its own ranking range that is valid only within thatparticular group.

For example, a cell can have 25 ADCEs of which:

. five have been deleted

. three are mandatory with KPIs, ranking from one to three

. two are mandatory without KPIs, ranking from four to five

. ten are common adjacencies with KPIs, ranking from six to 15

. five are common adjacencies without KPIs, ranking from 15 to 20

Ranking is needed in the following cases:

. If any of the ADCEs in the ranking group has a wrong or poorranking, all the ADCEs in that group are ranked again

. If ranking is below 0 or higher than 32



. The ranking value does not belong to the range for that rankinggroup

. In groups where there are KPIs, if the new ranking differs from theold ranking to a greater extent than defined in the Rank ChangeThreshold

. If more than one ADCEs have the same ranking within the group

6.2 GSM interference measurements

BSC provides the measurements that are needed for mobile-measurement-based optimization of adjacencies and frequencies of thenetwork. Nokia Siemens Networks NetAct supports the whole automatedplanning process, and it uses the BSC measurements as well as thenetwork configuration database as inputs to the optimization logic. Themeasurements used are Channel Finder (CF) measurement and DefinedAdjacent Cell measurement (DAC), or Total FEP (Frame ErasureProbability) in S11 that is optional to DAC and CF measurements.

For Siemens, measurements used is Smart Carrier Allocation (SCA) inbinary file. For other vendor, measurements such as Cell name, InterfererARFCN and Interferer BSIC are in CSV file.

The Configurator module of NetAct is also needed to manage BSSelements. Optimizer uses the functionality of Configurator to get the actualnetwork configuration.

In addition to interference matrix, traffic data is also used when a newfrequency plan is computed. The interference matrix contains aquantitative description of interference relation and is not weighted withtraffic. However, traffic measurements are taken into account in the costfunction of the Frequency Allocation tool. The interference matrix can alsobe exported to be used with a preferred external AFP tool. Other relevantfactors are taken into account by changing the parameter settings of theFrequency Allocation cost function.

6.2.1 Measurements needed for Optimizer

Optimizer needs the following measurements to be activated for the Nokiacell at BSC level:




. Defined Adjacent Cell (DAC) measurement, which collects dataabout all cells defined as adjacent cells

. Channel Finder (CF) measurement, which collects data about cellsthat are not adjacent cells

OR

. Total FEP measurement (in S11, optional to DAC and CF)

For Siemens measurements such as Smart Carrier Allocation (SCA) inavailable in binary file. For other vendors the measurements are in CSVfile. The CSV file is available in two formats: one with Date and Timecombined in the same column and the other with Date and Time in aseparate columns. User should mention the format and the otherparameter details of the importing CSV file in the InterferenceMeasurement Retrieval dialog. The measurements that are available in theCSV file are as follows:

. Cell name in the CSV file should match with the Cell nameparameter in Optimizer when it goes through CM adaptation.

. The Interferer ARFCN parameter is the BCCH frequency of theinterferer.

. The Interferer BSIC parameter has a 2 digit value similar to NCC andBCC.

. The unit of Interferer average signal strength can be either RXLEV ordBm (modulo value).

The measurement scope and measurement period are defined in theAdministration of Measurements application. The measurements areactivated per BSC, and all the BTSs in a BSC collect the information. Formore information, see Administration of Measurements Help.

Measurements should be started simultaneously and with the samemeasurement period. The supported measurement period is 24 hours.

6.2.2 Measurements and NetAct capacity

By default, Channel Finder and Defined Adjacent Cell measurements arenot activated. However, these measurements are started when needed.Note that these measurements have to be enabled in BSCs before theycan be started.



Measurements can be run for a long period, that is, several hours, and areprocessed in the BSC at the end of the period. This reduces the amount ofdata to be transferred to NetAct and as a result, reduces the system load.

Increasing the number of BCCHs in the BA list to include all possibleBCCHs instead of only the number of current adjacencies increases theload in the network during the measurement period. However, this is not aremarkable increase and does not cause detectable decrease inperformance.

Nokia Siemens Networks NetAct contains advanced functionality foranalyzing the load caused by the measurements. The Capacity IndicationTool can be used to accurately determine the load of the existingmeasurements in the network. By starting the measurements required byOptimizer in a small network area such as one BSC, it is possible toreceive information on the additional network load.

6.2.3 Measurement period

The measurements must be scheduled for a few hours on several daysbecause Optimizer requires measurements from a longer period, that is,approximately one week. The measurements are sent from the BSC toReporter after each day. Running measurements for a long time causesadditional load to the network and also to the MS handover behaviour.

To identify unnecessary adjacencies, measurements can be conductedduring several days. When toggling the BCCH band and measuringreceived signals, the list of correct adjacencies can be generated bymeasuring for a few hours (from three to four hours) during a couple ofdays (from two to three days). The required time depends on the trafficprofile in the network. The supported measurement period is 24 hours.

6.3 Retrieving measurements

When collecting the interference measurements from mobile-originatedBSS measurements for interference matrix generation, and further forfrequency allocation, it is necessary to record all possible interferingsignals and identify the interfering cells.




6.3.1 External and foreign interferers

Optimizer is a part of regional NetAct and can thus, by default, combinethe measurements and configuration data of any network elementmanaged by that NetAct. Interference outside the cluster is referred to asforeign interference, in which case the interferers are known. However,sometimes BTSs in the optimization scope area are interfered by BTSsmanaged in another NetAct, another vendor OMC, or even by BTSs ofanother operator. In this case, the interferers are not known and theinterference is referred to as external interference. Although it is notpossible to optimise frequency allocation for those BTS, the interferencethat they cause is taken into account in the creation of an interferencematrix.

6.4 Predictions

Predictions are used to complement measured data when interferencedata is not available for interference matrix creation. Such cases includeinitial frequency planning for cells that are not yet in operation in thenetwork and giving a plausible interference value for detected blind spots.Predicted data can be scaled according to measured results.

Predictions for interference matrix are made based on distance, antennadirection, and simple link loss calculation. Optimizer’s simple link losscalculation does not take topographic or morphographic data into accountand therefore, the calculation is fast. Predictions are indicative but toachieve reliable results, they should not be used alone but always incombination with measurements.

6.4.1 Basic assumptions behind simple link loss calculations

The basic assumptions behind the simple link loss calculations are thefollowing:

. Antennas have approximately the same gain

. BTSs have the same BCCH power (this may not affect interferenceto a great extent as the site density defines the radius of the cells)

. Nearly homogenous cell distribution

. Antennas have the same height



. Nearly the same cable losses

. City environment (propagation factor 4; manual adjustment may beneeded near the water, for instance)

. All cells are sectorized or BTSs mounted on the outer wall of thebuilding

. Indoor cells are not calculated

. Antennas can be on different edges of the building




7 WCDMA interference matrix generation

The Interference Matrix is provided for visualization and further analysis. InWCDMA it is essential to distinguish between necessary neighbors andovershooting interferers. With Optimizer visualization methods theovershooting cells can be easily detected. It is essential to identify andunderstand the interference location, severity and root cause in thenetwork before selecting the corrective actions, as frequency re-planningin WCDMA is not an option. Instead there are basic methods to reduceinterference from overshooting cells or long distance adjacencies; theyinclude changes in antenna height, antenna type (beamwidth, gain),antenna downtilt, and primary CPICH power tuning. Optimizer providesmeans to identify these cases. It combines the measured interference withthe actual network topology and presents all this for efficient visualanalysis.

In Optimizer, Interference Matrix is created from the mobile measurementreports (MMR) that have been collected from a live network and stored inthe PM database. Interference Matrix provides interference data forvisualization and interference analyzer. A WCDMA Interference Matrixrepresents the interference relations between cells. It is expressed withEc/No and RSCP values.

For information on interference matrix generation, see section Creating anInterference Matrix for WCDMA in Optimising a Network Using Optimizer.For detailed instructions, see Creating an Interference Matrix for WCDMAin Optimizer Help.



WCDMA interference matrix generation

8 Measurement-based automatedadjacency optimization

Measurement-based adjacency optimization uses handovermeasurements collected by BSCs and RNCs. By analyzing the reportsgenerated based on the measurements, the unused adjacent cells can beidentified and removed from the adjacency list.

You can run several sessions of optimization, visualize and compare theresults, and select the desired optimization results to be saved. Runningseveral sessions provides better control over the adjacency optimizationprocess.

Mobiles measure the whole BCCH segment of the frequency band andreport the received power levels of the serving and surrounding cells.Based on this, promising cells are added to the adjacency list of each cell.The new adjacency plan can be visualized and modified.

Note that if the common BCCH feature is on, there can be only 31frequencies in the adjacent cell and BA list, and the maximum adjacencylist length for ADCE needs to be 31.

WCDMA adjacencies are rotated to get measurements for each adjacencycandidate. Rotation is only needed if a lot of candidates are to be testedper cell. Rotation can be omitted by using DSR in the case of ADJS.Rotation is not needed if adjacencies are only deleted. For moreinformation, see section 8.3 WCDMA adjacency KPI retrieval andoptimization. ADJS type adjacencies can be created using Detected SetReport measurements.

8.1 Measurements related to automated optimization

Adjacency optimization is based on the following measurements:



Measurement-based automated adjacency optimization

. GSM interference measurements: Channel Finder measurementand Defined Adjacent Cell measurement

. ADCE KPIs: Handover Adjacent Cell measurement. For a list of theKPIs, see ADCE KPIs.

. ADJG KPIs. For a list of the KPIs, see ADJG KPIs.

. ADJS KPIs. For a list of the KPIs, see ADJS KPIs.

. ADJD KPIs. For a list of the KPIs, see ADJD KPIs

. ADJI KPIs. For a list of the KPIs, see ADJI KPIs

Note

The ADJG and ADJS measurement collection should be aligned withprovisioned rotations.

For more information, see sections Optimizing adjacencies automaticallyand Provisioning rotation plans in Optimising a Network Using Optimizer.

8.1.1 GSM interference data

For Nokia, the interference data for GSM adjacency creation is receivedfrom an interference matrix that is based on the following measurements:

. Channel Finder measurement, S9

. Defined Adjacent Cell measurement, S10

For Siemens the measurement data is available in binary file. For othervendors measurements such as Cell name, Interferer ARFCN andInterferer BSIC are available in CSV file.

For more information, see 6 GSM interference matrix generation.

8.1.2 Detected Set Reporting

For ADJS creation, information from the Detected Set Reportingfunctionality can be used. For more information, see Creating ADJSadjacencies based on Detected Set Reports in Optimising a NetworkUsing Optimizer.



8.2 Adjacency-optimization-related KPIs

The adjacency-optimization-related KPIs are presented in the followingtables. See also Appendix 1 Supported KPIs.

Table 3. ADCE-related KPIs

Parameter Description

HO Attempts to ADCE The number of handover attempts per adjacency. Can be displayed on Mapor in Browser.

Sum of HO Attempts [N] The sum of HO Attempts over actual, updated, and deleted adjacencies in acell (number).

Remaining HO Attempts [%] 100*(The sum of HO Attempts over actual and updated adjacencies in cell)/ (the sum of handover attempts over actual, updated, and deletedadjacencies in a cell) (in percentages).

HO Success to ADCE The number of handover successes per adjacency. Can be displayed onMap or in Browser.

HO Success Ratio to ADCE The handover success rate per adjacency. Can be displayed on Map or inBrowser.

Co-channel Average ReceivedPower

Co-channel Average Received Power is derived from Channel Findermeasurement and Defined Adjacent Cell measurement for all cells exceptfor blind spot cells.

Co-channel Average ReceivedPower Weighted

Co-channel Average Received Power Weighted * Co-channel AverageReceived Power. (0..63 RXLEV.) This is not a measured KPI but calculatedby the Adjacency Optimization tool. Not displayed on Map but used by thetool internally. GSM Adjacencies can be weighted to avoid giving too muchpreference to bigger cells (macro cells).

FEP Frame Erasure Probability

CIP Carrier over Interferer Probability

ADJG-related KPIs are presented in the following table:

Table 4. ADJG-related KPIs


ISHO Attempt Rate The number of handover attempts per adjacency per hour. Can bedisplayed on Map or in Browser.

Sum of ISHO Attempt Rates [N/h]

100*(The sum of ISHO Attempt Rate over actual and updated adjacenciesin cell) / (The sum of ISHO Attempt Rate over actual, updated, and deletedadjacencies in a cell) (in percentages).

ISHO Attempts [N] The number of attempts per adjacency.




Table 4. ADJG-related KPIs (cont.)


ISHO Share The relative amount of handovers a particular adjacency at one cell hascompared to all the sum of handovers of all adjacencies at that cell. This isnot a measured KPI but calculated by Optimizer. Can be displayed on Mapor in Browser.

ISHO Success Ratio [%] The handover success ratio per adjacency. Can be displayed on Map or inBrowser.

Received Signal StrengthIndicator (RSSI)

The average Received Signal Strength Indicator for an identified target cell.

BSIC Verification Time The time in milliseconds that is needed to verify the BSIC codes for thetarget cells.

Fitness value Not a measured KPI but calculated from several KPIs to indicate how goodan adjacency is. Can be displayed in the Adjacency Optimization tool view.Fitness is not used as a criterion or threshold for deletion or creation, but isused to determine the order (in case not all adjacencies can be created ordeleted).

Note that some of the ADJGs may have a full set of KPIs (HO share, HOsuccess, RSSI (dBm) and BSIC verification time) and others may haveonly the RSSI (dBm) KPI. The ISHO (GSM) measurements are reportedperiodically. If HO does still not happen, the RSSI (dBm) values areretrieved but no HO statistics can be collected.

The ADJS-related KPIs are presented in the following table:

Table 5. ADJS-related KPIs


SHO Attempt Rate The number of handover attempts per adjacency per hour. Can bedisplayed on Map or in Browser.

Sum of SHO Attempt Rates [N/h] The sum of Soft Handover Attempt Rate over actual, updated, and deletedadjacencies in a cell (number per hour).

SHO Attempts [N] The number of Soft Handover attempts per adjacency during measurementtime

SHO Share [%] The relative amount of handovers a particular adjacency at one cell hascompared to all the sum of handovers of all adjacencies at that cell. This isnot a measured KPI but calculated by Optimizer. Can be displayed on Mapor in Browser.

SHO Success Ratio The handover success ratio per adjacency. Can be displayed on Map or inBrowser.

Ec/No [dB] The average Ec/No of the reported WCEL



Table 5. ADJS-related KPIs (cont.)


Fitness value Not a measured KPI but calculated from several KPIs to indicate how goodan adjacency is. Can be displayed in the Adjacency Optimization tool view.

Number of detected reports Number of Detected Set Reports

RSCP Received Signal Code Power

Note that in soft handover (SHO) a user equipment (UE) receives acombined neighbor cell list from all cells in its current active set. As HOstatistics are updated in all the cells the UE has a connection to (all activeset cells), also handover measurement reports can be included into thesource cell statistics of source cells that have no adjacency relation to atarget cell entering the SHO. For example, a bidirectional adjacency isdefined between Cell 1 and 2 as well as between Cell 2 and 3 but notbetween Cell 1 and 3. When the UE is in SHO to Cell 1 and 2, its combinedneighbor cell list may be composed of cells 1, 2, and 3. If Cell 3 is enteringthe SHO, both Cell 1 and 2 record, for example, an HO attempt. At thesame time the counter for the adjacency between Cell 2 and 3 is updatedand, even though there is no adjacency between Cell1 and 3, the countersfor this cell pair is updated in this case.

The ADJI-related KPIs are presented in the following table.

Table 6. ADJI-related KPIs


IFHO Attempts [N] The number of attempts per adjacency. Can be displayed on Map or inBrowser.

IFHO Success Ratio [%] The handover success ratio per adjacency.

Fitness Thresholds Sets threshold values.

IFHO Attempt Rate Threshold for adjacency deletion based on the IFHO Attempt Rate to ADJI(number per hour).

IFHO Share Threshold for adjacency deletion based on the IFHO Share (inpercentages).

Note: for tables ADJG-related KPIs and ADJS-related KPIs: for KPIs (I)SHO Attempts or (I)SHO Success Ratio there are two different ways to getthese KPIs: from NetAct PM Database (PM) or from the RNC, using StartWCDMA Measurements.




For adjacencies with statuses ACTUAL, MODIFIED or DELETED, whenthe adjacency optimization tool is started, first KPIs from the NetAct PMDatabase are loaded. After that, each RNC is checked and if there are noKPIs loaded from the NetAct PM Database then the KPIs from using theStart WCDMA Measurements dialog are loaded. For the creation of ADJSor ADJG, the KPIs from the RNC using Start WCDMA Measurements arealways used.

8.2.1 Fitness value

The fitness value is calculated in WCDMA adjacency optimization fromseveral KPIs and is used to organize adjacencies in order of superiority.The KPIs are weighted according to your own definitions in the FitnessThresholds tool view. For a description of the tool view, see FitnessThresholds tool view in Optimizer Help.

The following figure illustrates the cost function for fitness.

Figure 6. Cost function for fitness

In the cost function for fitness,

. w is the KPI weight

. Fitness_share (Fitness (i)) is the fitness share of the KPI. Fitnessshare is the normalized value of the KPI. The value of the KPI isscaled to the range of 0 to 1.

. Fitness is calculated using the previous cost function for fitnesswhere fitness shares are weighted according to weighting factors toget the fitness value which has the range of 0 to 1.

The following figure illustrates mapping one KPI value to the fitness value.

Fitness FitnessFitness

n21

nn2211

w...ww

*wwwFitness

+++

+...+*+=

*



Figure 7. Mapping a KPI to the fitness value

In the previous figure, Min, Bad, Good, and Max are definable thresholdsfor each KPI. If the KPI is below the minimum threshold, the fitness value is0. If the KPI is above the Max value, the fitness value is 1. Mappings ofFitness_share in points Min/0, Bad/0.2, Good/0.9, Max/1 are always thesame and cannot be modified.

The following figure illustrates an example where the fitness value iscalculated from three KPIs. The actual KPI values are:

. SHO Attempt Rate: 950 (Fitness_share: 0.975)

. SHO Success Ratio: 75% (Fitness_share: 0.783

. SHO Share: 9% (Fitness_share: 0.76)

Note that this is an example, more KPIs exist currently.

Fitness

Fitness i

KPI value

KPI

Min Bad Good Max

1.0

0.9

0.2

0.0 i




Figure 8. Example of calculating the fitness value

8.3 WCDMA adjacency KPI retrieval and optimization

To decide which existing adjacencies are good ones and which ones arenot needed, handover statistics are collected for the existing adjacencies.Furthermore, in Nokia RAN, the concept of knowing beforehand whichadjacencies are missing does not exist yet and therefore handoverstatistics are used for finding new good adjacencies. Candidateadjacencies need to be provisioned to the network before handoverstatistics can be collected for them. For this reason, Optimizer can makerotation plans for testing adjacencies in the network. Each rotation plancan be visualized and modified. Furthermore, the final list can also bevisualized and modified.

RNC statistics

RNC reports counters and Optimizer uses them partly (for RAS06) usingthe Start WCDMA Measurements dialog. For RU10 Optimizer uses onlyNetAct KPIs.

Starting and retrieving measurements

WCDMA KPI(s) can be retrieved in two ways, depending on the RNCversion: either by using measurements which are started in Optimizer fromthe Start WCDMA Measurements dialog (for RAS06 elements), or byretrieving measurements from the NetAct PM database (for RU10).

Measurements which are started from the Start WCDMA Measurementsdialog are used only for RAS06 elements. As part of the measurement,the KPI value corresponding to a valid ADJS cell pair is stored in one KPIset, and the KPI value corresponding to the undefined adjacency cell pairis stored in another KPI set. For example, in the case of the SHO attemptsKPI, one KPI set corresponds to the SHO Attempts KPI of the adjacencytype ADJS and another KPI set to the SHO Attempts KPI of the adjacencytype ADJD.



Note that to start WCDMA measurements, you either need to have theNetwork Administrator role or the permission operationRUN_RNC_MEASUREMENTS included in the role assigned to you. For moreinformation and instructions on starting the measurements, see StartingWCDMA adjacency measurements and Start WCDMA Measurementsdialog in Optimizer Help.

To check the status of the measurements, open the WCDMAMeasurements tool view by selecting Tools → Network Statistics →View Measurement Status. In the RNC Monitoring Status dialog, you canalso check the current status of the log buffer (buffer filled in percentages)and the estimated time left in minutes until the buffer becomes full. Formore information, see RNC Monitoring Status dialog in Optimizer Help.

In the Key Performance Indicators tool view, you can check if there are KPIstatistics and whether statistics are available for all network elements(shown in the Coverage column of the view). The retrieved measurementsare inserted into the Optimizer database as WCDMA adjacency KPIs.

When retrieving measurements from the NetAct PM database, the ADJSKPIs SHO Attempt Rate and SHO Share are retrieved for RU10 elements,whereas the ADJS KPIs SHO Attempts and SHO Success Ratio areretrieved for both RU10 and RAS06 elements. The retrieved KPI setcontains KPI values only for valid ADJS cell pairs and is used by theAdjacency Optimization tool in the deletion of ADJS adjacencies. TheADJD KPIs SHO Attempt Rate, SHO Share, Ec/No, RSCP and Number ofReports are retrieved for RU10 elements, whereas the ADJD KPIs SHOAttempts and SHO Success Ratio are retrieved for both RU10 and RAS06elements. The retrieved KPI set contains KPI values only for valid ADJDcell pairs and undefined adjacency cell pairs.

Rotating adjacencies and creating the final list

WCDMA adjacency optimization consists of the following phases:

. Selecting a list of existing adjacencies that are good enough and arenot deleted (basic list, BL)

. Creating a list of potentially good adjacencies (candidate pool, P)

. Measuring their performance in live network

. Selecting the best adjacencies to be kept in the network

You can control the rotation process, that is, the number of rotation roundsand the amount of adjacency candidates in each rotation round. Inaddition, the maximum number of adjacency candidates can be controlled.Note that Optimizer may not create candidates if the adjacency lists are




already full or if the maximum numbers are exceeded. During eachrotation, a part of the adjacencies from the candidate pool are placed intothe rotation. For example, on day one, the adjacencies in the basic list andthe candidate pool number one are measured (rotation one). On day two,the adjacencies in the basic list and the candidate pool number two aremeasured (rotation two). Finally, on day five, adjacencies in the basic listand the candidate pool number five are measured (rotation slot five).

Figure 9. Basic List and Rotation slots

The duration of one rotation is one day. There can be severalmeasurement times per day. To get hourly variations, the measurementtimes can be different for each day, that is, rotation. The summarizationlevel of the measurements is Daily, and therefore each rotation producesone KPI set that has KPIs for adjacencies that were actuals during thatday. In the previous example, five KPI sets are produced.

Based on the fitness of the rotated adjacencies, the best adjacencies areincluded in the final optimized adjacency list. The final list consists of thebest adjacencies in the basic list and the rotation pool. To compare all themeasured adjacencies, one KPI set that contains KPIs for all of theseadjacencies is needed. This KPI list is produced by merging the sets fromeach rotation period into one bigger set.

As the optimization case can consist of any number of rotations, none ofthe default summarization levels can be used for this set. Therefore, thecustom summarization level is used. When you select this summarizationlevel, you have access to all the KPIs of all the adjacencies measuredduring the optimization case (also to the KPIs of the adjacencies that arenot actual adjacencies but were or are candidates). You can also use thisset to visualize all measured adjacencies on Map to compare themmanually. If the traffic is in the network is low, the coverage may not bevery high after one day or rotations. Therefore, measurements should becontinued until the coverage does not improve substantially when the KPIshave been combined.

In the following figure, one measurement set scheduled for the entirerotation period is created and named (Custom Measurement). In theOptimizer main toolbar, this measurement set is selected as thesummarization level.



Figure 10. Summarization level and measurement set

For more detailed instructions on creating the final list, see Rotation ofADJS and ADJG adjacencies in Optimising a Network Using Optimizer.




9 Automated frequency planning

The Frequency Optimization algorithm creates a new frequency planbased on the interference information from interference matrix.Interference can be presented as CIP (Carrier to Interference Probability),FEP (Frame Erasure Probability), or ARP (Average Received Power).DAC (Defined Adjacent Cell) and CF (Channel Finder) measurements areused for CIP and Total FEP measurement for FEP. For more informationon interference matrix, see chapter 6 GSM interference matrix generation.

When a new frequency plan has been created, you can visualize theresults and implement or schedule the implementation of the newfrequency plan to the network. The interference matrix can also be copiedand used with a preferred external automated frequency planning (AFP)tool.

Frequency Optimization can be used to a target area of any size, rangingfrom allocating frequencies to single cells to allocating frequencies to allthe cells in a NetAct cluster.

The focus of the frequency allocation or optimization can be altered withdifferent interference data scaling and weighting factors. Parameters canbe assigned to a TRX layer specifically, for example, BCCH channels canhave stricter constraints than other channels.

Optimizer supports frequency optimization in hopping and non-hoppingnetworks, and in hopping networks both BB and RF (synthesized) hoppingis supported. For more information and instructions on ad hoc allocation,see Performing ad hoc allocation in Optimising a Network Using Optimizer.

For a an overview of the procedure, see chapter Creating a frequency planin Optimising a Network Using Optimizer. For detailed instructions, seeFrequency Allocation Help.

Optimizer has three allocation methods: Fast, Optimization, and Accuratemethod. In BSIC allocation, only the Fast and Accurate methods are used.



Automated frequency planning

Fast method

The Fast method uses the Stochastic Greedy algorithm and randomstarting point to optimization. The Fast method produces a reasonablygood allocation quickly by finding a local minimum in one optimizationloop. It is useful for ensuring that the defined parameters are appropriatebefore carrying out the accurate allocation. The Fast method is alsoconvenient when only a few missing frequencies need to be allocatedwithout changing the rest of the allocation.

Optimization method

The Optimization method also uses the Stochastic Greedy algorithm butstarts from the existing allocation and can only change frequencies if theresulting network is better than before.

Accurate method

The Accurate method uses Simulated Annealing algorithm and starts fromthe random allocation. The Accurate method is more time consuming andshould be used for the actual allocation that is implemented to the network.The accurate method produces allocations close to the most optimal onewithin a reasonable amount of time.

The accurate allocation works so that the more time is given, the better theallocation. The default time is calculated based on the number of the itemsto be allocated and it equals the number of TRXs if no RF-hopping is used.If RF-hopping is used, it equals to the number of frequencies in all MA liststo be allocated.

9.1 Allocation scopes

Frequencies can be allocated to the whole network, for a part of thenetwork (one BSC area, for example) or only for missing frequencies.Initial channel allocation information provided by the networkmeasurement data can be used as a basis for optimization.

If allocation parameters have been changed, the first allocation can bemade by running the fast allocation algorithm to ensure that the definedparameters are appropriate. In other words, you need to check that thereare enough channels and that the quality requirements are not too tight orthat the separations are not broken.



In Accurate allocation, the more time is given, the better the allocation. Asa general recommendation, it is better to run a long allocation once than torun several short allocations. Therefore, if the plan is big, it may be best tolet the allocation run overnight. If the network is reasonably small, it maybe better to let the algorithm run for a shorter period of time.

BCCH and TCH channels are usually separated into their own bandsegments by using frequency groups. Often the BCCH allocation staysconstant much longer than the TCH allocation. Therefore, we recommendallocating the BCCH channels before TCH channels.

9.1.1 Allocating frequencies for a part of the network

If you are reallocating frequencies only for a part of the network, select onlythe cells to be allocated as the target. The Frequency Optimization toolautomatically finds all the surrounding cells that affect these cells. Theallocation status to these target cells is set on and to other cells off in thetarget BTSs.

9.1.2 Allocating missing frequencies

When the network is expanded and new cells and TRXs are added, it isnecessary to allocate frequencies for these cells. To do this, select theAllocate only planned objects option in the Analysis tab.

If there are only a few frequencies to be allocated, we prefer fast allocationto accurate allocation.

9.2 Frequency optimization cases

Frequency optimization cases can be divided into the following categories:

. Full allocation, when the whole frequency plan is allocated again.For more information, see section 9.2.1 Full allocation.. Optimization, when a relatively good allocation exists and only

some tuning (minimal changes) may be needed.. New allocation, where all cells in the target area get new

frequencies

. Allocation keeping suggested channels, when a few new TRXs areadded and only these new objects require allocation. For moreinformation, see section 9.2.2 Allocating planned objects only.




9.2.1 Full allocation

In the initialization phase of full allocation, the algorithm tries to find anallocation fulfilling all separation constraints. If this is not possible, thealgorithm tries to keep the most important separation constraints andviolate only the less important ones. There are several separationconstraint classes, each of which can have a different priority or cost. Thealgorithm used is a constructive stochastic greedy algorithm, whichorganizes the TRXs according to the required separation constraints.Initialization phase produces an allocation using the lowest availablechannels. Therefore, they are used more often than the highest channels,which may cause bias to interference minimization. In an optimalallocation, the spectrum is used quite evenly.

For these reasons, in the second phase, the algorithm removes the biascaused by the initialization phase so that the spectrum is used moreevenly. This scrambling of frequencies is an iterative process changingeach TRX the channel to a random available channel within theconstraints. This process is then repeated several times.

In the final phase, the algorithm modifies the frequency plan so that theinterference is minimized while maintaining all the constraints.

There are three methods for the Full allocation optimization case: Fast,Optimization, and Accurate. The Fast and Optimization methods both usethe same Stochastic Greedy algorithm. However, the Fast method startsfrom a random point and the method Optimization starts from the currentallocation. The Stochastic Greedy algorithm produces an allocationquickly. This algorithm stops to the first found local minimum but it can beused to get a rough idea of the quality of the allocation. The Fast algorithmis very useful when only a few missing frequencies need to be allocated.This way, possible parameter and other errors can be found and correctedas early as possible. This algorithm also gives a good reference point forthe accurate algorithm which should always produce clearly betterallocations. For more information, see 9.1 Fast method.

The method Optimization requires an existing allocation that is kept as astarting point for optimization. If the allocation is already in a localminimum, the Fast algorithm cannot find any improvement whereas theAccurate algorithm is able to escape from the local minimum if a betterminimum exists. For more information, see 9.1 Optimization method.



The Accurate method is a simulated-annealing-based algorithm that canescape from the local minima while it is going towards the global minimum.Parameters define the time used by this algorithm, and the more time it isgiven, the better the allocation. The algorithm produces the best possibleallocation within a given time. Allocation is closer to the global minimumthe more time it is given. For more information, see 9.1 Accurate method.

All three algorithms are stochastic. They may give somewhat differentallocations each time, even when the allocation problem remains thesame. Standard deviation of the results is relatively big for the Fastalgorithm but small for the Accurate algorithm and becomes even smaller ifthe available time is increased.

9.2.2 Allocating planned objects only

In the initial phase of allocating only new planned objects, the goal is tokeep the channels that have already been assigned and give the lowestpossible channels to the TRXs missing allocation. If a channel that fulfilsthe constraints is not found, a random channel is given. In the secondphase, scrambling is made only for the planned TRXs.

In the final phase, the algorithm modifies the frequency plan so that theinterference is minimized while maintaining all the constrains in the sameway as described in section Allocation.

9.3 Structure of the allocation algorithms

The frequency optimization algorithms contain the following parts:

. Algorithm Logic selects according to certain rules which TRX is to bechanged next. For more information, see section 9.3.1 AlgorithmLogic.

. Channel Assignment assigns a new channel to the selected TRX.For more information, see section 9.3.2 Channel Assignment.

. Cost Function Calculation calculates how “good” the allocation is,after which the Algorithm Logic part makes the decision whether toaccept the change or not. For more information, see section 9.3.3Cost Function Calculation.




9.3.1 Algorithm Logic

Each algorithm has its own Algorithm Logic to select the next TRX to bechanged. In the initial phase, the algorithm orders TRXs according toseparation requirements. In the final phase, the accurate algorithmrandomly selects the next TRX, and the fast algorithm randomly selectsthe next TRX from a set of TRXs.

9.3.2 Channel Assignment

When a TRX has been selected, the algorithm asks Channel Assignmentto assign the channel. This channel can be the lowest available, randomlyselected, or the best of all the available channels, depending on the type ofalgorithm. When Channel Assignment selects the channel, it has to findthe legal channels fulfilling all separation constraints. There can beforbidden frequencies for certain cells and different TRXs can have inoverall a different set of allowed channels. Also, the set of allowedchannels varies depending on the current allocation.

9.3.3 Cost Function Calculation

When the new channel has been assigned, the Cost Function Calculationpart calculates the cost value for the changed allocation. This value tellshow “good” or “bad” the allocation is. The smaller the value, the better theallocation. It is possible to scale the interference value, and different TRXscan have different scales. In general, it is possible to scale co-channel andadjacent channel interference, and interference coming to and from theBCCH. In addition, different separation violations can have differentpenalties. The following separation cases are classified: co-site, co-cell,adjacent cell, C/lc level, C/la level, and edited separations, It is alsopossible to give a penalty for using other than a suggested channel.Scaling interference upwards reduces that particular interference in thefinal allocation when the corresponding optimization goal is used. Formore information on the interference scales and optimization goals, seeFrequency Allocation Help.

When the cost value for the changed allocation is calculated, AlgorithmLogic either accepts or rejects the change and selects a new TRX for thenext loop. This is iterated until the ending criteria are fulfilled and allocationis stopped. The fast algorithm stops when no improvement can be found,which means that the allocation has reached a minimum. For the accuratealgorithm the ending criteria are somewhat more complex, because it canescape from the minima. The accurate algorithm stops when the“temperature”, which is an internal parameter of the algorithm, hasreached a certain level.



9.4 User settings to guide the algorithms

This section covers issues related to forbidden channels, frequencygroups and manual separations.

9.4.1 Forbidden channels

Optimizer supports all the GSM frequency band variations: GSM, EGSM,GSM1800, GSM1900, and GSM850. When working with FrequencyGroups in the Frequency Allocation tool, the list of channels in the selectedfrequency band is listed. However, the tool does not restrict the band-specific forbidden channels but those are also visible in the frequency list.You can check the selected channels for each frequency group so thatglobally or nationally forbidden channels are not accidentally used.

The number of available frequencies can be smaller in the border areabetween two countries compared to the operator’s whole band. In thatcase, certain frequencies can be excluded from the frequency groupsinstead of tailoring several frequency groups for the border area.

It is possible to import forbidden channels in CSV format into FrequencyOptimization using the Import Forbidden Channels dialog.

9.4.2 Passive intermodulation

Passive intermodulation can be taken into account in automated frequencyplanning. In the Start Frequency Optimization dialog, it is possible to definethat passive intermodulation is to be avoided. Intermodulation is caused bypoor antennas or otherwise faulty hardware. A third frequency is created oftwo different downlink frequencies. This third frequency interferes someuplink frequency, for example, 2*f1(DL)-f2 (DL)=f3(UL).

9.4.3 Frequency groups

The basic purpose of using frequency groups is to define the frequenciesand separation requirements for the Frequency Allocation tool. Thefrequencies and separation requirements are used in the frequencyoptimization process (when generating a separation matrix) for each TRX.Frequency group settings are user-specific and are saved with theoptimization plan. For more information and instructions, see Creating anddefining frequency groups in Frequency Allocation Help. See also seesection Creating frequency groups in Optimising a Network UsingOptimizer.




9.4.4 Manual separations

Separations can be manually defined between the cell pairs which areknown to interfere with each other, but do not show as interfering inmeasurements because of inadequate measurement data.

9.4.5 MA lists

For frequency hopping networks, it is possible to use predefined MA lists.Alternatively, the Frequency Allocation tool can create them automatically.MA lists need to be set into predefined mode if they need to be keptuntouched by Optimizer during frequency allocation. See Modifying MobileAllocation Lists (MALs) in Frequency Allocation Help for details.

9.5 BSIC planning

The Base Station Identity Code (BSIC) Planning functionality in Optimizerchecks the current BSIC allocation for conflicts and assigns again validcodes for those found invalid. BSICs (+BCCH frequency) are required bythe mobiles and network to distinguish the cell which is being measured.BCCH and BSIC combination must be unique within a certaingeographical area in the network. BSICs should always be allocated againwhen frequency plans are changed.

The BSIC allocation process uses the entire range (0-7) of Base StationColor Codes (BCCs) but only those Allowed Network Color Codes (NCCs)selected in the Start Frequency Optimization dialog.

9.6 Interpreting frequency optimization results

If co-cell or co-site separations for a layer are violated, there are either toofew frequency channels available, or the parameter values needadjustment. The separations and the fee for breaking them (violationpenalties) are set to influence each layer (BCCH, TCH, Underlayer..)separately as well as between the layers. The separations protect usersfrom creating obviously interfering frequency assignments by settingminimum rules for frequency reuse. However, unnecessary or unrealisticrules should not be set, as these will influence the capability of thealgorithm to minimize the measured interference in the network. It isadvised that the user will iteratively compromise these values, i.e. run



several iterations with different value sets and then compare the resultsuntil an optimum balance is achieved. If the parameters are correct, butviolations still exist, more channels should be assigned to keep theseseparations.

Similarly, if adjacent cell separations are broken, the reason may be thatthere are too few channels or that the adjacent cell separations have beenset incorrectly in the allocation parameters. It is also possible that there areunnecessary adjacencies, which in turn produce too many adjacent cellseparation violations. To resolve this, obsolete adjacent cells need to beremoved with the help of the Automated Adjacency Optimization (AAO)tool and the channels need to be allocated again. If there are still adjacentcell separation violations, the only possibility is to add more channels orloosen the adjacent cell separation requirements. If adjacent cellseparations are used, the violation penalty in the BCCH frequency groupshould be much bigger than in the TCH frequency group. It isrecommended to set the adjacent cell separations only for the BCCH layer.

The common adjacent cell separation may equally be applicable for theBCCH layer, if the band is large enough in comparison with the averageadjacent cell list length. This rule sets that allocation of the same BCCHchannel to two cells is penalized if they have a common adjacent cell.However, in planning cases with a dedicated BCCH band, this separationis often not used due to a large number of resulting violations. It isrecommended to set the common adjacent cell separation only for BCCHlayer.

To summarize, basically all separations act as hard constraints, as eventhe minimum penalty value (1) well exceeds the typical cell levelinterference cost. An advanced user may in some cases decide to “soften”selected cell separations by minimizing the related penalties and at thesame time scaling up significantly the co- and adjacent channelinterferences for the cost function. But nevertheless, the more and thelarger the residual violations, the less is the weight of the interferenceminimization and the higher is the residual interference level afterallocation. The Fast Allocation option as well as Violations Report (listingthe violations and causes) and Network Interference Report (providing anaverage residual interference per layer) in AFPAnalysis are the basic toolsfor finding optimum settings for each planning case. The interferencereport is also useful in balancing the co- and adjacent channel interferenceweights.

In order to keep the most important cells (highways, VIP areas, forexample) as interference free as possible, you can define priorities forcells, for example in such a way that cells that tolerate interference aredefined as low priority cells and cells that do not tolerate interference aredefined as high priority cells.




10 Primary downlink scrambling codemanagement

In WCDMA networks, it is forbidden to have the same scrambling code incells defined as neighbors and in the neighbor cells' neighbors which usethe same frequency. There is however an option to reuse scramblingcodes for cells in the same sector but with different UARFCNs.Furthermore, it is not advisable to reuse a certain scrambling code within agiven minimum reuse distance. Therefore, in Optimizer you can analyzeactual data and optimization plans for such collisions. You can thenmanually or automatically correct existing collisions and violations, ormake a completely new allocation taking into account the following:

. Frequency (UARFCN)

. Collisions in the neighboring cell and in the neighbor’s neighboringcells

Three types of collisions are possible:. Cell A - scrambling code 1

Cell B (neighbor) - scrambling code 1. Cell A - scrambling code 1

Cell B (neighbor’s neighbor) - scrambling code 1. Cell A - scrambling code 1

Cell B (neighbor) - scrambling code 2

Cell C (neighbor’s neighbor) - scrambling code 2

Due to neighbor cell list combination during SHO, up to fourlevels of neighbors are taken into account.

. Scrambling code rule violations

Optimizer checks for the following rule violations:. Reuse distance is too small. WCEL specific forbidden code is used. Global forbidden code is used. Invalid scrambling code is used



Primary downlink scrambling code management

. Adjacency direction

When allocating scrambling codes and/or correcting scramblingcode collisions, the Scrambling Code Allocation tool takes theadjacency direction into account. For example, there is an incomingadjacency from Cell A to Cell B and the cells have the samescrambling code. When the Take adjacency direction into accountoption is selected, the tool finds only one collision from Cell A to CellB. If the option is not selected, the tool finds two collisions from CellA to Cell B and from Cell B to Cell A.

. Minimum desired reuse distance

When allocating scrambling codes, Optimizer checks if thescrambling code of the cell is reused closer than the specifiedthreshold. If yes, the scrambling code of this cell is changed. Forexample, Cell A and Cell B both have scrambling code 1. Thedistance between the cells is 10 km and the minimum reuse distancethreshold is set to 12 km. When allocating scrambling codes, thealgorithm checks cell by cell whether the scrambling code should bechanged. First, Cell A is checked and the scrambling code ischanged. Next, Cell B is checked and as the scrambling code of CellA has already been changed, the scrambling code of Cell B is notchanged.

. Forbidden scrambling codes (can be defined on a WCEL-level, orglobally for the whole PLMN)

Forbidden code set is a set of scrambling codes which cannot beused by the cell when this set is assigned to the cell. For example,the forbidden codes set number 1 contains scrambling codes1,2,3,4,5, and 6. If the set is assigned to Cell A, Cell A cannot useany of these codes.

When collisions are corrected, first a list of all valid codes is created(collisions via ADJI are taken into account, but not yet ADJD). This listcontains all possible codes used by the cell’s neighbors and neighbor’sneighbors. In addition, the codes included in the forbidden scramblingcode groups (if any) are excluded from the list. Finally, the new scramblingcode is randomly picked from this list.

In the Scrambling Code Reuse Visualization dialog, you can define whichscrambling codes are visualized on Map. In addition, you can select thefrequency (UARFCN). On Map, all cells which have a different frequencyare displayed in grey. Cells which have the same frequency andscrambling code are displayed in red. Cells which have the same



frequency and belong to the same scrambling code group are displayed inyellow. Cells which have the same frequency and belong to differentscrambling code groups are displayed in blue. Cells which have a differentfrequency are displayed in grey (if the frequency is activated).

You can also view scrambling code collision paths and colliding cells onMap. For details, see Visualizing scrambling code collision paths andcolliding cells on Map in Optimizer Help.

For more information, see Managing primary downlink scrambling codes inOptimising a Network Using Optimizer. For instructions, see Checking andcorrecting scrambling code collisions, Checking and correcting scramblingcode violations, and Optimizing scrambling code allocation in OptimizerHelp.



Primary downlink scrambling code management

11 Dominance areas in visualization

Cell dominance area information provides an informative overview of thenetwork situation. For example, when using the actual cell configuration(antenna data, TX power, HO settings) for building dominance maps andmeasured traffic distribution (cell loading per service) display, it is easier tounderstand adjacency relations and interference conditions. Furthermore,it is possible to show any measured KPI information together with celldominance areas and parameters for effective analysis of the reasons forperformance of cells.

Dominance visualization in Optimizer is done using a Voronoi graphalgorithm and with the simplified assumption that all cells have the samepower and antenna parameters besides azimuth. Hence the dominancearea consists of locations that are closest to a certain cell.

Note that calculations are made for visualization purposes only and are notused by optimization algorithms. Calculations do not use map data. Theidea of calculations is to give a rough visual background for displayingaccurate measurement data. For related use cases, see AppendixOptimization cases in Optimising a Network Using Optimizer.

Calculations take into account the following parameters:

. Antenna direction

. Maximum cell coverage radius

11.1 Calculation area

Dominance is calculated for the visible area on Map, plus a margin to theleft, right, below, and above. In addition, cells within a buffer zone aroundthis area are included in the calculation.



Dominance areas in visualization

12 Multi-PLMN support in Optimizer

Optimizer supports the optimization and visualization of multiple PLMNs.Each cluster can be viewed and grouped in Navigator and Browser. All theoptimization tools can be used in the same way as when working with asingle or local cluster. The local cluster is named PLMN-PLMN. Theoptimization results are saved from Optimizer DB to Configurator DB as aplan and exported from Configurator DB to other management systemusing the existing interfaces.



Multi-PLMN support in Optimizer

13 Multi-vendor support in Optimizer

Multi-vendor (MV) support in Optimizer allows the user to visualize andmodify foreign vendor Network Elements (NE). These foreign NEs aretreated as normal elements and can be used with all tools, though somerestrictions apply. Optimizer can only read Configuration Management(CM) data from the Configurator CM database. Before Multi-vendor CMdata can be used in Optimizer, it has to be available in the Configurator CMdatabase.

A separate adaptation project is needed to import MV CM data into theConfigurator CM database from another Network Management System(NMS). A network-wide CM environment is created by importing externalNE data from foreign NMSs. The import is done using XML files which areprepared during the adaptation project.

13.1 Multi-vendor data

External regions’ data is read into Optimizer automatically using normalsynchronization process between the Configurator CM database and theOptimizer database.

Configuration Management data

Configuration Management data is copied from the Configurator CMdatabase to the Optimizer database using the existing Optimizer datamodel and hierarchy. External Network Elements are visualized andhandled exactly like local network elements. Both parameters and KPIsare mapped to existing Optimizer object parameters and KPIs. A new CMparameter, vendor, becomes visible in all cells and controllers inOptimizer. This makes it possible to separate one vendor’s NEs fromothers.



Multi-vendor support in Optimizer

Performance Management data

Normally Optimizer reads KPI data from the NetAct PerformanceManagement database. With external NEs this is not possible. Optimizerincludes a feature to import KPIs from a file. The data file must be in theComma Separated Values (CSV) format. Both automatic and manualimport is possible. Automatic import will read the CSV file from a user-specifed location in the Linux Application Server (LinAS). Manual import isconfigured and started from the Optimizer user interface. KPI import canalso be used for local region NEs.

13.2 Multi-vendor visualization

External and non-local network elements are visualized in the same wayas local Nokia NEs.

Navigator

In the Navigator, the external and non-local controllers are displayed usingthe same tree structure as the local controllers. By default, the vendorname is indicated in the label of the controllers and cells. The top-level ofthe Hardware Topology view groups the regions by cluster, but this can bechanged in the preferences (User Interface > Enable Cluster Level).

Map

On the Map, the user can use a different color for each vendor. A tool tipdisplays the cell label, indicating the vendor when the pointer is placedover a cell icon. The legend can be set by the user.

Browser

In the Browser, foreign and non-local NEs are displayed in the same wayas local Nokia NEs. For foreign NEs, only the most important parametershave values, however. The rest of the parameters show empty values. Thevendor name can be displayed in the Browser. There are also defaultBrowser profiles for external NEs, in order to make it easier to see onlyrelevant parameters.



13.3 Multi vendor GSM Interference Matrix Creation

An Interference Matrix (IM) can be created using measurement data fromthe PM database for Nokia NEs and from binary files for Siemens NEs.The multi vendor functionality helps the user to create the IM setindependent of vendors by importing the CSV file. During importing IM setis created under the selected BSCs. Therefore, GSM IM Creationfunctionality is available for all the vendors. An Interference Matrix that hasbeen created elsewhere can also be imported to an external or non-localcontroller as a CSV file, where cells are identified by Cell ID and LocationArea Code (LAC). For more information on creating GSM IM refer toCreating an interference matrix for GSM in Optimizer Help.

13.4 Multi-vendor restrictions

Since external network elements do not have all the parameters that thelocal NEs have, some Optimizer features and tools are not available whenthe scope includes these foreign objects.

Instant Adjacency Provisioning

Adjacencies of foreign vendor cells or external cells cannot be provisionedinstantly since no direct network connection exists to these NEs. If instantadjacency is started, the foreign vendor adjacencies are skipped. Detailsof the operation can be found from the Task Management tool view.

Frequency Optimization

The Automated FP tool can be used to allocate BCCH frequencies andBSIC codes also to external cells.

WCDMA Measurements

WCDMA measurements can only be started for local Nokia RNCs. Notethat if WCDMA measurement KPIs are imported to the Optimizerdatabase, then a WCDMA Interference Matrix can be created for externalor non-local RNCs.

Automated Adjacency Creation

The rotation process for creating WCDMA and inter-system adjacencies isnot valid for external or non-local adjacency creation.



Multi-vendor support in Optimizer

14 Where to find more informationOptimizer documentation

. For information on the process of optimizing a network usingOptimizer, see Optimising a Network Using Optimizer.

. For an overview of the functionality changes between Optimizerreleases, see Functionality Changes in Optimizer.

. For detailed technical information on Optimizer, see OptimizerTechnical Reference Guide.

. For information on Optimizer database tables, see DatabaseDescription for Optimizer.

. For detailed instructions on how to use the Optimizer applications,see the following helps:. Optimizer Help. Frequency Allocation Help. Antenna Data Editor Help

Geographic Information System documentation

. For information on the Geographic Information System, see thefollowing documents:. Geographic Information System Principles. Map Administrator Help

NetAct Configurator documentation

. For information on the NetAct Configurator, see the followingdocuments:. NetAct Configurator Principles. NetAct Configurator Technical Reference Guide



Where to find more information

Appendix A Supported KPIs

This appendix lists the supported KPIs.

A.1 ADCE KPIs

. HO Attempts to ADCE [N]

. HO Success Ratio [%]

. HO Success to ADCE [N]

A.2 ADJG KPIs

Mentioned KPIs are available from RNC, but from RAS05.1 onwards.ADJG ISHO attempts and ISHO success ratio is available from NetActusing Autodef measurements for RAS06 and earlier version. For RU10 allthe KPIs are available from NetAct using Autodef measurements.

. BSIC Verification Time [ms]

. ISHO Attempt Rate [N/h]

. ISHO Attempt [N]

. ISHO Share [%]

. ISHO Success Ratio [%]

. Received Signal Strength Indicator (dBm)

A.3 ADJS KPIs

Starting from RU10 all KPIs are available from NetAct using Autodefmeasurements. For releases older than RU10 all KPIs are available via theStart WCDMA Measurements dialog but only SHO attempts and SHOsuccess ratio are available from NetAct using Autodef measurement. Formore information, see Starting and retrieving measurements andManaging measurement data in Optimizing a Network using Optimizer.

. SHO Attempt Rate [N/h]

. SHO Attempts [N]

. SHO Share [%]



Supported KPIs

. SHO Success Ratio [%]

. Ec/No [dB]

. Number of detected reports [N]

. RSCP [dBm]

A.4 ADJD KPIs

Mentioned KPIs are available from RU10 onwards. The following KPIs areavailable from NetAct using Autodef measurements.

. SHO Attempt Rate [N/h]

. SHO Attempts [N]

. SHO Share [%]

. SHO Success Ratio [%]

. Ec/No [dB]

. Number of detected reports [N]

. RSCP [dBm]

A.5 ADJI KPIs

IFHO Attempts and IFHO Success Ratio KPIs are available from NetActusing Autodef measurements and only from RAS05.1 onward. For earlierversions, these KPIs cannot be retrieved from NetAct nor from RNC. ForRU10, all KPIs are available from NetAct using Autodef measurements.

. IFHO Attempts [N]

. IFHO Attempt Rate

. IFHO Success Ratio

. IFHO Share

A.6 BTS KPIs

. Additional GPRS channel use [TSL]

. Average CS traffic per BTS (trf_97) [Erlang]



. Average DL TBF per timeslot (TBF/TSL) (S10) [N]

. Average DL TBF per timeslot (TBF/TSL) (S11.5) [N]

. Average PS territory (Number of TSLs Available for PS traffic onnormal TRX) [TSL]

. Average PS traffic per BTS including CS 3 and 4 [Erlang]

. BTS CS Data Traffic [Erl]

. BTS CS Traffic [Erl]

. BTS DL Cumulative Quality in Class 4 V2 (dlq_2a) [%]

. BTS DL Cumulative Quality in Class 5 V2 (dlq_2a) [%]

. BTS Incoming HO Success (hsr_18) [%]

. BTS Outgoing HO Success (hsr_19) [%]

. BTS SDCCH Blocking (blck_5a) [%]

. BTS SDCCH Congestion Time (cngt_2) [sec]

. BTS SDCCH Congestion [%]

. BTS SDCCH Drop Ratio (sdr_1a) [%]

. BTS SDCCH TCH Setup Success (cssr_2) [%]

. BTS TCH Blocking (blck_8d) [%]

. BTS TCH Drop Out Before Call Re-establishment (dcr_4f) [%]

. BTS Total HO Failure (hfr_1) [%]

. BTS Traffic Share [%]

. BTS UL Cumulative Quality in Class 4 V2 (ulq_2a) [%]

. BTS UL Cumulative Quality in Class 5 V2 (ulq_2a) [%]

. PS territory utilization [%]

. TCH congestion time [%]

. Territory downgrade rejection rate due to streaming class usage [%]

. Territory upgrade rejection rate due to CSW traffic [%]

. Territory upgrade rejection rate due to lack of PCU capacity [%]



Supported KPIs

A.7 Cell KPIs

. Cell CS Data Traffic [Erl]

. Cell CS Traffic [Erl]

. Cell DL Cumulative Quality in Class 4 V2 (dlq_2a) [%]

. Cell DL Cumulative Quality in Class 5 V2 (dlq_2a) [%]

. Cell Outgoing HO Success (hsr_19) [%]

. Cell SDCCH Blocking (blck_5a) [%]

. Cell SDCCH Congestion [%]

. Cell SDCCH Congestion Time (cngt_2) [sec]

. Cell SDCCH Drop Ratio (sdr_1a) [%]

. SDCCH TCH Setup Success (cssr_2) [%]

. Cell TCH Blocking (blck_8d) [%]

. Cell TCH Drop Out Before Call Re-establishment (dcr_4f) [%]

. Cell Total HO Failure (hfr_1) [%]

. Cell Traffic Share [%]

. Cell UL Cumulative Quality in Class 4 V2 (ulq_2a) [%]

. Cell UL Cumulative Quality in Class 5 V2 (ulq_2a) [%]

. Cell Incoming HO Success (hsr_18) [%]

. Timing Advance Max Calls [N]

. Timing Advance Max Distance Calls [N]

. Timing Advance Max Distance Class [1-9]

. Timing Advance Max Report Class [1-9]

A.8 TRX KPIs

. DL Cumulative Quality in Class 4 V2 (dlq_2a) [%]

. DL Cumulative Quality in Class 5 V2 (dlq_2a) [%]

. DL Cumulative Quality in Class 4 V2 (ulq_2a) [%]

. DL Cumulative Quality in Class 5 V2 (ulq_2a) [%]



A.9 KPIs shown with the 3G_OPTIMIZER license

RNC KPIs

. Soft Handover Overhead for Area Level (RNC_192a) [%]

WCEL KPIs

. Allocated DL Dedicated Channel Capacity, CS Voice (RNC_163a)[kbit/s]

. Allocated DL Dedicated Channel Capacity, Data (RNC_165a) [kbit/s]

. Allocated UL Dedicated Channel Capacity, CS Voice (RNC_162a)[kbit/s]

. Allocated UL Dedicated Channel Capacity, Data (RNC_164a) [kbit/s]

. Average Downlink Load (RNC_102b) [dBm]

. Average Noise Level (RNC_177b) [dBm]

. Average Uplink Load (RNC_101b) [dBm]

. Cell Availability (RNC_133b) [%]

. CS Data Call Conversational Class (RNC_2b) [kbit/s]

. DL CS Data Call Streaming Class (RNC_3b) [kbit/s]

. DL CS Voice Call (RNC_1a) [kbit/s]

. DL PS Data Call Background Class (RNC_7b) [kbit/s]

. DL PS Data Call Conversational Class (RNC_4) [kbit/s]

. DL PS Data Call Interactive Class (RNC_6b) [kbit/s]

. DL PS Data Call Streaming Class (RNC_5b) [kbit/s]

. HSDPA Accessibility for NRT Traffic (RNC_604a) [%]

. HSDPA MAC-d Net Throughput (RNC_606a) [kbit/s]

. HSDPA MAC-hs Efficiency (RNC_607b) [%]

. HSDPA Received Data (RNC_608a) [Mbit]

. HSDPA User Accessibility for NRT Traffic (RNC_605a) [%]

. HSDPA Retainability for NRT Traffic (RNC_609a) [%]

. Intersystem Hard Handover Attempts (RNC_282a) [N]

. Intersystem Hard Handover Success Ratio (RNC_169a) [%]



Supported KPIs

. Intrasystem Hard Handover Attempts (RNC_281a) [N]

. Intrasystem Hard Handover Success Ratio (RNC_168a) [%]

. Maximum Noise Level (RNC_135a) [dBm]

. RAB Drop Ratio, NRT Services (RNC_100c) [%]

. RAB Drop Ratio, RT Services other than Voice (RNC_160a) [%]

. RAB Drop Ratio, Voice (RNC_159a) [%]

. RAB Setup and Access Complete Ratio, NRT Services (RNC_157a)[%]

. RAB Setup and Access Complete Ratio, RT Services other thanVoice (RNC_97a) [%]

. RAB Setup and Access Complete Ratio, Voice (RNC_96a) [%]

. RRC Drop Ratio (RNC_158a) [%]

. RRC Setup and Access Complete Ratio (RNC_154b) [%]

. Soft Handover Overhead for Cell Level (RNC_79b) [%]

. Soft Handover Success Ratio (RNC_195a) [%]

. Soft Handover Update Attempts (Addition and Replacement), NRT[N]

. Soft Handover Update Attempts (Addition and Replacement), RT [N]

. Soft Handover Update Attempts, NRT (RNC_194a) [N]

. Soft Handover Update Attempts, RT (RNC_193a) [N]

. Soft Handover Update Success Ratio (Addition and Replacement),NRT (RNC_194a) [N]

. Soft Handover Update Success Ratio (Addition and Replacement),RT (RNC_193a) [N]

. UL CS Data Call Streaming Class (RNC_9b) [kbit/s]

. UL CS Voice Call (RNC_8a) [kbit/s]

. UL PS Data Call Background Class (RNC_13b) [kbit/s]

. UL PS Data Call Conversational Class (RNC_10) [kbit/s]

. UL PS Data Call Interactive Class (RNC_12b) [kbit/s]

. UL PS Data Call Streaming Class (RNC_11b) [kbit/s]

. Propagation Delay Max Distance Class [0-255]



. Propagation Delay Max Distance Report Number [N]

. Propagation Delay Max Report Class [0-255]

. Propagation Delay Max Reports [N]

. HSDPA throughput over active time (RNC_722a) [kbit/s]



Supported KPIs

Appendix B Parameters read and optimized by Optimizer Tools

The tables below lists the parameters in the configuration database thatOptimizer reads and optimizes. The first table lists the parameters read byAdjacency Management. The second table lists the parameters read andoptimized by Frequency Allocation. The third table lists the parametersread and optimized by the service optimization tools.

Table 7. Parameters read and optimized by Adjacency Management

Parameter in Configuration database

Read byAdjacencyManagement

Optimised byAdjacencyManagement

BTS

Label x

Frequency Band In Use x

InSite Gateway x

Master BTS For Multi BCF x

Is Foreign x

Distinguished Name x

ADCE, ADJW, ADJS, ADJI, ADJG, ADJD

Label x

Old Status x x

BSC

Label x

BCF

BCF Type x

RNC

Label x

ANTE

Antenna bearing x

Adjacency constraint x

Adjacency constraint status x

Cell



Table 7. Parameters read and optimized by Adjacency Management (cont.)


Read byAdjacencyManagement

Optimised byAdjacencyManagement

Label x

BSIC BCC x

BSIC NCC x

SITE

Label x

Latitude x

Longitude x

TRX

Initial Frequency x

Channel 0 Type x

WBTS

Label x

WCEL

Label x

Primary downlink scrambling code x

UARFCN x

Is Foreign x


Note that Frequency allocation also creates the MAL object if necessary.

Table 8. Parameters read and optimized by Frequency Allocation


Read byFrequencyAllocation

Optimised byFrequencyAllocation

SITE x

User Label x

Latitude x



Parameters read and optimized by Optimizer Tools

Table 8. Parameters read and optimized by Frequency Allocation (cont.)




Longitude x

GID x

BSC x

User Label x

Version x


GID x

Cell x x

User Label x

BCC x x

NCC x x

Cell ID x

LAC x

Cell Type x

SITE GID x

GID x

BTS x x

User Label x

HSN1 x x

HSN2 x x

HSN3 x x

Hopping Mode x x

Is Hopping Used x x

Underlay Hopping Mode x x

MAIO Offset x x

Underlay MAIO Offset x x

MAIO Step x x

Underlay MAIO Step x x

Used MAL Id x x







Used Underlay MAL Id x x

MAL Id Used x x

Underlay MAL Id Used x x


Band x

Cell GID x

BSC GID x

GID x

MAL x x

Instance x x

Band x x

Distinguished Name x x

Frequencies x x

BSC GID x

GID x x

TRX x x

User Label x

Frequency Type x

Initial Frequency x x

Channel 0 Type x

TSC x x

BTS GID x

GID x

ADCE x

Source BTS GID x

Target BTS GID x

BTS KPI x

CS Traffic x



Parameters read and optimized by Optimizer Tools





CS Data Traffic x

Blocking x



Appendix C Default optimization profiles in Browser

There are object-specific default profiles and default optimization-case-specific profiles in Browser. The default optimization-case-specific profilesare briefly described in this appendix. For more information on Browser,see Browser in Optimizer Help.

C.1 Object-specific default profiles

Object-specific default profiles, such as the Default BTS profile, areprofiles for the network elements shown in Browser.

C.2 Default optimization-case-specific profiles

In addition to object-specific default profiles, some default optimizationprofiles have been created for selected planning tasks. The default profilesserve as examples on how to use the Browser Profile Editor to createoptimization-case-specific profiles and how to use them for optimization orvisualization. You can freely combine CM and PM data to form the profiles.

This section contains one example of a default optimization-case-specificprofile, and briefly lists the rest of such profiles.

C.2.1 RNC-WCEL Default Area Codes Analysis

The RNC-WCEL Default Area Codes Analysis profile contains the actualsituation of RNC identifiers, location area codes (LAC), routing area codes(RAC), and cell identifiers. The sorting feature in Browser provides an easymeans of making a Network Audit of wrongly assigned identifiers and/orcodes. Visualizing the information on Map simultaneously on dominance,cell icon and cell label makes errors in LAC/RAC/cell identifiers visual, andallows manual (mass) correction.

The profile displays the RNC element hierarchy: RNC - WCDMA cell.

The content of this profile is the following:

. RNC. RNC name. RNC Identifier

. WCDMA cell



Default optimization profiles in Browser

. Location area code

. Routing area code

. Service area code (SAC)

. Service area code for broadcast (SACB)

. Cell Identifier

Modifying the profile

In Browser, you can, for example, sort the objects according to the columnheaders, filter rows based on a certain column value, and change thecolumn order by dragging and dropping columns. For instructions, seeSorting objects in Browser and Changing the view in Browser in OptimizerHelp. The table layout is saved when you change the profile or object type.

By clicking Modify Profile in the Browser toolbar, you can create a newprofile based on this profile and add parameters or a KPI values to theprofile. In addition, if you want to see adjacency information, for example, itis possible to add a new relationship to the profile in the Browser ProfileEditor dialog. For instructions, see Managing profiles in Browser inOptimizer Help. Note that if a default profile contains a KPI, itssummarization level and day is selected in toolbar of the Optimizer mainwindow.

C.2.2 Other optimization-case-specific profiles

. Default Adjacency Optimization (site)

This profile contains adjacency information for adjacencies per site.The profile displays the element hierarchy: site - cell - BTS -adjacency. It lists all the adjacencies on the selected site, theirperformance and cell-level success.

. Default Adjacency Optimization (cell)

This profile contains adjacency information for adjacencies per cell.The profile displays the element hierarchy: cell - BTS - adjacency.

. Default Frequency Optimization (cell)

This profile contains a cell-level parameter set for frequencyoptimization. The profile displays the element hierarchy: cell - BTS -TRX.

. RNC-WCEL Default Adjacency CM

This profile contains all types of WCDMA adjacencies with a defaultconfiguration to get a fast overview of the existing adjacencysituation as a starting point for mass creation and/or editing.



. RNC-WCEL Default Call Setup and Retainability Analysis

Admission control or call access control in Nokia RAN are based onthe received and transmitted powers, their increased estimations arecaused by new connections, and certain targets and thresholds. Ifthe targets are set too low, too many calls may be blocked. On theother hand, targets that are set too high result in too muchinterference and degraded performance or even dropped calls in thenetwork. The purpose of optimizing the admission control test caseis to verify that with Optimizer, you can monitor and analyze theperformance of new calls to a network and the retainability ofexisting calls within a network. Also, you can optimize theparameters controlling these actions so that the target performanceis achieved.

. RNC-WCEL Default SHO Analysis

Soft Handover (SHO) in WCDMA networks offers diversity gain bycombining individually fading multiple radio links to a more reliableconnection. Moreover, because of the nature of SHO, the handoveras such is more reliable than a hard handover, as the newconnection is established before the old one is released. However,there are also some drawbacks that are discussed in the following.

In DL, the signal has to be transmitted by two or more different cellseither at one or several different sites. Therefore, there is a need foradditional resources (physical resources: WSP cards, moretransmitters, more power, and logical resources: morechannelization codes, for example). The number of additionalresources is characterized by the number of SHO overhead. TheSHO is always beneficial for a single user, but unlike in UL, wherethe UE in SHO still transmits only one signal received by multiplecells, in the DL, SHO needs multiple transmission that introducesadditional interference for other users. As a network-wide effect inDL, there is a point where the gain of SHO actually turns into a loss.

A good balance between the number of UEs in SHO and the UEsnot in SHO ensures the following:. SHO connections do not occupy too much resources (blocking

of new users).. the right number of the UEs are in SHO to still have an overall

gain.

The main effects to the SHO overhead are the transmission power ofthe primary CPICH (pilot power) and the parameters that affect thereporting of the SHO conditions by the UE.

. RNC-WCEL Default HHO (IF-HO) Analysis




The RNC-WCEL Default Hard Handover (Inter-frequency) Analysisprofile can be used to quickly check if there are problems in thehandover attempts and success, and link the problems to therelevant CM. For example, there may be certain reasons why HHOis not enabled, or thresholds may be set in a wrong way.

. RNC-WCEL Default IS-HO Analysis

The RNC-WCEL Default Inter-system Handover Analysis profile canbe used to quickly check if there are problems in the handoverattempts and success, and link the problems to the relevant CM. Forexample, there may be certain reasons why to make IS-HO may notbe enabled, or thresholds may be set in a wrong way. By showingthe HO attempts together with system borders on Map, conclusionscan be drawn if the HOs at the coverage end of one system happenin the border cells, or already earlier. Also, it is advisable to check ifthere are extensive IS-HO failures at the system border. This couldbe a consequence of HOs that are initiated too late and/or handoverthresholds or parameters that have been wrongly set.

. RNC-WCEL Default Prx Noise Analysis

Cells with potential problems from noise and/or interference in theWCDMA air interface can be spotted by analyzing the respectivenoise and/or interference related KPIs. Typically, these problems arecrucial for the performance of a WCDMA network but they cannot befixed by simple network parameter adjustments. They often resultfrom installation problems (for example, crossed feeders, badantenna locations, wrong main lobe directions, wrong tilts and badcable connections). These problems can cause increasedinterference. Also, industrial and man-made noise can be spottedwithout expensive on-site measurements. It is possible to export thelist of the worst performing cells to support site visits and correctivemeasures.

. RNC-WCEL Default Power and Load Analysis

This profile can be used to identify cells with high load. Such cellscan be targets for load balancing and/or HW upgrade. This profilecan also be used for identifying cells where the received andtransmitted powers do not match with the traffic carried, which mayindicate interference or noise problems.

. RNC-WCEL Default HSDPA Analysis

The RNC-WCEL Default HSDPA Analysis profile is intended forvisualizing, analyzing, and optimizing the main HSDPAconfiguration, HSDPA performance, and resource sharing betweenHSDPA and Dedicated Channels (DCHs). The profile contains bothCM data and KPIs.



For information on the HSDPA optimization cases that you canperform using Optimizer, see Visualizing HSDPA in Optimising aNetwork Using Optimizer.

. Default WCEL-ADJG

The Default ADJG profile is intended to display ADJG mainadjacency parameters with KPIs. The profile combines adjacencyCM and PM data.

. Default WCEL-ADJS

The Default ADJS profile is intended to display ADJS mainadjacency parameters with KPIs. The profile combines adjacencyCM and PM data.




Index

Aadjacency

list 59plan 59ranking 49template 32

adjacency direction 82adjacency type

ADCE 31ADJD 31ADJG 31ADJI 31ADJS 31ADJW 31

administrative tasks 16analysis 14Antenna Data Editor 16ARP 47automated adjacency management 36Average Received Power 47

BBCCH allocation list 48Browser 22, 29Browser export 27

CCarrier over Interferer Probability 47channel assignment 76CIP 47constraint 34

Ddominance 85

Fforbidden channel 77frequency group 77frequency optimization 71

GGeographic Information System (GIS) 16

Iinterference data 60interference matrix 26interference measurements 51

Kkey performance indicator 24

ADCE 95ADJD 96ADJG 95ADJI 96ADJS 95BTS 96cell 98

RNC 99TRX 98WCEL 99

MMap 21measurement retrieval 53

NNavigator 20

Oopen interface 26optimization

algorithm 13automatic 13manual 13process 13-14

optional functionality 14

Ppanes 19parameter management 25parameters 102performance degradation 24periodical tuning 14permissions 15polygon 17predictions 54

RRadio Resource Management 15rotation 66

Sscope 19, 21scrambling code 81separation 78simple link loss calculation 54

Ttemplate assignment rule 32temporary BA list 48threshold set 25Threshold Sets dialog 25

Uuser interface 19

WWCDMA adjacency 59



optimizer principles for 2.2 cd2

Documents