Mobility Management (MM)

Different MM schemes for CS and PS mode

MM states
t t
Involved protocols
Procedures
P
d

References:
Kaaranen, Ahtiainen, Laitinen, Naghian, Niemi: UMTS Networks Architecture, Mobility
and Services. Wiley 2001, Ch. 5.2 (MM states) and 10.3 (MM procedures)
3G 23.060 GPRS Service Description
3G 24.007 Mobile radio interface signaling layer 3, General aspects
UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

Mobility Management (MM) Basics

Mobility Management
covers all procedures
procedures, methods and identities
required to maintain knowledge about the UEs locations when it is
moving in the network
Involved entities
UE
CN

SGSN (PS mode, transitions between PMM states)

MSC/VLR (CS mode, transitions between MM states)
HLR (in
(i home
h
network)
t
k)

in MM/PMM connected mode

RNC (cell and/or URA updates)

GGSN/GMSC

in case of roaming
visited PLMN

UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

CS Mobility Management States

MM in CS mode is highly related to connection management
no active call
(nor signaling)

call completion
MMIdle

call setup or
LA update

active call
(or signaling)
MMMM
Connecte
d
cell known

LA known
(paging
(pag
g possible)
po b )

IMSI detach

IMSI attach or
LA update (UE is switched on)

MMD t h d
Detached
LA unknown
(no paging)
UE switched
it h d off
ff
MM state is maintained in UE and MSC/VLR
UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

PS (GPRS) Mobility Management States

M S M M S tates

3G -S G S N M M S tates

PM M DET ACHED

GPRS detach
P S D etac h
P S A ttach

GPRS attach
P S S ignalling
C onn ection R ele ase
P M M -ID L E
S M -A C T IV E o r
IN A C T IV E

P S S ignalling
C onn ection E s ta blish

Paging only
(no signaling
connection
between MS
and
d SGSN)

PM MDET ACHED

D etac h,
P S A ttach R eject,
R A U R eje ct

PM MC O N N E C TE D
S M -A C T IV E o r
IN A C T IV E

Signaling
g
g
connection
between
MS and SGSN
(addressing
by U-RNTI)

U-RNTI:
U
RNTI: UTRAN - Radio Network Temporary Identity
Source: 3GPP 23.060-4.1.0
UMTS Networks

P S D etac h
P S A ttach
P S S ignalling
C onn ection R ele ase
P M M -ID L E

D etac h,
P S A ttach R eject,
R A U R eje ct

PM M C O N N EC TED

S M -A C T IV E o r
S M -A C T IV E o r
P S S ignalling
IN A C T IV E
IN A C T IV E
C onn ection E s ta blish

S ervin g R N C
reloc ation

PS Mobility Management (PMM) is

independent of Session Management (SM),
(SM)
e.g. availability of IP address & traffic activity
PMM is independent of the number and state of PDP
contexts for the subscriber
In both the PMM-IDLE and the PMM-CONNECTED states,
session management may or may not have activated a PDP
context (assigned a dynamic IP address)

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

Signaling Connection
No

signaling connection exists (MM/PMM-IDLE state)

UE has no relation to UTRAN, only to CN
no data transfer
paging identification by IMSI, TMSI, P-TMSI

Signaling connection exists (MM/PMM-CONNECTED state)

Addressing
g byy U-RNTI
UE position can be known on different levels:
- URA level (UTRAN registration area): URA is a specified set of
cells, which can be identified on the broadcast channel (BCCH)
- Cell level: Different channel types can be used for data transfer:
- Common transport channels (RACH, FACH, CPCH, DSCH)
- Dedicated transport channels (DCH)
Source: 3GPP 25.301-4.1.0, ch 6.2
UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

Relations between CM/SM, MM/PMM and RRC

States
CM/SM state(s)
Subscrip
Subscription
(UE-SGSN-GGSN)
Core
Network

UTRAN

PDCP
address

inactive

active

detached

idle

connected

Signaling
connection
(UE-SGSN)

none

yes

RRC state
(UE-RNC)

idle

connected

MM/PMM state
(UE, SGSN, HLR)

(cell_DCH, cell_FACH,
cell_PCH, or URA_PCH)

Paging using
TMSI/P-TMSI
UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

Addressing
using RNTI
6

PS Mobility Management States

PMM-DETACHED State:
No communication between the MS and the SGSN
MS and SGSN hold no valid location or routing information for the MS
MS MM state machine does not react to system information related to
the SGSN
MS is not reachable by the PLMN, as the MS location is not known to
the SGSN
MM context establishment:
GPRS-attach procedure: establish MM contexts in the MS and the SGSN
When PS signalling connection is established between the MS and
the SGSN for performing the GPRS attach, the state changes to
PMM-CONNECTED in the SGSN and in the MS
The PS signalling connection is made up of two parts: an RRC
connection and an Iu connection

UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

7 o

PS Mobility Management States

PMM-CONNECTED State:

MS location is known in the SGSN with an accuracy of a serving RNC

Location of the MS is tracked by the serving RNC
MS performs the routing area update procedure when RAI changes
A PS signaling connection is established between the MS and the SGSN

R l
Release
off signaling
i
li connection
ti (move
(
to
t PMM-IDLE
PMM IDLE state):
t t )

In SGSN: PS signalling connection release or failed downlink transfer with cause

"IMSI unknown in RNC" changes the state to PMM-IDLE
In MS: enter the PMM-IDLE state when its PS signaling connection to the SGSN
has been released or broken (release or failure is explicitly indicated by the
RNC to the MS or detected by the MS > RRC connection failure)
Si
Signaling
li connection
ti is
i also
l released
l
d if a URA update
d t fails
f il because
b
off "RRC
connection not established", or if the URA update timer expires while the MS is
out of coverage
SGSN may decide to release the PS signaling connection after a signaling
procedure (e.g. routing area update)

MM context release:

GPRS detach changes the state to PMM-DETACHED

UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

8 o

PS Mobility Management States

PMM-IDLE State:
MS location is known in the SGSN with an accuracy of a routing area
Paging is needed in order
o de to reach
each the MS,
MS e.g.
e g for
fo signalling
MS and SGSN have established MM contexts
MS p
performs a routing
g area update
p
if the RA changes
g
(signaling towards the HLR is needed if the (new) SGSN does not have
an MM context for this MS)
Establishment of signaling connection (move to PMM-CONNECTED state):
MS and SGSN enter the PMM-CONNECTED state when the PS signalling
connection is established between the MS and the SGSN
MM context release:
GPRS detach procedure changes the state to PMM-DETACHED
SGSN may perform
f
an implicit
i li it GPRS detach
d t h any time
ti
after
ft th
the MS
reachable timer expiry; the MS's MM context is deleted, preferably after
a certain (implementation dependent) time; the HLR may be informed
about the deletion
UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

9 o

Mobility Management
Involved Protocols (PS mode)
Protocols used by MM procedures
Uu: RRC protocol
Iu: RANAP protocol
Gr ((SGSN and HLR):
) MAP protocol
p
Gf (SGSN and EIR): MAP protocol
Gs (SGSN and VLR): BSSAP+ protocol

Source: 3GPP 23.060-4.1.0, Ch 6.4

UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

10 o

Mobility Management Procedures

Connected state
Cell
C ll update
d
(PS mode):
d ) UE-UTRAN
UE UTRAN interaction
i
i
URA update (PS mode): UE-UTRAN interaction
Idle state
RA Update (PS mode): UE-CN interaction (transparent to UTRAN)
LA U
Update
d t (CS mode):
d ) UE-CN
UE CN iinteraction
t
ti (t
(transparentt tto UTRAN)

See also Kaaranen, ch 10.3

UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

11

Cell Update (PS)

UE

RNC

reason for
cell update

RRC: cell update

RRC: cell update confirm

exchange
g of RRC msgs
g

UMTS Networks

PS mode:
d
-> explicit cell update procedure
Reasons for cell update
cell reselection
periodic cell update
uplink data transmission
paging
g g response
re-entered service area
radio link failure
unrecoverable RLC error

CS mode:
continuous exchange of cell
information
o at o du
during
g call
ca (or
(o transaction)
t a sact o )

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

12

URA Update (PS)

UE

RNC

reason for
URA update

RRC: URA update

PS mode:
->
> explicit URA update procedure
Reasons for URA update
p
URA identity changes
periodic URA update

RRC: URA update confirm

exchange
g of RRC msgs
g

UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

13

RA
A Upd
date (w
with c
chang
ge of S
SGSN
N)
UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

14

RA Up
R
pdate (deta
ails)

new
SRNS

MS

new
3G-SGSN

old
SRNS

1. Routeing
g Area Update
p
Request
q

old
3G-SGSN

GGSN

new
MSC/VLR

HLR

old
MSC/VLR

2 SGSN C
2.
Context
t tR
Requestt

2a. SRNS Context Request

C1

2a. SRNS Context Response

2. SGSN Context Response
3. Security Functions
4. SGSN Context Ack
5. SRNS Data Forward Command
6. Forward Packets
7. Forward Packets
C2
8. Update PDP Context Request

Source
e: 3GPP 23.0
060

8. Update PDP Context Response

UMTS Networks

9 Update Location
9.
10a. Iu Release Command

10. Cancel Location

10a Iu Release Complete

10a.
10. Cancel Location Ack
Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

15 o

new
3G-SGSN

old
SRNS

old
3G-SGSN

GGSN

new
MSC/VLR

HLR

old
MSC/VLR

11 Insert
11.
I t Subscriber
S b ib Data
Dt
11. Insert Subscriber Data Ack
12. Update
p
Location Ack
13. Location Update Request
14a. Update Location
14b Cancel Location
14b.

Combineed LA/RA up
pdate

Reaso
ons for R
RA update
es
En
ntering a new RA
A
Exxpiration of period
dic RA
timer
...

RA Up
R
pdate (deta
ails)

MS

new
SRNS

14c. Cancel Location Ack

14d. Insert Subscriber Data
14e. Insert Subscriber Data Ack
14f. Update Location Ack
15. Location Update Accept
C2

16. Routeing Area Update Accept

C3
17. Routeing Area Update Complete
18. TMSI Reallocation Complete
UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

16 o

Routeing Area Update Procedure Details (1)

A routeing area update takes place when
an attached MS detects that it has entered a new RA
when the periodic RA update timer has expired
when RRC connection is released with cause "Directed
Signalling connection re-establishment"
when
h the
h MS has
h to indicate
d
new access capabilities
bl
to
the network
The SGSN detects that it is an intra-SGSN routeing area
update by noticing that it also handles the old RA. In this
case, the SGSN has the necessary information about the
MS and there is no need to inform
f
the GGSNs or the HLR
about the new MS location. A periodic RA update is
always an intra-SGSN routeing area update.
In Iu mode, an RA update is either an intra-SGSN or
inter-SGSN RA update, either combined RA / LA update or
only RA update, either initiated by an MS in
PMM-CONNECTED (only valid after a Serving RNS
Relocation Procedure, see clause 6.9.2.2) or in PMM-IDLE
state. All the RA update cases are contained in the
procedure illustrated in the figure.
1) The RRC connection is established, if not already done.
The MS sends a Routeing Area Update Request message
(P-TMSI, old RAI, old P-TMSI Signature, Update Type,
follow on request, etc.) to the new SGSN. Update Type
shall indicate:
RA Update if the RA Update is triggered by a change
of RA;
Periodic RA Update if the RA update is triggered by
p y of the Periodic RA Update
p
timer;;
the expiry
Combined RA/LA Update if the MS is also IMSIattached
UMTS Networks

2) If the RA update is an Inter-SGSN Routeing area

update and if the MS was in PMM-IDLE state, the new

SGSN sends an SGSN Context Request message (old
P-TMSI, old RAI, old P-TMSI Signature) to the old SGSN
to get the MM and PDP contexts for the MS. The old
SGSN validates
lid
the
h old
ld P-TMSI
P TMSI Si
Signature and
d responds
d
with an appropriate error cause if it does not match the
value stored in the old SGSN. This should initiate the
security functions in the new SGSN. If the security
functions authenticate the MS correctly,
y, the new SGSN
shall send an SGSN Context Request (IMSI, old RAI, MS
Validated) message to the old SGSN. MS Validated
indicates that the new SGSN has authenticated the MS. If
the old P-TMSI Signature was valid or if the new SGSN
indicates that it has authenticated the MS
MS, the old SGSN
responds with SGSN Context Response (Cause, IMSI, MM
Context, PDP contexts). If the MS is not known in the old
SGSN, the old SGSN responds with an appropriate error
cause. The old SGSN starts a timer. The new SGSN shall
i
ignore
the
th MS Network
N t
kC
Capability
bilit contained
t i d iin MM
Context of SGSN Context Response only when it has
previously received an MS Network Capability in the
Routeing Area Request.

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

17 o

Routeing Area Update Procedure Details (2)

2a) If the MS is PMM-CONNECTED
PMM CONNECTED state in the old
3G-SGSN or, in case of an intra-SGSN RA update, if the
MS is in the PMM-CONNECTED state and the RAU was
received over another Iu connection than the established
one, the old SGSN sends an SRNS Context Request (IMSI)
message to the old SRNS to retrieve the sequence
numbers for the PDP context for inclusion in the SGSN
Context Response message from the SRNS. Upon
reception of this message, the SRNS buffers and stops
sending downlink PDUs to the MS and returns an SRNS
Context Response (IMSI, GTP-SNDs, GTP-SNUs,
PDCP-SNUs) message. The SRNS shall include for each
PDP context the next in-sequence GTP sequence number
to be sent to the MS and the GTP sequence number of
the next uplink PDU to be tunnelled to the GGSN. For
each active PDP context using acknowledged mode, the
SRNS also includes the uplink PDCP sequence number
(PDCP-SNU). PDCP-SNU shall be the next in-sequence
PDCP sequence number expected from the MS (per each
active radio bearer)
bearer).
3) Security functions may be executed. These procedures
are defined in clause "Security Function". If the security
functions do not authenticate the MS correctly, the
routeing area update shall be rejected, and the new SGSN
shall send a reject indication to the old SGSN. The old
SGSN shall continue as if the SGSN Context Request was
never received.

UMTS Networks

4) If the RA update is an Inter-SGSN

Inter SGSN Routeing area
update, the new SGSN sends an SGSN Context
Acknowledge message to the old SGSN. The old SGSN
marks in its context that the MSC/VLR association and the
information in the GGSNs and the HLR are invalid. This
triggers the MSC/VLR
MSC/VLR, the GGSNs
GGSNs, and the HLR to be
updated if the MS initiates a routeing area update
procedure back to the old SGSN before completing the
ongoing routeing area update procedure.
5) If the MS is in PMM-CONNECTED state in the old 3GSGSN or, in case of an intra-SGSN RA update, if the MS is
PMM connected and the RAU was received over another
Iu connection than the established one, the old 3G-SGSN
sends an SRNS Data Forward Command (RAB ID,
ID
Transport Layer Address, Iu Transport Association)
message to the SRNS. Upon receipt of the SRNS Data
Forward Command message from the 3G-SGSN, the SRNS
shall start the data-forwarding timer.
6) The SRNS shall start tunnelling the partly transmitted
and the transmitted but not acknowledged PDCP-PDUs
together with the PDCP downlink sequence number, and
start
t td
duplicating
li ti and
d tunnelling
t
lli the
th buffered
b ff d GTP PDUs
PDU to
t
the old 3G-SGSN.
7) If the RA update is an Inter-SGSN RA Update, the old
3G SGSN tunnels the GTP PDUs to the new 3G-SGSN
3G-SGSN
3G SGSN.

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

18 o

Routeing Area Update Procedure Details (3)

8) If the RA update is an Inter-SGSN
Inter SGSN RA Update and if
the MS wasnot in PMM-CONNECTED state in the new 3GSGSN, the new SGSN sends Update PDP Context Request
(new SGSN Address, QoS Negotiated, Tunnel Endpoint
Identifier,) to the GGSNs concerned. The GGSNs update
their PDP context fields and return an Update PDP
Context Response (Tunnel Endpoint Identifier). Note: If
the RA update is an Inter-SGSN routeing area update
initiated by an MS in PMM-CONNECTED state in the new
3G-SGSN, the Update PDP Context Request message is
sent as described in subclause "Serving RNS Relocation
P
Procedures".
d
"
9) If the RA update is an Inter-SGSN RA Update, the new
SGSN informs the HLR of the change of SGSN by sending
Update Location (SGSN Number, SGSN Address, IMSI) to
the HLR.
HLR
10) If the RA update is an nter-SGSN RA Update, the HLR
sends Cancel Location (IMSI, Cancellation Type) to the
old SGSN with Cancellation Type set to Update Procedure.
If the timer described in step 2 is not running,
running the old
SGSN removes the MM context. Otherwise, the contexts
are removed only when the timer expires. It also ensures
that the MM context is kept in the old SGSN in case the
MS initiates another inter SGSN routeing area update
before completing
p
g the ongoing
g g routeing
g area update
p
to
the new SGSN. The old SGSN acknowledges with Cancel
Location Ack (IMSI).
10a) On receipt of Cancel Location, if the MS is
PMM-CONNECTED in the old 3G-SGSN,, the old 3G-SGSN
sends an Iu Release Command message to the old SRNC.
When the data-forwarding timer has expired, the SRNS
responds with an Iu Release Complete message.
UMTS Networks

11) If the RA update is an nter-SGSN

nter SGSN RA Update, the HLR
sends Insert Subscriber Data (IMSI, subscription data) to
the new SGSN. The new SGSN validates the MS's
presence in the (new) RA. If due to regional subscription
restrictions the MS cannot attach to the RA, the SGSN
rejects the Routeing Area Update Request with an
appropriate cause, and may return an Insert Subscriber
Data Ack (IMSI, SGSN Area Restricted) message to the
HLR. If all checks are successful, the SGSN constructs an
MM context for the MS and returns an Insert Subscriber
Data Ack (IMSI) message to the HLR.
12) If the RA update is an Inter-SGSN RA Update, the
HLR acknowledges the Update Location by sending
Update Location Ack (IMSI) to the new SGSN.
13) If Update Type indicates combined RA/LA update with
IMSI attach requested, or if the LA changed with the
routeing area update, the association has to be
established, and the new SGSN sends a Location Update
Request (new LAI, IMSI, SGSN Number, Location Update
Type) to the VLR. Location Update Type shall indicate
IMSI attach if Update Type in step 1 indicated combined
RA / LA update with ISI attach requested. Otherwise,
Location Update Type shall indicate normal location
update.
p
The VLR number is translated from the RAI via a
table in the SGSN. The SGSN starts the location update
procedure towards the new MSC/VLR upon receipt of the
first Insert Subscriber Data message from the HLR in
step 8). The VLR creates or updates the association with
the SGSN by storing SGSN Number.

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

19 o

Routeing Area Update Procedure Details (4)

14) If the subscriber data in the VLR is marked as not
confirmed by the HLR, the new VLR informs the HLR. The
HLR cancels the old VLR and inserts subscriber data in
the new VLR (this signalling is not modified from existing
GSM signalling and is included here for illustrative
purposes):
a) The new VLR sends an Update Location (new VLR) to
the HLR.
b) The HLR cancels the data in the old VLR by sending
Cancel Location (IMSI) to the old VLR.
c) The old VLR acknowledges with Cancel Location Ack
(IMSI).
d) The HLR sends Insert Subscriber Data (IMSI, GSM
subscriber data) to the new VLR.
e) The new VLR acknowledges with Insert Subscriber
Data Ack (IMSI)
(IMSI).
f) The HLR responds with Update Location Ack (IMSI) to
the new VLR.

17) The MS confirms the reallocation of the TMSIs by

returning a Routeing Area Update Complete message to
the SGSN.
18) The new SGSN sends a TMSI Reallocation Complete
message to the new VLR if the MS confirms the VLR
TMSI.
NOTE 3: Steps 14, 15, and 18 are performed only if
step
t 12 is
i performed.
f
d

15)) The new VLR allocates a new TMSI and responds

p
with
Location Update Accept (VLR TMSI) to the SGSN. VLR
TMSI is optional if the VLR has not changed.
16) The new SGSN validates the MS's presence in the
new RA.
RA If due to roaming restrictions the MS cannot
attach to the SGSN, or if subscription checking fails, the
SGSN rejects the routeing area update with an
appropriate cause. If all checks are successful, the new
SGSN establishes MM context for the MS. The new SGSN
responds
p
to the MS with Routeing
g Area Update
p
Accept
p
(P-TMSI, VLR TMSI, P-TMSI Signature).

UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

20 o

LA
A Upd
date (C
CS)
UMTS Networks

Andreas Mitschele-Thiel, Jens Mckenheim

12-Nov-08

21