BSC LEVEL PARAMETER CHANGE

August 5, 2010

METHOD
OF
PROCEDURE

BSC LEVEL PARAMETER CHANGE

Nokia Siemens Networks Pvt Ltd.

MS India
Process & Quality Team

Page 1
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

Document History

Document Author Vipindas Regional BSS vipindas.d@nsn.com

Manager-South
Document Contributor(s)

Document Approver Lalit Sharma National BSS- lalit.sharma@nsn.com

Head
Document Release Authority

Versions
Date Name Version Contents of change
01/08/2010 Vipindas V1.0 Initial Document

Page 2
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

Table of contents
1. Purpose and Scope of Document .................................................................................................4
2. Prerequisite ..................................................................................................................................4
3. Compatibility / Dependencies to other products/system/owner ..................................................... 4
4. Acronym Glossary ........................................................................................................................4
5. Assumptions & Out of Scope details ............................................................................................4
6. Relations with other work instructionns ........................................................................................4
7. Detailed description ......................................................................................................................5
7.1 Detailed job description..........................................................................................................5
7.2 Tools Used. ...........................................................................................................................6
7.3 Impact on Service ..................................................................................................................6
7.4 Identification of the Stakeholders ...........................................................................................6
7.5 Specific Instructions ( Entry / Exit Criteria) .............................................................................6
7.6 Software backup and change control requirements ............................................................... 7
7.7 Pre-Test Plan and expected results .......................................................................................7
7.8 Detailed step-by-step procedures ..........................................................................................7
7.9 Post-Test Plan and expected results.................................................................................... 13
7.10 Roll back Plan ..................................................................................................................13
7.11 Emergency Contact Details .............................................................................................. 14
7.12 Additional Document Reference ....................................................................................... 14
Appendix ............................................................................................................................................15

Page 3
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

1. Purpose and Scope of Document

This technical document covers the activity of BSC Level Parameter Changes in the
network. The purpose of this document is to describe the actions needed for BSC Level Parameter
Changes in the network as requested by the RF team. This document is intended for the use of
Managed services professional only for the purpose of the agreement under which the document is
submitted, and no part of it may be used, reproduced, modified or transmitted without the prior
permission of Nokia Siemens Networks.

2. Prerequisite

An Engineer with detailed knowledge of BSC architecture, Fault Management,

Configuration & Integration of Nokia BSC

3. Compatibility / Dependencies to other products/system/owner

CM tools when used for BSC Level parameter change allows the engineer to accommodate
more work into theoutage hour window. Once the plan is prepared and activated via CM tools,
the engineer is free to initiate otheractivities. The only manual intervention other than preparation
of the plan is the post check process.

4. Acronym Glossary

Table 4.1 Acronym and Glossary

S.No: Key Word Definition

1. TRX Transciever

2. BTS Base Transceiver Station

3. BSC Base Station Controller

5. Assumptions & Out of Scope details

• NA

Page 4
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

6. Relations with other work instructions

• None

7. Detailed description

7.1 Detailed job description

• Open CM editor via CM tools to create a plan for the necessary BSC parameter changes.
• Create an editor view which contains the parameters which are to be changed in the given
BSC by following the procedure listed below
• Right click on editor views
• Select new editor view
• Name the editor view with a suitable name in the name field of the editor view header
• Click on PLMN of the MO class field of the editor view header
• Click on BSC
• Make single or multiple selections on those elements whose parameters need to be
changed and when finished click update
• Now click on the created editor view name on the left side panel (editor views)
• Select all parameters required from the right panel and click update
• The required editor view is now ready
• Next the given data has to be sorted in ascending order of BSC ID, BCF ID in accordance to
the format in the CM editor before posting it into the CM editor application.
• After sorting the data, prepare the data in the format as required by the CM applications.
• BCF format - "PLMN-PLMN/BSC-XXXXXX"
• In CM editor, right click on opened plans and select new plan to create a new plan in CM
editor and name the same. On creation of the new plan,
• Check consistency between both data’s (data provided by RF and the sorted data). The
number of BCFs in the data received from the RF engineer should match the number of
data pasted into the plan.
• Select the appropriate editor view and enter all corresponding required data’s in the
available columns.
• After pasting the values to be changed in spaces available in the plan, the data in the CM
Editor should be cross-examined for the correctness. All values received from the RF
engineer should match the values in the created plan.
• On verification of the data in the CM editor, the plan can be activated via the CM Operations
Manager during the allocated outage time. To activate the plan, select plan in CM
operations manager. Right click, select provision and do the following
• Assign name
• Deselect entire plan option and select all BSC’s in the GSM window
• Deselect prepare plan
• Select provision and choose option activate
• Click on start
• On completion of the activation, the plan needs to be checked for any errors. Fix errors if
any.

Page 5
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

7.2 Tools Used.

(Vendor Platform, Software version, Application Details)

• Tools Used:
1. CM Editor
2. CM Operation Manager
3. Reflection

• Vendor platform: Nokia DX 200

7.3 Impact on Service

• Activity Duration: Based on the Cell quantity.

• Outage Involved: No

• Outage Severity: Total

7.4 Identification of the Stakeholders

• GNSC –CM Team

• RF Team

7.5 Specific Instructions (Entry / Exit Criteria)

Page 6
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

• Check the correct username and password of given BSC

• Check the user rights of particular user name

• Check the permission from customer to activate this parameter

• Post check should be done befote exit

7.6 Software backup and change control requirements

• NA

7.7 Pre-Test Plan and expected results

• Check the data received from authorized RF engineer for correctness & all essential data

• Check for any incorrect or missing values in the data given by circle.

• Check if BSC name specified matches with BSC C-NUM specified

• Check the BSC ID, BCF ID which require the changes in the BSC

7.8 Detailed -by- procedures

Example:

Types of Parameter files

Page 7
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

• PRFILE (General Parameter File)

– Standard features
– Optional features
– Interrogate with MML command ZWOS

• FIFILE (Feature Information Control File)

– Stores optional parameters from the PRFILE
– Interrogate with MML command ZWOI

• PAFILE (BSC Control Parameter File)

– GSM-BSC parameters
– GSM Timers
– Interrogate with MML command ZEGO

Features & Activation status

• ZWOS command :

• ZWOI command:

Page 8
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

• ZEGO command

Page 9
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

Viewing parameters Using NetAct CM Editor:

Page
10
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

Viewing parameters using MML commands in BSC:

ZEQO Output:

Page
11
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

Exporting Parameters using NetAct CM Ops Manager:

Page
12
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

7.9 Post-Test Plan and expected results

• After checking the plan for any errors, the current data has to be checked with
the given data for any discrepancies

7.10 Roll back Plan

• None

Page
13
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

7.11 Emergency Contact Details

Mandatory
Name & Phone No. Contact details,time line Escalation Priority
Drive Test Engineer
RF Engineer
SPOC

Escalation Matrix
Team Lead
GNSC Manager

7.12 Additional Document Reference

• NOLS

• NED of BSC

Page
14
 BSC LEVEL PARAMETER CHANGE
August 5, 2010

Appendix

Page
15