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

Proprietary Use pursuant to Company instruction
PRELIMINARY
Title page
W-CDMA
Alcatel-Lucent 9300 W-CDMA Product Family | V7.1
Neighboring Plan Update (NRP)
NN-20500-090
ISSUE 11.02
NOVEMBER 2009
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
.............................................................................................................................................................................................. v
v
PRELIMINARY
Contents
Reason for revision ........................................................................................................................................................................ vv

ew in this release ......................................................................................................................................................................... vv
Intended audience
.......................................................................................................................................................................... v
v
Supported systems ........................................................................................................................................................................ vi

vi
How to use this document
Prerequisites
......................................................................................................................................................... vi
vi
................................................................................................................................................................................... vi
vi
Vocabulary conventions
............................................................................................................................................................. vi
vi
Conventions used .......................................................................................................................................................................... vi

vi
Related information
Document support
...................................................................................................................................................................... vii
vii
Technical support
....................................................................................................................................................................... vii
vii
How to order
................................................................................................................................................................................. vii
vii
How to comment
1
..................................................................................................................................................................... vi
vi
......................................................................................................................................................................... vii
vii
Roadmap to Configuration Management documentation

Overview ....................................................................................................................................................................................... 1-1
1-1
........................................................................................... 1-2
Neighboring Plan Update Overview and procedure preparation

Overview ....................................................................................................................................................................................... 2-1
2-1
Procedure preparation
......................................................................................................................................................... 2-2
2-2
.............................................................................................................................................................. 2-3
2-3
eighboring Plan Update under WPS Access ................................................................................................................. 2-7

...................................................................................................................................................................................................................................
NN-20500-090
iii
Issue 11.02 November 2009
PRELIMINARY
eighboring plan update
PRELIMINARY
Contents
...................................................................................................................................................................................................................................
Neighboring Plan Update Procedures

Overview ....................................................................................................................................................................................... 3-1
3-1
Performing Reverse Engineering - Sheet 1
...................................................................................................................... 3-2
Importing a new eighboring Plan under WPS Access - Sheet 2
........................................................................... 3-4
Consistency checks under WPS Access - Sheet 3 .......................................................................................................... 3-9

Modifications of the eighboring Plan under WPS Access - Sheet 4
................................................................. 3-11
Exporting Workorders - Sheet 5 ......................................................................................................................................... 3-13

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

5
.......................................................................................................................... 4-6
Reverse procedures
Overview ....................................................................................................................................................................................... 5-1
5-1
Fallback Workorder Activation for RCs (C-ode Part) in case of Fallback failure
Reverse Workorder Activation
...................................... 5-2
.............................................................................................................................................. 5-5
5-5
PRELIMINARY
Glossary
...................................................................................................................................................................................................................................
NN-20500-090
iv
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 neighboring plan in an UMTS network, without
interruption of service on the existing RCs. The situation of new neighboring plan
introduction (i.e. from scratch) is also covered by the current procedure of neighboring
plan update.
Reason for revision
Reasons for reissue are:

Issue number
Issue date
Reason for reissue
11.02
ovember 2009
Preliminary issue
11.01
October 2009
Initial draft issue for V7.1
New in this release

New features:
one
Other changes:
one
Intended audience
The audience for this document is:

Configuration management personnel
etwork administration personnel
...................................................................................................................................................................................................................................
NN-20500-090
v
PRELIMINARY
PRELIMINARY
About this document

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

This document covers the following systems:
ode B
RC
WMS
WPS
How to use this document
Start with the first chapter and work through the manual to the end. Once you have done
this, you will have carried out the re-configuration procedure in the proper sequence.
Prerequisites
A good knowledge of UTRA configuration principles as well as Microsoft Windows T

4.0, Windows 2000 or Windows XP is required before reading this RP.
It is also recommended that readers become familiar with the following documents:
Alcatel-Lucent 9300 W-CDMA Product Family - Terminology, (-20500-002)

Alcatel-Lucent 9353 Management System - System Overview, (-20500-031)
Alcatel-Lucent 9353 Management System - User Guide, (-20500-032)
Alcatel-Lucent 9300 W-CDMA Product Family - Parameters Reference Guide,
(-20500-027)
Alcatel-Lucent 9352 Provisioning System - User Guide, (-20500-036)
Vocabulary conventions
one.
Conventions used
one.
Related information
PRELIMINARY
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
...................................................................................................................................................................................................................................
NN-20500-090
vi
...................................................................................................................................................................................................................................
[R5] Alcatel-Lucent 9353 Management System - User Guide, -20500-032

[R6] Alcatel-Lucent 9300 W-CDMA Product Family - Terminology, -20500-002
Document support
For support in using this or any other Alcatel-Lucent document, contact Alcatel-Lucent at
one of the following telephone numbers:
PRELIMINARY
About this document
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-090
vii
PRELIMINARY
PRELIMINARY
PRELIMINARY
1oadmap to Configuration
R
Management
documentation
Overview
Purpose
This chapter provides the roadmap for Configuration Management documentation.

Contents
1-2
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
1-1
PRELIMINARY
...................................................................................................................................................................................................................................

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:
PRELIMINARY
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-090
1-2
PRELIMINARY
2 eighboring Plan Update

N
Overview and procedure
preparation
Overview
Purpose
This chapter describes the eighboring Plan Update and procedure preparations
Contents
eighboring plan update
2-2
2-3
eighboring Plan Update under WPS Access
2-7
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
2-1
PRELIMINARY
Neighboring Plan Update Overview and procedure

preparation
Neighboring plan update
...................................................................................................................................................................................................................................
Neighboring plan update

General description
The neighboring plan update procedure aims at modifying the neighboring plan either due
to a new site addition or an addition, deletion, update of neighboring links in the UMTS
network.
When the modifications of the configuration data concern the neighboring links uniquely
(neighboring links are created, updated or deleted), the objects involved in this procedure
are as follows:
The UMTS neighboring links created, updated or deleted

The GSM neighboring links created, updated or deleted.
The GSM cell(s) impacted by the GSM neighboring links modification.
Note:
Equivalent activity needs to be performed on 2G system for reciprocal neighbours.

Note:
As 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
Compounding Neighouring List
Some new parameters or new parameter value are added to handle:
The priority defined per neighboring cell

The occurrence of a cell within all neighbourhoods
The parameters are:
PRELIMINARY
maxCompoundingListSizeIntraFreq
typeOfCompoundingeighbourListIntraFreq
numOfPrimaryCelleighbourIntraFreq
neighbourCellPrio
...................................................................................................................................................................................................................................
NN-20500-090
2-2
...................................................................................................................................................................................................................................
Procedure description
The following diagram displays the different steps to be conducted to perform the new
neighboring plan introduction.
PRELIMINARY

preparation
XML file provided by the Cell Planning

for Neighbouring Plan Update is available
Neighbouring Plan Update

under WPS Access
Workorder (CM XML) file for
Neighbouring Plan Update activation is available
Pre-Checks
in WPS
Post-Checks
The Neighbouring Plan is up to date
Prerequisites
The etwork and the OMC are up and running without any problem. (Alarm, OMC
MIB State, Synchronization State, etc.)
All ode B and FDDCell objects referred by the new neighboring plan are already
declared in the host RCs.
...................................................................................................................................................................................................................................
NN-20500-090
2-3
PRELIMINARY
The RP: "eighboring Plan Update", described in this document applies only if all of
the following conditions are verified:
PRELIMINARY

preparation
...................................................................................................................................................................................................................................
The RRM subtree required for the new neighboring plan is initialized on the host
RCs.
The configuration files coming from the Cell Planning Tool can be compatible with
WPS ACCESS CP XML format, as specified in document [R4] or with the CM
XML format, as specified in document [R2].
ote: It is recommended to use the CP XML format (specified in document [R4]).
This Snapshot format provides extra identifiers for the objects and does not require
specific UMTS topology information (RC, ode B) that are required in the CM
XML format. evertheless some pre-requisites on the etwork View are required in
order to be able to import a CP XML file in WPS ACCESS with the Cell Planning
Import Wizard:
There must be a unique definition of GSMCell within the etwork

The Cell Planning Id for GSMCell, BTSCell, AntennaAccess and AntennaSystem
must be unique over the entire network
Cell Planning Id must be consistent between a GSMCell and its associated
GSMeighbouringCell
RCid must be unique over the entire network
The LocalCellId of the FDDCell and BTSCell must be unique over the entire
network
The FDDCell UserLabel must be unique over the entire network
The UMTS eighboring FDDCell identification and/or related FDDCell
parameter definition must be consistent with related FDDCell.
Limitations
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 associated FDD Cells.
If the new neighboring plan comes from a CM XML files, o partial neighboring
plan can be obtained.
The creation and deletion of ode Bs or UMTS cells are out of scope in this
document.
The modification of the scrambling code, or LAC plan are out of the scope in this
document.
o modifications should be done on the Target RCs and their associated MO
(Managed Object) through WMS GUI, WICL from the beginning of the RP (export
XML from Main server, sheet 1) until the end of the procedure.
As 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 the each ROC.
...................................................................................................................................................................................................................................
NN-20500-090
2-4
...................................................................................................................................................................................................................................
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

preparation
ote: That Durations are given for the modification of the neighboring plan for a
network with 7 RCs, 860 BTSEquipment and 2540 Cells.
Neighboring Plan Update preparation under WPS Access
Step
Sheet
Timing
1 (Optional)
Sheet 1 - Peforming Reverse

Engineering
30 minutes
Sheet 2 - Importing a new neighboring

plan Under WPS Access
Few minutes
Sheet 3 - Consistency checks under

WPS Access
Few minutes
4 (Optional)
Sheet 4 - Modifications of the

eighboring Plan under WPS Access
Few minutes
Sheet 3 - Consistency checks under

WPS Access
Few minutes
Sheet 5 - Exporting Workorders
Few minutes

Step
Chapter 5.1
Timing
6 (optional)
< 1 hour
Step
Chapter 5.2
Timing
35 minutes
CM XML Import in WMS

Step
Chapter 5.3
Timing
8 (Optional)
Post-Checks
< 1 hour
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
2-5
PRELIMINARY

preparation
...................................................................................................................................................................................................................................
Impacts
This topic summarizes the impacts on the service given for each step of the Procedure.
Main Steps
Impact on Service
eighboring plan update preparation under WPS Access
one
one
one
one
PM and FM impacts
The Es are managed by the PM system.
PRELIMINARY
The procedure ensures the correct declaration of the Es with respect to FM
management.
...................................................................................................................................................................................................................................
NN-20500-090
2-6
Neighboring Plan Update under WPS Access
...................................................................................................................................................................................................................................

Purpose
This activity aims at defining the provisioning data required for the neighboring plan
update in the live network. This data consists of a XML file that contains:
The modification to be applied on:
PRELIMINARY

preparation
The UMTS neighboring links

The GSM cell
The Outgoing GSM eighboring cells associated with the updates neighboring plan
Optional: the following Objects may be impacted in the XML file provided by the Cell
Planning (for more information please see document referenced [R4]):
BTSCell
Site
AntennaAccess
AntennaSystem
Description
The following figure provides an overview of the steps to follow in order to provide the
OMC team with the relevant data set required to implement the updated neighboring plan:
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
2-7
PRELIMINARY

preparation
...................................................................................................................................................................................................................................
The procedure that follows is derived from the preceding figure, and gathers all the steps
and notes that should be followed to implement an updated neighboring plan.
The steps sequence required to complete the neighboring plan update preparation is:
Step
Sheet
1 (Optional)
Sheet 1 - Performing Reverse Engineering
Sheet 2 - Importing a new eighboring Plan Update under WPS Access
Sheet 3 - Consistency checks under WPS Access
4 (Optional)
Sheet 4 - Modifications of the eighboring Plan under WPS Access

Sheet 3 - Consistency checks under WPS Access
PRELIMINARY
Sheet 5 - Exporting Workorders
As the result of these steps, the Workorder (CM XML) file which contains the updated
neighboring plan information is available.
...................................................................................................................................................................................................................................
NN-20500-090
2-8
...................................................................................................................................................................................................................................
CP XML interface overview
WPS ACCESS provides a specific interface for Cell Planning Tools based on XML
format, named CP XML, and described in the document referenced [R4].
This Specific format allows the user to use different identifiers for the Cell Planning
Objects that the ones defined in CM XML format described in document [R2] and to be
independent from the Topology (RC, ode B).
PRELIMINARY

preparation
In WPS ACCESS, a CP XML import Wizard allows the user to import the CP XML files.
This Wizard provides two options of import depending on the selection of the "Delete
un-impacted neighbouring links" field:
If "Delete un-impacted neighbouring links" is selected (re-build Mode): For all the
FDD Cells defined in the CP XML file, all the related neighboring Cells (UMTS and
GSM) defined in 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
neighboring Cells (UMTS and GSM) 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.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
2-9
PRELIMINARY
PRELIMINARY
PRELIMINARY
3 eighboring Plan Update

N
Procedures
Overview
Purpose
This chapter details the following procedures:

Importing a new eighboring Plan Update under WPS Access - Sheet 2
Consistency checks under WPS Access - Sheet 3
Exporting Workorders - Sheet 5
Contents
3-2
Importing a new eighboring Plan under WPS Access - Sheet 2
3-4
3-9
3-11
3-13
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
3-1
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 uploaded.
Duration
Step duration depends on the number of E available on the network.

See Mean Time chapter for dimensioning info.
Action 1: less than 20 minutes

Action 2: less than 10 minutes
Impact on service
one.
Procedure
...................................................................................................................................................................................................
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).
...................................................................................................................................................................................................
Under WPS ACCESS:
Open a new Workspace. Refer to procedure "Open a workspace" in document [R3] for
details of workspace creation
From the file menu launch the Import and Export wizard:
...................................................................................................................................................................................................................................
NN-20500-090
3-2
...................................................................................................................................................................................................................................
Select "Import Snapshot" (form the Local file system or the Live server repository)
and click Next
Select "Replace initial snapshot and discard existing workorders" and click Next
Click Browse
Select the XML file exported step 1 and Click Open
Click Next
If a part of the snapshot need to be excluded Click Edit Filter?, Choose Objects to
import and Click Next otherwise Click directly Next
Select "o, proceed without saving" and click Start
PRELIMINARY
...................................................................................................................................................................................................
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-090
3-3
PRELIMINARY
Importing a new Neighboring Plan under WPS Access Sheet 2
...................................................................................................................................................................................................................................
Importing a new Neighboring Plan under WPS Access - Sheet 2

Purpose
This step details how to proceed with WPS ACCESS in order to import the updated
neighboring plan.
Depending on the received format of the ew eighboring Plan, this step can be divided
in four actions:
The ew eighboring Plan is provided through a CP XML Snapshot file
The ew eighboring Plan is provided through a file in CM XML format

The ew eighboring Plan is provided through a Workorder, under WPS ACCESS,
in your Workspace
The ew eighboring Plan is provided through a Snapshot, under WPS ACCESS,
in your Workspace
Input parameters
All Design parameters regarding the new neighboring plan need to be provided to the
Application Engineer by the etwork Designers, i.e.
Cell planning information

eighboring information
All these information can be provided through CP XML snapshot file as described in the
Document [R4] or through a CM XML snapshot or workorder file following the CM
XML format described in [R2].
As a consequence the following Object information should be provided in the XML file:
UMTSFDDeighbouringCell
GSMCell if impacted
GSMeighbouringCell if impacted
BTSCell (Optional)
Site (Optional)
AntennaAccess (Optional)
AntennaSystem (optional)
PRELIMINARY
If the ew eighboring Plan is provided through a CP XML file, perform Step 1 only.
ote: If the option "Delete un-impacted neighbouring links" is chosen for CP XML
file import, for impacted FDD Cells the full list of neighbouring cells (GSM and
UMTS) must be provided.
If the ew eighboring Plan is provided through a CM XML file, perform Step 2 only.
...................................................................................................................................................................................................................................
NN-20500-090
3-4
...................................................................................................................................................................................................................................
Initial status
Under WPS ACCESS, a Workspace describing the current configuration of your network
is available. Templates files, RRM tree are uploaded.
Duration
PRELIMINARY
See Mean Time chapter for dimensioning info.

Few minutes
Impact on service
one.
Procedure
...................................................................................................................................................................................................
The ew eighboring Plan is provided through a CP XML Snapshot file

...................................................................................................................................................................................................
Under WPS ACCESS, create a new Workorder and renames it (for example:
"eighboring plan Import") as described in document referenced [R3].
...................................................................................................................................................................................................
Under WPS ACCESS, in your Workspace, from the etwork tree:

1. Select the etwork
2. From the Wizards & Operation area, click Cell Planning Import Wizard
3. In the "Cell Planning Import Wizard", launch the "Import Cell Planning file"
Operation
4. In the "Import Cell Planning file" Operation, click Browse
5. Select the CP XML Snapshot file and click Open
Delete un-impacted neighbouring links

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

E...................................................................................................................................................................................................
N D O F S T E P S
...................................................................................................................................................................................................................................
NN-20500-090
3-5
PRELIMINARY
6. Depending on the Input Parameters (See above):

If in the CP XML Snapshot file the UMTS FDD neighbouring Cells and GSM
eighbouring Cells of the impacted FDD Cells are not defined, DO OT select
the option Delete un-impacted neighbouring links
If in the CP XML Snapshot file All the UMTS FDD neighbouring Cells and GSM
eighbouring Cells of the impacted FDD Cells are defined, SELECT the option
PRELIMINARY
...................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................
The ew eighboring Plan is provided through a file in CM XML format

...................................................................................................................................................................................................
Under WPS ACCESS, create a new Workorder and renames it (for example: "Initial
eighboring plan deletion") as described in document referenced [R3].
...................................................................................................................................................................................................
Under WPS ACCESS, in your Workspace, from the etwork tree:

1. Select All the RCs
2. Right Click, Select "Add to Dataset", Click New Dataset....., enter a dataset name
("All_RCs" for example) and Click OK
3. From the Dataset area, Select the previously created Dataset containing all the RCs
4. In the Dataset Conversion area Select:
Input type: RC (model RC)

avigators: [Generic] Children
Output type: RC/odeB/FDDcell/ UMTSFddeighbouringCell (model RC)
Output Dataset: enter a dataset name ("EI" for example)
Click Apply
Close the report window

5. Select the previously created Dataset containing all the RCs

Output type: RC/GSMeighbour/GsmCell (model RC)
Output Dataset: Select the Dataset previously created (named "EI")
Click Apply
PRELIMINARY

7. Select the previously created Dataset containing all the RCs

Output type: RC/odeB/FDDcell/GsmeighbouringCell (model RC)
Output Dataset: Select the Dataset previously created (named "EI")
Click Apply
...................................................................................................................................................................................................................................
NN-20500-090
3-6
...................................................................................................................................................................................................................................
9. Select the result Dataset containing all the eighboring Cells and GSM Cells
10. Right Click Remove all objects from Networks and Click Yes
E...................................................................................................................................................................................................
N D O F S T E P S
Procedure
PRELIMINARY
...................................................................................................................................................................................................
The ew eighboring Plan is provided through a Workorder, under WPS ACCESS, in
your Workspace
...................................................................................................................................................................................................
Select "Import Workorders" and click Next
Click Browse
Select the XML file and click Open
Click Next
...................................................................................................................................................................................................

E...................................................................................................................................................................................................
N D O F S T E P S
Procedure
...................................................................................................................................................................................................
The ew eighboring Plan is provided through a Snapshot, under WPS ACCESS, in
your Workspace
...................................................................................................................................................................................................
Select "Import Snapshots" and click Next
Select "Merge with Planned etwork" and Click Next

Click Browse
Select the XML file and click Open
Click Next
If a part of the snapshot need to be excluded Click Edit Filter?, Choose Objects to
import and Click Next otherwise Click directly Next
...................................................................................................................................................................................................................................
NN-20500-090
3-7
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
E....................................................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of errors, contact your local Engineering representative and correct errors
manually or require a new input.
Final status
PRELIMINARY
At this step, the new UMTS and GSM neighboring plan is created under the FDD Cells
impacted and all GSM Cells are declared under the host RC(s).
...................................................................................................................................................................................................................................
NN-20500-090
3-8
...................................................................................................................................................................................................................................

Purpose
The procedure details how to checks that the neighboring plan is consistent with all
UMTS and GSM cells declared.
PRELIMINARY
Input parameters
one.
Initial status
A new UMTS and/or GSM, neighboring plan has been imported

Having ode Bs parented to RC with UMTS and/or GSM neighboring plan updated as
GSMCell parented to RC in a Workspace under WPS ACCESS
Duration

See Mean Time chapter for dimensioning info
Few minutes
Impact on service
one.
Procedure
...................................................................................................................................................................................................
Under WPS ACCESS, create a new Workorder and rename it (for example: "consistency
checks") as described in document [R3]
...................................................................................................................................................................................................
From the etwork Object, launch the checker as described in document [R3].
...................................................................................................................................................................................................
In the Checks Window, select a check, right click Disable All

...................................................................................................................................................................................................
In the category "neighbouring", enable the following check "Target Cell Consistency" and
select "Autofix"
EI_UMTS_42
EI_UMTS_43
...................................................................................................................................................................................................................................
NN-20500-090
3-9
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
EI_UMTS_45
EI_UMTS_49
EI_UMTS_51
EI_UMTS_52
EI_UMTS_55
...................................................................................................................................................................................................
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 them.
Final status
At this step, you have a planning view under WPS ACCESS with a neighboring plan up
to date.
PRELIMINARY
The configuration is error free.
...................................................................................................................................................................................................................................
NN-20500-090
3-10
Modifications of the Neighboring Plan under WPS Access Sheet 4
...................................................................................................................................................................................................................................

Purpose
This step details how to manage under WPS ACCESS the neighboring links by using the
basic WPS ACCESS features. Please note that this step applies only for light
modifications of the neighboring links!
PRELIMINARY
Input parameters
From cell planning representative the following information must be available:
The outgoing GSM neighboring links of ode Bs

The GSM Cell relative to the GSM eighboring links created under the RC
The updated UMTS neighboring links
(Optional) The results of the network checker execution, with the objects and
attributes which generated the errors and/or warnings.
Initial status
In a "Workspace" under WPS Access, the neighboring links and GSM cells are up to date.
Duration

Impact on service
one.
Procedure
...................................................................................................................................................................................................
Under WPS ACCESS, create a new Workorder and rename it (for example: "eighboring
plan <plan ame> modification") as described in document [R3]
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
NN-20500-090
3-11
PRELIMINARY
By using the Editor and/or Workorder Inhibition and/or the operations of eighbors
Creation (See document [R3]) and the input data, modify the neighboring links (UMTS
and/or GSM).
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Launch the etwork Checker in order to verify the modification coherency, see Sheet 3
E....................................................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of trouble, delete the Workorder, redo this step.

Final status
PRELIMINARY
At the end of this step the neighboring plan is up to date with desired modifications.
...................................................................................................................................................................................................................................
NN-20500-090
3-12
...................................................................................................................................................................................................................................

Purpose
This procedure details how to generate the Workorder (CM XML) file, which describes
only the modified Es between the initial and the final network configuration.
This procedure enables to speed up the whole process, by importing on the main server
only the relevant modifications to apply.
PRELIMINARY
Input parameters
one.
Initial status
The eighboring plan is up to date in the Workspace 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, Right click workorders folder and
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-090
3-13
PRELIMINARY
...................................................................................................................................................................................................
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Enter a <Filename>, select a <Result_folder> and click Save

ote: If Live Server repository is used perform the following:
1. Select:
HOST
Username and Password (of the server)
2. Browse in the folders and give a name to the file
3. Click OK
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 to apply on the etwork. 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-090
3-14
PRELIMINARY
4
Overview
Purpose
This chapter describes the reconfiguration activation procedures

This chapter is divided in three parts:

Contents
4-2
4-3
4-6
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
4-1
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
This procedure aims at verifying that:
Calls can be achieved on the impacted RC
The new neighboring plan is ready to be activated: Workorder is generated.
This procedure has to be repeated for each impacted RC.

This Procedure is a recommendation and is not mandatory if all the states given by the
checks described above are well known.
Procedure
...................................................................................................................................................................................................
Check that no impacting Alarms exist (See document [R5])

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

...................................................................................................................................................................................................
Perform calls on the impacted RC(s). Especially it can be interesting to pass calls on
Cells impacted by the neighboring plans update.
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-090
4-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 the document referenced [R5].
Initial Status
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 the document referenced [R5].
Duration

Impact on service
one.
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.

Result: The Create Session window appears.
...................................................................................................................................................................................................
In the Create Session window - Creation parameters pane, enter a <Session ame>.
...................................................................................................................................................................................................................................
NN-20500-090
4-3
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
From the Sessions Manager window - session <session name> pane, click Summary
for <session name>.
Result: The Summary for <session name> pane expands.
...................................................................................................................................................................................................
In the Summary for <session name> pane, check:
the Activation Status of the nodes:

RC nodes must be in "validated" state.
the Validation Report of each node:
Select an RC to display its details in the lower part of the pane and click the here
hyperlink to display the full validation report.
Result: The session must be completed without errors.
...................................................................................................................................................................................................
PRELIMINARY
10
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-090
4-4
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
11
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 6 (Reverse Procedure) and activate the reverse Workorder
E...................................................................................................................................................................................................
N D O F S T E P S
PRELIMINARY
Troubleshooting
All commands are logged in the Command Manager (See document [R5])
Failed Step
Node Status
Action
3.5
"Excluded"
In case of errors in session creation analyze logs or

contact your local support or etwork Designers in
order to correct the XML file. Abort the session and
return to step 1.
3.6
"Validation Failed"
In case of errors in session validation, analyze logs or

contact your local support or etwork Designers in
order to correct the XML file, Abort the session and
return to step 1.
4.2
"Activation Partly
realized"
In the Command Manager window check the status of

impacted RCs:
If the Status is "Completed with errors":
Fallback ALL the RC C-odes (See document [R5]):
If the Fallback is completed : Terminate the session and
go to Chapter 6 (Reverse Procedure) to restore the initial
configuration of the other nodes using the reverse
Workorder.
If the Fallback failed: Abort then terminate the session
and go to Chapter 6 (Reverse Procedure) to restore the
initial configuration
Final status
...................................................................................................................................................................................................................................
NN-20500-090
4-5
PRELIMINARY
At the end of this step, the new configuration has been loaded at OMC side and has been
activated into the RC(s).
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
This procedure aims at verifying that:
Calls can be achieved on the impacted RC
The new neighboring plan is OK.
This procedure has to be repeated for each impacted RC.

This Procedure is a recommendation and is not mandatory if all the states given by the
checks described above are well known.
Procedure
...................................................................................................................................................................................................
Check that no impacting Alarms exist (See document [R5])

...................................................................................................................................................................................................
Perform calls on the impacted RC(s). Especially it can be interesting to pass calls on
Cells for which the neighboring plans have been updated.
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.
PRELIMINARY
The new neighboring plan is in service.
...................................................................................................................................................................................................................................
NN-20500-090
4-6
PRELIMINARY
Reverse procedures
5
Overview
Purpose
This chapter describes the reverse procedure.

Pre-Requisites
All the steps of the new neighboring plan procedure have been completed or the
Troubleshooting required going back to the Initial Configuration.
Input Parameters
The Workorder file <Filename>_reverse.xwo mandatory for reverse operation (See

/<Result_folder>) must be available.
The used XML file will be found under this latter folder only.
Duration

Contents
Fallback Workorder Activation for RCs (C-ode Part) in case of Fallback
failure
5-2
5-5
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
5-1
PRELIMINARY
Reverse procedures
Fallback Workorder Activation for RNCs (C-Node Part) in

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

of Fallback failure
Purpose
If the Fallback of all RC C-odes has been successful skipped the steps 1 to 6 described
below.
Go through the following sequences taking into account data coming from
/<Result_folder> folder.
Procedure
...................................................................................................................................................................................................
In WMS and for each RC C-ode named <RC_ame> on which Fallback has failed,
Launch the "Sessions Manager" from the WMS client menu bar
...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
In the Create Session window - Creation parameters pane, enter a <reverse session
name>.
...................................................................................................................................................................................................

cmXML/<Result_folder> folder, select the reverse workorder file
<Filename>_reverse.xwo you want to activate.
...................................................................................................................................................................................................
PRELIMINARY
Click Add to list.

Result: The reverse workorder is added in the right pane.
...................................................................................................................................................................................................
Click Next to display the impacted nodes.
...................................................................................................................................................................................................................................
NN-20500-090
5-2

...................................................................................................................................................................................................................................
Result: The Create Session window - Excluded odes pane appears and details, for
each impacted node, activation details and impacted objects.

...................................................................................................................................................................................................
Click Launch.
PRELIMINARY
Reverse procedures
...................................................................................................................................................................................................
In the "Sessions Manager" window, Click Summary for <session name for RNC> and
check the Activation Status of the nodes: RC should be in "Validated" state.
Change by right clicking the activation type to CRITICAL
...................................................................................................................................................................................................
10
In the "Sessions Manager" window, In the "Actions for <session name for RC> tab click
Activation
Select all the impacted RCs and click Launch
When all tasks are completed, in the "Sessions Manager" window Click Summary for
<session name for RNC> to check that all nodes are activated
...................................................................................................................................................................................................
11
From the "Sessions Manager" window, in the Session List Right click <session name for
RNC> and in scroll down menu select Terminate in order to delete the session
E...................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
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 then terminate the session
and return to step 1
"Validation Failed"

contact your local support or etwork Designers in order
to correct the XML file, Abort then terminate the session
and return to step 1
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
5-3
PRELIMINARY
Reverse procedures

...................................................................................................................................................................................................................................
Failed step
Node status
Action
"Activation Partly
realized"
In the Command Manager window check the status of

impacted RC C-ode:
In case of Build failure (the Status is "Stopped with
errors"), analyze the logs or contact your local support or
etwork Designers in order to correct the problem (i.e.
problem of XML file, transmission cut while building).
Once the problem identified and corrected, return to step
5
Final Status
PRELIMINARY
The neighboring plan is back to the initial configuration.
...................................................................................................................................................................................................................................
NN-20500-090
5-4
...................................................................................................................................................................................................................................

Purpose
Go through the following sequences by taking into account data coming from
/Result-Rev:
PRELIMINARY
Reverse procedures
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................

...................................................................................................................................................................................................
In the Create Session window - Creation parameters pane, enter a <reverse session
name>.
...................................................................................................................................................................................................

cmXML/<Result_folder> folder, select the reverse workorder file
<Filename>_reverse.xwo you want to activate.
...................................................................................................................................................................................................
Click Add to list.

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.
...................................................................................................................................................................................................................................
NN-20500-090
5-5
PRELIMINARY
PRELIMINARY
Reverse procedures
...................................................................................................................................................................................................................................

...................................................................................................................................................................................................
From the Sessions Manager window - Session <reverse session name> pane, click
Summary for <reverse session name> and check the Activation Status of the nodes.
Result: RC nodes must be in "valided" state.
...................................................................................................................................................................................................
Select an RC in the table and click on the Validate report hyperlink to display the
HTML validation report.
Result: Check the validation report of each node in the summary section.
...................................................................................................................................................................................................
10
After session creation completion without errors, in the "Actions for <reverse 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 on "Summary
for <reverse session name> to check that all nodes are activated
...................................................................................................................................................................................................
11
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
E....................................................................................................................................................................................................................................
N D O F S T E P S
PRELIMINARY
Troubleshooting
Failed Step
Node status
Action
3.5
"Excluded"
In case of errors in session creation, analyze logs or contact

your local support or etwork Designers in order to correct
the XML file, Abort then terminate the session and return to
step 1.
3.6
"Validation
Failed"

contact your local support or etwork Designers in order to
correct the XML file, Abort then terminate the session and
return to step 1.
...................................................................................................................................................................................................................................
NN-20500-090
5-6
...................................................................................................................................................................................................................................
Failed Step
Node status
Action
4.2
"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) (refer to [R5])
PRELIMINARY
Reverse procedures
Final Status
The neighboring plan is back to the initial configuration.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-090
5-7
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
AN
Access ode
PRELIMINARY
Glossary
...................................................................................................................................................................................................................................
CM
Configuration Management
...................................................................................................................................................................................................................................
EM
Equipment Monitor
...................................................................................................................................................................................................................................
FM
Fault Management
...................................................................................................................................................................................................................................
GUI
Graphic User Interface

...................................................................................................................................................................................................................................
IN
Interface ode
Itf-B
Interface between the ode B and its Element Manager

Itf-R
Itf-R
...................................................................................................................................................................................................................................
MO
...................................................................................................................................................................................................................................
PM
Performance Management
...................................................................................................................................................................................................................................
NN-20500-090
GL-1
PRELIMINARY
Managed Object
PRELIMINARY
Glossary
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................................................
ROC
Regional Operational Center

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

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

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-090 (9300 W-CDMA Product Family - Neighboring Plan Update NRP) 11

Uploaded by

Copyright:

Available Formats

Proprietary Use pursuant to Company instruction

Proprietary Use pursuant to Company instruction

About this document

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

Supported systems ........................................................................................................................................................................ vi

Conventions used .......................................................................................................................................................................... vi

Roadmap to Configuration Management documentation

Neighboring Plan Update Overview and procedure preparation

eighboring Plan Update under WPS Access ................................................................................................................. 2-7

eighboring plan update

Neighboring Plan Update Procedures

Importing a new eighboring Plan under WPS Access - Sheet 2

Consistency checks under WPS Access - Sheet 3 .......................................................................................................... 3-9

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

Reconfiguration Activation Post-Checks

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:

About this document

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

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,

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

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

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

Roadmap to Configuration Management documentation

Roadmap to Configuration Management documentation

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

2 eighboring Plan Update

eighboring Plan Update under WPS Access

Neighboring Plan Update Overview and procedure

Neighboring plan update

Neighboring plan update

The UMTS neighboring links created, updated or deleted

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

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

The priority defined per neighboring cell

The parameters are:

Neighboring Plan Update Overview and procedure

XML file provided by the Cell Planning

Neighbouring Plan Update

The Neighbouring Plan is up to date

Neighboring Plan Update Overview and procedure

There must be a unique definition of GSMCell within the etwork

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

Neighboring Plan Update Overview and procedure

Sheet 1 - Peforming Reverse

Sheet 2 - Importing a new neighboring

Sheet 3 - Consistency checks under

Sheet 4 - Modifications of the

Sheet 3 - Consistency checks under

Sheet 5 - Exporting Workorders

Reconfiguration Activation Pre-Checks

Reconfiguration Activation Pre-Checks