UMTS Initial Tuning

UMTS Initial Tuning

9-16-2012 | Page 2

Are there any differences between 2G and 3G?

2G Initial Tuning
New Operators Mature System and UE Coverage focused Stable processes Stable tools Medium requirements on Project Management Over shooting sites are causing interference Neighbor relations are basic

3G RAN-Tuning
Mature Operators, but not in 3G... NEW and sophisticated Systems features and Ue Coverage & Capacity focus already in the initial network Modified/Enhanced processes New tools High requirements on Project Management Overshooting and Neighbor sites are causing interference Optimized Neighbor relations are key

Co-sited with GSM and Dual band antennas

Inter-working with GSM

9-16-2012 | Page 3

Typical Tuning Process Flow

Data Collection

Analysis

Reporting Preparation Post Processing Change Proposals

Change Verification

Preparation

Measurement

Root Analysis

Implementation & Verification

9-16-2012 | Page 4

Initial tuning overview

Main RF System performance indicators:
BLER (connection quality) Access Failures Dropped Calls Pilot Channel Ec/Io Mobile Transmitted and Received Power Forward/Reverse Link BLER Call Processing Information Service Measurements

9-16-2012 | Page 5

Initial tuning overview

Network tunning parameters
Neighbour list Antenna height, tilt and orientation Network parameters: - Output power - Cell Selection & Reselection - Handover - Power Control - Other

9-16-2012 | Page 6

Test Equipment
Pilot Scanner
Scan pilots measuring Ec/Io and RSCP Independent of system parameters (soft-HO, etc)

UEs: Mobile phones and PC Cards GPS Mobile Monitor software installed in Laptop
Mobile, GPS and Scanner connected to laptop Collects all data measured and processed by Mobile: - RSCP and Ec/Io of cells in Active Set+Neighbour Set - Mobile Tx and Rx power - L2 and L3 messaging - Call processing - BLER - Service Measurements

9-16-2012 | Page 7

Drive test tools configuration

Drive Test Equipments for Voice, CS64 & PS call
Short call Long Call CS64 PS

USB1

USB2
USB1 USB2

GPS

Com 1

scanner

9-16-2012 | Page 8

Data Analysis
Post processing data analysis software
Generate plots, table, show L3 messaging TEMS (Ericsson), X-Cal (Couei), etc

GIS Software
To display graphical results from coverage surveys overlaid on street maps MAPINFO, ARCVIEW, etc

RF Planning tool
Planning and evaluation of modifications TEMS CPU, Asset, Atoll, etc

9-16-2012 | Page 9

Initial tuning procedure

1. Spectrum clearance Check external interference 2. Sector Tests Basic call processing functionality checking 3. Unloaded Cluster optimization Group of 15-20 NodeBs (3 rings) Clusters should overlapp Detection of main problems and basic adjustment 4. Complete system-wide optimization Optimization under loaded conditions (OCNS) Adjustement of Inter-cluster areas Fine tuning to reach KPI objectives

9-16-2012 | Page 10

Initial tuning Steps

First step: check UMTS Spectrum
Possible sources of external interference: Microwave data transmissions Wideband noise from machinery Monitor Uplink and Downlink interference in the UMTS band

9-16-2012 | Page 11

Initial tuning Steps

Second Step: Site testing
Test of basic call processing functions: origination, termination of Call, Videocall, PDP context, Data transmissions Test of softer handover Check correct power settings Check correct PSCs of cells Check antenna orientation and footprint

9-16-2012 | Page 12

Initial tuning Steps

Unloaded Cluster optimization

Collect basic site parameters: coordinates, antenna height, orientations and tilts, PSC. Check design with RF planning tool Visit sites Verify SC plan (1 cell cant have 2 neighbours with same PSC) Check Cell parameters (LAC, power settings, HO, etc..) Neighbour list definition Define extensive drive test Check O&M alarms before drive test

9-16-2012 | Page 13

Initial tuning Steps

Unloaded Cluster optimization
First Pass Optimization Neighbour list correction Detect low coverage areas Detect areas with Pilot Polution Plot and check coverage of each cell Aerial modifications: antenna height, azimuth, tilt. Useful plots: - UE Rx and Tx power - Dominant PSC, RSCP and Ec/Io - BLER - Scanner Top1 PSC, RSCP, Ec/Io - Call Events (Drop, Fail, etc)

9-16-2012 | Page 14

Initial tuning Steps

Unloaded Cluster optimization
Second Pass Optimization Same as 1st pass: - Neighbour list correction - Detect low coverage areas - Detect areas with Pilot Polution - Check coverage of each sector - Aerial modifications: antenna height, azimuth, tilt. Adjustment of power settings (CPICH power) Adjustment of HO parameters: - Soft-HO: addition, deletion, max active set size - Hard HO GSM UMTS parameters Exhaustive Call Events analysis

9-16-2012 | Page 15

Initial tuning Steps

Complete system-wide optimization
Neighbour list correction in inter-cluster areas Load simulation in downlink and uplink Under loaded conditions additional tuning is required acceptable areas without load may suffer from interference under load Fine tuning (aerial modifications, parameters) Exhaustive Call Event Analysis for KPI calculation

9-16-2012 | Page 16

What can be achieved with a scanner?

The basic measurements of scanner is CPICH_RSCP (received signal code power) CPICH_Ec/No (received energy per chip divided by the power density in the band) RSSI (received signal strength indicator) What can you detect with scanner? Crossed feeder issues (DL) Coverage verification Interference problems (cell overlap, pilot pollution) Missing neighbours Detect overshooters
9-16-2012 | Page 17

COVERAGE VERIFICATION - Primary Common Pilot Channel (Example)

Verify P-CPICH detection to minimize coverage holes P-CPICH RSCP P-CPICH Ec/No
Verify coverage predictions

Use threshold events and/or coverage maps to detect coverage holes. Use Best Server Indication to identify interferer
9-16-2012 | Page 18

Best Server Signal Strength (RSCP)

Green is good Yellow can generate problems Brown is bad

Problems occur in areas with bad coverage

RSCP in dBm

C
B D

9-16-2012 | Page 19

Pilot Ec/No measurements (Example)

Green is good Yellow can generate problems Brown is bad
A

Problem areas
B Ec/No in dB
-9 to 0
-12 to 10 -30 to -13
9-16-2012 | Page 20

Finding interference (Example)

T Th ha am me es s

6741

By correlating low Ec/No with high RSCP, areas with high interference can be detected

B4009

25003
Reading Reading Reading Station Station Station Station Reading Reading Reading Station

Museum Museum Museum of of Reading Reading Museum Museum Museum of of of of Reading Reading Reading Reading

1408
A329 Reading Reading Reading West West Station Station Reading Reading Reading West West West West Station Station Station Station Reading Reading Reading Reading Reading Reading

23405 23400 23401 1685

-30

-40

A4155
-50

RSCP [dBm]

-60

A4

B3031

High interference
-70

-80

-90

T T The he he he University University Universityof of of Reading Reading Reading University of Reading T T T he he University of Reading

RSCP [dBm]
-100 -25 -20 -15 -10 Ec/Io [dB] -5 0 5

6734

-50 to -60 to -70 to -80 to -90 to

-41,6 -50 -60 -70 -80

(100) (357) (598) (376) (70)

A327

K Ke en nn ne ett

9-16-2012 | Page 21

Initial Tuning experiences RN aspects

1st priority
Securing coverage Identifying interference Tuning neighbor relations

O&M aspects (CM)

Parameter consistency Consistent network configuration

2nd priority
LA/RA planning Power settings Correct code plan Detecting crossed feeders

3rd priority
Feature tuning Measurement principles
9-16-2012 | Page 22

Securing Coverage
Checking UL and DL service coverage
Verify RSCP Verify Ec/No

1st priority

Drive test to verify pilot RSCP and Ec/No

RAB

Required Ec/No unloaded -16 -14 -12 -9

Required Ec/No With load -12 -10 -8 -5

Required Ec unloaded -114 -110 -110 -110

Required Ec With load -111 -107 -107 -107

128 kbps: 95%

20% 18% 16% 14% 12% 10% 8% 6% 4% 2% 0% -16 -14 -12 -10

384 kbps: 80%

100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% -8 -6 -4 Pilot Ec/No

P64/64 P64/128 P64/384

Values depend on CPICH setting and antenna configuration

Actual DL service coverage based on Ec/No measurments

9-16-2012 | Page 23

Cumulative distribution

%bins at given Ec/No

AMR 12.2

1st priority

Identifying interference
In case of low RSCP:
Up tilt/re-direct antenna Build new site A pilot power increase will only help marginally

Minimum quality
Interference limited

30

Both design criteria 40 fulfilled

50 60 70 80 90

In case of low Ec/No (and high RSCP)

down-tilt/redirect antenna if necessary turn off interfering sector Reducing pilot power is not a preferred solution
Coverage and interference limited 25 20 15 10 Coverage limited 5 0

100

Ec/N0 [dB]

RSCP req outdoor Potentially, high interference can be due to co-code problems Make sure to utilize all 512 codes
9-16-2012 | Page 24

RSCP [dBm]

Tuning neighbour definitions

Good neighbour definitions are essential A missing neighbour relation can make call drop

1st priority

Consequences of missing/too many neighbour definitions

Common reasons for poor nonworking neighbours
Neighbour has not been defined=> missing neighbour The neighbour list has been truncated

Pilot Ec/No

UE released

best server
releaseConnOffset [12 dB]

cell not in active set

9-16-2012 | Page 25

Tuning neighbour definitions

Effect of truncation
Monitored set
Cell A Cell B Cell C Cell A1 Cell B1 Cell C1

1st priority
Active set (AS)

Monitored set is the union of the Ncell list of the cells in AS. Note: Duplicated Ncell entities are removed

Cell A10 Cell B10 Cell X Cell Y Cell Z

max 32 cells Unmonitored set not measured by all UE Neighbours are truncated

Avoiding truncation is important to keep drop rate low

A healthy network has not more than 15-20 relations per cell
9-16-2012 | Page 26

Crossed feeder detection

Common scenarios
Reference case

2nd priority
Swapped TX&RX

DL UL

TX/RX1 RX2

DL UL
No coverage, loss of UL diversity Low signal level, poor Ec/No Dropped calls Handover fails Call set up problems High UL power

Swapped TX (or Swapped RX)

DL
UL
Loss of UL diversity High UL power

By monitoring Code, signal level, quality and UE performance (handover, setup success, power) crossed feeder can be detected.

9-16-2012 | Page 27

Feature tuning
Things to start with
IRAT
Purpose To secure a well working mobility/prioritization between WCDMA and GSM network
Parameters UsedFreqThres2dEcno UsedFreqThres2dRscp gsmThresh3a hoType idle mode and GSM parameters

3rd priority
HSDPA
Purpose To ensure high user bitrate and high HS utilisation Parameters
hsHysteresis1d hsTimetoTrigger1d

hsdschInactivityTimer other HS parameters

Packet data
Purpose To secure a good trade off between available resources and PS performance
Parameters downswitchtimer (channel switching) SF8 (number of 384 users per cell) BLER target

9-16-2012 | Page 28

Trouble shooting: Call Events Analysis

1. Classify the reason of dropped and failed calls between a) Radio related cases b) Network related cases c) other related cases 2. Drops and Fails due to Radio related cases to be fixed: Missing Neighbours Pilot polution Low coverage (if this can be improved) 3. Network issues are transmitted to the UTRAN equipment supplier for system investigation 4. Other issues types are being classified and investigated (TMA problems, Test equipment malfunction, etc)
9-16-2012 | Page 29

RF Performance Tools : L3 call processing messaging

9-16-2012 | Page 30

[ 2004 Apr 14

03:09:55.445 ] DL DCCH

log_chan_type : 3 rb_id : 3 length : 6 value DL-DCCH-Message ::= message downlinkDirectTransfer : r3 : downlinkDirectTransfer-r3 rrc-TransactionIdentifier 1, cn-DomainIdentity cs-domain, nas-Message '052265'H mobility management messages ===> mobility management messages ===> Connection management messages: CM SERVICE REJECT Reject cause value : Message not compatible with the protocol state

Drop Call Reasons Example

Drop calls reasons

Missing neighbour Good RSCP, high Ec/IoPilot polution Good RF but high BLER, release cause unspecified Test equipment malfunction Out of cluster

Type of drop
Radio Issue Radio Issue Network issue Other issue Other issue

9-16-2012 | Page 31

Call Events Analysis : Drops and Fails

Correct classification is not always obvious: for a correct Analysis a variety of RF parameters need to be taken into account: CPICH RSCP and Ec/Io of detected cells measured by UE and Scanner BLER DL (Drive Test Equipment) BLER UL (Traces) UE Tx power L3 messaging UL Interference (Uplink measurements) Etc

9-16-2012 | Page 32

Summary RAN Tuning

Ensure that there is coverage
All sites are in place correctly installed with correct power settings

Make sure to minimize missing neighbours

Use techniques such as NCS, counters, drive tests

Keep a consistent radio network

To ensure that same performance in all parts of the network

Selected feature tuning when there is significant amount of traffic

Current recommended settings has proven to give good performance equal to GSM

Eliminate over shooters Well defined cell coverage Smooth transition to GSM RND have impact on RAN tuning Efficient RAN tuning => Shorter TTM

9-16-2012 | Page 33

For more details

formation@yacom.net

9-16-2012 | Page 34