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 zwangslufig bestimmte Teile der Gerte unter Span-nung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverlet-zungen und Sachschden fhren.

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 Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.

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 Optimizers 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 objects 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 IDWCDMA Cells:

MCC MNC RNC Identifier Cell IdentifierThe 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 neededThe 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 neighbors 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 [01]. 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 - SourceAntennaBearing1g 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