LTE Internal

Content
• Network Architecture
• Basic Functionalities In LTE
• Call Flow
• KPI Analysis With Counter/Parameters.*
– Accessibility
– Integrity
– Retainability
– Mobility
 Network Architecture
• The high-level network architecture of LTE is
comprised of following three main components:
– The User Equipment (UE).
– The Evolved UMTS Terrestrial Radio Access Network
(E-UTRAN).
– The Evolved Packet Core (EPC).
• The E-UTRAN handles the radio communications
between the mobile and the evolved packet core
and just has one component, the evolved base
stations, called eNodeB or eNB.
• Each eNB is a base station that controls the
mobiles in one or more cells. The base station that is
communicating with a mobile is known as its serving
eNB.
 Network Architecture
• EPC
– The Home Subscriber Server (HSS) component has been carried
forward from UMTS and GSM and is a central database that
contains information about all the network operator's subscribers.
– The Packet Data Network (PDN) Gateway (P-GW)
communicates with the outside world ie. packet data networks
PDN, using SGi interface. Each packet data network is identified by
an access point name (APN). The PDN gateway has the same role
as the GPRS support node (GGSN) and the serving GPRS support
node (SGSN) with UMTS and GSM.
– The serving gateway (S-GW) acts as a router, and forwards data
between the base station and the PDN gateway.
– The mobility management entity (MME) controls the high-level
operation of the mobile by means of signalling messages and
Home Subscriber Server (HSS).
– The Policy Control and Charging Rules Function (PCRF) is a
component which is not shown in the above diagram but it is
responsible for policy control decision-making, as well as for
controlling the flow-based charging functionalities in the Policy
Control Enforcement Function (PCEF), which resides in the P-GW
Network Architecture
Functional split between the E-UTRAN and
2G/3G Versus LTE the EPC

2G/3G LTE
GERAN and
E-UTRAN
UTRAN
SGSN/PDSN-
S-GW
FA
GGSN/PDSN
PDN-GW
-HA
HLR/AAA HSS
VLR MME
SS7-
MAP/ANSI- Diameter
41/RADIUS
DiameterGT
Pc-v0 and GTPc-v2
v1
 Basic Functionalities In LTE

• Basic Parameters

• Numbering & Addressing

• Radio Protocol Architecture

• Protocol Stack Layers

• Communication Channels

• Radio Interface
 Basic Parameters
Parameters Description

Frequency range UMTS FDD bands and TDD bands defined in 36.101(v860) Table 5.5.1, given below

Duplexing FDD, TDD, half-duplex FDD

Channel coding Turbo code
Mobility 350 km/h

•1.4
•3
•5
Channel Bandwidth (MHz)
•10
•15
•20

•6
•15
Transmission Bandwidth Configuration NRB : (1 resource block = •25
180kHz in 1ms TTI ) •50
•75
•100

UL: QPSK, 16QAM, 64QAM(optional)

Modulation Schemes
DL: QPSK, 16QAM, 64QAM

UL: SC-FDMA (Single Carrier Frequency Division Multiple Access) supports 50Mbps+ (20MHz spectrum)
Multiple Access Schemes
DL: OFDM (Orthogonal Frequency Division Multiple Access) supports 100Mbps+ (20MHz spectrum)

UL: Multi-user collaborative MIMO

Multi-Antenna Technology
DL: TxAA, spatial multiplexing, CDD ,max 4x4 array

UL: 75Mbps(20MHz bandwidth)

Peak data rate in LTE DL: 150Mbps(UE Category 4, 2x2 MIMO, 20MHz bandwidth)
DL: 300Mbps(UE category 5, 4x4 MIMO, 20MHz bandwidth)
MIMO UL: 1 x 2, 1 x 4
(Multiple Input Multiple Output) DL: 2 x 2, 4 x 2, 4 x 4
Coverage 5 - 100km with slight degradation after 30km
QoS E2E QOS allowing prioritization of different class of service
Latency End-user latency < 10mS
 Numbering & Addressing
• An LTE network area is divided into
three different types of geographical
areas explained below:
– The MME pool areas

– The S-GW service areas

– The Tracking areas

• The Network IDs

• MME IDs
• Each MME has three main identities. An MME code
(MMEC) uniquely identifies the MME within all the pool
areas. A group of MMEs is assigned an MME Group
Identity (MMEGI) which works along with MMEC to
make MME identifier (MMEI). A MMEI uniquely identifies
the MME within a particular network.

• Tracking Area IDs

 Radio Protocol Architecture
• The radio protocol architecture for LTE can be
separated into control plane architecture and
user plane architecture.

• User Plane
– PDCP (Packet Data Convergence Protocol)
– RLC (radio Link Control)
– Medium Access Control (MAC)

• Control Plane
– The control plane includes additionally the Radio
Resource Control layer (RRC) which is responsible for
configuring the lower layers
 Protocol Stack Layers
• Physical Layer (Layer 1)
– Physical Layer carries all information from the MAC transport
channels over the air interface. Takes care of the link adaptation
(AMC), power control, cell search (for initial synchronization and
handover purposes) and other measurements (inside the LTE
system and between systems) for the RRC layer.

• Medium Access Layer (MAC)

– MAC layer is responsible for Mapping between logical channels
and transport channels, Multiplexing of MAC SDUs from one or
different logical channels onto transport blocks (TB) to be
delivered to the physical layer on transport channels, de
multiplexing of MAC SDUs from one or different logical channels
from transport blocks (TB) delivered from the physical layer on
transport channels, Scheduling information reporting
Communication Channels
• Logical Channels : Define whattype of
information is transmitted over the air,
e.g. traffic channels, control
channels, system broadcast, etc.
Data and signaling messages are
carried on logical channels between
the RLC and MAC protocols.

• Transport Channels : Define howis

something transmitted over the air,
e.g. what are encoding, interleaving
options used to transmit data. Data
and signaling messages are carried
on transport channels between the
MAC and the physical layer.

• Physical Channels : Define whereis

something transmitted over the air,
e.g. first N symbols in the DL frame.
Data and signaling messages are
carried on physical channels
between the different levels of the
physical layer.
RADIO INTERFACE
• Downlink and Uplink Transmission Technique

• Flexible Spectrum Usage

•
HARQ

Radio Interface and Channel Structure eNB

?
Downlink Transmission Technique
• The LTE radio interface is based on OFDM
(Orthogonal Frequency Division Multiplex) and
OFDMA (Orthogonal Frequency Division Multiple
OFDM/OFDMA
Access) in the downlink (DL)
eNB
• OFDM has very good performance in highly time
dispersive radio environments (i.e. many delayed
and strong multipath reflections).

• That is because the data stream is distributed over

many subcarriers.

Datastream
Downlink Transmission Technique
• The users in DL are separated with
OFDMA, which means that each
user has its own time- and frequency User #1 scheduled User #2 scheduled
resources, so called scheduling
blocks.

• Dynamic channel dependent User #3

scheduling allocates a number of
these time- and frequency resources scheduled
to different users at different times. In
that way it is possible to schedule
users on the frequencues they
experience the best quality on
during a certain time intervall.

• The LTE radio transmissions are based

on a very short TTI (Transmission Time
Interval) of 1ms, which speeds up the
operation of all functions. The short
TTI also reduces the radio interface frequency
latency
Uplink transmission technique
• The uplink transmission technique, SC-
FDMA, is realized in a similar manner as
for the downlink and is also called DFTS-
OFDM (Discrete Fourier Transform Spread
– OFDM).

• The time domain structure is also similar

in uplink and downlink. One of the
reasons for the choice of SC-FDMA for
the uplink is that it enables the UE to be
made more power efficient and
manufactured at a lower cost since the
Peak to Average Power Ratio (PAPR) is
lower than for OFDMA.

• In contrary to WCDMA, the uplink

transmissions in LTE are, thanks to the SC-
FDMA solution, perfect separated within
a cell (intra-cell orthogonality). This leads
to a less extensive power control
operation.
 Bandwidth flexibility
• The support for operation in six
different bandwidths, 1.4, 3, 5, 10,
15 and 20 MHz, plays an important
role of the spectrum flexibility part
in the standardization of the radio
interface.

• The maximum number of Resource

Blocks that can be allocated is 100.
The 10 remaining RBs (since 20 MHz
corresponds to 110 RBs) are used 1.4 3 5 10 15 20 MHz
as guard bands.

1.4 MHz
110 RB (20 MHz)
Time-domain structure
• Both FDD (Frequency Division Duplex) and TDD (Time Division Duplex)
is supported, which opens up for deployment in both paired and
unpaired spectrum.

• In FDD, different frequency bands are used for UL and DL. In TDD the
UL and DL transmissions are separated in time.

• There are pros and cons with both methods. TDD has some more
overhead and latency, due to the frequent switching in time.

• On the other hand, the TDD mode enables radio channel

reciprocity, which means that uplink measurements can be used for
downlink transmissions, and vice versa.

• The TDD mode is also simpler to deploy in areas with limited available
spectrum since it can utilize unpaired frequency bands.

• A half duplex FDD mode (HD-FDD) is also defined, where the UE does
not have to transmit at the same time as it receives. Therefore, more
cost effective UEs can be manufactured since a duplex filter is not
needed.
 The HARQ Principle
• The Hybrid ARQ (HARQ) protocol is
very similar to the solution adopted for Demultiplexed and forwarded to RLC
HSDPA, i.e., the protocol uses multiple
stop-and-wait hybrid ARQ processes.

• In this case, we have a received

datastream that is processed by
HARQ and demultiplexed into logical
channels and forwarded to the RLC Receiver process
Receiver process Receiver process
Receiver process
protocol for re-ordering. The HARQ process
process
HARQ process process

motivation for the HARQ protocol is to

allow continuous transmission, which
cannot be achieved with a single
stop-and-wait scheme, while at the 0 1 2 3 4 5 6 7 8 9
same time having some of the
simplicity of a stop-and-wait protocol.
Datastream
• HARQ works with several processes at
the same time. In this example only 4
processes are shown. For FDD it will be
up to 8 parallel processes but for TDD
it will differ depending on the
configuration.
CALL FLOW
Add a Slide Title - 2
Add a Slide Title - 3
Add a Slide Title - 4
Add a Slide Title - 5