02 02 RN20222EN13GLN0 Assessment

Assessment
RN2022-13N
RANOP – Radio Network Optimization Principles
Assessment
1 © Nokia Siemens Networks RN20222EN13GLN0
RN20222EN13GLN0 1
Assessment
Objectives
At the end of the this chapter participants will be able to
• know what is network assessment

• know why network assessment is needed
• know how to collect data for assessment
• know which data to collect from OSS
• know which tools can be used for assessment
RN20222EN13GLN0 2
Assessment
Contents of RANOP
• Introduction to optimization
– What is network optimization
– What should be taken into account when starting Network
Optimization?
•Assessment
– Situation at the moment
• KPIs and Measurements
– Measurement tables + KPIs
• Solution findings (optimization) and verification
– Maximum gain in limited time
– Bottlenecks
• Features to be considered
– NSN recommended features to be used in optimization
RN20222EN13GLN0 3
Assessment
Assessment – table of contents
• Configuration Assessment
– Introduction / dependency table example
– Area assessment
– Network assessment
• Parameter Assessment
– Parameter values
– Default and specific values
– Parameter checks (default and specific parameters)
– Consistency checks & delta values
– Frequencies (planning tool vs. real network values)
– Parameter discrepancies
– Feature assessment
• Performance Assessment
– Benchmarking KPIs used
– Performance Data analysis
– Multi vendor KPI
– Field Tests
– Alarms
• Tools to be used
RN20222EN13GLN0 4
Assessment
More detailed inputs

(if necessary) based
INPUTS on assessment
Performance Project Assessments &

Solutions
Problems Starts Analysis
Assessment - Introduction
Solution
Implementations Work orders Priorization
Verification
Are Criteria’s Monitoring /

Fulfilled Analysis Solutions
Data collection
Project
report
Project
Ends

Performance Project Assessments Solutions

Problems Starts
Solution
Verification Assessment
Configuration assessment
Are Criteria’s
No Parameter assessment
Monitoring /
Performance assessment
Data collection
Yes Project
report
Project
Ends
RN20222EN13GLN0 5
Assessment
Configuration Assessment
RN20222EN13GLN0 6
Assessment


Solutions
Configuration Assessment – Introduction

Solution
Verification

Data collection
Project
report
Project
Ends
Why configuration assessment is needed?

• It supports optimization decisions
– It gives information which features can be implemented
 If there are some limitations, dependency table, these should be
known
 If AMR project and lots of Talk Family BTSs
– It gives information, how much capacity can be increased
 If there are some limitations. Can same BTS cabinet be used if
additional TRX will be added
 Are TRXs supporting EDGE=
 Can HR be used?
• It specify targets and inputs
– It gives information if special resources / knowledge will be needed
RN20222EN13GLN0 7
Assessment


Solutions
Configuration Assessment –
Solution
Verification

Data collection
Dependency table example

Project
report
Project
Ends
DTM – Dual Transfer Mode in BSC
BTS BTS BTS

BSS BSC
Flexi EDGE UltraSite MetroSite
Release BSS12 S12 No dependency No dependency No dependency
BTS BTS BTS 2nd Gen

TalkFamily PrimeSite InSite BTS
Release No dependency Not supported Not supported Not supported
SGSN MCS BSC NetAct

BSC2i or BCS3i
Release SG5 or later M11 or later OSS4.1
PCU2
RN20222EN13GLN0 8
Assessment


Solutions
Configuration Assessment –
Solution
Verification

Data collection
Feature to Feature Dependency table example

Project
report
Project
Ends
Some examples of feature to feature dependencies

• DTM
– GPRS,EDGE must be implemented before DTM can be used
– BSC2i or BSC3i / PCU2
• HMC
– 3GPP release 4 or earlier MSs are limited to combined DL/UL TSL sum
of 5
• DFCA
– DFCA requires BSS synchronization assuming that a Location
Measurement Unit (LMU) unit is installed in every BTS site with DFCA.
RN20222EN13GLN0 9
Assessment


Solutions
Configuration Assessment – Area assessment

Solution
Verification

Data collection
Project
report
Project
Ends
• Situation in general
• Area size
• Antenna types …
• Capacity situation in general

• # of sites
• # of cells, segments…
• Network element types and software:

• BTS / BSC types & SWs
• PCU types
• Volume of network element and connectivity usage of

network elements:
• # of BSCs
• Average DAP size/BCF, SS7 link sizes etc…
• The following information should be collected related to

terminals used in the network:
• Ratio of AMR capable terminals
10 • Ratio of R97, R98,
© Nokia Siemens Networks R99, R4 capable terminals …
RN20222EN13GLN0
RN20222EN13GLN0 10
Assessment


Solutions
Configuration Assessment – Network Element

Solution
Verification

Data collection
Assessment
Project
report
Project
Ends
• Sites / cells (Site database)

• Site, cell names with IDs
• BTS configurations
• Antenna types, azimuths, heights, feeder lengths
• Location, coordinates and addresses
• MSC, BSC, LAC, RAC parameters, TX powers
• E1/T1s
• BTS HW Assessments
• Which HW versions are in use in certain site
• BSC
• BSC name and type
• BSC Utilization and max capacity
RN20222EN13GLN0 11
Assessment
Parameter assessment
RN20222EN13GLN0 12
Assessment


Solutions
Parameter assessment – Parameter values

Solution
Verification

Data collection
Project
report
Project
Ends
Generic process of parameter collection
Upload BSC Take BSC Define Run Generate

Actual XML Audit Audit XML
Configuration Dump Template Script Output
RN20222EN13GLN0 13
Assessment


Solutions
Parameter assessment – Parameter values

Solution
Verification

Data collection
Project
report
Project
Ends
Following parameters should be collected to get full

parameter assessment
ACP BTS LMUA RTSL

ADJC/ADCE DAP MA/MAL SG
ANE GPC NS_VC SMLC
BA/BAL HOC NSE TRK_TBL/TRKT
BCF IO_TEXT/TID PCU TRX
BSC LAC to SPC POC UADJC/ADJW
BTS LCSE RA
SS7 signalling network parameters

Parameters of X.25
Parameters of CLNS
PAFILE
PRFILE and FIFILE
RN20222EN13GLN0 14
Assessment


Solutions
Parameter assessment – Default and specific

Solution
Verification

Data collection
parameter values
Project
report
Project
Ends
Default Parameter Values:

• Almost all parameters are set to
default values
• Default values are defined based
on studies
Specific Parameter Values:

• Special solution for certain area
• Default values are not working well
• Changes might be quite dangerous as
they may have a critical impact on the
network.
• It is not recommended to fix side-
effects of the special values by setting
special values
RN20222EN13GLN0 15
Assessment


Solutions
Parameter assessment – default parameter check

Solution
Verification

Data collection
Project
report
Project
Ends
Default parameter check
• Export Actual Default Parameters from the OSS through a xml file, for e.g.
• Use always latest default values (based on latest studies)
• Import xml file into a Database using for e.g. CM Plan Editor.
• Compare Planned Default Sets with Actual Default Parameters in the
network.
• Mark exceptions for each default parameter
• Show differences
• Select changes to be done
• Create dat file or xml file for correction
Note! It is very important to verify if any changes to Default Parameters

has been done before any optimization, as this may result in undesired and
unexpected impacts on the network.
RN20222EN13GLN0 16
Assessment


Solutions
Parameter assessment – Specific parameter check

Solution
Verification

Data collection
Project
report
Project
Ends
Specific
Parameter area
Specific
Parameter area
Specific Specific
Parameter area Parameter area
Specific
Parameter area
Hmm! Do I really handle

all these specific
relationships?
If lots of specific parameters in the

network. What kind of problems might
exists?
RN20222EN13GLN0 17
Assessment


Solutions
Parameter assessment – Consistency check

Solution
Verification

Data collection
Project
report
Project
Ends
OSS Master configuration Consistenc

Parameter database y check
file Imp
or t o
Exp rt
actual specific
CMDatabase
Database actual default Consistency
CM
check
Imp default
o rt rt
Expo
Parameter
planned
file
Consistenc
import y check
Parameter
file
Mapinfo export
NetAct Planner
ODBC Planning
database
RN20222EN13GLN0 18
Assessment


Solutions
Parameter assessment – Consistency check

Solution
Verification

Data collection
Project
report
Project
Ends
• Delta values, planning tool values, network values (next slide)

– All values should be as planned
– For example frequencies, BSICs, neighbors …
• Delta values, network values vs. default/recommended values
– If not specific values, parameter values should be set as default value.
– BSC, BTS, GPRS, POC, HOC …
• Discrepancies
– Neighbor parameters
• Non symmetrical neighbors (slide)
– BTS parameter vs. adjacent parameters
RN20222EN13GLN0 19
Assessment


Solutions
Parameter assessment – Frequencies - Planning

Solution
Verification

Data collection
Project
report
Project
Ends
Tool values vs. network values
If there are some delta between network and planned values,

consequences might be fatal.
Planning tool values Network values
100,99 100,99
96,92 96,92
112,88 115,88
78,72 78,72
75,115 75,115
Same channels (115)
1 TRX should => bad interference!!
81,110 be added 81,110
RN20222EN13GLN0 20
Assessment


Solutions
Parameter assessment – discrepancies

Solution
Verification

Data collection
Project
Non symmetrical adjacencies

report
Project
Ends
Find all non symmetrical adjacencies :

• cell B is neighbour of Cell A
• cell A is not neighbour of Cell B
Cell A Cell B
RN20222EN13GLN0 21
Assessment


Solutions
Parameter assessment – discrepancies

Solution
Verification

Data collection
N-BCCH in ADCE table against FREQ in TRX table

Project
report
Project
Ends
TRX
BSC id BTS id TRX id FREQ

fA
N-Neighbour
ADCE
fAB BSC id BTS id N-LAC N-Cell id N-BCCH
Cell A Cell B fAB

fA
Applies also to other cell parameters !!
RN20222EN13GLN0 22
Assessment


Solutions
Parameter Assessment – BSS Feature

Solution
Verification

Data collection
Assessment
Project
report
Project
Ends
The following features must be checked and interworking issues must be

emphasized among features below:
– Idle mode settings and Directed Retry

– BB and RF Hopping
– MultiBCF and Common BCCH
– Umbrella
– FR / HR / DR / AMR
– HSCSD
– Extended Cell
– Intelligent Underlay Overlay
– Priority based QoS
– NMO1
– NCCR
– CS1-4
– NACC
– DFCA
– DTM
RN20222EN13GLN0 23
Assessment
Performance Assessment
RN20222EN13GLN0 24
Assessment


Solutions
Solution
Verification

Data collection
Introduction
Project
report
Project
Ends
• Why Performance assessment is needed?

• Performance assessment is needed to get clear picture
about network functionality and find the possibilities for
increasing the performance.
• Challenges
• Missing data
– If some hourly data is missing – difficult to find out without hourly
analysis
– All tables are not activated
– All tables can not be found from OSS
RN20222EN13GLN0 25
Assessment


Solutions
Solution
Verification

Data collection
Benchmarking KPIs used

Project
report
Project
Ends
• Bencmarking KPIs
– Is recommended for reporting
– Release specific
• Customer KPIs
– Almost all operators have operator specific KPIs.
– Important KPIs because optimization is done for customer
• Limitations
– SW Release limitation
 There might be errors in results if wrong KPIs will be used
– Feature limitations
 There might be errors in results if wrong KPIs will be used
 For example if HR is not used
RN20222EN13GLN0 26
Assessment


Solutions
Solution
Verification

Data collection
Performance data analysis

Project
report
Project
Ends
Performance data measurements and analysis are

usually separated to
• OSS Performance data
• Statistics
• Benchmarking KPIs
• Multi Vendor KPI
• Alarms
• Customer complaints
• Drive Test Analysis
• Planning tools
• Executive Summary & Overview
RN20222EN13GLN0 27
Assessment


Solutions
Solution
Verification

Data collection
Statistics
Project
report
Project
Ends
Strong points +
• Allows centralized data collection
• A cost efficient way to monitor network quality
• Pro-Active
• Selective performance monitoring (e.g. after new feature activation)
• Permanent information flow
• Useful to monitor trends
• Locate problems on a per-cell level
Weak points -
• Needs statistically relevant traffic volume to provide reliable results
• Limited geographical location of problems is possible
• Can be difficult to understand the meaning of the counters
RN20222EN13GLN0 28
Assessment


Solutions
Solution
Verification

Data collection
Benchmarking KPIs - CS
Project
report
Project
Ends
OSS counter and CS KPI analysis gives exact picture about network
performance. The analysis of CS KPIs can be based on the following list:
• Accessibility
– SDCCH access KPIs S13 EDGE, GPRS, and
– TCH, SDCCH Blocking KPIs GSM KPIs can be seen
– HO failure due to blocking here
• Retainability
– TCH, SDCCH drop KPIs
– Total HO failure, HO drops
• Quality
– UL/DL Quality KPIs KPIs
• Traffic share
– TCH, SDCCH Traffic sum
– AMR traffic share
RN20222EN13GLN0 29
Assessment


Solutions
Solution
Verification

Data collection
Benchmarking KPIs - PS
Project
report
Project
Ends
OSS counter and PS KPI analysis gives exact picture about network performance. The analysis
of PS KPIs can be based on the following list:
• Network Usage
– UL/DL PS Traffic
– UL /DL Payloads
• PDTCH Congestion
– DL hard/soft blocking
• Abis/PCU Congestion
– Inadequate EDAP resources in DL
– DL MCS selection limited by PCU
• PDTCH Quality
– UL/DL (E)GPRS RLC throughput
– TBD Success ratio
• Mobility
– Downlink flush per minute
• Availability
– Data service availability ratio
• User Experience
– LLC Throughput
RN20222EN13GLN0 30
Assessment


Solutions
Solution
Verification

Data collection
Benchmarking KPIs - PS
Project
report
Project
Ends
• QoS
– TBF establishment/success ratio
• Connectivity capacity
– DL MCS selection KPIs
• Mobility
– DL Flush
• E2E data rate
– LLC Throughput
– Volume weighted LLC throughput
RN20222EN13GLN0 31
Assessment


Solutions
Solution
Verification

Data collection
Customer Complaints
Project
report
Project
Ends
Strong points +
• Good co-operation between network optimization and customer service department is
necessary
• Helps to find not known problems
• Helps to confirm known problems
• Might pinpoint location of problem
• Reports indoor coverage holes
• May trigger fast decision from management in case heavy users are involved
• Problems with specific mobiles
• Problems of mobile configuration
Weak points -
• Reacting to customer complaints is reacting too late
• Not efficient for optimizing a whole network
• Difficult to distinguish between mss and bss problems
E.g.: Errors in the numbering plan can only be detected from Customer Complaints!
RN20222EN13GLN0 32
Assessment


Solutions
Solution
Verification

Data collection
Project
Multi Vendor KPI

report
Project
Ends
Multi Vendor KPI comparison is like comparing

apples and kiwis
Strong points +
• Performance can be compared by using statistics
Weak points -
• Counter trigger points might be different
• Calculation methods might be different
– Are we calculating fails or (all attempts - successful
attempts)
RN20222EN13GLN0 33
Assessment


Solutions
Solution
Verification

Data collection
Project
Field Tests
report
Project
Ends
Drive Test Software
Pre-defined route GPS Indoor antenna
Outdoor antenna
Network 1
Another way of measuring the target network performance

Necessary in different steps of optimisation
Drive Test process consists on:
1. Doing the test and collecting the logs
2. Post-processing these logs
3. Analysis of Drive Test
RN20222EN13GLN0 34
Assessment


Solutions
Solution
Verification

Data collection
Project
report
Field Tests
Project
Ends
Strong points +
• Helps to adjust propagation models
• Troubleshooting
• Detects problems that can be masked by statistics
• Graphical reports on maps that allow to easily identify “hot areas”
• Monitoring and validation of new functionalities or changes done in the network
• Identify coverage problems, meaning both coverage holes and cells covering less or more than
wanted. Used in antenna tilting optimisation.
• Finding interference (difficult to measure) and bad quality.
• Detecting adjacency problems:
– Missing neighbours
– Unnecessary or unwanted neighbours
– Incorrectly defined adjacencies.
• Finding hardware problems:
– Crossed sectors.
– Mixed antenna lines.
– Faulty units (TRXs, BBUs, etc).
– Imbalance problems (e.g., due to ROE in cables or jumpers).
RN20222EN13GLN0 35
Assessment


Solutions
Solution
Verification

Data collection
Project
Field Tests
report
Project
Ends
Weak points -
• Very resource and time consuming, making it expensive to monitor wide
areas and sometimes restricts DTs to specific areas
• QoS monitoring from moving subscriber point of view. Gives a feeling of
customer view, although slow moving MS, indoor MS, high floor MS are not
taken into consideration
• Supplies in most cases only downlink information
• Snap-shot in time
• Statistics can be influenced by the velocity of the driver in good areas and in
bad areas.
RN20222EN13GLN0 36
Assessment


Solutions
Solution
Verification

Data collection
Project
Field Tests examples

report
Project
Ends
• CS
– Coverage
– Quality - Interference
– HO measurements
– CSSR with short call duration
– Traffic handling measurements
• PS
– PSW accessibility analysis
• GPRS attach / PDP content activation / TBF establishment
– Throughput analysis – Stationary
• Average throughput (RLC/MAC and Application)
• MCS distribution
• BLER ,C/I ratio
– Throughput analysis – Mobility (intra/inter PCU and RAU cell-reselection)
• LLC, RLC/MAC
37 © Nokia Siemens Networks
• Retransmission
RN20222EN13GLN0
based on cell re-selection
RN20222EN13GLN0 37
Assessment


Solutions
Solution
Verification

Data collection
Project
Optimizer
report
Project
Ends
Problems cells based on interference matrix from Optimizer
RN20222EN13GLN0 38
Assessment


Solutions
Solution
Verification

Data collection
Project
Executive Summary and Overview

report
Project
Ends
In performance assessment report following items should be

mentioned
• Executive summary
– Strengths
– Weakness
• Overview
– All KPIs with values should be listed
– Network level & BSC level
– Main causes for problems should be mentioned
RN20222EN13GLN0 39
Assessment


Solutions
Solution
Verification

Data collection
Project
Alarms
report
Project
Ends
In assessment report all main active alarms can be mentioned:

* Low Priority
** Med Priority
*** High Priority
Note! Check also if any blocked / filtered alarms
If there are lots of active alarms, collected data is not valid
• Performance data is not reliable
• Optimization targets are based on wrong inputs
 Optimization can be started when (most of) critical active

alarms have been solved
RN20222EN13GLN0 40
Assessment
Tools to be used
RN20222EN13GLN0 41
Assessment


Solutions
Tools to be used
Solution
Verification

Data collection
Project
report
Project
Ends
Example of tools to be used in assessment phase

• Configuration data
– NetAct tools (Plan Editor, CM Plan Manager etc)
– Planning tools (NetAct Planner, Asset, etc)
• Performance data
– Statistics (Reporting Suite, Metrica, Report Builder etc)
– Drive test (Nemo Outdoor. TEMS, Actix etc)
• Parameter assessment
– NetAct tools (Plan Editor, Reporting Suite etc
– Planning tools (NetAct Planner, Asset, etc)
RN20222EN13GLN0 42

02 02 RN20222EN13GLN0 Assessment

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

02 02 RN20222EN13GLN0 Assessment

Hochgeladen von

Copyright:

Verfügbare Formate

Assessment

1 © Nokia Siemens Networks RN20222EN13GLN0

At the end of the this chapter participants will be able to

• know what is network assessment

2 © Nokia Siemens Networks RN20222EN13GLN0

3 © Nokia Siemens Networks RN20222EN13GLN0

Assessment – table of contents

4 © Nokia Siemens Networks RN20222EN13GLN0

More detailed inputs

Performance Project Assessments &

Are Criteria’s Monitoring /

More detailed inputs

Performance Project Assessments Solutions

6 © Nokia Siemens Networks RN20222EN13GLN0

More detailed inputs

Performance Project Assessments &

Configuration Assessment – Introduction

Are Criteria’s Monitoring /

Why configuration assessment is needed?

7 © Nokia Siemens Networks RN20222EN13GLN0

More detailed inputs

Performance Project Assessments &

Are Criteria’s Monitoring /

Dependency table example

DTM – Dual Transfer Mode in BSC

BTS BTS BTS

Release BSS12 S12 No dependency No dependency No dependency

BTS BTS BTS 2nd Gen

Release No dependency Not supported Not supported Not supported

SGSN MCS BSC NetAct

8 © Nokia Siemens Networks RN20222EN13GLN0

More detailed inputs

Performance Project Assessments &

Are Criteria’s Monitoring /

Feature to Feature Dependency table example

Some examples of feature to feature dependencies

9 © Nokia Siemens Networks RN20222EN13GLN0

More detailed inputs

Performance Project Assessments &

Configuration Assessment – Area assessment

Are Criteria’s Monitoring /

• Capacity situation in general

• Network element types and software:

• Volume of network element and connectivity usage of

• The following information should be collected related to

More detailed inputs

Performance Project Assessments &

Configuration Assessment – Network Element

Are Criteria’s Monitoring /

• Sites / cells (Site database)

11 © Nokia Siemens Networks RN20222EN13GLN0

12 © Nokia Siemens Networks RN20222EN13GLN0

More detailed inputs

Performance Project Assessments &

Parameter assessment – Parameter values

Are Criteria’s Monitoring /

Generic process of parameter collection

Upload BSC Take BSC Define Run Generate

13 © Nokia Siemens Networks RN20222EN13GLN0

More detailed inputs

Performance Project Assessments &

Parameter assessment – Parameter values

Are Criteria’s Monitoring /

Following parameters should be collected to get full