Huawei DBS3900 Commissioning MOP - V1 - 2 20090515

Huawei DBS3900 Commissioning Procedure Security Level:
Huawei DBS3900
Commissioning Procedure
(V1.2)
2009-05-15 HUAWEI Confidential Page1, Total30

Scope
The scope of this document is to give a detail procedure for the commissioning of the
Huawei DBS3900 base station. The document will provide the required tools, contacts
and procedures to be followed.
Document Revision
Version Author Reviewer Date Approver Change Log
Draft S Perkins 02/11/2009 Initial Draft
V1.0 Pan Fei 04/20/2009 V1.0
V1.1 Pan Fei 04/27/2009 V1.1
V1.2 Pan Fei 05/15/2009 V1.2
1. Tools List
Tools Sub Contractor Huawei
Compass X
Digital Camera X
GPS Navigation (Optional) X
Laptop X
Mobile Phone (For X
communication)
Test Data Card X
Test Mobile Phone and SIM X
USB Flash Memory Stick X
UTP Network Cable X
Vehicle X
Multi meter X
2. Site Awareness
There are a number of site in Canada that are in remote location that require
situational awareness therefore when travelling to and from remote site locations it is
important that the engineer is equipped for travel to remote sites
Engineers must also be aware that Tower work takes precedent over any other site
work; therefore if tower work is in progress then the tower crew is in control of the site.

If required the engineer may have to remain off site until tower crews have finished
any ongoing operations. If tower work is in progress then hard hats are required to be
worn onsite.
3. Commissioning Process
The commissioning process for the Huawei DBS3900 will follow the flow shown below.
The following section will provide a breakdown of the activities required for successful
commissioning of the base station.

4. NTP Report
The NTP report is a report that details which sites have received “Notice to Proceed”
(NTP) from the customer. This report then provides the basis for scheduling activities
for commissioning preparation and commissioning activities. From this report a
forecasting schedule will then be produced to initiate the site configuration data to be
prepared and the scheduling of engineers to attend site for commissioning.
The details of this process are not covered in this document and is only included for
informational purposes.
5. Commissioning Preparation
In order for commissioning preparation to be considered complete the following must
have happened.
1. Confirmed NTP report released, hardware installation completed, NodeB was

powered on and IP connectivity is available (Telus)
2. Iub data and cell data for the NodeB is downloaded to RNC (Huawei)
3. Cells were correctly declared on Core Network side (NSN)
4. NodeB was created on OSS (Huawei)
5. IPCLK links were created on 2 IPCLK servers
6. Sub-contractor team got the correct NodeB software and Script from Huawei.
7. Sub-contractor team got the special USB memory stick with LED available and
kept the NodeB software and script with the correct name, file format in the
correct path as following:
NodeB software: \\NodeB\Software\Software.cspBoot
BootROM: \\NodeB\Software\Firmware.csp
Data configuration file: \\NodeB\Configuration\NodeBCfg.xml
Make sure that each USB stick is only kept with 3 files above dedicatedly for one
NodeB, it’s better to label the USB stick with the site Name before commissioning to
avoid the USB sticks mixing if more than 1 site will be integrated for one team.

6. Site Keys and Codes

In order for the engineer to be able to attend a site for commissioning it will be
necessary for the keys and/or codes to be signed out. A valid Huawei ID card will be
required for all engineers attending site.
• Sign out Telus Mobility key from Huawei Region PM.
• Approved footwear must be worn
• All employees must have a hard hat, hard hat must be worn at all times
when a tower crew is on site
7. Site Access Procedures

On attending site the engineer will be required to follow the site access procedures
laid out below.
• Upon entry into the site one person must immediately call the security control
center and report what site you have entered, provide your name and you are
from Huawei, report site name and site number, report what your work order is
to be on site.
• The security control center phone number, site name and site ID is posted
on the wall beside the phone
• If there is a site book you must log into the book.
• When you are last person in the site you must call security control and sign out
from the site before leaving.
• You must take care and ensure that the lights are turned off, the shelter door is
locked and properly closed, shut the gate and close the gate lock.
This procedure must happen all the time, every time.
8. Site Installation Checks

Before the engineer begins the commissioning of the base station they will be
required to carry out an audit of the installation quality. There are two parts to the audit,
the first is checklist for the BBU hardware, and the second is the checklist for the

DCDU. Please refer to the document: <Telus Checklist for Hardware

Installation.>
Both checklist need to be completed, photographs must be taken and submitted as

part of the site documentation.
<Site ID>_<Equipment>_Photo.jpg (Overview, DCDU, BBU and Power)
Once the audit checks have been completed and no major issues have been found
then commissioning can commence. If any major issues are found then the issue
must be recorded and escalated to Huawei Regional PM and Huawei RNC Engineer
9. BBU Serial Number

After BBU hardware checking, find the BBU serial number as following and record the
number with the file:
<Site ID>_BBU SN_<Serial Number>.txt
For example 21023156401000001572

10. Local Commissioning

There are 2 possible ways to commission the Huawei DBS3900, the first is the USB
commissioning method and the second is the LMT Commissioning method, both are
covered below.
10.1 USB Commissioning

Please refer to the document: < DBS3900 Commissioning Key Point
Guide_Telus>
DBS3900 automatically reads the related software and data configuration file under
the fixed directory structure from the USB stick and verifies their names and formats:
NodeBsoftware: \\NodeB\Software\Software.csp
BootROM: \\NodeB\Software\Firmware.csp
Data configuration file: \\NodeB\Configuration\NodeBCfg.xml
Downloading the Software and Data Configuration File
1. Connect the USB Memory stick provided by Huawei to the USB port on the
BBU3900 (do not use the test port). If the USB Memory stick is detected
correctly the following should happen within 20 seconds: the LED on the USB
disk is blinking; the RUN LED on the WMPT is blinking quickly (On for 1s, OFF
for 1s) about 2 seconds, ALM LED on WMPT is “ON” since the hardware is
different with the default scripts; CPRI LED on WBBPb are “OFF”.
2. Once the downloading of the software and configuration to the DBS3900

begins the following should be occurring: the LED on the USB disk is blinking,
the RUN LED on the WMPT blinks quickly at 4 Hz(0.125s ON, 0.125s OFF)
configuration file, it will last about 15 minutes.
RUN LED Blinking (ON
ALM LED
“ON” WMPT
3. The software is automatically activated on the DBS3900 when this happens

the RUN LED on WMPT blinks at 4Hz (ON for 0.125s, OFF for 0.125s) the
USB LED remains solidly “ON”. It will take about 10 minutes to activate the
software.
4. The DBS3900 will carry out a reset after the software and the data
configuration has been activated. During this process the LED on the USB will
transition from ON->OFF->Blinking; the RUN LED on WMPT transitions:
ON->OFF->Blinking (ON for 0.125s, OFF for 0.125s); RUN LED on the 2
WBBPb will blink respectively; CPRI LED on WBBPb will flash once “RED”
and then become “Green”. The full reset will take about 5 minutes.
5. After the reset is complete, DBS3900 runs normally, the status should now be:
LED on USB is “OFF”; RUN LED on WMPT blinks (ON for 1s, OFF for 1s);
ALM LED on WMPT stays “OFF” (If there are no alarms); RUN LED on
WBBPb blinks (ON for 1s, OFF for 1s);CPRI LED on WBBPb stays “GREEN”

10.1.1 USB Commissioning Summary

Procedure LED on the USB RUN LED on the WMPT During
disk Time
Detecting USB disk ON Blinking (ON for 1s, OFF for 1s) about 2sec
Downloading the Blinking Blinking (ON for 0.125s, OFF for about
software and the 0.125s) 15min
data configuration
file from the USB
disk
Activating the ON Blinking (ON for 0.125s, OFF for about
software 0.125s) 10min
Resetting NodeB ON->OFF- ON->OFF->Blinking(ON for 0.125s, about 5min
>Blinking OFF for 0.125s)
NodeB Running Software Level Blinking (ON for 1s, OFF for 1s) –
Dependant
10.1.2 USB LED Status dependant on software

Software Level USB LED Status when NodeB is
running
C01B051 OFF
C01B052 OFF
C01B053 ON
Note: WMPT always blinks slowly (ON for 1s, OFF for 1s) in 30 seconds, please plug
it again.

10.2 Commissioning using LMT
10.2.1 Connecting to the NodeB

1. Connect laptop and NodeB with a Fast Ethernet cable.
Connect
2. Set the IP address for laptop. You can log in to the NodeB on the LMT only
when the IP address of the LMT PC is correctly set. For local maintenance on
the LMT, the IP addresses of the LMT PC and the NodeB local maintenance
channel stay within the same network segment. You need set IP Address is
17.21.2.33 and mask is 255.255.0.0 in your laptop.
3. Click the “Local maintenance Terminal” in start menu to start LMT.
4. Click the […] button on the Office row.

5. Click Add and Fill the table. The Office name is NODEB, the IP Address is
17.21.2.15 and the NE type is NodeB then click [Close].
6. Input the User Name: admin Password: NodeB. Click the “Login”
7. Once you are logged in successfully you should see the following.

10.2.2 Upgrading the BOOTROM

1. Select the Maintenance tab and choose Service > Software Management.
Then double-click Software Update.
2. The Software Update dialog box is now displayed, select Upgrade BOOTROM
and click [Next].

3. The Upgrade BOOTROM dialog box is now displayed, select [Download

BOOTROM Package] and [Activate BOOTROM], then use the [Browse] button
to located the NodeB BOOTROM software on your hard disk. Once this is all
complete click [Next].
10.2.3 Upgrading the NodeB software
Note: NodeB Bootrom must be upgraded before upgrading NodeB Software; the
reversed procedure may cause the NodeB breakdown.
Then double-click Software Update, as before.
2. The Software Update dialog box is now displayed, this time select Upgrade
NodeB Software and click [Next]

3. The Upgrade NodeB software dialog box will not be displayed. Select
[Download NodeB Software Package], [Download By Configuration] and
[Activate NodeB Software] and then use the [Browse] button to set the location
of the NodeB Software Package, then click the [Next] button.
After the upgrade the software is complete, system will automatically reset
NodeB, this will take about 5 minutes.

10.2.4 Upgrading the Configuration File

Then double-click Data Config File Transfer. The following dialog box will then
be displayed. Select the [Download (FTP Server to NodeB)] option.
Use the [Browse] button to set the location of the configuration file
(NodeBCfg.xml) and click [Start].
2. Once the progress bar reaches 100% click [Close]. Go to the MML command
window for the NodeB and type the command ‘RST NODEB”. Once the
NodeB has reset the new configuration will take effect. Please wait 5-10
minutes.
10.3 Additional Commissioning Tasks
10.3.1 RUN ‘extra command’ sent by Huawei

From LMT, ‘system’/‘Batch Commands’/

Then open the ‘extra command’ file on your hard disk. Excution type is ‘All’
and don’t select the ‘prompt when error occurs.
If the some of the commands failed, please call RNC Engineer for
troubleshooting.
To finalize the commissioning of the NodeB and make it ready for call testing it is
necessary to notify the RNC engineer that the software upgrade and the
commissioning is complete. The RNC engineer will need to unlock the cells and load
the appropriate license keys for the NodeB configuration.
11. System Checking

After the commissioning of the NodeB is complete it is necessary to verify that the
NodeB software and BOOTROM levels are correct and that the configuration file as
loaded correctly in the NodeB. The following section describes the checks required.
11.1 Checking Software and BOOTROM Level

1. Login to the NodeB by LMT.
2. Open a MML Command window and use the following commands to list the
software and BOOTROM version for all units present in the NodeB:
“LST VER”
“LST SOFTWARE”
Pleae make sure the version is V200R010C01B053 and then you can make
callp. If it is not the right version, please do Item 10 Local Commissioning
again.
Log the results of the commands to a file and name it <Site
ID>_<SW_Version.txt>. This file will become part of the site
documentation package.
11.2 LED Status

After the activation of the software and the configuration the NodeB should be in a
normal run mode, check the LED status to verify the run state of the NodeB.
LED LED Status Comments

WMPT Run LED Blinking (ON for 1s, OFF
for 1s)
WMPT Alarm OFF Unless alarms are present
LED
WMPT Act LED ON
WBBPb Run LED Blinking (ON for 1s, OFF
for 1s)
WBBPb Alarm OFF Unless alarms are present
LED
WBBPb Act ON
CPRI LED ON OFF if not configured, RED is RRU
is not seen
11.3 Local Cell Status

Once the RNC engineer has loaded the appropriate license keys and unlocked the
cells the local engineer can check the cell status using the command DSP LOCELL:;
log the output to the file <Site ID>_Locell_Status.txt this will form part of the site
documentation to be submitted.
11.4 Cell Configuration

If the local cell is available and operational, check the cell status using the command
DSP CELLCFG: MODE=ALLCELL; log the output to the file <Site ID>_Cell_CFG.txt

this will form part of the site documentation to be submitted. Record the Primary
Scrambling Code for each cell in <Site ID>_CallP_Register.xls for Call_P test.
11.5 RRU Topology

Once finished software upgrade and local commissioning, select Maintenance tab on
LMT, and click RRU Physical Topology, to check the RRU topology if it’s consistent
with what NodeB configured, and snapshot the windows saved as file <Site
ID>_Topology.jpg, this will form part of the site documentation to be submitted.
11.6 Alarm Checks

Once the local cell status has been verified the local engineer will need to check the
alarms on the NodeB and snapshot the alarm window save as file <Site
ID>_Alarms.jpg. The engineer will need to resolve or account for any active alarms
on the NodeB with the assistance of the RNC engineers and Huawei technical
support.
11.7 Troubleshooting
For assistance in troubleshooting any problems that arise during the commissioning
of the NodeB the first point of contact will be the RNC engineer for the area. If the
RNC engineer is not able to provide the necessary support the local engineer will
need to contact Huawei technical support.

12. Cell Orientation

Prior to call testing it is necessary for the local engineer to verify that there are no
crossed fibers/feeders present in the configuration. To do this the engineer will need
to us a compass to find orientate the direction of the sectors and then verify the Cell
ID and scrambling codes for each antenna. The diagram below details the orientation
of the Antennas, the first sector (Alpha) is the one orientating to the north east, alone
the clockwise, are the second (Beta) and the third (Gamma) sector.
Alpha
Gamma
N
Beta
Once the cell orientation has been verified then call testing can begin. ( Telus has
some special sites, which are not defined like this, Huawei will provide a list of these
kind of sites)
13. Call P Testing
13.1 Call-P Procedure
Call P testing is to be carried out with co-ordination with the RNC Engineer; there are
3 sections to the Call P process, which are:
• Dedicated Call Tests

• Basic Service Tests
• Handover Tests
Please call RNC Engineer to check all cells are available. And then ask them to
block 800 Cells, you can make all the 1900 Calls and Handover

After you finish the 1900 call test, please call RNC Engineer to unblock 800 cells
and block 1900 cells, you can make 800 calls and Handover
After you finish the callp, please call RNC Engineer to unblock all cells and tell
them the Callp on site finished.
Record the all of the test results to <Site ID>_Telus_CallP Record after finished
each test.
PS: When you make the PS handover test, please remember to record the
average download speed to ‘Telus_CallP Record’ spreadsheet.
13.2 Dedicated Call Test (For you reference)

This section of call testing consists of a number of standard calls that test the routing
of calls between the site and fixed line numbers in both directions (only one of each
call is required per Site). Call tests should consist of the following:
• Mobile to Fix line using 11 digits (Local Site telephone can be used for this
purpose)
• Mobile to Fix line using 10 digits (Local Site telephone can be used for this
purpose)
• Fix line to Mobile using 11 digits (Local Site telephone can be used for this
purpose)
• Fix line to Mobile using 10 digits (Local Site telephone can be used for this
purpose)
13.3 Basic Service Tests and handover test (For you reference)
This section of call tests deals with testing the services on each cell of the Site, one of
each of the following tests is required in order to achieve a pass grade for the cells
(unless know conditions exist to prevent one or more of the tests, details of these
conditions must be detailed in the Call P documentation).
1. Call RNC Engineer to block all 850 cells. Then make Voice call and video call in
each 1900 cell. Make sure the PSC is right in each cell.
2. Make a call and walk around the site, to make sure there is no call drop. And then
reverse to make sure there is no call drop

3. 3. Call RNC Engineer to unblock 850 cells and block all 1900 Cells. Then make
Voice call and video call in each 850 cells. Make sure the PSC is right in each cell.
4. Make a PS download and walk around the site, to make sure there is no call drop.
And then reverse to make sure there is no call drop
• Voice call – to be held for 1 minute and checked for call quality.
• Video Call – to be held for 1 minute and checked for video and voice quality.
• HSPA data test
1. Initiate the internet connection and make sure connection is set up.
2. Login to site http://speedtest.net/, choose the city where the site
located and initiate the download test and upload test.
3. Check the download speed
4. Check the upload speed

13.4 Commissioning Report

Use Batch command tool to collect the commissioning information and send
back to Huawei.
Steps: 1. Open LMT: System/Batch Commands
2. Click ‘Open’ to find the ‘Data Scan_20090414_V3.txt’ file in the

‘Commissioning Report Tool’ file.
3. Click ‘ Set’ on LMT to set the save direction. Just select ‘Save
Successful Reaults’ and save to your folder.
4. Click ‘Go’ to run the scripts.

5. Go to the ‘Commissioning Report Tool’ folder to open the file ‘ATP

Data Sheet_scripted_V3.xls’ . Click ‘Get Data’, find the batch command result
just now you saved. And then you can get the values in this XLS file.
6. Save it and send all these three files to Huawei.
14. Compiling and Submitting the Site Documents
14.1 Contents of Site Documentation

There are several documents that form part of the site documentation, all of these
must be provided to Huawei at the completion of the site commissioning and call
testing. The following is a list of the information to keep, file convention and purpose
of each document
Item Folder/Naming Purpose

Convention
NodeB configuration //<Site Commissioning Data file provided to
ID>/Configuration/NodeBCf engineer to commission the site.
g.xml
Site Overview Photo //<Site ID>/Site Photo/<Site Provides a visual view of the installed
ID>_Overview.jpg equipment in the rack.
DCDU Audit Checklist //<Site ID>/HW Installation Confirms the audit results carried out
Check/<Site for the DCDU prior to commissioning of
ID>_DCDU_Checklist.doc the site.
DCDU Close Up Photo //<Site ID>/Site Photo/<Site Provides a close up view of the
ID>_DCDU.jpg installed DCDUs, to visually confirm
install.
BBU Audit Checklist //<Site ID>/HW Installation Confirms the audit results carried out
Check/<Site for the BBU prior to commissioning of
ID>_BBU_Checklist.doc the site.
BBU Serial Number //<Site ID>/HW Installation Provide the accurate BBU serial
Check/<Site ID>_BBU number for each sites.
SN_<Serial Number>.txt

BBU Close Up Photo //<Site ID>/Site Photo/<Site Provides a close up view of the
ID>_BBU.jpg installed BBU, to visually confirm install.
Power Cabling (PSU //<Site ID>/Site Photo <Site Provides a close up view of the power
end) ID>_PWR.jpg cabling to the PSU.
Site Software //<Site ID>/Commissioning Provides evidence of current software

versions Log/<Site and BootROM versions
ID>_SW_Version.txt
Local Cell Status //<Site ID>/Commissioning Provides evidence of Cell Status after
Log/<Site commissioning.
ID>_Localcell_Status.txt
Cell Configuration //<Site ID>/Commissioning Provides the cell configuration after the
Log/<Site ID>_ commissioning of the NodeB
Cells_Config.txt
Topology Snapshot //<Site ID>/Commissioning Provides a topological view of the

Log/<Site ID>_Topology.jpg NodeB after commissioning
Alarm Snapshot //<Site ID>/Commissioning Provides a snapshot of alarms present

Log/<Site ID>_Alarms.jpg on the NodeB after commissioning
Alarm Log //<Site ID>/Commissioning Provides a log of all of the full alarm
Log/<Site ID>_Alarms.csv information for the site in CSV format.
Call-p Result //<Site ID>/CallP Provides Call-p results of all the cells
Register/<Site for the site.
ID>_Telus_CallP Record
Commissioning //<Site ID>_Commissioning Include three files: ATP Data
Report Report Sheet_scripted_V3.xls,
BatchMML_Result.txt, Data Scan.txt
14.2 Submitting Documentation

Once finished the site commissioning and service test, complete the documents as
requested and keep them in the correct path accordingly as categorized in 14.1:
//<Site ID>/Configuration/

//<Site ID>/Site Photo/
//<Site ID>/HW Installation Check/
//<Site ID>/Commissioning Log/
//<Site ID>/Call_P Register/
// <Site ID>Commissioning Report
Each team leader should send out all these request files in 24 hours. after the
commissioning. Please send to Huawei Local PM, Site Technician and RNC
Engineer.
15 Handover Testing Guide

Handover tests are to be carried out under the direction of the RNC engineer as the
RNC engineer will need to monitor and feedback the current serving cells information
to the onsite engineer. Testing will differ slightly between S111 and S222 sites due to
the different in cells present on the site. The general concept of the handover testing

is to achieve intra-frequency (and in the case S222 sites inter-frequency) handovers

between adjacent cells on the site.
• Intra-Frequency Handover
S111:
1. [RNC engineer] Unblock the 3 cells of each sector.
2. [Site Engineer] Make sure mobile phone camp on the cell of sector Alpha,
originate a voice call to the 2nd mobile phone.
3. [Site Engineer] Hold on the call proceeding and move to the cell of sector Beta
and Gamma sequently in clockwise, then move to cell of sector Alpha.
4. [Site Engineer] Make sure the voice call is clear and without drop.
5. [Site Engineer] Hold on the call, move back to cell of sector Gamma and Beta
sequently in anti-clockwise, finally back to cell of sector Alpha.
7. [Site Engineer] Terminate the call and confirm with RNC engineer for the test
results.
8. [Site Engineer] Record the test results in callp register table.
step5 step3
S222:
1. [RNC engineer] Unblock the 3 cells of F1 (850MHZ) of each sector, block the
other 3 cells of F2 (1900MHZ).
2. [Site Engineer]Follow the step2~8 for S111 handover test.
3. [RNC engineer] Block the 3 cells of F1 (850MHZ) of each sector, unblock the
other 3 cells of F2 (1900MHZ).
4. [Site Engineer]Follow the step2~8 for S111 handover test.
• Inter-Frequency Handover (only for S222)

1. [RNC engineer] Unblock 850M cell (Alpha), 1900M cell (Beta) and
850M cell (Gamma).
2. [Site Engineer] Make sure mobile phone camp on the 850M cell (Alpha),
originate a voice call to the 2nd mobile phone.
3. [Site engineer] Hold on the call proceeding and move to the 1900M cell (Beta)
in clockwise.
5. [Site Engineer] Confirm with RNC engineer for the successful handover to
1900M cell (Beta) and move to 850M cell (Gamma).
6. [RNC Engineer] Block 850M cell (Alpha), unblock 1900M cell (Alpha).
850M cell (Gamma) and move to 1900M cell (Alpha).
8. [RNC Engineer] Block 1900M cell (Beta), unblock 850M cell (Beta).
1900M cell (Alpha) and move to 850M cell (Beta).
10. [RNC Engineer] Block 850M cell (Gamma), unblock 1900M cell (Gamma).
850M cell (Beta) and move to 1900M cell (Gamma).
1900M cell (Gamma) and move to 850M cell (Alpha).
850M cell (Alpha) and move back to1900M cell (Gamma) in anti-clockwise.
1900M cell (Gamma) and move to 850M cell (Beta) in anti-clockwise.
850M cell (Beta) and move to 1900M cell (Alpha) in anti-clockwise.
18. [RNC Engineer] Block 1900M cell (Gamma), unblock 850M cell (Gamma).
1900M cell (Alpha) and move to 850M cell (Gamma) in anti-clockwise.
20. [RNC Engineer] Block 850M cell (Beta), unblock 1900M cell (Beta).

850M cell (Gamma) and move to 1900M cell (Beta) in anti-clockwise.
1900M cell (Beta) and move to 850M cell (Alpha) in anti-clockwise.
850M cell (Alpha).
25. [Site Engineer] Terminate the call and confirm with RNC engineer for the test
results.
26. [Site Engineer] Record the test results in Callp register table.


Huawei DBS3900 Commissioning MOP - V1 - 2 20090515

Enviado por

Dados do documento

Descrição original:

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Huawei DBS3900 Commissioning MOP - V1 - 2 20090515

Enviado por

Direitos autorais:

Formatos disponíveis

Huawei DBS3900 Commissioning Procedure Security Level:

2009-05-15 HUAWEI Confidential Page1, Total30

2009-05-15 HUAWEI Confidential Page2, Total30

2009-05-15 HUAWEI Confidential Page3, Total30

1. Confirmed NTP report released, hardware installation completed, NodeB was

2009-05-15 HUAWEI Confidential Page4, Total30

6. Site Keys and Codes

• Sign out Telus Mobility key from Huawei Region PM.

• Approved footwear must be worn

7. Site Access Procedures

This procedure must happen all the time, every time.

8. Site Installation Checks

2009-05-15 HUAWEI Confidential Page5, Total30

DCDU. Please refer to the document: <Telus Checklist for Hardware

Both checklist need to be completed, photographs must be taken and submitted as

<Site ID>_<Equipment>_Photo.jpg (Overview, DCDU, BBU and Power)

9. BBU Serial Number

<Site ID>_BBU SN_<Serial Number>.txt

For example 21023156401000001572

2009-05-15 HUAWEI Confidential Page6, Total30

10. Local Commissioning

10.1 USB Commissioning

Downloading the Software and Data Configuration File

2. Once the downloading of the software and configuration to the DBS3900

RUN LED Blinking (ON

3. The software is automatically activated on the DBS3900 when this happens

2009-05-15 HUAWEI Confidential Page8, Total30

10.1.1 USB Commissioning Summary

10.1.2 USB LED Status dependant on software

2009-05-15 HUAWEI Confidential Page10, Total30

10.2 Commissioning using LMT

10.2.1 Connecting to the NodeB

3. Click the “Local maintenance Terminal” in start menu to start LMT.

4. Click the […] button on the Office row.

2009-05-15 HUAWEI Confidential Page11, Total30

2009-05-15 HUAWEI Confidential Page12, Total30

10.2.2 Upgrading the BOOTROM

2009-05-15 HUAWEI Confidential Page13, Total30

3. The Upgrade BOOTROM dialog box is now displayed, select [Download

10.2.3 Upgrading the NodeB software

2009-05-15 HUAWEI Confidential Page14, Total30

2009-05-15 HUAWEI Confidential Page15, Total30

10.2.4 Upgrading the Configuration File

10.3 Additional Commissioning Tasks

10.3.1 RUN ‘extra command’ sent by Huawei

2009-05-15 HUAWEI Confidential Page16, Total30

11. System Checking

11.1 Checking Software and BOOTROM Level

11.2 LED Status

LED LED Status Comments

11.3 Local Cell Status

11.4 Cell Configuration

2009-05-15 HUAWEI Confidential Page18, Total30

11.5 RRU Topology

11.6 Alarm Checks

2009-05-15 HUAWEI Confidential Page19, Total30

12. Cell Orientation

13. Call P Testing

13.1 Call-P Procedure

• Dedicated Call Tests

2009-05-15 HUAWEI Confidential Page20, Total30

13.2 Dedicated Call Test (For you reference)