presentasi initial tuning

21
Objective Know How To Drive Test Initial Tuning Know Software for Initial Tuning : mcom , katherein scala, static analyzer Know Initial Tuning Report

Upload: makhful-adhim

Post on 20-Jan-2016

18 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: Presentasi Initial Tuning

Objective

• Know How To Drive Test Initial Tuning• Know Software for Initial Tuning : mcom ,

katherein scala, static analyzer• Know Initial Tuning Report

Page 2: Presentasi Initial Tuning

INITIAL TUNING

Page 3: Presentasi Initial Tuning

Preparation• Software :

- Tems Investigation 4- Map Info- MCOM- Kathrein Scala (additional)- Static Analyzer (additional)

• Tools :- 2 Tems MS (T68)- GPS- Laptop- Camera- Other ( inverter, rigger tools)

Page 4: Presentasi Initial Tuning

Preparation

• Basic Knowledge :– GSM Generally– Drive Test (plus Scanning Freq n Time Slot Check)

• Data :– Map– CDD + MO (dump + process) - daily Update– Kathrein Analog– STS database – daily update (additional)

Page 5: Presentasi Initial Tuning

About MCOM• Create New Project• Import new mcom site• Import CDD dump (neigbor+carrier) – CDD Should be updated daily• Check BCCH and interference• Check neighbor• MCOM workspace will be used as MapInfo workspace

Page 6: Presentasi Initial Tuning

About MCOM• Check BCCH and Interference sample

Page 7: Presentasi Initial Tuning

About MCOM• Check Neighboring sample

Page 8: Presentasi Initial Tuning

About Kathrein Scala & Katalog• Know antenna type and specification• Know how antenna downtilt affects coverage area in Kathrein Scala

Page 9: Presentasi Initial Tuning

About Static Analyzer• Check Performance Site – Basic KPI Statistic (drop rate, SDCCH success

rate, handover success rate)• Database Should be Updated Daily

Page 10: Presentasi Initial Tuning

About Static Analyzer• Sample 1 : TCH Drop Rate

BAD GOOD

Page 11: Presentasi Initial Tuning

About Static Analyzer• Sample 1 : SDCCH Success Rate

BAD GOOD

Page 12: Presentasi Initial Tuning

About Static Analyzer• Sample 1 : Hand Over Success Rate

BAD GOOD

Page 13: Presentasi Initial Tuning

About CDD n MO• Cell Design Data (contain data such as frequency, neighboring, etc)• Management Object (contain data such as site config, alarm, etc)

Page 14: Presentasi Initial Tuning

Initial Tuning Activity• Preparation (tools and site data)• Site + Neighbors Audit and Change (Coordinate, tilt, orientation/bearing,

panorama, antenna type, height, area)• Drive Test

Tuning Site Band 900: First : MS1 = Dedicated Lock 900, MS2 : Idle Locked to BCCH, Second : MS1 = Dedicated Normal, MS2 : Idle Locked to BCCH,TS Check, Freq ScanningTuning Site Band 1800:MS1 = Dedicated Normal, MS2 : Idle Locked to BCCH,TS Check, Freq Scanning

• Report…..

Page 15: Presentasi Initial Tuning

TimeSlot Check and Freq Scan

• How?5 minutes for Freq Scan each cells / sector

15 minutes for Time Slot Check each cells / sector using Tems Layer 3 Control

• Telkomsel Freq Scan : 50-88 (900 band)576 – 820 (1800 band)

Page 16: Presentasi Initial Tuning

Target

• Target Drive Test– No Blocked Call, No HandOver Fail, No Dropped Call– Good CI plot– Rx Lev, Rx Qual, SQI– Idle Rx Lev vs TCP Plot

• Target KPI Statistik- DCR, HOSR, SDSUCC

Page 17: Presentasi Initial Tuning

Target Drive Test

Parameter GSM (lock

Band) DCS NoteCall Setup

Success Rate 100% 100% Dedicated

Dropped Calls 0% 0% Dedicated

HOSR 100% 100% Dedicated

Rx Qual 0 - 5 >= 97.00% >= 98.50% dedicated, pada level >= -90 dBm

SQI >=18 >=95.00% >=96.00%dedicated, pada level >= -90 dBm, in

Full Rate or EFR condition.

Plot Rx Level >=95.00% >=95.00%

Page 18: Presentasi Initial Tuning

Level Idle vs TCP Plotsample

Page 19: Presentasi Initial Tuning

Target KPI Stats

AVERAGE VALUE SDSR HOSR TDR

Dense Urban 900 / ST DCS 90,00% 94,00% 1,08%

Dense Urban 1800 93,35% 94,85% 0,59%

Urban 900 / ST DCS 86,00% 94,80% 1,70%

Urban 1800 89,20% 97,30% 0,81%

Rural 900/ ST DCS 84,00% 94,50% 2,10%

Rural 1800 91,20% 97,50% 1,10%

Page 20: Presentasi Initial Tuning

Problems• Site Down (Power?, Transmisi?) -- call Tuning Engineer / Coordinator• Site On but not Servin -- call Tuning Engineer / Coordinator• Cannot making call -- call Tuning Engineer / Coordinator• Cannot HO (Neighbor Relation not created yet) – call Tuning Engineer / Coordinator• HO Failure (Interference, Co BSIC, Congestion), need parameter / frequency

changing -- call Tuning Engineer / Coordinator• Pingpong HO (Cross feeder, orientation problem) -- call Tuning Engineer /

Coordinator• Difficult HO DCS (Layer 6) to GSM (Layer 7) -- call Tuning Engineer / Coordinator• Bad Quality (Interference), need frequency changing -- call Tuning Engineer /

Coordinator.• Low signal strength (wrong tilt / orientation)• Installation Problem (cross feeder, antenna tilt n orientation), take any logfiles /

photos -- call Tuning Engineer / Coordinator• Coordinate problem, different between planned coordinate and actual coordinate --

need any changing -- call Tuning Engineer / Coordinator• Drive Test Route Problem• Community Problem, Cannot access to site – call Tuning Engineer / Coordinator• Dll…

Page 21: Presentasi Initial Tuning

Making Report• Export Logfiles• KPI calculation (optional using macro)• Plot in Map Info• Others……….