By : Fajar Primadi A

Date : 6-Jan-2010

Agenda
INTRODUCTION
ACCESSIBILITY ANALYSIS
RETAINABILITY ANALYSIS
INTEGRITY ANALYSIS

INTRODUCTION
1. Accessibility

The ability of a user to obtain the requested service from the system.

2. Retainability

The ability of the user to retain the requested service once connected
for the desired duration.

3. Integrity

The ability of a user to receive the requested service at a desired quality.

HSDPA ACCESSIBILITY SUCCESS RATE (%)

RRC DROP RATE (%)

RAB ESTABLISH FAIL RATE CS(%)

RAB ESTABLISH FAIL RATE PS(%)

CCSR CS VOICE (%)

CCSR CS VIDEO (%)

CCSR PS (%)

HSDPA RETAINABILITY SUCCESS RATE (%)

RAB DROP RATE PS [%]

RAB DROP RATE CS [%]

ISHO RT SUCCESS RATE (%)

SHO SUCC RATE (%)

INTEGRITY

CSSR PS (%)

RETAINABILITY

CSSR CS VIDEO (%)

TARGET

ACCESSIBILITY

CSSR CS VOICE (%)

DETAIL KPI

KPI

98

98

98

98

99

99

99

99

1.5

1.5

95

95

Accessibility program
RAN Capacity utilization Analysis and monitoring

Audit Node B HW and License Capacity

Consistency check RBS and RNC parameter

Admission parameter adjustment

Periodic Evaluation

Accessibility Analysis

Transport and RNC Load Capacity utilization analysis

and monitoring

RAN Capacity utilization Analysis and

monitoring
OBJECTIVE
Monitor utilization of RAN capacity to prevent performances degradation due to
lack of resources.
Analyze capacity trend and network growing for upgrade proposal

Capacity monitored

CE UL and CE DL utilization
DL power utilization
DL code utilization
HS user utilization
Grace period of license monitoring.

Transport and RNC Load Capacity

utilization analysis and monitoring
OBJECTIVE
Monitor utilization of transport capacity to prevent performances degradation
due to lack of resources.
Analyze capacity trend and network growing for upgrade proposal

Capacity monitored

Iub (Node to RXI) Utilization

Iub (RXI to RNC) Utilization
Cid Utilization
IuCS Utilization
IuPS Utilization
Iur Utilization
RNC Mpload

Audit Node B HW and License Capacity

OBJECTIVE
Audit actual RBS configuration
Audit and consistency check RBS parameter
Monitor actual RBS HW capacity and license capacity

Capacity monitored

HW Capacity : RAXB, TXB, RU, E1

License Key Capacity
RBSLocalCell Parameter
NodeBFunction Parameter
RBS Product type
GraceTimePeriod
AAL2 Configuration
IMA Configuration
E1
IubDataStream
AntennaRef

RBS Parameter dump

OBJECTIVE
Utilize of available resources in RBS
Utilize of available license in RBS
Consistency of RBS parameter and RNC parameter

Capacity monitored

maxDlPowerCapability
maxNumHsPdschCodes
maxNumHsdpaUsers
supportOf16qam
maxHsRate
electricalUlDelay, ulAttenuation
electricalDlDelay, dlAttenuation

Admission parameter adjustment

OBJECTIVE
Optimize of available resources by admission parameter adjustment

Capacity monitored

dlCodeAdm
hsdpaUsersAdm
pwrAdm
sf16Adm
sf16AdmUl
sf4AdmUl
sf8Adm
sf8AdmUl
numHsPdschCodes
maximumTransmissionPower

Accessibility Study Case

Below is HSDPA accessibility success rate of PBR037W3

HSDPAAccSR
Degraded ?

Accessibility Study Case cont

Counter to be checked:

1. pmNoFailedRabEstAttemptExceedConnLimit
Number of failed PS RAB establishment attempts due to exceeding the configured
connection limit when allocating Spreading Factor

Parameter related: e.g sf16admUl, sf8admUl

2. pmNoFailedRabEstAttemptLackDlChnlCode

Number of failed RAB establishment attempts due to lack of DL channelization codes

Parameter related: dlCodeAdm
3. pmNoFailedRabEstAttemptLackDlPwr
Number of failed RAB establishment attempts due to lack of DL power. Counter is stepped
when admission control fails with reject reason lack of DL power
Parameter related: pwrAdm

Accessibility Study Case COnt

NCCR #279
Lack of DL Code
& DL Power

Action: Create NCCR for changing dlCodeAdm &

pwrAdm parameter

Retainability
For most of the drop causes related to RF conditions issues, the speech RAB is
considered as a reference, hence some counters for speech drop call causes
have been defined in order to spot possible radio conditions problems. Following
the RAB speech drop causes are described:

1. Drop speech due to soft handover actions

It is dropped Speech calls due to Soft Handover action, which are network initiated call releases due
to inability to include a non-valid or valid cell in the active set. This means that missing neighbour
drops due to releaseConnOffset exceeding are included. In general every cause that does not allow
executing a SHO is triggering the counter at numerator

Counter related : pmNoSysRelSpeechSoHo

2. Drop speech due to missing neighbor
It is dropped Speech call due to unknown measured cell (missing neighbor relation).

Counter related : pmNoSysRelSpeechNeighbr

Retainability
3. Drop speech due to UL Synchronization lost
It is dropped Speech call due to UL Synchronization Lost. It has to be noted that the counter at
numerator is only pegged as a UL synch drop if dchRcLostT (default 5s) expires.

Counter related : pmNoSysRelSpeechUlSynch

Retainability Study Case

Below is CCSR Voice for PAD012W1
Mostly below KPI
threshold (< 99%)?

Retainability Study Case cont

NCCR #346

High count in pmNoSysRelSpeechSoHo &

pmNoSysRelSpeechNeighbr

Action: check and add some missing neighbor

Integrity
Integrity consist of Soft Handover (SHO) and IRAT Handover
performance:

1. SHO SR:
100 * (1 - pmNoTimesCellFailAddToActSet / (pmNoTimesCellFailAddToActSet + pmNoTimesRlAddToActSet)

pmNoTimesCellFailAddToActSet
Number of times a cell fails to be added to an active set
pmNoTimesRlAddToActSet
Number of times an RL is added to an active set

Integrity
2. IRAT HO SR:
100 * (pmNoSuccessOutIratHoSpeech / (pmNoAttOutIratHoSpeech)
pmNoSuccessOutIratHoSpeech
Number of successful outgoing (to GSM) inter-RAT handover forConversational
speech RAB for the best cell in the active set

pmNoAttOutIratHoSpeech
Number of attempted outgoing (to GSM) inter-RAT handover for Conversational
speech RAB for the best cell in the active set.

integrity Study Case

Below is SHO performance of RNPAD02.
There was SHO degradation on 24 and 25 Nov 09

integrity Study Case cont cont

Check worst cell list:
Date/Time
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09
24-Nov-09

Region
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng
Sumbagteng

Cluster
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi
Bukittinggi

Utran_Cell
BKT091W2
BKT091W3
BKT091W1
BKT175W2
BKT024W2
BKT176W2
BKT176W3
BKT023W1
BKT023W2
BKT023W3
BKT024W1
BKT024W3
BKT175W1
BKT175W3
BKT176W1
BKT508W1
BKT508W2
BKT508W3
PAY250W1
PAY250W2

SHOSR
0
0.001894406
0.003619189
99.72899729
99.86168741
99.94463923
99.97441801
100
100
100
100
100
100
100
100
100
100
100
100
100

pmNoTimesCellFailAddToActSetpmNoTimesRlAddToActSet
28247
0
158358
3
55259
2
1
368
4
2888
3
5416
2
7816
0
6583
0
474
0
342
0
9975
0
5824
0
750
0
422
0
12350
0
8742
0
3301
0
5973
0
2
0
61

The worst cell are: BKT091WA, BKT091WB and BKT091WC

integrity Study Case cont cont

Check site status from RNC:
RNC
SITE ID CFRPHEM1 CFRPHEM2 CFRPHEM3 ICDS TN
RNPAD02 BKT091W
10001
10001
10001
1110 A

Check alarm in BKT091W:

Conclusion: SHO was degraded due to transmission problem