Optimizer Introduction Setup

8/12/2019 Optimizer Introduction Setup

1/30

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

Optimizer Introduction


2/30


Contents

Optimizer Overview

Optimizer Interfaces

Optimisation workflow in NetAct


3/30

Configuring

ServiceManagement

Security & SystemManagement

Planning

SubscriptionManagement

Reporting

Adaptation

Multitechnology & MultivendorNetworks

Multiservice,

OptimisingMonitoring

NokiaNetAct

Functionality areas of NetAct

Functionality area


4/30


Optimizer target is to provide GSM/GPRS/WCDMA functionality for maximising NW capacity utilisation rate

optimising the service performance with minimum manual effortThe application combines means for NW analysis and optimisation:

Geographical NW visualisation and analysisActual 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 cov erages

Graphical map

KPI dataConfiguration

data

Rules

Consistency checks

CellParameters


5/305 NOKIA / Preliminary tasks in Optimizer / 6-137228 / version 2.0 en / 05.05.2004 / Bettina Baacke

Optimizer Interfaces

Interfaces overview

Interfaces with RAC

Interfaces with Reporter

Preliminary tasks



Optimizer - Interfaces and Data Flow

Optimizer

PM Data

CM Data

SITE and ANTE

RACUpload ACTUALsProvision Plans

xml

Q.3

Planner

ReporterAdministration of

Measurements, e.g.

Channel FinderDefined Adjacencies

OSS Database

OptimizerDatabase



Network Data and Non-Network Data

Optimizer

PM Data

RAC DatabaseCM Data

SITE and ANTE

OSS Database

OptimizerDatabase

RAC Database

Non-network Data

e.g. Antenna data(bearing, tilt, height)

Network Data

Reporter Database

Antenna data:

Radiation patternImport



Interworking with RAC and Reporter

Optimizer obtains the actual or planned GSM configuration datafrom 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 CMProvisioner



CM Data

BSC

RNC

CM Plan Manager

CM Editor

CM Analyser

CM Provisioner

Upload ManagedObjects

Topology

Browser

Optimizer

Adminstrationof Measurements

PM Data

RAC

Reporter

Interworking with RAC and Reporter

BSC


10/30


Actual configuration data is presented in Navigator each time when Optimizer isopened

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


11/30


KPIs from PM database

Reporter collects the data from network and stores the counters

Dedicated KPIs provided in Reporter for different purposesOptimizer Report defined containing KPIs needed for optimisation

KPIs are calculated based on scripts defined in Report Builder

Selected KPIs from yesterday and last week are copied automatically toOptimizer database over night

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

consistency

Interference measurement data as an exception

CF and DAC measurements are activated in BSC only when needed

Results are retrieved from PM database to Optimizer by request via aseparate interface (IM creation)

Possible to provide the data also from an external tool (IM import)


12/30


Why Mobile Measurement Based OptimisationFeatures?

In most of the planning tools the radio environment (interference

matrix etc) is estimated with predictions Predictions can be made quiteaccurate if all models are very

accurate and tuned

Propagation model, map data, antenna model

Optimizer uses predictions mainly for visualisation andanalysis. The decisions are made based on measurements

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

Coverage: the interference data is reported where the

mobiles really are

Standard MMRs (Mobile Measurement Reports) are used


13/30


Preliminary tasks


14/30


Contents

Check the Network Configuration Data

Create Parameter Templates

Managing Measurement Data

O ti i i N t k U i O ti i


15/30


Optimising a Network Using OptimizerOverview of the preliminary tasks

Start

Check the network configuration dataCM Editor

Create parameter templatesCM Editor

EndManaging Measurement DataOptimizer


16/30


Checking the network configurationdata

Importing Site and Antenna data

Check co-ordinate settings of SITE objects

Check the settings for the ANTE objects


17/30


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

LogitudeLatitude

AntennaBearing

TiltHeight

Import Type:SITE information

Import Type:Plans

Note: The radiation patterns need to beimported separately to Optimizer from theplanning tool.

Checking the ANTE objects in CM


18/30


Checking the ANTE-objects in CMEditor


19/30


Checking the SITE-objects in CM Editor


20/30


Checking ANTE-objects in Optimizer


21/30


Creating parameter templates fornew adjacencies

Template Management in CM Editor

Create a new template in CM Editor

Assign different templates to managed objects in CM Editor


22/30


Template Management in CM Editor


23/30


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 themeasurements

Starting measurements with Administration of Measurements

Preparation & Measurements activation


24/30


Preparation & Measurements activation

Benchmark the NW for comparison(KPIs)

Obtain BCCH allocation listsinformation from the NW area to be

optimized

Create new BA Lists

Activate CF and DAC measurementsand ensure that traffic and HO

measurements are running

Schedule provisioning theconfiguration Plans to RNW

START

Create configuration Plans to attach

and activate BA lists to BSCs

Retrieve Measurement reports andgenerate Interference Matrix

CM

Editor

CMProvisioner

Administration ofmeasurements

Optimizer1.1

Covered in chapterCreating frequency

Plan with Optimizer

C t d f BA Li t


25/30


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 definedadjacency cells.The reason for creating new BCCH Allocation lists is to retrievealso measurement data from surrounding cells which are notdefined as adjacency cells.These new defined BA lists are used only during the Measuringperiod and should be removed after the measurements arecompleted.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 BCCHsin the NW to be optimized exceeds 32. If less than 32 BCCHsare used then there is no need for this process step

Measurements for NetAct Optimizer


26/30


ADJACENCY OPTIMIZATION

HO PERFORMANCE

TRAFFIC

DEFINED ACJACENCY CELL MEASUREMENTS *

CHANNEL FINDER MEASUREMENTS *

INTERFERENCE MATRIX GENERATIONDEFINED ACJACENCY CELL MEASUREMENTS *

CHANNEL FINDER MEASUREMENTS *

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

Measurements for NetAct Optimizer

Undefined and Defined Adjacent Cell


27/30


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)

defined

defined

defined

defineddefined

BCCH

Un-defined

Un-definedReporter

MSs scan the whole BCCH block

Cell identifiers are BCC, NCC, BCCH

Reports collected to BSCData analysis and thresholds provide adjacent cell rankings for each measuredcell

Undefined and Defined Adjacent CellMeasurement

Adjacency Creation/Deletion


28/30


Adjacency Creation/DeletionMeasurements

BSC

BTS BAL BAL BAL

BAL = All BCCH

BCCH of undefinedcells

...and definedadjacent cells

Active MS

In additiontoDefined/Undefined AdjacentCell MeasurementsAdjacency Creation andDeletion uses:

1. Handover traffic percentage2. Handover attempts to

adjacent cell

3. Handover success toadjacent cell

St t Ad i i t ti f M t


29/30


Start Administration of Measurements

Preliminary Tasks Summary


30/30


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)

Optimizer Introduction Setup

Documents