Wireless Network Solution Design Operation and Application Guide To LTE eRAN6.0 Network Dimensioning

Product Name Security Level
LTE RND Internal

Product Version Total pages 71
eRAN6.0
Wireless Network Solution Design Operation and

Application Guide to LTE eRAN3.0 Network
Dimensioning
(For internal use only)
Prepared By Liu Yadong Date 2011-10-30

Reviewed By Date
Reviewed By Date
Approved By Date
Huawei Technologies CO., LTD.

All Rights Reserved
Wireless Network Solution Design Operation and Application Guide to LTE eRAN3.0
Network Dimensioning INTERNAL
Change History
Date Revision V CR ID Sec No. Change Description Author

ersion
2011-10-30 0.0 Completed the draft Liu Yadong (employee ID:

00168824)
Key words
Link budget, capacity estimation, coverage radius, edge rate, S1&X2 traffic estimation, number of activated
subscribers, TA paging capacity, E-MBMS coverage, indoor coverage, small base station coverage
Abstract
This document describes the parameter settings of the LTE network capacity estimation tool, and provides
examples for using the estimation functions.
Acronyms and Abbreviations

Abbreviations Full Spelling
ACK/NACK Acknowledgement/Not-acknowledgement
AMC Adaptive Modulation and Coding
BBU Baseband Unit
BHSA Busy Hour Session Attempt
BLER Block Error Rate
BPSK Binary Phase Shift Keying
CCE Control Channel Element
CINR Carrier-to-Interference and Noise Ratio
CP Cyclic Prefix
CQI Channel Quality Indication
D-BCH Dynamic-Broadcast Channel
DCI Downlink Control Information
2013-12-16 Huawei confidential. No spreading without Page 2 of 71
permission.
DMRS Demodulation Reference Signal

EIRP Equivalent Isotropic Radiated Power
eNodeB E-URTA Node B
EPRE Energy Per Resource Element
FDD Frequency Division Duplex
FSTD Frequency Switched Transmit Diversity
FTP File Transport Protocol
GSM Global System for Mobile communication
HARQ Hybrid Automatic Retransmission Request
HTTP Hypertext Transfer Protocol
IRC Interference Rejection Combining
LNA Low Noise Amplifier
LTE Long Term Evolution
MAC Media Access Control
MAPL Maximum Allowed Path Loss
MBMS Multimedia Broadcast Multicast Service
MBSFN Multicast/Broadcast Signal Frequency Network
MCS Modulation and Coding Scheme
MCW Multiple Code Word
MIMO Multiple Input Multiple Output
MRC Maximum Ratio Combining
OFDMA Orthogonal Frequency Division Multiple Access
OOK On-Off Keying
PBCH Physical Broadcast Channel
PCFICH Physical Control Format Indication Channel
PDCCH Physical Downlink Control Channel
PDSCH Physical Downlink Share Channel
PHICH Physical HARQ Indication Channel
PMI Precoding Matrix Indication

permission.
PRACH Physical Random Access Channel

PUCCH Physical Uplink Control Channel
PUSCH Physical Uplink Share Channel
QoS Quality of Service
QPSK Quadrature Phase Shift Keying
RACH Random Access Channel
RB Resource Block
REG Resource Element Group
RFU Radio Frequency Unit
RRU Remote Radio Unit
RS Cell-Specific Reference Signal
RSRP Reference Signal Received Power
RV Redundant Version
SC-FDMA Single Carrier-Frequency Division Multiple Access
SCH Synchronization Signal
SFBC Space-Frequency Block Code
SFM Shadow Fading Margin
SFM Slow Fading Margin
SINR Signal-to-Interference and Noise Ratio
SRI Scheduling Request Indication
SRS Sounding Reference Signal
TA Tracking Area
TAL Tracking Area List
TAU Tracking Area Update
TDD Time Division Duplex
TMA Tower Mounted Amplifier
UCI Uplink Control Information
UE User Equipment
VMIMO Virtual MIMO
VoIP Voice over IP

permission.
VP Video Phone

permission.
Contents
1 About This Document.....................................................................................................................9

1.1 Background........................................................................................................................................................9
1.2 Document Description.......................................................................................................................................9
1.3 Application Scope..............................................................................................................................................9
2 Application Scenarios...................................................................................................................9
2.1 Solution Principles.............................................................................................................................................9
2.2 Typical Scenarios.............................................................................................................................................10
3 Settings of Common Parameters..............................................................................................11

3.1 Global Parameters............................................................................................................................................11
3.1.1 Duplex Mode..........................................................................................................................................11
3.1.2 Sectorization...........................................................................................................................................13
3.1.3 TMA Used..............................................................................................................................................13
3.1.4 DL PB......................................................................................................................................................14
3.1.5 Adaptive ICIC.........................................................................................................................................14
3.1.6 Cyclic Prefix...........................................................................................................................................14
3.1.7 PDCCH Overhead..................................................................................................................................15
3.2 Scenario Parameters.........................................................................................................................................15
3.2.1 Morphology............................................................................................................................................15
3.2.2 Propagation Model.................................................................................................................................15
3.2.3 Environment...........................................................................................................................................17
3.2.4 Channel Model.......................................................................................................................................17
3.2.5 Service Type...........................................................................................................................................17
3.2.6 Bandwidth...............................................................................................................................................18
3.2.7 Total Number of RBs..............................................................................................................................18
3.2.8 PUCCH Overhead..................................................................................................................................19
3.2.9 Carrier Frequency...................................................................................................................................19
3.2.10 Penetration Loss...................................................................................................................................20
3.2.11 PropagationCm.....................................................................................................................................20
3.2.12 MIMO Scheme.....................................................................................................................................21
3.2.13 Target Load...........................................................................................................................................22
3.2.14 RBs can be Used...................................................................................................................................22
3.2.15 Area Coverage Probability....................................................................................................................23
3.2.16 Edge Coverage Probability...................................................................................................................23
3.2.17 Std.of Shadow Fading...........................................................................................................................23
3.2.18 Ior/Ioc...................................................................................................................................................23
3.2.19 Interference Margin..............................................................................................................................24
3.2.20 Shadow Fading Margin........................................................................................................................24
3.2.21 Hard handover Gain..............................................................................................................................24
3.3 Equipment Parameters.....................................................................................................................................25
3.3.1 eNodeB Parameters................................................................................................................................25
3.3.2 UE Parameters........................................................................................................................................26
4 Operation Guide..........................................................................................................................27
4.1 Calculating the Cell Coverage Radius When the Service Rate at the Cell Edge Is Known............................27
4.1.1 Parameters Involved...............................................................................................................................27
4.1.2 Operation Guide.....................................................................................................................................28
4.2 Calculating the Cell Edge Rate When the Cell Radius Is provided.................................................................30
4.2.2 Operation Guide.....................................................................................................................................30
4.3 RSRP Dimensioning........................................................................................................................................31
4.3.1 Calculating the Outdoor RSRP that Meets the Cell Edge Date Rate Requirement................................31
4.3.2 Calculating the RS Coverage Radius When the Outdoor RSRP Is provided.........................................32
4.3.3 Calculating the RS Coverage Radius When the Indoor (Outdoor) RS Demodulation Threshold Is
Known.............................................................................................................................................................32
4.4 Calculating the Control Channel Coverage.....................................................................................................33
4.4.2 Operation Guide.....................................................................................................................................36
4.5 Site Scale Dimensioning..................................................................................................................................36
4.5.2 Operation Guide.....................................................................................................................................37
4.6 Capacity Dimensioning....................................................................................................................................38
4.6.2 Operation Guide.....................................................................................................................................39
4.7 Evaluating the Balance Between Coverage and Capacity...............................................................................41
4.7.2 Operation Guide.....................................................................................................................................42
4.8 Active Subscribers Number Dimensioning......................................................................................................43
4.8.2 Operation Guide.....................................................................................................................................46
4.9 S1&X2 Traffic Dimensioning..........................................................................................................................46
4.9.2 Operation Guide.....................................................................................................................................51
4.10 Calculating the TA Paging Capacity..............................................................................................................52
4.10.1 Parameters Involved.............................................................................................................................52
4.10.2 Operation Guide...................................................................................................................................56
4.11 E-MBMS Coverage Dimensioning................................................................................................................56
4.11.2 Operation Guide....................................................................................................................................59
4.12 Indoor Pico Base Station and DAS Dimensioning........................................................................................60
4.12.3 Operation Guide...................................................................................................................................66
5 Operation Guide for Useful Tools...........................................................................................68

5.1 Performing Positive and Reverse Calculation of the Distance and Path Loss.................................................68
5.1.2 Calculating the Path Loss When the Distance Is Known.......................................................................68
5.1.3 Calculating the Distance When the Path Loss Is Known.......................................................................69
5.2 Calculating the Service Rate and RB Quantity................................................................................................69
5.2.2 Calculating the Data Rate Based on the MCS and Number of RBs.......................................................69
5.2.3 Calculating Number of RBs Based on the MCS and Data Rate.............................................................70
5.3 Optimizing the Uplink MCS............................................................................................................................70
5.4 Calculating the Feeder Loss.............................................................................................................................71
5.5 Calculating Indoor RSRP, EIRP, and Cell Radius...........................................................................................71
5.6 Calculating Indoor Signaling Strength at the Cell Edge..................................................................................72
5.7 Operation Suggestions.....................................................................................................................................73
6 Known Issues...............................................................................................................................74
7 References Document.................................................................................................................74
1 About This Document
1.1 Background
When the LTE network dimensioning algorithm is used in the radio network dimensioning (RND) tool,
detailed descriptions of parameter settings in the functional modules are required to quickly and accurately
obtain the estimation results.
1.2 Document Description

This document describes the application scenarios, key parameters, parameter settings in the functional
modules, and application instances of the LTE RND tool.
1.3 Application Scope

This document is released with eRAN6.0. It is applicable to the biding activities and communication of
frontline personnel, project quotations, and network preplanning. It can also provide guidance for network
dimensioning research.
2 Application Scenarios
2.1 Solution Principles
Table 2.1.1.1.1.1.1.1 Principles of the network dimension solution

Dimensioning Sub- Basic Principle
solution
Dimensioning of A signal undergoes a series of gains and losses in the path from the transmitter
services, control to the receiver, including antenna gains, cable loss, body loss, spatial path loss,
channels, and pilot penetration loss, receive antenna gains, and eNodeB transceiver converter loss.
coverage After all the gains and losses are added and subtracted, the actual received
signal strength is calculated, with the interference margin, slow fading margin,
and handover gain taken into consideration. The signal strength is then
compared with the receiver sensitivity. If the signal strength meets the
requirement regarding sensitivity, it can be demodulated. The preceding path is
used to evaluate the coverage performance of network links.
Capacity Capacity dimensioning is implemented based on the scenario-based capacity
dimensioning simulation and condition fitting. The SINR distribution and the required number
of RBs in different scenarios and with different site spacing and load can be
obtained by performing the scenario-based simulation using the network
planning and simulation tool U-net. Cell average capacity can be obtained by
fitting the RB distribution, while taking factors such as bandwidth, load, power,
cable coupling loss, cell radius, and feature gains into consideration. The
number of allocated RBs and the SINR distribution are queried based on the
entered criteria. The data rate at each distribution point is calculated based on
the MIMO mode and channel demodulation capability. The average cell
throughput is the sum of the data rates of the distribution points.
Evaluation of the The evaluation of the balance between the cell coverage and capacity provides a
balance between the reference for determining the number of sites, site spacing, and edge rate that
call coverage and meet coverage and capacity requirements. By doing this, the performance of the
capacity entire network can be roughly estimated during the network preplanning phase.
The regional capacity calculation provides a reference for estimating the
bandwidth of the core network.
Set the expected total capacity of the region and the number of RBs used by
edge users. Set the cell radius to different values in corresponding scenarios.
Calculate the cell coverage area with each radius and the number of eNodeBs
required to fulfill the coverage requirement. Calculate the cell throughput with
each radius and the number of eNodeBs required to fulfill the throughput
requirement. When the numbers of eNodeBs are the same in both cases, a
balance of coverage and capacity has been reached. The cell edge rate is the cell
edge rate under the balance.
S1&X2 traffic When data packets are transmitted to upper-layer networks, headers, such as IP
dimensioning header, MAC header, and VLAN header, are added to these packets. The user-
and control-plane bandwidths required for the peak rate can be obtained by
calculating the overhead coefficient and peak-to-average ratio.
Calculation of the The maximum number of RRC connected UEs supported by the system can be
number of active estimated based on the cell capacity and traffic model, while taking the average
subscribers service rate and resource usage rate into consideration.
Dimensioning of the Estimation of the TA capacity helps to estimate the number of eNodeBs
TA paging area required in a TA, providing a reference for network preplanning. According to
capacity the paging mechanism, the TA size depends on the processing capability of the
MCU board on the MME and the paging capability of the eNodeB. The paging
capability of the eNodeB is subjected to the PDSCH, PDCCH, CPU usage rate,
and paging congestion rate. Therefore, many factors need to be considered
when planning the TA.
Estimating E-MBMS To be added
coverage
Pico/DAS indoor Indoor system dimensioning evaluates the site layout and power that meet the
estimation indoor coverage requirement. The edge level and edge rate are considered
during the indoor system dimensioning, which provides a reference for feeder
planning in the DAS system.
2.2 Typical Scenarios

The LTE network dimensioning is primarily used to estimate the coverage and capacity of outdoor macro
base stations, transmission bandwidth, maximum number of online users, TA size, and coverage of indoor
small-cell base stations. These functions are detailed in the following sections.
3 Settings of Common Parameters

3.1 Global Parameters
3.1.1 Duplex Mode
LTE system supports both time division duplex (TDD) and frequency division duplex (FDD). This link
budget tool supports both duplex modes. When the TDD mode is selected, options of uplink-downlink time
slot configuration and special time slot configuration will be displayed in an associated manner.
Setting principles: Set the parameter according to the RAT of the operator. When the TDD mode is used,
select the uplink-downlink time slot configuration and special time slot configuration as required.
When a duplex mode is selected, the MIMO mode and noise factor of the eNodeB will be configured in an associated
manner.
3.1.1.1 TDD UL/DL Subframe Configuration

When the FDD mode is selected, the TDD UL/UL Configuration option is not displayed. When the TDD
mode is used, the following seven uplink-downlink subframe configurations can be selected.
Table 3.1.1.1.1.1.1.1 LTE TDD uplink/downlink subframe configuration

Uplink-downlink Downlink-to-Uplink Subframe Number
Configuration Switch-point Periodicity
0 1 2 3 4 5 6 7 8 9
#0 5 ms D S U U U D S U U U
#1 5 ms D S U U D D S U U D
#2 5 ms D S U D D D S U D D
#3 10 ms D S U U U D D D D D
#4 10 ms D S U U D D D D D D
#5 10 ms D S U D D D D D D D
#6 5 ms D S U U U D S U U D
The letter D in the table represents a downlink subframe, the letter U represents an uplink subframe, and the letter S
represents a special subframe. eRAN6.0 supports the uplink-downlink subframe configurations of #0, #1, #2, and #5.
The following figure shows the uplink-downlink subframe configurations displayed on the RND tool.
Table 3.1.1.1.1.1.1.2 Options of LTE TDD uplink-downlink subframe configurations

Configuration
#0, 5 ms, 1:3

#1, 5 ms, 2:2
#2, 5 ms, 3:1
#3, 10 ms, 6:3
#4, 10 ms, 7:2
#5, 10 ms, 8:1
#6, 5 ms, 3:5
Setting principles: With the same downlink data rate, the uplink-downlink subframe configurations with a
high proportion of downlink subframes indicates fewer RBs are used in the downlink. With the same uplink
data rate, the uplink-downlink subframe configurations with a high proportion of downlink subframes
indicates fewer RBs are used in the uplink. Set the parameter based on customer requirements. The default
value is #1, 5 ms, 2:2 on the RND.
3.1.1.2 LTE TDD Special Subframe Configuration

The TDD special subframe configuration option is displayed only when the TDD mode is used. Each
special subframe (S) consists of three parts: DwPTS, GP, and UpPTS. The following table illustrates the
proportions (equivalence of symbol proportion) of these three parts.
Table 3.1.1.2.1.1.1.1 TDD special subframe configurations

Configuration Normal CP Extended CP
DwPTS GP UpPTS DwPTS GP UpPTS
0 3 10 1 3 8 1
1 9 4 1 8 3 1
2 10 3 1 9 2 1
3 11 2 1 10 1 1
4 12 1 1 3 7 2
5 3 9 2 8 2 2
6 9 3 2 9 1 2
7 10 2 2 - - -
8 11 1 2 - - -
When normal CPs are used, eRAN6.0 supports the special subframe configurations of #4, #5, and #7. The
following figure shows the special subframe configurations displayed on the RND tool.
Table 3.1.1.2.1.1.1.2 Options of TDD special subframe configuration

Configuration Normal CP Extended CP
0 #0 3:10:1 #0 3:8:1
1 #1 9:4:1 #1 8:3:1
2 #2 10:3:1 #2 9:2:1
3 #3 11:2:1 #3 10:1:1
4 #4 12:1:1 #4 3:7:2
5 #5 3:9:2 #5 8:2:2
6 #6 9:3:2 #6 9:1:2
7 #7 10:2:2 #7 -:-:-
8 #8 11:1:2 #8 -:-:-
Setting principles: The RND tool supports dimensioning regardless of whether normal CPs or extended CPs
are used. Set the parameter based on customer requirements. The default value is #7 10:2:2.
3.1.2 Sectorization
There are three types of eNodeBs: omnidirectional, three-sector, and six-sector eNodeBs. This RND tool
supports dimensioning of only omnidirectional and three-sector eNodeBs. The typical antenna gain and
coverage area of an eNodeB depend on the eNodeB type, as shown in the following figure.
Table 3.1.2.1.1.1.1.1 eNodeB type and antenna gain

eNodeB Antenna Gain Three-Sector (dBi) Omnidirectional eNodeB
(dBi)
2600 MHz 18 11
900 MHz 15 11
Setting principles: Set the parameter based on system requirements. The default value is 3 Sector.
This RND tool does not support the capacity dimensioning of omnidirectional eNodeBs.
3.1.3 TMA Used

When tower mounted amplifiers (TMAs) are used, the uplink noise factor decreases on the eNodeB and the
uplink receive sensitivity and uplink coverage increase. However, the use of the TMA causes insertion loss
(TMA loss).
This parameter has two values:
 Enable: When this parameter is set to Enable, the TMA is used.
 Disable: When this parameter is set to Disable, the TMA is not used.
When the parameter is set to Enable, the TMA Gain and TMA Insertion Loss parameters are available.
Setting principles: Set the parameter based on system requirements. The default value is Disabled. The
parameter is generally set to Enable when the RRU is not mounted on a tower or the feeder loss is large.
3.1.3.1 TMA Gain

The TMA Gain parameter is available when the TMA Used parameter is set to Enable. The TMA Gain
parameter has two values:
 TMA_12dB (12 dB of TMA gain)
 TMA_24dB (24 dB of TMA gain)
Setting principles: Set the parameter based on system requirements. Generally, the TMA with the gains of
12 dB is selected.
3.1.3.2 TMA Insertion Loss
The TMA Insert Loss parameter is available when the TMA Used parameter is set to Enable. When the
TMA is used, insertion loss occurs in the downlink, compromising the downlink coverage.
Setting principles: Set the value based on system requirements. It is set to 0.5 in LTE systems.
3.1.4 DL PB
The parameter Pb indicates the offset between the RS EPRE and the type A PDSCH EPRE. The Pb
parameter can be set to 0, 1, 2, or 3. The RS EPRE is calculated using the following formula:
RS EPRE = type A PDSCH EPRE + 10 x log10 (1+ Pb)
Setting principles: Set the parameter according to the number of antennas used in the eNodeB. When one
antenna is used, set the parameter to 0. Otherwise, set the parameter to 1.
Type A symbols are symbols in which no RS is transmitted. Type B symbols are symbols in which RSs are transmitted.
3.1.5 Adaptive ICIC

Adaptive inter-cell interference coordination (ICIC) adaptively mitigates the uplink/downlink interference
between cells. It reduces the uplink and downlink interference for CEUs. This parameter has an impact on
both the link budget and capacity dimensioning. Its gain is reducing uplink/downlink interference margin.
The value of this parameter is predetermined and cannot be changed on the GUI.
Setting principles: Set the parameter based on system requirements. The default value is Disabled.
3.1.6 Cyclic Prefix

Cyclic prefix is introduced in OFDM to mitigate inter-symbol interference and ensure the orthogonality
between sub-carriers. There are two types of CPs: normal CPs and extended CPs. Extended CPs are used in
wide coverage scenarios or MBSFN-based MBMS transmission scenarios. CP types determine the number
of traffic channel REs that can be used in an RB pair. For details, see eRAN6.0 Network Dimensioning
High Level Design.
Setting principles: Set the parameter based on system requirements. In most cases, normal CPs are used by
default. When extended CPs are used, beamforming is unavailable.
3.1.7 PDCCH Overhead

The PDCCH Overhead parameter indicates the number of symbols for transmitting service data in each
RB. This parameter can be set to 1, 2, 3, or 4. Larger value indicates that fewer REs can be used in an RB
to transmit data. The parameter cannot be set to 1 when the system bandwidth is 1.4 MHz, 3 MHz, or 5
MHz. The parameter must be set to 4 when the system bandwidth is 1.4 MHz. When the bandwidth is
larger than 10 MHz, the parameter can be set to 1, 2, or 3.
Setting principles: Set the parameter based on system requirements. The default value is 3.
3.2 Scenario Parameters

3.2.1 Morphology
There are four types of morphology:
 Dense Urban
 Urban
 SubUrban
 Rural Area
When a morphology type is selected, the eNodeB installation height, penetration loss, and shadow fading
standard deviation are automatically configured in an associated manner.
Setting principles: Set the parameter based on site requirements. The default value is Dense Urban.
3.2.2 Propagation Model

The RND supports the following seven propagation models:
 Cost231-Hata (Classic)
 Cost231-Hata (Huawei)
 Okumura-Hata (Classic)
 Okumura-Hata (Huawei)
 SPM
 Microcell
 Cost231 Walfish Ikegami
The Cost231-Hata model or SPM model is used on the 1500 MHz band or higher. The Okumura-Hata
model is used on the band lower than 1500 MHz.
 When the former four models are used, the PropagationCm parameter is automatically set in an
associated manner.
 When the SPM model is selected, the parameter is displayed and automatically configured based on
the scenario.
The Microcell model is used in small-cell base stations. When this model is selected, the transmit power
and eNodeB installation height will be automatically configured in an associated manner.
When the Cost231-WI model is selected, the eNodeB installation height will be automatically configured in
an associated manner, and relevant parameters will be displayed. This model can also be used in micro base
stations, as shown in the following.
3.2.2.1 SPM Parameters
Table 3.2.2.1.1.1.1.1 SPM propagation model parameters

Parameter K1 K2 K3 K4 K5 K6 Clutter Loss(dB)
Default Value 30.37 44.9 5.83 0.5 -6.55 1 0
When the SMP model is selected, the preceding parameters are automatically configured to the default
values. You can modify the value based on the scenario.
3.2.2.2 Parameters of the Cost231 Walfish Ikegami propagation model

This model can be used when the following conditions are met:
1. The spectrum ranges from 800 MHz to 2000 MHz.
2. The cell radius ranges from 0.02 km to 0.5 km.
3. The eNodeB antennas height ranges from 4 m to 50 m (same as or lower than the height of the roof
top).
4. The UE antenna height ranges from 1 m to 3 m.
Corresponding parameters are:
 LOS (line of sight)
This propagation model corresponds to the free space propagation model. It is used when the distance
between the UE and the eNodeB is larger than 20 m. This model is seldom used.
 NLOS (non line of sight)
(1) Road Width
This parameter indicates the width of the road. The unit is m. Generally, this parameter is set to 25
m.
(2) Building Interval
This parameter indicates the distance between buildings. The unit is m. The typical parameter
value is 50 m.
(3) Building Height
This parameter indicates the height of a building. The unit is m. The typical parameter value is 12
m.
(4) Inci Angle
This parameter indicates the angle between the incident wave and the road. The unit is degree (°).
The typical parameter value is 30°.
Setting principles: Select the propagation model based on the morphology and frequency. When a
propagation model is selected, the corresponding parameters are automatically set to default values. Change
the parameter values as required. Currently, the RND does not support the capacity dimensioning of
systems using the Microcell and Cost231 Walfish Ikegami models.
3.2.3 Environment
There are two types of UE environment:
 Indoor
 Outdoor
The penetration loss varies with the type of environment. The penetration loss is 0 outdoor.
Setting principles: Set the parameter according to the actual environment. The default value is Indoor.
3.2.4 Channel Model

There are the following three types of channel models:
 EPA: corresponding to the EPA 3 channel on the RND
 ETU: with the speed of 3 km/h, 30 km/h, 60 km/h, and 120 km/h which correspond to the ETU3,
ETU30, ETU60, ETU120 channels on this tool respectively
 EVA, with the speed of 30 km/h, 60 km/h, and 120 km/h which correspond to the EVA30, EVA60,
EVA120 channels on this tool respectively
Setting principles: Set the parameter based on the morphology type.
1. When Dense Urban, Urban, or SubUrban is selected, set the channel model to ETU.
2. When Urban Pedestrian is selected, set the channel model to EPA3.
3. When Rural Area, set the channel model to EVA.
This default value is ETU 3.
3.2.5 Service Type

Currently, the RND supports the following service types:
 PS (data service)
 VoIP 7.95 (AMR speech service. The service rate is 7.95 kbit/s)
 VoIP 12.2 (AMR speech service. The service rate is 12.2 kbit/s)
The first type is packet data service, the latter two are voice services (VoIP).
When the service type is PS, the service rate at the cell edge can be set based on service requirements.
When the service type is VoIP, manual setting of the service rate at the cell edge is not required. It is
automatically set based on service requirements. The data rate is set to 256 kbit/s when the service type is
VoIP 7.95, and 336 kbit/s when the service type is VoIP 12.2.
Setting principles: Set the parameter as required. The default value is PS.
3.2.5.1 Body Loss

This parameter indicates the body loss. The parameter value depends on the service type. The unit is dB.
When PS services are used, the parameter is set to 0 dB; when VoIP services are used, the parameter is set
to 3 dB.
Setting principles: When PS services are used, this parameter is not displayed. When VoIP service types are
used, this parameter is set to 3 dB in an associated manner.
3.2.5.2 TTI Bundling Gain

This parameter indicates the gain of TTI bundling, which is enabled only when the following conditions are
met:
 The VoIP services are used.
 The user uses three or less RBs in the uplink.
 The modulation mode is QPSK.
Setting principles: When the PS service type is selected, this parameter is not displayed. When the VoIP
service type is selected, the parameter is automatically set to 4.5 dB. Consider using TTI bundling when
three or less RBs are required for the link budget, and the QPSK modulation is used.
3.2.6 Bandwidth
The following table lists the six bandwidths available for LTE systems.
Table 3.2.6.1.1.1.1.1 LTE system bandwidths

Bandwidth(MHz)
1.4
3
5
10
15
20
When a certain bandwidth is selected, the corresponding parameters, including Total Number of RBs,
PUCCH Overhead, and DL/UL RBs Can Be Used, are automatically configured in an associated manner.
Setting principles: Set the parameters based on system requirements.
3.2.7 Total Number of RBs

The bandwidth determines the number of RBs that can be used. The following table describes the
correlation between the bandwidth and the number of RBs.
Table 3.2.7.1.1.1.1.1 Number of RBs that can be used at different bandwidths

Bandwidth(MHz) Total Number of RBs
1.4 6
3 15
5 25
10 50
15 75
20 100
Setting principles: This parameter is displayed, but it cannot be modified. The parameter value is
automatically set when a certain bandwidth is selected.
3.2.8 PUCCH Overhead

This parameter indicates the number of RBs used in the PUCCH. The following figure shows the default
values of this parameter with different bandwidths. The values are depends on the product capability of
eRAN6.0.
Table 3.2.8.1.1.1.1.1 Default values of PUCCH Overhead at different bandwidths

Bandwidth (MHz) PUCCH Overhead
1.4 2
3 4
5 4
10 6
15 8
20 10
Setting principles: This parameter is automatically set when a certain bandwidth is selected. Modify the
value as required.
3.2.9 Carrier Frequency

This parameter specifies the uplink and downlink carrier frequencies. The unit is MHz.
 DL Carrier Frequency
Set the parameter based on site requirements. The values of DL Penetration Loss, DL
PropagationCm, and eNodeB Antenna Gain vary with the downlink carrier frequency.
 UL Carrier Frequency
Set the parameter based on site requirements. When an uplink carrier frequency is selected, the UL
Penetration Loss, UL PropagationCm, and eNodeB Noise Figure parameters are automatically
configured in an associated manner.
Setting principles: Set the DL Carrier Frequency and UL Carrier Frequency parameters separately. In
AWS systems, set UL Carrier Frequency to 1700 MHz and DL Carrier Frequency to 2100 MHz. In
LTE TDD systems, UL Frequency and DL Carrier Frequency must be set to the same value and larger
than 1800 MHz.
3.2.10 Penetration Loss

This parameter indicates the penetration loss. The unit is dB. When UEs are located outdoors, this
parameter is set to 0 dB. When UEs are located indoors, the parameter value varies with the scenario and
uplink/downlink frequencies. The following table lists the default values.
Table 3.2.10.1.1.1.1.1 Relationship between penetration loss, morphology and frequency

Penetration Loss
Frequency (MHz) DU U SU RA HST
700 18 14 10 7 22
800 18 14 10 7 22
850 18 14 10 7 22
900 18 14 10 7 22
1500 19 15 11 8 25
1700 19 15 11 8 25
1800 19 15 11 8 25
1900 19 15 11 8 25
2100 20 16 12 8 25
2300 20 16 12 8 25
2600 20 16 12 8 25
3500 20 16 12 8 25
Setting principles: This parameter is separately configured in the uplink and in the downlink. The value of
this parameter varies with Morphology and UL/DL Carrier Frequency. You can modify the parameters
according to specific requirements of the scenario.
3.2.11 PropagationCm
This parameter modifies Morphology and Propagation Model. The unit is dB. There are two types of
value available for this parameter: Classic and Huawei. The following table lists the default values of this
parameter.
Table 3.2.11.1.1.1.1.1 Relationships between PropagationCm and Propagation Model

Propagation Model Dense Urban Suburban Rural Area Hotspot
Urban
Cost231-Hata(Classic) 3 0 0 -4.78 x -4.78 x (lgf)2+18.33 x

(lgf)2+18.33 lgf-35.94
x lgf-35.94
Cost231-Hata (Huawei) 3 0 -8 -15 -15
Okumura-Hata (Classic) 0 0 -2 x -4.78 x -4.78 x (lgf)2+18.33 x
(lg(f/28))2- (lgf)2+18.33 lgf-40.94
5.4 x lgf-35.94
Okumura-Hata 3 0 -8 -15 -15
(Huawei)
The letter f represents frequency.
Setting principles: This parameter is configured separately in the uplink and in the downlink. The value of
this parameter varies with Propagation Model are UL/DL Carrier Frequency. Modify the values based
on specific requirements of the scenario.
3.2.12 MIMO Scheme

MIMO mode is represented as "MxN", indicating that the numbers of transmit and receive antennas are M
and N, respectively. The RND supports the following MIMO modes:
Downlink MIMO schemes:
 1x2
 2x2 SFBC
 4x2 SFBC+FSTD
 4T2Ports
 8T2Ports
 4x2 BF (supported only in the LTE TDD system)
 8x2 BF (supported only in the LTE TDD system)
The 4x2 SFBC+FSTD scheme is mapped to using four ports. The 4T2Ports, 8T2Ports, 4x2 BF and 8x
2 BF schemes are mapped using two ports. In the LTE TDD system, the 4x 2 BF and 8x
2 BF schemes can be selected. The beamforming feature brings capacity gain, which is fixed.
Uplink MIMO modes:
 1x2
 1x4
 1x8
Setting principles: Set the parameter based on system requirements. Set the uplink and downlink MIMO
modes in pairs. Take the compatibility between the beamforming feature and MIMO mode into
consideration.
3.2.13 Target Load

This parameter determines the number of RBs that can be used in the uplink and downlink. The value of
this parameter represents the average load of the entire network. The loads of the serving cell and
neighboring cell are set to this value. The default value is 100% in both the downlink and uplink. The
parameter can be modified by using the slider. The adjustment precision of 5%.
Setting principles: Set the parameter as required.
3.2.14 RBs can be Used

This parameter indicates the number of RBs that can be used with a certain bandwidth and load. It is
configured separately in the uplink and in the downlink. Set the parameter for the uplink based on the value
of PUCCH Overhead. PUCCH Overhead is displayed in the RND, but its value cannot be modified.
The following table lists the number of RBs that can be used (rounding down) when the load is 70% in the
downlink.
Table 3.2.14.1.1.1.1.1 Number of downlink RBs that can be used at different bandwidths when the load is 70%
Bandwidth (MHz) Total Number of RBs
1.4 6 x 70% = 4
3 15 x 70% = 10
5 25 x 70% = 17
10 50 x 70% = 35
15 75 x 70% = 52
20 100 x 70% = 70
The following table lists the number of RBs can be used (round down) when the load is 70% in the uplink
and PUCCH Overhead is set to the default value.
Table 3.2.14.1.1.1.1.2 Number of uplink RBs can be used when the load is 70% and PUCCH Overhead is set
to the default value
Bandwidth (MHz) PUCCH Overhead Total Number of RBs
1.4 2 (6 - 2) x 70% = 2
3 4 (15 - 4) x 70% = 8
5 4 (25 - 4) x 70% = 14
10 6 (50 - 6) x 70% = 30
15 8 (75 - 8) x 70% = 46
20 10 (100 - 10) x 70% = 63
Setting principles: The values of preceding parameter depend on the bandwidth, uplink and downlink load,
and PUCCH overhead.
3.2.15 Area Coverage Probability

This parameter indicates the coverage probability in the area. The parameter value varies with the
morphology type. The following table lists the default values of this parameter.
Table 3.2.15.1.1.1.1.1 Relationship between morphology types and the area coverage probability
Morphology Dense Urban SubUrban Rural Hotspot
Urban Area
Area Coverage Probability 95% 95% 90% 90% 90%
Setting principles: The value of this parameter depends on the morphology type. You can modify this
parameter as required.
3.2.16 Edge Coverage Probability

This parameter indicates the coverage probability at the cell edge. The parameter value depends on the area
coverage probability and shadow fading standard deviation. The parameter is displayed on the RND tool,
but its value cannot be directly modified.
Setting principles: The value of this parameter varies with the area coverage probability and shadow fading
standard deviation.
3.2.17 Std.of Shadow Fading

This parameter indicates the shadow fading standard deviation. The unit is dB. The parameter value varies
with the scenario and the indoor and outdoor environment. The following table lists the default values of
this parameter.
Table 3.2.17.1.1.1.1.1 Default values of Std.of Shadow Fading in the indoor and outdoor environment
Morphology DU U SU RA HST
Indoor 11.7 9.4 7.2 6.2 6.2

Outdoor 10 8 6 6 6
Setting principles: The value of this parameter varies with the morphology type and UE environment.
Modify the parameter as required.
3.2.18 Ior/Ioc
This parameter indicates the interference factor of the neighboring cell. The unit is dB. The parameter is
separately set in the uplink and in the downlink. The default values are as follows:
 DL Cell Edge Ior/Ioc: 1.78 dB
 UL Cell Edge Ior/Ioc: 0.65 dB
Setting principles: A larger value of this parameter indicates more severe interference from a neighboring
cell to the serving cell. If the parameter is set to 0, no date is transmitted in the neighboring cell, which
means no neighboring cell is deployed.
3.2.19 Interference Margin

This parameter indicates interference margin. The unit is dB. The parameter is separately set in the uplink
and in the downlink. The RND supports the calculate mode and Enter mode. When the Enter mode is
selected, the value of this parameter is entered manually during link budget. When the calculate mode is
selected, the value is calculated during link budget.
Setting principles: The calculate mode is recommended. You can modify this parameter as required.
3.2.20 Shadow Fading Margin

This parameter indicates the shadow fading margin. The unit is dB. The value of this parameter depends on
coverage probability at the cell edge, shadow fading standard deviation and hard handover gain.
Setting principles: The value of this parameter varies with the area coverage probability and shadow fading
standard deviation. You can modify this parameter as required.
3.2.21 Hard handover Gain

This parameter indicates the hard handover gain. The unit is dB. The value of this parameter varies with the
area coverage probability and shadow fading standard deviation. The following table lists the specific
values.
Table 3.2.21.1.1.1.1.1 Relationship between the hard handover gain, area coverage probability, and shadow
fading standard deviation.
Area Coverage Probability
90% 91% 92% 93% 94% 95%
Shadow 12 4.19 4.23 4.28 4.33 4.38 4.45

fading
standard 11 4.6 4.7 4.81 4.93 5.07 5.22
deviation
10 3.41 3.44 3.48 3.52 3.56 3.61
9 2.29 2.25 2.21 2.17 2.12 2.07
8 2.61 2.64 2.67 2.7 2.74 2.78
7 1.6 1.55 1.5 1.45 1.39 1.32
6 1.82 1.83 1.85 1.88 1.9 1.93
Setting principles: This parameter depends on the area coverage probability and shadow fading standard
deviation. You can modify this parameter as required.
3.3 Equipment Parameters

3.3.1 eNodeB Parameters
3.3.1.1 eNodeB Total Tx Power
This parameter indicates the total transmit power of the eNodeB. The unit is dBm. The value of this
parameter depends on the eNodeB model and system bandwidth. The default value is 46 dBm. In the TDD
mode, the eNodeB transmit power is 49 dBm when the 8x2 BF scheme is used, and is 33 dBm when the
Microcell propagation mode is used.
Setting principles: The value of this parameter depends on other parameters. You can manually modify the
parameter based on the system configurations.
3.3.1.2 eNodeB Noise Figure

This parameter indicates the eNodeB noise figure. The unit is dB. The default value depends on the duplex
mode and frequency. The following table lists the specific values.
Table 3.3.1.2.1.1.1.1 The relationship between eNodeB Noise Figure, Duplex Mode, and Carrier Frequency
Frequency (MHz) 700 800 850 900 1500 1700 1800 2100 2300 2600
FDD eNodeB Noise 2.3 2.3 2.3 2.3 2.3 2 2.3 2.3 2.3 2.5
Figure (dB)
TDD eNodeB Noise 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5 3.5
Figure (1T/2T/4T)
(dB)
TDD eNodeB Noise 4 4 4 4 4 4 4 4 4 4

Figure (8T) (dB)
Setting principles: The value of this parameter depends on the uplink and downlink frequency and the
duplex mode. You can manually modify the parameter according to the system configurations.
3.3.1.3 eNodeB Antenna Height

This parameter indicates the height of the eNodeB antenna above the ground. The unit is m. The default
value depends on the morphology. The following table lists the specific values.
Table 3.3.1.3.1.1.1.1 eNodeB antenna height in difference morphology types
Morphology Dense Urban Urban Suburban Rural Area High Railway
eNodeB Antenna 30 30 35 40 20
Height (m)
In the Microcell propagation mode, The default value is 5. In the Cost231 WI propagation mode, the default eNodeB
height is 12.5 m.
Setting principles: The value of this parameter varies with the morphology type. You can manually modify
the parameter based on the system configurations.
3.3.1.4 eNodeB Antenna Gain

This parameter indicates eNodeB antenna gain. The unit is dBi. The default value depends on the
frequency. The following table lists the specific values.
Table 3.3.1.4.1.1.1.1 Default values of eNodeB antenna gain in different frequencies

Frequency (MHz) 700 800 850 900 1500 1700 1800 1900 2100 2300
eNodeB Antenna 15 15 15 15 18 18 18 18 18 18
Gain (dBi)
Setting principles: The value of this parameter depends on the frequency. You can manually modify the
parameter based on the system configurations.
3.3.1.5 eNodeB Cable Loss

This parameter indicates the loss in cables between the antenna and the RRU, including the loss in the
feeders and jumpers, and on the connections. The unit is dB.
Setting principles: Set the parameter according to the installation mode of the RRU. If the RRU is mounted
on a tower, set the parameter to 0.5 dB. Otherwise, set the parameter to 3 dB.
3.3.2 UE Parameters
3.3.2.1 UE Total Tx Power
This parameter indicates the maximum transmit power of the UE. The unit is dBm. The LTE protocol
specifies that the maximum transmit power of the UE is 23 dBm.
Setting principles: Set the parameter as required. The default value is 23 dBm.
3.3.2.2 UE Noise Figure

This parameter indicates the UE noise figure. The unit is dB.
Setting principles: Set the parameter as required. The default value is 7.
3.3.2.3 UE Antenna Height
This parameter indicates the UE antenna height. The unit is m.
Setting principles: Set the parameter as required. The default value is 1.5 m.
3.3.2.4 UE Antenna Gain

This parameter indicates the UE antenna gain. The unit is dBi. UEs generally use omnidirectional antennas,
which do not offer antenna gain. When the UE type is CPE, the antenna gain ranges from 2 dB to 5 dB.
4 Operation Guide
4.1 Calculating the Cell Coverage Radius When the Service Rate at the
Cell Edge Is Known
This functional module performs the positive calculation of traffic channel in the link budget. It calculates
the uplink and downlink coverage radius based on the known uplink and downlink service rate at the cell
edge of the traffic channel and the used MCS.
4.1.1 Parameters Involved

4.1.1.1 Edge Rate
 DL Edge Rate
This parameter indicates the downlink service rate at the cell edge. The unit is kbit/s.
Setting principles: Set the parameter as required. The value of this parameter must be equal to or
smaller than the downlink service rate supported by the highest-order MCS. The default values are as
follows:
− PS: 1024 kbit/s
− VoIP 7.95: 256 kbit/s
− VoIP 12.2: 336 kbit/s
 UL Edge Rate
This parameter indicates the uplink service rate at the cell edge. The unit is kbit/s.
Setting principles: Set the parameter as required. The value of this parameter must be equal to or
smaller than the downlink service rate supported by the highest-order MCS. The default values are as
follows:
− PS: 256 kbit/s
− VoIP 7.95: 256 kbit/s
− VoIP 12.2: 336 kbit/s
4.1.1.2 MCS Used

 DL MSC Used
This parameter indicates the MCS used in the downlink.
Setting principles: Set the parameter as required. The default value is QPSK 0.19. With the same the
edge rate, a lower-order MCS indicates more RBs are required and the downlink coverage distance is
longer. When the service rate at the cell edge is set too high or the MCS is set too low, the number of
RBs required exceeds the number of RBs available in the system.
 UL MSC Used
This parameter indicates the MCS used in the uplink.
Setting principles: Set the parameter as required. The default value is QPSK 0.31. The power of the
UE is evenly distributed on the allocated RBs. With the same service rate at the cell edge, a lower-
order MCS indicates that fewer RBs are required. In this case, the coverage radius increases and then
decreases. When the service rate at the cell edge is set too high or the MCS is set too low, the number
of RBs required exceeds the number of RBs available in the system.
When selecting the uplink MCS, use the UL MCS Optimization module in the Tools tab to query the
MCS that allows the longest coverage distance with the uplink rate. For detailed information about
how to use this tool, see Chapter 5"Operation Guide for Useful Tools".
4.1.1.3 Outdoor Edge RSRP Requirement

This parameter indicates the edge RSRP in the valid coverage area of the RS. The unit is dB.
Setting principles: Set the parameter as required. The default value is outdoor -105.
4.1.1.4 Edge RS SINR Requirement

This parameter indicates the RS SINR that meets the minimum demodulation capability requirement. The
unit is dB. This parameter is used to evaluate the actual coverage capability of the RS.
Setting principles: Set the parameter as required. The default value is -3.
4.1.2 Operation Guide

1. Set global parameters, scenario parameters, eNodeB parameters, and UE parameters as required.
2. Choose Edge Rate in the Edge Rate → Cell Radius module. Separately set the parameter for the
downlink and uplink. The parameter value can be set based on the default values or to values provided
by the customer, as shown in the following figure.
Figure 4.1.2.1.1.2.1 The Edge Rate parameter in Edge Rate → Cell Radius
3. Select an appropriate modulation order to roughly calculate the number of RBs used. The RB number
will be automatically modified in subsequent steps based on the RB usage. The default value is
determined based on past experience. You can modify the value if required, as shown in the following
figure.
Figure 4.1.2.1.1.3.1 The MCS Used parameter in Edge Rate → Cell Radius
4. Click Para Check & Execute & Output in the module and the system will automatically check the
parameters. If the parameters are incorrectly set, the system will display a message providing
suggestions for modification. If the parameters are correctly set, the Link Budget Output tab displays
the dimensioning output of the uplink and downlink traffic channels, as shown in the following figure.
 Subcarriers to Distribute Power

 This parameter indicates the number of carriers to over which the transmit power is distributed. It is
separately configured in the uplink and the downlink. The number of downlink subcarriers = 12 x the
number of RBs.
This parameter indicates the antenna connector power on each subcarrier. The unit is dBm. The
parameter value depends on the number of subcarriers, antenna gain, feeder loss, and body loss.
 SINR
This parameter indicates the receiver SINR that meets the requirement of the predetermined edge rate
and the number of RBs used. The unit is dB.
 Receiver Sensitivity/Subcarrier
This parameter indicates the receiver sensitivity on each subcarrier. The unit is dB.
 Min Signal Reception/Subcarrier
This parameter indicates the minimum signal reception strength on each subcarrier. The unit is dB.
 Max Allowed Path Loss
This parameter indicates the maximum allowed path loss. It corresponds to the maximum coverage
radius. The unit is dB.
 Coverage Radius for Diff Channels
This parameter indicates the coverage radius for different channels. The unit is km.
 Cell Radius
This parameter indicates the minimum coverage radii of different channels. Minimum coverage radius
refers to the coverage distance provided when the signal quality is lowest in the channels. The unit of
this parameter is km.
 Outdoor RSRP threshold to Meet Cell Edge Data Rate Requirement
This parameter indicates the outdoor RSRP at a specific edge rate. The unit is dB.
 Coverage Radius Based on Outdoor RSRP Requirement
This parameter indicates the coverage radius that meets the outdoor RSRP requirement. The unit is
km.
 Coverage Radius Based on RS SINR Requirement
This parameter indicates the maximum cell coverage radius that meets the requirement of cell edge RS
demodulation capability. The unit is km.
4.2 Calculating the Cell Edge Rate When the Cell Radius Is provided
This module performs reverse calculation of the traffic channel in link budget. The cell edge rate can be
calculated after the cell radius and the number of RBs used in the uplink and downlink are entered.

4.2.1.1 RB Used
 DL RB Used
This parameter indicates the number of RBs used in the downlink. With the same cell radius, larger
number of RBs indicates higher service rate at the cell edge.
Setting principles: Set the parameter as required. The default value is 23. When verifying the results of
the direct or reverse calculation, set this parameter to the same value as number of the RBs obtained in
the direct calculation result.
 UL RB Used
This parameter indicates the number of RBs used in the uplink. With the same cell radius, larger
number of RBs indicates higher cell edge rate.
Setting principles: Set the parameter as required. The default value is 4. The number of available RBs
is calculated in an associated manner based on the bandwidth and PUCCH Overhead. The number of
RBs = 2a x 3b x 5c. When verifying the direct and reverse calculation results, set this parameter to the
same value as number of the RBs obtained in the direct calculation result.
4.2.1.2 Cell Radius

This parameter indicates the cell coverage radius. The unit is km.
Setting principles: Set the parameter based on the scenario. The default value is 23. When verifying the
direct and reverse calculation results, set this parameter to the same value as the minimum coverage radii of
the channels in the direct calculation result.

2. Choose RB Used in the Cell Radius → Edge Rate module. Set the number of RBs that are used in
the downlink and the uplink. Do not set the number of downlink RBs as larger than the maximum
number of RBs allowed by the predetermined cell load. Several options for the number of uplink RBs
are available in the interface. Select a number based on system requirements, as shown in the
following figure.
Figure 4.2.2.1.1.2.1 The RB Used parameter in Cell Radius → Edge Rate
3. Enter the radius of the cell being calculated, as shown in the following figure.
Figure 4.2.2.1.1.3.1 The Cell Radius parameter in Cell Radius → Edge Rate
4. Click Para Check & Execute & Output. The tool will automatically check whether the parameters
involved are correctly set and prompt the checking result. If the parameters are correctly set, the
dimensioning result of the uplink and downlink traffic channels will be displayed on the Link Budget
Output tab page.
4.3 RSRP Dimensioning

4.3.1 Calculating the Outdoor RSRP that Meets the Cell Edge Date Rate
Requirement
This function is integrated into the control channel dimensioning module, and is used to calculate the RSRP
of a cell. The coverage radius of the cell is calculated when the edge data rate is known.
Both the traffic channel coverage radius and the outdoor RSRP of the cell are displayed on the Link
Budget Output tab page.
Figure 4.3.1.1.1.1.1 Outdoor RSRP threshold to meet the cell edge data rate
4.3.2 Calculating the RS Coverage Radius When the Outdoor RSRP Is

provided
1. This function is integrated into the Edge Rate → Cell Radius module. Enter the outdoor RSRP. The
default value is -105. Set the parameter as required, as shown in the following figure.
Figure 4.3.2.1.1.1.1 Input parameters for calculating the RS coverage radius when the outdoor RSRP is known
2. Both the traffic channel coverage radius and the coverage radius that meets the outdoor RSRP
requirement are displayed on the Link Budget Output tab page.
Figure 4.3.2.1.1.2.1 Output parameters for calculating the RS coverage radius when the outdoor RSRP is known
4.3.3 Calculating the RS Coverage Radius When the Indoor (Outdoor) RS

Demodulation Threshold Is Known
1. This function is integrated into the Edge Rate → Cell Radius module. Enter the indoor (outdoor) RS
demodulation threshold. The default value is -3. Set the value as required, as shown in the following
figure.
Figure 4.3.3.1.1.1.1 Input parameters for calculating the RS coverage radius when the indoor (outdoor) RS
demodulation threshold is known
2. When the traffic channel coverage radius is being calculated, the RS coverage radius that meets the
edge RS SINR requirement is displayed on the Link Budget Output tab page, as shown in the
following figure.
Figure 4.3.3.1.1.2.1 Input parameters for calculating the RS coverage radius when the indoor (outdoor) RS
demodulation threshold is known
4.4 Calculating the Control Channel Coverage

This module calculates the control channel coverage to help determine whether the cell radius is limited by
the coverage distance of control channels. It supplements the direct calculation of the coverage radius
performed in link budget.

4.4.1.1 PDCCH Format
This parameter indicates the format of the downlink control channel. The following figure shows the
options of this parameter.
Table 4.4.1.1.1.1.1.1 PDCCH Format

PDCCH Format
DCI 0/1a
DCI 2
DCI 2a
DCI 3/3a
 DCI 0: For carrying the PUSCH scheduling permission.
 DCI 2: For carrying PDSCH scheduling information.
 DCI 1a: For carrying PDSCH scheduling information in compression mode.
 DCI 2a: For carrying encrypted compressed PDSCH scheduling information.
 DCI 3: For carrying TPC commands for PUCCH and PUSCH power adjustment.
 DCI 3a: For carrying information about PUCCH and PUSCH power adjustment.
Setting principles: Set the parameter based on system requirements. The default value is DCI 0/1a.
4.4.1.2 PDCCH CCEs Used

This parameter indicates the convergence of RBs in the downlink control channel. The following table lists
the parameter values.
Table 4.4.1.2.1.1.1.1 PDCCH CCEs Used

PDCCH CCEs Used
1 CCE
2 CCE
4 CCE
8 CCE
Based on the CCE convergence, the PDCCH can be classified into the four types: 1CCE, 2CCE, 4CCE, and
8CCE. Higher level of convergence indicates better demodulation performance. Therefore, only the 8CCE
PDCCH is used in link budget. For different DCI formats, the demodulation threshold varies when the
same CCE is used.
Setting principles: Set the parameter based on system requirements. The default value is 8 CCE.
4.4.1.3 PUCCH Format

This parameter indicates the PUCCH format. There are six types of PUCCH format, as shown in the
following table.
Table 4.4.1.3.1.1.1.1 PUCCH Format

PUCCH Format
Format 1/1a
Format 1b
Format 2
Format 2a
Format 2b
 Format 1: For carrying scheduling request identifier (SRI) when a UE sends a request to an eNodeB
for PUSCH resources
 Format 1a: For carrying 1-bit ACK message, indicating that a UE receives a TB in the downlink
 Format 1b: For carrying 2-bit ACK message, indicating that a UE receives two TBs in the downlink.
 Format 2: For carrying the CQI or for carrying CQI+1 information or 2-bit HARQ ACK/NACK
messages when extended CP is used
 Format 2a: For carrying CQI and 1-bit ACK message. It is used when a UE sends ACK and CQI at
the same time.
 Format 2b: For carrying CQI and 2-bit ACK message. It is used when a UE sends ACK and CQI at
the same time. Demodulation threshold varies with PUCCH formats.
Setting principles: Set the parameter as required. The default value is Format 1/1a.
4.4.1.4 PRACH Format

This parameter indicates the PRACH format. The values are as follows:
Table 4.4.1.4.1.1.1.1 PRACH Format

PRACH Format
Burst 0
Burst 1
Burst 2
Burst 3
Burst 4
Burst 0 supports cells with maximum radius less than 15 km. Burst 1, burst 2, and burst 3 support cells with
radius larger than 15 km. Burst 4 support only TDD mode. The PRACH supports the MIMO mode of 1
RX, 2 RX, 4 RX, and 8 RX, and uses 6 RBs.
Setting principles: Set the parameter as required. The default value is Burst 0.

1. The control channel coverage needs to be considered in actual network capacity dimensioning. In the
Control Channel Coverage module, select the control channel formats and corresponding RS power
offset. If no special requirement is made, use the default value.
Figure 4.4.2.1.1.1.1 Input parameters in Control Channel Coverage
2. After completing the calculation of the traffic channel radius, click Para Check & Execute & Output
in the module to check the parameters and display the dimensioning results of the uplink/downlink
control channel on the Link Budget Output tab page.
3. After the control channel estimation is performed, the coverage radius for different channels can be
obtained. The minimum coverage radius of a channel is used as its actual coverage radius, as is shown
in the following figure.
Figure 4.4.2.1.1.3.1 Output parameters in Control Channel Coverage
4.5 Site Scale Dimensioning

This module is used to estimate the site scale. The estimation provides a reference for the site scale
planning.

4.5.1.1 Surface Area to Be Covered
This parameter indicates the surface area to be covered. The unit is km2.
Setting principles: Set the parameter according to the site area planning. The default value is 100.
4.5.1.2 Cell Radius for Estimation

This parameter indicates the coverage radius of a single cell. The parameter value can be obtained using the
Input or Calculate mode. When the calculate mode is used, the parameter is automatically set to the cell
radius obtained in link budget using direct calculation. When the Input mode is used, the coverage radius is
manually entered for estimating the site number in the area. The default mode is Calculate mode.
Setting principles: The calculate mode is recommended. When the cell coverage radius is known, use the
input mode.

2. In the Sites Estimation of Coverage module, obtain the cell radius by calculating the cell radius that
meets the edge rate requirement, or manually enter the cell radius if it is known, as shown in the
following figure:
Figure 4.5.2.1.1.2.1 Input parameter for site scale dimensioning
3. The Link Budget Output tab displays the number of sites needed for the seamless coverage in the
region, as shown in the following figure.
Figure 4.5.2.1.1.3.1 Output parameter for dimensioning the site scale
4.6 Capacity Dimensioning

4.6.1.1 Cell Radius for Capacity Dimensioning
This parameter indicates the cell radius for capacity dimensioning. The parameter value can be obtained by
using the Input mode or Calculate mode. In Input mode, the cell radius is manually entered. In Calculate
mode, the cell radius is obtained from the result of the direct calculation in link budget. Other parameters
are obtained from the Input Parameters tab page.
Setting principles: It is recommended that you use the calculate mode. When the site distance is different
within the same group of parameters, use the input mode.
4.6.1.2 Capacity Features
The following features are included:
 Adaptive ICIC
This feature is used to increases the cell edge throughput. It can be used in both the FDD and TDD
modes, and is disabled by default.
 Improved FSS
This feature is the improved frequency selection scheduling. It can be used in both FDD and TDD
modes. Due to different surge responses; frequencies provide different gains for different users.
Therefore, select a superior combination to transmit data. The gain of this feature is predetermined and
cannot be changed in the interface.
 4Rx V-MIMO
This feature is the uplink 4 Rx virtual MIMO. Two users with good orthogonality can form a virtual
MIMO to increase the uplink throughput. This feature can be used in both FDD and TDD modes.
However, it can be used only when the eNodeB is equipped with four receiving antennas.
 TDD MU-BF
TDD MU-BF is short for TDD multi-user beam forming. It can be used only in TDD mode in
conjunction with multi-users MIMO. When the 4x2 BF or 8x2 BF mode is selected, this feature is
enabled in an associated manner.
 FDD Intra-eNodeB UL CoMP
FDD Intra-eNodeB UL CoMP is short for FDD Intra-eNodeB uplink multi-point coordination. It was
developed in eRAN2.2 and is commercially used in eRAN6.0. The gain of this feature is
predetermined and cannot be changed in the interface.
Table 4.6.1.2.1.1.1.1 Use of feature combinations in FDD mode

Adaptive Improved FSS 4Rx V- TDD MU- FDD Intra-
ICIC MIMO BF eNodeB UL
CoMP
Adaptive ICIC Downlink Downlink only

only
Improved FSS Downlink Uplink only Uplink only
only
4Rx V-MIMO Uplink only Uplink only
TDD MU-BF
FDD Intra- Uplink only Uplink only
eNodeB UL
CoMP
The cell indicates that the combination cannot be used.

Table 4.6.1.2.1.1.1.2 Use of feature combinations in TDD mode
Adaptive Improved 4Rx V- TDD MU- FDD Intra-
ICIC FSS MIMO BF eNodeB UL
CoMP
Adaptive ICIC Downlink Downlink Downlink

only only only
Improved FSS Downlink Uplink only Downlink
only only
4Rx V-MIMO Uplink only
TDD MU-BF Downlink Downlink Downlink
only only only
FDD Intra-eNodeB
UL CoMP
Setting principles: During link budget, the preceding features are disabled by default. During the
capacity dimensioning, you are advised to enable all the features in compliance with the eNodeB
version, or enable some of the features based on the scenario requirements. If the features are
incorrectly selected, the RND will display a message which contains operation instructions.

2. In the Capacity Dimensioning module, obtain the cell radius by calculating the cell radius the meets
the edge rate requirement, or manually enter the cell radius if it is known, as shown in the following
figure.
Figure 4.6.2.1.1.2.1 Input parameters of the cell radius in Capacity Dimensioning
3. Determine whether to enable capacity-related features that are consistent with system configurations.
If the feature selection is incorrect, the system will display the following message:
Figure 4.6.2.1.1.3.1 Feature selection in Capacity Dimensioning
4. Click Para Check & Execute & Output in the module and the system will automatically check
whether the parameters involved are correctly set. If the parameters are incorrectly set, the system
displays an error message. If the parameters are correctly set, the Capacity Dimensioning Output tab
displays the uplink/downlink capacity dimensioning results, as shown in the following figure:
Figure 4.6.2.1.1.4.1 Output parameter in Capacity Dimensioning
5. The following figure shows the visual comparison of uplink/downlink SINR distribution in difference
scenarios.
Figure 4.6.2.1.1.5.1 SINR distribution in Capacity Dimensioning
4.7 Evaluating the Balance Between Coverage and Capacity

This module evaluates the balance between the area coverage, cell edge rate and capacity. By doing this, a
reference can be provided for the dimension of the network traffic and the entire network condition.

4.7.1.1 Network Area to be Covered
This parameter indicates the area to be covered for the evaluating the balance between the coverage and
capacity. The unit is km2.
Setting principles: Set the parameter as required. The default value is 100 km2.
4.7.1.2 Total Expected DL/UL Capacity of Network

This parameter indicates the total expected uplink/downlink capacity of the network.
Setting principles: The parameter is separately set in the uplink and in the downlink. Its values vary with
scenarios, and are generally provided by the customer. The default value is 45000 Mbit/s in the downlink
and 25000 Mbit/s in the uplink in dense urban areas.
4.7.1.3 DL/UL RBs Used for Cell Edge User
This parameter indicates the number of RBs that are used by cell edge users. The parameter is used to
evaluate the cell edge throughput with corresponding coverage and cell capacity. It is separately set in the
uplink and in the downlink.
Setting principles: Set the parameter as required. The default values are both 10 RBs in the uplink and in
the downlink.

2. Enter the coverage area, total expected uplink/downlink capacity, and number of uplink/downlink RBs
used by cell edge users, as shown in the following figure:
Figure 4.7.2.1.1.2.1 Input parameters in Balance between Coverage and Capacity
3. Click Para Check & Execute & Output in the module and the system will automatically check
whether the parameters involved are correctly set. If the parameters are incorrectly set, the system
displays an error message. If the parameters are correctly set, the Capacity Dimensioning Output tab
will display the evaluation results of the balance between coverage and capacity, including the number
of sites required to meet the coverage requirement, the number of sites required to meet the capacity
requirement, and the corresponding cell edge rate.
Figure 4.7.2.1.1.3.1 Output parameters for the balance between coverage and capacity
4. The following figure shows the curve comparison of the number of sites needed to support the
coverage, the number of sites needed to provide required capacity, and the corresponding cell edge
rate.
Figure 4.7.2.1.1.4.1 Curve comparison for the balance between coverage and capacity
Perform the comparison separately in the uplink and in the downlink. Otherwise, the result may not be
obtained due to incorrect inputs.
4.8 Active Subscribers Number Dimensioning

Calculation of the number of active subscribers invokes the capacity dimensioning module. As a result,
when the values of parameters on this interface are changed, the values of corresponding parameters on the
Input Parameters tab page are changed to the same values.

4.8.1.1 Morphology
This parameter indicates the scenario for calculating the number of active subscribers. When the value of
this parameter is changed, the value of Morphology on the Input Parameters tab page is changed to the
same value.
Setting principles: Set the parameter based on system requirements. The default value is Dense Urban.
4.8.1.2 Bandwidth
This parameter indicates the system bandwidth for calculating the number of active subscribers. The unit is
MHz. When the value of this parameter is modified, the value of Bandwidth parameter is changed in an
associated manner on the Input Parameters tab page.
4.8.1.3 Cell Radius

This parameter indicates the cell radius for calculating the number of active subscribers. The unit is km.
When this parameter is modified, the value of the Cell Radius for Capacity Dimensioning parameter on
the Input Parameters tab page is changed to the same value.
Setting principles: Set the parameter based on system requirements. The default value is 0.29, which
corresponds to the Dense Urban morphology.
4.8.1.4 DL Carrier Frequency and UL Carrier Frequency

These parameters indicate the system uplink and downlink carrier frequencies for evaluating the number of
active subscribers. The unit is MHz. When the values of these parameters are changed, the values of the DL
Carrier Frequency and UL Carrier Frequency parameters on the Input Parameters tab page are
changed to the same values.
Setting principles: Set the parameter based on system requirements. The default values are both 2600 for
the uplink and the downlink.
4.8.1.5 DL System Load and UL System Load

These parameters indicate the system uplink and downlink load for evaluating the number of active
subscribers.
Setting principles: Set the parameter based on system requirements. The default values are both 100% for
the uplink and the downlink.
4.8.1.6 DL Spectral Efficiency and UL Spectral Efficiency

These parameters indicate the uplink and downlink spectral efficiency for the specified system load. The
unit is bit/s/Hz.
Setting principles: The values of these parameters are obtained by calculation. These parameters are
displayed but cannot be set.
4.8.1.7 Std. of DL Spectral Efficiency and UL Spectral Efficiency

These parameters indicate the standard deviation of the uplink and downlink spectral efficiency in the
system for which the number of active users is calculated.
Setting principles: The values of these parameters are obtained by calculation. These parameters are
displayed but cannot be set.
4.8.1.8 User Idle Time

This parameter indicates the user idle duration. The unit is s.
Setting principles: This parameter is set by system configurations. The default value is 20.
4.8.1.9 GoS Probability

This parameter indicates the service loss rate of a system.
Setting principles: This parameter is set by system configurations. The default value is 2%.
4.8.1.10 VoIP DL Offered Traffic L_GBR/ and VoIP UL Offered Traffic L_GBR
These parameters indicate the voice traffic volume of VoIP users. They are separately set for the uplink and
downlink. The unit is merlang.
Setting principles: The value of this parameter is provided by the customer. The values are both 16
merlang for the uplink and downlink.
4.8.1.11 File Sharing DL Offered Bit Rate per Session and File Sharing UL
Offered Bit Rate per Session
These parameters indicate the average download and upload bit rate of each file sharing user in a session.
The unit is kbit/s. The reading time during packet call needs to be taken into account when this rate is
calculated.
Setting principles: The value of this parameter is provided by the customer. The default value is 30 for the
downlink and 5 for the uplink.
4.8.1.12 Chat DL Offered Bit Rate per Session and Chat UL Offered Bit Rate
per Session
These parameters indicate the average download and upload bit rate of each chat user during a session. The
unit is kbit/s.
Setting principles: The value of this parameter is provided by the customer. The default value is 0.3 for the
downlink and 0.3 for the uplink.
4.8.1.13 VoIP DL Rate of Active User and UL Rate of Active User

These parameters indicate the average bit rate of each VoIP user in the active state. They are separately set
for the uplink and downlink. The unit is kbit/s.
4.8.1.14 VoIP DL Utilization of Active User and VoIP UL Utilization of Active

User
These parameters indicate the average resource usage rate of each VoIP user in the active state. They are
separately set for the uplink and downlink. The unit is merlang.
4.8.1.15 File Sharing DL Rate of Active User and File Sharing UL Rate of Active
User
These parameters indicate the average transmission rate of each file sharing user in the active state. They
are separately set for the uplink and downlink. The unit is kbit/s.
4.8.1.16 File Sharing DL Utilization of Active User and File Sharing UL

Utilization of Active User
These parameters indicate the average resource usage rate of each file sharing user in the active state. The
parameters are separately set in the uplink and downlink. The unit is merlang.
4.8.1.17 Chat DL Rate of Active User and Chat DL UL Rate of Active User
These parameters indicate the average transmission rate of each chat user in the active state. They are
separately set for the uplink and downlink. The unit is kbit/s.
4.8.1.18 Chat DL Utilization of Active User and Chat UL Utilization of Active

User
These parameters indicate the average resource usage rate of each chat user in the active state. They are
separately set for the uplink and downlink. The unit is merlang.
4.8.1.19 DL Active User Number and UL Active User Number
These parameters indicate the maximum number of active users supported by the system. The parameter
values depend on the system capacity and the usage of VoIP, File Sharing and Chat services.
These output parameters indicate the maximum number of active users calculated based on the parameter settings. The
actual processing capacity of the system baseband unit in use is not considered. When calculating the actual number of
active users, take the maximum number of active users supported by the product version into consideration.

1. Set scenario parameters and traffic model parameters on the Active User Number tab page. For
detailed settings of these parameters, see section 4.7.2"Operation Guide". When the values of these
parameters are changed, the same parameters on the Active User Number tab page are changed to the
same values.
2. Click Execute in the active subscribers number dimensioning module to invoke the capacity
dimensioning module for iterative operation to obtain the standard deviation of the spectral efficiency
at different loads.
3. After the iterative calculation is performed, the number of active users supported by the system
configurations in a cell can be obtained.
The number of active users is limited by the processing capability of the baseband unit. Therefore, the
number of active users must be set as smaller than the limit.
4.9 S1&X2 Traffic Dimensioning

4.9.1.1 Throughput/eNodeB
This parameter indicates the busy-hour throughput of the eNodeB. It is separately set for the uplink and
downlink. The unit is Mbit/s. The following table lists the eNodeB throughput value in different scenarios.
Table 4.9.1.1.1.1.1.1 eNodeB throughput in different scenarios

Scenario eNodeB Downlink Throughput eNodeB Uplink Throughput (Mbit/s)
(Mbit/s)
DU 90.0 64.5
U 82.5 58.8
SU 67.7 42.1
RA 58.2 35.9
Setting principles: Set the parameter according to the actual system capacity. The default value is 90 for the
downlink and 60 for the uplink.
The value of this parameter is obtained in capacity dimensioning.
4.9.1.2 Packet Size
This parameter indicates the size of users' data packets, which is the weighted average size of packets
calculated based on the proportion of each service type on the network. The unit is bytes.
Setting principles: Set the parameter based on the service type. The default value is 700.
4.9.1.3 GTPU Head

This parameter indicates the header field overhead at the GPRS tunneling protocol (GTP) layer on the user
plane. The unit is bytes.
Setting principles: The default value is 12.
4.9.1.4 UDP Head

This parameter indicates the overhead of UDP packets. The unit is bytes.
4.9.1.5 IPsecHead
This parameter indicates the IPsec header overhead. The unit is bytes.
Setting principles: The default value of this parameter is 70.
4.9.1.6 VLAN Head

This parameter indicates the VLAN header overhead. The unit is bytes.
4.9.1.7 MAC Head

This parameter indicates the MAC header overhead. The unit is bytes.
4.9.1.8 IP Head
This parameter indicates the IP header overhead. The unit is bytes. The IPV4 header overhead is 20 bytes,
and IPV6 header overhead is 40 bytes.
4.9.1.9 Peak to Ave Ratio

This parameter indicates the peak to average ratio of the traffic over the S1 interface. It is used to calculate
the transport bandwidth margin, which is used for handling peak throughput and signaling storm.
The following table lists the values of Peak to Ave Ratio in difference scenarios.
Table 4.9.1.9.1.1.1.1 Values of Peak to Ave Ratio in different scenarios

Scenario Peak to Ave Ratio
Dense Urban 1.4

Urban 1.2
SubUrban 1.1
Rural Area 1.0
Setting principles: Set the parameter as required. The default value is 1. When the brief estimate mode is
used, this parameter takes effect on both the user plane and control plane. When the exact calculate mode is
used, it takes effect only on the control plane.
4.9.1.10 S1 Control Signalling

This parameter indicates the mode of calculating the signaling traffic on the control plane over the S1
interface. The parameter can be set to Brief Estimate or Exact Calculate. When this parameter is set to
Brief Estimate, the Control to User Ratio parameter is available. That is, the user-plane signaling traffic
multiplied by 1% to 3% is converted into control-plane signaling traffic.
When this parameter is set to Exact Calculate, the Control to User Ratio parameter is not unavailable.
The detailed calculation process is displayed. The Exact calculate mode is used if required by the
customer.
Setting principles: Select the calculation mode according to customer requirements. The default mode is
Brief Estimate.
4.9.1.11 Control to User Ratio

This parameter specifies the ratio at which the user-plane signaling traffic is converted into control-plane
signaling traffic. The parameter value ranges from 1% to 3%. The parameter value is determined based on
the simulation data and live network statistics for a simplified calculation. This parameter is available when
the S1 Control Signalling parameter is set to Brief Estimate.
Setting principles: Select a ratio according to network requirements. The default value is 2%.
4.9.1.12 eNodeB Maximum Online User

This parameter indicates the maximum number of active users supported by an eNodeB. The parameter
value depends on the eNodeB version and system bandwidth.
Setting principles: Set the parameter based on system requirements. The default value is 5400 for eRAN2.2
with a bandwidth of 20 MHz, and 10800 for eRAN6.0 with a bandwidth of 20 MHz.
4.9.1.13 S1 Interface Number

This parameter indicates the number of S1 interfaces deployed on an eNodeB. The parameter value
depends on the eNodeB version and the system mode.
Setting principles: Set the parameter based on system requirements. The default value is 4. Restriction: The
maximum value is 16 for eRAN6.0. In multi-operator core network (MOCN) scenario or S1-flex
networking scenarios, the value must be greater than 1.
4.9.1.14 X2 Interface Number

This parameter indicates the number of X1 interfaces deployed on an eNodeB. The parameter value
depends on the eNodeB version and the system mode.
Setting principles: Set the parameter based on system requirements. The default value is 32. The maximum
number of X2 interfaces is 64 for an eRAN6.0 eNodeB.
4.9.1.15 S1/X2 Message Redundancy Ratio
This parameter indicates the message redundancy ratio over the S1 and X2 interface. The parameter value
is used to evaluate the bandwidth margin for signaling transmission.
Setting principles: Set the parameter based on system requirements. The default value is 1.3.
4.9.1.16 Peak: Average Transport Dimensioning Ratio on eNodeB Side

This parameter indicates the peak to average ratio of control messages on the eNodeB. It can be used to
handle problems such as signaling storm.
4.9.1.17 Huawei S1/X2 Traffic Model

100%
The parameters in this group display the detailed user and signaling information. indicates
0.8
that the value can be entered or modified. indicates that the value is obtained by calculating
0.2
related parameters. indicates that the value is a calculation result or is not considered for
singling calculation.
For detailed calculation of the parameters in this group, see eRAN6.0 Network Dimensioning High Level
Design.
Setting principles: Set the parameter based on system requirements or obtain the parameter value by
referring to traffic statistics. The parameter value depends on the systems that are used in the sites
conditions. No default value is provided.
4.9.1.18 X2 to S1 Ratio
This parameter indicates the ratio of signaling traffic over the X2 interface to the signaling traffic over the
S1 interface. The value ranges from 1% to 3%. The parameter value is determined based on the simulation
data and live network statistics for a simplified calculation.
Setting principles: Set the parameter according to the system requirements. The default value is 2%.
4.9.1.19 Physical Packet Size

This parameter indicates the size of the original user-plane packets prefixed with various header fields on
the physical layer. The parameter value depends on the original user-plane packet size and the size of the
header overheads.
4.9.1.20 OverHead Ratio

This parameter indicates the ratio of Physical Packet Size to Packet Size. With the same size of header
overheads and cell throughput, a larger value of the Packet Size indicates a smaller value of Overhead
Ratio, which means lower transmission bandwidth is required on the user plane.
4.9.1.21 DL User Plane Throughput and UL User Plane Throughput

These parameters indicate the uplink and downlink throughput on user plane over the S1 interface. The unit
is Mbit/s. The parameter value depends on the value of Packet Size and the cell throughput.
4.9.1.22 S1-AP Message
This parameter indicates the traffic of S1-AP signaling messages, which is a part of the S1 control plane
signaling. The unit of this parameter is kbit/s. The parameter is separately set for the uplink and downlink.
The required bandwidth equals to the larger between the uplink and downlink traffic.
4.9.1.23 S1-SCTP Heatbeat Message

This parameter indicates the traffic of S1-SCTP signaling messages, which is a part of the S1 control plane
4.9.1.24 X2-AP Message

This parameter indicates the traffic of X2-AP signaling messages, which is a part of the X2 control plane
4.9.1.25 X2-SCTP Heatbeat Message

This parameter indicates the traffic of X2-SCTP signaling messages, which is a part of the X2 control plane
4.9.1.26 1588 V2 PTP message

This parameter indicates the traffic of clock synchronization signals. The unit is kbit/s. The parameter
value depends on the system duplex mode. The parameter is separately set for the uplink and downlink.
4.9.1.27 Total Transmission Requirement for High Priority Message

These parameters indicate the traffic of S1 control plane signaling messages. The parameter value is the
sum of the S1-AP signaling traffic and S1-SCTP signaling traffic. The unit of this parameter is kbit/s. The
parameter is separately set for the uplink and downlink. The required bandwidth equals to the larger
between the uplink and downlink traffic.
4.9.1.28 DL Control Plane Throughput and UL Control Plane Throughput

These parameters indicate the traffic of S1 control plane signaling messages. The unit is Mbit/s. The
parameter is separately set for the uplink and downlink. When the S1 Control Signalling parameter is set
to Brief Estimate, the value of this parameter is calculated based on the traffic on the user plane. When the
S1 Control Signalling parameter is set to Exact Calculate, the value of this parameter equals to the value
of the Total Transmission Requirement for High Priority Message parameter.
4.9.1.29 S1 DL Throughput and S1 UL Throughput

These parameters indicate the traffic over the S1 interface, including user plane traffic and control plane
traffic. The unit is Mbit/s. The parameter is separately set for the uplink and downlink.
4.9.1.30 Throughput of S1 Interface

This parameter indicates the traffic volume over the S1 interface. The unit is Mbit/s. The parameter value
equals to the larger value between S1 Downlink Throughput and S1 Uplink Throughput.
4.9.1.31 Throughput of X2 Interface
This parameter indicates the traffic over the X2 interface. The unit is Mbit/s. When the S1 Control
Signalling is set to Brief Estimate, the value of this parameter equals to the value of the Throughput of
S1 Interface parameter, which is converted based on X2 to S1 Ratio. When the S1 Control Signalling is
set to Exact Calculate, the value of this parameter is obtained by calculating the actual traffic over the X2
interface.
4.9.1.32 Clock synchronization

This parameter indicates the traffic of clock synchronization signals. The unit is kbit/s. When the Brief
Estimate mode is selected, this parameter does not have an output value. When the Exact calculate mode is
selected, the output parameter value is the actual clock synchronization traffic obtained by calculation.

1. Set input parameters in the S1&X2 Interface Dimensioning tab. The key parameter is
Throughput/eNodeB, which must be set based on scenario requirements, bandwidth, and load. For
example, for an eNodeB with 100% load and a bandwidth of 20 MHz in dense urban area, the
throughput is about 95 Mbit/s in the downlink and 66 Mbit/s in the uplink. See Section 4.9.1 for the
setting of other parameters.
2. The traffic of control signaling over the S1 interface can be calculated by using the Brief Estimate
mode or Exact calculate mode based on site requirements. The Brief Estimate mode is selected by
default, as shown in the following figure.
Figure 4.9.2.1.1.2.1 Calculation modes for the traffic volume of S1 control signaling
When the Exact calculate mode is selected, the detailed calculation process for traffic over S1 and X2
interfaces as well as the traffic of clock synchronization signals is displayed. You can modify the
parameters based on the system configurations.
The following figure shows the parameters, which are mainly network interface and system parameters,
during the exact calculation.
Figure 4.9.2.1.1.2.2 Key parameters for the exact calculation of traffic over the S1 and X2 interfaces
The following figure shows the output information about the traffic over the S1 and X2 interfaces, and
clock synchronization traffic.
Figure 4.9.2.1.1.2.3 Output information for the calculation of traffic over the S1 and X2 interfaces and clock
synchronization
3. In different calculation modes, click Execute to obtain the bandwidth requirements for the S1 and X2
interfaces of an eNodeB.
In Exact Calculate mode, you need to obtain the exact site information from the operator or by referring to general
parameters.
4.10 Calculating the TA Paging Capacity

4.10.1.1 ECU Board Num/MME
This parameter indicates the number of ECU boards deployed in each MME. The parameter value depends
on the network system.
4.10.1.2 Attached Users Num/MME

This parameter indicates the number of attached users of an MME. The parameter value depends on the
actual network.
4.10.1.3 Max Paging Times/ECU/s

This parameter indicates the maximum paging times per second supported by each ECU board. The
parameter value depends on the version and performance of the device.
Setting principles: Set the parameter based on system requirements. The default value is 14000
times/ECU/s for Huawei ECU boards.
4.10.1.4 Paging Times/Attached Subscriber @ BH

This parameter indicates the paging times of each attached user during busy hours. The parameter value
depends on the traffic mode.
Setting principles: Set the parameter based on the actual traffic mode. In LTE networks, this parameter is
set to 2.17.
4.10.1.5 Paging Cycle (Pc)

This parameter indicates the user paging cycle. The parameter can be set to 32 frames, 64 frames, 128
frames, and 256 frames.
Setting principles: Set the parameter based on system requirements. The default value is 128 frames for
Huawei baselines.
4.10.1.6 Paging Subframe/Cycle (nB)

This parameter indicates the number of paging subframes in each paging cycle. The parameter can be set to
4T, 2T, T, 1/2 T, 1/4 T, 1/8 T, 1/16T, and 1/32T (T stands for paging cycle).
Setting principles: Set the parameter based on system requirements. The default value is 1 (the number of
subframes equals to the paging cycle) for Huawei baselines.
4.10.1.7 Max User Supported/eNodeB

This parameter indicates the maximum number of active users supported by an eNodeB. The parameter
value depends on the eNodeB version and product specifications.
Setting principles: Set the parameter based on system requirements. A Huawei eRAN6.0 eNodeB supports
a maximum of 10800 active users.
4.10.1.8 Bandwidth
This parameter indicates the system bandwidth. The unit is MHz.
4.10.1.9 Senior Parameters

This parameter indicates setting modes of the senior parameters in TA estimation. When the parameter is
set to Default, the senior parameters are set to their default values. When this parameter is set to Input, the
values of the senior parameters can be modified.
Setting principles: Set the parameter as required. The default value is Default.
Senior parameter setting:
 SCR_Paging: Indicates the speed of modulation and coding. If QPSK0.10 is adopted, the value
of SCR_Paging is 0.10.
 ModTypeOrder: Indicates the order of the modulation mode. If QPSK0 .10 is adopted, the value of
ModTypeOrder is 2.
 k: Indicates other massages contained in a paging message, such as systemInfoModification and etws-
Indication. The default value is 2.
 Ui: Indicates the S-TMSI IE. The default value is 40.
 REpdsch: Indicates the number of valid REs in an RB pair that can be used to transmit data. The
parameter value equals to 168 minus the RS overhead and PDCCH overhead. The parameter value
depends on the MIMO mode and PDCCH overhead. For more information about the values of this
parameter, see eRAN6.0 Network Dimensioning High Level Design.
 CRL(CCE): Indicates the CCE convergence level in PDCCH. This parameter can be set to 1, 2, 4, and
8. The default value is 4.
4.10.1.10 Paging Users/PO (Pun)
This parameter indicates the maximum number of paging users supported by each paging subframe. The
parameter value depends on the bandwidth.
Setting principles: When a certain bandwidth is select, this parameter is configured in an associated
manner.
4.10.1.11 Scheduling Blocks/Frame

This parameter indicates the number of scheduling blocks contained in a frame. The parameter value
depends on the bandwidth.
Setting principles: When a certain bandwidth is select, this parameter is configured in an associated
manner.
4.10.1.12 Max PDSCH Load (%)

This parameter indicates the maximum PDSCH frame load allowed by an eNodeB. The parameter
value is provided by the operator. Generally, the value does not exceed 3%.
Setting principles: Obtain the parameter value from the customer. The default value is 3%.
4.10.1.13 PDCCH Overhead (symbol)

This parameter indicates the number of symbols occupied by the PDCCH overhead. It determines the
number of CCEs available.
4.10.1.14 Max PDCCH Load (%)

This parameter indicates the paging load of the PDCCH, which is provided by the operator. Generally, the
parameter value does not exceed 1%.
4.10.1.15 CPU Occupancy (%)

This parameter indicates the usage rate of CPU resources that the eNodeB allocates for paging. It
determines the performance that serves the maximum number of paging users. The parameter value is
generally 60% for Huawei CPUs.
Setting principles: Set the parameter based on system requirements. The default value is 60%.
4.10.1.16 Max Paging Blocking (%)

This parameter indicates the maximum paging blocking rate. The parameter value is provided by the
operator. Generally, the parameter value does not exceed 2%.
4.10.1.17 eNodeB Num/TA list under MME Constraint

This parameter indicates the maximum number of eNodeBs in the TA list, which is subjected to the MME.
4.10.1.18 eNodeB PDSCH Paging Capacity

This parameter indicates the paging capacity of the eNodeB PDSCH. The unit is pages/s.
4.10.1.19 eNodeB PDCCH Paging Capacity
This parameter indicates the paging capacity of the eNodeB PDCCH. The unit is pages/s.
4.10.1.20 eNodeB CPU Paging Capacity

This parameter indicates the paging capacity allowed by the eNodeB CPU. The unit is pages/s.
4.10.1.21 eNodeB Blocking Paging Capacity

This parameter indicates the paging capacity allowed by the eNodeB paging blocking rate. The unit is
pages/s.
4.10.1.22 eNodeB Num/TA list under eNodeB Constraint

This parameter indicates the maximum number of eNodeBs in the TA list, which is subjected to the
eNodeB. The parameter value depends on factors such as PDSCH, PDCCH, CPU, and paging blocking.
4.10.1.23 eNodeB Num/TA list

This parameter indicates the maximum number of eNodeBs in the TA list, which is subjected to the MME
and eNodeB.

1. Enter related parameters in the TA Paging Capacity tab. Obtain the values of the Max PDSCH
Load, Max PDCCH Load, and Max Paging Blocking parameters from the customer. Select the
setting mode for Senior Parameters to display the setting of senior parameters, as shown in the
following figure. For detailed information about the setting method, see Section 4.10.1"Parameters
Involved".
Figure 4.10.2.1.1.1.1 Senior parameter setting for TA paging
2. After entering the parameters, click Execute to obtain the maximum number of eNodeBs in the TA
list which is subjected to the MME and eNodeB.
Figure 4.10.2.1.1.2.1 Outputs of the TA paging capacity calculation
Infinity indicates that the capacity is not limited.
4.11 E-MBMS Coverage Dimensioning

4.11.1.1 Morphology
This parameter indicates the scenario. The default value is Dense Urban. For more information, see section
3.2.1"Morphology".
4.11.1.2 Environment
This parameter indicates the UE environment. The default value is Outdoor.
4.11.1.3 Propagation Model

This parameter indicates the propagation model used. The default value is Cost231-Hata(Huawei).
4.11.1.4 Bandwidth
This parameter indicates the system bandwidth. The default value is 20.
4.11.1.5 DL MIMO Scheme

The parameter indicates the downlink MIMO modes. Currently, the E-MBMS does not support the MIMO
mode. The default value of this parameter is 1x2.
4.11.1.6 DL PB
This parameter indicates the downlink power distribution, which affects the service data and RS
distribution. The default value is 0.
4.11.1.7 Max Transceiver Power

This parameter indicates the maximum transmit power of the eNodeB. The unit is dBm. The default value
is 46.
4.11.1.8 DL Frequency
This parameter indicates the downlink frequency. The unit is MHz. The default value is 2600.
4.11.1.9 Transceiver Antenna Height

This parameter indicates the eNodeB antenna height. The unit is m. The default value is 30. For more
information, see section3.3.1.3.
4.11.1.10 Receiver Antenna Height
This parameter indicates the UE antenna height. The unit is m. The default value is 1.5 m.
4.11.1.11 Transceiver Cable Loss

This parameter indicates the eNodeB feeder loss. The unit is dB. The default value is 0.5. For more
information, see section 3.3.1.5.
4.11.1.12 Receiver Cable Loss

This parameter indicates the UE feeder loss. The unit is dB. Generally, the parameter is set to 0 dB on the
UE.
4.11.1.13 Transceiver Body Loss

This parameter indicates the body loss of the eNodeB. The unit is dB. The default value is 0.
4.11.1.14 Receiver Body Loss

This parameter indicates the body loss of the UE. The unit is dB. The E-MBMS is a data service. Therefore,
the value is generally set to 0.
4.11.1.15 Interference Margin

This parameter indicates the downlink interference margin. The unit is dB. The E-MBMS transmits data
jointly in multiple cells. Therefore, interference is not generated between cells and this parameter is
generally set to 0.
4.11.1.16 Receiver Noise Figure

This parameter indicates the UE noise figure. The unit is dB. The parameter is generally set to 7 on Huawei
LTE UEs. For more information, see section 3.3.2.2.
4.11.1.17 Std.of Shadow Fading

This parameter indicates the standard deviations of slow fading. The unit is dB. The default value is 11.7.
4.11.1.18 Penetration Loss

This parameter indicates the penetration loss. The unit is dB. The default value is 20.
4.11.1.19 Area Coverage Probability (%)

This parameter indicates the area coverage probability. The default value is 95. For more information, see
section 2.2.15.
4.11.1.20 Duplex Mode

This parameter indicates the system duplex mode. E-MBMS supports both the FDD and TDD modes. The
default value is TDD.
4.11.1.21 MBSFN Combined Layers Num

This parameter indicates the number of MBSFN combined layers. The default value is 4.
4.11.1.22 MBS Subframe
This parameter indicates the number of MBS subframes used. The value ranges from 1 to 6 for FDD
systems, and from 1 to 5 for TDD systems. The default value is 5.
4.11.1.23 The Range of DL Edge Rate

This parameter indicates the range of the downlink edge rate. The value depends on the number of MBS
subframes and can be modified within a certain range.
4.11.1.24 UE Velocity
The parameter indicates the UE velocity. Currently, the RND supports only the speed of 3 km/h.
4.11.1.25 Cyclic Prefix

This parameter indicated the cyclic prefix configuration used. MBMS uses only extended CPs, which
greatly increases the coverage area. However, the data rate is limited.
4.11.1.26 SINR Request

This parameter indicates the minimum SINR required for an UE to demodulate the MBMS data. The unit is
dB. The parameter value is specified in the protocol.
4.11.1.27 MBMS Coverage Radius

This parameter indicates the MBMS coverage radius. The unit is km.
4.11.1.28 MCS Index

This parameter indicates the modulation order used by E-MBMS. The parameter value depends on SINR
Request.

1. Enter the parameters in the E-MBMS Coverage tab. See preceding sections for the values of the
parameter. If SPM is selected as the propagation mode, the following options are displayed.
Table 4.11.2.1.1.1.1.1 Senior parameters for calculating the E-MBMS coverage

SPM Parameters
K1- 　 27.43
K2- 　 44.9
K3- 　 5.83
K4- 　 0.5
K5- 　 -6.55
K6- 　 1
Clutter Loss- 0
2. After entering the parameters, click Execute to obtain the E-MBMS coverage radius.
Table 4.11.2.1.1.2.1.1 Output parameters for E-MBMS coverage calculation

Budget Results
Penetration Loss(dB) 20
Std.of Shadow Fading(dB) 11.7
Area Coverage Probability 0.95
Edge Coverage Probability 88.70%
Shadow Fading Margin(dB) 8.9
Max Allowed Path Loss(dB) 138.1
MBMS Coverage Radius(km) 0.7
MCS Index 18
4.12 Indoor Pico Base Station and DAS Dimensioning

Because outdoor macro eNodeBs are similar to the pico base stations and DAS, this section describes only
parameters dedicated to pico base stations and DAS. For details about the parameter settings same as those
of outdoor macro eNodeBs, see Chapter 3"Settings of Common Parameters"Settings of Common
Parameters.
4.12.1.1 Scenario Parameters
4.12.1.1.1 Morphology
The parameter indicates the indoor morphology types, including:
 Recreation Ground
 Office Building
 Supermarket
 Hotel
 Airport/Show
 Park
Setting principles: Set the parameter to the actual morphology type. The default value is Airport/Show.
4.12.1.1.2 Channel Model

This parameter indicates indoor channel models. Currently, the RND supports the following channel
models:
 Winner II-A1:used in SOHO scenarios, such as small offices, home offices, and hotels, where there
are many rooms and space is not open
 Winner II-B3: Used in indoor hotspot scenarios, such as exhibition centers and airports, where the
space is open
Setting principles: Set the parameter based on site requirements. The default value is Winner II-A1.
4.12.1.1.3 Propagation Model
This parameter indicates indoor channel models. Currently, the RND supports the following propagation
models:
 Keenan-Motley
 ITU-R P.1238
Both of the preceding models are based on the calibration of propagation models in the free space. The
combination of ITU-R P.1238, Frequency, Morphology truthfully reflects the indoor environment.
Setting principles: Set the parameter based on site requirements. The default value is ITU-R P.1238.
4.12.1.1.4 DL MIMO Scheme

The parameter indicates the downlink MIMO mode used in pico base stations. The following MIMO modes
are supported:
 1x2
 2x2 SFBC (diversity):Used to improve coverage capability when the signal quality is poor in the
channels
 2x2 MCW (multiplexing): Used to improve data rate when the signal quality is good in the channels
Setting principles: Set the parameter as required. The signal quality is generally good indoors. Therefore,
the default value is 2x2 MCW.
4.12.1.1.5 Sight Type

The parameter indicates the indoor sight types, which include:
 LOS (line of sight)
 NLOS (non line of sight)
Setting principles: Set the parameter as required. Generally, the coverage spans across walls. Therefore, the
default value is NLOS.
4.12.1.1.6 UL/DL Penetr Loss

These parameters indicate uplink/downlink penetration loss. The unit is dB. The parameter values depend
on the environment and the blocking capability of obstacles. Generally, the penetration loss depends on the
thickness and quantity of walls.
Setting principles: Set the parameter as required. The default value is 20 for both the uplink and downlink.
4.12.1.1.7 ULDL Interf Margin

This parameter indicates the interference from inter-RAT or intra-RAT frequencies to the serving cell. The
unit is dB. In actual networking, the interference margin must be configured to counteract the decrease of
signal quality.
Setting principles: Set the parameter as required. The default value is both 2 dB for the uplink and
downlink.
4.12.1.1.8 HHO Gain

This parameter indicates the hard handover gain, which refers to the link gain provided when an indoor UE
accesses a neighboring cell. The unit of this parameter is dB.
Setting principles: Set the parameter as required. The indoor hard handover range and the signal
quality difference are small. Therefore, the default value is set to 2 dB
4.12.1.1.9 Pico/UE Tx Power

This parameter indicates the maximum transmit power of the Pico base station and UE. The unit is dBm.
Setting principles: Set the parameter as required. The indoor hard handover range is small, and the signal
quality varies little indoors. Therefore, the default value is 2.
4.12.1.1.10 Pico/UE Tx Power

This parameter indicates the maximum transmit power of pico base stations or UEs. The unit is dB.
Setting principles: Set the parameter based on the equipment specifications. The default value is 24 for pico
base stations, and 23 for UEs.
4.12.1.1.11 Pico/UE Antenna Gain

This parameter indicates antenna gain of the pico base station or UE. The unit is dBi.
Setting principles: Set the parameter as required. The default value is 2 for pico base stations, and 0 for
UEs.
4.12.1.1.12 Pico/UE Noise Figure

This parameter indicates the noise figure of the pico base station or UE. The unit is dB.
UEs.
4.12.1.1.13 Pico/UE Cable Loss

This parameter indicates cable loss of the pico base station and UE. The unit is dB.
UEs.
4.12.1.1.14 Pico JumConLoss

This parameter indicates jumper and connector loss of pico base stations and UEs. The unit is dB.
Setting principles: Set the parameter based on system requirements. The default value is 0.5 for pico base
stations, and 0 for UEs.
4.12.1.1.15 UE Body Loss

This parameter indicates the UE body loss. The unit is dB.
Setting principles: Set the parameter based on the service type. For PS services, the parameter is generally
set to 0. For VoIP services, the parameter is generally set to 3.

4.12.2.1 Pico Base Station Parameters
4.12.2.1.1 UL/DL Edge Rate
This parameter indicates the uplink/downlink service rate at the cell edge. The unit is kbit/s.
Setting principles: Set the parameter based on coverage requirements. The default value is 2000 for the
uplink and 3000 for the downlink.
4.12.2.1.2 UL/DL MCS Selected
This parameter indicates the selected modulation scheme at the cell edge.
Setting principles: Set the parameter based on coverage requirements. The default value is 64QAM0.66 in
the uplink and 64QAM0.65 in the downlink.
4.12.2.1.3 Total Num of Floor
The parameter indicates the number of floors that need to be covered.
Setting principles: Set the parameter based on coverage requirements. The default value is 10.
4.12.2.1.4 Cover Area per Floor
This parameter indicates the area of each floor that needs to be covered. The unit is m 2.
4.12.2.1.5 Num of Floor per Pico
This parameter indicates the planned number of floors covered by a pico base station. The parameter value
depends on the actual coverage capability of the base station.
Setting principles: Set the parameter based on the coverage capability of the pico base station. The
penetration loss is high for the coverage across floors. Therefore, the default value is 1.
4.12.2.1.6 Cell Radius
This parameter indicates the coverage radius of the pico base station. The unit is m.
Setting principles: Set the parameter based on the planned coverage radius of the pico base station. The
default value is 10.
4.12.2.1.7 UL/DL RB Used
These parameters indicate the number of uplink/downlink RBs used by users at the cell edge.
Setting principles: The value of this parameter depends on the scheduling algorithm and the number of
users. The default value is 4 in the uplink and 8 in the downlink.
4.12.2.2 DAS Parameters

4.12.2.2.1 Building Length
This parameter indicates the length of a building. The unit is m.
Setting principles: Set the parameter to the actual building length. The default value is 150.
4.12.2.2.2 Building Width
This parameter indicates the width of a building. The unit is m.
Setting principles: Set the parameter to the actual building width. The default value is 30.
4.12.2.2.3 Floor Height
This parameter indicates the height of a building. The unit is m.
Setting principles: Set the parameter to the actual building height. The default value is 5.
4.12.2.2.4 Building Floors
This parameter indicates the number of floors in a building that need to be covered.
Setting principles: Set the parameter to the actual number of floors in the building. The default value is 20.
4.12.2.2.5 eNodeB Location
The parameter indicates the location of the eNodeB in the building. The parameter can be set to one of the
following values:
 Edge: indicates that the eNodeB is located at the bottom or top of the building.
 Middle: indicates that the eNodeB is located in the middle floors of the building.
Setting principles: Set the parameter based on the actual location of the eNodeB. The default value is
Middle.
4.12.2.2.6 Weak Current Well Location
This parameter indicates the location of the weak current well. The weak current well can be installed in the
following locations:
 Corner: indicating that the weak current well is located in the corner of the floor
 Middle_LongSide: indicating that the weak current well is located at the middle long side of the floor
 Middle_WideSide: indicating that the weak current well is located at the middle wide side of the floor
 Center: Center: indicating that the weak current well is located in the center of the floor
Setting principles: Set the parameter based on the actual location of the weak current well. The default
value is Corner.
4.12.2.2.7 Insert Loss
This parameter indicates the insertion loss of the devices. The unit is dB.
Setting principles: Set the parameter based on device specifications. The default value is 0.3.
4.12.2.2.8 MR Cable Type
This parameter indicates the type of main feeder, which determines the loss of a main feeder per 100 m.
Setting principles: Set the parameter to the type of main feeder used. The default value is AVA5 7/8.
4.12.2.2.9 Br Cable Type
This parameter indicates the branch feeder type, which determines the loss of a branch feeder per 100 m.
Setting principles: Set the parameter to the branch feeder type selected. The default value is AVA5 7/8.
4.12.2.2.10 Initial Sectorization
This parameter indicates the number of initialized sectors. The parameter value depends on the networking
mode.
Setting principles: Set the value based on the number of floors. The default value is 5.
4.12.2.2.11 eNodeB Antenna Gain
This parameter indicates the downlink antenna gain of the DAS. The unit is dBi.
Setting principles: Set the parameter based on device specifications. The default value is 2.
4.12.2.2.12 eNodeB Max Power
This parameter indicates the maximum transmit power of the DAS. The unit is dBm.
4.12.2.2.13 eNodeB Body Loss
This parameter indicates the body loss of the DAS. The unit is dB.
4.12.2.2.14 eNodeB Noise Figure
This parameter indicates the noise figure of the DAS. The unit is dB.
4.12.2.2.15 UE Max Power
This parameter indicates the maximum transmit power of the UE. The unit is dBm.
Setting principles: The parameter is generally set to 23 for LTE UEs.
4.12.2.2.16 UE Body Loss
This parameter indicates the UE body loss. The unit is dB.
4.12.2.2.17 UE Noise Figure
This parameter indicates the UE noise figure. The unit is dB.
4.12.2.2.18 UE Cable Loss
This parameter indicates the feeder loss of the UE. The unit is dB.
4.12.2.2.19 Standard Power
This parameter indicates the maximum effective transmit power allowed for a single antenna port on a
DAS. The unit is dBm. The parameter can be set to 15 or 23.
Setting principles: Set the parameter based on the electromagnetic requirements. The default value is 15 for
the primary standard.
4.12.2.2.20 Expected Radius
This parameter indicates the expected radius of a single antenna on the DAS. The unit is m.
4.12.2.2.21 Edge RSRP
This parameter indicates the expected RSRP at the cell edge. The unit is dBm.
Setting principles: Set the parameter based on coverage requirements. The default value is -105.
4.12.2.2.22 UL/DLRB Used
These parameters indicate the number of uplink/downlink RBs used by users at the cell edge.
Setting principles: Set the parameter based on actual resources. The default value is 4 in the uplink and 8 in
the downlink.

4.12.3.1 Calculating the Pico Coverage Radius When the Service Rate at the Cell
Edge Is Known
1. Set global parameters, scenario parameters, and equipment parameters as required.
2. Set the parameters on the interface, as shown in the following figure.
Figure 4.12.3.1.1.2.1 Interface of the functional parameters for calculating the coverage radius of the pico base
station when the service rate at the cell edge is known
3. Click Execute to obtain the calculation results, as shown in the following figure.
Figure 4.12.3.1.1.3.1 Calculation results for the coverage radius of the pico base station when the service rate at
the cell edge is known
4.12.3.2 Calculating the Service Rate at the Cell Edge When the Coverage Radius of
the Pico Base Station Is Known
2. Set the interface parameters, as shown in the following figure.
Figure 4.12.3.2.1.2.1 Interface of the functional parameters for calculating the service rate at the cell edge of the
pico base station when the coverage radius is known
Figure 4.12.3.2.1.3.1 Calculation results for the service rate at the cell edge when the coverage radius of the pico
base station is known
4.12.3.3 Calculating the DAS Coverage

2. Set the parameters on the interface, as shown in the following figure.
Figure 4.12.3.3.1.2.1 Parameters for calculating the DAS coverage
Figure 4.12.3.3.1.3.1 Calculation results for the DAS coverage

5 Operation Guide for Useful Tools
5.1 Performing Positive and Reverse Calculation of the Distance and Path
Loss
Set Morphology, Propagation Model, Frequency, eNodeB Antenna Height, and UE Antenna Height,
and PropagationCM, as shown in the following figure.
Figure 5.1.1.1.1.1.1 Common parameters for the positive and reverse calculation of distance and path loss
5.1.2 Calculating the Path Loss When the Distance Is Known

Enter the distance. The path loss is obtained based on the propagation model, as shown in the following
figure.
Figure 5.1.2.1.1.1.1 Calculating the path loss when the distance is known
5.1.3 Calculating the Distance When the Path Loss Is Known

Enter the path loss. The distance is obtained based on the propagation model, as shown in the following
figure.
Figure 5.1.3.1.1.1.1 Calculating the distance when the path loss is known
5.2 Calculating the Service Rate and RB Quantity

Set Duplex Mode, DL MCS Used, and UL MCS Used, as shown in the following figure.
Figure 5.2.1.1.1.1.1 Common parameter for calculating the MCS-RB-Rate
5.2.2 Calculating the Data Rate Based on the MCS and Number of RBs
The data rate can be calculated based on the number of RBs used and MCS, as shown in the following
figure.
Figure 5.2.2.1.1.1.1 Calculating the data rate based on the MCS and number of RBs
5.2.3 Calculating Number of RBs Based on the MCS and Data Rate
The number of RBs used can be calculated based on the data rate and MCS, as shown in the following
figure.
Figure 5.2.3.1.1.1.1 Calculating the number of RBs based on the MCS and the data rate
5.3 Optimizing the Uplink MCS

1. Set the uplink service rate at the cell edge.
2. Set the uplink service rate at the cell edge. The UL MCS Optimization tool calculates the number of
RBs used and the maximum path loss supported when different MCS are used, as shown in the
following figure.
Figure 5.3.1.1.1.2.1 Output information of unlink MCS optimization
3. Select an appropriate MCS based on the number of RBs used and the coverage radius.
Figure 5.3.1.1.1.3.1 Output information of unlink MCS optimization in curves
5.4 Calculating the Feeder Loss

After the frequency, cable type, manufacturer, cable length, and connector loss are entered, the cable loss
can be calculated, as shown in the following figure.
Figure 5.4.1.1.1.1.1 Cable loss calculation
Only cables provided by Andrew support the cable loss calculation.
5.5 Calculating Indoor RSRP, EIRP, and Cell Radius

1. Enter the related parameters, as shown in the following figure.
Figure 5.5.1.1.1.1.1 Parameters involved in the calculation of indoor RSRP, EIRP, and Cell Radius
2. Click Execute to obtain the RS coverage radius, as shown in the following figure.
Figure 5.5.1.1.1.2.1 Calculation results of indoor RSRP - EIRP - Cell Radius
5.6 Calculating Indoor Signaling Strength at the Cell Edge

1. Enter the related parameters, as shown in the following figure.
Figure 5.6.1.1.1.1.1 Parameters involved in indoor cell edge signal calculation
2. Click Execute to obtain the signal strength of the serving cell and downlink IoT, as shown in the
following figure:
Figure 5.6.1.1.1.2.1 Parameter output for the indoor cell edge signal calculation
5.7 Operation Suggestions

 Suggestions for the Operation Flowchart:
(1) The positive calculation in link budget includes calculation on both the traffic and control
channels. The interference margin in the control channel comes from the traffic channel. Therefore,
perform the calculation on the traffic channel first.
(5) When the calculate mode is used to calculate the cell radius for the site scale dimensioning and
capacity dimensioning, perform positive calculation on the traffic channel and control channel in
link budget first.
The following figure shows the operation flowchart.
Figure 5.7.1.1.1.1.1 LTE network dimensioning flowchart
Link budget
eMBMS coverage
Calculate the coverage radius.
dimensining
Calculate the RSRP.
Calculate the service rate at the

cell edge.
Balance between
capacity and coverage
 Suggestions
Capacityfor Parameter Setting
dimensioning Traffic model
(1) When the LTE TDD mode is selected, the carrier frequency must be higher than 1800 MHz, and
the uplink frequency must be the same as the downlink frequency.
(6) The carrier frequency must match the propagation model. The Cost231 propagation model is used
for carrier frequencies higher than 1500 MHz. The Okumura propagation model is used for carrier
frequencies lower than 1500 MHz.
(7) The RND does not support capacity dimensioning in high-speed railway scenarios or when the
Micocell or Cost231-WI propagation model is used.
(8) The penetration loss must match the environment. In outdoor environment, the default value is 0.
(9)S1&X2 Traffic load is setNumber
If the uplink/downlink of active
to 0, subsequent calculation cannot be performed. Therefore, the
uplink/link load must be set to an appropriate value. TA paging capacity
(10)
dimensioning subscribers
When the positive calculation is performed in link budget, the uplink/downlink data rate
cannot exceed the maximum value supported by the bandwidth, load, and MCS.
(11) When the reverse calculation is performed in link budget, the number of downlink RBs must
be smaller than the number of RBs that can be used with the corresponding load.
(12) In capacity dimensioning, the features must be used in accordance with the system
configurations. The RND will display a message when the feature combination is incorrect.
6 Known Issues
7 References Document
[1] RNPS LTE eRAN6.0 Parameter Setting Guide V1.1
[2] RNPS-LTE S1X2 Network Dimensioning Instruction
[3] User Guide to the Active User Number Tool
[4] LTE Location Area Planning for Network Planning Solution v2.00
[5] LTE Location Area Planning for Network Planning Solution v2.00

Wireless Network Solution Design Operation and Application Guide To LTE eRAN6.0 Network Dimensioning

Caricato da

Informazioni sul documento

Titolo originale

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

Wireless Network Solution Design Operation and Application Guide To LTE eRAN6.0 Network Dimensioning

Caricato da

Copyright:

Formati disponibili

Product Name Security Level

LTE RND Internal

Wireless Network Solution Design Operation and

Prepared By Liu Yadong Date 2011-10-30

Huawei Technologies CO., LTD.

Date Revision V CR ID Sec No. Change Description Author

2011-10-30 0.0 Completed the draft Liu Yadong (employee ID:

Acronyms and Abbreviations

DMRS Demodulation Reference Signal

2013-12-16 Huawei confidential. No spreading without Page 3 of 71

PRACH Physical Random Access Channel

2013-12-16 Huawei confidential. No spreading without Page 4 of 71

2013-12-16 Huawei confidential. No spreading without Page 5 of 71

1 About This Document.....................................................................................................................9

3 Settings of Common Parameters..............................................................................................11

5 Operation Guide for Useful Tools...........................................................................................68

1.2 Document Description

1.3 Application Scope

Table 2.1.1.1.1.1.1.1 Principles of the network dimension solution

2.2 Typical Scenarios

3 Settings of Common Parameters

3.1.1.1 TDD UL/DL Subframe Configuration

Table 3.1.1.1.1.1.1.1 LTE TDD uplink/downlink subframe configuration

Table 3.1.1.1.1.1.1.2 Options of LTE TDD uplink-downlink subframe configurations

#0, 5 ms, 1:3

3.1.1.2 LTE TDD Special Subframe Configuration

Table 3.1.1.2.1.1.1.1 TDD special subframe configurations

DwPTS GP UpPTS DwPTS GP UpPTS

Table 3.1.1.2.1.1.1.2 Options of TDD special subframe configuration

Table 3.1.2.1.1.1.1.1 eNodeB type and antenna gain

3.1.3 TMA Used

3.1.3.1 TMA Gain

3.1.5 Adaptive ICIC

3.1.6 Cyclic Prefix

3.1.7 PDCCH Overhead

3.2 Scenario Parameters

3.2.2 Propagation Model

3.2.2.1 SPM Parameters

Table 3.2.2.1.1.1.1.1 SPM propagation model parameters

Default Value 30.37 44.9 5.83 0.5 -6.55 1 0

3.2.2.2 Parameters of the Cost231 Walfish Ikegami propagation model

3.2.4 Channel Model

3.2.5 Service Type

3.2.5.1 Body Loss

3.2.5.2 TTI Bundling Gain

Table 3.2.6.1.1.1.1.1 LTE system bandwidths

3.2.7 Total Number of RBs

Table 3.2.7.1.1.1.1.1 Number of RBs that can be used at different bandwidths

3.2.8 PUCCH Overhead

Table 3.2.8.1.1.1.1.1 Default values of PUCCH Overhead at different bandwidths

3.2.9 Carrier Frequency

3.2.10 Penetration Loss

Table 3.2.10.1.1.1.1.1 Relationship between penetration loss, morphology and frequency

Frequency (MHz) DU U SU RA HST

Table 3.2.11.1.1.1.1.1 Relationships between PropagationCm and Propagation Model

Cost231-Hata(Classic) 3 0 0 -4.78 x -4.78 x (lgf)2+18.33 x

The letter f represents frequency.

3.2.12 MIMO Scheme

3.2.13 Target Load

3.2.14 RBs can be Used

3.2.15 Area Coverage Probability

Area Coverage Probability 95% 95% 90% 90% 90%

3.2.16 Edge Coverage Probability