3G RF Opt Process

(1)

Soc Classification level

1 © Nokia Siemens Networks Presentation / Author / Date

3G RF optimisation

(2)

RF Optimisation - Introduction

Make RF Scanning & Verification to

look at:

Dominance

DL coverage

Quality

Pilot Pollution

UL Coverage

Make Neighbour list

Verification

RAN

KPI / Performance

Analysis

Make RF Optimisation to:

•Improve coverage areas and

sharpen dominance areas

•Optimise SHO area

(3)

RF Feild Optimisation

• For RF Optimisation and neighbour verification both Scanner and UE

measurements are required simultaneously

• Post-Processing tool is required for data analysis

• Individual call failures or drops can be analysed with Drive test tools (e.g.

Nemo Outdoor) but to get bigger picture, a proper analysis tool is required

• Actix or Nemo Analyser can be used for

–

Data analysis

–

Create Maps

(4)

RF scanner

The purpose of using the RF scanner is to be able to scan and measure all used carriers/cells and their corresponding DL scrambling

codes. This gives the full picture of the (on air) radio network within a selected frequency band. The results are used to identify and

understand reasons for peculiar behaviour discovered during field measurements. In addition, the scanner will indicate presence of

“illegal” RF interference within the sub bands allocated to the network. The scanner data analyses can be done for many purposes:-

For low coverage areas

For antenna installation problems

For missing neighbours

For coverage optimisation

With the scanner you can get the following info from the surrounding cells:

Different Scrambling codes

CPCIH RSCP value (dBm)

CPICH EcNo value (dB)

UE measurements

are different than to RF scanner measurements. The Scanner measures all SCs, whereas the UE only

measures SC signals from the cells that the system has informed/ordered the UE through the BCH (neighbour list) or via the

“measurement control” message.

With this we can get following info:

The BLER downlink

Carrier RSSI

Data Throughput Downlink

Data Throughput Uplink

Ec/No Active Cell

Ec/No Monitored Cell

Pilot BER

Random Access Initial Tx Power

Random Access Preamble Count

Random Access Preamble Step

Random Access Tx Power

SIR target

UE Tx Power

(5)

Radio Link Performance

Troubleshooting:



Distant servers



Too many servers



Unnecessarily large neighbour lists



Excessive soft handoff

Event Detection and

Drive Test Analysis:



Coverage problems



Poor UL or DL, coverage limited, interference



Handover problems



Missing neighbours



Pilot pollution

Overall Call View:



Detailed dropped call and failed set-up level analysis



Detected problem(s) identified per call



Individual call extraction for detailed message level analysis

Neighbour List Analysis:



Generation of recommendations for optimal neighbour list settings



Integration with Network Element Database



Based on UMTS/WCDMA scanner drive test data

Supported

Measurements with

Scanner are:



Layer 1 scanner measurements (for example EcIo, RSCP, etc.)

Supported

Measurements with

Handset are:



Layer 1 handset measurements (for example EcNo, TxPow, etc.)



RRC Layer 3 signalling – Call Control (CC), Mobility Management (MM), GPRS Mobility Management,

GPRS Session Management

Actix

:

Analysis tool Actix analyser is a tool for post-processing cellular network data (GSM, CDMA, WCDMA).

The tool is specifically tailored to import measurement data from various (measurement) tools and file

formats and then present it in map, table, workbook or chart format. Also it is possible to define your

own specific queries

(6)

Dominance Verification

First task is to overlay the cells dominance area to check that the coverage

areas of the cells are clear, all sites are “on air” and there are no cross feeders

Missing Site- No

dominance

server in the

(7)

Coverage

• If lack of coverage is indicated then

coverage enhancement is required.

• Has excessive tilting been used? Is

up-tilting or an Panning the antenna

an option for some cells.

• For initial roll out stages (low traffic)

increasing the P-CPICH power is an

option the feasibility will depend upon

the margins in the link budget

• Poor coverage during Pre-

Optimisation & Acceptance

(8)

Coverage

Planned Site

• What impact will any planned sites (if any)

have on the overall performance?

• A study of UE logs for the area should

provide an indication of the number of failed

Setups/calls that would have been prevented

if a planned site was available.

• Failures due to missing sites needs to be

estimated and this information should be

communicated to the operator. It may be

possible to influence the roll out schedule

based on this information

(9)

Coverage verification with RSCP Scan for each SC

• CPICH_SCAN_RSCP_for SC X overlay plotted out for all three sectors of a

site showing the coverage for each sector

• Gives a good indication if a sector is radiating too far and may need down

tilt.

281

282

280 Scan RSCP for SC 282

Scan RSCP for SC 280

Scan RSCP for SC 281

280

281

(10)

SC162

No measurements

in vicinity of sector

C (SC = 162)

Sector B-SC161

No measurements

in vicinity of sector

C (SC = 162)

Verification of Swapped feeder or other issue

• Plotting RSCP of each SC highlights any hardware or databuild issues where

the coverage area of the cell is different to the planned coverage.

• This will include swapped feeders, incorrect azimuths/tilts or incorrect

scrambling codes assigned to the cell

SC161 and SC162

Tx from same

sector

crossed feeders can occur at:

• Antenna

(11)

RSCP Verification

Check that the RSCP levels for the area meet the target thresholds for the

service and environment (clutter, building loss)

(12)

Ec/No Quality

• Identify areas of poor quality

• Identify excessive polluters (overshooting cells)

• Recommend physical optimisation: downtilts and panning.

• Implement changes.

(13)

Ec/No Verification

If coverage is acceptable then check for area of poor EcNo in the area.

Poor coverage areas can

still have good Ec/No if there

(14)

Pilot Pollution Analysis

I

Pilot pollution areas can be shown with Scanner Pilot Pollution query with user

defined RSCP and EcNo levels

(CPICH_SCAN_EcNo_Sorted_By_EcNo (0)<-12) AND

(CPICH_SCAN_RSCP_Sorted_By_EcNo (0)>-92)

(15)

Pilot Pollution Analysis

II

Pilot polluter workbook shows the worst polluters in the area e.g. SC 344

have most of the samples

SC 344 displayed

over pilot pollution

(16)

Pilot Pollution Example

Scanner sees 5

SC‟s, all within 5 dB

of each other.

This is clearly an

area suffering from

pilot pollution.

RSCP is good -91

Looking at the dashed lines

to the cells serving at this

point we can see that there

are several cells (SCs 136,

496, 272) which are not

particularly close to the point

(17)

Pilot Pollution Example

SC 272

• This site is clearly

radiating much too far

and is a definite

candidate for

down-tilting.

• By removing

scrambling codes

within 5dBs of the best

server, we can

improve the best

server‟s Ec/Io

SC 272 is the furthest away these sites and is joint second best server.

(18)

UL Coverage Verification

By using UE together with Scanner during testing we can check the UEs

transmit power for problem areas where UE cannot maintain the link quality

(19)

Multi-path

Problem

A

Dominance Area OK

Yes

amount of Scrambling

Codes > X

A

No

A

No

Low

CPICH Ec

Pilot

Pollution

Aggregated to Peak

> 3 dB

A

Yes

A

Bad

Ec/Io

No

A

Possible

Actions/Solutions

1. Antenna Tilting

2. Antenna Panning

3. Change Antenna Type

4. Change Antenna Height

5. Change CPICH Tx Pwr

6. (Add sites)

Scanner and UE drive

logs

Compare scanner measurements with

planned quality and coverage

thresholds

CPICH RSCP =>

planned threshold

e.g. -90 dBm

CPICH Ec/No =>

planned threshold

e.g. -12 dBm

Yes

No

Coverage

target agreed

with customer

Ec/No target agreed

with customer &

depends service mix

Currently X = Max AS

size = 3 for Nokia RAN

(20)

RF Optimisation

• Check if the cause of call setup failure is CPICH RSCP and Ec/No

coverage problem

• The received best server‟s CPICH RSCP and Ec/No will be compared to

the coverage thresholds at the location where call setup failed and if best

server‟s CPICH RSCP OR Ec/No is less than the thresholds, coverage

optimisation will be performed.

• The thresholds of CPICH RSCP and Ec/No depend on UE‟s sensitivity:

–

CPICH RSCP coverage threshold = -110 dBm

–

CPICH Ec/No coverage threshold = -16 dB

• Simulation using NetActPlanner will be used to verify the proposed

(21)

KPI Route CSF Causes

8.33%

8.33% _8.33%

75.00%

RF Issue : Interference

System Issue :NodeB

UE Issue

Unknown

KPI Route Call Drop Causes

11.11% 14.81% 18.52% 29.63% 3.70% 22.22% _{RF Issue : Interference} AS Update Failure : Cause unknown Unknown UE Issue Missing neighbor RF Issue : Coverage

To better understand the failure mechanisms that contribute to radio failure

as measured with network statistics.

Categorise the failure causes for Call Setup and drop call performance.

• Drop Call analysis shows that significant proportion of Interference failures

is due the missing neighbour

• Analysis also confirms that conclusion derived from the scanner data that

DL interference is major contributing factor to failure on the radio Interface

(22)

Down-tilting of interfering cells‟ antenna,

which generate pilot pollution

Change CPICH Tx Power: Increase

serving cell‟s Tx power but decrease

interfering cell‟s Tx power

Change antenna bearing angles of cells

involved in pilot pollution

Change antenna patterns of cells

involved in pilot pollution. Smaller gains

for interfering cells and higher gain for

victim cell

Decrease antenna height of interfering

cells and increase antenna height of

victim cell with adequate tilting angle

 Reducing the tilt of serving cell‟s

antenna to extend coverage radius and to

improve unsatisfied coverage area

Increase CPICH Tx Power of serving cell

Change Antenna Bearing Angle: Focus

the main beam of antenna to coverage

holes and low RSCP area

 Change Antenna Pattern: Displace with

higher gain antenna with adequate

antenna tilting

Increase serving cell‟s antenna height to

get higher effective antenna gain but there

is risk to make undesirable inter-cell

interference to adjacent cells

Tuning methods for

Coverage Problem Area

High Priority

_{Dominance Problem Area}

Tuning methods for

(23)

Physical Optimisation - Antenna changes

Antenna tilting (or panning) is needed mainly if:

• There is too much interference created by a site covering too much

(overshooting)

• There is lack of coverage or dominance

One should carefully consider the tilt type

• Electrical or mechanical (both have advantages and disadvantages)

Antenna tilting should be followed by another round of drive-tests in order to

evaluate the impact

Multiple antenna tilt or azimuth changes in the same time in the same area

should be avoided

Decisions must be made based on scanner measurements.

• UE measurements can be also used, but they can sometimes lead to

wrong results, for example in case of missing neighbours.

Tilt changes include both down and up-tilting.

(24)

Mechanical

• The downtilt angle varies over the

horizontal beamwidth. Patterns

measured ±90° from the centre of

the beam have decreasing tilt angle

until there is no tilt 90° from the main

beam.

• The horizontal half-power beam

width increases with greater downtilt

angle.

• The resulting gain reduction

depends on azimuth direction.

Electrical

• There is uniform downtilt over the

whole azimuth range.

• The horizontal half-power

beamwidth is independent of the

downtilt angle.

• There is identical gain reduction in

(25)

Mechanical Tilt require Site Visit

No “real“ maximum tilt angle

Mechanical down tilt causes deformation in the

horizontal pattern

Deformation of the

horizontal pattern

Mechanical

Down tilt kit

(26)

Electrical Tilt

• The Adjustable EDT antennas can be adjusted manually or remotely

• Phase shifters provides variable phase distribution which in turn keeps the

pattern shape constant

• Maximum Adjustable EDT range approx. 0-14° (normally 0-8°)

• For a higher downtilt angle a combination of the Mechanical DT and the

Adjustable EDT is recommended

Horizontal pattern

remains constant

Remote

use

Manual

use

(27)

Impact on Ec/No

(28)

Impact on Ec/No

(29)

Antenna tilt example -1 deg E-tilt – Overshooting

Cell

No dominant

Server in the area

due the missing

site JS9218

Site JS9125 (SC28) from cluster 5

is overshooting to cluster 1

Before

After

Site JS9125 (SC28) was tilted by 1

deg (E-tilt From 4 deg to 5 deg)

(30)

Neighbour List Verification

Neighbour definitions required by cell re-selection and handover

Soft handovers are based upon intra-frequency neighbour list

Hard handovers are based upon either intra-frequency (Between RNCs without Iur or

Iur congestion) , inter-frequency (IFHO) or inter-system (ISHO) neighbour lists

Each neighbour has a set of associated parameters e.g. CPICH measurement offset

The post processing tool should be able to suggest appropriate neighbour lists

Strategy for initial system deployment is to place the emphasis upon adding

neighbours rather than removing them

Intra-Frequency

Neighbors

Cell a

Cell b

Cell c

Cell d

Cell e

M

ax.

31 Inter-Frequency

Neighbors

Cell k

Cell l

Cell m

Cell n

Cell o

M

ax.

48 (32

/carr

ier)

Inter-System

Neighbors

Cell r

Cell s

Cell t

Cell u

Cell v

M

ax.

32 Total max 111 in RNC

database, limitation due to

specifications of SIB11/12

size

(31)

There is a restriction on the number of cells contained in SIB 11/12 due to an

inconsistency problem in the standards

SIB 11/12 should be able to contain a maximum of 96 neighbours

• (32 intra-frequency cells, 32 inter-frequency cells and 32 GSM cells)

On the other hand, the physical size of SIB data (no more than 3552 bits) has

capacity only for about (depending on the type etc.)

47 cells!!

If too many adjacencies are declared, the cell will go blocked by system with

alarm:

• 7771 WCDMA CELL OUT OF USE (BCCH scheduling error)

As a rule of thumb, assuming that …

ADJS=15, ADJG=15, ADJI=15

… and “realistic worst case values”, SIB11 length =

3187.5 < 3552 -> OK!!

Some sites might need additional neighbors and might pose a problem with the

SIB11 limitation

• Avoid setting

AdjsQoffset2

values, different CPICH values or other parameters

used to tune cell reselection or handover

Further information Technical Note No. 046 / Restriction on number of

cells in SIB11/12 due to inconsistency problem in 3GPP TS 25.331

Max. 96

neighbours due

SIB limitation

(32)

Neighbour List Verification – SIB 11/12

When offsets are added to the neighbours or the CPICH power of the neighbour cell

is different to that of the serving cell the length of the message for each neighbour in

SIB 11/12 is increased

• The length of one ADJS with no offsets is 48 bits

• The length of an ADJS with

AdjsQoffset1

or

AdjsQoffset2

is 48 or 56 bits on a

case by case basis (average length 55.2 bits)

• The length of an ADJS with

AdjsQoffset1

and

AdjsQoffset2

is 56 or 64 bits on a

case by case basis (average length 62.1 bits)

When the neighbour cell has a different CPICH Tx Power from the serving cell

• Without Offset and

AdjsPtxCPICH

: 54.2bits

• With

AdjsQOffset1

or

AdjsQOffset2

: 61.1bits

(33)

Neighbour List Verification

There are a number of approaches that can be used to both plan and verify

the neighbour plan

Drive Testing

Neighbour

Creation

Manual Check

Analytical

Planning Tool

Other

Neighbour

Creation

Neighbour

Verification

Manual Check

Measured

Network Stats

(34)

Neighbour List Verification - Analytical

• Analytical Neighbour Planning methods are traditionally used to generate

original neighbour lists but they can also be used for verification and new site

addition.

• Planning Tools – use coverage arrays and handover parameter data to

determine required neighbour relations

• Other desk top tools can be based on:

• Site coordinate data,

• Cell azimuth data,

• Cell coverage distance estimations

(35)

Neighbour List Verification - Manual

• Cell in blue had nine 3G

neighbours defined –

highlighted in green on

map

• 6 missing neighbours

were identified for this

site and added – Manual

Check would have

(36)

• Process starts directly with the drive test

Record drive test

results with Scanner in

„TOP N‟ mode

Start

Neighbour List Verification – Drive Test

Input Data

Source

CPICH Scrambling code Ec/Io

Scanner

Measurement position

Scanner

Cell ID, cell position, cell azimuth Planning Tool

Cell scrambling code

Radio Design

(37)

High Level

Process

_{Record drive test}

results with Scanner in

„TOP N‟ mode

Analysis (within

Actix Analyzer)

Start

Finish

Numerical Analysis

• Part automatic and part manual neighbour list analysis

• Analysis within a tool such as Actix Analyzer is automatic and numerical

• Analysis requires the definition of a

neighbour window

which is applied to the

CPICH Ec/Io measurements

• Recommended to set the

neighbour window

as 10 dB (drop window + margin)

Neighbour

Window

Ec/Io

Time

Strongest

Ec/Io

Neighbours

reported when

within this range

216

349

83

436 SC

Site

Sector

97 85 (47.4%); 303 (17.5%)

Num Of Samples

Suggested NBR Additions

Reading Rubgy FC

00179719B2

97 351 (28.9%)

Ewer Park Stud

00161126C

WOODLEY ATE

00001085A

96 350 (34.4%); 84 (25.0%)

TILEHURST ATE

00001081B

90 434 (22.2%); 283 (22.2%)

(38)

• Analysis provided by the post

processing tool:

• Consider adding neighbours

reported by the tool

• If neighbour list is full then

consider replacing some of

the existing neighbours

• Do not remove existing

neighbours without further

investigation

Run (Actix) Analyzer

Routine

No

Consider adding

suggested

neighbours

Start

Progress to

further additions

Is the

Neighbour

List full?

Consider

replacing

existing

neighbours by

those suggested

by the tool

(39)

• As a minimum define the

neighbour list as

All cells belonging to that site

The first perimeter of cells

Cell for which

the neighbour

list is being

defined

Neighbours

Yes

Add

neighbours

Complete visual

inspection of

neighbour list

Does list include

all cells belonging

to that site and

the first perimeter

of cells

Continue from Analysis

Finish

Add any other

neighbours which

may improve

coverage

• Subsequent manual

tuning of neighbour list

Neighbour List Verification

(40)

Optimisation

activities to improve call performance

Common performance issues that affect any service

Voice (AMR) call performance

CS Video call performance

PS call performance

(41)

41 © Nokia Siemens Networks

Common Call Performance Issues

Presentation / Author / Date

Behaviour

Problem

Description

Possible solutions

Call set-up failure

Poor coverage area

If problem is poor coverage, this means poor RSCP (<-95 dBm) thus also the EcNo degrades very rapidly (< -12 dB) when the coverage border is reached.

Check Antenna line installation (antenna position and quality, cable length and quality).

Call drop Check that CPICH powers are balanced between the

studied cells.

Check presence of shadowing obstacles.

Add a site to the area.

Call set-up failure

Poor dominance area.

No main server in the area, too many cells with weak CPICH level.

Use buildings and other environmental structures to isolate cell(s) coverage.

Call drop CPICH EcNo is usually very bad even the RSCP is good _{e.q. RSCP –80…-90 dBm but EcNo about –10 dB} Down tilt antennas to make cells dominant and limit effects of interfering cell(s).

Check antenna bearing.

Add a site.

Call set-up failure

Pilot Pollution

Bad CPICH Ec/Io (<-12 dB) level although CPICH RSCP level is good. High site in the neighbourhood may cause interference.

Find interfering cell from Scanner results.

Call drop Adjust antenna bearing and down tilt or lower the antenna

height (too much tilt will break the dominance).

Add interfering cell to the neighbour of the serving cell.

Dropped call/SHO failure Missing neighbour

A good usable neighbour is present within cells coverage area, can cause DL interference if it is not in the active set.

Check scanner data and look for missing neighbours. Swapped sectors in WBTS. Check the cabling in antenna line.

Call set-up Failure

High PrxTotal due to UL External interference

The PrxTotal level is significantly higher than expected in no/low load conditions.

Try to figure the possible area/direction of the interference by checking PrxTotal level on neighbouring cells.

Call drop Alternatively use spectrum analyser & directive antenna to

locate interferer.

Inform operator/regulator about the found conditions.

Check if auto tuning range is large enough (20 dB).

Call set-up failure

High PrxToatal due to wrong MHA settings

In case of MHA is used in BTS check MHA and cables loss parameters, otherwise PrxTotal value will be too high.

Call drop MHA settings should be checked, see more in reference

(If MHA parameter is set to ON, Cable loss parameter is used, Cable loss = Real MHA gain = Feeder loss parameter)

Call set-up failure High Prxtotal due to Installation problems

Check the antenna installation as the last alternative in high PrxNoise case.

Call drop Cell set-up failure

Bad RRC connection set-up success rate due to slow Ue cell reselection

RRC connection set-up complete message not heard by BTS.

Set parameters so that reselection process will start earlier: Qqualmin, Sintrasearch and Qhyst2 as per latest

recommendation

Long call set-up time Long time interval for sync between RNC and BTS before connection

The value of Parameter N312 is too high: maximum number of “in sync” indications received from L1 during the establishment of a physical channel

Use smaller value N312 (2, recommendation is 4). Use Actix for checking the call set-up delay (L3 messages). Use call set-up time optimisation feature Dynamic setting of “ActivationTimeOffset” (possible in RAN1.5.2 ED2) enables 200 to 500ms reduction for set up delay.

(42)

Common Call Performance Issues

Behaviour

Problem

Description

Possible solutions

Dropped call SHO to wrong cell will cause drop call.

Overshooting cell come temporarily into active set and forces a suitable serving cell to be dropped out. Later RSCP suddenly drops in the “wrong cell” and causes a dropped call because there is no neighbour defined.

Pan away overshooting cell if it is too close to the serving cell, otherwise apply down tilting as well.

Dropped call Cell suffering from UL interference = DL (CPICH) coverage much bigger than UL coverage

As the UE Tx power is not enough for target cell synchronisation, the SHO fails which will cause call drop later.

Use cell individual offset (negative value) parameter to balance the DL and UL coverage.

Check traffic direction of in-car UEs to decide which cell requires offsets. Dropped call DL CPICH coverage < UL coverage Cell with lower CPICH power than the

surrounding is having “too good” UL performance, as this cells‟ UL cannot be used efficiently due to SHO is decided upon DL (CPICH Ec/No).

Use cell individual offset (positive value) parameter to balance the DL and UL coverage.

Note: Cell individual offsets are not taken into account when calculating the added cell Tx power.

Dropped call

Round the corner effect

The call drops due to too rapid CPICH coverage degradation for Cell A, and therefore there is not enough time for SHO.

Use cell individual offset (positive value) parameter to balance the DL and UL coverage.

Note: Cell individual offsets are not taken into account when calculating the added cell Tx power.

Dropped call/SHO failure Too many neighbours In SHO area the number of combined neighbouring cells become more than 31. HO list is created using RNC algorithm in the final stage some of the neighbours will randomly be removed.

Delete unnecessary neighbours.

(43)

Video Call Performance Issues

Behaviour Problem

Description

Possible solutions

Dropped call Not enough DL power to maintain good quality

CS video connection needs more power to maintain the SIR target and thus also BLER target.

Increase the max DL Radio Link power by decreasing the CPICHtoRefRaBOffset

In case the max power increment is a lot (~3dB) then the minimum power is increased by 3dB as well which can lead to the minimum power problems (BTS sending too much power to the UEs close to the BTS and therefore causing problems to the UE and even dropped call)

Therefore the PCrangeDL parameter should be tuned according to the CPICHtoRefRabOffset parameter tuning (from the default)

Call set-up Failure

High PrxTotal due to UL External interference

Try to figure the possible area/direction of the interference by checking PrxTotal level on neighbouring cells.

Call drop

Alternatively use spectrum analyser & directive antenna to locate interferer. Inform

operator/regulator about the found conditions.

(44)

ISHO performance

Behaviour

Problem

Description

Possible solutions

Call drop

RAN is not working

correctly during SHO.

No GSM neighbour list is

sent for measurements in

case there are 3 cells in

Active Set.

This should be corrected

in laterRAN release(s).

Call drop

Failure to decode BSIC

before the call drop.

CM starts too late

Set higher ISHO

thresholds, FMCS: CPICH

EcNo, CPICH RSCP, UE

TX Pwr

Call drop

Failure to decode BSIC

before the call drop.

BSIC verification takes too

much time.

Set smaller measurement

time for GSM cells,

FMCG: Maximum

measurement period,

Minimum measurement

interval,

(45)

NETWORK HEALTH CHECK

The Network health check ensures that the planned network is implemented correctly, all cells are up and

running and correct parameters are set. These should be done before optimisation. There are many

checks to look at: -

Alarm check (BTS, RNC, other)

SW and Parameter check

Neighbour consistency check

Cell load check

KPI check

UE performance check for all the services in a controlled environment

Cell load checks

Cell load can be checked by looking at the UL interference situation with PrxNoise counter

in each cell. Normally the PrxNoise is around –102…-105 dBm, but if it is more than this,

there is something wrong in the cell. The reason could be external interference, or

incorrect MHA parameters.

The total load in UL and DL (PtxTotal, PrxTotal) should be less than (PtxTarget, PrxTarget),

otherwise the cell is overloaded.

(46)

(47)

(48)

Major RS reports for Performance analysis

Report Name Description

RSRAN000

System_Program_RNC_Level_Daily

RSRAN018

Inter System_Handover_Reasons

RSRAN019

Inter System_Handover_per_Cause

RSRAN023

Inter System_Handover_Performance

RSRAN044

IFHO_Adjacencies

RSRAN045

ISHO_Adjacencies

RSRAN046

SHO_Adjacencies

RSRAN066

Node_B_Capacity Daily

RSRAN067

Cell_Capacity_daily

RSRAN068

RNC_Capacity_Daily

RSRAN068

RNC_Capacity_Hourly

RSRAN070

Allocated_Traffic_Amounts_(R99_+_HSPA)_Daily

RSRAN073

Service_Session_Accessibility_Analysis_Daily

RSRAN079

Service_Session_Retainability_Analysis_Daily

RSRAN084

System_Program_Cell_Level_Daily.xls

(49)

Various Reporting-Suit reports for KPI analysis

Sl.N

o

3G RAN Reports

Report Name

Object

Type

Object Aggregation

1 System Program

RSRAN000

PLMN

RNC

2 System Program

RSRAN084

PLMN

WCEL

3 Capacity

RSRAN066, RSRAN067, RSRAN068,RSRAN087,RSRAN085

PLMN

WBTS,WCEL,RNC & IuB

4 Capacity

RSRAN066, RSRAN067, RSRAN068,RSRAN087,RSRAN085

PLMN

WBTS,WCEL,RNC & IuB

5 Service Level

RSRAN073, RSRAN079,RSRAN101

PLMN

PLMN,RNC

6 Service Level

RSRAN073, RSRAN079,RSRAN101

PLMN

WCEL,RNC

7 Traffic

RSRAN070, RSRAN077

PLMN

WCEL

8 Traffic

RSRAN070, RSRAN077, RSRAN088

PLMN

WCEL, RNC

9 Mobility & Handover

RSRAN033, RSRAN018, RSRAN019,

PLMN

WCEL

RSRAN023, RSRAN044, RSRAN045,

RSRAN046, RSRAN028

10 Mobility & Handover

RSRAN033, RSRAN018, RSRAN019,

PLMN

WCEL

RSRAN023, RSRAN044, RSRAN045,

RSRAN046, RSRAN028

11 HSPA

RSRAN051, RSRAN039, RSRAN092, RSRAN091, RSRAN041,

RSRAN074, RSRAN090, RSRAN034, RSRAN075,RSRAN040

PLMN

WCEL

12 HSPA

RSRAN051, RSRAN039, RSRAN092, RSRAN091, RSRAN041,

RSRAN074, RSRAN090, RSRAN034, RSRAN075,RSRAN040

PLMN

WCEL

13 Signalling

RSRAN027, RSRAN038

PLMN

WCEL

14 Signalling

RSRAN027, RSRAN038

PLMN

WCEL

15 PRACH Propagation

Delay

RSRAN104

PLMN

WCEL

16 Ec/No Distribution

RSRAN028

PLMN

WCEL

17 Prx Distribution

RSRAN067

PLMN

WCEL

18 Ptx Distribution

RSRAN067

PLMN

WCEL

19 RNC Hardware

RSRAN102

PLMN

RNC/DSPPID

20 Customized XML file /

Raw Counters

If customised reports required for Assessment are not available

with Local engineer, we can extract that information by uploading

(50)

Call Setup failures for Voice and Packet

RRC connection setup

RAN resources are reserved

for signaling connection

between UE and RNC

RRC access

Connection between UE and

RRC

RRC active

UE has RRC connection. If

dropped, also active RAB is

dropped.

RAB setup

Attempts to start the call

RAB setup access

RAB active phase

UE has RAB connection

CSSR For Voice affected if any of

the followings take place.

RRC Conn. Setup Fail

RRC Conn. Access Fail

RAB Setup Fail

RAB Setup Access Fail

Setup

Complete

Access

Complete

Active

Complete

Setup

Access

Active

A

tt

e

mp

ts

Setup failures

(blocking)

Access failures

A

ccess

Active

Release

Active

Failures

RRC

Drop

Success

Phase:

(51)

Call/packet Setup improvement

• RRC/RAB/PS call Setup & Access Analysis Process Flow Chart

Sites

OK ?

Cell and Neighbour

Cells availability

Alarms/Tickets

Setup

/Access

Yes

Setup

/Access

Setup

Failure

Cause?

Capacity

Optimisation

BTS/TRANS/FROZBS

UL/DL Interference (DL codes)

AC

Troubleshooting

RNC

RF

Optimisation

Top (N) RRC Setup

and Access failures

Top (N) RAB Setup/Access

or PS Setup failures

Coverage/I

nterference

setup

Interference

Coverage

3G cell at

inter-RNC

border ?

SRNS

Relocation/Iur

troubleshooting

Yes

NO

Access

Setup/Access

SHO based on DSR,

CPICH EcNo

difference

RAB/DCH setup

&failures, UL

coverage counters

to see UL spikes

RRC_setup/SRB_act fails,

RB_setup failures for

HSDPA

DCH reconfiguration

failures AC/BTS/trans

SHO branch setup fail

BTS/Iub, RNC capacity SW,

new DSP counters

Rej_DCH_due to

power or codes

(UL/DL)

RAB setup fail voice

Iur/trans, DCH setup

failure for NRT in Iur

Fail_MAC_d_setup

_HSDPA

(52)

Low CSSR

• RRC Setup Analysis

1. Check the problem cells and its neighbouring cells of any faulty alarms

2. Identify root cause failure distribution using Service Report ->

RSRAN073

3. RRC_CONN_STP_FAIL_AC

Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity

UL Power Spikes -> Disable UL Admission Control to if the number of failures is critical (Prxtarget ->30 dB)

M1002C1 CH_REQ_LINK_REJ_UL_SRNC ----> Evaluate Prx Resource Problem

M1002C2 CH_REQ_LINK_REJ_DL_SRNC --->Evaluate Ptx Resource Problem

4. RRC_CONN_STP_FAIL_BTS

Evaluate NBAP counters (radio link reconf. Failures) and KPIs for troubleshooting BTS resources

Check BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to

evaluate lack of Channel Elements (more info in RSRAN066)

Expand the Capacity or decrease the traffic offered to the site

In case BTS is not responding delete and re-create COCO

5. RRC_CONN_STP_FAIL_TRANS

Evaluate Number of reconfiguration failure due the transmission

Check COCO Configuration

Use AAL2 Mux in case of two WAM

Expand the Iub capacity or decrease the traffic offered to the site

6. RRC_CONN_STP_FAIL_RNC

(53)

Low CSSR

• RRC Access Analysis

7. RRC_CONN_ACC_FAIL_RADIO

This is quite Dominant failure cause in case of sync. problems

This could happen in Coverage border

UL Coverage -> Decrease Cell Coverage (higher RxlevMin) if the cause is

UL interference

DL Coverage-> Increase Cell Coverage max :CPICHToRefRABOffset (2->0

dB)

Service Level -> RSRAN073

NBAP: Synchronisation Indication

L1 Synchronisation

L1 Synchronisation RRC: RRC ConnectionSetup Complete (DCH)

X

UE

BT

S

R

N

C

X

RRC Access Failures for L1 synchronization

L1 Synchronisation

L1 Synchronisation RRC: RRC Connection Setup Complete (DCH)

X

UE

BT

S

R

N

C

RRC Access Failures due to MS

Cell Reselections (no

error)

RRC_CONN_ACC_F

AIL_MS

UL Coverage ->

Tune Cell

Dominance (or

CPICH) in order to

balance UL and DL

(if UL interference if

not the cause)

(54)

Low CSSR : Propagation delay

• RRC Access Analysis

9. If RRC setup/access failure due to Radio/MS, it is also possible to check whether UEs

are located at distance area or close to cell edge area



Propagation delay counters from

RRC measurement M1006C128-C148

reports call

setup distance during RRC connection request or cell update



This give hints that either cells has large coverage area (tall sites with

over-shooting) or non-optimum cell coverage from neighbouring cells

0 100000 200000 300000 400000 500000 600000 Y_CLA SS _0 Y_CLA SS _1 Y_CLA SS _2 Y_CLA SS _3 Y_CLA SS _4 Y_CLA SS _5 Y_CLA SS _6 Y_CLA SS _7 Y_CLA SS _8 Y_CLA SS _9 Y_CLA SS _10 Y_CLA SS _11 Y_CLA SS _12 Y_CLA SS _13 Y_CLA SS _14 Y_CLA SS _15 Y_CLA SS _16 Y_CLA SS _17 Y_CLA SS _18 Y_CLA SS _19 Y_CLA SS _20 0.00% 20.00% 40.00% 60.00% 80.00% 100.00% 120.00% average CDF

(55)

Low CSSR: UL interference counters

• 10. From RU10, new coverage counters (RAN1630) for total

uplink power (RTWP) measurement also can be used to

identify RRC setup/access fail due to AC/Radio/MS.

–

All the received power is taken into account, not just

Rel99

–

These counters could be used to see UL interference in

the cell

M1000C320 Cell_Resource

RTWP_CLASS_0

M1000C321 Cell_Resource

RTWP_CLASS_1

M1000C322 Cell_Resource

RTWP_CLASS_2

M1000C323 Cell_Resource

RTWP_CLASS_3

M1000C324 Cell_Resource

RTWP_CLASS_4

M1000C325 Cell_Resource

RTWP_CLASS_5

M1000C326 Cell_Resource

RTWP_CLASS_6

M1000C327 Cell_Resource

RTWP_CLASS_7

M1000C328 Cell_Resource

RTWP_CLASS_8

M1000C329 Cell_Resource

RTWP_CLASS_9

M1000C330 Cell_Resource

RTWP_CLASS_10

M1000C331 Cell_Resource

RTWP_CLASS_11

M1000C332 Cell_Resource

RTWP_CLASS_12

M1000C333 Cell_Resource

RTWP_CLASS_13

M1000C334 Cell_Resource

RTWP_CLASS_14

M1000C335 Cell_Resource

RTWP_CLASS_15

M1000C336 Cell_Resource

RTWP_CLASS_16

M1000C337 Cell_Resource

RTWP_CLASS_17

M1000C338 Cell_Resource

RTWP_CLASS_18

M1000C339 Cell_Resource

RTWP_CLASS_19

M1000C340 Cell_Resource

RTWP_CLASS_20

M1000C341 Cell_Resource

RTWP_CLASS_21

0.00 200.00 400.00 600.00 800.00 1 000.00 1 200.00 1 400.00 29. 07.2 009_ _23: 00: 00 30. 07.2 009 __0 3:00 :00 30. 07.2 009 __0 7:0 0:00 30.0 7.20 09_ _11: 00:0 0 30.0 7.2 009 __1 5:0 0:00 30.0 7.20 09__ 19: 00: 00 30.0 7.20 09__ 23: 00:0 0 31.0 7.2 009 __0 3:0 0:00 31.0 7.20 09__ 07: 00: 00 31. 07.2 009 __11 :00: 00 31. 07.2 009 __1 5:00 :00 31. 07.2 009 __1 9:00 :00 31.0 7.2 009 __2 3:0 0:00 01.0 8.20 09__ 03: 00:0 0 01.0 8.2 009 __0 7:0 0:00 01.0 8.2 009 __1 1:0 0:00 01.0 8.20 09__ 15: 00:0 0 01.0 8.20 09__ 19: 00: 00 01.0 8.20 09__ 23: 00: 00 02. 08.2 009 __03 :00: 00 02. 08.2 009 __0 7:00 :00 02. 08.2 009 __1 1:00 :00 02.0 8.2 009 __1 5:0 0:00 02. 08.2 009 __1 9:00 :00 02. 08.2 009 __2 3:00 :00 03.0 8.20 09_ _03: 00:0 0 03.0 8.2 009 __0 7:0 0:00 03.0 8.20 09__ 11: 00: 00 03. 08.2 009 __1 5:0 0:00 RTW P_CLASS_14 (M1000C334, -92..-89 dBm) RTWP_CLASS_15 (M1000C335, -89..-86 dBm) RTW P_CLASS_16 (M1000C336, -86..-83 dBm ) RTWP_CLASS_17 (M1000C337, -83 dBm..-80 dBm) RTW P_CLASS_18 (M1000C338, -80..-75 dBm) RTWP_CLASS_19 (M1000C339, -75..-70 dBm) RTW P_CLASS_20 (M1000C340, -70..-65 dBm) RTWP_CLASS_21 (M1000C341, > -65 dBm)

RRC Access Analysis

Temporary High UL

interference:

class_21 could be

seen

(56)

Low CSSR



With RU10, there is new counters to measure the setup success of standalone Signaling Radio

Bearers (SRBs). Standalone SRB means a successfully established RRC connection that is

waiting for the RAB assignment



SRB active fail is pegged when RNC sent RRC:RRC connection Release before RAB assignment



With RNC_1219a, this give better visibilities where low CSSR is somehow caused by failure in

active standalone SRB phase

(57)

Low CSSR

• AMR RAB setup/access Analysis

1. Check the problem cells and its neighbouring cells of any faulty alarms

2. Identify root cause failure distribution and main failure contributor using Services ->

RSRAN073

3. RAB_STP_FAIL_XXX_AC

Check UL Interference, DL Power & Code occupancy if there is need to upgrade radio capacity

REQ_CS_VOICE_REJ_UL_SRNC -> Evaluate Prx cell resource

REQ_CS_VOICE_REJ_DL_SRNC -> Evaluate Ptx cell resource

NO_CODES_AVAILABLE_SF128/SF32 -> Evaluate AMR voice / PS64 code congestion

Check parameter setting with UL throughput based AC and power based AC

4. RAB_STP_FAIL_XXX_BTS

Evaluate NBAP counters (radio link reconf. Add failures) and KPIs for troubleshooting BTS resources

Check BTS configuration in terms of WAM and CE allocation – Use Channel Element (5001) Counters in order to evaluate lack of

Channel Elements

Expand the Capacity or decrease the traffic offered to the site

5. RAB_STP_FAIL_XXX_TRANS

Evaluate Number of reconfiguration failure due the transmission

Check M1005C128 CANC_ADD_SRNC_TRAN_STP_FAIL

Check RAB_STP_FAIL_XXX_IUB_AAL2, M1001C531-C533

6. RAB_ACC_FAIL_XXX_UE

Evaluate Cell resource Prx and Ptx (for example high uplink interference)

Check RB reconfiguration failure ration ( If offset for activation time (RNC) setting is insufficient – recommmended is 500-700ms )

7. RAB_ACC_FAIL_XXX_RNC

Typically RNC fault or Incoming SRNC Relocation Failure (inter-RNC border)

Required ICSU log tracing if no RNC fault or SRNC relocation problem

(58)

Low CSSR

• AMR RAB Setup/Access Analysis

8. RAB_Setup_FAIL_CS_Voice_LIC

Counter incremented when the RNC rejects a CS Voice RAB request due to AMR capacity license Exceeded (only for

RNC2600)

9. RAB_Setup_FAIL_CS_Voice_Iur_TR

Counter incremented when a CS voice traffic class RAB setup fails due to Iur transport resources shortage

10. RAB_Setup_FAIL_CS_Voice_Iu_CS

Counter incremented when a CS voice traffic class RAB setup fails due to Iu-CS transport resources

(59)

Low CSSR

• Rel99 NRT RAB Setup Success Analysis



There is two ways to evaluate the Rel99 NRT RAB setup success performance



M1001,

RNC_576e

Packet Service Setup Success Ratio (CSSR) / CSSR PS NRT



M1022,

RNC_943a

R99 Setup Success Ratio from user perspective for NRT/ R99 stp SR

Usr



Since RNC_576c (M1001) is measured NRT DCH setup upto 0/0kbps, it is always showing

>99.5%. So it is not useful for data call setup analysis



Packet calls starts with user plane capacity allocation (transfer from FACH/PCH, DCH 0/0) and

ends with dedicated resource release (transfer back to FACH/PCH, DCH 0/0, RAB release,

outgoing relocation, HHO, ISHO)

Service -> RSRAN073

(60)

Low CSSR

• Rel99 NRT RAB Setup Success Analysis



With RU10, there is new counters which gives better visibilities in terms of Rel99 NRT DCH setup

failure causes (DCH0/0 -> DCH x/x kbps or DCH upgrade request)



The number of NRT DCH setup rejects for interactive/BG traffic class due to running out of

channelisation codes in DL and power in DL/UL (This counter includes initial DCH setups, handover

attempts and channel type switches from HS-DSCH to DCH)



The number of NRT DCH reconfiguration rejects (bitrate upgrade) for interactive/BG traffic class due

to running out of channelizatin codes in DL and power in DL/UL



Iur resources setup fails during user plane allocation/modification of PS NRT RAB over IUR branch

M1002C553

Traffic

REJ_DCH_DUE_CODES_INT_DL

M1002C554

Traffic

REJ_DCH_DUE_CODES_BGR_DL

M1002C555

Traffic

REJ_DCH_DUE_POWER_INT_DL

M1002C556

Traffic

REJ_DCH_DUE_POWER_BGR_DL

M1002C557

Traffic

REJ_DCH_REC_DUE_CODES_INT_DL

M1002C558

Traffic

REJ_DCH_REC_DUE_CODES_BGR_DL

M1002C559

Traffic

REJ_DCH_REC_DUE_PWR_INT_DL

M1002C560

Traffic

REJ_DCH_REC_DUE_PWR_BGR_DL

M1002C626

Traffic

REJ_DCH_DUE_POWER_INT_UL

M1002C627

Traffic

REJ_DCH_DUE_POWER_BGR_UL

M1002C628

Traffic

REJ_DCH_REC_DUE_PWR_INT_UL

M1002C629

Traffic

REJ_DCH_REC_DUE_PWR_BGR_UL

0.00 10.00 20.00 30.00 40.00 50.00 60.00 70.00 80.00 90.00 100.00 1 11 21 31 41 51 61 71 81 91 101 111 121 131 141 151 161 m a x , a v e o c c u p a n c y & b lo c k in g ( % ) 0.00 50.00 100.00 150.00 200.00 250.00 300.00

Reconfig

reject due to

lack of codes

M1004C165 FAIL_NRT_DCH_SETUP_IUR

NRT DCH SETUP FAIL DUE TO IUR

M1004C166

FAIL_NRT_DCH_UL_RECON F_IUR

NRT DCH UL RECONFIG FAIL FOR NRT RB DUE TO IUR FAIL_NRT_DCH_DL_RECON NRT DCH DL RECONFIG FAIL

(61)

Low Packet/session success rate (SSSR)

Service -> RSRAN073

Rel99 Packet session setup failures Analysis (M1022)

Evaluate Dominant failures:

AC failure : lack of DL power or high UL

interference, UL admission control

parameter setting

Other failure: This could be due to max

HSPA users limit reached or “radio link

failure” during setup

BTS failure: lack of HW CE capacity

DMCU failure: DMCU/DSP faulty or lack of

DSP resources in RNC

TRANS failure: lack of Iub capacity

UE failure: UE internal problem (not

capability issue)

Cannot differentiate

Rel99 DCH , HSDPA,

HSUPA setup failure





_DCH_BGR

PS_ATT_DCH

M1022C8

+

_DCH_INT

PS_ATT_DCH

M1022C7

D_ALLO_BGR

D_D_REQ_D_

M1022C32

+

D_ALLO_INT

D_D_REQ_D_

M1022C31

100

(62)

Low Packet/session success rate (SSSR)

M1022 Rel99 Packet session setup failures Analysis



In RU10, new counters to identify the Rel99 NRT DCH setup and successful setup based on

initial request bit rates or DCH upgrade bit rates



Uplink initial request and success include also HSDPA UL return channel



This is useful to identify each of the bit rate setup performance and its distribution as well as

capacity bottleneck

M1022C83 Packet_call INIT_DCH_REQ_64_UL M1022C84 Packet_call INIT_DCH_REQ_64_DL M1022C85 Packet_call INIT_DCH_REQ_128_UL M1022C86 Packet_call INIT_DCH_REQ_128_DL M1022C87 Packet_call INIT_DCH_REQ_256_UL M1022C88 Packet_call INIT_DCH_REQ_256_DL M1022C89 Packet_call INIT_DCH_REQ_384_UL M1022C90 Packet_call INIT_DCH_REQ_384_DL M1022C91 Packet_call DCH_UPGR_REQ_64_UL M1022C92 Packet_call DCH_UPGR_REQ_64_DL M1022C93 Packet_call DCH_UPGR_REQ_128_UL M1022C94 Packet_call DCH_UPGR_REQ_128_DL M1022C95 Packet_call DCH_UPGR_REQ_256_UL M1022C96 Packet_call DCH_UPGR_REQ_256_DL M1022C97 Packet_call DCH_UPGR_REQ_384_UL M1022C98 Packet_call DCH_UPGR_REQ_384_DL M1022C99 Packet_call SUCC_INIT_ALLO_64_UL M1022C100 Packet_call SUCC_INIT_ALLO_64_DL M1022C101 Packet_call SUCC_INIT_ALLO_128_UL M1022C102 Packet_call SUCC_INIT_ALLO_128_DL M1022C103 Packet_call SUCC_INIT_ALLO_256_UL M1022C104 Packet_call SUCC_INIT_ALLO_256_DL M1022C105 Packet_call SUCC_INIT_ALLO_384_UL M1022C106 Packet_call SUCC_INIT_ALLO_384_DL M1022C107 Packet_call SUCC_INIT_ALLO_REQ_64_UL M1022C108 Packet_call SUCC_INIT_ALLO_REQ_64_DL M1022C109 Packet_call SUCC_INIT_ALLO_REQ_128_UL M1022C110 Packet_call SUCC_INIT_ALLO_REQ_128_DL M1022C111 Packet_call SUCC_INIT_ALLO_REQ_256_UL M1022C112 Packet_call SUCC_INIT_ALLO_REQ_256_DL M1022C113 Packet_call SUCC_INIT_ALLO_REQ_384_UL M1022C114 Packet_call SUCC_INIT_ALLO_REQ_384_DL M1022C115 Packet_call SUCC_UPG_NRT_DCH_64_UL M1022C116 Packet_call SUCC_UPG_NRT_DCH_64_DL M1022C117 Packet_call SUCC_UPG_NRT_DCH_128_UL M1022C118 Packet_call SUCC_UPG_NRT_DCH_128_DL M1022C119 Packet_call SUCC_UPG_NRT_DCH_256_UL M1022C120 Packet_call SUCC_UPG_NRT_DCH_256_DL M1022C121 Packet_call SUCC_UPG_NRT_DCH_384_UL M1022C122 Packet_call SUCC_UPG_NRT_DCH_384_DL M1022C123 Packet_call SUCC_UPG_NRT_DCH_REQ_64_UL M1022C124 Packet_call SUCC_UPG_NRT_DCH_REQ_64_DL M1022C125 Packet_call SUCC_UPG_NRT_DCH_REQ_128_UL M1022C126 Packet_call SUCC_UPG_NRT_DCH_REQ_128_DL M1022C127 Packet_call SUCC_UPG_NRT_DCH_REQ_256_UL M1022C128 Packet_call SUCC_UPG_NRT_DCH_REQ_256_DL M1022C129 Packet_call SUCC_UPG_NRT_DCH_REQ_384_UL M1022C130 Packet_call SUCC_UPG_NRT_DCH_REQ_384_DL

(63)

Low Packet/session success rate (SSSR)



In RU10, new counters also to identify the Rel99 NRT DCH

Reconfiguration failure during initial request (DCH0/0 to

DCH x/x kbps or cell Fach to DCH) and bit rate upgrade

request



Also HSDPA uplink allocations update these counters

M1022C139 FAIL_REC_INTERA_DCH_UL_AC

DCH UPLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE

M1022C140 FAIL_REC_BGR_DCH_UL_AC

DCH UPLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND

M1022C141 FAIL_REC_INTERA_DCH_DL_AC

DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR INTERACTIVE

M1022C142 FAIL_REC_BGR_DCH_DL_AC

DCH DOWNLINK RECONFIG FAIL DUE TO AC FOR BACKGROUND

M1022C135 FAIL_REC_INTERA_DCH_UL_BTS

DCH UPLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE

M1022C136 FAIL_REC_BGR_DCH_UL_BTS

DCH UPLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND

M1022C137 FAIL_REC_INTERA_DCH_DL_BTS

DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR INTERACTIVE

M1022C138 FAIL_REC_BGR_DCH_DL_BTS

DCH DOWNLINK RECONFIG FAIL DUE TO BTS FOR BACKGROUND

M1022 Rel99 Packet session setup failures Analysis

M1022C131 FAIL_REC_INTERA_DCH_UL_TRANS

DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR INTERACTIVE

M1022C132 FAIL_REC_BGR_DCH_UL_TRANS

DCH UPLINK RECONFIG FAIL DUE TO TRANSPORT FOR BACKGROUND

M1022C133 FAIL_REC_INTERA_DCH_DL_TRANS

DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR INTERACTIVE

M1022C134 FAIL_REC_BGR_DCH_DL_TRANS

DCH DOWNLINK RECONFIG FAIL DUE TO TRANSPORT FOR BACKGROUND

M1022C143 FAIL_REC_INTERA_DCH_UL_OTH

DCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR INTERACTIVE

M1022C144 FAIL_REC_BGR_DCH_UL_OTH

DCH UPLINK RECONFIG FAIL DUE TO OTHER REASONS FOR BACKGROUND

M1022C145 FAIL_REC_INTERA_DCH_DL_OTH

DCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS FOR INTERACTIVE

M1022C146 FAIL_REC_BGR_DCH_DL_OTH

DCH DOWNLINK RECONFIG FAIL DUE TO OTHER REASONS FOR BACKGROUND

0.00 200.00 400.00 600.00 800.00 1 000.00 1 200.00 1 400.00 1 600.00 1 800.00 2 000.00 1 10 19 28 37 46 55 64 73 82 91 100 109 118 FAIL_REC_BGR_DCH_DL_TRAN S FAIL_REC_INTERA_DCH_DL_TR ANS FAIL_REC_INTERA_DCH_DL_BT S FAIL_REC_BGR_DCH_DL_BTS FAIL_REC_INTERA_DCH_DL_AC FAIL_REC_BGR_DCH_DL_AC FAIL_REC_INTERA_DCH_DL_OT H FAIL_REC_BGR_DCH_DL_OTH

In DL, Failures mainly from

AC (Interactive and