IMP TA1 11 001 Day1 LTE Protocol

UMTS Long Term
Evolution (LTE)
protocol aspects
Reiner Stuhlfauth
Reiner.Stuhlfauth@rohde-schwarz.com
Training Centre
Rohde & Schwarz, Germany
3GPP UMTS Evolution
What are the major technical road works?

As usual: Bandwidth
-Wider frequency bandwidth
-MIMO systems
-Additional frequency bands
-Higher value modulation schemes
Reduce Round Trip Time, RTT
-Node-B upgrade
-Fast scheduling methods
All over Packet Switched Connection
-Deployment of IMS (IP Multimedia Subsystem) in core networks
-solely Shared Channel setups
Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 2
Round Trip Time, RTT

ACK/NACK
generation in RNC
TTI
~10msec
Iu
Iub/Iur
Node B
MSC
Serving
RNC
SGSN
TTI
=1msec
MME/SAE Gateway
eNode B
ACK/NACK
generation in node B
IMS: Reference Model (3GPP/3GPP2)

IP Multimedia
Subsystem IMS
= All over IP connection
LTE Protocol Architecture
LTE Protocol Architecture

Reduced complexity
l Reduced number of transport channels

l Shared channels instead of dedicated channels
l Reduction of Medium Access Control (MAC) entities
l Streamlined concepts for broadcast / multicast (MBMS)
l No inter eNodeB soft handover in downlink/uplink
l No compressed mode
l Reduction of RRC states
E-UTRA protocol structure

Dj vu from
WCDMA?
Radio Resource Control (RRC)
Layer 2
Layer 1
Control / Measurements
Layer 3
Radio Link Control, RLC
Logical channels
Medium Access Control
(MAC)
Transport channels
Physical layer
EUTRAN stack: different channels
Control & Measurements
Radio Resource Control

RRC
Radio Link Control
RLC
Service Access Point

SAP
Logical channels
What to be
transmitted

MAC
Transport
channels
How to transmit
PHYSICAL LAYER
Physical
channels
Code, Frequency, etc.
EUTRAN stack: protocol layers overview

MM
ESM
User plane
Control & Measurements

RRC
Packet Data Convergence
PDCP
Radio Link Control
RLC
MAC
PHYSICAL LAYER
Channel structure: User + Control plane

Protocol structure
User plane
Header compression (ROHC)

In-sequence delivery at handover
Duplicate detection
Ciphering for user/control plane
Integrity protection for control plane
Timer based SDU discard in Uplink
AM, UM, TM
ARQ
(Re-)segmentation
Concatenation
In-sequence delivery
Duplicate detection
SDU discard
Reset
Mapping between logical and

transport channels
(De)-Multiplexing
Traffic volume measurements
HARQ
Priority handling
Transport format selection
PDCP = Packet Data Convergence Protocol

RLC = Radio Link Control
MAC = Medium Access Control
PHY = Physical Layer
SDU = Service Data Unit
(H)ARQ = (Hybrid) Automatic Repeat Request
Control plane
Broadcast
Paging
RRC connection setup
Radio Bearer Control
Mobility functions
UE measurement control
EPS bearer management

Authentication
ECM_IDLE mobility handling
Paging origination in ECM_IDLE
Security control
EPS = Evolved packet system

RRC = Radio Resource Control
NAS = Non Access Stratum
ECM = EPS Connection Management
LTE channel mapping
LTE channels
LTE channels: control information mapping

CFI
DCI
HI
Control Format Indicator
Downlink Control Information
HARQ Indicator
MCH
PCH
DL-SCH
BCH
DL transport channels
DL physical channels
PMCH
PCFICH
PDCCH
PDSCH
PHICH
PBCH
UCI
Uplink Control Information
RACH
UL-SCH
UL transport channels
UL physical channels
PRACH
PUCCH
PUSCH
LTE Identifiers and System Information
Radio Network Transaction Identifiers, RNTI

C-RNTI
SI-RNTI
Cell RNTI,
identifies a UE
having a RRC connection
within a cell
System InformationRNTI,
Broadcast of
System information
RA-RNTI
Random AccessRNTI,
Random Access Response
P-RNTI
TPC-RNTI
Paging-RNTI,
Paging and System
Information change info
Transmit Power Control

RNTI,
For power control, DCI 3,
i.e. multiplexing TPC
commands
RNTI - usage
RNTI
Usage
Transport Channel
Logical Channel
P-RNTI
Paging and System Information change

notification
PCH
PCCH
SI-RNTI
Broadcast of System Information
DL-SCH
BCCH
RA-RNTI
DL-SCH
N/A
DL-SCH
CCCH
Temporary C-RNTI
Contention Resolution
(when no valid C-RNTI is available)
Temporary C-RNTI
Msg3 transmission
UL-SCH
CCCH, DCCH, DTCH
C-RNTI
Dynamically scheduled unicast transmission
UL-SCH
DCCH, DTCH
C-RNTI
Dynamically scheduled unicast transmission
DL-SCH
CCCH, DCCH, DTCH
C-RNTI
Triggering of PDCCH ordered random access
N/A
N/A
Semi-Persistent
Scheduling CRNTI
Semi-Persistently scheduled unicast

transmission
(activation, reactivation and retransmission)
DL-SCH, UL-SCH
DCCH, DTCH
Semi-Persistent
Scheduling CRNTI
Semi-Persistently scheduled unicast

transmission
(deactivation)
N/A
N/A
TPC-PUCCH-RNTI
Physical layer Uplink power control
N/A
N/A
TPC-PUSCH-RNTI
Physical layer Uplink power control
N/A
N/A
Masking of CRC in LTE general principle

Bit - Mask
Data or control message
Mask used to send control

Information. Saves space in
data part
Cyclic Redundancy
Check, CRC
CRC used for error detection
LTE is using CRC for 2 reasons: For error detection and to send control information,
i.e. killing 2 birds with 1 stone
One example:
Data part
00110011
Data part
Original CRC
1101
1.step: data + original CRC
1111
+
1101
Data part
00110011
Here: 3 masks
Original
CRC
Masked CRC
0010
3.step: data + masked CRC
0010
00110011
Bit Mask
Masked
CRC
2nd step: select mask

and XOR with CRC
Receiver does
not know which
Mask nor if CRC
Is right -> try it
One mask will be
Succesful!
Masked CRC
0010
0010
0010
0000
1111
0101
0010
1101
0111
Uplink allocation using C-RNTI

Cell-RNTI
16 bits: xk
CRC is scrambled with

RNTI to identify the UE
PDCCH
c k = (bk + x rnti ,k
)mod 2
Cyclic Redundancy
Downlink Control Information DCI
Check, CRC
Format 0
16 bits: bk
PUSCH
Uplink transport block sent on PUSCH
Downlink allocation using C-RNTI

Cell-RNTI
16 bits: xk

RNTI to identify the UE
PDCCH
)mod 2
Cyclic Redundancy
Check, CRC
Format 1 or 2
16 bits: bk
PDSCH
Downlink transport block sent on PDSCH

Downlink transport block sent on PDSCH
DCI Format 2 is used

In case of MIMO, it can
Indicate 1 or 2
transport blocks
Downlink allocation using SI-RNTI

SI-RNTI
16 bits: xk

System Information-RNTI
PDCCH
)mod 2
Cyclic Redundancy
Check, CRC
Format 1
16 bits: bk
PDSCH
Downlink transport block, containing

System Information message
Downlink allocation using P-RNTI

P-RNTI
16 bits: xk

Paging-RNTI
PDCCH
)mod 2
Cyclic Redundancy
Check, CRC
Format 1
16 bits: bk
PDSCH
Downlink transport block, containing

Paging Information message
Downlink allocation using TPC-RNTI

TPC-RNTI
16 bits: xk

Transmit Power Control RNTI
PDCCH
)mod 2
Cyclic Redundancy
Check, CRC
Format 3
16 bits: bk
tpc-Index=1
PDSCH
TPC_cmd1
TPC_cmd2
TPC_cmd N
tpc-Index=2
tpc-Index=N
Multiplexing of power control

Commands in 1 message
E-UTRAN Identities
3GPP TS 36.300 subclause 8
l UE identities
l C-RNTI (Cell Radio Network Temporary Identity)
l Random value for contention resolution
l eNodeB identities
l ECI E-UTRAN Cell Identifier
28 Bit eNB Identifier
l ECGI E-UTRAN Cell Global Identifier
Composition of MCC (Mobile Country Code), MNC (Mobile Network Code) and
ECI
l TAI Tracking Area Identifier
Composition of MCC, MNC and TAC (Tracking Area Code)
System Information Block Types

l Master Information Block (Periodicity of 40 ms)
l Essential PHY information to allow receiving further SIBs
l SIB Type 1 (Periodicity of 80 ms)
l Cell access information and essential information to allow receiving further SIBs
l SIB Type 2
l Common and shared channel information
l SIB Type 3
l Serving cell related cell re-selection information
l SIB Type 4
l Serving cell information
l SIB Type 5
l E-UTRA neighbour cell information
l SIB Type 6
l UTRA neighbour cell information
l SIB Type 7
l GERAN neighbour cell information
l SIB Type 8
l CDMA2000 neighbour cell information
l SIB Type 9
l Home eNB identifiers (e.g. femto cell)
LTE Physical Layer

Downlink physical control channels
LTE: new physical channels for data and control

Physical Control Format Indicator Channel PCFICH:
Indicates Format of PDCCH
Physical Downlink Control Channel PDCCH:

Downlink and uplink scheduling decisions
Physical Downlink Shared Channel PDSCH: Downlink data
Physical Hybrid ARQ Indicator Channel PHICH:

ACK/NACK for uplink packets
Physical Uplink Shared Channel PUSCH: Uplink data
Physical Uplink Control Channel PUCCH:

ACK/NACK for downlink packets, scheduling requests, channel quality info
LTE downlink
Scheduling of downlink data
Check PDCCH for your UE ID. As
soon as you are addressed, you will
find all the information you need there.
Physical Downlink Control
Channel (PDCCH)
Physical Downlink Shared

Channel (PDSCH)
I would like to receive data on
PDSCH but I dont know which
resource blocks are allocated for me
and how they look like
Physical Control Format Indicator Channel (PCFICH)

Indicating PDCCH format
Check PCFICH. It will tell you how many
symbols (1, 2, or 3)in the beginning of the
subframe are allocated for PDCCH.
Physical Control Format
Indicator Channel (PCFICH)
Physical Downlink Control
Channel (PDCCH)
I would like to read the PDCCH but

where is it?
Physical Hybrid ARQ Indicator Channel (PHICH)

Acknowledging uplink data packets
Read the PHICH. It carries ACK or
NACK for each single packet.
Physical Hybrid ARQ
Indicator Channel (PHICH)
Physical Uplink Shared Channel

(PUSCH)
I have sent data packets on PUSCH

but I dont know whether they have
been received correctly.
?
LTE Downlink
OFDMA time-frequency multiplexing
QPSK, 16QAM or 64QAM modulation
1 resource block =
180 kHz = 12 subcarriers
frequency
UE4
UE5
UE3
UE2
UE6
Subcarrier spacing = 15 kHz

UE1
*TTI = transmission time interval

** For normal cyclic prefix duration
1 subframe =
1 slot = 0.5 ms = 1 ms= 1 TTI*=
7 OFDM symbols** 1 resource block pair
time
LTE Downlink: FDD channel mapping example
PDSCH
PDCCH
PCFICH
PBCH
S-SCH
P-SCH
Time
PDSCH
DCI
Frequency
Demodulation performed by the UE

UE samples channel bandwidth and 1 subframe
As IQ samples. Demodulation only performed on
Particular channels / resources
1 subframe = 1msec
If UE detects RNTI it
will read PDSCH on
scheduled resource
0001111010101011110111010
UE checks
for PCFICH
UE checks for DCI in

common or dedicated
search space
1101100101
1101100101 1101100101
1101100101
PDCCH
1101100101
Channel Bandwidth
1101100101
Downlink: resource element group
REG7
REG3
REG6
REG
REG4
Variable
mapping scheme
for control channels:
PDCCH, PCFICH
and PHICH
REG5
REG8
REG
REG1
REG
R
REG2
REG
REG7
6 OFDM symbol periods
12 subcarriers ( 180 kHz )
REG3
REG6
REG4
REG5
REG8
REG
REG1
R
REG2
12 subcarriers ( 180 kHz )
7 OFDM symbol periods
= used for PDSCH

= in some resouce blocks used for PCFICH
= optional usage for PDCCH if less than 10 RBs assigned
= optionally used for PHICH
= cell specific reference symbol. Precedence over every other resource element content
= optionally used for PDCCH, depending on format
Downlink: resource element group, REG
REG
REG7
REG
REG4
REG5
REG8
REG
REG2
subcarriers
REG3
REG6
7 OFDM symbols
REG1
3.Symbol:
REG size =
4 resource
elements
1.Symbol:
REG size =
6 resource
elements
2. Symbol:
REG size = 6 or 4
resource elements,
depending on # of
antennas
Resource element group

= mapping of control
information to resource
elements
PDCCH, PCFICH and PHICH

use a certain number of REGs to
send control information
4. Symbol:
REG size = 6 or 4 resource
elements, depending on
extended or normal cyclic prefix
Physical Format Indicator Channel, PCFICH

Indicates how many OFDM symbols are used for PDCCH in that subframe,
i.e. the control format indicator, CFI
Transmitted in every subframe, QPSK modulated
Coded as 32 bits, transmitted in 4 Resource Element Groups, REG
Mapping on frequency resource depends on cell identity (see TS36.211 section 6.7.4)
Subframe where PCFICH is
sent
Number of OFDM symbols for PDCCH when

DL
N RB
> 10
DL
N RB
10
Subframe 1 and 6 in TDD

mode
1, 2
Subframe 0 in FDD mode
1, 2, 3
2, 3, 4
b0 , b1 ,..., b31
Most frequent scenario

C FI c od e w o rd
< b 0, b 1 , , b
C F I
3 1
>
< 0 ,1 , 1 ,0 ,1 , 1 ,0 , 1 , 1 ,0 , 1 ,1 , 0 ,1 ,1 , 0 ,1 ,1 , 0 ,1 , 1 , 0 ,1 , 1 ,0 , 1 ,1 ,0 , 1 ,1 ,0 ,1 >
< 1 ,0 , 1 ,1 ,0 , 1 ,1 , 0 , 1 ,1 , 0 ,1 , 1 ,0 ,1 , 1 ,0 ,1 , 1 ,0 , 1 , 1 ,0 , 1 ,1 , 0 ,1 ,1 , 0 ,1 ,1 ,0 >
< 1 ,1 , 0 ,1 ,1 , 0 ,1 , 1 , 0 ,1 , 1 ,0 , 1 ,1 ,0 , 1 ,1 ,0 , 1 ,1 , 0 , 1 ,1 , 0 ,1 , 1 ,0 ,1 , 1 ,0 ,1 ,1 >
4
(R e se rv e d )
< 0 ,0 , 0 ,0 ,0 , 0 ,0 , 0 , 0 ,0 , 0 ,0 , 0 ,0 ,0 , 0 ,0 ,0 , 0 ,0 , 0 , 0 ,0 , 0 ,0 , 0 ,0 ,0 , 0 ,0 ,0 ,0 >
PCFICH mapping on physical resource
PCFICH
PCFICH
PCFICH
PCFICH
Resource block
Mapping of PCFICH onto resource elements is based on Physical Layer Cell Identity!
)(
cell
DL
k = N scRB 2 N ID
mod 2 N RB
1
First resource block
)
Last resource block
Channel Bandwidth
4
z ( p ) (0) is mapped to the resource - element group represented by k = k

z ( p ) (1)
z
( p)
DL
is mapped to the resource - element group represented by k = k + N RB
2 N scRB 2
DL
(2) is mapped to the resource - element group represented by k = k + 2 N RB
2 N scRB 2
DL
z ( p ) (3) is mapped to the resource - element group represented by k = k + 3N RB
2 N scRB 2
PCFICH mapping on physical resource

Example: 3 cells with 10 MHz
NCellID =99
PCFICH is
frequency interleaved
NCellID =0
2
1
294
444
594
f
0
150
300
144
450
Number of resource element group,

i.e. which resource block carries PCFICH
Value = first subcarrier of REG
Channel Bandwidth, here = 50 RB

NCellID =231
36
186
336
486
Physical HARQ Indicator Channel, PHICH

Indicates ACK or NACK of previous uplink data block
Transmitted in every subframe, BPSK modulated
Multiple PHICHs on same resource -> separated by orthogonal sequence
Mapping on frequency resource depends on cell identity (see TS36.211 section 6.7.4)
PHICH is identified by group and sequence identifiers
(n
group
seq
,
n
PHICH PHICH
RRC layer configures number of groups:

PHICH-resource (1/6, ,1 or 2) multiplied with bandwidth
group
N PHICH
=
DL
N g N RB
b0 , b1 , b2
Orthogonal sequence, Spreading Factor is 2 or 4

Sequence index
seq
nPHICH
Given by MIB
DL
N g N RB
)
0
1
for normal cyclic prefix

for extended cyclic prefix
2
3
4
5
6
7
Orthogonal sequence
Normal cyclic prefix Extended cyclic prefix
[+ 1
[+ 1
[+ 1
[+ 1
[+ j
[+ j
[+ j
[+ j
PHICH
N SF
=4
+ 1 + 1 + 1]
1 +1
+1
1
1]
1]
1 + 1]
+ j + j + j]
j +j
+j
j]
j]
j + j]
PHICH
N SF
=2
[+ 1
[+ 1
[+ j
[+ j
+ 1]
1]
+ j]
j]
PHICH principle
n+4
n+4
t=0 t=1 t=2 t=3 t=4
Downlink
PUSCH
Data
PUSCH
Data
PDCCH
PHICH
ACK/NACK
n+4
t=5 t=6 t=7 t=8 t=9 t=0 t=1 t=2
t=3 t=4 t=5
1 frame = 10 subframes
8 HARQ processes
RTT = 8 msec
Uplink
PHICH physical resource mapping
n+4
Mapped on
frequency
resource
starting at
PHICH group
calculated
based on
n+4
PHICH
ACK/NACK
n+4
t=0 t=1 t=2 t=3 t=4
PUSCH data
sent on
Uplink resource
starting at:
Downlink
PUSCH
Data
PUSCH
Data
DCI0
UL Frequency
domain: Lowest
index resource
block
Demodulation
reference
symbol, DMRS,
3bit
Uplink
Sysinfo:
Number of
PHICH
groups
t=5 t=6 t=7 t=8 t=9 t=0 t=1 t=2 t=3 t=4 t=5
group
group
group
lowest _ index
n PHICH
= ( I PRB
+ n DMRS ) mod N PHICH
+ I PHICH N PHICH
_ RA
seq
lowest _ index
group
PHICH
n PHICH
= ( I PRB
/ N PHICH
+ n DMRS ) mod 2 N SF
_ RA
PHICH mapping on physical resource

RRC value
PHICH-duration: normal (= 1
OFDM symbol) or extended (=3
OFDM symbols)
Resource block
PHICH
PHICH
Optional used for PHICH
PHICH group resource = 3 Resource Element Groups
PHICH Group1
PHICH Group1
PHICH Group1
REG 1
REG 2
REG 3
f
Last resource block
Mapping of PHICH onto resource elements is based on Physical Layer Cell Identity!
PHICH mapping on physical resource

Example: 3 cells with 10 MHz, each cell has 2 PHICH groups configured
PHICH area
306
312
114
504 PHICH group1
120
510 PHICH group2
Number of resource element group,

i.e. which resource block carries PHICH
Value = first subcarrier of REG
3
2
318
324
NCellID =231
1
f
138
144
348
354
96
102
NCellID =99
PHICH is
frequency interleaved
NCellID =0
546 PHICH group1

552 PHICH group2
516 PHICH group1

522 PHICH group2
Physical Downlik Control Channel PDCCH

PDCCH transmits a list of control messages
Control message is called Downlink Control information DCI
Number of DCIs is variable
#OFDM symbols
DCI
DCI
DCI
DCI
DCI
DCI
DCI
DCI
DCI
DCI
NCCE =
f(Bandwidth,
#OFDM symbols
and PHICH
Configuration)
1 DCI is of length
1, 2, 4 or 8 CCE
Number of Control Channel Elements, i.e.

the resource available for DCI transmission
PDCCH resources
REG
REG
REG
REG
REG
REG
REG
REG
Resource block
REG
1 Control Channel Element, CCE = 9 REGs = 72 bits

CCE
CCE
CCE
CCE
CCE
CCE
CCE
CCE
CCE
CCE
CCE
PDCCH can be size

of either 1, 2, 4 or 8 CCEs
= aggregation level
CCE
CCE
CCE
CCE
Downlink Control Channel (PDCCH)

PDCCH carries L1 and L2 control information
It is QPSK modulated
Each PDCCH is transmitted via one or several consecutive Control
Channel Elements (CCEs). Content of these CCEs
is the Downlink Control Information (DCI).
DCI contains DL or UL scheduling, or UL power control
CRC is scrambled with UE-specific identity
UE monitors a set of PDCCH candidates for assigned DCIs in
every non-DRX subframe (Each possible DCI format is checked.)
1 PDCCH
1,2,4 or 8 CCEs
1 CCE
9 Resource Element Groups REG
1 REG
6 Resource Elements RE in 1st symbol

4 RE in 2nd and 3rd symbol
PDCCH
format
Number
of CCEs
Number of
ResourceElement Groups
Number of
PDCCH
bits
72
18
144
36
288
72
576
PDCCH search space

Resources used for PCFICH
Resources used for PHICH
PDSCH with:
System information
Paging
CCCH
PDSCH with:
Dedicated
data
PUSCH
Resources
To send
Dedicated data
#OFDM symbols
or
Common search space

DCIs
DCIs
Dedicated search spaces

DCIs
DCIs
Last resource block

NCCE =
f(Bandwidth,
#OFDM symbols
and PHICH
Configuration)
e.g. UEs in connected mode to
monitor resource allocation.
e.g. UEs in idle mode to

monitor system information
+ paging
Note: search spaces may overlap
PDCCH search space: # of REG per RB
frequency
REG3
REG6
REG
REG7
REG
REG4
REG5
REG8
REG
R
REG2
subcarriers
PCFICH indication: PDCCH size

1 OFDM symbol => 1 Ressource Block = 2 REGs
2 OFDM symbols => 1 Ressource Block = 5 REGs
3 OFDM symbols => 1 Ressource Block = 8 REGs
7 OFDM symbols
REG1
3.Symbol:
REG size =
4 resource
elements
R
time
1.Symbol:
REG size =
6 resource
elements
Capacity of PDCCH depends on

configuration of PHICH,
Channel bandwidth and
number of OFDM symbols
used for PDCCH
2. Symbol:
REG size = 4
(assume 1 or 2
antennas)
PDCCH search space: CCE number

Capacity of PDCCH depends on
configuration of PHICH,
Channel bandwidth and
number of OFDM symbols
Num PHICH Groups

System Bandwidth
1.4 MHz
3 MHz
5 MHz
10 MHz
15 MHz
20 MHz
Example: this table gives the available number

of control channel elements, CCE
(remember 1CCE = 9 REGs)
used to carry PDCCH information
1
Num Rb
6
15
25
50
75
100
Number of Available CCEs 1 & 2 Antennas

Num Symbols PDCCH
1
2
3
4
N/A
2
4
6
2
7
12
N/A
4
13
21
N/A
10
27
43
N/A
15
40
65
N/A
21
54
88
N/A
Number of CCE used for PDCCH transmission

PDCCH search space calculation

UE has to monitor PDCCH for various sizes, e.g. aggregation levels separately
UE specific: PDCCH candidate
sizes are 1, 2, 4 or 8 CCE
UE common: PDCCH candidate

sizes are 4 or 8 CCE
(L )
Search space S k
Type
UEspecific
Common
CCE CCE CCE CCE
Number of PDCCH
candidates
Aggregation level L
Size [in CCEs]
12
16
16
16
CCE CCE CCE CCE
M (L )
CCE CCE CCE CCE
1 PDCCH candidate
CCE CCE CCE CCE
PDCCH search space calculation

UE has to monitor PDCCH for various sizes, e.g. aggregation levels separately
(L )
Search space S k
Type
Aggregation level L
Size [in CCEs]
12
16
16
16
UEspecific
Common
CCE CCE CCE CCE
Number of PDCCH
candidates
CCE CCE CCE CCE
M (L )
CCE CCE CCE CCE
UE has to blind detect which

Aggregation level is used,
e.g. here the UE will decode both
search space format possibilities
and tries to detect a proper result,
based on CRC checksum!
CCE CCE CCE CCE
1 PDCCH candidate
CCE CCE CCE CCE CCE CCE CCE CCE
CCE CCE CCE CCE CCE CCE CCE CCE
1 PDCCH candidate
PDCCH aggregation of control channel elements

The aggregation level of CCE is selected by the eNodeB according to the RF conditions
Bad RF conditions:
eNodeB selects aggregation level = 4
Good RF conditions:
eNodeB selects aggregation level = 1
CC
E
CCE
CC
E
CC
E
CC
E
DCI
DCI
Here: DCI is
scrambled and spread
over 4 CCEs
PDCCH common search space calculation

Search space position is given as:
{(Y
+ m ) mod N CCE, k / L
Aggregation Level L
4
Common Search Space
See before: depends on bandwidth and PHICH configuration
TTI
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
Yk
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
}+i
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Where Yk = 0, for common search space

PDCCH Candidate
1
2
3
4
8
12
4
8
12
4
8
12
4
8
12
4
8
12
4
8
12
4
8
12
4
8
12
4
8
12
4
8
12
8
8
This example gives the PDCCH channel
8
8
numbers, i.e. start CCE for the common
8
search space.
8
Here NCCE = 26 and #PHICH groups = 2
8
8
8
8
PDCCH dedicated search space calculation

Search space position is given as:
{(Yk + m ) mod
Aggregation Level L
1
TTI
0
1
2
3
4
5
6
7
8
9
0
1
2
3
4
5
6
7
8
9
See before: depends on bandwidth and PHICH configuration
N CCE, k / L
Yk
5048
44717
41521
27283
62118
17373
40362
5838
50287
35166
5048
44717
41521
27283
62118
17373
40362
5838
50287
35166
0
4
23
25
9
4
5
10
14
3
14
8
20
24
18
8
10
20
2
6
2
1
5
24
0
10
5
6
11
15
4
15
10
22
0
20
10
12
22
4
8
4
Yk = ( A Yk
+i
) mod D
Where Y-1 = RNTI, A = 39827 and D = 65537

PDCCH Candidate
2
3
6
7
25
0
1
2
11
12
6
7
7
8
12
13
16
17
5
6
16
17
12
14
24
0
2
4
22
24
12
14
14
16
24
0
6
8
10
12
6
8
4
8
1
3
13
8
9
14
18
7
18
16
2
6
0
16
18
2
10
14
10
5
9
2
4
14
9
10
15
19
8
19
18
4
8
2
18
20
4
12
16
12
UE specific
Hopping to
avoid blocking
or PDCCH
congestion
This example gives the PDCCH channel numbers, i.e. start CCE for the dedicated search
space extracted. Here NCCE = 26 and #PHICH groups = 2 and UEs RNTI = 10.
E.g. UE expects PDCCH candidate 0 to start at CCE = 4 in subframe = 0
Downlink Control Information DCI formats

Frequency allocation could be
distributed or contiguous
DCI format will
Indicate which
Transmission mode
Is applied
PDCCH
PDSCH
Reporting about precoding matrix,

only in closed loop spatial
multiplexing
2nd transport block only active

when in MIMO mode spatial
multiplexing
DCI formats
l DCI format 0 is used for the scheduling of PUSCH.
l DCI format 1 is used for the scheduling of one PDSCH codeword.
l DCI format 1A is used for the compact scheduling of one PDSCH codeword and random
access procedure initiated by a PDCCH order.

l DCI format 1B is used for the compact scheduling of one PDSCH codeword with
precoding information.
l DCI format 1C is used for very compact scheduling of one PDSCH codeword.
l DCI format 1D is used for the compact scheduling of one PDSCH codeword with
precoding and power offset information.
l DCI format 2 is used for scheduling PDSCH to UEs configured in closed-loop spatial
multiplexing mode.
l DCI format 2A is used for scheduling PDSCH to UEs configured in open-loop spatial
multiplexing mode.
l DCI format 3 is used for the transmission of TPC commands for PUCCH and PUSCH
with 2-bit power adjustments.
l DCI format 3A is used for the transmission of TPC commands for PUCCH and PUSCH
with single bit power adjustments.
Downlink Control Information DCI content

DCI format 0 is used for the scheduling of PUSCH.
Flag for format0/format1A differentiation
1 bit
Hopping flag
1 bit
Resource block assignment
max 13bits
Modulation and coding scheme and redundancy version 5bits
New data indicator
1 bit
TPC command for scheduled PUSCH
2 bits
Cyclic shift for demodulation reference signals
3 bits
UL index (only for TDD)
2 bits
Downlink Assignment Index (DAI) (only for TDD)
2 bits
CQI request
1 bit

DCI format 1 is used for the scheduling of
one PDSCH codeword
Resource allocation header (allocation type 0 or 1)
1 bit
max 25 bits
Modulation and coding scheme
5 bits
HARQ process number
3/4 bits(FDD/TDD)
New data indicator
1 bit
Redundancy version
2 bits
2 bits
2 bits

DCI format 1A is used for the compact scheduling of
one PDSCH codeword (allocation type 2) and
random access procedure initiated by a PDCCH order
Flag for format0/format1A differentiation
HARQ process
New data indicator
Redundancy version

DCI format 1B is used for the compact scheduling of
one PDSCH codeword with precoding information
Localized/Distributed VRB assignment flag
HARQ process number
New data indicator
Redundancy version
TPMI information for precoding number
PMI confirmation for precoding

DCI format 1C is used for very compact scheduling of
one PDSCH codeword (allocation type2)
1 bit indicates the gap value
Hopping flag
Transport block size index
CRC scrambled with P-,
RA-, or SI-RNTI (system
info RNTI) and used
modulation scheme is
always QPSK

DCI format 1D is used for the compact scheduling of
one PDSCH codeword with precoding
and power offset information
Localized/Distributed VRB assignment flag
HARQ process number
New data indicator
Redundancy version
TPC command for PUCCH
Downlink Assignment Index (for TDD only)
TPMI information for precoding
Downlink power offset

DCI format 2 is used for 2 Transport Blocks
Resource allocation header (allocation type0/1)
1 bit
max 25bits
2 bits
2 bits
HARQ process number
3 / 4 bits (FDD/TDD)
Transport block to codeword swap flag
1 bit
Precoding information
3 or 6 bits (2 or 4 antennas)
Transport block 1
Transport block 2
Modulation and coding scheme 5 bits Modulation and coding scheme

New data indicator
1 bit New data indicator
Redundancy version
2 bit Redundancy version
DCI transport block to codeword mapping

2 transport
blocks enabled
transport block
to codeword
swap flag value
codeword 0
(enabled)
codeword 1
(enabled)
transport block 1
transport block 2
transport block 2
transport block 1
transport block 1
transport block 2
codeword 0
(enabled)
codeword 1
(disabled)
enabled
disabled
transport block 1
disabled
enabled
transport block 2
1 transport
blocks enabled

DCI format 2A is used for 2 Transport Blocks
Resource allocation header
HARQ process number
Precoding information
Transport block 1
New data indicator
Redundancy version
Transport block 2
New data indicator
Redundancy version

DCI format 3 is used for the transmission of
TPC commands for PUCCH and PUSCH
with 2-bit power adjustments
TPC command number 1
,,
TPC command number N
Idea to send several TPC commands

to different UEs in parallel

DCI format 3A is used for the transmission of
TPC commands for PUCCH and PUSCH
with single bit power adjustments
,,
TPC command number M
Idea to send several TPC commands

to different UEs in parallel
PDCCH layer 1/2 control channel contents

Transmission modes
l
l
For DCI formats 1A and 1C, UE may be addressed via S-RNTI or P-RNTI or
RA-RNTI (all common search space)
UE-specific search space for the following transmission modes:
1. Single-antenna port; port 0
2. Transmit diversity
3. Open-loop spatial multiplexing
4. Closed-loop spatial multiplexing
5. Multi-user MIMO
6. Closed-loop Rank=1 precoding
7. Single-antenna port; port 5
Association of DCI formats to transmission modes
l
l
l
l
l
l
l
Single-antenna port; port 0

Transmit diversity
Open-loop spatial multiplexing
Closed-loop spatial multiplexing
Multi-user MIMO
Closed-loop Rank=1 precoding
Single-antenna port; port 5

Transmission modes for C-RNTI usage

Transmission modes for SPS C-RNTI usage

Transmission modes for Temp. C-RNTI usage
DCI format blind detection

Based on L3 signaling, the UE knows which transmission mode
The size of the DCI message is known by the UE
The UE calculates the dedicated search space
Blind detection based on DCI format and aggregation level
Aggregation Level
1
2
4
8
Here 4
aggregation
levels are
possible
TTI
Yk
12620
12620
12620
12620
0
20
40
80
0
1
21
42
0
8
Example: UE is in transmission mode 3:

DCI format 1A and 2A are possible.
Each DCI format has 16 possible
Positions in the dedicated search space
+ aggregation level.
-> so the UE will do 16 (DCI 1A) +
16 (DCI2A) = 32 blind detections
PDCCH Candidate
2
3
22
23
44
46
4
24
48
5
25
50
For aggregation level 1 and 2

there are 6 candidates,
For aggregation level 4 and 8
are 2 candidates
-> UE blind detects 6+6+2+2
= 16 possible DCIs
LTE Physical Layer

Uplink physical channels
LTE Uplink: channel mapping example

Unscheduled Resource Blocks
Scheduled PUCCH
Scheduled Resource Blocks
Demodulation Reference Signal PUCCH
Demodulation Reference Signal PUSCH

Sounding Reference Signal
tim
Allocated bandwidth
frequency
1s
ub
fra
me
Total available bandwidth
Uplink channel coding + mapping

Logical
Channels
CCCH
DCCH
DTCH
(MAC SDUs)
MAC Multiplexing
Transport
Channels
RACH
UL-SCH
(MAC PDUs)
Layer 1 + 2
Control
PHY Encoding, Modulation, Mapping
Either or
Physical
Channels
PUCCH
PRACH
(signal)
PUSCH
Uplink Control Information, UCI
RI= number of
useful transmission
layers, i.e.
Min{NRX,NTX}
New data or
Retransmit?
ACK/
NACK
[W(i)]
CQI= Transport
format and
modulation
scheme?
PDSCH
PMI= Which
precoding matrix
shall be used?
UCI on PUSCH or PUCCH:

CQI, Channel Quality Indication
Precoding Matrix Information, PMI
Rank Indicator, RI
ACK/NACK
Scheduling requests
PUCCH scheduling request, SR

PUSCH
MACPDU
UL
nPRB = N RB
1
MAC layer has data to send, but no PUSCH available

=> UE is allowed to send scheduling request
m =1
m=3
m=0
m=2
m=2
m=0
m=3
m =1
UE specific index
point to position of
PUCCH
SchedulingRequestConfig ::=CHOICE {
nPRB = 0
release
NULL,
setup
SEQUENCE {
(1)
(1)
sr-PUCCH-ResourceIndex INTEGER (0..2047), nPUCCH
= nPUCCH,
SRI
One subframe
sr-ConfigIndex
INTEGER (0..155),
dsr-TransMax
ENUMERATED {n4, n8, n16, n32, n64, spare3, spare2, spare1}
}
}
Maximum transmission of SRs
Scheduling
Request
opportunity
Scheduling
Request
opportunity
Periodicity given in number of subframes by sr-ConfigIndex
Scheduling
Request
opportunity
Uplink Control Channel (PUCCH)

Carries Uplink Control Information (UCI) when no PDSCH is transmitted
TDD: PUCCH is not transmitted in subframes containing the UpPTS field
PUCCH
format
Bits per
subframe
Modulation
Contents
On/Off
N/A
Scheduling Request (SR)
1a
BPSK
ACK/NACK, ACK/NACK+SR
1b
QPSK
ACK/NACK, ACK/NACK+SR
20
QPSK
CQI/PMI or RI (any CP),

(CQI/PMI or RI)+ACK/NACK (long CP only)
2a
21
QPSK+BPSK
(CQI/PMI or RI)+ACK/NACK (normal CP only)
2b
22
QPSK+BPSK
(CQI/PMI or RI)+ACK/NACK (normal CP only)
Channel quality reporting comprises Channel Quality Indicator (CQI),

Precoding Matrix Indicator (PMI) and Rank Indicator (RI)
CQI/PMI/RI are only signaled via PUCCH when periodic reporting is
requested. Scheduled/aperiodic reporting is only done via PUSCH
LTE Uplink:
PUCCH: physical uplink control channel
nPRB =
m
2
UL
1
N RB
if (m + ns mod 2 ) mod 2 = 0
m
2
if (m + ns mod 2 ) mod 2 = 1
resource i
resource j
frequency
PUCCH region
resource j
resource i
1 ms subframe
A control channel resource is defined by a code and two resource blocks,

consecutive in time, with hopping at the slot boundary .
Frequency diversity benefit given by this design
PUCCH resource allocation

Edge of channel
bandwidth
Format 2, 2a, 2b (m=1)
Format 2, 2a, 2b (m=N(2)RB)
Format 2, 2a, 2b (m=)
Format 1, 1a, 1b +
2, 2a, 2b (m=)
Format 1, 1a, 1b (m=NHORB)
Channel bandwidth
Resource blocks
reserved for
PUCCH = NHORB
Resource reserved for PUSCH
Only 1 RB
for mixed format
Format 1, 1a, 1b (m=NHORB)
Format 1, 1a, 1b +
2, 2a, 2b (m=)
Format 2, 2a, 2b (m=N(2)RB)
PUCCH RB index
Resource blocks
reserved for format
2, 2a and 2b = N(2)RB
optional
PUCCH reference symbols position

Number of reference symbols per slot
PUCCH
format
Normal cyclic
prefix
Extended cyclic
prefix
1, 1a, 1b
2a, 2b
N/A
Reference symbol location

PUCCH
format
Set of values
Normal cyclic
prefix
Extended
cyclic prefix
1, 1a, 1b
2, 3, 4
2, 3
1, 5
2a, 2b
1, 5
N/A
PUCCH
allocation 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
time
Example: normal CP
PUCCH format 1a
frequency
0123456 0123456 0123456 0123456
time
Example: normal CP
PUCCH format 2a
frequency
PUCCH formats 1, 1a & 1b: coding chain

Depends on cell
identity + SCFDMA symbol
numer and
timeslot
Sequence index noc(ns )
PUCCH
Orthogonal sequences w(0) L w(NSF
1)
[+1
[+1
[+1
0
1
2
+1 +1 +1]
1 +1
1
1]
1 +1]
1 or 2 bits
ACK/NACK
and/or
ACK/NACK + SR
Cyclically
shifted CAZAC
sequence
12 possible
cyclic shifts
ru(,v ) (n)
Scrambling with PUCCH index

specific scrambling
Code.
S (n s ) =
1
ej
PUCCH
Sequence z(n)
Spreading
with orthogonal
cover code.
3 possible
sequences
if n' (n S ) mod 2 = 0
otherwise
Based on higher layer parameters PUCCH index and delta_shift
PUCCH formats 1, 1a & 1b: Multiplexing

ACK/NACK
or
ACK/NACK + SR
ru(,v ) (n)
Cyclically
shifted CAZAC
sequence
12 possible
cyclic shifts
Scrambling with PUCCH index

specific scrambling
Code.
12 cyclic shift sequences and

3 orthogonal sequences =>
Up to 36 UEs can share
multiplexed PUCCH
resources
PUCCH resource format 1 =
#Ref. Symbols * 12
PUCCH
shift
PUCCH
Sequence z(n)
Spreading
with orthogonal
cover code.
3 possible
sequences
But
Interference due
to multipath is
likely
PUCCH formats 1, 1a & 1b: Multiplexing

= inter-cell
Interference
Reduction by cell
Specific offset
Cell specific
cyclic shift offset
deltaoffset=1
deltaoffset=0
OCindex=
0
CSindex=1
CSindex=0
k=0
10
11
10
11
To reduce interference,
not all combinations
are allowed, here
Delta_shift = 2,
reduces multiplexing
to 18 PUCCH
Example:
Normal Cyclic prefix
Delta_shift = 2
PUCCH
shift
PUCCH orthogonal cover OC

OCindex=1
OCindex=2
12
6
1
13
7
14
8
15
9
16
10
UE with
Index 14 uses
OC with index = 2
And cyclic shift
With index = 4
17
11
PUCCH
shift
=cyclic shift
difference for
adjacent ACK
Resources,
Here =2
PUCCH format 1, 1a & 1b: timing + allocation

PDSCH PDCCH
k+4
ACK/
NACK
PUCCH resource is k+4 subframes

later than PDSCH
t=0 t=1 t=2 t=3 t=4 t=5 t=6 t=7 t=8 t=9 t=0
1 frame = 10 subframes
UL
nPRB = N RB
1
Position of PDCCH
containing DCI
defines the PUCCH
location.
nPRB = 0
m =1
m=3
m=0
m=2
Location of PUCCH format 1,1a or 1B is given as:

(1)
(1)
nPUCCH
= nCCE + N PUCCH
m=2
m=0
m=3
m =1
One subframe
Given by SIB 2
Resource optionally
reserved for
Position of CCE used
PUCCH format
to send DCI on PDCCH
2, 2a or 2b
PUCCH formats 2, 2a & 2b: coding chain

Format 2 = 20 bits
Format 2a = 21 bits 1
Format 2b = 22 bits
Depends on
PUCCH index +
SC-FDMA
symbol numer
and timeslot
Cyclically
shifted CAZAC
sequence
12 possible
cyclic shifts
20 bits
ACK/NACK
and/or
CQI/PMI or RI
ru(,v ) (n)
PUCCH
Sequence z(n)
Z(n) is mapped
On data part of
PUCCH resource block
Scrambling with C-RNTI

specific scrambling
Code.
cell
cinit = ( ns 2 + 1) 2 N ID
+ 1 216 + n RNTI
Format 2a and 2b steals the additional 1 or 2 bits to

substitutes the reference symbol
0123456
CAZAC
Sequence as
Reference
symbol
PUCCH format 2, 2a & 2b: timing + allocation

PUCCH resource follows rules
Of CQI and RI reporting
Rank
Indicator
PMI
Wide
band
CQI
PMI
Wide
band
CQI
PMI
Rank
Indicator
Wide
band
CQI
Periodicity given in number of subframes by various RRC parameters
UE specific
PUCCH index
Identifies position of PUCCH
(2)
RB
m = nPUCCH
N sc
UE specific RRC parameter:

cqi-ReportConfig
MAC
MAC structure UE side
Data transfer
Radio resource allocation
Logical Channels
PCCH
BCCH
CCCH
DCCH
DTCH
MAC-control
Logical Channel Prioritization

(UL only)
(De-) Multiplexing
HARQ
PCH
BCH
DL-SCH
Control
Random
Access Control
UL-SCH
RACH
Data transfer, CQI feedback, Transport channels

scheduling request + HARQ feedback
Layer 2 Structure for Downlink

Multiple applications
Layer 2 Structure for Uplink

Radio Bearers
ROHC
ROHC
Security
Security
PDCP
RLC
Segm.
ARQ
...
Segm.
ARQ
Logical Channels
Scheduling / Priority Handling
MAC
Multiplexing
HARQ
Transport Channels
MAC PDU structure

R /R/E/LCID
sub-header
R /R /E/LCID[/F/L]
sub-header
R/R/E/LCID /F/L
sub-header
R/R/E/LCID/F/L
sub-header
...
R/R/E/LCID /F/L
sub-header
R /R /E/LCID padding
sub -header
Variable size
Fix size
MAC header
MAC Control
element 1
MAC Control
element 2
MAC SDU
MAC payload
e.g. buffer status reports, C-RNTI,

DRX commands,Timing advance,
power headroom,
...
MAC SDU
Padding
(opt)
MAC prioritized bit rate PBR

Logical
channel
A
PBR for
Logical
channel
A
Logical
channel
B
PBR for
Logical
channel
B
Logical
channel
C
RRC configures each
Logical channel with a
Prioritized bit rate PBR.
MAC-PDU will be served
In decreasing order of
Priority.
PBR for
Logical
channel
C
MAC-PDU is larger,
So highest priority channel
Can send more data
Total MAC-PDU size

RLC structure
Radio Link Control Protocol, RLC

User Plane

RRC
RLC SDU
Control &
Measurements
Variable size possible
Radio Link Control

RLC
RLC PDU
Logical channel
header RLC SDU

MAC
Lower layer notifies

Transmission opportunity
EUTRAN stack: RLC architecture

Transparent
mode
AM-SAP
Unacknowledged
mode
UM-SAP
Control
TM-SAP
Acknowledged
mode
Transmitting
transparent
entity
Receiving
transparent
entity
BCCH/PCCH
CCCH
Acknowledged
Transmitting
mode
unacknowledged
entity
entity
DCCH/
DTCH
SAP = Service Access Points
Receiving
unacknowledged
entity
DTCH
RLC PDU structure

Segmentation and concatenation of SDUs is possible (except TM mode)
Total size indicated by lower layer
SDU = Service Data Unit

PDU = Packet Data Unit
PDCP structure
Packet Data Convergence Protocol
PDCP structure view

UE/E-UTRAN
RRC control
RB can be signaling radio bearer SRB

or
Data radio bearer, DRB
Radio Bearers, RB
PDCP-SAP
PDCP-SAP
...
C-SAP
PDCP
sublayer
PDCP entity
PDCP entity
PDCP - PDU
RLC - SDU
...
RLC UM-SAP
RLC AM-SAP
Each PDCP entity carries data from 1 Radio Bearer
RLC
sublayer
PDCP functional overview

UE/E-UTRAN
E-UTRAN/UE
Transmitting
PDCP entity
Max SDU size

= 8188 octets
Receiving
PDCP entity
Sequence numbering
In order delivery and duplicate

detection (u-plane only)
Header Compression (u-plane

only)
Header Decompression (uplane only)

Packets associated
to a PDCP SDU
Integrity Verification
(c-plane only)
Ciphering
Deciphering
Add PDCP header
Timer based
discard function
Packets not
associated to a
PDCP SDU
Integrity Protection
(c-plane only)
Packets not
associated to a
PDCP SDU
Packets associated
to a PDCP SDU
Remove PDCP Header
Radio Interface (Uu)
No compression
of data so far, only
header
Based on hyper frame

and sequence number
= COUNT
PDCP re-establishment
Handover, with
statusReportRequired
Status report
Acknoledging PDUs
PDCP re-establishment
including retransmissions
Re-establishment resets
ciphering and integrity protection
PDCP lossless handover in uplink

1
S-GW
5
6
Source
eNB
PDCP PDU
Nr. 3 and 5
1
are lost
Target
eNB
3
PDCP PDU
Nr. 1 and 2
are ACK
4
5
Handover
UE sends PDCP sequence number
After Handover: UE sends PDCP sequence number
PDCP lossless handover in downlink

2
LP
S-GW
7
6
LP
Source
eNB
Target
eNB
6
4
PDCP PDU
Nr. 3 is lost
PDCP PDU
Nr. 1 and 2
are ACK
eNB retransmits packets

Nr. 3 and 4, even if 4
Is already received.
5
4
Handover
UE receives PDCP Nr. 1, 2 and 4
LP
= Last Packet
RRC procedures
RRC Protocol states WCDMA <-> LTE

UTRARRCConnectedMode
URA_PCH
out of
service
in
service
CELL_DCH
out of
service
in
service
GSM
Connected
Mode
GPRS
Packet
Transfer
Mode
CELL_FACH
out of
in
service service
ReleaseRRC
Connection
GSM:
Handover
UTRA:
Inter-RAT
Handover
CELL_PCH
Cell reselection
EstablishRRC ReleaseRRC EstablishRRC

Connection
Connection Connection
ReleaseRR
Connection
EstablishRR
Connection
Releaseof Initiationof
temporary temporary
blockflow blockflow
GPRSPacketIdleMode1
CampingonaUTRANcell1
CampingonaGSM/ GPRScell1
IdleMode
WCDMA protocol states
RRC connected
state
RRC Idle state
LTE protocol states
LTE Interworking with 2G/3G

Two RRC states: CONNECTED & IDLE
GSM_Connected
CELL_DCH
Handover
E-UTRA
RRC CONNECTED
Handover
GPRS Packet
transfer mode
CELL_FACH
CELL_PCH
URA_PCH
CCO with
NACC
Reselection
Connection
establishment/release
UTRA_Idle
Reselection
CCO,
Reselection
Connection
E-UTRA
RRC IDLE
Connection
Reselection
CCO, Reselection
GSM_Idle/GPRS
Packet_Idle
LTE Interworking with CDMA2000 1xRTT and

HRPD (High Rate Packet Data)
1xRTT CS Active
Handover
E-UTRA
RRC CONNECTED
Handover
HRPD
HRPD Dormant
Active
Connection
1xRTT Dormant
Reselection
E-UTRA
RRC IDLE
Reselection
HRPD Idle
System information broadcast
UE
Master Information Block (on BCH),

periodicity 40 ms:
System bandwidth, number of
transmit antennas, PHICH
configuration, SFN
E-UTRAN
MasterInformationBlock
System Information Block Type 1

(on DL-SCH), periodicity 80 ms:
PLMN IDs, Tracking Area Code,
Cell identity, Access restrictions,
scheduling information,
SystemInformationBlockType1
SystemInformation
SI-RNTI is used on PDCCH to

address System Information
Block Type 1 and SI messages
System information blocks with

same scheduling requirements
can be mapped to same SI
message (DL-SCH)
System information
MIB:
Physical layer info
SIB Type 1:
Access restrictions,
SIB scheduling info
SIB Type 2:
Common and
shared channel info
SIB Type 3:
Cell reselection info
SIB Type 4:
Cell reselection info,
intra-fr. neighbour info
SIB Type 5:
Cell reselection info,
inter-fr. neighbour info
SIB Type 6:
for UTRA
SIB Type 7:
for GERAN
SIB Type 8:
for CDMA2000
SIB Type 9:
Home eNB identifier
(HNBID)
SIB Type 10:

ETWS primary
notification
SIB Type 11:

ETWS secondary
notification
ETWS = Earthquake and Tsunami Warning System
Initial access procedure

Sent on PRACH
resources associated with
RA-RNTI
UE
Sent on UL-SCH; includes

NAS UE identifier and RRC
CONNECTION REQUEST
eNB
Random Access Preamble
Generated by MAC sent on DLSCH with RA-RNTI; assignment

of Temporary C-RNTI, timing
advance, initial uplink grant
2
Scheduled Transmission
Early contention resolution

(mirroring of uplink message)
generated by MAC sent on
DL-SCH
Initial access procedure

Sent on PRACH
resources associated with
RA-RNTI
UE
Sent on UL-SCH; includes

NAS UE identifier and RRC
CONNECTION REQUEST
eNB
Random Access Preamble
Generated by MAC sent on DLSCH with RA-RNTI; assignment

of Temporary C-RNTI, timing
advance, initial uplink grant
2
Scheduled Transmission
Hopping flag
Fixed size resource block assignment
Truncated modulation and coding scheme
UL delay
CQI request
Early contention resolution

(mirroring of uplink message)
generated by MAC sent on
DL-SCH
Paging
UE
EUTRAN
Paging
Paging procedure is used to:

Transmit paging information to a UE
Inform about System Information Change
Send Earthquake and Tsunami Warning
RRC Connection Establishment

UE
EUTRAN
RRCConnectionRequest
RRCConnectionSetup
RRCConnectionSetupComplete
RRC Connection Reconfiguration

UE
Also used for

handover
EUTRAN
RRCConnectionReconfiguration
RRCConnectionReconfigurationComplete
UE
EUTRAN
RRCConnectionReconfiguration
RRCConnectionReconfigurationFailure
Signaling Radio Bearer, SRB

SRBs are radio bearers for RRC and NAS control message transmission
SRB 0 for RRC messages using CCCH
SRB 1 for RRC messages (optional piggybacked NAS)

using DCCH and before
establishment of SRB2
SRB 2 for NAS messages using DCCH.

Lower priority than SRB1
Configured after security activation
EPS Bearer Service Architecture

E-UTRAN
UE
EPC
eNB
S-GW
Internet
P-GW
Peer
Entity
End-to-end Service
EPS Bearer
Radio Bearer
Radio
External Bearer
S1 Bearer
S5/S8 Bearer
S1
S5/S8
Gi
Default EPS bearer setup

UE
EUTRAN
Initial access and RRC connection establishment

attach request and PDN connectivity request
Authentication
NAS security
UE capability procedure
AS security
RRC connection reconfiguration
Attach accept and default EPS bearer context request
Default EPS bearer context accept
LTE Registration
incl. security activation
UE
SS
RRC ConnectionnRequest
RRC ConnectionnSetup
RRC ConnectionSetupComplete
contains
NAS ATTACH REQUEST
PDN CONNECTIVITY REQUEST
NAS : AUTHENTICATION REQUEST
NAS : AUTHENTICATION RESPONSE
NAS : SECURITY MODE COMMAND

NAS : SECURITY MODE COMMAND COMPLETE
RRC : SECURITY MODE COMMAND

RRC : SECURITY MODE COMMAND COMPLETE
RRC ConnectionReconfiguration
NAS ATTACH ACCEPT
NAS : ACTIVATE DEFAULT EPS BEARER CONTEXT REQ
RRC ConnectionReconfigurationComplete
NAS : ATTACH COMPLETE
NAS : ACTIVATE DEFAULT EPS BEARER CONTEXT
ACCEPT
contains
Default EPS bearer setup
No.
UE eNB
Message Sequence
Layer
Message
1
2
3
4
RRC
RRC
RRC
RRC
NAS
NAS
SYSTEM INFORMATION (BCCH)

RRC Connection Request
RRC Connection Setup
RRC Connection Setup Complete
Attach Request
PDN Connectivity Request
RRC
NAS
DL Information Transfer
Authentication Request
RRC
NAS
UL Information Transfer
Authentication Response
7
8
9
RRC
RRC
RRC
NAS
UE Capability Inquiry
UE Capability Information
DL Information Transfer
Security Mode Command
10
RRC
NAS
Security Mode Command Complete
11
12
13
RRC
RRC
RRC
NAS
NAS
Security Mode Command

Security Mode Command Complete
RRC Connection Reconfiguration
Attach Accept
Activate Default EPS Bearer Context Request
14
15
RRC
RRC
NAS
NAS
RRC Connection Reconfiguration Complete

Attach Complete
Activate Default EPS Bearer Context Accept
16
RRC
RRC Connection Release
RRC measurement reporting

l Measurement objects
l
defines on what the UE has to

measure, e.g. frequency carrier
Reporting configuration
periodic or event-triggered criteria
which cause to send measurement report + information of what to
report
Measurement identities: A list of measurement identities where
each measurement identity links one measurement object with
one reporting configuration.
Quantity configurations: The quantity configuration defines the
measurement quantities and associated filtering used for all event
evaluation and related reporting of that measurement type.
Measurement gaps: Periods that the UE may use to perform
measurements, i.e. no (UL, DL) transmissions are scheduled.
RRC measurement reporting

l Event A1 (Serving becomes better than threshold)
l Event A2 (Serving becomes worse than threshold)
l Event A3 (Neighbour becomes offset better than serving)
l Event A4 (Neighbour becomes better than threshold)
l Event A5 (Serving becomes worse than threshold1 and neighbour
becomes better than threshold2)

l Event B1 (Inter RAT neighbour becomes better than threshold)
l Event B2 (Serving becomes worse than threshold1 and inter RAT
neighbour becomes better than threshold2)
Non Access Stratum

messages, procedures
& architecture
Protocol States (NAS and AS)

EMM states:
ECM states:
EMM-DEREGISTERED
ECM-IDLE
(UE location not known)
(no NAS signalling connection, UE performs cell

(re)selection and PLMN selection)
EMM-REGISTERED
ECM-CONNECTED
(entered by Attach or Tracking Area Update procedure)
(UE location/cell ID known in MME, UE performs

handover)
RRC states:
RRC_IDLE (no RRC context stored in eNodeB)
RRC_CONNECTED (UE has E_UTRAN RRC connection and context)
EMM=EPS Mobility Management
ECM = EPS Connection Management
LTE NAS architecture, MS side

ESMREG SAP
Radio Bearer from User plane
CM
ESM
RB1
Bearer
RB2
EBI
Control
RB n
EMM
SM
- SAP
SAP
EMMREG
MM Sublayer
PD
EMM
PDCP
SAP
EMMAS
SAP
-
PDCP
EUTRAN Access Stratum sublayer
RRC
GUTI: Globally Unique Temporary Identifier

8
EPS mobile identity IEI
octet 1
Length of EPS mobile identity contents
octet 2
odd/
even
indic
Type of identity
octet 3
MCC digit 2
MCC digit 1
octet 4
MNC digit 3
MCC digit 3
octet 5
MNC digit 2
MNC digit 1
octet 6
MME Group ID
octet 7
MME Group ID (continued)
octet 8
MME Code
octet 9
M-TMSI
octet 10
M-TMSI (continued)
octet 11
M-TMSI (continued)
octet 12
M-TMSI (continued)
octet 13
EMM states
Detach,
Attach Reject,
TAU reject,
E-UTRAN interface switched off due to Non-3GPP handover,
All bearers deactivated
EMM-DEREGISTERED
UEs location not known
EMM-REGISTERED
Attach accept
EMM functions
l NAS signalling;
l NAS signalling security;
l Inter CN node signalling for mobility between 3GPP access networks
l
l
l
l
l
l
l
l
l
l
l
l
(terminating S3);
UE Reachability in ECM-IDLE state (including control and execution of paging
retransmission);
Tracking Area list management;
PDN GW and Serving GW selection;
MME selection for handovers with MME change;
SGSN selection for handovers to 2G or 3G 3GPP access networks;
Roaming (S6a towards home HSS);
Authentication;
Authorization;
Bearer management functions including dedicated bearer establishment;
Lawful Interception of signalling traffic;
Warning message transfer function (including selection of appropriate eNB);
UE Reachability procedures.
EMM: EPS Mobility Management

EMM-NULL
EMM-TRACKINGAREA-UPDATINGINITIATED
- TAU rejected
(other causes)
EMMDEREGISTEREDINITIATED
- enable
S1 mode
- enable S1 and
S101 mode
- TAU accepted
- TAU failed
- TAU rejected
(#13, #15, #25)
- disable
S1 mode
- DETACH accepted
- Lower layer failure
- DETACH requested
(not power off)
- disable S1 and
S101 mode
EMMDEREGISTERED
- ATTACH
requested
DETACH requested
(power off)
Any state
- Network init. DETACH requested

- local DETACH
- intersystem change to cdma2000
HRPD completed
- TAU
requested
EMMREGISTERED
- ATTACH rejected
- SR initiated
- Network init. DETACH requested
- Lower layer failure
- SR accepted
- ATTACH
- SR failed
accepted and
- SR rejected
default EPS bearer
(#13, #15, #18,
context activated
#25, #39)
EMMREGISTEREDINITIATED
EMM- SERVICEREQUEST-INITIATED
Idle mode signaling reduction ISR

ISR is signalled explicitly by core network, i.e. TAU message
Reduces signaling when inter-RAT cell reselection
Sets TIN, Temporary Identity used in Next update
Message received by UE
Current TIN value stored by UE
TIN value to be set by the UE when receiving

message
Attach Accept via E-UTRAN

(never indicates "ISR activated")
Any value
GUTI
Attach Accept via GERAN/UTRAN

(never indicates "ISR activated")
Any value
P-TMSI
TAU Accept
not indicating "ISR Activated"
Any value
GUTI
TAU Accept
indicating "ISR Activated"
GUTI
P-TMSI or RAT-related TMSI
GUTI
RAT-related TMSI
RAU Accept
not indicating "ISR Activated"
Any value
P-TMSI
RAU Accept
indicating "ISR Activated"
P-TMSI
GUTI or RAT-related TMSI
P-TMSI
RAT-related TMSI
MME procedures
Authentication
procedure
Authentication +
Identity request
procedure
MME: Attach procedure
Initial attach procedure complete view

UE
eNodeB
new MME
Serving GW
Old
MME/SGSN
1. Attach Request
HSS
PCRF
PDN GW
EIR
2. Attach
Request
3. Identification Request
3. Identification Response
4. Identity Request
4. Identity Response
5a. Authentication / Security
5b. Identity Request/Response
5b. ME Identity Check
6. Ciphered Options Request

6. Ciphered Options Response
7. Delete Sesion Request
(E)
7. PCEF Initiated IP-CAN

Session Termination
7. Delete Session Response
(A)
8. Update Location Request

9. Cancel Location
9. Cancel Location Ack
10. Delete Session Request
10. Delete Session Response
(F)

Session Termination
(B)
11. Update Location Ack

12. Create Session Request
13. Create Session Request
14. PCEF Initiated IP-CAN Session
Establishment/Modification
(C)
15. Create Session Response

First Downlink Data (if not handover)
16. Create Session Response
17. Initial Context Setup Request / Attach Accept
18. RRC Connection Reconfiguration
19. RRC Connection Reconfiguration Complete
20. Initial Context Setup Response
21. Direct Transfer
22. Attach Complete
First Uplink Data
23. Modify Bearer Request
23a. Modify Bearer Request
23b. Modify Bearer Response
(D)
24. Modify Bearer Response
First Downlink Data
25. Notify Request
26. Notify Response
Tracking Area Update

l
Periodic Tracking Area Updates in idle mode keep the network

informed about whether a UE is in EUTRAN coverage or not. A
similar mechanism is required at AS level so that the network
can be kept informed that UE is in coverage while in long lived
connected mode DRX.
l Indicate that in Connected Mode, network needs to be kept informed
about whether UE is in EUTRAN coverage by periodic updates at
AS level
MME: Tracking Area Update
ECM, EPS connection management
RRC connection
released
ECM-CONNECTED
ECM-IDLE
RRC connection
established
No signaling connection between UE and network
UE monitors paging
UE performs tracking area update
Location of UE known based on TAI (if EMM registered)
signaling connection between UE and MME

UE has RRC signaling radio bearer established
Mobility is handover procedure
Location of UE known based on cell ID
ESM: EPS session management
EMM connection management
Service Request procedure

UE
MME
eNodeB
1. NAS: Service Request

2. NAS: Service Request
PDN GW
Serving GW
PCRF
HSS
Go from EMM_IDLE to
EMM_CONNECTED
3. Authentication/Security
4. S1-AP: Initial Context Setup Request
When UL data is to be sent

Or for MT/MO CS procedures
5. Radio Bearer Establishment

6. Uplink Data
7. S1-AP: Initial Context Setup Complete

Session Modification
(A)

LTE IP Connectivity
l PDN Connectivity
l Allows UE to request connectivity to IPv4, IPv6 or IPv4v6 network
l Coupled to Establishment of a Default EPS Bearer
l Default EPS Bearer
l Owns IP Address(es) for IPv4, IPv6 or IPv4v6 Connection
l Typically low QoS
l Intended for plumbing services (e.g. DNS, ICMP, ...)
l Dedicated EPS Bearer
l Always linked to a Default EPS Bearer
l Shares IP Address(es) with linked Default EPS Bearer
l Requires Traffic Flow Template (TFT) to select Packets
l QoS depends on Application
ESM: Default EPS Bearer

Initiated by network
Default bearer = established with every new connection to PDN.

Established over lifetime of PDN connection
No guaranteed bit rate
Identifies traffic flows that receive common QoS treatment
ESM: Dedicated EPS bearer

Initiated by network,
can be requested by UE
Dedicated bearer = Traffic Flow Template TFT and QoS specific.

(e.g. IP address, Port number, protocol information)
Quality of Service negociated between UE and network
Traffic Flow Template (TFT) = IP Filtering

l TFT Operations
l Create new TFT
l Add packet filters to existing TFT
l Replace packet filters in existing TFT
l Delete packet filters from existing TFT
l Delete existing TFT
l Direction
l UL
l DL
l Bi-directional
l Filter Types
l IPv4 remote address
l IPv6 remote address
l Protocol/NextHeader
l Local Port
l Local Port Range
l Remote Port
l Remote Port Range
l Security Param Index
l Type of Service/Traffic Class
l IPv6 Flow Label
EPS Bearer example with 2 unicast EPS bearer

Application / Service Layer
UL Traffic Flow Templates
UL TFT -> RB ID
UL TFT -> RB ID
Radio Bearer
UE
eNB
S1 Bearer
DL Traffic Flow Templates

DL TFT
DL TFT
S5/S8 Bearer
Serving
GW
PDN
GW
IP address allocation in LTE

l Home network allocates IP address (static or dynamic)
l Visited network allocates IP address (static or dynamic)
l External allocation, IP address is allocated by external PDN
l PDN types IPv4, IPv6 and IPv4v6 are supported
l A UE which is IPv6 and IPv4 capable shall request for PDN type IPv4v6.
l A UE which is only IPv4 capable shall request for PDN type IPv4.
l A UE which is only IPv6 capable shall request for PDN type IPv6.
l UE indicates to the network if it would like to receive the IPv4 address
during default EPS beares setup or via DHCP after the default bearer
setup procedure
IPv6 address allocation

External
PDN
Default Bearer Establishment
Router solicitation message

PDN-GW
Ipv6 prefix
(if external
Allocation)
Router advertising message

Contains IPv6 prefix as in default bearer
Link local identifier to generate IPv6 address
UE generates IPv6 address
UE IPv6 address is globally

Unique ->
IPv6 prefix is linked to IMSI
CSFB Circuit Switched Fallback

UE/MS
eNodeB
BSS/RNS
MME
MSC
SGSN
Serving
GW
1a. Extended Service Request

1b. S1-AP Message with CS Fallback indicator
2. Optional Measurement Report Solicitation
3. PS HO as specified in 23.401 [2] (preparation phase and start of execution phase)
4. CM Service Request
4. A/Iu-cs message (with CM Service Request)
5. CM Service Reject
5. CM Service Reject
Location Area Update or Combined RA/LA Update

6. CS call establishment procedure
7. PS HO as specified in 23.401 [2] (continuation of execution phase)
If the MSC
is changed
There will be enough topics

for future trainings
Thank you for your attention!
Comments and questions
welcome!

IMP TA1 11 001 Day1 LTE Protocol

Uploaded by

Document Information

Original Title

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

IMP TA1 11 001 Day1 LTE Protocol

Uploaded by

Copyright:

Available Formats

UMTS Long Term

3GPP UMTS Evolution

What are the major technical road works?

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 2

Round Trip Time, RTT

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 3

IMS: Reference Model (3GPP/3GPP2)

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 4

LTE Protocol Architecture

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 5

LTE Protocol Architecture

l Reduced number of transport channels

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 6

E-UTRA protocol structure

Radio Resource Control (RRC)

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 7

EUTRAN stack: different channels

Control & Measurements

Radio Resource Control

Service Access Point

Medium Access Control

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 8

EUTRAN stack: protocol layers overview

Control & Measurements

Radio Resource Control

Channel structure: User + Control plane

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 10

Header compression (ROHC)

Mapping between logical and

PDCP = Packet Data Convergence Protocol

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 11

EPS bearer management

EPS = Evolved packet system

LTE channel mapping

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 13

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 14

LTE channels: control information mapping

Control Format Indicator

Downlink Control Information

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 15

LTE Identifiers and System Information

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 16

Radio Network Transaction Identifiers, RNTI

Transmit Power Control

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 17

Paging and System Information change

Broadcast of System Information

Random Access Response

CCCH, DCCH, DTCH

Dynamically scheduled unicast transmission

Dynamically scheduled unicast transmission

CCCH, DCCH, DTCH

Triggering of PDCCH ordered random access

Semi-Persistently scheduled unicast

Semi-Persistently scheduled unicast

Physical layer Uplink power control

Physical layer Uplink power control

Jan 11 | LTE protocols| R.Stuhlfauth, 1MAT 18

Masking of CRC in LTE general principle

Mask used to send control

CRC used for error detection

1.step: data + original CRC

3.step: data + masked CRC