Prepared by:

Heba Ibrahim
Contents

1) Introduction
2) Main KPIs
3) SDCCH congestion
4) TCH congestion
5) CSSR
6) HOSR
7) CDR
8) Useful information
Introduction

Firstly, we must differentiate between 4 words:

Introduction

1) Counter:
It is the counters in the BSC that counts every
event in the layer 3 messages.

Such as : K3012B Call Drops in TCH Handovers (Traffic Channel),

(ET02) TCH CDR Per Cell & K3016:Configured TCHs

Introduction

2) KPI:

It is the combination of some counters in a

certain formula to help in judging the network

performance .
Such as: CDR, HOSR & TCH congestion
Introduction

3) Parameter:

It is the item in the BSC to be adjusted to have a

switch, threshold or an interval

Such as: CRO, Concentric circles HO allowed & UtoO traffic HO

allowed.
Introduction

4) Algorithm:

It is a group of commands controlling a certain

process.
Such as: HO algorithm, Power control algorithm & Direct retry

algorithm.
Main KPIs
To judge a network we have 5 main KPIs:

SDCCH
TCH congestion CSSR
congestion

HOSR CDR
SDCCH Congestion
SDCCH congestion

1) SDCCH congestion:

Total No. of SDCCH assignment failures(Due to congestion)

Total No. of SDCCH requests
SDCCH congestion

SDCCH congestion may be due to:

A) Capacity No. of required SDCCHs > Configured SDCCHS

B) Availability No. of Available SDCCHs Configured SDCCHS

SDCCH congestion

Incase of Capacity problem & TCH congestion=0 the solution will be:

Static SD: Traffic in BH > Available capacity

Expansion
(Static or Dynamic SDCCH)
Dynamic SD: Congestion is due to sudden
increase in SD requests

Sharing the load with neighboring cells

Load sharing using both CRO & PBGT parameters
SDCCH congestion

Incase of Capacity problem & TCH congestion0 the solution will be:

Enabling Dynamic SDCCH if TCH & SD

congestion are not in the same time
Expansion
Physical expansion is needed if TCH & SD
congestion are in the same time

Sharing the load with neighboring cells

Load sharing using both CRO & PBGT parameters
SDCCH congestion

Incase of availability :

Checking alarms on the cell

Checking alarms on neighboring cells

TCH Congestion
TCH congestion

No. of TCH assignment failures due to congestion

(Stable state + HO)

No. of TCH assignment requests(Stable state + HO)

TCH congestion

SDCCH congestion may be due to:

A) Capacity No. of required TCHs > Configured TCHS

B) Availability No. of Available TCHs Configured TCHS

TCH congestion

Incase of Capacity problem the solution will be:

Enabling HR
Expansion
Remove useless SDs & Packet TSs
(Static or Dynamic SDCCH)
Add new TRX

Idle mode: CRO & Direct Retry(DR)

Load sharing

Dedicated mode: Incoming & outgoing

PBGT HO & load HO
TCH congestion

Incase of availability :

Available
Configured Checking alarms on the cell

Available = With sudden increase in traffic then

Configured check alarms on neighboring cells
CSSR
CSSR

( 1-
Total No. of TCH assignment failures
Total No. of TCH assignment requests
)
(1 - Total No. of SDCCH requests )
Total No. of SDCCH failures

(1 - SDCCH call drop)

CSSR

For TCH assignment failure, it includes:

1) Radio problems

2) BSS problems

3) Congestion problems
CSSR

For SD drop rate, it is affected by:

1) Poor coverage

2) UL-DL imbalance

3) High Interference (Internal or External)

4) Cross connection

For SD congestion, it was discussed in the previous slides

HOSR
HOSR

Total No. of successful HOs

(Incoming + Outgoing + Intracell)

Total No. of HO requests

(Incoming + Outgoing + Intracell)
HOSR

HO purposes:

Mobility

Sustain calls

Save MS & BTS power

HOSR

We may classify HOs according to:

Network Architecture Synchronization Radio

Intra BSC: Synchronous Normal (Better cell/PBGT)

Intra-cell Asynchronous Emergency (BQ/Edge/TA/
Inter-cell Interference/Sudden level
Intra-site drop)
Inter-site Performance (Load/Layer/
Level/ Fast moving)
Concentric (UtoO/OtoU)
HOSR

For PBGT HO:

RxLevel RxLevel + Max of (PBGT HO threshold,
(neighbour) (serving) PBGT HO hystersis)
For BQ HO:
RxLevel RxLevel + PBGT HO BQ HO
(neighbour) (serving) threshold
-
threshold

For Interference HO:

RxLevel (serving) RxLevel threshold
Quality (serving) BQ threshold

Interference HO has lower priority than BQ HO because there is no

condition on the target cell level
HOSR

For Layer HO:

(4) Umbrella
(3) Macro
(2) Micro
(1) Pico

RxLevel Layer HO + Hystersis

(Higher priority) threshold

This level is the min. level required for the higher priority cell to trigger layer HO
There is no PBGT HO between 2 cells in different layers
Entering higher layer cell is by layer HO & exiting is by Edge HO
HOSR

For Edge HO:

If UL Edge HO RxLevel threshold OR
DL Edge HO RxLevel threshold is satisfied
For Load HO:
If Load HO threshold on source AND
Load HO threshold on target cells are satisfied

For TA HO:
TA (serving) TA HO threshold

It is the logical way to overcome overshooting

HOSR

For MS fast moving HO:

It is done by increasing the ranking of higher layer &
prevent HO to lower layer

For Sudden power drop HO:

It is done in the BSC by comparing values of successive
measurement reports.
It is disabled in Huawei network

For Level HO:

It is disabled in Huawei network
HOSR
HO Algorithm:
MR

MR preprocessing

Penalty application

Basic ranking (16-Bit)

HO decision
 1
TA HO HOSR
BQ HO

2
HO Priorities:
Sudden
RxLevel drop

3
HO

Interference

4
HO

5 Load HO

Edge HO
6

Layer/Level
7

HO

PBGT HO
8
9

Concentric HO

MS fast moving
10

HO
HOSR

To Analyze HOSR it is divided to:

Intra cell HO failures

Incoming HO failures

Outgoing HO failures
HOSR

Intracell HO failures may be

OtoU UtoO

Congestion on underlaid Congestion on overlaid

Underlaid Interference Faulty DCS TRXs or DDPUs
Alarms Path Imbalance
Faulty EGSM TRXs or DDPUs Alarms
Path Imbalance Wrong DCS electric tilt
HOSR

Incoming HO failures may be due to

Congestion BSS Radio

Failed TCH seizures due Alarms External Interference

to busy TCHs Failed Faulty TRXs or combiners Internal Interference
Incoming HO failures Path imbalance Configuration problem
HOSR

Outgoing HO failures may be due to

To one cell To all cells

Problem in the Revise counters

neighbour cell requests
HOSR
To analysze outgoing HO requests:

1) Quality requests >>> Level requests

External
UL Quality requests >>> DL Quality requests
Interference
Internal
DL Quality requests >>> UL Quality requests
Interference

2) Strenth requests >>> Remaining counters

Path Imbalance
UL Strenth requests >>> Remaining counters (UL limited)
Path Imbalance
DL Strenth requests >>> Remaining counters (DL limited) or
HW problem
HOSR

3) UL, DL quality & strenth requests >>> PBGT requests

Poor coverage area

Ideally, the majority of requests must be PBGT requests

CDR
CDR

Total No. of dropped calls (Stable state + HO)

No. of successful TCH assignments (Stable state + HO)

CDR

Call drops may be due to

Error indication Connection Failure Release Indication

Incase of bad radio Incase MS does not decode The MS send a

conditions if the BTS SACCH or the BTS does not disconnection message
does not receive the decode MR until RLT to the BTS
correct frame & T200 expires(=32 in DL & 24 in UL)
timer expired N200+1 the call drops
times the call drops
CDR

Call drop reasons:

1) Poor coverage
2) Interference
3) Missing neighbors
4) Outgoing HO failures
5) Congestion on underlaid
6) Overshooting
7) Path imbalance
8) Configuration problems
9) Alarms
Thank You