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

Proprietary Use pursuant to Company instruction
PRELIMINARY
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
PRELIMINARY
Alcatel-Lucent Internal
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
PRELIMINARY
Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
About this document

Purpose
............................................................................................................................................................................................. ix
ix
Reason for revision
...................................................................................................................................................................... ix
ix
ew in this release
....................................................................................................................................................................... ix
ix
Intended audience
......................................................................................................................................................................... ix
ix
Supported systems
......................................................................................................................................................................... x
x
PRELIMINARY
Contents
How to use this document ........................................................................................................................................................... xx

Prerequisites ..................................................................................................................................................................................... xx
Vocabulary conventions ............................................................................................................................................................... xx
Conventions used
........................................................................................................................................................................... x
x
Related information
..................................................................................................................................................................... xi
xi
Document support
....................................................................................................................................................................... xi
xi
Technical support
......................................................................................................................................................................... xi
xi
How to order ................................................................................................................................................................................... xi

xi
How to comment ........................................................................................................................................................................... xi
xi
1
Roadmap to Configuration Management documentation

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

......................................................................................................................... 2-1
........................................................................................................................................................................ 2-1
2-1
Procedure preparation
Overview ....................................................................................................................................................................................... 3-1
3-1
...................................................................................................................................................................................................................................
NN-20500-086
iii
Issue 9.02 November 2009
PRELIMINARY
Context Diagram
3
........................................................................................... 1-1
PRELIMINARY
Contents
...................................................................................................................................................................................................................................
4
.............................................................................................................................................................. 3-1
3-1
Scrambling Code Plan Update under WPS Access

Overview ....................................................................................................................................................................................... 4-1
4-1
Scrambling Code Update Procedures
Performing Reverse Engineering
....................................................................................................... 4-2
................................................................................................................................. 4-3
......................................................................................................................................... 4-4
4-4
Importing a ew Scrambling Code Plan Under WPS ACCESS
.............................................................................. 4-6
eighboring Target Cell Consistency Check under WPS Access

Consistency Checks under WPS Access
............................................................................ 4-9
......................................................................................................................... 4-11
Exporting Workorders ............................................................................................................................................................ 4-13

4-13
5
Reconfiguration Activation
Overview ....................................................................................................................................................................................... 5-1
5-1
Reconfiguration Activation Pre-Checks
Reconfiguration Activation in WMS
............................................................................................................................ 5-2
.................................................................................................................................. 5-3
5-3
Reconfiguration Activation Post-Checks

6
.......................................................................................................................... 5-7
Reverse Procedure
Overview ....................................................................................................................................................................................... 6-1
6-1
Reverse Procedure
..................................................................................................................................................................... 6-2
6-2
PM and FM Impacts
Overview ....................................................................................................................................................................................... 7-1
7-1
PM and FM Impacts
................................................................................................................................................................. 7-1
7-1
PRELIMINARY
Glossary
...................................................................................................................................................................................................................................
NN-20500-086
iv
6-1
Fallback Workorder Activation for RCs (C-ode Part) in case of Fallback failure
...................... 6-4
6-2
Reverse Workorder Activation .............................................................................................................................. 6-4
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
v
PRELIMINARY
List of tables
PRELIMINARY
PRELIMINARY
2-1
Scrambling Code Plan Update: Context Diagram
4-1
Data Generation Scrambling Code Plan Update
......................................................................................... 2-2
............................................................................................ 4-2
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
vii
PRELIMINARY
List of figures
PRELIMINARY
PRELIMINARY
PRELIMINARY
About this document

About 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 RCs. 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
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
ix
PRELIMINARY
About this document

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

This document applies to the following systems:
ode B
RC
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
PRELIMINARY
one.
...................................................................................................................................................................................................................................
NN-20500-086
...................................................................................................................................................................................................................................
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)
PRELIMINARY
About this document
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
(comments@alcatel-lucent.com) .
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
xi
PRELIMINARY
PRELIMINARY
PRELIMINARY
1oadmap to Configuration
R
Management
documentation
Overview
Purpose
This chapter provides the roadmap for Configuration Management documentation.

Contents
1-1

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
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
1-1
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
NN-20500-086
1-2
S2crambling Code Plan

Update Overview
PRELIMINARY

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 (UMTSFDDeighbouringCell) 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.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
2-1
PRELIMINARY
PRELIMINARY
Context Diagram
...................................................................................................................................................................................................................................
Figure 2-1 Scrambling Code Plan Update: Context Diagram
...................................................................................................................................................................................................................................
NN-20500-086
2-2
PRELIMINARY
3
Overview
Purpose
This chapter describes the procedures and preparation required to perform them.
Contents
3-1
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 RCs
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
3-1
PRELIMINARY
...................................................................................................................................................................................................................................
The configuration files coming from the Cell Planning Tool can be compatible with
WPS ACCESS CP XML format, as specified inRelated 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 (RC, 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

GSMeighbouringCell
RCid 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
PRELIMINARY
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 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 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 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.
...................................................................................................................................................................................................................................
NN-20500-086
3-2
...................................................................................................................................................................................................................................
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.
PRELIMINARY
ote: Durations are given for the modification of the scrambling code for a network
with 7 RCs, 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
Importing a ew Scrambling Code Plan Under

WPS ACCESS (p. 4-6)
Few minutes
eighboring Target Cell Consistency Check

under WPS Access (p. 4-9)
Few minutes

(p. 4-11)
Few minutes
Exporting Workorders (p. 4-13)
Few minutes
Step
Procedure
Duration
6(optional)
Reconfiguration Activation Pre-Checks (p. 5-2)
< 1 hour
Step
Procedure
Duration
Reconfiguration Activation in WMS (p. 5-3)
35 minutes
Step
Procedure
Duration
8 (optional)
Reconfiguration Activation Post-Checks (p. 5-7)
< 1 hour
Reconfiguration
Activation Pre-Checks
Reconfiguration
Activation in WMS
Reconfiguration
Activation
Post-Checks
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
3-3
PRELIMINARY
...................................................................................................................................................................................................................................
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
one
FDDCell are locked/unlocked sequentially

(*)
one
PRELIMINARY
(*) Impacted FDD Cells are locked then unlocked one by one sequentially. Then in case
of Handover failure calls might be dropped.
...................................................................................................................................................................................................................................
NN-20500-086
3-4
PRELIMINARY
S4crambling 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
4-2
4-3
4-4
Importing a ew Scrambling Code Plan Under WPS ACCESS
4-6
eighboring Target Cell Consistency Check under WPS Access
4-9
4-11
Exporting Workorders
4-13
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
4-1
PRELIMINARY
...................................................................................................................................................................................................................................

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:
Figure 4-1 Data Generation Scrambling Code Plan Update
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 Scrambling Code plan.
Step
Procedure
1 (Optional)
Importing a ew Scrambling Code Plan Under WPS ACCESS (p. 4-6)
...................................................................................................................................................................................................................................
NN-20500-086
4-2
...................................................................................................................................................................................................................................
Step
Procedure
eighboring Target Cell Consistency Check under WPS Access (p. 4-9)
Consistency Checks under WPS Access (p. 4-11)
PRELIMINARY
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 (RC, 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.

This chapter details the following procedures:
eighboring Target Cell Consistency Check under WPS Access (p. 4-9)
Consistency Checks under WPS Access (p. 4-11)
...................................................................................................................................................................................................................................
NN-20500-086
4-3
PRELIMINARY

Importing a ew Scrambling Code Plan Under WPS ACCESS (p. 4-6)
PRELIMINARY
...................................................................................................................................................................................................................................

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
...................................................................................................................................................................................................
PRELIMINARY
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).
...................................................................................................................................................................................................................................
NN-20500-086
4-4
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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
PRELIMINARY
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
...................................................................................................................................................................................................
After import completion, check the report and close it.

E...................................................................................................................................................................................................
N D O F S T E P S
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.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
4-5
PRELIMINARY
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
PRELIMINARY
See MEA TIME chapter for dimensioning info

Few minutes.
Impact on service
one.
...................................................................................................................................................................................................................................
NN-20500-086
4-6
...................................................................................................................................................................................................................................
CP XML Snapshot procedure
If the ew Scrambling Code Plan is provided through a CP XML Snapshot file:
...................................................................................................................................................................................................
Under WPS ACCESS, create a new Workorder and renames it (for example: "Scrambling
Code plan Import") as described in Related information (p. xi) [R3].
PRELIMINARY
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
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
CM XML format Workorder procedure
If the ew Scrambling Code Plan is provided through a file in CM XML format as a
workorder:
...................................................................................................................................................................................................
Under WPS ACCESS, in your Workspace:
3. Click Browse
4. Select the XML file and click Open
...................................................................................................................................................................................................................................
NN-20500-086
4-7
PRELIMINARY
1. From the file menu launch the Import and Export wizard.
2. Select "Import Workorders" and click Next
PRELIMINARY
...................................................................................................................................................................................................................................
5. Click Next
6. Select "o, proceed without saving" and click Start
...................................................................................................................................................................................................
E....................................................................................................................................................................................................................................
N D O F S T E P S
CM XML format Snapshot procedure
If the ew Scrambling Code Plan is provided through a file in CM XML format as a
snapshot:
...................................................................................................................................................................................................
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
...................................................................................................................................................................................................
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.
PRELIMINARY
Final Status
At this step, the new Scrambling Code plan is propagated under the FDD Cells impacted
under the host RC(s).
...................................................................................................................................................................................................................................
NN-20500-086
4-8
Neighboring Target Cell Consistency Check under WPS

Access
...................................................................................................................................................................................................................................
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.
PRELIMINARY
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
...................................................................................................................................................................................................
Under WPS ACCESS, create a new Workorder and rename it (for example: "target cell
consistency") as described in Related information (p. xi)
...................................................................................................................................................................................................
From the etwork Object, launch the checker as described in Related information
(p. xi) [R3].
...................................................................................................................................................................................................
In the Checks Window, select a check, right click Disable All

...................................................................................................................................................................................................
EI_UMTS_42
EI_UMTS_51
EI_UMTS_55
...................................................................................................................................................................................................................................
NN-20500-086
4-9
PRELIMINARY
In the category "neighbouring", enable the following check "Target Cell Consistency" and
select "Autofix"
PRELIMINARY
Neighboring Target Cell Consistency Check under WPS

Access
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Click OK, to launch the check

...................................................................................................................................................................................................
Errors corresponding to the new Scrambling Code plan on the neighbouring Links will
appear in the Check Session report.
...................................................................................................................................................................................................
Click Re-run check session

...................................................................................................................................................................................................
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)
E....................................................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of errors, contact your local Engineering representative and correct errors.
Final Status
PRELIMINARY
At this step, you have Scrambling Code plan up to date at FDD Cells side but also
propagated into the related eighbouring FDD Cells.
...................................................................................................................................................................................................................................
NN-20500-086
4-10
...................................................................................................................................................................................................................................

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

engineering rules.
PRELIMINARY
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
...................................................................................................................................................................................................
Under WPS ACCESS, create a new Workorder and rename it (for example: "consistency
checks") as described in Related information (p. xi) [R3]
...................................................................................................................................................................................................
Launch checks from the network as described in Related information (p. xi) [R3]
...................................................................................................................................................................................................
Check that no error appears in the Check Session report.

E...................................................................................................................................................................................................
N D O F S T E P S
In case of error, contact your local Engineering representative and correct the reported
errors.
...................................................................................................................................................................................................................................
NN-20500-086
4-11
PRELIMINARY
Troubleshooting
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
Final Status
At this step, you have the new Scrambling Code plan up to date under WPS ACCESS.
The configuration is error-free.
...................................................................................................................................................................................................................................
NN-20500-086
4-12
...................................................................................................................................................................................................................................
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.
PRELIMINARY
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
...................................................................................................................................................................................................
Under WPS ACCESS, from the Workorders Menu select "Merge etwork Changes"
...................................................................................................................................................................................................
Select an option to save your Workspace, if needed enter a new Workspace ame, and
Click Run
...................................................................................................................................................................................................
Close the report Window and go to the Workspace Area.

...................................................................................................................................................................................................
In the Workorders folder select the "Merge" Workorder, right click and click Export
workorder (choose "on local file system" or on "live server repository")
...................................................................................................................................................................................................................................
NN-20500-086
4-13
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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
E....................................................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of trouble during generation of Workorder file redo this step.

Final Status
PRELIMINARY
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_reverse.xwo in the Result_folder will be used.
...................................................................................................................................................................................................................................
NN-20500-086
4-14
PRELIMINARY
5
Overview
Purpose
Contents
5-2
5-3
5-7
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
5-1
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
This procedure aims at verifying that:
Calls can be achieved on the impacted RC
The new scrambling code 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
...................................................................................................................................................................................................
Check that no impacting Alarms exist (See Related information (p. xi) [R5] and [R7])
...................................................................................................................................................................................................
Launch checks from the network as described in Related information (p. xi) [R3]
...................................................................................................................................................................................................
Check that no error appears in the Check Session report.
E....................................................................................................................................................................................................................................
N D O F S T E P S
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
PRELIMINARY
The impacted ode B(s) is (are) up and running
...................................................................................................................................................................................................................................
NN-20500-086
5-2
...................................................................................................................................................................................................................................

Purpose
For all the impacted RCs, this activity will lead to activate the Workorder describing the
reconfiguration through the activation manager mechanism.
PRELIMINARY
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
...................................................................................................................................................................................................
From the WMS client menu bar, select Configuration -> Sessions Manager.
Result: The Sessions Manager window appears.
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................................................
NN-20500-086
5-3
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
Result: The Create Session window appears.

...................................................................................................................................................................................................
In the Create Session window - Creation parameters pane, enter a <Session Name>.
...................................................................................................................................................................................................
From the Create Session window - Workorder(s) Selection pane, in the

cmXML/<Result_folder> folder, select the workorder you want to activate.
...................................................................................................................................................................................................
Click Add to list.

Result: The Workorder is added in the right pane.
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
Click Launch.
Result: The Create Session window closes and the details of the created session are
displayed in the Sessions Manager window.
...................................................................................................................................................................................................
In the Session Manager Window:
In the "Sessions Manager" window Click Summary for session name and check the
Activation Status of the nodes: RC nodes should be in "Validated" state
Check the validation report of each node in the summary section:
Select a RC in the table and click here the hyperlink to display the HTML validation
report.
...................................................................................................................................................................................................
PRELIMINARY
After session creation completion without errors, in the "Actions for session name" 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
session name to check that all nodes are activated.
...................................................................................................................................................................................................................................
NN-20500-086
5-4
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
E...................................................................................................................................................................................................
N D O F S T E P S
PRELIMINARY
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
"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.
"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.
"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 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
PRELIMINARY
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
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 RC(s).
...................................................................................................................................................................................................................................
NN-20500-086
5-6
...................................................................................................................................................................................................................................

Purpose
This procedure aims at verifying that:
calls can be achieved on the impacted RC
The new scrambling code plan is OK.
PRELIMINARY
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
...................................................................................................................................................................................................
Check that no impacting Alarms exist (See Related information (p. xi) [R5] and [R7])
...................................................................................................................................................................................................
Perform calls on the impacted RC(s). Especially it can be interesting to pass calls on
Cells for which the scrambling code plans have been updated.
E...................................................................................................................................................................................................
N D O F S T E P S
Final Status
The impacted RC(s) is (are) up and running

The impacted ode B(s) is (are) up and running
The new Scrambling Code Plan is in service.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
5-7
PRELIMINARY
PRELIMINARY
PRELIMINARY
Reverse Procedure
6
Overview
Purpose
Contents
Reverse Procedure
6-2
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
6-1
PRELIMINARY
Reverse Procedure
Reverse Procedure
...................................................................................................................................................................................................................................
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
RC 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
...................................................................................................................................................................................................
From the WMS client menu bar, select Configuration -> Sessions Manager.
Result: The Sessions Manager window appears.
...................................................................................................................................................................................................
PRELIMINARY
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.
...................................................................................................................................................................................................
In the Create Session window - Creation parameters pane, enter a <reverse session
name>.
...................................................................................................................................................................................................................................
NN-20500-086
6-2
Reverse Procedure
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
Click Add to list.
PRELIMINARY
Reverse Procedure
Result: The reverse workorder is added in the right pane.

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

...................................................................................................................................................................................................
Click Launch.
Result: The Create Session window closes and the details of the created session are
displayed in the Sessions Manager window.
...................................................................................................................................................................................................
In the Session Manager window:
In the "Sessions Manager" window Click Summary for reverse session namename"
and check the status of the nodes: RC nodes should be in "Validated" state.
Check the validation report of each node in the summary section:

Select a RC in the table and click here the hyperlink to display the HTML validation
report
...................................................................................................................................................................................................
After session creation completion without errors, in the "Actions for reverse session
namename" 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 reverse session name to check that all nodes are in state Activated.
...................................................................................................................................................................................................
10
E...................................................................................................................................................................................................
N D O F S T E P S
...................................................................................................................................................................................................................................
NN-20500-086
6-3
PRELIMINARY
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.
PRELIMINARY
Reverse Procedure
Reverse Procedure
...................................................................................................................................................................................................................................
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
failed Step
Node Status
Action
"Excluded"

then terminate the session and return
to step1.
"Validation Failed"

to step1.
"validated"
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
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.
PRELIMINARY
Table 6-2
Reverse Workorder Activation
failed Step
Node Status
Action
3.f
"Excluded"

to step 1.
...................................................................................................................................................................................................................................
NN-20500-086
6-4
Reverse Procedure
...................................................................................................................................................................................................................................
Table 6-2
Reverse Workorder Activation
(continued)
failed Step
Node Status
Action
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 RCs
Alarms:
If the Critical Alarm "Cnode

internal synchronization error"
exists, the RC(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 RC(s)
(see document [R5]).
PRELIMINARY
Reverse Procedure
Final Status
The Scrambling Code plan is back to the initial configuration.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
6-5
PRELIMINARY
PRELIMINARY
PRELIMINARY
PM and FM Impacts
7
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.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-086
7-1
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
AN
Access ode
PRELIMINARY
Glossary
...................................................................................................................................................................................................................................
CM
Configuration Management
CN
Control ode
...................................................................................................................................................................................................................................
EM
Equipment Monitor
...................................................................................................................................................................................................................................
FM
Fault Management
...................................................................................................................................................................................................................................
GUI
Graphical User Interface

...................................................................................................................................................................................................................................
IN
Location Area Code

Itf-B`
Interface between the ode B and its Element Manager

Itf-R
Interface between the RC and its Element Manager
MO
Managed Object
...................................................................................................................................................................................................................................
NN-20500-086
GL-1
PRELIMINARY
...................................................................................................................................................................................................................................
PRELIMINARY
Glossary
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
PM
Performance Management
...................................................................................................................................................................................................................................
ROC
Regional Operation Center

...................................................................................................................................................................................................................................
WICL
PRELIMINARY
Wireless Internet Command Language
...................................................................................................................................................................................................................................
NN-20500-086
GL-2

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

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

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

Uploaded by

Copyright:

Available Formats

Proprietary Use pursuant to Company instruction

Proprietary Use pursuant to Company instruction

About this document

Reason for revision

ew in this release

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

How to order ................................................................................................................................................................................... xi

Roadmap to Configuration Management documentation

Scrambling Code Plan Update Overview

Scrambling Code Plan Update under WPS Access

Importing a ew Scrambling Code Plan Under WPS ACCESS

eighboring Target Cell Consistency Check under WPS Access

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

Reconfiguration Activation Post-Checks

Reverse Workorder Activation .............................................................................................................................. 6-4

Scrambling Code Plan Update: Context Diagram

Data Generation Scrambling Code Plan Update

About this document

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

Reasons for reissue are.

Reason for reissue

Initial draft issue for V7.1

New in this release

The audience for this document is:

Configuration management personnel

About this document

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

The following topics are out of scope of this document:

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

How to use this document

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

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

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

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

About this document

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

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

This chapter provides the roadmap for Configuration Management documentation.

Roadmap to Configuration Management documentation

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

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

Roadmap to Configuration Management documentation

Roadmap to Configuration Management documentation

S2crambling Code Plan

Scrambling Code Plan Update Overview

The Objects involved in this procedure are as follows:

Scrambling Code Plan Update Overview

Figure 2-1 Scrambling Code Plan Update: Context Diagram

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

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

Performing Reverse Engineering (p. 4-4)

Importing a ew Scrambling Code Plan Under

eighboring Target Cell Consistency Check

Consistency Checks under WPS Access

Exporting Workorders (p. 4-13)

Reconfiguration Activation Pre-Checks (p. 5-2)

Reconfiguration Activation in WMS (p. 5-3)

Reconfiguration Activation Post-Checks (p. 5-7)

Scrambling code plan update under WPS Access

Reconfiguration Activation Pre-Checks

Reconfiguration Activation in WMS

FDDCell are locked/unlocked sequentially

Reconfiguration Activation Post-Checks

S4crambling Code Plan