0% found this document useful (0 votes)
120 views7 pages

MOP 2G Signalling Robustness Parameter Tuning

This document provides an implementation solution for changing signalling robustness parameters on BSC BBTG1 and BSRG03 in Jabo. The change aims to reduce call drops and improve retainability. It will take place from April 23rd to 25th, 2019. The on-site change team will back up data, check equipment status, run scripts to implement the change, monitor KPIs, and have rollback plans in case of failures. Risks are assessed as low with countermeasures like fallback in case of degradation.

Uploaded by

Miqdad Dwi Rezki
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
120 views7 pages

MOP 2G Signalling Robustness Parameter Tuning

This document provides an implementation solution for changing signalling robustness parameters on BSC BBTG1 and BSRG03 in Jabo. The change aims to reduce call drops and improve retainability. It will take place from April 23rd to 25th, 2019. The on-site change team will back up data, check equipment status, run scripts to implement the change, monitor KPIs, and have rollback plans in case of failures. Risks are assessed as low with countermeasures like fallback in case of degradation.

Uploaded by

Miqdad Dwi Rezki
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

MOP XL HS Project

Signalling Robustness Parameter


Tuning BSC BBTG1 and BSRG03
Jabo

Prepared by: DATE:

Reviewed by: DATE:

Approved by: DATE:


Implementation Solution for Change

Contents
1 Description of Change....................................................................................................... 3

1.1 Description of Site................................................................................................. 3

1.2 Purpose and Requirements .................................................................................... 3

2 Preparations for Change .................................................................................................... 4

2.1 Change Period ............................................................................................................. 4

2.2 Composition of Change Team............................................................................... 4

2.2.1 Huawei On Site Change Team .............................................................................. 4

2.3 Check Equipment Running ................................................................................... 4

2.4 Change Risks and Countermeasures ..................................................................... 5

2.5 Check Before Change ........................................................................................... 5

3 Operation Steps for Change .............................................................................................. 6

3.1 Change Steps ......................................................................................................... 6

3.1.1 Overall Description ............................................................................................... 6

3.1.2 Operation Steps for Change ............................... Error! Bookmark not defined.

3.1.3 Test and Verification ............................................ Error! Bookmark not defined.

3.2 Solution for Change-back In the Case of Failure .................................................. 6

3.2.1 Definition of Change Failure ............................................................................... 6

3.2.2 Change back Steps .............................................................................................. 7

3.2.3 Equipment Status Check ..................................................................................... 7

3.2.4 Tests after Change-back ..................................................................................... 7

3.2.5 Change-back Risk Analysis ................................................................................ 7

4 Work After Change ........................................................................................................... 7

4.1 Observation ........................................................................................................... 7

Technical support website: Technical support hotline: Page 2 of 7


http://support.huawei.com Fax:
Implementation Solution for Change

1 Description of Change

1.1 Description of Site

1.2 Purpose and Requirements


Reduce Call Drop and Improve Retainability.

Change solution category: Cell Data configuration.

Change scope: 2 BSC BBTG1 and BSSRG03 Jabo


Change time: 23-April 2019 23:00 to – 25 April 2019 11:00

Change Affection:

Relative NE Relative Impact


Cell No service impact during execution.

Technical support website: Technical support hotline: Page 3 of 7


http://support.huawei.com Fax:
Implementation Solution for Change

Preparations for Change


2.1 Change Period
The change period is from 10:00 hours, 23.04.2019 to 11:00 25.04.2019 Indonesia Local

time (GMT+7).

Operation Time could be changed according to customer schedule.


Operational Window – 23-25 April 2019
Task Start time End time Date
Running Script 23:00 00:00 23-April 2019
Check execution logs 23:00 00:00 23-April 2019
Check cell status 01:00 30:00 24-April 2019
KPI checking (Traffic, SD Cong, Perceived Cong) 09:00 10:00 24-April 2019
Roll-Back (in case of Failure) 11:00 12:00 24-April 2019

1.2 Composition of Change Team

1.2.1 Huawei On Site Change Team


No Name Email Phone

1 OSS Center [email protected]

2 Fitri Cahyaningtyas [email protected] 081314228875

3 Simon Sianturi [email protected] 085261156110

4 Fadhil Hadi [email protected] 081267569661/087792497251

5 Juniar [email protected] 087882248284

1.3 Check Equipment Running


Current alarm logs will be analyzed before the change as well KPI (CS & PS) will be checked.

The owner of this operation will execute the analysis. Equipment running checklist

Items Result Whether will impact operation remark

Alarm analysis Normal No

KPI analysis (Traffic, Call Drops, Normal No

HOSR, Accessibility KPIs)

Cell & TRX Status Normal No

Technical support website: Technical support hotline: Page 4 of 7


http://support.huawei.com Fax:
Implementation Solution for Change

1.4 Change Risks and Countermeasures


No Service interruption during change.

No. Risk Description Possibility Impact Countermeasure

1 Accessibility Degrada Low Low If significant degradation, will

tion fallback

Remote Access is not available. But we would have on site Team for Troubleshooting /
Fallback if needed

1.5 Check Before Change


No. Preparations Before Change Owner Completion Date

1 Data backup Fitri 23-April 2019 at 09:30

2 Collect Alarms, Cell status, TRX Fitri 24-April 2019 at 09:30


Status

Technical support website: Technical support hotline: Page 5 of 7


http://support.huawei.com Fax:
Implementation Solution for Change

2 Operation Steps for Change


2.1 Change Steps
2.1.1 Overall Description

The overall operation steps will be as follows:

- Back dump, alarm before execution

- Running Parameter

- Back dump, alarm after execution

- KPI monitoring after execution

- Roll Back in case of abnormal

HOW TO RUNNING SCRIPT IN BSC


1. Prepare Script
2. Open terminal emulator
3. Start logging
4. Log in to BSC via winfiol (eaw <BSC>)
5. Copy Script 1, paste into terminal emulator <BSC>, confirm execution
6. Copy Script 2, paste into terminal emulator <BSC>, confirm execution
7. Quit from <BSC>
8. Continue to execute other BSC (start from no. 4 again)
For execution script, please find attached files below:

BO_NCCR_R3_2G
Signalling Robustness Parameter Tuning_Dede_BBTG1_BSRG03_20190422.xlsx

2.2 Solution for Change-back In the Case of Failure


2.2.1 Definition of Change Failure

The change fails if one of the following issues cannot be resolved before 05:00 PM.

Thus the change-back must be operated. will decide whether need change-back.

 Have traffic degradation about10% after execution

 Have KPI degradation about 10% after execution.

 Have Service Impact about 10 sites after execution

 Have Complain from customer

Technical support website: Technical support hotline: Page 6 of 7


http://support.huawei.com Fax:
Implementation Solution for Change

2.2.2 Change back Steps


Rollback process
For Rollback Scripts, please see in attached file.

BO_NCCR_R3_2G
Signalling Robustness Parameter Tuning_Dede_BBTG1_BSRG03_20190422.xlsx

2.2.3 Equipment Status Check


No. Operation Item Operation Method Owner Time
1. Cell status Same as before Dede 15:00-16:00
2. Check Performance Accessibility, Retainability, Mobility Dede 15:00 onwards

2.2.4 Tests after Change-back

Alarms, Database, and KPI monitoring will be checked as well by field team.
No. Operation Item Operation Method Owner Time
1. Cell status Same as before Dede 15:00-16:00
2. Check Performance Accessibility, Retainability, Mobility Dede 15:00 onwards

2.2.5 Change-back Risk Analysis

No risk after change back, since parameter setting is set back to original value.

3 Work After Change


3.1 Observation

No. Operation Item Expected result Period Owner


1 Alarm and Hardware status No new alarm, If there have 11:00AM- 12:00AM Fitri (Tel.

check new alarm it should not 081314228875)

affect service

2 KPI Check (Call drop ratio, Should be 03:00PM- 04:00PM Dede Sujana (Tel.

HOSR, CSSR) maintained without 081999542245)

significant degradation

Technical support website: Technical support hotline: Page 7 of 7


http://support.huawei.com Fax:

You might also like