Target KPI

No System Category Activity Main Results

Improvement
1 2G Strategy amrConfHrCodecModeSet MOS, TCH Drop Subs with bad MOS experience reduced 8.50%, TCH Drop improved 3.49%
2 2G Strategy Idle Mode Parameterisation SD Block, TCH Drop SD Blocking improved 2.25%, TCH Drop improved 0.20%
3 2G Strategy Dedicated Mode Parameterisation TCH Block, TCH Drop TCH Blocking improved 0.05%, TCH Drop improved 0.15%
4 2G Strategy SDCCH Re-dimensioning TCH Block, TCH Drop TCH Blocking improved 0.03%, TCH Drop improved 0.05%
5 2G Strategy ISH0 2G – 3G ISHO SR ISHO SR improved 3%
RNC PAT1: ISHO SR improve :3.89%
6 3G Strategy ISHO Parameterisation 3G – 2G ISH0 SR
RNC PAT2 :ISHO SR improve :3.63%
HSDPA HSDPA Payload Improved : 6%
7 3G Strategy Disbling CTS due to SIR Error
Payload/Throughput HSDPA Throughput Improved :6.9%
HSDPA Throughput increased : 4.7%
8 3G Strategy HSPDSCHCodeSet HSDPA Throughput
HSDPA Payload increased : 10.8%
Average RTWP reduced : 3dB (-90dBm to -93dBm)
CSSR CS Improved : 0.2%
9 3G Strategy SIR Target Reduction HSDPA UL Return Channel RTWP/Retainability
CSSR PS Improved : 0.5%
HSDPA Retainability Improved : 0.2%
10 3G Strategy RACH Parameter Standardisation RTWP Average RTWP Improved : 17.7%
HSDPA/HSUPA Accessibility : 0.7% / 7.5%
11 3G Strategy WAC Parameterisation HSPA HSDPA/HSUPA Retainability : 0.3% / 0.35%
HSDPA/HSUPA Throughput : 0.7% / 16.5%
RRC Conn Stp SR Improved : 0.1%
12 3G Strategy Ptx Parameter Standardisation Accessibility CSSR CS Improved : 0.25%
CSSR PS Improved : 0.11%
13 3G Strategy Flexible RLC UL HSUPA Payload HSUPA Payload Increased : 2.4%
HSUPA Accessibility/Retainability Improved : 2.4% / 0.17%
HSUPA
14 3G Strategy Frequency Domain Equalizer HSUPA Payload/Throughput Increase : 8.8% / 6.5%
Performance/RTWP
RTWP Improved : Reduced 0.7dB
15 4G Strategy Enable Fast Uplink Link Adaptation Throughput UL throughput Improved 8.86% (from 1693.54 to 1843.59)

16 4G Implementation QoS Setting in Radio IP (Ipaso) Throughput Max DL Throughput is achieved

Fact Finding: MML RANGE:
0: disabled
• High number of subscriber with bad MOS experience (MOS < 3) 1: 4.75 kbit/s
Action Taken: 2: 5.15 kbit/s
4: 5.90 kbit/s
• Rollout at all Truebex sitelist in Bima and Mataram City was done on 14-Apr-2016
8: 6.70 kbit/s
16: 7.40 kbit/s
Pro : Parameter Setting :
• To reduce subscriber with bad MOS experience OLD Setting NEW Setting
Cons : amrConfHrCodecModeSet=21 amrConfHrCodecModeSet=20

• - amrConfHrStartMode=0 amrConfHrStartMode=1
amrConfHrDlThreshold2=28 amrConfHrDlThreshold2=0
Execution Selection Criteria : amrConfHrUlThreshold2=28 amrConfHrUlThreshold2=0
• - amrConfHrHysteresis2=2 amrConfHrHysteresis2=0

Background :
• More than 50% number of cells in Bima and Mataram have impacted subscriber with
Result Summary (Data comparison 8-10 Apr and 15-17 Apr 2016)
bad MOS experience more than 100 subs per cell • Number of subs with bad MOS experience improve 8.50%
• And more than 80% of that cells have amrSegLoadDepTchRateLower setting more • TCH Drop improved 3.49%
than 90

Analysis:
amrSegLoadDepTchRateLower: With this parameter you define the percentage of full rate
TCH resources that must be available for traffic channel allocation in order to use full rate
for AMR calls in the cell. AMR full rate TCHs are allocated until the number of free full rate
resources is reduced below the threshold given in the parameter. AMR half rate resources
are then allocated.
amrConfHrCodecModeSet: With this parameter you define the codec mode set for a half
rate channel. If the parameter is defined as disabled, then the whole codec mode set is
disabled. If the parameter is defined as disabled, then other AMR HR set related
parameters (thresholds, hystereses, ICMI and start mode) are set as 0
Fact Finding: Parameter Setting :
 Idle Mode parameterisation Propose Setting
Parameter
Action Taken: cellReselectParamInd DCS=1, GSM=0

• Rollout at all Truebex in Denpasar 30 Apr 15 cs3Cs4Enabled 1

egprsEnabled 1

gprsEnabled 1
Pro :
• Improvement in SD Blocking and drop call
Result Summary
Cons : • SD Blocking improved 2.25%
• SDSR improved 2%
• TCH Blocking increased • TCH Drop Call improved 0.20%
• TCH Blocking increased 0.20%
Execution Selection Criteria :
• -
Background :
High congestion and drop call

Analysis:
Found some cells in truebex area still haven’t use recommended value for idle
parameter
Fact Finding: Parameter Setting :
 Dedicated mode parameterisation Parameter Propose Setting
diversityUsed 1
Action Taken: drInUse 1
• Rollout at all Truebex in Denpasar 30 Apr 15 dtxMode 1
qSearchI 7
qSearchP 7
Pro : enableUmbrellaHo 1
• Improvement in TCH Block and TCH drop
Cons : Result Summary
• - • TCH Block improved 0.05%
• TCH Drop improved 0.15%
Execution Selection Criteria : • TBF DL ESR improved 2.5%
• -
Background :
High congestion and drop call

Analysis:
Found some cells in truebex area still haven’t use recommended value for idle
parameter. Current setting will trigger high congestion and drop call. After changing
dedicated parameter to recommended value, we can see TCH congestion reduce
and TCH drop improve
Fact Finding: Parameter Setting :
 Capacity balancing between TCH, SD and PDCH Re-dimension SDCCH to TCH, from channelType 3 to channelType 2
Action Taken:
• Rollout at all Truebex in Denpasar 5 May 15
Result Summary
Pro : TCH Blocking improved 0.03%
• Improvement in TCH Blocking and TCH drop Rate TCH Drop improved 0.05%
Cons : TBF Completion improved 0.1%
• -
Execution Selection Criteria :
• SD Utilisation <50%, SD Block = 0%, TCH Utilisation >50%
• After reduce SD Channel, SD Utilisation still < 70%

Background :
In Truebex area, we found some cells have many SD timeslot with low SD utilization
(less than 50%) This condition will make unbalance capacity between TCH, SD and
PDCH which will lead high congestion on voice and data

Analysis:
There are around 13.7% of all cells inside truebex cluster can be changed (re-
dimensioning) to TCH if fulfill this condition (if SD utilization less than 50% with 0 SD
Block and TCH utilization more than 50%)

After SDCCH re-dimensioning done, we can see TCH blocking reduce, TBF completion
and TCH drop rate slightly improve
Fact Finding: Parameter Setting :
 ISHO 2G to 3G improvement Parameter Value
Action Taken: minEcnoThreshold 24
• Rollout at all Truebex in Denpasar 10 June 15

Pro :
• Improvement in ISHO SR Result Summary
• ISHO SR improved 3%
Cons :
• -
Execution Selection Criteria
Cell with high HO blocking percentage to target WCDMA cell

Background :
ISHO 2G to 3G ~86% for truebex area.

Analysis:
Mostly low inter system HO reason from 2G to 3G due to high congestion on target
cells
Fact Finding: Parameter Setting :
• ISHO Success Rate below 90% for PUMA

Action Taken:
• Execution 1-Apr in mcRNCPATI1 & RNCPAT2
• Rollout PUMA Apr16

Pro :
• Improved is ISHO SR

Cons :

Execution Selection Criteria :

• Identify Inner and border cells for implementation with different value

Result Summary (weekly comparison before and after implementation)

Background: • RNC PAT1: ISHO SR improve :3.89%
Implementation of 3G for traffic retention strategy leads to reduced ISHO attempts with • RNC PAT2 :ISHO SR improve :3.63%
compressed mode measurement triggering at lower level EcNo level -14dB or RSCP -
105dBm levels. This leads to ISHO attempts remaining at cell edge and poor radio
environment.

Analysis:
ISHO failure trace returns with UE ISHO fail message Physical channel configuration
failure. A set of refined parameter was proposed to increase the averaging window for
compressed mode triggering to prevent false triggering due to fading, target cell selection
of 2G target cells with good RxLevel and increasing the GSM measurement interval
measurement timer to prevent UEs which experienced ISHO failure from re-attempting
inter-RAT measurements before timer expires.
Fact Finding: Parameter Setting :
• Improvement for HSDPA payload required in Jayapura

Action Taken:
• Execution 14-Jul-15 in RJAP1 & RJAP2

Pro :
• Improved is State Transition SR HS-DSCH to DCH Result Summary (Before: 8-9Jul after 15-16Jul)
• Maintain data traffic in HSPA • HSDPA Payload Improved : 6%
• HSDPA Accessibility Improved :1%
Cons : • HSUPA Accessibility Improved :2.3%
• HSDPA Throughput Improved :6.9%
• HSUPA Throughput Improved : 3.9%
Execution Selection Criteria : • HS-DSCH _DCH Switch Success Rate :6.6%
• All RNC

Background:
During poor UL SIR error conditions HSDPA calls which have only one cell in active set or
where are switched from HSDPA to DCH. Also HSDPA calls in soft handover might be
switched to DCH if other active set cell's are not suitable HSDPA serving cell candidates

Analysis:
Channel type switches due to UL SIRerror occur frequently triggering HSDPA to DCH.
Parameter change prevents channel type switch to DCH due UL SIRerror measurement
without preventing the possibility to use UL SIRerror measurement to trigger HSDPA
serving cell change, thus maintaining service in HSDPA.
Fact Finding: Parameter Setting :
• Throughput Improvement in Ambon

Action Taken:
• Execution 23-Sep-15 in mcRNCPATI1 Result Summary (Before: 22Sep / After 25Sep 15)
•HSDPA Payload increased : 10.8%
•HSUPA Payload increased : 7.2%
Pro : •HSDPA Throughput increased : 4.7%
• Increase HSDPA duration allocation for 13 codes •HSUPA Throughput increased : 3%
• Increase HSDPA Throughput

Cons :
• Increase in code blocking for sites with existing code blocking issue.

Execution Selection Criteria :

• All cells with no code blocking issue.

Background:
Existing setting for HSDPA code allocation is 5, 8 , 10, 12, 14 & 15 codes for HSDPA. Where
the code upgrade requires 2 available codes before upgrade is possible.

Analysis:
Majority of the HSDPA code duration is within 12 & 14 codes. With 12 codes duration
occupying up to 70%. New setting will enable all code allocation from 5-15 codes, where
it required only 1 code available for code upgrade, thus increasing the capability for
higher throughput.
Fact Finding: Parameter Setting :
• High Average RTWP values reaching -90dBm

Action Taken:
• Execution 13-Jan-15 in RJAP1, RJAP2, RNCAMB2, RNCAMB3, RTIM1, RMWR1

Pro :
• Reduction in RTWP which will lead to better retainability.

Cons :
• Too low SIR target values will lead to longer time to reach actual SIR target during Result Summary (Before: 8-12 Jan/ After 15-19Jan15)
closed loop power control, leading to higher BLER. • Average RTWP reduced : 3dB (-90dBm to -93dBm)
• CCSR CS Improved : 0.2%
• CCSR PS Improved : 0.5%
Execution Selection Criteria : • HSDPA Retainability Improved : 0.2%
• All WCELs

Background:
Excessive UL load increase during the first few seconds of the call due to slow OLPC
convergence with high SIR target values.

Analysis:
Excessive UL load increase during OLPC contributed to higher RTWP. Target is to reduce
Uplink SIR target for HSDPA Uplink return channel reduction by 3dB to reduce overall
uplink load contributed by HSDPA uplink return channel.
Fact Finding: Parameter Setting :
• Standardise and clear RACH parameter inconsistency to reduced RTWP

Action Taken:
• Execution 19-Jan-15 in RJAP1, RJAP2, RNCAMB2, RNCAMB3, RTIM1, RMWR1

Pro :
• Reduction in RTWP

Cons :
Result Summary (Before: 15-18Jan/After 22-25Jul15)
• Average RTWP reduced : 2dB (-93.8dBm to -95.8dBm) Improved 17.7%

Execution Selection Criteria :

• RU40 cells

Background:

Analysis:
Found many Inconsistent RACH parameter in all RNCs. Improper RACH parameter setting
would lead to pre-ambles not reaching the Node B, thus causing repeat in preamble
cycles, introducing load into the network. Inconsistency parameters were corrected to the
RU40 recommended parameter values. The new recommended values reduced the
PRACH required CI with the increased in pre-amble ramp-up step size, allowing faster
acquisition of with less preambles.
Fact Finding: Parameter Setting : Result Summary
• WAC parameter optimization to improve HSPA performance (Before: 12-14 Jan/After 16-18Jan15)
• HSDPA Accessibility Improved : 0.7%
Action Taken: • HSUPA Accessibility Improved : 7.5%
• HSDPA Retainability Improved : 0.3%
• Execution 15-Jan-15 in RJAP1, RJAP2, RNCAMB2, RNCAMB3, RTIM1, RMWR1 • HSUPA Retainability Improved : 0.35%
• HSDPA Throughput Improved : 0.7%
• HSUPA Throughput Improved : 16.5%
Pro :
• Improvement is HSDPA and HSUPA Performance

Cons :

Execution Selection Criteria :

• All WCELs

Background:

Analysis:
Parameter standardization with optimized value in the WAC table to improve the resource
utlisation in DCH.
• Faster Release of E-DCH NRT MAC-d flow due to low throughput faster to FACH to save
HSUPA CE resources and allow better utilization of EDCH for UE with buffer in queue.
• Reduction the initial bit rate to control to save CE resources and uplink load
• Faster Release of DCH resource due to inactivity
• Faster Release of MACd due to low utilisation to save HSDPA scheduler resources
• Decreases amount of uplink capacity requests by increasing the time for UE to send
the traffic volume measurements with are having the same traffic volume event
identify
• Shifting of Low RLC UL buffer Ues of 256 bytes or below to FACH to relieve congestion
in the DCH state. i.e keep alive messages and etc.
Fact Finding: Parameter Setting :
• Ptx Parameter standardisation

Action Taken:
• Execution 27-Jan-15 in RJAP1, RJAP2, RNCAMB2, RNCAMB3, RTIM1, RMWR1

Pro :
• Improvement in Accessibility RRC, CCSR CS and CSSR PS
Result Summary
Cons : (Before: 25-26 Jan/After 27-28Jan15)
• RRC Conn Stp SR Improved : 0.1%
• CSSR CS Improved : 0.25%
Execution Selection Criteria : • CSSR PS Improved : 0.11%
• All WCELs

Background:
There inconsistent Ptx Parameter setting in the network for WCEL in relation with Cell
power.

Analysis:
Standadisation of ptx parameters for CS, R99 and HSDPA with a consistent values in
relation of the WCEL power capability. The standardised Ptx parameters provided a
proper power allocation and DL admission control to the CS, R99 and HSDPA services.
Fact Finding:
• Flexible RLC Activation

Action Taken:
• Execution 1-Jun-15 in RJAP1, RJAP2, RNCAMB2, RNCAMB3, RTIM1, RMWR1

Pro :
• Improvement in HSUPA Payload

Cons :

Execution Selection Criteria : Parameter Setting :

• All WCELs

Background:
This feature allows the use of variable RLC PDU sizes up to 1505 bytes for the WCDMA
uplink (UL), which reduces the overhead in the RLC layer in the uplink; this, in turn,
enables higher HSUPA peak rates
Result Summary
(Before: 26-29 May 15 /After 2-5 Jun 15)
• HSUPA Payload Increased : 2.4%
Analysis:
Feature RAN1910: Flexible RLC in UL enables higher bit rates for single end users,
increases overall data throughput in the network and reduces the Layer 2 overhead and
padding in combination with the optimum transport block size for different radio
conditions
Fact Finding: Parameter Setting :
• Frequency Domain Equalizer Activation
Activation thought BTS manager Commissioning. Tick the “check box’ for Frequency Domain
Equalizer in use.
Action Taken:
• Execution 14-16 AP-15 in RJAP1, RJAP2, RNCAMB2, RNCAMB3, RTIM1, RMWR1

Pro :
• Improvement in HSUPA Performance

Cons :

Execution Selection Criteria :

• All Node B
Result Summary
(Before: 10-12Apr 15 /After 17-19 Apr 15)
• HSUPA Accessibility Improved : 2.4%
Background: • HSUPA Retainability Improved : 0.17%
• HSUPA Payload Increase : 8.8%
Frequency Domain Equalizer captures the energy from all multipaths and performs • HSUPA Throughput Increased : 6.5%
reliably in all channel conditions with up to twice the 16QAM data rate compared to the • RTWP Improved : Reduced 0.7dB
rake receiver

Analysis:
Frequency Domain Equalizer removes inter-symbol interference arising from the user's
own signal because of multipath propagation. The rake receiver is unable to receive high
data rates even in the absence of other cell interference, since the short spreading codes
with high HSUPA data rates are vulnerable to inter-symbol interference. FDE removes
the inter-symbol interference, which are generated by the user itself, thus the UL user
bit rate is limited only by the interference from other users (of the same cell and
surrounding cells)
Fact Finding:
• Need to increase UL throughput in Bali Parameter Setting :
OLD Setting NEW Setting
Action Taken:
actUlLnkAdp = 5 (E-ULA) actUlLnkAdp = 6 (F-ULA)
• Rollout all eNodeB in Bali

Pro : Result Summary

• Improve average UL cell throughput • Overall main KPI performance are maintained
Cons : • there is improvement trend in average UL throughput ~ 8.86%

Before After
Execution Selection Criteria : KPI 1-4 April 16 8-11 April 16 Delta Status
Cell Uplink Average Throughput 1693.54 1843.59 8.86% improve

Background :
• Network cannot adjust the transmission settings fast enough to offer the best user
experience to end users
• Fast UL link adaption(F-ULA) introduces a new uplink link adaptation algorithm based on
available Extended Uplink Link Adaptation (E-ULA), which provides fast upgrade and fast
downgrade of the modulation and coding scheme (MCS) selection

+8.86%
Fact Finding:
• Low Throughput in Good Radio Condition based on field Test Parameter Setting :
Action Taken:
• Setting QoS in Radio IP MW side (CIR/EIR/EBS/CBS)

Pro :
• Improve maximum cell throughput
Cons :
Result Summary
Execution Selection Criteria : • Overall main KPI performance are maintained
• Transport using MW and setting end to end.
• Improvement in Throughput experience test on field and trend increment Payload
Background : more obvious
• User experience hard to get maximum DL Throughput even in good radio condition and
usually get bigger UL Throughput than DL Throughput near site.
Payload
• Site with Radio IP MW(NEC Ipaso) mostly got this experience
45

40

35

30
Setting QoS
25

GB
20

15

10

3/17/2016

4/3/2016
3/1/2016
3/3/2016
3/5/2016
3/7/2016
3/9/2016
3/11/2016
3/13/2016
3/15/2016

3/19/2016
3/21/2016
3/24/2016
3/26/2016
3/28/2016
4/1/2016

4/5/2016
4/7/2016
4/9/2016
4/11/2016
4/13/2016
4/15/2016
4/17/2016
4/19/2016
DL Payload UL Payload Sum of Total Payload

Before After Payload WAENPERMAI