NN-20500-086 (9300 W-CDMA Product Family - WMS Scrambling Code Update NRP) 09

Title page

W-CDMA

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

WMS Scrambling Code Plan Update (NRP)

NN-20500-086

ISSUE 9.02

NOVEMBER 2009

Alcatel-Lucent – Internal

Proprietary – Use pursuant to Company instruction

Proprietary Use pursuant to Company instruction

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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.

Proprietary Use pursuant to Company instruction



PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Contents

About this document

Purpose ............................................................................................................................................................................................. ixix

Reason for revision ...................................................................................................................................................................... ixix

�ew in this release ....................................................................................................................................................................... ixix

Intended audience ......................................................................................................................................................................... ixix

Supported systems ......................................................................................................................................................................... xx

How to use this document ........................................................................................................................................................... xx

Prerequisites ..................................................................................................................................................................................... xx

Vocabulary conventions ............................................................................................................................................................... xx

Conventions used ........................................................................................................................................................................... xx

Related information ..................................................................................................................................................................... xixi

Document support ....................................................................................................................................................................... xixi

Technical support ......................................................................................................................................................................... xixi

How to order ................................................................................................................................................................................... xixi

How to comment ........................................................................................................................................................................... xixi

1 Roadmap to Configuration Management documentation

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

Roadmap to Configuration Management documentation ........................................................................................... 1-11-1

2 Scrambling Code Plan Update Overview

Scrambling Code Plan Update Overview ......................................................................................................................... 2-12-1

Context Diagram ........................................................................................................................................................................ 2-12-1

3 Procedure preparation

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

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

NN-20500-086

Issue 9.02 November 2009



iii

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Procedure preparation .............................................................................................................................................................. 3-13-1

4 Scrambling Code Plan Update under WPS Access

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

Scrambling Code Plan Update under WPS Access ....................................................................................................... 4-24-2

Scrambling Code Update Procedures ................................................................................................................................. 4-34-3

Performing Reverse Engineering ......................................................................................................................................... 4-44-4

Importing a �ew Scrambling Code Plan Under WPS ACCESS .............................................................................. 4-64-6

�eighboring Target Cell Consistency Check under WPS Access ............................................................................ 4-94-9

Consistency Checks under WPS Access ......................................................................................................................... 4-114-11

Exporting Workorders ............................................................................................................................................................ 4-134-13

5 Reconfiguration Activation

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

Reconfiguration Activation Pre-Checks ............................................................................................................................ 5-25-2

Reconfiguration Activation in WMS .................................................................................................................................. 5-35-3

Reconfiguration Activation Post-Checks .......................................................................................................................... 5-75-7

6 Reverse Procedure

Overview ....................................................................................................................................................................................... 6-16-1

Reverse Procedure ..................................................................................................................................................................... 6-26-2

7 PM and FM Impacts

Overview ....................................................................................................................................................................................... 7-17-1

PM and FM Impacts ................................................................................................................................................................. 7-17-1

Glossary

Contents

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

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

iv Alcatel-Lucent – Internal


NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

List of tables

6-1 Fallback Workorder Activation for R�Cs (C-�ode Part) in case of Fallback failure ...................... 6-46-4

6-2 Reverse Workorder Activation .............................................................................................................................. 6-46-4

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

NN-20500-086




v

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

List of figures

2-1 Scrambling Code Plan Update: Context Diagram ......................................................................................... 2-22-2

4-1 Data Generation Scrambling Code Plan Update ............................................................................................ 4-24-2

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

NN-20500-086




vii

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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 Scrambling Code plan in a UMTS network, with

minimum impact of service on the existing R�Cs. The situation of a new Scrambling

Code plan introduction (i.e. from scratch) is also covered by the current procedure.

Reason for revision

Reasons for reissue are.

Issue number Issue date Reason for reissue

9.02 �ovember 2009 Preliminary issue

9.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-086




ix

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Supported systems

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

This document applies to the following systems:

• �ode B

• R�C

• WMS

• WPS

The following topics are out of scope of this document:

• Transmission backbone (IuB, ItF-R, ItF-B)

• Core �etwork impacts (modifications, operations)

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 are required before reading this procedure.

It is also recommended that readers become familiar with:

• 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.

About this document

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

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

x Alcatel-Lucent – Internal


NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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)

• [R5] Alcatel-Lucent 9353 Management System - User Guide (��-20500-032)

• [R6] Alcatel-Lucent 9300 W-CDMA Product Family - Terminology (��-20500-002)

• [R7] Alcatel-Lucent 9353 Management System - System Overview (��-20500-031)

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-086




xi

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

http://infodoc.alcatel-lucent.com/comments/enus/



mailto:[email protected]

mailto:[email protected]

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

1 1Roadmap to Configuration

Management

documentation

Overview

Purpose

This chapter provides the roadmap for Configuration Management documentation.

Contents

Roadmap to Configuration Management documentation 1-1

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

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

NN-20500-086




1-1

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Roadmap to Configuration Management documentation Roadmap to Configuration Management documentation

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

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

1-2 Alcatel-Lucent – Internal


NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

2 2Scrambling Code Plan

Update Overview

Scrambling Code Plan Update Overview

Purpose

The Scrambling Code plan update procedure aims at updating a scrambling code plan on

existing cell and at propagating the scrambling code changes on related neighboring links

in the UMTS network.

General Description

The Objects involved in this procedure are as follows:

• The UMTS FDD Cell (FDDCell) updated by XML file import in WPS ACCESS

• The UMTS FDD neighboring links (UMTSFDD�eighbouringCell) updated by

autocorrective Check.

Note: As WPS Access 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.

Context Diagram

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

Scrambling Code plan introduction.

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

NN-20500-086




2-1

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Figure 2-1 Scrambling Code Plan Update: Context Diagram

Scrambling Code Plan Update Overview Context Diagram

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

3 3Procedure preparation

Overview

Purpose

This chapter describes the procedures and preparation required to perform them.

Contents

Procedure preparation 3-1

Procedure preparation

Prerequisites

The �RP: "Scrambling Code 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 Scrambling Code plan are

already declared in the host R�Cs

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

NN-20500-086




3-1

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

WPS ACCESS CP XML format, as specified in“Related information” (p. xi) [R4] or

with the CM XML format, as specified in “Related information” (p. xi)[R2].

�ote: It is recommended to use the CP XML format (specified in “Related

information” (p. xi)[R4]). This Snapshot format provides extra identifiers for the

Objects and does not require specific UMTS topology information (R�C, �ode B)

that are required in the CM XML format. �evertheless some prerequisites on the

�etwork View are required in order to be able to import a CP XML file in WPS

ACESS with the Cell Planning Import Wizard:

– There must be a unique definition of GSMCell within the �etwork

– The Cell Planning Id for GSMCell, BTSCell or OneBTSCell, AntennaAccess,

AntennaSystem must be unique over the entire network

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

GSM�eighbouringCell

– R�Cid must be unique over the entire network

– The LocalCellId of the FDDCell and BTSCell or OneBTSCell must be unique

over the entire network

– The FDDCell UserLabel must be unique over the entire network

– The UMTS �eighbouring FDDCell identification and/or related FDDCell

parameter definition must be consistent with related FDDCell.

Limitations

• The procedure focuses on UTRA� �Es: R�C, and �ode B

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

terms of managed �ode Bs and UMTS FDD Cells

• The new Scrambling Code plan comes from a Cell-Planning Tool

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

document.

• The modification of the neighboring, or LAC plan is out of scope of this document

• �o modifications should be done on the Target R�Cs 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 WPS access 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.

Procedure preparation Procedure preparation

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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: Durations are given for the modification of the scrambling code for a network

with 7 R�Cs, 860 BTSEquipment and 2540 Cells.

Scrambling code plan update under WPS Access

Step Procedure Duration

1 (optional) “Performing Reverse Engineering” (p. 4-4) 30 minutes

2 “Importing a �ew Scrambling Code Plan Under

WPS ACCESS” (p. 4-6)

Few minutes

3 “�eighboring Target Cell Consistency Check

under WPS Access” (p. 4-9)

Few minutes

4 “Consistency Checks under WPS Access”

(p. 4-11)

Few minutes

5 “Exporting Workorders” (p. 4-13) Few minutes

Reconfiguration

Activation Pre-Checks


6(optional) “Reconfiguration Activation Pre-Checks” (p. 5-2) < 1 hour

Reconfiguration

Activation in WMS


7 “Reconfiguration Activation in WMS” (p. 5-3) 35 minutes

Reconfiguration

Activation

Post-Checks


8 (optional) “Reconfiguration Activation Post-Checks” (p. 5-7) < 1 hour


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

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

NN-20500-086




3-3

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Impacts

This table summarizes the impacts on the service given for each step of the procedure.

Main Steps Impact on Service

Scrambling code plan update under WPS Access �one

Reconfiguration Activation Pre-Checks �one

Reconfiguration Activation in WMS FDDCell are locked/unlocked sequentially

(*)

Reconfiguration Activation Post-Checks �one

(*) Impacted FDD Cells are locked then unlocked one by one sequentially. Then in case

of Handover failure calls might be dropped.


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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

4 4Scrambling Code Plan

Update under WPS Access

Overview

Purpose

This activity aims at defining the provisioning data required for the Scrambling Code plan

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

modifications to be applied on the UMTS FDD Cells.

Contents

Scrambling Code Plan Update under WPS Access 4-2

Scrambling Code Update Procedures 4-3

Performing Reverse Engineering 4-4

Importing a �ew Scrambling Code Plan Under WPS ACCESS 4-6

�eighboring Target Cell Consistency Check under WPS Access 4-9

Consistency Checks under WPS Access 4-11

Exporting Workorders 4-13

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

NN-20500-086




4-1

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Scrambling Code Plan Update under WPS Access

Purpose

This activity aims at defining the provisioning data required for the Scrambling Code plan

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

modifications to be applied on the UMTS FDD Cells.

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 Scrambling Code

plan:

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 Scrambling Code plan.

Step Procedure

1 (Optional) “Performing Reverse Engineering” (p. 4-4)

2 “Importing a �ew Scrambling Code Plan Under WPS ACCESS” (p. 4-6)

Figure 4-1 Data Generation Scrambling Code Plan Update

Scrambling Code Plan Update under WPS Access Scrambling Code Plan Update under WPS Access

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Step Procedure

3 “�eighboring Target Cell Consistency Check under WPS Access” (p. 4-9)

4 “Consistency Checks under WPS Access” (p. 4-11)

5 “Exporting Workorders” (p. 4-13)

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

Scrambling Code plan information is available.

CP XML Interface OVERVIEW

WPS ACCESS provides a specific interface for Cell Planning Tools based on XML

format, named CP XML, and described in “Related information” (p. xi) [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 “Related information”

(p. xi) [R2] and to be independent from the Topology (R�C, �ode B).

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

This Wizard provides 2 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 neighbouring Cells defined in

WPS ACCESS 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

neighbouring Cells defined in the CP XML file will be updated (if already defined in

WPS ACCESS) or created (if not defined in WPS ACCESS) by the Cell Planning

Import Wizard.

Scrambling Code Update Procedures

This chapter details the following procedures:

• “Performing Reverse Engineering” (p. 4-4)

• “Importing a �ew Scrambling Code Plan Under WPS ACCESS” (p. 4-6)

• “�eighboring Target Cell Consistency Check under WPS Access” (p. 4-9)

• “Consistency Checks under WPS Access” (p. 4-11)

• “Exporting Workorders” (p. 4-13)

Scrambling Code Plan Update under WPS Access Scrambling Code Plan Update under WPS Access

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

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

NN-20500-086




4-3

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Performing Reverse Engineering

Purpose

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

view of the current network configuration into WPS ACCESS if the WPS ACCESS view

is not up-to-date.

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

WPS ACCESS 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

WPS ACCESS is installed and ready to be used. The template files are imported.

Duration

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

See MEA� 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 WPS ACCESS PC directory).

Scrambling Code Plan Update under WPS Access Performing Reverse Engineering

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

2 Under WPS ACCESS:

• Open a new Workspace. Refer to procedure "Open a workspace" in “Related

information” (p. xi) [R3] for details of workspace creation

• From the file menu launch the "Import and Export-":

1. Select "Import Snapshot" (form the Local file system or the Live server

repository) and click Next

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

3. Click Browse

4. Select the XML file exported step 1 and Click Open

5. Click Next

6. If a part of the snapshot need to be excluded Click Edit Filter Choose Objects to

import and Click Next otherwise Click Next

7. 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.

Scrambling Code Plan Update under WPS Access Performing Reverse Engineering

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

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

NN-20500-086




4-5

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

Importing a New Scrambling Code Plan Under WPS ACCESS

Purpose

This step details how to proceed with WPS ACCESS in order to import the new

Scrambling Code plan.

Input parameters

All Design parameters regarding the new Scrambling Code plan need to be provided to

the Application Engineer by the �etwork Designers, i.e.

• Cell planning information

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

the Document “Related information” (p. xi) [R4] or through a CM XML snapshot or

workorder file following the CM XML format described in “Related information”

(p. xi) [R2].

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

file:

• FDDCell (containing the new Scrambling Code Value)

• Required if the option "Delete un-impacted neighbouring links" is chosen for CP

XML file Import:

For those FDD Cells, the full list of (UMTS and GSM) �eighbouring Cells must be

provided.

If the �ew Scrambling Code Plan is provided through a CP XML file, perform “CP

XML Snapshot procedure” (p. 4-7) only.

If the �ew Scrambling Code Plan is provided through a CM XML file, through a

Workorder, perform “CM XML format Workorder procedure” (p. 4-7) only.

If the �ew Scrambling Code Plan is provided through a CM XML file, through a

Snapshot,, perform “CM XML format Snapshot procedure” (p. 4-8) only.

Initial status

Under WPS ACCESS, a Workspace describing the current configuration of your network

is available. Templates files, RRM tree are imported.

Duration


See MEA� TIME chapter for dimensioning info

Few minutes.

Impact on service

�one.

Scrambling Code Plan Update under WPS Access Importing a New Scrambling Code Plan Under WPS ACCESS

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

CP XML Snapshot procedure

If the �ew Scrambling Code Plan is provided through a CP XML Snapshot file:

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

1 Under WPS ACCESS, create a new Workorder and renames it (for example: "Scrambling

Code plan Import") as described in “Related information” (p. xi) [R3].

1. Under WPS ACCESS, in your Workspace, from the �etwork tree:

2. Select the �etwork

3. From the Wizards & Operation area, select the "Cell Planning Import Wizard" and

click Run

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

Operation

a. In the "Import Cell Planning file" Operation:

b. Click Browse

c. Select the CP XML Snapshot file and click Open

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

a. 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 unimpacted neighbouring links"

b. 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"

5. Click OK

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


CM XML format Workorder procedure

If the �ew Scrambling Code Plan is provided through a file in CM XML format as a

workorder:

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

1 Under WPS ACCESS, in your Workspace:

1. From the file menu launch the Import and Export wizard.

2. Select "Import Workorders" and click Next

3. Click Browse

4. Select the XML file and click Open


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

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

NN-20500-086




4-7

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

5. Click Next

6. Select "�o, proceed without saving" and click Start

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


CM XML format Snapshot procedure

If the �ew Scrambling Code Plan is provided through a file in CM XML format as a

snapshot:

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

1 Under WPS ACCESS, in your Workspace:

1. From the file menu launch the Import and Export wizard:

2. Select "Import Snapshots" and click Next

3. Select "Merge with Planned �etwork" and Click Next

4. Click Browse

5. Select the XML file and click Open

6. Click Next

7. If a part of the snapshot needs to be excluded click Edit Filter..., choose objects to

import and click Next, otherwise click Next directly.

8. Select No, proceed without savingand click Start

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


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 Scrambling Code plan is propagated under the FDD Cells impacted

under the host R�C(s).


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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

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

Neighboring Target Cell Consistency Check under WPS Access

Purpose

The procedure details how to propagate the new Scrambling Codes from the FDDCell to

the neighboring Target Cells by using a check with "Autofix" option.

Input paramters

�one.

Initial status

A new Scrambling Code plan has been imported

Duration


See MEA� TIME chapter for dimensioning info;

Few minutes.

Impact on service

�one.

Procedure

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

1 Under WPS ACCESS, create a new Workorder and rename it (for example: "target cell

consistency") as described in “Related information” (p. xi)

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

2 From the �etwork Object, launch the checker as described in “Related information”

(p. xi) [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_51

• �EI_UMTS_55

Scrambling Code Plan Update under WPS Access Neighboring Target Cell Consistency Check under WPS

Access

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

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

NN-20500-086




4-9

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

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 errors.

Final Status

At this step, you have Scrambling Code plan up to date at FDD Cells side but also

propagated into the related �eighbouring FDD Cells.

Scrambling Code Plan Update under WPS Access Neighboring Target Cell Consistency Check under WPS

Access

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

Consistency Checks under WPS Access

Purpose

The procedure details how to check the configuration consistency, according to

engineering rules.

Input paramters

�one.

Initial status

The new Scrambling Code plan is up to date under WPS ACCESS.

Duration



Few minutes.

Impact on service

�one.

Procedure

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

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

checks") as described in “Related information” (p. xi) [R3]

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

2 Launch checks from the network as described in “Related information” (p. xi) [R3]

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

3 Check that no error appears in the Check Session report.

Troubleshooting

In case of error, contact your local Engineering representative and correct the reported

errors.

Scrambling Code Plan Update under WPS Access Consistency Checks under WPS Access

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

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

NN-20500-086




4-11

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

Final Status

At this step, you have the new Scrambling Code plan up to date under WPS ACCESS.

The configuration is error-free.

Scrambling Code Plan Update under WPS Access Consistency Checks under WPS Access

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Exporting Workorders

Purpose

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

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 paramters

�one.

Initial status

To have the new Scrambling Code up to date under WPS ACCESS.

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 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")

Scrambling Code Plan Update under WPS Access Exporting Workorders

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

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

NN-20500-086




4-13

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

5 Enter a Filename, select a Result_folder and click Save

�ote: If Live Server repository is used perform the following: (TBC)

• Select "HOST" then the Username and Password (of the server)

• Browse in the folders and give a name to the file

• Click OK

Troubleshooting

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

Final Status

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

Filename.xwo which describes only the modifications. This file will be used for the

activation. If the reverse procedure needs to be applied, the file named Filename_rever-

se.xwo in the Result_folder will be used.

Scrambling Code Plan Update under WPS Access Exporting Workorders

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

5 5Reconfiguration Activation

Overview

Purpose

Contents

Reconfiguration Activation Pre-Checks 5-2

Reconfiguration Activation in WMS 5-3

Reconfiguration Activation Post-Checks 5-7

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

NN-20500-086




5-1

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Reconfiguration Activation Pre-Checks

Purpose

This procedure aims at verifying that:



• Calls can be achieved on the impacted R�C

• The new scrambling code plan is ready to be activated: Workorder is generated...

This procedure has to be repeated for each impacted R�C.

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 “Related information” (p. xi) [R5] and [R7])

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

2 Launch checks from the network as described in “Related information” (p. xi) [R3]

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

3 Check that no error appears in the Check Session report.

Final Status

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

State, Synchronization State, etc.)

The impacted R�C(s) is (are) up and running

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

Reconfiguration Activation Reconfiguration Activation Pre-Checks

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

Reconfiguration Activation in WMS

Purpose

For all the impacted R�Cs, this activity will lead to activate the Workorder describing the

reconfiguration through the activation manager mechanism.

Input parameters

The Workorder file Filename.xwo is available in a folder (/Result_folder of the Main

Server as described in “Related information” (p. xi) [R5].

Initial status

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

State, Synchronization State, etc.).

All the Workorder files (Filename.xwo and Filename_reverse.xwo) generated by WPS

ACCESS have been transferred to a /Result_folder Main Server directory as described in

“Related information” (p. xi) [R5].

Duration



35 minutes

Impact on service

Impacted FDD Cells are locked then unlocked one by one sequentially. Then in case of

Handover failure calls might be dropped.

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.

Reconfiguration Activation Reconfiguration Activation in WMS

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

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

NN-20500-086




5-3

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Result: The Create Session window appears.

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

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

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

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

cmXML/<Result_folder> 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 In the Session Manager Window:

• In the "Sessions Manager" window Click Summary for session name and check the

Activation Status of the nodes: R�C nodes should be in "Validated" state

• Check the validation report of each node in the summary section:

Select a R�C in the table and click here the hyperlink to display the HTML validation

report.

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

9 After session creation completion without errors, in the "Actions for session name" tab

click Activation:

• Select all the impacted R�C(s) and Click Launch

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

session name to check that all nodes are activated.


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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

10 From the "Sessions Manager" window, in the Session List Right click session name 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 5 (Reverse Operation) and activate the reverse Workorder

Troubleshooting

�ote: All commands are logged in the Command Manager (See “Related

information” (p. xi) [R5])

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

the session and return to step 1.

3 "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 "Activation Partly

realized"

In the Command Manager window

check the status of impacted R�Cs:

• If the Status is "Completed with

errors":

Fallback ALL the R�C C-�odes

(See “Related information”

(p. xi) [R5]):

• If the Fallback is completed :

Terminate the session.

• If the Fallback failed: Abort then

terminate the session and go to

Chapter 5 (Reverse Step) to

restore the initial configuration


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

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

NN-20500-086




5-5

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

Final Status

At the end of this step, the new scrambling code plan has been loaded at OMC side and

has been activated into the R�C(s).


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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Reconfiguration Activation Post-Checks

Purpose

This procedure aims at verifying that:



• calls can be achieved on the impacted R�C

• The new scrambling code plan is OK.

This procedure has to be repeated for each impacted R�C.

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 “Related information” (p. xi) [R5] and [R7])

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

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

Cells for which the scrambling code plans have been updated.

Final Status



• The impacted R�C(s) is (are) up and running

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

• The new Scrambling Code Plan is in service.

Reconfiguration Activation Reconfiguration Activation Post-Checks

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

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

NN-20500-086




5-7

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

6 6Reverse Procedure

Overview

Purpose

Contents

Reverse Procedure 6-2

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

NN-20500-086




6-1

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Reverse Procedure

Prerequisites

All the steps of the new Scrambling Code plan procedure have been completed or the

Troubleshooting required going back to the Initial Configuration.

Input parameters

• The Workorder file Filename_reverse.xwo mandatory for reverse operation (See

/Result_folder>) must be available.

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

Duration



TBC

Impact on service

R�C build in case of Fallback failure in TroubleShooting part of chapter 5.2 otherwise

none.

Activation

Go through the following sequences by taking into account data coming from

/<Result_folder>:

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 <reverse session

name>.

Reverse Procedure Reverse Procedure

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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

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

cmXML/<Result_folder> folder, select the reverse workorder file

<Filename>_reverse.xwo you want to activate.

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

5 Click Add to list.

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

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

6 Click Next to display the impacted nodes.

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

each impacted node, activation details and impacted objects.

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

7 Click Launch.

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

displayed in the Sessions Manager window.

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

8 In the Session Manager window:

• In the "Sessions Manager" window Click Summary for reverse session namename"

and check the status of the nodes: R�C nodes should be in "Validated" state.

• Check the validation report of each node in the summary section:

• Select a R�C in the table and click here the hyperlink to display the HTML validation

report

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

9 After session creation completion without errors, in the "Actions for reverse session

namename" tab Click Activation:

• Select all the impacted R�C(s) and Click Launch

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

for reverse session name to check that all nodes are in state Activated.

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

10 From the "Sessions Manager" window, in the Session List Right click <reverse session

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


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

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

NN-20500-086




6-3

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

Troubleshooting

�ote: All commands are logged in the Command Manager (See “Related

information” (p. xi) [R5])

Table 6-1 Fallback Workorder Activation for RNCs (C-Node Part) in case of

Fallback failure


3 "Excluded" In case of errors in session creation,




then terminate the session and return

to step1.

4 "Validation Failed" In case of errors in session creation,





to step1.

5 "validated" In the Command Manager

window check the status of

impacted R�C C-�ode:

In case of Build failure (the Status

is "Stopped with errors"), analyze

the logs or contact your local


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.

Table 6-2 Reverse Workorder Activation


3.f "Excluded" In case of errors in session creation,





to step 1.


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

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



NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Table 6-2 Reverse Workorder Activation (continued)


3.g "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.

4.b "Activation Partly

realized"

• If the Status is "Completed

with errors": terminate the

session and check the R�Cs

Alarms:

• If the Critical Alarm "Cnode

internal synchronization error"

exists, the R�C(s) must be built

on-line in order to restore its

initial configuration. Contact

your local support and if really

required launch the Build

On-line on the impacted R�C(s)

(see document [R5]).

Final Status

The Scrambling Code plan is back to the initial configuration.


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

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

NN-20500-086




6-5

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

7 7PM and FM Impacts

Overview

Purpose

Contents

PM and FM Impacts 7-1

PM and FM Impacts

PM

The �Es are managed by the PM system.

FM Impact

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

management.

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

NN-20500-086




7-1

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Glossary

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

A AN

Access �ode

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

C CM

Configuration Management

CN

Control �ode

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

E EM

Equipment Monitor

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

F FM

Fault Management

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

G GUI

Graphical User Interface

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

I IN

Location Area Code

Itf-B`

Interface between the �ode B and its Element Manager

Itf-R

Interface between the R�C and its Element Manager

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

M MO

Managed Object

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

NN-20500-086




GL-1

PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

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

P PM

Performance Management

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

R ROC

Regional Operation Center

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

W WICL

Wireless Internet Command Language

Glossary

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

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

GL-2 Alcatel-Lucent – Internal


NN-20500-086


PR

ELIM

IN

AR

YP

RELIM

IN

AR

Y

Documents

NN-20500-086 (9300 W-CDMA Product Family - WMS Scrambling Code Update NRP) 09