Optimizer Principles

Optimizer Principles

DN0196638 Issue 3-3 en

© Nokia Corporation Nokia Proprietary and Confidential

1 (54)


The information in this documentation is subject to change without notice and describes only the product defined in the introduction of this documentation. This documentation is intended for the use of Nokia's customers only for the purposes of the agreement under which the documentation is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the documentation are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the documentation. Nokia's liability for any errors in the documentation is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this documentation or the information in it. This documentation and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this documentation may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright © Nokia Corporation 2005. All rights reserved.

2 (54)



Contents Contents 3 List of tables 4 List of figures 5 1 1.1

About this document 7 Terms 7

2

Changes in NetAct documentation 11

3

NetAct compatibility and capacity information 13

4 4.1

Introduction to Optimizer 15 Radio network optimisation process in NetAct 16

5 5.1 5.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4 5.4 5.4.1 5.4.2 5.4.3 5.5 5.6 5.7 5.7.1 5.7.2 5.8 5.9

Basic optimisation functionalities 19 Optimizer main user interface 19 Optimisation plans 21 Administration 22 Map administration 22 Antenna Data Editor 22 Task Management 23 Polygon Area Management 23 Network Statistics Control 23 KPI Retrieval 23 Threshold sets 29 Interference matrix generation 29 Adjacency constraint management 29 Manual adjacency management 30 Automated adjacency management 31 Restrictions for adjacency optimisation 31 Distance and antenna bearing based adjacency creation 34 Manual Configuration Management Parameter Tuning 36 Open interfaces 36

6 6.1 6.2 6.3 6.4

Optional Optimizer functionality 39 Measurement based automated adjacency optimisation 39 Automated frequency planning 39 Service Optimizer 40 Advanced visualisation 40

7

Where to find more 43

Appendix A. Parameters read and optimised by Optimizer Tools 45 Index 53



3 (54)


List of tables

4 (54)

Table 1.

Terms

7

Table 2.

Supported CM objects in Optimizer

Table 3.

Parameters read and optimised by Adjacency Management

Table 4.

Parameters read and optimised by Frequency Allocation

Table 5.

Parameters read and optimised by Service Optimizer


21 45

47

49


List of figures Figure 1.

Optimisation cycle in NetAct 16

Figure 2.

Optimizer main user interface 20

Figure 3.

The relation between antenna directions and the positions of the source and destination sector 35

Figure 4.

Adjacency creation factor K 36



5 (54)


6 (54)



About this document

1

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

1.1

Terms The following table explains the terms and abbreviations used in this document.

Table 1.


Terms

Term

Explanation

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

ADJW

An adjacency from a BTS to a WCEL

AVG

Average

AFP

Automatic Frequency Planning

ARP

Average Received Power

BA list (BAL)

BCCH Allocation List

BCC

Base station Colour Code

BCCH

Broadcast Control Channel

BCF

Base Control Function

BSC

Base Station Controller

BSIC

Base Station Identity Code

BSS

Base Station Subsystem


7 (54)


Table 1.

8 (54)

Terms (Continued)

Term

Explanation

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

CM

Configuration Management

CS, CSW

Circuit Switched

CSV

Comma-separated values

DCN

Data Communication Network

DL

Downlink

EWCE

External WCDMA cell

EXCC

External cell collection

FEP

Frame Erasure Probability

GIS

Geographic Information System

GPRS

General Packet Radio Service

HO

Handover

HOC

Handover Control

HOPG

Inter-system Handover Path

HOPI

Inter-frequency Handover Path

HOPS

Intra-frequency Handover Path

HOSR

Handover Success Rate

HSCSD

High Speed Circuit Switched Data

HSN

Hopping Sequence Number

ICR

Interferer over Carrier Ratio

ID

Identifier

IRP

Integration Reference Point

KPI

Key Performance Indicator

LAC

Location Area Code



About this document

Table 1.


Terms (Continued)

Term

Explanation

MAIO

Mobile Allocation Index Offset

MAL

Mobile Allocation List

MML

Man-machine Language

MS

Mobile Station

NCC

Network Colour Code

NE

Network Element

NSVC

Network Service Virtual Connection

PAPU

Packet Processing Unit

PI

Performance Indicator

PLMN

Public Land Mobile Network

PM

Performance Management

POC

Power Control

PS

Packet Switched

RAC

Radio Access Configurator

RF

Radio Frequency

RNC

Radio Network Controller

RRM

Radio Resource Management

RXLEV

Received Signal Level

SACCH

Slow Associated Control Channel, bi-directional

SDCCH

Stand Alone Dedicated Control Channel

SMS

Short Message Service

TCH

Traffic Channel

TREC

Treatment Class

TRX

Transceiver

WAP

Wireless Access Protocol

WBTS

WCDMA Base Station

WCDMA

Wideband Code Division Multiple Access

WCEL

WCDMA Cell


9 (54)


10 (54)



Changes in NetAct documentation

2

Changes in NetAct documentation The information in this document relates to OSS3 releases and deliveries. This document is compatible with the latest release of NetAct and covers the necessary release specific updates. For information on the release specific changes in this document and the related software changes, see Changes in NetAct Documentation.

Note If you are using a PDF print-out of this document and also need the change information, please print out the Changes in NetAct Documentation (dn03511086) document.



11 (54)


12 (54)



NetAct compatibility and capacity information

3

NetAct compatibility and capacity information For information on NetAct system and capacity, and the compatibility between NetAct and network element releases, see the NetAct Compatibility and Capacity Information document.



13 (54)


14 (54)



Introduction to Optimizer

4

Introduction to Optimizer NetAct Optimizer is used in the statistical and/or network wide optimisation process in NetAct. Optimizer provides visibility to current network behaviour by combining the actual GSM and WCDMA network configuration parameters and measured performance statistics with advanced visualisation and analysis functionality. Parameters can be optimised manually for small changes or automatically by choosing from the range of optimisation solutions provided by Optimizer. Optimizer can be used for a single cell or for a whole region. The result of optimisation algorithms can be visualised on a geographical map before downloading the optimisation plan to the network. The plan with the changed parameters is sent to RAC (Radio Access Configurator) where it is validated 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 real network), 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 raster map based calculations - where, for example, the interference matrix is calculated by considering signal strengths in each map pixel - a mobile measurement report is used. When the data is processed in Optimizer, only some analysis is needed.

•

Increased level of automation. With Optimizer, the whole optimisation cycle is faster than with planning tools. As Optimizer is implemented in the NetAct Framework, the actual configuration data and measurement reports are available for processing. The network topology in Optimizer is always consistent with the actual network data. When running Optimizer for the first time, some customising is needed, such as parameters needed to guide the generation algorithms. Once the parameters are set, the next optimisation round is more effortless.



15 (54)


Optimizer obtains performance data from the BSC release S10.5 and S11 measurements via an interface to a reporting tool. The reporting functionality in the NetAct basic package can be used for network monitoring and for collecting KPIs into Optimizer. Any preferred external tool can be used for monitoring performance before and after optimisation. The Optimizer solution is composed of basic and licensed functionalities. Geographical map based visualisation and manual object and parameter management are basic optimisation functionalities. The following four functionalities are optional:

4.1

•

Advanced visualisation

•

Automated adjacency management

•

Frequency allocation, including BSIC planning (Performance Optimisation)

•

Service Optimizer

Radio network optimisation process in NetAct The optimisation process usually takes place when the monitored performance drops below the set targets, when a periodical tuning task is to be started or when there is need to optimise the behaviour of new network elements in the network. Measurements are used for analysing the network and service performance development against set targets. A detailed analysis is performed in order to find the reasons behind decreased performance and to select the right corrective actions. In this phase, the relations between performance indicators and element parameters are analysed. After the analysis phase, the configuration parameter settings are optimised and the set quality criteria are checked. When the corrections are verified and implemented into the network, the quality monitoring cycle starts from the beginning. Implement with RAC Optimisation in NetAct Tune Improve with Optimizer

Figure 1.

16 (54)

Measure Analyse with Reporter

Analyse with Optimizer

Optimisation cycle in NetAct



Introduction to Optimizer

Optimisation can be targeted to improve the radio resource utilisation rate (optimisation) by changing the operating point on the capacity-coverage-cost trade-off curve. Statistical optimisation also sets the limits and operation targets for real time optimisation loops, like Radio Resource Management (RRM) in network elements. Optimisation is also involved when the network is enhanced in terms of new cells or new services, or changes are made in the service provisioning etc. As soon as elements are activated in the network and they can be measured, they can be optimised as well.



17 (54)


18 (54)



Basic optimisation functionalities

5

Basic optimisation functionalities The following sections describe the basic functionalities available in Optimizer by default. The main application user interface is also presented with some details of the interface components to give an idea how Optimizer works in general.

5.1

Optimizer main user interface The main user interface contains a main menu bar with application-specific menus. In addition, the user interface consists of several workspaces, each of them tailored for certain functionality area supported by Optimizer. The availability of a workspace depends on the purchased Optimizer software license. When the workspace is available, it can be accessed from the Workspaces menu of the main menu bar or by clicking the shortcut icons that are always visible on the left side of the main window. The practical optimisation and analysis work happens always in the context of workspace(s) and with the defined optimisation scope (target). The optimisation scope is selected from the Network View workspace, which opens by default when Optimizer is started. It is the core workspace for object browsing, navigation, and manual optimisation. Each workspace may have different scope selected for optimisation at the same time. The following figure shows the Optimizer main user interface with the Network View workspace open:



19 (54)


Figure 2.

20 (54)

Optimizer main user interface

1.

Navigator. This component offers several tree views for managing the data groups, most suitable for different optimisation purposes. For example, a different tree view presentation is preferred depending on whether you optimise adjacencies, or if you browse or tune objects of the hardware topology.

2.

Map. This component is used to show the network objects and related analysis, and optimisation results on a geographical map. Also, Map can be used for manual adjacency management.




5.2

3.

Visualisation Profiles. This component is used to control the parameter and KPI visualisation of the managed objects and the related analysis on the Map.

4.

Browser. With this component you can browse and edit objects in a table view. Object filtering and mass editing are supported. Also, with powerful browser profile management you can customise the view of the object parameters and the object relations, for your own purposes, or you can also share your profiles with other users. Browser has a set of default profiles (for each object type) that all users can always use when Optimizer is open. From the browser, you can export data to a CSV file.

Optimisation plans All parameter tuning and optimisation in Optimizer happens via optimisation plans. If you do the optimisation work only on top of an actual (live) network configuration, the optimisation plans do not depend on RAC configuration management plans (planned network configurations). However, sometimes you also need to take the planned network configurations into account in the optimisation process (for example, network due to network roll-out preparation). For this, Optimizer supports the import of planned objects from the RAC configuration management plan. You can use this feature before starting the actual optimisation work. Optimizer supports the following NetAct CM and topology CM objects:

Table 2.

Supported CM objects in Optimizer

ADCE

BTS

HOPS

ADJG

EWCE

MAL

ADJI

EXCC (not visible in the UI)

PAPU

ADJS

FMCG

POC

ADJW

FMCI

RNC

ANTE

FMCS

SGSN

BAL

HOC

TRX

BCF

HOPG

WBTS

BSC

HOPI

WCEL



21 (54)


In addition, GSM cells are modelled as SEGMENT objects.

Note Parameters for planned SGSNs cannot be edited because they are not available in Service Optimizer. When you are ready with the optimisation plan and the changes can be applied to the actual network, the optimisation plan including the proposed modifications to the actual network configuration is exported to the RAC plan database, which then in turn is prepared for provisioning with RAC tools. For plan management (create, delete, import, and export), Optimizer has simple user interface tools, Plan Management dialog and CM Data Exchange dialog, which are included in its basic functionality. You can access these tools from the main menu and the toolbar under it.

5.3

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

5.3.1

Map administration Optimizer uses Geographic Information System (GIS) to visualise digital map data. The map data needs to be initialised before optimisation can be started even if Optimizer is used without any map data. Map Administrator tools is used to define the basic settings for GIS. For more information on GIS, see Geographic Information System Principles, and on managing GIS settings, see Managing GIS Maps.

5.3.2

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

22 (54)




Antenna Data Editor is a stand-alone administration application that is included in the basic Optimizer installation package.

5.3.3

Task Management Every Optimizer user can monitor the ongoing task executions in the Administration workspace of Optimizer. You can check task status reports, remove tasks, and view the task configurations during normal operations while the Optimizer main user interface is open.

5.3.4

Polygon Area Management Optimizer map supports the selection of sites by polygon area. You can define polygon areas on top of a geographical map for private use and also define the polygons as public (seen by all users), if necessary.

5.4

Network Statistics Control Optimizer has a dedicated workspace for controlling the performance management (PM) counter data retrieval and the timeline of PM data for KPI analysis and optimisation purposes.

5.4.1

KPI Retrieval Key performance indicators (KPI) are the most important indicators of network performance. KPI reports allow the operator to detect the first signs of performance degradation and prevent the development of critical network problems. KPIs on the regional level can be used for analysing performance trends, on the RNC level for locating problems and on the cell level for troubleshooting specific cells. The supported KPIs are listed below. ADCE KPIs


•

HO Attempts to ADCE

•

HO Success Rate

•

HO Success to ADCE

•

HO Traffic Share


23 (54)


BSC KPIs

•

BSC Avg user throughput TREC1

•


•


•

BSC Throughput TREC1 DL

•

BSC Throughput TREC1 UL

•


•


•


•


•

BSC Traffic TREC1 DL

•


•


•

BSC Traffic TREC2 UL

•


•

BSC Traffic TREC3 UL

BTS KPIs

24 (54)

•

Additional GPRS channel use

•

Average CS traffic per BTS (trf_97)

•

Average DL TBF per timeslot (tbf_38c)

•

Average PS territory (ava_16b)

•

CS Data Traffic

•

CS Traffic

•

CSW congestion

•

DL Cumulative Quality in Class 4 V2 (dlq_2a)

•


•

Incoming HO Success (hsr_18)

•

Outgoing HO Success (hsr_19)




•

SDCCH Blocking (blck_5a)

•

SDCCH Congestion Time (cngt_2)

•

SDCCH Congestion

•

SDCCH Drop Ratio (sdr_1a)

•

SDCCH TCH Setup Success (cssr_2)

•

TCH Blocking (blck_8d)

•

TCH Drop Out Before Call Re-establishment (dcr_4f)

•

Territory upgrade rejection rate due to CSW traffic

•

Territory upgrade rejection rate due to lack of PCU capacity

•

Total HO Failure (hfr_1)

•

Traffic Share

•

UL Cumulative Quality in Class 4 V2 (ulq_2a)

•


PAPU KPIs

•

PAPU Avg BSSGP Buf Util Prior 1

•


•


•


•

PAPU NSVC discarded data packets Prior 1

•


•


•


RNC KPIs

•

Soft Handover Overhead for Area Level

SEGMENT KPIs


•

CS Data Traffic

•

CS Traffic

•

Cell Avg user throughput TREC1


25 (54)


26 (54)

•


•


•

Cell Throughput TREC1 DL

•

Cell Throughput TREC1 UL

•


•


•


•


•

Cell Traffic TREC1 DL

•

Cell Traffic TREC1 UL

•


•


•


•


•


•


•

Incoming HO Success (hsr_18)

•

Outgoing HO Success (hsr_19)

•

SDCCH Blocking (blck_5a)

•

SDCCH Congestion Time (cngt_2)

•

SDCCH Congestion

•

SDCCH Drop Ratio (sdr_1a)

•

SDCCH TCH Setup Success (cssr_2)

•

TCH Blocking (blck_8d)

•

TCH Drop Out Before Call Re-establishment (dcr_4f)

•

Total HO Failure (hfr_1)

•

Traffic Share




•


•


SGSN KPIs

•

SGSN Avg BSSGPBuf Util Prior 1

•


•


•


•

SGSN NSVC discarded data packets Prior 1

•


•


•


TRX KPIs

•


•


•

DL Cumulative Quality in Class 4 V2 (ulq_2a)

•

DL Cumulative Quality in Class 5 V2 (ulq_2a)

WCEL KPIs


•

Allocated DL Dedicated Channel Capacity, CS voice

•

Allocated DL Dedicated Channel Capacity, Data

•

Allocated UL Dedicated Channel Capacity, CS voice

•

Allocated UL Dedicated Channel Capacity, Data

•

Average Downlink Load

•

Average Noise Level

•

Average Uplink Load

•

CS Data Call Conversational Class

•

Cell Availability

•

DL CS Data Call Streaming Class

•

DL CS Voice Call


27 (54)


28 (54)

•

DL PS Data Call Background Class

•

DL PS Data Call Conversational Class

•

DL PS Data Call Interactive Class

•

DL PS Data Call Streaming Class

•

Intersystem Hard Handover Attempts

•

Intersystem Hard Handover Success Ratio

•

Intrasystem Hard Handover Attempts

•

Intrasystem Hard Handover Success Ratio

•

Maximum Noise Level

•

RAB Drop Ratio, NRT Services

•

RAB Drop Ratio, RT Services other than Voice

•

RAB Drop Ratio, Voice

•

RAB Setup and Access Complete Ratio, NRT Services

•

RAB Setup and Access Complete Ratio, RT Services other than Voice

•

RAB Setup and Access Complete Ratio, Voice

•

RRC Drop Ratio

•

RRC Setup and Access Complete Ratio

•

Soft Handover Attempts (Addition, Deletion and Replacement), NRT

•

Soft Handover Attempts (Addition, Deletion and Replacement), RT

•

Soft Handover Overhead for Cell Level

•

Soft Handover Success Ratio

•

Soft Handover Update Success Ratio (Addition and Replacement), NRT

•

Soft Handover Update Success Ratio (Addition and Replacement), RT

•

UL CS Data Call Streaming Class

•

UL CS Voice Call

•

UL PS Data Call Background Class

•

UL PS Data Call Conversational Class




5.4.2

•

UL PS Data Call Interactive Class

•

UL PS Data Call Streaming Class

Threshold sets A threshold set is an ordered set of threshold ranges. Threshold sets can be defined for KPIs (Key Performance Indicators) and CM parameters for visualisation. Threshold sets are global, which means that they are visible to all users, and therefore, they are not plan-specific or user-specific. An assignment between a threshold set and a parameter is user-specific, but it is not plan-specific. Threshold sets can be created, edited and deleted in the Threshold Sets dialog. Instructions on these tasks are given in Optimizer Help. KPIs and CM parameters are classified according to the network hierarchy in the Threshold Sets dialog, where the they can be found under corresponding network elements. The colours used with the threshold sets for visualising parameters and KPIs are defined in the Select/Edit Gradient dialog.

5.4.3

Interference matrix generation The interference matrix represents the potential interference relations between cells. Interference can be computed or expressed with different mathematical methods such as ARP (Average Received Power), CIP (Carrier over Interferer Probability), or FEP (Frame Erasure Probability). In Optimizer, interference is computed based on measurements that have been made in an operated network. Also, predicted interference can be generated to new cells or cells where measurements are missing otherwise, for example because of so called blind spots. The structure and contents of an interference matrix are described in more detail in the Interference Matrix Open Interface document. If you have purchased the licence for Optimizer's Performance Optimisation and Automated Adjacency Management options, a separate document containing more details will be delivered with the software package.

5.5

Adjacency constraint management Adjacency constraints exist only in actuals and are not network objects, which could be provisioned. You can create two types of adjacency constraints in Optimizer: mandatory and forbidden adjacency constraint.



29 (54)


Adjacency constraints are always checked when adjacencies are deleted or created by automated adjacency creation algorithms. If there are forbidden adjacency constraints, the adjacency cannot be created by the automated adjacency optimisation. If there are mandatory adjacency constraints, the adjacency cannot be deleted by the automated adjacency optimisation. In manual adjacency creation, forbidden adjacencies are checked and if they exist, the adjacency cannot be created before the constraint is removed.

5.6

Manual adjacency management Adjacencies define the relationship between cells. Adjacencies can be created, modified and deleted either on the map or in Navigator. Depending on the type of cells for which the relationship is defined, there are different types of adjacencies: •

ADCE, an adjacency between BTSs

•

ADJW, an adjacency from a BTS to a WCEL

•

ADJG, an adjacency from a WCEL to a BTS

•

ADJS, an adjacency between WCELs, intra-frequency

•

ADJI, an adjacency between WCELs, inter-frequency

All adjacency types can be displayed on map at the same time or separately. The adjacencies may have different colouring depending on their type. The direction of the adjacency is also visualised. Adjacency state (deleted/actual/planned/forbidden/mandatory) can also be used as filtering criteria of the visible objects. All these settings can be customised per user. An adjacency can be visible on map only if the target cells are visible. In addition, there is a Foreign Adjacency which is an inter-NetAct adjacency. An adjacency to a foreign BTS, that is a BTS that belongs to another NetAct, is also shown on map. These adjacencies can be viewed at the same time with other adjacencies or separately. A foreign BTS is always a target in adjacency relation. The same applies to a foreign WCEL. Optimizer shows the available adjacency templates that have been created in CM Editor. Templates contain default parameter values for adjacency creation. You can select the templates to be used for different adjacency types and create the rules for each source and target cell combination according to which these templates are assigned. Templates can be assigned globally, or individual controllers (BSC or RNC) or group of controllers can be selected for a template assignment. If no matching adjacency template is found, Optimizer assigns the System template by default. This should be avoided because the System template parameter values do not work properly in a real network.

30 (54)




5.7

Automated adjacency management Optimizer provides two methods for creating adjacencies automatically:

5.7.1

•

Predicted distance and antenna direction based adjacency creation for GSM, WCDMA and between the systems

•

6.1 Measurement based automated adjacency optimisation.

Restrictions for adjacency optimisation In unidirectional adjacency creation, outgoing adjacencies are created (or undeleted) in the selected scope only if the adjacency meets all the thresholds defined by the user. In the same way, adjacency is deleted (or removed from the plan) if the adjacency violates any of the thresholds defined by the user. There are also certain restrictions for the algorithm. For some algorithms, the user can decide whether to ignore or take them into account (controllable restrictions), but the rest of them cannot be violated (restrictions uncontrollable for the user). These restrictions are listed below in order of importance: 1.

Indoor (Uncontrollable)

2.

Foreign (User controllable)

3.

Scrambling code/frequency collisions (Uncontrollable)

4.

Adjacency ID limitation for WCDMA and intersystem adjacencies (Uncontrollable)

5.

Enable Creating ADCEs to same BCCH (User controllable)

6.

Enable Creating neighbours to same BCCH BSIC (User controllable)

7.

Dual Band Adjacency creation (Uncontrollable)

8.

Forbidden adjacency (Uncontrollable)

9.

Mandatory adjacency (Uncontrollable)

10.

Bi-directional Adjacency Creation (User controllable)

11.

Enable Changes in and out of the selected scope (User controllable)

Restrictions uncontrollable by the user

The following list shows the cases where adjacencies are never created and/or deleted by the optimisation algorithm:



31 (54)


•

The optimisation algorithm does not create or delete adjacencies (bidirectional or unidirectional) to an indoor BTS (except when the indoor BTS is In/Out GateWay). The algorithm can create an adjacency between normal and In/Out Gateway BTSs and between In/Out Gateway BTSs.

•

The optimisation algorithm does not create or delete adjacencies to or from a foreign BTS or EWCE.

•

In the pure WCDMA adjacency creation, the case where the source and target cells have the same scrambling code and frequency causes handover ambiguity.

•

In Radio Access Configurator, ADJS, ADJI, ADJG and ADJW adjacencies have the same amount of adjacency IDs as is the amount of allowed ADJS/ADJI/ADJG/ADJW adjacencies per cell. Adjacency Optimisation takes into account the ID restriction only within the opened plan. For example, if GSM BTS-1 has 25 actual ADJWs and 5 ADJWs would be in deleted status, then the algorithm could create only 7 new ADJWs as totally there are 32 IDs reserved. In plan and actual (RAC or Optimizer), the following statuses reserve IDs: • • • •

ACTUAL CREATED UPDATED DELETED.

Adjacency optimisation tool can change statuses. The status can change from: • •

32 (54)

CREATED to REMOVE_FROM_PLAN DELETED to UNDELETED.




Adjacency Optimisation counts adjacencies with statuses ACTUAL, CREATED, UPDATED, and DELETED. The sum or these adjacencies is shown in the user interface as ID reservation AMOUNT. Algorithm is not allowed to exceed Maximum ID amounts.

Note As adjacency optimisation takes only actual context and the opened Optimizer plan into account, it is still possible to exceed the ID amount in RAC plan, but at least inside one plan ID amount is not exceeded. ID reservation can be controlled by keeping some buffer in the Maximum Adjacency List Length (for example, using 30 instead of full 48 in ADJI Maximum Adjacency List Length). To be able to create new adjacencies for a cell that has the maximum amount adjacencies in use, the user has to delete some adjacencies (create a deletion plan, provision it to network and remove the deletion plan). When adjacency ID is not found from topology (that is, no actual or planned adjacencies with that ID exist in RAC DB) it, can be used again. Before exporting Optimizer plan to RAC, the user needs to check that there are no old delete plans containing ADJG/ADJI/ADJS/ADJW objects, because the IDs for adjacencies remain reserved as long as a plan for the object exists in the RAC database. •

Adjacency optimisation does not delete adjacencies that have a mandatory adjacency constraint. Mandatory adjacency constraints are defined on the map or in the Browser.

•

The user can create forbidden adjacency constraints between cells in Navigator and on map. Adjacency optimisation does not create an adjacency where it is forbidden.

•

The following rules apply for dual band adjacency creation: • • • •


BTS in PGSM900 band shall have maximum 18 adjacencies to BTSs in bands EGSM900+GSM1800. BTS in GSM1800 band shall have maximum 16 adjacencies to BTSs in band GSM900. BTS in 850 band it can have maximum 18 adjacencies to BTSs in 1900 band. BTS in 1900 band can have maximum 22 adjacencies to BTSs in 850 band.


33 (54)


Restrictions controllable by the user

•

The algorithm can create an adjacency from normal to foreign BTSs. That is, the user can enable/disable adjacencies with the parameter.

•

The user can select whether the algorithm is allowed to create adjacencies to cells that have the same BCCH as the source cell. The user can control this with the UI parameter Enable Creating ADCEs to same BCCH.

•

The user can select whether the algorithm is allowed to create neighbours to cells that have the same BCCH BSIC combination as the source cell. If this option is used and it results in same BCCH BSIC combination with source and adjacent cell's adjacent cell, it is recommended that frequencies are optimised after adjacency optimisation. The user can control this with the UI parameter Enable Creating ADCEs to same BCCH BSIC.

•

The option Enable Changes in and out of the selected scope enables deleting and creating of adjacencies from the optimisation scope to outside of the optimisation scope. This also enables deleting and creating adjacencies from outside the optimisation scope to the optimisation scope. With this option it is possible to optimise a whole regional cluster using one optimisation scope at a time (optimisation areas), so that optimisation scopes do not overlap with each other.

•

According to the "Technical Note TN 046 Restriction on number of cells in SIB11/12 due to inconsistency problem in 3GPP TS 25.331", the maximum number of neighbours with any configuration is guaranteed to be 47 (35 if HCS is used). Optimizer restricts creating more WCDMA adjacencies to Optimizer plan than what is defined in the configuration file setting. The user can change the values according to the used configuration in the optimizereditable-system.properties file (for more information on this configuration file, see Optimizer Technical Reference Guide).

5.7.2

Distance and antenna bearing based adjacency creation Distance and antenna direction based adjacency creation allows creating and deleting of adjacencies by using distance or distance and bearing as criteria. This method can be used for initial adjacency creation in cases where the network objects are not yet in the air, but it provides also means for fast mass creation or deletion of actual objects. This is useful, especially when managing WCDMA adjacencies. The distance and antenna bearing based algorithm is based on distance and antenna bearing. It could be summarised as follows:

34 (54)




1.

User defines the maximum distance for the adjacency to be created D.

2.

User defines the maximum angle q (Maximum Theta Angle). In the following figure, angle1 is the angle between the antenna bearing and the direction of the vector joining the source and destination sights, as similar to angle2. Theta angle is angle1 + angle2.

(X1,Y1) 1 2

1

d 2

(X2,Y2)

Figure 3.


The relation between antenna directions and the positions of the source and destination sector

3.

User selects the types of adjacencies he wants to create.

4.

User defines the maximum number of adjacencies to be created /cell N.

5.

The algorithm creates adjacencies between all sectors that belong to the same site.

6.

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

7.

Highest priority would be assigned to each adjacency created in Step 5, while for adjacencies created in Step 6, it will prioritised according to the value of the adjacency creation factor K. The higher the value of K the higher the priority of the adjacency in that site.


35 (54)


Figure 4.

Adjacency creation factor K

F has no unit. The range is [0…1], angle 1 and angle 2 are in degrees.

5.8

Manual Configuration Management Parameter Tuning Parameter optimisation can be done either manually for small, occasional changes or automatically by using the optimisation algorithms provided by Optimizer. Object parameters can be edited manually in Browser or in Navigator. You can create a profile for the network elements shown in Browser. The profile defines which child elements are shown beneath the profiled element. For example, in this way you can select possible child elements related to a BTS. Using profiles parameter-related problems can be better visualised.

5.9

Open interfaces In order to complete the optimisation process, some additional data handling is required. Optimizer contains open interfaces to handle information. In addition, optimisation results can be transferred in a table view to external tools, and forbidden channels can be imported from a CSV file for a selected BSC. Interference Matrix open interface

Optimizer generates an Interference Matrix based on mobile measurement information collected to Reporter via BSCs. The matrix is used when generating adjacency lists and in frequency allocation. The measurement based Interference Matrix is more accurate than any prediction-based Interference Matrix and it will thus enable more efficient frequency utilisation. Predicted interference can be generated to new cells or cells where measurements are missing otherwise, for example because of so called blind spots. Predicted interferences are based on antenna directions and distances between cells.

36 (54)




With the Interference Matrix open interface you can export the Interference Matrix from Optimizer to use it with an external tool, for example, another allocation tool. It is also possible to import Interference Matrices from external systems to Optimizer, if, for example, measurements are insufficient in some BTSs to enable accurate Interference Matrix creation and the matrix is completed manually or based on estimates outside Optimizer. The interference data is stored in the Optimizer database. When a user exports the interference matrix, it is saved to a specified location in XML or CSV format. A more accurate description of the format can be found in the Interference Matrix Open Interface document. Browser export

A selected area or all Browser data can be exported into an export file. Exported Browser data can be used in other tools (for example, Microsoft Excel). Import of forbidden channels

Forbidden channels can be imported from a CSV file into Optimizer for a selected BSC to be used in frequency allocation. The CSV file should have the following columns: Mode, BscId, LAC, CI, and Forbidden Channels. The values are separated with commas and the records are separated with line feeds. The mode column attributes are the following: ADD, REP, and DEL.



37 (54)


38 (54)



Optional Optimizer functionality

6

Optional Optimizer functionality The following sections introduce Optimizer’s optional functionality modules.

6.1

Measurement based automated adjacency optimisation Adjacency optimisation utilises handover measurements collected and reported by BSCs. By analysing the reports, the unused adjacent cells can be identified and removed from the adjacency list. Mobiles measure the whole BCCH segment of the frequency band and report 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 visualised and modified. You can run several sessions of optimisation, compare the results, and select the desired optimisation results to be saved. Running several sessions provides better control over the adjacency optimisation process. If you have purchased the licence for Optimizer's Automated Adjacency Management option, a separate document containing more details will be delivered with the software package.

6.2

Automated frequency planning Frequency allocation is an optional optimisation package. It uses an interference matrix generated based on the mobile measurements or an imported interference matrix. It uses CS Traffic, CS Data Traffic, and blocking KPIs. These traffic KPIs with interference matrix are used for minimising the amount of interfered traffic with powerful optimisation algorithms. The tool supports common-BCCH and multi-BCF features as well as all frequency hopping modes, including allocating MALs, MAIO offset, MAIO step, and HSNs. Also BSIC and TSC can be optimised. Allocation results can be analysed in table and graph formats and on top of a geographical map.



39 (54)


If you have purchased the licence for Optimizer's Performance Optimisation option, a separate document containing more details will be delivered with the software package.

6.3

Service Optimizer Service Optimizer, one of Optimizer's optional functionality modules, is the first NetAct tool to implement the treatment class (TREC) concept. Service Optimizer allows user to define the treatment classes (target behaviour setting in terms of throughput), decide - together with service management - how the available TRECs should be used for services (service mapping), and follow the target achievements on TREC level via analysis methods based on measurements. The QoS-related parameters in BSC and 2G SGSN can also be configured in Service Optimizer. Packet based services - of which Push-to-Talk and WAP browsing are examples - are not the only end-user services that have requirements related to quality. Traditional circuit-switched based speech and SMS services also need to be taken into account, and for this reason, Service Optimizer also looks at traffic balancing between CS and PS traffic in terms of capacity allocation. The capacity in radio network is visualised and analysed for the chosen area/NEs, and locating the cells where changes to capacity allocation are needed, is easy. Service Optimizer provides an algorithm for optimising the capacity allocation. In case capacity problems cannot be overcome by adjusting the capacity allocation, the tool also suggests where it would be necessary to add capacity (a new TRX). If you have purchased the licence for Optimizer's Service Optimizer option, a separate document containing more details will be delivered with the software package.

6.4

Advanced visualisation A geographical map provides a baseline for the visualisation of network topology, actual parameters and measured KPIs. Link loss estimates combined with configuration and measurement statistics provide useful map views for analysing the network. The map information is used in the optimisation process for visualisation of the mobile network structure and to give a new perspective for performance analysis. The main input data for the optimisation algorithms comes from statistical measurements, from the network elements or user equipment. It is possible to calculate cell dominance areas and interference distribution for performance visualisation purposes. Note that only one dominance raster is stored at a time, and calculating a new dominance raster or closing Optimizer removes the previous dominance raster from memory.

40 (54)



Optional Optimizer functionality

Residual interference can be displayed on top of dominance, and Cell Icon and label. It is a quality indicator calculated from both CM and PM data to be used as a tool to test the quality of the frequency plan. By using it, you can view the overall probability of interference for each cell. If you have purchased the licence for Optimizer's Advanced Visualisation option, a separate document containing more details will be delivered with the software package.



41 (54)


42 (54)



Where to find more

7

Where to find more Optimizer documentation

•

For information on the process of optimising a network using Optimizer, see Optimising a Network Using Optimizer.

•

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

•

For information on Optimizer database tables, refer to Database Description for Optimizer.

•

For detailed instructions on how to use the Optimizer applications, see the following helps: • •

Optimizer Help Frequency Allocation Help

Geographic Information System documentation

•

For information on the Geographic Information System, see the following documents: • •

Geographic Information System Principles Managing GIS Maps

Radio Access Configurator documentation

•

For information on the Radio Access Configurator, see the following documents: • •


Radio Access Configurator Principles Radio Access Configurator Technical Reference Guide


43 (54)


44 (54)



Parameters read and optimised by Optimizer Tools

Appendix A. Parameters read and optimised by Optimizer Tools The tables below lists the parameters in the configuration database that Optimizer reads and optimises. The first table lists the parameters read by Adjacency Management. The second table lists the parameters read and optimised by Frequency Allocation. The third table lists the parameters read and optimised by Service Optimizer.

Table 3.


Parameter in Configuration database

Read by Adjacency Management

Optimised by Adjacency Management

BTS Label

x

Frequency Band In Use

x

InSite Gateway

x

Master BTS For Multi BCF

x

Is Foreign

x

ADCE, ADJW, ADJS, ADJI, ADJG Label

x

Old Status

x

BSC Label

x

BCF BCF Type

x

RNC Label

x

ANTE Antenna bearing



x

45 (54)


Table 3.



Read by Adjacency Management

Optimised by Adjacency Management

SEGMENT 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

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

46 (54)




Table 4.


Parameters read and optimised by Frequency Allocation Optimised by Frequency Allocation


Read by Frequency Allocation

SITE

x

User Label

x

Latitude

x

Longitude

x

GID

x

BSC

x

User Label

x

Version

x

Distinguished Name

x

GID

x

SEGMENT

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

User Label

x

HSN1

x

x

HSN2

x

x

HSN3

x

x


x

x

47 (54)


Table 4.

48 (54)




Optimised by Frequency Allocation

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

Distinguished Name

x

Band

x

SEGMENT 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




Table 4.




Optimised by Frequency Allocation

Initial Frequency

x

x

Channel 0 Type

x

TSC

x

BTS GID

x

GID

x

ADCE

x

Source BTS GID

x

Target BTS GID

x

BTS KPI

x

CS Traffic

x

CS Data Traffic

x

Blocking

x

Table 5.

x

Parameters read and optimised by Service Optimizer


Read by Service Optimizer

Optimised by Service Optimizer

Can be manually optimised in Service Optimizer

BSC BSC_ID

x

Name

x

Downlink Scheduling Step Size (High priority)

x

x

Downlink Scheduling Step Size (Normal priority)

x

x

Downlink Scheduling Step Size (Low priority)

x

x

Uplink Scheduling Step Size (Class 1)

x



49 (54)


Table 5.

Parameters read and optimised by Service Optimizer (Continued)






x

x


x

x


x

x

BTS BTS_ID

x

Name

x

Segment ID

x

GPRS enabled

x

EGPRS enabled

x

Maximum GPRS capacity

x

Dedicated GPRS capacity

x

x

x

Default GPRS capacity

x

x

x

Master BTS

x

NSEI

x

LAC

x

Segment Segment ID

x

TRX TRX ID

x

Name

x

Half-rate support

x

Extended mode

x

GPRS enabled

x

Channel types

x

SGSN SGSN ID

x

Name

x

50 (54)




Table 5.

Parameters read and optimised by Service Optimizer (Continued)





QoS Scheduling Priority (Class 1)

x

x


x

x


x

x


x

x

PAPU PAPU ID

x

Name

x



51 (54)


52 (54)



Index A

P

adjacency list 39 plan 39 adjacency type ADCE 30 ADJG 30 ADJI 30 ADJS 30 ADJW 30 analysis 16, 40 ARP 29 Average Received Power

parameter management performance degradation 23 periodical tuning 16

36

R Radio Resource Management

17

T threshold set 29 Threshold Sets dialog

29

29

B Browser export

37

C Carrier over Interferer Probability CIP 29

29

F Foreign Adjacency

30

I interference matrix

29,

36

K Key performance indicator

23

M manual adjacency management

30

O open interface 36 optimisation algorithm 15 automatic 15 manual 15 process 15, 16 Optimizer parameters 45


©Nokia Corporation Nokia Proprietary and Confidential

53 (54)


54 (54)



Optimizer Principles

Recommend Documents