Method of Procedure Reparenting of BSC13 in LHR-Pool

1

1. Purpose

The purpose of this document is to provide the high level implementation strategy for introducing BSC13 in the Lahore POOL having MSS03/MSS04/MSS5/MSS11/MSS12/MSS13 and MGW29/MGW30.

2. Scope of Work

BSC13 is located in LHR-2 site. BSC-13 is currently working with MSC-10; the scope is to introduce BSC-13 with the Lahore pool members’ i-e MSS 3,4,5,11, 12, 13.

3. Activity DescriptionThe 7 STM-1s will be distributed towards the six MSS in pool members (MSS 3,4,5,11,12,13) using the MGW 29 & 30.

4. Health ChecksThe attached file will be used for node HC before and after the activity.

5. Project Specific Information

This chapter gives details specific to an individual project and implementation using this procedure. This information will be changed for each specific project or implementation.

6. Node Information

Node Type Node Name NRI value CNID BSC and LAC BSC-13 - LACTarget (Pool) MSC MSS 3,4,5,11/12/13 Pool MGw MGw 29 & 30MIP-2 Live MSS MSS 3, 4, 5 ,11, 12, 13

7. Timetable of Events

Implementation Day (DAY) is : 27th Aprch, 09.

Date Time Description

2

Date Time Description27th Apr - STS & Traffic data must be collected for

handovers/call rejection/call congestion and traffic trends for whole week on BSC-13/ MSS11/12/13/3/4/5. This data will be compared with that recorded after MIP activation.

27th Apr - Check A-interface circuits, routes and C7 is completed and working. The BSC must also be defined in the alternate MSC node.

27th Apr 22:00 Engineers arrive at Site

27th Apr 22:15 Health checks performed as per the attached HC file.

27th Apr 22:30 Log into all MIP network Nodes via OSS/Winfiol.Initiate Pre monitoringInitiate pre activity drive testing.

27th Apr 23:30 Pre activity backup performed (will be done by MS as per the responsibility matrix)

27th Apr 00:00 Start Implementation.A-interface splitting will be performed for MSS3/4/5/11/12/13 by core team.Inner/outer cell definitions for MSS 3,4,5,11, 12, 13 will be executed by RAN team. Outercells of BSC-13 in neighboring MSCs will be defined.

28th Apr 00:45 Deblock A interface of 1st STM divided into 6 MSS.

3

Date Time Description28th Apr 01:00 Activation phase- 1st STM

Path for MSS03 , MSS04 and so on till MSS11 in BSC-13 will be activated. MSS 4/5/11/12/13 will be barred for stoppage of further new LU till drive testers get camped into MSS03. Drive tester will make new LU, and start drive testing. MSS 4/5/11/12/13 will be reverted back to Active mode once drive tester is camped on. And this procedure will be repeated for MSS 4,5,11,12,13.

28th Apr 01:30 After confirmation of basic call testing, deblocking of Rest of E1 as per DT toward the other MSS will be started.

28th Apr 02:00 Configuration of E1s towards MSS4,11,12/13 will be executed in the mean while.

28th Apr 02:15 It will be decide by this time after final statement from Drive tester that every case is passed for MSS03,04. MSS 04 will made active towards BSC-13, and exactly the same steps will be repeated.

28th Apr 04:45 MSS05 final call testing should be concluded and system should be ready for complete cutover.

28th Apr 05:45 Rest of the STMs will also be made ACTIVATED using the same procedure as stated above.

28th Apr 06:45 Drive Testing will be performed for the remaining STMs.

4

Date Time Description28th Apr 07:00 Check point.

A- If every thing goes good, Its time to start even distribution of Subscriber in the pool.

Or

B- Fall back have been decided.

Fall back Options/Decision table attached.

28th Apr 08:30 Subscriber re-distribution will be performed as per the attached procedure.

5

8.

9. Roles & Responsibilities

This section lists roles and responsibilities of the people will be the single point of contact for each activity.

Company (e.g. Ericsson, Warid)

Group (e.g. MU, GSDC)

Name Phone Number

Prime Role / Responsibility

Ericsson EO/MS BackupsEricsson FO Alarm Monitoring

and informing the engineers doing baby-sitting for any issues reported. Specially 15 minutes out put of RPMO during peak hour time.

Ericsson/Warid RF Drive Testers Drive testsEricsson/Warid ECP/NDI, ECP-

PMG, W-PMG, TSG.CORE, NOC.GSM

Email notifications

Ericsson E/// Core team Hassan Ajwad, Ali Qamber

+92 321 477 5039

Circuit build

Ericsson E/// Core team Hassan Ajwad, Ali Qamber

+92 321 477 5039

Implementation

Ericsson MS/GNOC/GSDC SupportEricsson FO/NPO Stats verification

during implementation/baby sitting

Ericsson BO/NDI Baby-sitting after the activity

6

9.1 Checklists

This section contains check lists to be used before and during the implementation. Each item should be initialled and marked as OK or NOK (not OK).

9.1.1 Pre-Requisites

ItemNo.

Item OK / NOK

Initial

R01 This document has been accepted, demonstrated and signed off by Warid

R02 The network design activity is completed and values for NRIV, NRIL, CAP and CNID are known

R03 The circuit build between target MSC-S and BSC is completed. All circuits and routes are de-blocked and working.

R04 OSS/node-login account with Administrator rights is obtained from Warid

R05 Test equipment is availableR07 DTs are prepared.R08 Consistency check performedR09 STS data collected before implementation (Warid)R10 BSC definition in Target MSCs is OKR11 Manual check of signalling link data in

MSCs/MGWs and BSCsR12 Health Checks performed in Source & Target

MSCs/MGW and BSC.R13 Backups made in Source & Target MSCs/MGW

and BSCR14 Traffic case tests completed (before

implementation)R15 Data pre-loading in Source and Target MSCs is

complete.

9.1.2 Preparation Phase

ItemNo.

Item OK / NOK

Initial

P01 Data is loaded in the Source MSC/MGW P02 Data is loaded in the Target MSC/MGW P03 Data is loaded in the BSC P04 Data is loaded in the Neighbouring MSCsP05 All log files from data loading are stored.

7

9.1.3 Activation Phase

ItemNo.

Item OK / NOK

Initial

A01 Log files are activatedA02 MIP routing in BSC is activatedA04 DTs checkedA06 DTs double checkedA07 VerificationsA08 Test calls completedA09 MSC modes set to active

9.1.4 Cleanup Phase

ItemNo.

Item OK / NOK

Initial

C01 Backups taken for all nodes, without rotation.C02 Health checks run immediately after

Implementation C03 All test calls completedC04 Old data is removed.C04 Logs are stored. C05 Customer acceptance of the Implementation as

complete.

8

9