Mobility Management

and
Connection Management

1 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

 Objectives

At the end of this module, you will be able to

• Remember the NAS related location management
function
• See the relationship between 2G and 3G MM and CM
procedures

2 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

MM and CM Procedures

UE CN
NAS controls
NAS: Connection Management (CC, SS,
SMS, SM)

Mobility Management (MM & PMM)

AS:
RRC RANAP

UTRAN
4 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
 Part I
Mobility Management

5 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

Mobility Management (MM) Procedures
MM procedures

MM connection
MM common MM specific
mgt
procedures procedures
procedures
Network initiated: • MM connection
• normal LUP
• TMSI reallocation establishment
• periodic LUP
• authentication • MM connection
• IMSI attach
• identification release
• MM information
• abort (MM
connection
established)
UE initiated:
• IMSI detach

7 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

cket Switched Mobility Management Procedures
GMM procedures

GMM common GMM specific

procedures procedures
Network initiated:
Network initiated: • GPRS detach and
• P-TMSI (re-) allocation combined GPRS detach
• GPRS authentication and UE initiated:
ciphering • GPRS attach and
• GPRS identification combined GPRS attach
• GPRS information • GPRS detach and
combined GPRS detach
• normal routing area
update and combined
routing area update
• periodic routing area
update
• service request

9 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

PS Mobility Management States

3G-SGSN only:
S-RNC Relocation

PS Signalling Connection
Establishment
PMM-CONNECTED PMM-IDLE
PS Signalling Connection
Release
GPRS Attach

GPRS Detach Implicit GPRS Detach

GPRS Attach Reject PMM-DETACHED
(SGSN: MS Reachable
RAU Reject Timer expires)

(adopted from TS 23.060 V3.13.

11 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
Packet Data Protocol States

UE 3G-SGSN GGSN

Activate PDP Context

INACTIVE ACTIVE

Deactivate PDP Context

or
MM context change to PMM-DETACHED
(adopted from TS 23.060 V3.13.
13 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
Mobility Management Messages
Miscellaneous

Registration Network initiated:

• MM INFORMATION
Security • MM STATUS
UE initiated:
Network initiated:
• LOCATION UPDATING
• MM STATUS
ACCEPT • MM NULL
• LOCATION UPDATING
REJECT Network initiated:
UE initiated:
• IMSI DETACH INDICATION
• AUTHENTICATION REJECT Connection
• AUTHENTICATION REQUEST
• LOCATION UPDATING • IDENTITY REQUEST Management
REQUEST • TMSI REALLOCATION
COMMAND
UE initiated:
• AUTHENTICATION
Network initiated:
RESPONSE
• CM SERVICE ACCEPT
• IDENTITY RESPONSE
• CM SERVICE REJECT
• TMSI REALLOCATION
• ABORT
COMPLETE
UE initiated:
• CM SERVICE REQUEST
• CM RE-ESTABLISHMENT
REQUEST
• CM SERVICE ABORT

16 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

GPRS Mobility Management Messages
Security
Registration

Miscellaneous
Network initiated:
Network initiated: • AUTHENTICATION AND Network initiated:
• ATTACH ACCEPT CIPHERING REQUEST • GMM STATUS
• ATTACH REJECT • AUTHENTICATION AND • GMM INFORMATION
• DETACH REQUEST CIPHERING REJECT UE initiated:
• ROUTING AREA UPDATE • IDENTITY REQUEST
• P-TMSI REALLOCATION
• GMM STATUS
ACCEPT
• ROUTING AREA UPDATE COMMAND
REJECT • SERVICE ACCEPT
UE initiated: • SERVICE REJECT
• ATTACH REQUEST UE initiated:
• ATTACH COMPLETE • AUTHENTICATION AND
• DETACH ACCEPT CIPHERING RESPONSE
• DETACH REQUEST • AUTHENTICATION AND
• ROUTING AREA UPDATE CIPHERING FAILURE
REQUEST • IDENTITY RESPONSE
• ROUTING AREA UPDATE • P-TMSI REALLOCATION
COMPLETE COMPLETE
• SERVICE REQUEST

17 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

etwork Mode of Operation and UE Modes

S
Iu-C 3G-MSC/VLR
UE Gs
UTRAN
Iu-P
S

3G-SGSN
UE modes:
• CS mode
• PS mode
NMO I: Gs interface is present
• CS/PS
NMO II: Gs interface is not present
mode

19 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

 Location Area Concepts
Location Area LAI = MCC MNC LAC

LA2
LA1

Routing Area RAI = MCC MNC LAC RAC

RA3
RA2 LA2
RA1
RA4

Service Area SAI = MCC MNC LAC SAC

SA7
SA1 SA4 LA2 SA8
SA3
LA1
SA2 SA5 SA6

21 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

Location Update Types
normal location LA1 / RA 1
update
LA 2 / RA 2

last interaction
with network
periodic location Periodic timer
set Periodic timer periodic update
update expires initiated by UE
timer set
time

IMSI attach I am off

Ind i cation
I D e tach
IMS uest
R e q
n U pdate
o 3G-MSC/VLR
Locati
I am on
again
23 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
riodic Location Update Timers and the Attach Flag
UTRAN
System Information ( )

CS domain RNC
UE SIB1PS domain
Node B

• T3212 IE: CN domain specific• RAC

GSM-MAP NAS system
• ATT-flag • NMO

ATTACH ACCEPT ( ) / ROUTING AREA UPDATE ACCEPT ( )

T3312 3G-SGSN
UE
(default 54 min)

25 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

Location Update Status
CS Mode PS Mode
U1 Updated GU1
Last LU and registration Last RAU and
successful registration
USIM has successful
• valid LAI • CK, IK, CKSN USIM has
USIM
operator XYZ
• possibly TMSI • valid RAI
• possibly P-TMSI
U2 Not Updated GU2
Last LU failed Last RAU failed
USIM USIM has no valid location USIM has no valid
information and key are routing
deleted. area information and
key are deleted.
U3 Roaming Not Allowed GU3
Last LU successful, but Last RAU successful,
registration rejected. but
USIM may have registration rejected.
• valid LAI • CK, IK, CKSN USIM USIM may
• possibly TMSI have
27 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
• valid RAI
 Location Update Procedure
Location Updating Request ( )

UE
3G-MSC/VLR
Mobility management 0101: mobility management message
protocol discriminator
0000 Standard format of
Skip Indicator
every NAS message
Location Updating xx001000: location updating request
Request message type
Normal LU/ periodic LU / IMSI attach
ocation updating type
Follow on request pending: yes / no
Ciphering key
sequence number
Location area MCC + MNC + LAC
identification
for GSM MSs: revision level, controlled early classmark
Mobile station sending option, A5/1 support, RF power capability.
classmark
TMSI, if not available => IMSI
Mobile identity
See MS classmark; LCS VA capability, SoLSA support, A5/2 suppo
OP
Mobile station A5/3 support, CM Service Prompt support, etc.
classmark for UMTS
29 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
Location Update Procedure
Location Updating Accept ( )

UE
3G-MSC/VLR
Mobility management
0101: mobility management message
protocol discriminator
Skip Indicator 0000
Location Updating
xx000010: location updating accept
Accept message type
Location area
MCC + MNC + LAC
identification
OP
Mobile Identity TMSI, if not available => IMSI
Follow on proceed OP
OP
CTS permission the MS is allowed to use GSM-Cordless Telephony System in this
OP
Equivalent PLMNs number of PLMNs and their MCC and MNC.

30 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

Location Update Procedure
3G-MSC/VLR
UE
Start T3210
LOCATION UPDATING REQUEST ( )

(Identification Procedure)

Authentication Procedure
T3210
= 20 s Stop T3210 Security Mode Procedure
U1
LOCATION UPDATING ACCEPT ( )

e.g. new TMSI

follow on proceed TMSI confirmation
M message pending T3250 (= 12 s)
TMSI REALLOCATION COMPLETE (
T3240 (= 10 s) )

(*)

(*) Prolonged RR connection T3255

(e.g. if pending request in Location Updating
32 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
Location Update Procedure
UE
Start T3210
LOCATION UPDATING REQUEST ( )
Authentication Procedure
Stop T3210 Security Mode Procedure 3G-MSC/VLR
T3210 U3
= 20 s LOCATION UPDATING REJECT ( )

Wait for RR connection to be release

T3240
(= 10 s)

U1, if
T3210 expiry • LAI on USIM equal to BCCH, and
15 s • attempt counter < 4, and
T3210 expiry • user status was U1
Start T3211
U2, if
U1, if UE in
T3211 expiry
LU Req. no new LA • LAI on USIM not equal to BCCH
LU Req. time
• attempt counter  4, or
• user status was not U1
34 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
 IMSI Detach
Abnormal Situation:
UE cannot establish
RR Connection
 Abort IMSI Detach

UE
RR Connection Establishment
Start T3220
IMSI DETACH INDICATION ( )
3G-MSC/VLR
Stop T3220
T3220 RR Connection Release
=5s • no response
• release of ongoing
MM connections
• release of
T3220 Expiry RR connection
UE aborts internally
its RR sub-layer
36 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
 GPRS Attach
UE
Start T3310
ATTACH REQUEST ( )

(Identification Procedure) 3G-SGSN

T3310 Stop T3310 Authentication and Ciphering Procedure
= 15 s GU1
ATTACH ACCEPT ( )
e.g. new TMSI
or P-TMSI (P-)TMSI confirmation
T3350 (= 6 s)
ATTACH COMPLETE ( )

T3310 expiry
ATTACH T3310 expiry T3310 expiry T3310 expiry
T3311 expiry T3302 expiry
Req. Start T3311
ATTACH Req.Start T3311 Start T3302 ATTACH Req.

time
15 s T3302 (default 12 min.)
GPRS attach request counter =GPRS
1 attach request counter  5
 mobility status = GU2
38 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
 UE Initiated GPRS Detach
normal detach IE Detach type:
• GPRS detach / IMSI detach / combined GPRS/IMSI detach
• normal detach / power switch off

UE 3G-SGSN
Start T3321
DETACH REQUEST ( )

(Identification Procedure)

T3321 Stop T3321 Authentication and Ciphering Procedure

= 15 s
DETACH ACCEPT ( )

Expiry: retransmission of DETACH REQUEST (up to 4 times)

Releases all
power switch UE 3G-SGSN
resources on
off lower layers
DETACH REQUEST ( )

40 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

Network Initiated GPRS Detach
re-attach required UE 3G-SGSN
Start T3322
DETACH REQUEST ( )
terminate all
logical links and (Identification Procedure)
PDP Contexts
Authentication and Ciphering Procedure T3322
Stop T3322 =6s
re-start all
logical links and DETACH ACCEPT ( )
PDP Contexts ATTACH REQUEST ( )

IMSI detach UE DETACH REQUEST ( ) 3G-SGSN

U2 DETACH ACCEPT ( )
ROUTING AREA UPDATE REQUEST ( )
combined RA/LA updating with IMSI attach

re-attach not
required
See re-attach required, but with no message following the DETACH ACCEPT.
42 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
 Routing Area Update
UE
Start T3330
ROUTING AREA UPDATE REQUEST ( )

(Identification Procedure) 3G-SGSN

T3330 Stop T3330 Authentication and Ciphering Procedure
= 15 s GU1
ROUTING AREA UPDATE ACCEPT ( )
e.g. new TMSI and/or P-TMSI
or Receive N-PDU number needed
T3350 (= 6 s)
ROUTING AREA UPDATE COMPLETE ( )

T3330 expiry
ATTACH T3330 expiry T3330 expiry T3330 expiry
T3311 expiry T3302 expiry
Req. Start T3311
ATTACH Req.Start T3311 Start T3302 ATTACH Req.

time
15 s T3302 (default 12 min.)
GPRS attach request counter =GPRS
1 attach request counter  5
 mobility status = GU2
44 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
The Service Request Procedure
UE
Start T3317
SERVICE REQUEST ( )
Authentication and Ciphering Procedure 3G-SGSN
Stop T3317
T3317 SERVICE ACCEPT ( )
= 10 s
Radio Bearer Setup

UE 3G-SGSN
SERVICE REQUEST ( )
Authentication and Ciphering Procedure

SERVICE REJECT ( )
I abort
T3317 expiry the
procedur
e

46 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

The Service Request Procedure
UE 3G-
SERVICE REQUEST ( )
SGSN

Protocol discriminator
Skip indicator
Service Request
Ciphering key
sequence number 000: Signalling
Service Type 001: Data
010: Paging Response
P-TMSI
OP
PDP context status NSAPI x: 0 = corresponding PDP context is inactive
1 = corresponding PDP context is inactive
X = 0 .. 15, (0..4 are coded as inactive)

47 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

okia Parameters for NAS Mobility Management
RAN 1 supports only NMO II, where the Gs interface is not present. Consequently,
procedures such as combined GPRS attach is not supported.

• RNC: PS_NMO
In Operation Mode I it is possible to have combined CS and PS side paging via SGSN.
In Operation Mode II the combined paging procedure is not possible (and neither are
combined attach procedures). Used only for the PS domain. NMO is part of PS CN
domain specific NAS System information in SIB1.
0 (Network Mode of Operation I), 1 (Network Mode of Operation II), default: 1
• RNC: CSAttachDetachAllowed
Defines whether IMSI attach and detach are allowed or not. Given only for CS
domain. This is part of CS CN domain specific NAS System information in SIB1.
0 (UE shall not apply these procedures), 1 (MSs shall apply these procedures);
default value: 1
• RNC: CNDomainIndicator
Indicates the CN domain from which the message originates, or to which the
message will be sent. This parameter is also part of System Information Block 1.
0 (Circuit Switched), 1 (Packet Switched)

49 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

okia Parameters for NAS Mobility Management
• RNC: CS_T3212
The timeout value, in decihours (6 min), for periodic location
updating. Given only for CS domain. (SIB1). The value 0 is
used for an infinite timeout value.
[0 ... 255] decihours, step 1 decihours; default value: 0
decihours

• RNC: PS_T3313

50 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

 Part II
Connection Management

52 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer

UE Initiated PDP Context Activation
3G-
SGSN
UE GGSN
ACTIVATE PDP CONTEXT REQUEST ( )
CREATE PDP CONTEXT REQUEST

CREATE PDP CONTEXT RESPONSE

T3380 Radio Bearer Setup
= 30 s UPDATE PDP CONTEXT REQUEST
UPDATE PDP CONTEXT RESPONSE
ACTIVATE PDP CONTEXT ACCEPT ( )

T3380 expiry
T3330 expiry T3211 expiry
T3211 expiry
(*) (*) (*) (*)

time
UE aborts
counter = 1 counter = 4
procedure
(*) := ACTIVATE PDP CONTEXT REQUES
54 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
PDP Context Activation
UE 3G-
ACTIVATE PDP CONTEXT REQUEST ( )
SGSN

Protocol discriminator 1010: GPRS session management messages

Transaction indicator
Activate PDP context
01000001: Activate PDP context request
request message ID
Requested NSAPI • Delay class
• Reliability class
Requested LLC SAPI • Precedence class
Requested QoS • Mean and peak
throughput class
Requested PDP address • Maximum UL/DL bit rate
• Transfer delay
Access Point Name OP
• Guaranteed UL/DL bit
Protocol configuration rate
OP
options • Residual BER
56 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer • Delivery order
 PDP Context Activation
UE 3G-
ACTIVATE PDP CONTEXT ACCEPT ( )
SGSN

Protocol discriminator 1010: GPRS session management messages

Transaction indicator
Activate PDP context
request message ID 01000010: Activate PDP context accept

Negotiated LLC SAPI

Not required in UMTS, but transmitted to
Negotiated QoS
support UMTS – GPRS cell reselection
Radio priority
Spare half octet
PDP address OP
Protocol configuration
OP
options
Packet Flow IdentifierOP
57 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
 To which PDP
Secondary PDP Contexts context if PDUs
have the same PDP
address?

GGSN
PDN
UE

Traffic Flow Template (TFT) attributes PDP PDU

• Source Address and Subnet Mask
• Protocol Number (IPv4) / Next Header (IPv6)
• Destination Port Range
• Source Port Range
• IPSec Security Parameter Index (SPI)
• Type of Service (TOS) (IPv4) / Traffic class (IPv6) and Mask
GGSN
• Flow Label (IPv6)
UE

ACTIVATE SECONDARY PDP CONTEXT REQUEST ( )

CREATE PDP CONTEXT REQUEST
T3380 CREATE PDP CONTEXT RESPONSE
ACTIVATE SECONDARY PDP CONTEXT ACCEPT ( )
= 30 s
SGSN
60 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer
Call Setup Flow
• Call control protocol
mandatory
discriminator
IEs
• Transaction identifier
• Setup type message
• Bearer capability 1
e.g. radio channel requirement,
speech version indication,
information transfer capability,
modem type, etc.
UE • Called party BCD number 3G-MSC/VLR
SETUP ( )

CALL PROCEEDING

ALERTING

CONNECT

CONNECT ACKNOWLEDGE

62 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer