TMO 18553 WCDMA D2u D4u Distributed NodeB Integration in An Existing UTRAN - 14w29 PDF

9326 d2U /9926 BBU 2U/4U
Distributed Node B
Integration
Course Reference: TMO 18553

GPEC
July 2014
All Rights Reserved Alcatel-Lucent 2006
Agenda
Distributed NodeB Integration in an Existing UTRAN
Distributed NodeB Integration Testing
Distributed NodeB Integration Additional NSP GUI
Work order creation
NodeB integration to WMS / NSP GUI
Basics Tests
2 | Distributed Node B Integration | July 2014
Distributed Node B Integration

in an Existing UTRAN
Node B Integration - Preparation steps

The flow diagram outlines the
preparation steps for the
integration of a Node B.
Node B Integration flow of activities

The flow diagram outlines
the steps which need to be
performed to complete the
integration of a Node B.
Node B Integration Testing - Flow Diagram

the steps which need to
be performed to complete
the integration testing of a
Node B.
Node B Integration Applicable IEH521 Sections & Methods Documents

Applicable IEH 521 Sections for WCDMA Node B Integration
Applicable Methods documents for IEH 521 Sections 4xx

9YZ-04088-0014-PCZZA Alcatel-Lucent 9353 Wireless Management System User Guide
https://infoproducts.alcatel-lucent.com/aces/cgibin/dbaccessfilename.cgi/9YZ040880014PCZZA_V1_
9YZ-04088-0015-TQZZA Alcatel-Lucent 9353 Wireless Management System - Security
Fundamentals
https://infoproducts.alcatel-lucent.com/aces/cgibin/dbaccessfilename.cgi/9YZ040880015TQZZA_V1_
9YZ-05870-0060-UFZZA Alcatel-Lucent 9353 Wireless Management System - Node B Alarms
Reference Guide (LR13.3)
http://cic.us.alcatel-lucent.com/pdfdocs14/pristore215/536534.pdf
Node B Integration 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
Node B Integration Procedures Overview

The following table provides an overview about the steps required to perform integration of
WCDMA Node B.
Node B Integration Test Procedures Overview

The table below lists all operational steps for testing of a new Node B after integration.
Node B Integration 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).
Conditions:
This procedure has to be executed only during the initial setup for a specific integration (customer).
If done already no action is required.
Preconditions:
The following data are required for the setup:
NSP server name or
NSP server IP address
Setup PC for OAM client Procedure

Step
Action
Locate host file on the PC and open with text editor
Check for presence of NSP server name and IP address in hosts file
Save new host file
Node B Integration 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 Procedure

Step
Action
Start Web browser with

http://NSPserver's name:8080/NSP/
or
http://IPadress:8080/NSP/
This command opens the WMS entry page.
Update Java to correct version
Complete JRE installation and launch
Click on LAUNCH GUI to open NSP session
Execute login
NOTE: Use your User ID and Password.
Accept warning window
Node B Integration 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 Procedure

Step
Action
Click on File and open Select Network Layout to open the Layout Selector.
Select the desired layout (use Layout Name) and click View button to open den concerned layout in Navigator.
Double click on concerned layout to open the Resource Browser for the concerned RNC.
Click with right button of mouse on concerned RNC within the Resource Browser to open submenu.
Select Show alarms and right click to open Alarm Manager window.
Check for un-allowed RNC alarms in the Alarm Manager window for the concerned RNC:
NOTE: Un-allowed RNC alarms: Iub alarms
All un-allowed alarms of the node

under work need to be cleared prior
to continuation.
NOTE: External alarms do not require
clearance and can be accepted.
NOTE: Use Alarm Dictionary for alarm analysis
and clearance.
End of procedure
Node B Integration 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:
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 Configuration Data Procedure

Step
Action
Open Resource Browser GUI on NSP.
Select target RNC for Node B integration and select Configuration | CM XML | Export NE Grouping
Node B Integration Proc 4: Export Network Configuration Data (Continued)

Export Network Configuration Data Procedure (Continued)
Step
3
Action
Press Export Now on Export NE Grouping tag.
Snapshot to data designer

The exported network data snapshot (.xml) is:
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)
Check on Command Manager when export is finished.
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
Send snapshot to data fill team for further processing to generate work order for Node B integration.
NOTE: Network Data Designer (data filler) contact information is required to hand-off
the snapshot (email address). Contact TPM for contact information and planning.
Node B Integration 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 snapshot
The exported network data snapshot (.xml file) must be sent to the network data design team (data filler) for further
processing.
Work order generation
Network Data Design team generates the new Node B / Node B parenting work order based on:
provided network data snapshot (.xml)
customer data (CIQ based)
configuration data
Reception of work order
Network Data Design team provides new Node B / Node B parenting work order to integrator for further use during the
integration.
Delivery method of work order
Email from data filler
Node B Integration 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 import Procedure

Step
Action
Load work order (.xwo) into PC in preparation of file transfer
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
Verify that the work order has been successfully transferred into the WMS main server under
/opt/nortel/data/cmXML
Node B Integration Proc 7: Pre-checks before activation

Description:
This procedure performs pre-checks prior to activation of the work order
RNC alarms
MIB audit
Preconditions:
The work order (.xwo) is available on the WMS main server under the main server directory: /opt/nortel/data/cmXML
Pre-checks before activation Procedure

Step
Action
Click on File and open Select Network Layout to open the Layout Selector.
Select the desired layout (use Layout Name) and click View button to open den concerned layout in
Navigator.
Double click on concerned layout to open the Resource Browser for the concerned RNC.
Click with right button of mouse on concerned RNC within the Resource Browser to open submenu.
Select Show alarms and right click to open Alarm Manager window.
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

Step
Action
Open Audit Action Window from context menu (right-click on NE)
Select Configuration | Select MIB | Select Audit to open Action Audit Window
10
Click on Audit Now to start audit process.
NOTE: The Command Manager window appears

and display audited NEs and the audit progress.
11
Check audit results for unwanted status by use of Details tab:
NOTE: The audit process can take several minutes to complete


Step
12
Action
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.
Node B Integration 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.
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 Procedure

Step
Action
Open NSP session manager by clicking on

Configuration |Sessions Manager from NSP menu bar.
Activate Create New Session

NOTE: Create Session window is opened
Enter a value for Session Name to start the NSP session.

NOTE: It is recommended to use the work order name.
Expand cmXML tree and select previously loaded new work

order for Node B integration.
Click Add to list button to move work order into right window.
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.
(continued)
Node B creation Procedure (continued)

Step
Action
Activate Node B work order by clicking Launch button.

NOTE: A new window with two worksheets is opened:
Creation
Summary & Action
Monitor creation status and monitor until completed
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.
10
Expand Actions for <Session> and select RNC/xxx RNCEquipment/0 INode/xxx node
and
activate Validation button
to execute the Validation task.
(continued)

Step
Action
11
Verify that validation task is successfully completed:
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)

Step
14
Action
Monitor progress and
ensure successful completion
NOTE: All impacted nodes must have:

Status = Successful
Progress = 100%
15
Terminate session when activation was successful.
Node B Integration 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 procedure describes the individual steps to create a new Node B on an available RNC.
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 into layout Procedure

Step
Action
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.
Select from Layout Selector window desired layout and click on Edit button to open the Navigator window.
Double click on selected layout to open in edit mode.

NOTE: It will load the layout into the resource browser.
Open NE Store to search for target Node B
Node B Integration Proc 9: Move of new Node B into layout
(Continued)
Move Node B into layout Procedure (Continued)

Step
Action
Find Node B for move in NE Store
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.
Node B Integration 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 Node B NE ID
Retrieve required NE ID number from site through TIL (on-site activity)
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 NeID Procedure

NOTE: Steps 1 to 4 are on-site activities and not required if Node B NeID is available from TPM.
Step
Action
Connect TIL to CCM(-U) port 1
Login by using:
Login: nodeB
Password: nodeblnx
Retrieve the Node B serial number which is displayed at the bottom of the TIL GUI:
Read:
.Serial Number: example
Store Serial Number for further use.

NOTE: Node B NeID is typically provided by on-site personnel through phone or email.
Node B Integration Proc 10: Update Node B NeID (Continued)

Update Node B NeID Procedure (continued)
Step
Action
Select new Node B icon in NSP Resource Browser
Use right click to open menu bars and select Configuration
A new under menu opens select Object Editor
Select line with attribute

neid in open Object Editor window
Enter correct (previously retrieved from site)

NeID number
Apply new value by clicking

Set and Apply all changes
Node B Integration 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 State Change and Activation Procedure

Step
Action
Test connectivity with Node B on OAM link by sending ping command to Node B IP address.
Select new Node B in Resource Browser.
Right click Configuration then select Set NEs`OAM Link Administrative State
Click Unlock when State Action Window is open.
Node B Integration Proc 11: Node B OAM link State Change & Activation
(continued)
Node B OAM link State Change and Activation Procedure (Continued)

Step
Action
Check that the NE status changes from Lock to Unlock

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.
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
7
With successful build report after unlocked OAM administrative state the Node B is successfully activated
and ready for testing.
Node B Integration 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.
Preconditions:
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
Creation of New layout in WMS Procedure

Step
Action
In NSP open window, select File from the menu bar and select Select Network Layout to open Layout
Selector.
Click on Layout Management and then New to open new Window to enter new layout name.
Enter name for new layout NEW Layout and press OK button
NOTE: The new layout name appears in the Layout Selector window.
Node B Integration 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 Procedure

Step
Action
In NSP open window, select File from the menu bar and select Select Network Layout to open Layout
Selector.
Select from Layout Selector window desired layout and click on Edit button to open the Navigator window.
Double click on selected layout to open in edit mode.

NOTE: It will load the selected layout into the resource browser.
Node B Integration Proc 14: View layout in WMS (optional)

Description:
This operation details how to open the layout in view mode.
Supporting Procedure for integration :
Opening of Layout is used for many different reasons during the operation of a network.
In the context of this IEH521 the layout on WMS open in view mode is required to perform necessary actions during the
integration procedure.
Entry Criteria:
NSP GUI operational
View layout Procedure

Step
Action
Select File from menu bar and click on Select Network Layout to open Layout Selector window.
Select desired Layout and click on View to open Navigator window
Load layout applications by double clicking on desired Layout

NOTE: The desired layout is now open for further operations.
Node B Integration 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 procedure :
Outdoor cabinet from Eltek: Small S6 Includes: 9326 d2U V2 or 9926 d2U V3
DC/DC power supply configuration:
DO NOT use this procedure to integrate alarms of an external DC/DC power supply.
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.
External PSU alarm integration in small cabinet Procedure

Step
Action
Open layout in WMS with Node B for integration of power supply alarms
Right click on concerned Node B and select Equipment Monitor to open Equipment Monitor.
Open External Alarm Mapping Table and select ExternalAlarms/0
External PSU alarm integration in small cabinet Procedure (Continued)
Step
4
Action
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.


to Small S6 PSU Alarm = Major Alarm PSU

Step
8
Action

to Small S6 PSU Alarm = Minor Alarm PSU
10

11

to Small S6 PSU Alarm = Door Alarm

Step
Action
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.
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.
Integrate the DC surge protection box alarm in small cabinet as described in the action table
Integration sequence:
This procedure will be executed AFTER the mandatory steps of a new Node B integration are successfully done.
NOTE: DC surge protection box is optional. Integration of alarm is only required if present
DC surge protection box alarm integration procedure small cabinet (optional) Procedure
Step
Action

Set the field alarm message to Small S6 PSU Alarm = DC Surge Protection Box Failure (RRH1 to RRH3)
Click Set and then Apply All Changes
Node B Integration 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 procedure :
Outdoor cabinet from Eltek:
Medium Md6 or Medium Md4
Includes: 9326 d2U V2 or 9926 d2U V3 or 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.
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.
External PSU alarm integration in medium cabinet Procedure

Step
Action
Open layout in WMS with Node B for integration of power supply alarms
Right click on concerned Node B and select Equipment Monitor to open Equipment Monitor.
Open External Alarm Mapping Table and select ExternalAlarms/0

(optional)
External PSU alarm integration in medium cabinet Procedure (Continued)
Step
4
Action

5

to Medium PSU Alarm = AC Mains Alarm


to Medium PSU Alarm = Major Alarm PSU

(optional)

Step
8
Action

to Medium PSU Alarm = Minor Alarm PSU
10

11

to Medium PSU Alarm = Door Alarm

(optional)

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

(optional)
Integrate the DC surge protection box alarm in medium cabinet as described in the action table
Integration sequence:
This procedure will be executed AFTER the mandatory steps of a new Node B integration are successfully done.
NOTE: DC surge protection box is optional. Integration of alarm is only required if present
DC surge protection box alarm integration procedure medium cabinet (optional) Procedure
Step
Action

Set the field alarm message to Medium PSU Alarm = DC Surge Protection Box Failure (RRH1 to RRH3)

Set the field alarm message to Medium PSU Alarm = DC Surge Protection Box Failure (RRH4 to RRH6)
Distributed Node B
Integration Testing
Node B Integration Testing - Tools Required

Description:
To test successful integration of a Node B, a small set of equipment and tools is required for on-site testing activities.
Equipment needs on-site:
The following equipments are required for integration testing by on-site engineer:
WCDMA cell-phone operating in the frequency band of Node B under integration
Capabilities:
Voice
Video
Data (FTP)
Network registered SIM card
Equipment needs remote / NSP :
The following equipments are required for integration testing remote / NSP GUI site:
Phone access (to allow information exchange with on-site engineer)
IT equipment capable for NSP GUI operations
45 | Distributed Node B Integration Testing | July 2014
Node B Integration Testing - Flow Diagram

the steps which need to
be performed to complete
the integration testing of a
Node B.
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 and RNC number of Node B under check
Node B online tests Procedure

Step
Action
Open layout view on WMS (NSP)
Set cursor on the RNC NE and click on the right mouse button to open pull-down menu
Select Show Alarms to open Alarm manager Window
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.
If FDD cell alarms occur :

Analyze alarms by using the document External UTRAN Alarms Dictionary
Perform trouble shooting to clear unexpected FDD cell alarms before moving to next step of Integration testing
Node B Integration Testing - Proc 1: Node B online tests: Communication Tests

Content of communication tests: The communication tests do consist of:
CS call test (voice)
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 specific deviations
Customer specific requirements for testing may result in modifications of the call testing. Customer specific requests should
not change the generic flow of call tests operation and shall 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 sector and frequency for call tests
Lock all FDD cells of the integrated Node B which are NOT subject to call test of the required sector and frequency.
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 selection of sector and frequency for call tests
A new FDD cell is made available for
call testing by change the locking status of FDD cells.
Selection of sector
Locking of all FDD cells of sectors must be
in synchronization with the position of the site engineer.
Example: Sector 0 and Sector 2 locked:
NOTE: Call testing can be performed in Sector 1.
Node B Integration Testing - Flow Diagram of Call Tests Operation

The following flow of
operation provides
information about the
steps and sequence to call
test a integrated Node B,
consisting of several
sectors and frequencies
(FDD cells)
Information to control lock/unlock of FDD cell :
The on-site engineer (performing
the call testing) provides
information about the need to
change the locking status.
The information is typically
submitted by phone.
Node B Integration Testing - Proc 2: Change Locking/Un-locking status of FDD

cells
Description:
This procedure allows to lock / unlock FDD cells of a dedicated Node B.
Preconditions:
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.

cells (Continued)
Locking of FDD cells Procedure
Step
Action
Right click in Layout on concerned RNC (Node B under test is connected there) to open sub-menu
Click on Equipment Monitor to open Equipment Monitor window
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.
4
Click on Lock button to start execution of lock command.
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)
Repeat steps 1 to 5 for every FDD cell to be locked.

cells (Continued)
Unlocking of FDD cells Procedure
Step
Action
Right click in Layout on concerned RNC (Node B under test is connected there) to open sub-menu
Click on Equipment Monitor to open Equipment Monitor window
Select FDD cell of Node B under integration test

targeted to unlock.
Then press
Configuration|Set Administrative State.
RESULT: The Set Administrative State Action Window opens for selected FDD cell.
4
Click on Unlock button to start execution of unlock command.
Monitor successful execution of Unlock command in Command Manager window by selecting logs
RESULT: Selected FDD cell is unlocked
Repeat steps 1 to 5 for every FDD cell to be locked.
Node B Integration Testing - 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 definition
Circuit Switched Call on FDD cell of a Node B.
Recommended call duration: ~ 2 mins
Success criteria
Connection to predefined subscriber is established. Understandable audio conversation (uplink and downlink).
Node B Integration Testing - Proc 3: Circuit Switched Call Test (Continued)

Circuit Switched Call Test Procedure
Step Action
1
Verify with integrator that all FDD cells not under call test are locked and FDD cell under test is unlocked.
Verify that the ON SITE engineer is well positioned for the CS call test of the dedicated sector (FDD cell) under
test.
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.
Document result of CS call test in Call test sheet.
Continue with further call tests or change cell locking status:
IMPORTANT: After finalization of all communication tests all FDD cells of the Node B under communication testing
have to be unlocked.
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:
Specific Cell phone (video call capable) with network registered SIM
Telephone number for test (Video call capable)
IMPORTANT: For all communication tests, collaboration of on-site personnel and integration tester is required. Use
telephone connection to exchange necessary information.
Video call - test definition
Video Call on FDD cell under test of a Node B.
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.
Node B Integration Testing - Proc 4: Video Call Test (Continued)

Video Call Test Procedure
Step Action
1
Verify that the ON SITE engineer is well positioned

for the Video call test of the dedicated sector (FDD cell) under test.
Perform video call (Site engineer 1 to a 2nd 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.
Document result of Video call test in Call test sheet.
Node B Integration Testing - 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:
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/)
Target throughput values for DL and UL are available for checking (from network design team)
IMPORTANT: For all communication tests, collaboration of on-site personnel and integration tester is required. Use telephone
connection to exchange necessary information.
PS call - test definition
Packet Switched call to available website on FDD cell of a Node B
File transfer to and from FTP server
(Continued)
Packet Switched Call Test Procedure

Step Action
1
Verify that the ON SITE engineer is well positioned

for the PS call test of the dedicated sector (FDD cell) under test.
Perform PS call test by opening a test website

(e.g. www.alcatel-lucent.com)
and check that the website builds up correctly.
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.
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.
(Continued)
Packet Switched Call Test Procedure

Step Action
6
Document result of PS call test in Call test sheet.
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)
Preconditions:
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
Node B Integration Testing - Proc 6: External alarms test small/medium

cabinet (Optional) (Continued)
External alarms test small/medium cabinet Procedure Door Alarm
Step
Action
Open door of Small or Medium Cabinet to trigger Door Alarm (Site Engineer)
Open layout view on WMS (NSP) Node B resource browser
Set cursor on the Node B NE and click on

the right mouse button to open pull-down menu
and select Show Alarms in new Window
to open Alarm manager Window.
Verify occurrence of Door Alarm.
NOTE: Alarm manager window

must display Door Alarm
5
Close door of Small or Medium Cabinet to remove alarm condition (Site Engineer)
Validate that the Door Alarm has disappeared at WMS in OMC alarm view
Node B Integration Testing - 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.
Node B Integration Testing - Proc 7: External PSU alarms test medium cabinet
cabinet (Optional) (Continued)
External PSU alarms test medium cabinet Procedure AC Mains Alarm
Step
Action
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
Open layout view on WMS (NSP) Node B resource browser
Set cursor on the Node B NE and click on

the right mouse button to open pull-down menu
and select Show Alarms in new Window
to open Alarm manager Window.
Verify occurrence of
Medium PSU ALARM = AC Mains Alarm PSU.
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)
Validate that the Medium PSU ALARM = AC Mains Alarm PSU has disappeared at WMS in OMC alarm view.
Distributed Node B
Integration
Additional NSP GUI
Workorder & Uploading WO to WMS using FileZilla

The operational Workorder is sent by the engineering team up to the OAM operational team.
The next operation is to put the Workorder on WMS using Filezilla and integrate the NodeB in an existing UTRAN.
The Workorder should be under the following folder:
/opt/nortel/data/cmXML/
PC Folder
WMS Folder:
/opt/nortel/data/cmXML/
Workorder files (.xwo)

(Ex for Node B Montreuil )
Layout without NodeB MONTREUIL

Launch NSP and open the layout where the NodeB will be integrated
Integration
From NSP go to Configuration / Session manager
A session window will be opened => click on Create new session
Integration
Select the Workorder of the dedicated Node B and click on Add to list then next
Integration
Click on Launch
Integration - Validation
Follow each step of Action window (Validation, Pre-activation, Activation)
Step 1 : VALIDATION
Integration - Preactivation
Step 2 : PRE-ACTIVATION
Integration - Activation
Step 3 : ACTIVATION
Integration Terminate session

Step 4 : TERMINATE SESSION / YES
Integration NE store
From NSP go to File / Select Network Layout Click on the Layout Name then Edit.
Integration - NE Store
Open the Layout and click on NE store. Then, click on find
NE Store
NodeB : MONTREUIL
Inrtegration NE Store
Select the NE (NodeB MONTREUIL) from the list and click on Move to and select the Layout
Integration - NE Store
Node B MONTREUIL is seen in the Layout
Node B MONTREUIL
Is seen in the Layout
Integration
From NSP go to File / Select Network Layout click on the layout and then View
Integration - Neid
From NSP open the layout. Select the NodeB, right click / configuration / Object editor
Integration - Neid
Object editor opened. Select the attribute NeId, Enter the correct value ( The same with the NodeB site)
Enter the new value and apply it by clicking Set and Apply all changes
Integration
From NSP open the layout where the NodeB is integrated. Select the NodeB, right click / configuration /
set NEs OAM Link Administrative State
Integration
Click on Unlock
Integration
After few minute the Node B is supervised (appears in Red).
Check all alarms and perform some basic tests (CS & PS calls)
www.alcatel-lucent.com
84 | eModules migration | Sept 2011

TMO 18553 WCDMA D2u D4u Distributed NodeB Integration in An Existing UTRAN - 14w29 PDF

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TMO 18553 WCDMA D2u D4u Distributed NodeB Integration in An Existing UTRAN - 14w29 PDF

Uploaded by

Copyright:

Available Formats

9326 d2U /9926 BBU 2U/4U

Course Reference: TMO 18553

All Rights Reserved Alcatel-Lucent 2006

2 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Distributed Node B Integration

All Rights Reserved Alcatel-Lucent 2006

Node B Integration - Preparation steps

4 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration flow of activities

5 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Testing - Flow Diagram

6 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Applicable IEH521 Sections & Methods Documents

Applicable Methods documents for IEH 521 Sections 4xx

7 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Prerequisites

8 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Procedures Overview

9 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Test Procedures Overview

10 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Proc 1: Setup PC for OAM client

Setup PC for OAM client Procedure

Locate host file on the PC and open with text editor

11 | Distributed Node B Integration | July 2014

Save new host file

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Proc 2: Connect to WMS and start session

NSP GUI Start Procedure

Start Web browser with

Update Java to correct version

Complete JRE installation and launch

Click on LAUNCH GUI to open NSP session

Accept warning window

12 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Proc 3: Check RNC alarm and layout conditions

Check Alarms Procedure

All un-allowed alarms of the node

13 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Proc 4: Export Network Configuration Data

Export Network Configuration Data Procedure

Open Resource Browser GUI on NSP.

14 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Proc 4: Export Network Configuration Data (Continued)

Snapshot to data designer

Check on Command Manager when export is finished.

Use Filezilla (or similar) to connect to NSP server for FTP.

15 | Distributed Node B Integration | July 2014

All Rights Reserved Alcatel-Lucent 2006

Node B Integration Proc 5: Work order creation for a new Node B

16 | Distributed Node B Integration | July 2014