s08 3g Rpls2_v2-0 Mm and Cm

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

1/34

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

Mobility Managementand

Connection Management

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

2/34


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

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

3/34


MM and CM Procedures

NAS controls

RRC

NAS:

Mobility Management (MM PMM)

UE CN

AS:

UTRAN

RANAP

Connection Management (CC, SS, SMS, SM)

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

4/34


Part IMobility Management

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

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

Mobility Management (MM) ProceduresMM procedures

MM commonprocedures

MM specificprocedures

MM connection mgtprocedures

Network initiated:

TMSI reallocation

authentication

identification

MM information

abort (MM connection established)

UE initiated:

IMSI detach

normal LUP

periodic LUP

IMSI attach

MM connection establishment

MM connection release

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm


Packet Switched Mobility Management ProceduresGMM procedures

GMM commonprocedures

GMM specificprocedures

Network initiated:

P-TMSI (re-) allocation

GPRS authentication and ciphering

GPRS identification

GPRS information

Network initiated:

GPRS detach and combined GPRS detach

UE initiated:

GPRS attach and combined GPRS attach

GPRS detach and combined GPRS detach

normal routing area update and combined routing

area update

periodic routing area update

service request

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm


PS Mobility Management States

PMM-DETACHED

PMM-CONNECTED PMM-IDLE

GPRS DetachGPRS Attach Reject

RAU Reject

GPRS Attach

Implicit GPRS Detach

(SGSN: MS Reachable

Timer expires)

PS Signalling Connection

Release

PS Signalling Connection

Establishment

3G-SGSN only:

S-RNC Relocation

(adopted from TS 23.060 V3.13.0)

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

8/34


Packet Data Protocol States

INACTIVE ACTIVE

(adopted from TS 23.060 V3.13.0)

Activate PDP Context

Deactivate PDP Context

or

MM context change to PMM-DETACHED

UE 3G-SGSN GGSN

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

9/34


Mobility Management MessagesRegistration

Network initiated:

LOCATION UPDATING ACCEPT

LOCATION UPDATING REJECT

UE initiated:

IMSI DETACH INDICATION

LOCATION UPDATINGREQUEST

Security

Connection Management

Miscellaneous

Network initiated:

AUTHENTICATION REJECT

AUTHENTICATION REQUEST

IDENTITY REQUEST

TMSI REALLOCATION

COMMAND

UE initiated:

AUTHENTICATION RESPONSE

IDENTITY RESPONSE

TMSI REALLOCATION

COMPLETE

Network initiated:

CM SERVICE ACCEPT

CM SERVICE REJECT

ABORT

UE initiated: CM SERVICE REQUEST

CM RE-ESTABLISHMENT

REQUEST

CM SERVICE ABORT

Network initiated:

MM INFORMATION

MM STATUS

UE initiated:

MM STATUS

MM NULL

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

10/34


GPRS Mobility Management MessagesRegistration

Network initiated:

ATTACH ACCEPT

ATTACH REJECT

DETACH REQUEST

ROUTING AREA UPDATE ACCEPT

ROUTING AREA UPDATE REJECT

UE initiated:

ATTACH REQUEST

ATTACH COMPLETE

DETACH ACCEPT

DETACH REQUEST

ROUTING AREA UPDATE REQUEST

ROUTING AREA UPDATE

COMPLETE

Security

MiscellaneousNetwork initiated:

AUTHENTICATION AND

CIPHERING REQUEST

AUTHENTICATION AND

CIPHERING REJECT

IDENTITY REQUEST

P-TMSI REALLOCATION COMMAND SERVICE ACCEPT

SERVICE REJECT

UE initiated:

AUTHENTICATION AND

CIPHERING RESPONSE

AUTHENTICATION AND

CIPHERING FAILURE

IDENTITY RESPONSE P-TMSI REALLOCATION COMPLETE

SERVICE REQUEST

Network initiated:

GMM STATUS

GMM INFORMATION

UE initiated:

GMM STATUS

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

11/34


Network Mode of Operation and UE Modes

UTRAN3G-MSC/VLR

3G-SGSN

Gs

NMO I: Gs interface is present

NMO II: Gs interface is not present

UE

UE modes:

CS mode

PS mode

CS/PS mode

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

12/34


Location Area ConceptsLocation Area

Routing Area

Service Area

LA1 LA2

MCC MNC LACAI =

MCC MNC LACAI = RAC

LA2RA1

RA2RA3

RA4

MCC MNC LACAI = SAC

LA1LA2A1

SA2SA3

SA4SA5

SA7SA8

SA6

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

13/34


Location Update Types

time

timer set

last interaction

with network

Periodic timer

set Periodic timer

expires

periodic update

initiated by UE

periodic location

update (T3212)

normal location

update

LA1 / RA 1

LA 2 / RA 2

IMSI attachI am off

I am on again

3G-MSC/VLR

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

14/34


Periodic Location Update Timers and the Attach Flag

Node B

UTRANSystem Information ( )

UE RNCSIB1CS domain PS domain

T3212

ATT-flag

RAC

NMO

IE: CN domain specific

GSM-MAP NAS system

3G-SGSN

ATTACH ACCEPT ( ) / ROUTING AREA UPDATE ACCEPT ( )

UE T3312(default 54 min)

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

15/34


Location Update Status

USIM

USIMoperator XYZ

CS Mode PS ModeU1 GU1pdated

Last LU and registration

successful

USIM has

valid LAI

possibly TMSI

Last RAU and registration

successful

USIM has

valid RAI

possibly P-TMSI CK, IK, CKSN

U2 GU2ot UpdatedLast LU failed

USIM has no valid location

information and key are

deleted.

Last RAU failedUSIM has no valid routing

area information and key are deleted.

U3 GU3oaming Not AllowedLast LU successful, but

registration rejected.

USIM may have

valid LAI

possibly TMSI

Last RAU successful, but

registration rejected. USIM USIM may have

valid RAI

possibly P-TMSI CK, IK, CKSN

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

16/34


Location Update Procedure

UELocation Updating Request ( )

3G-MSC/VLR0101: mobility management message

0000

xx001000: location updating request

Normal LU/ periodic LU / IMSI attach

Follow on request pending: yes / no

MCC + MNC + LAC (previous LAI)

for GSM MSs: revision level, controlled early classmark

sending option, A5/1 support, RF power capability.

TMSI, if not available => IMSI (previous TMSI)

See MS classmark; LCS VA capability, SoLSA support, A5/2 support,

A5/3 support, CM Service Prompt support, etc.

Standard format of

every NAS message

Mobility managementprotocol discriminator

Mobile identity

Mobile stationclassmark

Location areaidentification

Ciphering keysequence number

Location updating type

Skip IndicatorLocation Updating

Request message type

Mobile stationclassmark for UMTS

OP

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

17/34


Location Update Procedure

UELocation Updating Accept ( )

3G-MSC/VLRMobility managementprotocol discriminator

Follow on proceedMobile Identity

Skip IndicatorLocation Updating

Accept message type

CTS permissionEquivalent PLMNs

Location areaidentification

0101: mobility management message

0000

xx000010: location updating accept

TMSI, if not available => IMSI (new TMSI)

the MS is allowed to use GSM-Cordless Telephony System in this LA

number of PLMNs and their MCC and MNC.OP

OP

OP

OP

MCC + MNC + LAC (new LAI)

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

18/34


Location Update ProcedureUE 3G-MSC/VLR

LOCATION UPDATING REQUEST ( )(Identification Procedure)

Authentication Procedure

Security Mode Procedure

Start T3210

T3210= 20 s

LOCATION UPDATING ACCEPT ( )

TMSI confirmationT3250 (= 12 s)

(*) Prolonged RR connection T3255(e.g. if pending request in Location Updating Req.)

Stop T3210U1

e.g. new TMSIfollow on proceed

(*)

TMSI REALLOCATION COMPLETE ( )CM message pendingT3240 (= 10 s)

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

19/34


Location Update ProcedureUE

3G-MSC/VLRLOCATION UPDATING REQUEST ( )

Authentication Procedure

Security Mode Procedure

Start T3210

T3210= 20 s LOCATION UPDATING REJECT ( )

Stop T3210U3

T3240(= 10 s)

Wait for RR connection to be release

time

T3210 expiryStart T3211U1, if UE inno new LAU Req. T3211 expiryLU Req.

T3210 expiryU1, if LAI on USIM equal to BCCH, and

attempt counter < 4, and

user status was U1U2, if LAI on USIM not equal to BCCH

attempt counter 4, or

user status was not U1

15 s

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

20/34


IMSI Detach

UE

3G-MSC/VLRMSI ATTACH INDICATION ( )RR Connection Establishment

Start T3220

T3220= 5 s

RR Connection Release

Stop T3210

Abnormal Situation:

UE cannot establish

RR Connection

Abort IMSI Detach

T3220 Expiry

UE aborts internally

its RR sub-layer

no response release of ongoing

MM connections release ofRR connection

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

21/34


T3302 expiryATTACH Req.

GPRS AttachUE

ATTACH REQUEST ( )

(Identification Procedure)

Authentication and Ciphering Procedure

Start T3310

T3210= 15 s

ATTACH ACCEPT ( )

(P-)TMSI confirmationT3350 (= 6 s)

Stop T3310GU1

e.g. new TMSIor P-TMSI

ATTACH COMPLETE ( )

time

T3310 expiryStart T3311ATTACHReq.


T3310 expiry

15 s

T3310 expiryStart T3311

GPRS attach request counter = 1


GPRS attach request counter 5mobility status = GU2

T3302 (default 12 min.)

3G-SGSN

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

22/34


UE Initiated GPRS Detach

UEDETACH REQUEST ( )



Start T3321

T3321= 15 s DETACH ACCEPT ( )

Stop T3321

3G-SGSN

IE Detach type:

GPRS detach / IMSI detach / combined GPRS/IMSI detach

normal detach/ power switch off

UEDETACH REQUEST ( )

3G-SGSN

normal detach

power switch off

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

Releases allresources onlower layers

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

23/34


Network Initiated GPRS DetachUE

DETACH REQUEST ( )(Identification Procedure)


Start T3322

T3322= 6 s

DETACH ACCEPT ( )Stop T3322

3G-SGSNre-attach required

ATTACH REQUEST ( )

terminate alllogical links andPDP Contexts

re-start alllogical links andPDP Contexts

UE DETACH REQUEST ( )DETACH ACCEPT ( )

3G-SGSN

ROUTING AREA UPDATE REQUEST ( )

IMSI detach

combined RA/LA updating with IMSI attach

re-attach not

requiredSee re-attach required, but with no message following the DETACH ACCEPT.

U2

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

24/34



Routing Area UpdateUE

ROUTING AREA UPDATE REQUEST ( )



Start T3330

T3330= 15 s

ROUTING AREA UPDATE ACCEPT ( )

T3350 (= 6 s)

Stop T3330GU1

e.g. new TMSI and/or P-TMSIor Receive N-PDU number needed

ROUTING AREA UPDATE COMPLETE ( )

time

T3330 expiryStart T3311ATTACHReq. T3211 expiryATTACH Req.

T3330 expiry

15 s


GPRS attach request counter = 1


GPRS attach request counter 5mobility status = GU2

T3302 (default 12 min.)

3G-SGSN

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

25/34


Radio Bearer Setup

The Service Request ProcedureUE

SERVICE REQUEST ( )Authentication and Ciphering Procedure

Start T3317

T3317= 10 s

SERVICE ACCEPT ( )Stop T33173G-SGSN

T3317 expiry I abort the

procedure

UESERVICE REQUEST ( )


SERVICE REJECT ( )

3G-SGSN

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

26/34


The Service Request Procedure

Protocol discriminator

P-TMSIService Type

Skip indicator

PDP context status OP

Service RequestCiphering key

sequence number

UE 3G-SGSNSERVICE REQUEST ( )

000: Signalling

001: Data

010: Paging Response

NSAPI x: 0 = corresponding PDP context is inactive1 = corresponding PDP context is inactive

X = 0 .. 15, (0..4 are coded as inactive)

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

27/34


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

supported.

RNC: PS_NMOIn 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: CSAttachDetachAllowedDefines whether IMSI attach and detach are allowed or not. Given only for CS domain. This is part of CS CN domain specificNAS System information in SIB1.

0 (UE shall not apply these procedures), 1 (MSs shall apply these procedures);

default value: 1

RNC: CNDomainIndicatorIndicates 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)

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

28/34


Nokia 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

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

29/34


Part IIConnection Management

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

30/34


Radio Bearer Setup

UE Initiated PDP Context ActivationUE

3G-SGSN

GGSNACTIVATE PDP CONTEXT REQUEST ( )

ACTIVATE PDP CONTEXT ACCEPT ( )

CREATE PDP CONTEXT REQUEST

CREATE PDP CONTEXT RESPONSET3380

= 30 s

time

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

T3380 expiry

counter = 1(*) := ACTIVATE PDP CONTEXT REQUEST

T3211 expiry(*)

counter = 4 UE aborts procedure

UPDATE PDP CONTEXT REQUESTUPDATE PDP CONTEXT RESPONSE

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

31/34


PDP Context Activation


Requested QoSRequested LLC SAPI

Transaction indicatorActivate PDP contextrequest message ID

Requested PDP addressAccess Point Name OP

Requested NSAPI

Protocol configurationoptions OP

1010: GPRS session management messages

01000001: Activate PDP context request

Delay class

Reliability class

Precedence class

Mean and peak throughput class

Maximum UL/DL bit rate

Transfer delay

Guaranteed UL/DL bit rate

Residual BER Delivery order

etc.

UE 3G-SGSNACTIVATE PDP CONTEXT REQUEST ( )

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

32/34


PDP Context Activation


Negotiated QoSNegotiated LLC SAPI

Transaction indicatorActivate PDP contextrequest message ID

PDP address

Packet Flow Identifier

OPProtocol configuration

optionsOP

Radio prioritySpare half octet

OP

1010: GPRS session management messages

01000010: Activate PDP context accept

Not required in UMTS, but transmitted to

support UMTS GPRS cell reselection

UE 3G-SGSNACTIVATE PDP CONTEXT ACCEPT ( )

T hi h PDP if PDU h

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

33/34


Secondary PDP Contexts

UEGGSN

PDN

PDP PDU

To which PDP context if PDUs have

the same PDP address?

UEGGSN

ACTIVATE SECONDARY PDP CONTEXT REQUEST ( )

ACTIVATE SECONDARY PDP CONTEXT ACCEPT ( )

CREATE PDP CONTEXT REQUESTCREATE PDP CONTEXT RESPONSET3380

= 30 s

Traffic Flow Template(TFT) attributes 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 Flow Label (IPv6)

SGSN

8/13/2019 s08 3g Rpls2_v2-0 Mm and Cm

34/34


Call Setup Flow

UE 3G-MSC/VLRSETUP ( ) most important info is the called party hp no.

CALL PROCEEDING

ALERTING

CONNECT

CONNECT ACKNOWLEDGE

Call control protocol discriminator

Transaction identifier

Setup type message

Bearer capability 1e.g. radio channel requirement, speech version indication,

information transfer capability, modem type, etc.

Called party BCD number

mandatory

IEs

Documents

s08 3g Rpls2_v2-0 Mm and Cm