03 - OEB206900 ENodeB LTE V100R008C10 Local Commissioning

0
eNodeB LTE V100R008C10 Local Commissioning
Confidential Information of Huawei. No Spreading Without Permission


Commissioning Modes:
 U2000-based Commissioning: After hardware installation and power-on check are
complete, the transmission link must be available. You can remotely commission the
base station on the U2000 in the central equipment room;
 USB+U2000-based Commissioning: After hardware installation and power-on check are
complete, if the transmission link is unavailable, upgrade the software and data
configurations by using the USB flash drive at the site. When the transmission link is
available, continue the commissioning on the U2000;
 Local Commissioning with LMT: After hardware installation and power-on check are
complete, if the transmission link is unavailable, upgrade the software and data
configurations on the LMT at the site. When the transmission link is available, continue
with the commissioning on the U2000. This commissioning method requires a laptop at
the site and is used as a backup scheme, because it needs a higher deployment cost and
has a stronger requirements for commissioning skills of the personnel.
Commissioning Prerequisites for eNodeB hardware
 The eNodeB hardware is installed and passes the hardware installation check. For details,
see the related hardware installation guide;
 All cables are correctly connected.
Commissioning Prerequisites for the Transport network

 The eNodeB is connected to the core network equipment MME or S-GW, which is
already commissioned and can provide the basic functions of the core network;
 The U2000 server has the mediation corresponding to the target version of the eNodeB
to be commissioned.
The lines in the preceding figures indicate only the connections but not the quantity
and types of cables.
Figure shows a typical application of the commissioning network without the
security GW. The eNodeB, MME, S-GW, and U2000 are located in a trust domain,
and they can communicate with each other directly.

The lines in the preceding figure indicate only the connections but not the quantity
and types of cables.
Figure shows a typical application of the commissioning network with the security
GW. The eNodeB is located on a network whose trusted domain is different from the
network where the MME, S-GW, and U2000 are located. Therefore, the eNodeB
communicates with the MME, S-GW, and U2000 through the security GW.

The eNodeB LMT is mainly used to help Commissioning the eNodeB, find faults
locally, and clear faults.
You can operate and maintain the eNodeB through the LMT in the following
scenarios:
 When the transmission between the eNodeB and the U2000 is unavailable, you
can Commissioning the eNodeB through the LMT;

 When the communication between the eNodeB and the U2000 fails, you can
locate and clear faults through the LMT;
 When alarms are generated on the eNodeB and related boards need to be
replaced locally, you can locate and clear faults through the LMT.

Remote Commissioning on the U2000

The remote commissioning on the U2000 is applicable to the following scenarios:
 The eNodeB is properly connected to the U2000;
 Site swapping (permissible downtime ≥ 1 hour);
 Deploying a new site.
For the detailed description of Remote Commissioning refer to “eNodeB LTE

V100R008 Remote Commissioning” module
Local Commissioning Through the USB Disk

The local commissioning through the USB disk is applicable to the following
scenarios:
 The connection between the eNodeB and the U2000 is not established yet;
 Site swapping (permissible downtime < 1 hour);
NOTE: If the IP address of the U2000 can be pinged on the eNodeB, the connection
between the eNodeB and the U2000 is normal.

Local Commissioning on the LMT

The local commissioning on the LMT is applicable to the following scenarios:
 The connection between the eNodeB and the U2000 is not established yet;
 The eNodeB fails to be started up through a USB disk, or there is no USB disk;
 Site swapping (permissible downtime < 1 hour);
NOTE: If the IP address of the U2000 can be pinged on the eNodeB, the connection
between the eNodeB and the U2000 is normal.

This section describes the procedures to upgrade software and configure data using
a USB disk, check the operating status of the eNodeB hardware, and rectify the
eNodeB hardware faults (if any) in time at the eNodeB site. For the detailed
description of the procedures to be carried remotely at the U2000 after the local
operation has been finished, please refer to the eNodeB LTE V100R008 Remote
Commissioning module.


In the local eNodeB commissioning through the USB storage device, you can upgrade
the eNodeB software and download data configuration file by using the USB storage
device, and check the indicators for the operating status of the eNodeB.
For the remote side, we can create commissioning task to monitor the procedure of
commissioning, when start the deployment list on the U2000, unselect the
Download Software, Download Configuration and Activate in the displayed task
setting dialog box. The unselected steps are skipped through the automatic eNodeB
commissioning.

In the local eNodeB commissioning through the USB storage device, you can upgrade
the eNodeB software and download data configuration file by using the USB storage
device, and check the indicators for the operating status of the eNodeB.
For the remote side, we can create commissioning task to monitor the procedure of
commissioning, when start the deployment list on the U2000, unselect the
Download Software, Download Configuration and Activate in the displayed task
setting dialog box. The unselected steps are skipped through the automatic eNodeB
commissioning.

This section describes the procedures to upgrade software and configure data using
a USB disk, check the operating status of the eNodeB hardware, and rectify the
eNodeB hardware faults (if any) in time at the eNodeB site. For the detailed
description of the procedures to be carried remotely at the U2000 after the local
operation has been finished, please refer to the eNodeB LTE V100R008 Remote
Commissioning module

Preparing a Software Package, Data Configuration Files, and Deployment Lists

The deployment lists are uploaded to the U2000 server. The software package and
data configuration files are stored on a local PC for preparing a USB flash drive.
Uploading a Commissioning License
The commissioning license is uploaded to the U2000 server.
Obtaining a device panel drawing
The device panel drawing shows the installation position and cable connections of
each board and module in a base station. To facilitate the commissioning, field
engineers must obtain the installation information about the boards and modules of
a base station.
Preparing a USB for eNodeB
Before the local eNodeB commissioning through USB, you need to prepare the
related eNodeB information, software, files and tools, and save the required files in a
specified directory structure of the USB.

Prerequisites
The data copy right has been obtained for the PC that is used to make a USB flash
drive. If this right is not obtained, the PC for making a USB flash drive cannot copy
data from the USB flash drive. In this case, obtain the data copy right by following
the corresponding procedure.
The following files are available:
ITEM DESCRIPTION
Obtain the software package from Huawei engineers and decompressed
Software package
the software package on a local PC.
Upgrade files
Pre-configuration script Precfg.ini can only be prepared manually. For details, see Preparing a Pre-
(Precfg.ini) configuration Script.
Export deployment lists and data configuration files from the CME and save
these files on a local PC. For detailed operations about exporting
deployment lists and data configuration files from the CME, see Exporting
Configuration Deployment lists and Deployment Lists and Data Configuration Files from the CME.
files data configuration files The .xml data configuration files exported from the CME must be used. The
encrypted .ecf data configuration files exported from the CME can be
delivered to the base station only through MML commands, and these files
cannot be used to prepare a USB flash drive for commissioning.
(Optional) License file Get ready the LTE commissioning license before enabling LTE services.

The following tools are available:
ITEM DESCRIPTION
The USB flash drive meets the following requirements:
• Has a capacity larger than or equal to 4 GB;
• Has a data transmission indicator;
USB flash drive • Has no additional functions such as encryption, virus
killing, self-booting, MP3, MP4, and smartphone;
• Has passed the compatibility check conducted by Huawei
engineers using Huawei internal tools.
USB making and The tool is saved in U2000 client installation
protection directory\client\client\USBProtector.

NOTICE:
After the folders are copied to the USB flash drive, eject or safely remove the USB
flash drive from the Windows operating system. You can only remove the USB flash
drive from the PC after either of the preceding operations. If the USB flash drive is
forcibly ejected, the files in the USB flash drive may be damaged. As a result,
software and data configuration files cannot be loaded by using the USB flash drive.
When transferring files for a making USB flash drive, do not copy the .xml files from
a remote desktop to a local PC. Otherwise, base station deployment will fail. You are
advised to compress the required files into a .rar or .zip file for file transfer.

Checking a Transport Network

Remote engineers can choose different methods to check a transport network based on
whether the USB flash drive contains the configuration data.
Setting Environmental Alarm Parameters
Setting environmental alarm parameters are used for a user-defined alarm.
Preparing Dialing test tools
Dialing test tools are used to check whether the base station can perform services
correctly. Commonly used tools are test terminals. For ordinary terminals, the
subscriber identity module (SIM) cards must be defined on the home location register
(HLR) or home subscriber server (HSS) before the commissioning.
Creating an NE Commissioning Task
Remote engineers import a deployment list to the U2000 server to create an NE
commissioning task
Printing the Bar Code on the U2000
To deploy base stations using deployment IDs, you must plan the deployment IDs in
advance and print the bar codes containing the IDs on the U2000. Then, onsite
engineers can scan the bar codes into the NE using a bar code scanner
Presetting a Bar Code Scanner
You should preset a bar code scanner before you use a bar code scanner to bind the
base station for the first time
Starting an NE Commissioning Task
After a commissioning task is started, the U2000 automatically commissions one or
multiple NEs

Base station binding

If configuration files for the eNodeB are not contained on the USB flash drive, the
step of binding a base station with the U2000 is needed for OM channels
establishment. There are 2 ways for base station binding:
 Bar-code-based binding mode;
 ESN-based binding mode.

The ESN is printed on both the label and the mounting ear of the BBU, as shown in
the figure. The local engineer must remove the label, record the site information in
the Site area on the label, and report the information to the remote engineer.
If there is no label on the fan module in the BBU, the local engineer must record the
ESN and site information manually, and report the information to the remote
engineer.

If the USB flash drive stores only the software, the base station loads only this
software.
If the USB flash drive stores only data configuration files, the base station loads only
these files.
The base station does not load the software or data configuration files from the USB
and the RUN indicator on the main control board indicates a loading failure (steady
on) in the following conditions:
 The base station finds out that the USB is not intended for it;
 The expected directories or files do not exist;
 The expected directories or files formats are not correct;
 Data in the USB flash drive is not encrypted or integrity-protected;
 Data configuration files loaded from a USB flash drive last time are the same as
that on the current USB flash drive.
If the USB flash drive contains the license file, the LTE main control board will read
this license file.

The local engineer can observe the status of the RUN indicator on the main control
board to determine the loading status of the software and data configuration files.
For a single-mode base station, this step takes about 15 minutes. For a multimode
base station, this step takes about 25 to 30 minutes. It is recommended that the
local engineer observe the status of the RUN indicator after this duration.
After the loading process is completed, the software activation and base station
restart take about 3 minutes. You do not have to observe the status of the RUN
indicator during this time.
Do not remove the USB flash drive when the base station is still in the Loading...
Status.

Prerequisites for LTE service testing:

 The transmission between the eNodeB and the MME/S-GW is ready. MME stands
for mobility management entity, and S-GW stands for serving gateway;
 The data negotiated for the eNodeB has been added to the MME and S-GW;
 The UE has been defined on the HSS;
 An FTP server is ready;
 A WWW server is ready.


Testing Installation and Deployment Quality

The local engineer checks the ports and rectifies the problems. After the
troubleshooting, the local engineer instructs the remote engineer to resume the
commissioning task.
Handling Alarms
If the ALM indicator on a board is steady on and the RUN indicator is on for 0.125 s
and off for 0.125 s, do not replace the board because the board is loading the
software package or data configuration files. If the ALM indicator is still steady on
when the RUN indicator does not blink fast, replace the board.
Checking Environmental Alarms:
 The local engineer performs a loopback test on an alarm port of the UPEU using a
twisted pair. The remote engineer checks whether the U2000 receives an
environmental alarm from the alarm ports;
 The local engineer stops the loopback test. The remote engineer checks whether
the alarm on the U2000 is cleared;
 Both local and remote engineers repeat the preceding steps until all eight of the
alarm ports on the UPEU pass the tests.

This chapter describes how to use local maintenance terminal at the eNodeB to
upgrade eNodeB software and configure eNodeB data, check eNodeB hardware
status, rectify eNodeB hardware faults (if any) to facilitate the establishment of
eNodeB OM channels. This chapter also describes how to check the operating status
of the eNodeB on the U2000.

Mandatory
Optional

Tool Description
• The hardware configuration, software configuration, and
communication capabilities of the laptop should meet certain
specifications. For details, see Configuration Requirements for the
Laptop
Computer Installed with the LMT in the eNodeB LMT User Guide;
• The software and data configuration file required for the eNodeB
commissioning on the LMT are saved in the laptop.
Ethernet The Ethernet cable connects the laptop to the eNodeB.
cable
Testing UE The testing UE is functional and is registered in the HSS.
Before local eNodeB commissioning on the LMT, you need to obtain the related
information and tools required for eNodeB commissioning, and configure the FTP
server. When the security GW is deployed on the network, the digital certificate is
required if there is no configuration file. The digital certificate needs to be added to
the eNodeB from the LMT.


An adapter is used for local maintenance to connect the USB port on the UMPT to
an Ethernet cable towards the LMT PC, it has a USB 3.0 connector at one end and an
Ethernet connector at the other end.
Pin of the USB3.0 Pin of the Ethernet

Wire Color Wire Type
Connector Connector
X1.9 Blue X2.1
Twisted pair
X1.8 White X2.2
X1.6 Orange X2.3
Twisted pair
X1.5 White X2.6
X1.Shell - Shell X2.Shell

A maximum of six local users and EMS users can log in to the LMT at the same time.
WARNING:
Do not change the system time or time zone of a computer installed with the LMT
when the LMT is running. Otherwise, a critical fault may occur in the system. If the
system time or time zone has to be changed, you must perform the operation after
the LMT exits.
The refresh function of the browser cannot be used on the LMT. If you use the
refresh function in the LMT main window, the window exits. If you use the refresh
function on the monitoring page, an error occurs in the script.
When the LMT uses an Internet Explorer, do not change the properties of the file
system. Otherwise, the Internet Explorer is automatically refreshed, and therefore
an error occurs in the LMT main window.
If you start FTP services by choosing Start > Run, the LMT main window is replaced
with the login dialog box of the FTP server. To avoid this problem, choose Tools >
Internet Options from the menu of the Internet Explorer. On the Advanced tab page,
clear the Reuse windows for launching shortcuts check box under Browse.
Before an LMT version upgrade or rollback, you must clear the buffer and cookies of
the Internet Explorer.
If you press the ALT + <--- key, the LMT main window may experience an exception.
In this case, press the ALT + ---> key to restore the window. If the window cannot
restore, you are advised to close the Internet Explorer and log in to the LMT again.


Set the FTP server in the LMT PC:

1. Double-click SFTPServer.exe to start the FTP server. The FTP server icon is
displayed as in the status area on the right of the taskbar;
2. Right-click , and choose FTP server configure. The FTP server
configuration dialog box is displayed, as shown;
3. Set User name, Password, and Working directory of the FTP server. By
default, the user name is admin and the password is admin. Working
directory should be set as the directory where the software and data
configuration file are saved;
4. Click OK.

In special scenarios such as base station deployment or upgrade, select the

Download version software check box and set Delay Download Flag to Yes (Delay
download) to reduce the time required. In delay download mode, only the minimum
LMT package is downloaded, and the complete LMT package can be automatically
downloaded about four hours later. This mode has no impact on the base station
software. If the functions of the complete LMT package are required before the
complete package is automatically downloaded, you can run the SPL SOFTWARE
command to download the complete package to the base station.
If the Install license check box is selected and Force flag is set to Yes, the license file
is forcibly installed despite of any errors. If Force flag is set to No, which is
recommended, error information is displayed during the license file installation.
Mapping between tasks and MML commands:

There are two storage area in LMPT/UMPT, main area stores the current running
software, and standby area stores the latest downloaded software.
After eNB activates the recent download software, then it will be running on main
area and meanwhile the previous version will be stored in standby area for rollback.



 On the LMT, click the Alarm/Event button. The Alarm/Event tab page is displayed;
 Check for active alarms on the Engineering Alarm tab page of the Browse
Alarm/Event tab page;
 Double-click an active alarm. Detailed Information dialog box is displayed;
 Click Solution... to know the detailed information and alarm handling procedure.
Clear the active alarm by following the alarm handling procedure.


Types of MML commands:

Actio Actio
Meaning Meaning
n n
ACT Activate RST Reset
ADD Add SET Set
BKP Back up STP Stop
BLK Block STR Start
DLD Download UBL Unblock
Display dynamic
DSP ULD Upload
information
LST List static data SCN Scan
MOD Modify CLB Calibrate
RMV Remove
Formats of MML Commands:

 The format of an MML command can be "Command Word: Parameter
Name=Value;".
 The command word is mandatory, whereas the parameter name and value are
optional.
 An example of an MML command with a command word and parameters: BLK
BRD: CN=0, SRN=0, SN=3;
 An example of an MML command with only a command word: LST VER:;

If there is no configuration file available, the local commissioning can be carried out
with the execution of a series of MML commands based on the planning
information.
Other commissioning tasks should be performed before and after, for example
software download, license installation, handling of alarms, etcetera, to complete
the commissioning.
Following is a guide with commands to achieve the commissioning of eNodeB with
MML commands.

To turn off the DHCP Switch, so that the BS attempts to restore remote maintenance
channel based on the transmission configurations.
SET DHCPSW: SWITCH=DISABLE;
An eNodeB is initially configured in minimum configuration mode. To remove the
original default configuration run the following commands, for RRUs in SRN=60 to
77, RRUCHAINs in RCN= 0 to 17 and BRDs in slots 0 to 6.
RMV RRU: CN=0, SRN=[60 to 77], SN=0
RMV RRUCHAIN: RCN=[0 to 17];
RMV BRD: CN=0, SRN=0, SN=[0 to 6];
Optional: The LMPT board is configured by default in slot 7, if you need to change
this, delete it first, then configure it as needed:
RMV BRD: CN=0, SRN=0, SN=7;


A large number of alarms are generated during eNodeB maintenance, such as

deployment, upgrade, or commissioning. These high-severity alarms are usually
related to reset, switchover, and link interruption, and are automatically cleared
after eNodeB maintenance is complete. Users can shield these alarms during
eNodeB maintenance to ensure proper network monitoring. This is done by setting
the Maintenance Mode of the eNodeB with the following command:
SET MNTMODE: MNTMode=INSTALL, MMSetRemark="Commissioning the eNodeB";



Add the Radio Frequency data:

ADD RRUCHAIN: RCN=0, TT=CHAIN, HCN=1, HSRN=0, HSN=3, HPN=0, CR=AUTO;
ADD RRU: CN=0, SRN=60, SN=0, RCN=0, PS=0, RT=LRRU, RS=LO, RN="ALFA", RXNUM=2,
TXNUM=2, ALMPROCTHRHLD=25;
The number rule of RRU subrack:
 1, The number rule of RRU subrack is consistent in the same network;
 2, The number rule of RRU subrack starts from low frequency according to the
frequency supported by RRU. For example, there are three frequencies in the network.
They are 900M, 1800M, 2100M and use RRU3926, RRU3929, RRU3806. Normally, the
RRU3926 uses the number 60-69; the RRU3929 uses the number 70-79; the RRU3806
uses the number 80-89.

The Commissioning of Antenna line Devices changes a slightly depending on

Hardware Configuration, for example depending on type of BTS3900 or DBS3900
with RRU or RFU, and the use of RET only, RET and a Smart Bias Tee, or RET and
Smart Tower Mounted Amplifier. But the steps above have the general procedure for
completing the commissioning of ALD.
Notes:
 MOD ANTENNAPORT can be executed only when the corresponding RRU or RFU
works properly. MOD RETPORT can be executed only when the corresponding
RRU works properly;
 The power switches of both the antenna port and RET port of the RRU cannot be
set to ON at the same time. If both power switches are set to ON, the system
returns a message indicating that the execution of the command fails;
 The undercurrent alarm threshold is usually set to 20% to 30% of the normal
working current of the equipment. The overcurrent alarm threshold is set to
150% to 200% of the normal working current of the equipment. If an antenna is
used in a special installation scenario, the alarm threshold type must be set to
UER_SELF_DEFINE. If a non-recommended ALD model is used, the alarm
threshold type must be set to UER_SELF_DEFINE;
 The result of scanning for ALD contains the information about all ALDs that are
physically connected to the BS, regardless of whether the ALDs are configured;
 Calibration must be performed after the installation of an RET antenna. If this
operation is skipped, the network coverage might be affected by an improper tilt.

Enable the ALD power

MOD RETPORT: CN=0, SRN=60, SN=0, PN=RET_PORT, PWRSWITCH=ON,
THRESHOLDTYPE=RET_ONLY_MULTICORE;
Scan for Antenna Line Devices
SCN ALD:;
Add Antenna Line Devices
ADD RET: DEVICENO=0, DEVICENAME="dev0",CTRLPORTCN=0,CTRLPORTSRN=60,
CTRLPORTSN=0, RETTYPE=SINGLE_RET, POLARTYPE=DUAL, SCENARIO=REGULAR;
Download RET configuration (this can be obtained from RET manufacturer)
DLD RETCFGDATA: OPMODE=SITE, IP="192.168.0.88", USR="admin", PWD="*****",
SRCF="C:/ret/ret.bin";
Calibrate the Remote Electrical Tilt
CLB RET: OPMODE=SITE;
Modify configuration according to Planning
MOD RETSUBUNIT: DEVICENO=0, SUBUNITNO=1, CONNCN1=0, CONNSRN1=60,
CONNSN1=0, CONNPN1=R0A, CONNCN2=0, CONNSRN2=60, CONNSN2=0,
CONNPN2=R0B, TILT=50;
MOD RETDEVICEDATA: DEVICENO=0, SUBUNITNO=1, BEARING=80;

Enable ALD power:

MOD ANTENNAPORT:
CN=0,SRN=60,SN=0,PN=R0A,PWRSWITCH=ON,FEEDERTYPE=7/8_Feeder;
MOD ANTENNAPORT:
CN=0,SRN=60,SN=0,PN=R0B,PWRSWITCH=OFF,FEEDERTYPE=7/8_Feeder;
Scan for Antenna Line Devices.
Add Antenna Line Devices.
Download RET configuration (this file can be obtained from RET manufacturer).
Calibrate the Remote Electrical Tilt.
Modify configuration according to Planning.

Enable the ALD power:

MOD ANTENNAPORT:
CN=0,SRN=60,SN=0,PN=R0A,PWRSWITCH=ON,THRESHOLDTYPE=UER_SELF_DEFINE,
UOTHD=40, UCTHD=60, OOTHD=400, OCTHD=380, FEEDERTYPE=7/8_Feeder;
MOD ANTENNAPORT:
CN=0,SRN=60,SN=0,PN=R0B,PWRSWITCH=OFF,FEEDERTYPE=7/8_Feeder;
Scan for Antenna Line Devices.
Add Antenna Line Devices:
ADD RET: DEVICENO=0, DEVICENAME="dev0",CTRLPORTCN=0,CTRLPORTSRN=60,
CTRLPORTSN=0, RETTYPE=SINGLE_RET, POLARTYPE=DUAL, SCENARIO=REGULAR;
ADD TMA: DEVICENO=10, DEVICENAME="tma0", CTRLPORTCN=0,
CTRLPORTSRN=60, CTRLPORTSN=0, SUBUNITNUM=2, CONNCN1=0, CONNSRN1=60,
CONNSN1=0, CONNPN1=R0A, CONNCN2=0, CONNSRN2=60, CONNSN2=0,
CONNPN2=R0B;
Download RET configuration (this file can be obtained from RET manufacturer).
Calibrate the Remote Electrical Tilt.
Modify configuration according to Planning.

Configure monitoring units and external alarms, with one or more of the following
commands:
ADD FMU: CN=0, MPN=0;
ADD TCU: CN=0, MPN=1;
SET ALMPORT: CN=1, SRN=0, SN=18, PN=0, SW=ON, AID=65033, PT=BOOL,
AVOL=HIGH;
Configure power modules, by running one or more of the following commands:

ADD PMU: CN=0, PTYPE=APM30, MPN=0, LSDF=DISABLE;
ADD PSU: CN=0, SN=1;
ADD BATTERY: CN=0, BTYPE=VRLA_BAT, BC=1000, HTSDF=ENABLE, LVSDF=ENABLE;

Configure time information with the following commands:

SET TIMESRC: TIMESRC=NTP;
ADD NTPC: MODE=IPV4, IP="172.166.1.205", PORT=123, SYNCCYCLE=60,
AUTHMODE=PLAIN;
SET TZ: ZONET=GMT+0800, DST=NO;
Configure synchronization information with the following commands:

ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=ETH, PN=0, IP="80.3.101.21",
MASK="255.255.252.0";
ADD IPCLKLINK: ICPT=PTP, SN=7, CNM=UNICAST, IPMODE=IPV4, CIP="80.3.101.21",
SIP="172.168.49.49", PROFILETYPE=1588V2;
SET CLKMODE: MODE=MANUAL, CLKSRC=IPCLK;

Configure transport resources and security based on the planned scenario.

Example of transmission configuration in EP mode:

ADD ETHPORT: SN=7, SBT=BASE_BOARD, PA=COPPER, SPEED=AUTO, DUPLEX=AUTO;
ADD DEVIP: SN=7, SBT=BASE_BOARD, PT=LOOPINT, PN=0, IP="8.10.10.60", MASK="255.255.255.255";
ADD IPRT: SN=7, SBT=BASE_BOARD, DSTIP="0.0.0.0", DSTMASK="0.0.0.0", RTTYPE=NEXTHOP,
NEXTHOP="80.3.101.1";
ADD EPGROUP:EPGROUPID=0,USERLABEL="HW";
ADD SCTPTEMPLATE:SCTPTEMPLATEID=0,SWITCHBACKFLAG=ENABLE;
ADDSCTPHOST:SCTPHOSTID=0,IPVERSION=IPv4,SIGIP1V4="8.10.10.60",SIGIP1SECSWITCH=DISABLE,SIGIP
2SECSWITCH=DISABLE,PN=2910,SCTPTEMPLATEID=0;
ADD SCTPPEER: SCTPPEERID=0,IPVERSION=IPv4,SIGIP1V4="8.10.10.61",
SIGIP1SECSWITCH=DISABLE,SIGIP2SECSWITCH=DISABLE,PN=2910;
ADD USERPLANEHOST: UPHOSTID=0,IPVERSION=IPv4,LOCIPV4="8.10.10.60",IPSECSWITCH=DISABLE;
ADD USERPLANEPEER: UPPEERID=0,IPVERSION=IPv4,PEERIPV4="8.10.10.62",IPSECSWITCH=DISABLE;
ADD SCTPHOST2EPGRP: EPGROUPID=0, SCTPHOSTID=0;
ADD SCTPPEER2EPGRP: EPGROUPID=0, SCTPPEERID=0;
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;
ADD S1: S1ID=0,CNOPERATORID=0,EPGROUPCFGFLAG=CP_UP_CFG,CPEPGROUPID=0, UPEPGROUPID=0;
ADD X2: X2ID=0,CNOPERATORID=0,EPGROUPCFGFLAG=CP_UP_CFG,CPEPGROUPID=0, UPEPGROUPID=0;
ADD OMCH: IP="8.10.10.65", MASK="255.255.255.255",
PEERIP="172.166.1.251",PEERMASK="255.255.255.255", BEAR=IPV4, SN=7, SBT=BASE_BOARD, BRT=NO;


Configure a sector by running the following command:

ADD SECTOR: SECTORID=0, ANTNUM=2, ANT1CN=0, ANT1SRN=60, ANT1SN=0,
ANT1N=R0A, ANT2CN=0, ANT2SRN=60, ANT2SN=0, ANT2N=R0B,
CREATESECTOREQM=FALSE;
ADD SECTOREQM: SECTOREQMID=0, SECTORID=0, ANTNUM=2, ANT1CN=0,
ANT1SRN=60, ANT1SN=0, ANT1N=R0A, ANTTYPE1=RXTX_MODE, ANT2CN=0,
ANT2SRN=60, ANT2SN=0, ANT2N=R0B, ANTTYPE2=RXTX_MODE;
Notes:
 A base station supports a maximum of 96 sectors;
 A base station supports a maximum of 192 sector antennas;
 A sector can be added with a maximum of eight antennas. After a sector is added,
operators can run the MOD SECTOR command to continue to add antennas;
 An antenna belongs only to one sector;
 When adding a sector, operators can set CREATESECTOREQM as required. The
default sector equipment contains all existing antennas in the sector. Each
antenna in the sector equipment works in TX and RX mode and is configured as a
master antenna. The antennas added through the MOD SECTOR command are
not considered as default sector equipment.

Configure a cell and activate it with the following commands:

ADD CELL: LocalCellId=0, CellName="ALFA", SectorId=0, FreqBand=7,
UlEarfcnCfgInd=NOT_CFG, DlEarfcn=2850, UlBandWidth=CELL_BW_N100,
DlBandWidth=CELL_BW_N100, CellId=100, PhyCellId=100, FddTddInd=CELL_FDD,
RootSequenceIdx=1, HighSpeedFlag=HIGH_SPEED,
CustomizedBandWidthCfgInd=NOT_CFG, EmergencyAreaIdCfgInd=NOT_CFG,
UePowerMaxCfgInd=NOT_CFG, MultiRruCellFlag=BOOLEAN_FALSE;
ADD EUCELLSECTOREQM: LocalCellId=0, SectorEqmId=1;
ADD CELLOP: LocalCellId=0, TrackingAreaId=0;
ACT CELL: LocalCellId=0;

Configure neighboring cells by running the following commands:

MOD CELLALGOSWITCH: LocalCellId=0, FreqPriorityHoSwitch=FreqPriorIFHOSwitch-
1&FreqPriorIFBlindHOSwitch-1;
MOD ENODEBALGOSWITCH: AnrSwitch=IntraRatEventAnrSwitch-
1&IntraRatFastAnrSwitch-1&IntraRatAnrAutoDelSwitch-1;
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="02", eNodeBId=236, CellId=0,
DlEarfcn=3100, UlEarfcnCfgInd=NOT_CFG, PhyCellId=236, Tac=33;
ADD EUTRANEXTERNALCELL: Mcc="460", Mnc="02", eNodeBId=236, CellId=1,
DlEarfcn=2850, UlEarfcnCfgInd=NOT_CFG, PhyCellId=236, Tac=33;
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=3100, UlEarfcnCfgInd=NOT_CFG,
CellReselPriorityCfgInd=NOT_CFG, SpeedDependSPCfgInd=NOT_CFG,
MeasBandWidth=MBW100, PmaxCfgInd=NOT_CFG, QqualMinCfgInd=NOT_CFG;
ADD EUTRANINTERFREQNCELL: LocalCellId=0, Mcc="460", Mnc="02",
eNodeBId=236, CellId=0;
ADD EUTRANINTRAFREQNCELL: LocalCellId=0, Mcc="460", Mnc="02",
eNodeBId=236, CellId=1
ADD GERANEXTERNALCELL: Mcc="460", Mnc="20", GeranCellId=1234, Lac=1234,
RacCfgInd=NOT_CFG, BandIndicator=GSM_dcs1800, GeranArfcn=515,
NetworkColourCode=0, BaseStationColourCode=0;
ADD GERANNFREQGROUP: LocalCellId=0, BcchGroupId=1, GeranVersion=EDGE,
StartingArfcn=515, BandIndicator=GSM_dcs1800, CellReselPriorityCfgInd=NOT_CFG,
PmaxGeranCfgInd=NOT_CFG;
ADD GERANNCELL: LocalCellId=0, Mcc="460", Mnc="20", Lac=123,
GeranCellId=1234;


03 - OEB206900 ENodeB LTE V100R008C10 Local Commissioning

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

03 - OEB206900 ENodeB LTE V100R008C10 Local Commissioning

Caricato da

Copyright:

Formati disponibili

0

eNodeB LTE V100R008C10 Local Commissioning

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Commissioning Prerequisites for the Transport network

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

can Commissioning the eNodeB through the LMT;

Confidential Information of Huawei. No Spreading Without Permission

Remote Commissioning on the U2000

 Site swapping (permissible downtime ≥ 1 hour);

 Deploying a new site.

For the detailed description of Remote Commissioning refer to “eNodeB LTE

Local Commissioning Through the USB Disk

 Site swapping (permissible downtime < 1 hour);

 Deploying a new site.

Confidential Information of Huawei. No Spreading Without Permission

Local Commissioning on the LMT

 Site swapping (permissible downtime < 1 hour);

 Deploying a new site.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Preparing a Software Package, Data Configuration Files, and Deployment Lists

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

The following tools are available:

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Checking a Transport Network

Confidential Information of Huawei. No Spreading Without Permission

Base station binding

 ESN-based binding mode.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

 The expected directories or files do not exist;

 The expected directories or files formats are not correct;

 Data in the USB flash drive is not encrypted or integrity-protected;

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Prerequisites for LTE service testing:

 The UE has been defined on the HSS;

 An FTP server is ready;

 A WWW server is ready.

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Testing Installation and Deployment Quality

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Pin of the USB3.0 Pin of the Ethernet

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission

Set the FTP server in the LMT PC:

Confidential Information of Huawei. No Spreading Without Permission

In special scenarios such as base station deployment or upgrade, select the

Confidential Information of Huawei. No Spreading Without Permission

Confidential Information of Huawei. No Spreading Without Permission