METHOD OF PROCEDURE BTC BOTSWANA Mi P PROJECT Final

Ericsson InternalIMPLEMENT INSTRUCTION 1 (45)

Prepared (Subject resp) No.

Tope KareemApproved (Document resp) Checked Date Rev Reference

2015-06-08 PA1

Method of Procedure for BTC BOTSWANA MiP Project

Contents

1 Purpose...........................................22 Customer Information..............................23 Escalation Procedure..............................24 Contact Details...................................35 Summary of Implementation plan....................45.1 MSC – GBRNC3 Activity.............................45.2 MSC – FTRNC1 Activity.............................45.3 MSC – GBEVOB1 and FTEVO1 Activities...............46 Detailed Implementation Time Plan.................56.1 Activation Phase..................................56.2 Subscriber Redistribution.........................77 MSC Activities....................................77.1 Entry Criteria....................................77.2 Baseline checks...................................87.3 Health Check......................................87.4 Preparation Phase................................107.5 Activation Phase.................................147.6 Subscriber Re-distribution Phase.................158 BSC Activities...................................168.1 Entry Criteria...................................168.2 Baseline checks..................................168.3 Health Check.....................................178.4 Preparation Phase................................198.5 Activation Phase.................................209 RNC..............................................209.1 Entry Criteria...................................209.2 Baseline checks..................................209.3 Preparation Phase................................219.4 Activation Phase.................................2110 Fallback Procedure - MSC.........................2611 Fallback Procedure - BSC.........................28




2015-06-08 PA1

12 Fallback Procedure - RNC.........................2913 Roles & Responsibilities Checklist...............3114 Implementation Checklist.........................3215 Commencement Signoff.............................3216 Completion and Acceptance........................3417 Fault Log........................................35




2015-06-08 PA1

1 PurposeThe purpose of this document to facilitate in identifying & communicating the key steps & actions required as part of the upgrade procedure and to ensure that ALL parties are aware of the documentation that is required. Documents detailed in the MOP are only to be used in accordance with the official method of procedure for activating MSC-IN-POOL. All parties must sign the MOP for the MSC-IN-POOL to commence if satisfied that all roles, responsibilities & actions are clearly understood and in place. On completion of the full upgrade procedure, all parties must, again sign the MOP listing any outstanding items identified with a specified completion date. It is not the intention of this document to replace any of the implementation procedures nor is not part of the standard deliverables.

2 Customer Information

Customer Name BTC BotswanaSite name GBMSS3 and FTMSS1Products APZ 212 60, APG43Project Description MSC-in-POOLPlanned FI dates 23rd, 25th and 29th June 2015

3 Escalation Procedure

In the event of emergency, escalation processes within Ericsson andBTC will be followed beginning with the contact details given below.

Emergency Contacts:The primary contact for emergency issues during the execution of this Method of Procedure will be the responsible engineer Name & Contact details are in below details. Ericsson Internal escalation process is known by the Engineer. Customer Escalation process should be known by the Customer Engineer.




2015-06-08 PA1

Name Position Number EmailOutage/Alarms

1st

Hamizan Mohamad

Project Manager

26773909942

[email protected] Minor

2nd

Hamizan Mohamad

Lead ProjectManager

26773909942

[email protected] Major

3rd

Didimalang Moaro

Service Delivery Manager

26772305032

[email protected] Critical

4th

Kristoffer Gade

Country Operations Manager

26772302442

[email protected] Emergency

mailto:[email protected]


mailto:%[email protected]








2015-06-08 PA1

Name Position Number EmailOutage/Alarms

1st Kaone Mpodi

Mobile ProjectManager

26773100072 [email protected] Minor

2nd

Moemedi Moremi

Mobile NetworkBuild Manager

26773235488 [email protected] Major

3rd

GabalemogweRankgate

Peter Olyn

Head of Network BuildHead of Mobileservices

[email protected]

[email protected] Critical

4th Thabo Nkala

General Manager Technology

26772302442 [email protected] Emergency

4 Contact Details

Ericsson Engineer Information Ericsson Engineer Information

1.

Name: Tope

1.

Name: Jei Cai

Mobil +267 73723008 Mobile: +8613995693429Signum etopkar Signum:

email [email protected] email: [email protected]

2.

Name: Arokki Krishnaprasad

2.

Name:Mobile:

Mobile:Signum: Signum:email:

Arokki. [email protected]

email:

BTC Engineer Information Supervisor / manager Information

1.

Name: Boingotl Maswabi

1.

Name: Reetsang Mmereki

Mobil +26773100113 Mobile: 73100016Signum Signum:

email [email protected] email: [email protected]

2.

Name: Mothulwe Motlhokomedi

2.

Name: Kaone MpodiMobile:

Mobile: 73100072Signum: Signum:email:

[email protected] email: [email protected]






2015-06-08 PA1

5 Summary of Implementation plan

5.1 MSC – GBRNC3 Activity

DAY1 NightTime Durati

onActivity Responsib

leComments

22:00 30 min Baseline and health checks on MSCs

Ericsson

22:00 30 min Baseline and health checks on GBRNC3

Ericsson

22:30 30 min Preparation phase on MSCs Ericsson22:30 30 min Preparation phase on

GBRNC3Ericsson

00:00 10 min Activation Phase on MSC Ericsson00:10 10 min Activation phase on

GBRNC3Ericsson

00:20 2 hours

Subscriber re-distribution phase on MSC

Ericsson

5.2 MSC – FTRNC1 Activity

DAY 2 NightTime Durati


leComments


Ericsson

22:00 30 min Baseline and health checks on FTRNC1

Ericsson


FTRNC1Ericsson

00:00 10 min Activation Phase on MSC Ericsson




2015-06-08 PA1

00:10 10 min Activation phase on FTRNC1

Ericsson

00:20 2 hours


Ericsson

5.3 MSC – GBEVOB1 and FTEVO1 Activities

DAY 3 NightTime Durati


leComments


Ericsson

22:00 30 min Baseline and health checks on GBEVOB1

Ericsson

22:30 30 min Baseline and health checks on FTEVO1

Ericsson


GBEVOB1Ericsson

00:00 30 min Preparation phase on FTEVO1

Ericsson

00:30 10 min Activation Phase on MSC Ericsson00:40 10 min Activation phase on

GBEVOB1Ericsson

00:50 10 min Activation phase on FTEVO1

Ericsson

01:00 2 hours


Ericsson

6 Detailed Implementation Time PlanThe time plan is divided into four phases. Phase 1 and 2 will be performed at least one week before the main activity and will be repeated 1-day beforethe main activity.

The four phases are:

Pre-implementation phase




2015-06-08 PA1

Preparation phase

Activation phase

Subscriber redistribution

Activities in pre-implementation and Preparation phases are not traffic affecting and can be performed at any time of the day. However, customer will be notified before and after the activity. All changes made must be communicated to the customer and logfiles must be released.

6.1 Activation Phase

Time Action Resp. Duration

Check Impact

23:00 MSC:Redefine Inner and Outer cell definitions, Charging Origin, Routing Origin and Emergency AreaLoading of the prepared DT

Tope 30mins

BSC: MSC Pool Activation in

all BSC

Loading of the prepared DT

Prasad

1hour




2015-06-08 PA1

Change MODE to BARRED on both GBMSS3 and FTMSS1

RLTDC:MODE=GBMSS3,MODE=BARRED; RLTDP:MSC=ALL;

Change MODE to ACTIVE

RLTDC:MODE=GBMSS3,MODE=ACTIVE; RLTDP:MSC=ALL;

RNC : Undefined the existing

RANAP definition towards the serving MSC

Set the Network Resource Identifier Length for Circuit-switched traffic

Redefine the RANAP definition towards theserving MSC with new MSC in Pool parameters.

Loading of the prepared Scripts




2015-06-08 PA1

6.2 Subscriber Redistribution

This section is driven by the MSC Engineer. Support will be provided by all the team member.

Time Action Resp. Duration

Check Impact

00:00MSC:

Check signaling towards MGW and RAN

Check for blocked devices on routes

Perform subscriber observation

Block Selected MSC-S for new traffic

Perform 2nd subscriberobservation

Initiate pool redistribution

Observe the situation in all MSCs

End pool redistribution

Unblock selected MSC-sfor new traffic

CTM 1hrIn-charge Engineer: ObservingEngineer:

Traffic willbe affectedfor 5mins




2015-06-08 PA1

7 MSC Activities

7.1 Entry Criteria

The following entry criteria must be met before this migration procedure commences.

• Understanding the Network Design

• Review of the software requirements of all the MSC involved.

• The required licenses have been purchased for the MSC-S features required

• Any new hardware requirements have been met.

7.2 Baseline checks

7.2.1 Initial Pre-Implementation Checks

This check must be performed a week before implementation and repeated 2 days before the d-day.

Analyse and fix all A1, A2 and A3 alarms

ALLIP:ACL=A1; ALLIP:ACL=A2;

Note: This is the responsibility of the Customer.

Collect the following STS data

Authentication Call success RateLocation updateSize alteration

7.3 Health Check

MSC-S




2015-06-08 PA1

Print alarm list.

ALLIP:ACL=A1; ALLIP:ACL=A2; ALLIP:ACL=A3;

Print CP state

DPWSP;

CP state should be normal (A-side is EX and B-side SB/WO).

Check RP stateEXRPP: RP=ALL;

Check EM stateEXEMP: RP=ALL, EM=ALL;

NOTE: RP STATE is WO. For EM DATA, RP state is WO/WOTWIN.

Check that no serious faults exist on RP’s.

DIRRP: RP=ALL;

Check that no serious faults exist on CP.

DIRCP; Print connection data for IP Ports.

IHCOP: IPPORT=ALL; Check IP Port Status

IHSTP: IPPORT=all;Prints the blocking and operational states of the specified IP port(s).

Print SCTP Layer Status

IHSLP; Print SCTP Association Status

IHSAP: SAID=said;




2015-06-08 PA1

Print SCTP Association/End pointIHALP: EPID=ALL;

Check M3UA Routing.M3RSP: DEST=ALL; Destination Point State (DST) should be available (AVA). Route State (RST) should be enabled with association

Check M3UA Association State.M3ASP:[SAID=said];Association state should be “ACT”. Give the command without parameters to print all SCTP associations.

Check SCCP stateC7NCP: SP=ALL, SSN=ALL; NOTE: SPSTATE should be ALLOWED SCCPSTATE should be ALLOWED SUBSYSTEMSTATE should be ALLOWED

Print SNT statusNTSTP:SNT=ALL;

Print MGW status.NRGWP:MGW=ALL;

Print MGG data.NRGGP:MGG=ALL;

Print SAE fault information.DBTSP:TAB=SAEFAULTS;

Execute all SAE's from the list, if any.SAALI;This command is used in case of Software File Congestion cases in the previous command.

Check status of automatic size alteration.SAOCP;Status should be ‘Active’.

Print restart data.SYRIP:SURVEY;

Print the list of all blocked routes.BLORP;




2015-06-08 PA1

Print System Backup FilesSYBFP:FILE; NOTE: Latest file should be in RELFSW0.

Make backup on both MSC-S

7.4 Preparation Phase

7.4.1 Preparation

The Preparation Phase activity will not introduce any disruption to the network. NOTE: The MSC in pool feature for GBMSS3 and FTMSSS3 should be still de-activated.

7.4.2 Verify the MSC pool for MSCS1, 2 and 3 created/defined

Use the following commands to modify a value for MSCin pool Features.

SYPAC: ACCESS=ENABLED,PSW=psw; DBTRI; DBTSC:TAB=AXEPARS,SETNAME=GSMMMSC,NAME=p_name,VALUE=x; DBTRE: COM; SYPAC: ACCESS=DISABLED;

DBTSP:TAB=AXEPARS,NAME=p_name; (eg:p_name=OWNCNID)

Check the OWNCNID in the respective MSC Data table.

Check TMSI Allocation DBTSP:TAB=AXEPARS,NAME=TMSIPAR; NOTE: Value of TMSIPAR should be 2.

Check MSCPOOL value DBTSP:TAB=AXEPARS,NAME=MSCPOOL; NOTE: Value of MSCPOOL should be 1.




2015-06-08 PA1

Check ADMHOMSCPOOL value DBTSP:TAB=AXEPARS,NAME= ADMHOMSCPOOL; NOTE: Value of ADMHOMSCPOOL should be 1.

Check TMSILAIMSC value DBTSP:TAB=AXEPARS,NAME= TMSILAIMSC; NOTE: Value of TMSILAIMSC should be 0

Check OWCNID value.

DBTSP:TAB=AXEPARS,NAME= OWNCNID; NOTE: Value of OWNCNID is unique to each MSC.

Check TIMNRICHGM value DBTSP:TAB=AXEPARS,NAME= TMSILAIMSC; NOTE: Value of TIMNRICHGM should be 255.

Check PAGREP1LA value DBTSP:TAB=AXEPARS,NAME= PAGREP1LA; NOTE: Value of PAGREP1LA should be 2

Check PAGREPGLOB value DBTSP:TAB=AXEPARS,NAME= PAGREPGLOB; NOTE: Value of PAGREPGLOB should be 0

Check MSCREQNUM value DBTSP:TAB=AXEPARS,NAME= MSCREQNUM;NOTE: Value of MSCREQNUM should be 2

7.4.3 Set NRI Length and Assign NRI value to GBMSS3 and FTMSS1

MGNDP; MGNDI:NRIL=x,NRIV=y; MGNDP;

NOTE: y=2 and 3 for GBMSS3 and FTMSS1 respectively. X=4 for both GB and FT.




2015-06-08 PA1

7.4.4 Define Null NRI value in GBMSS3 and FTMSS1.

MGNDI:NULLNRIV=5;

Note: NRIV=5 is defined in both GBMSS3 and FTMSS1.

7.4.5 Print Inner and outer cells in the MSC Pool.

MGCEP:CELL=ALL; MGOCP:CELL=ALL; MGLAP;

7.4.6 Circuit building and signaling definition

We ensure that all C7 and SCCP data for all the BSC/RNC nodes. The BSC/RNC should be defined in GBMSS3 and FTMSS1. All circuits and routes should be deblocked and working. This ensures that any instability in transmission is detected at an early stage.

7.4.7 Global Paging is turned off

Check the status of Global Paging DBTSP:TAB=AXEPARS,NAME=PAGREPGLOB;

NOTE: Value should be 0

7.4.8 Definition of Enhanced Co-Operating VLR functionality in neighboring MSC-Servers

This must be defined for both GBMSS3 and FTMSS1.

MGCVP:VLR=ALL,LAI=ALL;MGCVI:VLR=GBMSS3,LAI=,VLRADDR=GB-VLR-ADDRESS,MAPV=GBMAP VERSION,NRIV=GB NRIV;MGCVP:VLR=ALL,LAI=ALL;




2015-06-08 PA1

7.4.9 Define Non-Enhanced Co-Operating VLR functionality

In an unusual case that enhanced co-operating functionality is not available, do the following command in GBMSS3, and it will act as Proxy.

MGCVI: VLR=MSC1,VLRADDR=4-11111111111,MAPV=MAP-3,LAI=444-11-22222;MGPTI: VLRADDR=FT VLR-ADDRR,NRIV=3;

7.4.10 Create load file for BSCs configuration data

The existing LAs in the MSC-S shall be extended withthe LAs (excluding the ones containing neighboring cells) from the other MSC-Ss. This step shall be executed only if the LAI administration function is used.

The existing inner cells in an MSC-S shall be extended with the inner cells from the other MSC-Ss with exception of cells from LAIs where outer cells (that will become inner cells later on) are defined.The outer cells are still needed for handover, as the pool is not operative yet.

The existing outer cells in an MSC-S shall be extended with the outer cells from the other MSC-Ss (with exception of the outer cells that become innercells when the pool is built).

The outer cells shall be removed and transformed into inner cells. The former inter-MSC handover willbecome intra-MSC handover. The handover availabilitywill increase as long as the former outer cells are defined as inner cells. Charging Origin, Routing Origin and Emergency Area should also be defined here.NOTE: Outer cells belonging to BSCs outside of the pool should not be removed.




2015-06-08 PA1

Example of DT in Pooled MSC-Ss:

MGOCE:CELL=BSC2; ! this is done for all the BSCs attached to MSCMGLAI:LAI=111-22-333; MGCEI:CELL=B20000,BSC=BSC2,CGI=111-22-333-4444; MGCEC:CELL= B20000,CO=31,RO=1,NCS=0,EA=22;

The DT prepared here shall be loaded during the activation phase.

7.4.11 Create load file for RNCs configuration data

The existing RNCs in the MSC shall be extended with the RNCs (excluding outer RNCs) from the other MSC-Ss. The RNCs defined as outer in the MSC are still required for handover/SRNS relocation, as the pool is

The existing area clusters in the MSC-S shall be extended with the area clusters from the other MSC-Ss (excluding the ones containing elements which areneighbouring to the other MSC-Ss that will constitute the pool). In this document we assume that area cluster administration is used.

The existing outer cells/RNCs in an MSC-S shall be extended with the outer cells/RNCs from the other MSC-Ss (with exception of the outer cells/RNCs that become inner cells/RNCs when the pool is built).

The outer RNCs shall be removed and transformed intoown RNCs.

The former outer RNCs shall be redefined as own RNCs. The former inter-MSC handover/SRNS relocation will become intra-MSC handover/SRNS relocation. The handover/SRNS relocation availability will increase as long as the former outer RNCs are defined as own RNCs

Example of DT in Pooled MSC-Ss:




2015-06-08 PA1

MGOCE:CELL=RNC2; MGLAI:LAI=222-22-333; MGMAI:RNC=RNC2,LAI=222-22-333; MGAAI:AREA=2,SAI=222-22-333-4444; MGAAC:AREA=2,CO=31,EA=22;

The DT prepared here shall be loaded during the activation phase.


7.5.1 Redefine Inner and Outer cell definitions, Charging Origin, Routing Origin and Emergency Area

Load the DT created in 4.1.9 here.

7.5.2 Set GLCNID to Supported

Set GLCID to value=1 in GBMSS3 and FTMSS1 (value=1).

MGRIC:GLCNID=1;

7.5.3 Redefine Inner and Outer cell definitions, Charging Origin, Routing Origin and Emergency Area

Load the DT created in 4.1.10 here.

7.6 Subscriber Re-distribution Phase

7.6.1 Pre MSC Pool Re-distribution checks

7.6.1.1 Check signaling towards MGW and RAN

C7LTP:LS=ALL; C7RSP:DEST=ALL; C7NCP:SP=ALL,SSN=ALL; C7SPP:SP=ALL;




2015-06-08 PA1

M3RSP:DEST=ALL;

7.6.1.2 Check for blocked devices on routes

STRSP:R=M1G2B2O&M1G2B2I; ! check for the exact routes.

STRDP:R=M1G2B2O&M1G2B2I,STATE=BLOC;

7.6.2 MSC Pool Re-distribution

7.6.2.1 Perform subscriber observationCheck how many subscribers are registered, how many can be subject to selection for redistribution and what level of effectiveness a redistribution session may have based on other characteristics of subscribers (detached subscribers, subscribers in location areas external topool). Observe also situation in other MSCs of the pool.

MGSVP;

7.6.2.2 Block Selected MSC-S for new trafficSet MSC-S selected for applying MSC pool redistribution on, as blocked for new traffic in all BSCs/RNCs of the pool. This will be performed in the BSC/RNC.

7.6.2.3 Perform 2nd subscriber observationWait at least 1 minute before giving command MGSVP again, in MSC-S subject for redistribution, in order to allow subscribers with ongoing registration actions to complete the procedure and obtain a more stable picture of the VLR(s) in the printout.

7.6.2.4 Initiate Pool Re-distributionWarning: The user should be familiar with the ‘MSC Pool Redistribution and Associated functions

MGPRI:PART=50;

NOTE: In this example 50% of the registered subscribers are re-distributed.




2015-06-08 PA1

7.6.2.5 Observe situation in all MSC-Ss in poolAfter redistribution initiation the redistribution progress should be checked. MGSVP;

MGPRP;

7.6.2.6 End Pool Re-distributionOnce the user is satisfied with the subscriber distribution, the session canbe ended.

MGPRE;

7.6.2.7 Unblock Selected MSC-S for new traffic

Wait a few minutes and then unblock the relative MSC-S in BSC/RNC.

8 BSC Activities

8.1 Entry Criteria

The following entry criteria must be met before this migration procedure commences.

Verify parameter values NRI Value, Core Network Identity (CNI) and Relative Capacity (CAP) are known for each BSSMAP definition required for the MSC Pool

Verify parameter value for parameter NRI Length is known for the MSC inPool to be implemented.


Verify that all the target BSC’s are on correct SW level (06B or later)

8.2 Baseline checks




2015-06-08 PA1


These checks should initially be made 1 week before the implementation and then repeated again 2 days before the implementation.

Analyse and fix all A1, A2 and A3 alarms

ALLIP:ACL=A1; ALLIP:ACL=A2;

8.3 Health Check

BSC Print alarm list.

ALLIP:ACL=A1; ALLIP:ACL=A2; ALLIP:ACL=A3;

Print CP state

DPWSP;

CP state should be normal (A-side is EX and B-side SB/WO).

Check RP stateEXRPP: RP=ALL;

Check EM stateEXEMP: RP=ALL, EM=ALL;

NOTE: RP STATE is WO. For EM DATA, RP state is WO/WOTWIN.

Check that no serious faults exist on RP’s.

DIRRP: RP=ALL;

Check that no serious faults exist on CP.

DIRCP;

Check SCCP routing.




2015-06-08 PA1

C7NCP: SP=ALL, SSN=ALL;SPSTATE should be ALLOWED SCCPSTATE should be ALLOWED

SUBSYSTEMSTATE should be ALLOWED Print SNT status

NTSTP:SNT=ALL;

Print SAE fault information.DBTSP:TAB=SAEFAULTS;

Execute all SAE's from the list, if any.SAALI;This command is used in case of Software File Congestion cases in the previous command.

Check status of automatic size alteration.SAOCP;Status should be ‘Active’.

Print restart data.SYRIP:SURVEY;

Print the list of all blocked routes.BLORP;

Print System Backup FilesSYBFP:FILE; NOTE: Latest file should be in RELFSW0.

Print State of Group SwitchGDSTP; GSSTP;

Print state of DIP’sDTSTP:DIP=ALL;

Print state of SDIP’sTPSTP:SDIP=ALL;

Print state of Link setsC7LTP:LS=ALL;

Print routing data for signalling routesC7RSP:DEST=ALL;




2015-06-08 PA1

Print all link set dataC7LDP:LS=ALL;

Print Semipermanent Connection data EXSCP:NAME=ALL;

Print outstanding alarm situations for all TRXCs RXASP:MOTY=RXOTG; RXASP:MOTY=RXETG;

Print all cell resources RLCRP:CELL=ALL;

Print status of all internal cells RLSTP:CELL=ALL;

Print status of MO’s RXMSP:MOTY=RXOTG,SUBORD;

Check MSC Pool feature towards MSC-S’s DBTSP:TAB=AXEPARS,NAME=MIP; DBTSP:TAB=AXEPARS,NAME=MIPROUTE;

NOTE: Features should currently be de-activated e.g.Value = 0.

Customer should make backup


8.4.1 Preparations

All logical mesh connections between three MGW’s and all MSC-S members in the pool are already connected.

8.4.2 Circuit building and signaling definitionAll the C7 and SCCP data should be defined in BSC nodes towards target MSC-Ss. The BSC should be defined in all MSC-S pool members. All routes towards new BSC/RNC should be defined in the target MSC-server. All circuits and routes should be deblocked and working. This ensures that any instability intransmission is detected at an early stage




2015-06-08 PA1

8.4.3 Define GBMSS3 and FTMSS1 in their respective BSCs if not already defined

RRMBI:MSC=GBMSS3,SP=SPC,CNID=GBMSS3-CNID ;

RRMBP:MSC=ALL;

8.4.4 Define NRI value and length

RRNRI: MSC=GBMSS3,NRIV=GB-NRIV; RRNLC:MSCNRILENGTH=x;

RRNLP;

8.4.5 Define CAP values in BSC and ensure MODE INACTIVE toward GBMSS3 and FTMSS1

RLTDC:MSC=GBMSS3,MODE=INACTIVE,CAP=cap;

NOTE: The parameter MODE will be INACTIVE during the preparation phase to ensure that mobiles do not register in target MSC-Server.

8.4.6 Define the CNID for both GBMSS3 and FTMSS1

RRMBC:MSC=GBMSS3,CNID=GB-CNID;


8.5.1 MSC Pool Activation in all BSC

The MSC in pool Routing function is activated initially.

DBTSP:TAB=AXEPARS,NAME=MIPROUTE; SYPAC: ACCESS=ENABLED,PSW=psw; DBTRI; DBTSC:TAB=AXEPARS,SETNAME=CME20BSCF,NAME=MIPROUTE,VALUE=1; DBTRE: COM; SYPAC: ACCESS=DISABLED;

DBTSP:TAB=AXEPARS,NAME= MIPROUTE;




2015-06-08 PA1

8.5.2 Change MODE to BARRED on both GBMSS3 and FTMSS1

RLTDC:MODE=GBMSS3,MODE=BARRED;

RLTDP:MSC=ALL;

8.5.3 Change MODE to ACTIVE

RLTDC:MODE=GBMSS3,MODE=ACTIVE;

RLTDP:MSC=ALL;

9 RNC

9.1 Entry Criteria

Verify that target RNCs are on correct SW level (P6 or later)

Verify that all RNC-MSC signaling (Iu-cs signaling) for target nodes is implemented on SIGTRAN.

9.2 Baseline checks


These checks should initially be made 1 week before the implementation and then repeated again 2 days before the implementation.

Collecting data using Moshell command DCGThe dcg command offers a number of options. The recommended command for the Healthcheck prior to MSC in Pool implementation is “dcgmsi” The result files will be put in the Moshell logfile directory under a directory called /dcg/”RNC name”/”date”/ The result files should be checked to ensure there are no outstanding alarms, the hardware status is normal and all required interfaces are operational.




2015-06-08 PA1


9.3.1 Preparations

Verify a detailed design of the SIGTRAN network, detailing all IP addressing, SCTP endpoints and parameters, M3UA associations, Mtp3b signaling routes and parameters for all target nodes is available.

Verify any new RNC-MSC external network interface connections have beenconnected, configured and verified on all switches/routers.

Verify any new RNC-MGW external network interface connections have beenconnected, configured and verified on all nodes.


Verify parameter values NRI Value, Core Network Identity (CNI) and Relative Capacity (CAP) are known for each RANAP (Iu-cs signalling) definition required for the MSC Pool


9.4.1 MSC in Pool Activation in all the RNC

This section requires an understanding of customer network. One need to knowhow the RNCs are connected to their respective MSCs (GB and FT) before you can undefined and redefine the RNCs.

The steps for activating MSC in Pool in an RNC are:

Undefine the existing RANAP definition towards the serving MSC

Set the Network Resource Identifier Length for Circuit-switched traffic

Redefine the RANAP definition towards the serving MSC with new MSC in Pool parameters.

Below is the sample script to undefine the existing RANAP definition.

1. Undefine the existing RANAP-CS This will effect ongoing circuit-switched traffic RNC2:




2015-06-08 PA1

DELETE ( mo "ManagedElement=1,RncFunction=1,Ranap=cs_MSC2" exception none

)

2. Activate the Iu-Flex feature for MSC in Pool. This is done by setting the Network Resource Identifier Length for circuit-switched traffic. Configure the RncFunction with this value according to the data provided in the Network design. RNC2: SET ( mo "ManagedElement=1,RncFunction=1" exception none networkResourceIdentifierLengthCs Integer 8 )3. Redefine the RANAP-CS towards the MSC, using the values from the previousRANAP definition and including the new parameters CNid, NRI and Relative Capacity.

RNC2: CREATE ( parent "ManagedElement=1,RncFunction=1,CnOperator=1,IuLink=1" identity "cs_MSC2" moType Ranap exception none nrOfAttributes 7 cnDomainInd Integer 0 localSccpApRef Ref "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1,SccpApLocal=ranapLocal" remoteSccpApRef Ref "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1,SccpApRemote= cs_MSC2" cnId Integer 1002 networkResourceIdentifier Array Integer 8 3 -1 -1 -1 -1 -1 -1 -1




2015-06-08 PA1

relativeCapacity Integer 70 userLabel String "cs_MSC2" )4. The activation of MSC in Pool in the RNC2 is now complete

5. Repeat Steps 1 to 4 for RNC1 and RNC3, substituting the relevant network data.

9.4.2 Add new RNC to an MSC Pool Area.

Sample script is given below

1. Define the required RANAP-CS for each new MSC RNC2: CREATE ( parent "ManagedElement=1,RncFunction=1,CnOperator=1,IuLink=1" identity "cs_ MSC1" moType Ranap exception none nrOfAttributes 7 cnDomainInd Integer 0 localSccpApRef Ref "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1,SccpApLocal=ranapLocal" remoteSccpApRef Ref "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1,SccpApRemote=cs_MSC1" cnId Integer 1001 networkResourceIdentifier Array Integer 8 2 -1 -1 -1 -1 -1 -1 -1 relativeCapacity Integer 20 userLabel String "cs_MSC1" )CREATE (

parent "ManagedElement=1,RncFunction=1,CnOperator=1,IuLink=1"identity "cs_ MSC3"




2015-06-08 PA1

moType Ranap

exception nonenrOfAttributes 7 cnDomainInd Integer 0 localSccpApRef Ref "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1,SccpApLocal=ranapLocal" remoteSccpApRef Ref "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1,SccpApRemote=cs_MSC3" cnId Integer 1003 networkResourceIdentifier Array Integer 8 4 -1 -1 -1 -1 -1 -1 -1 relativeCapacity Integer 30 userLabel String "cs_MSC3" )2. Define a Signalling Route Set for each new MSC

RNC2: CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1" identity "cs_MSC1" moType Mtp3bSrs exception none nrOfAttributes 2 destPointCode Integer 101 autoReroute Boolean false )CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1" identity "cs_MSC3" moType Mtp3bSrs exception none nrOfAttributes 2 destPointCode Integer 103

autoReroute Boolean false




2015-06-08 PA1

3. Define Mtp3b Access Point for each new MSC

RNC2: CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1" identity "cs_MSC1"

moType Mtp3bApexception none nrOfAttributes 2 routeSetId Ref "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=cs_MSC1" serviceInd Integer 12 )CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1" identity "cs_MSC3" moType Mtp3bAp exception none nrOfAttributes 2 routeSetId Ref "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=cs_MSC3" serviceInd Integer 12

)

4. Define SCCP Access Point for each new MSC RNC2: CREATE ( parent "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1" identity "cs_MSC1" moType SccpApRemote exception none nrOfAttributes 2 mtp3bApId Ref "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp=cs_MSC1" ssN Integer 142 )CREATE ( parent "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1" identity "cs_MSC3" moType SccpApRemote exception none




2015-06-08 PA1

nrOfAttributes 2 mtp3bApId Ref "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp=cs_MSC3" ssN Integer 142 )5. Define M3uAssociations for each new MSC

RNC2: CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1" identity " cs_MSC1" moType M3uAssociation

exception nonenrOfAttributes 10 mtp3bSrsId Ref "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=cs_MSC1" sctpId Ref "ManagedElement=1,TransportNetwork=1,Sctp=1" remoteIpAddress1 String "10.173.137.16" role Integer 0 dscp Integer 10 localPortNumber Integer 2905 autoStartAssociation Boolean true remotePortNumber Integer 2905 remoteIpAddress2 String "10.173.137.80" localIpMask Integer 3 )CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1" identity "cs_MSC3" moType M3uAssociation exception none nrOfAttributes 10 mtp3bSrsId Ref "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=cs_MSC3" sctpId Ref "ManagedElement=1,TransportNetwork=1,Sctp=1" remoteIpAddress1 String "10.173.137.16" role Integer 0 dscp Integer 10 localPortNumber Integer 2905 autoStartAssociation Boolean true remotePortNumber Integer 2905 remoteIpAddress2 String "10.173.137.80" localIpMask Integer 3 )6. Define and enable the Signalling routes for each new MSC




2015-06-08 PA1

RNC2: CREATE ( parent "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=cs_MSC1" identity "cs1_MSC1" moType Mtp3bSr exception none nrOfAttributes 2 linkSetM3uId Ref "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=cs_MSC1" priority Integer 1 )CREATE ( parent "ManagedElement=1,TranTransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=cs_MSC3"

identity "cs1_MSC3"moType Mtp3bSr exception none nrOfAttributes 2 linkSetM3uId Ref "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,M3uAssociation=cs_MSC3" priority Integer 1 )7. Confirm Signalling connections are defined and enabled on the remote MSCsbefore unblocking all Iu-cs signalling connections

8. Unblock the Mtb3b Signalling Routes and M3uAssociations

10 Fallback Procedure- MSC

No.

Activity StartTime

FinishTime

DurationTime(Impact)

Comments

Total Time (~15 mins)1

MSC Pool Fall-Back – 2G Specific Restore Inner and Outer cell relationships

30 min




2015-06-08 PA1

The command files created in section 9.2.2 which restore all inner and outer cell relationships should be executed on each MSC-S. This will return the cell configuration to a ‘Pre MSC Pool’ state. Remove neighboring MSC-S group definitions data fromMSC-Ss outside of pool. MGMGP:MSC=ALL; MGMGE:MSCG=POOL1; MGMGP:MSC=ALL; Remove Enhanced VLR Functionality in MSC outside pool MGCVE:VLR=MSC4,LAI=444-11-22222,NRIV=2&3&4; Remove Equivalent PLMN data in MSC-S 1,2 & 3 The Equivalent PLMN data is duplicated across all pool members. The rollback of this data will includeonly that which was copied from other pool members. MGELP:EPLMNL=ALL; MGELE:EPLMNL=1; MGELP:EPLMNL=ALL; Remove National Roaming Restrictions data in MSC-S 1, 2 & 3 The National Roaming Restrictions data is duplicatedacross all pool members. The rollback of this data will include only that which was copied from other pool members. MGNRP:LAI=ALL; MGNRE:LAI=111-22-3,NRRG=1; MGNRP:LAI=ALL; Turn off Feature INTER-MSC HANDOVER TO MSC POOL in MSCs outside of pool. DBTSP:TAB=AXEPARS,NAME= ADMHOMSCPOOL; SYPAC: ACCESS=ENABLED,PSW=PSW2PAR; DBTRI; DBTSC: TAB=AXEPARS,SETNAME=GSMMMSC,NAME=ADMHOMSCPOOL,VALUE=0; DBTRE: COM; DBTSP:TAB=AXEPARS,NAME= ADMHOMSCPOOL; Restore the Paging parameters in all MSC pool members. The following parameters should be restored to theirpre MSC Pool values. NOTE: only need to restore Paging parameters from MSC-S 2 if not in pool with other BSC's Table 14 Paging Parameters Parameter

Description




2015-06-08 PA1

PAGREP1LA Valid when PAGLATA=0 0 - Indicates that paging in one particularlocation area is not repeated. 1 - Indicates that paging in one particularlocation area is repeated once with either TMSI or IMSI. 2 - Indicates that paging in one particularlocation area is repeated once with IMSI.3 - Indicates that paging is repeated once as global paging with IMSI.

PAGREPCT1LA Valid when PAGLATA=1 0 - Indicates that paging in a location area is not repeated. 1 - Indicates that paging in a location area is repeated with either TMSI or IMSI. 2 - Indicates that paging in a location area is repeated with IMSI. 3 - Indicates that paging is repeated as call delivery LATA paging with IMSI.

PAGREPGLOB 0 - Global paging is notrepeated 1 – Global paging repeated once with IMSI

2 Post health Check 20 min




2015-06-08 PA1

11 Fallback Procedure- BSC

No.

Activity StartTime

FinishTime


Comments

Total Time (~15 mins)1 BSC Fall-Back

Change T3212 timer to 30 minutes in the BSC RLSBP:CELL=ALL; RLSBC:CELL=ALL,T3212=5; RLSBP:CELL=ALL; Move subscribers back to MSC-S 2 The subscribers are returned to their source MSC-Server by setting the MODE parameter on the BSC to BARRED, toward target MSC-Server. This example is from a BSC 2 perspective. RLTDP:MSC=ALL; RLTDC:MSC=MSC1, MODE=BARRED, PART=30, RAND=0; RLTDC:MSC=MSC3, MODE=BARRED, PART=30, RAND=0; RLTDP:MSC=ALL; ALL subscribers registered from the BSC will move inthe interval 2x T3212. Restore Timer T3212 in the BSC. The T3212 timer is set to it’s original value. RLSBP:CELL=ALL; RLSBC:CELL=ALL,T3212=X; RLSBP:CELL=ALL; Turn off MiP routing in the BSC. The value of AXE Parameter MIPROUTE is changed to 0.DBTSP:TAB=AXEPARS,NAME=MIPROUTE; SYPAC: ACCESS=ENABLED,PSW=psw; DBTRI; DBTSC:TAB=AXEPARS,SETNAME=CME20BSCF,NAME=MIPROUTE,VALUE=1; DBTRE: COM; SYPAC: ACCESS=DISABLED; DBTSP:TAB=AXEPARS,NAME=MIPROUTE; Make target MSC-Ss INACTIVE on BSC This example is from a BSC 2 perspective. RLTDP:MSC=ALL; RLTDC:MSC=MSC1,MODE=INACTIVE; RLTDC:MSC=MSC3,MODE=INACTIVE; RLTDP:MSC=ALL; Remove Network Resource Identifier (NRI)

30min




2015-06-08 PA1

The NRI’s are removed from all MSC-S 1, 2 & 3. NOTE: Only need to remove NRI data from source MSC if not in pool with other BSC RRNRE:MSC=ALL; Turn off MiP features in BSC node. The following features should be restored to their pre MSC Pool values Table 18 MiP Feature Values Feature

MiP Value

MIP 1 MIPROUTE 1

2 Post health Check 20min

12 Fallback Procedure - RNC

No.

Activity StartTime

FinishTime


Comments

Total Time (~20 mins)1 RNC Fall-Back

There is no requirement to deactivate the Iu-Flex Feature in the RNC, as the operation of the RNC with one MSC in the Pool is the same as if the MSC Pool Feature is not activated. However, additional MSC-Ss that have been added to the MSC Pool, must be removed. Remove MSC-S This procedure removes an MSC-S, MSC-S 1 as an example, from an existing MSC Pool. 1. Set the priority of all the MSC signalling routes to a low value.

2. Block the signalling routes to the MSC.

3. Delete the signalling routes to the MSC

DELETE ( mo

30 min




2015-06-08 PA1

"ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs=cs_MSC1, Mtp3bSr=cs1_MSC1" exception none ) 4. Delete M3uAssociations for the MSC

DELETE ( mo "ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1, M3uAssociation= cs_MSC1" exception none ) 5. Delete SCCP Access Point for the MSC

DELETE ( mo "ManagedElement=1,TransportNetwork=1,SccpSp=1,SccpScrc=1, SccpApRemote= cs_MSC1" exception none ) 6. Delete Mtp3b Access Point for each new MSC

DELETE ( mo " ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bAp= cs_MSC1" exception none ) 7. Define a Signalling Route Set for each new MSC

DELETE ( mo " ManagedElement=1,TransportNetwork=1,Mtp3bSpItu=1,Mtp3bSrs= cs_MSC1" exception none ) 8. Delete the existing RANAP definition for the MSC.

DELETE (mo




2015-06-08 PA1

"ManagedElement=1,RncFunction=1,CnOperator=1,IuLink=1,Ranap=cs_ MSC1" exception none )

2 Post Health Check 20 min




2015-06-08 PA1

13 Roles & Responsibilities Checklist

Role Name On Site TeamMembers

Contact number

Assessment ofcustomer impact

duringconversion

BTC

ImplementationLeader

ArokkilKishnaprasadTope Kareem

Ericsson +267 73723008

ELS onsitesupport (includeOSS contact)

ArokkilKrishnaprasad

Ericsson +26773702215+26776944739

ImplementationAssistants

ArokkilKrishnaprasad Ericsson / BTC +26776944739

ELS onsite or oncall babysitting

ArokkilKrishnaprasad Ericsson +26776944739

On callbabysitting 2nd

line support

ArokkilKrishnaprasad Ericsson

+26776944739

Decision toabort or

continue theconversionduring

implementation

Kaone Mpodi /Reetsang Mmereki BTC

+26773100072/+26773100016

Outage controland escalationresponsibility

Kaone Mpodi BTC +26773100072

OutageJonas Gidlund

Ericsson / BTC+26773100072




2015-06-08 PA1

escalation




2015-06-08 PA1

14 Implementation ChecklistBelow is a checklist that must be completed during the Customer Meeting. Please tick the boxes when ALL parties have agreed on the action.

Agreed Roles and Responsibilities discussed and agreedupon? Are there any steps that require the presence of the Customer? Are there restricted hours when work cannot be carried out? Are there any mandatory/ operational practices that need to be known about?

What equipment will be impacted as a result of the upgrade?

All Service restoration and escalation procedures are to be available and understood?

Are there any “service” issues that the team should be made aware of before commencing activities?

15 Commencement SignoffAfter completing the previous pages, the Customer representative agrees that the detailed procedures provided are adequate to complete the work, a signature below; indicating acceptance will enable work to commence.

No Changes shall be made without the prior approval of the Customerand ELS representatives.




2015-06-08 PA1

ELS Representative:

Title:

Date:

Signature:

Customer Representative:

Title:

Date:

Signature:




2015-06-08 PA1

16 Completion and AcceptanceThe Customer agrees that the documentation, implementation time plan and implementation checklist specified in the MOP for the above site and any referred attachments have been acknowledged to their satisfaction and acceptance will enable work to commence. No Changes shall be made without the prior approval of the Customer and ELS representatives.

The table below lists all faults experienced during and after the upgrade. A CSR should be raised for any issues experienced after the 24-hr babysitting period.

ELS Representative:

Title:

Date:

Signature:

Customer Representative:

Title:

Date:

Signature:




2015-06-08 PA1

17 Fault Log

Event Type

BLOCK Description Solution / Resp

Status

Date post:	25-Apr-2023
Category:	Documents
Upload:	abm
View:	0 times
Download:	0 times