NN-20500-088 (9300 W-CDMA Product Family - Node B Reparenting NRP) 12

Proprietary Use pursuant to Company instruction
PRELIMINARY
Title page
W-CDMA
Alcatel-Lucent 9300 W-CDMA Product Family | V7.1
Intra-Roc Node B reparenting (NRP)
NN-20500-088
ISSUE 12.03
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
Document support
...................................................................................................................................................................... xii
xii
Technical support
....................................................................................................................................................................... xii
xii
How to order
................................................................................................................................................................................. xii
xii
How to comment
1
..................................................................................................................................................................... xi
xi
......................................................................................................................................................................... xii
xii
Roadmap to Configuration Management documentation

Overview ....................................................................................................................................................................................... 1-1
1-1
........................................................................................... 1-2
Node B reparenting overview

Overview ....................................................................................................................................................................................... 2-1
2-1
................................................................................................................................................................... 2-2
2-2
Procedure description
Overview ....................................................................................................................................................................................... 3-1
3-1
...................................................................................................................................................................................................................................
NN-20500-088
iii
Issue 12.03 November 2009
PRELIMINARY
ode B reparenting
PRELIMINARY
Contents
...................................................................................................................................................................................................................................
............................................................................................................................................................... 3-2
3-2
Intra-ROC ode B reparenting restriction
....................................................................................................................... 3-4
Mean time (TBC) ....................................................................................................................................................................... 3-5

3-5
Impacts ........................................................................................................................................................................................... 3-6
3-6
Limitations
................................................................................................................................................................................... 3-7
3-7
Prerequisites ................................................................................................................................................................................. 3-8

3-8
4
NodeB reparenting preparation under WPS

Overview ....................................................................................................................................................................................... 4-1
4-1
Description
................................................................................................................................................................................... 4-2
4-2
Sheet 1 - Reverse Engineering

Sheet 2a - iBTS Reparenting
.............................................................................................................................................. 4-4
4-4
................................................................................................................................................. 4-6
4-6
Sheet 2b - OneBTS (ATM) Reparenting ......................................................................................................................... 4-10

Sheet 2c - OneBTS (IP) Reparenting
Sheet 3 - odeB Update
.............................................................................................................................. 4-13
....................................................................................................................................................... 4-16
4-16
Optional Sheet 4 : eighboring Plan Update

Sheet 6 - Consistency Checks
................................................................................................................ 4-18
............................................................................................................................................. 4-19
4-19
Sheet 7 - Export workorders ................................................................................................................................................ 4-20

4-20
5
Installation and commissioning

Overview ....................................................................................................................................................................................... 5-1
5-1
Performing checks before reparenting
Change I&C parameters
............................................................................................................................... 5-2
.......................................................................................................................................................... 5-3
5-3
On Site activities for transmission network update
PRELIMINARY
Reconfiguration activation in WMS

odeB verification
....................................................................................................... 5-4
................................................................................................................................... 5-5
5-5
.................................................................................................................................................................. 5-11
5-11
Performing checks after reparenting
................................................................................................................................ 5-12
...................................................................................................................................................................................................................................
NN-20500-088
iv
...................................................................................................................................................................................................................................
Reverse operation
Overview ....................................................................................................................................................................................... 6-1
6-1
Reverse operation
...................................................................................................................................................................... 6-2
6-2
PM and FM impacts
PRELIMINARY
Contents
Impacts ........................................................................................................................................................................................... 7-1

7-1
Glossary
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
v
PRELIMINARY
PRELIMINARY
2-1
General description for an iBTS
.......................................................................................................................... 2-2
2-2
General description for a OneBTS
3-1
ode B reparenting
...................................................................................................................... 2-3
PRELIMINARY
List of figures
.................................................................................................................................................. 3-3
3-3
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
vii
PRELIMINARY
PRELIMINARY
PRELIMINARY
About this document

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

(RP) applicable for ode B reparenting under the same ROC in the UMTS network,
without interruption of service on the existing RC.
Reason for revision
The reissue reasons are:

Issue number
Issue date
Reason for reissue
12.03
ovember 2009
Updated after internal review.
12.02
ovember 2009
Preliminary issue
12.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-088
ix
PRELIMINARY
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:
odeB
RC
WMS
WPS
The following topics are out of the scope of this document:
Transmission backbone (IuB, ItF-R, ItF-B)

Core etwork activity
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:
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)
Alcatel-Lucent odeB UA6.x DHCP Activation, IM 30-6239
Alcatel-Lucent OneBTS UA6.x DHCP Activation, IM 30-6232
Vocabulary conventions
one.
PRELIMINARY
Conventions used
one.
...................................................................................................................................................................................................................................
NN-20500-088
...................................................................................................................................................................................................................................
Related information
ode B Capacity Licensing
[R2] Installation
Method 30-9196
UMTS BTS Integration in an Exiting UTRA
[R3]
-20500-036
Alcatel-Lucent 9352 Provisioning System - User Guide
[R4]
-20500-090
eighboring Plan Update
[R5]
-20500-032
Alcatel-Lucent 9353 Management System - User Guide
[R6] Installation
Method 24-9356
UMTS iBTS commissioning Procedure
[R7]
UMT/OMC/DD/
007615
CM XML format Description
[R8]
-20500-002
Product Family - Terminology
[R9]
-20500-031
Alcatel-Lucent 9353 Management System - System Overview
[R10]
UMT/SYS/DD/
0089
UMTS Drop & Insert via IBTS with fractional ATM over single E1
[R11]
-20500-033
Alcatel-Lucent 9300 W-CDMA Product Family - Performance Management
[R12]
-20500-057
Alcatel-Lucent 9313 Micro ode B and 9314 Pico ode B - Local

Maintenance Tool Manual
[R13]
-20500-058
Alcatel-Lucent 9313 Micro ode B and 9314 Pico ode B - Operation and
Maintenance Manual
[R14]
-20500-049
Intra-ROC E Rehoming
[R15]
Alcatel-Lucent odeB UA7.x DHCP Activation
IM 30-6239
[R16]
Alcatel-Lucent OneBTS UA7.x DHCP Activation
IM 30-6232
...................................................................................................................................................................................................................................
NN-20500-088
xi
PRELIMINARY
[R1]
-20500-154
PRELIMINARY
About this document
PRELIMINARY
About this document

...................................................................................................................................................................................................................................
[R17]
9300 W-CDMA Product Family - Activation of ative IP IuB
-20500-261
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
PRELIMINARY
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) .
...................................................................................................................................................................................................................................
NN-20500-088
xii
PRELIMINARY
1oadmap to Configuration
R
Management
documentation
Overview
Purpose
This chapter provides the roadmap for Configuration Management documentation.

Contents
1-2
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
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-088
1-2
PRELIMINARY
2 ode B reparenting
N
overview
Overview
Purpose
The odeB reparenting procedure aims at reparenting active odeB(s) from the
"Source" RC to the "Target" RC.
Contents
ode B reparenting
2-2
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
2-1
PRELIMINARY
Node B reparenting
...................................................................................................................................................................................................................................
Node B reparenting
Overview diagrams for iBTS and OneBTS
as displayed in the diagram below:

Figure 2-1 General description for an iBTS
Source
RNC
Optical
RNC
ATM/OC3 or STM1
CN
Source
RNC
IN
WPS
XML
IBTS
ATM/E1
or T1
Inter RNC
Reparenting
IuB
Backbone
Itf-R/Itf-B
WMS
Target
RNC
IP
CN
ATM/OC3 or STM1
PRELIMINARY
IP Backbone
IN
IP
...................................................................................................................................................................................................................................
NN-20500-088
2-2
Node B reparenting
...................................................................................................................................................................................................................................
Figure 2-2 General description for a OneBTS

Itf-B
Source
RNC
Optical
RNC
ATM/OC3 or STM1
CN
Source
RNC
IN
PRELIMINARY
WPS
XML
OneBTS
ATM/E1
or T1
DCHP Relay
Function
IuB
Backbone
Inter RNC
Reparenting
Itf-R
WMS
Target
RNC
IP
CN
ATM/OC3 or STM1
IP Backbone
IN
IP
Definitions
Itf-B
Interface between the odeB and its Element Manager
Itf-R
Interface between the RC and its Element Manager
For more information refer to [R8].

Procedure overview
The following Es are involved in this procedure:
The reparented odeB(s)

The source RC I-ode, source RC C-ode
The target RC I-ode, target RC C-ode
This procedure applies when both Source and Target RCs are managed by the same
ROC
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
2-3
PRELIMINARY
PRELIMINARY
Node B reparenting
...................................................................................................................................................................................................................................
ote: For details relating to DHCP activation, refer to one of the folowing
documents:
For a odeB use document [R15], Alcatel-Lucent odeB UA7.x DHCP

Activation, IM 30-6239
For a OneBTS use document [R16], Alcatel-Lucent OneBTS UA7.x DHCP
...................................................................................................................................................................................................................................
NN-20500-088
2-4
PRELIMINARY
3
Overview
Purpose
This chapter describes the procedure.

Contents
3-2
Intra-ROC ode B reparenting restriction
3-4
Mean time (TBC)
3-5
Impacts
3-6
Limitations
3-7
Prerequisites
3-8
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
3-1
PRELIMINARY
...................................................................................................................................................................................................................................
Main steps
The following diagram displays the different steps to be conducted in order to complete
the odeB(s) reparenting.
The preparation under WPS is offline. It can be made anytime before WMS and etwork
related Online actions.
ote:
PRELIMINARY
This procedure is not applicable for Micro/Pico ATM odeB.
...................................................................................................................................................................................................................................
NN-20500-088
3-2
...................................................................................................................................................................................................................................
Figure 3-1 Node B reparenting
PRELIMINARY
For the main steps of this procedure, reverse operations are presented at the end of the
document.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
3-3
PRELIMINARY
Intra-ROC Node B reparenting restriction
...................................................................................................................................................................................................................................
Intra-ROC Node B reparenting restriction

Restriction
Important! In case of the reparenting is applicable to a iBTS or a OneBTS.

And if the Source and the Target RCs are not managed by the same Main Server of
the ROC.
PRELIMINARY
Then, see chapter Prerequisites of this document to check all the conditions where this
document applies.
...................................................................................................................................................................................................................................
NN-20500-088
3-4
Mean time (TBC)
...................................................................................................................................................................................................................................
Mean time (TBC)

Purpose
This topic 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 network, transmission network performance, etc.) and
then might significantly vary from a configuration to another, the times given in this
chapter are only for information and planning purpose.
PRELIMINARY
ote: ote that durations are given for the reparenting of 1 odeB in a etwork
containing 7 RCs and 860 odeBs.
Step times
odeB reparenting preparation under WPS
Step
Sheet
Timing
1 (Optional)
30 minutes
2 (For each
odeB)
Sheet 2a - odeB Reparenting
2 minutes
Sheet 2b - OneBTS (ATM) Reparenting
3 minutes
3 minutes
(Optional) Sheet 3 - odeB Update
5 minutes
(Optional) iBTS and OneBTS with associated

Site if any ? OAM Intra-ROC rehoming
See document
referenced in [R14]
3 (Optional)
Sheet 4 - eighboring plan update
<10 minutes
Sheet 6- Consistency Checks
<5 minutes
Sheet 7 - Export workorders
<1 minute
Reconfiguration Activation Pre-Checks

Step
Chapter
Timing
6(Optional)
<1hour
Reconfiguration Activation in WMS

Step
Chapter
Timing
<10 minutes
Depend on test
strategy
<10 minutes
On site activities for transmission etwork update
Depend on
Transmission etwork
...................................................................................................................................................................................................................................
NN-20500-088
3-5
PRELIMINARY
odeB Verification
PRELIMINARY
PRELIMINARY
Impacts
...................................................................................................................................................................................................................................
Impacts
Purpose
This topic summarizes the impacts on the service given for each step of the Procedure.
Main Steps
Impacts on service
odeB reparenting preparation under WPS
one
Supervision Outage and possible Telecom

outage.
On site activities for transmission etwork update
Telecom outage
one
Telecom outage
odeB Verification
Depend on test strategy
...................................................................................................................................................................................................................................
NN-20500-088
3-6
Limitations
...................................................................................................................................................................................................................................
Limitations
Purpose
o intra RC reparenting is supported by the current procedure.

o inter ROC reparenting is supported by the current procedure.
This procedure does not cover the GSM etwork Elements impact.
Manufacturer parameter setting is out of scope in the procedure. As Manufacturer

parameters can be different on the target RC than on the source one, contact your
local engineering in order to set them accordingly.
The procedure focuses on UTRA Es: RC and odeB. Core etwork
reconfiguration is out of the scope in this document.
Iso DHCP configuration.
Frequencies used are not modified.
eighboring cell managed by other ROC is out of the scope in this document.
PRELIMINARY
o modifications should be done on the source, Target, RCs and their associated
MO (Managed Object) through WMS GUI, WICL from the beginning of the RP
(export CM XML file from main server, sheet 1) until the end of the procedure.
The partial reverse is not supported. The reverse is made for all the odeB(s). Due
to this limitation it is recommended to choose , the number of odeBs as small as
possible.
Remarks relating to National Roaming Management:
Be careful to avoid any Cell Reparenting (which is defined as a neighboring cell of an

access network of a second operator) to a target RC belonging to the same operator with
a PLMID different from the one of the source RC: this destination RC could belong
to a shared coverage areas that will forbid access to this cell for the second operator.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
3-7
PRELIMINARY
...................................................................................................................................................................................................................................
Prerequisites
Purpose
The odeB reparenting RP described in this document applies if all the following
conditions are verified:
PRELIMINARY
Prerequisites
The etwork and the OMC are up and running without any problem. (Alarm, OMC
MIB State, Synchronization State, etc.).
The ItF-R interface between WMS and the source and target RCs are up and
running.
The same WMS Main Server hosts the source and target RCs
The Itf-B interface:
For the iBTS: The Itf-B interface between WMS and the odeB is implemented
via the RC Iode in both source and target configurations for all involved
odeB(s). See the corresponding picture in chapter General description.
For the OneBTS: The Itf interface links the WMS to the IuB Backbone. See
corresponding picture in chapter General description.
The source and target RCs share the same system version.
Intra-ROC Inter-MainServer(Cluster) odeB reparenting: in the ROC if the
Source and the Target RC are not homed by the same MainServer (ClusterId
are not the Same), prior to the execution of the RP the related BTS Equipment
and its associated Site (if exists) must have been re-homed from the source
RC's MainServer(Cluster1) to the Target RC's MainServer(Cluster2). See
document [R14].
BTS Equipment software version is not modified.
The LAC, RAC, SAC of the odeB(s) must be well declared at Core etwork side.
In case of reparenting of a BTS1 in Drop & Insert (initially configured in Drop &
Insert or not) as dropped or dropping of another BTS2 which already exist on the
Target RC, the BTS2 on the target RC must be already configured in Drop &
Insert (See document [R3]).
...................................................................................................................................................................................................................................
NN-20500-088
3-8
PRELIMINARY
4 odeB reparenting
N
preparation under WPS
Overview
Purpose
This chapter defines the data provisioning required to reparent the odeB(s) in the live
network
The resultant data consists of a Workorder (CM XML) file that contains:
The new configuration to be activated on the reparented odeB(s)

The modifications to be applied on the following objects:
The RC C-odes and RC I-odes source and target
Contents
Description
4-2
4-4
4-6
4-10
4-13
Sheet 3 - odeB Update
4-16
Optional Sheet 4 : eighboring Plan Update
4-18
4-19
4-20
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
4-1
PRELIMINARY
Description
...................................................................................................................................................................................................................................
Description
Purpose
The following figure presents an overview of the algorithm to be applied in order to

provide the OMC team with the relevant data set required to reparent odeB(s).
The procedure that follows is derived from the preceding figure, and gathers all the main
steps and notes, which need to be followed to reparent a odeB.
The main steps to complete the odeB reparenting datafill preparation are:
Step
Sheet
1 (Optional)
OMC Snapshot import
PRELIMINARY

2 (for each odeB)
Sheet 2a - odeB Reparenting

Sheet 2b - OneBTS (ATM)Reparenting
(Optional) Sheet 3 - odeB Update
3 (Optional)
Sheet 4 - eighboring Plan Update
...................................................................................................................................................................................................................................
NN-20500-088
4-2
Description
...................................................................................................................................................................................................................................
Step
Sheet
The result of these main steps is that a Workorder (CM XML) file, which describes the
odeB(s) to reparent, is available.
PRELIMINARY
Additional steps
In addition to the reparenting steps performed in step 2 above using the IuB wizard, the
following updates may be required
If DCHP is to be updated, new subnets may be required on the target RC.

OneBTS backplane may require updating if new Vlan Ids have been used for the
transport network to connect to the target RC.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
4-3
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
This topic ensures that an up-to-date view of the current network configuration is
available.
Presentation
This step details how to proceed with WPS and the main server to import a view of the
current network configuration into WPS if the WPS view is not up-to-date.
This step is recommended when a problem has occurred. You can bypass it if you are sure
that your WPS 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 and WMS are installed and ready to be used. The template files are uploaded.
Step Duration
Step duration depends on the number of E available on the network. Example: for a
network with 7 RC, 860 BTSEquipments and 2540 Cells, durations are the following:
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 PC directory).
...................................................................................................................................................................................................................................
NN-20500-088
4-4
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Under WPS:
Open a new Workspace. Refer to the procedure "Creating a new workspace" in

document [R3] for details of workspace creation
From the file menu launch Import and Export...
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 procedure.

Final Status
At this step, you have a Workspace with an Initial Snapshot describing your current
network.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
4-5
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
This activity provides the steps to reparent an iBTS from a source RC to a target RC,
from WPS perspective.
During this reparenting procedure, two features are configured:
Alcap
This feature tracks the implementation of Alcap for the management of the AAL2
connections on the Iub interface (as specified by 3GPP) instead of the partially
proprietary solution.
Hybrid Iub
This feature introduces support for a hybrid transport (IP & ATM) Iub interface
through a software upgrade and the addition of two (1+1) 4ptGigE Cards on the RC.
Both features can be activated through the Iub wizard. For more information, see
document [R3] - "Iub Creation".
To parent a new OneBTS, see sheet 2b or 2c- OneBTS Reparenting.
Input parameters
All design parameters regarding the iBTS need to be provided to the Application
Engineer by the etwork Designers. The design parameters required are:
Cell planning information

Topological information
Relevant parameters values written in WPS templates
ote: For any questions concerning the odeB DHCP activation or configuration,
refer to the documents [R15]:
Alcatel-Lucent odeB UA07.x DHCP Activation, IM 30-6239
Both features can be activated through the Iub wizard. For more information, see
document [R3] - "Iub Creation".
To parent a new OneBTS, see sheet 2b or 2c- OneBTS Reparenting.
PRELIMINARY
Initial status
Under WPS, a Workspace describing the current configuration of your network is

available. Templates files and RRM tree are imported.
A odeB is parented to a source RC and a target RC is available.
Step Duration
2 minutes for 1 odeB

...................................................................................................................................................................................................................................
NN-20500-088
4-6
...................................................................................................................................................................................................................................
Impact on service
one
Procedure
...................................................................................................................................................................................................
Under WPS, create a new Workorder (if needed) and rename it (for example: "odeB
<odeB reparenting>") as described in document [R3].
PRELIMINARY
...................................................................................................................................................................................................
In the etwork Tree, select the odeB and launch IuB Wizard
...................................................................................................................................................................................................
In the IuB Wizard:
Delete the Iub:

In the "odeB parenting" task, launch Delete Iub Operation
Select only the option "Delete Atm Switching at RC Optical level" and unselect
the others available option
Parent the odeB to a new RC:

In the "odeB parenting" task, launch the "Parent odeB to a RC" Operation
Select the target RC
If required change the odeB.IubIf
Click OK
Click OK
Go through all tasks and fulfill all requested information as described in document
[R3] - "Iub Creation".
...................................................................................................................................................................................................
Configure the Alcap link: once the Iub wizard is launched, select Streams Definition and
click Add streams
...................................................................................................................................................................................................
Check that the Number of Alcap streams to be added is set to 1

...................................................................................................................................................................................................
Fill in the following stream parameters if required:

umber of AAL2 streams
ATM rules
...................................................................................................................................................................................................................................
NN-20500-088
4-7
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Fulfill with the correct value then click OK:
Aggregation point of OAM stream
BTS sap A2EA
...................................................................................................................................................................................................
Select Streams definition and click Configure OAM & Cplane & Alcap streams
...................................................................................................................................................................................................
A window opens, select the correct value for both parameters Qaal2Params and
SscopParms
...................................................................................................................................................................................................
10
Click OK
...................................................................................................................................................................................................
11
From the Iub wizard tree, select BTS ATM configuration, click Configure ATM switching
...................................................................................................................................................................................................
12
For the object AlcapBearer/0 fill in the values of the Vp, Vc, ServiceCategory and
holdingPriority and choose the correct template in Vcc template
...................................................................................................................................................................................................
13
Click OK
...................................................................................................................................................................................................
14
From the Iub wizard, select Switching configuration then click Configure Iub ATM
switching
...................................................................................................................................................................................................
15
Fill in all the parameters

...................................................................................................................................................................................................
16
Click OK
...................................................................................................................................................................................................
17
In the network tree, select the BTSEquipment linked to the new nodeB.
PRELIMINARY
...................................................................................................................................................................................................
18
In the Object window, select the Edition tab.

...................................................................................................................................................................................................
19
Check that the parameter AlcapActivation is set to true.
...................................................................................................................................................................................................................................
NN-20500-088
4-8
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
20
If you want to configure an hybrid Iub interface:
The Ethernet cable must be connected to the lower level of the plug.
The TIL or the site LA must be connected to the upper level of the plug.
1. Select the odeB and launch Iub wizard.
2. Select odeB parenting and click Reconfigure IUB Transport Type
PRELIMINARY
3. Fill in Transport type with atm+ip

4. Click OK
5. In the network tree, select BTSEquipment and click IpRan
6. In the Object BTSEquipment part, select the Edition mode
7. Fill in with the right value, both parameters:
ipRanodeBaddress
ipRanSubnetMask
8. Click Set to record the new value of each parameter
E...................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of trouble, delete the Workorder and redo this procedure.

Final Status
At this step, you have a Workorder containing the scenario to reparent an iBTS.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
4-9
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
The procedure details how to parent an ATM OneBTS to an existing RC with WPS.
This feature can be activated through the Iub wizard. For more information, see document
[R3] Alcatel-Lucent 9352 Provisioning System - User Guide, -20500-036.
In this case the OneBTS bears only ATM protocol. So no IP link is available on this
equipment. OneBTS requires specific templates.
Input parameters
All Design parameters regarding the odeB need to be provided to the Application
Engineer by the etwork Designers. These design parameters are the following:


ote: For any questions concerning the OneBTS DHCP activation or configuration,
Initial status

Step Duration
The step duration to parent 1 OneBTS is 3 minutes.

Impact on service
one
Procedure
PRELIMINARY
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................................................
NN-20500-088
4-10
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the IuB Wizard:
Delete the Iub:

1. In the "odeB parenting" task, launch Delete Iub Operation
2. Select only the option Delete Atm Switching at RNC Optical level and unselect
the others available option
3. Click OK
PRELIMINARY
...................................................................................................................................................................................................
In the etwork Tree, Select the odeB and click Iub wizard
...................................................................................................................................................................................................
Select odeB parenting and click Parent NodeB to a RNC

...................................................................................................................................................................................................
Fill in with the correct values, select the right target RC, Transport Type must be ATM
and click OK
...................................................................................................................................................................................................
Verify:
The OneBTS is located under the target RC

If needed, check that Aggregation Point Definition is correctly defined
...................................................................................................................................................................................................
In the Iub wizard tree, select Streams definition and click Add streams
...................................................................................................................................................................................................
Fill in with the correct values. Set ATM Rules and Click OK
...................................................................................................................................................................................................
10
In the Iub wizard tree, select Streams definition and click Configure OAM & CPlane &
Alcap Streams
...................................................................................................................................................................................................
11
Fill in with the correct values. Set ATM Rules and Click OK
...................................................................................................................................................................................................
12
verify that the following objects are well defined:

OneBTS Physical resource Configuration
OneBTS ATM Configuration
...................................................................................................................................................................................................
13
In the Iub wizard, select Interface ode Configuration and click Switching configuration
...................................................................................................................................................................................................................................
NN-20500-088
4-11
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
14
Click Configure Iub ATM switching

...................................................................................................................................................................................................
15
Set ATM Rules, set all Vcc Template with the correct templates and Click OK
E....................................................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of trouble, delete the Workorder and redo this procedue.

Final Status
PRELIMINARY
At this step, you have a Workorder containing the scenario to reparent a OneBTS.
...................................................................................................................................................................................................................................
NN-20500-088
4-12
...................................................................................................................................................................................................................................

Purpose
The procedure details how to parent an IP OneBTS to an existing RC with WPS.
This feature can be activated through the Iub wizard. For more information, see document
[R3] Alcatel-Lucent 9352 Provisioning System - User Guide, -20500-036
PRELIMINARY
In this case OneBTS bears IP protocol.

Input parameters
All Design parameters regarding the odeB need to be provided to the Application
Engineer by the etwork Designers. These design parameters are the following:


IuB user rules file installed under \Program Files\9352 WPS\<version>\user.
ote: For any questions concerning the OneBTS DHCP activation or configuration,
Initial status

WiPS checks for OneBTS and source and target RC did not show unexpected
consistency check errors.
If this is the first OneBTS to be connected via IP under the target RC, check if the 4pGe
cards are already created. Otherwise run WO #1 from Chapter 4 in 9300 W-CDMA
Product Family - Activation of ative IP IuB, -20500-261s
Step Duration
The step duration to parent 1 OneBTS is 3 minutes.
one
...................................................................................................................................................................................................................................
NN-20500-088
4-13
PRELIMINARY
Impact on service
PRELIMINARY
...................................................................................................................................................................................................................................
Procedure
...................................................................................................................................................................................................
...................................................................................................................................................................................................
...................................................................................................................................................................................................
In the IuB Wizard:
Delete the Iub:

1. In the "odeB parenting" task, launch Delete Iub Operation
2. Select the following options:
Delete IuB at BTS level
Delete IuB at RNC level
Deparent NodeB
Delete incoming Neighbours
3. Click OK
...................................................................................................................................................................................................
In the etwork Tree, Select the odeB and click Iub wizard
...................................................................................................................................................................................................
Select odeB parenting and click Parent NodeB to a RNC

...................................................................................................................................................................................................
Fill in with the correct values, select the right target RC, Transport Type must be IP and
click OK
...................................................................................................................................................................................................
Verify that the OneBTS is located under the target RC.

...................................................................................................................................................................................................
In the Iub wizard tree, select Streams definition and click Add Cplane streams
...................................................................................................................................................................................................
PRELIMINARY
Run Configure Cplane streams, fill in the correct values and click OK.
...................................................................................................................................................................................................
10
In the Iub wizard tree, select Streams definition and click Add Uplane streams
umber of Uplane streams to be added = 4 for QoS 3,2,1,0.
...................................................................................................................................................................................................................................
NN-20500-088
4-14
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
11
Run Configure Uplane streams, fill in correct values and Click OK.
...................................................................................................................................................................................................
12
In the IuB wizard refer to the following :
OneBTSEquipment IP Configuration
External RC IuB IP Configuration
PRELIMINARY
Check if the attributes to be configured via these tasks require updating and update
accordingly:
odeB telecom subnet IP address / subnet mask / VLA Id

Routing table
PTP odeB subnet IP address / subnet mask / VLA Id
...................................................................................................................................................................................................
13
Re-create the eighbour Relations which have been removed during step 3 above Delete
IuB.
To synchronise the re-creation of eighbour Relations to a new eighboring plan, see
Optional Sheet 4 : eighboring Plan Update (p. 4-18).
...................................................................................................................................................................................................
14
Run WPS checks for OneBTS, source and target RC and fix any consistency check
errors related to OneBTS re-parenting operation.
E...................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of trouble, delete the Workorder and redo this procedure.

Final Status
At this step, you have a Workorder containing the scenario to reparent a OneBTS.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
4-15
PRELIMINARY
Sheet 3 - NodeB Update
...................................................................................................................................................................................................................................

Purpose
This activity aims at updating odeB configuration if some configuration parameters

need to be modified (FddCellId, Lac, Rac, Sac, RRM references, etc.).
If not required, this step can be skipped.
Input parameters
All Design parameters regarding the reparented odeB such as:
Fdd Cell Id (unique id per RC)
Lac, Rac, Sac.

RRM references
Initial status
WPS is installed and ready to be used. Templates files and RRM tree are imported.
Under WPS, a Workspace with the reparented odeB(s) is available.
Step Duration
This step lasts 5 minutes for 1 odeB.

Impact on service
one
Procedure
...................................................................................................................................................................................................
Under WPS, create a new Workorder and rename it (for example: "odeB <odeB
name> update") as described in document [R3].
...................................................................................................................................................................................................
PRELIMINARY
Under WPS, in the etwork Tree, select the reparented odeB under the Target RC and
launch the odeB Wizard. Go through the Wizard and update the parameters as specified
into document [R3], chapter "odeB/BTSEquipment creation".
For RRM references update:

In "odeB Configuration" task launch the Operation "Links Setting":
For each FDDCell Set the attributes by selecting the relevant class given in Input.
...................................................................................................................................................................................................................................
NN-20500-088
4-16
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
Update of the relatedFDDCell attribute of the incoming UMTS FDD eighboring Cells:
In the etwork Tree, Select the etwork
Launch the Checks (See document [R3])

Select a Check and Right Click Disable All
In the category "eighboring", enable the check "Target Cell Consistency" Id

EI_UMTS_51 and EI_UMTS_55, and select "Autofix" and Click OK
Click Re-run check session and Check that no more error appears on the incoming
UMTS FDD eighboring Cells.
PRELIMINARY
...................................................................................................................................................................................................
If the LAC and/or RAC of the FDDCell have been changed: Update of the LAC and/or
RAC attributes of the incoming UMTS FDD eighboring Cells:
In the etwork Tree, Select the etwork

Launch the Checks (See document [R3])
Select a Check and Right click Disable All
In the category "eighboring", enable the checks "Target Cell Consistency" Id

EI_UMTS_51 and EI_UMTS_55, and select "Autofix" and Click OK.
Click Re-run check session and Check that no more error appear on the incoming
UMTS FDD eighboring Cells.
E...................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of trouble, delete the Workorder and redo this procedue.

Final Status
At this step, you have a Workorder containing the scenario to update the odeB.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
4-17
PRELIMINARY
Optional Sheet 4 : Neighboring Plan Update
...................................................................................................................................................................................................................................
Optional Sheet 4 : Neighboring Plan Update

Purpose
This procedure details how to manage the neighboring plan update under WPS.
Presentation
If the eighboring Plan Update is not required, this step can be skipped.
evertheless if the reparenting of the odeB(s) requires an update of the neighboring
plan, this procedure details how to manage the neighboring plan update under WPS.
To update efficiently the eighboring Plan refer to chapter 'eighboring Plan update
procedures' in document [R4].
Impact on service
one.
Final status
PRELIMINARY
At this step, you have a Workorder containing the scenario to update the neighboring
plan.
...................................................................................................................................................................................................................................
NN-20500-088
4-18
...................................................................................................................................................................................................................................

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

engineering rules.
PRELIMINARY
Input parameters
one.
Initial status
To have new odeB(s) reparented to RC in a Workspace under WPS.

Step Duration
This step lasts less than 5 minutes for a etwork containing 7 RCs and 860 odeBs.
Impact on service
one
Procedure
...................................................................................................................................................................................................
Under WPS, create a new workorder (if needed) and rename it (for example: "consistency
checks") as described in document [R3].
...................................................................................................................................................................................................
Launch checks from the network as described in document [R3].

...................................................................................................................................................................................................
Check that no error appears in the check session report.

E...................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of error, contact your local Engineering representative and correct the reported
errors.
After the execution of this procedure, all the checks must be error free.
...................................................................................................................................................................................................................................
NN-20500-088
4-19
PRELIMINARY
Final Status
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
This procedure details how to generate the XML file, which describes the modified Es
between the initial and the final network configuration.
This procedure enables to speed up the whole process, by exporting on the main server
only the relevant modifications to apply.
Input parameters
one.
Initial status
To have the odeB(s) reparented to RC in a Workspace under WPS.

To have the initial snapshot representing the initial network state and workorders
representing the modifications to apply on the network.
Step Duration
This step lasts a few seconds for 1 odeB.

Impact on service
one
Procedure
...................................................................................................................................................................................................
Under WPS, 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.
PRELIMINARY
...................................................................................................................................................................................................
In the workorders folder select the "Merge" workorder, right click Export workorder...
(choose "on local file system" or on "live server repository").
...................................................................................................................................................................................................
Enter a <Filename>, select a <Result_folder> and click Save
...................................................................................................................................................................................................................................
NN-20500-088
4-20
...................................................................................................................................................................................................................................
ote:
Select:
1. HOST
2. Username and Password (of the server)

Browse in the folders and give a name to the file
Click OK
PRELIMINARY
E...................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
In case of trouble during generation of XML file redo this step.

Final Status
At this step, the <Result_folder> contains the workorder (CM XML) file
<Filename>.xwo which describes the odeB(s) to reparent. This file will be used for the
direct operation. If the reverse operations needs to be applied, the Workorder file
<Filename_reverse>.xwo in the <Result_folder> will be used.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
4-21
PRELIMINARY
PRELIMINARY
PRELIMINARY
I5nstallation and
commissioning
Overview
Purpose
This chapter provides installation and commissioning procedures.

Contents
5-2
5-3
5-4
5-5
odeB verification
5-11
5-12
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
5-1
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
This procedure verifies that:
The network and the OMC are up and running without any problem. (Alarm, OMC
MIB State, Synchronization State, etc.)
Calls can be achieved on the impacted odeB
Calls can be achieved on the target RC
The odeB is ready to be reparented.
This procedure must be repeated for each impacted odeB.

This procedure is a recommendation and is not mandatory if all the states given by the
checks described above are well known.
Actions
Following operations may be performed:
Check that no impacting Alarm exist (See documents [R5] and [R9])
Perform an audit of the impacted RC (See document [R5])
Perform calls on the impacted RCs. Especially perform a call on the impacted
odeB(s)'s Cells
For Alcatel-Lucent 9313 Micro odeB and 9314 Pico odeB, see documents [R2],
[R12] and [R13]
Launch the TIL on the new odeB to check I&C parameters (See documents [R2] and
[R6])
Final status
The network and the OMC are up and running without any problem. (Alarm, OMC MIB
State, Synchronization State, etc.)
PRELIMINARY
The impacted RCs are up and running and the odeB is ready to be reparented.
...................................................................................................................................................................................................................................
NN-20500-088
5-2
...................................................................................................................................................................................................................................

Purpose
This activity modifies I&C parameters of the BTS.

For example, if DHCP configuration is not used, the IP address of the BTS has to be
changed. It is performed by using:
PRELIMINARY
The LMT for Alcatel-Lucent 9313 Micro odeB and 9314 Pico odeB.(See
document [R12])
The TIL for all other BTS (See document [R6]).
ote: For any questions concerning the DHCP activation or configuration, refer to the
documents [R15] or [R16]:
For a odeB use document [R15], Alcatel-Lucent odeB UA7.x DHCP

For a OneBTS use document [R16], Alcatel-Lucent OneBTS UA7.x DHCP

For Drop & Insert configuration, see documents [R10] and [R6].
Important! Before any IP address modifications, be sure of its new value. Any error
will need a change via a local TIL or RMT.
ote: After any IP address modification, a reset of the ode B is mandatory. This
operation will make a Supervision and a Telecom outages.
Actions
Out of scope of this document. Specific information could be found in the documents:
For Alcatel-Lucent 9313 Micro odeB and 9314 Pico odeB, see document [R12]
For all other BTS, see document [R6].
UMTS Drop & Insert via IBTS with fractional ATM over single E1
Final status
I&C parameters of the odeB are compliant with the target RC interface.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
5-3
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
These activities update the transmission network in order to move the connection of the
odeB(s) from the source RC to the target RC.
Especially if a Point of Concentration ode (POC, AM) is used. It might be
reconfigured in order to correctly re-direct the IuB to the target RC.
Actions
Out of scope of this document.

For information on the subject:
For Alcatel-Lucent 9313 Micro odeB and 9314 Pico odeB, see documents [R13]
and [R12]
ote: Do not forget to synchronize the reparenting work with the transmission
operational service.
Final status
The transmission network provides interconnection between the reparented odeB(s) and
the target RC(s).
PRELIMINARY
ote: If some transmission problems occur, refer to the transmission external team.
...................................................................................................................................................................................................................................
NN-20500-088
5-4
...................................................................................................................................................................................................................................

Purpose
This step activates the reparented odeB(s) so that they can start providing wireless
services again. It is performed on the WMS server using Access Module GUIs.
The activation is performed through "Activation Manager" mechanism in order to avoid
any interruption of service on the other odeB(s) of the RCs.
PRELIMINARY
At this step, on site activities should have been completed in order to resume BTS
Equipment supervision.
Input parameters
The IP address of the BTS must be known (I&C parameters)

The workorder (CM XML) file <Filename>.xwo is available in a folder
(/<Result_folder>) of the main server as described in document [R5].
Initial status
The I&C parameters of the BTS Equipment(s) and the Transmission etwork are up to
date.
Parameters at Core etwork Side are synchronized with the potential reconfigurations.
The etwork and the OMC are up and running without any problem. (Alarm, OMC MIB
State, Synchronization State, etc.).
All the workorder (CM XML) files from /<Result_folder> directory generated by WPS
have been transferred to a /<Result_folder> Main Server directory as described in
document [R5].
Step Duration
This step lasts for 1 odeB: TBC.

Impact on service
If required BTS Build otherwise none for the other odeB(s) of the impacted RCs.
Actions
...................................................................................................................................................................................................................................
NN-20500-088
5-5
PRELIMINARY
Activation of source and target RCs and, if required, Pre-Activation of

BTSEquipment(s)
PRELIMINARY
...................................................................................................................................................................................................................................
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>.
...................................................................................................................................................................................................
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.
...................................................................................................................................................................................................
PRELIMINARY
In the "Create Session" window:
Click Launch
In the "Sessions Manager" window Click Summary for <session_name> and check
the activation status of the nodes:
I-ode(s) should be in "Loaded" state
RC(s) should be in "Validated state

If listed, BTSEquipment(s) should be in "Validated" state
...................................................................................................................................................................................................................................
NN-20500-088
5-6
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
After session creation completion without errors, in the "Actions for <session_name>" tab
click Validation:
Select all the impacted I-ode(s) and click Launch
Check the validation report of each node in the summary section:

In the "Sessions Manager" window Click Summary for <session_name> (Iode(
s) should be in released state), select a node in the table and click the hyperlink to
display the HTML validation report
PRELIMINARY
...................................................................................................................................................................................................
After validation completion without errors, in the "Actions for <session name>" tab click
Pre-activation:
If listed, select all the impacted odes BTSEquipment(s) and click Launch
...................................................................................................................................................................................................
10
After validation and pre-activation completion without errors, in the "Actions for
<session name>" tab click Activation:
When all tasks are completed, in the "Sessions Manager" window Click Summary for
<session name> to check that all impacted I-ode(s) are Released
For each odeB (except Alcatel-Lucent 9313 Micro odeB and 9314 Pico odeB):
Open link and activation of the new equipment
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
5-7
PRELIMINARY
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
11
Check that the ode B become reachable and send a Ping command to the BTS
Equipment in order to check the OAM link.
Result: The ping correctly responds
...................................................................................................................................................................................................
12
Select the reparented BTS Equipment in WMS Graphical etwork Display.

ote: If the BTS Equipment was not in the same layout that the Target RC it might
be necessary to move it in your Layout from the E Store. For more information
please refer to document [R9].
...................................................................................................................................................................................................
13
If necessary, set the OAM link administrative state of the BTS Equipment to "unlocked"
in the "Set E's OAM Link Administrative State Action Window" command window.
...................................................................................................................................................................................................
14
After BTS Equipment connection request success, in the "Sessions Manager" window:
In the "Actions for <session name>" tab click Launch
If listed, select the BTS Equipment and click Launch

When all tasks are completed, in the "Sessions Manager" window Click Summary for
<session name> to check that the BTSEquipment is released
Post-condition: The BTS Equipment is released with unlocked administrative state.

Repeat step 11, 12, 13 and 14 for each reparented odeB.
Activation of source and target RCs (C-ode Part)
...................................................................................................................................................................................................
15
In the "Sessions Manager" window:
In the "Actions for <session name> 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> to check that all nodes are released.
...................................................................................................................................................................................................
PRELIMINARY
16
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
Post-condition: The odeB sub-tree is released on the target RC with unlocked
administrative states and de-activated from the source RC
...................................................................................................................................................................................................................................
NN-20500-088
5-8
...................................................................................................................................................................................................................................
ote: After terminating the session if you want to restore the initial configuration go
toReverse operation (p. 6-2) and activate the reverse Workorder
E...................................................................................................................................................................................................
N D O F S T E P S
Troubleshooting
PRELIMINARY
ote : All commands are logged in the Command Manager (See [R7])
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"
In case of errors in session validation, analyze logs or

"Validated"
In case of error in pre-activation, return to step 5.
"Validation Failed"

11
Ping does not

respond
In case of ping failure, contact your local support or

networks designers in order to correct XML file, Abort
then terminate the session and return to step 1.
"Locked"
In case of unlock command failure, contact your local

support or network designers in order to identify and
correct the problem and return to step 9 to check the
correction.
10
"Validated"
In the Command Manager window check the status of

impacted BTSEquipment:
...................................................................................................................................................................................................................................
NN-20500-088
5-9
PRELIMINARY
In case of Build failure (the Status is "Stopped with

errors") analyze the logs or contact your local support or
networks designers in order to correct the problem. Once
the problem identified and corrected, return to step 10
otherwise terminate the session and go toReverse
operation (p. 6-2) to restore the initial configuration.
PRELIMINARY
...................................................................................................................................................................................................................................
Failed Step
Node Status
Action
11
"Activation partly
realized"
If the Status is "Completed with errors":

Fallback all the RC C-odes and all the RC I-odes
(see document [R5]):
If the Fallback is completed : Terminate.
If the Fallback failed: Abort then terminate the

session and go toReverse operation (p. 6-2) to
restore the initial configuration.
Final status
WMS Level
Object
State
Value
BTSEquipment
OAMlinkadministrativeState
unlocked
odeB
administrativeState
unlocked
FDDcell
administrativeState
unlocked
Object
State
Value
RC
Activation
Released
RC I-ode
Activation
Released
BTSEquipment
Activation
Released
odeB(s) is(are) available for monitoring.

NodeB Level
The odeB(s) is(are) ready to provide service

RNC
PRELIMINARY
The RC ensures call management for the reparented odeB(s).

Mobility
The UMTS outgoing neighboring links are active.
The UMTS incoming neighboring links are active.
ote: If the reparented ode B is managed by a new RC, a new organization of the
WMS layout may be possible.
...................................................................................................................................................................................................................................
NN-20500-088
5-10
NodeB verification
...................................................................................................................................................................................................................................
NodeB verification
Purpose
This activity ensures that the reparented odeB provides the expected level of wireless
service.
PRELIMINARY
Actions
Out of scope of this document, specific information could be found in the following
documents:
For Alcatel-Lucent 9313 Micro odeB and 9314 Pico odeB, see documents [R2],
[R12] and [R13]
Final status
The odeB(s) is (are) fully available for wireless services.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
5-11
PRELIMINARY
...................................................................................................................................................................................................................................

Purpose
This procedure aims at verifying the following points:
The network and the OMC are up and running without problem (Alarms, OMC MIB
state, synchronization state, etc.)
Calls can be achieved on the reparented ode B.
This procedure has to be repeated for each impacted ode B.

Action
The following actions must be performed:
Check that no impacting alarm exist (See document [R5] and [R9])
Perform an audit of the impacted RC
Perform calls on the impacted RC and ode B.
Launch the TIL or RMT (as appropriate) on the reparented ode B to check the I&C
parameters (See documents [R2] and [R6])
Final status
The network and the OMC are up and running without problem.
PRELIMINARY
The impacted RC and the reparented ode B are up and running.
...................................................................................................................................................................................................................................
NN-20500-088
5-12
PRELIMINARY
Reverse operation
6
Overview
Purpose
This chapter provides the reverse operation to retrieve the initial configuration.
Contents
Reverse operation
6-2
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
6-1
PRELIMINARY
Reverse operation
Reverse operation
...................................................................................................................................................................................................................................
Reverse operation
Overview
If the BTS Equipment, in final configuration, does not manage to open the OAM
connection, it will go back to the initial configuration to re-establish a connection with the
OMC. In this case, a reverse operation described below is to be done.
The reverse operation is also required when the activation step has not been successfully
completed or if the operator wants to retrieve the initial configuration.
Input parameters
The data mandatory for reverse operation (See /<Result_folder> folder) must be
available.
The used workorder (CM XML) file will be found under this latter folder only
Step Duration
This step lasts for 1 odeB: TBC.

Impact on service
RC build in case of Fallback failure in troubleshooting part of chapterReconfiguration

activation in WMS (p. 5-5) otherwise one.
Actions
Reverse workorder activation

Go through the following sequences, taking into account data coming from
/<Result_folder> folder.
Procedure
...................................................................................................................................................................................................
Important! Be aware that the I&C modification parameters can lead to transmission
lost. Then all modification can be done via local TIL.
PRELIMINARY
If the I&C parameters are modified, return to the initial I&C parameters (see chapter
Change I&C parameters (p. 5-3)).
...................................................................................................................................................................................................
Update back the transmission network in order to move back the connection of the
odeB(s) from the target RC to the source one (see chapter On Site activities for
transmission network update (p. 5-4)).
ote: If some transmission problems occur, refer to the transmission external team.
...................................................................................................................................................................................................................................
NN-20500-088
6-2
Reverse operation
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
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.
PRELIMINARY
Reverse operation
Result: The Create Session window appears.

...................................................................................................................................................................................................
In the "Create Session " window:
Enter a <reverse session name>

Select in the <Result_folder> folder the workorder (CM XML)
file<Filename>_reverse.xwo to be activated
Click Show impacts in order to list the impacted nodes
If the fallback have been already performed, exclude the RC C-ode(s) by selecting
them in the list
Click Launch
In the "Sessions Manager" window Click Summary for <reverse session name> and
check the activation status of the nodes:
I-ode(s) should be in "Loaded" state

RC(s) should be in "Validated" state
If listed, BTSEquipment(s) should be in "Validated" state
...................................................................................................................................................................................................
After session creation completion without errors, in the "Actions for <reverse session
name>" tab click Validation:
Check the validation report of each node in the summary section:

Click Summary for <reverse session name> (I-ode(s) should be in released.
Check the odesBs are removed
...................................................................................................................................................................................................
After validation completion without errors, in the "Actions for <reverse session name>
tab click Activation
When all tasks are completed, click Summary for <reverse session name> to check
that all impacted I-ode(s) are activated
...................................................................................................................................................................................................................................
NN-20500-088
6-3
PRELIMINARY
PRELIMINARY
Reverse operation
Reverse operation
...................................................................................................................................................................................................................................
...................................................................................................................................................................................................
In the "Sessions Manager" window:
In the "Actions for <reverse session name>" tab click Activation
Select all the impacted RCs and BTSEquipment(s) and click Launch
When all tasks are completed, click Summary for <reverse session name> to check
that all nodes are activated
...................................................................................................................................................................................................
The Command Manager window can be launched to display the status of each command.
...................................................................................................................................................................................................
10
When all tasks are completed check the logs for each command to confirm the completion
of the activation.
...................................................................................................................................................................................................
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
Troubleshooting
PRELIMINARY
ote: All commands are logged in the Command Manager (See document [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 then terminate the
session and return to step 3.
"Validation Failed"

"Validated"
In case of error in pre-activation, return to step 7.
"Validation Failed"

...................................................................................................................................................................................................................................
NN-20500-088
6-4
Reverse operation
...................................................................................................................................................................................................................................
Failed Step
Node Status
Action
"Validated" for
BTSEquipment
In the Command Manager window check the status

of impacted BTSEquipment(s):
In case of Build failure (the Status is "Stopped with
errors") analyze the logs or contact your local support
or networks designers in order to correct the problem.
Once the problem identified and corrected, return to
step 8.
"Activation partly
realized"
PRELIMINARY
Reverse operation
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]).
Final Status
WMS, source RC, and target RC are back to their initial state.
The neighboring plan goes back to the initial configuration.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
6-5
PRELIMINARY
PRELIMINARY
PM and FM impacts
7
PRELIMINARY
Impacts
PM impact
If I&C modifications are performed ChapterChange I&C parameters (p. 5-3) in order to
change the IP address, the BTS should be reset (in order to connect BTS to OMC-B). As a
consequence, the BTS Performance counter history is cleared. This implies that the PM
System cannot get the BTS counters related to the latest period before IP change (for
more details see Chapter "How to retrieve counters further to an odeB IP address
change" in document [R11]).
The reparented odeB(s) is managed by the PM system.
FM impact
The procedure ensures the correct declaration of the reparented odeB(s) with respect to
FM management.
PRELIMINARY
...................................................................................................................................................................................................................................
NN-20500-088
7-1
PRELIMINARY
PRELIMINARY
...................................................................................................................................................................................................................................
AN
Access ode
PRELIMINARY
Glossary
...................................................................................................................................................................................................................................
CM
Configuration Management
CN
Control ode
...................................................................................................................................................................................................................................
EM
Equipment Monitor
...................................................................................................................................................................................................................................
GUI
Graphic User Interface

...................................................................................................................................................................................................................................
IN
Interface ode
...................................................................................................................................................................................................................................
MO
Managed Object
...................................................................................................................................................................................................................................
PM
Performance Management
...................................................................................................................................................................................................................................
WICL
Wireless Internet Command Language

WMS
Wireless Management System (the old name was W-MS)

...................................................................................................................................................................................................................................
NN-20500-088
GL-1
PRELIMINARY
PRELIMINARY
PRELIMINARY
Glossary
...................................................................................................................................................................................................................................
WPS
Wireless Provisioning System
...................................................................................................................................................................................................................................
NN-20500-088
GL-2

NN-20500-088 (9300 W-CDMA Product Family - Node B Reparenting NRP) 12

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

NN-20500-088 (9300 W-CDMA Product Family - Node B Reparenting NRP) 12

Загружено:

Авторское право:

Доступные форматы

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

Roadmap to Configuration Management documentation

Node B reparenting overview

Intra-ROC ode B reparenting restriction

Mean time (TBC) ....................................................................................................................................................................... 3-5

Prerequisites ................................................................................................................................................................................. 3-8

NodeB reparenting preparation under WPS

Sheet 1 - Reverse Engineering

Sheet 2b - OneBTS (ATM) Reparenting ......................................................................................................................... 4-10

Optional Sheet 4 : eighboring Plan Update

Sheet 7 - Export workorders ................................................................................................................................................ 4-20

Installation and commissioning

On Site activities for transmission network update

Reconfiguration activation in WMS

Performing checks after reparenting

Impacts ........................................................................................................................................................................................... 7-1

General description for an iBTS

General description for a OneBTS

About this document

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

The reissue reasons are:

Reason for reissue

Updated after internal review.

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.

The following topics are out of the 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)

UMTS BTS Integration in an Exiting UTRA

Alcatel-Lucent 9352 Provisioning System - User Guide

eighboring Plan Update

Alcatel-Lucent 9353 Management System - User Guide

UMTS iBTS commissioning Procedure

CM XML format Description

Product Family - Terminology

Alcatel-Lucent 9353 Management System - System Overview

Alcatel-Lucent 9300 W-CDMA Product Family - Performance Management

Alcatel-Lucent 9313 Micro ode B and 9314 Pico ode B - Local

Alcatel-Lucent odeB UA7.x DHCP Activation

Alcatel-Lucent OneBTS UA7.x DHCP Activation

About this document

About this document

9300 W-CDMA Product Family - Activation of ative IP IuB

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,

Node B reparenting overview

as displayed in the diagram below:

Figure 2-2 General description for a OneBTS

Node B reparenting overview