Chapter 3

The GMM/SM ProtocolContents:3.1 GMM tasks

1. GMM Procedures2. The concept of Routing Areas3. GPRS Mobility Management State Transition4. Combined /not combined GMM/MM procedures

3.2 Session Management SM1. PDP State Model2. Elements involved in PDP contexts3. PDP related parameters

3.3 Message formatting1. GMM/SM message formats 2. Mandatory message fields3. SM Message types4. ATTACH REQUEST message content5. PDP context activation example

Chapter 3

The GMM/SM Protocol3.4 GMM procedures

1. Authentication and Ciphering 2. GPRS Attach Procedure 3. MS Initiated Detach 4. Network Initiated Detach 5. Routing Area Update 6. GMM Information

3.5 SM procedures1. General Aspects about PDP Contexts2. PDP Context States and Packet Sessions3. PDP Context Related Parameters4. Successful PDP Context Activation Procedure 5. Secondary PDP Contexts 6. PDP Context Modification7. PDP Context Deactivation

Chapter 3.1

Contents:3.1 GMM tasks

1. GMM Procedures2. The concept of Routing Areas3. GPRS Mobility Management State Transition4. Combined /not combined GMM/MM procedures

The GMM/SM Protocol

GPRS Mobility Management

MS BSSUm Gb

MAC

GSM RF

RLC

LLC

GMM

MAC

GSM RF

RLC

NSFR

L1

BSSGP

Relay

NSFR

L1

BSSGP

LLC

GMM

SGSN

GMM Procedures

GMM Common Procedures GMM Specific Procedures

• GPRS Authentication and Ciphering• GPRS Identification• GPRS Information• P-TMSI (Re-)allocation

• GPRS Attach,Combined GPRS Attach• GPRS Detach, Combined GPRS Detach• Normal Routing Area Update

Combined Normal Routing Area Update Periodic Routing Area Update

•GMM common procedures GMM common procedures can be always initiated when a packet switched signalling connection exists.

•GMM specific procedures GMM specific procedures are used to establish and maintain a GMM context between MS and SGSN. If the network supports combined procedures, also circuit switched mobility related MM tsks are performed by the SGSN.

The concept of Routing Areas

MCCMobile Country Code

MNCMobile Network Code

LAC (16 bits)Location Area Code

CI (16 bits)Cell Identity

RAC (8 bits)Routing Area Code

LAILocal Area Identifier

CGICell Global Identity

RAIRouting Area Identifier

=

=

LARA

CI

MS initiates: Normal Routing Area Updatecombined Normal Routing Area Update (with Location Area Update),Periodic Routing Area Update.

RA size : by default one RA is equal to one LA. This is reasonable until the PS

paging load is increasing and the available paging capacity is exceeded. The number of paging is

a function of the number of subscribers and of the used services. To reduce the paging load a LAI may be split

into RAs (of course increasing the number of RA updates) or the PPCH channel may be configured (of course loosing resources on the air)

GMM Specific Procedures

GPRS Mobility Management State Transition

IDLE READY STANDBY

GPRS Attach

PDU transmission

IDLE READY STANDBY

GPRS Attach

PDU reception

Implicit Detach/Cancel Location

READY Timer expiry/Force to STANDBY/

READY Timer expiry/Force to STANDBY/

Abnormal RLC conditions

GPRS Detach

GPRS Detach/Cancel Location

Seen by SGSN

Seen by MS:

MS location not known. Subscriber is not reachable by the GPRS NW.

MS location known to Cell Level. MS is transmitting or has just been transmitting. MS is capable of receiving Point-to-Point data and Point-to-Multipoint data.

MS location known to RA Level.MS is capable of receiving Point-to-Multipoint data and being paged for Point-to-Point data

GMM Specific Procedures

Combined /not combined GMM/MM procedures

NMO IIIMSI

attachedGPRS

attached

NMO IIMSI

attachedGPRS

attached

cs pagingmessage

PCH, orPPCH, orPACCH

ps pagingmessage

PCH

NMO IIIIMSI

attachedGPRS

attached

PCHPCH, or PPCH (if used)

- Gs interface required- works with or without PBCCH- Paging Coordination- Combined Mobility Management

- no Gs interface -no PBCCH-separate Mobility Management

- no Gs interface-works with or without PBCCH-separate Mobility Management

The NMO (Network Mode of Operation) parameter is broadcast in BCCH or PBCCH. Pictures are valid only for classA and B MSs. A class C MS can not be attached in MSC and SGSN simultaneously!!!

SGSNMSC/VLRSGSNMSC/VLRGs

SGSNMSC/VLR

Chapter 3.2

3.2 Session Management SM1. PDP State Model2. Elements envolved in PDP contexts3. PDP related parameters

The GMM/SM Protocol

PDP State Model

INACTIVE• no routing and mapping of PDP

PDUs possible• no data transmission

ACTIVE• routing and mapping of PDP PDUs possible• location update

takes place

Activate PDP Context

Deactivate last PDP ContextMM state change to IDLE

The session management functions are used for activation, modification and deactivation of PDP (Packet Data Protocol) contexts, i.e. for packet routing and to enable the transfer of user data. The SM functions are located in MS, SGSN and GGSN.

INACTIVE State: A data service has not been activated. PDP PDUs can neither be routed nor mapped to this PDP address. Actually, no data transmission for this PDPcontext is possible (except SMS).

ACTIVE State: The PDP context for one or several PDP address is set active in the MS, SGSN, and GGSN. By doing so, the transfer of user data between the MS and the GGSN via the SGSN is possible.

MS BSSUm Gb

MAC

GSM RF

RLC

LLC

SM

MAC

GSM RF

RLC

NSFR

L1

BSSGP

Relay

NSFR

L1

BSSGP

LLC

SM

SGSN

PDP State Model

Elements envolved in PDP contexts

GPRS Backbone

SGSN GGSN

applications

applications

applications

GTP tunnel

several applicationsvia different PDP contexts

to one AP

several applicationsvia 1 PDP context

to one AP

several applicationsvia 1 PDP context

to different APsnot possible!!!

GTP tunnel

GTP tunnel

MMS

WAP

streaming

WAP

MMS

WAP

GTP tunnel

MS

Several PDPs may be active simultaneously (not every phone supports that,-one PDP = 1 set of QoS parameters). Different applications may require different QoS, that means different PDPs have to be activated. The information about the PDP has to be configured in the phone. Required is the so called APN (Access Point Name, eg operator.net) to create the logical connection between MS and external Packet Data Network. With the PDP context activation the GTP tunnel between the SGSN and GGSN is created.

PDP related parameters

NSAPI

APN

PDP type

PDPaddress

APN

The NSAPI is used as a global identifier for a PDP context. It is especially used from outside of the GPRS network to access a PDP context. So if the PDP context is used

for the tunnelling of IP datagrams, the associated IP layer in the MS (or equipment connected to the MS) will use the NSAPI as interface identifier. In fixed line IP networks this is mainly used to distinguish between several interface cards (e.g. Ethernet cards, modems, etc.).

PDP State

Dynamic Address AllowedQoS Profile Requested

QoS Profile Negotiated

Radio Priority

The PDP type indicates which protocol is tunnelled through the PDP context (e.g. IPv4/v6 or PPP).

The PDP address is a routing address of the tunnelled protocol. The MS uses the PDP address to be connected to the external data network. For the GPRS network this address

has no meaning, which means that it will not be used for routing within the GPRS network. (e.g. IP v4/v6 address)

The APN is the name of the external data network. Hence it indicates the internet service provider (ISP). Within the GPRS network the APN is used by the SGSN to find a suitable

GGSN using a Domain Name Server. The GGSN uses the APN to find the correct port to the specified ISP.

The SM protocol that handles the PDP contexts between MS and SGSN uses the TI (Transaction Identifier) to differentiate between different PDP contexts. This is the same

as for circuit switched calls.

APNTI

APNothers

Chapter 3.3

3.3 Message formatting1. GMM/SM message formats 2. Mandatory message fields3. SM Message types4. ATTACH REQUEST message content5. PDP context activation example

The GMM/SM Protocol

GMM/SM message formats

The GPRS Mobility Management and Session Management procedures are defined in the recommendation 3GPP 03.60. Every GMM/SM message contains several parameters, also known as Information Elements (IE). Section 9 of GSM Guideline 04.08 defines the mandatory and optional parameters for every message. The same parameter may be mandatory for one message and optional for another. Optional parameters bear an identifier (Information Element Identifier, IEI) to show their presence. The identifier is always located at the beginning of the parameter. Mandatory parameters, by contrast, include sometimes - dependent on the position - an identifier.The parameters are sub-divided into 5 parameter formats (described in GSM 04.07):

1 Message: several mandatory or optional (conditional) Information Elements

GMM/SM message formats

Information Element formats:V(value only) parameters have neither an identifier (IEI) nor a length indicator; they are mandatory parameters of fixed length. The length is either an integer amount of bytes or 1/2 byte. In the last case, V-parameters of 1/2 byte length are combined to form pairs whenever possible. The first parameter in the combination encompasses the 4 least significant bits, the second parameter the 4 most significant bits. If the total number of V-parameters of 1/2 byte is odd, the 4 most significant bits of the last byte are filled with 0000. TV(type and value) parameters have an identifier (IEI) but no length indicator. If the length of the contents is an integer amount of bytes, then the IEI is 1 byte in length, and the most significant IEI bit is 0. If the length of the contents is 1/2 byte, then the IEI is likewise 1/2 byte in length. The most significant bit is 1, and the succeeding bits must not be 010 (to distinguish them from T-parameters, see below).T(type only) parameters have 0 byte content. The communicated information consists solely in the presence or absence of the parameter. Obviously, such parameters can only be considered as optional. The identifier (IEI) is 1 byte in length and begins with 1010 (so that no confusion with TV-parameters is possible). One example of a type-2 parameter is the authorization given in "Location Update Accept" for the Mobile Station to set up a MM connection directly after the location update (i.e. in the same RR connection). This authorization may, or may not, be present.LV(length and value) parameters have a length indicator but no identifier (IEI); they are mandatory parameters of variable length. The length indicator is the first byte and indicates how many bytes of contents follow.TLV(type, length and value) parameters have an identifier (IEI) and a length indicator. The IEI is the first byte of the parameter; its most significant bit is 0. The length indicator is the second byte of the parameter and indicates how many bytes of contents follow.

Message formats

Parameter Format Length integer amount of Bytes Length of 1/2 Byte

contentcontent 2 content 1content 4 content 3

content 50 0 0 0

Example: 5 parameters

V alue

content

IEI0

IEI1 content# 0 1 0

T ype, V alue

content

Length indicator

1 0 1 0 IEI

content

Length indicatorIEI0

T ype, L ength, V alue

L ength, V alue

T ype

TI-valueTI-flag

Protocol discriminator

Message type

Message Type

Protocol discriminatorTransaction identifier

or Skip indicator

Each message begins with the same three V-parameters:The protocol discriminator is a parameter of 1/2 byte length. The transaction identifier is a V-parameter of 1/2 byte.The message type identifies the nature of the message. It is a V-parameter with a length of 1 byte.

Mandatory message fields

The protocol discriminator specifies the layer 3 part to which the message belongs. It is a parameter of 1/2 byte length.(3 GPP 04.07)

The message type ( here for GMM) identifies the nature of the message. It is a V-parameter with a length of 1 byte.(3GPP 4.08)

group call controlbroadcast call controlReserved: was allocated in earlier phases of the protocolcall control; call related SS messagesGPRS Transparent Transport Protocol (GTTP)mobility management messagesradio resources management messages

non call related SS messages

reserved for extension of the PD to one octet length

0 0 0 0

0 0 0 1

0 0 1 0

0 0 1 1

0 1 0 0

0 1 0 1

0 1 1 0

1 0 0 0

1 0 0 1

1 0 1 0

1 0 1 1

1 1 00

1 1 1 0

1 1 1 1 reserved for tests procedures

Attach request

Attach accept

Attach complete

Attach reject

Detach request

Detach accept

Routing area update request

Routing area update accept

Routing area update complete

Routing area update reject

Service Request

Service Accept

Service Reject

P-TMSI reallocation command

P-TMSI reallocation complete

Authentication and ciphering req

Authentication and ciphering resp

Authentication and ciphering rej

Authentication and ciphering failure

Identity request

Identity response GMM status

GMM information

Location services

GPRS mobility management messages

GPRS session management messages

Same format used to CS/PS core SMS messages

ATTACH REQUEST message content I

00 0 0 1 0 0 0

00 0 0 0 0 0 1

00 0 0 0 0 0 1

00 0 0 0 1 1 0

0 0 0 1

00 0 0 1 0 0 0

1 0 0 1

CKSN

00 0 0 0 0 0 1

00 0 0 1 1 1 1

1. digit

2. digit3. digit

n - digit

MCC

MNC

DUMMY

PD=GMM, Skip indicator

67 5 4 3 2 1 0

Message Type = Attach Request

Example (start)

MS Network CapabilityLength 1 ByteMS Network Capabilty value

Attach Type = GPRS Attach

DRX parameternon DRX timer, split on CCCH

Mobile IdentityLength 8 ByteType of Identity = IMSIodd number of digits

Old Routing Area Identification

ATTACH REQUEST message content II

00 0 0 1 0 0 1

67 5 4 3 2 1 0

Old Routing Area Identification

MS Radio Access CapabilityLength 9 Byte

LAC

RAC

MS Radio AccessCapability

Example end

ATTACH REQUEST message content III

Table 9.4.1/3GPP TS 24.008:Information Element Type/Reference Presence Format Length

Protocol discriminator Protocol discriminator10.2

M V 1/2

Skip indicator Skip indicator10.3.1

M V ½

Attach request message identity Message type10.4

M V 1

MS network capability MS network capability10.5.5.12

M LV 3-9

Attach type Attach type10.5.5.2

M V ½

GPRS ciphering key sequence number

Ciphering key sequence number 10.5.1.2

M V ½

DRX parameter DRX parameter10.5.5.6

M V 2

P-TMSI or IMSI Mobile identity10.5.1.4

M LV 6 - 9

Old routing area identification Routing area identification10.5.5.15

M V 6

MS Radio Access capability MS Radio Access capability10.5.5.12a

M LV 6 - 52

Old P-TMSI signature P-TMSI signature10.5.5.8

O TV 4

Requested READY timervalue

GPRS Timer10.5.7.3

O TV 2

TMSI status TMSI status10.5.5.4

O TV 1

|---0---- |1 HSCSD MultiSlot Flag |not present |

|----1--- |1 GPRS MultiSlot/Ext. Flag |present |

|***b5*** |1 GPRS MultiSlot Class |4 |

|--0----- |1 GPRS Extended Dynamic Allo. CAP1. |not implemented |

|---0---- |1 SMS and SM Value Flag |not present |

|----1--- |1 MS RA capability Flag |present |

|***b4*** |2 Access Technology Type |GSM 1800 |

|-0001001 |2 Access technology type len |9 |

|001----- |2 RF Power CAP1ability |1 |

|---0---- |2 Encryption Alogorithm Flag |not present |

|----1--- |2 Early classmark |implemented |

|-----0-- |2 Pseudo Synchronisation |not present |

|------0- |2 Voice Group Call Service |no VGCS wanted |

|-------0 |2 Voice Broadcast Service |no VBS wanted |

|0------- |2 MultiSlot CAP1ability flag |not present |

|-0------ |2 MS RA capability Flag |not present |

|--000000 |Padding |0 |

|MS Radio Access Capability |

|00001000 |IE Length |8 |

|0001---- |1 Access Technology Type |GSM E |

|***b7*** |1 Access technology type len |25 |

|---100-- |1 RF Power CAP1ability |4 |

|------1- |1 Encryption Alogorithm Flag |present |

|-------1 |1 A5/1 |available |

|1------- |1 A5/2 |available |

|-0------ |1 A5/3 |not available |

|--0----- |1 A5/4 |not available |

|---0---- |1 A5/5 |not available |

|----0--- |1 A5/6 |not available |

|-----0-- |1 A5/7 |not available |

|------1- |1 Early classmark |implemented |

|-------0 |1 Pseudo Synchronisation |not present |

|0------- |1 Voice Group Call Service |no VGCS wanted |

|-0------ |1 Voice Broadcast Service |no VBS wanted I

|--1----- |1 MultiSlot CAP1ability flag |present |

MS Radio Access CapabilityLength 9 Byteexample

ATTACH REQUEST message content IV

This shows an example of the IE Radio Access capability contained in the GPRS attach request message for example.

PDP context activation example

PD=SM, TI-flag=00 1 0 1 0

10 0 0 0 0 0 1 Msg T.=Activate PDP Context Request

00 0 0

0 0

0

00 0 0 0 0 1 1

Reliability Class

Requested NSAPI e.g. NSAPI=5

Quality of ServiceLength 3 Byte

TI-value

NSAPI

Requested LLC SAPI e.g. SAPI=300 0 0 LLC SAPI

Delay Class

Precedence ClassPeak throughput

0 0 0 Mean throughput

00 0 0 0 0 1 0 PDP addressLength 2 ByteIETF specified addressIPv4 address (dynamic addressing)

00 0 0 00 0 1

00 1 0 0 0 0 1

00 1 0 0 1 1 1

00 1 0 0 1 0 0

01 0 0 0 0 0 0

Content n-Byte

Protocol Configuration OptionsLength 36 ByteLength 36 ByteOptions format value, extension bitOptions format value, extension bit

67 5 4 3 2 1 0

PDP context activation example

Activate PDP context request

|----1010 |Protocol Discriminator |Session management messages

|-000---- |Transaction Id value |TI value 0

|0------- |Transaction Id |message sent from orig TI

|01000001 |Message Type |65

|Network Service Access Point

|----0101 |NSAPI value |NSAPI 5

|0000---- |Spare |0

|LLC SAPI

|----0011 |SAPI |SAPI 3

|0000---- |Spare |0

|Quality of Service

|00000011 |IE Length |3

|-----011 |Reliability class |Unack. GTP&LLC,Ack.RLC,Prot. data

|--100--- |Delay class |Delay class 4 (best effort)

|00------ |Spare |0

|-----011 |Precedence class |Low priority

|----0--- |Spare |0

|0101---- |Peak throughput |Up to 16000 octet/s

|---11111 |Mean throughput |best effort

|000----- |Spare |0

|Packet Data Protocol Address

|00000010 |IE Length |2

|----0001 |Type of address |IETF specified address

0000---- |Spare |0

|00100001 |Packet data protocol type |IPv4

|Access Point Name |

|00101000 |IE Name |Access Point Name

|00010000 |IE Length |16

|**B16*** |Access Point Name Value XXXXXXXXXXX

|Protocol Configuration Options

|00100111 |IE Name |Protocol Configuration Options

|01010000 |IE Length |80

|-----000 |Options format value |PPP

|-0000--- |Spare |0

|1------- |Extension bit |Octet 3 is extended

|**B79*** |Address information |c2 23 19 01 01 00 19 14 9b e0 d4 6f |

|Protocol Config. Options PAP(RFC 1334) CHAP(RFC 1994) IPCP(RFC 1332) (CHAP_PAP) |

|---v--- DECODING ERROR: PE_DEC_AUFZ_LEN ---v---

|CHAP-Challenge

|***B2*** |Challenge-Handshake Authentication Protocol |c223

|00011001 |Total length |25

|00000001 |Algorithm |1

|00000001 |Code |Challenge

|00000000 |Identifier |0

|***B2*** |Length |6420

|Challenge

|10011011 |Value size |155

Chapter 3.4

The GMM/SM Protocol3.4 GMM procedures

1. Authentication and Ciphering 2. GPRS Attach Procedure 3. MS Initiated Detach 4. Network Initiated Detach 5. Routing Area Update 6. GMM Information

Authentication and Cipher Setting

SGSN

MS

Authentication And Ciphering Request(ciphering algorithm, RAND, A&C reference number,

GPRS ciphering key sequence number)

Authentication And Ciphering Response(A&C reference number, SRES, IMEISV)

Authentication And Ciphering Reject

Start T3360 (= 6s)

Stop T3360

SRESMS SRESAC

T3360 expiry retransmission (max. 4 times)

( )

Subscriber record• ps service data• RAI / CI

GPRS Attach Procedure

SGSN

MS

RA 1

RA 2

RA 3

HLR

IMSI

Subscriber record• Service data• SGSN no. (E.164)• SGSN IP address

IMSI

IMSI/MSISDN

RAI =IMSI =

MSISDN =

MCC + MNC + LAC + RACMCC + MNC + MSINCC + NDC + SN

GPRS Attach Procedure - Example

Attach Request( old [RAI,P-TMSI] )

Identification Request( RAI, P-TMSI )

Identification Response( cause, IMSI, authentication data )

Update GPRS Location( IMSI, SGSN-no., SGSN-IP-address )

Authentication

Insert Subscriber Data( IMSI, PS subscription information )

Cancel Location( IMSI, type=update )

Cancel Location Ack( )

Insert Subscriber Data Ack

Update GPRS Location Ack( HLR number )

Attach Accept( new PTMSI, new RAI )

Attach Complete( )

SGSN SGSNHLR

MS

Successful GPRS Attach

Attach Request( MS network capability, Access type,

GPRS ciphering key sequence number,P-TMSI or IMSI, old RAI, MS radio access capability )

GMM common procedures (e.g. Authentication and Ciphering)

Attach Accept( Attach result, Force to standby, Period RA update timer,

Radio Priority for SMS, new RAI, optional: allocated P-TMSI, equivalent PLMNs

Cell Notification )

Attach Complete( )

SGSN

MS

Start T3310(= 15 s)

Stop T3310 Start T3350 (= 6 s)(only if (P-)TMSIallocated)

Stop T3350

MS Initiated Detach

Detach Request( Detach type :

GPRS detach or IMSI detach orcombined GPRS/IMSI detach

normal detach or power switch detach,optional: P-TMSI, P-TMSI signature )

Authentication

Detach Accept( )

SGSN

MS

Start T3321(= 15 s)

Stop T3321

only with power switch detach

GGSN

Delete PDP Context Request( TEID )

Delete PDP Context Response( TEID )

Network Initiated Detach (Example)

Detach Request( Detach type :

re-attach required orre-attach not required orIMSI detach (after VLR failure) )

Detach Accept( )

Start T3322(= 6 s)

Stop T3322

Delete PDP Context Request( TEID )

Delete PDP Context Response( TEID )

Cancel Location( IMSI,

type = subscription withdrawn )

Cancel Location Ack( )

GGSNSGSN

MS

HLR

Routing Area Update Causes

RA 1

RA 2 no RA update

no RA update

normal RA update

periodic RA update

( T3312: default: 54 min )

SGSN

Attach Accept or Routing Area Update Accept

Combined RA/LA updating with IMSI attach

Combined RA/LA updating

Intra Routing Area Update

Routing Area Update Request( Update type: RA updated or combined RA/LA updated,

GPRS ciphering key sequence number,old RAI, MS radio access capability )

Authentication

Routing Area Update Accept( Update result,

Period RA update timer, current RAI, optional: allocated P-TMSI, P-TMSI signature,

Receive N-PDU number )

Routing Area Update Complete

SGSN

MS

Start T3330(= 15 s)

Stop T3330 Start T3350 (= 6 s)only when • P-TMSI and/or• Receive N-PDU numberswere allocated

Stop T3350

P-TMSI Reallocation and Identity Request

P-TMSI Relocation Command( Allocated P-TMSI , RAI , Force to standby,

optional: P-TMSI signature )

P-TMSI Relocation Complete( )

SGSN

MS

Start T3350 (= 6 s)

Stop T3350

Identity Request( Identity type: IMSI, IMEI, IMEISV, TMSI )

Identity Response( Mobile Identity )

Start T3370(= 6 s)

Stop T3370

GMM Information

GMM Information( Full name for network, Short name for network,

Local time zone, Universal time and local time zone,LSA identity, Network daylight saving time )

GMM Status( GMM cause )

SGSN

MS

Optional:

only when the GMM request is rejected

Chapter 3.5

The GMM/SM Protocol3.5 SM procedures

1. General Aspects about PDP Contexts2. PDP Context States and Packet Sessions3. PDP Context Related Parameters4. Successful PDP Context Activation Procedure 5. Secondary PDP Contexts 6. PDP Context Modification7. PDP Context Deactivation

PDP Context States and Packet Sessions

INACTIVE ACTIVE

Activate PDP Context

Deactivate PDP Context /GMM changes to IDLE state

SGSN

MS

GGSNISP

Packet Session (using PDP)

PDP Context PDP Bearer

Session Management GPRS Tunnelling Protocol

PDP Context Parameters Except

SGSN

MS

GGSNISP

NSAPI

PDP type

PDPaddress

APN

NSAPI

PDP type

PDPaddress

APN

GGSNaddress

TEIDGGSN

for control

NSAPI

PDP type

PDPaddress

APN

SGSNaddress

PDPaddress

TEIDGGSN

for data

TEIDSGSN

for controlTEIDSGSN

for data

Successful PDP Context Activation Procedure

Activate PDP Context Request( Transaction Identifier, Requested NSAPI, Requested LLI SAPI,Requested QoS, Requested PDP addressoptional: APN )

Authentication

Activate PDP Context Accept

SGSN

MS

Start T3380(= 30s)

Stop T3380

GGSN

Create PDP Context Request( TEIDSGSN data, TEIDSGSN control plane, NSAPI, QoS profile, End user address,

SGSN address for control plane and for user traffic )

Create PDP Context Response

( Transaction Identifier, Negotiated LLI SAPI, Negotiated QoS, Radio priority, optional: PDP address, packet flow id )

( TEIDGGSN data, TEIDCGSN control plane, QoS profile, End user address, GGSN address for control plane

and for user traffic )

Successful PDP Context Activation by the Network

PDP ACTIVATE IND

SGSN

MS

Start T3385 (= 8s)

GGSN

PDU Notification Request

( IMSI, SGSN address )

PDU Notification Response

( Offered PDP address, optional: APN )

( IMSI, TEIDCGSN control plane, End user address, APN,

GGSN address for control plane)

ISPHLR

PDP PDUSend Routing Info for GPRS Request

Send Routing Info for GPRS Response

( IMSI)

PDP Context Activation Procedure

Activate PDP Context Response

Stop T3385

Secondary PDP Contexts

GGSN

PDP context 1

PDP context 1a

PDP context 2

(PDP address: A, APN: a)

(PDP address: A, APN: a)

(PDP address: B, APN: a)

Dest address: A

Dest. address: B

IPv4 source address

TFT 1

TFT 2

TFT 3

IPv6 source address

Protocol ID / Next Header

Source Port Number

Source Port Number Range

Dest. Port Number

Dest. Port Number Range

Type of Service/Traffic Class

Flow Label

IPsec security parameter

Traffic Flow Template (TFT)

IPv4 source address

IPv6 source address

Protocol ID / Next Header

Source Port Number

Source Port Number Range

Dest. Port Number

Dest. Port Number Range

Type of Service/Traffic Class

Flow Label

IPsec security parameter

PDP context 1

PDP context 1a

PDP context 2ISP

PacketFilter

Successful Secondary PDP Context Activation

Activate Secondary PDPContext Request

( Transaction Identifier, Requested NSAPI, Requested LLC SAPI,Requested QoS, Linked TIoptional: TFT )

Authentication

Activate Secondary PDP Context Accept

SGSN

MS

Start T3380(= 30s)

Stop T3380

GGSN

Create PDP Context Request( TEIDSGSN data, TEIDSGSN control plane, NSAPI, QoS profile, End user address,

SGSN address for control plane and for user traffic, TFT )

Create PDP Context Response

( Transaction Identifier, Negotiated LLI SAPI, Negotiated QoS, Radio priority )

( TEIDGGSN data, TEIDCGSN control plane, NSAPI, QoS profile, End user address,

GGSN address for control plane and for user traffic )

Successful PDP Context Modification (MS initiated)

Modify PDP Context Request( Transaction Identifier, optional: Requested LLC SAPI, Requested new QoS, New TFT )

Authentication

Modify PDP Context Accept

SGSN

MS

Start T3381(= 8s)

Stop T3381

GGSN

Update PDP Context Request( TEIDSGSN data, TEIDSGSN control plane,

NSAPI, QoS profile, SGSN address for control plane

and for user traffic )

Update PDP Context Response

( Transaction Identifier, optional: Negotiated LLI SAPI, Negotiated QoS, New radio priority, packet flow id )

( TEIDGGSN data, TEIDCGSN control plane, QoS profile,,

GGSN address for control plane and for user traffic )

PDP Context Modification (SGSN initiated)

Modify PDP Context Request( Transaction Identifier, Requested LLC SAPI, Radio priority, Requested new QoS, optional: PDP address, TFI )

Modify PDP Context Accept

SGSN

MS

Start T3386(= 8s)

Stop T3386

GGSN

Update PDP Context Request( TEIDSGSN data, TEIDSGSN control plane,

NSAPI, QoS profile, SGSN address for control plane

and for user traffic )

Update PDP Context Response

( Transaction Identifier )

( TEIDGGSN data, TEIDCGSN control plane, NSAPI, QoS profile,,

GGSN address for control plane and for user traffic )

PDP Context Modification (GGSN initiated)

SGSN

MS

GGSN

Update PDP Context Request( NSAPI,

optional: end user address,QoS profile )

Update PDP Context Response( optional: QoS profile )

Modify PDP Context Request( Transaction Identifier, Requested LLC SAPI, Radio priority, Requested new QoS, optional: PDP address, TFI )

Modify PDP Context Accept

Start T3386(= 8s)

Stop T3386( Transaction Identifier )

PDP Context Deactivation (MS initiated)

Deactivate PDP Context Request( Transaction Identifier, SM causeoptional: Teardown indicator )

Authentication

Deactivate PDP Context Accept

SGSN

MS

Start T3390(= 8s)

Stop T3390

GGSN

Delete PDP Context Request( NSAPI, Teardown indicator )

Delete PDP Context Response

( Transaction Identifier )

( cause )

SM Message types

GPRS session management messages

PRIMITIVE PARAMETER(message, info elements of message, other parameters)

SMREG-PDP-ACTIVATE-REQ PDP address, QoS, NSAPI, APN, Protocol configuration options

SMREG-PDP-ACTIVATE-CNF PDP address, QoS, NSAPI, Protocol configuration options

SMREG-PDP-ACTIVATE-REJ Cause, NSAPI, Protocol configuration options

SMREG-PDP-ACTIVATE-IND PDP address, APN

SMREG-PDP-ACTIVATE-REJ-RSP Cause, PDP address, APN

SMREG-PDP-DEACTIVATE-REQ NSAPI(s) tear down indicator, cause

SMREG-PDP-DEACTIVATE-CNF NSAPI(s)

SMREG-PDP-DEACTIVATE-IND NSAPI(s), tear down indicator, cause

SMREG-PDP-MODIFY-IND QoS, NSAPI

SMREG-PDP-MODIFY-REQ QoS, NSAPI, TFT

SMREG-PDP-MODIFY-CNF QoS, NSAPI

SMREG-PDP-MODIFY-REJ Cause, NSAPI

SMREG-PDP-ACTIVATE-SEC-REQ QoS, NSAPI, TFT, Primary NSAPI

SMREG-PDP-ACTIVATE-SEC-CNF QoS, NSAPI

SMREG-PDP-ACTIVATE-SEC-REJ Cause, NSAPI

3 GPP 04.07