UTRAN Optimization Process

All Rights Reserved © Alcatel-Lucent 2006, #####

 Agenda

• Global Optimization Process

• Post-Launch Optimization Process
• Optimization Tools
1
Global Optimization Process
4
Network Deployment:::

5
Pre-Launch Optimization:

6
Cluster Optimization:Data and Voice

7
Cluster Optimization:3G-2G:

8
Network Acceptance:

9
 Summary of Optimization Objective

• Optimization aims at improving the network performance and/or

capacity
To improve the system initial performance
Pre-launch phases
To reach acceptance criteria
To enhance the subscriber satisfaction
Post-launch phases
To increase the number of subscribers

• Methods differ for :

– Pre-launch optimization (performed for acceptance, trials)
– Post-launch monitoring and optimization (performed for in-service networks)
• Pre-launch Optimization
– The main objective is to reach agreed network key performance indicators by validating sites
functioning and by performing network optimization
FTP
HTTP
PING
-
- 1
4
7
*
2
5
8
0
3
6
9
#

• Post-launch Optimization
– The main objective is to improve performance of a network influenced by real traffic load,
using system performance data and/or drive tests data

RNC
1 2 3
4 5 6
7 8 9
* 0 #
1 2 3
4 5 6
7 8 9
* 0 #

1 2 3
4 5 6
7 8 9
* 0 #

1 2 3
4 5 6
1 2 3
7 8 9
4 5 6 * 0 #
7 8 9
* 0 #

1
4
7
*
2
5
8
0
3
6
9
#
1
4
7
*
2
5
8
0
3
6
9
#
OAM
 Optimization Steps

Pre-launch optimization Post-launch optimization

KPI Targets
Improvement
Network E2E
optimization
LAUNCH Cluster E2E
Optimization
Final QoS
Network Initial KPI Benchmark
Acceptance Targets
Network E2E Tools
optimization ALU Customer
NPO
Cluster E2E Initial QoS
Optimization Benchmark Call Trace RFO Protocol
Site verification
CTb / Ctg Analyzer
RF Optim
Mobiles Post-Proc.
Trace SW SW RF Planning
Tool
Scanner
3
Post Optimization Process
1. Glossary of terms and abbreviations:

FM Fault Management
CM Configuration Management
PM Performance Measurement
Description of the optimization process:

The different fields of UMTS RF optimization can be summarized by the

following items:

• FM audit and analysis

• RF design audit and optimization
• CM audit and optimization
• PM audit and optimization
• Drive testing and investigation
• Network interface tracing and analysis

These fields of UMTS optimization are displayed in Figure 1 in yellow below.

Figure 1: ALU UMTS optimization process – process flow
Pre-requisite before starting with a performance verification and optimization
is that:
• The FM analysis shows no severe alarms that might influence the
performance measurements as retrieved by the PM statistic or drive
test data.

• The RF design audit and optimization has been finished for the region
to be optimized .
In case, one or both pre-requisites are not fulfilled starting with the
performance investigation and troubleshooting does not make much sense.
For troubleshooting and optimizing new clusters, the Drive test and
interfaces’ traces would be more relevant than PMs that may get skewed
because of small number of users.

17
Fault Management:Check any alarms in sites in using
NSP:
1-Right-click on RNC and show alarms

18
From the NodeB:

19
Check the configuration for any errors or
warning regarding unidirectionnel
neighbouring by using WIPS:
1-Import snapshot of the network.
2-Run Checks.

20
 Cluster Optimization Process

Monitoring (KPI dashboard)

Accessibility
Drive Test Retainability
Scanner trace Mobility
UE Trace Capacity
IMSI trace: CTb Quality

Yes Yes Target Dashboard

Target DT KPI reached No compulsory optimization
KPI reached

No No

HW Change/Addition Parameters Optimization

RF Optimization Accessibility
Cross Feeder
Coverage improvement Call Admission Control
iCEM,xCEM
Interference reduction Radio Resource Management
MCPA
Neighbouring optimization Mobility
E1
Capacity Iub Efficiency
...
HSDPA
 Drive Test Based Optimization

Define drive test routes

Perform DT intra cluster

Check, Analyze, post-process DT raw data
Propose HW and parameters change recommendation

Change Parameter
Aerial Tuning is necessary Open ticket with when an issue is detected
is necessary

Ticket Treatment

Change Parameter
Process Customer Agreement

Aerial Tuning Perform DT until Cluster optimization

is completed and target KPI are met

Perform New DT
Check, Analyze, post-process DT raw data

Provide KPI progress report on a weekly basis

Perform DT until Cluster optimization is complete and KPI targets are met
Exemple of Drive Test Scenario:

 Test in mobility conditions in Tours area with NEMO air interface acquisition

 Scanner Measurement :
– Scanner to collect measurement on UMTS 2100 Band

 Test #1 -> CS AMR Short Call :

– UE Mobile in dual mode
– Long QoS call : s / Idle mode: 60s

 Test #2&3 -> Data FTP UL/DL :

– DataCard in dual mode used for HSDPA & HSUPA test
– Sequence of Download 500Mo file size
– Sequence of Upload 500Mo file size
– Idle mode: 60s between 2 data transfer

 Test #4 -> Idle mode:

– UE Mobile in dual mode

23
 Counter Based Optimization

Monitoring

Accessibility Retainability

Includes all the steps allowing Defines the ability of the network to
the user to access a particular provide reliable service to the end
service user.

Counter
based KPI
Mobility
Quality
Defines the ability of the network to
Defines the ability of the network ensure UE’s calls continuity.
to provide quality transmission of
the user requested services

Traffic

Defines the traffic volume seen on the

network in downlink and in uplink

Monitoring concerns all aspects of QOS

24
 Counter Based Optimization
Check the daily and weekly KPI dashboards

Yes
Target KPI reached No compulsory optimization

No

Check the Worst Cell List

Global Issue or on specific cells

Troubleshooting: additional metrics/counters,

And traces CTg, CTn,CTB,DT (UE/CTb)

(1)No (2)No
Root cause found Open a ticket
Perfrom DT

Yes

Apply corrective actions: HW or parameters change Ticket treatment by high level support

check of the KPI dashboard

4
Optimization Tools
 Optimization Tools Set

IP
OAM
Call RNC
Trace Iu
Iub NodeB
1-RFO+DT
post processing
SW. Workorders
2-Atmspy in case of
Transport
Layer issue.
ALU 3-RNC internal Traces:
ppc logs,TMU traces. ALU ?
4-E.DAT WiPS Protocol
Analyzer

ALU

Data
Collection SW Counters

A9155 NPO
Scanner
UE
ALU
ALU ALU

27 | UTRAN Optimization Process All Rights Reserved © Alcatel-Lucent 2006

 Drive Test Measurement Chain
OUTDOOR

GPS
Magnetic
Antenna

PC with
Acquisition SW
INCAR

Dual Frequency Scanner

R99 UE
HSDPA UE: Option datacard (Qualcom
chipset)
 Call Trace
Call Traces are activated on the OAM GUI. The log files are stored on the Performance Server.
⇒ Used to trace one or several UE calls.
CTa ⇒ UEs selection based the IMSI or the IMEI.
⇒ Activation on Core Network.

⇒ Used to trace the calls related to only one UE. Possible to trace several UEs
CTb by activating several CTb sessions.
⇒ UEs selection is based: on the IMSI or TMSI or P-TMSI or IMEI.
Most used Call Traces

⇒ Activation at the OAM.

⇒ Used to trace calls established within a certain geographical area (one,

CTg several or all the cells of a RNC).
⇒ Calls are traced even if moving outside the defined area.
⇒ Activation at the OAM.

⇒ Used to trace events related to calls’ mobility

CTn ⇒ Events related to traced calls are only logged when the mobile is inside the
defined area.
⇒ No UE identity is required.
⇒ Activation at the OAM.

Trace data related to all elements (events) handled by an object of the network :
 A cell or group of cells
OTCell  Iu CS interface
IU-CS  Iu PS interface
IU-PS  One Neighbour RNC or a group of neighbour RNC
IUR  One RNC
Launch the Call Trace Wizard for UMTS

1.Launch the Call Trace Wizard for UMTS

- Select the RNC network Layout (in menu File/ Select

Network Layout)
- From the - From the Menu Performance/RadioAccess,
Launch the Call Trace Wizard for UMTS
31
32
Geographical Call Trace: CTg

A Geographic Call Trace (CTg) session allows to trace a % of the calls established within a geographical
area in the UTRAN specified during the session activation.
The geographical area in the UTRAN is a list of geographical areas in specified RNSs. RNSs are defined
by their RNC Id.
The geographic area in a RNS may be a cell, a set of cells from the RNS, all the cells in the RNS.
There are therefore no UEs identified in a CTg session creation.
Calls may be traced within a CTg as soon as the trace session is activated and exists.

33 | UTRAN Optimization Process All Rights Reserved © Alcatel-Lucent 2006

Calltrace storage:

The callTrace directory is

/opt/nortel/data/utran/callTrace/”session
Type”(GeographicalArea,.....)/sessionId/
yyyymmdd/calls

Exemple:
/opt/nortel/data/utran/callTrace/ GeographicalArea/
sessionId/ yyyymmdd/calls

34
RFO (RF Optimizer)

Post-processing Tool to analyse data log files from UE acquisition tools and Call Trace.

35 | UTRAN Optimization Process All Rights Reserved © Alcatel-Lucent 2006

 NPO (Network Performance Optimizer)
ALU’s Performance Management Solution.

Allows to monitor the network performance, detect

network issues and troubleshoot them through the
counters.
Collects and stores for long periods of time all the
UTRAN counters.
Includes metrics (indicator based on several
counters) defined by Alcatel-Lucent.
The counters are available at RNC level and/or at
FDDCell level.
Easy report generation (drag & drop).
Pre-defined reports available.

36 | UTRAN Optimization Process All Rights Reserved © Alcatel-Lucent 2006

www.alcatel-lucent.com

All Rights Reserved © Alcatel-Lucent 2006