3G New Site and Multi-Sector

OSS KPI Status Summary

Breakdown KPI Not Passed NEW SITE

Breakdown KPI Not Passed

Multisector

Row Labels
SHO OH
ISHO
IFHO
ISHO, IFHO, SHO_OH
IFHO, ISHO
SHO
CSSR CS PS HS
SHO, ISHO, IFHO
CSSR CS PS HS / SHO
OH
CSSR PS HS
CCSR HS
CSSR
SHO_OH, IFHO
SHO,IFHO
Traffic
Payload
CSSR HS
ISHO,IFHO
Grand Total

Count of Site
Name
102
26
15
7
4
3
2
1
1
1
1
1
1
1
1
1
1
1
170

KPI Issues
SHO OH, IFHO,
ISHO
Other KPIs
Total

Sites

158

92.94%

12

7.06%
100.00
%

170

Row Labels
ISHOSR
CSSRPS
IFHOSR
SHOOH
CSSRCS
DTLock
Flicker
TDR
SDSR
TBFCSR
DLTBFESR
CSSR
CCSRCS
SHOSR
Needauditnewsite
CCSRPS
DownlinkQual
DownlinkQua
Needuptilsect1
CSSRHS
Permitnewsitenyreleas
ed
nbrBOJONGMW
Reject
Facing
Grand Total

Count of
KPIISSUE1
24
22
19
12
6
6
6
5
5
4
3
2
2
2
2
1
1
1
1
1
1
1
1
1
129

3G Multi-Sector
SHO Overhead Optimization
Guideline
1. SHO OH
>50%
2.TP > ISD >
10%
3. DT
coverage
Check
Overshooti
ng

Height >
35m

Propose antenna
lowering

N
N
Rule3

Azimuth
between
antenna
<=90

Re-azimuth > 90
difference

Rule1

Re-azimuth >=10
difference with
neighbor

N
Rule2

Overlap
opposite
neighbor

Re-azimuth >=10
difference with
neighbor

N
1BPS >10
OR 1APS
>4

N
Antenna
face to
face with
neighbor

E tilt <
8/10
(below
max)

N
TRIGTIME1
B
>320

Implement RET =>2

*MOD
INTRARELTHDFOR1BP
S =10
INTRARELTHDFOR1AP
S=4

*MOD TRIGTIME1B
=320

N
Down tilt
Mechanical

END

*Monitor other main KPI

specially CCSR after implement

3G Multi-Sector
Re-Azimuth guideline
More than 10

Rule 1: Opposite Antenna can

not face to face, the minimum
angle of them should more than
10 degrees;

Overlap no opposite

More than 10

Rule 2: The overlap can not

opposite, the minimum angle of
them should more than 10
degrees;

Angle between Antennas larger than 90

Less than 90

Rule 3: The angle between 65

antenna and split antenna should be

more than 90

more than 90 degrees between the

split antenna should be more than 100
degree

IRAT Optimization Principle

IRAT Problem Checklist
IRAT Troubleshooting Checklist
1. Scope and Failure Causes
Determine if cause by network , WPC, Top UEs and
Top causes

Physical Channel Failure

2. Parameter Consistency
Verify network IRAT NPT parameters if
implemented

3G Aggressive Setting

3. Version
Check if there are known issues for current version

Current network no issue with version

4. Clock
Check clock issues between 2G and 3G WPCs

Check 2G and 3G clock alarm

5. RF Channels
Check 2G WPCs IB band (3-5 >5%) and RxQual (05 <80%)

Check 2G IB band and RxQual indicators

6. Resources and Capacity

Identify congested 2G based on TCH block, CPU
and DPU load

Check 2G TCH blocking

IRAT CS Scope and Failures

About 98% of CS IRAT Failures are due to Physical Channel Failure
CS IRAT Failure Causes
1.On the networks where the inter-RAT CS handover success rate is normal,
physical channel failure accounts for more than 75% in causes for
handover failures.
2.Abort and No reply causes refer to causes of non-physical channel failures.
During handovers, UEs was not able ton access GSM networks or return to
the UMTS networks. This kind of failures is recorded as call drops.

JABO ISHO SR
JABODETABEK - Sum of ISHO_ATT

7000000
6000000
5000000
4000000
3000000
2000000
1000000
0

Jabodetabek IRAT CS Failure Distribution

Sum
of
VS.IRATHO.F
ailOutCS.Abort; 9605;
2%
Sum
VS.IRATHO.FailOutCS.NoReply;
5; 0%
Sum
ofof
IRATHO.F
ailOutCS.CfgUnsupp;
561;
0%

JABODETABEK - Sum of ISHO Success Rate

ISHO
Optim
May 18

95.3
95.2
95.1
95
94.9
94.8
94.7
94.6
94.5

Sum of IRATHO.FailOutCS.PhyChFail; 390901; 97%

98% of IRAT CS failures are due to Physical

Channel failures
*Data taken May 20-22

3G Strategy Rollout: TARGETRATCSTHD,PENALTYTIMEFORPHYCHFAIL ,INTERRATPHYCHFAILNUM & CSPSHOPRIOMEASTIMERLEN

Fact Finding:
Currently Jabo ISHO SR is less than 95%.

Action Taken:

Rollout at 6 WPC RNC was done on 18-May-2016

Analysis:
From performance show that IRAT SR is 92.55%(take one worst RNC
BuaranMetro1 for example) already less than 95%, and The mainly
ISHO failure is PhyChFail , which contribute 93.15%:

Pro :

To improve ISHO SR.

Cons :
Have impact on CDR.

Execution Selection Criteria :

No 3G Congestion, ISHO SR <93%, sorted highest ISHO Fail

Background:
TARGETRATCSTHD:

this parameter is used for the assessment of

coverage-based inter-RAT hand over. When the quality of target cell in the interRAT measurement report fulfills the formula Mother_RAT(GSM RSSI) + CIO >=
Tother_RAT(TARGETRATCSTHD) + H/2, The system starts the trigger timer, and
makes the handover decision after the timer expires. By the bigger parameter
setting to reduce IRAT handover and improve ISHO SR .

PENALTYTIMEFORPHYCHFAIL:

its Length of a penalty timer for inter-RAT

handover failures due to physical channel failures. During the period specified
by "PenaltyTimeForPhyChFail", the UE is not allowed to make inter-RAT handover
attempts.
INTERRATPHYCHFAILNUM: its maximum number of inter-RAT handover
failures allowed due to physical channel failure. When the number of inter-RAT
handover failures due to physical channel failure exceeds the threshold, a
penalty is given to the UE. During the time specified by
"PenaltyTimeForInterRatPhyChFail", the UE is not allowed to make inter-RAT
handover attempts.
CSHOPRIOMEASTIMERLEN: Interval between an inter-frequency
measurement control message for CS services and an inter-RAT measurement
control message for CS services. When a UE in compressed mode is processing
a CS service and is about to perform an inter-RAT or inter-frequency handover,
the RNC preferentially sends the UE an inter-frequency measurement control

Parameter Setting :
Current Setting
TARGETRATCSTHD=16
PENALTYTIMEFORPHYCHFAIL=30
INTERRATPHYCHFAILNUM=3
CSHOPRIOMEASTIMERLEN=3
PSHOPRIOMEASTIMERLEN=3

Proposed Setting
TARGETRATCSTHD=26
PENALTYTIMEFORPHYCHFAIL=60/90
INTERRATPHYCHFAILNUM=1
CSHOPRIOMEASTIMERLEN=3
PSHOPRIOMEASTIMERLEN=3

Result Summary (Data comparison 12-May and 19-May

2016):
ISHO SR % improve 18.29%
Improve
18.29%

KPI Data

IRAT Optimization Principle

IRAT Optimization Actions
IRAT Optimization Actions
Physical Channel Failures

Action2: TargetRatCsThd set to 25

The BTS does not detect the Handover Access

message.

Trace the BSC

signaling.

Check the interference, uplink/downlink

imbalance, and clock status to ensure
that the synchronization between the UE
and the target cell is successful.

The BSC does not receive the Handover

Access message.

Trace the BSC

signaling.

Check and optimize the flow control and

congestion.

The physical information is abnormal. For

example, the BTS does not send the physical
information, the UE fails to receive the
physical information, or the UE fails to decode
the physical information message.

Trace the UE
signaling.

Check whether the BTS delivers the

physical information and whether the UE
receives the information. Check the
interference, uplink/downlink imbalance.

The SABM frame is abnormal. For example,

the BTS does not receive the SABM frame,
the UE does not send the SABM frame, or the
BTS fails to decode the SABM frame.

Trace the UE
signaling.

Check the interference, uplink/downlink

imbalance, and whether the UE sends the
SABM frame.

The UA frame is abnormal. For example, the

BTS does not send the UA frame, the UE does
not receive the UA frame, or the UE fails to
decode the UA frame.

Trace the UE
signaling.

Check whether the BTS delivers the UA

frame and whether the UE receives the
frame. Check the interference,
uplink/downlink imbalance,.

The establish indication decoding fails.

Trace the BSC

signaling.

The top UEs cause the physical channel

failure.

Trace the PCHR

and IOS.

The top cells cause the physical channel

failure.

Trace the PCHR,

traffic statistics,
and IOS.

Limited DL Coverage: RxQual 0-5 < 80%

Action1: CIOOffset set to 10
Action2: TargetRatCsThd set to 25
Congestion: TCH Blocking > 3%
Action1: CIOOffset set to 10
UE Compatibility: Top 5% UE contribute >30%
failures
Action1: UE blacklist IRAT CS
Clock Issue: Clock alarm
Action1: Fix clock alarm

Troubleshooting and
Optimization Measures

Scenario

Limited UL Coverage: IB Band 3-5 > 5%

Action1: CIOOffset set to 10

Confirmatio
n Method

No.

Check the interference and

uplink/downlink imbalance.
Check whether UE incompatibility
occurs according to the blacklist and
white list and check the clock.
Different UEs have different sensitivity to the
clock frequency offset.

Check and optimize the clock,

interference, and uplink/downlink
imbalance.

IFHO SR JABODETABEK
IFHO SR Daily KPI vs. Optimization Activity
Activity

JABODETABEK - IFHO SR
97
96
95
94
93

Target
IFHO SR >
95%

3
2

6
5

9
8

1
0

1. Feb-1 Black list for IFHO

RNC_TTCBSD4

2. Feb-3 IFHO Penalty All RNC

rollout

3. Feb-10 IFHO improvement

Blind HO trial
RNC_WismaMulia1

4. Feb-16 IFHO Black UE List

rollout RNC_Meruya2 and
RNC_SimatupangMetro1

5. Feb-17 IFHO Inter-

92

FreqThdEcNo threshold trial

RNC_BuaranMetro1

91

6. Feb-22 IFHO Inter-Freq trigger

90

7. Mar-1 IFHO Improvement-

89

trial RNC_BuaranMetro1

BlindHO Optim Rollout Batch

1

8. Mar-3 IFHO Improvement-

BlindHO Optim Rollout Batch

2

9. Apr-7 CS IFHO Priority for

cells ISHO SR WPC in 5 RNC

10.Apr-13 CS IFHO Priority for

cells ISHO SR WPC in 8 RNC

RAN QUALITY: IFHO STRATEGIC Summary

System

Strategy and Feature

Deployed

3G

IFHO Black list

Strategic

1-Feb-16

3G

IFHO Black list

Strategic

3-Feb-16

3G

IFHO Blind Handover Optim

Strategic

10-Feb-16

3G

IFHO Blacklist

Strategic

16 & 17 February 2016

3G

Inter-FreqThdEcNo Threshold

Strategic

17-Feb-16

3G

IFHO Blind Handover Optim

Strategic

18-Feb-16

3G

IFHO Inter-Freq Trigger (fallback)

Strategic

22-Feb-16

3G

IFHO Blind Handover Optim (Batch1)

Strategic

1-Mar-16

3G

IFHO Blind Handover Optim (Batch2)

Strategic

3-Mar-16

14 RNC

IFHO SR improve 25.27%

3G
3G

CS IFHO Priority
CS IFHO Priority

Strategic
Strategic

7-Apr-16
13-Apr-16

4 RNC
8 RNC

ISHO SR % improve 31.94%

ISHO SR % improve 41.01%

UCELLINTERFREQHOCOV

Category Date Execution Scale

Result

IFHO SR maintain (need longer time to monitor)

CCSR CS and PS maintain
IFHO SR improve 22.86%
2694 Cells CCSR CS maintain
CCSR PS maintain
IFHO SR improve 43.08%
20 Cells CCSR PS improve 67.34%
CCSR CS improve 44.03%
RNC_Meruya2
- CCSR CS improve 34.08%
2 RNC
- IFHO SR maintain
RNC_SimatupangMetro1
- IFHO SR improve 21.05%
CCSR CS maintain
1 RNC
CCSR PS maintain
IFHO SR improve 47.78%
923 Cells
BlindHO SR improve 10.31%
IFHO SR under monitoring -31.28%
2654 Cells CCSR CS maintain
CCSR PS maintain
IFHO SR improve 3.53%
14 RNC CCSR CS improve 10.27%
Traffic Voice improve 5.14%
1 RNC

UCELLINTRAFREQHO

IFHOFAILNUM=1 (make smaller)

BLINDHORSCP1FTHRESHOLD=-70 (make bigger)
PENALTYTIMERFORIFHOFAIL=90 (make larger)

3G Strategy Rollout: IFHO Penalty

Fact Finding:

Background:

IFHO SR degrade less than 95% and need improve IFHO SR.
Action Taken:
Roll out on All RNC Top 100 Worst Cells (total 2694 cells)
was done on 3 February 2016
Result Summary (Data comparison 28-Jan and 4-Feb):
IFHO SR improve 22.86%
CCSR CS maintain
CCSR PS maintain

IFHOFAILNUM=1
PENALTYTIMERFORIFHOFAIL=90

IFHOFAILNUM: Maximum number of consecutive handover failures after a

coverage-based inter-frequency handover, inter-frequency blind handover
triggered by event 1F, or QoS-based inter-frequency handover to a cell
fails due to the air interface faults. When the number of consecutive
handover failures of a UE in a call is greater than the value of this
parameter, the RNC penalizes the UE and the UE cannot initiate such
inter-frequency handovers within the penalty period.
PENALTYTIMERFORIFHOFAIL : Duration after which the coverage-based
inter-frequency handover, inter-frequency blind handover triggered by
event 1F, or QoS-based inter-frequency handover to a cell can be reinitiated after a failure of such handover to this cell due to the air
interface faults.
BGN: Fallback BGN setting to 171 if -105.9dB<RTWP <-95 dB to increase
IFHO attempts due to load balancing and improve success rate.

KPI Trend

Improve
22.86%

maintai
n

maintai
n

3G Strategy Rollout : IFHO Blind Handover Optim (Batch 2)

Fact Finding:
IFHO SR in Jabotabek less than 95%, need improve IFHO SR.

Action Taken:

Rollout at all cell BindHO SR <95% in Jabo batch 2 (14 RNC) was done on 3-March2016 23:00
Result Summary (Data comparison 26-Feb and 4-March):

IFHO SR improve 25.27 %

Background:
Quality threshold for triggering an emergent blind handover to a cell in the event 1F
report. A blind handover is triggered only when the signal quality of a cell in the event
1F report exceeds the value of this parameter. Otherwise, the report is discarded.
This parameter is used to increase the success rate of blind handovers. If the signal
quality of all the cells in the event 1F report is poor, the UE may be located at the
edge of the coverage area. Under this situation, triggering blind handovers may cause
call drops.

Improve
25.27 %

KPI