3G AOP 2012 Performance Acceptance Methodology DraftV1-2

WCDMA RADIO NETWORKS
ANNUAL OPERATION PROGRAM (AOP) 2012
WCDMA RADIO NETWORK

3G ANNUAL OPERATION PROGRAM

PERFORMANCE ACCEPTANCE METHODOLOGY
(Version 1)
On Behalf of Indosat,
On Behalf of NSN,
HERI PURNOMO
DH Network Quality Planning
GILBERTHUS NAPITU
NPO Senior Manager
1 of 36

Table of Contents
Table 1 KPI Lock Values 6..............................................................4

Table 2 KPI Best Value 6...................................................................4
Table 3 KPI Target 7..........................................................................4
Table 4 Newsite OSS KPI Target 7....................................................4
Table 5 Newsite DT KPI Target 8.......................................................4
Table 6 Modernization OSS KPI Target 9..........................................4
Table 7 Modernization DT KPI Target 9.............................................4
Table 8 Decongestion KPI Target 10.................................................4
Table 9 Rehoming, Reparenting, Lac Split KPI Target 11..................4
Table 10 Final and Acceptance Report 29.........................................4
Table 11 Appendix table 35................................................................4
Table 12 Document History 35...........................................................5
Figure 1 Newsite and 2nd Carrier Process Flow 31..........................5
Figure 2 UMTS 900 Process Flow 32................................................5
Figure 3 Modernization Process Flow 33..........................................5
Figure 4 Decongestion, Rehoming, Reparenting, Lac Split Process Flow 34.5
1. Introduction.....................................................................................6
2. Scope6
2.1 Scope of Service........................................................................................................................ 6
2.2 Scope of Work............................................................................................................................ 6
3. Schedule.........................................................................................6
2 of 36

4. Performance...................................................................................7
4.1 Key Performance Indicator......................................................................................................... 7
4.2 Lock Value.................................................................................................................................. 7
4.3 Best Value.................................................................................................................................. 7
4.4 KPI Target................................................................................................................................... 8
4.5 Newsite, New 2nd Carrier, and UMTS 900 KPI Method.............................................................8
4.5.1 OSS KPI................................................................................................................................. 8
4.5.2 Drive Test KPI......................................................................................................................... 9
4.6 Modernization KPI Method.........................................................................................................9
4.6.1 OSS KPI............................................................................................................................... 10
4.6.2 Drive Test KPI....................................................................................................................... 10
4.7 Decongestion............................................................................................................................ 11
4.8 Rehoming, Reparenting, And Lac-Split Method........................................................................11
4.9 Frequency Scanning Method....................................................................................................12
5. OSS KPI Methodology And Formula............................................13

5.1 OSS KPI Methodology.............................................................................................................. 13
5.2 OSS KPI Formula..................................................................................................................... 14
5.2.1 Call Setup Success Rate CS................................................................................................14
5.2.2 Call Setup Success Rate PS................................................................................................14
5.2.3 Soft Handover...................................................................................................................... 15
5.2.4 Call Drop Rate CS................................................................................................................ 15
5.2.5 Call Drop Rate PS................................................................................................................ 16
6. DT KPI Methodology And Formula...............................................16

6.1 DT KPI Methodology................................................................................................................ 16
6.2 Description of events for Drivetest KPIs...................................................................................17
6.2.1 Call Setup Success Rate for Voice.......................................................................................17
6.2.2 Call Setup Success Rate for Video.......................................................................................18
6.2.3 Call Setup Success Rate for R99 Data.................................................................................19
6.2.4 Call Setup Success Rate for HSDPA....................................................................................20
6.2.5 Call Drop Rate for Voice.......................................................................................................22
6.2.6 Call Drop Rate for Video.......................................................................................................22
6.2.7 Call Drop Rate for R99 Data.................................................................................................23
6.2.8 Call Drop Rate for HSDPA....................................................................................................24
6.2.9 Soft Handover Success Rate...............................................................................................25
6.2.10 Inter System Handover Success Rate................................................................................26
7. Successfullness............................................................................28
8. Acceptance...................................................................................29
8.1 Newsite, New 2nd Carrier, and UMTS 900...............................................................................29
8.2 Modernization........................................................................................................................... 29
8.3 Decongestion, Rehoming, Reparenting, And Lac-Split.............................................................29
9. Reporting And Delivery.................................................................30

9.1 OSS Reporting......................................................................................................................... 30
9.2 Parameter Change Request.....................................................................................................30
9.3 Documentation Reporting.........................................................................................................30
9.4 Final And Acceptance Report...................................................................................................30
3 of 36

10. Tools...........................................................................................30
11. Parameter Setting.......................................................................31
12. Process Flow..............................................................................32
12.1 Newsite And New 2nd Carrier.................................................................................................32
12.2 UMTS 900.............................................................................................................................. 33
12.3 Modernization......................................................................................................................... 34
12.4 Decongestion, Rehoming, Reparenting, And Lac Split...........................................................35
13. Appendix.....................................................................................35
14. Document History.......................................................................36
List of Tables
Table 1 KPI Lock Values..................................................................7

Table 2 KPI Best Value.......................................................................7
Table 3 KPI Target..............................................................................8
Table 4 Newsite OSS KPI Target........................................................8
Table 5 Newsite DT KPI Target...........................................................9
Table 6 Modernization OSS KPI Target............................................10
Table 7 Modernization DT KPI Target...............................................10
Table 8 Decongestion KPI Target......................................................11
Table 9 Rehoming, Reparenting, Lac Split KPI Target......................12
Table 10 Final and Acceptance Report.............................................30
Table 11 Appendix table....................................................................36
Table 12 Document History...............................................................36
4 of 36

List of Figures
Figure 1 Newsite and 2nd Carrier Process Flow..............................32

Figure 2 UMTS 900 Process Flow....................................................33
Figure 3 Modernization Process Flow..............................................34
Figure 4 Decongestion, Rehoming, Reparenting, Lac Split Process Flow.....35
1.
Introduction
5 of 36

This document serves to describe NSNs Radio Access Network (RAN) Acceptance
Methodology of Annual Operational Program (AOP). This agreement will be mandated
effective to sites under AOP 2012 Contract.
2.
Scope
2.1
Scope of Service
This project covers following services:
Newsite
New 2nd Carrier
UMTS 900
Modernization
Decongestion
Frequency Scanning
Rehoming
Reparenting
LAC Split
2.2
Scope of Work
The services are aimed to ensure performance of the delivered site has met the target
defined.
3.
Schedule
AOP 2012 project will be delivered in two phase:
Phase 1 will start on July 2012.
Phase 2 will start on November 2012.
Each phase consist of one or more services.
The schedule may be changed due project condition.
6 of 36

4.
Performance
4.1
Key Performance Indicator

Key Performance Indicator (KPI) is the performance to be measured to indicate
successfulness of the project. There are two methods may be used to observe the
network performance; OSS KPI and Drive Test KPI. There are two methods for OSS
KPI; OSS Blended KPI and OSS Busy Day Busy Hour (BDBH) KPI.
4.2
Lock Value
KPI Lock value is OSS Blended KPI value thresholds where the equipment must be
locked to avoid very low performance occur in the network and could raise complaints
from customers.
The minimum KPI (Lock value) is as desribed below:
Minimum KPI
(Locked Value)
>= 88.00%
<= 6.00%
OSS KPI
Call Setup Success Rate (CSSR)
Drop Call Rate (DCR)
Table 1 KPI Lock Values
4.3
Best Value
KPI target of some services are maintain, which means KPI Target is equal to baseline.
Best value shall be considered as KPI Target, if baseline is better than best value.
OSS KPI
Best Value
CSSR_CS
99.50%
CSSR_PS
99.50%
SHO_RT_NRT
99.50%
CDR_CS
0.30%
CDR_PS
0.30%
Table 2 KPI Best Value
7 of 36

4.4
KPI Target
Following are KPI Target and Performance Deliverable for each service:
KPI
Service
Target
OSS
DT
Newsite
Basic KPI
Yes
Yes
New 2nd Carrier
Basic KPI
Yes
Yes
UMTS 900
Basic KPI
Yes
Yes
Modernization
Maintain
Yes
Yes
Decongestion
Maintain
Yes
No
Rehoming
Maintain
Yes
No
Reparenting
Maintain
Yes
No
Lac Split
Maintain
Yes
No
Table 3 KPI Target
4.5
Newsite, New 2nd Carrier, and UMTS 900 KPI Method

Newsite and New Collocated Service performance is observed using OSS KPI and
DT KPI with total 23 KPIs (10 OSS + 13 DT).
KPI Achievement is the performance of the site which is measured after Hotnews.
For UMTS 900, frequency scanning in Buffer and Core Zone shall be done after
implementation, in order to make sure there is no frequency interfence from GSM
Network.
KPI Target is Basic KPI.
KPI Target shall be achieved within 4 weeks
4.5.1
OSS KPI
OSS Basic KPI and weighting:
KPI Type
OSS
Blended
(10%)
OSS BDBH
(40%)
KPI
Weight
Target KPI
CSSR_CS
20%
>= 95%
CSSR_PS
20%
>= 95%
SHO_RT_NRT
20%
>= 95%
CDR_CS
20%
<= 2%
CDR_PS
20%
<= 2%
CSSR_CS
20%
>= 95%
CSSR_PS
20%
>= 95%
SHO_RT_NRT
20%
>= 95%
CDR_CS
20%
<= 2%
CDR_PS
20%
<= 2%
Table 4 Newsite OSS KPI Target
8 of 36

KPI is calculated in site level.
4.5.2
Drive Test KPI

KPI
Weight
Target
KPI
CSSR Voice
7.50%
>= 95%
CSSR Video
5.00%
>= 95%
CSSR R99
7.50%
>= 95%
CSSR HSDPA
7.50%
>= 95%
CDR Voice
7.50%
<= 2%
CDR Video
5.00%
<= 2%
KPI Type
DT (50%)
CDR R99
7.50%
<= 2%
CDR HSDPA
7.50%
<= 2%
SHO_RT_NRT
8.00%
>= 95%
ISHO_RT_NRT *
2.00%
>= 95%
CQI
10.00%
>= 18.00
Ec/No >= -10dB

12.50%
>= 90%
CPICH RSCP >= -95 dBm on agreed
route
12.50%
>= 90%
HOSR Inter System Handover : In 3G border area & No measurement for 2nd carrier
Table 5 Newsite DT KPI Target
DT is performed based on Site level
4.6
Modernization KPI Method

Modernization Service performance is observed using OSS Blended KPI and DT
KPI with total 18 KPIs (5 OSS Blended+ 13 DT)
KPI Target is maintain (baseline).
Baseline is the performance of the site which is measured a week before the
execution week.
For Cluster Level, baseline is the performance of the cluster which is measured a
week before implementation of the first site.
In case baseline is better than best value then best value shall be considered as KPI
Target.
KPI Target value must be agreed by Indosat.
KPI Achievement is the performance of the cluster which is measured after the
Hotnews of the last site.
KPI Target shall be achieved within 4 weeks.
9 of 36

4.6.1
OSS KPI
KPI Type
OSS
Blended
(50%)
KPI
Weight
Target KPI
CSSR_CS
20%
>= baseline
CSSR_PS
20%
>= baseline
SHO_RT_NRT
20%
>= baseline
CDR_CS
20%
<= baseline
CDR_PS
20%
<= baseline
Table 6 Modernization OSS KPI Target
KPI will be measured based on cluster and Site-cell level.

For sites which are adjacent, will be defined into a cluster by including existing sites.
Cluster is defined before project start and must comply Indosat approval.
Changes in clusters may apply and must be approved by Indosat.
Cluster is applicable for performance measurement based on OSS and Drive Test.
Sites without adjacent will be measured as site-cell level which means, if the KPI of
cell level does not fulfill the target, site level measured KPI will be proposed.
4.6.2
Drive Test KPI

KPI Type
DT (50%)
KPI
Weight
Target KPI
CSSR Voice
7.50%
>= baseline
CSSR Video
5.00%
>= baseline
CSSR R99
7.50%
>= baseline
CSSR HSDPA
7.50%
>= baseline
CDR Voice
7.50%
<= baseline
CDR Video
5.00%
<= baseline
CDR R99
7.50%
<= baseline
CDR HSDPA
7.50%
<= baseline
SHO_RT_NRT
8.00%
>= baseline
ISHO_RT_NRT *
2.00%
>= baseline
CQI
10.00%
>= baseline
Ec/No >= -10dB

CPICH RSCP >= -95 dBm on agreed
route
12.50%
>= baseline
12.50%
>= baseline
Table 7 Modernization DT KPI Target
10 of 36

DT is performed based on Site level.
4.7
Decongestion
Decongestion Service performance is observed using OSS Blended KPI with total 5
KPIs.
execution week.
Target.
KPI Type
OSS
Blended
KPI
Target KPI
CSSR_CS
>= baseline
CSSR_PS
>= baseline
SHO_RT_NRT
>= baseline
CDR_CS
<= baseline
CDR_PS
<= baseline
Table 8 Decongestion KPI Target
4.8
Rehoming, Reparenting, And Lac-Split Method

11 of 36

Rehoming, Reparenting, and Lac-Split Services performance is observed using

OSS Blended KPI with total 5 KPIs.
Functionality Test shall be performed, to ensure all service is working as before.
Functionality Test is performed in sample sites in cluster.
execution week.
Target.
KPI Type
OSS
Blended
KPI
Target KPI
CSSR_CS
>= baseline
CSSR_PS
>= baseline
SHO_RT_NRT
>= baseline
CDR_CS
<= baseline
CDR_PS
<= baseline
Table 9 Rehoming, Reparenting, Lac Split KPI Target
4.9
Frequency Scanning Method

Frequency Scanning is performed after Refarming implementation to ensure the
frequency band to be used for UMTS 900 is clean from GSM transmission.
There is no KPI Acceptance for Frequency Scanning Service. However, Nokia Siemens
Networks must submit performance report which is observed using DT Frequency
Scanning.
12 of 36

Frequency Scanning is performed on cluster level.

Frequency Scanning is performed using specified method and formula which is
detail on chapter Measurement.
Frequency Scanning result is the maximum RX Level on each ARFCN.
ARFCN will be stated as CLEAN when the RX level is under -105 dBm.
The Route to be used is the same as used in the Refarming Service.
The report shall consist of the following info:
Status of each ARFCN.
The chart of the Frequency Scanning result.
The scanning Route.
Comment and Suggestions if available and required.
5.
OSS KPI Methodology And Formula
5.1
OSS KPI Methodology

The time frame KPI achievement is within 4 weeks after HOTNEWS of last site
within cluster or the HOTNEWS of the site for the island sites.
For OSS Blended KPI, performance is measured by accumulating used counters of
1 week data (7x24 hours) from Monday to Sunday.
For OSS BDBH KPI of cell level, performance is measured by collecting counters in
the busiest hour of each cells in 1 week data (7x24 hours) from Monday to Sunday.
While for OSS BDBH KPI Network Level, performance is measured by accumulating
used counters of OSS BDBH KPI of cell level.
Achievement week may shift due to abnormal or invalid data in the week caused by
measurement collection problem, an event take place in the coverage area or a
running project take place on the cluster.
Specific for BDBH KPI, the busy day and the busy hour may shift to the next busy
day or busy hour due to abnormal or invalid data.
For lebaran,natal, and new year festive, achievement week is shifted two weeks
before and two weeks after.
d The number of samples required for OSS KPI calculation shall consists of
minimum of 500 samples per site per week. If this minimum sample is not met, the
KPI involved still could be considered, NSN will provide justification if needed.
13 of 36

5.2
OSS KPI Formula
5.2.1
Call Setup Success Rate CS
CSSR_CS
Unit
Formula
100* sum(MOC_CONV_CALL_ATTS - MOC_CONV_CALL_FAILS + MTC_CONV_CALL_ATTS MTC_CONV_CALL_FAILS + EMERGENCY_CALL_ATTS - EMERGENCY_CALL_FAILS RRC_ACC_REL_EMERGENCY - RRC_ACC_REL_MO_CONV - RRC_ACC_REL_MT_CONV)
/ sum(MOC_CONV_CALL_ATTS + MTC_CONV_CALL_ATTS + EMERGENCY_CALL_ATTS RRC_ATT_REP_MO_CONV - RRC_ATT_REP_MT_CONV - RRC_ATT_REP_EMERGENCY RRC_ACC_REL_EMERGENCY - RRC_ACC_REL_MO_CONV - RRC_ACC_REL_MT_CONV RRC_CONN_STP_REJ_EMERG_CALL)
* sum(RAB_ACC_COMP_CS_VOICE+RAB_ACC_COMP_CS_CONV)
/ sum(RAB_STP_ATT_CS_VOICE+RAB_STP_ATT_CS_CONV)
Notes
5.2.2
Refers to rnc_565f and rnc_566e
Call Setup Success Rate PS
14 of 36

CSSR_PS
Unit
Formula
100 * sum(MOC_INTER_CALL_ATTS - MOC_INTER_CALL_FAILS + MOC_BACKG_CALL_ATTS

MOC_BACKG_CALL_FAILS + MTC_INTER_CALL_ATTS - MTC_INTER_CALL_FAILS +
MTC_BACKG_CALL_ATTS - MTC_BACKG_CALL_FAILS + MOC_HIGH_PRIOR_SIGN_ATTS MOC_HIGH_PRIOR_SIGN_FAILS + MTC_HIGH_PRIOR_SIGN_ATTS MTC_HIGH_PRIOR_SIGN_FAILS - RRC_ACC_REL_INTERACTIVE RRC_ACC_REL_MO_BACKGROUND - RRC_ACC_REL_MO_HIGH_PR_SIGN RRC_ACC_REL_MO_INTERACTIVE - RRC_ACC_REL_MT_BACKGROUND RRC_ACC_REL_MT_HIGH_PR_SIGN)
/ sum(MOC_INTER_CALL_ATTS + MOC_BACKG_CALL_ATTS +
MOC_HIGH_PRIOR_SIGN_ATTS + MTC_INTER_CALL_ATTS + MTC_BACKG_CALL_ATTS +
MTC_HIGH_PRIOR_SIGN_ATTS - RRC_ATT_REP_INTERACTIVE RRC_ATT_REP_MO_INTERACTIVE - RRC_ATT_REP_MO_HIGH_PR_SIGN RRC_ATT_REP_MO_BACKGROUND - RRC_ATT_REP_MT_BACKGROUND RRC_ATT_REP_MT_HIGH_PR_SIGN - RRC_ACC_REL_INTERACTIVE RRC_ACC_REL_MO_BACKGROUND - RRC_ACC_REL_MO_HIGH_PR_SIGN RRC_ACC_REL_MO_INTERACTIVE - RRC_ACC_REL_MT_BACKGROUND RRC_ACC_REL_MT_HIGH_PR_SIGN)
* sum(RAB_ACC_COMP_PS_INTER+RAB_ACC_COMP_PS_BACKG)
/sum(RAB_STP_ATT_PS_INTER+RAB_STP_ATT_PS_BACKG)
Notes
5.2.3
Refers to rnc_576e
Soft Handover
SHO_RT_NRT
Unit
Formula
%
100* sum(SUCC_UPDATES_ON_SHO_FOR_RT +SUCC_UPDATES_ON_SHO_FOR_NRT)
/sum(CELL_ADD_REQ_ON_SHO_FOR_RT +CELL_DEL_REQ_ON_SHO_FOR_RT
+CELL_REPL_REQ_ON_SHO_FOR_RT +CELL_ADD_REQ_ON_SHO_FOR_NRT
+CELL_DEL_REQ_ON_SHO_FOR_NRT +CELL_REPL_REQ_ON_SHO_FOR_NRT)
Notes
Refers to rnc_195a
5.2.4
Call Drop Rate CS
15 of 36

CDR_CS
Unit
Formula
Notes
5.2.5
%
100*sum(RAB_ACT_REL_CS_VOICE_P_EMP + RAB_ACT_FAIL_CS_VOICE_IU +
RAB_ACT_FAIL_CS_VOICE_RADIO + RAB_ACT_FAIL_CS_VOICE_BTS +
RAB_ACT_FAIL_CS_VOICE_IUR + RAB_ACT_FAIL_CS_VOICE_RNC +
RAB_ACT_FAIL_CS_VOICE_UE + RAB_ACT_FAIL_CS_VOICE_TRANS+
RAB_ACT_FAIL_CS_CONV_IU + RAB_ACT_FAIL_CS_CONV_RADIO +
RAB_ACT_FAIL_CS_CONV_BTS + RAB_ACT_FAIL_CS_CONV_RNC +
RAB_ACT_FAIL_CS_CONV_IUR + RAB_ACT_FAIL_CS_CONV_UE +
RAB_ACT_REL_CS_CONV_P_EMP + RAB_ACT_FAIL_CS_CONV_TRANS)
/ sum(RAB_ACT_COMP_CS_VOICE + RAB_ACT_REL_CS_VOICE_SRNC +
RAB_ACT_REL_CS_VOICE_P_EMP +RAB_ACT_REL_CS_VOICE_HHO +
RAB_ACT_REL_CS_VOICE_ISHO + RAB_ACT_REL_CS_VOICE_GANHO +
RAB_ACT_FAIL_CS_VOICE_IU + RAB_ACT_FAIL_CS_VOICE_RADIO +
RAB_ACT_FAIL_CS_VOICE_BTS +RAB_ACT_FAIL_CS_VOICE_IUR +
RAB_ACT_FAIL_CS_VOICE_RNC +RAB_ACT_FAIL_CS_VOICE_UE +
RAB_ACT_FAIL_CS_VOICE_TRANS+ RAB_ACT_COMP_CS_CONV +
RAB_ACT_REL_CS_CONV_SRNC + RAB_ACT_REL_CS_CONV_HHO +
RAB_ACT_REL_CS_CONV_ISHO + RAB_ACT_REL_CS_CONV_P_EMP +
RAB_ACT_FAIL_CS_CONV_IU + RAB_ACT_FAIL_CS_CONV_RADIO +
RAB_ACT_FAIL_CS_CONV_BTS + RAB_ACT_FAIL_CS_CONV_RNC +
RAB_ACT_FAIL_CS_CONV_IUR + RAB_ACT_FAIL_CS_CONV_UE +
RAB_ACT_FAIL_CS_CONV_TRANS)
Refes to rnc_231d and rnc_232e
Call Drop Rate PS
CDR_PS
Unit
Formula
Notes
%
100* sum(PS_REL_RL_FAIL_HS_E_INT +PS_REL_RL_FAIL_HS_E_BGR
+PS_REL_RL_FAIL_HS_D_INT +PS_REL_RL_FAIL_HS_D_BGR +PS_REL_RL_FAIL_D_D_INT
+PS_REL_RL_FAIL_D_D_BGR +PS_REL_OTH_FAIL_HS_E_INT
+PS_REL_OTH_FAIL_HS_E_BGR +PS_REL_OTH_FAIL_HS_D_INT
+PS_REL_OTH_FAIL_HS_D_BGR +PS_REL_OTH_FAIL_D_D_INT
+PS_REL_OTH_FAIL_D_D_BGR +PS_REL_RL_FAIL_HS_E_STRE
+PS_REL_RL_FAIL_HS_D_STRE +PS_REL_RL_FAIL_D_D_STRE
+PS_REL_OTH_FAIL_HS_E_STRE +PS_REL_OTH_FAIL_HS_D_STRE
+PS_REL_OTH_FAIL_D_D_STRE)
/sum(PS_REL_RL_FAIL_HS_E_INT +PS_REL_RL_FAIL_HS_E_BGR
+PS_REL_RL_FAIL_HS_D_INT +PS_REL_RL_FAIL_HS_D_BGR +PS_REL_RL_FAIL_D_D_INT
+PS_REL_RL_FAIL_D_D_BGR +PS_REL_OTH_FAIL_HS_E_INT
+PS_REL_OTH_FAIL_HS_E_BGR +PS_REL_OTH_FAIL_HS_D_INT
+PS_REL_OTH_FAIL_HS_D_BGR +PS_REL_OTH_FAIL_D_D_INT
+PS_REL_OTH_FAIL_D_D_BGR +PS_REL_NORM_HS_E_INT +PS_REL_NORM_HS_E_BGR
+PS_REL_NORM_HS_D_INT +PS_REL_NORM_HS_D_BGR +PS_REL_NORM_D_D_INT
+PS_REL_NORM_D_D_BGR +PS_REL_RL_FAIL_HS_E_STRE +PS_REL_RL_FAIL_HS_D_STRE
+PS_REL_RL_FAIL_D_D_STRE +PS_REL_OTH_FAIL_HS_E_STRE
+PS_REL_OTH_FAIL_HS_D_STRE +PS_REL_OTH_FAIL_D_D_STRE
+PS_REL_NORM_HS_E_STRE +PS_REL_NORM_HS_D_STRE +PS_REL_NORM_D_D_STRE)
Refes to rnc_922b
6.
DT KPI Methodology And Formula
6.1
DT KPI Methodology
16 of 36

Performance is measured by performing Drive Test using specified method and

formula.
Drive Test tools equipment, software version and enabled features shall be the
same before and after execution.
Drive Test to be conducted after site HOTNEWS and must be achieved within 4
weeks.
For lebaran,natal, and new year festive, baseline and achievement week is shifted
two weeks before and two weeks after.
NSN and Indosat have agreed to use NEMO as tools for drive test measurement.
Drivetest route shall be agreed by both Indosat & NSN.
2nd Carrier Drive Test is locked to UARFCN of 2nd carrier.
Calculation of the successfulness will take into account from the total sample under
agreed drivetest route.
NSN shall deliver the raw data (log file) of NEMO result.
The drive test in connected mode for voice is defined as 60 seconds connected and
10 second idle.
Time for measurement is from 08.00 am to 08.00 pm during working days (Monday
to Friday).
The suggested car to be used will be MPV or SUV type only, boat and motor cycle
drive test may applicable for specified area.
The vehicle speed for drivetest activity is ranges 50 km to 70 km per hour.
Number of minimum sample for voice is 20 attempts, while for PS call is 10
attempts.
If the number of sample did not meet the requirement on the speed of defined above
(main drivetest), extension drivetest should be taken to fulfilled number of sample
required. The extension drivetest route is the way back of the defined route. Only
one time extension drivetest allowed and the extention drivetest must cover the
whole way back route. There is no speed limitation on the extention drivetest. The
main drivetest and the extension drivetest is a continues call.
For sites situated in the 3G Area Border, drivetest shoud be continued until the
value of RSCP <= -102 dbm AND EcNO <= -14 dbm has been fulfilled.
Voice Call termintating number is the MSC test number
PS Downloading using FTP server.
6.2
Description of events for Drivetest KPIs
6.2.1
Call Setup Success Rate for Voice

17 of 36

Voice Call Setup Success Rate

Definition
Ratio between successfully established CS voice calls compared to the overall number of
voice call establishment attempts. The successful establishment of a voice call on the UE
side is defined by the successful reception of the layer 3 CC ALERTING message at the
UE. The voice call establishment attempt is the submission of the RRC CONNECTION
REQUEST message with the establishment cause Originating Conversational Call by the
UE. This assumes the UE initiates a call to PSTN (MOC).
Methodology
of measuring
This measurement can be either 3G to PSTN or 3G to 3G measurements

1 UE (or 2 UE) with FMT (Nemo) Mobile measurements
Set FMT to generate a voice call to the test number automatically (to a PLMN within
same country) ( or to other UE )
Start drive test and continue driving until drive route is completed and enough samples
are collected. (re-drive route until there is enough samples)
Verify the call setup time by recording the interval between RRC CONNECTION
REQUEST and L3 Alert at the UE side
Formula
Notes
6.2.2
CSSRVoice =
number _ of ( ALERTING )
*100%
number _ of ( RRC _ CONNECTION _ REQUEST )
Mobility measurement
UE locket to 3G
Call Setup Success Rate for Video
18 of 36

Video Call Setup Success Rate

Definition
Ratio between successfully established CS video calls compared to the overall number of
video call establishment attempts. The successful establishment of a video call on the UE
side is defined by the successful reception of the layer 3 CC ALERTING message at the
UE. The video call establishment attempt is the submission of the RRC CONNECTION
REQUEST message with the establishment cause Originating Conversational Call by the
UE. This assumes the UE initiates a call to PSTN (MOC).
Methodology
of measuring
This measurement can be either 3G to PSTN or 3G to 3G measurements

1 UE (or 2 UE) with FMT (Nemo) Mobile measurements
Set FMT to generate a video call to the test number automatically (to a PLMN within
same country) ( or to other UE )
Verify the call setup time by recording the interval between RRC CONNECTION
REQUEST and L3 Alert at the UE side
Formula
Notes
6.2.3
CSSRVideo =
number _of (ALERTING)

number _of (RRC_CONNECTION_REQUEST)
UE locket to 3G
* 100%
Call Setup Success Rate for R99 Data
19 of 36

R99 Call Setup Success Rate

Definition
R99 Call Success Rate is the ratio between successful PS PDP CONTEXT
ACTIVATION procedures compared to the number of PDP CONTEXT ACTIVATION
attempts. The successful establishment of a PDP context on the UE side is defined
by the successful reception of the ACTIVATE PDP CONTEXT ACCEPT message at
the UE. The corresponding attempt is the submission of the RRC CONNECTION
REQUEST message by the UE.
Methodology of
measuring
1 PS UE with FMT
Set FMT to generate data call to the data server automatically.
Start drive test and continue driving until drive route is completed and enough
samples are collected. (re-drive route until there is enough samples)
Verify the PS PDP Context Activation Success Rate by recording the number of
Activate PDP Context Accept messages and the number of corresponding
attempts on the UE side (RRC Connection Request)
Formula
R99CSSR = number _of (ACTIVATE_PDP_CONTEXT_ACCEPT) * 100%

Notes
Mobility Measurement
UE locked to 3G
6.2.4
Call Setup Success Rate for HSDPA
20 of 36

HSDPA Call Setup Success Rate

Definition
Methodology of
measuring
HSDPA Call Success Rate is the ratio between successful PS PDP CONTEXT
ACTIVATION procedures compared to the number of PDP CONTEXT ACTIVATION
attempts. The successful establishment of a PDP context on the UE side is defined
by the successful reception of the ACTIVATE PDP CONTEXT ACCEPT message at
the UE. The corresponding attempt is the submission of the RRC CONNECTION
REQUEST message by the UE.
1 PS UE with FMT
Start drive test and continue driving until drive route is completed and enough
samples are collected. (re-drive route until there is enough samples)
Verify the PS PDP Context Activation Success Rate by recording the number of
Activate PDP Context Accept messages and the number of corresponding
attempts on the UE side (RRC Connection Request)
Formula
HSDPACSSR = number _of (ACTIVATE_PDP_CONTEXT_ACCEPT) * 100%

Notes
UE locked to 3G
21 of 36

6.2.5
Call Drop Rate for Voice
Drop Call Rate, Voice

Definition
Ratio between abnormally released voice calls and the overall number of established
voice calls. For the purpose of end-to-end measurements, an abnormal release of a CS
call is defined as any call termination at the UE side which has not been triggered by the
mobile user at the UE side or its corresponding peer party.
The successful establishment of a CS call on the UE side is defined by submitting the
CC ALERTING message by the UE. The call drop is given if the call is not regularly
released by the UE itself after a certain holding time. A regular release is given if the UE
terminates the call by submitting a CC DISCONNECT message.
Methodology
of measuring
1 UE with FMT (Nemo) or 2 UE with FMT (Nemo)

same country) (or to other UE)
Formula
Notes
CDRVoice =
number _ of ( ALERTING DISCONNECT )

*100%
number _ of ( ALERTING )
Mobility Measurements
UE locked to 3G
6.2.6
Call Drop Rate for Video

22 of 36

Drop Call Rate, Video

Definition
Ratio between abnormally released video calls and the overall number of established
video calls. For the purpose of end-to-end measurements, an abnormal release of a CS
call is defined as any call termination at the UE side which has not been triggered by the
mobile user at the UE side or its corresponding peer party.
The successful establishment of a CS call on the UE side is defined by submitting the
CC ALERTING message by the UE. The call drop is given if the call is not regularly
released by the UE itself after a certain holding time. A regular release is given if the UE
terminates the call by submitting a CC DISCONNECT message.
Methodology
of measuring
1 UE with FMT (Nemo) or 2 UE with FMT (Nemo)

same country) (or to other UE)
Formula
CDRVideo = number _of (ALERTING - DISCONNECT) * 100%

number _of (ALERTING)
Notes
Mobility Measurements
UE locked to 3G
6.2.7
Call Drop Rate for R99 Data
23 of 36

R99 Drop Call Rate

R99 Drop Call Rate is calculated from R99 Call Success Rate with formula (1
Definition
R99 Call Success Rate) and R99 Call Success Rate is calculated as a ratio of
successful R99 sessions compared to overall number of established R99 sessions.
Abnormally released R99 session is any call termination at the UE side which has
not been triggered by the mobile user at the UE side or its corresponding peer
party.
Methodology
of
measuring
1 PS UE with FMT
Assumptions Reasons for a Abnormal session release caused by the UMTS network include:
and pre Abnormal release of a RAB by the UTRAN (without RAB re-establishment before the
conditions
PS session abnormally terminates)
De-activation of the PDP context by the core network
Stop of the data transfer by the UMTS network
Violation of requested Quality of Service for the PDP context (e.g. Significant packet
loss, high delay)
Formula
R99CDR = number _of (Success_Session Abnormal_Session_Release) * 100%

number _of (Success_Session)
Notes
UE locked to 3G
6.2.8
Call Drop Rate for HSDPA

24 of 36

HSDPA Drop Call Rate

HSDPA Drop Call Rate is calculated from HSDPA Call Success Rate with formula
Definition
(1 HSDPA Call Success Rate) and HSDPA Call Success Rate is calculated as a
ratio of successful HSDPA sessions compared to overall number of established
HSDPA sessions. Abnormally released HSDPA session is any call termination at
the UE side which has not been triggered by the mobile user at the UE side or its
corresponding peer party.
Methodology
of
measuring
1 PS UE with FMT
Assumptions Reasons for a Abnormal session release caused by the UMTS network include:
and pre Abnormal release of a RAB by the UTRAN (without RAB re-establishment before the
conditions
PS session abnormally terminates)
De-activation of the PDP context by the core network
Stop of the data transfer by the UMTS network
Violation of requested Quality of Service for the PDP context (e.g. Significant packet
loss, high delay)
Formula
HSDPACDR = number _of (Success_Session Abnormal_Session_Release) * 100%

number _of (Success_Session)
Notes
UE locked to 3G
6.2.9
Soft Handover Success Rate

25 of 36

SHO Success Rate

Definition
The Successful Soft Handover is defined as the ratio of successful Active set
updates and Active set update attempts
Methodology of
measuring
1 UE with FMT
Start drive test and continue driving until drive route is completed and
enough samples are collected. (re-drive route until there is enough
samples)
Formula
Notes
6.2.10
SHOSuccess =
number _ of ( Successfull _ SHO)

* 100%
number _ of ( SHO_ attempts)
UE locked to 3G
Inter System Handover Success Rate
26 of 36

ISHO Success Rate, 3G2G (In 3G Border area)

Definition
Methodology of
measuring
The successful CS UMTS to GSM Inter-System Handover procedure on the

UE side is defined as the ratio between number of GSM layer 3 HANDOVER
COMPLETE messages from the 2G MSC being received at the UE and the
number of RRC HANDOVER FROM UTRAN messages according to being
received from the UE.
1 dual mode UE with FMT (Nemo)
Set FMT to generate a voice call to the test number automatically (to a
PLMN within same country)
Use long call to be able to trigger ISHO
Start drive test and continue driving until drive route is completed and
enough samples are collected. (re-drive route until there is enough
samples)
Assumptions and preconditions
The measurement assumes the presence of an existing GSM network.

Furthermore, it is assumed that events triggering the counters occur in an
area with sufficient coverage and good radio conditions in both UMTS and
GSM.
Procedure is conducted under combined 2G/3G MSC/MSC-S
Formula
number _ of (GSM _ L3 _ HANDOVER _ COMPLETE)

ISHOSR =
*100%
number _ of (HANDOVER _ FROM _ UTRAN )
Notes
UE in dual mode
27 of 36

7.
Successfullness
Performance in 3G AOP 2012 project shall meet the OSS and DT KPI targets within
the time frame as defined.
In case of some cell has very bad performance, NSN will deploy RF Optimization
Engineers and O&M Engineers on site to fix the cause of problem immediately.
For newsite service, in case of some cells performance is worst then Lock Value
(CSSR < 88% or DCR > 6%), the cell should be switched off and NSN should perform
troubleshooting on site immediately
Incase of KPI Target are not meet due to factors which is beyond NSN Control such
as HW faults due to external (third party) problem, Transmission and Core problem,
NSN shall submit an exclusion and Indosat is agreed to have it.
Incase of KPI Targets do not meet the time frame, NSN shall provide an explanation
and justification. When Indosat approved the submitted justification, the KPI is
considered to be acceptable.
Incase of KPI Targets do not meet due to some reasons where NSN has put all of
optimization efforts to improve the KPI, NSN should provide a justification which is
consist of detail problem explanation, action or effort taken history, detail KPI data and
recommendation for improvement. When Indosat approved the submitted justification,
the KPI achievement is considered to be acceptable.
28 of 36

8.
Acceptance
8.1
Newsite, New 2nd Carrier, and UMTS 900

A For each achieved KPI, will be granted a score according to the defined weighting.
Not achieved KPI will be granted score 0 (zero).
OSS KPI Blended is weighted 10%, OSS KPI BDBH is weighted 40% and DT KPI is
weighted 50%.
The Site shall be accepted if total score is equal or greater than 90.
NSN will prepare the acceptance documents required and propose the acceptance
meeting.
OSS KPI acceptance meeting will be held in Head quarter of Indosat and shall be
attended by Indosat and NSN representative.
Site Acceptance Certificate will be issued by Indosat to NSN for each accepted cluster
or Site.
8.2
Modernization
A For each achieved KPI, will be granted a score according to the defined weighting.
Not achieved KPI will be granted score 0 (zero).
OSS KPI Blended is weighted 50% and DT KPI is weighted 50%.
The Site shall be accepted if total score is equal or greater than 90.
meeting.
or Site.
8.3
Decongestion, Rehoming, Reparenting, And Lac-Split

The Site shall be accepted if All KPI Target is achieved.
meeting.
or Site.
29 of 36

9.
Reporting And Delivery
9.1
OSS Reporting
Statistic report is taken from OSS reports. OSS reports are forming technical reliable
and comprehensive representation of network performance and quality.
9.2
Parameter Change Request

It is assumed that all logical system configuration, operational parameter and OSS
performance reporting related changes for NSN Element are implemented by NSN
Team with the support from Indosat O&M organisation. NSN teams will use standard
Indosat change request and approval processes for initiating network changes.
9.3
Documentation Reporting
The following documents will be created by NSN and delivered to Indosat:
3G AOP 2012 Performance Acceptance Methodology.
9.4
Final And Acceptance Report

Nokia Siemens Networks shall submit the complete final report or acceptance report
based on the scope of service.
Service
Report
Newsite
New Site Acceptance Report
New 2nd Carrier
UMTS 900
Modernization
Modernization Acceptance Report
Frequency Scanning
Frequency Scanning Final Report
Decongestion
Decongestion Acceptance Report
Rehoming
Rehoming Acceptance Report
Reparenting
Reparenting Acceptance Report
LAC Split
LacSplit Acceptance Report

Table 10 Final and Acceptance Report
10.
Tools
NSN will provide the tools during project delivery. The recommended tool for Drivetest
(DT) is NEMO version 6.0 at minimum.
30 of 36

Indosat will provide the access to OSS server.
11.
Parameter Setting
In order to maintain the current level of satisfaction perceived by subscriber, the
following rule of modifying BSS parameter setting is to be followed by NSN:
Node-B Power shall be set at recommended value. Transmit power can be set lower
or higher subject to Indosat approval.
Any changes in antenna reorientation / tilting shall require approval from Indosat.
Any parameter changes that may impact to Indosat billing system (changing Cell ID,
RNC rehoming, etc) shall be informed in advance and closely coordinated with
Indosat.
Any RAN parameters change shall be performed by vendor.
Any critical or mass parameter changes such as Scrambling Code, LAC, RAC, shall
get approval from Indosat
Any non critical parameters change shall get acknowledgement from Indosat
Vendor shall responsible for RAN parameters consistency.
Vendor may use any available (purchased) features for maintaining the KPI prior
Indosat approval.
Any parameter changes shall be implemented by considering OSS KPI targets.
Any optimization activities shall not degrade performance of surounding (direct
neighbour) cells.
31 of 36

12.
Process Flow
12.1
Newsite And New 2nd Carrier

Site On-air
Lock / switch off the

cell(s)
Single Site Verification

(SSV) Submitted
Vendor put maximum

effort to fix the problem
HOTNEWS
D+0
Monitoring Quality for 3

hours
PLO Process for 1 week

(Monday to Sunday)
Basic KPI
Target
Achieved
?
No
Yes
KPI Acceptance Report

Submitted
No
Pass
Lock
Value?
No
Time
Frame >
4 week?
PASS
Yes
Yes
days
Justification Submitted
Quality Statement
submitted.
D+4
Yes
PASS
Justificati
on
Accepted
?
No
FAIL
Figure 1 Newsite and 2nd Carrier Process Flow
32 of 36

12.2
UMTS 900
Site On-air

(SSV) Submitted

(Monday to Sunday)
Frequency Scanning
Basic KPI
Target
Achieved
?

cell(s)
HOTNEWS
D+0
No
Yes
Vendor put maximum

hours

Submitted
No
Time
Frame >
4 week?
No
PASS
Pass
Lock
Value?
Yes
Yes
days
Yes
Quality Statement
submitted.
D+4
PASS
Justificati
on
Accepted
?
No
FAIL
Figure 2 UMTS 900 Process Flow
33 of 36

12.3
Modernization
Get Baseline for KPI
Target
Implemention

cell(s)

(SSV) Submitted
Vendor put maximum

HOTNEWS
D+0

hours
No

(Monday to Sunday)
KPI
Target
Achieved
?
No
Yes

Submitted
Pass
Lock
Value?
No
Time
Frame >
4 week?
PASS
Yes
Yes
days
Quality Statement
submitted.
D+4
Yes
PASS
Justificati
on
Accepted
?
No
FAIL
Figure 3 Modernization Process Flow
34 of 36

12.4
Decongestion, Rehoming, Reparenting, And Lac Split
Get Baseline for KPI

Target
(Monday to Sunday)
Implemention
KPI
Target
Achieved
?
HOTNEWS
D+0
Time
Frame >
4 week?
No
No
Yes
Yes

Submitted
PASS
Yes
Justificati
on
Accepted
?
PASS
No
FAIL
Figure 4 Decongestion, Rehoming, Reparenting, Lac Split Process Flow
13.
Appendix
35 of 36

Number
Description
File reference
Status
3G_2012_Newsite_KPI Report_Template_v1_2.zip
3G_2012_Modernization_KPI Report_Template_v1_2.zip
3G_2012_Decongestion_KPI Report_Template_v1_0.zip
Template Report
3G_2012_Rehoming_KPI Report_Template_v1_0.zip
3G_2012_Reparenting_KPI Report_Template_v1_0.zip
3G_2012_LacSplit_KPI Report_Template_v1_0.zip
Table 11 Appendix table
14.
Document History
Version
1
Date
18 Jul 12
Author by
BPU
Approved by
Gilberthus Napitu
Description of Change
Release Document
Table 12 Document History
36 of 36

3G AOP 2012 Performance Acceptance Methodology DraftV1-2

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

3G AOP 2012 Performance Acceptance Methodology DraftV1-2

Enviado por

Direitos autorais:

Formatos disponíveis

WCDMA RADIO NETWORKS

ANNUAL OPERATION PROGRAM (AOP) 2012

WCDMA RADIO NETWORK

3G ANNUAL OPERATION PROGRAM

WCDMA RADIO NETWORKS

Table 1 KPI Lock Values 6..............................................................4

WCDMA RADIO NETWORKS

5. OSS KPI Methodology And Formula............................................13

6. DT KPI Methodology And Formula...............................................16

9. Reporting And Delivery.................................................................30

WCDMA RADIO NETWORKS

Table 1 KPI Lock Values..................................................................7

WCDMA RADIO NETWORKS

Figure 1 Newsite and 2nd Carrier Process Flow..............................32

WCDMA RADIO NETWORKS

WCDMA RADIO NETWORKS

Key Performance Indicator

WCDMA RADIO NETWORKS

New 2nd Carrier

Table 3 KPI Target

Newsite, New 2nd Carrier, and UMTS 900 KPI Method

Table 4 Newsite OSS KPI Target

WCDMA RADIO NETWORKS

KPI is calculated in site level.

Drive Test KPI

Ec/No >= -10dB

DT is performed based on Site level

Modernization KPI Method

WCDMA RADIO NETWORKS

Table 6 Modernization OSS KPI Target

KPI will be measured based on cluster and Site-cell level.

Drive Test KPI

Ec/No >= -10dB

Table 7 Modernization DT KPI Target

WCDMA RADIO NETWORKS

DT is performed based on Site level.

Table 8 Decongestion KPI Target

Rehoming, Reparenting, And Lac-Split Method

WCDMA RADIO NETWORKS

Rehoming, Reparenting, and Lac-Split Services performance is observed using

Table 9 Rehoming, Reparenting, Lac Split KPI Target

Frequency Scanning Method

WCDMA RADIO NETWORKS

Frequency Scanning is performed on cluster level.

OSS KPI Methodology And Formula

OSS KPI Methodology

WCDMA RADIO NETWORKS

OSS KPI Formula

Call Setup Success Rate CS

Refers to rnc_565f and rnc_566e

Call Setup Success Rate PS

WCDMA RADIO NETWORKS

100 * sum(MOC_INTER_CALL_ATTS - MOC_INTER_CALL_FAILS + MOC_BACKG_CALL_ATTS

Call Drop Rate CS

WCDMA RADIO NETWORKS

Call Drop Rate PS

DT KPI Methodology And Formula

WCDMA RADIO NETWORKS

Performance is measured by performing Drive Test using specified method and

Description of events for Drivetest KPIs

Call Setup Success Rate for Voice

WCDMA RADIO NETWORKS

Voice Call Setup Success Rate

This measurement can be either 3G to PSTN or 3G to 3G measurements