ALU RF Optim Process

Training session 3
Optimization services
August 2010 )
Alcatel-Lucent W-CDMA Description

All rights reserved 2009, Alcatel-Lucent
Agenda (Radio/optimization operational services)
2
Global Optimization Process

Global view
Mandatory task for new 3G operators
Pre-optimisation (design phase)
Pre-Launch Optimization Process
General view (process/KPI/ressource)
Configuration Audit
Site Audit
Cluster Optimization
Network Optimization
Post-Launch Optimization Process
Optimization Tools
All Rights Reserved Alcatel-Lucent 2009

Workshop OCI Services Optimisation December 2009
1 Global optimisation process
Global view
Mandatory tasks for a new 3G operator

Generic Roll Out Process : RF Design & OPTIMIZATION services
Network Network Network Network Network
targets Radio Implementation Pre launch Post launch 4
hypothesis & Planning Optimisation Optimisation
assumptions
2a - Cell 9a - RF Design 11a - Site 18a - Perf

1a - RF Design Planning Verification Management
analysis
guidelines definition
12a - Cluster RF 19a - Access
3a - Site survey 10a - RF Design optimisation Benchmark
preoptimisation
13a - Network 20a - Monitoring
4a - CW Optimization
Measurement 21a - Access
14a - Access
Parameter parameter
5a Propagation Optimization customization
Model Calibration 22a - E2E audit
15a - E2E
/ Optimization
Optimization
6aGeo.Database 23a - Application
Validation 16a - Application audit/
Optimization Optimization
24a -
7a - Co-siting Densification
studies
17a Configuration 25a -
8a - Spectrum analysis Troubleshooting
Clearance 26a - New feature /
Main Roll Out Step Load Introduction
Support
Associated RF Design & Optimization services
All these services can be delivered through turnkeys, FTE, workshops or OJTs.
Partly covered in design Partly covered in services
WS (day2) (day3) All Rights Reserved Alcatel-Lucent 2009
NDO2009
Workshop OCI Services Optimisation December
Optimization Objective
5
Optimization aims at improving the network performance and/or

capacity
To improve the system initial performance
Pre--launch phases
Pre
To reach acceptance criteria
To enhance the subscriber satisfaction
Post--launch phases
Post
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)

Optimization Steps
6
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 XCAP
XCAL RF Planning
Tool
Scanner
Improvement is easier before launch

2 Pre optimisation (design phase)

WCDMA RF Characteristics compared to GSM
8
Coverage quality sensitive to traffic load.

Capacity usually limited by Down Link Interference.
All neighbor cells are considered as Co Channel interferers =>
Interference Control Critical for all CDMA-based Technologies.
Faster Handoff Processing & Power Control are essential
Coverage control should be exercised at the early design stage
Optimisation need to be done per cluster area (per group of cell): it
means that optimisation must drive site integration
Pilot Ec/Io is the Key metric, not signal Level

Coverage & Interference Control !!

Pre-Optimization principle
9
Pre-requisite.
Design threshold for the most constraining service (UL link budget)
Network downlink load assumption
QoC to be reached (90%, 95%)
Pilot power setting and minimum Ec/Io (DL link budget)
1st step initial setting :
Default tilt to be set by environment (Urban 6,Suburban 4)
Exceptional tilt to be set according to site height (Tilt 8if H>=40m)
2nd step simulation tuning:

Maximize the coverage (based on RSCP level)
Minimize the pilot pollution (based on Ec/Io map & overlapping)
Optimize the overlap (overlapping)
last step :
- Global improvement should be check with all tilts implemented
Pre-Optimization criteria
10
Global definition
RSCP level >= design threshold (98-100% of the area)
Ec/Io>= Ec/Io minimum (90-95% of the area according to QoC)
Less than 4 servers in X dB interval from the best (X=4-8 dB)
3rd server level <= design threshold + Y dB (Y= 6-10 dB), to avoid
overcoverage (impact in HSDPA optimization)
radio criteria example:

RSCP > - 88 dBm (Indoor Daylight, QoC 90%)
Ec/Io > -9 dB (unloaded network)
Less than 4 pilots within a 6dB interval from best server
3rd server coverage less than -78dBm

3 Pre-launch optimisation process
General view (process/KPI/ressource)
Configuration Audit
Site Audit

3G Optimisation Process
Main Steps for pre-launch phase
12
KPI
PREPARATION R99 3G AMR Call drop rate
DL FTP Success rate
RF Design Assessment
UL FTP Success rate
Cluster Definition 3G Video Call Success rate
Acceptance defined
PROCESSES Ready
Cluster RF KPIs
Ready OK OK
Site
I&C Cluster QoS QoS
Verification
NodeB OPTIM. VERIF. Audit
Providing the best RF & system

performance HSDPA
(around Site and inside Cluster/Area)
KPI
Throughput FTP DL
-RF Control
TV Live Success rate
-Mobility / Call Performance
-Parameter Settings

Pre-Launch Optimization Services : Overall process
13
Step 1: RNP Assessment & Site verification

Access all site configuration and assess RNP settings (tilts, neighbour relations)
Project schedule and drive routes defined at this stage for the town.
Perform RF field measurements for each new site:
Coverage check, crossed feeders
Freq/SCs, interference/pilot pollution
Step 2: Cluster RF Optimization

Drive tests done in mobility, on voice services (KPI L1)
coverage holes, interference analysis, neighbours' tuning
radio link quality of the bearer
Step 3: Town/region EtE Optimization

Drive tests done in mobility for Voice and Static
for Data services (KPI L2)
Homogeneous QoS
End User services tested
radio link quality of bearers
Secure Region/Network Launch date with Optimal End User QoS from Day1

Main 3G KPIs pre-launch example
14
Pre-launch RF Optimisation KPIs

Test area PROTOCOL TEST KPIs Associated KPI Value
Radio Coverage 95% of Ec/Io samples
(KPIs always RF Optimisation report with Drive test
part of Cluster coverage maps including Radio quality
Optimisation measurements Ec/Io & RSCP 95% of RSCP samples
To be agreed during local
Report) RFQ negociation
Optimizatio Quality of Services - Drive-test-based KPIs
n Level 1
Test area PROTOCOL TEST KPIs Associated KPI Value
Retainability CS long call voice Drop call rate
Retainability CS short call voice Drop call rate
Accessibility CS short call call setup success rate
success rate CS HHO
Mobility HHO 3G-2G To be agreed during local
success rate PS HHO RFQ negociation
Call setup success rate
Service PS UL PS 128 UL
Average Throughput
Call setup success rate
Service PS DL PS 384 DL
Optimizatio Average Throughput
n Level 2 Throughput Mobile Cat 12
Mono User-Cell center CQI > 20
Service HSDPA HSDPA DL
Mono User-Cell edge CQI > 15
Service HSUPA HSUPA UL
Throughput Mobile Cat 3
To be agreed during local
Mono user -Cell center RFQ negociation

Optimization Steps
15
Configuration Audit
RF design audit
Spectrum Clearance
System parameters check
Recommended values setting
Site Verification
Network integrity verification
H/W troubleshooting
Coverage improvement
Neighbouring optimization
Parameters optimization
Cluster fine tuning
Optimization spreading to all clusters
Network fine tuning

Configuration Audit
16
Objective
The objective of the configuration audit is to ensure proper system configuration and functioning in the
integrated system.
Checking
Cell Database: coordinates, # of antennas, antenna type, antenna tilt
RF Design: site and cluster Coverage, SC planning, neighbour list, site configuration
Datafill: parameters coherence with Engineering rules and recommendations
Spectrum Clearance (Noise floor measurements)
Method
Cell database information collection and check
Coverage prediction maps
Datafill check with WiPS
Drive tests with spectrum analyzer

Site Verification
17
Objective
The objective of the cell verification is to ensure proper cell site operation in the
integrated system.
The verification is the last check after integration and prior to optimization to detect any
residual issues such as cross feeder.
Some voice & PS calls tests are already done during I&C procedure.
It is performed on site by site basis and any issues shall be corrected.
Checking
Softer and soft handoff OK
Scanner received levels are within expected ranges
The UE Tx power is within an acceptable range
Correct scrambling codes and neighbour lists are data-filled
Detection of major issues on antenna tilts and azimuth
Missing SC : compare Top N SC received on the scanner with Active/ Neighbour set
list from the mobile

Site verification
18
Method
Drive tests at approximately 30 percent of the expected cell coverage area
Tools : Scanner and Trace Mobile with XCAL
Post processing with XCAP and analysis recommending the necessary HW and SW modification
due to errors in installation.
CS Calls : Call originated on one sector, and move towards other sectors
PS Calls : 5 Mbytes (DL) and 1 Mbytes (UL) files are downloaded while driving
Other verifications :
- cross feeders (while driving)
- RSCP (detect any abnormal low value)
- Missing SC : compare Top N SC received on the scanner with Active/ Neighbour set list from
the mobile
Sector
Sector

Carrier
Carrier
Code
Code
Power
Power

Sector

Carrier
Code
Power


19
Objective
Perform RF design verification,
Identify and categorize network or coverage problems
Optimize for best performance according to the acceptance criteria and agreed KPI
Two phases to be followed RF Optimization & Parameter Optimization
RF Optimization
Objective :
Reach the optimal configuration of each cell site (height, tilt, EIRP,
orientation, antenna type, etc.)
Maximize RF QoS (coverage improvement, interference reduction,
neighbouring list optimisation) and capacity of the network.
Method : Use of Call trace data and drive test (scanner and UE).
Parameter Optimization
Objective :
Starting from recommended values, the objective is to tune any specific parameters to solve
issue related with specific scenarios within the cluster. Set system parameters in order to
reach optimal network performance.
Method : Use of KPI dashboard, Call trace and drive test data (scanner and UE).
The cluster optimization process will be detailed in the next section of this document as the E2E optimization
will be performed on 2 clusters before being spread on the whole network.

20
Define drive test routes
Perform DT intra cluster

Check, Analyze, post-process DT raw data
Propose HW and parameters change recommendation
Change Parameter Open ticket with when an issue is detected

Aerial Tuning is necessary
is necessary
Ticket Treatment
Change Parameter
Process Operator Agreement
Aerial Tuning Perform DT until Cluster optimization is completed

and target KPI are met
Perform New DT
Provide KPI progress report on a weekly basis

Perform DT until Cluster optimization is complete and KPI targets are met

21
Main metrics to be used along the process
RF Quality indicators
CPICH Ec/Io (dB) Received energy per chip divided by the power density in the
band i.e. it is identical to the RSCP measured on the CPICH divided by the RSSI.
Active Set Size Number of Radio Links established simultaneously by the UE
Application layer Metrics

Dropped Call Rate Number of Calls abnormally terminated;.
Call Setup Success Percentage of calls established related to the number of
attempted calls
Successful Calls Percentage of calls that could be normally established,
maintained and terminated normally

22
Drive Tests Runs

1st Run : RF control
Scanner + voice (long call) + XCAL
Check radio conditions
Post processing will mainly be on radio conditions
2nd Run : RF control fine tuning + neigbor tuning

Scanner + voice (long call) + CSD (long call) + XCAL
Radio conditions + first KPIs (drop / access failure)
Post processing will mainly be on access failure / call drops
3rd Run : RF control fine tuning + KPI

Mainly pre-KPIs measurements
Scanner + Voice, CSD, PS64/384 + XCAL + Call Trace + Probe (if needed)
Post processing will mainly be on access failure / call drops / KPI achievement

22
23
1st Run Post-Processing

Mainly with XCAP, Planning tool
Check radio coverage (RF Quality indicators)
RSCP (Best SC and per SC)
Ec/Io (Best SC and per SC)
Active set size
SC footprint => overshooting
Pilot Pollution
Comparison with Planning tool
Check Application layers metrics (drop / access failure)
Identify problematic areas
Determine Antenna changes and Neighbor List change to be done

24
1st Run Post-Processing: Pilot Pollution Analysis
A map with colour coded symbols (based on the number of

sectors beating the threshold) is displayed.
2 possible modes :
Nb Sectors above Ec/No threshold
Nb Sectors below Ec/No delta
threshold (related to strongest Ec/No)
Indicates of how many sectors could be

in the active set.

25
1st Run Post-Processing: Coverage Analysis
User selects the Scrambling Code (SC) corresponding to

the sector to analyse.
2 possible modes :
Best Ec/No
All Ec/No instances: Display symbols
where Ec/No measurements are
reported (regardless of the value) for
the selected SC.

26
2nd and 3rd Runs Post-processing

Mainly done with XCAP, Actix
Main issues to check / solve : Application layer metrics : Access failure /

Drop Calls to classify
Radio issue
Poor Coverage : under thresholds RSCP
Configuration
Pilot Pollution (Several servers with equivalent level) => Create a dominant
server
Overshooting : strong signal far away from site => Change antenna
configuration or add neighbour
Missing neighbour : Good RSCP and Ec/No for best cell in the scanner, bad
Ec/No for best cell in the active set. This cell is different to the best one
from the scanner. => Check and add neighbour cell

27
2nd and 3rd Runs Post-processing

Radio issue
Slow Handover
The Ec/Io of a serving SC goes down very quickly, and a defined
neighboring SC gets strong very quickly deriving on a fast increase of
the DL BLER. Not enough time for active set update => change
antenna configuration / change legadd / legdrop parameters.
Network (deeper investigation needed)

SW issue (neigbhour list, )
HW issue (BTS, transmission, TMA, )
Parameter Configuration (3rd run)
Mobile
Other

28
Example
The following slides show how to analyze a typical dropped call with post drive
analysis software
Call Event

29
Example
UE
Dominant PSC = 85
Active Dominant Ec/No = -25 dB
Dominant RSCP = -82.2 dBm
Time of the
drop Scanner
Top 1 SC = 164
Top 1 RSCP = -52 dB
Top 1 Ec/No= -4.9 dBm

30
Example
This slide shows the UE dominant active Ec/No at the time of the drop (value= -25 dB)
UE is moving left to right
UE Plot
Active Dominant Ec/No

31
Example
This slide shows the UE dominant PSC at the time of the drop
(value= 85)
UE Plot
Dominant PSC

32
Example
This slide shows the scanner Top 1 SC (164) at the time of
the drop
Scanner Plot
Top 1 SC

33
Example
This slide shows the scanner Top 1 RSCP (-52 dBm) at the time of the
drop
Scanner Plot
Top 1 RSCP

34
Example
The UE is on PSC 85 and driving toward the cell with PSC 164. As the UE gets
closer to the site with PSC 164, the Ec/No degrades to a point where the call
drops.
The UE is on PSC 85 at Ec/No = -25 and the scanner is showing the best SC is
164 at -52 dBm (-4.9 Ec/No).
When the UE drops, the call is re-established on PSC 164.
This is a typical scenario for a missing neighbour. Reviewing the neighbour list
for the cell with PSC 85 shows that the cell with PSC 164 is not declared as its
neighbour.

35
Objective
The objective of network optimization is to optimize the sum of all clusters covering an entire
region
Checking
Agreed KPI
Method
Verify network performance covering several clusters simultaneously
Perform the final fine-tuning of the network settings paying special attention to the inter-cluster
sites.
Collect metrics and statistics: KPI dashboard
Conduct drive tests on selected clusters or key routes in case of KPI degradation.

4 Post-launch optimisation process

Cluster Optimization Process
37
Monitoring (KPI dashboard)

Accessibility
Drive Test Retainability
Scanner trace Mobility
UE Trace: XCAL 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
Interference reduction Radio Resource Management
MCPA
Neighbouring optimization Mobility
E1
Capacity Iub Efficiency
...
HSDPA

Drive Test Based Optimization
38
Define drive test routes
Perform DT intra cluster

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
Provide KPI progress report on a weekly basis

Perform DT until Cluster optimization is complete and KPI targets are met

Counter Based Optimization 39
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 UEs 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

Counter Based Optimization 40
Check the daily and weekly KPI dashboards
Yes
Target KPI reached No compulsory optimization
No
Check the Worst Cell List
Perform DT in addition to the

check of the KPI dashboard Global Issue or on specific cells
Troubleshooting: additional metrics/counters, CTg, DT (UE/CTb)
No
Root cause found Open a ticket
Yes
Apply corrective actions: HW or parameters change Ticket treatment

5 Optimisation tools

Drive Test Measurement Chain
42
OUTDOOR
GPS
Magnetic
Antenna
PC with
Acquisition SW
INCAR
Dual Frequency Scanner
R99 UE:
HSDPA UE: Option datacard Cat. 12 /
Cat. 6 (Qualcom chipset)

Optimization Tools Set 43
IP
OAM
Call RNC
Trace Iu
Iub
NodeB
RFO+DT
post processing
SW Workorders
ALU
ALU ?
WiPS Protocol
Analyzer
ALU
Data
Collection SW Counters
A9155 NPO
Scanner
UE
ALU
ALU ALU

Call Trace
44
Call Traces are activated on the OAM GUI. The log files are stored on the Performance Server.
Trace all calls of one or several UEs

CTa Activated from Core Network
Most used Call Traces
Trace all calls of one specified UE

CTb Activated from Access Network
Trace a % of calls over the NW on a specific cell or group of cells.

CTg Activated from Access Network
Trace a % of calls (only neighbouring optimisation related messages) over the NW on a

specific cell or group of cells
CTn Activated from Access Network
Post-Processing with WQA Tool
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 PS interface
One Neighbour RNC or a group of neighbour RNC
One RNC
Activated from Access Network

45
www.alcatel-lucent.com

46
Backup tool

Call Trace B: CTb
47
A Call Trace B session provides data related to all calls initiated by a specified UE during the
session activation.
There is one and only one UE traced in a CTb session.
Therefore if n mobiles are to be traced simultaneously, then n sessions are created.
The UE identity, specified at the OMC-R when creating a CTb session, may be one of all
choices of the Initial UE identity IE supported by the RRC protocol specified in 3GPP
specification 25.331: TMSI,P-TMSI, IMSI, IMEI.

Geographical Call Trace: CTg
48
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.

RFO (RF Optimizer)
49
Post-processing Tool to analyse data log files from UE acquisition tools and Call
Trace.
It supports Nemo traces and is able to synchronize them with CTb traces.

NPO (Network Performance Optimizer)
50
ALUs 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.
Intersystem Cell Reselection

1200000 100.00%
98.00%
1000000
96.00%
94.00%
800000
92.00%
600000 90.00%
88.00%
400000
86.00%
84.00%
200000
82.00%
0 80.00%
15-mar-06 22-mar-06 29-mar-06
Attempts Success Success Rate


ALU RF Optim Process

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

ALU RF Optim Process

Transféré par

Droits d'auteur :

Formats disponibles

Training session 3

Alcatel-Lucent W-CDMA Description

Global Optimization Process

All Rights Reserved Alcatel-Lucent 2009

Alcatel-Lucent W-CDMA Description

2a - Cell 9a - RF Design 11a - Site 18a - Perf

Optimization aims at improving the network performance and/or

Methods differ for :

All Rights Reserved Alcatel-Lucent 2009

Pre-launch optimization Post-launch optimization

All Rights Reserved Alcatel-Lucent 2009

Alcatel-Lucent W-CDMA Description

Coverage quality sensitive to traffic load.

Pilot Ec/Io is the Key metric, not signal Level

All Rights Reserved Alcatel-Lucent 2009

2nd step simulation tuning:

radio criteria example:

All Rights Reserved Alcatel-Lucent 2009

Alcatel-Lucent W-CDMA Description

Providing the best RF & system

All Rights Reserved Alcatel-Lucent 2009

Step 1: RNP Assessment & Site verification

Step 2: Cluster RF Optimization

Step 3: Town/region EtE Optimization

All Rights Reserved Alcatel-Lucent 2009

Pre-launch RF Optimisation KPIs

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

Define drive test routes

Perform DT intra cluster

Change Parameter Open ticket with when an issue is detected

Aerial Tuning Perform DT until Cluster optimization is completed

Provide KPI progress report on a weekly basis

All Rights Reserved Alcatel-Lucent 2009

Main metrics to be used along the process

Application layer Metrics

All Rights Reserved Alcatel-Lucent 2009

Drive Tests Runs

2nd Run : RF control fine tuning + neigbor tuning

3rd Run : RF control fine tuning + KPI

All Rights Reserved Alcatel-Lucent 2009

1st Run Post-Processing

Check Application layers metrics (drop / access failure)

Identify problematic areas

Determine Antenna changes and Neighbor List change to be done

All Rights Reserved Alcatel-Lucent 2009

1st Run Post-Processing: Pilot Pollution Analysis

A map with colour coded symbols (based on the number of

Indicates of how many sectors could be

All Rights Reserved Alcatel-Lucent 2009

1st Run Post-Processing: Coverage Analysis

User selects the Scrambling Code (SC) corresponding to

All Rights Reserved Alcatel-Lucent 2009

2nd and 3rd Runs Post-processing

Main issues to check / solve : Application layer metrics : Access failure /

All Rights Reserved Alcatel-Lucent 2009

2nd and 3rd Runs Post-processing

Network (deeper investigation needed)

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009