Optimizer Principles 3.0

Optimizer Principles

DN0196638

2 DN0196638


Id:0900d805807a51ed

The information in this document 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 Siemens Networks customers only for the purposes of the agreement under which the document is submitted, and no part of it may be used, reproduced, modified or transmitted in any form or means without the prior written permission of Nokia Siemens Networks. The documentation has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks 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 are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

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

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark of Nokia 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 2010/8/24. All rights reserved

f Important Notice on Product Safety Elevated voltages are inevitably present at specific points in this electrical equipment. Some of the parts may also have elevated operating temperatures.

Non-observance of these conditions and the safety instructions can result in personal injury or in property damage.

Therefore, only trained and qualified personnel may install and maintain the system.

The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to comply with the applicable safety standards.

The same text in German:

Wichtiger Hinweis zur Produktsicherheit

In elektrischen Anlagen stehen zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert und wartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.

DN0196638

3


Id:0900d805807a51ed

Table of ContentsThis document has 88 pages.

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1 NetAct compatibility and capacity information . . . . . . . . . . . . . . . . . . . . . 81.2 Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Introduction to Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 Radio network optimization process in NetAct. . . . . . . . . . . . . . . . . . . . 142.2 Permission management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.3.1 Map administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.2 Antenna Data Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.3 Task management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3.4 Polygon area management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Basic optimization functionalities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1 Optimizer main user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1.1 Navigator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.1.2 Cell Groups tool view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.3 Scopes tool view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.4 Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.1.5 Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.2 Optimization plans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.3 Network statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.3.1 KPI retrieval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.4 Threshold sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.5 Manual configuration management parameter tuning . . . . . . . . . . . . . . 213.6 Open interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.7 Use Cases tool view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.8 Alarms view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

4 Visualization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

5 LTE support in Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265.1 Visualizing LTE network elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265.2 Optimizer role in LTE autoconfiguration. . . . . . . . . . . . . . . . . . . . . . . . . 265.2.1 Neighbor relation creation for eNBs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 275.2.2 PCI allocation in LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

6 Adjacency management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.1 Adjacency types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.2 Adjacency templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.2.1 Template assignment rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316.3 Adjacency constraint management . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326.3.1 Adjacency constraint import. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336.4 Automated adjacency management . . . . . . . . . . . . . . . . . . . . . . . . . . . 346.4.1 Restrictions for adjacency optimization . . . . . . . . . . . . . . . . . . . . . . . . . 346.4.2 Adjacency creation based on distance and antenna bearing . . . . . . . . 366.4.3 List length reduction in automated adjacency optimization . . . . . . . . . . 38

4 DN0196638


Id:0900d805807a51ed

6.4.4 Distance and measurement based adjacency optimization . . . . . . . . . . 39

7 Capacity analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417.1 Capacity analysis rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427.2 Visualization of capacity analysis results . . . . . . . . . . . . . . . . . . . . . . . . 427.3 Busy hour definitions for capacity analysis . . . . . . . . . . . . . . . . . . . . . . . 437.4 Analysis of KPI trends. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447.5 Abis View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

8 GSM interference matrix generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458.1 BCCH Allocation (BA) lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458.1.1 Temporary BA lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468.1.2 The number of BCCH frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468.1.2.1 Adjacency ranking when using MBAL. . . . . . . . . . . . . . . . . . . . . . . . . . . 468.2 GSM interference measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478.2.1 Measurements needed for Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . 488.2.2 Measurements and NetAct capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488.2.3 Measurement period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498.3 Retrieving measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498.3.1 External and foreign interferers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498.4 Predictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498.4.1 Assumptions used in link loss calculations . . . . . . . . . . . . . . . . . . . . . . . 50

9 WCDMA interference matrix generation . . . . . . . . . . . . . . . . . . . . . . . . . 51

10 Measurement-based automated adjacency optimization . . . . . . . . . . . . 5210.1 Measurements related to automated optimization . . . . . . . . . . . . . . . . . 5210.1.1 GSM interference data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5210.1.2 Detected Set Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5310.2 Adjacency-optimization-related KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . 5310.2.1 Fitness value. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5510.3 WCDMA adjacency KPI retrieval and optimization . . . . . . . . . . . . . . . . . 57

11 Adjacency rotation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

12 Automated frequency planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5912.1 Allocation scopes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6012.1.1 Allocating frequencies for a part of the network . . . . . . . . . . . . . . . . . . . 6012.1.2 Allocating missing frequencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6012.2 Frequency optimization cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6012.2.1 Full allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6112.2.2 Allocating planned objects only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6112.3 Structure of the allocation algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . 6212.3.1 Algorithm Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6212.3.2 Channel Assignment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6212.3.3 Cost Function Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6212.4 User settings to guide the algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . 6312.4.1 Forbidden channels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6312.4.2 Passive intermodulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6312.4.3 Frequency groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6312.4.4 Manual separations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

DN0196638

5


Id:0900d805807a51ed

12.4.5 MA lists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6412.5 BSIC planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6412.6 Interpreting frequency optimization results . . . . . . . . . . . . . . . . . . . . . . 64

13 Primary downlink scrambling code management . . . . . . . . . . . . . . . . . 66

14 Dominance areas in visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6814.1 Calculation area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

15 Multi-PLMN support in Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

16 Multi-vendor support in Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7016.1 Multi-vendor data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7016.2 Multi-vendor visualization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7016.3 Multi vendor GSM Interference Matrix Creation. . . . . . . . . . . . . . . . . . . 7116.4 Multi-vendor restrictions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

17 Where to find more information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

A Appendix Supported KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73A.1 ADCE KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73A.2 ADJG KPIs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73A.3 ADJS KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73A.4 ADJD KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73A.5 ADJI KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73A.6 BTS KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74A.7 Cell KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74A.8 TRX KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75A.9 KPIs shown with the 3G_OPTIMIZER license . . . . . . . . . . . . . . . . . . . . 75A.10 KPIs used in WCDMA capacity analysis . . . . . . . . . . . . . . . . . . . . . . . . 76A.11 KPIs used in GSM capacity analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

B Appendix Parameters read and optimized by Optimizer tools . . . . . . . . 78

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

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

6 DN0196638


Id:0900d805807a51ed

List of FiguresFigure 1 Optimization cycle in NetAct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 2 Optimizer main user interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Figure 3 Collision between LTE cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 4 Confusion in LTE cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 5 The relation between antenna directions and the positions of the source

and destination sector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 6 Antenna factor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 7 Cost function for fitness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Figure 8 Mapping a KPI to the fitness value . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 9 Example of calculating the fitness value . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 10 Basic List and Rotation slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

DN0196638

7


Id:0900d805807a51ed

List of TablesTable 1 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Table 2 Supported CM objects in Optimizer . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 3 ADCE-related KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Table 4 ADJG-related KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Table 5 ADJS-related KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Table 6 ADJI-related KPIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Table 7 Parameters read and optimized by Adjacency Management . . . . . . . . 78Table 8 Parameters read and optimized by Frequency Allocation . . . . . . . . . . 80

8 DN0196638


Id:0900d805807a51ea

About this document

1 About this documentThis document gives an overall picture of Nokia Siemens Networks NetAct Optimizer. It describes the principles behind Optimizer’s functionalities, giving you background infor-mation you may need when using them.

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

1.2 TermsThe following table explains the terms and abbreviations used in this document.

Term Explanation

3GPP Third Generation Partnership Project

AAL2 ATM adaptation layer type 2

Abis Base station controller (BSC) to base transceiver station (BTS) interface

AC Admission Control

ADCE An adjacency between BTSs

ADJG An adjacency from a WCEL to a BTS

ADJI An adjacency between WCELs, inter-frequency

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

ADJLL An adjacency between LNCELs, intra-frequency

ADJS An adjacency between WCELs, intra-frequency

ADJW An adjacency from a BTS to a WCEL

AFP Automatic Frequency Planning

ANTE Antenna object

AMR Adaptive multi-rate speech codec

APN Access Point Name

ARFCN Absolute radio frequency channel number

ARP Average Received Power

ATM Asynchronous transfer mode

AVG Average

BA list (or: BAL) BCCH Allocation List

BCC Base station Color Code

BCCH Broadcast Control Channel

BCF Base Control Function

Table 1 Terms

DN0196638

9

Optimizer Principles About this document

Id:0900d805807a51ea

BSC Base Station Controller

BSIC Base Station Identity Code

BSS Base Station Subsystem

BSSGP BSS GPRS Protocol

BTS Base Transceiver Station

CAC Connection admission control

CDED Current Dedicated GPRS territory

CDEF Current Default Territory Setting

CE Channel Element

CF Channel Finder

C/I Carrier to Interferer Ratio

C/Ia Adjacent Channel Carrier to Interferer Ratio

C/Ic Co-channel Carrier to Interferer Ratio

CID Channel identifier

CIP Carrier over Interferer Probability

CIR Carrier to Interference Power Ratio

CM Configuration Management

COCO Connection configuration object

CS, CSW Circuit Switched

CSV Comma-separated values

DAC Defined Adjacent Cell

DAP Dynamic Abis pool

DCN Data Communication Network

DL Downlink

Ec/No Ratio of energy per modulating bit to the noise spectral density

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

FRBC Frame Relay Bearer Channel

Gb Interface between the base station system and the serving GPRS support node

GID Global identifier

Term Explanation

Table 1 Terms (Cont.)

10 DN0196638


Id:0900d805807a51ea

About this document

GIS Geographic Information System

GPRS General Packet Radio Service

HLR DX HLR

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

IFHO Inter-frequency handover

ID Identifier

IM Interference matrix

IP Internet Protocol

IRP Integration Reference Point

ISHO Inter-system handover

Iub Interface between the radio network controller and the base trans-ceiver station

KPI Key Performance Indicator

LinAS Linux Application Server

LAC Location Area Code

LNCEL LTE Cell

LLC Logical Link Control

LNBTS LTE Base Transceiver Station

LTE Long-term evolution

MAIO Mobile Allocation Index Offset

MAL (or: MA list) Mobile Allocation List

MCC Mobile Country Code

MCS Modulation and coding scheme

MBAL Measurement BCCH Allocation (BA) List

MNC Mobile Network Code

MML Man-machine Language

MRBTS Multi-Radio BTS

MS Mobile Station

Term Explanation


DN0196638

11

Optimizer Principles About this document

Id:0900d805807a51ea

NCC Network Color Code

NCL Neighbor Cell List

NE Network Element

NMS Network Management System

NRT Non-real time

NSVC Network Service Virtual Connection

NSVL Network service virtual link

QoS Quality of Service

PAPU Packet Processing Unit

PCI Physical-layer cell ID

PCU Packet Control Unit

PI Performance Indicator

PLMN Public Land Mobile Network

PM Performance Management

POC Power Control

PS, PSW Packet Switched

RAB Radio Access Bearer

RAC Routing Area Code

RF Radio Frequency

RNC Radio Network Controller

RRM Radio Resource Management

RSCP Received Signal Code Power

RXLEV Received Signal Level

SAC Service Area Code

SACB Service Area Code for Broadcast

SACCH Slow Associated Control Channel, bi-directional

SCA Smart carrier Allocation

SDCCH Stand Alone Dedicated Control Channel

SGSN Serving GPRS Support Node

SIB System Information Block

SMS Short Message Service

TBF Temporary Block Flow

TCH Traffic Channel

TRX Transceiver

TSC Training Sequence Code

TSL Timeslot

Term Explanation


12 DN0196638


Id:0900d805807a51ea

About this document

UARFCN UTRA absolute radio frequency channel number

UE User Equipment

UL Uplink

UTM Universal Transverse Mercator

UMTS Universal Mobile Telecommunications System

UTRA UMTS terrestrial radio access

VCC Virtual Channel Connection

VPC Virtual path connection

WAP Wireless Access Protocol

WBTS WCDMA Base Transceiver Station

WCDMA Wideband Code Division Multiple Access

WCEL WCDMA Cell

Term Explanation


DN0196638

13

Optimizer Principles Introduction to Optimizer

Id:0900d805807a51ea

2 Introduction to OptimizerNetAct Optimizer is used in the statistical network-wide optimization process in NetAct. Optimizer provides visibility to current network behavior by combining actual GSM, WCDMA and LTE network configuration parameters and measured performance statis-tics with advanced visualization and analysis functionality. Parameters can be optimized manually for small changes or automatically by choosing from the range of optimization solutions provided by Optimizer. Optimizer can be used for a single cell or for a whole region, or even across multiple regions.

The result of optimization algorithms can be visualized on a geographical map before downloading the optimization plan to the network. The plan with the changed parame-ters is sent to the NetAct 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 calculations based on raster map - where, for example, the inter-ference 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 automationWith Optimizer, the whole optimization 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 Opti-mizer for the first time, some customizing is needed, such as parameters needed to guide the generation algorithms. Once the parameters are set, the next optimization round is more effortless.

• Self Organizing Networks (SON) solutionNetAct Optimizer is a key component in the Nokia Siemens Networks Self Organiz-ing Networks Suite. The Optimizer for SON solution provides complete element level optimization for real time SON functions.

Optimizer obtains performance data from the NetAct database for BSCs and RNCs. Any preferred external tool can be used for monitoring the performance before and after opti-mization.

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

• GSM automated adjacency optimization • WCDMA automated adjacency optimization • GSM Performance Optimization • WCDMA Performance Optimization • GSM capacity analysis • WCDMA capacity analysis

14 DN0196638


Id:0900d805807a51ea

Introduction to Optimizer

2.1 Radio network optimization process in NetActThe optimization 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 optimize the behavior of new network elements in the network.

Measurements are used for analyzing the network and service performance develop-ment against set targets. A detailed analysis is performed to find the reasons behind decreased performance and to select the right corrective actions. In this phase, the rela-tions between performance indicators and element parameters are analyzed. After the analysis phase, the configuration parameter settings are optimized 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.

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 and operation targets for real time optimization loops, such as radio resource management (RRM) in network elements.

Optimization is also involved when the network is enhanced with new cells or new ser-vices, or changes are made in the service provisioning, and so on. As soon as elements are activated in the network and they can be measured, they can be optimized as well.

2.2 Permission managementOptimizer provides the means to restrict some users from performing certain tasks. When Optimizer has been installed, only users who have the Network Administrator role have all the permissions. For example, only a user with the Network Administrator role or a user with the MANAGE_PUBLIC_PROFILES permission can modify and edit public profiles.

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

For more information on user management in general, see the Managing Users docu-ment.

2.3 AdministrationThere 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.

DN0196638

15

Optimizer Principles Introduction to Optimizer

Id:0900d805807a51ea

2.3.1 Map administrationOptimizer uses Geographic Information System (GIS) to visualize digital map data. The map data needs to be initialized before optimization can be started even if Optimizer is used without any map data. Only maps that are made 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. This means 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. For more infor-mation 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 fast import and syn-chronization 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.

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

2.3.3 Task managementEvery Optimizer user can monitor the ongoing task executions in the Task Management view in Optimizer. You can check task status reports, remove tasks, and view the task configurations during normal operations.

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

2.3.4 Polygon area managementOptimizer 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. For instructions, see Creating and managing polygons in Optimizer Help.

16 DN0196638


Id:0900d805807a51ea

Basic optimization functionalities

3 Basic optimization functionalitiesThe 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.

3.1 Optimizer main user interfaceThe Optimizer main user interface consists of the following panes: the Navigator pane, the Map/Tool pane, the Browser pane, the Scopes pane, and the Cell Groups pane. The tool views open into these panes. If several tool views open into the same pane, each tool view has its own tab that you can close if needed. In addition, the main user interface also contains the main menu bar and the main toolbar.

The availability of a tool view depends on the purchased Optimizer software license. The tool views can be accessed from the Tools menu of the main menu bar or by using thepop-up menus of Navigator, Browser, Map or the Scopes pane.

The practical optimization and analysis work happens always in the context of tool view(s) and with the defined optimization scope (target). The optimization scope is selected from the main window, which opens by default when Optimizer is started. It is the core workspace for object browsing, navigation, and manual optimization. Each tool view may have different scope selected for optimization at the same time.

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

DN0196638

17

Optimizer Principles Basic optimization functionalities

Id:0900d805807a51ea

Figure 2 Optimizer main user interface

1. The Navigator Pane. By default, Navigator opens into this pane. For more informa-tion, see section Navigator.

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

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

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

3.1.1 NavigatorNavigator offers four tree views that are suitable for different optimization purposes: the Default view, the Hardware Topology view, the Adjacency Management view, and the Capacity Management view. For example, you can use a different tree view presenta-tion depending on whether you optimize adjacencies or browse or tune objects of the hardware topology. For more information, see Navigator in Optimizer Help.

18 DN0196638


Id:0900d805807a51ea


3.1.2 Cell Groups tool viewg To be able to manage cell groups, you need either the Optimizer Administrator role

or the Optimizer Provisioning User role assigned to you.

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 Groups tool view and Managing cell groups in Optimizer Help.

The cell groups are arranged in a particular order both in the Cell Groups pane and in the Visualization pane, the most general cell group being highest on the list and the least general cell group lowest on the list. The generality of the cell groups can be modified using the Move cell group up and Move cell group down icons in the Cell Groups pane toolbar. For more information on visualizing cell groups on Map, see Cell groups in Opti-mizer Principles

3.1.3 Scopes tool viewIn the Scopes tool view, you can create, modify, and delete tailored scopes. You can use the tailored scope as a starting point for different optimization tools. Scopes are always global. For more information, see Scopes tool view and for related instructions, see Managing scopes in Optimizer Help.

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

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

With the Browser profile management functionality you can customize the view of the object parameters and the object relations for your own purposes, or you can share your profiles with other users. The Browser profiles support object hierarchy but are always determined according to the parent object. The lower level (child) objects can be freely selected. Browser has a set of default profiles (for each object type) that all users can always use when Optimizer is open. For more information, see Browser in Optimizer Help.

3.2 Optimization plansAll parameter tuning and optimization in Optimizer happens via optimization plans. If you optimize only on top of an actual (live) network configuration, the optimization plans do not depend on NetAct Configurator configuration management plans (planned network

DN0196638

19


Id:0900d805807a51ea

configurations). For more information and instructions, see Managing optimization plans in Optimising a Network Using Optimizer.

Sometimes you also need to take the planned network configurations into account in the optimization process (for example, network due to network roll-out preparation). For this, Optimizer supports the import of planned objects from the Configurator configuration management plan. You can use this feature before starting the actual optimization work. Configurator configuration management plans are made using CM Editor or they are imported from some other tool (such as Plan Editor) using CM Operations Manager.

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

ADCE

ADJG

ADJI

ADJS

ADJD

ADJW

ANTE

BAL

BCF

BSC

Cell

FMCG

FMCI

FMCS

GCAL

HOC

HOPG

HOPI

HOPS

LNBTS

LNCEL

POC

RNC

SGSN

TRX

WBTS

WCAL

WCEL

Table 2 Supported CM objects in Optimizer

20 DN0196638


Id:0900d805807a51ea


In addition, GSM cells are modelled as Cell objects.

For a list of the parameters of these objects that are read and optimized by Optimizer, see Appendix Parameters read and optimized by Optimizer tools.

When you are ready with the optimization plan and the changes can be applied to the actual network, the optimization plan that contains the modifications to the actual network configuration is exported to the Configurator plan database. When the optimi-zation plan has been exported to Configurator, its consistency must be checked. Checking the consistency of the plan and provisioning the plan to the network are done by using CM Analyser and CM Operations Manager. The only exception is instant adja-cency provisioning, in which changes to adjacencies can be provisioned to the network directly from Optimizer. The changes are saved into a plan as usual, but the provisioning phase is automated. For more information on provisioning the plan to the network, see chapter Transferring the optimization plan to the network in Optimising a Network Using Optimizer. If the versions of network elements change in Configurator, this data can be updated in Optimizer by running the metadata refresh process. See Refreshing metadata in Optimizer Help for details.

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

3.3 Network statistics Optimizer has the following tool views where you can view network statistics:

• The Key Performance Indicators tool view • The Interference Matrices for GSM tool view • The Interference Matrices for WCDMA tool view

In addition to these, the Preparing GSM IM creation wizard displays network statistics and also guides the user through all the steps needed in preparing for GSM Interference Matrix creation.

For more information, see Tool views and Preparing GSM IM creation wizard in Opti-mizer Help. See also Managing network statistics in Optimising a Network Using Opti-mizer.

3.3.1 KPI retrievalKey performance indicators (KPI) are the most important indicators of network perfor-mance. KPI reports allow the operator to detect the first signs of performance degrada-tion and prevent the development of critical network problems. KPIs on the regional level can be used for analyzing performance trends, on the RNC level for locating problems, and on the cell 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. Busy hour is the hour when there is most traffic. The time of the busy hour can vary from week to week and from day to day. Optimizer calculates the busy hour on-the-fly for every BTS.

In Optimizer, you can use your own preferred KPIs called custom KPIs for visualizing and analyzing the network performance. You can create custom KPIs and import KPI

DN0196638

21


Id:0900d805807a51ea

values to Optimizer either manually or automatically using a CSV file. The Capacity Analysis tool by default uses NetAct KPIs, but if the custom KPIs describe the network performance better, they can be used in the analysis instead of the default KPIs.

For information on creating custom KPIs see Adding and deleting custom KPIs in Opti-mizer Help. For information on modifying capacity analysis rules see Performing capacity analysis and Rule Threshold Editor dialog in Optimizer Help.

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

3.4 Threshold setsA threshold set is an ordered set of threshold ranges. Threshold sets can be defined for KPIs (Key Performance Indicators) and CM parameters for visualization. Threshold sets are global, which means that they are visible to all users, and therefore, they are not plan specific or user specific.

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

KPIs and CM parameters are classified according to the network hierarchy in the Threshold Sets dialog, where they can be found under corresponding network elements.

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

3.5 Manual configuration management parameter tuningYou can optimize parameters either manually for small, occasional changes or automat-ically by using the optimization algorithms provided by Optimizer. For more information, see Editing network object parameters in Optimising a Network Using Optimizer.

Object parameters can be edited manually in Browser when a plan is open. You can create a profile for the network elements shown in Browser. The profile defines which child elements are shown beneath the profiled element and which parameters and KPIs are shown for these elements. For example, in this way you can select possible child elements related to a 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 Default optimization profiles in Browser. See also chapter Visualization.

3.6 Open interfacesTo complete the optimization process, some additional data handling is required. Opti-mizer contains open interfaces to handle information. In addition, optimization results can be transferred in a table view to external tools, and forbidden channels can be imported from a CSV file to a selected BSC.

Interference Matrix open interfaceOptimizer generates an Interference Matrix based on mobile measurement information collected to Reporter via BSCs. The matrix is used when generating adjacency lists and in allocating frequencies. The measurement-based Interference Matrix is more accurate than any prediction-based Interference Matrix and it enables more accurate frequency optimization. Predicted interference can be generated to new cells or cells where mea-

22 DN0196638


Id:0900d805807a51ea


surements are missing otherwise, for example, because of so called blind spots. Pre-dicted interferences are based on antenna directions and distances between cells. You need to assign a user-specific non-zero priority number for each interference set that is to be included in the Interference Matrix. For instructions, see Creating an interference matrix for GSM in Optimizer Help.

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 you export the interfer-ence matrix, it is saved to a specified location in CSV format. A more accurate descrip-tion of the format can be found in the Interference Matrix Open Interface document.

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

Import of forbidden channelsForbidden channels can be imported from a CSV file into Optimizer for selected BSCs or cells 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 with line feeds. The mode column attributes are the fol-lowing: ADD, REP, and DEL. For more information, see Importing forbidden channels in Optimising a Network Using Optimizer. For instructions, see Importing forbidden channels in Optimizer Help.

Import of intermodulation groups It is possible to import intermodulation groups into Optimizer and to assign the groups to cells. In frequency allocation it is possible to take into account the channels that cause and suffer from intermodulation. Intermodulation is caused by poor antennas or other-wise faulty hardware. For instructions, see Importing intermodulation groups in Fre-quency Allocation Help.

Import of adjacency constraintsYou can import adjacency constraints to Optimizer from a CSV file. For more information on this, see Import of adjacency constraints.

3.7 Use Cases tool viewBy default, the Use Cases tool view opens to the Browser pane (the lower right pane) in the Optimizer user interface. The tool view provides guidance on performing different workflows or use cases. When you click the name of the use case, the use case opens displaying a check list of the different phases the steps you need to follow to complete the workflow. Based on what you want to do, you can choose the desired path by select-ing from different options using check boxes or radio buttons. When you have selected the desired path, the relevant steps are displayed.

DN0196638

23


Id:0900d805807a51ea

3.8 Alarms viewAlarm history visualization for cells helps in identifying possible root causes for poor KPIs (such as a faulty network element) or reasons for deteriorated network quality after optimization. You can view alarms in the Alarms view that opens into Browser. You can select to view all alarms or only active alarms. For related instructions, see Viewing alarms in Optimizer Help.

24 DN0196638


Id:0900d805807a51ea

Visualization

4 VisualizationBrowserIn Browser, you can visualize any CM, PM, and any combination of CM and PM data. The default optimization profiles in Browser serve as examples 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 more information on Browser, see section Browser. For more information on Browser profiles, see Appendix Default optimization profiles in Browser. See also section Manual configuration management parameter tuning.

MapOn Map, you can use the cell visualization settings (Dominance Area, Cell Icon, 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 visualization settings (Interference Line), and the distance visu-alization settings (Distance Color) to visualize CM parameters or KPIs. The Distance KPI settings can show Propagation Delay and Timing Advance which are cell-specific and can be visualized as arcs on the map and as histograms. For instructions, see Visu-alizing Propagation Delay on Map and Visualizing Timing Advance on Map in Optimizer Help. Using Threshold Sets, it is possible to create user-specific threshold profiles. You can also calculate interference based on the interference matrix and visualize it on Map as colored interference lines. In cell and BTS level visualization, Optimizer always uses master BTS values. For more information, see section Map. See also Map in Optimizer Help. For instructions, see Changing an object’s visualization settings and Calculating interference for visualization in Optimizer Help.

Cell groupsCell groups can be used for identifying different cell types on Map. Cell groups can be customized based on object parameters. Cell groups are used as the Default quality indicator (color) in the Visualizations pane for both Cell icon and Dominance area. The cell groups are divided into Actual, Planned and Foreign cell groups. In the Visualization pane legend visible cell groups can be selected by selecting and unselecting the check boxes 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 cells on Map are visualized such that they belong to the active cell group containing the selected quality indicator's parameters. The cells on Map are 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/LNCEL is listed to Browser, this field lists the cell groups of the selected Cell/WCEL/LNCEL. If the Cell/WCEL/LNCEL belongs to multiple cell groups, all those cell groups are listed under the Cell Groups field in Browser.

LTE network elementsFor more information about LTE network element visualization, see LTE support in Opti-mizer.

DN0196638

25

Optimizer Principles Visualization

Id:0900d805807a51ea

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

ProfilesUser-specific visualization settings can be stored in Visualization Profiles, including the KPIs and CM parameters selected for visualization. A new profile is a copy of the current profile, and public profiles are copies of the private profiles. The visualization settings take effect immediately but are not automatically saved. Public profiles can be edited and deleted by other users. For more information and instructions, see Managing a visu-alization profile in Optimizer Help.

26 DN0196638


Id:0900d805807a51ea

LTE support in Optimizer

5 LTE support in Optimizer In Optimizer, the LTE network elements are visualized in the same way as GSM and WCDMA network elements. The LTE support in Optimizer allows the user to visualize and optimize the LTE network. The LTE network elements (site, MRBTS, LNBTS, LNCEL, LCAL, ADJLL and ANTE) are grouped under LTE pseudo controllers (LTE-NW) for easy visualization.

5.1 Visualizing LTE network elementsNavigatorIn Navigator, the Default view, the Hardware Topology view and the Adjacency Manage-ment views support LTE network elements. The network elements are displayed in a hierarchical tree view.

In the Default view, the LTE sites are listed under LTE pseudo controller; each site lists the associated LNBTS. Similarly, LNBTS lists the LNCEL and LNCEL lists the associ-ated Antennas and ADJLL (intra-LTE adjacency).

In the Hardware Topology view, MRBTSs are listed under LTE pseudo controllers. MRBTS lists the associated LNBTSs and LNBTS lists the associated LNCELs. Each LNCEL lists LCAL objects, which in turn list ANTE objects. Sites are not visible in the Hardware Topology view

The Adjacency Management view displays GSM, WCDMA and LTE sites. The sites containing LTE objects list LNCELs, and LNCELs lists ADJLLs.

MapLTE objects on Map are visualized in the same way as objects in GSM and WCDMA networks. LTE objects such as sites, cells, adjacencies and antennas can be located on Map from Navigator and Browser.

In LTE, there can be more than one antenna under a cell. When multiple antennas belonging to one cell are selected in Navigator and located on Map, it locates the asso-ciated cell on Map.

BrowserThe LTE objects can be listed to Browser from Map and Navigator.

AdjacencyLTE network supports intra-LTE adjacency (ADJLL). ADJLLs can be located on Map, viewed in Navigator and listed to Browser.

5.2 Optimizer role in LTE autoconfigurationWhen an eNB is commissioned into the network, autoconfiguration of that eNB is trig-gered automatically. During autoconfiguration, Optimizer is invoked by NetAct Configu-rator through Configurator Workflow Engine to create neighbor relations for eNBs and to allocate PCIs to the cells of eNB.

For more information, refer to eNB auto configuration phase in Configuring LTE Flexi Multiradio BTS Using Auto Connection and Auto Configuration.

DN0196638

27

Optimizer Principles LTE support in Optimizer

Id:0900d805807a51ea

5.2.1 Neighbor relation creation for eNBs During autoconfiguration, neighbor relation for eNBs is created according to user policies set in the LTE Adjacency Management and the Adjacency Optimization in the Preferences dialog. Along with the parameters, priority order is also considered when creating neighbor eNB lists. From the priorities between all cell pairs hosted by the source eNB and the candidate target neighboring eNB, the maximum inter-cell priority is used as the inter-LNBTS priority.

For information on the user policies for neighbor relation creation, refer to Preferences dialog in Optimizer Help. For more information about the priority function, see Adjacency creation based on distance and antenna bearing.

If enough suitable neighboring eNBs are found within the given search distance, the given maximum number of neighboring eNBs are added to the neighbor list in decreas-ing inter-eNB priority order. If the number of suitable neighboring eNBs found within the search distance fulfills the given minimum and maximum number of neighboring eNBs, all the found neighboring eNBs are added to the list.

If the minimum number of neighboring eNBs is not available within the specified search distance, the search distance is increased until the minimum number of eNBs can be found. The search distance is allowed to increase until the given maximum search distance is reached. If the minimum number of neighboring eNBs are not found with the maximum search distance, the algorithm stops and returns only the neighboring eNBs that are found within the maximum search distance, even if the number is smaller than the required minimum number of neighboring eNBs.

g If no antenna is found for an LNCEL within the search distance or if an antenna bearing parameter is invalid, an omni antenna and its respective parameters are used as default in the priority calculation for that LNCEL.

The neighbor eNB list is created for an LNBTS associated to a site. If an LNBTS is not associated to any site, that LNBTS is not considered in the neighbor eNB list creation. If the sites are in the same location, the Same Site Distance Limit Used [m] option is considered and the adjacencies are searched inside the Same Site Distance Limit and added in a priority order.

g Neighbors are always bidirectional and never deleted by Optimizer. A neighbor can be added only if both source and target eNBs have space in the neighbor lists. For new eNBs the parameter Maximum number of neighboring eNBs is followed. For other eNBs the absolute maximum 32 is followed. It is important to use a small enough value for Maximum number of neighboring eNBs to avoid having full lists too early. The lists should have space for new neighbors if new eNBs near or in the middle of existing eNBs are added in the future. In addition to this, quite a tight search distance can be used. If new eNBs are added in the middle of actual eNBs that already have full neighbor lists, either no neighbors are added or - in the best case, if a large search distance is used - only poor neighbors might be added. Also in this situation the search distance is exceeded to fullfill the Minimum number of neighboring eNBs parameter, and even more far away neighbors might be added to the list.

During the creation of the neighbor eNB list, feedback messages are given to the Con-figurator Workflow Engine.

28 DN0196638


Id:0900d805807a51ea


5.2.2 PCI allocation in LTEIn LTE, each cell has an identifier called Physical-layer Cell Identification (PCI). The allo-cation of PCIs is done as part of autoconfiguration in LTE. During the allocation different PCI allocation rules are checked in the network. They are:

– Collision-free and confusion-free allocation– Minimum PCI reuse distance – PCI allocation group-wise

Initially the collision-free and confusion-free PCIs are checked in the network. The avail-able PCIs from the collision-free and confusion-free rule are considered in the minimum PCI reuse distance rule. The PCIs available after collision-free and confusion-free rule, and fulfilling the minimum PCI reuse distance rule are considered in the group-wise allo-cation rule.

The following section gives a brief description of the PCI allocation rules.

Collision-free and confusion-free PCI allocationWhen a cell and its neighbor cell have the same PCI value, it results in a collision. The figure below illustrates a collision between neighbor cells, where Cell A and Cell B have the same PCI value X.

Figure 3 Collision between LTE cells

Similarly, if a cell has neighbor cells with the same PCI values, it results in a confusion. In the Figure below, Cell B is confused because Cell B has Cell A and Cell C as neighbor cells with the same PCI value X.

Figure 4 Confusion in LTE cells

During the autoconfiguration process, collision-free and confusion-free PCI values are allocated to the cells under the requested LNBTS.

Additionally to the collision-free and confusion-free allocation, the user can select to optimize the reuse distance of PCI values and/or to allocate PCI values from the same or consecutive PCI groups to the cells hosted by the same eNBs.

g For collision-free and confusion-free PCI allocation it might be necessary to change the PCI values of actual existing cells.

Minimum PCI reuse distance ruleAfter collision-free and confusion-free allocation, the available PCIs in the network are considered in the minimum PCI reuse distance rule. In this rule the PCIs are checked

DN0196638

29

Optimizer Principles LTE support in Optimizer

Id:0900d805807a51ea

for reuse, that is, the PCIs can be reused above a certain distance (minimum PCI reuse distance) in the network.

If there are PCIs available for reuse above the minimum PCI reuse distance, the PCIs will be allocated to the cells of an LNBTS, and if there are no PCIs available for reuse, the minimum PCI reuse distance is reduced iteratively.

During iteration, the PCIs are checked for the reuse. If there are PCIs for reuse, the iter-ation stops and PCIs are allocated to the cells. If no PCI valuess are available within the reuse distance, the iteration continues till it reaches the number of iterations in the Number of iterations for reduction field or till the value of Minimum PCI reuse distance field reaches the threshold distance mentioned in the Threshold for stopping iterations field. For information on all the above fields, refer to the PCI Management option in the Preferences dialog in Optimizer Help.

g If the minimum PCI reuse distance or the number of iterations for reduction has been reached without a valid PCI allocation, then the rule is violated and the previous collision-free and confusion-free allocation is accepted.

Group-wise PCI allocation ruleThree consecutive PCI values starting with the multiple of three form a PCI group, for example, the PCI values (0, 1, 2) form a group and the next consecutive PCI values (3, 4, 5) form an another group, similarly the subsequent groups are formed till the number of PCIs are available in the network. In group-wise PCI allocation, the PCIs from the same group are tried to be allocated to the cells of an LNBTS.

g The minimum PCI reuse distance rule is mandatory after collision-free and confu-sion-free rule, where as, the PCI allocation group-wise rule is triggered only if the Allocate PCIs group-wise to LNBTSs option is set to true in the Preferences dialog in Optimizer Help.

During group-wise PCI allocation, PCIs available after checking the collision-free and confusion-free rule and fulfiling the minimum PCI reuse distance rule are allocated. The available PCIs from the rule could be from the same group or from the different groups. Based on the available PCI values, the PCI allocation group-wise rule is executed accordingly as follows:

• If there are PCIs available after collision-free and confusion-free rule, fulfilling the minimum PCI reuse distance rule and if the PCIs are from the same group, then those PCIs are allocated to the LNBTS through the PCI allocation group-wise rule.

• If there are no PCIs available from the same group after collision-free and confusion-free rules fulfilling the minimum PCI reuse distance rule, then the PCI allocation group-wise rule is ignored, and the allocation is done based on the minimum PCI reuse distance rule.

• If there are no PCIs available from the minimum PCI reuse distance rule, then the PCIs that were available to achieve the collision-free and confusion-free allocation are considered by the PCI allocation group-wise rule. If those PCIs belong to the same group, then the PCIs are allocated to the cells of an LNBTS through the PCI allocation group-wise rule.

• If there are no PCIs from the minimum PCI reuse distance rule and if the PCIs that are available after the collision-free and confusion-free allocation are not from same group, then the minimum PCI reuse distance rule and the PCI allocation group-wise rule is ignored. In that case, the PCIs that were available to achieve the collision-free and confusion-free allocation are considered and allocated to the cells of an LNBTS.

30 DN0196638


Id:0900d805807a51ea


g If the number of cells in an LNBTS is below three, the PCIs for the existing cells are allocated from a group and the remaining PCIs of that group will be discarded.

DN0196638

31

Optimizer Principles Adjacency management

Id:0900d805807a51ea

6 Adjacency managementAdjacencies define the relationship to allow mobile call handover (HO) between cells. Adjacencies can be created, modified, and deleted manually either on Map, in Naviga-tor, or in Browser. For instructions, see Optimizing adjacencies in Optimising a Network Using Optimizer. For information on measurement-based automated adjacency optimi-zation, see chapter Measurement-based automated adjacency optimization.

6.1 Adjacency typesDepending on the type of cells for which the relationship is defined, there are 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 (Soft Handover Based on

Detected Set Reporting). • ADJI, an adjacency between WCELs, inter-frequency • ADJLL, an intra-LTE adjacency

g Creation, modification, deletion and provisioning of ADJLL is not supported.

All adjacency types can be displayed on Map at the same time or separately. The adja-cencies may have different coloring depending on their type. The direction of the adja-cency is also visualized. Adjacency state (deleted/actual/planned/in provision) can also be used as filtering criteria of the visible objects. All these settings can be customized per user. An adjacency can be visible on Map only if the target cells are visible.

g 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).

6.2 Adjacency templatesOptimizer 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 per cluster, 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.

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

6.2.1 Template assignment rulesThere are two kinds of adjacency template assignment rules: cluster-specific assign-ment rules and controller-specific rules. The rules consist of source and target catego-ries. The source and target categories can consist of the following items:

32 DN0196638


Id:0900d805807a51ea

Adjacency management

• GSM • Cell Types. The value of the Cell Type parameter in BTS is mapped as one cat-

egory. • 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. The template assignment can be seen in Browser in the Original Template column. Planned template assignment can be used if 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 this case, the AND operation is applied between the rules. The rule is applicable to adjacency if both the source and the target categories match with the source and target cell data. If there are several applicable rules for adjacency, the following priorities are used:

• The controller-specific rule is always more important than the cluster-specific assignment rule.

• The source category is more important than the target category when there is the same priority level of categories in the source and target categories.

• In general, rules are applied with priority from the more precise to more 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 assignment rules, see Managing template assignment rules in Optimizer Help.

6.3 Adjacency constraint managementThere are adjacency constraints only in actuals as globals. Adjacency constraints are not network objects that could be provisioned. You can create two types of adjacency constraints in Optimizer: mandatory and forbidden adjacency constraints.

The automated adjacency creation algorithms always check adjacency constraints when adjacencies are deleted or created. If there are forbidden adjacency constraints, the adjacency cannot be created or it can be deleted by the automated adjacency opti-mization. If there are mandatory adjacency constraints, the adjacency cannot be deleted or it can be created (if it does not exist) by the automated adjacency optimization.

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

DN0196638

33


Id:0900d805807a51ea

For instructions on managing adjacency constraints, see Managing adjacency con-straints in Optimising a Network Using Optimizer, and Creating adjacency constraints and Deleting adjacency constraints in Optimizer Help.

6.3.1 Adjacency constraint importYou can import adjacency constraints to Optimizer from a CSV file. You can import con-straints to an empty database, or to a database which already contains constraints. The import operation overwrites existing constraints in the database with the same source and target cell identification. Furthermore, if the import file contains overlapping con-straints with the same source and target identification, only the last constraint is imported. The constraints to be imported can be defined as mandatory, forbidden, or removed (in other words, the old constraint is removed from the database).

In Adjacency Constraint Import, the identification of cells is as follows:

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 the columns have headers in this order:

Parameter name,Type,Possible values:ADJACENCY_TYPE, string, [ADCE, ADJW, ADJS,ADJI, ADJG]S_MCC, string S_MNC, stringS_RNC_ID, string, Empty for GSM CellsS_GSM_LAC, integer, Empty for WCDMA CellsS_CELL_CI, integerT_MCC, stringT_MNC, stringT_RNC_ID, string, Empty for GSM CellsT_GSM_LAC, integer, Empty for WCDMA CellsT_CELL_CI, integerACTION, string, [MANDATORY, FORBIDDEN, REMOVE]INFO, string, [the range is limited by the databasecolumn to less than 512 characters], Note that if thelength 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 of GSM Cells, the *_RNC ID column can be empty. In case of WCDMA Cells the *_GSM_LAC columns can be empty. In the following, an example of the 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,

34 DN0196638


Id:0900d805807a51ea


244,5,4,,11891,244,5,,9112,62076,MANDATORY,Must be mandatoryADCE,244,5,,9112,63265,244,5,,9112,13,MANDATORY,Must bemandatory ADJS,244,5,4,,11733,244,5,4,,11732,FORBIDDEN,Shouldnot 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 made visible on Map, in Browser and in the Adjacency Optimization tool in Adjacency Browser. On Map the info text is only visible as a tooltip of a constraint object but not with adjacency. In Browser, info text is visible only with constraint object. In the Adjacency Optimization tool, the info text is visible with the adjacency object itself.

In Adjacency Optimization, rules can be run after import to delete adjacencies where for-bidden adjacency constraint exist and to create adjacencies where mandatory adja-cency constraints exist.

☞ In Adjacency Optimization Tool in Adjacency Browser there are all columns avail-able for import. Data can be copied to a file which can be imported.

For instructions, see Importing adjacency constraints in Optimizer Help.

6.4 Automated adjacency managementOptimizer provides two methods for creating adjacencies automatically:

• Adjacency creation based on distance and antenna direction for GSM, WCDMA and LTE, and also between the systems for GSM and WCDMA.

• Measurement-based adjacency creation and deletion for GSM, WCDMA and between the systems for GSM and WCDMA. For more information, see chapter Measurement-based automated adjacency optimization.

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

6.4.1 Restrictions for adjacency optimizationIn unidirectional adjacency creation, an adjacency is created only if all thresholds are met, that is, each optimization value is better than the corresponding threshold. An adja-cency is deleted if all of the thresholds are not met, that is, at least one optimization value is worse than the corresponding threshold. Optimization value means KPI value, dis-tance, or any value that defines how good an adjacency is.

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

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

Restrictions controllable by the userBy default, the optimization algorithm does not create or delete adjacencies (bi-direc-tional or unidirectional) to an Indoor Cell, but the user can enable creation or deletion in the user interface. A cell is defined as indoor if any of the antennas related to the cell has an indoor antenna. An antenna is indoor if the user defined state parameter contains the string indoor. The string is case insensitive. There can be other strings in

DN0196638

35


Id:0900d805807a51ea

the parameter. In/Out Gateway Cells should not be defined as indoor cells if they are wanted to be included in optimization without enabling optimization of all indoor cells.

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

RU10 (3GPP R6, Correction target RU10: RAN1323 Extension of SIB11 (SIB11bis) implements SIB11bis which enables the SIB11+SIB11bis to accommodate all 96 cells and solves the contradiction in the earlier specification. SIB11bis is included as standard feature in RU10. It should be noted that only R6 and later UEs are capable of decoding SIB11bis. RAN Parameters AdjsSIB, AdjiSIB and AdjgSIB can be used to disable the transmission of a neighbor info in SIB11/12. In Addition, in RU10 RNC the neighbors 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 is used for con-nected 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 BTSs in bands EGSM900+GSM1800.

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

• BTS in 850 band can have maximum 18 adjacencies to BTSs in 1900 band. • BTS in 1900 band can have maximum 22 adjacencies to BTSs in 850 band.

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

Restrictions uncontrollable by the userThe cases when adjacencies are never created and/or deleted by the optimization algo-rithm are the following:

• Adjacency optimization does not delete adjacencies that have a mandatory adja-cency constraint. Mandatory adjacency constraints are defined on Map or in Browser, and you can also import mandatory and forbidden constraints using a CSV file.

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

Collision typesIn addition to restrictions for the algorithm, also collisions can occur in adjacency optimi-zation. The collisions types are the following:

• Same BCCH in source and target cells and Same BCCH BSIC combination 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 same BCCH 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

36 DN0196638


Id:0900d805807a51ea


• The ADJS NCL has more than one cell with the same scrambling code-UARFCN combination or the source and the target cell have the same scram-bling code-UARFCN combination.

• 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 SHO ADJS and ADJI

NCL • The combined ADJS and ADJI NCL in three cells’ SHO has more than one cell

with the same scrambling code-UARFCN combination (in other words, this means neighbors and neighbor’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 Frequency Allocation is per-formed after Adjacency Optimization. If collisions are created for ADJSs, it is recom-mended that Scrambling Code Allocation is performed after Adjacency Optimization. Collisions created for ADJI, ADJW, and ADJG can be corrected only manually in Opti-mizer.

If ADJSs or ADJG are to be created to several rotation plans, all the created adjacencies in all the rotation plans are checked. For example, if collisions are not allowed, all the created adjacencies can be in the network at the same time without new collisions occurring.

When user equipment is connected to two or three WCDMA cells, the neighbor cell lists of the connected cells are combined. Collision checking is based on adjacency informa-tion and assumes that any combination of the combined neighbor cell lists is possible in the user equipment. As collision checks are theoretical, all combinations of combined neighbor cell lists are not instantiated in practise, an so all collisions are not causing problems from the user equipment point of view. Removing obsolete long distance adja-cencies is important as they limit the adjacency creation by causing theoretical collision situations. The collision creation restrictions "Same Scrambling Code and UARFCN Combination in 3 Cells SHO ADJS and ADJI NCL" and "Same BCCH BSIC combination in 3 Cells SHO ADJG NCL" may be too tight in some cases and collision creation might be enabled. However, in cases when a collision is created, it is recommended that the result is verified in the Scrambling Code Managament tool and on Map.

g No scrambling code collision checking is done for ADJD adjacencies.

6.4.2 Adjacency creation based on distance and antenna bearing Adjacency creation based on distance and antenna direction allows creating and deleting of adjacencies by using distance and/or bearing as criteria. This method can be used for initial adjacency creation when the network objects are not yet in the air, but it

DN0196638

37


Id:0900d805807a51ea

provides also means for fast mass creation or deletion of actual objects. This is useful, especially when managing WCDMA adjacencies.

Creating adjacencies based on distance and antenna bearing includes the following steps:

1. User defines the maximum distance D for the adjacency to be created.2. User defines the maximum angle q (Maximum Theta Angle). In the following figure,

theta1 is the angle between the antenna bearing and the direction of the vector joining the source and destination sites, similar to theta2. Theta angle is theta1 + theta2. Theta1 and theta2 are always positive (>=0).

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

3. The algorithm creates adjacencies between all sectors that belong to 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 creates outgoing adjacency from that sector to all sectors within the range.

5. The highest priority is assigned to each adjacency created in Step 3, while adjacen-cies created in Step 4 are prioritised according to the value of the adjacency creation factor P. The higher the value of P, the higher the priority of the adjacency in that site.P= (exp(-N * D/Dmax) ) (O1 * O2 * A)In the Priority equation, • N is the propagation constant with default 2 • D is the distance between sites • Dmax is the maximum distance. In case of autoconfiguration, neighbor creation

Dmax is defined by an option Search Distance • O1 is the Omni Antenna Correction Factor for the source cell • O2 is the Omni Antenna Correction Factor for the target cell • A is Antenna FactorThe higher the value of P the higher the priority of the adjacency is in that sight.Omni Antenna Correction Factor (O1 or O2) is 1 if the antenna is not omni. Omni Antennas have smaller antenna gain than normal antennas. Therefore, using the Omni Antenna Correction Factor, we get more equal results. The smaller the value,

(X2,Y2)

(X1,Y1)

1

2d 1

2

38 DN0196638


Id:0900d805807a51ea


the smaller the priority value when the source and/or target cell's antenna is omni. The default is 0.8.When the source or the target cell have multiple antennas/power divider, the priority is calculated for all antenna combinations. The antenna combination which results highest Priority is used.

Figure 6 Antenna factorIn the antenna factor A, • F (Antenna Correction Factor) has the range [0…1]. 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││g The -/+ or -/+ sign is used if Theta1 and Theta2 are on the same/different

side of the connecting line between the sites. The Antenna Correction Factor and Omni Antenna Correction Factor can be adjusted in the Preferences dialog under Adjacency Optimization. For instruc-tions, see Managing preferences in Optimizer Help.

6.4.3 List length reduction in automated adjacency optimizationAutomated 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. List length reduction is applied only to the cells which are in the optimization scope.

Adjacency priorities is defined as follows:

If no measurements are involved, Priority here means distance and antenna angle based priority. This applies for all adjacency types.

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

• For existing remaining adjacencies (ACTUAL, UPDATED) • ADCE: The sum of HO Attempts in outgoing and incoming directions [N] • ADJS: The sum of SHO Attempts in outgoing and incoming directions [N] • ADJG: The sum of ISHO Attempts in outgoing and incoming directions [N] • ADJI: The sum of IFHO Attempts in outgoing and incoming directions [N]

• 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 list lengths in Options → Preferences → Adjacency Management → Maximum Amount of ADxx and the adjacency type specific Max list lengths defined in the Adjacency Optimization tool view (Common tab → Adjacency list lengths) are used, and the smaller one is selected. In the case of ADCE, a cell specific BTS Constraint "Maximum length of ADCE Adjacency List" is also considered. If a BTS Constraint is assigned to a BTS, the list

DN0196638

39


Id:0900d805807a51ea

length limits in the BTS Constraint are used even if the restriction in the BTS Constraint is less strict than the restrictions set in the Common tab of Adjacency Optimization.

The algorithm to reduce the list length is as follows:

1. If adjacency type is selected for creation, remove the poorest CREATED adjacen-cies from the plan, until the NCL length is smaller than the maximum NCL length.

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

6.4.4 Distance and measurement based adjacency optimizationAdjacencies can be optimized based on distance only (see cases 1-3 below), or mea-surements can be used (see case 4).

If both deletion and creation of adjacencies are selected and no measurements are used, the creation can undelete adjacencies and deletion can remove created adjacen-cies from the plan. Undeletion is done using the parameters under the Creation tab in the Adjacency Optimization tool view. Removing of adjacencies from the plan is done based on parameters under the Deletion tab in the Adjacency Optimization tool view. In this case created and undeleted adjacencies are optimized at the same time, so that an optimal solution is found (see Case 3 below). For more information, see Adjacency Opti-mization tool view in Optimizer Help.

Four different cases of distance based adjacency optimization are described 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 are used : • 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 adjacen-

cies 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

40 DN0196638


Id:0900d805807a51ea


• If creation is used, new adjacencies are created based on creation thresholds • If creation is used, list length reduction is done for CREATED adjacencies • If deletion is used, list length reduction is done for ACTUAL and UPDATED adja-

cencies

DN0196638

41

Optimizer Principles Capacity analysis

Id:0900d805807a51ea

7 Capacity analysisThe target of thecapacity analysis is to see how the current capacity is used in different interfaces or network elements.

The interfaces used in the GSM capacity analysis as well as the key resources when monitoring each interface are listed below:

• Radio interface– GPRS maximum capacity in BTS– GPRS default capacity in BTS– GPRS dedicated capacity in BTS

• Abis interface– Dynamic Abis pool size

• PCU interface– UL congestion– DL congestion– Modulation and coding scheme (MCS) limitations in Radio interface due to PCU

capacity– Territory upgrade rejections due to PCU capacity

• Gb interface– Gb link utilization– Gb link size

The interfaces used in the WCDMA capacity analysis as well as the key resources when monitoring each interface are listed below:

• Radio interface– Downlink WBTS power– Uplink received interference– Code tree utilization

• WBTS interface– Channel element shortage

• Iub interface ATM based Iub:– Traffic load / capacity utilization– Connection admission control (CAC) resource reservation (DL)– Channel identifier (CID) utilization (number of AAL2 connections) per VCC IP based route Iub:– Accessibility and capacity reservation level

In the analysis Key Performance Indicators (KPIs) are compared to user-definable thresholds. As a result, the Capacity Analyzer detects possible capacity shortages and advises the user on how to improve the situation. The required KPIs have to be retrieved from the NetAct database to Optimize before the analysis is started. KPIs can be imported automatically or manually from the NetAct database or manually via a CSV interface. Capacity analysis can be done with KPI data from one or several days. When several days are analyzed, the analysis uses statistical validity to find out the general performance situation. With the statistical analysis you can specify how many days of the days analyzed should be problematic before the results show a capacity shortage. The number of problem days can also be defined as a percentage of the days analyzed.

42 DN0196638


Id:0900d805807a51ea

Capacity analysis

If you make changes in the network configuration, capacity analysis can be used to see how the changes affect the network performance. After making changes it is recom-mended that you measure the network for at least five days in order to see the effect of the changes properly in the KPI values. If the capacity is increased in one point in the network, the performance bottleneck may disappear from that point but it may move to some other part of the network. To avoid this, it is recommended that you analyze all the interfaces and elements in the chain to see the overall situation in the network before you make any changes.

For more information, see Performing capacity analysis in Optimizer Help and Analyzing network capacity in Optimising a Network using Optimizer.

7.1 Capacity analysis rules Each interface or element in the network has a defined set of rules, and WCDMA and GSM have their own rule sets. Rules can also be used one at a time. Each rule contains one or several logical rules where the KPIs are checked against the thresholds. The rule body is fixed but you can change the KPIs, operands and threshold values of the rule to better fit the network which is analyzed. You can for example use your own, customized KPIs that you have imported with CSV import. Operands can be changed, for example, if the logic of the selected KPI is opposite to the original one. Default thresholds are general defaults defined by network optimization experts to fit Nokia Siemens Networks KPIs, but, especially if customer specific KPIs are used, the thresholds can be changed. Default thresholds can always be reverted.

The default rules have been designed for the Daily Busy Hour summarization level, but most of the rules can also be run using the Daily summarization level. If the Daily sum-marization level is used, the thresholds for the rules need to be adjusted.

For more information about the capacity analysis rules and customized KPIs, see the Capacity Analyzer tool view, Rule Threshold Editor dialog and Adding and deleting custom KPIs in Optimizer Help.

7.2 Visualization of capacity analysis results You can analyze network interfaces or elements one by one or several at the same time. You can select to show the analysis results on Map, in Browser, or both.

When Map is selected, you can define how the results are visualized on Map. Results can be shown per interface or element analysis result or even per rule result in different visualization channels: Cell icon, Cell dominance area, Cell dominance area border, or Site icon as colors.

When you select to see results in Browser, the results are shown per interface in separate Browser tabs. Each tab contains a Browser representation of the results of that interface. In each tab the interface-specific results are shown using a Browser profile. The profile used in each tab is specific to the base element used in Browser for the inter-face result presentation. The profile also shows essential configuration parameters and KPIs that are used in the analysis as well as solution notes for the rules. The KPI values follow the date selection made in the Optimizer main window. You can modify the con-figuration parameters and save them to a plan, which can be provisioned to the network. A Browser profile with its data can be copied to an Excel sheet for further investigation.

DN0196638

43

Optimizer Principles Capacity analysis

Id:0900d805807a51ea

More information about the visualization of analysis results can be found in Viewing capacity analysis results in Optimizer Help. For more information about capacity analysis profiles in Browser, see Appendix Default optimization profiles in Browser.

7.3 Busy hour definitions for capacity analysisThis section describes how the busy hour (BH) for capacity analysis is defined in Opti-mizer.

WCDMA

• Radio rules for WCDMA use the NetAct busy hour definitions. • WBTS busy hour: max(AVG_USED_CE_DL + AVG_USED_CE_UL +

AVG_HSUPA_CE_UL + AVG_HSUPA_CE_DL) • ATM based Iub: max RNC_753a, where the actual KPI value is calculated as a sum

of all user plane and signaling link VCC values of this KPI • IP Route Based Iub: max RNC_1635a

GSM

• Radio interface: CS busy hour and PS busy hour.– CS busy hour criteria: Max(ave_busy_tch)– PS busy hour criteria: Actual DL data throughput (blocks)

The number of blocks is equivalent to 1 timeslot full use in each BTS of the area.=sum(a.rlc_data_blocks_dl_cs1 + a.rlc_data_blocks_dl_cs2 + a.rlc_mac_cntrl_blocks_dl + a.RETRA_RLC_DATA_BLOCKS_DL_CS1 + a.RETRA_RLC_DATA_BLOCKS_DL_CS2) +sum over MCS1..6, 11..12 of (b.dl_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_dl+ b.dl_rlc_blocks_in_unack_mode) +sum over mcs7..9 of (b.dl_rlc_blocks_in_ack_mode+b.retrans_rlc_data_blocks_dl+ b.dl_rlc_blocks_in_unack_mode)/2--------------------------------------------------------- sum(period_duration*60)*50 ;50 blocks /sec /tsl

• Abis interface: PS busy hour. Busy hour criteria: max(DL_EDAP_ALLOATION_REQUEST, UL_EDAP_ALLOATION_REQUEST)Calculated from the p_nbsc_dynamic_abis table, which is a DAP level measure-ment.

• PCU element: PS busy hour. Busy hour criteria: max(DL_EDAP_ALLOATION_REQUEST, UL_EDAP_ALLOATION_REQUEST)Calculated from the p_nbsc_dynamic_abis table, which is a DAP level measure-ment and summarized to PCU.

44 DN0196638


Id:0900d805807a51ea

Capacity analysis

• Gb interface, Frame Relay: PS busy hour. Busy hour criteria: max(DL_EDAP_ALLOATION_REQUEST, UL_EDAP_ALLOATION_REQUEST)Calculated from the p_nbsc_dynamic_abis table, which is a DAP level measure-ment and summarized to PCU.

• Gb interface, IP: PS busy hour. Busy hour criteria: max(PAYLOAD_SENT_TO_SGSN_IN_KB + PAYLOAD_RCVD_FROM_SGSN_IN_KB)Calculated from the P_NBSC_GB_OVER_IP table, which is an NSE level measure-ment and summarized to NSVL level.

7.4 Analysis of KPI trendsKPI behavior can also be analyzed as a trend. In Optimizer's KPI Trends tool view you can see several days' KPI values in the same view as well as several KPIs in the view at the same time. You can also draw a trend line to show KPI values to be expected in the future. For related instructions, see Creating KPI trend charts in Optimizer Help.

7.5 Abis ViewThe Pulse Code Modulation (PCM) line timeslot configuration of various network elements can be checked using the Abis View dialog. The Abis View shows the PCM timeslots and sub-slots with information of the timeslot usage. For related instructions, see Viewing the Abis configuration in Optimizer Help.

DN0196638

45

Optimizer Principles GSM interference matrix generation

Id:0900d805807a51ea

8 GSM interference matrix generationInterference Matrix (IM), which is primarily based on interference-related measurements but which can also be complemented with predictions, provides interference data for adjacency management and frequency planning -related algorithms.

An interference matrix represents the interference relations between cells if they use the same frequency (co-channel) or adjacent frequency (adjacent channel). 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 Matrix for Nokia NEs are created from the mobile measure-ment reports (MMR) that have been collected from a live network. For Siemens, mea-surements are in binary format and for other vendors measurements are in CSV file format.

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

It is recommended to use Optimizer with dedicated BCCH frequencies. The BCCH block does not need to be a continuous band: you can also use several slots if they are dedi-cated to BCCH use only. It is possible to measure a mixed band as well, but that requires more manual work. Note that in the case of dedicated BCCH, the number of TCH fre-quencies is not limited and even if only the BCCHs are measured, the inter-cell depen-dency is also applicable to TCH frequencies. As the signal strengths of the surrounding cells are studied in the measurement period, the information is also valid for TCH fre-quencies. In the frequency allocation phase, different interference thresholds are given to TCH frequencies and BCCHs, thus achieving tighter reuse for TCH frequencies with a higher level of expected interference.

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

8.1 BCCH Allocation (BA) listsNormally, the BCCH Allocation (BA) lists of a BTS contain BCCH frequencies of the adjacent cells. During the measurements, the BA lists must contain every BCCH fre-quency used in the network. The BA lists must be changed for every BTS in the BSC before measurements are started.

46 DN0196638


Id:0900d805807a51ea

GSM interference matrix generation

8.1.1 Temporary BA listsThe idea of having a temporary BA list for measurements is to have a list of the BCCHs of all the cells, including cells that are not defined as neighbors. Before connecting to a neighbor cell, mobile phones first listen to the BCCH in the BA list to verify sufficient signal strength and quality. By adding all possible BCCHs to the BA list for the duration of the measurement period and measuring all surrounding cells, all the required data for correct adjacencies and frequency planning can be collected. If there are fewer than 32 BCCHs, both the current and possible adjacent cell BCCHs are included in the BA list.

The temporary BA list is defined for the measurement period and you need to return the original BA list to the network once the measurements are completed. You can change the BA list as well as measurement scheduling using MML commands.

To enable the BTS to receive the BA list, the double BCCH Allocation feature must be activated in the BTS. Furthermore, configuration should not be changed during the mea-surement period because then the measurements no longer correspond to reality. The original BA list together with other parameter data is returned when the measurements are ready.

8.1.2 The number of BCCH frequenciesThe procedure for creating temporary BA lists depends on the number of BCCH fre-quencies:

• If there are 32 or fewer BCCH frequencies, the plan for the BA list changes can be created in CM Editor or in Optimizer using the Preparing GSM IM creation wizard. For instructions, see Activating measurements with 32 or fewer BCCH frequencies in Optimising a Network Using Optimizer. You can set the common restriction for the maximum amount of ADCEs in the Pref-erences dialog under Adjacency Management. For instructions, see Managing pref-erences in Optimizer Help. You can also set the same parameter optimization case specifically in the Common tab of the Adjacency Optimization tool view. For more information, see Adjacency Optimization tool view in Optimizer Help.

• If there are more than 32 BCCH frequencies in the network, the measurements need to be run in several cycles of equal length but with different BA lists. Rotating fre-quencies in BA lists can be done in the following ways: • automatically in BSC S11 (or newer) by using the Measurement BA List (MBAL)

feature and Total FEP measurements, or • using the BAL Rotation tool for rotation of BA lists in S10.5 (or newer) and with

CF and DAC measurementsFor instructions, see Using the BAL Rotation tool for measuring more than 32 fre-quencies or Using MBAL and total FEP measurement of BSC S11 to measure more than 32 frequencies in Optimising a Network Using Optimizer.

8.1.2.1 Adjacency ranking when using MBAL Adjacency ranking is needed if the S11-level MBAL is used and the number of adjacen-cies needs to be reduced during the measurements. To run Interference Measurements using MBAL rotation, ADCEs for every BTS must be ranked according to their impor-tance.

You can define parameters for adjacency ranking algorithm and start adjacency ranking using the Start Adjacency Ranking dialog. In the dialog you can choose if HO Attempts

DN0196638

47


Id:0900d805807a51ea

to ADCE or HO Traffic Share are used in adjacency ranking. The algorithm sets the value for Neighbor Cell Ranking for ADCEs in BTS if the ADCE is not ranked or if the old ranking is inadequate. The value for the most important adjacency is 1 and for the least important 32 (thirty-two is the maximum number of adjacencies for one BTS).

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

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

1. Adjacencies with mandatory adjacency constraint and KPIs2. Adjacencies with mandatory adjacency constrains but without KPIs3. Adjacencies with KPIs4. Adjacencies without KPIs. Note that if there are no KPIs, the new ranking is arbitrary.

Each group has its own ranking range that is valid only within that particular 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 poor ranking, 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 ranking group • In groups where there are KPIs, if the new ranking differs from the old ranking to a

greater extent than defined in the Rank Change Threshold • If more than one ADCEs have the same ranking within the group

8.2 GSM interference measurementsBSC provides the measurements that are needed for the mobile-measurement-based optimization of adjacencies and frequencies of the network. Nokia Siemens Networks NetAct supports the whole automated planning process, and it uses the BSC measure-ments as well as the network configuration database as inputs to the optimization logic. The measurements used are Channel Finder (CF) measurement and Defined Adjacent Cell measurement (DAC), or Total FEP (Frame Erasure Probability) in S11 that is optional to the DAC and CF measurements.

For Siemens, the measurement used is Smart Carrier Allocation (SCA) in a binary file. For other vendors, measurements are read from CSV files, where carrier is identified with Cell name and interference with ARFCN and BSIC.

The Configurator module of NetAct is also needed to manage BSS elements. Optimizer uses the functionality of Configurator to get the actual network configuration.

48 DN0196638


Id:0900d805807a51ea


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

8.2.1 Measurements needed for OptimizerOptimizer needs the following measurements to be activated for the Nokia cell at BSC level:

• Defined Adjacent Cell (DAC) measurement, which collects data about all cells defined as adjacent cells

• Channel Finder (CF) measurement, which collects data about cells that are not adjacent cells

OR

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

For Siemens measurements such as Smart Carrier Allocation (SCA) are available in binary file. For other vendors the measurements are in a CSV file. The CSV file is avail-able in two formats: one with Date and Time combined in the same column and the other with Date and Time in separate columns. The format and the other parameter details of the CSV file to be imported are given in the Interference Measurement Retrieval dialog. The measurements that are available in the CSV file are as follows:

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

• The Interferer ARFCN parameter is the BCCH frequency of the interferer. • The Interferer BSIC parameter has a 2-digit value similar to NCC and BCC. • The unit of Interferer average signal strength can be either RXLEV or dBm (modulo

value).

The measurement scope and measurement period are defined in the Administration of Measurements application. The measurements are activated per BSC, and all the BTSs in a BSC collect the information. For more information, see Administration of Measure-ments Help.

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

8.2.2 Measurements and NetAct capacityBy default, Channel Finder and Defined Adjacent Cell measurements are not activated. However, these measurements are started when needed. Note that these measure-ments have to be enabled in BSCs before they can be started.

Measurements can be run for a long period, that is, several hours, and are processed in the BSC at the end of the period. This reduces the amount of data 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 possible BCCHs instead of only the number of current adjacencies increases the load in the network during the

DN0196638

49


Id:0900d805807a51ea

measurement period. However, this is not a remarkable increase and does not cause detectable decrease in performance.

Nokia Siemens Networks NetAct contains advanced functionality for analyzing the load caused by the measurements. The Capacity Indication Tool can be used to accurately determine the load of the existing measurements in the network. By starting the mea-surements required by Optimizer in a small network area such as one BSC, it is possible to receive information on the additional network load.

8.2.3 Measurement periodThe measurements must be scheduled for a few hours on several days because Opti-mizer requires measurements from a longer period, that is, approximately one week. The measurements are sent from the BSC to Reporter after each day. Running mea-surements for a long time causes additional load to the network and also to the MS handover behaviour.

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

8.3 Retrieving measurementsWhen collecting the interference measurements from mobile-originated BSS measure-ments for interference matrix generation, and further for frequency allocation, it is nec-essary to record all possible interfering signals and identify the interfering cells.

8.3.1 External and foreign interferersOptimizer is part of regional NetAct and can thus, by default, combine the measure-ments and configuration data of any network element managed by that NetAct. Interfer-ence outside the cluster is referred to as foreign interference, in which case the interferers are known. However, sometimes BTSs in the optimization scope area are interfered by BTSs managed in another NetAct, another vendor OMC, or even by BTSs of another operator. In this case, the interferers are not known and the interference is referred to as external interference. Although it is not possible to optimize frequency allo-cation for those BTSs, the interference that they cause is taken into account in the creation of an interference matrix.

8.4 PredictionsPredictions are used to complement measured data when interference data is not avail-able for interference matrix creation. Such cases include initial frequency planning for cells that are not yet in operation in the network 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, antenna direction, and simple link loss calculation. Optimizer’s simple link loss calculation does not take topo-graphic or morphographic data into account and therefore, the calculation is fast. Pre-dictions are indicative but to achieve reliable results, they should not be used alone but always in combination with measurements.

50 DN0196638


Id:0900d805807a51ea


8.4.1 Assumptions used in link loss calculationsLink loss calculation is based on Okumura Hata propagation model and antenna’s vertical gain pattern. If not, the basic assumptions behind the used propagation model are the following:

• Directed antennas have same gain at main beam direction and omni antennas have an own constant gain to all directions

• BTSs have same default BCCH power • Indoor cells have half of the default power • Antennas have the same height • Cable loss is not taken into account • In city environment propagation factor 4 could be used • Many antennas are taken into account. Accordingly, coordinates are used from

antennas and not from sites although they both have their own coordinates. There-fore, antenna coordinates should be correct

DN0196638

51

Optimizer Principles WCDMA interference matrix generation

Id:0900d805807a51ea

9 WCDMA interference matrix generationThe Interference Matrix is provided for visualization and further analysis. In WCDMA it is essential to distinguish between necessary neighbors and overshooting interferers. With Optimizer visualization methods the overshooting cells can be easily detected. It is essential to identify and understand the interference location, severity and root cause in the network before selecting the corrective actions, as frequency re-planning in WCDMA is not an option. Instead there are basic methods to reduce interference from overshoot-ing cells or long distance adjacencies; they include changes in antenna height, antenna type (beamwidth, gain), antenna downtilt, and primary CPICH power tuning. Optimizer provides means to identify these cases. It combines the measured interference with the actual network topology and presents all this for efficient visual analysis.

In Optimizer, Interference Matrix is created from the mobile measurement reports (MMR) that have been collected from a live network and stored in the PM database. Interference Matrix provides interference data for visualization and interference ana-lyzer. A WCDMA Interference Matrix represents the interference relations between cells. It is expressed with Ec/No and RSCP values.

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

52 DN0196638


Id:0900d805807a51ea

Measurement-based automated adjacency optimiza-tion

10 Measurement-based automated adjacency optimizationMeasurement-based adjacency optimization uses handover measurements collected by BSCs and RNCs. By analyzing the reports generated based on the measurements, the unused adjacent cells can be identified and removed from the adjacency list.

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

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 visu-alized and modified.

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

WCDMA adjacencies are rotated to get measurements for each adjacency candidate. Rotation is only needed if a lot of candidates are to be tested per cell. Rotation can be omitted by using DSR in the case of ADJS. Rotation is not needed if adjacencies are only deleted. For more information, see section Adjacency rotation. ADJS type adjacen-cies can be created using Detected Set Report measurements.

10.1 Measurements related to automated optimization Adjacency optimization is based on the following measurements:

• GSM interference measurements: Channel Finder measurement and Defined Adjacent Cell measurement

• ADCE KPIs: Handover Adjacent Cell measurement. For a list of the KPIs, 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

g The ADJG and ADJS measurement collection should be aligned with provisioned rotations.

For more information, see sections Optimizing adjacencies automatically and Provision-ing rotation plans in Optimising a Network Using Optimizer.

10.1.1 GSM interference data For Nokia, the interference data for GSM adjacency creation is received from an inter-ference matrix that is based on the following measurements:

• Channel Finder measurement, S9 • Defined Adjacent Cell measurement, S10

DN0196638

53

Optimizer Principles Measurement-based automated adjacency optimiza-tion

Id:0900d805807a51ea

For Siemens the measurement data is available in binary file. For other vendors mea-surements such as Cell name, Interferer ARFCN and Interferer BSIC are available in CSV file.

For more information, see GSM interference matrix generation.

10.1.2 Detected Set ReportingFor ADJS creation, information from the Detected Set Reporting functionality can be used. For more information, see Creating ADJS adjacencies based on Detected Set Reports in Optimising a Network Using Optimizer.

10.2 Adjacency-optimization-related KPIsThe adjacency-optimization-related KPIs are presented in the following tables. See also Appendix Supported KPIs.

ADJG-related KPIs are presented in the following table:

Parameter Description

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

Sum of HO Attempts [N] The sum of HO Attempts over actual, updated, and deleted adjacencies in a cell (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 deleted adjacencies in a cell) (in percentages).

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

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

Co-channel Average Received Power

Co-channel Average Received Power is derived from Channel Finder mea-surement and Defined Adjacent Cell measurement for all cells except for blind spot cells.

Co-channel Average Received Power Weighted

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

FEP Frame Erasure Probability

CIP Carrier over Interferer Probability

Table 3 ADCE-related KPIs


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

Table 4 ADJG-related KPIs

54 DN0196638


Id:0900d805807a51ea


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

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

Sum of ISHO Attempt Rates [N/h] 100*(The sum of ISHO Attempt Rate over actual and updated adjacencies in cell) / (The sum of ISHO Attempt Rate over actual, updated, and deleted adja-cencies in a cell) (in percentages).

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

ISHO Share The relative amount of handovers a particular adjacency at one cell has compared to all the sum of handovers of all adjacencies at that cell. This is not a measured KPI but calculated by Optimizer. Can be displayed on Map or in Browser.

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

Received Signal Strength Indica-tor (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 the target cells.

Fitness value Not a measured KPI but calculated from several KPIs to indicate how good an 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 is used to determine the order (in case not all adjacencies can be created or deleted).


Table 4 ADJG-related KPIs (Cont.)


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

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

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

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

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

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

Fitness value Not a measured KPI but calculated from several KPIs to indicate how good an 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

Table 5 ADJS-related KPIs

DN0196638

55


Id:0900d805807a51ea

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

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

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

The following figure illustrates the cost function for fitness.

Figure 7 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. Fitness share is the nor-

malized value of the KPI. The value of the KPI is scaled to the range of 0 to 1. • Fitness is calculated using the previous cost function for fitness where fitness shares

are weighted according to weighting factors to get the fitness value which has the range of 0 to 1.

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


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

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 (in percentages).

Table 6 ADJI-related KPIs

Fitness FitnessFitness

n21

nn2211

w...ww

*wwwFitness

+++

+...+×+=

×

56 DN0196638


Id:0900d805807a51ea


Figure 8 Mapping a KPI to the fitness value

In the previous figure, Min, Bad, Good, and Max are definable thresholds for each KPI. If the KPI is below the minimum threshold, the fitness value is 0. If the KPI is above the Max value, the fitness value is 1. Mappings of Fitness_share in points Min/0, Bad/0.2, Good/0.9, Max/1 are always the same and cannot be modified.

The following figure illustrates an example where the fitness value is calculated 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.

Figure 9 Example of calculating the fitness value

Fitness

Fitnessi

KPI value

KPI

Min Bad Good Max

1.0

0.9

0.2

0.0 i

DN0196638

57


Id:0900d805807a51ea

10.3 WCDMA adjacency KPI retrieval and optimizationStarting and retrieving measurementsWCDMA KPI(s) are retrieved by retrieving measurements from the NetAct PM data-base.

The following measurements are retrieved for ADJS KPIs:

• SHO Attempt Rate • SHO Share • SHO Attempts • SHO Success Ratio

The retrieved KPI set contains KPI values only for valid ADJS cell pairs and is used by the Adjacency Optimization tool in the deletion of ADJS adjacencies.

The following measurements are retrieved for ADJD KPIs:

• SHO Attempt Rate • SHO Share • Ec/No • RSCP • SHO Attempts • SHO Success Ratio • Number of Reports

The retrieved KPI set contains KPI values only for valid ADJD cell pairs and undefined adjacency cell pairs.

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

58 DN0196638


Id:0900d805807a51ea

Adjacency rotation

11 Adjacency rotationTo decide which existing adjacencies are good ones and which ones are not needed, handover statistics are collected for the existing adjacencies. Furthermore, in RAN, the concept of knowing beforehand which adjacencies are missing does not exist yet and therefore handover statistics are used for finding new good adjacencies. Candidate adjacencies need to be provisioned to the network before handover statistics can be col-lected for them. For this reason, Optimizer can make rotation plans for testing adjacen-cies in the network. Each rotation plan can be visualized and modified. Furthermore, the final list can also be visualized and modified.

Rotating adjacencies and creating the final listWCDMA adjacency optimization consists of the following phases:

• Selecting a list of existing adjacencies that are good enough and are not 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 rounds and the amount of adjacency candidates in each rotation round. In addition, 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 each rotation, a part of the adjacencies from the candidate pool are placed into the rotation. For example, on day one, the adjacencies in the basic list and the candidate pool number one are measured (rotation one). On day two, the adjacen-cies in the basic list and the candidate pool number two are measured (rotation two). Finally, on day five, adjacencies in the basic list and the candidate pool number five are measured (rotation slot five). Use the weekly summarization level for KPIs.

Figure 10 Basic List and Rotation slots

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

Based on the fitness of the rotated adjacencies, the best adjacencies are included in the final optimized adjacency list. The final list consists of the best adjacencies in the basic list and the rotation pool. To compare all the measured adjacencies, one KPI set that contains KPIs for all of these adjacencies is needed.

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

DN0196638

59

Optimizer Principles Automated frequency planning

Id:0900d805807a51ea

12 Automated frequency planningThe Frequency Optimization algorithm creates a new frequency plan based on the inter-ference 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) measure-ments are used for CIP and Total FEP measurement for FEP. For more information on interference matrix, see chapter GSM interference matrix generation.

When a new frequency plan has been created, you can visualize the results and imple-ment or schedule the implementation of the new frequency plan to the network. The interference matrix can also be copied and used with a preferred external automated fre-quency planning (AFP) tool.

Frequency Optimization can be used to a target area of any size, ranging from allocating frequencies to single cells to allocating frequencies to all the cells in a NetAct cluster.

The focus of the frequency allocation or optimization can be altered with different inter-ference data scaling and weighting factors. Parameters can be assigned to a TRX layer specifically, for example, BCCH channels can have stricter constraints than other chan-nels.

Optimizer supports frequency optimization in hopping and non-hopping networks, and in hopping networks both BB and RF (synthesized) hopping is 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 plan in Optimising a Network Using Optimizer. For detailed instructions, see Frequency Allocation Help.

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

Fast methodThe Fast method uses the Stochastic Greedy algorithm and random starting point to optimization. The Fast method produces a reasonably good allocation quickly by finding a local minimum in one optimization loop. It is useful for ensuring that the defined param-eters are appropriate before carrying out the accurate allocation. The Fast method is also convenient when only a few missing frequencies need to be allocated without changing the rest of the allocation.

Optimization methodThe Optimization method also uses the Stochastic Greedy algorithm but starts from the existing allocation and can only change frequencies if the resulting network is better than before.

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

The accurate allocation works so that the more time is given, the better the allocation. The default time is calculated based on the number of the items to 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 lists to be allocated.

60 DN0196638


Id:0900d805807a51ea

Automated frequency planning

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

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

In Accurate allocation, the more time is given, the better the allocation. As a general rec-ommendation, it is better to run a long allocation once than to run several short alloca-tions. Therefore, if the plan is big, it may be best to let the allocation run overnight. If the network is reasonably small, it may be better to let the algorithm run for a shorter period of time.

BCCH and TCH channels are usually separated into their own band segments by using frequency groups. Often the BCCH allocation stays constant much longer than the TCH allocation. Therefore, we recommend allocating the BCCH channels before TCH chan-nels.

12.1.1 Allocating frequencies for a part of the networkIf you are reallocating frequencies only for a part of the network, select only the cells to be allocated as the target. The Frequency Optimization tool automatically finds all the surrounding cells that affect these cells. The allocation status to these target cells is set on and to other cells off in the target BTSs.

12.1.2 Allocating missing frequenciesWhen the network is expanded and new cells and TRXs are added, it is necessary to allocate frequencies for these cells. To do this, select the Allocate only planned objects option in the Analysis tab.

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

12.2 Frequency optimization casesFrequency optimization cases can be divided into the following categories:

• Full allocation, when the whole frequency plan is allocated again. For more informa-tion, see section 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 are added and only these new objects require allocation. For more information, see section Allocating planned objects only.

DN0196638

61


Id:0900d805807a51ea

12.2.1 Full allocationIn the initialization phase of full allocation, the algorithm tries to find an allocation fulfilling all separation constraints. If this is not possible, the algorithm tries to keep the most important separation constraints and violate only the less important ones. There are several separation constraint classes, each of which can have a different priority or cost. The algorithm used is a constructive stochastic greedy algorithm, which organizes the TRXs according to the required separation constraints. Initialization phase produces an allocation using the lowest available channels. Therefore, they are used more often than the highest channels, which may cause bias to interference minimization. In an optimal allocation, the spectrum is used quite evenly.

For these reasons, in the second phase, the algorithm removes the bias caused by the initialization phase so that the spectrum is used more evenly. This scrambling of fre-quencies is an iterative process changing each TRX the channel to a random available channel within the constraints. This process is then repeated several times.

In the final phase, the algorithm modifies the frequency plan so that the interference 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 use the same Stochastic Greedy algorithm. However, the Fast method starts from a random point and the method Optimization starts from the current allocation. The Stochastic Greedy algorithm produces an allocation quickly. This algorithm stops to the first found local minimum but it can be used to get a rough idea of the quality of the allocation. The Fast algorithm is very useful when only a few missing frequencies need to be allocated. This way, possible parameter and other errors can be found and corrected as early as possible. This algorithm also gives a good reference point for the accurate algorithm which should always produce clearly better allocations. For more information, see Fast method.

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

The Accurate method is a simulated-annealing-based algorithm that can escape 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 is given, the better the allocation. The algorithm produces the best possible allocation within a given time. Allocation is closer to the global minimum the more time it is given. For more information, see Accurate method.

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

12.2.2 Allocating planned objects onlyIn the initial phase of allocating only new planned objects, the goal is to keep the channels that have already been assigned and give the lowest possible channels to the TRXs missing allocation. If a channel that fulfils the constraints is not found, a random channel is given. In the second phase, scrambling is made only for the planned TRXs.

62 DN0196638


Id:0900d805807a51ea


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

12.3 Structure of the allocation algorithmsThe frequency optimization algorithms contain the following parts:

• Algorithm Logic selects according to certain rules which TRX is to be changed next. For more information, see section Algorithm Logic.

• Channel Assignment assigns a new channel to the selected TRX. For more informa-tion, see section Channel Assignment.

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

12.3.1 Algorithm LogicEach algorithm has its own Algorithm Logic to select the next TRX to be changed. In the initial phase, the algorithm orders TRXs according to separation requirements. In the final phase, the accurate algorithm randomly selects the next TRX, and the fast algo-rithm randomly selects the next TRX from a set of TRXs.

12.3.2 Channel AssignmentWhen a TRX has been selected, the algorithm asks Channel Assignment to assign the channel. This channel can be the lowest available, randomly selected, or the best of all the available channels, depending on the type of algorithm. When Channel Assignment selects the channel, it has to find the legal channels fulfilling all separation constraints. There can be forbidden frequencies for certain cells and different TRXs can have in overall a different set of allowed channels. Also, the set of allowed channels varies depending on the current allocation.

12.3.3 Cost Function CalculationWhen the new channel has been assigned, the Cost Function Calculation part calcu-lates the cost value for the changed allocation. This value tells how “good” or “bad” the allocation is. The smaller the value, the better the allocation. It is possible to scale the interference value, and different TRXs can have different scales. In general, it is possible to scale co-channel and adjacent channel interference, and interference coming to and from the BCCH. In addition, different separation violations can have different penalties. The following separation cases are classified: co-site, co-cell, adjacent cell, C/lc level, C/la level, and edited separations, It is also possible to give a penalty for using other than a suggested channel. Scaling interference upwards reduces that particular interfer-ence in the final allocation when the corresponding optimization goal is used. For more information on the interference scales and optimization goals, see Frequency Allocation Help.

When the cost value for the changed allocation is calculated, Algorithm Logic either accepts or rejects the change and selects a new TRX for the next loop. This is iterated until the ending criteria are fulfilled and allocation is stopped. The fast algorithm stops when no improvement can be found, which means that the allocation has reached a

DN0196638

63


Id:0900d805807a51ea

minimum. For the accurate algorithm the ending criteria are somewhat more complex, because it can escape from the minima. The accurate algorithm stops when the “tem-perature”, which is an internal parameter of the algorithm, has reached a certain level.

12.4 User settings to guide the algorithmsThis section covers issues related to forbidden channels, frequency groups and manual separations.

12.4.1 Forbidden channelsOptimizer supports all the GSM frequency band variations: GSM, EGSM, GSM1800, GSM1900, and GSM850. When working with Frequency Groups in the Frequency Allo-cation tool, the list of channels in the selected frequency 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 that globally or nationally forbidden channels are not accidentally used.

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

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

12.4.2 Passive intermodulationPassive intermodulation can be taken into account in automated frequency planning. In the Start Frequency Optimization dialog, it is possible to define that passive intermodu-lation is to be avoided. Intermodulation is caused by poor antennas or otherwise faulty hardware. A third frequency is created of two different downlink frequencies. This third frequency interferes some uplink frequency, for example, 2*f1(DL)-f2 (DL)=f3(UL).

12.4.3 Frequency groupsThe basic purpose of using frequency groups is to define the frequencies and separation requirements for the Frequency Allocation tool. The frequencies and separation require-ments are used in the frequency optimization process (when generating a separation matrix) for each TRX. Frequency group settings are user-specific and are saved with the optimization plan. For more information and instructions, see Creating and defining fre-quency groups in Frequency Allocation Help. See also see section Creating frequency groups in Optimising a Network Using Optimizer.

12.4.4 Manual separationsSeparations can be manually defined between the cell pairs which are known to interfere with each other, but do not show as interfering in measurements because of inadequate measurement data.

64 DN0196638


Id:0900d805807a51ea


12.4.5 MA listsFor 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 kept untouched by Optimizer during frequency allo-cation. See Modifying Mobile Allocation Lists (MALs) in Frequency Allocation Help for details.

12.5 BSIC planningThe Base Station Identity Code (BSIC) Planning functionality in Optimizer checks the current BSIC allocation for conflicts and assigns again valid codes for those found invalid. BSICs (+BCCH frequency) are required by the mobiles and network to distin-guish the cell which is being measured. BCCH and BSIC combination must be unique within a certain geographical area in the network. BSICs should always be allocated again when frequency plans are changed.

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

12.6 Interpreting frequency optimization resultsIf co-cell or co-site separations for a layer are violated, there are either too few frequency channels available, or the parameter values need adjustment. The separations and the fee for breaking them (violation penalties) are set to influence each layer (BCCH, TCH, Underlayer..) separately as well as between the layers. The separations protect users from creating obviously interfering frequency assignments by setting minimum rules for frequency reuse. However, unnecessary or unrealistic rules should not be set, as these will influence the capability of the algorithm to minimize the measured interference in the network. It is advised that the user will iteratively compromise these values, i.e. run several iterations with different value sets and then compare the results until an optimum balance is achieved. If the parameters are correct, but violations still exist, more channels should be assigned to keep these separations.

Similarly, if adjacent cell separations are broken, the reason may be that there are too few channels or that the adjacent cell separations have been set incorrectly in the allo-cation parameters. It is also possible that there are unnecessary adjacencies, which in turn produce too many adjacent cell separation violations. To resolve this, obsolete adjacent cells need to be removed with the help of the Automated Adjacency Optimiza-tion (AAO) tool and the channels need to be allocated again. If there are still adjacent cell separation violations, the only possibility is to add more channels or loosen the adjacent cell separation requirements. If adjacent cell separations are used, the viola-tion penalty in the BCCH frequency group should be much bigger than in the TCH fre-quency group. It is recommended to set the adjacent cell separations only for the BCCH layer.

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

DN0196638

65


Id:0900d805807a51ea

To summarize, basically all separations act as hard constraints, as even the minimum penalty value (1) well exceeds the typical cell level interference cost. An advanced user may in some cases decide to “soften” selected cell separations by minimizing the related penalties and at the same time scaling up significantly the co- and adjacent channel interferences for the cost function. But nevertheless, the more and the larger the residual violations, the less is the weight of the interference minimization and the higher is the residual interference level after allocation. The Fast Allocation option as well as Viola-tions Report (listing the violations and causes) and Network Interference Report (provid-ing an average residual interference per layer) in AFP Analysis are the basic tools for finding optimum settings for each planning case. The interference report is also useful in balancing the co- and adjacent channel interference weights.

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

66 DN0196638


Id:0900d805807a51ea

Primary downlink scrambling code management

13 Primary downlink scrambling code manage-mentIn WCDMA networks, it is forbidden to have the same scrambling code in cells defined as neighbors and in the neighbor cells' neighbors which use the same frequency. There is however an option to reuse scrambling codes for cells in the same sector but with dif-ferent UARFCNs. Furthermore, it is not advisable to reuse a certain scrambling code within a given minimum reuse distance. Therefore, in Optimizer you can analyze actual data and optimization plans for such collisions. You can then manually or automatically correct existing collisions and violations, or make a completely new allocation taking into account the following:

• Frequency (UARFCN) • Collisions in the neighboring cell and in the neighbor’s neighboring cells

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 2Cell C (neighbor’s neighbor) - scrambling code 2Due to neighbor cell list combination during SHO, up to four levels of neighbors are taken into account.

• Scrambling code rule violationsOptimizer 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

• Adjacency directionWhen allocating scrambling codes and/or correcting scrambling code collisions, the Scrambling Code Allocation tool takes the adjacency direction into account. For example, there is an incoming adjacency from Cell A to Cell B and the cells have the same scrambling code. When the Take adjacency direction into account option is selected, the tool finds only one collision from Cell A to Cell B. If the option is not selected, the tool finds two collisions from Cell A to Cell B and from Cell B to Cell A.

• Minimum desired reuse distanceWhen allocating scrambling codes, Optimizer checks if the scrambling code of the cell is reused closer than the specified threshold. If yes, the scrambling code of this cell is changed. For example, Cell A and Cell B both have scrambling code 1. The distance between the cells is 10 km and the minimum reuse distance threshold is set to 12 km. When allocating scrambling codes, the algorithm checks cell by cell whether the scrambling code should be changed. First, Cell A is checked and the scrambling code is changed. Next, Cell B is checked and as the scrambling code of Cell A has already been changed, the scrambling code of Cell B is not changed.

DN0196638

67

Optimizer Principles Primary downlink scrambling code management

Id:0900d805807a51ea

• Forbidden scrambling codes (can be defined on a WCEL-level, or globally for the whole PLMN)Forbidden code set is a set of scrambling codes which cannot be used by the cell when this set is assigned to the cell. For example, the forbidden codes set number 1 contains scrambling codes 1,2,3,4,5, and 6. If the set is assigned to Cell A, Cell A cannot use any 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 list contains all possible codes used by the cell’s neighbors and neighbor’s neighbors. In addition, the codes included in the for-bidden scrambling code groups (if any) are excluded from the list. Finally, the new scrambling code is randomly picked from this list.

In the Scrambling Code Reuse Visualization dialog, you can define which scrambling codes are visualized on Map. In addition, you can select the frequency (UARFCN). On Map, all cells which have a different frequency are displayed in grey. Cells which have the same frequency and scrambling code are displayed in red. Cells which have the same frequency and belong to the same scrambling code group are displayed in yellow. Cells which have the same frequency and belong to different scrambling code groups are displayed in blue. Cells which have a different frequency are displayed in grey (if the frequency is activated).

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

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

68 DN0196638


Id:0900d805807a51ea

Dominance areas in visualization

14 Dominance areas in visualizationCell dominance area information provides an informative overview of the network situa-tion. For example, when using the actual cell configuration (antenna data, TX power, HO settings) for building dominance maps and measured traffic distribution (cell loading per service) display, it is easier to understand adjacency relations and interference condi-tions. Furthermore, it is possible to show any measured KPI information together with cell dominance areas and parameters for effective analysis of the reasons for perfor-mance of cells.

Dominance visualization in Optimizer is done using a Voronoi graph algorithm and with the simplified assumption that all cells have the same power and antenna parameters besides azimuth. Hence the dominance area consists of locations that are closest to a certain cell.

Note that calculations are made for visualization purposes only and are not used by opti-mization algorithms. Calculations do not use map data. The idea of calculations is to give a rough visual background for displaying accurate measurement data. For related use cases, see Appendix Optimization cases in Optimising a Network Using Optimizer.

Calculations take into account the following parameters:

• Antenna direction • Maximum cell coverage radius

g Dominance area visualization is supported in GSM, WCDMA and LTE networks.

14.1 Calculation areaDominance is calculated for the visible area on Map, plus a margin to the left, right, below, and above. In addition, cells within a buffer zone around this area are included in the calculation.

DN0196638

69

Optimizer Principles Multi-PLMN support in Optimizer

Id:0900d805807a51ea

15 Multi-PLMN support in OptimizerOptimizer supports the optimization and visualization of multiple PLMNs. Each cluster can be viewed and grouped in Navigator and Browser. All the optimization tools can be used in the same way as when working with a single or local cluster. The local cluster is named PLMN-PLMN. The optimization results are saved from the Optimizer DB to the Configurator DB as a plan and exported from the Configurator DB to other management system using the existing interfaces.

70 DN0196638


Id:0900d805807a51ea

Multi-vendor support in Optimizer

16 Multi-vendor support in OptimizerMulti-vendor (MV) support in Optimizer allows the user to visualize and modify foreign vendor Network Elements (NE). These foreign NEs are treated as normal elements and can be used with all tools, though some restrictions apply. Optimizer can only read Con-figuration Management (CM) data from the Configurator CM database. Before Multi-vendor CM data can be used in Optimizer, it has to be available in the Configurator CM database.

A separate adaptation project is needed to import MV CM data into the Configurator CM database from another Network Management System (NMS). A network-wide CM envi-ronment is created by importing external NE data from foreign NMSS. The import is done using XML files which are prepared during the adaptation project.

16.1 Multi-vendor dataExternal regions’ data is read into Optimizer automatically using normal synchronization process between the Configurator CM database and the Optimizer database.

Configuration Management dataConfiguration Management data is copied from the Configurator CM database to the Optimizer database using the existing Optimizer data model and hierarchy. External Network Elements are visualized and handled exactly like local network elements. Both parameters and KPIs are mapped to existing Optimizer object parameters and KPIs. A new CM parameter, vendor, becomes visible in all cells and controllers in Optimizer. This makes it possible to separate one vendor’s NEs from others.

Performance Management dataNormally Optimizer reads KPI data from the NetAct Performance Management data-base. With external NEs this is not possible. Optimizer includes a feature to import KPIs from a file. The data file must be in the Comma Separated Values (CSV) format. Both automatic and manual import is possible. Automatic import will read the CSV file from a user-specifed location in the Linux Application Server (LinAS). Manual import is config-ured and started from the Optimizer user interface. KPI import can also be used for local region NEs.

16.2 Multi-vendor visualizationExternal and non-local network elements are visualized in the same way as local Nokia NEs.

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

MapOn the Map, the user can use a different color for each vendor. A tool tip displays the cell label, indicating the vendor when the pointer is placed over a cell icon. The legend can be set by the user.

DN0196638

71

Optimizer Principles Multi-vendor support in Optimizer

Id:0900d805807a51ea

BrowserIn the Browser, foreign and non-local NEs are displayed in the same way as local Nokia NEs. For foreign NEs, only the most important parameters have values, however. The rest of the parameters show empty values. The vendor name can be displayed in the Browser. There are also default Browser profiles for external NEs, in order to make it easier to see only relevant parameters.

16.3 Multi vendor GSM Interference Matrix CreationAn Interference Matrix (IM) can be created using measurement data from the PM database for Nokia NEs and from binary files for Siemens NEs. The multi vendor func-tionality helps the user to create the IM set independent of vendors by importing the CSV file. During importing IM set is created under the selected BSCs. Therefore, GSM IM Creation functionality is available for all the vendors. An Interference Matrix that has been created elsewhere can also be imported to an external or non-local controller as a CSV file, where cells are identified by Cell ID and Location Area Code (LAC). For more information on creating GSM IM refer to Creating an interference matrix for GSM in Opti-mizer Help.

16.4 Multi-vendor restrictionsSince external network elements do not have all the parameters that the local NEs have, some Optimizer features and tools are not available when the scope includes these foreign objects.

Instant Adjacency ProvisioningAdjacencies of foreign vendor cells or external cells cannot be provisioned instantly since no direct network connection exists to these NEs. If instant adjacency is started, the foreign vendor adjacencies are skipped. Details of the operation can be found from the Task Management tool view.

Frequency OptimizationThe Automated FP tool can be used to allocate BCCH frequencies and BSIC codes also to external cells.

Automated Adjacency CreationThe rotation process for creating WCDMA and inter-system adjacencies is not valid for external or non-local adjacency creation.

72 DN0196638


Id:0900d805807a51ea

Where to find more information

17 Where to find more informationOptimizer documentation

• For information on the process of optimizing a network using Optimizer, see Opti-mising a Network Using Optimizer.

• For an overview of the functionality changes between Optimizer releases, see Func-tionality Changes in Optimizer.

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

• For information on Optimizer database tables, see Database Description for Opti-mizer.

• 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 the following docu-ments: • Geographic Information System Principles • Map Administrator Help

NetAct Configurator documentation

• For information on the NetAct Configurator, see the following documents: • NetAct Configurator Principles • NetAct Configurator Technical Reference Guide

DN0196638

73

Optimizer Principles Appendix Supported KPIs

Id:0900d805807a51ea

A Appendix Supported KPIsThis 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 KPIsAll 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 KPIsAll KPIs are available 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.4 ADJD KPIsAll KPIs are available 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 KPIsAll KPIs are available from NetAct using Autodef measurements.

• IFHO Attempts [N] • IFHO Attempt Rate

74 DN0196638


Id:0900d805807a51ea

Appendix Supported KPIs

• 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 on normal 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 [%]

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) [%]

DN0196638

75


Id:0900d805807a51ea

• 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 licenseRNC 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_606d) [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) [%]

76 DN0196638


Id:0900d805807a51ea

Appendix Supported KPIs

• Intersystem Hard Handover Attempts (RNC_282a) [N] • Intersystem Hard Handover Success Ratio (RNC_169a) [%] • 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 than Voice (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 Distance of Max Reports[km] • Propagation Delay Max Distance Report Number[N] • Propagation Delay Max Distance[km] • Propagation Delay Max Reports[N] • HSDPA throughput over active time (RNC_722a) [kbit/s]

A.10 KPIs used in WCDMA capacity analysis • Marginal Area Load Time Share DL (RNC_111a) [%] • Overload Time Share DL (RNC_112a) [%] • Marginal Area Load Time Share UL (RNC_106a) [%] • Overload Time Share UL (RNC_107a) [%] • Channelisation Code Occupancy (RNC_113a) [%] • Max Code Occupancy (RNC_520b) [%] • Noise floor of the System (RNC_177b) [dBm] • Average VCC Egress Utilization (DL utilization) (RNC_732b) [%]

DN0196638

77


Id:0900d805807a51ea

• Allocated peak capacity of ATM VCC (max reserved peak capacity / max capacity) (RNC_760a) [%]

• AAL2 connection reservation success rate (RNC_602a) [%] • Max AAL2 connection utilization (CID utilization) (RNC_1057a) [%] • Max Reserved IP based route bandwidth (RNC_1909a) [%] • IP Route Accessibility for outgoing traffic (RNC_5005a) [%] • Maximum number of available CEs (M5001C0) [N]Maximum number of used CE DL

(M5001C3) [N] • Maximum number of used CE UL (M5001C4) [N] • Average available CEs (M5001C2) • Average ratio of utilized CE for DL in BTS (RNC_730a) [%] • Average ratio of utilized CE for UL in BTS (RNC_731a) [%]

A.11 KPIs used in GSM capacity analysisg There are two busy hours for Radio KPIs and in Optimizer you see those KPIs twice

for example in KPI retrieval. The daily level value is the same for both KPIs.

• GPRS triggered handovers (ho_61) [N] • Average available area level PS territory size for nTRXs (ava_44) [TSL] • Share of territory upgrades caused by decreasing CS traffic (trf_240) [%] • Share of territory upgrades caused by increasing PS traffic (trf_241) [%] • GPRS UL Payload Data (trf_212c) [kB] • GPRS DL Payload Data (trf_213c) [kB] • EGPRS UL payload data (trf_214a) [kB] • EGPRS DL payload data (trf_215a) [kB] • Average UL TBF per timeslot (tbf_37d) [N] • Average DL TBF per timeslot (tbf_38d) [N] • UL multislot allocation blocking (tbf_15a) [%] • DL multislot allocation blocking (tbf_16a) [%] • Downlink multislot allocation blocking (tbf_16b) [N] • Downlink multislot soft blocking (blck_33b) [%] • DL multislot soft blocking (blck_33a) [%] • Peak GPRS Channels (sum(PEAK_GPRS_CHANNELS) from

P_NBSC_RES_AVAIL) [N] • DL EDAP congestion due to small pool size (blck_33b) [min/GB] • Inadequate EDAP resources in DL limited by EDAP size (dap_13) [%] • Max. received load (frl_8a) [%] • Ratio of discarded received packets (gbip_1) [%] • Packet drop ratio (gbip_2) [%] • Downlink MCS selection limited by PCU (dap_9) [min/GB] • UL EDAP congestion due to PCU limitation (dap_14) [%] • UL EDAP slave channels congestion due to small pool size (dap_18) [%] • DL EDAP congestion due to PCU limitation (dap_15) [%] • Territory upgrade rejection due to PCU capacity (blck_32) [%]

78 DN0196638


Id:0900d805807a51ea

Appendix Parameters read and optimized by Optimizer tools

B Appendix Parameters read and optimized byOptimizer toolsThe tables below lists the parameters in the configuration database that Optimizer readsand optimizes. The first table lists the parameters read by Adjacency Management. Thesecond table lists the parameters read and optimized by Frequency Allocation. The thirdtable lists the parameters read and optimized by the service optimization tools.

Parameter in Configuration database

Read by Adja-cency Manage-ment

Optimized by Adjacency Management

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

Label x

BSIC BCC x

Table 7 Parameters read and optimized by Adjacency Management

DN0196638

79

Optimizer Principles Appendix Parameters read and optimized by Optimizertools

Id:0900d805807a51ea

BSIC NCC x

LNBTS

DN x

MCC in PLMN x

MNC in PLMN x

Neighboring eNB DNS (internal parameter to create the ADIPNO object)

x

LNCEL

Physical Cell ID 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


LNBTS

DN x

MCC in PLMN x

MNC in PLMN x




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

80 DN0196638


Id:0900d805807a51ea


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

Neighboring eNB DNS (internal parameter to create ADIPNO object)

x

LNCEL

Physical Cell ID x


Read by Fre-quency Alloca-tion

Optimised by Frequency Allocation

SITE x

User Label x

Latitude x

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

Table 8 Parameters read and optimized by Frequency Allocation




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

DN0196638

81

Optimizer Principles Appendix Parameters read and optimized by Optimizertools

Id:0900d805807a51ea

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




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

82 DN0196638


Id:0900d805807a51ea


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 8 Parameters read and optimized by Frequency Allocation (Cont.)

DN0196638

83

Optimizer Principles Appendix Default optimization profiles in Browser

Id:0900d805807a51ea

C Appendix Default optimization profiles inBrowserThere are object-specific default profiles and default optimization-case-specific profilesin Browser. The default optimization-case-specific profiles are briefly described in thisappendix. For more information on Browser, see Browser in Optimizer Help.

C.1 Object-specific default profilesObject-specific default profiles, such as the Default BTS profile, are profiles for the network elements shown in Browser.

C.2 Default optimization-case-specific profilesIn addition to object-specific default profiles, some default optimization profiles have been created for selected planning tasks. The default profiles serve as examples 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.

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

C.2.1 RNC-WCEL Default Area Codes AnalysisThe RNC-WCEL Default Area Codes Analysis profile contains the actual situation of RNC identifiers, location area codes (LAC), routing area codes (RAC), and cell identifi-ers. The sorting feature in Browser provides an easy means of making a Network Audit of wrongly assigned identifiers and/or codes. Visualizing the information on Map simul-taneously on dominance, cell icon and cell label makes errors in LAC/RAC/cell identifi-ers visual, and allows 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 • Location area code • Routing area code • Service area code (SAC) • Service area code for broadcast (SACB) • Cell Identifier

Modifying the profileIn Browser, you can, for example, sort the objects according to the column headers, filter rows based on a certain column value, and change the column order by dragging and dropping columns. For instructions, see Sorting objects in Browser and Changing the view in Browser in Optimizer Help. The table layout is saved when you change the profile or object type.

84 DN0196638


Id:0900d805807a51ea

Appendix Default optimization profiles in Browser

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

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 adjacen-cies on the selected site, their performance 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 frequency optimization. The profile displays the element hierarchy: cell - BTS - TRX.

• RNC-WCEL Default Adjacency CMThis profile contains all types of WCDMA adjacencies with a default configuration to get a fast overview of the existing adjacency situation as a starting point for mass creation and/or editing.

• RNC-WCEL Default Call Setup and Retainability AnalysisAdmission control or call access control in RAN are based on the received and transmitted powers, their increased estimations are caused by new connections, and certain targets and thresholds. If the targets are set too low, too many calls may be blocked. On the other hand, targets that are set too high result in too much inter-ference and degraded performance or even dropped calls in the network. The purpose of optimizing the admission control test case is to verify that with Optimizer, you can monitor and analyze the performance of new calls to a network and the retainability of existing calls within a network. Also, you can optimize the parameters controlling these actions so that the target performance is achieved.

• RNC-WCEL Default SHO AnalysisSoft Handover (SHO) in WCDMA networks offers diversity gain by combining indi-vidually fading multiple radio links to a more reliable connection. Moreover, because of the nature of SHO, the handover as such is more reliable than a hard handover, as the new connection 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 cells either at one or several different sites. Therefore, there is a need for additional resources (physical resources: WSP cards, more transmitters, more power, and logical resources: more channelization codes, for example). The number of additional resources is charac-terized by the number of SHO overhead. The SHO is always beneficial for a single user, but unlike in UL, where the UE in SHO still transmits only one signal received by multiple cells, in the DL, SHO needs multiple transmission that introduces addi-tional interference for other users. As a network-wide effect in DL, 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 UEs not in SHO ensures the following:

DN0196638

85

Optimizer Principles Appendix Default optimization profiles in Browser

Id:0900d805807a51ea

• 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 of the primary CPICH (pilot power) and the parameters that affect the reporting of the SHO condi-tions by the UE.

• RNC-WCEL Default HHO (IF-HO) AnalysisThe RNC-WCEL Default Hard Handover (Inter-frequency) Analysis profile can be used to quickly check if there are problems in the handover attempts and success, and link the problems to the relevant CM. For example, there may be certain reasons why HHO is not enabled, or thresholds may be set in a wrong way.

• RNC-WCEL Default IS-HO AnalysisThe RNC-WCEL Default Inter-system Handover Analysis profile can be used to quickly check if there are problems in the handover attempts and success, and link the problems to the relevant CM. For example, there may be certain reasons why to make IS-HO may not be enabled, or thresholds may be set in a wrong way. By showing the HO attempts together with system borders on Map, conclusions can be drawn if the HOs at the coverage end of one system happen in the border cells, or already earlier. Also, it is advisable to check if there are extensive IS-HO failures at the system border. This could be a consequence of HOs that are initiated too late and/or handover thresholds or parameters that have been wrongly set.

• RNC-WCEL Default Prx Noise AnalysisCells with potential problems from noise and/or interference in the WCDMA air inter-face can be spotted by analyzing the respective noise and/or interference related KPIs. Typically, these problems are crucial for the performance of a WCDMA network but they cannot be fixed by simple network parameter adjustments. They often result from installation problems (for example, crossed feeders, bad antenna locations, wrong main lobe directions, wrong tilts and bad cable connections). These problems can cause increased interference. Also, industrial and man-made noise can be spotted without expensive on-site measurements. It is possible to export the list of the worst performing cells to support site visits and corrective measures.

• RNC-WCEL Default Power and Load AnalysisThis profile can be used to identify cells with high load. Such cells can be targets for load balancing and/or HW upgrade. This profile can also be used for identifying cells where the received and transmitted powers do not match with the traffic carried, which may indicate interference or noise problems.

• RNC-WCEL Default HSDPA AnalysisThe RNC-WCEL Default HSDPA Analysis profile is intended for visualizing, analyz-ing, and optimizing the main HSDPA configuration, HSDPA performance, and resource sharing between HSDPA and Dedicated Channels (DCHs). The profile contains both CM data and KPIs.For information on the HSDPA optimization cases that you can perform using Opti-mizer, see Visualizing HSDPA in Optimising a Network Using Optimizer.

• Default WCEL-ADJGThe Default ADJG profile is intended to display ADJG main adjacency parameters with KPIs. The profile combines adjacency CM and PM data.

• Default WCEL-ADJSThe Default ADJS profile is intended to display ADJS main adjacency parameters with KPIs. The profile combines adjacency CM and PM data.

• The default Capacity Analysis browser profiles for GSM and WCDMA show the rule results for each interface or element selected to be analyzed. Rule results are

86 DN0196638


Id:0900d805807a51ea

Appendix Default optimization profiles in Browser

shown for the rules that we used in the analysis. The results are shown with color: red indicates a capacity shortage, green that there is enough capacity in the current situation and orange that the analysis could not be made because of, for example, missing KPI data.The profiles also show essential configuration parameters and KPIs that are used in the analysis, as well as solution notes for the rules. The default capacity profiles are listed below.The default capacity profiles for WCDMA are:– WCEL Default Radio Rules Analysis– WBTS Default WBTS Rules Analysis– WBTS Default Iub Rules Analysis

This browser profile shows analysis results for two base elements: WBTS and VCC. The base element for the ATM based Iub analysis in the profile is VCC and the base element for the IP Route based Iub analysis is WBTS. Both base elements are shown in the same profile. The rule results are shown in separate columns for each base element. The results for the WBTS element also show the overall results of the VCC analysis; red if any VCC under a specific WBTS shows red and green if all VCCs under a specific WBTS are green.

The default capacity profiles for GSM are the following:– GSM Default Radio Rules Analysis– GSM Default PCU Rules Analysis– GSM Default Abis Rules Analysis– GSM Default Gb Rules Analysis

• The default Browser profiles for LTE are the following:– Default LNBTS– Default LNCEL– Default ADJLL– Default MRBTS– Default LTE-NW– Default LCAL

DN0196638

87


Id:0900d805807a51ed

Index

AAbis View 44adjacency

list 52plan 52ranking 46template 31

adjacency direction 66adjacency type

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

administrative tasks 14analysis 14Antenna Data Editor 15ARP 45automated adjacency management 34Average Received Power 45

BBCCH allocation list 45Browser 18, 24Browser export 22Browser profiles

capacity analysis 85LTE 86

Ccapacity analysis 41

rules 42Carrier over Interferer Probability 45channel assignment 62CIP 45constraint 32

Ddominance 68

Fforbidden channel 63frequency group 63frequency optimization 59

GGeographic Information System (GIS) 15

Iinterference data 52interference matrix 21interference measurements 47

Kkey performance indicator 20

ADCE 73ADJD 73ADJG 73ADJI 73ADJS 73BTS 74cell 74GSM capacity analysis 77RNC 75TRX 75WCDMA capacity analysis 76WCEL 75

KPI trends 44

LLTE network 26

MMap 18measurement retrieval 49

NNavigator 17

Oopen interface 21optimization

algorithm 13automatic 13manual 13process 13, 14

optional functionality 13

Ppanes 16parameter management 21parameters 78performance degradation 20periodical tuning 14permissions 14polygon 15predictions 49

88 DN0196638


Id:0900d805807a51ed

RRadio Resource Management 14rotation 58

Sscope 16, 18scrambling code 66separation 63

Ttemplate assignment rule 31temporary BA list 46threshold set 21Threshold Sets dialog 21

Uuser interface 16

WWCDMA adjacency 52

Documents

Optimizer Principles 3.0