LTE L13 Radio Network Design: Student Book LZT1380915 R2A

LTE L13 Radio Network Design
STUDENT BOOK
LZT1380915 R2A
LZT1380915 R2A
DISCLAIMER
This book is a training document and contains simplifications.

Therefore, it must not be considered as a specification of the
system.
The contents of this document are subject to revision without

notice due to ongoing progress in methodology, design and
manufacturing.
Ericsson shall have no liability for any error or damage of any kind
resulting from the use of this document.
This document is not intended to replace the technical

documentation that was shipped with your system. Always refer to
that technical documentation during operation and maintenance.
© Ericsson AB 2013
This document was produced by Ericsson.
 The book is to be used for training purposes only and it is

strictly prohibited to copy, reproduce, disclose or distribute it in
any manner without the express written consent from Ericsson.
This Student Book, LZT1380915, R2A supports course number
LZU1089105.
-2 - © Ericsson AB 2013 LZT1380915 R2A

Table of Contents
Table of Contents
1 LTE INTRODUCTION ........................................................................9
1 INTRODUCTION ............................................................................ 10
2 DIMENSIONING PRINCIPLES ....................................................... 13
2 LTE AIR INTERFACE ...................................................................... 15
3 INTRODUCTION ............................................................................ 16
4 LTE DOWNLINK PHYSICAL RESOURCES ................................... 18
4.1 DOWNLINK REFERENCE SIGNALS........................................... 20
4.2 DOWNLINK L1/L2 CONTROL SIGNALING ................................. 21
4.3 SYNCHRONIZATION SIGNALS (SS) .......................................... 22
4.4 BROADCAST CHANNEL ............................................................. 23
4.5 DOWNLINK USER PLANE DATA ................................................ 24
4.6 DOWNLINK USER DATA RATES ................................................ 29
5 LTE UPLINK PHYSICAL RESOURCES.......................................... 33
5.1 UPLINK USER DATA RATES ...................................................... 35
6 LTE UE CAPABILITIES .................................................................. 36
7 LTE FREQUENCY BANDS ............................................................. 37
8 ........................................................................................................... 37
9 RADIO WAVE PROPAGATION ...................................................... 38
9.1 OKUMURA-HATA MODEL .......................................................... 38
9.2 WALFISH-IKEGAMI MODEL........................................................ 39
CHANNEL MODELS ............................................................................ 41
3 LTE TRAFFIC .................................................................................. 43
1 INTRODUCTION ............................................................................ 44
1.1 WEB BROWSING TRAFFIC ........................................................ 45
1.2 EMAIL TRAFFIC .......................................................................... 46
LZT1380915 R2A © Ericsson AB 2013 -3 -

1.3 VIDEO STREAMING TRAFFIC .................................................... 47
1.4 FILE DOWNLOAD TRAFFIC........................................................ 48
1.5 VOICE TRAFFIC .......................................................................... 48
2 INTERNET PROTOCOLS USED FOR LTE TRAFFIC .................... 49
2.1 TRANSMISSION CONTROL PROTOCOL (TCP) ........................ 49
2.1.1 TCP OPERATION ..................................................................... 52
2.1.2 TCP FLOW CONTROL ............................................................. 53
2.1.3 TCP THROUGHPUT ................................................................. 54
2.2 USER DATAGRAM PROTOCOL (UDP) ...................................... 56
2.3 HYPERTEXT TRANSFER PROTOCOL (HTTP) .......................... 58
2.3.1 WEB OPERATION EXAMPLE .................................................. 59
2.4 FILE TRANSFER PROTOCOL (FTP) .......................................... 60
3 VOICE OVER LTE .......................................................................... 61
3.1 HARQ EFFECT ON VOICE SERVICE ......................................... 62
4 LTE DIMENSIONING ....................................................................... 63
1 INTRODUCTION ............................................................................ 64
2 LTE NETWORK DIMENSIONING EXAMPLE ................................. 65
2.1 CELL THROUGHPUT (TCELL) ....................................................... 67
3 UPLINK DIMENSIONING................................................................ 69
3.1 SITE-TO-SITE DISTANCE EXPRESSED AS SIGNAL

ATTENUATION .................................................................................... 70
3.2 POWER CONTROL TARGET ...................................................... 72
3.3 PUSCH LOAD .............................................................................. 72
3.4 UPLINK COVERAGE CALCULATION ......................................... 73
3.4.1 THERMAL NOISE ..................................................................... 74
3.4.2 UPLINK SYSTEM REFERENCE POINT ................................... 76
3.4.3 NOISE RISE ............................................................................. 77

Table of Contents
3.4.4 UL RESOURCE BLOCK ALLOCATION .................................... 78
3.4.5 POWER LEVEL ........................................................................ 79
3.4.6 UL BIT RATES .......................................................................... 80
3.4.7 LOG-NORMAL FADING ............................................................ 82
3.4.8 UL CELL EDGE BIT RATES ..................................................... 83
3.4.9 UL LINK BUDGET ..................................................................... 84
3.5 UL CAPACITY CALCULATION .................................................... 86
3.5.1 AVERAGE RX POWER ............................................................ 86
3.5.2 CELL THROUGHPUT ............................................................... 88
3.5.3 OPTIMIZING POWER CONTROL AND PUSCH LOAD ............ 89
4 DOWNLINK DIMENSIONING ......................................................... 90
4.1 DL COVERAGE ........................................................................... 91
4.1.1 DOWNLINK SYSTEM REFERENCE POINT ............................. 92
4.1.2 DL NOISE RISE AT CELL EDGE .............................................. 93
4.2 DOWNLINK CAPACITY ............................................................... 98
5 DOWNLINK CONTROL CHANNEL COVERAGE............................ 99
6 UPLINK CONTROL CHANNEL COVERAGE ................................ 101
7 RING METHODS .......................................................................... 102
7.1 DL RING METHOD .................................................................... 102
7.2 UL RING METHOD .................................................................... 106
8 TDD DIMENSIONING ................................................................... 106
9 ADDITIONAL FEATURES IMPACTING COVERAGE AND

CAPACITY ......................................................................................... 110
9.1 MINIMUM RATE PROPORTIONAL FAIR SCHEDULING .......... 110
9.2 UL FREQUENCY-SELECTIVE SCHEDULING .......................... 110
9.3 DL FREQUENCY SELECTIVE SCHEDULING .......................... 110
9.4 ANTENNA INTEGRATED RADIO (AIR) ..................................... 111

10 CONTROL CHANNEL DIMENSIONING ..................................... 112
10.1 PHYSICAL SIGNALS ............................................................... 113
10.2 DL CONTROL CHANNELS ...................................................... 113
10.3 POWER USAGE ...................................................................... 119
10.4 UL CONTROL CHANNEL ........................................................ 120
10.5 SOUNDING REFERENCE SIGNAL ......................................... 125
10.6 PAGING CAPACITY ................................................................ 127
10.6.1 MME PAGING CAPACITY .................................................... 127
10.6.2 RBS PAGING CAPACITY ..................................................... 127
11 PCI PLANNING ........................................................................... 135
11.1 PCI PLANNING OBJECTIVES ................................................. 135
11.2 PCI PLANNING RECOMMENDATION .................................... 136
11.3 AUTOMATIC PCI PLANNING .................................................. 137
12 TRACKING AREA DIMENSIONING............................................ 137
12.1 TRACKING AREA PLANNING ................................................. 139
12.1.1 PLANNING STRATEGIES .................................................... 141
5 COLOCATION AND COEXISTENCE ............................................ 145
1 INTRODUCTION .......................................................................... 146
1.1 GUARD BAND AND CARRIER SEPARATION .......................... 148
1.2 LTE RBS RF CHARACTERISTICS ............................................ 148
1.3 OUT OF BAND EMISSION ........................................................ 148
1.4 SPURIOUS EMISSIONS............................................................ 151
2 RECEIVER CHARACTERISTICS ................................................. 154
2.1 ADJACENT CHANNEL SELECTIVITY (ACS) ............................ 154
2.2 RECEIVER BLOCKING ............................................................. 156
3 ADJACENT CHANNEL INTERFERENCE ..................................... 158
3.1 DOWNLINK ACIR (ACIRDL) - RBS TO UE INTERFERENCE ..... 160

Table of Contents
3.2 UPLINK ACIR (ACIRUL) - UE TO RBS INTERFERENCE ........... 161
4 EFFECT OF INTERFERENCE...................................................... 162
4.1 INTERFERENCE EFFECT ON RBS .......................................... 162
4.2 INTERFERENCE EFFECT ON UE ............................................ 163
4.3 SENSITIVITY DEGRADATION DUE TO INTERFERENCE........ 163
4.4 ISOLATION BETWEEN SYSTEMS............................................ 166
4.5 CALCULATION EXAMPLES ...................................................... 168
5 COLLOCATION AND COEXISTENCE FOR E-UTRA ................... 172
5.1 E-UTRA WITH E-UTRA ............................................................. 172
5.2 E-UTRA BAND 7 WITH GSM 1800 ............................................ 172
5.3 E-UTRA BAND 7 WITH UTRA BAND I ...................................... 172
5.4 E-UTRA BAND 13 WITH CDMA 2000 BAND 0 .......................... 173
5.5 COLOCATION SOLUTIONS ...................................................... 173
5.5.1 COLOCATION WITH SEPARATE ANTENNA SYSTEMS ....... 173
5.5.2 COLOCATION WITH DUAL DIPLEXER AND SHARED

MAST FEEDER .................................................................................. 174
5.5.3 COLOCATION WITH SHARED ANTENNA ............................. 175
5.6 NEAR-FAR PROBLEM .............................................................. 176
6 LTE CELL PLANNING AND HARDWARE .................................... 177
1 TEMS CELLPLANNER LTE MODULE .......................................... 178
1.1 DOWNLINK SINR FOR A GIVEN LOAD .................................... 179
1.2 DOWNLINK RB DATA RATE FOR A GIVEN LOAD ................... 179
1.3 DOWNLINK DATA RATE FOR A GIVEN LOAD......................... 180
1.4 UPLINK MAXIMUM SINR FOR A MONTE-CARLO LOAD ......... 181
1.5 UPLINK RB DATA RATE FOR A MONTE-CARLO LOAD .......... 182
1.6 UPLINK DATA RATE FOR A MONTE-CARLO SIMULATED

LOAD ................................................................................................. 183
1.7 LTE NEIGHBOUR ANALYSIS.................................................... 184

2 RBS 6000 FAMILY ........................................................................ 187
2.1 RBS 6000 HARDWARE ARCHITECTURE ................................ 188
2.1.1 RADIO UNIT FOR LTE (RUL) ................................................. 190
2.1.2 DIGITAL UNIT FOR LTE (DUL) .............................................. 190
7 ABBREVIATIONS .......................................................................... 193
8 INDEX ............................................................................................ 205
9 TABLE OF FIGURES ..................................................................... 213

LTE Introduction
1 LTE Introduction
Objectives
After this chapter the participants will be able to:

1. Explain the reasons behind the 3GPP Long Term Evolution
(LTE) strategy for UMTS.
2. Explain the general dimensioning principles
Figure 1-1 Objectives of Chapter 1

1 Introduction
This chapter introduces the Long Term Evolution (LTE) and System Architecture
Evolution (SAE) for third generation cellular networks as specified by the Third
Generation Partnership Project (3GPP) in Release 8 specifications.
The 3GPP is a collaboration agreement that was established in December 1998.

The collaboration agreement brings together a number of telecommunications
standards bodies, e.g. ARIB, CCSA, ETSI, TTA and TTC.
The original scope of 3GPP was to produce globally applicable Technical

Specifications and Technical Reports for a 3rd Generation Mobile System based
on evolved GSM core networks and the radio access technologies that they
support (i.e., Universal Terrestrial Radio Access (UTRA) both Frequency
Division Duplex (FDD) and Time Division Duplex (TDD) modes). The scope
was subsequently amended to include the maintenance and development of the
Global System for Mobile communication (GSM) Technical Specifications and
Technical Reports including evolved radio access technologies (e.g. General
Packet Radio Service (GPRS) and Enhanced Data rates for GSM Evolution
(EDGE)). See www.3gpp.org for further information.
The first practically implemented 3GPP specification for WCDMA was released
and frozen 1999 and is called Release 99.
WCDMA Release 99 supports both circuit switched (CS) and packet switched
(PS) traffic up to a theoretical rate 2 Mbps.
The evolution of 3G called HSDPA (High Speed Downlink Packet Access,

specified in Release 5 - 2002) and HSUPA (High Speed Uplink Packet Access,
specified in Release 6 – 2004) increase the maximum downlink (DL) bit rate to
14 Mbps and the uplink (UL) rate to maximum 5.76 Mbps. HSDPA and HSUPA
is referred to as HSPA (High Speed Packet Access). HSUPA is also called EUL
(Enhanced Uplink).
The next step for WCDMA, called HSPA evolution or HSPA+, is currently
ongoing (specified in Release 7 and 8) and aims to increase the maximum bit
rates even further (up to 42 Mbps in DL). This is accomplished using e.g. MIMO
(Multiple Input Multiple Output) antenna solutions and Higher Order Modulation
(HOM).
In September 2007 the 3GPP family was extended with yet another member, the
Evolved UTRAN (eUTRAN). The work with creating the concept was officially
started in the summer of 2006 when the study phase was successfully completed
and the 3GPP work item “3G Long Term Evolution – Evolved Packet System
RAN” (LTE) commenced. More than 50 companies and research institutes are
participating in the largest joint standardization effort ever to specify the new
world wide radio access and the evolved core network technology.
The 3G evolution and some typical peak user data rates are illustrated in Figure
1-2 below.
- 10 - © Ericsson AB 2013 LZT1380915 R2A

LTE Introduction Top right
Slide title
40 pt 3G Evolution corner for
field-mark,
customer or
Peak rate
Slide subtitle UL: ≈75 Mbps partner logotypes.
24 pt DL: ≈300 Mbps See Best practice
for example.
Text
24 pt
Bullets level 2-5
LTE
20 pt
4G
R99 R4 R5 R6 R7 R8 LTE
Advanced
WCDMA HSDPA HSUPA HSPA+
Peak rate Peak rate Peak rate Peak rate

UL: 64 kbps UL: 384 kbps UL: ≈5 Mbps UL: ≈5 Mbps
DL:384 kbps DL: ≈14 Mbps DL: ≈14 Mbps DL: ≈42 Mbps
Figure 1-2 3G Evolution

© Ericsson AB 2008 01_03813 LZU 108 7263 Uen
. Rev A Figure 1 - 2 LTE Introduction
The standard development in 3GPP is grouped into two work items, where LTE
targets the radio network evolution and System Architecture Evolution (SAE)
targets the evolution of the packet core network. Common to both LTE and SAE
is that only a packet switched will be specified. The result of these work items are
the Evolved UTRAN (eUTRAN) and the Evolved Packet Core (EPC). These
together (eUTRAN+EPC) builds the Evolved Packet System (EPS).
LTE/SAE is specified from Release 8.
Note that LTE and SAE refer to the work items in 3GPP. The name of the actual
Radio Access Network (RAN) is eUTRAN and the name of the Core Network
(CN) is Enhanced Packet Core (EPC).
The eUTRAN supports use of different MIMO (Multiple Input Multiple Output)
multiple antenna configurations. This increases the data rates and spectrum
efficiency.
LTE is sometimes referred to as 3.9G. Why not 4G? Well, ITU has defined IMT
Advanced, which is the follower to IMT2000. IMT Advanced is regarded as 4G
and is meant to support theoretical bitrates up to approximately 1Gbit/s and may
be deployed with LTE Advanced as a foundation.
EPS in Release 8 is based on a simplified network architecture compared to

Release 6. The number of user-plane nodes is reduced from four in Release 6
(NodeB, RNC, SGSN and GGSN) to only three; enhanced Node B, Serving and
Packet data Gateways (eNodeB, S-GW and P-GW) as illustrated in Figure 1-3
below.
LZT1380915 R2A © Ericsson AB 2013 - 11 -

Top right
Slide title
40 pt Simplified Network Architecture LTE L13 Radio Network Design corner for
field-mark,
customer or
Slide subtitle partner logotyp
24 pt See Best practi
WCDMA LTE/SAE for example.
Text
24 pt GGSN
Bullets level 2-5 SAE CN (EPC)
20 pt CN
P/S-GW
SGSN
A flat architecture
for optimized
performance and Moving RNC
cost efficiency functions to
E-NodeB
RNC RNC
NodeB NodeB eNodeB eNodeB
Less nodes
UE UE => lower latency
Figure 1-3 Simplified Network

Figure 1Architecture
.-3 Rev A LTE Introduction
In the non-roaming case the S-GW and P-GW functionalities are both located
within one operators network and can be implemented in a combined S and P-
GW node.
Only a PS domain is defined in LTE. This means that the traditionally CS

services will be carried by PS bearers.

LTE Introduction
2 Dimensioning principles
The process for calculating LTE coverage and capacity can be made in an
arbitrary way, but adapted to the dimensioning project input demands and the
expected output. The process begins with defining quality requirements
expressed as uplink and downlink bit rates provided with a certain probability
and cell capacity.
The general dimensioning process for LTE is shown in Figure 1-4.
- eNodeB power
- Tx Diversity
1 - MIMO
Quality Requirements - UE Power
- UE Rx Diversity
2
UL Dimensioning
- Cell range
- UL cell edge bit rate
Input 3
- UL cell Capacity
requirements DL Dimensioning
not met
4 - Downlink cell edge bit rate
Control Channel - DL cell capacity
Coverage
Done
Figure 1-4 LTE Dimensioning Process.
1. Define the Quality Requirement

The quality requirement related to coverage is based on a throughput requirement
at a given coverage probability (e.g. 100 kbps must be reached with 98%
probability).
The quality requirement related to capacity is that the radio network must be
capable of handling a certain amount of offered traffic (e.g. on average an offered
traffic of 5 Mbps per cell or 10 Mbps per square kilometer).
The prerequisites must be determined as well.
The following attributes need to be set:

 Transmit type – MIMO or TX diversity
 Receive diversity in the user equipment and base station
 RBS power class, for example, 20 W or 40 W
 User equipment output power
 Bandwidth

 Frequency band
2. Uplink Dimensioning
By gradually increasing the site-to-site distance the maximum site-to-site distance

supporting the quality requirements is found.
If the site-to-site distance is given and the quality requirements are not met, the
quality requirements must be relaxed or the prerequisites modified.
3. Downlink Dimensioning
Based on the site-to-site distance obtained in the uplink dimensioning process,

the downlink coverage and cell capacity is calculated. If the downlink quality
requirements are met, the site-to-site distance calculated in the uplink is the final
result (uplink limited system). If the downlink requirements are not met, the site-
to-site distance must be reduced until the DL requirements are met, providing the
final result.
4. Control Channel Coverage
The control channel performance at cell edge should be verified against a quality
requirement with the calculated coverage as input. This is to guarantee that
control channel performance is not limiting cell edge performance. If the control
channel performance does not fulfill the quality requirement, the definition of cell
edge quality or some prerequisites for the calculation may need to be reiterated.

LTE Air Interface
2 LTE Air Interface
Objectives

1. Perform calculations on the radio interface capacity
2. Explain how the LTE downlink and uplink data rates are
achieved and calculated.
3. List the LTE UE category capabilities.
4. Explain radio wave propagation and typical channel models

3 Introduction
The radio interface in LTE is developed according to the requirements of
spectrum flexibility, spectrum efficiency, cost effectiveness etc. Robustness
against time dispersion has influenced the choice of transmission technique in
both UL and DL.
The 3GPP has chosen Orthogonal Frequency Division Multiplex (OFDM) as the
air interface for downlink (eNodeB to UE) and Single Carrier Frequency Division
Multiple Access (SC-FDMA) for the uplink (UE to eNodeB) as illustrated in
Figure 2-2 below. Both of these access techniques support a variable bandwidth
and hence enable operators to deploy LTE in different regions with different Top right
Slide title
40 pt LTE Air Interface Introduction
frequency bands and bandwidths available. corner for
field-mark,
customer or
Slide subtitle UE #1 Δf=15 kHz UE #2 OFDM partner logotypes.
24 pt See Best practice
for example.
UE #3
Text 1m
24 pt tim s
e
Bullets level 2-5
20 pt frequency 180 kHz
Users given variable number of 15 kHz subcarriers
in blocks of 12 (12X15 = 180 kHz) every 1 msec
k
Uplin
o w nlink
D
SC-FDMA
tim
e
LTE UEs frequency eNodeB
Each UE uses a separate variable bandwith carrier

. Rev A Figure 2 - 3 LTE Air Interface
Figure 2-2 LTE Air Interface Introduction
With OFDM each user is given a variable number of 15 kHz subcarriers in blocks
or 12 (12∙15 = 180 kHz) every 1 msec. This allows the operator to deploy LTE
with variable size bandwidth allocations. Each 15 kHz subcarrier has a slow
symbol rate resulting in a long symbol time giving a very good performance in
highly time dispersive radio environments (i.e. many delayed and strong
multipath reflections). The long symbol time also reduces Inter Symbol
Interference (ISI).
One drawback of OFDM is its high Peak to Average Power Ratio (PAPR)
resulting in relatively high power consumption and amplifier cost making it
impractical for use in the uplink given the power consumption and cost
constraints associated with User Equipment (UE) design. With SC-FDMA each
UE uses a separate variable bandwidth carrier which although not as flexible as
OFDM produces a much lower PARP.

LTE Air Interface
Although Frequency Division Duplex (FDD) and Time Division Duplex (TDD)
are specified by the 3GPP only the FDD mode will be covered in this chapter.
As can be seen in Figure 2-2 the radio resources are divided in the time and
frequency domain. The smallest allocation is twelve 15 kHz subcarriers for 1
msec known as a Scheduling Block (SB). These SBs are dynamically allocated
by the eNodeB with variable modulation schemes and coding rates depending on
the received Channel Quality Indicators (CQI) from connected UEs.
Hybrid Automatic Repeat and reQuest (HARQ) caters for very quick layer 2
retransmission functionality. In addition, ordinary ARQ is implemented in the
RLC layer.
The LTE radio transmissions are based on a very short Transmission Time
Interval (TTI) of 1ms, which speeds up the operation of all of the above functions
and also reduces the radio interface latency, which is one of the main concerns in
the LTE development.
The type of modulation used in LTE depends on the radio environment. The UE
estimates the quality in the downlink and signals it back to the eNodeB in the
Channel Quality Indicator (CQI). The uplink reference signals that are embedded
into the uplink transmission are used by the eNodeB to estimate the quality in the
uplink. The eNodeB decides which modulation technique should be used based
on the quality of the downlink and uplink radio environment. LTE supports the
following modulation techniques in the downlink and uplink:
 64 Quadrature Amplitude Modulation (64 QAM)

which uses 64 different quadrature and amplitude combinations
to carry 6 bits per symbol
 16 Quadrature Amplitude Modulation (16 QAM)
which uses 16 different quadrature and amplitude combinations
to carry 4 bits per symbol
 Quadrature Phase Shift Keying (QPSK) which used 4 different
quadratures to send 2 bits per symbol.

4 LTE Downlink Physical Resources

The basic LTE downlink physical resource can be seen as a time-frequency grid
as illustrated in Figure 2-3 below, where each resource element corresponds to
one OFDM subcarrier during one OFDM symbol interval. A Resource Block
corresponds to twelve OFDM sub-carriers during one 0.5 ms slot.
Resource Block
(12 subcarriers)
f = 15 kHz
frequency
tim
e
On Modulation symbol
es
lot ( 66.7 s)
(0.
On 5 ms
es e
ub c)
fra
me
(1
ms
ec
)
1 Antenna Port: 12 X 14 = 168 modulation symbols every ms

2 Antenna Ports: (12 X 14) X 2 = 336 modulation symbols every ms
Figure 2-3 LTE Downlink Physical Resources
The LTE symbol length is 1/15000 = 66.7 s. Each symbol is followed by a 4.7
s ‘Cyclic Prefix’ (CP) which is copy of the last part of the symbol used to
preserve the subcarrier orthogonality and improve its robustness in time-
dispersive channels. This means that each subcarrier can carry 1/(0.0667 +
0.0047) = 14 modulation symbols during one TTI. The 12 subcarriers that make
up a RB can thus carry 12 ∙ 14 = 168 modulation symbols with 1 Antenna Port or
(12 ∙ 14) ∙ 2 = 336 with 2 Antenna Ports as illustrated in Figure 2-3 above.
One resource element carries one modulation symbol and these resource elements
are used to carry downlink physical channels and reference signals.
The number of RBs (nRB) depends on the Channel Bandwidth (BWChannel) as

illustrated in Figure 2-4 below.

LTE Air Interface
Channel Bandwidth [MHz]
Transmission Bandwidth Configuration [RB]
Transmission
Bandwidth [RB]
Channel edge
Channel edge
Resource block DC carrier (downlink only)
Active Resource Blocks
Channel B andwidth BW Channel [MHz] 1.4 3 5 10 15 20
Number of Resource Blocks ( nRB) 6 15 25 50 75 100
Figure 2-4 Number of Resource Blocks (nRB)
The LTE Air Interface supports channel bandwidths from 1.4 up to 20 MHz. The
Direct Current (DC) carrier in the centre of the bandwidth along with a number at
the channel edge are not used leaving the number of active RBs ranging from 6 to
100 as illustrated in Figure 2-4 above. All defined bandwidths can be used for
FDD as well as TDD.
The active resource elements are used to carry the following traffic types:
 Downlink Reference Signals

 Downlink L1/L12 Control signaling
 Synchronization Signals (SS)
 Broadcast Control Channel (BCH)
 User plane data

4.1 Downlink Reference Signals

Eight resource elements per RB are used to carry the cell specific reference signal
used by the UE to identify the cell and perform channel estimation. To allow the
UE to distinguish between the antenna ports these reference signals are staggered
in time with transmission suspended alternatively on each antenna port when the
other is transmitting. This means that a total of 16 resource elements are required
to carry the DL Reference Signals per scheduling block as illustrated in Figure
2-5 below.
No data sent (a hole) when Antenna

Port # 1 is transmitting reference
signals
No data sent (a hole) when Antenna

Port # 0 is transmitting reference
signals
Antenna
Port #0
Antenna
8 Modulation Symbols per antenna port
Port #1
used to carry DL reference signals
Figure 2-5 Downlink Reference Signals
When the DL Reference Signals and the corresponding holes are taken into
account the number of resource elements available for user data per SB (1 ms)
drops to:
 1 Antenna Port: 168 – 8 = 160
 2 Antenna Ports: 2∙(168 – 16) = 304
Note: 1 antenna port corresponds to SISO (Single Input Single
Output) and 2 antenna ports corresponds to e.g. 2x2 MIMO
(Multiple Input Multiple Output) or Tx Diversity.

LTE Air Interface
4.2 Downlink L1/L2 Control signaling

A minimum of one OFDM symbol per subframe is reserved for downlink L1/L2
control signaling from PCFICH, PDCCH and, PHICH. The L1/L2 control
signaling includes downlink scheduling assignments required by the UE to
properly receive, demodulate and decode PDSCH, uplink scheduling grants
informing UE about resources and transport formats for its uplink transmission
and HARQ acknowledgements in response to the UEs uplink transmissions.
The number of OFDM symbols needed to carry the downlink control signaling
depends on the number of UEs being scheduled in the cell and can range from 1
to 4 (4 is only used for 1.4 MHz system BW). Figure 2-6 below illustrates the
case where only one OFDM symbol is used to carry Downlink L1/L2 Control
signaling.
Downlink Reference Symbols, Antenna # 0

Downlink Reference Symbols, Antenna # 1
L1/L2 Control Signalling
(PCFICH, PDCCH and PHICH)
1-4 OFDM symbols
used to carry
Antenna
Port #0
1-4 OFDM symbols

used to carry
Antenna
8-46 Modulation Symbols per antenna port
Port #1
used to carry L1/L2 Control Signalling
Figure 2-6 Downlink L1/L2 Control Signalling
Since no data can be transmitted when the downlink reference signals are being
transmitted, in this example 8 OFDM symbols per antenna port are used to carry
L1/L2 control signals as illustrated in Figure 2-6 above.
When the DL Reference Symbols and least amount of L1/L2 control signaling
are taken into account the number of resource elements available for user data per
SB drops to:
 1 Antenna Port: 168 – 16 – 8 = 144 (2 antenna ports are taken
into account for the first OFDM symbol)
 2 Antenna Ports: 2∙(168 – 16 – 8) = 288

The location of the control signaling at the beginning of the subframe is

advantageous as it allows the terminal to decode the downlink scheduling
assignment prior to the end of the subframe. Processing of the DL-SCH can
therefore begin earlier compared to the case of the control signaling spanning the
full subframe duration. This minimizes the delay in the DL-SCH decoding and
thus the overall downlink transmission delay.
Furthermore, by transmitting the L1/L2 control channel at the beginning of the

sub-frame, i.e. by allowing for early decoding of the L1/L2 control information,
mobile terminals that are not scheduled may turn off their receiver circuitry for a
large part of the subframe, with reduced terminal power consumption as a
consequence.
The downlink L1/L2 control signaling consists of three different physical channel
types:
 Physical Control Format Indicator Channel (PCFICH),

informing the terminal about the number of OFDM symbols
(1-4) used for L1/l2 control signaling in the current subframe.
There is only one PCFICH in a cell.
 Physical Downlink Control Channel (PDCCH), used to carry
downlink scheduling assignments and uplink scheduling grants.
In addition, it is also used for power control of UL transmitters.
 Physical Hybrid-ARQ Indicator Channel (PHICH), used to
transmit ACK/NAK in response to reception of UL-SCH
transmissions. Typically, there are multiple PHICH in a cell.
4.3 Synchronization Signals (SS)

Cell search is the process of identifying and obtaining downlink synchronization
to cells, so that the broadcast information from the cell can be detected. This
procedure is used both at initial access and at handover.
In order to simplify initial cell search – where the UE has no a-priori information
about the spectrum allocation of the cell – the Synchronization Signal (SS)
always occupies only 63 (62 + DC carrier which is not used) subcarriers in the
center of the available spectrum. The UE therefore always processes only these
63 sub-carriers, independent of the spectrum allocations.
One Synchronization Signal is comprised of a primary SS (P-SS) sent during

symbols #5 and a secondary SS (S-SS) sent during symbols #6 in the RB as
illustrated below.

LTE Air Interface
Downlink Reference Symbols Antenna # 0

Downlink Reference Symbols Antenna # 1
S-SS
NOTE: Synchronization P-SS
Signals only sent on the
62 centre subcarriers in
subframe 0 and 5
Antenna
Port #0
10 msec radio frame
0 1 2 3 4 5 6 7 8 9 Antenna
Port #1
1 msec subframe
Figure 2-7: Synchronization Signals
It should be noted that the synchronization signals are only sent on the 62 centre
(DC +/- 31) subcarriers and only during subframe 0 and 5 of each 10 ms Radio
Frame as illustrated above. However, the SS occupies 72 subcarriers in total. The
10 remaining subcarriers are not used.
The P-SS uses 124 resource elements per antenna port per frame. The S-SS uses
124 resource elements per antenna port per frame.
Note: The amount of resource elements needed per antenna port for the SS are
always the same, i.e. independent of the used bandwidth.
4.4 Broadcast Channel

The Broadcast Channel (BCH) is the transport channel used to carry system
information to idle UEs in the cell. This system information is divided up into
statically scheduled parts MIB and SIB1. The Master Information Block (MIB)
contains SFN and system bandwidth. SIB1 carries for example the PLMN ID.
The remaining System Information Blocks (SIBs) carries dynamic system
information.
PBCH carries parts of the BCH. The PBCH is only sent on the 72 centre (DC +/-
36) subcarriers and uses the first four OFDMA symbols of the second slot in the
first subframe of each 10 ms radio frame as illustrated below. However, PBCH
sometimes collides with the Reference Signals and they have a higher priority
than the PBCH. Therefore, the system always allocates resource elements to the
PBCH as if four antenna ports were used to avoid collisions. This implies that
there will be an extra amount of holes where the PBCH is transmitted.

Downlink Reference Signals Antenna # 0

Downlink Reference Signals Antenna # 1
S-SS
NOTE: BCH only sent on P-SS
the 72 centre subcarriers BCH
in subframe 0
Antenna
Port #0
10 msec radio frame
0 1 2 3 4 5 6 7 8 9 Antenna
Port #1
1 msec subframe
Figure 2-8: Broadcast Channel
As illustrated above, in subframe 0, there are 40 resource elements used per

resource block (only the 6 centre resource blocks in subframe 0) to carry the
PBCH.
4.5 Downlink User Plane Data

The amount of user plane data carried by a SB will depend on the amount of
resource elements left after the reference signals, L1/L2 control signaling, SS and
BCH, the number of antenna ports used and, the modulation and puncturing used.
The highest user plane data rate is achieved when the SB is not carrying SCH or
BCH and the least amount of L1/L2 control signaling as illustrated in Figure 2-9
below.

LTE Air Interface
Downlink Reference Signals, Antenna Port # 0

1 Antenna Port
150 Modulation Symbols
QPSK = 150 X 2 = 300 bits
16 QAM = 150 X 4 = 600 bits
64 QAM = 150 X 6 = 900 bits User Plane
Antenna
Port #0
2 Antenna Ports
2∙144 Modulation Symbols
QPSK = 288 X 2 = 576 bits
16 QAM = 288 X 4 = 1152 bits
64 QAM = 288 X 6 = 1728 bits
Antenna
Port #1
Figure 2-9 DL RB (High PDSCH Data Rate)
When 1 Antenna Port is used the SB has 150 resource elements available for user
plane data. This would carry 300, 600 or 900 bits using QPSK, 16 QAM and 64
QAM respectively.
When 2 Antenna Ports are used the SB has 288 resource elements available for
user plane data. This would carry 576, 1152 or 1728 bits using QPSK, 16 QAM
and 64 QAM respectively.
The maximum number of bits on the PDSCH in one SB is 1728 bits as illustrated
in Figure 2-9 above. This is achieved by transmitting different data on 2 Antenna
Ports.
The lowest user plane data rate is achieved when the RB is SS and BCH with the
most amount of L1/L2 control signaling as illustrated below.


1 Antenna Port P-SS
44 Modulation Symbols
S-SS
QPSK = 44 X 2 = 88 bits
BCH
16 QAM = 44 X 4 = 176 bits
64 QAM = 44 X 6 = 264 bits User Plane
Antenna
Port #0
2 Antenna Ports
2∙40 Modulation Symbols
QPSK = 80 X 2 = 160 bits
16 QAM = 80 X 4 = 320 bits
64 QAM = 80 X 6 = 480 bits
Antenna
Port #1
Figure 2-10: DL RB (Low PDSCH Data Rate)
When 1 Antenna Port is used the RB has 44 resource elements available for user
plane data. This would carry 88, 176 or 264 bits using QPSK, 16 QAM and 64
QAM modulation respectively.
When 2 Antenna Ports are used the RB has 80 resource elements available for
user plane data. This would carry 160, 320 or 480 bits using QPSK, 16 QAM
and 64 QAM modulation respectively.
The minimum number of bits on the PDSCH in one SB is 88 bits as illustrated in

Figure 2-9 above. This is achieved by transmitting on 1 Antenna Port.
Remember that the actual PDSCH rate is a mix of a lot of different SBs with
different amount of L1/L2 signaling. Furthermore, since the number of SBs
allocated to a UE along with the modulation scheme and puncturing is constantly
varying it is very difficult to calculate an instantaneous PDSCH data rate.

LTE Air Interface
Link adaptation
The RBS adapts the coding rate to suit the radio environment. For example in
poor radio environments a low coding rate which contains more parity than
systematic bits and offers a high protection against bit errors would be used. On
the other hand when the radio environment is high a coding rate which contains
more systematic than parity bits could be used offering lower protection but
higher user data rate as illustrated in Figure 2-11.
Systematic Bit
Parity Bit
Poor Radio Environment Good
Low data rate/ high data rate/ RBS

high protection low protection
Coding rates 33 to 95 %
Figure 2-11 Adaptive Coding
The RBS will adapt the modulation and coding rate to offer the UE the best
possible data rate in various radio environments while maintaining an adequate
Bit Error Rate (BER). Coding rates between 33 and 95 % are possible.
In Tx diversity the same data is sent from both antenna ports increasing the
robustness of the signal. In good radio environments when robustness is not an
issue the RBS can send different data from each antenna port effectively doubling
the data rate. In the illustration in Figure 2-12 the UE in the poor radio
environment is sent the same data from each antenna port represented by the
duplicated numbered squares.

User data bits
Poor Radio Environment Good
AP 0 1 2 3 4 5 6 7 8 AP 0 1 2 3 4 5 6 7 8
AP 1 1 2 3 4 5 6 7 8 AP 1 9 10 11 12 13 14 15 16 RBS
Low data rate/ High data rate/
TX Diversity No TX Diversity
Figure 2-12 Tx Diversity vs 2x2 MIMO.
The UE in the good radio environment on the other hand, is send different data
from each antenna port represented by the 16 numbered squares. From this
illustration it can bee seen that in a good radio environment the RBS can sacrifice
TX diversity for an increased user data rate. The UE can distinguish each
antenna transmission by the embedded cell reference signals which are sent at
different times from each antenna.

LTE Air Interface
4.6 Downlink User Data Rates

The payload carried in one subframe of a downlink RB will vary depending on
the coding and modulation scheme. Some mapping examples for each
modulation scheme and the corresponding data rate at the MAC Layer are
Top right
Slide title
40 pt Downlink Channel mapping Examples corner for
field-mark,
customer or
Slide subtitle partner logotypes.
Data from MAC Layer
24 pt TX TX TX 2X2 See Best practice
TX Diversity or 2X2 MIMO for example.
Diversity Diversity Diversity MIMO
Text Type of Modulation QPSK 16 QAM 64 QAM 64 QAM
24 pt CRC Generator
Bullets level 2-5 Rate at MAC Layer [ kbps] 96 432 800 1600
20 pt
Payload bits 96 432 800 1600
CRC Size (bits) 24 24 24 24
Turbo Coder
Input to Tur bo Coder 120 456 824 1624
Systematic Bits (Input + 4) 124 460 828 1628
Systematic Parity
Parity #1 Bits (Input + 4) 124 460 828 1628
Parity #2 Bits (Input + 4) 124 460 828 1628
Puncturing Punctured Parity #1 Bits 82 58 18 50
Punctured Parity #2 Bits 82 58 18 50
Systematic Parity
Physical layer b its 288 576 864 1728
Coding Rate [%] 33 75 93 93
Physical layer bits

Figure 2-13 Downlink. Channel Rev A Figure 2 - 18 LTE Air Interface
mapping Examples
As illustrated in Figure 2-13 above a downlink data rate of 1600 kbps can be
achieved at the MAC layer using 64 QAM, 2X2 MIMO and a coding rate of
93%. This rate would only be possible when the RB is not carrying SCH or BCH
and the UE is in a very good radio environment.
The UE evaluates the radio environment by measuring the Signal to Interference

and Noise Ratio (SINR) of the cell specific reference signals and sends it back to
the eNodeB in the Channel Quality Indicator. Simulations for a range of RBs and
SINR values have been used to produce practical RBs rates that can be used for
radio network dimensioning.

To check if the data has been received correctly the transmitter adds a 24-bit
CRC to each block of user data before it is passed through a Turbo Coder. The
Turbo Coder adds extra ‘parity bits’ to enable the receiver to recover bit errors
introduced by the air interface. The more parity bits sent the greater the
protection against bit errors but at the expense of the user data rate. Based on the
quality of the radio environment the eNodeB these parity bits can be punctured or
removed reducing the protection but increasing the user data rate.
If the CRC is decoded correctly an ‘ACKnowledgement’ (ACK) message will be

sent to the transmitter or a ‘Negative ACKnowledgement’ (NACK) in the case
that it is not. On reception of the NACK the transmitter will perform a
retransmission using either ‘Chase Combining’ or ‘Incremental Redundancy
(IR)’. When Chase Combining is used the same data is sent resulting in a power
gain. In the IR retransmission the parity bits that were punctured in the initial
transmission are sent allowing the receiver to use the full strength of the Turbo
Coding to correct the error.

LTE Air Interface
An example of coding and puncturing for a payload block of 432 bits is

illustrated in Figure 2-14 below. Top right
Slide title
40 pt Coding and Puncturing corner for
field-mark,
customer or
Slide subtitle Payload partner logotypes.
Size (bits) 456 TURBO 1380 for example.
CRC Coder
Text 432 Generator 432 24 (data x 3) 460 460 460
24 pt (+24 bits) +
Bullets level 2-5 (4 tail bits) Systematic bits Parity bits
20 pt
Since 576 bits were sent on the air interface to represent

576
432 payload bits the coding rate is 432/576 = 75 %
Initial Transmission => systematic bits and

460 58 58
punctured parity bits
NACK
Retransmission with Chase Combining:

Same as initial transmission => power gain
460 58 58
Retransmission with Incremental Redundancy: 288 288

Punctured parity bits => coding gain
Figure 2-14 Coding and

.
Puncturing
Rev A Figure 2 - 6 LTE Air Interface
A 24-bit CRC is added to the 432 bits of payload data producing a block of 456
bits that is passed to the Turbo Coder. The Turbo Coder adds 4 tail bits to this
block producing what is known as the ‘systematic bits’, in this case 460 bits .
The Turbo Coder also outputs two parity bits for each input bit along with 4 tail
bits for each block of parity bits. The total output is 456 + 4 + 456 + 4 + 456 + 4
= 1380 bits.
In this example the 576 bits sent to the modulator for the initial transmission is
made up of 460 systematic bits and two blocks of parity bits punctured down to
58. Since 576 bits were sent on the air interface to represent 432 payload bits the
coding rate is 432/576 = 0.75 or 75%.
In this example we assume that this transmission was not correctly decoded and a
NACK message was received implying that the receiver is requesting a
retransmission. If Chase Combining is used this retransmission will contain the
same data as the initial transmission producing a power gain. In the case of
Incremental Redundancy (IR) the retransmission contains only parity bits which
are combined with the initial transmission to get the full benefit of Turbo Coding.
The benefits of each type of redundancy will depend on the amount of puncturing
in the initial transmission. IR would be preferable over Chase Combining when
the initial transmission was heavily punctured. The redundancy version that is
carried in the Hybrid Automatic Retransmission Request (HARQ) information
lets the receiver know if chase combining or incremental redundancy should be
used.

The user data rates measured at the higher layer will be slightly lower due to the
extra overhead introduced by the various protocols illustrated in Figure 2-15 Top right
Slide title
40 pt
below.
Downlink Data Flow corner for
field-mark,
customer or
24 pt Higher Layer PDU Higher Layer PDU Higher Layer PDU See Best practice
Radio Bearer 1 Radio Bearer 1 Radio Bearer 2
for example.
Text header Higher Layer Payload header Higher Layer Payload header Higher Layer Payload
24 pt
Bullets level 2-5 PDCP
20 pt (Header Compression H H H
& Ciphering)
PDCP PDCP PDCP

PDCP SDU PDCP SDU PDCP SDU
header header header
RLC
(segmentation & RLC SDU RLC SDU RLC SDU
concatenation)
RLC RLC RLC

header header header
RLC PDU RLC PDU RLC PDU
MAC MAC MAC

MAC SDU MAC SDU
(multiplexing) header header
MAC PDU MAC PDU
PHY Transport Block CRC Transport Block CRC
Figure
© Ericsson AB2-15 Downlink
2008 02_03813 . Data
LZU 108 7263 Uen Rev A Flow
Figure 2 - 20 LTE Air Interface

LTE Air Interface
5 LTE Uplink Physical Resources

The LTE uplink air interface uses the same 15 kHz orthogonal subcarriers
grouped in blocks of 12 to produce Resource Blocks (RBs). There are no unused
Direct Centre (DC) subcarriers in the uplink however a number of RBs at the
edge of the uplink channel bandwidth are reserved for PUCCH signaling from
UEs that have not been scheduled. Each UE can be assigned 1 or any number of
RBs provided it is a factor of 2, 3 or 5 from the remaining RBs. For example a
UE could be dynamically assigned 6, 8 or 9 RBs as illustrated in Figure 2-16
below but not 7.
Uplink Channel Bandwidth

6 RBs
RBs reserved for PUCCH
from unscheduled UEs
8 RBs
9 RBs
Number of RBs allocated to each

UE can be 1 or a factor of 2, 3 or 5.
UEs eNodeB
Figure 2-16 LTE Uplink Resource Blocks
In contrast to the downlink, uplink resource blocks assigned to a UE must always

be consecutive in the frequency domain, as illustrated in Figure 2-16 above. This
is necessary in order to keep the ‘single-carrier’ property of the uplink
transmission. Note that, similar to the downlink, the uplink resource block is
defined as twelve subcarriers during one 0.5 ms slot. At the same time, uplink
scheduling is carried out on a sub-frame (1 ms) basis. Thus, similar to the
downlink, the uplink resource assignment is carried out in terms of pairs of
resource blocks, where each pair consists of two resource blocks in consecutive
slots, i.e. scheduling block.
The number of RBs reserved for signaling from unscheduled UEs (PUCCH)
varies depending on parameter settings and system bandwidth as illustrated in
Figure 2-16 above. For details, see control channel dimensioning in chapter 4.

The same 1 ms subframe containing two slots is used for LTE in the uplink. The
number of resource elements per slot will depend on the number of RBs assigned
to the UE. Since each slot carries one resource element and there are 12
subcarriers in each RB there is a total of 12 ∙ 7 = 84 resource elements per slot or
84 ∙ 2 = 168 per subframe as illustrated in Figure 2-17.
Resource Block
(12 subcarriers)
f = 15 kHz
frequency
tim
e
On UL Reference Signals
es
lot
(0 User Plane
On .5 ms
es e
ub c)
fra
me
(1
ms
ec
)
12 X 14 = 168 Modulation Symbols
12 X 2 = 24 Reference Signals
 144 User Plane symbols
QPSK = 144 X 2 = 288 bits
16 QAM = 144 X 4 = 676 bits
64 QAM = 144 X 6 = 864 bits
Figure 2-17 LTE Uplink Physical Resources
The UL Reference Signals illustrated in Figure 2-17 are used for channel
estimation and are transmitted in the fourth symbol each uplink slot. Uplink
frequency hopping is normally applied, whereby the two slots illustrated in
Figure 2-17 above are transmitted on different, perhaps substantially separated,
frequencies.
When a UE has been given an uplink scheduling grant, that is has been assigned
UL-SCH resources in the current subframe the PUCCH is time multiplexed with
the user data. Unlike the downlink there is no minimum number of resource
elements reserved for the PDCCH making it possible for all resource elements
except those reserved for UL reference signals to be used for user data. This
means that 168 – 24 = 144 resource elements per RB can be used to carry user
data as illustrated in Figure 2-17 above.
Similar coding, puncturing and modulation schemes are used in the uplink but
there is, according to 3GPP Release 8, no option of transmitting on 2 antenna
ports, only 1 tx antenna port is supported in UL. This means one subframe can
carry 288, 676 or 864 bits using QPSK, 16 QAM and 64 QAM modulation
symbols respectively.
The uplink transport format is completely decided by the scheduler in the

eNodeB. Consequently, and in contrast to High Speed Downlink Packet Access
in WCDMA the uplink control signaling does not need to carry the transport
format.

LTE Air Interface
5.1 Uplink User Data Rates

The payload carried in one subframe of an uplink RB will vary depending on the
coding and modulation scheme. Some mapping examples for each modulation
scheme and the corresponding data rate at the MAC Layer are illustrated in
Top right
Figure 2-18 below.
Slide title
40 pt Uplink Channel mapping Examples corner for
field-mark,
customer or
Data from MAC Layer
Type of Modulation QPSK 16 QAM 64 QAM for example.
Text Rate at MAC Layer [kbps] 96 432 824

24 pt CRC Generator
Bullets level 2-5
20 pt
Payload bits 96 432 824
CRC Size (bits) 24 24 24
Turbo Coder Input to Turbo Coder 120 456 848

Systematic Bits (Input + 4) 124 460 852
Systematic Parity
Parity #1 Bits (Input + 4) 124 460 852
Parity #2 Bits (Input + 4) 124 460 852
Puncturing
Punctured Parity #1 Bits 82 58 6
Systematic Parity Punctured Parity #2 Bits 82 58 6
Physical layer bits 288 576 864
Physical layer bits Coding Rate [%] 33 75 95
Figure 2-18 Uplink Channel mapping Examples
As illustrated in Figure 2-18 above an uplink data rate of 824 kbps can be
achieved at the MAC layer using 64 QAM and a coding rate of 95%. This rate
would only be possible in a very good radio environment.
The eNodeB evaluates the radio environment by measuring the Signal to

Interference and Noise Ratio (SINR) of the UL reference signals and schedules
the UE accordingly.
The user data rates measured at the higher layer will be slightly lower due to the
extra overhead introduced by the MAC, RLC and PDCP protocols illustrated in
Figure 2-15.
Note that, in the general case, uplink frequency hopping may be applied,
implying that the two slots illustrated in Figure 2-17 are transmitted on different,
perhaps substantially separated, frequencies.

6 LTE UE Capabilities
The number of modulation schemes and MIMO layers supported by the LTE UE
will dictate its maximum uplink and downlink data rates. LTE UEs are divided Top right
Slide title
40 pt LTE UE Categories
up into five categories as illustrated in Figure 2-19 below. corner for
field-mark,
customer or
24 pt LTE UE Category 1 2 3 4 5 See Best practice
for example.
Text DL peak rate [Mbps] 10 50 100 150 300

24 pt
Bullets level 2-5
20 pt UL peak rate [Mbps] 5 25 50 50 75
Max DL Modulation 64 QAM
Max UL Modulation 16 QAM 64 QAM
MIMO No 2X2 4X4
Figure 2-19
© Ericsson AB 2008 LTE
02_03813 UE
LZU 108 Categories
7263 Uen
As the illustration in Figure 2-19 above suggests, LTE UEs will not be confined
to the traditional phone and data card format common in existing 3G networks.
Category 5 UE data rates are not fully supported in the early Ericsson LTE
releases as only 2X2 MIMO is supported.

LTE Air Interface
7 LTE Frequency Bands

The 3GPP have identified the 14 Frequency Division Duplex (FDD) bands listed
in Figure 2-20 below.
E - UTRA Uplink (UL) Downlink (DL)

Band
F UL_low – F UL_high F UL_low – F UL_high
1 1920 MHz – 1980 MHz 2110 MHz – 2170 MHz
2 1850 MHz – 1910 MHz 1930 MHz – 1990 MHz
3 1710 MHz – 1785 MHz 1805 MHz – 1880 MHz
4 1710 MHz – 1755 MHz 2110 MHz – 2155 MHz
5 824 MHz – 849 MHz 869 MHz – 894MHz
6 83 0 MHz – 840 MHz 87 5 MHz – 8 85 MHz
7 2500 MHz – 2570 MHz 2620 MHz – 2690 MHz
8 880 MHz – 915 MHz 925 MHz – 960 MHz

9 1749.9 MHz – 1784.9 MHz 1844.9 MHz – 1879.9 MHz
10 1710 MHz – 1770 MHz 2110 MHz – 2170 MHz
11 1427.9 MHz – 1452.9 MHz 1475.9 MHz – 1500.9 MHz
12 698 MHz – 716 MHz 728 MHz – 746 MHz
13 777 MHz – 787 MHz 746 MHz – 756 MHz
14 788 MHz – 798 MHz 758 MHz – 768 MHz
Figure 2-20 LTE FDD Frequency Bands
Ericsson LTE early releases will operate in E-UTRA band 1, 7 and 13 as

illustrated in Figure 2-20.

9 Radio Wave Propagation

The choice of frequency band to deploy LTE in may have a large impact on the
cell range, since the propagation loss depends on the used frequency. By using
the frequencies around 2600 MHz instead of 700 MHz results in propagation
losses of in the range of 11 to 18 dB. However, the lower frequency bands might
already be occupied and limiting the available bandwidth. Thereby the flexibility
and capacity might be less in the lower frequencies. Techniques such as antenna
gain are used to mitigate these losses.
9.1 Okumura-Hata model

The Okumura method is semi-empirical and based on extensive measurements
performed in the Tokyo area. The results of these measurements are a series of
curves, with field strength as a function of distance for different frequencies and
antenna heights.
The Okumura model was intended for non-computer use. Hata made an attempt
to derive semi-empirical formulas from the curves for computational use. In the
model, an effective antenna height is defined for the base station to obtain a field
strength suitable for varying types of terrain. However, the original expression
where only valid for frequencies up to 1500 MHz, cell range between 1 and 20
km, RBS height between 30 to 200 m and a UE height between 1 and 10 m.
The Ericsson variant of the model includes correction factors for suburban and
open areas, mixed land-sea path, isolated mountain area, and sloping terrain.
Furthermore, the frequency range has been stretched up to 3.5 GHz.
Urban: A= 157.5 dB, Suburban: A= 151.5 dB If hm = 1.5 m

Rural: A= 137.6 dB, Open: A= 127.5 dB => 3.2(Log(11.75hm))2 - 4.97 = 0
2.6 GHz
Lp  A  13.82 log hb  44.9  6.55 log hb log R  3.2log 11.75hm   4.97

2
hb
hm
Figure 2-21 Okumura-Hata model (Ericsson variant).

LTE Air Interface
The Ericsson variant Okumura-Hata model that calculates the path loss L p [dB]
for 2.6 GHz can be written as:
L p  A  13.82 log hb  44.9  6.55 log hb log R  3.2log 11.75hm   4.97

2
157.5, urban areas

151.1,
 suburban areas
A
137.6, rural areas
127.5, open areas
R is the cell range. A is a constant depending of the frequency used as well as the
area.1 hb and hm is the RBS height and UE height above the ground respectively.
Note that there is no correction factor for the UE height when hm = 1.5m as
shown in Figure 2-21.
The Okumura-Hata model is well established and different variants of the model
are implemented worldwide in various tools for RF planning. The model can be
used for simple estimations, for example in tenders, as in the RN Proposal Tool
(RNPT).
9.2 Walfish-Ikegami model

Another radio wave propagation model is the Walfish-Ikegami model. The model
was developed based on studies in Urban environment. Ikegami studied the path
loss due to diffractions over rooftops. The result was an expression that calculate
the path loss due to rooftop-to-street diffraction, Lrts .
Walfish and Bertoni made a theoretical study of propagation in the urban

environment. According to their study the total path loss consists of three
components:
 Contribution from loss in free space
 Reduction of the fields above the rooftops due to forward
diffraction past many rows of buildings
 Diffraction of the rooftop fields down to ground level
The contribution from the last two components is denoted as Lex [dB]. Walfish
and Bertoni assume an area having buildings of relatively uniform height and
with a regular street grid. The primary propagation path lies over the top of the
buildings.
By combining the two results from Walfish and Ikegami, including the free space
loss Lsp , one gets an expression for the path loss between UE and RBS in street
canyon.
1 A complete list of A values can be found in the Radio Wave Propagation Guideline

L  Lsp  Lrts  Lmsd
Lmsd is the loss due to multi-screen diffraction and is based on the Walfish-
Bertoni expression, Lex . The expression is called the COST-231 Walfish-
Ikegami Model.2
The loss is dependent on e.g. the street width w, distance from the RBS R,
building height H, UE height hm, RBS height hb above the ground as shown in
Figure 2-22.
Lmsd L  Lsp  Lrts  Lmsd

Lrts
w
Lsp
hb
h
hm
R
Figure 2-22 Walfish-Ikegami model (Cost-231).
The model above is valid for:

 frequencies between 800 MHz and 2000 MHz
 distance from RBS between 0.02 to 2 km
 RBS heights between 4 and 50 m above the ground
 UE heights between 1 and 3 m above the ground
 flat ground
 uniform building heights and building seperation
 not line of sight
However with some correction factors the model can be used for other frequency
ranges as well which makes it another important model for radio wave
propagation.
2 More information about the different Walfish-Ikegami models can be found in the Radio Wave Propagation Guideline

LTE Air Interface
Channel Models
Channel models are used to represent various average propagation conditions that
are used for the performance measurements in multi-path fading environments
for various Doppler frequencies.
Maximum
Type of Doppler
Description
User Model frequency
(fdoppler)
EPA5 5 Hz Represents slow speed pedestrian users and
yields the highest peak throughput of the channel
models.
EVA70 70 Hz Represents medium speed users such as in-car
users, and should be used when drive test
measurements are compared.
ETU300 300 Hz A high speed model which is highly dispersive,
and with multi-path that exceeds the cyclic prefix
window. The result is comparatively lower peak
throughputs.
Figure 2-23 Channel Models.
The speed of the user depends on the chosen frequency band. The following
equation calculates the speed:
v  user speed [m/s]

c  speed of light [m/s]
f doppler 
v c , 
f carrier  f doppler  Doppler frequency [Hz]
 f carrier  carrier frequency [Hz]
In this course we are going to design a network with a carrier frequency of 2600
Hz and use EPA5 as the user model. This corresponds to a user speed of
approximately 2 km/h.

Intentionally Blank

LTE Traffic
3 LTE Traffic
Top right
Slide title
40 pt Objectives of Chapter 3 corner for
field-mark,
Objectives
LTE Traffic
customer or
for example.
Text
24 pt
Bullets level 2-5 After this chapter the participants will be able to:
20 pt
1. Describe the different types of traffic carried by LTE networks.
2. Explain the protocols that support the various LTE traffic
types.
3. Explain the operation of TCP, UDP, HTTP and FTP Internet
Protocols.
4. Explain the issues surrounding Voice over LTE.

. Rev A Figure 3 - 1 LTE Traffic

LTE Dimensioning
1 Introduction
The type of traffic carried by LTE networks can be split into the five categories
listed below:
 Web Browsing
Request-response traffic generated by end user applications like
Internet ‘Explorer’ and ‘Firefox’ etc used to browse the
Internet.
 Email
Traffic generated by reading and sending emails.
 Audio/Video Streaming
Streaming traffic generated by end user applications like
‘Youtube’ used to view video content on the Internet.
 File Transfer
Traffic generated by users downloading or uploading files from
the Internet.
 Voice
Traffic generated by Voice over IP (VoIP) applications like
‘Skype’ that allow users to make and receive voice calls over
the Internet.
Each of these categories and their particular traffic demands are explained in this
chapter.

LTE Traffic
1.1 Web Browsing Traffic

The request for a web page produces a small uplink traffic requirement with a
much higher demand on the downlink as the page is downloaded to the user. The
acknowledgements and retransmission requests sent in the uplink as the page is
downloaded produce a much lower traffic requirement. The time taken to
download the web page and hence the ‘delay’ experienced by the user will
depend on the contents of the page, number of retransmissions, bandwidth
available and any latencies in the connection. The traffic generated by a user
browsing three web pages and the Internet protocol stack used is illustrated in
Figure 3-2 below. Top right
Slide title
40 pt Web Browsing Traffic corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt
www.ericsson.com
Protocol Stack
Hypertext Transfer Protocol
HTTP
Transmission Control Protocol
TCP
Internet Protocol
IP
Figure 3-2 Web Browsing

. Rev A
Traffic
Figure 3 - 2 LTE Traffic
The user generating the traffic illustrated in Figure 3-2 above reached a peak rate
of 1.36 mbps in the downlink with an average rate of 105.1 kbps and 12.3 kbps in
the downlink and uplink respectively.
As Figure 3-2 above shows Hypertext Transfer Protocol (HTTP) and

Transmission Control Protocol (TCP) are used to carry web browsing traffic over
IP. The operation of these and other Internet protocols are explained later in this
chapter.

LTE Dimensioning
1.2 Email Traffic

An email user will generate frequent peaks in the downlink and uplink traffic
requirement as the emails are read and sent. The duration of these peaks will
depend on the size of the email and the available bandwidth. As emails are
transferred to and from the users PC acknowledgements sent in the opposite
direction also generate smaller peaks in traffic requirements. Any
retransmissions will be experienced as ‘delay’ by the user. The traffic generated
by an email user reading and sending emails and the Internet protocol stack used
is illustrated in Figure 3-3 below. Top right
Slide title
40 pt Email Traffic corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt
Protocol Stack
HTTP
TCP
Internet Protocol
IP
Figure
© Ericsson AB3-3 Email
2008 03_03813 Traffic
LZU 108 7263 Uen
of 367.7 kbps in the downlink as an email was being downloaded from the server.
A slightly lower peak was reached in the uplink as an email was sent to the
server. Over the course of the session an average rate of 31.8 kbps and 19.1 bps
was generated in the downlink and uplink respectively.
As Figure 3-3 above shows Hypertext Transfer Protocol (HTTP) and

Transmission Control Protocol (TCP) are also used to carry email traffic over IP.
The operation of these and other Internet protocols are explained later in this
chapter.

LTE Traffic
1.3 Video Streaming Traffic

A user watching streaming video from the Internet generates consistently high
downlink traffic requirement as the video content is downloaded from the server.
Once a certain (configurable) buffering time has elapsed the content is shown to
the user using a suitable video playing application while the remainder is being
downloaded. The acknowledgements and retransmission requests sent in the
uplink produce a much lower traffic requirement. Any retransmissions or
bandwidth restrictions may produce a pause in the video content if all the data in
the buffer has been viewed. The traffic generated by a video streaming user and
the Internet protocol stack used is illustrated in Figure 3-4 below. Top right
Slide title
40 pt Video Streaming Traffic corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt
Protocol Stack
HTTP
TCP
Internet Protocol
IP
Figure
© Ericsson AB3-4 Video
2008 03_03813 Streaming
LZU 108 7263 Uen
. Rev A Traffic
of 1.58 mbps in the downlink with an average rate of 830.6 kbps and 20.2 kbps in
As Figure 3-4 above shows HyperText Transfer Protocol (HTTP) and

Transmission Control Protocol (TCP) are also used to carry video streaming
traffic over IP. The operation of these and other Internet protocols are explained
later in this chapter.

LTE Dimensioning
1.4 File Download Traffic

A user downloading or uploading a file from or to the Internet produces a
constantly high traffic requirement in the direction that the file is transferred.
The acknowledgements and retransmission requests sent in the opposite direction
as the file is transferred produce a much lower traffic requirement. Any
retransmissions or bandwidth restrictions increase the time required to download
or upload the file. The traffic generated by a user downloading a file from the
Internet and the Internet protocol stack used is illustrated in Figure 3-5 below. Top right
Slide title
40 pt File Transfer Traffic corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt
Protocol Stack
File Transfer Protocol
FTP
TCP
Internet Protocol
IP
Figure
© Ericsson AB3-5 File LZU
2008 03_03813 Download
108 7263 Uen
. Rev ATraffic
of 1.53 mbps in the downlink with an average rate of 650 kbps and 14.2 kbps in
As Figure 3-5 above shows File Transfer Protocol (FTP) and Transmission
Control Protocol (TCP) are used to support file transfer over IP. The operation of
these and other Internet protocols are explained later in this chapter.
1.5 Voice Traffic

A voice over IP (VoIP) call, unlike the previous traffic types produces a near
symmetrical but relatively small traffic requirement. Since latency is an important
consideration in conversational traffic there is no retransmission mechanism
employed by the higher layers, however the LTE HARQ mechanism will use
retransmissions to correct errors in the air interface in the same manner as all
other traffic. The traffic generated by a Voice over IP (VoIP) call and the
Internet protocols used is illustrated in Figure 3-6 below.

LTE Traffic Top right
Slide title
40 pt Voice Traffic corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt
3 minutes of speech:
(21.4 + 24.7) X 103 X 60 X 3
≈ 1 MB
8 X 220
Protocol Stack
User Datagram Protocol
UDP
Internet Protocol
IP
Figure 3-6
© Ericsson AB Voice
2008 03_03813 LZU Traffic
108 7263 Uen
of 39 kbps in the uplink with an average rate of 21.4 kbps and 24.7 kbps in the
downlink and uplink respectively.
A 3-minute speech call will generate approximately 1 MB of combined uplink

and downlink data as illustrated in Figure 3-6 above.
Datagram Protocol (UDP) is used to carry voice traffic over IP. The operation of
this and other Internet protocols will be explained in this chapter.
2 Internet Protocols used for LTE Traffic

The Internet Protocols that will be explained in this chapter are listed below:
 Transmission Control Protocol (TCP)
 User Datagram Protocol (UDP)
 Hypertext Transfer Protocol (HTTP)
 File Transfer Protocol (FTP)
It is assumed that the students are familiar with Internet Protocol
(IP) which ultimately carrys all these protocols across the Internet.
2.1 Transmission Control Protocol (TCP)

Transmission Control Protocol (TCP) is a reliable, connection-oriented delivery
service. Since it is connection-oriented a session must be established between the
two end point connections before data can be exchanged.

LTE Dimensioning
The end point connections on each device known as ‘sockets’ consist of an IP

address and 16-bit port number. The port identity is used by transport protocols
to identify to which application protocol or process they must deliver incoming
messages.
TCP views the data stream as a sequence of octets or bytes that is divided into
segments for transmission. Each segment travels across the network in a single IP
packet. Reliability is achieved by assigning a sequence number to each segment.
When TCP sends a segment it maintains a timer, waiting for the other end to
acknowledge reception of the segment. If an acknowledgement is not received
within the timer period, the segment is retransmitted.
To support flow control each end of a TCP connection has a finite amount of
buffer space which it signals to the transmitter so that it is not overloaded with
data. TCP also reacts to congestion on the network and automatically adjusts the
transmission speed to the bandwidth available on the network.
A TCP session is initialized by means of a three-way handshake. During this

process, the two communicating devices synchronize the sending and receiving
of segments, inform each other of the amount of data they are able to receive at
once (window size and segment size), and establish a virtual connection.
TCP advertises a window size during connection establishment. The

communicating ends set the buffer for the connection by looking at the window
size advertised by the other end.
The TCP packet structure and a summary of its operation is illustrated in Figure
3-7 below.

LTE Traffic Top r
Slide title
40 pt Transmission Control Protocol corne
field-
custo
Slide subtitle + Bits 0-7 Bits 8-15 Bits 16-23 Bits 24-31 partn
24 pt See B
for ex
0 Source Port Destination Port
Text
24 pt 32 Sequence Number
Bullets level 2-5
20 pt
64 Acknowledgement Number
96 Offset Res Flags Window
128 Checksum Urgent Pointer
160 Options Padding
• Connection-oriented
• Data sent between ‘sockets’
192+ Data • Sequence number on each segment.
• Tx waits for ACKnoledgement
• Each end informs the other about window size
• Connection closed by ‘FIN’ flag.
Figure 3-7 Transmission Figure

. Control
© Ericsson AB 2008 03_03813 LZU 108 7263 Uen Rev A
3-7 Protocol LTE Traffic
The contents of the TCP header are explained below:

 Source Port
16 bits used to identify the TCP port of the sending device.
 Destination Port
16 bits used to identify the TCP port of the receiving device.
 Sequence Number
32 bits used to identify the sequence number of the data
segment sent.
 Acknowledgement Number
32 bits used to identify the sequence number that the receiver
expects to receive next.
 Offset
4 bits used to indicate the number of 23-bit words in the TCP
header.
 Res
6 bits reserved for future use.
 Flags
The following one bit flags are used to communicate between
the TCP entities:

LTE Dimensioning
- Synchronous (SYN) set set during the three-way handshake

connection establishment.
- Finish (FIN) set during connection termination.
- Congestion Window Reduced (CWR) set to indicate a
reduction in the congestion window.
- Urgent (URG) set when urgent data has been sent in the
normal stream.
- Acknowledgement (ACK) is set when the receiving TCP
generates a segment to acknowledge the received data sent by
the sender.
- Push (PSH) set to instruct the receiver to pass all its data to
the receiving process.
- Reset connection (RST) A common situation where a reset is
generated is when a connection request arrives and no process
is listening on the destination port. Another is when one end is
willing to immediately abort the connection. That end transmits
a segment with the reset flag set.
 Window
16 bits used to specify the number of data bytes that the
receiver’s buffer can accept.
 Checksum
16 bit result of a checksum performed on the TCP header and
data.
 Urgent Pointer
16 bits used to point to the end of the urgent data in the
segment when applicable.
 Options
This variable size field can be used for a number of functions,
the most common being to indicate the maximum segment size
(MSS).
2.1.1 TCP Operation

Before data can be transferred using TCP the ‘client’ must set up a connection
with the ‘server’ using a three-way handshake process. This process begins with
the client generating a sequence number and sending a segment with the SYN
flag set to on to the server. This segment header also includes the size of client’s
receive buffer (window size) and the size of the biggest data segment that it can
handle.
The server acknowledges (ACK) the request by sending back a segment with the
synchronisation SYN flag set to on. This segment header contains the server’s
own start-up sequence number and the acknowledgement for the previous SYN
segment it received from the client and also the size of the server’s receive buffer
(window size) and the size of the biggest data segment it can handle.

LTE Traffic
The client then sends back an acknowledgement of the server’s start-up sequence
segment. Once server receives this acknowledgement the three-way handshake
process is complete and data transmission can begin as illustrated the example in
Figure 3-8 below.
Top right
Slide title
40 pt TCP Operation corner for
field-mark,
customer or
Sequence No: 1,000 Flags
Window size: 8,750 Bytes SYN
24 pt Max segment: 1,460 Bytes See Best practice
Three-way Acknowledgment No: 1,001 SYN
for example.
handshake Window size: 8,750 Bytes ACK
Text Max segment: 1,460 Bytes
24 pt Sequence No: 1,001 Flags
Bullets level 2-5 Acknowledgment No: 3,001 ACK
20 pt
Sequence No: x Flags
Acknowledgment No: 1 ACK
Data
Sequence No: y Flags

Acknowledgment No: 1 ACK
Data
Sequence No: n Flags
Acknowledgment No: z ACK
Client Sequence No: 3,531 Flags Server

Acknowledgment No: 5,145 FIN
ACK
Acknowledgment No: 3,532 ACK
Closing the
connection Sequence No: 5,146 Flags
Acknowledgment No: 3,532 FIN
ACK
Acknowledgment No: 5,147 ACK

Figure 3-8 TCP Operation
During the data transmission the client sends an acknowledgement after every
second segment has been received as illustrated in Figure 3-8 above.
Either end can close the connection by sending a segment with the FIN flag set.
When one end receives a segment with the FIN flag set it sends back an
acknowledgement followed by a segment of its own with the FIN flag set. Once
this is acknowledged by the other end the TCP connection is closed.
2.1.2 TCP Flow Control

TCP packet may experience some queuing in any routers between the client and
server. This can result in dropped packets if the router runs out of buffer space.
The TCP flow control mechanism is designed to reduce the amount of data sent
when congestion is detected in the network.
After the connection is established TCP will send the number of segments
specified by the ‘congestion window size (cwnd)’ which is normally set to 1 and
wait for an ACK from the receiver. When that ACK is received cwnd is
increased from one to two, and two segments can be sent. When each of these
two segments are acknowledged, cwnd is increased to four and so on. The
transmitter will increase cnwd exponentially until it reaches the advertised
window size of the receiver or until congestion is reached. This TCP ‘Slow Start
Algorithm’ is illustrated in Figure 3-9 below.

LTE Dimensioning Top right
Slide title
40 pt
TCP Flow Control LTE L13 Radio Network Design
corner for
field-mark,
customer or
Slide subtitle partner logotyp
24 pt See Best pract
Slow Start Congestion avoidance for example.
Text Receiver Window Size

Number of Segments sent
24 pt
Bullets level 2-5 Packet Loss
20 pt (congestion)
SSTresh
Initial cwnd
Time
Figure 3-9 TCP Flow ControlFigure 3 - 9
. Rev A LTE Traffic
When a loss occurs half of the current cwnd is saved as a Slow Start Threshold
(SSThresh) and slow start begins again from its initial cwnd. Once the cwnd
reaches the SSThresh TCP goes into ‘congestion avoidance mode’ where each
ACK increases the cwnd by a number equal to segment size X segment
size/cwnd. This produces a linear increase in cwnd as illustrated in Figure 3-9
above.
2.1.3 TCP Throughput

To ensure reliable data transfer the transmitter will limit the amount of data it
sends before receiving acknowledgements to the size of the receiver's window.
This means that the maximum throughput of a TCP connection is limited by the
receive window size and the Round Trip Time (RTT). Thus the maximum TCP
throughput can be calculated by dividing the Receive Window size (in bits) by
the Round Trip Time (in seconds). The first formula illustrated in Figure 3-10
below can be used to calculate the downlink throughput requirement for a FTP
service.

Top right
Slide title
40 pt
LTE Traffic TCP Throughput corner for
field-mark,
customer or
Slide subtitle partner logotypes
for example.
Receive Window Size
Text DL Throughput =
24 pt Round Trip Time
Bullets level 2-5
20 pt
Window Size
Round Trip Time
DL Throughput
UL Throughput = X ACK Size
(2 X Segment Size)
Figure 3-10 TCP Throughput
During a file transfer the TCP receiver sends an acknowledgement for every two
segment that it receives. This means that a certain amount of throughput is
required in the uplink to support file transfer in the downlink.
The number of segments sent per second can be calculated by dividing the
downlink throughput (in bits per second) by the segment size (in bits). Since one
acknowledgement will be required for every two of these segments the uplink
bandwidth requirement can then be calculated by dividing the number of
segments sent per second by two and multiplying by the size of the
acknowledgement. The second formula illustrated in Figure 3-10 above can be
used to calculate the uplink throughput requirement for a FTP service.
For calculation purposes it can be assumed that the segment size is 1360 Bytes or
10880 bits and that the acknowledgement size is 20 Bytes or 160 bits.

LTE Dimensioning
Top right
2.1.3.1 TCP Throughput Example
Slide title
40 pt TCP Throughput Example corner for
field-mark,
customer or
An example TCP throughput calculation is illustrated in Figure 3-11 below.
Slide subtitle partner logotype
24 pt See Best practic
for example.
(8750 X 8)
Text DL Throughput = =_________ = ___ mbps
24 pt 10 X 10-3
Bullets level 2-5
20 pt
8,750 Bytes
10 msec
UL Throughput = X 160 = ______= ___kbps

(2X10880)
Figure 3-11 TCP Throughput Example
It should be remembered that all throughput values in Figure 3-11 above are at
TCP level.
2.2 User Datagram Protocol (UDP)

User Datagram Protocol (UDP) is the simplest of the Transport Layer protocols
and provides the least service. It is basically a datagram type service that is
connectionless, unreliable and efficient as there is no connection opening or
closing. UDP is ideally suited to carry small packets of traffic that do not require
acknowledgement from the receiver making it the ideal choice to carry voice over
IP.
UDP provides port numbers used to distinguish between multiple programs

executing on a single device. That is, in addition to the data sent, each UDP
message contains both a destination port number and a source port number. This
makes it possible for the UDP software at the destination to deliver the message
to the correct application program, and for the application program to send a
reply.
The UDP packet structure and a summary of its operation is illustrated in Figure
3-12 below.

LTE Traffic Top right
Slide title
40 pt User Datagram Protocol corner for
field-mark,
customer or
+ Bits 0-7 Bits 8-15 Bits 16-23 Bits 24-31 for example.
Text
24 pt
Bullets level 2-5
0 Source Port Destination Port
20 pt
32 Length Checksum
• Connectionless
64
Data Data
• Unreliable
+
• Efficient
• No sequence numbering
• No connection opening or closing
Figure 3-12 User Datagram Protocol
The contents of the UDP header are explained below:

 Source Port
16 bits used to identify the UDP port of the sending device.
 Destination Port
16 bits used to identify the UDP port of the receiving device.
 Length
16 bits used indicate the size in bytes of the UDP packet,
including the header and data. The minimum length is 8 bytes
which is the length of the header alone.
 Checksum
16 bits used used to verify the integrity of the UDP header. The
checksum is performed on a “pseudo header” consisting of
information obtained from the IP header (source and
destination addresses, and protocol number) as well as the UDP
header. The purpose of using a pseudo-header is to verify that
the UDP packet has reached its correct destination. The UDP
header itself specifies only the protocol port number. Thus, to
verify the destination, UDP on the sending machine computes a
checksum that covers the destination IP address as well as the
UDP packet. At the ultimate destination, UDP software verifies
the checksum using the destination IP address obtained from
the header of the IP packet that carried the UDP message. If the
checksum agrees, then it must be true that the packet has
reached the intended destination host as well as the correct
protocol port within that host.

LTE Dimensioning
2.3 Hypertext Transfer Protocol (HTTP)

Hypertext Transfer Protocol (HTTP) is the Internet standard communication
protocol used between Web servers and clients and Hypertext Markup Language
(HTML) is the standard language for writing Web documents. The logical
structure of a Web document is based on HTML tags which identify headers, lists
and paragraphs. All documents, images, audio or video clips on the Web are
called ‘resources’. To address and identify the access method for these resources
the Web uses URLs (Uniform Resource Locators).
Every Web page is assigned a unique URL (Uniform Resource Locator) that
effectively serves as the page’s world-wide name. URLs have three parts: the
protocol, the Domain Name Server (DNS) name of the host on which the page is
located, and a local name uniquely indicating the specific page (usually a file
name and path). For example, http://www.ericsson.com/datacom/solutions.
The HTTP request message as illustrated in Figure 3-13 below is an ASCII

character string containing a verb (command describing what to do) and an
Top right
address (where to do it at). The address format is defined by a uniform resource
Slide title
40 pt Hypertext Transfer Protocol
location (URL), which also includes the protocol to be used.
corner for
field-mark,
customer or
24 pt Command Uniform Resource Location (URL) See Best practice
for example.
Text
24 pt
Bullets level 2-5
GET http://server.name/path/file.type
20 pt
www.ericsson.com
Requested web page carried to user by TCP

Figure 3-13 Hypertext Transfer Protocol
In the example in Figure 3-13 above the HTTP command ‘GET’ is sent from the
UE to the server followed by the URL for the requested web page. The response
message contains the requested data which is carried to the UE using TCP.

LTE Traffic
2.3.1 Web Operation Example

In the example illustrated in Figure 3-14 below the user has just clicked on some
piece of text or perhaps an icon that points to the page whose URL is: Top right
‘http://www.3gpp.org/specs/numbering.htm’
Slide title
40 pt HTTP Operation Example corner for
field-mark,
customer or
24 pt Domain See Best practice
Name for example.
Server
Text
24 pt
‘www.3gpp.org’ IP address?
Bullets level 2-5
20 pt 1
2
IP address is ‘195.238.226.15
3
TCP connection setup
www.3gpp.org/specs/numbering.htm
4 HTTP GET /specs/numbering.htm
ACK ACK ACK
7 5 ‘numbering.htm’ sent to browser
Segment Segment Segment Segment Segment Segment

6 TCP connection released
www.3gpp.org
195.238.226.15
Figure 3-14 HTTP Operation

. Rev A
Example
The steps that occur between the user’s click and the page being displayed are as
follows:
1 The browser asks the Domain Name Server (DNS) for the IP address
of ‘www.3gpp.org’.
2 The DNS replies with the IP address ‘195.238.226.15’.
3 The browser makes a TCP connection to IP address 195.238.226.15.
4 HTTP ‘GET /specs/numbering.htm’ command is sent by the browser

to IP address 195.238.226.15.
5 The ‘numbering.htm’ file is sent form IP address 195.238.226.15 to

the browser using TCP.
6 The TCP connection is released.
7 The browser displays all the text in ‘LTE.html’.

LTE Dimensioning
For each image (icon, drawing, photo and so on) on a page, the browser
establishes a new TCP connection to the relevant server to fetch the
image.
2.4 File Transfer Protocol (FTP)

FTP is the Internet standard for file transfer used to copy a complete file from one
system to another. FTP runs exclusively over TCP. By default a server listens on
TCP port 21 for incoming connections from FTP clients. When a connection is
detected the server will send the FTP response message number 220 (FTP Server
ready) from TCP port 21 to the originating TCP port on the client.
The client will then send a FTP request message containing the ‘USER’
command and a username or ‘anonymous’ to TCP port 21 on the server. If the
username is valid or if ‘anomies’ is allowed the server will indicate this to the
client with a FTP response message number 331 (Username OK, password
required).
On reception of this response the client will send a FTP request message
containing the ‘PASS’ command and the password it is using. If the password is
allowed the server will send FTP response message number 230 (Guest Login
okay) or similar.
The client uses a FTP request message containing the ‘SIZE’ command to get the
file size from the server. Once all the FTP signaling negotiations have been
complete file transfer can begin on a separate FTP ports as illustrated in Figure Top right
Slide title
40 pt File Transfer Protocol Text
3-15 below. corner for
field-mark,
customer or
24 pt TCP Port Response: # 220 (FTP Server ready) TCP Port See Best practice
xxxx 21 for example.
Text Request: USER ‘anonymous’

24 pt
Bullets level 2-5
20 pt Response: # 331 (Username OK, password required)
Server
Client
Request: PASS ‘IEuser@’
Response: 230 (Guest Login okay)
Response: 226 (Transfer complete)
TCP Port TCP Port

yyyy zzzz
Segment Segment Segment Segment Segment Segment TCP TCP TCP
ACK ACK ACK
Figure 3-15 File Transfer Protocol

Figure 3 - 18. Rev A LTE Traffic
The file is transferred by TCP in the normal way. The server will send the FTP
response message no 226 (Transfer complete) to the client when file transfer is
complete as illustrated in Figure 3-15 above.

LTE Traffic
3 Voice over LTE

The user satisfaction with a voice service due to its conversational nature is
dependent on the total delay. For a voice service carried by LTE this total delay
is made up of the following:
 Delay associated with the size of the speech frame (Tframe)

which is 20 msec.
 Delay associated with the AMR encoding process (Tenc)
 Radio Network Radio delay (Tr)
 Transport Network delay (Tt)
 Service Network delay (Ts)
 Delay associated with the jitter correction buffer at the receiver
(Tjitter)
 Delay associated with the AMR decoding process (Tdec)
The delays experienced by a voice call between two LTE users is Top right
Slide title
40 pt Voice over LTE Total Delay
corner for
field-mark,
customer or
for example.
eNodeB eNodeB
Terminating
Text Originating Service UE
UE Network
24 pt AMR
AMR: AMR AMR
+ jitter buffer:
Bullets level 2-5
Tframe Tdec
20 pt +
RTP/UDP GW GW UDP/RTP
+
Tenc IP IP IP IP Djitter
PDCP PDCP PDCP PDCP
RLC UM RLC RLC RLC UM
MAC MAC MAC MAC
PHY HARQ PHY TR TR TR TR PHY HARQ PHY
Radio Radio
delay: delay:
Tr Tr
Transport: Service: Transport:

Tt Ts Tt
User satisfaction depends on total delay

(Tframe + Penc + Tr + Tt + Ts + Tt + Tr + Tdec + Tjitter)
Figure 3-16 Voice over

.
LTE Total
Rev A
Delay
The Radio Delay (Tr) is mainly associated with the Hybrid ARQ
process as illustrated in Figure 3-16 above.

LTE Dimensioning
3.1 HARQ Effect on Voice Service

In WCDMA each 20 msec block of speech is carried by a continuous stream of
data over the air interface without any retransmission mechanism. If a block
arrives corrupted it is simply discarded resulting in an increase in the Block Error
Rate (BLER).
In LTE the 20 msec speech block is carried by one 1 msec subframe and is
subject to retransmissions. If this subframe is not received correctly it will be
retransmitted according the HARQ process. A comparison between the
transmission of four speech blocks on WCDMA and LTE is illustrated in Figure Top right
Slide title
40 pt HARQ Effect on Voice Service
3-17 below. corner for
field-mark,
customer or
Power
Slide subtitle
24 pt
WCDMA partner logot
See Best pra
X X
for example.
Speech Frame Speech Frame Speech Frame Speech Frame
Text
24 pt #1 #2 #3 #4
Bullets level 2-5
20 pt 20 msec 20 msec 20 msec 20 msec Time
Power
LTE
X X X XXX X X
1 msec
Time
Radio Delay (T r)
Radio Delay (Tr) < 80 msec

Lost or late Blocks <1 %
Figure 3-17 HARQ Effect onFigure

Voice
3 - 17 Service
. Rev A LTE Traffic
< 80 msec
Although the first and second speech frames were not correctly decoded by the
WCDMA receiver, the third and fourth frames were sent without any
retransmissions producing an increased BLER.
On the LTE system the first subframe was incorrectly decoded and retransmitted
twice before the second subframe was sent. These retransmissions and the
second speech block were also incorrectly decoded requiring a number of
retransmissions.
The final retransmission of the first speech block represents the Radio Delay (T r)
in this illustration. Speech users are satisfied if the Radio Delay (Tr) is less than
80 msec and the number of and lost or delayed blocks is less than 1% as
illustrated in Figure 3-17 above.

ChapterTitle
4 LTE Dimensioning
Objectives

1. Explain the Ericsson LTE dimensioning process.
2. Perform uplink and downlink coverage and capacity calculations for LTE.
3. Perform Control Channel dimensioning
4. Perform Tracking Area planning
5. Perform Paging Capacity calculations
6. Explain which tools are used in radio network dimensioning
7. Apply subscriber and traffic growth scenarios and perform dimensioning
exercise
8. Recommend sites for LTE deployment to meet coverage and capacity
requirements set by the customer

1 Introduction
The typical Network requirements that make up the input to the dimensioning
process are; coverage area, number of subscribers, traffic model and
Uplink/Downlink cell edge throughput. There are a number of ways to
dimension the LTE network to meet these requirements. Figure 4-2 below
illustrates one LTE dimensioning process that can be followed to produce a final
site count (or site-to-site distance) that meets the uplink and downlink coverage
and capacity requirements.
- eNodeB power
- Tx Diversity
1 - MIMO
Quality Requirements - UE Power
- UE Rx Diversity
2
UL Dimensioning
- cell range
- UL cell edge bit rate
Input 3
- UL cell Capacity
requirements DL Dimensioning
not met
4 - DL cell edge bit rate
Control Channel - DL cell capacity
Coverage
Done
Figure 4-2 LTE Dimensioning Process
The uplink coverage calculations are started with assuming a short site-to-site
distance. Calculations are performed to determine if the performance with the
estimated initial (short) site-to-site distance fulfill the network requirements. The
site-to-site distance is then increased in several iterations until one or more of the
requirements are not fulfilled anymore. Once a maximum site-to-site distance that
meets the uplink requirements has been determined it is used as input to the
downlink coverage calculations.
The downlink coverage calculations are performed to ensure that the downlink
network requirements are met. Like the uplink the site-to –site distance may
need to be decreased if the downlink requirements are not met. The final site-to-
site distance that meets both uplink and downlink coverage requirements is
chosen.

ChapterTitle
The uplink and downlink capacity calculations are performed to provide the
uplink and downlink cell and maximum user throughputs which are the inputs to
subsequent dimensioning tasks for the eNodeB and transmission network.
› Define quality requirements

– Coverage
› e.g. 500 kbps at cell edge with 98% probability
– Capacity
› e.g. cell throughput 5 Mbps or 10Mbps per square kilometer
› Define prerequisites
– Diversity, MIMO, RBS and UE power, BW, freq band
› UL dimensioning
– Increase site-site distance until requirements not fulfilled
– Tune power ctrl and PUSCH load parameters
› DL dimensioning
– Use site-site distance from UL and check DL requirements
› Control channel coverage
– Ctrl channel performance should not limit cell edge performance
Figure 4-3. Dimensioning method.
The tools to use for LTE radio network dimensioning include e.g. spreadsheet
applications like Excel or similar, pocket calculators or internally developed
tools. In this course Excel is used.
2 LTE Network Dimensioning Example

An urban area of 9 km2 is covered by eighteen 3-sector (54 cells) WCDMA sites
as illustrated in the figure below.

Area Characteristics
20,000 LTE Subscribers
9 km2 Urban area
Network Requirements
Cell Edge Throughput:
- Uplink = 500 kbps
- Downlink = 8 Mbps
20,000/54 = 371 subscribers per cell @ 95% coverage probability
Subscriber Traffic Profile

Channel Model: EPA5
Monthly data upload: 2 GB
Monthly data download: 5 GB
Network Details
RBS power at ref point = 40W
UE O/P Power = 23 dBm
Channel Bandwidth = 20 MHz
Frequency band: 2600 MHz
Figure 4-4: Network Dimensioning Example
The LTE dimensioning process is used to calculate the number of eNodeBs

needed to cover the same area with the LTE network requirements given in the
table in the figure above.
The following prerequisites are assumed for this network:
 E-UTRA Band 7 (2.6 GHz) with 20MHz channel bandwidth.

 RRUs (no feeder loss) are used with 40W output power at the
reference point.
 MIMO configuration with 2x2 OLSM
 Base Station antenna gain is 18.5 dB, equivalent tilt angle of 5˚
for a cell range of 1000m
 UE output power: 23 dBm, antenna gain 0 dBi; receive
diversity
 18 dB indoor penetration loss
 3dB additional loss due to jumpers, body loss etc
 Mobile broadband traffic model
 Number of OFDM symbols allocated for PDCCHs: 1
 Number of resource blocks allocated for PUCCHs: 4
 Max modulation for UL: 16 QAM
 All UEs have two receiving antennas

ChapterTitle
 ICIC is used, i.e. transmission starts at random positions in the

deployed frequency band so that inter-cell interference is
evenly distributed over the bandwidth
 Layer 1 overhead for all control channels and signals is
included in the SINR to bit rate relationships.
 All resource blocks are transmitted at the same power.
 We assume that the most efficient Modulation and Coding
Scheme (MCS) is always used.
 No positioning (no PRS resources allocated for OTDOA)
 Channel Model: EPA 5
 Urban area
Since this area is already covered by eighteen 3-sector sites, or (3∙18) 54 cells,
this would be a good choice for the initial site count. Since there is 20,000
subscribers and 54 cells this means that there will be 20,000/54 = 371 subscribers
per cell.
2.1 Cell Throughput (Tcell)

If we assume that there are 30 days per month and the average subscriber is
active for 10 hours per day and since there are 3600 seconds in an hour and 8 bits
in a Byte, the amount of data uploaded by an average subscriber (Dsub,UL) in GB Top right
(Bytes ∙ 230) can be converted to the subscriber uplink throughput (Tsub,UL) in kbps
Slide title
40 pt Uplink Cell Throughput (T
using the formula illustrated in Figure 4-5 below. cell,UL ) corner for
field-mark,
customer or
Dsub,UL X 230 X 8 for example.
Tsub,UL = [kbps]
Text 30 X 10 X 3600 X 103
24 pt
Bullets level 2-5 Dsub,UL
20 pt
[GB]
Dsub,UL Dsub,UL
Tcell,UL = Tsub,UL X Nsubs [kbps]
[GB] [GB]
Dsub,UL
[GB]
Figure 4-5 Uplink Cell Throughput

Figure 4 - 3 . Rev A LTE Dimensioning

The uplink cell throughput (Tcell,UL) in kbps can be calculated by multiplying the
subscriber uplink throughput (Tsub,UL) by the number of subscribers served by the
cell (Nsubs) as illustrated in Figure 4-5 above.
Alternatively Tcell,UL can be given as one of the network criteria inputs if the
number of subscribers and traffic model is not known.
The calculation of Tsub,UL and Tcell,UL for the Network dimensioning example is
2 X 230 X 8
15.9 [kbps]
= _____
30 X 10 X 3600 X 103
1 GB
1 GB 15.9 371 = _______

_____X 5900 [kbps]
1 GB
1 GB
371 subs per cell
Figure 4-6 Uplink Cell throughput Example
This uplink cell throughput (Tcell,UL) for the cell in Figure 4-6 above is (rounded
to nearest 1000 kbps) ____________ kbps.
The downlink cell throughput requirement can be calculated in the same way as
for UL, i.e. Tcell,DL = 5/2*Tcell,UL =___________ kbps.
Also, an optional quality requirement for high bit rates can be defined. This is
valid for UEs close to the site, i.e. with low path loss and high SINR. Here we
use an UL high rate requirement of 10 Mbps.

ChapterTitle
Fill in the input requirements below:
Input requirements: [kbps]

UL celledge rate 500 coverage prob 0,95
UL high rate 10000
UL cell thrp 6000
DL cell edge rate 3000 coverage prob 0,95
DL cell thrp 15000
1
Quality Requirements
2
UL Dimensioning
3
DL Dimensioning
4
Control Channel
Coverage
Done
Figure 4-7: Input requirements
Now we have the quality requirements that we will use as input to the
dimensioning process, starting with the UL.
3 Uplink Dimensioning
In many cases the uplink is the limiting link (bottleneck). That is why we start
with the uplink dimensioning process, which is shown below:
1
2 Assume:
-site-site distance (short)
-PC target
4 -UL load
Increase 5
site-site
3 Adjust PC
distance until Coverage calculation target and
input UL load to
requirements 6 increase site-
not fulfilled site distance
Capacity calculation
further
Done
Figure 4-8 UL dimensioning process.

The uplink dimensioning process is iterative. By gradually increasing the site-to-

site distance, the maximum distance supporting the quality requirements is found.
The starting point is a short site-to-site distance where the quality requirements
are fulfilled, a certain power control setting and a certain load level. The coverage
and capacity is calculated and the result is compared to the quality requirements.
The site-to-site distance is increased in several iterations as long as the
requirements are still fulfilled. When the coverage and capacity has been
degraded to the level of the requirements, the power control target (P0) and the
load level (QUL) are optimized in order to further increase the site-to-site distance.
› Is used as a variable in order to maximize coverage area

with fulfilled requirements
› Can also be a prerequisite (e.g. at co-siting)
R
3R
d=
2
9√3R2
Areacell=
8
Figure 4-9. Site-to-site distance, d.
In many situations, the site-to–site distance is given (e.g. at co-siting LTE with
e.g. WCDMA). Then optimization of the performance is done by finding the
optimum power control and load combination.
The iteration parameters are listed below:
3.1 Site-to-site distance expressed as signal attenuation

The site-to-site distance is expressed as the median signal attenuation at the cell
border, Lsa,cellrange.
This is done in order to make the make the calculations invariant of the wave-
propagation characteristics.
The signal attenuation is the air path loss, including antenna gains and various
losses.

ChapterTitle
› The median signal attenuation at the cell border, Lsa,cellrange ,

is used to represent site-site distance
› Good starting point is 110 to 120 dB
med
ian a
ttenu
ation
(Ls
a ,cellr
ange )
Figure 4-10: Signal attenuation

3.2 Power control target

The power control algorithm gives the operator a possibility to adjust the power
control target, P0, with the parameter pZeroNominalPusch.
› The parameter pZeroNominalPusch sets the power control

target, P0
› P0 = pZeroNominalPusch – 10log(nant)
› The setting of P0 affects both coverage and capacity
› P0 is the PSDrx target, common for all UEs in the cell
› A higher setting leads to higher cell throughput but also
higher noise rise. Good starting point is -106dBm/RB
nant=number of P0 Interference, IRB,UL
antennas Interference
PUE,RB
Figure 4-11: Power control target
3.3 PUSCH load

The load level can be a prerequisite or used as a variable where different load
levels can be tested in order to maximize performance.
› Fraction of PUSCH resource blocks carrying user data

› Prerequisite
or
› Variable in order to maximize performance
› If not a prerequisite, a suitable starting point is 80-100%
tim
e
frequency
Figure 4-12. PUSCH load level, QPUSCH.

ChapterTitle
Now we will start with the UL dimensioning and fill in the results from above
(Lsa,cellrange, P0 and QPUSCH) in the first iteration (It1) in table below.
In the second iteration (It2), Lsa,cellrange is increased to the maximum, with the
other parameters kept at initial assumptions, still fulfilling the quality
requirements.
The third iteration corresponds to the final Lsa,cellrange,with optimized values for P0
and QPUSCH.
We will work with iteration 1 in this book. Iteration 2 and 3 are not shown since
there are probably a very large number of iterations inbetween the first (It1) and
the final iteration (It3).
Fill in the iteration parameters for iteration 1 below (iteration 2 and 3 are also
shown in the ppt slide at the end of this chapter, where all figures are shown):
1
2 Assume:
-PC target
4 -UL load
5
3
Coverage calculation
6
Done
Figure 4-13: Iteration parameters
3.4 Uplink coverage calculation

The UL coverage is calculated for a given combination of Lsa,cellrange, P0 and QUL.,
which includes the steps and variables shown below:

› Thermal noise, Nt
› Noise rise, BIUL
› Resource block allocation, n’RB
› Power level, PUE,RB
› Bit rate, R
› Cell edge bit rate, Rcelledge 1
› High bit rate, Rh 2 Assume:
› UL link budget, Lpmax 4
-PC target
-UL load
5
3
6
Done
Figure 4-14: Uplink coverage calculation
3.4.1 Thermal Noise

Thermal noise is the noise contribution that the electron thermal movement gives
rise to in a conductor. The thermal noise power per hertz can be expressed as:
N t  10 log( kT ) [dBm]
Where
k is Boltzmann’s constant = 1.38 X 10-23 J/K
T is the absolute temperature in Kelvin = 290 (17o C)
Nt=10log(1,38e-23 x 290) = -204dBW/Hz = -174dBm/Hz
The noise figure (Nf) of a receiver describes how much it degrades the SNR due
to its own components. The Radio Unit (RU) has a noise figure of typically 2 dB
(=1.58 linear).
The total noise floor per resource block of the RBS (NRB,UL) can, in linear form,
be expressed as the thermal noise per hertz (Nt), multiplied by the bandwidth in
hertz (180 kHz, which corresponds to one resource block), multiplied by the
receiver total noise figure. In logarithmic form (dB) it becomes the sum of these
terms (the bandwidth has to be converted to dB).
The expression for the total noise figure of the RBS Nf,RBS, according to Friis
formula, is shown in the figure below. It depends on the TMA noise figure Nf,,TMA,
the RU noise figure Nf,RU (multiplied by the feeder loss, Lf) and the gain of the
TMA (GTMA). This total noise figure has to be considered when calculating the
total noise floor. The formulas for the thermal noise calculations (per resource
block) are shown below. Fill in the result.

ChapterTitle
N RB ,UL  Nt  10 log(WRB )  N f , RBS

Nt -174
Wrb 180000
Where: Nf,tma 1
Nf,ru 1,58
– Nt is thermal noise power density (PSD): -174dBm/Hz
– WRB is the RB bandwidth: 180 kHz Lf 1
– Nf,RBS is the RBS noise figure at the RX reference point [dB] Gtma 1
N f , RU L f  1 Nrb,ul -119,46
N f , RBS  10 log( N f ,TMA  )
GTMA
Where:
– Nf,TMA is the noise figure of TMA: e.g. 1.0 (no TMA, linear)
– Nf,RU is the noise figure of the RU: e.g. 1.58 (linear)
– Lf is the feeder loss: e.g. 1.0 (RRU, linear)
– GTMA is the gain of the TMA: e.g. 1.0 (no TMA, linear)
Figure 4-15. UL thermal noise.

3.4.2 Uplink System Reference Point

The uplink system reference point for link budget calculations will depend on
whether an ASC is used or not as illustrated in figure below.
UE Antenna Gain
i] X
(GUE) [dBi] [dB eNodeB Antenna
ode X
+ Ge
N
Gain (GeNodeB) [dBi]
= GU
E
X
Ga
Antenna Jumper loss (LJ) [dB]
Reference point with ASC

ASC ASC insertion loss (LASC) [dB]
ASC contains TMA

to overcome
LASC, LF and LJ+C Feeder loss Jumper & Connector
(LF) [dB] losses (LJ+C) [dB]
Reference point without ASC
eNodeB
Figure 4-16: Uplink System Reference Point
The Antenna System Controller (ASC) contains a variable gain Tower Mounted
Amplifier (TMA). The gain of the ASC is adjusted to overcome the sum of ASC
insertion loss (LASC), Feeder loss (LF) and all Jumper and Connector losses
between the ASC and eNodeB (LJ+C) for the uplink. This means that when the
ASC is used the reference point for link budget calculations is the top of the ASC
as illustrated in figure above and only the Antenna Jumper loss (LJA) needs to be
included.
If an ASC is not used the uplink reference point for link budget calculations is the
top of the eNodeB and all feeder and jumper/connector losses must be included.
In the case where the eNodeB uses a Remote Radio Unit (RRU) fiber optical
cables are used instead of RF feeder, jumper and connectors so no feeder and
jumpers losses need to be included in link budget calculations.
The antenna gain (Ga) is the sum of the UE and eNodeB antenna gains (GUE +
GeNodeB) as illustrated in figure above.

ChapterTitle
Interference Rejection Combining (IRC) is an optional feature that can be used to

enhance capacity by suppressing inter-cell interference in UL.
› Inter Cell Interference can be suppressed by interferer

spatial combining of multiple receiving
antennas
› Increases the Capacity
› Replaces Maximum Ratio Combining (MRC)
› Cancellation efficiency expressed by factor β
0 < β < 1,
depending on scenario. 0 means no
cancellation and 1 means complete
cancellation of interferer
Figure 4-17: Interference Rejection Combining (IRC)
3.4.3 Noise rise

The interference from other cells is modeled as an interference margin, or “noise
rise”. The interference per resource block, IRB,UL depends on the power control
target, cell geometry and isolation. This can be estimated with a ring method. The
result is shown in the graph below, where IRB,UL can be read at a certain Lsa,cellrange.
The formula for UL noise rise, BIUL, is shown below. Fill in the result.
QUL (1   ) I RB ,UL
BIUL  10 log(1  ) Irb,ul -108
N RB ,UL Biul 11,7604
Where:
– IRB,UL is the average inter-cell
interference per RB (linear) -95
P 0= -119
P 0= -115
P 0= -111
-100
– IRB,UL can be obtained from UL

P 0= -107
P 0= -103
ring method. The result is -105

P 0= -99
P 0= -95
illustrated in the graph to the

IRB,UL [dBm]
right: -110
– β is the interference cancellation -115
efficiency factor due to IRC

-120
-125
-130
110 115 120 125 130 135 140 145 150
Lsa,cellrange [dB]
Figure 4-18: UL noise rise

3.4.4 UL resource block allocation

The calculation of the resource block allocation in UL tries to capture the link
adaptation behavior. It is a tradeoff between selecting the largest possible number
of RBs and maintaining the desired level of SINR (γ) per RB. The desired level
of SINR is here called γ0.
To allocate resource blocks so that γ < γ0 is not useful, since the achievable bit
rate will not increase. Resource blocks that are not allocated can be used by other
UEs to increase cell throughput.
The number of resource blocks allocated in UL (n’RB) is modeled by the formula

in the following slide. It calculates the maximum number of resource blocks
while still satisfying the γ0 requirement.
The number of resource blocks allocated will typically be equal to the maximum
number of resource blocks at low path losses. When the path loss increases, at a
certain point, where the UE cannot longer keep up the power per resource block,
the number of allocated RBs will drop, according to the exponential expression in
the formula until it reaches the minimum number.
( PUE  Lsa  N RB ,UL  BIUL  0 ) /10

n'RB  max( n'RB ,min ; min( n'RB ,max ;10 ))
Where:
# RBs reaching γ0
– n’RB,min and n’RB,max is the minimum
resp. maximum number of resource
blocks a UE can be allocated
– PUE is the max output power of a UE,
e.g. 23dBm
– Lsa is the signal attenuation between
UE and RBS ref point
– γ0 models the link adaptaion
behaviour at low SINR. Can be seen
as the min desired SINR at the RBS.
Recommended value shown below:
Channel model EPA5 EPA70 ETU300

γ0 [dB] for 1.4 MHz BW -2.0 2.8 2.0
γ0 [dB] for 10 MHz BW -4.0 -1.4 -1.4
Figure 4-19: UL resource block allocation

ChapterTitle
3.4.5 Power level

The power control setting influences the SINR per RB and therefore also the
number RBs allocated.
The UE power per resource block (PUE,RB) will either satisfy the power control
target (P0) or be limited by the maximum UE power (PUE).
If the UE power is sufficient for reaching the power control target at the RBS, the
UE power will be equal to the target plus the signal attenuation.
If the UE reaches its maximum power, the power per resource block becomes the
max UE power divided by the number of allocated resource blocks (in
logarithmic form PUE – 10log(n’RB)).
The calculated UE power is then subtracted by the signal attenuation to obtain the
received power (PRX,RB). The SINR (γ) is then calculated as this received power
minus the noise (NRB,UL) minus the interference margin (BIUL) (in logarithmic
form). See the following two pictures.
PUE , RB  min( PUE  10 log( n'RB ); P0  Lsa )
UE at max pwr PC target

reached
Where:
– α is set to 1 in the current release
PRX , RB  PUE , RB  Lsa

› The resulting SINR can be
calculated as:
  Prx, RB  N RB ,UL  BIUL

Figure 4-20: UL power level

The power control behavior is summarized in the graph below.
[dB, dBm]
20
γ0
SINR [dB]
-30 PUE,RB [dBm]
Prx,RB [dBm]
-80
P0
-130
Lsa [dB]
P0 is met max UE n’RB n’RBmin
power decreases reached
Figure 4-21. UL power levels.
3.4.6 UL bit rates

The bit rate is possible to calculate when the SINR is known. This is
accomplished by using the formula and parameters below. This formula is used
for all bit rate calculations, when the SINR is known. Note that different
parameters (a0-a4) are used for DL.
Note: always check the latest guideline for correct values!

ChapterTitle
R  n'RB RRB ( )

RRB    max 0, a3  (a0  a3 )e ln(2)[(  a1 ) / a2 ]
a4
;   a1
RRB ( )  a0 ;   a1
EPA 5
Max modulation: 16QAM 64QAM

a0 [kbps] 519.7 719.2
a1 [dB] 37.0 45.9
a2 [dB] 29.7 35.2
a3 [kbps] 0 0
a4 [kbps] 4 4
Figure 4-22: UL bit rates
BW=1,4 MHz EPA 5 EVA 70 ETU 300

Max modulation: 16QAM 64QAM 16QAM 64QAM 16QAM 64QAM
a0 [kbps] 529.2 717.4 528.6 711.2 379.0 394.6
a1 [dB] 35.3 43.4 23.8 28.8 21.5 22.1
a2 [dB] 28.2 33.2 12.5 14.5 12.2 12.4
a3 [kbps] 0 0 0 0 0 0
a4 [kbps] 4 4 2 2 2 2
All other BWs EPA 5 EVA 70 ETU 300

a0 [kbps] 519.7 719.2 519.7 718.2 388.3 400.7
a1 [dB] 37.0 45.9 37.4 47.8 32.2 33.0
a2 [dB] 29.7 35.2 27.8 34.5 24.7 25.2
a3 [kbps] 0 0 0 0 0 0
a4 [kbps] 4 4 4 4 4 4
Figure 4-23: Link Curve Coefficients for UL FDD & TDD, 1x2
The graph below illustrates the a0-a4 parameter behavior.

RRB
a1
RRB L2 bitrate [kbps]

 SINR [dB]
a0 a0, a1, a2 and a3 are fitted parameters
a2
(values depend on channel model)
a3

Figure 4-24. SINR to bit rate estimation.
3.4.7 Log-Normal Fading

A radio signal envelope is composed of a fast fading signal super-imposed on a
slow fading one.
The short term or fast fading (Rayleigh fading) signal (peak-to-peak distance 
/2) is usually present during radio communication, due to the fact that the
mobile antenna is lower than the surrounding structures, such as trees and
buildings which act as reflectors. The resulting signal consists of several waves
with various amplitudes and phases. Sometimes these almost completely cancel
out each other. The Rayleigh effect is proportional to the wavelength () and UE
speed. The SINR (γ) values used for LTE dimensioning include the effect of
Rayleigh fading.
Assuming that fast fading has been removed (averaged out), the local mean value
of the signal strength fluctuates in a way not modeled by the standard propagation
RF prediction algorithms. This fluctuation is log normally distributed about the
mean value with a standard deviation () which is typically between 6 and 10 dB
depending on the environment.
If outdoor base stations are used to provide indoor coverage then the standard
deviation in Building Penetration Loss (BPL) and signal strength inside the
building must be added. Typical values for this combined standard deviation ()
are between 10 and 14 dB depending on the environment.
The log-normal fading margin (BLNF) used in the link budget calculations will
depend on the standard deviation of the environment () and the required
coverage probability.
The standard deviations () for various environments and the log-normal margin
(BLNF) that should be used to achieve the required coverage probability is
illustrated in Figure 4-25.

ChapterTitle
3.4.8 UL cell edge bit rates

In order to estimate the cell edge bit rates, we first need to estimate the median
signal attenuation for cell edge users, Lsa,celledge. This is done by adding the log-
normal fading margin BLNF to the median signal attenuation at the cell border,
Lsa,cellrange. The log-normal fading margin in dB is tabled below for different
standard deviations, σ, of the fading. The standard deviation depends on the radio
environment (rural, suburban, urban, indoor, outdoor etc).
› Median signal attenuation at the

cell border, Lsa,celledge Blnf 4,9
Lsa,celledge 119,9
› Lsa,celledge = Lsa,cellrange + BLNF
Environment Std Coverage probability

dev
98% 95% 90% 85%
σ
[dB]
Rural, 6 5,5 2,9 0,5 -1,2

suburban
Urban 8 8,1 4,9 1,8 0,2
Log-normal Fading Margin, BLNF
Dense urban 10 10,6 6,7 3,1 0,6
and suburban
indoor  Indoor
Urban indoor 12 13,1 8,4 4,2 1,3 
Outdoor
Dense urban 14 15,3 9,9 5,1 1,8
indoor
Figure 4-25 UL cell edge bit rates.
The median signal attenuation for cell edge users is calculated and used in order
to calculate the median SINR at the cell edge, which in turn is used to estimate
the bit rate per resource block. The bit rate at the cell edge is calculated by
multiplying the rate per RB with the number of RBs allocated at the cell edge.
( PUE  Lsa ,celledge  N RB ,UL  BIUL  0 ) /10
n'RB ,celledge  max( n'RB ,min ; min( n'RB ,max ;10 ))
 celledge  min( PUE  10 log( n'RB ,celledge ); P0  Lsa,celledge )  Lsa,celledge  N RB ,UL  BIUL
Rcelledge  n'RB ,celledge RRB ( celledge )

Figure 4-26: UL cell edge bit rates
The high rate quality requirement is evaluated for a UE close to the site. The bit
rate close to the site depends to a large extent on the power control target. Here it
can be assumed that the maximum number of resource blocks is allocated and
that the SINR is given by:
 h  P0  N RB ,UL  BIUL
SINRh 1,886704
n'rb,h 97,4
Rh  n'RB ,max RRB ( h )
Rrb,h 113,4111
Rh 11046
The above is valid where the UE

can reach the power control target:
Lsa  PUE  10 log( n'RB ,max )  P0

Figure 4-27. UL high bite rates.
3.4.9 UL link budget

Lsa,cellrange is converted to air propagation loss, Lpmax
Lp max  Lsa,cellrange  LBL  LCPL  LBPL  GA  L j Lbl 3

Lbpl 18
Lcpl 0
Where: Ga 18,5
Lpmax is the max path loss in the air [dB] Lpmax 112,5
LBL is the body loss, e.g 3 dB
LCPL is the car penetration loss, e.g. 0 dB
LBPL is the building penetration loss, e.g 18 dB
Ga is the sum of the RBS and UE antenna gains )
ss (L pmax
Lj is the jumper loss ath lo
mp
imu
Max
Figure 4-28 UL link budget.
Sometimes it is more convenient to base the link budget on the RBS receiver
sensitivity.

ChapterTitle
3.4.9.1 eNodeB Receiver sensitivity (SeNodeB)
The eNodeB receiver sensitivity (SeNodeB) is defined as the minimum signal that is
required to decode the Uplink RB. This will depend on the thermal noise power
density (Nt), noise figure of the eNodeB (Nf), bandwidth of the RB (WRB) and the
SINR target requirement for the uplink RB (γtarget) as illustrated in Figure 4-29
below.
SeNodeB = Nt + Nf + 10log(WRB) + target [dBm]
eNodeB Receiver Sensitivity (SeNodeB)
SINR (target) dB
Bandwidth per Resource Block (WRB)
10log(WRB) = 52.55 dB
eNodeB Noise figure (Nf)
(2 dB)
Thermal Noise Power Density (Nt)

(-174 dBm/Hz)
eNodeB
Figure 4-29 eNodeB Receiver Sensitivity
The Thermal Noise Power Density (Nt) of -174 dBm/Hz illustrated in Figure 4-29
above is calculated from Boltzmann’s constant (K) and the absolute temperature
in Kelvin (T) as below:
Nt = 10log(KT/10-3) dBm/Hz
Where K = 1.38 ∙ 10-23 J/K and T = 290 (17o C)
=> Nt = 10log[(1.38 ∙ 10-23 ∙ 290)/10-3] = -173.98

= approximately -174 dBm/Hz

The eNodeB noise figure (Nf) is assumed to be 2 dB as illustrated in Figure 4-29.
The bandwidth per Resource Block (WRB) is 180,000 Hz

=> 10log(WRB) = 10log(180,000) = 52.55 dB as illustrated in Figure 4-29 above.
› When the eNodeB receiver sensitivity is used, the link

budget can be calculated as:
Lp max  PUE , RB  SeNodeB  BIUL  BLNF  LBL  LCPL  LBPL  Ga  L j
For the cell edge bit rate, assuming the UE uses max power,
the receiver sensitivity can be calculated as:
SeNodeB  PUE  Lsa,cellrange  BLNF  10 log( n'RB )  BIUL

Figure 4-30 Alternative link budget.
3.5 UL capacity calculation

The UL capacity is calculated for a given combination of iteration parameters;
Lsa,cellrange, P0 and QPUSCH.
The calculation involves the following three steps:
› Average RX power, PRX,RB,ave

› Average SINR, γave
› Cell throughput, Tcell,UL
1
2 Assume:
-PC target
4 -UL load
5
3
6
Done
Figure 4-31: Uplink capacity calculation
3.5.1 Average RX power

The average received power per resource block depends on the power control
target, Lsa,cellrange and P0 according to the following graph:

ChapterTitle
› PRX,RB,ave depends on the power control target, P0, and

Lsa,cellrange
› At low Lsa,cellrange , the PRX,RB,ave equals P0
›PRX,RB,ave can be
obtained from UL ring
method. The result is
PRX,RB,ave
illustrated in the following
graph:
Figure 4-32. UL average RX power.
The power control target, P0, reflects the target received power, which is
achieved when all UEs reach the target. This can be seen in the left part of the
graph (PRX,RB,ave = P0).
The UL average SINR can be calculated based on the average received power.
 ave  PRX , RX ,ave  N RB ,UL  BIUL Prx,rb,ave -106

SINRave 1,886704
Figure 4-33 UL average SINR.

The UL coverage calculation method is summarized in the following picture.
Lp max  Lsa,cellrange  BIUL  BLNF  LBL  LCPL  LBPL  GA  L j
Maximum path loss (Lpmax)
 Q I 
BIUL  10 log1  UL UL 
P  10 log nRB  N RB 
PUE  min  UE
 P0  Lsa
 nRB ,min SeNodeB  N t  Nf  10 log BW   target

 nRB ,max

nRB , celledge  max  
min 10 PUE  Lsa  N RB ,UL  BIUL  /10 N RB  N t  N f, eNodeB  10 log BW
 
 N f , RU L f  1 
 UE
P  10 log nRB , celledge  Lsa  N RB ,UL  BIUL N f, eNodeB  10 log  N f ,TMA  
 celledge  min   GTMA 
 P0  Lcelledge  Lsa  N RB ,UL  BIUL
  PRX  N RB,UL  BIUL
Rcelledge  nRB ,celledgeR  celledge 
 PRX  PUE, RB  Lsa
Figure 4-34: Uplink CoverageSummary
3.5.2 Cell throughput

The UL cell throughput is calculated based on average SINR.
RRB ,UL ,ave  RRB ( ave )

Tcell ,UL  QPUSCH nRB , PUSCH RRB ,UL ,ave
nRB , PUSCH  nRB  nRB , PUCCH  nRB , PRACH
2-4 0.6 (1.2 for cell range > 15 km)
where :
nRB , PUCCH  2,4,6...
nRB,PUCCH
nRB
nRB , PRACH  0.6

Available RBs
Figure 4-35: UL cell throughput

ChapterTitle
Finally, Lpmax is converted to a corresponding cell range, R, by using an Ericsson

specific variant of the Okumura-Hata model.
Urban: A= 157.5 dB, Suburban: A= 151.5 dB If hm = 1.5 m

2.6 GHz
Rural: A= 137.6 dB, Open: A= 127.5 dB => =0
Lp  A  13.82 log hb  44.9  6.55 log hb log R  3.2log 11.75hm   4.97

2
 L p max  A  13.82 log hb 

hb R  log 1  [km] cell range,
0,2005
max
 44.9  6.55 log hb  hm
Figure 4-36: Uplink Cell Range
3.5.3 Optimizing power control and PUSCH load

When the UL coverage and capacity has been calculated in iterations with
increasing site-to-site distance, and verified against the requirements, the
maximum site-to-site distance can be further increased by optimizing the power
control target and PUSCH load settings.
This is also the way the design process is performed when the site-to-site distance
is given (e.g. at co-siting LTE with other systems).
› As a last step, P0 and QPUSCH can be adjusted in order to

increase performance
› If UL cell edge bit rate is the bottleneck
– decrease P0 and/or QPUSCH
› If the UL capacity is the bottleneck
– increase P0 and/or QPUSCH
› If the UL high bit rate is the bottleneck
– increase P0 and/or decrease QPUSCH
Figure 4-37 Power control and PUSCH load

Note: In large parts of the cell, the UE will operate at the maximum power. Also,
for large cells, the cell edge UEs will typically be allocated the minimum number
of resource blocks. The noise rise will in that case depend on the PUSCH load.
By increasing PUSCH load level until the desired capacity is reached, the lowest
possible cell range can be found. For large cells, the noise rise is almost
independent of the power control target P0.
4 Downlink dimensioning
The downlink dimensioning uses the cell range result from the uplink
calculations. This is represented by the maximum path loss Lpmax.
› Downlink coverage and link budget

– Determine the limiting link
– Determine the DL bit rate at the cell edge calculated for UL
› Max path loss from UL, Lpmax
› Bit rate requirement, Rreq,DL
› Power per RB, Ptx,RB 1
› DL noise rise (interference margin), BIDL
2
› DL link budget, Lpmax UL Dimensioning
› RX sensitivity, SUE 3
DL Dimensioning
› Bit rate at cell edge, RRB 4

Control Channel
Coverage
Done
Figure 4-38: Downlink dimensioning
The path loss from UL is the starting point for DL calculations and also used to
obtain the DL noise rise estimate.
› Lpmax calculated from the uplink is used as starting point for

the downink calculations
› If the new DL Lpmax turns out to be less than UL Lpmax, both
UL and DL link budgets can be recalculated (including
noise rise) using the new Lpmax
Figure 4-39 Path loss from uplink.

ChapterTitle
4.1 DL Coverage
The bit rate requirement Rreq,DL is divided by nRB in order to obtain the required bit
rate per RB.
› DL transmissions should always use the maximum number

of resource blocks (e.g. nRB = 100 for 20 MHz system BW)
› Rreq,RB,DL = Rreq,DL/nRB
(for BW=1.4 MHz, only 90% of the this rate is achieved, because the fraction of used subframes,
ksubf,DL is 0.9)
› Rreq,RB,DL is compared with the DL cell edge bit rate (cell

edge defined by UL calculations)
Figure 4-40: DL Bit rate
In the DL, it is assumed that all RBs are used and allocated an equal amount of
power. The power per resource block at the tx system reference point is
calculated according to:
› The DL power is shared equally

by all resource blocks
Ptx, RB  10 log( Pnom,ref )  L f  10 log( nRB )
Where:
Pnom,ref is the sum of nominal power from all
radio units in a cell. Typical values are 20, 40
and 60W. With MIMO the values may be
doubled
Lf is the feeder loss in dB
Figure 4-41 DL power per resource block.

4.1.1 Downlink System Reference Point

The losses between the antenna and system reference point depend on whether an
ASC is used or not as illustrated in figure below.
i]
UE Antenna Gain [dB
(GUE) [dBi] ode X
+ Ge
N eNodeB Antenna
X
= GU
E Gain (GeNodeB) [dBi]
Ga X
Antenna Jumper loss (LJ) [dB]
Reference point with ASC

ASC ASC insertion loss (LASC) [dB]
Feeder loss Jumper & Connector

(LF) [dB] losses (LJ+C) [dB]
Reference point without ASC
eNodeB
Figure 4-42: Downlink System Reference Point
When the ASC is used its output is taken as the reference point meaning that only
the Antenna Jumper loss (LJA) needs to be included in link budget calculations as
illustrated in figure above.
If an ASC is not used the top of the eNodeB is taken as the reference point and
the ASC insertion loss (LASC), Feeder loss (LF) and all Jumper and Connector
losses between the ASC and eNodeB (LJ+C) must be included in link budget
calculations.
In the case where the eNodeB uses a Remote Radio Unit (RRU) fiber optical
cables are used instead of RF feeder, jumper and connectors so no feeder and
jumpers losses need to be included in link budget calculations.
The antenna gain (Ga) is the sum of the UE and eNodeB antenna gains (GUE +
GeNodeB) as illustrated in figure above.

ChapterTitle
4.1.2 DL noise rise at cell edge

In order to be able to calculate the DL link budget, the DL noise rise at the cell
edge, BIDL,celledge is needed. The control channel interference load depends on if
the network has time synchronized cells or not.
DL noise rise is calculated as (all quantities linear):

Ptx , RB Fc (QCCH  (1  QCCH )QPDSCH )
BIDL ,celledge  1 
N RB , DL Lsa,celledge
QPDSCH is the fraction of PDSCH RBs carrying user data

QCCH is the interference caused by control channels (see table below)
Fc is the average ratio between received power from other cells to that of own cells at the cell edge
NRB,DL is the thermal noise per RB. NRB,DL = Nt + Nf + 10log(WRB)
Nf is the UE noise figure, typically 7dB
BW 1.4MHz 3MHz 5MHz 10MHz 15MHz 20MHz
QCCH 23.2% 17.1% 16.5% 16.1% 12.0% 11.8%

(Non-sync NW)
QCCH 9.7% 8.3% 8.3% 8.3% 7.7% 7.7%

(Non-sync NW)
Figure 4-43: DL noise rise at the cell edge
The factor Fc is the ratio between received power from all other cells to that
received from own cell at a location near the cell edge. The table below shows Fc
for different electric tilt angles for 3-sector sites.
Cell radius 5000m 2000m 1000m 500m Fc

0.0 0.0 0.0 0.0 2.8
0.2 0.5 1.0 2.0 2.7
0.4 1.0 2.0 4.0 2.5
0.6 1.5 3.0 6.0 2.3
Tilt angle 0.8 2.0 4.0 8.0 2.1
1.0 2.5 5.0 9.9 1.8
1.2 3.0 6.0 11.9 1.6
1.4 3.5 7.0 13.8 1.5
1.6 4.0 8.0 15.7 1.4
Figure 4-44 Table for Fc.

QCCH is an estimation of the interference on the payload from the control

channels. It is the fraction of the PDSCH REs that will be interfered by control
channels from typical (averaged) 2-antenna port neighbors. The actual figure is a
weighted average of in-sync and out-of-sync neighbors. Intra site neighbors are
typically in-sync, while inter-site neighbors can be out-of-sync or randomly and
partially in-sync. The interference from the control channels is at its minimum
when the neighbors are synchronized and at its maximum when they are
completely un-synchronized.
The DL cell edge SINR can be derived by solving equations for UE receiver
sensitivity and DL link budget. The resulting formula is shown in the figure
below.
Lpmax = Ptx,RB – SUE – BIDL – BLNF – LBL – LCPL – LBPL + Ga – LJ
SUE = Nt + Nf + 10log(WRB) + 
Pnom,ref [mW]
10log nRB [dBm]
 = Ptx,RB - Lpmax - Nt - Nf - 10log(WRB) - BIDL - BLNF - LBL - LCPL - LBPL + Ga - LJ [dB]
From Uplink
Link budget
calculation
[dB]
Figure 4-45 Downlink cell edge bit rate.
We assume that the most efficient Modulation and Coding Scheme (MCS) is
always used. This perfect selection mechanism is modeled by the Signal to
Interference and Noise Ratio, SINR versus bit rate (R) relationships, using the a0,
a1, a2, a3 and a4 parameters.
Note: Always check the latest guideline for correct values.

ChapterTitle
The resulting DL cell edge bit rate is calculated from the SINR as shown in the
figure below.
  Ptx , RB  L p max  N RB , DL  B IDL,celledge  BLNF  LBL  LCPL  LBPL  Ga  L j

RRB , DL  RRB ( )
R  RRB , DL nRB k subf , DL

RRB    max 0, a3  (a0  a3 )e  ln(2)[(  a1 ) / a2 ] ;
a4
   a1
RRB ( )  a0 ;   a1
The rate is calculated using the following

parameters (valid for OLSM 2x2): a0 and a3 adjusted with regards to
control channel configuration:
Channel EPA5 EVA70 ETU300
model
 n n 48  nant 
a0  a0,max  1  PDCCH  CRS  
a0,max [kbps] 1489,2 1352,6 1080,6
 14 168 140  nRB 
a1 [dB] 56,8 59,4 54
 n n 48  nant 
a2 [dB] 41 42,4 38,9 a3  a3,max  1  PDCCH  CRS  
 14 168 140  nRB 
a3,max [kbps] 0 0 0
a4 4 4 4 nCRS  number of cell specific reference signals
(6 for one DL antenna port, 12 for two ports)
A complete list can be found in the Coverage nPDCCH  number of allocated symbols for PDCCH
and Capacity Dimensioning CPI nRB  total number of RBs
k subf , DL  Fraction of used subframes, 0.9 for 1.4MHz,

1 for all other BWs
Figure 4-46: DL bit rate at cell edge
The DL cell edge bit rate is compared to the quality requirements.
The DL coverage calculation method is summarized below.
Lp max  Lsa,cellrange  BIUL  BLNF  LBL  LCPL  LBPL  GA  L j

SUe  N t  Nf  10logBW  γ Ptx, RB  10 logPnom,ref   L j  10 lognRB 
γ  Ptx,RB  L pmax  N RB,DL  BIDL, celledge  BLNF  L BL  LCPL  L BPL  G a  L j

R RB,DL,celledge  R RB γ 
Figure 4-47 Downlink CoverageSummary

› If the DL rate is higher than the required rate, UL is the limiting link.
– Link budget concluded.
› If the DL rate is lower than the required rate, DL is the limiting link
› If DL is the bottleneck, the true max cell range must be determined by
backtracking the DL link budget:
– RRB,req is transformed into required SINR (γreq), using the a0-a4 parameters
– γreq is used to derive SUE at cell edge
– SUE is used in the link budget, using same BIDL,celledge
– A new Lsa,cellrange is derived
– A new BIDL,celledge is derived
– Iterate until Lsa,cellrange and BIDL are constant
– The new Lsa,cellrange is converted to Lpmax, which reflects the true cell range
Figure 4-48 Concluding the DL link budget
The following figures show the principle to use when the DL is the limiting link
and the link budget is backtracked.
The γreq can be solved from this equation:

RRB    max 0, a3  (a0  a3 )e  ln(2)[(  a1 ) / a2 ] ;
a4
   a1
RRB ( )  a0 ;   a1
The result is:
1 / a4
 a a 
 req  a1  a2  ln( 0 3 ) / ln 2  ; 0  RRB  a0
 R 
 RB , req  a3 
Figure 4-49 Backtracking DL link budget
The SINR requirement is used in order to derive the UE sensitivity.
› SUE is the required power at the UE reference point in order to

achieve a certain bit rate in the absence of inter cell interference
SUE  Nt  N f ,UE  10 log(WRB )   req  N RB , DL   req [dB]

Figure 4-50 UE receiver sensitivity.

ChapterTitle
The UE sensitivity is used in the link budget, initially with the same BIDL,celledge as
before. A new signal attenuation Lpmax,DL is derived.
Lp max,DL  Ptx, RB  SUE  BIDL ,celledge  BLNF  LBL  LCPL  LBPL  Ga  L j [dB]
Where:
Ptx,RB is the TX power per RB at the system reference point
SUE is the UE sensitivity in dBm
Figure 4-51 DL link budget.
A new Lsa,cellrange is derived:
Lsa,cellrange  Lp max  LBL  LCPL  LBPL  Ga  L j [dB]
Where:
Lpmax is from UL calculations
A new noise rise is calculated, using

Iteration until Lsa,cellrange and BIDL,celledge are constant

The new Lsa,cellrange is converted to Lpmax, which yields the new
true cell range
Figure 4-52 DL signal attenuation.
A DL limited system means that the UL quality exceeds the requirement. But if
the UL also is needed to report, the UL link budget also needs to be backtracked.
Then the Lsa,cellrange from the DL calculations are used as input for the new UL
calculations.

4.2 Downlink capacity

The DL capacity dimensioning includes SINR and cell throughput calculations.
› Average SINR, γDL,ave

› Cell throughput, Tcell,DL
nRB
DL,ave => RRB,DL,ave
Figure 4-53 DL capacity.
In order to be able to calculate the DL average SINR, we first need the average
noise rise, BIDL,ave. The calculation includes the F-factor, which is the average ratio
of path gains for interfering cells to those of the serving cell. The formula for the
noise rise and the F-table is shown in the figure below.
Ptx , RB F (QCCH  (1  QCCH )QPDSCH )

BIDL ,ave  1 
N RB , DL Lsa,cellrange
Where:
F is the average ratio of path gains for
interfering cells to those of serving cell
Cell radius 5000m 2000m 1000m 500m F
0.0 0.0 0.0 0.0 1.1
0.2 0.5 1.0 2.0 0.9
0.4 1.0 2.0 4.0 0.8
0.6 1.5 3.0 6.0 0.7
Tilt angle 0.8 2.0 4.0 8.0 0.7
1.0 2.5 5.0 9.9 0.6
1.2 3.0 6.0 11.9 0.5
1.4 3.5 7.0 13.8 0.4
1.6 4.0 8.0 15.7 0.4
Figure 4-54 DL average noise rise.

ChapterTitle
The average SINR is calculated using the following formula.
Ptx, RB
 DL ,ave 
BIDL ,ave N RB , DL HLsa,cellrange
Where:
H is the average attenuation factor.
Recommended value is 0.36
Figure 4-55: DL average SINR
When the average SINR is derived, the rate per resource block can be calculated
by using the a0-a4 parameters. Then the cell throughput is simply calculated by
multiplying with the number of resource blocks allocated and the average DL
load.
› RRB,DL = RRB(γ)
› Rave,DL = nRBRRB,DLksubf,DL
› Tcell,DL = QPDSCHRave,DL
Figure 4-56: DL cell throughput
5 Downlink control channel coverage

It should be verified that the control channel performance at the cell edge is not
limiting the cell edge bit rates.
The DL control channels to be checked include PCFICH and PDCCH.
Since PCFICH and PDCCH are time-multiplexed with PDSCH, the SINR at the
cell edge for the control channels can be assumed to be equal to the DL cell edge
SINR as calculated before.

In a non time synchronized network, the PDCCH is interfered by both PDSCH

and control channels in other cells. Therefore, the same calculation as before
(SINR at cell edge) can be used for the control channels.
› The SINR for PCFICH and PDCCH should not limit the cell edge
bit rates and should fulfill the following requirements:
1
SINR [dB] SIMO 1x2 Tx Div 2x2
2
UL Dimensioning
BW EPA5 EVA70 ETU300 EPA5 EVA70 ETU300
>3 MHZ -4.5 -5.5 -4.5 -6 -6.5 -5.5 3
DL Dimensioning
≤3MHz -1.5 -3 -2 -3.5 -4 -3
4
Control Channel
Coverage
Done
› If the SINR is slightly less than the tabled values, the throughput
at cell edges will degrade gracefully
› If the SINR is substantially lower, the site-site distance need to be
decreased
Figure 4-57: DL control channel coverage Non time synchronized Network
Next slide shows the method in case of a time synchronized network.
In a time synchronized network, PDCCH is only

interfered by control channels in other cells and the
noise rise is calculated as:
Ptx , RB Fc QPDCCH
BIDL,celledge, PDCCH  1
N RB , DL Lsa ,celledge
Where:
QPDCCH is the PDCCH load. 100% corresponds to a fully
loaded PDCCH
The result is used as input instead of

BIDL,celledge in the SINR calculation in DL bit
rate at cell edge
Figure 4-58: DL control channel coverage Time synchronized network

ChapterTitle
6 Uplink control channel coverage

The ACK/NACK transmitted on PUCCH may limit the DL cell edge throughput,
if correct dimensioning is not performed.
› Unsuccessful ACK/NACK signaling on PUCCH may degrade DL cell

edge throughput
› PUCCH power control is defined by:
P0, PUCCH  pZeroNo min alPucch  10 log( nant )
Where:
pZeroNominalPucch is by default set to -117 dBm/RB
› The SINR for PUCCH can be calculated as:
 PUCCH , A / N  min( P0, pucch; PUE  Lsa,celledge )  10 log(10 N  QPUCCH , A / N (  F ) *10

RB ,UL / 10 P0 , pucch /10
)
Where:
QPUCCH,A/N is the number of simultaneously ACK/NACK. Recommended value is 2.
μ is the non-orthogonality factor. Recommended value is 0.2
Figure 4-59 UL control channel coverage.
The SINR for the PUCCH ACK/NACK should fulfill the following
requirements:
› In order not to degrade DL cell edge bit rates, the SINR for
PUCCH should exceed:
SINR [dB] EPA5 EVA70 ETU300
SINR for PUCCH ACK/NACK -8 -8 -7.5
› If the SINR is slightly less than the tabled values, the throughput
at cell edges will degrade gracefully
› If the SINR is substantially lower, the site-site distance need to be
decreased
P0,pucch -120,01
SINRpucch,A/N -2,5908
Figure 4-60 UL control channel coverage.

7 Ring methods
7.1 DL ring method

An alternative method of calculating cell throughput is using a ring method. The
method averages the throughput from several thin cell “rings”. In a ring, the
SINR and path loss is considered constant.
› A method to estimate the throughput vs pathloss

› Includes the following stages:
– Signal attenuation for each ring, Lsa,i
– Calculation of equivalent tilt angle, θeq
– SINR for each ring, γi
– Average cell throughput, Tcell,DL
– Throughput for each ring, Ti,RB,DL
Figure 4-61 DL ring method.
The cell area is modeled as a hexagon and divided into a large number of thin cell
rings. In each ring the radio characteristics, like path loss, SINR, data rate are
considered equal.
› Area is divided into N hexagon

rings with area = di2-d2i-1
› Signal attenuation everywhere in
each ring assumed to be equal
› Lpmax from UL or Dl coverage
calculation is used at the cell dmax= R
border di
› Signal attenuation in each ring is di-1
calculated as:
Lsa,i  Lsa,cellrange  10m log10 (di / d max ) [dB]
Where:
m is the path loss exponent, typically 3.5
Fi
Figure 4-62 Cell rings.

ChapterTitle
The F value for each ring can be corrected due to the different geometrics when
the ring diameter changes. Therefore, an equivalent tilt angle is introduced.
However, it can be shown that using the F values directly from the 5 degrees
column in the F table gives appropriate results. So the equivalent tilt angle is not
used here.
› An equivalent tilt angle, θeq can be used to select the appropriate F

value in each ring
› This is because the values in the F-table is based on a cell range of
1000m and an antenna height of 30m
dmax
d 30
 eq   max Ant tilt eq 2,3445
θeq
1000 hb 1000m
θ
Note: In this release we
use 5˚ tilt angle directly 30m
from the F-table instead

of equivalent tilt
Figure 4-63: Equivalent tilt angle
The following table provides F values for a cell range of 1000 meters and antenna
height of 30 meters:


ChapterTitle
The SINR for each cell ring is calculated according to the following:
1
i 
(QCCH  (1  QCCH )QPDSCH ) Fi  ( N RB , DL Lsa,i ) / Ptx, RB
Where:
Ptx,RB is the tx power at the system reference point
QPDSCH is the PDSCH load
QCCH is the load due to control channels
Fi is the F value in ring i
NRB,DL is the thermal noise per resource block in DL
Figure 4-64 SINR in each ring.
The SINR is used as input to the rate calculations for each ring. Then an
averaging is performed, where the proportion of users in each ring is included, in
order to derive the average rate in the cell. The total cell throughput is derived by
multiplying with the DL load factor.
› Bit rates in each ring is calculated according to:

RRB    max 0, a3  (a0  a3 )e  ln(2)[(  a1 ) / a2 ] ;
2
   a1
RRB ( )  a0 ;   a1
› The proportion of users in each ring is:

d i2  d i21
puser,i  2
d max
› The average rate in each ring is:

Ravg, DL   puser,iTi , RB , DL
i
› The cell throughput is:

Tcell , DL  QPDSCH Ravg, DL
Figure 4-65: DL bit rates, ring method

7.2 UL ring method

In order to perform accurate calculations of cell throughput, noise rise and user
throughput distributions, a ring method can be used also for the uplink. The
approach is very similar to the one used for downlink.
› A similar ring method as for DL can be used in UL

› In each ring, the following is calculated
– the number of supported resource blocks, n’RB
– SINR, γ
– bit rate, RRB
– generated interference, BIUL
Figure 4-66 UL ring method.
In case of traffic growth scenarios, a new dimensioning process with iterations

can be performed, in order to find new parameter settings and/or new site-to-site
distances for the quality requirements to be fulfilled. The placement of sites may
then be reconsidered.
8 TDD Dimensioning
TDD is based on a single frequency that is shared in uplink and downlink by time
division multiplex. Although several differences exist between TDD and FDD,
the radio interface is based on OFDMA in the downlink and SC-FDMA in the
uplink. TDD performance is approximated based on the FDD model.
For coverage calculations, the modeling described for FDD for uplink and for
FDD downlink applies. However the TDD bit rate requirements for uplink and
downlink must be transformed to equivalent bit rates that take the silent periods
into account:

ChapterTitle
› Same methods for UL and DL as for FDD

› TDD bit rate requirement, Rreq,TDD must be transformed to equivalent
rates that take the silent periods into account:
Rreq,TDD ,UL
Rreq,UL 
k subf ,UL
Rreq,TDD, DL
Rreq, DL 
k subf , DL  (k subf , ss  nsymb, DL / 14)
Where:
ksubf,DL is the proportion of subframes used for DL
ksubf,UL is the proportion of subframes used for UL
ksubf,ss is the proportion of subframes used for special subframes
nsymb,DL is the number of DL symbols in special subframes
Figure 4-67 TDD Coverage
The TDD system capacity scales as described in the figure below.
› Same methods for UL and DL as for FDD

› The throughput is then scaled as:
TTDD,UL  TFDD ,UL  ksubf ,UL

TTDD, DL  TFDD , DL  (ksubf , DL  (ksubf ,ss  nsymb, DL / 14)
Where:
ksubf,DL is the proportion of subframes used for DL
ksubf,UL is the proportion of subframes used for UL
ksubf,ss is the proportion of subframes used for special subframes
nsymb,DL is the number of DL symbols in special subframes
Figure 4-68 TDD Capacity
The TDD UL/DL configurations are shown below.

UL/DL ksubf,DL ksubf,UL ksubf,ss

configuration
0 0.2 0.6 0.2
1 0.4 0.4 0.2
2 0.6 0.2 0.2
3 0.6 0.3 0.1
4 0.7 0.2 0.1
5 0.8 0.1 0.1
6 0.3 0.5 0.2
SS conf 0 1 2 3 4 5 6 7 8
3:10:1 9:4:1 10:3:1 11:2:1 12:2:1 3:9:2 9:3:2 10:2:2 11:1:2
nsymb,DL 0 9 10 11 12 0 9 10 11
Figure 4-69 TDD UL/DL configurations
The a0 and a3 parameters have to be adjusted according to the figure below.
› In TDD DL, the a0 and a3 parameters have to be adjusted
 nPDCCH (k subf , DL  k subf , ss ) k subf , DL (nCRS  nUERS )  k subf , ss (nCRS , ss  nUERS , ss ) nPBCH  nPSS / SSS  nBF ,loss 
a0  a0,max  1    
 14 ksubf , DL  nsymb, DL k subf , ss 12(14k subf , DL  nsymb, DL k subf , ss ) 120nRB (14k subf , DL  nsymb, DL k subf , ss 
 nPDCCH (k subf , DL  k subf , ss ) k subf , DL (nCRS  nUERS )  k subf , ss (nCRS , ss  nUERS , ss ) nPBCH  nPSS / SSS  nBF ,loss 
a3  a3,max  1    
 14 ksubf , DL  nsymb, DL k subf , ss 12(14k subf , DL  nsymb, DL k subf , ss ) 120nRB (14k subf , DL  nsymb, DL k subf , ss 
 nlim,RB (168  12n pdcch  nCRS  nUERS ) ; TM 7


nBF ,loss  2nlim,RB (168  12nsymb, DL  24(nPDCCH  1)nCRS  nCRS , ss ) ; TM 8

 0 ; otherwise
Where:
nCRS is the number of cell specific reference signals per RB nCRS,ss is the number of cell specific RS in special subframes per RB
ksubf,UL is the proportion of subframes used for UL nUERS is the number of UE specific RS per RB
ksubf,ss is the proportion of subframes used for special subframes nUERS,ss is the number of UE specific RS in special subframes per RB
nsymb,DL is the number of DL symbols in special subframes nPBCH is the amount of resources lost due to PBCH
nPSS/SSS is the amount of resources lost due to sync signals
nlim,RB is the number of RBs not used for PDSCH
Figure 4-70: TDD bitrate calculations
The variables needed for the above conversion are shown below.

ChapterTitle
Antenna Configuration nCRS nCRS,ss

Special Subframe Configuration 5 Special Subframe Configuration 6 & 7
nant,DL = 1 6 0 4
nant,DL = 2 12 0 8
nant,DL = 4 and nPDCCH = 1 20 0 16
nant,DL = 4 and nPDCCH > 1 16 0 12
Special Subframe nUERS,ss

Configuration
TM7 TM8 All other TMs

5 0 0 0
6 6 12 0
7 9 12 0
Bandwidth [MHz] nlim,RB
5 8
10 9
15,20 12
Figure 4-71: Variables
a0,max [kbps] 1229.2 880.5 530.5

a1 [dB] 52.4 55.1 43.9
a2 [dB] 36.5 38.7 32.1
a3,max [kbps] 0 0 0
a4[kbps] 4 4 4
a0,max [kbps] 1380.7 1018.1 623.3

a1 [dB] 54.6 53 41.5
a2 [dB] 39.1 38.3 31.2
a3,max [kbps] 0 0 0
a4[kbps] 4 4 4
Figure 4-72: Link curve coefficients for DL TDD 2x2 OLSM


a0 [kbps] 529.2 717.4 528.6 711.2 379.0 394.6
a1 [dB] 35.3 43.4 23.8 28.8 21.5 22.1
a2 [dB] 28.2 33.2 12.5 14.5 12.2 12.4
a3 [kbps] 0 0 0 0 0 0
a4 [kbps] 4 4 2 2 2 2

a0 [kbps] 519.7 719.2 519.7 718.2 388.3 400.7
a1 [dB] 37.0 45.9 37.4 47.8 32.2 33.0
a2 [dB] 29.7 35.2 27.8 34.5 24.7 25.2
a3 [kbps] 0 0 0 0 0 0
a4 [kbps] 4 4 4 4 4 4
Figure 4-73: Link Curve Coefficients for UL TDD, 1x2
9 Additional features impacting coverage and

capacity
9.1 Minimum Rate Proportional Fair scheduling

In favorable conditions (with many users per cell and a low time dispersive radio
channel ),Minimum Rate Proportional Fair scheduling improves the cell capacity.
Throughput gains of 20-30% (compared to Resource Fair algorithm) can be
achieved, while still maintaining the cell edge user throughput.
9.2 UL Frequency-Selective Scheduling

UL frequency Selective Scheduling improves both coverage and capacity. The
coverage can be extended up to 2dB in favorable conditions. The capacity gain in
UL throughput can be up to 50%, while maintaining the same cell edge coverage,
compared to the Resource Fair algorithm.
9.3 DL Frequency Selective Scheduling

DL Frequency Selective Scheduling can, in favorable conditions, increase the DL
capacity up to 30%, while maintaining the same cell edge coverage, compared to
Resource Fair algorithm.

ChapterTitle
9.4 Antenna Integrated Radio (AIR)

AIR consists of two RUs integrated with an antenna. Compared to an equivalent
RRU of the same power class and same antenna for factor, the UL and DL
performance are improved.
 The RBS noise figure is reduced by 1.2 dB.
 The jumper loss is zero.
 The antenna gain is increased 0.3 dB.
Compared to an RRU configuration with jumper loss of 0.5 dB, AIR will
improve the UL sensitivity by 2 dB and increase the DL tx power with 0.8 dB.
› Minimum rate Proportional Fair

– Capacity gain of up to 20-30% with same coverage
› UL Frequency Selective Scheduling
– Capacity gain of up to 50% with same coverage or
– 2 dB better coverage with same capacity
› DL Frequency Selective Scheduling
– Capacity gain up to 30% with same coverage
› Carrier Aggregation
– Capacity increased in proportion to increased spectrum (UL &DL)
› AIR
– RBS NF reduced by 1.2 dB
– Antenna gain + 0.3 dB
Figure 4-74: Features impacting capacity and coverage

10 Control Channel Dimensioning

The control channels (PCFICH, PHICH, PDCCH and PBCH for DL and PUCCH
for UL) and the Physical Signals (RS, PSS and SSS for DL and DMRS for UL)
consumes a certain part of the available physical resources (REs and power). The
remaining resources can be used for the user data and L3 signaling on PDSCH
and PUSCH.
In order to be able to calculate the amount of resources consumed by the control

channels in DL the following figure can be helpful:
Subcarrier
Time
Subframe 1-4, 6-9
index
Subframe 0 Subframe 5
Frequency
288
: : :
180
: : :
168
: : :
Details of colors
PDSCH, UE0
PDCCH
PHICH
PCFICH
108 PBCH
: : : SSS
PSS
RS
Not Used
0 0 6 7 13 0 6 7 13 0 6 7 13
Figure 4-75. DL resource grid, 5 MHz.
Here we see each RE and what it is used for. Some REs are left unused as
indicated by black color in Figure 4-75.
Note that unused PDCCH resources are not shown in black. The amount of
unused PDCCH resources is instead indicated later in this chapter.

ChapterTitle
10.1 Physical Signals

The physical signals in DL consist of Reference Signal (RS) and Primary and
Secondary Synchronization Signal (PSS and SSS).
The RS consists of reference symbols, which each occupies one Resource

Element (RE). There are 8 reference symbols per scheduling block (12
subcarriers and 14 OFDM symbols) per antenna port (when one or two antenna
ports are configured).
The PSS and SSS uses the 72 centre subcarriers in OFDM symbol 6 and 5
respectively in the first slot of subframe 0 and 5. However, there are five
subcarriers reserved for future use on each end of the 72 subcarriers. This makes
62 subcarriers available for PSS and SSS. In each radio frame, 124 subcarriers
will be used for PSS and 124 subcarriers will be used for SSS.
10.2 DL control channels

PBCH uses the 72 centre subcarriers of the first subframe, second slot in OFDM
symbols 0, 1, 2 and 3. the number of Res used by PBCH is always 240 per radio
frame, independent of bandwidth and number of configured antenna ports.
PCFICH is always mapped onto four REGs in OFDM symbol 0, each carrying
four modulation symbols. These four REGs are spread over the system
bandwidth in order to achieve frequency diversity. Thus, 160 REs are used by
PCFICH every radio frame.
PHICH carries the Hybrid ARQ ACK/NACK. Each UE has an individual PHICH
assigned. Similar to PCFICH, PHICH is mapped in Resource Element Groups
(REGs) in OFDM symbol 0 spread across the whole system bandwidth.
The figure below shows the number of resource elements per frame used for
PHICH for the different system bandwidths.

BW [MHz] #RBs nRE,PHICH

1.4 6 120
3 15 240
5 25 480
10 50 840
15 75 1200
20 100 1560
Figure 4-76: Number of Resource Elements used by PHICH in one frame
PDCCH is transmitted in the beginning of each downlink subframe in REs not

used for reference signals, PHICH or PCFICH.
Mapping the PDCCHs to REs is based on CCEs. The number of CCEs required
for a certain PDCCH depends on the PDCCH message size and on the channel
coding rate. It is restricted to four different aggregation levels, 1, 2, 4 or 8 CCEs
per PDCCH.
The number of OFDM symbols available for PDCCHs in a subframe is equal to

CFI, except for 1.4 MHz bandwidth where it is equal to CFI +1.
CFI can vary between subframes to match the estimated demand of PDCCH in
the subframe. The maximum number of OFDM symbols, limited by the
parameter pdcchCfiMode, is not exceeded. See the following table.
pdcchCfiMode Description
CFI_STATIC_BY_BW Control region uses only CFI=1 for 15 and 20 MHz system
bandwidth, and uses only CFI=2 otherwise, which
corresponds to the hard coded setting in previous
releases.
CFI_STATIC_1 PDCCH uses only CFI=1
CFI_AUTO_MAXIMUM_2 PDCCH dynamically adapts CFI up to the value of 2,

depending on the actual load in each subframe
CFI_AUTO_MAXIMUM_3 PDCCH dynamically adapts CFI up to the value of 3,
depending on the actual load in each subframe
Figure 4-77: Setting of pdcchCfiMode

ChapterTitle
To secure a sufficient amount of CCEs to transmit PDCCH for common channel

messages, CFI_STATIC_1 is not allowed for bandwidths less than 10 MHz.
However CFI=1 can be used in some subframes with pdcchCfiMode set to
CFI_AUTO_MAXIMUM_2 or CFI_AUTO_MAXIMUM_3 at low PDCCH
demand.
To handle peaks of PDCCH load it is recommended for bandwidth of 10 MHz or

less to set pdcchCfiMode to CFI_AUTO_MAXIMUM_3.
For bandwidths larger than 10 MHz CFI_AUTO_MAXIMUM_2 is recommended

as pdcchCfiMode can increase the number of RB pairs allocated to PUCCH.
An increase in the number of RBs pairs allocated to PUCCH leads to a reduced

uplink peak rate.
The number of CCEs available for PDCCH depends on CFI, the bandwidth, and
the amount of resources occupied by PHICH and PCFICH. In many cases not all
CCEs are assigned to a PDCCH. Unused CCEs are part of the interleaving and
mapping process in the same way as any other CCE.
The following table shows the maximum number of REs, nRE,PDCCH used by
PDCCH in one frame, including holes associated with unused CCEs for each
setting of pdcchCfiMode:
nRE,PDCCH Bandwidth [MHz]
pdcchCfiMode 1.4 3 5 10 15 20
CFI_STATIC_BY_BW 1440 2520 4320 9000 4320 6120
CFI_STATIC_1 N/A N/A N/A 2880 4320 6120
CFI_STATIC_2 1440 2520 4320 9000 13320 18000

CFI_AUTO_MAXIMUM_2
CFI_STATIC_3 2160 4320 7200 14760 22320 30240

CFI_AUTO_MAXIMUM_3
Figure 4-78: Max number of Resource Elements for PDCCH per radio frame
The number of CCEs in a subframe can be calculated by dividing the number of

REs in the table above by 360.
An example of calculation of the resource usage is shown below:
In a 10 MHz system bandwidth, there are 12∙14∙50∙10 = 84000 resource elements

per radio frame.
The resource consumption for the control channels can be calculated for 10 MHz
and one antenna port and CFI = 2 as follows:
RS: 8 Reference Symbols per scheduling block => 8/168=4.76%

PSS: 62∙2 PSS resource elements per radio frame 124/(168∙10∙50) = 0.15%
SSC: same as PSS = 0.15%
PBCH: 240/(168∙10∙50) = 0.29%
PCFICH: 160/(168∙10∙50) = 0.2%
PHICH: 840/(168∙10∙50) = 1%
PDCCH: 9000/(168∙10∙50) = 10.7%
Total Control Channel: 17.2%
Normally, some REGs per subframe are left unused. This is because the unused
REGs are too few to form a complete CCE. The unused REGs are interleaved and
mapped in the same way as the REGs grouped in a CCE. The following table
shows the total number of REs nRE,UN in unused REGs for different bandwidth:
nRE,UN nRE,UN nRE,UN

BW [MHz] #RBs For CFI=1 For CFI=2 For CFI=3
1.4 6 - 200 200
3 15 - 80 80
5 25 - 40 160
10 50 120 0 240
15 75 320 320 320
20 100 160 280 40
Figure 4-79: Number of Resource Elements not used in control region per frame
An example of calculation of unused REs per frame for 10 MHz system

bandwidth using CFI = 2 and one antenna port is shown below:
5 unused RE on each side of PSS and SSS => (5+5)∙4
0 unused RE per frame for PDCCH.
48 REs are always reserved for RS (or corresponding holes) in the PBCH region
(as if it was four antenna ports). 12 of these used for actual RS per antenna port
when one antenna port is used, i.e. 36 unused REs.

ChapterTitle
In the control region, there are 2 REs per RB “reserved” for RS as if two antenna
ports where used. This equals 2∙50 = 100 unused REs per subframe at 10MHz
system bandwidth.
Total unused REs:
(5+5)∙4/(168∙10∙50) + 0/(168∙10∙50) + 36/(168∙10∙50) + 100∙10/84000 = 1.29%
Total control channel and non-used resources equals 18.5%. This leaves 81.5%
for PDSCH.
Fill in the above calculations in below.
PSS
and Total
Unused RS PBCH PCFICH PHICH PDCCH PDSCH
SSS Ctrl Ch
1000  40
84000
Calculation
0  36

84000
%
1.3
Figure 4-80: Resource consumption for control channels and PDSCH,

BW=10MHz, CFI=2, 1 AP
When two antenna ports are configured, the unused REs due to RSs equals 8/168.
12 more REs are used for actual RS in the PBCH area. This gives us 24 unused
RE in the PBCH area.
This results in a loss of:
8/168 + 24/84000 + 40/84000 + 0/84000 = 4.8%
In similar ways it is possible to calculate the resource usage for other

configurations (CFI =1, 2, 3 and BW = 1.4, 3, 5, 15 and 20 MHz).
Calculate and fill in the following table for 10 MHz system bandwidth, CFI = 2
and two antenna ports:

PSS
and Total
SSS Ctrl Ch
4000  40
84000
Calculation
0  24

84000
%
4.8
Figure 4-81: Resource consumption for control channels and PDSCH,

BW=10MHz, CFI=2, 2 APs
For 20MHz system bandwidth, 1AP, and CFI=1 the calculation can be done as
follows:
In a 20 MHz system bandwidth, there are 12∙14∙100∙10 = 168000 resource

elements per radio frame.
The resource consumption for the control channels can be calculated for 20 MHz
and one antenna port and CFI=1 as follows:
RS: 8 Reference Symbols per scheduling block => 8/168=4.76%
PSS: 62∙2 PSS resource elements per radio frame 124/(168∙10∙100) = 0.074%
SSC: same as PSS = 0.074%
PBCH: 240/(168∙10∙100) = 0.14%
PCFICH: 160/(168∙10∙100) = 0.095%
PHICH: 1560/(168∙10∙100) = 0.93%
PDCCH: 6120/(168∙10∙100) = 3.6%
Total Control Channel: 9.7%
Not used:
5 unused RE on each side of PSS and SSS => (5+5)∙4
160 unused RE per frame for PDCCH.
In the control region, there are 2 REs per RB “reserved” for RS as if two antenna
ports are used. This equals 2∙100 = 200 RE per subframe unused at 20MHz BW.
Total unused REs:

ChapterTitle
(5+5)∙4/(168∙10∙100) + 160/(168∙10∙100) + 36/(168∙10∙100) + 2000/(168∙10∙100)

= 1.3%.
48 REs are always used for RS in the PBCH region (as if it was four antenna
ports). When two APs are configured, 12 of these are used for actual RS per
antenna port when two antenna ports are used, i.e. 24 unused REs.
Calculate and fill in the following table for 20 MHz system bandwidth and two
antenna ports:
PSS
and Total
SSS Ctrl Ch
8000  40
168000
Calculation
160  24

168000
Figure 4-82. Resource consumption for control channels and PDSCH,

BW=20MHz, CFI = 1, 2 APs..
10.3 Power usage

The DL power per antenna port is divided equally over the whole system
bandwidth except for the reference symbols when more than one antenna port is
used. This means that a constant PSD (Power Spectrum Density) is used. All
subcarriers within an RB are allocated the same power, the reference power Pref,
which is the total antenna port power divided by the number of allocated
subcarriers (12∙NRB).
The reference symbols are an exception from this rule when more than one
antenna port is configured. The reference symbols on one antenna port
corresponding to holes on the other antenna port are given all antenna port’s
power since there is no other transmission on the other port. This corresponds to
3 dB more power when two antenna ports are used.
With this information together with the previous calculated resource usage, it is
possible to calculate the power usage for the control channels and physical
signals.

Fill in the missing fields in the table below with power usage for the DL
channels, assuming a 40 W total cell power. The result from the resource
consumption calculations is already filled in.
PSS
and Total
SSS Ctrl Ch
% 1.4 4.8 0.3 0.3 0.2 0.9 10.7 17.2 81.5
Figure 4-83. Power consumption per antenna port, BW=10MHz, CFI = 2, 1 AP,
40W.
Fill in the missing fields in the table below with power usage for the DL
channels, assuming a 40 W total cell power. The result from Figure 4-82 is
already filled in. Please note that the total RBS power (nominal power from all
radio units in the cell) must be divided by the number of antenna ports (in this
example 2) and that the RS is boosted with 3 dB.
PSS
and Total
SSS Ctrl Ch
% 4.9 4.8 0.15 0.14 0.1 0.9 3.6 9.7 85.4
Figure 4-84 Power consumption per antenna port, BW=20MHz,CFI = 1, 2 APs,

40W.
PHICH is power controlled per PHICH group, so users with poor radio
conditions can be allocated higher power than users with good conditions. Res
belonging to one PHICH group can be allocated a different power than PRE,ref.
The average power of PHICH is however equal to PRE,ref.
10.4 UL control channel

The Physical Uplink Control Channel (PUCCH) carries uplink control
information from user equipment for which no PUSCH resource is granted in the
same subframe. For user equipment already granted a PUSCH, control signalling
is multiplexed with data onto PUSCH.
PUCCH is used for transmitting:
• Hybrid Automatic Repeat Request (HARQ) Acknowledgement/Negative

Acknowledgement (ACK/NACK)

ChapterTitle
• Scheduling Request (SR)
• Channel status reports, Channel Quality Indicator (CQI) and Rank Indicator
(RI)
The RBs allocated for PUCCH are placed at the band edges. The information sent
on PUCCH uses one RB in each of the two consecutive slots in a subframe. The
two RB used for PUCCH is here after called resource block pair (RB-pair).
PUCCH are not only specified by an RB-pair and a periodicity. To allow an RB-
pair to be shared by several user equipments, a resource on PUCCH are also
specified by a cyclic shift, and for SR and HARQ resources also an orthogonal
cover sequence.
Depending on the information to be carried on PUCCH, one of two formats is

used:
• PUCCH Format 1 for SR and HARQ ACK/NACK
• PUCCH Format 2 for CQI and RI
A user equipment is allocated CQI and SR resources at the UE setup procedure.

The resources are kept as long as the user equipment is uplink synchronized.
A UE is allowed to connect to a cell if there are free SR resources, therefore it

should be at least as many SR resources as CQI resources allocated. A UE
already in connected mode will stay connected when uplink synchronization is
timed out and PUCCH resources are released.
The parameters noOfPucchCqiUsers and noOfPucchSrUsers determine the

number of resources for CQI and SR per cell. To avoid PUSCH from interfering
PUCCH, it is recommended to use the same setting of noOfPucchCqiUsers and
noOfPucchSrUsers and thereby the same number of PUCCH RBs in all cells.
To maximize PUSCH throughput, the number of RB-pairs should not be over-

dimensioned and preferably be an even number as an odd number will leave one
RB-pair unused by both PUCCH and PUSCH.
The following table describes the highest recommended value of

noOfPucchCqiUsers and noOfPucchSrUsers per cell and DU for the
most common configurations.

BW [MHz] SR resources/cell CQI resources/cell

1.4 729 792
3-20 810 880
DU type # Rx antennas Max # of RB pairs

per DU
DUL20 2 24
4 12
DUS31 2, 4 24
DUS41 2, 4 36
Figure 4-85: Highest value of SR and CQI resources
If cells with different number of RX antennas are configured in a DU, the highest
number of RX antennas used in a cell should be chosen in the Maximum number
of RB pairs.
The simultaneous allocated resources in all cells in a DU are limited by the

maximum number of resources available in the DU. The resources are pooled
within the DU which means that the number of used resources can vary between
cells. The figure below describes the available number of SR and CQI resources
in a DU. These values do not limit the setting of noOfPucchCqiUsers and
noOfPucchSrUsers.
DU BW SR resources/DU CQI resources/DU

type [MHz] 2 Rx 4 Rx 2 Rx 4 Rx
DUL20 1.4 1224-x 819-x 1224 792
3-20 1360-x 910-x 1360 880
DUL31 1.4 1638-y 1638-y 1584 1584
DUL41 3-20 1820-y 1820-y 1760 1760
x
y
Figure 4-86: SR and CQI resources per DU

ChapterTitle
Given a desired setting of noOfPucchSrUsers and noOfPucchCqiUsers,

the number of RB-pairs for PUCCH can be calculated as shown in the figure
below:
 noOfPucchC qiUsers 10 
nRBformat2    
 n T
cap p ,CQI n SF , PUCCH 
 noOfPucchS rUsers 10 
nPUCCH , SR     nPUCCH,HARQ pdcchCfiMode
 T p , SR n SF , PUCCH  CFI_AUTO_MAXI CFI_AUTO_MAXI
CFI_STATIC_BY_ CFI_STATIC_1 MUM_2 MUM_3
BW
 nPUCCH , SR  nPUCCH , HARQ  BW CFI_STATIC_2 CFI_STATIC_3
nRBFormat1    1.4 5 N/A 5 7

 36 
3 8 N/A 8 13
 n  n 
nRB , PUCCH  2 RBFormat1 RBFormat 2  5 13 N/A 13 22
 2 
10 27 11 27 44
15 16 16 41 66
Where:
20 22 22 55 88
Ncap is the CQI resources per RB-pair, equal to 4
Tp,CQI is the periodicity for CQI reporting, equal to 80ms
nSF,PUCCH is the no of subframes with PUCCH, equal to 9
for 1.4 Mhz, otherwise 10
Tp,SR is the periodicity for SR, equal to 10ms
Figure 4-87: Calculation of PUCCH RB usage
Given a wanted number of RB-pairs for format 1 and format 2, the setting of
noOfPucchSrUsers and noOfPucchCqiUsers can be calculated as in
the figure below:
nSF , PUCCH
noOfPucchS rUsers  (36nRB , format1  nPUCCH , HARQ )Tp , SR
10
nSF , PUCCH
noOfPucchC qiUsers  nRB , format2 ncapTp ,CQI
10
Figure 4-88: Calculation of SR and CQI resources - from a wanted number of
RB-pairs for Format1 and Format2
The Demodulation Reference Signal (DMRS) uses two OFDM symbols per
subframe. This equals 11.8-13.6%, depending on system BW.
PRACH uses one subframe (1ms) over 6 RBs per radio frame in subframe 1, 4 or
7. This corresponds to 6/50∙1/10 = 1.2% for 10 MHz system BW. See figure
below.

PRACH
PUCCH
PUSCH
DMRS in PUSCH
Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6 Subframe 7 Subframe 8 Subframe 9
For cell range over 15 km Other possible PRACH

opportunities
PRACH
PUCCH
PUSCH
DMRS in PUSCH
Figure 4-89: UL resource grid
Based on the above information and the resource grid structure, calculate and fill
in the resource usage for the UL in the following table (assuming 2 RBs used for
PUCCH for all system bandwidths, except 10 and 20 MHz where 4 RBs are used
for PUCCH):
BW
PRACH PUCCH DMRS on PUSCH PUSCH
[MHz]
1.4
10
15
20
Figure 4-90. Uplink resource usage – cell range max 15 km

ChapterTitle
BW
PRACH PUCCH DMRS on PUSCH PUSCH
[MHz]
6/6x2/10 2/6x8/10 = 4/6x1/7-4/6x1/7x2/10 =
1.4 = 20% 45.7%
26.7% 7.6%
6/15x2/10 2/15 = 13/15x1/7-6/15x1/7x2/10 =
3 67.5%
= 8% 13.3% 11.2%
5 6/25x2/10 2/25 = 23/25x1/7-6/25x1/7x2/10 =

74.7%
= 4.8% 8.0% 12.5%
6/50x2/10 4/50 = 46/50x1/7-6/50x1/7x2/10 =
10 76.8%
= 2.4% 8.0% 12.8%
15 6/75x2/10 2/75 = 73/75x1/7-6/75x1/7x2/10 = 82.0%

= 1.6% 2.7% 13.7%
6/100x2/10 4/100 = 96/100x1/7-6/100x1/7x2/10 =
20 81.3%
= 1.2% 4.0% 13.5%
Figure 4-91 Uplink resource usage - Cell Range above 15km
10.5 Sounding Reference Signal

Sounding is a prerequisite for UL Frequency Selective Scheduling, see (FSS).
Uplink Frequency-Selective Scheduling. When sounding is activated a UE can
transmit Sounding Reference Signals (SRS) over the uplink system bandwidth.
With the help of SRS the eNB can estimate the UL frequency dependant path loss
between the UE and the eNB.
REs for SRS are allocated on every 5th subframe. Such a subframe is referred to
as a sounding subframe. In order to avoid interference between SRS and PRACH,
sounding subframes are not configured in subframes with PRACH. Only the last
symbol is allocated for SRS. This means that the fraction of REs reserved for
SRS is approximately 1.4%. Note that these REs are always reserved in cells with
the sounding functionality enabled regardless of if there are UE using sounding.
Several UE can transmit SRS simultaneously in the same RB using different
transmission combs and cyclic shifts. Which SRS resource to use is signaled to
the UE by RRC signalling. A UE keeps its SRS resource as long as it is uplink
synchronized.
The structure of SRS and the number of RBs over which SRS are transmitted is
given by the following figure:

PRACH
PUCCH
PUSCH
DMRS in PUSCH
SRS
BW [MHz] RBs SRS FH #SRS SRS tx SRS

each periodicity period
occasion
1.4 4 No 4 20 20
3 12 No 12 20 20
5 24 Yes 24 20 20
10 48 Yes 12 5 20
15 72 Yes 12 5 30
20 96 Yes 24 5 20
Figure 4-92: Sounding Reference Signal
Depending on the PUCCH configuration, the SRS bandwidth can overlap with
RBs allocated for PUCCH. To avoid interference between SRS and information
carried over PUCCH format 1, a short PUCCH format 1 is used in sounding
subframes. The short PUCCH format 1 has the last symbol reserved for SRS.
PUCCH format 2 is not modified in sounding subframes and interference
between SRS and PUCCH format 2 can occur. The impact is considered
negligible.
For system bandwidth of less than 10 MHz a non-frequency hopping SRS

transmission scheme is used while for larger bandwidths a frequency hopping
SRS scheme is used. In case of non-frequency hopping a UE being allocated SRS
resources transmits SRS every 20 ms. At each transmission occasion the entire
SRS bandwidth is covered. In case of the frequency hopping scheme, on each
transmission occasion SRS are sent on a subset of the SRS bandwidth.
Several transmission occasions are required to cover the entire SRS bandwidth.
The transmission schemes are summarized in the figure above.

ChapterTitle
10.6 Paging capacity

A small number of cells in the TA (or TA list) lead to frequent TA updates which
in turn increases the MME load and UE battery consumption. Also, frequent TA
updates may lead to reduced paging capacity since the UE may be busy making
TA updates and therefore not able to respond to a paging simultaneously.
A large number of cells in the TA (or TA list) reduces the TA update frequency,
but increases the paging load, since more cells are being paged simultaneously.
The bottleneck in this case may be the MME paging capacity and the RBS paging
capacity.
10.6.1 MME paging capacity

The number of SCTP/S1 boards in the MME determines the MME paging
capacity. Each MkVI board should not exceed 2000 pages per second.
Therefore the MME paging capacity can be expressed as:
CMME = 2000 ∙ nSCTP, (with SCTP MkVI)
where nSCTP is the number of SCTP boards in the MME. This is valid for SGSN-
MME with MkVI hardware. For MkVIII hardware, the capacity is 6000 pages/s
per SCTP board.
10.6.2 RBS paging capacity

The RBS paging capacity depends on the
 RBS CPU load, which leads to a certain paging capacity
(CCPU) in relation to CPU load caused by paging
 PDSCH load, which leads to a certain paging capacity
(CPDSCHload) in relation to PDSCH load caused by paging
 Blocking, which leads to a certain paging capacity (Cblocking) in
relation to blocking caused by paging
 PDCCH load, which leads to a certain paging capacity
(CPDCCHload) in relation to PDCCH load caused by paging

› MME paging capacity

– 2000 pages/s per SCTP board
› RBS Paging capacity
– CPU load (<600 pages/s)
– PDSCH load (< 5%)
– Blocking (< 2%)
– PDCCH load (< 5%)
CRBS=min(CCPU, CPDSCHload, Cblocking, CPDCCHload)

Figure 4-93: Paging capacity
The scheduler gives higher priority to paging than user data. Therefore, a high
paging load may reduce the DL capacity and bit rates on PDSCH. Also, the
PDCCH signaling in terms of scheduling assignments for DL and scheduling
grants for UL may suffer, since paging has higher priority than the user data.
The total RBS paging capacity can be expressed as the minimum of the four
capacity figures:
CRBS=min(CCPU, CPDSCHload, Cblocking, CPDCCHload),
where CCPU is recommended not to exceed 600.
The CPDSCHload can be calculated as follows:
100  10n RB LPDSCH max

C PDSCHload  ,
nSB, page
where:
100·10·nRB is the number of scheduling blocks per second
nRB is the number of RBs in system bandwidth
LPDSCHmax is the maximum tolerable PDSCH load due to paging
nSB,page = 3+0.32(nPDCCHsymb-1), which indicates the number of scheduling blocks

required to convey one page over PDSCH where nPDCCHsymb is the number of
PDCCH symbols (=2 for system bandwidth 3 and 5 MHz and =1 for 10, 15 and
20 MHz). Note that this is only an example and may change due to automatic
setting of CFI. See Control channel dimensioning earlier in this chapter.

ChapterTitle
The figure below shows the result of the above relationships between tolerable
PSDCH load and paging capacity.
100 10nRB LPDSCH max › 100·10·nRB is the number of scheduling blocks

C PDSCHload  per second
nSB, page
› nRB is the number of RBs in system bandwidth
› LPDSCHmax is the maximum tolerable PDSCH

nSB, page  3  0.32(nPDCCH , symb  1) load due to paging
› nSB,page = 3+0.32(nPDCCHsymb-1), which

indicates the number of scheduling blocks
required to convey one page over PDSCH
› where nPDCCHsymb is the number of PDCCH

symbols (=2 for system bandwidth 3 and 5
MHz and =1 for 10, 15 and 20 MHz).
Figure 4-94: Calculation of PDSCH paging capacity
The results of these calculations are shown in the following figure:
Figure 4-95: Paging capacity in relation to PDSCH load
The probability that PDSCH is blocked as a function of paging capacity (Cblocking)

can be calculated using the following poisson-based expression:

Rmax R
Cblocking
R max  e   ( Rmax  R)
Cblocking , PO , PO
R!
Pblocking,max  1  R 0
Cblocking, PO
The paging capacity Cblocking is shown as a function of PDSCH blocking

probability in Figure 4-96 for the 16 different settings of
maxNoOfPagingRecords (1-16).
16
15
14
maxNoOfPagingRecords
13
12
11
10
9
8
7
6
5
4
3
2
1
Figure 4-96. Paging capacity vs blocking probability.
The paging capacity in pages per PO can be converted to pages to second using:
Cblocking = Cblocking,PO ∙ 100 ∙ nB/T
The recommended setting of maxNoOfPagingRecords is 1 for 1.4MHz system

bandwidth, 4 for 3MHz, 7 for 5MHz and 16 for 10, 15 and 20 MHz. Exceeding
these recommendations may cause the RBS exceeding the available resources in
the subframe.
An example with 20 MHz system bandwidth and 2% tolerable PDSCH blocking

(this is the maximum general recommended value) would give us a paging
capacity of 12 pages per PO. This corresponds to 12 ∙ 100 nB/T. If nB is set to
½T, the paging capacity would be 600 pages per second.
If nB is increased, the paging capacity in relation to PDSCH blocking can be

increased, but the paging capacity in relation to the PDCCH then decreases.
The probability that a scheduling assignment for a paging arrives is poisson

distributed and can be expressed as:
PSA = 1 – e-Ipage,PO

ChapterTitle
The scheduling assignment for a paging uses 8 CCEs. The average number of
CCEs required for paging traffic per frame is then:
nCCE,frame = 4nPO,frame(1 – e-Ipage,PO); for bandwidth ≤ 3 MHz
nCCE,frame = 8nPO,frame(1 – e-Ipage,PO); for bandwidth > 3MHz
The PDCCH capacity can then be expressed as a function of PDCCH load as

follows (for bandwidths equal and below 3MHz and above 3 MHz respectively):
nCCE, frame LPDCCH ,max

C PDCCHload  100n PO , frame  ln(1  )
4n PO , frame
nCCE, frame LPDCCH ,max

C PDCCHload  100n PO , frame  ln(1  )
8n PO , frame
BW
1.4 3 5 10 15 20
[MHz]
nPDCCHsymb
N/A 20 30 80 120 170
=1
nPDCCHsymb
20 70 120 250 370 500
=2
nPDCCHsymb
40 120 200 410 620 840
=3
nPDCCHsymb
60 N/A N/A N/A N/A N/A
=4
nCCE, frameLPDCCH ,max

CPDCCHload  100nPO , frame  ln(1  ) BW =< 3MHz
4nPO , frame
nCCE, frameLPDCCH ,max
CPDCCHload  100nPO , frame  ln(1  ) BW > 3MHz
8nPO , frame
Figure 4-97: Number of CCEs per frame - nCCE,frame

By using the configuration and the above expression of PDCCH capacity result in
the following graphs:
Figure 4-98. Paging capacity vs PDCCH load – 1.4 MHz.
Figure 4-99. Paging capacity vs PDCCH load – 3 MHz.

ChapterTitle
Figure 4-100. Paging capacity vs PDCCH load – 5 MHz and 15 MHz.
Figure 4-101. Paging capacity vs PDCCH load - 10 MHz.

Figure 4-102.Paging capacity vs PDCCH load - 20 MHz.
A general rule is that the PDCCH load due to paging should not exceed 5%.
An example using 5 MHz system bandwidth and the recommended values

maxNoOfPagingRecords = 7, max CPU load of 600 pages/s, PDSCH and
PDCCH load due to paging traffic max 5% and blocking probability of max 2%
would look like this:
1. CPU load:
CCPU = 600 pages/s.
2. PDSCH load:
100  10n RB LPDSCH max

C PDSCHload 
nSB, page
, where nSB,page = 3+0.32(nPDCCHsymb-1)
results in 100 ∙ 10 ∙ 25 ∙ 0.05/nSB,page.
nSB,page is 3 + 0.32(2-1)=3.32
so, 100 ∙ 10 ∙ 25 ∙ 0.05/3.32 = 376 pages/s.

ChapterTitle
3. Blocking:
From Figure 4-96, we can see that for 2% blocking probability, the
paging capacity is 4 pages/PO (using maxNoOfPagingRecords = 7
according to the recommendation for 20 MHz).
This is converted to pages per second:
Cblocking = Cblocking,PO ∙ 100 ∙ nB/T =4 ∙ 100 ∙ nB/T
By setting nB = ½T, Cblocking equals 200 pages/s. With nB = T we get

400 pages/s. This setting clearly exceeds the CPU capacity in step 1,
so instead a setting of nB to 1/2T which yields 200 pages/s would
better fit the CPU capacity.
4. PDCCH load:
In Figure 4-102, we can see that the paging capacity is around 140
pages/s for a load of 5%, nB=T and infinity for nB=1/2T
5. In order to optimize all steps in this procedure, a setting of nB to 1/2T

seems to be the optimum and results in a paging capacity of 200
pages/s.
11 PCI Planning
The Physical Cell Identity (PCI), or Layer 1 identity, is an essential configuration
parameter of a radio cell. It identifies the cell in cell search and mobility
functions such as cell reselection and handover. The PCI is also used to
determine the location of the resource elements containing the PCFICH and
PHICH channels.
168 pseudo random sequences represent the Secondary Synchronization Signals

(SSS). They determine frame timing and the cell identity group. Each cell
identity group is combined with one of three orthogonal primary
sequences,.which represents the Primary Synchronization Signal (PSS). See
3GPP TS36.211 for more information.
The combination of these sequences offers 504 unique sequences regardless of

the system bandwidth. This allows for the reuse of the PCI in different cells.
11.1 PCI Planning Objectives

PCI planning for LTE is similar to scrambling code planning for WCDMA. The
main objective of PCI planning is to ensure that all cells are correctly identified.
If locations exist where the same PCI is received from two different cells,
ambiguities can appear in measurement reports. This may lead to erroneous
handover decisions and thereby reduced throughput and increased latency.

11.2 PCI Planning Recommendation

The reference signals are allocated with one of six possible frequency shifts,
depending on the PCI assigned to the cell, (see 3GPP TS36.211). When using
two antenna ports, there is an automatic frequency shift for the second antenna
port so that it cannot interfere with the first antenna port. The cell ID remains the
same for both ports.
If a network is planned with different primary sequences, the

reference signals from (the time aligned) intra-site neighbors will interfere
with each other. If planned with the same primary sequence, they will
interfere mainly with resource elements containing user data. According to
early preliminary observations, the cell edge user throughput will benefit
from a plan with different primary sequences. On the other hand, the
highest ranges of user throughput, obtained close to the site, will benefit
from a plan with the same primary sequences. These observations regard
only networks where cells on the same site are time-synchronized, but
different sites are not.
For example, if the cells are assigned the PCIs 24, 25 and 26 respectively,
the cells in a site are assigned different primary sequences.
It is recommended to assign PCIs with future network expansions in mind,
to avoid total replanning. This also helps to resolve unexpected PCI
clashes.
An additional option is to reserve some from the 168 SSS sequences to be

used in areas where PCI clashes can be anticipated. Such areas include, but
are not limited to, PLMN borders and indoor installations.
When planning PCIs it is also important to consider the uplink Sounding
Reference Signals (SRSs). They are determined by the PCI according to
PCI mod 30, which gives 30 sequences, see 3GPP TS 36.211. The same
sequences should not collide within the same site. The same would be
valid for the uplink Demodulation Reference Signals (DMRS).

ChapterTitle
11.3 Automatic PCI Planning

The Automatic PCI Selection feature will provide automatic planning of PCIs.
OSS-RC will provide both consistency checks and automatic assignment of the
PCIs. The operator has to accept the changes before they are activated in the
RBSs.
› 504 unique reference signal

sequences
0 27
› Objective 3 2 1 18 23 22
– Avoid PCI clashes 5 4 9 20 19 24
– Plan with future migration in mind 6 11 10 15 26 25
8 7 12 17 16 27
› Picture showing different PSS on
14 13 29 28
each cell
Figure 4-103: PCI Planning.
12 Tracking Area Dimensioning

The process of TA dimensioning contains two main tasks:
 TA dimensioning for the MME
 TA dimensioning for the RBS
These steps can be done sequentially or in parallel. The output of the tasks is the
total number of RBSs suitable to include in a TA list.
The following input data is required in the TA dimensioning process:

 Paging capacity of the MME, C MME .
 Paging capacity of the RBS, C RBS .
 Paging intensity per subscriber (during busy hour), I page, sub, s .
 Number of Simultaneously Attached Users in an MME during

busy hour, nSAU , MME .
 Average number of subscribers per RBS during busy

hour, nsub, RBS .

All input data are used for calculation of the maximum number of
RBSs in a TA list in relation to the MME paging capacity.
C MME
n RBS ,TAlist , MME 
nSAU , MME  I page, sub, s
We also need to calculate the maximum number of RBSs in a TA list in relation

to the RBS paging capacity.
C RBS
n RBS ,TAlist , RBS 
nsub, RBS  I page, sub, s
Finally, the maximum number of RBSs to include in a TA list is:
nRBS ,TAlist  min nRBS ,TAlist ,MME , nRBS ,TAlist , RBS 
Paging capacity of
MME
C MME
 TA dimensioning for the MME n RBS ,TAlist ,MME 
nSAU , MME  I page, sub, s
#Simultaneously Paging intensity

Attached Users in per sub.
MME
Paging capacity of
RBS
CRBS
 TA dimensioning for the RBS nRBS ,TAlist , RBS 
nsub, RBS  I page, sub, s
#Subs. in RBS
nRBS ,TAlist  min nRBS ,TAlist ,MME , nRBS ,TAlist , RBS 

Figure 4-104 TA Dimensioning
Example:
In this example, the number of RBSs in the TA list is calculated based on the
MME being configured with 5 SCTP/S1 boards.
The following data is used in the example:
• In a city with 700,000 attached subscribers there are two MMEs.
• 50% of the subscribers have PC cards and 50% have handheld terminals.
• In this example it is assumed that there are 0.39 paging requests for PC card
users and 1.68 paging requests for handheld users per busy hour.

ChapterTitle
As paging intensity varies greatly between networks, the intensity in this example
shall not be used in a real TA dimensioning process without further studies.
• It is also assumed that there are approximately 5000 users per RBS and the RBS
paging capacity has been determined to be approximately 200 pages/s, according
to the earlier example above.
Solution:
The following list shows the tasks in finding a solution for TA dimensioning:
1 The first step is to calculate the paging intensity per subscriber and second:
Ipage,sub,s = (0.39*0.5 + 1.68*0.5)/3600
2 The second step is to perform TA dimensioning in relation to the MME:
Assuming that the number of attached users in the two MMEs are equally split
between the two MMEs, nSAU,MME becomes:
nSAU,MME = 700000/2 = 350000
The MME paging capacity with 5 SCTP boards is:
CMME = 2000*nSCTP = 2000*5 = 10000
The number of RBS per TA list for MME paging capacity:
nRBS,TAlist,MME = CMME/(nSAU,MME*Ipage,sub,s) = 10000/(350000*0.0002875) = 99
3 The third step is to perform TA dimensioning in relation to RBS paging

capacity:
nRBS,TAlist,RBS = CRBS/(nsub,RBS*Ipage,sub,s) = 200/(5000*0.0002875) = 140
4 The maximum number of RBSs to include per TA list is given by:
nRBS,TAlist = min(nRBS,TAlist,MME;nRBS,TAlist,RBS) = 99
In this example, the TA list size is limited by the MME capacity to 99 RBSs per
TA list:
12.1 Tracking area planning

When planning borders between TAs and TA lists, the following two general
rules apply:
 TAs and TA lists should be planned so that areas with frequent
TA update signalling are located in low traffic areas. This
makes it easier for the RBS to cope with the additional
signalling caused by the TA update procedure.

 TAs and TA lists should be planned so that the need for TA

updates is minimized. This is accomplished by considering how
users travel within the network. Busy roads, railways, and so
on, should cross as few TA list borders as possible.
General principles:
 Locate frequent TA update signalling to low traffic
areas
– Additional signalling caused by TA update procedure
 Minimize the need for TA updates

– How does the users travel?
 Busy roads
 Railways
Figure 4-105 TA Planning - Planning borders between TAs and TA lists
From release SGSN-MME R2010A RP02, up to 16 TAs per TA list will be

supported. For every TA, the operator can specify a list of up to 15 TAs.
Remember that the MME always adds the old TA to the list to reduce the risk of
ping-pong updates. This is the reason that the operator can not specify up to 16
TAs per list.
In MME releases prior to SGSN-MME R2010A RP02, the MME includes only
the current TA in the TA list.
In case TA lists with multiple TAs are employed, the average number of RBSs
per TA should not exceed:
n RBS ,TAlist
n RBS ,TA 
nTA,TAlist
n RBS ,TA the number of RBSs to include per TA list, calculated in

the dimensioning process
nTA,TAlist  2 the number of TAs in the TA list. When TA lists with

multiple TAs are used
Besides reducing the risk for ping-pong updates, TA lists with multiple TAs can
help resolve the issue of a few cells having to handle a high number of TA
updates.

ChapterTitle
This is done by including many TAs in the TA list and defining the TA lists in a
sliding window, as shown in Figure 4-106.
 One method to reduce ping-pong updates

TA list in TAC=12
TA list in TAC=16
TAC=1 TAC=2 TAC=4
TAC=3 TAC=5 TAC=6 TAC=7 TAC=9 TAC=8
Figure 4-106 TA lists - Sliding Window
With this strategy, the TA update load is distributed over a large number of cells.
The operator can determine the number of TAs to include per TA list, taking into
account the characteristics of the cell plan. The larger the number the more even
is the distribution of TA update signalling. One drawback with a larger TA list is
that it requires more planning and administration.
12.1.1 Planning strategies

There are currently two different strategies to consider when planning tracking
areas. Either you plan the TAs with consideration to migrating to TA lists with
multiple TAs or not. There are of course advantages and drawbacks with both
methods.

12.1.1.1 Without considering future migration to TA lists with multiple TAs
In MME releases prior to SGSN-MME R2010A RP02 only the current TA is sent
in the TA list. With one TA in the TA list it is possible to allocate all RBSs to the
same TA, as shown in Figure 4-107.
Many RBSs/TA:
TAC=1
 Large TAs
– Possibility to Reuse
Routing Areas (RA)
 High paging load

– pages blocked
– user traffic affected
 Must eventually be
replanned in the future
Figure 4-107 TA Planning strategy - Without considering future migration to TA
lists with multiple TAs.
With this strategy, the TAs are likely to be large, and large parts of existing RA
boundaries can be re-used.
The drawback to this strategy is that TAs must be replanned once TA lists with
multiple TAs are introduced to the network. Another drawback is that the paging
load could increase and thereby the user traffic might be affected.
12.1.1.2 Considering future migration to TA lists with multiple TAs
To avoid replanning TAs when introducing TA lists with multiple TAs, the
option exists to dimension the TA size equal to n RBS ,TA .
A drawback is that this strategy can lead to more frequent TA updates, which
increases the MME load. This could result in a decrease of the success rate for
terminated calls as well as lower battery life for the UEs.

ChapterTitle
The additional update signalling is not a major problem if the number of

subscribers is small. An example planning for multiple TAs per TA list is shown
in Figure 4-108.
Few RBSs/TA
TAC=2 TAC=6
 Ready for future migration
 Frequent TA updates
– Drains battery
– Possible decrease of TAC=4 TAC=15
success rate for
terminated calls
– High signaling load
Figure 4-108 TA Planning strategy - Considering future migration to TA lists with
multiple TAs.
There are two options for how the Ericsson SGSN-MME creates a TA-list:
TA lists based on visited TAs. With this option the SGSN-MME creates a TA list
based on the current TA and a number of previously visited TAs. Only TAs
visited during the last MaxTaiAge hours will be part of the list and the maximum
number of TAs in the list is limited to MaxTaiListLength.
TA lists containing the current TA, last visited TA and an operator defined
specified list of up to 14 TAs.
In both cases, the average number of RBSs per TA should not exceed
nRBS,TA=nRBS,TAlist/nTA,TAlist.
12.1.1.3 Effects of CS Fallback to GSM/WCDMA on TA Planning
The feature CS Fallback to GSM/WCDMA enables a UE to fallback from E-

UTRAN to access the CS-domain in legacy GSM or WCDMA networks.
To minimize CS call setup delay when using CS Fallback the coverage of a TA

or TA list must be within the coverage of one and only one Location Area (LA).
This makes it possible for the MME to inform the MSC in which LA the UE is
located. An incorrect LA information sent from the MME will cause a minor
delay due to increased signalling if the incorrect and actual LA are controlled by
the same MSC or MSC pool. A larger additional delay will occur if the LA
indicated by MME and the LA in which the UE is located are controlled by
different MSCs or MSC pools. Therefore it is recommend to align TA list borders
so that they do not span over borders between MSCs or MSC pools. An
implication is that UE along borders between MSCs or MSC pools will have an
increased risk to experience ping-pong TA updates.
For more information about the feature CS Fallback to GSM/WCDMA, see CPI
CS Fallback to GSM and WCDMA

Solution to dimensioning exercise
Input requirements: [kbps] Legend UL input UL Control channel coverage

UL celledge rate 500 coverage prob 0,95 DL input P0,pucch -120,01
UL high rate 10000 Partial calc SINRpucch,A/N-4,36942
UL cell thrp 6000 Partial calc and various input
DL cell edge rate 8000 coverage prob 0,95 Approximated inputs from graphs
DL cell thrp 15000 Output fulfilling req
Output not fulfilling req
This tool is designed for training purposes only

UL C&C It1 It2 It3 DL C&C
Lsa,cellrange 115 120 128 High bit rate SINRh 1,70032935 1,70032935 13,8334345 Lpmax 125,5
P0 -106 -106 -103 n'rb,h 95,4 95,4 95,4 Blnf 4,9
Qpusch 1 1 0,25 Rrb,h 130,328779 130,328779 402,082726 Lbl 3
Rh 12433 12433 38359 Lbpl 18
Noise rise Lcpl 0
Nt -174 -174 -174 Cell trp Ga 18,5
Wrb 180000 180000 180000 equals P0 as long
Prx,rb,ave
as UEs reach target,
-106 otherwise
-106
fig 8 -109,2963 Lj 0
Nf,tma 1 1 1 SINRave 1,70032935 1,70032935 7,53713824 Lsa,cellrange 128
Nf,ru 1,58 1,58 1,58 Rrb,ul,ave 130,328779 130,328779 265,596547 Lsa,celledge 132,9
Lf 1 1 1 Tcell 12433 12433 6334,5 Ptx 40
Gtma 1 1 1 Ptx,rb 0,4
Cell Size Fc 1,8
Thermal Noise Nrb,ul -119,46 -119,46 -119,46 Lbl 3 3 3 Qpdsch 0,55
Lbpl 18 18 18 Qcch 0,118
Irb,ul -108 -108 -114,24 Lcpl 0 0 0 Nf,ue 7
Biul 11,7604 11,7604 2,62727 IRC_Beta 0 Ga 18,5 18,5 18,5 Nrb,dl -114,447
Lpmax 112,5 117,5 125,5
Cell edge bit rate cell range,
0,2005
max 0,278 0,4689 Bidl 8,573821
Blnf 4,9 4,9 4,9 (also DL control ch coverage)
att at cell edge Lsa,celledge 119,9 124,9 132,9 SINRcelledge -1,00595
alloc RBs n'rb,celledge 30,2018 9,55065 12,3978 gamma0 -4 npdcch 1
Pue,rb,celledge 8,19967 13,1997 12,0666 a0 1271,564
Prx,rb,celledge -111,7 -111,7 -120,83 a1 56,8
SINRcelledge -4 -4 -4 a2 41
a3 0
a0 519,7 519,7 519,7 a4 4
a1 37 37 37 Rrb 82,19367
a2 29,7 29,7 29,7 LB R 8219
a3 0 0 0
a4 4 4 4 DL Cap
Rrb,celledge 41,9279 41,9279 41,9279 H 0,36
Rcelledge 1266 400 520 F 0,6
Bidl,ave 8,68495
SINRave 8,2199
Rrb,dl 324,3339
Rave,dl 32433,39
Tcell 17838

Colocation and Coexistence
5 Colocation and Coexistence
Objectives

1. Explain on overview level the transmitter interference
characteristics.
2. Explain Adjacent Channel Leakage Ratio (ACLR) and spurious
emissions.
3. Describe the receiver interference characteristics
4. Explain Adjacent Channel Selectivity (ACS) and receiver blocking.
5. Explain Adjacent Channel Interference Ratio (ACIR).
6. Explain the co-existence problems that may appear.
Figure 5-1 Objectives of chapter 5

1 INTRODUCTION
The various E-UTRA Frequency Division Duplex (FDD) frequency bands are
illustrated in the figure below.
FDD Frequency Bands

Band ”Identifier” UL [MHz] DL [MHz] 1.4 3 5 10 15 20 Duplex
1 IMT Core Band 1920 – 1980 2110 – 2170 ● ● ● ● 190
2 PCS 1900 1850 – 1910 1930 - 1990 ● ● ● ● ● ● 80
3 GSM 1800 1710 – 1785 1805 – 1880 ● ● ● ● ● ● 95
4 AWS (US & other) 1710 – 1755 2110 - 2155 ● ● ● ● ● ● 400
5 850 824 – 849 869 – 894 ● ● ● ● 45
6 850 (Japan #1) 830 – 840 875 – 885 ● ● 45
7 IMT Extension 2500 – 2570 2620 – 2690 ● ● ● ● 120
8 GSM 900 880 – 915 925 – 960 ● ● ● ● 45
9 1700 (Japan) 1750 – 1785 1845 -1880 ● ● ● ● 95
10 3G Americas 1710 – 1770 2110 – 2170 ● ● ● ● 400
11 1500 (Japan #1) 1427.9-1452.9 1475.9-1500.9 ● ● ● ● 48
12 US 700 698 – 716 728 - 746 ● ● ● ● 30
13 US 700 777 - 787 746 - 756 ● ● ● ● -31
14 US 700 788 - 798 758 - 768 ● ● ● ● -30
15,16 Reserved - -
17 US 700 704 - 716 734 - 746 ● ● 30
18 850 (Japan #2) 815 – 830 860 - 875 ● ● ● 45
19 850 (Japan #3) 830 - 845 875 - 890 ● ● ● 45
20 Digital Dividend 832 – 862 791 - 821 ● ● ● ● -41
21 1500 (Japan #2) 1447.9 – 1462.9 1495.9 – 1510.9 ● ● ● 48
● Valid channel bandwidths for the different frequency bands
Figure 5-2: Operating Bands - LTE FDD
The various E-UTRA Frequency Division Duplex (TDD) frequency bands are
illustrated in the figure below.
TDD Frequency Bands

Band ”Identifier” Frequencies [MHz] 1.4 3 5 10 15 20
33 TDD 2000 1900 – 1920 ● ● ● ●

34 TDD 2000 2010 – 2025 ● ● ●
35 TDD 1900 1850 – 1910 ● ● ● ● ● ●
36 TDD 1900 1930 – 1990 ● ● ● ● ● ●
37 PCS Center Gap 1910 – 1930 ● ● ● ●
38 IMT Extension Center Gap 2570 – 2620 ● ● ● ●
39 China TDD 1880 – 1920 ● ● ● ●
40 2.3 TDD 2300 – 2400 ● ● ● ●
Figure 5-3: Operating Bands - LTE TDD
The various CDMA and eHRPD bands are illustrated in the figure below.

Band ”Identifier” UL ( ) DL ( ) Duplex

0 800 MHz cellular band 824 – 849 869 - 894 45
1 1.8 to 2.0 GHz PCS band 1850 - 1910 1930 – 1990 80
2 872 to 960 MHz TACS band 872 – 915 917 - 960 45
3 832 to 925 MHz JTACS band 887 – 925 832 - 870 55
4 1.75 to 1.87 GHz Korean PCS band 1750 – 1780 1840 - 1870 90
5 450 MHz NMT band 452.5 – 460, 479 – 483.5 462.5 – 470, 489 – 493.5 10
6 2 GHz IMT-2000 band 1920 – 1980 2110 – 2170 190
7 700 MHz band 776 – 794 746 – 764 30
8 1800 MHz band 1710 – 1785 1805 - 1880 95
9 900 MHz band 880 – 915 925 - 960 45
10 Secondary 800 MHz band 806 – 824, 896 - 901 851 – 869, 935 - 940 45, 39
11 400 MHz European PAMR band 1 411.5 - 483.5 421.5 – 493.5 10
12 800 MHz PAMR band 870 – 876 915 – 921 45
13 2.5 GHz IMT-2000 Extension Band 2500 – 2570 2620 - 2690 120
14 US PCS 1.9GHz Band 2
1850 – 1915 1930 - 1995 80 or 120
15 AWS Band 1710 – 1755 2110 - 2155 400
16 US 2.5GHz Band 2502 – 2568 2624 – 2690 122
17 US 2.5GHz Forward Link Only Band 3 N/A 2624 - 2690 n/a
Figure 5-4: Operating Bands CDMA & eHRPD

WCDMA
WCDMA TDD
The different bands utilised by the different systems discussed in here are shown
PHS
in Figure 5-5 below. The most critical co-existence situations occur when the
DECT
DownLink (DL) of the interfering system (aggressor) is close to the UpLink (UL)
GSM 1800
of the interfered system (victim). In that case the Radio Base Station (RBS) of the
PDC 1500
interfering system is constantly disturbing the victim RBS, probably with high
PCS 1900
gain antennas on both

TACS
sides. GSM 900
LTE* ETACS
WCDMA
CDMA IS-95 800
region 2
WCDMA TDMA IS-136 800

region 1&3
WCDMA TDD PDC 800
PHS 800 1000 1200 1400 1600 1800 2000 2200

Frequency [MHz]
DECT
Uplink Downlink Uplink and Downlink
GSM 1800
PDC 1500
PCS 1900
TACS
GSM 900
ETACS
CDMA 800
IS 95
TDMA 800
IS 136
PDC 800
800 1000 1200 1400 1600 1800 2000 2200 2400 2600 2800
Frequency [MHz]
* LTE can be deployed
in any band listed in Uplink Downlink Uplink and Downlink
this sheet
Figure 5-5 WCDMA and other communication systems
User Equipment (UEs) may also be close to each other and cause interference,
but this happens only occasionally. RBS and UE may also interfere with each
other in special situations.

1.1 Guard band and carrier separation

“Guard band” means the unutilised frequency band between two cellular systems,
that is, the area between two operators outside the allocated spectrum. Carrier
separation means the distance between the centre frequencies of two adjacent
channels.
1.2 LTE RBS RF characteristics

When considering the coexistence interference issues, it is necessary to know the
RF characteristics of the transmitter and receiver because coexistence
interference is mainly caused by the transmitter non-linearities and imperfect
receiver filtering.
This section is divided into two parts, transmitter and receiver. In the transmitter
part, leakage powers to the adjacent channels or non-LTE band due to spectrum
mask from the transmitter are presented. In the receiver part, the receiver
performance, which is non-ideal and with side lobes in the adjacent channel, is
described. Transmitter characteristics
1.3 Out of band emission

Out of band emissions are unwanted emissions immediately outside the channel
bandwidth resulting from the modulation process and non-linearity in the
transmitter but excluding spurious emissions.
One of the requirements for out of band emission is Adjacent Channel Leakage
power Ratio (ACLR). It is defined as the ratio of the transmitted power to the
power measured in an adjacent channel. Both the transmitted power and the
adjacent channel power are measured through a matched filter (Root Raised
Cosine and roll-off 0.22) with a noise power bandwidth equal to the chip rate for
WCDMA and a rectangular filter for LTE.
In practice, it is difficult to make a small and high-complexity power transmitter

for the UE. Thus, uplink adjacent channel interference is mainly caused by the
UE’s non-linear power amplifier. Therefore, UE ACLR becomes a critical
parameter for UL adjacent channel leakage power.

ACLR can be described as the ‘relative amount of transmitted power leaking into
adjacent channels’ as illustrated in Figure 5-6 below.
Channel BW Channel BW
ACLR ACLR
Adjacent channel Transmitted channel Adjacent channel
Relative amount of transmitted power leaking into

adjacent channels
Figure 5-6 Adjacent Channel Leakage Ratio
The RBS ACLR characteristics are specified in the 3GPP specification 36.104.
An excerpt of this specification is illustrated in Figure 5-7 below.
E-UTRA transmitted BS adjacent channel Assumed adjacent Filter on the adjacent ACLR
signal channel centre frequency offset channel carrier channel frequency and Limit
bandwidth BWChannel below the first or above (informative) corresponding filter
the last carrier centre Bandwidth
[MHz]
frequency transmitted
1.4, 3.0, 5, 10, 15, 20 BW Channel E-UTRA of same BW Square (BW Config) 45 dB
2 x BW Channel E-UTRA of same BW Square (BW Config) 45 dB
BW Channel /2 + 2.5 MHz 3.84 Mcps UTRA RRC (3.84 Mcps) 45 dB
BW Channel /2 + 7.5 MHz 3.84 Mcps UTRA RRC (3.84 Mcps) 45 dB
NOTE 1: BW Channel and BW Config are the channel bandwidth and transmission bandwidth configuration of the E-UTRA transmitted
signal on the assigned channel frequency.
NOTE 2: The RRC filter shall be equivalent to the transmit pulse shape filter defined in TS 25.104 [6], with a chip rate as defined in
this table.
Figure 5-7 RBS ACLR specification

The UE ACLR characteristics are specified in the 3GPP specification 36.101. An

excerpt from this specification is illustrated in Figure 5-8 below.
Minimum requirement
If the measured adjacent channel power is greater than -50dBm then the ACLR shall be higher than:
Channel bandwidth / E-UTRAACLR1 / measurement bandwidth
1.4 3.0 5 10 15 20
MHz MHz MHz MHz MHz MHz
E-UTRAACLR1 30 dB 30 dB 30 dB 30 dB 30 dB 30 dB
Adjacent channel centre +1.4 +3.0 +5 +10 +15 +20

frequency offset / / / / / /
(in MHz) -1.4 -3.0 -5 -10 -15 -20
Figure 5-8 UE E-UTRA ACLR specifications - min requirements 3GPP TS 36.101

v8.9.0
If the measured adjacent channel power is greater than -50dBm then the ACLR shall be higher than:
Channel bandwidth / UTRAACLR1/2 / measurement bandwidth
1.4 3.0 5 10 15 20
MHz MHz MHz MHz MHz MHz
UTRAACLR1 33 dB 33 dB 33 dB 33 dB 33 dB 33 dB
Adjacent channel 0.7+BWUTRA/2 1.5+BWUTRA/2 +2.5+BWUTRA/2 +5+BWUTRA/2 +7.5+BWUTRA/2 +10+BWUTRA/2

centre frequency / / / / / /
offset (in MHz) -0.7-BWUTRA/2 -1.5-BWUTRA/2 -2.5-BWUTRA/2 -5-BWUTRA/2 -7.5-BWUTRA/2 -10-BWUTRA/2
UTRAACLR2 - - 36 dB 36 dB 36 dB 36 dB
Adjacent channel +2.5+3*BWUTRA/2 +5+3*BWUTRA/2 +7.5+3*BWUTRA/2 +10+3*BWUTRA/2

centre frequency - - / / / /
offset (in MHz) -2.5-3*BWUTRA/2 -5-3*BWUTRA/2 -7.5-3*BWUTRA/2 -10-3*BWUTRA/2
E-UTRA channel
Measurement 1.08 MHz 2.7 MHz 4.5 MHz 9.0 MHz 13.5 MHz 18 MHz
bandwidth
UTRA 5MHz
channel
3.84 MHz 3.84 MHz 3.84 MHz 3.84 MHz 3.84 MHz 3.84 MHz
Measurement
bandwidth*
UTRA 1.6MHz
channel
1.28 MHz 1.28 MHz 1.28 MHz 1.28MHz 1.28MHz 1.28MHz
measurement
bandwidth**
* Note: Applicable for E-UTRA FDD co-existence with UTRA FDD in paired spectrum.
** Note: Applicable for E-UTRA TDD co-existence with UTRA TDD in unpaired spectrum.
Figure 5-9 UE UTRA ACLR specifications - min requirements 3GPP TS 36.101

v8.9.0.

1.4 Spurious emissions

Spurious emissions are caused by unwanted transmitter effects such as harmonic
emission, parasitic emission, intermodulation products and frequency conversion
products. The requirement also covers the intermodulation requirements outside
the transmitter band with several transmitting carriers transmitting.
Spurious emission is defined as the ‘amount of transmitted power measured more

than 10 MHz from the transmitting band as illustrated in Figure 5-10 below.
Spurious emissions Operating band unwanted Spurious emissions

.. emissions ..
Out-of band Out-of band

emissions emissions
Receive Band Transmit Band Receive Band

(operating band)
10MHz 10MHz
Amount of transmitted power measured more than

10 MHz from the DL operating band
Figure 5-10 Spurious Emissions.
The RBS spurious emission characteristics are specified in the 3GPP

specification 36.104. An excerpt from this specification showing the spurious
emission characteristics into the LTE receive band is illustrated in Figure 5-11
below.
Frequency range Maximum Level Measurement

Bandwidth
FUL_low – FUL_high -96 dBm 100 kHz
Figure 5-11. RBS spurious emissions into LTE.

Figure 5-12 shows the RBS spurious emission requirements for co-located RBS
in FDD mode.
Type of co-located BS Frequency range for co- Maximum Level Measurement

location Bandwidth
requirement
Macro GSM900 876-915 MHz -98 dBm 100 kHz
Macro DCS1800 1710 - 1785 MHz -98 dBm 100 kHz
Macro PCS1900 1850 - 1910 MHz -98 dBm 100 kHz
Macro GSM850 824 - 849 MHz -98 dBm 100 kHz
UTRA FDD Band I or E-UTRA Band 1 1920 - 1980 MHz -96 dBm 100 kHz
UTRA FDD Band II or E-UTRA Band 2 1850 - 1910 MHz -96 dBm 100 kHz
UTRA FDD Band III or E-UTRA Band 3 1710 - 1785 MHz -96 dBm 100 kHz
UTRA FDD Band IV or E-UTRA Band 4 1710 - 1755 MHz -96 dBm 100 kHz
UTRA FDD Band V or E-UTRA Band 5 824 - 849 MHz -96 dBm 100 kHz
UTRA FDD Band VI or E-UTRA Band 6 815 - 850 MHz -96 dBm 100 kHz
UTRA FDD Band VII or E-UTRA Band 7 2500 - 2570 MHz -96 dBm 100 KHz
UTRA FDD Band VIII or E-UTRA Band 8 880 - 915 MHz -96 dBm 100 KHz
UTRA FDD Band IX or E-UTRA Band 9 1749.9 - 1784.9 MHz -96 dBm 100 KHz
UTRA FDD Band X or E-UTRA Band 10 1710 - 1770 MHz -96 dBm 100 kHz
UTRA FDD Band XI or E-UTRA Band 11 1427.9 - 1447.9 MHz -96 dBm 100 kHz
UTRA FDD Band XII or E-UTRA Band 12 698 - 716 MHz -96 dBm 100 kHz
UTRA FDD Band XIII or E-UTRA Band 13 777 - 787 MHz -96 dBm 100 kHz
UTRA FDD Band XIV or E-UTRA Band 14 788 - 798 MHz -96 dBm 100 kHz
E-UTRA Band 17 704 - 716 MHz -96 dBm 100 kHz
Figure 5-12 RBS Spurious emission into other bands – colocated RBS FDD:
(3GPP TS 36.104 v8.9.0)
The RBS spurious emissions into different band for co-existing base-stations is
System type for E- Frequency range for Maximum Measurement Note
UTRA to co-exist co-existence Level Bandwidth
with requirement
GSM900 921 - 960 MHz -57 dBm 100 kHz This requirement does not apply to E-UTRA BS operating in band 8
876 - 915 MHz -61 dBm 100 kHz For the frequency range 880-915 MHz, this requirement does not apply to E-UTRA BS
operating in band 8, since it is already covered by the requirement for own or different
RBS
DCS1800 1805 - 1880 MHz -47 dBm 100 kHz This requirement does not apply to E-UTRA BS operating in band 3.
1710 - 1785 MHz -61 dBm 100 kHz This requirement does not apply to E-UTRA BS operating in band 3, since it is already
covered by the requirement for own or different RBS.
UTRA FDD Band I or 2110 - 2170 MHz -52 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in band 1,
E-UTRA Band 1
1920 - 1980 MHz -49 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in band 1, since it is already
covered by the requirement for own or different RBS
UTRA FDD Band VII 2620 - 2690 MHz -52 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in band 7.
or
E-UTRA Band 7 2500 - 2570 MHz -49 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in band 7, since it is already
UTRA FDD Band VIII 925 - 960 MHz -52 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in band 8.
or
UTRA FDD Band XIII 746 - 756 MHz -52 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in band 13.
or
Figure 5-13 RBS spurious emission - co-existing RBSs FDD: (3GPP TS 36.104
v8.9.0)

System type for E Frequency range Maximum Measurement Note

UTRA to co-exist for co-existence Level Bandwidth
with Requirement
UTRA TDD in Band 1900 - 1920 MHz -52 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in Band 33
a) or E-UTRA Band
33
UTRA TDD in Band a) 2010 - 2025 MHz -52 dBm 1 MHz This requirement does not apply eto E-UTRA BS operating in Band 34
or E-UTRA Band 34
UTRA TDD in Band b) 1850 – 1910 MHz -52 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in Band 35
or E-UTRA Band 35
UTRA TDD in Band b) 1930 - 1990 MHz -52 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in Band 2 and 36
or E-UTRA Band 36
UTRA TDD in Band c) 1910 - 1930 MHz -52 dBm 1 MHz This is not applicable to E-UTRA BS operating in Band 37. This unpaired
or E-UTRA Band 37 band is defined in ITU-R M.1036, but is pending any future
deployment.
UTRA TDD in Band d) 2570 – 2620 MHz -52 dBm 1 MHz This requirement does not apply to E-UTRA BS operating in Band 38.
or E-UTRA Band 38
E-UTRA Band 39 1880 – 1920MHz -52 dBm 1 MHz This is not applicable to E-UTRA BS operating in Band 39
E-UTRA Band 40 2300 – 2400MHz -52 dBm 1 MHz This is not applicable to E-UTRA BS operating in Band 40
Figure 5-14. RBS spurious emission - co-existing RBSs TDD: (3GPP TS 36.104
v8.9.0).
The UE spurious emission characteristics are specified in the 3GPP specification

36.101. An excerpt from this specification is illustrated in Figure 5-15 below.
Channel 1.4 3.0 5 10 15 20

band MHz MHz MHz MHz MHz MHz
width
ΔfOOB (MHz) 2.8 6 10 15 20 25
In order that the measurement of spurious emissions falls within the frequency
ranges that are more than ΔfOOB (MHz) from the edge of the channel bandwidth,
the minimum offset of the measurement frequency from each edge of the channel
should be ΔfOOB + MBW/2. MBW denotes the measurement bandwidth defined in
following table:
Frequency Range Maximum Level Measurement Bandwidth

9 kHz  f < 150 kHz -36 dBm 1 kHz
150 kHz  f < 30 MHz -36 dBm 10 kHz
30 MHz  f < 1000 MHz -36 dBm 100 kHz

1 GHz  f < 12.75 GHz -30 dBm 1 MHz
Figure 5-15 UE spurious emissions – 3GPP TS 36.101 v8.9.0

2 Receiver characteristics
2.1 Adjacent channel selectivity (ACS)

Adjacent Channel Selectivity (ACS) is a measure of a receiver’s ability to receive
a LTE signal at its assigned channel frequency in the presence of an adjacent
channel signal at a given frequency offset from the center frequency of the
assigned channel. ACS is the ratio of the receiver filter attenuation on the
assigned channel frequency to the receiver filter attenuation on the adjacent
channel(s). For a similar reason as that mentioned in the ACLR section, it is
Adjacent Channel Selectivity (ACS)
difficult to implement a perfect filter with low side lobe in the UE; therefore,
downlink adjacent channel interference is mainly caused by UE’s imperfect
receiver. ACS is illustrated in Figure 5-16 below.
5 MHz 5 MHz
ACS ACS
Adjacent channel Assigned channel Adjacent channel

Figure 5-16 Adjacent Channel Selectivity (ACS)
Ability to receive a WCDMA signal in the presence
of an adjacent channel
8/ 038 13 - EN/LZU 108 5173 PA2 2 WCDMA Radio Network Design R4

The RBS ACS characteristics are specified in the 3GPP specification 36.104. An
excerpt from this specification is illustrated in Figure 5-17 and below.
E-UTRA Reference sensitivity power level, PREFSENS

Reference measurement channel
channel bandwidth [MHz] [dBm]
1.4 FRC A1-1 -106.8
3 FRC A1-2 -103.0
5 FRC A1-3 -101.5
10 FRC A1-3 * -101.5
15 FRC A1-3 * -101.5
20 FRC A1-3 * -101.5
Note*: PREFSENS is the power level of a single instance of the reference measurement channel. This requirement shall be met for each
consecutive application of a single instance of FRC A1-3 mapped to disjoint frequency ranges with a width of 25 resource blocks each
Reference channel A1-1 A1-2 A1-3 A1-4 A1-5

Allocated resource blocks 6 15 25 3 9
DFT-OFDM Symbols per subframe 12 12 12 12 12
Modulation QPSK QPSK QPSK QPSK QPSK
Code rate 1/3 1/3 1/3 1/3 1/3
Payload size (bits) 600 1544 2216 256 936
Transport block CRC (bits) 24 24 24 24 24
Code block CRC size (bits) 0 0 0 0 0
Number of code blocks - C 1 1 1 1 1
Coded block size including 12bits trellis termination (bits) 1884 4716 6732 852 2892
Total number of bits per sub-frame 1728 4320 7200 864 2592
Total symbols per sub-frame 864 2160 3600 432 1296
Figure 5-17 RBS reference sensitivity levels - 3GPP TS 36.104 v8.9.0
The throughput shall be ≥ 95% of the maximum throughput of

the reference measurement channel
E-UTRA
Interfering signal centre frequency
Channel Wanted signal mean power Interfering signal
offset from the channel edge of Type of interfering signal
Bandwidth [dBm] mean power [dBm]
the wanted signal [MHz]
[MHz]
1.4 PREFSENS + 11dB* -52 0.7025 1.4MHz E-UTRA signal
3 PREFSENS + 8dB* -52 1.5075 3MHz E-UTRA signal
Note*: PREFSENS depends on the channel bandwidth as specified in RBS reference sensitivity levels.
Example: ACS (20MHz BW) =

Figure 5-18. RBS ACS (3GPP TS 36.104 v8.9.0).
From this we can calculate the ACS for a 20 MHz BW to be -52 -(-101.5 + 6) =
43.5 dB
The UE Adjacent Channel Selectivity characteristics are specified in the 3GPP

specification 36.101. An excerpt from this specification is illustrated in Figure
5-19 below.

The UE shall fulfil the minimum requirement specified in Table 7.5.1-1 for all values of an adjacent channel interferer up to
–25 dBm. However it is not possible to directly measure the ACS, instead the lower and upper range of test parameters
are chosen in Table 7.5.1-2 and Table 7.5.1-3 where the throughput shall be ≥ 95% of the maximum throughput of the
reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern
OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1).
Channel bandwidth
Rx Parameter Units 1.4 MHz 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz
ACS dB 33.0 33.0 33.0 33.0 30 27
Figure 5-19 UE ACS (3GPP TS 36.101 8.9.0).
2.2 Receiver Blocking

Blocking characteristics is a measure of a receiver’s ability to receive a static
signal at the allocated channel frequency (except adjacent channels), without
exceeding a given degradation due to the presence of an interferer at any
frequency (in the frequency band 100kHz to 12.75GHz) other than the wanted
signal frequency. Receiver blocking is illustrated in Figure 5-20 below.
Frequencies other than

spurious response or
adjacent channels
Receive Band Transmit Band

Ability to receive wanted signal in presence of an
unwanted interferer on frequencies other than those
of the spurious response or the adjacent channels
Figure 5-20 Receiver Blocking

The RBS receiver blocking characteristics are specified in the 3GPP

specification 36.104. An excerpt from this specification is illustrated in
Figure 5-21 below.
For all operating bands and technologies, the interfering

signal mean power is +16dBm for a desired signal mean
power of PREFSENS + 6dB
Figure 5-21 RBS Receiver blocking- colocation, (3GPP TS 36.104 v8.9.0)
The UE receiver blocking characteristics are specified in the 3GPP specification

36.101. An excerpt from this specification is illustrated in Figure 5-22 below.
Rx Parameter Units Channel bandwidth
1.4 MHz 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz
Wanted signal mean REFSENS + channel bandwidth specific value below

dBm
power 6 6 6 6 7 9
BWInterferer MHz 1.4 3 5 5 5 5
FIoffset, case 1 MHz 2.1+0.0125 4.5+0.0075 7.5+0.0125 7.5+0.0025 7.5+0.0075 7.5+0.0125
FIoffset, case 2 MHz 3.5+0.0075 7.5+0.0075 12.5+0.0075 12.5+0.0125 12.5+0.0025 12.5+0.0075
Note 1: The transmitter shall be set to 4dB PUMAX at the minimum uplink configuration specified in Table 7.3.1-2.
Note 2: The interferer consists of the Reference measurement channel specified in Annex A.3.2 with one sided dynamic OCNG Pattern OP.1 FDD/TDD as described in Annex
A.5.1.1/A.5.2.1 and set-up according to Annex C.3.1
E-UTRA band Parameter Units Case 1 Case 2 Case 3
PInterferer dBm -56 -44 -30

=-BW/2 - FIoffset, case 1  -BW/2- FIoffset, case 2 -BW/2 – 9 MHz
FInterferer
MHz & & &
(Offset)
=+BW/2 + FIoffset, case 1  +BW/2 + FIoffset, case 2 -BW/2 – 15 MHz
1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,12, FDL_low -15
13, FInterferer MHz (Note 2) to
33,34,35,36,37,38,39,40 FDL_high +15
17 FInterferer MHz FDL_low -9.0 FDL_low -15
(Note 2) to and
FDL_high +15 FDL_low -9.0 (Note 3)
Note
1 For certain bands, the unwanted modulated interfering signal may not fall inside the UE receive band, but within the first 15 MHz below or above the
UE receive band.
2 For each carrier frequency the requirement is valid for two frequencies:
a. the carrier frequency -BW/2 -FIoffset, case 1 and
b. the carrier frequency + BW/2 + FIoffset, case 1.
3 Finterferer range values for unwanted modulated interfering signal are interferer center frequencies.
4 Case 3 only applies to assigned UE channel bandwidth of 5 MHz.
Figure 5-22 UE Receiver blocking.

3 Adjacent channel interference

Adjacent channel interference as shown in Figure 5-23 below happens when
different systems co-exist within the same geographical area without site co-
ordination planning. They will always interfere with each other to some extend
due to the imperfections of the transmitter and receiver filter.
Two RF requirements related to adjacent channel interference were described

earlier. They are “Adjacent Channel Leakage power Ratio” (ACLR) and
“Adjacent Channel Selectivity” (ACS). To analyze the adjacent channel
interference, a new definition is used: Adjacent Channel Interference power Ratio
(ACIR). Combination of ACLR and ACS
Transmitter Carrier 1 Carrier 2 Receiver
Power Attenuation
PTX
ACLR
ACS
Figure8/ 038
5-23 Adjacent
13 - EN/LZU 108 5173 Channel
PA2 Interference 1Ratio (ACIR) WCDMA Radio Network Design R4
ACIR is the ratio of the total power transmitted from a source (can be BS or UE)
to the total interference power affecting a victim receiver as illustrated in the
equation below:
PTX
ACIR =
ITOTAL
The total interefernce (ITOTAL) is the sum of intereference due to ACLR (IACLR)
and ACS (IACS ) as below:
ITOTAL = IACLR + IACS
But

PTX
IACLR =
ACLR
and
PTX
IACS =
ACS
Therefore
PTX PTX
ITOTAL = +
ACLR ACS
If this is substituted into the equation for ACIR it becomes:
PTX 1
ACIR = =
PTX PTX 1 1
+ +
ACLR ACS ACLR ACS
Figure 5-24 Adjacent Channel Interference Ratio (ACIR).
ACIR is the ratio of the total power

transmitted from a source (can be PTX
ACIR =
BS or UE) to the total interference ITOTAL
power affecting a victim receiver.
PTX P
ITOTAL = IACLR + IACS but since IACLR = and IACS = TX
ACLR ACS
PTX PTX
ITOTAL = +
ACLR ACS
PTX 1
Therefore ACIR = =
PTX PTX 1 1
+ +
ACLR ACS ACLR ACS
Figure 5-25 Adjacent Channel Interference Ratio (ACIR).

3.1 Downlink ACIR (ACIRDL) - RBS to UE interference

For the case of adjacent channel interference between a RBS and UE the ACIR is
calculated using equation 27 as below:
1
ACIRDL = dB
1 1
+
ACLRRBS ACSUE
Equation 27 Downlink ACIR
Where ACLRRBS is that of the RBS = 45dB = 104.5
and ACSUE is that of the UE = 33dB = 103.3
This is the value of ACIR that will be used in the case of adjacent channel
interference between a RBS and UE.
For the case of adjacent channel interference between a RBS

and UE the ACIR is calculated using equation 27 as below:
1
ACIRDL = dB
1 1 Equation 27
+
ACLRRBS ACSUE
Where ACLRRBS is that of the RBS = 45dB = 104.5
and ACSUE is that of the UE = 33dB = 103.3
= 1876.8 = 32.7 dB  33dB

1
ACIRDL =
1 1
+
104.5 103.3
Figure 5-26 Downlink ACIR (ACIRDL, RBS to UE interference).

3.2 Uplink ACIR (ACIRUL) - UE to RBS interference

For the case of adjacent channel interference between a UE and RBS, the ACIR
is calculated using equation 28 as below:
1
ACIRUL = dB
1 1
+
ACLRUE ACSRBS
Equation 28 Uplink ACIR
Where ACLRUE is that of the UE = 30dB = 103.0
and ACSRBS is that of the RBS = 43.5dB (20 MHz) = 106.3
This is the value of ACIR that will be used in the case of adjacent channel
interference between a UE and RBS.
For the case of adjacent channel interference between a UE

and RBS is calculated using equation 28 as below:
1
ACIRUL = dB
1 1 Equation 28
+
ACLRUE ACSRBS
Where ACLRUE is that of the UE = 30dB = 103.0
and ACSRBS is that of the RBS = 43.5dB(20MHz)= 104.35
= 957.24 = 29.8 dB  30dB

1
ACIRDL =
1 1
+
103.0 104.35
Figure 5-27 Uplink ACIR (ACIRUL, UE to RBS interference).

4 Effect of Interference
Interference will degrade the sensitivity of the RBS and UE.
4.1 Interference effect on RBS

As illustrated in Figure 5-28 below, the minimum signal required at the RBS (the
Interference effect on RBS
sensitivity) is increased by the interference (Ni).
Noise rise RBSs ens (with interference) = RBS sens(unloaded) + NI

caused by
interference RBSs ens(unloaded) = Nt + 10log (Bw) + Nf +C/I
(NI)
C/I
Noise rise
caused by
interference Nt + 10log (Bw) + Nf Interference source
(NI)
(Aggressor)
Figure 5-28 Interference effect on RBS


4.2 Interference effect on UE

As illustrated in Figure 5-29 below, the minimum signal required at the UE (the
Interference effect on UE
sensitivity) is increased by the interference (Ni).
Noise rise UEsens (with interference) = UEsens(unloaded) + NI

caused by
interference UEsens (unloaded) = Nt + 10log (Bw) + Nf +C/I
(NI)
C/I
Noise rise
caused by
interference Nt + 10log (Bw) + Nf Interference source
(NI)
(Aggressor)
Figure 5-29 Interference effect on UE

4.3 Sensitivity degradation due to Interference

As can be seen from Figure 5-28 and Figure 5-29 the sensitivity of the RBS and
UE will be increased by the noise rise due to interference (NI) as below:
UE or RBSsens = (UE or RBSsens + NI )dBm
The noise rise due to interference is given in dB by:
Noise with Aggressor (N+Pint)

NI = 10log dB
Noise before Aggressor (N)
N Pint
NI = 10log + =10log(1+ Pint/N)
N N

Hence the sensitivity degradation due to interference can be given by equation 29

below:
Sensitivity degradation = 10log(1+ Pint/N) dB Equation 29
Equation 29 Sensitivity degradation due to interference
UE or RBSsens = (UE or RBSsens + NI )dBm
The noise rise due to interference (NI) is given in dB by:
Noise with Aggressor (N+Pint)

NI = 10log dB
Noise before Aggressor (N)
N Pint
NI = 10log + =10log(1+ Pint/N)
N N
Sensitivity degradation = 10log(1+ Pint/N) dB Equation 29
Figure 5-30 Sensitivity degradation due to interference.
Thermal noise (from chapter 4) is given by equation 30 below:
N = 10 log (KTBNf) dBm Equation 30

Equation 30 Thermal Noise
Where
K is Boltzmann’s constant = 1.38 X 10-23 J/K
B is the Bandwidth in Hz = e.g 10 x 106
Nf is the Noise figure of receiver, typically for RBS = 5dB (3.16),

UE = 7dB(5)
For the RBS (10 MHz system BW) this works out to be:
NRBS = 10log [(1.38 X 10-23 X 290 X 10 X 106 X3.16)/10-3]dBm
= -99 dBm

For the UE this works out to be:
NUE = 10log [(1.38 X 10-23 X 290 X 10 X 106 X5)/10-3]dBm
= -97 dBm
These values will be used in interference calculations.
N = 10 log (KTBNf) dBm Equation 30

K is Boltzmann’s constant = 1.38 X 10-23 J/K
B is the Bandwidth in Hz = 10 x 106
Nf is the Noise figure of a typical receiver = 5dB (3.16), UE = 7dB(5)
NRBS = 10log [(1.38 X 10-23 X 290 X 10 X 106 X3.16)/10-3]dBm

= -99 dBm
NUE = 10log [(1.38 X 10-23 X 290 X 10 X 106 X5)/10-3]dBm

= -97 dBm
Figure 5-31 Thermal Noise (N).
LTE RBS sensitivity degradation
The RBS sensitivity degradation when collocated with an GSM 1800 base station
can be calculated as follows:
Max spurious emission requirement for collocation according to 3GPP:
= -98dBm/100kHz
=> -98 + 10 log (10/0.1) = -78 dBm/10MHz
With 30 dB system isolation, the external interference Pint is calculated as:
Pint = -78 – 30 = -108 dBm
For a noise figure of 5dB, the LTE noise floor is -99dBm/10MHz and the
sensitivity degradation can be calculated according to:
Sensitivity degradation = 10 log(1 + 10-10.8/10-9.9) = 0.5 dB

Max spurious emission = -98 dBm/100kHz (according to 3GPP requirements)

=> -98 + 10 log(10/0.1) = -78dBm/10MHz (10MHz system BW example)
With 30dB system isolation, the external interference Pint is:
Pint = -78 -30 = -108 dBm
For a noise figure of 5 dB, the LTE noise floor is -99dBm/10MHz and the
sensitivity degradation is:
ΔS = 10 log (1 + Pint/N) =
10 log (1 + 10-10.8/10-9.9) = 0.5dB
Figure 5-32. LTE sensitivity degradation - GSM 1800 example.
4.4 Isolation between systems

Isolation between systems is defined as the attenuation between the transmitter
port in the interfering (aggressor) system (RBS or UE) and the receiver (Victim)
port (RBS or UE) no matter whether ASC is used or not.
Note: The reference points for calculating system isolation are different to the
RBS reference points.
In Figure 5-33 below, the downlink of one antenna i (aggressor) interferes with
the uplink of another antenna j (victim).
Antenna gain (GA,i)
Propagation loss (Lp,ij)

Antenna gain (GA,j)
α1
α2
Feeder loss (Lf,i )
Filter loss (Lx,1) Feeder loss (Lf,j )
Isolation
• •
TX RX
Aggressor Victim
Figure 5-33 Isolation between systems

The isolation between the antennas i and j in this case is given by equation 31
below.
Isolationi,j = Lf,i - GA,i + Lp,ij - GA,j + Lf,j + Lx,I + D
Equation 31 isolation between systems
Where:
Lf,i and Lf,j are the feeder losses of feeders i and j
GA,i and GA,j are the antenna gains of antennas i and j
Lp,ij is the propagation loss between antennas i and j
Lx,1 is losses in an extra filter in antenna system i
D is the coupling factor achieved by changing direction or

tilt of the main antenna lobe
When systems are operating in the same geographical area, the worst case would
be with their antennas are pointing at each other. The isolation between these
systems will be obtained by simplifying equation 31, that is, neglecting feeder
losses, considering only the nearest antenna.
Worst case is given in equation 32, that is when there are
noThe worst case of co-area isolation is given in equation 32, that is when there are
feeder or filter losses (Lf,I=, 0)Lf,j and Lx,1 = 0)
no feeder or filter losses (Lf,I, Lf,j and Lx,1
Co-area isolation the worst case = - GA,i + Lp,ij - GA,j

Equation 32 Worst case Co-area isolation
Isolationi,j = Lf,i - GA,i + Lp,ij - GA,j + Lf,j + Lx,I + D
Lf,I & Lf,j are the feeder losses of feeders i and j

GA,i & GA,j are the antenna gains of antennas i and j
Lp,ij is the propagation loss between antennas i and j
Lx,1 is losses in an extra filter in antenna system I
D is the decoupling factor achieved by tilt or change of azimuth direction
Worst case is when there are no feeder or filter losses and the antennas are
pointing towards each other (Lf,I, Lf,j, Lx,1 and D = 0)
Co-area isolation the worst case = - GA,i + Lp,ij - GA,j

Figure 5-34 Isolation (equation 31).
The path loss can, for distances in the far field zone of the antenna (>10 m), be
approximated to free space path loss.
Free space loss when d is in km and f in MHz is given by equation 33 below.
Lp = 32.4 + 20·log(d) + 20·log(f)

Equation 33 Free space path loss
Assuming the distance between RBSs is 100 m, the free space path loss for the
different frequency bands are given in Table 5-1 below.
Table 5-1 Free space path loss for 100m
Frequency band [MHz] Lp [dB]

800 70
900 71
1500 76
1800 78
1900 78
2000 78
Figure 5-35 Co-area operation.
4.5 Calculation examples

The isolation required can be calculated in the following way:

ΔS = 10 log (1 + 10Pint/10N) =>

(A tolerable value of ΔS is 0.8dB) =>
Pint = N – 6.94
(N = Nt + Nf + 10logB)
The required isolation can then be found as:
Lisol = Pem - Pint
Figure 5-36. Isolation required.

The blocking requirement Iblock for LTE eNB is 16dBm, and is specified for a
degradation ΔS of 6 dB.
The required isolation can be found as:

Lisol = PBS – Iblock
Where:
Iblock is the received interference (= +16dBm)
PBS is the output power from the aggressor BS (=43dBm)
=> Lisol = 43 -16 = 27 dB
Figure 5-37. Isolation against blocking towards LTE.
A calculation example of required isolation for colocated GSM base stations are
shown in the following figure (LTE bandwidth is assumed to be 10 MHz):
 GSM1800 max emission level: -98 dBm/100kHz

 Pem = -98 + 10 log (10/0.1) = -78 dBm
 Noise figure 5 dB
 N = -114 + 5 + 10log(10) = -99 dBm
 Pint = -6.9 – 99 = -105.9 dB
 Lisol = -78 + 105.9 = 27.9 dB
 Isolation can be achieved by adding extra filters on GSM

equipment or adapting the site solution
Figure 5-38. Isolation against spurious emissions - colocation with GSM 1800.
When the base stations are collocated, the isolation can be achieved either by
adapting the site solution or by adding extra filters on the GSM equipment.

For coexistence in the same geographical area, the minimum required physical
separation between LTE (with 0.8 dB degradation) and GSM can be estimated to
roughly 300m, according to the calculation below:
 GSM1800 max emission level: -61 dBm/100kHz

 Pem = -61 + 10 log (10/0.1) = -41 dBm
 Noise figure 5 dB
 N = -114 + 5 + 10log(10) = -99 dBm
 Pint = -6.9 – 99 = -105.9 dB
 Lisol = -41 + 105.9 = 64.9 dB
 Assuming D = 10 dB, f = 2600 MHz, Ga = Gb = 18dBi

 Lisol = 32.4 + 20log(d) + 20log(f) – (Ga + Gb) + D =>
 => d= 0.32 km
Figure 5-39. Isolation against spurious emissions - coexistence with GSM 1800.
Calculate the maximum spurious emission levels that can be tolerated can be
calculated, assuming Lisol = 30 dB:
 Assuming Lisol = 30dB, Nf = 5 dB, ΔS =0.8dB

 N=
 Pint =
 Pem =
Figure 5-40. LTE spurious emission level.

5 Collocation and coexistence for E-UTRA
5.1 E-UTRA with E-UTRA
ΔS[dB] Pem [dBm] Irx – N [dBm] Lisol [dB]

Spurious emissions, 0.8 -96/100kHz -6.9 29.9
colocation
coexistence, different
bands, E-UTRA band 7
to E-UTRA band 7
coexistence, same band
ΔS[dB] PBS [dBm] Iblock [dBm] Lisol [dB]
Blocking 6 43 16 27
Figure 5-41. Colocation and coexistence for E-UTRA with E-UTRA.
5.2 E-UTRA band 7 with GSM 1800

colocation
Blocking 6 43 16 27
Figure 5-42. Colocation and coexistence for E-UTRA band 7 with GSM 1800.
5.3 E-UTRA band 7 with UTRA band I

colocation
Blocking 6 43 16 27
Figure 5-43. Colocation and coexistence for E-UTRA band 7 with UTRA band I.

5.4 E-UTRA Band 13 with CDMA 2000 band 0

The spurious emission limits in CDMA 2000 for collocated and coexisting base
stations are for further reference, and isolation figures are not calculated.
Collisions do not occur between the operating bands for E-UTRA Band 13 and
CDMA 2000 Band 0, so guard bands are unnecessary. In this case, no additional
actions are required beyond using appropriate filters.
5.5 Colocation solutions
5.5.1 Colocation with separate antenna systems

The antennas for LTE and the other system is separated vertically or horizontally,
at a certain distance (see Figure 5-44), pointing parallel or away from each other.
When horizontal separation is used, the azimuths should not intersect.
When vertical separation is used, the tilting angles should not intersect.
Horizontal Beam Width GSM 900 GSM1800/GSM19 GSM900 with

(directional antennas) only [m] 00/UMTS/LTE GSM1800/GSM1800/GS
only [m] M1900/UMTS/LTE [m]
65 ± 10 0.4 0.2 0.3
90 ± 10 1.0 0.5 0.5
105 ± 10 1.5 0.7 0.7

120 ± 10 2.0 1.0 1.0
180 ± 10 5.0 2.5 2.5
Antenna Gain
(omni antennas)
< 10 3.0 1.5 1.0
> 10 5.0 2.5 1.0
For vertical separation, the minimum distance is 0.2m

Figure 5-44. Horizontal and vertical separation for colocated antennas.

5.5.2 Colocation with dual diplexer and shared mast feeder

In this solution there are two diplexers. The first diplexer combines the LTE
Tx/Rx and the Tx/Rx for the other technology from each base station to a single
feeder, which ascends the mast. A second diplexer splits the two into separate
ASC/TMA/antennas. These antennas should have at least 30 dB antenna
isolation. The first diplexer should be at least 50 dB, and the main concern is
inter-modulation products of the third order generated after the first diplexer.
>30dB
isolation
Shared feeder
WCDMA ASC
TMA
Diplexer
>50dB inter-
Diplexer
modulation
suppression
LTE WCDMA/GSM
Figure 5-45. Feeder sharing and separate antennas.

5.5.3 Colocation with shared antenna

The existing Tx/Rx antenna is replaced with an antenna covering both LTE and
the other technology (this is actually two antennas in the same radome). This
antenna must have at least 30 dB isolation between LTE and the other
technology.
Shared antenna >30dB

isolation LTE – other
technology
TMA Diplexer WCDMA ASC
LTE WCDMA/GSM
Figure 5-46. Shared antenna only.

5.6 Near-far problem

For the base station to mobile scenario, an essential issue is the Near-Far effect.
Assume an LTE system is deployed in the same geographical area using adjacent
frequency blocks.
Co-site
Co-area
interference
interference
Near-far
effect
Operator A
Operator B
Same site Operator C
Figure 5-47. Co-existence interference scenarios.
In Figure 5-47, system A represents the LTE system and system B and C
represents a system of another technology. When a mobile from system A is
located near a base station from system C, it can cause interference for the
receiver of the system C base station, and the reverse also applies. When the user
equipment of system A is located far away from the base station of system A, but
close to the base station of system C, significant interference can occur, because
the mobile transmits at high power to overcome the high pathloss. If different
operators colocate base stations on the same sites, the Near-Far effect is
eliminated.

LTE Cell Planning and Hardware
6 LTE Cell Planning and Hardware
Top right
Slide title
40 pt Objectives
Objectives of Chapter 5 corner for
field-mark,
customer or
Slide subtitle LTE Cell Planning and Hardware partner logotypes.
for example.
Text
24 pt After this chapter the participants will be able to:
Bullets level 2-5
20 pt 1. Explain the tools and hardware associated with LTE cell
planning.
2. Explain the downlink and uplink analysis supported by the
TEMS CellPlanner LTE module.
3. List the Ericsson products in the RBS 6000 family.
4. Explain the hardware structure and capabilities of the RBS
6201 and 6102.

. Rev A Figure 5 - 1 LTE Cell Planning and Hardware

1 TEMS CellPlanner LTE Module

The TEMS CellPlanner (TCP) LTE module uses a choice of path loss models to
predict and plot the pathloss between the RBS and UE antenna as illustrated in
Figure 6-2 below.
Top right
Slide title
40 pt
TEMS Cellplanner LTE Pathloss Plot corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-2 TEMS CellPlanner LTE Pathloss Plot
The status bar along the bottom of the screen continually displays the coordinates
and path loss to the serving cell. In the illustration in Figure 6-2 above the grid
reference position East 1,620,824 North 6,589,266 is served by RBS-9 cell B1
with a pathloss of 98.72 dB.
The pathloss prediction is the used to produce the following plots:

 Downlink estimated average SINR for a given load
 Downlink RB data rate for a given load
 Downlink data rate for a given load
 Uplink maximum SINR for a Monte-Carlo simulated load
 Uplink RB data rate for a Monte-Carlo simulated load
 Uplink data rate for a Monte-Carlo simulated load
 LTE Neighbour analysis

1.1 Downlink SINR for a given load

Using the pathloss prediction the TCP LTE module is able to produce a plot of
the SINR for a given system load. The TCP downlink SINR plot in Figure 6-3
has been produced for a downlink system load of 60% (percentage of used RBs).
Top right
Slide title
40 pt
DL SINR (60% Load) corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-3 DL SINR (60% Load)
From the plot in Figure 6-3 above it can be seen that the downlink SINR can be
quite low where the sectors overlap due inter-cell interference. The cell planner
should try to minimize this with various antenna beam-widths and down-tilts. As
there will always be some overlap between sectors care should be taken to ensure
that this does not happen in areas of high traffic.
The status bar along the bottom of the screen continually displays the
coordinates, serving cell and DL SINR. In the illustration in Figure 6-3 above the
grid reference position East 1,620,824 North 6,589,266 is served by RBS-9 cell
B1 with a downlink SINR of 8.84 dB.
1.2 Downlink RB data rate for a given load

Based on the downlink SINR plot the TCP LTE module is able to produce a plot
of the corresponding downlink Resource Block (RB) data rate for a given channel
model, UE speed and transmission scheme. The coverage plot illustrated in
Figure 6-4 below shows the possible downlink RB data rate for the Enhanced
Pedestrian A (EPA) channel model assuming a UE speed of 2.1 km/h, 2X2
MIMO transmission scheme with a system load of 60%.

Top right
Slide title
40 pt
DL RB Data Rate (60% Load) corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-4 DL RB Data Rate (60% Load)
From the plot in Figure 6-4 above it can be seen that the downlink RB data rate
can be quite low where the sectors overlap due inter-cell interference. The cell
planner should try to ensure that the highest downlink RB data rate is supported
in the areas of highest traffic concentration.
coordinates, serving cell and downlink RB data rate. In the illustration in Figure
6-4 above the grid reference East 1,620,824 North 6,589,266 is served by RBS-9
cell with a downlink RB data rate of 237 kbps.
1.3 Downlink data rate for a given load

Based on the number of available RBs in the channel bandwidth and the
downlink RB data rate, the TCP LTE module can produce a plot of the downlink
data rate for a given system load assuming all RBs were used to support the LTE
bearer. The downlink data rate plot illustrated in Figure 6-4 below shows the
possible downlink LTE bearer data rate for the Enhanced Pedestrian A (EPA)
channel model assuming a UE speed of 2.1 km/h, 2X2 MIMO transmission
scheme, 20 MHz channel bandwidth (100 RBs) and a system load of 60%.

Top right
Slide title
40 pt
DL Data Rate (60% Load) corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-5 DL Data Rate (60% Load)
From Figure 6-5 above it can be seen that the lowest downlink data rate in the
area to be covered is 422 kbps. This value should be greater than the cell edge
throughput requirement of the network.
coordinates, serving cell and downlink data rate. In the illustration in Figure 6-5
above the grid reference position East 1,620,824 North 6,589,266 is served by
RBS-9 cell B1 with a downlink data rate of 23729 kbps or approximately 24
Mbps.
1.4 Uplink maximum SINR for a Monte-Carlo load

Since uplink interference is dependant on the location of the UE with respect to
neighbouring base stations a process of ‘Monte-Carlo’ analysis is used to predict
the typical network performance for a given number of UEs distributed
throughout the network. A configurable number of simulations, each using a
pseudo-random distribution of UE in the network are used to produce an average
indication of the uplink network performance. The uplink maximum SINR after
100 Monte-Carlo simulations is illustrated in Figure 6-6 below.

Top right
Slide title
40 pt
UL Max SINR (Monte-Carlo Load) corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-6 UL Max SINR (Monte-Carlo Load)
From Figure 6-6 above it can be seen that the uplink SINR (estimated using
Monte Carlo) can also be quite low where the sectors overlap due interference
from UEs in other cells. As with the downlink, the cell planner should try to
minimize this with various antenna beam-widths and down-tilts.
coordinates, serving cell and uplink maximum SINR. In the illustration in Figure
6-6 above the grid reference position East 1,620,824 North 6,589,266 is served
by RBS-9 cell B1 and would support an uplink maximum SINR of 19.56 dB.
1.5 Uplink RB data rate for a Monte-Carlo load

Based on the uplink maximum SINR plot the TCP LTE module is able to
produce a plot of the corresponding uplink Resource Block (RB) data rate for a
given channel model and UE speed. The coverage plot illustrated in Figure 6-7
below shows the possible uplink RB data rate for the Enhanced Pedestrian A
(EPA) channel model assuming a UE speed of 2.1 km/h based on the results of
the previous Monte-Carlo analysis.

Top right
Slide title
40 pt
UL RB Data Rate (Monte-Carlo Load) corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-7 UL RB Data Rate (Monte-Carlo Load)
From the plot in Figure 6-7 above it can be seen that the uplink RB data rate can
be quite low where the sectors overlap due interference from UEs in other cells.
The cell planner should try to ensure that the highest uplink RB data rate is
supported in the areas of highest traffic concentration.
coordinates, serving cell and uplink RB data rate. In the illustration in Figure 6-7
RBS-9 cell B1 and would support an uplink RB data rate of 589 kbps.
1.6 Uplink data rate for a Monte-Carlo Simulated load

Based on the number of available RBs in the channel bandwidth minus the
number reserved for PUCCH and the uplink RB data rate, the TCP LTE module
can produce a plot of the uplink data rate for a given system load assuming all
RBs are used to support the LTE bearer. The coverage plot illustrated in Figure
6-8 below shows the possible uplink LTE bearer data rate for the Enhanced
Pedestrian A (EPA) channel model assuming a UE speed of 2.1 km/h, 20 MHz
channel bandwidth (100 – 6 = 94 RBs) based on the results of the previous
Monte-Carlo analysis.

Top right
Slide title
40 pt
UL Data Rate (Monte-Carlo Load) corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-8 UL Data Rate (Monte-Carlo Load)
From Figure 6-8 above it can be seen that the lowest downlink data rate in the
area to be covered is 5.184 X 103 kbps or 5.184 Mbps. This value should be
greater than the cell edge throughput requirement of the network.
coordinates, serving cell and uplink data rate. In the illustration in Figure 6-8
RBS-9 cell B1 with an uplink data rate of 55352 kbps or approximately 55 Mbps.
1.7 LTE Neighbour analysis

The TEMS CellPlanner LTE module also includes a Neighbor list Analysis
function which may be used to generate a list of neighbors for a given number of
sites and LTE traffic case as illustrated in Figure 6-9 below.

Top right
Slide title
40 pt
LTE Neighbor Analysis corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-9 LTE Neighbor Analysis
For each cell using the same carrier as defined in the selected traffic case, the
analysis evaluates possible neighbor cells. Neighbor cells are the cells to/from
which handover is possible from/to the analyzed cell (based on signal strength,
RSRP). For each analyzed cell, the analysis presents the cells allowing handover
in a neighbor list. These neighbors are accepted by applying the list.
It is possible to override this automatic selection by moving cells between the

neighbor list and a waiting list (still possible candidates), an error list (rejected
candidates) and a list with all other cells.
The generated neighbor lists can be exported, and existing neighbor lists can be
imported into TCP.

Top right
Slide title
40 pt
LTE Neighbor Analysis Results
Figure 6-10 below shows an example result of the LTE Neighbor Analysis corner for
field-mark,
function. customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt
Figure 6-10 LTE Neighbor

. Rev A
Analysis
Figure 5 - 10
Results LTE Cell Planning and Hardware
The neighbors of particular cells can also be graphically displayed as illustrated

in Figure 6-11 below.
Top right
Slide title
40 pt
LTE Neighbor Analysis Plot corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt

Figure 6-11 LTE Neighbor Analysis Plot

TEMS Cell Planner also includes a feature for automatic cell planning, called
ACP (Automatic Cell Planning).
Top right
Slide title corner for
2 RBS 6000 Family
40 pt
RBS 6000 Family field-mark,
customer or
Slide subtitle The RBS 6000 Product Family illustrated in Figure 6-12 below is designed to partner logotyp
24 pt See Best practi
support a mix of GSM, WCDMA and LTE in the same RBS and ensure a smooth
for example.
transition to next-generation technologies, while providing exceptional GSM and
Text WCDMA capacity to meet current and future market needs.
24 pt
Bullets level 2-5
20 pt RBS 6102 RBS 6101 RBS 6201 RBS 6601 RRU RBS 6301
Figure 6-12 RBS 6000 Family
The RBS 6102 outdoor macro base station contains radio, transmission and
battery backup to support a complete site in a single cabinet with a footprint of
2 7263 Uen
just
© Ericsson AB 2008 0.9LZU
05_03813 m108(1300×700
. Rev A mm).
Figure 5 - 2It supports maximum configurations of 6 x 12
LTE Implementation
GSM, 6 x 4 WCDMA with MIMO or 6 x 20 MHz LTE with MIMO or a

combination of smaller mixed configurations.
The RBS 6101 outdoor macro base station supports the same configurations as
the RBS 6102 but without the battery backup.
The RBS 6201 is an indoor version of the 6101.
All these RBSs can be used in conjunction with the LTE Remote Radio Unit
(RRU) to support a ‘main-remote’ RBS solution.
The RBS 6601 is a very small indoor main unit that can be deployed inside other
cabinets that are already at the site. One LTE product will be realized as an RBS
6601 main unit with LTE RRUs, a solution that can be deployed very flexibly
even at very challenging sites with minimal space available
The RBS 6301 is a low capacity, very compact main unit for main-remote site
configurations or as a micro replacement. Typical applications are dense urban
environment or indoor solutions, both cases where the power grid can be so
reliable that battery back up is not needed while a small outline is essential.

2.1 RBS 6000 Hardware Architecture

All RBS 6000 products contain a number of Radio Units (RUs), Digital Units Top right
Slide title
40 pt RBS 6000 Hardware Architecture
(DUs) and space for transmission equipment as illustrated in the examples for the
RBS 6102 and 6201 in Figure 6-13 below.
corner for
field-mark,
customer or
for example.
Text Radio Units (RUs)

24 pt
Bullets level 2-5
20 pt
Digital Units (DUs)
Batteries Transmission Equipment

Figure 6-13 RBS 6000 Hardware Architecture
. Rev A Figure 5 - 3 LTE Implementation
The RBS 6102 also has space for battery backup as illustrated in Figure 6-13
above.
The Radio Unit (RU) contains the following components:

 Transceiver (TRX)
 Transmitter (TX) amplification
 Transmitter/Receiver (TX/RX) duplexing
 TX/RX filtering
 Voltage Standing Wave Ratio (VSWR) support
The Digital Unit (DU) contains the following components:

 Control processing
 Clock distribution
 Synchronization from transport interface or GPS
 Baseband processing
 Transport network interface
 RU interconnects
 Site Local Area Network (LAN) and maintenance interface

Top rig
Separate RUs and DUs are used for GSM (RUG and DUG), WCDMA (RUW
Slide title
40 pt RBS 6000 RU and DU Variants
and DUW) and LTE (RUL, DUL) as illustrated in Figure 6-14 below.
corner
field-ma
custom
Slide subtitle RU21
partner
2130
24 pt See Be
2100
TX
All
TX
GSM Dat
a
for exam
D F
P I
O
FU
U Ctrl
Text RX
B
RX
A
24 pt Power
Bullets level 2-5

20 pt DUG RUG
DXU DRU
RU21
2130
2100
WCDMA
RU21
2130
2100
FU12
RU21 21
2130 TX
2100 2100
All
TX TX
All
TX
TX
All
TX RX
A2
RX
A1 Dat
a
Ant A
Dat
D a
Dat
a
P
F
I
O D
FU F
U Ctrl
P I
O
FU
F F
I
O
FU
O
I U Ctrl
Ctrl Ctrl
RX
B
RX
B
RX
RX A
B RX
Ant
B A
Power
RX
A Power
Power
RX
B1
DUW RUW DUS RUS

BB RU FU
RU21
2130
2100
TX
All
TX
LTE
Dat
a
D
F
P I
O
FU
U Ctrl
RX
B
RX
A
Power
DUL RUL
Figure 6-14 RBS 6000 RU and DU Variants

. Rev A Figure 5 - 4 LTE Implementation
As the RBS 6000 product evolves GSM, WCDMA and LTE will be supported by
the RUS and DUS as illustrated in Figure 6-14 above.

2.1.1 Radio Unit for LTE (RUL)

The RUL supports 60 W output power with a bandwidth of 20 MHz. Multiple
RULs can be combined into different radio configurations from 1 to 6 sectors and
up to 20 MHz for single or dual band configurations as illustrated in Figure 6-15 Top right
Slide title
40 pt Radio Unit LTE Configurations
below. corner for
field-mark,
customer or
for example.
Text
24 pt Configuration No of RUs Output Power (W)
Bullets level 2-5
20 pt
3 X 20 3 60
3 X 20 MIMO 6 60 + 60
6 X 20 6 60
6 X 20 MIMO 12 60 + 60
3 X 20 | 3 X 20 (Dual Band) 3|3 60 | 60
3 X 20 | 3 X 20 MIMO (Dual Band) 6|6 60 + 60 | 60 + 60
Figure 6-15 Radio Unit LTEFigure

Configurations
5-5 . Rev A LTE Implementation
2.1.2 Digital Unit for LTE (DUL)

The DUL contains the baseband, control, and switching, as well as the S1 and
Mub interfaces for LTE RBSs. The DUL supports different time-varying traffic
mixes over the LTE high-speed data interface.
Baseband resources are pooled in the DUL and the high-speed data capacity can
be optimized to fit operator requirements for user type and number of services.
The baseband capacity is pooled independently of sectors and frequencies, and up

to two baseband pools can exist (two DUL units) in the same node.
The baseband complies with 3GPP standards and is fully integrated with the
same O&M system as the RBS 3000 family. The software can be downloaded
through the OSS-RC, either locally or through an access gateway, and is stored in
non-volatile memory in the RBS.
The Digital Unit for LTE (DUL) comes in two variants supporting different
capacities as illustrated in Figure 6-16 below.

LTE Cell Planning and Hardware Top right
Slide title
40 pt Digital Unit LTE Varients corner for
field-mark,
customer or
for example.
Text
24 pt
Bullets level 2-5
20 pt
Configuration DUL-20 DUL-30
DL Peak Throughput (Mbps) 150 300
UL Peak Throughput (Mbps) 50 100
Number of Users 500 1000

.
Figure 5 - 6Rev A LTE Implementation
Figure 6-16 Digital Unit LTE Variants
The RBS 6000 family software platform provides generic support for the
application software and includes an execution platform with operating system,
IP transport, and O&M infrastructure.
The DUL stabilizes the clock signal extracted from the transport network
connection or optional external GPS equipment and uses it to synchronize the
RBS.
The DUL provides:
 Full IP connectivity
 A gigabit Ethernet transport network interface
Additional interfaces and transport network configurations are available as

options.

Intentionally Blank

Table of Figures
7 Abbreviations
3GPP 3rd Generation Partnership Project

rd
3PP 3 Party Product
A working group within IETF that produced a standard for E.164
ENUM
number and DNS. Defined in IETF RFC 2916.
AGW Access Gateway
APN Access Point Name
A-SBG Access SBG
AS Access Stratum
A-RACF Access-Resource Admission Control Function
AM Acknowledged Mode
ACK Acknowledgement
AMR Adaptive Multi-Rate
ARW Add RBS Wizard
A-MPR Additional Maximum Power Reduction
ACM Address Complete Message (ISUP Message)
ACIR Adjacent Channel Interference Ratio
ACLR Adjacent Channel Leakage Ratio
ACS Adjacent Channel Selectivity
ASSL Adjacent Subcarrier Set Leakage
ASSR Adjacent Subcarrier Set Rejection
AES Advanced Encryption Standard
AMBR Aggregate Maximum Bit Rate
AP Aggregation Proxy
ARP Allocation and Retention Priority
ANM Answer Message (ISUP Message)
AISG Antenna Interface Standards Group
ASC Antenna System Controller
API Application Programming Interface
APAC Asia Pacific
AKA Authentication and Key Agreement
AuC Authentication Centre
AV Authentication Vector
AAA Authentication, Authorization and Accounting
AIF Auto-Integration Function
AIR Automated Integration of RBS

ANR Automated Neighbor Relation

ACP Automatic Cell Planning
ARQ Automatic Repeat Request
ASD Automatic SW Download
ARPU Average Revenue Per User
BE-DB Back End Database
B2B UA Back To Back User Agent
BW Bandwidth
BS Base Station
BFCP Binary Floor Control Protocol
BEM Block Edge Masks
BGF Border Gateway Function
BGCF Breakout Gateway Control Function
BB Broadband
BCH Broadcast Channel
BCCH Broadcast Control Channel
BM-SC Broadcast-Multicast Service Center
BSR Buffer Status Report
BCE Business Communication Enabler
CDIV Call Diversion
CSCF Call Session Control Function
CX-AS Capability Exchange Application System
CAPEX Capital Expenditure
CAPEX Capital Expenditure
CE Carrier Ethernet
CIC Carrier Identification Code
C/I Carrier-to-Interference Power Ratio
IWS CDMA200 InterWorking Solution
C-RNTI Cell RNTI
CTR Cell TRace
CUDB Centralized User Database
CA Certificate Authority
CFR Channel Feedback Report
CQI Channel Quality Indicator
CS Circuit Switched
CSFB Circuit Switched FallBack
CDMA Code Division Multiple Access
CW Codeword
CSV Comma-Separated Values
CCCH Common Control Channel
COMINF Common O&M Infrastructure
CORBA Common Object Request Broker Architecture
CoH Conference Handler
CO Conference Owner
CM Configuration Management
CMDB Configuration Management Data Base
CMC Connection Mobility Control
CAZAC Constant Amplitude Zero Auto-Correlation
CFRA Contention Free Random Access
CPC Continous Packet Connectivity
CCE Control Channel Elements
CP Control Plane
C-plane Control Plane

Table of Figures
CPM Converged IP Messaging

CO-OP Cooperative Open-OSS Project (interface also called Itf-P2P)
C-BGF Core Border Gateway Function
CN Core Network
Counter Cipher Mode with Block Chaining Message Authentication
CCMP
Code Protocol
CDF Cumulative Distribution Function
CAI Customer Administration Interface
CAS Customer Administration System
CDD Cyclic Delay Diversity
CRC Cyclic Redundancy Check
DCN Data Communication Network
DRB Data Radio Bearer
DCH Dedicated Channel
DCCH Dedicated Control Channel
DTCH Dedicated Traffic Channel
DBS/SABE Delay Based Scheduling/Service Aware Buffer Estimation
DFT-S-
DFT Spread OFDM
OFDM
Diameter represents the next generation of authentication,
Diameter authorization, and accounting (AAA) controls for network access,
optimized for mobile access and advanced services
DSCP Differentiated Services Code Point
DECT Digital Enhanced Cordless Telecommunications
DSL Digital Subscriber Line
DRX Discontinuous Reception
DTX Discontinuous Transmission
DFT Discrete Fourier Transform
DNS Domain Name Service
Domain Name System (Defined in STD 13, RFC 1034, RFC 1035 and
DNS
a number of following RFCs.)
DL Downlink
DCI Downlink Control Information
DwPTS Downlink Pilot Time Slot
DL-SCH Downlink Shared Channel
DBL Dynamic Black List
DHCP Dynamic Host Configuration Protocol
DHCP Dynamic Host Configuration Protocol
ETWS Earth Quake and Tsunami Warning System
ECC Electronic Communications Committee
E-CSCF Emergency-CSCF
E-DCH Enhanced DCH
e-GEM Enhanced Generic Ericsson Magazine
e-GEM 2 Enhanced Generic Ericsson Magazine 2:nd version
ECM EPS Connection Management
EMM EPS Mobility Management
ESM EPS Subscriber Module
EHPLMN Equivalent Home PLMN
EBS Ericsson Blade System
EMA Ericsson Multi-Activation
EPC Ericsson Policy Control
TSP Ericsson Telecom Server Platform
EVM Error Vector Magnitude

EMEA Europe, Middle East and Africa

ETSI European Telecommunications Standards Institute
ECGI E-UTRAN Cell Global Identifier
eNB E-UTRAN NodeB
eNode B E-UTRAN NodeB
E-RAB E-UTRAN Radio Access Bearer
EV-DO Evolution - Data Optimized
EPS Evolved Packet System
E-UTRA Evolved UTRA
E-UTRAN Evolved UTRAN, used as synonym for LTE in the document.
XML eXtensible Markup Language
XML Extensible Markup Language
EXB Extension Blade
eDNS External DNS
FFT Fast Fourier Transform
FM Fault Management
FMX Fault Management Expert
FCC Federal Communications Commission
FTP File Transfer Protocol
FW Fire Wall
FMC Fixed-Mobile Convergence
FFS For Further Study
FEC Forward Error Correction
FS Frame Structure
FDD Frequency Division Duplex
FDMA Frequency Division Multiple Access
FDM Frequency Division Multiplexing
FQDN Fully Qualified Domain Name
GINR Gain to Interference and Noise Ratio
GW Gateway
GGSN Gateway GPRS Support Node
GPRS General Packet Radio Service
GSTN General Switched Telephone Network (PSTN + PLMN)
GCL Generalized Chirp Like
GMPLS Generalized Multi-Protocol Label Switching
GE Gigabit Ethernet
GNSS Global Navigation Satellite System
GSM Global System for Mobile communication
GUTI Globally Unique Temporary Identifier
GIBA GPRS IMS Bundled Authentication
GTP GPRS Tunneling Protocol
GUI Graphical user Interface
GSMA GSM Association
GERAN GSM EDGE Radio Access Network
GTP-C GTP Control
GTP-U GTP User Data Tunneling
GBR Guaranteed Bit Rate
GP Guard Period
HO Handover
HW Hardware
HW Hardware
HP Hewlett Packard
HA-CS High Availability Cluster Solution

Table of Figures
HD High Definition
HDVC High Quality Video Conferencing
HRPD High Rate Packet Data
HSDPA High Speed Downlink Packet Access
HS-DSCH High Speed Downlink Shared Channel
HSPA High Speed Packet Access
HSUPA High Speed Uplink Packet Access
HOM Higher Order Modulation
HLR Home Location Register
HPLMN Home PLMN
HSS Home Subscriber Server
HSS-FE HSS Front End
HARQ Hybrid ARQ
HTTP Hypertext Transfer Protocol
HTTP Hypertext Transfer Protocol
HTTPS Hypertext Transfer Protocol over Secure Socket Layer
ID Identifier
SSLIOP IIOP over SSL
ICS IMS Centralized Services
CoSe IMS Communication Services
IMS-M IMS Messaging
IMT IMS Multimedia Telephony
ISC IMS Service Control interface. (Defined in 3GPP TS 23.228)
ISIM IMS SIM
ISM IMS Subscriber Module
ICB Incoming Call Barring
IMSI Individual Mobile Subscriber Identity
IM Instant Messaging
IEEE Institute of Electrical and Electronics Engineers
ISDN Integrated Services Digital Network
IS Integrated Site
ISER Integrated Site Edge Router
IRAT Inter Radio Access Technology
IRAT Inter Radio Access Technology
ISI Inter Symbol Interference
IASA Inter-Access Anchor
ICIC Inter-Cell Interference Coordination
IBCF Interconnection Border Control Function
I-BGF Interconnection Border Gateway Function
iDNS Internal DNS
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
International Public Telecommunication Numbering Plan as describe in
E.164
the ITU-T Recommendation E.164.
ITU International Telecommunications Union
IETF Internet Engineering Task Force
IP Internet Protocol
IPTV Internet Protocol Television (Television over IP)
Ipv4 Internet Protocol version 4. (Defined in IETF STD 5 and RFC 791).
Ipv6 Internet Protocol version 6.(Defined in IETF RFC 2460)
I-CSCF Interrogating CSCF
IWF Interworking function
IFFT Inverse FFT

IMPI IP Multimedia Private Identity

IMS IP Multimedia subsystem
IPSec IP Security
IPW IPWorks
ISUP ISDN User Part
ITU-R ITU Radio communication Sector
JCP Java Community Process
JSR Java Specification Request
KPI Key Performance Indicator
LED Light Emitting Diode
LDAP Lightweight Directory Access Protocol. (Defined in IETF RFC 1777)
LDC Linear Dispersion Code
LB Load Balancing
LAN Local Area Network
LCID Logical Channel ID
LTE Long Term Evolution
LCR Low Chip Rate
LCR-TDD Low Chip Rate TDD
LDPC Low-Density Parity-check Code
MXB Main Switching Blade
MCID Malicious Communication Identification
MCR Malicious Communication Rejection
MOCI Managed Object Configuration Interface
MBA Management Based Activation
MIB Management Information Base
MS Management Services
MBR Maximum Bit Rate
MOP Maximum Output Power
MPR Maximum Power Reduction
mUPE MBMS UPE
MSAP MCH Subframe Allocation Pattern
MOS Mean Opinion Score
MGW Media Gateway
MeGaCo Media Gateway Control Protocol (also referred to as H.248)
MGC Media Gateway Controller
MGCF Media Gateway Controller Function
MP Media Proxy
MRFC Media Resource Function Controller
MRFP Media Resource Function Processor
MRS Media Resource System
MAC Medium Access Control
MiO Messaging in One
MAP Mobile Application Part
MEF Mobile Entertainment Forum
M-MGw Mobile Media Gateway
MNP Mobile Number Portability
MSS Mobile Softswitch Solution
MSISDN Mobile Subscriber Integrated Services Digital Network-Number
MSC Mobile Switching Center
MM Mobility Management
MME Mobility Management Entity
MCS Modulation and Coding Scheme
M3UA MTP Level 3 (MTP3) User Adaptation Layer

Table of Figures
MMTel Multi Media Telephony

MSP Multi Service Proxy
MBSFN Multicast Broadcast Single Frequency Network
MCH Multicast Channel
MCCH Multicast Control Channel
MTCH Multicast Traffic Channel
MCE Multi-cell/multicast Coordination Entity
ML-PPP Multilink point to point protocol
MAR/MAA Multimedia Authentication Request/Answer (Diameter Message)
MBMS Multimedia Broadcast Multicast Service
MMS Multimedia Messaging Service Managed Objects interface (MOCI)
MTAS Multimedia Telephony Application Server
MIMO Multiple Input Multiple Output
MPLS Multiple Protocol Label Switching
MU-MIMO Multiple User-MIMO
NAB Name and Address Book
NB Narrowband
NBA NASS Bundled Authentication
NENA National Emergency Number Association
NACK Negative Acknowledgement
NR Neighbor cell Relation
NCL Neighbour Cell List
NCS Neighbouring Cell Support
NW Network
NNI Network – Network Interface
NAI Network Access Identifier
NAT Network Address Translation
NASS Network Attachment Subsystem
NCC Network Color Code
NE Network Element
NEM Network Element Manager
NMX Network level deployment of expert rules
NM Network Management
NMS Network Management System
NOC Network Operations Center
N-SBG Network SBG
NSP Network Server Platform
NGMN Next Generation Mobile Networks
NGSA Next Generation Service Assurance
NH Next Hop Key
NCLI Node Command Line Interface
NRT Non Real Time
NAS Non-Access Stratum
OMA Open Mobile Alliance
OPEX Operating Expenditures
operating mode of CDMA2000. 1x (the number of 1.25MHz channels)
1XRTT
Radio Transmission Technology
O&M Operation and Maintenance
OMC Operation and Maintenance Center
OSS Operation and Support System
OSS-RC Operation and Support System Radio and Core
OAM Operations Administration and Management
OTN Operator Terminal Network

OFDMA Orthogonal Frequency Division Multiple Access

OFDM Orthogonal Frequency Division Multiplexing
OOB Out Of Band
OCB Outgoing Call barring
PANI P-Access-Network-Info (SIP Header)
PBN Packet Backbone Network
PDCP Packet Data Convergence Protocol
PDN Packet Data Network
PDN-GW Packet Data Network Gateway
PDP Packet Data Protocol
Packet Data Serving Node is a component of a CDMA2000 mobile
PDSN
network
PDB Packet Delay Budget
PSC Packet Scheduling
PS Packet Switched
P(N)CCH Paging (and Notification) Control Channel
PCH Paging Channel
PCCH Paging Control Channel
P-RNTI Paging RNTI
P-GW PDN Gateway
PAPR Peak to Average Power Ratio
PAR Peak to Average Ratio
P2P Peer-to-Peer
PARC Per Antenna Rate Control
PM Performance Management
PRD Permanent Reference Document (by GSMA)
PC Personal Computer
PHS Personal Handy-phone System
PBCH Physical Broadcast CHannel
PCI Physical Cell ID
PCFICH Physical Control Format Indicator CHannel
PDCCH Physical Downlink Control CHannel
PDSCH Physical Downlink Shared CHannel
PHICH Physical Hybrid ARQ Indicator CHannel
PHY Physical layer
PMCH Physical Multicast CHannel
PRACH Physical Random Access CHannel
PRB Physical Resource Block
PUCCH Physical Uplink Control CHannel
PUSCH Physical Uplink Shared Channel
PnP Plug and Play
PoP Point of Presence
PCC Policy and Charging Control
PCRF Policy and Charging Rules Function
PCEF Policy Charging Enforcement Function
PA Power Amplifier
PBC Power and Battery Cabinet
PHR Power Headroom Report
PSD Power Spectrum Density
PMI Precoding Matrix Indicator
PGM Presence Group and Data Management
PSK Pre-Shared Keys
P-SCH Primary Synchronization Channel

Table of Figures
PBR Prioritized Bit Rate

PCO Protocol Configuration Option
PDU Protocol Data Unit
PBBTE Provider Backbone Bridge Traffic Engineering
P-CSCF Proxy - Call Session Control Function
PMIP Proxy Mobile IP
PLMN Public Land Mobile Network
PSTN Public Switched Telephone Network
PUI Public User Identity
PCM Pulse Code Modulation
PTT Push To Talk
QCI QoS Class Identifier
QAM Quadrature Amplitude Modulation
QPP Quadrature Permutation Polynomial
QPSK Quadrature Phase Shift Keying
QoS Quality of Service
RAN Radio Access Network
RAN Radio Access Network
RAT Radio Access Technology
RAC Radio Admission Control
RBS Radio Base Station
RB Radio Bearer
RBC Radio Bearer Control
RBG Radio Bearer Group
RF Radio Frequency
RLC Radio Link Control
RNC Radio Network Controller
RNL Radio Network Layer
RNTI Radio Network Temporary Identifier
RRU Radio Remote Unit
RRC Radio Resource Control
RRM Radio Resource Management
RANAP RAN Application Part
RA Random Access
RACH Random Access Channel
RA-RNTI Random Access RNTI
RI Rank Indicator
RM Rate Matching
RT Real Time
RTP Real Time Protocol
RTSP Real Time Streaming Protocol
RX Receiver
ROP Recording Output Periods
RS Reference Signal
RPLMN Registered PLMN
RA Registration Authority
Remote Authentication Dial In User Service (Defined in RFC 2865,
RADIUS
RFC 2866 and RFC 2869)
RET Remote Electrical Tilt
RFC Request For Comment
RU Resource Unit
RSN Retransmission SN
RCS Rich Communication Suite

RCS-e Rich Communication Suite-enhanced

RoHC Robust Header Compression
RTCP RTP Control Protocol
S1-MME S1 for the control plane
S1-U S1 for the user plane
SB Scheduling Block
SR Scheduling Request
SU Scheduling Unit
S-SCH Secondary Synchronization Channel
SFTP Secure File Transfer Protocol
S-FTP Secure File transfer protocol
SRTP Secure Real-Time Protocol
SSH Secure Shell
SSL Secure Sockets Layer
SeGW Security Gateway
S-PARC Selective PARC
SON Self Organizing Networks
SSP Self-Service Portal
SN Sequence Number
SAR/SAA Server Assignment Request/Answer (Diameter Message)
SAP Service Access Point
SAPC Service Aware Policy Controller
SCC-AS Service Centralization and Continuity Application Server
SDF Service Data Flow
SDU Service Data Unit
SLA Service Level Agreement
SLO Service Level Objectives
SNF Service Network Framework
S-CSCF Serving CSCF
S-GW Serving Gateway
SGSN Serving GPRS Support Node
SBC Session Border Controller
SBG Session Border Gateway
SDP Session Description Protocol
SDES Session Description Protocol Security Descriptions
SGC Session Gateway Controller
SIP Session Initiation Protocol
SM Session Management
SPDF Session Policy Decision Function
SCCH Shared Control Channel
SMS Short Message Service
SMS Short Message Service
SINR Signal to Interference and Noise Ratio
SNR Signal to Noise Ratio
SCCP Signaling Connection Control Part
SRB Signaling Radio Bearer
SS7 Signaling System No 7
SID Silence Insertion Descriptor
SCEP Simple Certificate Enrolment Protocol
SOAP Simple Object Access Protocol
SOX Simple Outline XML
SC-FDMA Single Carrier – Frequency Division Multiple Access
SISO Single Input Single Output

Table of Figures
SRVCC Single Radio Voice Call Continuity

SSO Single Sign On
SU-MIMO Single-User MIMO
SIS Site Infrastructure Support
SFP Small Form factor Pluggable
SW Soft Ware
SW Software
SMRS Software Management Repository
SMO Software Manager Organizer
SDMA Spatial Division Multiple Access
SEM Spectrum Emission Mask
SCTP Stream Control Transmission Protocol
SQL Structured Query Language
SIM Subscriber Identity Module
SLF Subscriber Location Function
SPID Subscriber Profile ID for RAT/Frequency Priority
SCH Synchronization Channel
SDH Synchronous Digital Hierarchy
SAE System Architecture Evolution
SFN System Frame Number
SI-RNTI System Info RNTI
SI System Information
SIB System Information Block
Telecommunication Standardization Sector of the International
ITU-T
Telecommunications Union
Telecoms & Internet converged Services & Protocols for Advanced
TISPAN Networks
(http://portal.etsi.org/portal_common/home.asp?tbkey1=TISPAN)
TAS Telephony Application Server
TLP TEMS LinkPlanner
T-ADS Terminating-Access Domain Selection
The European Conference of Postal and Telecommunications
CEPT
Administrations
TLA Three Letter Acronym
TDD Time Division Duplex
TTM Time To Market
TDM Time-Division Multiplexing
TMO T-Mobile International AG
TBD To Be Decided
TMA Tower Mounted Amplifier
TA Tracking Area
TAU Tracking Area Update
TFT Traffic Flow Template
TFP Traffic Forwarding Policy
TCP Transmission Control Protocol
TTI Transmission Time Interval
TPC Transmit Power Control
TX Transmitter
TM Transparent Mode
TB Transport Block
TF Transport Format
TFCI Transport Format Combination Indicator
TLS Transport Layer Security

TNL Transport Network Layer

UETR UE TRace
UTRA UMTS Terrestrial Radio Access
UTRAN UMTS Terrestrial Radio Access Network
UM Unacknowledged Mode
URI Uniform Resource Identifier. (Defined in RFC 2396)
Uniform Resource Locator. The address of a file (resource) accessible
URL
on the Internet. (Defined in RFC 2396)
UMTS Universal Mobile Telecommunication System
USIM Universal SIM (3G SIM)
UL Uplink
UCI Uplink Control Information
UpPTS Uplink Pilot Time Slot
UL-SCH Uplink Shared Channel
UAC User Agent Client
UA User Agent. An endpoint in a SIP based network.
UE User Equipment
UP User Plane
U-plane User plane
UPE User Plane Entity
UNI User-to-Network Interface
URA UTRAN Routing Area
WDM Wavelength Division Multiplexing
WCG Web Communication Gateway
WUIGM Web User Interface for Group and Data Management
WCDMA Wideband Code Division Multiple Access
WAPECS Wireless Access Policy for Electronic Communications Services
WAP Wireless Access Protocol
VRB Virtual Resource Block
VPLMN Visited PLMN
VAD Voice Activity Detector
VoHSPA Voice over HSPA
VoIP Voice over IP
VoLTE Voice over LTE
WiMAX Worldwide Interoperability for Microwave Access
X2-C X2-Control plane
X2-U X2-User plane
XCAP XML Configuration Access Protocol
XDMS XML Document Management Server

Table of Figures
8 Index
1 ANR, 194
16 QAM, 17, 25, 26, 34 AP, 117, 120, 193
1XRTT, 199 APAC, 193
3 API, 193
3G, 10, 11 APN, 193
3GPP, 10, 11, 16, 17, 34, 37, 135, 136, 149, A-RACF, 193
150, 151, 152, 153, 155, 156, 157, 165, ARP, 193
190, 193, 197
ARPU, 194
3PP, 193
ARQ, 17, 22, 61, 113, 194, 197, 200
6
ARW, 193
64 QAM, 17, 25, 26, 29, 34, 35
AS, 193, 194, 202
A
AAA, 193, 195 A-SBG, 193
ACIR, 6, 7, 158, 159, 160, 161, 193 ASC, 76, 92, 166, 174, 193
ACK, 22, 30, 52, 53, 54, 101, 113, 120, 121, ASD, 194
193 ASSL, 193
ACLR, 148, 149, 150, 154, 158, 193 ASSR, 193
ACM, 193 AuC, 193
ACP, 187, 194 AV, 193
ACS, 6, 154, 155, 156, 158, 193 B
AES, 193 B2B UA, 194
AGW, 193 BB, 194
AIF, 193 BCCH, 194
AIR, 5, 111, 193 BCE, 194
AISG, 193 BCH, 19, 23, 24, 25, 29, 194
AKA, 193 BE-DB, 194
AM, 193 BEM, 194
AMBR, 193 BFCP, 194
A-MPR, 193 BGCF, 194
AMR, 61, 193 BGF, 194, 195, 197
ANM, 193 BM-SC, 194
BS, 158, 194

BSR, 194 CW, 194

BW, 21, 117, 118, 119, 120, 123, 155, 164, CX-AS, 194
194 Cyclic Prefix’, 18
C D
C/I, 194 DBL, 195
CA, 194 DBS/SABE, 195
CAI, 195 DCCH, 195
CAPEX, 194 DCH, 195
CAS, 195 DCI, 195
CAZAC, 194 DCN, 195
C-BGF, 195 DECT, 195
CCCH, 194 DFT, 195
CCE, 115, 116, 194 DFT-S-OFDM, 195
CCMP, 195 DHCP, 195
CDD, 195 Diameter, 195, 199, 202
CDF, 195 Digital Units, 188
CDIV, 194 DL, 5, 6, 10, 14, 16, 20, 21, 22, 25, 26, 68,
CDMA, 7, 146, 147, 173, 194 80, 90, 91, 93, 94, 95, 96, 97, 98, 99, 100,
CE, 194 101, 102, 105, 107, 108, 109, 110, 111,
CEPT, 203 112, 113, 119, 120, 128, 147, 179, 180,
CFR, 194 181, 195
CFRA, 194 DL-SCH, 22, 195
Channel models, 41 DNS, 58, 59, 193, 195, 196, 197
Chase Combining, 30, 31 DRB, 195
CIC, 194 DRX, 195
CM, 194 DSCP, 195
CMC, 194 DSL, 195
CMDB, 194 DTCH, 195
CN, 11, 195 DTX, 195
CO, 194, 195 DUL, 189, 190, 191
CoH, 194 DwPTS, 195
COMINF, 194 E
CO-OP, 195 E.164, 193, 197
CORBA, 194 EBS, 195
CoSe, 197 ECC, 195
CP, 18, 194 ECGI, 196
CPC, 194 ECM, 195
C-plane, 194 E-CSCF, 195
CPM, 195 E-DCH, 195
CQI, 17, 121, 122, 123, 194 EDGE, 10
CRC, 30, 31, 195 eDNS, 196
C-RNTI, 194 e-GEM, 195
CS, 10, 12, 143, 194, 196 e-GEM 2, 195
CSCF, 194, 195, 197, 201, 202 EHPLMN, 195
CSFB, 194 EMA, 195
CSV, 194 EMEA, 196
CTR, 194 EMM, 195
CUDB, 194 eNB, 125, 170, 196
eNode B, 196

Table of Figures
ENUM, 193 GTP-C, 196

EPA5, 41 GTP-U, 196
EPC, 11, 195 GUI, 196
EPS, 11, 195, 196 GUTI, 196
E-RAB, 196 GW, 11, 12, 196, 200, 202
ESM, 195 H
ETSI, 10, 196 HA-CS, 196
ETWS, 195 HARQ, 4, 17, 21, 31, 48, 62, 120, 121, 197
EUL, 10 HD, 197
E-UTRA, 7, 37, 66, 143, 146, 150, 172, 173, HDVC, 197
196 HLR, 197
eUTRAN, 10, 11 HO, 196
E-UTRAN, 143, 196 HOM, 10, 197
EV-DO, 196 HP, 196
EVM, 195 HPLMN, 197
EXB, 196 HRPD, 147, 197
F HSDPA, 10, 197
FCC, 196 HS-DSCH, 197
FDD, 10, 17, 19, 37, 81, 106, 146, 152, 196 HSPA, 10, 197, 204
FDM, 196 HSS, 197
FDMA, 16, 106, 196, 202 HSS-FE, 197
FEC, 196 HSUPA, 10, 197
FFS, 196 HTTP, 4, 45, 46, 47, 49, 58, 59, 197
FFT, 196, 197 HTTPS, 197
FM, 196 HW, 196
FMC, 196 I
FMX, 196 IASA, 197
FQDN, 196 IBCF, 197
FS, 196 I-BGF, 197
FTP, 4, 48, 49, 54, 55, 60, 196, 202 ICB, 197
FW, 196 ICIC, 67, 197
G ICS, 197
GBR, 196 I-CSCF, 197
GCL, 196 ID, 23, 136, 197, 198, 200, 203
GE, 196 iDNS, 197
GERAN, 196 IEEE, 197
GGSN, 11, 196 IETF, 193, 197, 198
GIBA, 196 IFFT, 197
GINR, 196 IM, 197
GMPLS, 196 IMEI, 197
GNSS, 196 IMPI, 198
GP, 196 IMS, 196, 197, 198
GPRS, 10, 196, 202 IMSI, 197
GSM, 7, 10, 143, 165, 166, 170, 171, 172, IMS-M, 197
187, 189, 196 IMT, 11, 197
GSMA, 196, 200 Incremental Redundancy, 30, 31
GSTN, 196 Inter Symbol Interference, 16
GTP, 196

IP, 44, 45, 46, 47, 48, 49, 50, 56, 57, 59, 191, MBMS, 198, 199
195, 197, 198, 201, 204 MBR, 198
IPSec, 198 MBSFN, 199
IPTV, 197 MCCH, 199
Ipv4, 197 MCE, 199
Ipv6, 197 MCH, 198, 199
IPW, 198 MCID, 198
IRAT, 197 MCR, 198
IS, 197 MCS, 67, 94, 198
ISC, 197 MEF, 198
ISDN, 197, 198 MeGaCo, 198
ISER, 197 MGC, 198
ISI, 16, 197 MGCF, 198
ISIM, 197 MGW, 198
ISM, 197 MIB, 23, 198
ISUP, 193, 198 MIMO, 10, 11, 13, 20, 28, 29, 36, 66, 179,
ITU, 11, 197, 198, 203 180, 187, 199, 203
ITU-R, 198 MiO, 198
ITU-T, 197, 203 ML-PPP, 199
IWF, 197 MM, 127, 142, 198
IWS, 194 MME, 6, 127, 137, 138, 139, 140, 142, 143,
J 198, 202
JCP, 198 M-MGw, 198
JSR, 198 MMS, 199
K MMTel, 199
KPI, 198 MNP, 198
L MOCI, 198, 199
LAN, 188, 198 modulation symbols, 18
LB, 198 MOP, 198
LCID, 198 MOS, 198
LCR, 198 MP, 198
LCR-TDD, 198 MPLS, 199
LDAP, 198 MPR, 193, 198
LDC, 198 MRFC, 198
LDPC, 198 MRFP, 198
LED, 198 MRS, 198
LTE, 3, 4, 6, 7, 8, 9, 10, 11, 12, 13, 15, 16, MS, 198
17, 18, 19, 33, 34, 36, 37, 38, 43, 44, 48, MSAP, 198
49, 59, 61, 62, 63, 64, 65, 66, 70, 82, 89, MSC, 143, 198
135, 146, 148, 151, 154, 165, 166, 170, MSISDN, 198
171, 173, 174, 175, 176, 177, 178, 179, MSP, 199
180, 182, 183, 184, 185, 186, 187, 189, MSS, 52, 198
190,191, 196, 198, 204 MTAS, 199
M
MTCH, 199
M3UA, 198
MU-MIMO, 199
MAC, 29, 35, 198
mUPE, 198
MAP, 198
MXB, 198
MAR/MAA, 199
MBA, 198

Table of Figures
N PANI, 200
NAB, 199 PAPR, 16, 200
NACK, 30, 31, 101, 113, 120, 121, 199 PAR, 200
NAI, 199 PARC, 200, 202
NAS, 199 PBBTE, 201
NASS, 199 PBC, 200
NAT, 199 PBCH, 23, 24, 112, 113, 116, 117, 118, 119,
NB, 199 200
NBA, 199 PBN, 200
NCC, 199 PBR, 201
NCL, 199 PC, 46, 138, 200
NCLI, 199 PCC, 200
NCS, 199 PCCH, 200
NE, 199 PCEF, 200
NEM, 199 PCFICH, 21, 22, 99, 112, 113, 114, 115, 116,
NENA, 199 118, 135, 200
NGMN, 199 PCH, 200
NGSA, 199 PCI, 6, 135, 136, 137, 200
NH, 199 PCM, 201
NM, 199 PCO, 201
NMS, 199 PCRF, 200
NMX, 199 P-CSCF, 201
NNI, 199 PDB, 200
NOC, 199 PDCCH, 21, 22, 34, 99, 100, 112, 114, 115,
NR, 199 116, 118, 127, 128, 130, 131, 132, 133,
NRT, 199 134, 135, 200
N-SBG, 199 PDCP, 35, 200
NSP, 199 PDN, 200
NW, 199 PDN-GW, 200
O PDP, 200
O&M, 190, 191, 194, 199 PDSCH, 21, 25, 26, 94, 99, 100, 112, 117,
OAM, 199 118, 119, 127, 128, 129, 130, 134, 200
OCB, 200 PDSN, 200
OFDM, 16, 18, 21, 22, 66, 113, 114, 123, PDU, 201
195, 200 Peak to Average Power Ratio, 16
OFDMA, 23, 106, 200 PGM, 200
Okumura-Hata model, 38, 39 P-GW, 11, 12, 200
OMA, 199 PHICH, 21, 22, 112, 113, 114, 115, 116, 118,
OMC, 199 120, 135, 200
OOB, 200 PHR, 200
OPEX, 199 PHS, 200
OSS, 137, 190, 195, 199 PHY, 200
OSS-RC, 137, 190, 199 PLMN, 23, 136, 195, 196, 197, 201, 204
OTN, 199 PM, 200
P PMCH, 200
P(N)CCH, 200 PMI, 200
P2P, 195, 200 PMIP, 201
PA, 200 PnP, 200

PoP, 200 RCS-e, 202

PRACH, 123, 125, 200 Reference Signals, 20
PRB, 200 Remote Radio Unit, 187
PRD, 200 resource elements, 18, 19, 20, 21, 23, 24, 25,
P-RNTI, 200 26, 34
PS, 10, 12, 200 RET, 201
PSC, 200 RF, 6, 39, 76, 82, 92, 148, 158, 201
P-SCH, 200 RFC, 193, 195, 197, 198, 201, 204
PSD, 119, 200 RI, 121, 201
PSK, 200 RLC, 17, 35, 201
PSTN, 196, 201 RM, 201
PTT, 201 RNC, 11, 201
PUCCH, 33, 34, 101, 112, 115, 120, 121, 123, RNL, 201
124, 126, 183, 200 RNTI, 194, 200, 201, 203
PUI, 201 RoHC, 202
PUSCH, 4, 5, 72, 89, 90, 112, 120, 121, 200 ROP, 201
Q RPLMN, 201
QAM, 17, 25, 26, 29, 34, 35, 66, 201 RRC, 125, 201
QCI, 201 RRM, 201
QoS, 201 RRU, 76, 92, 111, 187, 201
QPP, 201 RS, 112, 113, 115, 116, 117, 118, 119, 120,
QPSK, 17, 25, 26, 34, 201 201
R RSN, 201
RA, 142, 201 RT, 201
RAC, 201 RTCP, 202
RACH, 201 RTP, 201, 202
Radio Units, 188 RTSP, 201
RADIUS, 201 RU, 74, 188, 189, 201
RAN, 10, 11, 201 RUL, 189, 190
RANAP, 201 RX, 5, 86, 87, 122, 188, 201
RA-RNTI, 201 S
RAT, 201, 203 S1-MME, 202
RB, 7, 18, 20, 22, 25, 26, 29, 34, 35, 78, 79, S1-U, 202
83, 85, 87, 91, 115, 117, 118, 119, 121, SAE, 10, 11, 203
122, 123, 125, 178, 179, 180, 182, 183, SAP, 202
201 SAPC, 202
RBC, 201 SAR/SAA, 202
RBG, 201 SB, 17, 20, 21, 24, 25, 26, 202
RBS, 6, 7, 8, 13, 27, 28, 38, 39, 40, 74, 79, SBC, 202
84, 111, 120, 127, 128, 130, 137, 138, 139, SBG, 193, 199, 202
147, 148, 149, 151, 152, 153, 155, 157, SCC-AS, 202
160, 161, 162, 163, 164, 165, 166, 178, SCCH, 202
179, 180, 181, 182, 183, 184, 187, 188, SCCP, 202
189, 190, 191, 193, 201 SCEP, 202
RBS 6000, 187, 188, 189, 191 SC-FDMA, 16, 106, 202
RBS 6101, 187 SCH, 22, 24, 29, 34, 195, 200, 202, 203, 204
RBS 6201, 187
S-CSCF, 202
RBS 6601, 187
SCTP, 127, 138, 139, 203
RCS, 201, 202
SDES, 202

Table of Figures
SDF, 202 SSH, 202

SDH, 203 SSL, 197, 202
SDMA, 203 SSLIOP, 197
SDP, 202 SSO, 203
SDU, 202 SSP, 202
SeGW, 202 SU, 202, 203
SEM, 203 SU-MIMO, 203
SFN, 23, 203 SW, 194, 203
SFP, 203 T
SFTP, 202 TA, 10, 127, 137, 138, 139, 140, 141, 142,
S-FTP, 202 143, 203
SGC, 202 T-ADS, 203
SGSN, 11, 127, 140, 142, 143, 202 TAS, 203
S-GW, 11, 12, 202 TAU, 203
SI, 203 TB, 203
SIB, 203 TBD, 203
SID, 202 TCP, 4, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54,
SIM, 197, 203, 204 55, 56, 58, 59, 60, 178, 179, 180, 182, 183,
SINR, 7, 29, 35, 67, 68, 78, 79, 80, 82, 83, 185, 203
84, 85, 87, 88, 94, 95, 96, 98, 99, 100, 101, TDD, 5, 10, 17, 19, 81, 106, 107, 108, 109,
102, 105, 178, 179, 181, 182, 202 110, 146, 153, 198, 203
SIP, 200, 202, 204 TDM, 203
SI-RNTI, 203 TEMS CellPlanner, 178, 184
SIS, 203 TF, 203
SISO, 20, 202 TFCI, 203
SLA, 202 TFP, 203
SLF, 203 TFT, 203
SLO, 202 TISPAN, 203
SM, 202 TLA, 203
SMO, 203 TLP, 203
SMRS, 203 TLS, 203
SMS, 202 TM, 203
SN, 201, 202 TMA, 74, 76, 174, 203
SNF, 202 TMO, 203
SNR, 74, 202 TNL, 204
SOAP, 202 TPC, 203
SON, 202 TSP, 195
SOX, 202 TTI, 17, 18, 203
S-PARC, 202 TTM, 203
SPDF, 202 Turbo Coder, 30, 31
SPID, 203 TX, 13, 28, 188, 203
SQL, 203 U
SR, 121, 122, 123, 202 UA, 194, 204
SRB, 202 UAC, 204
SRTP, 202 UCI, 204
SRVCC, 203 UE, 3, 6, 7, 16, 17, 20, 21, 22, 26, 27, 28, 29,
33, 34, 35, 36, 38, 39, 40, 58, 66, 76, 78,
SS7, 202
79, 82, 84, 90, 92, 94, 96, 97, 113, 121,
S-SCH, 202
125, 126, 127, 143, 147, 148, 150, 153,

154, 155, 156, 157, 158, 160, 161, 162, V

163, 164, 165, 166, 178, 179, 180, 181, VAD, 204
182, 183, 204 VoHSPA, 204
UETR, 204 VoIP, 44, 48, 204
UL, 5, 6, 8, 10, 16, 22, 34, 35, 66, 67, 68, 69, VoLTE, 204
73, 74, 75, 77, 78, 79, 80, 81, 83, 84, 86, VPLMN, 204
87, 88, 89, 90, 97, 101, 106, 107, 108, 110, VRB, 204
111, 112, 120, 124, 125, 128, 147, 148, W
182, 183, 184, 204 Walfisch-Ikegami model, 39, 40
UL-SCH, 22, 34, 204 WAP, 204
UM, 204 WAPECS, 204
UMTS, 204 WCDMA, 10, 34, 62, 65, 70, 135, 143, 147,
UNI, 204 148, 187, 189, 204
UP, 204 WCG, 204
UPE, 198, 204 WDM, 204
U-plane, 204 WiMAX, 204
UpPTS, 204 WUIGM, 204
URA, 204 X
URI, 204 X2-C, 204
URL, 58, 59, 204 X2-U, 204
USIM, 204 XCAP, 204
UTRA, 7, 10, 37, 66, 146, 150, 172, 173, 196, XDMS, 204
204 XML, 196, 202, 204
UTRAN, 10, 11, 143, 196, 204

Table of Figures
9 Table of Figures
Figure 1-1 Objectives of Chapter 1 ................................................................................................. 9

Figure 1-2 3G Evolution ................................................................................................................ 11
Figure 1-3 Simplified Network Architecture ................................................................................... 12
Figure 1-4 LTE Dimensioning Process. ......................................................................................... 13
Figure 2-1 Objectives of Chapter 2 ............................................................................................... 15
Figure 2-2 LTE Air Interface Introduction ...................................................................................... 16
Figure 2-3 LTE Downlink Physical Resources ............................................................................... 18
Figure 2-4 Number of Resource Blocks (nRB) ................................................................................ 19
Figure 2-5 Downlink Reference Signals ........................................................................................ 20
Figure 2-6 Downlink L1/L2 Control Signalling................................................................................ 21
Figure 2-7: Synchronization Signals .............................................................................................. 23
Figure 2-8: Broadcast Channel ..................................................................................................... 24
Figure 2-9 DL RB (High PDSCH Data Rate) ................................................................................. 25
Figure 2-10: DL RB (Low PDSCH Data Rate) ............................................................................... 26
Figure 2-11 Adaptive Coding ........................................................................................................ 27
Figure 2-12 Tx Diversity vs 2x2 MIMO. ......................................................................................... 28
Figure 2-13 Downlink Channel mapping Examples ....................................................................... 29
Figure 2-14 Coding and Puncturing .............................................................................................. 31
Figure 2-15 Downlink Data Flow ................................................................................................... 32
Figure 2-16 LTE Uplink Resource Blocks ...................................................................................... 33
Figure 2-17 LTE Uplink Physical Resources ................................................................................. 34
Figure 2-18 Uplink Channel mapping Examples ........................................................................... 35
Figure 2-19 LTE UE Categories .................................................................................................... 36
Figure 2-20 LTE FDD Frequency Bands ....................................................................................... 37
Figure 2-21 Okumura-Hata model (Ericsson variant). ................................................................... 38
Figure 2-22 Walfish-Ikegami model (Cost-231). ............................................................................ 40
Figure 2-23 Channel Models. ........................................................................................................ 41
Figure 3-2 Web Browsing Traffic ................................................................................................... 45
Figure 3-3 Email Traffic ................................................................................................................. 46
Figure 3-4 Video Streaming Traffic ............................................................................................... 47
Figure 3-5 File Download Traffic ................................................................................................... 48
Figure 3-6 Voice Traffic ................................................................................................................. 49

Figure 3-7 Transmission Control Protocol ..................................................................................... 51

Figure 3-8 TCP Operation ............................................................................................................. 53
Figure 3-9 TCP Flow Control......................................................................................................... 54
Figure 3-10 TCP Throughput ........................................................................................................ 55
Figure 3-11 TCP Throughput Example.......................................................................................... 56
Figure 3-12 User Datagram Protocol............................................................................................. 57
Figure 3-13 Hypertext Transfer Protocol ....................................................................................... 58
Figure 3-14 HTTP Operation Example .......................................................................................... 59
Figure 3-15 File Transfer Protocol ................................................................................................. 60
Figure 3-16 Voice over LTE Total Delay ....................................................................................... 61
Figure 3-17 HARQ Effect on Voice Service ................................................................................... 62
Figure 4-2 LTE Dimensioning Process .......................................................................................... 64
Figure 4-3. Dimensioning method. ................................................................................................ 65
Figure 4-4: Network Dimensioning Example ................................................................................. 66
Figure 4-5 Uplink Cell Throughput ................................................................................................ 67
Figure 4-6 Uplink Cell throughput Example ................................................................................... 68
Figure 4-7: Input requirements ...................................................................................................... 69
Figure 4-8 UL dimensioning process. ............................................................................................ 69
Figure 4-9. Site-to-site distance, d. ............................................................................................... 70
Figure 4-10: Signal attenuation ..................................................................................................... 71
Figure 4-11: Power control target .................................................................................................. 72
Figure 4-12. PUSCH load level, QPUSCH. ................................................................................... 72
Figure 4-13: Iteration parameters .................................................................................................. 73
Figure 4-14: Uplink coverage calculation ...................................................................................... 74
Figure 4-15. UL thermal noise. ...................................................................................................... 75
Figure 4-16: Uplink System Reference Point................................................................................. 76
Figure 4-17: Interference Rejection Combining (IRC) .................................................................... 77
Figure 4-18: UL noise rise ............................................................................................................. 77
Figure 4-19: UL resource block allocation ..................................................................................... 78
Figure 4-20: UL power level .......................................................................................................... 79
Figure 4-21. UL power levels. ....................................................................................................... 80
Figure 4-22: UL bit rates ............................................................................................................... 81
Figure 4-23: Link Curve Coefficients for UL FDD & TDD, 1x2 ....................................................... 81
Figure 4-24. SINR to bit rate estimation. ....................................................................................... 82
Figure 4-25 UL cell edge bit rates. ................................................................................................ 83
Figure 4-26: UL cell edge bit rates ................................................................................................ 84
Figure 4-27. UL high bite rates. ..................................................................................................... 84
Figure 4-28 UL link budget. ........................................................................................................... 84
Figure 4-29 eNodeB Receiver Sensitivity ...................................................................................... 85
Figure 4-30 Alternative link budget. ............................................................................................... 86
Figure 4-31: Uplink capacity calculation ........................................................................................ 86
Figure 4-32. UL average RX power. .............................................................................................. 87
Figure 4-33 UL average SINR. ...................................................................................................... 87
Figure 4-34: Uplink CoverageSummary ........................................................................................ 88
Figure 4-35: UL cell throughputFinally, Lpmax is converted to a corresponding cell range, R, by using
an Ericsson specific variant of the Okumura-Hata model. ............................................................. 88
Figure 4-36: Uplink Cell Range ..................................................................................................... 89
Figure 4-37 Power control and PUSCH load ................................................................................. 89
Figure 4-38: Downlink dimensioning ............................................................................................. 90
Figure 4-39 Path loss from uplink. ................................................................................................. 90
Figure 4-40: DL Bit rate ................................................................................................................. 91

Table of Figures
Figure 4-41 DL power per resource block. .................................................................................... 91

Figure 4-42: Downlink System Reference Point ............................................................................ 92
Figure 4-43: DL noise rise at the cell edge .................................................................................... 93
Figure 4-44 Table for Fc................................................................................................................ 93
Figure 4-45 Downlink cell edge bit rate. ........................................................................................ 94
Figure 4-46: DL bit rate at cell edge .............................................................................................. 95
Figure 4-47 Downlink CoverageSummary ..................................................................................... 95
Figure 4-48 Concluding the DL link budget ................................................................................... 96
Figure 4-49 Backtracking DL link budget ....................................................................................... 96
Figure 4-50 UE receiver sensitivity. ............................................................................................... 96
Figure 4-51 DL link budget. ........................................................................................................... 97
Figure 4-52 DL signal attenuation. ................................................................................................ 97
Figure 4-53 DL capacity. ............................................................................................................... 98
Figure 4-54 DL average noise rise. ............................................................................................... 98
Figure 4-55: DL average SINR ...................................................................................................... 99
Figure 4-56: DL cell throughput ..................................................................................................... 99
Figure 4-57: DL control channel coverage Non time synchronized Network ................................ 100
Figure 4-58: DL control channel coverage Time synchronized network ...................................... 100
Figure 4-59 UL control channel coverage.................................................................................... 101
Figure 4-60 UL control channel coverage.................................................................................... 101
Figure 4-61 DL ring method. ....................................................................................................... 102
Figure 4-62 Cell rings. ................................................................................................................. 102
Figure 4-63: Equivalent tilt angle ................................................................................................. 103
Figure 4-64 SINR in each ring. .................................................................................................... 105
Figure 4-65: DL bit rates, ring method ......................................................................................... 105
Figure 4-66 UL ring method. ....................................................................................................... 106
Figure 4-67 TDD Coverage ......................................................................................................... 107
Figure 4-68 TDD Capacity .......................................................................................................... 107
Figure 4-69 TDD UL/DL configurations ....................................................................................... 108
Figure 4-70: TDD bitrate calculations .......................................................................................... 108
Figure 4-71: Variables ................................................................................................................. 109
Figure 4-72: Link curve coefficients for DL TDD 2x2 OLSM ........................................................ 109
Figure 4-73: Link Curve Coefficients for UL TDD, 1x2 ................................................................. 110
Figure 4-74: Features impacting capacity and coverage ............................................................. 111
Figure 4-75. DL resource grid, 5 MHz. ........................................................................................ 112
Figure 4-76: Number of Resource Elements used by PHICH in one frame ................................. 114
Figure 4-77: Setting of pdcchCfiMode ......................................................................................... 114
Figure 4-78: Max number of Resource Elements for PDCCH per radio frame............................. 115
Figure 4-79: Number of Resource Elements not used in control region per frame....................... 116
Figure 4-80: Resource consumption for control channels and PDSCH, BW=10MHz, CFI=2, 1 AP
................................................................................................................................................... 117
Figure 4-81: Resource consumption for control channels and PDSCH, BW=10MHz, CFI=2, 2 APs
................................................................................................................................................... 118
Figure 4-82. Resource consumption for control channels and PDSCH, BW=20MHz, CFI = 1, 2
APs.. ........................................................................................................................................... 119
Figure 4-83. Power consumption per antenna port, BW=10MHz, CFI = 2, 1 AP, 40W. ............... 120
Figure 4-84 Power consumption per antenna port, BW=20MHz,CFI = 1, 2 APs, 40W. ............... 120
Figure 4-85: Highest value of SR and CQI resources .................................................................. 122
Figure 4-86: SR and CQI resources per DU ................................................................................ 122
Figure 4-87: Calculation of PUCCH RB usage ............................................................................ 123

Figure 4-88: Calculation of SR and CQI resources - from a wanted number of RB-pairs for
Format1 and Format2 ................................................................................................................. 123
Figure 4-89: UL resource grid ..................................................................................................... 124
Figure 4-90. Uplink resource usage – cell range max 15 km ....................................................... 124
Figure 4-91 Uplink resource usage - Cell Range above 15km..................................................... 125
Figure 4-92: Sounding Reference Signal .................................................................................... 126
Figure 4-93: Paging capacity....................................................................................................... 128
Figure 4-94: Calculation of PDSCH paging capacity ................................................................... 129
Figure 4-95: Paging capacity in relation to PDSCH load ............................................................. 129
Figure 4-96. Paging capacity vs blocking probability. .................................................................. 130
Figure 4-97: Number of CCEs per frame - nCCE,frame .............................................................. 131
Figure 4-98. Paging capacity vs PDCCH load – 1.4 MHz. ........................................................... 132
Figure 4-99. Paging capacity vs PDCCH load – 3 MHz. .............................................................. 132
Figure 4-100. Paging capacity vs PDCCH load – 5 MHz and 15 MHz. ........................................ 133
Figure 4-101. Paging capacity vs PDCCH load - 10 MHz. ........................................................... 133
Figure 4-102.Paging capacity vs PDCCH load - 20 MHz............................................................. 134
Figure 4-103: PCI Planning. ........................................................................................................ 137
Figure 4-104 TA Dimensioning.................................................................................................... 138
Figure 4-105 TA Planning - Planning borders between TAs and TA lists .................................... 140
Figure 4-106 TA lists - Sliding Window........................................................................................ 141
Figure 4-107 TA Planning strategy - Without considering future migration to TA lists with multiple
TAs. ............................................................................................................................................ 142
Figure 4-108 TA Planning strategy - Considering future migration to TA lists with multiple TAs. . 143
Figure 5-1 Objectives of chapter 5 .............................................................................................. 145
Figure 5-2: Operating Bands - LTE FDD ..................................................................................... 146
Figure 5-3: Operating Bands - LTE TDD ..................................................................................... 146
Figure 5-4: Operating Bands CDMA & eHRPD ........................................................................... 147
Figure 5-5 WCDMA and other communication systems .............................................................. 147
Figure 5-6 Adjacent Channel Leakage Ratio ............................................................................... 149
Figure 5-7 RBS ACLR specification ............................................................................................ 149
Figure 5-8 UE E-UTRA ACLR specifications - min requirements 3GPP TS 36.101 v8.9.0 .......... 150
Figure 5-9 UE UTRA ACLR specifications - min requirements 3GPP TS 36.101 v8.9.0. ............. 150
Figure 5-10 Spurious Emissions. ................................................................................................ 151
Figure 5-11. RBS spurious emissions into LTE. .......................................................................... 151
Figure 5-12 RBS Spurious emission into other bands – colocated RBS FDD: (3GPP TS 36.104
v8.9.0)......................................................................................................................................... 152
Figure 5-13 RBS spurious emission - co-existing RBSs FDD: (3GPP TS 36.104 v8.9.0) ............ 152
Figure 5-14. RBS spurious emission - co-existing RBSs TDD: (3GPP TS 36.104 v8.9.0). .......... 153
Figure 5-15 UE spurious emissions – 3GPP TS 36.101 v8.9.0 ................................................... 153
Figure 5-16 Adjacent Channel Selectivity (ACS) ......................................................................... 154
Figure 5-17 RBS reference sensitivity levels - 3GPP TS 36.104 v8.9.0....................................... 155
Figure 5-18. RBS ACS (3GPP TS 36.104 v8.9.0). ...................................................................... 155
Figure 5-19 UE ACS (3GPP TS 36.101 8.9.0). ........................................................................... 156
Figure 5-20 Receiver Blocking .................................................................................................... 156
Figure 5-21 RBS Receiver blocking- colocation, (3GPP TS 36.104 v8.9.0) ................................. 157
Figure 5-22 UE Receiver blocking. .............................................................................................. 157
Figure 5-23 Adjacent Channel Interference Ratio (ACIR) ............................................................ 158
Figure 5-24 Adjacent Channel Interference Ratio (ACIR). ........................................................... 159
Figure 5-25 Adjacent Channel Interference Ratio (ACIR). ........................................................... 159
Figure 5-26 Downlink ACIR (ACIRDL, RBS to UE interference). ................................................. 160
Figure 5-27 Uplink ACIR (ACIRUL, UE to RBS interference). ..................................................... 161
Figure 5-28 Interference effect on RBS ....................................................................................... 162

Table of Figures
Figure 5-29 Interference effect on UE ......................................................................................... 163

Figure 5-30 Sensitivity degradation due to interference............................................................... 164
Figure 5-31 Thermal Noise (N).................................................................................................... 165
Figure 5-32. LTE sensitivity degradation - GSM 1800 example. .................................................. 166
Figure 5-33 Isolation between systems ....................................................................................... 166
Figure 5-34 Isolation (equation 31). ............................................................................................ 168
Figure 5-35 Co-area operation. ................................................................................................... 168
Figure 5-36. Isolation required. ................................................................................................... 169
Figure 5-37. Isolation against blocking towards LTE. .................................................................. 170
Figure 5-38. Isolation against spurious emissions - colocation with GSM 1800. .......................... 170
Figure 5-39. Isolation against spurious emissions - coexistence with GSM 1800. ....................... 171
Figure 5-40. LTE spurious emission level. .................................................................................. 171
Figure 5-41. Colocation and coexistence for E-UTRA with E-UTRA. ........................................... 172
Figure 5-42. Colocation and coexistence for E-UTRA band 7 with GSM 1800. ........................... 172
Figure 5-43. Colocation and coexistence for E-UTRA band 7 with UTRA band I. ........................ 172
Figure 5-44. Horizontal and vertical separation for colocated antennas. ..................................... 173
Figure 5-45. Feeder sharing and separate antennas. .................................................................. 174
Figure 5-46. Shared antenna only. .............................................................................................. 175
Figure 5-47. Co-existence interference scenarios. ...................................................................... 176
Figure 6-1 Objectives of Chapter 6 ............................................................................................. 177
Figure 6-2 TEMS CellPlanner LTE Pathloss Plot ........................................................................ 178
Figure 6-3 DL SINR (60% Load) ................................................................................................. 179
Figure 6-4 DL RB Data Rate (60% Load) .................................................................................... 180
Figure 6-5 DL Data Rate (60% Load) .......................................................................................... 181
Figure 6-6 UL Max SINR (Monte-Carlo Load) ............................................................................. 182
Figure 6-7 UL RB Data Rate (Monte-Carlo Load)........................................................................ 183
Figure 6-8 UL Data Rate (Monte-Carlo Load) ............................................................................. 184
Figure 6-9 LTE Neighbor Analysis .............................................................................................. 185
Figure 6-10 LTE Neighbor Analysis Results ................................................................................ 186
Figure 6-11 LTE Neighbor Analysis Plot ..................................................................................... 186
Figure 6-12 RBS 6000 Family ..................................................................................................... 187
Figure 6-13 RBS 6000 Hardware Architecture ............................................................................ 188
Figure 6-14 RBS 6000 RU and DU Variants ............................................................................... 189
Figure 6-15 Radio Unit LTE Configurations ................................................................................. 190
Figure 6-16 Digital Unit LTE Variants .......................................................................................... 191

LTE L13 Radio Network Design: Student Book LZT1380915 R2A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE L13 Radio Network Design: Student Book LZT1380915 R2A

Uploaded by

Copyright:

Available Formats

LTE L13 Radio Network Design

This book is a training document and contains simplifications.

The contents of this document are subject to revision without

This document is not intended to replace the technical

This document was produced by Ericsson.

 The book is to be used for training purposes only and it is

-2 - © Ericsson AB 2013 LZT1380915 R2A

1 LTE INTRODUCTION ........................................................................9

2 DIMENSIONING PRINCIPLES ....................................................... 13

2 LTE AIR INTERFACE ...................................................................... 15

4 LTE DOWNLINK PHYSICAL RESOURCES ................................... 18

4.1 DOWNLINK REFERENCE SIGNALS........................................... 20

4.2 DOWNLINK L1/L2 CONTROL SIGNALING ................................. 21

4.3 SYNCHRONIZATION SIGNALS (SS) .......................................... 22

4.4 BROADCAST CHANNEL ............................................................. 23

4.5 DOWNLINK USER PLANE DATA ................................................ 24

4.6 DOWNLINK USER DATA RATES ................................................ 29

5 LTE UPLINK PHYSICAL RESOURCES.......................................... 33

5.1 UPLINK USER DATA RATES ...................................................... 35

6 LTE UE CAPABILITIES .................................................................. 36

7 LTE FREQUENCY BANDS ............................................................. 37

9 RADIO WAVE PROPAGATION ...................................................... 38

9.1 OKUMURA-HATA MODEL .......................................................... 38

9.2 WALFISH-IKEGAMI MODEL........................................................ 39

CHANNEL MODELS ............................................................................ 41

3 LTE TRAFFIC .................................................................................. 43

1.1 WEB BROWSING TRAFFIC ........................................................ 45

1.2 EMAIL TRAFFIC .......................................................................... 46

LZT1380915 R2A © Ericsson AB 2013 -3 -

1.3 VIDEO STREAMING TRAFFIC .................................................... 47

1.4 FILE DOWNLOAD TRAFFIC........................................................ 48

1.5 VOICE TRAFFIC .......................................................................... 48

2 INTERNET PROTOCOLS USED FOR LTE TRAFFIC .................... 49

2.1 TRANSMISSION CONTROL PROTOCOL (TCP) ........................ 49

2.1.1 TCP OPERATION ..................................................................... 52

2.1.2 TCP FLOW CONTROL ............................................................. 53

2.1.3 TCP THROUGHPUT ................................................................. 54

2.2 USER DATAGRAM PROTOCOL (UDP) ...................................... 56

2.3 HYPERTEXT TRANSFER PROTOCOL (HTTP) .......................... 58

2.3.1 WEB OPERATION EXAMPLE .................................................. 59

2.4 FILE TRANSFER PROTOCOL (FTP) .......................................... 60

3 VOICE OVER LTE .......................................................................... 61

3.1 HARQ EFFECT ON VOICE SERVICE ......................................... 62

4 LTE DIMENSIONING ....................................................................... 63

2 LTE NETWORK DIMENSIONING EXAMPLE ................................. 65

2.1 CELL THROUGHPUT (TCELL) ....................................................... 67

3.1 SITE-TO-SITE DISTANCE EXPRESSED AS SIGNAL

3.2 POWER CONTROL TARGET ...................................................... 72

3.3 PUSCH LOAD .............................................................................. 72

3.4 UPLINK COVERAGE CALCULATION ......................................... 73

3.4.1 THERMAL NOISE ..................................................................... 74

3.4.2 UPLINK SYSTEM REFERENCE POINT ................................... 76

3.4.3 NOISE RISE ............................................................................. 77

-4 - © Ericsson AB 2013 LZT1380915 R2A

3.4.4 UL RESOURCE BLOCK ALLOCATION .................................... 78

3.4.5 POWER LEVEL ........................................................................ 79

3.4.6 UL BIT RATES .......................................................................... 80

3.4.7 LOG-NORMAL FADING ............................................................ 82

3.4.8 UL CELL EDGE BIT RATES ..................................................... 83

3.4.9 UL LINK BUDGET ..................................................................... 84

3.5 UL CAPACITY CALCULATION .................................................... 86

3.5.1 AVERAGE RX POWER ............................................................ 86

3.5.2 CELL THROUGHPUT ............................................................... 88