Ringback tone Issue on vIMS

Prepared by: Date:

Reviewer: Date:

Approver: Date:
 Contents

1 Description of Change and Change Influence........................................................................1

1.1 Change Purpose.....................................................................................................................................................................1
1.2 Basic Information and Change Plan......................................................................................................................................1
1.2.1 Network Topology.................................................................................................................................................................1
1.2.2 Change Batches.....................................................................................................................................................................1
1.2.3 Peripherals.............................................................................................................................................................................2
1.3 Change Influence...................................................................................................................................................................3

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

2.1 Composition of Change Team and Responsibility of Team Members..................................................................................4
2.1.1 Change Team of Claro Company..........................................................................................................................................4
2.1.2 Huawei On-site Change Team...............................................................................................................................................4
2.1.3 Huawei Support & Guarantee Team......................................................................................................................................4
2.2 Remote Access.......................................................................................................................................................................5
2.3 Tool and Software Preparation..............................................................................................................................................5
2.4 Check of Equipment Running...............................................................................................................................................6
2.5 Change Risks and Countermeasures.....................................................................................................................................6
2.6 Confirm Work Before Change...............................................................................................................................................7

3 Operation Steps for Change........................................................................................................9

3.1 Overall Description of Change Steps....................................................................................................................................9
3.2 Preparation for Change Implementation...............................................................................................................................9
3.3 Operation Steps for Change.................................................................................................................................................10
3.4 Test and Verification............................................................................................................................................................11
3.5 Solution for Changeback In the Case of Failure..................................................................................................................11
3.5.1 Definition of Change Failure...............................................................................................................................................11
3.5.2 Overall Description of Changeback....................................................................................................................................12
3.5.3 Changeback Steps................................................................................................................................................................12
3.5.4 Tests After Changeback.......................................................................................................................................................12
3.5.5 Changeback Risk Analysis..................................................................................................................................................13
3.6 Change of Spare Parts and Emergency Workstation...........................................................................................................13

4 Work After Change.....................................................................................................................14

4.1 Observation..........................................................................................................................................................................14

Issue ()
1 Description of Change and Change Influence

1.1 Change Purpose

Change Customer feedback vIMS caller cannot hear ringback tone for some scenario.
Purpose* This operation will add pem sendrecv on 18x.
Limit: If the called party don't play ring back tone, after this workaround still can't hear
ring back tone same as legacy network.

1.2 Basic Information and Change Plan

1.2.1 Network Topology
Network
topology
diagram

1.2.2 Change Batches

No NE Type* NE QTY Start Start End Curre Target
. ID/Name* * Date* Tim End Time nt Version*
e* Date* * Versio
n*

1 CGP CGP 1 2023-09- 22:00 2023- 06:00 CGP_ -

20 09-21 V200R
021C1

Issue ()
 No NE Type* NE QTY Start Start End Curre Target
. ID/Name* * Date* Tim End Time nt Version*
e* Date* * Versio
n*

0SPC2
16
2 CSCF CSCF 1 2023-09- 22:00 06:00 CSCF_ -
20 V500R
2023-
021C1
09-21
0SPH1
20
3 ATS ATS 1 2023-09- 22:00 06:00 ATS_ -
20 V500R
2023-
O21C1
09-21
0SPH1
37
4 CCF CCF 1 2023-09- 22:00 06:00 CCF_ -
20 V600R
2023-
021C1
09-21
0SPC1
07
5 MRP MRP 1 2023-09- 22:00 06:00 MRP6 -
20 600_V
2023- 500R0
09-21 21C10
SPH10
6
6 SPG SPG 1 2023-09- 22:00 06:00 SPG_V -
20 500R0
2023-
21C10
09-21
SPC10
3
7 SBC SE2980 1 2023-09- 22:00 06:00 SE298 -
20 0_V50
2023-
0R021
09-21
C10SP
C100

1.2.3 Peripherals
No. Related NE type Related NE ID/Name Version

1 CGP CGP CGP_V200R021C10S

PC216
2 CSCF CSCF CSCF_V500R021C10
SPH120

Issue ()
 No. Related NE type Related NE ID/Name Version

3 ATS ATS ATS_V500RO21C10

SPH137
4 CCF CCF CCF_V600R021C10S
PC107
5 MRP MRP MRP6600_V500R021
C10SPH106
6 SBC SE2980 SE2980_V500R021C
10SPC100
7 U2000 MAETAISHAN U2020
https://10.255.171.5:31943/

1.3 Change Influence

Change Scope First Site ☐Whole Network ☐Region ☐City ☐Other Item
Special Scenarios ☐Application at the first site ☐Single site ☐Perform operations at the DR site at
the same time. ☐No disaster recovery is performed on the target hardware.
☐Typical Scenarios of Major Accidents ☐N/A ☐Three-layer decoupling ☐Two-
layer decoupling N/A ☐OthersIf yes, please fill in

Key Features and ☐A-SBC ☐I-SBC ☐VOLTE ☐emergency-call ☐PBX OthersIf yes, please
Business fill in

Related Business ☐500,000 or later ☐30,000-500,000 ☐1000-30,000 Less than 1000

Amount ☐OthersIf yes, please fill in
Customer Concern Customer Low-level Concern ☐Customer Mid-level Concern ☐Customer
High-level Concern ☐External event ☐Internal event ☐OthersIf yes, please fill in
Change Influence Introduce new features, services, and functions related to the new commerical cutover
operation whether affect the voice/data service, O&M, performance，alarms and
charging or not.

Issue ()
2 Preparations for Change

2.1 Composition of Change Team and Responsibility of Team

Members
2.1.1 Change Team of Claro Company
Name Responsibility/Position Telephone
No.

Roberto Chief commander +502 5826

Villatoro 1444
Luis Miguel Claro key information owner +502 5826
Reyes 3723
Christoper Owner for CloudePDG product change +502 5205-
0067

2.1.2 Huawei On-site Change Team

Name Responsibility/Position Telephone No.

Rogelio Rodolfo Chief commander (CS Manager/PM) * +502-30155137

Pamal Villanueva
Zeng Hongbin Expert for Change (TD)* +86-18392952786/+502-
54971581
Jose Antonio Expert for product(TL) +502-
Velasquez 56303770(Preferred)
Chong Yi Xuan Change Owner +60-166669917/+502-
41977674

2.1.3 Huawei Support & Guarantee Team

Name Responsibility/Position Telephone No.

GTAC/RTAC Experts Supporting overall coordination as L2 technical expert +862981770999

GTAC/RTAC Experts Supporting overall coordination as L3 technical expert +862981770999

Issue ()
2.2 Remote Access
Item Preparation status Owner

Remote Access Solution* OK ☐NOK ☐NARemarkeSpace, WeLink Chong Yi

Xuan
Remote Access Currently Huawei owns an authorization letter for network Chong Yi
Authorization* access Xuan
Remote Access Test* Perform screen shift speed and packet drop rate before Chong Yi
operation, and upload the test result to IT system Xuan

Figure2-1 Figure1-1

2.3 Tool and Software Preparation

Type Content Owner

Tools* Web LMT/ U2020 Chong Yi

Xuan
Material* ☐Ethernet Cable ☐Serial Cable NA ☐OthersIf others please Chong Yi
fullfill Xuan

Communication Backup Mobile ☐Other Operator SIM Card ☐NA ☐OthersIf Chong Yi
backup* others please fullfill Xuan
（essential for high
risk change）
Version software Yes ☐NARemarkPlease fullfill detail version information Chong Yi
Xuan
Test tools ☐Service Test Tool OthersCustomer will do service test Chong Yi
Xuan

Issue ()
2.4 Check of Equipment Running
Check Item* Check result or steps*

Alarm Pass ☐Not Pass ☐NARemarkUpload the Proof

KPI Pass ☐Not Pass ☐NARemarkUpload the Proof
Hardware operation Pass ☐Not Pass ☐NARemarkUpload the Proof
status

2.5 Change Risks and Countermeasures

No. Main Issues and Risks Description Possibility Impact Operatio
n

1 Module failure ☐High ☐Middle ☐High ☐Middle 1.Restart

Low Low the
module
2.Block
the
Module
2 The service dialing test is abnormal ☐High ☐Middle ☐High ☐Middle 1: Trace
Low Low messages
during
testing and
demarcate
the first
NE which
responeses
error 2:
Determine
if the first
NE
which
responeses
error
needs to
configure
related-
data for
the
operation,
and if it
is
required,
request
peer NE to
check 3: If
the first

Issue ()
 No. Main Issues and Risks Description Possibility Impact Operatio
n

NE which
responeses
error
doesn't
need to
configure
related-
data for
the
operation,
request
peer NE
for
troublesho
oting
3 high risk command/operation ☐High ☐Middle ☐High ☐Middle NA
Low Low

2.6 Confirm Work Before Change

No. Confirm Work Before Change Completio Owner
n Date

1 Change back solution has been prepared, confirmed and authorized 2023-09-20 Chong Yi
by customer* Xuan
2 Change solution and change back solution have been verified* 2023-09-20 Chong Yi
Xuan
3 Confirm main/standby switchover test has been performed 2023-09-20 Chong Yi
Xuan
4 Readiness of getting access permission to the site 2023-09-20 Chong Yi
Xuan
5 Readiness of remote log-in environment 2023-09-20 Chong Yi
Xuan
6 Confirm change risks and emergency measures 2023-09-20 Chong Yi
Xuan
7 Confirm data and configuration are backup 2023-09-20 Chong Yi
Xuan
8 Confirm network performance is tested and recorded 2023-09-20 Chong Yi
Xuan
9 Readiness of change test personnel 2023-09-20 Chong Yi
Xuan

Issue ()
 No. Confirm Work Before Change Completio Owner
n Date

10 Readiness of relevant equipment maintenance personnel 2023-09-20 Chong Yi

Xuan
11 Readiness of support & guarantee team 2023-09-20 Chong Yi
Xuan
12 Readiness of mobile phone test card 2023-09-20 Chong Yi
Xuan
13 Readiness of boards, tools, and instruments 2023-09-20 Chong Yi
Xuan

Issue ()
3 Operation Steps for Change

3.1 Overall Description of Change Steps

No. Main steps Start Time End Time

1 Preparation before Operation 22:00 23:00

2 Log in and Data Check 22:00 23:00
3 Data backup 22:00 23:00
4 Change Operation 22:00 23:00
5 Service Test and Result Analysis 22:00 23:00
6 Briefly Report After the Operation 22:00 23:00
7 Rollback detailed Steps decomposition 22:00 23:00

3.2 Preparation for Change Implementation

No. Confirm Work on Change Day Completi Owner
on Time

1 Confirm there is no new alarm or new alarm do not affect the SPS cutover 16:00 Chong
Yi Xuan
2 Network blocking: One day before the migration, block the network to 16:00 Chong
forbid operations, such as subscriber data modification, local data Yi Xuan
modification, hardware switchovers. The time for network blocking may
vary depending on site requirements.
3 Tools: Ensure that the dialing test table, charging test table, test personnel, 16:00 Chong
tools, and vehicles required on the night of the migration are available. Yi Xuan
4 Contingency plan: Familiarize yourself with measures taken in case of an 16:00 Chong
emergency described in the contingency plan. Yi Xuan
5 Pre-migration preparation: Ensure that portable computers, software, 16:00 Chong
network cables, and serial cables are available. Yi Xuan
6 Pre-migration meeting: Hold a meeting before the migration. 16:00 Chong
Yi Xuan
7 Maintenance personnel of neighboring NEs: Ensure that maintenance 16:00 Chong
personnel of neighboring NEs can be reached during the migration. Yi Xuan
8 Distribution of related information: Print and distribute the migration 16:00 Chong

Issue ()
 No. Confirm Work on Change Day Completi Owner
on Time

procedure and contact information about migration personnel. Yi Xuan

9 Risk and emergency measures: Determine risks that may occur after the 16:00 Chong
migration and corresponding emergency measures. Yi Xuan
10 Confirm data and configuration are backup 16:00 Chong
Yi Xuan
11 Confirm network performance is tested and recorded 16:00 Chong
Yi Xuan
12 Readiness of change test personnel 16:00 Chong
Yi Xuan
13 Readiness of relevant equipment maintenance personnel 16:00 Chong
Yi Xuan
14 Readiness of support & guarantee team 16:00 Chong
Yi Xuan
15 Readiness of mobile phone test card 16:00 Chong
Yi Xuan

3.3 Operation Steps for Change

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).

No. Change Step* Detail Operation* Imple Star End

mentat t Time
ion Tim *
Person e*
*

1 Check whether the LST ME:; Check whether the NE type, NE name, Chong 22:0 23:00
login to the NE is and NE ID are operated Nes Yi Xuan 0
correct
2 Operation Follow the script below for implementation: Chong 23:0 00:00
implementation Yi Xuan 0

3 Data Backup EXP MML:; Chong 01:0 02:00

before The BKP SYS: BKTYPE=LOCAL, BKCON=ALL; Yi Xuan 0
Operation

Issue ()
3.4 Test and Verification
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
No. Test Item* Operation Method* Owner Start End
* Time* Tim
e*

1 Service test and result It is recommended that frontline engineers Chong 03:00 05:00
analysis use the service dialing test cases provided Yi
by frontline engineers or customers Please Xuan
refer to the:
2 CDR verification Contact the CDR verification personnel to Chong 03:00 05:00
verify the CDR and verify that the CDR Yi
verification is normal Xuan
3 KPIs analysis Check the counters are normal and fill in Chong 03:00 05:00
the counters . Yi
Xuan
4 Collect operation logs of Collect all operation logs and UI operation Chong 03:00 05:00
the night logs Yi
Xuan
5 Briefly report after the Complete the briefly report. Chong 03:00 05:00
operation Yi
Xuan

3.5 Solution for Changeback In the Case of Failure

3.5.1 Definition of Change Failure
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 Time* 04:00

Issue ()
 Changeback Huawei Side: Zeng Hongbin +50254971581
Decision Maker* Customer Side: Christoper Santisteban +50258261444

Changeback 1. The operation was not completed before deadline;

Condition 2. Expansion of single board, process loading failed;
3. New Exception alarm, and can not be solved in time;
4. The new expansion link can not be reached, and can not be solved in time;
5. In the call test, there is a lot of failure calling,
6. Billing validation failed;
7. A large number of users cannot be called normally;
8. A large number of user voice service single pass
9. The scope of business impact beyond the change plan;
10. After the operation, the KPI for IMS NE drops below normal

3.5.2 Overall Description of Changeback

Briefly describe the changeback in an overall manner.

3.5.3 Changeback Steps

Describe changeback steps in details, clarify owners, and specify the time period needed for completing each step.

No. Changeback Operation Content* Owner Start End

Steps* * Time Time
* *

1 Information Get one-cllick information of CGP Chong 03:00 05:00

Collection Yi
before The Xuan
Rollback
2 rollback the Follow the rollback script below: Chong 03:00 05:00
change scripts Yi
Xuan

3 Check KPIs After rollback, check the KPI and alarms for any Chong 03:00 05:00
abnormal Yi
Xuan

3.5.4 Tests After Changeback

Describe the tests that shall be conducted after changeback and clarify test owners.

Issue ()
 No. Test Item* Operation Method* Owner* Start End
Time Tim
* e*

1 Service test and result It is recommended that frontline Chong Yi 04:00 05:00
analysis engineers use the service dialing test Xuan
cases provided by frontline engineers
or customers Please refer to the test list:
2 CDR verification Contact the CDR verification personnel Chong Yi 04:00 05:00
to verify the CDR and verify that the Xuan
CDR verification is normal
3 KPIs analysis CSC: Chong Yi 04:00 05:00
Number of Registered Subscribers Xuan
Initial Registration Success Rate
Re-registration Success Rate
MO Session Connection Rate
MT Session Connection Rate
ATS:
ATS MO Call Attempts
Call Completion Rate on the MO Side
of the ATS
ATS MT Call Attempts
Call Completion Rate on the MO Side
of the ATS
4 Collect operation logs of the Collect all operation logs and UI Chong Yi 04:00 05:00
night operation logs Xuan
5 Briefly report after the Complete the briefly report. For details, Chong Yi 04:00 05:00
operation see the "Result Report " sheet Xuan

3.5.5 Changeback Risk Analysis

Analyze the risks that may be brought by changeback, and provide corresponding countermeasures.

No. Main Issues and Risks Possibility Impact Countermeasure

Description

1 the KPI degradation and ☐High ☐Middle ☐High Contact Peripheral

service affected Low ☐Middle NEs GTAC support
Low team to recover

2 The link is faulty after the ☐High ☐Middle ☐High Contact GTAC support
cutover. Low ☐Middle team to recover
Low

Issue ()
3.6 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.

Issue ()
4 Work After Change

4.1 Observation
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. Observation Observation Method* Observation Time* Owner

Item* *

1 Alarm Whether there is new 2023-09-21 09:00-- 2023-09-21 Chong

generated alarm 18:00 Yi
Xuan
2 KPI Take the KPI of the same time 2023-09-21 09:00-- 2023-09-21 Chong
range one week and one 18:00 Yi
month before the change as Xuan
reference.

Issue ()