Alcatel-Lucent

INTEGRATION ENGINEERING HANDBOOK 521

WCDMA Node B (iBTS Global Markets)
Release LR13.3W
30-6-2014

Delivery Readiness Document

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
LEGAL NOTICE

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are
the property of their respective owners.

The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for
inaccuracies contained herein.

Copyright 2014 Alcatel-Lucent. All Rights Reserved.

This document contains proprietary/trade secret information which is the property of Alcatel-Lucent and must not be
made available to, or copied or used by anyone outside Alcatel-Lucent without its written authorization.

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section TOC

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Table of Contents

Release Date Section Title

Introduction
June, 30, 2014 Cover Cover
June, 30, 2014 TOC Table of Content
June, 30, 2014 001 Introduction
Commissioning
June, 14, 2013 301 Commissioning Planning
April, 30, 2013 302 Commissioning Procedure
April, 30, 2013 310 Commissioning Testing
June, 14, 2013 320 Node B RF path validation
December, 15, 2013 331 U2100 + U900 Daisy Chain Check Procedure
June, 14, 2013 399 Commissioning Test Records
Integration
June, 30, 2014 401 Integration Planning
April, 30, 2013 402 Integration into existing UTRAN
June, 30, 2014 410 Integration Testing
June, 30, 2014 411 RF Path Testing
June, 30, 2014 412 Ethernet OAM in the Node B Testing procedure
June, 30, 2014 413 NodeB Daisy Chain Remote Checking
December, 15, 2013 431 24 Cells and 12 Antenna Pairs Procedures
December, 15, 2013 432 Hosting 2 Node Bs WCDMA in one d4U Procedures
June, 30, 2014 433 External Alarm Logic Status Integration Procedures
June, 30, 2014 434 971x LR Cabinet Alarm Checking Configuration
June, 30, 2014 499 Node B Integration Test Records
Migration

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section TOC Table of Contents

December, 15, 2013 701 d2U/BBU to d4U migration procedure

December, 15, 2013 702 CCM-U board migration procedure
December, 15, 2013 703 CEM-U board migration procedure
December, 15, 2013 705 Single to Dual Node B Migration Procedures
June, 30, 2014 706 NodeB Daisy Chaining through the Node B
Multi-Technology Products Commissioning
June, 30, 2014 9xx Multi-Technology commissioning and integration procedures:
Refer to INTEGRATION ENGINEERING HANDBOOK 523-
Multi-Standard RF
Glossary
December, 15, 2013 Glossary Glossary

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 001

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Introduction

Table of Contents

General ............................................................................................................ 2
Covered Node B products ................................................................................... 2
Organization .................................................................................................. 2
Sections ........................................................................................................ 2
Chapter ........................................................................................................ 2
Numbering Format ........................................................................................... 2
Exclusions of operations covered ......................................................................... 3
Common Blocks .................................................................................................. 4
Release Notes ................................................................................................. 4
Download Information ....................................................................................... 4
Support Contact Information ............................................................................... 4
Naming conventions ......................................................................................... 5
Node B definition............................................................................................. 5
Node B Product Information ................................................................................. 6
Technical Product Documents ............................................................................. 6
Access to supporting documentation ..................................................................... 7
WCDMA Node B Installation Support ......................................................................... 8
Toll free Support ............................................................................................. 8
Laptop Support ............................................................................................... 8
Methods and Procedures Feedback ....................................................................... 8
Action Request (AR) ......................................................................................... 8
Handbook Location .............................................................................................. 9
General ........................................................................................................ 9
Access and download of the handbook ................................................................... 9
Access restrictions ........................................................................................... 9
Assisted IEH521 ............................................................................................... 9

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 001 Introduction

General

Covered Node B The detailed procedures of the IEH521 cover the deployment of WCDMA (global market)
products distributed Node B which consist of:
One digital unit
One or more RRHs
which may or may not be installed in dedicated cabinets.

Organization This handbook is divided into Chapters and Sections.

Sections A section contains

a set of procedures to perform a dedicated task with a clear end result
provides an overview and additional information about a set of tasks to be performed to get
to the required end result

Chapter Chapters are used to group together sections of a dedicated topic.

Example is: Integration planning, Integration, Integration testing

Numbering Each Section is numbered based on the Chapter if falls under. The numbering scheme of each
Format of the Chapters is shown in below table:

Chapter Series Chapter Title

000 Introduction
100 Test Equipment Description and Setup
***future***
200 Software Updates
***future***
300 Commissioning Procedures
400 Integration Procedures
500 Trouble Shooting
***future***
600 Growth / De-Growth
***future***
700 Migrations
900 Reference only: Moved to IEH523:
Multi-Technology Products procedures (MC-
TRX, MC-TRDU, MC-RRH)
Glossary Glossary

Each section number will reside within the numbering block of the Chapter to which it belongs.

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Introduction IEH 521, Section 001

Continued on next page

General, Continued

Exclusions of
operations
covered
IMPORTANT: IEH 521 does not cover some operational tasks during installation of
the WCDMA Node B:

Equipment Engineering
Site Engineering and Preparation
Physical Installation of Equipment

Guidelines and documents to support this operations are available and can be found under the
GPEC portal webpage:
https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 001 Introduction

Common Blocks

Release Notes The following table provides information about the IEH 521 history:

Version History
Version 1.0 Initial version (commissioning and integration only) for distributed
Node B (iBTS based) in support of Global Markets
June 2013 Updates to include
Node B RF path validation
December 2013 Updates to include
(aligned with LR13.1W features (U2100 + U900 Daisy Chain Check
LR13.1W) Procedure, 24 Cells and 12 Antenna Pairs Procedures, Hosting
2 Node Bs WCDMA in one d4U Procedures, Single to Dual
Node B Migration Procedures)
D2U/BBU to d4U migration
CCM-U board migration
CEM-U board migration
MC-TRX 2G/3G commissioning
V4.0 Addition of rf path testing from WMS
LR13.3W feature related updates
Ethernet OAM in the Node B Testing procedure
External Alarm Logic Status Integration Procedures
971x LR Cabinet Alarm Checking Configuration
NodeB Daisy Chaining through the Node B
NodeB Daisy Chain Remote Checking
Guidelines for assisted IEH521 (externally available version)

Download The entire IEH 521 can be accessed via the GPEC web portal on following address:
Information https://all1.na.alcatel-lucent.com/Teams/GCDNetworks/WirelessGPEC/default.aspx
The referenced documents can be obtained by going directly to Alcatel Lucent Product
Documentation website on following address: http://www.cic.lucent.com

Support For additional support, comments, feedback on this handbook you can access the Information
Contact Product Support web page at the following URL:
Information Alcatel-Lucent Values Your Comments
http://infodoc.alcatel-lucent.com/comments/

Select the Feedback link and language, enter the appropriate information in the form and
submit the form.

Continued on next page

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Introduction IEH 521, Section 001

Common Blocks, Continued

Naming The following product related naming conventions are used inside this document:
conventions

Product Related naming convention

d2U Digital unit (2 units high)
d4U Digital unit (4 units high)
9326 d2U d2U V1
9326 d2U V2 d2U V2
9926 BBU d2U V3
9926 DBS 4U d4U V3
RRH Remote Radio Head: means all types and frequency bands of
RRHs unless specifically stated differently.
MC-TRX Multi-Carrier TRX

NOTE: 9396 d2U and 9396 d4U are NOT supported by this IEH521

Node B Node B = digital unit with RRH(s) connected.

definition

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 001 Introduction

Node B Product Information

Technical The following table provides an overview to technical information about the Node B products:
Product
Documents
Product Doc # Doc Title
9926 - BBU (d2U V3) Alcatel-Lucent 9926 Base
Band Unit Node B for
NN-20500-283
WCDMA - Technical
Description
9926-d4U ALU 9926 DBS 4U -
3MN-01637-0004-DEZZA WCDMA - Technical
Description
9326d2U Alcatel-Lucent 9326 digital
NN-20500-108 2U Node B - Technical
Description
9326d2U V2 Alcatel-Lucent 9326 digital
NN-20500-203 2U V2 Node B - Technical
Description
9341 RRH 20W 2100MHz Alcatel-Lucent Remote
NN-20500-106 Radio Head 20W - 2100
MHz - Technical Description
9341 RRH 2x 40W 900MHz Alcatel-Lucent Remote
Radio Head 2X40W - 900
NN-20500-281
MHz for GSM and WCDMA -
Technical Description

Continued on next page

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Introduction IEH 521, Section 001

Node B Product Information, Continued

Technical
Product
Product Doc # Doc Title
Documents
(continued) 9341 RRH 40W
850 Alcatel-Lucent Remote
Radio Head 40W - 850,
AWS NN-20500-120
AWS, 1900, 2100 MHz -
1900 Technical Description
2100
9341RRH 60W
850 Alcatel-Lucent Remote
Radio Head 60W - 850, 900,
900 NN-20500-235
1900, 2100 MHz - Technical
1900 Description
2100
9341RRH 2x60W
850 ALU Remote Radio Head
NN-20500-307 2X60W - 850, 1900, 2100
1900 MHz - Technical Description
2100

Access to Access to all product related documents through GPEC portal:

supporting https://all1.na.alcatel-
documentation lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 001 Introduction

WCDMA Node B Installation Support

Toll free If technical assistance is required during integration of a WCDMA Node B, please contact
Support Product Technical Support hotline:

Outside USA https://support.alcatel-

lucent.com/portal/olcsHome.do

Country specific access details are available

from support website.
Inside USA 1-866-582-3688 (Prompt 1)

Laptop Support For technical assistance, please contact help desk:

Outside USA https://support.alcatel-

lucent.com/portal/olcsHome.do

Country specific access details are available

from support website.
Inside USA 1-888-443-4243 (US)

Methods and To facilitate feedback or change request:

Procedures As a workaround please contact the GPEC WCDMA IEH521 group by the following email
Feedback address: [email protected]
Your description of the problem should include:
Handbook number
Section number
Publish date
Page number
Figure or table
Short description of issue
Supporting information (if available) e.g. screen shot

Action Request Use of CARES tool is planned for the next release of this handbook
(AR)

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Introduction IEH 521, Section 001

Handbook Location

General Paper copies of the handbook cannot be ordered from CIC web site at current time.

Access and IEH521 can be downloaded from WCDMA delivery readiness portal:
download of the https://all1.na.alcatel-
handbook lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Access IEH521 is restricted to ALU internal and is secured through access restrictions:
restrictions Inside U.S.:
CIC Security Class Code D15: ALU INSTALL HANDBOOKS & CONTRACTS
For read access of the documents a permission has to be applied for per HRID
Outside U.S.:
CIC Security Class Code D15: ALU INSTALL HANDBOOKS & CONTRACTS
For read access of the documents a permission has to be applied for per HRID

Assisted IEH521 An externally available version of IEH521 can be made available on request.
Requests have to be directed to [email protected]

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 001 Introduction

This page intentionally left blank.

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 301

Jun 14, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Commissioning Planning

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation Access ...................................................................................... 5
Applicable IEH 521 Sections ................................................................................ 5
Applicable Methods Documents............................................................................ 6
Prerequisites ..................................................................................................... 7
Prerequisites .................................................................................................. 7
Node B Commissioning Flow Initial Preparation.......................................................... 8
Node B Commissioning flow diagram - for Initial Preparation for Commissioning ................ 8
Node B Commissioning Flow Software Downloading and Release Activation ....................... 9
Node B Commissioning Flow Diagram for Node B Software Downloading and Release
Activation...................................................................................................... 9
Node B Commissioning Flow Parameter Setting Node B .............................................. 10
Node B Commissioning Flow Diagram -Parameter Setting Node B................................. 10
Node B Commissioning Flow Test and Validation ...................................................... 11
Node B Commissioning Flow Diagram Node B Commissioning Test and Validation ............ 11
Commissioning Procedure Overview ....................................................................... 12
Reference of Commissioning Procedures Mandatory ............................................... 12
Reference of Commissioning Test Procedures ........................................................ 13
Commissioning Checklists .................................................................................... 14
Purpose ...................................................................................................... 14
Checklist Customization .................................................................................. 14
Remote Operations Checklist ............................................................................ 14
Remote Operations Checklist (continued) ............................................................. 15
Node B Form Parameters ..................................................................................... 16
General ...................................................................................................... 16
Node B Parameters Required prior to Node B Commissioning ..................................... 16
Node B BTS Parameters ................................................................................... 16

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B RRH Parameters................................................................................... 17

Node B Backhaul Parameters ............................................................................ 17
Node B PCM (E1) Parameters ............................................................................. 17
Node B PCM (T1) Parameters ............................................................................ 18
Node B PCM & IMA Parameters .......................................................................... 19
Node B Ethernet Parameters ............................................................................. 19
Node B ATM Parameters .................................................................................. 20
Node B IP Parameters ..................................................................................... 20
Node B Packaging Parameters and Configurations ...................................................... 21
BTS Packaging Parameters Cross-reference ........................................................... 21
BTS Packaging Parameters Cross-reference (continued) ............................................ 22
BTS Packaging Parameters Cross-reference (continued) (continued) ............................ 23
Node B RF Path Validation References .................................................................... 24
General ...................................................................................................... 24
Documentation Access .................................................................................... 24
Node B RF Path Validation Prerequisites .................................................................. 25
Prerequisites ................................................................................................ 25
Node B RF Path Validation Flow Initial Preparation ................................................... 26
Node B RF Path Validation flow diagram - Initial Preparation ..................................... 26
Node B RF Path Validation Flow Test, Measurement and Validation ............................... 27
Node B RF Path Validation flow diagram Test, Measurement and Validation ................. 27
Node B RF Path Validation Procedure Overview ......................................................... 28
Reference of Node B RF Path Validation Procedures ................................................ 28
Node B RF Path Validation Checklists ...................................................................... 29
Purpose ...................................................................................................... 29
Checklist Customization .................................................................................. 29
Remote Operations Checklist ............................................................................ 29
Node B RF Path Validation Form Parameters ............................................................. 31
General ...................................................................................................... 31
Node B RF Path Validation Form Parameters -Site Description .................................... 31
Node B RF Path Validation Form Parameters -Stakeholders Information ........................ 32
Node B RF Path Validation Form Parameters Antenna and TMA Frequency Band ............. 33
Node B RF Path Validation Form Parameters Antenna and TMA Manufacturer Specifications
................................................................................................................ 33
Node B RF Path Validation Form Parameters RF Cables Manufacturer Specifications ....... 34
Node B RF Path Validation Form Parameters Antenna and TMA Site Description ............. 35

List of Figures

Figure 1: Initial Preparation for the Commissioning ................................................................ 8

Figure 2: Software Downloading and Release Activation ........................................................... 9
Figure 3: Parameter Setting Node B ................................................................................. 10
Figure 4: Test and Validation ......................................................................................... 11
Figure 5: Global Antenna Link: Antenna, Feeder and Jumpers ................................................. 25
Figure 6: Initial Preparation of the Node B RF Path Validation ................................................. 26
Figure 7: Test, Measurement and Validation of the Node B RF Path Validation ............................. 27

2 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Commissioning ....................................... 5
Table 2: Applicable Methods Documents for IEH521 ................................................................ 6
Table 3: Operational Procedures for the Node B Commissioning ............................................... 12
Table 4: Test Procedures for the Node B Commissioning ........................................................ 13
Table 5: Sequence of Operations Used for the Node B Commissioning ........................................ 14
Table 6: Node B Parameters Required Prior to Node B Commissioning ........................................ 16
Table 7: Node B BTS Parameters ..................................................................................... 16
Table 8: Node B RRH Parameters ..................................................................................... 17
Table 9: Node B Backhaul Parameters ............................................................................... 17
Table 10: Node B PCM (E1) Parameters ............................................................................. 17
Table 11: Node B PCM (T1) Parameters ............................................................................. 18
Table 12: Node B PCM & IMA Parameters ........................................................................... 19
Table 13: Node B Ethernet Parameters.............................................................................. 19
Table 14: Node B ATM Parameters ................................................................................... 20
Table 15: Node B IP Parameters ...................................................................................... 20
Table 16: Node B Parameters: BTS Packaging ...................................................................... 21
Table 17: Test Procedures for the Node B RF Path Validation .................................................. 28
Table 18: Sequence of Operations Used for the Node B RF Path Validation .................................. 29
Table 19: Site Description ............................................................................................. 31
Table 20: Stakeholders ................................................................................................. 32
Table 21: UMTS Frequency Band...................................................................................... 33
Table 22: RF Modules Manufacturer Specifications................................................................ 33
Table 23: RF Cables Manufacturer Specifications ................................................................. 34
Table 24: Antenna and TMA Site Description ....................................................................... 35

Jun 14, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

General

Section This section provides:

Description Planning information for commissioning
Overview on the procedures to perform the commissioning

Previous Release New creation : 30 April 2013

Date

Release Notes Update: June 2013 - Addition of Node B RF path validation including flow diagrams and forms.
New creation: April 2013 under utilization of existing IM documents for UA08.1.

4 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B commissioning.

Documentation Links to applicable documents can be found under:

Access

https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in table below are required for WCDMA Node B commissioning.
521 Sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B

Commissioning

Section Description
302 WCDMA Node B Commissioning
310 WCDMA Node B Commissioning Test
320 WCDMA Node B RF Path Validation
399 WCDMA Node B Commissioning Test Records

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

References, Continued

Applicable The following methods documents are required to perform the Node B commissioning
Methods
Documents
Table 2: Applicable Methods Documents for IEH521
Doc Number Doc Title URL
9YZ-03450- Alcatel-Lucent Node B UA08.1 http://cic.us.alcatel-
4401-RJZZA Commissioning Procedure lucent.com/pdfdocs15/pr
istore214/521872.pdf

3MN-01637- Alcatel-Lucent 9926 Distributed Base Station http://cic.us.alcatel-

0005-REZZA 4U - W-CDMA UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519914.pdf

NN-20500-284 Alcatel-Lucent 9926 Base Band Unit Node B http://cic.us.alcatel-

for W-CDMA UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519912.pdf

NN-20500-110 Alcatel-Lucent 9326 Digital 2U Node B http://cic.us.alcatel-

UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519908.pdf

NN-20500-019 Alcatel-Lucent Node B Commissioning and http://cic.us.alcatel-

Fault Management User Manual: TIL lucent.com/pdfdocs14/pr
istore215/525147.pdf

NN-10300-031 Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-

System -Security Fundamentals lucent.com/pdfdocs14/pr
istore215/525128.pdf

NOTE: The documents can be fetched from the GPEC portal website:
https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

NOTE: The documents can be fetched from the CIC portal website:
http://www.cic.lucent.com/

6 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Prerequisites

Prerequisites This section lists all items that must be performed prior to the commissioning of a Node B.
The following modules must be installed and powered up:
Node B Digital Unit
RRHs
TRDU
All antenna work must be completed
The RF jumpers and optical or electrical link must be connected to:
RRHs
TRDU
The end-to-end connectivity (i.e. E1/T1 PCM or IP) must be available

Jun 14, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B Commissioning Flow Initial Preparation

Node B The flow diagram below outlines the initial preparation steps for the commissioning of a Node B
Commissioning to connect the laptop on the CCM-U and launch the TIL in local mode.
flow diagram -
for Initial
Preparation for Figure 1: Initial Preparation for the Commissioning
Commissioning

8 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B Commissioning Flow Software Downloading

and Release Activation

Node B The flow diagram below outlines the steps for the Node B commissioning to Download the
Commissioning Software to the Node B and activate the new release with the TIL in local Mode.
Flow Diagram
for Node B
Software Figure 2: Software Downloading and Release Activation
Downloading
and Release
Activation

Jun 14, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B Commissioning Flow Parameter Setting

Node B

Node B The flow diagram below outlines the steps for the Node B commissioning to Set all Node B
Commissioning parameters with the TIL in local Mode.
Flow Diagram - Figure 3: Parameter Setting Node B
Parameter
Setting Node B

10 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B Commissioning Flow Test and Validation

Node B The flow diagram below outlines the steps for the Node B commissioning to Test and Validate
Commissioning all Node B parameters with the TIL in local Mode.
Flow Diagram
Node B
Commissioning Figure 4: Test and Validation
Test and
Validation

Jun 14, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Commissioning Procedure Overview

Reference of The following table lists all operational procedures of a Node B commissioning.
Commissioning
Procedures
Mandatory Table 3: Operational Procedures for the Node B Commissioning
Step Operation Opt/ Proc. Remark
Mand.
1 Node B Software Installation M Proc. 1
on the Laptop
2 First Laptop Setting O Proc. 2 If first laptop TIL
connection
3 TIL Connection M Proc. 3
4 Specific Preparation O Proc. 4 If d4U used
5 Node B Software M Proc. 5
Downloading
6 New Node B Release O Proc. 6 If new Node B Software
Activation downloaded
7 Node B Configuration Checks M Proc. 7
8 Node B Setting BTS M Proc. 8
Parameters
9 Node B Setting RRH O Proc. 9 If RRH or TRDU is used
Parameters
10 Node B Setting Backhaul M Proc. 10
Parameters
11 Node B Setting PCM E1 O Proc. 11 If PCM E1 used
Parameters
12 Node B Setting PCM T1 O Proc. 12 If PCM T1 used
Parameters
13 Node B Setting PCM & IMA O Proc. 13 If PCM & IMA used
Parameters
14 Node B Setting Ethernet O Proc. 14 If IP link used
Parameters
15 Node B Setting ATM O Proc. 15 If PCM used
Parameters
16 Node B Setting IP O Proc. 16 If IP link used
Parameters
17 Node B Setting NeID O Proc. 17 If Node B NeID need to be
Exchange changed
18 Sending I&C Parameters to O Proc. 18 If at least one parameter
the Node B was changed

Continued on next page

12 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Commissioning Procedure Overview, Continued

Reference of
Commissioning
Step Operation Opt/ Proc. Remark
Procedures
Mandatory Mand.
(continued) 19 Node B reset in Connected M Proc. 19
Mode
20 I&C Parameters Verification M Proc. 20
21 MCA Backup File M Proc. 21

Reference of The following table list tests procedures which may be required during a Node B
Commissioning commissioning Tests.
Test
Procedures
NOTE: The following procedures are optional and may be required If test required for certain
Node B configurations

Table 4: Test Procedures for the Node B Commissioning

Step Operation Opt/ Procedures Remarks

Mand.
1 TIL Connection O Proc. 3 If test required and if
not already connected
2 Node B Configuration O Proc. 7 If test required and not
Checks already checked
3 IP Ping Test O Proc. 22 If IP link is used
4 Final Commissioning M Proc. 23
Operations

Jun 14, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Commissioning Checklists

Purpose Checklists are available to support and document the flow of operations before, during and
after commissioning for
On site activities
Node B parameters
Remote (TIL) operations
and document successful completion of commissioning by customer acceptance

Checklist The checklists of IEH521 are generic and can be used as basis for further modifications and
Customization enhancements as per specific customer / market requirements.

Remote Sequence of operations for use by remote operations to verify success of mandatory and
Operations optional steps
Checklist

Table 5: Sequence of Operations Used for the Node B Commissioning

Procedure Condition Expected result To OK NOK
use?
Proc. 1: Node B Software Mandatory Node B Software installed on the
Installation on the Laptop laptop.
If first time PC Laptop configured
Proc. 2: First Laptop Setting setting
Proc. 3: TIL Connection Mandatory TIL GUI visible on Laptop.
Proc. 4: Specific Preparation If DBS 4U used TIL GUI d4U with CCM-U only
before Software Download only visible on Laptop.
Proc. 5: Node B Software Mandatory Node B Software downloaded into
Downloading the Node B (CCM-U+ CEM-U).
Proc. 6: New Node B Release If new software The TIL GUI shows the new Node
Activation downloaded B Software used.
Mandatory No Alarm appears in red and I&C
Proc. 7: Node B Configuration parameters saved into the default
Checks path.
Mandatory The parameters: BTS Packaging,
Proc. 8: Node B Setting BTS Fallback to previous I&C data, GPS
Parameters Synchronization , are configured
Proc. 9: Node B Setting RRH If RRH or TRDU The CPRI link parameter is
Parameters used configured.
Proc. 10: Node B Setting Mandatory The type of incoming link is
Backhaul Parameters configured.

Continued on next page

14 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Commissioning Checklists, Continued

Remote Operations Checklist (continued)

Procedure Condition Expected result To OK NOK

use?
Proc. 11: Node B Setting PCM If PCM E1 used All PCM E1 parameters are
E1 Parameters configured.
Proc. 12: Node B Setting PCM If PCM T1 used All PCM T1 parameters are
T1 Parameters configured.
Proc. 13: Node B Setting If PCM & IMA All PCM and IMA parameters are
PCM&IMA Parameters used configured.
If IP link used All Ethernet parameters are
Proc. 14: Node B Setting (hybrid Iub or Iub configured.
Ethernet Parameters over IP network)
Proc. 15: Node B Setting ATM If PCM used OMC-B VP and VC identifiers
Parameters parameters are configured
Proc. 16: Node B Setting IP If IP link used All IP address are filled correctly
Parameters
If need to change The NeID filled on the TIL GUI is
Proc. 17: Node B NeID the NeID the same as the serial number of
Exchange the Node B
If at least one A success message is displayed
parameter was when I&C parameters are sent to
Proc. 18: Sending I&C changed the CCM-U in order to update the
Parameters to the Node B MCA module.
If at least one The TIL GUI shows that the Node B
Proc. 19: Node B reset in parameter was is connected to OMC-B
Connected Mode changed
Proc. 20: I&C Parameters mandatory The I&C parameters are correctly
Verification saved in the MCA module.
mandatory The MCA file is copied on the local
disk in the default path and sent by
Proc. 21: MCA Backup File email to the coordinator TPM.

Jun 14, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B Form Parameters

General This section is a form of Parameters necessary to perform the WCDMA Node B
commissioning.
The form of parameters based on the CIQ must be documented by the coordinator according to
the expected parameters and configuration.
The form of parameters must be send by email or available on a link.

Node B The following table is the list of Node B parameters required prior to commissioning.
Parameters
Required prior
to Node B Table 6: Node B Parameters Required Prior to Node B Commissioning
Commissioning
Node B parameter Value
Node B IP address
Configuration
Sub-network mask
Software upgrade on Node B: Yes / No
Node B - Software version
Hardware reference
BTS Parameters: BTS Packaging (refer to table)

Node B BTS The following Node B BTS parameters are required prior to commissioning
Parameters

Table 7: Node B BTS Parameters

Node B BTS parameters Value
BTS Packaging Refer to BTS packaging table
Fallback to previous I&C data Activate
Deactivate
GPS synchronization Activate
Deactivate
Ru Name:
Pec Code:
Serial Number:
Manufacturing Date:

Continued on next page

16 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B Form Parameters, Continued

Node B RRH The following Node B RRH parameters are required prior to commissioning
Parameters

Table 8: Node B RRH Parameters

Node B RRH parameters Value
RRH Type CPRI(1,2,3)/HSSL(4,5,6)
CPRI(1,2,3,4,5,6)

Node B The following Node B Backhaul parameters are required prior to commissioning
Backhaul
Parameters
Table 9: Node B Backhaul Parameters
Node B Backhaul parameters Value
Type of Incoming Link E1/T1
STM
Fast Ethernet
Gigabit Ethernet

Node B PCM The following Node B PCM (E1) parameters are required prior to commissioning
(E1)
Parameters
Table 10: Node B PCM (E1) Parameters

Node B PCM parameters Value

PCM Type E1 to used
T1 (If used refer to the following table)
E1 Adaptation E1 120Ohms
E1 75 Ohms
PCM E1 Frame Multiframe
Single Frame
Automatic multiframe
PCM receive sensitivity Low (short haul) by default
High (long haul)
PCM CRC threshold 915 (or type a new value)
Protection Module No
Yes

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B Form Parameters, Continued

Node B PCM The following Node B PCM (T1) parameters are required prior to commissioning
(T1)
Parameters
Table 11: Node B PCM (T1) Parameters
Node B PCM parameters Value
PCM Type E1 (If used refer to the above table)
T1 to used
PCM T1 frame Single Frame
Extended super frame
PCM Coding B8ZS
AMI
LBO 0 to 133ft (0 to 40m) by default
133 to 266ft (40 to 81m)
266 to 399ft (81 to 121m)
399 to 533ft (121 to 162m)
533 to 655ft (162 to 199m)
PCM receive CRC CRC not used by default
CRC used
PCM receive sensitivity Low (short haul) by default
High (long haul)
PCM CRC threshold 320 (or type a new value)
Protection Module No
Yes

Continued on next page

18 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B Form Parameters, Continued

Node B PCM & The following Node B PCM & IMA parameters are required prior to commissioning
IMA Parameters

Table 12: Node B PCM & IMA Parameters

Node B PCM & IMA parameters Value
IMA Usage IMA
Standard
Drop&Insert
PCM with OAM Link/synchro inN 1 (Do not change the value)
IMA Version V1.0
V1.1
Frame length 32
64
128 to used
256
Max Differential Delay 20 (Do not change the value)
Min number of Active Link in Gr (Do not change the value)
Test Pattern Procedure Activation Test No to used
Test Yes
Alpha Parameter 2 (Do not change the value)
Beta Parameter 2 (Do not change the value)
Gamma Parameter 1 (Do not change the value)

Node B The following Node B Ethernet parameters are required prior to commissioning
Ethernet
Parameters
Table 13: Node B Ethernet Parameters

Node B Ethernet parameters Value

VLAN ID 0 (Do not change the value)
VLAN TAGGING Disabled
Enabled to used
LAG / HUBBING used (Do not change the value)
Eth Port used for iub IF (Do not change the value)
Eth Port used for Hubbing (Do not change the value)

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B Form Parameters, Continued

Node B ATM The following Node B ATM parameters are required prior to commissioning
Parameters

Table 14: Node B ATM Parameters

Node B ATM parameters Value
OMC-B VP Identifier __ __ (example: 1)
OMC-B VC identifier __ __ (example: 32)
All other values (Do not change the value)

Node B IP The following Node B IP parameters are required prior to commissioning

Parameters

Table 15: Node B IP Parameters

Node B IP parameters Value
Existence of a DHCP server No
Yes
BTS IP Address IP@: __.__.__.__
OMC-B IP Address IP@: __.__.__.__
OMC-B port 6301
Sub-network mask 255.255.255.0
BTS port 6301
Default Gateway Ip Address (Do not change the value)

20 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B Packaging Parameters and Configurations

BTS Packaging The following table shows the full list of BTS Packaging shown in the drop down menu of the
Parameters TIL parameters.
Cross-reference The BTS Packaging parameter is required prior to commissioning according to the Node B
configuration to use.
The selection of the BTS Packaging parameter must be agreed with the coordinator to get
the expected configuration.

If the Node B configuration is ... Then select the BTS Packaging

parameter...
a Distributed Node B according to the hosting cabinet using the
new digital and radio components
(CCM-U/CEM-U) + (TRDU or RRH or
MCTRX) from the table below in white lines.
not a Distributed Node B according to the hardware cabinet and
using the legacy digital and radio
components
(CCM/CEM/TRM) + (DDM/MCPA) from the
table below in grey lines.

Table 16: Node B Parameters: BTS Packaging

BTS Packaging Value Cabinet Digital Radio
Components Components
Legacy New Legacy New
CCM/ CCM-U/ DDM/ TRDU/
CEM/ CEM-U MCPA RRH/
TRM d2U/ d4U MCTRX
Indoor 700mm 9311 Macro ID1 700mm X X
Outdoor 9311 Macro Outdoor1 X X X X
Indoor 600mm 9311 Macro ID1 600 mm X X
Compact indoor (3) 9312 Compact ID X X
(Former BTS6010)
Street (compact outdoor) 9315 Macro Street X X
Indoor 2 9311 Macro Indoor2 X X X X
Outdoor 2 9311 Macro Outdoor2 X X X X
Mono (3) 9313 Micro (Former BTS 1020) X X
GSM-UMTS Indoor (3) Former BTS 18010 X X
Indoor GSM-UMTS

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B Packaging Parameters and Configurations,

Continued

BTS Packaging Parameters Cross-reference (continued)

BTS Packaging Value Cabinet Digital Radio

Components Components
GSM-UMTS Outdoor (3) Former BTS 18020 X X
Outdoor GSM-UMTS
dBTS 2U 9326 d2U V1 X X
Subway (4) 9311 Macro ID2 X X
dBTS 6110 Indoor 6110 digital BTS ID X X
dBTS 6120 Outdoor 6120 digital BTS OD X X
rBTS 6110 Indoor AC 6110 radio BTS ID AC X
rBTS 6110 Indoor DC 6110 radio BTS ID DC X
rBTS 6120 Outdoor AC 6120 radio BTS OD AC X
rBTS 6120 Outdoor DC 6120 radio BTS OD DC X
rBTS 6120 Outdoor AC/DC 6120 radio BTS OD AC/DC X
BTS12120 (3) 9311 Macro OD2 X X
dBTS 2U-V2 9326 d2U V2 or X X
9926 d2U V3 Stand.
d2U / Smart / MBI/MBO (2G) /
PSU / MBI3+ /
MBI3L / MBO1L.
dBTS 4U (3) No product
Korea d4U (3)(4) 9926 d4U for Korean market
9100 MBS MID Indoor 9100 MBI5 ev2 (3G) X X
9100 MBS Large Indoor 9100 MBI5 ev2 (3G) X X
9100 MBS MID Outdoor 9100 MBO1 ev2 (3G) X X
9100 MBS Large Outdoor (3) 9100 MBO1 ev2 (3G) X X
dBTS 2U-V5 9926 d2U V5 standalone X X
9100 MBS MID Indoor 5 9100 MBI5 (2G cabinet) X X
3GOO (2)
9100 MBS MID Outdoor 2E 9100 MBO2 ev. (2G cabinet) X X
3GOO (2)
9944 S8k Outdoor 9944 Smart Base X X
Station S8k OD cabinet
9944 S18k Outdoor 9944 Smart Base X X
Station S18k OD cabinet

Continued on next page

22 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B Packaging Parameters and Configurations,

Continued

BTS Packaging Parameters Cross-reference (continued) (continued)

BTS Packaging Value Cabinet Digital Radio

Components Components
9100 MBS MID Outdoor 1E 9100 MBO1 ev. (2G cabinet) X X
3GOO (2)
dBTS 4U-V3 9926 d4U X X
Standalone/Smart/PSU
9711 lightRadio Indoor AC (1) 9711 LR Indoor AC X X
9712 lightRadio Outdoor AC 9712 LR Outdoor AC X X
9711 lightRadio Indoor DC (1) 9711 LR Indoor DC X X
9712 lightRadio Outdoor DC 9712 LR Outdoor DC X X
(1)

9712 lightRadio Outdoor AC 9712 LR MBS Outdoor AC for X X

NAR (1)(3) NAR market

NOTES:
1. Only used when 3G is master of the cabinet, otherwise use d2U/d4U standalone BTS packaging.
2. To be used in the relevant 2G cabinet where 3G is master of the cabinet (no connection to 2G OMC-R and
MCTRX 3G, only radio equipment).
3. The product is no longer supported or available
4. Korean market only

Jun 14, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B RF Path Validation References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
Node B RF Path Validation.

Documentation Links to applicable documents can be found under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

24 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B RF Path Validation Prerequisites

Prerequisites The following modules must be installed prior to the Node B RF Path Validation:
Antenna
TMA (if used)
Feeders RF and Jumpers RF (Upper and Lower)
Ground Kit
Radio Elements (RRHs or TRDU)

IMPORTANT: The Node B RF Path Validation must be performed before the

Node B Commissioning.

Figure 5: Global Antenna Link: Antenna, Feeder and Jumpers

Jun 14, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B RF Path Validation Flow Initial Preparation

Node B RF Path The flow diagram below outlines the Initial Preparation steps for the Node B RF Path
Validation flow Validation.
diagram - Initial
Preparation
Figure 6: Initial Preparation of the Node B RF Path Validation

26 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B RF Path Validation Flow Test,

Measurement and Validation

Node B RF Path The flow diagram below outlines the Test, Measurement and Validation steps for the Node B
Validation flow RF Path Validation.
diagram Test,
Measurement
and Validation Figure 7: Test, Measurement and Validation of the Node B RF Path
Validation

Jun 14, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B RF Path Validation Procedure Overview

Reference of The following table list tests procedures which may be required during the Node B RF Path
Node B RF Path Validation.
Validation NOTE: The following procedures are mandatory or optional and may be required If test
Procedures required for certain Node B RF Path Validation.

Table 17: Test Procedures for the Node B RF Path Validation

Step Operation Opt/ Procedures Remarks

Mand.
1 Physical Antenna and TMA Aerial
M
check Installation Height work
2 Verification of Cable Run M Verification

3 Measurement of the Antenna Azimuth

M Height work
Azimuth Measurement
4 Frequency Band Selection M Ground work
5 If only one port used
One Port Calibration M
Self Calibration Ground work
6 If two port used
Two Port Calibration O
Ground work
7 Cable Loss Measurement M
Measure the
8 VSWR Measurement with 50 Ground work
M feeder losses
Ohms Load
9 Measure the
TMA Measurement M TMA Gain and Height work
Filter
10 TMA and Antenna VSWR
M Height work
Measurement VSWR
11 VSWR measurement of the Measurement
M Ground work
whole line
12 Distance to Fault Location DTF
M Ground work
(DTF) Measurement
13 Creation of a Database M
14 Measurement Transfer into Control
M
the Database Datasheet Ground work
Process
15 Calculation of Distance to
M
Fault
16 Antenna
Antenna Validation Report M Validation Ground work
Report

28 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B RF Path Validation Checklists

Purpose Checklists are available to support and document the flow of operations before, during and
after Node B RF Path Validation for
On site activities
Site Master tool parameters
Antenna specifications from the manufacturer
TMA Gain specifications from the manufacturer
Feeder and Jumper specifications from the manufacturer
and document successful completion of Node B RF Path Validation for customer acceptance

Checklist The checklists of IEH521 are generic and can be used as basis for further modifications and
Customization enhancements as per specific customer / market requirements.

Remote Sequence of operations for use by remote operations to verify success of mandatory and
Operations optional steps
Checklist

Table 18: Sequence of Operations Used for the Node B RF Path Validation

Procedure Condition Expected result To OK NOK

use?
Get an idea of the quality of the
Aerial Installation Verification Mandatory installation (Antenna, TMA, Cable
Run)
Measure the azimuth of the
Measurement of the Antenna
Mandatory antenna to check the predicted
Azimuth
antenna coverage of the site.

Self Calibration and Calibrate the Site Master on each

Frequency Band Selection site whenever necessary and taken
Mandatory
into account the climatic conditions
dependent.
If only One Port Calibrate only one port of the Site
One Port Calibration
used Master according to the need.
Calibrate two ports of the Site
Two Port Calibration If two Port used
Master according to the need.
Measure the loss value of the cable
in dB over the given frequency
Cable Loss Measurement Mandatory
bandwidth to validate the cable
attenuation.

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B RF Path Validation Checklists, Continued

Remote Operations Checklist (continued)

Procedure Condition Expected result To OK NOK

use?
Measure the VSWR to validate the
VSWR Measurement with 50 feeder and Jumpers (adapted with
Mandatory
Ohms Load 50 Ohms load) before to connect to
the antenna.
Measure the TMA Gain and
TMA Measurement Mandatory Filtering to validate its
characteristics
Measure the TMA and antenna
TMA and Antenna VSWR
Mandatory VSWR to validate the antennas
Measurement
jumper to the TMA on downlink
Measure the VSWR of the whole
VSWR measurement of the
Mandatory line to validate the whole line with
whole line
antenna, feeder, jumper and TMA.
Detect all discontinuities in the line
Distance to Fault Location and give a good technical status
Mandatory
(DTF) and a reference of the line from its
installation.
Record and transfer all traces and
Control Datasheet Process Mandatory measurement into the database to
fill the antenna validation report.
Evidence for the acceptance of the
Antenna Validation Report Mandatory
validation link with antenna TMA.

30 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B RF Path Validation Form Parameters

General This section is a form of Parameters necessary to performing the Node B RF Path Validation.
The form of parameters based on the CIQ must be documented by the coordinator according to
the expected parameters and configuration (from RF manufacturers specifications).
The following form of parameters must be sent by email or available on a link for the technician
prior to performing RF path validation.

Node B RF Path The following table is required by the technician prior to perform Node B RF Path Validation.
Validation Form The coordinator must fill the following description of the site according to the information
Parameters - received from the customer (CIQ).
Site Description

Table 19: Site Description

Site Description
Site Name:
Site Code:
Address:

City: Country:
GPS Coordinates:
Telephone Building :
Parking available: YES NO
Distance between parking and site location: (meters)
Site location: (Select the site configuration below)
Basement Ground Floor Shelter
Floor Number Rooftop Other:

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B RF Path Validation Form Parameters, Continued

Node B RF Path The following table is required by the technician prior to performing Node B RF Path
Validation Form Validation.
Parameters - The coordinator must fill the following list of stakeholders according to the information received
Stakeholders from the customer.
Information

Table 20: Stakeholders

Stakeholders
Site Manager Name:
Address:

Tel: Mobile Phone:

Key-holder Name:
Address:

Tel: Mobile Phone:

For visits and deliveries, advise: Name:
Address:

Tel: Mobile Phone:

Qualified Technician #1 for test Name:
measurements: Address:

Tel: Mobile Phone:

Qualified Technician #2 for test Name:
measurements (if work involving Address:
climbing)

Tel: Mobile Phone:

Continued on next page

32 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B RF Path Validation Form Parameters, Continued

Node B RF Path The following table is required by the technician prior to performing Node B RF Path Validation.
Validation Form The coordinator must fill the following UMTS Frequency Band used on the site according to the
Parameters information received from the customer.
Antenna and
TMA Frequency
Band Table 21: UMTS Frequency Band

UMTS Frequency (Band)

850Mhz 900Mhz 1900Mhz AWS 2100Mhz
(Band V) (Band VIII) (Band II) (Band IV) (Band I)

Node B RF Path The following table is required by the technician prior to perform Node B RF Path Validation.
Validation Form The coordinator must fill the following Manufacturer Specifications of the RF Modules according
Parameters to the information received from the customer.
Antenna and
TMA
Manufacturer Table 22: RF Modules Manufacturer Specifications
Specifications
Cell 1 2 3 4 5 6
Antenna Manufacturer Specifications
Antenna
Manufacturer Name
Antenna Type
(reference)
Maximum VSWR
value of the Antenna
TMA Manufacturer Specifications
TMA Manufacturer
Name
TMA Type
(reference)
Gain of TMA

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

Node B RF Path Validation Form Parameters, Continued

Node B RF Path The following table is required by the technician prior to performing Node B RF Path Validation.
Validation Form The coordinator must fill the following Manufacturer Specifications of RF Cables according to
Parameters RF the information received from the customer.
Cables
Manufacturer
Specifications Table 23: RF Cables Manufacturer Specifications

Cell 1 2 3 4 5 6
Feeders Manufacturer Specifications
Manufacturer Name
Type (reference)
Length
Expected Feeder
Losses
Upper Jumpers TMA Manufacturer Specifications
Manufacturer Name
Type (reference)
Length
Expected Upper
Jumper TMA Losses
Upper Jumpers Manufacturer Specifications
Manufacturer Name
Type (reference)
Length
Expected Upper
Jumper Losses
Lower Jumpers Manufacturer Specifications
Manufacturer Name
Type (reference)
Length
Expected Lower
Jumper Losses
VSWR Measurement of the Whole Line
Acceptable value of
the VSWR of the
entire line (Antenna
and Feeder)

Continued on next page

34 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Planning IEH 521, Section 301

Node B RF Path Validation Form Parameters, Continued

Node B RF Path The following table is required by the technician prior to performing Node B RF Path
Validation Form Validation.
Parameters The coordinator must fill the following site description of the Antenna and the TMA according
Antenna and to the information received from the customer and the Network Design Engineering team (CIQ
TMA Site based).
Description

Table 24: Antenna and TMA Site Description

Cell 1 2 3 4 5 6
Antenna type
Antenna Height
Azimuth (in Degree)
Tilt (in Degree)
Grounding Kit
(OK/NOK)
TMA Type

NOTE:
Azimuth: defines the horizontal plane of the antenna radiation pattern
Tilt: vertical orientation, used to reduce interference.

Jun 14, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 301 Commissioning Planning

This page intentionally left blank.

36 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 302

April 30, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Commissioning Procedure

Table of Contents

General ............................................................................................................ 5
Section Description .......................................................................................... 5
Previous Release Date ....................................................................................... 5
Release Notes ................................................................................................. 5
References ........................................................................................................ 6
General ........................................................................................................ 6
Documentation Access ...................................................................................... 6
Applicable IEH521 Sections ................................................................................. 6
Applicable Methods Documents............................................................................ 6
Material Requirements ......................................................................................... 8
General ........................................................................................................ 8
Hardware Tool ................................................................................................ 8
Software Tool ................................................................................................. 8
Commissioning Procedures Overview ........................................................................ 9
Commissioning Procedures ................................................................................. 9
Overview ....................................................................................................... 9
Proc. 1: Node B Software Installation on the Laptop ................................................... 10
Description .................................................................................................. 10
Condition .................................................................................................... 10
Required Data .............................................................................................. 10
Procedure of Preparation before Node B Software Installation ................................... 10
Procedure of Node B Software Installation on the Laptop .......................................... 11
Procedure of Node B Software Installation on the Laptop (continued) .......................... 12
Procedure of Node B Software Installation on the Laptop (continued) .......................... 13
Procedure of the Node B Software Verification ...................................................... 14
Proc. 2: First Laptop Setting ................................................................................ 15
Description .................................................................................................. 15
Preconditions ............................................................................................... 15
First Laptop Setting Procedure .......................................................................... 15
Proc. 3: TIL Connection ...................................................................................... 18
Description .................................................................................................. 18
Preconditions ............................................................................................... 18

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

TIL Connection Procedure ................................................................................ 18

Supporting Information ................................................................................... 23
Proc. 4: Specific Preparation ................................................................................ 24
Description .................................................................................................. 24
Restriction ................................................................................................... 24
Requirement with 9926 DBS 4U .......................................................................... 24
Procedure for Distributed Node B d4U ................................................................. 24
Proc. 5: Node B Software Downloading .................................................................... 25
Description .................................................................................................. 25
Preconditions ............................................................................................... 25
Node B Software Downloading Procedure ............................................................. 25
Node B Software Downloading Procedure (continued) .............................................. 27
Supporting Information ................................................................................... 27
Proc. 6: New Node B Release Activation .................................................................. 28
Description .................................................................................................. 28
Preconditions ............................................................................................... 28
Procedure of New Node B release Activation ......................................................... 28
Procedure of the latest Software Release Verification.............................................. 29
Supporting Information ................................................................................... 30
Proc. 7: Node B Configuration Checks ..................................................................... 31
Description .................................................................................................. 31
Precondition ................................................................................................ 31
Node B Configuration Checks Procedure ............................................................... 31
Procedure to Save the I&C Parameters ................................................................ 35
Supporting Information ................................................................................... 36
Proc. 8: Node B Setting BTS Parameters .................................................................. 37
Description .................................................................................................. 37
Preconditions ............................................................................................... 37
Node B Settings BTS Parameters Procedure ........................................................... 37
Supporting Information ................................................................................... 39
Proc. 9: Node B Setting RRH Parameters .................................................................. 40
Description .................................................................................................. 40
Preconditions ............................................................................................... 40
Node B Setting RRH Parameters Procedure ........................................................... 40
Supporting Information ................................................................................... 41
Proc. 10: Node B Setting Backhaul Parameters .......................................................... 42
Description .................................................................................................. 42
Preconditions ............................................................................................... 42
Node B Setting Backhaul Parameters Procedure ..................................................... 42
Supporting Information ................................................................................... 43
Proc. 11: Node B Setting PCM E1 Parameters ............................................................ 44
Description .................................................................................................. 44
Preconditions ............................................................................................... 44
Node B Setting PCM E1 Parameters Procedure........................................................ 44
Procedure if PCM Protection Module used ............................................................. 47
Supporting Information ................................................................................... 47
Proc. 12: Node B Setting PCM T1 Parameters ............................................................ 48
Description .................................................................................................. 48
Preconditions ............................................................................................... 48
Node B Setting PCM T1 Parameters Procedure ....................................................... 48
Procedure if PCM Protection Module used ............................................................. 51

2 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Supporting Information ................................................................................... 51

Proc. 13: Node B Setting PCM&IMA Parameters .......................................................... 52
Description .................................................................................................. 52
Preconditions ............................................................................................... 52
Node B Setting PCM&IMA Parameters Procedure ..................................................... 52
Procedure if IMA Configuration used ................................................................... 53
Procedure if Drop & Insert Configuration used ....................................................... 55
Supporting Information ................................................................................... 56
Proc. 14: Node B Setting Ethernet Parameters .......................................................... 57
Description .................................................................................................. 57
Preconditions ............................................................................................... 57
Node B Setting Ethernet Parameters Procedure ...................................................... 57
Procedure if CCM-U used with GE MDA ................................................................. 59
Supporting Information ................................................................................... 59
Proc. 15: Node B Setting ATM Parameters ................................................................ 60
Description .................................................................................................. 60
Preconditions ............................................................................................... 60
Node B Setting ATM Parameters Procedure ........................................................... 60
Supporting Information ................................................................................... 61
Proc. 16: Node B Setting IP Parameters ................................................................... 62
Description .................................................................................................. 62
Preconditions ............................................................................................... 62
Node B Setting IP Parameters ............................................................................ 62
Procedure.................................................................................................... 62
Supporting Information ................................................................................... 63
Proc. 17: Node B NeID Exchange............................................................................ 64
Description .................................................................................................. 64
Preconditions ............................................................................................... 64
Node B NeID Exchange Procedure ....................................................................... 64
Supporting Information ................................................................................... 65
Proc. 18: Sending I&C Parameters to the Node B ........................................................ 66
Description .................................................................................................. 66
Preconditions ............................................................................................... 66
Sending I&C Parameters to the Node B Procedure ................................................... 66
Supporting Information ................................................................................... 68
Proc. 19: Node B reset in Connected Mode ............................................................... 69
Description .................................................................................................. 69
Preconditions ............................................................................................... 69
Node B reset in Connected Mode Procedure .......................................................... 69
Supporting Information ................................................................................... 70
Proc. 20: I&C Parameters Verification..................................................................... 71
Description .................................................................................................. 71
Preconditions ............................................................................................... 71
I&C Parameters Verification Procedure ................................................................ 71
Supporting Information ................................................................................... 73
Proc. 21: MCA Backup File ................................................................................... 74
Description .................................................................................................. 74
Preconditions ............................................................................................... 74
MCA Backup File Procedure .............................................................................. 74
Supporting Information ................................................................................... 77
End of Commissioning ..................................................................................... 77

April 30, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

List of Figures

Figure 1: Example of TIL GUI for d2U ................................................................................ 22

Figure 2: Example of TIL GUI for d4U: (with CCM-U coming from Factory in UA7.1) ....................... 23

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B commissioning ....................................... 6
Table 2: Applicable Methods documents for IEH 521 ............................................................... 6
Table 3: Hardware Tools ................................................................................................. 8
Table 4: Software Tools .................................................................................................. 8
Table 5: Procedures to perform according to the Network Used: ................................................ 9

4 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

General

Section This section provides detailed information about the individual procedures for commissioning
Description of a WCDMA Node B:
Preconditions
Inputs
Outputs
Additional details
Link to commissioning methods document where the procedure is contained.

Previous Release New creation

Date

Release Notes New creation: Apr 2013 under utilization of existing IM documents for UA08.1.

April 30, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B commissioning.

Documentation Access to applicable documents can be made under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable The sections listed in Table 1 below are required for WCDMA Node B commissioning.
IEH521 Sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B

commissioning

Section Description
301 Node B Commissioning Planning
310 Node B Commissioning Test
399 Node B Commissioning Test Records

Applicable The following methods documents are required to perform the Node B commissioning
Methods
Documents
Table 2: Applicable Methods documents for IEH 521

Doc Doc Title URL

Number
9YZ-03450- Alcatel-Lucent Node B UA08.1 Commissioning http://cic.us.alcatel-
4401-RJZZA Procedure lucent.com/pdfdocs15/pr
istore214/521872.pdf

3MN-01637- Alcatel-Lucent 9926 Distributed Base Station http://cic.us.alcatel-

0005-REZZA 4U - W-CDMA UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519914.pdf

NN-20500- Alcatel-Lucent 9926 Base Band Unit Node B for http://cic.us.alcatel-

284 W-CDMA UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519912.pdf

Continued on next page

6 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

References, Continued

Applicable
Methods
Doc Doc Title URL
Documents
(continued) Number
NN-20500- Alcatel-Lucent 9326 Digital 2U Node B UA08.1 http://cic.us.alcatel-
110 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519908.pdf

NN-20500- Alcatel-Lucent Node B Commissioning and http://cic.us.alcatel-

019 Fault Management User Manual: TIL lucent.com/pdfdocs14/pr
istore215/525147.pdf

NN-10300- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-

031 System - Security Fundamentals lucent.com/pdfdocs14/pr
istore215/525128.pdf

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

April 30, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Material Requirements

General This section describes the hardware and software tools required to perform the commissioning
method.

Hardware Tool The hardware tools listed in the following table are required to perform the commissioning.

Table 3: Hardware Tools

Hardware Tool Quantity Description
Keys to open the NodeB 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

Software Tool The software tools materials listed in the following table are required to perform the
commissioning.

Table 4: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox or
equivalent
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with
WIN7)

8 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Commissioning Procedures Overview

Commissioning The following table provides an overview about the steps required to perform commissioning
Procedures of WCDMA Node B dependant on the backhaul interface.
Overview

Table 5: Procedures to perform according to the Network Used:

Procedure ATM Iub Hybrid Iub over
Iub IP
Proc. 1: Node B Software Installation on To perform if necessary
the Laptop
Proc. 2: First Laptop Setting To perform if necessary (first setting)
Proc. 3: TIL Connection Mandatory to perform
Proc. 4: Specific Preparation To perform if necessary (with d4U)
Proc. 5: Node B Software Downloading To perform if necessary
Proc. 6: New Node B Release Activation To perform if necessary
Proc. 7: Node B Configuration Checks Mandatory to perform
Proc. 8: Node B Setting BTS Parameters Mandatory to perform
Proc. 9: Node B Setting RRH Parameters To perform if necessary (with RRH or TRDU)
Proc. 10: Node B Setting Backhaul Mandatory to perform
Parameters
Proc. 11: Node B Setting PCM E1 Mandatory to perform
Parameters
Proc. 12: Node B Setting PCM T1 Mandatory to perform
Parameters
Proc. 13: Node B Setting PCM&IMA Mandatory to perform
Parameters
Proc. 14: Node B Setting Ethernet Mandatory to perform
Parameters
Proc. 15: Node B Setting ATM Parameters Mandatory to perform
Proc. 16: Node B Setting IP Parameters Mandatory to perform
Proc. 17: Node B NeID Exchange To perform if necessary (NeID)
Proc. 18: Sending I&C Parameters to the Mandatory to perform
Node B
Proc. 19: Node B reset in Connected Mode Mandatory to perform
Proc. 20: I&C Parameters Verification Mandatory to perform
Proc. 21: MCA Backup File Mandatory to perform
Proc. 22: IP Ping Test To perform if necessary
Proc. 23: Final Commissioning Operations Mandatory to perform

April 30, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 1: Node B Software Installation on the Laptop

Description This procedure gives the process to use the hard disk of the PC as the source for the software
upgrade.

Condition This procedure has to be executed only at the first time (initial setup) to install the Node B
software delivery components on the PC.
If already done no action is required.

Required Data The following data are required for the setup:
Node B software available on a Web server or
Node B software available on a CD

Procedure of Execute the preparation procedure before the Node B Software Installation as per table below:
Preparation
before Node B
Software Step Action
Installation
1 Click Start in the Windows Taskbar.
2 Select Programs/Windows Explorer.
3 Double-click on C: to open it.
4 Verify that a Delivery folder is present on your laptop.

If the Delivery folder... Then ...

is a personal folder Rename it
is a previous software release Imperatively delete it
delivery folder

NOTE: The Delivery folder must be unique and only dedicated to the last
Software release delivery.

Continued on next page

10 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 1: Node B Software Installation on the

Laptop, Continued

Procedure of
Preparation
Step Action
before Node B
Software 5 Check the type of Node B Software delivery
Installation
(continued)
If ... Then ...
Node B Software delivery from a Continue with following Procedure
Web server of Node B Software Installation
from step 1 up to step 4 and
continue with step 7 up to the end.
Node B Software delivery using a Continue with following Procedure
CD-ROM of Node B Software Installation
step 5 up to the end.

Procedure of Execute the installation procedure of the Node B Software on the laptop as per table below:
Node B
Software
Installation on Step Action
the Laptop
1 Open the compress software (ex here: tar.gz)
2 Select Options and Configuration

3 Select Miscellaneous or Select all

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 1: Node B Software Installation on the

Laptop, Continued

Procedure of
Node B
Step Action
Software
Installation on 4 Remove the check box: TAR file smart CR/LF conversion.
the Laptop
(continued)

5 Insert the Node B software release CD-ROM in the CD-ROM drive.

NOTE: In this case the Node B Software into the CD-ROM is not compressed.
6 Click on the CD-ROM drive letter
7 Click on the Delivery folder to select the NodeB SW
8 Press the CTRL + C to copy the Delivery folder in the clipboard.
9 Click on C: to select it.
10 Press the CTRL + V to paste the clipboard content in C:

Continued on next page

12 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 1: Node B Software Installation on the

Laptop, Continued

Procedure of
Node B
Step Action
Software
Installation on 11 Wait during the transfer
the Laptop
(continued)

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 1: Node B Software Installation on the

Laptop, Continued

Procedure of Execute the verification procedure of the Node B Software installed on the laptop as per table
the Node B below:
Software
Verification
Step Action
1 Check on the folder C:/ delivery the existence of the new SW file UNB

NOTE: The Node B SW is now available on the Laptop.

2

If ... Then ...

Node B Software delivery from a Decompress the Node B Software
Web server is compressed on the file UNB
folder C:/ delivery
Node B Software delivery using a End of the procedure
CD-ROM is not compressed on the
folder C:/ delivery

NOTE: The Node B SW is now installed on the Laptop.

3 End of the procedure

NOTE: Detailed information about the procedure is available in the documents listed in the
section References.

14 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 2: First Laptop Setting

Description This procedure gives the process for the first Laptop setting to prepare the first TIL connection
with the WCDMA Node B.

Preconditions The following preconditions for this procedure step must be met:
PC has never been set as TIL GUI
Have Java run type environment installed into the laptop with the right version
Have User ID and Password for TIL GUI available

First Laptop Execute the procedure steps as per table below:

Setting
Procedure
Step Action
1 In the Local Area Connection:
Select Internet Protocol Version 4 (TCP/IPv4)
2 Click on Properties

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 2: First Laptop Setting, Continued

First Laptop
Setting
Step Action
Procedure
(continued) 3 In TCP/IP Properties screen, in the IP Address tab:
Note and record the current configuration (if necessary)
4 Modify properties to access Node B digital board:
Select use the following IP address
5 Fill the following IP address:

When ... Then use address...

IP Address 223.254.254.1
Subnet mask 255.255.240.0

6 Click OK to quit the TCP/IP Properties screen

Continued on next page

16 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 2: First Laptop Setting, Continued

First Laptop
Setting
Step Action
Procedure
(continued) 7 Click OK to quit the network screen

NOTE: Detailed information about the procedure is available in the documents listed in the
section References.

April 30, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 3: TIL Connection

Description This procedure gives the process

To connect the Laptop on the CCM-U board and
To launch the TIL in Local Mode (direct connection to CCM-U board)

Preconditions The PCMCIA card setting on the Laptop should be correctly configured according to Proc.2.
In case of Outdoor Node B and before opening the doors:

If ... Then ...

No water is located above the Node B doors Open the doors
or roof
Water is located above the Node B doors or Wipe it with a sponge or a duster to avoid
roof any water from falling into the Node B before
to open the doors.

The installation procedure is finalized and the Node B is power ON.

TIL Connection Execute the procedure steps as per table below:

Procedure

Step Action
1 Connect the RJ45 (Cross-Cable) between Laptop and the CCM-U board
(Port1)

NOTE: When connecting the RJ45 the Green LED should light on Port 1 of the
CCM-U
2 Start the Web Browser.

Continued on next page

18 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 3: TIL Connection, Continued

TIL Connection
Procedure
Step Action
(continued)
3 In the URL field of your web browser.
Enter the following address:
http://223.254.254.244/til/index.html

IMPORTANT:
This URL field will be use for CCM-U coming from factory only.

In case of re-use CCM-U from field customer, a specific Node B IP address is

required to enter into the URL field:
http://<Node B IP Address>/til/index.html

4 Press Return

NOTE: During Java Applet downloading, a progress bar is displayed.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 3: TIL Connection, Continued

TIL Connection
Procedure
Step Action
(continued)
5 When the Java Applet is completely downloaded and if not already filled.
Enter your User Name.
Enter your Default Path (the directory where the results will be saved).

6 Click Start on the TIL Applet

NOTE: During TIL manager and test server connection, a message is

displayed.

Continued on next page

20 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 3: TIL Connection, Continued

TIL Connection
Procedure
Step Action
(continued)
7 In the Security window
Enter the Login: nodeb
Enter the Password: Nodeblnx

IMPORTANT:
The Login nodeb and the password nodeblnx will be used during the TIL
connection on the CCM-U not built.

IMPORTANT:
During the TIL connection, a new Login and a new Password could be
required by the customer after build the node B.

NOTE: to change the Login and Password can be found in the manual
Alcatel-Lucent 9353 Wireless Management System -Security
Fundamentals (refer to the reference section)

8 Click OK

NOTE: At the end of the connection, the TIL board screen is displayed.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 3: TIL Connection, Continued

Figure 1: Example of TIL GUI for d2U

Continued on next page

22 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 3: TIL Connection, Continued

Figure 2: Example of TIL GUI for d4U: (with CCM-U coming from Factory in UA7.1)

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 4: Specific Preparation

Description This procedure describes how to configure a DBS 4U before software upgrade of the
distributed Node B 4U with the TIL.

Restriction This procedure is applicable to the DBS 4U with CCM-U in UA7.1 software version from
factory.

Requirement
with 9926 DBS
4U
IMPORTANT:
If upgrading a 9926 DBS 4U with the CCM-U from spare or from the factory containing an
UA07.1 software load.
The UA8.1 software will not start correctly if these steps are not performed for a 9926 DBS 4U
with a CCM-U containing a UA7.1 software load.

Procedure for Execute procedure as per table below

Distributed Node
B d4U
Step Action
1 If the DBS 4U is powered up, it must be first powered down.
2 Remove all of the CEM-U cards from the DBS 4U

NOTE: The CEM-U cards will be physically re-installed after the Node B
release activation
3 Power up the DBS 4U without the CEM-U cards.

NOTE: Details of the power up, power down procedures can be found in the
Alcatel-Lucent Distributed Base Station Maintenance Guide (refer to the
reference section)
4 Proceed with re-establish the TIL Connections (Refer to Procedure 3)
5 Perform the following procedures

24 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 5: Node B Software Downloading

Description This procedure describes how to download the software into the Node B.

Preconditions The upgrade of Node B will be done from one software release to the current network release
in local mode (direct connection between the laptop up to the CCM-U board.
To use the hard disk of the PC as the source of the upgrade, the Node B software delivery
components must be previously installed on the PC
The Laptop Setting and TIL connections are already done and available.

Node B Execute procedure as per table below

Software
Downloading
Procedure Step Action
1 In the TIL GUI:
Go to Tools menu
2 Select Software Upgrade
3 Select New Software Download

4 In the Choose a delivery file dialog box:

Check that the name of the folder is the same as the current network Node B
release to download.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 5: Node B Software Downloading, Continued

Node B
Software
Step Action
Downloading
Procedure 5 Double Click on the folder UN
(continued)

6 Select the File named FILE0_<Version>.

7 Click Choose a delivery file

NOTE: The software downloading starts and a progress bar is displayed on

the screen.

Continued on next page

26 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 5: Node B Software Downloading, Continued

Node B
Software
Step Action
Downloading
Procedure 8 Wait while the 2 steps are automatically performed:
(continued) Step 1: Each file is transferred from the PC to the CCM-U board.
Step 2: Files are transferred from the CCM-U to the others boards.

NOTE: The transfer files takes around:

6 mn for step 1.
4 mn for step 2.

NOTE: On the front panel of the CCM-U the lower rectangle LED is blinking.
At the end of the download, a success message is displayed.
9 Click OK

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 6: New Node B Release Activation

Description This procedure describes how to activate the new software on the Node B.

Preconditions The laptop setting and TIL connections are already done and available.
The Node B software downloading is already perform

Procedure of Execute procedure as per table below

New Node B
release
Activation Step Action
1 In the TIL GUI:
Go to Tools menu
2 Select Software Upgrade
3 Select Activation and iBTS reset

4 Click OK to confirm the reset

5 Click OK to close the last screen
6 Close imperatively the WEB browser in order to take into account the new TIL
JAVA Applet
7 Wait while the Node B Startup

NOTE: The Node B startup takes:

Around 3min for CCM-U
Around 4min for other boards

Continued on next page

28 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 6: New Node B Release Activation, Continued

Procedure of
New Node B
Step Action
release
Activation 8 Apply specific requirement after the Node B release activation
(continued)

If ... Then ...

DBS 4U (with a CCM-U containing Insert all CEM-U
initially a UA7.1 software load)

DBS 4U (with a CCM-U containing No specific requirement to

initially a UA8.1 software load) perform
Follow the next steps
Other Distributed Node B No specific requirement to
perform
Follow the next steps

Procedure of Execute procedure as per table below to verify the latest software release used
the latest
Software
Release Step Action
Verification
1 Re-start the Web browser.
2 Re-start the TIL Applet
3 Verify that the TIL GUI shows the correct Node B configuration and the
latest software release.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 6: New Node B Release Activation, Continued

Procedure of
the latest
Step Action
Software
Release 4 Check the DBS 4U Software reference Version used, which is displayed at
Verification the bottom of the TIL GUI.
(continued)

If ... Then ...

DBS 4U software is the UA07 Redo Procedure of New Node B
Version (UNB07D) release Activation or
Contact the support team to
troubleshoot the software version
issue
Node B software is the UA08 End of this procedure.
Version (UNB08D)

5 End of this procedure

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

30 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 7: Node B Configuration Checks

Description This procedure describes how to check the Node B operational condition prior to start
commissioning.
Check MCA Status
Check Hybrid Iub (HIUB)
Check Node B Alarm Status
Check GPSAM Status
Check RRH Alarm Status

Precondition The TIL must be already connected to the CCM-U

The software must be at the right version

Node B Execute procedure as per table below

Configuration
Checks
Procedure Step Action
1 In the TIL GUI:
Check the MS (MCA status) LED displayed on GPSAM board

If ... Then ...

MS LED is Green (OK) Continue to next step
MS LED is Red (KO) Ask a maintenance operation to the
site coordinator

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 7: Node B Configuration Checks, Continued

Node B
Configuration
Step Action
Checks
Procedure 2 Check that the information contained in the TIL board's GUI complies with the
(continued) Node B configuration:
Check the Software Reference
Check the Node B type
Verify that the Serial Number is the same as the Serial Number given by
the packing list (refer to planning part).

NOTE: If abnormal check occurred, contact the site coordinator before going
on.
3 Check that for Hybrid IuB configuration a maximum of 4 PCM lines is in active
status by checking the HIUB label must be in Green.
4 Check all Boards Alarms condition that there is no alarm.
Check with label AL (Alarm) that no board appears in alarms (RED color).

NOTE: To troubleshoot alarms check the Alcatel-Lucent Node B

Commissioning and Fault Management User Manual: TIL (refer to references
section) and/or contact the support team.

Continued on next page

32 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 7: Node B Configuration Checks, Continued

Node B
Configuration
Step Action
Checks
Procedure 5 Check GPSAM Alarms condition that there is no alarm.
(continued) Right click on the GPSAM board and select Alarms to open the Alarm status.

Exception: expected alarms on GPSAM board are allowed.

User alarm
Door contact alarm

NOTE: To troubleshoot alarms check the Alcatel-Lucent Node B

Commissioning and Fault Management User Manual: TIL (refer to references
section) and/or contact the support team.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 7: Node B Configuration Checks, Continued

Node B
Configuration
Step Action
Checks
Procedure 6 Check RRH Alarms condition that there is no alarm.
(continued) On the GUI xCOB:
Right click on the OIx GUI connected with the RRH select RRH alarms.

7 In the Pop-up menu of RRH view

Right click on the RRH and select Alarms to check that no RRH appears in
alarms (RED color).

NOTE: To troubleshoot alarms check the Alcatel-Lucent Node B

Commissioning and Fault Management User Manual: TIL (refer to references
section) and/or contact the support team.

Continued on next page

34 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 7: Node B Configuration Checks, Continued

Node B
Configuration
Step Action
Checks
Procedure 8 In the Pop-up menu of RRH view,
(continued) Right click on the GUI to select Return to main GUI

Procedure to Execute procedure as per table below to save the I&C parameters to the default path.
Save the I&C
Parameters
Step Action
1 In the TIL GUI:
Go to the I&C Menu
Select Save I&C parameters
2 In the File_name field of the dialog box
Type the name of the file where the old I&C parameter will be saved.

NOTE: This name must be equal to:

old_<NeId>.til with NeId=Serial Number of the Node B.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 7: Node B Configuration Checks, Continued

Procedure to
Save the I&C
Step Action
Parameters
(continued) 3 This command save the default configuration data before commissioning Node
B.
Click Save.

NOTE: The file will be saved in

<Default path>/[email protected]/Icparam folder.
The <Default path> is the path defined during TIL launching.

NOTE: In case of problem, go back to this file in order to restore the default
parameters.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

36 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 8: Node B Setting BTS Parameters

Description This procedure describes how to set BTS parameters with the TIL:
BTS Packaging
Fallback to previous I&C data
GPS Synchronization

Preconditions The laptop setting and TIL connections are already done and available.
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)
The selection of the BTS Packaging parameter must be agreed with the coordinator to get the
expected configuration. (refer to BTS Packaging table from commissioning planning section)

Node B Settings Execute procedure as per table below

BTS Parameters
Procedure
Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters
3 Select BTS

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 8: Node B Setting BTS Parameters, Continued

Node B Settings
BTS Parameters
Step Action
Procedure
(continued) 4 For BTS Packaging
Select the drop-down menu of the BTS packaging according to the Node B
configuration on field.

If Node B configuration Then select the

with... BTSPackaging Parameter...
9326 d2U V2 with RRH or TRDU in: dBTS 2U-V2
Standalone or
Smart or
MBI/MBO (2G) or
PSU or
MBI/MBO (3G) Cabinet
9926 d4U V3 with RRH or TRDU in: dBTS 4U-V3
Standalone or
Smart or
PSU Cabinet
Other distributed Node B Refer to the BTS Packaging table
configuration in Commissioning Planning
section to select the right one.

5 For Fallback to previous I&C data

Select the drop-down menu of the Fallback to previous I&C data

If ... Then select...

Need fallback to previous I&C Activate
data
No need fallback, Deactivate (mainly before the
(Usually used before to send the procedure 18 Sending I&C
parameters to iBTS). Parameters to the NodeB)

Continued on next page

38 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 8: Node B Setting BTS Parameters, Continued

Node B Settings
BTS Parameters
Step Action
Procedure
(continued) 6 For GPS Synchronization if used
Select the drop-down menu of the GPS Synchronization.

If Node B... Then select...

use a GPS Synchronization Activate
do not use a GPS Synchronization Deactivate

7 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 9: Node B Setting RRH Parameters

Description This procedure describes how to set RRH parameters with the TIL

Preconditions The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)
The laptop setting and TIL connections are already done and available.
Use case with RRH (Optical CPRI Link)
Use case with TRDU (Electrical CPRI Link)

Node B Setting Execute procedure as per table below

RRH Parameters
Procedure
Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters
3 Select RRH

Continued on next page

40 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 9: Node B Setting RRH Parameters, Continued

Node B Setting
RRH Parameters
Step Action
Procedure
(continued) 4 For RRH Type:
Select the drop-down menu of the RRH type.

If configuration use... Then select...

9341 RRH 20W CPRI (1,2,3) HSSL (4,5,6)
All Other RRH types CPRI (1,2,3,4,5,6)
TRDU CPRI (1,2,3,4,5,6)

NOTE: The default parameter value is CPRI (1,2,3,4,5,6)

5 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 10: Node B Setting Backhaul Parameters

Description This procedure describes how to set Backhaul parameters with the TIL :
Use case of ATM Iub network (ATM only)
Use case of Hybrid Iub network (IP + ATM simultaneous)
Use case of Iub over IP network (IP only)

Preconditions The laptop setting and TIL connections are already done and available.
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)
The CCM-U must be equipped with the following daughter board according the network used:

If the network is... Then the CCM-U must be

equipped: ...
ATM IuB only With the E1/T1 MDA daughter board.
Hybrid Iub With GE MDA daughter board
(IP + ATM simultaneous connected with (IP connected to the GE MDA and
RJ45 or Optical fiber + E1/T1 PCM) ATM connected on the CCM-U) or
Without GE MDA daughter board.
(IP and ATM connected on the CCM-U only)
IuB over IP only With the GE MDA daughter board.
(IP only connected with RJ45 or Optical
fiber)

Node B Setting Execute procedure as per table below

Backhaul
Parameters
Procedure Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters
3 Select BACKHAUL

Continued on next page

42 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 10: Node B Setting Backhaul Parameters,

Continued

Node B Setting
Backhaul
Step Action
Parameters
Procedure 4 For Type of Incoming Link:
(continued) Select the drop-down menu of the Type of Incoming Link.

If CCM-U is used for... Then select...

ATM Iub E1/T1
(with E1/T1 MDA)
Hybrid Iub E1/T1 and
(With Iub over IP+ ATM Iub) Do the Procedure 14 Node B
Setting Ethernet Parameters
Iub over IP only with Optical fiber STM
(with GE MDA Port 3 or 4)
Iub over IP only Fast Ethernet
(Port 2 of CCM-U) Do the Procedure 14 Node B
(without GE MDA) Setting Ethernet Parameters

Iub over IP only Giga Ethernet

(with GE MDA) Do the Procedure 14 Node B
Setting Ethernet Parameters

5 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 11: Node B Setting PCM E1 Parameters

Description This procedure describes how to set PCM E1 parameters with the TIL.
This procedure applies in case of :
The PCM protection module is present if necessary.
The E1 PCM parameters of the site are different from the factory default parameters.

Preconditions The laptop setting and TIL connections are already done and available.
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)
The following table shows the E1 factory default parameters:

Parameters Name Parameters Value

PCM E1 frame Automatic Multiframe
PCM receive sensitivity (1) Low (short haul)
PCM CRC threshold (1) 915
Protection Module No

NOTE: (1) Must not be modified.

Node B Setting Execute procedure as per table below

PCM E1
Parameters
Procedure Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters

Continued on next page

44 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 11: Node B Setting PCM E1 Parameters, Continued

Node B Setting
PCM E1
Step Action
Parameters
Procedure 3 Select PCM
(continued)

4 For PCM type:

If PCM network type is... Then select...

With E1 PCM E1 and continue to the following
steps up to the end.
With T1 PCM T1 and go to procedure Setting
PCM T1 parameters.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 11: Node B Setting PCM E1 Parameters, Continued

Node B Setting
PCM E1
Step Action
Parameters
Procedure 5 For E1 Adaptation:
(continued)

If E1 PCM adaptation is... Then select...

In 120 Ohms E1 120 Ohms
In 75 Ohms E1 75 Ohms

6 For PCM E1 frame:

If PCM E1 Frame is... Then select...

in ATM only Multiframe
in Hybrid Iub Automatic multiframe
to manage the CRC

7 For PCM receive sensitivity:

Select the default value

If ... Then select...

Value for all PCMs (1 to 8) Select for all PCMs (1 to 8)
Low (short haul) by default or
High (Long haul)
Value per PCM Select for each PCM (1 to 8)
Low (short haul) by default or
High (Long haul)

8 For E1 PCM CRC threshold:

Enter the value 915 if not already done

Continued on next page

46 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 11: Node B Setting PCM E1 Parameters, Continued

Procedure if Execute procedure as per table below if PCM protection module used
PCM Protection
Module used
Step Action
1 For Protection module: (If PCM protection module is present)

If PCM Protection is... Then select parameter

value...
used Yes
not used (by default) No

2 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 47

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 12: Node B Setting PCM T1 Parameters

Description This procedure describes how to set PCM T1 parameters with the TIL.
This procedure applies in case of :
The PCM protection module is present.
The T1 PCM parameters of the site are different from the factory default parameters.

Preconditions The laptop setting and TIL connections are already done and available.
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)
The following table shows the T1 factory default parameters:

Parameters Name Parameters Value

PCM frame Extended super frame
PCM coding B8ZS
LBO 0 to 133 ft (0 to 40m)
PCM receive sensitivity (1) Low (short haul)
PCM receive CRC CRC not used
PCM CRC threshold (1) 320
Protection Module No

NOTE: (1) Must not be modified.

Node B Setting Execute procedure as per table below

PCM T1
Parameters
Procedure Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters

Continued on next page

48 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 12: Node B Setting PCM T1 Parameters, Continued

Node B Setting
PCM T1
Step Action
Parameters
Procedure 3 Select PCM
(continued)

4 For PCM type:

If PCM network type is... Then select...

With E1 PCM E1 and go to procedure Setting
PCM E1 parameters
With T1 PCM T1 and continue to the following
steps up to the end.

5 For PCM T1 frame:

Select the frame profile Extended super frame
6 For PCM coding:
Select the coding profile B8ZS

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 49

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 12: Node B Setting PCM T1 Parameters, Continued

Node B Setting
PCM T1
Step Action
Parameters
Procedure 7 For LBO:
(continued) Select the default value

If LBO parameters... Then select one LBO value

or default value...
Are the same for all PCM T1 for all PCM (from 1 to 8)
according to the length:
0 to 133ft (0 to 40m) < by default
133 to 266ft (40 to 81m)
266 to 399ft (81 to 121m)
399 to 533ft (121 to 162m)
533 to 655ft (162 to 199m)
Are not the same for all PCM T1 for each PCM (from 1 to 8)
according to the length:
0 to 133ft (0 to 40m) < by default
133 to 266ft (40 to 81m)
266 to 399ft (81 to 121m)
399 to 533ft (121 to 162m)
533 to 655ft (162 to 199m)

8 Click Validate on the LBO view

9 For PCM receive CRC:
Select the default value

If ... Then select...

Need PCM receive CRC CRC used
No need PCM receive CRC CRC not used by default

Continued on next page

50 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 12: Node B Setting PCM T1 Parameters, Continued

Node B Setting
PCM T1
Step Action
Parameters
Procedure 10 For PCM receive sensitivity:
(continued) Select the default value

If ... Then ...

Value for all PCMs (1 to 8) Select for all PCMs (1 to 8)
Low (short haul) by default or
High (Long haul)
Value per PCM Select for each PCM (1 to 8)
Low (short haul) by default or
High (Long haul)

11 For PCM CRC threshold:

Enter the value 320 if not already done

Procedure if Execute procedure as per table below if PCM protection module used
PCM Protection
Module used
Step Action
1 For Protection module: (If PCM protection module is present)

If PCM Protection is... Then select parameter

value...
used Yes
not used (by default) No

2 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 51

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 13: Node B Setting PCM&IMA Parameters

Description This procedure describes how to set PCM&IMA parameters with the TIL.
This procedure applies in case of ATM Iub or Hybrid Iub with:
IMA Configuration or
Drop and insert configuration.
PCM carrying OAM link value is different from 1

Preconditions The laptop setting and TIL connections are already done and available.
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)

Node B Setting Execute procedure as per table below

PCM&IMA
Parameters
Procedure Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters
3 Select PCM&IMA

4 For IMA usage parameter:

If... Then select...

Use IMA Configuration IMA and go to dedicated following
Procedure
Do not used IMA Configuration Standard and
do not change other parameters
Use Drop and Insert Configuration Drop & Insert and go to
dedicated following Procedure

5 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Continued on next page

52 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 13: Node B Setting PCM&IMA Parameters,

Continued

Procedure if Execute procedure as per table below if IMA configuration used

IMA
Configuration
used Step Action
1 If the IMA Parameters are already displayed: (for IMA Configuration)
Do not change the parameter value
2 For PCM with OAM link/Synchro in NIP parameter: (for IMA Configuration)
Do not change the parameter value

If PCM Carrying OAM... Then ...

Link is from 1 Do not change the parameter value
at 1
Link is different from 1 Type the new PCM value (2 to 8)

3 For IMA Version parameter: (for IMA Configuration)

Do not change the parameter value

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 53

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 13: Node B Setting PCM&IMA Parameters,

Continued

Procedure if
IMA
Step Action
Configuration
used 4 Press the Send to BTS button only after completion of all parameters setting
(continued) in all relevant tabs.

Continued on next page

54 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 13: Node B Setting PCM&IMA Parameters,

Continued

Procedure if Execute procedure as per table below if Drop & insert configuration used
Drop & Insert
Configuration
used Step Action
1 For Drop & Insert Configuration
In Mask of PCM timeslots used:
Type the hexadecimal value in the rectangular box or
Click inside the box to select the Time Slot (TS).

Details explanation: The hexadecimal value is getting reflected by the

graphic representative TS boxes.

If the box is ... Then means ...

White It is unselected
Grey It is selected
Black It cannot be changed (boxes 0 and
16)

NOTE: TS status can be changed individually by single clicking the TS box.

Status changed will be reflected by the color change.

2 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 55

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 13: Node B Setting PCM&IMA Parameters,

Continued

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

56 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 14: Node B Setting Ethernet Parameters

Description This procedure describes how to set Ethernet parameters with the TIL

Preconditions The laptop setting and TIL connections are already done and available.
The Backhaul Parameters must be already set.
Use case of Hybrid Iub network (IP + ATM simultaneous)
Use case of Iub over IP network (IP only)
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)

Node B Setting Execute procedure as per table below

Ethernet
Parameters
Procedure Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters
3 Select Ethernet

If CCM-U used... Then ...

Without GE MDA Continue to follow steps 4; 5; 6; 7; 8;
9
With GE MDA Go directly to following Procedure if
CCM-U used with GE MDA

4 For VLAN ID:

If ... Then fill the parameter

value...
IP Network used 1
IP Network not used 0 and stop this procedure

5 For VLAN TAGGING:

Do not change the parameter value

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 57

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 14: Node B Setting Ethernet Parameters,

Continued

Node B Setting
Ethernet
Step Action
Parameters
Procedure 6 For LAG/HUBBING:
(continued) Keep the parameter value at No LAG and Hubbing
7 For Eth Port used for IF:
Select the drop-down menu of the Eth Port used for IF.

If Eth Port used is... Then select...

CCM-U RJ45 (Fast Ethernet) Mother Board RJ45
GE MDA RJ45 (Fast Ethernet) MDA RJ45
GE MDA Optical SFP1 MDA SFP1
(Giga Ethernet)
GE MDA Optical SFP2 MDA SFP2
(Giga Ethernet)

Continued on next page

58 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 14: Node B Setting Ethernet Parameters,

Continued

Node B Setting
Ethernet
Step Action
Parameters
Procedure 8 For Eth Port used for Hubbing:
(continued) Do not Change the parameter value
9 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Procedure if Execute procedure as per table below if CCM-U used with GE MDA
CCM-U used
with GE MDA
Step Action
1 For VLAN ID: (If CCM-U used with GE MDA)
Keep the parameter value at 1
2 For VLAN TAGGING: (If CCM-U used with GE MDA)
Do not change the parameter value
3 For LAG/HUBBING: (If CCM-U used with GE MDA)
Select the parameter value at 0
4 For Eth Port used for IF: (If CCM-U used with GE MDA)
Select the parameter value at 4
5 For Eth Port used for Hubbing: (If CCM-U used with GE MDA)
Select the parameter value at 8
6 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 59

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 15: Node B Setting ATM Parameters

Description This procedure describes how to set ATM parameters with the TIL if necessary

Preconditions The laptop setting and TIL connections are already done and available.
Use case of Hybrid Iub network (IP + ATM simultaneous)
Use case of full ATM Iub network (ATM only)
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)

Node B Setting Execute procedure as per table below

ATM
Parameters
Procedure Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters

Continued on next page

60 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 15: Node B Setting ATM Parameters, Continued

Node B Setting
ATM
Step Action
Parameters
Procedure 3 Select ATM Parameters
(continued)

4 Type the OMC-B VP identifier parameter value according to the customer

information CIQ (example here: 1)
5 Type the OMC-B VC identifier parameter value according to the customer
information CIQ (example here: 32)
6 Do not change all other parameters values.
7 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 61

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 16: Node B Setting IP Parameters

Description This procedure describes how to modify the IP Address parameters with the TIL.
This procedure applies in case the IP network is not equipped with a DHCP server.

Preconditions The laptop setting and TIL connections are already done and available.
Use case of Hybrid Iub network (IP + ATM simultaneous)
Use case of Iub over IP network (IP only)
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)

Node B Setting Execute procedure as per table below

IP Parameters
Procedure
Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters
3 Select IP Parameters

4 For the Existence of a DHCP server

Select No
5 For the BTS IP Address
Type the BTS IP Address coming from the CIQ

Continued on next page

62 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 16: Node B Setting IP Parameters, Continued

Procedure
(continued)
Step Action
6 For the OMC-B IP Address
Type the OMC-B IP Address coming from the CIQ
7 For the Sub-network mask
Type the Sub-network mask IP Address coming from the CIQ
8 Do not change the other parameters value of:
the OMC-B port
the BTS port
the Default Gateway IP Address

9 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 63

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 17: Node B NeID Exchange

Description This procedure describes how to retrieve and change the BTS NeID (Serial number) with the
TIL.
The BTS NeID is locally stored from factory into the RUC memory of the Node B.

Preconditions The laptop setting and TIL connections are already done and available.
The Web browser is started with in the URL field the BTS IP@ according to :
>http://BTS IP@/til/index.html
The serial Number of the Node B must be available on the frame NeID label.
The form of parameters based on the CIQ must be documented and available according to the
expected configuration. (refer to form parameters table from commissioning planning section)

Node B NeID Execute procedure as per table below

Exchange
Procedure
Step Action
1 In the main TIL GUI:
Check the SerialNumber which is displayed on the bottom of the page.

If NeID and Serial number... Then ...

Are the same number Do not change the NeID
Are not the same number Continue with the next steps
is 012345 Continue with the next steps

2 In the TIL GUI:

Go to I&C menu
3 Select Change I&C parameters
4 Select BTS

Continued on next page

64 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 17: Node B NeID Exchange, Continued

Node B NeID
Exchange
Step Action
Procedure
(continued) 5 For Serial Number:
Type the right NeID number

NOTE: The NeID (= Serial Number) must be unique in the same network and
different from 012345.

6 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 65

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 18: Sending I&C Parameters to the Node B

Description This procedure describes how to send the I&C parameters to the CCM-U board in order to
update the MCA Module with the TIL

Preconditions The laptop setting and TIL connections are already done and available.
All I&C parameters have been already correctly set with the previous procedures using the TIL

Sending I&C Execute procedure as per table below

Parameters to
the Node B
Procedure Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select Change I&C parameters
3 Select BTS

Continued on next page

66 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 18: Sending I&C Parameters to the Node B,

Continued

Sending I&C
Parameters to
Step Action
the Node B
Procedure 4 For Fallback to previous I&C data:
(continued) Select Deactivate

5 Click Send to BTS

NOTE: During MCA update, a message is displayed

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 67

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 18: Sending I&C Parameters to the Node B,

Continued

Sending I&C
Parameters to
Step Action
the Node B
Procedure 6 Approximately 15 seconds after, a success message is displayed
(continued) Click OK

If ... Then ...

In case of out of range parameter, a Click Close and
message displayed Verify all the parameters to
correct wrong value(s)
In case an error message appears Change the PCM carrying OAM
link.
Contact the support team to
troubleshoot the issue

DO NOT:
Reset BTS Equipment after changing the TIL parameters.
Lets the activation to be performed during the integration.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

68 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 19: Node B reset in Connected Mode

Description This procedure describes how to reset the Node B in connected mode with the TIL
This procedure applies when at least one of I&C parameters has been modified.

Preconditions The laptop setting and TIL connections are already done and available.
At least one of I&C parameters has been modified.

Node B reset in Execute procedure as per table below

Connected
Mode
Procedure Step Action
1 In the TIL GUI:
Go to Tools menu
2 Select BTS reset
3 Select Reset in connected mode

4 Click OK in the Confirm the reset window

5 Click OK in the End of reset window
6 Wait while Node B Startup

NOTE: Node B Startup takes:

Around 3mn for CCM-U
Around 4mn for other board
7 Check that no card appears in alarm.

NOTE: All LEDs on each module should be green, except for MCAs (MCA not
configured).

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 69

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 19: Node B reset in Connected Mode, Continued

Node B reset in
Connected
Step Action
Mode
Procedure 8 In the TIL GUI:
(continued) Go to Connection menu
9 Select Connect to BTS

10 Check if the Node B is now Connected to OMC-B.

If the NodeB is... Then ...

Connected to OMC-B Check that at the bottom of the TIL
GUI shows Connected to OMC-B
Not connected to OMC-B Contact the site coordinator before
going on

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

70 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 20: I&C Parameters Verification

Description This procedure describes how to verify if the new I&C parameters are correctly saved in the
MCA module with the TIL

Preconditions The laptop setting and TIL connections are already done and available.

I&C Parameters Execute procedure as per table below

Verification
Procedure
Step Action
1 In the TIL GUI: to verify that the TIL used is correct:
Check the CCM-U Iub network configuration:
ATM or
Iub over IP or
Hybrid Iub
2 Check that the Software reference corresponds to an UA08.1 SW Version.
3 Check that the iBTS packaging corresponds to the site configuration
4 Check that the Node B TIL GUI is
Not connected to OMC-B and
Config. file not found
5 In the TIL GUI:
Go to I&C menu
6 Select Save I&C parameters

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 71

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 20: I&C Parameters Verification, Continued

I&C Parameters
Verification
Step Action
Procedure
(continued) 7 In the File-name field of the dialog box:
Type the name of the file where the new I&C parameters will be saved.

NOTE: This name must be equal to new_<NeId>.til with NeId=Serial number

of the Node B.
8 Click Save

NOTE: The file will be saved in:

<Default path>/[email protected]/Icparam folder.
The <Default path> is the path defined during TIL launching.

9 Open the file new_<NeId>.til

Continued on next page

72 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 20: I&C Parameters Verification, Continued

I&C Parameters
Verification
Step Action
Procedure
(continued) 10 Verify the I&C parameters you have entered comply with those of the report
sheet.

If ... Then ...

Parameters are not correct Apply again the Sequence of
operations to change the PCM
carrying OAM link.
Parameters are correct Continue the procedure

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 73

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 21: MCA Backup File

Description This procedure describes how to create a MCA backup file with the TIL
This backup file must be stored on a customer server and will be reused exclusively in case of
maintenance action with a double fault (MCA and CCM-U failures).
Handover of the MCA backup file to the customer is coordinated by the TPM.

Preconditions The laptop setting and TIL connections are already done and available.
The I&C parameters verification must be completed.

MCA Backup Execute procedure as per table below

File Procedure

Step Action
1 In the TIL GUI:
Go to I&C menu
2 Select MCA recovery tools

Continued on next page

74 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 21: MCA Backup File, Continued

MCA Backup
File Procedure
Step Action
(continued)
3 In the MCA recovery tools dialog box:
Select Prepare MCA file on CCM Board
Click OK

4 At the end of the operation, a success message is displayed concerning MCA

file creation
Click OK

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 75

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

Proc. 21: MCA Backup File, Continued

MCA Backup
File Procedure
Step Action
(continued)
5 In the MCA recovery tools dialog box:
Select Save MCA file on local disk
Click OK

6 At the end of the operation, a success message is displayed concerning Save

MCA file on local disk
Click OK

Continued on next page

76 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Procedure IEH 521, Section 302

Proc. 21: MCA Backup File, Continued

MCA Backup
File Procedure
Step Action
(continued)
7 Open the MCABackup folder present on your default path to verify if MCA
backup file exists.

NOTE: The number given in the file name must be the same as the serial
number (NEid) of the Node B.

NOTE: The default path is <Default path>/[email protected].

The <Default path> is the path defined during TIL launching.

8 Send by email the MCA backup file to the coordinator TPM.

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

End of With completion of the procedure 21 the commissioning is finished

Commissioning Next is to validate success of commissioning by commissioning tests

April 30, 2013 Alcatel-Lucent Internal 77

Proprietary Use pursuant to Company instruction
IEH 521, Section 302 Commissioning Procedure

This page intentionally left blank.

78 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 310

April 30, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Commissioning Testing

Table of Contents

General ............................................................................................................ 2
Section Description .......................................................................................... 2
Previous Release Date ....................................................................................... 2
Release Notes ................................................................................................. 2
References ........................................................................................................ 3
General ........................................................................................................ 3
Documentation access ...................................................................................... 3
Applicable IEH 521 sections ................................................................................ 3
Applicable Methods documents ............................................................................ 3
Material Requirements ......................................................................................... 5
General ........................................................................................................ 5
Hardware Tool ................................................................................................ 5
Software Tool ................................................................................................. 5
Proc. 22: IP Ping Test ........................................................................................... 6
Description .................................................................................................... 6
Preconditions ................................................................................................. 6
IP Ping Test Procedure ...................................................................................... 6
Supporting Information ..................................................................................... 7
Proc. 23: Final Commissioning Operations .................................................................. 8
Description .................................................................................................... 8
Preconditions ................................................................................................. 8
Final Commissioning Operations Procedure ............................................................. 8
Supporting Information ..................................................................................... 8

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Commissioning Tests ............................... 3
Table 2: Applicable Methods Documents for IEH521 ................................................................ 3
Table 3: Hardware Tools ................................................................................................. 5
Table 4: Software Tools .................................................................................................. 5

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 310 Commissioning Testing

General

Section This section provides detailed information about the individual procedures for commissioning
Description tests of a WCDMA Node B:
Preconditions
Inputs
Outputs
Additional details
Link to commissioning methods document where the procedure is contained

Previous Release New creation

Date

Release Notes New creation: April 2013 under utilization of existing IM documents for UA08.1.

2 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Testing IEH 521, Section 310

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B commissioning tests.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required for WCDMA Node B commissioning tests.
521 sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B

Commissioning Tests

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
399 Node B Commissioning Test Records

Applicable The following methods documents are required to perform the Node B commissioning
Methods
documents
Table 2: Applicable Methods Documents for IEH521

Doc Number Doc Title URL

9YZ-03450- Alcatel-Lucent Node B UA08.1 http://cic.us.alcatel-
4401-RJZZA Commissioning Procedure lucent.com/pdfdocs15/pr
istore214/521872.pdf

3MN-01637- Alcatel-Lucent 9926 Distributed Base Station http://cic.us.alcatel-

0005-REZZA 4U - W-CDMA UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519914.pdf

NN-20500-284 Alcatel-Lucent 9926 Base Band Unit Node B http://cic.us.alcatel-

for W-CDMA UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519912.pdf

NN-20500-110 Alcatel-Lucent 9326 Digital 2U Node B http://cic.us.alcatel-

UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519908.pdf

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 310 Commissioning Testing

References, Continued

Applicable
Methods
Doc Number Doc Title URL
documents
(continued) NN-20500-019 Alcatel-Lucent Node B Commissioning and http://cic.us.alcatel-
Fault Management User Manual: TIL lucent.com/pdfdocs14/pr
istore215/525147.pdf

NN-10300-031 Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-

System - Security Fundamentals lucent.com/pdfdocs14/pr
istore215/525128.pdf

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

4 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Testing IEH 521, Section 310

Material Requirements

General This section describes the hardware and software tools required to perform the commissioning
method.

Hardware Tool The hardware tools listed in the following table are required to perform the commissioning test.

Table 3: Hardware Tools

Hardware Tool Quantity Description
Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

Software Tool The software tool listed in the following table are required to perform the commissioning test

Table 4: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with
WIN7)

April 30, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 310 Commissioning Testing

Proc. 22: IP Ping Test

Description This procedure describes how to test the IP Link with the TIL
This test is not mandatory and is only applicable with an IP Network configuration (Hybrid Iub
or Iub over IP)

Preconditions The laptop setting and TIL connections are already done and available.
The IP link (Hybrid Iub or Iub over IP) is physically connected on both sites.
The IP address of the OMC-B.

IP Ping Test Execute procedure as per table below

Procedure

Step Action
1 In the TIL GUI:
Go to Tools menu
2 Choose IP Ping

Continued on next page

6 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Commissioning Testing IEH 521, Section 310

Proc. 22: IP Ping Test, Continued

IP Ping Test
Procedure
Step Action
(continued)
3 In the IP Ping menu
Check the IP Address to test

4 Click on Ping
5 A IP Ping Process window appears
Click OK
6 A IP Ping test result window appears
Check that the test result indicate in the last IP Ping Result: is Reachable

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

April 30, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 310 Commissioning Testing

Proc. 23: Final Commissioning Operations

Description This procedure describes how to perform final commissioning operations

Preconditions The laptop setting and TIL connections are already done and available.
The Node B has been reset in connected mode
The tests are successfully

Final Execute procedure as per table below

Commissioning
Operations
Procedure Step Action
1 Close the Web browser
2 Remove the cable between Port 1 of the CCM-U and the laptop
3 Close the Node Bs doors
4 Finish filling out the report sheet available in the Commissioning Test
Records section 399

NOTE: All non-compliance cases have to be physically spotted on site and

described
5 Leave one copy of the report sheet on site and send one to the coordinator.
6 Refer to the coordinator for any corrective action.
7 Clean the site
8 Now the Node B commissioning is finish and this Node B is ready to be
integrated in an existing UTRAN, according to the UTRAN version used and
following the Integration Procedure IEH521 or :
Alcatel-Lucent Node B UA08.1 Integration in an existing UTRAN

Supporting NOTE: Detailed information about the procedure is available in the documents listed in the
Information section References.

8 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 320

Jun 14, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Node B RF Path Validation

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Preconditions ................................................................................................. 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation access ...................................................................................... 5
Applicable IEH 521 sections ................................................................................ 5
Material Requirements ......................................................................................... 6
General ........................................................................................................ 6
Tools to Check the Antenna Link .......................................................................... 6
Tools for RF Measurement of Antenna Link ............................................................. 7
Complementary Tools ....................................................................................... 8
Site Master Description ..................................................................................... 8
Technician Skills Required .................................................................................. 9
Site Preconditions .......................................................................................... 11
Aerial Installation Verification .............................................................................. 12
Description .................................................................................................. 12
Preconditions ............................................................................................... 12
Physical Antenna and TMA Checks Procedure ......................................................... 12
Verification of the Cable Run ............................................................................ 14
Measurement of the Antenna Azimuth .................................................................... 15
Description .................................................................................................. 15
Preconditions ............................................................................................... 15
Measurement of the Antenna Azimuth Procedure .................................................... 16
Process for Node B RF Path Validation .................................................................... 18
Description .................................................................................................. 18
Preconditions ............................................................................................... 18
Process for Node B RF Path Validation ................................................................. 18
Self Calibration ................................................................................................ 20
Description .................................................................................................. 20

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Preconditions ............................................................................................... 20
Frequency Band Selection Procedure................................................................... 21
One Port Calibration Procedure ......................................................................... 21
Two Port Calibration Procedure ......................................................................... 22
Cable Loss Measurement ..................................................................................... 24
Description .................................................................................................. 24
Preconditions ............................................................................................... 24
Cable Loss Measurement Procedure .................................................................... 25
VSWR Measurement with 50 Load ........................................................................ 26
Description .................................................................................................. 26
Preconditions ............................................................................................... 26
VSWR Measurement with 50 Ohms Load Procedure .................................................. 27
TMA Measurement ............................................................................................. 28
Description .................................................................................................. 28
Preconditions ............................................................................................... 28
TMA Measurement Procedure ............................................................................ 29
TMA and Antenna VSWR Measurement ..................................................................... 31
Description .................................................................................................. 31
Preconditions ............................................................................................... 31
TMA and Antenna VSWR Measurement Procedure .................................................... 32
VSWR Measurement of the Whole Line .................................................................... 34
Description .................................................................................................. 34
Preconditions ............................................................................................... 34
VSWR Measurement of the whole Line ................................................................. 35
Distance to Fault Location (DTF) ........................................................................... 37
Description .................................................................................................. 37
Preconditions ............................................................................................... 37
Calibration Procedure ..................................................................................... 38
Measurement Procedure .................................................................................. 39
Control Datasheet Process ................................................................................... 41
Description .................................................................................................. 41
Preconditions ............................................................................................... 41
Creation of a Data Base ................................................................................... 42
Measurement Transfer into the Database ............................................................. 43
Distance to Fault ........................................................................................... 45
Node B RF Path Validation Report .......................................................................... 49
Description .................................................................................................. 49
Preconditions ............................................................................................... 49
Node B RF Path Validation Report Procedure ......................................................... 49

List of Figures

Figure 1: Measurement Process View ................................................................................ 19

List of Tables

Table 1: Applicable IEH 521 Sections for Node B RF Path Validation ............................................ 5
Table 2: Tools to Check the Antenna Link ............................................................................ 6

2 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Table 3: Tools for RF Measurement .................................................................................... 7

Table 4: Complementary Tools ......................................................................................... 8

Jun 14, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

General

Section This section provides detailed information to test the physical and electrical characteristics of
Description antennas, feeders and TMA (if used).
This section have to be performed:
On all sites
On all types of antennas with TMA
On all types of wireless networks such as a GSM 900/1800 or WCDMA 2100
On all types of installations: roof, masts etc.
After the antenna, TMA and Feeder installation and
Before BTS/ Node B connection
Before all the section Commissioning Procedure.

They allow the radio link to be characterized, and help prevent mistakes during radio coverage
optimization.

Preconditions Only Technicians who are qualified to work on masts with the appropriate safety equipment
can do this task.
The staff must have general knowledge in radio propagation and specific training for these
types of measurements.

Previous Release No
Date

Release Notes New creation: June 2013 under utilization of existing IM documents for UA08.1.

4 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
Node B RF Path Validation.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required for Node B RF path validation.
521 sections

Table 1: Applicable IEH 521 Sections for Node B RF Path Validation

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
310 Node B Commissioning Test
320 Node B RF Path Validation
399 Node B Commissioning Test Records

NOTE: The documents can be fetched from the GPEC portal website:
https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Jun 14, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Material Requirements

General This section describes the hardware tools and specific skills required to perform the Antenna
link validation with TMA.

Tools to Check The tools listed in the following table are required to perform the physical check of antenna
the Antenna link.
Link Table 2: Tools to Check the Antenna Link
Hardware Tool Quantity Description
Geometer Compass 1 Such as universal compass from Topochaix
or equivalent
(Topochaix compass also includes a
dendrometer)
Inclinometer or 1 To measure the tilt
Dendrometer
Antenna aligner 1 Such as Cell Aligner (Optional)
Decameter 1 10 meters minimum
Precise map of the site 1 scale 1/50 000 for rural area
scale 1/15 000 for urban area

Continued on next page

6 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Material Requirements, Continued

Tools for RF The tools listed in the following table are required to perform the RF measurement of antenna
Measurement of link.
Antenna Link Table 3: Tools for RF Measurement
Hardware Tool Quantity Description
Torque Wrench 7/16 1
Torque Wrench N 1
Site Master series 1 Set Data analysis software,
(from ANRITSU) Soft carrying case,
(S331E-S332E-S361E- Users guide.
S362E)
with valid calibration date (less than one
or equivalent year ago).
Site Master Charger 1 Set Rechargeable battery,
AC/DC power supply,
12.5V automobile cigarette lighter
adapter,
Set of reference 1 Set (1 meter Low phase shift)
measurement cables (1m)

Precision load 50, 1 Set load 50 (with N connector)

load 50 (with7/16 connector)
Tool set for site master 1 Set (short circuit, open, 50 )
calibration
Laptop PC with post 1
processing software
RS232 cable 1 To connect between the Site Master and
the Laptop PC

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Material Requirements, Continued

Complementary The tools listed in the following table are required to perform the validation of antenna link.
Tools

Table 4: Complementary Tools

Tool Quantity Description
Keys to open the Node B 1 set If necessary
Camera with Zoom 1
GPS for positioning 1 (optional)
Adapted Individual 1 set (Safety protection for climber)
protective equipment
Set of waterproofing 1 set

Site Master The Site Master is a cable & antenna analyzer handheld it must have two port analyzer and
Description bias Tee options.
It is constituted by a keyboard to select mode and measurements type and to enter the data
and a LCD screen to visualize results on all selected bandwidths.

The tool works on a point-to-point mode with a maximum of definition points to keep an
accurate view.
Use sub bandwidth such as transmission and reception band, which will increase the result
definition.

Continued on next page

8 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Material Requirements, Continued

Site Master
Description
(continued)
DO NOT: Do not use on large analysis bandwidth to avoid data loss.

Before any measurement, the first step is to calibrate the tool and enter parameters of the
measurements to ensure a correct reference.
This includes the self-calibration on the frequency band that will be analyzed and the control of
the cable parameters in the equipment database in order to perform a good distance to fault
(DTF).
Requirement of equipment:
Site Master Series with a valid calibration date (less than one year ago).
Complete set of connectors, load and measurement cables.

Technician The antenna validation measurements take place on roof, terrace or masts. This kind of job
Skills Required requires special training for the staff.
The technician who undertakes the measurements and checks of antenna links must be an
RF specialist able to determine if the results are realistic or not.

When the experience skills are... Then the technician will ...
in cable and antennas Give the technical bases for this activity
in site engineering Allow to ensure that the antenna mounting
is correctly installed
in topography Allow to check the azimuths of the
antennas, and ensure these are correct.
In test equipment Perform all the measurements and he will
ensure measurements are correctly
performed.

HIGH FREQUENCY MAGNETIC FIELDS:

When the measurements are... Then the technician ...

performed on a site where radio equipment will be in safety condition
is powered off
performed near equipment whose antenna must avoid working in front of the antenna
is radiating. and will respect the safety distance from the
radiation

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Material Requirements, Continued

Technician Skills
Required
(continued)

WARNING:

When the job is... Then each technician ...

performed on a site where it is necessary to Must be trained and qualified for the job.
climb on roof, terrace or mast to access the Must be an RF specialist able to
equipment. determine if the results are realistic or not.
Must hold the appropriate climbing
qualification certificates on site for
working at height.
Must have a special medical inspection
related to this kind of job
Must have an Individual Safety
Equipment required by the safety
standards.
Must require at least two qualified people
on site at all times for safety reasons.
performed on a site where it is not Must be trained and qualified for the job.
necessary to climb : Must be an RF specialist able to
ground floor or determine if the results are realistic or not.
into a secure zone

Continued on next page

10 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Material Requirements, Continued

Site
Preconditions

DO NOT: Do not access to the roof, terrace or mast when the weather conditions
are difficult : (Strong wind, Storm, Strong rain, Snow)

WARNING: Measurements are performed on a site where radio equipment is

powered off.

WARNING: In general manner, measurements are performed before the first

connection of the Base station. However, be careful, before any base station disconnection, it
is necessary to stop the BTS transmission (switch off or PA locked).

HIGH FREQUENCY MAGNETIC FIELDS:

Equipment connecting to transmit antenna generates high frequency magnetic fields when
operating.
Avoid remaining in the immediate vicinity of the antennae when the Node B is in operation.
The high density of energy can damage the eyes and certain tissues of the human body
exposed to radiations.
The station must be shut down when work is performed on transmitting antenna.

Jun 14, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Aerial Installation Verification

Description This procedure describes how to check the physical elements to evaluate the quality of the
installation before specific checks

Preconditions The antenna, TMA and feeder installation are already done.
Two qualified technicians on site at all times when work involve to climb up to the RF module
and cable.
Required equipment:
Copy of the site design
Map (scale under 1/50 000 rural or 1/15000 urban area)
Decameter (10 meters minimum)
Compass (Topochaix universal or equivalent)
Equipment to measure the tilt (as inclinometer or dendrometer)
Antenna aligner like Cell Aligner or equivalent (optional).

Physical Execute procedure as per table below to check the physical antenna and TMA.
Antenna and
TMA Checks
Procedure Step Action
1 Check the side mounting brackets
2 Check the name and fixing of the antennas
3 Check the position of the antennas compared to the building or mast
4 Check the antenna height

Continued on next page

12 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Aerial Installation Verification, Continued

Physical
Antenna and
Step Action
TMA Checks
Procedure 5 Check the antenna azimuth with a compass and map
(continued)
6 Check and measure the tilt with a Inclinometer or Dendrometer

If tilt is ... Then ...

With a mechanical system Measure the value of Tilt with a
Inclinometer or Dendrometer .
Fill the tilt value into the Test
report section
With an electrical system as a RETA Check the value of Tilt shown in
(Remote Electrical Tilt Antenna) graduated rod of the RETA
located below the antenna.
Fill the tilt value into the Test
report section

NOTE: The measurement of Tilt is expressed in degrees and half degree.

7 Check the good TMA installation and grounding

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Aerial Installation Verification, Continued

Verification of Execute procedure as per table below to verify the cable run.
the Cable Run

Step Action
1 Check the location and fixing of the jumpers (high and low) and feeders
2 Check the bending radius is within the cables specifications
3 Check the connection of the grounding kit
4 Note the location of the feeder and jumpers at both ends of the cable run, and
compare with the site folder
5 After measurements, do and check the waterproofing of all the connectors.

NOTE: this last check will be done when all the measurements are finished

14 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Measurement of the Antenna Azimuth

Description This procedure describes how to perform azimuth measurement of the antenna.
The azimuth measurement of an antenna requires a good precision in order to get the
predicted coverage of the site.
Several ways exist to check the azimuths:
Use of compass
Use of Cell aligner systems

Preconditions The technician must have a good experience of topography for the azimuth measurement.
The azimuth measurement requires accurate tools as described in materiel requirements
section.

IMPORTANT: An important point is the risk of magnetic variation due to the

metallic structure of the mast or building.

CAUTION: The compass use can introduce errors.

Avoid :
Positioning the compass near a large metallic mass,
Referencing a point that is close to your position, it is preferable to use a reference point
close to the horizon.
Compass near the eye: Error of reading
The measurement near a radiating antenna: Error due to the magnetic radiating fields.

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Measurement of the Antenna Azimuth, Continued

Measurement of Execute procedure as per table below

the Antenna
Azimuth
Procedure Step Action
1 Mark on a precise map a set of reference points around the site
2 Calculate the angle between the nearest point and the azimuth of the antenna

3 Fix the alignment tool on the antenna to control or to re-azimuth.

4 Measure the azimuth starting from the ground of the mast and check the angle
of several reference points.
5 Do the same measurements to check the same reference points while on the
mast by the antenna to be aligned.

Continued on next page

16 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Measurement of the Antenna Azimuth, Continued

Measurement of
the Antenna
Step Action
Azimuth
Procedure 6 Adjust the azimuth of the antenna according to the following rules:
(continued)

When ... Then ...

The difference created by the This correction will be used when
structure can then be calculated aligning the antennas.
When the tool is fixed on the Rotate the antenna in order to push
antenna it on its azimuth by alignment with
the reference point.

NOTE: This type of tool is sold by most of antenna manufacturers. It requires

knowing with precision a reference point on a topographic map.
7 The reference point of the azimuth measurement is an essential point.

If the azimuth of the cell Then the azimuth measured

planning is referenced with on site...
...
magnetic North is the right value without correction
need
the geographical North or the North Must be corrected for magnetic
of a map variation.

Jun 14, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Process for Node B RF Path Validation

Description This process describes how to perform the Node B RF Path validation of the electrical
measurements done with a Site Master.

Preconditions The installation has been fully completed (including TMA connection)
The technician must have a good experience of the test equipment for the RF electrical
measurement.
The RF electrical measurement requires accurate tools as a Site Master (chosen inside Site
Master Series reference from ANRITSU) described in materiel requirements section.

Process for Execute the process for Node B RF Path validation in the chronological order as per table
Node B RF Path below and refer to figure 1
Validation

IMPORTANT: The site Master can only deliver reliable results if it is calibrated.
The calibration is dependent on ambient temperature. It is very important to proceed with the
self-calibration on each site whenever necessary.

Stage Description
1 Self Calibration on each site whenever necessary:
Frequency band selection
One port calibration
Two port calibration
2 Perform the Feeders Measurement Procedure to measure feeder losses (Down
activity)
With open or short circuit
With load 50 Ohms
3 Perform the TMA Testing to measure the TMA Gain & filter (Top activity)
4 Perform the VSWR measurement of TMA and Antenna (Top activity)
5 Perform the Global VSWR measurement of Feeder, jumper, TMA and antenna
(Down activity)
6 Perform the Distance To Fault (DTF) of the entire line (Down activity)
7 Perform the Waterproofing of all connectors.

Continued on next page

18 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Process for Node B RF Path Validation, Continued

Global Process
for RF
Electrical Figure 1: Measurement Process View
Measurements
(continued)

Jun 14, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Self Calibration

Description This procedure describes how to perform the self calibration of the Site Master to optimize
measurement accuracy.
Before any measurement:
Calibrate the Site Master tool
Enter parameters of the measurements to ensure a correct reference.
This includes the self-calibration on the frequency band that will be analyzed and control of the
cable parameters in the equipment database in order to perform a good DTF.

Preconditions The technician must have a good experience of the test equipment for the RF electrical
measurement.
The RF electrical measurement requires accurate tools as a Site Master (chosen inside Site
Master Series reference from ANRITSU) described in materiel requirements section.
All specifications described in the Site Design document must be available:
Maximum value of the VSWR of the antennas (specified by the manufacturer)
Expected feeder losses
Gain of TMA
Acceptable values of the VSWR of the line (antenna and feeder) depend on feeder length.

IMPORTANT: The site Master can only deliver reliable results if it is calibrated.
The calibration is dependent on ambient temperature. It is very important to proceed with the
self-calibration on each site whenever necessary.
Two types of calibration are necessary to calibrate the Site Master depending on use or not
two ports.
NOTE: This functionality is climatic conditions dependent.

Continued on next page

20 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Self Calibration, Continued

Frequency Execute procedure as per table below to select the frequency band
Band Selection
Procedure
Step Action
1 From the main menu (Escape | Clear).
Press on FREQ.
2 Press on F1 and enter the starting frequency of the band
(in MHz with the keyboard ).
3 Press on ENTER to validate.
4 Press on F2 and enter the end of the bandwidth band
(in MHz with the keyboard ).
5 Press on ENTER to validate.

One Port Execute procedure as per table below to calibrate the first Port.
Calibration NOTE: For the calibration it is necessary to use Site Master and extension cable Test Port
Procedure stabilized in Phase.

Step Action
1 Press on START CAL, the instruction CONNECT OPEN appears.
2 Connect the OPEN component.
3 Press on ENTER, the site master makes the measurement
The instruction CONNECT SHORT appears.
4 Connecter the SHORT component.
5 Press on ENTER, the site master makes the measurement.
The instruction CONNECT LOAD appears.
6 Connect the precision load
7 Press on ENTER, the site master makes the measurement and calculate the
calibration.
8 Check on the upper left side of the screen that the calibration is ON.

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Self Calibration, Continued

Two Port Execute procedure as per table below to calibrate the two Port.
Calibration
Procedure
NOTE: For the calibration it is necessary to use Site Master and the two extensions cables
Test Port which are stabilized in Phase.

Step Action
1 Perform the frequency band selection procedure to select the appropriate
frequency range.
2 Press on START CAL, the instruction CONNECT OPEN TO RF Out appears.
3 Connect the OPEN component.
4 Press on ENTER, the site master makes the measurement
The instruction CONNECT SHORT TO RF Out Port appears.
5 Connecter the SHORT component.
6 Press on ENTER, the site master makes the measurement.
The instruction CONNECT LOAD on both Ports appears.
7 Connect the precision load
8 Press on ENTER, the site master makes the measurement and calculate the
first calibration step.
The load message ISOLATION appears.
The instruction CONNECT RF Out Port to RF In Port appears.
9 Remove the Loads connect the both cable with N female adaptor and press
ENTER.
Message THRU appears.

22 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Continued on next page

Self Calibration, Continued

Two Port
Calibration
Step Action
Procedure
(continued) 10 Check on the upper left side of the screen that the calibration is ON.

11 The site master is ready for measurements.

Jun 14, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Cable Loss Measurement

Description This procedure describes how to perform the cable loss measurement.
Cable Loss measurement gives automatically the loss value of the cable in dB over the given
frequency bandwidth. Then the result is averaged to know the cable attenuation.

The loss is measured across the entire working bandwidth of the system, and can be
performed either on Open or Short circuit.

Preconditions The technician must have a good experience of the test equipment for the RF electrical
measurement.
The RF electrical measurement requires accurate tools as a Site Master (chosen inside Site
Master Series reference from ANRITSU) described in materiel requirements section.
The Site Master tool must be power on.

IMPORTANT: In case of TMA, the VSWR measurement will verify only the path till
the entry port of the TMA (not including the RF link till the antenna)

Continued on next page

24 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Cable Loss Measurement, Continued

Cable Loss Execute procedure as per table below

Measurement
Procedure
Step Action
1 Connect the tool (Site Master) to the feeder
2 From the main menu (Escape | Clear).
3 Check that the calibration is ON (upper left side of the screen)
4 Press OPT
5 Press B1 to select CL (or RL on older Site Master)
6 Press AUTOSCALE, the measurement goes on
7 Press SCALE | LIMIT and move on the horizontal limit with the arrows ,
validate with ENTER and determine the average value of CL or RL.

If ... Then ...

only the RL is available Divide the average value by 2 and
fill in the control datasheet.
only the CL is available Keep the average value as it is and
fill in the control datasheet

8 Press SAVE DISPLAY and give a number or name to the measurement

(Depending on the Site Master version) and Press ENTER.

Jun 14, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

VSWR Measurement with 50 Load

Description This procedure describes how to perform the VSWR measurement with 50 Load.
Before connecting the antenna, we have to be sure that the feeder has no fault and is adapted
for a 50 load.

Preconditions The technician must have a good experience of the test equipment for the RF electrical
measurement.
The RF electrical measurement requires accurate tools as a Site Master (Reference S251C
ANRITSU) described in materiel requirements section.
The Site Master tool must be power on.
An accurate 50 load must be mounted at the extremity of the feeder to perform the VSWR
measurement.

Continued on next page

26 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

VSWR Measurement with 50 Load, Continued

VSWR Execute procedure as per table below

Measurement
with 50 Ohms
Load Procedure Step Action
1 Verify and connect the tool (Site Master) to the feeder.
2 From the main menu (Escape | Clear).
3 Check that the calibration is ON (upper left side of the screen)
4 Press OPT
5 Press B1 to select SWR
6 Press AUTOSCALE, the measurement goes on
7 Press ESCAPE | CLEAR then MARKER.
8 Press M1 PEAK, the M1 marker indicates the max value of the VSWR.
9 Press SAVE DISPLAY, and give a number or a name to the measurement
and press ENTER
10 Fill in the control datasheet.

NOTE: The result depends on feeder length and diameter. If the attenuation is high, the
VSWR is low.

If ... Then VSWR ...

Feeder length is above or equal to 30meters must be under 1.35 0.5 (RL 17 dB)
Feeder length is less than 30 meters or could be around 1.4 0.5 (RL 15.6 dB)
above 10 meters
Jumpers and antenna must be the value 1.5 max (RL=14 dB)
( in case of RRH used, connected with a (limited to the antenna VSWR, for outdoor)
jumper only)

Jun 14, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

TMA Measurement

Description This procedure describes how to perform the TMA measurement.

This measurement is realized on mounted TMA. It is performed to control the TMA
characteristics (Amplification and filtering).

Preconditions Two technicians must have the climbing equipment and qualification certificates on site.
The technician must have a good experience of the test equipment for the RF electrical
measurement.
All frequency band F1 and F2 must be specified and available in the Site Design document.

IMPORTANT: Be careful F1 and F2 are chosen depending on network and

frequency band used.

Required equipment:
Site Master S251c (with Build-in Bias Tee Option10B)
2 measurement RF cables
External Anritsu Power supply to feed the TMA
N-7/16 adaptors (x2) Nf -7/16m

NOTE: This measurement is performed on whole frequency range (emission + reception).

IMPORTANT: Be careful also to the topology of TMA connectors.

Measurements are made between TMAs antenna (input) and BTS port (output).

Continued on next page

28 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

TMA Measurement, Continued

TMA Execute procedure as per table below

Measurement
Procedure
Step Action
1 Connect the external power supply and the 2 test port cables

The following scheme presents the measurement for single TMA.

For a double TMA measure twice at each step.

2 Set up the Site Master as follows:

Site Master ON Insertion gain 30dBm
Frequency range Freq | Dist F1 and F2
3 Perform site master two port calibration
4 Connect RF out to antenna port of TMA
5 Connect RF in to RX connector of TMA
6 Press Sys key option Bias Tee to turn on the Bias Tee
7 Perform the measure.
8 Play with Amplitude key to adjust the result gain level
9 Save the result

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

TMA Measurement, Continued

TMA
Measurement
Step Action
Procedure
(continued) 10 Fill in the control datasheet.
11 The result must be close to the following:

NOTES:
Marker M1 indicates the receive band of the TMA. The level above the 0dB
reference level is the gain of the TMA
Marker M2 indicates the transmit band of the TMA where there is no gain
and give insertion loss of the TMA
12 Analyze the measurements of the TMA Gain.

If ... Then ...

TMA fault is detected The faulty equipment must be
replaced and measurements
redone.
TMA gain is correct and coherent Continue to the next procedure

13 After the TMA measurement, disconnect the RF In measurement cable.

30 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

TMA and Antenna VSWR Measurement

Description This procedure describes how to perform the TMA and antenna VSWR measurement.

Preconditions Two technicians must have the climbing equipment and qualification certificates on site.
The technician must have a good experience of the test equipment for the RF electrical
measurement.
Required equipment:
Site Master series (with Build-in Bias Tee Option10B)
2 measurement RF cables
External Anritsu Power supply to feed the TMA
N-7/16 adaptors (x2) Nf -7/16m

NOTE : Measurement is done on downlink frequency range

IMPORTANT: Be careful, when frequency range is changed, calibration must be

redone.

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

TMA and Antenna VSWR Measurement, Continued

TMA and Execute procedure as per table below

Antenna VSWR
Measurement
Procedure Step Action
1 Connect the antennas jumper to the TMA to perform VSWR measurement on
downlink.

2 Set up the Site Master as follows:

3 From the main menu (Escape | Clear).
Check that the calibration in ON (upper left side of the screen)
4 Press OPT
5 Press B1 to select SWR
6 Press AUTOSCALE, the measurement goes on
7 Press ESCAPE | CLEAR then MARKER.
8 Press M1PEAK, the M1 marker indicates the max value of the VSWR.

Continued on next page

32 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

TMA and Antenna VSWR Measurement, Continued

TMA and
Antenna VSWR
Step Action
Measurement
Procedure 9 Press SAVE DISPLAY, and give a number or a name to the measurement
(continued) and press ENTER
10 Fill in the control datasheet.
11 Analyze the VSWR measurements of the TMA and antenna.

If ... Then ...

a fault is detected the faulty equipment must be
replaced and measurements
redone.
the VSWR is correct and coherent continue to the next procedure

Jun 14, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

VSWR Measurement of the Whole Line

Description This procedure describes how to perform the VSWR measurement of the whole line.
When the TMA have been tested and checked as OK and verify that the whole line with the
antenna and feeder is valid.

Preconditions The technician must have a good experience of the test equipment for the RF electrical
measurement.
Required equipment:
Site Master Series (with Build-in Bias Tee Option10B)
2 measurement RF cables
External Anritsu Power supply to feed the TMA
N-7/16 adaptor

NOTE : Measurement is done on downlink frequency range only

Continued on next page

34 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

VSWR Measurement of the Whole Line, Continued

VSWR Execute procedure as per table below

Measurement of
the whole Line
Step Action
1 Connect all the antenna line elements except the Node B.
2 Connect the feeder to the TMA to perform a global VSWR measurement on
downlink.
3

4 Set up the Site Master as follows:

5 From the main menu (Escape | Clear).
Check that the calibration in ON (upper left side of the screen)
6 Press OPT
7 Press B1 to select SWR
8 Press AUTOSCALE, the measurement goes on

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

VSWR Measurement of the Whole Line, Continued

VSWR
Measurement of
Step Action
the whole Line
(continued) 9 Press ESCAPE | CLEAR then MARKER.

10 Press M1PEAK, the M1 marker indicates the max value of the VSWR.
11 Press SAVE DISPLAY, and give a number or a name to the measurement
and press ENTER
12 Fill in the control datasheet.
13 Analyze the Global VSWR measurements of the whole line (antenna, feeder
and jumpers connected).

If ... Then ...

the measurement is correct and waterproofing can be installed on
coherent the connectors
a fault is detected the faulty equipment must be
replaced and measurements
redone.

14 Install the waterproofing on the connectors

36 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Distance to Fault Location (DTF)

Description This procedure describes how to perform the distance to fault (DTF) location
This measurement allows the Technician to:
Detect discontinuities in the line
Give a good technical status of the line from its installation and of its functioning
Give a reference in case of problem during its lifetime
Give the proof that the fault was not present at the installation of the site

NOTE: If VSWR measurement is good (in accordance with the specification), DTF will be
good. However, this measurement could show risk area (if exist on the line tested) not actually
in fault but close to it in near future.

NOTE: When a problem occurs on the transmission line, the Distance To Fault measurement
(DTF) gives the location of the fault.

Preconditions The technician must have a good experience of the test equipment for the RF electrical
measurement.
Required equipment:
Site Master Series (with Build-in Bias Tee Option10B)
1 measurement RF cables
N-7/16 adaptor

NOTE: DTF is more efficiently analyzed when performed in SWR mode.

NOTE: If this measurement is performed with the line loaded at 50 , it gives the fault location
on the line.

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Distance to Fault Location (DTF), Continued

Calibration Execute procedure as per table below

Procedure

Step Action
1 From the main menu (Escape/Clear).
2 Check that the calibration in ON (upper left side of the screen)
3 Press DIST and then Press D1.
4 Enter the minimum distance in meter with the keyboard or the arrows .
5 Then press ENTER.
6 Press D2.
7 Enter the maximum distance in meter with the keyboard.
8 Validate with ENTER and MORE.
9 Press CABLE to select the coaxial cable from the menu or press the function
key LOSS and PROP V to enter the cable parameters of loss and propagation
velocity, if the cable type isnt referenced in the tool database.
10 Press ENTER to validate.

Continued on next page

38 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Distance to Fault Location (DTF), Continued

Measurement Execute procedure as per table below

Procedure

Step Action
1 From the main menu (Escape|Clear).
2 Press AUTO SCALE, the measurement start
3 Use the MARKER to mark the significant values.
4 Press SAVE DISPLAY, and record the measurement.
5 Fill in the control datasheet.

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Distance to Fault Location (DTF), Continued

Measurement
Procedure
Step Action
(continued)
6 Analyze the result of the Distance to Fault measurement on the line.

If ... Then ...

The measurement is correct and The acceptance document can be
coherent with the site design signed by the customer
document. representatives.
The waterproofing is installed on
connectors
The measurement is not correct and Contact the site coordinator to plan
not coherent with the site design troubleshooting operations.
document.

40 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Control Datasheet Process

Description This procedure describes how to use and analyze the recorded traces.
The control Datasheet is the document in which measurements results, observations, and
remarks are stored.
It confirms the validity of a site and/or traces the problems.
The Site Master software or Master Software Tool (MST) is used to analyze the recorded
traces.
Main Functions:
Measurements download
Database management
Measurement drawing
Distance to Fault calculation
Smith chart
Printing

Preconditions The technician must have a good experience of the test equipment for the RF electrical
measurement.
Required equipment:
Site Master S251c
RS232 cable
Laptop PC

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Control Datasheet Process, Continued

Creation of a Execute procedure as per table below

Data Base

Step Action
1 Select File/Database with the mouse in the main menu.
The following window appears :

2 Click Create New Database then OK

3 Give a name to the database, now it is created.

Continued on next page

42 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Control Datasheet Process, Continued

Measurement Execute procedure as per table below

Transfer into
the Database
Step Action
1 Connect the RS232 cable between the Site Master and the PC and switch on
the Site Master.
2 Select Capture I Capture Multiple to Database from the main menu.

3 Select the database in which measurements have to be transferred.

4 Fill in the field of the session and click OK

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Control Datasheet Process, Continued

Measurement
Transfer into
Step Action
the Database
(continued) 5 Enter the number of the measurement to download

6 The download is processing and then the following database window appears.

7 Move into the recording with the arrows

8 The DISPLAY button draws the measurement
9 The EDIT button allows to edit the measurement description.

Continued on next page

44 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Control Datasheet Process, Continued

Distance to The Distance To Fault (DTF) can be calculated from the VSWR or RL measurement
Fault Execute procedure as per table below

Step Action
1 Draw the VSWR measurement of the desired record by clicking DISPLAY

2 Select Tools | Fault Find or the icon

and the following windows appears :

Jun 14, 2013 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Continued on next page

Control Datasheet Process, Continued

Distance to
Fault (continued)
Step Action
3 Select the type of cable
4 Enter the start and stop distance to analyze
5 Select the format of data (VSWR, Return Loss, milliRho)
6 Click OK
7 The calculated curve shows the status of the line as a function of distance.
The following example shows a feeder connected to an X-polarized antenna in
VSWR format:

The results of the treatments are integrated in the site validation report.

Continued on next page

46 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Control Datasheet Process, Continued

Distance to
Fault (continued)
Step Action
8 Analyze the result of the Distance to Fault measurement on the line without
TMA.

Expected result:
Example of interpretation where M1, M2, M3, M4 correspond to the
connectors between Antenna, Feeder and Jumpers

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 47

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

Control Datasheet Process, Continued

Distance to
Fault (continued)
Step Action
9 Analyze and deduce the distance between the lower jumper and the antenna
connector.

If ... Then the DTF measurement

...
TMA used stop at the input of the TMA
TMA not used stop at the input of the Antenna

NOTE: The distance result of the treatments is integrated in the site validation
report.

NOTE: This initial status of line (DTF) is mandatory inside the site
validation report. This status of line can be reused to analyze the RF
environment evolution during the life of this site.

48 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Node B RF Path Validation IEH 521, Section 320

Node B RF Path Validation Report

Description This procedure describes how to perform the Node B RF Path validation report.
The control datasheet is a site document. It is written on site and its main function is the
acceptance of the antenna validation. Nevertheless in order to complete it, a validation report
is written.

Preconditions The technician must have a good experience of the test equipment for the RF electrical
measurement.
Required equipment:
All measurements results
Laptop PC

Node B RF Path Execute procedure as per table below

Validation
Report
Procedure Step Action
1 Fill the Antenna Validation Report with the following information items:
Administrative data of the site (name, address, localization, access, type)
Technical folder of the measurements (operators name, used means with
calibration date and serial number)
Checking of the performed controls
Picture of the site
Pictures of the antennas
All the different measurements curves (VSWR, cable loss, distance to fault)

2 The report must be updated as per table below to troubleshoot the Node B RF
Path if necessary.

If ... Then ...

a fault seen on one of the antenna This fault will be mentioned and
links The DTF added to the report.
a corrective action has been New measurements are also added
performed on: to the report.
one of the antenna links or
the azimuth or
the tilt

Jun 14, 2013 Alcatel-Lucent Internal 49

Proprietary Use pursuant to Company instruction
IEH 521, Section 320 Node B RF Path Validation

This page intentionally left blank.

50 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 331

December 15, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

U2100 + U900 Daisy Chain Check Procedure

Table of Contents

General ............................................................................................................ 3
Section Description .......................................................................................... 3
Previous Release Date ....................................................................................... 3
Release Notes ................................................................................................. 3
References ........................................................................................................ 4
General ........................................................................................................ 4
Documentation access ...................................................................................... 4
Applicable IEH 521 sections ................................................................................ 4
Applicable documents ....................................................................................... 5
Tools Requirements ............................................................................................. 6
General ........................................................................................................ 6
Hardware Tool ................................................................................................ 6
Software Tool ................................................................................................. 6
U2100 + U900 Daisy Chain Procedure Overview ............................................................ 7
Reference of radio configuration Procedures Mandatory ........................................... 7
U2100 + U900 Daisy Chain Checklists ........................................................................ 8
Purpose ........................................................................................................ 8
Checklist Customization .................................................................................... 8
Remote Operations Checklist .............................................................................. 8
U2100 + U900 Daisy Chain Parameters Form ............................................................... 9
General ........................................................................................................ 9
Node B Parameters Required Prior to Check Node B Configuration ................................. 9
Node B: Frequency Band .................................................................................... 9
Radio Module Configuration U2100 + U900 Daisy Chain ........................................... 10
U2100 + U900 Daisy Chain Visual Check Procedure...................................................... 11
Description .................................................................................................. 11
Preconditions ............................................................................................... 11
U2100 + 900 Daisy Chain configuration 1 sector .................................................... 12
U2100 + 900 Daisy Chain configuration 3 sectors ................................................... 13
Cabinet configurations BTS packaging parameter .................................................. 14
U2100 + U900 Daisy Chain Configuration Check procedure ......................................... 15
Record Sheets / Checklists - On Site ....................................................................... 20

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

Report Sheet -Node B: Frequency Band ................................................................ 20

Report Sheet Radio and digital Module Configuration U2100 + U900 Daisy Chain .......... 20
Report Sheet -Radio Module location Configuration U2100 + U900 Daisy Chain .............. 21
List of Figures

Figure 2: U2100 + U900 Daisy Chain Configuration for one sector .............................................. 12
Figure 3: U2100 + U900 Daisy Chain Configuration for 3 sectors................................................ 13
Figure 1: U2100 + U900 Daisy Chain Configuration Supported in 9100 MBS ................................... 14

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Commissioning Tests ............................... 4
Table 2: Applicable Methods Documents LR13.x for IEH521 ....................................................... 5
Table 3: Hardware Tools ................................................................................................. 6
Table 4: Software Tools .................................................................................................. 6
Table 5: Operational Procedures to Check the Radio Configuration ............................................. 7
Table 6: Sequence of Operation Used to Check the Radio Configuration ....................................... 8
Table 7: Node B Parameters Required Prior to Node B Commissioning .......................................... 9
Table 8: UMTS Frequency Band ......................................................................................... 9
Table 9: Radio configuration (U2100 + U900 Daisy Chain) ....................................................... 10
Table 10: UMTS Frequency Band...................................................................................... 20
Table 11: Radio and Digital Module configuration ................................................................. 20
Table 12: Dual Band U2100 + U900 Daisy Chain Configuration with TRDU / MC-TRX........................ 21

2 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

General

Section This section provides detailed information about the individual procedures for commissioning
Description tests of a WCDMA Node B for the U2100 and U900 daisy chain feature
Preconditions
Inputs
Outputs
Additional details
Link to commissioning methods document where the procedure is contained

Previous Release New creation

Date

Release Notes New creation: December 2013 under utilization of existing IM documents for LR13.1.

December 15, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B commissioning tests.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required for WCDMA Node B commissioning tests.
521 sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B

Commissioning Tests

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
399 Node B Commissioning Test Records

Continued on next page

4 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

References, Continued

Applicable The following methods documents are required to perform the Node B commissioning and
documents integration in LR13.x

Table 2: Applicable Methods Documents LR13.x for IEH521

Doc Number Doc Title URL
9YZ-04088- Alcatel-Lucent Node B http://cic.us.alcatel-
0095-RJZZA Commissioning Procedure lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=55054&prc=Unknown
9YZ-04088- Alcatel-Lucent Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault lucent.com/cgi-
Management User Manual: TIL bin/design2006/dbaccessprototyp
e1/01?key=55050&prc=Unknown
9YZ-04088- Alcatel-Lucent Node B Integration in http://cic.us.alcatel-
0098-RJZZA an existing UTRAN lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=55057&prc=Unknown
9YZ-04088- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
0014-PCZZA Management System User Guide lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=54991&prc=Unknown
9YZ-04088- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
0015-TQZZA Management System - Security lucent.com/cgi-
Fundamentals bin/design2006/dbaccessprototyp
e1/01?key=54992&prc=Unknown
WCDMA IM 04- Alcatel-Lucent TRDU Configuration http://cic.us.alcatel-
6149 (X+Y, star and Daisy Chain mode & lucent.com/cgi-
Mixity d2U/d4U + TRDU) bin/design2006/dbaccessprototyp
Installation Guide e1/01?key=68875&prc=Unknown

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

December 15, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

Tools Requirements

General This section describes the hardware and software tools required to perform the commissioning
method.

Hardware Tool The hardware tools as listed in the following table are required to perform the commissioning
test.

Table 3: Hardware Tools

Hardware Tool Quantity Description

Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

Software Tool The software tools as listed in the following table are required to perform the commissioning
test

Table 4: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with
WIN7)

6 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

U2100 + U900 Daisy Chain Procedure Overview

Reference of The following table lists all operational procedures to be performed to check the radio
radio configuration with U2100 + U900 in daisy chain.
configuration
Procedures
Mandatory Table 5: Operational Procedures to Check the Radio Configuration
Step Operation Opt/ Proc. Remark
Mand.
1 U2100 + U900 Daisy Chain M Proc. 1
Visual Check Procedure

December 15, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

U2100 + U900 Daisy Chain Checklists

Purpose Checklists are available to support and document the flow of operations before, during and post
the check of the radio configuration with U2100 + U900 Daisy Chain for
On site activities
Node B and RF parameters
Remote (TIL) operations
and document the successful completion of the radio configuration with U2100 + U900 Daisy
Chain before customer acceptance

Checklist The checklists of IEH521 are generic and can be used as basis for further modifications and
Customization enhancements as per specific customer / market requirements.

Remote Sequence of operations for use by remote operations to verify success of mandatory and
Operations optional steps
Checklist

Table 6: Sequence of Operation Used to Check the Radio Configuration

Procedure Condition Expected result To OK NOK
use?
U2100 + U900 Daisy Chain Mandatory The TIL GUI result is compliant to
Visual Check Procedure the expected final configuration Y/N
Type U2100 + U900 Daisy Chain

8 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

U2100 + U900 Daisy Chain Parameters Form

General This section lists all parameters, necessary to perform the visual check of the radio
configuration with U2100 + U900 Daisy Chain and do the commissioning.
The forms of parameters are based on the CIQ and must be documented by the coordinator
according to the expected parameters and configuration.
The forms of parameters must be sent by email or must be available on a link.

Node B The following table is the list of Node B parameters required prior to visual check the radio
Parameters configuration with U2100 + U900 Daisy Chain.
Required Prior
to Check Node B
Configuration Table 7: Node B Parameters Required Prior to Node B Commissioning
Node B parameter Value for Node B
Node B IP address
Configuration
Sub-network mask
Software upgrade on Node B: Yes / No
Node B - Software version (LR13.1 minimum)
Hardware reference
BTS Parameters:

Node B: The following table gives the UMTS Frequency Band used by the Node B and the Radio
Frequency Module.
Band

Table 8: UMTS Frequency Band

UMTS Frequency (Band)
2100Mhz 900Mhz
(Band I) (Band VIII)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

U2100 + U900 Daisy Chain Parameters Form, Continued

Radio Module The following table gives the usable radio Configuration with U2100 + U900 Daisy Chain.
Configuration
U2100 + U900
Daisy Chain Table 9: Radio configuration (U2100 + U900 Daisy Chain)

Radio configuration Module Used?

MC-TRX 900Mhz (3G only) Y/N
MC-TRX 900Mhz (3G only) Y/N
TRDU 2100Mhz Y/N
SUMx Y/N
9100 MBS MID Indoor 5 3GOO Y/N
9100 MBS MID Outdoor 2E 3GOO Y/N
D2U Y/N
D4U Y/N

10 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

U2100 + U900 Daisy Chain Visual Check Procedure

Description This procedure describes the way to visually check the configuration for U2100 + U900 Daisy
Chain feature with the help of TIL GUI.
This check is not mandatory and is only applicable if TRDU + MC-TRX are used in U2100 +
U900 Daisy Chain configuration.
The U2100 + U900 Daisy Chain is required to support a specific Ran Sharing configuration,
between 3 operators:
Operator 1: 2100 MHz (TRDU), 1 carrier
Operator 2: 900 MHz (MCTRX 3G), 1 carrier
Operator 3: 900 MHz (MCTRX 3G), 1 carrier

Preconditions The Node B + TRDU + MCTRX are already fully Integrated

The U2100 + U900 Daisy Chain feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.
The WCDMA Digital Controller must be d2U V2 (xmodules) or d2U V3 (emodules) (d4U is
not supported in cabinets 2G)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

U2100 + U900 Daisy Chain Visual Check Procedure,

Continued

U2100 + 900 The mixity and daisy chain mode must be supported by the Node B configuration using:
Daisy Chain TRDU 2100 Mhz
configuration 1
sector MC-TRX 900 Mhz in 3G only (without 2G BSC connection)
SUMx

Figure 1: U2100 + U900 Daisy Chain Configuration for one sector

Continued on next page

12 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

U2100 + U900 Daisy Chain Visual Check Procedure,

Continued

U2100 + 900 The following diagram outlines the daisy chaining for 3 sectors
Daisy Chain
configuration 3
sectors Figure 2: U2100 + U900 Daisy Chain Configuration for 3 sectors

NOTE: Refer to Alcatel-Lucent TRDU Configuration (X+Y, star and Daisy Chain mode & Mixity
d2U/d4U + TRDU) Installation Guide for more information about the connection instruction.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

U2100 + U900 Daisy Chain Visual Check Procedure,

Continued

Cabinet BTS Packaging parameter must be 3Goo

configurations
BTS packaging
9100 MBS MID Indoor 5
parameter
9100 MBS MID Outdoor 2E

Figure 3: U2100 + U900 Daisy Chain Configuration Supported in 9100

MBS

Continued on next page

14 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

U2100 + U900 Daisy Chain Visual Check Procedure,

Continued

U2100 + U900 Perform the following steps to visually check the U2100 + U900 daisy chain configuration with
Daisy Chain TIL GUI.
Configuration
Check
procedure Step Action
1 Visually check that the information contained in the TIL board's GUI complies
with the Node B configuration:

If check... Then parameter must be...

The software reference UNB131xxxxx (minimum software
load (LR13.1)
The Node B type for 9100 MBS 9100 MBS MID Indoor 5 3GOO
Indoor (iBTS Packaging)
The Node B type for 9100 MBS 9100 MBS MID Outdoor 2E 3GOO
Outdoor (iBTS Packaging)
Freq Band 1 2100Mhz
Freq Band 2 (Dual Band) 900Mhz

NOTE: If abnormal checking results occur then contact the site coordinator
before going on.
2 Visually check that the TIL board's GUI shows the SUMx
3

Check that no Alarms appear in alarms (RED color) on the SUMx.

NOTE: To troubleshoot alarms check the Alcatel-Lucent Node B

Commissioning and Fault Management User Manual or contact the support
team.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

U2100 + U900 Daisy Chain Visual Check Procedure,

Continued

U2100 + U900
Daisy Chain
Step Action
Configuration
Check 4 Visually check RRH Alarms condition that there is no alarm on the GUI of
procedure xCOB by right click on the OIx GUI connected with the Radio Module then
(continued) select RRH alarms.

5 Check TRDU and MC-TRX are alarm free by

in the Pop-up menu of Radio Modules view

Right click on the Radio Modules and select Alarms to visually check
neither TRDU nor MC-TRX appear in alarm condition (RED color).

NOTE: To troubleshoot alarms check the Alcatel-Lucent Node B

Commissioning and Fault Management User Manual or contact the support
team.

Continued on next page

16 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

U2100 + U900 Daisy Chain Visual Check Procedure,

Continued

U2100 + U900
Daisy Chain
Step Action
Configuration
Check 6 Check the daisy chain configuration on each CPRI link by use of OIx on the
procedure TIL GUI to display the U2100 + U900 Daisy Chain configuration supported:
(continued) OIx number is 1:
Applied on the OI4, OI5 and OI6.
Confirms the daisy chain is not used on these CPRI links 4, 5 and 6 (star
mode only) is compliant with the expected final configuration.
Olx number is 2:
Applied on the OI1, OI2 and OI3.
Confirms the daisy chain is used on these CPRI links 1, 2 and 3 is compliant
with the expected final configuration with 2 radio modules.
Olx number is 3:
Confirms the daisy chain is used on these CPRI links with 3 radio modules.
Check the CPRI links connection to solve the issue or contact the support
team to be compliant with the expected final configuration.
Olx number is 0:
Confirms that there is no radio module connected.
Check the CPRI connection to solve the issue or contact the support team to
be compliant with the expected final configuration.
Examples of displays:

NOTE: The theoretical view (from TIL GUI) on each CPRI link must be the
following, to be aligned with the typical U2100 + U900 Daisy Chain
configuration.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

U2100 + U900 Daisy Chain Visual Check Procedure,

Continued

U2100 + U900
Daisy Chain
Step Action
Configuration
Check 7 Check the following constraint and limitations are met:
procedure The first 3 CPRI ports (1 to 3) of CCM-U are used for TRDU (not MC-TRX)
(continued) with 2 TRDU per port in daisy chain (STSR x+y).
The last 3 CPRI ports (4 to 6) of CCM-U are reserved for MC-TRX (1 MC-
TRX per port).
The number of TRDU per port can be up to 3, with the constraint of 6 TRDU
total per NodeB.

8 Return to main GUI by clicking on Return to main GUI button

Continued on next page

18 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

U2100 + U900 Daisy Chain Visual Check Procedure,

Continued

U2100 + U900
Daisy Chain NOTE: The U2100 + U900 Daisy Chain is clearly identified in radio configuration with the TIL
Configuration GUI.
Check
procedure
(continued) If TIL GUI ... Then ...
Does not identify the U2100 + U900 Contact the support team to
Daisy Chain in radio configuration. troubleshoot the issue.

Has clearly identified the U2100 + The radio configuration is

U900 Daisy Chain in radio compliant with the expected final
configuration. Node B configuration
Go to section 310 to finalize the
Node B commissioning testing.
Or/ and go to section 410 to
finalize the Node B Integration
testing.
And fill the Test records with the
identified Radio Configuration.

December 15, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

Record Sheets / Checklists - On Site

Report Sheet - Select the UMTS Frequency Band used by the Node B.
Node B:
Frequency
Band Table 10: UMTS Frequency Band

UMTS Frequency (Band)

900Mhz 2100Mhz
(Band VIII) (Band I)

Report Sheet Fill the radio and digital module Configuration used with U2100 + U900 Daisy Chain.
Radio and
Table 11: Radio and Digital Module configuration
digital Module
Configuration
U2100 + U900
Daisy Chain Radio configuration Module Used?
MC-TRX 900Mhz (3G only) Y/N
MC-TRX 900Mhz (3G only) Y/N
TRDU 2100Mhz Y/N
SUMx Y/N
9100 MBS MID Indoor 5 3GOO Y/N
9100 MBS MID Outdoor 2E 3GOO Y/N
D2U Y/N
D4U Y/N

Ce sujet continue page suivante

20 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
U2100 + U900 Daisy Chain Check Procedure IEH 521, Section 331

Record Sheets / Checklists - On Site, Suite

Report Sheet - Fill the location (11, 12, 21, 22, 31, 32, 41, 51, 61) of radio modules used into the final
Radio Module configuration U2100 + U900 Daisy Chain.
location
Configuration
U2100 + U900 Table 12: Dual Band U2100 + U900 Daisy Chain Configuration with
Daisy Chain TRDU / MC-TRX

Dual Band Configurations CPRI Port # (on CCM-U)

Config. #

Fibers

RF Modules Band A (2100) Band B (900)

Chain
Daisy
STSR
1 2 3 4 5 6
3x1
1 11 21 31
(TRDU60-21)+
U2100+ DC
U900 3x1
6 12 22 32
Daisy ( MCTRX 900)
Chain 1+1
3x1
- 41 51 61
( MCTRX 900)

December 15, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 331 U2100 + U900 Daisy Chain Check Procedure

This page intentionally left blank.

22 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 399

Jun 14, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Commissioning Test Records

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation access ...................................................................................... 5
Applicable IEH 521 sections ................................................................................ 5
Applicable Methods documents ............................................................................ 6
Commissioning Checklists ...................................................................................... 7
Purpose ........................................................................................................ 7
Checklists overview of Node B Commissioning Tests .................................................. 7
Checklists overview of Node B RF Path Validation ..................................................... 7
Checklist customization ..................................................................................... 7
Used Documents ................................................................................................. 8
Used Documents .............................................................................................. 8
Reporting Sheets / Checklists - On Site ..................................................................... 9
Report Sheet -Node B: Frequency Band .................................................................. 9
Report Sheet -Node B Equipment Parameter ........................................................... 9
Report Sheet -Radio Module Equipment ............................................................... 10
Report Sheet -Inventories Equipment .................................................................. 10
Report Sheet -PCM Parameters .......................................................................... 11
Report Sheet -IP Parameters ............................................................................. 12
Report Sheet -IP Ping Test................................................................................ 12
Sign-Off Sheet .................................................................................................. 13
Description .................................................................................................. 13
Meaning of Sign-Off Sheet ................................................................................ 13
Sign-Off Sheet .............................................................................................. 13
Archiving of Reports ....................................................................................... 13
Node B RF Path Validation Reporting Sheets / Checklists - On Site .................................. 14
Report Sheet Antenna and TMA Description .......................................................... 14
Report Sheet -Site Master Self Calibration ............................................................ 14

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

Report Sheet - Node B RF Path Validation ............................................................. 15

VSWR definition ............................................................................................ 16
VSWR analysis ............................................................................................... 16
Return Loss (RL) definition ............................................................................... 17
Return Loss (RL) analysis ................................................................................. 17
Cable Loss definition ...................................................................................... 17
Cable Loss analysis ......................................................................................... 17
Distance To Fault (DTF) definition ...................................................................... 18
Distance To Fault analysis ................................................................................ 18
Sign-Off Sheet for Node B RF Path Validation ............................................................ 19
Description .................................................................................................. 19
Meaning of Sign-Off Sheet ................................................................................ 19
Sign-Off Sheet .............................................................................................. 19
Archiving of Reports ....................................................................................... 19

2 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Commissioning ....................................... 5
Table 2: Applicable Methods Documents for IEH521 ................................................................ 6
Table 3: Edition and Version of the Documents Used ............................................................... 8
Table 4: UMTS Frequency Band ......................................................................................... 9
Table 5: BTS Packaging ................................................................................................... 9
Table 6: Radio Module Equipment .................................................................................... 10
Table 7: Inventories Parameters ...................................................................................... 10
Table 8: PCM Parameters .............................................................................................. 11
Table 9: IP Parameters ................................................................................................. 12
Table 10: IP Ping Test .................................................................................................. 12
Table 11: Commissioning Checklists Customer Sign-off ........................................................ 13
Table 12: Antenna and TMA Description ............................................................................ 14
Table 13: Site Master Calibration..................................................................................... 14
Table 14: Node B RF Path Validation ................................................................................ 15
Table 15: Node B RF Path Validation Checklists Customer Sign-off .......................................... 19

Jun 14, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

General

Section This section provides overview on Checklists for commissioning planning, execution and
Description testing.

Previous Release New Creation: 30 April 2013

Date

Release Notes Update: 14 June 2013 - addition of reporting sheets for Node B RF path validation.
New creation: April 2013 under utilization of existing IM documents for UA08.1.

4 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B commissioning.

Documentation Links to applicable documents can be found under:

access

https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in table 1 below are required for WCDMA Node B commissioning.
521 sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B

Commissioning
Section Description
301 WCDMA Node B Commissioning Planning
302 WCDMA Node B Commissioning
320 WCDMA Node B RF Path Validation
310 WCDMA Node B Commissioning Test

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

References, Continued

Applicable The following methods documents are required to perform the Node B Commissioning
Methods
documents
Table 2: Applicable Methods Documents for IEH521
Doc Number Doc Title URL
9YZ-03450- Alcatel-Lucent Node B UA08.1 http://cic.us.alcatel-
4401-RJZZA Commissioning Procedure lucent.com/pdfdocs15/pr
istore214/521872.pdf

3MN-01637- Alcatel-Lucent 9926 Distributed Base Station http://cic.us.alcatel-

0005-REZZA 4U - W-CDMA UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519914.pdf

NN-20500-284 Alcatel-Lucent 9926 Base Band Unit Node B http://cic.us.alcatel-

for W-CDMA UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519912.pdf

NN-20500-110 Alcatel-Lucent 9326 Digital 2U Node B http://cic.us.alcatel-

UA08.1 Maintenance Guide lucent.com/pdfdocs15/pr
istore214/519908.pdf

NN-20500-019 Alcatel-Lucent Node B Commissioning and http://cic.us.alcatel-

Fault Management User Manual: TIL lucent.com/pdfdocs14/pr
istore215/525147.pdf

NN-10300-031 Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-

System - Security Fundamentals lucent.com/pdfdocs14/pr
istore215/525128.pdf

NOTE: The documents can be fetched from the GPEC portal website:
https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

NOTE: The documents can be fetched from the CIC portal website:
http://www.cic.lucent.com/

6 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

Commissioning Checklists

Purpose Checklists are available to support and document the flow of operations before, during and
post commissioning for
On-site activities
And document successful completion of Node B commissioning and commissioning testing by
customer acceptance.
The report sheet must be filled out by operator after successful Node B commissioning tests.

Checklists Used documents

overview of
Reporting Sheet/Checklists - on site
Node B
Commissioning Node B: Frequency Band
Tests Node B Equipment Parameter
Radio Module Equipment
Inventories Equipment
PCM Parameters
IP Parameters
IP Ping Test
Sign-Off Sheet

Checklists Node B RF Path Validation Reporting Sheet/Checklists - on site

overview of
Site Description
Node B RF Path
Validation Stakeholders Information
Antenna and TMA Frequency Band
Antenna and TMA Description
Site Master Self Calibration
Antenna Link Validation with TMA
Sign-Off Sheet for Node B RF Path Validation

Checklist The checklists of IEH521 are generic and can be used as basis for further modifications and
customization enhancements as per specific customer / market requirements.

Jun 14, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

Used Documents

Used Document which versions of required documents are used for Node B commissioning.
Documents When the applicable document is used the edition and version must be filled by the site
operator.

Table 3: Edition and Version of the Documents Used

Reference Applicable Documents Ed./Vers

IEH521 Alcatel-Lucent Installation Engineering Handbook
521 WCDMA Node B (iBTS Global Market)
9YZ-03450-4401- Alcatel-Lucent Node B UA08.1 Commissioning
RJZZA Procedure
3MN-01637-0005- Alcatel-Lucent 9926 Distributed Base Station 4U -
REZZA W-CDMA UA08.1 Maintenance Guide
NN-20500-284 Alcatel-Lucent 9926 Base Band Unit Node B for W-
CDMA UA08.1 Maintenance Guide
NN-20500-110 Alcatel-Lucent 9326 Digital 2U Node B UA08.1
Maintenance Guide
NN-20500-019 Alcatel-Lucent Node B Commissioning and Fault
Management User Manual: TIL
NN-10300-031 Alcatel-Lucent 9353 Wireless Management System
- Security Fundamentals

8 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

Reporting Sheets / Checklists - On Site

Report Sheet - Select the UMTS Frequency Band used by the Node B.
Node B:
Frequency
Band Table 4: UMTS Frequency Band
UMTS Frequency (Band)
850Mhz 900Mhz 1900Mhz AWS 2100Mhz
(Band V) (Band VIII) (Band II) (Band IV) (Band I)

Report Sheet - Select the Node B Equipment type used. (BTSpackaging)

Node B
Equipment
Parameter Table 5: BTS Packaging
Indoor Cabinet Outdoor Cabinet Standalone Smart / PSU
Configuration cabinet
9311 Macro ID1 9311 Macro OD1 9326 d2U V1 PSU Small S6
9311 Macro ID2 9311 Macro OD2 9326 d2U V2 PSU Medium S6
9315 Street 9926 BBU (d2U V3) PSU Md4 (d2U/d4U)
9100 MBI3 ev2 (3G) 9100 MBO1 ev2 (3G) 9926 DBS 4U 9941 Smart (d2U)
9100 MBI5 ev2 (3G) 9100 MBO1 ev. (2G) 9941 Smart (d4U)
9100 MBI5 (2G) 9100 MBO2 ev. (2G)
9944 Smart Base
Station S8k OD
9944 Smart Base
Station S18k OD

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

Reporting Sheets / Checklists - On Site, Continued

Report Sheet - Select the Radio Module Equipment used.

Radio Module
Equipment
Table 6: Radio Module Equipment
Radio Module Indoor Radio Module Outdoor
TRDU 9341 RRH20w (HSSL)
MC TRDU 9341 RRH40w
9341 RRH60w
9341 RRH2x40
9341 RRH2x60

Report Sheet - Fill the Inventories parameters used.

Inventories
Equipment
Table 7: Inventories Parameters
Parameters Values
Current Network Release (UNB)
NeID (Serial Number) (6 digits) __ __ __ __ __ __
User Label
Inventories parameters (not mandatory)
If half GSM upgrade towards GSM/UMTS
RU Name (30 characters max.)
PEC code (16 characters max.)
Manufacturing date (4 characters max.) __ __ __ __

Continued on next page

10 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

Reporting Sheets / Checklists - On Site, Continued

Report Sheet - Select the PCM Parameters if used:

PCM
Parameters
Table 8: PCM Parameters
PCM Parameters Used
PCM Protection Module used? Yes / No (Default value)
PCM Carrying OAM Link (Value from 1 to 8) 1 I 2 I 3 I 4 I 5 I 6 I 7 I 8
E1 PCM Parameters: PCM Frame? Multiframe (Default value)
Single frame
Automatic multiframe
IMA Usage Parameter Standard (Default value)
Drop & Insert
IMA
In case of Drop & (Hexadecimal value:
Insert: (8 digits) 0 x __ __ __ __ __ __
Mask of PCM TS 0x_ _ _ _ _ _
used?
Or bit mapping 0 I 1 I 2 I 3 I 4 I 5 I 6 I 7
(check box if TS 8 I 9 I 10 I 11 I 12 I 13 I 14 I 15
used) 16 I 17 I 18 I 19 I 20 I 21 I 22 I 23
24 I 25 I 26 I 27 I 28 I 29 I 30 I 31

NOTE: TS 0 & 16 can never be used for E1.

T1 PCM PCM Frame? Extended Super Frame (Default value)
Parameters: Single frame
Node B ready to be OMC-B (Default value)
connected to? AMI
PCM receive CRC? Yes / No (Default value)
LBO range for all 0: 0 to 133ft (0 to 40m) (Default value)
PCM? 1: 133 to 266ft (40 to 81m)
2: 266 to 399ft (81 to 121m)
3: 399 to 533ft (121 to 162m)
4: 533 to 655ft (162 to 199m)
LBO per PCM? 1 I 2 I 3 I 4 I 5 I 6 I 7 I 8

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

Reporting Sheets / Checklists - On Site, Continued

Report Sheet - Fill the IP Parameters if DHCP is not used:

IP Parameters

Table 9: IP Parameters
IP Parameters Value
DHCP server used? (Default value) --> Yes / No
Node B IP address ___.___.___.___
OMC-B IP address ___.___.___.___
Sub-Network Mask ___.___.___.___

Report Sheet - Fill the result of the IP Ping test:

IP Ping Test

Table 10: IP Ping Test

IP Ping Test Test Result
IP Ping Test required? Yes / No
IP Ping Test Status? Successful / Unsuccessful

Additional comments/remarks:

12 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

Sign-Off Sheet

Description Sign-Off sheet has to be completed to finally document acceptance of the commissioning
results.

Meaning of Sign- Completion of the Sign-Off sheet represents the finalization of the Node B commissioning
Off Sheet activity and is meant to serve for customer acceptance of the commissioning Node B.

Sign-Off Sheet Sign off sheet for successful commissioning.

The following sign-off confirms that all required checklists proof successful commissioning of
the Node B.

Table 11: Commissioning Checklists Customer Sign-off

Commissioner Coordinator / Customer
engineer on-Site Representative
activities
Company Name

Function
Name

Signature

Date

Archiving of All reporting sheets for an individual Node B commissioning must be archived.
Reports All reporting sheets must be available to be reused if necessary during the integration section.
Individual contractual agreements with customer may require the original to hand over to the
customer for archiving.

Jun 14, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

Node B RF Path Validation Reporting Sheets /

Checklists - On Site

Report Sheet The site technician must fill the following table by data from Antenna and TMA description as it
Antenna and is available on site
TMA
Description
Table 12: Antenna and TMA Description
Cell 1 2 3 4 5 6
Antenna type
Antenna Height
Azimuth (in Degree)
Tilt (in Degree)
Feeder Length
Upper Jumper Length
Lower Jumper Length
Grounding Kit
(OK/NOK)
TMA Type
Upper Jumper TMA
Length

NOTE:
Azimuth: defines the horizontal plane of the antenna radiation pattern
Tilt: vertical orientation, used to reduce interference.

Report Sheet - The site technician must fill the following table according to the self calibration which is
Site Master Self performed on the Site Master before the validation of the Node B RF Path.
Calibration

Table 13: Site Master Calibration

Frequency Band Selection
Frequency Band Starting Frequency of the Band (MHz)
Selection
End of the Bandwidth Band (MHz)
Site Master One Port Calibration (OK/NOK)
Calibration
Two Port Calibration (OK/NOK)
For TMA Insertion Gain (dB)
Measurement

Continued on next page

14 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

Node B RF Path Validation Reporting Sheets /

Checklists - On Site, Continued

Report Sheet - The site technician must fill the following table according to the measurements done on site to
Node B RF Path validate the Node B RF Path.
Validation

Table 14: Node B RF Path Validation

Cell 1 2 3 4 5 6
Cable attenuation
measurement
Registration number of
measurements

Cable VSWR
measurement
Registration number of
measurements

Cable VSWR
measurements
w/ 50 Ohm load
Registration number of
measurements

TMA Gain and Filter

measurement
Registration number of
measurements

TMA and Antenna

VSWR measurement
Registration number of
measurements

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

Node B RF Path Validation Reporting Sheets /

Checklists - On Site, Continued

Report Sheet -
Node B RF Path
Cell 1 2 3 4 5 6
Validation
(continued) Global line VSWR (in
dB) registration
Registration number of
measurements

Distance to Fault
Location
Registration number of
measurements

VSWR definition VSWR:

allows characterizing the adaptation of the transmission line
is defined by the following ratio :

VSWR analysis The following table can be used to analyze the measured VSWR value

When ... Then ...

the impedance of the charge is different from VSWR is increased
the impedance of the line.
VSWR is low or close to 1.0. the transmission line is matched
(This is a theoretical value and acceptance
criteria define the limit value.)

Continued on next page

16 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

Node B RF Path Validation Reporting Sheets /

Checklists - On Site, Continued

Return Loss (RL) Return loss (RL):

definition
is a way to define the adaptation of a system
is expressed in dB
represents the ratio of the forwarded power on the reflected power, hence, the non-
consumption of power by the charge due to its non-adaptation.

Return Loss (RL) The following table can be used to analyze the measured Return Loss (RL) value
analysis

When the Return Loss Then the adaptation...

measurement value ...
is highest is best
is lowest is worst because the reflection is increasing

Cable Loss Cable loss is the difference of power measured in dB between

definition
entrance of feeder
output of feeder
for a given wave.

Cable Loss The following table can be used to analyze the measured cable loss value
analysis

When ... Then ...

the line is completely non-adapted the totality of the forward signal on the line is
reflected.
the wave received at the entry of the cable is the measurement of the RL gives the
affected by twice the feeder attenuation. feeder loss for the round trip.
to know the cable loss, the value of the RL
has to be divided by 2.

Continued on next page

Jun 14, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

Node B RF Path Validation Reporting Sheets /

Checklists - On Site, Continued

Distance To DTF (Distance To Fault):

Fault (DTF)
Measurement which allows to localize a problem along a transmission line
definition
Measurement which detects a punctual alteration of the line and gives the distance from the
measurement point.

Distance To When you perform a DTF measurement then you

Fault analysis
you can detect:
a bad connector or
a damage of the feeder
you must take some precaution concerning
the calibration of the equipment and
the choice of the right propagation coefficient for the measured cable

Additional comments/remarks:

18 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
Commissioning Test Records IEH 521, Section 399

Sign-Off Sheet for Node B RF Path Validation

Description Sign-Off sheet has to be completed to finally document acceptance of the Node B RF Path
Validation

Meaning of Sign- Completion of the Sign-Off sheet represents the finalization of the Node B RF Path Validation
Off Sheet activity and is meant to serve for customer acceptance of the Antenna Link Validation with
TMA.

Sign-Off Sheet Sign off sheet for successful commissioning.

The following sign-off confirms that all required checklists proof successful Node B RF Path
Validation.

Table 15: Node B RF Path Validation Checklists Customer Sign-off

Commissioner Coordinator / Customer

engineer on-Site Representative
activities
Company Name

Function
Name

Signature

Date

Archiving of All reporting sheets for an individual Node B RF Path Validation results must be archived.
Reports All reporting sheets must be available to be reused if necessary during the integration section.
Individual contractual agreements with customer may require the original to hand over to the
customer for archiving.

Jun 14, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 399 Commissioning Test Records

This page intentionally left blank.

20 Alcatel-Lucent Internal Jun 14, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 401

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Integration Planning

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation Access ...................................................................................... 5
Applicable IEH 521 Sections ................................................................................ 5
Applicable Methods Documents............................................................................ 6
Prerequisites ..................................................................................................... 8
Prerequisites .................................................................................................. 8
Node B Integration Flow........................................................................................ 9
Node B Integration Flow Diagram Preparation for Integration ..................................... 9
Node B Integration Flow Diagram Optional Procedures for Integration ........................ 10
Node B Integration Flow Diagram ....................................................................... 11
Node B Integration Testing Flow Diagram ............................................................. 12
RF Path Tests Flow ............................................................................................ 13
RF Path Testing Flow Diagram ........................................................................... 13
Ethernet OAM in the Node B Testing Flow .............................................................. 14
Ethernet OAM in the Node B Testing Flow Diagram ................................................ 14
24 Cells and 12 Antenna Pairs - Flow ...................................................................... 15
Radio Configuration Check with 24 Cells and 12 Antenna Pairs - Flow Diagram ................ 15
Dual Node B WCDMA in one d4U Flow ..................................................................... 16
Dual Node B WCDMA in one d4U Flow Diagram ....................................................... 16
External Alarm Logic Status Integration and Inversion Flow ........................................... 17
External Alarm Logic Status Integration and Inversion Flow Diagram ............................ 17
971x LR Cabinet Alarm Checking Configuration Flow ................................................... 18
971x LR Cabinet Alarm Checking Configuration Flow Diagram ..................................... 18
Node B Daisy Chaining through the Node B Flow ........................................................ 19
Node B Daisy Chaining through the Node B Flow Diagram .......................................... 19
Node B Daisy Chain Remote Checking Flow ............................................................... 20
Node B Daisy Chain Remote Checking Flow Diagram ................................................ 20

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Integration Procedure Overview ............................................................................ 21

Reference of Integration Procedures ................................................................... 21
Integration Test Procedure Overview ...................................................................... 23
Reference of Integration Test Procedures ............................................................. 23
RF Path Test Procedure Overview .......................................................................... 24
Reference of RF Path Test Procedures ................................................................. 24
Ethernet OAM in the NodeB Testing Procedure Overview .............................................. 27
Reference of Ethernet OAM in the NodeB Test Procedure .......................................... 27
24 Cells and 12 Antenna Pairs Procedure Overview ..................................................... 28
Reference of radio configuration Procedures ......................................................... 28
Dual Node B WCDMA in one d4U Procedure Overview .................................................. 29
Reference of Dual Node B in d4U Configuration Procedures ....................................... 29
External Alarm Logic Status Integration and Inversion Procedure Overview ....................... 30
Reference of External Alarm Logic Status Integration and Inversion Procedure ................ 30
971x LR Cabinet Alarm Checking Configuration Procedure Overview ................................ 31
Reference of 971x LR Cabinet Alarm Checking Configuration Procedure ........................ 31
Node B Daisy Chaining through the Node B Activation Procedure Overview ........................ 32
Reference of Node B Daisy Chaining through the node B Procedures ............................ 32
Node B Daisy Chain Remote Checking Procedure Overview ........................................... 34
Reference of Node B Daisy Chaining through the node B Checking Procedures ............... 34
Node B Integration Test Records ........................................................................... 38
Purpose ...................................................................................................... 38
Node B Integration Test Records ........................................................................ 38

List of Figures

Figure 1: Preparation for Integration flow of activities ............................................................ 9

Figure 2: Optional Procedures after Integration flow of activities ............................................. 10
Figure 3: Integration - flow of activities ........................................................................... 11
Figure 4: Integration Testing flow of activities .................................................................. 12
Figure 5: RF Path Testing flow of activities ...................................................................... 13
Figure 6: Ethernet OAM in the Node B Testing flow of activities ............................................. 14
Figure 7: Radio Configuration Check with 24 Cells and 12 Antenna Pairs - flow of activities ............. 15
Figure 8: Dual Node Bs WCDMA in one d4U - flow of activities ................................................. 16
Figure 9: External Alarm Logic Status Integration and Inversion - flow of activities ........................ 17
Figure 10: 971x LR Cabinet Alarm Checking Configuration - flow of activities............................... 18
Figure 11: Node B Daisy Chaining through the Node B flow of activities .................................... 19
Figure 12: Node B Daisy Chain Remote Checking flow of activities .......................................... 20

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA integration ..................................................... 5

Table 2: Applicable ALU Documents for WCDMA integration ...................................................... 6
Table 3: List of Integration Procedures ............................................................................. 21
Table 4: List of Integration Test Procedures ....................................................................... 23

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Table 5: List of RF Path Test Procedures ........................................................................... 24

Table 6: List of Ethernet OAM in the NodeB Test Procedures ................................................... 27
Table 7: Operational Procedures to Check the Radio Configuration ........................................... 28
Table 8: Operational Procedures for Dual Node B in d4U Configuration ...................................... 29
Table 9: List of External Alarm Logic Status Integration and Inversion Procedures ......................... 30
Table 10: List of 971x LR Cabinet Alarm Checking Configuration Procedures ................................ 31
Table 11: List of procedures for Node B Daisy Chaining through the Node B ................................. 32
Table 12: List of Node B Daisy Chain Remote Checking Procedures............................................ 34

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

General

Section This section provides overview on

Description the flow of procedures
procedures to perform the integration of Node B into an existing WCDMA UTRAN
procedures to test the success of the integration of Node B into existing WCDMA UTRAN
procedures to perform the antenna functional tests
Checklists for planning and testing

Previous Release May 2013

Date

Release Notes Update: June 2014 :

Update of Table1: Applicable IEH 521 Sections for WCDMA integration
Addition of the new maps for:
RF Path Testing Procedures
NodeB Daisy Chain integration and Remote Checking Procedures.
24 Cells and 12 Antenna Pairs Procedures
Dual Node Bs WCDMA in one d4U Procedures
External Alarm Logic Status Integration and Inversion Procedures
971x LR Cabinet Alarm Checking Configuration Procedures

Update: May 15, 2013 Addition of the Integration tests planning of the VSWR, TX Power and
RSSI/RTWP measurements.

New creation: April 2013 under utilization of existing methods documents for UA08.1.

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B integration.

Documentation Links to applicable documents can be found under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN
/Documents/index.html

Use common Node B to find the latest applicable version.

Applicable IEH The sections listed in Table 1 below are required for WCDMA Node B integration.
521 Sections

Table 1: Applicable IEH 521 Sections for WCDMA integration

Section Description
402 Integration into existing UTRAN Procedures
410 Integration Testing Procedures
411 RF Path Testing Procedures
412 Ethernet OAM in the Node B Testing Procedures
413 NodeB Daisy Chain Remote Checking Procedures
431 24 Cells and 12 Antenna Pairs Procedures
432 Dual Node Bs WCDMA in one d4U Procedures
433 External Alarm Logic Status Integration and Inversion Procedures
434 971x LR Cabinet Alarm Checking Configuration Procedures
499 Node B Integration Test Records
706 NodeB Daisy Chaining through the Node B Activation Procedures

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

References, Continued

Applicable The following methods documents are required to perform the Node B integration
Methods
Documents
Table 2: Applicable ALU Documents for WCDMA integration

Doc Number Doc Title URL

9YZ-03450- Alcatel-Lucent Node B Integration in an http://cic.us.alcatel-
4402-EFZZA existing UTRAN (UA08.x) lucent.com/pdfdocs6/pris
tore212/512696.pdf
WCDMA IM 30- Alcatel-Lucent Node B DHCP activation http://cic.us.alcatel-
3003 (UA08.x) lucent.com/pdfdocs6/pris
tore212/512584.pdf
9YZ-04088- Alcatel-Lucent Node B DHCP activation http://cic.us.alcatel-
0099-RJZZA (LR13.1) lucent.com/pdfdocs14/pri
store215/536074.pdf
9YZ-05870- Alcatel-Lucent Node B DHCP activation http://cic.us.alcatel-
0099-RJZZA (LR13.3) lucent.com/pdfdocs14/pri
store215/536084.pdf
WCDMA IM 64- Alcatel-Lucent Node B IMA activation http://cic.us.alcatel-
3004 (UA08.x) lucent.com/pdfdocs6/pris
tore212/512574.pdf
9YZ-04088- Alcatel-Lucent Node B IMA activation http://cic.us.alcatel-
0100-RJZZA (LR13.1) lucent.com/pdfdocs14/pri
store215/536076.pdf
9YZ-05870- Alcatel-Lucent Node B IMA activation http://cic.us.alcatel-
0100-RJZZA (LR13.3) lucent.com/pdfdocs14/pri
store215/549349.pdf
NN-20500-032 Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
System - User Guide (UA08.x) lucent.com/pdfdocs14/pri
store215/530471.pdf
9YZ-04088- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.1) lucent.com/pdfdocs14/pri
store215/562268.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.3) lucent.com/pdfdocs14/pri
store215/586415.pdf
UMT/OMC/DD/ SIE External UTRAN Alarm dictionary https://wcdma-
013913 ll.app.alcatel-
lucent.com/livelink/livelin
k.exe?func=ll&objId=663
77977&objAction=brows
e&viewType=1

Continued on next page

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

References, Continued

Applicable
Methods
Doc Number Doc Title URL
Documents
(continued) NN-20500- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
018P1 UA08.1 System - Node B Alarms Reference Guide lucent.com/pdfdocs14/pri
(UA08.x) store215/524948.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0060-UFZZA System - Node B Alarms Reference Guide lucent.com/pdfdocs14/pri
(LR13.3) store215/536534.pdf

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Prerequisites

Prerequisites This section lists all points that must be satisfied prior to the integration of a Node B:

Node B digital unit and RRHs installation and commissioning are complete
All required tools for integration are available and operational
All antenna work is complete and jumpers are connected to the RRHs
All DSX wiring, cross-connects and backhaul configurations are provisioned and complete
End-to-End connectivity (i.e. E1) is available and validated
Associated core networks and UTRAN Elements are fully functional
All CS and PS routings are in place
UMTS SIMs have been provided, tested and provisioned for all required call scenarios

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Node B Integration Flow

Node B The flow diagram below outlines the preparation steps for the integration of a Node B.
Integration Flow
Diagram
Preparation for Figure 1: Preparation for Integration flow of activities
Integration

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Node B Integration Flow, Continued

Node B The flow diagram below outlines the optional Procedures to perform after the integration of a
Integration Node B.
Flow Diagram
Optional
Procedures for Figure 2: Optional Procedures after Integration flow of activities
Integration

Continued on next page

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Node B Integration Flow, Continued

Node B The flow diagram below outlines the steps which need to be performed to complete the
Integration Flow integration of a Node B.
Diagram Figure 3: Integration - flow of activities

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Node B Integration Flow, Continued

Node B The flow diagram below outlines the steps which need to be performed to complete the
Integration integration testing of a Node B.
Testing Flow Figure 4: Integration Testing flow of activities
Diagram

12 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

RF Path Tests Flow

RF Path Testing The flow diagram below outlines the steps which need to be performed to complete the RF
Flow Diagram Path testing of a Node B.

Figure 5: RF Path Testing flow of activities

June 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Ethernet OAM in the Node B Testing Flow

Ethernet OAM The flow diagram below outlines the steps to check the Ethernet OAM link status in the Node
in the Node B B
Testing Flow
Diagram
Figure 6: Ethernet OAM in the Node B Testing flow of activities

14 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

24 Cells and 12 Antenna Pairs - Flow

Radio The flow diagram below outlines the steps to check the radio configuration with 24 cells and
Configuration 12 Antenna Pairs
Check with 24
Cells and 12
Antenna Pairs - Figure 7: Radio Configuration Check with 24 Cells and 12 Antenna Pairs
Flow Diagram - flow of activities

June 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Dual Node B WCDMA in one d4U Flow

Dual Node B The flow diagram below outlines the steps for the Dual Node B WCDMA configuration in the
WCDMA in one same d4U.
d4U Flow
Diagram
Figure 8: Dual Node Bs WCDMA in one d4U - flow of activities

16 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

External Alarm Logic Status Integration and

Inversion Flow

External Alarm The flow diagram below outlines the steps for checking the External Alarm Logic Status
Logic Status Integration and Inversion Logic of External Alarm.
Integration and
Inversion Flow
Diagram Figure 9: External Alarm Logic Status Integration and Inversion - flow of
activities

June 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

971x LR Cabinet Alarm Checking Configuration Flow

971x LR The flow diagram below outlines the steps for checking of the 971x LR Cabinet Alarm
Cabinet Alarm Configuration.
Checking
Configuration
Flow Diagram Figure 10: 971x LR Cabinet Alarm Checking Configuration - flow of
activities

18 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Node B Daisy Chaining through the Node B Flow

Node B Daisy The flow diagram below outlines the steps which need to be performed to complete the Node
Chaining B Daisy Chaining through a Node B activation.
through the
Node B Flow
Diagram Figure 11: Node B Daisy Chaining through the Node B flow of
activities

June 30, 2014 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Node B Daisy Chain Remote Checking Flow

Node B Daisy The flow diagram below outlines the steps which need to be performed to complete the Node B
Chain Remote Daisy Chain Remote Checking.
Checking Flow
Diagram
Figure 12: Node B Daisy Chain Remote Checking flow of activities

20 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Integration Procedure Overview

Reference of Table 3 below lists all operational steps for a new Node B integration.
Integration NOTE: The integration flow diagram explains at what position in the integration process a
Procedures procedure is being used
NOTE: The integration procedures are detailed in Table1: Applicable IEH 521 Sections for
WCDMA integration.

Table 3: List of Integration Procedures

Operation Optional/ Procedure Remarks

Mandatory
Setup PC for OAM client O Proc. 1 Setting up PC (first time only)
Connect to WMS and M Proc. 2 How to start the NSP GUI
start session
Check RNC alarm and M Proc. 3 Check RNC layout before
layout conditions Node B integration
Export Network M Proc. 4 Details how to proceed with
Configuration Data WPS and main server to
import a view of the current
network into WPS.
Work order creation for a M Proc. 5 Creation of Node B work order
new Node B with WPS by data design team
*** Not in scope of this
procedure***
Work order import M Proc. 6 Importing of the work order to
WMS
Pre-checks before M Proc. 7 Pre-checks before activation of
activation Node B
Node B - creation M Proc. 8 Release the new Node B on
RNC and WMS
Move of new Node B into M Proc. 9 Details how make the new
layout Node B appear in the existing
layout
Update Node B NeID M Proc 10 Details how to verify and
change the Node B NE ID.
Node B OAM link state M Proc. 11 Node B into OAM layout, BTS
change and activation NEID update, Node OAM state
change and activation

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Integration Procedure Overview, Continued

Reference of
Integration
Operation Optional/ Procedure Remarks
Procedures
Mandatory
(continued)
Creation of layout in O Proc. 12 Details how to create the
WMS layout window in the WMS.

NOTE: Only on specific

demand of customer
Edit layout in WMS O Proc. 13 Details how to edit the layout
window in the WMS.

NOTE: Only on specific

demand of customer
View layout in WMS O Proc. 14 Details how to view the layout
window in the WMS.

NOTE: Supporting procedure:

used in multiple places
PSU alarm integration in O Proc. 15 9326/9926 d2U in small
small cabinet cabinet: integration of PSU
alarms and external alarms

NOTE: This procedure is

configuration dependent
PSU alarm integration in O Proc. 16 9326/9926 d2U in medium
medium cabinet cabinet: integration of PSU
and external alarms .

NOTE: This procedure is

configuration dependent

22 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Integration Test Procedure Overview

Reference of The table below lists all operational steps for testing of a new Node B after integration.
Integration Test NOTE: The integration flow diagram explains at what position which procedure is being used
Procedures

NOTE: The integration test procedures are detailed in Table1: Applicable IEH 521 Sections for
WCDMA integration.

Table 4: List of Integration Test Procedures

Operation Opt/ Procedures Remarks

Mand.
Node B online tests M Proc. 1 Node B sanity tests online
Circuit Switched call test M Proc. 2 Call through testing Circuit
Switched
For all sectors and carriers of a
Node B
Video Call Test M Proc. 3 Video Call through 2 cellphones.
For all sectors and carriers of a
Node B
Packet Switched Call Test M Proc. 4 Packet Switched Call ping to
GGSN and
FTP to test throughput.
For all sectors and carrier sof a
Node B
External alarms test O Proc. 5 How to verify external alarms with
small or medium cabinet
External PSU alarms test O Proc. 6 How to verify external PSU
alarms with medium cabinet

June 30, 2014 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

RF Path Test Procedure Overview

Reference of RF The table below lists all operational steps to perform RF path test after Node B integration
Path Test
Procedures
NOTE: The RF Path Test flow diagram explains at what position which procedure is being used
NOTE: The RF Path Test is part of the integration test procedures detailed in Table1:
Applicable IEH 521 Sections for WCDMA integration.

Table 5: List of RF Path Test Procedures

Operation Opt/ Procedures Remarks

Mand.
Setup PC for OAM O Proc. 1 Setting up PC (first time only)
client from Integration (From Integration Procedure)
Procedures
Connect to WMS M Proc. 2 How to start the NSP GUI
and start session from Integration (From Integration Procedure)
Procedures
Unlock the FDDCells M RF Path Test with How to check the FDDCell
WMS status and unlock the FDDCell
- if necessary with WMS.
Preparation
Check the M RF Path Test with Retrieve the pcpichPower
pcpichPower of the WMS value of FDDCell as reference
FDDCell - value with WMS.
Preparation
Select the M RF Path Test with Select the suitable
Measurement WMS measurement according to the
solution - tool used
Preparation
BTS Radio Power M RF Path Test with Display the WMS GUI for BTS
tab Selection WMS Radio Power measurement
-
BTS Radio Power Tab
RTWP/RSSI M RF Path Test with Retrieve the RTWP/RSSI
measurement WMS measurement of all types of
- RE with WMS.
BTS Radio Power Tab
TX Power M RF Path Test with Retrieve the TX Power
measurement WMS measurement of all types of
- RE with WMS.
BTS Radio Power Tab

Continued on next page

24 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

RF Path Test Procedure Overview, Continued

Reference of RF
Path Test
Operation Opt/ Procedures Remarks
Procedures
Mand.
(continued)
Log-in to the WMS O RF Path Health Check Start the WMS server IP
Server with Telnet - connection with Telnet
Telnet Preparation
-
(Optional)
Log-in to the Node B O RF Path Health Check Start the Node B IP
with Telnet - connection with Telnet
Telnet Preparation
-
(Optional)
Display Data List of O RF Path Health Check Show with Telnet command
all Radio Elements - the list of data of all RE
connected to the CPRI links.
Telnet Preparation
-
(Optional)
Display Data List of O RF Path Health Check Show with Telnet command
One Radio Elements - the list of data of one specific
RE connected to the CPRI
Telnet Preparation link..
-
(Optional)
Log-in to the Radio O RF Path Health Check Start the RE IP connection
Element with Telnet - using the RE login and
password with Telnet
Telnet Preparation commands
-
(Optional)
Login to ASB RRH O RE Path Tests for ASB Start the RE IP connection
Product Products with Telnet for ASB product
(2x60w or 60w-21C)
-
(Optional)
VSWR O RE Path Tests for ASB Retrieve the VSWR
Measurement Products measurements with Telnet
(2x60w or 60w-21C) (ASB)
-
(Optional)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

RF Path Test Procedure Overview, Continued

Reference of RF
Path Test
Operation Opt/ Procedures Remarks
Procedures
Mand.
(continued)
TX Power O RE Path Tests for ASB Retrieve the TX Power
Measurement Products measurements from RE (ASB)
(2x60w or 60w-21C)
-
(Optional)
RSSI Measurement O RE Path Tests for ASB Retrieve the RSSI
Products measurements from RE (ASB)
(2x60w or 60w-21C)
-
(Optional)
Login to GPCS RE O RE Path Tests for Start the RE IP connection
GPCS Products with Telnet for GPCS product
(60w-21)
-
(Optional)
VSWR O RE Path Tests for Retrieve the VSWR
Measurement GPCS Products measurements with Telnet
(60w-21) (GPCS)
-
(Optional)
PA Gain O RE Path Tests for Retrieve the PA Gain
Measurement GPCS Products measurements from RE
(60w-21) (GPCS)
-
(Optional)
TX Power O RE Path Tests for Retrieve the TX Power
Measurement GPCS Products measurements from RE
(60w-21) (GPCS)
-
(Optional)
RSSI Measurement O RE Path Tests for Retrieve the RSSI
GPCS Products measurements from RE
(60w-21) (GPCS)
-
(Optional)
Logout the Radio M Exit from the Telnet
Element Local application.
Terminal

26 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Ethernet OAM in the NodeB Testing Procedure

Overview

Reference of The table below lists all operational steps for testing of Ethernet OAM in the NodeB after
Ethernet OAM integration
in the NodeB NOTE: The integration flow diagram explains at what position which procedure is being used
Test Procedure

NOTE: The integration test procedures are detailed in Table1: Applicable IEH 521 Sections for
WCDMA integration.

Table 6: List of Ethernet OAM in the NodeB Test Procedures

Operation Opt/ Procedures Remarks

Mand.
Setup PC for remote Node M Proc. 1 Initial only
B Connection
Node B Integration in an M Proc. 2 Node B Integration completed
Existing UTRAN successfully
Open TIL GUI from NSP O Proc. 3 If WMS GUI is already used and
- GUI available.
Perform Remote TIL GUI O Proc. 4 If WMS GUI is not usable.
Connection on the Node B
Ethernet OAM Link M Proc. 5 To check visually the Ethernet
Location on the CCM OAM Link Location and Status
Board Procedure on the CCM Board.
Ethernet OAM Link on M Proc. 6 To check visually the Ethernet
GE MDA Procedure OAM Link on the GE MDA
Ethernet Alarm on GE M Proc. 7 To check visually the Ethernet
MDA Check Procedure Alarm on the GE MDA.
Ethernet OAM Link on M Proc. 8 To check visually the Ethernet
CCM Mother Board OAM Link on the CCM Mother
Procedure Board.
Perform other Optional O Proc. 9 If other optional procedures need
Procedures to be performed
Node B Integration Test M Proc. 10 To record all results of the
Records Procedure Integration tests

June 30, 2014 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

24 Cells and 12 Antenna Pairs Procedure Overview

Reference of The table lists all operational procedures to check the radio configuration with 24 cells and 12
radio Antenna Pairs.
configuration NOTE: The 24 Cells and 12 Antenna Pairs flow diagram explains at what position which
Procedures procedure is being used
NOTE: The 24 Cells and 12 Antenna Pairs is part of the integration test procedures detailed
inTable1: Applicable IEH 521 Sections for WCDMA integration.

Table 7: Operational Procedures to Check the Radio Configuration

Operation Opt/ Proc. Remark
Mand.
24 Cells and 12 antenna Pairs M Proc. 1 Selection of the
Preparation Procedure configuration used
Configuration Type 1 O Proc. 2 If configuration
Visual Check Procedure Type 1 is used
Configuration Type 2 O Proc. 3 If configuration
Visual Check Procedure Type 2 is used
Configuration Type 3 O Proc. 4 If configuration
Visual Check Procedure Type 3 is used
Configuration Type 4 O Proc. 5 If configuration
Visual Check Procedure Type 4 is used
Configuration Type: O Proc. 6 If configuration
Dual Band with TRDU/RRH Type Dual Band with
Visual Check Procedure TRDU/RRH is used

Configuration Type: O Proc. 7 If configuration

Dual Band with RRH2x Type Dual Band with
Visual Check Procedure RRH2x is used

28 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Dual Node B WCDMA in one d4U Procedure

Overview

Reference of The table below lists all operational procedures for Dual Node B WCDMA configuration in the
Dual Node B in same d4U.
d4U NOTE: The Dual Node B WCDMA configuration in the same d4U flow diagram explains at
Configuration what position which procedure is being used
Procedures
NOTE: The Dual Node B WCDMA configuration in the same d4U is part of the integration test
procedures detailed in Table1: Applicable IEH 521 Sections for WCDMA integration.

Table 8: Operational Procedures for Dual Node B in d4U Configuration

Step Operation Opt/ Proc. Remark
Mand.
1 Hosting 2 Node Bs WCDMA M Prepara-
in one d4U Preparation tion
2 Dual Node B in one d4U: M Proc. 1
BTS Parameter Setting
Procedure
3 Dual Node B in one d4U: M Proc. 2
2NodeBs Parameter Setting
Procedure
4 Dual Node B - Configuration O Proc. 3 If Configuration 1
1 Procedure required
5 Dual Node B - Configuration O Proc. 4 If Configuration 2
2 Procedure required
6 Dual Node B - Configuration O Proc. 5 If Configuration 3
3 Procedure required
7 Final Field Operation M Proc. 6
Procedure
8 Dual NodeB #1 Configuration M Proc. 7
Final Check Procedure
9 Dual NodeB #2 Configuration M Proc. 8
Final Check Procedure

June 30, 2014 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

External Alarm Logic Status Integration and

Inversion Procedure Overview

Reference of The table below lists all operational steps for checking of External Alarm Logic Status
External Alarm Integration and External Alarm Logic Inversion after integration
Logic Status NOTE: The integration flow diagram explains at what position which procedure is being used
Integration and
Inversion
Procedure NOTE: The integration test procedures are detailed in Table1: Applicable IEH 521 Sections for
WCDMA integration.

Table 9: List of External Alarm Logic Status Integration and Inversion

Procedures
Operation Opt/ Procedures Remarks
Mand.
Setup PC for remote Node M Proc. 1 Initial only
B Connection
Node B Integration in an M Proc. 2 Node B Integration completed
Existing UTRAN successfully
Open NSP GUI M Proc. 3 WMS GUI must be available.
External Alarm Logic M Proc. 4 To configure the External Alarm
Status Integration Logic Status during the
Procedures integration.
Open TIL GUI from NSP O Proc. 5 If WMS GUI is already used and
- GUI available.
Perform remote TIL GUI O Proc. 6 If WMS GUI is not usable.
Connection on the Node B
External Alarm Mask M Proc. 7 To check visually the Alarm Mask
Display Procedure for of the Cabinet.
Cabinet
External Alarm Mask M Proc. 8 To check visually the Alarm Mask
Display Procedure for of the RRH.
RRH
External Alarm Logic M Proc. 9 To set the Inversion of the
Inversion Configuration External Alarm Logic for a
Procedure for Cabinet cabinet.
External Alarm Logic M Proc. 10 To set the Inversion of the
Inversion Configuration External Alarm Logic for a RRH.
Procedure for RRH
Perform other Optional O Proc. 11 If other optional procedures need
Procedures to be performed
Node B Integration Test M Proc. 12 To record all results of the
Records Procedure Integration tests

30 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

971x LR Cabinet Alarm Checking Configuration

Procedure Overview

Reference of The table below lists all operational steps for checking of 971x LR Cabinet Alarm after
971x LR integration
Cabinet Alarm NOTE: The integration flow diagram explains at what position which procedure is being used
Checking
Configuration
Procedure NOTE: The integration test procedures are detailed in Table1: Applicable IEH 521 Sections for
WCDMA integration.

Table 10: List of 971x LR Cabinet Alarm Checking Configuration

Procedures
Operation Opt/ Procedures Remarks
Mand.
Setup PC for remote Node M Proc. 1 Initial only
B Connection
Node B Integration in M Proc. 2 Completed successfully
Existing UTRAN
Perform remote TIL GUI O Proc. 3 If WMS GUI is not available
Connection on the Node B
Open TIL GUI from NSP O Proc. 4 If WMS GUI is already used and
- GUI available
971x LR Cabinet Alarm M Proc. 5 Check the Alarms configuration
Checking Procedure according to the LR cabinet used.
Perform other Optional O Proc. 6 If other optional procedures need
Procedures to be performed
Node B Integration Test M Proc. 7 To record all results of the
Records Procedure Integration tests

June 30, 2014 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Node B Daisy Chaining through the Node B

Activation Procedure Overview

Reference of The table below lists all operational steps to activate and test the Node B Daisy Chaining at
Node B Daisy site after Node B integration.
Chaining NOTE: The Node B Daisy Chaining through the Node B flow diagram explains at what
through the position which procedure is being used
node B
NOTE: The Node B Daisy Chaining through the Node B is part of the integration test
Procedures
procedures detailed in Table1: Applicable IEH 521 Sections for WCDMA integration.

Table 11: List of procedures for Node B Daisy Chaining through the
Node B
Operation Opt/ Procedures Remarks
Mand.
Configuration of the M Proc 1 : Node B (A) Laptop setting and TIL
Backhaul link on the Daisy Chaining connections are already done
Ethernet Port/0 of Commissioning -TIL and available
Node B (A) Node B already integrated
Configuration of the M Proc. 2 :Node B (B) Laptop setting and TIL
Backhaul link on the Daisy Chained connections are already done
Ethernet Port/0 of Commissioning -TIL and available
Node B (B) Node B already integrated
Pre-Check the M Proc. 3 : Node B (A) The NSP GUI is operational
Ethernet Port Daisy Chaining Pre- The Proc 1 and the Proc 2
parameters of Node Check before Activation successfully performed
B (A) before Daisy -WMS
chain activation
Set the Ethernet M Proc. 4 : Node B (A) The NSP GUI is operational
Port/0 of Node B Daisy Chaining The Proc 3 successfully
(A) with Port Role in Ethernet Port/0 performed
Backhaul (MBH) Configuration
Procedure -WMS Parameters in Class 2 or
Class3
Set the Ethernet M Proc. 5 : Node B (A) The NSP GUI is operational
Port/1 of Node B Daisy Chaining The Proc 3 and Proc 4
(A) with Port Role in Ethernet Port/1 successfully performed
Daisy Chaining Configuration
(DC) Procedure -WMS Parameters in Class 2 or
Class3

Continued on next page

32 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Node B Daisy Chaining through the Node B

Activation Procedure Overview, Continued

Reference of
Node B Daisy
Operation Opt/ Procedures Remarks
Chaining
Mand.
through the
node B Set the IP Ran M Proc. 6 : Node B (A) The NSP GUI is operational
Procedures Parameter of Node Daisy Chaining IP Ran The Proc 4 and Proc 5
(continued) B (A) to TRUE Configuration successfully performed
Procedure -WMS
Parameters in Class3
Validation of Node B M Proc. 7 : Node B (A) The NSP GUI is operational
(A) Daisy chaining Daisy Chaining The Proc 4 and Proc 5
configuration Validation successfully performed
Parameters in Class3
Validation of Node B M Proc. 8 : Node B (B) The NSP GUI is operational
(B) Daisy chained Daisy Chained The Proc 4 and Proc 5
configuration Validation successfully performed
Parameters in Class3

June 30, 2014 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Node B Daisy Chain Remote Checking Procedure

Overview

Reference of The table below lists all operational steps to test the Node B after the Node B Daisy Chain
Node B Daisy through the Node B activation is done.
Chaining NOTE: The Node B Daisy Chaining through the Node B flow diagram explains at what position
through the which procedure is being used
node B
NOTE: The Node B Daisy Chaining through the Node B is part of the integration test
Checking
procedures detailed in Table1: Applicable IEH 521 Sections for WCDMA integration.
Procedures

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Table 12: List of Node B Daisy Chain Remote Checking Procedures

Operation Opt/ Procedures Remarks

Mand.
Log onto the WMS M Proc. 1 : Node B in Laptop available
SSH server to allow Daisy Chain Telnet with a terminal
usage of Telnet Log onto WMS emulator connected
commands. Server Procedure to WMS
WMS IP address
and login and
password are
available
Perform an IP Ping M Proc. 2 : IP Ping of Node B Daisy Chain
test with Telnet of all All Node B in Daisy Activated
Daisy Chained and Chain - Testing The Proc 1
daisy chaining Node Procedure successfully
B. performed
Laptop available
with a terminal
emulator connected
to WMS

Continued on next page

34 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Node B Daisy Chain Remote Checking Procedure

Overview, Continued

Reference of
Node B Daisy
Operation Opt/ Procedures Remarks
Chaining
Mand.
through the
node B Log onto the Node M Proc 3 : Node B Laptop available
Checking B to allow usage of Daisy Chaining with a terminal
Procedures Telnet commands. Telnet Log onto emulator connected
(continued) Node B to node B
Node B IP address
and login and
password are
available
Check the Node B O Proc. 4 : Node B (A) Node B Daisy Chain
(A) in Daisy Daisy Chaining Activated
Chaining Configuration The Proc 3
configuration Checking Procedure successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (A)
Check the VLAN Id O Proc. 5 : Node B (A) Node B Daisy Chain
of Node B (A) VLAN Id Checking Activated
Procedure The Proc 3
successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (A)
Check the Ethernet O Proc. 6 : Node B (A) Node B Daisy Chain
Port of Node B (A) Ethernet Port Activated
Checking Procedure The Proc 3
successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (A)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Node B Daisy Chain Remote Checking Procedure

Overview, Continued

Reference of
Node B Daisy
Operation Opt/ Procedures Remarks
Chaining
Mand.
through the
node B Check the Ethernet O Proc. 7 : Node B (A) Node B Daisy Chain
Checking Port Counters of Ethernet Port Activated
Procedures Node B (A) Counters Checking The Proc 3
(continued) Procedure successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (A)
Check the Node B O Proc. 8 : Node B (B) Node B Daisy Chain
(B) in Daisy Daisy Chained Activated
Chained Configuration The Proc 3
configuration Checking Procedure successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (B)
Check the VLAN Id O Proc. 9 : Node B (B) Node B Daisy Chain
of Node B (B) VLAN Id Checking Activated
Procedure The Proc 3
successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (B)

Continued on next page

36 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Integration Planning IEH 521, Section 401

Node B Daisy Chain Remote Checking Procedure

Overview, Continued

Reference of
Node B Daisy
Operation Opt/ Procedures Remarks
Chaining
Mand.
through the
node B Check the Ethernet O Proc. 10 : Node B Node B Daisy Chain
Checking Port of Node B (B) (B) Ethernet Port Activated
Procedures Checking Procedure The Proc 3
(continued) successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (B)
Check the Ethernet O Proc. 11 : Node B Node B Daisy Chain
Port Counters of (B) Ethernet Port Activated
Node B (B) Counters Checking The Proc 3
Procedure successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (B)

June 30, 2014 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 401 Integration Planning

Node B Integration Test Records

Purpose The Node B integration test records are checklists which are available to support and
document the flow of operations before, during and post integration for
On site activities
Remote (WMS / NSP) operations
and document successful completion of integration by customer acceptance.

Node B Node B integration test records are detailed in Table1: Applicable IEH 521 Sections for
Integration Test WCDMA integration.
Records

38 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 402

April 30, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Integration into existing UTRAN

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation access ...................................................................................... 5
Applicable IEH 521 sections ................................................................................ 5
Applicable Methods & Documents ......................................................................... 5
Proc. 1 Setup PC for OAM client ............................................................................ 6
Description .................................................................................................... 6
Condition ...................................................................................................... 6
Required data ................................................................................................. 6
Setup procedure .............................................................................................. 6
Proc. 2: Connect to WMS and start session ................................................................. 7
Description .................................................................................................... 7
Preconditions ................................................................................................. 7
NSP GUI start Procedure .................................................................................... 7
Proc. 3: Check RNC alarm and layout conditions .......................................................... 8
Description .................................................................................................... 8
Preconditions ................................................................................................. 8
Needed inputs ................................................................................................ 8
Check alarms procedure .................................................................................... 8
Alarm trouble shooting ...................................................................................... 9
External UTRAN alarms dictionary ........................................................................ 9
Proc. 4: Export Network Configuration Data ............................................................. 10
Description .................................................................................................. 10
Preconditions ............................................................................................... 10
Work order data ............................................................................................ 10
Export network configuration data procedure ........................................................ 10
Snapshot to data designer ................................................................................ 12
Proc. 5: Work order creation for a new Node B .......................................................... 13

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Description .................................................................................................. 13
Submission of snapshot.................................................................................... 13
Work order generation .................................................................................... 13
Reception of work order .................................................................................. 13
Delivery method of work order .......................................................................... 13
Proc. 6: Work order import .................................................................................. 14
Description .................................................................................................. 14
Prerequisites ................................................................................................ 14
Work order import procedure ............................................................................ 14
Proc. 7: Pre-checks before activation ..................................................................... 15
Description .................................................................................................. 15
Prerequisites ................................................................................................ 15
Pre-check procedure ...................................................................................... 16
Proc. 8: Node B creation ................................................................................... 21
Description .................................................................................................. 21
Preconditions ............................................................................................... 21
First Node B activation in RNC ........................................................................... 21
Node B creation procedure ............................................................................... 21
Supporting detailed instructions ........................................................................ 25
Proc. 9: Move of new Node B into layout ................................................................. 26
Purpose ...................................................................................................... 26
Description .................................................................................................. 26
Preconditions ............................................................................................... 26
Move Node B to layout procedure ....................................................................... 26
Supporting Information ................................................................................... 28
Proc. 10: Update Node B NeID .............................................................................. 29
Description .................................................................................................. 29
Preconditions ............................................................................................... 29
Retrieval of real Node B NE ID ........................................................................... 29
Retrieve Node B NeID procedure ........................................................................ 29
Update Node B NeID procedure ......................................................................... 29
Proc. 11: Node B OAM link state change and activation................................................ 31
Description .................................................................................................. 31
Preconditions ............................................................................................... 31
Node B OAM link state change and activation procedure ........................................... 31
Proc. 12: Creation of layout in WMS (optional) .......................................................... 34
Description .................................................................................................. 34
Purpose ...................................................................................................... 34
Precondition ................................................................................................ 34
New layout creation procedure.......................................................................... 34
Supporting information ................................................................................... 34
Proc: 13: Edit of layout in WMS (optional) ................................................................ 35
Description .................................................................................................. 35
Purpose ...................................................................................................... 35
Preconditions ............................................................................................... 35
Edit layout procedure ..................................................................................... 35
Supporting information ................................................................................... 35
Proc. 14: View layout in WMS (optional) .................................................................. 36
Description .................................................................................................. 36
Supporting Procedure for integration .................................................................. 36
Entry Criteria ............................................................................................... 36

2 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

View layout procedure .................................................................................... 36

Supporting information ................................................................................... 36
Proc. 15: PSU alarm integration in small cabinet (optional) .......................................... 37
Description .................................................................................................. 37
When to use this procedure .............................................................................. 37
DC/DC power supply configuration ..................................................................... 37
Preconditions ............................................................................................... 37
On site work: Rearrangement of external alarms .................................................... 37
PSU Alarm mapping ........................................................................................ 38
External alarms integration procedure ................................................................. 38
DC surge protection box alarm integration procedure small cabinet (optional)................ 41
Integration sequence ...................................................................................... 41
Supporting information ................................................................................... 41
Proc. 16: PSU alarm integration in medium cabinet (optional) ....................................... 42
Description .................................................................................................. 42
When to use this procedure .............................................................................. 42
DC/DC power supply configuration ..................................................................... 42
Preconditions ............................................................................................... 42
On site work: Rearrangement of external alarms .................................................... 42
PSU Alarm mapping ........................................................................................ 43
External alarms integration procedure ................................................................. 43
DC surge protection box alarm integration procedure medium cabinet (optional) ............ 46
Integration sequence ...................................................................................... 46
Supporting information ................................................................................... 46

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA integration ..................................................... 5

Table 2: Applicable methods & documents ........................................................................... 5
Table 3: Alarm Mapping of PSU alarms in small cabinet ......................................................... 38
Table 4: Alarm Mapping of PSU alarms in medium cabinet ...................................................... 43

April 30, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

General

Section This section provides detailed information about the individual procedures for integration of a
Description WCDMA Node B:
Preconditions
Inputs
Actions to be performed
Outputs
Additional details for clarifications

Supporting documents which can provide further details beyond this IEH are referenced.

Previous Release New creation

Date

Release Notes New creation: Apr 2013 under utilization of existing IM documents for UA08.1.

4 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B integration.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN
/Documents/index.html

Use Common Node B to find the latest applicable version.

Applicable IEH The sections listed in Table 1 below are required for WCDMA Node B integration.
521 sections

Table 1: Applicable IEH 521 Sections for WCDMA integration

Section Description
401 Integration Planning
410 Integration Testing
499 Node B Integration Test Records

Applicable The following methods documents are required to perform the Node B integration
Methods &
Documents
Table 2: Applicable methods & documents

Doc Number Doc Title URL

9YZ-03450-4402- Integration in an existing https://all1.na.alcatel-
EFZZA UTRAN lucent.com/Teams/GCDNetworks/W
irelessGPEC/DeliveryReadiness/W
CDMA/UTRAN/Documents/index.ht
ml

Use Common Node B to find the

latest applicable version.
NN-20500-032 Alcatel-Lucent 9353 Wireless https://infoproducts.alcatel-
Management System - User lucent.com/aces/cgi-
Guide (WMS user guide) bin/dbaccessfilename.cgi/NN20500
032UA08.1_V1_
UMT/OMC/DD/01 External UTRAN Alarms https://infoproducts.alcatel-
3913 Dictionary lucent.com/aces/cgi-
(UTRAN Alarm Dictionary) bin/dbaccessfilename.cgi/UMTOMC
DD013913UA08.1_V1_

April 30, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 1 Setup PC for OAM client

Description This procedure configures the PC as OAM client to allow for connection to the NSP server
(OAM).

Condition This procedure has to be executed only during the initial setup for a specific integration
(customer).
If done already no action is required.

Required data The following data are required for the setup:
NSP server name or
NSP server IP address

Setup procedure Execute table steps to setup PC for NSP environment:

Step Action
1 Locate host file on the PC and open with text editor
2 Check for presence of NSP server name and IP address in hosts file
3

If ... Then ...

NSP server name and IP address is Continue with step 5
present
NSP server name and IP address is Enter hostname and IP address into
NOT present hosts file
Example:
139.54.78.xxx wmst5xxx
wmst5xxx.alcatel-lucent.com

4 Save new host file

NOTE: Detailed information about the procedure is available in the methods document:

9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: To setup Hostname (optional)

For access to the document refer to section References of this IEH521 chapter.

6 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 2: Connect to WMS and start session

Description This procedure launches the NSP GUI.

Preconditions The following preconditions for this procedure step must be met:
PC must be setup as OAM client
Have NSP server name or IP address of NSP server present
Have User ID and Password for NSP GUI available
Java (version dependent on WMS version). Initial connection to WMS will enable for
download of correct Java version.

NSP GUI start Execute following steps to start NSP GUI session:
Procedure

Step Action
1 Start Web browser with
http://NSPserver's name:8080/NSP/
or
http://IPadress:8080/NSP/

This command opens the WMS entry page.

2 Update Java to correct version

If ... Then ...

JRE software already installed Continue with step 4
JRE software not installed Download the Windows 32-bit JRE
installer

3 Complete JRE installation and launch

4 Click on LAUNCH GUI to open NSP session
5 Execute login
NOTE: Use your User ID and Password.
6 Accept warning window

NOTE: Detailed information about the procedure is available in the methods document:

9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: Navigator Starting up configuration in UA08.1

For access to the document refer to section References of this IEH521 chapter.

April 30, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 3: Check RNC alarm and layout conditions

Description Open layout of concerned RNC on NSP

Check for unexpected equipment alarms to prepare for further integration steps

Preconditions NSP session is launched successfully

Needed inputs NE name of RNC to which the new Node B shall be integrated

Check alarms Execute following steps to verify RNC alarms and layout conditions:
procedure

Step Action
1 Click on File and open Select Network Layout to open the Layout Selector.
2 Select the desired layout (use Layout Name) and click View button to open
den concerned layout in Navigator.
3 Double click on concerned layout to open the Resource Browser for the
concerned RNC.
4 Click with right button of mouse on concerned RNC within the Resource
Browser to open submenu.
5 Select Show alarms and right click to open Alarm Manager window.
6 Check for un-allowed RNC alarms in the Alarm Manager window for the
concerned RNC:

NOTE: Un-allowed RNC alarms: Iub alarms

7

If ... Then ...

No un-allowed RNC alarms available Move on to step 8

NOTE: external alarms are allowed

If un-allowed RNC alarms are Troubleshoot un-allowed alarms to
available remove alarm condition

8 End of procedure

Continued on next page

8 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 3: Check RNC alarm and layout conditions,

Continued

NOTE: Detailed information about the procedure is available in the methods document:

9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure:

To open the concerned Layout in View mode
To display RNC alarms

For access to the document refer to section References of this IEH521 chapter.

Alarm trouble All un-allowed alarms of the node under work need to be cleared prior to continuation.
shooting

NOTE: External alarms do not require clearance and can be accepted.

NOTE: Use Alarm Dictionary for alarm analysis and clearance.

External UTRAN Use the document External UTRAN Alarms Dictionary to troubleshoot alarms (see references).
alarms
dictionary

April 30, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 4: Export Network Configuration Data

Description This procedure describes how to export a snapshot of the network configuration data into WPS
work space.

Preconditions NSP session is launched successfully

WPS on local computer and operational
RNC name for Node B integration

Work order data

IMPORTANT: The design team (data filler) always requires the snapshot of the
network data (latest version) for creation of the Node B integration work order.

Export network Execute procedure as per table below to export the network snapshot from WMS for further
configuration processing by datafill team.
data procedure

Step Action
1 Open Resource Browser GUI on NSP.
2 Select target RNC for Node B integration and select
Configuration | CM XML | Export NE Grouping

Continued on next page

10 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 4: Export Network Configuration Data, Continued

Export network
configuration
Step Action
data procedure
(continued) 3 Press Export Now on Export NE Grouping tag.

4 Check on Command Manager when export is finished.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 4: Export Network Configuration Data, Continued

Export network
configuration
Step Action
data procedure
(continued) 5 Use Filezilla (or similar) to connect to NSP server for FTP.
Download snapshot from the server to the computer.

NOTE: Location on server: /opt/nortel/data/cmXML

Example:

6 Send snapshot to data fill team for further processing to generate work order
for Node B integration.

Snapshot to data The exported network data snapshot (.xml) is:

designer
required by the Network Data Designer (data filler)
used as basis for the new work order to add the Node B into the existing Network
sent to the Network Data Designer (data filler)

NOTE: Network Data Designer (data filler) contact information is required to hand-off the
snapshot (email address). Contact TPM for contact information and planning.

12 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 5: Work order creation for a new Node B

Description This process step details the actions to allow for creation of new work order(s) for Node B
integration.

Submission of The exported network data snapshot (.xml file) must be sent to the network data design team
snapshot (data filler) for further processing.

Work order Network Data Design team generates the new Node B / Node B parenting work order based
generation on:
provided network data snapshot (.xml)
customer data (CIQ based)
configuration data

Reception of Network Data Design team provides new Node B / Node B parenting work order to integrator
work order for further use during the integration.

Delivery method Email from data filler

of work order

April 30, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 6: Work order import

Description This procedure imports the pre-defined work order to the Main Server directory on the WMS

Prerequisites The Node B integration work order is available in .xwo format from data filler for transfer to the
WMS Main server.
File transfer software (e.g. Filezilla) is available for file transfer of .xwo - work order to WMS.

Work order Use file transfer software to load work order into WMS main server directory
import
procedure
Step Action
1 Load work order (.xwo) into PC in preparation of file transfer
2 Execute file import of work order into WMS main server by use of file transfer
software (e.g. filezilla) to main server directory:
/opt/nortel/data/cmXML
3 Verify that the work order has been successfully transferred into the WMS main
server under /opt/nortel/data/cmXML

14 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 7: Pre-checks before activation

Description This procedure performs pre-checks prior to activation of the work order
RNC alarms
MIB audit

Prerequisites The work order (.xwo) is available on the WMS main server under the main server directory:
/opt/nortel/data/cmXML

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 7: Pre-checks before activation, Continued

Pre-check Execute pre-check procedure as per table below to ensure that the conditions are set for later
procedure Node B creation and activation:

Step Action
1 Click on File and open Select Network Layout to open the Layout Selector.
2 Select the desired layout (use Layout Name) and click View button to open
den concerned layout in Navigator.
3 Double click on concerned layout to open the Resource Browser for the
concerned RNC.
4 Click with right button of mouse on concerned RNC within the Resource
Browser to open submenu.
5 Select Show alarms and right click to open Alarm Manager window.
6 Check for unwanted RNC alarms in the Alarm Manager window for the
concerned RNC.

NOTE: Unwanted RNC alarms: Iub alarms of the concerned Node B

7

If ... Then ...

No unwanted RNC alarms available Move on to step 8

NOTE: External alarms are allowed

If unwanted RNC alarms are Troubleshoot unwanted
available alarms to remove alarm
condition

Continued on next page

16 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 7: Pre-checks before activation, Continued

Pre-check
procedure
Step Action
(continued)
8 Open Audit Action Window from context menu (right-click on NE)
9 Select Configuration | Select MIB | Select Audit to open Action Audit
Window

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 7: Pre-checks before activation, Continued

Pre-check
procedure
Step Action
(continued)
10 Click on Audit Now to start audit process.

NOTE: The Command Manager window appears and display audited NEs and
the audit progress.

Continued on next page

18 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 7: Pre-checks before activation, Continued

Pre-check
procedure
Step Action
(continued)
11 Check audit results for unwanted status by use of Details tab:

NOTE: The audit process can take several minutes to complete

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 7: Pre-checks before activation, Continued

Pre-check
procedure
Step Action
(continued)
12 Check audit results details by use of Audit Report Window.

NOTE: The audit results must be:

Successful
Must return no differences found

CAUTION: In case of unsuccessful audit the support organization has to be

contacted for scheduling a rebuild of the live RNC to avoid service impacts to
live network.

NOTE: Detailed information about the procedure is available in the methods document:

9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedures:

To open the concerned Layout in View mode

To display RNC alarms
Pre-checks before activation

For access to the document refer to section References of this IEH521 chapter.

20 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 8: Node B creation

Description This procedure describes the individual steps to create a new Node B on an available RNC.

Preconditions The work order is successfully loaded to WMS main server

RNC pre-checks and audit are successfully finalized.
NSP session is launched successfully

First Node B
activation in
RNC
IMPORTANT: In case of first Node B integration into an RNC, a build of the RNC
has to be re-launched once the Node B integration is finished to enable Iub CP and CCP.

Node B creation Create the Node B by execution the steps of table below:
procedure

Step Action
1 Open NSP session manager by clicking on
Configuration |Sessions Manager from NSP menu bar.
2 Activate Create New Session

NOTE: Create Session window is opened

3 Enter a value for Session Name to start the NSP session.

NOTE: It is recommended to use the work order name.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 8: Node B creation, Continued

Node B creation
procedure
Step Action
(continued)
4 Expand cmXML tree and select previously loaded new work order for Node B
integration.

5 Click Add to list button to move work order into right window.
6 Open the Excluded Nodes window by clicking Next button.

NOTE: Excluded Nodes window display a list of impacted Nodes. Do NOT

exclude any node in the Excluded Nodes window.
7 Activate Node B work order by clicking Launch button.

NOTE: A new window with two worksheets is opened:

Creation
Summary & Action

Continued on next page

22 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 8: Node B creation, Continued

Node B creation
procedure
Step Action
(continued)
8 Monitor creation status and monitor until completed
9 Select Summary & Action work sheet and validate session result

NOTE: The status result reflects the status of the work order. The status must
match the expected status results.

Node Expected Status

BTSEquipment/xxx Validated
RNC/yyy Validated
RNC/xxx RNCEquipment/0 Loaded
INode/xxx
Site/yyyq Released

10 Expand Actions for <Session> and select RNC/xxx RNCEquipment/0

INode/xxx node and activate Validation button to execute the Validation task.
11 Verify that validation task is successfully completed:

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 8: Node B creation, Continued

Node B creation
procedure
Step Action
(continued)
12 Press preactivation button to perform Preactivation task on
BTSEquipment/xxx and make sure that it is successfully completed.

13 Press activation button to perform activation task on

RNC/yyy
RNC/xxx RNCEquipment/ 0 INode/xxx
BTSEquipment/xxx

Continued on next page

24 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 8: Node B creation, Continued

Node B creation
procedure
Step Action
(continued)
14 Monitor progress and ensure successful completion

NOTE: All impacted nodes must have:

Status = Successful
Progress = 100%
15 Terminate session when activation was successful.

Supporting NOTE: Detailed information about the procedure is available in the methods document:
detailed
instructions
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: To create NodeB session using NSP

For access to the document refer to section References of this IEH521 chapter.

April 30, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 9: Move of new Node B into layout

Purpose The new Node B must be made visible in the RNC layout before additional integration work can
be executed. This procedure describes how to make the new Node B available in the RNC
layout.

Description This operation is used to move a NE (new Node B under integration) into an already existing
layout.

Preconditions NSP session is operational

The RNC layout must already exist.
Name of NE to be moved (edited) into the RNC layout must be known

Move Node B to Move the new Node B into existing layout on NSP by executing following steps as per table
layout below:
procedure

Step Action
1 In NSP open window, select File from the menu bar and select Select Network
Layout from drop-down menu.

NOTE: New window Layout Selector opens.

2 Select from Layout Selector window desired layout and click on Edit button to
open the Navigator window.
3 Double click on selected layout to open in edit mode.

NOTE: It will load the layout into the resource browser.

Continued on next page

26 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 9: Move of new Node B into layout, Continued

Move Node B to
layout
Step Action
procedure
(continued) 4 Open NE Store to search for target Node B

5 Find Node B for move in NE Store

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 9: Move of new Node B into layout, Continued

Move Node B to
layout
Step Action
procedure
(continued) 6 Press Move To button and select the target layout for move.

NOTE: This operation moves the target Node B from NE Store to the target
layout.

Supporting NOTE: Detailed information about the procedure is available in the methods document:
Information
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: To open the Layout in Edit Mode

For access to the document refer to section References of this IEH521 chapter.

28 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 10: Update Node B NeID

Description This procedure is to change the NodeB NeID (ex serial number) in WMS to match the real
NodeB NeID as configured during the Node B commissioning and consists of two steps:
Retrieve NodeB NeID
Update NodeB NeID

Preconditions NSP GUI is operational

Retrieval of real Retrieve required NE ID number from site through TIL (on-site activity)
Node B NE ID
NOTE: NodeB NeID number is set during the Node B commissioning to the target value.

NOTE: NodeB NeID target value is available from the TPM.

Retrieve Node B Retrieve NodeB NeID by execution of the steps as per table below:
NeID procedure

NOTE: Steps 1 to 4 are on-site activities and not required if Node B NeID is available from
TPM.

Step Action
1 Connect TIL to CCM(-U) port 1
2 Login by using:
Login: nodeB
Password: nodeblnx
3 Retrieve the Node B serial number which is displayed at the bottom of the TIL
GUI:
Read:
.Serial Number: example
4 Store Serial Number for further use.

NOTE: Node B NeID is typically provided by on-site personnel through phone

or email.

Update Node B Execute the following procedure to update (change) the new Node B NE ID:
NeID procedure

Step Action
1 Select new Node B icon in NSP Resource Browser
2 Use right click to open menu bars and select Configuration

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 10: Update Node B NeID, Continued

Update Node B
NeID procedure
Step Action
(continued)
3 A new under menu opens select Object Editor

4 Select line with attribute neid in open Object Editor window

5 Enter correct (previously retrieved from site) NeID number

6 Apply new value by clicking Set and Apply all changes

NOTE: Detailed information about the procedure is available in the methods document:

9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: To retrieve and change the BTS NeID (Optional)
For access to the document refer to section References of this IEH521 chapter.

30 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 11: Node B OAM link state change and

activation

Description Update of WMS GUI layout with new Node B

Change of administrative state of the Node B OAM link
Activation of physical new Node B

Preconditions The Node B must run with the required software version
Node B must be in created and activated state
Node B must be physically connected
Node B IP address

Node B OAM link Execute the following steps to change the OAM link state and activate the Node B
state change
and activation
procedure Step Action
1 Test connectivity with Node B on OAM link by sending ping command to Node
B IP address.
2 Select new Node B in Resource Browser.
3 Right click Configuration then select Set NEs`OAM Link Administrative
State

4 Click Unlock when State Action Window is open.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 11: Node B OAM link state change and

activation, Continued

Node B OAM
link state
Step Action
change and
activation 5 Check that the NE status changes from Lock to Unlock
procedure
(continued) NOTE: The color of the new Node B in the layout changes from blue to red or
grey. (Red means Node B with alarms)

NOTE: The unlock operation of the OAM link to the new Node B starts
automatically a build operation for the new Node B.
6 Monitor the build operation of the system in Command Manager and check for
successful completion.

NOTE: The Node B build operation is automatically started after unlock

operation

NOTE: If the build process will not be successful, then

Check for alarms and clear them
Execute the build process again

Continued on next page

32 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 11: Node B OAM link state change and

activation, Continued

Node B OAM
link state
Step Action
change and
activation 7
procedure
(continued)
With successful build report after unlocked OAM
administrative state the Node B is successfully activated and ready for
testing.

NOTE: Detailed information about the procedure is available in the methods document:

9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: Changing the OAM link administrative state of NEs

For access to the document refer to section References of this IEH521 chapter.

NOTE: Please check for optional integration procedures to be executed (configuration

dependent)

April 30, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 12: Creation of layout in WMS (optional)

Description This procedure allows creation of a new layout on the WMS.

This procedure has to be executed if required (e.g. by customer).

Purpose A new layout may be used to place new / migrated NEs in a specific layout for a period of
observation.

Precondition The creation of a new layout in WMS is determined by customer needs and created based
upon customer request.
The following information is required: Layout name
NSP session is established

New layout Execute steps as per table to create a new layout:

creation
procedure
Step Action
1 In NSP open window, select File from the menu bar and select Select Network
Layout to open Layout Selector.
2 Click on Layout Management and then New to open new Window to enter
new layout name.
3 Enter name for new layout NEW Layout and press OK button

NOTE: The new layout name appears in the Layout Selector window.

Supporting NOTE: Detailed information about the procedure is available in the methods document:
information
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: To create a new layout

For access to the document refer to section References of this IEH521 chapter.

34 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc: 13: Edit of layout in WMS (optional)

Description This operation is used to move a NE (new Node B under integration) into an already existing
layout.

Purpose New NEs under integration may be assembled under a specific layout for extended period for
observation.

Preconditions The layout must already exist.

Name of NE to be edited into layout must be known

Edit layout Execute steps as per attached table to edit an existing layout
procedure

Step Action
1 In NSP open window, select File from the menu bar and select Select Network
Layout to open Layout Selector.
2 Select from Layout Selector window desired layout and click on Edit button to
open the Navigator window.
3 Double click on selected layout to open in edit mode.

NOTE: It will load the selected layout into the resource browser.

Supporting NOTE: Detailed information about the procedure is available in the methods document:
information
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: To open the Layout in Edit Mode

For access to the document refer to section References of this IEH521 chapter.

April 30, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 14: View layout in WMS (optional)

Description This operation details how to open the layout in view mode.

Supporting Opening of Layout is used for many different reasons during the operation of a network.
Procedure for In the context of this IEH521 the layout on WMS open in view mode is required to perform
integration necessary actions during the integration procedure.

Entry Criteria NSP GUI operational

View layout The following table describes the stepwise procedure

procedure

Step Action
1 Select File from menu bar and click on Select Network Layout to open
Layout Selector window.
2 Select desired Layout and click on View to open Navigator window
3 Load layout applications by double clicking on desired Layout

NOTE: The desired layout is now open for further operations.

Supporting NOTE: Detailed information about the procedure is available in the methods document:
information
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: To open the Layout in View Mode

For access to the document refer to section References of this IEH521 chapter.

36 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 15: PSU alarm integration in small cabinet

(optional)

Description Integration and setting of cabinet alarms and PSU alarms for a very specific configuration (in
small cabinet)

When to use this Outdoor cabinet from Eltek: Small S6

procedure
Includes:
9326 d2U V2
9926 d2U V3

DC/DC power
supply
configuration
DO NOT use this procedure to integrate alarms of an external DC/DC power
supply.
Information about this specific configuration with external DC/DC power supply and how to
integrate the alarms can get retrieved from:
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN
Look for procedure: To set DC/DC convert alarm integration (Optional)
For access to the document refer to section References of this IEH521 chapter.

Preconditions The Node B is already fully integrated

On site work:
Rearrangement
of external
alarms IMPORTANT: In case of usage of more than 8 external alarm pairs by customer
some re-arrangements need to be made. This re-arrangement is required to be completed prior
to the setting and integration of the PSU alarms and are part of physical installation.
Detailed information is available in the methods document:
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN
Look for procedure: 9326 d2U V2 in a Small or Medium Alarms Integration

For access to the document refer to section References of this IEH521 chapter.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 15: PSU alarm integration in small cabinet

(optional), Continued

PSU Alarm The following table describes the PSU alarm mapping in case of the following cabinets: Small
mapping S6

Table 3: Alarm Mapping of PSU alarms in small cabinet

External Small S6
Alarm
Port
9 Small S6 PSU Alarm = AC Mains
Alarm
10 Small S6 PSU Alarm = MAJOR
Alarm PSU
11 Small S6 PSU Alarm = Minor
Alarm PSU
12 Small S6 PSU Alarm = Door
Alarm
13 Small S6 PSU Alarm = Surge
Protection Box Failure (RRH1 to
RRH3)
14 N/A

External alarms Following table contains all actions to configure and integrate the external alarms for the small
integration cabinet configuration
procedure

Step Action
1 Open layout in WMS with Node B for integration of power supply alarms
2 Right click on concerned Node B and select Equipment Monitor to open
Equipment Monitor.
3 Open External Alarm Mapping Table and select ExternalAlarms/0

Continued on next page

38 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 15: PSU alarm integration in small cabinet

(optional), Continued

External alarms
integration
Step Action
procedure
(continued) 4 Select ExternalAlarm/9 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

5 Set the field alarm message to Small S6 PSU Alarm = AC Mains Alarm
Click Set and then Apply All Changes.

6 Select ExternalAlarm/10 by right click and select

Configuration | Object Editor

NOTE: Object Editor window opens

7 Set the field alarm message to Small S6 PSU Alarm = Major Alarm PSU
Click Set and then Apply All Changes.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 15: PSU alarm integration in small cabinet

(optional), Continued

External alarms
integration
Step Action
procedure
(continued) 8 Select ExternalAlarm/11 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

9 Set the field alarm message to Small S6 PSU Alarm = Minor Alarm PSU
Click Set and then Apply All Changes.
10 Select ExternalAlarm/12 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

11 Set the field alarm message to Small S6 PSU Alarm = Door Alarm
Click Set and then Apply All Changes.
12 Return to layout in WMS and open Object Editor by right click on concerned
Node B: Select Configuration then Object Editor
13 Open attribute: supervisedExternalAlarm and set mask to
xxxxxxx 11110000 xxxxxxxx xxxxxxxx

DO NOT: Do not change values of bytes 1, 3, 4

Continued on next page

40 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 15: PSU alarm integration in small cabinet

(optional), Continued

External alarms
integration
Step Action
procedure
(continued) 14 Click Set and Apply All Changes to store and open the Command Manager
window.
15 Perform Set Online operation and validate that it is performed successfully.

NOTE: Test external alarms as per section 410.

DC surge Integrate the DC surge protection box alarm in small cabinet as described in the action table
protection box
alarm
integration NOTE: DC surge protection box is optional. Integration of alarm is only required if present.
procedure small
cabinet
(optional) Step Action
1 Select ExternalAlarm/13 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

2 Set the field alarm message to Small S6 PSU Alarm = DC Surge Protection
Box Failure (RRH1 to RRH3)
3 Click Set and then Apply All Changes

Integration This procedure will be executed AFTER the mandatory steps of a new Node B integration are
sequence successfully done.

Supporting NOTE: Detailed information about the procedure is available in the methods document:
information
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: 9326 d2U V2 in a Small or Medium Alarms Integration

For access to the document refer to section References of this IEH521 chapter.

April 30, 2013 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 16: PSU alarm integration in medium cabinet

(optional)

Description Integration and setting of cabinet alarms and PSU alarms for a very specific configuration (in
medium cabinet)

When to use this Outdoor cabinet from Eltek:

procedure Medium Md6
Medium Md4

Includes:
9326 d2U V2
9926 d2U V3
9926 d4U V3 (in Md4 cabinet only)

DC/DC power
supply
configuration
DO NOT use this procedure to integrate alarms of an external DC/DC power
supply.
Information about this specific configuration with external DC/DC power supply and how to
integrate the alarms can get retrieved from:
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN
Look for procedure: To set DC/DC convert alarm integration (Optional)
For access to the document refer to section References of this IEH521 chapter.

Preconditions The Node B is already fully integrated

On site work:
Rearrangement
of external
alarms IMPORTANT: In case of usage of more than 8 external alarm pairs by customer
some re-arrangements need to be made. This re-arrangement is required to be completed prior
to the setting and integration of the PSU alarms and are part of physical installation.
Detailed information is available in the methods document:
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN
Look for procedure: 9326 d2U V2 in a Small or Medium Alarms Integration

For access to the document refer to section References of this IEH521 chapter.

Continued on next page

42 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 16: PSU alarm integration in medium cabinet

(optional), Continued

PSU Alarm The following table describes the PSU alarm mapping in case of the following cabinets:
mapping
Medium Md6
Medium Md4
Table 4: Alarm Mapping of PSU alarms in medium cabinet

External Medium Md4/Md6

Alarm
Port
9 Medium PSU Alarm = AC Mains
Alarm
10 Medium PSU Alarm = MAJOR Alarm
PSU
11 Medium PSU Alarm = Minor Alarm
PSU
12 Medium PSU Alarm = Door Alarm
13 Medium PSU Alarm = Surge
Protection Box Failure (RRH1 to
RRH3)
14 Medium PSU Alarm = Surge
Protection Box Failure (RRH4 to
RRH6)

External alarms Following table contains all actions to configure and integrate the external alarms for the
integration medium cabinet configuration
procedure

Step Action
1 Open layout in WMS with Node B for integration of power supply alarms
2 Right click on concerned Node B and select Equipment Monitor to open
Equipment Monitor.
3 Open External Alarm Mapping Table and select ExternalAlarms/0

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 16: PSU alarm integration in medium cabinet

(optional), Continued

External alarms
integration
Step Action
procedure
(continued) 4 Select ExternalAlarm/9 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

5 Set the field alarm message to Medium PSU Alarm = AC Mains Alarm PSU
Click Set and then Apply All Changes.
6 Select ExternalAlarm/10 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

7 Set the field alarm message to Medium PSU Alarm = MAJOR Alarm PSU
Click Set and then Apply All Changes.
8 Select ExternalAlarm/11 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

9 Set the field alarm message to Medium PSU Alarm = Minor Alarm PSU
Click Set and then Apply All Changes.
10 Select ExternalAlarm/12 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

Continued on next page

44 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
Integration into existing UTRAN IEH 521, Section 402

Proc. 16: PSU alarm integration in medium cabinet

(optional), Continued

External alarms
integration
Step Action
procedure
(continued) 11 Set the field alarm message to Medium PSU Alarm = Door Alarm
Click Set and then Apply All Changes.
12 Verify whether surge protection box is used and execute DC surge protection
box alarm in medium cabinet procedure

If ... Then ...

DC surge protection box is used Execute DC surge protection box
alarm integration procedure medium
cabinet (optional)
13 Return to layout in WMS and open Object Editor by right click on concerned
Node B:
Select Configuration then Object Editor
14 Open attribute: supervised ExternalAlarm and set mask to
xxxxxxx 11110000 xxxxxxxx xxxxxxxx

DO NOT: Do not change values of bytes 1, 3, 4

15 Click Set and Apply All Changes to store and open the Command Manager
window.
16 Perform Set Online operation and validate that it is performed successfully.

Continued on next page

April 30, 2013 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 402 Integration into existing UTRAN

Proc. 16: PSU alarm integration in medium cabinet

(optional), Continued

DC surge Integrate the DC surge protection box alarm in medium cabinet as described in the action table
protection box
alarm
integration NOTE: DC surge protection box is optional. Integration of alarm is only required if present.
procedure
medium cabinet
(optional) Step Action
1 Select ExternalAlarm/13 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

2 Set the field alarm message to Medium PSU Alarm = DC Surge Protection
Box Failure (RRH1 to RRH3)
3 Click Set and then Apply All Changes.
4 Select ExternalAlarm/14 by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

5 Set the field alarm message to Medium PSU Alarm = DC Surge Protection
Box Failure (RRH1 to RRH3)
6 Click Set and then Apply All Changes.

Integration This procedure will be executed AFTER the mandatory steps of a new Node B integration are
sequence successfully done.

Supporting NOTE: Detailed information about the procedure is available in the methods document:
information
9YZ-03450-4402-EFZZA - Integration in an existing UTRAN

Look for procedure: 9326 d2U V2 in a Small or Medium Alarms Integration

For access to the document refer to section References of this IEH521 chapter.

46 Alcatel-Lucent Internal April 30, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 523, Section 410

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Node B Integration Testing

Table of Contents

General ............................................................................................................ 4
Description .................................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation Access ...................................................................................... 5
Applicable IEH521 sections ................................................................................. 5
Applicable Methods Documents............................................................................ 5
Integration Test Tools .......................................................................................... 6
Description .................................................................................................... 6
Equipment needs on-site.................................................................................. 6
Equipment needs remote / NSP ......................................................................... 6
Integration Test Process ....................................................................................... 7
Description .................................................................................................... 7
Integration Test Process .................................................................................... 7
Proc. 1: Node B online tests ................................................................................... 8
Description .................................................................................................... 8
Preconditions ................................................................................................. 8
Inputs ........................................................................................................... 8
Node B online tests procedure ............................................................................. 9
If FDD cell alarms occur ................................................................................... 10
External UTRAN Alarms Dictionary ...................................................................... 10
Communication Tests ......................................................................................... 11
Content of communication tests ........................................................................ 11
Description .................................................................................................. 11
Customer specific deviations ............................................................................ 11
Selection of sector and frequency for call tests ...................................................... 11
Change of selection of sector and frequency for call tests ......................................... 11
Selection of sector ......................................................................................... 12
Generic flow of call tests operation .................................................................... 13
Information to control lock/un-lock of FDD cell...................................................... 14

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 2: Change Locking/Un-locking status of FDD cells ............................................... 15

Description .................................................................................................. 15
Pre-conditions .............................................................................................. 15
Use Case ..................................................................................................... 15
Procedure Locking of FDD cells ......................................................................... 15
Procedure Un-locking of FDD cells .................................................................... 17
Proc. 3: Circuit switched call test .......................................................................... 19
Description .................................................................................................. 19
Preconditions ............................................................................................... 19
Communication with integrator ......................................................................... 19
Call testing position ....................................................................................... 19
CS call - test definition ................................................................................... 19
Success criteria ............................................................................................. 19
CS call test procedure ..................................................................................... 20
Proc. 4: Video Call Test ...................................................................................... 22
Description .................................................................................................. 22
Preconditions ............................................................................................... 22
Communication with integrator ......................................................................... 22
Call testing position ....................................................................................... 22
Video Call Test definition ................................................................................ 22
Video Call Procedure ...................................................................................... 23
Proc. 5: Packet Switched Call Test ......................................................................... 25
Description .................................................................................................. 25
Preconditions ............................................................................................... 25
Communication with integrator ......................................................................... 25
Call testing position ....................................................................................... 25
PS call test definition.................................................................................... 25
Success criteria ............................................................................................. 25
PS call test procedure ..................................................................................... 26
Proc. 6: External alarms test small/medium cabinet (Optional) ................................... 28
Description .................................................................................................. 28
Tested Configuration ...................................................................................... 28
Precondition ................................................................................................ 28
Test Sample ................................................................................................. 28
External PSU alarms test procedure Door Alarm ................................................... 28
Proc. 7: External PSU alarms test medium cabinet (Optional) ...................................... 31
Description .................................................................................................. 31
Tested Configuration ...................................................................................... 31
Preconditions ............................................................................................... 31
Test Sample ................................................................................................. 31
External PSU alarms test procedure AC mains alarm .............................................. 31

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA integration ..................................................... 5

Table 2: Applicable ALU Product Documents for WCDMA integration ........................................... 5
List of Figures

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Figure 1: Integration Test Process and Flow .......................................................................... 7

Figure 2: Generic flow of call test operations ..................................................................... 13

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

General

Description This section provides information how to validate that the Node B integration was successfully
done.

Previous Release June 15, 2013

Date

Release Notes June 30, 2014: Removal of RF path tests and transfer to new section 411.
June 15, 2013: Addition of RF path tests:
Remote through WMS
Remote through Telnet for trouble shooting

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B integration testing.

Documentation Access to applicable documents can be made under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Use common Node B to find the latest applicable version.

Applicable The sections listed in Table 1 below are required for WCDMA Node B integration testing.
IEH521 sections

Table 1: Applicable IEH 521 Sections for WCDMA integration

Section Description
001 Introduction
401 Integration Planning
402 Integration into existing UTRAN
499 Node B Integration Test Records

Applicable The following methods documents are required to perform the Node B integration testing
Methods
Documents
Table 2: Applicable ALU Product Documents for WCDMA integration
Doc Number Doc Title URL
9YZ-03450-4402- Integration in an existing https://all1.na.alcatel-
EFZZA UTRAN lucent.com/Teams/GCDNetworks/Wir
elessGPEC/DeliveryReadiness/WCD
MA/UTRAN/Documents/index.html

Use common Node B to find the

latest applicable version.
UMT/OMC/DD/01 SIE External UTRAN Alarms https://infoproducts.alcatel-
3913 Dictionary lucent.com/aces/cgi-
(UTRAN Alarm Dictionary) bin/dbaccessfilename.cgi/UMTOMCD
D013913UA08.1_V1_

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Integration Test Tools

Description To test successful integration of a Node B, a small set of equipment and tools is required for
on-site testing activities.

Equipment The following equipments are required for integration testing by on-site engineer:
needs on-site
WCDMA cell-phone operating in the frequency band of Node B under integration
Capabilities:
Voice
Video
Data (FTP)
Network registered SIM card

Equipment The following equipments are required for integration testing remote / NSP GUI site:
needs remote /
Phone access (to allow information exchange with on-site engineer)
NSP
IT equipment capable for NSP GUI operations

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Integration Test Process

Description The integration test process provides an overview and guidance about
which tests to perform
in which sequence that tests need to be performed

Integration Test The following flow outlines the validation tasks to be performed during integration test:
Process

Figure 1: Integration Test Process and Flow

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 1: Node B online tests

Description This procedure is used to check that there is no problem/unexpected alarm on the FDD cells of
the Node B.

Preconditions Node B must be integrated (IEH 521-402)

All cells must be unlocked / enabled
NSP session established

Inputs Node B - NeID

RNC number of Node B under check

Continued on next page

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 1: Node B online tests, Continued

Node B online Execute following steps to perform Node B online tests:

tests procedure

Step Action
1 Open layout view on WMS (NSP)
2 Set cursor on the RNC NE and click on the right mouse button to open pull-
down menu

.
3 Select Show Alarms to open Alarm manager Window

4 Check that no FDD cells of the integrated Node B are in the alarm manager
window and display an unexpected Node B alarm.

NOTE: Use Node B NeID to identify Node B alarms of Node B under

integration.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 1: Node B online tests, Continued

If FDD cell Analyze alarms by using the document External UTRAN Alarms Dictionary
alarms occur
Perform trouble shooting to clear unexpected FDD cell alarms before moving to next step of
Integration testing

External UTRAN The correct version of the External UTRAN Alarms Dictionary shall be used. See
Alarms References for access.
Dictionary

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Communication Tests

Content of The communication tests do consist of:

communication CS call test (voice)
tests
Video Test (streaming video)
PS call test (FTP).

Description The full set of communication tests has to be performed on:

Every carrier (frequency) of the integrated Node B
Every sector of the integrated Node B.

Customer Customer specific requirements for testing may result in modifications of the call testing.
specific Customer specific requests should not change the generic flow of call tests operation and shall
deviations be reflected in performing / not performing individual call tests (e.g. only on subset of FDD cells
per Node B or reducing/increasing the number of call tests)

Customer specific requirements must be documented in the call testing sheet.

Selection of Lock all FDD cells of the integrated Node B which are NOT subject to call test of the required
sector and sector and frequency.
frequency for
call tests

IMPORTANT:
Typically only ONE FDD cell (which is the cell dedicated for call testing) is unlocked. This will
force the mobile phone to use the desired cell for the call tests.

Change of A new FDD cell is made available for call testing by change the locking status of FDD cells.
selection of
sector and
frequency for
call tests
Continued on next page

June 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Communication Tests, Continued

Selection of Locking of all FDD cells of sectors must be in synchronization with the position of the site
sector engineer.

Example: Sector 0 and Sector 2 locked.

NOTE: Call testing can be performed in Sector 1.

Continued on next page

12 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Communication Tests, Continued

Generic flow of The following flow of operation provides information about the steps and sequence to call test a
call tests integrated Node B, consisting of several sectors and frequencies (FDD cells)
operation

Figure 2: Generic flow of call test operations

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Communication Tests, Continued

Information to The on-site engineer (performing the call testing) provides information about the need to
control lock/un- change the locking status.
lock of FDD cell The information is typically submitted by phone.

14 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 2: Change Locking/Un-locking status of FDD

cells

Description This procedure allows to lock / unlock FDD cells of a dedicated Node B.

Pre-conditions NSP GUI operational

Node B under call test must be known
Information from on site engineer

Use Case Procedure 2 (Change Locking / Un-locking status of FDD cells) need to be used to establish
the correct test environment for communication tests as part of integration testing.
Each procedure has to be executed for each FDD cell.

Procedure Execute the following procedure to lock FDD cells for call testing:
Locking of FDD
cells
Step Action
1 Right click in Layout on concerned RNC (Node B under test is connected there)
to open sub-menu
2 Click on Equipment Monitor to open Equipment Monitor window
3 Select FDD cell of Node B under integration test targeted to lock.
Then press Configuration|Set Administrative State.

RESULT: The Set Administrative State Action Window opens for selected
FDD cell.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 2: Change Locking/Un-locking status of FDD

cells, Continued

Procedure
Locking of FDD
Step Action
cells
(continued) 4 Click on Lock button to start execution of lock command.

5 Monitor successful execution of Lock command in Command Manager

window by selecting logs

RESULT: Selected FDD cell is locked (and therefore no call can be made
through this cell)
6 Repeat steps 1 to 5 for every FDD cell to be locked.

Continued on next page

16 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 2: Change Locking/Un-locking status of FDD

cells, Continued

Procedure Un- Execute the following procedure to un-lock FDD cells:

locking of FDD
cells
Step Action
1 Right click in Layout on concerned RNC (Node B under test is connected there)
to open sub-menu
2 Click on Equipment Monitor to open Equipment Monitor window

3 Select FDD cell of Node B under integration test targeted to lock.

The press Configuration|Set Administrative State.

RESULT: The Set Administrative State Action Window opens for selected
FDD cell.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 2: Change Locking/Un-locking status of FDD

cells, Continued

Procedure Un-
locking of FDD
Step Action
cells
(continued) 4 Click on Unlock button to start execution of lock command.

5 Monitor successful execution of Unlock command in Command Manager

window by selecting logs

RESULT: Selected FDD cell is unlocked

6 Repeat steps 1 to 5 for every FDD cell to be un-locked.

18 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 3: Circuit switched call test

Description Perform circuit switched communication tests (audio) to proof successful integration of the new
Node B

Preconditions Fully integrated Node B into existing UTRAN (unlocked enabled)

No impacting Alarms on Node B or RNC
Specific Cell phone with network registered SIM
Telephone number for test (PSTN)
FDD cells not under test must be locked.
Call tester (on-site engineer) must be in correct position within sector under test

Communication
with integrator

IMPORTANT: For all communication tests, collaboration of on-site personnel and

integration tester is required. Use telephone connection to exchange necessary information.

Call testing
position

IMPORTANT: On site engineers position during communication testing must be:

in the area, covered by the FDD cell under test (sector)
at least 100m away from the antenna position

CS call - test Circuit Switched Call on FDD cell of a Node B.

definition
Recommended call duration: ~ 2 mins

Success criteria Connection to predefined subscriber is established. Understandable audio conversation (uplink
and downlink).

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 3: Circuit switched call test, Continued

CS call test The following sequence of procedural steps needs to be performed for a CS call test on a
procedure single FDD cell:

Step Action
1 Verify with integrator that all FDD cells not under call test are locked and FDD
cell under test is unlocked.
2 Verify that the ON SITE engineer is well positioned for the CS call test of the
dedicated sector (FDD cell) under test.

3 Perform audio (CS) call to pre-defined subscriber to test audio connection both
ways is working through unlocked FDD cell by on-site engineer.

NOTE: Call is successful if connection is made and audio is understandable at

both ends.
4 Document result of CS call test in Call test sheet.

Continued on next page

20 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 3: Circuit switched call test, Continued

CS call test
procedure
Step Action
(continued)
5 Continue with further call tests or change cell locking status:

If ... Then ...

CS call test is the last call test of the Inform integrator to change locking
FDD cell under test status of Node B
Further call tests need to be Execute next communication test
performed on this FDD cell

IMPORTANT: After finalization of all communication tests all FDD cells of the
Node B under communication testing have to be unlocked.

June 30, 2014 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 4: Video Call Test

Description A video call is performed to proof video capabilities of the integrated FDD cell work (UL/DL)

Preconditions Fully integrated Node B into existing UTRAN (unlocked enabled)

No impacting Alarms on Node B or RNC
Specific Cell phone (video call capable) with network registered SIM
Telephone number for test (Video call capable)
FDD cells not under test must be locked.
Call tester (on-site engineer) must be in correct position within sector under test

Communication
with integrator

IMPORTANT: For all communication tests, collaboration of on-site personnel and

integration tester is required. Use telephone connection to exchange necessary information.

Call testing
position

IMPORTANT: On site engineers position during communication testing must be:

in the area, covered by the FDD cell under test (sector)
at least 100m away from the antenna position

Video Call Test Video Call on FDD cell under test of a Node B.
definition Recommended call duration: ~ 1 min

NOTE: If no video capable partner for testing is available using streaming video test (e.g.
www.youtube.com) would alternatively be possible as backup solution for test.

Continued on next page

22 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 4: Video Call Test, Continued

Video Call The following sequence of procedural steps need to be performed for a video call test on a
Procedure single FDD cell:

Step Action
1 Verify with integrator that all FDD cells not under call test are locked and FDD
cell under test is unlocked.
2 Verify that the ON SITE engineer is well positioned for the CS call test of the
dedicated sector (FDD cell) under test

nd
4 Perform video call (Site engineer 1 to a 2 Site engineer or from site
engineer to a video capable device) and check video quality is at acceptable
level on both sides.

NOTE: The test is successful if streaming video is available on the display.

4 Document result of Video call test in Call test sheet.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 4: Video Call Test, Continued

Video Call
Procedure
Step Action
(continued)
5 Continue with further call tests or change cell locking status:

If ... Then ...

Video call test is the last call test of Inform integrator to change locking
the FDD cell under test status of Node B
Further call tests need to be Execute next communication test
performed on this FDD cell

IMPORTANT: After finalization of all communication tests all FDD

cells of the Node B under communication testing have to be unlocked.

24 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 5: Packet Switched Call Test

Description Validate PS network connectivity end-to-end including Node B, RNC and GGSN by
performing
Web browser test (open web page) for PS connectivity
FTP test to verify the throughput

Preconditions Fully integrated Node B into existing UTRAN (unlocked enabled)

No impacting Alarms on Node B or RNC
Specific Cell phone (PS call capable) with network registered SIM - with Laptop connected
FTP server address and target file for download
Test website (http://www.alcatel-lucent.com/)
FDD cells not under test must be locked.
Call tester (on-site engineer) must be in correct position within sector under test
Target throughput values for DL and UL are available for checking (from network design
team)

Communication
with integrator

IMPORTANT: For all communication tests, collaboration of on-site personnel and

integration tester is required. Use telephone connection to exchange necessary information.

Call testing
position

IMPORTANT: On site engineers position during communication testing must be:

in the area, covered by the FDD cell under test (sector)
at least 100m away from the antenna position

PS call test Packet Switched call to available website on FDD cell of a Node B
definition
File transfer to and from FTP server

Success criteria The following success criteria have to be met for this test

PS call test Success criteria

Web browser test Website is building up an visible
FTP test UL: check throughput is >= network design
defined value
DL: check throughput is >= network design
defined value

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 5: Packet Switched Call Test, Continued

PS call test The following actions have to be performed to proof packet switched call functionality:
procedure

Step Action
1 Verify with integrator that all FDD cells not under call test are locked and FDD
cell under test is unlocked.
2 Verify that the ON SITE engineer is well positioned for the CS call test of the
dedicated sector (FDD cell) under test

3 Perform PS call test by opening a test website (e.g. http://www.alcatel-

lucent.com/) and check that the website builds up correctly.
4 Perform FTP transfer (UL) to pre-defined FTP server and check UL throughput
is within acceptable ranges.

NOTE: Available file transfer tools which allow validation of throughput must be
used (e.g. filezilla).

IMPORTANT:
For validation of PS interfaces: One FTP per RNC is sufficient.

Continued on next page

26 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 5: Packet Switched Call Test, Continued

PS call test
procedure
Step Action
(continued)
5 Perform FTP transfer (DL) of previously uploaded file from pre-defined FTP
server and check DL throughput is within acceptable ranges.

NOTE: Available file transfer tools which allow validation of throughput must be
used (e.g. filezilla).

IMPORTANT:
For validation of PS interfaces: One FTP per RNC is sufficient.
6 Document result of PS call test in Call test sheet.
7 Continue with further call tests or change cell locking status:

If ... Then ...

PS call test is the last call test of the Inform integrator to change locking
FDD cell under test status of Node B
Further call tests need to be Execute next communication test
performed on this FDD cell
8

IMPORTANT: After finalization of all communication tests all FDD

cells of the Node B under communication testing have to be unlocked.

June 30, 2014 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 6: External alarms test small/medium

cabinet (Optional)

Description This test is the validation that external PSU alarms are displayed at the OMC when they occur.

Tested
Configuration

IMPORTANT: This test has only to be performed in case of d2U or d4U inside the
Small Outdoor cabinet (S6)
Medium Outdoor cabinet (Md4 or Md6)

Precondition Integrated Node B:

Small Outdoor cabinet (S6)
Medium Outdoor cabinet (Md4 or Md6)
Integration of external PSU alarms have been done
Site engineer at Node B site to trigger alarms

Test Sample It is economically not feasible to test all external alarms. Simple and quick validation can be
done by checking the door alarm

External PSU Execute following steps to validate correct display of external PSU alarm (Door Alarm):
alarms test
procedure
Door Alarm Step Action
1 Open door of Small or Medium Cabinet to trigger Door Alarm (Site
Engineer)
2 Open layout view on WMS (NSP) Node B resource browser

Continued on next page

28 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 6: External alarms test small/medium

cabinet (Optional), Continued

External PSU
alarms test
Step Action
procedure
Door Alarm 3 Set cursor on the Node B NE and click on the right mouse button to open pull-
(continued) down menu and select Show Alarms in new Window to open Alarm manager
Window.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 6: External alarms test small/medium

cabinet (Optional), Continued

External PSU
alarms test
Step Action
procedure
Door Alarm 4 Verify occurrence of Door Alarm.
(continued)
NOTE: Alarm manager window must display Door Alarm

5 Close door of Small or Medium Cabinet to remove alarm condition (Site

Engineer)
6 Validate that the Door Alarm has disappeared at WMS in OMC alarm view

30 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 7: External PSU alarms test medium cabinet

(Optional)

Description This test is the validation that an external PSU alarm of the medium cabinet is displayed at the
OMC when they occur

Tested
Configuration

IMPORTANT: This test has only to be performed in case of d2U or d4U inside the
Medium Outdoor cabinet (Md4 or Md6).

Preconditions Integrated Node B: Medium Outdoor cabinet (Md4 or Md6)

Integration of external PSU alarms have been done
Site engineer at Node B site to trigger alarms

Test Sample It is economically not feasible to test all power alarms. Simplest and quick validation can be
done by checking the AC mains alarm.

IMPORTANT: This test can only to be performed in case of charged backup

batteries are present.

External PSU Execute following steps to validate correct display of external PSU alarm (AC mains alarm):
alarms test
procedure AC
mains alarm Step Action
1 Switch off the AC customer breaker (which supplies the Small or Medium
Cabinet) to trigger Medium PSU ALARM = AC Mains Alarm PSU (Site
Engineer)

IMPORTANT: Do not leave AC customer breaker open for

longer than 10 min (max) to avoid full discharge of batteries

2 Open layout view on WMS (NSP) Node B resource browser

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

Proc. 7: External PSU alarms test medium cabinet

(Optional), Continued

External PSU
alarms test
Step Action
procedure AC
mains alarm 3 Set cursor on the Node B NE and click on the right mouse button to open pull-
(continued) down menu and select Show Alarms in new Window to open Alarm manager
Window.

Continued on next page

32 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Testing IEH 523, Section 410

Proc. 7: External PSU alarms test medium cabinet

(Optional), Continued

External PSU
alarms test
Step Action
procedure AC
mains alarm 4 Verify occurrence of Medium PSU ALARM = AC Mains Alarm PSU.
(continued)
NOTE: Alarm manager window must display Medium PSU ALARM = AC
Mains Alarm PSU

5 Switch on the AC customer breaker (which supplies the Small or Medium

Cabinet) to remove alarm condition (Site Engineer)
6 Validate that the Medium PSU ALARM = AC Mains Alarm PSU has
disappeared at WMS in OMC alarm view

June 30, 2014 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 523, Section 410 Node B Integration Testing

This page is left blank intentionally

34 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 411

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

RF Path Validation Testing

Table of Contents

General ............................................................................................................ 4
Description .................................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation Access ...................................................................................... 5
Applicable IEH521 sections ................................................................................. 5
Applicable Methods Documents............................................................................ 6
RF Path Test Tools .............................................................................................. 7
Description .................................................................................................... 7
Equipment needs remote / NSP ......................................................................... 7
RF Path Test Process ............................................................................................ 8
Description .................................................................................................... 8
RF Path Test Process ........................................................................................ 8
Proc. 1: RF Path Tests with WMS - Preparation ............................................................ 9
Description .................................................................................................... 9
Pre-conditions ................................................................................................ 9
Use Cases of antenna functional tests preparation procedures ..................................... 9
Procedure Un-locking of FDD cells .................................................................... 10
Procedure Check the PCPICH Power of FDD cells .................................................. 13
Selection of the Measurement Solution ................................................................ 15
Proc. 2: RF Path Tests with WMS BTS Radio Power tab ............................................... 16
Description .................................................................................................. 16
Preconditions ............................................................................................... 16
Procedure BTS Radio Power tab Selection ........................................................... 17
Procedure RTWP/RSSI and TX Power Measurements ............................................... 20
Proc. 3: RF Path Health Check - Telnet Preparation - Optional ...................................... 24
Description .................................................................................................. 24
Preconditions ............................................................................................... 24
Procedure Log-in to the WMS server with Telnet Commands .................................... 25
Procedure Log-in to the Node B with Telnet Commands .......................................... 28

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Procedure - Display Data List of all Radio Elements ................................................. 29

Procedure - Display Data List of One Radio Element ................................................ 33
Telnet Command Show 1 (example) part 1 - General RE information ........................ 40
Telnet Command Show 1 (example) part 2 Measurement results............................ 41
Telnet Command Show 1 (example) explanation of measurement results ................... 42
Procedure Log-in to the Radio Element with Telnet Commands ................................ 43
Proc. 4: RF Path Tests for ASB Products (2x60w or 60w-21C) - Optional ............................ 45
Description .................................................................................................. 45
Purpose of RE test ......................................................................................... 45
Preconditions ............................................................................................... 45
Procedure Login to ASB RRH Product ................................................................... 46
RE local terminal command list ......................................................................... 47
Selection of Telnet Command for Return Loss measurement ...................................... 47
Conversion of the Return Loss Value to VSWR Value for ASB Products ........................... 48
Procedure - VSWR Measurement for Twin RRH 2x60w ............................................... 49
Multiple RRH measurements ............................................................................. 51
Procedure - VSWR Measurement for RRH 60w ........................................................ 52
Multiple RRH measurements ............................................................................. 54
Procedure - TX Power Measurement .................................................................... 54
Multiple RRH measurements ............................................................................. 57
Procedure RSSI Measurement .......................................................................... 58
Multiple RRH measurements ............................................................................. 60
Proc. 5: RF Path Tests for MTI - GPCS Products (60w-21) - Optional................................. 61
Description .................................................................................................. 61
Purpose of test ............................................................................................. 61
Preconditions ............................................................................................... 61
Procedure Login to GPCS RE ............................................................................ 62
Conversion of the Return Loss Value to VSWR Value for GPCS Products ......................... 63
Procedure - VSWR Measurement ........................................................................ 64
Multiple RRH measurements ............................................................................. 65
Procedure PA Gain Measurement ...................................................................... 66
Multiple RRH measurements ............................................................................. 68
Procedure - TX Power Measurement .................................................................... 69
Multiple RRH measurements ............................................................................. 70
Procedure - RSSI Measurement .......................................................................... 71
Multiple RRH measurements ............................................................................. 72
GPCS Transmitter Status (Telnet output - example)............................................... 73
GPCS Receiver Status (Telnet output - example) .................................................. 74

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA integration ..................................................... 5

Table 2: Applicable ALU Product Documents for RF path validation ............................................. 6
Table 3: ASB RE types .................................................................................................. 45
Table 4: Return Loss to VSWR value Conversion ................................................................... 48
Table 5: MTI-GPCS products supported .............................................................................. 61
Table 6: Return Loss to VSWR value Conversion ................................................................... 63

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

List of Figures

Figure 1: RF Path Tests Process and Flow ............................................................................. 8

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

General

Description This section provides information how to validate the RF path was successfully done.

Previous Release June 15, 2013

Date

Release Notes June 30, 2014: Separation of RF path tests into section 411

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
RF path validation testing.

Documentation Access to applicable documents can be made under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Use common Node B to find the latest applicable version.

Applicable The sections listed in Table 1 below are relevant for WCDMA Node B integration testing and
IEH521 sections RF path testing.

Table 1: Applicable IEH 521 Sections for WCDMA integration

Section Description
001 Introduction
401 Integration Planning
402 Integration into existing UTRAN
410 Integration Testing
499 Node B Integration Test Records

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

References, Continued

Applicable The following methods documents are required to perform RF path validation,
Methods
Documents
Table 2: Applicable ALU Product Documents for RF path validation

Doc Number Doc Title URL

UMT/OMC/DD/01 SIE External UTRAN Alarms https://infoproducts.alcatel-
3913 Dictionary lucent.com/aces/cgi-
(UTRAN Alarm Dictionary) bin/dbaccessfilename.cgi/UMTOMCD
D013913UA08.1_V1_
NN-20500-018P1 Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
UA08.1 Management System - Node B lucent.com/pdfdocs14/pristore215/52
Alarms Reference Guide 4948.pdf
(UA08.x)

9YZ-05870-0060- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-

UFZZA Management System - Node B lucent.com/pdfdocs14/pristore215/53
Alarms Reference Guide 6534.pdf
(LR13.3)

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

RF Path Test Tools

Description A small set of equipment and tools is required to validate the RF paths of a Node B

Equipment The following equipment is required for RF Path validation through remote / NSP GUI site:
needs remote / Phone access (to allow information exchange with on-site engineer)
NSP
IT equipment capable for NSP GUI operations

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

RF Path Test Process

Description The RF Path test process provides an overview and guidance about
which tests to perform
in which sequence that tests need to be performed

RF Path Test The following flow outlines the validation tasks to be performed during RF path test:
Process

Figure 1: RF Path Tests Process and Flow

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 1: RF Path Tests with WMS - Preparation

Description The Radio Element (RRH, MC RRH, Twin RRH, TRDU) for the individual frequencies (850,
900, 1900, 2100 Mhz) has to be prepared before the RF path test measurements can be
executed.

The procedures
Check that each FDDcell of a dedicated Node B are unlocked
Check the pcpichPower value of each FDDCell
Select the measurement solution
have to be performed

IMPORTANT: MC-TRX is currently not supported through this section.

Pre-conditions NSP GUI is operational

Node B under test must be known
All Node B RF Path validation Parameters Forms must be completed by the coordinator and
available for the site engineer (by email or on a dedicated link) prior to performing the
procedures.
All Radio Elements and the Node B must be connected and integrated.

Use Cases of The procedures

antenna Change Un-locking status of FDD cells
functional tests
preparation Check the pcpichPower of FDD cells
procedures Need to be used to establish the correct test environment for VSWR, TX Power and
RSSI/RTWP.
NOTE: Each procedure has to be executed for every FDD cell.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 1: RF Path Tests with WMS - Preparation,

Continued

Procedure Un- Execute the following procedure to un-lock FDD cells:

locking of FDD
cells
Step Action
1 Right click in Layout on concerned RNC (Node B under test is connected there)
to open sub-menu
2 Click on Equipment Monitor to open Equipment Monitor window

Continued on next page

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 1: RF Path Tests with WMS - Preparation,

Continued

Procedure Un-
locking of FDD
Step Action
cells (continued)
3 Select FDD cell of Node B under integration test targeted to unlock and
press Configuration|Set Administrative State.

RESULT: The Set Administrative State Action Window opens for the
selected FDD cell.
4 Change the FDDCell status if necessary

If the FDDCell Status is... Then ...

Locked Click on Unlock button to start
execution of unlock command.

Unlocked Do not change the current status

and close the Set Administrative
State Action window.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 1: RF Path Tests with WMS - Preparation,

Continued

Procedure Un-
locking of FDD
Step Action
cells (continued)
5 Monitor successful execution of Unlock command in Command Manager
window by selecting logs

RESULT: Selected FDD cell is unlocked

6 Repeat steps 1 to 5 for every FDD cell to be un-locked.

Continued on next page

12 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 1: RF Path Tests with WMS - Preparation,

Continued

Procedure Execute the following procedure to check the PCPICH power value of the FDD Cell:
Check the
PCPICH Power
of FDD cells Step Action
1 From the NE RNC/RNC pane (left of Equipment Monitor GUI)
Select the Node B concerned and open the file instances of FDDCell

2 Right click on the FDDCell for test and select Configuration | Object Editor
to open object editor window.

June 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Continued on next page

Proc. 1: RF Path Tests with WMS - Preparation,

Continued

Procedure
Check the
Step Action
PCPICH Power of
FDD cells 3 Select the pcpichPower Attribute
(continued)

4 Fill the report sheet with this pcpichPower value (dBm):

Example here: pcpichPower: 32.0 dBm

NOTE: The pcpichPower value will is required as the minimum value

reference to validate the result of the Tx Power Measurement.

5 Repeat all steps 1 to 5 for every FDD cell to check and fill the report sheet with
the pcpichPower value as reference before to measure the Tx Power.

Continued on next page

14 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 1: RF Path Tests with WMS - Preparation,

Continued

Selection of the Select the measurement solution according to the RE used and the tools (WMS or Telnet
Measurement commands) available for the tests:
Solution
NOTE: RF path test by WMS is recommended
Covers radio equipment from all suppliers
Limited effort to validate RF path

IMPORTANT: RF path tests by Telnet Commands is optional and mainly

recommended for troubleshooting because it is work intense and time consuming.

NOTE: Equipment of the following suppliers is covered

ASB
MTI-GPCS
Panasonic
MC-RE

If it is necessary to do ... Then ...

Measurement through the WMS tool. Go to Logical & Physical Resources
BTS Radio Power tab
Measurement through telnet commands for Have ASB or MTI-GPCS RRHs or TRDU
troubleshooting (optional) 2x80-21 Panasonic or MC-RE (MC-
RRH2x40-900Mhz or MC-TRDU2x60-
900Mhz)
No WMS access available or need more
detailed measurement results (e.g.
trouble shooting)
Go to Telnet Preparation

June 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 2: RF Path Tests with WMS BTS Radio Power

tab

Description Measurement for RTWP and TX Power can be performed remotely through the WMS and
displayed at the WMS GUI for
all Radio Elements (RRH, MC RRH, Twin RRH, TRDU, MC-TRDU, TRDU 2x80)
all frequency bands (850, 900, AWS,1900, 2100 Mhz)

The following procedures explain how to start measurements and how to read the displayed
values.

Preconditions The Node B is completely integrated and fully visible at the WMS.
Laptop available with access to WMS server
Laptop connected to the internet network with RJ45
WMS SSH server details and login details (Login and password) are available
Node B IP address and login details (Login and password) are available
The reference pcpichPower value for the Radio Equipment under test is available for
validation (e.g. by means of the suitable procedures of this IEH 521 handbook)

NOTE: Site access to Remote Radio Head is needed only in case of troubleshooting.

Continued on next page

16 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 2: RF Path Tests with WMS BTS Radio Power

tab, Continued

Procedure BTS The following procedure allows to select the BTS radio Power tab to allow access to the
Radio Power requested RTWP and TX Power measurements values.
tab Selection

Step Action
1 Log in to the WMS SSH server.
2 Click right on the distributed Node B of the Resource Browser

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 2: RF Path Tests with WMS BTS Radio Power

tab, Continued

Procedure BTS
Radio Power tab
Step Action
Selection
(continued) 3 Select Configuration | Logical & Physical Resources to open Logical &
Physical Resources window.

Result: Logical & Physical Resources window opens

4 Select the dedicated RNC at the pull-down menu of RNC

5 Select the dedicated BTS at the pull-down menu of BTS

Continued on next page

18 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 2: RF Path Tests with WMS BTS Radio Power

tab, Continued

Procedure BTS
Radio Power tab
Step Action
Selection
(continued) 6 Select BTS Radio Power tab

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 2: RF Path Tests with WMS BTS Radio Power

tab, Continued

Procedure The following procedure allows to display the RTWP and TX Power measurement values
RTWP/RSSI and
TX Power
Measurements Step Action
1 Click on Display to refresh all RTWP and TxPower measurements on all
RRHs connected to the selected Node B (BTS).

NOTE: RTWP and TxPower values display in the BTS Radio Power window.

2 Extract values for RTWP from displayed Sector Radio Power data and
transfer to test report sheets.

NOTE: The following When/Then table explains how to read the displayed

When a value in column ... Then means value of ...

Sector The list of string elements with the
(example: antennaConnection_1, antenna connection.
antennaConnection_2,
antennaConnection_3)
Admin State The administrative State of the
(locked or unlocked) FDDcell

Continued on next page

20 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 2: RF Path Tests with WMS BTS Radio Power

tab, Continued

Procedure
RTWP/RSSI and
Step Action
TX Power
Measurements 3 Extract RTWP values from displayed data and transfer to test report sheet.
(continued)
NOTE: Refer to the following description for RTWP (Received Total Wideband
Power) values as displayed in Cell Radio Power pane

When a value in column... Then ...

Main (dBm) RTWP/RSSI is measured at the
(rtwpMain attribute) main antenna connection
The result must be close to Div
value.
Div (dBm) RTWP/RSSI is measured at the
(rtwpDiv attribute) diversity antenna connection
The result must be close to Main
value.
Combined (dBm) Average of Main and Diversity
(rtwpCombined attribute) values at the antenna connection.
The result should be close to Main
and Div values.(accepted gap
2dBm)
NOTE: If not within this limits trouble
shooting is required.
Reference (dBm) The reference (- dBm) is the
(rtwpReference attribute) minimum radio noise level of this
site when cells are not loaded
(none call) on the antenna.
It is use as reference indicator for
troubleshooting and should
therefore be recorded.
The result of Main and Div(- dBm)
values must be better to avoid the
minimum radio noise level.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 2: RF Path Tests with WMS BTS Radio Power

tab, Continued

Procedure
RTWP/RSSI and
Step Action
TX Power
Measurements 4 Analyze RTWP/RSSI results (Main, Div, Combined and Reference values) for
(continued) correctness and perform action if necessary:

If the RX Power (RSSI/RTWP) Then the RX Power

value measured ... (RSSI/RTWP) measurement
...
Is superior to - 108 dBm is acceptable and validated
(> - 108 dBm)
NOTE: Tested radio equipment is
working properly in its receive band
Is inferior to - 108 dBm is not acceptable (faulty) and
(< -108 dBm) means there is an issue

NOTE: Contact coordinator for

troubleshooting of RTWP/RSSI
issue

5 Record RTWP/RSSI analysis results on the report sheet.

6 Extract the TX Power (Transmitted Carrier Power) values as displayed in the
Cell Radio Power pane or in the Sector Radio Power pane and transfer to
test report sheet

NOTE: The following table explains the meaning of the different values

When a value is in column Then this value means...

...
Tx_3GPP (dBm) the absolute txpower measured at
(txPowerSector-3gppRef attribute) antenna level as it is defined by
3GPP.
Tx_DDM (dBm) the absolute txpower measured at
the RF output connector of the
Radio Element (RRH or TRDU).

NOTE: The difference between Tx_3GPP and TX_DDM must be minimal.

Continued on next page

22 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 2: RF Path Tests with WMS BTS Radio Power

tab, Continued

Procedure
RTWP/RSSI and
Step Action
TX Power
Measurements 7 Analyze the output power (TX Power) results for correctness and perform
(continued) action if necessary:

NOTE: The pcpichPower value is the reference for the TX Power (Tx_3GPP
and Tx_DDM) analysis.

If the TX Power measured Then the Tx Power

... measurement ...
Is superior to pcpichPower is acceptable and validated
(> pcpichPower)
NOTE: The tested radio equipment
is working properly at the TX
interface
Is close to TX Power Max is acceptable and validated
(Example of Max TX Power:
TX P Max : 47.7w for RRH 60w) NOTE: The tested radio equipment
is working properly at the TX
interface

NOTE: The tested radio equipment

is used in the maximum traffic
conditions.
Is inferior to pcpichPower is not acceptable and means there
(< cppichPower) is an issue

NOTE: Contact coordinator for

troubleshooting of TX Power issue

8 Record TX Power analysis results on reporting sheet

9 Close the Logical & Physical Resources window and the WMS.

June 30, 2014 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional

Description Telnet commands can be used remotely to perform specific health checks for the RF path of a
Node B under test.
RF path tests through remote Telnet commands have to be understood as extension of the
WMS based RF path tests and provide additional information (e.g. to support trouble shooting)

Preconditions Node B is completely integrated on the WMS.

Laptop available with a terminal emulator : e.g. Putty (or equivalent)
Laptop connected to the internet network with RJ45
WMS SSH server details, Login details (Login and password) are available
Node B IP address and login details (Login and password) are available
Only remote access to Remote Radio Head is needed to execute some RRH telnet
commands.

NOTE: RF path test through Telnet commands are remote tests and do not required site
access to the equipment under test.

Continued on next page

24 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure Log- The following procedure details how to log-on to the WMS SSH server to allow usage of Telnet
in to the WMS commands.
server with
Telnet
Commands Step Action
1 Open the terminal emulator, for example here: Putty
Select Logging with the following parameters to save the session to provide
a full report sheet.
Select All session output
Select Browse to specify the name of the session to record (and set its
location)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure Log-
in to the WMS
Step Action
server with
Telnet 2 Connect to the WMS SSH server:
Commands Type the WMS IP address into the Host Name
(continued)
Select the connection type: SSH
Click Open

NOTE: WMS SSH server requests Login and Password

Continued on next page

26 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure Log-
in to the WMS
Step Action
server with
Telnet 3 Log-in to WMS SSH server:
Commands Enter the dedicated Login:
(continued)
Enter dedicated Password:

Expected Output:

login as: oamops

This system is a restricted access system. All activity on

this system is subject to monitoring. If information
collected reveals possible criminal activity or activity
that exceeds privileges, evidence of such activity may
be provided to the relevant authorities for further
action. By continuing past this point, you expressly
consent to this monitoring.

Using keyboard-interactive authentication.

Password:
Last login: Tue Jun 4 11:42:42 2013 from 135.120.1xx.xxx
Oracle Corporation SunOS 5.10 Generic Patch
January 2005
You have mail.
rapido:/home/oamops <101> (oamops) %

or depending to WMS SSH Server

Expected Output depending of the WMS configuration:

login as: BEHYAN

Using keyboard-interactive authentication.
Password:
Last login: Tue Jun 4 15:19:15 2013 from 135.244.2xx.xxx
Oracle Corporation SunOS 5.10 Generic Patch
January 2005
$

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure The following procedure describes how to log-in to the Node B

Log-in to the
Node B with
Telnet Step Action
Commands
1 Telnet to the Node B IP Address
Type: telnet [nodeb_ip_address]

Expected Output:
telnet 10.1.132.xxx
Trying 10.1.132.xxx...
Connected to 10.1.132.xxx.
Escape character is '^]'.
223.254.254.xxx login:

2 Type Login: nodeb | <enter>

Expected Output:
223.254.254.xxx login: nodeb

3 Type Password: nodeblnx | <enter>

NOTE: the password is not displayed on telnet screen while you type

Expected Output:
Password: nodeblnx

LINUX
~ ~ ~
\ | /
\ | /
\|/
^ #####################
| # #
+=====# Node B #<<<<<<<<->>>>>>>>
# xccm #
#####################

[ 08-Oct-2012 23:24 ]

xCCM-nodeb-nodeb>

NOTE: You are now connected to the CCM Board of the Node B.

Continued on next page

28 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure - The following procedure details how to display the data list for all Radio Element (RE)
Display Data connected on CPRI links.
List of all Radio
Elements
Step Action
1 Type: bcish | <enter>

Expected Output:

xCCM-nodeb-nodeb> bcish
/$

NOTE: You are now on the CCM OS terminal to run the BCI application and to
access the BCI menu.
2 Type: pltf and type on the Tabulation key
(an additional number appears after pltf)
on the BCI root menu

Expected Output:

xCCM-nodeb-nodeb> bcish
/$ pltf_579/
/pltf_579$

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of all Radio
Elements 3 Type: reproxy | <enter>
(continued)
on the CCM OS terminal to run the BCI application and to access the BCI
menu.

If there is a need to display Then ...

...
the data list for all connected Radio Type: show x to display the data list
Elements (RE). for all RE
The data list for one specific Radio Go directly to the next Procedure to
Elements (RE) Display Data List of one RE

Expected sequence:

xCCM-nodeb-nodeb> bcish
/$ pltf_579/
/pltf_579$ reproxy
/pltf_579/reproxy$
/pltf_579/reproxy$ show x

Continued on next page

30 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of all Radio
Elements 4 Use the RE (Radio Element) data list to check how many RE are connected
(continued) on each CPRI link and transfer this date to the report sheet for later use.

NOTE: The CPRI Link is the optical link (with RRH) or electrical link (with
TRDU) between the CCM-U of the Node B and the Radio Element (RE)

Example:
No RE is connected on CPRI link 1, 3, 4, 5, 6.
The RE for test is connected on CPRI link number 2
+- - - - - - - - - - - - - - - - - - - - - - - - - - - +
RE Configuration
----------------------
Number of connected REs : 1 means the number of CPRI
links used to connected between the Node B and the RE
No RE connected on link 1 means the CPRI link 1 is
not connected to the RE
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
Link : 2
Link state : CPRI_LINK_STATE_UP
Number of RE : 1
Reset Counters : 0 0 0 0 0 0
Reset Counters Timer : 0 0 0 0 0 0
- - - - - - - - - - - - - - - -
RE : 21
RE Vendor : ASB RRH(8) Give the name of the
Manufacturer of the RE for decision making which Telnet commands to
use
RE state : CPRI_RE_STATE_L3_UP
RE IP Address: 192.168.130.1 Provides the RE IP
address for use at a later stage for direct Telnet connection through CCM
(with Telnet Commands)
And at the end of the RE Data List :
- - - - - - - - - - - - - - - - - - - - - - - - - - - -
No RE connected on link 3
No RE connected on link 4
No RE connected on link 5
No RE connected on link 6 means the CPRI link 3, 4 ,
5, 6 are not connected to one RE.
+- - - - - - - - - - - - - - - - - - - - - - - - - - - +
/pltf_579/reproxy$

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of all Radio
Elements 5 Retrieve the following information from the RE (RRH or TRDU) Data list and
(continued) transfer to the report sheet sheets:
Number of RE connected
RE Vendor
RE IP Address
6 Analyze RE data list for
Single RRH connected at its CPRI link
Multiple RRHs are respectively connected at their CPRI link (up to 6)

If a CPRI link connects... Then ...

only one radio element (RE) perform the next step Logout of
the BCI application and
NOTE: example in step 4 of this go directly to Procedure Log-in
procedure to the Radio Element

More than one radio element (RE) Go directly to step 4 of the next
Procedure Display Data List of
One RE

7 Enter exit to logout from the BCI application.

Continued on next page

32 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure - The following procedure details how to

Display Data
display the data list of one specific Radio Element (RE) which is connected through one
List of One CPRI link
Radio Element
check the RF path health.

Step Action
1 Type: bcish | <enter>

Expected Output:
xCCM-nodeb-nodeb> bcish
/$

NOTE: CCM OS terminal must be in BCI application and allows to access the
BCI menu.
2 Type: pltf and strike the Tabulation key while you are in the root menu.

NOTE: an additional number will be displayed behind pltf

Expected Output:
xCCM-nodeb-nodeb> bcish
/$ pltf_579/
/pltf_579$
3 Type: reproxy | <enter> to access the BCI menu

Expected Output:
/pltf_586/reproxy
/pltf_586/reproxy$

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of One Radio
Element 4 Select the CPRI link number for the RE to be validated and type: show <CRPI
(continued) link number> | <enter> to display the data of the RE (RRH or TRDU)
connected to this CPRI link

NOTE: <CPRI link number> can range from 1 to 6.

NOTE: Type the following telnet commands are available to display the data of
RE individually or in a whole:

If you type the telnet Then the data of all RE

command ... connected at...are
displayed
show 1 CPRI Link 1
show 2 CPRI Link 2
show 3 CPRI Link 3
show 4 CPRI Link 4
show 5 CPRI Link 5
show 6 CPRI Link 6
show x all RE connected

Example: Show RE data of RE which is connected at CPRI link 1: See

separate block - Telnet Command Show 1 (example)
5 Retrieve data from the RE (or RRH) Data list and transfer to report sheet:
RuName:
PecCode:
SerialNumber:
RE Vendor
NumberOfCells

NOTE: NumberOfCells must not be 0 otherwise no measurement can be

performed

Continued on next page

34 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of One Radio
Element 6 Retrieve and post calculate for each LocalCellId the following measurement
(continued) values from RE (or RRH) Data list and transfer to report sheet : RX

When the measurement is Then the result value to

... read and to fill into the
report sheet ...
RxPowerMain is the measured and then post
calculated RX Power Main value (in
dBm) :

Calculation:
RX Power Main (dBm) = (-112dBm
reference value) - (- RxPowerMain
value)
RxPowerDiv is the measured and then post
calculated RX Power Div value (in
dBm)

Calculation:
RX Power Div (in dBm) = (-112dBm
reference value) (- RxPowerDiv
value)
RxPowerComb is the measured and then post
calculated RXPower Comb
average value between RX Power
Main and Div (in dBm)

Calculation:
RXPower Comb (dBm) = (-112dBm
reference value) (-
RxPowerComb value)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of One Radio
Element 7 Retrieve and post calculate for each LocalCellId the following measurement
(continued) values from RE (or RRH) Data list and transfer to report sheet : TX

When the measurement is Then the result value to

... read and to fill into the
report sheet ...
TxPowerCell (%) is the measured and then post
calculated value of TxPowerCell
Main (in dBm)

Calculation:
TX PowerCell (dBm) = 10 log (1000
x (MaxTxPowerlinear (W) x
TxPowerCell %))
TxPowerCell_Div (%) is the measured and then post
calculated value of TxPowerCell
Div (in dBm)

Calculation:
TX PowerCell_Div (dBm) = 10 log
(1000 x (MaxTxPowerlinear (W) x
TxPowerCell_Div %))
TxPowerCell to CallP (%) is the measured and then post
calculated value of TxPowerCell to
CallP (in dBm)

Calculation:
TX Power Cell to CallP (dBm) = 10
log (1000 x (MaxTxPowerlinear (W)
x TxPowerCell to CallP %))

Continued on next page

36 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of One Radio
Element 8 Analyze the RSSI results (RxPowerMain, RxPowerDiv and RxPowercomb) for
(continued) health and initiate trouble shooting action if necessary

If the RX Power (RSSI/RTWP) Then the RX Power

values are... (RSSI/RTWP) measurement
result ...
superior than - 108 dBm is healthy and validated
(> - 108 dBm)
NOTE: The RE working properly in
the receive band.
inferior or equal to - 108 dBm is not healthy and there is an
(< -108 dBm) issue

NOTE: Trouble shooting is required

to understand why the detected
RSSI/RTWP is not close to the
expected value.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of One Radio
Element 9 Analyze the output power (TX Power) results in dBm (TxPowerCell Main,
(continued) TxPowerCell Div and TxPowerCell to callP) for health and initiate trouble
shooting action if necessary

NOTE: The pcpichPower is the reference value of TX Power (Tx_3GPP and

Tx_DDM) and must be available as input (see previous procedure)

If the TX Power values are Then the Tx Power

... measurement ...
superior than pcpichPower is healthy and validated
(> pcpichPower)
NOTE: The RE TX power is working
properly.
close to TX Power Max is healthy and validated
(Example of Max TX Power:
TX P Max : 47.7w for RRH 60w) NOTE: The RE TX power is working
properly.

NOTE: The RE is used in maximum

traffic conditions
inferior than to pcpichPower is not healthy and there is an
(< cppichPower) issue

NOTE: Trouble shooting is required

to understand why the detected
TXPower values are not close to the
expected value.

NOTE: The RE may not be

configured.

Continued on next page

38 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure -
Display Data List
Step Action
of One Radio
Element 10 Retrieve RE IP Address under test from the RE (or RRH) Data list and
(continued) transfer it into the report sheet
11 Verify for each RE IP address for the connected RE that it matches with the
following table.

x RE (or Syntax Example IP Address

RRH)
CPRI Link 1 1 11 Reproxy | show 1 192.168.129.1
CPRI Link 2 2 21 Reproxy | show 2 192.168.130.1
CPRI Link 3 3 31 Reproxy | show 3 192.168.131.1
CPRI Link 4 4 41 Reproxy | show 4 192.168.132.1
CPRI Link 5 5 51 Reproxy | show 5 192.168.133.1
CPRI Link 6 6 61 Reproxy | show 6 192.168.134.1

12 Logout of the BCI application.

Type: cd ..
Type: cd ..
Type: exit to logout of the BCI to Node B CCM OS terminal/telnet session.

Expected Output:
/pltf_591/reproxy$ cd ..
/pltf_591$ cd ..
/$ exit
End of session
/$ Disconnection from 'launcher_518'
Disconnection from 'pltf_591'
eCCM-nodeb-nodeb>

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Telnet Example of Telnet Command Show 1 (as used in Procedure Display Data List of One
Command Radio Element)
Show 1 Example: Shows RE data of RE which is connected at CPRI link 1:
(example) part
/pltf_586/reproxy$ show 1
1 - General RE
- - - - - - - - - - - - - - - - - - - - - - - - - - -
information
Link : 1
Link state : CPRI_LINK_STATE_UP
Number of RE : 1
Reset Counters : 0 0 0 0 0 0
Reset Counters Timer : 0 0 0 0 0 0
- - - - - - - - - - - - - - - - - - - - - - - - - - -
RE : 11
RE Vendor : ASB RRH(8) RE manufacturer
RE state : CPRI_RE_STATE_L3_UP
RE IP Address: 192.168.129.1 RE IP address on the CPRI Link number 1
RE lib type : 0
RE Master RE state : Slave RE(MIMO use)
RE Software Status:
Active SwRed : _BI_RE_ASB2X_BAND01_FV_P03B0
Passive SwRed : _BI_RE_ASB2X_BAND01_FV_P0370
SelfTestResults: 0
SelfTestDetails:
LastResetReason: L1 RESET
FrequencyBand : 1
HwRef : 0x703
RuName : MOD:RRH2x60-21 RU name
PecCode : 3JR10050AAAA01 PecCode of the RE
SerialNumber : YP12260CE63 Serial Number of the RE
ManufDate :
HwRelease : P000
DHCP Timer : 0
L1 Timer : 0
Tod Timer : 353
LedNum : 1
LedColor : Green
LedStatus : ON
LedInfo :
AlarmNumber : 0
Sector 0 : sector number
:::
.further information is displayed as a response to the show 1 command (see next block)

Continued on next page

40 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Telnet Example of Telnet Command Show 1 (as used in Procedure Display Data List of One
Command Radio Element)
Show 1 Example: Show RE data and measurement results of RE which is connected at CPRI link 1:
(example) part
/pltf_586/reproxy$ show 1
2 Measurement
results .continuation of information as displayed as a response to the show 1 command (see previous
block)
:::
TxPathLossMain : ----
TxPathLossDiv : ----
MaxDlPowerCap : 47.800000 dBm
MinDlPowerCap : 21.800000 dBm
MinCpichPower : 11.800000 dBm
TxOutputLoss : 0 0.1dB
RxInputCablesLossMain : 0 0.1dB
RxInputCableLossDiv : 0 0.1dB
downlinkDelayMain : 2055 Tc/32
downlinkDelayDiv : 0 Tc/32
UplinkDelayMain : 864 Tc/32
UplinkDelayDiv : 864 Tc/32
RE Cell Status:
Sector : 0 NumberOfCells : 4 number of configured cells
LocalCellID : 14022 Identifier number of the cell under check
isMainCell : 0
CellConfig : SINGLERE_SECTOR_STANDARD_MAIN
RxAxC_Main : 0
RxAxC_Div : 1
TxAxC_Main : 0
TxAxC_Div : 255
RxFrequency : 9614 UARFCN
TxFrequency : 10564 UARFCN
MaxTxPower : 41.700000 dBm
MaxTxPowerRE: 41.700000 dBm
MaxTxPowerLinear : 14791.083984
RxPowerMain : 61 0.1dB
RxPowerDiv : 57 0.1dB
RxPowerComb : 59 0.1dB
TxPowerCell : 17 %load
TxPowerCell_Div : 0 %load
TxPowerCell to CallP : 0 %load
TxPower3gpp : 17 %load
TxPower3gpp_Div : 0 %load
TxPower3gpp to CallP : 0 %load
RTWP-AverageReportPower : 58.589722
TPC -AverageReportPower : 17.000000

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Telnet The following RX and TX measurement results are displayed as a result of the Telnet
Command command. The following example explains how to read the displayed measurement values.
Show 1 /pltf_586/reproxy$ show 1
(example) MaxTxPowerRE: 41.700000 dBm
explanation of Maximum TX Power of the RE
measurement
MaxTxPowerLinear : 14791.083984 mW
results
Maximum TX Power Linear: here = 14.791 Watts
RxPowerMain : 61 0.1dB
RX Power Main
Calculation:
Reference value RxPowerMain Value
(-112 dBm) - (-6.1 dBm) = - 105.9 dBm
RxPowerDiv : 57 0.1dB
RX Power Diversity
Calculation:
Reference value RxPowerDiv Value
(-112 dBm) - (-5.7 dBm) = - 106.3 dBm
RxPowerComb : 59 0.1dB
Combined value between RX Power Main and Div
Calculation:
Reference value RxPowerComb Value
(-112 dBm) - (-5.9 dBm) = - 106.1 dBm
TxPowerCell : 17 %load
value of TxPowerCell Main (in dBm)
Calculation:
10 log (1000 x (MaxTxPowerlinear (W) x TxPowerCell (%))
10 log (1000 x 14.791(W) x 17%) = 34 dBm
TxPowerCell_Div : 0 %load
value of TxPowerCell Div (in dBm)
Calculation:
10 log (1000 x (MaxTxPowerlinear (W) x TxPowerCell_Div (%))
10 log (1000 x 14.791(W) x 0%) = N/A
TxPowerCell to CallP : 0 %load
TxPowerCell Main (in dBm)
Calculation:
10 log (1000 x (MaxTxPowerlinear (W) x TxPowerCell to CallP(%))
10 log (1000 x 14.791(W) x 0%) = N/A
TxPower3gpp : 17 %load
TxPower3gpp_Div : 0 %load
TxPower3gpp to CallP : 0 %load
RTWP-AverageReportPower : 58.589722
TPC -AverageReportPower : 17.000000

Continued on next page

42 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure The following procedure allows to login to an individual Radio Element (RE) by use of Telnet
Log-in to the commands
Radio Element
with Telnet
Commands Step Action
1 Type: telnet [rrh_ip_address] | <enter>

NOTE: This establishes a telnet connection to the RRH IP address (local

Ethernet IP address assigned by the d2U/d4U) from the d2U/d4U CCM OS
terminal.

Expected Output:
eCCM-nodeb-nodeb> telnet 192.168.129.1

2 Enter Login/Password

NOTE: Login and passwords differ between RRH products and are explained
in the table below.

If RE module used is... Then use the ...

Login Password
RRH60-21C (ASB)
Twin RRH2x60-2100 (ASB)
asb asb#1234
Twin RRH2x60-850 (ASB)
Twin RRH2x60-1900 (ASB)
RRH 60-21 (GPCS)
n.a. n.a.
TRDU60-21 (GPCS)
TRDU 2x80 (Panasonic) root nodeb3G
MC-RE (MC-RRH, MC-TRDU) newclass nc_tmxda

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 3: RF Path Health Check - Telnet Preparation

- Optional, Continued

Procedure Log-
in to the Radio
Step Action
Element with
Telnet 3 Select procedure for further detailed RF path tests
Commands
(continued) NOTE: Telnet commands will be specific according to the RE Vendor for the
products as per table below

If RE Vendor is... Then ...

ASB Apply the Procedure for ASB
Products
Products:
2x60-2100 Mhz
2x60-850 Mhz
2x60-1900 Mhz
60-2100 Mhz C
MTI (TELASIC/GPCS) Apply the Procedure for MTI-GPCS
Products
Products:
RRH 60-21
TRDU 60-21
Panasonic Apply the Procedure for TRDU 2x80
Products
Product:
TRDU 2x80-2100Mhz
Multi Carrier-Radio Element Apply the Procedure for MC Radio
Element Products
Product
MC-RRH 2x40-900Mhz
MC-TRDU 2x60-900Mhz

NOTE: This table gives the RE products (RRH or Twin RRH or TRDU or MC-
RRH 2x40-09 or MC-TRDU 2x60-09 or TRDU 2x80-21) tested and usable with
Telnet Commands.
4 Type: logout to logout from RRH local terminal.

44 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional

Description This tests allow to retrieve

VSWR measurement values
Transmit Power Level values
RSSI (Received Signal Strength Indicator) level values
from the RE of manufacturer ASB and analyze the RF path (TX and RX).

NOTE: The RE types manufactured by ASB

Table 3: ASB RE types

RE Type RU Name PEC code
MOD: RRH 2x60-2100 Mhz 3JR10050AA
Twin RRH MOD: RRH 2x60-850 Mhz 3JR10601AA
MOD: RRH 2x60-1900 Mhz 3JR10801AA
RRH MOD: RRH 60-21 C 3BK28876AD

Purpose of RE The purpose of this test is to provide confidence that the Node B is radiating inside specified
test and adjusted power values and is properly receiving RX signals.

Preconditions Node B is completely integrated on the WMS.

Laptop available with a terminal emulator : here for example using Putty (or equivalent)
RRH IP address (according to the CPRI Link from the Telnet Preparation Procedures)
The reference pcpichPower value is checked with help of the previous dedicated procedure
and available into the report sheet
Only remote access to Remote Radio Head is needed to execute some RRH telnet
commands.

NOTE: Site access to Remote Radio Head is needed in case of troubleshooting only.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure The following procedure allows to log-in to the ASB RRH product
Login to ASB
RRH Product
Step Action
1 Type: telnet [rrh_ip_address] <enter>

Result:
This establishes the telnet connection to the RE IP address of the CCM OS as
bridgehead towards the RRH for test (this is the local Ethernet IP address
assigned by the d2U/d4U) from the distributed Node B.

Expected Output:
eCCM-nodeb-nodeb> telnet 192.168.129.1

2 Type Login | Password dedicated to ASB Product: asb | asb#1234

Expected Output:
Entering character mode
Escape character is '^]'.
Welcome to ASB RRU World ...
RRH2T login: asb
Password:
RFH1-1>
3 Type: bci

This will cause CCM OS terminal to run the BCI application and to access the
BCI menu.
4 Type the Login | Password dedicated to ASB Product: asb | asb#1234
to access the RE local terminal.

Expected Output:
RFH1-1>bci

Entering character mode

Escape character is '^]'.
Session is opened.
RRH2T login: asb
Password for asb:

Login successful
>

Continued on next page

46 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

RE local The RE local terminal allow the following commands and can be displayed by use of the
terminal command > ls
command list
Expected Output:
> ls
> cliproxy cliproxy
> cliserver cliserver commands
> context trace/error facilities
> debug Debug commands
> kernel Kernel space
> oam oam commands
> pltf Platform commands
> radioc radioc commands
>

NOTE: At anytime ls can be used to remind the available commands at each level for this RE.

Selection of Select the Return Loss Telnet command according to the RE used. to retrieve the VSWR
Telnet value.
Command for
Return Loss
measurement If the ASB product is ... Then use the Telnet command ...
RRH 2x60w getVswrReturnLoss 1
(adding 1 for TX1 or 2 for TX2)

NOTE: Continue with the procedure

VSWR Measurement for Twin RRH 2x60w
RRH 60w rctlAntTestTraceFlag=0x7fffffff

NOTE: Continue with the procedure

VSWR Measurement for RRH 60w

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 47

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Conversion of To retrieve the VSWR value before to analyze the result, the Return Loss value must be
the Return Loss converted according to the following conversion table.
Value to VSWR
Value for ASB NOTE: The grey cells of this table 3 show non- acceptable VSWR values and mean that there
Products is a potential issue on the RF path connection. A troubleshooting operation must be planned
with the site coordinator.

Table 4: Return Loss to VSWR value Conversion

RL(dB) VSWR RL(dB) VSWR RL(dB) VSWR RL(dB) VSWR

46.1 1.01 25.7 1.11 18.0 1.29 8.0 2.32
40.1 1.02 24.9 1.12 17.0 1.33 7.0 2.61
36.6 1.03 24.3 1.13 16.0 1.38 6.0 3.01
34.1 1.04 23.7 1.14 15.0 1.43 5.0 3.57
32.3 1.05 23.1 1.15 14.0 1.50 4.0 4.42
30.7 1.06 22.6 1.16 13.0 1.58 3.0 5.85
29.4 1.07 21.7 1.18 12.0 1.67 2.0 8.72
28.3 1.08 20.8 1.20 11.0 1.78 1.0 17.4
27.3 1.09 20.0 1.22 10.0 1.92 0.5 34.8
26.4 1.10 19.0 1.25 9.0 2.10 0.0 Infinity

NOTE: Conversion between Return Loss and VSWR can be done as per following calculation
rules

If convertion is required Then use the formula...

from ...
Return Loss to VSWR value VSWR = [1 + 10( Return loss / 20)] / [1 10( Return loss / 20)]
VSWR to Return Loss value Return Loss (dB) = 20 log [(VSWR 1)/(VSWR+1)]

Continued on next page

48 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure - The following procedure allows to measure the VSWR value on ASB RRH 2x60w (twin RRH)
VSWR only.
Measurement
for Twin RRH
2x60w Step Action
1 Type: debug
Type: antennatests
Type: ls
on the RE local terminal to be into the menu of VSWR measurement and
to view all VSWR tests available on this RE module

Expected Output:
/debug> antennatests
/debug/antennatests> ls
antTestHelp Print this list
setTxVswrAlarmThreshold Set threshold value for Vswr
alarm
enableVSWRTurnOffPA Enable/Disable PA for Vswr
getVswrThreshold Display current VSWR threshold
getVswrReturnLoss Get return loss of Vswr
setSimVSWRValue Set simu Vswr value
antTestSetTraceFlag Set trace flag, Hex params
antTestSetAlarmFlag Set on/off vswr alarm flag,
bool params
antTestSetSimFlag Set Sim VSWR value flag, bool
params
/debug/antennatests>

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 49

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure -
VSWR
Step Action
Measurement
for Twin RRH 2 Type getVswrReturnLoss 1 (adding TX number: 1 or 2)
2x60w to receive the Return Loss value for VSWR measurement
(continued)
Expected Output

> /debug/antennatests
/debug/antennatests> getVswrReturnLoss 1 RL telnet
command for TX1
getVswrReturnLoss: ReturnLoss of TX1 is: 200 Return Loss
value of TX1 = 20 dB
(0.1dB)CLI_OK Telnet command was successful
#command:CLI_OK
#return value:void
#out param:double:20.068491 TX1 Return Loss value
/debug/antennatests>
/debug/antennatests> getVswrreturnloss 2 RL telnet
command for TX2
getVswrReturnLoss: ReturnLoss of TX2 is: 219 Return Loss
value of TX2 = 21.9 dB
(0.1dB)CLI_OK
#command:CLI_OK Telnet command was successful
#return value:void
#out param:double:21.986302 TX2 Return Loss value
/debug/antennatests>

4 Convert the Return Loss value into VSWR value according to conversion
formula.

Continued on next page

50 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure -
VSWR
Step Action
Measurement
for Twin RRH 5 Analyze the VSWR results for correctness and perform action if necessary:
2x60w
(continued)
If VSWR measurement Then the VSWR
value... Measurement ...
is between 1 and 1.5 is acceptable and validated
(1< good VSWR<1.5)

NOTE: The value 1 is a theoretical

value and acceptance criteria to
define the limit value
Is higher than 1.5 is not acceptable and there is an
(1.5 < Bad VSWR) issue

NOTE: Trouble shooting is required

to understand why the detected
VSWR value is not OK.

6 Retrieve the VSWR value and transfer to report sheet:

Multiple RRH VSWR measurement must be executed for every RRH connected to the d2U/d4U digital unit.
measurements
Continued on next page

June 30, 2014 Alcatel-Lucent Internal 51

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure - The following procedure allows to measure the VSWR value on ASB RRH 60w only.
VSWR
Measurement
for RRH 60w Step Action
1 Type cd .. to get out from the BCI application and to go back to the RFH1-1>
menu level, before BCI telnet command.

Expected Output on RRH 60w:

RFH1-1>bci

Entering character mode

Escape character is '^]'.
Session is opened.
RRH2T login: asb
Password for asb:

Login successful
>
> exit
End of session
Connection closed by foreign host
RFH1-1>

2 Type rctlAntTestTraceFlag=0x7fffffff
to display the Return loss value for VSWR measurement on RRH 60 only

Expected Output on RRH 60w:

RFH1-1> rctlAntTestTraceFlag=0x7fffffff RL telnet command

handleRS485ReadEvents: received return loss = 7.714844!
Return Loss value (this value is not acceptable and indicates a problem)

3 Convert the Return Loss value into VSWR value using the conversion formula

Continued on next page

52 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure -
VSWR
Step Action
Measurement
for RRH 60w 4 Analyze the VSWR results for correctness and perform action if necessary:
(continued)

If VSWR measurement is... Then the VSWR

Measurement ...
is between 1 and 1.5 is acceptable and validated
(1< good VSWR<1.5)

NOTE: The value 1 is a theoretical

value and acceptance criteria to
define the limit value
Is higher than 1.5 is not acceptable and there is an
(1.5 < Bad VSWR) issue

NOTE: Trouble shooting is required

to understand why the detected
VSWR value is not OK.

5 Retrieve the VSWR value and transfer to report sheet:

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 53

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Multiple RRH VSWR measurement must be executed for every RRH connected to the d2U/d4U digital unit.
measurements

Procedure - TX The following procedure is available measure the TX Power value on the ASB radio head.
Power
Measurement
Step Action
1 Type cd .. (to return to the previous menu, before antennatests level)
Type cd .. (to return to the previous menu, before debug level)
Type ls to see all menu available on this RE module

This will result inside the menu of TX Power measurement at the Antenna
Port.

Expected Output:
> ls
> cliproxy cliproxy
> cliserver cliserver commands
> context trace/error facilities
> debug Debug commands
> kernel Kernel space
> oam oam commands
> pltf Platform commands
> radioc radioc commands
>

Continued on next page

54 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure - TX
Power
Step Action
Measurement
(continued) 2 Type radioc
Type ls to display all menu items available on this RE module

Expected Output:
/radioc> ls
trxClgcEnable clgc enable
txControl Enable or disable tx
trxRfEnable Enable or disable tx
setRRHMod set RRH mode(FEU type)
trxEnable enable/disable TX/RX paths
getVswrThreshold Display current VSWR threshold
> aisg ttlna facilities
> attn Attn commands
> delay delay commands
> freqc freqc commands
> gainc gainc commands
> lna lna commands
> pa pa commands
> powermeasure power measure commands
/radioc>

3 Type gainc
Type ls to display Tx Power test at antenna port available on this RE module

Expected Output:
/radioc/gainc> ls
setDucGain set the DUC gain value
tpgcSetGainState TPGC Set Gain State (dBFS)
txPwrShow Display the Tx power at antenna port
tpgcSetBenignMode tpgcSetBenignMode
/radioc/gainc>

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 55

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure - TX
Power
Step Action
Measurement
(continued) 4 Type txPwrShow
to display the RF power output measurement (Tx Power Measure)

Expected Output:
/radioc/gainc> txPwrShow
TX1 power : 3801 1/100 dBm means 38.01 dBm
TX2 power : NO CARRIER Configured
txPwrShow: CLI_OK means the command working correctly

#command:CLI_OK
#out param:int:3801
#out param:int:-888888
#return value:void
/radioc/gainc>

Or with 2 TX power configured:

Expected Output:
/radioc/gainc> txPwrShow
TX1 power : 3730 1/100 dBm means 37.30 dBm
TX2 power : 3765 1/100 dBm means 37.65 dBm
txPwrShow: CLI_OK means the command working correctly
#command:CLI_OK
#out param:int:3730
#out param:int:3765
#return value:void
/radioc/gainc>

Continued on next page

56 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure - TX
Power
Step Action
Measurement
(continued) 5 Analyze the transmit output power (TX1 and TX2 Power) results for
correctness and perform action if necessary:

NOTE: The pcpichPower is the reference value of the TX Power and must be
available from action before.

If the TX Power is ... Then the Tx Power

measurement ...
higher than pcpichPower is acceptable and validated
(> pcpichPower)
NOTE: The RE TX power is working
properly.
close to TX Power Max is acceptable and validated
(Example of Max TX Power:
TX P Max : 47.7w for RRH 60w) NOTE: The RE TX power is working
properly.

NOTE: The RE is used in maximum

traffic conditions
lower than to pcpichPower is not acceptable and there is an
(< cppichPower) issue

NOTE: Trouble shooting is required

to understand why the detected
TXPower values are not close to the
expected value.

NOTE: The RE may not be

configured.

6 Retrieve the TX Power values and transfer into report sheet.

NOTE: The TX Power value shown here with the txPwrShow command must
be divided by 100 for the transfer into the reporting sheet (dBm).

Multiple RRH TX Power measurement must be executed for every RRH connected to the d2U/d4U digital
measurements unit.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 57

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure The following procedure allows to measure the RSSI values on the ASB radio head.
RSSI
Measurement
Step Action
1 Type: cd ..
Type: ls
Type: powermeasure

to be into the menu for RSSI measurement

Expected Output:
/radioc/gainc> cd ..
/radioc> ls
trxClgcEnable clgc enable
txControl Enable or disable tx
trxRfEnable Enable or disable tx
setRRHMod set RRH mode(FEU type)
trxEnable enable/disable TX/RX paths
getVswrThreshold Display current VSWR threshold
> aisg ttlna facilities
> attn Attn commands
> delay delay commands
> freqc freqc commands
> gainc gainc commands
> lna lna commands
> pa pa commands
> powermeasure power measure
commands
/radioc>

> radioc
/radioc> powermeasure
/radioc/powermeasure> ls
RSSI Read RX1 and RX2 filtered power value
rdTrxPower Read TRX digital Channel power (dBFS)
dpsShowData Dump all digital power
dpsShowSamples Dump all in/dfr digital power samples
dpsIsrControl Dump dps Enabled status
dpsAverage Average 10 samples for 100ms power report
/radioc/powermeasure>

Continued on next page

58 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure RSSI
Measurement
Step Action
(continued)
2 Type: RSSI 0 or RSSI 1 or RSSI 2 or RSSI 3
to display the RSSI measurement values.

NOTE: To read the RSSI value, type the number of carrier by carrier ( range
0..3)

Expected Output:
/radioc/powermeasure> RSSI 0
57 55
#out param:int:57 57 dBm on carrier 0 RX1
#out param:int:55 57 dBm on carrier 0 RX2
#command:CLI_OK Tthe command working correctly
#return value:void

/radioc/powermeasure> RSSI 1
60 59
#out param:int:60 60 dBm on carrier 1 RX1
#out param:int:59 59 dBm on carrier 1 RX2
#command:CLI_OK The command working correctly
#return value:void

/radioc/powermeasure> RSSI 2
#out param:string:The carrier 2 is not config can not
calculate the RSSI RX not configured on carrier 2
#command:CLI_NOK The command not working correctly

/radioc/powermeasure> RSSI 3
#out param:string:The carrier 3 is not config can not
calculate the RSSI RX not configured on carrier 3
#command:CLI_NOK The command not working correctly
/radioc/powermeasure>

These values are the power value of antenna port

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 59

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 4: RF Path Tests for ASB Products (2x60w or

60w-21C) - Optional, Continued

Procedure RSSI
Measurement
Step Action
(continued)
3 Analyze the Received Signal Strength Indicator (RSSI) results for correctness
and perform action if necessary:

If the RX Power (RSSI) Then the RX Power (RSSI)

values are... measurement result ...
higher than - 108 dBm is acceptable and validated
(> - 108 dBm)
NOTE: The RE working properly in
the receive band.
Is lower or equal to - 108 dBm is not acceptable and there is an
(< -108 dBm) issue

NOTE: Trouble shooting is required

to understand why the detected
RSSI/RTWP is not close to the
expected value.

4 Retrieve the RX Power (RSSI) and transfer to report sheet.

5 Type: exit | exit to logout the RE local terminal.

Expected Output:
> exit
End of session
Connection closed by foreign host
RFH1-1> exit
Connection closed by foreign host
eCCM-nodeb-nodeb>

Multiple RRH RSSI measurement must be executed for every RRH connected to the d2U/d4U digital unit.
measurements

60 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional

Description This tests allow to retrieve

VSWR measurement values
Transmit Power Level values
RSSI (Received Signal Strength Indicator) level values
from the RE of manufacturer MTI-GPCS and analyze the RF path (TX and RX).

NOTE: The RE types manufactured by MTI-GPCS

Table 5: MTI-GPCS products supported

RE Type RU Name PEC code

RRH MOD: RRH 60W-A 2100 Mhz 3JR21013AA
TRDU MOD: TRDU BAND01 AC 60W 3JR21012AB

Purpose of test The purpose of this test is to provide confidence that the Node B is radiating inside specified
and adjusted values and is properly receiving RX signals.

Preconditions Node B is completely integrated on the WMS.

Laptop available with a terminal emulator : here for example using Putty (or equivalent)
RRH IP address (according to the CPRI Link from the Telnet Preparation Procedures)
The reference pcpichPower value is checked with help of the previous dedicated procedure
and available into the report sheet
Only remote access to Remote Radio Head is needed to execute some RRH telnet
commands.

NOTE: Site access to Remote Radio Head is needed in case of troubleshooting only.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 61

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure The following procedure is available to log-in the GPCS RE.

Login to GPCS
RE
Step Action
1 Type: telnet [rrh_ip_address]
to establish the Telnet connection to the RE IP address (this is the local
Ethernet IP address assigned by the d2U/d4U) of the distributed Node B
CCM-U OS terminal.

Expected Output:
xCCM-nodeb-nodeb> telnet 192.168.129.1

Entering character mode

Escape character is '^]'.

Sash command shell (version 1.1.1)

/>

NOTE: Login and Password are not required

2 To obtain help the following CLIP commands available

Type: clip | help

Expected Output:
/> clip help

[2013.05.31 17:20:19.813] dr2

[2013.05.31 17:20:21.427] show_rl_cal
[2013.05.31 17:20:21.431] show_rx_status
[2013.05.31 17:20:21.475] show_tx_status
[2013.05.31 17:20:21.596] upd_meas_values

[2013.05.31 17:20:21.671] >>

Continued on next page

62 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Conversion of For the analysis of the VSWR value it is necessary to convert the Return Loss value. The
the Return Loss following table is available to support this activity.
Value to VSWR
Value for GPCS NOTE: The grey cells of the following table show non- acceptable VSWR values and mean
Products that there is a potential issue on the RF path connection. A troubleshooting operation must be
planned with the site coordinator.

Table 6: Return Loss to VSWR value Conversion

RL(dB) VSWR RL(dB) VSWR RL(dB) VSWR RL(dB) VSWR

46.1 1.01 25.7 1.11 18.0 1.29 8.0 2.32
40.1 1.02 24.9 1.12 17.0 1.33 7.0 2.61
36.6 1.03 24.3 1.13 16.0 1.38 6.0 3.01
34.1 1.04 23.7 1.14 15.0 1.43 5.0 3.57
32.3 1.05 23.1 1.15 14.0 1.50 4.0 4.42
30.7 1.06 22.6 1.16 13.0 1.58 3.0 5.85
29.4 1.07 21.7 1.18 12.0 1.67 2.0 8.72
28.3 1.08 20.8 1.20 11.0 1.78 1.0 17.4
27.3 1.09 20.0 1.22 10.0 1.92 0.5 34.8
26.4 1.10 19.0 1.25 9.0 2.10 0.0 Infinity

NOTE: Conversion between Return Loss and VSWR can be done as per following calculation
rules

If need to convert ... Then used...

Return Loss to VSWR value VSWR = [1 + 10( Return loss / 20)] / [1 10( Return loss / 20)]
VSWR to Return Loss value Return Loss (dB) = 20 log [(VSWR 1)/(VSWR+1)]

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 63

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure - The following procedure is available to support the VSWR on the GPCS radio head.
VSWR
Measurement
Step Action
1 Type: clip
Type: get_vswr_meas
to get the VSWR measurement shell on the RE local terminal

Expected Output:
/> clip
clip version 1.0.2
[1026@55] CLI RX thread started.
clip> get_vswr_meas
[2013.05.31 17:34:07.884] Raw VSWR meas. 1.293457 means
VSWR measurement is 1.29
[2013.05.31 17:34:07.890] Ave. VSWR meas. 1.751722
means VSWR average measurement is 1.75
[2013.05.31 17:34:07.897] 0
[2013.05.31 17:34:07.944] >>

2 Analyze the VSWR results for correctness and perform action if necessary:

If VSWR measurement Then the VSWR

value... Measurement ...
is between 1 and 1.5 is acceptable and validated
(1< good VSWR<1.5)

NOTE: The value 1 is a theoretical

value and acceptance criteria to
define the limit value
Is higher than 1.5 is not acceptable and there is an
(1.5 < Bad VSWR) issue

NOTE: Trouble shooting is required

to understand why the detected
VSWR value is not OK.

3 Retrieve the VSWR value and transfer it to report sheet.

Continued on next page

64 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure -
VSWR
Step Action
Measurement
(continued) 4 Type: clip
Type: get_return_loss
to display the return loss measurement value.

Expected Output:
/> clip
clip version 1.0.2
[1026@55] CLI RX thread started.
clip> get_return_loss
[2013.05.31 17:31:43.763] Return Loss: 11.260088 means
Return Loss Measurement is 11.26 dB
[2013.05.31 17:31:43.768] 0
[2013.05.31 17:31:43.773] >>

5 Analyze the Return Loss results for correctness and perform action if
necessary:

If the Return Loss Then the adaptation ...

measurement value ...
is the higher is the best
is the lower is the worst because the reflection is
increasing.

6 Convert the Return Loss value in VSWR value according to the Table 4
(Return Loss to VSWR value Conversion) before to analyze the result with
help of table (If/Then) from step 2.
7 Retrieve the Return Loss value and transfer it to report sheet.

Multiple RRH VSWR measurement must be executed for every RRH connected to the d2U/d4U digital unit.
measurements
Continued on next page

June 30, 2014 Alcatel-Lucent Internal 65

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure PA The following procedure is available to measure the TX Power on the GPCS radio head.
Gain
Measurement
Step Action
1 Type: clip
Type: get_pa_gain
to get the PA Power measurement value.

Expected Output:
/> clip
clip version 1.0.2
[1026@55] CLI RX thread started.
clip> get_pa_gain
[2013.05.31 17:30:37.029] PA Gain : 31184
[2013.05.31 17:30:37.057] 0
[2013.05.31 17:30:37.188] >>

Continued on next page

66 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure PA
Gain
Step Action
Measurement
(continued) 2 Type: clip
Type: show_pa_gain_lut
to display the PA Gain measurement value

Expected Output:
/> clip
clip version 1.0.2
[1026@55] CLI RX thread started.
clip> show_pa_gain_lut
[2013.05.31 17:43:21.610]
PA Gain LUT
Freq: 2115.0 2125.0 2135.0 2145.0 2155.0 2165.0
Freq: 0 1 2 3 4 5
[2013.05.31 17:43:21.619] 30254 PA Gain at Freq 0 is 30.25
dBm
[2013.05.31 17:43:21.625] 30523 PA Gain at Freq 1
[2013.05.31 17:43:21.631] 30657 PA Gain at Freq 2
[2013.05.31 17:43:21.635] 30590 PA Gain at Freq 3
[2013.05.31 17:43:21.640] 30949 PA Gain at Freq 4
[2013.05.31 17:43:21.645] 31267 PA Gain at Freq 5
[2013.05.31 17:43:21.649]
[2013.05.31 17:43:21.678] 0
[2013.05.31 17:43:21.707] >>

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 67

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure PA
Gain
Step Action
Measurement
(continued) 3 Type: clip
Type: get_carrier_power 0
to get the power value in dBM of carrier 0

Expected Output:
/> clip
clip version 1.0.2
[1026@55] CLI RX thread started.
clip> get_carrier_power 0 PA Gain measurement on carrier 0 is
33.8 dBm
[2013.05.31 17:39:45.739] Carrier 0 power: 33.800000 dBm
[2013.05.31 17:39:45.743] 0
[2013.05.31 17:39:45.748] >>

NOTE: Replace 0 by 1 or 2 or 3 for more than one carrier to measure carrier

output power.

4 Retrieve the PA Gain for each carrier and transfer it to the report sheet.

Multiple RRH PA Gain measurement must be executed for every RRH connected to the d2U/d4U digital
measurements unit.

Continued on next page

68 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure - TX The following procedure is available to measure the TX Power on the GPCS radio head.
Power
Measurement
Step Action
1 Type: clip
Type: show_tx_status
to get the TX measurement values.

/> clip
clip version 1.0.2
[1026@55] CLI RX thread started.
clip> show_tx_status

Expected Output: See block GPCS Transmitter Status (Telnet output -

example)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 69

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure - TX
Power
Step Action
Measurement
(continued) 2 Analyze the transmit output power (TX Power) results for correctness and
perform action if necessary:

NOTE: The pcpichPower is the reference value of the TX Power and must be
available from previous action.

If the TX Power is ... Then the Tx Power

measurement ...
higher than pcpichPower is acceptable and validated
(> pcpichPower)
NOTE: The RE TX power is working
properly.
close to TX Power Max is acceptable and validated
(Example of Max TX Power:
TX P Max : 47.7w for RRH 60w) NOTE: The RE TX power is working
properly.

NOTE: The RE is used in maximum

traffic conditions
lower than pcpichPower is not acceptable and there is an
(< cppichPower) issue

NOTE: Trouble shooting is required

to understand why the detected
TXPower values are not close to
the expected value.

NOTE: The RE may not be

configured.

3 Retrieve the TX Power measurement and transfer to report sheet.

Multiple RRH TX Power measurement must be executed for every RRH connected to the d2U/d4U digital
measurements unit.

Continued on next page

70 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure - The following procedure is available to measure the RSSI on the GPCS radio head.
RSSI
Measurement
Step Action
1 Type: clip
Type: show_rx_status
to get the RX (RSSI) measurement shell.

/> clip
clip version 1.0.2
[1026@55] CLI RX thread started.
clip> show_rx_status

Expected Output: See block GPCS Receiver Status (Telnet output -

example)
2 Analyze the Received Signal Strength Indicator (RSSI) results for correctness
and perform action if necessary:

If the RX Power (RSSI) Then the RX Power (RSSI)

values are... measurement result ...
higher than - 108 dBm is acceptable and validated
(> - 108 dBm)
NOTE: The RE working properly in
the receive band.
Is lower or equal to - 108 dBm is not acceptable and there is an
(< -108 dBm) issue

NOTE: Trouble shooting is required

to understand why the detected
RSSI/RTWP is not close to the
expected value.

3 Retrieve the RX Power (RSSI) measurement values and transfer into the
report sheet.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 71

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

Procedure - RSSI
Measurement
Step Action
(continued)
4 Type: exit | exit to logout the RE local terminal.

Expected Output:
> exit
End of session
Connection closed by foreign host
RFH1-1> exit
Connection closed by foreign host
eCCM-nodeb-nodeb>

Multiple RRH RX Power (RSSI) measurement must be executed for every RRH connected to the d2U/d4U
measurements digital unit.

Continued on next page

72 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
RF Path Validation Testing IEH 521, Section 411

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

GPCS Displayed as a result of the Telnet command: clip> show_tx_status

Transmitter **************************************************
Status (Telnet [2013.05.31 17:35:28.427] * Transmitter Status
output - [2013.05.31 17:35:28.452] **************************************************
example) [2013.05.31 17:35:28.480] State = Operational
[2013.05.31 17:35:28.489] Carrier 0 Unlocked Carrier 0 Unlocked and operational
[2013.05.31 17:35:28.495] Carrier 1 Unconfigured Carrier 1 is not operational
[2013.05.31 17:35:28.503] Carrier 2 Unconfigured
[2013.05.31 17:35:28.509] Carrier 3 Unconfigured
[2013.05.31 17:35:28.514] Carrier 4 Unconfigured
[2013.05.31 17:35:28.520] Carrier 5 Unconfigured
[2013.05.31 17:35:28.525] Carrier 6 Unconfigured
[2013.05.31 17:35:28.531] Carrier 7 Unconfigured
[2013.05.31 17:35:28.553] Tx state : operating TX State is operational
[2013.05.31 17:35:28.557] PLLs are locked
[2013.05.31 17:35:28.683] PA Driver : 24.00 V
[2013.05.31 17:35:28.689] PA Final : 32.50 V
[2013.05.31 17:35:28.695] PA Temperature : 41.10 C
[2013.05.31 17:35:28.703] PA Power (based on input): 2436 mW (33.87 dBm)
[2013.05.31 17:35:28.834] PA Power (instantaneous): 33.89 dBm PA Power measurement is
33.89 dBm
[2013.05.31 17:35:28.857] VSWR measurement : 1.75 VSWR Measurement is 1.75
[2013.05.31 17:35:28.867] Downlink Delay : 15.771 us
[2013.05.31 17:35:28.895] Tx DAC is ready
[2013.05.31 17:35:28.900] Tx LO frequency : 2159001600.0 Hz
[2013.05.31 17:35:28.916] CP Channel 0
[2013.05.31 17:35:28.925] Power : 33.70 dBm TX Power measurement is 33.7 dBm
[2013.05.31 17:35:28.938] CTPO : -5.07 dB
[2013.05.31 17:35:28.958] CP Channel 1
[2013.05.31 17:35:28.963] Power : -299.90 dBm TX Power on channel 1 is not operational
[2013.05.31 17:35:29.008] CTPO : -1.00 dB
[2013.05.31 17:35:29.013] CP Channel 2
[2013.05.31 17:35:29.019] Power : -299.90 dBm TX Power on channel 2 is not operational
[2013.05.31 17:35:29.033] CTPO : -1.00 dB
[2013.05.31 17:35:29.038] CP Channel 3
[2013.05.31 17:35:29.060] Power : -299.90 dBm TX Power on channel 3 is not operational
[2013.05.31 17:35:29.066] CTPO : -1.00 dB
[2013.05.31 17:35:29.071] Clipper 1 : 5130, Clipper 2 : 6311
[2013.05.31 17:35:29.109] DPD level : 811, FB level : 2174
[2013.05.31 17:35:29.133] Pre DPD Gain : 3.913513, Post DPD Gain : 1.933594
[2013.05.31 17:35:29.162] UC Gain : 0.0805
[2013.05.31 17:35:29.166] CP level : 83765
[2013.05.31 17:35:29.171] WCDMA carrier(s) configured
[2013.05.31 17:35:29.175] AxC assignments
[2013.05.31 17:35:29.205] 0 0024
[2013.05.31 17:35:29.213] 1 0000
[2013.05.31 17:35:29.222] 2 0000
plus additional outputs of no relevance to TX power test

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 73

Proprietary Use pursuant to Company instruction
IEH 521, Section 411 RF Path Validation Testing

Proc. 5: RF Path Tests for MTI - GPCS Products

(60w-21) - Optional, Continued

GPCS Receiver Displayed as a result of the Telnet command: clip> show_rx_status

Status (Telnet **************************************************
output - [2013.05.31 17:36:36.568] * Receiver Status
example) [2013.05.31 17:36:36.636] **************************************************
[2013.05.31 17:36:36.647] Rx state : ready for operation
[2013.05.31 17:36:36.654] UTRAN sharing is not enabled
[2013.05.31 17:36:36.661] PLLs are locked
[2013.05.31 17:36:36.667] Main rx status
[2013.05.31 17:36:36.672] State: operating
[2013.05.31 17:36:36.819] LO: 1969920000.0 Hz
[2013.05.31 17:36:36.840] WCDMA NB AGC
[2013.05.31 17:36:36.977] M[0] Pin -107.00, AGC 51
[2013.05.31 17:36:36.983] M[1] Pin -94.19, AGC 179
[2013.05.31 17:36:36.990] M[2] Pin -94.19, AGC 179
[2013.05.31 17:36:37.038] M[3] Pin 0.00, AGC 621
[2013.05.31 17:36:37.044] Input overload count 0
[2013.05.31 17:36:37.049] External TMA gain 0.0dB
[2013.05.31 17:36:37.055] Div rx status
[2013.05.31 17:36:37.062] State: operating RX Power Diversity Status
[2013.05.31 17:36:37.069] LO: 1969920000.0 Hz Frequency used is 1970 Mhz
[2013.05.31 17:36:37.074] WCDMA NB AGC
[2013.05.31 17:36:37.086] D[0] Pin -106.67, AGC 54 RSSI measurement on Diversity 0 is -
106.67 dBm
[2013.05.31 17:36:37.092] D[1] Pin -94.19, AGC 179 RSSI measurement on Diversity 1 is -
94.19 dBm
[2013.05.31 17:36:37.098] D[2] Pin -94.19, AGC 179 RSSI measurement on Diversity 2 is -
94.19 dBm

[2013.05.31 17:36:37.141] D[3] Pin 0.00, AGC 621 RSSI on Diversity 3 is not operational
and not measured
[2013.05.31 17:36:37.147] Input overload count 0
[2013.05.31 17:36:37.152] External TMA gain 0.0dB
[2013.05.31 17:36:37.158] WCDMA Uplink Delay : 8.105 us
[2013.05.31 17:36:37.166] LTE Uplink Delay : 0.000 us
[2013.05.31 17:36:37.173] WCDMA carrier configured
AxC assignments
[2013.05.31 17:36:37.182] 0 0038
[2013.05.31 17:36:37.190] 1 004C
[2013.05.31 17:36:37.197] 2 0000
[2013.05.31 17:36:37.203] 3 0000
[2013.05.31 17:36:37.248] 4 0000
[2013.05.31 17:36:37.255] 5 0000
[2013.05.31 17:36:37.265] 6 CBAD
[2013.05.31 17:36:37.273] 7 CBAD
[2013.05.31 17:36:37.277] **************************************************
[2013.05.31 17:36:37.283] 0
[2013.05.31 17:36:37.288] >>

74 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 412

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Ethernet OAM in the Node B Testing Procedure

Table of Contents

General ............................................................................................................ 2
Section Description .......................................................................................... 2
Previous Release Date ....................................................................................... 2
Release Notes ................................................................................................. 2
References ........................................................................................................ 3
General ........................................................................................................ 3
Documentation access ...................................................................................... 3
Applicable IEH 521 sections ................................................................................ 3
Applicable Methods documents in LR13.3 ............................................................... 3
Tools Requirements ............................................................................................. 4
General ........................................................................................................ 4
Hardware Tools ............................................................................................... 4
Software Tools ................................................................................................ 4
Remote test tool ............................................................................................. 4
Ethernet OAM in the Node B ................................................................................... 5
Description .................................................................................................... 5
Preconditions ................................................................................................. 5
Determination of Ethernet OAM Link location on the CCM Board and checking procedure ..... 6
Ethernet OAM Link on GE MDA Procedure - SFP ........................................................ 8
Ethernet OAM Link on GE MDA Procedure RJ45 ..................................................... 12
Ethernet OAM Link on CCM Mother Board Procedure RJ45........................................ 16
List of Figures

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Tests ................................................... 3
Table 2: Applicable Methods Documents LR13.3 for IEH521 ....................................................... 3
Table 3: Hardware Tools ................................................................................................. 4
Table 4: Software Tools .................................................................................................. 4

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

General

Section This section provides detailed information about the individual procedures to validate the
Description function of the Ethernet OAM interface in the Node B
Preconditions
Inputs
Outputs
Additional details

Previous Release New creation

Date

Release Notes New creation: June 2014 under utilization of existing Installation Methods and user guides
documents for LR13.3W

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Ethernet OAM in the Node B Testing Procedure IEH 521, Section 412

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B tests.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are available to support the WCDMA Node B tests.
521 sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B Tests

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
399 Node B Commissioning Test Records
401 Integration Planning

Applicable The following methods documents are required to perform the Node B commissioning in
Methods LR13.3
documents in
LR13.3
Table 2: Applicable Methods Documents LR13.3 for IEH521

Doc Number Doc Title URL

9YZ-05870- Alcatel-Lucent 9100 and 93xx Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault Management User lucent.com/pdfdocs14/pr
Manual: TIL istore215/541291.pdf
9YZ-05870- Alcatel-Lucent 9353 WMS user Guide http://cic.us.alcatel-
0014-PCZZA lucent.com/pdfdocs14/pr
istore215/555634.pdf
9YZ-05870- Alcatel-Lucent 9353 WMS Node B Alarms http://cic.us.alcatel-
0060-UFZZA Reference Guide lucent.com/pdfdocs14/pr
istore215/536534.pdf

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

Tools Requirements

General This section describes the hardware and software tools required to perform the testing
Remote testing (recommended) use of TIL GUI through the WMS
At site testing (for trouble shooting) use of TIL tool at site

Hardware Tools The hardware tools listed in the following table are required to perform the test at site

Table 3: Hardware Tools

Hardware Tool Quantity Description

Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

Software Tools The software tool listed in the following table are required to perform the test at site

Table 4: Software Tools

Software Tool Version Allowed

OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with WIN
7)

Remote test tool For remote testing it is required to have WMS with TIL GUI operational

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Ethernet OAM in the Node B Testing Procedure IEH 521, Section 412

Ethernet OAM in the Node B

Description This procedure describes how to check the Ethernet OAM link status in the Node B.

Preconditions The Node B is already fully Integrated

The Ethernet OAM in Node B feature must be activated: concerning both parameter EFM
(Ethernet First Mille) and CFM (Connectivity Fault Management)
The minimum release software must be LR13.3.
The WMS TIL GUI is operational (remote) or the laptop setting and TIL connections are
already done and available (at site).
The Ethernet OAM link is connected to one of the following CCM ports :
Port #2 RJ45 from the CCM MB (Mother Board)
Port #3 SFP1 from the GE MDA
Port #4 SFP2 from the GE MDA
Port #5 RJ45 from the GE MDA

NOTE: The testing procedure is dependent on the interface used for Ethernet OAM at the
Node B

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

Ethernet OAM in the Node B, Continued

Determination This procedure describes how identify the OAM Ethernet link location and link status and
of Ethernet identify which procedure to use for testing
OAM Link
location on the
CCM Board and Step Action
checking
procedure 1 Display in TIL GUI the CCM board view
GE MDA or
E1/T1 MDA

Ethernet OAM in the NodeB TIL GUI

Continued on next page

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Ethernet OAM in the Node B Testing Procedure IEH 521, Section 412

Ethernet OAM in the Node B, Continued

Determination
of Ethernet OAM
Step Action
Link location on
the CCM Board 2 Use visible status to decide which testing procedure to use to check the
and checking Ethernet OAM interface
procedure
(continued)
If the visual check identifies Then
that
the MB RJ45 LED is Green Port #2 RJ45 from the CCM
Mother Board is used
Execute Ethernet OAM Link on
Mother Board Procedure - RJ45
the SFP1 LED of the GE MDA is Port #3 SFP1 from the GE MDA is
Green used
Execute Ethernet OAM Link on
GE MDA Procedure - SFP
the SFP2 LED of the GE MDA is Port #4 SFP1 from the GE MDA is
Green used
Execute Ethernet OAM Link on
GE MDA Procedure - SFP
the RJ45 LED of the GE MDA is Port #5 SFP1 from the GE MDA is
Green used
Execute Ethernet OAM Link on
GE MDA Procedure RJ45

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

Ethernet OAM in the Node B, Continued

Ethernet OAM Perform the following procedure steps to check the Ethernet OAM connected on the GE MDA
Link on GE MDA in case SFP interface is used
Procedure - SFP

Step Action
1 Check visually the SFP contextual menu associated to SFP1 or SFP2 from GE
MDA appears

OR

Continued on next page

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Ethernet OAM in the Node B Testing Procedure IEH 521, Section 412

Ethernet OAM in the Node B, Continued

Ethernet OAM
Link on GE MDA
Step Action
Procedure - SFP
(continued) 2 Select Ethport Configuration
The CCM Configuration of SFP window appears:

OR

3 Check the configuration parameters associated to the SFP Ethernet port.

The indication of the Ethernet OAM link is in operational mode :

When you check SFP Then indication is...

Port parameter...
State SFP cage 1 or 2 or RJ45
State: Connected
EFM EFM Mode: Active
Characteristics HW Type : SFP Optical
Link Speed: 1000
SFP rate mode: Full
Loopback mode: Normal

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

Ethernet OAM in the Node B, Continued

Ethernet OAM
Link on GE MDA
Step Action
Procedure - SFP
(continued) 4 Select Ethport Alarms from the SFP 1 or SFP 2 LED

Continued on next page

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Ethernet OAM in the Node B Testing Procedure IEH 521, Section 412

Ethernet OAM in the Node B, Continued

Ethernet OAM
Link on GE MDA
Step Action
Procedure - SFP
(continued) 5 Check that alarms indications from SFP MDA are all in green status.

Result: MDA SFP Alarms figures If EFM is activated:

Result: MDA SFP Alarms figures If EFM is not activated:

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

Ethernet OAM in the Node B, Continued

Ethernet OAM Perform the following procedure steps to check the Ethernet OAM connected on the GE MDA
Link on GE MDA in case RJ45 interface is used
Procedure
RJ45
Step Action
1 Check visually the RJ45 contextual menu associated to RJ45 from GE MDA
appears

Continued on next page

12 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Ethernet OAM in the Node B Testing Procedure IEH 521, Section 412

Ethernet OAM in the Node B, Continued

Ethernet OAM
Link on GE MDA
Step Action
Procedure
RJ45 (continued) 2 Select Ethport Configuration
The CCM Configuration of RJ45 window appears:

3 Check the configuration parameters associated to the RJ45 GE-MDA port.

The indication of the Ethernet OAM link is in operational mode :

When you check RJ45 Port Then indication must be...

parameter...
State RJ45 GE-MDA
State: Connected
Characteristics HW Type : ETH-RJ45
Link Speed: 100 Mbps
Loopback mode: Normal

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

Ethernet OAM in the Node B, Continued

Ethernet OAM
Link on GE MDA
Step Action
Procedure
RJ45 (continued) 4 Select Ethport Alarms from the RJ45 LED

Continued on next page

14 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Ethernet OAM in the Node B Testing Procedure IEH 521, Section 412

Ethernet OAM in the Node B, Continued

Ethernet OAM
Link on GE MDA
Step Action
Procedure
RJ45 (continued) 5 Check that alarms indications from RJ45 MDA are all in green status.

Result: MDA SFP Alarms figures If EFM is activated (on left) or If EFM is not
activated (on right):

NOTE: Contact the support team to troubleshoot the issue if necessary.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

Ethernet OAM in the Node B, Continued

Ethernet OAM This procedure describes how to check the Ethernet OAM connected on the CCM Mother
Link on CCM Board (RJ45 port #2).
Mother Board
Procedure
RJ45 Step Action
1 Right-click on the RJ45 Ethernet port connected on the Mother Board from the
TIL GUI: LED in green

Continued on next page

16 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Ethernet OAM in the Node B Testing Procedure IEH 521, Section 412

Ethernet OAM in the Node B, Continued

Ethernet OAM
Link on CCM
Step Action
Mother Board
Procedure 2 Select NIP Configuration
RJ45 (continued) The CCM Configuration of RJ45 Mother Board window appears:

3 Check the configuration parameters associated to the MB RJ45 port.

The indication of the Ethernet OAM link is in operational mode :

When you check Then indication must be...

parameter...
State MB RJ45
State: Connected
Characteristics HW Type : Copper
Link Speed: 100

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 412 Ethernet OAM in the Node B Testing Procedure

Ethernet OAM in the Node B, Continued

Ethernet OAM
Link on CCM
Step Action
Mother Board
Procedure 4 Select NIP Alarms
RJ45 (continued) The alarm of RJ45 Mother Board window appears:

5 Check that alarm indication is in green status.

NOTE: Contact the support team to troubleshoot the issue if necessary.

18 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 413

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Node B Daisy Chain Remote Checking Procedure Telnet Commands

Table of Contents

General ............................................................................................................ 3
Section Description .......................................................................................... 3
Previous Release Date ....................................................................................... 3
Release Notes ................................................................................................. 3
References ........................................................................................................ 4
General ........................................................................................................ 4
Documentation access ...................................................................................... 4
Applicable IEH 521 sections for WCDMA Node B commissioning ..................................... 4
Applicable IEH 521 sections for WCDMA Node B Integration ......................................... 4
Applicable IEH 521 sections for WCDMA Node B Daisy Chain Activation Procedure .............. 5
Applicable Methods documents ............................................................................ 5
Tools Requirements ............................................................................................. 6
General ........................................................................................................ 6
Hardware Tool ................................................................................................ 6
Software Tool ................................................................................................. 6
Node B Daisy Chain Remote Test Overview ................................................................. 7
Description .................................................................................................... 7
Node B Daisy Chain Remote Checking Flow Diagram .................................................. 7
Node B Daisy Chain Remote test process ................................................................ 8
Proc. 1: Node B in Daisy Chain Telnet Log onto WMS Server Procedure ........................... 11
Description .................................................................................................. 11
Preconditions ............................................................................................... 11
Log-onto the WMS server with Telnet Commands Procedure ...................................... 12
Proc. 2: IP Ping of All Node B in Daisy Chain - Testing Procedure .................................... 15
Description .................................................................................................. 15
Preconditions ............................................................................................... 15
IP Ping Testing of All Node B in Daisy Chain Procedure ............................................. 16
Proc. 3: Node B Daisy Chaining Telnet Log onto Node B ............................................. 18
Description .................................................................................................. 18
Preconditions ............................................................................................... 18
Log-onto the Node B Procedure Telnet Commands ................................................. 19
Proc. 4: Node B (A) Daisy Chaining Configuration Checking Procedure (Optional) .............. 23

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Description .................................................................................................. 23
Preconditions ............................................................................................... 23
Node B (A) Daisy Chaining Configuration Checking Procedure ..................................... 23
Proc. 5: Node B (A) VLAN Id Checking Procedure (Optional) ........................................ 26
Description .................................................................................................. 26
Preconditions ............................................................................................... 26
Node B (A) VLAN Id Checking Procedure ............................................................... 27
Proc. 6: Node B (A) Ethernet Port Checking Procedure (Optional) ................................. 28
Description .................................................................................................. 28
Preconditions ............................................................................................... 28
Node B (A) Ethernet Port Checking Procedure ........................................................ 29
Proc. 7: Node B (A) Ethernet Port Counters Checking Procedure (Optional) ..................... 32
Description .................................................................................................. 32
Preconditions ............................................................................................... 32
Node B (A) Ethernet Port Counters Checking Procedure ............................................ 33
Proc. 8: Node B (B) Daisy Chained Configuration Checking Procedure (Optional) ............... 34
Description .................................................................................................. 34
Preconditions ............................................................................................... 34
Node B (B) Daisy Chained Configuration Checking Procedure ...................................... 34
Proc. 9: Node B (B) VLAN Id Checking Procedure (Optional) ........................................ 36
Description .................................................................................................. 36
Preconditions ............................................................................................... 36
Node B (B) VLAN Id Checking Procedure ............................................................... 37
Proc. 10: Node B (B) Ethernet Port Checking Procedure (Optional) ................................ 38
Description .................................................................................................. 38
Preconditions ............................................................................................... 38
Node B (B) Ethernet Port Checking Procedure ........................................................ 38
Proc. 11: Node B (B) Ethernet Port Counters Checking Procedure (Optional) .................... 42
Description .................................................................................................. 42
Preconditions ............................................................................................... 42
Node B (B) Ethernet Port Counters Checking Procedure ............................................ 43

List of Figures

Figure 1: Node B Daisy Chain Remote Checking flow of activities .............................................. 7

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Commissioning Tests ............................... 4
Table 2: Applicable IEH 521 Sections for WCDMA Node B Integration Tests .................................... 4
Table 3: Applicable IEH 521 Sections for WCDMA Node B Daisy Chain Activation Procedure ................ 5
Table 4: Applicable Methods Documents for IEH521 ................................................................ 5
Table 5: Hardware Tools ................................................................................................. 6
Table 6: Software Tools .................................................................................................. 6
Table 7: List of Node B Daisy Chain Remote Checking Procedures ............................................... 8

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

General

Section This section provides detailed information about methods to do remote checking of Node B
Description under daisy chaining
Preconditions
Inputs
Outputs
Additional details
Link to commissioning methods document where the procedure is contained

Previous Release New creation

Date

Release Notes New creation: June 2014 under utilization of existing Installation Methods and user guides
documents from LR13.1.

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA NodeB tests.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required for WCDMA Node B commissioning tests.
521 sections for
WCDMA Node B
commissioning Table 1: Applicable IEH 521 Sections for WCDMA Node B
Commissioning Tests

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
399 Node B Commissioning Test Records

Applicable IEH The sections listed in Table 2 below are required for WCDMA Node B Integration tests.
521 sections for
WCDMA Node B
Integration Table 2: Applicable IEH 521 Sections for WCDMA Node B Integration
Tests
Section Description
401 Node B Integration Planning
402 Node B Integration Procedure
499 Node B Integration Test Records

Continued on next page

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

References, Continued

Applicable IEH The sections listed in Table 3 below are required for WCDMA Node B Integration tests.
521 sections for
WCDMA Node B
Daisy Chain Table 3: Applicable IEH 521 Sections for WCDMA Node B Daisy Chain
Activation Activation Procedure
Procedure
Section Description
706 Node B Daisy Chaining through the Node B - Activation Procedurea

Applicable The following methods documents are required to perform the Node B commissioning and
Methods Integration Test
documents

Table 4: Applicable Methods Documents for IEH521

Doc Number Doc Title URL

9YZ-04088- Alcatel-Lucent 9100 and 93xx Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault Management User lucent.com/pdfdocs14/pr
Manual: TIL (LR13.1) istore215/529074.pdf
9YZ-05870- Alcatel-Lucent 9100 and 93xx Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault Management User lucent.com/pdfdocs14/pr
Manual: TIL (LR13.3) istore215/541291.pdf
9YZ-04088- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.1) lucent.com/pdfdocs14/pr
istore215/562268.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.3) lucent.com/pdfdocs14/pr
istore215/586415.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0060-UFZZA System - Node B Alarms Reference Guide lucent.com/pdfdocs14/pr
(LR13.3) istore215/536534.pdf

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Tools Requirements

General This section describes the hardware and software tools required to perform the telnet
commands procedures.

Hardware Tool The Table below lists all hardware tools which are required to perform the telnet commands
procedures.

Table 5: Hardware Tools

Hardware Tool Quantity Description
Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For Telnet GUI visualization and
interface RJ45 modification
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

Software Tool The Table below lists all software tools which are required to perform the telnet commands
procedures.

Table 6: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Terminal Emulator e.g. Putty (or equivalent)

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Node B Daisy Chain Remote Test Overview

Description The Node B Daisy Chain Remote test provides an overview and guidance about
which tests to perform
in which sequence that tests need to be performed

Node B Daisy The following flow outlines the validation tasks to be performed during Node B Daisy Chain
Chain Remote Remote Test:
Checking Flow NOTE: The Node B Daisy Chaining through the Node B flow diagram explains at what position
Diagram which procedure is being used

Figure 1: Node B Daisy Chain Remote Checking flow of activities

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Node B Daisy Chain Remote Test Overview, Continued

Node B Daisy The Table below lists all operational steps to test the Node B after the Node B Daisy Chain
Chain Remote through the Node B activation is done.
test process

Table 7: List of Node B Daisy Chain Remote Checking Procedures

Operation Opt/ Procedures Remarks

Mand.
Log onto the WMS M Proc. 1 : Node B in Laptop available
SSH server to allow Daisy Chain with a terminal
usage of Telnet Telnet Log onto emulator connected
commands. WMS Server to WMS
Procedure WMS IP address
and login and
password are
available
Perform an IP Ping M Proc. 2 : IP Ping of Node B Daisy Chain
test with Telnet of All Node B in Daisy Activated
all Daisy Chained Chain - Testing The Proc 1
and daisy chaining Procedure successfully
Node B. performed
Laptop available
with a terminal
emulator connected
to WMS
Log onto the Node M Proc 3 : Node B Laptop available
B to allow usage of Daisy Chaining with a terminal
Telnet commands. Telnet Log onto emulator connected
Node B to node B
Node B IP address
and login and
password are
available
Check the Node B O Proc. 4 : Node B (A) Node B Daisy Chain
(A) in Daisy Daisy Chaining Activated
Chaining Configuration The Proc 3
configuration Checking Procedure successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (A)

Continued on next page

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Node B Daisy Chain Remote Test Overview, Continued

Node B Daisy
Chain Remote
Operation Opt/ Procedures Remarks
test process
Mand.
(continued)
Check the VLAN Id O Proc. 5 : Node B (A) Node B Daisy Chain
of Node B (A) VLAN Id Checking Activated
Procedure The Proc 3
successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (A)
Check the Ethernet O Proc. 6 : Node B (A) Node B Daisy Chain
Port of Node B (A) Ethernet Port Activated
Checking Procedure The Proc 3
successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (A)
Check the Ethernet O Proc. 7 : Node B (A) Node B Daisy Chain
Port Counters of Ethernet Port Activated
Node B (A) Counters Checking The Proc 3
Procedure successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (A)
Check the Node B O Proc. 8 : Node B (B) Node B Daisy Chain
(B) in Daisy Daisy Chained Activated
Chained Configuration The Proc 3
configuration Checking Procedure successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (B)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Node B Daisy Chain Remote Test Overview, Continued

Node B Daisy
Chain Remote
Operation Opt/ Procedures Remarks
test process
Mand.
(continued)
Check the VLAN Id O Proc. 9 : Node B (B) Node B Daisy Chain
of Node B (B) VLAN Id Checking Activated
Procedure The Proc 3
successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (B)
Check the Ethernet O Proc. 10 : Node B Node B Daisy Chain
Port of Node B (B) (B) Ethernet Port Activated
Checking Procedure The Proc 3
successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (B)
Check the Ethernet O Proc. 11 : Node B Node B Daisy Chain
Port Counters of (B) Ethernet Port Activated
Node B (B) Counters Checking The Proc 3
Procedure successfully
performed
Laptop available
with a terminal
emulator connected
to Node B (B)

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 1: Node B in Daisy Chain Telnet Log onto

WMS Server Procedure

Description This procedure describes the Telnet commands that can be used remotely to log onto WMS
server of the Node B Daisy Chain under test.
Node B tests through remote Telnet commands have to be understood as extension of the
WMS based Node B tests and provide additional information (e.g. to support trouble shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
Laptop connected to the internet network with RJ45
WMS IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 1: Node B in Daisy Chain Telnet Log onto

WMS Server Procedure, Continued

Log-onto the This procedure describes how to log-onto the WMS SSH server to allow usage of Telnet
WMS server with commands.
Telnet
Commands
Procedure Step Action
1 Open the terminal emulator, for example here: Putty
Select Logging with the following parameters to save the session to provide
a full report sheet.
Select All session output
Select Browse to specify the name of the session to record (and set its
location)

Continued on next page

12 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 1: Node B in Daisy Chain Telnet Log onto

WMS Server Procedure, Continued

Log-onto the
WMS server with
Step Action
Telnet
Commands 2 Connect to the WMS SSH server:
Procedure Type the WMS IP address into the Host Name
(continued)
Select the connection type: SSH
Click Open

NOTE: WMS SSH server requests Login and Password

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 1: Node B in Daisy Chain Telnet Log onto

WMS Server Procedure, Continued

Log-onto the
WMS server with
Step Action
Telnet
Commands 3 Log-in to WMS SSH server:
Procedure Enter the dedicated Login:
(continued)
Enter dedicated Password:

Expected Output:
login as: oamops

This system is a restricted access system.

All activity on this system is subject to monitoring.
If information collected reveals possible criminal
activity or activity that exceeds privileges, evidence of
such activity may be provided to the relevant authorities
for further action. By continuing past this point, you
expressly consent to this monitoring.

Using keyboard-interactive authentication.

Password: oam_oamops
Last login: Wed May 21 13:44:59 2014 from 172.27.155.159
Oracle Corporation SunOS 5.10 Generic Patch January
2005
You have new mail.
wms5220:/home/oamops <103> (oamops) %
$

14 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 2: IP Ping of All Node B in Daisy Chain -

Testing Procedure

Description This procedure describes the Telnet commands that can be used remotely to perform an IP
Ping test of all Node B (A) Daisy Chaining and Node B (B) Daisy Chained.
The Ping test of the chained Node B (Node B (B)) is the fastest proof that the daisy chaining
configuration through Node B (A) is working.

NOTE: This Ping test can be used for Node B (B) under test in case of
2G Node B
3G Node B
4G Node B

Note: Node B tests through remote Telnet commands have to be understood as extension of
the WMS based Node B tests and provide additional information (e.g. to support trouble
shooting).

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B in Daisy Chaining Telnet Log onto WMS Server Procedure is
successfully performed
Laptop is connected to the internet network with RJ45
Node B (A) IP address is available
Node B (B) IP address is available

NOTE: Node B tests through Telnet commands are remote tests and do not require site
access to the equipment under test.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 2: IP Ping of All Node B in Daisy Chain -

Testing Procedure, Continued

IP Ping Testing This procedure describes how to perform an IP Ping test with Telnet of all Daisy Chained and
of All Node B in Daisy Chaining Node B.
Daisy Chain
Procedure
NOTE: Procedure Log-on to the WMS server with Telnet Commands is already
performed.

Step Action
1 Type: ping [IP address of the Node B (B) Daisy Chained] | <enter>

NOTE: This IP Ping test the physical link between the OAM up to the Node B
(B) daisy chained and passing through the NodeB (A)

Expected Output:
wms5220:/home/oamops <103> (oamops) % ping 172.26.127.2x3
172.26.127.2x3 is alive Check
wms5220:/home/oamops <104> (oamops) %

2 Check the Ping test result

If IP Ping tests result is... Then ...

[IP address] of Node B (B) is alive The physical link between the OAM
(Example: up to the Node B (B) daisy chained
and passing through the NodeB (A)
172.26.127.2x3 is alive)
is validated
No answer from [IP address] of The physical link between the
Node B (B) OAM up to the Node B (B) is not
(Example: validated or not configured.
no answer from To troubleshoot physical link
172.26.127.2x3) between the OAM and the Node
B, contact the coordinator and the
support team and if necessary
perform the following procedures
for initial check.

Continued on next page

16 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 2: IP Ping of All Node B in Daisy Chain -

Testing Procedure, Continued

IP Ping Testing
of All Node B in
Step Action
Daisy Chain
Procedure 3 Type: ping [IP address of the Node B (A) Daisy Chaining] | <enter>
(continued)
NOTE: This IP Ping test the physical link between the OAM up to the Node B
(A) daisy chaining

Expected Output:
wms5220:/home/oamops <103> (oamops) % ping 172.26.127.2x6
172.26.127.2x6 is alive Check
wms5220:/home/oamops <104> (oamops) %

4 Check the Ping test result

If IP Ping tests result is... Then ...

[IP address] of Node B (B) is alive The physical link between the OAM
(Example: up to the Node B (A) daisy chaining
is validated
172.26.127.2x6 is alive)
No answer from [IP address] of The physical link between the
Node B (B) OAM up to the Node B (A) is not
(Example: validated or not configured.
no answer from To troubleshoot physical link
172.26.127.2x6) between the OAM and the Node
B, contact the coordinator and the
support team and if necessary
perform the following procedures
for initial check..

June 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 3: Node B Daisy Chaining Telnet Log onto

Node B

Description This procedure describes how to setup for the use of Telnet commands for the Node B Daisy
Chain under test.
NOTE: Node B tests through remote Telnet commands have to be understood as extension of
the WMS based Node B tests and provide additional information (e.g. to support trouble
shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop is available with a terminal emulator : e.g. Putty (or equivalent)
Laptop is connected to the internet network with RJ45
Node B IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Continued on next page

18 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 3: Node B Daisy Chaining Telnet Log onto

Node B, Continued

Log-onto the This procedure describes how to log-on to the Node B to allow usage of Telnet commands.
Node B
Procedure
Telnet Step Action
Commands
1 Open the terminal emulator, for example here: Putty
Select Logging with the following parameters to save the session to provide
a full report sheet.
Select All session output
Select Browse to specify the name of the session to record (and set its
location)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 3: Node B Daisy Chaining Telnet Log onto

Node B, Continued

Log-onto the
Node B
Step Action
Procedure
Telnet 2 Connect alternatively to the Node B (A) and NodeB (B):
Commands Type the Node B IP address into the Host Name
(continued)
Select the connection type: SSH
Click Open

NOTE: WMS SSH server requests Login and Password

3 Telnet to the Node B IP Address

Type: telnet [nodeb_ip_address]

4 Type Login: nodeb | <enter>

Expected Output:
172.26.127.xxx login: nodeb

Continued on next page

20 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 3: Node B Daisy Chaining Telnet Log onto

Node B, Continued

Log-onto the
Node B
Step Action
Procedure
Telnet 5 Type Password: nodeblnx | <enter>
Commands
(continued) NOTE: the password is not displayed on telnet screen while you type

Expected Output:
login as: nodeb
[email protected]'s password: nodeblnx

###
#####
# #O#O#
###### ### #VVV#
## # ## VV ##
## ### ### ### ### ### ##### ##### # ##
## # ## ### ## ## ## ## ## # ##
## # ## ## ## ## ## ### # ###
## ### ## ## ## ## ### QQ# ##Q
## # ### ## ## ## ## ## ## QQQQQQ# #QQQQQQ
## ## ### # ## ## ### ### ## ## QQQQQQQ# #QQQQQQQ
######### ### #### #### ### ## ##### ##### QQQQQ#####QQQQQ

~ ~ ~
\ | /
\ | /
\|/
^ #####################
| # #
+=====# Node B #<<<<<<<<->>>>>>>>
# eccm #
#####################

[ 28-May-2013 15:25 ]

eCCM-nodeb-nodeb>

NOTE: You are now connected to the CCM Board of the Node B.
6 Type: bcish | <enter>

Expected Output:
eCCM-nodeb-nodeb> bcish
/$

NOTE: You are now on the CCM OS terminal to run the BCI application and to
access the BCI menu.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 3: Node B Daisy Chaining Telnet Log onto

Node B, Continued

Log-onto the
Node B
Step Action
Procedure
Telnet 7 Type: pltf and type on the Tabulation key
Commands (an additional number appears after pltf)
(continued) on the BCI root menu

Expected Output:
eCCM-nodeb-nodeb> bcish
/$ pltf_641/
/pltf_641$

NOTE: The Node B platform session is open under the BCI application.

22 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 4: Node B (A) Daisy Chaining Configuration

Checking Procedure (Optional)

Description The configuration details of the Node B in daisy chaining (Node B (A)) can get retrieved from
the Node B through Telnet commands.
NOTE: Node B tests through remote Telnet commands have to be understood as extension of
the WMS based Node B tests and provide additional information (e.g. to support trouble
shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B Daisy Chaining Telnet Log onto Node B is successfully
performed
Laptop is connected to the internet network with RJ45
Node B (A) IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Node B (A) This procedure describes how to check the Node B (A) in Daisy Chaining configuration
Daisy Chaining with usage of Telnet commands.
Configuration
Checking
Procedure NOTE: Procedure Log-on to the Node B with Telnet Commands is already performed.

Step Action
1 Type: emo | <enter> from the Node B platform session open with telnet.

/pltf_641/emo$

Fortsetzung auf nchster Seite

June 30, 2014 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 4: Node B (A) Daisy Chaining Configuration

Checking Procedure (Optional), Fortsetzung

Node B (A) Daisy

Chaining
Step Action
Configuration
Checking 2 Type: Bts | <enter>
Procedure
(Fortsetzung) /pltf_641/emo$ Bts

Expected Output:

--------------------- Configuration ---------------------

Cluster Type ..... REMOTE
Radio Mode ....... STSR 1+1
---------------------------------------------------------
Bts Iub Mode ..... Native IP Check
NODEBCP ASU ...... DISCONNECTED
OMCB ............. connected Check
ALCAP ............ NOT PRESENT
MIBState ......... Build Check
CheckDLU ......... OK
Flip-Flop ........ Not actif
Version .......... UNB09114D00 Check

...
--------------------- Ethernet Configuration -------------
Port id| HW Type |Link_Speed|SFP rate Mode|EFM
Activation | Mode | Remote LB support
3 | RJ45 | 100Mbps | FULL | No
| ACTIVE| NO
1 | SFP_OPT_1000| 1Gbps | FULL | No
| ACTIVE| NO
----------------------------------------------------------

Continued on next page

24 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 4: Node B (A) Daisy Chaining Configuration

Checking Procedure (Optional), Continued

Node B (A) Daisy

Chaining
Step Action
Configuration
Checking 3 Check the Node B (A) configuration is done with:
Procedure BTS Iub Mode Native IP
(continued)
Node B Connected to OMC-B
MIB State is Build
Minimum Software version UNB0911xxxx
Both ports id (example: one with RJ45 and another with SFP OPT) are
active

June 30, 2014 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 5: Node B (A) VLAN Id Checking Procedure

(Optional)

Description This procedure describes the Telnet commands that can be used remotely to check VLAN Id
of the Node B (A) Daisy Chaining under test.
Node B tests through remote Telnet commands have to be understood as extension of the
WMS based Node B tests and provide additional information (e.g. to support trouble shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B Daisy Chaining Telnet Log onto Node B is successfully
performed
Laptop is connected to the internet network with RJ45
Node B (A) IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Continued on next page

26 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 5: Node B (A) VLAN Id Checking Procedure

(Optional), Continued

Node B (A) This procedure describes how to check the VLAN Id of Node B (A) with usage of Telnet
VLAN Id commands.
Checking NOTE: Procedure Log-on to the Node B with Telnet Commands is already performed.
Procedure

Step Action
1 Type: ip | <enter>

/pltf_641/emo/ip$

2 Type: VirtualInterface | <enter>

/pltf_641/emo/ip$ VirtualInterface

Expected Output:
===== The Virtual Interface Object Parameters =====
nbVirtualInterface : 2
VirtualInterface [0] :
nbTypeOfTraffic : 2
TypeOfTraffic : CP and UP
IpAddress : 10.30.3.2xx
VlanId : 303 Check

VirtualInterface [1] :
nbTypeOfTraffic : 1
TypeOfTraffic : OAM
IpAddress : 172.26.127.2xx
VlanId : 301 Check

/pltf_641/emo/ip$

3 Check the VLAN Id value of the Node B (A) is compliant with the Network
configuration:
One VLAN Id dedicated to the CP and UP traffic
One VLAN Id dedicated to the OAM traffic
4 Type: cd .. | <enter> | cd .. | <enter>
To come back to platform session level:
/pltf_641/

June 30, 2014 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 6: Node B (A) Ethernet Port Checking

Procedure (Optional)

Description This procedure describes the Telnet commands that can be used remotely to check Ethernet
Port configuration of the Node B (A) Daisy Chaining under test.
NOTE: Node B tests through remote Telnet commands have to be understood as extension of
the WMS based Node B tests and provide additional information (e.g. to support trouble
shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B Daisy Chaining Telnet Log onto Node B is successfully
performed
Laptop is connected to the internet network with RJ45
Node B (A) IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Continued on next page

28 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 6: Node B (A) Ethernet Port Checking

Procedure (Optional), Continued

Node B (A) This procedure describes how to check the Ethernet Port of Node B (A) with usage of Telnet
Ethernet Port commands.
Checking NOTE: Procedure Log-on to the Node B with Telnet Commands is already performed.
Procedure

Step Action
1 Type: 1 | <enter>

Expected Output: if Ethernet port number selection is: 1 for GE MDA SFP 1

/pltf_641/pltf/ethport$ EthportStatus
STATUS Link Display :
- 0 - Mother Board (MB)
- 1 - Mda-GE SFP 1
- 2 - Mda-GE SFP 2
- 3 - Mda-GE RJ45
ETHPORT number > 1
ETHPORT#1
CONFIG :
-> management_state = ETHPORT_IN_SERVICE Check
-> operational_state = Enable Check
CONFIG SFP :
-> syncE mode activate = No
-> SFP state = Present
-> SFP tx_state = Enabled
-> SFP rate_select = Full Rate
CONFIG EFM :
-> Activation = Disabled
STATUS :
-> availability_status = ETHPORT_CONNECTED Check
-> hw_type = ETHPORT_HW_TYPE_SFP_OPT_1000 Check
-> link_up = UP Check
-> auto_negociation = Complete
-> link_duplex = Full
-> link_speed = ETHPORT_LINK_SPEED_1000
-> test_type = ETHPORT_NO_TEST
ETHPORT_EFM_DISABLE

/pltf_641/pltf/ethport$ EthportStatus

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 6: Node B (A) Ethernet Port Checking

Procedure (Optional), Continued

Node B (A)
Ethernet Port
Step Action
Checking
Procedure 2 Type: 2 | <enter>
(continued)
Expected Output: if Ethernet port number selection is: 2 for GE MDA SFP 2

/pltf_641/pltf/ethport$ EthportStatus
STATUS Link Display :
- 0 - Mother Board (MB)
- 1 - Mda-GE SFP 1
- 2 - Mda-GE SFP 2
- 3 - Mda-GE RJ45
ETHPORT number > 2
/pltf_641/pltf/ethport$

3 Type: 3 | <enter>

Expected Output: if Ethernet port number selection is: 3 for GE MDA RJ45

/pltf_641/pltf/ethport$ EthportStatus
STATUS Link Display :
- 0 - Mother Board (MB)
- 1 - Mda-GE SFP 1
- 2 - Mda-GE SFP 2
- 3 - Mda-GE RJ45
ETHPORT number > 3
ETHPORT#3
CONFIG :
-> management_state = ETHPORT_IN_SERVICE Check
-> operational_state = Enable Check
CONFIG EFM :
-> Activation = Disabled
STATUS :
-> availability_status = ETHPORT_CONNECTED Check
-> hw_type = ETHPORT_HW_TYPE_RJ45 Check
-> link_up = UP Check
-> auto_negociation = Complete
-> link_duplex = Full
-> link_speed = ETHPORT_LINK_SPEED_100
-> test_type = ETHPORT_NO_TEST
ETHPORT_EFM_DISABLE

/pltf_641/pltf/ethport

Continued on next page

30 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 6: Node B (A) Ethernet Port Checking

Procedure (Optional), Continued

Node B (A)
Ethernet Port
Step Action
Checking
Procedure 4 Check that the existing Port configuration of the Node B (A) is compliant with
(continued) the expected network:
Example : (regarding the 3 previous steps)
MDA GE SFP1 is configured with Ethport SFP Optical and connected
MDA GE SFP2 is not configured
MDA GE RJ45 is configured with Ethport RJ45 and connected

June 30, 2014 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 7: Node B (A) Ethernet Port Counters

Checking Procedure (Optional)

Description This procedure describes the Telnet commands that can be used remotely to check Ethernet
Port Counters of the Node B (A) Daisy Chaining under test.
NOTE: Node B tests through remote Telnet commands have to be understood as extension of
the WMS based Node B tests and provide additional information (e.g. to support trouble
shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B Daisy Chaining Telnet Log onto Node B is successfully
performed
Laptop is connected to the internet network with RJ45
Node B (A) IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Continued on next page

32 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 7: Node B (A) Ethernet Port Counters

Checking Procedure (Optional), Continued

Node B (A) This procedure describes how to check the Ethernet Port Counters of Node B (A) with
Ethernet Port usage of Telnet commands.
Counters NOTE: Procedure Log-on to the Node B with Telnet Commands is already performed.
Checking
Procedure
Step Action
1 Type: EthportPortCounters | <enter>

Expected Output:
/pltf_641/pltf/ethport$ EthportPortCounters

Daisy Chain Feature : Activated Daisy Chain on Node B

(A)
Backhaul Port : RJ45 Backhaul port used on
RJ45
Daisy Chain Port : SFP1 Daisy Chain port used
on SFP1

*********************************************************
************ Ethport Daisy Chain Counters
******************Updated Every 5 mins*******************
---------------------------------------------------------
RxFrames RxOctets RxDiscardPkts TxFrames TxOctets
TxDiscardPkts
---------------------------------------------------------
SFP1 526391 35669729 0 906851 94778899 0
RJ45 1204388 106429776 0 1356202 98128672 0
---------------------------------------------------------
/pltf_641/pltf/ethport

2 Check that the existing Port configuration is compliant with the expected
network (example with daisy chain configuration)
3 Check the existing traffic on both Rx and Tx on the Backhaul port (example
RJ45) in the Node B (A) (with Ethernet counters nonzero)
4 Check the existing traffic on both Rx and Tx on the Daisy Chain port
(example SFP1) in the Node B (A) (with Ethernet counters nonzero)

June 30, 2014 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 8: Node B (B) Daisy Chained Configuration

Checking Procedure (Optional)

Description This procedure describes the Telnet commands that can be used remotely to check
Configuration of the Node B (B) Daisy Chained under test.
NOTE: Node B tests through remote Telnet commands have to be understood as extension of
the WMS based Node B tests and provide additional information (e.g. to support trouble
shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B Daisy Chaining Telnet Log onto Node B is successfully
performed
Laptop connected to the internet network with RJ45
Node B (B) IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Node B (B) Daisy This procedure describes how to check the Node B (B) in Daisy Chained configuration with
Chained usage of Telnet commands.
Configuration NOTE: Procedure Log-on to the Node B with Telnet Commands is already performed.
Checking
Procedure
Step Action
1 Type: emo | <enter> from the Node B platform session open with telnet.

/pltf_641/emo$

Fortsetzung auf nchster Seite

34 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 8: Node B (B) Daisy Chained Configuration

Checking Procedure (Optional), Fortsetzung

Node B (B) Daisy

Chained
Step Action
Configuration
Checking 2 Type: Bts | <enter>
Procedure
(Fortsetzung) /pltf_641/emo$ Bts

Expected Output:

--------------------- Configuration ---------------------

Cluster Type ..... REMOTE
Radio Mode ....... STSR 1
---------------------------------------------------------
Bts Iub Mode ..... Native IP Check
NODEBCP ASU ...... DISCONNECTED
OMCB ............. connected Check
ALCAP ............ NOT PRESENT
MIBState ......... Build Check
CheckDLU ......... OK
Flip-Flop ........ Not actif
Version .......... UNB1330A700 Check

...
-------------------- Ethernet Configuration -------------
Port id| HW Type |Link_Speed|SFP rate Mode|EFM
Activation | Mode | Remote LB support
1 |SFP_OPT_1000| 1Gbps | FULL | No |
ACTIVE| NO
---------------------------------------------------------
3 Check the Node B (A) configuration is done with:
BTS Iub Mode Native IP
Node B Connected to OMC-B
MIB State is Build
Minimum Software version UNB0911xxxx
Only one Port id (example: one with SFP OPT) is Active

June 30, 2014 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 9: Node B (B) VLAN Id Checking Procedure

(Optional)

Description This procedure describes the Telnet commands that can be used remotely to check VLAN Id
of the Node B (B) Daisy Chained under test.
Node B tests through remote Telnet commands have to be understood as extension of the
WMS based Node B tests and provide additional information (e.g. to support trouble shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B Daisy Chaining Telnet Log onto Node B is successfully
performed
Laptop connected to the internet network with RJ45
Node B (B) IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Continued on next page

36 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 9: Node B (B) VLAN Id Checking Procedure

(Optional), Continued

Node B (B) This procedure describes how to check the VLAN Id of Node B (B) with usage of Telnet
VLAN Id commands.
Checking
Procedure
NOTE: Procedure Log-on to the Node B with Telnet Commands is already performed.

Step Action
1 Type: ip | <enter>

/pltf_641/emo/ip$

2 Type: VirtualInterface | <enter>

/pltf_641/emo/ip$ VirtualInterface

Expected Output:
===== The Virtual Interface Object Parameters =====
nbVirtualInterface : 2
VirtualInterface [0] :
nbTypeOfTraffic : 2
TypeOfTraffic : CP and UP
IpAddress : 10.30.3.2xx
VlanId : 303 Check

VirtualInterface [1] :
nbTypeOfTraffic : 1
TypeOfTraffic : OAM
IpAddress : 172.26.127.2xx
VlanId : 301 Check

/pltf_641/emo/ip$

3 Check the VLAN Id value of the Node B (A) is compliant with the Network
configuration:
One VLAN Id dedicated to the CP and UP traffic
One VLAN Id dedicated to the OAM traffic
4 Type: cd .. | <enter> | cd .. | <enter>
To come back to platform session level:
/pltf_641/

June 30, 2014 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 10: Node B (B) Ethernet Port Checking

Procedure (Optional)

Description This procedure describes the Telnet commands that can be used remotely to check Ethernet
Port of the Node B (B) Daisy Chained under test.
NOTE: Node B tests through remote Telnet commands have to be understood as extension of
the WMS based Node B tests and provide additional information (e.g. to support trouble
shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B Daisy Chaining Telnet Log onto Node B is successfully
performed
Laptop connected to the internet network with RJ45
Node B (B) IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Node B (B) This procedure describes how to check the Ethernet Port of Node B (B) with usage of Telnet
Ethernet Port commands.
Checking
Procedure
NOTE: Procedure Log-on to the Node B with Telnet Commands is already performed.

Step Action
1 Type: pltf | <enter>
/pltf_641/ pltf$

2 Type: ethport | <enter>

/pltf_641/pltf/ ethport$

Continued on next page

38 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 10: Node B (B) Ethernet Port Checking

Procedure (Optional), Continued

Node B (B)
Ethernet Port
Step Action
Checking
Procedure 3 Type: EthportStatus | <enter>
(continued) /pltf_641/pltf/ethport$ EthportStatus

Expected Output:

STATUS Link Display :

- 0 - Mother Board (MB)
- 1 - Mda-GE SFP 1
- 2 - Mda-GE SFP 2
- 3 - Mda-GE RJ45
ETHPORT number >

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 10: Node B (B) Ethernet Port Checking

Procedure (Optional), Continued

Node B (B)
Ethernet Port
Step Action
Checking
Procedure 4 Type: 1 | <enter>
(continued)
Expected Output: if Ethernet port number selection is: 1 for GE MDA SFP 1

/pltf_641/pltf/ethport$ EthportStatus
STATUS Link Display :
- 0 - Mother Board (MB)
- 1 - Mda-GE SFP 1
- 2 - Mda-GE SFP 2
- 3 - Mda-GE RJ45
ETHPORT number > 1
ETHPORT#1
CONFIG :
-> management_state = ETHPORT_IN_SERVICE Check
-> operational_state = Enable Check
CONFIG SFP :
-> syncE mode activate = No
-> SFP state = Present
-> SFP tx_state = Enabled
-> SFP rate_select = Full Rate
CONFIG EFM :
-> Activation = Disabled
STATUS :
-> availability_status = ETHPORT_CONNECTED Check

-> hw_type = ETHPORT_HW_TYPE_SFP_OPT_1000 Check

-> link_up = UP Check
-> auto_negociation = Complete
-> link_duplex = Full
-> link_speed = ETHPORT_LINK_SPEED_1000
-> test_type = ETHPORT_NO_TEST
ETHPORT_EFM_DISABLE

/pltf_641/pltf/ethport$

Continued on next page

40 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 10: Node B (B) Ethernet Port Checking

Procedure (Optional), Continued

Node B (B)
Ethernet Port
Step Action
Checking
Procedure 5 Type: 2 | <enter>
(continued)
Expected Output: if Ethernet port number selection is: 2 for GE MDA SFP 2

/pltf_641/pltf/ethport$ EthportStatus
STATUS Link Display :
- 0 - Mother Board (MB)
- 1 - Mda-GE SFP 1
- 2 - Mda-GE SFP 2
- 3 - Mda-GE RJ45
ETHPORT number > 2
/pltf_641/pltf/ethport$

6 Type: 3 | <enter>

Expected Output: if Ethernet port number selection is: 3 for GE MDA RJ45

/pltf_641/pltf/ethport$ EthportStatus
STATUS Link Display :
- 0 - Mother Board (MB)
- 1 - Mda-GE SFP 1
- 2 - Mda-GE SFP 2
- 3 - Mda-GE RJ45
ETHPORT number > 3
/pltf_641/pltf/ethport$

7 Check that the existing Port configuration of the Node B (B) is compliant with
the expected network:
Example : (regarding the 3 previous steps)
MDA GE SFP1 is configured with Ethport SFP Optical and connected
MDA GE SFP2 is not configured
MDA GE RJ45 is not configured

June 30, 2014 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

Proc. 11: Node B (B) Ethernet Port Counters

Checking Procedure (Optional)

Description This procedure describes the Telnet commands that can be used remotely to check Ethernet
Port Counters of the Node B (B) Daisy Chained under test.
NOTE: Node B tests through remote Telnet commands have to be understood as extension of
the WMS based Node B tests and provide additional information (e.g. to support trouble
shooting)

IMPORTANT: Node B Daisy Chaining tests by Telnet Commands is optional and

mainly recommended for troubleshooting:

Preconditions Node B is completely integrated on the WMS.

Node B Daisy Chaining through the Node B feature is activated.
Laptop available with a terminal emulator : e.g. Putty (or equivalent)
The Procedure Node B Daisy Chaining Telnet Log onto Node B is successfully
performed
Laptop is connected to the internet network with RJ45
Node B (B) IP address and login details (Login and password) are available

NOTE: Node B tests through Telnet commands are remote tests and do not required site
access to the equipment under test.

Continued on next page

42 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chain Remote Checking Procedure Telnet Commands IEH 521, Section 413

Proc. 11: Node B (B) Ethernet Port Counters

Checking Procedure (Optional), Continued

Node B (B) This procedure describes how to check the Ethernet Port Counters of Node B (B) with
Ethernet Port usage of Telnet commands.
Counters
Checking
Procedure NOTE: Procedure Log-on to the Node B with Telnet Commands is already performed.

Step Action
1 Type: EthportPortCounters | <enter>

Expected Output:
/pltf_641/pltf/ethport$ EthportPortCounters

Daisy Chain Feature : Deactivated No Daisy Chain on

Node B (B)
Backhaul Port : SFP1 Backhaul port used on
SFP1
Daisy Chain Port : (null) Daisy Chain port not
used

*********************************************************
**************** Ethport Daisy Chain Counters
*********************Updated Every 5 mins****************
---------------------------------------------------------
RxFrames RxOctets RxDiscardPkts TxFrames TxOctets
TxDiscardPkts
---------------------------------------------------------
SFP1 858896 90098447 0 511106 34371135 0
RJ45 0 0 0 0 0 0
---------------------------------------------------------
/pltf_641/pltf/ethport$

2 Check that the existing Port configuration is compliant with the expected
network (example without daisy chain configuration)
3 Check the existing traffic on both Rx and Tx only on the Backhaul port
(example SFP1) in the Node B (B) (with Ethernet counters nonzero)

June 30, 2014 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 413 Node B Daisy Chain Remote Checking Procedure Telnet Commands

This page is left blank intentionally

44 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 431

December 15, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

24 Cells and 12 Antenna Pairs Procedures

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation access ...................................................................................... 5
Applicable IEH 521 sections ................................................................................ 5
Applicable documents in LR13.x .......................................................................... 6
Tools Requirements ............................................................................................. 7
General ........................................................................................................ 7
Hardware Tool ................................................................................................ 7
Software Tool ................................................................................................. 7
Applications ................................................................................................... 7
24 Cells and 12 Antenna Pairs - Flow ........................................................................ 8
Radio Configuration check with 24 cells and 12 Antenna Pairs - flow diagram ................... 8
24 Cells and 12 Antenna Pairs Procedure Overview ....................................................... 9
Reference of radio configuration Procedures Mandatory ........................................... 9
24 Cells and 12 Antenna Pairs Checklists ................................................................. 10
Purpose ...................................................................................................... 10
Checklist Customization .................................................................................. 10
Remote Operations Checklist ............................................................................ 10
24 Cells and 12 Antenna Pairs Parameters Forms ....................................................... 12
General ...................................................................................................... 12
Node B Parameters Required prior to check the Node B Configuration .......................... 12
Node B: Frequency Band .................................................................................. 12
Radio Module Configuration 24 Cells and 12 Antenna Pairs ...................................... 13
Configuration Overview and Details ........................................................................ 14
Description .................................................................................................. 14
Hardware requirement .................................................................................... 14
24 Cells and 12 Antenna Pairs Rules Description ..................................................... 15
BBU Hostelling Configurations - RRH60-21/C based ................................................. 16

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

BBU Hostelling Configurations - RRH2x60-21A based ............................................... 17

Dual-Band Configurations - TRDU/MCTRX/RRH based ............................................. 18
Proc 1: 24 Cells and 12 antenna Pairs Preparation Procedure ........................................ 19
Description .................................................................................................. 19
Preconditions ............................................................................................... 19
24 Cells and 12 Antennas Pairs Configuration Check Preparation Procedure ................... 19
Selection Table ............................................................................................. 21
Proc 2: Configuration Type 1 - Visual Check Procedure ................................................ 22
Description .................................................................................................. 22
Preconditions ............................................................................................... 22
Visual Check Procedure Configuration Type 1 - RRH60-21C ...................................... 23
Proc 3: Configuration Type 2 - Visual Check Procedure ................................................ 25
Description .................................................................................................. 25
Preconditions ............................................................................................... 25
Visual Check Procedure Configuration Type 2 TRDU60-21B + RRH60-09 ..................... 25
Proc 4: Configuration Type 3 - Visual Check Procedure ................................................ 28
Description .................................................................................................. 28
Preconditions ............................................................................................... 28
Visual Check Procedure Configuration Type 3 RRH60-21C + RRH60-09 ....................... 28
Proc 5: Configuration Type 4 - Visual Check Procedure ................................................ 30
Description .................................................................................................. 30
Preconditions ............................................................................................... 30
Visual Check Procedure Configuration Type 5 RRH60-21C + RRH40-21C + RRH60-09 ...... 30
Proc 6: Configuration Type: Dual Band with TRDU/RRH - Visual Check Procedure ................ 33
Description .................................................................................................. 33
Preconditions ............................................................................................... 33
Visual Check Procedure - Configuration Type Dual Band w/ TRDU60-21 or RRH60-21 ........ 33
Proc 7: Configuration Type: Dual Band with RRH2x - Visual Check Procedure ..................... 36
Description .................................................................................................. 36
Preconditions ............................................................................................... 36
Visual Check Procedure - Configuration type Dual Band w/ RRH2x60-21 - ...................... 36
List of Figures

Figure 1: Radio Configuration check with 24 Cells and 12 Antenna Pairs: Flow diagram..................... 8
Figure 2: Config. #2 with 3 TRDU60-21B + 3 RRH60-09 ........................................................... 25
Figure 3: Config. 3 with 3 x RRH60-21C + 3 RRH60-09 ............................................................ 28
Figure 4: Config. 4 with RRH60-21C + RRH40-21C and 3 RRH60-09 ............................................. 30
Figure 5: Dual Band Configuration: DB1 / DB2 / DB3 /DB4 ...................................................... 33
Figure 6: Dual Band Configuration with RRH2x60-21: DB5 / DB6 ............................................... 36

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Commissioning Tests ............................... 5
Table 2: Applicable IEH 521 Sections for WCDMA Node B Integration Tests .................................... 5
Table 3: Applicable Methods Documents LR13.x for IEH521 ....................................................... 6
Table 4: Hardware Tools ................................................................................................. 7
Table 5: Software Tools .................................................................................................. 7
Table 6: Operational Procedures to Check the Radio Configuration ............................................. 9
Table 7: Sequence of Operations Used to Check the Radio Configuration .................................... 10

2 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Table 8: Node B Parameters Required Prior to Node B Commissioning ........................................ 12

Table 9: UMTS Frequency Band ....................................................................................... 12
Table 10: Radio configuration (24 Cells and 12 Antenna Pairs) ................................................. 13
Table 11: Definition of Sector, Carrier and Cell ................................................................... 15
Table 12: BBU Hostelling Configuration with RRH60-21 /C ...................................................... 16
Table 13: BBU Hostelling Configuration with RRH2x60-21A...................................................... 17
Table 14: Dual Band Configuration with TRDU / MC-TRX / RRH ................................................ 18

December 15, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

General

Section This section provides detailed information about the individual procedures for tests of a
Description WCDMA Node B prior to enabling the 24 Cells and 12 Antenna Pairs feature
Preconditions
Inputs
Outputs
Additional details
Link to commissioning methods document where the procedure is contained

Previous Release New creation

Date

Release Notes New creation: December 2013 under utilization of existing IM documents for LR13.1.

4 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B commissioning tests.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required for WCDMA Node B commissioning tests.
521 sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B

Commissioning Tests

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
310 Node B Commissioning Testing
399 Node B Commissioning Test Records

Table 2: Applicable IEH 521 Sections for WCDMA Node B Integration

Tests

Section Description
401 Integration Planning
402 Integration into existing UTRAN
410 Integration Testing
499 Node B Integration Test Records

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

References, Continued

Applicable The following methods documents are required to perform the Node B commissioning and
documents in integration in LR13.x
LR13.x

Table 3: Applicable Methods Documents LR13.x for IEH521

Doc Number Doc Title URL
9YZ-04088- Alcatel-Lucent Node B http://cic.us.alcatel-
0095-RJZZA Commissioning Procedure lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=55054&prc=Unknown
9YZ-04088- Alcatel-Lucent Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault lucent.com/cgi-
Management User Manual: TIL bin/design2006/dbaccessprototyp
e1/01?key=55050&prc=Unknown
9YZ-04088- Alcatel-Lucent Node B Integration in http://cic.us.alcatel-
0098-RJZZA an existing UTRAN lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=55057&prc=Unknown
9YZ-04088- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
0014-PCZZA Management System User Guide lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=54991&prc=Unknown
9YZ-04088- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
0015-TQZZA Management System - Security lucent.com/cgi-
Fundamentals bin/design2006/dbaccessprototyp
e1/01?key=54992&prc=Unknown

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

6 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Tools Requirements

General This section describes the hardware and software tools required to perform the commissioning
method.

Hardware Tool The hardware tools listed in the following table are required to perform the commissioning test.

Table 4: Hardware Tools

Hardware Tool Quantity Description
Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

Software Tool The software tool listed in the following table are required to perform the commissioning test

Table 5: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with
WIN7)

Applications The tools listed here are necessary to perform the check of this feature 24 Cells and 12
Antenna Pairs:
OMCB,
NEM,
TIL,
LAMP,
Wireless data card

December 15, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

24 Cells and 12 Antenna Pairs - Flow

Radio The flow diagram below outlines the steps to check the radio configuration with 24 cells and
Configuration 12 Antenna Pairs
check with 24
cells and 12
Antenna Pairs - Figure 1: Radio Configuration check with 24 Cells and 12 Antenna
flow diagram Pairs: Flow diagram

8 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

24 Cells and 12 Antenna Pairs Procedure Overview

Reference of The following table lists all operational procedures to check the radio configuration with 24
radio cells and 12 Antenna Pairs.
configuration
Procedures
Mandatory Table 6: Operational Procedures to Check the Radio Configuration
Step Operation Opt/ Proc. Remark
Mand.
1 Proc 1: 24 Cells and 12 M Proc. 1 Selection of the
antenna Pairs Preparation configuration used
Procedure
2 Proc 2: Configuration Type 1 O Proc. 2 If configuration Type 1 is
- Visual Check Procedure used
3 Proc 3: Configuration Type 2 O Proc. 3 If configuration Type 2 is
- Visual Check Procedure used
4 Proc 4: Configuration Type 3 O Proc. 4 If configuration Type 3 is
- Visual Check Procedure used
5 Proc 5: Configuration Type 4 O Proc. 5 If configuration Type 4 is
- Visual Check Procedure used
6 Proc 6: Configuration Type: O Proc. 6 If configuration Type Dual
Dual Band with TRDU/RRH - Band with TRDU/RRH is
Visual Check Procedure used
7 Proc 7: Configuration Type: O Proc. 7 If configuration Type Dual
Dual Band with RRH2x - Band with RRH2x is used
Visual Check Procedure

December 15, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

24 Cells and 12 Antenna Pairs Checklists

Purpose Checklists are available to support and document the flow of operations before, during and post
the check of the radio configuration with 24 cells and 12 Antenna Pairs for
On site activities
Node B and RF parameters
Remote (TIL) operations
and document successful completion of the radio configuration with 24 cells and 12 Antenna
Pairs by customer acceptance

Checklist The checklists of IEH521 are generic and can be used as basis for further modifications and
Customization enhancements as per specific customer / market requirements.

Remote Sequence of operations for use by remote operations to verify success of mandatory and
Operations optional steps
Checklist

Table 7: Sequence of Operations Used to Check the Radio Configuration

Procedure Condition Expected result To OK NOK

use?
Proc 1: 24 Cells and 12 Mandatory The preconditions of radio
antenna Pairs Preparation configuration are fulfilled.
Procedure The next visual check procedure Y/N
is selected according to the
Radio configuration used.
Proc 2: Configuration Type 1 - If configuration The TIL GUI is compliant to the
Visual Check Procedure Type 1 is used expected final configuration Type Y/N
1
Proc 3: Configuration Type 2 - If configuration The TIL GUI is compliant to the
Visual Check Procedure Type 2 is used expected final configuration Type Y/N
2
Proc 4: Configuration Type 3 - If configuration The TIL GUI is compliant to the
Visual Check Procedure Type 3 is used expected final configuration Type Y/N
3
Proc 5: Configuration Type 4 - If configuration The TIL GUI is compliant to the
Visual Check Procedure Type 4 is used expected final configuration Type Y/N
4

Continued on next page

10 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

24 Cells and 12 Antenna Pairs Checklists, Continued

Remote Operations Checklist (continued)

Procedure Condition Expected result To OK NOK

use?
Proc 6: Configuration Type: If configuration The TIL GUI is compliant to the
Dual Band with TRDU/RRH - Type Dual Band expected final configuration Type
Y/N
Visual Check Procedure with TRDU/RRH is Dual Band with TRDU/RRH
used
Proc 7: Configuration Type: If configuration The TIL GUI is compliant to the
Dual Band with RRH2x - Type Dual Band expected final configuration Type
Y/N
Visual Check Procedure with RRH2x is Dual Band with RRH2x.
used

December 15, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

24 Cells and 12 Antenna Pairs Parameters Forms

General This section contains the forms for parameters needed to connect the TIL on the Node B to
perform the visual inspection of the radio configuration with 24 cells and 12 pairs of antenna.
The parameter forms are based on the CIQ and must be documented by the coordinator
according to the expected parameters and configuration.
The form of parameters must be sent by email or available on a link.

Node B The following table is the list of Node B parameters required for the visual check of the radio
Parameters configuration with 24 cells and 12 Antenna Pairs.
Required prior
to check the
Node B Table 8: Node B Parameters Required Prior to Node B Commissioning
Configuration
Node B parameter Value for Node B
Node B IP address
Configuration
Sub-network mask
Node B - Software version (LR13.1 minimum)
Hardware reference
BTS Parameters:

Node B: The following table gives the UMTS Frequency Band used by the Node B and the Radio
Frequency Module.
Band

Table 9: UMTS Frequency Band

UMTS Frequency (Band)
850Mhz 900Mhz 1900Mhz AWS 2100Mhz
(Band V) (Band VIII) (Band II) (Band IV) (Band I)

Continued on next page

12 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

24 Cells and 12 Antenna Pairs Parameters Forms,

Continued

Radio Module The following table gives the usable radio Configuration with 24 Cells and 12 Antenna Pairs.
Configuration
24 Cells and 12
Antenna Pairs Table 10: Radio configuration (24 Cells and 12 Antenna Pairs)

Main Radio configuration Config Refer to Refer to

(24 Cells and 12 Antenna Pairs) Used? Config # table #
in Proc 1
6x2 RRH60-21C (STSR2) Y/N H1 (1)

4x3 RRH60-21C (STSR2) Y/N H1 (2)

2x3 RRH60-21C (STSR2)

Y/N H1 (3)
+ 3x2 RRH60-21C (STSR2) 16
3x3 RRH60-21C (STSR2) with
H1 (4) RRH60-21
+ 1x2 RRH60-21C (STSR2) Y/N
C
+ 1x1 RRH60-21C (STSR2)
1x3 RRH60-21C (STSR2)
+ 4x2 RRH60-21C (STSR2) Y/N H1 (5)
+ 1x1 RRH60-21C (STSR2)
6x2 RRH2x60-21A Y/N H2 (1)
4x3 RRH2x60-21A Y/N H2 (2)

8x1 RRH2x60-21A Y/N H3 17

4x2 RRH2x60-21A Y/N H3 (3) with
RRH2x60-
3x2 RRH2x60-21A + 1x2 RRH2x60-21A Y/N H3 21 A

8x1 RRH2x60-21A Y/N H4

4x2 RRH2x60-21A Y/N H4 (4)

3x2 TRDU60-21 + 3x1 MCTRX 900 Y/N DB1

3x2 TRDU60-21 + 3x1 RRH 900 Y/N DB2 18

3x2 RRH60-21 + 3x1 RRH 900 Y/N DB3 with TRDU
/ MC-TRX /
3x2 RRH60- 21 + 3x1 MCTRX 900 Y/N DB4 RRH /
RRH2x
3x1 Twin RRH2x60-21 + 3x1 MCTRX 900 Y/N DB5

3x1 Twin RRH2x60-21 + 3x1 RRH 900 Y/N DB6

December 15, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Configuration Overview and Details

Description The feature 24 cells and 12 antenna pairs allows a number of possible configurations to
support hostelling and dual-band operation.

Hardware The following table lists the hardware supported by this feature 24 Cells and 12 Antenna Pairs
requirement

Cabinet Board Outdoor Radio Indoor Radio

Equipment Equipment
9326 D2U v2 xCCM-U RRH40-21 TRDU
9926 BBU (D2U v3) eCCM-U RRH60-09 MC TRDU
9926 D4U v3 xCEM-U RRH60-21C MCTRX
9311 Macro Indoor2 eCEM-U RRH2x60-21 (Twin)
RRH2x60-850 (Twin)

Continued on next page

14 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Configuration Overview and Details, Continued

24 Cells and 12 The following table describes the possible configurations of 24 cells and 12 antennas through
Antenna Pairs schematic representation.
Rules
Description

IMPORTANT: Dependency of configuration from RRH type exists. Please use

BBU hostelling configuration and dual band configuration tables to determine.

Table 11: Definition of Sector, Carrier and Cell

When ... Then ...
1 sector x 1 carrier = 1 cell
1 sector x 2 carriers = 2 cells
3 sectors x 2 carriers = 6 cells

3 sectors x 5 carriers = 15 cells

Refer to Configuration 2
3 sectors x 6 carriers = 18 cells
Refer to Configuration 3

6 sectors x 2 carriers = 12 cells

Refer to Configuration H2

6 sectors x 3 carriers = 18 cells

Refer to Configuration 4

6 sectors x 4 carriers = 24 cells

12 sectors x 2 carriers = 24 cells

Refer to Configuration 1

3 sectors x 4 carriers (2100Mhz) 12 cells +

3 sectors with 2 carriers (900Mhz) 6 cells
+
= 18 cells
Refer to Configuration DB 1/ 2 / 3 / 4

3 sectors x 3 carriers (2100Mhz) 9 cells +

+ 3 sectors with 2 carriers (900Mhz) 6 cells
= 15 cells
Refer to Configuration DB 5 /6

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Configuration Overview and Details, Continued

BBU Hostelling BBU Hostelling Configurations with distributed Node B and RRH60-21C
Configurations -
RRH60-21/C
based Table 12: BBU Hostelling Configuration with RRH60-21 /C
BBU Hostelling
CPRI Port # (on CCM-U)
Config. #

Fibers Configurations

Cells
RF Modules Band A

Chain
Daisy
STSR
RRH60-21 /C 1 2 3 4 5 6

H1 6x2 11 21 31 41 51 61
6 24 DC 2
(1) RRH60-21C 12 22 32 42 52 62
11 21 41 51
H1 4x3
4 24 DC 2 12 22 42 52
(2) RRH60-21C
13 23 43 53
11 41
2x3
DC 2 12 42
RRH60-21C +
H1
5 24 13 43
(3)
3x2 21 31 51
DC 2
RRH60-21C 22 32 52
11 21 31
3x3
DC 2 12 22 32
RRH60-21C +
13 23 33
H1
5 24 1x2 41
(4)
DC 2
RRH60-21C + 42
1 x1
- 2 51
RRH60-21C
DC 11
1x3
2 12
RRH60-21C +
13
H1
6 24 4x2 DC 21 31 41 51
(5)
2
RRH60-21C + 22 32 42 52
1x1
2 61
RRH60-21C

Continued on next page

16 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Configuration Overview and Details, Continued

BBU Hostelling BBU Hostelling Configurations with RRH2x60-21A including (RRH2x60 21A (2T4R) 4
Configurations - Antennas
RRH2x60-21A
based
Table 13: BBU Hostelling Configuration with RRH2x60-21A

BBU Hostelling
CPRI Port # (on CCM-U)
Config. #

Configurations
Fibers

Cells
RF Modules Band A

Chain
Daisy
STSR
RRH2x60-21A 1 2 3 4 5 6

H2 6x2 11 21 31 41 51 61
6 24 DC 1+1
(1) RRH2x60-21A 12 22 32 42 52 62
11 21 41 51
H2 4x3
4 24 DC 1+1 12 22 42 52
(2) RRH2x60-21A
13 23 43 53
8x1 11 21 31 41 51 61
H3 6 22 DC 2+1
RRH2x60-21A 12 42

H3 4x2 11 21 41 51
4 22 DC 2+1
(3) RRH2x60-21A 12 22 42 52
3x2 11 21 31
DC 2+1
RRH2x60-21A + 12 22 32
H3 4 22
1x2 41
DC 1+1
RRH2x60-21A 42
8x1 11 21 31 41 51 61
H4 6 22 DC 3
RRH2x60-21A 12 42

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Configuration Overview and Details, Continued

Dual-Band Dual-Band Configurations supported with 9926 BBU 4U and Local radio TRDU and MCTRX,
Configurations - remote radio RRH
TRDU/MCTRX/RR
H based
Table 14: Dual Band Configuration with TRDU / MC-TRX / RRH

Dual Band Configurations CPRI Port # (on CCM-U)

Config. #

Fibers

Cells RF Modules Band A (2100) Band B (900)

Chain
Daisy
STSR
1 2 3 4 5 6
3x2 11 21 31
(TRDU60-21 DC 2+2
DB1 12 22 32
or 6 15 or RRH60- 21)+
DB4
3x1
- 1 41 51 61
( MCTRX 900)
3x2 11 21 31
DB2 (TRDU60-21 DC 2+2
or 6 15 12 22 32
or RRH60-21)+
DB3
3 x 1 (RRH 900) - 1 41 51 61
3x2 11 21 31
(TRDU60-21 DC 2+2
12 22 32
or RRH60-21)+
4 15
1 x 3 (RRH 900) 41
- 1 42 nc nc
43
3 x 1 (Twin
- 2+2 11 21 31
RRH2x60-21)+
DB5
or 6 15 3x1
DB6 - 1 41 51 61
(MCTRX 900 or
RRH 900)
3 x 1 (Twin
- 2+2 11 21 31
RRH2x60-21)+
4 15 3 x 1 (RRH 900) 41
DC 1 42 nc nc
43

18 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 1: 24 Cells and 12 antenna Pairs Preparation

Procedure

Description This procedure describes the way to visually check with TIL GUI the configuration cases with
24 Cells and 12 Antenna Pairs

Preconditions The Node B + Radio Equipment (RE) are already fully Integrated
The 24 Cells and 12 Antenna Pairs feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

24 Cells and 12 Perform these steps to check the 24 Cells and 12 Antenna Pairs configuration with TIL GUI.
Antennas Pairs
Configuration
Check Step Action
Preparation
Procedure 1 In the TIL GUI:
Check that the information contained in the TIL board's GUI complies with the
Node B configuration:

If check... Then parameter must be...

The software reference UNB131xxxxx (minimum software load
(LR13.1)
Freq Band 1 2100Mhz
Freq Band 2 (if Dual Band used) 900Mhz or 850Mhz

NOTE: If abnormal check occurred, contact the site coordinator before going
on.
2 Identify 24Cells and 12 antenna pairs configuration from tables 12 to 14:

If Configuration used is... Then Refer to...

with RRH60-21 or RRH60-21C Table 12 BBU
Hostelling Configuration
with RRH60-21 /C
with RRH2x60-21A Table 13 BBU
Hostelling Configuration
with RRH2x60-21A
with TRDU / MC-TRX / RRH (in Dual Band) Table 14 Dual Band
Configuration with TRDU /
MC-TRX / RRH

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 1: 24 Cells and 12 antenna Pairs Preparation

Procedure, Continued

24 Cells and 12
Antennas Pairs
Step Action
Configuration
Check 3 Select visual check procedure type from selection table.
Preparation
Procedure NOTE: Input to selection is Configuration number from procedure step before.
(continued)

Continued on next page

20 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 1: 24 Cells and 12 antenna Pairs Preparation

Procedure, Continued

Selection Table The following table is available to support the procedure selection for the visual checks of 24
cells and 12 antenna pairs feature prior to activation

If target configuration is ... Then

Radio configuration Config # Refer to
6x2 RRH60-21C (STSR2) H1 (1)
4x3 RRH60-21C (STSR2) H1 (2)
2x3 RRH60-21C (STSR2) Go to configuration
H1 (3)
+ 3x2 RRH60-21C (STSR2) type 1
Table 12
3x3 RRH60-21C (STSR2) type 2
with RRH60-
+ 1x2 RRH60-21C (STSR2) H1 (4) type 3
21 C
+ 1x1 RRH60-21C (STSR2) type 4
Procedure
1x3 RRH60-21C (STSR2)
+ 4x2 RRH60-21C (STSR2) H1 (5)
+ 1x1 RRH60-21C (STSR2)
6x2 RRH2x60-21A H2 (1)
4x3 RRH2x60-21A H2 (2)
8x1 RRH2x60-21A H3
Table 13 Go to Configuration type
4x2 RRH2x60-21A H3 (3) Dual Band with
with
RRH2x60-21 RRH2x60-21
3x2 RRH2x60-21A
H3 A
+ 1x2 RRH2x60-21A
8x1 RRH2x60-21A H4
4x2 RRH2x60-21A H4 (4)
3x2 TRDU60-21
DB1
+ 3x1 MCTRX 900
3x2 TRDU60-21 Go to Dual Band
DB2
+ 3x1 RRH 900 configuration with
3x2 RRH60-21 TRDU60-21 or
DB3 Table 14
+ 3x1 RRH 900 RRH60-21
with TRDU /
3x2 RRH60- 21 MC-TRX /
DB4 RRH / RRH2x
+ 3x1 MCTRX 900
3x1 Twin RRH2x60-21
DB5 Go to Dual Band
+ 3x1 MCTRX 900
configuration with
3x1 Twin RRH2x60-21 RRH2x60-21
DB6
+ 3x1 RRH 900

December 15, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 2: Configuration Type 1 - Visual Check

Procedure

Description This procedure describes the way to visually check with TIL GUI the configurations type 1 with
24 Cells and 12 Antenna Pairs

Preconditions The Node B + Radio Equipment (RE) are already fully Integrated
The 24 Cells and 12 Antenna Pairs feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

Continued on next page

22 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 2: Configuration Type 1 - Visual Check

Procedure, Continued

Visual Check Perform the following procedure steps to visually check the BBU Hostelling Configuration with
Procedure RRH60.21C
Configuration
Type 1 -
RRH60-21C Step Action
1 Check with help of TIL GUI the compliancy with configuration 1
Configuration 1:
12 RRH60-21C in 4 chains and 3 Radio Element (RE) per chain.
(12 Sectors x 2 Carriers = 24 cells)
Config H1

Config. #1 with 12 x RRH60-21C

2 On the GUI xCOB:

Double click on the OIx GUI connected with the Radio Modules on the xCOB
GUI of the TIL

NOTE: The following TIL GUI appears for each CPRI link connected (here
Ol1; Ol2 and Ol4; Ol5):

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 2: Configuration Type 1 - Visual Check

Procedure, Continued

Visual Check
Procedure
Step Action
Configuration
Type 1 - RRH60- 3 Check that the 24 Cells and 12 antenna Pairs are clearly identified in all use
21C (continued) cases of radio configuration with the TIL GUI.

If TIL GUI ... Then ...

Does not identify the 24 cells and 12 Contact the support team to
antenna pairs in all use cases of troubleshoot the issue.
radio configuration.
Has clearly identified 24 cells and
12 antenna pairs in all use cases of The radio configuration is compliant
radio configuration. with the expected final Node B
configuration

4 Right click on the GUI to select Return to main GUI on the pop-up menu of
Radio Modules view

NOTE: Once compliancy of configuration at site with 24 cells and 12 antenna pairs is confirmed
the following further steps need to happen to complete the feature activation
finalize the Node B commissioning testing by use of IEH521 - 310
finalize the Node B Integration testing by use of IEH521 - 410
Fill the Test records with the identified Radio Configuration.

24 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 3: Configuration Type 2 - Visual Check

Procedure

Description This procedure describes the way to visually check with TIL GUI the configurations type 2 with
24 Cells and 12 Antenna Pairs

Preconditions The Node B + Radio Equipment (RE) are already fully Integrated
The 24 Cells and 12 Antenna Pairs feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

Visual Check Perform the following procedure steps to visually check the Dual Band Configuration with
Procedure TRDU60-21B + RRH60-09
Configuration
Type 2
TRDU60-21B + Step Action
RRH60-09
1 Check with help of TIL GUI the compliancy with configuration 2:
Configuration 2:
3 TRDU60-21B (STSR2+2) + 3 RRH60-09 (STSR1)
(3 Sectors x 5 Carriers = 15 Cells)
(with 9311 Macro ID2 + xCOB)

Figure 2: Config. #2 with 3 TRDU60-21B + 3 RRH60-09

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 3: Configuration Type 2 - Visual Check

Procedure, Continued

Visual Check
Procedure
Step Action
Configuration
Type 2 2 Double click on the OI1 GUI connected with the Radio Modules on the xCOB
TRDU60-21B + GUI of the TIL
RRH60-09
(continued) NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol1; Ol2 and Ol3):

3 Double click on the OI4 GUI connected with the Radio Modules on the xCOB
GUI of the TIL

NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol4; Ol5 and Ol6):

Continued on next page

26 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 3: Configuration Type 2 - Visual Check

Procedure, Continued

Visual Check
Procedure
Step Action
Configuration
Type 2 4 Check that the 24 Cells and 12 antenna Pairs are clearly identified in all use
TRDU60-21B + cases of radio configuration with the TIL GUI.
RRH60-09
(continued)
If TIL GUI ... Then ...
Does not identify the 24 cells and 12 Contact the support team to
antenna pairs in all use cases of troubleshoot the issue.
radio configuration.
Has clearly identified 24 cells and
12 antenna pairs in all use cases of The radio configuration is compliant
radio configuration. with the expected final Node B
configuration

5 Right click on the GUI to select Return to main GUI on the pop-up menu of
Radio Modules view

NOTE: Once compliancy of configuration at site with 24 cells and 12 antenna pairs is confirmed
the following further steps need to happen to complete the feature activation
finalize the Node B commissioning testing by use of IEH521 - 310
finalize the Node B Integration testing by use of IEH521 - 410
Fill the Test records with the identified Radio Configuration.

December 15, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 4: Configuration Type 3 - Visual Check

Procedure

Description This procedure describes the way to visually check with TIL GUI the configurations type 3 with
24 Cells and 12 Antenna Pairs

Preconditions The Node B + Radio Equipment (RE) are already fully Integrated
The 24 Cells and 12 Antenna Pairs feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

Visual Check Perform the following procedure steps to visually check the Dual Band Configuration with
Procedure RRH60-21C + RRH60-09
Configuration
Type 3
RRH60-21C + Step Action
RRH60-09
1 Check with help of TIL GUI the compliancy with configuration 3
Configuration 3:
3 RRH60-21C (STSR3) + 3 RRH60-09 (STSR3)
(3 Sectors x 6 Carriers = 18 Cells)
(with d2UV2)

Figure 3: Config. 3 with 3 x RRH60-21C + 3 RRH60-09

Continued on next page

28 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 4: Configuration Type 3 - Visual Check

Procedure, Continued

Visual Check
Procedure
Step Action
Configuration
Type 3 RRH60- 2 Double click on the OI4 GUI connected with the Radio Modules on the xCOB
21C + RRH60-09 GUI of the TIL
(continued)
NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol1 to OI6):

3 Check that the 24 Cells and 12 antenna Pairs are clearly identified in all use
cases of radio configuration with the TIL GUI.

If TIL GUI ... Then ...

Does not identify the 24 cells and 12 Contact the support team to
antenna pairs in all use cases of troubleshoot the issue.
radio configuration.
Has clearly identified 24 cells and
12 antenna pairs in all use cases of The radio configuration is compliant
radio configuration. with the expected final Node B
configuration

4 Right click on the GUI to select Return to main GUI on the pop-up menu of
Radio Modules view

NOTE: Once compliancy of configuration at site with 24 cells and 12 antenna pairs is confirmed
the following further steps need to happen to complete the feature activation
finalize the Node B commissioning testing by use of IEH521 - 310
finalize the Node B Integration testing by use of IEH521 - 410
Fill the Test records with the identified Radio Configuration.

December 15, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 5: Configuration Type 4 - Visual Check

Procedure

Description This procedure describes the way to visual check with TIL GUI the configurations type 4 with
24 Cells and 12 Antenna Pairs

Preconditions The Node B + Radio Equipment (RE) are already fully Integrated
The 24 Cells and 12 Antenna Pairs feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

Visual Check Perform the following procedure steps to visually check the Dual Band Configuration with
Procedure RRH40-21 + RRH60-21C + RRH60-09
Configuration
Type 5
RRH60-21C + Step Action
RRH40-21C +
RRH60-09 1 Check with help of TIL GUI the compliancy with configuration 4
Configuration 4:
3 chain with RRH60-21C + RRH40-21C (STSR2), and
3 fibers for RRH60-09 (STSR1)
(6 Sectors x 3 Carriers = 18 cells)
(with d2UV2)

Figure 4: Config. 4 with RRH60-21C + RRH40-21C and 3

RRH60-09

Continued on next page

30 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 5: Configuration Type 4 - Visual Check

Procedure, Continued

Visual Check
Procedure
Step Action
Configuration
Type 5 RRH60- 2 Double click on the OI1 GUI connected with the Radio Modules on the xCOB
21C + RRH40- GUI of the TIL
21C + RRH60-09
(continued) NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol1; Ol2 and Ol3):

3 Double click on the OI4 GUI connected with the Radio Modules on the xCOB
GUI of the TIL

NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol4; Ol5 and Ol6):

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 5: Configuration Type 4 - Visual Check

Procedure, Continued

Visual Check
Procedure
Step Action
Configuration
Type 5 RRH60- 4 Check that the 24 Cells and 12 antenna Pairs are clearly identified in all use
21C + RRH40- cases of radio configuration with the TIL GUI.
21C + RRH60-09
(continued)
If TIL GUI ... Then ...
Does not identify the 24 cells and 12 Contact the support team to
antenna pairs in all use cases of troubleshoot the issue.
radio configuration.
Has clearly identified 24 cells and
12 antenna pairs in all use cases of The radio configuration is compliant
radio configuration. with the expected final Node B
configuration

5 Right click on the GUI to select Return to main GUI on the pop-up menu of
Radio Modules view

NOTE: Once compliancy of configuration at site with 24 cells and 12 antenna pairs is confirmed
the following further steps need to happen to complete the feature activation
finalize the Node B commissioning testing by use of IEH521 - 310
finalize the Node B Integration testing by use of IEH521 - 410
Fill the Test records with the identified Radio Configuration.

32 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 6: Configuration Type: Dual Band with

TRDU/RRH - Visual Check Procedure

Description This procedure describes the way to visual check with TIL GUI the configurations Type: Dual
Band with TRDU/RRH supporting 24 Cells and 12 Antenna Pairs

Preconditions The Node B + Radio Equipment (RE) are already fully Integrated
The 24 Cells and 12 Antenna Pairs feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

Visual Check Perform the following procedure steps to visually check the Dual Band Configuration with
Procedure - TRDU60-21 or RRH60-21 and MCTRX900 or RRH900
Configuration
Type Dual Band
w/ TRDU60-21 Step Action
or RRH60-21
1 Check the Dual Band Configuration according to the target configuration used:
DB1 / DB2 / DB3 / DB4

Figure 5: Dual Band Configuration: DB1 / DB2 / DB3 /DB4

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 6: Configuration Type: Dual Band with

TRDU/RRH - Visual Check Procedure, Continued

Visual Check
Procedure -
Step Action
Configuration
Type Dual Band 2 Double click on the OI1 GUI connected with the Radio Modules on the xCOB
w/ TRDU60-21 GUI of the TIL
or RRH60-21
(continued) NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol1; Ol2 and Ol3):

OR

3 Double click on the OI4 GUI connected with the Radio Modules on the xCOB
GUI of the TIL

NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol4; Ol5 and Ol6):

OR

Continued on next page

34 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 6: Configuration Type: Dual Band with

TRDU/RRH - Visual Check Procedure, Continued

Visual Check
Procedure -
Step Action
Configuration
Type Dual Band 4 Check that the 24 Cells and 12 antenna Pairs are clearly identified in all use
w/ TRDU60-21 cases of radio configuration with the TIL GUI.
or RRH60-21
(continued)
If TIL GUI ... Then ...
Does not identify the 24 cells and 12 Contact the support team to
antenna pairs in all use cases of troubleshoot the issue.
radio configuration.
Has clearly identified 24 cells and
12 antenna pairs in all use cases of The radio configuration is compliant
radio configuration. with the expected final Node B
configuration

5 Right click on the GUI to select Return to main GUI on the pop-up menu of
Radio Modules view

NOTE: Once compliancy of configuration at site with 24 cells and 12 antenna pairs is confirmed
the following further steps need to happen to complete the feature activation
finalize the Node B commissioning testing by use of IEH521 - 310
finalize the Node B Integration testing by use of IEH521 - 410
Fill the Test records with the identified Radio Configuration.

December 15, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 7: Configuration Type: Dual Band with RRH2x -

Visual Check Procedure

Description This procedure describes the way to visually check with TIL GUI the configurations Type: Dual
Band with RRH2x supporting 24 Cells and 12 Antenna Pairs.

Preconditions The Node B + Radio Equipment (RE) are already fully Integrated
The 24 Cells and 12 Antenna Pairs feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

Visual Check Perform the following procedure steps to visually check the Dual Band Configuration with
Procedure - RRH2x60-21 + RRH60-09 or MCTRX-900
Configuration
type Dual Band
w/ RRH2x60-21 Step Action
-
1 Check the Dual Band Configuration according to the target configuration used:
DB5 / DB6

Figure 6: Dual Band Configuration with RRH2x60-21: DB5 /

DB6

Continued on next page

36 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
24 Cells and 12 Antenna Pairs Procedures IEH 521, Section 431

Proc 7: Configuration Type: Dual Band with RRH2x -

Visual Check Procedure, Continued

Visual Check
Procedure -
Step Action
Configuration
type Dual Band 2 Double click on the OI1 GUI connected with the Radio Modules on the xCOB
w/ RRH2x60-21 - GUI of the TIL
(continued)
NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol1; Ol2 and Ol3):

3 Double click on the OI4 GUI connected with the Radio Modules on the xCOB
GUI of the TIL

NOTE: The following TIL GUI appears for each CPRI link connected (here to
be done for Ol4; Ol5 and Ol6):

OR

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 431 24 Cells and 12 Antenna Pairs Procedures

Proc 7: Configuration Type: Dual Band with RRH2x -

Visual Check Procedure, Continued

Visual Check
Procedure -
Step Action
Configuration
type Dual Band 4 Check that the 24 Cells and 12 antenna Pairs are clearly identified in all use
w/ RRH2x60-21 - cases of radio configuration with the TIL GUI.
(continued)
If TIL GUI ... Then ...
Does not identify the 24 cells and 12 Contact the support team to
antenna pairs in all use cases of troubleshoot the issue.
radio configuration.
Has clearly identified 24 cells and
12 antenna pairs in all use cases of The radio configuration is compliant
radio configuration. with the expected final Node B
configuration

5 Right click on the GUI to select Return to main GUI on the pop-up menu of
Radio Modules view

NOTE: Once compliancy of configuration at site with 24 cells and 12 antenna pairs is confirmed
the following further steps need to happen to complete the feature activation
finalize the Node B commissioning testing by use of IEH521 - 310
finalize the Node B Integration testing by use of IEH521 - 410
Fill the Test records with the identified Radio Configuration.

38 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 432

December 15, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Hosting 2 Node Bs WCDMA in one d4U Procedures

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation access ...................................................................................... 5
Applicable IEH 521 sections ................................................................................ 5
Applicable documents in LR13.x .......................................................................... 6
Tool Requirements .............................................................................................. 7
General ........................................................................................................ 7
Hardware Tool ................................................................................................ 7
Software Tool ................................................................................................. 7
Dual Node B WCDMA in one d4U Flow ....................................................................... 8
Dual Node B WCDMA in one d4U flow diagram .......................................................... 8
Dual Node B WCDMA in one d4U Procedure Overview .................................................... 9
Reference Dual Node B in d4U Configuration Procedures Mandatory ............................. 9
Dual Node B WCDMA in one d4U Checklists ............................................................... 10
Purpose ...................................................................................................... 10
Checklist Customization .................................................................................. 10
Remote Operations Checklist ............................................................................ 11
Dual Node B WCDMA in one d4U Parameter Forms .................................................... 12
General ...................................................................................................... 12
Node B Parameters Required prior to Dual Node B Configuration ................................. 12
Node B BTS Parameters ................................................................................... 13
Node B Backhaul Parameters ............................................................................ 13
Node B Ethernet Parameters ............................................................................. 14
Node B IP Parameters ..................................................................................... 14
Dual NodeBs Parameters .................................................................................. 15
Hosting 2 Node Bs WCDMA in one d4U Preparation...................................................... 16
Description .................................................................................................. 16
Preconditions ............................................................................................... 16

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Basic Engineering Rules ................................................................................... 16

Dual Node B: Modules Location Description ........................................................... 17
Dual Node B naming conventions ...................................................................... 17
Dual Node B CEM board engineering rules ........................................................... 18
Dual Node B CEM-U Basic configuration rules ..................................................... 18
Modem slot Assignment Parameter configuration rules ........................................... 19
Controller slot Assignment Parameter - configuration rules ....................................... 20
Proc 1: Dual Node B in one d4U: BTS Parameter Setting Procedure ................................. 21
Description .................................................................................................. 21
Preconditions ............................................................................................... 21
BTS Setting .................................................................................................. 22
Parameters Procedure Dual Node B Mode ........................................................... 22
Proc 2: Dual Node B in one d4U: 2NodeBs Parameter Setting Procedure ........................... 26
Description .................................................................................................. 26
Preconditions ............................................................................................... 26
2NodeBs Setting Parameters Procedure - Dual Node B Mode ...................................... 26
Dual Node B Configuration Selection ...................................................................... 29
Description .................................................................................................. 29
Dual Node B configuration assignment rules .......................................................... 29
Proc 3: Dual Node B - Configuration 1 Procedure ....................................................... 30
Description .................................................................................................. 30
Preconditions ............................................................................................... 30
Dual Node B Configuration 1 Description Case 1 .................................................. 30
Dual Node B Configuration 1 Description Case 2 .................................................. 31
Dual Node B Configuration 1 Description Case 3 .................................................. 31
Configuration 1 Procedure Dual Node B .............................................................. 32
Proc 4: Dual Node B - Configuration 2 Procedure ....................................................... 36
Description .................................................................................................. 36
Preconditions ............................................................................................... 36
Dual Node B Configuration 2 Description ............................................................ 36
Configuration 2 Procedure - Dual Node B .............................................................. 37
Proc 5: Dual Node B - Configuration 3 Procedure ....................................................... 41
Description .................................................................................................. 41
Preconditions ............................................................................................... 41
Dual Node B Configuration 3 Description ............................................................ 41
Configuration 3 Procedure - Dual Node B .............................................................. 42
Proc 6: Final Field Operation Procedure .................................................................. 46
Description .................................................................................................. 46
Preconditions ............................................................................................... 46
Final Field Operation Procedure ........................................................................ 46
Proc 7: Dual NodeB #1 Configuration Final Check Procedure.......................................... 47
Description .................................................................................................. 47
Preconditions ............................................................................................... 47
Dual NodeB #1 Configuration Final Check Procedure ................................................ 47
Proc 8: Dual NodeB #2 Configuration Final Check Procedure.......................................... 51
Description .................................................................................................. 51
Preconditions ............................................................................................... 51
Dual NodeB #2 Configuration Final Check Procedure ................................................ 51
Record Sheets / Checklists - On Site ....................................................................... 55
Description .................................................................................................. 55
Report Sheet - Node B: Frequency Band ............................................................... 55

2 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Report Sheet - Radio Module Equipment............................................................... 55

Report Sheet - Inventories Equipment ................................................................. 56
Report Sheet - IP Parameters ............................................................................ 57
Report Sheet - 2NodeBs Parameters .................................................................... 57
Sign-Off Sheet .................................................................................................. 58
Description .................................................................................................. 58
Meaning of Sign-Off Sheet ................................................................................ 58
Sign-Off Sheet .............................................................................................. 58
Archiving of Reports ....................................................................................... 58
List of Figures

Figure 1: Hosting 2 Node Bs WCDMA in one d4U: Flow diagram................................................... 8

Figure 2: Dual NodeB in one d4U: Modules Location .............................................................. 17

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Commissioning Tests ............................... 5
Table 2: Applicable IEH 521 Sections for WCDMA Node B Integration Tests .................................... 5
Table 3: Applicable Methods Documents LR13.x for IEH521 ....................................................... 6
Table 4: Hardware Tools ................................................................................................. 7
Table 5: Software Tools .................................................................................................. 7
Table 6: Operational Procedures for Dual Node B in d4U Configuration ........................................ 9
Table 7: Sequence of Operations Used for Dual Node B Configuration ........................................ 11
Table 8: Node B Parameters Required Prior to dual Node B Commissioning.................................. 12
Table 9: Node B BTS Parameters ..................................................................................... 13
Table 10: Node B Backhaul Parameters ............................................................................. 13
Table 11: Node B Ethernet Parameters.............................................................................. 14
Table 12: Node B IP Parameters ...................................................................................... 14
Table 13: DualNodeBsParameters .................................................................................... 15
Table 14: Configuration Rules of Modem Slot Assignment Parameter ......................................... 19
Table 15: Configuration Rules of Controller Slot Assignment Parameter...................................... 20
Table 16: UMTS Frequency Band...................................................................................... 55
Table 17: Radio Module Equipment .................................................................................. 55
Table 18: Inventories Parameters .................................................................................... 56
Table 19: IP Parameters ................................................................................................ 57
Table 20: 2NodeBs Parameters ....................................................................................... 57
Table 21: Dual Node Bs inside one d4U Checklists Customer Sign-off ....................................... 58

December 15, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

General

Section This section provides detailed information about the individual procedures for commissioning
Description tests of a WCDMA Node B for the hosting of two Node B in one d4U
Preconditions
Inputs
Outputs
Additional details
Link to commissioning methods document where the procedure is contained

Previous Release New creation

Date

Release Notes New creation: December 2013 under utilization of existing IM documents for LR13.1.

4 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
WCDMA Node B commissioning tests.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required for WCDMA Node B commissioning tests.
521 sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B

Commissioning Tests

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
310 Node B Commissioning Testing
399 Node B Commissioning Test Records

Table 2: Applicable IEH 521 Sections for WCDMA Node B Integration

Tests

Section Description
401 Integration Planning
402 Integration into existing UTRAN
410 Integration Testing
499 Node B Integration Test Records
705 Single to Dual Node B Migration Procedures

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

References, Continued

Applicable The following methods documents are required to perform the Node B commissioning and
documents in integration in LR13.x
LR13.x

Table 3: Applicable Methods Documents LR13.x for IEH521

Doc Number Doc Title URL
9YZ-04088- Alcatel-Lucent Node B http://cic.us.alcatel-
0095-RJZZA Commissioning Procedure lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=55054&prc=Unknown
9YZ-04088- Alcatel-Lucent Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault lucent.com/cgi-
Management User Manual: TIL bin/design2006/dbaccessprototyp
e1/01?key=55050&prc=Unknown
9YZ-04088- Alcatel-Lucent Node B Integration in http://cic.us.alcatel-
0098-RJZZA an existing UTRAN lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=55057&prc=Unknown
9YZ-04088- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
0014-PCZZA Management System User Guide lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=54991&prc=Unknown
9YZ-04088- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
0015-TQZZA Management System - Security lucent.com/cgi-
Fundamentals bin/design2006/dbaccessprototyp
e1/01?key=54992&prc=Unknown

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

6 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Tool Requirements

General This section describes the hardware and software tools required to perform the commissioning
method.

Hardware Tool The hardware tools listed in the following table are required to perform the commissioning test.

Table 4: Hardware Tools

Hardware Tool Quantity Description
Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

Software Tool The software tool listed in the following table are required to perform the commissioning test

Table 5: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with
WIN7)

December 15, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Dual Node B WCDMA in one d4U Flow

Dual Node B The flow diagram below outlines the steps for the Dual Node B WCDMA configuration in the
WCDMA in one same d4U.
d4U flow
diagram
Figure 1: Hosting 2 Node Bs WCDMA in one d4U: Flow diagram

8 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Dual Node B WCDMA in one d4U Procedure

Overview

Reference Dual The following table lists all operational procedures of Dual Node B WCDMA configuration in
Node B in d4U the same d4U.
Configuration
Procedures
Mandatory Table 6: Operational Procedures for Dual Node B in d4U Configuration

Step Operation Opt/ Proc. Remark

Mand.
1 Hosting 2 Node Bs WCDMA M Prepara-
in one d4U Preparation tion
2 Dual Node B in one d4U: M Proc. 1
BTS Parameter Setting
Procedure
3 Dual Node B in one d4U: M Proc. 2
2NodeBs Parameter Setting
Procedure
4 Dual Node B - Configuration O Proc. 3 If Configuration 1
1 Procedure required
5 Dual Node B - Configuration O Proc. 4 If Configuration 2
2 Procedure required
6 Dual Node B - Configuration O Proc. 5 If Configuration 3
3 Procedure required
7 Final Field Operation M Proc. 6
Procedure
8 Dual NodeB #1 Configuration M Proc. 7
Final Check Procedure
9 Dual NodeB #2 Configuration M Proc. 8
Final Check Procedure

December 15, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Dual Node B WCDMA in one d4U Checklists

Purpose Checklists are available to support and document the flow of operations before, during and post
Dual Node B WCDMA configuration in the same d4U for
On site activities
Node B parameters
Remote (TIL) operations
and document successful completion of Dual Node B WCDMA configuration in the same d4U
by customer acceptance

Checklist The checklists of IEH521 are generic and can be used as basis for further modifications and
Customization enhancements as per specific customer / market requirements.

Continued on next page

10 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Dual Node B WCDMA in one d4U Checklists, Continued

Remote Sequence of operations for use by remote operations to verify success of mandatory and
Operations optional steps
Checklist

Table 7: Sequence of Operations Used for Dual Node B Configuration

Procedure Condition Expected result To OK NOK

use?
Hosting 2 Node Bs WCDMA in Mandatory The preconditions of Node B #1
one d4U Preparation in one d4U are fulfilled. Y/N
The field operations are selected.
Proc 1: Dual Node B in one Mandatory The BTS Parameter (split mode)
d4U: BTS Parameter Setting is configured and both CCM #A Y/N
Procedure and CCM #B are in dual mode.
Proc 2: Dual Node B in one Mandatory The 2NodeBs Parameters
d4U: 2NodeBs Parameter (Serialization Number Partner
Y/N
Setting Procedure and the Modem CEM slot
assignment) are configured.
Proc 3: Dual Node B - If Configuration 1 The 2 Node Bs are configured
Configuration 1 Procedure required according to the configuration
Y/N
type 1 with their own modem
CEM slot assigned.
Proc 4: Dual Node B - If Configuration 2 The 2 Node Bs are configured
Configuration 2 Procedure required according to the configuration
Y/N
type 2 with their own modem
CEM slot assigned.
Proc 5: Dual Node B - If Configuration 3 The 2 Node Bs are configured
Configuration 3 Procedure required according to the configuration
Y/N
type 3 with their own modem
CEM slot assigned.
Proc 6: Final Field Operation Mandatory The last field operations
Procedure procedure are completed here:
Node B commissioning,
Y/N
Sending I&C Parameters to the
NodeB and Node B activation
Single to dual Node B migration
Proc 7: Dual NodeB #1 Mandatory The dual Node B #1 is compliant
Configuration Final Check with the expected final Y/N
Procedure configuration
Proc 8: Dual NodeB #2 Mandatory The dual Node B #2 is compliant
Configuration Final Check with the expected final Y/N
Procedure configuration

December 15, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Dual Node B WCDMA in one d4U Parameter Forms

General This section provides several forms to capture the parameters to perform the Dual Node B
WCDMA configuration of the Node B #1 and Node B #2 in the same d4U.
The forms of parameters are based on the CIQ and must be documented by the coordinator
according to the expected parameters and configuration prior to the work.
The forms of parameters must be sent by email or must be available on a link.

Node B The following table is the list of dual Node B parameters required prior to commissioning the
Parameters d4U in Dual Node B (Node B #1 and Node B #2).
Required prior
to Dual Node B
Configuration Table 8: Node B Parameters Required Prior to dual Node B
Commissioning

Node B parameter Value for Node B #1 Value for Node B #2

CCM #A CCM #B
Node B IP address
Configuration
Sub-network mask
Software upgrade on Node B: Yes / No Yes / No
Node B - Software version (LR13.1 minimum) (LR13.1 minimum)
Hardware reference
BTS Parameters: dBTS 4U-V3 dBTS 4U-V3

Continued on next page

12 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Dual Node B WCDMA in one d4U Parameter Forms,

Continued

Node B BTS The following Node B BTS parameters are required prior to commissioning the d4U in Dual
Parameters Node B

Table 9: Node B BTS Parameters

Node B BTS parameters Value for Node B #1 Value for Node B #2
CCM #A CCM #B
BTS mode SingleMode SingleMode
(New parameter in LR13.1) SplitMode SplitMode
BTS Packaging (based on d4U) dBTS 4U-V3 dBTS 4U-V3
Fallback to previous I&C data Activate Activate
Deactivate Deactivate
GPS synchronization Activate Activate
Deactivate Deactivate
Ru Name:
Pec Code:
Serial Number:
Serialization Number of
Partner:
Manufacturing Date:

Node B The following Node B Backhaul parameters are required prior to commissioning the d4U in
Backhaul Dual Node B
Parameters NOTE: Hybrid Iub or full IP backhaul only are allowed

Table 10: Node B Backhaul Parameters

Node B Backhaul Value for Node B #1 Value for Node B #2
parameters CCM #A CCM #B
Type of Incoming Link Fast Ethernet Fast Ethernet
Gigabit Ethernet Gigabit Ethernet

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Dual Node B WCDMA in one d4U Parameter Forms,

Continued

Node B The following Node B Ethernet parameters are required prior to commissioning the d4U in
Ethernet Dual Node B
Parameters

Table 11: Node B Ethernet Parameters

Node B Ethernet Value for Node B #1 Value for Node B #2
parameters CCM #A CCM #B
VLAN ID 0 (Do not change) 0 (Do not change)
VLAN TAGGING Disabled Disabled
Enabled to use Enabled to use
LAG / HUBBING used (Do not change) (Do not change)
Eth Port used for iub IF (Do not change) (Do not change)
Eth Port used for Hubbing (Do not change) (Do not change)

Node B IP The following Node B IP parameters are required prior to commissioning the d4U in Dual
Parameters Node B.

Table 12: Node B IP Parameters

Node B IP parameters Value for Node B #1 Value for Node B #2
CCM #A CCM #B
Existence of a DHCP server No No
Yes Yes
BTS IP Address IP@: __.__.__.__ IP@: __.__.__.__
OMC-B IP Address IP@: __.__.__.__ IP@: __.__.__.__
OMC-B port 6301 6301
Sub-network mask 255.255.255.0 255.255.255.0
BTS port 6301 6301
Default Gateway Ip Address (Do not change the value) (Do not change the value)

Continued on next page

14 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Dual Node B WCDMA in one d4U Parameter Forms,

Continued

Dual NodeBs The following Node B 2NodeBs parameters are required prior to commissioning the d4U in
Parameters Dual Node B.
NOTE: New parameters in LR13.1

Table 13: DualNodeBsParameters

Node B dualNodeBs
parameters Value for Node B #1 Value for Node B #2
CCM #A CCM #B
Parameter name:
SerializationNumberOfPartner
Modem Slot Array: Assignment for NodeB#1 Assignment for NodeB#2
Physical Slot 1 (CEM #1) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 2 (CEM #2) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 3 (CEM #3) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 4 (CCM #B) NB#2
Physical Slot 5 (CCM #A) NB#1
Physical Slot 6 (CEM #4) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 7 (CEM #5) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 8 (CEM #6) Unassigned / Self /Partner Unassigned / Self /Partner

December 15, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Hosting 2 Node Bs WCDMA in one d4U Preparation

Description This procedure describes the way to set all parameters to host 2 Node Bs inside one d4U.
This configuration will be used to increase the capacity of d4U sites.

Preconditions The following preconditions must be met

Only one Node B is already fully Integrated in one d4U (Single Mode) .
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.
The modem slot assignment parameters value must be available

Basic Engineering rules to support the dual Node B configuration in d4U:

Engineering
Rules

DO NOT: Do not use xCCM-u controller in a dual Node B configuration.

The modems eCEM-U and / or xCEM-U can be used.

The two eCCM-U controllers must be equipped with GigE MDA mandatory.
The two eCCM-U controllers will be hosting their own Iub backhaul termination.
The two eCCM-U controllers will be hosting their own CPRI interfaces towards the REs
(TRDU or RRH or MCTRX).
Hybrid Iub and Full IP backhaul are allowed

Continued on next page

16 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Hosting 2 Node Bs WCDMA in one d4U Preparation,

Continued

Dual Node B: The following description gives the Dual Node B Modules location into the same d4U.
Modules
Location
Description Figure 2: Dual NodeB in one d4U: Modules Location

Dual Node B
naming
conventions
IMPORTANT: Naming conventions, used for the procedures:
NodeB 1 takes into account the CCM-U with naming CCM #A and will support 3G only
NodeB 2 takes into account the CCM-U with naming CCM #B and will support 3G or future
technology.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Hosting 2 Node Bs WCDMA in one d4U Preparation,

Continued

Dual Node B
CEM board
engineering
rules IMPORTANT: CEM-U board location inside the d4U cabinet is dependent on
eCCM-U slot, configuration used and board engineering.

When Modem CEM is inserted in Then CEMs can be used by ...

...
Physical Slot #1, #2 ,#3 The dual Node B #1 and Node B #2
(respectively managed by the CCM #A or
CCM #B) ) (link blue and red)
CCM#A can manage up to 5 CEM
CCM#B can manage up to 3 CEM
(Dual NodeB can have up to 6 CEM)

Physical Slot #6, #7, #8 The Node B #1 only

(managed by the CCM #A) (link red)

Dual Node B
CEM-U Basic
configuration
rules IMPORTANT: A CEM-U can only be configured for one Node B.

Example:
If one CEM (Slot #1, #2, #3) is already configured with one Node B #1 (managed by CCM #A)
then it cannot be configured by the other Node B #2 (managed by CCM #B).

IMPORTANT: Configuration of CEM-U for dual Node B operation is dependent on

software load.

Continued on next page

18 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Hosting 2 Node Bs WCDMA in one d4U Preparation,

Continued

Dual Node B
CEM-U Basic Apply following rules when modem CEM used with load < LR13.1W inserted in a Node B
configuration running with >= LR13.1 load with CCM-U #B.
rules (continued)

If Modem CEM is introduced... Then Modem CEM...

in UA8.1.3 (load UNB08D120C0) Wont be able to work with CCM #B
between UA8.1.3 to LR13.1 Cant be upgraded by CCM #B.
Shall be upgraded to LR13.1 load with
CCM #A before using with CCM #B.

Modem slot The following table describes the configuration rules of Modem Slot Assignment parameter
Assignment according to the CCM connected to the TIL.
Parameter
configuration
rules Table 14: Configuration Rules of Modem Slot Assignment Parameter
If module is... Then drop-down menu for Modem
Slot assignment appears ...
Modem Physical Node B From CCM #A From CCM #B
slot (TIL GUI) (TIL GUI)
CEM1 #1 #1 or #2 Self or
CEM2 #2 #1 or #2 Partner or
CEM3 #3 #1 or #2 Unassigned

CEM4 #6 #1
Self or Partner or
CEM5 #7 #1
Unassigned Unassigned
CEM6 #8 #1

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Hosting 2 Node Bs WCDMA in one d4U Preparation,

Continued

Controller slot The following table describes the configuration rules of the Controller Slot Assignment
Assignment Parameter.
Parameter - NOTE: Assignment cannot be changed on the CCM with TIL. The modem slot assignment
configuration parameter is automatically assigned by default according to the TIL connection.
rules

Table 15: Configuration Rules of Controller Slot Assignment Parameter

If TIL connected on ... Then controller assignment parameters
Module Physical Slot
value is ...

CCM #A #5
(this CCM When ... Then modem slot
manages assignment is by
NodeB #1) default as...
CCM #A used in Single
Self
Mode
CCM #A used in Dual Mode Self
CCM #A removed Unassigned
CCM #B used in Dual Mode Partner
CCM #B used in Single
Unassigned
Mode
CCM #B Remove Unassigned

CCM #B #4
(This CCM When ... Then modem slot
manages assignment is by
NodeB #2) default as...
CCM #A used in Single
Unassigned
Mode
CCM #A used in Dual Mode Partner
CCM #A removed Unassigned
CCM #B used in Dual Mode Self
CCM #B used in Single
Self
Mode
CCM #B Remove Unassigned

20 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 1: Dual Node B in one d4U: BTS Parameter

Setting Procedure

Description This procedure describes the way to set BTS parameters to host 2 Node Bs inside one d4U.
NOTE: The TIL GUI (from LR13.1 version) has a new BTS mode parameter which must be
set in the BTS tab. The BTS mode parameter allows CCM-U resources to manage the dual
NodeB mode in the same d4U.

Preconditions The following preconditions must be met

Hosting 2 Node Bs WCDMA in one d4U Preparation must be completed
Only one Node B is already fully Integrated in one d4U (Single Mode)
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 1: Dual Node B in one d4U: BTS Parameter

Setting Procedure, Continued

BTS Setting The following procedure describes how to configure BTS parameters in dual Node B mode in
Parameters d4U.
Procedure
Dual Node B
Mode NOTE: The laptop setting and TIL connections must be done alternatively on each CCM and
carried out for each CCM:

CCM #A to complete the dual mode of the Node B #1 configuration and

CCM #B to complete the dual mode of the Node B #2 configuration.

Step Action
1 Select the TIL connection according to the Node B to configure in dual Node
B:

If need to configure ... Then Connect the TIL ...

The Node B #1 of the d4U On the CCM #A
Go to the step 2
The Node B #2 of the same d4U On the CCM #B
Go to the step 3

Continued on next page

22 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 1: Dual Node B in one d4U: BTS Parameter

Setting Procedure, Continued

Parameters
Procedure Dual
Step Action
Node B Mode
(continued) 2 Connect the TIL on the CCM #A from Node B #1:

NOTE: Wait less than one minute before to see CEM modules in the TIL GUI.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 1: Dual Node B in one d4U: BTS Parameter

Setting Procedure, Continued

Parameters
Procedure Dual
Step Action
Node B Mode
(continued) 3 Connect the TIL on the CCM #B from Node B #2:

NOTE: Wait less than one minute before to see CEM modules in the TIL GUI.

4 Select I&C menu from the TIL GUI

5 Select Change I&C parameters

Continued on next page

24 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 1: Dual Node B in one d4U: BTS Parameter

Setting Procedure, Continued

Parameters
Procedure Dual
Step Action
Node B Mode
(continued) 6 Select BTS tab for a dual Node B Configuration

7 Select the BTS Mode parameter as SplitMode.

Result: The CCM#A or CCM #B is now in dual mode
8 Press the Send to BTS button only after completion of all parameters setting
in all relevant tabs.

NOTE: Refer to IEH521 section 302 commissioning Procedure to complete

the commissioning if necessary

December 15, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 2: Dual Node B in one d4U: 2NodeBs

Parameter Setting Procedure

Description This procedure describes the way to set 2NodeBs parameters to host 2 Node Bs inside one
d4U.

Preconditions The following preconditions must be met

The BTS parameter setting is already completed.
Only one Node B is already fully Integrated in one d4U (Split Mode).
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.
The Serialization Number of Partner value must be available.

2NodeBs The following procedure describes how to configure 2NodeBs parameters in dual Node B
Setting mode in d4U.
Parameters
Procedure -
Dual Node B NOTE: The laptop setting and TIL connections must be done alternatively on each CCM and
executed for each CCM:
Mode
CCM #A to complete the dual mode of the Node B #1 configuration and
CCM #B to complete the dual mode of the Node B #2 configuration.

Step Action
1 Connect the TIL on the CCM #A from Node #1 /
Connect the TIL on the CCM #B from Node #2
2 Select I&C Menu from TIL GUI

NOTE: TIL GUI is connected to CCM #A

3 Select Change I&C Parameters from menu tab

Continued on next page

26 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 2: Dual Node B in one d4U: 2NodeBs

Parameter Setting Procedure, Continued

2NodeBs Setting
Parameters
Step Action
Procedure - Dual
Node B Mode 4 Select 2NodeBs from menu tab
(continued)

5 Fill the Serialization Number of Partner value (NEID partner Parameter

available into CIQ with 6 digits like for example: 598461 ) in the list of
parameter value

NOTE: The parameter SerializationNumberOfPartner indicates the NEID of

the partner Node B #2 and must be unique into customer Network.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 2: Dual Node B in one d4U: 2NodeBs

Parameter Setting Procedure, Continued

2NodeBs Setting
Parameters
Step Action
Procedure - Dual
Node B Mode 6 Check in the drop-down menu of Modem Slot Assignment for the Modem
(continued) CEM slot assignment by Node B

NOTE: The Modem Slot Array indicates the modem assignment to the NodeB.

7 Set modem slot assignment parameter for each CEM and for each NodeB
by selecting from drop down menu.

NOTE: Consider Modem slot assignment rules and Modem slot

Assignment Parameter configuration rules when setting the assignment.

28 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Dual Node B Configuration Selection

Description It is necessary to decide which of the Dual Node B configuration needs to be configured to
identify the procedure needed.

NOTE: Dependent on engineering requirements a wide variety of different modem slot

assignments of CEM-U boards to Node B #1 / Node B #2 is possible.

Dual Node B The following table describes the modem slot assignment rules mapped to configuration case.
configuration
assignment rules
NOTE: Analysis must be made which Dual Node B configuration is available to select the Dual
Node B configuration procedure to continue.

If Initial single Node B Then set parameters

configuration is ... according to
Procedure ...
Configuration 1: Proc 3: Dual Node B -
1 Controller (CCM #A) + Configuration 1 Procedure
First Use Case
3 Modems (with CEM #4, #5 and #6); or
Second Use Case
2 Modems (with CEM #4 and #5); or
Third Use Case
1 Modems (with CEM #4);
Configuration 2: Proc 4: Dual Node B -
1 Controller (CCM #A) Configuration 2 Procedure
4 Modems (with CEM #1, #4, #5, #6);
Configuration 3: Proc 5: Dual Node B -
1 Controller (CCM #A) Configuration 3 Procedure
5 Modems (with CEM #1, #2, #4, #5, #6);

December 15, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 3: Dual Node B - Configuration 1 Procedure

Description This procedure describes the way to configure the dual Node B in one d4U for Dual Node B
configuration 1.

Preconditions The following preconditions must be met

Dual Node B is identified as Dual Node B configuration 1
The BTS parameter and the 2NodeBs parameter setting procedures are already
completed.
Only one Node B is already fully Integrated in one d4U (Split Mode) .
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.
The modem slot assignment parameters value must be available in the CIQ.

Dual Node B The D4U is configured to support dual Node B with the same hardware configuration: 1 x CCM
Configuration 1 + 3 x CEM per Node B.
Description
Case 1
Single Node B configuration Dual Node B configuration
before conversion
1 Controller (CCM #A) 1 Controller (CCM #A)
3 Modems (with CEM #4, #5 and #6); 3 Modems (with CEM #4, #5 and #6);

1 Controller (adding CCM #B)

3 Modems (adding CEM#1, #2 and #3)

Continued on next page

30 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 3: Dual Node B - Configuration 1 Procedure,

Continued

Dual Node B The D4U is configured to support dual Node B with the Node B#1 with 1 CCM and 2 CEM,
Configuration 1 Node B #2 with 1 x CCM + 3 x CEM.
Description
Case 2
Single Node B configuration Dual Node B configuration
before conversion
1 Controller (CCM #A) 1 Controller (CCM #A)
2 Modems (with CEM #4 and #5) 3 Modems (with CEM #4, #5)

1 Controller (adding CCM #B)

3 Modems (adding CEM#1, #2 and #3)

Dual Node B The D4U is configured to support dual Node B with the Node B#1 with 1 CCM and 1 CEM ,
Configuration 1 Node B #2 with 1 x CCM + 3 x CEM.
Description
Case 3
Single Node B configuration Dual Node B configuration
before conversion
1 Controller (CCM #A) 1 Controller (CCM #A)
2 Modems (with CEM #4) 3 Modems (with CEM #4)

1 Controller (adding CCM #B)

3 Modems (adding CEM#1, #2 and #3)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 3: Dual Node B - Configuration 1 Procedure,

Continued

Configuration 1 The following table describes how to configure the Dual Node B configuration 1
Procedure
Dual Node B
NOTE: TIL has to be connected first to CCM-U #A. TIL has to be moved to CCM-U #B after
configuration of CCM-U #A is finished.

Step Action
1 Bring TIL GUI for CCM-U #A into the 2 Node B menu by selecting I&C |
Change I&C Parameters | 2NodeBs

Continued on next page

32 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 3: Dual Node B - Configuration 1 Procedure,

Continued

Configuration 1
Procedure Dual
Step Action
Node B
(continued) 2 Set the Modem Slot Assignment for CCM #A as per following Node B
parameters table

If this module is ... Then change modem slot

assignment parameters ...
Module Physical Node B From CCM #A in To CCM #A in
Slot Single Mode Dual mode
CEM 1 #1 #2 Unassigned Partner
CEM 2 #2 #2 Unassigned Partner
CEM 3 #3 #2 Unassigned Partner
CCM B #4 #2 Unassigned Partner
CCM A (<) #5 #1 Self Self
CEM 4 #6 #1 Self Self
CEM 5 #7 #1 Self Self
CEM 6 #8 #1 Self Self

NOTE: The color of cells is used to assign modules with NodeB in all tables
and figures:
The cells in purple color are assigned to NodeB #2
The cells in green color are assigned to NodeB #1

NOTE: Modem Slot Assignment for CCM cannot be changed by TIL GUI. The
modem slot assignment parameter for CCM (Grey cell) is automatically
assigned by default according to the TIL connection.

IMPORTANT: If modem board slot is empty (filler) then select the

Modem slot Assignment parameter as Unassigned.
3 Connect TIL to CCM #B

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 3: Dual Node B - Configuration 1 Procedure,

Continued

Configuration 1
Procedure Dual
Step Action
Node B
(continued) 4 Bring TIL GUI for CCM-U #B into the 2 Node B menu by selecting I&C |
Change I&C Parameters | 2NodeBs

Continued on next page

34 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 3: Dual Node B - Configuration 1 Procedure,

Continued

Configuration 1
Procedure Dual
Step Action
Node B
(continued) 5 Set the Modem Slot Assignment for CCM #B as per following Node B
parameters table

If this module is ... Then change modem slot

assignment parameters ...
Module Physical Node B From CCM #B in To CCM #B in
Slot Single Mode Dual mode
CEM 1 #1 #2 Unassigned Self
CEM 2 #2 #2 Unassigned Self
CEM 3 #3 #2 Unassigned Self
CCM B (<) #4 #2 Unassigned Self
CCM A #5 #1 Unassigned Unassigned
CEM 4 #6 #1 Self Partner
CEM 5 #7 #1 Self Partner
CEM 6 #8 #1 Self Partner

NOTE: The color of cells is used to assign modules with NodeB in all tables
and figures:
The cells in purple color are assigned to NodeB #2
The cells in green color are assigned to NodeB #1

NOTE: Modem Slot Assignment for CCM cannot be changed by TIL GUI. The
modem slot assignment parameter for CCM (Grey cell) is automatically
assigned by default according to the TIL connection.

IMPORTANT: If modem board slot is empty (filler) then select the

Modem slot Assignment parameter as Unassigned.

December 15, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 4: Dual Node B - Configuration 2 Procedure

Description This procedure describes the way to configure the dual Node B in one d4U for Dual Node B
configuration 2.

Preconditions The following preconditions must be met

Dual Node B is identified as Dual Node B configuration 2
The BTS parameter and the 2NodeBs parameter setting procedures are already
completed.
Only one Node B is already fully Integrated in one d4U (Split Mode) .
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.
The modem slot assignment parameters value must be available in the CIQ.

Dual Node B The D4U is configured to support 2 Node Bs in the following configuration:
Configuration 2
The first Node B needs 4 modem slots (CEM: #1, #4, #5 & #6);
Description
The second Node B can access 2 modem slots (CEM #2 and #3)

Single Node B configuration Dual Node B configuration

before conversion
1 Controller (CCM #A) 1 Controller (CCM #A)
4 Modems (with CEM #1, #4, #5, #6) 4 Modems (with CEM #1, #4, #5, #6)

1 Controller (adding CCM #B)

2 Modems (adding CEM #2 and #3)

Continued on next page

36 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 4: Dual Node B - Configuration 2 Procedure,

Continued

Configuration 2 The following table describes how to configure the Dual Node B configuration 2
Procedure -
Dual Node B
NOTE: TIL has to be connected first to CCM-U #A. TIL has to be moved to CCM-U #B after
configuration of CCM-U #A is finished.

Step Action
1 Bring TIL GUI for CCM-U #A into the 2 Node B menu by selecting I&C |
Change I&C Parameters | 2NodeBs

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 4: Dual Node B - Configuration 2 Procedure,

Continued

Configuration 2
Procedure - Dual
Step Action
Node B
(continued) 2 Set the Modem Slot Assignment for CCM #A as per following Node B
parameters table

If this module is ... Then change modem slot

assignment parameters ...
Module Physical Node B From CCM #A in To CCM #A in
Slot Single Mode Dual mode
CEM 1 #1 #1 Self Self
CEM 2 #2 #2 Unassigned Partner
CEM 3 #3 #2 Unassigned Partner
CCM B #4 #2 Unassigned Partner
CCM A (<) #5 #1 Self Self
CEM 4 #6 #1 Self Self
CEM 5 #7 #1 Self Self
CEM 6 #8 #1 Self Self

NOTE: The color of cells is used to assign modules with NodeB in all tables
and figures:
The cells in purple color are assigned to NodeB #2
The cells in green color are assigned to NodeB #1

NOTE: Modem Slot Assignment for CCM cannot be changed by TIL GUI. The
modem slot assignment parameter for CCM (Grey cell) is automatically
assigned by default according to the TIL connection.

IMPORTANT: If modem board slot is empty (filler) then select the

Modem slot Assignment parameter as Unassigned.
3 Connect TIL to CCM #B

Continued on next page

38 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 4: Dual Node B - Configuration 2 Procedure,

Continued

Configuration 2
Procedure - Dual
Step Action
Node B
(continued) 4 Bring TIL GUI for CCM-U #B into the 2 Node B menu by selecting I&C |
Change I&C Parameters | 2NodeBs

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 4: Dual Node B - Configuration 2 Procedure,

Continued

Configuration 2
Procedure - Dual
Step Action
Node B
(continued) 5 Set the Modem Slot Assignment for CCM #B as per following Node B
parameters table

If this module is ... Then change modem slot

assignment parameters ...
Module Physical Node B From CCM #B in To CCM #B in
Slot Single Mode Dual mode
CEM 1 #1 #1 Self Partner
CEM 2 #2 #2 Unassigned Self
CEM 3 #3 #2 Unassigned Self
CCM B (<) #4 #2 Unassigned Self
CCM A #5 #1 Unassigned Unassigned
CEM 4 #6 #1 Self Partner
CEM 5 #7 #1 Self Partner
CEM 6 #8 #1 Self Partner

NOTE: The color of cells is used to assign modules with NodeB in all tables
and figures:
The cells in purple color are assigned to NodeB #2
The cells in green color are assigned to NodeB #1

NOTE: Modem Slot Assignment for CCM cannot be changed by TIL GUI. The
modem slot assignment parameter for CCM (Grey cell) is automatically
assigned by default according to the TIL connection.

IMPORTANT: If modem board slot is empty (filler) then select the

Modem slot Assignment parameter as Unassigned.

40 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 5: Dual Node B - Configuration 3 Procedure

Description This procedure describes the way to configure the dual Node B in one d4U for Dual Node B
configuration 3.

Preconditions The following preconditions must be met

Dual Node B is identified as Dual Node B configuration 3
The BTS parameter and the 2NodeBs parameter setting procedures are already
completed.
Only one Node B is already fully Integrated in one d4U (Split Mode) .
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.
The modem slot assignment parameters value must be available in the CIQ.

Dual Node B The D4U is configured to support 2 Node Bs in the following configuration:
Configuration 3
The first Node B needs 4 modem slots (CEM: #1, #2, #4, #5 & #6);
Description
The second Node B can access 1 modem (CEM #3)

Single Node B configuration Dual Node B configuration

before conversion
1 Controller (CCM #A) 1 Controller (CCM #A)
4 Modems (with CEM #1, #2, #4, #5, #6) 4 Modems (with CEM #1, #2, #4, #5, #6)

1 Controller (adding CCM #B)

2 Modems (adding CEM #3)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 5: Dual Node B - Configuration 3 Procedure,

Continued

Configuration 3 The following table describes how to configure the Dual Node B configuration 3
Procedure - NOTE: TIL has to be connected first to CCM-U #A. TIL has to be moved to CCM-U #B after
Dual Node B configuration of CCM-U #A is finished.

Step Action
1 Bring TIL GUI for CCM-U #A into the 2 Node B menu by selecting I&C |
Change I&C Parameters | 2NodeBs

Continued on next page

42 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 5: Dual Node B - Configuration 3 Procedure,

Continued

Configuration 3
Procedure - Dual
Step Action
Node B
(continued) 2 Set the Modem Slot Assignment for CCM #A as per following Node B
parameters table

If this module is ... Then change modem slot

assignment parameters ...
Module Physical Node B From CCM #A in To CCM #A in
Slot Single Mode Dual mode
CEM 1 #1 #1 Self Self
CEM 2 #2 #2 Self Self
CEM 3 #3 #2 Unassigned Partner
CCM B #4 #2 Unassigned Partner
CCM A (<) #5 #1 Self Self
CEM 4 #6 #1 Self Self
CEM 5 #7 #1 Self Self
CEM 6 #8 #1 Self Self

NOTE: The color of cells is used to assign modules with NodeB in all tables
and figures:
The cells in purple color are assigned to NodeB #2
The cells in green color are assigned to NodeB #1

NOTE: Modem Slot Assignment for CCM cannot be changed by TIL GUI. The
modem slot assignment parameter for CCM (Grey cell) is automatically
assigned by default according to the TIL connection.

IMPORTANT: If modem board slot is empty (filler) then select the

Modem slot Assignment parameter as Unassigned.
3 Connect TIL to CCM #B

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 5: Dual Node B - Configuration 3 Procedure,

Continued

Configuration 3
Procedure - Dual
Step Action
Node B
(continued) 4 Bring TIL GUI for CCM-U #B into the 2 Node B menu by selecting I&C |
Change I&C Parameters | 2NodeBs

Continued on next page

44 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 5: Dual Node B - Configuration 3 Procedure,

Continued

Configuration 3
Procedure - Dual
Step Action
Node B
(continued) 5 Set the Modem Slot Assignment for CCM #B as per following Node B
parameters table

If this module is ... Then change modem slot

assignment parameters ...
Module Physical Node B From CCM #B in To CCM #B in
Slot Single Mode Dual mode
CEM 1 #1 #1 Self Partner
CEM 2 #2 #2 Self Partner
CEM 3 #3 #2 Unassigned Self
CCM B (<) #4 #2 Unassigned Self
CCM A #5 #1 Unassigned Unassigned
CEM 4 #6 #1 Self Partner
CEM 5 #7 #1 Self Partner
CEM 6 #8 #1 Self Partner

NOTE: The color of cells is used to assign modules with NodeB in all tables
and figures:
The cells in purple color are assigned to NodeB #2
The cells in green color are assigned to NodeB #1

NOTE: Modem Slot Assignment for CCM cannot be changed by TIL GUI. The
modem slot assignment parameter for CCM (Grey cell) is automatically
assigned by default according to the TIL connection.

IMPORTANT: If modem board slot is empty (filler) then select the

Modem slot Assignment parameter as Unassigned.

December 15, 2013 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 6: Final Field Operation Procedure

Description This procedure describes the way to complete the field operation on the Dual NodeB
configuration inside one d4U.

Preconditions The following preconditions must be met

The BTS parameter and the 2NodeBs parameter setting procedures are already
completed.
The 2 Node Bs is already fully Integrated in one d4U (Split Mode) .
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available.

Final Field The following procedure describes how to activate the newly commissioned parameters inside
Operation the Dual Node B.
Procedure
NOTE: The procedure has to be executed for
Node B #1 (TIL connected to CCM-U #A)
Node B#2 (TIL connected to CCM-U #B)

Step Action
1 Connect TIL GUI with CCM

2 Check the commissioning parameters against CIQ and complete

commissioning task if required.

NOTE: All missing parameters must be fully completed now to avoid

performing several Node B reset.

NOTE: Use IEH521-302 as guideline for commissioning

3 Press the Send to BTS button after completion of all parameters setting in all
relevant tabs.

NOTE: Sending I&C Parameters to the Node B is described in IEH521-302

4 Perform reboot of the Node B by use of IEH521-302 Reset of Node B.

NOTE: The Node B comes up after reboot with the commissioned parameters.

46 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 7: Dual NodeB #1 Configuration Final Check

Procedure

Description This procedure describes the way to do a final check on the Dual NodeB #1 inside one d4U.
NOTE: The TIL GUI information is dependent on the CCM-U to which it is connected. It
displays the Modem board assignment for only this Node B.

Preconditions The following preconditions must be met

The BTS parameter and the 2NodeBs parameter setting procedures are already
completed.
Dual Node B is already fully Integrated in one d4U (Split Mode).
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available to CCM-U #A

Dual NodeB #1 The following procedure describes how to perform the final configuration checks for Node B
Configuration #1 inside the Dual Node B configuration.
Final Check
Procedure
Step Action
1 Connect TIL to CCM-U #A
2 Select I&C | Display I&C Parameters| BTS from TIL GUI
3 Check the Split Mode value for BTS Mode parameter is selected for dual
NodeB in d4U configuration

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 47

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 7: Dual NodeB #1 Configuration Final Check

Procedure, Continued

Dual NodeB #1
Configuration
Step Action
Final Check
Procedure 4 Select 2NodeBs and display the modem slot assignment values
(continued)

This example shows from display I&C parameters window: the modem slot
assignment of:
Slot1 CEM#1 is assigned as partner
Slot 2 CEM#2 is assigned as partner
Slot 3 CEM#3 is assigned as Self owner
Slot 6 CEM#4 is assigned as Self owner
Slot 7 CEM#5 is Unassigned
Slot 8 CEM#6 is Unassigned

Continued on next page

48 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 7: Dual NodeB #1 Configuration Final Check

Procedure, Continued

Dual NodeB #1
Configuration
Step Action
Final Check
Procedure 5 Compare Modem Slot Assignment values with physically present
(continued) configuration of the d4U (number of modems, slots).
Example:

When the module is ... Then modem slot assignment

parameters is ...
Module Physical Node B To CCM #A Slot Status
Slot in Dual mode
CEM 1 #1 #2 unassigned Empty
(in dark green)
CEM 2 #2 #2 Partner Used with CCM #B
CEM 3 #3 #1 Self Empty
(in light grey)
CCM B #4 #2 Partner Node B #2
CCM A (<) #5 #1 Self Node B #1
CEM 4 #6 #1 Self Used with CCM #A
CEM 5 #7 #1 Unassigned Occupied
(in dark grey)
CEM 6 #8 #1 Unassigned Empty
(in dark grey)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 49

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 7: Dual NodeB #1 Configuration Final Check

Procedure, Continued

Dual NodeB #1
Configuration NOTE: The d4U Node B #1 is working now in dual Mode with the modem configuration as
Final Check assigned.
Procedure
(continued)
NOTE: If there is a mismatch between the views of the CCM-U #A is not working in dual mode
then call for trouble shooting. Decide whether to downgrade to single configuration (IEH521
section 705 Proc4: Downgrade Procedure Dual to Single NodeB Mode)

50 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 8: Dual NodeB #2 Configuration Final Check

Procedure

Description This procedure describes the way to do a final check on the Dual NodeB #2 inside one d4U.
NOTE: The TIL GUI information is dependent on the CCM-U to which it is connected. It
displays the Modem board assignment for only this Node B.

Preconditions The following preconditions must be met

The BTS parameter and the 2NodeBs parameter setting procedures are already
completed.
Dual Node B is already fully Integrated in one d4U (Split Mode).
The 2 Node Bs WCDMA in one d4U feature must be activated
The minimum release software must be LR13.1.
The laptop setting and TIL connections are already done and available to CCM-U #B

Dual NodeB #2 The following procedure describes how to perform the final configuration checks for Node B
Configuration #2 inside the Dual Node B configuration.
Final Check
Procedure
Step Action
1 Connect TIL to CCM-U #B
2 Select I&C | Display I&C Parameters| BTS from TIL GUI
3 Check the Split Mode value for BTS Mode parameter is selected for dual
NodeB in d4U configuration

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 51

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 8: Dual NodeB #2 Configuration Final Check

Procedure, Continued

Dual NodeB #2
Configuration
Step Action
Final Check
Procedure 4 Select 2NodeBs and display the modem slot assignment values
(continued)

This example shows from display I&C parameters window, the modem slot
assignment of:
Slot1 CEM#1 is assigned as Self owner
Slot 2 CEM#2 is assigned as Self owner
Slot 3 CEM#3 is assigned to the partner Node B
Slot 6 CEM#4 is assigned to the partner Node B
Slot 7 CEM#5 is Unassigned
Slot 8 CEM#6 is Unassigned

Continued on next page

52 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Proc 8: Dual NodeB #2 Configuration Final Check

Procedure, Continued

Dual NodeB #2
Configuration
Step Action
Final Check
Procedure 5 Compare Modem Slot Assignment values with physically present
(continued) configuration of the d4U (number of modems, slots).
Example:

When the module is ... Then modem slot assignment

parameters is ...
Module Physical Node B To CCM #B in Slot Status
Slot Dual mode
CEM 1 #1 #2 Self Empty
(in light grey)
CEM 2 #2 #2 Self Used with CCM #B
CEM 3 #3 #1 Partner Empty
(in dark green)
CCM B #4 #2 Self Node B #2
CCM A (<) #5 #1 Partner Node B #1
CEM 4 #6 #1 Partner Used with CCM #A
CEM 5 #7 #1 Unassigned Occupied
(in dark grey)
CEM 6 #8 #1 Unassigned Empty
(in dark dark)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 53

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Proc 8: Dual NodeB #2 Configuration Final Check

Procedure, Continued

Dual NodeB #2
Configuration NOTE: The d4U Node B #1 is working now in dual Mode with the modem configuration as
Final Check assigned.
Procedure
(continued)
NOTE: If there is a mismatch between the views of the CCM-U #A is not working in dual mode
then call for trouble shooting. Decide whether to downgrade to single configuration (IEH521
section 705 Proc4: Downgrade Procedure Dual to Single NodeB Mode)

54 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Record Sheets / Checklists - On Site

Description The following record sheets are available to document the values for dual Node B
commissioning

Report Sheet - Select the UMTS Frequency Band used by the Node B.
Node B:
Frequency
Band Table 16: UMTS Frequency Band
UMTS Frequency (Band)
850Mhz 900Mhz 1900Mhz AWS 2100Mhz
(Band V) (Band VIII) (Band II) (Band IV) (Band I)

Report Sheet - Select the Radio Module Equipment used.

Radio Module
Equipment
Table 17: Radio Module Equipment
Radio Module Indoor Radio Module Outdoor
TRDU RRH40w
MC TRDU RRH60w
MC TRX RRH2x40
RRH2x60

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 55

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Record Sheets / Checklists - On Site, Continued

Report Sheet - Fill the Inventories parameters used.

Inventories
Equipment
Table 18: Inventories Parameters
Parameters Node B #1 Value Node B #2 Value
for CCM #A for CCM #B
Current Network Release (UNB)
(LR13.1 minimum required)
Software upgrade on Node B: Yes / No Yes / No
NeID (Serial Number) (6 digits) __ __ __ __ __ __ __ __ __ __ __ __
NeID Partner (Serial Number Partner) __ __ __ __ __ __ __ __ __ __ __ __
User Label
RU Name (30 characters max.)
PEC code (16 characters max.)
Manufacturing date (4 characters max.) __ __ __ __ __ __ __ __
Hardware reference
BTS Parameters: (BTS Packaging) dBTS 4U-V3 dBTS 4U-V3
BTS mode SingleMode SingleMode
SplitMode SplitMode

Continued on next page

56 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Hosting 2 Node Bs WCDMA in one d4U Procedures IEH 521, Section 432

Record Sheets / Checklists - On Site, Continued

Report Sheet - Fill the IP Parameters if DHCP is not used:

IP Parameters

Table 19: IP Parameters

IP Parameters Node B #1 Value Node B #2 Value
for CCM #A for CCM #B
DHCP server used? (Default value) (Default value)
Yes / No Yes / No
Node B IP address ___.___.___.___ ___.___.___.___
OMC-B IP address ___.___.___.___ ___.___.___.___
Sub-Network Mask ___.___.___.___ ___.___.___.___

Report Sheet - Fill the 2NodeBs parameters used.

2NodeBs
Table 20: 2NodeBs Parameters
Parameters
Node B dual2NodeBs
parameters Value for Node B #1 Value for Node B #2
CCM #A CCM #B
Parameter name:
SerializationNumberOfPartner
Modem Slot Array: Assignment for NodeB#1 Assignment for NodeB#2
Physical Slot 1 (CEM #1) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 2 (CEM #2) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 3 (CEM #3) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 4 (CCM #B) NB#2 Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 5 (CCM #A) NB#1 Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 6 (CEM #4) Unassigned / Self /Partner Unassigned / Self
Physical Slot 7 (CEM #5) Unassigned / Self /Partner Unassigned / Self
Physical Slot 8 (CEM #6) Unassigned / Self /Partner Unassigned / Self

December 15, 2013 Alcatel-Lucent Internal 57

Proprietary Use pursuant to Company instruction
IEH 521, Section 432 Hosting 2 Node Bs WCDMA in one d4U Procedures

Sign-Off Sheet

Description Sign-Off sheet has to be completed to finally document acceptance of the dual Node B
parameter configuration results in the same d4U.

Meaning of Sign- Completion of the Sign-Off sheet represents the finalization of the parameter configuration of
Off Sheet dual Node B activity and is meant to serve for customer acceptance of the Node B.

Sign-Off Sheet Sign off sheet for successful set the parameter of dual Node B in d4U.
The following sign-off confirms that all required checklists proof successful parameter
configuration of dual Node B in the same d4U.

Table 21: Dual Node Bs inside one d4U Checklists Customer Sign-off
Commissioner Coordinator / Customer
engineer on-Site Representative
activities
Company Name

Function
Name

Signature

Date

Archiving of All reporting sheets for an individual Node B commissioning must be archived.
Reports All reporting sheets must be available to be reused if necessary during the integration section.
Individual contractual agreements with customer may require the original to hand over to the
customer for archiving.

58 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 433

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

External Alarm Logic Status Integration Procedures

Table of Contents

General ............................................................................................................ 3
Section Description .......................................................................................... 3
Previous Release Date ....................................................................................... 3
Release Notes ................................................................................................. 3
References ........................................................................................................ 4
General ........................................................................................................ 4
Documentation access ...................................................................................... 4
Applicable IEH 521 sections ................................................................................ 4
Applicable Methods documents in LR13.3 ............................................................... 4
Tools Requirements ............................................................................................. 5
General ........................................................................................................ 5
Hardware Tool ................................................................................................ 5
Software Tool ................................................................................................. 5
External Alarm Logic Status Integration ..................................................................... 6
Description .................................................................................................... 6
Hardware requirements for the feature ................................................................. 6
Preconditions ................................................................................................. 6
External Alarm Description ................................................................................. 7
External alarms integration procedure ................................................................... 8
External Alarm Logical State Inversion .................................................................... 13
Description .................................................................................................. 13
Preconditions ............................................................................................... 13
TIL GUI Connection Principle ............................................................................ 13
Description of Alarm Type ................................................................................ 14
Alarm Display Definition .................................................................................. 14
External and User Alarm Initial Checking Procedure for Cabinet ................................. 15
External Alarm Initial Checking Procedure for RRH .................................................. 17
External Alarm Logical State Inversion Parameter Activation ..................................... 20
External Alarm Logic Inversion Validation Procedure for Cabinet ................................. 22
External Alarm Logic Inversion Validation Procedure for RRH ..................................... 24
List of Figures

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Integration Tests .................................... 4
Table 2: Applicable Methods Documents LR13.3 for IEH521 ....................................................... 4
Table 3: Hardware Tools ................................................................................................. 5
Table 4: Software Tools .................................................................................................. 5
Table 5: Required Hardware Configurations .......................................................................... 6
Table 6: External Alarm Hardware Detection ........................................................................ 7
Table 7: Maximum Number of External Alarm Supported by RRH type .......................................... 7

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

General

Section This section provides detailed information about the individual procedures for feature
Description integration into an existing UTRAN of a WCDMA Node B:
Preconditions
Inputs
Outputs
Additional details
Link to commissioning methods document where the procedure is contained

Previous Release New creation

Date

Release Notes New creation: June 2014 under utilization of existing IM documents for LR13.3W.

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
feature integration.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required

521 sections

Table 1: Applicable IEH 521 Sections for WCDMA Node B Integration

Tests

Section Description
401 Integration Planning
402 Integration into existing UTRAN
410 Integration Testing
499 Node B Integration Test Records

Applicable The following operational documents are required to perform the Node B Integration in LR13.3
Methods
documents in
LR13.3 Table 2: Applicable Methods Documents LR13.3 for IEH521
Doc Number Doc Title URL
9YZ-05870- Alcatel-Lucent 9353 WMS user Guide http://cic.us.alcatel-
0014-PCZZA lucent.com/pdfdocs14/pr
istore215/555634.pdf
9YZ-05870- Alcatel-Lucent 9353 WMS Node B Alarms http://cic.us.alcatel-
0060-UFZZA Reference Guide lucent.com/pdfdocs14/pr
istore215/536534.pdf

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

Tools Requirements

General This section describes the hardware and software tools required to perform the feature
integration.

Hardware Tool The hardware tools listed in the following table are required to perform the integration test.

Table 3: Hardware Tools

Hardware Tool Quantity Description

Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

If operation Then RJ45 cable

is ... will be
connected...
remote to the IP Backhaul
Network
at site (field to the CCM-U Board
operation)

Software Tool The software tool listed in the following table are required to perform the commissioning test

Table 4: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with
WIN7)

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logic Status Integration

Description This procedure describes how to set the logical State of cabinet alarms
NOTE: The additional procedure External Alarm Logic Status Inversion needs to be applied
according to customer need. (refer to section499 from IEH521)

Hardware The following table lists the hardware pre-conditions for the use of the procedure
requirements
for the feature
Table 5: Required Hardware Configurations
Cabinet Digital Module Alarm Module Radio Module
9100 MBI or MBO. 9326 d2U V2 Alco Driver RRH
9311 Macro Node B 9926 d2U V3 Reporting TRDU
9941 Smart Base 9926 d4U V3 eAMx MC-RRH
Station MC-TRDU

Preconditions The Node B is already fully Integrated

The External Alarm feature is activated
The minimum release software must be LR13.3W.
The laptop setting and WMS connections are already done and available.
The External Alarms are physically connected on macro or on distributed Node Bs

Continued on next page

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logic Status Integration, Continued

External Alarm The following table describes the status of external alarm detection by the Alarm Module from
Description the cabinet

Table 6: External Alarm Hardware Detection

External Alarm Hardware Detection Open Closed
Alco Driver reporting 1 0
eAMx 1 0

The following tables describes the maximum number of external alarms dependent on RRH
type or the cabinet type

If Node B is... Then alarm numbers supported is...

Macro or Distributed Node B with 32 alarms
eAMx
Macro with Alco Driver 8~16 alarms
Remote Radio Head Module (RRH 4~6 alarms dependent on the available RRH
or MC-RRH) RRH60-xx
RRH2x60-xx

The following table describes the maximum number or external alarms in dependency of RRH
type used.

Table 7: Maximum Number of External Alarm Supported by RRH type

60-21 40-21 2x60-
60-09 60-21A 40-08 60-08 850 MC RRH
RRH type:
60-09A 60-21C 40-19 60-19 2x60- 2x40-09
2x60-21 40-AWS 1900

Number of External
alarms supported 4 4 6 6 6 2
(Maximum)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logic Status Integration, Continued

External alarms This procedure describes how to configure and to integrate the external alarms logic status for
integration the cabinet configuration with Alco Driver or eAMx.
procedure

Step Action
1 Open layout in WMS with Node B for integration of external alarms
2 Right click on concerned Node B and select Equipment Monitor to open the
Equipment Monitor view.
3 Open External Alarm Mapping Table and select one by one each
ExternalAlarms/#

4 Select ExternalAlarm/# by right click and select

Configuration | Object Editor

NOTE: Object Editor window opens

Continued on next page

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logic Status Integration, Continued

External alarms
integration
Step Action
procedure
(continued) 5 Select and set one by one each field alarm message to External Alarm/# =
Description of external alarm

NOTE: Dependent on the customer requirements on external alarms, select

one External Alarm/# number and define its dedicated alarmMessage to
highlight.

NOTE: Example for dedicated alarmMessage: Alarm Air Filter or Door open
alarm.
6 Click Set and then Apply All Changes to apply the selected configuration
7 Select ExternalAlarm/# by right click and select
Configuration | Object Editor

NOTE: Object Editor window opens

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logic Status Integration, Continued

External alarms
integration
Step Action
procedure
(continued) 8 Open Object Editor by right click on concerned Node B on the WMS layout:
Select Configuration | Object Editor

Continued on next page

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logic Status Integration, Continued

External alarms
integration
Step Action
procedure
(continued) 9 Open the attribute of the external alarm dependent on to the equipment used:

If ... Then open and set the

attribute...
BTSEquipment supervisedExternalAlarmActiveStates
RemoteRadioHead supervisedRRHExternalAlarmActiveStates

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logic Status Integration, Continued

External alarms
integration
Step Action
procedure
(continued) 10 Set the logical states of each bit mask of the external alarms
supervisedExternalAlarmActiveStates according to the customer
requirements on the details window:
Example:
00000000 - 11110000 - 00000000 - 00000000

NOTE: External Alarm detection logic:

NOTE: These parameters can be updated online.

If bit is ... Then external alarm active state is ...

0 Open (no connection to ground)
Indicates that the alarm is detected when the contact is
open
1 Close (Connected to ground)
Indicates that the alarm is detected when the contact is
closed.

11 Click Set and Apply All Changes to store the alarm states definitions.

NOTE: Command Manager window opens

12 Perform Set Online operation and validate that it is performed successfully.
13 Check visually the External State following the Procedure External Alarm
State test using the TIL GUI.

12 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logical State Inversion

Description This procedure describes how to configure the inversion of the external alarms state (open or
closed) for:
Cabinet (alarm collection through eAM boards) or
RRH
in-house RRH,
RRH60-21 or 09
RRH2x60-21,
MC-RRH2x40-09.

NOTE: The execution of this procedure is only applicable if external alarms are used and if the
logical alarms status need to be inverted according to the alarm source used.

Preconditions The laptop setting and WMS connections are already done and available.
The laptop setting and TIL connections are already done and available. (Locally or
Remotely)
The Node B is already fully integrated.
The External Alarms Logical State Inversion feature must be activated.
The External Alarms are physically connected on macro or on distributed Node Bs
The alarm logic management would only be applied to the alarms from Alco driver.

NOTE: For some special cabinets: 9100 MBS INDOOR 3GOO (9100 MBI5AB) some external
alarms (16 for indoor) are reserved for the cabinet management (door, water, fire, power).
These alarms must not be inverted by use of alarm logic inversion.

TIL GUI This table describes how to establish the TIL GUI connection between Laptop PC and the
Connection Node B according to the operation it is used for.
Principle
If TIL operation is ... Then connect the Laptop PC (with RJ45) is
connected to...
remote the IP Backhaul Network using TIL through existing WMS
connection (WMS IP@ + Login/password are needed)
the IP Backhaul Network using TIL through existing web
browser (Node B IP@ + Login/password are needed)
local (field operation - the CCM-U Board (Port 1) for local TIL connection.
mainly for trouble
shooting)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logical State Inversion, Continued

Description of The following table describes the type and the numbers of alarms which are collected by the
Alarm Type Alarm Module of the cabinet

If alarm type is ... Then alarm mask window

displays...
External Alarm 1 to 32 alarms
User Alarms for E1 1 to 4 alarms
User Alarms for T1 1 to 3 alarms

NOTE: The Alarms mask window displays two types of alarms:

External alarm
User alarm

Alarm Display The following table details the visual meaning of the colors for the alarm mask.
Definition

If alarm indicator color is... Then it indicates that the alarm...

White Is masked (Level =0)
NOTE: The value 0 indicates that the alarm
is detected when the contact is opened.
Green Is not masked in DLU (Config File) and it
will be reported (Level =1)
NOTE: The value 1 indicates that the alarm
is detected when the contact is closed.
Yellow State can be configured

NOTE: These alarms parameters can be updated after the Node B integration in an existing
UTRAN and at any time of operational mode if need new addition of external alarm.

Continued on next page

14 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logical State Inversion, Continued

External and Perform the following procedure to perform an initial visual check of the Alarm Mask of the
User Alarm Cabinet before External Alarm inversion activation (or deactivation) is done.
Initial Checking
Procedure for NOTE: The laptop setting and TIL connections are already done and available. (Locally or
Cabinet Remotely)

Step Action
1 Select the Display Alarms Mask menu by right-clicking on GPSAM from TIL
GUI for External Alarms mask from cabinet.

2 Check the Alarms Mask window for masked and unmasked alarms.

NOTE: Refer to the Alarms display definition for alarm status meaning.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logical State Inversion, Continued

External and
User Alarm
Step Action
Initial Checking
Procedure for 3 Click on Report All Alarms button to display the alarm status
Cabinet
(continued)

NOTE: The report of all alarms can be done even if the alarm is disabled in
the Node B Configuration file (DLU Mask file).

4 Check the Alarms Mask window External Alarms and User Alarms
appears as shown in the following figure : (masked and unmasked alarms)

NOTE: Refer to the Alarms display definition.

5 Identify and notice from the Alarm Mask window

number of External Alarm or the User Alarms
which are available for the External Alarm Logic Inversion Validation
Procedure for Cabinet according to user needs.

NOTE:
YELLOW: can be available to be configured
GREEN: the alarm is already configured and used.
WHITE: the alarm is not usable and masked.

6 Click on Back to DLU Mask to return to DLU Mask

NOTE: The external and user alarms that can be masked /unmasked are user
definable.

Continued on next page

16 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logical State Inversion, Continued

External Alarm Perform the following procedure steps to perform an initial visually check the Alarm Mask from
Initial Checking RRH before External Alarm inversion activation (or deactivation).
Procedure for
RRH NOTE: The laptop setting and TIL connections are already done and available. (Locally or
Remotely)

Step Action
1 Select the Radio Element by clicking on GPxOIM (OI#) CPRI activated
(Green LED on Tx/Rx) from TIL GUI.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logical State Inversion, Continued

External Alarm
Initial Checking
Step Action
Procedure for
RRH (continued) 2 Select the Display Alarms Mask menu by right-clicking on Radio Element
from TIL GUI. for RRH alarm mask from RRH

3 Review the Display Alarms Mask window which appears as shown in the
following figure for Radio Element.

NOTE: Refer to the Alarms display definition.

Continued on next page

18 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logical State Inversion, Continued

External Alarm
Initial Checking
Step Action
Procedure for
RRH (continued) 6 Click on Report All Alarms button,

NOTE: The report of all alarms can be checked even if the alarm is disabled in
the Node B Configuration file (DLU Mask file).

7 Check the Alarms Mask window External Alarms appears as shown in the
following figure : (masked and unmasked alarms)

NOTE: Refer to the Alarms display definition.

8 Identify and notice from the Alarm Mask window the

number of External Alarm
which is available for the for the procedure External Alarm Logic Inversion
Validation Procedure for RRH as per user requirement.

NOTE:
YELLOW: can be available to be configured
GREEN: the alarm is already configured and used.
WHITE: the alarm is not usable and masked
9 Click on Back to DLU Mask to return to DLU Mask

NOTE: The external that can be masked /unmasked are user definable.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logical State Inversion, Continued

External Alarm Perform the following procedure to configure the External Alarm Logical State Inversion
Logical State parameter for the external alarms of Cabinet or RRH.
Inversion
Parameter
Activation NOTE: The laptop setting and WMS connections must be done and available. (Remotely)

Step Action
1 Open layout in WMS with Node B
2 Right click on concerned Node B and select Equipment Monitor to open the
Equipment Monitor view.
3 Open External Alarm Mapping Table and select one by one each
ExternalAlarms/#

4 Select ExternalAlarm/# by right click and select

Configuration | Object Editor

NOTE: Object Editor window opens

Continued on next page

20 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logical State Inversion, Continued

External Alarm
Logical State
Step Action
Inversion
Parameter 5 Open the attribute of the external alarm :
Activation isExternalAlarmLogicInversionAllowed
(continued)

6 Select True or False on the attribute

isExternalAlarmLogicInversionAllowed according to the customer need on
the details window:

If attribute Then external

isExternalAlarmLogicInversionAllowed alarm Logical
is ... State is ...
True Inverted
False Not inverted

NOTE: The External Alarm /# Logical State is now configured according to

user needs (activate or deactivate).

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logical State Inversion, Continued

External Alarm Perform the following procedure steps to validate visually the Alarms Logic Inversion Mask for
Logic Inversion the cabinet.
Validation
Procedure for
Cabinet NOTE: The laptop setting and TIL connections are already done and available. (Locally or
Remotely)

Step Action
1 Select the Active States menu by right-clicking on GPSAM from TIL GUI.

2 Check the Active States window which appears as shown in the following
figure for Cabinet External Alarms after activation of the alarm inversion
attribute.

NOTE: Use alarm display definition for the review

Continued on next page

22 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logical State Inversion, Continued

External Alarm
Logic Inversion
Step Action
Validation
Procedure for 3 Click on each square (displayed alarm state) to review whether the expected
Cabinet indication is matching customer requirements.
(continued)
NOTE: If the indications do not match customer requirements for one or
several external alarms, you can correct them individually by selection of
green square instead of white or the reverse to be aligned with customer
requirements.

NOTE: The selection of the status alarm changes after each click in a cyclic
mode (the sequence of change begins from Yellow to Green then White, then
Green then White...)

NOTE: Active States window explanation

The green square means that the alarm will be reported when level = 1
(Alarm is raised when contact is closed)
The white square means that the alarm will be reported when level = 0
(Alarm is raised when contact is open)

Expected Result: The external alarm color of the alarm where inversion is
allowed (set to True) is now inverted compared to the initial check.
Green color instead of White
White color instead of Green
.
4 Click the Save Active States button to activate the alarms logic in the Node B
Configuration.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logical State Inversion, Continued

External Alarm Perform the following procedure steps to validate visually the Alarms Logic Inversion Mask for
Logic Inversion RRH.
Validation
Procedure for
RRH NOTE: The laptop setting and TIL connections are already done and available. (Locally or
Remotely)

Step Action
1 Select the Radio Element by clicking on GPxOIM (OI#) CPRI activated
(Green LED on Tx/Rx) from TIL GUI.

Continued on next page

24 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
External Alarm Logic Status Integration Procedures IEH 521, Section 433

External Alarm Logical State Inversion, Continued

External Alarm
Logic Inversion
Step Action
Validation
Procedure for 2 Select the Active States menu by right-clicking on Radio Element from TIL
RRH (continued) GUI.

3 Check the Active States window which appears as shown in the following
figure for Radio Element Alarms after activation of the alarm inversion
attribute.

NOTE: Refer to the alarm display definition:

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 433 External Alarm Logic Status Integration Procedures

External Alarm Logical State Inversion, Continued

External Alarm
Logic Inversion
Step Action
Validation
Procedure for 4 Click on each square (displayed alarm state) to review whether the expected
RRH (continued) indication is matching customer requirements.

NOTE: If the indications do not match customer requirements for one or

several external alarms, you can correct them individually by selection of
green square instead of white or the reverse to be aligned with customer
requirements.

NOTE: The selection of the status alarm changes after each click in a cyclic
mode (the sequence of change begins from Yellow to Green then White, then
Green then White...)

NOTE: Active States window explanation

The green square means that the alarm will be reported when level = 1
(Alarm is raised when contact is closed)
The white square means that the alarm will be reported when level = 0
(Alarm is raised when contact is open)

Expected Result: The external alarm color of the alarm where inversion is
allowed (set to True) is now inverted compared to the initial check.
Green color instead of White
White color instead of Green
.
5 Click the Save Active States button to activate the alarms logic in the Node B
Configuration.

26 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 434

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

971x LR Cabinet Internal and External Alarms Checking Configuration

Table of Contents

General ............................................................................................................ 3
Section Description .......................................................................................... 3
Applicability ................................................................................................... 3
Previous Release Date ....................................................................................... 3
Release Notes ................................................................................................. 3
References ........................................................................................................ 4
General ........................................................................................................ 4
Documentation access ...................................................................................... 4
Applicable IEH 521 sections ................................................................................ 4
Applicable Methods documents ............................................................................ 4
Tools Requirements ............................................................................................. 5
General ........................................................................................................ 5
Hardware Tool ................................................................................................ 5
Software Tool ................................................................................................. 5
971x LR Cabinet Alarms Definition ........................................................................... 6
Description .................................................................................................... 6
Supported LR cabinet configurations ..................................................................... 6
Alarm Collection Device .................................................................................... 6
General Alarms Rules Description ......................................................................... 6
Frame Alarms definition .................................................................................... 7
WMS Display Rules ........................................................................................... 8
Cabinet Alarm Mapping Description for 9711 LR Indoor AC ........................................... 9
Cabinet Alarm Mapping Description for 9711 LR Indoor DC ......................................... 10
Cabinet Alarm Mapping Description for 9712 LR Outdoor AC ...................................... 11
Cabinet Alarm Mapping Description for 9712 LR Outdoor DC ...................................... 12
Alarm Mapping Description for TRDU Sub-rack used in LR Cabinet ............................... 13
Alarm Mapping Description for d2U/d4U used in LR Cabinet ....................................... 13
971x LR Cabinet Configuration - Alarm Checking ........................................................ 14
Description .................................................................................................. 14
Preconditions ............................................................................................... 14
TIL GUI Connection Principle ............................................................................ 14
971x LR Cabinet Alarm Checking Procedure .......................................................... 15

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

List of Figures

Figure 1: eAMoB Alarm Interface ....................................................................................... 6

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Integration Tests .................................... 4
Table 2: Applicable Methods Documents for IEH521 ................................................................ 4
Table 3: Hardware Tools ................................................................................................. 5
Table 4: Software Tools .................................................................................................. 5
Table 5: Cabinet Alarm Mapping for 9711 Light Radio Indoor AC ................................................. 9
Table 6: Cabinet Alarm Mapping for 9711 Light Radio Indoor DC ............................................... 10
Table 7: Cabinet Alarm Mapping for 9712 Light Radio Outdoor AC ............................................. 11
Table 8: Cabinet Alarm Mapping for 9712 Light Radio Outdoor DC ............................................. 12
Table 9: Alarm Mapping for TRDU Sub-rack ........................................................................ 13
Table 10: Alarm Mapping for D2U/D4U .............................................................................. 13

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
971x LR Cabinet Internal and External Alarms Checking Configuration IEH 521, Section 434

General

Section This section provides detailed information how to check internal and external alarms of the
Description 971x LR Cabinet configurations.
Preconditions
Inputs
Outputs
Additional details

Applicability This procedure should be viewed as part of the integration into an existing UTRAN of a
WCDMA Node B if the Node B is hosted inside the 971x LR Cabinet.

Previous Release New creation

Date

Release Notes New creation: June 2014 under utilization of existing documents.

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

References

General This section utilizes ALU Product Documents as well as handbook 521 sections as supportive
information for this integration testing.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The table below lists the required documents for WCDMA Node B Integration into an existing
521 sections UTRAN.

Table 1: Applicable IEH 521 Sections for WCDMA Node B Integration

Tests
Section Description
401 Integration Planning
402 Integration into existing UTRAN
410 Integration Testing
433 External Alarm Logic Status Integration and Inversion Procedures
499 Node B Integration Test Records

Applicable The following methods documents are required to perform the Node B Integration in LR13.3
Methods
documents
Table 2: Applicable Methods Documents for IEH521

Doc Number Doc Title URL

9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.3) lucent.com/pdfdocs14/pri
store215/586415.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0060-UFZZA System - Node B Alarms Reference Guide lucent.com/pdfdocs14/pri
(LR13.3) store215/536534.pdf

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
971x LR Cabinet Internal and External Alarms Checking Configuration IEH 521, Section 434

Tools Requirements

General This section describes the required hardware and software tools to perform the described
integration testing step.

Hardware Tool The hardware tools listed in the following table are required to perform the integration tests.

Table 3: Hardware Tools

Hardware Tool Quantity Description

Keys to open the Node B 1 set If necessary (If operation on field only)
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

If operation Then RJ45 cable

is ... will be
connected to...
remote the IP Backhaul
Network
local (in field) the CCM-U Board

Software Tool The software tool listed in the following table are required to perform the commissioning test

Table 4: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with
WIN7)

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

971x LR Cabinet Alarms Definition

Description This procedure describes all cabinet dependent alarms and how the alarms need to be
mapped to the external alarms.

Supported LR The following LR cabinets are target for this procedure

cabinet 9711 Light Radio Indoor cabinet AC
configurations
9712 Light Radio Outdoor cabinet AC
9711 Light Radio Indoor cabinet DC
9712 Light Radio Outdoor cabinet DC

Alarm Collection The following figure illustrates how the individual alarms are connected to the alarm collection
Device device.

Figure 1: eAMoB Alarm Interface

The following alarms can be supported by this board:

Frame alarms (up to 10)
Power alarms (4)
External loop user alarms (32)

General Alarms The list of alarms is consisting of

Rules Internal alarms fix wired inside the cabinet (Door, FAN, filters, power) and collected
Description through the alarm collection device (eAM).
External alarms - user defined alarms which are collected through an external alarm cable
entering in the cabinet and connected to the alarm collection device (eAM).

NOTE: All alarms are collected through the alarm collection device (eAM) and sent via the BBU
to the OAM center which will display the individual alarms.

NOTE: In case of stacking of the cabinet, the alarm outputs of the upper cabinet controller will
be connected to the input of the cabinet controller of the lower cabinet. The alarm port must be
considered as an OR of the possible alarms inputs from upper and lower cabinet.

Continued on next page

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
971x LR Cabinet Internal and External Alarms Checking Configuration IEH 521, Section 434

971x LR Cabinet Alarms Definition, Continued

Frame Alarms The following cabinet alarms can be generated in the LR cabinet and are considered part of the
definition internal alarms (frame alarms):
Door Intrusion
Fan unit failure
Filter unit 1
Filter unit 2
Over temperature
Under temperature
TRDU FAN failure
Air flow (equivalent to the Filter unit 2, but supported in WCDMA)

NOTE: The two Filter unit alarms are related to the size of the cabinet (small/compact)
implying a different size of the filter.

The following power related alarms can be generated for the primary rectifier shelf if available:
AC Mains
Rectifier minor failure
Rectifier Major failure
Battery Major failure
Battery minor failure
PSU Controller failure
surge protection

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

971x LR Cabinet Alarms Definition, Continued

WMS Display The following table describes the WMS display rules according to the Node B configuration
Rules used in the LR cabinet.

NOTE: The WMS 3G display does not always respect the real configuration in the cabinet on
site.

If the Node B configuration is... Then WMS GUI display...

Small No Specific distinction
Compact
D2U based cabinet The same as D2U standalone.

NOTE: Only the label at the bottom needs

to be changed according to BTSpackaging.
D4U based cabinet The same as 9926 D4U standalone.

NOTE: Only the label at the bottom needs

to be changed according to BTSpackaging
Other configuration with D2U/D4U are not The 9326 D2U/D4U with:
in charge of cabinet alarms RRH
TRDU
multi-technology with LTE the 3G part will be displayed like a set of
D2U/D4U (with no cabinet alarms)

Continued on next page

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
971x LR Cabinet Internal and External Alarms Checking Configuration IEH 521, Section 434

971x LR Cabinet Alarms Definition, Continued

Cabinet Alarm The following table describes the cabinet alarm mapping for 9711 Light Radio Indoor AC
Mapping version
Description for Table 5: Cabinet Alarm Mapping for 9711 Light Radio Indoor AC
9711 LR Indoor
AC
PIN Physical Alarm Alarm Equipment Alarm Cause
Type
PWR_ALM_01 Top Fan Cooling system Fan A Failure
PWR_ALM_02 Door Door Contact Door Open
PWR_ALM_03 TRDU Fan Cooling system Other Fan Rack Failure
PWR_ALM_04 TRDU Fan Cooling system Other Fan Rack Failure
FRAME_ALM_01 AC Main Power Distribution system AC Mains Voltage Fault
FRAME_ALM_02 Rectifier Minor Failure Rectifier System Rectifier Fault
FRAME_ALM_03 Battery Major Failure Power Distribution system Alarm Battery Major
FRAME_ALM_04 Power Control Module Rectifier system Energy System
Failure Controller Failed
FRAME_ALM_05 Battery Minor Failure Power Distribution system Alarm Battery Minor
(EOL)
FRAME_ALM_06 Surge Protection Lightning Protection Lightning Protector Fault
FRAME_ALM_07 Rectifier Major Failure Rectifier System Rectifier Fault Major
FRAME_ALM_08 N/A N/A To be masked
FRAME_ALM_09 N/A N/A To be masked
FRAME_ALM_10 N/A N/A To be masked
FRAME_ALM_11 Not used - Not used
FRAME_ALM_12 Not used - Not used

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

971x LR Cabinet Alarms Definition, Continued

Cabinet Alarm The following table describes the cabinet alarm mapping for 9711 Light Radio Indoor DC
Mapping version
Description for Table 6: Cabinet Alarm Mapping for 9711 Light Radio Indoor DC
9711 LR Indoor
DC
PIN Physical Alarm Alarm Equipment Alarm Cause
Type
PWR_ALM_01 Top Fan Cooling system Fan A Failure
PWR_ALM_02 Door Door Contact Door Open
PWR_ALM_03 TRDU Fan Cooling system Other Fan Rack
Failure
PWR_ALM_04 TRDU Fan Cooling system Other Fan Rack
Failure
FRAME_ALM_01 N/A N/A To be masked
FRAME_ALM_02 N/A N/A To be masked
FRAME_ALM_03 N/A N/A To be masked
FRAME_ALM_04 N/A N/A To be masked
FRAME_ALM_05 N/A N/A To be masked
FRAME_ALM_06 N/A N/A To be masked
FRAME_ALM_07 N/A N/A To be masked
FRAME_ALM_08 N/A N/A To be masked
FRAME_ALM_09 N/A N/A To be masked
FRAME_ALM_10 N/A N/A To be masked
FRAME_ALM_11 Not used - Not used
FRAME_ALM_12 Not used - Not used

Continued on next page

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
971x LR Cabinet Internal and External Alarms Checking Configuration IEH 521, Section 434

971x LR Cabinet Alarms Definition, Continued

Cabinet Alarm The following table describes the cabinet alarm mapping for 9712 Light Radio Outdoor AC
Mapping version
Description for Table 7: Cabinet Alarm Mapping for 9712 Light Radio Outdoor AC
9712 LR
Outdoor AC
PIN Physical Alarm Alarm Equipment Alarm Cause
Type
PWR_ALM_01 Fan Cooling system Fan A Failure
PWR_ALM_02 Door Door Contact Door Open
PWR_ALM_03 Air Filter 1 Cooling system Clogged Air Filter 1
PWR_ALM_04 Air Filter 2 Cooling system Clogged Air Filter 2
FRAME_ALM_01 AC Main Power Distribution system AC Mains Voltage
Fault
FRAME_ALM_02 Rectifier Minor Failure Rectifier System Rectifier Fault
FRAME_ALM_03 Battery Major Failure Power Distribution system Alarm Battery Major
FRAME_ALM_04 PSU Controller Failure Rectifier system Energy System
Controller Failed
FRAME_ALM_05 Battery Minor Failure Power Distribution system Alarm Battery Minor
(EOL)
FRAME_ALM_06 Surge Protection Lightning Protection Lightning Protector
Fault
FRAME_ALM_07 Rectifier Major Failure Rectifier System Rectifier Fault Major
FRAME_ALM_08 Over Temperature Cooling System Internal high
temperature
FRAME_ALM_09 Under Cooling System Internal low
Temperature temperature
FRAME_ALM_10 TRDU FAN Cooling System Other Fan Rack
Failure
FRAME_ALM_11 Not used - Not used
FRAME_ALM_12 Not used - Not used

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

971x LR Cabinet Alarms Definition, Continued

Cabinet Alarm The following table describes the cabinet alarm mapping for 9712 Light Radio Outdoor DC
Mapping version
Description for Table 8: Cabinet Alarm Mapping for 9712 Light Radio Outdoor DC
9712 LR
Outdoor DC
PIN Physical Alarm Alarm Equipment Alarm Cause
Type
PWR_ALM_01 Fan Cooling system Fan A Failure
PWR_ALM_02 Door Door Contact Door Open
PWR_ALM_03 Air Filter 1 Cooling system Clogged Air Filter 1
PWR_ALM_04 Air Filter 2 Cooling system Clogged Air Filter 2
FRAME_ALM_01 N/A N/A To be masked by SW
FRAME_ALM_02 N/A N/A To be masked by SW
FRAME_ALM_03 N/A N/A To be masked by SW
FRAME_ALM_04 N/A N/A To be masked by SW
FRAME_ALM_05 N/A N/A To be masked by SW
FRAME_ALM_06 N/A N/A To be masked by SW
FRAME_ALM_07 N/A N/A To be masked by SW
FRAME_ALM_08 Over Temperature Cooling System Internal high
temperature
FRAME_ALM_09 Under Cooling System Internal low
Temperature temperature
FRAME_ALM_10 TRDU FAN Cooling System Other Fan Rack
Failure
FRAME_ALM_11 Not used - Not used
FRAME_ALM_12 Not used - Not used

Continued on next page

12 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
971x LR Cabinet Internal and External Alarms Checking Configuration IEH 521, Section 434

971x LR Cabinet Alarms Definition, Continued

Alarm Mapping The following section describes the alarm mapping for the TRDU sub-rack used in the LR
Description for cabinet configuration.
TRDU Sub-rack
used in LR
Cabinet Table 9: Alarm Mapping for TRDU Sub-rack

Physical Alarm Alarm Equipment Type Alarm Cause

Cooling Unit Fail Fan Tray Fan Tray Failed
Internal Thermistor Failure Cooling system Internal Sensor Failure

Alarm Mapping The following section describes the alarm mapping for d2U/d4U used in the LR cabinet
Description for configuration.
d2U/d4U used The D2U/D4U is installed in the cabinet.
in LR Cabinet
For D2U own alarms: fan alarms are treated as usually.
For D4U, there are 2 fan trays inside, so when alarms are reported to WMS, the serial number
of FAN A or the serial partners number of FAN B must be included in the respective additional
information field of FAN alarm.

Table 10: Alarm Mapping for D2U/D4U

Physical Alarm Alarm Equipment Type Alarm Cause

Fan A (or 1) Failure Fan Tray (Serial Number) Fan A Failure
Fan B (or 2) Failure Fan Tray (Serial Partners Number) Fan B Failure

June 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

971x LR Cabinet Configuration - Alarm Checking

Description This procedure describes how to validate the correctness of the alarm configuration of the
971x LR Cabinet remotely through remote TIL connection and WMS.

NOTE: For trouble shooting reasons it is possible to execute the procedure at site through
local TIL connection.

Preconditions The Node B is already fully Integrated

The External Alarm feature must be activated
The minimum release software must be UA08.x.
The laptop setting and WMS and TIL connections are already done and available.
The LR cabinet is fully installed and cables & interfaces are fully connected
External Alarms are physically connected
The eAMiB/eAMoB alarm interface is installed and connected.
The cabling from eAMiB/eAMoB is connected to the master digital controller.
The BTS packaging type must be correctly commissioned into the right RUC.

NOTE: The LR cabinets TIL GUI have the same shelf/slot as D2U/D4U. Only the BTS
packaging displays the LR cabinet type under use:
9711 Light Radio Indoor cabinet AC
9712 Light Radio Outdoor cabinet AC
9711 Light Radio Indoor cabinet DC
9712 Light Radio Outdoor cabinet DC

TIL GUI The following table describes how to establish the TIL GUI connection between Laptop PC
Connection and the Node B according to the operation.
Principle

If TIL operation is ... Then connect the Laptop PC (with RJ45)...

In remote (for normal On the IP Backhaul Network using TIL through existing WMS
validation) connection (WMS IP@ + Login/password are needed)
On the IP Backhaul Network using TIL through existing web
browser (Node B IP@ + Login/password are needed)
On field (mainly for trouble On the CCM-U Board (Port 1) for local TIL connection.
shooting)

Continued on next page

14 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
971x LR Cabinet Internal and External Alarms Checking Configuration IEH 521, Section 434

971x LR Cabinet Configuration - Alarm Checking,

Continued

971x LR The following procedure describes how to check the 971x LR Cabinet Alarms Configuration.
Cabinet Alarm
Checking
Procedure Step Action
1 Verify that the correct BTS Packaging type is displayed and selected for the
LR Cabinet at the bottom of the TILGUI:

2 Display the current alarms by

Right click on the GPSAM board then select Alarms to display current alarms
from the TIL GUI or WMS

Or Select Alarms Display current alarms from the TIL GUI or WMS

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

971x LR Cabinet Configuration - Alarm Checking,

Continued

971x LR Cabinet
Alarm Checking
Step Action
Procedure
(continued) 3 Validate the Current Alarms Display window against the use LR cabinet
configuration is consistent by use of the table below

If LR Cabinet configuration Then refer to alarm

used is... mapping ...
9711 Light Radio Indoor cabinet AC Table 5
9711 Light Radio Indoor cabinet DC Table 6
9712 Light Radio Outdoor cabinet AC Table 7
9712 Light Radio Outdoor cabinet DC Table 8
With TRDU subrack Table 9
With d2U or d4U Table 10

Expected Result: The alarms must be correctly labeled in the current alarm
display window (as shown in next step) according to the Type of LR Cabinet
and following the dedicated alarm mapping table.

Continued on next page

16 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
971x LR Cabinet Internal and External Alarms Checking Configuration IEH 521, Section 434

971x LR Cabinet Configuration - Alarm Checking,

Continued

971x LR Cabinet
Alarm Checking
Step Action
Procedure
(continued) 4 Validate alarm function and correct mapping by activation of DOOR OPEN
alarm.

NOTE: This requires a person at site

NOTE: Alarms must get cleared prior to completing this procedure.

NOTE: To troubleshoot alarms check the Alcatel-Lucent Node B Fault

Management User Manual: TIL (refer to references section) and/or contact the
support team.

June 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 434 971x LR Cabinet Internal and External Alarms Checking Configuration

This page is left intentionally blank

18 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 499

Jun 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Node B Integration Test Records

Table of Contents

General ............................................................................................................ 6
Section Description .......................................................................................... 6
Previous Release Date ....................................................................................... 6
Release Notes ................................................................................................. 6
References ........................................................................................................ 7
General ........................................................................................................ 7
Documentation access ...................................................................................... 7
Applicable IEH 521 sections ................................................................................ 7
Applicable Methods documents ............................................................................ 8
Integration Checklists......................................................................................... 10
Purpose ...................................................................................................... 10
Checklists overview ........................................................................................ 10
Checklist customization ................................................................................... 10
Used Documents ............................................................................................... 11
Used Documents ............................................................................................ 11
Reporting Sheets / Checklists - On Site ................................................................... 13
BTS Parameters ............................................................................................. 13
Antenna Positions .......................................................................................... 13
Communication Test Results ............................................................................. 14
Reporting Sheet / Checklists Remote Operation (NSP) ............................................... 15
Sequence of operations log .............................................................................. 15
Sequence of operations log (continued) ............................................................... 16
Reporting Sheets / Checklists TX Power Test through remote operation (WMS) ................. 17
TX Power measurement ................................................................................... 17
RNC and BTS name under test ........................................................................... 17
TX Power measurement results .......................................................................... 17
Reporting Sheets / Checklists RX Tests through remote operation (WMS) ........................ 19
RTWP measurements ...................................................................................... 19
RNC and BTS name under test ........................................................................... 19
RTWP measurement results .............................................................................. 20
Supporting Sheets & Checklists RF Path Health Check and Telnet Preparation Optional ..... 21
Description .................................................................................................. 21

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Telnet Preparation ......................................................................................... 21

Log-in to the WMS Server (Telnet) ...................................................................... 21
Log-in to the Node B (Telnet) ............................................................................ 21
Display Data List of all Radio Element (Telnet) ...................................................... 22
Rx Power and Tx Power Measurements of each LocalCell ID (Telnet) ............................ 23
Supporting Sheets / Checklists RF Path Test for ASB RRH Products (2x60 or 60-21C) - optional
.................................................................................................................... 24
Description .................................................................................................. 24
RE Tests results of ASB Product ......................................................................... 24
Log-in to the Radio Element (Telnet) .................................................................. 24
VSWR Measurement (Telnet) results report ......................................................... 24
TX Power Measurement (Telnet) results report .................................................... 25
RSSI Measurement (Telnet) results report ........................................................... 25
Supporting Sheets / Checklists RF Path Tests for MTI - GPCS RRH (60w-21) - optional ......... 26
Description .................................................................................................. 26
RE Tests of GPCS Product ................................................................................. 26
Log-in to the Radio Element (Telnet) .................................................................. 26
VSWR Measurement (Telnet) ............................................................................. 26
PA Gain Measurement (Telnet) .......................................................................... 27
TX Power Measurement (Telnet) ........................................................................ 27
RSSI Measurement (Telnet) ............................................................................... 28
Reporting Sheet / Checklists Remote Operation (NSP) RF Path Tests ............................ 29
Sequence of operations log .............................................................................. 29
Supporting Sheets / Checklists Node B Daisy Chain through Node B Activation .................. 31
Description .................................................................................................. 31
Node B Daisy Chain Activation ........................................................................... 31
Node B (A) Daisy Chaining Commissioning ............................................................. 31
Node B (B) Daisy Chaining Commissioning ............................................................. 32
NodeB (A) Daisy Chaining Activation.................................................................... 32
NodeB (A) Daisy Chain Configuration ................................................................... 33
Node B Daisy Chain Visual Check ........................................................................ 34
Reporting Sheet / Checklists Node B Daisy Chain through Node B Activation .................... 35
Sequence of operations log .............................................................................. 35
Supporting Sheets / Checklists Node B Daisy Chain Remote Checking - optional ................ 36
Description .................................................................................................. 36
Node B Daisy Chain Remote Checking .................................................................. 36
Log onto the Node B (A) (Telnet) ....................................................................... 36
Node B (A) Daisy Chaining Configuration Checking .................................................. 36
Node B (A) VLAN Id Checking ............................................................................ 37
Node B (A) Ethernet Port Checking ..................................................................... 37
Node B (A) Ethernet Port Counters Checking ......................................................... 38
Log onto the Node B (B) (Telnet) ....................................................................... 38
Node B (B) Daisy Chaining Configuration Checking................................................... 39
Node B (B) VLAN Id Checking............................................................................. 39
Node B (B) Ethernet Port Checking ..................................................................... 39
Node B (B) Ethernet Port Counters Checking ......................................................... 40
Log onto the WMS Server (Telnet) ...................................................................... 40
IP Ping of All Node B in Daisy Chain..................................................................... 41
Reporting Sheet / Checklists Node B Daisy Chain Remote Checking - optional .................. 42
Sequence of operations log .............................................................................. 42
Sign-Off Sheet .................................................................................................. 44

2 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Description .................................................................................................. 44
Meaning of Sign-Off Sheet ................................................................................ 44
Sign-Off Sheet .............................................................................................. 44
Archiving of reports ........................................................................................ 44

Jun 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA integration ..................................................... 7

Table 2: Applicable ALU Documents for WCDMA integration ...................................................... 8
Table 3: Used Documents .............................................................................................. 11
Table 4: Integration Checklists - BTS parameters ................................................................. 13
Table 5: Integration Checklists - Antenna Positions ............................................................... 13
Table 6: Integration Checklists - Call Test reporting ............................................................. 14
Table 7: Integration Checklists - Remote Operations ............................................................. 15
Table 8: RNC and BTS Name Report sheet ........................................................................ 17
Table 9: TX Power reporting sheet ................................................................................... 18
Table 10: RNC and BTS Name Report sheet ....................................................................... 19
Table 11: RTWP Measurements (WMS) Report sheet ............................................................ 20
Table 12: WMS Server Log-in Parameter Report sheet .......................................................... 21
Table 13: Node B log-in Parameter Report sheet ................................................................ 21
Table 14: Number of RE and Cells (Telnet) Report sheet ...................................................... 22
Table 15: RE Vendor Data (Telnet) Report sheet ................................................................ 22
Table 16: RE IP Address Checking (Telnet) Report sheet ....................................................... 23
Table 17: RX and TX Power Measurement (Telnet) Report sheet ............................................. 23
Table 18: Radio Element log-in Parameter (ASB) Report sheet ............................................... 24
Table 19: VSWR Measurement (ASB) Report sheet .............................................................. 24
Table 20: TX Power (ASB) Report sheet ........................................................................... 25
Table 21: RSSI Measurement (ASB) Report sheet ................................................................ 25
Table 22: Radio Element log-in Parameter (GPCS) Report sheet ............................................. 26
Table 23: VSWR measurement (GPCS) Report sheet ............................................................ 26
Table 24: PA Gain measurement (GPCS) Report sheet.......................................................... 27
Table 25: TX Power measurement (GPCS) Report sheet........................................................ 27
Table 26: RX Power measurement (GPCS) Report sheet........................................................ 28
Table 27: Antenna Functional Tests Checklists - Remote Operations .......................................... 29
Table 28: Node B (A) IP Address Report sheet ................................................................... 31
Table 29: Node B (A) Daisy Chaining Report sheet .............................................................. 31
Table 30: Node B (B) IP Address Report sheet .................................................................... 32
Table 31: Node B (B) Daisy Chained Report sheet ............................................................... 32
Table 32: Node B (A) Daisy Chaining Activation Report sheet ................................................. 32
Table 33: Node B Daisy Chain Configuration Report sheet ..................................................... 33
Table 34: Node B Daisy Chain Visual Check Report sheet ...................................................... 34
Table 35: Node B Daisy Chain Functional Activation Checklists - Remote Operations ...................... 35
Table 36: Node B (A) log-in Parameter Report sheet ........................................................... 36
Table 37: Node B (A) Daisy Chaining Configuration Report sheet ............................................. 36
Table 38: Node B (A) VLAN Id Report sheet ....................................................................... 37
Table 39: Node B (A) Ethernet Port Report sheet ............................................................... 37
Table 40: Node B (A) Ethernet Port Configuration Report sheet .............................................. 38
Table 41: Node B (A) Ethernet Port Counters Report sheet ................................................... 38
Table 42: Node B (B) log-in Parameter Report sheet ........................................................... 38
Table 43: Node B (B) Daisy Chaining Configuration Report sheet ............................................. 39
Table 44: Node B (B) VLAN Id Report sheet ....................................................................... 39
Table 45: Node B (B) Ethernet Port Report sheet ............................................................... 39
Table 46: Node B (B) Ethernet Port Configuration Report sheet .............................................. 40
Table 47: Node B (B) Ethernet Port Counters Report sheet.................................................... 40
Table 48: WMS Server Log-in Parameter Report sheet .......................................................... 40

4 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Table 49: Node B (B) IP Ping Report sheet ........................................................................ 41

Table 50: Node B Daisy Chain Functional Remote Tests Checklists - Remote Operations .................. 42
Table 51: Integration Checklists Customer sign-off ............................................................. 44

Jun 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

General

Section This section provides overview on Checklists for integration planning, execution and testing.
Description

Previous Release May 2013

Date

Release Notes Update: June 2014 - addition of the Node B Daisy Chain through Node B Activation and remote
Checking
Update: May 2013 - addition of RF measurements:
VSWR
TX Power
RSSI/RTWP

6 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

References

General This section utilizes Alcatel-Lucent product documents as well as handbook 521 sections to
perform the WCDMA Node B integration.

Documentation Links to applicable documents can be found under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN
/Documents/index.html

Use common Node B to find the latest applicable version.

Applicable IEH The sections listed in Table 1 below are required for WCDMA Node B integration.
521 sections

Table 1: Applicable IEH 521 Sections for WCDMA integration

Section Description
001 Introduction
401 Integration planning
402 Integration into existing UTRAN
410 Integration Testing
411 RF Path Testing
412 Ethernet OAM in the Node B - Testing
431 24 Cells and 12 Antenna Pairs Procedures
432 Hosting 2 Node Bs WCDMA in one d4U Procedures
433 External Alarm Logic Status Integration and Inversion Procedures
434 971x LR Cabinet Alarm Checking Configuration Procedures
435 NodeB Daisy Chaining through the Node B
436 NodeB Daisy Chain Remote Checking
499 Node B Integration Test Records

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

References, Continued

Applicable The following methods documents are required to perform the Node B integration
Methods
documents
Table 2: Applicable ALU Documents for WCDMA integration

Doc Number Doc Title URL

9YZ-03450- Alcatel-Lucent Node B Integration in an http://cic.us.alcatel-
4402-EFZZA existing UTRAN (UA08.x) lucent.com/pdfdocs6/pris
tore212/512696.pdf
WCDMA IM 30- Alcatel-Lucent Node B DHCP activation http://cic.us.alcatel-
3003 (UA08.x) lucent.com/pdfdocs6/pris
tore212/512584.pdf
9YZ-04088- Alcatel-Lucent Node B DHCP activation http://cic.us.alcatel-
0099-RJZZA (LR13.1) lucent.com/pdfdocs14/pri
store215/536074.pdf
9YZ-05870- Alcatel-Lucent Node B DHCP activation http://cic.us.alcatel-
0099-RJZZA (LR13.3) lucent.com/pdfdocs14/pri
store215/536084.pdf
WCDMA IM 64- Alcatel-Lucent Node B IMA activation http://cic.us.alcatel-
3004 (UA08.x) lucent.com/pdfdocs6/pris
tore212/512574.pdf
9YZ-04088- Alcatel-Lucent Node B IMA activation http://cic.us.alcatel-
0100-RJZZA (LR13.1) lucent.com/pdfdocs14/pri
store215/536076.pdf
9YZ-05870- Alcatel-Lucent Node B IMA activation http://cic.us.alcatel-
0100-RJZZA (LR13.3) lucent.com/pdfdocs14/pri
store215/549349.pdf
NN-20500-032 Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
System - User Guide (UA08.x) lucent.com/pdfdocs14/pri
store215/530471.pdf
9YZ-04088- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.1) lucent.com/pdfdocs14/pri
store215/562268.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.3) lucent.com/pdfdocs14/pri
store215/586415.pdf

Continued on next page

8 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

References, Continued

Applicable
Methods
Doc Number Doc Title URL
documents
(continued) UMT/OMC/DD/ SIE External UTRAN Alarm dictionary https://wcdma-
013913 ll.app.alcatel-
lucent.com/livelink/livelin
k.exe?func=ll&objId=663
77977&objAction=brows
e&viewType=1
NN-20500- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
018P1 UA08.1 System - Node B Alarms Reference Guide lucent.com/pdfdocs14/pri
(UA08.x) store215/524948.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0060-UFZZA System - Node B Alarms Reference Guide lucent.com/pdfdocs14/pri
(LR13.3) store215/536534.pdf

Jun 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Integration Checklists

Purpose Checklists are available to support and document the flow of operations before, during and post
integration for
On-site activities
Remote (WMS / NSP) operations
Remote Telnet operations
and document successful completion of integration and integration testing by customer
acceptance.

Checklists Used documents

overview
Reporting Sheet/Checklists - on site
BTS parameters
Antenna Positions
Communication Test
Reporting Sheet/Checklists remote operations (NSP)
Antenna Functional Tests - Preparation (WMS)
Logical & Physical Resources BTS Radio Power Table (WMS)
Antenna Functional Tests Telnet Preparation (telnet)
RE Test of ASB Product (2x60w or 60w-21C) (telnet)
RE Test of MTI-GPCS Product (60w-21)( telnet)
Node B Daisy Chain through Node B Activation
Node B Daisy Chain Remote Checking
Sign-Off Sheet

Checklist The checklists of IEH521 are generic and can be used as basis for further modifications and
customization enhancements as per specific customer / market requirements.

10 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Used Documents

Used Documents Document which versions of required documents are used for Node B integration:

Table 3: Used Documents

Document title Version

IEH521
Installation Engineering Handbook 521
WCDMA Node B (iBTS - Global Markets)
IEH523
Installation Engineering Handbook 523
Multi-Standard RF (Global Markets)
9YZ-03450-4402-EFZZA - UA08.x :
Alcatel-Lucent Node B Integration in an
existing UTRAN (UA08.x)
WCDMA IM 30-3003 - UA08.x :
Alcatel-Lucent Node B DHCP activation
(UA08.x)
WCDMA IM 64-3004 UA08.x :
Alcatel-Lucent Node B IMA activation
(UA08.x)
NN-20500-032 UA08.x :
Alcatel-Lucent 9353 Wireless Management
System - User Guide (UA08.x)
NN-20500-018P1 UA08.x :
Alcatel-Lucent 9353 Wireless Management
System - Node B Alarms Reference Guide
(UA08.x)
9YZ-04088-0099-RJZZA LR13.1 :
Alcatel-Lucent Node B DHCP activation
(LR13.1)
9YZ-04088-0100-RJZZA LR13.1 :
Alcatel-Lucent Node B IMA activation
(LR13.1)
9YZ-04088-0014-PCZZA LR13.1 :
Alcatel-Lucent 9353 Wireless Management
System - User Guide
(LR13.1)

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Used Documents, Continued

Used Documents
(continued)
Document title Version
9YZ-05870-0099-RJZZA LR13.3 :
Alcatel-Lucent Node B DHCP activation
(LR13.3)
9YZ-05870-0100-RJZZA LR13.3 :
Alcatel-Lucent Node B IMA activation
(LR13.3)
9YZ-05870-0014-PCZZA LR13.3 :
Alcatel-Lucent 9353 Wireless Management
System - User Guide
(LR13.3)
9YZ-05870-0060-UFZZA LR13.3 :
Alcatel-Lucent 9353 Wireless Management
System - Node B Alarms Reference Guide
(LR13.3)

12 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Reporting Sheets / Checklists - On Site

BTS Parameters BTS parameters must be documented and available before integration of the Node B starts:

Table 4: Integration Checklists - BTS parameters

Required information Node B specific value

BTS IP address Value:

WMS IP address Value:

Configuration Sectors:
Frequencies:

Software Version Node B SW version:

Hardware reference: Type of Node B and its hardware

components:

..
..
..
..

Software upgrade on BTS YES / NO: ..

NOTE: This information must be available for remote integration (NSP operations)

Antenna Antenna positions information must be made available prior to call test as part of the site
Positions specific information.

Table 5: Integration Checklists - Antenna Positions

Cell 1 2 3 4 5 6
Azimuth
Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Reporting Sheets / Checklists - On Site, Continued

Communication Following table must be filled out by on site integrator during / after successful communication
Test Results tests for a Node B:

Table 6: Integration Checklists - Call Test reporting

Sector 1 2 3 4 5 6
Frequency A
CS call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA
Video call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA
PS call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA
Frequency B
CS call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA
Video call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA
PS call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA
Frequency C
CS call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA
Video call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA
PS call test ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA

Overall Node B ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA ok / nok/ NA

Status (OK / NOK)

NOTE: This table has to be filled by the call tester during test and submitted for completion of
integration report.

14 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Reporting Sheet / Checklists Remote Operation

(NSP)

Sequence of The following integration procedures log table describes the sequence of operations and must
operations log be filled out by the OMC / NSP operator during the integration and integration testing:

Table 7: Integration Checklists - Remote Operations

Step Procedure Condition To Ok Nok

Apply
1 Setup PC for OAM client Optional only first time for PC [Y]
setting
2 Connect to WMS and start session Y
3 Check RNC alarm and layout conditions Y
4 Export Network Configuration Data Y
5 Work order creation for a new Node B N/A
6 Work order import Y
7 Pre-checks before activation Y
8 Node B - creation Y
9 Move of new Node B into layout Y
10 Update Node B NeID Y
11 Node B OAM link state change and Y
activation
12 PSU alarm integration in small cabinet Optional Configuration [Y]
dependent
13 PSU alarm integration in medium cabinet Optional Configuration [Y]
dependent
14 Node B online tests Check of alarms Y
15 Circuit Switched call test On-Site activity required Y
16 Video Call Test On-Site activity required Y
17 Packet Switched Call Test On-Site activity required Y
18 Unlock of FDD cells Y
19 External PSU alarms test Optional Configuration [Y]
dependent
On-Site activity required

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Reporting Sheet / Checklists Remote Operation

(NSP), Continued

Sequence of operations log (continued)

Step Procedure Condition To Ok Nok

Apply
20 Creation of layout in WMS Optional - Only if required [Y]
21 Edit layout in WMS Optional - Only if required [Y]
22 View layout in WMS Optional - Only if required [Y]

Additional comments/remarks:

16 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Reporting Sheets / Checklists TX Power Test

through remote operation (WMS)
TX Power The following information has to be recorded to asses TX Power correctness of a Node B:
measurement FDD cell status: locked or unlocked
Sector number
pcpich Power value (dBm)
TX_3GPP power value (dBm)
TX_DDM power value (dBm)

RNC and BTS Record Node B and RNC name of the tested Node B for reference in belows table
name under test

Table 8: RNC and BTS Name Report sheet

RNC Name BTS Name

TX Power The following reporting table shall be used to record the test results and measurements for the
measurement TX Power tests as they are defined in IEH521, Section 410 and assess the result:
results RF Path Tests with WMS - Preparation
RF Path Tests with WMS BTS Radio Power tab

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Reporting Sheets / Checklists TX Power Test

through remote operation (WMS), Continued
Table 9: TX Power reporting sheet
FDD FDDCell Sector (antenna pcpichPower Tx_3GPP Tx_DDM TX
Cell # Status connector_...) Value (dBm) (dBm) Power
tick result antenna connector_... tick result
Locked /
0 Unlocked (dBm) OK / NOK
1 Locked / (dBm) OK / NOK
Unlocked
2 Locked / (dBm) OK / NOK
Unlocked
3 Locked / (dBm) OK / NOK
Unlocked
4 Locked / (dBm) OK / NOK
Unlocked
5 Locked / (dBm) OK / NOK
Unlocked
6 Locked / (dBm) OK / NOK
Unlocked
7 Locked / (dBm) OK / NOK
Unlocked
8 Locked / (dBm) OK / NOK
Unlocked
9 Locked / (dBm) OK / NOK
Unlocked
10 Locked / (dBm) OK / NOK
Unlocked
11 Locked / (dBm) OK / NOK
Unlocked

18 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Reporting Sheets / Checklists RX Tests through

remote operation (WMS)

RTWP The following information has to be recorded to asses RX of the Node B:

measurements
FDD cell status: locked or unlocked
Sector number
RTWP value main branch (dBm)
RTWP value diversity branch (dBm)
RTWP value combined (main & diversity) (dBm)
RTWP value reference (dBm)

RNC and BTS Record Node B and RNC name of the tested Node B for reference in belows table
name under test

Table 10: RNC and BTS Name Report sheet

RNC Name BTS Name

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Reporting Sheets / Checklists RX Tests through

remote operation (WMS), Continued

RTWP The following reporting table shall be used to record the test results and measurements for the
measurement TX Power tests as they are defined in IEH521, Section 410 and assess the result:
results RF Path Tests with WMS Preparation
RF Path Tests with WMS BTS Radio Power tab

Table 11: RTWP Measurements (WMS) Report sheet

FDD FDDCell Sector (antenna RTWP RTWP RTWP RTWP RTWP
Cell # Status connector_...) Main Div Combined Reference
(dBm) (dBm) (dBm) (dBm)
tick result antenna connector_.. tick result
0 Locked /
Unlocked OK / NOK
1 Locked / OK / NOK
Unlocked
2 Locked / OK / NOK
Unlocked
3 Locked / OK / NOK
Unlocked
4 Locked / OK / NOK
Unlocked
5 Locked / OK / NOK
Unlocked
6 Locked / OK / NOK
Unlocked
7 Locked / OK / NOK
Unlocked
8 Locked / OK / NOK
Unlocked
9 Locked / OK / NOK
Unlocked
10 Locked / OK / NOK
Unlocked
11 Locked / OK / NOK
Unlocked

20 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets & Checklists RF Path Health

Check and Telnet Preparation Optional

Description The following sheets and checklists are available to support the health check activity for
TX Power
RX branches
of a Node B through remote Telnet commands.

Telnet The following values table can be used by the OMC / NSP operator during the Antenna
Preparation Functional Tests - Telnet Preparation through Telnet commands:

Log-in to the Report sheet for WMS log-in parameter used for telnet connection.
WMS Server
(Telnet)
Table 12: WMS Server Log-in Parameter Report sheet
WMS IP Address WMS Login WMS Password
IP@: ___ . ___ . ___ . ___

Log-in to the Report sheet for Node B log-in parameter used for telnet connection.
Node B (Telnet)

Table 13: Node B log-in Parameter Report sheet

Node B IP Address Login Password

IP@: ___ . ___ . ___ . ___

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets & Checklists RF Path Health

Check and Telnet Preparation Optional, Continued

Display Data Report sheet for Data List of all RE (Number of RE and Cells) through Telnet commands.
List of all Radio
Element
(Telnet) Table 14: Number of RE and Cells (Telnet) Report sheet

Number of RE Connected NumberOfCells RE IP Address

192.168.129.1
192.168.130.1
192.168.131.1
192.168.132.1
192.168.133.1
192.168.134.1

Report sheet for Data List of all RE (RE Vendor, RuName, PecCode, Serial Number)
through Telnet commands.

Table 15: RE Vendor Data (Telnet) Report sheet

CPRI RE Vendor RuName PecCode SerialNumber
Link #
1
2
3
4
5
6

Continued on next page

22 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets & Checklists RF Path Health

Check and Telnet Preparation Optional, Continued

Rx Power and Report sheet for RE IP Address check with the Data List through Telnet commands.
Tx Power
Measurements
of each Table 16: RE IP Address Checking (Telnet) Report sheet
LocalCell ID
(Telnet) Check x RE (RRH Syntax IP Address
values or TRDU) Example
(OK/NOK)
CPRI Link 1 1 11 Reproxy | show 1 192.168.129.1
CPRI Link 2 2 21 Reproxy | show 2 192.168.130.1
CPRI Link 3 3 31 Reproxy | show 3 192.168.131.1
CPRI Link 4 4 41 Reproxy | show 4 192.168.132.1
CPRI Link 5 5 51 Reproxy | show 5 192.168.133.1
CPRI Link 6 6 61 Reproxy | show 6 192.168.134.1

Report sheet for RX and TX Power measurement values through Telnet commands.

Table 17: RX and TX Power Measurement (Telnet) Report sheet

RxPower (dBm) TxPowerCell (%) TxPowerCell (%)

LocalCell
ID # Main Div Comb Main Div
To Call
Main Div
To
IP Call IP
0
1
2
3
4
5
6

Jun 30, 2014 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets / Checklists RF Path Test for

ASB RRH Products (2x60 or 60-21C) - optional

Description The following sheets and checklists are available to support the trouble shooting activity for
TX Power
RX branches
of a Node B with RRHs from supplier ASB through remote Telnet commands.

RE Tests results The following reporting sheets can be filled out by the OMC / NSP operator during the Antenna
of ASB Product Functional Tests of RE ASB products through Telnet commands

Log-in to the Report sheet for the Radio Element log-in parameters used for the Telnet connection.
Radio Element
(Telnet)
Table 18: Radio Element log-in Parameter (ASB) Report sheet
RE IP Address Login Password RU Name PEC Code
192.168.129.1
192.168.130.1
192.168.131.1
192.168.132.1
192.168.133.1
192.168.134.1

VSWR Report sheet for the VSWR measurement values of ASB Products through Telnet commands.
Measurement
(Telnet)
results report Table 19: VSWR Measurement (ASB) Report sheet
CPRI
RE IP Address VSWR Value CLI (OK/NOK)
Link #
1 192.168.129.1
2 192.168.130.1
3 192.168.131.1
4 192.168.132.1
5 192.168.133.1
6 192.168.134.1

Continued on next page

24 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets / Checklists RF Path Test for

ASB RRH Products (2x60 or 60-21C) - optional,
Continued

TX Power Report sheet for TX Power measurement results of ASB Products through Telnet commands.
Measurement
(Telnet)
results report Table 20: TX Power (ASB) Report sheet

CPRI TX Power Value CLI

RE IP Address
Link # TX 1 (dBm) TX 2 (dBm) (OK/NOK)
1 192.168.129.1
2 192.168.130.1
3 192.168.131.1
4 192.168.132.1
5 192.168.133.1
6 192.168.134.1

RSSI Report sheet for RSSI Power measurement of ASB Products through Telnet commands.
Measurement
(Telnet)
results report Table 21: RSSI Measurement (ASB) Report sheet

CPRI RSSI Power Value CLI

RE IP Address
Link # RX 1 (dBm) RX 2 (dBm) (OK/NOK)
1 192.168.129.1
2 192.168.130.1
3 192.168.131.1
4 192.168.132.1
5 192.168.133.1
6 192.168.134.1

Jun 30, 2014 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets / Checklists RF Path Tests for

MTI - GPCS RRH (60w-21) - optional

Description The following sheets and checklists are available to support the trouble shooting activity for
TX Power
RX branches
of a Node B with RRHs from supplier GPCS through remote Telnet commands.

RE Tests of GPCS The following reporting sheets can be filled out by the OMC / NSP operator during the Antenna
Product Functional Tests of RE GPCS products through Telnet commands

Log-in to the Report for Radio Element log-in parameter used for Telnet connection.
Radio Element
(Telnet)
Table 22: Radio Element log-in Parameter (GPCS) Report sheet
CPRI Link # RE IP Address RU Name PEC Code
1 192.168.129.1
2 192.168.130.1
3 192.168.131.1
4 192.168.132.1
5 192.168.133.1
6 192.168.134.1

VSWR Report for VSWR measurement results of the MTI-GPCS product through Telnet commands.
Measurement
(Telnet)
Table 23: VSWR measurement (GPCS) Report sheet
CPRI Raw VSWR Ave. VSWR Return Loss
RE IP Address
Link # Meas. Meas. (dB)
1 192.168.129.1
2 192.168.130.1
3 192.168.131.1
4 192.168.132.1
5 192.168.133.1
6 192.168.134.1

Continued on next page

26 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets / Checklists RF Path Tests for

MTI - GPCS RRH (60w-21) - optional, Continued

PA Gain Report for PA Gain measurement result of the MTI-GPCS products through Telnet
Measurement commands.
(Telnet)

Table 24: PA Gain measurement (GPCS) Report sheet

CPRI PA Gain
Link # Freq 0 Freq 1 Freq 2 Freq 3 Freq 4 Freq 5
1
2
3
4
5
6

TX Power Report for TX Power measurement of the MTI-GPCS products through Telnet commands.
Measurement
(Telnet)
Table 25: TX Power measurement (GPCS) Report sheet

CPRI TX Power Value (dBm)

Link # Channel 0 Channel 1 Channel 2 Channel 3

1
2
3
4
5
6

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets / Checklists RF Path Tests for

MTI - GPCS RRH (60w-21) - optional, Continued

RSSI Report for RSSI (RX Power) measurement of the MTI-GPCS products through Telnet
Measurement commands.
(Telnet)

Table 26: RX Power measurement (GPCS) Report sheet

CPRI RX Power Value (dBm)

Link # RX Diversity 0 RX Diversity 1 RX Diversity 2 RX Diversity 3

1
2
3
4
5
6

28 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Reporting Sheet / Checklists Remote Operation

(NSP) RF Path Tests

Sequence of The following Antenna Functional Tests procedures log table describes the sequence of
operations log operations and must be filled out by the OMC / NSP operator during the integration and
integration testing

Table 27: Antenna Functional Tests Checklists - Remote Operations

Step Procedure Condition To Ok Nok
Apply
1 Setup PC for OAM client Optional only first time for PC [Y]
setting
2 Connect to WMS and start session Y
3 Unlock the FDDCells Y
RF path tests preparation for
4 Check the pcpichPower of the FDDCell RF components from all Y
suppliers
5 Select the Measurement solution Y
6 BTS Radio Power Measurement Y
RF path tests for RF
7 RTWP measurement Y
components from all suppliers
8 TX Power measurement Y
9 Log-in to the WMS Server with Telnet Optional
Commands
10 Log-in to the Node B with Telnet Commands RF path health check (possible Optional
for RF components from all
11 Display Data List of all Radio Elements Optional
suppliers). Should be used as
12 Display Data List of One Radio Elements first level trouble shooting Optional
13 Log-in to the Radio Element with Telnet Optional
Commands
14 RE Test for ASB RRH Product Optional
15 VSWR Measurement RF path tests for trouble Optional
shooting for RRH from supplier
16 TX Power Measurement ASB Optional
17 RSSI Measurement Optional

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Reporting Sheet / Checklists Remote Operation

(NSP) RF Path Tests, Continued

Sequence of operations log (continued)

Step Procedure Condition To Ok Nok

Apply
18 RE Test for GPCS Product Optional
19 VSWR Measurement Optional
RF path tests for trouble
20 PA Gain Measurement shooting for RRH from supplier Optional
MTI-GPCS
21 TX Power Measurement Optional
22 RSSI Measurement Optional
23 Logout the Radio Element Local Terminal Optional

Additional comments/remarks:

30 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets / Checklists Node B Daisy Chain

through Node B Activation

Description The following sheets and checklists are available for the Node B Daisy Chaining through Node
B activation.

Node B Daisy The following reporting sheets can be filled out by the OMC / NSP operator during the Node B
Chain Daisy Chain through Node B activation.
Activation

Node B (A) Report sheet for Node B (A) Daisy Chaining commissioning parameters using TIL
Daisy Chaining connection.
Commissioning

Table 28: Node B (A) IP Address Report sheet

Node B (A) IP Address Login Password

IP@: ___ . ___ . ___ . ___ nodeb nodeblnx

Table 29: Node B (A) Daisy Chaining Report sheet

I&C Parameter Parameter value Selected
Backhaul | Type of incoming Link GIGABIT EHERNET Yes / No
MDA SFP1 Yes / No
Ethernet | Eth Port used for Iub IF
(For Backhaul link on Ethernet Port/0 MDA SFP2 Yes / No
of Node B (A))
MDA RJ45 Yes / No

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets / Checklists Node B Daisy Chain

through Node B Activation, Continued

Node B (B) Report sheet for Node B (B) Daisy Chained commissioning parameters using TIL
Daisy Chaining connection.
Commissioning

Table 30: Node B (B) IP Address Report sheet

Node B (B) IP Address Login Password

IP@: ___ . ___ . ___ . ___ nodeb nodeblnx

Table 31: Node B (B) Daisy Chained Report sheet

I&C Parameter Parameter value Selected

Backhaul | Type of incoming Link GIGABIT EHERNET Yes / No
MDA SFP1 Yes / No
Ethernet | Eth Port used for Iub IF
(For Backhaul link on Ethernet Port/0 MDA SFP2 Yes / No
of Node B (B))
MDA RJ45 Yes / No

NodeB (A) Daisy Report sheet for Node B (A) Daisy Chaining Activation with NSP GUI connection.
Chaining
Activation
Table 32: Node B (A) Daisy Chaining Activation Report sheet

Parameter Attribute Value Selection

Ethernet - Port /0 Port Role Backhaul OK / Not OK
Ethernet - Port /1 Port Role Daisy Chaining OK / Not OK
IP Ran IsBackhauldaisyChain TRUE TRUE / FALSE
ingActivated

Continued on next page

32 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets / Checklists Node B Daisy Chain

through Node B Activation, Continued

NodeB (A) Daisy Report sheet for Node B Daisy Chain Configuration.
Chain
Configuration
Table 33: Node B Daisy Chain Configuration Report sheet

Ethernet Port /0 Ethernet Port /1 Ports

Node B
Backhaul Port Daisy chaining Port Used
MDA SFP2 Yes / No
MDA SFP1 connected to
Node B (A) MDA RJ45 Yes / No
Daisy chaining MDA SFP2 connected to Yes / No
MDA SFP1
MDA RJ45 connected to Yes / No
MDA SFP1 Yes / No
Node B (B)
MDA SFP2 Yes / No
Daisy chained
MDA RJ45 Yes / No

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets / Checklists Node B Daisy Chain

through Node B Activation, Continued

Node B Daisy Report sheet for visual check of Node B Daisy Chain with TIL GUI.
Chain Visual
Check
Table 34: Node B Daisy Chain Visual Check Report sheet

GE MDA
GE MDA
Port
Node B Port LED color LED color Status
Daisy
Backhaul
Chaining
SFP1 .. SFP1 .. OK / Not OK
Node B (A)
Daisy SFP2 .. SFP2 .. OK / Not OK
chaining
RJ45 .. RJ45 .. OK / Not OK
SFP1 .. OK / Not OK
Node B (B)
Daisy SFP2 .. OK / Not OK
chained
RJ45 .. OK / Not OK

NOTE: Use the following color code to identified the status of the LED color of the GE MDA
Ethernet port:
W: White (Port available, not used.)
G: Green (Up and running)
B: Black (Not usable.)
R: Red (Used, alarm)
O: Orange (Port administratively locked)

NOTE: MDA SFP2 and MDA RJ45 cannot be used simultaneously. (mutually exclusive)

34 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Reporting Sheet / Checklists Node B Daisy Chain

through Node B Activation

Sequence of The following Node B Daisy Chain through Node B Activation procedures log table describes
operations log the sequence of operations and must be filled out by the OMC / NSP operator during the Node
B Daisy Chain activation:

Table 35: Node B Daisy Chain Functional Activation Checklists - Remote Operations
Step Procedure Condition To Ok Nok
Apply
1 Node B (A) Daisy Chaining Commissioning - To Configure the Backhaul link Y
TIL on the Ethernet Port/0 of Node
B (A)
2 Node B (B) Daisy Chained Commissioning - To Configure the Backhaul link Y
TIL on the Ethernet Port/0 of Node
B (B)
3 Node B (A) Daisy Chaining Pre-Check To pre-check the Ethernet Port Y
before Activation -WMS parameters of Node B (A)
before Daisy chain activation
4 Node B (A) Daisy Chaining Ethernet Port/0 To set the Ethernet Port/0 of Y
Configuration Procedure -WMS Node B (A) with Port Role in
Backhaul (MBH)
5 Node B (A) Daisy Chaining Ethernet Port/1 To set the Ethernet Port/1 of Y
Configuration Procedure -WMS Node B (A) with Port Role in
Daisy Chaining (DC)
6 Node B (A) Daisy Chaining IP Ran To set the IP Ran Parameter of Y
Configuration Procedure -WMS Node B (A) to TRUE
7 Node B (A) Daisy Chaining Validation To validate Node B (A) is in Y
Daisy chaining configuration
8 Node B (B) Daisy Chained Validation To validate Node B (B) isin Y
Daisy chained configuration

Additional comments/remarks:

Jun 30, 2014 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets / Checklists Node B Daisy Chain

Remote Checking - optional

Description The following sheets and checklists are available to support the trouble shooting activity for
Node B Daisy Chain checking through remote Telnet commands.

Node B Daisy The following reporting sheets can be filled out by the OMC / NSP operator during the Node B
Chain Remote Daisy Chain Tests through Telnet commands.
Checking

Log onto the Report sheet for Node B (A) log-in parameter used for telnet connection.
Node B (A)
(Telnet)
Table 36: Node B (A) log-in Parameter Report sheet
Node B IP Address Login Password
IP@: ___ . ___ . ___ . ___ nodeB nodeblnx

Node B (A) Report sheet for Node B (A) Daisy Chaining Configuration checked with telnet connection.
Daisy Chaining
Configuration
Checking Table 37: Node B (A) Daisy Chaining Configuration Report sheet

Node B (A) Configuration Mode Status

BTS Iub Mode Native IP OK / Not OK
Node B link to OMC-B Connected OK / Not OK
MIB State Build OK / Not OK
Minimum Software version UNB0911xxxx OK / Not OK
st
1 Ethernet Ports id #
#1 #2 #3
(for Backhaul)
st
1 HW Type (Ethernet Config.) SFP1 SFP2 RJ45 Active / Not Active
nd
2 Ethernet Ports id #
#1 #2 #3
(for Daisy Chain)
nd
2 HW Type (Ethernet Config.) SFP1 SFP2 RJ45 Active / Not Active

Continued on next page

36 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets / Checklists Node B Daisy Chain

Remote Checking - optional, Continued

Node B (A) Report sheet for Node B (A) VLAN Id checked with telnet connection.
VLAN Id
Checking
Table 38: Node B (A) VLAN Id Report sheet

Type of Traffic for Type of Traffic for

Node B (A) VLAN Id
CP and UP OAM
VirtualInterface number : 0 1
IpAddress : IP@: ___ . ___ . ___ . ___ IP@: ___ . ___ . ___ . ___
VlanId parameter value :

Node B (A) Report sheet for Node B (A) Ethernet Port checked with telnet connection.
Ethernet Port
Checking
Table 39: Node B (A) Ethernet Port Report sheet
Node B (A) Configuration Ethernet Port Status
st
1 Ethernet Ports id # and Link Up #1 #2 #3 Up / Down
st
1 HW Type (Ethernet Config.) SFP1 SFP2 RJ45 Enable / Disable
nd
2 Ethernet Ports id # and Link Up #1 #2 #3 Up / Down
nd
2 HW Type (Ethernet Config.) SFP1 SFP2 RJ45 Enable / Disable

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets / Checklists Node B Daisy Chain

Remote Checking - optional, Continued

Node B (A) Report sheet for Node B (A) Ethernet Port Counters checked with telnet connection.
Ethernet Port
Counters
Checking Table 40: Node B (A) Ethernet Port Configuration Report sheet

Node B (A) Configuration Mode Status

Daisy chain features Activated OK / Not OK
Backhaul Port SFP1 SFP2 RJ45
Daisy chain Port SFP1 SFP2 RJ45

Table 41: Node B (A) Ethernet Port Counters Report sheet

Node B (A) Ethernet Observed Counters of Status
Port Frames Octets
Rx Frames Expected value 0 OK / Not OK
SFP1
Tx Frames Expected value 0 OK / Not OK
Rx Frames Expected value 0 OK / Not OK
SFP2
Tx Frames Expected value 0 OK / Not OK
Rx Frames Expected value 0 OK / Not OK
RJ45
Tx Frames Expected value 0 OK / Not OK

Log onto the Report sheet for Node B (B) log-in parameter used for telnet connection.
Node B (B)
(Telnet)
Table 42: Node B (B) log-in Parameter Report sheet
Node B IP Address Login Password
IP@: ___ . ___ . ___ . ___ nodeB nodeblnx

Continued on next page

38 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets / Checklists Node B Daisy Chain

Remote Checking - optional, Continued

Node B (B) Report sheet for Node B (B) Daisy Chaining Configuration checked with telnet connection.
Daisy Chaining
Configuration
Checking Table 43: Node B (B) Daisy Chaining Configuration Report sheet

Node B (B) Configuration Mode Status

BTS Iub Mode Native IP OK / Not OK
Node B link to OMC-B Connected OK / Not OK
MIB State Build OK / Not OK
Minimum Software version UNB0911xxxx OK / Not OK
st
1 Ethernet Ports id # (for Backhaul) #1 #2 #3
st
1 HW Type (Ethernet Config.) SFP1 SFP2 RJ45 Active / Not Active

Node B (B) Report sheet for Node B (B) VLAN Id checked with telnet connection.
VLAN Id
Checking
Table 44: Node B (B) VLAN Id Report sheet

Type of Traffic for Type of Traffic for

Node B (B) VLAN Id
CP and UP OAM
VirtualInterface number : 0 1
IpAddress : IP@: ___ . ___ . ___ . ___ IP@: ___ . ___ . ___ . ___
VlanId parameter value :

Node B (B) Report sheet for Node B (B) Ethernet Port checked with telnet connection.
Ethernet Port
Checking
Table 45: Node B (B) Ethernet Port Report sheet

Node B (B) Configuration Ethernet Port Status

Ethernet Ports id # and Link Up #1 #2 #3 Up / Down
HW Type (Ethernet Config.) SFP1 SFP2 RJ45 Enable / Disable

Continued on next page

Jun 30, 2014 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Supporting Sheets / Checklists Node B Daisy Chain

Remote Checking - optional, Continued

Node B (B) Report sheet for Node B (B) Ethernet Port Counters checked with telnet connection.
Ethernet Port
Counters
Checking Table 46: Node B (B) Ethernet Port Configuration Report sheet

Node B (B) Configuration Mode Status

Daisy chain feature Deactivated OK / Not OK
Backhaul Port SFP1 SFP2 RJ45
Daisy chain Port Null Null Null

Table 47: Node B (B) Ethernet Port Counters Report sheet

Node B (B) Ethernet Observed Counters of Status
Port Frames Octets
Rx Frames Expected value 0 OK / Not OK
SFP1
Tx Frames Expected value 0 OK / Not OK
Rx Frames Expected value 0 OK / Not OK
SFP2
Tx Frames Expected value 0 OK / Not OK
Rx Frames Expected value 0 OK / Not OK
RJ45
Tx Frames Expected value 0 OK / Not OK

Log onto the Report sheet for WMS log-in parameter used for telnet connection.
WMS Server
(Telnet)
Table 48: WMS Server Log-in Parameter Report sheet
WMS IP Address WMS Login WMS Password
IP@: ___ . ___ . ___ . ___

Continued on next page

40 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Supporting Sheets / Checklists Node B Daisy Chain

Remote Checking - optional, Continued

IP Ping of All Report sheet for IP Ping test of all Node B from WMS server using telnet connection.
Node B in Daisy
Chain
Table 49: Node B (B) IP Ping Report sheet

Node B IP Ping Node B IP Address Status

Node B (B) Daisy Chained IP@: ___ . ___ . ___ . ___ Is alive / No answer
Node B (A) Daisy Chaining IP@: ___ . ___ . ___ . ___ Is alive / No answer

Jun 30, 2014 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Reporting Sheet / Checklists Node B Daisy Chain

Remote Checking - optional

Sequence of The following Node B Daisy Chain Tests procedures log table describes the sequence of
operations log operations and must be filled out by the OMC / NSP operator during the Daisy Chain Remote
checking:

Table 50: Node B Daisy Chain Functional Remote Tests Checklists - Remote Operations

Step Procedure Condition To Ok Nok

Apply
1 Node B in Daisy Chain Telnet Log onto Y
WMS Server Procedure
2 IP Ping of All Node B in Daisy Chain - Y
Testing Procedure
3 Node B Daisy Chaining Telnet Log onto If necessary to trouble shoot Optional
Node B the Node B in Daisy Chain
configuration
4 Node B (A) Daisy Chaining Configuration To check the Node B (A) in Optional
Checking Procedure Daisy Chaining configuration If
necessary
5 Node B (A) VLAN Id Checking Procedure To check the VLAN Id of Node Optional
B (A) If necessary
6 Node B (A) Ethernet Port Checking To check the Ethernet Port of Optional
Procedure Node B (A) If necessary
7 Node B (A) Ethernet Port Counters To check the Ethernet Port Optional
Checking Procedure Counters of Node B (A) If
necessary
8 Node B (B) Daisy Chained Configuration To check the Node B (B) in Optional
Checking Procedure Daisy Chained configuration If
necessary
9 Node B (B) VLAN Id Checking Procedure To check the VLAN Id of Node Optional
B (B) If necessary
10 Node B (B) Ethernet Port Checking To check the Ethernet Port of Optional
Procedure Node B (B) If necessary
11 Node B (B) Ethernet Port Counters To check the Ethernet Port Optional
Checking Procedure Counters of Node B (B) If
necessary

Continued on next page

42 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
Node B Integration Test Records IEH 521, Section 499

Reporting Sheet / Checklists Node B Daisy Chain

Remote Checking - optional, Continued

Additional comments/remarks:

Jun 30, 2014 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 499 Node B Integration Test Records

Sign-Off Sheet

Description Sign-Off sheet has to be completed to finalize and document acceptance of the integration
results.

Meaning of Sign- Completion of the Sign-Off sheet represents the finalization of the Node B integration activity
Off Sheet and is meant to serve for customer acceptance of the integrated Node B.

Sign-Off Sheet The following sign-off confirms that all required checklists proof successful integration of the
Node B:

Table 51: Integration Checklists Customer sign-off

OMC/NSP Coordinator / Customer
engineer on-Site Representative
activities
Company Name

Function
Name
Signature

Date

Archiving of All integration test records for an individual Node B integration must be archived.
reports Individual contractual agreements with customer may require the original to hand over the
integration test records to the customer for archiving.

44 Alcatel-Lucent Internal Jun 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 701

December 15, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

d2U/BBU to d4U Migration Procedure

Table of Contents

General ............................................................................................................ 4
Scope of migration ........................................................................................... 4
Scope restriction ............................................................................................. 4
Supported Node B types .................................................................................... 4
Operational Impacts ......................................................................................... 5
Previous Release Date ....................................................................................... 5
Release Notes ................................................................................................. 5
References ........................................................................................................ 6
General ........................................................................................................ 6
Documentation Access ...................................................................................... 6
Applicable IEH521 Sections ................................................................................. 6
Applicable Methods Documents............................................................................ 7
Tools Requirements ............................................................................................. 9
General ........................................................................................................ 9
Hardware Tools ............................................................................................... 9
Material Requirements ....................................................................................... 10
General ...................................................................................................... 10
Hardware requirements and order information ...................................................... 10
Cable re-usage .............................................................................................. 10
Record Sheet ................................................................................................... 11
Description .................................................................................................. 11
Input parameter sheet .................................................................................... 11
Antenna positions sheet .................................................................................. 12
Communication test results sheet ...................................................................... 12
Self test results sheet ..................................................................................... 13
Sign-off sheet ............................................................................................... 14
d2U/BBU to d4U Migration Overview ...................................................................... 15
Description .................................................................................................. 15
D2U/BBU replacement to d4U flow diagram .......................................................... 15
D2U/BBU replacement to d4U overview ............................................................... 16
Precautions ..................................................................................................... 17
Description .................................................................................................. 17

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Safety related information ............................................................................... 17

Equipment Safety Requirements ........................................................................ 17
Preparations before d2U / BBU to d4U migration procedure execution ............................. 18
Description .................................................................................................. 18
Power / Energy requirements ............................................................................ 18
Transport reconfiguration requirements ............................................................... 18
Final Material Checks ...................................................................................... 18
Pre-Installation Checklist ................................................................................. 18
Initial Check and alarm clearance ...................................................................... 19
d2U/BBU - overview ....................................................................................... 19
9926 d4U - overview ...................................................................................... 20
xCCM-U with MDA E1/T1 front view .................................................................. 21
xCCM-U with MDA GE front view....................................................................... 21
eCCM-U with MDA GE / eCCM-U with MDA E1/T1 front view ..................................... 21
Proc. 1: d2U/BBU Sanity Check ............................................................................. 22
Description .................................................................................................. 22
Pre requisites ............................................................................................... 22
Visual Check................................................................................................. 23
Proc. 2: Lock Cell(s) & Site .................................................................................. 24
Description .................................................................................................. 24
Lock D2U/BBU Cells & site ............................................................................... 24
Proc. 3: d2U/BBU Power off ................................................................................. 26
Description .................................................................................................. 26
D2U/BBU Power off ........................................................................................ 26
Proc. 4: d2U/BBU Cables Disconnection ................................................................... 28
Description .................................................................................................. 28
D2U/ BBU .................................................................................................... 28
Dallas bus disconnection procedure .................................................................... 28
GPS module link disconnection procedure............................................................. 29
D2U/BBU backhaul cables options ...................................................................... 30
E1/T1 disconnection procedure xCCM-U + MDA E1/T1 w/ LPPCM ............................. 30
E1/T1 disconnection procedure xCCM-U + MDA E1/T1 wo/ LPPCM ............................ 31
E1/T1 disconnection procedure xCCM-U + MDA GE w/ LPPCM ................................. 31
E1/T1 disconnection procedure xCCM-U + MDA GE wo/ LPPCM ................................ 32
E1/T1 disconnection procedure eCCM-U + MDA GE w/ LPPCM ................................. 32
E1/T1 disconnection procedure eCCM-U + MDA GE wo/ LPPCM ................................ 33
IP disconnection procedure xCCM-U + MDA GE / eCCM-U + MDA GE electrical.............. 34
IP disconnection procedure xCCM-U + MDA GE / eCCM-U + MDA GE optical ................. 36
Radio Unit - optical link disconnection procedure ................................................... 37
Alarm cable disconnection procedure .................................................................. 37
Power cable disconnection procedure ................................................................. 38
GND Disconnection ......................................................................................... 39
Proc. 5: LPPCM module move ............................................................................... 40
Description .................................................................................................. 40
LPPCM Module removal ................................................................................... 40
Proc. 6: iEAM module move ................................................................................. 41
Description .................................................................................................. 41
iEAM Module removal ...................................................................................... 41
Proc. 7: Removal of d2U/BBU ............................................................................... 42
Description .................................................................................................. 42
Removal procedure ........................................................................................ 42

2 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 8: 9926 d4U Installation ............................................................................... 43

Description .................................................................................................. 43
D4U Installation procedure ............................................................................... 43
Proc.9: 9926 d4U Commissioning .......................................................................... 44
Description .................................................................................................. 44
D4U Commissioning procedure ........................................................................... 44
Proc. 10: 9926 d4U Integration ............................................................................. 45
Description .................................................................................................. 45
D4U Integration ............................................................................................. 45
Proc. 11: Final Checks and Clean-up ....................................................................... 46
Description .................................................................................................. 46
Final checks and clean-up procedure................................................................... 46

List of Figures

Figure 1: d2U / BBU to d4U migration flow chart ................................................................ 15

Figure 2: d2U/BBU overview .......................................................................................... 19
Figure 3: 9926 d4U overview .......................................................................................... 20
Figure 4: xCCM-U with MDA E1/T1 ................................................................................... 21
Figure 5: xCCM-U with MDA GE ....................................................................................... 21
Figure 6: eCCM-U with MDA GE or with MDA E1/T1 ............................................................... 21

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA d2U/BBU to d4U migration .................................. 6
Table 2: Applicable methods documents .............................................................................. 7
Table 3: Hardware Tools ................................................................................................. 9
Table 4: Hardware material requirements and order information ............................................. 10
Table 5: Input parameters ............................................................................................. 11
Table 6: Antennae Positions ........................................................................................... 12
Table 7: Communication Test ......................................................................................... 12
Table 8: NodeB Digital Shelf BISTS Results (applicable for all NodeBs) ....................................... 13
Table 9: Sequence of Operations ..................................................................................... 14
Table 10: Sign Off ....................................................................................................... 14
Table 11: d2U/BBU replacement to d4U overview ................................................................ 16
Table 14: CCM-U board backhaul configurations .................................................................. 30
Table 13: Installation procedures .................................................................................... 43
Table 14: Commissioning procedures ................................................................................ 44
Table 15: Integration procedures ..................................................................................... 45

December 15, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

General

Scope of This section provides detailed information how to perform the migration from d2U/BBU to the 9926
migration d4U.

Scope Migration of CCM-U board types and backhaul interfaces and migration of CEM-U board types
restriction are not in the scope of this procedure. Separate procedures are available inside the IEH521 to
support
CCM-U and backhaul interface migration
CEM-U migration

NOTE: If demanded the migrations of d2U/BBU, CCM-U and/or CEM-U should be carried out
together, following their individual procedures.

Supported Node The following table explains which Node B types are eligible for the migration from d2U/BBU to
B types 9926 d4U.

If the supported NodeB type is... Then d2U/BBU to d4U migration is

...
Standalone Configuration supported
(124935)
9941 Smart configuration, supported
in a standard 19 rack
9100 MBS Indoor Ev2 (3G) Configuration supported
(MBI3 Ev2 MBI5 Ev2)
9100 MBS Outdoor Ev2 (3G) Configuration supported
(MBO1 Ev2)
PSU (MD4) supported

Continued on next page

4 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

General, Continued

Supported Node
B types
If the supported NodeB type is... Then d2U/BBU to d4U migration is
(continued)
...
9311 Macro Node B (OD1/ID2/OD2) not supported
(118628)
NOTE: There is no initial configuration with
d2U/BBU
PSU (small/Medium) not supported

NOTE: There is no configuration planned

with d4U
9100 MBI/MBO (2G) Configuration not supported
(MBO2 and 9100 MBO2E) MBO/MBI/
NOTE: There is no configuration planned
with d4U

Operational
Impacts

IMPORTANT: The d2U/BBU to 9926 d4U migration procedure is impacting

operations of the Node B and causes service interruption while performed.

Previous Release New creation

Date

Release Notes New creation: Dec 2013 under utilization of existing IM documents from UA08.1.

December 15, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

References

General This section utilizes ALU product documents as well as handbook 521 sections to perform the
d2U/BBU to d4U migration

Documentation Access to applicable documents can be made under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable The sections listed in Table 1 below are required after the replacement of d2U/BBU to d4U.
IEH521 Sections

Table 1: Applicable IEH 521 Sections for WCDMA d2U/BBU to d4U

migration
Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
310 Node B Commissioning Test
399 Node B Commissioning Test Records
401 Node B integration Planning
402 Node B Integration in existing Utran
410 Node B Integration test
499 Node B Integration test record
702 CCM-U board migration procedure
703 CEM-U board migration procedure

Continued on next page

6 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

References, Continued

Applicable The following methods documents are required to perform the d2U/BBU to d4U replacement
Methods
Documents
Table 2: Applicable methods documents

Doc Number Doc Title URL

3MN-01637-0004-DEZZA Alcatel-Lucent 9926 digital http://cic.us.alcatel-
4U NodeB Technical lucent.com/pdfdocs14/pristor
Description e215/529526.pdf

3MN-00476-0001-DEZZA Alcatel-Lucent 9941 Smart http://cic.us.alcatel-

Base Station - Technical lucent.com/pdfdocs14/pristor
Description e215/526916.pdf

3MN-00461-0013-DEZZA Alcatel-Lucent 9100 Multi- http://cic.us.alcatel-

standard Base Station lucent.com/pdfdocs14/pristor
Indoor for WCDMA 2.1 Ghz e215/526862.pdf
-
Technical Description

3MN-00462-0026-DEZZA Alcatel-Lucent 9100 Multi- http://cic.us.alcatel-

standard Base Station lucent.com/pdfdocs14/pristor
Outdoor for WCDMA 2.1 e215/526866.pdf
Ghz - Technical Description

3MN-01637-0004-DEZZA Alcatel-Lucent 9926 BBU in http://cic.us.alcatel-

PSU MD4 Outdoor Cabinet lucent.com/pdfdocs14/pristor
- e215/529526.pdf
Technical Description

3MN-01637-0001-RJZZA Alcatel-Lucent 9926 digital http://cic.us.alcatel-

4U NodeB standalone lucent.com/pdfdocs14/pristor
Site Preparation e215/526688.pdf

CMN/BTS/APP/037054 9926 BBU 4U https://infoproducts.alcatel-

MOPG lucent.com/aces/cgi-
bin/dbaccessfilename.cgi/C
MNBTSAPP037054UA08.1_
V1_

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

References, Continued

Applicable
Methods
Doc Number Doc Title URL
Documents
(continued) 3MN-01637-0002-RJZZA Alcatel-Lucent 9926 LR http://cic.us.alcatel-
Digital Unit 4U Installation lucent.com/pdfdocs14/pristor
Manual in Standalone/Smart e215/541201.pdf
Configuration

3MN-00461-0002-RJZZA Alcatel-Lucent 9100 MBS http://cic.us.alcatel-

MBI Ev2 (3G) Install. Manual lucent.com/pdfdocs15/pristor
Procedure (d2u/d4U + TRDU e214/516144.pdf
(3G))
3MN-00462-0002-RJZZA Alcatel-Lucent 9100 MBS http://cic.us.alcatel-
MBO Ev2 (3G) Install. lucent.com/pdfdocs14/pristor
Manual Procedure (d2u/d4U e215/524344.pdf
+ TRDU (3G))

3MN-01495-0006-RJZZA Alcatel-Lucent 9926 DBS http://cic.us.alcatel-

BBU in PSU Md4 Outdoor lucent.com/pdfdocs15/pristor
Cabinet Installation Manual e214/516034.pdf
WCDMA IM 04-6114 Alcatel-Lucent 9941 Smart http://cic.us.alcatel-
Installation Guide (d4U BBU lucent.com/pdfdocs14/pristor
+ TRDU) e215/531215.pdf
WCDMA IM 04-6115 Alcatel-Lucent 9100 MBS http://cic.us.alcatel-
MBI Ev2 (3G) Indoor lucent.com/pdfdocs14/pristor
Cabinet Evolution Install. e215/531216.pdf
Guide (d4U BBU + TRDU)
WCDMA IM 04-6116 Alcatel-Lucent 9100 MBS http://cic.us.alcatel-
MBO Ev2 (3G) Outdoor lucent.com/pdfdocs14/pristor
Cabinet Evolution Install. e215/531217.pdf
Guide (d4U BBU + TRDU)

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

8 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Tools Requirements

General This table describes the hardware tools required to perform the d2U/BBU to d4U migration.

Hardware Tools The hardware tools listed in the following table are required to perform the d2U/BBU to d4U
migration.

Table 3: Hardware Tools

Hardware Tool Quantity Description

Keys to open the NodeB 1 set If necessary
A0625359 1 Antistatic wrist strap
Set of flat blade 1
screwdrivers
Set of Phillips screwdrivers 1
Set of open-end wrenches 1
Set of Torx screwdrivers 1
Ratchet 1

Sockets 1

5 Stepladder 1

Hacksaw 1

Rag 1

December 15, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Material Requirements

General Prior to the start of migration it has to be ensured that all demanded material is available.

Hardware The following table describes the material requirements to perform the d2U / BBU to d4U
requirements migration.
and order
information
Table 4: Hardware material requirements and order information

Module PEC Quantity

D4U shelf ? How equipped ? 1
xCCM-U with MDA E1/T1 or 3JR20038AA 1
eCCM-U with MDA E1/T1 or 3JR20073AB (maximum) if
xCCM-U with MDA GE or 3JR20038AD single Node B
eCCM-U with MDA GE 3JR20073BB 2
eCCM-U in case
of dual Node B
xCEM-U or 1 to 5
eCEM-U NOTE: quantitiy
depends on
configuration

NOTE: CCM-U and CEM-U boards available from the d2U/BBU before swap may be re-used in
the 9926 d4U shelf. Additionally required CCM-U (in case of dual Node B configuration) and
CEM-U boards have to be made available through the material requirements. For configuration
and ordering details see MOPG d4U- Applicable methods documents

Cable re-usage Available cables can be re-used if not broken or damaged.

NOTE: Additional or different cables may be demanded through further migrations (e.g.
backhaul interface migration on CCM-U). The cable requirements to support further migrations
are documented in the CCM-U board migration procedure and CEM-U board migration
procedure

10 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Record Sheet

Description A number of record sheets are available to support the information collection and
documentation for the d2U/BBU to d4U migration.

Input parameter The following input parameter sheet must be filled by the coordinator and / or commissioner
sheet before the site intervention.

Table 5: Input parameters

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Record Sheet, Continued

Antenna The following antenna position sheet must be filled by the coordinator and / or commissioner
positions sheet before the site intervention.

Table 6: Antennae Positions

Cell 0 1 2 3 4 5 6
Azimuth

Communication The following sheet is available to support the documentation of the communication test
test results results.
sheet Table 7: Communication Test
Cells 0 1 2 3 4 5 6
Frequency A

Frequency B

Frequency C

Status (OK /
NOK)

Continued on next page

12 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Record Sheet, Continued

Self test results The following sheet is available to support the documentation of the self test results.
sheet

Table 8: NodeB Digital Shelf BISTS Results (applicable for all NodeBs)

Modules State Status OK / NOK

xCEM-Uor eCEM-U The lower LED should be
GREEN
xCCM-Uor eCCM-U The lower LED should be
GREEN

At least the one PCM should

be GREEN

The displays state should be

comprise between 1 to 8

The activity LED should be

ON on the active

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Record Sheet, Continued

Sign-off sheet The following sheet is available to support the documentation of the procedure and final sign-
off of results.

Table 9: Sequence of Operations

Step Procedure Condition To Ok Nok
apply

1 d2U/BBU Sanity check

2 Lock Cells and site

3 D2U/BBU Power off

4 D2U/BBU cables disconnection

5 LPPCM module move

6 iEAM module move

7 Removal of d2U/BBU

8 9926 D4U Installation

9 9926 d4U Commissioning

10 9926 d4U Integration

Table 10: Sign Off

Coordinator Commissioner Customer
Representative
Company name

Functions

Name

Signature

Date

Comments

14 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

d2U/BBU to d4U Migration Overview

Description The migration from d2U/BBU to d4U consists of several steps to be executed.
Main elements are:
Planning and checks before migration
Take d2U/BBU out of service
Disconnect and remove d2U/BBU
Install and connect d4U
Commission and Integrate Node B with d4U

D2U/BBU The flow diagram below outline the d2U/BBU to d4U migration
replacement to
d4U flow
diagram Figure 1: d2U / BBU to d4U migration flow chart

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

d2U/BBU to d4U Migration Overview, Continued

D2U/BBU The purpose of this table is to give an overview of the mandatory or optional tasks to perform
replacement to in the migration from d2U/BBU to d4U.
d4U overview

Table 11: d2U/BBU replacement to d4U overview

Operation Optional / Procedures Remarks

Mandatory
Applicable M - Must be check by on
documents and tools site team
are available
Pre requisites and M - Must be check by on
checklist site team
d2U/BBU Sanity M Procedure 1 Must be check by on
check site team
Lock Cells and site M Procedure 2 Must be done by
OMC Operator
D2U/BBU Power off M Procedure 3 Must be done by on
site team
D2U/BBU cables M Procedure 4 Must be done by on
disconnection site team
Removal of LPPCM O Procedure 5 Must be done by on
module site team
Removal of iEAM O Procedure 6 Must be done by on
module site team
Removal of M Procedure 7 Must be done by on
d2U/BBU site team
9926 D4U M Procedure 8 Must be done by on
Installation site team
9926 d4U M Procedure 9 Must be done by on
Commissioning site team
9926 d4U M Procedure 10 Must be done by
Integration OMC Operator

16 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Precautions

Description This chapter describes the precautions to undertake before launching the d2U/BBU
replacement by the d4U in an existing system.

Safety related This document contains safety statements.

information Safety statements are given at points where risks of damage to personnel, equipment, or
operation may exist.
Failure to follow the directions in a safety statement may result in serious consequences.

Equipment
Safety
Requirements

IMPORTANT: Wearing an anti-static bracelet connected to ground via a

protective resistance to avoid damaging circuits when handling printed circuits is
mandatory.

IMPORTANT: In all the following procedures and steps the ESD foam must be
provided and must be used during any operation on board and the bench.

IMPORTANT : EMC sealing joints being fragile, shocks and hand contact
must be avoided.

IMPORTANT : No mechanical parts of the 9926 d4U or CCM-U board must

never be modified on site (holes, etc.).

December 15, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Preparations before d2U / BBU to d4U migration

procedure execution

Description This chapter describes the preparations to be done before launching the migration process.

Power / Energy
requirements

IMPORTANT: Before going on site to perform migration operations, ensure that

customer has provided the additional power supply line for the d4U.

Transport
reconfiguration
requirements
IMPORTANT: Before going on site to perform migration operations, ensure that
transport team is aware of the backhaul modification (if required).

Final Material Before starting removal operation ensure that :

Checks The correct amount of x/eCCM-U modules is available with the correct interface card in card
boxes

NOTE: Include already available x/eCCM-U modules from d2U/BBU into the check. All
boards with alarm status (LEDs in Red status) are not recommended to be used for the
migration.

The packaging is straight up and does not show any visible sign of faulty storing or handling.
Sufficient cables are available for the migration.
All personal and product safety requirements are being met.

Pre-Installation Verify the following items have been received and/or accomplished before proceeding with the
Checklist installation procedure.
The site has been prepared in compliance with Site Preparation and Installation Document
and Alcatel-Lucent 9926 d4U Site Specification.
The 19" standard frame support or user rack is correctly installed, connected and
secured.
The d4U space is available in a 19" standard user rack.

NOTE: It may be necessary to ensure that there is sufficient space available. This may require
the displacement of some optional modules, where present (ie LPPCM, iEAM, ...).

The completed recort sheet which gives all required input data to apply the procedure. All the
applicable documents listed in the Required Documents Table.

Continued on next page

18 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Preparations before d2U / BBU to d4U migration

procedure execution, Continued

Initial Check and Before going on site ensure with OMC operator that the initial configuration is in operational
alarm clearance status without any alarm.

In case of alarm following actions are required:

If faulty ... Then ...

x/eCCM-U board Contact support team for troubleshooting
x/eCEM-U board Provide spare if need
Radio Module Contact support team for troubleshooting

d2U/BBU -
overview
Figure 2: d2U/BBU overview

NOTE: For details of mounted d2U/BBU into the Node B cabinet types, please refer to the
Technical Description document of the cabinet in use.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Preparations before d2U / BBU to d4U migration

procedure execution, Continued

9926 d4U -
overview

Figure 3: 9926 d4U overview

NOTE: For details of mounted d4U into the Node B cabinet types, please refer to the Technical
Description document of the cabinet in use

Continued on next page

20 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Preparations before d2U / BBU to d4U migration

procedure execution, Continued

xCCM-U with
MDA E1/T1
front view Figure 4: xCCM-U with MDA E1/T1

xCCM-U with
MDA GE front
Figure 5: xCCM-U with MDA GE
view

eCCM-U with
MDA GE / eCCM-
U with MDA
Figure 6: eCCM-U with MDA GE or with MDA E1/T1
E1/T1 front
view

December 15, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 1: d2U/BBU Sanity Check

Description This procedure step is available to validate the operational status and health of the d2U/BBU
before removal.

Pre requisites Before starting removal operation ensure that :

The 9926 d4U, required additional boards and cables are delivered in several cardboard
boxes.
The 9926 d4U packaging is straight up and does not show any visible sign of faulty storing or
handling.
The external appearance of the 9926 d4U is OK (No stains, scratches, dents...).
There will be sufficient space available in the cabinet for d4U mounting.

Continued on next page

22 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 1: d2U/BBU Sanity Check, Continued

Visual Check The following procedure describes how to perform the sanity check of the CCM-U / CEM-U
boards before the migration of the d2U / BBU to d4U.

Step Action
1 Check visually each board in preparation:
All LEDs on - must be in Green Status on digital board
No LED on must be in Red Status on digital board

2 Check visually each CCM-U under operation:

All LEDs for connected optical ports must be in Green Status on connected
optical ports

December 15, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 2: Lock Cell(s) & Site

Description The purpose of this procedure is to stop the traffic and radiation of the impacted site

Lock D2U/BBU The following procedure describes how to lock cell(s) and site
Cells & site

NOTE: These actions should be done by OMC Operator

Step Action
1 Launch NSP GUI & Open the WMS Layout
2 Select the NodeB under migration on the layout and click on Equipment
Monitor

Continued on next page

24 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 2: Lock Cell(s) & Site, Continued

Lock D2U/BBU
Cells & site
Step Action
(continued)
3 Select NodeB & all FDDCell(s) on the left window of Equipment Monitor
window and click on configuration then Set Administrative State to open Set
Administration State Action Window

4 Lock all impacted cells and Node B by clicking Lock button.

NOTE: The d2U/BBU under migration is locked now and ready for migration.
The service is interrupted.

December 15, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 3: d2U/BBU Power off

Description The objective of this procedure is to power off the d2U/BBU and the entire Node B.

D2U/BBU Power The following procedure describes how to Power OFF the d2U/BBU.
off

Step Action
1 Check the ON/OFF Power Button on the RUC module - right side of the NodeB
to be in ON state.

2 Switch off Power Button of d2U / BBU on RUC module.

Continued on next page

26 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 3: d2U/BBU Power off, Continued

D2U/BBU Power
off (continued)
Step Action
3 Check that all d2U / BBU LEDs are extinguished.

NOTE: No LED inside the d2U/BBU must display

4 Switch OFF the breaker at the customer power distribution panel which supplies
the d2U/BBU in case of standalone configuration.

For power off of d2U/BBU in other cabinet configurations refer to Installation

Manual

December 15, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 4: d2U/BBU Cables Disconnection

Description The purpose of this procedure is to disconnect all the cables from the d2U/BBU under
migration:
Dallas bus
GPS antenna cable (if applicable)
Backhaul cables (dependent on configuration and interface type)
Radio links (RRH, TRDU)
Alarm cable
Power cable

D2U/ BBU The following procedure explains how to disconnect the Dallas bus from the d2U/BBU.
Dallas bus
disconnection
procedure Step Action
1 Disconnect the Dallas 1W cables as per configuration under migration

d2U/BBU + alarm module.

d2U/BBU + LPPCM configuration,
d2U/BBU + alarm module + LPPCM

NOTE: It is configuration dependent which cables are present and which

cables are to be disconnected.

2 Check Dallas 1W cables for good enough condition for re-use and store away
for later re-use

Continued on next page

28 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 4: d2U/BBU Cables Disconnection, Continued

GPS module link The following procedure explains how to disconnect the GPS Module from the CCM-U Module
disconnection in the d2U/BBU
procedure

Step Action
1 Disconnect GPS cable from CCM (RJ45)

NOTE: The GPS Synchro connector of the CCM-U is a shielded RJ45 female
receptacle with 10 pins.

2 Check GPS cable to be in good enough condition for re-use and store away for
later re-use

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 4: d2U/BBU Cables Disconnection, Continued

D2U/BBU The backhaul cables of the d2U/BBU under migration are dependent on CCM-U configuration,
backhaul cables backhaul interface type and option.
options Table 12: CCM-U board backhaul configurations

CCM-U configuration Backhaul interface Option

type
xCCM-U + MDA E1/T1 E1/T1 w/ LPPCM
wo/ LPPCM
xCCM-U + MDA GE E1/T1 w/ LPPCM
wo/ LPPCM
xCCM-U + MDA GE IP electrical
optical
eCCM-U + MDA GE E1/T1 w/ LPPCM
wo/ LPPCM
eCCM-U + MDA GE IP electrical
optical

E1/T1 The following procedure describes how to disconnect the E1/T1 PMC to the xCCM-U + MDA
disconnection E1/T1
procedure
xCCM-U + MDA
E1/T1 w/ Step Action
LPPCM
1 Disconnect cables on xCCM-U side and LPPCM side as per following figure

2 Check cables to be in good enough condition for re-use and store away for
later re-use (if required)

Continued on next page

30 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 4: d2U/BBU Cables Disconnection, Continued

E1/T1 The following procedure describes how to disconnect the E1/T1 PMC to the xCCM-U + MDA
disconnection E1/T1 wo/ Lightning Protection PCM unit.
procedure
xCCM-U + MDA
E1/T1 wo/ Step Action
LPPCM
1 Disconnect cable on xCCM-U side and up to the PCM cable and to the
terminator block side as per following figure

2 Check cables to be in good enough condition for re-use and store away for
later re-use (if required)

E1/T1 The following procedure describes how to disconnect the E1/T1 PMC to the xCCM-U + MDA
disconnection GE w/ Lightning Protection PCM unit.
procedure
xCCM-U + MDA
GE w/ LPPCM Step Action
1 Disconnect cable on xCCM-U side and up to the LPPCM as per following figure

2 Check cables to be in good enough condition for re-use and store away for
later re-use (if required)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 4: d2U/BBU Cables Disconnection, Continued

E1/T1 The following procedure describes how to disconnect the E1/T1 PMC to the xCCM-U + MDA
disconnection GE wo/ Lightning Protection PCM unit.
procedure
xCCM-U + MDA
GE wo/ LPPCM Step Action
2 Disconnect cable on xCCM-U side and up to the PCM cable and to the
terminator block side as per following figure

Check cables to be in good enough condition for re-use and store away for
later re-use (if required)

E1/T1 The following procedure describes how to disconnect the E1/T1 PMC to the eCCM-U + MDA
disconnection GE w/ Lightning Protection PCM unit.
procedure
eCCM-U + MDA Step Action
GE w/ LPPCM 1 Disconnect cable on eCCM-U side and up to the LPPCM as per following figure

2 Check cables to be in good enough condition for re-use and store away for
later re-use (if required)

Continued on next page

32 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 4: d2U/BBU Cables Disconnection, Continued

E1/T1 The following procedure describes how to disconnect the E1/T1 PMC to the eCCM-U + MDA
disconnection GE wo/ Lightning Protection PCM unit.
procedure
eCCM-U + MDA
GE wo/ LPPCM Step Action
1 Disconnect cable on xCCM-U side and up to the PCM cable and to the
terminator block side as per following figure

2 Check cables to be in good enough condition for re-use and store away for
later re-use (if required)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 4: d2U/BBU Cables Disconnection, Continued

IP disconnection The following procedure describes how to disconnect the IP interface, electrical to the eCCM-U
procedure + MDA GE
xCCM-U + MDA
GE / eCCM-U +
MDA GE Step Action
electrical
1 Disconnect the RJ45 CAT5 Backhaul Cable to the MDA module

Continued on next page

34 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 4: d2U/BBU Cables Disconnection, Continued

IP disconnection
procedure
Step Action
xCCM-U + MDA
GE / eCCM-U + 2 OPTION: In some cases Port 2 of xCCM-U or eCCM-U is used for backhaul
MDA GE connection.
electrical
(continued) Disconnect RJ45 from xCCM-U or eCCM-U board on port 2 (Mother board)

xCCM-U

NOTE: The isolator component (1AB243270001) and the RJ45 adaptator

(3JR22088AAAA) figure is only to be used in configuration with xCCM-U

eCCM-U:

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 4: d2U/BBU Cables Disconnection, Continued

IP disconnection
procedure
Step Action
xCCM-U + MDA
GE / eCCM-U + 3 Check cables to be in good enough condition for re-use and store away for
MDA GE later re-use (if required)
electrical
(continued)

IP disconnection The following procedure describes how to disconnect the IP interface, optical to the eCCM-U +
procedure MDA GE
xCCM-U + MDA
GE / eCCM-U +
MDA GE optical Step Action
1 Remove the Optical Transceiver SFP from the SFP cage on the MDA (Only one
SPF1 connection is used today)

2 Disconnect the Backhaul LC optical fiber from the optical transceiver SFP port.
3 Check cables and SFPs to be in good enough condition for re-use and store
away for later re-use (if required)

Continued on next page

36 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 4: d2U/BBU Cables Disconnection, Continued

Radio Unit - This procedure explains how to disconnect the optical link from the CPRI ports (1 to 6)
optical link
disconnection
procedure Step Action
1 Disconnect Radio module link from CCM board

If Radio Module is... Then ...

RRH /MC-RRH Unplug LC optical Fiber
remove Optical Transceiver from CPRI 1 to 6
TRDU / MC-TRDU Unplug electrical transceiver from CPRI 1 to 6
MC-TRX Unplug electrical transceiver from CPRI 1 to 6
2 Check cables and SFPs to be in good enough condition for re-use and store
away for later re-use (if required)

Alarm cable The following procedure describes how to disconnect the alarm cable
disconnection
procedure
Step Action
1 Locate the cable between RUC Module and CCM-U as shown

2 Disconnect the Alarm cable both sides

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 4: d2U/BBU Cables Disconnection, Continued

Power cable The following procedure describes how to disconnect the power cable from the d2U/BBU
disconnection
procedure

DANGER: Customer breaker must be in position "0" (OFF). Measurement of the

mains power is recommended to test that no active power is connected at the d2U/BBU.

Step Action
1 Check d2U/BBU Switch is in position "0" (OFF)

3 Disconnect the 3 lugs of the Power Cable from the d2U/BBU terminal lugs

NOTE: IN CASE of RUC/FAN Rack - 48Vdc:

Blue wire from the -48V (or" -" on the 9926 BBU terminal lug)
Black wire from the 0V (or" +" on the 9926 BBU terminal lug)
Yellow/Green wire from the GND point
4 Disconnect the cable of the client power plant.
NOTE: This cable cannot be re-used with the 9926 d4U.

Continued on next page

38 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 4: d2U/BBU Cables Disconnection, Continued

GND The following procedure explains how to disconnect the GND Cable in a 19" standard frame.
Disconnection

Step Action
1 Disconnect the Ground Cable (Green/Yellow) from the d2U/BBU

2 Disconnect the Ground Cable (Green/Yellow) from the GND Plate of the
19" Standard Frame.

IMPORTANT: Do not remove the GND Cables from the

support cabinet side. I dont understand the meaning of this sentence.
Please clarify !

NOTE: The DC return conductors shall be bonded to the frame ground system at the output of
the DC power system. For proper site grounding of the equipment, refer to Grounding and
Lightning Protection Guidelines for Alcatel-Lucent Network Wireless System Cell Sites,401-200-
115.

December 15, 2013 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 5: LPPCM module move

Description LPPCM is an optional module.

The LPPCM module may need to be moved to a different location inside the cabinet to free up
sufficient space for the d4U.

LPPCM Module Remove LPPCM module (if necessary) to free up space for the d4U shelf.
removal

Step Action
1 Disconnect PCM cables (incoming & outgoing) form LPPCM

NOTE: All cables should have been already removed from the d2U/BBU
disconnection procedures

2 Remove LPPCM module from 19" Standard Frame by loosening the screws.
3 Mount LPPCM in new rack position to allow fit of the d4U.

NOTE: Refer to Technical Description of the Node B configurations in support

of d4U.

40 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 6: iEAM module move

Description iEAM is an optional module.

The iEAM module may need to be moved to a different location inside the cabinet to free up
sufficient space for the d4U.

iEAM Module The objective of this procedure is to show how to remove the iEAM module to free up space
removal for final d4U configuration.

Step Action
1 Disconnect alarms cable from iEAM module

2 Remove iEAM module from 19" Standard Frame by loosening the screws
3 Mount iEAM in new rack position to allow fit of the d4U.

NOTE: Refer to Technical Description of the Node B configurations in support

of d4U.

December 15, 2013 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 7: Removal of d2U/BBU

Description After complete disconnection of all cables from d2U/BBU the d2U/BBU shelf must be removed
from the cabinet

Removal The following procedure describes how to remove the d2U/BBU from the cabinet
procedure

Step Action
1 Take it out CCM-U and CEM-U boards
2 Take out RUC module
3 Store removed boards / modules for potential re-use with d4U
4 Unscrew the 4 screws as shown with maintaining the d2U/BBU.

5 Remove the d2U/BBU from the cabinet

42 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 8: 9926 d4U Installation

Description Physical mounting, installation and (re-)connection of all cables to the d4U is covered by the
installation procedures.
The installation procedure varies dependent on the configuration of the d4U and the type of
hosting rack.

D4U Installation The installation of d4U as stand alone or into an existing cabinet is covered by the following
procedure installation documentation

Table 13: Installation procedures

Node B configuration Installation procedure

Standalone Configuration Alcatel-Lucent 9926 LR Digital Unit 4U
(124935) Installation Manual in Standalone/Smart
Configuration

9941 Smart configuration, Alcatel-Lucent 9941 Smart Installation Guide

in a standard 19 rack (d4U BBU + TRDU)

9100 MBS Indoor Ev2 (3G) Configuration Alcatel-Lucent 9100 MBS MBI Ev2 (3G)
(MBI3 Ev2 MBI5 Ev2) Indoor Cabinet Evolution Install. Guide (d4U
BBU + TRDU)
9100 MBS Outdoor Ev2 (3G) Configuration Alcatel-Lucent 9100 MBS MBO Ev2 (3G)
(MBO1 Ev2) Outdoor Cabinet Evolution Install. Guide
(d4U BBU + TRDU)
PSU (MD4) Alcatel-Lucent 9926 DBS BBU in PSU Md4
Outdoor Cabinet Installation Manual

December 15, 2013 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc.9: 9926 d4U Commissioning

Description After installation of the d4U the full commissioning of the Node B must take place as described
in the commissioning sections of this IEH521.

D4U The commissioning of the newly installed d4U is described in the IEH521 sections as per table
Commissioning below.
procedure Table 14: Commissioning procedures

Section Procedures
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
310 Node B Commissioning Test
399 Node B Commissioning Test Records

44 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
d2U/BBU to d4U Migration Procedure IEH 521, Section 701

Proc. 10: 9926 d4U Integration

Description After commissioning of the d4U the full integration of the Node B must take place as describe in
the integration sections of this IEH521.

D4U Integration The integration of the newly installed and commissioned d4U is described in the IEH521
sections as per table below.

Table 15: Integration procedures

Step Action
401 Node B integration Planning
402 Node B Integration in existing Utran
410 Node B Integration test
499 Node B Integration test record

December 15, 2013 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 701 d2U/BBU to d4U Migration Procedure

Proc. 11: Final Checks and Clean-up

Description Final actions at site are required to complete the d2U/BBUmigration work before leaving the
site

Final checks and The following procedure describes the final steps of action before leaving the site
clean-up
procedure
Step Action
1 Verify that all cables are correctly marked and secured with tie-wraps in case of
radio reconfiguration
2 Complete the report sheet.

NOTE: All cases of non-compliances identified during the migration must be

described.
3 Send report sheet to coordinator.

NOTE: Corrective actions to be synchronized with the coordinator.

4 Send the cardboard packing box with the old d2U/BBU module back to Alcatel-
Lucent

NOTE: Address is coordinator or supervisor of these retrofits

5 Close and lock the NodeB's doors and clean the site.

46 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 702

December 15, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

CCM-U Board Migration Procedure

Table of Contents

General ............................................................................................................ 5
Scope of migration ........................................................................................... 5
Migration paths ............................................................................................... 5
Operational Impacts ......................................................................................... 5
Restrictions.................................................................................................... 5
Previous Release Date ....................................................................................... 5
Release Notes ................................................................................................. 5
References ........................................................................................................ 6
General ........................................................................................................ 6
Documentation Access ...................................................................................... 6
Applicable IEH521 Sections ................................................................................. 6
Applicable Methods Documents............................................................................ 7
Location of supporting documents ........................................................................ 8
CCM-U Board Migration Process Interface Type Migration.............................................. 9
Description .................................................................................................... 9
CCM-U interface type migration process ............................................................... 9
OMC operator interaction .................................................................................. 9
Tools Requirements ........................................................................................... 10
General ...................................................................................................... 10
Hardware Tools ............................................................................................. 10
Material Requirements ....................................................................................... 11
General ...................................................................................................... 11
Board requirements ........................................................................................ 11
Board requirements order information ............................................................... 11
Ethernet cabling requirement ........................................................................... 12
Fiber cabling requirement ................................................................................ 12
Upgrade kits requirements ............................................................................... 12
Record Sheet ................................................................................................... 13
Description .................................................................................................. 13
Input parameter sheet .................................................................................... 13
Antenna positions sheet .................................................................................. 14
Communication test results sheet ...................................................................... 14

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Self test results sheet ..................................................................................... 15

Sign-off sheet ............................................................................................... 15
CCM-U Board Migration Procedure Overview ............................................................. 17
Description .................................................................................................. 17
CCM-U Migration flow diagram........................................................................... 17
CCM-U board migration procedure Overview table ................................................ 18
Precautions ..................................................................................................... 19
Description .................................................................................................. 19
Safety related information ............................................................................... 19
Equipment Safety Requirements ........................................................................ 19
Preparations before CCM-U migration procedure execution........................................... 20
Description .................................................................................................. 20
Transport .................................................................................................... 20
Initial Check ................................................................................................. 20
Final Material Checks ...................................................................................... 20
x/eCCM-U position within digital shelf d4U ........................................................... 21
x/eCCM-U position within digital shelf d2U ........................................................... 21
xCCM-U with MDA E1/T1 front view .................................................................. 22
xCCM-U with MDA GE front view....................................................................... 22
eCCM-U with MDA GE / eCCM-U with MDA E1/T1 front view ..................................... 22
Proc.1: xCCM-U / eCCM-U Sanity Check ................................................................... 23
Description .................................................................................................. 23
Visual check procedure ................................................................................... 23
Proc.2: Initial communication Test ........................................................................ 24
Description .................................................................................................. 24
Initial communication test procedure .................................................................. 24
Proc.3: Save I&C Parameters ................................................................................ 25
Description .................................................................................................. 25
Save I&C parameters procedure ......................................................................... 25
I&C parameters use for backup ........................................................................ 25
Proc.4: NodeB online check ................................................................................. 26
Description .................................................................................................. 26
NodeB online check procedure .......................................................................... 26
Proc. 5: CCM-U Migration .................................................................................... 28
Description .................................................................................................. 28
Operational Impacts ....................................................................................... 28
Hardware checks & pre migration tests procedure .................................................. 28
CCM-U physical migration procedure ................................................................... 29
Proc. 6: New CCM-U Backhaul Connection ................................................................ 32
Description .................................................................................................. 32
E1/T1 connection procedure xCCM-U + MDA E1/T1 w/ LPPCM................................. 33
E1/T1 connection procedure xCCM-U + MDA E1/T1 wo/ LPPCM ............................... 33
E1/T1 connection procedure xCCM-U + MDA GE w/ LPPCM ..................................... 34
E1/T1 connection procedure xCCM-U + MDA GE wo/ LPPCM ................................... 34
E1/T1 connection procedure eCCM-U + MDA GE w/ LPPCM..................................... 35
E1/T1 connection procedure eCCM-U + MDA GE wo/ LPPCM ................................... 35
IP connection procedure xCCM-U + MDA GE / eCCM-U + MDA GE electrical ................. 36
IP connection procedure xCCM-U + MDA GE / eCCM-U + MDA GE optical .................... 37
Proc. 7: Protection cover Installation ..................................................................... 38
Description .................................................................................................. 38
D-Sub Cover installation procedure ..................................................................... 38

2 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

SFP Cover installation procedure........................................................................ 39

Proc.8: CCM-U unchanged cables installation .......................................................... 40
Description .................................................................................................. 40
Proc. 9: Radio modules connection ........................................................................ 41
Description .................................................................................................. 41
Optical RRH interface SFP .............................................................................. 41
Radio module connection procedure optical ........................................................ 42
Radio module connection procedure electrical ..................................................... 43
Proc. 10: CCM-U Start-up and Visual Checks ........................................................... 44
Description .................................................................................................. 44
Automatic software download function ................................................................ 44
Automatic Software Downloading from OMC .......................................................... 44
Automatic software download monitoring procedure ............................................... 44
BTS automatic build function ............................................................................ 45
BTS automatic build from OMC .......................................................................... 45
Automatic BTS build function monitoring procedure ................................................ 45
xCCM-U migration start-up and final check procedure ............................................ 46
eCCM-U migration start-up and final check procedure ............................................ 47
Proc. 11: Final Checks and Clean-up ....................................................................... 49
Description .................................................................................................. 49
Final checks and clean-up procedure................................................................... 49
Fall-back to initial CCM-U configuration ............................................................... 49

List of Figures

Figure 1: CCM-U with MDA E1/T1 to CCM-U with MDA GE Migration Process ................................... 9
Figure 2: CCM-U Migration in d4U flow chart ....................................................................... 17
Figure 3: x/eCCM-U location within the 9926 d4U ................................................................ 21
Figure 4: x/eCCM-U location within the 9926 d2U ................................................................ 21
Figure 5: xCCM-U with MDA E1/T1 ................................................................................... 22
Figure 6: xCCM-U with MDA GE ....................................................................................... 22
Figure 7: eCCM-U with MDA GE or with MDA E1/T1 ............................................................... 22

List of Tables

Table 1: CCM-U Migration paths ........................................................................................ 5

Table 2: Applicable IEH 521 Sections for CCM-U Migration ........................................................ 6
Table 3: Applicable Methods documents .............................................................................. 7
Table 4: Hardware Tools ............................................................................................... 10
Table 5: CCM-U Migration with or without LPPCM ................................................................. 11
Table 6: CCM-U boards order information .......................................................................... 11
Table 7: Input parameters ............................................................................................. 13
Table 8: Antennae Positions ........................................................................................... 14
Table 9: Communication Test ......................................................................................... 14
Table 10: NodeB Digital Shelf BISTS Results (applicable for all NodeBs) ...................................... 15
Table 11: Sequence of Operations ................................................................................... 15
Table 12: Sign Off ....................................................................................................... 16
Table 13: CCM-U board migration .................................................................................... 18

December 15, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Table 14: CCM-U board backhaul configurations .................................................................. 32

4 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

General

Scope of This section provides detailed information to perform the migration of CCM-U board in 9926 d4U or
migration 9926 d2U.

Migration paths The following table describes the migration paths supported by the procedure

Table 1: CCM-U Migration paths

Module for migration xCCM-U module - eCCM-U module -
target target
xCCM-U + MDA E1/T1 xCCM-U + MDA GE eCCM-U + MDA E1/T1
eCCM-U + MDA GE
xCCM-U + MDA GE - eCCM-U + MDA E1/T1
eCCM-U + MDA GE
eCCM-U + MDA E1/T1 - eCCM-U + MDA GE
eCCM-U + MDA GE - -

Operational
Impacts

IMPORTANT: The CCM-U migration procedure is impacting operations of the

Node B and causes service interruption while performed.

Restrictions The Dual NodeB configuration with 9926 d4U must contain only eCCM-U and eCEM-U or
xCEM-U modules.

Previous Release New creation

Date

Release Notes New creation November 2013 under utilization of existing IM documents from UA08.1.

December 15, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

References

General This section lists Alcatel-Lucent product documents as well as handbook 521 sections to
perform the CCM migration.

Documentation Access to applicable documents can be made under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable The IEH521 sections, listed in table below are required for CCM-U migration procedure in d4U
IEH521 Sections or d2U NodeB.

Table 2: Applicable IEH 521 Sections for CCM-U Migration

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
310 Node B Commissioning Test
399 Node B Commissioning Test Records

Continued on next page

6 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

References, Continued
Applicable The following methods documents are available to support the CCM-U migration procedure
Methods with more details if required
Documents Table 3: Applicable Methods documents

Doc Number Doc Title URL

CMN/BTS/APP/037054 9326 D2U https://infoproducts.alcatel-
9926 BBU lucent.com/aces/cgi-
bin/dbaccessfilename.cgi/C
9926 BBU 4U MNBTSAPP037054UA08.1_
PSU (Md4/Md6) V1_
UMT/PFO/APP/025877 9941 Smart https://infoproducts.alcatel-
lucent.com/aces/cgi-
bin/dbaccessfilename.cgi/U
MTPFOAPP025877UA08.1_
V1_
UMT/PFO/APP/005833 9311 Macro ID2 https://infoproducts.alcatel-
lucent.com/aces/cgi-
bin/dbaccessfilename.cgi/U
MTPFOAPP005833UA08.1_
V1_
UMT/PFO/APP/012990 9311 Macro OD2 https://infoproducts.alcatel-
lucent.com/aces/cgi-
bin/dbaccessfilename.cgi/U
MTPFOAPP012990UA08.1_
V1_
UMT/PFO/APP/000005 9311 Macro OD1 http://cic.us.alcatel-
lucent.com/pdfdocs/pristore2
04/432832.pdf
UMT/PFO/APP/026813 9100 MBS MBI https://infoproducts.alcatel-
lucent.com/aces/cgi-
bin/dbaccessfilename.cgi/U
MTPFOAPP026813UA08.1_
V1_
UMT/PFO/APP/029480 9100 MBS MBO https://infoproducts.alcatel-
lucent.com/aces/cgi-
bin/dbaccessfilename.cgi/U
MTPFOAPP029480UA08.1_
V1_
CMN_BTS_APP_037185_L 9711 LR ID Cabinet http://cic.us.alcatel-
R13W lucent.com/pdfdocs14/pristor
e215/539573.pdf
CMN_BTS_APP_037184_L 9712 LR OD Cabinet http://cic.us.alcatel-
R13W lucent.com/pdfdocs14/pristor
e215/539572.pdf

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

References, Continued

Location of NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
supporting lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
documents ents/index.html

8 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

CCM-U Board Migration Process Interface Type

Migration

Description This chapter provides an overview about the CCM-U Board Migration Process in case it
demands the change of the interface type from MDA E1/T1 to MDA GE.
The migration procedure as described in IEh521-702 describes the actions to be performed on
site.
All non-on site actions are not subject of this procedure description.

CCM-U In case of MDA E1/T1 migration to MDA GE the following process must be applied because
interface type modification of the CCM-U module on-site is not possible.
migration
process
Figure 1: CCM-U with MDA E1/T1 to CCM-U with MDA GE Migration
Process

OMC operator Several interactions with the OMC operator are required as part of the migration procedures.
interaction The OMC operator must have the following information:
NodeB ID

December 15, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Tools Requirements

General The CCM-U migration demands the use of several tools.

Hardware Tools The hardware tools, listed in the following table are required to perform the CCM-U migration.

Table 4: Hardware Tools

Hardware Tool Quantity Description

Key 1 set Keys to open the cabinet doors (+ customer
site)
Antistatic wrist strap 1
Set of screwdriver 1 Flat and Philips screwdrivers for digital
modules
Clamp pliers 1 For cable tie
Module extractor 1 To remove the module (if not present in the
cabinet doors)
Lamp 1 Depending on time of intervention
Tent 1 if necessary (only for Outdoor)
UMTS mobile 1 Only for CS call (with trace capability)
Laptop PC 1 Needed for CCM-U upgrade with the TIL
RJ45 crossed cable 1 Needed for CCM-U upgrade with the TIL
Keys 1 To open the cabinet doors (+ customer site)

10 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Material Requirements

General Prior to the start of migration it has to be ensured that all demanded material is available.

Board The following table describes the board material requirements to perform the CCM-U migration.
requirements

Table 5: CCM-U Migration with or without LPPCM

Initial Final Board

configuration configuration requirement
xCCM-U xCCM-U xCCM-U + GE MDA
+ E1/T1 MDA + GE MDA
xCCM-U eCCM-U eCCM-U + E1/T1
+ E1/T1 MDA + E1/T1 MDA MDA

xCCM-U eCCM-U eCCM-U + GE MDA

+ E1/T1 MDA + GE MDA
eCCM-U eCCM-U eCCM-U + GE MDA
+ E1/T1 MDA + GE MDA

Board The following table provides information on the CCM-U boards ordering codes.
requirements
order
information Table 6: CCM-U boards order information

PEC Module
3JR20038AA xCCM-U with MDA E1/T1
3JR20073AB eCCM-U with MDA E1/T1
3JR20038AD xCCM-U with MDA GE
3JR20073BB eCCM-U with MDA GE

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Material Requirements, Continued

Ethernet cabling General cable requirements

requirement Category 6 Ethernet cable. CAT6
RJ45 cabling shall comply with IEC11801 & TIA/EIA-568 standards.
The physical length of the channel (fixed horizontal cable & patch cords / cross-connect
jumpers) shall not exceed 100 m.

Patch cords / cross-connect jumpers:

Length of patch cords/jumper cables must not exceed 10 m in total.
In case longer connection is required, the installation should be made of a horizontal cable
plus the required patch cords/jumper cables.
F/FTP and S/FTP minimum constructed cable, using 26 AWG minimum conductors.
Male-Male shielded connectorized cable.

Horizontal Cable:
Cable length shall not exceed 90 m.
STP or FTP cable construction, using 24 AWG minimum insulated solid conductors.
Female-Female connectorized cable.
Foil screens should be connected to ground for each cable of the Ethernet channel.

Fiber cabling Fiber cable as per requirement below :

requirement
Single Mode: fiber length from 500 m to 10 km
Multi Mode: fiber length from 0 m to 500 m

Upgrade kits Several upgrade kits are defined to support the migration of CCM-U.
requirements For upgrade kits refer to the MOPG documents of the dedicated NodeB under migration:
Applicable methods documents.

12 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Record Sheet

Description A number of record sheets are available to support the information collection and
documentation for the CCM-U migration.

Input parameter The following input parameter sheet must be filled by the coordinator and / or commissioner
sheet before the site intervention.

Table 7: Input parameters

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Record Sheet, Continued

Antenna The following antenna position sheet must be filled by the coordinator and / or commissioner
positions sheet before the site intervention.

Table 8: Antennae Positions

Cell 0 1 2 3 4 5 6
Azimuth

Communication The following sheet is available to support the documentation of the communication test
test results results.
sheet Table 9: Communication Test
Cells 0 1 2 3 4 5 6
Frequency A

Frequency B

Frequency C

Status (OK /
NOK)

Continued on next page

14 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Record Sheet, Continued

Self test results The following sheet is available to support the documentation of the self test results.
sheet

Table 10: NodeB Digital Shelf BISTS Results (applicable for all NodeBs)
Modules State Status OK
/ NOK

xCEM-Uor eCEM-U The lower LED should be GREEN

xCCM-Uor eCCM-U The lower LED should be GREEN

At least the one PCM should be GREEN

The displays state should be comprise between 1 to 8

The activity LED should be ON on the active

Sign-off sheet The following sheet is available to support the documentation of the procedure and final sign-
off of results.

Table 11: Sequence of Operations

Step Procedure Condition To Ok Nok
ap-
ply
1 Initial NodeB checks

2 Initial Communication Test

3 Save I&C Parameter

4 NodeB On Line Check

5 Hardware Checks

6 CCM-U hardware migration

procedure

7 New CCM-U connection

8 9326 d2U / 9926 d2U & 9926 d4U

visual check

9 Final Checks

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Record Sheet, Continued

Sign-off sheet
(continued)
Table 12: Sign Off
Coordinator Commissioner Customer
Representative
Company name

Functions

Name

Signature

Date

Comments

16 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

CCM-U Board Migration Procedure Overview

Description The CCM-U migration procedure consists of a sequence of steps. The sequence of the steps
and the procedure names are described in this chapter to provide the necessary overview.

CCM-U The flow diagram below outlines all the steps and the order to occur for CCM-U migration
Migration flow
diagram
Figure 2: CCM-U Migration in d4U flow chart

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

CCM-U Board Migration Procedure Overview, Continued

CCM-U board The purpose of the table below is to give an overview of the mandatory or optional tasks to
migration perform for CCM-U migration.
procedure
Overview table
Table 13: CCM-U board migration
Operation Optional / Procedures Remarks
Mandatory
Check documents M - Must be check by on
and hardware tools site team
are present
Pre requisites and M - Must be check by on
checklist site team
CCM-U Sanity check M Procedure 1 Must be check by on
site team
Initial M Procedure 2 Must be done by on
communication Test site team r
Save I&C M Procedure 3 Must be done by on
parameters site team
NodeB online Check M Procedure 4 Must be done by on
site team
CCM-U Migration M Procedure 5 Must be done by on
site team
Backhaul M Procedure 6 Must be done by on
Connection site team
Protection cover O Procedure 7 Must be done by on
Installation site team
Radio Modules M Procedure 9 Must be done by on
Connection site team
Start-up & Visual M Procedure 10 Must be done by on
Check site team
Final checks & M Procedure 11 Must be done by on
clean- up site team

18 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Precautions

Description This chapter describes the precautions to undertake before launching the migration procedure.

Safety related This document contains safety statements.

information Safety statements are given at points where risks of damage to personnel, equipment, or
operation may exist.
Failure to follow the directions in a safety statement may result in serious consequences.

Equipment
Safety
Requirements

IMPORTANT: Wearing an anti-static bracelet connected to ground via a protective

resistance to avoid damaging circuits when handling printed circuits is mandatory.

IMPORTANT: In all the following procedures and steps the ESD foam must be
provided and must be used during any operation on board and the bench.

IMPORTANT: EMC sealing joints being fragile, shocks and hand contact must be
avoided.

IMPORTANT: No mechanical parts of the 9926 d4U or CCM-U board must never
be modified on site (holes, etc.).

December 15, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Preparations before CCM-U migration procedure

execution

Description This chapter describes the preparations to be done before launching the migration process.

Transport

IMPORTANT: Before going on site to perform migration operations, ensure that

transport team is aware of the backhaul modification.

Initial Check Before going on site ensure with OMC operator that the initial configuration is in operational
status without any alarm.

Final Material Before starting removal operation ensure that

Checks
The correct amount of x/eCCM-U modules with the correct interface card is delivered in card
boxes.
The packaging is straight up and does not show any visible sign of faulty storing or handling.
Sufficient cables are available for the migration.
All personal and product safety requirements are being met.

Continued on next page

20 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Preparations before CCM-U migration procedure

execution, Continued

x/eCCM-U The following figure outlines the position of the CCM-U modules within the digital unit (d4U).
position within
digital shelf d4U
Figure 3: x/eCCM-U location within the 9926 d4U

x/eCCM-U The following figure outlines the position of the CCM-U modules within the digital unit (d2U).
position within
digital shelf d2U
Figure 4: x/eCCM-U location within the 9926 d2U

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Preparations before CCM-U migration procedure

execution, Continued

xCCM-U with
MDA E1/T1
front view Figure 5: xCCM-U with MDA E1/T1

xCCM-U with
MDA GE front
Figure 6: xCCM-U with MDA GE
view

eCCM-U with
MDA GE / eCCM-
Figure 7: eCCM-U with MDA GE or with MDA E1/T1
U with MDA
E1/T1 front
view

22 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc.1: xCCM-U / eCCM-U Sanity Check

Description This procedure step is available to validate the operational status and health of the CCM-U
board before removal from the digital shelf.

Visual check The following procedure describes how to perform the sanity check before removal of the
procedure CCM-U card from the digital shelf.

Step Action
1 Check visually each CCM-U under operation:
All LEDs on - must be in Green Status on digital board
No LED on must be in Red Status on digital board

2 Check visually each CCM-U under operation:

All LEDs for connected optical ports must be in Green Status on connected
optical ports

December 15, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc.2: Initial communication Test

Description The internal communication test is available to proof full operational status of the digital shelf
and the CCM-U prior to the CCM-U migration. The test is performed to have a baseline before
the operation starts.

Initial The following table describes how to perform the initial communication test
communication
test procedure
Step Action
1 Position the UMTS Mobile in the area covered by the NodeB.
2 Check the Primary Scrambling Code at the OMC.

NOTE: The Primary Scrambling Code must be the same in OMC view and
UMTS Mobile to make sure that the tests are performed for the correct Node B
entity.
3 Activate the trace of the UMTS Mobile
4 Perform CS call to the OMC via the PSTN using the UMTS mobile.
Verify Primary Scrambling Code is the same at OMC and UMTS mobile
5 Record the result of the test (Success / No Success)
6 Perform PS call to validated successful PS communication

NOTE: Web browsing recommended

7 Record the result of the test (Success / No Success / web address)
8 Check on site that no unexpected alarm appear through local LED check

24 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc.3: Save I&C Parameters

Description The objective of this procedure is to save I&C Parameters to keep the initial configuration
available in case of fall-back is required.

Save I&C The following procedure explains how to retrieve and save I&C parameters before service
parameters interrupting work starts
procedure

Step Action
1 Connect the RJ45 to : Port 1 if xCCM-U (or eCCM-U) used
2 Launch the TIL in local mode
3 Select from menu: I&C | Save I&C parameters

4 Click SAVE

NOTE: The file will be saved in <Default path>[email protected]>

folder. The <Default path> is the path defined when TIL is launched.

I&C parameters In case of a problem during the CCM-U migration which requires fall-back to the origin state go
use for backup back to the saved I&C parameters file in order to restore the default I&C parameters.

December 15, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc.4: NodeB online check

Description The objective of this procedure is to check final Node B alarm status and retrieve the software
version of the CCM-U before removal.
The SW version is required for the return sheet of the CCM-U board when sending it in for re-
work according the CCM-U migration process.

NodeB online The following procedure explains how to check Node B alarms with the TIL and retrieve
check procedure software version

Step Action
1 Launch the TIL in local mode to check the software load displayed at the bottom
of the TIL board screen.
2 Retrieve software load information as displayed at the bottom of the TIL board
screen.

3 Verify SW load information with OMC technician for correctness

4 Record the software load version in return sheet

Continued on next page

26 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc.4: NodeB online check, Continued

NodeB online
check procedure
Step Action
(continued)
5 Select from TIL menu Alarms | Display current alarms to retrieve alarm
status display

6 Check in TIL alarm manager window that there are no alarms on the CCM-U
7 Check in TIL manager window that there are no Node B alarms displayed.
8 Verify with OMC-B technician the correctness of local alarm check with TIL and
that there are no CCM-U alarms displayed at the OMC

NOTE: The OMC technician should perform the operation Show NEs Alarms
9 Check that there are no alarms on any of the cards. All the LEDs on each
module (except some PCM LEDs) should be green.

NOTE: If the Node B is not error free then refer to the technical support or the coordinator for
trouble shooting prior to start of migration.

December 15, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 5: CCM-U Migration

Description CCM-U migration procedure is describing how to

Remove existing CCM-U from the digital module
Replace with new CCM-U with target interface

Operational
Impacts

IMPORTANT: This procedure will provoke service until the digital unit is brought
back to service again. Approximate service interruption is 30 mins

IMPORTANT: If the 9926 d4U is in a BTS daisy-chain, then any Node B

downstream of the CCM-U under work will also suffer the same outage.

Hardware The following procedure describes how to perform final hardware checks and pre-migration
checks & pre tests before removal of the CCM-U from the digital unit.
migration tests
procedure
Step Action
1 Put on the antistatic wrist strap and test it.
2 Check the initial NodeB configuration for number of CCM-U modules.
3 Read the identification sticker present on the front panel of the CCM module
and check that the module can be migrated to the target configuration with the
material present at site.
4 Check which cables can be kept for re-use.
5 Validate that the cables available at site (including the ones which are kept for
re-use) are sufficient during the hardware upgrade according to the initial CCM-
U configuration
6 Unpack the new xCCM-U or eCCM-U
7 Check that the connectors of the new CCM are not damaged.
8 Keep the card packaging safe for the old card(s) to be re-sent

Continued on next page

28 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 5: CCM-U Migration, Continued

CCM-U physical The following procedure describes how to perform the physical exchange between CCM-U in
migration operation and new CCM-U.
procedure
Step Action
1 Prepare Node B for service interrupting work::
lock the cells of the NodeB
lock the site

NOTE: To be performed by OMC operator

2 Disconnect all the connectors from the front panel of the CCM-U module as
follows:
by hand for the RJ45 connectors (if used)
by hand for the Optical SFP or Electrical SFP from the SFP cages
by using a screwdriver for the Y or I PCM Cable Sub D connectors from the
xCCM-U and from the MDA E1/T1
by hand for GPS Synchro RJ45 connectors cable (if used)
by hand for Alarm cable between CCM-U and RUC

3 Remove all internal PCM cables that are not to be re-used with the xCCM-U.

xCCM-U Module Disconnection

4 Unscrew the two screws of the CCM-U module

5 Put on the antistatic wrist strap

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 5: CCM-U Migration, Continued

CCM-U physical
migration
Step Action
procedure
(continued) 6 Extract the CCM-U module using the front panel handle and the extraction tool
and carefully remove the module from the slot guides.

NOTE: The eCCM-U or xCCM-U modules are hot-pluggable. The digital shelf is
not operational during these steps.

7 Put the removed CCM-U into the antistatic bag and then into the cardboard
packaging that the new xCCM-U or eCCM-U was delivered in and include all
internal PCM cables that are not to be re-used.
8 Configure the eCCM-U's DIP-switch for UMTS use.

NOTE: By default the eCCM-U is configured from factory to be in LTE Network

configuration.

Continued on next page

30 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 5: CCM-U Migration, Continued

CCM-U physical
migration
Step Action
procedure
(continued) 9 Carefully insert the new CCM-U module and push it firmly into the slot.

NOTE: The CCM-U module is plug-and-play. The LEDs should turn on and the
all digital boards are restarted.
10 Tighten the 2 screws on the CCM-U module front panel.

December 15, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 6: New CCM-U Backhaul Connection

Description The migrated x/eCCM-U must be connected to the backhaul interface. The type of connection
and how it will be performed is dependent on the chosen CCM-U configuration, backhaul
interface type and available option at site.

NOTE: Select the procedure based on CCM-U configuration, backhaul interface type and
option.

Table 14: CCM-U board backhaul configurations

CCM-U configuration Backhaul interface Option

type
xCCM-U + MDA E1/T1 E1/T1 w/ LPPCM
wo/ LPPCM
xCCM-U + MDA GE E1/T1 w/ LPPCM
wo/ LPPCM
xCCM-U + MDA GE IP electrical
optical
eCCM-U + MDA GE E1/T1 w/ LPPCM
wo/ LPPCM
eCCM-U + MDA GE IP electrical
optical

Continued on next page

32 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 6: New CCM-U Backhaul Connection, Continued

E1/T1 The following procedure describes how to connect the E1/T1 PMC to the xCCM-U + MDA
connection E1/T1
procedure
xCCM-U + MDA
E1/T1 w/ Step Action
LPPCM
1 Check availability of the correct connection cables:
3JR22030AA CABLE : LPPCM PCM OUT/XCCM IUB
2 Connect cable on xCCM-U side and LPPCM side as per following figure

E1/T1 The following procedure describes how to connect the E1/T1 PMC to the xCCM-U + MDA
connection E1/T1 wo/ Lightning Protection PCM unit.
procedure
xCCM-U + MDA
E1/T1 wo/ Step Action
LPPCM
1 Check availability of the correct connection cables
3JR22031AA CABLE : ADAPTOR XCCM-U IUB/EXTPCM EVO
2 Connect cable on xCCM-U side and up to the PCM cable and to the terminator
block side as per following figure

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 6: New CCM-U Backhaul Connection, Continued

E1/T1 The following procedure describes how to connect the E1/T1 PMC to the xCCM-U + MDA GE
connection w/ Lightning Protection PCM unit.
procedure
xCCM-U + MDA
GE w/ LPPCM Step Action
1 Check availability of the correct connection cables
3JR22080AB CABLE : 4PCM XCCM-U D2U CABLE
2 Connect cable on xCCM-U side and up to the LPPCM as per following figure

E1/T1 The following procedure describes how to connect the E1/T1 PMC to the xCCM-U + MDA GE
connection wo/ Lightning Protection PCM unit.
procedure
xCCM-U + MDA
GE wo/ LPPCM Step Action
1 Check availability of the correct connection cables
3JR22093AA CABLE: ADAPTOR 4 PCM XCCM-U
2 Connect cable on xCCM-U side and up to the PCM cable and to the terminator
block side as per following figure

Continued on next page

34 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 6: New CCM-U Backhaul Connection, Continued

E1/T1 The following procedure describes how to connect the E1/T1 PMC to the eCCM-U + MDA GE
connection w/ Lightning Protection PCM unit.
procedure
eCCM-U + MDA
GE w/ LPPCM Step Action
1 Check availability of the correct connection cables
3JR22080AB CABLE : 4PCM XCCM-U D2U CABLE
2 Connect cable on eCCM-U side and up to the LPPCM as per following figure

E1/T1 The following procedure describes how to connect the E1/T1 PMC to the eCCM-U + MDA GE
connection wo/ Lightning Protection PCM unit.
procedure
eCCM-U + MDA
GE wo/ LPPCM Step Action
1 Check availability of the correct connection cables
3JR22093AA CABLE: ADAPTOR 4 PCM XCCM-U
2 Connect cable on xCCM-U side and up to the PCM cable and to the terminator
block side as per following figure

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 6: New CCM-U Backhaul Connection, Continued

IP connection The following procedure describes how to connect the IP interface, electrical to the eCCM-U +
procedure MDA GE
xCCM-U + MDA
GE / eCCM-U +
MDA GE Step Action
electrical
1 Check availability of the correct connection cables
Category 6 Ethernet cable. CAT6
2 Route the (RJ45 CAT5) Backhaul Cable up to the MDA
3 Connect the RJ45 CAT5 Backhaul Cable to the MDA module

Continued on next page

36 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 6: New CCM-U Backhaul Connection, Continued

IP connection The following procedure describes how to connect the IP interface, optical to the eCCM-U +
procedure MDA GE
xCCM-U + MDA
GE / eCCM-U +
MDA GE optical Step Action
1 Check availability of the correct connection cables

2 Route the Backhaul Optical Cable up to the MDA

3 Insert the Optical Transceiver SFP into the SFP cage on the MDA (Only one
SPF1 connection is used today)

4 Connect the Backhaul LC optical fiber to the optical transceiver SFP port.

December 15, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 7: Protection cover Installation

Description Unused interface connectors at the CCM-U need to be protected by covers.

D-Sub Cover The following procedure details how to install the cover on the D-Sub connector not in use.
installation
procedure
Step Action
1 Check Cover availability

2 Install the D-Sub Cover on the PCM E1/T1 connector (26p (M)) of the xCCM-U
or eCCM-U and tighten the 2 screws.

Continued on next page

38 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 7: Protection cover Installation, Continued

SFP Cover The following procedure details how to install the cover on the SFP connector not in use.
installation
procedure
Step Action
1 Check Cover availability: 1AD138010002 - SFP CAGE COVER

NOTE: There are 2 SFP ports on the MDA-GE. Each SFP port not in use must
be protected by an SFP cage cover.
Qty = 2 nb_SFP in use.
2 Install the SFP cover on unused SFP cages as illustrated

December 15, 2013 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc.8: CCM-U unchanged cables installation

Description Cables which are not impacted by the CCM-U migration are to be re-connected
Alarm cables
GPS sync cable
Optical or electrical radio module links
PCM, optical or electrical Backhaul connection cable.

D4U overview with cable connection positions

D2U overview with cable connection positions

40 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 9: Radio modules connection

Description All available radio modules (e.g. RRHs) need to be connected to the CCM-U through their
optical interfaces (mainly RRH)
electrical interfaces (mainly MC-TRX, TRDU)

NOTE: Number of interface connections required are dependent on the radio module
configuration.

Optical RRH
interface SFP

IMPORTANT: Specific care must be taken that the correct SFP modules are
available for the installation.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 9: Radio modules connection, Continued

Radio module The following procedure describes how to connect optical link to the radio module
connection
procedure
optical Step Action
1 Route the Optical link from the RRH up to the SFP cages
2 Remove the caps from the SFP cages 1 to 6 as needed

NOTE: Keep the cap on the SFP cage not required

3 Insert the optical transceiver SFP into the SFP cage according to the RRH
configuration and configuration rules
4 Connect the LC optical fiber to the optical transceiver SFP port.

Continued on next page

42 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 9: Radio modules connection, Continued

Radio module The following procedure describes how to connect the electrical link to the radio module
connection
procedure
electrical Step Action
1 Route the electrical link from the TRDU or the MCTRX up to the SFP cages
2 Remove the caps from the SFP cages 1 to 6 as needed

NOTE: Keep the cap on the SFP cage not required

3 Insert the electrical connection cable into the SFP cage according to the
configuration and configuration rules.

TRDU case:

MC-TRX case:

December 15, 2013 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 10: CCM-U Start-up and Visual Checks

Description After completion of all cabling the CCM-U is ready to be commissioned and integrated. The
result of this step is the Node B back in service.
NOTE: In case of need the SW version of the CCM-U will be updated automatically and the
Node B is re-built automatically.

Automatic After the physical migration of the CCM-U card:

software Automatic software download action is launched by WMS if the software inside CCM-U is
download different to software version stored in OAM database
function

NOTE: The downloaded software is activated automatically when complete.

NOTE: SW download and activation takes around 15 minutes and can be monitored by use of
Command manager window if the system_user user is selected.

Automatic The objective of this procedure is to check the automatic software downloading from OMC is
Software successfully performed.
Downloading NOTE: This operation must be done by OMC operator.
from OMC

Automatic The following table explains how to perform the checks of the automatic download
software
download
monitoring Step Action
procedure
1 Open Command Manager window.
2 Click on button Filter to select system as system-user
3 Check for display of download and activate messages.

NOTE: If these messages don't appear then, check flag automatic upgrade is
enabled. From NSP select the NodeB and, select Equipment
monitor/BTSEquipment / Object Editor to open flag view. If the flag is
desable then , enbale it and check again.

Continued on next page

44 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 10: CCM-U Start-up and Visual Checks,

Continued

BTS automatic After migration of each CCM-U card an automatic build action is launched automatically by
build function WMS.

NOTE: This function sends the required configuration data to the NodeB and it takes around 7
minutes to complete

BTS automatic The objective of this procedure is to monitor the BTS automatic build from OMC.
build from OMC

NOTE: This operation must be done by OMC operator.

Automatic BTS The following table explains how to perform the monitoring of the automatic build.
build function
monitoring
procedure Step Action
1 Open Command Manager window.
2 Click on button Filter to select system as system-user
3 Check for display of BTS Automatic build message.

NOTE: If this message don't appear then, launch the build manually. From NSP
select the NodeB and clic on BTS MIB rebuild.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 10: CCM-U Start-up and Visual Checks,

Continued

xCCM-U The following procedure describes the steps to configure, integrate and validate the xCCM-U
migration after the migration.
start-up and
final check
procedure NOTE: Node B is back in operation during this procedure

Step Action
1 Check xCCM-U board LEDs for
Red LED on.
Green LED on.

NOTE: The digital boards need around one minute for the xCCM-U and two
minutes for the other boards to display the status.
2 Perform the NodeB Commissioning procedure to adapt the IP Parameters and
the electrical or optical links according to the network configuration.

NOTE: Follow the following section of the IEH521 Section 302 NodeB
Commissioning Procedure

NOTE: Transport network configuration needs must match the settings of the
Node B for successful further steps.
3 Unlock the NodeB and the Cells of the Node B.

NOTE: To be performed by OMC operator

4 Validate LED status after unlocking the Node B and Cells.

All the digital x boards (xCCM-U, xCEM-U) must have:

Red LED off.

Green LED on

5 Perform communication test as described in Proc.2: Final Communication Test

and compare the results for sanity

NOTE: The results of the communication test need to be comparable.

Continued on next page

46 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 10: CCM-U Start-up and Visual Checks,

Continued

xCCM-U
migration NOTE: A fall-back to the original configuration is required if
start-up and
final check the migrated xCCM-U does not come up
procedure the migrated xCCM-U cannot be activated with the new commissioning data
(continued) the communication test results are not comparable (sanity)

eCCM-U The following procedure describes the steps to configure, integrate and validate the xCCM-U
migration after the migration.
start-up and NOTE: Node B is back in operation during this procedure
final check
procedure
Step Action
1 Check the LED status for the operational state of the eCCM-U after start-up:
The CMA #4 LED must be off and the CMA #3 LED must be green.(module
OK, UBOOT after BIST execution if BIST result is OK)
The CMA #2 LED should be yellow for UMTS or green for LTE.
The CMA #1 LED must be green. (active module)

NOTE: Startup time

Around two minutes for CCM-U
Around three minutes for CEM-U
2 Check synchronization status of the eCCM-U dependent on the configuration
under use

Sync: #1 to #4 is green if the 9926 d4U is Synchronized to the PCM (1 to 4).

or Sync: #5 to #8 is orange if the 9926 d4U is Synchronized to the PCM (5 to
8).
Sync: #1 to #4 is red if the 9926 d4U is Synchronized to the local clock
(means no connection).

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 47

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

Proc. 10: CCM-U Start-up and Visual Checks,

Continued

eCCM-U
migration
Step Action
start-up and
final check 3 Check synchronization status of the radio modules interfaces
procedure
(continued) Rx and Tx are Green: The communication is established between the 9926
d4U and the RRH or TRDU unit.
RX is Green and Tx is OFF: The RRH or TRDU unit is trying to communicate
with the Node B but without success.
Rx and Tx are OFF: No RRH or TRDU unit is connected or the RRH or
TRDU unit is not powered

4 Adapt the IP parameters and the electrical or optical link according to the
network configuration.

NOTE: Follow the following section of the IEH521 Section 302 NodeB
Commissioning Procedure

NOTE: Transport network configuration needs to match the settings of the

Node B for successful further steps.

NOTE: No commissioning is required if backhaul connection data are

unchanged
5 Unlock the NodeB and the cells of the Node B.

NOTE: To be performed by OMC operator

6 Perform communication test as described in Proc.2: Final Communication Test
and compare the results for feasibility and sanity

NOTE: The results of the communication test need to be comparable.

NOTE: A fall-back to the original configuration is required if

the migrated xCCM-U does not come up
the migrated xCCM-U cannot be activated with the new commissioning data the
communication test results are not comparable (sanity)

48 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CCM-U Board Migration Procedure IEH 521, Section 702

Proc. 11: Final Checks and Clean-up

Description Final actions at site are required to complete the CCM-U migration work before leaving the site

Final checks and The following procedure describes the final steps of action before leaving the site
clean-up
procedure
Step Action
1 Verify that all cables are correctly marked and secured with tie-wraps in case of
radio reconfiguration
2 Complete the report sheet.

NOTE: All cases of non-compliances identified during the migration must be

described.
3 Send report sheet to coordinator.

NOTE: Corrective actions to be synchronized with the coordinator.

4 Send the cardboard packing box with the old CCM-U module back to Alcatel-
Lucent

NOTE: Address is coordinator or supervisor of these retrofits

5 Close and lock the NodeB's doors and clean the site.

Fall-back to
initial CCM-U
configuration
IMPORTANT: If necessary and only with technical support and/or the coordinator's
approval a fall-back to the initial CCM-U configuration can be done by repeating all the previous
procedures under use of the CCM-U and saved I&C parameters.

December 15, 2013 Alcatel-Lucent Internal 49

Proprietary Use pursuant to Company instruction
IEH 521, Section 702 CCM-U Board Migration Procedure

This page intentionally left blank.

50 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 703

December 15, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

CEM-U Board Migration Procedure

Table of Contents

General ............................................................................................................ 4
Scope of migration ........................................................................................... 4
CEM terminology ............................................................................................. 4
Operational Impacts ......................................................................................... 4
Restrictions.................................................................................................... 4
Minimizing operational impact: common migration for CEM-U & CCM-U .......................... 5
Previous Release Date ....................................................................................... 5
Release Notes ................................................................................................. 5
References ........................................................................................................ 6
General ........................................................................................................ 6
Documentation Access ...................................................................................... 6
Applicable IEH521 Sections ................................................................................. 6
Applicable Methods Documents............................................................................ 6
Tools Requirements ............................................................................................. 7
General ........................................................................................................ 7
Hardware Tools ............................................................................................... 7
Material Requirements ......................................................................................... 8
Description .................................................................................................... 8
CEM-U configuration rules .................................................................................. 8
Board requirements .......................................................................................... 8
Report sheet .................................................................................................. 8
Record Sheet ..................................................................................................... 9
Description .................................................................................................... 9
Input parameter sheets ..................................................................................... 9
Communication test results sheet ...................................................................... 10
Antenna positions sheet .................................................................................. 10
RNC software version ...................................................................................... 11
License parameter sheet ................................................................................. 11
Sign-off sheet ............................................................................................... 12
CEM-U Board Migration Procedure Overview ............................................................. 14
Description .................................................................................................. 14
CEM-U Migration flow diagram ........................................................................... 14

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

CEM-U board migration procedure overview table ................................................. 15

Precautions ..................................................................................................... 16
Description .................................................................................................. 16
Safety related information ............................................................................... 16
Equipment Safety Requirements ........................................................................ 16
Preparations before CEM-U migration procedure execution ........................................... 17
Description .................................................................................................. 17
Initial Check ................................................................................................. 17
Final Material Checks ...................................................................................... 17
x/eCEM-U position within digital shelf d4U ........................................................... 17
x/eCEM-U position within digital shelf d2U ........................................................... 18
Pre-Migration board checklist............................................................................ 18
Proc. 1: CEM-U Sanity Check ................................................................................ 19
Description .................................................................................................. 19
Visual check procedure ................................................................................... 19
Alarm conditions ........................................................................................... 21
Proc. 2: Initial communication Test........................................................................ 22
Description .................................................................................................. 22
Initial communication test procedure .................................................................. 22
Proc. 3: Save I&C Parameter ................................................................................ 23
Description .................................................................................................. 23
Save I&C parameters procedure ......................................................................... 23
I&C parameters use for backup ........................................................................ 23
Proc.4 : CEM-U Board Migration ............................................................................ 24
Description .................................................................................................. 24
Multiple CEM-U boards .................................................................................... 24
Lock of CEM-U procedure ................................................................................. 24
CEM-U physical board migration procedure ........................................................... 28
Unlock CEM-U board procedure.......................................................................... 30
Proc.5: NodeB on line check ................................................................................ 34
Description .................................................................................................. 34
CEM-U LED visual check procedure ..................................................................... 34
NodeB software and alarm check procedure .......................................................... 35
Proc. 6: Communication Tests .............................................................................. 37
Description .................................................................................................. 37
Final communication test procedure ................................................................... 37
Communication test results .............................................................................. 38
Fall back ..................................................................................................... 38
Proc. 7: Fall Back of CEM-U.................................................................................. 39
Description .................................................................................................. 39
Fall-back procedure ....................................................................................... 39
Proc. 8: Final Checks and Clean-up ........................................................................ 40
Description .................................................................................................. 40
Final checks and clean-up procedure................................................................... 40

List of Figures

Figure 1: CEM-U Migration in d4U flow chart ....................................................................... 14

Figure 2: x/eCEM-U location within the 9926 d4U................................................................. 17

2 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Figure 3: x/eCEM-U location within the 9926 d2U................................................................. 18

List of Tables

Table 1: Applicable IEH 521 Sections for CEM-U Migration in d2U / d4U NodeB ............................... 6
Table 2: Applicable Methods documents for IEH 521 ............................................................... 6
Table 3: Hardware Tools ................................................................................................. 7
Table 4: CEM Module configuration table ............................................................................. 8
Table 5: CEM-U boards order information ............................................................................ 8
Table 6: BTS Parameters ................................................................................................. 9
Table 7: RNC Parameters ................................................................................................ 9
Table 8: Communication Tests ........................................................................................ 10
Table 9: Antennae Positions ........................................................................................... 10
Table 10: RNC Software ................................................................................................ 11
Table 11: License Parameter .......................................................................................... 11
Table 12: Sequence of Operations ................................................................................... 12
Table 13: Sign Off ....................................................................................................... 13
Table 14: CEM-U board migration .................................................................................... 15
Table 15: CEM Module pre-migration checklist .................................................................. 18

December 15, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

General

Scope of This section provides detailed information to perform the migration of CEM-U boards inside the
migration 9926 d4U or 9926 d2U.

NOTE: Reason for the migration can be

Increase of processing power and capacity
xCEM-U board unavailability

NOTE: Modification of number of CEM-U boards is NOT subject of this procedure.

CEM terminology The generic term CEM-U is used for xCEM-U or eCEM-U.

Operational
Impacts

IMPORTANT: The CEM-U migration procedure is normally NOT service impacting

while performed with more than one CEM-U in the Node B.
If there is only one CEM-U in the Node B the service is interrupted.

Restrictions In case of hosting 2 Node B in a single d4U restrictions apply on the distribution of the CEM-U
into card slots.

Continued on next page

4 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

General, Continued

Restrictions
(continued)

IMPORTANT: CEM board to CCM board assignment rules are existing as per table
below

CCM-U board CEM-U board Node B configuration

configuration allocated
CCM-U = slot 5 CEM-U = 1,2,3,6,7,8 Single Node B configuration

NOTE: Up to 6 CEM-U can

be assigned to one CCM-U
CCM-U = slot 5 CEM-U = 4,5,6 Dual Node B configuration

NOTE: Up to 5 CEM-U can

be assigned to CCM-U
CCM-U = slot 4 CEM-U = 1,2,3 Dual Node B configuration

NOTE: Up to 3 CEM-U can

be assigned to CCM-U

NOTE: Number of CEM-U boards is dependent on engineering for the Node B (performance)

Minimizing
operational
impact: common
migration for IMPORTANT: Effort and service impacts can be minimized by combining CEM-U
CEM-U & CCM-U and CCM_U migrations in case they are required for the same digital shelf.
Refer to IEH521-702 for the CCM-U board migration procedure.

Previous Release New creation

Date

Release Notes New creation: Dec 2013 under utilization of existing IM documents from UA08.1.

December 15, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
CEM migration in d2U or d4U NodeB.

Documentation Access to applicable documents can be made under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable The sections listed in Table 1 below are required for CEM-U migration procedure in d4U
IEH521 Sections NodeB.

Table 1: Applicable IEH 521 Sections for CEM-U Migration in d2U / d4U
NodeB

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
310 Node B Commissioning Test
399 Node B Commissioning Test Records
702 CCM-U Board Migration Procedure

Applicable The following methods documents are required to perform the CEM-U migration procedure in
Methods d4U NodeB
Documents
Table 2: Applicable Methods documents for IEH 521

Doc Number Doc Title URL

NN-20500-203 Alcatel-Lucent 9326 digital https://infoproducts.alcatel-
2U Node B V2 - Technical lucent.com/aces/cgi-
Description bin/dbaccessfilename.cgi/N
N20500203UA08.1_V1_
3MN-01637-0004-DEZZA Alcatel-Lucent 9926 digital http://cic.us.alcatel-
4U Node B - Technical lucent.com/pdfdocs14/pristor
Description e215/529526.pdf

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

6 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Tools Requirements

General The CEM-U migration demands the use of several tools.

Hardware Tools The hardware tools listed in the following table are required to perform the CEM-U migration.

Table 3: Hardware Tools

Tool / Test Set Qty. Description

1 Anti-static wrist strap
3JR08430AA 1 Handle extractor key
1 screwdriver
Keys to open the
1 set cabinet.doors (+ customer
site)
for outdoor product, tent if
1 the weather is rainy or
snowy.
Lamp, depending on time of
1
intervention.
1 Laptop PC
RJ45 PCMCIA Ethernet
board 10/100 BT
1 RJ45 crossover cable
1 or 3 UMTS Debug Mobile
1 SIM Card

December 15, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Material Requirements

Description Prior to the start of migration it has to be ensured that all demanded material is available.

CEM-U The following table describes the x/eCEM-U board configuration rules
configuration
rules Table 4: CEM Module configuration table

Topic Configuration rule comments

Number of boards Up to 6 eCEM-U or/and Single Node B application
xCEM-U in one digital shelf
Number for boards Up to 6 eCEM-U or/and 2 Node B application
xCEM-U in one digital shelf
Mixity eCEM-U and xCEM-U can
be freely mixed within the
allowed d4U slots

Board The following table provides information on the CEM-U boards ordering codes
requirements
Table 5: CEM-U boards order information

PEC Module
300986049 xCEM-U
3JR20059DA eCEM-U

Report sheet The report sheet is required for the migration of the CEM-U board(s).

8 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Record Sheet

Description A number of record sheets are available to support the information collection and
documentation for the CEM-U migration.

Input parameter The sheets are available to capture information prior to starting the migration activities.
sheets

Table 6: BTS Parameters

Parameter Content Parameter Content
BTS IP Address NodeB Outdoor / Indoor

OMC-B IP address Configuration

Sub-network mask Software version

Hardware
reference
Software upgrade on Yes / No
BTS:

Table 7: RNC Parameters

Parameter RNC-CN RNC-IN RNC-AN
Name

IP Address

Password

ATMIF employed

IUXIF employed

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Record Sheet, Continued

Communication The following sheet is available to support the documentation of the communication test
test results results.
sheet

Table 8: Communication Tests

CS call validation PS call validation status
Voice Call Test Ping Test

Iur link validation FTP Uplink Test

Test

Video Streaming Test FTP Downlink Test

Primary Scrambling
Code

Antenna The following antenna position sheet must be filled by the coordinator and / or commissioner
positions sheet before the site intervention.

Table 9: Antennae Positions

Cell 0 1 2 3 4 5 6
Azimuth

Continued on next page

10 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Record Sheet, Continued

RNC software The following RNC software table must be filled by the coordinator and/or the commissioner
version before the site intervention

Table 10: RNC Software

RNC-AN RNC-IN
.

License The following license parameter table must be filled

parameter sheet
Table 11: License Parameter
Item Information to be filled in
Product

Release

Customer Name

Host Name

Start Date

End Date

Bitmap

Key

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Record Sheet, Continued

Sign-off sheet The following sheet is available to support the documentation of the procedure and final sign-
off of results.

Table 12: Sequence of Operations

Step Procedure Condition To Ok Nok

ap-
ply
1 Check documents and hardware
tools are present
2 Pre requisites and checklist

3 CEM-U Sanity check

4 Initial communication Test

5 Save I&C parameters

6 CEM-U Migration

7 NodeB on line check

8 Communication tests

9 Roll back of CEM-U

Continued on next page

12 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Record Sheet, Continued

Sign-off sheet
(continued)
Table 13: Sign Off

Coordinator Commissioner Customer

Representative
Company name

Functions

Name

Signature

Date

Comments

December 15, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

CEM-U Board Migration Procedure Overview

Description The CEM-U migration procedure consists of a sequence of steps. The sequence of the steps
as well as their names are described in this chapter to provide the necessary overview.

CEM-U The flow diagram below outlines the CEM-U migration steps to occur.
Migration flow
diagram Figure 1: CEM-U Migration in d4U flow chart

Continued on next page

14 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

CEM-U Board Migration Procedure Overview, Continued

CEM-U board The purpose of this table is to give an overview of the mandatory or optional tasks to perform
migration the CEM-U migration.
procedure Table 14: CEM-U board migration
overview table

Operation Optional / Procedures Remarks

Mandatory
Check documents M - Must be check by on
and hardware tools site team
are present
Pre requisites and M - Must be check by on
checklist site team
CEM-U Sanity check M Procedure 1 Must be check by on
site team
Initial M Procedure 2 Must be done by on
communication Test site team
Save I&C M Procedure 3 Must be done by on
parameters site team
CEM-U Migration M Procedure 4 Must be done by on
site team
NodeB on line check M Procedure 5 Must be done by on
site team
Communication M Procedure 6 Must be done by on
tests site team
Roll back of CEM-U O Procedure 7 Must be done by on
site team

December 15, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Precautions

Description This chapter describes the precautions to undertake before launching the migration procedure.

Safety related This document contains safety statements.

information Safety statements are given at points where risks of damage to personnel, equipment, or
operation may exist.
Failure to follow the directions in a safety statement may result in serious consequences.

Equipment
Safety
Requirements

IMPORTANT: Wearing an anti-static bracelet connected to ground via a protective

resistance to avoid damaging circuits when handling printed circuits is mandatory.

IMPORTANT: In all the following procedures and steps the ESD foam must be
provided and must be used during any operation on board and the bench.

IMPORTANT: EMC sealing joints being fragile, shocks and hand contact must be
avoided.

IMPORTANT: No mechanical parts of the 9926 d4U or CCM-U board must never
be modified on site (holes, etc.).

16 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Preparations before CEM-U migration procedure

execution

Description This chapter describes the preparations to be done before launching the migration process.

Initial Check Before going on site ensure with OMC operator that the initial configuration is in operational
status without any alarm.

Final Material Before starting removal operation ensure that

Checks The correct amount of x/eCEM-U modules with the correct interface card is delivered in card
boxes.
The packaging is straight up and does not show any visible sign of faulty storing or handling.
All personal and product safety requirements are being met.

x/eCEM-U The following figure outlines the position of the CEM-U modules within the digital unit (d4U).
position within
digital shelf d4U Figure 2: x/eCEM-U location within the 9926 d4U

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Preparations before CEM-U migration procedure

execution, Continued

x/eCEM-U The following figure outlines the position of the CEM-U modules within the digital unit (d2U).
position within
digital shelf d2U Figure 3: x/eCEM-U location within the 9926 d2U

Pre-Migration The following checklist provides all items to be validated before start of the CEM-U migration
board checklist
Table 15: CEM Module pre-migration checklist

Initial Configuration Final configuration Board requirement

xCEM-U eCEM-U eCEM-U

18 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc. 1: CEM-U Sanity Check

Description This procedure step is available to validate the operational status and health of the CEM-U
board before removal from the digital shelf.

Visual check The following procedure describes how to perform the sanity check before removal of the CEM-
procedure U cards from the digital shelf.

Step Action
1 Identify all CEM-U modules which are subject for migration to be present and
their slots.

NOTE: Single Node B configuration requires xCEM-U board in slot 5.

NOTE: Two Node B hosting in one 9921 d4U requires xCEM-U boards in slots
4 and 5.

2 Record the initial configuration in the Report sheet

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc. 1: CEM-U Sanity Check, Continued

Visual check
procedure
Step Action
(continued)
3 Check the LED status of the targeted CEM-U board(s) for their status
dependent on the board type

xCEM-U: the lower green LED is on; upper red LED is off.
eCEM-U: third LED from the bottom is green; fourth LED from the bottom is
off.

xCEM-U:

eCEM-U:

Continued on next page

20 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc. 1: CEM-U Sanity Check, Continued

Visual check
procedure
Step Action
(continued)
4 Check the LED status of other digital modules (x/eCCM-U) for their operational
status dependent on the board type:

xCCM-U: the green lower LED should be on; upper red LED is off
eCCM-U: the LED CMA 3 is green; LED CMA 4 is off

xCCM-U:

eCCM-U:

5 Verify with OMC-B technician correctness of local alarm check and that there
are no CEM-U and CCM-U alarms

NOTE: The OMC technician can retrieve alarm status through the OMC operation
Show NEs Alarms
6 Record alarm status for CEM-U board dedicated for migration into report sheet.

Alarm conditions NOTE: If the Node B is not error free, refer to the technical support or the coordinator for trouble
shooting.

December 15, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc. 2: Initial communication Test

Description The internal communication test is available to proof full operational status of the digital shelf
and the CEM-U prior to the CEM-U migration. The test is performed to have a baseline before
the operation starts.

Initial The following table describes how to perform the initial communication test
communication
test procedure Step Action
1 Position the UMTS Mobile in the area covered by the NodeB.
2 Check the Primary Scrambling Code at the OMC.

NOTE: The Primary Scrambling Code must be the same in OMC view and
UMTS Mobile to make sure that the tests are performed for the correct Node B
entity.
3 Activate the trace of the UMTS Mobile
4 Perform CS call to the OMC via the PSTN using the UMTS mobile.
Verify Primary Scrambling Code is the same at OMC and UMTS mobile
5 Record the result of the test (Success / No Success)
6 Perform PS call to validated successful PS communication

NOTE: Web browsing recommended

7 Record the result of the test (Success / No Success / web address)

8 Check on site that no unexpected alarm appear through local LED check

22 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc. 3: Save I&C Parameter

Description The objective of this procedure is to save I&C Parameters to keep the initial configuration
available in case of fall-back is required.

Save I&C The following procedure explains how to retrieve and save I&C parameters before service
parameters interrupting work starts
procedure
Step Action
1 Connect the RJ45 to : Port 1 if xCCM-U (or eCCM-U) used
2 Launch the TIL in local mode
3 Select from menu: I&C | Save I&C parameters

4 Click SAVE

NOTE: The file will be saved in <Default path>[email protected]>

folder. The <Default path> is the path defined when TIL is launched.

I&C parameters In case of a problem during the CCM-U migration which requires fall-back to the origin status
use for backup go back to this file in order to restore the default I&C parameters.

December 15, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc.4 : CEM-U Board Migration

Description The migration from one CEM-U board to the next is basically a replacement and consists of the
following basic operational steps:
Lock CEM-U before migration to force live traffic to remaining CEM-Us in operation
Remove existing CEM-U board
Insert new CEM-U board
Unlock new CEM-U board to bring it back to operation

IMPORTANT: CEM-U board is hot swappable. The d4U remains in operation when
board removed and re-inserted.

Multiple CEM-U The CEM-U board migration procedures must be repeated for each CEM-U board under
boards migration.

Lock of CEM-U The following procedure describes how to lock the CEM-U prior to removal.
procedure
NOTE: Locking of CEM-U is performed through WMS GUI.

Step Action
1 Notify OMC operator of service impacting work

Service interruption occurs: Only one CEM-U in digital shelf

Service reduction occurs: More than one CEM-U in digital shelf
2 Select Equipment Monitor of the concerned NE on the WMS Resource
Browser window
.

Continued on next page

24 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc.4 : CEM-U Board Migration, Continued

Lock of CEM-U
procedure
Step Action
(continued)
3 Open BTS Equipment monitor window for Node B and select CEM-U board
dedicated for migration and check operational status:
administrativeStatemust be unlocked
standbyStatus must be providingService
operationalState must be enabled
standbyStatus must be providingService

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc.4 : CEM-U Board Migration, Continued

Lock of CEM-U
procedure
Step Action
(continued)
4 Select the concerned CEM-U board by clicking on it, then right click on the
mouse and choose Configuration|Set Administrative State.

Continued on next page

26 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc.4 : CEM-U Board Migration, Continued

Lock of CEM-U
procedure
Step Action
(continued)
5 Lock CEM-U in the Set Administrative State Action Window by pressing Lock
button.

NOTE: The CEM-U board passes from an UNLOCKED to a LOCKED.

NOTE: The CEM-U board passes into an i status on the monitor window

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc.4 : CEM-U Board Migration, Continued

CEM-U physical The following action list details how to physically exchange the CEM-U board under migration.
board migration
procedure

IMPORTANT: When inserting an eCEM-U board, the neighboring xCEM-U board

may reboot which results in operational impact to this xCEM-U under operation. To avoid this
operational impact (traffic loss) the cell or sector associated with the xCEM-U must be locked.

Step Action
1 Loosen the two screws of the CEM-U board subject to replacement
2 Extract the CEM-U module by use of front panel handle and carefully remove
the module from the slot guides

NOTE: The CEM-U module is hot-pluggable

3 Put the old CEM-U in the antistatic bag and then in the cardboard packaging (in
which the new CEM-U was delivered).

Continued on next page

28 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc.4 : CEM-U Board Migration, Continued

CEM-U physical
board migration
Step Action
procedure
(continued) 4 Insert carefully the new CEM-U module into the same slot from which the old
CEM-U got removed.

NOTE: The CEM-U module is plug and play

NOTE: The on-board LEDs must turn ON and the other digital boards should
restart.

5 Tighten the two screws of the new CEM-U module front panel.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc.4 : CEM-U Board Migration, Continued

Unlock CEM-U The following table describes how to unlock a migrated CEM-U. This action will allow the CEM-
board procedure U to handle traffic.
NOTE: This procedure should be repeated for each migrated CEM-U.

NOTE: Un-locking of CEM-U is performed through WMS GUI.

Step Action
1 Select Equipment Monitor of the concerned NE on the WMS Resource
Browser window
.

Continued on next page

30 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc.4 : CEM-U Board Migration, Continued

Unlock CEM-U
board procedure
Step Action
(continued)
2 Open BTS Equipment monitor window for Node B and select CEM-U board
(by clicking on it) under migration and check operational status:
administrativeStatemust be locked
standbyStatus must be providingService
operationalState must be enabled

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc.4 : CEM-U Board Migration, Continued

Unlock CEM-U
board procedure
Step Action
(continued)
3 Select the concerned CEM-U board by clicking on it, then right click on the
mouse and choose Configuration|Set Administrative State.

Continued on next page

32 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc.4 : CEM-U Board Migration, Continued

Unlock CEM-U
board procedure
Step Action
(continued)
4 Un-lock CEM-U in the Set Administrative State Action Window by pressing
Unlock button.

NOTE: The CEM-U board passes from an LOCKED to a UNLOCKED.

NOTE: The CEM-U board passes from i status into grey/white status on the
monitor window

December 15, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc.5: NodeB on line check

Description The software version of the CEM-U and alarm status of the Node B must be checked prior to
setting CCP status.

CEM-U LED The following procedure describes the steps to check the LEDS of the CEM-U.
visual check
procedure Step Action
1 Visualize the migrated CEM-U
2 Validate LED status after unlocking the Cells, depending on the board type.

Board LED Status

xCEM-U

The lower green LED is on; upper red LED is off.

eCEM-U
First LED from bottom is off
Second LED Yellow/amber is for UMTS
Third LED from the bottom is green
Fourth LED from the bottom is off

Continued on next page

34 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc.5: NodeB on line check, Continued

NodeB software This procedure describes how to check that there is no unexpected alarms at the NodeB.
and alarm check
procedure Step Action
1 Verify that there no alarms on migrated CEM-U by use of TIL in local mode.

Example Of TIL Board Screen with eCEM-U

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc.5: NodeB on line check, Continued

NodeB software
and alarm check
Step Action
procedure
(continued) 4 Validate with OMC operator that there is no alarm raised for the Node B under
migration

NOTE: To be performed through WMS GUI (operator level).

Select Node B under migration and Show Alarms to retrieve alarm manager
window at the WMS.

5 Verify in Alarm Manager window that there are no alarms displayed for CCM-U
and CEM-U.

NOTE: Unexpected alarms must be cleared before continuation

36 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc. 6: Communication Tests

Description The internal communication test is available to proof full operational status of the digital shelf
and the CEM-U after the CEM-U migration. The test is performed to compare the results
against the baseline test results from before the operation.

Final The following table describes how to perform the final communication test
communication
test procedure Step Action
1 Position the UMTS Mobile in the area covered by the NodeB.
2 Check the Primary Scrambling Code at the OMC.

NOTE: The Primary Scrambling Code must be the same in OMC view and
UMTS Mobile to make sure that the tests are performed for the correct Node B
entity.
3 Activate the trace of the UMTS Mobile
4 Perform CS call to the OMC via the PSTN using the UMTS mobile.
Verify Primary Scrambling Code is the same at OMC and UMTS mobile
5 Record the result of the test (Success / No Success)
6 Perform PS call to validated successful PS communication

NOTE: Web browsing recommended

7 Record the result of the test (Success / No Success / web address)
8 Check on site that no unexpected alarm appear through local LED check

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc. 6: Communication Tests, Continued

Communication The final communication test results must be comparable to the communication test results
test results prior to the CEM-U migration was started.
NOTE: Comparison of logged communication test results must happen to proof success of
migration operation
CS call
PS call

Fall back Fall-back to the original configuration is required if

the migrated CEM-U does not come up
the migrated CEM-U cannot be activated (unlocked)

38 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
CEM-U Board Migration Procedure IEH 521, Section 703

Proc. 7: Fall Back of CEM-U

Description In case of a non-operational CEM-U has been added a fall-back to the old CEM-U may be
required to bring the Node B back into service quickly.

IMPORTANT: This activity must only take place as trouble shooting action and is
not part of the normal CEM-U migration procedure

Fall-back The following procedure outlines on a higher level the flow of activities to roll back to the
procedure original CEM-U.

NOTE: The roll-back is principally a migration of the CEM-U and the described migration
procedure in this section can be used to perform this roll-back procedure.

Step Action
1 Ask the OMC technician to check there are no alarms . The OMC technician
should perform the operation NodeB on line check Proc.5
2 Lock the CEM-U Proc. 4.
3 Apply Proc. 4 CEM-U Board migration
Restore the I&C data saved before the migration with TIL. Proc. 3
Unlock the CEM-U Proc. 4.
4 Ask the OMC technician to check there are no alarms . The OMC technician
should perform the operation NodeB on line check - Proc. 5
5 Make a CS Test Call to prove functionality of 9926 d4U
6 Make a PS Test Call to prove functionality of 9926 d4U

December 15, 2013 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 703 CEM-U Board Migration Procedure

Proc. 8: Final Checks and Clean-up

Description Final actions at site are required to complete the CEM-U migration work before leaving the site

Final checks and The following procedure describes the final steps of action before leaving the site
clean-up
procedure Step Action
1 Verify that all cables are correctly marked and secured with tie-wraps in case of
radio reconfiguration
2 Complete the report sheet.

NOTE: All cases of non-compliances identified during the migration must be

described.
3 Send report sheet to coordinator.

NOTE: Corrective actions to be synchronized with the coordinator.

4 Send the cardboard packing box with the old CEM-U module back to Alcatel-
Lucent or to location as proposed by coordinator

NOTE: Address is coordinator or supervisor of these retrofits

5 Close and lock the NodeB's doors and clean the site.

40 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 705

December 15, 2013

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Single to Dual Node B Migration Procedures

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation Access ...................................................................................... 5
Applicable IEH 521 Sections ................................................................................ 5
Applicable Documents in LR13.x .......................................................................... 6
Tools Requirements ............................................................................................. 7
General ........................................................................................................ 7
Hardware Tool ................................................................................................ 7
Software Tool ................................................................................................. 7
Single to Dual Node B Migration Flow ........................................................................ 8
Purpose ........................................................................................................ 8
Applicable Configuration Cabinet ......................................................................... 8
Single to Dual Node B Migration flow diagram .......................................................... 9
Single to Dual Node B Migration Procedure Overview .................................................. 10
Reference of Migration Procedures Mandatory ..................................................... 10
Single to Dual Node B Migration Checklists ............................................................... 11
Purpose ...................................................................................................... 11
Checklist Customization .................................................................................. 11
Remote Operations Checklist ............................................................................ 11
Single to Dual Node B Form Parameters ................................................................... 12
General ...................................................................................................... 12
Node B Parameters Required prior to Dual Node B Migration ...................................... 12
Node B BTS Parameters ................................................................................... 13
Node B RRH Parameters................................................................................... 14
Node B Backhaul Parameters ............................................................................ 14
Node B Ethernet Parameters ............................................................................. 15
Node B IP Parameters ..................................................................................... 15
2NodeBs Parameters ....................................................................................... 16

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 1: Single to Dual Node B Migration Preparation ................................................... 17

Description .................................................................................................. 17
Preconditions ............................................................................................... 17
Naming Conventions ....................................................................................... 17
Dual Node B basic engineering rules .................................................................. 17
Modem Rules in Dual Mode Configuration in d4U ..................................................... 19
Upgrade Path Selection Procedure...................................................................... 20
Proc 2: Software Upgrade Procedure ...................................................................... 21
Description .................................................................................................. 21
Preconditions ............................................................................................... 21
Software Upgrade Procedure ............................................................................ 21
Proc 3: Migration Procedure: Single to Dual NodeB Mode .............................................. 24
Description .................................................................................................. 24
Preconditions ............................................................................................... 24
Parameters Configuration Procedure of CCM #A ..................................................... 24
Hardware Migration Procedure adding CCM #B ....................................................... 27
Parameters Configuration Procedure of CCM #B ..................................................... 29
Visual Check Procedure for Dual Node B configuration ............................................. 31
Proc 4: Downgrade Procedure: Dual to Single NodeB Mode ........................................... 34
Description .................................................................................................. 34
Preconditions ............................................................................................... 34
Downgrade Procedure - Dual to Single Node B Mode ............................................... 35
Proc 5: Dual NodeB Final Check ............................................................................ 40
Description .................................................................................................. 40
Preconditions ............................................................................................... 40
NSP GUI information Dual Node B configuration .................................................... 40
Dual Node B Final Check Procedure .................................................................... 41
Record Sheets / Checklists - On Site ....................................................................... 45
Report Sheet -Node B: Frequency Band ................................................................ 45
Report Sheet -Radio Module Equipment ............................................................... 45
Report Sheet -Inventories Equipment .................................................................. 46
Report Sheet -IP Parameters ............................................................................. 47
Report Sheet - 2NodeBs Parameters .................................................................... 48
Sign-Off Sheet .................................................................................................. 49
Description .................................................................................................. 49
Meaning of Sign-Off Sheet ................................................................................ 49
Sign-Off Sheet .............................................................................................. 49
Archiving of Reports ....................................................................................... 49
List of Figures

Figure 1: Single to Dual NodeB Migration in one d4U: Flow diagram ............................................. 9
Figure 2: Dual NodeB WCDMA in one d4U: Iub Backhaul and CPRI Link ........................................ 18
Figure 3: Dual NodeB WCDMA in one d4U: Modules Location .................................................... 19
Figure 4: WMS NSP GUI: Dual Node B mode information ....................................................... 40

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Dual Node B Commissioning Tests ......................... 5
Table 2: Applicable IEH 521 Sections for WCDMA Dual Node B Integration Tests .............................. 5

2 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Table 3: Applicable Methods Documents LR13.x for IEH521 ....................................................... 6

Table 4: Hardware Tools ................................................................................................. 7
Table 5: Software Tools .................................................................................................. 7
Table 6: Operational Procedures for Single to Dual Node B Migration ......................................... 10
Table 7: Sequence of Operations Used for Single to Dual Node B Migration .................................. 11
Table 8: Node B Parameters Required Prior to dual Node B Commissioning.................................. 12
Table 9: Node B BTS Parameters ..................................................................................... 13
Table 10: Node B RRH Parameters ................................................................................... 14
Table 11: Node B Backhaul Parameters ............................................................................. 14
Table 12: Node B Ethernet Parameters.............................................................................. 15
Table 13: Node B IP Parameters ...................................................................................... 15
Table 14: Node B 2NodeBsParameters ............................................................................ 16
Table 15: UMTS Frequency Band...................................................................................... 45
Table 16: Radio Module Equipment .................................................................................. 45
Table 17: Inventories Parameters .................................................................................... 46
Table 18: IP Parameters ................................................................................................ 47
Table 19: 2NodeBs Parameters ....................................................................................... 48
Table 20: Dual Node B Migration Checklists Customer Sign-off ............................................... 49

December 15, 2013 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

General

Section This section provides detailed information about the migration procedures from Single to Dual
Description Node B in the same d4U.
Preconditions
Inputs
Outputs
Additional details
Link to commissioning methods document where applicable

Previous Release New creation

Date

Release Notes New creation: December 2013 under utilization of existing IM documents for LR13.x.

4 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
Single to Dual Node B Migration procedures.

Documentation Access to applicable documents can be made under:

Access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required to perform the Single to Dual Node B
521 Sections Upgrade procedures.

Table 1: Applicable IEH 521 Sections for WCDMA Dual Node B

Commissioning Tests
Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
310 Node B Commissioning Testing
399 Node B Commissioning Test Records

Table 2: Applicable IEH 521 Sections for WCDMA Dual Node B

Integration Tests
Section Description
401 Integration Planning
402 Integration into existing UTRAN
410 Integration Testing
432 Hosting 2 Node Bs WCDMA in one d4U Procedures
499 Node B Integration Test Records

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

References, Continued

Applicable The following methods documents are required to perform the Single to dual Node B Upgrade
Documents in in LR13.x
LR13.x

Table 3: Applicable Methods Documents LR13.x for IEH521

Doc Number Doc Title URL
9YZ-04088- Alcatel-Lucent Node B http://cic.us.alcatel-
0095-RJZZA Commissioning Procedure lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=55054&prc=Unknown
9YZ-04088- Alcatel-Lucent Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault lucent.com/cgi-
Management User Manual: TIL bin/design2006/dbaccessprototyp
e1/01?key=55050&prc=Unknown
9YZ-04088- Alcatel-Lucent Node B Integration in http://cic.us.alcatel-
0098-RJZZA an existing UTRAN lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=55057&prc=Unknown
9YZ-04088- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
0014-PCZZA Management System User Guide lucent.com/cgi-
bin/design2006/dbaccessprototyp
e1/01?key=54991&prc=Unknown
9YZ-04088- Alcatel-Lucent 9353 Wireless http://cic.us.alcatel-
0015-TQZZA Management System - Security lucent.com/cgi-
Fundamentals bin/design2006/dbaccessprototyp
e1/01?key=54992&prc=Unknown
CMN/BTS/APP/ Standalone BBU WCDMA & https://infoproducts.alcatel-
037054 SUMX19" Model Offer Provisioning lucent.com/aces/cgi-
Guide bin/dbaccessfilename.cgi/CMNBT
SAPP037054LR13W_V1_

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

6 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Tools Requirements

General This section describes the hardware and software tools required to perform the single to dual
NodeB Upgrade Procedure.

Hardware Tool The hardware tools listed in the following table are required to perform the single to dual
NodeB Upgrade Procedure.

Table 4: Hardware Tools

Hardware Tool Quantity Description

Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

Software Tool The software tools listed in the following table are required to perform the single to dual
NodeB Upgrade Procedure.

Table 5: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with
WIN7)

December 15, 2013 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Single to Dual Node B Migration Flow

Purpose This map explains the flow of operations to migrate from single to dual Node B inside a d4U
shelf.

Applicable The d4U can be used in the following configuration cabinet :

Configuration
9100 Multi-standard Base Station Outdoor (MBO Ev2)
Cabinet
9100 Multi-standard Base Station Indoor (MBI Ev2)
9311 Macro V2 Node B Indoor
9311 Macro V1 Node B Outdoor
9311 Macro V2 Node B Outdoor
9941 Smart Base Station
9926 d4U in Standalone Configuration.

Continued on next page

8 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Single to Dual Node B Migration Flow, Continued

Single to Dual The flow diagram below outlines the steps for the single to dual Node B migration in the same
Node B d4U.
Migration flow
diagram
Figure 1: Single to Dual NodeB Migration in one d4U: Flow diagram

December 15, 2013 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Single to Dual Node B Migration Procedure

Overview

Reference of The following table lists all operational procedures of single to dual Node B migration.
Migration
Procedures
Mandatory Table 6: Operational Procedures for Single to Dual Node B Migration

Step Operation Opt/ Proc. Remark

Mand.
1 Single to Dual Node B M Proc. 1
Migration Preparation
2 Software Upgrade Procedure: O Proc. 2 If software load used is
for Dual Node B Mode not minimum LR13.1
3 Migration Procedure: Single M Proc. 3
to Dual Node B Mode
4 Downgrade Procedure: Dual O Proc. 4 If fallback required
to Single Node B Mode
5 Dual Node B Final Check M Proc. 5

10 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Single to Dual Node B Migration Checklists

Purpose Checklists are available to support and document the flow of operations before, during and post
single to dual node B migration in one d4U for
On site activities
Node B parameters
Remote (TIL) operations
and document successful completion of dual node B migration by customer acceptance

Checklist The checklists of IEH521 are generic and can be used as basis for further modifications and
Customization enhancements as per specific customer / market requirements.

Remote Sequence of operations for use by remote operations to verify success of mandatory and
Operations optional steps
Checklist

Table 7: Sequence of Operations Used for Single to Dual Node B Migration

Procedure Condition Expected result To OK NOK
use?
Proc 1: Single to Dual Node B Mandatory The preconditions of Node B #1
Migration Preparation in one d4U are fulfilled. Y/N
The field operations are selected.
Proc 2: Software Upgrade If software The minimum software load used
Procedure: for Dual Node B download required is LR13.1 Y/N
Mode in d4U

Proc 3: Migration Procedure: Mandatory The Node B #1 and Node B #2 in

Single to Dual Node B Mode the same d4U are configured in
dual Node B mode. Y/N
Both CCM (#A and #B) are
commissioned and integrated.
Proc 4: Downgrade If fallback required The Node B #1 only is configured
Procedure: Dual to Single in single Node B mode.
Node B Mode Y/N
Only CCM #A is commissioned
and integrated.
Proc 5: Dual Node B Final Mandatory The d4U operates in dual node B
Check mode and can be seen from Y/N
WMS

December 15, 2013 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Single to Dual Node B Form Parameters

General This section provides a number of forms to document the parameters necessary to perform the
(WCDMA-WCDMA) single to dual Node B migration of the Node B #1 and Node B #2 in the
same d4U.
The parameters are based on the CIQ must be documented by the coordinator according to the
expected parameters and configuration.
The form of parameters must be sent by email or available on a link.

Node B The following table is the list of dual Node B parameters required prior to commissioning the
Parameters d4U in Dual Node B (Node B #1 and Node B #2).
Required prior
to Dual Node B
Migration Table 8: Node B Parameters Required Prior to dual Node B
Commissioning
Node B parameter Value for Node B #1 Value for Node B #2
CCM #A CCM #B
Node B IP address
Configuration
Sub-network mask
Software upgrade on Node B: Yes / No Yes / No
Node B - Software version (LR13.1 minimum) (LR13.1 minimum)
Hardware reference
BTS Parameters: dBTS 4U-V3 dBTS 4U-V3

Continued on next page

12 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Single to Dual Node B Form Parameters, Continued

Node B BTS The following Node B BTS parameters are required prior to commissioning the d4U in Dual
Parameters Node B

Table 9: Node B BTS Parameters

Node B BTS parameters Value for Node B #1 Value for Node B #2
CCM #A CCM #B
BTS mode SingleMode SingleMode
(New parameter in LR13.1) SplitMode SplitMode
BTS Packaging (based on d4U) dBTS 4U-V3 dBTS 4U-V3
Fallback to previous I&C data Activate Activate
Deactivate Deactivate
GPS synchronization Activate Activate
Deactivate Deactivate
Ru Name:
Pec Code:
Serial Number:
Serialization Number of
Partner:
Manufacturing Date:

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Single to Dual Node B Form Parameters, Continued

Node B RRH The following Node B RRH parameters are required prior to commissioning the d4U in Dual
Parameters Node B

Table 10: Node B RRH Parameters

Node B RRH parameters Value for Node B #1 Value for Node B #2
CCM #A CCM #B
RRH Type CPRI(1,2,3)/HSSL(4,5,6) CPRI(1,2,3)/HSSL(4,5,6)
CPRI(1,2,3,4,5,6) CPRI(1,2,3,4,5,6)

Node B The following Node B Backhaul parameters are required prior to commissioning the d4U in
Backhaul Dual Node B
Parameters NOTE: hybrid Iub and Full IP backhaul only are allowed

Table 11: Node B Backhaul Parameters

Node B Backhaul Value for Node B #1 Value for Node B #2
parameters CCM #A CCM #B
Type of Incoming Link Fast Ethernet Fast Ethernet
Gigabit Ethernet Gigabit Ethernet

Continued on next page

14 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Single to Dual Node B Form Parameters, Continued

Node B The following Node B Ethernet parameters are required prior to commissioning the d4U in
Ethernet Dual Node B
Parameters Table 12: Node B Ethernet Parameters
Node B Ethernet Value for Node B #1 Value for Node B #2
parameters CCM #A CCM #B
VLAN ID 0 (Do not change) 0 (Do not change)
VLAN TAGGING Disabled Disabled
Enabled to use Enabled to use
LAG / HUBBING used (Do not change) (Do not change)
Eth Port used for iub IF (Do not change) (Do not change)
Eth Port used for Hubbing (Do not change) (Do not change)

Node B IP The following Node B IP parameters are required prior to commissioning the d4U in Dual
Parameters Node B.

Table 13: Node B IP Parameters

Node B IP parameters Value for Node B #1 Value for Node B #2

CCM #A CCM #B
Existence of a DHCP server No No
Yes Yes
BTS IP Address IP@: __.__.__.__ IP@: __.__.__.__
OMC-B IP Address IP@: __.__.__.__ IP@: __.__.__.__
OMC-B port 6301 6301
Sub-network mask 255.255.255.0 255.255.255.0
BTS port 6301 6301
Default Gateway Ip Address (Do not change the value) (Do not change the value)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Single to Dual Node B Form Parameters, Continued

2NodeBs The following Node B 2NodeBs parameters are required prior to commissioning the d4U in
Parameters Dual Node B.
NOTE: New parameters in LR13.1

Table 14: Node B 2NodeBsParameters

Node B 2NodeBs
parameters Value for Node B #1 Value for Node B #2
CCM #A CCM #B
Parameter name:
SerializationNumberOfPartner
Modem Slot Array: Assignment for NodeB#1 Assignment for NodeB#2
Physical Slot 1 (CEM #1) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 2 (CEM #2) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 3 (CEM #3) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 4 (CCM #B) NB#2
Physical Slot 5 (CCM #A) NB#1
Physical Slot 6 (CEM #4) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 7 (CEM #5) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 8 (CEM #6) Unassigned / Self /Partner Unassigned / Self /Partner

16 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 1: Single to Dual Node B Migration Preparation

Description This section describes the preparation before the migration from a single Node B to dual Node
B (WCDMA - WCDMA) inside one d4U.

Preconditions The following preconditions must be met

Only one Node B is already fully Integrated in one d4U (Single Mode).
The hosting 2 Node B WCDMA in one d4U feature is activated.
The software release is LR13.1 or higher to support the dual NodeB.
The laptop setting and TIL connections are already done and available.
The Serialization Number of Partner value must be available in the CIQ.

Naming
Conventions

IMPORTANT: Naming convention into the procedure:

NodeB 1 takes into account the CCM-U with naming CCM A and will support 3G only
NodeB 2 takes into account the CCM-U with naming CCM B and will support 3G or 4G

Dual Node B
basic
engineering
rules DO NOT: Do not use pure ATM backhaul.

DO NOT: Do not use xCCM-u controller in a dual Node B configuration.

Engineering rules to support the dual Node B configuration in d4U:

The modems eCEM-U and / or xCEM-U can be used.

The two eCCM-U controllers must be equipped with GigE MDA.
The two eCCM-U controllers will be hosting their own Iub backhaul termination.
The two eCCM-U controllers will be hosting their own CPRI interfaces towards the REs
(TRDU or RRH or MCTRX).
Hybrid Iub or full IP backhaul are allowed

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 1: Single to Dual Node B Migration

Preparation, Continued

Dual Node B
basic
engineering
rules (continued) Figure 2: Dual NodeB WCDMA in one d4U: Iub Backhaul and CPRI Link

Continued on next page

18 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 1: Single to Dual Node B Migration

Preparation, Continued

Modem Rules in
Dual Mode
Configuration in
d4U IMPORTANT: CCM-U #B cannot be used with software versions below
LR13.1W.

If Modem CEM is introduced... Then Modem CEM...

in UA8.1.3 (load UNB08D120C0) Unable to work with CCM #B
In LR13.1W Must be upgraded to LR13.1 load on CCM
#A before using CCM #B.

Figure 3: Dual NodeB WCDMA in one d4U: Modules Location

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 1: Single to Dual Node B Migration

Preparation, Continued

Upgrade Path Review available SW versions and decide whether a software upgrade needs to happen prior
Selection to performing the migration from Single to Dual Node B.
Procedure

Step Action
1 Review the available software version on the CCM-U and decide whether SW
upgrade is required.

If software in single Node B is Then perform

procedure ...
< LR13.1 load Proc 2: Software Upgrade
procedure

2 Review the available software version on the CCM-U and decide whether
Single to Dual Node B migration can be executed

If software in single Node B is Then perform

procedure ...
>= LR13.1 load Proc 3: Migration procedure
from Single to Dual Node B

20 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 2: Software Upgrade Procedure

Description This procedure describes the software upgrade to enable the migration from single to dual
Node B mode (WCDMA - WCDMA) inside one d4U.

Preconditions The following preconditions must be met

Only one Node B is already fully Integrated in one d4U (Single Mode).
The release software must be minimum UA8.x. before software download.
The hosting 2 Node B WCDMA in one d4U feature must be activated.
The laptop setting and TIL connections are already done and available.

Software The following procedure describes how to perform the software upgrade from UA08.1 as
Upgrade enabler for the single to dual Node B migration.
Procedure
NOTE: Software versions must be checked and potentially be upgraded for both CCM-Us:
CCM-U #A
CCM-U #B

Step Action
1 Verify that only one controller card (CCM-U #A) is in physical slot 5 and
works with a minimum 1 modem CEM.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 2: Software Upgrade Procedure, Continued

Software
Upgrade
Step Action
Procedure
(continued) 2 Verify that only one controller card (CCM-U #A) is in physical slot 5 and
works with a minimum 1 CEM up to 3 modems (CEM #1, #2, #3).

MOTE: CCM-U #A must be removed in this case

3 Connect TIL and verify the d4U Software reference version of the CCM-U
which is displayed at the bottom of the TIL GUI.

NOTE: The value must be UNB0813xxx maximum

Continued on next page

22 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 2: Software Upgrade Procedure, Continued

Software
Upgrade
Step Action
Procedure
(continued) 4 Download the required software (LR13.1 minimum) by use of IEH521-302
software download procedure
5 Activate the new software on the Node B by use of IEH521-302 software
activation procedure which includes a reboot of the Node B.
6 Verify the d4U Software reference version displayed at the bottom of the TIL
GUI.

NOTE: This value must be UNB0911xxx minimum. (Equivalent to LR13.1

SW load or higher software version.

December 15, 2013 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 3: Migration Procedure: Single to Dual NodeB

Mode

Description This procedure describes the migration from single to dual Node B mode (WCDMA - WCDMA)
inside one d4U.

Preconditions The following preconditions must be met

Only one Node B is already fully integrated in one d4U (Single Mode).
One controller CCM #A working with up to 6 modems (maximum).
The hosting 2 Node B WCDMA in one d4U feature must be activated.
Software version must be on LR13.1W or higher. Software upgrade procedure has been
performed if required to achieve this.
The laptop setting and TIL connections are already done and available.
The SiteLAN is connected to CCM #A
Alarm cable is daisy chained between both RUC (#1 and #2)
Cabinet and external alarm kit is connected to RUC # 2 if used.
The Serialization Number of Partner value must be available in the CIQ.

Parameters The following procedure describes how to perform the parameter configuration to set the first
Configuration controller (CCM #A) in dual mode
Procedure of
CCM #A
Step Action
1 Visually check all hardware in d4U for compliancy before migration start

NOTE: eCCM-U board is in slot 5 and a minimum of one CEM-U board is in

slot 6 to 8.
2 Connect the TIL on the controller CCM #A (Port #1)

Continued on next page

24 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Parameters
Configuration
Step Action
Procedure of
CCM #A 3 Set all dual Node B parameters according to the configuration required to
(continued) support the dual Node B in d4U

NOTE: IEH521-432 Hosting 2 Node Bs WCDMA in one d4U Procedures

details how to set first Node B into dual mode operation.

NOTE: A reboot will be performed during this procedure

4 Remove the TIL connection from the controller CCM #A (Port #1) after the
reboot occurred.
5 Pull CCM-U #A out that it is disconnected from the backplane of the d4U while
leave all connecting cables plugged in:

Leave Optical Fiber connected (up to 6 CPRI link for Radio module)
Leave Site LAN connected (Port 5 of MDA GE)
Leave Alarm Bus connected on the CCM#A side only
Disconnect Alarm Bus connector on the RUC #1
Leave PCM cable connected (if hybrid Iub used)
Leave GPS cable if used.

NOTE: The CCM #A must be disconnected from the backplane during the
CCM #B configuration to avoid the communication across the backplane. To
achieve this, it is recommended to pull the board about 2cm from the
backplane to avoid connector contact.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Parameters
Configuration
Step Action
Procedure of
CCM #A 7 Disconnect and remove the alarm cable (Dotted red in figure below) between
(continued) RUC #1 and RUC #2 of the d4U and remove Filler from slot 4.

NOTE: This alarm cable between both RUC is only used in single Mode.

NOTE: The first Controller CCM #A is now configured in Dual Mode (SplitMode) and
unconnected from d4U backplane.

Continued on next page

26 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Hardware The following procedure describes how to perform the addition of the second controller (CCM-
Migration U #B)
Procedure
adding CCM #B NOTE: Refer to the Standalone BBU WCDMA MOPG for new modules or cables to be used.

Step Action
1 Insert the second controller CCM #B into the empty slot 4
2 Move the external alarm cable from RUC #2 to RUC #1 (Red in figure below).

3 Connect alarm cable between CCM #B & RUC #2 (Red in figure below).

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Hardware
Migration
Step Action
Procedure
adding CCM #B 4 Connect all necessary interface cables to CCM-U #B
(continued) Optical Fiber (up to 6 CPRI link for Radio module)
PCM cable if hybrid Iub used.
GPS cable if used.

NOTE: Number of interface cables and type is dependent on engineering and

configuration

NOTE: The second Controller CCM #B is now installed and connected.

Continued on next page

28 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Parameters The following procedure describes how to perform the parameter configuration to set the
Configuration second controller (CCM #B) in dual mode
Procedure of
CCM #B
Step Action
1 Visually check all hardware in d4U for compliancy before migration start

2 Connect TIL to controller CCM #B (Port #1)

3 Perform commissioning of Node B #2 as described in IEH521-302
4 Set all dual Node B parameters according to the configuration required to
support the dual Node B in d4U:

SplitMode (to declare the controller in Dual NodeB Mode),

SerializationNumberOfPartner (refer to the CIQ to find this partner NEID
parameter)
Modem slot assignment for each modem CEM

NOTE: IEH521-432 Hosting 2 Node Bs WCDMA in one d4U Procedures

details how to set first Node B into dual mode operation.

NOTE: A reboot will be performed during this procedure

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Parameters
Configuration
Step Action
Procedure of
CCM #B 5 Connect the Site LAN cable on CCM #B (Port 5 of MDA GE)
(continued)

6 Perform integration of Node B #2 as described in IEH521- 402

NOTE: The second Controller CCM #B is now in Dual Mode (SplitMode)

Continued on next page

30 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Visual Check The following procedure describes how to enable Node B #1 for operational and to visually
Procedure for check the dual mode configuration of the d4U Node B
Dual Node B
configuration
Step Action
1 Insert CCM #A back into the d4U and connect alarm cable from CCM #A to
RUC #1

NOTE: All other cables are still connected to the CCM #A

NOTE: Now both controllers are in dual mode configuration and can
communicate across the backplane to pass and verify the consistency of
configuration information.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Visual Check
Procedure for
Step Action
Dual Node B
configuration 2 Connect TIL on CCM #A and verify modem assignment to Node B #1 by use
(continued) of TIL GUI

NOTE: The modem assignment must be consistent with the modem

assignment as configured and physically present in the d4U. Refer to IEH521-
432 Hosting 2 Node Bs WCDMA in one d4U Procedures for details of this
verification.

NOTE: If CCM-U #A validation is not consistent or displays in single mode call

for trouble shooting or execute Downgrade Procedure: Dual to Single
NodeB Mode

Continued on next page

32 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 3: Migration Procedure: Single to Dual NodeB

Mode, Continued

Visual Check
Procedure for
Step Action
Dual Node B
configuration 3 Connect TIL on CCM #B and verify modem assignment to Node B #2 by use
(continued) of TIL GUI

NOTE: The modem assignment must be consistent with the modem

assignment as configured and physically present in the d4U. Refer to IEH521-
432 Hosting 2 Node Bs WCDMA in one d4U Procedures for details of this
verification.

NOTE: If CCM-U #B validation is not consistent or displays in single mode call

for trouble shooting or execute Downgrade Procedure: Dual to Single
NodeB Mode

December 15, 2013 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 4: Downgrade Procedure: Dual to Single NodeB

Mode

Description This procedure describes the downgrade migration from dual to signle Node B mode
(WCDMA - WCDMA) inside one d4U.
NOTE: This procedure is only required in case of fallback or in case of Node B moving back to
single Node B operation.

Preconditions The following preconditions must be met

Both Node Bs are migrated from single to dual NodeB mode.
Both Node Bs are fully integrated in one d4U.
The hosting 2 Node B WCDMA in one d4U feature must be activated.
The minimum release software is LR13.1.
The laptop setting and TIL connections are already done and available.

Continued on next page

34 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 4: Downgrade Procedure: Dual to Single NodeB

Mode, Continued

Downgrade The following procedure describes how to perform the downgrade from Dual to Single Node B
Procedure - mode:
Dual to Single
Node B Mode
Step Action
1 Check before downgrade procedure that both controllers are there and work in
dual Node B mode with modems connected.

BTS_mode = SplitMode (for Dual NodeB)

The minimum software load is LR13.1

Check the minimum release software load at the bottom of the TIL GUI:

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 4: Downgrade Procedure: Dual to Single NodeB

Mode, Continued

Downgrade
Procedure -
Step Action
Dual to Single
Node B Mode 2 Lock the Cells of the Node B#2.
(continued) Lock the Node B#2.
Apply Reverse Workorder.

NOTE: OMC operations are required if Dual Node B is fully operational and
integrated before downgrade
3 Remove Alarm cable from CCM #B board to RUC #2 (red dotted line in figure
below)

4 Disconnect Optical Fiber connected (up to 6 CPRI link for Radio module)
Disconnect Site LAN connected (Port 5 of MDA GE)
Disconnect PCM cable connected (if hybrid Iub used)
Disconnect GPS cable if used.
on CCM #B

5 Remove CCM #B board from physical slot 4.

6 Replace CCM #B board by filler and secure it

Continued on next page

36 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 4: Downgrade Procedure: Dual to Single NodeB

Mode, Continued

Downgrade
Procedure -
Step Action
Dual to Single
Node B Mode 7 Connect Alarm cable (Red in figure below) between RUC #1 and RUC #2
(continued) D4U Single CCM (w/o eAM option)

8 Connect Alarm cable from eAM to RUC #2 (Red in figure below)

D4U Single CCM (with eAM option)

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 4: Downgrade Procedure: Dual to Single NodeB

Mode, Continued

Downgrade
Procedure -
Step Action
Dual to Single
Node B Mode 9 Leave siteLAN and all other connection on the controller CCM #A (port 5).
(continued)

10 Connect the TIL to CCM #A (Port 1)

11 Modify BTS_Mode parameter from Split Mode (Dual NodeB) to Single Mode
(Single Mode).

NOTE: Select from TIL I&C parameter screen tab BTS | BTS mode and
check for value SingleMode

Continued on next page

38 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 4: Downgrade Procedure: Dual to Single NodeB

Mode, Continued

Downgrade
Procedure -
Step Action
Dual to Single
Node B Mode 12 Validated for CCM #A in slot 5 is working with up to 6 modems and the BTS
(continued) mode is configured as SingleMode

NOTE: The d4U Node B is working in single Mode with CCM #A in slot 5.

If d4U Node B TIL GUI... Then ...

Shows the CCM #A in single mode Go to section 310 to finalize the
with their dedicated Modem. Node B commissioning testing.
(Maximum: CEM #4, #5, #6, #1,#2) Or/ and go to section 410 to finalize
the Node B Integration Testing.
Or Fill the Test Records
Does not show the CCM #A in Contact the support team to
single mode with their dedicated troubleshoot the issue.
Modem.

December 15, 2013 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 5: Dual NodeB Final Check

Description This procedure describes how to do a final check after migration in single or in dual Node B
mode (WCDMA - WCDMA) inside one d4U.

Preconditions The following preconditions must be met

Both Node B are migrated from single to dual NodeB mode.
Both Node B are fully integrated inside one d4U.
The hosting 2 Node B WCDMA in one d4U feature must be activated.
The minimum release software is LR13.1.

NSP GUI OMC operator can display data by Node B to identify and validate the dual Node B operation
information
Dual Node B
configuration Figure 4: WMS NSP GUI: Dual Node B mode information

Continued on next page

40 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 5: Dual NodeB Final Check, Continued

Dual Node B The following procedure describes how to perform the final checks of the dual Node B
Final Check configuration inside one d4U
Procedure NOTE: This procedure must be executed through access to WMS (OMC operator)
NOTE: NSP-GUI (WMS) shows the dual Node B on separate GUI
NOTE: The NSP-GUI does not display both Node B on the same d4U Rack on the GUI.

Step Action
1 Open the Object Editor of a NodeB on the d4U rack
2 Right click on the BTS equipment object
3 Select Open partner BTS Equipment Monitor listing on the tab.

NOTE: This option of Open partner BTS Equipment Monitor would not
appear on any other Rack type other than d4UV3.

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 5: Dual NodeB Final Check, Continued

Dual Node B
Final Check
Step Action
Procedure
(continued) 4 Open two different Equipment Monitors when opened through Open Partner
BTS Equipment Monitor menu to display both NodeBs in one NSP-GUI view

5 Verify for
One eCCM-U
Minimum of one and up to 5 CEM-U associated for the Node B #1 in the
correct slots above

NOTE: Use Modem slot assignment data for Node B #1 to compare

Continued on next page

42 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Proc 5: Dual NodeB Final Check, Continued

Dual Node B
Final Check
Step Action
Procedure
(continued) 6 Verify for
One eCCM-U
Minimum of one and up to 3 CEM-U associated for the Node B #2 in the
correct slots above
NOTE: Use Modem slot assignment data for Node B #2 to compare

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Proc 5: Dual NodeB Final Check, Continued

Dual Node B
Final Check
Step Action
Procedure
(continued) 7 Verify for each Node B that it is operational in Dual Node B operation mode
by selecting BTS Equipment I Configuration I Object Editor to check all
following parameters per Node B are consistent with local settings

Window is Then the value is...

Node B #1 NeID = NeID of Node B #1
BTSMode = Dual Mode
Modem Slot Array = 02, 02, 02, 00, 00, 01, 01, 01
NeID of Partner = NeID of Node B #2
Node B #2 NeID = NeID of Node B #2
BTSMode = Dual Mode
Modem Slot Array = 02, 02, 02, 00, 00, 01, 01, 01
NeID of Partner = NeID of Node B #1

NOTE: First byte of Modem Slot Array corresponds to physical slot 1

If modem slot Then modem is...

array byte is...
00 Unassigned
CCM (Controller) slot. (bytes 4 and 5)
01 Assigned to CCM #A
02 Assigned to CCM #B

NOTE: Modem Slot Array parameter is not used if BTSmode is in single

Mode (default value)

NOTE: The d4U Node B is operational in dual Node B mode.

44 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Record Sheets / Checklists - On Site

Report Sheet - Select the UMTS Frequency Band used by the Node B.
Node B:
Frequency
Band Table 15: UMTS Frequency Band
UMTS Frequency (Band)
850Mhz 900Mhz 1900Mhz AWS 2100Mhz
(Band V) (Band VIII) (Band II) (Band IV) (Band I)

Report Sheet - Select the Radio Module Equipment used.

Radio Module
Equipment
Table 16: Radio Module Equipment
Radio Module Indoor Radio Module Outdoor
TRDU RRH40w
MC TRDU RRH60w
MC TRX RRH2x40
RRH2x60

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Record Sheets / Checklists - On Site, Continued

Report Sheet - Fill the Inventories parameters used.

Inventories
Equipment
Table 17: Inventories Parameters
Parameters Node B #1 Value Node B #2 Value
for CCM #A for CCM #B
Current Network Release (UNB)
(LR13.1 minimum required)
Software upgrade on Node B: Yes / No Yes / No
NeID (Serial Number) (6 digits) __ __ __ __ __ __ __ __ __ __ __ __
NeID Partner (Serial Number Partner) __ __ __ __ __ __ __ __ __ __ __ __
Modem Slot Array: __.__.__.00.00__.__.__
User Label
RU Name (30 characters max.)
PEC code (16 characters max.)
Manufacturing date (4 characters max.) __ __ __ __ __ __ __ __
Hardware reference
BTS Parameters: (BTS Packaging) dBTS 4U-V3 dBTS 4U-V3
BTS mode SingleMode SingleMode
SplitMode SplitMode

Continued on next page

46 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Record Sheets / Checklists - On Site, Continued

Report Sheet - Fill the IP Parameters if DHCP is not used:

IP Parameters

Table 18: IP Parameters

IP Parameters Node B #1 Value Node B #2 Value
for CCM #A for CCM #B
DHCP server used? (Default value) --> (Default value) -->
Yes / No Yes / No
Node B IP address ___.___.___.___ ___.___.___.___
OMC-B IP address ___.___.___.___ ___.___.___.___
Sub-Network Mask ___.___.___.___ ___.___.___.___

Continued on next page

December 15, 2013 Alcatel-Lucent Internal 47

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

Record Sheets / Checklists - On Site, Continued

Report Sheet - Fill the 2NodeBs parameters used.

2NodeBs
Table 19: 2NodeBs Parameters
Parameters
Node B 2NodeBs
parameters Value for Node B #1 Value for Node B #2
CCM #A CCM #B
Parameter name:
SerializationNumberOfPartner
Modem Slot Array: Assignment for NodeB#1 Assignment for NodeB#2
Physical Slot 1 (CEM #1) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 2 (CEM #2) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 3 (CEM #3) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 4 (CCM #B) NB#2
Physical Slot 5 (CCM #A) NB#1
Physical Slot 6 (CEM #4) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 7 (CEM #5) Unassigned / Self /Partner Unassigned / Self /Partner
Physical Slot 8 (CEM #6) Unassigned / Self /Partner Unassigned / Self /Partner

Additional comments/remarks:

48 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
Single to Dual Node B Migration Procedures IEH 521, Section 705

Sign-Off Sheet

Description Sign-Off sheet has to be completed to finally document acceptance of the single to dual Node
B migration results in the same d4U.

Meaning of Sign- Completion of the Sign-Off sheet represents the finalization of the single to dual Node B
Off Sheet migration activity and is meant to serve for customer acceptance of the Node B migration.

Sign-Off Sheet Sign off sheet for successful migration of the single Node B to dual Node B in d4U.
The following sign-off confirms that all required checklists proof successful migration of the
single to dual Node B in the same d4U.

Table 20: Dual Node B Migration Checklists Customer Sign-off

Commissioner Coordinator / Customer
engineer on-Site Representative
activities
Company Name

Function
Name

Signature

Date

Archiving of All reporting sheets for an individual Node B commissioning must be archived.
Reports All reporting sheets must be available to be reused if necessary during the integration section.
Individual contractual agreements with customer may require the original to hand over to the
customer for archiving.

December 15, 2013 Alcatel-Lucent Internal 49

Proprietary Use pursuant to Company instruction
IEH 521, Section 705 Single to Dual Node B Migration Procedures

This page intentionally left blank.

50 Alcatel-Lucent Internal December 15, 2013

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Section 706

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Node B Daisy Chaining through the Node B - Activation Procedure

Table of Contents

General ............................................................................................................ 4
Section Description .......................................................................................... 4
Previous Release Date ....................................................................................... 4
Release Notes ................................................................................................. 4
References ........................................................................................................ 5
General ........................................................................................................ 5
Documentation access ...................................................................................... 5
Applicable IEH 521 sections for WCDMA Node B commissioning ..................................... 5
Applicable IEH 521 sections for WCDMA Node B Integration ......................................... 5
Applicable Methods documents in LR13.1 ............................................................... 6
Tools Requirements ............................................................................................. 7
General ........................................................................................................ 7
Hardware Tool ................................................................................................ 7
Software Tool ................................................................................................. 7
NodeB Daisy Chaining through the Node B - Feature Description ....................................... 8
Description .................................................................................................... 8
Feature benefits .............................................................................................. 8
Node B Daisy Chaining Basic Engineering Rules ....................................................... 9
NodeB Daisy Chaining Configuration Network Architecture ...................................... 11
NodeB Daisy Chaining Configuration 3G Node B 3G Node B ..................................... 11
NodeB Daisy Chaining Configuration 3G Node B 2G Node B ..................................... 12
NodeB Daisy Chaining Configuration 3G Node B 4G Node B ..................................... 13
Configuration of Node B Daisy Chaining 3G NodeB - 3G or 4G NodeB........................... 14
Node B 3G Chaining with a BTS 2G Configuration - Description. .................................. 16
Node B Daisy Chaining SynchronizationConfiguration Requirements ........................... 18
NodeB Daisy Chaining Port Configuration Guide .................................................... 19
NodeB Daisy Chaining Port Configuration Principles ............................................... 21
NodeB Daisy Chaining Port Configuration and Node B daisy chaining activation flow ....... 22
Proc. 1: Node B (A) Daisy Chaining Commissioning - TIL ............................................... 25
Description .................................................................................................. 25
Preconditions ............................................................................................... 25
NodeB (A) 3G Daisy Chaining Commissioning Procedure ............................................ 25

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 2: Node B (B) Daisy Chained Commissioning - TIL ................................................ 28

Description .................................................................................................. 28
Preconditions ............................................................................................... 28
Commissioning of Daisy Chained Node B ............................................................... 28
Node B (B) 3G Daisy Chained Commissioning Procedure ............................................ 29
Proc. 3: Node B (A) Daisy Chaining Pre-Check before Activation - WMS ............................ 32
Description .................................................................................................. 32
Preconditions ............................................................................................... 32
Ethernet Port Definitions ................................................................................. 32
NodeB (A) Daisy Chaining Pre-check before Activation Procedure ................................ 33
Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0 Configuration Procedure - WMS ............. 35
Description .................................................................................................. 35
Preconditions ............................................................................................... 35
Step of actions .............................................................................................. 35
Lock the Ethernet Port/0 Procedure - WMS/NSP ..................................................... 36
Ethernet Port/0 Configuration Procedure - WMS/NSP ............................................... 39
Unlock the Ethernet Port/0 Procedure - WMS/NSP .................................................. 42
Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1 Configuration Procedure - WMS ............. 44
Description .................................................................................................. 44
Preconditions ............................................................................................... 44
Step of actions .............................................................................................. 44
Lock the Ethernet Port/1 Procedure - WMS/NSP ..................................................... 45
Ethernet Port/1 Configuration Procedure - WMS/NSP ............................................... 48
Unlock the Ethernet Port/1 Procedure - WMS/NSP .................................................. 51
Proc. 6: Node B (A) Daisy Chaining IPRan Parameter Configuration Procedure - WMS ............ 53
Description .................................................................................................. 53
Preconditions ............................................................................................... 53
IPRan Parameter Configuration on Node B Daisy Chaining Procedure ............................ 54
Proc. 7: Node B (A) Daisy Chaining Validation ........................................................... 58
Description .................................................................................................. 58
Preconditions ............................................................................................... 58
Node B (A) Daisy Chaining Visual Check ................................................................ 58
Node B (A) Daisy Chaining Visual Check Procedure with TIL GUI .................................. 60
IP Ping test of all Node B (A) Daisy Chaining .......................................................... 63
Proc. 8: Node B (B) Daisy Chained Validation ............................................................ 64
Description .................................................................................................. 64
Preconditions ............................................................................................... 64
Node B (B) Daisy Chained Visual Check Procedure TIL GUI ....................................... 65
IP Ping test of all Node B (B) Daisy Chained ........................................................... 67

List of Figures

Figure 1: 3G Node B (A) Dropping 3G NodeB (B) ................................................................... 11

Figure 2: 3G Node B (A) Dropping 2G BTS (B) ...................................................................... 12
Figure 3: 3G Node B (A) Dropping 4G eNode B (B) ................................................................. 13
Figure 4: Node B (A) 3G Chaining Node B (3G) or eNodeB 4G Configuration. ................................ 14
Figure 5: Node B (A) 3G Chaining a BTS (B) 2G Configuration ................................................... 16
Figure 6: Node B (A) 3G Chaining a BTS (B) 2G Interconnection Description ................................. 17
Figure 7: Node B Daisy Chaining through the Node B flow of activities ..................................... 24

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

List of Tables

Table 1: Applicable IEH 521 Sections for WCDMA Node B Commissioning ....................................... 5
Table 2: Applicable IEH 521 Sections for WCDMA Node B Integration ........................................... 5
Table 3: Applicable Methods Documents LR13.1 for IEH521 ....................................................... 6
Table 4: Hardware Tools ................................................................................................. 7
Table 5: Software Tools .................................................................................................. 7
Table 6: Basic Engineering Rules for Node B daisy chaining ....................................................... 9
Table 7: 3G Node B (A) Supported Configurations if SyncE source is NOT used in Daisy Chaining ........ 18
Table 8: 3G Node B (A) Supported Configurations if SyncE source IS used in Daisy Chaining .............. 19
Table 9: GE MDA Ethernet Port Configuration Guide ............................................................. 20
Table 10: Visual Check of GE MDA Ethernet Port Status ......................................................... 59

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

General

Section This section provides detailed information about the individual procedures to introduce and
Description activate the Daisy Chaining of a WCDMA Node B:
Preconditions
Inputs
Outputs
Additional details

NOTE: The configuration and activation of the Node B daisy chaining is regarded as migration
from a regularly integrated Node B without daisy chaining.

Previous Release New creation

Date

Release Notes New creation: June 2014 under utilization of existing Installation Methods and user guides
documents for LR13.1.

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

References

General This section utilizes ALU Product Documents as well as handbook 521 sections to perform the
migration procedures of the WCDMA NodeB to activate Node B daisy chaining.

Documentation Access to applicable documents can be made under:

access https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

Applicable IEH The sections listed in Table 1 below are required

521 sections for
WCDMA Node B
commissioning Table 1: Applicable IEH 521 Sections for WCDMA Node B
Commissioning

Section Description
301 Node B Commissioning Planning
302 Node B Commissioning Procedure
399 Node B Commissioning Test Records

Applicable IEH The sections listed in Table 2 below are required for WCDMA Node B Integration tests.
521 sections for
WCDMA Node B
Integration Table 2: Applicable IEH 521 Sections for WCDMA Node B Integration
Section Description
401 Node B Integration Planning
402 Node B Integration Procedure
413 Node B Daisy Chain Remote Checking Procedure Telnet Commands
499 Node B Integration Test Records

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

References, Continued

Applicable The following methods documents are required to perform the Node B commissioning in
Methods LR13.1
documents in
LR13.1
Table 3: Applicable Methods Documents LR13.1 for IEH521

Doc Number Doc Title URL

9YZ-04088- Alcatel-Lucent 9100 and 93xx Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault Management User lucent.com/pdfdocs14/pr
Manual: TIL (LR13.1) istore215/529074.pdf
9YZ-05870- Alcatel-Lucent 9100 and 93xx Node B http://cic.us.alcatel-
0090-PCZZA Commissioning and Fault Management User lucent.com/pdfdocs14/pr
Manual: TIL (LR13.3) istore215/541291.pdf
9YZ-04088- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.1) lucent.com/pdfdocs14/pr
istore215/562268.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0014-PCZZA System - User Guide (LR13.3) lucent.com/pdfdocs14/pr
istore215/586415.pdf
9YZ-05870- Alcatel-Lucent 9353 Wireless Management http://cic.us.alcatel-
0060-UFZZA System - Node B Alarms Reference Guide lucent.com/pdfdocs14/pr
(LR13.3) istore215/536534.pdf

NOTE: The documents can be fetched from the GPEC portal website: https://all1.na.alcatel-
lucent.com/Teams/GCDNetworks/WirelessGPEC/DeliveryReadiness/WCDMA/UTRAN/Docum
ents/index.html

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Tools Requirements

General This section describes the hardware and software tools required to perform the commissioning
method.

Hardware Tool The hardware tools listed in the following table are required to perform the feature
configuration and activation

Table 4: Hardware Tools

Hardware Tool Quantity Description
Keys to open the Node B 1 set If necessary
Laptop PC with Ethernet 1 For TIL GUI visualization and modification
interface RJ45
RJ45 straight wiring cable 1 For connection between the Laptop and the
CCM-U board.

If operation Then RJ45 cable

is ... will be
connected to...
remote the IP Backhaul
Network
local (On field) the CCM-U Board

Software Tool The software tool listed in the following table are required to perform the feature configuration
and activation

Table 5: Software Tools

Software Tool Version Allowed
OS WIN XP or WIN 7
Web Browser Internet Explorer (5.5 or 6.0), Mozilla Firefox
Java Run Type Environment JRE 1.4.2 Minimum (and JRE 6 Maximum with WIN
7)

June 30, 2014 Alcatel-Lucent Internal 7

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description

Description This section describes the Node B Daisy Chaining feature through the WCDMA Node B and
how it operates.

Feature benefits This feature allows using a single Ethernet backhaul interface for sites with multiple base
stations 2G/3G/4G and allows to avoid using an external Ethernet aggregator

Continued on next page

8 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

Node B Daisy The following basic engineering rules must be met for planning, configuration and activation of
Chaining Basic the Node B daisy chaining feature.
Engineering
Rules
Table 6: Basic Engineering Rules for Node B daisy chaining

Topics Principe engineering rules

Port configuration Daisy chaining can be activated ONLY in Native IP Iub
configuration & when the backhaul interface is GE MDA.
Only 2 out of 3 GE MDA ports can be used since GE MDA
SFP2 and GE MDA RJ45 CANNOT be used simultaneously.
(mutually exclusive)
The 3 physical ports: SFP1, SFP2 & RJ45 of the GE MDA can
be used.
SFP1 and SFP2 can have either:
Fiber (optical) transceiver or
Copper (electrical) transceiver.
The configuration is limited to 1 GE link for backhaul, connected to
a common packet backhaul, and one GE link connecting a
dropped 3G or 4G BTS
Synchronization SyncE is supported w/ Node B daisy chaining feature in
ingress (Mobile BackHaul - MBH) and egress (Daisy Chain -
DC) ports.
The Node B itself does NOT modify the transparent clock
correction field and CANNOT act as a transparent clock in Daisy
Chaining mode
SyncE can only be propagated on optical SFP and GE MDA
RJ45 (electrical).
SyncE CANNOT be used as synchronization source if electrical
SFP1 or electrical SFP2 is used.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 9

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

Node B Daisy
Chaining Basic
Topics Principe engineering rules
Engineering
Rules Supported Node B Daisy Chaining mode is only validated with ALU
(continued) Equipment 2G/3G/4G products.
Support of different (e.g. 3rd party) products requires additional
testing (IOT).

NOTE: Testing of different products is to be covered by customer

project.

Node B Daisy Chaining only supported configurations are:

3G->3G,
3G->2G
3G->4G-IPv4,
3G->4G-IPv6,
3G->4G-IPv4-IPSEC

Features Daisy chaining cannot be deployed jointly with:

incompatibility Dual port configuration (i.e. Split Iub) (feature 79362)
Link Aggregation (LAG - feature 112412)
IEEE803.3ah (Ethernet First Mile - EFM) introduced in the Node B
with feature 103182 - Ethernet OAM in the Node B
Fault Management In case of 3G Node B failure or reset of the Node B under daisy
chaining the daisy chained traffic will be interrupted.

NOTE: Daisy chaining feature is subject to licensing. It is not activated by default.

NOTE: Node B Daisy Chain activation does not require any NodeB reset.

NOTE: To activate the feature, the operator must first get the license, then set the flag IpRan:
isBackhaulDaisyChainingActivated = TRUE.

Continued on next page

10 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

NodeB Daisy The following section describes the network architecture view with Node B Daisy Chaining in
Chaining operation:
Configuration 3G Node B (daisy chaining) 3G Node B
Network
3G Node B (daisy chaining) 2G Node B
Architecture
3G Node B (daisy chaining) 4G Node B

NOTE: The recommendation is that the backhaul is connected via the optical on SFP GE link,
and the dropped BTS is connected using either Optical on SFP or Electrical GE link on RJ 45

NodeB Daisy
Chaining Figure 1: 3G Node B (A) Dropping 3G NodeB (B)
Configuration
3G Node B 3G
Node B

NOTE: The chained 3G Node B (B) is unaware of the daisy chaining

3G NodeB (A) and (B) are handled by the same OMC and RNC.
No specific provisioning is needed for 3G NodeB (B), apart from the addressing schema which
has to be compatible with NodeB (A)s one.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 11

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

NodeB Daisy
Chaining Figure 2: 3G Node B (A) Dropping 2G BTS (B)
Configuration
3G Node B 2G
Node B

NOTE: The chained 2G BTS (B) is unaware of the daisy chaining.

No traffic limitation is expected in this case.
The 2G BTS has to be configured with Abis over IP/Ethernet.

Continued on next page

12 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

NodeB Daisy
Chaining Figure 3: 3G Node B (A) Dropping 4G eNode B (B)
Configuration
3G Node B 4G
Node B

NOTE: The chained 4G eNode B (B) is unaware of the daisy chaining.

The main drawback being that the overall throughput of the backhaul (MBH) is limited to 1Gb/s,
to be shared between 3G Node B and a LTE eNode B.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 13

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

Configuration The following information explains the principle configuration rules for Node B daisy chaining
of Node B of 3G Node B (A) with 3G Node B (B) or 4G Node B (B)
Daisy Chaining
3G NodeB - 3G
or 4G NodeB NOTE: The chaining BTS is MANDATORY a 3G Node B.

Hardware configuration / cabling

Figure 4: Node B (A) 3G Chaining Node B (3G) or eNodeB 4G

Configuration.

Continued on next page

14 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

Configuration of
Node B Daisy
Port configuration of Node B (A)
Chaining 3G
When the Node B daisy chaining is active, each Ethernet port of the chaining Node B (A) is
NodeB - 3G or
assigned to just one role:
4G NodeB
(continued) Daisy Chained port (DC): is reserved for the connection with the chained BTS(s)
Mobile Backhaul port (MBH): is used for the connection with the MBH (RNC, OMC, BSC,
MME)

Port configuration of Node B (B)

The chained 3G or 4G BTS (B) are unaware of the daisy chaining no specific configuration is
necessary on this BTS (B) side.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 15

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

Node B 3G The following section describes the Node B 3G (A) Chaining a BTS 2G (B) Configuration
Chaining with a
BTS 2G
Configuration - NOTE: The chaining BTS is MANDATORY a 3G Node B
Description.
Hardware configuration / cabling

Figure 5: Node B (A) 3G Chaining a BTS (B) 2G Configuration

NOTE: In use case of 2G distributed BTS (B) in daisy chained configuration the IP backhaul
will be connected on the SUMxs TRANS1 Connector.

Continued on next page

16 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

Node B 3G
Chaining with a
BTS 2G
Figure 6: Node B (A) 3G Chaining a BTS (B) 2G Interconnection
Configuration - Description
Description.
(continued)

The Ethernet IP backhaul will be connected only to MDA SFP1 from the 3G Node B. (as GE
MDA SFP2 and GE MDA RJ45 CANNOT be used simultaneously. (mutually exclusive))
The Ethernet IP connection between the Node B 3G and BTS 2G will be done by Electrical
cable (with RJ45 connectors) connected respectively between MDA RJ45 and TRANS1.

Port configuration of Node B (A)

When the Node B daisy chaining is active, each Ethernet port of the chaining Node B (A) is
assigned to just one role:
Daisy Chained port (DC): is reserved for the connection with the chained BTS(s)
Mobile Backhaul port (MBH): is used for the connection with the MBH (RNC, OMC, BSC,
MME)

Port configuration of Node B (B)

As the chained 2G BTS (B) is unaware of the daisy chaining no specific configuration is
necessary on the 2G BTS side.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 17

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

Node B Daisy Basic configuration rules for synchronization apply

Chaining
Synchronization
Configuration NOTE: SyncE can only be propagated on optical SFP and GE MDA RJ45 (electrical). If
Requirements electrical SFP1 or elecrical SFP2 is used, then SyncE CANNOT be used as synchronization
source.

Table 7: 3G Node B (A) Supported Configurations if SyncE source is

NOT used in Daisy Chaining

Continued on next page

18 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

Node B Daisy
Chaining
Synchronization
Table 8: 3G Node B (A) Supported Configurations if SyncE source IS
Configuration used in Daisy Chaining
Requirements
(continued)

NodeB Daisy The following table provides an overview on the possible port configurations of Node B (A) and
Chaining Port Node B (B) when using Node B daisy chaining.
Configuration
Guide
Continued on next page

June 30, 2014 Alcatel-Lucent Internal 19

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

NodeB Daisy
Chaining Port Table 9: GE MDA Ethernet Port Configuration Guide
Configuration
If GE MDA Ethernet Port Then Configure the following Ethernet
Guide
(continued) Configuration of port of each NodeB...
Chaining Node B is... Ethernet
Ethernet Port/0
Node B Port/1
Node B (A): for Dropping /Chaining MBH Port
Node B (B): for Dropped /Chained DC Port

(B) MDA SFP1 (3G/4G) n.a.

MDA RJ45 or
(A) MDA SFP1
MDA SFP2

(B) MDA SFP2 (3G/4G) n.a.

MDA RJ45 or
(A) MDA SFP1
MDA SFP2

(B) MDA RJ45 (3G/4G) n.a.

MDA RJ45 or
(A) MDA SFP1
MDA SFP2

(B) MDA SFP1 (3G/4G) n.a.

MDA RJ45 or
(A) MDA SFP1
MDA SFP2

(B) MDA SFP2 (3G/4G) n.a.

MDA RJ45 or
(A) MDA SFP1
MDA SFP2
MDA RJ45 (3G/4G)
or
(B) n.a.
TRANS1 (2G
SUMx)
MDA RJ45 or
(A) MDA SFP1
MDA SFP2

Continued on next page

20 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

NodeB Daisy
Chaining Port NOTE: The Ethernet Port /0 (MBH) port on the Node B (A) is configured from TIL GUI and
Configuration WMS/NSP GUI.
Guide NOTE: The Ethernet Port /1 (DC) port on the Node B (A) is configured from WMS/NSP GUI.
(continued)
NOTE: The Ethernet Port /0 (MBH) port on the Node B (B) is checked from TIL GUI (in 3G
only).

NodeB Daisy The following information describes the principles how to configure the Node B ports if Node B
Chaining Port daisy chaining is used.
Configuration
Principles
Port parameters:
Model and parameters to configure Node B ports and activate for Node B daisy chaining

NOTE: Parameters Class 2: the object instance (or the parent object instance) must be locked
to modify the parameter and the modification will be taken into account after the object instance
(or the parent object instance) has been unlocked.

NOTE: Parameters Class 3: the parameter can be changed on-line without impact on the
service. The new value is taken into account either immediately or for new calls only. This class
3 indicates that the operator is able to activate or deactivate The node B daisy chaining feature
without restarting the Node B.
NOTE: When IsBackhauldaisyChainingActivated flag is TRUE (daisy chained activated), the
port role CANNOT be modified from DaisyChaining to Backhaul

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 21

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

NodeB Daisy
Chaining Port
Configuration
Principles NOTE: The Ethernet Port /0 (MBH) port on the Node B (A) is configured from TIL GUI and
(continued) WMS/NSP GUI.
NOTE: The Ethernet Port /1 (DC) port on the Node B (A) is configured from WMS/NSP GUI.
NOTE: The Ethernet Port /0 (MBH) port on the Node B (B) is checked from TIL GUI (in 3G
only).

NodeB Daisy The following information describes the flow of activities how to configure the Node B ports if
Chaining Port Node B daisy chaining is used.
Configuration
and Node B
daisy chaining NOTE: The Ethernet Port /0 (MBH) port on the Node B (A) is configured from TIL GUI or
WMS/NSP GUI.
activation flow
NOTE: The Ethernet Port /1 (DC) port on the Node B (A) is configured from WMS/NSP GUI.
NOTE: The Ethernet Port /0 (MBH) port on the Node B (B) is checked from TIL GUI (in 3G
only).

Continued on next page

22 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

NodeB Daisy
Chaining Port
Configuration If Ethernet Port Configuration of Then Configure the Ethernet Port
and Node B Node B in Daisy Chain is... through...
daisy chaining
activation flow The Ethernet Port /0, The standard commissioning procedure for
3G Node B:
(continued) (MBH) port on Node B (A)
Proc.1: Node B(A) Daisy Chaining
Commissioning TIL
Proc.3: Node B(A) Daisy Chaining Pre-
check before Activation WMS
Proc.4: Node B(A) Daisy Chaining Ethernet
Port/0 Configuration Procedure WMS
Proc.6: Node B (A) Daisy Chaining IPRan
Parameter Configuration Procedure WMS
Proc.7: Node B(A) Daisy Chaining
Validation
The Ethernet Port /1, The WMS/NSP GUI:
(DC) port on Node B (A) Proc.1: Node B(A) Daisy Chaining
Commissioning TIL
Proc.3: Node B(A) Daisy Chaining Pre-
check before Activation WMS
Proc.4: Node B(A) Daisy Chaining Ethernet
Port/1 Configuration Procedure WMS
Proc.6: Node B (A) Daisy Chaining IPRan
Parameter Configuration Procedure WMS
Proc.7: Node B(A) Daisy Chaining
Validation
The Ethernet Port /0, The standard commissioning procedure for
(MBH) port on Node B (B) 3G Node B / 4G eNode B
Proc.2: Node B(B) Daisy Chained
Commissioning TIL
Proc.8: Node B(B) Daisy Chained
Validation

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 23

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

NodeB Daisy Chaining through the Node B - Feature

Description, Continued

NodeB Daisy
Chaining Port
Configuration
Figure 7: Node B Daisy Chaining through the Node B flow of activities
and Node B
daisy chaining
activation flow
(continued)

24 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 1: Node B (A) Daisy Chaining Commissioning -

TIL

Description This procedure describes how to configure the parameters of the Node B (A) for daisy
chaining

Preconditions The Node B (A) must be integrated in an existing network in LR13.1 or higher.
The minimum release software must be LR13.1.
The Node B synchronization Enhancements feature must be activated.
The VLAN Tagging is enabled on each side (Node B 3G / eNodeB 4G / BTS 2G)
The Native IP Iub configuration is used.
The GE MDA is required on xCCM (-U) or eCCM-U for Sync E /PTP.
The eCCM-U is required for analog 2.048/10/15 MHz synchronization source.
The laptop setting and TIL connections are already done and available.

NodeB (A) 3G This procedure describes how to configure the GE MDA port of the 3G Node B for daisy
Daisy Chaining chaining (Node B (A))
Commissioning
Procedure
NOTE: The Ethernet Port /0 (MBH) port on the Node B (A) is configured from TIL GUI.

Step Action
1 Perform procedure TIL Connection on the Node B (A) (Dropping /Chaining)
following IEH 521 section 302.
2 Select I&C menu from TIL GUI

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 25

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 1: Node B (A) Daisy Chaining Commissioning -

TIL, Continued

NodeB (A) 3G
Daisy Chaining
Step Action
Commissioning
Procedure 3 Select I&C | Change I&C parameters | Backhaul and select Gigabit
(continued) Ethernet if not already done

4 Select I&C | Change I&C parameters | Ethernet

Continued on next page

26 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 1: Node B (A) Daisy Chaining Commissioning -

TIL, Continued

NodeB (A) 3G
Daisy Chaining
Step Action
Commissioning
Procedure 5 Select the correct configuration from the Eth Port used for Iub IF drop down
(continued) menu using Table9: GE MDA Ethernet Port Configuration Guide to select the
backhaul link on Ethernet Port/0 of Node B (A).

Options:

6 Perform procedure Sending I&C Parameters to the Node B from IEH 521
section 302.
7 Perform procedure Node B reset in Connected Mode from IEH 521 section
302.

NOTE: The backhaul link is now configured on the Ethernet Port/0 of Node B (A) as required
for the daisy chaining configuration.

June 30, 2014 Alcatel-Lucent Internal 27

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 2: Node B (B) Daisy Chained Commissioning -

TIL

Description This procedure describes how to configure the daisy chaining port of the Node B (B) for Daisy
Chaining

Preconditions The Node B (B) must be integrated in an existing network in LR13.1 or higher.
The minimum release software must be LR13.1.
The Node B synchronization Enhancements feature must be activated.
The VLAN Tagging is enable on each side (Node B 3G / eNodeB 4G / BTS 2G)
The Native IP Iub configuration mandatory used.
The GE MDA is required on xCCM (-U) or eCCM-U for Sync E /PTP.
The eCCM-U is required for analog 2.048/10/15 MHz synchronization source.
The laptop setting and TIL connections are already done and available.

Commissioning The daisy chained Node B (Node B (B)) must be commissioned by performing the standard
of Daisy Chained commissioning procedure for the Node B (B) daisy chained to configure the correct Node B
Node B port for use in Node B daisy chaining configuration (see Table 8 as guideline).

Continued on next page

28 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 2: Node B (B) Daisy Chained Commissioning -

TIL, Continued

Node B (B) 3G This procedure describes how to configure the GE MDA port of the 3G Chained/Dropped
Daisy Chained Node B (B).
Commissioning
Procedure
NOTE: The Ethernet Port /0 (MBH) port on the Node B (B) is checked from TIL GUI (in 3G
only).

Step Action
1 Perform procedure TIL Connection on the Node B (B) (Dropped /Chained)
following IEH 521 section 302 and configure the Node B (B) port for normal
operation
2 Go to I&C menu from TIL GUI

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 29

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 2: Node B (B) Daisy Chained Commissioning -

TIL, Continued

Node B (B) 3G
Daisy Chained
Step Action
Commissioning
Procedure 3 Select I&C | Change I&C parameters | Backhaul
(continued)

Select Gigabit Ethernet if not already done

4 Select I&C | Change I&C parameters | Ethernet

Continued on next page

30 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 2: Node B (B) Daisy Chained Commissioning -

TIL, Continued

Node B (B) 3G
Daisy Chained
Step Action
Commissioning
Procedure 5 Select the Eth Port used for Iub IF parameter according to the Iub
(continued) configuration and the previous Table9: GE MDA Ethernet Port Configuration
Guide to select the backhaul link on Ethernet Port/0 of Node B (B)..

MDA RJ45 or
MDA SFP1 or
MDA SFP2

6 Perform procedure Sending I&C Parameters to the Node B from IEH 521
section 302.
7 Perform procedure Node B reset in Connected Mode from IEH 521 section
302.

NOTE: The backhaul link is now configured on the Ethernet Port/0 of Node B (B) according to
expected daisy chaining network

June 30, 2014 Alcatel-Lucent Internal 31

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 3: Node B (A) Daisy Chaining Pre-Check

before Activation - WMS

Description This procedure describes how to pre-check Ethernet Port parameters before activation of
Node B (A) Daisy Chaining of Node B (A).

Preconditions The operator must get the license to activate the Node B Daisy chaining feature.
The Node B must be integrated in an existing network in LR13.1 or higher
Proc1: Node B(A) Daisy Chaining Commissioning - TIL procedure is successfully
performed: The backhaul link is configured on the Ethernet Port/0 of Node B (A) as
required for the daisy chaining configuration.
The backhaul link is configured on the Ethernet Port/0 of Node B (B) according to
expected daisy chaining network
The minimum release software must be LR13.1.
The Node B synchronization Enhancements feature must be activated.
The VLAN Tagging is enable on each side (Node B 3G / eNodeB 4G / BTS 2G)
The Native IP Iub configuration mandatory used.
The GE MDA is required on xCCM (-U) or eCCM-U for Sync E /PTP.
The eCCM-U is required for analog 2.048/10/15 MHz synchronization source.
The NSP GUI is operational.

Ethernet Port OAM Ethernet port (MBH) is a logical instance and is always defined as EthernetPort/0.
Definitions
Daisy chain Ethernet port (DC) is specified as a physical instance and is never
EthernetPort/0. The choices are:
EthernetPort/1 meaning MDA SFP1
EthernetPort/2 meaning MDA SFP2
EthernetPort/3 meaning MDA RJ45

Continued on next page

32 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 3: Node B (A) Daisy Chaining Pre-Check

before Activation - WMS, Continued

NodeB (A) Daisy This procedure describes how to pre-check Ethernet Port parameters of Node B (A) before the
Chaining Pre- activation of the Node B Daisy Chain.
check before
Activation
Procedure Step Action
1 Open layout in W MS with Node B
2 Select Equipment Monitor by right click on concerned Node B (Node B (A))

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 33

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 3: Node B (A) Daisy Chaining Pre-Check

before Activation - WMS, Continued

NodeB (A) Daisy

Chaining Pre-
Step Action
check before
Activation 3 Check the following Ethernet Port requirements
Procedure
(continued)
If ... Then ...
Ethernet Port /0 and Port /1 does Node B ports are configured for
already exist Daisy chaining activation - Go to the
next procedure
Only one Ethernet Port /0 exists Redo the Node B integration from
IEH521 section 402 (Proc 5, 6 and
7) to create the missing Ethernet
Port with the new work order
including this additional Ethernet
Port/1. (Parameter included by the
network engineer team in the WO)

34 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS

Description This procedure describes how to configure the Ethernet Port/0 of Node B (A) for daisy
chaining through the Node B.

Preconditions The operator must get the license to activate the Node B Daisy chaining feature.
The Node B (A) must be integrated in an existing network in LR13.1.
Proc.3: Node B(A) Daisy Chaining Pre-Check before Activation WMS procedure
successfully performed.
The minimum release software must be LR13.1.
The Node B synchronization Enhancements feature must be activated.
The VLAN Tagging is enable on each side (Node B 3G / eNodeB 4G / BTS 2G)
The Native IP Iub configuration mandatory used.
The GE MDA is required on xCCM (-U) or eCCM-U for Sync E /PTP.
The eCCM-U is required for analog 2.048/10/15 MHz synchronization source.
The NSP GUI is operational.

Step of actions The following procedural steps need to be executed

Lock EthernetPort/0
Configure EthernetPort/0
Unlock EthernetPort/0

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 35

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS, Continued

Lock the This procedure describes how to lock the EthernetPort/0 before to configure it into MBH port
Ethernet Port/0 NOTE: This operation is executed from WMS
Procedure -
WMS/NSP Step Action
1 Open resource Browser GUI on NSP

2 Select Equipment monitor

Continued on next page

36 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS, Continued

Lock the
Ethernet Port/0
Step Action
Procedure -
WMS/NSP 3 Select BTSequipment | EthernetPort/0 | Configuration | Set
(continued) administrativeState.

4 Select Lock the Ethernet Port/0

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 37

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS, Continued

Lock the
Ethernet Port/0
Step Action
Procedure -
WMS/NSP 5 Wait until the status is 100% and Successful in the Command Manager
(continued) window

6 Check the new state of EthernetPort/0 is Locked

Result: EthernetPort/0 is Locked

Continued on next page

38 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS, Continued

Ethernet Port/0 This procedure describes how to configure the parameters for EthernetPort/0 in MBH port
Configuration
Procedure -
WMS/NSP Step Action
1 Select BTSequipment | EthernetPort/0 | Configuration | Object Editor

2 Select portRole from the list of attribute*

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 39

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS, Continued

Ethernet Port/0
Configuration
Step Action
Procedure -
WMS/NSP 3 Select Backhaul in the dropdown menu for the PortRole attribute of Ethernet
(continued) Port/0.

Continued on next page

40 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS, Continued

Ethernet Port/0
Configuration
Step Action
Procedure -
WMS/NSP 4 Click on SET button and Apply All Changes button
(continued)

5 Wait until the status is 100% and Successful in the Command Manager
window

NOTE: The Ethernet Port/0 of the Node B (A) is now configured as a Backhaul.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 41

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS, Continued

Unlock the This procedure describes how to unlock the EthernetPort/0 of the Node B (A) as MBH port
Ethernet Port/0
Procedure -
WMS/NSP Step Action
1 Select BTSequipment | EthernetPort/0 | Configuration | Set
administrativeState.

2 Select Unlock the Ethernet link/0

Continued on next page

42 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 4: Node B (A) Daisy Chaining Ethernet Port/0

Configuration Procedure - WMS, Continued

Unlock the
Ethernet Port/0
Step Action
Procedure -
WMS/NSP 3 Wait until the status is 100% and Successful in the Command Manager
(continued) window

4 Check the new state of EthernetPort/0 is Unlocked

Result: EthernetPort/0 is Unlocked

5 Close the Set Administrative State Action window

NOTE: The Ethernet Port/0 of the Node B (A) is now configured as a Backhaul and is
unlocked.

June 30, 2014 Alcatel-Lucent Internal 43

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS

Description This procedure describes how to configure the Ethernet Port/1 of Node B (A) for daisy
chaining through the Node B.

Preconditions The operator must get the license to activate the Node B Daisy chaining feature.
The Node B (A) must be integrated in an existing network in LR13.1.
Proc.3: Node B(A) Daisy Chaining Pre-check before Activation WMS procedure
successfully performed.
Proc.4: Node B(A) Daisy Chaining Ethernet Port/0 Configuration Procedure - WMS
procedure successfully performed.
The minimum release software must be LR13.1.
The Node B synchronization Enhancements feature must be activated.
The VLAN Tagging is enable on each side (Node B 3G / eNodeB 4G / BTS 2G)
The Native IP Iub configuration mandatory used.
The GE MDA is required on xCCM (-U) or eCCM-U for Sync E /PTP.
The eCCM-U is required for analog 2.048/10/15 MHz synchronization source.
The NSP GUI is operational.

Step of actions The following procedural steps must be executed to configure the Ethernet port 1 for daisy
chaining
Lock EthernetPort/1
Configure EthernetPort/1
Unlock EthernetPort/1

Continued on next page

44 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS, Continued

Lock the This procedure describes how to lock the EthernetPort/1 before to configure it into DC port
Ethernet Port/1 NOTE: This procedure requires access to the WMS
Procedure -
WMS/NSP
Step Action
1 Open resource Browser GUI on NSP

2 Select Equipment monitor

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 45

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS, Continued

Lock the
Ethernet Port/1
Step Action
Procedure -
WMS/NSP 3 Select BTSequipment | EthernetPort/0 | Configuration | Set
(continued) administrativeState.

4 Select Lock the Ethernet Port/1

Continued on next page

46 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS, Continued

Lock the
Ethernet Port/1
Step Action
Procedure -
WMS/NSP 5 Wait until the status is 100% and Successful in the Command Manager
(continued) window

6 Check the new state of EthernetPort/1

Result: EthernetPort/1 is locked

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 47

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS, Continued

Ethernet Port/1 This procedure describes how to configure the parameter EthernetPort/1 in DC port
Configuration
Procedure -
WMS/NSP Step Action
1 Select BTSequipment | EthernetPort/1 | Configuration | Object Editor

2 Select portRole from the list of attribute of the EthernetPort/1.

Continued on next page

48 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS, Continued

Ethernet Port/1
Configuration
Step Action
Procedure -
WMS/NSP 3 Select DaisyChaining in the dropdown menu for the PortRole attribute of
(continued) Ethernet Port/1.

4 Click on SET button and Apply All Changes button

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 49

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS, Continued

Ethernet Port/1
Configuration
Step Action
Procedure -
WMS/NSP 5 Wait until the status is 100% and Successful in the Command Manager
(continued) window

NOTE: The Ethernet Port/1 of the Node B (A) is now configured as a Daisy Chaining.

Continued on next page

50 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS, Continued

Unlock the This procedure describes how to unlock the EthernetPort/1 of the Node B (A) in DC port
Ethernet Port/1
Procedure -
WMS/NSP Step Action
1 Select BTSequipment | EthernetPort/1 | Configuration | Set
administrativeState.

2 Select Unlock the Ethernet link/1

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 51

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 5: Node B (A) Daisy Chaining Ethernet Port/1

Configuration Procedure - WMS, Continued

Unlock the
Ethernet Port/1
Step Action
Procedure -
WMS/NSP 3 Wait until the status is 100% and Successful in the Command Manager
(continued) window

Close the Command Manager window

4 Check the new state of EthernetPort/1

Result: EthernetPort/1 is Unlocked

5 Close the Set Administrative State Action window

NOTE: The Ethernet Port/1 of the Node B (A) is now configured as a Daisy Chain and is
unlocked.

52 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 6: Node B (A) Daisy Chaining IPRan Parameter

Configuration Procedure - WMS

Description This procedure describes how to configure the IPRan Parameter of Node B (A) for daisy
chaining through the Node B.

NOTE: Daisy chaining feature is subject to licensing. It is not activated by default.

NOTE: To activate the feature, the operator must first get the license, then set the flag IpRan:
isBackhaulDaisyChainingActivated = TRUE.

Preconditions The operator must get the license to activate the Node B Daisy chaining feature.
The Node B (A) must be integrated in an existing network in LR13.1.
Proc.4: Node B(A) Daisy Chaining Ethernet Port/0 Configuration Procedure - WMS
procedure successfully performed.
Proc.5: Node B(A) Daisy Chaining Ethernet Port/1 Configuration Procedure - WMS
procedure successfully performed.
The minimum release software must be LR13.1.
The Node B synchronization Enhancements feature must be activated.
The VLAN Tagging is enable on each side (Node B 3G / eNodeB 4G / BTS 2G)
The Native IP Iub configuration mandatory used.
The GE MDA is required on xCCM (-U) or eCCM-U for Sync E /PTP.
The eCCM-U is required for analog 2.048/10/15 MHz synchronization source.
The NSP GUI is operational.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 53

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 6: Node B (A) Daisy Chaining IPRan Parameter

Configuration Procedure - WMS, Continued

IPRan This procedure describes how to configure IPRan for daisy chaining.
Parameter NOTE: Configuration of IPRan parameter for Node B daisy chaining will activate the daisy
Configuration chaining in the Node B.
on Node B Daisy
Chaining NOTE: IsBackhauldaisyChainingActivated must be set to true
Procedure
Step Action
1 Open resource Browser GUI on NSP

Continued on next page

54 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 6: Node B (A) Daisy Chaining IPRan Parameter

Configuration Procedure - WMS, Continued

IPRan Parameter
Configuration on
Step Action
Node B Daisy
Chaining 2 Select BTSequipment | IpRan/0 | Configuration | Object Editor
Procedure
(continued)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 55

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 6: Node B (A) Daisy Chaining IPRan Parameter

Configuration Procedure - WMS, Continued

IPRan Parameter
Configuration on
Step Action
Node B Daisy
Chaining 3 Select IsBackhauldaisyChainingActivated from the list of attribute
Procedure
(continued)

4 Select True in the dropdown menu for the

IsBackhauldaisyChainingActivated attribute of IpRan/0.

Continued on next page

56 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 6: Node B (A) Daisy Chaining IPRan Parameter

Configuration Procedure - WMS, Continued

IPRan Parameter
Configuration on
Step Action
Node B Daisy
Chaining 5 Click on SET button and Apply All Changes button
Procedure
(continued)

6 Wait until the status is 100% and Successful in the Command Manager
window

7 Close the Command Manager window.

NOTE: The IpRan/0 of the Node B (A) is now activated in Daisy Chaining configuration.

June 30, 2014 Alcatel-Lucent Internal 57

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 7: Node B (A) Daisy Chaining Validation

Description This procedure describes how to check visually and validate the Node B (A) Daisy Chaining
through the Node B is operational.

Preconditions The operator must get the license to activate the Node B Daisy chaining feature.
The Node B must be integrated in an existing network under LR13.1 or higher.
The Node B daisy chaining must be activated.
The laptop setting and TIL connections are already done and available.
Laptop is available with a terminal emulator : e.g. Putty (or equivalent)
Laptop is connected to the internet network with RJ45
Node B (A) IP address and login details (Login and password) are available

Node B (A) Inspect LED status of both Node Bs (CCM module) to check visually the cabling and port
Daisy Chaining status as per Table below..
Visual Check
NOTE: This visual check requires being at site only for cabling issue or trouble shooting.

NOTE: The LED colors of the ports depends on their operational status whether daisy
chaining is active or not. If there is no daisy chaining port configured, but if CPRI connector
(SFP or RJ45 from GE MDA) is plugged with the Optical fiber or Electrical Link (MBH or DC
link), the LED status on the TIL GUI will be Green.

Continued on next page

58 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 7: Node B (A) Daisy Chaining Validation,

Continued

Node B (A) Daisy

Chaining Visual Table 10: Visual Check of GE MDA Ethernet Port Status
Check
(continued)
Then Check Visually the Ethernet port
If GE MDA Ethernet Port Status of each NodeB is...
Configuration of
Chaining Node B is... Node B (A) (3G) Node B (B) 3G
for Dropping /Chaining for Dropped /Chained

For Daisy Chaining link:

MDA SFP1 LED is Green
For IP Backhaul link:
MDA SFP2 LED is Green or
MDA RJ45 LED is Green

For IP Backhaul link:

MDA SFP1 LED is Green
For Daisy Chaining link:
MDA SFP2 LED is Green or
MDA RJ45 LED is Green

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 59

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 7: Node B (A) Daisy Chaining Validation,

Continued

Node B (A) This procedure describes how to check 3G Node B (A) configuration and activation for daisy
Daisy Chaining chaining with TIL tool.
Visual Check
Procedure with
TIL GUI NOTE: It is recommended to use remote TIL connection for economic reasons. At-site
activities are not required for this procedure.

Step Action
1 Open a TIL GUI (from WMS/NSP or a resource browser) on the Node B (A)
(3G) chaining

Continued on next page

60 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 7: Node B (A) Daisy Chaining Validation,

Continued

Node B (A) Daisy

Chaining Visual
Step Action
Check
Procedure with 2 Check visually the Node B (A) Chaining indications on the TIL GUI :
TIL GUI The following indications must be shown on the TIL GUI (refer to blue box
(continued) from the figure above)
The Node B is Connected to the OMC-B
The Config. file found has a DLU reference available (DLU: 0x)
The software reference is UNB0911xxxx (LR13.1) or higher.
The iBTS Packaging is known and compliant with the configuration
expected
One of the GE MDA port (example with RJ45) LED is green and defined
as Backhaul configuration
One of the other GE MDA port (example with SFP1) LED is green and
defined as Daisy Chaining configuration

NOTE: To troubleshoot inconsistency found, contact the coordinator and the

support team.
3 Validate on TIL GUI that the LEDs are compliant with Table 10: Visual Check
of GE MDA Ethernet Port Status as expected for the Node B (A) Daisy
Chaining configuration under test.

NOTE: Use the following guideline for LED description.

If LEDs on TIL GUI is... Then ...

Blank Port available, not used.
Green Up and running
Black Not usable.
MDA SFP2 and MDA RJ45 cannot
be used simultaneously. (mutually
exclusive)
Red Used, alarm
Orange Port administratively locked

NOTE: To troubleshoot alarms check the Alcatel-Lucent Node B

Commissioning and Fault Management User Manual: TIL (refer to references
section) and/or contact the support team.

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 61

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 7: Node B (A) Daisy Chaining Validation,

Continued

Node B (A) Daisy

Chaining Visual
Step Action
Check
Procedure with 4 Fill the LED result into the Node B Integration test records from IEH521
TIL GUI section 499.- Node B Integration test Records - Table Node B Daisy Chain
(continued) Visual Check Report sheet concerning the 3G Node B (A)

Continued on next page

62 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 7: Node B (A) Daisy Chaining Validation,

Continued

IP Ping test of This procedure describes the test to validate remotely the IP link between OAM and Node B
all Node B (A) (A) Daisy Chaining (Node B 3G mandatory used).
Daisy Chaining

Step Action
1 Perform the log-onto the WMS SSH server to allow usage of Telnet
commands using IEH521 - section 413 - Node B Daisy Chain Remote
Checking Procedure Telnet Commands:
Proc. 1: Node B in Daisy Chain Telnet Log onto WMS Server Procedure

2 Perform an IP Ping test of the Node B (A) Daisy Chaining with Telnet
commands, using IEH521 - section 413 - Node B Daisy Chain Remote
Checking Procedure Telnet Commands:
Proc. 2: IP Ping of All Node B in Daisy Chain - Testing Procedure

3 Check the Ping test result

If IP Ping tests result is... Then ...

[IP address] of Node B (B) is alive The physical link between the OAM
(Example: up to the Node B (A) daisy chaining
is validated
172.26.127.2x6 is alive)
No answer from [IP address] of The physical link between the
Node B (B) OAM up to the Node B (A) is not
(Example: validated or not configured.
no answer from To troubleshoot physical link
172.26.127.2x6) between the OAM and the Node
B, contact the coordinator and the
support team and if necessary
perform the following procedures
for initial check..

June 30, 2014 Alcatel-Lucent Internal 63

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 8: Node B (B) Daisy Chained Validation

Description This procedure describes the how to check and validate visually the Node B (B) Daisy
Chained whatever the technology used (2G or 3G or 4G)

Preconditions The Node B must be integrated in an existing network in LR13.1 or higher

All previous procedures are successfully performed.
The laptop setting and TIL connections are already done and available.
Laptop is available with a terminal emulator : e.g. Putty (or equivalent)
Laptop is connected to the internet network with RJ45
Node B (B) IP address and login details (Login and password) are available

Continued on next page

64 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 8: Node B (B) Daisy Chained Validation, Continued

Node B (B) This procedure describes how to check with TIL; the Node B (B) Daisy Chained is connected
Daisy Chained and activated.
Visual Check
Procedure TIL
GUI NOTE: It is recommended to use remote TIL connection for economic reasons. At-site
activities are not required for this procedure.

Step Action
1 Open a TIL GUI (from WMS/NSP or a resource browser) on the Node B (B)
(3G) chained

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 65

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

Proc. 8: Node B (B) Daisy Chained Validation, Continued

Node B (B) Daisy

Chained Visual
Step Action
Check
Procedure TIL 2 Check visually the Node B (B) Chained indications on the TIL GUI :
GUI (continued) The following indications must be shown on the TIL GUI (refer to blue box
from the figure above)
The Node B is Connected to the OMC-B
The Config. file found has a DLU reference available (DLU: 0x)
The software reference is UNB0911xxxx (LR13.1) or higher.
The iBTS Packaging is known and compliant with the configuration
expected
Only one of the GE MDA port (example here SFP1) LED is green and
defined as Backhaul configuration.

NOTE: To troubleshoot inconsistency found, contact the coordinator and the

support team.
3 Check TIL GUI LEDs are compliant with Table 10: Visual Check of GE MDA
Ethernet Port Status according to the configuration.
4 Check visually that the color code for LEDs is as follows:

If LEDs on TIL GUI is... Then ...

Blank Port available, not used.
Green Up and running
Black Not usable.
MDA SFP2 and MDA RJ45 cannot
be used simultaneously. (mutually
exclusive)
Red Used, alarm
Orange Port administratively locked

NOTE: Even if daisy chaining is not active, the color of the ports depends on
their operational status. For e.g. even if theres no daisy chaining port
configured, but if SFP is plugged along with the fiber, the status will be Green.

NOTE: To troubleshoot inconsistency found, contact the coordinator and the

support team.
5 Fill the LED result into the Node B Integration test records from IEH521
section 499.- Node B Integration test Records - Table Node B Daisy Chain
Visual Check Report sheet concerning the 3G or 4G Node B (B).

Continued on next page

66 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Node B Daisy Chaining through the Node B - Activation Procedure IEH 521, Section 706

Proc. 8: Node B (B) Daisy Chained Validation, Continued

IP Ping test of This procedure describes the test to validate remotely the IP link between OAM and Node B
all Node B (B) (B) Daisy Chained through the Node B (A). Whatever the technology used (2G or 3G or 4G)
Daisy Chained with the Node B (B).

Step Action
1 Perform the log-onto the WMS SSH server to allow usage of Telnet
commands using IEH521 - section 413 - Node B Daisy Chain Remote
Checking Procedure Telnet Commands:
Proc. 1: Node B in Daisy Chain Telnet Log onto WMS Server Procedure

2 Perform an IP Ping test of the Node B (B) Daisy Chained with Telnet
commands, using IEH521 - section 413 - Node B Daisy Chain Remote
Checking Procedure Telnet Commands:
Proc. 2: IP Ping of All Node B in Daisy Chain - Testing Procedure

3 Check the Ping test result

If IP Ping tests result is... Then ...

[IP address] of Node B (B) is alive The physical link between the OAM
(Example: up to the Node B (A) daisy chaining
is validated
172.26.127.2x6 is alive)
No answer from [IP address] of The physical link between the
Node B (B) OAM up to the Node B (A) is not
(Example: validated or not configured.
no answer from To troubleshoot physical link
172.26.127.2x6) between the OAM and the Node
B, contact the coordinator and the
support team and if necessary
perform the following procedures
for initial check..

June 30, 2014 Alcatel-Lucent Internal 67

Proprietary Use pursuant to Company instruction
IEH 521, Section 706 Node B Daisy Chaining through the Node B - Activation Procedure

This page is intentionally left blank

68 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
GCD Networks
Global Delivery Readiness

IEH 521, Glossary

June 30, 2014

Alcatel-Lucent
INTEGRATION ENGINEERING HANDBOOK 521
WCDMA Node B (iBTS - Global Markets)

Glossary

Table of Contents

General ............................................................................................................ 2
Section Description .......................................................................................... 2
Previous Release ............................................................................................. 2
Release Notes ................................................................................................. 2
Common Section ............................................................................................. 2
Acronyms .......................................................................................................... 3
A................................................................................................................. 3
B ................................................................................................................. 3
C................................................................................................................. 3
D ................................................................................................................ 3
E ................................................................................................................. 4
F ................................................................................................................. 4
G ................................................................................................................ 4
H ................................................................................................................ 4
I ................................................................................................................. 4
J ................................................................................................................. 4
K................................................................................................................. 4
L ................................................................................................................. 4
M ................................................................................................................ 4
N ................................................................................................................ 4
O ................................................................................................................ 5
P ................................................................................................................. 5
Q ................................................................................................................ 5
R................................................................................................................. 5
S ................................................................................................................. 5
T................................................................................................................. 5
U ................................................................................................................ 6
V................................................................................................................. 6
W ................................................................................................................ 6
X ................................................................................................................. 6
Y ................................................................................................................. 6
Z ................................................................................................................. 6

Alcatel-Lucent Internal
Proprietary Use pursuant to Company instruction
IEH 521, Glossary Glossary

General

Section This section provides an acronym list and glossary for the IEH 521.
Description

Previous Release Dec, 2013

Release Notes Updates due to addition of LR13.3W

Updates due to Node B RF validation procedures - June 14
Updates to include MC-TRX, d2U/BBU to d4U migration, CCM-U board migration, CEM-U
board migration, LR13.1W features

Common This section is applicable to all sections of the handbooks IEH 521
Section

2 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Glossary IEH 521, Glossary

Acronyms

A AC
ALU
Alternate Current
Alcatel Lucent
AN Access Node
ATM Asynchronous Transfer Mode

B BTS Base Transceiver Station

C CARES
CIC
Customer Assistance Request Entry System
Customer Information Center
CIQ Customer Information Questionnaire
CPRI Common Public Radio Interface
CS Circuit Switched
CCM Central Controller Module

D D2U Digital Baseband Unit (2 units high)

9326 D2U (d2U V2) and 9926 BBU (d2U V3)
D4U Digital Baseband Unit (4 units high)
9926 DBS 4U (d4U V3)
DC Direct Current
DHCP Dynamic Host Configuration Protocol
DL Down Link
DSX Digital Cross-Connect
DTF Distance To Fault

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 3

Proprietary Use pursuant to Company instruction
IEH 521, Glossary Glossary

Acronyms, Continued

F FDD
FTP
Frequency Division Duplex
File Transfer Protocol

G GGSN
GUI
Gateway GPRS Support Node
Graphic User Interface

H HSE High Speed Ethernet

I IEH
IMA
Integration Engineering Handbook
Inverse Multiplexing on ATM
IP Internet Protocol
I&C Installation and Commissioning

J JRE Java Runtime Environment

L LTE Long Term Evolution (4G)

M MIB
MC-TRX
Managed Information Blocks
Multi-Carrier Transceiver
MBH Mobile Back Haul

N NeID
NSP
Network Element Identifier
Network Services Platform

Continued on next page

4 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction
Glossary IEH 521, Glossary

Acronyms, Continued

O O&M/OAM
OMC
Operations and Maintenance
Operational Maintenance Center
OS Operating System

P PC
PCM
Personal Computer
Pulse Code Modulation
PS Packet Switched
PSTN Public Switched Telephone Network
PSU Power Supply Unit

R RRH
RF
Remote Radio Head
Radio Frequency
RL Return Loss
RSSI Received Signal Strength Indicator
RTWP Received Total Wideband Power
RX Receiver / Receive Path

S SIM
SUM
Subscriber Identity Module
Station Unit Module
SFP Single Fiber Port

T TPM
TIL
Technical Project Manager
NodeB Terminal for Local Installation
TMA Tower Mounted Amplifier
TX Transmitter / Transmit Path
TCP/IP Internet Protocol
TRE Transceiver Equipment (= TRX)

Continued on next page

June 30, 2014 Alcatel-Lucent Internal 5

Proprietary Use pursuant to Company instruction
IEH 521, Glossary Glossary

Acronyms, Continued

U UMTS
UL
Universal Mobile Telecommunications System
Uplink
UTRAN Universal Terrestrial Radio Access Network

V VSWR Voltage Standing Wave Ratio

W WCDMA
WMS
Wideband Code Division Multiple Access
Wireless Management System
WPS Wireless Provisioning System

6 Alcatel-Lucent Internal June 30, 2014

Proprietary Use pursuant to Company instruction