Suggested LOGO

for customer

MOP CHANGE
RTN QOS CONFIGURATION

Prepared by: Ryan Arrasuli Date: 26 April 2021

Reviewed by: Dimas Aryo Baskoro Date: 27 April 2021

Approved by: Ari Wijayanto Date: 27 April 2021

Suggested LOGO
for customer
 Implementation Solution for Change

Contents

1 Description of Change 3
1.1 Description of Site 3
1.2 Purpose 3
1.3 Description of Change and Change Influence 3
2 Preparations for Change 4
2.1 Change Period 4
2.2 Composition of Change Team and Responsibility of Team Members 4
2.2.1 Change Team of XX Company 4
2.2.2 Huawei On-site Change Team 4
2.2.3 Huawei Support & Guarantee Team 5
2.3 Check of Equipment Running 5
2.4 Change Risks and Countermeasures 6
2.5 Check Before Change 6
3 Operation Steps for Change 7
3.1 Change Steps 7
3.1.1 Overall Description 7
3.1.2 Operation Steps for Change 8
3.2 Test and Verification 9
3.3 Solution for Changeback In the Case of Failure 10
3.3.1 Definition of Change Failure 10
3.3.2 Overall Description of Changeback 10
3.3.3 Information Collection Before Changeback 10
3.3.4 Changeback Steps 10
3.3.5 Equipment Status Check 11
3.3.6 Tests After Changeback 11
3.3.7 Changeback Risk Analysis 11
3.4 Change of Spare Parts and Emergency Workstation 11
4 Work After Change 11
4.1 Observation 11
4.2 Provision of Materials 11
4.3 Provision of Software 11
4.4 Training 12

Page 3 of 13
 Implementation Solution for Change

4.5 Matters Needing Attention 12

1 Description of Change
1.1 Description of Site

This document is to be used as reference to configure QOS parameter on RTN

Microwave series 910, 950, 950A, 980, 980L. Due to the customer request for
combine all the QCI in 4G subscriber (XL & AXIS) by using 85% of weight on PHB
AF3 and in 3G subcriber (XL & AXIS) by using 5% of weight on AF1 in the LRAN
transport WRR distribution for Central Area (West and Central Java) as the first trial
area chosen.

1.2 Purpose and Requirements

Objective to have more bigger portion weighting of 4G traffic from previously 60% to
85% and lesser portion weighting of 3G traffic from previously 30% to 5%
Note : this weighting scheme is only running when the link is having congestion.
E2E Qos setting required to handle networks service quality .
Requirements are:

1. Ensuring that the server is good performance

2. Maintaining nms connectivity, Networks must be available during activity,
otherwise it cannot perform
3. NE database.
4. NCE client

1.3 Description of Change and Change Influence

Change existing Weighting (60:30) to new Weighting (85:5) parameter , base on plan
and customer request

Preparations for Change

1.4 Change Period

The change period is from 28 April 2021 – 05 May 2021

Page 4 of 13
 Implementation Solution for Change

1.5 Composition of Change Team and Responsibility of Team Members

2.2.1 Change Team of XL Company

Name Responsibility Telephone No.

Arif Rahman Ali Chief commander +6281806116667
Dimas Aryo Baskoro Owner for RTN product change +6287782727281
BO Transport Coordination with other NEs +6281806116667
BO Transport Test owner +6281806116667
Communication on handling +6287782727281
Dimas Aryo Baskoro
customer complaints
2.2.2 Huawei On-site Change Team

Name Responsibility Telephone No.

N/A

2.2.3 Huawei Support & Guarantee Team

Name Responsibility Telephone No.

Supporting overall +62818111767
Ryan Arrasuli coordination as the
technical expert
Dimas Aryo Product support contact +6287782727281
Baskoro person

1.6 Check of Equipment Running

Page 5 of 13
 Implementation Solution for Change

1). NCE server is running fine and normal

2). No other operation will be done on that NE at same time
3).Check the NE

1.7 Change Risks and Countermeasures

1). No any impact on current network

2). Monitoring will be available during execution

Key points of network adjustment (including network architecture and configuration parameter
adjustment):
1.RTN qos setting
2.network service quality

No. Risk Description Possibility Impact Countermeasure

(High/Middle/ (High/Middl
Low) e/Low)
1 Data backup Low Low No impact service
2 Impact on NEs Low Low No impact service
Risk in change Low Low No impact service
3
duration
4

1.8 Check Before Change

No. Preparations Before Change Owner Completion Date

1 Check Environment BO Trans 28 April 2021
2 Backup NE data BO Trans 28 April 2021
3 Test nms connection BO Trans 28 April 2021

Page 6 of 13
 Implementation Solution for Change

4 Verify account login BO Trans 28 April 2021

5 Verify remote login BO Trans 28 April 2021

2 Operation Steps for Change

2.1 Change Steps

2.1.1 Overall Description

N Date & Activities Duration Contact Remarks

o Time Name(Company)
dd/mm/ – 01X-xxxxxxx
yy

1 Day 1-2 Prepare data base NE Name 30 min BO Trans

and ID
2 Day 1-2 Perform QoS template and 15 min BO Trans
setting

3 Day 1-2 Synchronize NE Data 15 min BO Trans

Fallback Plan (if needed)

4 Day Rollback to Existing Qos 60 min BO Trans

1-10

2.1.2 Operation Steps for Change

1. Use WRR Profile: QOS_4G_3G_85_05_CVLAN_2021 Global Template to be

downloaded to NE. Valid for the following NE: RTN (RTN905, RTN910, RTN950,
RTN950A, RTN980 and RTN980L)

Page 7 of 13
Implementation Solution for Change

Page 8 of 13
 Implementation Solution for Change

Then Klik OK

2. Use Port Profile: QOS_4G_3G_85_05_CVLAN_2021 Global Template to be

downloaded to NE and port. Valid for the following NE: RTN (RTN905, RTN910,
RTN950, RTN950A, RTN980 and RTN980L)

Page 9 of 13
 Implementation Solution for Change

For downloading port profile to NE, please specify base on RTN Type
910/950/950A/980/980L) then klik download to NE and klik OK. All available NE type
should be downloaded,.and selected base on area (specific area should be chosen
due to huge amount of task execution if we choose all area at the same time)

For applying port profile to NE port, please specify base on RTN Type
910/950/950A/980/980L) then klik download to port and klik OK. All available NE
port should be downloaded. and selected base on area (specific area should be
chosen due to huge amount of task execution if we choose all area at the same time)

Page 10 of 13
 Implementation Solution for Change

2.2 Test and Verification

Service checking ad verification

1. Login to NE by NCE client

2. Enter to NE exlorer and check mandatory requirements (config, service etc)

3. For service make sure all MAC address in register VLAN are avalaible also BTS
mac address

4. Enter RMON performance and check TX and RX data statistic are normal.

5. Confirm BTS service to NOC

2.3 Solution for Changeback In the Case of Failure

2.3.1 Definition of Change Failure

A change failure shall be recognized if the activity fails

2.3.2 Overall Description of Changeback

Verify qos setting on NE configured

2.3.3 Information Collection Before Changeback

NE database

2.3.4 Changeback Steps

-Right click related NE-choose NE explorer

-Click qos setting

Page 11 of 13
 Implementation Solution for Change

2.3.5 Equipment Status Check

Synchronize NE data

2.3.6 Tests after Changeback

Verify NE in NCE server

2.3.7 Change back Risk Analysis

Need RND support

2.4 Change of Spare Parts and Emergency Workstation

No spare part change,because the activity only for NE renaming

3 Work after change

3.1 Observation

Engineer will observe the report by NCE server.

3.2 Provision of Materials

No material are required, activity only change Ne name

3.3 Provision of Software

The activity only for qos setting,existing software are support

3.4 Training

Training are not available

Page 12 of 13
 Implementation Solution for Change

3.5 Matters Needing Attention

After completion of the change, notify customer number of NE

already done

Page 13 of 13