34
1 © NOKIA topic: MM & CM Procedures/ July 2003 /Markus Wimmer Mobility Management and Connection Management

Nokia 3G Training 08 - Mobility Management and Connection Management

Embed Size (px)

Citation preview

Page 1: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Mobility Managementand

Connection Management

Page 2: Nokia 3G Training 08 - Mobility Management and Connection Management

2 © 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

Page 3: Nokia 3G Training 08 - Mobility Management and Connection Management

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

MM and CM Procedures

NAS controls

RRC

NAS:

Mobility Management (MM & PMM)

UE CN

AS:

UTRAN

RANAP

Connection Management (CC, SS, SMS, SM)

Page 4: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Part IMobility Management

Page 5: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Mobility Management (MM) ProceduresMM procedures

MM commonprocedures

MM specificprocedures

MM connection mgt

proceduresNetwork 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

Page 6: Nokia 3G Training 08 - Mobility Management and Connection Management

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

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 detachUE 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

Page 7: Nokia 3G Training 08 - Mobility Management and Connection Management

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

PS Mobility Management States

PMM-DETACHED

PMM-CONNECTED PMM-IDLE

GPRS DetachGPRS Attach RejectRAU Reject

GPRS Attach

Implicit GPRS Detach(SGSN: MS ReachableTimer expires)

PS Signalling ConnectionRelease

PS Signalling ConnectionEstablishment

3G-SGSN only:S-RNC Relocation

(adopted from TS 23.060 V3.13.0)

Page 8: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Packet Data Protocol States

INACTIVE ACTIVE

(adopted from TS 23.060 V3.13.0)

Activate PDP Context

Deactivate PDP Contextor

MM context change to PMM-DETACHED

UE 3G-SGSN GGSN

Page 9: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Mobility Management Messages

RegistrationNetwork initiated:• LOCATION

UPDATING ACCEPT

• LOCATION UPDATING REJECT

UE initiated: • IMSI DETACH

INDICATION • LOCATION

UPDATING REQUEST

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• ABORTUE initiated: • CM SERVICE

REQUEST• CM RE-

ESTABLISHMENT REQUEST

• CM SERVICE ABORT

Network initiated:• MM INFORMATION• MM STATUSUE initiated: • MM STATUS• MM NULL

Page 10: Nokia 3G Training 08 - Mobility Management and Connection Management

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

GPRS Mobility Management Messages

RegistrationNetwork initiated:• ATTACH ACCEPT• ATTACH REJECT• DETACH REQUEST• ROUTING AREA

UPDATE ACCEPT• ROUTING AREA

UPDATE REJECTUE initiated: • ATTACH REQUEST• ATTACH

COMPLETE• DETACH ACCEPT• DETACH REQUEST• ROUTING AREA

UPDATE REQUEST• ROUTING AREA

UPDATE COMPLETE

Security

Miscellaneous

Network initiated:• AUTHENTICATION

AND CIPHERING REQUEST

• AUTHENTICATION AND CIPHERING REJECT

• IDENTITY REQUEST

• P-TMSI REALLOCATION COMMAND

• SERVICE ACCEPT• SERVICE REJECTUE initiated: • AUTHENTICATION

AND CIPHERING RESPONSE

• AUTHENTICATION AND CIPHERING FAILURE

• IDENTITY RESPONSE

• P-TMSI REALLOCATION COMPLETE

• SERVICE REQUEST

Network initiated:• GMM STATUS• GMM

INFORMATIONUE initiated: • GMM STATUS

Page 11: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Network Mode of Operation and UE Modes

UTRAN

3G-MSC/VLR

3G-SGSN

Iu-CS

Iu-PS

Gs

NMO I: Gs interface is presentNMO II: Gs interface is not present

UE

UE modes:• CS mode• PS mode• CS/PS

mode

Page 12: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Location Area ConceptsLocation Area

Routing Area

Service Area

LA1LA2

MCC MNC LACLAI =

MCC MNC LACRAI = RAC

LA2RA1

RA2RA3

RA4

MCC MNC LACSAI = SAC

LA1LA2SA1

SA2SA3

SA4

SA5

SA7SA8

SA6

Page 13: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Location Update Types

timetimer set

last interactionwith networkPeriodic timer

set Periodic timerexpires

periodic updateinitiated by UE

periodic locationupdate

normal locationupdate

LA1 / RA 1

LA 2 / RA 2

IMSI attach

IMSI Detach Indication

Location Update Request

I am off

I am on again

3G-MSC/VLR

Page 14: Nokia 3G Training 08 - Mobility Management and Connection Management

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

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 specificGSM-MAP NAS system

3G-SGSN

ATTACH ACCEPT ( ) / ROUTING AREA UPDATE ACCEPT ( )

UE T3312(default 54 min)

Page 15: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Location Update Status

USIM

USIMoperator XYZ

CS Mode PS ModeU1 GU1Updated

Last LU and registrationsuccessfulUSIM has• valid LAI• possibly TMSI

Last RAU and registrationsuccessfulUSIM has• valid RAI• possibly P-TMSI

• CK, IK, CKSN

U2 GU2Not UpdatedLast LU failedUSIM has no valid locationinformation and key aredeleted.

Last RAU failedUSIM has no valid routingarea information and key are deleted.U3 GU3Roaming Not Allowed

Last LU successful, butregistration rejected.USIM may have• valid LAI• possibly TMSI

Last RAU successful, butregistration rejected. USIM USIM may have• valid RAI• possibly P-TMSI

• CK, IK, CKSN

Page 16: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Location Update Procedure

UE

Location Updating Request ( )

3G-MSC/VLR0101: mobility management message

0000

xx001000: location updating requestNormal LU/ periodic LU / IMSI attachFollow on request pending: yes / no

MCC + MNC + LACfor GSM MSs: revision level, controlled early classmarksending option, A5/1 support, RF power capability.

TMSI, if not available => IMSISee MS classmark; LCS VA capability, SoLSA support, A5/2 support,A5/3 support, CM Service Prompt support, etc.

Standard format ofevery 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

Page 17: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Location Update Procedure

UE

Location 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

the MS is allowed to use GSM-Cordless Telephony System in this LAnumber of PLMNs and their MCC and MNC.OP

OPOP

OP

MCC + MNC + LAC

Page 18: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Location Update Procedure

UE 3G-MSC/VLRLOCATION 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)

Page 19: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Location Update ProcedureUE

3G-MSC/VLR

LOCATION UPDATING REQUEST ( )Authentication ProcedureSecurity 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 LALU Req. T3211 expiry

LU 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

Page 20: Nokia 3G Training 08 - Mobility Management and Connection Management

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

IMSI Detach

UE

3G-MSC/VLRIMSI DETACH INDICATION ( )

RR Connection EstablishmentStart T3220

T3220= 5 s

RR Connection ReleaseStop T3220

Abnormal Situation:UE cannot establishRR Connection Abort IMSI Detach

T3220 ExpiryUE aborts internallyits RR sub-layer

• no response• release of ongoing

MM connections• release of

RR connection

Page 21: Nokia 3G Training 08 - Mobility Management and Connection Management

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

T3302 expiryATTACH Req.

GPRS AttachUE

ATTACH REQUEST ( )

(Identification Procedure)

Authentication and Ciphering Procedure

Start T3310

T3310= 15 s

ATTACH ACCEPT ( )

(P-)TMSI confirmationT3350 (= 6 s)

Stop T3310GU1

e.g. new TMSIor P-TMSI

ATTACH COMPLETE ( )

time

T3310 expiryStart T3311

ATTACHReq.

T3311 expiryATTACH Req.

T3310 expiry

15 s

T3310 expiryStart T3311

GPRS attach request counter = 1

T3310 expiryStart T3302

GPRS attach request counter 5 mobility status = GU2

T3302 (default 12 min.)

3G-SGSN

Page 22: Nokia 3G Training 08 - Mobility Management and Connection Management

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

UE Initiated GPRS Detach

UEDETACH REQUEST ( )

(Identification Procedure)

Authentication and Ciphering Procedure

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 all resources on lower layers

Page 23: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Network Initiated GPRS DetachUE

DETACH REQUEST ( )

(Identification Procedure)

Authentication and Ciphering Procedure

Start T3322

T3322= 6 s

DETACH ACCEPT ( )Stop T3322

3G-SGSNre-attach required

ATTACH REQUEST ( )

terminate all logical links and

PDP Contexts

re-start all logical links and

PDP Contexts

UE DETACH REQUEST ( )DETACH ACCEPT ( )

3G-SGSN

ROUTING AREA UPDATE REQUEST ( )

IMSI detach

combined RA/LA updating with IMSI attach

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

U2

Page 24: Nokia 3G Training 08 - Mobility Management and Connection Management

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

T3302 expiryATTACH Req.

Routing Area UpdateUE

ROUTING AREA UPDATE REQUEST ( )

(Identification Procedure)

Authentication and Ciphering Procedure

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 T3311

ATTACHReq.

T3311 expiryATTACH Req.

T3330 expiry

15 s

T3330 expiryStart T3311

GPRS attach request counter = 1

T3330 expiryStart T3302

GPRS attach request counter 5 mobility status = GU2

T3302 (default 12 min.)

3G-SGSN

Page 25: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Radio Bearer Setup

The Service Request ProcedureUE

SERVICE REQUEST ( )Authentication and Ciphering Procedure

Start T3317

T3317= 10 s

SERVICE ACCEPT ( )Stop T3317

3G-SGSN

T3317 expiryI abort

the procedur

e

UESERVICE REQUEST ( )

Authentication and Ciphering Procedure

SERVICE REJECT ( )

3G-SGSN

Page 26: Nokia 3G Training 08 - Mobility Management and Connection Management

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

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: Signalling001: Data010: Paging Response

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

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

Page 27: Nokia 3G Training 08 - Mobility Management and Connection Management

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

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 specific NAS 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)

Page 28: Nokia 3G Training 08 - Mobility Management and Connection Management

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

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

Page 29: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Part IIConnection Management

Page 30: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Radio Bearer Setup

UE Initiated PDP Context Activation

UE

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

Page 31: Nokia 3G Training 08 - Mobility Management and Connection Management

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

PDP Context Activation

Protocol discriminator

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 ( )

Page 32: Nokia 3G Training 08 - Mobility Management and Connection Management

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

PDP Context Activation

Protocol discriminator

Negotiated QoSNegotiated LLC SAPI

Transaction indicatorActivate PDP contextrequest message ID

PDP address

Packet Flow Identifier

OPProtocol configurationoptions

OP

Radio prioritySpare half octet

OP

1010: GPRS session management messages

01000010: Activate PDP context accept

Not required in UMTS, but transmitted tosupport UMTS – GPRS cell reselection

UE 3G-SGSNACTIVATE PDP CONTEXT ACCEPT ( )

Page 33: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Secondary PDP Contexts

UE

GGSNPDN

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

Page 34: Nokia 3G Training 08 - Mobility Management and Connection Management

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

Call Setup Flow

UE 3G-MSC/VLRSETUP ( )

CALL PROCEEDING

ALERTING

CONNECT

CONNECT ACKNOWLEDGE

• Call control protocol discriminator

• Transaction identifier• Setup type message• Bearer capability 1

e.g. radio channel requirement, speech version indication, information transfer capability, modem type, etc.

• Called party BCD number

mandatoryIEs