Suggested LOGO

for customer

Enable PRACH frequency-

domain position adaptation
4G Strategic
TRIAL & ROLL OUT
(Note: The selectable part of the title can be update/patch installation/rectification
according to the actual implementation scenario. )

Prepared Bruri Date: 13 May 2017

by:
13 May 2017
Reviewed Muh. Ridwan Date:
by:
13 May 2017
Approved Zhouyuliang Date:
by:
 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....................................................................5
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................................................................................7
3 Operation Steps for Change.................................................................................8
3.1 Change Steps............................................................................................8
3.1.1 Overall Description......................................................................................8
3.1.2 Operation Steps for Change.......................................................................8
3.2 Test and Verification...................................................................................9
3.3 Solution for Changeback In the Case of Failure........................................9
3.3.1 Definition of Change Failure.......................................................................9
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..........................................................................10
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...............................................................................12
4.4 Training....................................................................................................12
4.5 Matters Needing Attention.......................................................................12

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

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

1 Description of Change
1.1 Description of Site

Version Number
V100R011C10SPC260 1637 eNodeBs

The Connection Using U2000_Client_R16C10SPC250

1.2 Purpose

Change scenario: RF Optimization

Change solution category-1: Enable PRACH frequency-domain
position adaptation TRIAL
Change scope-1: 5 eNodeBs
Change time-1: 23:00, 05 23, 2017 to 01:00 05 24, 2017
Change solution category-2: Enable PRACH frequency-domain
position adaptation ROLL OUT
Change scope-2: 1632 eNodeBs
Change time-2: 23:00, 06 01, 2017 to 01:00 06 02, 2017

1.3 Description of Change and Change Influence

When the PRACH frequency-domain position is determined based on the

maximum number of RBs used by the PUCCH, the PRACH frequency-domain
position equals half of the maximum number of RBs used by the PUCCH, as shown
in Figure 4-5. When a small number of UEs exist and the number of RBs used by the

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

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

PUCCH is less than the upper limit, PUSCH resources are divided into two parts and
cannot be used as a whole by a single UE. In this situation, the eNodeB adjusts the
PRACH frequency-domain position based on the number of RBs used by the
PUCCH so that the PRACH is adjacent to the PUCCH located at the low frequency,
thereby preventing the waste of PUSCH RB resources.

2 Preparations for Change

2.1 Composition of Change Team and Responsibility of Team Members

2.2.1 Change Team of Huawei CompanyCustomer

N
G

2.2.2 Huawei On-site Change Team

Name Responsibility Telephone No.

Muh. Ridwan Chief commander 081364631499
Bruri RNO 082280409525
Andi OSS Chief 08111779315
Jacky Anugra Ass RNO 082168067073
Dian OSS 081322216660

2.2 Check of Equipment Running

Check Item Result Check Item

Alarm Normal Alarm
KPI Normal KPI

KPI.xlsx Alarm.csv

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

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

2.3 Change Risks and Countermeasures

Assess the risks that may be encountered during the change and provide corresponding
countermeasures.
No. Risk Description Possibilit Impact Countermeasure
y (High/Mi
(High/Mi ddle/Lo
ddle/Low w)
)
Abnormal issue Low Low Follow the execution FAQ to
happened during trouble shooting, if cannot solve
1
execution to block within 30 minutes ,contact with
execution operation GTAC Hotline.
Traffic abnormal or Low Low Contact with GTAC hotline
main KPI counter
2
degraded after
execution
Low Low Spare parts shall be prepared
3 Hardware fault for boards that damage easily
before version upgrade;

2.4 Check before Change

No. Preparations Before Change Owner Completion Date

1 Solution for change back in the case Bruri/Muh.Ridwan
20170523
of failure
2 Related data backup Andi 1 day before parameter change
3 Readiness of mobile phone test card The customer if
1 day before parameter change
needed
4 Readiness of change test engineer The customer if
3 hours before parameter change
needed
5 Readiness of relevant equipment BSS Team
3 hours before parameter change
maintenance engineer
6 Readiness of support & guarantee team GTAC 3 hours before parameter change
7 Readiness of remote log-in environment BSS Team 1 day before parameter change

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

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

3 Operation Steps for Change

3.1 Change Steps

3.1.1 Overall Description

The whole parameter change activity will be done by Huawei engineer Andi as OSS
Centralize Leader
NE Name Time Execution Date Execution
5 eNodeBs
23.05 - 23.10 May 23,2017
(TRIAL)
1632 eNodeBs
23.05 - 23.10 June 02,2017
(RO)

3.1.2 Operation Steps for Change

No Change Step Implementation Time(hourly Time(hourly

. Person level) TRIAL level) Roll Out
1 Backup data for MML, Dian
00:00 to 06:00, 00:00 to 06:00,
DB,ALARM and 7days
23 17, 2017 06 02, 2017
measurement
2 Andi 23:00, 05 17, 23:00, 05 22,
Implementation 2017 to 01:00 2017 to 01:00
23 17, 2017 06 02, 2017
3 KPI Monitor Performance Dikal 01:00 to 05:00, 01:00 to 05:00,
3 hours 23 17, 2017 06 02, 2017
4 Andi 02:00 to 03:00, 02:00 to 03:00,
Fallback if KPI degrade
23 17, 2017 06 02, 2017
5 Everything goes well and Bruri 05:00 to 06:00, 05:00 to 06:00,
send Email to customer 23 17, 2017 06 02, 2017

Parameter Change based on the Script as bellow attached:

CR Enable PRACH
frequency-domain position adaptation 13052017.xlsb

3.2 Test and Verification

No. Operation Operation Method Owne Time Time

Item r (TRIAL) (Roll Out)
Technical support website: Technical support hotline: Page 6 of 10
http://support.huawei.com Fax:
 Implementation Solution for Change

1 Parameters Opertation Log Check based on Jacky 23:00, 05 23:00, 05

confirm script anugr 17, 2017 22, 2017
a to 01:00 to 01:00
23 17, 2017 05 06 02,
2017
2 eNodeB cell DSP CELL:; All the cell are Dian 01:00 to 01:00 to
status normal 02:00, 23 02:00, 06
17, 2017 02, 2017
3 Alarm report LST ALMAF:; no new alarm. Dian 01:00 to 01:00 to
02:00, 23 02:00, 06
17, 2017 02, 2017

4 KPI monitoring Monitoring the KPI, ERAB/CDR Jacky 01:00 to 01:00 to

the base KPI is normal. anugr 05:00, 23 05:00, 06
L.Traffic.ActiveUser.Avg 17, 2017 02, 2017
a
5 Service test UE connected to network and do Jacky 01:00 to 01:00 to
web browsing, the service is anugr 02:00, 23 02:00, 06
normal.
a 17, 2017 02, 2017

3.3 Solution for Changeback In the Case of Failure

3.3.1 Definition of Change Failure

A change failure shall be recognized by HUAWEI TD (MR.muh ridwan, ID 273425) and

customer PM (MR. Gathut).If the following major problems cannot be resolved before 4:00
a.m. (within the stipulated period of time) and back-off operations shall be finished.
(1) Main KPI degrade very badly till 10%

3.3.2 Overall Description of Changeback

Use the remote client tool to do the rollback

Step Time Required

Performing the rollback 2050 minutes

Verifying the rollback 3060 minutes

3.3.3 Information Collection Before Changeback

MML, OPT LOG, ALARM and DB file for after upgrade

3.3.4 Changeback Steps

Technical support website: Technical support hotline: Page 7 of 10
http://support.huawei.com Fax:
 Implementation Solution for Change

No. Change back Operation Implementation Time(hourly

Step Person level)
1 MML,OPT LOG,ALARM Dian 4:00
and DB file for after
Data backup
upgrade

2 Perform the Andi 4:30

remote client to Executed fallback script
rollback

3.3.5 Equipment Status Check

N/A . This parameter changes will not impact to the Equipment.

3.3.6 Tests After Changeback

No. Operation Item Operation Method Owner Time

1 Monitor KPI Monitor KPI Jacky Anugra 04.00
L.Traffic.ActiveUser.Avg
For 3 Hour 07.00

3.3.7 Changeback Risk Analysis

Possibility Impact Countermeasure

No. Risk Description (High/Midd (High/Midd
le/Low) le/Low)
NEs Checklist & Middl middle 4G-3G-2G Side Check Items
Network Problems e
1 Avoid Issue &
Precautions
Checking

Technical support website: Technical support hotline: Page 8 of 10

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

High High 1. Suggest open CS/PS side

equipment instantaneous
high traffic strike flow control
function.
2.if Instantaneous traffic
Instantaneous traffic strike continue exceed 15
2 strike impact on main minutes , deactivate some
relevant NEs sites or forbid some SPU
board;
3.if Instantaneous traffic
strike continue exceed 30
minutes ,contact with GTAC
hotline
Traffic abnormal or High High Contact with GTAC hotline
4 main KPI counter
degraded
High High 1. If the remote connection
cannot restore within 30
minutes, Standby engineer in
Remote Connection NOC continue rollback
6 Abnormal during emergently.
rollback 2. If NOC remote connection
abnormal, notice customer
troubleshooting and contact
GTAC.
High High Follow the version upgrade
Abnormal issue
FAQ to troubleshooting, if
happened during
7 cannot solve within 30
version upgrade
minutes, contact with GTAC
rollback
Hotline.

3.4 Change of Spare Parts and Emergency Workstation

N/A. BSS Team L1 is responsible for the spare parts if needed

Technical support website: Technical support hotline: Page 9 of 10

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

4 Work After Change

4.1 Observation

We will compare the KPI analysis before and after the changes, we
also will focused on the main KPI CSSR < 95 %, SDR > 2% & CSFB SR
< 95% to make sure everything stay on the management threshold.
No. Operation Items: Operation method Owner Time
1 Keep monitoring with Alarm, Through U2000 Jacky 06:00
BSC KPIs and running status
check

4.2 Provision of Materials

Clarify owners, provision time, and materials that shall be provided.

4.3 Provision of Software

Clarify owners, provision time, and software and disks that shall be provided.

4.4 Training

Clarify owners for and time of providing training on the changed parts for customers.

4.5 Matters Needing Attention

After completion of the change, notify customers of modifying the used account and
password and returning SIM cards and related tools.

Technical support website: Technical support hotline: Page 10 of 10

http://support.huawei.com Fax: