BSS Frequency Plan Change Procedure

FREQUENCY PLAN CHANGE

Document number: DS/BSS/APP/0018 Document issue: 08.10 / EN Document status: Standard Date: 30/JUN/2006

External document

Copyright© 1999 - 2006 Nortel Networks, All Rights Reserved

Printed in France

NORTEL CONFIDENTIAL

The information contained in this document is the property of Nortel Networks. Except as specifically authorized in writing by Nortel Networks, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation and maintenance purposes only.

The content of this document is provided for information purposes only and is subject to modification. It does not constitute any representation or warranty from Nortel Networks as to the content or accuracy of the information contained herein, including but not limited to the suitability and performances of the product or its intended application.

This is the Way. This is Nortel, Nortel, the Nortel logo, and the Globemark are trademarks of Nortel Networks. All other trademarks are the property of their owners.

without notice. Nortel Networks assumes no responsibility for errors that might appear in t.All other brand and


Nortel confidential

DS/BSS/APP/0018 08.10 / EN Standard 30/JUN/2006 Page 2/86

PUBLICATION HISTORY

30/JUN/2006

Issue 08.10 / EN, Standard

Modification for RFF 30452 Network Synchronization support in FPC

10/MAY/2006


CR Q01293414

17/FEB/2006


CR Q01310071-10

25/JAN/2006


CR Q01280836, Q01295567-02

12/JAN/2006


CR Q01286675

28/DEC/2005


RFF 16411

06/DEC/2005


CR Q01216344-02

15/SEP/2005


Update after review


Nortel confidential


31/AUG/2005


Correction CR Q01171653, Q01169815, Q01182651

19/AUG/2005


Update for V16.0, RFF 26606, CR Q01007114-01

06/JUL/2005


Correction CR Q01159167-02

23/JUN/2005


Correction CR Q01159060, Q01159140

15/JUN/2005


Correction CR Q01152804

18/MAY/2005



04/MAY/2005


Additional update for V15.1.1, NFI 319

22/APR/2005


Updated after review.


Nortel confidential


15/APR/2005

Issue 07.01 / EN, Draft

Updated in accordance with “Feature 27426 - Frequency Plan Change – Adaptation for Large Scale Networks”

23/MAR/2004


Update for V15.1

05/FEB/2004

Issue 04.03 / EN, Status


06/JAN/2004


Correction CR Q00517242-01, Q00805709-01

24/SEP/2003


Modification for V15

19/MAR/2003


Correction CR Q00633230-03

16/MAY/2002



29/JAN/2002


Correction CRs Q00225490, Q00225600


Nortel confidential


07/JAN/2002



23/JAN/2001



01/FEB/1999


Creation


Nortel confidential


CONTENTS

1. INTRODUCTION ...........................................................................................................................8

1.1. SUBJECT..................................................................................................................................8

1.2. SCOPE OF THIS DOCUMENT.......................................................................................................8

2. RELATED DOCUMENTS..............................................................................................................9

2.1. APPLICABLE DOCUMENTS..........................................................................................................9

2.2. REFERENCE DOCUMENTS .........................................................................................................9

3. GENERAL DESCRIPTION..........................................................................................................10

3.1. READ CAREFULLY...................................................................................................................10

3.2. PREREQUISITES .....................................................................................................................10

3.3. RESOURCES ..........................................................................................................................10

3.4. TIME ESTIMATES.....................................................................................................................11

3.5. PROCEDURE STEPS ................................................................................................................12

3.6. INPUT FILE SYNTAX .................................................................................................................15

3.6.1 No frequency hopping...................................................................................................15 3.6.2 With frequency hopping ................................................................................................16 3.6.3 Network synchronization...............................................................................................18

3.7. COMMAND FILES HIERARCHY...................................................................................................19

3.7.1 Created directories naming...........................................................................................19 3.7.2 Generated command files naming................................................................................20

3.8. OPERATION OF BSIC/BCCH CONFLICTS .................................................................................22

3.8.1 Command files generated without FPC BSIC/BCCH conflict management.................22 3.8.2 Command files generated with FPC BSIC/BCCH conflict management......................23

3.9. IMPACT OF CELL TIERING ON THE FPC PROCEDURE..................................................................24

3.10. IMPACT OF NETWORK SYNCHRONIZATION FEATURE ....................................................25

4. OPERATION DETAILED DESCRIPTION...................................................................................26

4.1. DESCRIPTION OF PLUG-IN .......................................................................................................26

4.2. DESCRIPTION OF ACTION SEQUENCES .....................................................................................29

4.3. FREQUENCY PLAN RECONFIGUGRATION OPERATIONS ...............................................................30

4.3.1 Prerequisite operations.................................................................................................30 4.3.2 Generation of command files........................................................................................31 4.3.3 Automatic execution of generated command files........................................................32 4.3.4 Manual execution of command files (generated without provision against BSIC/BCCH conflicts) 33 4.3.5 Manual execution of command files (generated with provision against BSIC/BCCH conflicts) 34 4.3.6 Post-check operations ..................................................................................................35

4.4. ROLLBACK OPERATIONS..........................................................................................................36

4.4.1 Manual execution of command files (generated without provision against BSIC/BCCH conflicts) 36


Nortel confidential


4.4.2 Manual execution of command files (generated with provision against BSIC/BCCH conflicts) 37

4.5. FALLBACK RECOVERY OPERATIONS .........................................................................................38

4.5.1 BSC restoration.............................................................................................................38 4.5.2 BDE restoration.............................................................................................................39

5. SHEETS.......................................................................................................................................40

6. ABBREVIATIONS AND DEFINITIONS ......................................................................................75

6.1. ABBREVIATIONS .....................................................................................................................75

6.2. DEFINITIONS ..........................................................................................................................78

7. TYPOGRAPHIC CONVENTIONS...............................................................................................82

7.1. GENERAL CONVENTIONS.........................................................................................................82

7.2. INTERACTIVE TERMINAL SESSIONS...........................................................................................82

7.3. INTERACTIVE GRAPHIC SESSIONS ............................................................................................83

7.4. SEQUENCE TABLE CONVENTIONS.............................................................................................85


Nortel confidential


1. INTRODUCTION

1.1. SUBJECT

This procedure describes the operations needed to modify the frequency plan for an in-service network with or without frequency hopping and if needed to modify Network Synchronization parameters (tnOffset and fnOffset).

1.2. SCOPE OF THIS DOCUMENT

The document applies to an operational BSS (V12, V14, V15 or V16 BSC) and to OMC-R v16.0 (and later releases).

The document is applicable both to e3 and 2G architectures of the BSC.


Nortel confidential


2. RELATED DOCUMENTS

2.1. APPLICABLE DOCUMENTS

[A1] DS/BSS/DPL/0003 “Operation Index List”

[A2] PE/BSS/DD/012098 “Feature 27426 - Frequency Plan Change – Adaptation for Large Scale Networks” V01.06/EN

[A3] 411-9001-007 “Nortel GSM BSS Fundamentals Operating Principles”

[A4] PE/SYS/DD/005115 “15347 Network Synchronisation”

2.2. REFERENCE DOCUMENTS

[R1] DS/BSS/APP/0031 “Cell Tiering activation”

[R2] 411-9001-032 “Nortel GSM OMC-R Routine Maintenance and Troubleshooting”


Nortel confidential


3. GENERAL DESCRIPTION

3.1. READ CAREFULLY

Although the utmost care was taken to preclude any chance of undesirable events during this procedure, it is impossible to foresee all probable happenings. Therefore, if you face a problem or a situation that the procedure does not cover in an explicit and accurate manner, call for assistance.

Note: You can perform this procedure only if no other procedure involving network reconfiguration is in progress on the same OMC-R. A breach in this stipulation may lead to unpredictable results in system operation.

Note: This procedure is not intended for frequency hopping activation or deactivation.

Note: In order to speed up FPC plug-in execution, run the cf_updateSybaseStatistics.sh script before launching the plug-in (refer to [R2] for details.)

Note: The Network Synchronization parameters are applicable only to BSC e3 V15 or later versions.

3.2. PREREQUISITES

All involved sub-systems (OMC and BSS) should be operational.

The tool works with an assumption that the input file being generated by means of CT2K or another convenient engineering tool is organized in the following way: the lines related to one cell are placed one by one and not mixed with the lines describing other cells or separated by the line(s) related to the Network Synchronization parameters modification (input file syntax is described in paragraph 3.6).

Note: An input file contradicting this assumption leads to a faulty command file and, presumably, to command file execution failure.

Note: The plug-in should be launched only under the “oam” user.

3.3. RESOURCES

Note: The FPC procedure is performed from the OMC-R only. No action on the BSS site is necessary.

To prepare and perform the frequency plan change procedure it is necessary to have:

one operator for each OMC-R. The operator must be familiar with BSS operation (OMC-R shutdown, monitoring, observation and so on) and must know basic UNIX commands.

two blank DATs per site for OMC backups.


Nortel confidential


an input data file on one diskette. The input data file can be prepared with the help of the CT2K tool, another convenient engineering tool or typed manually (refer to item 3.6 for the syntax of the input data file).

a local workstation.

login names and passwords for OMC and UNIX accounts.

3.4. TIME ESTIMATES

1. The command file generation time per a BSC depends on the number of frequency changes and is about 15 minutes for a BSC with 700 TRX.

2. The procedure execution time per a BSC depends on the number of frequency changes and is about 9 minutes for a BSC with 700 TRX.

3. Out of service time per cell depends on the number of frequency changes and is less than 1 minute for a cell with 6 TRX.

Note: The above time estimates are given for straightforward procedure progress without fallbacks.


Nortel confidential


3.5. PROCEDURE STEPS

The steps of the FPC procedure are shown below:

Figure 1.– Main algorithm.

The order of the FPC procedure is as follows:

Preliminary checks.


Nortel confidential


The operator performs a number of necessary actions to verify that the network is operational.

This step is performed out of the maintenance window.

Backup of the BDE and all impacted BSCs.

The operator backs up the BDE and all impacted BSCs. Backing up is necessary to make the fallback possible in case of a grave failure.


Generation of command files.

To generate command files the operator runs the FPC tool with an input data file prepared with the help of the CT2K tool, another convenient engineering tool or typed manually (refer to section 3.6 for the syntax of the input data file).

There are the following approaches to command file generation. You can both generate the files with and without provisions against possible BSIC/BCCH conflicts that may result from implementation of a new frequency plan. And you can generate command files with modification of Network Synchronization parameters.

It is up to the operator to decide, which approach to command file generation to use.

Warning: Never perform parallel generation of command files.

Warning: Do not perform generation without provisioning against BSIC/BCCH conflicts if there is at least one BSC 2G on the network.

Warning: Do not perform generation without provisioning against BSIC/BCCH conflicts if there is at least one BTS S4000 on the network.

Warning: If generation without provisioning against BSIC/BCCH conflicts is performed, the version of all BSS subcomponents must be V15.1.1 or later releases.


BSIC/BCCH conflict management deactivation at the OMC-R level.

Note: Execute this step only if the command files have been generated without taking into account BSIC/BCCH conflicts.

The operator runs the NRP tool for CM check activation/deactivation with the purpose to deactivate the CM checks related to BSIC/BCCH conflict management at the OMC-R level.

This step is performed during the maintenance window.

Command file execution.

During this step the operator executes the command files generated by the FPC tool. The way how the generated command files should be executed depends on the category of the generated files (generated with or without provisions against BSIC/BCCH conflicts):


Nortel confidential


o The command files generated with FPC BSIC/BCCH conflict management shall be executed one after another (parallel command file execution is inadmissible).

o The command files generated without FPC BSIC/BCCH conflict management can be executed in parallel mode to decrease the total execution time.


Note: The procedure describes two modes of command file execution: manual and automatic. It is up to the operator to decide, which of the two to use.

BSIC/BCCH conflict management activation at the OMC-R level.

Note: This step is necessary only if the command files have been generated without provisions against BSIC/BCCH conflicts.

The operator executes the NRP tool for CM check activation/deactivation with the purpose of activating the CM checks related to BSIC/BCCH conflict management at the OMC-R level.


The rollback procedure.

In case of troubles during the command file execution step the operator must perform the rollback procedure (to revert the network to the initial state): the operator executes reverse command files either in parallel mode (for the command files generated without provisions against BSIC/BCCH conflicts) or one after another.


The fallback procedure.

In case of any troubles during rollback procedure execution the operator has to perform the fallback procedure to roll the network back to the initial state. There are two types of fallback procedures (perform them in the order listed below):

o Impacted BSCs restoration.

In case of failure during reverse command file execution the operator restores only the BSCs for which reverse command files are unworkable and rebuilds the BSCs.

o BDE restoration.

In case of any troubles during the former step the operator performs BDE restoration (using the backup copy of the BDE being created before new frequency plan applying) and rebuilds all BSCs.



Nortel confidential


3.6. INPUT FILE SYNTAX

3.6.1 NO FREQUENCY HOPPING

For a transceiver without frequency hopping the command line of the input file has the following syntax:

fplan (CellId; LAC; MCC; MNC; NCC; BCC; no; transceiverId : bcch frequency : frequency, ... transceiverId : bcch frequency : frequency)

The command line comprises 4 parts:

CellId (CellIdentity), LAC (LocationAreaCode), MCC

(MobileCountryCode) and MNC (MobileNetworkCode) indicate precisely a cell the frequencies of which change.

NCC, BCC represent a new BSIC for the cell. If no BSIC change is planned, enter the current NCC and BCC.

no is for no frequency hopping.

transceiverId : bcch frequency : frequency fill only one field - either bcch frequency or frequency. Enter the new BCCH frequency into the bcch frequency field, when the transceiver is carrying the BCCH frequency. Enter the new frequency for the transceiver into the frequency field, when the transceiver does not carry the BCCH frequency.

Note: One command line deals with one complete cell. So, the frequency of the transceiver, the transceiverId of which is not mentioned in the command line, will not change.

Example:

In the example below, the BCCH frequency modification applies to transceiver 0 and the modification of the absolute frequency to transceiver 1:

fplan(1200; 20; 466; 92; 6; 2; no; 0:45:,1::53)


Nortel confidential


3.6.2 WITH FREQUENCY HOPPING

Note: The FPC tool is not intended for frequency hopping activation/deactivation.

For a transceiver with frequency hopping the command line of the input file has the following syntax:

fplan (CellId; LAC; MCC; MNC; NCC; BCC; yes; simple; transceiverId; bcch frequency; f1, f2, f3, ..., fn; HSN; channelId: MAIO, ... channelId: MAIO)

The command line comprises several parts:

CellId (CellIdentity), LAC (LocationAreaCode), MCC

(MobileCountryCode) and MNC (MobileNetworkCode) indicate precisely a cell the frequencies of which change.

NCC, BCC represent a new BSIC for the cell. If no BSIC change is planned, enter the current NCC and BCC.

yes stands for the presence of the frequency hopping case.

simple indicates basic frequency hopping configuration (only ‘simple’ is allowed).

transceiverId refers to the transceiver to be modified.

bcch frequency presents the BCCH frequency used in the cell.

f1, f2, f3, ..., fn is basic mobile allocation for the transceiver. Every command line deals with one transceiver. The frequency parameters are separated by commas ",".

HSN is the hoping sequence number used in the transceiver. If no HSN change is planned enter the current HSN.

channelId: MAIO: specifies the value of the maio parameter used on a channel. The parameters of the same channel are separated by colons ":". The parameters of different channels are separated by commas ",".

Note: The FPC procedure can modify only existing frequency hopping objects and can not create new frequency hopping objects. It changes “mobile allocation” and “hopping sequence number” parameters of impacted frequency hopping objects in a cell.

The configuration of frequency hopping is planned on this model:

None of the channels of the transceiver carrying either the BCCH frequency or the absolute frequency is involved in frequency hopping.


Nortel confidential


All channel frequencies of the transceiver carrying the BCCH are set to the BCCH frequency.

The channel parameters of other transceivers are numbered from 0 to 7.

Note: The BCCH frequency can not be included in mobile allocation.

Example:

For the transceiver carrying the BCCH (with no frequency hopping):

fplan (1200; 20; 466; 92; 6; 2; no; 0:75:)

For the transceiver not carrying the BCCH:

fplan (1200; 20; 466; 92; 6; 2; yes; simple; 1; 75; 80,85,90,95; 0; 0:1, 1:1, 2:1, 3:1, 4:1, 5:1, 6:1, 7:1)


Nortel confidential


3.6.3 NETWORK SYNCHRONIZATION

Updating a frequency plan may require, in some cases, update of some network synchronization parameters. In order to lower the loss of service during this update, it is possible to include modification of those parameters in the frequency plan change procedure.

For network synchronization, the command line of the input file has the following syntax:

nSync ( bscId; btsSMId; fnOffset; tnOffset )

bscId, btsSMId fields are used to specify exactly the site impacted by parameters modification.

fnOffset presents a new frame number offset. If no fnOffset change is planned enter the current fnOffset.

tnOffset presents a new timeslot number offset. If no tnOffset change is planned enter the current tnOffset.

One command line deals with one BtsSiteManager.

Note: All fplan(…) lines related to the same cell must NOT be separated by a network synchronization nSync(…) line.

Note: It is recommended to place nSync(…) line at the beginning or at the end of the fplan(…) lines block related to the cells located under the impacted BtsSiteManager.

Example:

In the example below, the modification of fnOffset and tnOffset parameters applies to BSC 12, BTS site manager 3.

nSync (12; 3; 30000; 6)


Nortel confidential


3.7. COMMAND FILES HIERARCHY

The tool generates a structure of directories, the main direct and reverse command files stored in the base directory are specified as an option (for example - /OMC/data/cmdFile/root/oam/nrp_freq_plan_change/<baseDirectory>, where “baseDirectory“ is an argument provided for running the tool or an empty string by default). The structure of the directories created by the tool is shown in the figure below:

The tree of generated directories

3.7.1 CREATED DIRECTORIES NAMING

The tool creates the following directories:

<base directory> serving as the parent directory for automatically created subdirectories and as the storage place for main direct and reverse files consisting of the instructions to execute direct and reverse command files stored in the subdirectories. The makeup of the created directories varies with command file generation options, i.e. whether the BSIC/BCCH conflict management option is selected or not.

With the BSIC/BCCH conflict management option selected the tool creates the following directories:


Nortel confidential


• general used to store direct and reverse command files, command files providing recreation of the adjacent cell handover objects being in temporary conflict, for deletion of those being in temporary conflict and for recreation of those being in permanent conflict for all impacted BSCs.

With the BSIC/BCCH conflict management option not selected the tool creates the following directories:

• BSC_<impacted BSC Id> used to store direct and reverse command files for impacted BSCs (one directory per a BSC).

• alien used to store direct and reverse command files for alien cells.

Note: The list of impacted directories is available in the tool log file.

3.7.2 GENERATED COMMAND FILES NAMING

The tool generates the following command files:

The command files generated in the <base directory> directory include:

• “nrp_freq_plan_change_dir.cmd”, which is the main direct command file consisting of the instructions to execute the direct command files found in subdirectories;

• “nrp_freq_plan_change_rev.cmd”, which is the main reverse command file consisting of the instructions to execute the reverse command files found in subdirectories;

The command files generated in the subdirectories with the BSIC/BCCH conflict management option selected:

• “nrp_freq_plan_change_dir.cmd”, the direct command file containing commands for FPC with or without Network Synchronization parameters setting;

• “nrp_freq_plan_change_rev.cmd”, the reverse command file containing commands for FPC with or without Network Synchronization parameters setting;

• “nrp_recreate_conflicts_dir.cmd”, the command file intended to store the command ensuring re-creation of adjacent cell handover objects being in temporary BSIC/BCCH conflict.

• “nrp_recreate_conflicts_rev.cmd”, the command file intended to store the command providing for deletion of adjacent cell handover objects being in temporary BSIC/BCCH conflict.

• “nrp_permanent_conflicts.cmd”, the command file with the commands allowing recreation of adjacent cell handover objects that are in permanent BSIC/BCCH conflict.

The command files generated in the subdirectories with the BSIC/BCCH conflict management option not selected:


Nortel confidential


• “nrp_freq_plan_change_dir.cmd”, the direct command file containing commands for FPC with or without Network Synchronization parameters setting;

• “nrp_freq_plan_change_rev.cmd”, the reverse command file containing commands for FPC with or without Network Synchronization parameters setting;

Note: If the base directory or subdirectory for an impacted BSC already exists and contains command files the tool renames the files by adding the “_old” string to the existing file name.


Nortel confidential


3.8. OPERATION OF BSIC/BCCH CONFLICTS

3.8.1 COMMAND FILES GENERATED WITHOUT FPC BSIC/BCCH CONFLICT MANAGEMENT

The operation of BSIC/BCCH conflicts includes three steps:

BSIC/BCCH conflict management deactivation at the OMC-R level (to avoid temporary BSIC/BCCH conflicts that can occur during command file execution);

Resolution of permanent BSIC/BCCH conflicts after command file execution;

BSIC/BCCH conflict management activation at the OMC-R level.

3.8.1.1 BSIC/BCCH CONFLICT MANAGEMENT ACTIVATION/ DEACTIVATION AT THE OMC-R LEVEL

BSIC/BCCH conflict management activation/deactivation at the OMC-R level is performed by means of the /MD/base/tools/shell/sem_chk_bcch.sh shell script.

The script can be run with the following options:

- “off” – to deactivate BSIC/BCCH conflict management at the OMC-R level;

- “on” – to activate BSIC/BCCH conflict management at the OMC-R level;

3.8.1.2 RESOLUTION OF PERMANENT BSIC/BCCH CONFLICTS

Resolution of permanent BSIC/BCCH conflicts is achieved by running the /MD/base/tools/shell/cm_freq_plan_BCCHConf.sh shell script after successful execution of the command file. The script checks the system for permanent BSIC/BCCH conflicts, and if the conflicts exist, generates command files for deletion and recreation of the adjacent cell handover objects being in conflict. The operator needs to execute the command file for deletion of adjacent cell handover objects to resolve permanent BSIC/BCCH conflicts. The operator will be informed about deletion of conflicting adjacent cell objects. The operator uses the command file for recreation of adjacent cell handover objects only during the rollback procedure.


Nortel confidential


3.8.2 COMMAND FILES GENERATED WITH FPC BSIC/BCCH CONFLICT MANAGEMENT

The tool manages BSIC/BCCH conflicts that may happen during execution of the direct command file by deleting/recreating the neighboring cells (adjacent cell handover objects).

The tool automatically generates command files for deletion of neighboring cells recreation of deleted neighboring cells in the following directory: /OMC/data/cmdFile/root/oam/nrp_freq_plan_change/<baseDirectory>/general/, where “baseDirectory“ is the parameter passed to the tool as an input argument (which is an empty string, by default):

“nrp_recreate_conflicts_dir.cmd” containing commands for recreation of adjacent cell handover objects involved in temporary BSIC/BCCH conflict. The operator executes the file after applying a new FP (during the direct procedure).

“nrp_recreate_conflicts_rev.cmd” with commands for deletion of adjacent cell handover objects being in temporary BSIC/BCCH conflict. The operator executes the file before applying the old FP (during the rollback procedure).

“nrp_permanent_conflicts.cmd” containing commands for recreation of adjacent cell handover objects being in permanent BSIC/BCCH conflict. You cannot execute the file as its only intent is to inform the operator about the deleted adjacent cell handover objects found in permanent conflict.


Nortel confidential


3.9. IMPACT OF CELL TIERING ON THE FPC PROCEDURE

If the cell tiering feature is activated on all (or some of) impacted cells, the operator should proceed as follows:

1. Deactivate the cell tiering feature on all cells, where it is used.

2. Change the frequency plan on all impacted cells.

3. Recalculate the InterfererType (InterferenceType) parameter for all cells, where the cell tiering feature has been deactivated.

4. Activate the cell tiering feature for all cells, where it has been deactivated.

Note: The “Cell Tiering Activation” plug-in is intended for activation/deactivation of the cell tiering feature and recalculation of the InterfererType (InterferenceType) parameter (refer to [R1] for more information).


Nortel confidential


3.10. IMPACT OF NETWORK SYNCHRONIZATION FEATURE

The FPC tool is not intended for the Network Synchronization feature activation/deactivation, only for frequency plan change with modification of the fnOffset, tnOffset parameters.

When the network is not synchronized or only clock synchronized, the beginning of each frame is independent BTS per BTS, so the change in Mobile Allocation Index (MAI) occurs randomly. Furthermore, the frame number being also independent BTS per BTS, the frequency finally used to carry the frame appears randomly chosen in time, from BTS to BTS.

In case the network is time synchronized, some control of the timeslots number and frame number is available to the operator. The right combination of Network Synchronization parameters and HSN/MAIO can reduce the probability of cochannel and adjacent interference inside the site (refer to [A4] for more information).


Nortel confidential


4. OPERATION DETAILED DESCRIPTION

4.1. DESCRIPTION OF PLUG-IN

Examples of “Command file generation”, “Command file execution”, and “Display files” tabs with description of the parameters are shown below:

The “Command file generation” tab of the plug-in

Parameters Mandatory Type Explanation

Configuration file name Yes Alphanumeric Enter a file name with the path relative to the /CMN/data/plugins/ directory.

Base directory No Alphanumeric

The name of the base directory (that is - directory relative to /OMC/data/cmdFile/root/oam/nrp_freq_plan_change/ directory, where the tool stores generated command files). The empty value is used by default.

BSIC/BCCH conflict management

Yes Enumerated It specifies FPC BSIC/BCCH conflict management is either turned on (“on” value) or off (“off” value).

Meantime value (s) No Alphanumeric It is the “duration” parameter for the “sleep” command to add into command files for 2G BSCs. 1 second is used by default.

Number of lines to use meantime

No Alphanumeric It specifies the number of commands between “sleep” commands in command files for 2G BSCs. 1 line is used by default.


Nortel confidential


The “Command file execution” tab of the plug-in


Base directory No Alphanumeric

The name of the base directory (that is - directory relative to /OMC/data/cmdFile/root/oam/nrp_freq_plan_change/ directory, where the tool stores generated command files). The empty value is used by default.

Number of files to be executed in parallel

No Alphanumeric It specifies the number of command files to be executed in parallel. The parameter is useful only when BSIC/BCCH conflict management is turned off. “10” is used by default.


Nortel confidential


The “Display files” tab of the plug-in


Display the file Yes Alphanumeric The name of the file (with the path relative to the /CMN/data/plugins/ directory) to display.


Nortel confidential


4.2. DESCRIPTION OF ACTION SEQUENCES

Performing FPC procedure steps the operator should follow the order determined by successions of the document chapters presented in the columns of the table below.

FPC procedure

steps

Automatic execution of command files

Manual execution of command files

generated without FPC BSIC/BCCH

conflict management

Manual execution of command files

generated with FPC BSIC/BCCH conflict

management

Followed order of chapters



Prerequisites operations

§4.3.1 §4.3.1 §4.3.1

Command files generation

§4.3.2 §4.3.2 §4.3.2

Command files execution

§4.3.3 §4.3.4 §4.3.5

Post-check operations

§4.3.6 §4.3.6 §4.3.6


Nortel confidential


4.3. FREQUENCY PLAN RECONFIGUGRATION OPERATIONS

4.3.1 PREREQUISITE OPERATIONS

Step | Operation description (Total 43 + ? mn) mn Sheet page

OK / NOK

NOK step

Input Parameters

THE OMC-R IS OPERATIONAL

S1 How to ... 1 41

S2 Check alarms 5 45

bscList =the list of the bscNumber to process

S3 Perform BDA audit 15 60


S4 Check traffic on all BTS sites of the BSC 5 48

bscList =the list of the bscNumber to process phase = 1 param=-OFS

S5 Label DAT, if necessary 2 50

labelName = the name of the DAT label

S6 Backup the OMC-R environment database 15 51

actionType = archive dataType = backup labelName = the name of the DAT label specificDay = the day in format YYYYMMDDHHMM partName = omc

S7 Backup each impacted BSC ? 65

actionType = backup bscList =the list of the bscNumber to process

S8 If the cell tiering feature is active on the impacted cells, prepare configuration files for cell tiering activation/deactivation according to the Cell Tiering Activation procedure

? [R1]

THE FREQUENCY PLAN IS READY TO BE CHANGED


Nortel confidential


4.3.2 GENERATION OF COMMAND FILES

Step | Operation description (Total ? mn) mn Sheet page

OK / NOK

NOK step

Input Parameters

THE FREQUENCY PLAN IS READY TO BE CHANGED

S9 FPC configuration file creation or editing ? 55

plugInName = Frequency Plan Change Plug-in menuItem = “Configuration->NRP” commandToolBar = Display files Display the file = (refer to §4.1 for more details)

S10 Generation of command files with the FPC tool ? 55

plugInName = Frequency Plan Change Plug-in menuItem = “Configuration->NRP” commandToolBar = Command file generation Configuration file name = (refer to §4.1 for more details) Base directory = (refer to §4.1 for more details) BSIC/BCCH conflict management = (refer to §4.1 for more details) Meantime value = (refer to §4.1 for more details) Number of lines to use meantime = (refer to §4.1 for more details)

THE COMMAND FILES ARE GENERATED


Nortel confidential


4.3.3 AUTOMATIC EXECUTION OF GENERATED COMMAND FILES


OK / NOK

NOK step

Input Parameters

THE COMMAND FILES ARE GENERATED

EXECUTE THESE STEPS DURING THE MAINTENANCE WINDOW

S11 Check that Interference Matrix is not running on the network 1 68

param = “network”

S12 If the cell tiering feature is active on the impacted cells, deactivate it executing the phase “CellTiering Activation/Deactivation” of the Cell Tiering Activation procedure

? [R1]

S13 Execution of command files with the FPC tool ? 55 § 4.4

plugInName = Frequency Plan Change Plug-in menuItem = “Configuration->NRP” commandToolBar = Command file execution

Base directory = (refer to §4.1 for more details) Number of files to be executed in parallel = (refer to §4.1 for more details)

NEW FREQUENCY PLAN CONFIGURATION IS READY


Nortel confidential


4.3.4 MANUAL EXECUTION OF COMMAND FILES (GENERATED WITHOUT PROVISION AGAINST BSIC/BCCH CONFLICTS)


OK / NOK

NOK step

Input Parameters

THE COMMAND FILES HAVE BEEN GENERATED WITHOUT PROVISION AGAINST BSIC/BCCH CONFLICTS




S15 If command file /OMC/data/cmdFile/root/cm/freqPlan/freq_plan_REV exists, then rename it:

/bin/mv /OMC/data/cmdFile/root/cm/freqPlan/freq_plan_REV /OMC/data/cmdFile/root/cm/freqPlan/freq_plan_REV.old

1


? [R1]

S17 Deactivate BSIC/BCCH conflict management at the OMC-R level 2 61

parameter = “off”

S18 Frequency plan change through command file execution ? 63 § 4.4

cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ <impacted directory>/nrp_freq_plan_change_dir.cmd

mode = “parallel”

onError = “stop”

Note: “baseDirectory“ is the parameter passed to the tool as an input argument (the default argument is an empty string)

Note: impacted directories are listed during generation of the command files.

S19 Generate a command file for resolution of permanent BSIC/BCCH conflicts ? 62 § 4.4

S20 Resolution of permanent BSIC/BCCH conflicts through command file execution

? 63 § 4.4

cmdFileList = /root/cm/freqPlan/freq_plan

mode = “one after another”


S21 Activate BSIC/BCCH conflict management at the OMC-R level 2 61

parameter = “on”

THE NEW FREQUENCY PLAN CONFIGURATION IS READY


Nortel confidential


4.3.5 MANUAL EXECUTION OF COMMAND FILES (GENERATED WITH PROVISION AGAINST BSIC/BCCH CONFLICTS)


OK / NOK

NOK step

Input Parameters

THE COMMAND FILES ARE GENERATED WITH PROVISION AGAINST BSIC/BCCH CONFLICTS





? [R1]

S24 Frequency plan change through command file execution ? 63 § 4.4

cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ general/nrp_freq_plan_change_dir.cmd




S25 Recreation of temporary BSIC/BCCH conflicts through command file execution

? 63 § 4.4

cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ general/nrp_recreate_conflicts_dir.cmd




THE NEW FREQUENCY PLAN CONFIGURATION IS READY


Nortel confidential


4.3.6 POST-CHECK OPERATIONS


OK / NOK

NOK step

Input Parameters

THE NEW FREQUENCY PLAN CONFIGURATION IS APPLIED (POST-CHECK OPERATIONS TO PERFORM)

S26 Check alarms 5 45


S27 Check traffic on all BTS sites of the BSC ? 48 § 4.4

bscList =the list of the bscNumber to process phase = 2 param=-OFS

S28 If the cell tiering feature is active on the impacted cells, recalculate the InterfererType parameter executing the phase “InterfererType (InterferenceType) Update” of the Cell Tiering Activation procedure

? [R1]

S29 If the cell tiering feature is active on the impacted cells, activate it executing the phase “CellTiering Activation/Deactivation” of the Cell Tiering Activation procedure

? [R1]

S30 Perform BDA audit 15 60 § 4.4


S31 If needed purge oam user files 1 67

S32 Label DAT, if necessary 2 50

labelName = the name of the DAT label

S33 Backup the OMC-R environment database 15 51

actionType = archive dataType = backup labelName = the name of the DAT label specificDay = the day in format YYYYMMDDHHMM partName = omc

THE NEW FREQUENCY PLAN CONFIGURATION IS APPLIED (POST-CHECK PERFORMED )


Nortel confidential


4.4. ROLLBACK OPERATIONS

4.4.1 MANUAL EXECUTION OF COMMAND FILES (GENERATED WITHOUT PROVISION AGAINST BSIC/BCCH CONFLICTS)


OK / NOK

NOK step

Input Parameters

IF A PROBLEM OCCURS DURING COMMAND FILE EXECUTION WITH COMMAND FILES GENERATED WITHOUT BSIC/BCCH CONFLICTS HANDLING PROVISION


R1 Deactivate BSIC/BCCH conflict management at the OMC-R level 2 61

parameter = “off”

R2 If the following reverse command file exists, then execute it ? 63 § 4.5

cmdFileList = /root/cm/freqPlan/freq_plan_REV


onError = “continue”

R3 Execute the command file for reverse frequency plan change ? 63 § 4.5

cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ <impacted directory>/nrp_freq_plan_change_rev.cmd

mode = “parallel”



Note: impacted directories are listed during generation of command files.

R4 Activate BSIC/BCCH conflict management at the OMC-R level 2 61


R5 If the cell tiering feature is active on the impacted cells, activate it executing the phase “CellTiering Activation/Deactivation” of the Cell Tiering Activation procedure

? [R1]

R6 Perform BDA audit 15 60 § 4.5


R7 If needed purge oam user files 1 67

THE OLD FREQUENCY PLAN CONFIGURATION IS RESTORED

Note: After a successful rollback you may still find that your system operates unsatisfactory and want to revert the system to the initial state. You can do this by performing the fallback recovery procedure (see section § 4.5).


Nortel confidential


4.4.2 MANUAL EXECUTION OF COMMAND FILES (GENERATED WITH PROVISION AGAINST BSIC/BCCH CONFLICTS)

Step | Operation description (Total 16 + ?? mn) mn Sheet page

OK / NOK

NOK step

Input Parameters

IF A PROBLEM OCCURS DURING COMMAND FILE EXECUTION WITH THE COMMAND FILES GENERATED WITH THE BSIC/BCCH CONFLICTS HANDLING OPTION


R8 Execute the command file for deletion of temporary BSIC/BCCH conflicts ? 63 § 4.5

cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ general/nrp_recreate_conflicts_rev.cmd




R9 Execute the command file for reverse frequency plan change ? 63 § 4.5

cmdFileList = /root/oam/nrp_freq_plan_change/<baseDirectory>/ general/nrp_freq_plan_change_rev.cmd




R10 If the cell tiering feature is active on impacted cells, activate it executing the phase “CellTiering Activation/Deactivation” of the Cell Tiering Activation procedure

? [R1]

R11 Perform BDA audit 15 60 § 4.5


R12 If needed purge oam user files 1 67


Note: After a successful rollback you may still find that your system operates unsatisfactory and you wish to revert to the system initial state. You can do this by performing the fallback recovery procedure (see section § 4.5).


Nortel confidential


4.5. FALLBACK RECOVERY OPERATIONS

4.5.1 BSC RESTORATION

Step | Operation description (Total 48 +? mn) mn Sheet page

OK / NOK

NOK step

Input Parameters

IF A PROBLEM OCCURS DURING THE ROLLBACK


F1 Restore each impacted BSC ? 65 § 4.5.2

ActionType = restore bscList =the list of the BSC numbers to process

F2 Perform BDA audit 15 60


F3 If the BDA audit is NOK: rebuild the BDA 30 43

bscList =the list of the bscNumber with the BDA audit NOK modeLine = On-line automatic

F4 Activate BSIC/BCCH conflict management at the OMC-R level 2 61


F5 If needed purge oam user files 1 67



Nortel confidential


4.5.2 BDE RESTORATION

Step | Operation description (Total 63 mn) mn Sheet page

OK / NOK

NOK step

Input Parameters

IF A PROBLEM OCCURS DURING BSC RESTORATION: RESTORE THE DATABASE


F6 Restore the OMC-R database 15 51

actionType = restore dataType = backup labelName = the name of the DAT label specificDay = the day in format YYYYMMDDHHMM partName = omc

F7 Perform BDA audit 15 60


F8 If the BDA audit is NOK: rebuild the BDA 30 43

bscList =the list of the bscNumber with the BDA audit NOK modeLine = On-line automatic

F9 Activate BSIC/BCCH conflict management at the OMC-R level 2 61


F10 If needed purge oam user files 1 67



Nortel confidential


5. SHEETS

The operation sheets are arranged not in the order of execution. Therefore, always refer to an appropriate sequence table to determine what sheet is the next to execute and the values of the necessary input parameters.

The sheets included in this procedure are also applicable to other procedures as well to other hardware configurations. For this reason, some sheets may contain conditional sections or sentences that apply only to other procedures.


Nortel confidential


HOW TO . . .

PRESENTATION The purpose of this sheet is to provide a detailed explanation of how you can perform some basic operations, that may become necessary as you go on through your procedure.

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation. The BSS is operational.

ACTIONS

ON THE LOCAL OMC-R WORKSTATION: O1. How to open an omc shell window on a workstation: On the background menu:

SELECT « Access to UNIX » Then, enter your username (omc, root ...) and password. O2. How to remotely log on to the active server from a workstation:

O2.1. Open an omc shell window. O2.2. Go to this window and remotely log on to the active server:

Under omc login:

... (omc) % rlogin actServerName ↵

actServerName: hostname of the active server O3. How to open a session log:

GOTO « OMC-R Browser » SET « View » = Logical SELECT « Administration » SELECT « user session log... »

O4. How to find an active server:

GOTO « OMC-R Browser » SET « View » = Logical SELECT_OBJ « MD-R » SELECT « Objects - Display|Set »

Locate the managerServer parameter.

The value of this parameter is the hostname of the active server.


Nortel confidential


O5. How to open a notification window:

GOTO « OMC-R Browser » SET « View » = Logical SELECT « Fault » SELECT « Notification monitor...»

O6. How to change your working directory to the oam directory:

O6.1. Create the oam directory if not done yet during the previous steps.

Under omc login:

... (omc) % mkdir /home/omc/oam ↵

O6.2. Change the working directory to the oam directory.

Under omc login:

... (omc) % cd /home/omc/oam ↵

FINAL STATUS Now you know how to perform the required basic operations.


Nortel confidential


BDA REBUILD

PRESENTATION The purpose of this sheet is to detail how you can rebuild BDA (2G BSC) or MIB (e3 BSC). The term BDA is commonly used to denote 2G and e3 BSC database even if the e3 BSC database is refered to as MIB.

INPUT PARAMETERS bscList The list of bscNumber to process. modeLine This parameter indicates the way we achieve BDA on-line reset. (On-line automatic | On-line commanded | Fallback)

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation.

ACTIONS

ON THE LOCAL OMC-R WORKSTATION: 1. If not done yet, log on to the OMC-R as the administrator user. 2. For each BSC the bscNumber of which is on bscList : { Remotely log on to the active server if not done yet (see sheet How to...). } endfor 3. In parallel for each bscNumber on bscList: { In the shell window dedicated to the BSC bscNumber,

3.1 Change the working directory to the oam directory (see sheet How to...). 3.2 Build the BDA.

3.2.1 If modeLine = On-line automatic: {

Under omc login:

... (omc) % /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber

-A ↵

This tool performs BDA on-line reset, builds and activates new BDA. Though, possibly out of the maintenance window at the beginning of tool execution, you may find yourself in the maintenance window at the end of BDA build. So this action is started a few minutes before the maintenance window begins.

SERVICE INTERRUPTION!!! This takes a while. Continue with another BSC. } endif

3.2.2 If modeLine = On-line commanded: {


Nortel confidential


Under omc login:

... (omc) % /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber -C ↵

This tool resets BDA on-line and builds BDA. You may be out of the maintenance window during execution of this tool. This takes a while. Continue with another BSC and come back into this window when the BDA is built to run the next tool.

Under omc login:

... (omc) % /usr/local/oam/bin/ds_activateNewBDA.sh -BbscNumber

↵

This tool activates the newly built BDA. So, this action must be performed inside the maintenance window.

SERVICE INTERRUPTION!!!

This takes a while. Continue with another BSC. } endif

3.2.3 If modeLine = Fallback: {

Under omc login:

... (omc)% /usr/local/oam/bin/ds_buildBDAOnLine.sh -BbscNumber -F –A ↵

This tool builds BDA and automatically activates new BDA. This takes a while. Continue with another BSC. } endif

} endfor

TROUBLESHOOTING 1. See the log file /var/local/oam/bscNumber.ds_buildBDAOnLine.log. 2. See the log file /var/local/oam/bscNumber.ds_activateNewBDA.log. 3. In case of trouble, investigate or perform fallback recovery.

FINAL STATUS The BDA is reset and built.


Nortel confidential


BSS ACTIVE ALARMS CHECK

PRESENTATION The purpose of this sheet is to provide a detailed explanation of how to check active alarms on BSS. Run the checks of this sheet periodically in order to detect pending alarms. Though a special objective of the sheet operations is to verify if new alarms have appeared after the latest manipulations with the network operation (upgrade, reconfiguration...). If this is true fallback recovery is necessary.

INPUT PARAMETERS bscList The list of bscNumber to process

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation. The dedicated bscMdInterface object is operational for the BSC to process.

ACTIONS

ON THE LOCAL OMC-R WORKSTATION: 1. If not done yet, log on to the OMC-R MMI as administrator. 2. For each BSC the bscNumber of which is on bscList: Remotely log on to the active

server if not done yet (see sheet How to...). 3. In parallel for each bscNumber on bscList: {

In the shell window dedicated to BSC bscNumber, run the alarms check tool:

Under omc login:

... (omc) % /usr/local/oam/bin/ds_checkAlarm.sh -BbscNumber ↵

The tool performs the following tasks: Displays the cumulated table of all alarms for the current BSS.

} endfor 4. For each BSCe3 the bscNumber of which is on bscList: { Check the fault "ITM LED TROUBLE" from the “Fault – Notification log…”

From OMC side GOTO « OMC R Browser (...) » SELECT_OBJ « Fault » SELECT « Notification log »


Nortel confidential


When S/W is reporting “ITM LED TROUBLE”, it usually indicates a fault in communication with IEM's ITM that is former to the upgrade (the SPI bus from the IEM's processor to ITM is locked) This may lead to a situation when on resetting the board the IEM is unable to read its slot id from the backplane and cannot communicate with CEM. Check in the Notification log if some of the board of your TCU or BSC have the Notification (2032) MISCELLANEOUS SPM ALARM with the manufacturer information corresponding to ITM LED TROUBLE. In such a case, remove the faulty card, wait for 30 sec and plug this card back in. Repeat this step if you have several cards causing such a notification.

}


Nortel confidential


TROUBLESHOOTING 1. See the log file: /var/local/oam/bscNumber.ds_checkAlarm.log for details

about alarms. 2. In case of Critical or Major active alarms investigate and fix the on-site equipment. 3. If new alarms appear after network operations (upgrade, reconfiguration...),

perform fallback recovery to neutralize the effects of the corresponding faulty equipment or operation.

4. If you face problems while performing troubleshooting, call TAS.

FINAL STATUS Remaining active alarms of the BSS are analyzed and saved in the log file.


Nortel confidential


TRAFFIC OBSERVATION CHECK

PRESENTATION The purpose of this sheet is to detail a traffic observation check performed at the BTS (cell) level, using the C1611 observation counter (TCH allocation). The idea is to compare 2 successive observations (e.g. before and after a network operation) in order to detect any unexpected traffic allocation changes at the BTS level.

INPUT PARAMETERS bscList The list of bscNumber to process. phase The context in which the check is undertaken:

1 = before a major network operation (upgrade, reconfiguration...). 2 = after a major network operation (upgrade, reconfiguration...). 3 = as preventive maintenance.

param Type of observation: - OFS = Fast statistic observation. - ORT = Real time observation. - OGS = General statistic observation.

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation. The dedicated bscMdInterface object is operational for the BSC to process. The mdScanner object has been created on the dedicated BSC object. WARNING: With traffic available, let the mdScanner run for at least one complete

"mdGranularityPeriod" period.

ACTIONS

ON THE LOCAL OMC-R WORKSTATION: 1. If not done yet, log on to the OMC-R as the administrator user. 2. For each bscNumber in bscList: {

2.1. Remotely log on to the active server if not done yet (see sheet How to...). 2.2. Run the observation tool:

Under omc login:

... (omc) % /usr/local/oam/bin/ds_cellObservation.sh -BbscNumber param

↵


Nortel confidential


- If phase = 1: Note (or save to a file) all C1611 counters at « 0 » in the list, if any. - If phase = 2: If there are C1611 counters at « 0 », compare them with those in the

list obtained during phase 1. - If phase = 3: Note (or save to a file) all C1611 counters at « 0 » in the list, and

compare them with the latest results (saved during the latest BSS maintenance checks).

} endfor

TROUBLESHOOTING 1. If the tool execution has failed, check:

- If the "fast Statistic" or "real Time" or "general Statistic" mdScannerType is present (according to the observation type input parameter).

- If the "mdGranularityPeriod" observation period is not too long. 2. If phase = 2, if no cell is carrying traffic and all investigations fail, call TAS or perform a

fallback recovery. 3. If phase = 3, if some cells are still not carrying traffic, it may be a symptom of an

equipment failure. Search for the faulty equipment.

FINAL STATUS Traffic observation at the cell level is checked or recorded.


Nortel confidential


LABELLING NEW DAT

PRESENTATION The purpose of this sheet is to explain how you can label new DAT for subsequent OMC-R data archiving, if DAT is used for backup. Once the DAT is labelled, you can use it for several backups. Note that when you write a DAT label, all data recorded on the DAT are erased without confirmation. Required resources: 1 DAT

INPUT PARAMETERS labelName The name of the volume label written on DAT

INITIAL STATUS The OMC-R may be running or not. An omc UNIX session is available on an active server.

ACTIONS 1. If not done yet, open a shell session working as the omc user on an active server. 2. Insert DAT (without protection) into the DAT drive. 3. Check if the DAT is not labeled yet:

Under omc login on the server:

... (omc) % /CMN/base/exe/cf_save_tool.x -o consult ↵

...

4. Execute the following tool:

This action erases all previously saved data, so make sure you use the right DAT.

Under omc login on the server:

... (omc) % /CMN/base/exe/cf_save_tool.x –l labelName -o labelize ↵

...

FINAL STATUS The DAT is labeled.


Nortel confidential


OMC-R DATA ARCHIVING AND RESTORATION

PRESENTATION The purpose of this sheet is to describe:

• OMC-R environment data archiving/restoration. • The process of archiving/restoration of OMC-R daily data (observations, alarms...)

previously collected on a specific day. • Retrieval of OMC-R configuration files.

All archiving and restoration operations mentioned above are performed from the command line of the UNIX operating system. OMC-R environment data may be backed up either on DAT or NFS. For details of how to deal with each of the backup media types see the following manual:

411-9001-032 Nortel GSM OMC-R Routine Maintenance and Troubleshooting Required resources if the backup server is not used as the backup media (back up on DAT):

• 1 labelled DAT (for data archiving) • DAT with the previous data archive (for restoration)

Required resources if the backup server is used as the backup media (back up on NFS):

• a mounted file system handled by a backup server

INPUT PARAMETERS actionType The type of action (archive | restore | retrieve_cfg | label | consult | list). dataType The type of data (backup | fault | obs | trace | other). labelName The name of the media (DAT or file system) label (single word). specificDay The date of the handled data: (YYYYMMDDHHMM for backups | YYYYMMDD for other data types). partName The application part (omc | md).

INITIAL STATUS If actionType = restore and dataType = backup: the OMC-R is halted. If actionType = retrieve_cfg: the OMC-R is halted. An omc session is available on the active server.

ACTIONS 1. If using the DAT device rather than the mounted file system for the media device, and if

not done yet, insert the labeled DAT (without write protection if archiving) into the DAT drive of the active server.

2. If not done yet, working as omc, open a shell session on an active server.


Nortel confidential


3. If not done yet and if actionType = restore, stop the application on the OMC-R server(s):

Under omc login on the OMC-R active server:

... (omc) % appstop std ↵

... OMC- R is completely stopped ... (omc) %

4. If you don’t know whether the media is labeled or not, and in order to find out the label name (labelName):

Under omc login on the active server:

... (omc) % /CMN/base/exe/cf_save_tool.x -o consult ↵ label : labelName

5. If actionType = archive, and the media are not labeled:


... (omc) % /CMN/base/exe/cf_save_tool.x –l labelName -o labelize ↵

...

6. If actionType = restore, and you don’t know the value of the specificDay parameter:


... (omc) % /CMN/base/exe/cf_save_tool.x -o list -l labelName ↵ label : labelName partName dataType specificDay partName dataType specificDay ...

7. Launch the archive/restore tool:


... (omc) % /CMN/base/exe/cf_save_tool.x -o actionType [-l labelName]

[-y dataType] [-t specificDay] [-p partName] ↵

8. Wait till the tool execution is over:

dataType successfully completed

9. If you use the DAT device rather than the mounted file system for the storage media, eject the DAT from the DAT drive and make it write-protected by sliding the white tab open.

10. If actionType = restore, restart the OMC-R application on the OMC-R server(s):

Under omc login on the OMC-R active server:

... (omc) % /usr/local/oam/bin/ds_startOmc.sh –S -nodbcc ↵

... <-----... – Running sequence – MM/DD/YY HH:MM:SS -----> ...


Nortel confidential


11. If actionType = restore, and the OMC-R version is greater than or equal to V14.3: EFT check: From OMC side

GOTO « OMC R Browser (...) » SET « View » = Logical

SELECT_OBJ « MD-R » SELECT « Configuration - EFT - List empty deliveries directories on MD »

SELECT « Apply »

The results are displayed in the Session Log window. Using the list displayed in the Log session re-download all missing "Not accessed" EFTs and the EFTs referenced by the BSC. Example: List deliveries-md: object = (md);

03/18/03 15:47:50 47164351330000163 iss 47.164.141.78 SUCCEEDED

(completed) object md deliveryList ExeSoftName ExeSoftId Directory state Referenced BSCs

B3G14030000D 9 Not accessed 14 B3G14000007 11 Not accessed 14 B3G14000006 12 Not accessed Not used BS4124734C 2 Not accessed Not used TC314000001 10 Not accessed Not used TCB12A203 0 Not accessed Not used TCB6B0303 3 Not accessed 39 BC214E040 5 Not accessed Not used BCF14E010 4 Not accessed Not used PIC12C191 1 Not accessed 39 CBC14E030 6 Not accessed Not used TRX14E011 7 Not accessed Not used

CDR14E102 8 Not accessed Not used


Nortel confidential


EFT downloading from CD-ROM Insert the CD-ROM with correct EFT into the CD-ROM drive of the OMC-R active server. Install the EFT: GOTO « OMC R Browser (...) »

SET « View » = Logical SELECT_OBJ « OMC-R » SELECT « Configuration - EFT - Install Delivery from CD-ROM » SELECT « EFT to download »

SELECT « Apply » Wait for the message “(completed)" in the session log window. When the files copying process is over, the system outputs: "command succeeded". Remove the CD-ROM from the drive.

TROUBLESHOOTING See the log file /CMN/base/diagnostic/diag_savetool.

FINAL STATUS The OMC-R data are archived (or restored).


Nortel confidential


PLUG-IN EXECUTION

PRESENTATION The purpose of this sheet is to describe how to launch the plug-in tool.

INPUT PARAMETERS plugInName Defines the plug-in name to be launched menuItem Defines the plug-in menu location commandToolBar The specific tool bar used to launch the plug-in application inputParameters Specific tool parameters to use

Note: This is an optional parameter, the name of which is the one of the plug-in itself.

INITIAL STATUS The OMC-R is running and the MMI is available on the OMC-R workstation.

ACTIONS 1. Launch the plug-in window:

GOTO « OMC-R Browser » SELECT « menuItem » SELECT « plugInName »

2. Once the plug-in window is displayed: GOTO « plugInName »

Refer to the plug-in window template in the picture below illustrating the plug-in functions.


Nortel confidential


Note: The displayed plug-in parameters vary from plug-in configuration to plug-in configuration - ds_plugInName.cfg is the template file for the plug-in. You must edit this file to customize the plug-in. Keeping this file name is not necessary, though you must preserve its internal structure. - The Log file name is the log file of the plug-in. - Some parameters may have the drop-down list button (as Parameter #1 in the example above), while other look like a simple edit field, which is modifiable (such as Parameter #2 in the example mentioned above).

The 'Apply' button allows launching command tool execution

The 'Close' button allows closing the window (without tool interruption)

The 'Procedure' button displays the procedure

The 'Description' button displays plug-in on-line help

Command tool bar

Parameters area


Nortel confidential


If commandToolBar = Display files

3. If not done yet and if it exists, modify the configuration file of the plug-in: 3.1 Select the configuration file using the File browser Item:

GOTO « Display files » (on the command tool bar)

SELECT « File browser »

SELECT « Input files » (from the File type field)

SELECT « plugInName » (from the Directories field)

SELECT « ds_plugInName.cfg » (from the Files field)

Directories field

Files field

Files type field


Nortel confidential


SELECT « Apply »

3.2 Open the configuration file using the File browser Item: GOTO « Display files » (on the command tool bar)

SELECT « Apply »

GOTO « Edit[.../ds_plugInName.cfg] » Use the up-down, left-right scroll bars to move inside the file.

3.3 Modify the configuration file and save it before closing!

Else

4. Select the accurate Command tool bar to launch an appropriate command:

SELECT « Command commandToolBar »

5. Use the plug-in tool:

5.1 Enter all necessary information for each parameter, setting the parameter accurate value before launching the tool.

5.2 Launch the plug-in tool:

SELECT « Apply »

End If

TROUBLESHOOTING 1. In case of trouble inspect the log file:

GOTO « plugInName » (on the command tool bar) SELECT « Display Files » SELECT « Files browser »


Nortel confidential


SELECT « Temporary log files » (from the File type field)

SELECT « ds_pluginName.log » SELECT « Apply »

GOTO « plugInName » SELECT « Apply »

GOTO « View[.../ds_plugInName.log] »

Use the up-down, left-right scroll bars to move inside the file.

FINAL STATUS The execution is completed with no error messages in the log file.


Nortel confidential


BDA AUDIT

PRESENTATION The purpose of this sheet is to provide a detailed explanation of how you can check reconciliation between BDE (OMC-R database) and BDA (2G BSC) or MIB (e3 BSC). The term BDA is used as a common name for 2G and e3 BSC database even if e3 BSC database is often referred to as MIB.

INPUT PARAMETERS bscList The list of bscNumber to process

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation. The dedicated bscMdInterface object is operational on the BSC to process.

ACTIONS

ON THE LOCAL OMC-R WORKSTATION: 1. If not done yet, log on to the OMC-R MMI as administrator. 2. For each BSC the bscNumber of which is on bscList: { Remotely log on to the active server if not done yet (see sheet How to...). } endfor 3. In parallel for each bscNumber on bscList: { In the shell window of BSC bscNumber run the audit tool:

Under omc login:

... (omc) % /usr/local/oam/bin/ds_auditBDA.sh -BbscNumber ↵

The tool performs BDA audit and displays “OK” if no discrepancies are found, otherwise “KO”. This takes a while.

} endfor

TROUBLESHOOTING 1. See the log file: /var/local/oam/bscNumber.ds_auditBDA.log. 2. No data mismatch is acceptable. The revealed discrepancies require update.

FINAL STATUS The OMC-R database & BSC databases (BDE & BDA) are consistent.


Nortel confidential


BSIC/BCCH CONFLICT MANAGEMENT DEACTIVATION/ACTIVATION AT THE OMC-R LEVEL

PRESENTATION The purpose of this sheet is to describe the deactivation/activation of the BSIC/BCCH conflict management at the OMC-R level.

INPUT PARAMETERS parameter stands for option – “off” for the BSIC/BCCH conflict management

deactivation or “on” for the BSIC/BCCH conflict management activation.

INITIAL STATUS The OMC-R is running. An omc shell session in UNIX is available on the active server.

ACTIONS 1. If not done yet, open a shell session working as omc on the active server. 2. Execute the following tool:


... (omc) % /MD/base/tools/shell/sem_chk_bcch.sh parameter ↵

...

FINAL STATUS The BSIC/BCCH conflict management is deactivated/activated at the OMC-R level.


Nortel confidential


RESOLUTION OF PERMANENT BSIC/BCCH CONFLICTS

PRESENTATION The purpose of this sheet is to explain the generation of command files intended for resolution permanent BSIC/BCCH conflicts resulting from the application of the new frequency plan.

INPUT PARAMETERS None.


ACTIONS 1. If not done yet, open a shell session working as omc on the active server. 2. Execute the following tool:


... (omc) % /MD/base/tools/shell/cm_freq_plan_BCCHConf.sh oam ↵

...

FINAL STATUS The command files for resolution of permanent BSIC/BCCH conflicts are generated.


Nortel confidential


TOOL-AIDED EXECUTION OF COMMAND FILES

PRESENTATION The purpose of this sheet is to describe how command files can be executed by means of an execution tool.

INPUT PARAMETERS cmdFileList The list containing the names of the command files to execute. mode The option indicating how the command files should be executed – in parallel or

sequentially, one by one. onError The option defining an error policy for the execution time (“stop” aborts execution

when an error occurs and “continue” sets the mode when execution goes on despite possible errors).


ACTIONS 1 Execution of command files on the active server

1.1 If mode = “parallel”: { In parallel for each fileName in the cmdFileList:

1.1.1 Remotely log on to the active server if there is no free active session (see sheet How to...). Use one session for one thread of the parallel execution.

1.1.2 Run the execution tool:

If onError = “stop”: {


... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh -FfileName –S ↵

} else

{


... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh –FfileName ↵

} Note: the maximum number of command files executed in parallel is restricted to 15.


Nortel confidential


Note: if a command file execution fails do not launch other command files – just wait for the completion of those already processed.

} 1.2 If mode = “one after another”: {

1.2.1 Remotely log on to the active server if not done yet (see sheet How to...).

For each fileName in the cmdFileList: 1.2.2 Run the execution tool:

If onError = “stop”: {


... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh -FfileName –S ↵

} else

{


... (omc) % /usr/local/oam/bin/ds_executeCmdFile.sh –FfileName ↵

}

Note: execution of the next command file starts after completion of the previous command file.

} 2. Verify that execution of the command completed successfully.

TROUBLESHOOTING 1. See the log file: /var/local/oam/.<processId>.ds_executeCmdFile.log.

FINAL STATUS The command file is executed on the OMC-R.


Nortel confidential


BSC DATABASE BACKUP/RESTORATION

PRESENTATION This BSC per BSC Backup/Restoration provides a way to save and restore BDE data associated with a single BSC. Remember that the tool used here neither restores nor saves the mdScanner, traceControl, callPathTrace objects and the SMS-CB information.

• All the operations described here are performed in the command line of the UNIX OS.

• During the BSC restoration configuration requests for the BSC are not allowed. In case of a configuration request the system responds with the following error message "A request is already being processed for this BSC" displayed at the MMI level.

• Restoration is possible only on the OMC-R where backup is done.

• Only one instance of the tool can run at a time.

INPUT PARAMETERS actionType The action option ( backup | restore ) bscList The list of bscNumber to process.

INITIAL STATUS An omc session is available on the active server. The OMC-R tasks and the Sybase server application are active and running.

ACTIONS

ON THE LOCAL OMC-R WORKSTATION:

1. If not done yet, log on to the OMC-R as the administrator. 2. If not done yet, remotely log on to the active server (see sheet How to...).


Nortel confidential


3. For each bscNumber on bscList: {

Run the tool:


... (omc) % /usr/local/oam/bin/ds_restoreBsc.sh -OactionType -BbscId ↵

If actionType = backup:

The result is the 2 identical files containing the dump of the BSC bscId: "/MD/data/cm/cm_restoreBSC_bscId.dat" – the default file; "/MD/data/cm/cm_restoreBSC_bscId.dat.YYYYMMDDHHMMSS" – the

backup file.

Note: The generated "/MD/data/cm/cm_restoreBSC_bscId.dat" and "/MD/data/cm/cm_restoreBSC_bscId.dat.YYYYMMDDHHMMSS" files are removed in 3 days (by default). The default file is used for the “restore” action. This file is rewritten by the subsequent “backup” action on the same BSC. If you need to restore BSC from the previous dump file, copy the required backup file to the default file.

} endfor

TROUBLESHOOTING 1. See the log file /var/local/oam/bscId.ds_restoreBsc.log.

2. If the time between the backup and restoration exceeds the value set in the configuration file /CMN/tools/config/cm_restoreBSC.cfg, (for example 24 hours), the BSC can be restored only with option "-F".


... (omc) % /usr/local/oam/bin/ds_restoreBsc.sh -Orestore -BbscId –F ↵

If a failure occurs, the tool stops. The BDE content cannot be restored while any operations are being performed in BDE tables and the only way out is to perform full BDE restoration by restarting the OMC-R (see sheet “OMC-R DATA ARCHIVING AND RESTORATION”.)

FINAL STATUS The database of the BSC (bscId) is saved or restored.


Nortel confidential


PURGE OAM USER FILES

PRESENTATION The purpose of this sheet is to explain how to purge the files belonging to the “oam” user by means of the dedicated tool.

WARNING: All command files of the oam user will be deleted by the tool.

INITIAL STATUS The OMC-R is operational.

ACTIONS 1. If not done yet, open an omc shell session on the active server. 2. Run the purge oam files tool on the active server:


... (omc) % /usr/local/oam/bin/ds_purgeOamFiles.sh ↵

TROUBLESHOOTING 1. See the log file /var/local/oam/ds_purgeOamFiles.log.

FINAL STATUS Files belonging to the “oam” user are purged.


Nortel confidential


OMC/BSC/BTSSM PRECHECKS ON INTERFERENCE MATRIX

PRESENTATION The purpose of this sheet is to describe how to check that the interference matrix is not running on the required objects.

INPUT PARAMETERS param The parameter that describes the objects to be checked (“network” or “bsc”

or “btsSM”) objId The identifier of the object to process (bscId in case if param =”bsc”,

btsSMId if param=”btsSM”, unused in case if param=”network”)

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation. The user must be logged in the OMC-R browser.

ACTIONS

1. GOTO « OMC-R Browser (...) »

2. If param = “network” DESELECT ANY OBJECT

Else if param = “bsc” SELECT_OBJ « BSC objId object » Else if param = “btsSM” SELECT_OBJ « BTSSM objId object »

3. GOTO « Objects/Several »

4. Choose « Get ».


Nortel confidential


5. Select the object identifier:

5.1. In case if param = “network”: the following pop-up “Error” window appears. Click “Continue”:

5.1.1. In the “Enter object identifier” window click “Apply” (the whole network is chosen by default):


Nortel confidential


5.2. In case if param = “bsc”:

5.2.1. In the “Object list” window select BSC and click “OK”:

5.3. In case if param = “btsSM”

5.3.1. In the “Object list” window select btsSM:


Nortel confidential


6. In the “Action” window:

6.1. In case if param = “network” set the following parameters:

6.1.1. Scope Type: “sublevel”, Scope Level: 1

6.1.2. Filter: objectClass="bsc" & InterferenceMatrixRunningOnBSC=”yes”

6.1.3. Parameters to display: InterferenceMatrixRunningOnBSC

6.2. In case if param = “bsc” set the following parameters:

6.2.1. Scope Type: “base”

6.2.2. Filter: InterferenceMatrixRunningOnBSC=”yes”

6.2.3. Parameters to display: InterferenceMatrixRunningOnBSC


Nortel confidential


6.3. In case if param = “btsSM” set the following parameters:

6.3.1. Scope Type: “sublevel”, Scope Level: 1

6.3.2. Filter: objectClass="bts" & InterferenceMatrixRunningOnBTS=”yes”

6.3.3. Parameters to display: InterferenceMatrixRunningOnBTS


Nortel confidential


7. Click on the “Apply” button in the “Action” window

8. To the question about the response answer “Yes”:

9. Look at the “Response" window. Wait for the result of the command:

9.1. In case if param = “network”

“Display-several: object = (network); scope = sublevel 1; filter = objectClass = "bsc" &

InterferenceMatrixRunningOnBSC=”yes”; InterferenceMatrixRunningOnBSC;”

9.2. In case if param = “bsc”

“Display-several: object = (bsc = <objId>); scope = base; filter =

InterferenceMatrixRunningOnBSC=”yes”; InterferenceMatrixRunningOnBSC;”

9.3. In case if param = “btsSM”

“Display-several: object = (bsc = <bscId> & btsSiteManager = <objId>); scope =

sublevel 1; filter = objectClass = "bts" & InterferenceMatrixRunningOnBTS=”yes”;

InterferenceMatrixRunningOnBTS;”

10. The result of the command must be empty that is there are no objects on which the interference


Nortel confidential


matrix is running.

In case there are one or several objects on the list the result of the check is NOK. See the

TROUBLESHOOTING section for additional information.

TROUBLESHOOTING It is necessary to stop the interference matrix on the dedicated objects in order to reconfigure or upgrade them.

Any reconfiguration operation (upgrade, reparenting, frequency replanning, reconfiguration of location area code etc) is forbidden on the object where the interference matrix is running.

FINAL STATUS The param objId is successfully checked that the interference matrix is not running on the dedicated objects.


Nortel confidential


6. ABBREVIATIONS AND DEFINITIONS

6.1. ABBREVIATIONS

Abis ETSI generic name for BSC-BTS interface Agprs NORTEL generic name for BSC-PCU interface AIX IBM UNIX operating system ALA ALArm regrouping board (in BSC) AMR Adaptive Multi Rate Ater ETSI generic name for BSC-TCU interface ATM Asynchronous Transfer Mode ASCI Advanced Speech Call Items A5000 Sun™ StorEdge™ A5000 BCC Base Color Code BCCH Broadcast Control Channel BCF Base Common Functions BDA BSC application database BDE OMC-R operations database BIST Built-In Self Test BSC Base Station Controller BSCB BTS Signalling Concentration Board BSIC Base Station Identity Code BSS Base-station Sub-System BSSGP Base Station System GPRS Protocol BTS Base Transceiver Station CAS Component Administration System CCS7 Common Channel Signalling number 7 CC1 CAM Controller. This is the ATM switch composed of a CC1-SBC and a

CC1-TM CC1-SBC ATM switch for the ALPHA Platform CC1-TM Adapter for the CC1-SBC CCS7 Common Channel Signalling number 7 CDROM Compact Disk Read Only Memory CEM Common Equipment Module CGI Cell Global Identity CN Control Node CP Control Processor CPUE Central Processor Unit Esclave CPUM Central Processor Unit Maître CRC Cyclic Redundancy Check CSR Customer Service Request CTB Cable Transition Board CTM Cable Transition Module CTU Cable Transition Unit DAT Digital Audio Tape DCU Dual Channel Unit DDTI Dual Digital Trunk Interface


Nortel confidential


DELIVERY set of EFT DLCI Data-Link Connection Identifier DLU DownLoading Unit ECI Equipment Cabinet Interface EDGE Data rates for GSM Evolution EFR Enhanced Full Rate EFT “Ensemble de Fichiers Transférables” (set of downloadable files) ER Emergency Recovery ETF Enhanced TRAU Frame ETSI European Telecommunications Standards Institute E1 European Standard PCM link nickname E4xxx Sun™ Enterprise™ server family (E4002, E4500) FPRX Front Processor for Reception FHS Frequency Hopping System FPC Frequency Plan Change FR Full Rate FRATM Frame Relay Asynchronous Transfer Mode Gb ETSI generic name for SGSN- PCUSN interface GGSN Gateway GPRS Support Node GPRS General Packet Radio System GUI General User Interface HC100 High Capacity kit (IDE MMU and CPU133 OMU) HR Half Rate HSN Hopping Sequence Number IEM Interface Electronic Module IN Interface Node LAC Location Area Code LAPD Link Access Protocol D-Channel Lb ETSI generic name for BSC-SMLC interface LP Logical Processor LSA Low Speed Access LSA RC Low Speed Access Resource Complex L1M Layer 1 Management MCC Mobile Country Code MD Mediation Device MDM Nortel Networks Multiservice Data Manager MDP Nortel Networks MDM Management Data Provider MIM Module Information Memory MMI Man Machine interface MMS Memory Mass Storage MNC Mobile Network Code MOD Managed Object Dictionary (BSC / MD interface) MPU Main Processor Unit (BSC chain) MSS Nortel Networks Multiservice Switch MSW Main SWitching matrix MTM Module Test and Maintenance NCC Network Color Code NMS Network Management System NRP Network Reconfiguration Procedure


Nortel confidential


NSE Network Switch Element NSVC Network Switch Virtual Circuit NTP Nortel Telecom Publications OAM Operation Administration and Maintenance OC-3 Optical Carrier level 3 (SONET) ODIAG Observation DIAGnostic OMC-R Operation and Maintenance Centre - Radio part OML OAM link OMN Operation and Maintenance Network (BSC-MD Link, also known as the

"REM" link) OMU Operation and Maintenance Unit composed of an OMU-SBC and an OMU-

TM OMU-SBC VME SBC used for the OMU OMU-TM ATM Adapter for the OMU PCCCH Packet Common Control Channel PCGTL Pcusn Gprs Transport Layer PCM Pulse Code Modulation PCU Packet Control Unit PCUOAM Packet Control Unit Operation Administration and Maintenance server PCUSN Packet Control Unit Support Node PDCH Packet Data Channel PDP Packet Data Protocol, eg. IP or X25 PDTCH Packet Data Traffic Channel PEC PCM Error Correction PLMN Public Land Mobile Network PROM Programmable Read Only Memory QoS Quality of service Q3 MD manager interface RAC Routing Area Code RAM Random Access Memory RM Resource Module RSL Radio Signalling Link SAI Service Area Interface SBC Single Board Computer : Regular VME processor boards SDO Serveur de DOnnées SDS Software Distribution Site SFH Synthesised Frequency Hopping SGSN Serving GPRS Support Node SICD Serial Interface Controller for lapD protocol SICX Serial Interface Controller for X25 protocol SIM Shelf Interface Module SLS Serial Link Switch (BSC board supporting the serial link with OMC-R SLS2 Serial Link Switch, second generation SMS-CB Short Message Service – Cell Broadcast SMLC Serving Mobile Location Center SS1000 Sun™ SPARCserver™ 1000 SSA Sun™ SPARCstorage™ Array SS7 Common Channel Signalling number 7 SUP SUPervision board


Nortel confidential


SUP2 SUPervision board, second generation SWACT SWap of ACTivity SWC SWitching matrix Controller TAS Technical Assistance Service TCB TranscoderBoard Card TCB2 2nd generation TranscoderBoard Card TCP Transmission Control Protocol TCU TransCoder Unit TDMA Time Division Multiple Access TEI Terminal Equipment Identifier TIC Terminal for Installation and Commissioning TML Local maintenance terminal (Terminal de Maintenance Locale) TMU Traffic Management Unit composed of a TMU-SBC and a TMU-TM TMU-SBC VME SBC used for the TMU TMU-TM ATM Adapter for the TMU TO Temporary Observation TRAU Transcoder/rate Adaptator Unit TRM Transcoding Resource Module TRX Transmitter/Receiver TS Time Slot TTY Text Telephone T1 American Standard PCM link nickname VRTX Operating system used in CEM modules VxWorks Operating system used in TMU modules e3 BSC evolution 3rd generation BSC e3 TCU evolution 3rd generation TCU e3 TML evolution 3rd generation TML 2G BSC other BSC than e3 BSC 2G TCU other TCU than e3 TCU

6.2. DEFINITIONS

Active (respectively passive) server The term designating the actual active (respectively passive) server on an operational OMC-R, in case of dual servers configuration. For a single server configuration, only the active server exists.

BCCH conflict The set of attributes bCCHFrequency and bsIdentityCode must be unique in the set constituted by the cell and its neighbouring cells (adjacentCellHandOverNortel object class only).

BSIC The code used to identify a base station, which allows mobile stations to distinguish the cells sharing the same BCCH frequency. A BSIC is defined by an (NCC, BCC) combination.

CAS The command and control system that takes network management requests, passes them to appropriate components for action, and returns results to the


Nortel confidential


requester. The CAS is responsible for all provisioning and control commands and management of provisioning data on the MSS.

CGI Global identifier of a mobile network cell. The CGI contains the Location Area Code (LAC), Mobile Country Code (MCC), Mobile Network Code (MNC) and the cell identifier in the location area.

Concentric A cell is defined as concentric if two pools of resources (TDMAs) are defined using Rxlev and optionally Timing Advance as allocation criteria. One or two types of TRXs can be used.

Delivery Set of EFT

Dualzone A cell is defined as dualzone if the TRXs are configured to transmit at different power resulting in two different coverage areas.

Dualcoupling A cell is defined as dualcoupling if the TRXs are not combined with the same type of combiner and thus do not have the same coupling loss resulting in two different coverage areas. Linked to stepped coupling feature.

Dualband A cell is defined as dualBand if GSM900 TRXs and DSC1800 TRXs coexist and share the same BCCH. The propagation loss being different, it results in two different coverage areas.

DS0 One TS at 64kbps of one PCM without joker TS, one TDMA uses 2 DS0, which are configured on one PCM.

Erlang International (dimensionless) unit of traffic intensity defined as the ratio of time a facility is occupied to the time it is available for occupancy. One erlang is equal to 36 ccs. In the US, it is also known as a traffic unit.

E1 A primary PCM group, which consists in an assembly, by digital using multiplexing, of PCM signals occupying 32 channels time-slots in order to generate a signal with a digit rate of 2048 kbit/s, in both transmission directions.

GPRS Wireless packet data service that is an extension to the GSM network. It allows providing multiple radio channels to one user (high data user rate) as to share one radio channel between multiple users (radio resource optimization).

Joker DS0 On Abis, 64 kbps timeslot used as joker for EDGE TDMA. The total number of DS0 used for EDGE TDMA consists in 2 DS0 called main DS0 plus joker(s) DS0.

MDM Nortel Networks Multiservice Data Manager. The product developed by MSS Product Line. This product can configure an MSS, collect alarms and real time counters from an MSS node.

MDP Nortel Networks MDM Management Data Provider. The product developed by MSS Product Line. This product can collect spooled counters from an MSS node, convert them into ASCII files and send them to external devices.

Old-version Represents the old edition N-2, N-1 or N to be upgraded.

OMC-R OMC-R software installed on an OMC-R server or an OMC-R workstation.


Nortel confidential


OMC-R machine A machine running OMC-R software (an OMC-R server or an OMC-R workstation).

Preferential active (respectively passive) server The term designating a server administratively declared as active (respectively passive). A preferential passive server can become an operational active server after a switchover on an operational OMC-R. For a single server configuration, only a preferential active server exists.

PCUOAM (server/workstation) added to the OMC-R LAN to host MDP and NMS software and also OMC-R process which handles PCUSN alarms and counters collection. One PCUOAM can only be linked to only one OMC-R.

PCUSN A separate node in the BSS providing specific packet processing of the GPRS. There is only 1 PCU per BSC, but a PCUSN can be shared with several BSCs.

SDS A Software Distribution Site is an FTP server that handles GPRS MSS software. It is used during the upgrade procedure.

SMS-CB Short messages broadcast at the cell level.

TDMA The abbreviation used to designate a transmission frame on the radio interface, divided into eight timeslots (TS) or channels.

TRAU frame Frames (speech/data) with a fixed length of 320 bits (20 msec).

T1 (or DS1) is a primary PCM group, which consists in an assembly, by digital multiplexing, of PCM signals using 24 channels time-slots in order to generate a signal with a digit rate of 1544 kbit/s, in both transmission directions.

2G equipment:

2G BSC Other BSC than e3 BSC

2G TCU Other TCU than e3 TCU

BDA BSC application database

Active and Passive chain of a 2G BSC The BSC MPU (Main Processing Unit) processing chain is duplicated for reliability and operates in matched pairs (MPUA and MPUB). In duplex mode, the chain in service is called the active chain and provides the functions of the rack. The other chain, called the passive chain, takes over if the first one fails.

Duplex mode The state of a 2G BSC when both chains are on-line

Simplex mode The state of a 2G BSC when only one chain is on-line

Control cabinet A 2G BSC is composed of 2 cabinets. The control cabinet contains the processing chains MPUA and MPUB.


Nortel confidential


Equipment cabinet A 2G BSC is composed of 2 cabinets. The equipment cabinet contains the boards shared by both chains and their switching units.

Data mirroring Process whereby the data are updated on the passive chain while changing on the active chain, when the 2G BSC is in duplex mode operational state.

Switch-over Process whereby the passive chain becomes active, because the previously active chain is not able to maintain the 2G BSC in its operational state. It happens when the active chain is simply powered down, or when it is having a hardware or software problem.

Type 3 upgrade This type of upgrade is performed when there is a change of BDA format between the previous software version and the new software version. The service is lost.

Type 4 upgrade This type of upgrade is performed when there is a change of BSC application software only. BSC switchover is performed to activate the new software version. The service is not lost but calls established for more than 5 minutes are lost.

Type 5 upgrade This type of upgrade is performed when there is a change of BDA format between the previous software version and the new software version. But contrary to type 3 there is only one small service impact thanks to the mechanism called BDA n+1.

E3 equipment

e3 BSC Evolution 3rd generation BSC

e3 TCU Evolution 3rd generation TCU

MIB Managed Information Base. But even if the e3 BSC database is named MIB, the term of BDA is commonly used to name 2G and e3 BSC database.

Swact SWitch of ACTivity. It applies to CEM of Interface Node, CEM of TCU and to OMU of Control Node.

Type 3 upgrade This type of upgrade is performed when there is a compatibility break with a change of MIB format between the previous software version and the new software version. There is a “build off line”. The service is lost (important downtime).

Type 4 upgrade This type of upgrade is performed when there is a change of BSC application software without change of MIB and without compatibility break. There is no build. The service is not lost (no downtime).

Type 6 upgrade This type of upgrade is performed when there is a compatibility break


Nortel confidential


with change of MIB format between the previous software version and the new software version. There is a “build on line”. The service is lost following a BSC restart (downtime during few minutes).

Type 7 upgrade This type of upgrade is performed when there is a compatibility break without change of MIB format between the previous software version and the new software version. There is no build. The service is lost following a BSC restart (downtime during few minutes).

7. TYPOGRAPHIC CONVENTIONS

7.1. GENERAL CONVENTIONS

Words in italics (italic) are used to indicate where you see the actually displayed text or where you type the value of the parameter being entered.

Inscriptions as the one below indicate on what computer the recommended actions should be performed:

ON THE LOCAL OMC-R WORKSTATION:

Conditional commands are presented in the following format:

For all unlocked bscMdInterface objects:

{

.....

}

7.2. INTERACTIVE TERMINAL SESSIONS

There are two ways to start an interactive session on a terminal:

- by selecting the "Access to Unix" option of the background menu on the server or station;

- by means of the telnet or rlogin command providing remote access to the server or station from a shell window on any other host.

Different typefaces and symbols appearing in the description of an interactive session on a terminal (line terminal or Command Tool window) are used with the following purposes:

Convention used Meaning

Courier New The Courier New font represents the characters of a terminal session.

Bold Lines, commands or parameters entered from the keyboard are in bold type.


Nortel confidential



Italic The italic style denotes variable output. Substitute the actually displayed values in place of words in italics.

italic-bold Italic and bold types denote the input parameters that you enter as the required input value.

↵ Press the ENTER key.

[STOP],[a] The STOP and ‘a’ key pressed simultaneously.

.......... Dots represent a number of skipped lines.

✂ The scissors symbol indicates that the command being typed continues on the next line.

% or (user) % C shell prompt.

$ or (user) $ Bourne and Korn shell prompts.

# or (root) # Root super-user prompt in any shell.

Example of a terminal session:

Under omc login:

/ (omc) % cd my_directory ↵ my_directory (omc) % ls ↵ a.out i_am_a_short_file_with_a_really_i_mean_really_no_but_unbelievably_✂ long_name ........ toto.o my_directory (omc) % vi my_file ↵ my_directory (omc) %

The conventions of a terminal session are also used to display the content of a UNIX file.

7.3. INTERACTIVE GRAPHIC SESSIONS

The conventions used to describe actions performed during an interactive graphic session are as follows:



Nortel confidential


Convention used Meaning GOTO « Title » Go to the window named "Title".

SELECT « Save - OK » Click the button or option with the name "Save", then with the name "OK".

SELECT_OBJ « omc » Select the object « omc ».

SET State = locked T2 = 30s

Enter the parameter values shown in bold font by typing them on the keyboard.

CLOSE « Title » Close the window with the name "Title".


Nortel confidential


7.4. SEQUENCE TABLE CONVENTIONS

Every major phase of the procedure is described as a sequence of operations (procedure steps) presented in a sequence table. Each step is covered in details in the operation sheet referenced to by its page number.

Since operation sheets are not arranged in the execution order and the operations detailed therein can be executed several times, they do not provide a reliable reference. Refer to sequence tables for guidance during the procedure.

As the need to carry out a step operation may arise at different stages of the procedure and in various work situations (procedure contexts) the operation input parameters may vary and therefore are context-specific.

Sequence tables detail what operation is performed during each procedure step, present the order of individual steps, give a time estimate for every step operartion and mark the step result.

Time estimates for procedure steps are given for the maximum network configuration, and may vary with the hardware make-up.

A typical sequence table has the following format:

Step | Operation description (Total 35 mn + ? mn) mn Sheet page

OK / NOK

NOK step

Input Parameters

STATUS COMMENT

S1 Description of operation 1 30 12 OK F1

Parameter1 = value Parameter2 : explanations

S2 Description of operation 2 ? 14 OK F1

S3 Description of operation 3 5 17 OK F6

Parameter1 = value

Each time an operation is performed, the operator should note the result in the « OK / NOK » column.

If the result is « OK », the next operation is described in the following line of the table. If the result is « NOK », the procedure can not be continued. The next operation can be indicated in the last column of the current line and is either a fallback or a troubleshooting step. In case of fallback (indicated with "F"), the fallback procedure should be started at the specified step.

Result of the operation, filled in by the operator

Fallback or trouble shooting step to execute (if any), if

the result of the operation is NOK

Sheet page number

Operation time estimate for maximum configuration

Comment indicating the status at this stage of the major step

Name and value of input para-meters of the sheet (optional or « none » for no argument)


Nortel confidential


END OF DOCUMENT

Documents

BSS Frequency Plan Change Procedure