1 Optimizer Introduction&Setup

1 © NOKIA / Preliminary tasks in Optimizer / 6-137228 / version 2.0 en / 05.05.2004 / Bettina Baacke

Optimizer Introduction


Contents

• Optimizer Overview• Optimizer Interfaces• Optimisation workflow in NetAct

Configuring Configuring

Service Management

Service Management

Security & SystemManagement

Security & SystemManagement

PlanningPlanning

SubscriptionManagement SubscriptionManagement

ReportingReporting

AdaptationAdaptation

Multitechnology & MultivendorNetworks

Multitechnology & MultivendorNetworks

Multiservice,Multiservice,

OptimisingOptimisingMonitoringMonitoring

NokiaNetAct

Functionality areas of NetAct

Functionality area


• Optimizer target is to provide GSM/GPRS/WCDMA functionality for

•maximising NW capacity utilisation rate•optimising the service performance with minimum manual

effort

The application combines means for NW analysis and optimisation:

• Geographical NW visualisation and analysis•Actual and planned configuration on a map•Performance measurements with elements from GSM and

WCDMA networks

• Manual optimisation•GIS based adjacency management•Browser based parameter management•Synchronised with CM Editor

• Automated optimisation•Seamless integration with

optimisation solutions

Optimizer Features

NW wide optimisation

Map data

Cell coveragesGraphical map

KPI dataConfiguration

dataRules

Consistency checks

CellParameters


Optimizer Interfaces

Interfaces overview Interfaces with RAC Interfaces with Reporter Preliminary tasks


Optimizer - Interfaces and Data Flow

Optimizer

PM DataPM Data

CM DataCM Data

SITE and ANTESITE and ANTE

RACUpload ACTUALsProvision Plans

xml

Q.3

Planner

ReporterAdministration of

Measurements, e.g.•Channel Finder

•Defined Adjacencies

OSS Database

OptimizerDatabaseOptimizerDatabase


Network Data and Non-Network Data

Optimizer

PM DataPM Data

RAC DatabaseCM Data

RAC DatabaseCM Data

SITE and ANTESITE and ANTE

OSS Database

OptimizerDatabaseOptimizerDatabase

RAC Database

Non-network Datae.g. Antenna data (bearing, tilt, height)

Network Data

Reporter Database

Antenna data:Radiation pattern

Import


Interworking with RAC and Reporter

• Optimizer obtains the actual or planned GSM configuration data from Radio Access Developer part of RAC

• Actual: e.g. frequency allocation• Planned: e.g. adjacencies for new BTSs

• Performance statistics are retrieved from Reporter • Internal access to PM database• Selected set of KPIs for optimisation needs• The same KPIs as in Reporter

• Optimizer combines the selected CM & PM information • together with optimisation specific data• User input for guiding the algorithms • optimisation targets• User specific map and browser view customisation

• optimisation results are stored as plans in RAC DB• Common RAC functionality for plan management and

provisioning• Further plan processing in CM Editor, CM Analyser and CM

Provisioner


CM DataCM Data

BSC

RNC

CM Plan ManagerCM EditorCM AnalyserCM Provisioner

Upload ManagedObjects

TopologyBrowser

Optimizer

Adminstrationof Measurements

PM DataPM Data

RAC

Reporter

Interworking with RAC and Reporter

BSC


• Actual configuration data is presented in Navigator each time when Optimizer is opened

• Regularly synchronised with RAC database• Object parameters identical in Optimizer and CM Editor

• GSM network objects• BSC• BCF• BTS, ADCE, TRX, ANTE• Site• HOC• POC

• RAN objects• RNC• WBTS• WCell• ADJW, ADJG, ADJS, ADJI• Site

Configuration data for Optimizer 1.1


KPIs from PM database

• Reporter collects the data from network and stores the countersDedicated KPIs provided in Reporter for different purposesOptimizer Report defined containing KPIs needed for optimisationKPIs are calculated based on scripts defined in Report Builder

• Selected KPIs from yesterday and last week are copied automatically to Optimizer database over night

Fixed set of GSM, GPRS and WCMDA RAN KPIs Common KPI formula in all Reports and Optimizer keeps the

consistency

• Interference measurement data as an exceptionCF and DAC measurements are activated in BSC only when neededResults are retrieved from PM database to Optimizer by request

via a separate interface (IM creation)Possible to provide the data also from an external tool (IM import)


Why Mobile Measurement Based Optimisation Features?

• In most of the planning tools the radio environment (interference matrix etc) is estimated with predictions

• Predictions can be made quite accurate if all models are very accurate and tuned

• Propagation model, map data, antenna model

• Optimizer uses predictions mainly for visualisation and analysis. The decisions are made based on measurements

• However the best accuracy and the best coverage of the measurements can be done with Mobile Measurements

• Coverage: the interference data is reported where the mobiles really are

• Standard MMRs (Mobile Measurement Reports) are used


Preliminary tasks


Contents

• Check the Network Configuration Data• Create Parameter Templates• Managing Measurement Data


Optimising a Network Using OptimizerOverview of the preliminary tasks

Start

Check the network configuration dataCM Editor

Create parameter templatesCM Editor

EndManaging Measurement DataOptimizer


Checking the network configuration data

Importing Site and Antenna data Check co-ordinate settings of SITE objects Check the settings for the ANTE objects


Import SITE and ANTE objects

Site import(using Plan Manager)

Antenna import(using Plan Manager)

Merge non NW data(using Plan Manager)

SITE XML file Antenna XML file

Coordinates•Logitude •Latitude

Antenna•Bearing•Tilt•Height

Import Type:SITE information

Import Type:Plans

Note: The radiation patterns need to be imported separately to Optimizer from the planning tool.


Checking the ANTE-objects in CM Editor


Checking the SITE-objects in CM Editor


Checking ANTE-objects in Optimizer


Creating parameter templates for new adjacencies

Template Management in CM Editor Create a new template in CM Editor Assign different templates to managed objects in CM Editor


Template Management in CM Editor


Managing measurement data

Process of preparing and activating measurements Concepts and purpose of BA list Configuring a BA list using MML and CM Editor Required measurements in BSC for frequency plan creation Checking the prerequisites in BSC for starting the measurements Starting measurements with Administration of Measurements


Preparation & Measurements activation

Benchmark the NW for comparison (KPIs)

Obtain BCCH allocation lists information from the NW area

to be optimized

Create new BA Lists

Activate CF and DAC measurements and ensure that traffic and HO measurements

are running

Schedule provisioning the configuration Plans to RNW

START

Create configuration Plans to attach and activate BA lists to

BSCs

Retrieve Measurement reports and generate Interference

Matrix

CM Editor

CM Provisioner

Administration of

measurements

Optimizer 1.1

Covered in chapter“Creating frequencyPlan with Optimizer”


Concept and purpose of BA List

•Obtain the exiting BA-list (e.g. using Network Doctor) to investigate how the adjacencies are defined for each serving cell. *)•The existing BA lists contain only the BCCHs of the defined adjacency cells.•The reason for creating new BCCH Allocation lists is to retrieve also measurement data from surrounding cells which are not defined as adjacency cells.•These new defined BA lists are used only during the Measuring period and should be removed after the measurements are completed.•A new BA list can be created using MML or CM Editor (plan based).

*)Note: This is only important if the total amount of used BCCHs in the NW to be optimized exceeds 32. If less than 32 BCCHs are used then there is no need for this process step


•ADJACENCY OPTIMIZATION

•HO PERFORMANCE

•TRAFFIC

•DEFINED ACJACENCY CELL MEASUREMENTS *

•CHANNEL FINDER MEASUREMENTS *

•INTERFERENCE MATRIX GENERATION

•DEFINED ACJACENCY CELL MEASUREMENTS *

•CHANNEL FINDER MEASUREMENTS *

* DAC and CF measurements have to be explicit activated during the optimization process

Measurements for NetAct Optimizer


BSC

X

B (f11, f25, f31)C (f7, f15)D (f1, f5, f12)

E (f9, f15, f6)

G (f3, f29, f8, f25)

H ( f22, f28, f2) A (f24, f33)

480 ms

defined

defined

defined

defineddefined

BCCH

Un-defined

Un-definedReporter

• MSs scan the whole BCCH block• Cell identifiers are BCC, NCC, BCCH• Reports collected to BSC• Data analysis and thresholds provide adjacent cell rankings for each measured cell

Undefined and Defined Adjacent Cell Measurement


Adjacency Creation/Deletion Measurements

BSC

BTS

BALBAL BALBAL BALBAL

BAL = All BCCH

BCCH of undefinedcells

...and definedadjacent cells

Active MS

• In addition to Defined/Undefined Adjacent Cell Measurements Adjacency Creation and Deletion uses:

1. Handover traffic percentage

2. Handover attempts to adjacent cell

3. Handover success to adjacent cell


Start Administration of Measurements


Preliminary Tasks Summary

• Import sites and antennas (CM Plan Manager)

• … or create sites and antennas (CM Editor)

• Assign sites to network elements (CM Editor)

• Create Cell Antenna Links GCAL and WCAL (CM Editor)

• Create templates for cells and adjacencies (CM Editor)

• Plan BA lists for measurements (CM Editor)

• Define and activate CF and DAC measurements(Top Level UI -> Utils -> Administration of measurements)

• Reset BA lists (CM Editor)

Documents

1 Optimizer Introduction&Setup