Top Banner
1 Network Quality Management Parameter Standardization Guideline Service Impact Network Quality Management Group PT. Telekomunikasi Selular
21

Parameter Standarization Guideline

Dec 27, 2015

Download

Documents

Agus Bule

fwefwefwefwef
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Page 1: Parameter Standarization Guideline

1 Network Quality Management

Parameter Standardization GuidelineService Impact

Network Quality Management GroupPT. Telekomunikasi Selular

Page 2: Parameter Standarization Guideline

2 Network Quality Management

Outline• Background• Objective• General Concept• Detail Parameter• Parameter Change Flow Chart

Page 3: Parameter Standarization Guideline

3 Network Quality Management

Background Good KPI but bad user experience Many new sites / new NE implementation with

improper parameter Many in-consistent parameter on existing sites/NE Many adjustment on parameter that can improve KPI

but effecting worse user experience

Page 4: Parameter Standarization Guideline

4 Network Quality Management

Objective To Have standard parameter that could impact user

experience for all existing & new sites / NE To Decrease Gap between KPI achievement and user

experience

Page 5: Parameter Standarization Guideline

5 Network Quality Management

General Concept 3 Categorize of parameter :

1. Optimization parameter2. Non-Optimization parameter3. Non-Optimization parameter (as design)

Non-Optimization parameter will be categorized into service impact & non service impact

Non-Optimization parameter that service impact is parameter that if modified will improve KPI but effecting user experience worse

So these parameter must follow Tsel NPT value

Page 6: Parameter Standarization Guideline

6 Network Quality Management

2G RAN Parameter Parameter

Current Calue Recommend Value Unit Remarks

NSN Ericsson Huawei ZTE

Ms Tx Power MaxmsTxPwrMaxGSM : 33msTxPwrMaxGSM1x00 : 43gprsMsTxpwrMaxCCH : 33gprsMsTxPwrMaxCCH1x00 : 43

MSTXPWR GSM: 33DCS: 30

MSTXPWR GSM: 33DCS: 30 MsTxPwrMax : 33 GSM: 33

DCS: 30 dBm

RxLev Access Min rxLevAccessMin => GSM : 105, DCS : 95 ACCMIN => GSM : 102 , DCS : 95 ACCMIN => GSM : 102 , DCS : 95 RxLevAccessMin : -100 GSM: -105 dBm

DCS: -95 dBm dBm Impacted to TCH Drop

TA Max msMaxDistInCallSetup : 255 MAXTA => Normal cell : 64 , XrangeCell : 255 MAXTA => Normal cell : 64 TaMax : No Limit No Limit

BS Tx Power max (attenuation) bsTxPwrMax, bsTxPwrMax1x00 : 0 - - - 0 dB ZTE only has BS Tx Power Min

AFR Radio Link Timeout radioLinkTimeoutAmr : 44 RLINKTAFR (44) & RLINKUPAFR (48) AFR RLT:56 BsRadioLkTmOutAMRFR : 44 44 Sacch_times Impacted to TCH Drop

AHR Radio Link Timeout radioLinkTimeoutAmrHr : 44 RLINKTAHR (44) & RLINKUPAHR (48) AHR RLT:56 BsRadioLkTmOutAMRHR : 44 44 Sacch_times Impacted to TCH Drop

Radio Link Timeout radioLinkTimeout => GSM : 36, DCS : 32

RLINKT for Downlink (GSM : 36 , DCS :32) , RLINKUP for Uplink (GSM : 40 , DCS : 36)

RLT : 52BsRadioLKTmOut, MsRadioLKTmOut => GSM: 36; DCS: 32

36 Sacch_times Impacted to TCH Drop

Max Number of Retransmission maxNumberRetransmission : 2 MAXRET : 2 IMMASSMAXSENDNUM = 2 MaxRetrans : 4 2 times Number of Multiframes noOfMFramesBetweenPaging : 2 MFRMS : 2 BSPAMFRAMS=2 BsPaMframs : 5 2 Number Number of Slots Spread Trans nbrOfSlotsSpreadTrans : 32 TX : 32 TX : 32 TxInteger : 14 32 Number Periodic Ms Location Update(2G/3G) timerPeriodicUpdateMs : 2 h T3212 : 40 (Unit : decihour in

Ericsson)T3212 : 40 (Unit : decihour in Huawei) T3212 : 360 4 Hours If > 4 hours will be change to 4

hours, if below still remain

Sacch repeat window sacchRepeatWindow : 4 SACCH/T N200 : 5 times N200SACCH : 5 (RepeatACCH = YES) -> SACCH repeat Hardcoded 4 times

T200S T200S : 300 msParameter T200 in Ericsson related to parameter SIGDEL , if SIGDEL= NORMAL (T200=240ms) then SIGDEL=LONG (T200=1400ms)

T200S:200 T200_0, T200_5 : 5 240 ms Need confirm why ZTE value too small

T200F T200F : 200 msParameter T200 in Ericsson related to parameter SIGDEL , if SIGDEL= NORMAL (T200=240ms) then SIGDEL=LONG (T200=1400ms)

T200F:200 T200_1, T200_2 : 5 200 ms Need confirm why ZTE value too small

Max Queue Length timeLimitCall : 10 - TIQUEUINGTIMER=8 rmsT11 : 6 7 s T3101 T3101 : 3 15-30 (unit in deciseconds) T3101=3 RmsT3101 : 3 3 s

T8 T8 : 12 T8 in Ater Signalling => 8 second , T8 in A-interface : 25 second T8=10 RmsT8 : 1 As per vendor s Never been adjusted

T7 T7 : 20 T7 : 3 T7=10 RmsT7 : 1.5 As per vendor s Never been adjustedT3103 T3103 : 6 T3103 : 6 T3103=10 RmsT3103 : 6 As per vendor s Never been adjustedT3107 T3107 : 6 T3107 : 6 T3107=10 RmsT3107 : 6 As per vendor s Never been adjusted

Time Limit Handover timeLimitHandover : 5HANDOVER_ REQUEST_timer (THNDREQ) => 8 second , HANDOVER_ REJECT_timer (THNDRQREJ) => 1 second

TQHO=8 RmsTqho : 5 6 s

Call Reestablishment Allowed Not allowed Not allowed Not allowed Not allowed Not allowed Impacted to TCH Drop

Page 7: Parameter Standarization Guideline

7 Network Quality Management

3G RAN Parameter Parameter

Current Value Recommend Value Unit RemarkNSN Ericsson Huawei ZTE

DCH to FACH Transition Time

InactivityTimerDownlinkDCH8-32: 5InactivityTimerUplinkDCH8-32: 5InactivityTimerDownlinkDCH64-384: 2InactivityTimerUplinkDCH8-32: 2

hsdschInactivityTimerCpc For CPC Capable : 5 , hsdschInactivityTimer Non_CPC Capable : 2

BeD2FStateTransTimer=5 TRbRecfgCmpDtoF : 15 5 s

FACH to PCH Transition time UL_DL_activation_timer: 2ExtendedULDLactivationTmr: 0 - BeF2PStateTransTimer=

2 2 s

PCH to Idle state transition time MSActivitySupervision: 29 InactivityTimerPCH : 30 PSInactTmr= 5 As per vendor

minute

FACH to DCH Transition Time TrafVolTimeToTriggerUL: 0 sTrafVolTimeToTriggerDL: 0 s - BEF2DTVMTIMETOTRIG

=0T312Connected : 1N312Connected : 1 0 s

Trigger FACH to DCH TrafVolThresholdULLow: 7 (1 KB)TrafVolThresholdDLLow: 7 (1 KB)

- BEF2DTVMTHD=1024 1000 Bytes

HSDPA to FACH trigger time MACdflowthroughputTimetoTrigger: 5 - BEH2FTVMTIMETOTRIG

=5 5 s

HSDPA to FACH trigger throughput

MACdflowthroughputRelThr: 0 bps - BEH2FTVMTHD=64 64 Bytes

T3212 (Peridic Location Update) CS_T3212: 2 T3212 : 4 T3212=4 T3212Cs : 4 4 HoursIf > 4 hours will be change to 4 hours, if below still remain

QqualMin QqualMin : -18 QqualMin : -18 QqualMin=-18 QqualMin : -18 -18 dB QrxLevMin QrxLevMin : -115 QrxLevMin : -115 QrxLevMin=-115 QrxLevMin : -115 -115 dBm

Max Bit Rate HSPA/MAC-D Flow MaxBitRateNRTMACDFlow: No Limit - - HsMaxDlRateDch : No

Limit No Limit

Max Bit Rate DL PS MaxBitRateDLPSNRT: 384 - R99MaxDlRateDch : 384 384 Kbps

Max Bit Rate UL PS MaxBitRateULPSNRT: 384 - R99MaxUlRateDch : 384 384 Kbps

T313 T313 : 3 T313 : 3 T313=3 T313 : 3 3 S Impacted to CCSR CSN313 N313 : 50 N313 : 100 N313=20 N313 : 50 20 Times T300 T300 : 2 - T300=2 T3002 : 2 2 S N300 N300 : 3 - N300=3 N300 : 3 3 Times UE Tx Power on PRACH UEtxPowerMaxPRACH: 24 - MaxUlTxPowerforint=24 MaxRACHTxPwr : 24 24 dBm T314 T314 : 6 T314 : 12 T314=6 T314 : 4 6 s Impacted to CCSR CS

Page 8: Parameter Standarization Guideline

8 Network Quality Management

Sampling: 2G RLT SettingRadio Link Time Out BalNus vs CJ

• RLT setting in Balnus is too short if compare to setting in CJ that mostly RLT in maximum setting.

• Inline with the setting, drop call in BalNus is worst than CJ.

Page 9: Parameter Standarization Guideline

9 Network Quality Management

Sampling: 3G RLT Setting (T313&T314)

• T314 setting in Balnus is around 4 to 5 seconds while setting in CJ in maximum setting (20 second) and only one RNC is 12 second.

• Inline with the setting, CCSR CS in BalNus is worst than CJ.

Page 10: Parameter Standarization Guideline

10 Network Quality Management

CCR Trend & Improvement

We need to standardize all service impact parameter setting in order to Have standard parameter that could impact user experience for all existing & new sites / NE Decrease Gap between KPI achievement and user experience

Page 11: Parameter Standarization Guideline

11 Network Quality Management

Core Parameter Parameter Background Objective KPI / PI Main Goal

NSN EID NSN EIDDrop Call Issue in RNC PARE Sumalpua due to Mismacthed Timer.

TIAR ≥ 2 x TIAS + Margin for Inaccuracy Timer

Maintain and Improve SCR, CCR

No Standarization Value for parameter TIAS & TIAR in Telkomsel. Variant Value for parameter TIAS & TIAR implemented in TelkomselLong Call Setup due to long paging timer

MSC TIME > BSC TIME + Guard Time (for IDR)

Shorter Call Setup Time

1st Page : 8-10s 1st Page : 8s

No Global Paging used 2nd Page : 10s 2nd Page : 8sSecond Page activated (AT =1 for NSN MSS)

AT : 0 & 1 Global Page : 0 & 1 AT : 1 Global Page : 0

Call Failure due to "absent subscriber"

Maintain and Improve SCR, LUSR

Missmatch Timer Setting between Core and RadioNo Standardization Value for IMSI Detach Timer in both Core and RadioCall Failure due to HLR-VLR "Misscommunication"

Maintain and Improve SCR, PSR

Obselete Subcribers Database still record in VLR

Reducing Absent Subscribers

Intra MSC Handover Failure due to timer expiryInappropriate timer setting in both Core and Radio

Bad Voice Quality TrFO active at CoreHR codec (in Kbps) :

4.75, 5.90, 7.40HR codec (in Kbps) :

4.75, 5.90, 7.40

HR codec (in Kbps) : 4.75, 5.90, 7.40

FR codec (in Kbps) : 4.75, 5.90, 7.40, 12.2

FR codec (in Kbps) : 4.75, 5.90, 7.40, 12.2

FR codec (in Kbps) : 4.75, 5.90, 7.40, 12.2

TrFO Active TrFO Active TrFO Active TrFO Active

Property11(7)Property12(7)Property13(7)Property14(7)Property19(8)

Property20(8&15)Property21(0&7)Property22(0&7)

Property11(7)Property12(7)Property13(7)Property14(7)Property19(8)Property20(8)Property21(7)Property22(7)

2H:10m - 8H:15m 4H:6m - 7H:15m 5H:15m

1 Day 1 & 3 Days 1 Day 1 Day

15s 15s & 41s 41s 41s

5H:15m

INT : 400ms - 700ms INT : 400ms

TIAS : 60s TIAR : 660s

TIAS : 60s TIAR : 660s

Suggested Value

TIAS : 90s TIAR : 270s

TIAS : 300s TIAR : 660s

Current Value

Loitering Time

T8 Timer

Codec Parameter

SCR, CCR

PSR

SCR, LUSR

SCR, PSR

HOSR, CCR

MOS

Standardized Value : TIAS = 60s and TIAR = 660s for all Node

TIAS/TIAR

Paging Timer

IMSI Detach Timer

Second Paging are not activated in some LAC

Inappropriate Codec setting in both Core and Radio

Better MOS

MSC TIMER > T8 BSSMAP + T_ESTGUARD + T_REESTABLISH + T_REESTGUARD

1 Day Loitering Time at all MSS

BTDM > T3212 + Guard Time

Standardized Value for all Node

Maintain and Improve PSR

Reducing Absent Subscribers

Maintain and Improve HOSR, CCR

Page 12: Parameter Standarization Guideline

12

Key Programs:Standardized TIAS/TIAR Value for all network element in Telkomsel Network and meet the 3gpp parameter tuning Documentation where TIAR ≥ 2 x TIAS + Margin Time

Key Indicator:• Maintain and improve SCR CCR• Uniform and Standardized Value for all Node

Descriptions:TIAS/TIAR are Sending and Receiving inactive SCCP connection status timer supervision that lead the SCCP to control whole connection processes. In 3gpp standard TIAS is a Periodic "Inactive Test", the message are sent to the remote SCCP when no after message have been sent on the connection for the timer duration. In other hand the connection is terminated by TIAR time if no message are received from remote SCCP node for the duration of the time.

Benefit :• Improve Network Performance & Network Productivity• Easier way in Network Optimization for audit and standardization parameter• Reduced Network Parameter Inconsistency & Discrepancy

TIAS/TIAR Standardization

Re-audit and Update Meeting Roll Out Monitoring &

Evaluation Monitoring

Jan-2014 Feb-2014 Mar-2014 Apr-2015

TIAS/TIAR Standardization

Page 13: Parameter Standarization Guideline

13

Key Programs:Optimized Paging Timer Value for all network element in Telkomsel Network and meet Subscriber perceived satisfactionin making setup call.

Key Indicator:• Maintain and improve SCR CCR• Maintain and improve Paging Success Rate

Descriptions:Paging Timer is the core supervision time when network trying to reach subscriber status in radio network whenever call set up phase establishment. Lower Paging time response mean faster call set up time. Paging time in core network should consider all the set up time taking place in radio part. Standard time paging timer formula :

MSC TIME > BSC TIME + Guard Time (for IDR)

Benefit :• Improve Network Performance & Network Productivity• Optimized Paging Time and call set up time• Reduced Network load due to long call set up

Paging Timer Standardization

Paging Timer Standardization

KPI monitoring and Audit Initiation

Re-audit and Update Meeting FNI and Roll Out Evaluation &

Monitoring

Jan-2014 Feb-2014 Mar-2014 Apr-2015

Page 14: Parameter Standarization Guideline

14

Key Programs:Optimized Core Network in recording subscribers status within Its database and ensuring the “subscriber absent” status is keep up to date whenever call set up is proceeding.

Key Indicator:• Maintain and Improve SCR, • Maintain and Improve LUSR

Descriptions:

Automatic deregistration of mobile subscribers offers the possibility to automatically deregister mobile subscribers that have had no radio contact during a certain period of time in the MSC/VLR. Standard formulation Core IMSI Detach Timer is:

BTDM > T3212+ Guard Time

Benefit :• Improve Network Performance & Network Productivity• Reducing “Absent Subscribers”• Avoid Missmatch Timer Setting between Core and Radio

IMSI Detach Timer Standardization

IMSI Timer Standardization

KPI monitoring and Audit Initiation

Re-audit and Update Meeting FNI and Roll Out Evaluation &

Monitoring

Jan-2014 Feb-2014 Mar-2014 Apr-2015

Page 15: Parameter Standarization Guideline

15

Key Programs:Optimized Core Network in recording subscribers status within Its database and ensuring the “subscriber absent” status is keep up to date whenever call set up is proceeding.

Key Indicator:• Maintain and Improve SCR, • Maintain and Improve LUSR

Descriptions:

Loitering time is the periodic cleaning time to deregister Subscribers from VLR when subscriber already in detach state.

Benefit :• Improve Network Performance & Network Productivity• Reducing “Absent Subscribers”• Avoiding obselete Subscribers Database record in VLR

Loitering Timer Standardization

Loitering Timer Standardization

KPI monitoring and Audit Initiation

Re-audit and Update Meeting FNI and Roll Out Evaluation &

Monitoring

Jan-2014 Feb-2014 Mar-2014 Apr-2015

Page 16: Parameter Standarization Guideline

16

Key Programs:Optimized Core Network in handling the Handover processWithin its radio coverage and enhance core Network retainability in handling conversation call.

Key Indicator:• Maintain and Improve HOSR, • Maintain and Improve CCR

Descriptions:

the supervision timer value for the intra MSC handover completion in the anchor or non-anchor MSC. The time supervision period is started with the sending of a handover command to the source BSC and is stopped with the reception of a handover complete from the target BSC.

MSC TIMER > T8 BSSMAP + T_ESTGUARD + T_REESTABLISH + T_REESTGUARD

Benefit :• Improve Network Performance & Network Productivity• Reduce Intra MSC Handover Failure due to timer expiry• Avoid Inappropriate timer setting in both Core and Radio

T8 Timer Standardization

T8 Timer Standardization

KPI monitoring and Audit Initiation

Re-audit and Update Meeting FNI and Roll Out Evaluation &

Monitoring

Jan-2014 Feb-2014 Mar-2014 Apr-2015

Page 17: Parameter Standarization Guideline

17

Key Programs:Optimized Core Network in handling the Speech Quality

Key Indicator:

• Better MOS

Descriptions:

The Core/Radio parameter that provide the preference codec to be used whenever a call in progress. The good codec parameter setting will lead to good speech quality and end user perceived. The speech quality is measured in Mean Opinion Score (MOS)

Benefit :• Improve Network Performance & Network Productivity• Reduce Bad Voice Quality• Avoid Inappropriate Codec setting in both Core and Radio

Codec Parameter Standardization

Codec Parameter Standardization

KPI monitoring and Audit Initiation

Re-audit and Update Meeting FNI and Roll Out Evaluation &

Monitoring

Jan-2014 Feb-2014 Mar-2014 Apr-2015

Page 18: Parameter Standarization Guideline

18 Network Quality Management

Parameter Standardization

KPI Scanning

Parameter Audit

Analysis & AssessmentAction Plan

Evaluation Improvement

•Define “The Pros” and “The Cons”•Vendor Consultation•Changes Possibilities (Basic or

additional Feature)

• Define Parameter related to KPI and PI

• Audit All involved Node (Core – Radio – Transport)

• KPI and PI in node level Scanning based on Threshold (SCR<90%,CCR<95%,PDP SR<97%,PDP CR<96%)

• Achievement Evaluation•Recommendation for Next Roll

out

•Define Action plan based on analysis & assessment• Job Matrix responsibilities•Fallback Scenarios

Parameter Audit & Standardization

Page 19: Parameter Standarization Guideline

19 Network Quality Management

Parameter Change Flow Chart in Core

Page 20: Parameter Standarization Guideline

20 Network Quality Management

Parameter Change Flow Chart in RAN

Parameter Change Flow Chart

Page 21: Parameter Standarization Guideline

21 Network Quality Management

21