LTE E2e Part 1

LTE End to End System Part 1 - Procedures
Introduction
Mobility Management in
ECM-IDLE State
Connection
Management
ECM-CONNECTED State
End-to-End Example
Welcome to the e-learning course LTE

End to End System Part 1 - Procedures
This course provides an overview of the 3GPP Long
Term Evolution / Service Architecture Evolution
(LTE/SAE) end-to-end system, with a special emphasis
on mobility management and connection management
procedures, and taking into account Nokia Siemens
Networks -specific technical solutions.
We recommend reserving at least one hour for studying
the material.
1/1
Legal notice
Audio on/off
Speech script
Content map
Speech script
Welcome
Welcome
Page info
Welcome page
Copyright Nokia Siemens Networks 2007
Text.
Print
Abbreviations
Exit
Page 1
Introduction
1
1b
ECM-IDLE State
GERAN
Connection
Management
UTRAN
Gb
HSS
SGSN
3GPP
PS Core
Iu
S6a
2
S4
ECM-CONNECTED State
Evolved
UTRAN
eNB
End-to-End Example
S3
Examine
Examine the
the items
items with
with
your
your mouse
mouse pointer
pointer
MME
SAE
LTE
radio
interface
S5
S-GW
SGi
P-GW
eNB
1/1
Legal notice
4
5
S1-U
X2
Evolved
Packet
Core
S1-MME
S1-MME
Packet
Packet (IP)
(IP) traffic
traffic only
only
S11
LTE
Print
Abbreviations
Exit
Speech script
LTE / SAE Architecture
Welcome
Audio on/off
Speech script
Content map
Packet
Data
Network
UTRAN Long Term Evolution (LTE) refers to

the long term evolution of the 3GPP radio
access technology and is considered the
successor of the current UMTS system with
the rollout anticipated to begin with trials in
2009.
The LTE work in 3GPP is closely aligned to
the 3GPP system architecture evolution
(SAE) framework which is concerned with the
evolved core network architecture. The
LTE/SAE framework defines the flat, scalable,
IP-based architecture of the Evolved Packet
System (EPS) consisting of a radio access
network part (Evolved UTRAN) and the
Evolved Packet Core (EPC).
Note that the Evolved Packet System is
purely packet based. Voice transport is thus
based on Voice over IP (VoIP) technology.
Circuit-switched (CS) voice traffic is
supported by either using the CS fallback
(CSFB) or the single radio voice call
continuity (SR-VCC) interworking solution.
Move your mouse pointer over the items in
the architecture figure for a short introduction
to each item.
Page info
1. Show figure and add or highlight LTE label. 1b. Show dashed blue border line for a short time.
2. Add or highlight SAE label.
3. Highlight Evolved UTRAN. 4. Highlight Evolved Packet Core.
5. Add green text box.
6. Mouseover text on following slides.
Same page as in LTE radio

interface course, but icons have
changed (and small part of text
has changed)
Audio on/off
Speech script
Content map
Speech script
Welcome
Print
Abbreviations
Exit
Introduction
ECM-IDLE State
GERAN
Connection
Management
UTRAN
Gb
HSS
SGSN
Iu
S6a
S4
ECM-CONNECTED State
MME
Evolved
Packet
Core
eNB
S1-MME
X2
LTE
radio
interface
Page info
S3
Evolved
UTRAN
End-to-End Example
1/1
3GPP
PS Core
S11
S1-U
S5
S-GW
SGi
P-GW
eNB
The
The evolved
evolved Node
Node B
B (eNodeB,
(eNodeB, eNB)
eNB) supports
supports the
the LTE
LTE radio
radio
interface
interface and
and provides
provides the
the packet-switched
packet-switched functionality
functionality of
of aa
traditional
Legal
network
notice controller
|
Copyright
(RNC).
Nokia
aa result,
Siemens
the
traditional radio
radio
network
controller
(RNC).As
As
result,
theNetworks 2007
Evolved
Evolved UTRAN
UTRAN does
does not
not require
require aa separate
separate RNC
RNC network
network
element,
element, in
in other
other words
words the
the architecture
architecture is
is flat
flat
(architecture
(architecture contains
contains fewer
fewer types
types of
of network
network entities
entities and
and
interfaces).
interfaces).
The
The Mobility
Mobility Management
Management Entity
Entity (MME)
(MME) provides
provides
the
the basic
basic control
control plane
plane functionality
functionality in
in the
the Evolved
Evolved
Packet
Packet Core
Core network.
network. Note
Note that
that user
user plane
plane traffic
traffic
does
does not
not go
go through
through the
the MME.
MME.
The
The Serving
Serving Gateway
Gateway (S-GW)
(S-GW) and
and PDN
PDN Gateway
Gateway
(P-GW)
(P-GW) provide
provide the
the user
user plane
plane connectivity
connectivity
between
between the
the access
access network
network and
and the
the external
external
packet
packet data
data network
network (PDN).
(PDN). In
In the
the Nokia
Nokia Siemens
Siemens
Networks
Networks LTE
LTE solution,
solution, itit is
is possible
possible to
to implement
implement
these
these functional
functional entities
entities within
within aa single
single node.
node.
Packet
Data
Network
Use standardised
icons as on first slide
Audio on/off
Speech script
Content map
Welcome
Speech script

The
The S4
S4 interface
interface between
between the
the S-GW
S-GW and
and
SGSN
SGSN provides
provides aa GTP
GTP tunnel
tunnel for
for the
the user
user
plane
plane during
during an
an inter-system
inter-system handover.
handover.
Introduction
The
The S1-MME
S1-MME interface
interface carries
carries control
control plane
plane
signalling
signalling information
information between
between the
the eNB
eNB and
and
Mobility
Management
Entity.
Mobility
Management
Mobility
Managementin
Entity.
GERAN
Gb
ECM-IDLE State
HSS
SGSN
3GPP
PS Core
The
The S1-U
S1-U interface
interface between
between the
the eNB
eNB and
and
Connection
Serving
Serving Gateway
Gateway carries
carries the
the user
user plane
plane data
data
UTRAN
over
Management
over aa so-called
so-called GTP
GTP tunnel.
tunnel.
Iu
S6a
S4
ECM-CONNECTED State
S3
Evolved
Packet
Core
eNB
S1-MME
X2
LTE
radio
interface
S11
S1-U
S5
S-GW
The
The S6a
S6a interface
interface is
is used
used for
for transferring
transferring
subscription
subscription and
and authentication
authentication data
data between
between
the
the Home
Home Subscriber
Subscriber Server
Server (HSS)
(HSS) and
and MME.
MME.
The
The S3
S3 interface
interface carries
carries signalling
signalling between
between the
the
MME
MME and
and Serving
Serving GPRS
GPRS Support
Support Node
Node
(SGSN)
(SGSN) located
located in
in aa 2G/3G
2G/3G packet-switched
packet-switched
core
core network.
network.
MME
Evolved
UTRAN
End-to-End Example
Print
Abbreviations
Exit
The
The S11
S11 interface
interface carries
carries signalling
signalling messages
messages
between
between the
the Serving
Serving Gateway
Gateway and
and the
the Mobility
Mobility
Management
Management Entity.
Entity.
SGi
P-GW
eNB
The
The
The1LTE
LTE
radio interface
interface (air
(air interface,
interface, LTE-Uu)
LTE-Uu)
The X2
X2 interface
interface between
between two
two
/ 1 radio
is
eNB
is between
between the
the user
user equipment
equipment (UE)
(UE) and
and the
the
eNB network
network elements
elements is
is used
used
eNB.
Legal notice
|
Copyright during
Nokia Siemens
an
Networks
handover.
2007
eNB.
during
an inter-eNB
inter-eNB
handover.
Packet
Data
Network
The
The SGi
SGi interface
interface is
is between
between the
the PDN
PDN
Gateway
Gateway and
and the
the packet
packet data
data network
network (PDN).
(PDN).
The
The packet
packet data
data network
network may
may be
be an
an operatoroperatorexternal
external public
public or
or private
private IP
IP network,
network, or
or an
an IP
IP
network
network belonging
belonging to
to the
the operator,
operator, for
for instance
instance
providing
providing IP
IP Multimedia
Multimedia Subsystem
Subsystem (IMS)
(IMS)
services.
services. Legacy
Legacy Gn/Gp
Gn/Gp interface
interface connectivity
connectivity
to
to the
the EPS
EPS is
is also
also supported.
supported.
Page info
Mouseover action when mouse pointer is located over interface name. Text box appears and corresponding interface (line) is
highlighted.
Same as first page in LTE radio interface course, but blue text has changed.
Use standardised
icons as on first slide
Page 2
Introduction
ECM-IDLE State
SGSN
HSPA
HSPA
3GPP
3GPP R6
R6
Connection
Management
Packet
core
ECM-CONNECTED State
End-to-End Example
UE
BTS
RNC
GGSN
6
Control plane
User plane
7
1/1
Legal notice
Page info
1. Show figure above.
2. Highlight user plane and control plane connections (BTS-RNC-SGSN-GGSN) in the figure.
3. Highlight UE-BTS interface.
Print
Abbreviations
Exit
Speech script
Evolution towards Flat Network Architecture
Welcome
Audio on/off
Speech script
Content map
Closely associated with LTE is the evolution

towards a flat network architecture.
In a traditional 3GPP network both the user
plane data and control plane signalling is
carried between the UE and GGSN via the
BTS, RNC and SGSN. The high-speed
packet access (HSPA) solution in 3GPP
release 6 provides greatly increased radio
access capacity when compared to earlier
solutions.
As a next step in the network architecture
evolution, 3GPP release 7 offers the
possibility of implementing a direct GTP
tunnel for carrying user data between the
RNC and GGSN. The control plane signalling
still takes place via the SGSN.
The basic idea of the Internet HSPA (I-HSPA)
solution is to integrate the RNC packet
switched functionality into the base stations.
At the same time, the GTP tunnel for the user
plane traffic is extended to the I-HSPA
adapter in the BTS. The direct tunnel solution
offers high bitrates in a very cost efficient
manner and reduces the round trip time
(RTT) in the user plane.
The LTE network architecture is similar to the
I-HSPA architecture, although the
functionality and names of the network
elements have changed. Also, the LTE radio
interface provides greatly increased radio
access capacity when compared to HSPA.
Audio on/off
Speech script
Content map
Speech script
Welcome
Print
Abbreviations
Exit

Introduction
ECM-IDLE State

solutions.
SGSN
HSPA
HSPA
3GPP
3GPP R7
R7
Connection
Management
Packet
core
ECM-CONNECTED State
End-to-End Example
UE
BTS
RNC
Direct
Direct tunnel
tunnel for
for
user
user plane
plane traffic
traffic
GGSN
Control plane
User plane
1/1
Legal notice
Page info
4. Change label, make changes to figure and add callout.
5. Highlight control plane connection RNC-SGSN-GGSN.

Audio on/off
Speech script
Content map
Speech script
Welcome
Print
Abbreviations
Exit

Introduction
ECM-IDLE State

solutions.
SGSN
I-HSPA
I-HSPA
3GPP
3GPP R7
R7
Connection
Management
Packet
core
ECM-CONNECTED State
End-to-End Example
UE
BTS with I-HSPA adapter
High-capacity
High-capacity
direct
direct tunnel
tunnel
Packet
Packet functionality
functionality of
of
RNC
RNC integrated
integrated into
into BTS
BTS

GGSN
6
Control plane
User plane
7
1/1
Legal notice
Page info
6. Change label, make changes to figure and add yellow callout.
7. Highlight user plane connection BTS-GGSN and add blue callout.

Audio on/off
Speech script
Content map
Speech script
Welcome
Print
Abbreviations
Exit

Introduction
ECM-IDLE State

solutions.
MME / SGSN
LTE
LTE
3GPP
3GPP R8
R8
Connection
Management
Evolved
packet
core
ECM-CONNECTED State

End-to-End Example
UE
eNB
LTE
LTE radio
radio interface
interface brings
brings
great
great capacity
capacity increase
increase
S-GW / P-GW
GGSN

Control plane
User plane
1/1
Legal notice
Page info
8. Change label, make changes to figure and shortly highlight one by one eNB, MME and S-GW/P-GW icons.
9.

Page 3
Introduction
ECM-IDLE State
1
EPS
EPS bearer
bearer termination
termination in
in P-GW
P-GW
What is PMIP?
EPS
EPS bearer
bearer termination
termination in
in S-GW
S-GW
Show
Show
Connection
Management
E-UTRAN
EPC
Internet
ECM-CONNECTED State
UE
eNB
S-GW
Peer entity
P-GW
End-to-End Example
End-to-end service
EPS bearer
Radio bearer
Radio interface
S1 bearer
S1
S5/S8 bearer
S5/S8
SGi
5
1/1
Legal notice
Page info
1. Show figure above without title label highlighting.
2. Highlight upper title label.
Print
Abbreviations
Exit
Speech script
EPS Bearer
Welcome
Audio on/off
Speech script
Content map
In the Evolved Packet System (EPS), socalled EPS bearers are employed for carrying
the user data between the UE and the PDN
Gateway, or between the UE and the Serving
Gateway.
In the first option, the EPS bearer consists of
a radio bearer, an S1 bearer and an S5/S8
bearer. Between the eNodeB and PDN
Gateway, the transport of the user data takes
place within a GPRS Tunnelling Protocol
(GTP) tunnel.
In the second option, the EPS bearer and
associated GTP tunnel extends to the Serving
Gateway only. Over the S5/S8 interface the
IETF Proxy Mobile IP (PMIP) solution is used
instead for carrying the user data traffic.
Each EPS bearer is associated with a certain
Quality of Service (QoS) profile. Thus,
different packet flows with different QoS
requirements will be associated with different
EPS bearers, and the network can prioritise
packets accordingly.
When a UE connects to a packet data
network (PDN), one EPS bearer is
permanently established for the lifetime of the
PDN connection to provide always-on IP
connectivity with that PDN. This bearer is
referred to as the default bearer. Additional
dedicated EPS bearers may or may not be
allocated for the transport of user data.
The QoS concept will be explained in more
detail in Part 2 of the LTE End to End System
course.
Audio on/off
Speech script
Content map
Speech script
EPS Bearer
Welcome
Gateway.
Introduction
ECM-IDLE State
EPS
EPS bearer
bearer termination
termination in
in P-GW
P-GW
What is PMIP?
EPS
EPS bearer
bearer termination
termination in
in S-GW
S-GW
Show
Show
Connection
Management
E-UTRAN
EPC

(GTP) tunnel.
Internet
ECM-CONNECTED State
UE
eNB
S-GW
Peer entity
P-GW
End-to-End Example
End-to-end service
EPS bearer
Radio bearer
Radio interface
S1 bearer
S1
PMIP
S5/S8
1/1
Legal notice
Print
Abbreviations
Exit
SGi
Change
Page info
3. Change to figure shown above. Note also change of title label highlighting. Activate tutor animation.

course.
Audio on/off
Speech script
Content map
Speech script
EPS Bearer
Welcome
Gateway.
Introduction
ECM-IDLE State
EPS
EPS bearer
bearer termination
termination in
in P-GW
P-GW
What is PMIP?
EPS
EPS bearer
bearer termination
termination in
in S-GW
S-GW
Show
Show
Connection
Management
E-UTRAN
EPC

(GTP) tunnel.
Internet
ECM-CONNECTED State
UE
eNB
S-GW
P-GW

Peer entity
End-to-End Example
End-to-end service
EPS bearer
EPS bearer for VoIP traffic

EPS bearer for non-realtime (NRT) traffic
EPS bearer
EPS bearer
etc.
1/1
Legal notice
Print
Abbreviations
Exit
Page info
4. Change back to first figure with upper title label highlighted. Start with one EPS bearer with callout and gradually add two
more bearers with their callouts.

course.
Audio on/off
Speech script
Content map
Speech script
EPS Bearer
Welcome
Gateway.
Introduction
ECM-IDLE State
EPS
EPS bearer
bearer termination
termination in
in P-GW
P-GW
What is PMIP?
EPS
EPS bearer
bearer termination
termination in
in S-GW
S-GW
Show
Show
Connection
Management
E-UTRAN
EPC

(GTP) tunnel.
Internet
ECM-CONNECTED State
UE
eNB
S-GW
P-GW

Peer entity
End-to-End Example
End-to-end service
Default EPS bearer
Dedicated EPS bearer

QoS
QoS in
in LTE:
LTE:
See
See Part
Part 22 of
of LTE
LTE End
End
to
to End
End System
System course
course
:
5
1/1
Legal notice
Print
Abbreviations
Exit
Page info
5. Show now only one EPS bearer. When mentioned, change text on bearer to Default EPS bearer.
6. Add one or more bearers with text Dedicated EPS bearer.
7. Add yellow label.

course.
Speech script
EPS Bearer
Welcome
Introduction
What is Proxy Mobile IP (PMIP)?
ECM-IDLE State
PMIP is an IETF solution under development

that provides similar functionality to that of
Mobile IP (see RFC 3344).
Connection
Management
Unlike Mobile IP, PMIP does not require any

modifications to the protocol stack in the
mobile terminal, in other words the mobility is
taken care of completely by the network. This
also means that PMIP can be used for
localised mobility management - without any
involvement of the mobile terminal - as in the
EPC transport case.
ECM-CONNECTED State
End-to-End Example
Ok
Ok
1/1
Legal notice
Audio on/off
Speech script
Content map
Page info
5. Show now only one EPS bearer. When mentioned, change text on bearer to Default EPS bearer.
6. Add one or more bearers with text Dedicated EPS bearer.
7. Add yellow label.
Print
Abbreviations
Exit
Page 4
Introduction
ECM-IDLE State
1
UE
UE is
is not
not reachable
reachable
Connection
Management
ECM-CONNECTED State
EMM-DEREGISTERED
Attach (or tracking area update

from GERAN/UTRAN)
RRC
RRC connection
connection ++
S1-MME
S1-MME connection
connection
In the EMM-DEREGISTERED state, the MME

holds no valid location information for the UE.
The UE is not reachable, since its location is
not known.
The UE enters the EMM-REGISTERED state

either due to the LTE attach procedure or due
to a tracking area update (TAU) from a 2G
(GERAN) or 3G (UTRAN) network. In this
state, the UE can be reached by paging.
EMM-REGISTERED
ECM-CONNECTED
Signalling connection
released
Signalling connection
established
4
EMM-REGISTERED
ECM-IDLE
The two EPS Connection Management

(ECM) states, ECM-IDLE and ECMCONNECTED, describe the signalling
connectivity between the UE and Evolved
Packet Core.
Change
1/1
Legal notice
In the ECM-IDLE state, there exists no

signalling connection between the UE and the
MME.
In the ECM-CONNECTED state, there exists

a signalling connection between the UE and
the MME. The signalling connection is made
up of two parts: an RRC connection between
the UE and eNodeB, and an S1-MME
connection between eNodeB and MME.
Page info
1. Show figure without highlighting and text boxes.
2. Highlight EMM-DEREGISTERED and add upper yellow box.
3. Highlight EMM REGISTERED in lower two bubbles. 4. Add lower yellow box.
5. Highlight ECM-IDLE. 6. Highlight ECM-CONNECTED. 7. Add blue box.
There are two sets of states defined for each

UE based on the information held by the
Mobility Management Entity.
The two EPS Mobility Management (EMM)
states, EMM-DEREGISTERED and EMMREGISTERED, describe whether or not the
UE is registered in the MME and can be
reached by paging.
Detach
End-to-End Example
UE
UE can
can be
be reached
reached
by
by paging
paging
Print
Abbreviations
Exit
Speech script
EMM and ECM States
Welcome
Audio on/off
Speech script
Content map
Page 5
Introduction
2
ECM-IDLE State
LTE End to End System Part 1

2
EMM-DEREGISTERED
Connection
Management
3
4
EMM-REGISTERED
ECM-CONNECTED
ECM-CONNECTED State
EMM-REGISTERED
ECM-IDLE
End-to-End Example
5
6
LTE End to End System Part 2

QoS solutions
Security solutions
Charging solutions
User plane transport
LTE - 2G/3G/CDMA2000 interoperability
Radio network and frequency planning
Licensing issues
Network management
Subscription data management
Operator services
1/1
Legal notice
Page info
1. Show some nice background picture and the upper part of the figure.
2. Highlight bottom state bubble and third item in content list.
3. Highlight middle state bubble and fourth item in content list.
4. Highlight middle state bubble and fifth item in content list.
5. Highlight last item in content list.
6. Show lower part of the figure. Highlight bulleted items when mentioned.
Print
Abbreviations
Exit
Speech script
LTE End-to-End Procedures and Technology
Welcome
Audio on/off
Speech script
Content map
In this course, we will next examine various

procedures required for managing the end-toend LTE system.
The procedures include mobility management
procedures in the ECM-IDLE state,
connection management procedures, and
mobility management procedures in the
ECM-CONNECTED state, also known as
handovers. A small end-to-end example is
provided at the end of the course.
In LTE End to End System Part 2, we will then
turn our attention to various supporting
technologies and solutions needed for
achieving a complete functioning end-to-end
system. Topics in the course include:
Quality of Service (QoS) solutions, closely
related to the EPS bearer concept
Security solutions such as authentication
and encryption of user and control data
Charging solutions
User plane transport options
Interoperability between LTE and 2G/3G or
3GPP2 systems
Radio network planning, frequency planning
and licensing issues
Network management
Subscription data management
Operator services.
Page 6
Introduction
ECM-IDLE State
EMM-DEREGISTERED
MM procedures in
ECM-IDLE state:
Tracking
Tracking area
area update
update
Paging
Paging
Connection
Management
EMM-REGISTERED
ECM-CONNECTED
MM procedures in ECMCONNECTED state:
ECM-CONNECTED State
EMM-REGISTERED
ECM-IDLE
Handovers
Handovers
End-to-End Example
1/1
Legal notice
Print
Abbreviations
Exit
Speech script
Introduction
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show figure without highlighting. Show also some nice background picture since figure is quite dull.
2. Highlight bottom state bubble and first bulleted item in blue box.
3. Highlight bottom state bubble and second bulleted item.
4. Highlight middle state bubble and bulleted item in green box. Stop highlighting at the end.
Mobility management (MM) functions are

needed for keeping track of the current
location of a UE.
The basic mobility management procedures
in ECM-IDLE state are
tracking area update, needed when the
mobile terminal moves to a tracking area in
which it is not registered
paging, where the network indicates to the
mobile terminal that it should enter the ECMCONNECTED state.
These mobility management procedures will
be described on the following pages. Note
that mobility management procedures in the
ECM-CONNECTED state - usually refered to
as handovers - will be explained later in the
course.
Page 7
Introduction
ECM-IDLE State
TA2
TAU
TAU required!
required!
TA1
Connection
Management
TA3
3
ECM-CONNECTED State
Registered in TA1 - can be reached in TA1
Registered in TA2 - can be reached in TA2
Not registered in TA3 - cannot be reached in TA3
End-to-End Example
My ID in ECM-IDLE
state is S-TMSI
S-TMSI is used during paging

(and when responding to paging)
1/1
Legal notice
Print
Abbreviations
Exit
Speech script
Tracking Area
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show upper part of figure (without UE and without yellow label). 2. Add labels TA1, TA2 and TA3 to cell figure.
3. Show picture of UE (in cell figure and below cell figure) and add bulleted items one by one.
4. Add S-TMSI callout. 5. Add text next to this callout.
6. UE in cell figure slowly moves from TA1 via TA2 to TA3. When arriving in TA3, yellow label is shown.
If the network wishes to communicate with a

UE that is in the ECM-IDLE state, it needs to
have some information about where the UE is
located. This is handled using the tracking
area concept. Each cell belongs to a single
tracking area (TA). Note, however, that
different cells in a certain eNodeB can belong
to different tracking areas.
A UE in ECM-IDLE state can be reached in
those cells that belong to the tracking area in
which the UE is currently registered. The UE
may be registered in multiple tracking areas.
The MME allocates the UE a Temporary
Mobile Subscriber Identity (S-TMSI) which
uniquely identifies the UE within a given
tracking area. Thus, when a UE is in the
ECM-IDLE state, the MME can request within
one or more tracking areas that the UE with
the required S-TMSI switch to the ECMCONNECTED state. This MME request is
done by paging.
When the UE moves to a tracking area in
which it is not registered, a tracking area
update (TAU) must be performed to ensure
that it can be reached in the new tracking
area.
Note that the UE may also perform tracking
area updates on a periodical basis.
Page 8
Introduction
ECM-IDLE State
UE
eNB
MME
S-GW
Connection
Management
2
1
ECM-CONNECTED State
End-to-End Example
3
Incoming downlink
user data
5
6
5
Random Access
Procedure
Investigate the figure

with your mouse pointer
1/1
7
Legal notice
Print
Abbreviations
Exit
Speech script
Paging
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show figure without highlighting and callout. 2. Add callout. 3. Highlight arrow/button 1.
4. Highlight arrow/button 2. 5. Highlight arrow/button 3. 6. Highlight arrow/button 5.
7. Highlight Random Access Procedure.
8. Show now text Investigate.... Activate mouseover operation shown on next slide.
When a mobile terminal is in the ECM-IDLE

state, it can only be reached through paging.
The UE is paged in all cells of all tracking
areas in which it is currently registered. Note
that the UE may be registered in multiple
tracking areas.
There are a number of reasons why the
network needs to initiate contact. Most likely,
dowlink user data has arrived at the S-GW, in
which case the S-GW requests the MME to
page the UE to which the data should be
sent.
The MME sends a paging message to every
eNodeB in every tracking area in which the
UE is registered.
The eNodeB then initiates a two-stage paging
process. First, it indicates the paging group
by broadcasting a paging indication
message. UEs are allocated to paging groups
based on the UE identifier (IMSI or S-TMSI).
If a UE discovers that its group is being
paged, only then the UE reads the full paging
message.
When the UE detects that it is being paged, it
initiates the transition from the ECM-IDLE to
ECM-CONNECTED state. This always
involves the random access procedure.
You can see more details by moving your
mouse pointer over the items in the
procedure sequence chart.
Audio on/off
Speech script
Content map
Change Downlink
Paging
Welcome
Introduction
Speech script
ECM-IDLE State
UE
eNB
MME
S-GW
Connection
Management
1
ECM-CONNECTED State
End-to-End Example
6
Random Access
Procedure
:
1/1
Legal notice
8. Mouseover operation as shown.
Downlink
Downlink user
user data
data has
has arrived
arrived at
at the
the SSGW,
GW, and
and the
the MME
MME is
is requested
requested to
to page
page the
the
UE.
UE. The
The S-GW
S-GW will
will have
have received
received the
the
identity
identity and
and address
address of
of the
the serving
serving MME
MME
during
during the
the initial
initial attach
attach procedure.
procedure. This
This
information
information is
is stored
stored locally
locally at
at the
the S-GW,
S-GW,
and
and updated
updated during
during MME
MME relocation.
relocation.
The
The MME
MME sends
sends an
an S1AP
S1AP Paging
Paging Request
Request
message
message to
to every
every eNB
eNB in
in every
every tracking
tracking
area
area in
in which
which the
the UE
UE is
is registered.
registered.
Page info
Print
Abbreviations
Exit

The
The random
random access
access procedure
procedure is
is necessary
necessary
for
for establishing
establishing an
an RRC
RRC connection
connection
between
between UE
UE and
and eNB.
eNB. The
The signalling
signalling
continues...
Copyright Nokia Siemens
Networks 2007
continues...
The
The eNB
eNB broadcasts
broadcasts aa paging
paging indication
indication
message,
message, which
which includes
includes information
information about
about
how
how the
the paging
paging message
message can
can be
be read
read and
and
what
what physical
physical resources
resources have
have been
been
allocated
allocated for
for it.
it. The
The paging
paging indication
indication is
is
repeated
repeated until
until the
the UE
UE responds
responds or
or until
until the
the
number
number of
of re-tries
re-tries reaches
reaches aa maximum.
maximum.
The
The UE
UE reads
reads the
the paging
paging indication
indication
message
message and
and notices
notices that
that itit belongs
belongs to
to the
the
paging
paging group
group indicated
indicated in
in the
the message.
message.
The
The eNB
eNB broadcasts
broadcasts the
the paging
paging message
message
using
using the
the physical
physical resources
resources listed
listed in
in the
the
paging
paging indication
indication message.
message.
Since
Since the
the UE
UE belongs
belongs to
to the
the paging
paging group,
group, itit
reads
reads the
the full
full paging
paging message.
message. IfIf the
the UE
UE
detects
detects its
its own
own identifier
identifier (S-TMSI
(S-TMSI or
or IMSI)
IMSI) in
in
the
the paging
paging message,
message, itit knows
knows that
that itit is
is being
being
paged
paged and
and in
in this
this case
case starts
starts to
to establish
establish aa
signalling
signalling connection
connection to
to the
the MME.
MME.
Page 9
Introduction
ECM-IDLE State
UE
Connection
Management
ECM-CONNECTED State
eNB
MME
End-to-End Example
HSS
Oops, I have moved to a

new tracking area in which I
am not registered!
Random Access
Procedure
Next, the UE sends a TAU Request message

to the MME.
1/1
Legal notice
Page info
1. Show figure without highlighting and callout.
2. Add callout.
4. Highlight arrows/buttons 2 and 3.
5. Highlight arrows/button 4.

which it is not registered, it must perform a
tracking area update (TAU) to ensure that it
can be reached in the new tracking area. The
UE discovers which tracking area it is in by
listening to the broadcast channel.
When a tracking area update is necessary,
first an RRC connection between the UE and
eNodeB must be established using the
random access procedure.
Print
Abbreviations
Exit
Speech script
Tracking Area Update
Welcome
Audio on/off
Speech script
Content map
The MME may perform authentication, if

necessary, and sends a TAU Accept message
to the UE. The message includes, among
others, a new list of tracking areas in which
the UE is now registered.
In a more general case, the tracking area
update includes a procedure called MME
relocation, involving a new MME handling the
new tracking area and the old MME which
handled the previous tracking area. MME
relocation includes signalling between the two
MMEs, between the new MME and HSS for
adding new information, and between the old
MME and HSS for deleting old information.
Actually, the Serving Gateway is also involved
in the procedure, but this is not shown in the
figure for the sake of simplicity.
Moving back to the less complex tracking area
update case, you can see more details by
moving your mouse pointer over the items in
the procedure sequence chart.
Audio on/off
Speech script
Content map
Speech script
Welcome

which it is not registered, it must perform a
tracking area update (TAU) to ensure that it
can be reached in the new tracking area. The
UE discovers which tracking area it is in by
listening to the broadcast channel.
Introduction
ECM-IDLE State
UE
Connection
Management
ECM-CONNECTED State
eNB
Print
Abbreviations
Exit
New MME
Old MME
HSS
When a tracking area update is necessary,

first an RRC connection between the UE and
eNodeB must be established using the
random access procedure.
Random Access
Procedure
End-to-End Example
Next, the UE sends a TAU Request message

to the MME, partly using the RRC connection.
necessary, and sends a TAU Accept message
to the UE. The message includes, among
others, a new list of tracking areas in which
the UE is now registered.
1/1
Legal notice
Page info
7. Slowly change figure as shown. Do not yet add blue arrows. Highlight New MME and Old MME when mentioned.
8. Add top, middle and bottom blue arrow when mentioned.
9. Return to original figure and activate mouseover operation shown on next slide. Show now text Investigate....
In a more general case, the tracking area

update includes a procedure called MME
relocation, involving a new MME handling the
new tracking area and the old MME which
handled the previous tracking area. MME
relocation includes signalling between the two
MMEs, between the new MME and HSS for
adding new information, and between the old
MME and HSS for deleting old information.
Actually, the Serving Gateway is also involved
in the procedure, but this is not shown in the
figure for the sake of simplicity.
Moving back to the less complex tracking area
update case, you can see more details by
moving your mouse pointer over the items in
the procedure sequence chart.
Audio on/off
Speech script
Content map
Speech script
Welcome
Introduction
ECM-IDLE State
UE
Connection
Management
ECM-CONNECTED State
eNB
MME
HSS
Random Access
Procedure
2

1/1
The
The eNB
eNB forwards
forwards the
the TAU
TAU Request
Request
message
message to
to the
the MME.
MME.
The
The MME
MME may
may perform
perform authentication
authentication based
based
on
on data
data obtained
obtained from
from the
the HSS.
HSS.
6
Legal notice
The
The UE
UE sends
sends aa TAU
TAU Request
Request message
message to
to
the
the eNB.
eNB. The
The message
message includes
includes (among
(among
others)
others) the
the last
last visited
visited TA,
TA, so
so that
that the
the MME
MME
can
can produce
produce aa good
good list
list of
of TAs
TAs to
to be
be sent
sent to
to
the
the UE.
UE. In
In other
other words,
words, the
the MME
MME can
can keep
keep
this
this TA
TA in
in the
the new
new TA
TA list,
list, thus
thus avoiding
avoiding
ping-pong-like
ping-pong-like TAU
TAU behaviour.
behaviour.
The
The UE
UE detects
detects aa change
change to
to aa new
new tracking
tracking
area
area (TA)
(TA) by
by discovering
discovering that
that the
the current
current TA
TA
indicated
indicated on
on the
the broadcast
broadcast channel
channel is
is not
not in
in
the
the list
list of
of TAs
TAs that
that the
the UE
UE registered
registered with
with the
the
network.
network.
The
The random
random access
access procedure
procedure is
is necessary
necessary
for
for establishing
establishing an
an RRC
RRC signalling
signalling
connection
connection between
between UE
UE and
and eNB.
eNB.
End-to-End Example
Page info
Print
Abbreviations
Exit
IfIf the
the MME
MME accepts
accepts the
the tracking
tracking area
area update
update
request,
request, itit sends
sends aa TAU
TAU Accept
Accept message
message to
to
the
the UE.
UE. The
The message
message includes
includes (among
(among
others)
others) aa new
new list
list of
of valid
valid tracking
tracking areas
areas for
for
the
the UE.
UE.
Page 10
Introduction
ECM-IDLE State
Connection
Management
ECM-CONNECTED State
End-to-End Example
Print
Abbreviations
Exit
Speech script
Exercise
Welcome
Audio on/off
Speech script
Content map
Please click the correct tick boxes in the table below with
your mouse pointer. When you are ready, click Submit.
Paging
In this exercise, the idea is to associate

various statements with the correct mobility
management procedure. Please go ahead.
TAU
Downlink user data has arrived at the SGW

Random access procedure is required as
part of this procedure
UE checks if it belongs to a certain group
The MME updates a certain list and
sends this new list to the UE
MME relocation can also be part of this
procedure
Submit
Submit
This is not the correct solution.

Please try again.
Show
Show correct
correct solution
solution
Change
Congratulations, this is the correct
solution!
1/1
Legal notice
Page info
After Submit is clicked, correct choices are left in the figure (yellow boxes) and wrong choices removed. After three trials
Show correct solution is displayed.
Page 11
Introduction
LTE attach provides:

Default EPS bearer
IP address for UE
ECM-IDLE State
1
EMM-DEREGISTERED
CM procedures:
Connection
Management
EMM-REGISTERED
ECM-CONNECTED
Random
Random access
access
LTE
LTE attach
attach // detach
detach
Transition
Transition between
between ECM-IDLE
ECM-IDLE
and
and ECM-CONNECTED
ECM-CONNECTED
ECM-CONNECTED State
EMM-REGISTERED
ECM-IDLE
End-to-End Example
Random
Random access
access
What about state
change delays?
Show
Show
UE
10
1/1
|
Page info
1. Show state bubble figure and add green text box.
2. Highlight upper left arrow in state bubble figure. 3. Add callout.
4. Highlight lower left arrow in state bubble figure. Then highlight lower state bubble.
5. Highlight lower right arrow in state bubble figure.
6-9. Add items to figure as shown (remove yellow box in step 8). 10. Highlight and keep highlighted middle state bubble.
11. Add or activate tutor animation.
If there is no data traffic activity for some time,

the connection management state is changed
to ECM-IDLE. Now the location of the UE is
known only at the tracking area level and the
UE can only be reached through paging.
In ECM-CONNECTED state, the location of

the UE is known at the cell level and cell
changes are controlled by handovers.
S-GW
LTE attach means that a mobile device moves

from the EMM-DEREGISTERED state to the
EMM-REGISTERED and ECM-CONNECTED
state. Note that during LTE attach a mobile
terminal is always allocated a bearer - in other
words the default EPS bearer - and an IP
address.
5
eNB
Now let us examine four connection

management procedures in more detail:
Random access, LTE attach, setting up a user
data connection, and releasing the connection.
When a UE changes back from the ECM-IDLE

to ECM-CONNECTED state, a Radio
Resource Control (RRC) signalling connection
is first established over the LTE air interface
using a procedure called random access, and
the MME establishes a signalling connection
over the S1 interface. Next, the MME creates
a user plane connection between the UE and
Serving Gateway (S-GW). Now the transport
of user data can take place.
MME
Legal notice
Print
Abbreviations
Exit
Speech script
Introduction
Welcome
Audio on/off
Speech script
Content map
11
Finally, our tutor would like to introduce some

performance requirements related to these
state changes.
Speech script
Introduction
Welcome
Introduction
ECM-IDLE State
What about state change delays?
Connection
Management
The average delay of the attach procedure shall not

be greater than 120 ms.
ECM-CONNECTED State
The average delay of the network triggered service

request procedure (including security handling) shall
not be greater than 120 ms.
End-to-End Example
The average delay of the UE triggered service

request procedure (including security handling) shall
Ok
Ok
1/1
Legal notice
Page info
Tutor mouseover animation.
Audio on/off
Speech script
Content map
Print
Abbreviations
Exit
Page 12
Introduction
Contention
Contention Based
Based Random
Random Access
ECM-IDLE State
Non-Contention
Non-Contention Based
Based Random
Random Access
Access
Connection
Management
UE
ECM-CONNECTED State
LTE attach
User data in uplink
User data in downlink (indicated by
paging)
Tracking area update
etc.
Random Access Preamble Assignment
eNB
Random Access Preamble
End-to-End Example
You can see more details by clicking the

random access method buttons. Then move
your mouse pointer over the text in the
Contention Resolution
Page info
1. Show figure without highlighting buttons or sequence items.
2. Highlight upper button and four lowest sequence items as shown. Add bulleted items when mentioned.
Contention based random access is used

when the UE starts the LTE attach procedure,
or when the UE is in ECM-IDLE state and
wishes to contact the network. This is
necessary for instance when there is user
data to be sent in uplink or in downlink which is indicated by paging the UE - or
during a tracking area update.
Non-contention based random access is
used in some special cases when the UE is in
the ECM-CONNECTED state, for instance
when there is data to be sent in the downlink
but the UE is not synchronised to the network
for some reason, or when the network
commands the UE to perform a handover to
another cell.
Scheduled Transmission
1/1
Every time the UE wishes to initiate

communication with the network, a procedure
called random access has to be performed.
Two random access procedures have been
defined for LTE:
3
Random Access Response
Legal notice
Print
Abbreviations
Exit
Speech script
Random Access
Welcome
Audio on/off
Speech script
Content map
Audio on/off
Speech script
Content map
Speech script
Random Access
Welcome
Introduction
Every time the UE wishes to initiate

communication with the network, a procedure
called random access has to be performed.
Two random access procedures have been
defined for LTE:
Contention
Contention Based
Based Random
Random Access
ECM-IDLE State
Non-Contention
Based Random
Random Access
Access
Contention based random access is used

when the UE starts the LTE attach procedure,
or when the UE is in ECM-IDLE state and
wishes to contact the network. This is
necessary for instance when there is user
data to be sent in uplink or in downlink which is indicated by paging the UE - or
during a tracking area update.
User data in downlink (UE is in ECMCONNECTED state but not synchronised)

Handover to another cell
Connection
Management
UE
ECM-CONNECTED State
eNB
End-to-End Example
Non-contention based random access is

used in some special cases when the UE is in
ECM-CONNECTED state, for instance when
there is data to be sent in the downlink but
the UE is not synchronised to the network for
some reason, or when the network
commands the UE to perform a handover to
another cell.
You can see more details by clicking either

random access method button. Then move
your mouse pointer over the text in the

1/1
Legal notice
Print
Abbreviations
Exit
Page info
3. Highlight lower button and three topmost sequence items as shown. Fade out previous bulleted items and add new bulleted
items when mentioned.
4. Mouseover operation described on following slides.
Audio on/off
Speech script
Content map
Speech script
Random Access
Welcome
Introduction
Print
Abbreviations
Exit
Contention
Contention Based
Based Random
Random Access
ECM-IDLE State
Non-Contention
Based Random
Random Access
Access
Connection
Management
UE
ECM-CONNECTED State
eNB
The UE randomly chooses one of 64 possible

random access preamble sequences and sends it
to the eNB. Transmission of the preamble is
restricted to certain time and frequency resources
that constitute the Physical Random Access
Channel (PRACH). A random access preamble
occupies a bandwidth of 72 subcarriers. Several
preamble formats have been defined.

End-to-End Example

The network responds to the preamble with a

message (typically Random Access Response)
containing:
the preamble itself
temporary identifier for UE (Temporary C-RNTI)
timing alignment information
uplink grant for sending an RRC message
1/1
Legal notice
Page info
Contention occurs if more than one UE transmits

the
same random
preamble
at the same
Copyright
Nokia Siemens
Networks
2007 time. The
contention is resolved by the eNB sending an RRC
message including the identity of the UE that won
the contention. This message is sent to all UEs that
received the Temporary C-RNTI in the random
access response message. The UE that won the
contention promotes the Temporary C-RNTI to CRNTI. The other UEs have to start the random
access procedure from the beginning.
The UE sends the RRC message (typically

Connection Request) to the eNB along with a UE
identity (usually S-TMSI), which is used to identify
the UE to the eNB for the purpose of contention
resolution.
Audio on/off
Speech script
Content map
Speech script
Random Access
Welcome
Introduction
Contention
Contention Based
Based Random
Random Access
ECM-IDLE State
Non-Contention
Based Random
Random Access
Access
Connection
Management
UE
ECM-CONNECTED State
eNB

1/1
Legal notice
The eNB transmits a message including a

dedicated preamble to the UE. In the case of a
handover to a new cell, the Cell Radio Network
Temporary Identifier (C-RNTI) to be used in this
cell is also included in the message.
End-to-End Example
Page info
Print
Abbreviations
Exit
The UE returns the dedicated preamble it

received from the eNB. Note that there is no
danger of contention now because only one UE
can use the dedicated preamble in a cell at a
given time.
The eNB responds to the preamble with a
message containing timing alignment information
and an uplink grant for sending an RRC message.
The random access procedure ends at this point
since:
(a) the UE already has obtained a valid C-RNTI
(b) there was no contention when the UE returned
the dedicated preamble (previous step).
Page 13
Introduction
ECM-IDLE State
UE
Connection
Management
eNB
MME
S-GW
P-GW
HSS
2
3
End-to-End Example
2
4

5
6
7
Default EPS bearer is created

4
1/1
5
Legal notice
The LTE attach procedure is used when the

UE is in the EMM-DEREGISTERED state and
wishes to enter the EMM-REGISTERED state,
in other words the UE wishes to register with
the EPC network, for instance after power-on.
This animation - in two parts - outlines the
main functionality of the attach procedure as
specified by 3GPP. You can see more details
by moving your mouse pointer over the items
in the procedure sequence chart at the end of
the animation.
Random Access
Procedure
ECM-CONNECTED State
Print
Abbreviations
Exit
Speech script
LTE Attach (1/2)
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show figure without highlighting.
3. Highlight arrows/buttons 1 and 2. 4. Highlight arrows/button 3. 5. Highlight arrows/buttons 4-7.
6. Highlight Default EPS bearer is created.
First, a procedure called random access is

necessary. The purpose of this procedure is to
establish a Radio Resource Control (RRC)
signalling connection between the UE and
eNodeB.
Using this RRC signalling connection, an
Attach Request message is sent to the
eNodeB. The message is then forwarded to
the MME.
The MME may perform authentication at this
stage, if required.
Next, the MME contacts the Home Subscriber
Server (HSS), which sends the users
subscription data to the MME. The MME can
now create a context for the UE.
In LTE, an integral part of the attach procedure
is to establish the default EPS bearer. In
effect, this means that the UE directly enters
the ECM-CONNECTED state - at leat
temporarily. This is explained on the next
page.
Audio on/off
Speech script
Content map
Speech script
LTE Attach (1/2)
Welcome
Introduction
The
The random
random access
access procedure
procedure is
is necessary
necessary
for
for establishing
establishing an
an RRC
RRC signalling
signalling
connection
connection between
between UE
UE and
and eNB.
eNB.
ECM-IDLE State
UE
Connection
Management
eNB
MME
S-GW
P-GW
Random Access
Procedure
ECM-CONNECTED State
HSS
2
3
End-to-End Example
3
4
5
6
7
Default EPS bearer is created
1/1
5
6
7
Legal notice
Page info
Print
Abbreviations
Exit
A
A Non
Non Access
Access Stratum
Stratum (NAS)
(NAS) Attach
Attach
Request
Request message
message is
is sent
sent to
to the
the eNB
eNB
encapsulated
encapsulated in
in an
an RRC
RRC message.
message.
The
The eNB
eNB chooses
chooses an
an MME
MME to
to serve
serve the
the UE
UE
and
and forwards
forwards the
the NAS
NAS Attach
Attach Request
Request
message
message to
to the
the MME
MME encapsulated
encapsulated in
in an
an
S1AP
S1AP Initial
Initial UE
UE Message.
Message.
IfIf there
there is
is no
no context
context for
for the
the UE
UE anywhere
anywhere in
in
the
the network
network then
then authentication
authentication must
must be
be
performed.
performed. The
The authentication
authentication is
is based
based on
on
data
data obtained
obtained from
from the
the HSS.
HSS.
IfIf authentication
authentication was
was successful,
successful, the
the MME
MME
informs
informs the
the HSS
HSS that
that itit is
is now
now serving
serving the
the
UE
UE by
by sending
sending aa Location
Location Update
Update message.
message.
The
The HSS
HSS sends
sends the
the users
users subscription
subscription data
data
to
to the
the MME.
MME. The
The MME
MME acknowledges
acknowledges this
this
action.
action.
The
The HSS
HSS acknowledges
acknowledges the
the Update
Update
Location
Location message
message received
received from
from the
the MME
MME
in
in step
step 4.
4.
In
In LTE,
LTE, an
an integral
integral part
part of
of the
the attach
attach
procedure
procedure is
is to
to establish
establish the
the default
default EPS
EPS
bearer.
bearer.
Page 14
Introduction
ECM-IDLE State
2
UE
eNB
MME
Connection
Management
P-GW
S-GW
8
HSS
13
14
End-to-End Example
12
11
IP address
for UE
15
The radio bearers are established
Uplink user data (if available) can be sent

starting from this point
Downlink user data (if available) can be sent

starting from this point.
18
19
20

Message includes GTP tunnel endpoint identifier (TEID)
1/1
Legal notice
Page info
1. Figure on previous page scrolls up and box Default EPS bearer is created expands into figure shown above.
2. Highlight arrows/buttons 8, 9, 11, 12, 13, 17, 18 and 20.
3. Highlight button 10 and add callout. 4. Highlight arrows/buttons 14 and 15.
5. Highlight blue arrows/button 16. 6. Highlight blue arrows/button 19.
7. Shortly highlight blue circle and text at the bottom of the figure (and maybe all the blue-circled labels in the figure).
The user plane connection between the

PDN Gateway (P-GW), Serving Gateway (SGW), and eNodeB is established
The UE is allocated an IP address
16
17
Establishing the default EPS bearer includes

the following steps:
10
ECM-CONNECTED State
Print
Abbreviations
Exit
Speech script
LTE Attach (2/2)
Welcome
Audio on/off
Speech script
Content map
Note that GPRS Tunnelling Protocol (GTP)

tunnels must be set up in both directions for
the default bearer in the user plane between
the eNodeB and P-GW, and for the control
plane signalling between the S-GW and PGW. When setting up GTP tunnels, tunnel
endpoint identifier (TEID) information must be
sent to the relevant nodes. Messages
carrying TEID information are indicated with
blue circles in the figure.
Audio on/off
LTE Attach (2/2)
Welcome
Introduction
ECM-IDLE State
The
The eNB
eNB sends
sends aa confirmation
confirmation to
to
Connection
the
that
the MME
MME
that the
the radio
radio and
and S1
S1
bearers
have
bearers
Management
have been
been set
set up
up and
and the
the
UE
UE is
is now
now capable
capable of
of transmitting
transmitting
uplink
uplink user
user data.
data. The
The eNB
eNB also
also
Mobility
Management
includes
the
of
includes
the TEID
TEID
of the
the downlink
downlinkin
GTP
endpoint
ECM-CONNECTED
State
GTP tunnel
tunnel
endpoint in
in the
the eNB,
eNB,
and
and forwards
forwards the
the NAS
NAS Attach
Attach
Confirm
Confirm message
message (received
(received in
in
End-to-End
Example
message
15)
message
15) to
to the
the MME.
MME.
The
The MME
MME forwards
forwards the
the eNB
eNB TEID
TEID
(received
(received in
in message
message 17)
17) to
to the
the SSGW.
GW.
After
After receiving
receiving the
the eNB
eNB TEID
TEID
information,
information, the
the S-GW
S-GW can
can now
now
send
send downlink
downlink user
user data
data to
to the
the
eNB.
eNB. However,
However, itit is
is unlikely
unlikely that
that
there
there is
is any
any downlink
downlink user
user data
data at
at
this
this point,
point, since
since the
the UE
UE has
has only
only
just
network.
just attached
attached to
to the
the
network.
1/1
Finally,
Finally, the
the S-GW
S-GW sends
sends an
an
acknowledgement
acknowledgement to
to the
the MME.
MME.
UE
eNB
MME
P-GW
S-GW
8
HSS
17
12
13
11
The
The P-GW
P-GW assigns
assigns the
the UE
UE an
an IP
IP address.
address.
11
The
The P-GW
P-GW responds
responds to
to the
the S-GW
S-GW with
with the
the
TEIDs
TEIDs of
of the
the uplink
uplink GTP
GTP tunnel
tunnel endpoints
endpoints
(for
(for the
the user
user plane
plane and
and control
control plane
plane GTP
GTP
tunnels)
tunnels) in
in the
the P-GW.
P-GW.
15
12
16
18
17
18
13
19
19
20


20Legal notice
14
Page info
15

16
Since
Since the
the eNB
eNB has
has obtained
obtained the
the S-GW
S-GW TEID
TEID
information
information (in
(in message
message 13),
13), itit can
can send
send the
the
uplink
uplink user
user data
data (received
(received from
from the
the UE)
UE) to
to
the
the S-GW.
S-GW.
The
The S-GW
S-GW requests
requests the
the P-GW
P-GW to
to set
set up
up the
the
default
default bearer
bearer in
in the
the user
user plane
plane over
over the
the
S5/S8
S5/S8 interface.
interface. This
This message
message includes
includes the
the
tunnel
tunnel endpoint
endpoint identifiers
identifiers (TEIDs)
(TEIDs) of
of the
the
downlink
downlink GTP
GTP tunnel
tunnel endpoints
endpoints in
in the
the S-GW
S-GW
for
for the
the user
user plane
plane and
and control
control plane
plane GTP
GTP
tunnels.
tunnels.
10
10
14
Print
Abbreviations
Speech
script
The
selects
aa Serving
Gateway
The MME
MME
selects
Serving
Gateway (S(SExit
GW)
and
Content
requests
map itit to
set
up
the
default
GW)
and
requests
to
set
up
the
default
8
bearer.
bearer. Included
Included in
in the
the message
message is
is the
the MME
MME
identifier
and
identifier
and address,
address, used
used later
later for
for paging
paging
Speech
script
purposes
purposes (see
(see the
the paging
paging animation).
animation).
The
The S-GW
S-GW responds
responds to
to the
the MME
MME with
with the
the
TEID
TEID of
of the
the uplink
uplink GTP
GTP tunnel
tunnel endpoint
endpoint in
in
the
the S-GW
S-GW for
for the
the user
user plane
plane default
default bearer.
bearer.
The
The MME
MME forwards
forwards the
the S-GW
S-GW TEID
TEID
(received
(received in
in message
message 12)
12) to
to the
the eNB
eNB and
and
instructs
instructs the
the eNB
eNB to
to set
set up
up the
the radio
radio bearers
bearers
towards
towards the
the UE.
UE. The
The message
message includes
includes the
the
NAS
NAS Attach
Attach Accept
Accept message
message to
to be
be sent
sent to
to
the
the UE.
UE.
The
The eNB
eNB forwards
forwards the
the NAS
NAS Attach
Attach Accept
Accept
message
message to
to the
the UE
UE and
and starts
starts setting
setting up
up the
the
radio
radio bearers
bearers over
over the
the air
air interface.
interface.
A
A confirmation
confirmation is
is sent
sent back
back to
to the
the eNB
eNB when
when
the
the radio
radio bearers
bearers have
have been
been set
set up.
up. Also
Also
included
included is
is the
the NAS
NAS Attach
Attach Confirm
Confirm
message.
message.
Page 15
Introduction
ECM-IDLE State
UE
Connection
Management
eNB
MME
S-GW
HSS
The procedure includes the following steps:
2
3
End-to-End Example
An RRC connection between the UE and

eNodeB is established
The UE sends a Service Request message

to the MME, partly using the RRC connection
User traffic in
one direction
only?
6
7
8

necessary
The S1 bearers are established
The radio bearers are established
The user data is sent in the uplink.

Show
Show
9
10
1/1
Legal notice
The ECM-IDLE to ECM-CONNECTED state

transition procedure involves the UE,
eNodeB, MME and S-GW, and is required
when there is user data to be sent to/from the
UE while the UE is in the ECM-IDLE state.
If the UE has uplink data to be sent, the
procedure is initiated by the UE as shown in
the figure - hence the name UE-initiated
communication.
Random Access
Procedure
ECM-CONNECTED State
Print
Abbreviations
Exit
Speech script
UE-initiated Communication
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show figure without highlighting. When UE, eNB, MME and S-GW are mentioned, highlight the icons.
3. Highlight arrows/buttons 1 and 2. 4. Highlight arrows/button 3.
5. Highlight arrows/buttons 4, 8, 9 and 10. 6. Highlight arrows/button 5 and 6.
7. Highlight arrows/button 7.
Audio on/off
Speech script
Content map
Speech script
Welcome
Introduction
ECM-IDLE State
Connection
Management
User traffic in one direction only?
ECM-CONNECTED State
In a typical user data application,

there is also data traffic in the
opposite direction (for instance ACK
frames during a file transfer
session).
End-to-End Example
Note that a downlink GTP tunnel has

also been established (steps 8 and
9). However, the animation does not
show any downlink traffic.
Ok
Ok
1/1
Legal notice
Page info
Tutor animation.
Print
Abbreviations
Exit
Print
Audio on/off
Abbreviations
Speech script
Exit is
The
Content
access
map procedure
The random
random
access
procedure
is necessary
necessary
for
for establishing
establishing an
an RRC
RRC signalling
signalling
connection
connection
between UE
UE and
and eNB.
eNB.
Speech
script between
Welcome
Introduction
ECM-IDLE State
2
UE
Connection
Management
eNB
MME
S-GW
Random Access
Procedure
ECM-CONNECTED State
HSS
4
3
End-to-End Example
5
6
7
8
5
9

6
10
7
1/1
Legal notice
A
A Non
Non Access
Access Stratum
Stratum (NAS)
(NAS) Service
Service
Request
Request message
message is
is sent
sent to
to the
the eNB
eNB
encapsulated
encapsulated in
in an
an RRC
RRC message.
message.
The
The NAS
NAS Service
Service Request
Request message
message is
is
forwarded
forwarded to
to the
the MME
MME encapsulated
encapsulated in
in an
an
S1AP
S1AP Initial
Initial UE
UE Message.
Message.
The
The MME
MME may
may perform
based
on
on data
data obtained
obtained from
from the
the HSS.
HSS.
The
The MME
MME sends
sends an
an S1AP
S1AP Initial
Initial Context
Context
Setup
Setup Request
Request message
message to
to the
the eNB.
eNB. This
This
message
message includes
includes (among
(among others)
others) the
the
tunnel
tunnel endpoint
endpoint identifier
identifier (TEID)
(TEID) for
for the
the
uplink
uplink GTP
GTP tunnel
tunnel endpoint
endpoint in
in the
the S-GW.
S-GW.
The
The MME
MME obtained
obtained this
this information
information when
when
the
the default
default EPS
EPS bearer
bearer was
was established
established
during
during the
the LTE
LTE attach
attach procedure.
procedure.
Signalling
Signalling needed
needed for
for setting
setting up
up the
the radio
radio
bearers
bearers over
over the
the air
air interface.
interface.
After
After receiving
receiving the
the S-GW
S-GW TEID
TEID information,
information,
the
the eNB
eNB can
can send
send the
the uplink
uplink user
user data
data
received
received from
from the
the UE
UE to
to the
the S-GW.
S-GW.
The
The eNB
eNB sends
sends an
an S1AP
S1AP Initial
Initial Context
Context
Setup
Setup Complete
Complete message
message to
to the
the MME.
MME. This
This
message
message includes
includes the
the eNB
eNB TEID
TEID for
for the
the
downlink
downlink GTP
GTP tunnel.
tunnel.
Page info
The
The MME
MME forwards
forwards the
the eNB
eNB TEID
TEID
information
information to
to the
the S-GW.
S-GW.
10
Finally,
Finally, the
the S-GW
S-GW sends
sends an
an
acknowledgement
acknowledgement to
to the
the MME.
MME.
Page 16
Introduction
ECM-IDLE State
UE
eNB
S-GW
HSS
Notification
Connection
Management
ECM-CONNECTED State
MME
1
End-to-End Example
4
5
7
No user data
in uplink
10
User traffic in
one direction
only?
11
Show
Show

Legal notice
The UE will probably not have any uplink

data to send
However, the network has downlink data to

be sent to the UE
8
9
1/1
The main reason for network-initiated

communication is the arrival of downlink user
data at the Serving Gateway.
3
3
In order for the network to trigger the ECMIDLE to ECM-CONNECTED state transition,
the UE must be paged.
When the UE responds to the paging

request, the signalling procedure is similar to
that employed in UE-initiated communication,
but with the following differences:
Random Access
Procedure
2
Print
Abbreviations
Exit
Speech script
Network-initiated Communication
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show figure without callouts and highlighting. When mentioned must be paged, shortly highlight arrows/buttons marked 1.
2. Highlight top blue arrow.
3. Show blue callout (only during this step).
4. Highlight blue arrows with button number 10.

Audio on/off
Speech script
Content map
Speech script
Welcome
Introduction
ECM-IDLE State
Connection
Management
User traffic in one direction only?
ECM-CONNECTED State
In a typical user data application,

there is also data traffic in the
opposite direction (for instance ACK
frames during a file transfer
session).
End-to-End Example
Note that an uplink GTP tunnel has

also been established (step 5).
However, the animation does not
show any uplink traffic.
Ok
Ok
1/1
Legal notice
Page info
Tutor animation.
Change
Print
Abbreviations
Exit

1
The
random
Speech
Thescript
random access
access procedure
procedure is
is necessary
necessary
Welcome
for
for establishing
establishing an
an RRC
RRC signalling
signalling
connection
connection between
between UE
UE and
and eNB.
eNB.
Introduction
2
ECM-IDLE State
UE
eNB
Connection
Management
ECM-CONNECTED State
MME
S-GW
Random Access
Procedure
2
End-to-End Example
HSS

3
5
4
5
6
7
6
8
Print
Audio on/off
Abbreviations
Speech script
The
Content
pages
map
the
The MME
MME
pages
the UE.
UE. Exit
A
A Non
Non Access
Access Stratum
Stratum (NAS)
(NAS) Service
Service
Request
Request message
message is
is sent
sent to
to the
the eNB
eNB
encapsulated
encapsulated in
in an
an RRC
RRC message.
message.
The
The NAS
NAS Service
Service Request
Request message
message is
is
forwarded
forwarded to
to the
the MME
MME encapsulated
encapsulated in
in an
an
S1AP
S1AP Initial
Initial UE
UE Message.
Message.
The
The MME
MME may
may perform
based
on
on data
data obtained
obtained from
from the
the HSS.
HSS.
The
The MME
MME sends
sends an
an S1AP
S1AP Initial
Initial Context
Context
Setup
Setup Request
Request message
message to
to the
the eNB.
eNB. This
This
message
message includes
includes (among
(among others)
others) the
the
tunnel
tunnel endpoint
endpoint identifier
identifier (TEID)
(TEID) for
for the
the
uplink
uplink GTP
GTP tunnel
tunnel endpoint
endpoint in
in the
the S-GW.
S-GW.
Signalling
Signalling needed
needed for
for setting
setting up
up the
the radio
radio
bearers
bearers over
over the
the air
air interface.
interface.
9
10
8
11
1/1
9
Legal notice
Page info
10
11
The
The eNB
eNB sends
sends an
an S1AP
S1AP Initial
Initial Context
Context
Setup
Setup Complete
Complete message
message to
to the
the MME.
MME. This
This
message
message includes
includes the
the eNB
eNB TEID
TEID for
for the
the
downlink
downlink GTP
GTP tunnel.
tunnel.
The
The MME
MME forwards
forwards the
the eNB
eNB TEID
TEID
information
information to
to the
the S-GW.
S-GW.
After
After receiving
receiving the
the eNB
eNB TEID
TEID information,
information,
the
the S-GW
S-GW can
can send
send the
the downlink
downlink user
user data
data
via
via the
the eNB
eNB to
to the
the UE.
UE.
Finally,
Finally, the
the S-GW
S-GW sends
sends an
an
acknowledgement
acknowledgement to
to the
the MME.
MME.
Page 17
Introduction
ECM-IDLE State
UE
Connection
Management
eNB
MME
S-GW
The release of a connection, in other words

moving from the ECM-CONNECTED to ECMIDLE state, may occur for several reasons,
for instance user inactivity.
In this case the eNodeB requests the MME to

release the signalling and user plane
connections associated with this UE.
3
No data traffic
for a long time!
ECM-CONNECTED State
Naturally, the eNodeB also makes sure that

the radio bearers are released.

1
2
3
End-to-End Example
4
5
6
7

1/1
Legal notice
Print
Abbreviations
Exit
Speech script
Connection Release
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show figure. Add callout at the end of the sentence.
2. Highlight arrow/button 1.
3. Highlight arrows/buttons 2, 3, 4 and 7.
Audio on/off
Speech script
Content map
Speech script
Connection Release
Welcome
Introduction
ECM-IDLE State
UE
eNB
MME
S-GW
2
Connection
Management
1
ECM-CONNECTED State
2
3
End-to-End Example
4
5
6
7

4
5
6
1/1
Legal notice
Page info
Print
Abbreviations
Exit
The
The eNB
eNB decides
decides that
that the
the UE
UE should
should move
move
to
to the
the ECM-IDLE
ECM-IDLE state
state and
and sends
sends aa UE
UE
Context
Context Release
Release Request
Request message
message to
to the
the
MME.
MME.
The
The MME
MME sends
sends an
an S1AP
S1AP Update
Update Bearer
Bearer
Request
Request message
message to
to the
the S-GW,
S-GW, informing
informing
the
the S-GW
S-GW that
that the
the UE
UE will
will now
now move
move to
to the
the
ECM-IDLE
ECM-IDLE state.
state.
The
The S-GW
S-GW releases
releases the
the eNB
eNB related
related
information
information such
such as
as the
the tunnel
tunnel endpoint
endpoint
identifiers
identifiers (TEID)
(TEID) of
of the
the downlink
downlink GTP
GTP tunnel
tunnel
endpoints
endpoints in
in the
the eNB.
eNB. The
The S-GW
S-GW
acknowledges
acknowledges the
the release
release to
to the
the MME.
MME. Any
Any
downlink
downlink data
data for
for the
the UE
UE that
that arrives
arrives at
at the
the
S-GW
S-GW after
after this
this point
point will
will have
have to
to be
be
buffered.
buffered. The
The UE
UE can
can only
only be
be reached
reached
through
through paging.
paging.
The
The MME
MME sends
sends an
an S1AP
S1AP UE
UE Context
Context
Release
Release Command
Command message
message to
to the
the eNB.
eNB.
Signalling
Signalling needed
needed for
for releasing
releasing the
the radio
radio
bearers
bearers over
over the
the air
air interface.
interface.
The
The eNB
eNB releases
releases the
the S-GW
S-GW related
related
information
information such
such as
as the
the tunnel
tunnel endpoint
endpoint
identifiers
identifiers (TEID)
(TEID) of
of the
the uplink
uplink GTP
GTP tunnel
tunnel
endpoints
endpoints in
in the
the S-GW.
S-GW. The
The eNB
eNB
acknowledges
acknowledges the
the release
release by
by sending
sending an
an
S1AP
S1AP UE
UE Context
Context Release
Release Complete
Complete
message
message to
to the
the MME.
MME.
Page 18
Introduction
Cell Radio Network Temporary Identifier (C-RNTI)
Temporary
Temporary Mobile
Mobile Subscriber
Subscriber Identity
Identity (S-TMSI)
(S-TMSI)
Connection
Management
Uniquely identifies the UE within a given tracking area

Used over the air interface in ECM-IDLE state
Allocated by the MME
ECM-CONNECTED State
Globally Unique Temporary Identity (GUTI)
End-to-End Example
International
International Mobile
Mobile Equipment
Equipment Identity
Identity (IMEI)
(IMEI)
Globally unique terminal equipment (hardware) identifier
Used for checking stolen equipment
1/1
Legal notice
Page info
Add or highlight labels and bulleted items when mentioned. Maybe a nice background picture related to identifier.
The Temporary Mobile Subscriber Identity (STMSI) uniquely identifies the UE within a
certain tracking area. This identifier is
primarily used when the UE is in the ECMIDLE state.
The Globally Unique Temporary Identity

(GUTI) can be considered an extended
version of the S-TMSI, since it uniquely
identifies both the UE within a certain tracking
area and the MME handling the UE.
The International Mobile Subscriber Identity

(IMSI) uniquely identifies the UE anywhere in
the world. Since it is so revealing, it is not
transmitted unencrypted over the air interface
if not absolutely necessary. The S-TMSI is
used instead in this case.
Finally, the International Mobile Equipment

Identity (IMEI) uniquely identifies the teminal
equipment hardware. This number can be
used by the network to stop a stolen phone
from accessing the network.
Globally unique UE identifier

Used carefully over the air interface
Allocated by the home network operator
The Cell Radio Network Temporary Identifier

(C-RNTI) is used over the LTE air interface. It
uniquely identifies the UE within a certain cell.
The C-RNTI only exists when the UE is in the
ECM-CONNECTED state.
Temporary identifier including globally unique MME identity

GUTI is kind of extended S-TMSI
International
International Mobile
Mobile Subsriber
Subsriber Identity
Identity (IMSI)
Let us next look at some important UE

identifiers used in LTE.
Unique within a certain cell

Used over the air interface in ECM-CONNECTED state
Allocated by the eNB
ECM-IDLE State
Print
Abbreviations
Exit
Speech script
UE Identifiers used in LTE
Welcome
Audio on/off
Speech script
Content map
Change
Exercise
Welcome
Introduction
Page 19
In order to set up the uplink and downlink

GTP tunnels over the S1 interface, the tunnel
endpoint identifiers (TEID) of the GTP tunnel
endpoints must be conveyed to the relevant
network nodes.
ECM-IDLE to ECM-CONNECTED state transition
Your task is to indicate which signalling

messages include TEID information.
Connection
Management
UE
ECM-CONNECTED State
eNB
MME
S-GW
Random Access
Part of LTE
attach signalling
End-to-End Example
Print
Abbreviations
Exit
Speech script
In the figure below, four signalling messages include TEID

information. Click these messages with your mouse pointer
and click Submit when ready.
ECM-IDLE State
Audio on/off
Speech script
Content map
Change
Please try again.

solution!
Submit
Submit
1/1
Legal notice
Page info
Correct choice is indicated with yellow colour.
Page 20
Introduction
EMM-DEREGISTERED
Connection
Management
MM in ECM-CONNECTED
state = handovers
ECM-CONNECTED State
Four types of handover will be explained in

this course:
Intra-LTE intra-eNodeB handovers take place

between cells within a certain eNodeB. This is
the least complex type of handover.
EMM-REGISTERED
ECM-CONNECTED
EMM-REGISTERED
ECM-IDLE
End-to-End Example
Up to now, we have been examining

connection management and mobility
management procedures in the ECM-IDLE
state. Now let us turn to mobility management
procedures in the ECM-CONNECTED state.
These procedures are called handovers.
ECM-IDLE State
What about performance

requirements?
Show
Show
1/1
Legal notice
Print
Abbreviations
Exit
Speech script
Introduction
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show nice background picture. Show state diagram above and highlight ECM-CONNECTED when mentioned.
2. Add callout.
3. Fade out figure and fade in network figure on next slide.
:
:
8. Add or activate tutor animation (shown on later slide).
Intra-LTE inter-eNodeB handovers take place

between different eNodeBs, for instance
utilising the X2 interface as shown in the
second handover example in this course.
3GPP inter radio access technology (interRAT) handovers take place between the
Evolved UTRAN and a non-LTE 3GPP access
network (for instance UTRAN or GERAN). The
third handover example in this course shows
an E-UTRAN to UTRAN handover.
A non-3GPP inter-RAT handover takes place
between the Evolved UTRAN and a non-3GPP
access network, for instance WLAN, WiMAX
or 3GPP2 access network. The fourth
handover example in this course shows a
handover from an LTE network to a 3GPP2
evolved High Rate Packet Data (eHRPD)
network.
performance requirements related to
handovers.
Audio on/off
Speech script
Content map
Speech script
Introduction
Welcome

Introduction
E-UTRAN
ECM-IDLE State
EPC
UE
Connection
Management

this course:
eNB
Intra-eNodeB
Intra-eNodeB handover
handover
S-GW
P-GW
ECM-CONNECTED State
4
Packet
Data
Network
End-to-End Example
BTS
requirements?
RNC
UTRAN
Show
Show
1/1
Legal notice
Print
Abbreviations
Exit
Page info
4. Add label. UE makes intra-eNB handover (UE moves down, new cell appears, old cell fades out).

network.
handovers.
Audio on/off
Speech script
Content map
Speech script
Introduction
Welcome

Introduction
E-UTRAN
ECM-IDLE State
EPC
eNB
Connection
Management

this course:
X2
S-GW
UE
P-GW

eNB
ECM-CONNECTED State
Inter-eNodeB
Inter-eNodeB handover
handover
End-to-End Example
BTS
requirements?
RNC
UTRAN
Show
Show
1/1
Legal notice
Print
Abbreviations
Exit
Page info
5. Change label. UE makes handover from upper to lower eNB. Add/highlight X2 interface when mentioned.
Packet
Data
Network

network.
handovers.
Audio on/off
Speech script
Content map
Speech script
Introduction
Welcome

Introduction
E-UTRAN
ECM-IDLE State
EPC
3GPP
3GPP inter-RAT
inter-RAT handover
handover
Connection
Management

this course:
eNB
S-GW
ECM-CONNECTED State
P-GW
BTS
requirements?
6
UTRAN = 3G radio access network
GERAN = GSM/EDGE radio access network
1/1
|

RNC
UTRAN
Show
Show
Legal notice

Packet
Data
Network
UE
End-to-End Example
Print
Abbreviations
Exit
Page info
6. Change label again. UE makes handover from E-UTRAN to UTRAN and back to E-UTRAN (so that it can make another
handover on next slide). When mentioned, show UTRAN/GERAN legend.
network.
handovers.
Audio on/off
Speech script
Content map
Speech script
Introduction
Welcome

Introduction
ECM-IDLE State
E-UTRAN
EPC
Non-3GPP
Non-3GPP inter-RAT
inter-RAT handover
handover
Connection
Management

this course:
eNB
S-GW
ECM-CONNECTED State
Non-3GPP network
(WLAN, WiMAX, 3GPP2)

requirements?
Show
Show
1/1
Legal notice
P-GW

Packet
Data
Network
UE
End-to-End Example
Print
Abbreviations
Exit

3GPP2:
Evolved High Rate Packet
Data (eHRPD) network
Change lower network

at this point, not during
Copyright Nokia previous
Siemens Networksspeech
2007
Page info
7. Change lower network and label. UE makes handover from E-UTRAN to non-3GPP network. Add callout at the end of the
paragraph.

network.
handovers.
Speech script
Introduction
Welcome
Introduction
ECM-IDLE State
What about performance requirements?
Connection
Management
Inter-eNB handover over X2:

The average interruption in the user plane shall not
be greater than 54 ms (DL) and 58 ms (UL).
The average interruption in the control plane shall
ECM-CONNECTED State
Inter-RAT handover from LTE to UMTS:

The average interruption in the user plane shall not
be greater than 150 ms (DL) and 300 ms (UL).
End-to-End Example
Ok
Ok
1/1
Legal notice
Page info
Tutor mouseover animation.
Audio on/off
Speech script
Content map
Print
Abbreviations
Exit
Page 21
Introduction
1
E-UTRAN
ECM-IDLE State
EPC
2
UE
Connection
Management
eNB
S-GW
ECM-CONNECTED State
P-GW
Packet
Data
Network
End-to-End Example
BTS
RNC
UTRAN
1/1
Legal notice
Page info
1. Show figure without anchor point.
2. Add anchor point in S-GW and highlight blue connection S-GW - eNB - UE.
3. Highlight black connection S-GW - P-GW - packet data network.
Print
Abbreviations
Exit
Speech script
Mobility Anchor Point
Welcome
Audio on/off
Speech script
Content map
Mobility
anchor point
During mobility, the user plane data path

continuity to the packet data network is
maintained using a concept called mobility
anchoring.
The path from the UE to the mobility anchor
point may change during the handover.
However, the path from the anchor point to
the peer entity in the packet data network
does not change.
During an intra-eNodeB handover, the

eNodeB serves as the anchor point.
During an inter-eNodeB handover, the anchor

point is located in the Serving Gateway.
Also, during a 3GPP inter radio access

technology (inter-RAT) handover, the anchor
However, when the handover is to or from a

non-3GPP network, the anchor point is
located in the PDN Gateway.
Audio on/off
Speech script
Content map
Speech script
Welcome

anchoring.
Introduction
E-UTRAN
ECM-IDLE State
EPC

does not change.
UE
Connection
Management
eNB
S-GW
ECM-CONNECTED State
P-GW
4
Packet
Data
Network
End-to-End Example
BTS
Mobility
anchor point
1/1
|

RNC
UTRAN
Legal notice
Print
Abbreviations
Exit
Page info
4. Move anchor point to eNB. UE makes intra-eNB handover (UE moves down, new cell appears, old cell fades out).

Audio on/off
Speech script
Content map
Speech script
Welcome

anchoring.
Introduction
E-UTRAN
ECM-IDLE State
Connection
Management
EPC

does not change.
eNB
S-GW
UE
ECM-CONNECTED State
P-GW
Packet
Data
Network
End-to-End Example
BTS
1/1
|
Page info
5. Move anchor point to S-GW. UE makes handover from upper to lower eNB.

5

RNC
UTRAN
Legal notice
Print
Abbreviations
Exit
Mobility
anchor point

Audio on/off
Speech script
Content map
Speech script
Welcome

anchoring.
Introduction
E-UTRAN
ECM-IDLE State
Connection
Management
EPC

does not change.
eNB
S-GW
ECM-CONNECTED State
End-to-End Example
P-GW
UE
RNC
UTRAN

6
Mobility
anchor point
1/1
Legal notice

Packet
Data
Network
BTS
Print
Abbreviations
Exit
Page info
6. UE makes handover from E-UTRAN to UTRAN and back to E-UTRAN (so that it can make another handover on next slide).

Audio on/off
Speech script
Content map
Speech script
Welcome

anchoring.
Introduction
E-UTRAN
ECM-IDLE State
Connection
Management
EPC

does not change.
eNB
S-GW
ECM-CONNECTED State
End-to-End Example
P-GW

Packet
Data
Network
UE
Non-3GPP network
(WLAN, WiMAX, 3GPP2)
1/1
Legal notice
Print
Abbreviations
Exit
Page info
7. Move anchor point to P-GW. UE makes handover from E-UTRAN to non-3GPP network.

Mobility
anchor point

Page 22
Introduction
ECM-IDLE State
UE
eNB
Connection
Management
Print
Abbreviations
Exit
Speech script
Intra-eNodeB Handover
Welcome
Audio on/off
Speech script
Content map
S-GW
Intra-eNodeB handovers take place between

different cells within the same eNodeB. The
handover procedure is shown in the figure.
Since the UE is in the ECM-CONNECTED
state, user data can be sent both in uplink
and downlink before the handover.
1
3
Handover decision
ECM-CONNECTED State
Allocate resources
6a
End-to-End Example
6b
6c

2
Detach (old cell) and
random access (new cell)
3
Stop user data traffic over

air interface
Resume user data

transport over air interface
The UE detaches from the source cell and

synchronises with the target cell using the
non-contention based random access
procedure.
After successful handover, the user data

transport over the air interface can be
resumed.

1/1
|
Page info
1. Show figure without highlighting and callouts.
2-7. Highlight items in figure and add callouts (steps 5 and 7).
In the case of a handover decision, the

eNodeB allocates the resources for the target
cell. From this point on, downlink user data is
buffered in the eNodeB and uplink user data
in the UE until the handover has been
completed.
Release resources (old cell)
Legal notice
The handover decision in the eNodeB is

based on a measurement report sent by the
UE as well as radio resource management
(RRM) information.
Audio on/off
Speech script
Content map
The
UE
Speech
Thescript
UE is
is in
in the
the ECM-CONNECTED
ECM-CONNECTED state
state
Intra-eNodeB Handover
Welcome
Introduction
eNB
Connection
Management
S-GW
The
The radio
radio bearers
bearers in
in the
the target
target cell
cell are
are
configured.
configured. The
The UE
UE is
is allocated
allocated aa new
new CCRNTI
RNTI for
for identification
identification in
in the
the new
new (target)
(target)
cell.
cell. From
From this
this point
point on,
on, downlink
downlink user
user data
data
is
is buffered
buffered in
in the
the eNB
eNB and
and uplink
uplink user
user data
data
in
in the
the UE
UE until
until the
the handover
handover has
has been
been
completed.
completed.
1
Handover decision
ECM-CONNECTED State
Allocate resources
2
End-to-End Example
Detach (old cell) and

random access (new cell)
3
4
1/1
3
Legal notice
The
The eNB
eNB sends
sends an
an RRC
RRC Handover
Handover
Command
Command message
message towards
towards the
the UE
UE with
with
the
the necessary
necessary information
information (e.g.
(e.g. new
new CCRNTI)
RNTI) to
to allow
allow the
the UE
UE to
to connect
connect to
to the
the
target
target cell.
cell.
The
The UE
UE immediately
immediately detaches
detaches from
from the
the
source
source cell
cell and
and synchronises
synchronises with
with the
the target
target
cell
cell using
using the
the non-contention
non-contention based
based random
random
access
access procedure.
procedure.
Release resources (old cell)
Page info
so
so that
that user
user data
data can
can be
be sent
sent both
both in
in uplink
uplink
and
and downlink.
downlink.
The
The eNB
eNB makes
makes the
the decision
decision to
to handover
handover
the
the UE
UE to
to another
another cell
cell within
within the
the same
same eNB
eNB
based
based on
on measurement
measurement and
and RRM
RRM
information.
information.
ECM-IDLE State
UE
Print
Abbreviations
Exit
After
After successful
successful handover,
handover, the
the UE
UE sends
sends the
the
RRC
RRC Handover
Handover Confirm
Confirm message
message to
to the
the
eNB.
eNB.
The
The eNB
eNB can
can begin
begin sending
sending downlink
downlink user
user
data
data towards
towards the
the UE,
UE, and
and the
the UE
UE can
can begin
begin
sending
sending uplink
uplink user
user data
data to
to the
the eNB.
eNB.
The
The eNB
eNB releases
releases the
the UEs
UEs resources
resources in
in the
the
source
source cell.
cell.
Page 23
Introduction
ECM-IDLE State
Connection
Management
ECM-CONNECTED State
MME
S-GW
DL & UL
user data
3
4
Source
eNB
End-to-End Example
Target
eNB
X2 interface
4
1. Handover
decision
3. Resources
allocated
5
UE
1/1
Legal notice
Print
Abbreviations
Exit
Speech script
Intra-LTE Inter-eNodeB Handover 1/3
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show network elements and solid blue line only.
2. Highlight X2 interface (show green items and remove at end of paragraph to make place for other items).
3. Highlight blue line.
4. Add callout 1. 5. Add arrow/message 2. 6. Add callout 3. 7. Add arrow/message 4. 8. Add arrow/message 5.
7
8
Let us next see how an inter-eNodeB

handover is performed. The animation is in
three steps.
It is assumed that the X2 interface exists
between the source and target eNodeB. If
this interface does not exist, the handover
must be performed over the S1 interface
instead, which means more complex
signalling.
To begin with, the downlink and uplink user
data is carried via the source eNodeB - see
the blue line in the figure.
Based on UE measurement and RRM
information, the source eNodeB decides that
a handover to the target eNodeB is
necessary.
The source eNodeB sends a Handover
Request message over the X2 interface to
the target eNodeB. The message contains
necessary information to prepare the
handover at the target side.
The target eNodeB allocates resources for
the target cell. The UE is allocated a new CRNTI for identification in the target cell.
The target eNodeB sends a Handover
Request Acknowledge message to the source
eNodeB, which in turn sends an RRC
Handover Command message over the air
interface to the UE, including necessary
information (such as the new C-RNTI) so that
the UE can perform the handover.
Page 24
Introduction
ECM-IDLE State
MME
S-GW
Connection
Management
ECM-CONNECTED State
7. Buffer DL
user data
2
4
Source
eNB
Target
eNB
End-to-End Example
4
1. Handover
decision
8. Buffer UL user data, detach (old

cell) and random access (new cell)
3. Resources
allocated
10. DL & UL user
data
1/1
In animation, old items could be shadowed to make animation clearer

|
Now the UE can start sending the buffered

uplink user data and the target eNodeB can
forward the downlink user data to the UE. The
uplink user data is sent via the target eNodeB
directly to the Serving Gateway. This is
possible, since the uplink tunnel endpoint
identifier (TEID) in the S-GW was conveyed
to the target eNodeB already in step 2.
1. Add arrow/message 6. 2. Change blue line from previous slide to blue arrow from S-GW via source eNB to target eNB. Do
NOT continue blue line to UE yet. 3. Add callout 7. 4. Add callout 8. 5. Add arrow/message 9.
6. Now add blue arrow from UE to target eNB, and continue downlink blue arrow to UE (so now it goes S-GW - source eNB target eNB - UE).
7. Continue uplink blue arrow from target eNB to S-GW and add callout 10.
8. Shortly highlight item 2 when mentioned.
As soon as the Handover Command

message is received (step 5), the UE buffers
the uplink user data until the handover has
been completed, detaches from the source
cell, and synchronises with the target cell
using the non-contention based random
access procedure.
Next, the UE sends a Handover Confirm
message to the target eNodeB to indicate
that the handover procedure is completed as
far as the UE is concerned.
Page info
The source eNodeB sends Packet Data

Convergence Protocol (PDCP) sequence
number (SN) information to the target
eNodeB in an SN Status Transfer message.
This information is necessary to avoid
missing or duplicating PDCP packets when
the uplink and downlink user data paths are
switched from the source eNodeB to the
target eNodeB. Also, the source eNodeB now
forwards the received downlink user data
packets to the target eNodeB instead of
sending them to the UE. The downlink user
data packets are buffered in the target
eNodeB until the handover is completed.
UE
Legal notice
Print
Abbreviations
Exit
Speech script
Welcome
Audio on/off
Speech script
Content map
Page 25
Introduction
Next, the target eNodeB sends its downlink

tunnel endpoint identifier (TEID) to the MME,
which forwards it to the Serving Gateway.
Now the S-GW can send the downlink user

data directly to the target eNodeB.
14
ECM-IDLE State
MME
12
S-GW
13. New path for
DL user data
Connection
Management
11
17. Resources
released
ECM-CONNECTED State
15
7. Buffer DL
user data
2
4
Source
eNB
Target
eNB
End-to-End Example
16
1. Handover
decision
3. Resources
allocated
4
5
8. Buffer UL user data, detach (old

cell) and random access (new cell)
10. DL & UL user

data
UE
1/1
In animation, old items could be shadowed to make animation clearer

Legal notice
Print
Abbreviations
Exit
Speech script
Welcome
Audio on/off
Speech script
Content map
Page info
1. Add arrow/message 11 and 12.
2. Switch routing of blue downlink arrow to exclude source eNB as shown. Add callout 13.
3. Send a packet slowly along the dashed black arrow line. Then send another packet slowly along this line, and so on. (If you
want to show dashed black arrow line, do not show it any more after this paragraph.)
4. Add arrow/message 14 and 15. 5. Add arrow/message 16. 6. Add callout 17.
Before the S-GW can release any user plane

resources towards the source eNodeB, it
sends one or more end marker packets to
the source eNodeB as an indication that the
downlink data path has been switched. It
should be noted that these packets do not
contain any user data, and are transparently
forwarded by the source eNodeB to the target
eNodeB to help it decide when the last
forwarded packet was received.
After receiving an acknowledgement
message the target eNodeB informs the
source eNodeB about the success of the
handover. As a final step, the source eNodeB
releases all air interface and control plane
resources associated with the UE context.
Now the handover is completed.
Page 26
Introduction
ECM-IDLE State
Connection
Management
Source
eNB
UE
Target
RNC
Source
MME
Target
SGSN
S-GW
The following example illustrates a 3GPP

inter radio access technology (inter-RAT)
handover. The animation in two parts outlines
the basic operation during an LTE to 3G (that
is, E-UTRAN to UTRAN) handover.
1
2
Handover decision
3
ECM-CONNECTED State
End-to-End Example
Print
Abbreviations
Exit
Speech script
3GPP Inter-RAT Handover 1/2
Welcome
Audio on/off
Speech script
Content map
Prepare target access network
4
4
9
8
11
3
7
5
6
9
10
Detach and random access

8
10
Sending of UL
data possible
11
12
Legal notice
Based on UE measurement and RRM

information, the source eNodeB decides that
a handover to the target access network is
necessary and sends to the MME a message
containing necessary information to prepare
the handover at the target side. The MME
sends the information to the SGSN which in
turn prepares the target access network for
the handover.
Next, the SGSN provides relevant information
to the Serving Gateway, so that it can forward
downlink user data to the target RNC. Also,
the SGSN sends necessary information to the
UE so that the UE can perform the handover.
The eNodeB at this point sends so-called

Serving Radio Network Subsystem (SRNS)
Context information to be stored in the target
SGSN and RNC.
10
The downlink user data received at the

eNodeB is forwarded via the Serving
Gateway to the target RNC. Obviously, since
the UE is performing a handover it will not
send any uplink user data at this point.
13
1/1
To begin with, the downlink and uplink user

data is carried via the source eNodeB - see
the blue arrows in the figure.
| Routing
Copyright
Nokia Siemens
Networks
2007 (involves HSS)
areaupdate
(RAU) in
target system
Page info
1. Show figure without highlighting and highlight items when mentioned, or start figure from the top and add items when
mentioned. Another option is to scroll the figure somehow. Lower part of figure is animated on next page, it does not need to be 11
shown on this page.
2-7. Highlight or add items as shown. 8. Highlight or add arrows 5, 6 and 7 in this order.
9. Highlight or add the five arrows under item 8 from top to bottom.
10. Highlight or add blue arrows under item 9. 11. Add small blue arrow at the left, cross out and remove again.
Page 27
Introduction
ECM-IDLE State
Source
eNB
UE
Target
RNC
Source
MME
Target
SGSN
Handover decision
The UE detaches from the source cell and

synchronises with the target cell using the
WCDMA-based random access procedure.
Now the UE can send uplink user data via the

target RNC to the Serving Gateway.
ECM-CONNECTED State
1
S-GW
Connection
Management
3
Prepare target access network
End-to-End Example
Print
Abbreviations
Exit
Speech script
3GPP Inter-RAT Handover 2/2
Welcome
Audio on/off
Speech script
Content map
At this stage the target SGSN informs the

source MMEthat the UE has successfully
moved to the target access network.
The target SGSN completes the handover
procedure by informing the Serving Gateway
that the downlink user data can be sent
directly to the target RNC instead of being
sent back and forth via the source eNodeB.
Now, both the downlink and uplink user data
is carried via the target RNC.
9
6
1
Detach and random access
2
3
10
Sending of UL
data possible
4
11
5
12
13
1/1
Legal notice
Finally, the MME releases the resources in

the source access network.
| Routing
Copyright
Nokia Siemens
Networks
2007 (involves HSS)
areaupdate
(RAU) in
target system
Page info
Highlight or add items as shown. Upper part was animated on previous page. It could be shown in the beginning and then
collapsed, faded out or scrolled out, whatever is the best animation (but leave item 9 for continuity reasons).
Note that also the Home Subscriber Server

(HSS) must be informed about the handover.
This means that a routing area update must
be performed after the handover.
Page 28
Introduction
ECM-IDLE State
Connection
Management
ECM-CONNECTED State
3GPP2 (eHRPD)
network
P-GW
S-GW
HSGW
3
A11
S101
MME
End-to-End Example
eHRPD
access
network
eNB
E-UTRAN
6
User data
Signalling
UE
Perform pre-registration in
eHRPD access network
7
8
9
1/1
10
Legal notice
11
Page info
1. Show figure without callout and blue signalling arrows (but with blue user data lines).
2. Highlight 3GPP2 (eHRPD) network.
3. Add callout and signalling arrow between UE and eHRPD access network.
4. Highlight S101 interface. Fade out callout.
Print
Abbreviations
Exit
Speech script
LTE to CDMA2000 Handover
Welcome
Audio on/off
Speech script
Content map
Seamless handover will be supported

between LTE and CDMA2000 - to be more
specific between an LTE network and a
3GPP2 evolved High Rate Packet Data
(eHRPD) network - and general acceptance
has been reached that a closely coupled
architecture is needed to fulfill the stringent
latency requirements.
In the case of an LTE to eHRPD handover,
before the actual handover the UE performs
pre-registration with the target eHRPD
access network using the S101 interface
between the MME and eHRPD access
network. Pre-registration is performed in
order to speed up the actual handover phase.
A basic task of pre-registration is to set up a
data forwarding path over the S103 interface
between the LTE Serving Gateway and the
HRPD Serving Gateway (HSGW).
Using this path, the downlink user data is
forwarded to the eHRPD access network
during the handover as shown in the figure.
After completing the handover - again
signalled over the S101 interface - the user
data is routed directly between the P-GW and
the HSGW, and transport resources in the
Evolved Packet Core are released.
Note that the PDN Gateway acts as the
mobility anchor point during the handover.
Audio on/off
Speech script
Content map
Speech script
Welcome

Introduction
ECM-IDLE State
P-GW
3GPP2 (eHRPD)
network
S103
Connection
Management
ECM-CONNECTED State
Set up data
forwarding path
S-GW
HSGW
A11
S101
MME
End-to-End Example
eHRPD
access
network
eNB
E-UTRAN
UE
1/1
Legal notice

User data
Signalling
Print
Abbreviations
Exit
Page info
5. Add new callout, then the three signalling arrows, and then the tunnel over the S103 interface. Highlight S103 when
mentioned.
After completed handover - again signalled

over the S101 interface - the user data is
routed directly between the P-GW and the
HSGW, and transport resources in the
Audio on/off
Speech script
Content map
Speech script
Welcome

Introduction
ECM-IDLE State
S103
Connection
Management
ECM-CONNECTED State
3GPP2 (eHRPD)
network
P-GW
S-GW
HSGW

A11
S101
MME
End-to-End Example
eHRPD
access
network
eNB
E-UTRAN
6
User data
Signalling
UE
1/1
Legal notice
Print
Abbreviations
Exit
Page info
6. Fade out callout and signalling arrows from previous slide. Change user data path as shown.
7. Perform handover now (show left signalling arrow, UE moves to the right, show right signalling arrow and remove left
signalling arrow).

After completed handover - again signalled
over the S101 interface - the user data is
routed directly between the P-GW and the
HSGW, and transport resources in the
Audio on/off
Speech script
Content map
Speech script
Welcome

Introduction
Mobility
anchor point
ECM-IDLE State
P-GW
ECM-CONNECTED State
3GPP2 (eHRPD)
network
S103
Connection
Management
S-GW
HSGW

A11
S101
MME
End-to-End Example
eHRPD
access
network
eNB
E-UTRAN
User data
Signalling
UE

Release transport
resources
8
9
1/1
10
Legal notice
Print
Abbreviations
Exit
11
Page info
8. Add signalling arrow over S101 interface. Then fade out signalling arrow between UE and eHRPD access network.
9. Change user data path as shown.
10. Add green callout and signalling arrows between eNB and MME, MME and S-GW, and S-GW and P-GW. At the end of the
sentence, remove callout, all signalling arrows, and S103 interface.
11. Add blue callout.
After completing the handover - again

signalled over the S101 interface - the user
data is routed directly between the P-GW and
the HSGW, and transport resources in the
Page 29
In this exercise, the idea is to associate

various statements with the correct type of
handover. Please go ahead.
Introduction
Please click the correct tick boxes in the table below with
your mouse pointer. When you are ready, click Submit.
ECM-IDLE State
Connection
Management
ECM-CONNECTED State
End-to-End Example
Print
Abbreviations
Exit
Speech script
Exercise
Welcome
Audio on/off
Speech script
Content map
Intra-eNB
handover
Inter-eNB
handover
Inter-RAT
handover
X2 interface is relevant here

Random access procedure is involved
Non-LTE access technology is involved
Mobility anchor point is in S-GW
Change
Mobility anchor point is in eNB
Submit
Submit

Please try again.
Show
Show correct
correct solution
solution
solution!
1/1
Legal notice
Page info
After Submit is clicked, correct choices are left in the figure (yellow boxes) and wrong choices removed. After three trials
Show correct solution is displayed.
Page 30
Introduction
Get IP address for UE
LTE attach
ECM-IDLE State
Connection
Management
ECM-CONNECTED State
eNB
MME
EPC
UE
E-UTRAN
Random
access
S-GW
P-GW
2
3
Default EPS bearer

4
End-to-End Example
5
PDN
IMS
Peer
terminal
User data
Signalling
1/1
7
Legal notice
Print
Abbreviations
Exit
Speech script
End-to-End Example
Welcome
Audio on/off
Speech script
Content map
Page info
1. Show figure without user data and signalling connections. When mentioned, highlight other-end terminal.
2. Add left blue callout.
3. Add left green callout and then signalling line to which it points (between UE and eNB).
4. Add signalling lines between eNB and MME and between MME and S-GW/P-GW. Then add user data line between UE and
S-GW/P-GW and lower blue callout.
5. Add upper green callout.
Now let us summarise the procedures taking

place when a user switches on his/her mobile
terminal, connects to the LTE network, and starts
using Voice over IP (VoIP) for communicating
with another user.
When the UE is switched on, this means in
technical terms the LTE attach procedure. Like
in any mobile technology, the first step is to
perform random access in order to set up a
signalling connection over the radio interface.
Unlike in WCDMA/HSPA, the attach procedure by
default includes setting up a user plane
connection to the Evolved Packet Core - the
default EPS bearer connection. Also, an IP
address is allocated to the UE.
The VoIP connection is then set up using Session
Initiation Protocol (SIP) signalling. The SIP
signalling messages are carried transparently
through the Evolved Packet System. The IP
Multimedia Subsystem (IMS) may also interact
with the PDN Gateway via a Policy and Charging
Rules Function (PCRF) node as will be explained
in part two of this course.
If the network is not QoS-aware, the VoIP traffic
is carried within the EPS over the default EPS
bearer. In a QoS-aware network, however, a
separate dedicated EPS bearer could be
established for the high priority VoIP traffic.
When setting up a dedicated EPS bearer, the
signalling is quite similar to the signalling used
when setting up the default EPS bearer. The
main task of the signalling in both cases is to
convey tunnel endpoint identifier (TEID)
information to the network elements terminating
the GTP tunnel in the user plane.
Audio on/off
Speech script
Content map
Speech script
End-to-End Example
Welcome

with another user.
Introduction
ECM-IDLE State
Connection
Management
eNB
MME

EPC
UE
E-UTRAN
ECM-CONNECTED State
S-GW
P-GW
PCRF
PCRF
2
End-to-End Example
1
IMS
First 1 (signalling)
Unlike in WCDMA/HSPA, the attach procedure
by default includes setting up a user plane
then 2 (data)
PDN
Peer
terminal
SIP signalling
User data
6a
Signalling
1/1
7
Legal notice
Print
Abbreviations
Exit
Page info
6. Fade out callouts shown on previous slide. Then add first SIP signalling lines and legend and then add user data line to peer
terminal. 6a. Add PCRF with signalling lines.
7. During this sentence, fade out SIP and PCRF signalling items. Show VoIP traffic (in both directions) via user data line
between UE and peer terminal somehow.

through the Evolved Packet System. Note that
the IP Multimedia Subsystem (IMS) may also
interact with the PDN Gateway via a Policy and
Charging Rules Function (PCRF) node as will be
explained in part two of this course.
Audio on/off
Speech script
Content map
Speech script
End-to-End Example
Welcome

with another user.
Introduction
ECM-IDLE State
Connection
Management
eNB
MME

EPC
TEID
TEID
UE
E-UTRAN
ECM-CONNECTED State
S-GW
P-GW
Unlike in WCDMA/HSPA, the attach procedure by

default includes setting up a user plane
PCRF
PCRF
End-to-End Example
PDN
IMS

through the Evolved Packet System. Note that
the IP Multimedia Subsystem (IMS) may also
interact with the PDN Gateway via a Policy and
Charging Rules Function (PCRF) node as will be
explained in part two of this course.
Peer
terminal
User data
Signalling
1/1
Legal notice
Print
Abbreviations
Exit
Page info
8. Add green line between UE and S-GW/P-GW and green callout. Show VoIP traffic (in both directions) now via green user
data line between UE and peer terminal somehow.
9. Show TEID label in S-GW/P-GW, then turn label into small packet and move via MME to eNB where it vanishes. Then show
TEID label in eNB, then turn label into small packet and move via MME to S-GW/P-GW where it vanishes.


LTE E2e Part 1

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

LTE E2e Part 1

Загружено:

Авторское право:

Доступные форматы

LTE End to End System Part 1 - Procedures

Welcome to the e-learning course LTE

Copyright Nokia Siemens Networks 2007

LTE End to End System Part 1 - Procedures

LTE / SAE Architecture

UTRAN Long Term Evolution (LTE) refers to

Copyright Nokia Siemens Networks 2007

Same page as in LTE radio

LTE End to End System Part 1 - Procedures

LTE / SAE Architecture

LTE End to End System Part 1 - Procedures

LTE / SAE Architecture

LTE End to End System Part 1 - Procedures

Copyright Nokia Siemens Networks 2007

Evolution towards Flat Network Architecture

Closely associated with LTE is the evolution

LTE End to End System Part 1 - Procedures

Evolution towards Flat Network Architecture

Closely associated with LTE is the evolution

In a traditional 3GPP network both the user

Copyright Nokia Siemens Networks 2007

As a next step in the network architecture

LTE End to End System Part 1 - Procedures

Evolution towards Flat Network Architecture

Closely associated with LTE is the evolution

In a traditional 3GPP network both the user

BTS with I-HSPA adapter

As a next step in the network architecture

Copyright Nokia Siemens Networks 2007

The basic idea of the Internet HSPA (I-HSPA)

LTE End to End System Part 1 - Procedures

Evolution towards Flat Network Architecture

Closely associated with LTE is the evolution

In a traditional 3GPP network both the user

As a next step in the network architecture

The basic idea of the Internet HSPA (I-HSPA)

Copyright Nokia Siemens Networks 2007

The LTE network architecture is similar to the

LTE End to End System Part 1 - Procedures

Copyright Nokia Siemens Networks 2007

LTE End to End System Part 1 - Procedures

In the first option, the EPS bearer consists of

Copyright Nokia Siemens Networks 2007

In the second option, the EPS bearer and

LTE End to End System Part 1 - Procedures

In the first option, the EPS bearer consists of

In the second option, the EPS bearer and

EPS bearer for VoIP traffic

Copyright Nokia Siemens Networks 2007

Each EPS bearer is associated with a certain

LTE End to End System Part 1 - Procedures

In the first option, the EPS bearer consists of

In the second option, the EPS bearer and

Each EPS bearer is associated with a certain

Dedicated EPS bearer

Copyright Nokia Siemens Networks 2007

When a UE connects to a packet data

LTE End to End System Part 1 - Procedures

What is Proxy Mobile IP (PMIP)?

PMIP is an IETF solution under development

Unlike Mobile IP, PMIP does not require any

Copyright Nokia Siemens Networks 2007