NN-20500-090 (9300 W-CDMA Product Family - Neighboring Plan Update NRP) 11

Title page

W-CDMA

Alcatel-Lucent 9300 W-CDMA Product Family | V7.1

Neighboring Plan Update (NRP)

NN-20500-090

ISSUE 11.02

NOVEMBER 2009

Alcatel-Lucent Internal

Proprietary Use pursuant to Company instruction


PRELIMINARY

PRELIMINARY

Legal notice

Legal notice

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective

owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright 2009 Alcatel-Lucent. All rights reserved.

Contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be made available to, or copied or used by anyone outside

Alcatel-Lucent without its written authorization.

ot to be used or disclosed except in accordance with applicable agreements.

Trademarks

Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.




PRELIMINARY

PRELIMINARY

Contents

About this document

Purpose .............................................................................................................................................................................................. vv

Reason for revision ........................................................................................................................................................................ vv

ew in this release ......................................................................................................................................................................... vv

Intended audience .......................................................................................................................................................................... vv

Supported systems ........................................................................................................................................................................ vivi

How to use this document ......................................................................................................................................................... vivi

Prerequisites ................................................................................................................................................................................... vivi

Vocabulary conventions ............................................................................................................................................................. vivi

Conventions used .......................................................................................................................................................................... vivi

Related information ..................................................................................................................................................................... vivi

Document support ...................................................................................................................................................................... viivii

Technical support ....................................................................................................................................................................... viivii

How to order ................................................................................................................................................................................. viivii

How to comment ......................................................................................................................................................................... viivii

1 Roadmap to Configuration Management documentation

Overview ....................................................................................................................................................................................... 1-11-1

Roadmap to Configuration Management documentation ........................................................................................... 1-21-2

2 Neighboring Plan Update Overview and procedure preparation

Overview ....................................................................................................................................................................................... 2-12-1

eighboring plan update ......................................................................................................................................................... 2-22-2

Procedure preparation .............................................................................................................................................................. 2-32-3

eighboring Plan Update under WPSAccess ................................................................................................................. 2-72-7

...................................................................................................................................................................................................................................

NN-20500-090

Issue 11.02 November 2009



iii

PRELIMINARY

PRELIMINARY

3 Neighboring Plan Update Procedures

Overview ....................................................................................................................................................................................... 3-13-1

Performing Reverse Engineering - Sheet 1 ...................................................................................................................... 3-23-2

Importing a new eighboring Plan under WPSAccess - Sheet 2 ........................................................................... 3-43-4

Consistency checks under WPSAccess - Sheet 3 .......................................................................................................... 3-93-9

Modifications of the eighboring Plan under WPSAccess - Sheet 4 ................................................................. 3-113-11

Exporting Workorders - Sheet 5 ......................................................................................................................................... 3-133-13

4 Reconfiguration Activation

Overview ....................................................................................................................................................................................... 4-14-1

Reconfiguration Activation Pre-Checks ............................................................................................................................ 4-24-2

Reconfiguration Activation in WMS .................................................................................................................................. 4-34-3

Reconfiguration Activation Post-Checks .......................................................................................................................... 4-64-6

5 Reverse procedures

Overview ....................................................................................................................................................................................... 5-15-1

Fallback Workorder Activation for RCs (C-ode Part) in case of Fallback failure ...................................... 5-25-2

Reverse Workorder Activation .............................................................................................................................................. 5-55-5

Glossary

Contents

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

iv Alcatel-Lucent Internal


NN-20500-090


PRELIMINARY

PRELIMINARY

About this documentAbout this document

Purpose

The purpose of this document is to describe the etwork Reconfiguration Procedure

(RP) applicable to the update of the neighboring plan in an UMTS network, without

interruption of service on the existing RCs. The situation of new neighboring plan

introduction (i.e. from scratch) is also covered by the current procedure of neighboring

plan update.

Reason for revision

Reasons for reissue are:

Issue number Issue date Reason for reissue

11.02 ovember 2009 Preliminary issue

11.01 October 2009 Initial draft issue for V7.1

New in this release

New features:

one

Other changes:

one

Intended audience

The audience for this document is:

Configuration management personnel

etwork administration personnel

...................................................................................................................................................................................................................................

NN-20500-090




v

PRELIMINARY

PRELIMINARY

Supported systems

This document applies to Alcatel-Lucent W-CDMAV7.1 system release.

This document covers the following systems:

ode B

RC

WMS

WPS

How to use this document

Start with the first chapter and work through the manual to the end. Once you have done

this, you will have carried out the re-configuration procedure in the proper sequence.

Prerequisites

A good knowledge of UTRA configuration principles as well as Microsoft Windows T

4.0, Windows 2000 or Windows XP is required before reading this RP.

It is also recommended that readers become familiar with the following documents:

Alcatel-Lucent 9300 W-CDMA Product Family - Terminology, (-20500-002)

Alcatel-Lucent 9353 Management System - System Overview, (-20500-031)

Alcatel-Lucent 9353 Management System - User Guide, (-20500-032)

Alcatel-Lucent 9300 W-CDMA Product Family - Parameters Reference Guide,

(-20500-027)

Alcatel-Lucent 9352 Provisioning System - User Guide, (-20500-036)

Vocabulary conventions

one.

Conventions used

one.

Related information

For information on subjects related to the content of this document, refer to the following

documents:

[R1] Alcatel-Lucent 9300 W-CDMA Product Family -Parameters Reference Guide,

-20500-027

[R2] CM XML format Description, UMT/OMC/DD/007615

[R3] Alcatel-Lucent 9352 Provisioning System - User Guide, -20500-036

[R4] External WPS ACCESS interface, UMT/OMC/DD/006639

About this document

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

vi Alcatel-Lucent Internal


NN-20500-090


PRELIMINARY

PRELIMINARY

[R5] Alcatel-Lucent 9353 Management System - User Guide, -20500-032

[R6] Alcatel-Lucent 9300 W-CDMA Product Family - Terminology, -20500-002

Document support

For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at

one of the following telephone numbers:

1-888-582-3688 (for the United States)

1-317-377-8618 (for all other countries)

Technical support

For technical support on the product, contact your local Alcatel-Lucent customer support

team. See the Alcatel-Lucent Support web site (http://www.alcatel-lucent.com/support/)

for contact information.

How to order

To order Alcatel-Lucent documents, contact your local sales representative or use Online

Customer Support (OLCS) (https://support.lucent.com).

How to comment

To comment on this document, go to the Online Comment Form (http://infodoc.

alcatel-lucent.com/comments/enus/) or e-mail your comments to the Comments Hotline

([email protected]) .

About this document

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




vii

PRELIMINARY

PRELIMINARY

PRELIMINARY

PRELIMINARY

1 1Roadmap to Configuration

Management

documentation

Overview

Purpose

This chapter provides the roadmap for Configuration Management documentation.

Contents

Roadmap to Configuration Management documentation 1-2

...................................................................................................................................................................................................................................

NN-20500-090




1-1

PRELIMINARY

PRELIMINARY

Roadmap to Configuration Management documentation

The following figure shows where the current document stands within the W-CDMA

customer documentation.

For a global view of the W-CDMA customer documentation, see the Roadmap chapter in:

Alcatel-Lucent 9300 W-CDMA Product Family - Document Collection Overview,

-20500-050

Alcatel-Lucent 9300 W-CDMA Product Family - Access etwork Management

Overview, -20500-031

Roadmap to Configuration Management documentation Roadmap to Configuration Management documentation

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

1-2 Alcatel-Lucent Internal


NN-20500-090


PRELIMINARY

PRELIMINARY

2 2Neighboring Plan Update

Overview and procedure

preparation

Overview

Purpose

This chapter describes the eighboring Plan Update and procedure preparations

Contents

eighboring plan update 2-2

Procedure preparation 2-3

eighboring Plan Update under WPSAccess 2-7

...................................................................................................................................................................................................................................

NN-20500-090




2-1

PRELIMINARY

PRELIMINARY

Neighboring plan update

General description

The neighboring plan update procedure aims at modifying the neighboring plan either due

to a new site addition or an addition, deletion, update of neighboring links in the UMTS

network.

When the modifications of the configuration data concern the neighboring links uniquely

(neighboring links are created, updated or deleted), the objects involved in this procedure

are as follows:

The UMTS neighboring links created, updated or deleted

The GSM neighboring links created, updated or deleted.

The GSM cell(s) impacted by the GSM neighboring links modification.

Note:

Equivalent activity needs to be performed on 2G system for reciprocal neighbours.

Note:

As WPSAccess is mono ROC oriented, the procedure can be applied only on one ROC.

So if neighboring links towards cells belonging to others ROCs are updated, then the

same activity needs to be performed on each ROC

Compounding Neighouring List

Some new parameters or new parameter value are added to handle:

The priority defined per neighboring cell

The occurrence of a cell within all neighbourhoods

The parameters are:

maxCompoundingListSizeIntraFreq

typeOfCompoundingeighbourListIntraFreq

numOfPrimaryCelleighbourIntraFreq

neighbourCellPrio

Neighboring Plan Update Overview and procedure

preparation

Neighboring plan update

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

Procedure preparation

Procedure description

The following diagram displays the different steps to be conducted to perform the new

neighboring plan introduction.

Prerequisites

The RP: "eighboring Plan Update", described in this document applies only if all of

the following conditions are verified:

The etwork and the OMC are up and running without any problem. (Alarm, OMC

MIB State, Synchronization State, etc.)

All ode B and FDDCell objects referred by the new neighboring plan are already

declared in the host RCs.

Neighbouring Plan Updateunder WPS Access

Reconfiguration ActivationPre-Checks

Reconfiguration Activationin WPS

Reconfiguration ActivationPost-Checks

XML file provided by the Cell Planningfor Neighbouring Plan Update is available

Workorder (CM XML) file forNeighbouring Plan Update activation is available

The Neighbouring Plan is up to date


preparation


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




2-3

PRELIMINARY

PRELIMINARY

The RRM subtree required for the new neighboring plan is initialized on the host

RCs.

The configuration files coming from the Cell Planning Tool can be compatible with

WPSACCESS CPXML format, as specified in document [R4] or with the CM

XML format, as specified in document [R2].

ote: It is recommended to use the CPXML format (specified in document [R4]).

This Snapshot format provides extra identifiers for the objects and does not require

specific UMTS topology information (RC, ode B) that are required in the CM

XML format. evertheless some pre-requisites on the etwork View are required in

order to be able to import a CP XML file in WPSACCESS with the Cell Planning

Import Wizard:

There must be a unique definition of GSMCell within the etwork

The Cell Planning Id for GSMCell, BTSCell, AntennaAccess and AntennaSystem

must be unique over the entire network

Cell Planning Id must be consistent between a GSMCell and its associated

GSMeighbouringCell

RCid must be unique over the entire network

The LocalCellId of the FDDCell and BTSCell must be unique over the entire

network

The FDDCell UserLabel must be unique over the entire network

The UMTS eighboring FDDCell identification and/or related FDDCell

parameter definition must be consistent with related FDDCell.

Limitations

The procedure focuses on UTRA Es: RC, and ode B.

The Cell Planning Tool and the OMC must contain the same network coverage in

terms of managed ode Bs and associated FDD Cells.

If the new neighboring plan comes from a CM XML files, o partial neighboring

plan can be obtained.

The creation and deletion of ode Bs or UMTS cells are out of scope in this

document.

The modification of the scrambling code, or LAC plan are out of the scope in this

document.

o modifications should be done on the Target RCs and their associated MO

(Managed Object) through WMS GUI, WICL from the beginning of the RP (export

XML from Main server, sheet 1) until the end of the procedure.

As WPSAccess is mono ROC oriented, the procedure can be applied only on one

ROC. So if neighboring links towards cells belonging to others ROCs are updated,

then the same activity needs to be performed on the each ROC.


preparation


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

Mean Time

This chapter summarizes the duration given for each step of the Procedure. evertheless,

as the timing depends on too many heterogeneous parameters (Hardware Configuration,

Software Configuration, Size of the etwork, Transmission etwork performance, etc.)

and then might significantly vary from a configuration to another one, the times given in

this chapter are only for information and planning purpose.

ote: That Durations are given for the modification of the neighboring plan for a

network with 7 RCs, 860 BTSEquipment and 2540 Cells.

Neighboring Plan Update preparation under WPS Access

Step Sheet Timing

1 (Optional) Sheet 1 - Peforming Reverse

Engineering

30 minutes

2 Sheet 2 - Importing a new neighboring

plan Under WPSAccess

Few minutes

3 Sheet 3 - Consistency checks under

WPSAccess

Few minutes

4 (Optional) Sheet 4 - Modifications of the

eighboring Plan under WPSAccess

Few minutes

Sheet 3 - Consistency checks under

WPSAccess

Few minutes

5 Sheet 5 - Exporting Workorders Few minutes

Reconfiguration Activation Pre-Checks

Step Chapter 5.1 Timing

6 (optional) Reconfiguration Activation Pre-Checks < 1 hour

CM XML Import in WMS


7 Reconfiguration Activation in WMS 35 minutes

Reconfiguration Activation Post-Checks


8 (Optional) Reconfiguration Activation

Post-Checks

< 1 hour


preparation


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




2-5

PRELIMINARY

PRELIMINARY

Impacts

This topic summarizes the impacts on the service given for each step of the Procedure.

Main Steps Impact on Service

eighboring plan update preparation under WPSAccess one

Reconfiguration Activation Pre-Checks one

Reconfiguration Activation in WMS one

Reconfiguration Activation Post-Checks one

PM and FM impacts

The Es are managed by the PM system.

The procedure ensures the correct declaration of the Es with respect to FM

management.


preparation


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

Neighboring Plan Update under WPS Access

Purpose

This activity aims at defining the provisioning data required for the neighboring plan

update in the live network. This data consists of a XML file that contains:

The modification to be applied on:

The UMTS neighboring links

The GSM cell

The Outgoing GSM eighboring cells associated with the updates neighboring plan

Optional: the following Objects may be impacted in the XML file provided by the Cell

Planning (for more information please see document referenced [R4]):

BTSCell

Site

AntennaAccess

AntennaSystem

Description

The following figure provides an overview of the steps to follow in order to provide the

OMC team with the relevant data set required to implement the updated neighboring plan:


preparation


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




2-7

PRELIMINARY

PRELIMINARY

The procedure that follows is derived from the preceding figure, and gathers all the steps

and notes that should be followed to implement an updated neighboring plan.

The steps sequence required to complete the neighboring plan update preparation is:

Step Sheet

1 (Optional) Sheet 1 - Performing Reverse Engineering

2 Sheet 2 - Importing a new eighboring Plan Update under WPSAccess

3 Sheet 3 - Consistency checks under WPSAccess

4 (Optional) Sheet 4 - Modifications of the eighboring Plan under WPSAccess

Sheet 3 - Consistency checks under WPSAccess

5 Sheet 5 - Exporting Workorders

As the result of these steps, the Workorder (CM XML) file which contains the updated

neighboring plan information is available.


preparation


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

CP XML interface overview

WPSACCESS provides a specific interface for Cell Planning Tools based on XML

format, named CP XML, and described in the document referenced [R4].

This Specific format allows the user to use different identifiers for the Cell Planning

Objects that the ones defined in CM XML format described in document [R2] and to be

independent from the Topology (RC, ode B).

In WPSACCESS, a CP XML import Wizard allows the user to import the CP XML files.

This Wizard provides two options of import depending on the selection of the "Delete

un-impacted neighbouring links" field:

If "Delete un-impacted neighbouring links" is selected (re-build Mode): For all the

FDD Cells defined in the CP XML file, all the related neighboring Cells (UMTS and

GSM) defined in WPSACCESS but not defined in the CP XML file will be deleted

by the Cell Planning Import Wizard.

If "Delete un-impacted neighbouring links" is not selected (update Mode): all the

neighboring Cells (UMTS and GSM) defined in the CP XML file will be updated (if

already defined in WPSACCESS) or created (if not defined in WPSACCESS) by the

Cell Planning Import Wizard.


preparation


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




2-9

PRELIMINARY

PRELIMINARY

PRELIMINARY

PRELIMINARY

3 3Neighboring Plan Update

Procedures

Overview

Purpose

This chapter details the following procedures:

Performing Reverse Engineering - Sheet 1

Importing a new eighboring Plan Update under WPSAccess - Sheet 2

Consistency checks under WPSAccess - Sheet 3

Modifications of the eighboring Plan under WPSAccess - Sheet 4

Exporting Workorders - Sheet 5

Contents

Performing Reverse Engineering - Sheet 1 3-2

Importing a new eighboring Plan under WPSAccess - Sheet 2 3-4

Consistency checks under WPSAccess - Sheet 3 3-9

Modifications of the eighboring Plan under WPSAccess - Sheet 4 3-11

Exporting Workorders - Sheet 5 3-13

...................................................................................................................................................................................................................................

NN-20500-090




3-1

PRELIMINARY

PRELIMINARY

Performing Reverse Engineering - Sheet 1

Purpose

This step details how to proceed with WPSACCESS and the main server to import a

view of the current network configuration into WPSACCESS if the WPSACCESS view

is not up-to-date.

This is an optional, but recommended step. You can bypass it if you are sure that your

WPSACCESS view is synchronized with the network. In this case, please go to the next

step.

Once the CM XML export is performed, no "on line" modifications can take place on the

target E(s) until the end of the overall procedure in order to guarantee that the initial

view, on which the procedure is based, is synchronous with the Main server MIB.

Input Parameters

one.

Initial status

WPSACCESS is installed and ready to be used. The template files are uploaded.

Duration

Step duration depends on the number of E available on the network.

See Mean Time chapter for dimensioning info.

Action 1: less than 20 minutes

Action 2: less than 10 minutes

Impact on service

one.

Procedure

...................................................................................................................................................................................................

1 Export from the Main server (Global UTRA export) the XML file describing the

network (If required transfer the file to a WPSACCESS PC directory).

...................................................................................................................................................................................................

2 Under WPSACCESS:

Open a new Workspace. Refer to procedure "Open a workspace" in document [R3] for

details of workspace creation

From the file menu launch the Import and Export wizard:

Neighboring Plan Update Procedures Performing Reverse Engineering - Sheet 1

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

Select "Import Snapshot" (form the Local file system or the Live server repository)

and click Next

Select "Replace initial snapshot and discard existing workorders" and click Next

Click Browse

Select the XML file exported step 1 and Click Open

Click Next

If a part of the snapshot need to be excluded Click Edit Filter?, Choose Objects to

import and Click Next otherwise Click directly Next

Select "o, proceed without saving" and click Start

...................................................................................................................................................................................................

3 After import completion, check the report and close it.

Troubleshooting

Stop the global procedure and redo this step.

Final status

At this step, you have a Workspace with an Initial Snapshot describing your current

network.

Neighboring Plan Update Procedures Performing Reverse Engineering - Sheet 1

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




3-3

PRELIMINARY

PRELIMINARY

E N D O F S T E P S...................................................................................................................................................................................................

Importing a new Neighboring Plan under WPS Access - Sheet 2

Purpose

This step details how to proceed with WPSACCESS in order to import the updated

neighboring plan.

Depending on the received format of the ew eighboring Plan, this step can be divided

in four actions:

The ew eighboring Plan is provided through a CPXML Snapshot file

The ew eighboring Plan is provided through a file in CM XML format

The ew eighboring Plan is provided through a Workorder, under WPSACCESS,

in your Workspace

The ew eighboring Plan is provided through a Snapshot, under WPSACCESS,

in your Workspace

Input parameters

All Design parameters regarding the new neighboring plan need to be provided to the

Application Engineer by the etwork Designers, i.e.

Cell planning information

eighboring information

All these information can be provided through CP XML snapshot file as described in the

Document [R4] or through a CM XML snapshot or workorder file following the CM

XML format described in [R2].

As a consequence the following Object information should be provided in the XML file:

UMTSFDDeighbouringCell

GSMCell if impacted

GSMeighbouringCell if impacted

BTSCell (Optional)

Site (Optional)

AntennaAccess (Optional)

AntennaSystem (optional)

If the ew eighboring Plan is provided through a CPXML file, perform Step 1 only.

ote: If the option "Delete un-impacted neighbouring links" is chosen for CP XML

file import, for impacted FDD Cells the full list of neighbouring cells (GSM and

UMTS) must be provided.

If the ew eighboring Plan is provided through a CM XML file, perform Step 2 only.

Neighboring Plan Update Procedures Importing a new Neighboring Plan under WPS Access -

Sheet 2

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

Initial status

Under WPSACCESS, a Workspace describing the current configuration of your network

is available. Templates files, RRM tree are uploaded.

Duration


See Mean Time chapter for dimensioning info.

Few minutes

Impact on service

one.

Procedure

...................................................................................................................................................................................................

1 The ew eighboring Plan is provided through a CPXML Snapshot file

...................................................................................................................................................................................................

2 Under WPSACCESS, create a new Workorder and renames it (for example:

"eighboring plan Import") as described in document referenced [R3].

...................................................................................................................................................................................................

3 Under WPSACCESS, in your Workspace, from the etwork tree:

1. Select the etwork

2. From the Wizards & Operation area, click Cell Planning Import Wizard

3. In the "Cell Planning Import Wizard", launch the "Import Cell Planning file"

Operation

4. In the "Import Cell Planning file" Operation, click Browse

5. Select the CP XML Snapshot file and click Open

6. Depending on the Input Parameters (See above):

If in the CP XML Snapshot file the UMTS FDD neighbouring Cells and GSM

eighbouring Cells of the impacted FDD Cells are not defined, DO OT select

the option Delete un-impacted neighbouring links

If in the CP XML Snapshot file All the UMTS FDD neighbouring Cells and GSM

eighbouring Cells of the impacted FDD Cells are defined, SELECT the option

Delete un-impacted neighbouring links

...................................................................................................................................................................................................

4 After import completion, check the report and close it


Sheet 2

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




3-5

PRELIMINARY

PRELIMINARY

E N D O F S T E P S...................................................................................................................................................................................................

Procedure

...................................................................................................................................................................................................

1 The ew eighboring Plan is provided through a file in CM XML format

...................................................................................................................................................................................................

2 Under WPSACCESS, create a new Workorder and renames it (for example: "Initial

eighboring plan deletion") as described in document referenced [R3].

...................................................................................................................................................................................................

3 Under WPSACCESS, in your Workspace, from the etwork tree:

1. Select All the RCs

2. Right Click, Select "Add to Dataset", Click New Dataset....., enter a dataset name

("All_RCs" for example) and Click OK

3. From the Dataset area, Select the previously created Dataset containing all the RCs

4. In the Dataset Conversion area Select:

Input type: RC (model RC)

avigators: [Generic] Children

Output type: RC/odeB/FDDcell/ UMTSFddeighbouringCell (model RC)

Output Dataset: enter a dataset name ("EI" for example)

Click Apply

Close the report window

5. Select the previously created Dataset containing all the RCs




Output type: RC/GSMeighbour/GsmCell (model RC)

Output Dataset: Select the Dataset previously created (named "EI")

Click Apply


7. Select the previously created Dataset containing all the RCs




Output type: RC/odeB/FDDcell/GsmeighbouringCell (model RC)

Output Dataset: Select the Dataset previously created (named "EI")

Click Apply



Sheet 2

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

9. Select the result Dataset containing all the eighboring Cells and GSM Cells

10. Right Click Remove all objects from Networks and Click Yes

Procedure

...................................................................................................................................................................................................

1 The ew eighboring Plan is provided through a Workorder, under WPSACCESS, in

your Workspace

...................................................................................................................................................................................................

2 From the file menu launch the Import and Export wizard:

Select "Import Workorders" and click Next

Click Browse

Select the XML file and click Open

Click Next


...................................................................................................................................................................................................


Procedure

...................................................................................................................................................................................................

1 The ew eighboring Plan is provided through a Snapshot, under WPSACCESS, in

your Workspace

...................................................................................................................................................................................................

2 From the file menu launch the Import and Export wizard:

Select "Import Snapshots" and click Next

Select "Merge with Planned etwork" and Click Next

Click Browse

Select the XML file and click Open

Click Next

If a part of the snapshot need to be excluded Click Edit Filter?, Choose Objects to

import and Click Next otherwise Click directly Next



Sheet 2

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




3-7

PRELIMINARY

PRELIMINARY

E N D O F S T E P S...................................................................................................................................................................................................

E N D O F S T E P S...................................................................................................................................................................................................

...................................................................................................................................................................................................


Troubleshooting

In case of errors, contact your local Engineering representative and correct errors

manually or require a new input.

Final status

At this step, the new UMTS and GSM neighboring plan is created under the FDD Cells

impacted and all GSM Cells are declared under the host RC(s).


Sheet 2

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

E N D O F S T E P S....................................................................................................................................................................................................................................

Consistency checks under WPS Access - Sheet 3

Purpose

The procedure details how to checks that the neighboring plan is consistent with all

UMTS and GSM cells declared.

Input parameters

one.

Initial status

A new UMTS and/or GSM, neighboring plan has been imported

Having ode Bs parented to RC with UMTS and/or GSM neighboring plan updated as

GSMCell parented to RC in a Workspace under WPSACCESS

Duration


See Mean Time chapter for dimensioning info

Few minutes

Impact on service

one.

Procedure

...................................................................................................................................................................................................

1 Under WPSACCESS, create a new Workorder and rename it (for example: "consistency

checks") as described in document [R3]

...................................................................................................................................................................................................

2 From the etwork Object, launch the checker as described in document [R3].

...................................................................................................................................................................................................

3 In the Checks Window, select a check, right click Disable All

...................................................................................................................................................................................................

4 In the category "neighbouring", enable the following check "Target Cell Consistency" and

select "Autofix"

EI_UMTS_42

EI_UMTS_43

Neighboring Plan Update Procedures Consistency checks under WPS Access - Sheet 3

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




3-9

PRELIMINARY

PRELIMINARY

EI_UMTS_45

EI_UMTS_49

EI_UMTS_51

EI_UMTS_52

EI_UMTS_55

...................................................................................................................................................................................................

5 Click OK to launch the check

...................................................................................................................................................................................................

6 Errors corresponding to the new Scrambling Code plan on the neighbouring Links will

appear in the Check Session report.

...................................................................................................................................................................................................

7 Click Re-run check session

...................................................................................................................................................................................................

8 Check that no error appears in the Check Session report. (ote: if you are warn that you

have reached the maximum number of displayed error allowed by the System, repeat step

7 until no error appears)

Troubleshooting

In case of errors, contact your local Engineering representative and correct them.

Final status

At this step, you have a planning view under WPSACCESS with a neighboring plan up

to date.

The configuration is error free.

Neighboring Plan Update Procedures Consistency checks under WPS Access - Sheet 3

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

E N D O F S T E P S....................................................................................................................................................................................................................................

Modifications of the Neighboring Plan under WPS Access -

Sheet 4

Purpose

This step details how to manage under WPSACCESS the neighboring links by using the

basic WPSACCESS features. Please note that this step applies only for light

modifications of the neighboring links!

Input parameters

From cell planning representative the following information must be available:

The outgoing GSM neighboring links of ode Bs

The GSM Cell relative to the GSM eighboring links created under the RC

The updated UMTS neighboring links

(Optional) The results of the network checker execution, with the objects and

attributes which generated the errors and/or warnings.

Initial status

In a "Workspace" under WPSAccess, the neighboring links and GSM cells are up to date.

Duration



Impact on service

one.

Procedure

...................................................................................................................................................................................................

1 Under WPSACCESS, create a new Workorder and rename it (for example: "eighboring

plan modification") as described in document [R3]

...................................................................................................................................................................................................

2 By using the Editor and/or Workorder Inhibition and/or the operations of eighbors

Creation (See document [R3]) and the input data, modify the neighboring links (UMTS

and/or GSM).

Neighboring Plan Update Procedures Modifications of the Neighboring Plan under WPS Access -

Sheet 4

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




3-11

PRELIMINARY

PRELIMINARY

...................................................................................................................................................................................................

3 Launch the etwork Checker in order to verify the modification coherency, see Sheet 3

Troubleshooting

In case of trouble, delete the Workorder, redo this step.

Final status

At the end of this step the neighboring plan is up to date with desired modifications.

Neighboring Plan Update Procedures Modifications of the Neighboring Plan under WPS Access -

Sheet 4

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

E N D O F S T E P S....................................................................................................................................................................................................................................

Exporting Workorders - Sheet 5

Purpose

This procedure details how to generate the Workorder (CM XML) file, which describes

only the modified Es between the initial and the final network configuration.

This procedure enables to speed up the whole process, by importing on the main server

only the relevant modifications to apply.

Input parameters

one.

Initial status

The eighboring plan is up to date in the Workspace under WPSACCESS.

To have the initial Snapshot representing the initial etwork State and Workorders

representing the modifications to apply on the etwork.

Duration



Few minutes

Impact on service

one.

Procedure

...................................................................................................................................................................................................

1 Under WPS ACCESS, from the Workorders Menu, Right click workorders folder and

select "Merge etwork Changes"

...................................................................................................................................................................................................

2 Select an option to save your Workspace, if needed enter a new Workspace ame, and

Click Run

...................................................................................................................................................................................................

3 Close the report Window and go to the Workspace Area.

...................................................................................................................................................................................................

4 In the Workorders folder select the "Merge" Workorder, right click and click Export

workorder... (choose "on local file system" or on "live server repository")

Neighboring Plan Update Procedures Exporting Workorders - Sheet 5

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




3-13

PRELIMINARY

PRELIMINARY

...................................................................................................................................................................................................

5 Enter a , select a and click Save

ote: If Live Server repository is used perform the following:

1. Select:

HOST

Username and Password (of the server)

2. Browse in the folders and give a name to the file

3. Click OK

Troubleshooting

In case of trouble during generation of Workorder file redo this step.

Final status

At this step, the contains the Workorder (CM XML) file named

.xwo which describes only the modifications to apply on the etwork. This

file will be used for the activation. If the reverse procedure needs to be applied, the file

named _reverse.xwo in the will be used.

Neighboring Plan Update Procedures Exporting Workorders - Sheet 5

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

E N D O F S T E P S....................................................................................................................................................................................................................................

4 4Reconfiguration Activation

Overview

Purpose

This chapter describes the reconfiguration activation procedures

This chapter is divided in three parts:


Reconfiguration Activation in WMS


Contents

Reconfiguration Activation Pre-Checks 4-2

Reconfiguration Activation in WMS 4-3

Reconfiguration Activation Post-Checks 4-6

...................................................................................................................................................................................................................................

NN-20500-090




4-1

PRELIMINARY

PRELIMINARY


Purpose

This procedure aims at verifying that:



Calls can be achieved on the impacted RC

The new neighboring plan is ready to be activated: Workorder is generated.

This procedure has to be repeated for each impacted RC.

This Procedure is a recommendation and is not mandatory if all the states given by the

checks described above are well known.

Procedure

...................................................................................................................................................................................................

1 Check that no impacting Alarms exist (See document [R5])

...................................................................................................................................................................................................

2 Perform an Audit of the impacted RC(s) (See document [R5])

...................................................................................................................................................................................................

3 Perform calls on the impacted RC(s). Especially it can be interesting to pass calls on

Cells impacted by the neighboring plans update.

Final status

The etwork and the OMC are up and running without any problem. (Alarm, OMC MIB

State, Synchronization State, etc.)

The impacted RC(s) is(are) up and running.

The impacted ode B(s) is(are) up and running.

Reconfiguration Activation Reconfiguration Activation Pre-Checks

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

E N D O F S T E P S....................................................................................................................................................................................................................................

Reconfiguration Activation in WMS

Purpose

For all the impacted RCs, this activity will lead to activate the Workorder describing the

reconfiguration through the activation manager mechanism.

Input parameters

The Workorder file .xwo is available in a folder (/) of the

Main Server as described in the document referenced [R5].

Initial Status



All the Workorder files (.xwo and _reverse.xwo) generated by

WPSACCESS have been transferred to a / Main Server directory as

described in the document referenced [R5].

Duration



Impact on service

one.

Procedure

...................................................................................................................................................................................................

1 From the WMS client menu bar, select Configuration -> Sessions Manager.

Result:The Sessions Manager window appears.

...................................................................................................................................................................................................

2 From the Sessions Manager window, either:

in Session Tasks pane, click Create new session, or

in Available Sessions pane, right-click Sessions list and select New.

Result:The Create Session window appears.

...................................................................................................................................................................................................

3 In the Create Session window - Creation parameters pane, enter a .

Reconfiguration Activation Reconfiguration Activation in WMS

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




4-3

PRELIMINARY

PRELIMINARY

...................................................................................................................................................................................................

4 From the Create Session window -Workorder(s) Selection pane, in the

cmXML/ folder, select the workorder you want to activate.

...................................................................................................................................................................................................

5 Click Add to list.

Result:The Workorder is added in the right pane.

...................................................................................................................................................................................................

6 Click Next to list the impacted nodes.

Result:

The Create Session window - Excluded odes pane appears and details, for each

impacted node, activation details and impacted objects.

Select the node(s) to be excluded, if needed.

...................................................................................................................................................................................................

7 Click Launch.

Result:The Create Session window closes and the details of the created session are

displayed in the Sessions Manager window.

...................................................................................................................................................................................................

8 From the Sessions Manager window - session pane, click Summary

for .

Result:The Summary for pane expands.

...................................................................................................................................................................................................

9 In the Summary for pane, check:

the Activation Status of the nodes:

RC nodes must be in "validated" state.

the Validation Report of each node:

Select an RC to display its details in the lower part of the pane and click the here

hyperlink to display the full validation report.

Result:The session must be completed without errors.

...................................................................................................................................................................................................

10 After session creation completion without errors, in the Actions for tab

click Activation:

Select all the impacted RC(s) and click Launch

When all tasks are completed, in the "Sessions Manager" window Click Summary for

to check that all nodes are activated.


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

...................................................................................................................................................................................................

11 From the "Sessions Manager" window, in the Session List Right click

and in scroll down menu select Terminate in order to delete the session.

ote:After terminating the session if you want to restore the initial configuration go

to chapter 6 (Reverse Procedure) and activate the reverse Workorder

Troubleshooting

All commands are logged in the Command Manager (See document [R5])

Failed Step Node Status Action

3.5 "Excluded" In case of errors in session creation analyze logs or

contact your local support or etwork Designers in

order to correct the XML file. Abort the session and

return to step 1.

3.6 "Validation Failed" In case of errors in session validation, analyze logs or

contact your local support or etwork Designers in

order to correct the XML file, Abort the session and

return to step 1.

4.2 "Activation Partly

realized"

In the Command Manager window check the status of

impacted RCs:

If the Status is "Completed with errors":

Fallback ALL the RC C-odes (See document [R5]):

If the Fallback is completed : Terminate the session and

go to Chapter 6 (Reverse Procedure) to restore the initial

configuration of the other nodes using the reverse

Workorder.

If the Fallback failed: Abort then terminate the session

and go to Chapter 6 (Reverse Procedure) to restore the

initial configuration

Final status

At the end of this step, the new configuration has been loaded at OMC side and has been

activated into the RC(s).


...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




4-5

PRELIMINARY

PRELIMINARY

E N D O F S T E P S...................................................................................................................................................................................................


Purpose

This procedure aims at verifying that:



Calls can be achieved on the impacted RC

The new neighboring plan is OK.

This procedure has to be repeated for each impacted RC.

This Procedure is a recommendation and is not mandatory if all the states given by the

checks described above are well known.

Procedure

...................................................................................................................................................................................................

1 Check that no impacting Alarms exist (See document [R5])

...................................................................................................................................................................................................

2 Perform calls on the impacted RC(s). Especially it can be interesting to pass calls on

Cells for which the neighboring plans have been updated.

Final status



The impacted RC(s) is(are) up and running.

The impacted ode B(s) is(are) up and running.

The new neighboring plan is in service.

Reconfiguration Activation Reconfiguration Activation Post-Checks

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

E N D O F S T E P S....................................................................................................................................................................................................................................

5 5Reverse procedures

Overview

Purpose

This chapter describes the reverse procedure.

Pre-Requisites

All the steps of the new neighboring plan procedure have been completed or the

Troubleshooting required going back to the Initial Configuration.

Input Parameters

The Workorder file _reverse.xwo mandatory for reverse operation (See

/) must be available.

The used XML file will be found under this latter folder only.

Duration



Contents

Fallback Workorder Activation for RCs (C-ode Part) in case of Fallback

failure

5-2

Reverse Workorder Activation 5-5

...................................................................................................................................................................................................................................

NN-20500-090




5-1

PRELIMINARY

PRELIMINARY

Fallback Workorder Activation for RNCs (C-Node Part) in case

of Fallback failure

Purpose

If the Fallback of all RC C-odes has been successful skipped the steps 1 to 6 described

below.

Go through the following sequences taking into account data coming from

/ folder.

Procedure

...................................................................................................................................................................................................

1 In WMS and for each RC C-ode named on which Fallback has failed,

Launch the "Sessions Manager" from the WMS client menu bar

...................................................................................................................................................................................................

2 From the WMS client menu bar, select Configuration -> Sessions Manager.

Result:The Sessions Manager window appears.

...................................................................................................................................................................................................

3 From the Sessions Manager window, either:

in Session Tasks pane, click Create new session, or

in Available Sessions pane, right-click Sessions list and select New.

Result:The Create Session window appears.

...................................................................................................................................................................................................

4 In the Create Session window - Creation parameters pane, enter a .

...................................................................................................................................................................................................

5 From the Create Session window -Workorder(s) Selection pane, in the

cmXML/ folder, select the reverse workorder file

_reverse.xwo you want to activate.

...................................................................................................................................................................................................

6 Click Add to list.

Result:The reverse workorder is added in the right pane.

...................................................................................................................................................................................................

7 Click Next to display the impacted nodes.

Reverse procedures Fallback Workorder Activation for RNCs (C-Node Part) in

case of Fallback failure

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................



NN-20500-090


PRELIMINARY

PRELIMINARY

Result:The Create Session window - Excluded odes pane appears and details, for

each impacted node, activation details and impacted objects.

...................................................................................................................................................................................................

8 Click Launch.

Result:The Create Session window closes and the details of the created session are

displayed in the Sessions Manager window.

...................................................................................................................................................................................................

9 In the "Sessions Manager" window, Click Summary for and

check the Activation Status of the nodes: RC should be in "Validated" state.

Change by right clicking the activation type to CRITICAL

...................................................................................................................................................................................................

10 In the "Sessions Manager" window, In the "Actions for tab click

Activation

Select all the impacted RCs and click Launch

When all tasks are completed, in the "Sessions Manager" window Click Summary for

to check that all nodes are activated

...................................................................................................................................................................................................

11 From the "Sessions Manager" window, in the Session List Right click and in scroll down menu select Terminate in order to delete the session

Troubleshooting

Failed step Node status Action

3 "Excluded" In case of errors in session creation, analyze logs or

contact your local support or etwork Designers in order

to correct the XML file, Abort then terminate the session

and return to step 1

4 "Validation Failed" In case of errors in session validation, analyze logs or

contact your local support or etwork Designers in order

to correct the XML file, Abort then terminate the session

and return to step 1

Reverse procedures Fallback Workorder Activation for RNCs (C-Node Part) in

case of Fallback failure

...................................................................................................................................................................................................................................

...................................................................................................................................................................................................................................

NN-20500-090




5-3

PRELIMINARY

PRELIMINARY

E N D O F S T E P S...................................................................................................................................................................................................

Failed step Node status Action

5 "Activation Partly

realized"

In the Command Manager window check the status of

impacted RC C-ode:

In case of Build failure (the Status is "Stopped with

errors"), analyze the logs or contact your local support or

etwork Designers in order to correct the problem (i.e.

problem of XML file, transmission cut while building).

Once the problem identified and corrected, return to step

5

Final Status

The neighboring plan is back to the initial configuration.

Reverse procedure

Documents

NN-20500-090 (9300 W-CDMA Product Family - Neighboring Plan Update NRP) 11