ENodeB LTE V100R008C10 Data Introduction For Initial Configuration ISSUE 1.01

eNodeB LTE
V100R008C10 Data
Introduction for Initial
Configuration
www.huawei.com
Copyright © 2015 Huawei Technologies Co., Ltd. All rights reserved.

Internal use only!
This is a customer training slide from LS Dept. Without permission
of LS,please do not send or present this slide to customer!

References
 3900 Series Base Station Product Documentation (Product
Version: V100R010C10)
Copyright © 2015 Huawei Technologies Co., Ltd. All rights reserved. Page2
Objectives
 Upon completion of this course, you will be able to:
 Outline the meaning of the common parameters in device,
transport and radio data
 Implement initial data preparation by MML for basic scenario
 Implement data preparation for specific scenarios by MML
Contents
1. eNodeB Data Configuration Introduction
2. Common Data Parameters Introduction
3. Data Preparation in Specific Scenarios
Contents
Introduction to Data Configuration Tools
 There are two tools to help configure data for eNodeB:
 CME and LMT
 To understand data parameters well, MML used in LMT is the best way.
MML command window
Initial Configuration Procedure by MML
 An eNodeB has default configuration data

before delivery. You need to remove the
redundant data, like redundant RF data,
board data, RRU chain data, etc, in the
default configuration data if MML commands
are used for initial configuration.
Where to Get Data Value
BOQ from market
Configuration rules
Network design
Hardware configuration &
1. Capacity planning
Site configuration cable connection
2. Radio design
1. Transport networking
2. Data negotiation
3. Configuration planning
4. Data template
Basic Radio Device Transport

Data data Data Data
Contents
Contents
2.1 eNodeB Basic Data
2.2 eNodeB Device Data
2.3 eNodeB Transport Data
2.4 eNodeB Radio Data
Common Basic Data List
Function Area MO and MML Command
ENODEBFUNCTION
eNodeB function
(ADD ENODEBFUNCTION)
NE configuration attributes NE (SET NE)
•CNOPERATOR (ADD CNOPERATOR)

Operator
•CNOPERATORTA (ADD CNOPERATORTA)
NE maintenance mode Equipment (SET MNTMODE)
Add an eNodeB Function
ID of the application referenced by

an eNodeB function, which
depends on the MO application.
 Before adding an eNodeB function, DSP APP to check the application ID with
application type set to be eNodeB.
On an LTE single-mode
eNodeB, an Application MO
with the AID parameter being
1 has been configured by
default.
Set NE
Specify the site of the NE. When multiple

NEs are deployed at the same site, these
NEs have the same deployment identifier.
Function G U L
NE NE 1:BTS3900 GSM NE2: BTS3900
UPEU
RAT Deployment F
A GTMU
N WBBP
UPEU
LBBP UMPT
Hybrid-MPT G&[U*L]
Add an Operator
If an operator is added on
multiple eNodeBs managed by
one NMS, the same operator ID
must be configured.
An operator is uniquely identified

by the PLMN ID that is
comprised of the MCC and MNC.
The CN operator type can be the
primary operator or a secondary
operator.
Secondary operator is added in eRAN
sharing mode. only one primary
operator and a maximum of five
secondary operators can be added.
Add Tracking Area Configuration for
CN Operator
An operator can be
configured with a maximum of
18 TACs
Index of the operator, quoted

from ADD CNOPERATOR.
TAC is used by the EPC to
determine the area within
which paging messages are
sent.
Set Special Status of NE
The maintenance mode can be set

to NORMAL, INSTALL, EXPAND,
UPGRADE, TESTING. The status
is set to TESTING by default by
the manufacturers.
When the NE is in the special

status, the way of alarm reporting
is changed and the performance
measurement is unbelievable.
Questions
 What is the use of Deployment Identifier in SET NE?
 Do we need to ADD ENODEBFUNCTION for an LO site

during initial data configuration?
Contents
Procedure for Configuring eNodeB
Device Data
Start
Configure cabinets and BBU3900 device data
Configure RF unit data
Configure ALDs data (Optional)
Configure monitoring units data (Optional)
Configure power modules data (Optional)
Configure time data
Configure synchronization data
End
Page19
Common Device Data List about
Hardware
Function Area Subfunction Area MO and MML Command

Cabinets and •Cabinet (ADD CABINET)
subracks •Subrack (ADD SUBRACK)
Cabinet and BBU3900
device data •add boards based on the physical
Boards in the
board configurations in the BBU
BBU3900 subrack
(ADD BRD)
•RRUCHAIN (ADD RRUCHAIN)

RF unit data RRU/RFU
•RRU (ADD RRU)
Add a Cabinet
The cabinet type can be set to APM30,

APM100, APM200, PS4890, OMB, TMC, BBC,
RFC, BTS3900, BTS3900L, BTS3900D,
BTS3012_SRAN, BTS3012AE_SRAN,
BTS3012II_SRAN, TP48300A, VIRTUAL,
BTS3900AL, TP48600A, ILC29.
“VIRTUAL” is set when the type of a cabinet
is not specified within the value range.
Add a Subrack for BBU or RFU
The cabinet number of
the subrack, quoted from
When adding a subrack
ADD CABINET.
for BBU, 0 or 1 should be
set to the subrack No..
The subrack No. can

be set to 0~1, or 4~5.
When adding a subrack for

RFU, 4 or 5 should be set
to the subrack No..
Add an MPT Board
The number of the
The number of the subrack where the board
cabinet where the board is located, quoted from
is located, quoted from ADD SUBRACK with
ADD CABINET. subrack set to 0 or 1.
When adding an MPT

board, slot No. can
be set to 6~7.
Add an LBBP Board
 LBBP is LTE only BBP board.
 When adding an LBBP board, Work Mode is specified.

The subrack No. is
The cabinet No. is quoted quoted from ADD
from ADD CABINET. SUBRACK with subrack
set to 0 or 1.
When adding an
LBBP board, slot No.
can be set to 0~5.
Add an UBBP Board
 UBBP board is a newly introduced board since SRAN9.0 (eRAN7.0),
aiming to support GUL co-baseband processing.
 When adding a UBBP board, Base Band Work Standard is specified,

but LTE FDD and LTE TDD can’t be supported by co-BBP.
This parameter is used for

UMTS mode. For LTE, it is
always set to “FULL”.
Add FAN and UPEU
When adding an FAN

board, slot No. must
be set to 16.
When adding an
UPEU board, slot No.
can be set to 18~19.
Add an RRU Chain
 Before adding an RF unit, an RRU chain/ring need to be added, which is
designed to be quoted when adding an RF unit.
ID of the RRU chain. It The type of the topology.
uniquely identifies a chain The Value can be set as
within a base station. CHAIN, RING, and
The slot
number of the LOADBALANCE.
board where
the head CPRI
port is located,
quoted from
ADD BRD for
LBBP board.
The number of the CPRI port,

The user-defined rate. The value locating in LBBP board, to
AUTO indicates the the auto which the configuring
negotiation mode is adopted. RRUCHAIN is head to.
Add an RFU
The number of the cabinet
where the RFU is located, When adding an RFU,
quoted from ADD subrack No. need to be
CABINET. set to 4~5, quoted from
ADD SUBRACK.
ID of the
RRU chain,
quoted from
ADD
RRUCHAIN.
The number of RX and TX

channels of the RFU.
Add an RRU When adding an RRU,
subrack No. need to be
set 60~254, and the
slot No. is fixed to be 0.
ID of the
RRU chain,
quoted
from ADD
RRUCHAI
N.
The position where the

RRU is installed in the
topology. TRUNK indicates
that the RRU is located on
the main chain. The mailn
chain is connected to the
optical port on the LBBP.
.
Common Device Data List about Time
and Clock
Function Area Subfunction Area MO and MML Command
•TZ (SET TZ)

•TIMESRC (SET TIMESRC)
•NTPC (ADD NTPC, SET
Time data -
MASTERNTPS) which must be
configured when an eNodeB uses NTP
as time source.
•GPS reference clock •GPS (ADD GPS)
•IEEE1588 V2 •IPCLKLNK (ADD IPCLKLINK)
Synchronization
reference clock •SYNCETH (ADD SYNCETH)
data
•Ethernet reference •TASM (SET CLKMODE and SET
clock CLKSYNCMODE)
Set the Time Zone & the Daylight
Saving Time (DST)
DST start date can be set

later than the end date, to
set the DST information for
the southern hemisphere.
Set the Time Source
 If NTP is set for eNodeB time source, a maximum of four NTP servers
can be added by ADD NTPC, and use SET MASTERNTPS to set an NTP
server as a master NTP server
Basic Concept about Clock Synchronization
• Clock synchronization means that the frequencies or phases of clock
signals maintain a precise relationship.
 Frequency synchronization: Two signals have the same number of pulses in
the same interval. The sequence, start time, and end time of each pulse can be
different for the two signals.
 Time synchronization: Two signals have the same frequency, phase, and pulse
sequence.
Copyright © 2015 Huawei Technologies Co., Ltd. All rights reserved. Page 33
Synchronization Requirements of
LTE Base Stations
 In wireless applications, the clocks of different base stations must be
synchronized to a certain precision. Otherwise, call drops may occur
when UEs are handed over between base stations. Base stations in
FDD mode must achieve frequency synchronization. Base stations in
TDD mode must achieve time synchronization.
Frequency Precision Phase Synchronization

RAT
Requirement Requirement
LTE TDD 0.05 ppm 3 us
LTE FDD 0.05 ppm NA
Note: Some FDD features also require time synchronization, like eICIC.
Add a GPS
Based on the feeder length, the feeder
delay is calculated to ensure the clock
accuracy. The clock accuracy is
affected if the error between the value
of this parameter and the actual feeder
length is greater than 20 m(66 ft).
The priority of the clock source with

value range 1~4. The value 1 indicates
the current clock source has the
highest priority.
Add an IP Clock Link
 Client IP need to be quoted from existing device IP. So before adding an
IP clock link, run the ADD DEVIP command to add a device IP address
for the port.
The Client IP address, quoted from

ADD DEVIP, is set in the same
network segment as the IP
address of the IP clock server.
Set the System Clock
 set the working mode of the reference clock source.
 set the clock synchronization mode of a BS.
Questions
 What are the common device data that need to be
configured?
Contents
Contents
2.3.1 Procedure for Configuring eNodeB Transport Data
2.3.2 IP Configuration
2.3.3 Introduction to VLAN and VLAN Configuration
2.3.4 Application of Transmission Layer Configuration
E-UTRAN Transport Protocol Stack
• S1 and X2 interface are both divided into the user plane and control
plane. The X2 interface is required to be the same as the S1.
Control Plane User Plane

Radio
Radio Network
Network S1-AP
Layer
Layer
GTP-U
SCTP
UDP
Transport IP
NetworkL Transport IP
ayer Network
Data link layer Layer Data link layer
Physical layer Physical layer
• E-UTRAN S1 protocol stack
Transport Data
Start
Add Ethernet port to configure physical layer
Add device IP and IP route to configure the routing in transmission layer
Configure VLAN for the link layer
Configure the application in transmission layer
End
Contents
Common Transport Data of IP
Physical layer ETHPORT (ADD ETHPORT)
When VLAN networking is planned on the basis of the next hop's IP address, the
MOs that need to be configured are as follows:
Link layer •VLANMAP (ADD VLANMAP)
•DSCPMAP (SET DSCPMAP)
•VLANCLASS (ADD VLANCLASS)
•DEVIP (ADD DEVIP)

Transmission layer
•IPRT (ADD IPRT)
Configure an Ethernet Port
Indicates whether an Ethernet port is

an electrical port or optical port.
When the system starts, the system
Speed must be set to the binds an Ethernet port to an optical
same value as that of the port preferentially if the default value
peer port. of the port attribute is AUTO.
Add a Device IP Address
A maximum of eight The port where IP

device IP addresses address is located,
can be configured on quoted from ADD
an Ethernet port. ETHPORT.
IP address configured for the port.

Index of a VRF instance. For Multiple IP addresses can be
FDD mode, only VRF with configured on the same port by
number 0 is applied. multiple ADD DEVIP.
Add a Static IP Route
 Based on the actual networking, multiple IP routes can be
added to different destination IP by executing the following
MML multiple times.
Contents
What is VLAN?
 A VLAN covers a broadcast area and generally a network segment is
planned as a VLAN.
 VLANs provide two functions:

 Prevent broadcast storms and improve network security by communicating
with each other only through routes.
 Assign different VLAN priorities to frames forwarded by the data link layer.
That plan VLAN with different priority in a network is like divide one meeting room into several
small meeting room based on different topic
How is VLAN Featured in an Ethernet Frame?
6 bytes 6 bytes 2 bytes 46~1500 bytes ４ bytes

Length/
DMAC SMAC TAG Data FCS
Type
4 bytes
16 bits
Ethernet Type = Ox8100 3bit PRI 1bit CFI 12bit VLAN ID

Priority: It specifies the VLAN priority. A large value
indicates a high priority.

VLAN ID: It indicates which VLAN the frame belongs to.
 A TAG is added in an frame to feature the frame as a VLAN-tagged

frame, as shown in the above figure.
 The VLAN tag field consists of 4 parts.
How is VLAN Planned in LTE Network?
 During the configuration of an S1 interface, X2 interface, or OM
channel, whether to configure VLANs depends on the operator's
requirements and the status of the existing network.
 If VLAN is configured, based on network deployment, both the

eNodeB and a layer 2 switch can attach VLAN tags to packets.
However, the eNodeB is recommended.
VLAN Mode and Configuration
 For mapping VLAN priority and DSCP, Huawei eNodeB supports two
VLAN modes: Single VLAN mode and VLAN group mode.
 VLAN group mode is used when different user data traffic flows are
required to enter different VLANs.
 Configuration Relationship
 In single VLAN mode
VLAN tag VLANMAP
DSCPMAP
DSCP VLAN priority VLAN ID Next hop IP
 In VLAN group mode

Huawei VLAN Group
VLANCLASS VLANMAP
VLAN tag Next hop IP
Traffic type VLAN priority VLAN ID
(DSCP)
Add Mapping from Next Hop IP to VLAN in
Single Mode
• Default mapping between DSCP values

and VLAN priorities DSCP Value
DSCP Value VLAN Priority
When this parameter is
set to DISABLE, the 56 to 63 7
default DSCP-VLAN 48 to 55 6
priority mapping is
applied. But if the 40 to 47 5
mapping is configured 32 to 39 4
by SET DSCPMAP, the 24 to 31 3
configured mapping is
applied. 16 to 23 2
8 to 15 1
0 to 7 0
Set the DSCP to VLAN Priority Mapping
Configuration
the priority of a DSCP. A

larger value of this
parameter indicates a
higher priority.
 Different traffic flows entering the same VLAN
Add Mapping from Next Hop IP to
VLAN in Group Mode
VLANGROUP is
set for “VLAN
Mode” parameter.
•Mapping between
traffic types and
Value range: USERDATA, SIG, OM_HIGH,
VLAN tags
OM_LOW, and OTHER.
If non-USERDATA is selected, default DSCP
values are applied. But for USERDATA ,
DSCP values need to be configured in “User
Data Service Priority” parameter.
Contents
Common Transport Data of Application in
Transmission Layer
MO and MML Command
Function Area
Link Mode EndPoint Mode
•EPGROUP: Add the MOs SCTPHOST, SCTPPEER,

USERPLANEHOST and USERPLANEPEER to EPGROUP
thought the following MML commands: ADD
•IPPATH (ADD SCTPHOST2EPGRP, ADD SCTPPEER2EPGRP, ADD
IPPATH) UPHOST2EPGRP, ADD UPPEER2EPGRP
Transmission •SCTPLNK (ADD •USERPLANEHOST (ADD USERPLANEHOST)
layer SCTPLNK) •(Optional) USERPLANEPEER: manually configured or
•CPBEARER automatically created by the system. (ADD USERPLANEPEER)
(ADD •SCTPTEMPLATE (ADD SCTPTEMPLATE)
CPBEARER) •SCTPHOST (ADD SCTPHOST)
•SCTPPEER: This MO is mandatory for S1 self-setup and
optional for X2 self-setup. If it is not configured for X2 self-setup,
the system automatically creates this MO. (ADD SCTPPEER)
Other Transport Data of Application for
Link Mode
MO and MML Command
Function Area
Link Mode EndPoint Mode
•ENODEBPATH: defining the application

attributes of IP paths. (ADD
•S1 (ADD S1)
Interface information ENODEBPATH)
•X2 (ADD X2)
•S1INTERFACE (ADD S1INTERFACE)
•X2INTERFACE (ADD X2INTERFACE)
Maintenance channel OMCH (ADD OMCH)
Add OM Channel
Local IP address of a remote maintenance
channel, which can be quoted from ADD
DEVIP, or directly added by ADD OMCH.
If Local IP is added here, eNodeB will
generate a device IP, which can be queried
by DSP DEVIP.
If Local IP and Peer IP are on different

network segments, a route must be
bound to the channel, and “YES” is set
to Binding Route.
The route is indicated by Route Index,
which is quoted from ADD IPRT.
Link Mode and End Point (EP) Mode
 S1 and X2 interfaces can be configured in two modes: link
configuration mode and end point mode.
 Link configuration mode: traditional configuration mode.
 A transmission link is configured directly by MO of link. MOs to be
configured: SCTPLNK, CPBEARER, IPPATH, ENODEBPATH,
S1INTERFACE, and X2INTERFACE.
 End point configuration mode: configuration mode for link self-setup.

 During self-setup, the eNodeB automatically creates an S1-C, S1-U, X2-C,
or X2-U interface based on the configured end point MOs.
Link Mode – Configure User Plane Link
 Add IPPATH
Type of the IP path. ANY indicates

that this IP Path can be used to
carry services of any QoS and
hence is used to carry the service
without a specified DSCP.
Indicates whether to enable the

GTP-U static detection function for
a link.
Link Mode – Configure Control Plane Link
 Add SCTP link
These parameters
are included in MO
SCTPTEMPLATE,
which are used for
establishing control
plane link in EP
mode.
Link Mode – Add Control Port Bearer
 A Control Port bearer MO consists of the parameters related to
bearers for application-layer control interfaces of S1 and X2.
The number of a link carried

on the CP bearer, quoted
from ADD SCTPLNK.
Link Mode – Add S1/X2 Interface
ID of the operator that

owns the S1 interface, ID of the control port bearer
quoted from ADD for the S1 interface, quoted
CNOPERATOR. from ADD CPBEARER.
Control mode of the X2 interface,

which determines the control
policies of users and the SON
function on the X2 interface.
Link Mode – Add the Application Type of
the IP path
 ENODEBPATH is newly added in eRAN6.0.
 An eNodeBPath object must be configured. If it is not configured,

 UEs may not be able to access the network
 X2 user-plane handovers may fail
 No alarm will be reported when an IPPATH is faulty.
ID of the IP path, quoted

from ADD IPPATH.
EP Mode - Procedure for Creating
eNodeB1 S1/X2 Interface
 Procedure for configuring an S1 interface in end point configuration mode
 Note:
 The procedure for configuring an
X2 interface in end point
configuration mode is the same.
EP Mode – Add an SCTP Parameter Template
ID of the SCTP parameter
template, which will be quoted by
SCTPHOST.
Indicates whether to switch back

to the primary path upon
restoration of the primary path. If
the primary path is unavailable,
the SCTP link will be switched to
the secondary path.
EP Mode – Add an EP Group
ID of the end point group to

which an end point belongs.
Indicates whether to enable

the ACL rule self-configuration
function for packet filtering.
EP Mode – Add an User-plane Host
• Add a user-plane host to specify user-plane information about the
local end of the S1 interface
ID of the user-plane host,

which will be added to
EPGROUP.
The IP Address of the

user plane host
EP Mode – Add an User-plane Peer
• Add a user-plane peer to specify user-plane information about

the peer end of the S1 interface
ID of the user-plane peer,
which will be added to
EPGROUP.

user plane peer
Indicates whether to enable

the GTP-U static detection
function for a link.
EP Mode – Add an SCTP Host
• Add an SCTP host to specify control-plane information about the
local end of the S1 interface ID of the SCTP host, which
will be added to EPGROUP.

control plane host.
The number of the
local SCTP port,
which is used in
automatic setup of
a SCTP link.
ID of the SCTP parameters
template referenced by the SCTP
link that is automatically set up.
EP Mode – Add an SCTP Peer
• Add an SCTP peer to specify control-plane information about the

peer end of the S1 interface
ID of the SCTP peer, which
will be added to EPGROUP.

control plane peer. The number of
the peer SCTP
port.
EP Mode – Add the CP/UP Host/Peer to the
EP Group
EP Mode – Add an S1 Object
• Add an S1 MO to specify transport resources for the S1 interface
ID of the control-plane
end point group used
the S1 object ID.
by the S1 object.
Indicates whether to
ID of the user-plane
configure the control-plane
end point group used
or user-plane end point
by the S1 object.
group.
Questions
 Why does VLAN need to be planned for LTE networking?
 Can single VLAN mode replace VLAN group mode? Why?
 Why do you think end point configuration mode is brought in?
 Which MOs need to be configured for link configuration mode?
 Which MOs need to be configured for end point configuration

mode?
Contents
Contents
2.4.1 Procedure for Configuring Radio Data
2.4.2 Introduction to Relationships between Cell and Sector & Sector and
Cell Configuration
2.4.3 Introduction to Frequency Knowledge & Cell Configuration
2.4.4 Introduction to PCI Planning & Cell Configuration
2.4.5 Introduction to CP Planning & Cell Configuration
2.4.6 Introduction to PRACH Planning & Cell Configuration
2.4.7 Introduction to Mobility Management & Neighbor Cell Configuration
Radio Data
Start
Configure sectors
Configure RAN Sharing (Optional)
Configure cells
Configure beamforming (optional)
Configure neighbor cells (optional)
End
Page81
Common Radio Data

Sector SECTOR (ADD SECTOR)
SECTOREQM (ADD SECTOREQM)
Cell •Cell (ADD CELL)
•EUCELLSECTOREQM (ADD EUCELLSECTOREQM)
•CellOp (ADD CELLOP)
Neighboring cell •CellAlgoSwitch (MOD CELLALGOSWITCH)

(Optional) •ENodeBAlgoSwitch (MOD ENODEBALGOSWITCH)
•EutranExternalCell (ADD EUTRANEXTERNALCELL)
•EutranInterNFreq (ADD EUTRANINTERNFREQ)
•EutranInterFreqNCell (ADD EUTRANINTERFREQNCELL)
•EutranIntraFreqNCell (ADD EUTRANINTRAFREQNCELL)
•HoMeasComm (MOD HOMEASCOMM)
•InterFreqHoGroup (ADD INTERFREQHOGROUP)
•IntraFreqHoGroup (ADD INTRAFREQHOGROUP)
Contents
Cell Configuration
Relationship between Cells and Sectors
 A cell is an area where radio communication services are
provided. Based on the mapping between cells and sectors, cells
are classified into single-sector and multi-sector cells.
• Multi-sector cell is
• Single-sector cell is to join multiple
the kind of most sectors into one
common and cell, for providing
traditional cells radio coverage over
applied. a wide area.
Definitions of the Sector and SectorEqm
 In eRAN6.0, Sector is newly defined, SectorEqm and eUCellSectorEqm
are added.
 A sector is a radio area covered by a set of RF antennas with the same
coverage.
 Sector equipment is a set of RF antennas that can transmit or receive signals.

This set of antennas must belong to a sector.
 Cell and SectorEqm are binded through eUCellSectorEqm.
• MO relationships
• Generally, one Sector need to be configured with only one SectorEqm.
Add a Sector & Set Antennas for it
the number of antennas

to be added by default.
Indicates whether to add the default

sector equipment. If “TRUE” is
Indicates the clockwise angle chosen, the ID of the default sector
in degrees between the sector equipment to be added.
antenna and the direction of
the north.
Add a Cell
The two offsets
are used to
control handover.
Configured
for the
feature of Configured for
SFN. the feature of
Compact
bandwidth
Configured
for the
feature of
CPRI
compression
Bind Cell with Sector Equipment
Indicates the ID of the

ID of cell within an eNodeB
sector equipment that
need binding antenna,
serves the cell, quoted
quoted from ADD CELL.
from ADD SECTOR or
ADD SECTOREQM.
Questions
 Assume that a sector is 1T1R, which an FDD cell of 20MHz
bandwidth is established on. Please give the MML draft for the
above radio scenario.
Contents
Cell Configuration
LTE Frequency Bands
 LTE is designed to operate in these frequency bands：

 2.1GHz, 1.9GHz, 1.7GHz, 2.6GHz, 900 MHz, 800 MHz, 450 MHz,
etc , refer to 36.101 for details.
 Transmission bandwidth could be:
Channel bandwidth BWChannel [MHz] 1.4 3 5 10 15 20
Transmission bandwidth configuration
6 15 25 50 75 100
NRB
Channel Bandwidth [MHz]
Transmission Bandwidth Configuration [RB]
Transmission
Bandwidth [RB]
Channel edge
Channel edge
Resource block
Active Resource Blocks DC carrier (downlink only)
LTE Release 10 Bands for FDD
E-UTRA Downlink Uplink
Operating FDL_low
NOffs-DL Range of NDL FUL_low (MHz) NOffs-UL Range of NUL
Band (MHz)
1 2110 0 0 – 599 1920 18000 18000 – 18599
2 1930 600 600 - 1199 1850 18600 18600 – 19199
3 1805 1200 1200 – 1949 1710 19200 19200 – 19949
4 2110 1950 1950 – 2399 1710 19950 19950 – 20399
5 869 2400 2400 – 2649 824 20400 20400 – 20649
6 875 2650 2650 – 2749 830 20650 20650 – 20749
7 2620 2750 2750 – 3449 2500 20750 20750 – 21449
8 925 3450 3450 – 3799 880 21450 21450 – 21799
9 1844.9 3800 3800 – 4149 1749.9 21800 21800 – 22149
10 2110 4150 4150 – 4749 1710 22150 22150 – 22749
11 1475.9 4750 4750 – 4949 1427.9 22750 22750 – 22949
12 729 5010 5010 – 5179 699 23010 23010 – 23179
13 746 5180 5180 – 5279 777 23180 23180 – 23279
14 758 5280 5280 – 5379 788 23280 23280 – 23379
… reserved
17 734 5730 5730 – 5849 704 23730 23730 – 23849
18 860 5850 5850 – 5999 815 23850 23850 – 23999
19 875 6000 6000 – 6149 830 24000 24000 – 24149
20 791 6150 6150 – 6449 832 24150 24150 – 24449
21 1495.9 6450 6450 – 6599 1447.9 24450 24450 – 24599
22 3510 6600 6600 – 7399 3410 24600 24600 – 25399
23 2180 7500 7500 – 7699 2000 25500 25500 – 25699
24 1525 7700 7700 – 8039 1626.5 25700 25700 – 26039
25 1930 8040 8040 – 8689 1850 26040 26040 – 26689
26 859 8690 8690 – 9039 814 26690 26690 – 27039
27 852 9040 9040 – 9209 807 27040 27040 – 27209
28 758 9210 9210 – 9659 703 27210 27210 – 27659
Page 92
LTE Release 10 Bands for TDD
Downlink Uplink
E-UTRA
Operating FDL_low
Band NOffs-DL Range of NDL FUL_low (MHz) NOffs-UL Range of NUL
(MHz)
33 1900 36000 36000 – 36199 1900 36000 36000 – 36199
34 2010 36200 36200 – 36349 2010 36200 36200 – 36349
35 1850 36350 36350 – 36949 1850 36350 36350 – 36949
36 1930 36950 36950 – 37549 1930 36950 36950 – 37549
37 1910 37550 37550 – 37749 1910 37550 37550 – 37749
38 2570 37750 37750 – 38249 2570 37750 37750 – 38249
39 1880 38250 38250 – 38649 1880 38250 38250 – 38649
40 2300 38650 38650 – 39649 2300 38650 38650 – 39649
41 2496 39650 39650 –41589 2496 39650 39650 –41589
42 3400 41590 41590 – 43589 3400 41590 41590 – 43589
43 3600 43590 43590 – 45589 3600 43590 43590 – 45589
44 703 45590 45590 – 46589 703 45590 45590 – 46589
Page 93
Carrier Frequency EARFCN Calculation
FDL = FDL_low + 0.1(NDL - NOffs-DL)
eNB
FUL = FUL_low + 0.1(NUL - NOffs-UL)

UE
• Example
Page 94
Frequency Related Parameters in ADD CELL
Indicates whether to
configure the UL EARFCN
of the cell. If NOT_CFG is
set, default value is set for
Uplink EARFCN.
For an FDD cell, the UL
EARFCN equals the sum of
the DL EARFCN and
18000. For a TDD cell, the
UL EARFCN equals the DL
EARFCN.
Questions
 Assume the downlink central frequency given is 2125.5MHz, and
the uplink central frequency given is 1725.5MHz. Please calculate
the downlink EARFCN.
Contents
Cell Configuration
PCI and Synchronization signals
 The primary and secondary synchronization signals are used in the cell
search procedure. The particular sequences which are transmitted for the
PSS and SSS in a given cell are used to indicate the physical layer cell
identity (PCI) to the UE
PSS and SSS Location for FDD
PCI and Synchronization signals (Cont.)
 There are 504 unique physical layer cell identities in LTE, grouped into
168 groups of three identities.
 The three identities in a group would usually be assigned to cells under the
control of the same eNodeB. Three PSS sequences are used to indicate the
cell identity within the group.
 168 SSS sequences are used to indicate the identity of the group.
 UE determines PCI by reading PSS and SSS and by calculating following

formula:
nals
r o n i za tion Sig
ynch
Dow nlink S
PCI = 3*SSS + PSS eNB

Where: SSS = 0,…..167
UE PSS = 0, 1, or 2
PCI and Cell of eNodeB
SSS - One of 168

Group Identities
eNB eNB
eNB
504 Unique Cell
Identities PSS - One of 3 Identities
PCI and Reference signals in LTE
 PCI determines Reference Signal (RS) position in frequency
domain.
 Function of RS:
 RSRP, RSRQ calculation (for handover decisions, cell

(re)selections)
 Radio Channel Estimation (for Channel equalization)
 It is advised to distribute PCIs in adjacent cells such that RS does

not occupy same subcarrier position to avoid interference for
better channel estimation
PCI Planning Principle
 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.
PCI Planning Principle for Single Antenna
 For single antenna port, by RS position based on PCI mod 6, one
cell can have up to 5 different neighbors without interfering in
frequency domain.
Physical Cell ID = 0 Physical Cell ID = 8

RS position is R R
R R based on Physical
R R
Cell ID (Physical
R R
Cell ID mod 6) R R
eNB R R
eNB
R R
R R
PCI Planning Principle for 2x2 MIMO
 LTE is usually implemented with 2x2 MIMO, where RS in two
antennas will interfere each other by PCI modulo 6 planning.
Therefore PCI modulo 3 planning is applied in 2 antenna ports.
x R x R R x R x
R x R x x R x R
x R x R R x R x
R x R x x R x R
Antenna Port 0 Antenna Port 1
PCI Planning Principle for 4x4 MIMO
 RS of third and fourth antenna are located on second and
fifth OFDM symbol in resource block, so the planning
principle remains same as with 2x2 MIMO, complying with
Modulo3 principle.
R RS symbol for antenna port 0
xx R xx R Rx x Rx x xx x xR x xR x xx x
Rx x Rx x xx R xx R xR x xx x xx x xR x
xx R xx R Rx x Rx x xx x xR x xR x xx x
Rx x Rx x xx R xx R xR x xx x xx x xR x
Antenna Port 0 Antenna Port 1 Antenna Port 2 Antenna Port 3
PCI Planning Principle – Modulo3
 Modulo3 planning principle divides all PCIs into 3 groups. Each
group with PCI mod 3 equals to 0, 1 or 2, respectively. Such
planning applies to 3-sector sites.
2
1 1
0
2 2

In 4-sector site scenario, cells with same mod3 must point opposite
directions.
PCI in ADD CELL
Questions
 Assume the site is configured with 2*2MIMO, and the neighbor
relation of cells are shown as below.
4
2
1 5
0 3
6
8
7
 Q: Is the PCI planning in figure below reasonable? If no, please

give your planning.
Contents
Cell Configuration
Cyclic-prefix Function
Cyclic-prefix Insertion
Base symbol period, Extension, Base symbol period,

e.g 64 samples e.g 10 samples e.g 64 samples
Integrate (FFT) any 64 samples

within the extended period
Extended symbol period, e.g 64+10=74 samples
Cyclic Prefix Size
 LTE uses two Cyclic prefix lengths to mitigate for
excessive multipath propagation:
 Normal Cyclic Prefix
 Extended Cyclic Prefix
7 OFDM Symbols
(Normal Cyclic Prefix)
0 1 2 3 4 5 6
Tsymbol
6 OFDM Symbols
(Extended Cyclic Prefix)
0 1 2 3 4 5
CP (Cyclic Prefix)
Cyclic Prefix Size Decision
 Cells with larger range are expected to have longer delay
spread, therefore it is very likely that Extended Cyclic
prefix should be configured. Anywhere else Normal
Cyclic Prefix shall be configured.
 Rules for CP selection:

 If cell radius is less than 15km, use normal cyclic prefix
 Otherwise, use extended cyclic prefix
CP Configuration in ADD CELL
Questions
 Please describe how CP functions.
Contents
Cell Configuration
PRACH
 PRACH is composed of CP (Cyclic Prefix), preamble and guard
period.
 CP is related to the moving speed of UE
 The length of preamble sequence affects the reception quality of

eNodeB
 Length of guard period determines the cell access radius
CP Preamble Sequence
TCP TSEQ Guard Period

Preample
PRACH Format
0 ms 1 ms 2 ms 3 ms
CP Sequence
0.1 Format 0
0.1 0.8
CP Sequence Guard Period Format 1

0.68 0.8 0.52
CP Sequence Format 2
0.2
0.2 1.6
CP Sequence Guard Period

Format 3
0.68 1.6 0.72
5102 xTs
Format 4
PRACH Format Decision
 Guard period in PRACH determines the maximum Round Trip
Delays (TGT). TGT limits maximum cell radius according to the
equation:
CP Sequence
TGT  c TGT  3.105
r  [km]
2 2 TCP TSEQ Guard Period
c = speed of light (300000km/h) Preamble
Preamble Allocated TSEQ TCP (µs) TGT Max. Delay Cell Radius (km)
Format Subframes (µs) (µs) Spread (µs)
0 1 800 103.125 96.875 5.208 R < 14.531
1 2 800 684.375 515.625 16.666 29.5 < R < 77.344
2 2 1600 203.125 196.875 5.208 14.5 < R < 29.531
3 3 1600 684.375 715.625 16.666 77.3 < R < 102.65
4 (TDD) Special Frame 133.3 14.6 9.417 16.666 R < 1.41
So PRACH format decision is based on practical coverage radius.
Root Sequence Index Planning
Cell has 64
Preamble
Sequence generation based on: Sequences
PRACH format
Root Sequence Index (0 to 837)
High Speed Flag
Zero Correlation Zone Configuration eNB
 Root sequence index is the key part of PRACH configuration. It is used to

determine the preamble sequence used for random access under the cell.
 The calculation relation is as follows: N = ceil(64/floor(Nzc/Ncs))
 N: Number of Zadoff-Chu (ZC) sequence per cell
 Nzc: the length of each ZC sequence
 Ncs: size of cyclic shift for generating one preamble sequence
 So the root sequence index should be assigned to cells with neighbor
relationship by 0, N, 2N, 3N, etc.
How to get Nzc?
 Where the length N ZC of the Zadoff-Chu sequence is defined by
protocol based on preamble format
ZC sequence
……
0 0 1 2 3 836 837 838
……
1 0 1 2 3 836 837 838
Root
2 0 1 2 3 …… 836 837 838
Sequence
Index Preamble format N ZC
…
0–3 839
…… 4 139
837 0 1 2 3 836 837 838
Table 5.7.2-1: Random access

preamble sequence length.
Table 5.7.2-3: Cyclic shifts N CS for preamble
generation (preamble format 4)
How to get Ncs?

 Ncs is related with cell radius and maximum
delay spread. It practically allows to create
several random access preambles from
one Root Sequence.
 There are 16 Ncs configurations (Zero

Correlation Zone Config) defined in the
protocol
FALSE TRUE
Depending on the Parameter “Cell radius(m)”
Relationship of Cell radius and Ncs
 Max cell radius for given Ncs is calculated from the formula:
  c
 r   NCS - ng 
TSEQ TSEQ
NCS   TGT   DS -  DS  
N ZC  N ZC  2
TSEQ  800s( preamble _ symbol _ duration)  DS  (max_ delay _ spread )[5.2;16.6s]
N ZC  839( preamble _ length) ng  2(additional _ guard _ samples )
limitation based on Ncs
107.344 km (Format 3)
117.214 km; Ncs = 839
14.531 km (Format 0)
22.818 km; Ncs = 167
57.143 km; Ncs = 419

15.953 km; Ncs = 119
37.119 km; Ncs = 279

12.234 km; Ncs = 93
1.507 km; Ncs = 18
0.792 km; Ncs = 13
1.078 km; Ncs = 15
2.079 km; Ncs = 22
2.651 km; Ncs = 26
3.510 km; Ncs = 32
4.368 km; Ncs = 38
5.512 km; Ncs = 46
7.371 km; Ncs = 59
9.803 km; Ncs = 76
log3(Max Cell radius) [km]

Extended Cell Range
PRACH Planning Process
Determine the PRACH format
Determine the Ncs value
Calculate the available preamble number

for each root index
Calculate the necessary root sequence

number for each cell
Determine all the root sequence and

assign it to the cell
Root Sequence Index Selection Example
 Assumption:
 Preamble Format 0, Maximum Cell Radius of 4.5km and High Speed Flag
= LOW_SPEED.
 Planning process
 Step 1: For cell radius = 4.5km, the closest higher Ncs is 46;
 Step 2: from one Root Sequence we can create floor(839/46) = 18

Random Access Preambles;
 Step 3: to have 64 different preambles per cell, we need to reserve

ceil(64/18) = 4 Root Sequences for each cell
 SO that means the available Root Sequences could be 0, 4,

8, ……832, and we have floor(838/4) = 209 unique configurations in
network.
PRACH Related Parameters in ADD CELL
Questions
 Assume that the low speed cell radius is 10km. Please give your
root sequence planning for cells.
Contents
Cell Configuration
Mobility Management Overview
Mobility Management
Idle State Connected State
Cell Reselection Handover Redirection
Intra-frequency Inter-frequency Inter-RAT
Neighboring Cell Overview
20MHz
EUTRANINTRAFREQNCELL
1 2 1 2
20MHz
3 3
4 5 4 5
6 6
eNodeB1 eNodeB2
1 2 1 2 1 2
3 3 3
GSM BTS UMTS NodeB CDMA BTS
Set Handover Switch
 Modify Cell Algorithm Switch Configuration: MOD CELLALGOSWITCH
 This command is used to modify the settings of cell-level algorithm switches.
Switches for handover based on load, frequency-priority, and distance need to
be set by this command.
MML example:
 MOD CELLALGOSWITCH: LocalCellId=0, MlbAlgoSwitch=IntraFreqMlbSwitch-
1&InterFreqMlbSwitch-1&UtranMlbSwitch-0&GeranMlbSwitch-0&CdmaMlbSwitch-
0&IntraFreqIdleMlbSwitch-0&UtranIdleMlbSwitch-0&MlbLoadInfoSwitch-0;
 MOD CELLALGOSWITCH: LocalCellId=0, FreqPriorityHoSwitch=FreqPriorIFHOSwitch-

1&FreqPriorIFBlindHOSwitch-1;
 MOD CELLALGOSWITCH: LocalCellId=0, DistBasedHoSwitch=ON;
Set Handover Switch (Cont.)
 Modify eNodeB Algorithm Switch Settings: MOD ENODEBALGOSWITCH
 This command is used to modify the configuration of eNodeB-level algorithm
switches. Switches for handover based on coverage, service, and UL service
quality need to be set by this command.
MML example:
 MOD ENODEBALGOSWITCH: HoAlgoSwitch=IntraFreqCoverHoSwitch-
1&InterFreqCoverHoSwitch-1&ServiceBasedInterFreqHoSwitch-1&UlQualityInterFreqHoSwitch-1;
Add Inter-eNodeB Neighbor Cell
All the parameters in the command

are used to describe the external
cell.
Add Intra-frequency Neighbor Cell
Except “Local cell ID”, which is used to specify

the cell to be added with neighbor relationship,
the rest parameters are all used to describe the
intra-frequency neighbor cell.
Add Inter-frequency Neighbor Cell
 Add a neighboring E-UTRAN frequency: ADD EUTRANINTERNFREQ
ADD EUTRANINTERNFREQ: LocalCellId=0, DlEarfcn=2800, UlEarfcnCfgInd=NOT_CFG,
CellReselPriorityCfgInd=NOT_CFG, SpeedDependSPCfgInd=NOT_CFG, MeasBandWidth=MBW100,
PmaxCfgInd=NOT_CFG, QqualMinCfgInd=NOT_CFG;
 Add the neighboring relation with an inter-frequency E-UTRAN cell: ADD

EUTRANINTERFREQNCELL
Questions
 Assume the DL EARFCN of local cell 0 of eNodeB 0 is 2800, and
this cell has a neighbor cell with cell ID of 56 in eNodeB 1. the DL
EARFCN of cell 56 is 3100.
 Q: please give the neighbor data configuration with MML

command.
Question
 Please prepare the MML draft for initial configuration based
on given negotiated data.
Contents
Contents
3.1 FDD and TDD
3.2 RAN Sharing
3.3 LampSite LTE for Indoor Coverage
3.4 Blade Site
Introduction to FDD and TDD
 Frequency spectrum for FDD and TDD
 In FDD mode, two symmetric frequency

channels are used; a protection interval
exists between the TX channel and RX
channel.
 In TDD mode, the TX and RX signals are
transmitted in different time slots of the
same frequency channel, requiring no
allocation of symmetric frequency band.
In the case of asymmetric data
transmission, the limited frequency
resources can be fully used.
Frame Structure of FDD and TDD
 Frame structure for FDD
One radio frame, Tf = 307200Ts = 10 ms
One slot, Tslot = 15360Ts = 0.5 ms
#0 #1 #2 #3 #18 #19
One subframe
 Frame structure for TDD

DwPTS
DL UL
GP
subframe #0 subframe #2
One radio frame, Tf = 307200Ts = 10 ms
One half-frame, 153600Ts = 5 ms SSS PSS RS/Control UpPTS

Data
One slot,
Tslot=15360Ts 30720Ts
Subframe #0 Subframe #2 Subframe #3 Subframe #4 Subframe #5 Subframe #7 Subframe #8 Subframe #9
One subframe,
30720Ts
DwPTS GP UpPTS DwPTS GP UpPTS
Subframe Configuration in TDD
 In TDD mode, there are 5 ms/10 ms frames, 1 ms subframe, and special
subframe.
 For subframe configuration, UL and DL subframes can be configured in the
following seven typical ways.
Downlink-to-Uplink Subframe Number
Uplink-Downlink
Switch-Point Period
Subframe
(Downlink/Uplink
Configuration 0 1 2 3 4 5 6 7 8 9
Subframe Ratio)
0 5 ms(1:3) D S U U U D S U U U
1 5 ms(2:2) D S U U D D S U U D
2 5 ms(3:1) D S U D D D S U D D
3 10 ms(6:3) D S U U U D D D D D
4 10 ms(7:2) D S U U D D D D D D
5 10 ms(8:1) D S U D D D D D D D
6 5 ms(3:5) D S U U U D S U U D
Special Subframe Configuration
 For TDD, the special subframe (DwPTS:GP:UpPTS) has the following 9
typical configurations:
 The UpPTS occupies 1 or 2 symbols.

 The DwPTS occupies 3 or 12 symbols.
 The GP occupies 1 to 10 symbols, and supports the cell coverage at a radius
between 1 and 100 km.
Difference in Hardware Configuration
 Add LBBP
the working mode of the baseband

processing board, which indicate whether
the LBBP works for FDD or TDD.
Difference in Hardware Configuration
(Cont.)
 Add RRU
The RF Unit working mode

indicate whether the RRU
works for FDD or TDD.
Difference in Radio Configuration
The frequency band and

EARFCN for TDD will be
different from FDD.
After TDD is configured in

“Cell FDD TDD indication”,
“subframe assignment” and
“special subframe patterns”
need to be configured based
on actual requirement.
Contents
3.1 FDD and TDD
3.2 RAN Sharing
3.4 Blade Site
Data of RAN Sharing
•ENodeBSharingMode (MOD ENODEBSHARINGMODE)

•CnOperator (ADD CNOPERATOR)
•LicenseSharingPolicy (ADD LICENSESHARINGPOLICY)
RAN sharing
•LicRatio (MOD LICRATIO)
•CnOperatorTa (ADD CNOPERATORTA)
•CellAlgoSwitch (MOD CELLALGOSWITCH)
RAN Sharing Modes eNodeB Supported
Independent operator mode
RAN sharing with common carriers

RAN sharing with dedicated carriers
Modify eNodeB Sharing Mode
 By default, independent operator mode is set for this MO.
Indicates the eNodeB sharing mode.

INDEPENDENT(Independent Operator Mode)
SHARED_FREQ(Shared Frequency Sharing
Mode), corresponding to RAN sharing with common
carriers .
SEPARATED_FREQ(Separate Frequency Sharing
Mode), corresponding to RAN sharing with
dedicated carriers
Deployment of RAN Sharing with
Common Carriers
• The following aspects are need to be planned and configured:
a) Primary and secondary operators
b) Number of Active Users
c) Traffic Volume
d) Fair Sharing of Air Interface Resources
e) IP Address Planning
Configuration of Primary and Secondary
Operators
Configuration of Active Users Number
 The active users of the eNodeB can be distributed among operators
based on the proportions by using capacity control items in the license.
 The sum of proportions for all operators cannot be greater than 100%.
the proportion of the number

of UEs in
the proportion of users that RRC_CONNECTED mode of
the operator can share to the operator.
other operators .
Configuration of Traffic Volume
Sharing
 When operators purchase the license containing the traffic volume control
item, the total traffic volume can be allocated to operators based on the
proportions specified.
the proportion of the UL

licensed traffic to the total If SHARING is set, all the operators
licensed traffic of the eNodeB. share the total traffic of the eNodeB
without proportional limits.
If DEDICATE is set, all the operators
share the total traffic of the eNodeB
based on specific proportions.
Configuration of Traffic Volume
Sharing on Dedicated Operator
 If LicRatio.TrafficSharingType is set to DEDICATE(Dedicate), the total
traffic volume of the eNodeB is allocated to each operator based on the
proportions specified by the configuration as below:
The proportion of traffic used by

When the operator has spare traffic the operator
resource, the proportion of traffic that
can share with other operators
Fair Sharing of Air Interface Resources
 When the CELLALGOSWITCH .RanShareModeSwitch parameter is set
to ON(On), admission control, congestion control, and scheduling help to
ensure that:
 If an operator has idle resources, other operators can use them.
 If no operator has idle resources, each operator uses the resources allocated
based on predefined proportions as below:
IP Address Planning
 S1 Interface
 Operators use the same eNodeB IP address plan in the entire
network.
 Operators use different eNodeB IP address plans in the entire

network.
 X2 Interface
 It is recommended that operators use the same eNodeB IP
address plan in the entire network
Deployment of RAN Sharing with
Dedicated Carriers
 RAN sharing with dedicated carriers allows operators to have their

own cells. Therefore, the air interface resource sharing between
cells dedicated to RAN sharing with common carriers are not
required in RAN sharing with dedicated carriers.
 In RAN sharing with dedicated carriers, cell-level features are

configured for each individual operator, and eNodeB-level
features are shared between operators.
IP Address Planning
 IP address planning for S1 interfaces in RAN sharing with
dedicated carriers is the same as that in RAN sharing with
common carriers.
 The eNodeB uses the IP addresses dedicated to each operator to

communicate with other eNodeBs through X2 interfaces.
Therefore, the different IP addresses for X2 interface must be
configured for different operators.
Contents
3.1 FDD and TDD
3.2 RAN Sharing
3.4 Blade Site
Data for LampSite
Specific MO for LampSite

•Run theADD RHUB command to add an RHUB to a specified RRU chain or
ring.
LampSite For single frequency networking (SFN) of LampSite

•Run the ADD EUSECTOREQMGROUP command to add a sector device
group.
•Run the ADD EUSECTOREQMID2GROUP command to add a sector
equipment ID to a sector equipment group.
Huawei LampSite Solution Overview
• Huawei LampSite is for providing focused indoor coverage.
LampSite= BBU + RHUB + pRRU On ceiling/wall installation
pRRU
• 3 mode,UL+WiFi
• U2.1GHz
• L1.8/ 2.1/2.6GHz
• Wi-Fi, 2.4&5GHz
• 2.5L/3kg
Ethernet Cable
Cat5/6
RHUB
• PoE for pRRU
powering
• 4 level cascade
Fiber • 8pRRU/rHUB
BBU
Source: South Africa
LampSite CPRI Networking
 Branch chain (single-link) topology
 a pRRU connects
to an RHUB over one
Ethernet cable
 each RHUB can
connect to eight
pRRUs
 The pRRUs do not
support cascading.
LampSite CPRI Networking (Cont.)
 Branch load sharing topology
 a pRRU connects
to an RHUB over two
Ethernet cables
 each RHUB can
connect to a
maximum of four
pRRUs
SFN in LampSite
 Example of indoor coverage with one SFN cell served by pRRU groups
pRRU groups are deployed in different

areas on different floors.
1 to 16 pRRUs are grouped using
RHUBs.
Within this larger SFN cell, the number

of handovers due to UE movement
decreases. Each pRRU group serves a
physical cell.
Add an RHUB
 Each RHUB MO must have a unique combination of CN, SRN, and SN among all
MOs as follows: RRU, RHUB, AAMU.
Before an RHUB is added, an RRU

chain must be added, which is
described in the next page “Add RRU
chains for RHUBs”.
Add a pRRU
BRANCH indicates that the
RRU is connected to the RHUB.
The RRU type for a pRRU to be added to

a branch chain/ring must be MPMU, and Invalid parameters when the
the branch chain/ring must have been RRU type is MPMU.
configured, which is described in the next
page “Add RRU chains for pRRUs”.
Add RRU chains for RHUBs
Position of the head of RHUB

st
chains, e.g, 1 CPRI port of BBP
board in slot 3 of BBU.
Add RRU chains for pRRUs
Configuration for branch chain
(single-link) topology
Position of the head of pRRU

st
chains, e.g, 1 CPRI port of
RHUB defined by (0,60,0)
Add RRU chains for pRRUs (Cont.)
Configuration for branch load
sharing topology
Position of the head and tail of

pRRU chains for load balancing,
st nd
e.g, 1 and 2 CPRI ports of
RHUB defined by (0,60,0) as
head and tail respectively.
Relation from MO Sector to Cell
Step 1:
Sector equipment is
generated
automatically or
manually after sector
configuration.
Step 2:
Bind sector
equipment group(s)
to a cell.
Step 3:
Add set(s) of sector
equipment to each
group. The added
sector equipment are
RF combined to
serve a physical cell.
Questions
 Give MML draft for

configuring SFN Cell (1) in
the given LampSite CPRI
networking
Contents
3.1 FDD and TDD
3.2 RAN Sharing
3.4 Blade Site
Introduction to Blade Site
 Blade Site Solution
Blade
RRU  Seamless Installation
12 L
Blade
BBU
0  “0” Footprint
12 L
Blade  Fast installation, saving
Power
70% deployment time
12 L
 5 minutes three
modules
Blade
Battery  All RATs, all bands with
28 L high capacity
Scenario of Blade BBU
BBU3910A Hardware Description
 The BBU3910A houses a UMDU, a universal multimode digital unit,
which provides the following modules: main control module, transmission
module, power module, clock module, baseband module, interconnection
module (reserved), and monitoring module. The following figure shows
the working principle of the UMDU.
Exterior of a BBU3910A
UMDU Functions
 Provides ports for connecting to the transmission equipment, RF modules,

USB devicesa, external reference clock, and LMT or U2000 to provide
signal transmission, perform automatic software upgrade, receive
reference clock, and support BBU maintenance on the LMT or U2000.
 Manages the entire base station system. The management involves the
processing of uplink and downlink data, signaling processing, resource
management, and operation and maintenance.
Add an UMDU Board
The number of the The number of the
cabinet where the board subrack where the board
is located, quoted from is located, quoted from
ADD CABINET. ADD SUBRACK with
subrack set to 0 or 1.
When adding an MDU

board, slot No. can be
set to 6.
Page183
Add an RRU Chain
 Before adding an RF unit, an RRU chain/ring need to be added, which is
designed to be quoted when adding an RF unit.
ID of the RRU chain. It The type of the topology.
uniquely identifies a chain The Value can be set as
within a base station. CHAIN, RING, and
The slot
number of the LOADBALANCE.
board where
the head CPRI
port is located,
quoted from
ADD UMDU for
UMDU board.
The number of the CPRI port,

The user-defined rate. The value locating in LBBP board, to
AUTO indicates the the auto which the configuring
negotiation mode is adopted. RRUCHAIN is head to.
Page184
Add a Device IP Address
When adding an UMDU board in BBU3910A,

slot No. only can be set to 6.and UMDU board
provide ports for connecting to the transmission
equipment.
Page185
Thank you
www.huawei.com

ENodeB LTE V100R008C10 Data Introduction For Initial Configuration ISSUE 1.01

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ENodeB LTE V100R008C10 Data Introduction For Initial Configuration ISSUE 1.01

Încărcat de

Drepturi de autor:

Formate disponibile

eNodeB LTE

Copyright © 2015 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2015 Huawei Technologies Co., Ltd. All rights reserved.

 Implement initial data preparation by MML for basic scenario

 Implement data preparation for specific scenarios by MML

2. Common Data Parameters Introduction

3. Data Preparation in Specific Scenarios

2. Common Data Parameters Introduction

3. Data Preparation in Specific Scenarios

MML command window

 An eNodeB has default configuration data

Basic Radio Device Transport

2. Common Data Parameters Introduction

3. Data Preparation in Specific Scenarios

2.2 eNodeB Device Data

2.3 eNodeB Transport Data

2.4 eNodeB Radio Data

NE configuration attributes NE (SET NE)

•CNOPERATOR (ADD CNOPERATOR)

NE maintenance mode Equipment (SET MNTMODE)

ID of the application referenced by

Specify the site of the NE. When multiple

NE NE 1:BTS3900 GSM NE2: BTS3900

An operator is uniquely identified

Index of the operator, quoted

The maintenance mode can be set

When the NE is in the special

 Do we need to ADD ENODEBFUNCTION for an LO site

2.2 eNodeB Device Data

2.3 eNodeB Transport Data

2.4 eNodeB Radio Data

Configure cabinets and BBU3900 device data

Configure RF unit data

Configure ALDs data (Optional)

Configure monitoring units data (Optional)

Configure power modules data (Optional)

Configure time data

Configure synchronization data

Function Area Subfunction Area MO and MML Command

•RRUCHAIN (ADD RRUCHAIN)

The cabinet type can be set to APM30,

The subrack No. can

When adding a subrack for

When adding an MPT

 When adding an LBBP board, Work Mode is specified.

 When adding a UBBP board, Base Band Work Standard is specified,

This parameter is used for

When adding an FAN

The number of the CPRI port,

The number of RX and TX

The position where the

•TZ (SET TZ)

DST start date can be set

Frequency Precision Phase Synchronization

The priority of the clock source with

The Client IP address, quoted from

 set the clock synchronization mode of a BS.

2.2 eNodeB Device Data

2.3 eNodeB Transport Data

2.4 eNodeB Radio Data

2.3.3 Introduction to VLAN and VLAN Configuration

2.3.4 Application of Transmission Layer Configuration

Control Plane User Plane