07 - LTE Physical Channels and Procedures - v04

LTE Physical Channels and Procedures
LTE Air Interface Course
1 Nokia Siemens Networks

Layer and Channels Relationship

Physical Resource
Time Structure for FDD Mode
Time Structure for TDD Mode
Overview of FDD Physical Channels
Cell Search
Initial Access
LTE Downlink Transmission
LTE Uplink Transmission
TDD Physical Channels

DCCH
UL-SCH PUSCH
DTCH
UL
PUCCH
CCCH RACH PRACH
MTCH
MCH PMCH
MCCH
Transport channels
Logical channels
PDCCH
Upper Layers
Air interface
PHY
RLC
MAC
PCFICH
PHICH
DL
DTCH
DCCH
DL-SCH PDSCH
CCCH
Nokia Siemens Networks

PCCH PCH
BCCH BCH PBCH
5

Physical Resource
Cell Search
Initial Access

Resource Block and Resource Element
Physical Resource Block or Resource Block ( PRB or RB):

12 subcarriers in frequency domain x 1 slot period in time domain.
Subcarrier 0 1 2 3 4 5 6 0 1 2 3 4 5 6 Capacity allocation is based on

1 0 1 2 3 4 5 6 0 1 2 3 4 5 6 Resource Blocks
0 1 2 3 4 5 6 0 1 2 3 4 5 6 Resource Element ( RE):
0 1 2 3 4 5 6 0 1 2 3 4 5 6
1 subcarrier x 1 symbol period
0 1 2 3 4 5 6 0 1 2 3 4 5 6
180 KHz
0 1 2 3 4 5 6 0 1 2 3 4 5 6
Theoretical minimum capacity
allocation unit.
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
1 RE is the equivalent of 1
0 1 2 3 4 5 6 0 1 2 3 4 5 6
modulation symbol on a
subcarrier, i.e. 2 bits for QPSK,
0 1 2 3 4 5 6 0 1 2 3 4 5 6
4 bits for 16QAM and 6 bits for
0 1 2 3 4 5 6 0 1 2 3 4 5 6
64QAM.
Subcarrier 0 1 2 3 4 5 6 0 1 2 3 4 5 6
12
1 slot 1 slot Resource
1 ms Element
subframe
Physical Resource Blocks
12 subcarriers
In both the downlink and uplink
.. ..
direction, data is allocated to users
Frequency in terms of resource blocks (RBs).
A resource block consists of 12
Resource 1 ms subframe consecutive subcarriers in the
block or TTI
frequency domain, that are
reserved for the duration of one 0.5
millisecond time slot.
The smallest resource unit a
0.5 ms slot
Time scheduler can assign to a user is a

During each TTI,
resource blocks for
scheduling block which consists of
different UEs are two consecutive resource blocks
scheduled in the
eNodeB


Physical Resource
Cell Search
Initial Access

LTE Physical Layer - Introduction
It provides the basic bit transmission functionality over air
LTE physical layer based on OFDMA downlink and SC-FDMA in uplink
direction
This is the same for both FDD and TDD mode of operation
There is no macro-diversity in use
System is reuse 1, single frequency network operation is feasible
No frequency planning required
There are no dedicated physical channels anymore, as all resource mapping
is dynamically driven by the scheduler
FDD
Frequency band 1 ..
..
Frequency band 2 ..
..
TDD
Single frequency ..
.. band
Downlink Uplink
LTE Physical Layer Structure Frame Structure (FDD)
FDD Frame structure ( also called Type 1 Frame) is common to both uplink and
downlink.
Divided into 20 x 0.5ms slots
Structure has been designed to facilitate short round trip time
- Frame length =10 ms
- FDD: 10 ms sub-frame for UL and 10
ms sub-frame for DL
- 1 Frame = 20 slots of 0.5ms each
0.5 ms slot - 1 slot = 7 ( normal CP) or 6 symbols (
sy0 sy1 sy2 sy3 sy4 sy5 sy6 extended CP)
10 ms frame
s0 s1 s2 s3 s4 s5 s6 s7 .. s18 s19
SF: SubFrame
s: slot
0.5 ms slot
Sy: symbol
SF0 SF1 SF2 SF3 .. SF9

1 ms sub-frame

Physical Resource
Cell Search
Initial Access

LTE Physical Layer Structure Frame Structure (TDD)
TDD has a single frame structure: same as FDD but with some specific fields to enable
also TD-SCDMA co-existence (China):
Common frame structure and slot duration allows to parameterize the LTE TDD mode of operation
so that the site can have compatible UL and DL split (static parameter)
Each half frame carries six subframes and three specialized fields ( inherited from TD-
SCDMA): DwPTS, GP, UpPTS
Subframe 0 and DwPTS are reserved for downlink; subframe1 and UpPTS are reserved
for UL. Remaining fields are dynamically assigned between UL and DL.
Also called Frame Type 2. TDD may change between UL and DL either with 5 or 10 ms
period
radio frame 10 ms
f
DwPTS
DwPTS
SF SF ... SF SF SF ... SF
UpPTS
UpPTS
UL/DL
GP
GP
carrier #0 #1 #5 #0 #1 #5
subframe 0 subframe 1 subframe 0 subframe 1 Subframe 5
subframe 5
half frame
DwPTS: Downlink Pilot time Slot time

Downlink Subframe
UpPSS: Uplink Pilot Time Slot
Uplink Subframe
GP: Guard Period to separate between UL/DL
TDD frame structure (1/2)
There are 7 frame configurations, according to different
DL/UL partition DL Downlink subframe
UL Uplink subframe
1 frame = 10ms SS Special Switching subframe
1 subframe = 10ms
0 DL SS UL UL UL DL SS UL UL UL
1 DL SS UL UL DL DL SS UL UL DL
2 DL SS UL DL DL DL SS UL DL DL
3 DL SS UL UL UL DL DL DL DL DL
4 DL SS UL UL DL DL DL DL DL DL
5 DL SS UL DL DL DL DL DL DL DL
6 DL SS UL UL UL DL SS UL UL DL

TDD frame structure (2/2)
Downlink / Uplink ratio can vary from 1/3 (Frame configuration = 0) to 8/1
(Frame configuration = 1), depending on the service requirements of the
carrier
Frame always starts with a downlink subframe, used for advertising the
frame descriptor, PCFICH and PDCCH. UE hence learns the frame
structure in this subframe.
3rd frame is always used for uplink.
When switching from downlink to uplink, there is need for a special

switching subframe. No special subframe is used when switching from
uplink to downlink.

Special subframe
UE always needs a guard period in order to switch from receiver to

transmitter.
The guard period includes RTD (Round Trip Delay).
PT = Propagation Time
eNodeB ends Start of UL subframe
SP = Switching Period
transmitting reaches at eNodeB
GP RTD = Round Trip Delay
GP = Guard Period
PT SP PT
Downlink Uplink eNodeB
Downlink Uplink UE
End of DL UE has switched to RTD = 2 x PT

subframe has transmission and has GP = RTD + SP
reached at the UE begun UL subframe

Phyisical Resource
Cell Search
Initial Access

General Comment
Please note that the target of this section is to show the big picture of all the
physical channels involved in LTE. The details for every channel are shown in
the consequent following sections. Therefore it is recommended that here the
level of detail is kept as small as possible.
To show all steps and channels involved, one scenario is selected.

Scenario:
The end user is switching on his/her LTE mobile

and would like to download something
from the Internet
eNodeB
What are all the steps and

the physical channels
involved ??
UE

Cell Search
What do I need on the first place?
Find one cell
Get synchronisation time & frequency
Finally I read system info to find out:

Global cell id
Cell bandwidth


Cell Search (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
UE
like CPICH* in UMTS)
eNodeB
4. PBCH Physical Broadcast Channel
(MIB* DL system bandwidth, PHICH
*CPICH = Common Pilot configuration)
Channel
MIB = Master Information Block
PHICH = Physical HARQ
Indicator Channel
Cell Search
Challenge:
The PBCH contains only the MIB (Master Information Block) the
SIBs(System Information Blocks) are on the PDSCH (Physical Downlink
Shared Channel)!!
need to read SIBs on PDSCH
The UE should read PDSCH but it doesn't know which resource blocks are
reserved for it and where are they placed (in time and frequency)
Solution:
PCFICH (Physical Control Format Indicator Channel) indicates the size of
PDCCH (Physical Downlink Control Channel)
the PDCCH is indicating which resource blocks are scheduled and where
are located

Cell Search (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 UE
selection reselection, )
eNodeB
*SIB = System Information Block CELL SELECTION &

RESELECTION

What are the Next Steps?
The UE has selected one cell camping on the cell procedure
The camping on the cell procedure will be explained later

(more details in chapter 8)
The UE can start the initial access
I have found one suitable

cell. What is next?
UE eNodeB

Random Access (1/2)
8. PRACH preamble (A )
(A is the first random preamble )
.
.
.
8. PRACH preamble (C)
(C is the 3rd random preamble )
UE
eNodeB Challenge:
Several UEs may send the same preamble. How
to solve the collision ?
Solution:
contention resolution
Random Access (2/2)


(Resource allocation for PDSCH)

(Random Access response, UE
eNodeB ID of the received preamble,

C-RNTI *)
*C-RNTI = Cell Radio Network
Temporary Identity

Contention Resolution for the Initial Access
8. PRACH Preamble

(Random Access response, ID of the
received preamble, UL resources for TX,
C-RNTI)
12. PUSCH Physical Uplink Shared Channel

(RRC: RRC Connection Request,
UE
*C-RNTI,
eNodeB
TMSI or random number)

* C-RNTI = Cell Radio Network
Temporary Identity (Contention Resolution,
TMSI = Temporary Mobile
Subscriber Identity
C-RNTI & TMSI or random number)

What are the Next Steps?
The random access procedure is successfully finished
Next steps:
- RRC Connection Establishment
- Registration
- UE-CN Signalling (Attach)
eNodeB
Higher layer signalling -> not shown here
Now I am connected so I
can download the web
page from the Internet.
www.nsn.com
UE

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)
5. PDSCH Physical Downlink Shared Channel UE
(user data -> initial transmission)
eNodeB
(ACK/ NACK for HARQ)
CQI = Channel Quality Indicator
ACK = Acknowledgment 7. PDSCH Physical Downlink Shared Channel
NACK = Negative ACK
HARQ = Hybrid Automatic (user data eventual re-transmission)
Repeat Request
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 UE
(user data initial transmission)
eNodeB
6. PHlCH Physical HARQ Indicator Channel
*DPCCH = Dedicate Physical (ACK/ NACK for HARQ)
Control Channel
ACK = Acknowledgment 7. PUSCH Physical Uplink Shared Channel
NACK = Negative ACK
HARQ = Hybrid Automatic (user data eventual re-transmission)
Repeat Request

Phyisical Resource
Cell Search
Initial Access

Cell Search


UE
like CPICH in UMTS)
eNodeB
(MIB DL system bandwidth, PHICH
configuration)

Cell Search Procedure
eNodeB 1. Time & Frequency

Synchronisation
PBCH
2. Find the CELL identity (ID)
Synchronization (1504 options)
signals
I would like to
communicate
with the network. UE
What are the first 3. Receive and decode the cell system
steps? information sent on PBCH
(PBCH is scrambled with the cell ID)
PBCH = Physical
Broadcast Channel

Synchronisation
Challenge 1: find the cell
UE receives synchronisation signals from several cells
Challenge: How to distinguish between several cells??
Solution:??
Physical cell identity UE
eNodeB eNodeB
PSS = Primary Synchronisation Signal

SSS = Secondary Synchronisation Signal

Synchronisation
Challenge 2: time synchronisation
Get time synchronisation (symbol, time-slot, frame)

UE
eNodeB
The system may use long/ short cyclic prefix
How can the UE know the position in time of the synchronization signals??
Solution:??
Fixed time position for the synchronisation signals
PSS = Primary Synchronisation Signal

SSS = Secondary Synchronisation Signal

Synchronisation
Challenge 3: frequency synchronisation
Get the frequency synchronisation

UE
eNodeB
The UE does not know the system bandwidth:
5, 10 .. 20 MHZ ?
How big is the Bandwidth? Where are the synchronisation signals placed in
frequency domain??
Solution:??
Fixed frequency position for the synchronisation signals
Fixed bandwidth for the synchronisation signals
1. Find the Cell
Each cell has a physical layer ID (number)

1..504 physical layer IDs
Physical layer ID: 3 0,1,2

From PSS = Primary Synchronisation Signal
Physical layer cell id group: 168

From SSS = Secondary Synchronisation Signal
Total 168 x 3 = 504 cell IDs

Subject to network planning
See next slide

1. Find the Cell - Hierarchical Cell Identities
Possible planning of the 504 sequences:
3 (orthogonal) X 168 (pseudo-random) = 504 Physical layer

cell identity
Cells belonging to the same Node-B get the 3 (1 out of 504)
different cell IDs from the same group
Cells belonging to different Node-Bs get the

different cell IDs from different groups
Cell groups 0 1 167
Cell IDs 0 1 2 0 1 2 0 1 2

2. Time Synchronization FDD Mode
10ms Radio frame
2 3 4 5 7 8 9 10
1ms Subframe
SSS
PSS
0.5ms (One slot)
1 2 3 4 5 6 7 Normal CP
1 2 3 4 5 6 Extended CP
PSS and SSS frame and slot structure in time domain in the FDD
case

2. Time synchronization TDD mode
10ms Radio frame
1 2 3 4 5 6 7 8 9 10
1ms Subframe
SSS
PSS
1 ms TTI (two slots = 20.5ms)
1 2 3 4 5 6 7 1 2 3 4 5 6 7 Normal CP
1 2 3 4 5 6 1 2 3 4 5 6 Extended CP
PSS and SSS frame and slot structure in time domain in the TDD
case

PSS Primary Synchronisation Signal
Time slot (0.5 ms) syncronization

PSS placed strategically at the beginning and middle of frame
Estimation is vendor specific (matched filtering)
Frame ambiguity of 0.5 ms
Find physical layer cell ID

1 out of 3 sequences sent on PSS
1 to 1 mapping with the physical cell ID (table specified by 3GPP*)
The cell ID group not known yet
UE
eNodeB

* 3GPP TS 36.211
SSS Secondary Synchronisation Signal
Frame (10 ms) synchronization

2 different sequences depending on the cell group are sent: SSS0
and SSS1
By observing the combination of pairs SSS0 and SSS1 the UE can
identify either the begining or the middle of the frame
Example: the sequence SSS0-PSS is indicating the begining of the frame,
SSS1-PSS the middle of the frame
Find physical layer cell ID group

Sequences SSS0 and SSS1 are mapped with the cell id group 1..168
(table specified by 3GPP*)
The combination of SSS0 and SSS1 is giving the cell ID group

* 3GPP TS 36.211
3. Frequency Synchronization PSS
3 different PSS sequences
corresponding to 3
different cell IDs.
Length 63 Zadoff-Chu Sequence They could be generated
by using a different root
Zadoff Chu sequence M for the
Sequences are based ZCM(0) ZCM(1) ZCM(62) Zadoff-Sequences
on CAZAC =
Five zeros Five zeros
Constant Amplitude 0 0 0 0
Zero Auto-Correlation
Cell ID Root index
sequences
OFDM Modulator (M)
0 25
1 29
2 34
62 subcarriers (d.c. not included)
PSS structure in frequency domain -> only 62 subcarriers out of 72 used. This is
because the length of the Zadoff-Chu Sequence is 63 (d.c. not included).

3GPP TS 36.211
3. Frequency Synchronization SSS
a , b = two different 2 different SSS per cell:

cyclic shifts of a single SSS0 in subframe 0 and SSS1
Length-31 binary sequence
length-31 in subframe 5.
binary sequence SSS0 and SSS1 have the same
a0 a1 a30 b0 b1 b30
structure but are shifted in
frequency domain
The cyclic shift is
0 0 0 0
Dependent on the
Physical layer cell OFDM Modulator
ID group (1..168)
SSS0 in
subframe 0
SSS1 in
subframe 5
SSS structure in frequency domain
Cyclic Prefix Length and FDD/TDD Mode
At this stage the cyclic prefix length is not known:

Normal
Extended
It is important for PBCH decoding
How can I learn about the CP length?
Solution:??
The position of SSS is changed in time (symbol 5 or 6 inside the time slot)
The UE is using blind detection to find the position so to find the CP length
The mobile may also learn whether the system is operated on FDD or on TDD
mode
different placement for PSS and SSS in time

PSS and SSS Frame in Frequency and Time Domain
for FDD Case
Frequency
6 RBs 72 subcarriers = 1.4 MHz

(minimum LTE Bandwidth)
SSS
PSS
Reference signals
Unused RE
5 ms repetition Time
period
10 ms Radio frame
One subframe (1 ms)

Cell Search


UE
like CPICH in UMTS)
eNodeB
configuration)

DL Reference Signals
Used for:
DL channel quality measurements
DL channel estimation for coherent demodulation at the UE
Like CPICH (Common Pilot Channel) in UMTS
Principle: insert known reference signals
RS = Reference Signals UE
eNodeB

DL Reference Signals
Challenges:
How many reference signals?
Too many signals reduce the DL capacity
Too less signals may be not be enough for channel estimation
What should be their position in time-frequency ?

Easy to be found by UEs
How to distinguish between different cells?

Reduce the possible inter-cell interference
UE
eNodeB

How Many Reference Signals? (1)
Frequency
First slot Second slot

1 2 3 4 5 6 7 1 2 3 4 5 6 7
In Frequency: 1 reference symbol to
every 6th subcarrier
In one RB (resource block = 12
subcarriers): every 3rd subcarrier
Exact position dependent on cell ID
Reference signal
*Normal CP (cyclic prefix) assumed
Time
In Time is fixed: 2 reference symbols per
Time slot (TS 0 & TS 4)
3GPP TS 36.211 V8.6.0 (2009-03)

How Many Reference Signals? (2)
In time:
depends on the maximum Doppler spread
At v = 500 km/h
Considering fc = 2GHz
Doppler shift is fd = fc*(v/c) = 950 Hz
Nyquist sampling theorem Tc = 1/(2*fd) =0.5ms
So we need at least 2 samples per Time Slot (TS)
In frequency:
Every 3rd subcarrier by looking in one resource block = 12 subcarriers
It has been shown that a grid-like arrangement of the reference signals is

optimal for channel estimation

How to Distinguish Between Different Cells? (1)
504 possible reference signals:

3 various orthogonal sequences mapped to the physical layer cell ID
168 various pseudo-random sequences mapped to the cell ID groups
168 x 3 = 504 sequences in total
subject to network planning
UE
eNodeB eNodeB

How to Distinguish Between Different Cells? (2)
Reference Signals (RS) frequency hopping

Frequency domain positions of the RS may be changed between consecutive
subframes (1 ms)
Adding a frequency offset to the basic RS pattern:

6 different hopping shifts possibile (the distance in frequency
domain between the RSs is 6 subcarriers)
What shift to use is in a cell is dependent on the physical layer cell ID
(504 possibilities)
Reduce collision risk between neighbour cells
(see next slide)
UE
eNodeB eNodeB

Different Reference Signals Frequency Shift
Frequency
Shift = 0 Shift = 1 Shift = 5
Time
Reference signal

Cell-specific Reference Signals in Case of Multi-
Antenna Transmission
Antenna port 0 Antenna port 1
Reference signal Unused symbol

Cell Search


UE
like CPICH in UMTS)
eNodeB
configuration)

PBCH Design Criteria
Detectable without the knowledge of system Bandwith

mapped to the central 72 subcarriers
over 4 symbols
during second slot of each frame
Low system overhead & good coverage

Send minimum information only the MIB (Master Information Block)
SIBs (System Information Blocks) are sent on PDSCH
MIB (Master Information Block) content:

DL system Bandwidth
PHICH configuration (PHICH group number)
UE
System frame number SFN eNodeB

PBCH Mapping
Slot 0 Slot 1
Frequency
6 RBs 72 subcarriers = 1.4 MHz
(minimum LTE Bandwidth)
SSS
PSS
Reference signals
Unused RE
PBCH
Time
First subframe (1 ms)

PBCH Repetition Pattern
one radio frame = 10 ms

72 subcarriers
Repetition Pattern of PBCH = 40 ms

PBCH
The bit scrambling of the PBCH depends on the physical cell ID

Known from synchronisation
PBCH uses QPSK only
One MIB sent in 40 ms (repetition pattern)
1920 bits or 1728 bits are to be transmitted for normal or extended CP
4 OFDM-symbol durations x 72 RE's are used
-> 4 x 72 = 288 symbols per radio frame

UE
eNodeB


Phyisical Resource
Cell Search
Initial Access

Initial Access
8. PRACH Preamble

C-RNTI)

UE
C-RNTI,
eNodeB

(Contention Resolution,
C-RNTI & TMSI)

RACH Procedure
Random access procedure handled by MAC and PHY Layer through PRACH (in UL) and
PDCCH ( in DL)
RACH only carries the preambles and occupies 6 resource blocks in a subframe
Process:
UEs selects randomly a preamble from the list of preambles broadcasted in the BCCH
UE calculates OLPC parameters ( Initial Tx Power)
Checks contention parameters (i.e. max. number of retries)
UE transmits initial RACH and waits for a response before retry. Open loop PC ensures
that each retry will be at a higher power level.
Upon receipt of successful UL RACH preamble, eNB calculates power adjustment and
timing advance parameters together with an UL capacity grant ( so UE can send more
info )
PRACH
Not detected response
DL
Next On the resources indicated by PDCCH
PRACH
resource
UL PUSCH: UE specific data
Preamble Preamble
63 Nokia Siemens Networks Presentation / Author / Date
PRACH Design
Challenges:
No interference with UL channels like PUCCH or PUSCH
No interference with other PRACH in the same cell
No interference with other cells in UL (neighbours)
Solution:??
Reserve time & frequency resources for initial access
PRACH Physical UL Random Channel

UE
PUCCH Physical UL Control Channel
eNodeB
PUSCH Physical UL Shared Channel

PRACH Design
Challenges:
The UL transmission of PRACH should be time synchronised
Otherwise high probability to interfere with other channels even if there are
reserved resources !
Solution:??
Introduce some guard time
UE
eNodeB

PRACH Resources
No interference with UL PUCCH or PUSCH
Reserve resources for PRACH preambles

Frequency: 6 Resource Blocks x 180 KHz = 1,08 MHz
Time: 1 ms
The location of those resource blocks is dynamically defined by 2 RRC

Layer Parameters (PRACH Configuration Index and PRACH Frequency
offset). The UE may learn the configuration from the system
information
RACH only carries the preambles -> no signalling or user data (like in e.g.
UMTS)
BUT: The eNodeB may also schedule data in the resource blocks reserved for
random access channel preamble transmission.
Multiplexing of PRACH with PUSCH and PUCCH
PRACH slot
Duration( e.g. 1ms)
PUCCH
Total UL Bandwidth
PRACH
PRACH PRACH bandwidth
(1.08MHz)
PUSCH
PRACH slot period
PUCCH Time
UL PRACH is orthogonal with the data in PUCCH and PUSCH

(reserved resources)
CHALLENGE: UL synchronisation needed
UL Synchronisation
DL synchronisation already there from cell search procedure
UL time synchronization to be done:
The start of UL frame is relative to the start of a DL frame

Due to propagation delay between BS-UE -> relative delay which is
monitored relative to the start of the DL frame
the UE may start the PRACH preamble at different distances in the cell ->
different relative delay
Use a guard band to solve this uncertainty

UE
(See Next slide) eNodeB

PRACH Preamble Received at the eNodeB
PRACH slot duration
GT = Guard Time
UE close
Other
to the users
CP Preamble Other users
eNodeB
Observation interval
UE at the
Other
Cell edge users
CP Preamble Other users
CP = Cyclic Prefix It can be seen that the UE at cell

edge is using almost all Guard Time

PRACH Formats and Cell Ranges
1 ms
CELL RANGE
103 s 800 s 100 s
C G 14 Km
Format 0 Preamble
P T
2 ms
684 s 800 s 520 s
Format 1 CP Preamble GT 77 Km
2 ms
203 s 1600 s 200s
Format 2 CP Preamble Preamble GT 29 Km
3 ms
684 s 1600 s 720 s
Format 3 CP Preamble Preamble GT 100 Km

PRACH Formats
Four Random Access (RA) preamble formats are defined for Frequency
Division Duplex (FDD) operation.
Each format is defined by the durations of the sequence and its Cyclic
Prefix CP.
Preamble Format TCP (s) TSEQ (s) Typical usage
0 103.13 800 Normal 1 ms RA burst with 800 s preamble

sequence, for smallmedium cells (up to 14 km)
1 684.38 800 2 ms RA burst with 800 s preamble sequence, for
large cells (up to 77 km) without a link budget
problem
2 203.13 1600 2 ms RA burst with 1600 s preamble sequence,
for medium cells (up to 29 km) supporting low
data rates
3 684.38 1600 3 ms RA burst with 1600 s preamble sequence,
for very large cells (up to 100 km)

Intra-Cell Interference
How can multiple terminals perform

random access attempt at the same time
without collision?
eNodeB Solution ?
64 different orthogonal Preambles

available in each cell obtained by cyclic
UE1 UE3 shift of a Zadoff-Chu sequence
UE2 If however collision is happening (2 UEs
using the same preamble) -> contention
resolution process

PRACH Power Ramping
BCH information
UE sets the initial transmission power of RACH

and send preamble signal
eNodeB
UE Preamble (RACH)
Preamble (RACH)
Preamble (RACH) DL-SCH
Random access message (UL-SCH) Power Ramping process is not

mandatory like in e.g. UMTS.
One major disadvantage is the
increased latency.
-> optional in LTE

Initial Access
8. PRACH Preamble

C-RNTI)

UE
C-RNTI,
eNodeB

C-RNTI & TMSI)

Random Access Response
The random access procedure is performed for the following five events:
Initial access from RRC_IDLE;
RRC Connection Re-establishment procedure;
Handover;
DL data arrival during RRC_CONNECTED requiring random access procedure;
UL data arrival during RRC_CONNECTED requiring random access procedure;
E.g. when UL synchronisation status is "non-synchronised" or there are no
PUCCH resources for SR available.
The random access procedure takes two distinct forms:

Contention based (applicable to all five events);
Non-contention based (applicable to only handover and DL data arrival).
Normal DL/UL transmission can take place after the random access procedure.

Contention based Random Access
Steps:
1. A preamble will be selected by UE and
transmitted in the available subframe.
UE eNB
Based on correlation the NB may detect the
access and furthermore can measure the timing
of the UE transmission.
1 Random Access Preamble
2. The NB answers using the same preamble and

Random Access Response 2
at this point a timing advance will be fixed.
Information on the scheduled resource will be
exchanged and a temporary C-RNTI will be
assigned.
3 Scheduled Transmission
3. The UE sends its id. The type of id depends on

the state. In case of idle state NAS info has to be
Contention Resolution 4 provided (IMSI, TMSI) else the C-RNTI is used.
4. The contention resolution is performed, i.e. the

NB addresses the UE using the C-RNTI.

Non-Contention Based Random Access
This case it is applied generally in the case of

handover.
UE eNB
In the handover the latency requirement is more
restrictive and therefore it is not possibile to
apply the contention based scheme.
0 RA Preamble assignment
0. The UE is receiving from the eNodeB the

1
preamble to be used for the initial aceess
Random Access Preamble
procedure. In this is way the probably of colision
is zero
1. The UE is responding with the preamble from
2 Random Access Response
step 0
2. Random Access Response from the NodeB
Note that the preamble sent in step 0 to the

mobile should be one out of 64 possible but
not allocated for the contention based
procedure

Random Access Response
Content of the random access response:

Index of random access preamble received
Timing correction calculated at Node-B
A scheduling grant indicating UL resources
A temporary ID for the UE used for further communication
UE
eNodeB


Phyisical Resource
Cell Search
Initial Access

RS
Synch
DCI PDCCH
CFI PCFICH
HI PHICH
Upper Layers
Air interface
PHY
RLC
MAC
MTCH
MCH PMCH
MCCH
DTCH
DCCH
DL-SCH PDSCH
CCCH
Nokia Siemens Networks

PCCH PCH
BCCH BCH PBCH
80
DL Transmission


eNodeB

(user data eventual re-transmission)

DL Transmission
Process description:
The eNodeB is broadcasting the Reference Signals (like CPICH in UMTS)
The UE is performing measurements on Reference Signals
Based on the measurements the UE is generating the CQI
The CQI is transmitted to the eNodeB

UE Proposes eNB an optimum MCS so BLER is on target
Note: CQI not only in time domain (like e.g. HSDPA) but also in frequency
domain
MCS = Modulation and Coding Scheme
BLER = Block Error Rate

DL Transmission
The Node-B scheduler should decide based on UL CQI:

The number of UEs to be scheduled
The allocated resource block (time & frequency)
Modulation and coding scheme
MIMO used or not
The decision is sent to the UE in the Control Channel Region of the subfame
(1ms) (on PDCCH) together with the allocated resource blocks
The actual user data is sent to the UE on the remaining subframe Data
Region (on PDSCH)
(see next slide)
UE
eNodeB
Downlink Control Channels
One subframe (1ms)
Resource elements
reserved for
12 subcarriers
reference symbols
(two antenna port case)
Frequency
Control Channel Time

Data Region
Region (1-3 OFDM symbols)
Location of the control region at the beginning of frame is useful because the UE
may learn if there is something interesting for it , if no continue sleeping
RE Resource Elements Groups
In order to support DL control information mapping,
RE-groups are defined.
Four useful symbols are bundled, useful in the
sense that RE's carrying the cell-specific reference
symbols are not available.
The one cell-specific RS case is mapped in the
same way as in the two cell-specific RS case.
So the example sketched in the figure on the left

hand side applies for the one and two antenna
cases. In the first symbol are six REs grouped,
however only four are available as two are blocked
by reference signals.
RE groups are aligned within one symbol and

occupy consecutive frequencies (subcarriers).
The RE groups are addressed by the index pair
(k',l') where k' is the lowest number among the REs
of the considered group.

DL Transmission


eNodeB


PCFICH Physical Control Format Indicator Channel
CFI = control format indicators

Indicates how many OFDM symbols per subframe are for PDCCH: 1, 2 or 3
symbols
The CFI is carried by 32 bits of information
16 RE Resource Elements distributed in frequency

Cell specific offset applied to distinguish from neighbour cells
(based on the Physical cell ID)
Sent in the first 3 symbols of the subframe
UE
eNodeB

PDCCH Resource Adjustment from PCFICH
First subframe (1ms) Second subframe (1ms)

12 subcarriers
Frequency
Time
Control region
Control region -
3 OFDM symbols
1 OFDM symbol
Indicated by PCFICH
PCFICH Structure
2 input bits are enough
to signal the PDCCH 4
size: 1, 2 or 3 symbols
2 bits Rate 1/16 32 bits 32 bits QPSK 16

Scrambling
block code modulation symbols
72 subcarriers
4
D.C.
One Resource Element

Group (REG) = 4 RE 4
PCFICH resource elements
Resource elements reserved for 4

reference symbols
Time

DL Transmission


eNodeB


PDCCH Design (1)
Challenge 1: Several PDCCHs could be transmitted in one

subframe
One PDCCH contains DCI = DL control information
DCI could indicate:
Upling scheduling grants for PUSCH
Downlink scheduling assignements for PDSCH
TPC command for PUSCH and PUCCH
How to distinguish between the different information on PDCCH?
Solution:??
Use several formats
UE
eNodeB

PDCCH Design (2)
Challenge 2: What is the size of one PDCCH?

One PDCCH contains DCI = DL control information
The DCI may have different size (depending on the information e.g.
scheduling or power control command different formats possible)
The number of bits for one PDCCH may change based on channel conditions:
UE at cell edge more bits per PDCCH
UE close to BTS less bits per PDCCH
Solution:??
Variable size for PDCCH
UE
eNodeB

PDCCH Design (3)
Challenge 3: What is the size of the overall PDCCH region?

PDCCH has variable size
The number of the PDCCHs depends on the cell Bandwidth (1.4 ... 20 MHz)
The number of PDCCHs depends on the number of UEs which are scheduled
in the subframe (1ms)
cell load
Solution:??
Variable size for the PDCCH region (1, 2 or 3 symbols)

Formats for Downlink Control Information
Format 0 - transmission of Format 1 transmission of Format 1a - compact signaling of

resource grants for the PUSCH resource assignments for single resource assignments for single
codeword PDSCH for MIMO codeword PDSCH transmissions
transmissions (transmission - allocating a dedicated
modes 1, 2 and 7 see details in preamble signature to a UE for
chapter 8) contention-free random access
Flag to differentiate between Resource allocation type Flag to differentiate between

Format 0 and Format 1A Format 0 and Format 1A
Resource block assignment
Resource block grant Flag to indicate that the
Modulation and coding scheme distributed mapping mode is used
Modulation and coding scheme for the PDSCH transmission
HARQ information (otherwise the allocation is a
HARQ information and contiguous set of physical
redundancy version Power control command for resource blocks)
Physical Uplink Control Channel
Power control command for (PUCCH). Resource block assignment
scheduled PUSCH
Modulation and coding scheme
Request for transmission of an
aperiodic CQI report HARQ information
Power control command for

PUCCH.

Formats for Downlink Control Information
Format 1B - compact signaling of Format 1C - very compact Format 1D -compact signaling of

resource assignments for PDSCH transmission of PDSCH resource assignments for PDSCH
transmissions using closed loop assignments (e.g. signaling paging transmissions using multi-user
precoding with rank-1 transmission messages and some broadcast MIMO (transmission mode 5).
(transmission mode 6). system information messages)
- PDSCH transmission
constrained to use QPSK
modulation.
same information as in Format 1a, Resource block assignment same as in Format 1B, but instead of
but with the addition of an indicator one of the bits of the precoding
of the precoding vector applied for Modulation and coding scheme vector indicators, there is a single bit
the PDSCH transmission. to indicate whether a power offset is
Redundancy version. applied to the data symbols.
This feature is needed to show
whether or not the transmission
power is shared between two UEs
Format 3/3A - transmission of

power control commands for
PUCCH and PUSCH with 2-bit
or 1-bit power adjustments
respectively.
contain individual power control
commands for a group of UEs.
Size of one PDCCH
PDCCH format id Number of CCE's Number of RE Number of PDCCH

groups bits
0 1 9 72
1 2 18 144
2 4 36 288
3 8 72 576
1 CCE (Control Channel Element) = 9 REs (Resource Elements)
The number of bits for one particular PDCCH may change based on channel
conditions:
1. UE with good DL channel quality (closed to Node-B) one CCE may be

enough
2. UE at the cell edge several CCEs up to 8 CCEs could be allocated

Size of one PDCCH Example 1 CCE = 9 REGs = 36 RE
PCFICH
PHICH Allocation for UE 1
PDCCH
UE 1
Frequency
Allocation for UE 2
Time
UE 2
CCE = Control Channel Elements
REG = Resource Elements Groups
RE = Resource Elements

Size of the PDCCH Region
The number of bits for resource assignment is dependent on the system

bandwidth
E.g. DCI format 1 has 47 bits for UL & DL 10 MHz
The number of PDCCHs depends on the number of UEs (cell load & number
of UEs scheduled in 1 ms)
Variable size of the PDCCH region

Signalled by PCFICH
(see next slide)
UE
eNodeB
Size of the PDCCH Region
Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 Subframe 5 Subframe 6
Frequency
PDCCH region
1,2,3 OFDM symbols
in the beginning
of the subframe
not allocated by
PCFICH, PHICH
Slot No. 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 .
Time
PDCCH Decoding (1/4)
Challenge 1: PDCCHs for one UE or for several UEs

PDCCH should send DCI intended for:
All the UEs in the cell (e.g. System info scheduling)
A particular UE (dedicated info)
How to distinguish between these cases??
Solution:??
PDCCH identification:
The bits sent on PDDCH could be scrambled with
specific info identity (like SI-RNTI for system information)
The bits on PDCCH could be scrambled with specific UE
identity
SI RNTI = System Information Radio Network Temporary Identity
Challenge 2: How can the UE find out where is it`s PDCCH?

2 options possible:
1. Node-B can place the PDCCH anywhere so that the UE should blindly
decode
Too many decoding attempts (especially for large system
Bandwidth)
2. Define for each UE a limited set of PDCCH (like a dedicated channel)
Limit the number of UEs which could be scheduled or increase the
overhead
Solution:??
compromise needed
UE
eNodeB

Solution:
UE should search Control Channel Candidates in a search space:

Dedicated search space (for only one UE)
Common search space (for several UEs)
The number of candidates dependes on the format used (0,1,2 or 3)

The size of the canditates is 1,2,4 or 8 CCEs (Control Channel Elements = 9
Resource Elements)
Overlap possible between dedicated spaces
See next slide

2 candidates having 8
CCEs each
PDCCH No. of CCEs No. of No. of 1 CCE
format candidates in candidates in
common dedicated Common search space Dedicated search space
UE 1 search space search space
(UE1) (UE1)
3 8 2 2
2 4 4 2
1 2 - 6
0 1 - 6
PDCCH No. of CCEs No. of No. of 32 CCEs = 1200 subcarriers (20MHz Bandwidth)
format candidates in candidates in
common dedicated Common search space Dedicated search space
UE 2 search space search space
(UE2) (UE2)
3 8 2 2
2 4 4 2
1 2 - 6
0 1 - 6
DL Transmission


eNodeB


PDSCH Physical Downlink Shared Channel
Contain the actual user data from DL-SCH
Use the available Resource Elements
Allocation is signalled by PDCCH eNodeB

UE
Also used for:

SIBs (System Information Block) of the system information
Paging
PDCCH acting like a Paging Indicator Channel in UMTS
(see next slide)

PDSCH Physical Downlink Shared Channel
Subframe 0 Subframe 1 Subframe 2 Subframe 3 Subframe 4 ..
SSS Frequency
PSS
PBCH
PCFICH
PHICH
PDCCH
Reference signals
PDSCH UE1
Slot No. 0 1 2 3 4 5 6 7 8 9 .
PDSCH UE2
Time
System Information
System Information ( )
MIB UE
Sent on PBCH!
40 ms repetition
MIB: Master Information Block eNodeB

SIB: System Information Block
SFN: System Frame Number SIB 1 Fixed repetion 80 ms
First transmission in subframe #5 for
which SFN mod 8 = 0
Indicates the allocation of the other
SIBs 2...11
SIB 2 SIB 3 SIB 4 SIB 11

Special Use of PDSCH System Information Blocks
- Cell access related information (PLMN, cell identity, Tracking Area code etc.)
- Information for cell selection
SIB 1 - TDD configuration
- Information about time-domain scheduling of the remaining SIBs
SIB 2 - Access barring information
- Radio resource configuration of common channels (e.g. PCCH)
- Frequency information (UL UARFCN, uplink bandwidth)
SIB 3 - Cell-reselection information that is common for intra-frequency, inter-frequency

and/or inter-RAT cell re-selection.
SIB 4 - Neighbor cell related information only for intra-frequency cell re-selection.
SIB 5 - Inter-frequency cell re-selection like E-UTRAN related information

- Inter-frequency neighboring cell related information
SIB 6 - UTRA FDD and TDD frequency information for cell reselection
SIB 7 - Information relevant only for cell re-selection to the GERAN
SIB 8 - Information relevant only for cell re-selection to the cdma2000 system.
SIB 9 - Home eNodeB identifier
SIB 10 - Earthquake and Tsunami Warning System (ETWS) primary notification
SIB 11 - Earthquake and Tsunami Warning System (ETWS) secondary notification

Paging in LTE FDD Mode
Used for network originated services (e.g. VoIP)
The UE is sleeping most of the time to save battery power
The UE wakes up periodically to listen to the PDCCH to see if there is some

indication for paging
PDCCH acting like the Paging Indicator Channel in UMTS
How often the UE wakes-up is sent to the UE in SIB 2
If the UE is identifying on the PDCCH a group identity used for paging (P-RNTI)
then it wakes-up and looking for paging
The actual paging channel PCH is sent on PDSCH

An UE identity sent (S-TMSI)

Resource Allocation for PDSCH
Challenge:
How to signal on PDCCH (Physical Downlink Control Channel) the allocation of
the resource blocks on the PDSCH (containing DL-SCH)?
Possible solution:
Include a bitmap with the size equal to the number of RBs(Resource Blocks)
that have to be allocated
Advantage:
Arbitrary combinations of RBs for allocation are possible
Disadvantage:
Very large overhead (number of bits required for signaling)
E.g.: 100 RBs -> 100 bits !!
Solution: Compromise needed

Resource Blocks allocation type 0,1 and 2
Resource allocation for PDSCH
Resource allocation type 0:

Principle:
Do not point individual RBs (Resource Bloks) -> point groups of RBs (RBG)
A bitmap indicates which group of RBs is scheduled in the TTI
The number of RBs per group noted with P - is depending on the bandwidth (see
the table)
Advantage: point groups of RBs
therefore reduce the signaling
Disadvantage: scheduling granularity
is reduced (single resource blocks
cannot be allocated for bandwith bigger
than 10 Resource Blocks, i.e. more than
3 MHz)
Example: see next slide

Resource Allocation Type 0: Example
Example: 50 RBs are grouped into:

17 RBGs:16 RBGs of 3 RBs + 1 RBG of 2 RBs.
RBG = Resource Block Group
RB = Resource Block
The bitmap 0 -> the group is not allocated, 1 the group is allocated
1 1 1 0 0 0 0 0 1 0 1 1 1 0 0 1 1
The bitmap

Resource Allocation Type 1 and 2

Principle:
The resource blocks are divided in subsets
A bit map is defined for every subset
Every subset may also have a specific allocation shift
Advantage: every single resource block may be addressed
Disadvantage: additional information about subsets have to be sent -> higher
signaling than allocation type 0
Example: see next slide
Principle:
Contiguous allocation: the resource allocation is indicated as start position (resource
block) and length of resource blocks allocation
Advantage: less bits required for signaling
Disadvantage: only frequency-contiguous allocations possible
Resource Allocation Type 1: Example
Example: 50 RBs are organised into 3 RBG subsets of 18, 17 and 15 RRBs.
RBG = Resource Block Group
RB = Resource Block
Offset
1 0 1 0 0 0 0 0 1 0 1 1 1 0 0 1 1
2 bits showing
the number of The bitmap
Subsets:
3 subsets (the
second subset
in this example)
Offset 0
Offset 1

HARQ: 8 stop-and-wait processes (UL & DL)
UL: synchronous
DL: asynchronous

HARQ Soft Combining Principle
Redundancy versions
0 1 2 3 DPCCH
DPSCH
NACK
Tx


Phyisical Resource
Cell Search
Initial Access

Upper Layers
RLC
CCCH
DCCH
DTCH
MAC
UL-SCH
RACH
UCI
PHY
PUCCH
PRACH
PUSCH
DRS
SRS
Air interface

UL Transmission
scheduling)
Like DPCCH in UMTS)
eNodeB


Differences from DL Transmission (1/2)
Questions:
What are the main differences

from the DL transmission ??
Why? UE
eNodeB
Answers (1/2):
No UL signalling indicating the transport format (like on
PDCCH)
This is because the UE always follows the Node-B
scheduling
eNode-B has exact knowledge of the UL transport format
Differences from DL Transmission (2/2)
Answers (2/2):
UL L1/L2 signalling is divided:
Control signalling in the absence of the UL user data -> sent on PUCCH
(Physical UL Control Channel)
Control signalling in the presence of UL user data -> sent on PUSCH
(Physical UL Shared Channel)
Not possible to send PUCCH and PUSCH at the same time
This is because UL SC-FDMA is using single carrier

To separate PUCCH and PUSCH in frequency -> destroy the single carrier
feature
To separate PUCCH and PUSCH in time -> impact on coverage (low
coverage for both PUCCH and PUSCH)

PUCCH and PUSCH Multiplexing
PUCCH
Total UL Bandwith
PUSCH
Frequency
12 subcarriers
PUCCH
1 subframe = 1ms
Time

UL Transmission
scheduling)
Like DPCCH in UMTS)
eNodeB


PUCCH Design (1)
Challenge 1: Where should be PUCCH placed? Why?

Achieve frequency diversity by using frequency hopping from one edge of
the bandwidth to the other edge
PUCCH as a kind of guard band for the UL transmission (defining the
maximum UL Transmission Bandwith)
Maximize the available PUSCH region for user data
Solution:??
Placed at edge of the UL Bandwidth
(see next slide)

UE
eNodeB

PUCCH Design (1)
PUCCH
Total UL Bandwith
PUSCH
Frequency
12 subcarriers
PUCCH
1 subframe = 1ms

PUCCH Design (2)
Challenge 2: Distinguish between different information on

PUCCH
PUCCH contains UCI = UL Control Information
UCI could indicate:
Scheduling requests
HARQ ACK/NACK for DL transmission
How to distinguish between the different information on PUCCH?
Solution:??
Use several formats
UE
eNodeB
(See next slide)

PUCCH Formats
PUCCH Modulation scheme Number of bits per Type of information

format subframe
1 N/A N/A Scheduling Request (SR)
1a BPSK 1 ACK/ NACK
1b QPSK 2 ACK/ NACK
2 QPSK 20 CQI
2a QPSK+BPSK 21 CQI + 1 bit ACK/ NACK
2b QPSK+BPSK 22 CQI + 2 bits ACK/ NACK
UE
eNodeB

Scheduling Request Indicator (SRI) on PUCCH
UE eNB
Random access like
1 Scheduling Request Indicator
contention based
asynchronous mechanism
Uplink Scheduling Grant 2
Used for UEs in
3 Scheduling Request + Data connected mode
Challenge:
The Node-B cannot know when the UE like to sent one scheduling request
The resource allocation could not be forseen
Solution -> use a contention based mechanism
Procedure:
1. UE transmits a SRI (Scheduling Request Indicator)
2. eNodeB answers with an UL Scheduling Grant for a minimum assignment
(e.g. 1 Resource Block)
3. UE sends the actual Scheduling Request and possibly some data
ACK/NACK on PUCCH
The ACK/ NACK is used to acknowledge the Downlink Transport Blocks on

the PDSCH
ACK/ NACK frequency and resource allocation could be foreseen based on
the Node-B DL scheduling decisions (big resource allocation on PDSCH ->
high frequency probability for ACK/NACK)
If nothing is received by the UE on PDSCH -> nothing is transmitted (DTX =
Discontinuous Transmission)
ACK or NACK as information is using only 1 bit transmitted in 1 ms
(subframe)
This bit could be either BPSK or QPSK modulated
ACK could be sent using:
Format 1a/1b standalone (better
PUCCH coverage with this option)
Format 2a/ 2b together with CQI
UE
eNodeB

CQI on PUCCH
One CQI has 10 bits (transmitted in one subframe = 1ms)

QPSK is used -> 20 bits in total are sent
PUCCH format 1 has only 2 bits maximum -> PUCCH format 2 should be
used to transmit the CQI
CQI could be transmitted:

Standalone (format 2)
Together with ACK/NACK (format 2a/2b)
UE
eNodeB

Mapping of PUCCH Formats to the Physical Resources
The logical resources are noted with m

as can be seen on the figure
nPRB N RB
UL
1 m 1 m0
m3 m2 m = 0 and 1 may contain formats 2/2a or
2b which are placed at the outermost
resource blocks of the system bandwidth
m = 2 and 3 may contain formats 1/1a or

1b
m2 m3
nPRB 0 m0 m 1 It can be seen that PUCCH defines the UL
system bandwidth (in the figure the
system bandwidth is shown as the
One subframe maximum number of resource blocks)

Mapping of PUCCH Formats to the Physical Resources
Format 2/2a/2b
Format 2/2a/2b Format 2/2a/2b
PUCCH
Bandwith
Total UL
PUSCH
Frequency
12 subcarriers
PUCCH
1 subframe = 1ms
Time

SRI/ ACK/ CQI Multiplexed on PUCCH
Challenge: There are scenarios in which the UE should sent SRI or ACK or
CQI at the same time
Solution: Multiplexing or dropping signalling data
Possible Scenarios for multiplexing
1. SRI and CQI simultaneously

The scheduling request indicator SRI has higher priority -> only SRI will
be sent so the CQI is dropped
2. SRI and ACK/NACK and CQI simultaneously
The HARQ ACK will be sent on the SRI resources and the CQI will be
dropped
3. ACK/NACK and CQI simultaneously
It is possible to multiplex them together on the same subframe (1 ms)

SRI/ ACK/ CQI Multiplexed on PUCCH
PUCCH
Bandwith
Total UL
PUSCH
Frequency
12 subcarriers
PUCCH
1 subframe = 1ms
Time
ACK ACK DRS DRS DRS ACK ACK ACK ACK DRS DRS DRS ACK ACK
CQI DRS CQI CQI CQI DRS CQI CQI DRS CQI CQI CQI DRS CQI
0 1 2 3 4 5 6 0 1 2 3 4 5 6
ACK = Acknowledgment
Simbol number (normal CP)
DRS = Demodulation Reference Signals
PUCCH Design (3)
Challenge 3: What is the size in frequency of the overall PUCCH

region?
The size of the overall PUCCH region is dependent on:
1. For CQI (periodic) the resources are reserved in advance and depend on
the number of UL scheduled UEs
2. For ACK/ NACK the number of resources is directly related with the size of
the Downlink PDCCH region (1,2,3 symbols) which in turn is dependent on
the number of the DL scheduled users
3. For SRI Scheduling Request Indicator the ressources are allocated on the
need basis
Solution:??
Variable dependening on available bandwith and amount of
signalling

Size in Frequency of the Overall PUCCH Region
The overal number of the Resource Blocks used in UL is configured by

higher layer parameters
The UE knows the parameters from the system information
Main parameters used:
1. Maximum Resource Blocks used in one time slot (0,5 ms)

The actual size is dependent on the cell load (scheduling decision)
2. Number of Resource Blocks reserved for CQI periodic reporting -
3. Number of cyclic shifts reserved for the formats 1/1a/1b

This parameter is used with shared PUCCH resource blocks between
formats 1/1a/1b and 2/2a/2b
PUCCH Design (4)
Challenge 4: The resource allocation for PUCCH is too big for

only one UE
The resource allocation for one user = 1 resource block (12 subcarriers in 1
ms)
This may be too big for the transmission of the signalling associated to only
one UE (ACK/ Resource Request/ CQI)
Multiple UEs could be multiplexed on the same resource block
This in turn brings a new challenge: How can multiple terminals share the
same PUCCH resource block??
Solution:??
Multiple UEs may share the same
resource block UE
eNodeB
(see next slide)

Multiplexing of UEs on PUCCH
How to separate multiple UEs on PUCCH ??
Solution?
UE1 UE3
UE2
1. FDM frequency division multiplexing

This is because one UE may take one resource block and other users may take
different resource blocks
Naturally happening because of the PUCCH structure
2. CDM code division multiplexing

Using CAZAC = Constant Amplitude Zero Autocorrelation Codes
Orthogonal codes (cell specific length 12 sequence used)
Used to multiplex multiple users on the same resource block
Code orthogonality may be affected by the near-far problem
UL Transmission
scheduling)
Like DPCCH in UMTS)
eNodeB


PUSCH Physical Uplink Shared Channel
Content:
User data from UL-SCH
L1/L2 control information:
ACK/NACK for HARQ
CQI UE
eNodeB
Precoding Matrix Indicator (PMI)
Rank Indicator (RI)
Challenge: How to multiplex UL user data and different control

fields?
(see next slide)

1ms subframe
PUSCH Slot 0 Slot 1
UL-SCH
DFT for SC-FDMA

CQI/PMI
16/64QAM
36 subcarriers
QPSK,
MUX
RI
ACK
CQI = Channel Quality Indication

PMI = Precoding Matrix Indicator
RI = Rank Indicator 0 1 2 3 4 5 6 0 1 2 3 4 5 6
ACK = Acknowledgment used for HARQ SC-FDMA symbols
PUSCH CQI/PMI RI ACK PUSCH RS

UL Transmission
scheduling)
Like DPCCH in UMTS)
eNodeB


Uplink Reference Signals
Associated with transmission

of uplink data on PUSCH or
Demodulation PUCCH
Reference Used for channel estimation
for coherent detection and
Signals demodulation (both PUCCH
and PUSCH)
UE
Not associated with UL data

Sounding transmissions eNodeB
Used for estimation of the UL
Reference channel quality to enable the
Signals channel dependent scheduling

Demodulation Reference Signals DRS
Associated with PUCCH and PUSCH data transmission

Basically the same structure for both PUCCH DRS and PUSCH DRS
The main differences are the allocated bandwidth and the timing
Used for channel estimation:

For coherent detection and demodulation
Power control in UL
Timing estimation
UE
eNodeB
Like DPCCH (Dedicated Physical Control Channel) in UL in UMTS

Design of Demodulation Reference Signals DRS (1)
Challenge 1: Is it possibile to use the same structure for the reference signals
like in DL?
Remember the grid-like structure of the reference signals in the DL
But in UL there are some other issues to consider:
The variations in UL transmission power should be kept as low as possibile
Maximise the power available for data transmission (for coverage reasons)
Therefore:
It is not suitable to multiplex in time and frequency the user data and the
reference signals
Some SC-FDMA symbols will be reserved for the transmission of the UL
reference signals
Solution:??
In UL the reference signals are time multiplexed with the data
transmission of the same terminal

Challenge 2: What should be the position of the DRS?
Time domain:
For PUCCH: the number and the exact position of the DRS is dependent on
the format (1/1a/1b or 2/2a/2b) used
For PUSCH: every 4th symbol in every time
slot (the 3rd symbol for the extended cyclic
prefix)
Frequency domain:
DRS has the same bandwidth like
the UL transmission of the terminal
(see next slide)

Uplink DRS Multiplexed with PUSCH
Subframe 0 Subframe 1
Slot 1 Slot 2
No DFT
spreading !
0
0
X0RS
OFDM Modulator
Frequency-domain
36 Subcarriers
X1RS
reference signal
Sequence
M = sequence length
XM-1RS
0
0
PUSCH transmission
SC-FDMA symbol
number
0 1 2 3 4 5 6 0 1 2 3 4 5 6
Demodulation reference signal
Normal CP

Uplink DRS Multiplexed with PUCCH
PUCCH
Bandwith
Total UL
PUSCH
Frequency
12 subcarriers
PUCCH
1 subframe = 1ms
Time
ACK ACK DRS DRS DRS ACK ACK ACK ACK DRS DRS DRS ACK ACK
CQI DRS CQI CQI CQI DRS CQI CQI DRS CQI CQI CQI DRS CQI
0 1 2 3 4 5 6 0 1 2 3 4 5 6
ACK = Acknowledgment
Simbol number (normal CP)
DRS = Demodulation Reference Signals
Challenge 3: What should be the length of the DRS?

Since the DRS is sent on the UL transmission bandwidth then the length
should be variable
The minimum length should be 12 (minimum number of subcarriers in one
resource block)
The length should be variable and support all the allowed number of resource
blocks in UL
There are sequences of different length:
For BW = 12, 24, 60 subcarriers
For BW > 60 subcarriers
Solution:?? UE
variable, multiple of 12
eNodeB

Challenge 4: How many sequences for DRS?

As many DRS sequences as possibile for every length to make as easy as
possibile their allocation (network planning)
One limitation is commimg from the usage of the Zadoff-Chu sequences: the
number of sequences should be an integer number which should be a
prime number relative to the sequence length
Example: for a sequence of length 36 there are 31 sequences (prime
number)
For every length at least 30 sequences should be available (for bandwith
bigger than 72 subcarriers more sequences could be available)
Solution:??
at least 30 sequences available for every length

Challenge 5: How to separate the UEs in the same cell?

Please note that in UL the transmission on PUSCH is orthogonal so normally
there is no need to separate the DRS
coming from different terminals on the same cell
Scenarios where separation is needed:
1. UEs within the same cell simultaneously transmit
on the uplink using the same frequency resource
UE1 UE3
interferences in PUCCH transmissions UE2
2. Uplink multi-user MIMO
Solution:??
apply different cyclic shifts to the same basic reference signal
sequence
Cyclic Shifted Reference Signal Sequences
The cyclic time shift is providing

0
orthogonal sequences !
ej0 0 UE specific cyclic shifts
X0RS
OFDM Modulator
Basic The shift is in time domain
reference X1RS
Solve intra-cell interference!
signal
Sequence
ej1 The parameters for the shift could be
of length learned from the system information
M XM-1RS
ej(M-1) 0
0
Cyclic shifted reference Basic sequence

signal sequences
- = k/6 (phase rotation
parameter), where k ranges Cyclic shift of 1
from 0 to 11
up to 12 orthogonal
reference signals could be Cyclic shift of 2
generated
Challenge 6: How to separate the UEs in neighbour cells?

Simultaneous UL allocation in different cells may have the same bandwidth
because of the independent allocation
This complicates the optimisation of the cross-correlation between cells
eNodeB 1 eNodeB 2
Sequence group hopping
UE1 UE33 UE4 UE63

UE2 UE5 Sequence group planning
Solution: Cyclic shift hopping

based on sequence groups
Sequence hopping

Parameters for the DRS Planning
1.Sequence length (12, 24, )

Given by the UL allocation -> dependent on the allocated bandwidth
For PUCCH is 12 or 24 typically
For PUSCH could be much higher
2. Cyclic shift: 12 options

The cyclic shift in time of one sequence is generating another orthogonal sequence
-> UE and cell specific parameter
In practice 6 or more shifts could be used to avoid detection errors
3. The base sequence: 2 options

Multiple sequences could be derived from the base sequence (with the cyclic shift)
One base sequence per group if BW < 60 subcarriers
2 base sequences per group if BW > 60 subcarriers
-> cell specific parameter
4. The sequence group: 30 options

This is the number of sequences available for every sequence length
-> cell specific parameter

Cyclic Shift Hopping
A cell specific cyclic shift is applied on top of the UE specific cyclic shift
Always used
Several possibilities -> different hopping pattern (based on the cell id 1..504)
PUSCH -> cyclic shift in every slot
PUCCH -> cyclic shift in every symbol

Sequence Group Hopping
A group hopping pattern defined
Same group hopping pattern to 30 cells in a cluster
30 groups
504 cell IDs
504/30 = 17 sequence groups hopping patterns
Minimise the probability to use the same group at the same time in 2
neighbour cells

Sequence Group Planning
Different colours Different root

sequences
D1, D2, D3 Different cyclic

shifts of one root sequence

Sequence Hopping
Hopping between the 2 base sequences
Only for resource allocation with Bandwidth > 60 subcarriers
Could be switched on/off
Used when the sequence group hopping is off

UL Transmission
scheduling)
Like DPCCH in UMTS)
eNodeB


Uplink Reference Signals
Associated with transmission

of uplink data on PUSCH or
Demodulation PUCCH
Reference Used for channel estimation
for coherent detection and
Signals demodulation (both PUCCH
and PUSCH)
UE
Not associated with UL data

Sounding transmissions eNodeB
Used for estimation of the UL
Reference channel quality to enable the
Signals channel dependent scheduling

Sounding Reference Signals SRS
The SRS can be used for:
initial Modulation and Coding Scheme (MCS) selection
initial power control for data transmissions
timing advance
Frequency dependent scheduling for the UL
UE
eNodeB

Sounding Reference Signals
Why Demodulation References Signals cannot be used instead

of SRS?
The demodulation reference signals are only sent on the transmitted

bandwidth!
We need an estimation of the whole spectrum so the SRS may cover a

different, often larger, frequency span than for example PUSCH (if they are
transmitted together).
The SRS is not necessarily transmitted together with any physical channel

Sounding Reference Signals Structure
Subframe 0
Slot 0 Slot 1
No DFT
spreading !
0
0
Cyclic extension X0SRS
OFDM Modulator
of Zadoff-Chu 0
X1SRS
36 Subcarriers
sequence of 0
prime length M
(frequency 0
domain) XM-1SRS
0
0
PUSCH transmission
Demodulation reference signal

SC-FDMA symbol
Sounding reference signal number 0 1 2 3 4 5 6 0 1 2 3 4 5 6
Normal CP
SRS Subframe Configuration and Position
Subframe 0
Slot 1 Slot 2
Subframe configuration
The subframes in which SRS are PUSCH DM RS

transmitted by any UE within the cell
are indicated by cell-specific
broadcast signalling.
36 Subcarriers
Position
The SRS transmissions are always in

the last SC-FDMA symbol in the
configured subframes SRS
0 1 2 3 4 5 6 0 1 2 3 4 5 6
Normal CP
Duration and Periodicity of SRS Transmissions
2 ms (SRS minimum
transmission periodicity)
Subframe 0 Subframe 1 Subframe 2
The eNodeB in LTE may either
request:
an individual SRS transmission from

a UE
16 RBs
periodically transmission from a UE
If periodic SRS transmissions are

configured for a UE, the periodicity
may be any of 2, 5, 10, 20, 40, 80, 160
or 320 ms

SRS Symbol Structure
Comb-like
spectrum
InterleavedFDMA (IFDMA) is used in

Interleaved FDMA
the SRS SCFDMA symbol, with a
Repetition Factor (RPF) of 2.
0
0
implies that the signal occupies X0SRS
OFDM Modulator
every 2nd subcarrier within the 0
X1SRS
allocated sounding bandwidth with a 0
comb-like spectrum
0
XM-1SRS
a UE is assigned, as part of its 0
0
configurable SRS parameters, the
transmissionComb index (0 or 1) on
which to transmit the SRS.

SRS Bandwidths
Challenges
UE far from eNodeB cannot increase its transmit power to maintain the
transmission across the full bandwidth
Full bandwidth transmission limits the number of simultaneous UEs whose
channels can be sounded, due to the limited number of cyclic time shifts
Solution?
up to 4 SRS bandwidths can be simultaneously supported in LTE depending
on the system bandwidth improve the SNR and support a larger number
of SRS
8 sets of four SRS bandwidths are defined for each possible system
bandwidth provide flexibility with the values for the SRS bandwidths

SRS Bandwidths
Wideband SRS Transmission Narrowband SRS Transmission

(Non Frequency hopping SRS ) (Frequency hopping SRS )
System bandwidths 4060 RBs.
Subframe 0Subframe 1Subframe 2 Subframe 0Subframe 1Subframe 2 SRS BW SRSB SRS SRS SRS
config. W0 BW 1 BW 2 BW 3
0 48 24 12 4
More 1 48 16 8 4
wideband
16 RBs
SRS 2 40 20 4 4
bandwidth
3 36 12 4 4
= 4 RBs 3
= 12 RBs
4 32 16 8 4
5 24 4 4 4
6 20 4 4 4
7 16 4 4 4
Minimum Narow
SRS bandwidth
Sounding reference signal
= 4 RBs
Multiplexing of SRS
Challenge: How can be transmitted simultaneous

SRS from multiple UEs using the same RBs?
UE1 UE3
Solution: UE2
using different cyclic time shifts of the same base sequence

to achieve orthogonal separation
- multiple UEs share the same RB and the same offset of the comb
- eight (evenly-spaced) cyclic time shifts per SRS-comb are supported
with the cyclic shift being configured individually for each UE
- reference signals must span the same frequency band
Through frequency multiplexing by assigning different UEs to
different frequency shifts or combs .
- Transmission doesnt cover identical frequency bands

Multiplexing of SRS
Frequency multiplexing Cyclic time shifts

UE1 SRS UE2 SRS multiplexing
UE3 SRS UE4 SRS
UE1
phase rotation 1
UE2
phase rotation 2
36 Subcarriers
UE3
phase rotation 3
UE4
phase rotation 4
Slot 1 36 Subcarriers
Slot 0
UL Transmission
scheduling)
Like DPCCH in UMTS)
eNodeB


PHICH Structure
PHICH carries the HARQ ACK/NACK, which
indicates whether the eNodeB has correctly
received a transmission on the PUSCH PCFICH resource elements
HARQ Indicator 1
Reference symbols
PHICH resource elements

Repetition coding 1 1 1
Walsh
+1 -1 +1 -1 +1 -1 +1 -1 +1 -1 +1 -1
spreading
D.C.
72 subcarriers
PHICH Physical HARQ Indicator Channel
How to differentiate different cells??

Cell specific scrambling applied
How to differentiate the UEs?

PHICH groups (multiple PHICH on the same resource elements)
Different PHICH in a PHICH group are separated using complex Walsh
sequences
Walsh sequence length is 4 (2 for extended CP)
BPSK modulation is used for PHICH
Thus an individual PHICH can be uniquely represented by the number of the
PHICH group, the number of the orthogonal sequence within the group, and
information whether the I or the Q branch is used
The number of PHICH in a group is thus up to twice the sequence length
(max 8 UEs receiving their acknowledgements on the same set of downlink
resource elements)
Subframe configuration
an uplink transport block received in subframe n should be acknowledged on
the PHICH in subframe n + 4.
Position in time
PHICH is transmitted in the first OFDM symbol only of each subframe
allows UE to attempt to decode the PHICH even if it failed decoding of the
PCFICH.
To improve the coverage it is possible to semi-statically configure a PHICH
duration of three OFDM symbols
Position in frequency
Each PHICH group is mapped to three resource-element groups, separated by
approximately one-third of the downlink cell bandwidth obtain good
frequency diversity.
Challenge: How can I know what is my PHICH group and my

PHICH inside the group??
Solution:
PHICH group number indicated in PBCH
PHICH inside the group based on index
1 to 1 mapping PUSCH index PHICH index
PUSCH index = the index of the lowest UL resource block that has
been used for the UL transmission
In the case of uplink multi-user MIMO the same cyclic shift index as for
demodulation reference signals is used to shift the PHICH allocations in
the downlink each UE will receive its ACK or NACK on a different PHICH.


Phyisical Resource
Cell Search
Initial Access

FDD and TDD Modes
FDD and TDD modes Harmonisation FDD and TDD modes

(commonalities) differences
FDD and TDD mode included FDD developed in the paired 3GPP
together in the same spectrum
specification
TDD developed in the unpaired
Same radio interface schemes 3GPP spectrum
for both uplink and downlink
Small differences in the physical
Same subframe formats channels design
Same network architecture Different frame formats
Same air interface protocols FDD mode has commonalities with

3G UMTS
Same physical channels
procedures TDD mode has commonalities with
TD-SCDMA (developed in China)
Most physical channels and

procedures are the same in FDD
and TDD. Only the differences are
177 Nokia Siemens Networks shown in this section
FDD and TDD Modes Differences
Question:
What are the main differences between the FDD and TDD mode physical
channels design?
Answers:
1. TDD needs specific cell synchronization due to potential misalignment of
the subframes
2. Channel reciprocity could be used in TDD mode
3. Asymmetric UL/DL Capacity allocation is possible in TDD to meet the
traffic characteristics of the cell
4. Small difference in the design of the design of the physical channels
coming mostly from different frame structure
These differences are discussed in this section

TDD Cell Synchronization (1/3)
Interference scenario
Cell 1 Cell 2
UE2
eNodeB1 UE1 eNodeB2
eNodeB1 Tx, UE1 - Rx eNodeB1 Rx, UE1 - Tx Cell 1
Interference from UE 1 to UE 2 and viceversa, due to the misalignment

between subframes
Interference is severe, especially if UE1 and UE2 are close to each other
Solution: synchronize all DL & UL subframes in cells among the network
They must have the same time reference

Common GPS signal
Cell 1 Cell 2
UE2
eNodeB1 UE1 eNodeB2

E-UTRA standard provides several means of time synchronization between

cells:
Same frame configuration (06) is used in all cells among the network
Frame structure is chosen so that interference between LTE systems and

TD-SCDMA is avoided
Carrier using both TD-SCDMA and LTE TDD can avoid interference between
systems

Reciprocity in TDD (1/3)
FDD channel response in frequency is different in UL and DL, due to the
different occupied bands
Downlink Uplink band

band Same indexed subcarriers may experience
totally different channel conditions
TDD radio channel is reciprocal, i.e. DL & UL experience the same channel
response, since they occupy the same band
Downlink Uplink band

band Same indexed subcarriers experience
identical channel conditions
Rceiprocity in TDD (2/3)
How can we make use of reciprocity?

Use UL measurements in order to evaluate DL channel conditions!
If reciprocity is assumed, UL and DL measurements should be the
same
Save resources & time needed for sending DL feedback!
Sending feedback asks for some latency measurement results might
be obsolete, especially if channel is mobile.
1 subframe Channel has
Channel already changed
frequency
response
Measurement Results are Results are Results are

is done sent decoded taken into
account

Reciprocity in TDD (3/3)
Use feedback for:
- Downlink scheduling
- Measure channel over uplink for a specific UE
- Identify good subcarriers and bad subcarriers
- Use good subcarriers with high SNR to schedule over downlink
Low SNR Bad subcarriers High SNR Good subcarriers

Do not use for DL scheduling May use for DL scheduling
- Modulation and rate adaptation
- Use DL modulation and coding suitable for link conditions, as measured over uplink
- MIMO precoding
- Use precoding matrix / codebook according to feedback measured over uplink
Usage of Reciprocity (1/2)
Reciprocity however is limited for scheduling and adaptation.
Channel response is not the only criteria to take into account.
Interference may be different over UL and DL
SNR may be degraded by two factors:

- Fading over the channel
- This is almost the same for UL and DL => reciprocity can be used in
scheduling and adaptation.
- Interference
- This is likely to be different for DL and UL.
Reciprocity in scheduling can be used only in interference-limited scenarios.

Usage of Reciprocity (2/2)
Closed-loop MIMO precoding takes only the channel into account..
Reciprocity can be used.
Precoding in FDD over downlink:
- UE receiver measures the channel over downlink
- UE computes the optimum precoding matrix
- UE sends the feedback to the eNodeB, including optimum precoding

matrix, in PUCCH
- eNodeB uses this feedback as a recommendation for its next

transmission
Cell Search TDD mode


UE
like CPICH in UMTS)
eNodeB
configuration)

Initial Cell Search in FDD (reminder)
FDD positioning of synchronization signals (reminder)

PSS detection
Subframe 1 or 6
Slot 0 Slot 1
Slot timing
PSS => PHY CELL ID
SSS detection
Cyclic prefix
length detection
Subframe 1 or 6
PSS- Prymary Synchronisation Signal

Frame timing
SSS- Secondary Synchronisation Signal
SSS => Cell ID + subframe (1 or 6)

Initial Search in TDD (1/2)
UEs must also blindly detect if system uses TDD or FDD

Information can be hidden in SSS without introducing new sequences
Distance between SSS and PSS in the frame is varied according to
duplexing method
1 symbol for FDD and 3 symbols for TDD
4 positions to check for SSS after PSS detection
Start of detected PSS
3 long symbols = 249.9us
2 short symbols + 1 special symbol = 214.5us
1 long symbol = 83.3us
1 short symbol = 71.3us
TDD with short CP FDD with short CP
TDD with extended CP FDD with extended CP

Initial Search in TDD (2/2)
SSS is the one placed at the slot boundary, not PSS

Slot timing is achieved along with frame timing, after decoding SSS
1 frame = 10ms
0 1 2 3 4 5 6 7 8 9
Coherent detection of
SSS assumes channel
S does not vary too much
P
S between SSS and PSS
S
S (3 symbols)
S
DwPTS: Downlink Pilot time Slot

Slot 1 Slot 0
PSS is always placed in the special switching subframe, within DwPTS

Initial Access
8. PRACH Preamble

C-RNTI)

UE
C-RNTI,
eNodeB

C-RNTI & TMSI)

Random Access Channel (1/3)
There is no major difference between RACH in FDD and TDD, except for a
minor addition.
Remember that RACH allocation for FDD includes a GP (Guard Period) to
accommodate RTD (Round Trip Delay)
RACH preamble GP Close UEs
GP RACH preamble UEs at the cell edge
RACH allocation start

GP is wasted bandwidth and can go up to 700us (!) for cell radius of 100km.
In FDD, only one RACH allocation per frame is allowed
TDD already has a GP in the special frames used for Tx/Rx switching which
is supposed to accommodate RTD
We can include this GP in a RACH allocation!
In UpPTS, a Short RACH (S-RACH) can be scheduled, making use of the
already existent GP.
S-RACH has the length of the UpPTS, i.e. 2 symbols, 157us (usual
RACH has 800us or 1600us)
Suitable for small cells (< 1.5km)
DwPTS GP UpPTS
RACH allocation
RACH 0
RACH 1
GP Max 6 RACH
DwPTS: Downlink Pilot time Slot channels
UpPSS: Uplink Pilot Time Slot RACH 5
UpPTS = 2 symbols
Conclusions
FDD frames can have up to 1 RACH channel per frame, in which UEs
can transmit one of 4 possible RACH prembles
TDD frames can have up to 6 RACH channels per frame, either long
RACH preambles or S-RACH preambles sent in UpPTS
S-RACH can cover small cells due to small CP (max. 1.5km), while
RACHs cover cells up to 100km
RACH allocation in TDD systems is: time first, then frequency
Subframe 0 1 2 3 4 5 6 7 8 9
RACH 0 RACH 1 RACH 2 RACH 0 RACH 1 RACH 2
RACH 3 RACH 4 RACH 3 RACH 4

DL Dransmission


UE
eNodeB
(user data transmission of the system
information and/or paging)

Broadcast Channel (BCH)
Primary BCH (PBCH) is sent just as in FDD case.

Dynamic BCH (DBCH) is sent as in FDD case, but it is decoded differently
SIB 1 in DBCH specifies DL/UL ratio (i.e. Frame Configuration: 06).
However, UE cannot decode DBCH unless it already knows its position in
frame.
Position in frame depends on Frame Configuration so which comes
first?
1. Assume each of the 3
DBCH possible values for CCH size
CCH size
2. Try to decode DBCH
3. DBCH has been correctly
Frame decoded
Configuration => frame configuration

Paging in TDD
PCH is mapped onto PDSCH physical channel
There is no change in concept versus FDD
Only different frames in which paging can be done
Subframe 0 1 2 3 4 5 6 7 8 9
FDD
Subframe 0 1 2 3 4 5 6 7 8 9
TDD
DwPTS: Downlink Pilot time Slot Special frame -> Potential special frame ->
UpPSS: Uplink Pilot Time Slot PDCCH in DwPTS PDCCH in DwPTS
UL Transmission
scheduling)
Like DPCCH in UMTS)
eNodeB


Sounding Reference Signal SRS
In FDD
SRS always are present in the last symbol of the subframe
In TDD
Same concept last symbol of specially configured subframes
In special switching subframes, no data are transmitted
Control resources in UpPTS can be used for SRS as well
These are the primary resources for TDD SRS
SRS is mandatory for TDD (more sensitive to interference)
RACH channel
RACH channel
GP
DwPTS: Downlink Pilot time Slot
SRS
UpPTS = 2 symbols

07 - LTE Physical Channels and Procedures - v04

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

07 - LTE Physical Channels and Procedures - v04

Diunggah oleh

Hak Cipta:

Format Tersedia

LTE Physical Channels and Procedures

LTE Air Interface Course

1 Nokia Siemens Networks

Layer and Channels Relationship

4 Nokia Siemens Networks

Nokia Siemens Networks

Layer and Channels Relationship

6 Nokia Siemens Networks

Physical Resource Block or Resource Block ( PRB or RB):

Subcarrier 0 1 2 3 4 5 6 0 1 2 3 4 5 6 Capacity allocation is based on

Time scheduler can assign to a user is a

8 Nokia Siemens Networks

Layer and Channels Relationship

9 Nokia Siemens Networks

11 Nokia Siemens Networks

Layer and Channels Relationship

12 Nokia Siemens Networks

DwPTS: Downlink Pilot time Slot time

14 Nokia Siemens Networks

3rd frame is always used for uplink.

When switching from downlink to uplink, there is need for a special

15 Nokia Siemens Networks

UE always needs a guard period in order to switch from receiver to

Downlink Uplink eNodeB

End of DL UE has switched to RTD = 2 x PT

Layer and Channels Relationship

17 Nokia Siemens Networks

18 Nokia Siemens Networks

The end user is switching on his/her LTE mobile

What are all the steps and

19 Nokia Siemens Networks

What do I need on the first place?

Find one cell

Get synchronisation time & frequency

Finally I read system info to find out:

20 Nokia Siemens Networks

1. PSS Primary Synchronisation Signal

2. SSS Secondary Synchronisation Signal

22 Nokia Siemens Networks

5. PCFICH Physical Control Format Indicator Channel

6. PDCCH Physical Downlink Control Channel

7. PDSCH Physical Downlink Shared Channel

*SIB = System Information Block CELL SELECTION &

23 Nokia Siemens Networks

The UE has selected one cell camping on the cell procedure

The camping on the cell procedure will be explained later

The UE can start the initial access

I have found one suitable

24 Nokia Siemens Networks

9. PCFICH Physical Control Format Indicator Channel

10. PDCCH Physical Downlink Control Channel

11. PDSCH Physical Downlink Shared Channel

eNodeB ID of the received preamble,

26 Nokia Siemens Networks

11. PDSCH Physical Downlink Shared Channel

12. PUSCH Physical Uplink Shared Channel

13. PDSCH Physical Downlink Shared Channel

27 Nokia Siemens Networks

The random access procedure is successfully finished

Higher layer signalling -> not shown here

28 Nokia Siemens Networks

2. PUCCH Physical Uplink Control Channel (or PUSCH)

4. PDCCH Physical Downlink Control Channel