LTE Overview

Lte
Long term evolution
Content:
Lte introduction OFDMA and SC-FDMA Physical Layer Lte Physical Channels and Signals Multiple Input Multiple Output antennas Bandwidths System and UE parameter Interfaces and Nodes Protocols and Procedures Structure and Layers MBMS Miscellaneous 3 13 33 53 95 107 112 117 141 225 262 272
Page 2
Lte Introduction
Page 3
3GPP, CDMA2000 and WiMAX evolution:
Page 4
Telecom evolution:
GSM EDGE Voice EDGE II CDMA 1X
WCDMA HSPA HSPA+ Data
LTE TDSCDMA
CDMA EV-DO
WiMAX
LTE-A FDD TDD 3GPP Technologies WLAN
UMB
Other Technologies
Page 5
Lte Specifications:
36.101 User Equipment (UE) radio transmission and reception 36.104 Base Station (BS) radio transmission and reception 36.133 Requirements for support of radio resource management 36.141 Base Station (BS) Conformance Testing 36.201 LTE Physical Layer general description 36.211 E-UTRA; Physical Channels and Modulation 36.212 E-UTRA; Multiplexing and channel coding 36.213 E-UTRA; Physical Layer Procedures 36.214 E-UTRA; Physical layer - Measurements 36.300 E-UTRA Stage 2 Overall Description 36.302 Services Provided by the Physical Layer 36.304 UE Procedures in Idle Mode 36.306 UE Radio Access Capabilities 36.321 MAC Specification 36.322 RLC Specification 36.323 PDCP Specification 36.331 RRC Specification 36.3xx UE Categories 36.401 EUTRAN Architecture description 36.410 S1 General Aspects and Principles 36.411 S1 Layer 1 36.412 S1 Signalling Transport 36.413 S1 Application Protocol (S1-AP) 36.414 S1 Data Transport 36.420 X2 general aspects and principles 36.421 X2 layer 1 36.422 X2 signalling transport 36.423 X2 protocol specification (X2-AP) 36.424 X2 data transport 36.44x MBMS 36.5xx Conformance Testing 36.801 Measurement Requirements 36.803 User Equipment (UE) radio transmission and reception 36.804 Base Station (BS) radio transmission and reception 36.902 Self-configuring and self-optimizing network 36.913 LTE-A 36.938 Mobility between E-UTRAN and 3GPP2, Mobile WiMax 36.942 Radio Frequency (RF) system scenarios Page 6
REL.8: Lte:
-MIMO Antenna Technique used
-OFDM (DL) and SC-FDMA (UL) used as Access Technology -Lte Targets: (initial) 100 Mbps downlink, 50 Mbps uplink data rate Reduce latency (100 ms from Idle to Cell DCH) Scalable bandwidth (1,4 20 MHz) Operation in both FDD and TDD
-Voice via PS Core Network -Mobility: optimized 0 15 km/h, high performance 15 120 km/h, maintain 120 350 (500) km/h up to 5 km up to 100 km
-Cell sizes:
-Integration of GERAN, UTRAN, CDMA2000 and WiMax

Page 7
REL.8: Lte (Long term evolution):

Spectrum fexibility: 1.4, 3, 5, 10, 15, 20 MHz UL & DL for paired and unpaired spectrum DL 5 bps/Hz, UL 2,5 bps/Hz DL 100 Mbps, UL 50 Mbps (without MIMO) < 100 ms (idle to active), < 50 ms (dormant to active) 200 at 5 MHz bandwidh** < 5 ms
Spectrum efficiency: Peak Data Rate: (@ 20 MHz bandwidth) Control plane latency:
Users per cell: User plane latency
Page 8
REL.8: Lte versus WiMax:
Parameter Channel bandwidth
Lte Variable 1.4 20MHz
Duplex FDD & TDD Downlink Technique OFDMA Downlink QPSK, 64-QAM, 16-QAM Modulation Schemes Uplink SC-FDMA Uplink Modulation QPSK, 16-QAM, 64QAM Schemes Frame Length Multiple Antenna Techniques 10 ms (slot = 0.5 ms) STC, MIMO, AAS
Mobile WiMAX Variable 3.5 10MHz* TDD (FDD) S-OFDMA 64-QAM, 16QAM, QPSK S-OFDMA 64-QAM, 16QAM, QPSK
5 ms STC, MIMO, AAS
Page 9

MIMO order (Tx/Rx antennas) 4 Possible peak data rates: HSPA Evolution >50Mb/s Lte >200Mb/s
HSPA Evolution >25Mb/s Lte >4Mb/s 1,4 HSPA 14 Mb/s 5 Lte >25Mb/s 10
Lte >100Mb/s
Lte >50Mb/s 20 Carrier bandwidth (MHz)

Page 10
E-UTRA frequency bands:

E-UTRA Band:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 .. 17 .. 33 34 35 36 37 38 39 40
Uplink (UL):
1920 - 1980 MHz 1850 -1910 MHz 1710 -1785 MHz 1710 -1755 MHz 824 - 849MHz 830 - 840 MHz 2500 - 2570 MHz 880 - 915 MHz 1749.9 - 1784.9 MHz
Downlink (DL):
2110 -2170 MHz 1930 -1990 MHz 1805 -1880 MHz 2110 - 2155 MHz 869 - 894MHz 875 - 885 MHz 2620 - 2690 MHz 925 - 960 MHz 1844.9 - 1879.9 MHz
UL-DL Band separation:

130 MHz 20 MHz 20 MHz 355 MHz 20 MHz 35 MHz 50 MHz 10 MHz 60 MHz
Bandwidth:
2 x 60 MHz 2 x 60 MHz 2 x 75 MHz 2 x 45 MHz 2 x 25 MHz 2 x 10 MHz 2 x 70 MHz 2 x 35 MHz 2 x 35 MHz
Mode:
FDD FDD FDD FDD FDD FDD FDD FDD FDD
1710 -1770 MHz

1427.9 - 1452.9 MHz 698 - 716 MHz TBD* 777 787 MHz 788 798 MHz 704 - 716 MHz 1900 - 1920 MHz 2010 - 2025 MHz 1850 - 1910 MHz 1930 - 1990 MHz 1910 - 1930 MHz 2570 - 2620 MHz 1880 1920 MHz 2300 - 2400 MHz
2110 - 2170 MHz

1475.9 - 1500.9 MHz 728 - 746 MHz TBD* 746 756 MHz 758 768 MHz 734 - 746 MHz 1900 - 1920 MHz 2010 - 2025 MHz 1850 - 1910 MHz 1930 - 1990 MHz 1910 - 1930 MHz 2570 2620 MHz 1880 1920 MHz 2300 - 2400 MHz
340 MHz
23 MHz 12 MHz 21 MHz 20 MHz 18 MHz N/A N/A N/A N/A N/A N/A N/A N/A
2 x 60 MHz
2 x 25 MHz 2 x 18 MHz 2 x 10 MHz 2 x 10 MHz 2 x 12 MHz 20 MHz 15 MHz 60 MHz 60 MHz 20 MHz 50 MHz 40 MHz 100 MHz
FDD
FDD FDD FDD FDD FDD TDD TDD TDD TDD TDD TDD TDD TDD Page 11
E-UTRA band / channel bandwidth:

E-UTRA Band
1 2 3 4 5 6 7 8 9 10 11 12 13 14
1.4 MHz
3 MHz
5 MHz

10 MHz

15 MHz
20 MHz
17
... 33 34 35 36 37 38
39
40
Page 12
OFDMA and SC-FDMA

Orthogonal Frequency Division Multiple Access & Single Carrier Frequency Division Multiple Access
Page 13
W-CDMA or CDMA2000 single carrier transmission:
e.g. 5 MHz
Page 14
Frequency Division Multiplexing (FDM)
.........
.........
Sub carriers
Frequency
Page 15
Orthogonal Frequency Division Multiplexing (OFDM)

In an OFDM system, a very high rate data stream is divided into multiple parallel low rate data streams. This is possible with orthogonal frequencies. Each smaller data stream is then mapped to individual data sub-carrier and modulated using some sorts of PSK (Phase Shift Keying) or QAM (Quadrate Amplitude Modulation). i.e. BPSK, QPSK, 16-QAM, 64-QAM.
.........
.........
Orthogonal Sub carriers OFDM makes more efficient use of available spectrum. Sub-carrier spectrum overlaps, BUT orthogonally means that all sub-carriers (except the wanted one) are zero at the decision point. Spectrum has been saved with no loss in performance.
Frequency
Page 16
Orthogonal Frequency Division Multiplexing Access (OFDMA)

OFDMA employs multiple closely spaced sub-carriers, but the subcarriers are divided into groups of sub-carriers. Each group is named a sub-channel. The sub-carriers that form a sub-channel need not be adjacent. In the downlink, a sub-channel may be intended for different receivers. In the uplink, a transmitter may be assigned one or more subchannels.
.........
Guard band Guard band
Frequency Sub channel A Sub channel B Sub channel C

Page 17
Orthogonal Frequency Division Multiplexing Access (OFDMA):

Subchannelization defines sub-channels that can be allocated to subscribers depending on their channel conditions and data requirements. Using subchannelization, within the same time slot a evolved Node B (eNB) can allocate more transmit power to users with lower SNR (Signal-to-Noise Ratio), and less power to user devices with higher SNR. Subchannelization also enables the eNB to allocate higher power to sub-channels assigned to indoor subscribers resulting in better in-building coverage. Subchannelization in the uplink can save a user device transmit power because it can concentrate power only on certain sub-channel(s) allocated to it. This powersaving feature is particularly useful for battery-powered user devices.
f
Sub carriers
f
Sub channels
OFDM
OFDMA
t
Page 18
OFDM Sub-carrier Organization:

Data Sub-carriers DC Sub-carrier Pilot Sub-carriers
Guard Sub-carriers
f
OFDM Sub-carrier Organization:
Data Sub-carriers Transport QPSK, 16-QAM, 64-QAM etc. symbols Pilot Sub-carriers Transport known pilot symbol sequence (frequently at elevated power level) to permit channel estimation and coherent demodulation at receiver Guard Sub-carriers Suppressed permits spectrum shaping DC Sub-carrier (not used) Frequently suppressed to support direct-conversion receivers (with significant zero-frequency component ingress due to 1/f noise etc.)
Page 19
REL.8: LTE (Long Term Evolution):

Why OFDM: Robustness against multipaths using a large number of narrow-band sub-carriers (serial to parallel conversion) Ease of scheduling of time/frequency resources High spectral efficiency Excellent enabler for multiple antennas (MIMO) For even higher data rate support (> 10 x 3G-WCDMA)
Nc sub-carriers
Frequency Df (Hz) BW (Hz)

Page 20
OFDM Orthogonally:
f
In frequency domain zero crossing of all other carriers except the considered one due to SINC property.
Page 21
REL.8: Lte (OFDMA: Frequency Time representation):
Parallel transmission of data over multiple carriers!

Page 22
Insertion (copy) of normal Cyclic Prefix (CP): Ts (Symbol Period)
Cyclic Prefix
Data Payload
Tg
Tu (Useful Symbol Period)

copy
Tg
Tg = T Guard
Tg = 4,7 s (5,2 s for the first CP) for Frame structure 1
Tu ~ 66,7 s Ts ~ 71,5 s
Page 23
Insertion of Extended Cyclic Prefix (CP):

The extended cyclic prefix is defined in order to cover large cell scenarios with higher delay spread!
Ts (Symbol Period)
Cyclic Prefix
Data Payload
Tg

copy Tg = 16,6 s for Frame structure 1
Tg
Tg = T Guard
Tu ~ 66,7 s Ts ~ 83,3 s
Page 24
Insertion of dedicated MBMS Cyclic Prefix (CP): DL only Ts (Symbol Period)
Cyclic Prefix
Data Payload
Tg

copy Tg = 33,3 s for Frame structure 1
Tg
Tg = T Guard
Tu ~ 133,3 s Ts ~ 166,6 s
Page 25
LTE Uplink: Single Carrier FDMA (SC-FDMA):
Coded symbol rate= R Sub-carrier Mapping CP insertion
DFT
NTX symbols
IFFT
Size-NTX
Size-NFFT
Page 26
LTE Uplink: Single Carrier FDMA (SC-FDMA):
Page 27
SC-FDMA localized transmission:
Reduced Tx power! Transmission
Transmission of M modulation symbols

Page 28
SC-FDMA localized transmission:
S/P M Data Symbols
M-DFT CP Insertion P/S
N-IFFT
Tx
Page 29
4 Symbols transmitted: Downlink OFDMA:
CP OFDMA Symbol
15 kHz
f Uplink SC-FDMA:
t
CP SC-FDMA Symbol 60 kHz
f
Page 30
Modulation:
AMC: Adaptive Modulation and Coding
P
UE4
QPSK 16QAM
64QAM
UE3
eNB UE2 UE5 UE1
Page 31
Modulation Schemes: I QPSK (2bit/symbol) 16QAM (4bit/symbol) 64QAM (6bit/symbol)
Page 32
Physical Layer Lte
Page 33
Physical Layer for E-UTRA:

Frame structure type 1 (FDD) normal CP:
One radio frame, Tf = 307200Ts = 10 ms One slot, Tslot = 15360Ts = 0.5 ms
#0
#1
#2
#3
#18
#19
One subframe
Slot
1 2 3 4 5 6 7
C P
Symbol
Page 34

Frame structure type 1 (FDD) extended CP:
#0
#1
#2
#3
#18
#19
One subframe
Slot
1 2 3 4 5 6
C Symbol P
Page 35

Frame structure type 1 (FDD) dedicated MBMS CP:
#0
#1
#2
#3
#18
#19
One subframe
Slot
1 2 3
C P
Symbol
Page 36

Frame structure type 2 (TDD):
One radio frame, Tf = 307200Ts = 10 ms One half-frame, 153600Ts = 5 ms
One slot, Tslot=15360Ts
30720Ts
Subframe #0 One subframe, 30720Ts DwPTS

DwPTS: UpPTS: GP:
Subframe #2
Subframe #3
Subframe #4
Subframe #5
Subframe #7
Subframe #8
Subframe #9
GP
UpPTS
DwPTS
GP
UpPTS
Downlink Pilot Time Slot Uplink Pilot Time Slot Guard Period
Page 37

Frame structure type 2 (TDD):
One slot, Tslot=15360Ts= 0,5 ms
30720Ts = 1 ms
#0
#1
#4
#5
#6
#7
#8
#9
One subframe, 30720Ts
Slot
DwPTS GP UpPTS
1 C P 2 3 4 5 6 7
For switch time periodically = 5 ms, also the second half frame has the same format!
Symbol
Page 38

Frame structure type 2 (TDD) with switch time periodically 10 ms:
One radio frame Tf = 307200T s= 10 ms , One half -frame ,153600 Ts = 5 ms
One slot , Tslot 15360Ts= 0,5 ms =
30720Ts= 1 ms
#0
#1
#4
#5
#6
#7
#8
#9
One subframe , 30720 Ts DwPTS

1 C P 2 3
Slot
4 5 6 7
Symbol
Page 39
UL/DL allocation for TDD frame type 2:

Uplinkdownlink configuration 0
1 2 3 4 5 6
Downlink-to-Uplink Switch-point periodicity 5 ms

5 ms 5 ms 10 ms 10 ms 10 ms 5 ms
Subframe number
0 1 2 3 4 5 6 7 8 9
D
D D D D D D
S
S S S S S S
U
U U U U U U
U
U D U U D U
U
D D U D D U
D
D D D D D D
S
S S D D D S
U
U U D D D U
U
U D D D D U
U
D D D D D D
Page 40
Variable Lengths of DwPTS / GP / UpPTS:

Configura tion 0 1 2 Normal cyclic prefix
DwPTS GP UpPTS
Extended cyclic prefix

DwPTS GP UpPTS
6592 Ts 19760 Ts 21952 Ts
21936 Ts 8768 Ts 6576 Ts 2192 Ts
7680 Ts 20480 Ts 23040 Ts
20480 Ts 7680 Ts 5120 Ts 2560 Ts
3
4 5 6
24144 Ts
26336 Ts 6592 Ts 19760 Ts
4384 Ts
2192 Ts 19744 Ts 6576 Ts
25600 Ts
7680 Ts 20480 Ts 4384 Ts 23040 Ts
2560 Ts
17920 Ts 5120 Ts 2560 Ts 5120 Ts
7
8
21952 Ts
24144 Ts
4384 Ts
2192 Ts
Tf = 307200 x Ts = 10 ms Ts = 32,5520833 ns
Page 41
TDD:
Configuration 8, DL:UL = 39:30
5 ms half frame sub frame x, (1 ms) sub frame 0, (1 ms) 1 ms
DwPTS, 11 symbols Broadcast info
UpPTS, 2 symbols GP, 1 symbol
control
DL data
Gurad period (GP)
UpPTS, random access /sounding
UL transmission
Primary SCH
secondary SCH
Page 42
Overview of DL physical channel processing:
code words Modulation Mapper Layer Mapper Scrambling Modulation Mapper
layers
Resource element mapper
antenna ports OFDM signal generation OFDM signal generation
Scrambling
Precoding
Page 43
Overview of uplink physical channel processing:
Scrambling
Modulation mapper
Transform precoder
SC-FDMA signal gen.
Page 44
Multiple Access by applying chunks (Resource Blocks):

All chunks for shared data channel are assigned
User #1 #2 #3 #4 #5 #6 #7
Time Chunk bandwidth (180 kHz, 1 Resource Block)
A user with a high data rate uses several chunks within the same TTI Low data rate users
Frequency
TTI Subframe
slot
f sub carrier = 15 kHz
Page 45
Downlink Resource Block (RB):

One downlink slot Tslot
#0
#1
#2
#3
#18
#19
One subframe
DL N symb OFDM symbols
Example Frame type 1:

k
DL RB N RB N sc
Resource block DL RB N symb N sc resource elements
DL RB N RB N sc subcarriers
Resource block parameters:

RB N sc subcarriers
Configuration
Resource element (k , l )
RB N sc
DL N sy m b
Normal cyclic prefix
Df 15 kHz
12 6
180 kHz 12 sub carriers

k 0
Df 15 kHz
24
Df 7.5 kHz
l0
DL l N symb 1
Downlink resource grid

Page 46
Uplink Resource Block (RB):

One uplink slot Tslot
Example Frame type 2:
One slot, Tslot=15360Ts
30720Ts
UL N symb SC-FDMA symbols
Subframe #0 One subframe, 30720Ts DwPTS GP
Subframe #2
.....
Subframe #5
Subframe #7
Subframe #8
Subframe #9
UL RB k N RB N sc 1
UpPTS
DwPTS
GP
UpPTS
Resource block UL RB N symb N sc resource elements
UL RB N RB N sc subcarriers
RB N sc subcarriers
Resource element (k , l )
180 kHz
Configuration Normal cyclic prefix Extended cyclic prefix

k 0
RB N sc
UL N sy m b
12 12
7 6
l0
UL l N symb 1
Uplink resource grid

Page 47
Resource Block Scheduling:
Frequency
User 2 User 1
0,5 ms Slot, 7 symbols (normal CP)
180 kHz, 12 sub carrier Time One RB consists of 84 resource elements = 12 subcarrier x 7 symbols (normal cyclic prefix). Each symbol is QPSK, 16QAM or 64QAM.
Page 48

Configuration DL Normal Df 15 kHz cyclic prefix
RB N sc
DL N sy m b
7 12 6 24 3
MBMS
Df 15 kHz
Df 7.5 kHz
Configuration UL
Normal cyclic prefix Extended cyclic prefix
RB N sc
UL N sy m b
12 12
7 6
Page 49
OFDM parameters for downlink transmission scheme:

Transmission BW
Sub-slot duration Sub-carrier spacing Sampling frequency 1.92 MHz (1/2 3.84 MHz) 128 72 3.84 MHz
1.4 MHz
3 MHz
5 MHz
0.5 ms 15 kHz 7.68 MHz (2 3.84 MHz) 512 300
10 MHz
15 MHz
20 MHz
15.36 MHz (4 3.84 MHz) 1024 600
23.04 MHz (6 3.84 MHz) 1536 900
30.72 MHz (8 3.84 MHz) 2048 1200
FFT size Number of occupied sub-carriers Number of OFDM symbols per slot (0,5 ms) (Short/Long CP)
256 180
7/6
CP Length (s/samples)
Short
4.69 6, 5.21 1
16.67
4.69 6, 5.21 1
16.67
4.69 6, 5.21 1
16.67
4.69 6, 5.21 1
16.67
4.69 6, 5.21 1
16.67
4.69 6, 5.21 1
16.67
Long
Page 50
E-UTRA channel bandwidths:
Channel bandwidth BWChannel [MHz]
1.4
10
15
20
Transmission bandwidth configuration
15
25
50
75
100
NRB
Page 51
REL.8: Lte: BW
128 256
1.4 MHz
3 MHz
512
5 MHz
Constant sub -frame length, T s = 1 ms Constant number of symbols N s = 14 (12)
FFT size scales with BW
1024
10 MHz
2048
20 MHz
- sub-frame = 1 ms
Page 52
Physical Channels and Signals
Page 53
LTE Physical Channels and Signals:

Physical Channels and Physical Signals Physical Channels: PRACH PUSCH PUCCH PDSCH PBCH PMCH PHICH PCFICH PDCCH Physical Signals: Uplink Reference Signals Random Access Preamble Sounding Signal Downlink Reference Signal Primary Sync. Signal Secondary Sync. Signal
Downlink Uplink
Page 54
Physical Signals:
Uplink Reference Signals or Uplink pilot symbols: Zadoff-Chu Sequence Random Access Preamble: long Zadoff-Chu Sequence Sounding Signal: orthogonal broadband pilot channel Downlink Reference Signal: Used for synchronization, located on selected subcarriers on selected OFDM symbols.
DL Primary Sync. Signal and Secondary Sync. Signal: Used to identify 168 cell ID groups with 3 members
Downlink Uplink
Page 55
Physical Channels:
Physical broadcast channel (PBCH): The coded BCH transport block is mapped to four subframes within a 40 ms interval; 40 ms timing is blindly detected, i.e. there is no explicit signalling indicating 40 ms timing; Each subframe is assumed to be self-decodable, i.e. the BCH can be decoded from a single reception, assuming sufficiently good channel conditions. Physical control format indicator channel (PCFICH): Informs the UE about the number of OFDM symbols (1, 2,3 or 4) used for the PDCCHs; Transmitted in every subframe. Mapped to the first OFDM symbol in a downlink subframe. Carries the Control Format Indicator (CFI). Physical downlink control channel (PDCCH): Informs the UE about the resource allocation, and hybrid-ARQ information related to DL-SCH and PCH; Carries the uplink scheduling grant. Scheduling grants are provided to Layer 2. Physical downlink shared channel (PDSCH): Carries the DL-SCH. Physical multicast channel (PMCH): Carries the MCH. Physical uplink control channel (PUCCH): Carries ACK/NAKs in response to downlink transmission; Carries CQI reports. Scheduling Request (SR). CQI and Scheduling Requests are provided to Layer 2. Physical uplink shared channel (PUSCH): Carries the UL-SCH. Physical Hybrid ARQ Indicator Channel (PHICH): Carriers ACK/NAKs in response to uplink transmissions. Downlink Physical random access channel (PRACH): Uplink Carries the random access preamble.
Page 56
Physical Signals and Channels on Lte Air:

Physical Signals:
DL Reference Sig. Primary Sync. Secondary Sync. UL Reference Sig. Random Access Preamble Sounding Sig.
eNB
MME/ aGW
LTE Cell
Physical Channels:
PMCH PHICH PCFICH PBCH PDSCH PDCCH PUCCH PUSCH PRACH
S1 Interface
Page 57
REL.8: Lte:
Mapping between logical channels, transport channels and physical channels DL:
BCCH
PCCH
CCCH
DCCH
DTCH
MCCH
MTCH
Logical Channels
BCH
PCH
DL-SCH
MCH
Transport Channels
PHICH PCFICH PDCCH PBCH
PDSCH
PMCH
Physical Channels
Page 58
Mapping between downlink logical channels and downlink transport channels:
PCCH
BCCH
CCCH
DCCH
DTCH
MCCH
MTCH
Downlink Logical channels
PCH
BCH
DL-SCH
MCH
Downlink Transport channels

Page 59

Mapping between transport channels and physical channels DL:
BCH
MCH
PCH
DL-SCH
Downlink Transport channels
PBCH
PMCH
PDSCH
PDCCH
PHICH PCFICH
Downlink Physical channels
Page 60
Allocated P-SCH structure in frequency domain Centre Frequency
73 sub-carriers
Frequency
DC-sub carrier (DL only)
P-SCH sub-carrier null sub-carrier
Page 61
DL Primary and Secondary Synchronization Signals:

5 ms PDCCH, PDSCH SSS PSS PBCH, SSS PSS
0,5 ms 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
DL 10 ms
10 ms
72 subcarriers (1080 kHz)
fDL
73 subcarriers minus 1 DC subcarrier

Page 62
DL Reference Signals:
. .
DL Subframe 0:
Center Frequency 72 Subcarrier = 1080 kHz = 6 PRBs

PBCH, SSS and PSS only on the center frequencies
62 Sub carriers
............. ...............
. .
1 ms 0,5 ms PDCCH PBCH Reserved SSS PSS 0,5 ms DL Reference Signals PDSCH
Page 63
Physical channel mapping (DL):

N DL
=7
Symb
N DL = 100 RB
FDD frame structure (SF1) with normal cyclic prefix and 20 MHz system bandwidth:
PDCCH/PCFICH RB=99 PBCH PSS SSS RB=52 Frequency PDSCH
DC
6 RBs
62 sub carriers
RB=47
Reserved
5 ms
RB=0 OFDM 0 6 0 symbol # Slot #0 Slot #1 Sub frame #0 1 ms 6 0 Slot #2 Sub frame #1 0 6 Slot #10 Sub frame #5 Time
Page 64
Location of PBCH for FS1 (normal CP, extended CP):

Subframe #0
FDD:
Slot #0
Slot #1
PDSCH
frequency frequency
Normal CP case
PSC SH SC H
PDCCH
PBCH
Central 6 RBs
OFDM Symbols
Subframe #0 Slot #0 Slot #1
PDSCH
Extended CP case
PDCCH
PBCH
Central 6 RBs
H SSC H
PSC
OFDM Symbols
Page 65
DL Data trasmission: f
1 ms
User 1 User 2
t
SSS
PDCCH
PBCH
PSS
Used for Reference Signals

Page 66
DL Control Information (DCI):

DCI format 0 is used for the scheduling of PUSCH. DCI format 1 is used for the scheduling of one PDSCH codeword. DCI format 1A is used for the compact scheduling of one PDSCH codeword. DCI format 1B is used for the compact scheduling of one PDSCH codeword with precoding information. DCI format 1C is used for very compact scheduling of one PDSCH codeword. DCI format 1D is used for the compact scheduling of one PDSCH codeword with precoding and power offset information. DCI format 2 is used for scheduling PDSCH to UEs configured in closed-loop spatial multiplexing mode. DCI format 2A is used for scheduling PDSCH to UEs configured in open loop spatial multiplexing mode. DCI format 3 is used for the transmission of TPC commands for PUCCH and PUSCH with 2-bit power adjustments. DCI format 3A is used for the transmission of TPC commands for PUCCH and PUSCH with single bit power adjustments.
The Cyclic Redundancy Check (CRC) of the DCI is scrambled with the UE Identity (RNTI) of that UE which will use the information.
Page 67
Transmission mode & DCI:
Transmission mode:
DCI Format: 1, 1A 1, 1A 2A 2 1D 1B 1, 1A
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
Page 68
Physical channel mapping (DL, TDD, SF2):

DL/GP/UL Depending on cfg DL/GP/UL Depending on cfg
NDL -1 RB
Resource block
0 0 1 2 3 4 5 Subframe P-BCH P-SS S-SS PDCCH/PHICH/PCFICH Available or PDCCH/PHICH/PCFICH Unavailable in all configurations 6 7 8 9
Page 69
Location of PBCH for FS2 (normal CP, exteded CP):
TDD:
Slot #0
Subframe #0 Slot #1 DwPTS
Special subframe GP UpPTS
Normal CP case
PDCCH
frequency frequency
PDSCH
PBCH
SSC H
PSC H
Central 6 RBs
Symbols
Subframe #0 Slot #0 Slot #1 DwPTS Special subframe GP UpPTS
Extended CP case
PDCCH
PDSCH
PBCH
PSC H
SSC H
Central 6 RBs
Symbols
Page 70
DL-SCH physical-layer model:

Node B
Channel-state information, etc.
N Transport blocks (dynamic size S1..., SN)
ACK/NACK ACK/NACK HARQ info
UE
Error indications
HARQ
HARQ info
HARQ
CRC CRC
Coding + RM Coding + RM
Redundancy for error detection
CRC CRC
Coding + RM Decoding + RM
MAC scheduler
Redundancy version
Redundancy for data detection
Interleaving
Modulation scheme Resource/power assignment Antenna mapping
Interl.
Deinterleaving
QPSK, 16QAM, 64QAM
Interl.
Data modulation
Data modulation
Data modulation
Data demodulation RB mapping
RB mapping Resource mapping

Multi-antenna processing
Resource demapping
Antenna mapping
Antenna demapping
Page 71
BCH physical-layer model:

eNB
Single Transport blocks (fixed size S)
UE
Error indication
CRC
CRC
Coding + RM
Decoding + RM
Interleaving
QPSK only
Deinterleaving
Data modulation
Data demodulation
Resource mapping
Resourcedemapping
Antenna mapping
Antenna demapping
Page 72

Mapping between logical channels, transport channels and physical channels UL:
CCCH
DCCH
DTCH
Logical Channels
RACH
UL-SCH
Transport Channels
PUCCH
PRACH
PUSCH
Physical Channels
Page 73
Mapping between uplink logical channels and uplink transport channels:
CCCH
DCCH
DTCH
Uplink Logical channels
RACH
UL-SCH
Uplink Transport channels

Page 74

Mapping between transport channels and physical channels UL:
UL-SCH
RACH
Uplink Transport channels
UCI
PUSCH
PRACH
PUCCH
Uplink Physical channels
Page 75
Definition of Channel Bandwidth and Transmission Bandwidth Configuration:

Channel Bandwidth [MHz] Transmission Bandwidth Configuration [RB] Transmission Bandwidth [RB]
Channel edge
Channel edge
Resource block
Active Resource Blocks
DC carrier (downlink only)

Page 76
UL Structure with SRS, PUSCH and PUCCH:

f
PUCCH (no transmission)
PUSCH (no transmission)
SRS
PUCCH (no transmission)

Last symbol Subframe 1 ms
Page 77
Uplink frame structure:
CP Cyclic Prefix Symbol
Demodulation Reference Signal
Slot 0,5 ms
1 ms
0 Subframe 1 2 3
1 ms
4 5 6 7 8 9
1 Frame
UL 10 ms
Page 78
Uplink frame structure:

Demodulation Reference Signal DRS (for PUSCH and PUCCH)
PUCCH Format 1
PUCCH Format 2
1 ms
PUSCH
f
Page 79
PRB
Uplink frame structure: PUSCH Intra subframe hopping

= DRS
PUSCH
Offset
BW Startpoint
0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 1 2 3 4 5 6 0 slots
0,5
1,5 ms
Page 80
PUCCH:
PUCCH format: Modulation: bits:
1 1a 1b 2 NA BPSK QPSK QPSK NA 1 2 20
Content:
Scheduling Request ACK/NACK, ACK/NACK+SR ACK/NACK, ACK/NACK+SR (CQI/TPMI or TRI (any CP)) or (CQI/TPMI or TRI) + ACK/NACK (ext. CP only) CQI/TPMI or TRI) + ACK/NACK (normal CP only)
2a
QPSK+BPSK 21
2b
QPSK+QPSK 22
CQI/TPMI or TRI) + ACK/NACK (normal CP only)
Page 81
UL Acknowledgement (ACK/NACK):
PUCCH format 1, 1a, 1b:
ACK/NACK(1 symbol) CG sequences (length 12)
IFFT W0 W1
IFFT F0
RS F1
IFFT F2 W2
IFFT W3
IFFT
Symbol0
Symbol1
Reference Signal
Reference Signal
Reference Signal
Symbol2
Symbol3
1 SC-FDMA symbol
PUCCH Format 1, 1a, 1b
1 slot
Page 82
UL Acknowledgement (ACK/NACK):
Page 83
UL Cell Quality Indicator (CQI):
CQI
ZC (length=12) IFFT IFFT IFFT IFFT IFFT
IFFT
Reference Signal 1 Long Block
IFFT
Reference Signal
1 slot
PUCCH Format 2, 2a, 2b
Page 84
UL Cell Quality Indicator (CQI):
Page 85
ACK/NACK Channel Structure:

UL ACK Structure 3 Pilots 0.5 ms Freq
0 11 1 2 11 12 14 15 11 12 14 15 3 11 12 14 15 11 12 14 15 11 12 11 12 4 5 11 12 14 15 11 12 14 15 6 11 12 14 15 11 12 14 15 11 12 7 11 8 12 9 11 12 14 15 11 12 14 15 10 11 12 14 15 11 12 14 15 11 12 11 12 11 12 11 12 14 15 11 12 14 15 13 11 12 14 15 11 12 14 15
0.5 ms
Chu shift separation
15 11
...
11 11 12 14 15 11 12 14 15 11 12 14 15 11 12 14 15 11 12 11 12 11 12 14 15 11 12 14 15 11 12 14 15 11 12 14 15 11 12 11 12 11 12 14 15 11 12 14 15
...
11 12 14 15 11 12 14 15 11 12 11 12 11 12 14 15 11 12 14 15 11 12 14 15 11 12 14 15
Chu shift separation
15 11
15
DFT separation
Walsh cover
pilot
data
others
Page 86
Mapping to physical resource blocks for PUCCH:

UL nPRB N RB 1
m 1 m3
m0 m2
nPRB 0
m2 m0
m3 m 1
One Subframe
Maximum 6 PRBs can be allocated for PUCCH!
Page 87
Scheduling Request Procedure (SR):

UE
1
eNB
Scheduling Request Indicator asynchronous Uplink Scheduling Grant
2
Scheduling Request + Data
Scheduling Request Indicator in PUCCH
Page 88
UL-SCH physical-layer model:

Node B
Channel-state information, etc. Error indications
N Transport blocks (dynamic size S1..., SN)
ACK/NACK ACK/NACK HARQ info HARQ info
UE
HARQ
HARQ
MAC scheduler
Coding + RM Decoding + RM
QPSK, 16QAM, 64QAM
Coding + RM Coding + RM
Redundancy version
Deinterleaving
Modulation scheme Resource assignment Antenna mapping
Interl.
Interleaving
Interl.
Data demodulation RB mapping
Data modulation
Data modulation Data modulation

RB mapping Resource mapping
Modulation scheme Resource/power assignment Antenna mapping
Resource demapping
Antenna demapping
Antenna mapping
Page 89
Uplink transmission control
CRC CRC
CRC CRC
Random Access:
CP 0,1ms Cyclic Prefix Long Zadoff-Chu Sequence Preamble 800 s f 1 ms Subframe 1 ms PRACH Guard Time 0,1ms
UL 10 ms
Page 90
Usage of PRACH Preamble:
Long Zadoff-Chu Sequence 0 800 s
UE sends PRACH Preamble with 0 TA, eNB receives with x TA.

1
200 s 30 km RACH Preamble
RACH Response
800 s 120 km RACH Data (RRC)
Noise
PRACH
PRACH
PRACH
PDCCH PDSCH
PUSCH
t
Page 91
Timing Advance:
1ms Downlink transmission Uplink reception from UE1 Uplink reception from UE2 eNB
Downlink reception Uplink transmission UE1 (close to eNB)
Downlink reception Uplink transmission UE2 (far from eNB)
Page 92
Random access procedure:

Can be used for other random access channels or data transmission .
Data transmission
t
B W RA
T RA T RA - REP
1 ms sub frame ( 20 ms radio frame )
(Scheduled) Data transmission

Random Access Preamble
Guard Period
Page 93
PRACH Frequency Hopping:

PRACH minimum FH pattern for 20ms period
Page 94
MIMO
Multiple Input Multiple Output antennas
Page 95
Multiple antenna techniques: SISO MISO
SIMO
MIMO
Page 96
MIMO: (Multiple Input Multiple Output antennas)
MIMO creates multiple parallel channels between transmitter and receiver. MIMO is using time and space to transmit data (space time coding).
MIMO is a family of techniques:
Use multiple channels to send the same information stream to achieve diversity (transmit diversity) improve coverage and robustness of data transmission
Use multiple channels to send multiple information streams (spatial multiplexing) increase throughput
Page 97
Downlink MIMO:
Spatial Multiplexing: Spatial multiplexing allows to transmit different streams of data simultaneously on the same downlink resource block(s). These data streams can belong to one single user (single user MIMO / SU-MIMO) or to different users (multi user MIMO / MU-MIMO). While SU-MIMO increases the data rate of one user, MU-MIMO allows to increase the overall capacity. Spatial multiplexing is only possible if the mobile radio channel allows it! Transmit Diversity: Instead of increasing data rate or capacity, MIMO can be used to exploit diversity. Transmit diversity schemes are already known from WCDMA release 99 and will also form part of LTE as one MIMO mode. In case the channel conditions do not allow spatial multiplexing, a transmit diversity scheme will be used instead, so switching between these two MIMO modes is possible depending on channel conditions. Transmit diversity is used when the selected number of streams (rank) is one.
Page 98
Uplink MIMO:
Uplink MIMO schemes for LTE will differ from downlink MIMO schemes to take into account terminal complexity issues. For the uplink, MU-MIMO (Virtual MIMO) can be used. Multiple user terminals may transmit simultaneously on the same resource block. This is also referred to as Spatial Domain Multiple Access (SDMA). The scheme requires only one transmit antenna at UE side which is a big advantage. The UEs sharing the same resource block have to apply mutually orthogonal pilot patterns. To exploit the benefit of two or more transmit antennas, but still keep the UE cost low, antenna subset selection can be used. In the beginning, this technique will be used, e.g. a UE will have two transmit antennas but only one transmit chain and amplifier. A switch will then choose the antenna that provides the best channel to the eNB. MU-MIMO will be the first LTE uplink implementation.
Page 99
MIMO Spatial Multiplexing:
101 101010
101010
Tx 010
Rx
Page 100
Spatial Domain Multiple Access:

In operation, multiple mobile terminals may transmit simultaneously on the same channel or channels, but they do not cause interference to each other because mutually orthogonal pilot patterns are used. This techniques is also referred to as Spatial Domain Multiple Access (SDMA).
Time
OFDM symbol Control or data, maximum up to 4 symbols for control
Frequency
Common pilot symbols for 2nd TX antenna
sub-carrier
Common pilot symbols for 3rd and 4th antenna subframe 0 1 TTI = 1 ms subframe 0
Common pilot symbols For 1st antenna
Page 101
Mapping of downlink reference signals per PRB (normal CP):

One antenna port
R0 R0 R0 R0 R0 R0
R0
l0
R0
l6 l0 l6
Resource element (k,l)
Two antenna ports
R0
R0
R1
R1
R0
R0
R1
R1
Not used for transmission on this antenan port
R0
R0
R1
R1
Reference symbols on this antenna port

R1
R0
l0
R0
l6 l0 l6 l0
R1
l6 l0
l6
Four antenna ports
R0
R0
R1
R1
R2
R3
R0
R0
R1
R1
R2
R3
R0
R0
R1
R1
R2
R3
R0
l0
R0
l6 l0 l6 l0
R1
l6 l0
R1
l6 l0
R2
l6 l0 l6 l0
R3
l6 l0 l6
even-numbered slots odd-numbered slots Antenna port 0
even-numbered slots
odd-numbered slots
even-numbered slots
odd-numbered slots
even-numbered slots
odd-numbered slots
Antenna port 1
Antenna port 2
Antenna port 3
Page 102
MCW SU-MIMO:
UE1 Codeword 1 Codeword 2
Data Data CRC Data CRC CRC
UE1 Codeword 1 Codeword 2 MIMO

CRC
MIMO
Data
Round trip time
The HARQ processing of MCW SU-MIMO
Tx UE1
0 8
1 9
2 10
3 11
4 12
5 13
6 14
7 15
0 8
1 9
2 10
3 11
4 12
5 13
6 14
7 15
Rx UE1
0 8
1 9
2 10
3 11
4 12
5 13
6 14
7 15
0 8
1 9
2 10
3 11
4 12
5 13
6 14
7 15
ACK/ NAK
ACK/ NAK ACK/ NAK
ACK/ NAK ACK/ NAK
ACK/ NAK ACK/ NAK
ACK/ NAK ACK/ NAK
ACK/ NAK ACK/ NAK
ACK/ NAK ACK/ NAK
ACK/ NAK ACK/ NAK
UE1
ACK/ NAK
Page 103
Codebook:
No
Codebook Entry
1
1 0
2
0 1
3
1 1
4
1 -1
5
1 j
6
1 -j
weight for: Ant.1 Ant.2
Phase
UE receives
only from Ant1 only from Ant2 same phase from both Ant. opposite phase from both Ant. Ant. phase is 900 less than Ant.1 Ant. phase is 900 more than Ant.1
Page 104
Beamforming:
Antenna 1
Antenna 2 Spread/Scramble One Stream
Detection
Beam 1
Beam Forming based on EBB Antenna 8
Detector
One Stream
Detection
Page 105
MultiUser-MIMO:
UE 1 UE 2 UE 3 UE 4
Data Data Data Data CRC
MIMO
CRC
Data
CRC
UE 1
MIMO
CRC CRC
MIMO
Data
CRC
UE 2
Round trip time
Tx
UE 1 UE 2 UE 3 UE 4
0 0 0 0
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
0 0 0 0
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
MIMO
Data
CRC
UE 3
MIMO
Data
CRC
UE 4
Rx
UE 1 UE 2 UE 3 UE 4
0 0 0 0
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
0 0 0 0
1 1 1 1
2 2 2 2
3 3 3 3
4 4 4 4
5 5 5 5
6 6 6 6
7 7 7 7
UE 1 UE 2 UE 3 UE 4
ACK/ NAK ACK/ NAK ACK/ NAK ACK/ NAK
HARQ processing for 4Tx MU-MIMO
Page 106
Bandwidths
Page 107
LTE offers system flexibility by supporting systems and UEs of multiple bandwidths:
20-MHz bandwidth BCH/SCH
10-MHz bandwidth
5-MHz bandwidth
3.0-MHz bandwidth
1.4 -MHz bandwidth
Page 108
LTE offers system flexibility by supporting systems and UEs of multiple bandwidths:
Example: 10 -MHz UE in 20 -MHz cell site, SCH bandwidth = 1.4 MHz and BCH bandwidth = 1.4 MHz Cell site with 20 -MHz transmission bandwidth Center carrier frequency
Step 1: Cell search using synchronization channel detect center 1.4 spectrum of entire 20 -MHz spectrum Step 2: BCH reception BCH reception
BCH SCH
Step 3: UE shifts to the center carrier frequency assigned by the system and initiates data transmission
Initiate data transmission using assigned spectrum
Page 109

Variable bandwidth scenarios:
eNB TX CCH TX UE1 RX
UE2 RX UE3 RX UE4 RX
eNB TX CCH TX BS CCH TX TX UE5 RX
BS CCH TX TX
UE6 RX BS CCH TX TX UE7 RX
20 MHz
Cell A
Cell B
Cell C
Cell D
Cell E
UEs with different frequencies and bandwidth assigned to e. g. cell A:

Page 110
Inter and Intra-frequency measurements scenarios:

Depending on whether the UE needs transmission/reception gaps to perform the relevant measurements, measurements are classified as gap assisted or non gap assisted. Non GAP
Scenario A current cell UE target cell
Scenario B current cell UE target cell
Scenario C current cell UE target cell
fc
fc
fc
fc
fc
fc
GAP
Scenario D current cell UE target cell
Scenario E current cell UE target cell
Scenario F current cell UE target cell
fc
fc
fc
fc
fc
fc
Page 111
System and UE parameter
Page 112
E-UTRA FDD and E-UTRA TDD reference eNB and UE parameters:

Parameter
Maximum BS power FDD
Value
43 dBm for 1.4, 3 and 5 MHz carrier 46 dBm for 10, 15 and 20 MHz carrier 32 dBm 15 dBm 43 dBm for 1.4, 3 and 5 MHz carrier 46 dBm for 10, 15 and 20 MHz carrier 32 dBm 24 dBm (Class 3) 21 dBm (Class 4) -30 dBm
Page 113
Max. power per DL traffic channel FDD Min. BS power per user Maximum BS power TDD
Max. power per DL traffic channel TDD Maximum UE power
Minimum UE power
Lte UE Categories:
UE classes Num. of MIMO streams Max. num. of RBs Peak data rate (Mbps) Soft buffer size
25
DL UL
5 2 43.2 14.4 86.4 28.8 172.8 57.6 326.4 86.4
FFS
25
DL UL
FFS
50
DL UL
FFS
100
DL UL
FFS
100
DL UL
FFS
Page 114
Lte UE Classes:
UE Classes: Number of MIMO streams: Max. number of resource blocks: Peak data rate (Mbps):
DL
UL
25 (*1)
5.0
2.0
43.2 (*2)
14.4 (*2)
50
86.4 (*2)
28.8 (*2)
100
172.8 (*2)
57.6 (*2)
326.4 (*2)
86.4 (*3)
Page 115
Lte UE Categories:
UE Category Maximum number of DL-SCH transport block bits received within a TTI 10296 51024 102048 150752 302752 Maximum number of bits of a DLSCH transport block received within a TTI 10296 51024 75376 75376 151376 Maximum number of bits of an UL-SCH transport block transmitted within a TTI 5160 25456 51024 51024 75376 Total number of soft channel bits 250368 1237248 1237248 1827072 3667200 Maximum number of supported layers for spatial multiplexing in DL 1 2 2 2 4
Category 1 Category 2 Category 3 Category 4 Category 5
UE Category
Support for 64QAM in UL
Category 1 Category 2 Category 3 Category 4 Category 5
No No No No Yes
Page 116
Interfaces and Nodes
Page 117
UTRAN SGSN GERAN S3 S1-MME S6a MME S11 LTE-Uu UE E-UTRAN S1-U S10 S12 S4 Serving Gateway S5 Gx PDN Gateway SGi PCRF Rx Operator's IP Services (e.g. IMS, PSS etc.) HSS
Page 118

Roaming Configuration:
S6a
HSS
H-PCRF
Rx
HPLMN VPLMN UTRAN GERAN

S1-MME
S9
Home Operators IP Services
SGSN
S3 S4 S12 Gx S11
V-PCRF
MME
S10
"LTE-Uu"
UE
E-UTRAN
S1- U
Serving Gateway
S5
PDN SGi Gateway
Visited Operator PDN
Page 119

Air interface is OFDMA (DL) / SC-FDMA (UL) in TDD and FDD
modes not TD-CDMA or W-CDMA as in 3G. No macro diversity (no soft handover). LTE is exclusively packet-switched and IP-based. Voice and other services previously delivered over the CS Core network in UMTS are provided via a packet switched IP core and IMS. CS Core network does not exist. A key target of SAE is the interworking of multiple access networks under the same packet-switched core network (GERAN, UTRAN, WLAN). So the SAE has two major goals: Become the Core Network for LTE. Integrate legacy 3GPP and non-3GPP access network in the same architecture.
Page 120
The RAN network elements are compressed and pushed to the network edge:
The NodeB and most of the RNC functions are combined to create an element known as the eNB. The Iu-PS interface in UMTS becomes the S1 interface in LTE. The S-GW takes the UP core network functions. The MME takes the Mobility management functions.
Page 121
REL.8: Lte (SAE):
In the System Architecture Evolution (SAE) network architecture, the Core network elements of SGSN and GGSN are replaced by a number of entities: The SGSN control-plane functions become the Mobility Management Entity (MME). Some RNC functions, the SGSN user plane functions and the GGSN are incorporated into the Serving Gateway (SGW) and 3GPP Anchor. The split of functionality between S-GW and 3GPP anchor is not decided. In addition there is an SAE Anchor, which provides the S2 interface for non-3GPP access systems such as WLAN, etc..
Page 122
eNB, MME:
The eNB hosts the following functions: Functions for Radio Resource Management: Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in both uplink and downlink (scheduling); IP header compression and encryption of user data stream; Selection of an MME at UE attachment when no routing to an MME can be determined from the information provided by the UE; Routing of User Plane data towards Serving Gateway; Scheduling and transmission of paging messages (originated from the MME); Scheduling and transmission of broadcast information (originated from the MME or O&M); Measurement and measurement reporting configuration for mobility and scheduling.
The MME hosts the following functions (see 3GPP TS 23.401): NAS signalling; NAS signalling security; AS Security control; Inter CN node signalling for mobility between 3GPP access networks; Idle mode UE reach ability (including control and execution of paging retransmission); Tracking Area list management (for UE in idle and active mode); 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; Authentication; Bearer management functions including dedicated bearer establishment.
Page 123
S-GW, PDN-GW:
The Serving Gateway (S-GW) hosts the following functions (see 3GPP TS 23.401): The local Mobility Anchor point for inter-eNB handover; Mobility anchoring for inter-3GPP mobility; E-UTRAN idle mode downlink packet buffering and initiation of network triggered service request procedure; Lawful Interception; Packet routeing and forwarding; Transport level packet marking in the uplink and the downlink; Accounting on user and QCI granularity for inter-operator charging; UL and DL charging per UE, PDN, and QCI. The PDN Gateway (P-GW) hosts the following functions (see 3GPP TS 23.401): Per-user based packet filtering (by e.g. deep packet inspection); Lawful Interception; UE IP address allocation; Transport level packet marking in the downlink; UL and DL service level charging, gating and rate enforcement; DL rate enforcement based on AMBR;
Page 124

Roaming Configuration
MME MME
EPC
S1- u GTP -P
eNB
X2-c (X2-AP )
X2-U data
S 1 GTP -U data tunnel
S - GW
eNB
EPC
PDN GW
Page 125
Power-up
Initial Cell search:
Initial Cell Search
E-UTRAN
UTRAN
GERAN
Non-3GPP access
Page 126
Initial Cell search:

PowerUp
Initial Cell Search
E-UTRAN Release C_RNTI
Cell association C_RNTI]
UTRAN
GERAN
Non 3GPP
Idle
Associate C_RNTI
Active
Page 127
QoS concept and bearer service architecture:

E - UTRAN EPC Internet
UE
eNB
S - GW
P - GW
Peer Entity
End -to - end Service
EPS Bearer
External Bearer
E-RAB
S 5/S 8 Bearer
Radio Bearer
S 1 Bearer
Radio
S1
S 5/ S 8
Gi
Page 128
SAE Bearer and QoS Concept for a Single UE:

eNB UE
Signaling Radio Bearers C -Plane Signalling MAC Scheduler
S -GW
Radio Bearers Policy based QoS handling and IP packet mux and demux above bearer level
QoS Flow 1
Prio 1 - Q
S1 Bearers
QoS Flow 1
Prio 2 - Q QoS Flow 2
Uu
Prio 3 - Q
S1
QoS Flow 2
QoS Flow 3
QoS Flow 3
Aggregated IP Flows
MAC Mux
Aggregated IP Flows
Policy based QoS handling and IP packet mux and demux above bearer level
VoIP Video Streaming
Best Effort 1n
SAE Bearer Service
Page 129
Two unicast EPS bearers (GTP-U based S5/S8):
Application / Service Layer UL Service Data Flows UL-TFT UL-TFT RB - ID RB -ID S1-TEID DL Service Data Flows DL-TFT DL-TFT S5/S8a-TEID S1-TEID S5/S8a-TEID
UE Radio Bearer
eNodeB eNB S1 Bearer
Serving GW S5/S8 Bearer
PDN GW
Page 130
Standardized QCI / Label Characteristics:

QCI (QoS Class Identifier) 1 (NOTE 3) 2 (NOTE 3) 3 (NOTE 3) 4 (NOTE 3) 5 (NOTE 3) Resource Type Priority Packet Delay Budget (NOTE 1) 100 ms 150 ms 50 ms 300 ms 100 ms Packet Loss Rate (NOTE 2) 10-2 10-3 10-3 10-6 10-6 Example Services
2 4 GBR 3 5 1
Conversational Voice Conversational Video (Live Streaming) Real Time Gaming Non-Conversational Video (Buffered Streaming) IMS Signaling Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.) Voice, Video (Live Streaming), Interactive Gaming Video (Buffered Streaming) TCP-based (e.g., www, e-mail, chat, ftp, p2p file sharing, progressive video, etc.)
Page 131
6 (NOTE 3)
7 (NOTE 3) 8 (NOTE 5) 9 (NOTE 6)
Non-GBR
300 ms
10-6
7 8
100 ms
10-3
Non-GBR
9
300 ms
10-6
Mapping between standardized QCIs and pre-Rel-8 QoS parameter values:
QCI 1 2 FFS 3
Traffic Class Conversational Conversational Streaming Streaming
Traffic Handling Priority N/A N/A N/A N/A
Signaling Indication N/A N/A N/A N/A
Source Statistics Descriptor Speech Unknown Speech Unknown
5
7 6 8
Interactive
Interactive Interactive Interactive
1
1 2 3
Yes
No No No
N/A
N/A N/A N/A
Background
N/A
N/A
N/A
Page 132
QoS ARCHITECTURE:
QoS Profile + Bearer ID
QoS Profile + Bearer ID
QoS Profile
Subscriber ID + Service Flow Information
UE
Activate or Modify Radio Bearer
eNB
Activate or Modify Access Bearer
aGW
Apply Policy
PCRF
Session Authorisation
AF
Subscriber ID + Service Flow Information
Page 133
Security in 2G, 3G, Lte:

eUE 2G Security
2G Radio
2G BSENode BS 3G Security
SGSN
3G Radio
RNC
3G RAN LTE RRC Security

eNB interworking NAS security anchor
SAE Core
LTE Radio NAS handler
LTE RAN
UP security anchor
SAE NAS Security SAE UP Security
UP handler
lower layers higher layers
Page 134
Lte Security Architecture:
(IV)
User Application
Provider Application
Application stratum
(I) (III)
(I)
USIM
(II) (I) (I)
HE SN
(II)
Home stratum/ Serving Stratum
ME
(I)
AN
(I)
Transport stratum
Page 135
Security in Lte:
USIM / AuC
CK, IK
UE / HSS
KASME
UE / ASME
KNAS enc KNAS int KeNB
UE / MME
K CK IK KASME KNAS enc KNAS int KeNB KeNB-UP-enc KeNB-RRC-int KeNB-RRC-enc : Permanent stored in USIM & AuC : Cipher Key : Integrity Key : Access Security Management Entity : NAS Encryption : NAS Integrity : eNB Master Key : eNB User Plane Encryption : eNB RRC Integrity : eNB RRC Encryption
KeNB-UP-enc
KeNB-RRC- int
KeNB-RRC-enc
UE / eNB
Page 136
Security in Lte: (Network nodes)

HSS
network-ID
KeNB* Ks
256 256
256
KeNB
eNB
KDF
256 Physical cell ID 256
KDF
eNB
MME
256
256
KASME
256 NAS COUNT
KD F
KeNB
UP-enc-alg, Alg-ID RRC-int-alg, Alg-ID
NAS-enc-alg, Alg-ID
NAS-int-alg, Alg-ID
RRC-enc-alg, Alg-ID
KDF
256
KDF
256
KDF
256
KDF
256
KDF
256
256-bit keys
KNASenc
256
KNASint
256
256-bit keys
KRRCenc
256
KRRCint
256
KUPenc
256
Trunc
128
Trunc
128
Trunc
128
Trunc
128
Trunc
128
128-bit keys
KNASenc
KNASint
128-bit keys
KRRCenc
KRRCint
KUPenc
Page 137
Security in Lte: (UE)

ME Ks
256
KeNB*
network-ID
256
256
KDF
Physical cell ID 256 256
KDF
256
KASME
256 NAS COUNT
KD F
KeNB
UP-enc-alg, Alg-ID RRC-int-alg, Alg-ID RRC-enc-alg, Alg-ID
256
NAS-enc-alg, Alg-ID
NAS-int-alg, Alg-ID
KDF
256
KDF
256
KDF
256
KDF
256
KDF
256
256-bit keys
KNASenc
256
KNASint
256
256-bit keys
KRRCenc
256
KRRCint
256
KUPenc
256
Trunc
128
Trunc
128
Trunc
128
Trunc
128
Trunc
128
128-bit keys
KNASenc
KNASint
128-bit keys
KRRCenc
KRRCint
KUPenc
Page 138
Security termination points:
MME
S1-CP, Xu-C: NAS Ciphering & Integrity Protection
S-GW
S1-C
S1-U
eNB
X2
eNB
Xu-CP/UP: RRC, UP Ciphering & RRC Integrity Protection
X2-CP/UP: UP, CP Ciphering & CP Integrity Protection
UE
Page 139
Security Termination Points:

Ciphering NAS Signalling U-Plane Data RRC Signalling Required and terminated in MME Required and terminated in eNB Required and terminated in eNB Integrity Protection Required and terminated in MME Not Required Required and terminated in eNB
MAC Signalling
Not required
Not required
Page 140
Protocols and Procedures
Page 141
HSS H-PCRF
S6a
HPLMN
S9
VPLMN
UTRAN GSN GERAN

S3 S1-MME S4
V-PCRF
S12 Gx Rx
MME
S11 S10 LTE-Uu
S5
SGi
UE
E-UTRAN
S1-U
Serving Gateway
PDN Gateway
Visited Operator's IP Services
Page 142
Lte C-Plane
NAS RRC PDCP RLC MAC Radio UE Xu RRC PDCP RLC MAC Radio eNB S1-AP
NAS
S1-AP GTP-C GTP-C
SCTP
IP4/6
Ethernet
SCTP
IP4/6
Ethernet
UDP
IP4/6
Ethernet
UDP
IP4/6
Ethernet
S1
MME/S-GW
S-GW
Red indicates modifications! * MAC and RLC may be simplified

Page 143
Lte U-Plane
IP4/6 IP4/6
PDCP
RLC
PDCP
GTP-U RLC UDP UDP IP4/6 GTP-U
MAC
MAC
IP4/6
Radio UE
Radio
Ethernet
S1
Ethernet S-GW
eNB Xu Red indicates modifications!
Page 144
REL.8: Lte:
Protocol Stack user plane: GTP-U
UE IP PDCP RLC MAC PHY
eNB
S-GW
PDCP GTP-U RLC MAC PHY UDP IP UDP IP GTP-U
S1-U
Page 145
Protocol Stack UE:

NAS
Mobility & Bearer control layer
NAS_SEC SAP -c
IP
IP layer
NAS_SEC
RRCSAP PDC P-u SAP
RRC
PDC SAP P-c
Radio netw ork layer
C PDC P
PDC P
C RLC
RLC SAP -c
RLC SAP -u
RLC
Radio link layer
MAC SAP -c
MAC SAP -u
C MAC
MAC
Physical layer
PHY SAP
C PHY
PHY
Page 146
REL.8: Lte:
Protocol Stack signaling plane:
UE NAS eNB MME NAS
RRC
RRC
S1-AP
S1-AP
PDCP
PDCP
RLC
RLC
SCTP
SCTP
MAC
MAC
PHY
PHY
IP
IP
Page 147
REL.8: Lte (Functional split):

eNB Inter Cell RRM Connection Mobility Cont. RB Control Radio Admission Control SAE Bearer Control MM Entity Dynamic Resource Allocation (Scheduler) RRC Ciphering PDCP RLC RLC MAC MAC S1 PHY PHY User Plane eNB Measurement Configuration & Provision SAE Core Network
UE
MME
Ciphering
SAE Bearer Control S1 MM Entity S-GW
PDCP
User Plane
Page 148
Functional Split between E-UTRAN and EPC:

eNB Inter Cell RRM RB Control Connection Mobility Cont. MME Radio Admission Control NAS Security eNB Measurement Configuration & Provision Dynamic Resource Allocation (Scheduler) RRC PDCP S-GW RLC MAC S1 PHY Packet Filtering internet E-UTRAN EPC Mobility Anchoring UE IP address allocation P-GW Idle State Mobility Handling SAE Bearer Control
Page 149
REL.8: Lte (E-UTRAN architecture):
EPC MME / S-GW MME / S-GW
X2
eNB eNB
S1
eNB
X2
S1
S1
X2
Many to many configuration!

Page 150
S1
E-UTRAN
Control Plane for S3, S4, S5 S8a, S10, S11 Interfaces (SGSN MME, SGSN Serving GW, Serving GW - PDN GW, MME MME, MME - Serving GW ):
GTP-C
GTP-C
UDP IP4/6
Ethernet
UDP
IP4/6
Ethernet
S3, S4, S5, S8a, S10, S11 * IPSec optional, possible IP4
Page 151
UE PDN GW user plane:
Appl. IP PDCP RLC MAC

Radio
IP PDCP RLC MAC

Radio
GTP-U UDP IP4/6

Ethernet
GTP-U GTP-U UDP IP4/6

Ethernet
GTP-U UDP IP4/6

Ethernet
UDP IP4/6
Ethernet
Xu UE eNB * IPSec optional, possible IP4
S1-U S-GW
S5, S8a PDN-GW
SGi
Page 152
UE PDN GW user plane with 2G/3G access via S4 interface:
Appl.
IP
SNDCP
*
IP
GTP-U UDP
LLC
RLC
MAC
Radio
RLC BSSGP
MAC
Radio
SNDCP GTP-U LLC UDP BSSGP
GTP-U GTP-U UDP

*
UDP IP4/6
*
NS
L1
NS
L1
IP4/6
Ethernet
IP4/6
IP4/6
Ethernet
Ethernet Ethernet
Um UE BSS
Gb SGSN
S4 Serving-GW
S5
SGi PDN-GW
* IPsec optional, possible IP4

Page 153
User Plane for UTRAN mode and Direct Tunnel on S4-U:
Appl. IP PDCP PDCP GTP-U RLC UDP GTP-U GTP-U UDP IP4/6
L1
IP GTP-U GTP-U UDP IP4/6

L1
GTP-U UDP IP4/6

L1
RLC
MAC
Radio
UDP IP4/6
L1
UDP IP4/6
L1
MAC IP4/6
Radio L1
Uu UE UTRAN
Iu SGSN
S4 Serving-GW
S5
SGi PDN-GW
Direct tunnel between UTRAN and S-GW

Page 154
S1-AP (S1 Application Protocol) (TS 36.413):

An EP (Elementary Procedure) consists of an initiating message and possibly a response message. Two kinds of EPs are used: Class 1: Elementary Procedures with response (success and/or failure). Class 2: Elementary Procedures without response. For Class 1 EPs, the types of responses can be as follows: Successful: A signalling message explicitly indicates that the elementary procedure successfully completed with the receipt of the response. Unsuccessful: A signalling message explicitly indicates that the EP failed. On time supervision expiry (i.e. absence of expected response). Successful and Unsuccessful: One signalling message reports both successful and unsuccessful outcome for the different included requests. The response message used is the one defined for successful outcome.
Class 2 EPs are considered always successful.
Page 155
S1-AP Class 1 Procedures:

Elementary Procedure:
Handover Preparation Handover Resource Allocation Path Switch Request
Initiating Message:
Successful Outcome: Response message:
Unsuccessful Outcome: Response message:

HANDOVER PREPARATION FAILURE HANDOVER FAILURE PATH SWITCH REQUEST FAILURE
HANDOVER REQUIRED HANDOVER REQUEST PATH SWITCH REQUEST
HANDOVER COMMAND HANDOVER REQUEST ACKNOWLEDGE PATH SWITCH REQUEST ACKNOWLEDGE
Handover Cancellation
E-RAB Setup E-RAB Modify E-RAB Release Initial Context Setup Reset S1 Setup UE Context Release UE Context Modification eNB Configuration Update MME Configuration Update Write-Replace Warning
HANDOVER CANCEL
E-RAB SETUP REQUEST E-RAB MODIFY REQUEST E-RAB RELEASE COMMAND INITIAL CONTEXT SETUP REQUEST RESET S1 SETUP REQUEST UE CONTEXT RELEASE COMMAND UE CONTEXT MODIFICATION REQUEST ENB CONFIGURATION UPDATE MME CONFIGURATION UPDATE WRITE-REPLACE WARNING REQUEST
HANDOVER CANCEL ACKNOWLEDGE

E-RAB SETUP RESPONSE E-RAB MODIFY RESPONSE E-RAB RELEASE COMPLETE INITIAL CONTEXT SETUP RESPONSE RESET ACKNOWLEDGE S1 SETUP RESPONSE UE CONTEXT RELEASE COMPLETE UE CONTEXT MODIFICATION RESPONSE ENB UPDATE CONFIGURATION ACKNOWLEDGE MME CONFIGURATION UPDATE ACKNOWLEDGE WRITE-REPLACE WARNING RESPONSE UE CONTEXT MODIFICATION FAILURE ENB CONFIGURATION UPDATE FAILURE MME CONFIGURATION UPDATE FAILURE S1 SETUP FAILURE INITIAL CONTEXT SETUP FAILURE
Page 156
S1-AP Class 2 Procedures:

Handover Notification E-RAB Release Request Paging Initial UE Message Downlink NAS Transport HANDOVER NOTIFY E-RAB RELEASE REQUEST PAGING INITIAL UE MESSAGE DOWNLINK NAS TRANSPORT
Message:
Uplink NAS Transport

NAS non delivery indication Error Indication UE Context Release Request DownlinkS1 CDMA2000 Tunneling Uplink S1 CDMA2000 Tunneling
UPLINK NAS TRANSPORT

NAS NON DELIVERY INDICATION ERROR INDICATION UE CONTEXT RELEASE REQUEST DOWNLINK S1 CDMA2000 TUNNELING UPLINK S1 CDMA2000 TUNNELING
UE Capability Info Indication

eNB Status Transfer MME Status Transfer Deactivate Trace Trace Start Trace Failure Indication
UE CAPABILITY INFO INDICATION

eNB STATUS TRANSFER MME STATUS TRANSFER DEACTIVATE TRACE TRACE START TRACE FAILURE INDICATION
Location Reporting Control

Location Reporting Failure Indication Location Report Overload Start Overload Stop eNB Direct Information Transfer
LOCATION REPORTING CONTROL

LOCATION REPORTING FAILURE INDICATION LOCATION REPORT OVERLOAD START OVERLOAD STOP eNB DIRECT INFORMATION TRANSFER
MME Direct Information Transfer
MME DIRECT INFORMATION TRANSFER
Page 157
S1 Tunneling GTP:
Per bearer Mobility tunnels:
UE eNB Serving GW
Single Mobility tunnel per UE-PDN

UE eNB
Serving GW
It is proposed that a single mobility tunnel is utilized between eNB and S-GW for each active UE-PDN connection. All SAE bearers associated with the same UE-PDN connection are mapped to this single Mobility tunnel over the S1-u interface.
Page 158
Lte X2-Planes
X2-AP SCTP IP4/6

Ethernet
GTP-U UDP IP4/6

Ethernet
X2-AP SCTP * IP4/6

Ethernet
GTP-U UDP IP4/6

Ethernet
eNB
X2
eNB
* IPsec optional
Red indicates modifications!
Page 159
X2-AP:
X2 Procedures and Messages Class 1 (TS 36.423):
Elementary Procedure Handover Preparation Reset X2 Setup eNB Configuration Update Resource Status Reporting Initiation Initiating Message Successful Outcome Response message HANDOVER REQUEST RESET REQUEST X2 SETUP REQUEST ENB CONFIGURATION UPDATE RESOURCE STATUS REQUEST HANDOVER REQUEST ACKNOWLEDGE RESET RESPONSE X2 SETUP RESPONSE ENB CONFIGURATION UPDATE ACKNOWLEDGE RESOURCE STATUS RESPONSE X2 SETUP FAILURE ENB CONFIGURATION UPDATE FAILURE Unsuccessful Outcome Response message HANDOVER PREPARATION FAILURE
RESOURCE STATUS FAILURE
Page 160
X2-AP:
X2 Procedures and Messages Class 2 (TS 36.423):
Load Indication Handover Cancel SN Status Transfer UE Context Release Resource Status Reporting Error Indication
Initiating Message:
LOAD INFORMATION HANDOVER CANCEL SN STATUS TRANSFER UE CONTEXT RELEASE RESOURCE STATUS UPDATE ERROR INDICATION
Page 161
U-Plane Xu
PDCP RLC MAC-d MAC-hs/e PHY
RLC E-PDCP
Transparent or simplified simplified E-MAC E-PHY
Release 6
E-UTRA
Page 162
~ Rel.6 (HSxPA)
E-RLC E-PDCP
Header compression and decompression of IP data streams Buffering of transmitted PDCP SDU Maintenance of transmitted and received PDCP SDU Segmentation and reassembly Concatenation / Padding Error correction (ARQ) In-sequence delivery Flow control Sequence number check SDU discard Duplicate detection Ciphering
E-UTRAN
Header compression and decompression of IP data streams Buffering of transmitted E-PDCP SDU Maintenance of transmitted and received E-PDCP SDU Null or Transparent operation Segmentation and reassembly Concatenation / Padding Mux. of logical channels Ciphering HARQ (including in-sequence delivery, SN check, SDU discard, duplicate detection) Flow control Scheduling/priority handling Transport format selection
RLC
PDCP
MAC-hs/e
HARQ Flow control Scheduling/priority handling TFRC selection
E-MAC
Some functions are integrated, others are added.
Page 163
UMTS
Transport Channel type switching C/T MUX Priority setting Ciphering (for RLC-TM) Deciphering (for RLC-TM) DL scheduling/priority handling Flow control Scheduling/priority handling TCTF MUX UE id MUX MBMS Id Mux TFC selection Demultiplex DL code allocation Flow control Flow control Scheduling/priority handling HARQ TFRC selection Reordering Queue Distribution Reordering Macro diversity selection Disassembly E-DCH Scheduling E-DCH Control De-multiplexing HARQ
Lte
MAC-d
MAC-e
MAC-es MAC-hs
De-multiplexing Reordering Disassembly C/T MUX Priority setting TCTF MUX UE id MUX Ciphering / Deciphering Scheduling/priority handling HARQ Transport format selection Reordering Queue Distribution
MAC-c/sh/m
E-MAC
Page 164
Lte Signalling Connections:

CELL
Signalling may be received by all UEs in the Cell
BCCH PCCH
eNB1
S1-AP
Connectionless Signalling
MME
UE1
UE1 NAS UE1 RRC
UE1 NAS Signalling (Actually carried over UE1 [S1-AP + RRC DCCH2])
DCCH1 DCCH2
UE1 NAS UE1 S1-AP
UE1 S1-AP Connection Oriented Signalling
UE2
UE2 NAS UE2 RRC
UE2 NAS Signalling (Actually carried over UE2 [S1-AP + RRC DCCH2])
DCCH1 DCCH2
UE2 NAS
UE2 S1-AP Connection Oriented Signalling
UE2 S1-AP
UEn
UEn NAS UEn RRC
UEn NAS Signalling (Actually carried over UEn [S1AP + RRC DCCH2])
DCCH1 DCCH2
UEn NAS
UEn S1-AP Connection Oriented Signalling X2-AP

(eNB1 eNB2)
UEn S1-AP
eNB2
Page 165
Concatenation or parallel execution of RRC procedures:

UE
RRC Connection Request RRC Connection Setup C-plane Establishment
RAN
CN
UE
eNB
CN
RRC Connection Setup Complete

Initial Direct Transfer(GMM) Security Mode Command Security Mode Complete L2 STAT UL Direct Transfer(SM) Radio Bearer Setup U-plane Establishment Service Request(GMM) Security Mode Command Security Mode Complete
Enhanced RRC NAS connection request
Enhanced RRC NAS connection response
U-plane Establishment
Active PDP Context Request(SM) RAB Assignment Request
Radio Bearer Setup Complete

DL Direct Transfer(SM)
RAB Assignment Response

Active PDP Context Accept(SM)
U-plane Establishment
Call Setup Procedure in UTRAN
Call Setup Procedure in E-UTRAN

Page 166
REL.8: Lte (Attach and PDP Activation (one step access)):

S1c
MME
S10
S6
HSS
S5/S8
UE
Xu
eNB
S1u
S-GW
IASA
1. Attach Request (APN) 2. Authentication 3. Update Location 4. Insert Subscriber Data 5. Insert Subscriber Data Ack 6. Update Location Ack 7. Attach Request (APN, UPE + RRC keys) 8. Bearer Request 9. PCRF Interaction 12. RRC (radio resource info, QoS info) 10. Bearer Response 11. Radio Bearer Request (QoS, RRC keys) 13. Radio Bearer Confirm 14. Attach Accept (IP configuration) 15. Attach Accept (IP configuration) 16. Attach Complete
Page 167
ATTACH PROCEDURE:
UE eNodeB new MME Old MME/SGSN EIR 3. Identification Request 3. Identification Response 4. Identity Request 4. Identity Response 5a. Authentication / Security 5b. Identity Request/Response 5b. ME Identity Check Serving GW PDN GW PCRF HSS 1. Attach Request 2. Attach Request
6. PCO and/or APN Request 6. PCO and/or APN Response 7. Delete Bearer Request 7. Delete Bearer Response 8. Update Location Request 9. Cancel Location 9. Cancel Location Ack 10. Delete Bearer Request 10. Delete Bearer Response 11. Update Location Ack 12. Create Default Bearer Request 13. Create Default Bearer Request
14. PCEF Initiated IP-CAN Session Establishment 10. PCEF Initiated IP-CAN Session Termination
7. PCEF Initiated IP-CAN Session Termination
(A)
(B)
(C) 15. Create Default Bearer Response First Downlink Data (if not handover) 16. Create Default Bearer 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. Update Bearer Request 23a. Update Bearer Request 23b. Update Bearer Response (D) 24. Update Bearer Response First Downlink Data 25. Notify Request 26. Notify Response
Page 168
Tracking Area Update procedure with Serving GW change:

UE eNodeB new MME 1. UE changes to a new Tracking Area 2. TAU Request 3. TAU Request 4. Context Request 5. Context Response 6. Authentication 7. Context Acknowledge 8. Create Bearer Request 9. Update Bearer Request 10. Update Bearer Response 11. Create Bearer Response 12. Update Location 13. Cancel Location 14. Cancel Location Ack 15. Update Location Ack 16. Delete Bearer Request (B) 18. TAU Accept 19. TAU Complete 17. Delete Bearer Response (A) old MME/ old S4 SGSN new Serving GW old Serving GW PDN GW HSS
Page 169
Tracking Area Update procedure with MME and Serving GW change:

UE eNodeB new MME old MME new Serving GW old Serving GW PDN GW HSS
1. UE changes to a new Tracking Area 2. TAU Request 3. TAU Request 4. Context Request 5. Context Response 6. Authentication 7. Context Acknowledge 8. Create Bearer Request 9. Update Bearer Request 10. Update Bearer Response 11. Create Bearer Response 12. Update Location 13. Cancel Location 14. Cancel Location Ack 15. Insert Subscriber Data 15. Insert Subscriber Data Ack 16. Update Location Ack 17. Delete Bearer Request (B) 19. TAU Accept 20. TAU Complete
Page 170
(A)
18. Delete Bearer Response
MTC:
UE
Paging
eNB
Paging
MME
Random Access Procedure

NAS: Service Request
S1-AP: INITIAL UE MESSAGE (FFS) + NAS: Service Request + eNB UE S1AP ID S1-AP: INITIAL CONTEXT SETUP REQUEST + (NAS message) + eNB UE S1AP ID + MME UE S1AP ID + Security Context + UE Capability Information (FFS) + Bearer Setup (Serving SAE-GW TEID, QoS profile) S1-AP: INITIAL CONTEXT SETUP COMPLETE + eNB UE S1AP ID + MME UE S1AP ID + Bearer Setup Confirm (eNB TEID)
Page 171
RRC: Connection Setup (NAS Message)
RRC: Connection Setup Complete
REL.8: Lte:
Call Release:
UE
eNB
MME
S-GW
RRC: Uplink Direct Transfer (SIP-signalling)
S1-AP: Direct Transfer (SIP signaling)
S1-AP: S1 Release Command Prepare for Idle transition
RRC: RRC Conection Release (DL-SCH) S1-AP: S1 Relase Complete
Update U-Plane Routing

Remove UPE UE tunnel
Set UE to LTE_IDLE or LTE_DETACHED
Release all UE resources
Update U-Plane Routing Response

Set UE to LTE_IDLE or LTE_DETACHED
Page 172
Inter eNB handover without MME and without Serving GW relocation:

Source eNB Target eNB Downlink and uplink data Serving GW
UE
MME
PDN GW
Handover preparation
Handover execution Forwarding of data
Downlink data
Uplink data 1 Path Switch Request 2 User Plane Update Request 3 User Plane Update Response Downlink data 4. End marker
Handover completion
4. End marker 5 Path Switch Request Ack 6 Release Resource
7. Tracking Area Update procedure
Page 173
REL.8: Lte:
UE Source eNB Target eNB MME Serving Gateway 0. Area Restriction Provided RRC Conn. Reconf. incl. 1. mobilityControl information packet data packet data Legend L3 signalling L1/L2 3. HO decision 4. Handover Request 5. Admission Control 6. Handover Request Ack DL allocation 7. RRC Conn. Reconf. incl. mobilityControlinformation Deliver buffered and in transit packets to target eNB 8. SN Status Transfer signalling
HandOver:
UL allocation 2. Measurement Reports
User Data
Data Forwarding
Buffer packets from Source eNB 9. 10. 11. Synchronisation UL allocation + TA for UE
RRC Conn. Reconf. Complete
12. Path Switch Request
13. User Plane update request
End Marker
15.User Plane update response 16.Path Switch Request Ack
17. UE Context Release Flush DL buffer, continue delivering in - transit packets
Data Forwarding End Marker
18. Release Resources packet data packet data
Handover Completion
14.
Switch DL path
Handover Execution
Detach from old cell and synchronize to new cell
Handover Preparation
Page 174
Inter-eNB Handover with CN Node re-location:

UE Source eNB Target eNB Source MME Target MME Source Serving GW Target Serving GW PDN GW HSS Downlink User Plane data 1. Decision to trigger a relocation via S1 2. Handover Required 3. Forward Relocation Request 4. Create Bearer Request 4a. Create Bearer Response 5. Handover Request 5a. Handover Request Acknowledge 6. Create Bearer Request 6a. Create Bearer Response 7. Forward Relocation Response . 8. Create Bearer Request 8a. Create Bearer Response 9. Handover Command 10. Handover Command 11a. Only for Direct forwarding of data 11b. Only for Indirect forwarding of data Detach from old cell and synchronize to new cell 12. Handover Confirm Downlink data Uplink User Plane data 13. Handover Notify 14. Forward Relocation Complete 14b. Forward Relocation Complete Acknowledge 15. Update Bearer Request 16. Update Bearer Request
(A) 16a. Update Bearer Response 17. Update Bearer Response
Downlink User Plane data 18. Tracking Area Update procedure 19b. Delete Bearer Request 19a. Release Resources (B) 19c. Delete Bearer Response
Page 175
EUTRAN to UTRAN/GERAN Handover:

UE eNB MME SGSN Target RAN SAEGW
1. Reloc. Required [SAE bearer info...] 2. Create PDP Context Request 3. Create PDP Context Response 4. Forwd Reloation. req. [PDP Context info...] 6. Allocation of Radio resources 7. Reloation. req Ack 8. Forwd Reloc. Resp 10. HO Command 9. Reloc. Command 11. Data forwarding (opt.) (one tunnel per UMTS RAB) 12. Relocation Compl. 13 Update PDP Context Request 14 Update PDP Context Resp
5. Reloation. req.
15. Forwd Reloc Compl 16.Reloc. Complete
17. Mobility tunnel release
Page 176
Inter RAT handover:

UE Source eNodeB Target RNC Source MME Target SGSN Serving GW Target Serving GW PDN GW HSS
Uplink and Downlink User Plane PDUs 1. Handover Initiation 2. Handover Required 3. Forward Relocation Request 4. Create PDP Context Request 4a. Create PDP Context Response 5. Relocation Request 5a. Relocation Request Acknowledge 6. Create PDP Context Request 6a. Create PDP Context Response 7. Forward Relocation Response 8. Create Bearer Request 8a. Create Bearer Response
E-UTRAN to UTRAN Iu mode Inter RAT HO, preparation phase
Page 177
E-UTRAN to UTRAN Iu mode Inter RAT HO, execution phase:

UE Source eNB Target RNC Source MME Target SGSN Serving GW Target Serving GW PDN GW HSS
Uplink and Downlink User Plane PDUs
1. Handover Command 2. HO from-E-UTRAN Command 3. Forward SRNS Context 4. UTRAN Iu Access Procedures
4a. Handover to UTRAN Complete Sending of uplink data possible
3a. Forward SRNS Context 3b. Forward SRNS Context 3c. Forward SRNS Context Ack 3d. Forward SRNS Context Ack Downlink User Plane PDUs
Only if Direct Forwarding is applicable
Only if Indirect Forwarding is applicable. For "Indirect Forwarding", Serving GW Forwarding" and Serving GW Via Target SGSN in case Direct Tunnel is not used relocation the PDUs will be forwarded by the source Serving 5. Relocation Complete GW to target Serving GW and then to Target RNC when Direct 6. Forward Relocation Complete Tunnel is used, Target SGSN 6a. Forward Relocation Complete Acknowledge when Direct Tunnel is not used.
7. Update PDP Context Request

In case of Serving GW relocation Step 7, 8 and 9, and the following User Plane path, will be handled by Target Serving GW
8. Update Bearer Request

(A)
8a. Update Bearer Response
9. Update PDP Context Response

Uplink and Downlink User Plane PDUs (Via Target SGSN in case Direct Tunnel is not used)
10. Routing Area Update procedure 11. Delete Bearer Request 11b. Release Resources 11a. Delete Bearer Response
(B)
Page 178
UTRAN Iu mode to E-UTRAN Inter RAT HO, preparation phase:
UE
Source RNC
Target eNodeB
Source SGSN
Target MME
Serving GW
Target Serving GW
PDN GW
HSS
Uplink and Downlink User Plane PDUs (via Source SGSN in case Direct Tunnel is not used)
1. Handover Initiation 2. Relocation Required 3. Forward Relocation Request 4. Create Bearer Request 4a. Create Bearer Response 5. Handover Request 5a. Handover Request Acknowledge 6. Create Bearer Request 6a. Create Bearer Response 7. Forward Relocation Response 8. Create Bearer Request 8a. Create Bearer Response
Page 179
UTRAN Iu mode to E-UTRAN Inter RAT HO, execution phase:

UE Source RNC Target eNodeB Source SGSN Target MME Serving GW Target Serving GW PDN GW HSS Uplink and Downlink User Plane PDUs (via Source SGSN in case Direct Tunnel is not used) 1. Relocation Command 2. HO from UTRAN Command 3. Forward SRNS Context 3a. Forward SRNS Context 4. E-UTRAN Access Procedures 3b. Forward SRNS Context Ack 3c. Forward SRNS 5. HO to E-UTRAN Complete Context Downlink Payload User Plane PDUs (via Source SGSN in case Direct Tunnel is not used)
Sending of uplink data possible
Only if Direct Forwarding is applicable
Via Source SGSN in case Direct Tunnel is not used 6. Handover Notify 7. Forward Relocation Complete 7a. Forward Relocation Complete Acknowledge 8. Update Bearer Request
In case of Serving GW relocation Step 8, 9 and 10, and the following User Plane path, will be handled by Target Serving GW
Only if Indirect Forwarding is applicable. For "Indirect Forwarding" and Serving GW relocation the PDUs will be forwarded by the source Serving GW to target Serving GW and then to Target eNodeB
9. Update Bearer Request (A) 9a. Update Bearer Response 10. Update Bearer Response
Uplink and Downlink User Plane PDUs

TAU Procedure
11. Tracking Area Update Request 12. Security functions 12. Security functions 13. Update Location 14. Cancel Location 15. Iu Release Procedure 14a. Cancel Location Ack 16. Delete PDP Context Request
Only in case of Serving GW relocation
(B) 16a. Delete PDP Context Response 17. Insert Subscriber Data 17a. Insert Subscriber Data Ack 18. Update Location Ack
19. Tracking Area Update Accept 20. Tracking Area Update Complete
Page 180
E-UTRAN to GERAN A/Gb Inter RAT HO, preparation phase:
UE
Source eNodeB
Target BSS
Source MME
Target SGSN
Target Serving GW Serving GW
PDN GW
HSS
Uplink and Downlink User Plane PDUs 1. Handover Initiation 2. Handover Required 3. Forward Relocation Request 4. Create PDP Context Request 4a. Create PDP Context Response 5. PS Handover Request 5a. PS Handover Request Acknowledge 6. Create PDP Context Request 6a. Create PDP Context Response 7. Forward Relocation Response 8. Create Bearer Request 8a. Create Bearer Response
Page 181
E-UTRAN to GERAN A/Gb mode Inter RAT HO, execution phase:

UE Source eNodeB Target BSS Source MME Target SGSN Serving GW Target Serving GW PDN GW HSS Uplink and Downlink User Plane PDUs 1. Handover Command 2. HO from E-UTRAN Command 3. Forward SRNS Context 4. GERAN A/Gb Access Procedures 3b. Forward SRNS Context Ack 5. XID Response Downlink User Plane PDUs Sending of uplink data possible Only if Direct Forwarding is applicable Only if Indirect Forwarding is applicable. For Indirect Forwarding and Serving GW relocation the PDUs will be forwarded by the source Serving GW to target Serving GW and then to Target SGSN 3a. Forward SRNS Context
6. PS Handover Complete 7. XID Response 8. Forward Relocation Complete
8a. Forward Relocation Complete Acknowledge 9. Update PDP Context Request In case of Serving GW relocation Step 9, 10 and 11, and the following User Plane path, will be handled by Target Serving GW 12. XID Negotioation for LLC ADM 12a. SABM UA exchange (re-establishment and XID negotiation for LLC ABM) Uplink and Downlink User Plane PDUs 13. Routeing Area Update Request 14. Security functions 14. Security functions 15. Update Location 16. Cancel Location 17. Release Resource 16a. Cancel Location Ack 18. Delete Bearer Request Only in case of Serving GW relocation 18a. Delete Bearer Response 19 Insert Subscriber Data 19a Insert Subscriber Data Ack 20. Update Location Ack 21. Routing Area Update Accept 22. Routing Area Update Complete (B) RAU Procedure 10. Update Bearer Request (A) 10a. Update Bearer Response 11. Update PDP Context Response
Page 182
GERAN A/Gb mode to E-UTRAN inter RAT HO, preparation phase:
UE
Source BSS
Target eNodeB
Source SGSN
Target MME
Target Serving GW Serving GW
PDN GW
HSS
Uplink and Downlink User Plane PDUs 1. Handover Initiation 2. PS Handover Required 3. Forward Relocation Request 4. Create Bearer Request 4a. Create Bearer Response 5. Handover Request 5a. Handover Request Acknowledge 6. Create Bearer Request 6a. Create Bearer Response 7. Forward Relocation Response 8. Create Bearer Request 8a. Create Bearer Response
Page 183
GERAN A/Gb mode to E-UTRAN Inter RAT HO, execution phase:

UE Source BSS Target eNodeB Source SGSN Target MME Serving GW Target Serving GW PDN GW HSS Uplink and Downlink User Plane PDUs
Only if Direct Forwarding is applicable Only if Indirect Forwarding is applicable In case of Indir ect Forwarding and Serving GW relocation the PDUs will be forwarded by the source Serving GW to target Serving GW and then to Target eNodeB
1. PS HO Required Acknowledge 2. PS Handover Command 4. E - UTRAN Access Procedures 3. Forward SRNS Context 3 a . Forward SRNS C ontext Ack 3b. Forward SRNS Context 5. HO to E -UTRAN Complete Sending of uplink data possible 6. Handover Notify 7. Forward Relocation Complete
7a. Forward Relocation Complete Acknowledge
8. Update PDP Context Request 9. Update Bearer Request

In case of Serving GW relocation Step 8, 9 and 10, and the following User Plane path, will be handled by Target Serving GW"
(A)
9a. Update Bearer Response
10. Update PDP Context Response

User Plane PDUs
Uplink and Downlink 11. BSS Packet Flow Delete Procedure
12. Tracking Area Update Request 13. Security functions 13. Security functions 14. Update Location 15. Cancel Location 15a. Cancel Location Ack 16. Delete PDP Context Request Only in case of Serving GW relocation 16a. Delete PDP Context Response 17 Inse rt Subscriber Data 17a Insert Subscriber Data Ack 18. Update Location Ack 19. Tracking Area Update Accept 20. Tracking Area Update Complete
TAU Procedure
Page 184
Basic CS to LTE Handover Call Flow:

EPC 2G CS domain IMS
UE
Source eNB
CS Proxy
MME, Serving GWG, PDN Gateway
Source BSS
Source MSC
HSS
MGCF/ MGW
VCC Application
B2B UA
Call 1a
Initial state - UE in PSTN Call while in CS domain
Call 1b
Call 1b
Call 1b
1 Measurements Reports
2 Handover Required (info)
3 MAP Prepare Handover Req (CS Proxy DN, Target MME, IMSI) 3a CS Proxy via S6a: Lookup VCC AS DN using UEs IMSI 3b return VCC AS DN 4. MAP Prepare Handover Req (VCC AS DN, CS Proxy DN, Target MME) 5a. MAP Prepare Handover Resp (CS Proxy DN, HO#, Ref #, HO_CMD) 5b MAP Prepare Handover Resp (CS Proxy DN, HO#, HO_CMD) 6. ISUP IAM (HO#) 7. SIP INVITE (HO#) 9. ISUP ACM 10. Handover CMD (Ref #) 11 . LTE attach procedure as defined in TS 23.401, 5.3.2 12. SIP INVITE (Ref #) 13. SIP 200 OK 15. Release 2G CS resources 14. ISUP ANM 13a. SIP 200 OK 8. SIP Progress
Basic Handover
Voice gap
Page 185
REL.8: Lte:
Initial Attach WLAN:
UE
1 IKE_AUTH Authentication
ePDG
Serving GW
3GPP AAA Proxy
PDN GW
HSS/ AAA
Authentication and Authorization
Proxy BU ( MN-ID, IP Addr Request ) Proxy BU ( MN-ID, IP Addr Req)
Update PDN GW Address

Proxy Binding Ack (P Addr I Proxy Binding Ack IP Addr)
IPsec tunnel setup completion
IKEv2 (IP Address Configuration)
IPsec Tunnel
PMIP Tunnel
PMIP Tunnel
Page 186
REL.8: Lte:
Initial Attach WLAN:
UE
1 IKEv2 authentication and tunnel setup
ePDG
SAE GW
HSS/ AAA
IKEv2 (IP Addr)
IPsec Tunnel
MIPv6 Security Association Setup and Home Address Configuration
Binding Update
6 IPsec Tunnel 7
Binding Ack
CMIP Tunnel
Page 187
WiMax Interworking over S101
BS
WiMAX ASN HRPD AN Operators IP services S2a Rx+ PCRF
S101
S1-MME MME S11 S10 UE E-UTRAN S1-U Serving GW S5 PDN GW S7
SGi
Page 188
WiMax Interface S101
S101AP
S101AP
UDP
UDP
IPv4 / IPv6
IPv4 / IPv6
L2/L1
L2/L1
MME
S101
HRPD AN
Page 189
WiMax Handover
UE Source eNB Source MME WIMAX Access User DL/UL Data System Information Measurement Report Serving GW PDN GW
Decision of WIMAX handover
Initiate WIMAX handover E-UTRAN radio Tunnel WiMAX handover signalling S1 Tunnel WiMAX handover signalling MME <-> WIMAX Tunnel WiMAX handover signalling
UE leaves E-UTRAN radio WiMAX signalling User DL/UL Data Update UE location
Page 190
LTE to WiMax Handover with MIH:

UE MIHF EUTRAN MME MIHF WiMAX ASN MIHF Serving GW PDN GW AAA
1.UE detects WiMAX Access
2.MIH_Scan Req/Rsp 3. MIH_Resource Query

4. MIH Relay of Authentication
4. MIH Relay 4. Access Authentication
5.MIH_HO_Commit Req
6.Detach from 3G and Synchronize to WiMAX
7.WiMAX Entry
8. Radio and Access Bearer Establishment
9. Proxy BU
Access Bearer
10. MIH_HO_Complete
PMIPv6
11.Release EPS Bearer
Page 191
S1 Setup & Reset:

UE eNB MME
S1AP initiatingMessage S1 SETUP REQUEST S1AP succesfulOutcome S1 SETUP RESPONSE
S1AP initiatingMessage RESET S1AP succesfulOutcome RESET ACKNOWLEDGE
S1AP initiatingMessage RESET S1AP succesfulOutcome RESET ACKNOWLEDGE
Page 192
S1 Error Indication & Reset:

UE
eNB
MME
S1AP initiatingMessage S1 ERROR INDICATION S1AP initiatingMessage RESET
S1AP succesfulOutcome RESET ACKNOWLEDGE
S1AP initiatingMessage S1 ERROR INDICATION S1AP initiatingMessage RESET
S1AP succesfulOutcome RESET ACKNOWLEDGE
Page 193
Random Access Procedure (Contention based) over RACH and SCH:

UE eNB MME
1 PRACH MAC Random Access Preamble
2 PDCCH MAC RA-RNTI

2 PDSCH MAC Random Access Response 3 UL-SCH RLC TM RRC-ConnectionRequest() 4 PDSCH MAC Contention Resolution DL-SCH RLC TM RRC-ConnectionSetup UL-SCH RLC AM S1AP: initiatingMessage INITIAL UE MESSAGE RRC-ConnectionSetupComplete(NAS) NAS
Page 194
Attach and default bearer/context setup:

UE eNB UL-SCH RLC TM RRC-ConnectionRequest DL-SCH RLC TM RRC-ConnectionSetup MME
UL-SCH RLC AM RRCConnection SetupComplete NAS (Attach Request (PDN CONNECTIVITY REQUEST)) DL-SCH RLC AM RRC-Connection Reconfiguration NAS (Attach Accept ( ACTIVATE DEFAULT EPS BEARER UL-SCH RLC AM RRC-Connection CONTEXT REQUEST)) ReconfigurationComplete
S1AP: initiatingMessage INITIAL UE MESSAGE NAS (Attach Request (ESM))

S1AP: initiatingMessage INITIAL CONTEXT SETUP REQUEST NAS (Attach Accept (ESM))
S1AP: succesfulOutcome INITIAL CONTEXT SETUP RESPONSE UL-SCH RLC AM RRC-ULInformation Transfer NAS (Attach Complete ( S1AP: initiatingMessage UL DIRECT ACTIVATE DEFAULT EPS BEARER TRANSPORT NAS (Attach Complete (ESM)) CONTEXT COMPLETE)) IP up and downlink traffic
Page 195
In the case of DHCP IP address allocation:

UE eNB MME
UL-SCH RLC UM IP DHCP Discover S1-U GTP IP DHCP Discover
DL-SCH RLC UM IP DHCP Offer UL-SCH RLC UM IP DHCP Request
S1-U GTP IP DHCP Offer (IP address)
S1-U GTP IP DHCP Request
DL-SCH RLC UM IP DHCP Ack
S1-U GTP IP DHCP Ack
IP up and downlink traffic
Page 196
Attach and default bearer/context setup UE ESM failure:

UL-SCH RLC AM RRCConnection SetupComplete NAS (Attach Request (PDN CONNECTIVITY REQUEST)) DL-SCH RLC AM RRC-Connection Reconfiguration NAS (Attach Accept ( ACTIVATE DEFAULT EPS BEARER UL-SCH RLC AM RRC-Connection CONTEXT REQUEST)) ReconfigurationComplete

S1AP: initiatingMessage INITIAL CONTEXT SETUP REQUEST NAS (Attach Accept (ESM))
S1AP: succesfulOutcome INITIAL CONTEXT SETUP RESPONSE UL-SCH RLC AM RRC-ULInformation S1AP: initiatingMessage UL DIRECT Transfer NAS (Detach Request) TRANSPORT NAS (Detach Request)
Detach procedure continues! Context Release follows

Page 197
Attach failure:
UL-SCH RLC AM RRCConnection SetupComplete NAS (Attach Request ESM (PDN CONNECTIVITY REQUEST)) DL-SCH RLC AM RRCDLInformation Transfer NAS (Attach Reject)

S1AP: initiatingMessage DL DIRECT TRANSFER NAS (Attach Reject)
Page 198
Attach and default bearer/context setup CORE ESM failure:

UL-SCH RLC AM RRCConnection SetupComplete NAS (Attach Request ESM (PDN CONNECTIVITY REQUEST)) DL-SCH RLC AM RRCDLInformation Transfer NAS (Attach Reject ESM (PDN CONNECTIVITY REJECT)

S1AP: initiatingMessage DL DIRECT TRANSFER NAS (Attach Reject (ESM))
Page 199
Service Request (EMM REGISTERED):

UE eNB MME
1 PRACH MAC Random Access Preamble
2 PDCCH MAC RA-RNTI

2 PDSCH MAC Random Access Response 3 UL-SCH RLC TM RRC-ConnectionRequest() 4 PDSCH MAC Contention Resolution DL-SCH RLC TM RRC-ConnectionSetup UL-SCH RLC AM RRC-ConnectionSetupComplete(NAS S1AP: initiatingMessage INITIAL UE MESSAGE NAS (Service Request) SERVICE REQUEST)
Page 200
Service Request (FAILURE):

UE eNB MME
1 PRACH MAC Random Access Preamble 2 PDCCH MAC RA-RNTI 2 PDSCH MAC Random Access Response 3 UL-SCH RLC TM RRC-ConnectionRequest() 4 PDSCH MAC Contention Resolution DL-SCH RLC TM RRC-ConnectionSetup UL-SCH RLC AM RRC-ConnectionSetupComplete(NAS S1AP: initiatingMessage INITIAL UE MESSAGE NAS (SERVICE REQUEST) SERVICE REQUEST) S1AP: initiatingMessage DL DIRECT DL-SCH RLC AM RRCTRANSFER NAS (SERVICE REJECT) DLInformation Transfer NAS (SERVICE REJECT)
Page 201
Paging (EMM REGISTERED):

UE eNB S1AP: initiatingMessage Paging MME
0 DL-SCH PCH RLC TM RRC Paging

1 PRACH MAC Random Access Preamble 2 PDCCH MAC RA-RNTI 2 PDSCH MAC Random Access Response 3 UL-SCH RLC TM RRC-ConnectionRequest()
4 PDSCH MAC Contention Resolution

DL-SCH RLC TM RRC-ConnectionSetup UL-SCH RLC AM RRC-ConnectionSetupComplete(NAS S1AP: initiatingMessage INITIAL UE MESSAGE NAS (Service Request) Service Request)
Page 202
Activate Default bearer:

UE eNB MME
UL-SCH RLC AM RRC-Uplink Information Transfer NAS (PDN CONNECTIVITY REQUEST) S1AP: initiatingMessage UPLINK NAS TRANSPORT NAS (PDN CONNECTIVITY REQUEST)
S1AP initiatingMessage DOWNLINK NAS TRANSPORT NAS (ACTIVATE DEFAULT EPS BEARER OPT. DL-SCH RLC AM RRC-DownlinkCONTEXT REQUEST) Information Transfer NAS (ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST)
UL-SCH RLC AM RRC-Uplink Information Transfer NAS (ACTIVATE DEFAULT EPS S1AP: initiatingMessage BEARER CONTEXT COMPLETE) UPLINK NAS TRANSPORT NAS (ACTIVATE DEFAULT EPS BEARER CONTEXT COMPLETE)
IP up and downlink traffic
Page 203
Activate Default bearer failure CORE:

UE eNB MME
UL-SCH RLC AM RRC-Uplink Information Transfer NAS (PDN CONNECTIVITY REQUEST) S1AP: initiatingMessage UPLINK NAS TRANSPORT NAS (PDN CONNECTIVITY REQUEST) OPT. S1AP initiatingMessage DOWNLINK NAS TRANSPORT NAS (PDN CONNECTIVITY REJECT) OPT. DL-SCH RLC AM RRC-Downlink Information Transfer NAS (PDN CONNECTIVITY REJECT)
Page 204
Activate Default bearer failure UE:

UE eNB MME
UL-SCH RLC AM RRC-Uplink Information Transfer NAS (PDN CONNECTIVITY REQUEST) S1AP: initiatingMessage UPLINK NAS TRANSPORT NAS (PDN CONNECTIVITY REQUEST) OPT. S1AP initiatingMessage DOWNLINK NAS TRANSPORT NAS (ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST) OPT. DL-SCH RLC AM RRC-Downlink Information Transfer NAS (ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST) UL-SCH RLC AM RRC-Uplink Information Transfer NAS (ACTIVATE DEFAULT EPS S1AP: initiatingMessage BEARER CONTEXT FAILURE) UPLINK NAS TRANSPORT NAS (ACTIVATE DEFAULT EPS BEARER CONTEXT FAILURE)
Page 205
eNB initiated CONTEXT RELEASE:

UE eNB MME
S1AP initiatingMessage UE CONTEXT RELEASE REQUEST

S1AP initiatingMessage UE CONTEXT RELEASE COMMAND DL-SCH RLC UM RRC-ConnectionRelease S1AP succesfulOutcome UE CONTEXT RELEASE COMPLETE
Page 206
MME initiated CONTEXT RELEASE:

UE eNB MME
S1AP initiatingMessage UE CONTEXT RELEASE COMMAND DL-SCH RLC UM RRC-ConnectionRelease S1AP succesfulOutcome UE CONTEXT RELEASE COMPLETE
Page 207
Detach (Active State, UE initiated):

UE eNB MME
UL-SCH RLC AM RRC-Uplink Information Transfer NAS (Detach Request) S1AP: initiatingMessage UPLINK NAS TRANSPORT NAS (Detach Request) OPT. S1AP initiatingMessage DOWNLINK NAS TRANSPORT NAS (Detach Accept) OPT. DL-SCH RLC AM RRC-Downlink Information Transfer NAS (Detach Accept)
Note: The MME initiated Context Release procedure has to follow
Page 208
Detach (Idle state, UE initiated):

UE eNB MME
UL-SCH RLC TM RRC-ConnectionRequest DL-SCH RLC TM RRC-ConnectionSetup UL-SCH RLC AM RRCConnection SetupComplete NAS (Detach Request) S1AP: initiatingMessage INITIAL UE MESSAGE NAS (Detach Request)
OPT. S1AP: initiatingMessage DOWNLINK OPT. DL-SCH RLC AM RRC-Downlink NAS TRANSPORT NAS (Detach Accept) Information Transfer NAS (Detach Accept)
Page 209
Detach (Active State, NWK initiated):

UE eNB MME
S1AP initiatingMessage DOWNLINK NAS TRANSPORT NAS (Detach Request) DL-SCH RLC AM RRC-Downlink Information Transfer NAS (Detach Request) UL-SCH RLC AM RRC-Uplink Information Transfer NAS (Detach Accept)
S1AP: initiatingMessage UPLINK NAS TRANSPORT NAS (Detach Accept)
Note: The MME Context Release procedure has to follow
Page 210
Intra eNB, Handover procedure

UE eNB UL/DL Data MME S-GW RRC-ConnectionReconfiguration
RRC-Measurement Report
Handover decision
RRC-ConnectionReconfiguration
PRACH (RACH Preamble) PDCCH (RA-RNTI)
Non contention based RA
PDSCH (Random Access Resp. (TA, UL Grand, Temp. CRNTI) RRCConnectionReconfigurationComplete PHICH (HARQ ACK/NACK) UL/DL Data
Page 211
Inter eNB X2, Intra MME/Serving GW Handover procedure

MME UL/DL Data S-GW
UE Source eNB Target eNB RRC-ConnectionReconfiguration Procedure
RRC-Measurement Report
Handover decision
X2AP HO Request
X2AP HO Request ACK RRC-ConnectionReconfiguration

X2AP SN Status Transfer Forwarding of Data (continues) PRACH (RACH Preamble) PDCCH (RA-RNTI) PDSCH (Random Access Resp., (TA, UL Grand, Temp. CRNTI)) RRCS1AP Path Switch Req. UP Update Req. ConnectionReconfigurationComplete UP Update Resp. PHICH (HARQ End marker ACK/NACK) End marker S1AP Path Switch Req. X2AP UE Context Release Ack. UL/DL Data
Page 212
Tracking Area Update:

UE eNB MME
UL-SCH RLC TM RRC-ConnectionRequest DL-SCH RLC TM RRC-ConnectionSetup UL-SCH RLC AM RRC-ConnectionSetupComplete NAS (Tracking Area Update Request) S1AP initiatingMessage INITIAL UE MESSAGE NAS (Tracking Area Update Request) S1AP initiatingMessage DOWNLINK NAS TRANSPORT (Tracking Area Update Accept)
DL-SCH RLC AM RRC-DownlinkDirectTransfer NAS (Tracking Area Update Accept)
Page 213
Dedicated bearer setup:

UE eNB MME
DL-SCH RLC AM RRC-Connection Reconfiguration
S1AP: initiatingMessage SAE BEARER SETUP REQUEST NAS (ACTIVATE DEDICATED EPS BEARER CONTEXT REQUES
UL-SCH RLC AM RRC-ConnectionReconfigurationComplete
UL-SCH RLC AM RRC-Uplink Information Transfer NAS S1AP: succesfulOutcome SAE BEARER SETUP RESPONSE NAS (ACTIVATE DEDICATED EPS BEARER CONTEX ACCEPT)
Page 214
Dedicated bearer release:

UE eNB MME
S1AP: initiatingMessage SAE BEARER RELEASE COMMAND DL-SCH RLC AM RRC-Connection Reconfiguration
UL-SCH RLC AM RRC-Connection Reconfiguration Complete S1AP: succesfulOutcome SAE BEARER RELEASE RESPONSE
Page 215
Contention based Random Access Procedure:

UE eNB
Random Access Response
Scheduled Transmission
Contention Resolution
Page 216
Random Access Procedure (non Contention based) HO case: UE eNB
RA Preamble assignment
Random Access Response
Page 217
Mobility procedures between E-UTRA and CDMA2000:
1xRTT CS Active
Handover
E-UTRA RRC_CONNECTED
Handover
HRPD Dormant HRPD Active
Connection establishment/release
1xRTT Dormant
Reselection
E-UTRA RRC_IDLE
Reselection
HRPD Idle
Page 218
E-UTRAN to CDMA2000 HRPD handover:

UE E-UTRAN MME HRPD Access Network HSGW S-GW PDN GW PCRF AAA 0. UE connected via E-UTRAN 1. CDMA m eas urements 2. Handover decis ion 3. Handover from E-UTRA preparation reques t 4. UL inform ation trans fer 5. Uplink S1 CDMA2000 Tunneling 6. Direct Trans fer Reques t 7. A11 Signalling 8. Direct Trans fer Reques t 9a. Create forwarding tunnels Reques t (UL 9b. Create forwarding tunnels Res pons e 10. Downlink S1 CDMA2000 Tunneling 11. Mobility from E-UTRA
11. Data Forwarding
12. HRPD AN acquires UE 13. HRPD TCC 14a. A11 Reques t Signalling 14b. Proxy Binding Update 14c. Proxy Binding Acknowledge 14d. A11 Response Signalling 15a. HO Com plete 15b. HO Com plete 16. E-UTRAN Bearer Releas e 17a. Delete Bearer Reques t 17b. Delete Bearer Res pons e 18. P-GW initiates resource allocation deactivation procedure at E-UTRAN 14e. PCEF Initiated IP-CAN Sess ion Modification Procedure
Page 219
REL.8: Lte (S1 Flex):
I.AS Anchor
I.AS Anchor
MME/UPE Service Area 1

MME/UPE MME/UPE
MME/UPE Service Area 2

MME/UPE
S1-flex
LTE-RAN Entity 1
LTE-RAN Entity 2
LTE-RAN Entity 3
LTE-RAN Entity 4
LTE-RAN Entity 5
UE1
UE1
UE1
UE1
UE1
UE switches to LTE_IDLE mode

Page 220
REL.8: Lte (S1 Flex):
Operator A MME sGW MME sGW
Operator B MME S sGW 1 MME sGW
S1
eNB eNB eNB
RAN Operator
Many to many configuration!
Page 221
Radio access network sharing configuration:

MME Operator A S-GW Operator A MME Operator B S-GW Operator B
S1
Non-shared LTE
X2
X2
X2
X2
Non-shared LTE
Customer of operator A
Customer of operator B
Up to 6 PLMN IDs can be broadcasted per cell!
Page 222
Pool Area, Tracking Area and S1 Flex Concepts:
SAE-GW Pool Area A

MME Pool Area 1 MME MME MME
1 2 3 4 5 6 7 8
SAE-GW SAE-GW SAE-GW
SAE-GW SAE-GW SAE-GW MME Pool Area 2 MME MME MME

9 10 11 12 13 14
MME Pool Area 3 MME MME MME

15 16 17 18 19
TA1
TA2
TA3
TA4
TA5
TA6
TA7
TA8
eNodeBs Cells
SAE-GW Pool Area B
Tracking Areas
Page 223
SAE GW, MME, eNB, Cells, Pool Area, Tracking Area:

SAE GW
MME MME MME
MME MME MME
eNB-1
eNB-2
eNB-3
Cell 1
Cell 2
Cell 3
Cell 4
Cell 5
Cell 6
Cell 7
Cell 8
Cell 9
Cell 10
Cell 11
Cell 12
TA-1 TA-2
TA-3
MME Pool Area 1
MME Pool Area 2
Page 224
Structures and Layers
Page 225
Protocol layer and SAPs UE - eNB:

TS 24.301 EMM/ESM
NAS
Mobility & Bearer control layer
NAS_ -c SAP SEC
IP
IP layer
NAS_SEC
RRCSAP PDC P-u SAP
TS 36.331
C P PDC
RRC
PDC SAP P-c
Radio netw ork layer
TS 36.323
C RLC
PDC P
RLC SAP -c
RLC SAP -u
RLC
Radio link layer
TS 36.322
MAC SAP -c MAC SAP -u
C MAC
MAC
Physical layer
PHY SAP
TS 36.321
C PHY
TS 36.2xx
PHY
Page 226
Lte Layer Data flow:

SAE Bearer 1 Header Payload SAE Bearer 2 Header Payload SAE Bearer 3 Header Payload
PDCP header Compression, Ciphering
PDCP Header
PDCP SDU
PDCP Header
PDCP SDU
PDCP Header
PDCP SDU
RLC segmentation, Concatenation
RLC Header
RLC SDU
RLC SDU
RLC Header
RLC SDU
RLC Header
RLC SDU
MAC Multiplexing
MAC Header
MAC SDU
MAC Header
MAC SDU
PHY
Transport Block
CRC
Transport Block
CRC
Page 227
REL.8: Lte (Layer 2 Structure for DL):
Radio Bearers ROHC PDCP Security Security Security Security ROHC ROHC ROHC
RLC
Segm. ARQ etc
...
Segm. ARQ etc Logical Channels
Segm. ARQ etc
...
Segm. ARQ etc
CCCH BCCH
PCCH
Scheduling / Priority Handling
MAC
Multiplexing UE1
Multiplexing UEn
HARQ Transport Channels
HARQ
Page 228
REL.8: Lte (Layer 2 Structure for UL):

Radio Bearers ROHC PDCP Security Security ROHC
RLC
Segm. ARQ etc
...
Segm. ARQ etc
CCCH Logical Channels
Scheduling / Priority Handling
MAC
Multiplexing
HARQ Transport Channels
Page 229
Functions of the MAC sub layer:

Mapping between logical channels and transport channels; Multiplexing of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels; Demultiplexing of MAC SDUs from one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels; Scheduling information reporting; Error correction through HARQ (up to 8 FDD(15 TDD) processes parallel); Priority handling between UEs by means of dynamic scheduling; Priority handling between logical channels of one UE; Logical Channel prioritisation; Transport format selection;
MAC function
Mapping between logical channels and transport channels
UE
X
eNB
X
Downlink
X X
Uplink
X X X
Multiplexing
X X X X X
Demultiplexing
X X X X X X X X X Page 230
Error correction through HARQ
X X
X X X X
Transport Format Selection Priority handling between UEs Priority handling between logical channels of one UE Logical Channel prioritisation Scheduling information reporting X X
X X X
MAC PDU:
MAC PDU consisting of MAC header, MAC control elements, MAC SDUs and padding:
R/R/E/LCID sub-header
R/R/E/LCID/F/L sub-header
...
R/R/E/LCID padding sub-header
MAC header
MAC Control element 1
MAC Control element 2
MAC SDU
...
MAC SDU
Padding (opt)
MAC payload
LCID = Logical Channel ID L = Length E = End field
Page 231
MAC Sub Header:
LCID
Oct 1
R F
E L
LCID
Oct 1 Oct 2
R F
E L L
LCID
Oct 1 Oct 2 Oct 3
R/R/E/LCID/F/L sub-header with 7-bits L field
R/R/E/LCID/F/L sub-header with 15-bits L field
Page 232
MAC:
Values of LCID for DL-SCH: Index: LCID-values: 00000 CCCH 00001 - ID of logical channel 01010 01011 - reserved 11011 11100 UE Contention Res. ID 11101 Timing Advance Com. 11110 DRX 11111 Padding Value of the F-field: Index: Size of the Length field: 0 7 bit 1 15 bit Values of LCID for UL-SCH: Index: LCID-values: 00000 CCCH 00001 - ID of logical channel 01010 01011 - reserved 11001 11010 Power Headroom Report 11011 C-RNTI 11100 Truncated BSR 11101 Short BSR 11110 Long BSR 11111 Padding
SRB1 = LCID 1, SRB2 = LCID 2

Page 233
MAC Control Elements:

UE Contention Resolution Identity MAC control element:
MAC Buffer Status control element:
UE Contention Resolution Identity UE Contention Resolution Identity UE Contention Resolution Identity UE Contention Resolution Identity UE Contention Resolution Identity UE Contention Resolution Identity
Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct 6
LCG ID
Buffer Size
Oct 1
Buffer Size #0 Buffer Size #1 Buffer Size #2
Buffer Size #1 Buffer Size #2
Oct 1 Oct 2 Oct 3
Buffer Size #3
DRX Command MAC Control Element: The DRX Command MAC control element is identified by a MAC PDU subheader with LCID. It has a fixed size of zero bits. C-RNTI MAC control element:
C-RNTI C-RNTI
Oct 1 Oct 2
Page 234
MAC Control Elements:

Timing Advance Command MAC control element:
Timing Advance Command
Oct 1
Power Headroom MAC control element:
Power Headroom
Oct 1
MAC PDU (transparent MAC):

MAC SDU
MAC PDU
Page 235
MAC PDU (Random Access Response) DL:

E/T/RAPID MAC sub-header (Random Access Preamble ID): E/T/R/R/BI MAC sub-header (Backoff Indicator):
RAPID
Oct 1
E T R
Index
BI
Backoff Parameter value (ms)
Oct 1
MAC RAR:
0
10 20 30 40 60 80 120 160 240 320 480 960
Page 236
Timing Advance Command UL Grant
Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct 6
2 3 4 5 6 7 8 9 10 11 12
Timing Advance Command
UL Grant UL Grant Temporary C-RNTI Temporary C-RNTI
MAC PDU (Random Access Response) DL:
MAC PDU consisting of a MAC header and MAC RARs:
E/T/R/R/BI subheader
E/T/RAPID subheader 1
E/T/RAPID subheader 2
...
E/T/RAPID subheader n
MAC header
MAC RAR 1
MAC RAR 2
...
MAC RAR n
Padding (opt)
MAC payload
Page 237
RNTI values:
Value (hexa-decimal) FDD TDD RNTI
0000-0009
000A-FFF2
0000-003B
003C-FFF2
RA-RNTI
C-RNTI, SemiPersistent Scheduling CRNTI, Temporary C-RNTI, TPCPUCCH-RNTI and TPCPUSCH-RNTI
FFF3-FFFC
FFFE FFFF
Reserved for future use

P-RNTI SI-RNTI
Page 238
RLC Functions:
Functions: The following functions are supported by the RLC sub layer: transfer of upper layer PDUs; error correction through ARQ (only for AM data transfer); concatenation, segmentation and reassembly of RLC SDUs (only for UM and AM data transfer); re-segmentation of RLC data PDUs (only for AM data transfer); in sequence delivery of upper layer PDUs (only for UM and AM data transfer); duplicate detection (only for UM and AM data transfer); RLC SDU discard (only for UM and AM data transfer); RLC re-establishment; Protocol error detection and recovery
Page 239
RLC:
upper layer (i.e. RRC layer or PDCP sub layer) SAP between upper layers transmitting TM RLC entity receiving TM RLC entity transmitting UM RLC entity receiving UM RLC entity AM RLC entity
eNB
logical channel
lower layers (i.e. MAC sub layer and physical layer) radio interface lower layers (i.e. MAC sub layer and physical layer) logical channel receiving TM RLC entity transmitting TM RLC entity receiving UM RLC entity transmitting UM RLC entity AM RLC entity
UE
SAP between upper layers
upper layer (i.e. RRC layer or PDCP sub layer)
Page 240
RLC Transparent Mode:

UE/ENB ENB/UE
radio interface TM-SAP TM-SAP
Transmission buffer
Transmittin g TM-RLC entity
Receiving TM-RLC entity
BCCH/PCCH/CCCH
BCCH/PCCH/CCCH
Page 241
RLC Unacknowledged Mode:

UE/ENB radio interface UM-SAP UM-SAP ENB/UE
Transmission buffer Transmittin g UM-RLC entity Segmentation & Concatenation Receiving UM-RLC entity
SDU reassembly
Remove RLC header
Add RLC header
Reception buffer & HARQ reordering
DCCH/DTCH/MCCH/MTCH
DCCH/DTCH/MCCH/MTCH
Page 242
RLC Acknowledged Mode:

AM-SAP
Transmission buffer
RLC control
SDU reassembly
Segmentation & Concatenation
Retransmission buffer
Remove RLC header
Reception buffer & HARQ reordering
Add RLC header Routing
DCCH/DTCH
DCCH/DTCH
Page 243
RLC PDU Structure:
RLC SDU ...
n+1
n+2
n+3 ...
RLC header
RLC header
RLC PDU
Page 244
RLC PDU:
FI E Data ... SN Oct 1 Oct 2 Oct N
Data ...
Oct 1 Oct N
UMD PDU with 5 bit SN (No LI):

(Window size 16)
TMD PDU:
R1
R1
R1
FI SN Data ...
SN
Oct 1 Oct 2 Oct 3 Oct N
D/C
RF
FI SN Data ...
SN
Oct 1 Oct 2 Oct 3 Oct N
UMD PDU with 10 bit SN (No LI):

(Window size 512)
AMD PDU (No LI): (Window size 512)
Page 245
RLC PDU:
D/C E LI1 LI2 ... E LIK-1 LIK-1 E LIK Data ... LIK RF P FI SN LI1 E E SN Oct Oct Oct Oct Oct Oct Oct Oct Oct 1 2 3 4 5 [2+1.5*K-2] [2+1.5*K-1] [2+1.5*K] [2+1.5*K+1]
AMD PDU (Even number of LIs, i.e. K = 2, 4, 6, )
LI2
Oct N
D/C E
RF
FI SN LI1 E LI2 ...
SN
LI1
LI2 (if K>=3)
Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct
1 2 3 4 5 [2.5+1.5*K-4] [2.5+1.5*K-3] [2.5+1.5*K-2] [2.5+1.5*K-1] [2.5+1.5*K] [2.5+1.5*K+1]
AMD PDU (Odd number of LIs, i.e. K = 1, 3, 5, )
Present if K >= 3
E LIK-2 E LIK
LIK-2 E LIK-1 LIK
LIK-1
Padding Data ...
Oct N
Page 246
RLC PDU:
D/C LSF RF P FI SN SO SO Data ... E SN Oct Oct Oct Oct Oct 1 2 3 4 5
AMD PDU segment (No LI)
Oct N
D/C LSF
RF
FI SN SO SO LI1 E LI2 ...
SN
E LI1
LI2
Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct
1 2 3 4 5 6 7
AMD PDU segment (Even number of LIs, i.e. K = 2, 4, 6, )
E LIK-1
LIK-1 E LIK Data ...
LIK
[4+1.5*K-2] [4+1.5*K-1] [4+1.5*K] [4+1.5*K+1]
Oct N
Page 247
RLC PDU:
D/C LSF SO E LI1 LI2 ... Present if K >= 3 E LIK-2 E LIK Data ... LIK-2 E LIK-1 LIK Padding LIK-1 LI1 E LI2 (if K>=3) RF P FI SN SO E SN Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct Oct 1 2 3 4 5 6 7 [4.5+1.5*K-4] [4.5+1.5*K-3] [4.5+1.5*K-2] [4.5+1.5*K-1] [4.5+1.5*K] [4.5+1.5*K+1]
D/C
CPT ACK_SN ACK_SN E1 NACK_SN E1 E2 NACK_SN NACK_SN E1 E2 SOstart SOstart SOend SOend SOend NACK_SN ...
Oct Oct Oct Oct Oct Oct Oct Oct Oct
1 2 3 4 5 6 7 8 9
STATUS PDU:
Oct N
AMD PDU segment (Odd number of LIs, i.e. K = 1, 3, 5, )
Page 248
RLC PDU segmented:

1st AMD PDU segment
E=0 D/C =0 R=1 SI=01 P
2nd AMD PDU segment

E=1 D/C =0 R=1 SI=10 P
PDU SN
PDU SN
PDU SN
LSF 0
PDU SN
LSF 1
offset Offset=0
offset Offset=8
E=0
Reserved LI (cont.)
LI
8 octet
payload
payload
payload
Page 249
UMD PDU with 5 bit SN:
UMD PDU with 5 bit SN (Odd number of LIs, i.e. K = 1, 3, 5, ): UMD PDU with 5 bit SN (Even number of LIs, i.e. K = 2, 4, 6, ):
FI E LI1 Present if K >= 3
E LI1 E LI2 ...
SN LI2 (if K>=3)
Oct 1 Oct 2 Oct 3 Oct 4 Oct [2.5+1.5*K-5] Oct [2.5+1.5*K-4] Oct [2.5+1.5*K-3] Oct [2.5+1.5*K-2] Oct [2.5+1.5*K-1] Oct [2.5+1.5*K] Oct N
FI E LI1
E LI1 E LI2 ...
SN LI2
E LIK-2 E LIK
LIK-2 E LIK-1 LIK
Oct 1 Oct 2 Oct 3 Oct 4 Oct [2+1.5*K-3] Oct [2+1.5*K-2] Oct [2+1.5*K-1] Oct [2+1.5*K] Oct N
LIK-1
E LIK-1
LIK
Padding Data ...
Page 250
UMD PDU with 10 bit SN:

UMD PDU with 10 bit SN (Even number of LIs, i.e. K = 2, 4, 6, )
R1 E LI1 Present if K >= 3 LI2 ... E LIK-2 E LIK Data ... LIK-2 E LIK-1 LIK Padding LIK-1 R1 R1 FI SN LI1 E E SN Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct [2.5+1.5*K-4] Oct [2.5+1.5*K-3] Oct [2.5+1.5*K-2] Oct [2.5+1.5*K-1] Oct [2.5+1.5*K] Oct [2.5+1.5*K+1] Oct N
R1 E
R1
R1
FI SN LI1 E LI2 ...
SN
LI2 (if K>=3)
LI1
LI2
Oct 1 Oct 2 Oct 3 Oct 4 Oct 5 Oct [2+1.5*K-2] Oct [2+1.5*K-1] Oct [2+1.5*K] Oct [2+1.5*K+1] Oct N
E LIK-1
LIK
UMD PDU with 10 bit SN (Odd number of LIs, i.e. K = 1, 3, 5, )
Page 251
PDCP Functions:
The Packet Data Convergence Protocol supports the following functions:

-header compression and decompression of IP data flows using the ROHC protocol, at the transmitting and receiving entity, respectively; -transfer of data (user plane or control plane). This function is used for conveyance of data between users of PDCP services; -maintenance of PDCP sequence numbers for radio bearers mapped on RLC AM; -in-sequence delivery of upper layer PDUs at handover; -duplicate elimination of lower layer SDUs at handover for radio bearers mapped on RLC AM; -ciphering and deciphering of user plane data and control plane data; -integrity protection and integrity verification of control plane data; -timer based discard.
Page 252
PDCP Structure:
UE/E-UTRAN
PDCP entiy
Radio Bearers PDCP-SAP
PDCP-SAP
C-SAP
PDCP entity PDCP entity
...
PDCP sublayer
PDCP - PDU RLC - SDU
...
RLC UM-SAP RLC AM-SAP
RLC sublayer
Page 253
PDCP Layer, Functional View CP:

UE/E-UTRAN
Transmitting PDCP entity Receiving PDCP entity
E-UTRAN/UE
Add PDCP header with SN
Remove PDCP Header
Integrity protection
Integrity Verification
Ciphering
Deciphering
Radio Interface (Uu)
Page 254
PDCP Layer, Functional View UP:

UE/E-UTRAN
Transmitting PDCP entity Receiving PDCP entity
E-UTRAN/UE
Sequence numbering Header Compression (u-plane only) Packets associated to a PDCP SDU Integrity Protection (c-plane only) Ciphering Add PDCP header
Packets not associated to a PDCP SDU
In order delivery and duplicate detection (u-plane only) Header Decompression (uplane only) Packets associated to a PDCP SDU Integrity Verification (c-plane only) Deciphering
Remove PDCP Header
Packets not associated to a PDCP SDU
Radio Interface (Uu)

Page 255
PDCP:
PDCP Data PDU for signalling radio bearers Using 5 bit sequence number: PDCP Data PDU for user plane radio bearers using 12 bit sequence number (RLC AM, UM):
R Data ...
PDCP SN
Oct 1 Oct 2
D/C
PDCP SN
Oct 1 Oct 2 Oct 3
PDCP SN (cont.) Data
MAC-I MAC-I (cont.) MAC-I (cont.) MAC-I (cont.)
Oct N-3
...
Oct N-2 Oct N-1 Oct N
Page 256
PDCP:
PDCP Data PDU for user plane radio bearers using 7 bit sequence number (RLC UM): PDCP Control PDU for ROHC feedback packet:
D/C
PDCP SN Data ...
Oct 1 Oct 2
D/C
PDU Type
Oct 1 Oct 2
Interspersed ROHC feedback packet ...
PDCP Control PDU for PDCP status report:
D/C
PDU Type FMS (cont.) Bitmap1 (optional) ... BitmapN (optional)
FMS
Oct 1 Oct 2 Oct 3
Oct 2+N
Page 257
Reduced number of RRC protocol states:

LTE_Idle LTE_Active
Inactivity - Release C-RNTI - Allocate DRX for PCH Perform Registration - Allocate C-RNTI, TA-ID, IP addr - Perform Authentication - Establish security relation
Power-Up
LTE_Detached
LTE_IDLE
RRC: RRC_IDLE Context in network: - Includes information to enable fast transition to LTE_ACTIVE (e.g. security key information) Allocated UE-Id(s): - IMSI - ID unique in Tracking Area (TA-ID) - 1 or more IP addresses UE position: - Known by network at Tracking Area (TA) level Mobility: - Cell reselection DL activity: - UE is configured with DRX period
LTE_ACTIVE
RRC: RRC_CONNECTED RRC Context in network: - Includes all information necessary for communication Allocated UE-Id(s): - IMSI - ID unique in Tracking Area (TA-ID) - ID unique in cell (C-RNTI) - 1 or more IP addresses UE position: - Known by network at cell level Mobility: - Handover DL/UL activity: - UE may be configured with DRX/DTX periods
LTE_DETACHED
RRC: NULL RRC Context in network: - Does not exist
Allocated UE-Id(s): - IMSI
UE position: - Not known by network Mobility - PLMN/Cell selection DL/UL activity: - None
New traffic - Allocate C-RNTI
Change of PLMN/deregistration - Deallocate C-RNTI, TA-ID, IP address
Timeout of periodic TA-update - Deallocate TA-ID, IP address
Page 258
E-UTRA states and inter RAT mobility procedures:
GSM_Connected CELL_DCH Handover E-UTRA RRC_CONNECTED Handover GPRS Packet transfer mode CCO, Reselection Connection establishment/release
CELL_FACH CCO with optional NACC Reselection Connection establishment/release
CELL_PCH URA_PCH Connection establishment/release UTRA_Idle
Reselection
E-UTRA RRC_IDLE
Reselection CCO, Reselection
GSM_Idle/GPRS Packet_Idle
Page 259
RRC Messages:
BCCH-BCH-Message ::= SEQUENCE { message BCCH-BCH-MessageType ::= BCCH-BCH-MessageType} MasterInformationBlock
BCCH-DL-SCH-Message ::= SEQUENCE {

message BCCH-DL-SCH-MessageType ::= c1 systemInformation systemInformationBlockType1 messageClassExtension PCCH-Message ::= message PCCH-MessageType ::= CHOICE { c1 paging messageClassExtension DL-CCCH-Message ::= SEQUENCE { message DL-CCCH-MessageType ::= CHOICE { c1 rrcConnectionReestablishment rrcConnectionReestablishmentReject CHOICE { RRCConnectionReestablishment, RRCConnectionReestablishmentReject, DL-CCCH-MessageType} SEQUENCE {}} CHOICE { Paging}, SEQUENCE { PCCH-MessageType} SEQUENCE {}} CHOICE { CHOICE { SystemInformation, --SIB 2-11 BCCH-DL-SCH-MessageType}
SystemInformationBlockType1},
rrcConnectionReject
rrcConnectionSetup messageClassExtension SEQUENCE {}}
RRCConnectionReject,
RRCConnectionSetup},
Page 260
RRC Messages:
DL-DCCH-Message ::= SEQUENCE { message DL-DCCH-MessageType ::= CHOICE { c1 DL-DCCH-MessageType} CHOICE { CDMA2000-CSFBParametersResponse, DLInformationTransfer, HandoverFromEUTRAPreparationRequest, MobilityFromEUTRACommand, RRCConnectionReconfiguration, RRCConnectionRelease, SecurityModeCommand, UECapabilityEnquiry}, SEQUENCE {}} UL-CCCH-MessageType} CHOICE { RRCConnectionReestablishmentRequest, RRCConnectionRequest}, SEQUENCE {}} UL-DCCH-MessageType} CHOICE { CDMA2000-CSFBParametersRequest, MeasurementReport, RRCConnectionReconfigurationComplete, RRCConnectionReestablishmentComplete, RRCConnectionSetupComplete, SecurityModeComplete, SecurityModeFailure, UECapabilityInformation, ULHandoverPreparationTransfer, ULInformationTransfer, cdma2000-CSFBParametersResponse dlInformationTransfer handoverFromEUTRAPreparationRequest mobilityFromEUTRACommand rrcConnectionReconfiguration rrcConnectionRelease securityModeCommand ueCapabilityEnquiry messageClassExtension UL-CCCH-Message ::= SEQUENCE { message UL-CCCH-MessageType ::= CHOICE { c1
rrcConnectionReestablishmentRequest rrcConnectionRequest messageClassExtension UL-DCCH-Message ::= SEQUENCE { message UL-DCCH-MessageType ::= CHOICE { c1 cdma2000-CSFBParametersRequest measurementReport rrcConnectionReconfigurationComplete rrcConnectionReestablishmentComplete rrcConnectionSetupComplete securityModeComplete securityModeFailure ueCapabilityInformation ulHandoverPreparationTransfer ulInformationTransfer spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL}, messageClassExtension SEQUENCE {}}
Page 261
MBMS
Multimedia Broadcast Multicast Service
Page 262
REL.8: MBMS (1 3 (62) Mbps):

New channels: Mapped over the (Rel. 6 FACH) DL-SCH or MCH
MTCH MCCH MSCH MICH
MBMS cell
MTCH mapped over (FACH) DL-SCH or MCH MCCH mapped over (FACH) DL-SCH or MCH MSCH mapped over (FACH) DL-SCH or MCH MICH new physical Channel (not used in Lte)
Page 263
MBMS Reference Signals:

Mapping of MBSFN reference signals (extended cyclic prefix, f = 15 kHz):
R4 R4 R4 R4 R4 R4 R4 R4 R4 R4 R4 R4
l 0 l 5l 0
R4 R4 R4 R4 R4 R4 R4 R4 R4 R4 R4 R4 R4 R4 R4 l 0 l 2l 0 l 2
even-numbered odd-numbered slots slots
Mapping of MBSFN reference signals (extended cyclic prefix, f = 7,5 kHz):
R4 R4 R4 R4 R4 R4
l 5
R4
R4
even-numbered slots
odd-numbered slots
Antenna port 4
R4
Antenna port 4
Page 264
REL.8: Lte:
MBMS:
single cell transmission on MCH or DL-SCH from a mixed cell
MCH or DL-SCH
MCH or DL-SCH
multicell transmission on MCH from mixed cells
MC H
MC H
MC H
MC H
mutlicell transmission on MCH from MBMS dedicated cells
single cell transmission on MCH or DL-SCH from MBMS dedicated cell

Page 265
MBMS logical Architecture:
Contents Provider PDN Gateway PDN Gateway

SGimb MBMS UP
Contents Provider
eBMSC
SGmb MBMS CP
eBMSC
SGmb MBMS CP SGimb MBMS UP
E- MBMS GW
M3
MCE
F4 F2
M1
M3
M1
M2
eNB
Signaling User Plane
Page 266
eNB
MCE
eNB
MCE
eNB
MBMS logical Architecture:

BM-SC
For LTE/SAE MBMS
For Rel-6/7 MBMS
EPC
MME
M3
mSAE GW
SGSN
E-UTRAN
IP multicast capable TNL
MCE
M1
RNC
C-plane
U-plane M2
eNB
eNB
eNB
Node B
Red lines indicate I/F that are used when SFN operation is required
Page 267
MBMS Definitions:
MBMS Service Area
MBSFN Area MBSFN Area
MBSFN Area
MBSFN Area Transmitting-Only Cell
MBSFN Area Transmitting and Advertising Cell
MBSFN Area Transmitting-Only Cell
MBSFN Area Reserved Cell

Page 268
MBMS eNB Synchronization:

UE MBMS packet
PDCP
m-Sgm
eNB E - MBMS Gateway

PDCP
m-Sgm
eBM -SC
MBMS packet
SYNC
M1-AP
SYNC
M1-AP
TNL
RLC
MAC PHY
RLC TNL MAC PHY TNL
M1
SYNC: Protocol to synchronize data used to generate a certain radio frame
Page 269
MBMS message flow:

UE eNB MBMS MBMS Coord Entitiy
Random Access Response Scheduled Transmission [ RR MBMS Request TMGI ] Contention Resolution [ RR Assignment ] MBMS Data UPDATE UPDATE ACK
Page 270
IGMP Join message [ IP Multicast ] MBMS Data
REL.8: Lte (MBMS):
Page 271
Miscellaneous
Page 272
REL.8: Lte (C-Plane processing in UE, eNB and MME):

1. Delay for RACH Scheduling period UE eNB MME
3. Processing delay 2. RACH Preamble 4. Processing delay in UE 3. TA + Scheduling Grant 7. Processing delay in eNB 5. RRC Connection Request 6. H-ARQ Retransmission RRC Contention Resolution 8. Connection Request 9. Processing delay in MME in eNB
14. Processing delay in UE 12. RRC Connection Setup 13. H-ARQ Retransmission
10. Connection Setup
11. Processing delay in eNB
15. RRC Connection Complete 16. H-ARQ Retransmission
Page 273
REL.8: Lte C-Plane latency

Step
0 1 2 3 UE wakeup time Average delay due to RACH scheduling period RACH Preamble Preamble detection and transmission of RA response (Time between the end RACH transmission and UEs reception of scheduling grant and timing adjustment) UE Processing Delay (decoding of scheduling grant, timing alignment and C-RNTI assignment + L1 encoding of RRC Connection Request)
Description
Duration
Implementation dependent Not included 5ms 1ms 5ms
2.5ms
5
6 7 8 9 10
TTI for transmission of RRC Connection Request

HARQ Retransmission (@ 30%) Processing delay in eNB (Uu > S1-C) S1-C Transfer delay MME Processing Delay (including UE context retrieval of 10ms) S1-C Transfer delay
1ms
0.3 * 5ms 4ms Ts1c (2ms 15ms) 15ms Ts1c (2ms 15ms)
11
12 13 14 15 16
Processing delay in eNB (S1-C > Uu)

TTI for transmission of RRC Connection Setup (+Average alignment) HARQ Retransmission (@ 30%) Processing delay in UE TTI for transmission of L3 RRC Connection Complete HARQ Retransmission (@ 30%)
4ms
1.5ms 0.3 * 5ms 3ms 1ms 0.3 * 5ms
Total Lte_IDLELte_ACTIVE delay (C-plane establishment)
47.5ms + 2 * Ts1c
Page 274
REL.8: Lte U-Plane latency

Step Description
Lte_IDLELte_ACTIVE delay (C-plane establishment)
Duration
47.5ms + 2 * Ts1c
17 18 19
TTI for UL DATA PACKET (Piggy back scheduling information) HARQ Retransmission (@ 30%) eNB Processing Delay (Uu > S1-U)
1ms 0.3 * 5ms 1ms
U-plane establishment delay (RAN edge node) 20 21 S1-U Transfer delay UPE Processing delay (including context retrieval)
51ms + 2 * Ts1c Ts1u (1ms 15ms) 10ms
U-plane establishment delay (Serving GW)
61ms + 2 * Ts1c + Ts1u
Page 275
REL.8: Lte (U-Plane latency components in Lte):

UE eNB
TTI + frame alignment 1.5 ms
1 ms
1 ms
HARQ RTT 5 ms
1 ms
1.5 ms
1 ms
Page 276
Home eNB Concept:

HIGHER NETWORK NODE
OTHER 3GPP LTE MACRO CELL SYSTEM
A D
Page 277
Home eNB Concept:
EPC MME / S-GW MME / S-GW
S1
S1
S1
eNB
S1
eNB HeNB HeNB HeNB
X2
S1
S1
X2
S1
S1
HeNB GW eNB E-UTRAN
S1
S1
X2
Page 278
Home eNB Concept: Iu based architecture:
Core Network
DSL
Macro site
3G HeNB
Iu
Internet + 3G HNB network
SGSN
MSC
Page 279
Home eNB Concept:

Local Breakout
Home eNodeB
B-NT
IPSEC
Internet
FGW
Home GW S1-MME S1-U
LTE UE
E-UTRAN
S1
MME aGW
S11
Serving GW S5 PDN GW
Page 280
Home eNB Concept:
SMLC
CBC
Iu-pc HNB Access Network
Iu-bc Iu-cs
HPLMN/VPLMN
MSC Uu Iu-h
UE
3G HNB
Generic IP Access Network
HNB-GW
Iu-ps SGSN
AAA Proxy/ Server
SEGW Wm Iu-hm
HLR
D/Gr
HNB Mgmt System
Page 281
Home eNB Concept:

Control plane for S1-MME Interface for HeNB to MME with the HeNB GW:
S1-AP SCTP Remote IP IPSec ESP Transport IP Access Layer S1-MME HeNB SeGW
S1-AP SCTP
S1-AP SCTP
S1-AP SCTP
Remote IP IPSec ESP Transport IP Access Layer Access Layer IP HeNB GW Access Layer Access Layer S1-MME MME Access Layer Remote IP Remote IP Remote IP Remote IP
Page 282
Home eNB Concept: CS User Plane Protocol Architecture:
Uu
Iu-h
Iu-cs
CS User Data RTP (RFC 4867) UDP RLC RLC Remote IP IPSec ESP MAC L1 UE MAC L1 3G HNB Transport IP Access Layers Transport IP Access Layers Generic IP Network Remote IP IPSEC ESP Transport IP Access Layer HNB-GW Transport Network Control and Data Transport Layers (TS 25.414) RTP (RFC 4867) UDP Iu-UP
CS User Data
Iu UP
Transport Network Control and Data Transport Layers (TS 25.414)
MSC
Page 283
Home eNB Concept: Optimized PS user plane architecture:

Iu-h
Uu
Iu-ps GGSN
PS User Data PDCP PDCP GTP-U UDP RLC RLC Remote IP IPSec ESP MAC Transport IP Transport IP IPSec ESP Transport IP Data Transport Lower Layers (TS 25.414) IP
GTP-U UDP IP
MAC
L1
L1
Access Layers 3G HNB
Access Layers Generic IP Network
Access Layers
Data Transport Lower Layers (TS 25.414)
UE
HNB-GW
SGSN
Page 284
REL.8: Lte:
GTP
Visited NW
GTP
GGSN
Visited NW
GGSN
user plane
UTRAN Rel-6
GTP
GPRS One-Tunnel Rel-7

GTP
SGSN
GTP
SGSN
control plane
RNC
RNC
NodeB
NodeB
UE
UE
Page 285
REL.8: Lte:
GTP
LTE Tunnel:
Visited NW
S-GW
GTP
MME
GTP
eNB
eNB
UE
Page 286
Lte: IP Transport Technology Options:

L3 IP Details of protocols used for encapsulation are not shown in this diagram
Ethernet L2 MPLS
mc-ml ppp
ATM
WiMAX
(IMA) PHY SDH/SONET DSL PDH
TECHNIQUE
PON
P2P
CWDM
DWDM
P2MP
P2P
MEDIA
fibre
micro-wave
copper
Page 287
Self Optimation Network (SON):

Self configuration and self optimization:
eNB power on (or cable connected)
(A) Basic setup
a-1: Configuration of IP address and detection of OAM server a-2: Authentication of eNB/NW a-3: Association to aGW
Self-Configuration (Pre-operational state)
a-4: Downloading eNB software

(and operational parameters)
(B) Initial radio configuration
b-1: Neighbor list configuration b-2: Coverage/capacity related parameter configuration c-1: Neighbor list optimization c-2: Coverage and capacity control
Self-Optimization (Operational state)
(C) Optimization/ Adaptation
Page 288

Self Optimization & Self Configuration (Insertion of new eNB in network):
Cell A Cell B
Add eNodeB
Cell A
Cell C
Cell D
Cell B
-Add new cell in neighbour list -Configure parameter
Initial Configuration in New Cell: -Configure neighbours -Setup X2 interface -Configure parameter
-Add new cell in neighbour list -Configure parameter
Page 289

Self Optimization & Self Configuration (Handover Parameters Optimisation):
Cell A Cell C Cell D Cell B
- Periodically exchange cell traffic load information (over X2) - Detect congestion
Optimize HO parameters between Cell A and Cell C
Cell A
Cell C
Cell D
Cell B
- Load is balanced between Cell A and Cell C

Page 290
Automated Configuration of Physical Cell Identity:
The physical cell identity, or L1 identity (Phy_ID), is an essential configuration parameter of a radio cell, it corresponds to a unique combination of one orthogonal sequence and one pseudo-random sequence, and 504 unique Phy_IDs are supported leading to unavoidable reuse of the Phy_ID in different cells. When a new eNB is brought into the field, a Phy_ID needs to be selected for each of its supported cells, avoiding collision with respective neighbouring cells.
Page 291
Self Optimation Network (SON): Intra-Lte/frequency Automatic Neighbor Relation Function:
Cell A Phy-CID=3 Global-CID =17
Cell B Phy-CID=5 Global-CID =19
1) report(Phy-CID=5, strong signal)
3) Report Global-CID=19
2b) Read BCH()
2) Report Global-CID Request (Target PhyCID=5)
Page 292

Inter-RAT/Inter-frequency Automatic Neighbour Relation Function:
Cell A Type = LTE Phy-CID= 3 Global-CID =17 2) Report Neighbour Response (Phy-CID, Signal level)
Cell B Type = UTRAN Phy-CID=PSC=5 Global-CID =19
1) Report Neighbour Request (RAT, Frequency)
3b) Read BCH ()
4) Report Global-CID=19
3) Report Global-CID Request (Target Phy-CID=5)
Page 293
Interaction between eNB and O&M due to ANR:
O&M
Add/Update Neighbor Relations
NR report
Neighbor Relation Table

Neighbour Relation O&M controlled Neighbour Relation Attributes
No Remove
Internal Iinformation
NRremove
No HO No X2
NR 1 2
TCI
NRupdate
TCl#1 TCI#1 TCI#1
NRT Managemnt Function
Neighbour Removal Function
NRadd
Neighbour Detection Function
ANR function
Mrmnt requests
Mrmnt reports
RRC
eNB
Page 294
SON Use Cases:

Self-Configuration
Self-Optimization
Maintenance
colour
Network Configuration Authentication Management Automated HW Config.
Energy Detection & Compensation Savings Coverage Hole

Detection
MIMO Mode QoS-related Optimization Adaptive Parameter Channel Optimization Configuration Coverage
Cell Outage
TDD FDD / TDD
Standardized Drive Tests

Subscriber and Equipment Trace
ANR and Capacity Automatic Config. Optimization Generation ANR Automated of Radio OptimizationMobility Interference Parameters Phy Cell ID Optimization Reduction Config. Automated Config.of Load Interfaces Balancing Automatic Generation of Transport Parameters
Planning of Security Node, aGW and OMC
Performance Management
Relay Flexible Management & Spectrum Resource Use Partitioning

MBMS Optimization Automatic SW Download to eNB
Autonomous Inventory
line type
Major Decision in Rel. 8 Major Decision in Rel. 9 Beyond Rel. 9
Frame Sync. and UL/DL switching point coordination
Page 295
REL. 8: Lte:
Lte: New radio interface (DL OFDMA, UL SC-FDMA, flexible bandwidth, MIMO) Integration of GERAN, UTRAN, CDMA2000 and WLAN (WiMax) New network structure (simplified and tunneling) Simplified protocol stacks, combined protocol functions Increase of data rates, decrease of latency
Page 296

LTE Overview

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

LTE Overview

Încărcat de

Drepturi de autor:

Formate disponibile

Lte

Long term evolution

3GPP, CDMA2000 and WiMAX evolution:

WCDMA HSPA HSPA+ Data

LTE-A FDD TDD 3GPP Technologies WLAN

-Integration of GERAN, UTRAN, CDMA2000 and WiMax

REL.8: Lte (Long term evolution):

Users per cell: User plane latency

REL.8: Lte versus WiMax:

Parameter Channel bandwidth

Lte Variable 1.4 20MHz

REL.8: Lte (Long term evolution):

Lte >50Mb/s 20 Carrier bandwidth (MHz)

E-UTRA frequency bands:

UL-DL Band separation:

1710 -1770 MHz

2110 - 2170 MHz

E-UTRA band / channel bandwidth:

OFDMA and SC-FDMA

W-CDMA or CDMA2000 single carrier transmission:

Frequency Division Multiplexing (FDM)

Orthogonal Frequency Division Multiplexing (OFDM)

Orthogonal Frequency Division Multiplexing Access (OFDMA)

Frequency Sub channel A Sub channel B Sub channel C

Orthogonal Frequency Division Multiplexing Access (OFDMA):

OFDM Sub-carrier Organization:

REL.8: LTE (Long Term Evolution):

Frequency Df (Hz) BW (Hz)

REL.8: Lte (OFDMA: Frequency Time representation):

Parallel transmission of data over multiple carriers!

Insertion (copy) of normal Cyclic Prefix (CP): Ts (Symbol Period)

Tu (Useful Symbol Period)

Tg = 4,7 s (5,2 s for the first CP) for Frame structure 1

Insertion of Extended Cyclic Prefix (CP):

Tu (Useful Symbol Period)

Insertion of dedicated MBMS Cyclic Prefix (CP): DL only Ts (Symbol Period)

Tu (Useful Symbol Period)

LTE Uplink: Single Carrier FDMA (SC-FDMA):

Coded symbol rate= R Sub-carrier Mapping CP insertion

LTE Uplink: Single Carrier FDMA (SC-FDMA):

SC-FDMA localized transmission:

Reduced Tx power! Transmission

Transmission of M modulation symbols

SC-FDMA localized transmission:

S/P M Data Symbols

M-DFT CP Insertion P/S

4 Symbols transmitted: Downlink OFDMA:

eNB UE2 UE5 UE1

Modulation Schemes: I QPSK (2bit/symbol) 16QAM (4bit/symbol) 64QAM (6bit/symbol)

Physical Layer Lte

Physical Layer for E-UTRA:

One radio frame, Tf = 307200Ts = 10 ms One slot, Tslot = 15360Ts = 0.5 ms

Physical Layer for E-UTRA:

One radio frame, Tf = 307200Ts = 10 ms One slot, Tslot = 15360Ts = 0.5 ms

Physical Layer for E-UTRA:

One radio frame, Tf = 307200Ts = 10 ms One slot, Tslot = 15360Ts = 0.5 ms

Physical Layer for E-UTRA:

One radio frame, Tf = 307200Ts = 10 ms One half-frame, 153600Ts = 5 ms

One slot, Tslot=15360Ts

Subframe #0 One subframe, 30720Ts DwPTS

Physical Layer for E-UTRA:

One slot, Tslot=15360Ts= 0,5 ms

One subframe, 30720Ts

Physical Layer for E-UTRA: