INDOOR OPTIMIZATION PROCEDUREINDOOR OPTIMIZATION PROCEDURE4 4 -- Main Problem:Main Problem:-- TCH DropTCH Drop-- High Handover FailHigh Handover Fail-- Low SDCCH Success RateLow SDCCH Success Rate-- High TCH BlockingHigh TCH Blocking-- Customer/VIP ComplaintCustomer/VIP Complaint

Prepared by: Anton AriyastonoPrepared by: Anton Ariyastono

HIGH TCH DROP (one to one relation)HIGH TCH DROP (one to one relation)HIGH TCH DROP (one to one relation)HIGH TCH DROP (one to one relation)HIGH TCH DROP (one to one relation)HIGH TCH DROP (one to one relation)HIGH TCH DROP (one to one relation)HIGH TCH DROP (one to one relation)Main Possible Problem:1. Interference on BCCH TRX2. Interference on Hopping TRX (DL Interference)3. External Interference (UL interference)4. Bad Neighbor relation (bad handover)5. Low Coverage6. Hardware faulty or unbalance TRX Power7. Spillage8. Caused by A_IF, TR or LAPD FAIL

Data collection:1. BCCH planning, ND report 072 and Scan Test2. ND Report 216, 072 and Walk Test3. ND Report 216 and Alarm (interference)4. ND Report 204, 153, 072 and Walk Test 5. ND Report 216, IBS design, and Walk Test6. Alarm (ZEOH & ZEOL) and site visit7. ND Report 216 or 232 and Walk Test8. ND Report 204

Problem Analysis:1. Check possibility Co. or Adj. Interference. Check

clean BCCH frequency.2. Check DL quality Distribution, Check clean

BCCH frequency (072 or Walk Test) and Check MAL and MAIO

3. Check UL quality Distribution, check UL interference and Average band of TCH interference

4. Check % of HO fail from adjacencies, focused on High HO Fail. Check TCH_RF_HO_OLD. Check possibility to add some neighbor.

5. Check best serving cell, possibility HO to best serving cell (Macro or Indoor) and possibility to add antenna.

6. Check TRX alarm (mostly 7745 together with 7743 or 7746). Check TRX configuration.

7. Check TA distribution, coverage spillage and BS TX PWR MAX.

8. Check and compare which one the highest: Fail on RADIO, ABIS, A_IF, TR or LAPD.

Problem Solving:1. Changing BCCH2. Use non-hopping on 2nd TRX (if 2 TRXs installed).

Change MAL or MAIO. Disable power control to combat interference.

3. Setting power control parameter to decrease interference in Busy Hour. Discussed with Telkomsel to Scan freq. if there is real external interference.

4. Make faster or delay HO by changing HO parameter on correct network layering to decrease HO fail. Add some possible neighbor.

5. Make faster HO to best serving cell to minimize possibility of drop call. Add some antenna on worst area. Review IBS design and retrofit.

6. Reset TRX or inform Telkomsel to replaced TRX. Change configuration if this make unbalance of TRX power.

7. Changing antenna placement. Changing HO parameter add some delay with FMT or AUCL. Change BS TX PWR MAX if possible.

8. Discuss and inform Telkomsel if problem on A_IF, TR and LAPD.

HIGH HANDOVER FAIL (one to one relation)HIGH HANDOVER FAIL (one to one relation)HIGH HANDOVER FAIL (one to one relation)HIGH HANDOVER FAIL (one to one relation)HIGH HANDOVER FAIL (one to one relation)HIGH HANDOVER FAIL (one to one relation)HIGH HANDOVER FAIL (one to one relation)HIGH HANDOVER FAIL (one to one relation)

Main Possible Problem:1. Interference on BCCH2. High TCH blocking on neighbor or it self3. Wrong TSC (Training Sequence Code) setting4. Bad Neighbor relation5. Hardware faulty or unbalance TRX power6. Spillage7. Others

Data collection:1. BCCH planning, ND report 072 and Scan Test2. Cell Stat (TQM2001) and ND report 1533. OMCPAR and ND Report 1534. ND Report 153, 072 and Walk Test5. Alarm (ZEOH & ZEOL) and site visit6. ND Report 216 or 232 and Walk Test7. ND Report 216

Problem Analysis:1. Check possibility Co. or Adj. Interference and

check clean BCCH frequency.2. Check neighbor traffic & TCH blocking, check

possibility for traffic sharing.3. Check TSC setting should same value with

BCC. Check HO performance (in and out)4. Check percentage of HO fail from adjacencies,

focused on High HO Fail. Check possibility to add some neighbor.

5. Check TRX alarm (mostly 7745 together with 7743 or 7746). Check TRX configuration.

6. Check TA distribution, coverage spillage and BS TX PWR MAX.

7. Check the highest handover cause: by interference, quality, level, power budget, GPRS, etc. Check for the highest HO failure: by Blocked, Conn. Fail., Return to Old, End of HO, etc. The highest value is possible as the highest contribution of HO fail.

Problem Solving:1. Changing BCCH2. Add TRX, traffic sharing by optimize HO or per

ADCE and optimize directed retry.3. Change TSC same as BCC value4. Make faster or delay HO by changing HO

parameter or per ADCE on correct network layering to decrease HO fail. Add some possible neighbor. Decrease “ping-pong” handover.

5. Reset TRX or inform Telkomsel to replaced TRX. Changing configuration if this make unbalance of TRX power.

6. Changing antenna placement. Changing HO parameter add some delay with FMT or AUCL. Change BS TX PWR MAX if possible.

7. Optimize HO based on HO cause problem with focused to the highest failure. Disable power control if high number of HO caused by level.

LOW SDCCH SUCCESS RATE (one to one relation)LOW SDCCH SUCCESS RATE (one to one relation)LOW SDCCH SUCCESS RATE (one to one relation)LOW SDCCH SUCCESS RATE (one to one relation)LOW SDCCH SUCCESS RATE (one to one relation)LOW SDCCH SUCCESS RATE (one to one relation)LOW SDCCH SUCCESS RATE (one to one relation)LOW SDCCH SUCCESS RATE (one to one relation)

Main Possible Problem:1. Interference on BCCH2. High TCH blocking3. SD Drop on Location Update4. Caused by A_IF, TR or LAPD FAIL5. Hardware faulty6. Spillage7. Others

Data collection:1. BCCH planning, ND report 072 and Scan Test2. Cell Stat (TQM2001) and ND report 1533. ND Report 2164. ND Report 2045. Alarm (ZEOH & ZEOL)6. ND Report 216 or 232 and Walk Test7. ND Report 204, OMCPAR and Cellstat

(TQM2001)

Problem Analysis:1. Check possibility Co. or Adj. Interference and

check clean BCCH frequency.2. Check neighbor traffic & TCH blocking, check

possibility for traffic sharing.3. Check SDCCH True Seizure. Check if Location

update is the highest contributor of SD Drop.4. Check and compare which one the highest: Fail

on RADIO, ABIS, A_IF, TR or LAPD.5. Check TRX alarm (mostly 7745 alone or

together with 7743)6. Check TA distribution, coverage spillage and BS

TX PWR MAX.7. Check RX Lev Access Min and Max Number of

Retransmission. Check RACH Rejected and SDCCH request (fails or ghost).

Problem Solving:1. Changing BCCH2. Add TRX, traffic sharing by optimize HO and

optimize directed retry.3. Optimize C2 parameter. Re-homing.4. Discuss and inform Telkomsel if problem on

A_IF, TR and LAPD.5. Reset TRX or inform Telkomsel to replaced TRX6. Changing antenna placement. Optimize C2

parameter. Change BS TX PWR MAX if possible.7. Optimize RX Lev Access Min, purpose for

minimizing Ghost RACH. Optimize Max Number of Retransmission.

HIGH TCH BLOCKING (one to one relation)HIGH TCH BLOCKING (one to one relation)HIGH TCH BLOCKING (one to one relation)HIGH TCH BLOCKING (one to one relation)HIGH TCH BLOCKING (one to one relation)HIGH TCH BLOCKING (one to one relation)HIGH TCH BLOCKING (one to one relation)HIGH TCH BLOCKING (one to one relation)

Main Possible Problem:1. Normal TCH Blocking2. Caused by Handover

Data collection:1. Cell Stat (TQM2001) and ND report 1532. ND Report 204, 153 and Walk Test

Problem Analysis:1. Check neighbor traffic & TCH blocking, check

possibility for traffic sharing.2. Check TCH request by handover. Check the

highest number of HO to adjacencies. Check possibility of spillage.

Problem Solving:1. Add TRX. Traffic sharing by optimize HO or per

ADCE and optimize directed retry.2. Optimize HO parameter per ADCE. Put some

delay on handover to decrease possible “ping-pong” handover causing lack of TCH resources.

CUSTOCUSTOCUSTOCUSTOMER/VIP COMPLAINTMER/VIP COMPLAINTMER/VIP COMPLAINTMER/VIP COMPLAINTCUSTOMER/VIP COMPLAINTCUSTOMER/VIP COMPLAINTCUSTOMER/VIP COMPLAINTCUSTOMER/VIP COMPLAINT

Main Possible Problem:- TCH drop- Call Drop on Call Setup- Low coverage

Data collection:1. Walk Test Continuous call2. Walk Test Call sequence3. Walk Test Scanning Frequency4. ND Report 072, 153, 204 and 2165. IBS Design spreadsheet

Problem Analysis:1. Continuous call to check handover performance,

quality of call, DL RX level, MS TX Power.2. Call sequence to check the best serving cell, C2

parameter of knowing cells. Call setup performance.

3. Scanning Frequency to check possibility interference. Check un-define adjacencies by real-time walk test.

4. ND Report 072: Check un-define adjacencies ND Report 153: Check ADCE HO performance ND Report 204: Check Cell Performance ND Report 216: Check Cell Performance

5. Review IBS design of antenna EIRP

Problem Solving:1. Caused by HO performance problem; optimize

HO and HO per ADCE.2. Caused by missing neighbor; add neighbor based

on Scanning frequency and ND Report 072.3. Caused by call setup camping on Macro site;

Optimize C2, make to be the highest C2 than neighbor, the possibility of spillage should be consider.

4. Achievement criteria:- Call should always camped to indoor cell during

call setup; Make indoor the higher C2 than ADCE.

- No handover to outdoor cell during the call; Make delay handover to outdoor cell, the possibility of delay HO in the lobby should be consider.

- No drop call during the call; Make only handover-in (one-way HO) for the lowest RX level neighbor. Add neighbor (one-way, HO-in) of the highest possibility ADCE of the neighbor, to minimize drop call if the call handover to ADCE of the neighbor.

5. Review IBS design for possibility of retrofit or add some antenna in the low coverage area.