mpirical courseware

Interactive

LTE Operation
for

Motorola
9th – 13th August 2009

www.mpirical.com
LTE Operation

LTE Operation

MPI4003-01-01 © mpirical limited, 2009 1

 LTE Operation

2 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

LTE Architecture

SWx AAA

HSS
BSC
S6b Rx PSTN
Abis Home PCRF

Gb Gr Server
MS
BTS SGSN S7/Gx
PDN
GW SGi CSCF

IuPS
RNC S7c
Iub
S6a
UE SGi
Node B IP Broadband
S3 SWd
Services

S4 HPLMN
S8
X2 VPLMN
UE eNB X2
eNB MME
S9
Tracking
Area 1 eNB S11

S-GW Visited
S10 PCRF
eNB AAA

UE eNB
Tracking
S2c
Area 2

eNB eNB S7/Gxc

S6b
MME
S11
SWm
S-GW
S1-MME
S5 PDN
UE GW
eNB S2b
Tracking S1-U
Area 3 ePDG
eNB eNB S2a
SWn
ASN
GW Un-trusted Non 3GPP
R6 Trusted Non 3GPP Access Access Network
Network
MS Station Access Point
BS

MPI4003-01-01 © mpirical limited, 2009 3

 LTE Operation

LTE Interface

Reference Point Comments Reference Point Comments

S1-MME For the Control Plane protocol between E-UTRAN and MME. This transfers policy and charging control information between the Home PCRF and
S9
the Visited PCRF in order to support local breakout functions.
For the per bearer User Plane tunnelling and inter eNB path switching during
S1-U
handover between E-UTRAN and Serving GW. This enables MME interaction for MME relocation and MME to MME information
S10 transfer.
It provides the user plane with related control and mobility support between trusted
S2a
non 3GPP IP access and the Gateway. This reference point provides transfer of (QoS) policy information from PCRF to the
Gxa
It provides the user plane with related control and mobility support between ePDG Trusted Non-3GPP accesses.
S2b
and the Gateway.
Gxb Not yet defined.
It provides the user plane with related control and mobility support between UE and
This reference point provides transfer of (QoS) policy information from PCRF to the
S2c the Gateway. This reference point is implemented over trusted and/or untrusted Gxc
Serving Gateway.
non-3GPP Access and/or 3GPP access.
S11 This enables interaction between the MME and S-GW.
This enables user and bearer information exchange for inter 3GPP access network
S3
mobility in Idle and/or Active State. This is the interface between UTRAN and S-GW for User Plane tunnelling when a
S12
This provides control and mobility support between GPRS core and the 3GPP direct tunnel is established.
S4
anchor function of S-GW.
SGi This is the interface the PDN GW and external packet data network.
This provides user plane tunnelling and tunnel management between S-GW and
S5
PDN GW.
This interface connects Untrusted non-3GPP IP Access with the 3GPP AAA Server/
This enables transfer of subscription and authentication data between MME and
S6a SWa Proxy and transports access authentication, authorization and charging-related
HSS.
information in a secure manner.

It is the reference point between PDN Gateway and 3GPP AAA server/proxy for This interface connects the 3GPP AAA Proxy, possibly via intermediate networks, to
SWd
S6b mobility related authentication . It may also be used to retrieve and request storage the 3GPP AAA Server.
of mobility parameters and QoS profile for a mobile for non-3GPP access. This reference point is located between 3GPP AAA Server/Proxy and ePDG and is
SWm
used for AAA and MIP signalling.
This interface between the Untrusted Non-3GPP IP Access and the ePDG supports
SWn
It is the reference point between Serving Gateway in VPLMN and 3GPP AAA Proxy mobile traffic towards the ePDG.
S6c
for mobility related authentication and mobility parameters. This reference point between the UE and the ePDG and supports the handling of
SWu
IPSec tunnels.
This reference point is located between 3GPP AAA Server and HSS and is used for
S7 This transfers policy and charging rules from PCRF to PCEF in the PDN GW. SWx
transport of authentication data.
This transfers User and Control Plane data between the S-GW in the VPLMN and This interface connects the trusted non-3GPP IP Access with the 3GPP AAA
S8 STa Server/Proxy and transports access authentication, authorization, mobility
the PDN GW in the HPLMN.
parameters and charging-related information in a secure manner.

4 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

Initial Attach
Policy and Home
Charging Rules Subscriber
PDN Function Server
S-GW
GW
MME PCRF
HSS
Message
UE eNB S1AP - Initial UE Message
Information Elements
RRC Connection Request eNB UE S1AP ID
NAS PDU - Attach Request
RRC Connection Setup E-UTRAN CGI
RRC Connection Setup Complete TAI
Message Initial UE Message RRC Establishment Cause
EMM - Attach Request Attach Request
Information Elements Attach Request
EPS Attach Type Downlink NAS Transport
NAS Key Set Identifier Message
Old GUTI or IMSI Downlink Information Transfer Identity Request
S1AP - Downlink NAS Transport
UE Network Capability Identity Request Information Elements
ESM Message Container Authentication based on Message
MME UE S1AP ID MAP - Update Location
Uplink Information Transfer eNB UE S1AP ID USIM AKA process.
Information Elements Message
Identity Response Uplink NAS Transport NAS PDU - Identity Request IMSI
- IMSI MAP - Insert Subscriber Data
Identity Response MMEI Information Elements
IMSI
Authentication Process Authentication Process Subscription Data
Default APN, AMBR
Subscribed APN
Message Update Location APN 1, QoS profile 1
GTPv2 - Create Session Request APN 2, QoS profile 2
Message Information Elements ---
S1AP - Initial Context Setup Request S-GW Address (User Plane) Insert Subscriber Data
Information Elements S-GW TEID (User Plane)
MME UE S1AP ID S-GW TEID (Control Plane)
Message
eNB UE S1AP ID Default Bearer QoS, PDN Address Insert Subscriber Data Ack
RRC Connection Reconfiguration Request
UE Aggregate Maximum Bit Rate Allocation, AMBR and EPS Bearer ID
Information Elements
E-RAB to be Setup List
Measurement Configuration
E-RAB ID Update Location Ack
Mobility Control
Transport Layer Address - S-GW
Dedicated NAS Information
GTP-TEID - S-GW
Radio Resource Configuration
UE Security Capabilities Create Session Request
Security Configuration
Security Key
UE Related Information Create Session Request
GUTI
UE IP Address PCRF Interaction
EPS Radio Bearer ID Create Session Response
QoS Parameters
Create Session Response
Initial Context Setup Request
Information Regarding Additional
RRC Connection Reconfiguration Bearers to be Established.
Message
Request S1AP - Downlink NAS Transport
Message
RRC Connection Reconfiguration Information Elements
GTPv2 - Create Session Response
MME UE S1AP ID
Complete Initial Context Setup Response Information Elements
eNB UE S1AP ID
UE IP Address
NAS PDU - Attach Accept
PDN GW Address (User Plane)
Message PDN GW TEID (User Plane)
S1AP - Initial Context Setup Response Downlink NAS Transport PDN GW TEID (Control Plane)
Information Elements EPS Bearer ID
Questions
MME UE S1AP ID
eNB UE S1AP ID
E-RAB to be Setup List
1. What is the identity used by the UE to reference
E-RAB ID Message itself with the MME?
Transport Layer Address - eNB S1AP - Uplink NAS Transport
GTP-TEID - eNB Information Elements
2. What RRC message is used to transport the
MME UE S1AP ID
eNB UE S1AP ID initial NAS message?
Message NAS PDU - Attach Complete Message
EMM - Attach Accept Downlink Information Transfer GTPv2 - Modify Bearer Request 3.What message informs the MME about the
Information Elements
Attach Accept Information Elements mobiles subscribed services?
EPS Attach Result
EPS Bearer ID
T3412 Value Uplink Information Transfer
eNB Address (User Plane)
TAI List Attach Complete Uplink NAS Transport 4. What message passes the S-GW uplink tunnel
eNB TEID (User Plane)
ESM Message Container
information to the eNB?
GUTI
Uplink Data Flow
5. Why does the MME need to send a Modify
Message Modify Bearer Request Bearer Request to the S-GW?
EMM - Attach Complete
Information Elements
ESM Message Container Modify Bearer Response
Downlink Data Flow

MPI4003-01-01 © mpirical limited, 2009 5

 LTE Operation

Dedicated Bearer

S-GW PDN
GW
MME PCRF

UE eNB

Message
E-RAB Setup Request
Information Elements
MME UE S1AP ID
eNB UE S1AP ID
Message UE Aggregate Maximum Bit Rate
RRC Connection Reconfiguration Request E-RAB to be Setup List
Information Elements NAS-PDU
Measurement Configuration Activate Dedicated EPS Bearer Context Request
Mobility Control Information LBI (Linked Bearer Identity)
NAS-Dedicated Information List EPS QoS
Activate Dedicated EPS Bearer Context Request TFT PCRF Initiated
Radio Resource Configuration Protocol Configuration Options Session Modification Begin
DRB To Add Modify List
MAC Main Configuration
Physical Configuration - Dedicated Create Bearer Request
Security Configuration Note: It is also possible that the
Create Bearer Request UE can request a bearer resource
E-RAB Setup Request modification. In this case a Bearer
Resource Command message is
RRC Connection Reconfiguration
sent from a MME to a SGW and
Request
Message forwarded to PGW.
RRC Connection Reconfiguration Create Bearer Request
Complete E-RAB Setup Response Information Elements
PTI (Procedure Transaction Identity)
LBI (Linked Bearer Identity)
Message APN-AMBR
Message
RRC Connection Reconfiguration Complete Protocol Configuration Options
E-RAB Setup Response
Information Elements Bearer Contexts
MME UE S1AP ID EPS Bearer ID =0
eNB UE S1AP ID TFT
E-RAB to be Setup List Bearer Level QoS
Charging Information
TEIDs

Uplink Information Transfer

Uplink NAS Transport
Create Bearer Response
Message Create Bearer Response
Uplink Information Transfer PCRF Initiated
Information Elements Session Modification End
NAS-Dedicated Information
Activate Dedicated EPS Bearer Context Accept Message Message
Uplink NAS Transport Create Bearer Response
Information Elements Information Elements
MME UE S1AP ID Cause
eNB UE S1AP ID Bearer Contexts
NAS PDU EPS Bearer ID (Allocated By MME)
Activate Dedicated EPS Bearer Context Accept Cause
TFT
TEIDs

6 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

Authentication Procedure

Based on the user’s IMSI the AuC

identifies K, it generating a fresh
K + IMSI sequence number SQN and an
unpredictable challenge RAND.
MME

AuC K
UE USIM eNB
Includes the UE identity
(GUTI), security capabilities
of the UE, and KSASME.
RRC Connection

NAS Signalling
Authentication Data Request
MCC+MNC+MSIN, MME ID

RAND K Optional SQN

AMF
f1 f2 f3 f4 f5 xor
SQN

MAC-A XRES CK IK AK SQN AK

Upon receipt of RAND and AUTN the USIM computes the AK
anonymity key using f5, K and RAND. It then retrieves the sequence
number SQN and computes X-MAC using f1, K, RAND and AMF. AV = (RAND II XRES II CK II IK II AUTN)
Next it compares this with MAC-A which is included in AUTN. If they
are different, the user sends the Authentication Reject message AUTN = SQN [ AK] AMF MAC-A
back to the MME with an indication of the cause and the user
abandons the procedure. In this case the MME initiates an
Authentication Failure Report procedure towards the HSS.

Authentication Data Response

Authentication Request
RAND II AUTN
RAND K Optional SQN AK The MME stores the AV and challenges The AuC sends an authentication
the UE using the User Authentication response back to the MME that usually
Request Message containing the contains an array of authentication
challenge RAND and the AUTN. vectors.

AMF
f1 f2 f3 f4 f5 xor
SQN

X-MAC RES CK IK AK SQN Questions

AUTN = SQN [
RES is computed using f2, K and RAND.
This is then sent back in an Authentication
Response messages back to the MME.
1. Which scenarios will trigger the Authentication
AK] AMF MAC-A procedure to be conducted, and which function
prompts this?
Upon receipt of user Authentication
Response the MME compares RES with 2. List the keys that are derived in the network from
the XRES (Expected Response) from the CK and IK?
selected Authentication Vector. If XRES
equals RES then the authentication of the 3. What is the reason for the MAC-A variable in the
user is successful. Authentication Request message?
Authentication Response

RES

MPI4003-01-01 © mpirical limited, 2009 7

 LTE Operation

Key Distribution

HSS Ks

Network ID 256
KeNB KeNB*
256
256 KDF
eNB

Ks KeNB*

Network ID 256

KDF
UE KDF
KDF
Physical 256
Cell ID Physical
256 Cell ID 256
KeNB eNB MME
KeNB
KASME 256 KASME

KDF
KDF

256 UP-enc-alg, RRC-enc- 256

NAS Alg-ID alg, Alg-ID NAS
COUNT RRC-int-alg, RRC-int-alg, COUNT
Alg-ID Alg-ID
RRC-enc-alg, UP-enc-
NAS-enc-alg, NAS-int-alg, Alg-ID alg, Alg-ID NAS-enc-alg, NAS-int-alg,
Alg-ID Alg-ID Alg-ID Alg-ID
KDF KDF KDF KDF KDF KDF KDF KDF KDF KDF

256 256 256 256 256 256 256 256 256 256

256bit 256bit 256bit 256bit

KNASenc KNASint KRRCenc KRRCint KUPenc KRRCenc KRRCint KUPenc KNASenc KNASint
Keys Keys Keys Keys

256 256 256 256 256 256 256 256 256 256

Trunc Trunc Trunc Trunc Trunc Trunc Trunc Trunc Trunc Trunc

128 128 128 128 128 128 128 128 128 128

128bit 128bit 128bit 128bit

KNASenc KNASint KRRCenc KRRCint KUPenc KRRCenc KRRCint KUPenc KNASenc KNASint
Keys Keys Keys Keys

8 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

IP Datagram Mapping

TCP/IP Header TCP/IP Header

TCP/IP (40 Bytes)
Payload (E.g. HTTP)
(40 Bytes)
Payload

2 Bytes
PDCP PDCP
PDCP Header Typically
PDCP SDU
Header
PDCP SDU

compressed
to ~ 3 bytes

RLC SDU RLC SDU

Segment fits required TB Segment fits required TB

RLC (Transport Block) size (Transport Block)

UM (Unacknowledged Mode) or
AM (Acknowledged Mode) header
RLC Segment RLC

Questions
1. Which layer performs encryption/ciphering?

MAC
MAC SDU Padding
MAC Header 2. What parameter in the RLC header is used to
identify the start or the end of the RLC SDU?

3. What parameter in the MAC header is used to

link this MAC SDU to the Radio Bearer?

PHY Transport Block CRC

MPI4003-01-01 © mpirical limited, 2009 9

 LTE Operation

LTE Control and User Planes

Control Plane
NAS NAS GTPv2-C GTPv2-C

RRM

RRC RRC S1AP S1AP

Change compared to
HSPA
PDCP PDCP SCTP SCTP UDP UDP
High
RLC RLC IP IP IP IP
Medium High
MAC MAC Layer 2 Layer 2 Layer 2 Layer 2
Medium Low
PHY PHY Layer 1 Layer 1 Layer 1 Layer 1
Low

MME S-GW

UE

eNB

User Plane
IP IP

PDCP PDCP GTP-U GTP-U GTP-U GTP-U

RLC RLC UDP UDP UDP UDP

MAC MAC IP IP IP IP

PHY PHY Layer 2 Layer 2 Layer 2 Layer 2

Layer 1 Layer 1 Layer 1 Layer 1

S-GW PDN
GW

UE
eNB

10 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

PRACH Configuration

PRACH Subcarrier Spacing

The PRACH subcarriers utilize a 1.25KHz
subcarrier spacing . Thus 1/1.25KHz = 0.8ms.

Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe
0 1 2 3 4 5 6 7 8 9
RB 24

PRACH-Configuration
Root Sequence Index (0 to 837)
PRACH Configuration Index (0 to 63)
High Speed Flag
Zero Correlation Zone Configuration (0 to 15)
PRACH Frequency Offset (0 to 104)

839 Subcarriers
PRACH Baseband Parameters
Formats 0-3 have a 7 subcarrier C C C
ZC ZC ZC
offset. Format 4 has a 2 P P P
subcarrier offset .

Preamble Sequence Length

RB 0
For preamble formats 0-3 the N ZC length is 839,
however for Format 4 the N ZC is 139. The latter is
when using frame structure type 2 and special
subframe configurations with UpPTS lengths 4384 TS
and 5120 TS only (7.5KHz subcarrier Configuration ).

PRACH Frequency
Questions
Offset (0 to 104
Resource Blocks) eNB indicates that
preamble /ZC sequence 1. How many Resource Blocks are used to provide a PRACH opportunity ?
was received. Includes
initial UL grant
2. Where is PRACH format 4 used?

Open Loop
Power Control 3. What is the normal subcarrier spacing for the PRACH ?

Noise/ 4. How many subcarrier are sent in the PRACH ?

Interference
Scheduled Message
E.g. RRC Connection Request 5. For PRACH formats 0-3, what is the value of the subcarrier offset (number of
subcarrier from the edge of the physical resource block allocation )?

PRACH PRACH PRACH DPCCHDL PUSCH

-SCH

MPI4003-01-01 © mpirical limited, 2009 11

 LTE Operation

HARQ Operation
HARQ
Scheduling Methods Questions
For FDD, there are 8 HARQ processes in the downlink. In
contrast the uplink has 8 HARQ processes for non-subframe LTE supports Dynamic and Semi-persistent scheduling, the latter being used to reduce 1. How many HARQ Processes in the
bundling operation, i.e. normal HARQ operation, and 4 HARQ the amount of control channel overhead/signalling. This enables the eNB scheduler to UL and DL for FDD?
processes in the uplink for subframe bundling operation. The efficiently schedule resources for application/bearers which have a continual allocation
number of HARQ processes for TDD is related to the frame requirement, e.g. VoIP. The semi-persistent allocation persists until the eNB scheduler
configuration and varies between 4 and 15. changes it.
2. What is the number of frames
between a FDD HARQ downlink
Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe transmission and its ACK/NACK?
0 1 2 3 4 5 6 7 8 9 0 1
Semi Semi Semi
DL-SCH Dynamic
Persistent Persistent Persistent
3. What is the advantage of “Semi-
Persistent” scheduling?
Downlink
eNB PDCCH D S
Scheduling and
HARQ

PUCCH ACK NACK ACK ACK

UE k
HARQ
For FDD, when both ACK/NACK and SR are
ACK NACK Timing transmitted in the same sub-frame a UE transmits
For Frame Structure type 1 (FDD), an ACK/NACK received on the PHICH assigned to a UE in subframe i is the ACK/NACK on its assigned ACK/NACK PUCCH
associated with the PUSCH transmission in subframe i-4. resource for a negative SR transmission and
For Frame Structure type 2 (TDD) UL/DL configuration 1-6, an ACK/NACK received on the PHICH assigned transmit the ACK/NACK on its assigned SR PUCCH
to a UE in subframe i is associated with the PUSCH transmission in the subframe i-k. Where k is defined in a resource for a positive SR transmission. In TDD
table (36.213). Note that when using frame configuration 0, depending on the value of PHICH, k either there are also mapping rules, however the outcome
relates to the table or is equal to 7. depends on the use of subframe bundling, as well
as the possible requirement to multiplex multiple
ACK/NACKs.
TDD ACK Modes
For TDD, two ACK/NACK feedback modes
are supported by higher layer configuration.
- ACK/NACK bundling.
- ACK/NACK multiplexing.
For TDD ACK/NACK bundling, HARQ-ACK
consists one or two bits or information. For
TDD ACK/NAK multiplexing, HARQ-ACK
consists of between one and four bits of
information.

Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe
0 1 2 3 4 5 6 7 8 9 0 1

DL-SCH

eNB PDCCH D D
Uplink
Scheduling and
HARQ
PHICH A N

PUSCH Dynamic Dynamic

UE 4 Frames (FDD)

12 © mpirical limited, 2009 MPI4003-01-01

LTE Operation
System Information Messages
Subframe Subframe Subframe Subframe Subframe Subframe Subframe
0 1 2 3 4 5 6 7
NRB
Frame 0 Frame 1 Frame 2 Frame 3 Frame 4 Frame 5
MIB (Master Information Block)
Repeats every 40ms and uses a 40ms SIB2 (System Information Block Type 2)
TTI (Time Transmission Interval). Information Elements
Aligned to SFN mod 4 = 0 Access Class Information
Information Elements
Uplink Carrier Frequency
DL-Bandwidth (6, 15, 25, 50, 75, 100) UL Bandwidth
PHICH Configuration MBSFN Configuration Information
System Frame Number
SIB3 (System Information Block Type 3)
Information Elements
Cell Reselection Information
Q-Hyst
Speed State Reselection Parameters
Q-Hyst Speed SF (Scaling Factor)
Treselection EUTRA
Treselection EUTRA SF
S Intra Search
Cell Reselection Serving Freq Info
S-Non-Intra Search Info
Threshold Serving Low Value
Intra Freq Cell Reselection Info
p-Max
Allowed Measurement Bandwidth
MPI4003-01-01
Subframe Subframe Subframe
8 9
Frame 6 Frame 7 Frame 8
SIB4 (System Information Block Type 4)
Information Elements
Intra Freq Neighbour Cell List
q-OffsetCell
Intra Freq Black Cell List
CSG Physical Cell Id Range
SIB5 (System Information Block Type 5)
Information Elements
Inter Frequency Carrier Freq List
Inter Frequency Carrier Freq Info
Inter Frequency Neighbour Cell List
Inter Frequency Neighbour Cell Info
Inter Frequency Black Cell List
Inter Frequency Black Cell Info
SIB6 (System Information Block Type 6)
Information Elements
Carrier Frequency List UTRA
UTRA Reselection Information
© mpirical limited, 2009
SIB1 (System Information Block Type 1)
Repeats every 80ms and uses a 80ms TTI (Time Transmission Interval). Aligned to
subframe 5 and starts in SFN mod 8 = 0.
Information Elements
PLMN Identity List
Tracking Area Code
Cell Barred Indication
Intra Frequency Reselection
CSG Indication (TRUE - the UE CSG (Closed Subscriber Group) identity needs to match)
CSG Identity
Qrxlevminoffset
P-Max
Frequency Band Indicator
SI Periodicity Mapping Information
SIB Window Length (Common SI scheduling window for all SIB: 1, 2, 5, 10, 15, 20, 40ms)
System Info Value Tag
Frame 9 Frame 10 Frame 11 Frame 12 Frame 13 Frame 14
SIB7 (System Information Block Type 7)
Information Elements
Carrier Frequency List GERAN
Questions
GERAN Reselection Information
1. How often is SIB1 sent?
SIB8 (System Information Block Type 8)
Information Elements 2. Which SIB carries Intra Frequency cell
CDMA2000 Information information?
3. What subframe is used to send the MIB?
SIB9 (System Information Block Type 9)
Information Elements
Home eNB Name 4. How quickly can the SIB’s 2-9 be sent?
5. Which SIB contains the main cell
reselection information?
13
 LTE Operation

MIMO Operation

MIMO and Transmission Options SU-MIMO

The mobile is semi-statically configured via higher layer signalling to receive PDSCH data transmissions signalled Increases a user’s capacity by
via PDCCH. Part of this signalling include the method of transmission. In LTE the following Transmission Modes enabling a single user to benefit
are included: from multiple data streams.
*Depends on the DCI and
1/ Single-Antenna transmission, port 0, no MIMO.
RNTI configuration.
2/ Transmit diversity.
3/ Transmit diversity or Large Delay CDD*.
4/ Transmit diversity or Closed-loop spatial multiplexing*, UE feedback required. SU-MIMO
MU-MIMO
5/ Transmit diversity or Multi-user MIMO* (more than one UE is assigned to the same resource block).
6/ Transmit diversity or Closed-loop precoding* for rank=1 (i.e. no spatial multiplexing, but precoding is used).
7/ Single-antenna port*; port 5 (Beamforming).
MIMO Base
UE
MIMO Base Station
Station
CDD (Cyclic Delay Diversity)
Transmit Diversity (Space Time Coding) In LTE, Cyclic Delay Diversity can be used in
For transmit diversity, the layer mapping is done conjunction with spatial multiplexing. This adds an MU-MIMO
according to a Table in the 36.211 specification. Note additional antenna specific delay to the signals UE Increases sector capacity by
that there is only one codeword used and the number of transmitted. As a result, it introduces artificial selecting users in good channel
layers is equal to the number of antenna ports used for multipath and thus increases the diversity in the conditional and sharing their UE
transmission of the physical channel. Precoding for channel. LTE supports various configurations e.g. data streams.
transmit diversity is used in combination with layer zero, small or large delay.
mapping for transmit diversity. ThIs is defined for two
and four antenna ports.
Spatial Multiplexing MIMO in LTE
Transmit Diversity MIMO in LTE
Spatial Multiplexing
LTE allows up to two code words to be mapped onto different layers. The system can
Layers Antenna Ports use precoding to enable spatial multiplexing. This diagram illustrates the mapping of
codebook index onto layers for a 2 transmit antenna configuration. Note that the 36.211
Resource OFDMA specification includes the detail of precoding and layer mapping equations for the
Element Signal different techniques and also for 4 antenna configurations.
Mapper Generation For the closed-loop spatial multiplexing transmission mode, the codebook index 0 is not
Layer used when the number layers is equal to 2.
Modulation Precoding
Scrambling Mapper
Mapper
Resource OFDMA
Element Signal CodeBook Number of Layers
Mapper Generation Index 1 2
1 Codeword
1 1 1 1 0
0
2 1 2 0 1

Adaptive MIMO Spatial

1 1 1 1 1
Multiplexing
Efficiency

To truly optimize the channel efficiency, some systems 1

offer the ability to support adaptive MIMO switching. The 2 -1 2 1 -1
diagram illustrates how a system could utilize a mixture
of Spatial Multiplexing and Transmit Diversity. As can be
seen in the diagram, a device close to the base station Transmit 1 1 1 1 1
could use Spatial Multiplexing, and thus increase Diversity 2
network performance, whereas a mobile on the edge of 2 j 2 j -j
the cell could use Transmit Diversity. The latter
providing better resilience-to-interference. MIMO Base
MIMO 1 1
Low SNR High SNR Station
Handset 3 -
2 -j

14 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

FDD/TDD Timing

FDD Operation
For FDD and normal HARQ operation. If a UE detects a
PDCCH with DCI format 0 and/or a PHICH LTE Bundling
transmission in subframe n intended for the UE, will LTE also supports subframe bundling where a bundle of
adjust the corresponding PUSCH transmission in PUSCH transmissions consists of four consecutive uplink
subframe n+4 according to the PDCCH and PHICH subframes in both FDD and TDD. The subframe bundling
information. operation is configured by the parameter “ttiBundling”
provided by higher layers.
PDCCH For FDD and subframe bundling, the UE upon detection of
a PDCCH with DCI format 0 in subframe n intended for the
UE, and/or a PHICH transmission in subframe n-5
FDD Downlink
intended for the UE, adjusts the corresponding first
FDD Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe PUSCH transmission in the bundle in subframe n+4
0 1 2 3 4 5 6 7 8 9 0 1 according to the PDCCH and PHICH information.

FDD
:K =4

FDD Uplink
Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe
0 1 2 3 4 5 6 7 8 9 0 1

4 Subframe Delay
PUSCH

K for DL/UL Configurations 0-6

TDD Operation TDD UL/DL DL Subframe Number n
For TDD UL/DL configurations 0-6 and normal Configuration 0 1 2 3 4 5 6 7 8 9
HARQ operation the UE, upon detection of a 0 4* 6* 4* 6*
PDCCH with DCI format 0 and/or a PHICH 1 6 4 6 4
transmission in subframe n intended for the
UE, adjusts the corresponding PUSCH 2 4 4
transmission in subframe n+k, with k given in 3 4 4 4
the table shown, according to the PDCCH and 4 4 4
TDD PHICH information. 5 4
6 7 7 7 7 5

PDCCH * Depending on certain conditions in 36.213 (related to UL

Index or PHICH location) this can be configured as 7.
Frame Configuration 2
DSUDDDSUDD
Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe Subframe
0 1 2 3 4 5 6 7 8 9 0 1 2 3

4 Subframe Delay
PUSCH
Switch to Uplink Switch to Downlink

MPI4003-01-01 © mpirical limited, 2009 15

 LTE Operation

Timing Advance

Downlink Radio Frame n-2 Downlink Radio Frame n-1 Downlink Radio Frame n Downlink Radio Frame n+1

eNB
Uplink Radio Frame n-2 Uplink Radio Frame n-1 Uplink Radio Frame n Uplink Radio Frame n+1

Uplink Radio Frame (No Timing Advance) Uplink Radio Frame (With Timing Advance)

Timing Advance

Downlink/Uplink Timing Relationship

Timing Advance
The uplink frame transmission takes place approximately (NTA + NTA offset )×TS
seconds before the reception of the first detected path of the corresponding
downlink frame. Where NTA offset = 0 for frame structure type 1 and NTA offset = 624
for frame structure type 2.
If the mobile receives a timing advance command on subframe n, the corresponding
adjustment of the timing is applied from the beginning of subframe n+6.
Note that when the mobiles uplink PUCCH/PUSCH/SRS transmissions in subframe
n+5 and subframe n+6 are overlapped due to the timing adjustment, the mobile
transmits a complete subframe n+5 and does not transmit the overlapped part of
subframe n+6.

Uplink Radio Frame (No Timing Advance) Uplink Radio Frame (With Timing Advance) Uplink Radio Frame (With Timing Advance)
UE

11 Bit Timing Advance

This indicates NTA values by index values of TA = 0, 1, 2, ..., 1282, where an amount of the
time alignment is given by NTA = TA × 16.
6 Bit Timing Advance
This indicates adjustment of the current NTA value, NTA,old, to the new NTA value, NTA,new,
by index values of TA = 0, 1, 2,..., 63, where NTA,new = NTA,old + (TA - 31)×16. Thus,
adjustment of the NTA value by a positive or a negative amount indicates advancing or
delaying the uplink transmission timing by a given amount respectively.
Timing Requirements
The mobile’s initial transmission timing error must be less than or equal to ±12xTs seconds (=3MHz) or ±24xTs
seconds (1.4MHz).
The downlink timing is defined as the time when the first detected radio path of the corresponding
downlink frame is received from the reference cell.
All adjustments made to the UE timing shall follow these rules:
1) The maximum amount of the timing change in one adjustment is 2xTS (=3MHz) or 4xTS (1.4MHz) seconds.
2) The minimum adjustment rate is 7xTS seconds per second.
3) The maximum adjustment rate is 2xTS (=3MHz) or 4xTS (1.4MHz) seconds per 200ms.

Timing Advance Calculation Example Round trip One way Maximum Timing
Round trip delay distance distance Advance Value Maximum Range
TS = 32.552ns

Timing Advance step sizes = 16xTS = 0.5208µs (3 x 108 m/s) x 0.5208µs = 156.25m (156.25m / 2) = 78.125m per step 1282 x 78.125m = 100.15625Km

16 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

Feedback Mechanisms

Feedback Reporting PMI Feedback Type

In order to optimize the systems performance mobiles can provide various feedback information about the radio channel
No PMI Single PMI
environment. LTE has various feedback reporting options which depend on the MIMO and eNB configuration. The

Feedback Type
reporting may consist of the following elements: Wideband

PUCCH CQI
CQI (Channel Quality Indicator) Mode 1-0 Mode 1-1
(Wideband CQI)
This provides an indication of the downlink channel quality and effectively identifies an optimum modulation and coding
scheme for the eNB to use. There are various coding options for the CQI, with the main CQI index ranging from 0 to 16.
The system defines multiple types of CQI, the term “wideband CQI” relates to the entire system bandwidth. In contrast, UE Selected
Mode 2-0 Mode 2-1
“sub-band CQI” relates to a value per sub-band. This is defined and configured by the higher layers and relates to (Subband CQI)
number of resource blocks. It is also worth noting that a CQI per codeword is reported for MIMO spatial multiplexing.
PMI (Precoding Matrix Indicator)
This enables the mobile to select an optimal precoding matrix. The PMI value relates to a codebook table within the
specifications. Like sub-band CQI, the eNB defines which resource blocks are related to a PMI report. The PMI reports Options
are used in various mode, including: closed loop spatial multiplexing, multi-user MIMO and closed-loop rank 1 Transmission Mode 1: Modes 1-0, 2-0
precoding. Transmission Mode 2: Modes 1-0, 2-0
RI (rank indication) Transmission Mode 3: Modes 1-0, 2-0
This indicates the number of useful transmission layers when spatial multiplexing is used. Thus, in case of transmit Transmission Mode 4: Modes 1-1, 2-1
diversity, rank is equal to 1 (RI=1). Transmission Mode 5: Modes 1-1, 2-1
Transmission Mode 6: Modes 1-1, 2-1
Periodic and Aperiodic CQI Transmission Mode 7: Modes 1-0, 2-0
Depending on the scheduling mode Periodic and Aperiodic CQI reporting can be used.
In “Frequency Non-selective” and “Frequency selective” mode the PUCCH is used to carry periodic CQI reports. In
contrast in “Frequency selective” mode the PUSCH is used to carry aperiodic CQI reports.
PMI Feedback Type
No PMI Single PMI Multiple PMI

Wideband

PUSCH CQI Feedback

Mode 1-1 Mode 1-2
(Wideband CQI)

PUCCH Reporting Modes (bits/BP)

Type
PUCCH Report Type Reported Mode State UE Selected
Mode 1-1 Mode 2-1 Mode 1-0 Mode 2-0 Mode 2-0 Mode 2-1 Mode 2-2
(Subband CQI)
RI=1 NA 4+L NA 4+L
1 Sub-band CQI
RI>1 NA 7+L NA 4+L Higher Layer
2 TX Antennas RI=1 6 6 NA NA Configured Mode 3-0 Mode 3-1
Wideband CQI/ 4 TX Antennas RI=1 8 8 NA NA (Subband CQI)
2
PMI 2 TX Antennas RI>1 8 8 NA NA
4 TX Antennas RI>1 11 11 NA NA
2 Layer SM 1 1 1 1
3 RI Options
4 Layer SM 2 2 2 2 Transmission Mode 1: Modes 2-0, 3-0
4 Wideband CQI RI=1 or RI>1 NA NA 4 4 Transmission Mode 2: Modes 2-0, 3-0
Transmission Mode 3: Modes 2-0, 3-0
Transmission Mode 4: Modes 1-2, 2-2, 3-1
Transmission Mode 5: Modes 3-1
Transmission Mode 6: Modes 1-2, 2-2, 3-1
Transmission Mode 7: Modes 2-0, 3-0

MPI4003-01-01 © mpirical limited, 2009 17

 LTE Operation

S1 Protocols

S-GW
MME

eNB eNB

User IP Datagrams User IP Datagrams

S1 Application Part S1 Application Part
(SDU) (SDU)

Radio Network Layer

Transport Network Layer

GTPv1-U paths identified by IP

S1AP identified through SCTP SCTP SCTP GTPv1-U GTPv1-U address and port number of each
port or protocol ID in SCTP endpoint. Packets are
header. multiplexed onto GTP paths
using TEID.

GTPv1-U identified through the

SCTP provides a robust reliable UDP UDP IANA registered port 2152.
delivery mechanism to S1 AP.

UDP provides a best effort

transport service to GTPv1-U.
IP IP IP IP

S1-MME Interface S1-U Interface

IP Addressing is used to route IP Addressing is used to route
S1 AP messages between S1 GTPv1-U messages between
endpoints such as the eNB and S1-U endpoints such as the eNB
MME. and S-GW

Question
List the main functions of the S1 Application Part in the space provided below.

18 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

S1 Handover Procedure

S-GW
S-GW PDN
GW
MME MME

UE eNB eNB HSS

Target
Source Target Source Target Source

Identity of target eNB triggers handover/relocation process Message

Handover Request
Information Elements
Handover Required MME UE S1AP ID
Forward Relocation Request Handover Type - Intra LTE, LTE to UTRAN, LTE to GERAN
Cause
Create Session Request UE Aggregated Maximum Bit Rate
Message RABs to be Setup List
Handover Required E-RAB ID
Information Elements Create Session Response Transport Layer Address
MME UE S1AP ID GTP TEID - UL Traffic
eNB UE S1AP ID
Handover Request
E-RAB QoS Parameters
Handover Type - Intra LTE, LTE to UTRAN, LTE to Source to Target Transparent Container
GERAN
Cause
Handover Request Ack UE Security Capabilities
Security Context
Target ID Create Session Request
Direct Forwarding Path Availability
SRVCC HO
Source to Target Transparent Container Create Session Response
Forward Relocation Response

Create Session Request Message

Handover Request Acknowledge
Information Elements
Create Session Response MME UE S1AP ID
Handover Command eNB UE S1AP ID
RRC Connection Message Handover Type - Intra LTE, LTE to UTRAN, LTE to
Reconfiguration Handover Command GERAN
Request Direct Forwarding Information Elements RABs to be Setup List
MME UE S1AP ID E-RAB ID
eNB UE S1AP ID Transport Layer Address
Indirect Forwarding Handover Type - Intra LTE, LTE to UTRAN, LTE to GERAN GTP TEID
NAS Downlink COUNT Target to Source Transparent Container
E-RABs Subject to Forwarding List
E-RAB ID
Transport Layer Address
Handover Confirmed DL GTP TEID Message
UL GTP TEID Handover Notify
Target to Source Transparent Container Information Elements
Downlink Data MME UE S1AP ID
Uplink Data eNB UE S1AP ID
E-UTRAN CGI
TAI
Handover Notify UE Security Capabilities

Forward Relocation Complete

Forward Relocation Complete Ack

SI AP Messages Modify Bearer Request
Modify Bearer Request
GTPv2-C Messages
Modify Bearer Response
Modify Bearer Response

Downlink Data

TAU Procedure Follows

MPI4003-01-01 © mpirical limited, 2009 19

 LTE Operation

E-UTRA Handover Messages

S-GW
MME

UE eNB Message eNB

Measurement Report
Source Information Elements Target
Trigger Met
Cell ID
RRC Connection Reconfiguration

Measurement and
Measurement Control

Reporting
Packet Data Transfer

Measurement Report

Message
RRC Connection Reconfiguration Handover Request
Information Elements Admission Control
MeasConfig 1 Reserve Radio Resources.
Event A1 (Serving becomes better than threshold) 1 Establish RAB.

Handover Preparation Phase

Event A2 (Serving becomes worse than threshold)
Admission Control 1 Allocate C-RNTI to scheduler.
Event A3 (Neighbour becomes offset better than serving )
Event A4 (Neighbour becomes better than threshold )
Event A5 (Serving becomes worse than threshold1 and
neighbour becomes better than threshold 2)
Handover Request Ack
Questions
RRC Connection Reconfiguration
1. What is the main message that is used to
Handover Command configure the UE measurement reports?
Forward buffered and
Detach from source
in-transit data to the
eNB
target eNB 2. Which radio characteristics are measured by the
UE and reported in uplink measurement reports?
Forward user data

3. If contention free access is to be performed by

the UE what must be provided to it by the target
RACH Process eNB?

RRC Connection Reconfiguration Complete

RACH Preamble allocated by
target eNB (Contention Free).

Handover Execution Phase

Path Switch
Using New C-RNTI User Plane Update Request

Switch downlink path to

target eNB

User Plane Update Response

Path Switch Ack

Packet Data Transfer

Release Resources

20 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

IMS Registration
ISIM

P I S
CSCF CSCF CSCF
RAN DNS

SIP Agent
Initial Registration
DNS Query

Initial Registration SLF

Dx-SLF-Query

Dx-SLF-Response
HSS

Cx-Query

Cx-Query-Response

Cx-Select-Pull

Cx-Select-Pull-Response

Initial Registration

Cx AuthDataRequest

Cx AuthDataResponse
Generate 401 Unauthorized
Session
Keys 401 Unauthorized

401 Unauthorized

Generate
Response
and Session
Keys
Subsequent Registration
Subsequent Registration
Subsequent Registration Check Response

Cx_Put

Cx_Put_Response

Cx_Pull

Cx_Pull_Response

200 OK
200 OK
200 OK

MPI4003-01-01 © mpirical limited, 2009 21

 LTE Operation

IMS Session

S-GW PDN P S
GW CSCF CSCF
PCEF
CGF PCRF

SIP Agent Application Server

EPS Bearer Context - (IMS Signalling) INVITE

(as@homenetwork.net) INVITE (as@homenetwork.net)
INVITE (as@homenetwork.net)

183 (Session Progress)

183 (Session Progress)

Authorize QoS
Policy Information

Dedicated EPS Bearer Establishment

183 (Session Progress)

PRACK
PRACK
PRACK

200 OK PRACK
200 OK PRACK
200 OK PRACK

UPDATE
UPDATE UPDATE Preconditions
Preconditions Met (Remote)
200 OK UPDATE
Met (Local) 200 OK UPDATE
200 OK UPDATE

200 OK INVITE
200 OK INVITE
200 OK INVITE

Ack Ack
Ack

22 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

Tracking Area Update

Message
Context Request
Information Elements
IMSI
GUTI
Complete TAU Request Message
S-GW S-GW PDN
GW
MME MME
HSS
UE eNB
New Old New Old
Message
Tracking Area Update Request Context Request
Context Request Information Elements
MM Context
Message IMSI, AVs, S-GW Control Plane address and TEID
Tracking Area Update Request Context Response EPS Bearer Context
Information Elements Plane address and TEI PDN GW Control lD
EPS Update Type
Old GUTI
AKA Authentication
NAS KSI ASME
NAS KSI SGSN
Context Acknowledge

Message
Create Session Request Create Session Request
Information Elements
IMSI
RAT Type Modify Bearer Request
Indication Flags
Sender F-TEID for Control Plane
PDN Type Modify Bearer Response
Maximum APN Restriction
Bearer Contexts
Create Session Response

Message Update Location

Create Session Response
Information Elements
Cause Cancel Location
PGW S5/S8 Address for Control
Plane
APN Restriction Cancel Location Ack
Bearer Contexts Created

Insert Subscriber Data

Message
Tracking Area Update Accept Insert Subscriber Data Ack
Information Elements
EPS update result
GUTI Update Location Ack
TAI List

Delete Bearer Request Questions

1. What triggers the UE to perform a TAU?

Tracking Area Update Accept Delete Bearer Response
2. If no context information is available within the
Tracking Area Update Complete old MME which additional signalling process will
need to be included in the TAU?

UE Triggered Service Request Procedure 3. In which part of the process are the downlink IP
tunnels to the New S-GW defined?

Uplink and Downlink Traffic Flow

MPI4003-01-01 © mpirical limited, 2009 23

 LTE Operation

EPC Relocation

S-GW PDN
S-GW
GW
MME MME

UE eNB eNB HSS

Target
Source Target Source Target Source

Identity of target eNB triggers relocation process Allocation of Uplink PDN-GW Allocation of uplink S-GW
IP address and Uplink TEID. IP address and TEID for
Handover Required S1-U interface.
Forward Relocation Request
Create Bearer Request
Uplink IP address and Employed if “one
TEID of target S-GW. tunnel” not
Create Bearer Response
supported.
Handover Request

Handover Request Ack

Create Bearer Request
Employed if “one
Allocation of target eNB IP Create Bearer Response tunnel” supported.
address and downlink Forward Relocation Response
TEID.
Target S-GW IP address Create Bearer Request
and TEID for indirect Allocation of uplink S-GW
forwarding. Target S-GW IP address IP address and TEID if
Create Bearer Response indirect forwarding is to be
and TEID for indirect
Handover Command forwarding. used.
RRC Connection
Reconfiguration
Handover Command Direct Forwarding Target eNB IP address
and forwarding TEID
Indirect Forwarding (direct forwarding only).

RRC Connection Reconfiguration Complete

Handover Confirmed
Downlink Data
Uplink Data

Handover Notify
Allocation of downlink GTP EPC tunnel
Forward Relocation Complete target eNB IP address and management only.
TEID for S1-U interface.
Forward Relocation Complete Ack
Update Bearer Request
Update Bearer Request

Update Bearer Response

Update Bearer Response

Downlink Data

TAU Procedure Follows

24 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

X2 Protocols

eNB eNB eNB eNB

X2 Application Part X2 Application Part User IP Datagrams User IP Datagrams

Radio Network Layer

Transport Network Layer GTPv1-U paths identified by IP

address and port number of each
X2AP identified through SCTP endpoint. UE SDU multiplexed
port or protocol ID in SCTP onto GTP paths using TEID.
SCTP SCTP GTPv2-U GTPv1-U
header.

GTPv1-U identified through the

IANA registered port 2152.
SCTP provides a robust reliable
delivery mechanism to X2AP. UDP UDP

UDP provides a best effort

transport service to GTPv1-U.

IP IP IP IP
IP Addressing is used to route
X2AP messages between X2.
IP Addressing is used to route
X2 Control Plane X2 User Plane GTPv1-U messages between
eNB’s.

Question
List the main functions of the X2 Application Part in the space provided below.

MPI4003-01-01 © mpirical limited, 2009 25

 LTE Operation

X2 Procedure Example - X2 Handover (No S-GW Relocation)

S-GW
MME

UE eNB eNB
Source Target
Measurement Configuration IE

Measurement and
Reporting
Packet Data Transfer

Measurement Report

Message
Handover Request
Information Elements
Old eNB UE X2AP ID
Cause

Handover Preparation Phase

Target ID
GUMMEI (Globally Unique MME Identifier)
UE Context Information Handover Request Admission Control
MME UE S1AP ID Reserve Radio Resources.
UE Capabilities Establish RAB.
Security Context Allocate C-RNTI to scheduler.
UE Aggregate Maximum Bit Rate
E-RAB to be Setup List Admission Control
E-RAB ID
E-RAB QoS
Questions
GTP-TEID 1. What is the role of the UE X2AP ID’s in the X2AP
RRC Context Handover Request Ack messages?
UE History Information
Message
RRC Connection Reconfiguration Request Handover Request Acknowledge
Information Elements 2. Is a SN Status Transfer required whenever a
Old eNB UE X2AP ID handover is performed? If not, what factor decides
New eNB UE X2AP ID
this?
UL GTP-U Tunnel Endpoints
Detach from source Forward buffered and in-transit E-RABs Admitted List
eNB data to the target eNB Target eNB To Source eNB Transparent Container
3. What is the purpose of the Transparent
SN Status Transfer Container?
Message
SN Status Transfer
Information Elements
Old eNB UE X2AP ID
New eNB UE X2AP ID Forward User Data
E-RABs Subject to Transfer
E-RAB ID Downlink Packet Data Transfer
UL Count Value
DL Count Value
Downlink Packet Data Transfer
Downlink Packet Data Transfer

Handover Execution Phase

Uplink Packet Data Transfer

Handover Confirmed
Path Switch
Update User Plane Request Switch downlink
path to target eNB
Update User Plane Response

Packet Data Transfer

End Marker
Note
Message
End Marker End Markers are GTP-U messages
Context Release with no user data that are sent to
Information Elements Path Switch Ack indicate that the source will no longer
Old eNB UE X2AP ID be sending user data to the target .
New eNB UE X2AP ID
Context Release

26 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

EUTRAN to UTRAN Routing Area Update

SGSN
PDN
S-GW
GW
MME
HSS
UE eNB NodeB
GUTI
SGSN Resolves GUTI from P-TMSI and SGSN Address
UE changes to UTRAN/GERAN old RAI

Routing Area Update Request

Context Request

P-TMSI Context Response

Old RAI (Tracking Area)
UE Capabilities

Authentication
SGSN Address
TEIDs S-GW Address
Context Acknowledge RAT Type TEIDs
RAT Type

Modify Bearer Request

Modify Bearer Request
Possible Interaction with
Modify Bearer Response PCRF
Modify Bearer Response

PDN-GW Address
TEIDs
S-GW Address QoS & Charging Information
TEIDs
QoS & Charging Information

Update Location

Cancel Location

Cancel Location Ack

Insert Subscriber Data

Insert Subscriber Data Ack

Update Location Ack

Routing Area Update Accept

Routing Area Update Complete

MPI4003-01-01 © mpirical limited, 2009 27

 LTE Operation

EUTRAN to UTRAN Mobility

SGSN
S-GW PDN
RNC GW
MME
HSS
UE Source eNB

IMSI
Handover Initiation Tunnel and Address Information (MME & S-GW)
MME Context
Session Context
Handover Required Downlink Tunnel Information

Handover Preparation Phase

Forward Relocation Request
Target RNC ID.
Source to Target Transparent Container
Create Session Request
Employed if “one
Source to Target Transparent Container tunnel” not
Create PDP Context Response supported
Relocation Request

Relocation Request Acknowledge

Create PDP Context Request
Uplink Tunnel Information Employed if “one
Target to Source Transparent Container Create PDP Context Response tunnel” supported
Forward Relocation Response
Handover Command
Mobility from E-UTRA Command

Target to Source Transparent Container

UTRAN Access
Based on parameters in Target to Source Transparent Container

Handover Execution Phase

Handover to UTRAN Complete
Relocation Complete

Forward Relocation Complete

Forward Relocation Complete

Acknowledge Modify Bearer Request
Modify Bearer Request

Modify Bearer Response

Modify Bearer Response

Uplink and Downlink Data Flow

Routing Area Update Procedure

Clear Down E-UTRAN Radio

Resources

28 © mpirical limited, 2009 MPI4003-01-01

LTE Operation

LTE Specifications

Main E-UTRA Air Interface and E-UTRAN Specifications Other Related 3GPP Specifications (not a complete list)
TS 36.101 E-UTRA; UE radio transmission and reception 21.201 Technical Specifications and Reports relating to an EPS based 3GPP system
TS 36.104 E-UTRA; Base Station (BS) radio transmission and reception 22.278 Service requirements for the Evolved Packet System (EPS)
TS 36.106 E-UTRA; FDD repeater radio transmission and reception 23.806 Voice call continuity between Circuit Switched (CS) and IMS Study
TS 36.113 E-UTRA; Base Station (BS) and repeater Electro Magnetic Compatibility (EMC) 23.830 Architecture aspects of Home Node B (HNB) / Home enhanced Node B (HeNB)
TS 36.124 E-UTRA; Electromagnetic compatibility (EMC) requirements for mobile terminals and ancillary equipment
23.869 Support for IP based IMS Emergency calls over GPRS and EPS
TS 36.133 E-UTRA; Requirements for support of radio resource management
23.879 Study on Circuit Switched (CS) domain services over evolved Packet Switched
TS 36.141 E-UTRA; Base Station (BS) conformance testing
TS 36.143 E-UTRA; FDD Repeater conformance testing 23.882 3GPP system architecture evolution (SAE): Report on technical options
TS 36.201 E-UTRA; Long Term Evolution (LTE) physical layer; General description 23.891 Evaluation of LCS Control Plane Solutions for EPS
TS 36.211 E-UTRA; Physical channels and modulation 24.206 Voice call continuity between Circuit Switched (CS) and IMS; Stage 3
TS 36.212 E-UTRA; Multiplexing and channel coding 24.301 Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3
TS 36.213 E-UTRA; Physical layer procedures 24.801 3GPP System Architecture Evolution (SAE); CT WG1 aspects
TS 36.214 E-UTRA; Physical layer - Measurements 24.879 Combining Circuit-Switched (CS) calls and IP Multimedia Subsystem (IMS) sessions
TS 36.300 E-UTRA and E-UTRAN; Overall description; Stage 2 29.272 EPS; Mobility Management Entity (MME) and SGSN related interfaces
TS 36.302 E-UTRA; Services provided by the physical layer
29.273 Evolved Packet System (EPS); 3GPP EPS AAA interfaces
TS 36.304 E-UTRA; UE procedures in idle mode
29.274 EPS; Evolved GPRS Tunnelling Protocol for Control plane (GTPv2-C); Stage 3
TS 36.305 E-UTRAN; Stage 2 functional specification of UE positioning in E-UTRAN
TS 36.306 E-UTRA; UE radio access capabilities 29.276 Optimized Handover Procedures between EUTRAN and cdma2000 HRPD Access
TS 36.314 E-UTRAN; Layer 2 - Measurements 29.277 Optimized Handover Procedures between EUTRAN Access and 1xRTT Access
TS 36.321 E-UTRA; Medium Access Control (MAC) protocol specification 29.280 EPS; 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC
TS 36.322 E-UTRA; Radio Link Control (RLC) protocol specification
TS 36.323 E-UTRA; Packet Data Convergence Protocol (PDCP) specification
TS 36.331 E-UTRA; Radio Resource Control (RRC); Protocol specification
TS 36.401 E-UTRAN; Architecture description
TS 36.410 E-UTRAN; S1 layer 1 general aspects and principles
TS 36.411 E-UTRAN; S1 layer 1
TS 36.412 E-UTRAN; S1 signalling transport
TS 36.413 E-UTRAN; S1 Application Protocol (S1AP)
TS 36.414 E-UTRAN; S1 data transport
TS 36.420 E-UTRAN; X2 general aspects and principles
TS 36.421 E-UTRAN; X2 layer 1
TS 36.422 E-UTRAN; X2 signalling transport
TS 36.423 E-UTRAN; X2 Application Protocol (X2AP)
TS 36.424 E-UTRAN; X2 data transport
TS 36.440 E-UTRAN; General aspects and principles for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN
TS 36.441 E-UTRAN; Layer 1 for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN
TS 36.442 E-UTRAN; Signalling Transport for interfaces supporting Multimedia Broadcast Multicast Service (MBMS) within E-UTRAN
TS 36.443 E-UTRAN; M2 Application Protocol (M2AP)
TS 36.444 E-UTRAN; M3 Application Protocol (M3AP)
TS 36.445 E-UTRAN; M1 Data Transport
TS 36.446 E-UTRAN; M1 User Plane protocol
TS 36.508 E-UTRA and EPC; Common test environments for UE conformance testing
TS 36.509 E-UTRA and EPC; Special conformance testing functions for UE
TS 36.521-1 E-UTRA; UE conformance specification; Radio transmission and reception; Part 1: Conformance testing
TS 36.521-2 E-UTRA; UE conformance specification; Radio transmission and reception; Part 2: Implementation Conformance Statement (ICS)
TS 36.521-3 E-UTRA; UE conformance specification; Radio transmission and reception; Part 3: Radio Resource Management (RRM) conformance testing
TS 36.523-1 E-UTRA and EPC; UE conformance specification; Part 1: Protocol conformance specification
TS 36.523-2 E-UTRA and EPC; UE conformance specification; Part 2: ICS
TS 36.523-3 E-UTRA and EPC; UE conformance specification; Part 3: Test suites
TR 36.800 Universal Terrestrial Radio Access (UTRA) and E-UTRA; Extended UMTS / LTE 800 Work Item Technical Report
TR 36.801 E-UTRA; Measurement Requirements
TR 36.803 E-UTRA; UE radio transmission and reception
TR 36.804 E-UTRA; Base Station (BS) radio transmission and reception
TR 36.805 E-UTRA; Study on minimization of drive-tests in next generation networks
TR 36.814 E-UTRA; Further advancements for E-UTRA Physical layer aspects
TR 36.902 E-UTRAN; Self-configuring and self-optimizing network (SON) use cases and solutions
TR 36.903 E-UTRA; Derivation of test tolerances for multi-cell Radio Resource Management (RRM) conformance tests
TR 36.912 Feasibility study for Further Advancements for E-UTRA (LTE-Advanced)
TR 36.913 Requirements for further advancements for E-UTRA (LTE-Advanced)
TR 36.938 E-UTRAN; Improved network controlled mobility between E-UTRAN and 3GPP2/mobile WiMAX radio technologies
TR 36.942 E-UTRA; Radio Frequency (RF) system scenarios
TR 36.956 E-UTRA; Repeater planning guidelines and system analysis

MPI4003-01-01 © mpirical limited, 2009 29

 LTE Operation

30 © mpirical limited, 2009 MPI4003-01-01