BSC6900-6910 UMTS License Renew MOP

Suggested LOGO
for customer
Zain Company
Implementation
Solution for BSC6900
and 6910 UMTS
License Renew
(Note: The selectable part of the title can be update/patch installation/rectification
according to the actual implementation scenario. )

Suggested LOGO
for customer
Prepared by: Yasir Date: 7/11/2019

Y00410939
Reviewed by: Yasir Date: 7/11/2019

Y00410939
Approved by: Yasir Date: 7/11/2019

Y00410939
Implementation Solution for Change
Contents
1 Description of Change..........................................................................................3
1.1 Description of Site......................................................................................3
1.2 (Note: KCP1)Purpose and Requirements..................................................4
1.3 (Note: KCP2)Description of Change and Change Influence......................4
2 Preparations for Change.......................................................................................5
2.1 (Note: KCP3)Composition of Change Team and Responsibility of Team
Members 5
2.2.1 Change Team of XX Company.................................................................5
2.2.2 Huawei On-site Change Team.................................................................5
2.2.3 Huawei Support & Guarantee Team........................................................6
2.2 (Note: KCP4)Remote Access.....................................................................6
2.3 (Note: KCP5)Platform and Software Preparation......................................7
2.4 (Note: KCP6)Check of Equipment Running...............................................8
2.5 Change Risks and Countermeasures........................................................8
2.6 (Note: KCP7)Check Before Change..........................................................8
3 Operation Steps for Change...............................................................................10
3.1 Overall Description of Change Steps.......................................................10
3.2 (Note: KCP8)Operation Steps for Change...............................................10
3.3 (Note: KCP9)Test and Verification...........................................................11
3.4 Solution for Changeback In the Case of Failure......................................12
3.4.1 (Note: KCP10)Definition of Change Failure.............................................12
3.4.2 (Note: KCP11)Overall Description of Changeback..................................13
3.4.3 (Note: KCP11.1)Changeback Steps........................................................13
3.4.4 (Note: KCP11.2)Tests After Changeback................................................13
3.4.5 (Note: KCP11.3)Changeback Risk Analysis............................................14
3.5 Change of Spare Parts and Emergency Workstation..............................14
Technical support website: Technical support hotline: Page 3 of 20

http://support.huawei.com Fax:
4 (Note: KCP12)Work After Change......................................................................14
4.1 Observation..............................................................................................14
4.2 Other work...............................................................................................15
Filling Attention:
 The red font content with * is essential
 Normal font content is optional content, region/project can change
as per requirement
 The blue font content with under line is the description or example,
please delete these content when output the final version

1 Description of Change
1.1 Description of Site
Network
topology
diagram
Key features N/A
and
business
N/A
Related
business
amount
Key features License Activation in 10 BSC6900/BSC6910
and
business
Related
business License Activation in whole ZAIN network except
amount

1.2 (Note: KCP1)Purpose and Requirements
 The red font content with * is essential
 Change purpose*(essential)：problem resolution/version
sales/rectification/network performance optimization/ engineering network
adjustment
 Change time*(essential)：should mention time, e.g. yyyy-mm-dd hh:mm to
hh:mm
 the change time should avoid business peak hour, festival, large activity and
other change at the same time; if the change is separate to batches, change
time should describe separately
The MOP Prepared for BSC6910 UMTS LICENSE ACTIVATION

Change
V100R020C00SPC535 AND BSC6900 UMTS BSC6900
purpose*
V900R020C00SPC535
Change scope BSC6910/BSC6900 UMTS License Activation
Change time* 2020/04/05 00:00 to 06:00
1.3 (Note: KCP2)Description of Change and Change Influence
NE Info*(essential) ：Clearly describe change NEs, NE ID/name, quantity, version and patch
information
No. NE type* NE ID* QTY* Current version* Target version*
*
1 BSC690 BSC6900 3 V900R020C00SPC535 V900R020C00SPC535
0 UMTS
2 BSC691 BSC6910 7 V100R020C00SPC535 V100R020C00SPC535

0 UMTS
No. Related NE type Related NE ID Version

1 M2000 U2000 V200R018C10SPC250
Change Influence
Introduce new features, services, and functions related to the changed version or patch, and
specify the influences on users' daily operations such as data configuration and maintenance.
Specify if operations need to be finished on hardware to realize the change and if changes of
spare parts are needed, and state influences of the change on maintenance.
2 Preparations for Change
2.1 (Note: KCP3)Composition of Change Team and Responsibility of

Team Members
Change team preparation*（essential for high risk change）：
1. Whether the name and contact information of chief commander, key information owner,
Owner for xx product change, etc. from customer side is complete;
2. Whether the name and contact information of managers, product expert, change owner,
etc. from Huawei side is complete;
3. Whether the name and contact information of expert and PSE from Huawei support team is
complete;
4. Whether assigned on site owner for remote operation.
2.2.1 Change Team of ZAIN Company
Name Responsibility Telephone No.

Musa Chief commander +249912399613
Musa key information owner +249912399613

Musa Owner for BSC product change +249912399613

Musa Coordination with other NEs +249912399613
Musa Test owner +249912399613
Musa Charging verification owner +249912399613
Musa Network management test owner +249912399613
Musa Communication on handling customer +249912399613
complaints
Musa Onsite support +249912399613
2.2.2 Huawei On-site Change Team

Yasir +249912399639
Chief commander
00410939
Yasir +249912399639
Owner for License Activation
00410939
Yasir +249912399639
Expert for BSC product
00410939
Yasir +249912399639
Service test
00410939
Yasir +249912399639
Service verification
00410939
Yasir +249912399639
Onsite support
00410939
2.2.3 Huawei Support & Guarantee Team

Supporting overall +86 18583937181
GTAC
coordination as the
HOTLINE
technical expert
chenyan c00516642 +86 18583937181
GTAC WL
person C00516642

2.2 (Note: KCP4)Remote Access
Remote access is essential for medium and high risk change
If customer is not agree to access remotely, please clearly mention in this section,
and upload customer feedback file/email to IT system
Item Preparation status Owner

Remote access NO N/A
solution*
authorization*
test*
2.3 (Note: KCP5)Platform and Software Preparation
Platform and Software Preparation*(essential) ：Clearly describe the needed tools software,
material, backup communication, license, ect. and responsible owner.
Type Content Owner

Software Tools* N/A N/A
Material* N/A N/A
Communication N/A N/A
backup*
（essential for
high risk
change）
Version software BSC6900 V900R020C00SPC535 N/A
BSC6910 V100R020C00SPC535
License N/A
New License.rar
License
Test tools N/A N/A

Hardware N/A N/A
installation tools
2.4 (Note: KCP6)Check of Equipment Running
Check of Equipment Running*(essential)：Whether describe the equipment running
checking result, or the checking content and steps before operation, include but not limited to:
1. Check and analyze the network alarm, performance indicators, network KPIs, and
hardware operation status.
Clear the equipment alarms and obtain KPIs prior to the change. (KPIs prior to the cutover
must be obtained.)
For cutover, the checklist result must be provided.
2. Check whether there are scheduled tasks in the system (such as scheduled tasks of the
system, jobs executed by the database regularly, and scripts run periodically), and evaluate the
influences of these tasks on the normal change.
3. Confirm with the customer's maintenance department on whether there are operations on
surrounding parts at that night and whether they would affect the change. Attach special attention
to the customer's network and surrounding charging parts.
Check Item* Check result or steps*

alarm /check before operation; Can attach check result
KPI check before operation; Can attach check result
hardware operation check before operation; Can attach check result
status
Pass/Not Pass/check before operation; Can attach check
Timer
result
Pass/Not Pass/check before operation; Can attach check
…
result
2.5 Change Risks and Countermeasures

No. Risk Description Possibility Impact Countermeasure
(High/Middle/Low) (High/Middle/Low)
Low Low Contact GTAC

Data backup
Provide DB, License,
BKP DB, License, EXP
CFGMML, GCELL
1 CFGMML, DSP
status and alarms
GCELL, Alarm and NE
back up for further
backup
analysis
Impact on NEs High High Contact with GTAC
Effect service for NE, hotline or call
KPI performance will 02981770999
affected ( CSSR,
CS/PS traffic, Service

2
Drop Rate, Traffic
volume, User
Uplink/Downlink
Average Throughput
need to check (3%) )
Risk in change Low Low Contact with GTAC
3 duration hotline or call
Board don’t up 02981770999
2.6 (Note: KCP7)Check Before Change
Check Before Change*(essential for high risk change) ：Whether describe the required
checking items, owner and finish time before change, include but not limited to:
1.Changeback solution and confirmation from customer
2.Verification result of network change solution and changeback solution

3.Preparation of spare parts,and contingency plan without spare part
4.Collecting and uploading of product information for emergency recovery and location
5.Preparation checking for Site entry permission, remote access prepare result,data backup,
person, tools and material
No. Preparations Before Change Owner Completion Date

1 Change back solution has been Yasir Finish before
prepared, confirmed and authorized by 00410939 change
customer (essential for high risk change) *

2 Change solution and change back Yasir Finish before
solution have been verified (essential for 00410939 change
high risk change) *

3 Spare parts are ready for use within x N/A Finish before
minutes; if no spare part, contingency change
plan is available (essential for high risk
change) *
4 As per change scenario, collect data for Yasir
recovery following <XX product data 00410939

Finish 4 hours
collection guide>, and upload to
before change
iCare/eTrance (essential for high risk
change) *
5 Confirm has perform main/standby N/A Finish before
switchover test change

6 Readiness of getting access permission to N/A Finish before
the site change

7 Readiness of remote log-in environment N/A Finish 4 hours
before change
8 Confirm change risks and emergency N/A Finish before
measures change
9 Confirm data and configuration are backup Yasir Finish before
00410939 change
10 Confirm network performance is tested Yasir Finish before

and recorded 00410939 change

11 Readiness of change test personnel Yasir Finish before
00410939 change
12 Readiness of relevant equipment N/A Finish before
maintenance personnel change

13 Readiness of support & guarantee team Yasir Finish before
00410939 change
14 Readiness of mobile phone test card Yasir Finish before
00410939 change
15 Readiness of boards, tools, and Yasir Finish before
instruments 00410939 change
3 Operation Steps for Change
3.1 Overall Description of Change Steps
Specify please fill into below table must follow applied operation window, and if here
filled, please don't forget to fill icare system entrance to WFM-CS Task as below
information
No. Main steps Operation time

1 Preparation/planned Operation Action Start 22:00-00:00
Time
2 Operation/Implementation End Time 00:00-01:30
3 Verification/Verification End Time 01:30-03:00
4 Rollback/Planned Rolling-back Start Time 03:00-04:00
5 Complete/Planned Operation Action End Time 06:00
//icare system entrance to WFM-CS Task information //

3.2 (Note: KCP8)Operation Steps for Change
Operation Steps for Change*(essential):
1. Clarify the owner for each step of operation, the estimated start and end time, and the
basis for judging the success. Specify measures for handling emergencies that may happen during
the change, which shall be implemented in batch if there are a large number of involved sites.
2. Operation steps are reasonable and complete, and match with live network equipment and
target version or patch.
3. The key technical points specified in work instructions for each product are reviewed
(second-line PSE).
Specify feedback channels and handling owners for the problems that may emerge
during the change to ensure that the problems can be reported to all relevant personnel
in time. (The specific operation steps must be based on the related technical instructions
of transformation operation. If there is any customized step, it is required to inform the
technical reviewer about risk assessment conduction).
Operation
No. Operation Method Owner Time
Item
U2000: Backup Current
1 Alarm backup Yasir 00410939 23:15-23:30
alarm
Configuration U2000: Backup CFGMML, Yasir
2 23:30-23:45
backup BKPDB, License file 00410939
3 License U2000: NE file transfer Yasir 00:00-01:30
activation àLicense upload 00410939

MML: CHK DATA2LIC
MML: ACT LICENSE

Feature Yasir
4 MML: DSP LICUSED 01:35-02:00
Check 00410939
Test Call Yasir
5 DT by on site team 01:30-02:00
Onsite 00410939
3.3 (Note: KCP9)Test and Verification
Test and Verification*(essential):
Refer to target of this change, the test solution should include:
1. Verify whether achieve the target of this change
2. Define the test content as per scenario, e.g.: basic service, business verify for VIP
area/user, abnormal alarm, KPI change before and after change (define the name of KPI), new
features, the existing fault, charging and network management after change, etc.
3. test owner and planned time
Describe how to conduct the test during the change in details, and clarify owners for test
items and specific test contents. After the test, record details of the test process and
submit the results to the billing center for charging confirmation. Tests shall cover the
following aspects:
1. Basic services (of this site and between sites) are normal.
2. New functions and new features
3. Original defects are corrected?
4. Charging verification and network management verification after the change;
specifying owners for providing the report
5.
No. * Test Item* Operation Method* Owner* Time*

1 CELL Check the cells up or not Yasir 10 m

Status 00410939
2 KPI CSSR/PSSR Yasir After

Status
00410939 2 hours
3.4 Solution for Changeback In the Case of Failure
3.4.1 (Note: KCP10)Definition of Change Failure
Definition of Change Failure*(essential): Whether clearly defined change back time, decision
maker and Change back condition
Define what is a change failure and who can recognize a change failure (negotiate with
the user before the change to determine this part).
Changeback
4:00
time*
Changeback
Yasir 00410939
decision maker*
1. Did not finish operation within the solution planned time
2. The dial test shows that calls cannot be made through a
certain office route.
3. Charging amount is wrong.
4. A lot of users fail to make or receive calls.

Changeback
condition 5. One-way audio in a large area
6. Frequent breakdown (degraded Traffic,CSSR,PSSR)
7. Business effecting range is over the planned
range(HSDPA Users)
3.4.2 (Note: KCP11)Overall Description of Changeback
Briefly describe the changeback in an overall manner. If here not related change back,

please remark Reason and fill not related..
3.4.3 (Note: KCP11.1)Changeback Steps
Changeback Steps*(essential): The requirement is the same as "operation steps for change"
1. Clarify the owner for each step of operation, the estimated start and end time, and the basis
for judging the success. Specify measures for handling emergencies that may happen during the
change, which shall be implemented in batch if there are a large number of involved sites.
2. Operation steps are reasonable and complete, and match with live network equipment and
target version or patch.
3. The key technical points specified in work instructions for each product are reviewed
(second-line PSE).
Describe changeback steps in details, clarify owners, and specify the time period needed
for completing each step.
No. Changeback Steps* Operation Onwer* Time
* content* *
1 Information collection before Yasir 4:00
changeback 00410939
2 Yasir 4:00
Activate the old license
00410939
3 Yasir 4:00
Check cell status
00410939
4
5
3.4.4 (Note: KCP11.2)Tests After Changeback
Tests after Change back*(essential): Describe the test content after change back, and clearly
define test owner. Estamate the business effecting range and duration of change back solution by

test.
Describe the tests that shall be conducted after changeback and clarify test owners.
No. * Test Item* Operation Method* Owner* Time*

1 Call Yasir 6:00
test 00410939
2
3.4.5 (Note: KCP11.3)Changeback Risk Analysis
Changeback Risk Analysis*(essential): Analysis the risk of change back, and provide
Countermeasure. If there is also changeback failure risk, what is the contingency plan for such
condition
Analyze the risks that may be brought by changeback, and provide corresponding
countermeasures.
No. Main Issues Possibility Impact Countermeasure
and Risks (High/Middle/ (High/Middl
Description Low) e/Low)

Changeback Low High Perform XX
1
failure contingency plan
2
3.5 Change of Spare Parts and Emergency Workstation
Determine the time, and clarify owners for the change of spare parts and emergency
workstation. The change of spare parts and emergency workstation shall be finished
within one week after successful change.

4 Work After Change
4.1 (Note: KCP12)Observation
Observation*(essential): 1. The observation period after the change is specified and proved to
be compliant with requirements. (Generally, the heavy traffic period at morning and night shall be
covered, and specific topology/features and requirements of the product shall also be considered.)
2. The observation owners and work content are specified.
3. If charging conversion is involved by the operation, check whether the charging bill is
normal regularly within a charging period. Compare with and analyze the charging bill before the
operation to find differences.
Consider effected business and function of this operation, and refer the product
guidance/customer requirement, set specific KPI, alarm, monitor items, etc.
Specify owners for maintenance during the equipment observation period after the
change and state work contents.
No. Observati Observation

Observation time* Owner*
on Item* method*
1 KPI Compare the 6:00 Yasir 00410939
KPI with same
time of last
week or last
month for
reference
2 Alarm 6:00 Yasir 00410939
…
4.2 Other work
Clarify owners, provision time, and materials that shall be provided.
No. Work content Owner

1 Provide material N/A
2 Provide software N/A
3 Trainning N/A

4 Notify customers of modifying the used account and N/A

password
5 Returning SIM cards and related tools N/A N/A
… … N/A


BSC6900-6910 UMTS License Renew MOP

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

BSC6900-6910 UMTS License Renew MOP

Hochgeladen von

Copyright:

Verfügbare Formate

Suggested LOGO

Solution for BSC6900

and 6910 UMTS

according to the actual implementation scenario. )

Prepared by: Yasir Date: 7/11/2019

Reviewed by: Yasir Date: 7/11/2019

Approved by: Yasir Date: 7/11/2019

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

1.2 (Note: KCP1)Purpose and Requirements..................................................4

1.3 (Note: KCP2)Description of Change and Change Influence......................4

2 Preparations for Change.......................................................................................5

2.1 (Note: KCP3)Composition of Change Team and Responsibility of Team

2.2.1 Change Team of XX Company.................................................................5

2.2.2 Huawei On-site Change Team.................................................................5

2.2.3 Huawei Support & Guarantee Team........................................................6

2.2 (Note: KCP4)Remote Access.....................................................................6

2.3 (Note: KCP5)Platform and Software Preparation......................................7

2.4 (Note: KCP6)Check of Equipment Running...............................................8

2.5 Change Risks and Countermeasures........................................................8

2.6 (Note: KCP7)Check Before Change..........................................................8

3 Operation Steps for Change...............................................................................10

3.1 Overall Description of Change Steps.......................................................10

3.2 (Note: KCP8)Operation Steps for Change...............................................10

3.3 (Note: KCP9)Test and Verification...........................................................11

3.4 Solution for Changeback In the Case of Failure......................................12

3.4.1 (Note: KCP10)Definition of Change Failure.............................................12

3.4.2 (Note: KCP11)Overall Description of Changeback..................................13

3.4.3 (Note: KCP11.1)Changeback Steps........................................................13

3.4.4 (Note: KCP11.2)Tests After Changeback................................................13

3.4.5 (Note: KCP11.3)Changeback Risk Analysis............................................14

3.5 Change of Spare Parts and Emergency Workstation..............................14

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

4 (Note: KCP12)Work After Change......................................................................14

4.2 Other work...............................................................................................15

please delete these content when output the final version

1.1 Description of Site

Key features N/A

Key features License Activation in 10 BSC6900/BSC6910

business License Activation in whole ZAIN network except

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

1.2 (Note: KCP1)Purpose and Requirements

 The red font content with * is essential

 Change purpose*(essential)：problem resolution/version

sales/rectification/network performance optimization/ engineering network

 Change time*(essential)：should mention time, e.g. yyyy-mm-dd hh:mm to

time should describe separately

The MOP Prepared for BSC6910 UMTS LICENSE ACTIVATION

Change scope BSC6910/BSC6900 UMTS License Activation

Change time* 2020/04/05 00:00 to 06:00

1.3 (Note: KCP2)Description of Change and Change Influence

No. NE type* NE ID* QTY* Current version* Target version*

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

No. Related NE type Related NE ID Version

2 Preparations for Change

2.1 (Note: KCP3)Composition of Change Team and Responsibility of

Change team preparation*（essential for high risk change）：

Owner for xx product change, etc. from customer side is complete;

etc. from Huawei side is complete;

4. Whether assigned on site owner for remote operation.

2.2.1 Change Team of ZAIN Company

Name Responsibility Telephone No.

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

Musa Owner for BSC product change +249912399613