LTE Optimization

Day 1
 Course Contents
Day 1:
• LTE Introduction
• SAE and Site solution

Day 2:
• Interfaces, Bearers and Protocols
• LTE Key Technologies
1. OFDMA
2. SCFDAM
3. HARQ
4. AMC
5. MIMO

Day 3:
• LTE Air Interface overview
• LTE Frame Structure
• LTE Frequency Structure

232/
 Course Contents
Day 4:
• DL Channels

Day 5:
• UL Channels

Day 6:
• Idle Mode Behavior
1. PLMN Selection
2. MIB & SIBs
3. Cell Selection
4. Cell Reselection
5. TAU
6. Paging
• Attach
• CSFB
• RLS

332/
 Course Contents
Day 7:
• Handover
• Power Control
• Scheduler

Day 8:
• LTE Voice Solutions
• CSFB troubleshooting
• VoLTE Solution
• IMS Network Architecture

Day 9:
• IMS Signaling and Procedures
• VoLTE Network Deployment

Day 10:
• VoLTE Signaling analysis
• VoLTE Features
432/
Day Contents
• LTE Introduction
• SAE and Site solution

532/
 Why LTE ?
Need for PS optimized system
Evolve UMTS towards packet only system
Need for higher data rates
Can be achieved with HSDPA/HSUPA and/or new air interface defined by 3GPP
LTE
Less processor load cost
• Less number of transitions between different states will lead definitely to less
processor load
Need for high quality of services
Use of licensed frequencies to guarantee quality of services
Always-on experience (reduce control plane latency significantly)
Reduce round trip delay (→ 3GPP LTE)
Need for cheaper infrastructure
Simplify architecture, reduce number

632/
LTE Design Aspects
LTE Spectrum Efficiency is Adaptive Modulation and Coding

• 5 bits/s/HZ for DL • DL Modulations: QPSK, 16-QAM and 64-QAM modulation

• 2.5bits/s/HZ for UL • UL Modulations: QPSK and 16-QAM
• Turbo code
Duplexing Methods

• FDD
UL and DL can reach the peak traffic simultaneously
• TDD
UL and DL can not reach the peak traffic
simultaneously

Accessing techniques

• OFDMA for the DL

• SC-FDMA for the UL
732/
 LTE Design Aspects
Control Plane Latency

The delay of changing the mobile mode from the active to non active and vice versa
• If the terminal was in the idle mode it needs 100msec
• If the terminal was in the dormant it needs 50msec

User Plane Latency

Time the terminal takes to transmit small packets to the RAN and Vice versa is 5 msec
Active Mode Capacity

At 5MHZ BW the Cell can support 200 users simultaneously. At BW more than 5 MHZ the Cell can support up to
600 Simultaneously terminal.

IDLE Mode Capacity

Can support more than 400 Users at the same time

832/
 LTE Design Aspects
User throughput Mobility

95% from the users will take average throughput 0-15km/ hour the more better subscriber behavior.
5% will be little bit smaller than the average 120 km/ hour the accepted behavior.
350 km/ hour very low data rate and data throughput.
Coverage
Enhanced MBMS
5 Km with high throughput
30 Km with low throughput Up to 16 multimedia channels per just one carrier
100Km with very low throughput

932/
 LTE Design Aspects
Flexible spectrum Deployment

The carrier could be 1.25 MHZ , 1.6 MHZ, 2.5 MHZ ,5MHZ , 10MHZ , 15MHZ or 20 MHZ

LTE Can be deployed at any IMT / ITU Defined Bands

LTE Deployment strategy

Stand Alone LTE Network

Coexisting LTE Network with full interoperability with Legacy networks

LTE Frequency Reuse Pattern

Generally it is equal to 1

1032/
LTE Design Aspects
LTE RAN agreed on the following

Full IP network Supporting both RT and NRT Services

No RNC Reduce the possibility of having SPOF
NO CS-CN reduce System complexity
Separate treatment for Signaling and Traffic improve the latency and
give more system flexibility
No SOHO enhance overall resources efficiency
QoS Fully aware genuine system
Multiple Antenna techniques fully supported to improve system
overall performance

1132/
Day Contents
• LTE Introduction
• SAE and Site solution

1232/
LTE Network Architecture
Historical Background

1332/
High Level SAE Architecture
SAE Architecture

SAE is system architecture evolution.

The Main Goal of SAE is to have very optimized Packet transfer
system
No RNC as well as no CS-CN
SAE consists of
1. EPC (Evolved Packed Core)
2. E-UTRAN
3. LTE-UE

1432/
SAE Architecture

1532/
SAE Architecture - EUTRAN

1632/
 SAE Architecture-EUTRAN
The X2 interface is designed to provide a logical signalling and
traffic path between neighbouring eNBs.

The term ‘neighbouring’ in this sense refers to eNBs that

generate adjacent cells between which Ues would be expected
to request handovers. The X2 interface is the functional
successor to the UMTS Iur interface, which interconnects
neighbouring RNCs.

An eNB is only expected to support X2 interfaces to

neighbouring sites with which there is a realistic possibility of
handover events occurring; an individual eNB would not be
required to support X2 interfaces to all eNBs in the network.
Indeed, the X2 is an optional interface and all of its functions
can be performed indirectly via the S1 and the MME/S-GW if
direct connections are not supported.

1732/
 SAE Architecture-EUTRAN
If supported, logical X2 interfaces can be physically transported along either direct or
indirect
connections.

A direct connection would require a point-to-point broadband connection to exist

between the two related eNB sites. This option offers advantages in terms of
resilience, in the sense that if multiple physical connections are supported the loss of
one transmission link would not be catastrophic, but has disadvantages in terms of
cost. If each eNB was expected to host connections to five or six neighbouring sites,
for example, the costs associated with the additional transmission requirements
could be unsustainably high.

Another disadvantage of using direct connections to support X2 interfaces is lack of

flexibility. The LTE E-UTRAN is designed to take advantage of a concept known as the
SON (Self-Organizing Network). The optional SON functionality supported by the eNB
allows it to attempt to establish an X2 interface connection automatically to any
previously unknown local cells reported in UE measurements. Such automatic
discovery and connection is only possible when all local eNBs are connected to the
same
common routing environment.
1832/
 SAE Architecture – Site Solution
Modern Single RAN base stations typically employ SDR techniques and follow
3GPP MSR guidelines, which allow them to operate in multi-standard, multi-
RAT modes. A high-level view of the generic layout of a hypothetical MSR base
station is shown in the diagram.

The transmission element connects the base station to a shared, packet-based

backhaul, which carries traffic for all supported RATs. The central
processor/control element maintains signalling connections with the
supported access controllers and core networks and routes traffic between
backhaul channels and DSP Pools.

In this example, a separate DSP instance from the baseband DSP Pool has
been assigned to handle each RAT transmitted in each sector, so each sector
has one DSP dedicated to handling a GSM cell, another for a UMTS cell and a
third for an LTE cell. Each DSP will perform the SDR functions required to take
the received user traffic and signalling and turn it into a transmitted downlink
signal. The set of downlink signals created for a given radio unit may be
summed. They will also take the signals received on the uplink and extract
from them the user traffic and signalling to pass on to the appropriate access
controller or core network.
1932/
 SAE Architecture – Site Solution
The links between baseband and radio units carry digital traffic. This consists of
complex-valued samples representing the carriers to be transmitted on the TX
side and high-rate sample streams describing the received RF signal on the
uplink side.

Each sector, in this example, requires its own radio unit to manage the physical
RF TX and RX functions. On the transmit side the radio unit performs DAC (Digital
to Analogue Conversion) and turns the stream of complex-valued data symbols
generated by the baseband DSPs into a physical analogue RF signal with the
same characteristics. An LPA (Linear Power Amplifier) then boosts the RF signal
to the required output power. In this example a single multi-carrier, multi-RAT
LPA is employed to amplify all RATs simultaneously before the signal is passed
through a TX filter to remove any out-of-band components.

On the RX side, the received signal is passed through an RX bandpass filter to

limit it to the required bandwidth and is then passed through an LNA (Low Noise
Amplifier) which boosts the signal, partly to overcome the loss experienced on
its journey from the antenna. The RF receiver and ADC (Analogue to Digital
Convertor) receive and sample the incoming RF signal at a very high rate to be
passed to the baseband.
2032/
 SAE Architecture – Site Solution
Base stations that follow the OBSAI/CPRI models, or that employ a similar
vendor-specific solution, offer network planners two main site design
choices that can be described as localized and distributed.

A localized design employs traditional antenna connectivity in the form of

analogue feeder cables. Typical configurations employ mast head downlink
amplifiers, which are commonly abbreviated as MHAs (Mast Head
Amplifiers), TMAs (Tower Mounted Amplifiers) or some other vendor-
specific acronym and are used to boost the strength of downlink signals to
offset some of the losses that signals can expect to experience as they
travel down the feeder. Power for an MHA can be fed up the feeder itself by
installing a ‘Bias T’ unit at the base station end of the cable. The loss
associated with analogue feeders typically limits the maximum distance
between the RF units and the antennas to something less than 120 m, even
with MHAs.

The main challenges associated with a distributed model relate to the need
to provide a local power feed for the RRH units at the antenna site and the
difficulties associated with routing an optical fibre cable between the
connected nodes
2132/
 SAE Architecture – Site Solution
Different vendors have adopted a variety of designs for their particular
RRH units, which may incorporate a range of different elements.

Most RRH designs include at least the DAC/ADC elements that allow the
digital baseband-RF interface to connect to the analogue RF
components and all will incorporate an RF transceiver. Some RRH types
include radio up/down conversion elements that position that radio
signal into the correct part of the spectrum, although other designs
handle this functionality in SDR back in the baseband.

The transmitter side of the RRH includes the LPA and TX filter, while the
receive side includes the RX filter and LNA. Both sides are typically
connected to an RF combiner/diplexer, which allows the RRH to support
both main and diverse TX/RX feeder cables, which would be used if the
RRH was connected to, for example, a cross-polarized antenna panel.

2232/
SAE Architecture – EPC

2332/
SAE Architecture – EPC

2432/
 SAE Architecture – EPC
S1 Flex Deployment

Each eNB is able to establish associations with multiple MME and S-GW devices
following a principle known as S1-Flex.

The main benefit of Flex capability is that it provides redundant core network
services for each eNB and the set of UEs they serve. When a new UE requests
service in a cell, whether due to an initial Attach or following a Handover, the
eNB is able to select the MME to which it forwards the NAS connectivity
request from one or more MME Groups. If an individual MME fails or becomes
overloaded, the Flex concept ensures that only a subset of each cell’s users will
be affected. Similar redundancies are provided for EPS Bearer connections
through S-GWs.

Associated with the benefits of service redundancy are those of load balancing.
If eNBs tailor the numbers of UEs they introduce to each MME to the
advertised ‘relative capacity’ of each of those devices then the chances of
individual MMEs becoming overloaded is minimized.

2532/
SAE Architecture – EPC

2632/
SAE Architecture – EPC

2732/
SAE Architecture – EPC

2832/
SAE Architecture – EPC

2932/
SAE Architecture – EPC

3032/
SAE Architecture – EPC

3132/
SAE Architecture – EPC

3232/
LTE Interfaces – Over all View
 X2- Interface
With the removal of the RNC from the access network architecture,
inter-eNB handover is negotiated and managed directly between eNBs
using the X2-C interface. In LTE implementations that need to support
macro diversity, the X2-U interface will carry handover traffic PDUs
(Protocol Data Units) between eNBs.

X2-C (control plane) signalling is carried by the X2AP (X2 Application

Protocol), which travels over an SCTP association established between
neighbouring eNBs.

X2AP performs duties similar to those performed by RNSAP (Radio

Network Subsystem Application Protocol), which operates between
neighbouring RNCs over the Iur interface in UMTS R99 networks.

X2-U (user plane) traffic is carried by the existing GTP-U (GPRS

Tunnelling Protocol – User plane), as employed in UMTS R99 networks.
The facilities provided by the X2-U interface are only expected to be
required if macro-diversity handover is supported.

Both sub-types of the X2 interface travel over IP: SCTP/IP for the X2-C
and UDP/IP for the X2-U.
 S1- Interface
Backhaul links to the core network are carried by the S1 interface.
Following the general structure of the Iub interface which it replaces,
traffic over the S1 is logically split into two types.

S1-U flows carry user plane traffic and S1-MME flows carry mobility
management, bearer control and direct transfer control plane traffic.

Message structures for the S1-MME interface that operate between the
eNB and the MME are defined by S1AP (S1 Application Protocol). The
S1AP performs duties that can be seen as a combination of those
performed by R99 RANAP (Radio Access Network Application Part) and
GTP-C (GPRS Tunnelling Protocol – Control plane).

To provide additional redundancy, traffic differentiation and load

balancing, the S1- flex concept allows each eNB to maintain logical
connections to multiple S-GWs and MMEs – there may therefore be
multiple instances of the S1 interface per node.

The S1-U interface employs GTP-U to create and manage user-plane

data contexts between the eNB and the S-GW.
 Air Interface - NAS
EMM Is evolved mobility management Protocol and it is
responsible on
• Attach
• Detach
• TAU
• …. etc

ECM (ESM) is evolved connection (Session) management

protocol and it is responsible on
• Session Setup
• Session release
• Session Negotiation
• …. etc
 Air Interface - RRC
As with other E-UTRA protocols, the RRC layer, which previously resided
in the RNC, has been relocated to the eNB. In addition, the functionality
and complexity of RRC has been significantly reduced relative to that in
UMTS. The main RRC functions for LTE include creation of BCH system
information; creation and management of the PCH (Paging Channel);
RRC connection management between eNB and UEs, including
generating temporary identifiers such as the C-RNTI; mobility-related
functions such as measurement reporting, inter-cell handover and
inter-eNB UE context handover; QoS management; and direct transfer
of messages from the NAS to the UE.

The RRC is in overall control of radio resources in each cell and is

responsible for collating and managing all relevant information related
to the active UEs in its area.
THANK YOU
OFFICE ADDRESS
UK Office
1A Rothesay Avenue, Wimbledon Chase
London SW20 8AX
+44 7901 572145

Egypt Office
Building-1 St. 210, Victoria Square, Maadi, Cairo
+201111113341
+20111 8003322
+201001150012
EMAIL
info@digis2.com
Sales@digis2.com

facebook.com/DIGIS2

LinkedIn.com/DIGIS2

DIGIS2 Company Profile

www.DIGIS2.com