UTRAN Optimisation Process

NORTEL NETWORKS CONFIDENTIAL

June June 0022Arnaud PIAZZAArnaud PIAZZA

UMTS UMTS UTRAN Optimisation ProcessUTRAN Optimisation Process

Internal Use OnlyInternal Use Only

Presentation name - 2NORTEL NETWORKS CONFIDENTIAL

AgendaAgenda

• Introduction Introduction

• Pre-launch Optimisation process Pre-launch Optimisation process

• Monitoring&Optimisation processMonitoring&Optimisation process

• CostsCosts

• ImpactsImpacts

• ToolsTools


• Optimisation aims at improving the network performance and/or capacity.To improve the system initial performance

To reach acceptance criteria (=>payment)

To enhance the subscriber satisfaction

To increase the number of subscribers

To decrease CAPEX

• Methods may differ for : – Pre-launch optimisation (performed for acceptance, trials)– Post-launch monitoring and optimisation (performed for in-service

networks) Non loaded networks optimisation (for first product releases) Loaded networks (normally from product release 4)

IntroductionWhy optimising a network?Why optimising a network?

Pre-launch phasesPre-launch phases

Post-launch phasesPost-launch phases


IntroductionOptimisation phasesOptimisation phasesTr

ial

Tria

l

VOVO AcceptanceAcceptance Network Monitoring & OptimisationNetwork Monitoring & Optimisation

NetworkLaunch

Pre-launch Optimisation Post-launch Optimisation

No network load (traffic limited)

Cluster optimisation based mainly on drive tests data

High optimisation gains

Significant network load (increasing)

Optimisation based mainly on statistical data (counters, Call Trace)

Optimisation gain is less (but baseline performance are higher).


IntroductionOptimisation in GSM and in UMTSOptimisation in GSM and in UMTS

GSM Optimisation

Recommended parameter settings Repetitive drive-test campaigns (up

to 5) for Pre-launch optimisation

NetworkLaunch

UMTS Optimisation

Recommended parameter settings Single drive-test campaign for Pre-

launch optimisation

HighTraffic

System Parameters optimisation mainly

RF&System Parameters optimisation ND optimisation New features implementation Densification

RF Parameters Optimisation ND optimisation New features implementation Densification

“Services-Based” optimisation RF parameters optimisation mainly ATM parameters optimisation


Pre-launch optimisation processSteps teps descriptiondescription

Configuration AuditConfiguration Audit• System parameters check (Eng’g rules, consistencies,…)• Recommended values setting

Shakedown Shakedown • Network integrity verification• H/W trouble shooting

Cluster OptimisCluster Optimisationation• Parameters optimisation • neighbouring relationships optimisation

NetworkNetwork Optimis Optimisationation• Optimisation spreading to all clusters• Network fine tuning


Pre-launch optimisation process Configuration Configuration AuditAudit• Objective

– The objective of the configuration audit is to ensure proper system configuration and functioning in the integrated system.

• CheckingSystem parameters

• Database information consistency• Parameters coherence with Eng’g rules and recommandations

RF parameters• Spectrum Clearance (Noise floor measurements)• RF Design Information• Cell Database and Datafill (coordinates, # of antennas, antenna type, antenna tilt, …)

Transmission parameters• Datafill consistency between two linked networks elements

• Method – Database information collection and checks


• Objective – The objective of the cell shakedown is to ensure proper cell site operation in the

integrated system. Proper operation is verified through drive tests around the site and evaluation of antenna orientation, cable interconnecting and correct code assignments.

• Checking network access,call setupRRM algorithm settingshandoffs between cellsantenna orientationCarrier&code allocationpower levelsReception path

• Method – Drive tests at approximately 30 percent of the expected cell coverage area– Unloaded conditions

Pre-launch optimisation process Cell Cell ShakedownShakedown


• Objective – The objective of cluster optimisation is to perform RF design verification,

identify and categorize network or coverage problems, optimize for best performances according to the acceptance criteria and serve as a first pass of problem resolution.

• Analysis and Problem ResolutionNeighbor list optimizationCoverage problems (can include holes, failures due to multiple or rapidly

rising pilots)Network timer checking and tuning. Handoff parameters checking and tuning

• Method and requirements – Drive tests over the cluster– RF&Configuration audit and shakedown must be completed

Pre-launch optimisation process Cluster Cluster optimisationoptimisation


• Objective – The objective of system optimization (or control route analysis) is to

optimize the sum of all clusters covering an entire region.

• Method– The system performance optimization starts with two optimized clusters

and ends with all the clusters in the region.– Due to the cross-effects between clusters, handoff parameters, neighbor

list contents and neighbor prioritization might need changes at borders between clusters.

• Final deliverables - Performance Result Report - Performance Measurement Report - Test Environment Report - Issue list

Pre-launch optimisation process Network Network optimisationoptimisation


Pre-launch optimisation processOptimisation Optimisation timingtiming

Configuration AuditCell ShakedownCluster OptimisationPerformance data collectionReporting

Week N+1 Week N+2 Week N+3

Depends on the number of sites

Week N-1Week N-2 Week N


Monitoring &Optimisation processSteps teps descriptiondescription

Different process according to the level of services : Level 3 : Advanced services

• Network optimisation• Growth planning• End-user services planning

Level 2 : Performance engineering services • Network monitoring • Network fine tuning

Level 1 : Operational support services• Emergency technical assistance service• Network expansion• First line operations


OptimisationOptimisation• Network performance improvment• NEs detailed performance&capacity analysis

Monitoring&Optimisation processSteps teps descriptiondescription

MonitoringMonitoring• Network audit • Performance fine tuning• Issues trouble shooting

Parameters auditMobility AnalysisCapacity Analysis

Voice quality Analysis

RF Analysis

Data quality Analysis

Quality Analysis

End user services planning Parameters optimisation

Code planningLoad balancing

RF Optimisation Growth planning


Monitoring &Optimisation processMonitoring Monitoring (1/4)(1/4)

• Quality / Capacity Analysis – Objective :

measure and report on the Quality of Service / Capacity of the network or of some network elements => provide a complete set of metrics representing the perception of the users of the network.

trouble shoot/fine tune network performance.– Method : Use of Counter/Call trace data => computation of performance metrics.– Benefit :

settle performance issues and improve network quality/capacity, reporting of the network behavior => those data are key inputs for optimisation

actions.

• RF Analysis– Objective :

Evaluate the RF quality of the network or for some particular locations/NEs. trouble shoot RF related issues.

– Method : Use of Counter/Call trace data or drive tests data.– Benefit : settle local RF issues (pilot pollution, missing neighbours,…).



• Mobility Analysis – Objective : measure and report on the mobility profile of subscribers. – Method : Use of Counter/Call trace data.– Benefit :

Identification partitioning issues, fine tuning of network partitioning (RNC, LAC, ...boundaries).

reporting of the subscribers behavior => subscriber profile is a key input for network capacity dimensioning and traffic growth forecast.

• Parameters Audit– Objective :

Check the parameters setting consistency, Check setting coherence with Eng’g rules/recommendations.

– Method : Use of MIB extracts.– Benefit :

Identification and trouble shooting of network issues, System parameters setting « cleaning ».



• Data Quality Analysis – Objective :

measure and report on the data services quality (troughput mainly) => provide a complete set of metrics representing the perception of the users of the network.

trouble shoot or fine tune.– Method : Use of Counter/Call trace data => computation of performance metrics.– Benefit : Solve data quality (throughput,…) issues,

• Voice Quality Analysis– Objective :

measure and report on the voice quality on the network => provide a complete set of metrics representing the perception of the users of the network.

trouble shoot or fine tune.– Method : Use of VQ drive tests data.– Benefit : Identification and trouble shooting of voice quality issues.



• Transmission Analysis – Objective :

measure and report on the transmission quality (congestion, buffers size,...) => apply to the ATM transmission network, E1,...

trouble shoot or fine tune.– Method : Use of Counter/Call trace data => computation of performance metrics.– Benefit : Solve quality and reliability issues,


Monitoring &Optimisation processOptimisation (1/4)Optimisation (1/4)

• RF Optimisation – Objective :

Reach the optimal configuration of each cell site in the wireless network (height, tilt, EIRP, orientation, antenna type, etc.)

Maximizes RF QoS (coverage improvement, interference reduction, neighbouring list optimisation) and capacity of the network.

– Method : Use of Call trace data and drive test. – Benefit : Better RF quality and capacity.

• Parameters Optimisation– Objective :

Set system parameters in order to reach optimal network performance. Adapt TCP and RLC parameters to optimise data connection performances.

– Method : Use of Call trace, protocol analyzer and drive test data. – Benefit : Better system performance.


Monitoring &Optimisation processOptimisation (2/4)Optimisation (2/4)• End User Services Planning

– Objective : Evaluate the impact of new service introduction on the quality and capacity of the network.

– Method : Use of Counter/Call trace data to compute previsions.– Benefit :

Necessary to plan system optimisation and/or network design actions. Give the customer a clear view of new service impact and help planning

precisely for future growth.

• Growth Planning– Objective :

Forecast network growth, Determine network capacity limits and bottlenecks.

– Method : Use of Counter/Call trace data to compute traffic, load forecasts.– Benefit : minimize the future infrastructure needs of the operator through

precision engineering and use of just-in-time concepts.



• Load Balancing – Objective : Balance the load between different network elements (may be MSCs,

RNCs, ...) or between NE’s ressources (RNC cards,...).– Method : Use of call trace, counters and drive tests data to optimise the network

partitionning (LACs, number of cells per RNC,...) – Benefit : Improve load distribution over the different NEs or over the different

NE’s ressources.

• Code Planning– Objective : find an optimal scrambling code plan taking into consideration (actual

cell sites positions, inteferences, jammers, etc ...) and the real time data (radio measurements, counters, etc ...).

– Method : Use of call trace, counters and drive tests data.– Benefit :

Improve call quality, Improve capacity.



• Transmission Optimisation – Objective :

Reach the optimal configuration and settings to maximize the transmission network reliability, performance and capacity.

– Method : Use of counters, Call trace and protocol analyser data. – Benefit : Better UTRAN performance in terms of both quality and capacity.


Costs Pre-Launch teamPre-Launch team

• The Regional RF Manager control the Pre-launch Optimisation operations for the region.

• The Drive-Test team is composed by one Operator (technician) and one Driver (local people) and is managed by the RF Optimisation Engineer.

The Operator runs data collection, controls drive test equipment and is in charge of downloading and post-processing the resulting data.

The RF Optimisation engineer analyses data from each drive tests and make change recommendations. He usually manages 2 drive-test teams: briefing/debriefing, advice for issue solving, eventual real-time analysis with the drive test team on-site.

• Additional ressources should be available for : call trace operator at the switch (one OMC technician).

datafill changes and configuration audit (one OMC technician).

RF Manager

RegionalRF Manager

RegionalRF Manager

RegionalRF Manager

RF Optim Engineer

Drive test team:- technician- driver


RF Optim Engineer




Let’s assume a network made up of 1000 sites, to be optimised in 3 months

This campaign requires about 11 drive test teams with the related RF engineers and RF managers teams.

Considering drive test tasks are outsourced to managed services, the costs related to ressources would be approximately US$ 1.2M

Tool sets for all teams would cost approximately US$ 300K

Total costs would be Total costs would be ~ US$ 1.5M~ US$ 1.5M

Costs Pre-Launch operationsPre-Launch operations

RF Manager

RegionalRF Manager

RegionalRF Manager

RegionalRF Manager

RF Optim Engineer



RF Optim Engineer




Efficient optimisation process leads to good system performance and therefore customer satisfaction

good opportunity for potential extension, good opportunity for other networks implementation.

For Turn-key networks, optimisation helps reaching the predicted design => no need to « offer » additional equipments to reach targets.

Lack of optimisation and/or unefficient optimisation leads to poor system performance and

risk of delayed or failed network acceptance. Penalties example : XferaXfera: if network performance acceptance fail, US$ 200M. mmO2mmO2: 10% withholding on equipment costs until network performances are met. OniwayOniway: no payment before fully accepted network.

ImpactsImpact of optimisation Impact of optimisation


ImpactsImpact of optimisation feature shortageImpact of optimisation feature shortage

2002(early

deploy)

2003+(capacity/expansion)

Counters/Call Trace - lack of traffic volume counters (inhibits capacity assessment, expansion planning, call model feedback) Med High - lack of well defined call drop counter Low High - lack of fine granularity per-call power trace (inhibits RF capacity assessment, call drop troubleshooting) High Med - lack of CTg (Call Trace "geographic") Med HighConfiguration - Datafill Audit: lack of single "1 row per cell, 1 column per parameter" view across all per-cell parameters. High Low - many parameters require equipment restart to change values (inhibits quick changes for new settings) High HighPerformance - handoff link addition time too long (high FER, call drops) High High - lack of event-based measurement reporting (periodic measurements further delay the handoff process) Med High - lack of implementation of some of the performance enhancing "tricks" found on IS95 (power boosts, quick repeat of certain key messages)

Med High

Other Misc Deployment related - lack of OCNS in V2 (inhibits network acceptance procedures) High High

These will likely cause extended deployment time (struggle to meet performance objectives). Some of these have V3 FRSs associated so comment is mainly aimed at V2.


Acquisition toolsCall TraceTrace Mobile (QCT)GraysonRF AnalyzerRadcomIP sniffer

Post-processingRFO3GIDADIVA

Pre-launch OptimisationPre-launch Optimisation Network Monitoring&OptimisationNetwork Monitoring&Optimisation

NetworkNetworkLaunchLaunch

AcceptanceAcceptanceLaunchLaunch

Network Monitoring toolsNetwork Monitoring toolsAcquisition toolsOMC (Counters)Call Trace

Post-processingPrOptima

Acquisition toolsCall TraceTrace mobiles Grayson RF AnalyzerRadcomIP sniffer

Post-processingRFO3GIDADIVA

Trial & acceptance toolsTrial & acceptance tools

Trouble-Shooting toolsTrouble-Shooting tools

Tools PhasingPhasing


Tools RoadmapRoadmap

Tool . . . Week 19

Week 20

Week 21

Week 22

Week 23

Week 24

Week 25

Week 26

Week 27

Week 28

Week 29

Week 30

Week 31

Week 32

Week 33

Week 34

Week 35

Week 36

Week 37

Week 38

Week 39

Week 40

Week 41

Week 42

Week 43

UTRAN releasesCN releasesTTM FCS CR

Mobiles QCT QCT QCT QCT QCT QCT

Grayson

Call Trace CTb CTb

RFO

ProOptima

CTa, CTb

v 2v 2.0c v 2.0d

Motorola Motorola

Beta Version

Beta Version

v 2.0a v 2.0b


(R&D tools are not displayed on this chart)

GSMGSM

UMTSUMTS

RNCRNC

RNCRNC

BSCBSC

ACCESSACCESS CORECORE

GSMGSM

UMTSUMTS

PCUSNPCUSN

Iub ATM

Abis A

GbAgprs

Iur IuIP

IP

N*64K PSTNPSTN

InternetInternet

IntranetIntranet

CSCS

PSPS

Radcom IP sniffers

RFO

Trace MSGrayson

PrOptima

Call TraceA&SA&S

ServersServers

3Gida

Accesscounters

Corecounters

Utran functionality Acquisition tool Post-processing tool

RF Analyzer

DIVA

Tools ArchitectureArchitecture


UMTS Optimization tools UMTS Optimization tools – Description (1/4)Internal tool External tool Product Comments

Call Trace X Available in V2 => improvments in V3

Counters X Some available in V2 => new counters in V3

Trace mobile X Qualcom and possibly Motorola,…Qualcom acquisition S/W is QXDM until replaced by CAIT

Drive test platform X Grayson

RF Analyzer X Grayson or Agilent

Protocol analyzer X Radcom

IP sniffer X Network Monitor, Ethereal, TCPtrace

E2E Data Packet X R&D tool

RFO X (X) Internal but might be external

PrOptima X External only (no license for internal use)

3GIDA X R&D tool

DIVA X R&D tool

Acquisition tools

Post-processing tools

UTRAN functionalities

R&D tool (no support for external use)


• UTRAN functionalities to collect network data are : Counters : The system counts events and record them in registers called

counters. They enable the operator to observe and track the NE performance and the offered Quality of Service. Counters are grouped in functional areas: HO, Radio link Management, Mobility Management, Session Management, Traffic …

Call trace : Call Trace is a RNC feature that allows collecting detailed information : protocol messages (on one or more mobiles, cells, or interface), measurements, events,…This feature is available in V2 but will be strongly enhanced in V3.

• Acquisition tools are used to collect data : Trace Mobile (QualcomQualcom) : It allows collecting protocol messages on the

mobile side but also measurements on the DL path (air interface). Qualcom is currently used for field testing but other brands like Samsung or Motorola are also used in labs. Trace mobiles use a S/W for data acquisition. For first releases, Qualcom proposes QXDM. It should be replaced by QCAIT.

UMTS Optimization tools UMTS Optimization tools – Description (2/4)


Drive test platform (GraysonGrayson) : It mainly allows collecting data from more than one trace mobile simultaneously. Optionally, a scanner can be plugged and its outputs merged with the trace mobiles ones. Grayson solution is likely to be chosen by Eng’g.

RF Analyzer : It is a code domain analyzer that decodes scrambling and spreading codes and in general all UMTS channels. It is mainly used to estimate the RF quality of the network, but also for debugging purposes when a problem occurs on radio interface. Agilent E7476A is currently used but should be replaced by Grayson scanner.

Protocol analyzer (RadcomRadcom): It can be plugged on Iub, Iur,and Iu interfaces. The Radcom that is currently used can monitor 2 interfaces in parallel.

IP Sniffer : It is a protocol analyzer plugged on the IP network to spy IP traffic.

E2E Voice Quality / Data Packet : This S/W creates traffic (voice or data) on one End and collect it on the other End. It then provides statistics and metrics on this E2E session.



• Post-processing software used are : 3Gida : This S/W is used to post-process traces provided by the

Radcom protocol analyzer. It allows decoding all protocol messages exchanged on Iu, Iub and Iur interfaces, but also computing metrics and statistics associated to UMTS data transfers.

DIVA : This S/W processes data coming from the Agilent RF analyzer, TENOR and E2E VQ/DP. It provides the user with RF statistics, voice and data metrics,…

RFO : This internal tool processes data from Call Trace and trace mobiles. It the provides the user with call statistics and numbers of RF analysis.

PrOptima : PrOptima uses counters and Call Trace data as inputs and process them, providing the user with monitoring statistics


UTRAN Optimisation Process

Documents

Transcript of UTRAN Optimisation Process