LTE Workshop v3 PDF

LTE-VoLTE Workshop
AUP - Amdocs LTE team

May/2018
Agenda
▪ LTE
▪ Introduction & Architecture
▪ Radio Interface description
▪ Logical Channels
▪ MIMO description
▪ PRACH procedure & main parameters
▪ Signalling
▪ Mobility & connection states
▪ HandOver procedures (intra/inter X2/S1/IRAT)
▪ Metric Definitions (RSSI, RSRP, RSRQ, SINR…)
▪ LTE Scenaries (definitions/parameters)
▪ LTE Optimization (cases example)
▪ VoLTE in LTE
▪ Introduction
▪ Definition of CSFB, SVLTE, VoLTE and OTT
▪ SRVCC definition
▪ Architecture
Information Security Level 2 – Sensitive

2 © 2017 – Proprietary & Confidential Information of Amdocs
LTE and UMTS comparison (1/2)
UMTS LTE
Core Network
CS and PS PS
Domains
Flat Architecture No (includes RNC) Yes
5MHz
10MHz with 2 carrier HSDPA capability (3GPP release 8)
Channel Bandwidth 10MHz with 2 carrier HSUPA capability (3GPP release 9)
1.4, 3, 5, 10, 15, 20MHz
20MHz with 4 carrier HSDPA capability (3GPP release 10)
Multiple Access WCDMA OFDMA/ SC-FDMA
Frequency Re-Use Re-use of 1 Re-use of 1
Yes for DCH and HSUPA

Soft Handover Support No for HSDPA
No
Fast Power Control Yes for DCH and HSUPA

No, slower power control used for uplink
Support No for HSDPA
QPSK for DCH

Uplink Modulation 16QAM for HSUPA
QPSK, 16QAM, 64QAM
QPSK for DCH

Downlink Modulation 16QAM and 64QAM for HSDPA
QPSK, 16QAM, 64QAM, 256QAM
Adaptive Modulation Yes for HSDPA and HSUPA Yes

LTE and UMTS comparison (2/2)
UMTS LTE
Uplink MIMO No No
Downlink MIMO 2x2 for HSDPA 2x2 and 4x4
Peak Uplink 85Mbps (20MHz channel, 64AQM, Coding Rate 1,

23Mbps (10MHz channel, 16QAM, Coding rate 1)
Throughput normal cyclic prefix, 2PUCCH Resource Blocks per slot)
Peak Downlink 325Mbps (20MHz channel, 64QAM, 4x4 MIMO, Coding

86Mbps (10MHz channel, 64QAM, 2x2 MIMO,
Throughput Coding rate 1, 15 HS-PDSCH codes per carrier)
rate 1, normal cyclic prefix, 1 PDCCH symbol per sub
frame)
No for DCH
Hybrid ARQ Support Yes for HSDPA and HSUPA
Yes
No for DCH
BTS Scheduling Yes for HSDPA and HSUPA
Yes
Neighbor planning Yes No if ANR capability is supported
Scrambling Code
Yes No
Planning
Physical Layer Cell
No Yes
Identity Planning

Evolution of Network Architecture
CS and PS
TDMA
BSC Core Network
CS and PS
WCDMA
RNC Core Network
Only IP PS
OFDMA network Core Network

LTE and UMTS functional architecture differences
PDN GateWay Serving GateWay
PGW
GGSN (only user plane functions)
SGW
Mobility Management Entity
SGSN MME
(not user plane
functions)
RNC
Control plane and user plane

split for better scalability
between MME and gateways
RNC functions
moved to eNodeB

UTRAN Long Term Evolution
Radio Access Network – E-UTRAN Evolved Packet Core (EPC)
S1-MME
S6a
X2 S1-MME
eNB HSS
MME PCRF
S11 S7
eUu
to PDN
UE
S1-U S5/S8 (Pocket Data Network)
Serving PDN
eNB Gateway Gateway

Evolved Node B (eNB) functions
• Physical layer and Radio Resource Management (bearer control,
mobility control, scheduling)
• Ciphering and integrity protection for the air interface
• MME selection if necessary
• Exchange of crucial cell-specific data to other base stations
(eNBs)
• User Plane data transfer to and from serving gateway S1-MME
• Transmission of messages coming from MME and to MME
(broadcast, paging) MME
• Collection and evaluation of the measurements eNB
X2 S1-U
X2-CP interface – allows signaling between eNodeB
X2-UP interface – allows the transfer of application data between eNodeB
S1-U interface – allows application data transfer through the Serving Gateway
Serving
S1-MME interface – allows signaling with the MME
Gateway
eNB

Mobility Management Entity (MME) functions
• UE attach and detach procedures control
• Signaling for transport bearers setup and release control HSS
• Authentication and integrity protection control
• Tracking Area (TA) updates control S6a
• Paging control
• Roaming control S1-MME
S11 interface – allows signaling information for mobility MME

and bearer management to be transferred
S11
S6a interface – allows signaling with Home Subscriber
Server (HSS – evolution of HLR) eNB
S1-MME interface – allows signaling with the eNodeB
Serving
Gateway

OFDM
▪ Available bandwidth (frequency spectrum) is divided into many overlapping
subcarriers (multi-carrier transmission)
▪ All subcarriers are orthogonal to each other (FFT property)
▪ Single subcarrier can carry only one modulated and coded symbol
▪ Subcarrier spacing is determined by the sampling frequency and FFT size
▪ Constant spacing for all bandwidth configurations in LTE
FFT size and sampling frequency depends on the

bandwidth configurations in order to keep the
constant subcarrier spacing.
Sampling is an integer multiple of 3.84 MHz
(WCDMA symbol sampling)

OFDM versus coventional FDM
• OFDM allows a tight packing of small carrier - called the subcarriers - into a given frequency
band.
Power Density
Power Density
Saved
Bandwidth
Frequency (f/fs) Frequency (f/fs)

Propagation delay exceeding the Guard Period
2
1
3
4
Time Domain T Tg
SYMBOL
Delay spread > Tg 1

 ISI time
2
time
3
time
Tg: Guard period duration
ISI: Inter-Symbol Interference 4
time
The Cyclic Prefix OFDM symbol
• In all major implementations of the OFDMA technology (LTE,

WiMAX) the Guard Period is equivalent to the Cyclic Prefix CP. OFDM symbol
• This technique consists in copying the last part of a symbol
shape for a duration of guard-time and attaching it in front of the
symbol (refer to picture sequence on the right).
• CP needs to be longer than the channel multipath delay
spread (refer to previous slide). OFDM symbol
• A receiver typically uses the high correlation between the CP

and the last part of the following symbol to locate the start of the
symbol and begin then with decoding.
OFDM symbol
Cyclic Part of symbol

prefix used for FFT
processing in the
13
Information Security Level 2 – Sensitive receiver
© 2017 – Proprietary & Confidential Information of Amdocs
LTE Radio Frames - FDD mode
Radio Frame – 10ms
0 1 2 3 16 17 18 19
Frequency (subcarriers)
Subcarrier
0 1 2 3 16 17 18 19 frequency –
180KHz
Sub-frame – 1ms Slot– 0,5ms
0 1 2 3 4 5 6 The number of Symbols per Slot (0.5ms)

could be 6 or 7 depending on the Cyclic
Prefix length
Symbols
Time (radio frames)

LTE OFDM symbol: 66.67µs (1/15kHz)
Subframe structure & CP length
• Subframe length: 1 ms for all bandwidths
• Slot length is 0.5 ms
– 1 Subframe= 2 slots
• Slot carries 7 symbols with normal CP or 6 symbols with long CP
– CP length depends on the symbol position within the slot:
▪ Normal CP: symbol 0 in each slot has CP = 160 x Ts = 5.21μs; remaining symbols CP= 144 x Ts = 4.7μs
▪ Extended CP: CP length for all symbols in the slot is 512 x Ts = 16.67µs
Short cyclic prefix: Ts:

5.21 s ➢ ‘sampling time’ of the overall channel
➢ basic Time Unit
Long cyclic prefix: ➢ = 32.5 nsec
16.67 s 1 sec
= Data Ts =
= Cyclic prefix Copy Subcarrier spacing X max FFT size

LTE OFDM symbol: 66.67µs (1/15kHz)
LTE resource grid
• PRB is defined as consisting of 12 consecutive subcarriers for one slot (0,5ms)
• PRB is the smallest element of resource allocation assigned by the eNB scheduler
• NRB DL defines the numer of resources blocks used in the DL
Subcarrier 0 1 2 3 4 5 6 0 1 2 3 4 5 6
1 0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
KHz
180
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
0 1 2 3 4 5 6 0 1 2 3 4 5 6
Subcarrier
Resource
12 1 slot 1 slot Element
1 ms subframe
OFDM Key Parameters
Bandwidth options: 1.4, 3, 5, 10, 15 and 20 MHz
Variable Bandwidth (BW)
A higher Bandwidth is better because a higher

peak data rate could be achieved and also bigger
capacity. Also the physical layer overhead is lower
for higher bandwidth Frequency
Δf
Subcarrier Spacing (Δf = 15 KHz)
→ The Symbol time is Power
Tsymbol = 1/ Δf = 66,7μs density
A compromise needed between:

→ Δf as small as possibile so that the symbol time
Tsymbol is as large as possibile.
This is beneficial to solve Intersymbol Interference in Frequency
time domain Amplitude
→ A too small subcarrier spacing it is increasing the
ICI = Intercarrier Interference due to Doppler effect
TCP TSYMBOL
CP T
SYMBOL
17
Information Security Level 2 – Sensitive Time
TS
OFDM Key Parameters
The number of Subcarriers Nc
→ Nc x Δf = BW
In LTE not all the available channel bandwidth (e.g. 20 MHz) will be used. For the transmission bandwidth typically 10% guard
band is considered (to avoid the out band emissions).
If BW = 20MHz → Transmission BW = 20MHz – 2MHz = 18 MHz
→ the number of subcarriers Nc = 18MHz/15KHz = 1200 subcarriers
Channel Bandwidth [MHz]
Transmission Bandwidth Configuration [RB]

Transmission
Bandwidth [RB]
Channel edge
Channel edge
Resource block
Active Resource Blocks DC carrier (downlink only)

OFDM Key Parameters
FFT (Fast Fourier Transform) size Nfft
Nfft should be chosen so that:
1. Nfft > Nc number of subcarriers (sampling theorem)
2. Should be a power of 2 (to speed-up the FFT operation)
Therefore for a bandwidth BW = 20 MHz → Nc = 1200 subcarriers not a power of 2
→ The next power of 2 is 2048 → the rest 2048 -1200 = 848 padded with zeros
Sampling rate fs
This parameter indicates what is the sampling frequency:

→ fs = Nfft x Δf
Example: for a bandwidth BW = 5 MHz (with 10% guard band)
The number of subcarriers Nc = 4.5 MHz/ 15 KHz = 300
300 is not a power of 2 → next power of 2 is 512 → Nfft = 512
Fs = 512 x 15 KHz = 7,68 MHz → fs = 2 x 3,84 MHz which is the chip rate in UMTS!!
The sampling rate is a multiple of the chip rate

from UMTS/ HSPA. This was acomplished because the
subcarriers spacing is 15 KHz. This means UMTS and LTE
have the same clock timing!
OFDM Key Parameters for FDD and TDD Modes
Bandwidth 1.4 MH 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz

(NC Δf)
Subcarrier Fixed to 15 kHz (7.5kHz defined for MBMS)

Spacing (Δf)
Symbol Tsymbol = 1/Δf = 1/15kHz = 66.67μs

duration
Sampling rate, 1.92 3.84 7.68 15.36 23.04 30.72

fS (MHz)
Data 72 180 300 600 900 1200

Subcarriers (NC)
NIFFT 128 320 512 1024 1536 2048

(IFFT Length)
Number of 6 15 25 50 75 100
Resource Blocks
Symbols/slot Normal CP=7; extended CP=6
CP length Normal CP=4.69/5.12μsec., Extended CP= 16.67μsec

Logical, transport and physical channels
Upper Layers
DL UL
RLC
MCCH
MTCH
CCCH
DTCH
DCCH
BCCH
PCCH
CCCH
DCCH
DTCH
Logical channels
DL-SCH MAC
MCH
UL-SCH
BCH
PCH
RACH
Transport channels
PHY
PCFICH
PDCCH
PDSCH
PHICH
PMCH
PBCH
PUCCH
PRACH
PUSCH
Information Security Level 2 – Sensitive Air interface
Logical Channels in LTE
Logical Channel
• type of information;
• MAC priority;
• UE identification;
Control Channel Traffic Channel
• signaling info (RRC); • user plane data (IP)
BCCH DCCH DTCH MTCH

• broadcast control ch.;
• system information; • dedicated control ch.; • dedicated traffic • multicast traffic ch.;
• downlink only; • dedicated RRC signaling channel; • MBMS traffic for broadcast
with one UE; • IP user plane data; or multicast MBMS services;
• bi-directional; • bi- or uni-directional; • downlink only;
PCCH
• paging control ch.;
• paging message for
LTE_IDLE UE;
• downlink only;
CCCH
• common control ch.;
• initial access signaling for
RRC_IDLE UE;
MCCH
• multicast control ch.;
• MBMS
Information Securitycontrol
Level 2 – information
Sensitive
22 © 2017 for
– Proprietary
MTCH;& Confidential Information of Amdocs
• downlink only;
Transport Channels in LTE
Transport Channel (TrCH)
• transfer characteristics:
• delay, collision risk;
• supported block sizes and number of blocks;
• support for HARQ;
• support for beam-forming;
• support for DRX/DTX;
• coding (reliability);
Downlink TrCH • static | dynamic resource allocation; Uplink TrCH
• support for QPSK, 16QAM, 64QAM;
BCH RACH
• broadcast channel; • random access channel;
• carries BCCH; • carries no logical channel;
• only for initial L1 access
PCH request;
• paging channel;
UL-SCH
• carries PCCH;
• uplink shared channel;
MCH • carries CCCH, DCCH, DTCH;
• supports HARQ;
• multicast channel;
• carries MTCH, MCCH;
DL-SCH
• downlink shared channel;
• carries DCCH, DTCH, BCCH,
MTCH, MCCH;
23 • supports
© 2017 – Proprietary & Confidential HARQ;
Information of Amdocs
Physical Channels in LTE
Physical Channels / Signals
• set of OFDM/SC-FDMA resource elements;
• carry higher layer data (physical channel PhyCH) or
• used internally by L1 (physical channel/signal);
Downlink PhyCH Downlink Signal Uplink Signals Uplink PhyCH
PBCH DL reference signal Demodulation ref. signal PUSCH

• physical broadcast ch.; • pre-defined 2-dimensional • pre-defined sequence • phys. UL shared channel;
• carries BCH (BCCH); orthogonal/pseudo-noise sent along with • carries UL-SCH;
sequence; PUSCH/PUCCH
• used for DL channel • used for uplink channel PUCCH
PDSCH estimation, demodulation; estimation, demodulation;
• phys. DL shared channel; • phys. UL control channel;

• carries PCH and DL-SCH;
DL synch. signal Sounding ref. signal • L1 information
• 1 of 3 pre-defined • pre-defined (long)
PMCH sequences (Zadoff-Chu); sequence sent alone;
• associated with cell-id; • used by NW to optimize
PRACH
• phys. multicast channel; • used for cell detection and channel dependent • phys. random access
• carries MCH; initial time/phase synch.; scheduling; (channel);
• carries RACH (access
request preamble);
PDCCH • [in TS 36.211 referenced
as signal, not as channel]
• phys. DL control channel;
• L1 control information
(scheduling assignments);
PCFICH
• phys. control format
indicator channel
• L1 control information (no.
of ODFM symbols used for
PDCCH);

Downlink Reference Signal
▪ DL Reference Signal is spread over the whole bandwidth
▪ Pilot signal is necessary to perform channel estimation and demodulation (e.g. CPICH in WCDMA)
▪ Channel estimation in LTE is based on reference signals – CQI, RSRP, RSRQ
▪ Reference signals position in time domain is fixed (0 and 4 for Type 1 Frame) whereas in frequency domain it
depends on the Cell ID
▪ In case more than one antenna is used (e.g. MIMO) the Resource Elements allocated to reference signals
on one antenna are DTX on the other antennas
▪ Reference signals are modulated to identify the cell to which they belong
Resource Elements allocated to Reference Signals cannot be

used for anything else → overhead
- If 1 Tx antenna*: 4 RSs per PRB
- If 2 Tx antenna*: there are 8 RSs per PRB
- If 4 Tx antenna*: there are 12 RSs per PRB

MIMO
MIMO Overview
Data Transmission Number of Antennas Number of Users
Pre-Coding SISO SU-MIMO

(beamforming) (Single Input Single Output) (Single User MIMO)
single data stream sent over
multiple input antennas
pre-coding
MISO
(Multiple Input Single Output)
X …
Spatial Multiplexing
multiple data stream sent over SIMO
multiple input antennas (Single Input Multiple Output) MU-MIMO
pre-coding
X1
…
… …
…
Xn
MIMO
(Multiple Input Multiple Output)
Diversity Coding
single data stream sent over
multiple input antennas … …
with different coding
e.g. CDMA soft handover
DL PDSCH
• The Physical Downlink Shared Channel (PDSCH) is the main data-bearing
downlink channel in LTE
• It is used for all user data, as well as for broadcast system information
which is not carried on the PBCH, and for paging messages – there is no
specific physical layer paging channel in the LTE system dlMimoMode PDSCH Transmission Scheme TMs involved in
PDSCH
There are the following mode in case of PDSCH: SingleTX Single stream TM1
2-way TXDiv Transmit Diversity using 2 TM2

•Transmission Mode 1: Transmission from a single eNodeB antenna port transmit antennas
•Transmission Mode 2: Transmit diversity 4-way TXDiv Transmit Diversity using 2 TM2
transmit antennas
•Transmission Mode 3: Open-loop spatial multiplexing
Static Open Open Loop MIMO using 2 TX TM3
•Transmission Mode 4: Closed-loop spatial multiplexing Loop MIMO antennas
•Transmission Mode 5: Multi-user Multiple-Input Multiple-Output (MIMO) (2x2)
•Transmission Mode 6: Closed-loop rank-1 precoding Dynamic Open Open Loop MIMO using 2 TX TM2, TM3
Loop MIMO antennas
•Transmission Mode 7: Transmission using UE-specific reference signals (2x2)
dlMimoMode : Downlink MIMO mode Closed Loop Closed Loop MIMO using 2 TX TM4
SingleTX (0), MIMO (2x2) antennas
2-way TXDiv (10), Closed Loop Closed Loop MIMO using 4 TX TM4, TM2
4-way TXDiv (11), MIMO (4x2) & antennas
Static Open Loop MIMO (2x2) (20), (4x4)
Dynamic Open Loop MIMO (2x2) (30), Single Stream Single stream beamforming TM7, TM2 (TM3*)
Closed Loop MIMO (2x2) (40), Beamforming
Closed Loop MIMO (4x2) (41), & Closed Loop MIMO (4x4) (43)
Information Security Level 2 – Sensitive Dual Stream Dual stream beamforming TM8, TM2 (TM3*)
27 © 2017 – Proprietary & Confidential Information of Amdocs Beamforming
PRACH Planning
Wrap Up
▪ Steps:
▪ - Define the prachConfIndex
• Depends on preamble format (cell range)
• It should be the same for each cell of a site
▪ - Define the prachFreqOff
• Depends on the PUCCH region
• It can be assumed to be the same for all cells of a network (simplification)
▪ - Define the PrachCS
• Depends on the cell range
• If for simplicity same cell range is assumed for all network then prachCS is the same for all cells
▪ - Define the rootSeqIndex
• It points to the first root sequence
• It needs to be different for neighbour cells
• rootSeqIndex separation between cells depends on how many are necessary per cell
(depends on PrachCS)

RACH Procedure
Introduction
▪ Used in several cases: E.g. initial access (from idle to connected), to re-establish a radio link
after a failure, as part of the handover
▪ Process starts by UE selecting randomly a preamble from the list of preambles broadcasted in
the BCCH
▪ There are 64 preambles (sequences) per cells
1 frame (10ms)
• RACH Operation uses
– Frequency: 6 PRBs (1 RACH
3MHz BW (15 PRBs)

resource = 6 PRBs)
– Time: Variable depending on
the format ( 4 possible formats
in FDD)

Preamble Formats
▪ 3GPP (TS36.211) specifies 4
random access formats for
FDD
• Difference in formats is based in the different durations for the cyclic prefix,
sequence and guard time which have an effect on the maximum cell radius
Recommendation:
▪ Select Format0 for cell
ranges <14.53 km
▪ Select Format1 for cell
ranges <77.34 km

PRACH Configuration Index Extract of the random access
prachConfIndex preamble configurations table (only for
supported preamble formats 0 and 1)
▪ The parameter defines the Allowed System

Frame for random access attempts, the Sub-
frame numbers for random access attempts
and the Preamble format
▪ Supported values:
▪ For Preamble Format 0: 3 to 8
▪ For Preamble Format 1: 19 to 24
▪ RACH Density indicates how many RACH

resources are per 10ms frame.
▪ Only RACH density values of 1 and 2 are
supported .E.g.
Recommendation:
▪ RACH density=1 Only one random access
attempt per frame Configure the same PRACH configuration
▪ RACH density=2 Two random access Indexes at cells belonging to the same site.
attempts per frame E.g.:
▪ 3 or 4 or 5 if RACH density=1 and 6 or 7or 8 if
RACH density=2 (Preamble Format 0)

PRACH Frequency Offset
prachFreqOff
• Indicates the first PRB available for PRACH in the UL frequency band
▪ PRACH area (6 PRBs) should be next to PUCCH area either at upper or lower border of
frequency band to maximize the PUSCH area but not overlap with PUCCH area
▪ Parameter is configured based on the PUCCH region (see PUCCH dimensioning) i.e. its value
depends on how many PUCCH resources are available.
▪ If PRACH area is placed at the lower border of UL frequency band then:
PRACH-Frequency Offset= roundup [PUCCH resources/2]
• If PRACH area is placed at the upper border of the UL frequency band then:
PRACH-Frequency Offset= NRB -6- roundup [PUCCH resources/2]
NRB: Number of Resource Blocks

PRACH Cyclic Shift
PrachCS
▪ PrachCS defines the configuration used for the preamble generation. i.e. how many cyclic shifts
are needed to generate the preamble
▪ PrachCS depends on the cell size
▪ Different cell ranges correspond to different PrachCS
▪ Simplification: To assume all cells have same size (limited by the prachConfIndex)
Recommendation:
Select PrachCS based on the cell
range E.g. if estimated cell range is
15km then PrachCS: 12
If all cells in the network are assumed
to have same cell range them
PrachCS is the same network wise

PrachCS and rootSeqIndex
▪ PrachCS defines the number of cyclic shifts (in terms of number of samples) used to generate
multiple preamble sequences from a single root sequence
▪ Example based on PrachCS=12 -> number of cyclic shifts: 119
▪ Root sequence length is 839 so a cyclic shift of 119 samples allows ROUNDDOWN (839/119)= 7 cyclic shifts
before making a complete rotation (signatures per root sequence)
▪ 64 preambles are transmitted in the PRACH frame. If one root is not enough to generate all 64
preambles then more root sequences are necessary
▪ To ensure having 64 preamble sequences within the cell it is necessary to have ROUNDUP (64/7)= 10 root
sequences per cell

PRACH Cyclic Shift
rootSeqIndex Extract from 3GPP TS 36.211 Table 5.7.2.-4 (
Preamble Formats 0-3). Mapping between logical
and physical root sequences.
Logical Physical root sequence index (in increasing order of the
▪ RootSeqIndex points to the first root sequence to be root corresponding logical sequence number)
used when generating the set of 64 preamble sequen

ce
sequences. number
▪ Each logical rootSeqIndex is associated with a single 0–23 129, 710, 140, 699, 120, 719, 210, 629, 168, 671, 84, 755, 105,
734, 93, 746, 70, 769, 60, 779
physical root sequence number. 2, 837, 1, 838
▪ In case more than one root sequence is necessary 24–29 56, 783, 112, 727, 148, 691
the consecutive number is selected until the full set is 30–35 80, 759, 42, 797, 40, 799
generated 36–41 35, 804, 73, 766, 146, 693
42–51 31, 808, 28, 811, 30, 809, 27, 812, 29, 810
52–63 24, 815, 48, 791, 68, 771, 74, 765, 178, 661, 136, 703
Recommendation:
…. …..
Use different rootSeqIndex across
neighbouring cells means to ensure 64–75 86, 753, 78, 761, 43, 796, 39, 800, 20, 819, 21, 818
neighbour cells will use different 810– 309, 530, 265, 574, 233, 606
815
preamble sequences
816– 367, 472, 296, 543
819
820– 336, 503, 305, 534, 373, 466, 280, 559, 279, 560, 419, 420, 240,
837 599, 258, 581, 229, 610
Exercise
Plan the PRACH Parameters for the sites below:

Assumptions:
▪ PUCCH resources =6
▪ Cell range = 12km (all cells have same range)
▪ BW:10MHz
Sites Cell Azimuth PrachConfIndex PrachFreqOff PrachCs rootSeqIndex

1 0
eNB #1 2 120
3 240
1 0
eNB #2 2 120
3 240
1 0
eNB #3 2 120
3 240
1 0
eNB #4 2 120
3 240
1 0
eNB #5 2 120
3 240

Solution (1/3)
Steps:
1. Define the prachConfIndex
Cell Range is 12 Km therefore Format 0 is planned
For start RACH density 1 is selected
Therefore:
prachConfIndex = 3, for example the same in all the cell
2. Define the prachFreqOff

We assume that PRACH area is placed at the upper border of the UL frequency band then:
PRACH-Frequency Offset= NRB -6- roundup [PUCCH resources/2]
(NRB = 50 for 10 MHz (1...50) & PUCCH resources = 6)
prachFreqOff = 50 – 6 – roundup[6/2] = 41

Solution (2/3)
Steps:
3. Define the prachCs
Cell range is 12 Km therefore the prachCS = 11
In this case there are 93 cyclic shifts to generate the
preambles and 9 signatures per root sequence
4. Define the rootSeqIndex
There are 8 root signatures required per cell
The planning could be done to allocate the rootSeqIndex per cluster
We assume that the planned cells in the example are belonging to
one cluster
In this way the first cell is taking the rootSeqIndex= 0..7, the second cell
8..15, the third cell 16..23 and so on

Solution (3/3)
Plan the PRACH Parameters for the sites below:
Assumptions:
▪ PUCCH resources =6
▪ Cell range = 12km (all cells have same range)
▪ BW:10MHz
Sites Cell Azimuth PrachConfIndex PrachFreqOff PrachCs rootSeqIndex

1 0 3 41 11 0
eNB #1 2 120 3 41 11 8
3 240 3 41 11 16
1 0 3 41 11 24
eNB #2 2 120 3 41 11 32
3 240 3 41 11 40
1 0 3 41 11 48
eNB #3 2 120 3 41 11 56
3 240 3 41 11 64
1 0 3 41 11 72
eNB #4 2 120 3 41 11 80
3 240 3 41 11 88
1 0 3 41 11 96
eNB #5 2 120 3 41 11 104
3 240 3 41 11 112

Protocol Stack and msg flow

Enhanced scheduling
▪ In GSM, WCDMA and HSPA it is only possible to schedule users in the time domain
▪ LTE, due to OFDM-based air interface, introduces a new way of joint scheduling in the time and
frequency domain
CDMA OFDMA
Single Carrier transmission does The part of total available
not allow to perform frequency channel experiencing bad
aware scheduling. Every fading channel condition (fading) can
gap effects the data. be avoided during resource
allocation procedure.
MCS Index Modulation TBS Index
MCS for PDSCH

I MCS Order Q m I TBS
0 2 0
1 2 1
2 2 2
3 2 3
4 2 4 QPSK
5 2 5
▪ 29 MCS’s defined for PDSCH (MCS0 – 6 2 6
MCS28) (table Table 7.1.7.1-1) 7
8
2
2
7
8
9 2 9
▪ Four modulation schemes possible: 10 4 9
QPSK, 16QAM, 64QAM, 256QAM 11 4 10
12
13
4
4
11
12
16QAM
▪ TBS index refers to TBS table in 3GPP 14 4 13
TS36.213 (Table 7.1.7.1-1 is for the UE 15
16
4
4
14
15
which does not support 256 QAM and 17 6 15
18 6 16
Table 7.1.7.1-1A is for the UE which 19 6 17
support 256 QAM) 20
21
6
6
18
19
22 6 20 64QAM
▪ Note, 264QAM currently supported. 23 6 21
24 6 22
256QAM 25 6 23
26 6 24
27 6 25
28 6 26
29 2
30 4
Information Security Level 2 – Sensitive 31 6 reserved
MCS Index Modulation TBS Index Redundancy
MCS for PUSCH

Order Version
rvidx
0 2 0 0
1 2 1 0
2 2 2 0
3 2 3 0
▪ 29 MCS’s defined for PDSCH (MCS0 – MCS28) 4 2 4 0
5 2 5 0 QPSK
▪ Three modulation schemes possible: QPSK, 6
7
2
2
6
7
0
0
16QAM, 64QAM 8 2 8 0
9 2 9 0
▪ TBS index refers to TBS table in 3GPP TS36.213 10
11
2
4
10
10
0
0
(table 7.1.7.2.1-1) 12 4 11 0
13 4 12 0
14 4 13 0
15 4 14 0
16 4 15 0
16QAM
17 4 16 0
18 4 17 0
19 4 18 0
20 4 19 0
21 6 19 0
22 6 20 0
23 6 21 0
24 6 22 0 64QAM
25 6 23 0
26 6 24 0
27 6 25 0
28 6 26 0
29 1
30 2
43 © 2017 – Proprietary & Confidential Information of Amdocs 31 reserved 3
NPRB NPRB
TBS mapping (PDSCH Example)

MCS Index Modulation TBS Index
TBS translation table (incomplete)
Order I TBS N PRB
1 2 3 4 … 99 100 101 … 109 110
0 2 0
1 2 1 0 16 32 56 88 … 2728 2792 2792 … 2984 3112
2 2 2 1 24 56 88 144 … 3624 3624 3752 … 4008 4008
3 2 3 2 32 72 144 176 … 4392 4584 4584 … 4968 4968
4 2 4 3 40 104 176 208 … Example: 4 PRB’s @ TBS index
5736 5736 5992 … 6456 6456
5 2 5 4 56 120 208 256 … 6968 7224 7224 … 7736 7992
6 2 6 5 72 144 224 328 … 18 allocated to UE
8760 8760 8760 … 9528 9528
7 2 7 6 328 176 256 392 … 10296 10296 10680 … 11448 11448
8 2 8
7 104 224 328 472 … 12216 12216 12216 … 13536 13536
9 2 9
8 120 256 392 536 … 14112 14112 14112 … 15264 15264
10 4 9
11 4 10
TBS=1544bits
9 136 296 456 616 … 15840 15840 15840 … 16992 17568
12 4 11 → instantaneous throughput: 1544bits/1ms TTI = 1.544Mbps
10
11
144
176
328
376
504
584
680
776
…
…
17568
19848
17568
19848
17568
20616
…
…
19080
22152
19080
22152
13 4 12
14 4 13 → coding rate:
12 208 440 680 904 … 22920 22920 22920 … 24496 25456
15 4 14 13 224 488 744 1000 … 25456 25456 26416 … 28336 28336
16 4 15 TBS/(N *12sucarriers_per_PRB*14symbols_per_TTI*6bits_per
14
PRB
256 552 840 1128 … 28336 28336 29296 … 31704 31704
17
18
6
6
15
16
_64QAM_symbol) = 1544/(4*12*14*6) = 0.38
15 280 600 904 1224 … 30576 30576 30576 … 34008 34008
16 328 632 968 1288 … 31704 32856 32856 … 35160 35160
19 6 17
17 336 696 1064 1416 … 35160 36696 36696 … 39232 39232
20 6 18
21 6 19 18 376 776 1160 1544 … 39232 39232 40576 … 43816 43816
22 6 20 19 408 840 1288 1736 … 42368 43816 43816 … 46888 46888
Example: MCS20 → 64QAM
23 6 21 20 440 904 1384 1864 … 46888 46888 46888 … 51024 51024
24 6 22 21 488 1000 1480 1992 … 48936 51024 51024 … 55056 55056
25 6 23 22 520 1064 1608 2152 … 52752 55056 55056 … 59256 59256
26 6 24 23 552 1128 1736 2280 … 57336 57336 57336 … 61664 63776
27 6 25 24 584 1192 1800 2408 … 61664 61664 61664 … 66592 66592
28 6 26
25 616 1256 1864 2536 … 63776 63776 63776 … 68808 71112
29 2
44 30 © 2017 – Proprietary
4 & Confidential Information of Amdocs
26 712 1480 2216 2984 … 73712 75376 75376 … 75376 75376
31 6 reserved
Call Search Procedure (1/2)
1. PSS Primary Synchronisation Signal
(Time-slot & Frequency synchronisation
+ Physical cell id (0,1,2) )
2. SSS Secondary Synchronisation Signal

(Frame synchronisation
+ Physical Cell id group (1..168) )
3. DL Reference Signals
(Channel estimation & measurements –
like CPICH* in UMTS)
4. PBCH – Physical Broadcast Channel

*CPICH = Common Pilot Channel
MIB = Master Information Block (MIB* – DL system bandwidth, PHICH
PHICH = Physical HARQ Indicator configuration)
Channel

Call Search Procedure (2/2)
5. PCFICH Physical Control Format Indicator Channel
(How many symbols (1,2,3) in the beginning of
the sub-frame are for PDCCH)
6. PDCCH Physical Downlink Control Channel

(Resource allocation for PDSCH )
7. PDSCH Physical Downlink Shared Channel

(*SIBs: Cell global ID, parameters for cell
selection reselection, … )
*SIB = System Information Block → CELL SELECTION & RESELECTION

(according to 3GPP TS36.306)
Random Access (1/2)
8. PRACH preamble (A )
(A – is the first random preamble )
.
.
.
8. PRACH preamble (C)
(C – is the 3rd random preamble )
For the initial random access the steps are the following
8A – the mobile is selecting randomly one preamble. There are in total 64 preambles available preambles in one cell. In this
case with A it is intended to note the first random preamble
8C – If no answer is received from the Node-b then the mobile is repeating the preamble. In this example with C is noted
the 3rd preamble. That means that the assumption is that after three preambles the UE is receiving an answer from the
Node-B

Random Access (2/2)
(Resource allocation for PDSCH)

(Random Access response,
ID of the received preamble,
C-RNTI *)
*C-RNTI = Cell Radio Network → Possible Next steps:

Temporary Identity ▪ RRC Connection Establishment
▪ Registration
48
▪ UE-CN Signalling (Attach)
DL Transmission
1. DL Reference signals
2. PUCCH Physical Uplink Control Channel (or PUSCH)

(CQI based on DL reference signals measurements)
(Downlink assignment for PDSCH: Modulation &
coding, resource blocks)
(user data -> initial transmission)
CQI = Channel Quality Indicator
ACK = Acknowledgment (ACK/ NACK for HARQ)
NACK = Negative ACK
HARQ = Hybrid Automatic Repeat 7. PDSCH Physical Downlink Shared Channel
Request
49
(user data → eventual re-transmission)
UL Transmission
(UL scheduling request)
2. UL Sounding Reference Signal
(used by Node-B for channel dependent scheduling)
3. UL Demodulation Signal
(UL channel estimation, demodulation,
→ Like *DPCCH in UMTS)
(UL grant – capacity allocation)
5. PUSCH Physical Uplink Shared Channel
(user data → initial transmission)
6. PHlCH Physical HARQ Indicator Channel
*DPCCH = Dedicate Physical Control
Channel (ACK/ NACK for HARQ)
ACK = Acknowledgment
NACK = Negative ACK 7. PUSCH Physical Uplink Shared Channel
HARQ = Hybrid Automatic Repeat
Request
(user data → eventual re-transmission)
SIB Information (1/2)
•Access Class Information
•PLMN Identity list
•TAC
•Cell Barred Indication
SIB 2: •Uplink Carrier Frequency
•UL Bandwidth
•MBSFN Configuration Information
•Intra frequency reselection
•CSG Indication
SIB 1:
•CSG Identity
•Qrxlevminoffset
•P-Max
•Frequency band indicator
•SI periodicity mapping information •Cell Reselection Information
•SIB window length (Common SI scheduling •Q-Hyst
window for all SIB •Speed State Reselection Parameters
•System Info Value Tag •Q-Hys Speed SF (Scaling Factor)
•Treselection EUTRA
SIB 3:
•Treselection EUTRA SF
•S Intra Search
•Cell Reselection Serving Info
•S-Non-Intra Search Info
•Threshold Serving Low Value
•Intra Freq Cell Reselection Info
•P-Max
•Intra Freq Neighbour Cell List
SIB 4:
•Allowed measurement Bandwidth
•Q-OffsetCell
•Intra Freq Black Cell List
•CSG Physical Cell ID Range
The periodicity of MIB is 40ms SIB1 is sent with the periodicity of 80ms
SIB Information (2/2)
SIB 6:
• Carrier Frequency List UTRA
•Inter Frequency Carrier Freq List • UTRA Reselection
•Inter Frequency Carrier Freq Info
Information
SIB 5: •Inter Frequency Neighbor Cell List
•Inter Frequency Neighbor Cell Info
SIB 7:
•Inter Frequency Black Cell List • Carrier Frequency List GERAN
•Inter Frequency Black Cell Info
• GERAN Reselection Information
SIB 8: • CDMA2000 Information

SIB 10: • Earthquake and Tsunami Warning
System primary Notification
SIB 9: • Home eNB Name
SIB 11: • Earthquake and Tsunami Warning

System secondary Notification

SIB messages example
SIB 1 SIB 3
SIB 2

Radio Bearers

LTE Call flow example – attach and default
bearer setup (1/2)

LTE Call flow example – attach and default
bearer setup (2/2)

LAYER 3 CALL FLOW-Log file

Layer 3 messages examples

Dedicated & Default Bearer
• Default Bearer : When LTE UE attaches to the network for the first time, it will be assigned default bearer
which remains as long as UE is attached. Each default bearer comes with an IP address
• Dedicated bearers : It provides dedicated tunnel to one or more specific traffic (i.e. VoIP, video etc).
Dedicated bearer acts as an additional bearer on top of default bearer.

Mobility
▪ Concept Comparison
Connected Connected Connected Connected Connected Connected
mode mode mode mode mode mode
Idle Idle Idle Idle Idle Idle
• idle mode mobility • operates on the edge of idle- • connected mode mobility
• no active data/voice connection connected mode mobility • maintaining data/voice
is in place • release procedure with connection when UE moves to
• UE selects a more suitable cell redirection information different cell, frequency layer or
and camp on it • UE is ordered to switch to RAT
• UE performs re-selection actions another frequency layer or RAT • resources are reserved in advance
independently, following the rules • no resources are reserved in on target side
given by the network via advance on target side • service interruption is unnoticeable
Broadcast Channel (BCH) • Radio Access Network (RAN) from end-user perspective
• Absolute Priority (AP) based cell Information Management (RIM) – • seamless Quality of Experience
re-selection mechanism System Information Block (SIB) (QoE)
tunneling
reselection redirection handover

Interworking Functionalities
SRVCC
CS fallback
Inter-System HO
GSM CS Connected
3G DCH LTE RRC CONNECTED
PS HO
3G FACH GSM PS Transfer
3G URA/CELL PCH
connection
connection establishement/release
connection
establishement/release establishement/release
3G IDLE LTE RRC IDLE GSM/GPRS IDLE

Reselection Reselection

Mobility and Connection States (1/2)
▪ 2 sets of states for the UE are defined based on the information held in the MME:
▪ EMM: EPS Mobility Management States
EPS: Evolved Packet System
▪ ECM: EPS Connection Management States
▪ EMM:
▪ EMM- DEREGISTERED
▪ MME holds no valid location information about the UE (location unknown)
▪ UE can not be paged
▪ EMM- REGISTERED
▪ UE registers with an MME and establishes a default bearer for application data transfer via attach procedure or TAU
procedure after inter-system HO
▪ UE responds to paging messages
EMM Attach
EMM registered
deregistered Detach

Mobility and Connection States (2/2)
▪ ECM:
▪ UE and MME enter ECM-CONNECTED state when the signaling connection is established between UE and
MME
▪ UE and E-UTRAN enter RRC-CONNECTED state when the signaling connection is established between UE and
the E-UTRAN
RRC connection S1 connection

MME
UE
E-UTRAN MME
RRC connection
establishment
RRC idle RRC connected
RRC connection release
S1 connection establishment
ECM idle ECM connected
S1 connection release
LTE Radio Resource Control (RRC) States
▪RRC Idle state
▪ No signalling connection between UE and
network exists
▪ RRC connection may be released due to the following
▪ UE performs cell reselections
reasons:
▪ Paging needed when the there is data in
▪ UE is inactive for a long time
downlink direction
▪ High mobility: UE makes x handovers within m minutes
▪ RACH procedure used on RRC connection
establishment ▪ Max number of RRC connected UEs reached. Then,
longest inactive UE is released
RRC Connected State
▪ A signalling connection exists between UE and
network
▪ UE location is known in MME with an accuracy of
a cell ID
▪ The mobility of UE is handled by the handover
procedure

LTE connection states
Connection states
E-UTRAN Radio Resource Control EPS Connection Management
RRC Connected ECM Connected
RRC Idle ECM Idle
EPS Mobility Management
EMM Registered
EMM Deregistered

LTE Connection States transitions
Power On
Release due to
Registration (Attach) Inactivity
• Allocate C-RNTI, S_TMSI
• Release RRC connection
• Allocate IP addresses • Release C-RNTI
• Authentication • Configure DRX for paging
• Establish security context
EMM Deregistered EMM Registered EMM Registered
ECM Idle ECM Connected ECM Idle
Deregistration (Detach) New Traffic

Change PLMN
•Establish RRC Connection
• Release C-RNTI, S-TMSI •Allocate C-RNTI
• Release IP addresses
Timeout of Periodic TA
Update
• Release S-TMSI
• Release IP addresses
LTE Tracking Area
▪ Tracking Area Identity = MCC (Mobile Country Code), MNC (Mobile Network Code) and TAC
(Tracking Area Code)
o If the UE is in EMM Registered state, an MME knows the exact Tracking Area to which it belongs
o Paging, if needed, will be done within the full Tracking Area
o When a UE is attached to the network, the MME will know the UE’s position on tracking area level
▪ Tracking areas are allowed to overlap. One cell can belong to multiple tracking areas
▪ UE is told by the network to be in several tracking areas simultaneously
o Gain: when the UE enters a new cell, it checks which tracking areas the new cell is part of. If this TA is on UE
TA list, then no tracking area update is necessary
HSS
TAI1 eNB 1 2
TAI1-2
TAI1 MME
TAI1-2
TAI1
TAI2
TAI2 eNB
TAI2
TAI2
TAI2
Cell Identity TAI2
TAI2
TAI2
TAI3
TAI3 S-eNB 3
TAI3
TAI3 MME
TAI3
TAI3
Information Security Level 2 – Sensitive TAI3
TRIGGERS FOR TAU PROCEDURE
▪ UE detects it has entered a new TA (Tracking Area) that is not in the list of TAIs (Tracking Area Indicators) that
the UE registered with the network;
▪ The periodic TA update timer has expired;
▪ UE was in URA_PCH when it reselects to E-UTRAN;
▪ UE was in GPRS READY state when it reselects to E-UTRAN;
▪ The RRC connection was released with release cause "load re-balancing TAU required";
▪ The RRC layer in the UE informs the UE's NAS layer that an RRC connection failure (in either E-UTRAN or UTRAN)
has occurred;
▪ To update certain UE specific parameters in the network (ex:- when the UE changes the “UE network
capability information” or the “MS network capability information” or the UE specific DRX parameter etc...)*

International Mobile Subscriber Identity (IMSI)
▪ Used in GSM/UMTS/EPS to uniquely identify a subscriber world-wide.
▪ The format is:
▪ MCC: mobile country code
▪ MNC: mobile network code
▪ MSIN: mobile subscriber identification number
▪ MME uses the IMSI to locate the HSS holding the subscribers permanent registration data for
tracking area updates and attaches.
Not more than 15 digits

2 or 3
3 digits digits
MCC MNC MSIN

NMSI
IMSI

Cell Radio Network Temporary Identifier (C-RNTI)
▪ C-RNTI is 16 bits long
▪ Temporary UE identity which is only valid within the serving cell. (To identify an UE uniquely in a
cell)
▪ Used for radio management procedures
E-UTRA C-RNTI allocated

RRC_CONNECTED
E-UTRA
RRC_IDLE C-RNTI released

Globally-unique UE Temporary Identifier (GUTI)
▪ Composition
▪ GUTI = <GUMMEI><M-TMSI>
▪ GUMMEI = <MCC><MNC><MME ID>
▪ MME ID = <MME Group ID><MME Code>
▪ Length
▪ MCC and MNC shall have the same field size as in earlier 3GPP systems.
▪ M-TMSI shall be of 32 bits length.
▪ MME Group ID shall be of 16 bits length.
▪ MME Code shall be of 8 bits length.
▪ M-Temporary Mobile Subscriber Identity
▪ M-TMSI identifies a user between the UE and the MME.
▪ The relationship between M-TMSI and IMSI is known only in the UE and in the MME.
▪ The M-TMSI is unique within MME that allocate it. (Within the MME, the mobile is identified by the M-TMSI)
2 bytes 1 bytes 4 bytes
MCC MNC MME Group ID MME Code M-TMSI
GUTI
S–Temporary Mobile Subscriber Identity (S-TMSI)
▪ S-TMSI is shortened form of GUTI that enable more efficient radio signalling procedures (e.g. paging
and Service Request)
▪ Its main purpose is for user confidentiality.
▪ S-TMSI = <MME Code><M-TMSI>
▪ If S1-flex interface option is used, the eNB must select the right MME for a UE. This is done by using
MME Code portion of S-TMSI
▪ To locally identify a UE in short within a MME group (Unique within a MME Pool)
1 bytes 4 bytes
MME Code M-TMSI
S-TMSI

Network Entity Related Identities
▪ The following identities are used in EPS for identifying a specific network entity:
▪ Globally Unique MME Identity (GUMMEI): used to identify MME globally.
▪ GUMMEI = <MCC><MNC><MME Group Id><MME Code> EPS: Evolved Packet System
▪ E-UTRAN Cell Global Identifier (ECGI): used to identify cells globally.
▪ ECGI = <MCC><MNC><CI>
▪ eNB Identifier (eNB ID): used to identify eNBs within a PLMN.
▪ The eNB ID is contained within the CI of its cells.
▪ Global eNB ID: used to identify eNBs globally.
▪ Global eNB ID = <MCC><MNC><eNB ID>
▪ Tracking Area identity (TAI): used to identify tracking areas.
▪ TAI = <MCC><MNC><TAC>
▪ EPS Bearer ID / E-RAB ID:
▪ The value of the E-RAB ID used at S1 and X2 interfaces to identify an E-RAB allocated to the UE
▪ The same as the EPS Bearer ID used at the Uu interface to identify the associated EPS Bearer.
▪ It may also be used at Non-Access Stratum layer.
▪ Physical-layer Cell Identity (PCI) : used to distinguish between cells/sectors. It similar to Primary Scrambling
Code (PSC) on UTRAN.

Cell Identifier ECI (is not the same as PCI !!!)
LNCEL: eutraCelId
• The E-UTRAN Cell Global Identifier (ECGI) is used to identify cells globally
• The ECGI is constructed from the MCC, MNC and E-UTRAN Cell Identifier (ECI)
• The ECI is used to identify cells within a PLMN
• It has a length of 28 bits and contains the eNodeB Identifier
• LNCEL: eutraCelId Range: 0…..268435455

• Parameter is compiled by the system from following two
individual parameters on binary string level: 20 bit LNBTSId 8 bit LCRId
• LNBTS: lnBtsId Range: 0…1048575
• LNCEL: lcrId Range: 0….255
eutraCelId

eNodeB (LNBTS) and Cell Identity - CM

X2 Handover Procedure
Before handover Handover preparation Radio handover Late path switching
S-GW + P-GW S-GW + P-GW S-GW + P-GW S-GW + P-GW
MME MME MME MME
Target
Source eNB
eNB X2
= Data in radio = S1 signalling

= Signalling in radio = X2 signalling
= GTP tunnel
= GTP signalling
▪ X2 HO as a basic type of a handover within LTE
X2 Handover Preparation
UE Source Target MME GW
1. The source eNB configures the UE
measurement procedures with
MEASUREMENT CONTROL
2. UE is triggered to send MEASUREMENT 1. Measurement control
REPORT to the source eNB. It can be event
2. Measurement report
triggered or periodic
3. Source eNB makes handover decision
3. HO decision
based on UE report + load and service
information 4. HO request
4. The source eNB issues a HANDOVER REQUEST
5. Admission
to the target eNB control
5. Target eNB performs admission control
6. HO request ack.
6. Target eNB sends the HANDOVER REQUEST
ACKNOWLEDGE to the source eNB

X2 Handover Execution
7. Source eNB generates the HANDOVER
UE Source Target MME GW
COMMAND towards UE
Source eNB starts forwarding packets to target
eNB
8. Source eNB sends status information to 7. HO command
target eNB Forward
packets to
9. UE performs the final synchronisation to target
target eNB and accesses the cell via 8. Status transfer
RACH procedure
Buffer packets
DL pre-synchronisation is obtained during cell from source
identification and measurements
9. Synchronization
10.Target eNB gives the uplink allocation
and timing advance information 10. UL allocation and timing advance
11.UE sends HANDOVER CONFIRM to target
11. Handover confirm
eNB
Target eNB can begin to send data to UE
X2 Handover Completion
12.Target eNB sends a PATH SWITCH message to UE Source Target MME GW
MME to inform that the UE has changed cell
13.MME sends a USER PLANE UPDATE REQUEST message
to Serving Gateway 12. Path switch request
14.Serving Gateway switches the downlink data
13. User plane update request
path to the target side
15.Serving Gateway sends a USER PLANE UPDATE 14. Switch
RESPONSE message to MME downlink
path
16.MME confirms the PATH SWITCH message with
the PATH SWITCH ACK message 15. User plane update
17.By sending RELEASE RESOURCE the target eNB response
informs success of handover to source eNB and 16. Path switch request ack.
triggers the release of resources 17. Release resources
18.Upon reception of the RELEASE RESOURCE message,
18. Release
the source eNB can release radio and C-plane resources
related resources associated to the UE context
Intra-LTE Inter-eNodeB handover via S1
• Applicable for intra and inter frequency HO and only for

inter-eNB HO
• DL Data forwarding via S1
• Handover in case of
– no X2 interface between eNodeBs, e.g. not operative,
not existing or because blacklisted usage
– eNodeBs connected to different CN elements
• For the UE there is no difference whether the HO is executed via X2 or S1 interface

• HO reasons ‘better cell HO’ (A3) and ‘coverage HO’ (A5) are supported
• MME and/or SGW can be changed during HO (i.e. if source and target eNodeB belong to different
MME/S-GW)

Inter RAT Handover to WCDMA
Phases:
1. Handover initiation:
▪ eNB starts a HO to WCDMA following a received measurement report with
event B2 (A2/A1 activates/deactivates measurements)
▪ Max. 8 cells reported (strongest first) that create the TCL (target cell list)
2. Handover preparation:
▪ Resource allocation on target side (E-RAB parameters mapped into PDP
context)
3. Handover execution:
▪ UE moves into WCDMA cell after receiving ‘MobilityfromEUTRACommand’
message
4. Handover completion:
▪ Release of S1 connection and internal resources after successful HO (no
timers expired)

RRC Connection Release with Redirect
• feature RRC Connection Release with Redirect (LTE423)
• When serving RSRP falls below certain threshold (threshold4) and stays bellow for certain time
(a2TimeToTriggerRedirect) the RRC connection is released and UE redirects to configured E-
UTRA or inter-RAT carrier frequency with highest priority (if several redirection objects defined)
regardless of the signal strength of the target carrier
• UE capabilities are considered when performing redirect

Mapping to QoS requirements
▪ Every bearer must be tied with QoS Class Indicator (QCI) which determines the
QoS parameters
o Applications sharing the same bearer will be affected by the same quality requirements,
thus it is not possible to map very different services (e.g. HTTP with telco) onto the same QCI
o MME creates the default (non-GBR) bearer for every UE attaching a cell
o GBR bearer can be established on UE demand
QCI Guarantee Priority Delay Loss rate Application

1 GBR 2 100ms 1e-2 VoIP
2 GBR 4 150ms 1e-3 Video call
3 GBR 5 300ms 1e-6 Streaming
Real time
4 GBR 3 50ms 1e-3
gaming
5 Non-GBR 1 100ms 1e-6 IMS signaling
Interactive
6 Non-GBR 7 100ms 1e-3
gaming

TCP protocols:
8 Non-GBR 8 300ms 1e-6 Browsing, email,
file download

LTE Data Rate Calculation (1/2)
# OFDM Symbols/Subframe
14 for Normal CP
12 for Extended CP
1. Maximum channel data rate
The maximum channel data rate is calculated taking into account the total number of the
available resource blocks in 1 TTI = 1ms
Max Data Rate = Number of Resource Blocks x 12 subcarriers x (14 symbols/ 1ms) # REs
= Number of Resouce Blocks x (168 symbols/1ms) [symb/ms]
2. Impact of the Channel Bandwidth: 5, 10, 20 MHz
For BW = 5MHz  25 Resource Blocks Symbol Rate

-> Max Data Rate = 25 x (168 symbols/1ms) = 4,2 * Msymbols/s [symb/s] =
BW = 10MHz -> 50 Resource Blocks -> Max Data Rate = 8,4 Msymbols/s # Subcarrier x
BW = 20MHz -> 100 Resource Blocks -> Max Data Rate =16,8 Msymbols/s OFDM Symbol/ms
x 1000
3. Impact of the Modulation: QPSK, 16QAM, 64QAM
For QPSK – 2bits/symbol; 16QAM – 4bits/symbol; 64QAM – 6 bits/symbol
QPSK: Max Data Rate = 16,8 Msymbols/s * 2bits/symbol = 33,6 Mbits/s (bandwith of 20 MHz)
16QAM: Max Data Rate = 16,8 Msymbols/s * 4 bits/symbols = 67,2 Mbits/s
64QAM: Max Data Rate = 16,8 Msymbols/s * 6 bits/symbols = 100,8 Mbits/s = LTE PHY Layer Rate
- CP Overhead
Data Rate Calculation (2/2)
4. Impact of the Channel Coding
In LTE Turbo coding of rate 1/3 will be used. The effective coding rate is dependent on the
Modulation and Coding Scheme selected by the scheduler in the eNodeB.
In practice several coding rates can be obtained. Here it is considered 1/2 and 3/4
1/2 coding rate: Max Data rate = 33,6 Mbits/s * 0,5 = 16,8 Mbits/s - Coding Overhead
3/4 coding rate: Max Data rate = 33,6 Mbits/s * 0,75 = 25,2 Mbits/s (Redundancy)
5. Impact of MIMO = Multiple Input Multiple Output

If spatial diversity it is used (2x2 MIMO) then the data rate will be doubled since the data is sent
in parallel in 2 different streams using 2 different antennas.
2x2 MIMO: Max Data Rate = 25,2 Mbit/s * 2 = 50,4 Mbits/s
6. Impact of physical layer overhead and higher layers overhead
The real data rate of the user will be further reduced if the physical layer overhead is
considered. Also the higher layers may introduce overhead (example IP , PDCP , RLC and MAC
are introducing their own headers. .

Basic Metric Definitions
• LTE Carrier Received Signal Strength Indicator (RSSI)
o Definition: The total received wideband power observed by the UE from all sources, including co-channel
serving and non-serving cells, adjacent channel interference and thermal noise within the bandwidth of the
whole LTE signal
• LTE Reference Signal Received Power (RSRP)

o Definition: The RSRP is determined for a considered cell as the linear average over the power
contributions (Watts) of the resource elements that carry cell specific Reference Signals within the
considered measurement frequency bandwidth
• LTE Reference Signal Received Quality (RSRQ) Definition: RSRQ = N · RSRP / RSSI
o N is the number of Resource Blocks (RBs) of the LTE carrier
o RSSI measurement bandwidth. Since RSRQ exists in only one or a few resource blocks, and RSSI is measured
over the whole width of the LTE signal
• SINR calculation are:

o S: the power of measured usable signals, such as Reference signals (RS) and physical downlink shared
channels (PDSCHs)
o I: the power of measured interference from other cells in the current system
o N: background noise power
o UEs typically use SINR to calculate the CQI (Channel Quality Indicator) they report to the network
o SINR= S/(I+N)
• Power Headroom (PH)

o In dB, is the difference between current UE PUSCH transmit power and the UE’s maximum capable power
output:
o Power Headroom = UE Max Transmission Power - PUSCH Power
Ranges of metrics
Metric Reporting Range
RSRP -44dBm … -140dBm
RSRQ -3dB … -19,5dB
SINR -23dB … +40dB
PH -23dB … +40dB
CQI 0 … 15
Relation between RSRP and downlink throughput based on drive Relation between SINR and downlink throughput based on drive
test data (26MHZ and 20MHz network) test data (26MHZ and 20MHz network)
RSRP vs. throughput SINR vs. throughput
80.0 70
70.0
60
60.0
50
50.0
40
Mbps
Mbps
40.0
30
30.0
20.0 20
10.0 10
0.0 0
-130
-128
-126
-124
-122
-120
-118
-116
-114
-112
-110
-108
-106
-104
-102
-100
-98
-96
-94
-92
-90
-88
-86
-84
-82
-80
-78
-75
-4 -3 -2 -1 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
dBm dB

Very good LTE Conditions
• In a very good LTE call

o RSSI and RSRP will be well above their respective
noise floor
o RSRQ will be -9dB or stronger
o SINR will be +20dB or stronger
o Power headroom will be +10dB or stronger

Signature of LTE Dropped Call in Poor Coverage
• In bad coverage
o RSSI will be around noise floor, -115dB
o RSRP will be around noise floor, -130dBm
o RSRQ will be -12dBm or weaker
o Power headroom will be below 0
o SINR will be below 0

Signature of LTE Downlink Interference
• In downlink interference area

o RSSI will be normal but its strength comes from
the strong included interference
o RSRP will be lower than expected taking under
consideration RSSI
o RSRQ will be lower than normal, well below -9
o Power headroom is not affected by downlink
o SINR will be lower than normal, around 0

Signature of LTE Uplink Interference
• In uplink interference area

o Power headroom will be very low, even 0 or below
0
o RSRP, RSRQ, RSSI and SINR can be good
enough

LTE Received Channel Quality Indication
Required
CQI Modulation Coding rate
SINR
1 QPSK 0.076 -4.46
2 QPSK 0.11 -3.75
3 QPSK 0.18 -2.55
4 QPSK 308/1024 -1.15 • LTE modulation is adapted in real-

5 QPSK 449/1024 1.75
time to match existing RF condition
reported by the UE
6 QPSK 602/1024 3.65
7 16QAM 378/1024 5.2

• The table shows CQI index and their
8 16QAM 490/1024 6.1
relation to coding rate and SINR
9 16QAM 616/1024 7.55
10 64QAM 466/1024 10.85
11 64QAM 567/1024 11.55
12 64QAM 666/1024 12.75
13 64QAM 772/1024 14.55
14 64QAM 873/1024 18.15
15 64QAM 948/1024 19.25

LTE Sceneries

Sceneries
Accessibility
MO Parameter name Modification Normal Aggressive_QDA

▪ When apply?
dlRsBoost objectLocking 1300
LNCEL 1000 ▪ Overshooter cells with no possibilities of
LNCEL
inactivityTimer onLine 10
10 electrical tilt possibility to change.
LNCEL
threshold2Wcdma onLine 24
24 ▪ 700Mhz cells at maximum e-tilt and still
b2Threshold1Utra onLine 23 overshooting the city/urban areas.
LNHOW 23
LNHOW hysB2ThresholdUtra onLine 6 6 ▪ Generally Accessibility impacted due to
RRC compl missing counter
MO Parameter name Modification Normal Moderate_QDA

LNCEL 1177
LNCEL 10
LNCEL 24
b2Threshold1Utra onLine 23
LNHOW 23
LNHOW hysB2ThresholdUtra onLine 6 6
Sceneries
Coverage
Aggresive
MO Parameter name Modification Normal
Coverage ▪ When apply?
LNCEL 1300 ▪ When there are holes coverage into
LNCEL
10 highways, routes, avenues, etc.
LNCEL
28 ▪ Trigger before the measurements & IRAT
b2Threshold1Utra onLine 23 HO.
LNHOW 27
LNHOW hysB2ThresholdUtra onLine 6 4 ▪ Sceneries Not used anymore, due to PSHO
for LTE network was disable. Then only
redirection to 3G still working.
Moderate
Coverage
LNCEL 1300
LNCEL 10
LNCEL 28
b2Threshold1Utra onLine 23
LNHOW 27
LNHOW hysB2ThresholdUtra onLine 6 6
Sceneries
Interference
Aggresive
Coverage ▪ When apply?
LNCEL 700 ▪ Reduce -3dB de Reference signal, when
LNCEL
5 there area interference in the area
LNCEL
24 ▪ Improve the user perception just
b2Threshold1Utra onLine 23 connecting to LTE when the DL power is
LNHOW 23
hysB2ThresholdUtra onLine 6
enough to good LTE service.
LNHOW 6
▪ Scenaries apply for special cases, when
Feature LTE786 is not able (interference not
located into the border of the spectrum)

Sceneries
Capacity For AWS 10Mhz
MO_FL16A MO_FL17A Parameter name Modification Normal_AWS_10Mhz Capacity_AWS_10Mhz Extreme_Capacity_AWS_10Mhz
LNCEL LNCEL actLdPdcch onLine 1 0 0

LNCEL LNCEL iniMcsDl onLine 4 8 8
LNCEL LNCEL iniMcsUl onLine 4 8 8
LNCEL LNCEL maxNumActUE onLine 432 580 880
LNCEL LNCEL prachConfIndex BTS restart needed 3 6 6
LNCEL LNCEL_FDD prachFreqOff onLine 39 38 36
LNCEL LNCEL_FDD inactivityTimer onLine 10 5 5
LNCEL LNCEL_FDD iniPrbsUl onLine 10 5 5
LNCEL MPUCCH_FDD n1PucchAn onLine 36 36 54
MPUCCH MPUCCH_FDD addAUeRrHo onLine 18 20 20
MPUCCH MPUCCH_FDD addAUeTcHo onLine 24 20 20
MPUCCH MPUCCH_FDD addEmergencySessions onLine 48 20 20
MPUCCH MPUCCH_FDD cellSrPeriod objectLocking 2 3 3
MPUCCH MPUCCH_FDD cqiPerNp objectLocking 40 80 80
MPUCCH MPUCCH_FDD maxNumRrc onLine 432 580 880
MPUCCH MPUCCH_FDD maxNumRrcEmergency onLine 480 600 900
MPUCCH MPUCCH_FDD nCqiRb objectLocking 4 6 9
LNBTS LNBTS_FDD actHighRrc BTS restart needed 0 0 1
Sceneries
Capacity For 700Mhz 15Mhz
MO_FL16A MO_FL17A Parameter name Modification Normal_700Mhz_15Mhz Capacity_700_15Mhz Extreme_Capacity_700_15Mhz
LNCEL LNCEL actLdPdcch onLine 1 0 0

LNCEL LNCEL iniMcsDl onLine 4 8 8
LNCEL LNCEL iniMcsUl onLine 4 8 8
LNCEL LNCEL maxNumActUE onLine 432 580 880
LNCEL LNCEL prachConfIndex BTS restart needed 19 22 22
LNCEL LNCEL_FDD prachFreqOff onLine 64 63 61
LNCEL LNCEL_FDD inactivityTimer onLine 10 5 5
LNCEL LNCEL_FDD iniPrbsUl onLine 10 5 5
LNCEL MPUCCH_FDD n1PucchAn onLine 36 36 54
MPUCCH MPUCCH_FDD addAUeRrHo onLine 18 20 20
MPUCCH MPUCCH_FDD addAUeTcHo onLine 24 20 20
MPUCCH MPUCCH_FDD addEmergencySessions onLine 48 20 20
MPUCCH MPUCCH_FDD cellSrPeriod objectLocking 2 3 3
MPUCCH MPUCCH_FDD cqiPerNp objectLocking 40 80 80
MPUCCH MPUCCH_FDD maxNumRrc onLine 432 580 880
MPUCCH MPUCCH_FDD maxNumRrcEmergency onLine 480 600 900
MPUCCH MPUCCH_FDD nCqiRb objectLocking 4 6 9
LNBTS LNBTS_FDD actHighRrc BTS restart needed 0 0 1
705
LTE users TU222L100MB1 TU222
432
Mass Event (Football match, recital, etc) Special parameter

Setting to manage from
432 to 720 users.
Reduction of Bad QDA att
(cell not excluded due to
▪ NQI affecting all actions implemented
solved the situation)
▪ All samples are bad attempts
No failures
▪ Low Accessibility
▪ High number of users temporary and punctual TU222
880 users
880 users
LTE users CF145 LTE users CF201
LTE users
CF145 CF201
Bad attempts for Bad attempts for

NQI (QDA & QDE Bad attempts
NQI (QDA & QDE DL for NQI (QDA
affected) DL affected)
& QDE DL
affected)

LTE Optimization
Cases Examples

LTE Optimization
Coverage Optimization
•Identify Over shooter and Under Propagating sectors.
•Reduce Coverage overlap and create dominate
server.
Coverage Capacity •Low downlink or uplink MSC usage analysis
Optimization Optimization
Capacity Optimization
•Identify High PRB Utilization Cluster
•Identify High users cells/clusters
•Identify High PRACH Utilization Cluster
Carrier Balance Analysis

Top •Maximize Layer Efficiency
Carrier LTE •Balance Traffic and Load between carriers
Balance Offenders •Best Possible Customer Experience
Optimization
Analysis Analysis
Interference Analysis
•Identify External and Internal Interference
•Massive cluster level RF shaping
•Improve Performance and RSRQ
Mobility Optimization
• Identify Ping Pong HO area
Interference Mobility • Perform Parameter tuning to improve HOSR and
Analysis Optimization redirection
• Perform Parameter tuning to improve CSFB
Top Offenders Analysis

• Identify and Optimize Daily top 20 offender sectors

Three times increased the
LTE – Smart Layering - CSFB redirection from 3G to LTE after CS
voice call is released.
▪ New setting for CSFB detection (RU50) Tested, Recommended & RU50 bring new parameter CSFB
implemented all over the network. detection. The usage this detection, allows
to redirect back after CS call release
▪ Reducing the timing of returning to LTE network after CS voice call in when the redirection from LTE to 3G was
3G. Then improving end user perception, reducing timing into 3G done by CSFB with PSHO.
network. CSFBDetection,
0: Disabled
1: Enabled for blind redirection cases only
2: Enabled for all cases
Redirection to LTE after CS call end

All Redirection reasons

AMX Layering Off Load
Technology Mode objetct Parameter Current guideline Proposal
3G Idle HOPL AdjLQrxlevminEUTRA -112 -120 -114
LTE - Offload WCDMA Strategy

3G Idle HOPL AdjLThreshigh 0 4 0
4G Connected LNCEL threshold1 -60 N/A -60
4G Connected LNCEL threshold2a -106 N/A -106
4G Connected LNCEL hysThreshold2a 2 N/A 0
4G Connected LNCEL threshold2Wcdma -112 -113 -114
4G Connected LNCEL hysThreshold2Wcdma 0 2 0
4G Connected LNHOW b2Threshold1Utra -116 -113 -115
4G Connected LNHOW hysB2ThresholdUtra 2 3 3
4G Connected LNHOW b2Threshold2UtraRscp -100 -99 -99
4G Connected LNHOW offsetFreqUtra 0 0 0
▪ Move any LTE capable UE to LTE. Performing CS calls in 3G then pushing back to LTE as
soon as possible
▪ Recommended & implemented:
▪ Mobility Parameters (Reselection/IRAT), better setting between both networks (WCDAM / LTE)
▪ Smart LTE Layering better parameters setting (based on drive test & trials)
▪ Results Network level

▪ Huge increase (~36% more) using Smart LTE Layering redirections after parameter changed showing that
the users return to LTE faster than before
▪ Increase in PDCP SDU DL volume
▪ Increase in number of connected UEs
▪ Increase in Data Radio Bearer Attempts
▪ For 3G users/volume/load, it was not identify clear view of impact, basically estimated due to low LTE UE in
the network. But from LTE point of view it was increased the volume/users/attempts as described.
Huge increase (~36% more) using

Smart LTE Layering redirections
LTE - RACH PERFORMANCE Periodic Review: detected & RSI
solved all over the network.
RSI Conflict Resolution
RSIs changed
RSIs changed
RSIs changed
• Big improvement in KPI RACH Setup Completion Success Rate (LTE_5569a) -> Currently close to
100% on the analyzed cells.
rootSeqIndex

LTE – 3G Femto - Interworking Solutions
▪ Different test cases were done with the objective to verify the main Interworking
functionalities between LTE macro cell and 3G femto cells.
T.C # Functionality Source -> Target Status
1 IRAT Cell Reselection to UTRAN. 4G -> 3G Femto Cell ok

2 Cs Fallback with redirection: MOC & MTC. 4G -> 3G Femto Cell Tested & solutions
3 Inter System HO to UTRAN. 4G -> 3G Femto Cell Tested & solutions
4 IRAT Cell Reselection to E-UTRAN. 3G Femto Cell -> 4G Tested & solutions
▪ Recommendations & solutions:

▪ Change UTRAN Carrier priorization order for IRAT reselection and redirection in LTE cells with overlapping coverage with 3G
Femto Cells -> The highest priority for FEMTO UTRA Carrier frequency
▪ SIB19 should be enabled on 3G Femto Cell (siB19Enable = True – FEMTO parameter) to allow to camp on LTE in
acceptable radio conditions -> UE Retention in the highest technology layer
▪ Parameters and configurations for 3G Femto Cells to enable HO coming from LTE. Note that psHOFromLteEnabled (Femto
parameter) -> Improving User perception of service quality.
▪ Other functionality on 3G Femto Cells such CS Fallback with fast return to LTE should be investigated to speed up the back
to LTE -> UE Retention in the highest technology layer
Periodic Review: detected & solved
LTE – GSM Mobility configuration all over the network.
• 2G → LTE functionalities
• LTE System Information (BSS 21353) (RG20)
• Idle mode mobility to LTE
• Inter-System NCCR for LTE (RG301737) (RG30) Not recommended due to not well
performing Packet Cell Change Order
• GPRS Packet transfer mode mobility to LTE RRC-Idle (PCCO) message, as NCCR to 3G experience.
• Fast Return to LTE (RG301854) (RG30) Not recommended for now,

before LTE launch, due to risk of
• Redirection, direct camping on LTE cell immediately after the CS call ends. moving Mobiles w/LTE
capabilities w/o subscription
GSM Network 3G Network 4G Network
BSC does not know whether it is CSFB call or not, CSFB
Re-selection/ ISHO Re-selection / PS is seen as normal call setup from BSC point of view.
HO/ Smart LTE (Currently not enabled LTE CSFB to GSM) For normal
call setup, after call ends will be redirected to LTE with
layering the feature enabled.
LTE capable UE
Current situation
GSM Network 4G Network • Directly
• Faster
Recommended &
Re-selection
• without transit into 3G network implemented.
LTE capable UE
Recommended

LTE – Interference method detection (1/3)
Summary Periodic Review: detected & reported for
hunting all over the network.
▪ LTE interference detection method definition & create a delivery Avg RSSI for PUSCH > -95 dBm
report for interference hunting Avg SINR for PUSCH < 5 dB
▪ Very important issue for LTE because is affecting/impacting

eNBs:
▪ Degradation for NQI (QDA/QDR/QDE), all attempts are bad.
▪ Initial Accessibility Interference Good Cell
RRC access (radio fails)

All attempts are BAD, then affect QDA
▪
▪ Drop Rate (radio fails) Better QDA, just few hours below 99%
▪ Throughput (cell/user)
▪ Intra eNB HandOver
▪ Inter eNB HandOver through X2 interface

Example of detected areas
Periodic Review: detected & reported
for hunting all over the network.
▪ Interference method definition

▪ Detection of cells.
▪ These cells are in Area with Low UL
Throughput
Avg RSSI for PUSCH > -95 dBm
Avg SINR for PUSCH < 5 dB

Example of feature activation • Feature LTE786 activated to improve end
user performance
• Not recovered NQI but Amdocs solution
provide service to end user.
Flexible UL BW LTE786
• User LTE increased
• Apply for every cell interfered.
Still having bad QDA
Interference
LNCEL:
blankedPucch:0 -> 40.
redBwRpaEnUl: True.
prachFreqOff:25.
MPUCCH:
nCqiRb: 44
LTE – Paraguay & ARG 700Mhz parameters issues detection
& solutions Periodic Review: detected & solved
configuration all over the network.
▪ Paraguay in AWS and Argentina in 700 MHz were deployed with a BandWidth of 15 MHz and the
prachFreqOffset value has setting as equal as for 10 MHz.
▪ To maximize the PUSCH area and consequently improve uplink performance in terms of user/cell throughput
& volume (peak & average), the prachFreqOffset value should be changed from 39 to 64 or 5 for all cells
with LTE BandWidth = 15 MHz ( Paraguay in AWS and Argentina in 700 MHz)

Retention into LTE (1)
RSRQ redirection disabling Implemented Nov2017
RSRQ cell drops below value of (threshold4Rsrq – hysThreshold4Rsrq)
& remains below threshold for a2TimeToTriggerRedirectRsrq
▪ Motivation: as the Retention into LTE was one key problem into LTE, then to retain more traffic into
LTE it was found that disabling RSRQ (Quality) redirection to 3G
▪ Then after this change only redirection due to RSRP will be trigger
▪ Improving PSRET LTE, not impacting QDR
▪ Less ping pong between both networks
Operator Amdocs
MO Parameter
Value proposal eNodeB
device
LNCEL hysThreshold4Rsrq 0 15dB mobile
user
03Nov Started rollout Parameter rollout

Pushing traffic to LTE
Measurement Based LTE Layering – RSRQ Implemented Nov2017
▪ Motivation: As LTE network has better performance for data services, then pushing the
user faster from 3G to LTE will improve the end user performance into Claro user.
▪ Then moving the threshold values of more relax quality during the Measurement Based
LTE Layering
▪ Increasing around 15% of redirection from 3G to LTE
Operator
Increasing around 130k redirection at daily level from 3G to LTE & MO Parameter
Value
Amdocs proposal
reducing the LTE not found redirection during the Measurements HOPL AdjLminRSRQLevel 15dB 19.5dB
Measurement Based Layering

RSRQ <19.5dB

Only redirections allowed from LTE to 3G (1/2)
LTE IRAT PSHO disabling Implemented Dic2017
▪ Motivation: improve the LTE PS RETENTION, also MLL LTE Periodic Trigger Timer is not
working when users are coming with PSHO to 3G network (based on the PRFILE 002:1916
RN60_MAINT_41)
▪ After this change the mobility from LTE to 3G will be only due to redirections RSRP
w/measurement & CSFB w/measurements
After change keep the same values of mobility CSFB with 100% After change keep the same values of mobility with 100%
redirections & not anymore CSFB PS IRAT HO. redirections and not anymore PS IRAT HO.

Only redirections allowed from LTE to 3G (2/2)
LTE IRAT PSHO disabling Implemented Dic2017
▪ PSRET LTE improved & Increased 15 % of redirection from 3G to LTE.

Amdocs
MO Parameter Operator Value
proposal
LNBTS preventPsHOtoWcdma 0 1
LNBTS actCsfbPsHoToUtra 1 0
LNHOW b2Threshold1Utra 25 (-115dBm) 23 (-117dBm)

LTE PS RETENTION
LNHOW hysB2ThresholdUtra 6 (3dB) 6 (3dB)
LNCEL threshold2Wcdma 26 (-114dNm) 24 (-116dBm)
LNCEL threshold2a 34 (-106dBm) 34 (-106dBm)
Redirection from 3G to LTE

Link Adaptation & ATB (Adaptive Transmission Bandwidth)
Adapt the parameter setting Implemented Nov2017
▪ Motivation: improve the efficiency of the resource usage. Then as the network is showing the traffic profile, it is
important to adapt the parameter setting for the link Adaptation & Adaptive Transmission Bandwidth (ATB).
▪ At call setup the maximum number of PRB’s that can be allocated to a single UE shall be limited to reduce
the PRBs usage for the initial moments (iniPrbsUl). Also defining the lowest possible amount of allocable PRBs
(eUlLaLowPrbThr).
▪ Then during the link adaptation functionality defining how many MCS indexes (eUlLaDeltaMcs) above the
minimal MCS index
Operator Amdocs
MO Parameter
Value proposal
LNCEL eUlLaDeltaMcs 4 6
LNCEL eUlLaLowPrbThr 5 1
LNCEL iniPrbsUl 10 5
UL Efficiency improved

Summary - Pushing traffic to LTE (2)
Measurement Based LTE Layering – RSRP
▪ Motivation: As LTE network has better performance for data services, then pushing the
user faster from 3G to LTE will improve the end user performance into Claro user.
▪ Then moving the threshold values to more relax signal level during the Measurement
Based LTE Layering will allow to push users to LTE network.
Increasing around ~40% of redirection from 3G to LTE

& returning to 3G increased around ~10% of
redirection from LTE to 3G
Note: average for the three areas tested (RMEN5, RTUC4, RTORC)
Measurement Based Layering

RSRP <19.5dB
Operator
MO Parameter Amdocs proposal
Value
HOPL AdjLMinRSRPLevel -114dBm -116dBm

Results - Pushing traffic to LTE (2)
RTORC
▪ Results of PoC done into Tucuman/Mendoza/

AMBA areas (RTUC4, RMEN5, RTORC)
▪ Redirection from LTE to 3G increased around
40%
RTUC4

RTUC4
Results - Pushing traffic to LTE (2)

▪ Redirection from LTE to 3G increase around 10%

▪ The users into LTE increased around 2% RTORC
▪ Not impacted QDA/QDR for LTE & WCDMA

RMEN5
RTORC
RMEN5
RMEN5 RTORC

Retention into LTE (2) Trial Feb 2018
RSRP redirection stronger
▪ Motivation: as the Retention into LTE was one key problem into LTE, then to retain more traffic into LTE it was
found that making the values of RSRP (Coverage) lower for redirection to 3G. ONLY apply for CORE cells.
▪ Improving PSRET LTE, not impacting QDR
▪ 80% reduction of redirection RSRP to 3G
▪ Improved HSDPA/HSUPA Accessibility
▪ Improved ~20% BAD HS QDA ATT reduction
▪ Reduction of HSPA users/improved throughput
eNodeB
device
Operator mobile
MO Parameter Amdocs proposal user
Value
LNCEL Threshold4 -120dBm -125dBm

Retention into LTE (2) Trial Feb 2018
RSRP redirection stronger
eNodeB
device
▪ 3G improved mobile
user

Idle Mode Mobility Load Balancing
Prevent RRC attempts overload in 3G F3 carrier
▪ Motivation: prevent RRC attempts overload in F3 carrier due to CSFB.

▪ LTE487 Idle mode mobility load balancing (IMMLB) statistically distributes UEs sent with
RRC connection release message towards different frequency layers
▪ By enabling IMMLB, RRC attempts in 3G carriers are better balanced.
RRC Attempts example
Operator Amdocs
MO Parameter
Value proposal
REDRT redirFreqUtra UARFCN UARFCN
REDRT csFallBPrio 0 1
REDRT redirectPrio 0 1
LNBTS actIdleLB 0 1

VoIP in LTE

Introduction CS: Circuit Switched
VoLTE: Voice over LTE
▪ What is VoLTE?
• LTE networks are packet- switched. They do not include the traditional 2G/3G
voice services (CS).
• VoLTE (Voice over LTE) is the solution to provide the Voice (VoIP) and SMS
service capability on LTE networks. Requirements:
- Real time traffic
- Quality of Service
- Interoperability to existing CS voice network
IP Multimedia Subsystem (IMS) enables integrated voice, data and multi-

media services interworking between different access networks.
- IMS is based on SIP call control for creating, modifying, and terminating
sessions
Commercial LTE Voice Solutions

SVLTE Definition
•
In the simultaneous voice and LTE (SVLTE) solution, dual-mode mobile phones work on the
LTE network and the CS network simultaneously. The LTE network provides data services,
while
• the CS network provides voice services.
Advantage: SVLTE is a solution for mobile phones without requirements for the network.
Disadvantage:
• The cost and power consumption of dual-mode mobile phones are high.
MSC server
MME
CS EPC
Voice service Data service
2G/3G LTE

OTT Definition
• Over-the-top (OTT) is a solution that uses APPs, such as the Skype, to provide
voice services for LTE subscribers.
• Advantage:
□ Only the OTT server needs to be deployed to the live network and slight change is
required. The OTT can enhance user experience by offering rich multimedia services.
• Disadvantages:
□ The OTT solution is not carrier-class-based and has low reliability.
□ The OTT solution cannot provide E2E QoS guarantee.

□ The OTT solution is hard to provide common services, such as emergency calls and
interception, and services that are used only by regulatory bodies.
□ Roaming and interconnection are hard to be implemented due to lack of standards.

Comparison Among CSFB, SVLTE, VoLTE and OTT
Deployment
Solution Feature Advantage Disadvantage Suggestion
The IMS and LTE

networks provide voice Rich
VoLTE services. The handover The IMS network Large-scale LTE
multimedia
between the LTE
services. needs to be coverage
network and 2G/3G
network is supported. HD voice/video. deployed.
E2E QoS
Voice calls are
Voice services are Slight change not reliable. -
OTT implemented by APPs is required on Roaming and
of OTT carriers. live networks.
interworking are
hard to be
implemented.
UEs attach to the LTE Slight change
The call delay is long. Initial phase of the
network. When a UE is required on
CSFB User experience is LTE network
initiates or receives a live networks.
(transition
call, the UE falls back to New NEs do not need affected.
solution)
the CS network. to be deployed.
Terminals attach to both Costs of mobile
Initial phase of the
the CS and LTE phones are high.
The live network does LTE network
SVLTE networks. The CS Advantages of the
(transition solution)
network provides voice not need to be LTE network cannot
127 services. be used.
adjusted.
Voice support in LTE
CSFB
(CS Fallback)
Voice in LTE
SRVCC
(Single Radio Voice Call Continuity)
(Voice over LTE)

CS Fallback
▪ Circuit Switched Fall Back (CSFB) is a technology whereby voice and SMS services are
delivered to LTE devices through the use of GSM or another circuit-switched network.
▪ CS Fallback is performed during the call setup as:
o Inter-RAT redirection from LTE to UTRAN
o Inter-RAT handover from LTE to UTRAN
o Inter-RAT cell change order from LTE to GERAN (NACC)
o The EPC needs to support CS inter-working because the MME indicates the eNB to perform
HO/NACC
▪ Benefits
o Existing 2G/3G infrastructure can be reused in initial LTE deployments
o CSFB feature can be further utilized in roaming scenarios
Switching is based on priorities of layers configured by an

operator:
• GSM layer = set of BCCH frequencies,
• UMTS layer = carrier frequency.
CSFB Mobile Terminating Call via redirect to UMTS
UE eNB RNC MME SGW MSC
SGs Paging Request
Paging (Idle) // CS Service Notification (Active) Service Request (Active)
Extended Service Request NAS : MT CS Fallback
Service Request (Idle) S1AP : CS Fallback Indicator

Initial Context Setup Request (Idle)
Initial Context Setup Response (Idle)

UE Context Modification Request (Active) S1AP : CS Fallback Indicator
UE Context Modification Response (Active)
RRC Connection Release RRC : Redirect Information

UE Context Release Request
Release Access Bearer Request

UE Context Release Command
Release Access Bearer Response
UE Context Release Complete
4G -> 3G
RRC Connection Setup
Location updating or Paging Response

Layer 3 Message CSFB (MT Call) LTE–UMTS

Introduction to SRVCC
3GPP Mobility Management events
High serving cell RSRP
Event Triggers
A1 Serving becomes better than threshold A2 measurements
active
A2 Serving becomes worse than threshold
Start of 3G
A3 Neighbour becomes offset better than
measurements
serving A2 event
A4 Neighbour becomes better than threshold
B2 measurements active
A5 Serving becomes worse than threshold1 and
for the provided
neighbour becomes better than threshold2
measurement objects
B1 Inter RAT neighbour becomes better than
threshold Start of handover
B2 Serving becomes worse than threshold1 and B2 event
inter RAT neighbour becomes better than Low serving cell RSRP
threshold2
* Measurement gaps scheduled if needed – depending on the UE capability, so acc. to IE interRAT-NeedForGaps stored in UE-
EUTRA Capability
Single Radio Voice Call Continuity
▪ SRVCC provides voice service continuity when changing from an LTE cell to a
WCDMA/GSM cell
o The eNB will trigger required inter-RAT measurements only if the UE has an EPS bearer with
QCI=1 (i.e. GBR for Conversational Voice) and both the MME and the UE are SRVCC
capable
o Non-voice bearers handling
▪ SRVCC to GERAN: PSHO is not supported, non-voice bearers will not be handed over
▪ SRVCC to UTRAN: all non-voice bearers will be handed over to PS domain

Volte Analysis example
Layer 3 Analysis E2E- Tektronix Analysis

Thank you

LTE Workshop v3 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

LTE Workshop v3 PDF

Caricato da

Copyright:

Formati disponibili

LTE-VoLTE Workshop

AUP - Amdocs LTE team

Information Security Level 2 – Sensitive

Multiple Access WCDMA OFDMA/ SC-FDMA

Frequency Re-Use Re-use of 1 Re-use of 1

Yes for DCH and HSUPA

Fast Power Control Yes for DCH and HSUPA

QPSK for DCH

QPSK for DCH

Adaptive Modulation Yes for HSDPA and HSUPA Yes

Information Security Level 2 – Sensitive

Downlink MIMO 2x2 for HSDPA 2x2 and 4x4

Peak Uplink 85Mbps (20MHz channel, 64AQM, Coding Rate 1,

Peak Downlink 325Mbps (20MHz channel, 64QAM, 4x4 MIMO, Coding

Neighbor planning Yes No if ANR capability is supported

Information Security Level 2 – Sensitive

Information Security Level 2 – Sensitive

Control plane and user plane

Information Security Level 2 – Sensitive

Information Security Level 2 – Sensitive

Information Security Level 2 – Sensitive

S11 interface – allows signaling information for mobility MME

Information Security Level 2 – Sensitive

FFT size and sampling frequency depends on the

Information Security Level 2 – Sensitive

Frequency (f/fs) Frequency (f/fs)

Information Security Level 2 – Sensitive

Delay spread > Tg 1

• In all major implementations of the OFDMA technology (LTE,

• A receiver typically uses the high correlation between the CP

Cyclic Part of symbol

Sub-frame – 1ms Slot– 0,5ms

0 1 2 3 4 5 6 The number of Symbols per Slot (0.5ms)

Time (radio frames)

Information Security Level 2 – Sensitive

Short cyclic prefix: Ts:

Information Security Level 2 – Sensitive

A higher Bandwidth is better because a higher

A compromise needed between:

Transmission Bandwidth Configuration [RB]

Active Resource Blocks DC carrier (downlink only)

This parameter indicates what is the sampling frequency:

The sampling rate is a multiple of the chip rate

Bandwidth 1.4 MH 3 MHz 5 MHz 10 MHz 15 MHz 20 MHz

Subcarrier Fixed to 15 kHz (7.5kHz defined for MBMS)

Symbol Tsymbol = 1/Δf = 1/15kHz = 66.67μs

Sampling rate, 1.92 3.84 7.68 15.36 23.04 30.72

Data 72 180 300 600 900 1200

NIFFT 128 320 512 1024 1536 2048

Symbols/slot Normal CP=7; extended CP=6

CP length Normal CP=4.69/5.12μsec., Extended CP= 16.67μsec

Information Security Level 2 – Sensitive

Control Channel Traffic Channel

• signaling info (RRC); • user plane data (IP)

BCCH DCCH DTCH MTCH

Downlink PhyCH Downlink Signal Uplink Signals Uplink PhyCH

PBCH DL reference signal Demodulation ref. signal PUSCH

• phys. DL shared channel; • phys. UL control channel;

Information Security Level 2 – Sensitive

Resource Elements allocated to Reference Signals cannot be

Information Security Level 2 – Sensitive

Pre-Coding SISO SU-MIMO

2-way TXDiv Transmit Diversity using 2 TM2