2. Owb201800 Bts3900 Wcdma v200r015 Comisionamiento Issue 1.

NodeB WCDMA V200R015 Commissioning

Confidential Information of Huawei. No Spreading Without Permission

N-1



N-2



P-3

BTS3900 WCDMA V200R014 Local Commissioning



P-4

Basic Modules  The 3900 series base stations have a modular structure.  The basic modules of the 3900 series base stations are the Base Band Unit (BBU), Radio Frequency Unit (RFU), and Remote Radio Unit (RRU). To meet the requirements for radio network deployment, the BBU and RFU/RRU are connected through a CPRI port that uses an electrical or optical cable to transmit CPRI signals.




P-5










P-6

Transport subsystem:  Provides ports for communication between the base station and the RNC.  Provides the OM channel for connection to the LMT or M2000. Baseband subsystem: The baseband subsystem processes UL and DL baseband signals. This subsystem consists of the following modules:  UL baseband processing module: consists of the demodulation unit and the decoding unit. The module processes the UL baseband data before transmitting the data to the RNC through the transport subsystem.  DL baseband processing module: consists of the modulation unit and the coding unit. The module processes the data from the transport subsystem and then transmits the data to the interface module. Control subsystem: The control subsystem performs centralized management of the entire base station in terms of OM and signaling processing and provides the system clock.  The OM functions involve equipment management, configuration management, alarm management, software management, and commissioning management.  The signaling processing functions involve NodeB Application Part (NBAP) signaling processing, Access Link Control Application Part (ALCAP) processing, Stream Control Transmission Protocol (SCTP) processing, and logical resource management.  The clock module supports the line clock, GPS clock, or free-run clock, generates a synchronization clock for the entire base station, and provides the system clock required by the base station. Power module:  The module converts the -48 V DC or +24 V DC power into the power required by the boards.  The module collects various types of Boolean alarm information, and reports the information to the control subsystem. Confidential Information of Huawei. No Spreading Without Permission






P-7

The Universal Main Processing & Transmission unit (UMPT) processes signals and manages resources on other boards in the BBU3900. The UMPT is classified into two types: UMPTa1 and UMPTa2. The UMPTa1 is only used for UMTS mode.







P-8

The Universal Main Processing & Transmission unit (UMPT) processes signals and manages resources on other boards in the BBU3900. The UMPT is classified into two types: UMPTa1 and UMPTa2. The UMPTa1 is only used for UMTS mode.









P-9

GTMU: The GTMU is the main control and transmission board of the BBU3900 working in GSM mode. It has the following functions:  Provides the CPRI ports for connecting to the RF modules.  Processes clock signals and provides a unified clock for service boards in GSM mode.  Provides OM management for the GSM network.  Provides four E1s/T1s, one FE electrical port, and one FE optical port. WMPT: The WMPT is the main control and transmission board of the BBU3900 working in UMTS mode. It has the following functions:  Processes clock signals and provides a unified clock for service boards in UMTS mode.  Provides OM management for the UMTS network.  Provides four E1s/T1s, one FE electrical port, and one FE optical port.  Provides one USB port to download and activate the host software by using a USB disk.  Processes signaling and manages resources.  In UMTS mode, the WMPT supports the 1 + 1 redundancy mode. LMPT: The WMPT is the main control and transmission board of the BBU3900 working in LTE mode. It has the following functions:  Enabling configuration management, device management, performance monitoring, signaling processing, and radio source management.  Enabling control for the boards in the system.  Providing the system clock.  Enabling signal exchange between the eNodeB and MME/S-GW.





  

 

N-10

Provides Operation and Maintenance (OM) functions such as configuration management, equipment management, performance monitoring, signaling processing, and active/standby switchover and provides OM channels connected to the OMC (LMT or M2000) Provides the reference clock Processes signaling and manages resources for other boards in the BBU3900 Provides USB ports, one of which facilitates automatic base station upgraded when a USB disk is inserted during software installation and data configuration Provides four E1s/T1s which support ATM and IP protocols Provides one FE electrical port and one FE optical port which support the IP protocol




N-11



N-12




  



N-13

The WBBP has the following functions: Provides the CPRI interface for communication between the BBU and the RRU or RFU, and supports the CPRI interface in 1+1 backup mode. Processes uplink and downlink baseband signals. The WBBPd supports interference cancellation (IC) within the board. When installed in slot 2 or slot 3, the WBBPd supports the IC function of uplink data. WBBP: The WBBP is the baseband processing unit in UMTS mode, and it has the following functions:  Provides CPRI ports for connection to RF modules.  Processes uplink and downlink baseband signals.




N-14



N-15












 



N-16

Módulo de Transporte Síncrono (Synchronous Transport Module). Unidad de transmisión básica de la Jerarquía Digital Síncrona (SDH), correspondiente al primer nivel básico The Universal Transmission Processing unit (UTRP) is the transmission extension board of the BBU3900. It provides eight E1s/T1s, one unchannelized STM-1/OC-3 port, and four electrical ports or two optical ports. . The UTRP2 provides two 100M/1000M Ethernet optical ports, performs functions of the MAC layer, receives and transmits data on Ethernet links, and analyzes the MAC address. The UTRP3 provides eight E1s/T1s and performs inverse multiplexing and demultiplexing on a single ATM cell flow on the eight E1/T1 links. The UTRP4 provides eight E1s/T1s, frames and deframes HDLC frames, and allocates and controls the 256 HDLC timeslot channels. The UTRP6 supports one unchannelized STM-1/OC-3 port. The UTRP9 provides four 10M/100M/1000M Ethernet electrical ports and performs the functions of the MAC layer and physical layer. Cold backup is supported.




N-17

HUAWEI BTS3900 Hardware Structure





N-18

The UPEU is classified into the Universal Power and Environment Interface Unit Type A (UPEA) and the Universal Power and Environment Interface Unit Type B (UPEB).  The UPEA converts -48 V DC to +12 V DC  The UPEB converts 24 V DC to 12 V DC The UPEU has the following functions:  Converting -48 V or +24 V DC to +12 V DC that is applicable to the boards  Providing two ports with each transmitting one RS485 signal and another two ports with each transmitting four dry contact signals  Providing reverse connection protection for power cable connectors. 



RS-485 o también conocido como EIA-485, que lleva el nombre del comité que lo convirtió en estándar en 1983. Es un estándar de comunicaciones en bus de la capa física del Modelo OSI. Está definido como un sistema en bus de transmisión multipunto diferencial, es ideal para transmitir a altas velocidades sobre largas distancias (35 Mbit/s hasta 10 metros y 100 kbit/s en 1200 metros) y a través de canales ruidosos, ya que reduce los ruidos que aparecen en los voltajes producidos en la línea de transmisión. El medio físico de transmisión es un par entrelazado que admite hasta 32 estaciones en 1 solo hilo, con una longitud máxima de 1200 metros operando entre 300 y 19 200 bit/s y la comunicación half-duplex (semiduplex). Soporta 32 transmisiones y 32 receptores.





N-19

The UEIU transmits monitoring signals and alarm signals from external devices to the main control board  Providing two ports with each transmitting one RS485 signal  Providing two ports with each transmitting four dry contact signals





N-20

The USCU has the following functions:  Providing absolute timing information and the 1 PPS reference clock for the main control board  Compatible with six types of satellite card: Resolution T, M2M, GPS15L, K161, GG16, and JNS100  Determining the type of satellite card in use by checking the 1 PPS timing signals  Supporting the input of RGPS signals  Providing the BITS port and supporting adaptive input of the 2.048 MHz and 10 MHz clocks

Puerto GPS: Coaxial SMA Puerto GPRS: PCB





The UBFA has the following functions:  Controlling the fan speed  Reporting the fan status to the main control board.  Detecting the temperature of the air inlets


N-21



P-23



P-24




Remote Radio Unit


N-25




 



 

N-26

Dúplex es un término utilizado en telecomunicación para definir a un sistema que es capaz de mantener una comunicación bidireccional, enviando y recibiendo mensajes de forma simultánea Low-noise amplifier (LNA) PA: Power Amplifier consists of the high-speed interface unit, signal processing unit, power amplifier, duplexer, extension ports, and power module

Simplemente amplificadores de optimizado para diferentes propósitos. Amplificador de bajo ruido normalmente no está obligado a ofrecer una enorme potencia (Watts y superior) en la salida, pero debe tener un bajo coeficiente de ruido y, preferentemente, bajo consumo de energía, mientras que ocurre lo contrario Amplificador de Potencia. Las características buenas para, por ejemplo, de alta potencia (por ejemplo, etapas de alta linealidad, diseño polietápico) trabajan contra bajo nivel de ruido y viceversa







N-27

Multiplexes receive (RX) and TX signals on the RF channel, which enables these signals to share the same antenna path. It also filters the RX and TX signals Recibe senales banda base en downlink desde la BBU baseband data from the BBU and sends uplink baseband data to the BBU.




N-28



N-29



N-30



N-31



N-32




Versiones Posteriores


N-33



N-34


 

M2000 based commissioning Preparing for the commissioning  In the equipment room:  1. Prepare the software, automatic deployment data, and LTE commissioning license  2. Create and start a commissioning task.  3. Prepare materials: 

Deployment ID-based base station binding: bar codes and barcode scanner

ESN-based base station binding: none  4. Configure the controller, obtain the device panel drawing, confirm the transport network status, and get ready the related features. Base station auto discovery  Onsite and in the equipment room:  5. Performing the deployment ID-based or ESN-based base station binding.  In the equipment room:  6. Ensure that the OMCH is available. Automatic base station configurations Automatic base station commissioning  Onsite and in the equipment room:  7. Check the project quality.  8. Test the environment alarms and handle the active alarms Completing the commissioning  In the equipment room:  9. Complete the commissioning task and obtain the deployment.  10. Modify the base station status to Normal. 



 



N-35




P-37






P-38

Site Information  Before commissioning, you must obtain the following basic information about the site Information on the networking and related configuration of the base station, including the base station type, transmission mode, networking mode, and cell configuration.  Base station data configured on the base station controller. Board Information  Before commissioning, you need to download the related board software onto the PC. In the case that the commissioning is performed by using the USB disk, you need to download the software onto the USB disk in advance. 

Diodo emisor de Luz - Light emitting diode (LED)




P-39



P-40



P-41




P-42

Commissioning Preparations  Obtaining Digital Certificates Required for NodeB Commissioning on the LMT in Scenarios Where a Security Gateway Is Deployed in the Network.  Downloading Digital Certificates on the LMT in Scenarios Where a Security Gateway Is Deployed in the Network.  Configuring Security Equipment in Scenarios Where a Security Gateway Is Deployed in the Network.




P-43


 

P-44

The default password for NodeB is “NodeB”. Proxy function is used to log in to the NodeB through M2000 or other proxy, M2000 server IP could be filled in Proxy server.




P-45




P-46

NodeB software  NodeB BootROM : Firmware.csp Applicable for NodeB progress starting up. NodeB Software : Software.csp 



Version file for each board of NodeB. For NodeB software, Software is mandatory to upgrade, the BootROM is optional. For some versions, the new software file is compatible with old BootROM, and there is no new BootROM file in the new version folder, so it’s no need to upgrade the BootROM. If there is new BootROM file in the new version folder which means the new software file is not compatible with old BootROM file, we must upgrade the BootROM also. 





 



 

P-47

Click the Maintenance tab in the navigation tree. Choose Software Management > Software Update > Upgrade BootROM. The Update BootROM dialog box is displayed. Choose the directory where you store the version file, then click “Next” to download the new BootROM from laptop to NodeB. If you click the “Activate BootROM”, the BootROM will be activated automatically after downloading. Activating the BootROM does not reset the NodeB. After you log in to the NodeB LMT by online mode, the SFTPServer is started up automatically. You’ll see in your windows tool bar. And the setting is done by system. Double-click the icon to check the detailed setting.



 













P-48

Click the Maintenance tab in the navigation tree. Choose Software Management > Software Update. The Software Update dialog box is displayed. Select Upgrade NodeB Software in the dialog box. Click Next. The Update NodeB Software dialog box is displayed. Select Backup Data Configuration File, Download NodeB Software Package, and Download by Configuration to specify a directory for backing up the file and a directory for downloading the NodeB software package. Backup Data Configuration File is optional. It is recommended that you select the option. When the configuration and initial configuration changes or the configuration file encounters an error, click Download Data Configuration File to download the data configuration file again. Then, click Effective Data Configuration File to confirm its validity before activating the NodeB software. It is recommended that you select Download by Configuration. If it is not selected, a dialog box is displayed to note this may cause the software download to fail. Click OK to start the download of the software. Click Cancel to review selections. When downloading by configuration, only required board software packages are downloaded. This reduces the total volume of data to be downloaded, shortens the download time, and saves storage space on the NodeB.





P-49

The green color indicates that the board operates normally. The red color indicates that the board is faulty, and an alarm related to the board exists.




P-50






P-51

command to query the time of latest successful synchronization of the SNTP client to the SNTP server, and whether the synchronization is successful comando para consultar la hora de la última sincronización exitosa del cliente SNTP con el servidor SNTP, y si la sincronización tiene éxito




P-52


 

 





P-53

In the navigation pane, click the Maintenance tab. Double-click Realtime Specific Monitoring > Cell RTWP. The Cell RTWP dialog box is displayed. For the parameter details in the Cell RTWP dialog box. Set the corresponding parameters in the dialog box. Click OK. A monitoring window is displayed, showing the current monitoring task in graphs. To stop this test task, use either of the following methods:  Method 1: Close the task monitoring window directly to stop all monitoring tasks displayed in the window.  Method 2: Right-click the task on the monitoring task list and select Delete Task from the shortcut menu. The curve displayed for the task is deleted together with the task. NOTE:  One RF module can be configured with one to four carriers. The system outputs the RTWP value of the corresponding carrier based on the actual configuration.  One carrier may be configured with main and diversity RX.



 

 



P-54

In the navigation pane, click the Maintenance tab. Double-click Realtime Specific Monitoring > Board RTWP. The Board RTWP dialog box is displayed. For the parameter details in the Board RTWP dialog box. Set the corresponding parameters in the dialog box. Click OK. A monitoring window is displayed, showing the current monitoring task in graphs. To stop this test task, use either of the following methods:  Method 1: Close the task monitoring window directly to stop all monitoring tasks displayed in the window.  Method 2: Right-click the task on the monitoring task list and select Delete Task from the shortcut menu. The curve displayed for the task is deleted together with the task.







   



P-55

In the navigation tree of the Local Maintenance Terminal window, click the Maintenance tab. Select Realtime Specific Monitoring > Output Power Monitoring. The Output Power Monitoring dialog box is displayed. For the parameter details in the Output Power Monitoring dialog box. Set the corresponding parameters in the dialog box. Click OK. A window is displayed, showing the current monitoring task in graph. To stop this test task, use either of the following methods:  Method 1: Close the task monitoring window directly to stop all monitoring tasks displayed in the window.  Method 2: Right-click the task on the monitoring task list and select Delete Task from the shortcut menu. The curve displayed for the task is deleted together with the task. Result:  The table monitoring items for the NodeB output power measurement. Item

Description

Carrier Output Power(Channel No: X; Carrier No: Y; Unit: 0.1dBm)

Indicates the output power of Y carrier in X channel. The carrier output power is the actual output power of the RRU.

Channel Output Power(Channel No: X; Unit: 0.1dBm)

Indicates the typical output power in X channel corresponding to the RF module. The carrier output power is the actual output power of the RRU.





P-56

Clicking Alarm in the NodeB LMT window, and the Browse Alarm tab page is displayed in the NodeB Alarm window









P-57

Context:  An excessively large VSWR results in a short transmission distance and reduced cell coverage, affecting the normal operation of the system. The normal VSWR ranges from 1 to 2.0. The VSWR less than 1.5 is preferred. Prerequisites:  Check that the antenna system is correctly installed based on the checked VSWR.  Ensure the NodeB services are resumed. CAUTION: During testing of the VSWR, the services of the NodeB are interrupted. Therefore, you are advised to test the VSWR when the service volume is light or after the NodeB services are isolated.





  

P-58

Run the DSP RRU command to query the cabinet/subrack/slot number, TX channel number, and maximum output power of the RRU or RFU. Run the LOC RRUTC command to set the maximum output power of the RRU or RFU. Run the RST BRD command to reset the RRU or RFU. Run the DSP TXBRANCH command to check that the maximum output power of each RRU or RFU is set successfully.





Check that the reported alarm is consistent with the configured external alarm


P-59

P-60




Data Sheet for NodeB Commissioning Site Name NodeB Model

Commission Time Commissioning Engineer Commissioning Result

□ Successful; □ Failed

Conclusion Handling Exceptional Cases □ Yes; □ Faults in NodeB hardware installation are cleared. No □ Yes; □ Commissi Transmission links between the NodeB and the RNC are ready. No oning Preparati Negotiation data of the NodeB to be commissioned is added to the □ Yes; □ No on Phase RNC. □ Yes; □ The required NodeB software, BootROM software, and data No configuration file are ready. Commissioning Item

The NodeB software, BootROM software are successfully upgraded. The data configuration file is successfully downloaded. Commissi oning The NodeB hardware status is checked. Phase The running status of the NodeB is checked. The NodeB VSWR is checked. Problem Description

□ Yes; □ No □ Yes; □ No □ Yes; □ No □ Yes; □ No □ Yes; □ No

Impact

Unsolved Problems After Commissioning Component Confidential Information of Huawei.P/N No Spreading Without Permission Faulty Board Record



P-61



P-62






P-63

On the NodeB side, you can upgrade the software and data configuration through the USB flash drive, check the hardware status based on the LED status, and then check the VSWR of the antenna. On the M2000 side, you can perform fault diagnosis and service verification for the NodeB. Commissioning Preparations:  Obtaining the Common Configuration File in Scenarios Where a Security Gateway Is Deployed in the Network.  Obtaining a USB Flash Drive for NodeB Commissioning.  Configuring Security Equipment in Scenarios Where a Security Gateway Is Deployed in the Network.



 







P-64

Obtain the tools required for the local NodeB commissioning using the USB storage device. The USB Storage Device for NodeB commissioning must be delivered by Huawei. Check the compatibility of the USB flash drive with the NodeB. Do as follows to test the USB flash drive: insert the flash drive into the USB port on the WMPT or UMPT of a NodeB that runs normally, and wait three seconds. If the indicator on the flash drive blinks once, the flash drive is functional. If the flash drive fails the preceding test, you are advised to replace the original flash drive. Save required files in the specified paths of the USB flash drive, depending on the specific scenarios. Optional: Use the USB protection tool to encrypt configuration files in the USB flash drive to prevent key information leakage or unauthorized modification. CAUTION: After you have downloaded the file to the USB flash drive from the computer, unplug the flash drive according to the system prompt. If you do not unplug the USB flash drive according to the system prompt, errors may occur when you access the flash drive.  The antenna VSWR detection script can be customized, with the file name of STRVSWR.dat. The file content is as follows:[Config] VSWRTHD = a Where, a indicates the VSWR threshold, which can be set as required. The recommended value is 1.5.











P-65

After the USB flash drive is inserted into the USB port on the WMPT/UMPT of the BBU3900, the BBU3900 automatically detects the USB flash drive and installs the USB disk driver. After the installation, the NodeB automatically reads the software and data configuration file in the specified directories of the USB flash drive and verifies their names and formats. When the NodeB reads the software and data configuration file, it checks whether the active software version and configuration data is the same as the software version and configuration data in the USB flash drive. If they are different, the NodeB automatically starts the software and configuration upgrade. If they are the same, the NodeB skips the upgrade. When upgrading the software and configuration using the USB flash drive, pay attention to the following points:  By default, the NodeB downloads the software and data configuration file from the USB flash drive by configuration. The NodeB also supplements the software. For example, when an RRU is not connected to the BBU3900 through a fiber optic cable, the software and data configuration file related to the RRU are not downloaded. After the RRU is connected to the BBU, the NodeB automatically downloads the software and data configuration file related to the RRU from the USB flash drive.  If only the software is saved in the USB flash drive, the NodeB automatically upgrades the software.  If only the data configuration file is saved in the USB flash drive, the NodeB automatically downloads the data configuration file. After downloading the software and data configuration file from the flash drive, remove the USB flash drive before leaving the site.


P-66




Status of the indicators on the USB flash drive and the WMPT/UMPT(table1) Event

State of the LED on the USB Disk

State of the RUN LED on the WMPT/UMPT

Duration

Automatically detecting the USB flash drive

ON

Blinking (on for 1s and off for 1s)

About 1 second to 2 seconds

Downloading the software and data configuration file from the USB flash drive

Blinking

Blinking (on for 0.125s and off for 0.125s)

About 14 minutes

Blinking (on for 1s and off for 1s)

- (If this status remains for more than one minute, the upgrade is successful.)

Normal NodeB operation

ON





P-67

NOTE: 







Do not remove the USB flash drive during the period from insertion of the flash drive to normal operation of the NodeB. Otherwise, the file load or parsing fails. After the software and data configuration file are downloaded, the software activation takes three or four minutes and NodeB reset takes about two minutes. You can omit the indicator status during this period. You only need to check the indicator status in the three phases described in Table 1. The time for downloading the software and data configuration file from the USB flash drive and the time for activating the software may differ from those in Table 1, according to the version and configuration. The upgrade or configuration fails if any of the following cases occurs: 



After the USB flash drive is inserted, the RUN indicator on the WMPT/UMPT blinks slowly, and the LED on the USB flash drive is on. During the upgrade, the indicator on the USB flash drive is off, and the RUN indicator on the WMPT/UMPT blinks slowly.

During the software upgrade and data configuration update, the indicator on the USB flash drive is off. After clearing the faults in the hardware of the USB flash drive, check that the version software and data configuration file are saved in the correct directory. 







P-68

When all the LED status of the BBU3900 boards and auxiliary devices coincide with those listed in table, the NodeB is functional.





P-69

Methods of rectifying common faults

If...

You can Infer That... Then...

The LED on the USB disk is off

The NodeB software fails to be upgraded from the USB disk.

Insert the USB disk again, and upgrade the software. If the software fails to be upgraded again, record the problem in the data sheet for the NodeB commissioning, and then upgrade the software on the LMT.

The software is RUN LED on each being loaded or the Wait for five minutes and then check the status of the RUN LED again. BBU board blinks board is wrongly If the RUN LED still blinks (on for 0.125s and off for 0.125s), check whether (on for 0.125s and positioned in the the board is positioned in the correct slot. If not, reinstall the board. off for 0.125s) slot of another board. The ALM LED on Reinstall the board to check whether the fault is rectified. If the ALM LED the WMPT, WBBP, The board is faulty. still blinks, replace the board. or UTRP is on

The ALM LED on The external port the active WMPT on the active blinks WMPT is faulty.

•Check whether the RUN LED on the PMU, AFMU, EMU, or EMUA blinks (on for 0.125s and off for 0.125s). If the RUN LED on those boards blinks (on for 0.125s and off for 0.125s), check whether the RS485 signal cable is connected properly. •Check whether the dry contact alarm signal cable is properly connected to the corresponding port on the UPEU. If the fault persists, record the fault and the LED status of the WMPT in the data sheet for the NodeB commissioning. Then, rectify the fault on the LMT or M2000.

•Check whether the optical module is installed. If not, install the optical module. The CPRI optical •Check whether the CPRI optical cable is improperly connected, for example, A CPRI LED on the cable is improperly the receive end and the transmit end are reversed. If it is improperly WBBP is steady connected, or the connected, reinstall it. Then, wait for 30 seconds, and check the status of the red optical module is CPRI LED again. out of position. •Check whether the CPRI optical cable is damaged. If it is damaged, replace it. CPRI LED on the WBBP blinks red The RRU or the (on for 0.25s and WRFU is faulty. off for 0.25s)

Check whether an ALM LED on the RRU or the WRFU is on. If an LED is on, power on the RRU or the WRFU again. If the fault persists, replace the RRU or the WRFU.

•Check whether a VSWR LED on the RRU or the WRFU is off. If the VSWR LED is not off. There is a VSWR •Check whether a ALM LED on the RRU or the WRFU blinks. If it blinks, then: CPRI LED on the alarm, an antenna • Check whether the antenna devices are properly connected WBBP blinks red alarm or an to the RRU or the WRFU. (on for 1s and off external alarm on • Check whether there is an external dry contact alarm on the for 1s) the RRU or the RRU or the WRFU. If there is an external dry contact alarm, WRFU. record the alarm in the data sheet for the NodeB commissioning.



 



P-70

Plug the USB disk into the USB port on the WMPT/UMPT of the BBU3900. Wait for the NodeB to automatically test the VSWR. When the USB disk LED is off, the VSWR test is complete. Observe the status of the CPRI LED on the WBBP.  If the CPRI LED blinks red (on for 1s and off for 1s), the RRU or WRFU has the VSWR alarm.  If the CPRI LED is steady green, the test result is normal and there is no VSWR alarm. Unplug the USB disk and end the VSWR test. Unplug the USB disk first and then plug it back into the USB port. When the USB disk LED is off, observe the CPRI LED on the WBBP to check whether the VSWR is normal.  If the CPRI LED blinks red (on for 1s and off for 1s), the fault persists.  If the CPRI LED is steady green, the test result is normal and there is no VSWR alarm. Unplug the USB disk and end the VSWR test.





P-71

Perform fault diagnosis and service verification for the NodeB through the M2000 after transmission is available.


BTS3900 WCDMA V200R014 Remote Commissioning



P-72

You can perform the remote commissioning on multiple base stations on the M2000 in the central equipment room. The commissioning procedures, such as software and configuration upgrade, alarm monitoring, and service verification, can be performed on the M2000.





P-73

NodeB auto discovery refers to the entire process of powering on the NodeB and establishing the OM link after the NodeB hardware configuration is complete. The process is described as follows:  The NodeB performs self-check after being powered on.  If the onsite networking mode is VLAN, the NodeB needs to learn about the VLAN and obtain the VLAN ID.  The NodeB sends a DHCP request to the DHCP server (the M2000) to obtain information such as the OMIP address.  The DHCP request sent by the NodeB includes NodeB ESN information. After the DHCP server detects the NodeB ESN.  After the ESN has been bound, the DHCP server automatically records the ESN in the DHCP request. When the NodeB sends a DHCP request again, the DHCP server automatically matches the ESN and the ESN reported by the NodeB. In this way, the IP address is assigned.  After the DHCP request sent by the NodeB succeeds, an OM link is automatically established between the NodeB and the M2000.





P-74

Preparing for NodeB commissioning:  Check that the NodeB hardware, such as the cabinets, cables, antenna system, and auxiliary devices, is installed and passes the installation check. The NodeB passes a power-on status check and is powered on.  Check that the controller hardware is installed and commissioned successfully and the controller runs normally. The negotiated data of the NodeB to be commissioned is configured at the controller and recorded.  Check that the M2000 is commissioned, it is connected to the corresponding controller, and the configuration synchronization is completed.  Check that the M2000 server is installed with an adaptation layer whose version matches the version of the NodeB to be commissioned.  Check that the software package of the target NodeB version to be commissioned is obtained from the website.  Prepare the data configuration file of the NodeB to be commissioned.  The deployment list of the NodeB to be commissioned is ready.  Check that the NodeB relay server is set correctly.  Check that the network is normal.





P-75

When the network transmission works normally, you can commission a NodeB using the NodeB plug-and-play function on the M2000 in a central equipment room.













P-76

Log in the M2000 Client.

Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Click Prepare File&Data. The window for preparing files and data is displayed. Upload data files as required. Date files have the following types: 

NE software



cold patches



hot patches



configuration data files



deployment lists

File save paths: 







Software version:/export/home/sysm/ftproot/NodeB Type/Software/NodeB Software Version/ Cold or hot patch:/export/home/sysm/ftproot/NodeB Type/Patch/NodeB Patch Version/ Configuration data file:/export/home/sysm/ftproot/adn/AutoDeploymentData/NodeB/CfgData/

Deployment list:/export/home/sysm/ftproot/adn/AutoDeploymentData/NodeB/ADList/



 





P-77

The methods of Obtaining deployment list are listed as follows: Deployment lists are exported from the CME  If the CME has been deployed and you have initially configured NodeBs on the CME, it is recommended that you use the CME to export NodeB deployment lists. For details, see Exporting the Deployment List and Configuration Files of Physical NodeBs in M2000 Help.  Obtain and open the exported deployment list. Check whether the software version, cold patch, and hot patch are consistent with planned ones. If they are inconsistent, change them as planned. In addition, set other relevant data. Deployment lists are exported from the M2000 client  If the CME has not been deployed, you can export NodeB deployment lists from the NodeB Auto Deployment window on the M2000 client.  Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed.  Click . The Save dialog box is displayed.  Specify a save path and click OK.  Open the exported deployment lists and fill out or modify relevant data based on the planned data that is confirmed with the network planning engineers. Note:Before the deployment, check whether the planned target version is consistent with the target version in the deployment list.







Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. Select deployment lists and configuration data files.  Click . The Import deployment list dialog box is displayed.  In the Specify Deployment List area, select deployment lists. 

Import deployment lists from the M2000 server: Select From Server and choose deployment lists from the drop-down list box.

Import deployment lists from the M2000 client: Select From Client and click to select deployment lists. Click OK. The system starts the import.  After the import is complete, the M2000 checks any mandatory parameters in the list are empty and whether any parameter values are invalid. In addition, the information indicating whether the import succeeded or failed is displayed on the Operation Information tab page. (Optional) Modify data in the imported deployment lists as required. This step is mandatory when you need to modify the data in the imported deployment lists. 





P-78





 

Right-click a commissioning task in the commissioning task list, and then choose Deployment Parameter from the shortcut menu. The Deployment Parameter dialog box is displayed. Double-click the cells containing parameter values to modify the values. If you need to modify ESNs, perform the following operations: 

Click

in the ESN value cell. The Bind ESN dialog box is displayed.

Select an ESN that is not bound, and then click OK to return to the Deployment Parameter dialog box. After the modification, click OK. 



P-79









P-80

Optional: For a NodeB, you need to run the MML command REQ NECMCTRL first to set the Configuration Management (CM) control switch of the NodeB to ON. Choose Maintenance > Maintenance Mode to open the Maintenance Mode window. Set the NEs to enter the corresponding maintenance mode. CAUTION:  The maintenance mode must be set to TESTING. No other mode is allowed. After maintenance operations are complete, restore the NE to the NORMAL mode.









 

P-81

Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. On the Deployment List tab page, right-click one or multiple commissioning tasks and choose Start from the shortcut menu. The Task Settings dialog box is displayed. Select steps in the Select column based on the actual plan to customize steps for commissioning procedures. (Optional) Set the AACP function based on the actual plan. Click OK. The M2000 automatically checks whether the data files required for procedures are available.







Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. View the status and progress of commissioning tasks in the commissioning task list.  You can quickly view the status of commissioning tasks by using either of the following methods: 

In the commissioning task list, the status of the tasks is displayed in Status, the current procedures are displayed in Current Phase, and details about each procedure are displayed in Description.

In the commissioning task list, select one or multiple commissioning tasks whose status you want to view, and then click . The right pane displays execution status of steps for commissioning procedures.  The displayed information includes the execution status, description, start time and end time of each commissioning substep. (Optional) Click . The Statistics dialog box is displayed, counting the number of commissioning tasks in each status. Click OK to close the dialog box. 



P-82









P83

Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. In the commissioning task list, right-click a commissioning task for which you want to handle alarms and choose Open Monitor Window from the shortcut menu. The alarm monitoring window is displayed. Handle alarms.  Double-click an alarm to be handled in the alarm list in the right pane. The Details dialog box is displayed.  Click the link in Reason and Advice.  Handle exceptions based on the alarm reference.









P-84

Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. In the commissioning task list, right-click a commissioning task for which you want to perform fault diagnosis, and choose Open Monitor Window from the shortcut menu. The alarm monitoring window is displayed. Perform fault diagnosis on physical transmission port, boards, or antennas.  Select an object from the left pane of the displayed window, or select a specific alarm of the object from the alarm list in the right pane, right-click the object or alarm, and choose Diagnose from the shortcut menu. The Diagnosis parameter settings dialog box is displayed.  Select a NodeB in the Select NE area, select a diagnosis type in the Select diagnose type area, type diagnosis parameters in the Type diagnosis parameters area, and click OK. The dialog box for confirming the diagnosis is displayed.  Click Yes. The system starts the fault diagnosis. During the fault diagnosis, a diagnosis task is added to the diagnosis task list. Right-click a diagnosis task in the diagnosis task list, and choose Diagnose Report from the shortcut menu to view diagnosis results. 











P-85

Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. In the commissioning task list, select a commissioning task for which you want to view verification results, right-click the task, and choose Open Service Verification Window from the shortcut menu. The service verification window is displayed. View service verification results and perform operations as required.  The accumulated values of the counters, which are collected in the time range between the start of service verification and the restart of commissioning or the confirmation of commissioning completion, are displayed in the service verification window.  If cells corresponding to all counters once display , service verification is successful. You can confirm the completion of the commissioning.  If the cell corresponding to a certain counter always displays , services related to this counter are running abnormally. You need to rectify the faults.







P-86

Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. On the Deployment List tab page, select one or multiple commissioning tasks and perform operations as required.







P-87

Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. In the commissioning task list, select one or multiple commissioning tasks for which you want to confirm completion. Right-click the tasks and choose Confirm Completion from the shortcut menu to confirm the completion.  After the commissioning is complete, the M2000 stops the following services: 



Monitoring alarms on the NodeBs and relevant alarms on the RNCs that manage these NodeBs. Subscribing to the service verification performance counters of the NodeBs.



 

P-88

Choose Maintenance > Maintenance Mode. Click and check whether Current NE Maintenance Mode is NORMAL.  If Current NE Maintenance Mode is NORMAL, no further operation is required.  If Current NE Maintenance Mode is not NORMAL, set the NE to enter the NORMAL mode and select Instant.











P-89

Choose Configuration > Auto Deployment > NodeB Auto Deployment from the main menu of the M2000 client. The NodeB Auto Deployment window is displayed. In the commissioning task list, select one or more commissioning tasks for which you want to export the report, right-click the tasks, and then choose Export Deployment Report from the shortcut menu. A dialog box is displayed, asking you whether to export alarm data at the same time. Specify a save path, and then click Save.  You can customize a filename for the commissioning report. If you do not specify a filename, the M2000 names and saves the file based on the naming convention NodeB_Auto_Deployment_Report_user name_YYYYMMDDHHMMSS.zip. (Optional) Decompress the generated report file. In the decompressed folder, double-click index.html to view the commissioning report.  If you choose to export alarm data at the same time, the file containing the alarm data is saved in the alarm sub-folder.


P-90




  

Run the DSP RRU command to query the cabinet/subrack/slot number, and maximum output power of the RF unit. Run the LOC RRUTC command to set the maximum output power of the RF unit. Run the RST BRD command to reset the RF unit. Run the DSP TXBRANCH command to check that the maximum output power of each RF unit is set successfully.

If...

Then...

The maximum TX power of each RF unit is set successfully

End this task.

The maximum TX power of each RF unit is not set successfully

Check whether the maximum output power exceeds the power specifications supported by the RF unit. Set the maximum output power again. If the setting of the maximum output power still fails, contact Huawei for technical support.




N-91

2. Owb201800 Bts3900 Wcdma v200r015 Comisionamiento Issue 1.

Recommend Documents