omb221124 bts3900 wcdma v200r012 commissioning practice guide issue1.00

Revision RecordCourse Code Product Product

VersionCourse Version

ISSUE

BTS3900 V200R012 1.00

Developer/Modifier

Time Approver New/Update

Linzhihang 2010-8-30 New

BTS3900 WCDMA Commissioning

Practice Guide

BTS3900 WCDMA Commissioning Practice Guide

Contents

1 Remote Commissioning..................................................................11.1 Running the BSC LMT......................................................................................................................................11.2 Automatically Detecting the NodeB..................................................................................................................21.3 Creating a NodeB Commissioning Project on the M2000.................................................................................41.4 Obtaining the Commissioning Report of the NodeB Through the M2000........................................................61.5 Downloading and Commissioning the License on the M2000..........................................................................71.6 Checking the Running Status of the Base Station.............................................................................................8

1.6.1 Checking the Running Status of the NodeB on the M2000.....................................................................81.7 Commissioning the NodeB Services.................................................................................................................8

2 SMT/LMT + Remote Commissioning...............................................112.1 Running the NodeB LMT................................................................................................................................11

2.1.1 Setting the IP address of the LMT Client...............................................................................................112.1.2 Connecting the LMT Client and the Base Station..................................................................................132.1.3 Logging In to the LMT...........................................................................................................................13

2.2 Querying the Current Software Version of the NodeB....................................................................................142.3 Upgrading the NodeB Software.......................................................................................................................15

2.3.1 Downloading the BootROM Software of the NodeB.............................................................................152.3.2 Activating the BootROM Software of the NodeB..................................................................................182.3.3 Downloading NodeB Software...............................................................................................................202.3.4 Activating the NodeB Software..............................................................................................................23

2.4 Downloading the NodeB Data Configuration File..........................................................................................262.5 Checking the Running Status of the Base Station and Clearing the Alarms...................................................27

2.5.5 Checking the Running Status of the NodeB...........................................................................................272.5.6 Checking the NodeB Alarms..................................................................................................................29

2.6 Checking the VSWR of the NodeB.................................................................................................................30

3 Local USB + Remote Commissioning.............................................313.1 Preparation Before the Commissioning...........................................................................................................31

3.1.1 Arranging for Related Information and Tools Required for Base Station Commissioning....................313.1.2 Arranging for the Files in the USB Storage Device Required for the Base Station Commissioning.....32

3.2 Upgrading Software Through the USB Disk...................................................................................................333.2.1 Upgrading the NodeB Software and Downloading the Data Configuration File...................................33

Confidential Information of Huawei. No Spreading without Permission. i


4 Data Sheet for Commissioning......................................................354.1 Data Sheet for NodeB Commissioning............................................................................................................35

ii Confidential Information of Huawei. No Spreading without Permission


1 Remote Commissioning

1.1 Running the BSC LMTProcedure

Step 1 Choose Start > All Programs > Internet Explorer to start IE. Enter the external virtual IP address of the BSC6900 OMU in the IE Address box, and then press Enter.

Step 2 Enter the User Name , Password , Verify Code, and then click Login to enter the BSC6900 LMT interface.

Confidential Information of Huawei. No Spreading without Permission. 1


----End

1.2 Automatically Detecting the NodeBPrerequisite

You have logged in to the M2000 client successfully. The RNC is properly connected to the M2000 server. The NodeB mediation is installed on the M2000 server. The transmission links between the M2000 and the NodeBs function normally.

Context In actual situations, the NodeB OM channel supports IP, ATM, or both ATM/IP dual-

stack. When creating a NodeB in the ATM/IP dual-stack scenario, you can set two IP addresses. The primary address is the IP address of the ATM network and the secondary address is the IP address of the IP bearer network. Both the primary IP address and the secondary IP address must be different from the IP address of another NodeB, including the NodeBs that are on a different network. The network connection can be set up for the NodeB if either of the IP addresses is valid. After being disconnected from the network with an exception, the NodeB automatically uses the current IP address to reconnect to the network. If the attempt fails for five consecutive times, the NodeB uses the other IP address to connect to the network.

The IP address of the IP bearer network is dynamically assigned by the DHCP server. The Dynamic Host Configuration Protocol (DHCP) provides information such as the IP addresses to the Internet host on the TCP/IP network. The DHCP server can dynamically assign an IP address to the Internet host.

When the OM channel supports ATM, you can use ATM BOOTP to establish a remote OM channel.

2 Confidential Information of Huawei. No Spreading without Permission


The procedure of automatic NodeB detection is as follows:− The M2000 server obtains, from the database, the information about the NodeBs

managed by an RNC, such as the NodeB ID, NodeB name, and the IP address of the NodeB.

− The M2000 server obtains, from the DHCP server, the information about the NodeBs, such as the NodeB ID, NodeB name, and the IP address of the NodeB.

− The M2000 server compares the obtained information about the NodeBs according to NodeB IDs. If the information from the database is different from the information from the DHCP server, the data from the DHCP server prevails.

− Create a NodeB in the topology view and set up a connection between the NodeB and the M2000 server.

NodeBs may be reparented. However, the NodeBs that need to be deleted are not automatically deleted when they are automatically detected. Instead, they are displayed as disconnected. In this case, you need to determine whether the disconnected NodeBs need to be deleted, reparented, or reconnected.

ProcedureStep 1 Choose Topology > Main Topology. The Main Topology window is displayed.

Step 2 In the topology navigation tree or the topology view, right-click an RNC, and then choose Search NodeB from the shortcut menu. In the Main Topology window, the system automatically synchronizes the information about the NodeBs managed by a specific RNC, such as the total number of NodeBs managed by the RNC, number of NodeBs connected to



the M2000, number of NodeBs with identical names, and number of NodeBs with identical IP addresses.

----End

1.3 Creating a NodeB Commissioning Project on the M2000Prerequisite

The NodeB is properly connected to the M2000. The data configuration file of the NodeB to be commissioned is ready. The NodeB software and BootROM software are uploaded to the M2000 server.

ProcedureStep 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is

displayed.

Step 2 Click New. The – Please Select The NodeBs To Be Surveyed dialog box is displayed.



Step 3 Set Project Name and select the NodeBs that need to be commissioned.

Step 4 Click Next. The – Configuration Setting dialog box is displayed.

Step 5 In Operation Setting, select the commissioning items.

You can select all the operation items by selecting All.



Step 6 Set the BootROM version .

Step 7 Set the software version .

Step 8 Upload the data configuration file.

1. Click Upload new config file.2. In Choose Config File Directory, find the folder where the NodeB configuration files

are saved.

You need to save the NodeB configuration files in the folder named by the corresponding NodeB, and save the folder in client installation path. The default client installation path is \client\Data\NodeBSurvey\NodeBConfig.

You can upload the configuration files in batches. You can upload one or multiple NodeB configuration files to the server if you choose client

installation path.

3. Click Upload Config To Server.The NodeB configuration files in the specified save path are uploaded to the server.

Step 9 Click Finish.

----End

Postrequisite To view the commissioning progress of a NodeB commissioning task, see Viewing the

NodeB Commissioning Progress. To add or to delete the commissioning object in a commissioning project, see Adjusting

the Commissioning Object. To start or stop a commissioning task in a commissioning project, see Starting or

Stopping a NodeB Commissioning Task. To upload the NodeB data configuration files required by the ConfigFile Download

commissioning item again, see Re-Uploading the NodeB Configuration File.

1.4 Obtaining the Commissioning Report of the NodeB Through the M2000Prerequisite

Some NodeB commissioning tasks are created.

ProcedureStep 1 Choose Maintenance > NodeB Commissioning. The NodeB Commissioning dialog box is

displayed.

Step 2 In Projects, right-click the project whose NodeB commissioning report is required, and then choose Get Project Report from the shortcut menu. The browser automatically opens the commissioning report and displays the contents in the report.



----End

1.5 Downloading and Commissioning the License on the M2000Prerequisite

The eNodeB communicates properly with the M2000. The license is already obtained.

ProcedureStep 1 On the M2000 client, choose System > NE License Management. The NE License

Management window is displayed.

Step 2 In the navigation tree of NE License Management, choose NE License Management > NE License Maintenance.

Step 3 Click Load License File. The Load License File dialog box is displayed.

Step 4 Click to select the license to be downloaded.



Step 5 In the Load License File dialog box, click Next and then click Select to select the target NE that requires the license.

Step 6 In the Load License File dialog box, click Finish. The system starts to download the license to the target NE. Click NE License Maintenance in the navigation tree. The task list is displayed in the right area. You can check the execution status of the license downloading task.

----End

1.6 Checking the Running Status of the Base Station1.6.1 Checking the Running Status of the NodeB on the M2000Prerequisite

The status of the NodeB hardware is checked. The transmission links function normally. The currently running software version and the downloaded data configuration file are consistent with the actual requirements.

You have logged in to the M2000 client and created the NodeB commissioning project. The execution of the NodeB commissioning project is complete, and the NodeB commissioning report is obtained.

ProcedureStep 1 Open the NodeB commissioning report and view the contents to check the running status of

the NodeB.

Step 2 Handle the active alarms based on the commissioning report.

If... Then...

An alarm is generated Handle the alarm according to the NodeB Alarm Reference.

An active alarm cannot be cleared Record it in Data Sheet for NodeB Commissioning.

----End



1.7 Commissioning the NodeB ServicesPrerequisite

Two test UEs equipped with USIM cards are available. The USIM information of the two test UEs has been registered in the HLR. The RNC runs properly. The circuit switched (CS) and packet switched (PS) domains in the core network (CN)

work properly. All the logical cells of the NodeB on the RNC side are normal. You can check the status

of the logical cells by using the DSP CELL command on the RNC side.

Procedure Commissioning voice services

Testing Method Result

Make a call from a UE to a PSTN user.

Make a call from a PSTN user to a UE.

Make a call from UE 1 to UE 2.

Commissioning CS streaming services


Originate the video service from UE 1 to UE 2.

Commissioning PS services


Activate data services on a UE and browse web pages.

----End



2 SMT/LMT + Remote Commissioning

2.1 Running the NodeB LMT2.1.1 Setting the IP address of the LMT Client

This section describes how to set the IP address of the LMT client. You must set a correct IP address of the LMT client before logging in to the LMT. The following procedure is performed on the Windows XP system.

PrerequisiteThe TCP/IP protocol is installed on the LMT client.

ContextIn remote maintenance mode, you need ; IP 1, and IP 2. IP 1 stands for the IP address of the LMT client. IP 2 stands for the external IP address of the entity directly connected to the LAN where the LMT client is located, for example, the external IP address of the RNC BAM. IP 1 and IP 2 must be on the same network segment, as shown in Figure 6-34.

Figure 1-1 IP addresses in remote maintenance mode



Ensure that the IP address of the LMT client does not conflict with the IP address of another computer within the same LAN.

ProcedureStep 1 On Windows XP, choose Start > Control Panel.

If... Then...

The control panel is displayed in category view

Go to Step 2.

The control panel is displayed in classic view

Go to Step 3.

Step 2 Click Network and Internet Connections, and then go to Step 3.

Step 3 Double-click Network Connections. The Network Connections dialog box is displayed. Right-click Local Area Connection.

Step 4 Choose Properties from the shortcut menu. The Local Area Connection Properties dialog box is displayed.

Step 5 Select Internet Protocol (TCP/IP).

Step 6 Click Properties. The Internet Protocol (TCP/IP) Properties dialog box is displayed.

Step 7 Select Use the following IP address.

Step 8 Set the IP address, subnet mask, and default gateway of the LMT client. For details, see Table 6-4.

Table 1-1 IP parameters of the LMT client for commissioning on the NodeB side

Parameter Description

IP Address The IP address of the LMT client is on the same network segment as the IP address of the NodeB local maintenance channel.In local maintenance mode, the IP address of the NodeB is 17.21.2.15 by default.

Subnet Mask The subnet mask of the LMT client is the same as that of the NodeB local maintenance channel.

Default Gateway

The IP addresses on the same network segment correspond to the same subnet masks and subnet addresses (subnet mask AND IP address).



Step 9 Click OK to complete the settings.

----End

2.1.2 Connecting the LMT Client and the Base StationProcedure

Step 1 On the LMT client, choose Start > Run, and then run the cmd command. The command window is displayed.

Step 2 Run the ROUTE ADD Networkaddress MASK netmask gatewayaddress command in the command window to add a route from the PC to the gateway. Then, set "Networkaddress", "netmask", and "gatewayaddress". For details, see Table 6-5.

Table 1-1 Parameters for setting the route from the PC to the gateway

Parameter Description

Networkaddress OM IP address of the NodeB.

netmask Subnet mask of the PC is the same as the external subnet mask of the RNC BAM.

gatewayaddress External IP address of the BAM.

Different devices must correspond to different IP addresses. The IP addresses on the same network segment correspond to the same subnet masks and subnet

addresses (subnet mask AND IP address).

Step 3 Run ping target_name -t in the command window to check the connection between the LMT client and the NodeB. "target_name" is the OM IP address of the base station.

----End

2.1.3 Logging In to the LMTProcedure

Step 1 Choose Start > All Programs > HUAWEI Local Maintenance Terminal. If the Local

Maintenance Terminal is started, choose System > Logout, or click . The User Login dialog box is displayed.



Figure 1-1 User Login dialog box

Field Description

User Name Type the user name of the NodeB. By default, the user name is admin. The user name is mandatory and case-sensitive.

Password Password of the NodeB. By default, the password is NodeB. The password consists of 6 to 16 alphanumeric and case-sensitive characters.

Office Select the name and IP address of the LMT client that is connected to the NodeB. Click

to edit the office information. When you log in to the NodeB locally through the LMT, the IP address of the office is the same as the IP address of the NodeB local maintenance channel.

Proxy Server Leave this field blank. Ensure that you do not select the check box.

Step 2 In the Office area, set IP Address and Office.

Step 3 Type the user name and password in corresponding text boxes.

Step 4 Click Login to log in to the NodeB.



2.2 Querying the Current Software Version of the NodeB

This section describes how to query the current version of the NodeB. Before upgrading the NodeB software, you should query the information of the active software version.

ProcedureStep 1 Run the LST SOFTWARE command to query the NodeB software version and NodeB

BootROM version.

----End

2.3 Upgrading the NodeB Software2.3.1 Downloading the BootROM Software of the NodeBPrerequisite

The FTP server functions properly and is connected to the NodeB in the same Intranet. There is no firewall between the FTP server and the NodeB. The FTP user can access the specified directory.

ProcedureStep 1 Click the Maintenance tab in the navigation tree.

Step 2 Choose Software Management > Software Update. The Software Update dialog box is displayed.



Step 3 Select Upgrade BOOTROM in the dialog box.

Step 4 Click Next. The Upgrade BOOTROM dialog box is displayed.



The system downloads the BootROM package and then activates it. You can choose one step each time and the system proceeds with the task that you choose.

Step 5 Click Modify. The FTP Setting dialog box is displayed.

.

Field Description

Use Built-in FTP Server This enables you to decide whether to use a built-in or a specified FTP server. The built-in FTP server is selected by default.



Field Description

Use Specified FTP Server

IP Address The local computer installed with the LMT application can serve as the FTP server or any other computer can serve as the FTP server. Here, the IP address refers to the IP address of the FTP server.

User Name

This specifies the user name for logging in to the FTP server.

Password This specifies the password for logging in to the FTP server.

Step 6 Set the FTP server.

Step 7 Click OK. The FTP Setting dialog box is closed and the Upgrade BOOTROM dialog box is displayed.

Step 8 Select Download BOOTROM Package, and then specify a path to save the BootROM package.

Step 9 Click Next. A confirmation dialog box is displayed.

Step 10 Click Yes. A dialog box is displayed, indicating the status and the progress of the procedure.

----End

2.3.2 Activating the BootROM Software of the NodeBContext

Before the activation, the system checks the BootROM versions of the boards. The system activates the BootROM loaded to a board only when there is a new BootROM version.

Because the BootROM software does not affect the NodeB services, you need not manually reset the NodeB to activate the BootROM. The NodeB starts with the upgraded BootROM next time you reset the NodeB.

After the BootROM is activated, the NodeB is not reset.





Step 3 Select Upgrade BOOTROM in the dialog box.

Step 4 Click Next. The Upgrade BOOTROM dialog box is displayed.



The system downloads the BootROM package and then activates it. You can choose one step each time and the system proceeds with the task that you choose.

Step 5 Select Activate BOOTROM.



----End

2.3.3 Downloading NodeB SoftwarePrerequisite

The FTP server functions properly and is connected to the NodeB in the same Intranet. There is no firewall between the FTP server and the NodeB. The FTP user can access the specified directory.





Step 3 Select Upgrade NodeB Software in the dialog box.

Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed.



Step 5 Set the FTP server.

Step 6 Click OK. The FTP Setting dialog box is closed and the Upgrade NodeB Software dialog box is displayed.



Step 7 Select Backup Data Configuration File to specify a directory for backing up the file, and then select Download NodeB Software Package and Download by Configuration to specify a directory for downloading the NodeB software package.

Backup Data Configuration File is optional. It is recommended that you select the file. When the initial configuration and the configuration need be changed or the configuration data in the

file is incorrect, click Download Data Configuration File to download the data configuration file again. Click Effective Data Configuration File to ensure that the configuration file takes effect before you activate the NodeB software.

It is recommended that you select Download by Configuration. If it is not selected, a dialog box is displayed to prompt that this may cause the software download failure. Click OK to start the download of the software. Click Cancel to select again, and download the software by configuration.

If you select Download by Configuration, the NodeB selectively downloads required board software packages from the relay server according to the configured board type. In this manner, the total amount of data to be downloaded is reduced, thus reducing download time and saving storage space.



----End

2.3.4 Activating the NodeB SoftwareThis section describes how to switch the standby directory to the active one, download the NodeB software to boards and then activate it. You can activate the NodeB software immediately after or later than the downloading. After the activation, the NodeB is reset and all the services are disrupted.


Step 2 Choose Software Management > Software Update. The Software Update dialog box is displayed, as shown in Figure 6-45.



Figure 1-1 Software Update dialog box

Step 3 Select Upgrade NodeB Software in the dialog box.

Step 4 Click Next. The Upgrade NodeB Software dialog box is displayed, as shown in Figure 6-46.



Figure 1-1 Upgrade NodeB Software dialog box

Step 5 Select Activate NodeB Software, and then from the Version drop-down list, select the NodeB software version to be upgraded.

The Version drop-down list is displayed only when Download NodeB Software is not selected. When the initial configuration and the configuration need be changed or the configuration data in the

file is incorrect, click Download Data Configuration File to download the data configuration file again. Click Effective Data Configuration File to ensure that the configuration file takes effect before you activate the NodeB software.





The NodeB is automatically reset, and the new version of the NodeB software is enabled after the activation.

If the software activation fails, the NodeB software cannot operate properly. You need reactivate the NodeB software in the standby file directory or reinstall the NodeB software.

----End

2.4 Downloading the NodeB Data Configuration File

This section practice how to download the NodeB data configuration file from the FTP server to the NodeB. The new NodeB data configuration file takes effect after the NodeB is reset.

Procedure In GUI mode1. Click the Maintenance tab in the navigation tree.2. Choose Software Management > Data Config File Transfer. The DataConfig File

Transfer dialog box is displayed.

3. Select Download (FTP Server to NodeB).



4. Click Modify. The FTP Setting dialog box is displayed.

5. Set the FTP server.6. Click OK. The FTP Setting dialog box is closed and the DataConfig File Transfer

dialog box is displayed.7. Set the other parameters in the dialog box.8. Click Start. In MML mode

Run the DLD CFGFILE command. The configuration file takes effect after the base station is manually reset.

----End

2.5 Checking the Running Status of the Base Station and Clearing the Alarms2.5.1 Checking the Running Status of the NodeBProcedure

Step 1 Check the running status of the current cell so that you can perform proper operations. Run the DSP LOCELL command to check the status of all local and logical cells of the NodeB.

Option Description

If... Then...

The information prompting faults is displayed

Rectify the faults according to the information.

No information prompting faults is displayed

End the task.

Step 2 Measure Received Total Wideband Power (RTWP) to calibrate the uplink RF channel. The RTWP measurement does not disrupt services.

1. On the Local Maintenance Terminal, click the Maintenance tab.



2. Double-click Realtime Specific Monitoring > RTWP Measurement. The RTWP Measurement dialog box is displayed.

3. Set the parameters in the dialog box.4. Click OK. A window is displayed, showing the graph of the current monitoring task.

RTWP: dBm5. Stop the task with one of the following methods:

Close the task monitoring window and stop all monitoring tasks displayed in the active window. Right-click the task in the task list, and then choose Delete Task from the shortcut menu. The curve

displayed with the task is also deleted.

Analysis of the RTWP measurement is as follows: If the NodeB is not connected to the antenna system or a matching load, the reported RTWP is about

-108 dBm. If the NodeB is connected to the antenna system with the TMA started or a matching load, the reported RTWP is about -105 dBm.

If the services are normal and the uplink load reaches 75%, the RTWP is 6 dB higher than the RTWP when the NodeB does not carry any service.

Step 3 Monitor the output power of the NodeB. On the LMT, you can view the typical output power and output power of each carrier.

1. On the Local Maintenance Terminal, click the Maintenance tab.2. Double-click Realtime Specific Monitoring > Output Power Monitoring.



3. Set the parameters in the dialog box.4. Click OK. A window is displayed, showing the graph of the current monitoring task. Output Power: dBm5. Stop the task with one of the following methods:

Close the task monitoring window and stop all monitoring tasks displayed in the active window. Right-click the task in the task list, and then choose Delete Task from the shortcut menu. The curve

displayed with the task is also deleted.

If the pilot power and typical output power are configured, the output power of the WRFU is similar to the pilot power and the output power of the RRU is about 3 dBm greater than the pilot power when the NodeB does not carry services. If the output power is considerably lower than the pilot power, the output power of the NodeB is abnormal.

----End

2.5.2 Checking the NodeB AlarmsProcedure

Step 1 Run the LST ALMAF command to query the active alarms.

Step 2 Handle the NodeB alarms.

If... Then...

Active NodeB alarms exist Clear the alarms according to the alarm online help.

Active alarms cannot be cleared Record them in Data Sheet for NodeB Commissioning.

----End



2.6 Checking the VSWR of the NodeBThis section describes how to check the Voltage Standing Wave Ratio (VSWR). The VSWR is used to verify whether the antenna system is correctly installed. You can check the VSWR through the M2000 in a centralized manner.

Prerequisite The configuration of the NodeB is complete, and the transmission is available. The NodeB fails to provide the services or the services are isolated.

ContextAn excessively large VSWR results in short transmission distance and may burn down the power amplifier, thus affecting the normal operation of the communication system. The normal VSWR range is between 1 and 1.5.

During testing of the VSWR, the services of the NodeB are interrupted. Therefore, you are advised to test the VSWR when the traffic is light or after the NodeB services are isolated.

ProcedureStep 1 Choose Maintenance > Standing Wave Ratio Test > Standing Wave Ratio Test. The

Standing Wave Ratio Test tab page is displayed.

Step 2 In the navigation tree on the left pane of the Standing Wave Ratio Test tab page, select one or multiple NodeBs to be tested.

Step 3 Click Query. Then in the displayed dialog box, click Yes.

The system prompts: VSWR query will impact the system service greatly! Please confirm to continue or not.

Step 4 View the check results.

1. During the check, the system displays the check progress in the VSWR Query dialog box. Click Detail to see the detailed information about the check progress.

2. When the progress reaches 100%, click close to close the VSWR Query dialog box. Then, the check results are displayed on the Query Result tab page.

----End



3 Local USB + Remote Commissioning

3.1 Preparation Before the Commissioning3.1.1 Arranging for Related Information and Tools Required for Base Station Commissioning

Before the local base station commissioning through the USB disk, you need to arrange for the related base station information and tools.

ProcedureStep 1 Collect the information related to the base station, as described in Table below.

Item Source or Remarks

Base station name Planned by the operator.

Base station ID Planned by the operator.

Base station ESN ESN identifies an NE uniquely. During network deployment, the installation engineer reports the mapping relation between the location of each site and the ESN. Before delivery, the ESN is attached to the BBU of the base station, as shown in Figure below.



Step 2 Obtain the tools required for the local commissioning through the USB disk, as described in Table below.

Tool Description

USB disk The USB disk is equipped with an LED that indicates the data transmission status.

Capacity ≥ 256 MBYou should test the USB disk before using it. Do as follows to test the USB disk: Insert the USB connector into any functional USB port on the base station, and wait 3 seconds. If the LED on the USB disk has blinked once, it indicates that the USB disk is functional. Otherwise, change the USB disk.Recommended model: Netac U208 The USB disk has no additional function, which includes

but is not limited to encryption, antivirus, bootstrap, MP3, MP4, and smart mobile phone.

Test UE The test UE is functional and is registered in the HSS.

----End

3.1.2 Arranging for the Files in the USB Storage Device Required for the Base Station Commissioning

Before the local commissioning through the USB disk, you need to save the required files in a specified directory of the USB disk.

Prerequisite The USB disk is ready. The software and data configuration file are available.



Procedure Saving the NodeB software package and data configuration script in the specified path

under the USB device

File Specified Path of the USB Storage Device

NodeB software package usb:/NodeB/Software/Software.csp

Data configuration script usb:/NodeB/Configuration/NodeBCfg.xml

----End

3.2 Upgrading Software Through the USB Disk3.2.1 Upgrading the NodeB Software and Downloading the Data Configuration File

This section describes how to commission the NodeB through the USB disk. The NodeB supports to upgrade the software and download the data configuration file directly from the USB disk. After the files are downloaded, the NodeB automatically activates the software and data configuration file. Then, the NodeB is reset.

PrerequisiteThe USB disk is ready for use, and the required files are saved in the USB disk..

ContextWhen the USB connector is inserted into the corresponding port on the WMPT of the NodeB, the BBU3900 automatically detects the USB disk and installs the USB disk driver. After the installation is complete, the NodeB automatically reads the related software and data configuration file under the fixed directory and verifies their names and formats.

You should pay attention to the following situations when you upgrade the software and download the data configuration file from the USB disk:

If only the software is saved in the USB disk, the NodeB automatically upgrades the software.

If only the data configuration file is saved in the USB disk, the NodeB automatically downloads the data configuration file.

In any of the following situations, the NodeB does not upgrade the software or download the data configuration file from the USB disk.− The directory or the file does not exist.− The file format is illegal.− The software version to be used is the same as the current software version.− The data to be used in the configuration file is the same as the current configuration

data.

ProcedureStep 1 Insert the USB connector into the USB port on the WMPT of the BBU3900.



Step 2 The NodeB automatically downloads the software and data configuration file, and activates the software. After the sofware is activated, the NodeB is reset. Table below describes the state of the LED on the USB disk and the RUN LED on the WMPT in this step.

Software Upgrade

State of the LED on the USB Disk

State of the RUN LED on the WMPT

Duration

When the USB connector is inserted into the corresponding port on the WMPT, the WMPT automatically detects the USB disk.

ON Blinking (ON for 1s and OFF for 1s)

About 1 second to 2 seconds

The WMPT downloads the software and data configuration file from the USB disk.

Blinking Blinking (ON for 0.125s and OFF for 0.125s)

About 14 minutes

Activating the Software

ON Blinking (ON for 0.125s and OFF for 0.125s)

About 4 minutes to 5 minutes

The NodeB is reset. ON first, OFF for a while, and then blinking

ON first, OFF for a while, and then blinking (ON for 0.125s and OFF for 0.125s)

About 2 minutes

NodeB is running properly.

ON Blinking (ON for 1s and OFF for 1s)

-

The time to download the software and data configuration file and the time for the NodeB to activate the software vary according to the version and configuration. That is, the actual period of time required may slightly differ from that described in Table. The whole process (involving software and data configuration file downloading, and software activation) takes about 20 minutes.

Step 3 After all the commissioning operations such as upgrading the software, downloading the data configuration file, checking the GBTS hardware status, and troubleshooting are complete, remove the USB disk.

----End



4 Data Sheet for Commissioning

4.1 Data Sheet for NodeB CommissioningThis section provides the data sheet that is used to record the process and results of the NodeB commissioning

Table 1-1 Data sheet for NodeB commissioning

Site Name

NodeB Type

Commission Time

Commissioning Engineer

Commissioning Mode

□ Local USB + remote commissioning □ SMT/LMT + remote commissioning □ Remote commissioning

Commissioning Result

□ Successful □ Failed

Commissioning Item Conclusion Handling Exceptional Case

Commissioning Preparation Phase

Faults in the NodeB hardware installation are rectified.

□ Yes; □ No

Transmission links between the NodeB and RNC are ready.

□ Yes; □ No

Negotiation data of the NodeB to be commissioned is added to the RNC.

□ Yes; □ No

Commission Local The NodeB is upgraded. □ Yes; □ No



ing Phase Commissioning through USB

The NodeB hardware is functional.

□ Yes; □ No

SMT/LMT Commissioning

The NodeB software and BootROM software are upgraded through the LMT.

□ Yes; □ No

The data configuration file of the NodeB is downloaded from the LMT.

□ Yes; □ No

The NodeB hardware status is checked.

□ Yes; □ No

Remote Commissioning

The UMTS transmission is normal.

□ Yes; □ No

The commissioning project of the NodeB is created.

□ Yes; □ No

The commissioning report of the NodeB is obtained.

□ Yes; □ No

The NodeB hardware status is checked.

□ Yes; □ No

The NodeB services are commissioned.

□ Yes; □ No

The NodeB environment alarms are commissioned.

□ Yes; □ No

Problem Description Impact

Unsolved Problems After Commissioning

Component P/N

Faulty Board Record


omb221124 bts3900 wcdma v200r012 commissioning practice guide issue1.00

Documents