 The following table describes the areas in the LMT main window.

SN Area Description
1 Menu bar Provides the menu.

2 Toolbar Provides shortcut icons.

3 Navigation tree Displays the Maintenance and MML Command

4 Object window
5 Status bar
tab pages in the form of a navigation tree.
Provides the window for performing maintenance
and configuring MML commands.
Displays information, such as the user name,
connection status, and IP address of the current
login account.
 The following table describes the components of the MML Command tab page.

SN Component Description

Common Displays command execution results.

Maintenance (Alt+C)
Operation Record Displays historical commands executed in
Informatio
(Alt+R) the latest login session before you exit or
1 n pane
deregister with the LMT.
Help Information Displays help information, such as
(Alt+N) command functions and parameter
description.
• Allows you to enter a command and
the command parameters.
Manual input box • Displays the command entered in the
Command Input box or selected
from the History Command box.
Displays all the commands entered during
Command History Command the current login session and allows you to
configurati box select a command from the drop-down
2 list.
on pane
• Allows you to enter a command with
the parameters specified in the
Command Input box parameter configuration area.
• Displays the command selected from
the Navigation Tree.
Parameter Allows you to configure the parameters of
configuration area a command.
 The following table lists the tools and software that are required for commissioning an
eNodeB.
Tool and Description
Software
Portable computer Meets the requirements related to hardware, software, and
communication capability. For details, see the PC configuration
requirements in the eNodeB JAVA LMT User Guide.
Ethernet cable Connects the portable computer and eNodeB.
Test UE Works normally and has been registered in the core network.
eNodeB LMT The default IP address for the LMT is 192.168.0.49, which is
used for local commissioning.
 Global data includes the maintenance channel, eNodeB data, operator data, and tracing
area data.
 Note

 After the commissioning is complete, run the SET DHCPSW command with the
OMCH Auto-Establishment Switch parameter set to ENABLE(Enable) to turn on
the switch.

 Example

 SET DHCPSW: SWITCH=DISABLE;

 Note

 Manual eNodeB reset is required for this command to take effect. You are advised
to manually reset the eNodeB after the commissioning is completed.

 Example

 MOD ENODEB: ENODEBID=0, NAME="eNodeB1", ENBTYPE=eNodeB,

PROTOCOL=CPRI;
 Note

 The EnodeB Work Sence parameter can be set to

EMERGENCYSCENE(Emergency Scene) only when the fallback function is enabled
on the eNodeB or the Rapid system is used.

 Example

 SET ENODEBMODE: EnodeBMode=TRUNKMODE, WorkSence=NORMALSCENE,

WorkMode=NORMALMODE;
 Note

 If the eNodeB works in independent mode, only one operator can be added and this
operator must be the primary operator.

 If the eNodeB works in eRAN sharing with shared frequency mode or eRAN sharing
with separate frequency mode, only one primary operator and a maximum of five
secondary operators can be added. The primary operator must be added before the
secondary operators are added

 The mobile country code and mobile network code must be consistent with those
configured on the core network.

 Example

 ADD CNOPERATOR: CnOperatorId=0, CnOperatorName=“huawei",

CnOperatorType=CNOPERATOR_PRIMARY, Mcc="460", Mnc="06";
 Note

 The CN Operator ID parameter in this command must be set to the same value as
that in the ADD CNOPERATOR command.

 Tracking area code is used by the core network to determine the area within which
paging messages are sent. In trunking mode, a tracking area and a cell have a one-
to-one mapping relationship. In non-trunking area, a tracking area may contain
multiple cells.

 Example

 ADD CNOPERATORTA: TrackingAreaId=0, CnOperatorId=0, Tac=1;

 Note

 This command can only be used to add boards in the BBU subrack.

 If a CNPU board is to be added to a standalone eNodeB, the Board Type parameter

must be set to LMPT(LMPT).

 The message "Running this command may reboot the board." will be displayed if
this command is executed.

 Example

 ADD BRD: CN=0, SRN=0, SN=16, BT=FAN;

 ADD BRD: CN=0, SRN=0, SN=19, BT=UPEU;

 ADD BRD: CN=0, SRN=0, SN=3, BT=LBBP, WM=TDD;

 ADD BRD: CN=0, SRN=0, SN=7, BT=LMPT;

 Note

 This command is used to add an RRU chain/ring before adding an RRU to this
chain/ring.

 The Topo Type parameter can be set to CHAIN(CHAIN), RING(RING), or

LOADBALANCE(LOADBALANCE). If the eRRUs use the star or chain topology, the
Topo Type parameter must be set to CHAIN(CHAIN).

 If the AccessType parameter is set to LOCALPORT(local port), the LBBP board is

connected to the RRU through the CPRI port. If the AccessType parameter is set to
PEERPORT(peer port), the peer LBBP is directly connected to the RRU, and the
local LBBP is connected to the peer LBBP through the IDX2 port on the backplane.

 The Head Slot No. parameter indicates the slot number of the board where the
head CPRI port is located.

 The Head Port No. parameter indicates the number of the head CPRI port.

 The CPRI Line Rate parameter is a user-defined rate. If this rate is inconsistent with
the current running rate, CPRI-related alarms will be generated.

 Example

 ADD RRUCHAIN: RCN=0, TT=CHAIN, HSN=3, HPN=0, CR=AUTO;

 Note

 Before an RRU is added, an RRU chain/ring must be added by running the ADD
RRUCHAIN command.

 The RRU Chain No. parameter in this command must be set to the same value as
that in the ADD RRUCHAIN command.

 The Number of RX channels or Number of TX channels parameter indicates the

RX or TX channels used by the eRRU. The parameters are locally planned and can be
set to the number of RF ports on the eRRU.

 The RRU type parameter must be the hardware model of the RRU, which can be
queried by running the DSP BRDVER command.

 Example

 ADD RRU: CN=0, SRN=60, SN=0, RCN=0, PS=0, RT=MRRU, RS=TDL, RXNUM=4,
TXNUM=4;
 Antenna mode

 The antenna mode of sectors on a TDD network with fixed eNodeBs can be set to
the following as required:

 1T1R: An eRRU3251/eRRU3255 cell can be split to two 1T1R cells using path
division.

 2T2R: An eRRU3251/eRRU3255 cell does not need to be split. An eRRU3232,

RRU3232, or RRU3252 cell can be split to two 2T2R cells using path division.
An eRRU3253 cell can be split to four 2T2R cells using path division.

 4T4R: An eRRU3232, RRU3232, or RRU3252 cell does not need to be split. An

eRRU3253 cell can be split to two 4T4R cells using path division.

 The antenna mode of sectors in a vehicle-mounted TDD communication system

must be set to 2T2R.

 Two eRRU3232 cells can be split to four 2T2R cells using path division.

 An eRRU3253 cell can be split to four 2T2R cells using path division.

 Two eRRU3255 cells are used without path division.

 The antenna mode of sectors on an FDD network with fixed eNodeBs must be set
2T2R. An RRU3268 cell is used without path division.
 Example

 ADD SECTOR: SECN=0, GCDF=DEG, LONGITUDE=0, LATITUDE=0,

SECM=NormalMIMO, ANTM=1T1R, COMBM=COMBTYPE_SINGLE_RRU, CN1=0,
SRN1=60, SN1=0, PN1=R0A, ALTITUDE=0;
 Note

 After a GPS clock is added, the GPS clock becomes an optional reference clock for
the system.

 Example

 ADD GPS: SRN=0, SN=7;

 Note

 If the Clock Working Mode parameter is set to AUTO(Auto), the system obtains
clock signals through the GPS.

 If the Clock Working Mode parameter is set to MANUAL(Manual), the Selected

Clock Source parameter must be set to GPS(GPS Clock) and the Clock Source
No. parameter must be set to the same value as the GPS Clock No. parameter in
the ADD GPS command.

 Example

 SET CLKMODE: MODE=FREE;

 Example
 SET CLKSYNCMODE: CLKSYNCMODE=TIME;
 Note

 If the GPS is used as the reference clock, the Time Source parameter must be set to
GPS(GPS).

 If the Network Time Protocol (NTP) is used as the reference clock, the Time Source
parameter must be set to NTP(NTP). The ADD NTPC command also needs to be
executed to configure the NTP server information.

 Example

 SET TIMESRC: TIMESRC=NTP;

 Note

 The IP Mode parameter must be set to IPV4(IPv4).

 The Synchronization Period parameter indicates the interval at which the NTP
time synchronization is performed. This parameter is locally planned and the
recommended value is 360.

 If the Authentication Mode parameter is set to PLAIN(Plain), the system is

vulnerable to security risks.

 You are advised to regularly change the value of the Authentication Key
parameter to ensure system security.

 Example

 ADD NTPC: MODE=IPV4, IP="10.175.197.210", SYNCCYCLE=60,

AUTHMODE=PLAIN;
 Set the parameters as follows:

 The Time Zone parameter must be set according to the actual situation.

 The Dst Tag Information parameter is set to NO(No) by default. When it is set to
YES(Yes), the parameters related to DST start and end mode, date, and time must
be specified according to the local plan.

 Example

 SET TZ: ZONET=GMT-0800, DST=NO;

 Note

 The Slot No. parameter is set to 7, which is the slot number of the LMPT board.

 The Subboard Type parameter is set to BASE_BOARD(Base Board).

 You are advised to set the Speed parameter as required. The speed must be the
same as that on the peer port.

 If the Speed parameter is set to AUTO(Automatic Negotiation), the Duplex

parameter must be set to AUTO(Automatic Negotiation). If the Speed parameter
is set to 10M(10M), 100M(100M), or 1000M(1000M), the Duplex parameter
must be set to FULL(Full Duplex).

 Example

 SET ETHPORT: SN=7, SBT=BASE_BOARD, PA=COPPER, SPEED=AUTO,

DUPLEX=AUTO;
 Example

 ADD VLANMAP: NEXTHOPIP="10.20.1.93", MASK="255.255.255.255",

VLANMODE=SINGLEVLAN, VLANID=92, SETPRIO=DISABLE;
 Note

 A maximum of eight device IP addresses can be configured on an Ethernet port or a

port that carries an Ethernet trunk. A maximum of seven device IP addresses can be
configured on a port that carries a PPP link or an MP group.

 If IP resources are insufficient, an eNodeB can be configured with only one IP

address that is used for communications on the service links and between the
maintenance links.

 The parameters IP Address and Mask define the subnet where the eNodeB ports
can connect to the transmission device. Multiple eNodeBs can be configured on the
same subnet.

 Example

 ADD DEVIP: SN=0, SBT=ETH_COVERBOARD, PT=ETH, PN=1, IP="10.175.197.201",

MASK="255.255.255.0";

 ADD DEVIP: SN=0, SBT=ETH_COVERBOARD, PT=ETH, PN=0, IP="172.16.2.11",

MASK="255.255.255.0";
 Note:

 For example, the Destination IP parameter is 172.168.0.0 and the Mask

parameter is 255.255.0.0 (a 16-digit value). If the Destination IP parameter is set
to 172.168.7.3 and the Mask parameter is set to 255.255.0.0, an error message
will be displayed because the destination IP address is not a network IP address.

 Example

 ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="172.168.3.1",

DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="10.20.1.93",
PREF=60, DESCRI="To MME";

 ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="172.168.7.3",

DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="10.20.1.93",
PREF=60, DESCRI="To UGW";
 Note

 If the local IP address and the peer IP address are on different network segments, a
route to the peer IP address must be added by running the ADD IPRT command
before running the ADD SCTPLINK command.

 The SCTP link is used for transmission on the S1-based link and must be used with
the corresponding S1 interface.

 Example

 ADD SCTPLNK: SCTPNO=0, SN=7, LOCIP="172.16.2.11", LOCPORT=36412,

PEERIP="172.16.2.100", PEERPORT=36412, AUTOSWITCH=ENABLE;
 Note

 A maximum of 128 IP paths can be configured on an LMPT.

 The Adjacent Node ID parameter indicates the ID of the adjacent signaling point to
which the IP path belongs. The Adjacent Node ID parameter is valid only when the
Application Type parameter is set to X2(X2). The Adjacent Node ID parameter
must be set to the ID of the X2 interface. The SCTP link referenced by this X2
interface must be an IPv4 SCTP link.

 Example

 ADD IPPATH: PATHID=0, SN=7, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=DISABLE,

LOCALIP="172.16.2.11", PEERIP="172.16.2.100", ANI=0, APPTYPE=S1,
PATHTYPE=ANY;
 Note

 The S1 SCTP link ID parameter must be set to the same value as the SCTP link No
. parameter in the ADD SCTPLNK command.

 The CN operator ID parameter must be set to the same value as the CN Operator
ID parameter in the ADD CNOPERATOR command configured as global data.

 Example

 ADD S1INTERFACE: S1InterfaceId=0, S1SctpLinkId=0, CnOperatorId=0;

 Note
 An eNodeB can be configured with a maximum of two remote OM channels, which
are the active and standby OM channels. The local IP addresses of the two remote
OM channels cannot be on the same network segment.
 The IP address of a remote OM channel must be on a different network segment
from the IP address for local maintenance.
 The binding route ensures the communications between the two ends of an OM
channel. If the Binding Route parameter is set to YES(Yes), the following
parameters must also be configured:
 Destination IP: This parameter indicates the IP address or the IP network
segment address of the eOMC910. This parameter must be configured
according to the network plan.
 Destination Mask: This parameter must be configured according to the
network plan.
 Route Type: This parameter must be set to NEXTHOP(Next Hop), and the
Next Hop IP parameter must be configured according to the network plan.
 Example
 ADD OMCH: IP="10.175.197.201", MASK="255.255.255.0",
PEERIP="10.175.197.210", PEERMASK="255.255.252.0", BEAR=IPV4, SN=7,
SBT=BASE_BOARD, BRT=NO;
 Bands for TDD

E-UTRA Downlink Uplink

Operating F DL_low F UL_low
Band NOffs-DL NOffs-UL
(MHz) (MHz)
33 1900 36000 1900 36000
34 2010 36200 2010 36200
35 1850 36350 1850 36350
36 1930 36950 1930 36950
37 1910 37550 1910 37550
38 2570 37750 2570 37750
39 1880 38250 1880 38250
40 2300 38650 2300 38650
41 2496 39650 2496 39650
42 3400 41590 3400 41590
43 3600 43590 3600 43590
44 703 45590 703 45590
…
60 (2) 380 18360 380 18360
60 (3) 566 19260 566 19260
61 1437 64436 1437 64436
62 1785 64736 1785 64736
63 1800 64936 1800 64936
64 2545 65236 2545 65236
 Bands for FDD

E-UTRA Downlink Uplink

Operating
F DL_low F UL_low
Band NOffs-DL NOffs-UL
(MHz) (MHz)
1 2110 0 1920 18000
2 1930 600 1850 18600
3 1805 1200 1710 19200
4 2110 1950 1710 19950
5 869 2400 824 20400
6 875 2650 830 20650
7 2620 2750 2500 20750
8 925 3450 880 21450
9 1844.9 3800 1749.9 21800
10 2110 4150 1710 22150
11 1475.9 4750 1427.9 22750
12 729 5010 699 23010
13 746 5180 777 23180
14 758 5280 788 23280
… reserved
17 734 5730 704 23730
18 860 5850 815 23850
19 875 6000 830 24000
20 791 6150 832 24150
21 1495.9 6450 1447.9 24450
22 3510 6600 3410 24600
23 2180 7500 2000 25500
24 1525 7700 1626.5 25700
25 1930 8040 1850 26040
26 859 8690 814 26690
27 852 9040 807 27040
28 758 9210 703 27210
 EARFCN: E-UTRA Absolute Radio Frequency Channel Number
 The three identities in a group would usually be assigned to cells under the control of the
same eNodeB.
SSS - One of 168
Group Identities

eNB eNB

eNB
504 Unique Cell
Identities PSS - One of 3 Identities

 PCI planning is applied in intra-frequency networking.

 Principle for PCI planning:

 The reuse distance shall be as large as possible.

 Make RS in adjacent cells not occupy the same subcarrier position. The value of
PCI/3 should be 0, 1, or 2 in each eNodeB.
 Subframes fall into three types: uplink, downlink, and special.

 Uplink and downlink subframes transmit uplink and downlink data, respectively.
Uplink and downlink subframes are independent of each other in the time domain.

 A special subframe consists of the downlink pilot timeslot (DwPTS), GP, and uplink
pilot timeslot (UpPTS). A special subframe can be used for downlink data
transmission, but not for uplink data transmission. Therefore, a special subframe is
considered a downlink subframe.

 3GPP TS 36.211 defines seven uplink-downlink subframe configurations.

 For example, downloading files and watching videos online require high downlink rates,
while real-time monitoring requires high uplink rates. To meet such requirements, 3GPP TS
36.211 defines uplink-downlink subframe configurations.

 Among these configurations, an appropriate uplink-downlink subframe configuration is

used for asymmetric data transmission. This ensures that limited spectral resources can be
used efficiently.

 Currently, Huawei supports three uplink-downlink subframe configurations.

 Configuration 1, in which the ratio of uplink subframes to downlink subframes is 2:2

 Configuration 2, in which the ratio of uplink subframes to downlink subframes is 1:3

 Configuration 0, in which the ratio of uplink subframes to downlink subframes is 3:1

 The guard period(GP) in the special subframe ensures uplink-downlink switching.

 If the DwPTS is longer than 9 symbols, the special subframe can transmit downlink
services.

 The length of the GP determines the coverage radius of a cell.

 If the UpPTS contains only one symbol, the symbol can transmit only SRSs. If the
UpPTS contains 2 symbols, the UpPTS can transmit format 4 physical random access
channel (PRACH) and sounding reference signals (SRSs).

 Currently, Huawei supports three special subframe configurations. The configurations can
be changed based on site requirements.

 Configuration 7, in which the ratio of DwPTS:GP:UpPTS is 10:2:2

 Configuration 4, in which the ratio of DwPTS:GP:UpPTS is 12:1:1

 Configuration 5, in which the ratio of DwPTS:GP:UpPTS is 3:9:2

 Configuration 6, in which the ratio of DwPTS:GP:UpPTS is 9:3:2

 Note

 Adding the operator information to a cell in active state will result in automatic reset
of the cell.

 The Local cell ID parameter indicates the cell ID in an eNodeB and must be set to
the same value as the Local cell ID parameter in the ADD CELL command.

 The Tracking area ID parameter indicates the identity of a tracking area and is
locally planned. This parameter must be set to the same value as the Tracking area
ID parameter in the ADD CNOPERATORTA command configured as global data.

 Example

 ADD CELLOP: LocalCellId=0, TrackingAreaId=0;

 Note

 Only an unblocked cell can be properly set up.

 Before running this command, ensure that the cell operator and carrier resources
have been configured.

 Example

 ACT CELL: LocalCellId=0;

 Note

 Resetting an eNodeB causes service interruption. The eNodeB restarts automatically.

 The system returns a success message irrespective of whether the eNodeB is

successfully reset or not.

 Example

 RST ENODEB:;
 Note

 The LMT is communicating with the eNodeB properly.

 The configured FTP server connects to the eNodeB on the same network segment
and is functioning properly.

 There is no firewall between the FTP server and the eNodeB.

 Each FTP user has the permission to read a specified folder.

 The eNodeB license file is stored on the FTP server.

 Example

 DLD ELICENSE: MODE=IPV4, IP="192.168.0.100", USR="admin",

PWD="********", FN="TTR30_eNB_License_Tmp.dat";