LTE Final v2

Outline
o Introduction
o LTE Architecture
o Physical Time-Frequency Structure
o Communication Channels
o LTE Protocol Stack
o Initial Access
o PRACH
o EPS Bearer and ICIC
o Mobility Management
INTRODUCTION
LTE
• LTE stands for Long Term Evolution
• Mobile broadband technology from 3GPP
• Promises data transfer rates of x100 Mbps
• Based on 3G UMTS technology
• Two variants:
– LTE FDD (most popular)
– LTE TDD (more promising?!)
• Optimized for All-IP traffic
LTE Benefits
3GPP Targets of LTE
• Higher performance
– Up to 200 active users in a cell (5 MHz)
– 100 Mbit/s peak downlink, 50 Mbit/s peak uplink
• 1G/s for LTE-Advanced (4G IMT-Advanced)
• Better cell edge performance
• Reduced data plane latency (up to 10 ms) for better user experience
• Scalable bandwidth from 1.4 MHz to 20 MHz
• Backwards compatible
– Works with GSM/EDGE/UMTS/HSPA based Mobile networks
– Utilizes existing 2G and 3G spectrum and newly available spectrum bands
– Supports handover and roaming to existing Mobile networks
• Reduced Capex/Opex via simple, flat, all-IP architecture
– reuse of existing cell-sites and multi-vendor sourcing of components
• Enhanced multimedia broadcast multicast service (E-MBMS)
• TDD (unpaired) and FDD (paired) spectrum modes
• Optimized for 0 ~ 15 km/h, but supports up to 350 km/h
• Large range of devices (phones, PCs, tablets, cameras, IoT, etc)
Peak Data Rates of 3GPP Technologies
Source:”LTE for UMTS OFDMA and SC-FDMA Based Radio Access” by Harri Holma
LTE FDD Frequency Bands
Source:”Radio-Electronics.com”
LTE TDD Spectrum Bands
Source:”Radio-Electronics.com”
LTE Enabling Technologies
• Uses Orthogonal Frequency Division Multiple Access
(OFDMA) for downlink, not CDMA as in 3G UMTS
– CDMA is not suitable for carrier bandwidths beyond 5MHz due
to multipath fading
– OFDM is a kind of multi-carrier transmission
– But, low power-amplifier efficiency due to large variations in
instantaneous power of the txed signal
• Uses Single-Carrier Frequency Division Multiple Access
(SC-FDMA) for uplink
– Reduces Peak Average Power Ratio (PAPR) and saves power of UEs
• Multi-user MIMO for enhanced system throughput
• Adaptive modulation and coding
– QPSK, 16QAM, 64QAM
– Convolutional coding, turbo coding
• Multi-carrier channel-dependent resource scheduling
• Fractional frequency reuse
– Active interference avoidance and coordination
LTE: Summary of Major Features
Source: Agilent
3GPP UTMS Long Term Evolution
3GPP LTE Evolution
Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

3GPP LTE Evolution
LTE ARCHITECTURE
LTE Architecture
LTE Architecture
• X2: only logical interface, practically transported over the same backhaul
link as the S1 interface up to first IP aggregation router
• It exists between neighbor eNodeBs for handover and interference mgmt
Source:http://ltemobilezone.wordpress.com/category/lte-physical-introduction/
LTE Architecture
• LTE network encompasses the evolution of:
– the radio access through the E-UTRAN
– the non-radio aspects under the term System Architecture Evolution (SAE)
• At a high-level, the network is comprised of:
– Core Network (CN), called Evolved Packet Core (EPC) in SAE has 3 main logical nodes:
• PDN Gateway (P-GW), Serving Gateway (S-GW) and Mobility Management Entity (MME)
– access network (E-UTRAN/also called as LTE)
• E-UTRAN solely contains the evolved base stations, called eNodeBs or eNBs
• E-UTRAN + EPC  Evolved Packet System (EPS)
• EPC is responsible for overall control of UEs and establishment of the bearers
– A bearer is an IP packet session with a defined QoS between P-GW & UE in EPS
– So, when an end point of flow is in Internet, end-to-end QoS is not guaranteed. Skype vs JIO voice
• EPC can be connected to other 3GPP and non-3GPP radio access networks and it
also includes other nodes and functions, such as
– Home Subscriber Server (HSS) (similar to HLR in 2G)
– Policy Control and Charging Rules Function (PCRF)
• EPS only provides a bearer path of a certain QoS, control of multimedia
applications is provided by the IP Multimedia Subsystem (IMS), which is
considered outside of EPS
eNodeB/eNB
• Unlike UMTS Node-B, eNodeBs are most complex,
autonomous nodes and perform additional tasks like
– Dynamic scheduling of Resource Blocks (discussed later) in DL &
UL to its attached UEs
– Ciphering and header compression
– Providing QoS for real-time & background bearers
– Load balancing between different simultaneous radio bearers to
different UEs
– Interference management: talks with neighbor eNodeBs over X2
to exchange
• channel quality
• RB allocations, etc
– Mobility management: if target eNodeB is reachable over X2,
eNBs communicate directly and perform seamless handovers
Mobility Management Entity (MME)
• It’s the control plane node in EPC
• Handles all signaling b/w eNBs and EPC, and b/w UEs and
EPC except air interface signaling (i.e., NAS signaling)
• Like SGSN of GPRS/UMTS networks, but does not handle
user data
• Performs the following tasks
– Authentication
– Establishment of bearers
– NAS mobility management  paging idle UEs
– Handover support, if no X2 is available b/w eNBs
– Interworking with other radio networks like GSM or UMTS: either
eNodeB does handover or asks MME to handle that
– SMS and voice support
S-GW and P-GW
• S-GW and P-GW: User plane nodes in EPC
• Serving-GW (S-GW): Manages user data tunnels b/w
eNodeBs and P-GW
– Mobility anchor for other 3GPP techs (GSM/GPRS/HSPA)
• P-GW: Gateway to the Internet, intranets
– Like GGSN of GPRS, UMTS networks
– Assigns IP addresses to UEs
– Handles roaming services
– Mobility anchor for non-3GPP techs (CDMA2000, Wi-Fi)
• In theory, MME, S-GW, P-GW could be implemented
in a single node
LTE vs 3G UMTS
3GPP Towards Flat Architecture
Source:”LTE for UMTS OFDMA and SC-FDMA Based Radio Access” by Harri Holma
Mixed 3GPP Cellular Network Architecture
Source:3GPP Long Term Evolution (LTE)Protocol Primer by Sandy Fraser June 25, 2008
LTE PHYSICAL TIME-FREQUENCY
STRUCTURE
PHY Layer
• Based on OFDMA with cyclic prefix in downlink
• Based on SC-FDMA with a cyclic prefix in the uplink
• Three duplexing modes are supported: full duplex FDD,
half duplex FDD, and TDD
• Two frame structure types:
– Type-1 shared by both full- and half-duplex FDD
– Type-2 applicable to TDD
• Supported modulation schemes: QPSK, 16QAM, 64QAM
• Broadcast channel only uses QPSK
• CRC-24 used for error detection (not at MAC as in Wi-Fi)
OFDM
LTE has 1200 sub-carriers for 20MHz carrier BW

OFDMA
• OFDM as user-multiplexing/MA scheme
– Different subsets of the set of sub-carriers can be

assigned to different users for U/L and D/L txs
– This assignment can be adjusted dynamically at
every OFDM symbol interval
OFDMA
• OFDM as user-multiplexing/MA scheme
– Distributed user multiplexing

– LTE exploits it for D/L scheduling

OFDMA vs SC-FDMA
Source: http://lte-epc.blogspot.in/2011_12_01_archive.html
http://www.eefocus.com/book/08-04/408401276057576.html
Type-1 Frame (FDD)
• A radio frame has a length of 10 ms and contains 20 slots
• Two adjacent slots constitute a subframe of length 1 ms
– Short subframe enables the exploitation of channel variations by
scheduling users depending on their current channel quality
• Frame definition is also true for UL/DL in FDD and TDD modes
Source: :LTE Physical-Layer Overview by Peter Wanmg

Resource Grid
Source:Technical Overview of 3GPP LTE by Hyung

OFDMA time-freq multiplexing
• LTE UEs are scheduled in frequency and time domains

• Basic time domain unit for scheduling is 1 TTI=1subframe
Source:LTE Physical-Layer Overview by Peter Wanmg

LTE Time-Frequency Resource Grid
Name Length in Time Domain Length in
Frequency
Domain
Resource Element 1 OFDM Symbol (66.7 1 subcarrier (15
microsec) KHz)
Resource Block 7 OFDM symbols in 12 subcarriers
(12*7=84 OFDM NCP (0.5 millisec=1
symbols) time slot)
Resource Block Pair 2 consecutive time 12 subcarriers
slots ( 1ms=1subframe)
Half-frame 5ms >= 72
subcarriers
Frame 10ms >= 72
subcarriers
Physical Resource Block (PRB)
PRB: Smallest RB assigned to an UE
TTI: Scheduling Unit
TTI (1ms: sub-frame): Smallest Scheduling Interval
Half-duplex FDD
• Frequency-band dependent
– In bands having narrow duplex gap
• UE is typically full-duplex and configurable for both
modes
• But eNodeB is always full-duplex
– Supports UEs of both types simultaneously
– But half-duplex UEs bring in scheduling restrictions
Type-2 Frame (TDD)
• UE and eNB share single carrier frequency for UL & DL

• Frame consists of 1 or 2 special sub-frames
• DwPTS: D/L Pilot time slot is like normal D/L subframe, but short (3 symbols)
• UpPTS: very short and does n’t carry any data tx, but for sounding and RACH
• GP (20 microsec) for switching radio from TX to RX and vice versa

Timing Relation for TDD

Type-2 (TDD) Frame Configurations

Type-2 (TDD) Frame Configurations
• eNodeB: which UL/DL configuration to operate on?
– Depends on traffic demands in UL/DL directions
– Can be changed on frame-by-frame basis
• Arbitrary UL/DL configurations by neighboring cells
could lead to severe interference
– E.g., UE1 at cell edge rxing from associated eNB1 while
UE2 associated with eNB2 txing at the same time in vicinity
– Solutions:
• Align UL/DL config with neighboring cells eNBs and change on very
slow basis
• Manage interference by carefully assigning RBs through ICIC
mechanism (via X2 interface)  discussed later in detail
Communication Channels
Communication channels
Three categories:
1. A logical channel is defined by the type of information it
carries and are classified as:
I. a control channel, used for transmission of control and configuration
information necessary for operating an LTE system
II. a traffic channel, used for the user data
2. A transport channel is defined by how and with what
characteristics the information is transmitted over the radio
interface
3. A physical channel is defined by time-frequency resource grid
on underlying frequency band
LTE Logical Channels
Logical channels are offered by the MAC layer.
• Control Channels: Control-plane information
– Broadcast Control Channel (BCCH)
– Paging Control Channel (PCCH)
– Common Control Channel (CCCH)
– Multicast Control Channel (MCCH)
– Dedicated Control Channel (DCCH)
• Traffic Channels: User-plane information
– Dedicated Traffic Channel (DTCH)
– Multicast Traffic Channel (MTCH)
LTE Transport Channels
Physical layer transport channels offer information
transfer to/from MAC and higher layers
• DL Channels
– Broadcast Channel (BCH)
– Downlink Shared Channel (DL-SCH)
 Used by many logical channels
– Paging Channel (PCH)
– Multicast Channel (MCH)
• UL Channels
– Uplink Shared Channel (UL-SCH)
 Used by many logical channels
– Random Access Channel (RACH)
LTE Physical Channels
These are timeslots (resource elements) on frequency
channel that carry user data & control messages
• DL Channels
– Physical Broadcast Channel (PBCH): System Info like cell BW in
MIB by using QPSK
– Physical Control Format Indicator Channel (PCFICH): length of
Control region i.e., 1-3 OFDM symbols in every sub-frame (1 ms)
– Physical Downlink Control Channel (PDCCH): inform DL
scheduling decisions, UL grants, UL power-control cmds;
o PDCCH carries Downlink Control Information (DCI) which carries
control information for a particular UE
o Multiple DCIs per cell
– Physical Hybrid ARQ Indicator Channel (PHICH): ACKs/NAKs
– Physical Downlink Shared Channel (PDSCH): data traffic, paging
– Physical Multicast Channel (PMCH): multicast data traffic
LTE Physical Channels
These are timeslots on frequency channel that carry
user data & control messages
• UL Channels
– Physical Uplink Control Channel (PUCCH): ACKs/NAKs,
scheduling requests (SRs)
– Physical Uplink Shared Channel (PUSCH): data traffic
– Physical Random Access Channel (PRACH)
• The only non-synchronised transmissions that UEs can make
• UEs contend for radio resources by using this channel
Downlink Channel mapping
• BCCH: Broadcast • DTCH: Dedicated Traffic • DL-SCH: Downlink Shared

• CCCH: Common • MTCH: Multicast Traffic • MCH: Multicast
• PCCH: Paging • BCH: Broadcast
• MCCH: Multicast
• PCH: Paging
https://netmanias.com/en/post/blog/12895/lte/lte-radio-channels
Uplink Channel Mapping
Source: LTE “ The UMTS Long Term Evolution” by Stefania Sesia

Downlink Reference Signals
• Predefined (pilot) signals occupying specific resource elements within time-freq grid
• Several types of D/L reference signals: Cell-Specific reference signals (CRS), positioning
signals (release 9), etc
• Ref Signals are used by UE to acquire Channel-State Info (CSI)
• Downlink: Total of 8 cell-specific reference symbols per reference signal in 1 sub-

frame (Time-domain) for all Resource blocks (RBs) in frequency-domain
• How many Ref symbols in a frame if LTE contains 100 RBs?
• 504 different physical-cell identities: have varying positions of Ref symbols
• 6 frequency shifts & ref symbols are txed with higher energy compared to
other resource elements
• Neighbor cells use differently frequency shifted ref signals to improve SIR gain for
ref symbols
DL Physical Channel Structure
Downlink /w two reference signals
• Control region carries L1/L2 control signaling

• Partly comes from L1 (PHY) & L2 (MAC) and supports D/L & U/L transport channels
• PCFICH, PDCCH, PHICH, and Relay-PDCCH
• D/L scheduling assignments, info to receive, demodulate, and decode DL-
SCH, uplink scheduling grants, width of control region, H-ARQ ACK/NACKs,
power control commands for uplink phy channels
• Width of control region depends on amount of traffic and cell bandwidth and could be
varied per sub-frame level
• More BW: lesser width
• More UEs for scheduling: more width
• Txed at the start of sub-frame to reduce D/L delay in delivery of data
• It also helps UEs not having any data to receive to sleep for rest of sub-frame
Physical D/L Control CH (PDCCH)
• PDCCH carries Downlink Control Info (DCI)
– D/L scheduling assignments, inc. PDSCH resource
indication, transport format, Hybrid ARQ info, cmd
for power control of PUCCH
– U/L scheduling grants, inc. PUSCH resource
indication, transport format, Hybrid ARQ, cmd for
power control of PUSCH
– One PDCCH carries one DCI, so multiple PDCCHs
per cell to support data transfer to multiple UEs
UL Physical Channel Structure
Position of PUCCH (carries L1/L2 control signals) on Uplink

PUCCH carries scheduling Reqs & ACK/NAKs
UL Sounding Reference Signals
Sent On PUSCH
Physical Channel Structure

LTE peak bit rate calculation
• From the 3gpp specification:-
• 1 Radio Frame = 10 Sub-frames
• 1 Sub-frame = 2 Time-slots
• 1 Time-slot = 0.5 ms (i.e, 1 Sub-frame = 1 ms)
• 1 Time-slot = 7 Modulation Symbols (when normal CP length is used)
• 1 Modulation Symbol = 6 bits; if 64 QAM is used as modulation scheme
• Radio resource is managed in LTE as resource grid

1 Resource Block (RB) = 12 Sub-carriers
• Assume 20 MHz channel bandwidth (100 RBs)
• How many number of bits in a sub-frame?

• = 100RBs x 12 sub-carriers x 2 slots x 7 modulation symbols x 6 bits
• = 100800 bits
Hence, data rate = 100800 bits / 1 ms = 100.8 Mbps
• If 4x4 MIMO is used, then the peak data rate would be 4 x 100.8 Mbps = 403
Mbps.
• If 3/4 coding is used to protect the data, we still get 0.75 x 403 Mbps = 302
Mbps as peak PHY data rate.
LTE PROTOCOL STACKS
LTE Protocol Stack
Source:3GPP Long Term Evolution (LTE)Protocol Primer by Sandy Fraser

Protocol Layers
IP packets are passed through multiple protocol entities:
• Packet Data Convergence Protocol (PDCP)
– IP header compression based on Robust Header Compression (ROHC)
– ciphering and integrity protection of transmitted data, in-sequence delivery to
higher layers
– One entity per Radio bearer
• Radio Link Control (RLC)
– segmentation/concatenation of compressed PDCP SDUs
– retransmission handling (ARQ) for reliable delivery
– in-sequence delivery to higher layers
– One entity per Radio bearer
• Medium Access Control (MAC)
– Multiplexes logical channels to transport channels
– handles Hybrid-ARQ retransmissions, one H-ARQ per component carrier
– uplink and downlink scheduling done centrally at the eNodeB
• Physical Layer (PHY)
– coding/decoding, modulation/demodulation (OFDM)
– multi-antenna mapping, other typical physical layer functions
Protocol Layers
• Radio Resource Control (RRC) is part of only Control plane Stack
– Broadcast of system information
• It communicates to lower layers for cell specific configuration/reconfiguration and
UE specific configuration/reconfiguration
– RRC connection control
• Covers all procedures related to the establishment, modification and release of an
RRC connection, including paging, initial security activation, establishment of
Signalling Radio Bearers (SRBs) and of radio bearers carrying user data (Data Radio
Bearers, DRBs)
– Handovers/mobility, Recovery from radio link failure
– Inter-RAT mobility including security activation, transfer of RRC context
information
– Measurement configuration and reporting
• Establishment/modification/release of measurements (e.g., intra-frequency, inter-
frequency and inter- RAT measurements)
• Generic protocol error handling
• Support of self-configuration and self-optimization
• Other functions including transfer of dedicated NAS information and non-3GPP
dedicated information, transfer of UE radio access capability information, support
for E-UTRAN sharing (multiple PLMN identities)
LTE Protocol Stack: Functional split
RAN Protocol Architecture

LTE Protocol Architecture (User Plane)
Source: http://lte-epc.blogspot.in/2009_11_01_archive.html
LTE Protocol Architecture: Downlink
• RLC offers services
to PDCP in the form
of radio bearers
• MAC offers services
to RLC in the form of
logical channels
• PHY offers services
to MAC in the form
of transport
channels
• PHY maps transport
channels to physical
channels (aka time-
frequency resource
grids)

LTE Data Flow:

LTE Layers in UE side:
Transport block is sent in data region (PUSCH/PDSCH) of subframe

Initial Access
LTE Initial Access
• In LTE, a UE must perform certain steps before
it can receive or transmit data
• These steps can be categorized as
– Cell search and cell selection
– Derivation of system information
– Random access
LTE Initial Access
• Acquisition of frequency and symbol synch to a cell

• Acquisition of frame timing of cell: start of D/L radio frame
• Determine PHY layer cell-ID
Cell Search
Physical Channel Structure

Physical cell identity
PSS and SSS positions in FDD & TDD
Difference in position of PSS/SSS in FDD/TDD allows UE for the detection of the

duplex scheme used on a carrier if this is not known in advance

Cell Search
• Step I – Primary Synchronization Signal
– The UE first looks for PSS which is transmitted in the last
OFDM symbol of the first time slot of the
subframes (subframe 0, 5) in a frame.
– PSS sent in a frame are identical
– 3 different PSS sequences exists
– With PSS UE has identified phy layer identity (but
not cell-id group) for this cell and 5 ms timing
• So, position of SSS is also known to UE
• But, UE does not know whether it’s first half frame or
2nd half frame of an LTE radio frame
Structure of PSS
Three different length-63 sequences;

Mapped to 72 sub-carriers (6 center RBs of the cell)
Hence these 72 sub-carriers are not available for DL-SCH
Step II – Secondary Synchronization Signal (SSS)
• The second step is to obtain the radio frame timing

and the cells’ group identity (168 alternatives)
– 168 different PSS sequences exists
• This information can be found from the SSS.
• SSS is transmitted in the symbol before the PSS .
• Like PSS, SSS is also transmitted in the first and sixth
subframes (subframes 0 and 5) of a frame
• PSS structure varies in a frame (SSS1 and SSS2)
– So, UE determines whether it’s 1st half frame or 2nd half
frame
Structure of SSS
At the end of Cell Search…
• UE gets frame timing and phy layer cell-id, which
helps it to know the reference signal pattern
– 504 different reference signals
• As discussed earlier, ref signals help UEs in
– RRC_IDLE: To estimate D/L channel quality and decoding of
BCH transport channel to get sys info or
– RRC_CONNECTED: To measure received power and send it
to source eNB as RSRP/RSRQ reports for making handover
decisions
System Information
• By cell search, a UE gets cell-ID, synchronizes to a cell
and listens to cell-specific reference symbols for D/L
channel estimation.
• Then it requires system information to be able to
access and, in general, operate properly within the
network and within a specific cell.
• System information includes
– information about the downlink and uplink cell
bandwidths
– the uplink/downlink configuration in the case of TDD
– detailed parameters related to random-access
transmission and uplink power control, etc.
System Information
• In LTE, system information is delivered by two
different mechanisms relying on two different
transport channels:
– A limited amount of system information,
corresponding to the so-called Master-Information
Block (MIB), is transmitted using the BCH/PBCH.
– The main part of the system information,
corresponding to different so-called System-
Information Blocks (SIBs), is transmitted using the
downlink shared channel (DL-SCH)
• PDCCH is used to convey this scheduling decision to all UEs
by using SI-RNTI identifier
MIB
• MIB (Sent on BCH/PBCH every 40 ms, repeated
every 10 ms) includes mainly the following
information
– Information about the downlink cell bandwidth
• 4-bit field to convey 16 different BWs
– Information about the PHICH configuration of the cell
• Helps UE to be able to receive L1/L2 control signaling on
PDCCH which in turn is needed to receive DL-SCH
– The System Frame Number (SFN)
MIB

SIB (System Information Block)
• The main part of the system information is sent as
System-Information Blocks (SIBs)
• LTE defines a number of different SIBs characterized
by the type of information that is included within
them:
– SIB1 includes information mainly related to
whether a UE is allowed to camp on the cell
• MCC and MNC of cell
• TDD config, Tracking area code (for paging)
• Scheduling list of other SIBs that are sent and their
intervals, which can vary from cell to cell, operator to
operator
• SIB2 includes information that UEs need in order
to be able to access the cell.
• the uplink cell bandwidth, PUCCH config
• random-access parameters (PRACH length)
• Parameters related to uplink power control, SRS config
• SIB3 mainly includes information related to cell
reselection.
• SIB4–SIB8 include neighboring-cell-related information
– LTE and non-LTE, on same and different channels
• SIB9 contains the name of the home-eNodeB (smallcells)
• SIB10–SIB12 contain public warning messages, for
example earthquake/tsunami/floods information.
• SIB13 contains information necessary for MBMS
reception
MIB/SIB
• Like MIB, SIBs are sent periodically

• SI: System Information message corresponds to one Transport Block
sent on DL-SCH
• SIBs should have common period for mapping them to same SI
Random Access
Random Access
• Random access is used by UEs for
– connection setup
– acquisition of uplink timing
• In LTE, random access is used for several purposes, including:
– for initial access when establishing a radio link, getting C-
RNTI ID (if it does n’t have one)
(RRC_IDLE to RRC_CONNECTED state)
– to re-establish a radio link after radio-link failure
– for handover when uplink synchronization needs to be
established to the new cell
– as a scheduling request if no dedicated scheduling-request
(SR) resources has been configured on PUCCH for UE
Random Access-contention based
Only first 2 steps for Contention-free Random Access

RRC Connection Establishment procedure
https://www.eventhelix.com/lte/#.W-XWaZMzbD6
Step 1- Random Access Request
• The transmission of a random-access preamble, allowing
eNodeB to estimate the transmission timing of the terminal.
• Uplink synchronization is necessary as the terminal otherwise
cannot transmit any uplink data.
• Terminal sends a preamble to the eNodeB using Physical
Random-Access Channel (PRACH).
• Terminal selects a preamble from a set of 64 preambles
available in a cell  This is a contention phase.
• 64 preambles are divided into 3 sets
• Contention-free preambles used for handovers
PRACH Configuration
• 6 RBs in Frequency domain

• 1 or more sub-frames in time domain, tuned by eNB dynamically
based on cell size, FDD/TDD mode, etc

Step 2: Random-Access Response
• In response to the detected random-access attempt,
eNodeB transmits Message2 on the DL-SCH containing:
– The index of the random-access preamble sequences the
network detected and for which the response is valid.
– The timing correction calculated by the random-access
preamble receiver.
– A scheduling grant on UL-SCH, indicating resources the UE
could use for the transmission of the message in Step 3
– A temporary identity, C-RNTI, for UE for further
communication between the UE and the network.
• Upon reception of the random-access response in the
step 2, the UE will adjust its uplink transmission timing
and continues to Step 3
Step 3: Terminal Identification
• Before user data can be transmitted to/from the
terminal, a unique identity within the cell must be
assigned to the terminal.
• If the terminal is in the RRC_CONNECTED state – that is,
connected to a known cell and therefore has a M-TMSI
assigned – this M-TSMI is used as the terminal identity in
the uplink message
• Otherwise terminal picks random no. as the UE identity
• In MSG3, RRC Connection REQ is sent to eNB to setup
RRC channel to exchange signaling messages with eNB
and Core N/W
– It includes conn. Establishment cause
– It includes UE identity: M-TMSI/Random No.
Step 4: Contention Resolution
• It consists of downlink message for contention resolution & RRC
conn. Setup message
• From Step 2, multiple terminals performing simultaneous
random-access attempts using the same preamble sequence in
Step 1 listen to the same response message in Step 2 and
therefore have the same temporary identifier.
• Terminals that do not find a match between the identity
received in the fourth step and the respective identity
transmitted as part of the third step are considered to have
failed the random-access procedure.
• MSG4 contains parameters for setting up a dedicated Signaling
RB (SRB-1) in AM mode at UE
– SRB-1 is used to carry further RRC msgs for setting up additional radio
bearers and NAS signaling msgs for authentication before actual DATA tx
Random Access-contention free
Source:3GPP Long Term Evolution (LTE)Protocol Primer by Sandy Fraser June 25, 2008
Random Access-Contention free
• Some preambles are reserved for contention
free RACH.
• The eNodeB assigns these preambles to
specific UEs
• At a time only one user uses each preamble.
• Used for re-establishing uplink
synchronization upon downlink data arrival,
handover, and positioning.
Physical Channel Procedure (1/2)

Physical Channel Procedure (2/2)

LTE Identities
https://www.eventhelix.com/lte/LTE-identifiers.pdf
MAC Layer
Medium Access Control (MAC)
• Data on a transport channel is organized into transport
blocks.
• In each Transmission Time Interval (TTI), at most one
transport block of varying size is transmitted over the radio
interface to/from a UE (in absence of spatial multiplexing)
• Each transport block has an associated Transport Format (TF)
– specifies how the block is to be transmitted over the radio interface
(e.g. transport-block size, modulation scheme, and antenna
mapping)
• By varying the transport format, the MAC layer can realize
different data rates.
– Rate control is therefore also known as transport-format selection
MAC Header and SDU Mux
• MAC ctrl elements carry time-advance info and RACH responses in D/L
and Power head room and Buffer status in U/L

MAC Header and SDU Mux
• Carrier aggregation (e.g., 20MHz+20MHz) is visible only at MAC layer

• Separate HARQ per component carrier (CC)
• Up to 2 Transport blocks (incase of MIMO spatial multiplexing) per
component carrier per UE
MAC Scheduler
• eNB scheduler assigns the time/frequency resources at each TTI
dynamically for both uplink and downlink
– dynamically controls the UE(s) to transmit to and, for each of these
UEs, the set of RBs upon which the UE’s DL-SCH/UL-SCH should be
transmitted
– Semi-static scheduling to reduce control overhead in PDCCH and for
QoS
• VoIP, streaming apps
• Uplink and Downlink decisions can be taken independently by eNB
• Scheduler broadcasts resource assignment decisions/grants on
PDCCHs  All UEs monitors PDCCHs on Control Region in TTIs
• Scheduler is responsible for implementing QoS parameters assigned
to radio bearers
• The scheduling strategy is implementation specific and not specified
by 3GPP
– scheduler selects best multiplexing for UE based on channel conditions
– preferably schedules transmissions to a UE on resources with
advantageous channel condition
MAC Scheduler
• Most scheduling strategies need information about:
– channel conditions at the terminal
– buffer status and priorities of the different data flows
– interference situation in neighboring cells (if some form of interference
coordination is implemented)
• UE transmits
– channel-status reports reflecting the instantaneous channel quality in the time
and frequency domains
– Buffer & battery status
– information necessary to determine the appropriate antenna processing in
case of MIMO spatial multiplexing
• Interference coordination, which tries to control the inter-cell
interference on a slow basis, is also part of the scheduler
– ICIC (discussed later)
Downlink Scheduling

Uplink Scheduling
• eNB assigns U/L sch grants in UL-

SCH to UEs for sending L1/L2
control signals (buffer status (u/l
req), CSI, HARQ ACKs) + U/L DATA
• Else UE uses PUCCH to send

L1/L2 control signals
• eNB assigns RBs per terminal

(UE), not per radio bearer in u/l
• UE in turn decides which logical

CHs muxed into transport block

UE: UL Scheduling Request
• Each UE can be assigned a dedicated PUCCH scheduling REQ
resource every nth frame
– 1-bit flag & no need to tell UE ID to eNB
– It’s better in high traffic intensity scenarios
• Alternative approach: contention-based scheduling REQ in
RACH for low traffic scenarios
UE: UL Scheduling Grant
• eNB first assigns few RBs in UL-SCH as scheduling grant to UE
• UE sends DATA & piggybacks additional info to eNB in UL-SCH grants
– MAC cntrl elements are used for this purpose
– Buffer status report per Logical channel group
– Power headroom at UE
Uplink Priority Scheduling
• Option 1: Serve logical channels in strict priority order
– Starvation
• For each logical channel, a prioritized data rate is configured
in addition to the priority value
Ex: Prioritization of two logical channels for three different uplink grants
Signaling D/L RB Allocation in PDCCH
• 3 different schemes: Type 0, 1, 2 which
consume varying no. of bits for
signaling RB allocation inside PDCCH
• Type 0/1 support non contiguous RB System BW RBG Size (P)
allocation while Type 2 does n’t (No. of RBs)
• Type 0: a bit in bitmap corresponds to ≤10 1
a group of RBs in freq. domain; Size of 11 – 26 2
group depends on BW; For large BWs, 27 – 63 3
a bit  2 to 4 RBs which affects 64 – 110 4
scheduling granularity
• Best in terms of flexibility, but
expensive in terms of overhead as bit
map size could be =Total no. of RBs in
network
http://www.etsi.org/deliver/etsi_ts/136200_136299/136213/08.08.00_60/ts_136213v080800p.pdf
DL Type-0 Allocation: Example
http://www.sharetechnote.com/html/DCI.html & http://www.sharetechnote.com/html/Handbook_LTE_RAType.html

Signaling D/L RB Allocation
• Type 1: UE is assigned a set of PRBs from one of P RBG
subsets
– Bitmap addresses a single RB in the selected RBG subset in
such a way that MSB to LSB of the bitmap are mapped to the
RBs in the increasing frequency order
– To reduce no. of bits in bitmap & keep total no of bits same
as that in Type 0, offset is introduced (refer Sec 7.1.6.2)
• Type 2: UE is assigned a set of contiguously allocated
localized or distributed RBs
http://www.etsi.org/deliver/etsi_ts/136200_136299/136213/08.08.00_60/ts_136213v080800p.pdf
Resource allocation is done at 'RBG Subset' level


Signaling U/L RB Allocation
• Allocated RBs have to be contiguous in order to guarantee single-carrier
property (SC-FDMA is used in the Uplink in LTE)
• 2 different schemes: Type 0, 1
– Single-cluster (similar to Type 2 in D/L, hopping flag)
– Multi-cluster (up to 2 clusters, no hopping flag)
Timing Relation of Uplink Grants
An uplink grant received in a subframe n triggers an uplink transmission in subframe n+4
Uplink transmission occurs in subframe n + k, where k is the smallest value larger

than or equal to 4 such that subframe n + k is an uplink subframe.
Scheduling Algorithms
• Round Robin (RR)
• Maximum CQI
• Proportional Fair (PF)
• So many others …
• Perform differently for

– Full buffer
– Real User traffic patterns
• Metrics considered
– Complexity and scalability
– Spectral efficiency
– Fairness
– QoS provisioning
System Model
Channel-dependant Scheduling

Round Robin
• Allocation of RBs equally among UEs in time slice manner
• UE with bad channel condition gets low throughput, so
there is no throughput fairness in equal allocation of RBs
• Increase in Delay and not suited for real-time traffic
Channel Aware / Max CQI
• Channel quality information (CQI) are periodically
sent by UEs to eNB
• Dik(t) are achievable throughput expected for the ith user at
the tth TTI over the kth RB
Dik(t) = log [1 + SINRik(t)]
• Types of algorithms
 Maximum Throughput/CQI
o Maximizes the overall throughput by assigning each RB
to the user that can achieve the maximum
throughput/CQI in the current TTI
o Unfair sharing of resources (cell edge users will suffer)
 Proportional Fair
Proportional Fair
• It is very suitable scheduling option for non real-time traffic
• A practical scheduler operating somewhere in between the max-C/I
scheduler and RR
– Try to utilize fast variations in channel conditions as much as
possible while still satisfying some degree of fairness between users
• It attempts to maintain fairness for users with bad channel conditions
by scheduling them on their fading peaks regardless of channel quality
• It exploits short-term channel variations for RB allocation while
maintaining the long-term average user data rate
• Select user k with relatively best radio link quality
Where Ri is is the instantaneous data rate for user i and 𝑅𝑅�𝑖𝑖 is the average
data rate for user i
• So, ensures fairness by ensuring same avg throughput for all UEs
or at least a certain min throughput for all UEs
Comparison of Scheduling Algos

Comparison of Scheduling Algos

Other Types of Scheduling Algorithms
• Resource allocation algorithms can be classified into following
groups:
– channel-unaware
– channel-aware/QoS-unaware
– channel-aware/QoS-aware
– semi-persistent for VoIP support
– energy-aware
Survey paper on LTE Downlink Scheduling:

https://drive.google.com/open?id=0B6Myw_O3S0w4YXBGS
HNaZ3I5Umc
Channel Unaware Strategies
• First In First Out
• Blind Equal Throughput
• Resource Preemption
• Weighted Fair Queuing
• Guaranteed Delay
– Earliest Deadline First
– Largest Weighted Delay First (LWDF)
Hybrid ARQ (HARQ)
• Hybrid ARQ = ARQ + FEC.
• In hybrid ARQ, up to 8 parallel stop-and-wait processes are used by eNB/UE
(this can result in data being delivered from the hybrid-ARQ mechanism out-
of-sequence, in-sequence delivery is ensured by the RLC layer)
– Why 8 SAW processes?
– Min 5 SAWs as sender can retx earliest in (n+5)th subframe as receiver takes 3ms to process
received block and then 1ms to send ACK/NACK in PUSCH/PUCCH or PHICH
– But sender can defer retx even further, hence up to 8 SAWs
Timing Relation of Uplink Grants
An uplink grant received in a subframe n triggers an uplink transmission in subframe n+4
Uplink transmission occurs in subframe n + k, where k is the smallest value larger

than or equal to 4 such that subframe n + k is an uplink subframe.
Hybrid ARQ (HARQ)
• Hybrid ARQ is not applicable for all types of traffic (broadcast transmissions
typically do not rely on hybrid ARQ).
– Hence, hybrid ARQ is only supported for the DL-SCH and the UL-SCH
• MAC uses HARQ with soft combining
– Erroneous packet still contain some useful info, so it is kept in a buffer and
combined with retx packet (possibly with different set of FEC/CRC bits)
before decoding again
• After some retries, HARQ discards packet
• HARQ in Downlink
– Asynchronous (n+5 to n+8) and adaptive (tx attributes like MCS, RBs allocated, FEC/CRC are
adapted based on channel conditions)
• HARQ in Uplink
– Synchronous, non-adaptive or adaptive (tx attributes like MCS, FEC/CRC are adapted based
on channel conditions
• RLC ensure in-sequence delivery by employing ARQ + sliding-window
protocol
RLC Layer
Radio Link Control (RLC) Layer
• Depending on the scheduler decision, a certain amount of
data (byte stream like in TCP) is selected for transmission from
the RLC SDU buffers and the SDUs are
segmented/concatenated to create the RLC PDU.
• Each RLC PDU includes a header, containing, among other
things, a sequence number used for in-sequence delivery by
the retransmission mechanism
• A retransmission protocol operates between the RLC entities
in the receiver and transmitter.
– Receiver monitors sequence numbers and identifies missing PDUs
• Although the RLC is capable of handling transmission errors,
error-free delivery is in most cases handled by HARQ at MAC
layer
RLC Segmentation and Concatenation:

LTE RLC Modes
Source: 3GPP LTE Radio Link Control (RLC) Sub Layer

RLC Modes
• Transparent Mode (TM)
– Virtually a null entity that does not perform any
RLC function
• No Segmentation/concatenation, no ARQ, no in-
sequence-delivery
• RLC PDU = RLC SDU containing an RRC msg
– Used to carry RRC msgs (paging/Broadcast) that
do not require any security protection by PDCP &
reach all UEs
– Upper layer of TM RLC is RRC
– Supports only unidirectional radio bearers
RLC Modes
• Unacknowledged Mode (UM)
– Optimized to carry delay sensitive user plane traffic,
from DTCH logical channel, like VoIP or audio/video
streaming
• No retransmissions (i.e, no ARQ) but in-sequence delivery
– Framing function to make RLC SDUs fit into RLC PDUs
whose size is indicated by the MAC layer
• Concatenation/segmentation of RLC SDUs in the buffer on
byte stream at RLC Tx entity
– In-sequence-delivery at RLC Rx entity
– Supports only unidirectional radio bearers
RLC Modes
• Acknowledged Mode (AM)
– The main mode of operation of RLC layer
– UM with Retransmissions (ARQ)
– Used to carry traffic reliably by control and data planes like
RRC msgs that are not sent using RLC TM and TCP traffic on
DL-SCH
– ARQ functions
• Sliding window protocol with windows at both ends
• Polling (Tx entity seeks pkt reception status)
• Status reporting by Rx entity
• Retxs
• Re-segmentation to adapt to channel conditions
– Supports bidirectional radio bearers
Example: In-Sequence Delivery
RLC Modes
• Reordering aka in-sequence-delivery
– Done in UM and AM RLC entities
– Why out-of-sequence reception?
• Several SAW based HARQ processes at MAC
– RLC sequence no in RLC PDU is used to detection it
– Reordering timer to detect loss in a HARQ process and
to limit max wait time for missing PDUs
• Only one timer in an RLC entity on the first received out-of-
sequence PDU
• On expiry, UM RLC reassembles SDUs from RLC PDUs stored in
the buffer
• On expiry, AM RLC rx sends status report to AM RLC tx for
getting them retransmitted
– After reception, reordering timer is set to the highest SN PDU in the
buffer
Example: In-Sequence, Reliable Delivery
PDCP Layer
Packet Data Convergence Protocol
(PDCP)
• Header compression and decompression for user
plane data
• Security functions:
– ciphering and deciphering for user plane and
control plane data;
– integrity protection and verification for control
plane data;
• Handover support functions:
– in-sequence delivery and reordering of PDUs for the
layer above at handover;
– lossless handover for user plane data mapped on RLC
Acknowledged Mode (AM)
Overview of User Plane PDCP PDU

Header Compression
• One of the main functions of PDCP is header compression using the RObust
Header Compression (ROHC) protocol defined by the IETF
• In LTE, header compression is very important because there is no support for
the transport of voice services via the Circuit-Switched (CS) domain.
• Thus, in order to provide voice services on the Packet-Switched (PS) domain in a
way that comes close to the efficiency normally associated with CS services it is
necessary to compress the IP/UDP/RTP3 header which is typically used for Voice
over IP (VoIP) services.

Header Compression
• The support of ROHC is not mandatory for the UE,
except for those UEs which support VoIP.
• UEs which support VoIP have to support at least one
profile for compression of RTP, UDP and IP.
• Typically, for the transport of a VoIP packet which
contains a payload of 32 bytes
– header added will be 60 bytes for the case of IPv6 and 40
bytes for the case of IPv4– i.e. an overhead of 188% and
125% respectively.
– By means of ROHC, after the initialization of the header
compression entities, this overhead can be compressed to
four to six bytes, and thus to a relative overhead of 12.5–
18.8%.
• This calculation is valid during the active periods, but during
silence periods the payload size is smaller so the relative
overhead is higher.

RRC Layer
Radio Resource Control (RRC)
• Main services and functions
– Broadcast of System info (both NAS and AS related)
– Tx of Paging messages
– Establishment, maintenance and release of an RRC connection
b/w UE and E-UTRAN
• Allocation of temp identifiers b/w UE and E-UTRAN
• Confg of signaling radio bearer(s), SRB, which is mapped to CCH/DCCH
for sending RRC messages to UE
– Security functions including key management
– Establishment, configuration, maintenance and release of point
to point Radio Bearers
– Mobility functions
• UE measurement reporting
• Handovers
• UE cell re(selection)
– QoS control
– Measurement configuration and reporting
RRC States (1/2)
• RRC_IDLE
– PLMN selection
• PLMN info (MCC/MNC) are included in SIB1
– Selection of suitable cell to camp on
• UE uses Ref Signal Rx Power (RSRP in rel 8)/Ref Signal Rx Quaility
(RSRQ in rel 9) as cell selection criteria
• UE Monitors PCH and system info on BCH/DL-SCH from camped cell
• DRX config by NAS to save power
– UE shall have been allocated an id which uniquely identifies
the UE in a Tracking Area, TA or TA list (not at the granularity
of cell)
– Cell re-selection due to mobility
– No RRC context stored in the eNB
– UE performs random access to move to RRC_Connected
state
RRC States (2/2)
• RRC_CONNECTED
– RRC_Idle  RRC_Connected
• RRC context established
– Connected Cell is known and UE gets C-RNTI for signaling with eNB
– Network can transmit and/or receive data to/from UE
• In_SYNC: DL and UL Data Tx possible
• Out_of_SYNC: ONLY DL Data Rx possible
– Network controlled mobility
• Intra-RAT and inter-RAT
– Neighbour cell measurements
– At PDCP/RLC/MAC level
• UE monitors control signalling channel for shared data channel to see if
any transmission over the shared data channel has been allocated to UE
• UE also reports channel quality information and feedback information
to eNB
• DRX period can be configured according to UE activity level for UE
power saving and efficient resource utilization
RSRP
• RSRP (Ref Signal Received Power)
– RSRP is the linear average of cell-specific reference signals
across the channel bandwidth
– RSRP provides information about signal strength and gives
no indication of signal quality
– The reporting range of RSRP is defined from -140 dBm to -44
dBm with 1 dB resolution.
• Mapped to integer numbers value range from 0 to 97 before they
are included in the RRC messages.
RSRQ
• RSRQ (Ref Signal Received Quality)
– RSRQ indicates quality of received reference signal
– RSRQ is based on RSRP and RSSI
• RSSI
– RSSI comprises linear avg. of the total received power only in OFDM
symbols containing ref symbols over N RBs by UEs from all sources, inc.
co-channel and adjacent from serving and non-serving cells, noise
– UE does not report RSSI
• N is no. of RBs
EPS Bearers
EPS Bearers
• QoS flows called EPS bearers established b/w UE and P-GW
• Default bearer is established when UE connects to a PDN, and that remains
established throughout the lifetime of the PDN connection to provide the UE with
always-on IP connectivity to that PDN.
• The initial bearer level QoS parameter values of the default bearer are assigned
by the network, based on subscription data.
• Dedicated bearer: Any additional bearer established
• The decision to establish or modify a dedicated bearer can only be taken by the EPC,
and the bearer level QoS parameter values are always assigned by the EPC
EPS Bearer Service Architecture
A data radio bearer transports packets of EPS bearer b/w UE and

eNB; 1-1 mapping b/w EPS and radio bearer

Message Flow For EPS Establishment

GBR vs N-GBR Bearers
• GBR bearer: Dedicated network resources of Guaranteed Bit Rate
(GBR) are permanently allocated (e.g. by an admission control
function in eNB) at bearer establishment/modification
• Otherwise, a bearer is referred to as a Non-GBR bearer
• A dedicated bearer can either be a GBR or a Non-GBR bearer while
a default bearer shall be a Non-GBR bearer
• A bearer is associated with QoS parameters
– QoS Class Identifier (QCI): scalar that is used as a reference to access
node-specific parameters that control bearer level packet forwarding
treatment (e.g. scheduling weights, admission thresholds, queue
management thresholds, link layer protocol configuration, etc)
– Allocation and Retention Priority (ARP): the primary purpose of ARP is to
decide whether a bearer establishment /modification request can be
accepted or needs to be rejected in case of resource limitations &
dropping of bearers during handovers
• Defined by priority level, pre-emption capability and pre-emption
vulnerability flags
– GBR bearer additionally has 2 QoS parameters
• Guaranteed Bit Rate (GBR): the bit rate that can be expected to be provided by a
GBR bearer
• Maximum Bit Rate (MBR): the maximum bit rate that can be expected to be
provided by a GBR bearer. MBR >= GBR
QoS Class Identifiers in LTE
• Packet Delay Budget (PDB) defines an upper bound for the time that a packet may be delayed
between the UE and the PCEF. PDB denotes a "soft upper bound”– no dropping of expired pkts
• Note that TCP is very sensitive to packet loss than Voice and hence uses ARQ at lower layers to mask
losses
Table 6.1.7 in TS 23.203 & http://4g-lte-world.blogspot.in/2013/01/quality-of-service-qos-in-lte.html
QoS Class Identifiers in LTE
A-AMBR: APN Aggregate maximum bit rate is the max allowed total non-GBR throughput to specific APN
UE -AMBR: UE Aggregate maximum bit rate is the max allowed total non-GBR throughput among all APN to a UE
TFT: Traffic flow template is always associated with dedicated bearer and while default bearer may or may not have TFT.
L-EBI: It stands for Linked EPS bearer ID.
http://www.3gpp.org/DynaReport/23401.htm
Handovers
Handovers
• X2 interface is used in general for handover preparation
• S-GW acts as anchor for inter-eNB handovers
X2 Handover Steps
X2 based Handover

http://www.3glteinfo.com/intra-lte-handover-
using-x2-interface/
S1 based Handover
S1 based Handover
References
1. 4G LTE/LTE-Advanced for Mobile Broadband by
Stefan parkvall et. al. (on GC)
2. www.3gpp.org
3. Small cell forum
4. Videos, Papers, Tutorials:
http://www.eventhelix.com/lte/lte-tutorials.htm
5. Handbook
http://www.sharetechnote.com/html/Handbook_LTE.html

LTE Final v2

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LTE Final v2

Uploaded by

Copyright:

Available Formats

Outline

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

LTE has 1200 sub-carriers for 20MHz carrier BW

– Different subsets of the set of sub-carriers can be

– Distributed user multiplexing

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Source: :LTE Physical-Layer Overview by Peter Wanmg

Source:Technical Overview of 3GPP LTE by Hyung

• LTE UEs are scheduled in frequency and time domains

Source:LTE Physical-Layer Overview by Peter Wanmg

• UE and eNB share single carrier frequency for UL & DL

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

• BCCH: Broadcast • DTCH: Dedicated Traffic • DL-SCH: Downlink Shared

Source: LTE “ The UMTS Long Term Evolution” by Stefania Sesia

• Downlink: Total of 8 cell-specific reference symbols per reference signal in 1 sub-

• Control region carries L1/L2 control signaling

Position of PUCCH (carries L1/L2 control signals) on Uplink

Source:LTE Physical-Layer Overview by Peter Wanmg

• Radio resource is managed in LTE as resource grid

• Assume 20 MHz channel bandwidth (100 RBs)

• How many number of bits in a sub-frame?

Source:3GPP Long Term Evolution (LTE)Protocol Primer by Sandy Fraser

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Transport block is sent in data region (PUSCH/PDSCH) of subframe

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

• Acquisition of frequency and symbol synch to a cell

Source:LTE Physical-Layer Overview by Peter Wanmg

Difference in position of PSS/SSS in FDD/TDD allows UE for the detection of the

Source:LTE Physical-Layer Overview by Peter Wanmg

Three different length-63 sequences;

• The second step is to obtain the radio frame timing

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

• Like MIB, SIBs are sent periodically

Only first 2 steps for Contention-free Random Access

• 6 RBs in Frequency domain

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Source:LTE Physical-Layer Overview by Peter Wanmg

Source:LTE Physical-Layer Overview by Peter Wanmg

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

• Carrier aggregation (e.g., 20MHz+20MHz) is visible only at MAC layer

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

• eNB assigns U/L sch grants in UL-

• Else UE uses PUCCH to send

• eNB assigns RBs per terminal

• UE in turn decides which logical

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

http://www.sharetechnote.com/html/DCI.html & http://www.sharetechnote.com/html/Handbook_LTE_RAType.html

Resource allocation is done at 'RBG Subset' level

http://www.sharetechnote.com/html/DCI.html & http://www.sharetechnote.com/html/Handbook_LTE_RAType.html

http://www.sharetechnote.com/html/DCI.html & http://www.sharetechnote.com/html/Handbook_LTE_RAType.html

An uplink grant received in a subframe n triggers an uplink transmission in subframe n+4

Uplink transmission occurs in subframe n + k, where k is the smallest value larger

• Perform differently for

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall

Survey paper on LTE Downlink Scheduling:

An uplink grant received in a subframe n triggers an uplink transmission in subframe n+4

Uplink transmission occurs in subframe n + k, where k is the smallest value larger

Source: 4G LTE/LTE-Advanced for Mobile Broadband by Stefan Parkvall