IM 30-6221-301 Alcatel-Lucent NodeB UA7.x Integration in An Existing Utran

Alcatel-Lucent NodeB UA07.
x
Integration in an Existing UTRAN
Installation Method 30-6221
April 23, 2010

Issue Number: 3.01
UNCONTROLLED COPY: The master of this document is stored on an electronic

database and is "write protected"; it may be altered only by authorized persons. While
copies may be printed, it is not recommended. Viewing of the master electronically
ensures access to the current issue. Any hardcopies taken must be regarded as
uncontrolled copies.
ALCATEL-LUCENT CONFIDENTIAL: The information contained in this document is
the property of Alcatel-Lucent. Except as expressly authorized in writing by AlcatelLucent, the holder shall keep all information contained herein confidential, shall
disclose the information only to its employees with a need to know, and shall protect
the information from disclosure and dissemination to third parties. Except as expressly
authorized in writing by Alcatel-Lucent, the holder is granted no rights to use the
information contained herein. If you have received this document in error, please notify
the sender and destroy it immediately.
2010 Alcatel-Lucent
All Rights Reserved
April 23, 2010
Method 30-6221
Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 1
Method 30-6221
April 23, 2010
Table of Contents
1.0 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.2 Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3 Reason for Reissue. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.0 .Material Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
2.1 Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.2 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.3 Hardware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2.4 Login/password Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
3.0 Precautions and Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.1 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.2 Preparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
3.3 Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.0 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.1 UTRAN introduction of the UA07 / OAM07 system release . . . . . . . . . . . . . . . . . . . . . . 16
4.2 Alcatel-Lucent UTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.3 RNC Main Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4 W-NMS General principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.5 WPS General Principles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.6 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.7 First Time Only PC Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Procedure 1 Hostname Setup (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
4.8 NSP Starting Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Procedure 2 Navigator Starting Up Configuration in UA06 . . . . . . . . . . . . . . . . 23
4.9 Opening the RNC Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Procedure 3 Opening the Concerned Layout in View Mode . . . . . . . . . . . . . . . 27
Procedure 4 Show RNCs Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.10 Import Network Configuration into WPS (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Procedure 5 Import Network Configuration into WPS (optional) . . . . . . . . . . . . 31
4.11 New NodeB Creation with WPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.12 Parenting a New NodeB* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Procedure 6 Parenting a new NodeB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
4.13 Export Workorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Procedure 7 Export Workorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.14 Pre Checks before Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Procedure 8 Pre Checks before Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.15 Session Creation for NodeB Activation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Procedure 9 NodeB Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.16 Open Link of each NEs and build the Equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Procedure 10 Changing the NEs OAM Link Administrative State . . . . . . . . . . 71
4.17 BTS Online Tests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Procedure 11 Checking the BTS Cell(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Procedure 12 Board Redundancy Test (Optional) . . . . . . . . . . . . . . . . . . . . . . 78
4.18 Communication Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
4.18.1 CS Call on a cell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Procedure 13 Locking the Untested Cell(s). . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
2 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN
April 23, 2010
Method 30-6221
Procedure 14 CS Call on the Unlocked Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

4.18.2 Video Streaming Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Procedure 15 Locking the Untested Cell(s) (Optional) . . . . . . . . . . . . . . . . . . . . 86
Procedure 16 Video Call on the Unlocked Cell (Optional) . . . . . . . . . . . . . . . . . 88
4.18.3 PS Communication Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Procedure 17 Locking the Untested Cell(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Procedure 18 Dial-up Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Procedure 19 IP Address Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Procedure 20 Ping the GGSN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
4.19 Open for a FTP Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Procedure 21 Open a FTP Session (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.20 Call Trace Configuration (Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
4.20.1 Call Trace Session configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Procedure 22 Call Trace Configuration Wizard (optional) . . . . . . . . . . . . . . . . 101
4.20.2 Trace Session Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Procedure 23 Creation of a Trace Session Template (optional) . . . . . . . . . . . 112
4.20.3 Call Trace Deletion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Procedure 24 Call Trace Deletion (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . 118
4.21 Layout Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4.21.1 Layout Creation (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Procedure 25 Layout Creation (Optional). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
4.21.2 Layout Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Procedure 26 Opening a Layout in Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . 120
4.21.3 Layout in view mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Procedure 27 Opening the Layout in View Mode . . . . . . . . . . . . . . . . . . . . . . . 123
4.22 Node-B software verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
4.23 BTS NeId exchange (optional) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Procedure 28 Retrieve and Change the BTS NeId (Optional) . . . . . . . . . . . . . 126
4.24 DC/DC Converter Alarm Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Procedure 29 DC/DC Converter Alarm Integration (Optional) . . . . . . . . . . . . . 130
4.25 9326 d2U V2 in a Small or Medium S6 OD Alarms Integration . . . . . . . . . . . . . . . . . . 134
Procedure 30 9326 d2U V2 in a Small or Medium Alarms Integration (Optional) .
134
5.0 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1 Appendix A -- Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2 Appendix B -- Dial-up Setup and Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 31 Setup the Dial-up Networking (Optional) . . . . . . . . . . . . . . . . . .
Procedure 32 Check the Dial-up Properties (Optional) . . . . . . . . . . . . . . . . . .
5.3 Appendix C -- Workorder Creation for a new NodeB . . . . . . . . . . . . . . . . . . . . . . . . . . .
Procedure 33 NodeB Workorder Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.4 Appendix D - Report Sheet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
140
140
141
141
145
149
149
161
6.0 Last page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Method 30-6221
April 23, 2010
April 23, 2010
Method 30-6221
Figures
Figure 1 Research the Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 2 Hosts File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 3 Open the NSP*Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 4 Open the NSP*Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 5 Console Java Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 6 Login Window* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 7 Warning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 8 NSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 9 Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 10 Concerned Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 11 Resource Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 12 Show Alarms of the Concerned RNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 13 Alarm Manager Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 14 WPS GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 15 Import Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 16 Import Snapshot (local file system). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 17 File Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 18 Replace Initial Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 19 Import Completion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 20 Create a New Workorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 21 NodeB Parenting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 22 NodeB Parenting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 23 Parent NodeB operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 24 Streams Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 25 Streams parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 26 Call Admission Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 27 Call Admission Control parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 28 BTS PCM Configuration* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 29 OneBTS Physical Resource Configuration *. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 30 BTS ATM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 31 OneBTS ATM Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 32 ATM Switching Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 33 Optical Connection Configuration* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 34 Optical Connections Configuration * . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 35 Iub ATM Switching Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 36 Aggregation Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 37 DHCP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 38 NodeB parented . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 39 Merge Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 40 Workspace Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 41 Configuration - MIB - Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 42 Audit Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 43 Command Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 44 Session Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 45 Workorder to Open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 46 Session Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 47 Summary for Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 48 Validation Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 49 Validation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
21
22
23
24
25
26
26
27
27
28
28
29
30
31
32
32
33
34
35
37
38
39
40
41
42
43
44
44
45
46
47
48
49
50
51
52
53
54
55
56
57
57
58
59
60
61
62
63
64
Method 30-6221
April 23, 2010
Figure 50 Pre Activate Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Figure 51 Pre Activate Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 52 Activation Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 53 Activation Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 54 Command Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 55 Release Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Figure 56 OAM Link Administrative State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Figure 57 OAM Link Administrative State (OneBTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Figure 58 Set NEs OAM Link Administrative State Locked Status . . . . . . . . . . . . . . . . 74
Figure 59 Set NEs OAM Link Administrative State Locked Status (OneBTS) . . . . . . . . 74
Figure 60 Set NEs OAM Link Administrative State Unlocked Status . . . . . . . . . . . . . . . 75
Figure 61 Set NEs OAM Link Administrative State Unlocked Status (OneBTS) . . . . . . . 75
Figure 62 RNC NE Show Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Figure 63 Alarm Manager for FCC Cell Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Figure 64 Equipment Monitor Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Figure 65 BTS Equipment Monitor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Figure 66 Reset Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 67 Reset Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Figure 68 Equipment Monitor Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Figure 69 FDD Cells Set Administrative State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Figure 70 FDD Cell Administrative State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 71 Command Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Figure 72 Communication Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Figure 74 FDD Cell Set Administrative State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 75 FDD Cell Set Administrative State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Figure 76 Video Call Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Figure 78 FDD_Cell_Set_Administrative_State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 79 FDD Cell Administrative State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Figure 80 Dial-up Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Figure 81 Run Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Figure 82 IP address Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Figure 83 Ping Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Figure 84 Ping Message Validated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 85 Ping Message Not Validated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Figure 86 Ping Way or PS Network Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Figure 87 Cmd Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Figure 88 FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 89 FTP Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Figure 90 Downlink Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 91 Uplink Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Figure 92 Call Trace Configuration Wizard command . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Figure 93 Call Trace Configuration Wizard window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 94 Manage the Call Trace Session. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Figure 95 Create Call Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 96 Call Trace Access Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 97 Creation type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 98 RNC and NBAP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 99 Mobile identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Figure 100 Mobiles Indentified . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Figure 101 Summary information* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
April 23, 2010
Method 30-6221
Figure 102 Trace session creation successful* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 103 Command Manager* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 104 Call Trace Operation Successful* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 105 Call Trace Session Creation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 106 Session Manager for Call Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 107 Creation of Trace Session Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 108 Trace Session Template Parameters* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 109 Summary of Template Information* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 110 Trace Session Template Creation* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 111 Successful Operation* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 112 NSP View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 113 Layout Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 114 Input Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 115 NSP View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 116 Layout Selector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 117 New Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 118 Navigator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 119 Edit Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 120 NSP View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 121 New Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 122 Navigator Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 123 View Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 124 Main TIL Window of the BTS (example) . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 125 Object Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 126 Object Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 127 Equipment Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 128 External Alarm Mapping Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 129 External Alarm Mapping Table Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 130 Object Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 131 Object Editor Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 132 Object Editor Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 133 Command Manager* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 134 Equipment Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 135 External Alarm Mapping Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 136 Customer External Alarms with less than 8 pairs used. . . . . . . . . . . . . . . . . .
Figure 137 Customer External Alarms with more than 8 pairs used (up to 12 available) .
Figure 138 External Alarm Mapping Table Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 139 Object Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 140 Object Editor Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 141 Object Editor Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 142 Command Manager * . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 143 New Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 144 Wizard Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 145 Network Connection Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 146 Phone Number to Dial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 147 Connection Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 148 Connection Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 149 Dial-up Properties: General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 150 Dial-up Properties: Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 151 Dial-up Properties: Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 152 Dial-up Properties: Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 153 Create a New Workorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
108
109
110
111
112
113
114
115
116
117
119
119
119
120
120
121
121
122
123
123
124
124
127
128
129
130
130
130
131
132
132
133
134
134
135
135
136
136
138
138
139
141
142
143
143
144
144
145
146
147
148
149
Method 30-6221
April 23, 2010
Figure 154 NodeB Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Figure 155 BTS Equipment Configuration window
...........................
...........................
...........................
Figure 158 BTS Equipment Operation Status Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 159 OneBTS or NodeB Cells Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 160 NodeB Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 161 OneBTS Creation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 162 FDD Cell Radio Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 163 FDD Cell Localization Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 164 Geographical Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figure 165 NodeB Channel Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
151
152
153
154
155
156
157
157
158
158
159
160
April 23, 2010
Method 30-6221
Tables
Table 1 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 2 Hardware tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 3 NodeB Integration Operations Listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 4 Optional operations for NodeB integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 5 Required Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 6 BTS Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 7 Communication Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 8 Antennae Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Table 9 Sequence of Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Method 30-6221
April 23, 2010
1.0 General Information

1.1 Description
Purpose: This document describes the operations to perform to
integrate new NodeB on an in-service UTRAN using W-NMS NSP.
Equipment: This document applies to all the UMTS NodeB with 9370
RNC except for the STM1 9313 Micro/9314 Pico NodeB.
For the 9313 Micro/9314 Pico NodeB, please refer to NN-20500-058
Pico/Micro Operations.
Application: This document applies to:
the UTRAN equipment from V7.0 software release with the OAM in
V7.0 software release until a new document is provided.
the WPS application is performed during this procedure as an
example.
Service Impact: None.
1.2 Sequence
This method is to be performed after the following procedure:
IM 30-6222 Alcatel-Lucent 9370 RNC UA07.x Integration
IM 24-6253 Alcatel-Lucent NodeB Commissioning Procedure
IM 24-0648 Alcatel-Lucent 9313 Micro (1120) Commissioning
Procedure
IM 24-6298 Alcatel-Lucent 9314 Pico (1010) Commissioning
Procedure
These procedures can be find under the following link:
https://wcdma-ll.app.alcatel-lucent.com/livelink/livelink.exe/fetch/
2000/29267553/29445737/36413001/36566963/36528788/36528896/
customview%2Ehtml?func=ll&objId=36528896&objAction=browse&
sort=name&viewType=1
or under the following Link:
http://www.cic.lucent.com/
April 23, 2010
Method 30-6221
1.3 Reason for Reissue

301: (23/04/2010) Update in Standard Version
203: TIL password used on the xCCM.
202: Add the NRP and WPS documentation link as mandatory
required
201: This is the initial release of this method
Method 30-6221
April 23, 2010
2.0 .Material Requirements

2.1 Required Documents
NN-20500-149 Alcatel-Lucent Node-B Software Upgrade Procedure
Using OAM 7.x Inter Release Upgrade
NN-20500-151 Alcatel-Lucent 9313 Micro Node B and 9314 Pico
Node B - Software Upgrade Procedure Using OAM 7.x
NN-20500-152 Alcatel-Lucent OneBTS Software Upgrade
Procedure Using OAM 7.x
@ https://wcdma-ll.app.alcatel-lucent.com/livelink/
livelink.exe?func=ll&objId=52077919&objAction=browse&sort=nam
e&viewType=1
NN-20500-036 (Alcatel-Lucent 9352 Provisioning System - User
Guide)
NN-20500-087 (Alcatel-Lucent 9300 W-CDMA - NodeB Addition
NRP)
NN-20500-027 P4 (Alcatel-Lucent 9300 W-CDMA - Parameter
Reference Guide - NodeB Parameters)
Reference Guide - Micro NodeB Parameters)
Reference Guide - OneBTS Parameters)
e&viewType=1
NN-20500-234 (Alcatel-Lucent 9300 W-CDMA Product Family Performance Management )
e&viewType=1
NN-20500-057 (Alcatel-Lucent 9313 Micro Node B and 9314 Pico
Node B - Local Maintenace Tool Manual)
NN-20500-058 (Alcatel-Lucent 9313 Micro Node B and 9314 Pico
Node B - Operation and Maintenance Manual)
@: https://wcdma-ll.app.alcatel-lucent.com/livelink/
e&viewType=1
April 23, 2010
Method 30-6221
2.2 Software
For the use of OAM V7 client and the Remote TIL, the PC should be
equipped with:
Table 1 Software
Operating
System
Internet
Web
browser
One of the following: (supported by OAM V7)

Windows 2000 or XP or NT 4.0
One of the following:
Internet Explorer 6 or higher
Mozilla Firefox 1.7 or higher
Additional
software
requirements
Web access for OAM Client is Java Runtime Environment 1.5.0 or higher (JRE
1.5.0_14 is recommended and can be found at http://java.sun.com/j2se/1.5/
download.html)
The IP address of the Alcatel-Lucent NodeB equipment to which the TIL must
connect (see Note).
Note: JRE 1.5.0 On site, CCM/iCCM has a unique address 223.254.254.244 on
port 2 (or port 1 for xCCM)
Note: If the TML has already been installed on the PC, the JRE installation is not necessary.
Telnet VT100
Exceed available for running MDM
2.3 Hardware
The following table summarizes the hardware required to run the TIL
tool
Table 2 Hardware tools
Minimum
Hardware
required
1 PC with VGA Monitor

128 Mbyte of RAM
10 Mbyte or more (20 Mbyte are recommended) of free hard disk space
1 CD ROM 4X drive
1 PCMCIA board interface(s)
1 Ethernet board in a PCMCIA format
1 RJ45 crossover cable (for direct connection)
1 RJ45 straight through cable
1 PC/AT enhanced keyboard (101/102-key)
Method 30-6221
April 23, 2010
Table 2 Hardware tools (Contd)

Additional
Hardware
requirements
3G Mobile (for CS calls)

PC setup with Mobile Driver
PC Dial up connection ready (for PS data Calls)
No other materials are required to perform this method.
2.4 Login/password Availability

W-NMS OAM Client administrator account login and password with
full access are required.
April 23, 2010
Method 30-6221
3.0 Precautions and Preparations

3.1 Precautions
Check that all the prerequisites have been done.
3.2 Preparations
It is strongly recommended that this method be read in its entirety before
starting the operations presented herein.
3.3 Check List

Verify that the following items have been received and/or accomplished
before proceeding with the procedure.
F The UTRAN has been integrated using:
IM 65-6222 Alcatel-Lucent 9370 RNC UA07.x Integration.
F The BTS to add has been commissioned using:
IM 24-6253 Alcatel-Lucent NodeB Commissioning Procedure.
F The JRE already downloaded to access to the first GUI URL
F The NSP GUI with access plug-in on OAM PC client have been
installed and are operational. At least one user should be created in
the NSP administrator group, the correct access rights have to be set
to allow the user to create a layout.
F The CM XML files should be present in the MAIN SERVER.
Method 30-6221
April 23, 2010
4.0 Procedure
4.1 UTRAN introduction of the UA07 / OAM07 system release
The UTRAN is composed of several Radio Network Subsystems
(RNS). An RNS covers a certain geographical area. It is equivalent to
the GSM BSS. Each RNS is composed of one Radio Network Controller
(RNC) and several Node Bs. RNSs are interconnected through the Iur
interface of each RNC to form a network.
4.2 Alcatel-Lucent UTRAN

The Alcatel-Lucent UTRAN of the UA07 / OAM07 system release is
based on the following components:
UMTS RNC
UMTS BTS
WMS for the OAM part
UTRAN release is UA07 / OAM07.
4.3 RNC Main Functions

The main functions of the RNC are to control and manage:
Radio Access Network (RAN)
Signaling between Core Network (CN) components and the Radio
Network System (RNS)
Node Bs and their radio resources
The RNC provides the following interfaces:
Iub towards a Node B
Iu towards the Core Network
Iur towards another RNC
Iupc towards a Standalone A-GPS SMLC (SAS)
4.4 W-NMS General principles

The Wireless Network Management System (W-NMS) is the solution
for network planning, building,operation and maintenance. W-NMS is
built on Network Services Platform (NSP) technology. The NSP
window is the window from which you launch and display other
applications. The Layout Selector enables to open network layouts for
April 23, 2010
Method 30-6221
viewing or editing. The Navigator window opens automatically when

you open a layout and shows a hierarchical tree display of the resource
groups in the opened layout.
4.5 WPS General Principles

WPS is a high-performance kernel which provides support to design and
configure Alcatel-Lucent networks. It offers a centralized view and
configuration of all Network Elements (NE) & parameters. WPS
applications can be used for configuration at every stage of a network
management:
Data engineering of a new network.
Data engineering for network expansion, densification.
Data engineering for network optimization.
Data engineering for upgrade provisioning.
WPS manages configuration data coming from various sources. The file
format used is CM XML. Very large networks are supported in a
workable and acceptable performances. WPS supports multiple WNMS
Main Servers within a Regional Operational Center (ROC).
Method 30-6221
April 23, 2010
4.6 Overview
The operations detailed in the following table are mandatory for a
correct NodeB integration.
Table 3 NodeB Integration Operations Listing
Procedure
Number
Operations Name
Remarks
Hostname Setup (Optional)
First Connection with laptop on the

network
P2
Navigator Starting Up
Configuration in UA06
How to Start the NSP
P3
- Opening the Concerned

Layout in View Mode
- Show RNCs Alarms
Check RNC layout and Alarms before

NodeB integration
Import Network
Configuration into WPS
(optional)
This step details how to proceed with WPS

and the main server to import a view of the
current network configuration into WPS
NodeB Workorder Creation
Example of Creation of the NodeB

workorder with WPS
Parenting a new NodeB
Example of how to parent a new NodeB to

an existing RNC with WPS
Export Workorder
Generation of a XML file with the

differences between the initial and final
network configuration.
P1
P4
P5
Appendix CProc 33
P6
P7
P8
P9
Pre Checks before

Activation
NodeB Session
Activation of the Node with Session

Manager
P10
Changing the NEs OAM

Link Administrative State
Changing NE OAM Link and (Automaticaly)

Build of the new Equipment.
P11
P12
-Checking the BTS Cell(s)

- Locking the Untested
Cell(s)
NodeB on line tests
April 23, 2010
Procedure
Number
P13
P14
P15
P16
P17
P18
P19
P20
Method 30-6221
Operations Name
Remarks

Cell(s)
- CS Call on the Unlocked
Cell
Cell(s) (Optional)
- Video Call on the
Unlocked Cell (Optional)
Cell(s)
- Dial-up Connection
- IP Address Allocation
- Ping the GGSN
Communication Tests
Method 30-6221
April 23, 2010
The following procedures are optional but could be used for checks and
network verification.
Table 4 Optional operations for NodeB integration
Procedure
Number
Operations Name
Remarks
P21
Open a FTP Session

(Optional)
FTP Session
P22
- Call Trace Configuration

Wizard (optional)
- Creation of a Trace
Session Template
(optional)
- Call Trace Deletion
(optional)
Call trace operations:

How to create and manage Call Trace
sessions
- Layout Creation (Optional)

- Opening a Layout in Edit
Mode
- Opening the Layout in
View Mode
Layout Operations:
How to create, edit and view layout window
P28
Retrieve and Change the

BTS NeId (Optional)
NeId Exchange:
How to verify and change the NodeB NeId
P29
DC/DC Converter Alarm

Integration (Optional)
P30
9326 d2U V2 in a Small or

Medium Alarms Integration
(Optional)
P23
P24
P25
P26
P27
Important: Please Note the pictures displayed on the following

procedures are shown as operations examples and could be
slightly different from those you can see during the NE
operations.
April 23, 2010
Method 30-6221
4.7 First Time Only PC Setting

WARNING
This chapter applies only for first time PC setting. The
aim of this chapter is to set all the access parameters in
the PC in order to make the PC as an OAM client station.
The objective of this procedure is to explain how to reach the NSP server
from the PC.
Procedure 1 Hostname Setup (Optional) (Page 1 of 2)
Step
Action
Observation
Check that the NSP server name and its IP

address are present under the hosts file: Find the
hosts file on your PC (see Figure 1) and open it,
e.g. using notepad (see Figure 2).
Figure 1 Research the Hosts File
Select this check box if necessary
Method 30-6221
April 23, 2010
Procedure 1 Hostname Setup (Optional) (Page 2 of 2)

Step
Action
Observation
If it is not the case, to be able to reach the

dedicated NSP server, write its hostname and IP
address in the Hosts file of your PC. Open the
Hosts file (e.g .using notepad), and write the
NSP server parameters.
Refer to Figure 2. In our example the IP

address is 135.120.165.101 and the hostname is
ducados.
Figure 2 Hosts File
The NSP servers parameters are set in the PC.

Save these new parameters in the hosts file.
April 23, 2010
Method 30-6221
4.8 NSP Starting Up

The objective of this procedure is to launch the GUI and if needed to
provoke the correct JRE downloading.
In UA6 the mandatory Java Runtime Environment is version 1.5.0
update 14
Procedure 2 Navigator Starting Up Configuration in UA06 (Page 1 of 4)
Step
Action
Start your web browser.

In the URL field of your web browser, enter the
NSP servers name.
Observation
In our example below, the NSP server is:
"ducados" .
>http://servers name:8080/NSP/
>http://
ducados.ctflab.cit.alcatel.fr:8
080/NSP/
Figure 3 Open the NSP*Session
Select "Executer"
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 4 Open the NSP*Session
In the Web browser, click on LAUNCH GUI

Refer to Figure 4.
Note: If the JRE 1.5.0_14 is not installed on

the PC, download and install it by clicking on
Download the Windows 32-bit JRE installer
A new Java window appears
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 5 Console Java Window
Open the Preside NSP, enter your User ID and

Password, then click on Login.
See Figure 6.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 6 Login Window*
Figure 7 Warning
Select " Accept" on Warning window (Figure 7)
After " Authentication progress" a "Warning

window appears
Authentification progress
Initialization progress
Initialization Progress
Initializing
April 23, 2010
Method 30-6221
4.9 Opening the RNC Layout

The objective of this procedure is to open the layout of the concerned
RNC where the NodeB will be inserted in view mode in order to check
that there is no unexpected alarms on the equipment (RNC-CN, RNCIN, POC)
Procedure 3 Opening the Concerned Layout in View Mode (Page 1 of 2)
Step
1
Action
Observation
Once the NSP is open, click on File then Select

Network Layout. Refer to the Figure 8.
This action opens the Layout Selector, see

Figure 9.
Figure 8 NSP
File
Find
Select Network Layout...
Close Network Layout
Exit
In the Layout Selector, see Figure 9, select the

concerned layout and click on View.
The layout is now open in view mode, refer to

Figure 10.
Figure 9 Layout
Method 30-6221
April 23, 2010
Procedure 3 Opening the Concerned Layout in View Mode (Page 2 of 2)

Step
Action
Observation
Figure 10 Concerned Layout
In the navigator window, see Figure 10, double

click on the concerned layout.
This action opens the resource browser, see

Figure 11.
Figure 11 Resource Browser
April 23, 2010
Method 30-6221
The objective of this procedure is to check that there is no unexpected

alarms on the RNC.
Procedure 4 Show RNCs Alarms (Page 1 of 2)
Step
1
Action
Observation
In Resource Browser right click on the RNC

NE then select show Alarms (refer to Figure
12).
Figure 12 Show Alarms of the Concerned RNC
Alarm Manager window opens and it displays

all the alarms related to selected RNC
Refer to Figure 13
Method 30-6221
April 23, 2010
Procedure 4 Show RNCs Alarms (Page 2 of 2)

Step
Action
Figure 13 Alarm Manager Window
Observation
April 23, 2010
Method 30-6221
4.10 Import Network Configuration into WPS (optional)

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. WPS here is used as an example.
This is an optional, but recommended step. You can bypass it if you are
sure that your WPS view is synchronized with the network.
The XML file with the network configuration will be transfered on a
WPS PC workspace.
Refer to NN-20500-036 Alcatel-Lucent 9352 Provisioning System User Guide for more details during this procedure.
Procedure 5 Import Network Configuration into WPS (optional) (Page 1 of 5)
Step
1
Action
Observation
On WPS, open a new workspace. From the File menu, launch the Import and Export Wizard
Figure 14 WPS GUI
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 15 Import Snapshot
Select Import Snapshot (from the Local file

system or the Live server repository) and click on
Next
Refer to Figure 15
Select Replace initial snapshot and discard

existing workorders and click on Next
refer to Figure 16
Figure 16 Import Snapshot (local file system)
Click on Browse, Select the XML file

exported from the main server and Click Open
then Click on"Next"
Refer to Figure 17
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 17 File Selection
7
9
Click on Next. Select No, proceed without

saving and click on Start
Refer to Figure 18
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 18 Replace Initial Snapshot
After import completion, check the report and

close it.
Refer to Figure 19
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 19 Import Completion
Method 30-6221
April 23, 2010
4.11 New NodeB Creation with WPS

All design parameters regarding the new NodeB need to be provided by
the Network Designers.
Cell Planning Information
Topological Information
Under WPS, a workspace describing the current configuration of your
network is available. Templates files and RRM tree are uploaded.
The Workorder creation is explained as an example on "Appendix C - Workorder Creation for a new NodeB" on page 149
Note: for more detail about the WPS to use for WO creation, refer to
the paragraph "2.1 Required Documents".
April 23, 2010
Method 30-6221
4.12 Parenting a New NodeB*

The procedure explain how to parent a new NodeB to an existing RNC
with WPS.
Templated files and RRM tree are uploaded
Note: Make sure both RNC and NodeB have been created before user
starts the Iub wizard
Procedure 6 Parenting a new NodeB (Page 1 of 18)
Step
Action
On WPS, Create a new workorder and rename it

(for example: NodeB (NodeB Name) parenting
Observation
Refer to Figure 20
Figure 20 Create a New Workorder
In the network tree, select the NodeB and launch

the IuB wizard. From the IuB wizard task tree,
select the NodeB parenting task.
Refer to Figure 22
Method 30-6221
April 23, 2010

Step
Action
Figure 21 NodeB Parenting
Observation
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 22 NodeB Parenting
Parent NodeB to RNC
From the Status panel, run Parent NodeB to a

RNC
Refer to Figure 22
Fill in the parameters values then OK
Refer to Figure 23
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 23 Parent NodeB operation
The NodeB parenting task turn to green. Once

parented, the NodeB object is moved under the
RNC object
From the IuB wizard tree, select the Streams

definition task. From the panel, Add Streams
Refer to Figure 24
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 24 Streams Definition
Add Streams
From the panel, Add Streams.

Fill the parameters values then OK
Refer to Figure 25
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 25 Streams parameters
From the panel, select Configure Call

Admission Control
Refer to Figure 26
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 26 Call Admission Control
Call Admission Control
Fill in the parameters then OK
Refer to Figure 27
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 27 Call Admission Control parameters
10
Refer to Figure 28
From the IuB wizard tree, depending on the
hardware select the BTS PCM Configuration or
OneBTS Physical resource Configuration task.
From the BTS PCM Configuration or OneBTS
Physical resource Configuration panel, select
the Physical Resource Definition.
Figure 28 BTS PCM Configuration*
Number of PCM action
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 29 OneBTS Physical Resource Configuration *
This task is OK
. Select number of PCM
Number of PCM action
11
Fill in the parameters then OK. Number of PCM

range is 1 to 8.
The BTS PCM Configuration or OneBTS
Physical resource Configuration task turns to
green
12
From the IuB wizard tree, select the BTS ATM

Configuration or OneBTS ATM
Configuration task. From the panel, Configure
ATM Switching
Refer to Figure 30
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 30 BTS ATM Configuration
Configure ATM switching
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 31 OneBTS ATM Configuration
Configure ATM Switching
13
Select in and Apply the Apply Rule field if

relevant, fill in the parameters then OK
Refer to Figure 32
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 32 ATM Switching Parameters
14
The BTS ATM Configuration or OneBTS

ATM Configuration task turns to green
15
The BTSEquipment configuration or

OneBTSEquipment configuration task turns to
green
16
If any Physical resource to create on the INode,

select the Optical Connections Configuration
Sub-task. From the Optical Connections
Configuration panel, run Create a new Optical
Connection.
Refer to Figure 33
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 33 Optical Connection Configuration*
Create a new optical connection
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 34 Optical Connections Configuration *
17
Fill the parameters then OK
18
To configure ATM on the INode, select the

Switching Configuration sub-task. From the
Switching Configuration panel, run Configure
Iub ATM Switching.
Refer to Figure 35
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 35 Iub ATM Switching Configuration
19
the Switching Configuration sub-task turns to

green
20
If needed from the Iub Wizard task tree, select

the Aggregation Point Definition task. From the
panel, run Create an Aggregation Point
Refer to Figure 36
Note: Aggregation Point task gets created

and becomes green after Parent NodeB to a
RNC operation.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 36 Aggregation Point
Aggregation
Point
21
Fill in the IP Address and the Subnet Mask and

then OK
22
If any DHCP to define, select the DHCP

Configuration sub-task. From the panel, run
Configure relays to DHCP servers.
Refer to Figure 37
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 37 DHCP Configuration
23
Fill the number of DHCP servers then click the

Number of DHCP servers fiels in order to
display the DHCP Servers. Fill in the
parameters then OK.
24
From the IuB wizard tree, select the NodeB IP

Subnet Selection sub-task. From the panel, run
Select an IP Subnet
Note: If NodeB Version > = UA06.0, this task

is not available.
25
Fill the parameters then OK. Close the Iub

wizard. The NodeB object appears under the
parenting RNC
Refer to Figure 38
Method 30-6221
April 23, 2010

Step
Action
Figure 38 NodeB parented
Observation
April 23, 2010
Method 30-6221
4.13 Export Workorder

This procedure explain how to generate the XML file, which describe
only the modifed NEs between the initial and final network
configuration.
To have the new NodeB parented with RNC 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
Procedure 7 Export Workorder (Page 1 of 2)
Step
Action
On WPS, Select Workorders tab then select

Workorders folder from Workspace tree then
fromWorkorders Menu select Merge Network
Changes
Observation
Refer to Figure 39
Figure 39 Merge Network
Select an option to save your Workspace, if

needed enter a new Workspace name, and click
on Run
Refer to Figure 40
Method 30-6221
April 23, 2010
Procedure 7 Export Workorder (Page 2 of 2)

Step
Action
Figure 40 Workspace Name
Close the report window and go to the

Workspace Area
In the Workorders folder, select the "Merge"

Workorder, right click and click on "Export
Workorder .." (choose "on local file system" or
on "live server repository")
Enter a <Filename>, select a <Result Folder>

and click on Save.
Close the report window
Then the <Result Folder> contains the
Workorder file named <Filename>.xwo which
describes the NodeB to add.
Observation
April 23, 2010
Method 30-6221
4.14 Pre Checks before Activation

This procdure aims at verifying there is no impacting alarms on the
OMC and on the RNC.
Perform an Audit on the impacted RNC.
Procedure 8 Pre Checks before Activation (Page 1 of 2)
Step
Action
On the NSP GUI, you can verify there is no

impacted alarm in the Network
For that, you can refer to the Procedure 4

"Show RNCs Alarms" on page 29
If necessary, you can perform an Audit on the

impacted RNC.
Open the Audit Command window from the
contextuel menu (right click on an NE)
Configuration --> MIB --> Audit
Observation
Figure 41 Configuration - MIB - Audit
The Audit action window appears
Refer to Figure 42
Figure 42 Audit Action
Method 30-6221
April 23, 2010
Procedure 8 Pre Checks before Activation (Page 2 of 2)

Step
5
Action
Observation
Click the Audit Button. After the audit process

starts, The Command Manager window
appears. This window displays the name of the
NE being audited and the audit progress. After
the command has completed, the command
results are available under the Details Tab.
Refer to Figure 43
Figure 43 Command Manager
Details Tab
There will be also a link to the Audit Report

Window*. The Audit Report for NE display
about the sucessfully audit .
April 23, 2010
Method 30-6221
4.15 Session Creation for NodeB Activation

The objective of this procedure is to create on NSP the Session for the
NodeB in order to activate the NE NodeB on the RNC layout.
Ensure first the NodeB has been correctly commissioned with IM
24-6253 Alcatel-Lucent NodeB Commissioning Procedure.
Ensure the Workorder made during WPS Session has been transfered to
one <Result_Folder> located on the Main Server directory.
WARNING
In case of first NodeB Integration after the RNC Integration (First NodeB Integration not done at the same time
as the RNC one), a build of the RNC has to be relaunched
once the NodeB integration is finished to enable IuB CP &
CCP
Procedure 9 NodeB Session (Page 1 of 12)

Step
Action
Observation
On the NSP menu, open a session manager with

the menu Configuration -- Session Manager
and Create New Session
The following window open. Refer to Figure

44
Figure 44 Session Creation
Click on Create new session button
In the Create Session window, Enter A Session

Name
Method 30-6221
April 23, 2010

Step
Action
Expand cmXML Tree and select the workorder

you want to import
Click Add to list button then selected workorder
will appear in right window
Click Next, it opens an Excluded Nodes window
this displays the list of impacted nodes, dont
exclude any node.
Observation
Refer to Figure 45 and Figure 46
Note: This WO has been placed on the

result folder in /opt/nortel/data/cmXML/
operatorfolder/file.xwo before this
procedure
Note: The Workorders generated by WPS
are no more loaded by a XML import menu,
but loaded during a session created using the
Activation Session Manager
Figure 45 Workorder to Open
April 23, 2010
Method 30-6221

Step
4
Action
Click Launch in Excluded Nodes window this
opens a new window which will have three
(Creation for Session Name, Summary for
Session Name and Actions for Session Name)
sections.
Creation for Session Name section will show
the Status of importing workorder.
Observation
Refer to Figure 46
Figure 46 Session Creation
Expand the Summary for Session Name to

check the Activation Status and Activation
Type of the nodes.
Refer to Figure 47
Status of BTSEquipments/xxx should be

"Validated",
Status of RNC/yyy should be "Validated",
Status of RNC/xxx RNCEquipment/0 INode/
xxx should be "Loaded" and
Status of Site/yyy should be "Released"
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 47 Summary for Session
Expand the Actions for Session Name and select

RNC/xxx RNCEquipment/0 INode/xxx node
and click Launch to execute Validation task on
it.
Make sure Validation task is successfully
completed.
Refer to Figure 48
Refer to Figure 49
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 48 Validation Task
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 49 Validation Status
Click Launch to execute Preactivation task on

BTSEquipments/xxx node
select BTSEquipments/xxx node and click
Launch to execute Validation task on it
Refer to Figure 50
Make sure Preactivation task is successfully

completed
Refer to Figure 51
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 50 Pre Activate Task
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 51 Pre Activate Status
Select all RNC/yyy, RNC/xxx RNCEquipment/ Refer to Figure 52

0 INode/xxx and BTSEquipments/xxx nodes
and click Launch to execute Activation task on Note: This action ensure the Semantic
Checks and the MIB building
it
Make sure Activation task on each node is
Refer to Figure 53
successfully completed
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 52 Activation Task
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 53 Activation Status
During this action , the Command Manager

could display the course of operations
Refer to Figure 54
April 23, 2010
Method 30-6221

Step
Action
Observation
10
When all tasks are completed, click on

Summary for Session Name to check that all
the impacted nodes are in Released state
Method 30-6221
April 23, 2010

Step
Action
Figure 55 Release Status
Observation
April 23, 2010
Method 30-6221
4.16 Open Link of each NEs and build the Equipment

The BTS should be running with the right software version. Otherwise
it is needed to upgrade the software.Refer to "Node-B software
verification" on page 125 for Standard BTS
Note: for 9313 Micro and 9314 Pico:
Refer to NN-20500-057 (Alcatel-Lucent 9313 Micro Node B and 9314
Pico Node B - Local Maintenance Tool Manual)
And NN-20500-058 (Alcatel-Lucent 9313 Micro Node B and 9314 Pico
Node B - Operation and Maintenance Manual)
Note: Before user open the link between NE and OAM make sure user
need to put the NE in the layout because we just imported the
NodeB workorder in Section 4.10 without putting the NodeB in
the layout. Once NE is placed in layout then follow the steps
below.
The objective of this procedure is to change the NEs OAM Link
administrative state of the BTS in order to build it.
Procedure 10 Changing the NEs OAM Link Administrative State (Page 1 of 5)
Step
Action
Observation
Send a ping command to the BTS Equipment in

order to check the OAM Link
Use a telnet view with the @IP of the BTS

Equipment
If the ping respond:

Right click on the concerned NE. Select
Configuration then Set NEs OAM Link
Administrative State.
Refer to Figure 56
Method 30-6221
April 23, 2010

Step
Action
Figure 56 OAM Link Administrative State
Observation
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 57 OAM Link Administrative State (OneBTS)
Once the Set NEs OAM Link Administrative

State Action Window is open, select the BTS by
clicking on it and choose UNLOCK.
Refer to Figure 58. Check that the NEs status

passes from LOCKED to UNLOCKED.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 58 Set NEs OAM Link Administrative State Locked Status
Figure 59 Set NEs OAM Link Administrative State Locked Status (OneBTS)
The color of the concerned NE turns RED.

Check it in its layout.
Refer to Figure 60.
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 60 Set NEs OAM Link Administrative State Unlocked Status
Figure 61 Set NEs OAM Link Administrative State Unlocked Status (OneBTS)
After Equipment connection, the System will run

automatically the build operation. Wait until the
end of the build.
If build report is OK, The NodeB is activated

with unlocked OAM administrative state.
Method 30-6221
April 23, 2010
4.17 BTS Online Tests

The objective of this procedure is to check that there is no problem on
the FDD cells of the NodeB.
Procedure 11 Checking the BTS Cell(s) (Page 1 of 2)
Step
Action
Set the cursor on the RNC NE and click on the

right mouse button. Choose Show Alarms (refer
to Figure 62).
Observation
This action opens a new window, refer to
Figure 63.
Figure 62 RNC NE Show Alarms
In the alarm manager window, check that no

FDD cells are in alarms, see Figure 63.
April 23, 2010
Method 30-6221
Procedure 11 Checking the BTS Cell(s) (Page 2 of 2)

Step
Action
Observation
Figure 63 -Alarm Manager for FCC Cell Window
FDD Cell Component
Method 30-6221
April 23, 2010
The objective of this procedure is to test the redundancy of boards as

iCCM, i/TRM, i/CEM, xCEM.
Note: xCCM duplex mode is not supported in UA5.1.
Procedure 12 Board Redundancy Test (Optional) (Page 1 of 4)
Step
1
Action
Right click on the concerned BTS, select
Equipment Monitor (refer to Figure 64).
Observation
Figure 65.
Figure 64 Equipment Monitor Command

OneBTS
NodeB
In the Equipment Monitor window, check that

the board to reset is the active one: click on it and
check its standbyStatus is providingService
Refer to Figure 65.
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 65 BTS Equipment Monitor
Right click on the concerned board choose

Configuration then Reset Board.
Refer to Figure 66.

This action opens a new window for confirm
the reset , refer to Figure 67.
Method 30-6221
April 23, 2010

Step
Action
Figure 66 Reset Board
Figure 67 Reset Window
Observation
April 23, 2010
Method 30-6221

Step
Action
Observation
In the command manager window, check that the

reset action performs normally, then go back to
the equipment monitor window and check that
the state of each board has changed.
The active board becomes passive

(standbyStatus is HotStandby) and the passive
becomes the active one (standbyStatus is
providingService).
Method 30-6221
April 23, 2010
4.18 Communication Test

4.18.1 CS Call on a cell
The objective of this chapter is to check that the BTS is fully integrated
in the UTRAN, using Procedure 13 and Procedure 15 for each cell and
for each frequency to be tested.
IMPORTANT
For all these CS communication tests, the ON SITE
engineer should go away from the BTS site (100 meters if
possible), in the area covered by the sector to test (FDD
CELL).
The objective of this procedure is to lock all the untested cells in order
to make a CS call on the unlocked cells. These procedures should be
repeated for each cell and for each frequency to be tested.
IMPORTANT
The ON SITE engineer should make one call per
frequency to the OMC-B via the PSTN for each sector to
be tested. For example, a total of 6 calls for a BTS in
STSR-1 radio configuration with 2 frequencies.
Procedure 13 Locking the Untested Cell(s) (Page 1 of 3)

Step
Action
Observation
Check that the ON SITE engineer is well

positioned in the area covered by the sector to
test.
Refer to Table 8 "Antennae Positions" on

page 161 for the azimuth of the concerned
sector.
Lock the cells that are not tested. Right click on

the concerned RNC, select Equipment Monitor
(refer to Figure 68).
The equipment appears in the Layout ( refer to

Figure 69).
April 23, 2010
Method 30-6221

Step
Action
In the RNC equipment monitor (see Figure

69), click on the concerned NodeB , then on the
concerned FDDCell.
Right click on FDDcell and select
Configuration, then Set Administrative State.
Observation
Figure 70.
Figure 69 FDD Cells Set Administrative State
The Set NEs OAM Link Administrative State

Action Window window appears, shows
selected FDDCell in an UNLOCKED state
(refer to Figure 70). Select the object by clicking
on it and choose Lock.
Refer to Figure 71.

Check that the object state goes from
UNLOCKED to LOCKED.
Method 30-6221
April 23, 2010

Step
Action
Figure 70 FDD Cell Administrative State
The lock command opens the Command

Manager window. In the command manager,
click on logs and check that all the tasks perform
normally.
Observation
April 23, 2010
Method 30-6221
The objective of this procedure is to make a CS call on the unlocked

cells.
Procedure 14 CS Call on the Unlocked Cell
Step
Action
Observation
The On-site engineer is well positioned in the

area covered by the sector to test. All the
untested cells are locked.

sector.
Once the untested cells are locked, the On-site

engineer should make one call to the OMC via
the PSTN using the UMTS mobile.
Refer to Figure 72. In our example, the FDD

CELL 1 is unlocked, the FDD CELL 0 and 2
are locked.
Once the call has been performed on the

unlocked cell, ask the On-site engineer to move
to another area in order to test another sector.
Repeat Procedure 13 and Procedure 15, for each

cell to be tested and for each frequency.
Once the test is finished, unlock all the

concerned FDD cells.
Once all the sectors and frequencies have been

tested, note the results in Table 7
"Communication Test" on page 161.
Figure 72 Communication Test
FDD CELL 0
LOCKED
FDD CELL 2
LOCKED
FDD CELL 1
UNLOCKED
Method 30-6221
April 23, 2010
4.18.2 Video Streaming Test
IMPORTANT
The video streaming test is recommended to be done
only on the first cell of a given RNC. Once a video call has
been verified on a given RNC, it validates the function of
all its other cells located on the other BTSs.
The objective of these procedures is to lock all the untested cells in order
to make a video call on the unlocked cell(s).
Procedure 15 Locking the Untested Cell(s) (Optional) (Page 1 of 2)
Step
Action
Observation
Check that the 2 site engineers are well

test.

sector.
Lock the cell(s) that are not tested. Right click on

Refer to Figure 73.
The equipment appears in the Layout.

Refer to Figure 74.
In the RNC equipment monitor , click on

NodeB, then on the concerned FDDCell.
Right click on FDDCell and select
This action opens a new window

Refer to Figure 75.
April 23, 2010
Method 30-6221
Procedure 15 Locking the Untested Cell(s) (Optional) (Page 2 of 2)

Step
Action
Observation
Figure 74 FDD Cell Set Administrative State


UNLOCKED to LOCKED.
Figure 75 FDD Cell Set Administrative State
Method 30-6221
April 23, 2010
The objective of this procedure is to make a video call between the 2

mobiles located on the unlocked cell(s).
Procedure 16 Video Call on the Unlocked Cell (Optional)
Step
Action
Observation
The 2 site engineers are well positioned in the

area covered by the sector to test. All the
untested cells are locked.
Refer to Figure 76.

sector.
Once the untested cells are locked, one engineer

should call the other via a video call.
The video call quality is evaluated on both

sides.
Figure 76 Video Call Test
FDD Cell 2
April 23, 2010
Method 30-6221
4.18.3 PS Communication Test
IMPORTANT
The PS tests (ping GGSN and files transfer) are
recommended to be done only on the first cell of a given
RNC. Once a PS call has been verified on a given RNC, it
validates the PS function of all its other cells located on
the other BTSs. Consequently, this test is not required
systematically: time consuming and require a PC on site.
The objective of this procedure is to Lock all the untested cells. The
objective of this procedure is to launch a dial-up connection
Step
Action
Observation
Check that the ON SITE engineer is well

test.

sector.
Lock the cells that are not tested. Right click on

Refer to Figure 77.
The equipment appears in the Layout.

Refer to Figure 78.
In the equipment monitor, click on NodeB, then

on the concerned FDDCell.
Right click on FDDCell and select
This action opens a new window.

Refer to Figure 79.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 78 FDD_Cell_Set_Administrative_State


UNLOCKED to LOCKED.
Figure 79 FDD Cell Administrative State
April 23, 2010
Method 30-6221
IMPORTANT
The dial-up connection should be configured and its
parameters checked using the Procedure 31 "Setup the
Dial-up Networking (Optional)" on page 141 and
Procedure 32 "Check the Dial-up Properties (Optional)"
on page 145.
Procedure 18 Dial-up Connection

Step
Action
Observation
Open the dial-up connection window (see Figure

80) , once the dial-up connection window is
open, enter the password and click on Dial.
This action opens a connection between the PC

and the UTRAN. The mobile is now used as a
modem.
Figure 80 Dial-up Connection
Method 30-6221
April 23, 2010
The objective of this procedure is to check that the network sent a

dedicated IP address.
Procedure 19 IP Address Allocation (Page 1 of 2)
Step
Action
Observation
Click on Start, then Run. In the Run window,

type cmd and OK to open the command prompt
window and type ipconfig.exe inside this one
Refer to Figure 81.

Refer to Figure 82.
Figure 81 Run Window
cmd
Check that the UTRAN has allocated an IP

address number.
It validates the PDP context activation.
April 23, 2010
Method 30-6221
Procedure 19 IP Address Allocation (Page 2 of 2)

Step
Action
Observation
Figure 82 IP address Allocation
Method 30-6221
April 23, 2010
The objective of this procedure is to validate the PS network

connectivity from the laptop to the GGSN.
IMPORTANT
The ON SITE engineer should only execute one GGSN
ping per RNC located in the UTRAN.
Procedure 20 Ping the GGSN (Page 1 of 3)

Step
Action
Observation
The On-site engineer is well positioned in the

area covered by the sector to test.
The On-site engineer brings the dial up

connection using the Figure 80 .
Once the negotiation is over (it can take around

one minute), the connection should be
established between the PC (connected to the
UMTS mobile) and the UMTS network.
Once the call has been established, the on-site

engineer should ping the GGSN via its PC.
In our example, the GGSN IP address is

47.164.96.112 .
Refer to Figure 83.
Figure 83 Ping Command
The ping Test between the PC and the GGSN

should be OK. This ping test is sufficient to
validate the PS function.
Each ping command should return with a
message indicating a time value in "ms" and a
TTL value.
Once the Ping has been completed, note the

results in Table 7 "Communication Test" on
page 161.
Refer to Figure 84
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 84 Ping Message Validated
Figure 85 Ping Message Not Validated
Method 30-6221
April 23, 2010

Step
Action
Figure 86 Ping Way or PS Network Path
Observation
April 23, 2010
Method 30-6221
Note: All the following procedures are optional and dedicated for
tests or check of UTRAN configuration:
Please find hereafter the optional procedures list:
Download and transfer files via a FTP session:
Procedure 21 , "Open a FTP Session (Optional)," on page 98
Call Trace Sessions:
Procedure 22 , "Call Trace Configuration Wizard (optional),"
on page 101
Procedure 23 , "Creation of a Trace Session Template
(optional)," on page 112
Procedure 24 , "Call Trace Deletion (optional)," on page 118
Network Layout Operations (Creation, Edition, Visualization):
Procedure 25 , "Layout Creation (Optional)," on page 119
Procedure 26 , "Opening a Layout in Edit Mode," on page 120
Procedure 27 , "Opening the Layout in View Mode," on page
123
Node-B software verification before network integration :
NodeB Serial Number Exchange:
Procedure 28 , "Retrieve and Change the BTS NeId (Optional),"
on page 126
DC/DC Converter Alarms Integration:
Procedure 29 , "DC/DC Converter Alarm Integration
(Optional)," on page 130
9326 d2U V2 in a small or Medium Alarms Integration:
Procedure 30 , "9326 d2U V2 in a Small or Medium Alarms
Integration (Optional)," on page 134
Method 30-6221
April 23, 2010
4.19 Open for a FTP Session

The objective of this procedure is to download and to send files via a
FTP Session in order to validate a transfer file on the uplink and
downlink channels of the PS way.
IMPORTANT
The ON SITE engineer should make only one uplink and
downlink file transfer per RNC located in the UTRAN.
IMPORTANT
The FTP server should be installed and operational.
IMPORTANT
The Sim card should be declared in the HLR, it is
preferable that the SIM card have all the services
declared.
Procedure 21 Open a FTP Session (Optional) (Page 1 of 3)

Step
Action
On the test PC, type Start then Run (see Figure

87 ), this action opens the Figure 88, type the
command cmd
Observation
Refer to the Figure 88.
Figure 87 Cmd Command
Once the window is open, ping the FTP server,

Type Ping (IP address of FTP server)
The FTP server should be reach via a ping

session.
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 88 FTP Server
Once the FTP server was pinged, open a FTP

session on it, type: ftp (IP address of FTP
server), then once connected enter your login
and password.
Once you are logged in, type the following
command: dir
Refer to Figure 89.
Figure 89 FTP Connection
Download a concerned file type: hash, then get

name of file.
Ensure downlink rate is within expected range.

Refer to Figure 90.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 90 Downlink Transfer
Transfer a concerned file, type the following

command: put name of file.
Refer to Figure 91.
Ensure uplink rate is within expected range.
Figure 91 Uplink Transfer
Once the transfer file have been completed, note

the results in Table 7 "Communication Test"
on page 161 and close the window.
Refer to 5.4 "Appendix D - Report Sheet" on

page 161.
April 23, 2010
Method 30-6221
4.20 Call Trace Configuration (Optional)

The aim of this procedure is to launch the Call Trace Wizard menu from
the NSP and to to manage call trace session or to manage a template
trace sesion.
This feature described below has to be run with UTRAN UA06.0 and
OAM 06.0.
4.20.1 Call Trace Session configuration
The aim of this procedure is to launch the Call Trace Configuration
Wizard for describe the Call parameters.
Procedure 22 Call Trace Configuration Wizard (optional) (Page 1 of 12)
Step
1
Action
You can Launch the Call Trace Wizard
application from the performance menu of the
NSP main window (Performance/Radio
Access/Call Trace Configuration Wizard)
Observation
Refer to Figure 92
Figure 92 Call Trace Configuration Wizard command
The Call Trace Configuration Wizard allows

user to manage the following Trace Sessions:
Refer to Figure 93
Manage the Call Trace Session

Manage the Trace Session Template
Click Next
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 93 Call Trace Configuration Wizard window
Select Manage the Call Trace Session then

click Next
Refer to Figure 94
Figure 94 Manage the Call Trace Session
Select Create Call Trace Sessions then click

Next
Refer Figure 95
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 95 Create Call Trace
The next step will open the session window
Refer to Figure 96
Figure 96 Call Trace Access Session
Select either Create one or more Access

sessions on a single RNC or Create single
access session on one or more RNCs option.
Refer to Figure 97
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 97 Creation type
Click Next. It opens Select one RNC and set

NBAP Dedicated Measurement parameters
window
Refer to Figure 98
Figure 98 RNC and NBAP Parameters
Select the Equipment identification (RNC to

trace) and set the value for NBAP parameters:
It must be comprised between 500 and 10000
It must be a multiplier of 500
Refer to Figure 98
The Next button opens Identify mobiles and set

sessions' parameters window
Refer to Figure 99
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 99 Mobile identification
10
For IMSI mobile identification, enter the digits

numbers.
Then for the session parameters, follow the
recommendations below:
Note: Once all the parameters are

described , click the Add button, then the
mobile identification and session parameters
will be displayed on the upper side of the
window . Refer to Figure 101
Session Template: Select a session (default is

troubleshooting)
User Label: enter a unique label
Duration: enter a session duration in mn
Session note: enter additional information
about the session.
Start Time: enter the lapse of time (in mn)
between the session creation and its first
activation.
File upload size: enter the maximum size of
the trace file (max 1024)
File upload period: enter the lapse of time
before the trace file is closed and made
available.
Click the Add button
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 100 Mobiles Indentified
11
The next button displays the summary

information
Refer to Figure 101
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 101 Summary information*
12
Then click on create button

You will get the following window if the creation
is successful
Refer to Figure 102
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 102 Trace session creation successful*
13
The command manager window tell you the

exact status of the call trace.
Refer to Figure 103
Once the Trace session is create successfully,

please use the Session Manager to activate it.
Refer to Step 16
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 103 Command Manager*
14
The successfully operation is displayed in the

following window
Refer to Figure 104
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 104 Call Trace Operation Successful*
15
Once you have closed the wizard session, the

calls could be launched by the site technician and
he could refer to 4.18 "Communication Test"
on page 82 with the different calls type (CS, PS,
Video)
Note: You can create a template for

your trace session. That will permit to
another operator to understand more
easily the session. Refer to next
Procedure 23 , "Creation of a Trace
Session Template (optional)," on
page 112
16
The Session Manager will help you for manage

the Call Trace Session. The Action Menu allow
you to activate the session.
Refer to Figure 105 and Figure 106
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 105 Call Trace Session Creation
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 106 Session Manager for Call Trace
17
Once a call is launched, a call trace file is

created.
4.20.2 Trace Session Template

The aim of this procedure is to create a template for the call trace session
Procedure 23 Creation of a Trace Session Template (optional) (Page 1 of 6)
Step
Action
On the Figure 94 from the Procedure 22, Call

Trace Configuration Wizard (optional)
above, you can create a Trace Session Template
by the Manage Trace Session Template item
The next button enable the following window
Observation
Refer to Figure 107
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 107 Creation of Trace Session Template
Click the next button for start the Trace Session

Template creation. A window appears with
"Trace Session Template parameters fields"
Refer to Figure 108
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 108 Trace Session Template Parameters*
Enter a unique name for the Template Name.

Chooze the Mode List and the Trace Record
List.
Regarding the information you have entered, the

next window display the summary
Refer to Figure 109
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 109 Summary of Template Information*
The Create button display the following window
Refer to Figure 110 for acknowledge the

successful
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 110 Trace Session Template Creation*
Click Finish to validate the operation
Refer to Figure 111
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 111 Successful Operation*
The template has been created, click on Close

button
Method 30-6221
April 23, 2010
4.20.3 Call Trace Deletion

The aim of this procedure is to delete an existing call trace session .
Procedure 24 Call Trace Deletion (optional)
Step
Action
Observation
From the Menu Performance/Radio Access,

Launch the Call Trace Configuration Wizard
Refer to Figure 92 "Call Trace

Configuration Wizard command" on page
101
Click on Next two times and select Delete Call

Trace Session
Refer to Figure 95 "Create Call Trace" on

page 103
Click on Next and a box appears with all Call

Trace Sessions created on this RNC. Click on
the one you want to delete and click on Next
Click on Delete
April 23, 2010
Method 30-6221
4.21 Layout Operations

4.21.1 Layout Creation (optional)
The objective of this procedure is to create a new layout in case the BTS
layout is different from the RNC one.
Procedure 25 Layout Creation (Optional) (Page 1 of 2)
Step
Action
Once the Preside NSP is open, click on File then

Select Network Layout. Refer to the Figure
112.
Observation
This action opens the Layout Selector in
Figure 113.
Figure 112 NSP View
In the Figure 113, click on layout management

then New.
This action opens a new window. Refer to

Figure 114
Figure 113 Layout Selector
Enter the layout name, then click on OK.
The layout is now created.
Figure 114 Input Window
Method 30-6221
April 23, 2010
Procedure 25 Layout Creation (Optional) (Page 2 of 2)

Step
4
Action
Observation
The new layout appears in the Layout selector

window (refer to Figure 115).
Figure 115 Layout Selector
4.21.2 Layout Edition

The objective of this procedure is to open the new or existing layout in
edit mode in order to move the concerned BTS(s) inside it.
Procedure 26 Opening a Layout in Edit Mode (Page 1 of 3)
Step
Action
In the preside window, click on File then click on

Select Network Layout (refer to Figure 116).
Observation
Figure 117.
Figure 116 -NSP View
In Figure 117, select the concerned layout, then

click on Edit.
This action opens the navigator window. Refer

to Figure 118.
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 117 New Layout
In the navigator window, double click on the

concerned layout (see Figure 118).
The layout is now opened in edit mode, refer to

Figure 119.
Figure 118 Navigator Window
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 119 Edit Mode
April 23, 2010
Method 30-6221
4.21.3 Layout in view mode

The objective of this procedure is to open the concerned layout in view
mode in order to operate the concerned BTS.
Procedure 27 Opening the Layout in View Mode (Page 1 of 2)
Step
1
Action
In the NSP window, click on File then click on
Select Network Layout (refer to Figure 120).
Observation
Figure 121.
Figure 120 NSP View
In Figure 121, select the concerned layout, then

click on View.
This action opens the navigator window. Refer

to Figure 122.
Figure 121 New Layout
Method 30-6221
April 23, 2010
Procedure 27 Opening the Layout in View Mode (Page 2 of 2)

Step
Action
Observation
Figure 122 Navigator Window
In the navigator window, double click on the

concerned layout (see Figure 122).
The layout is now open in view mode (see

Figure 123).
Figure 123 View Mode
April 23, 2010
Method 30-6221
4.22 Node-B software verification

Important: Regarding the OAM version, it is mandatory to verify the
Node-B software release version.
If the Node-B software version is different that the SRS one, the NodeB software upgrade should be done.
Method 30-6221
April 23, 2010
4.23 BTS NeId exchange (optional)

The objective of this procedure is to retrieve and change the BTS NeID
(ex serial number) if the color of the concerned NE never becomes RED
during the previous Procedure 10 "Changing the NEs OAM Link
Administrative State" on page 71.
CAUTION/WARNING:
The Login "nodeb" and the password "nodeblnx" will be

used during the TIL connection on the xCCM.
Procedure 28 Retrieve and Change the BTS NeId (Optional) (Page 1 of 4)
Step
1
Action
Connect to the BTS via TIL
Start your web browser.
In the URL field of your web browser,
Strike the BTS IP@
>http://BTS IP@/til/index.xml
Observation
Check if the NeId (Serial number) of the BTS
and the NEid in the OAM database are the
same.
Note: TIL connection on a xCCM (not builded) use the login "nodeb" and the password
"nodeblnx"
Note: The TIL password could be changed if the nodeB is builded (refer to the manual
"NN-10300-031 Alcatel-Lucent 9353 Management System Security Overview")
2
Check in the main window BTS serial number

which is displayed on the bottom of the page.
Refer to Figure 124
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 124 Main TIL Window of the BTS (example)
xxx xxx
Other manner: (Optional)

Connect to the BTS by telnet command
>telnet @Ip of nodeB
>$$$
>emo
>data
>I2M
>sim
Retrieve NEid from the NSP

Open object Editor for the BTSEquipment
Refer to Figure 125.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 125 Object Editor
Check that NEid and serial number are the same,

if not follow next step to upgrade NEid.
Enter the right number in the details for NEid,

apply the type offline,
press Set
and Apply all changes.
Refer to Figure 126
April 23, 2010
Method 30-6221

Step
Action
Observation
If the BTS is still BLUE, contact your next level

support for help.
Method 30-6221
April 23, 2010
4.24 DC/DC Converter Alarm Integration

This procedure applies only in case the iBTS is equipped with a +24 V
to -48 VDC external converter. The objective of this procedure is to
describe the way to set the DC/DC converter alarm in the OMC-B.
Procedure 29 DC/DC Converter Alarm Integration (Optional) (Page 1 of 4)
Step
1
Action
Right click on the concerned BTS and select
Equipment Monitor.
Observation
Figure 127 Equipment Monitor
In the Equipment Monitor window, click on

ExternalAlarmMappingTable, 0 in order to
open its sub-object.
Figure 128 External Alarm Mapping Table
Select ExternalAlarmMappingTableEntry, 9,
click right on it, select Configuration, Object
Editor.
Figure 129 External Alarm Mapping Table Entry
April 23, 2010
Method 30-6221

Step
Action
In the object editor window, set the field alarm

Message at "+24 V DC/DC Converter Alarm =
INPUT +24V DC Fault. Click on Set then Apply
All Changes.
Observation
Repeat the same operations on:

ExternalAlarmMappingTableEntry, 10, set
the field alarm Message at "+24 V DC/DC
Converter Alarm = OUTPUT -55V DC Fault.
Converter Alarm=2 or more than 2 converters
are fault.
Converter Alarm=Only 1 converter is fault.
Once these changes have been performed, go

back in the layout, right click on the concerned
BTS and choose Configuration then Object
Editor.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 131 Object Editor Command
In the object editor window, click on the

attribute: supervisedExternalAlarm. Set the
mask at: xxxxxxxx11110000xxxxxxxxxxxxxxxx.
Note: Where x= 0 or 1 depending of the

supervision.
Figure 132 Object Editor Window
In the object editor window (refer to Figure

132), click on Set then Apply All Changes.
This action opens the command manager, refer

to Refer to Figure 133.
April 23, 2010
Method 30-6221

Step
9
Action
Observation
In the command manager (see Figure 133),

check that the set online operation performs
normally.
Figure 133 Command Manager*
Method 30-6221
April 23, 2010
4.25 9326 d2U V2 in a Small or Medium S6 OD Alarms Integration

This procedure applies only in case of 9326 d2U V2 into the Small S6
or Medium Md6 OD. The objective of this procedure is to describe the
way to set the Small or Medium S6 OD alarm in the OMC-B.
Procedure 30 9326 d2U V2 in a Small or Medium Alarms Integration (Optional) (Page 1 of
6)
Step
1
Action
Right click on the concerned BTS and select
Equipment Monitor.
Observation
Figure 134 Equipment Monitor
In the Equipment Monitor window, click on

ExternalAlarm/0 in order to open its sub-object.
Figure 135 External Alarm Mapping Table
April 23, 2010
Method 30-6221

6)
Step
Action
Observation
According to the customer, the OMC can manage

several differents external alarms mapping.
Check the initial external alarm mapping table of
the customer before to attribute the 4 new
external alarms of the PSU to the free pairs of the
alarms cable.
If necessary reasign the alarm labelling from the
OMC according to the new mapping alarm table.
If the customer use less than 8 pairs refer to
Figure 136 to understand the External Alarms
Mapping.
If the customer use more than 8 pairs refer to
Figure 137 to understand the External Alarms
Mapping.
Figure 136 Customer External Alarms with less than 8 pairs used
Customer
Alarm DF
Port 2
9...16
Port 1
1...8
1...8
RUC
Internal PSU
GND
Alarms DF
Pin out
Port 2
AC Mains
Major Alarm PSU
Minor Alarm PSU
Door Alarm
Pairs
12345678
iEAM
PSU
Relay #
9
10
11
12
1
2
3
4
13
14
15
16
5
6
7
8
4 Alarms
PSU
Not used
with
short
circuit
Small or Medium PSU
Figure 137 Customer External Alarms with more than 8 pairs used (up to 12 available)
RUC
Customer
Alarm DF
Port 2
9...16
Port 1
1...8
1...8
12345678
Internal PSU
GND
Alarms DF
Pin out
Port 2
AC Mains
Major Alarm PSU
Minor Alarm PSU
Door Alarm
Pairs
12345678
iEAM
9...16
Warning: reasign the alarm
labelling from the OMC
according to this new
mapping alarm table
PSU
Relay #
9
10
11
12
1
2
3
4
13
14
15
16
5
6
7
8
4 Alarms
PSU
Additional External Alarms Cable (4 pairs maxi)

Small or Medium PSU
Method 30-6221
April 23, 2010

6)
Step
Action
Select ExternalAlarmMappingTableEntry, 9,
click right on it, select Configuration, Object
Editor.
Observation
Figure 138 External Alarm Mapping Table Entry
In Case of PSU used in a Small S6 Frame

5
In the object editor window, set the field alarm

Message at "Small S6 PSU Alarm => AC
Mains Alarm" Click on Set then Apply All
Changes.
April 23, 2010
Method 30-6221

6)
Step
6
Action
Observation

the field alarm Message at "Small S6 PSU
Alarm = MAJOR Alarm PSU."
Alarm = Minor Alarm PSU."
Alarm = Door Alarm."
and if DC surge Protection Box used:
Alarm = DC Surge Protection Box Failure
(RRH1 to RRH3)."
In Case of PSU used in a Medium Frame

7

the field alarm Message at "Medium PSU
Alarm = AC Mains Alarm PSU."
Alarm = MAJOR Alarm PSU."
Alarm = Minor Alarm PSU."
Alarm = Door Alarm."
and if DC surge Protection Box used:
(RRH1 to RRH3)."
(RRH4 to RRH6)."
Once these changes have been performed, go

back in the layout, right click on the concerned
BTS and choose Configuration then Object
Editor.
Method 30-6221
April 23, 2010

6)
Step
Action
Observation
Figure 140 Object Editor Command
In the object editor window, click on the

attribute: supervisedExternalAlarm. Set the
mask at:
xxxxIxxxxI1111I0000IxxxxIxxxxIxxxxIxxxx.
Note: Where x= 0 or 1 depending of

the supervision.
Figure 141 Object Editor Window
April 23, 2010
Method 30-6221

6)
Step
Action
10
In the object editor window (refer to Figure

132), click on Set then Apply All Changes.
11
In the command manager (see Figure 133),

check that the set online operation performs
normally.
Observation
This action opens the command manager, refer
to Refer to Figure 133.
Figure 142 Command Manager *
12
The PSU alarms can be tested to check if there no

issue connection up to the OMC according to the
following step
13
Ask to the OMC Operator or the Site Operator to

check with you that the correct alarm will be
updated on the OMC view:
First Alarm tested: "Door Alarm"
When you close and open the Small or Medium
door the "Medium PSU Alarm = Door
Alarm" must be appear on the OMC alarm
view.
Second Alarm tested: "Main AC power"
When you switch OFF the AC customer
Breaker dedicated to the Small or Medium, the
"Medium PSU Alarm = AC Mains Alarm
PSU" must be appear on the OMC alarm view.
14
Do not forget to switch ON the AC customer

breaker after the test.(10 min maxi)
Risk to do a complete discharge of the battery.
Method 30-6221
April 23, 2010
5.0 Appendix
5.1 Appendix A -- Glossary
Term
Definition
AN
PCM Access Node
CN
Control Node
IN
Interface Node
MDM
Multiservice Data Manager
MIB
Managed Information Base
NE
Network Element
OAM
Operation, Administration & Maintenance
SRS
Software Repository Service
STM-1
Synchronous Transfer Mode level 1 (SDH)
UTRAN
UMTS Terrestrial Radio Access Network
CCM
Core Control Module
CEM
Channel Element Module
iCEM
Channel Element Module
xCEM
Extended Channel Element Module
xCCM
Extended Core Control Module
April 23, 2010
Method 30-6221
5.2 Appendix B -- Dial-up Setup and Checks

IMPORTANT
The USB driver regarding the concerned mobile should
be already installed (refer to the mobile user guide).
The dedicated mobile should be started, connected to the
PC and configured in PS mode (refer to the mobile user
guide).
The objective of this procedure is to set up the dial-up networking. This

procedure applies for the first time dial-up.
Note: The figures might deviate slightly depending on which operating
system is used
Procedure 31 Setup the Dial-up Networking (Optional) (Page 1 of 4)
Step
1
Action
In Windows, create a new modem: click on
Start, Settings, Network and Dial-up
Connections, Make New Connection
Observation
This action opens the Network Wizard
Window.
Figure 143 New Connection
Method 30-6221
April 23, 2010

Step
2
Action
In the Wizard window, click on Next
Observation
Figure 144 Wizard Connection
In the Network Connection window, click on

Dial-up to private network, then click on Next

April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 145 Network Connection Type
In the Phone number window, enter the phone

number to dial, then click on Next.

Figure 146 Phone Number to Dial
In the Connection Availability window, click on

For all users, then click on Next.

Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 147 Connection Availability
In the Connection window, type the name

dedicated to the connection, then click on Finish.
Figure 148 Connection Window
April 23, 2010
Method 30-6221
The objective of this procedure is to check that the Dial-up parameters

are compliant with those expected.
Procedure 32 Check the Dial-up Properties (Optional) (Page 1 of 4)
Step
1
Action
Open the dial-up connection window, once the
dial -up connection window is open, click on
Properties, refer to Figure 149. In the General
field check that:
Observation
Once these parameters are checked, click on
the Options field. This action opens a new
window
The modem used (connect using field)

corresponds to the concerned mobile.
The dial string corresponds to the concerned
mobile.
Figure 149 Dial-up Properties: General
In the Options field (refer to Figure 150) check

that:
Dialing option is: display progress while
connecting.

the Security field, this action opens a new
window
The redialing options are:

Redial attempts: 3,
Time between redial attempts: 1 minute,
Idle time before hanging up: never.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 150 Dial-up Properties: Options
In the Security field (see Figure 151) check that

Security options are Typical recommended
settings and allow unsecured password.

the Networking field. This action opens a new
window
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 151 Dial-up Properties: Security
In the Networking field check that:

The Type of dial-up server is PPP windows
95/98/NT4/2000, internet,
Click on Setting and check that no PPP settings
fields are selected,
Check that the only allowed network protocol
is "TCP/IP",
Check the TCP/IP properties are: obtain an IP
and a DNS server addresses automatically.
Once these parameters are checked, click on OK.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 152 Dial-up Properties: Networking
The only allowed network protocol

is TCP/IP
April 23, 2010
Method 30-6221
5.3 Appendix C -- Workorder Creation for a new NodeB

The WPS tool has been launched and the network configuration has
been loaded
Note: This procedure is for example, for more detail refer to the NRP
documentation following this link:
https://wcdma-ll.app.alcatel-lucent.com/livelink/
livelink.exe?func=ll&objId=52478346&objAction=browse&sort=name&viewTy
pe=1
In case of remote cells, set the remote configuration parameter in the

Configure BtsEquipment window to RRH1 or RRH2.
RRH1 for remote cells with one frequency
RRH2 for remote cells with two frequency,
Procedure 33 NodeB Workorder Creation (Page 1 of 12)
Step
Action
Under WPS, create a new Workorder and name

it. (Ex: NodeB Name addition). Launch Apply .
Observation
Figure 153 Create a New Workorder
Method 30-6221
April 23, 2010

Step
Action
In the network area, from the root tree

"Network", launch the NodeB Wizard link.
From the NodeB Wizard task tree, select the BTS
Equipment Configuration or OneBTS
Equipment Configuration task according to the
need.
From the panel, Create a new BtsEquipment or
Create a new OneBTSEquipment according to
the need.
Observation
Refer to Figure 154
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 154 NodeB Wizard
Creation of new
OneBTS Equipmen
Creation of new
NodeB Equipment
Method 30-6221
April 23, 2010

Step
3
Action
The BTS Configuration equipment window
open.
Fill in the parameters values then OK.
Observation
Refer to Figure 155
OneBTS Creation Window

Or
NodeB Creation Window
April 23, 2010
Method 30-6221

Step
Action
Observation

Or
The Configure BTS Equipment operation is

now available. From the panel, select Configure
BtsCells. There must be at least one BTSCell per
BTSEquipment.
Refer to Figure 158
Method 30-6221
April 23, 2010

Step
Action
Observation

Or
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 158 BTS Equipment Operation Status Panel
Configure BTS Cells
The BTS Cells window open. Fill in the

parameters values then OK. The BTS
Equipment Configuration comes available and
turns to green.
Refer to Figure 159
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 159 OneBTS or NodeB Cells Parameters
The BTS Equipment Configuration comes

available and turns to green.
Refer to Figure 160
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 160 NodeB Configuration
NodeB Configuration task

7
From the NodeB wizard task tree, select the

NodeB Configuration task. From the panel,
select Create a new NodeB. Fill the parameters
then OK
Create a new NodeB

Refer to Figure 161
Figure 161 OneBTS Creation
Example with a OneBTS

8
The Define FddCell Radio Configuration

operation is available. From the panel, select
Define FddCell Radio Configuration. The
correspondant window open
Refer to Figure 162
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 162 FDD Cell Radio Configuration Window
Fill in the parameters then OK. Then the Define

FddCell Localization Configuration operation
is available. From the panel, select Define
FddCell Localization Configuration.The
Operation: Define FddCell Localization
Configuration window opens. Fill the
parameters values then OK.
Refer to Figure 163
Figure 163 FDD Cell Localization Configuration
10
From the panel, select Define FddCell

GaiCoord configuration.
The Operation: Define FddCell GaiCoord
configuration window opens.
Refer to Figure 164
April 23, 2010
Method 30-6221

Step
Action
Observation
Figure 164 Geographical Points
Geographical Points
11
Fill the Number of geographical points and

click the Number of geographical points field
in order to display the List of GaiCoord. Fill in
the parameters values then OK.
12
From the NodeB wizard task tree, select the

Channels Configuration sub-task.
Method 30-6221
April 23, 2010

Step
Action
Observation
Figure 165 NodeB Channel Configuration
13
From the panel, select Propagate Channels

Model To FddCells.
The Operation: Propagate Channels Model To
FddCells window opens.
14
Fill the parameters values then OK.

The NodeB Configuration task turn to green
15
Close the NodeB wizard.

The BTS Equipment and NodeB objects appears
in the Network tree.
16
Save the Workorder on your laptop or transfer it

to the XML directory on the main server
Refer to Figure 165
April 23, 2010
Method 30-6221
5.4 Appendix D - Report Sheet

The following parts must be filled by the coordinator before the site intervention.
Table 5 Required Documents
Document
Reference
NodeB Software Upgrade Procedure Using OAM 5.
Edition
411-8111-239
Table 6 BTS Parameters

BTS IP Address:........................
OMC-B IP address:...............................
Sub-network mask:..............................
Software upgrade on BTS:
Configuration:................................
Software version:..........................
Hardware reference:..........................
Yes
No
Table 7 Communication Test

Cells
Frequency A
Frequency B
Frequency C
Status (OK / NOK)
Table 8 Antennae Positions

Cell
Azimuth
Method 30-6221
April 23, 2010
The column "To apply" must be filled by the coordinator before the site intervention.
The columns "Ok" and "Nok" must be filled by the OMC operator during site intervention.
Table 9 Sequence of Operations
Step
Procedure
Condition
To
apply
Procedure 1 , "Hostname Setup

(Optional)," on page 21.
This procedure applies only

for the first time PC setting.
Procedure 2 , "Navigator Starting Up

Configuration in UA06," on page 23
NSP Startup
Procedure 3 , "Opening the Concerned

Layout in View Mode," on page 27
Verify the RNC Layout and

the Layout consistency
Procedure 4 , "Show RNCs Alarms," on

page 29
Procedure 5 , "Import Network

Configuration into WPS (optional)," on
page 31
Procedure 6 , "Parenting a new NodeB,"

on page 37
Procedure 7 , "Export Workorder," on

page 55
Procedure 8 , "Pre Checks before

Activation," on page 57
Procedure 9 , "NodeB Session," on page

59
10
Procedure 10 , "Changing the NEs

OAM Link Administrative State," on
page 71
11
Procedure 11 , "Checking the BTS

Cell(s)," on page 76
12
Procedure 12 , "Board Redundancy Test

13
Procedure 13 , "Locking the Untested

14
Procedure 14 , "CS Call on the Unlocked

Cell," on page 85
Communications Tests
15

Cell(s) (Optional)," on page 86
Sesson Manager for NodeB

Activation
Check of board redondancy
5
5
Ok
Nok
April 23, 2010
Method 30-6221

Step
Procedure
Condition
To
apply
16
Procedure 16 , "Video Call on the

Unlocked Cell (Optional)," on page 88
17

18
Procedure 18 , "Dial-up Connection," on

page 91
19
Procedure 19 , "IP Address Allocation,"

on page 92
20
Procedure 20 , "Ping the GGSN," on

page 94
21
Procedure 21 , "Open a FTP Session

22
Procedure 22 , "Call Trace

Configuration Wizard (optional)," on
page 101
23
Procedure 23 , "Creation of a Trace

Session Template (optional)," on page
112
24
Procedure 24 , "Call Trace Deletion

(optional)," on page 118
25
Procedure 25 , "Layout Creation

26
Procedure 26 , "Opening a Layout in

Edit Mode," on page 120
27
Procedure 27 , "Opening the Layout in

View Mode," on page 123
28
Procedure 28 , "Retrieve and Change the

BTS NeId (Optional)," on page 126
29
Procedure 29 , "DC/DC Converter

Alarm Integration (Optional)," on page
130
In case of +24 VDC to 48VDC converter.
30
Procedure 30 , "9326 d2U V2 in a Small

or Medium Alarms Integration
In case of 9326 d2U V2 in a

Small or Medium
31
Procedure 31 , "Setup the Dial-up

Networking (Optional)," on page 141
Ok
Nok
Method 30-6221
April 23, 2010

Step
Procedure
Condition
To
apply
32
Procedure 32 , "Check the Dial-up

Properties (Optional)," on page 145
33
Procedure 33 , "NodeB Workorder

Creation," on page 149
Ok
Nok
Comments:
Sign off:
OMC Technician
Coordinator
Company name
Functions
Name
Signature
Date
Last page
Customer
Representative

IM 30-6221-301 Alcatel-Lucent NodeB UA7.x Integration in An Existing Utran

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IM 30-6221-301 Alcatel-Lucent NodeB UA7.x Integration in An Existing Utran

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent NodeB UA07.

Installation Method 30-6221

April 23, 2010

UNCONTROLLED COPY: The master of this document is stored on an electronic

April 23, 2010

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 1

April 23, 2010

2 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN

April 23, 2010

Procedure 14 CS Call on the Unlocked Cell. . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

6.0 Last page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 3

4 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN

April 23, 2010

April 23, 2010

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 5

April 23, 2010

Figure 50 Pre Activate Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

6 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN

April 23, 2010

Figure 102 Trace session creation successful* . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 7

April 23, 2010

Figure 154 NodeB Wizard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN

April 23, 2010

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 9

April 23, 2010

1.0 General Information

10 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN

April 23, 2010

1.3 Reason for Reissue

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 11

April 23, 2010

2.0 .Material Requirements

12 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN

April 23, 2010

One of the following: (supported by OAM V7)

1 PC with VGA Monitor

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 13

April 23, 2010

Table 2 Hardware tools (Contd)

3G Mobile (for CS calls)

No other materials are required to perform this method.

2.4 Login/password Availability

14 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN

April 23, 2010

3.0 Precautions and Preparations

3.3 Check List

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 15

April 23, 2010

4.2 Alcatel-Lucent UTRAN

4.3 RNC Main Functions

4.4 W-NMS General principles

16 / Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN

April 23, 2010

viewing or editing. The Navigator window opens automatically when

4.5 WPS General Principles

Alcatel-Lucent NodeB UA07.x Integration in an Existing UTRAN / 17

April 23, 2010

Hostname Setup (Optional)

First Connection with laptop on the

How to Start the NSP