GPRS

Mobility Management MM

After attachment procedure the network assigns a TLLI (temporary logical link identifier ) The mobile uses this TLLI after the network assigns P_TMSI (packet TMSI). Three mobility management states are related to GPRS subscriber and each level describe the level of functionality and information allocated. In Idle state the subscriber isn t yet attached. Ready state the MS is attached to the GPRS MM and is known in the accuracy of the cell. Each cell has its CGI , each cell is associated with a LA , but in GPRS its associated with a routing area. If the ready timer for the MS expired , the MS is moved to standby state. In standby state , the subscriber is attached to GPRS MM and is known in the accuracy of the routing area. States transitions :

Attach procedures : there are 3 types of attach as follows : GPRS attach : needs the P-TMSI and RAI IMSI attach : specific to GSM , but may be performed by GPRS if P-TMSI or TMSI are allocated yet to the mobile. IMSI/GPRS attach (for class A and MS)

GPRS Attached Scenario:

1. The mobile station sends an attach request with its identity (P_TMSI or TMSI) to the SGSN. This message will also contain a Network Service Area Point Identifier (NSAPI), which is specific to a particular network application at the mobile station. The Subnetwork-Dependent Convergence Protocol (SNDCP) layer uses this NSAPI to communicate with the network application. Several NSAPIs may be associated with an individual mobile station. One may be for an Internet browser, whereas another could be an e-mail service. 2. The SGSN verifies whether the user is authorized and authenticated for that particular service by checking with the HLR entry for the mobile station. 3. After authorization, the SGSN sends back a reply to the mobile station with a TLLI. The TLLI is specific to the mobile and is used by the Logical Link Control (LLC) layer in the protocol stack. The purpose of this TTLI is to provide a temporary ID to the mobile station, which can be used for data communication. 4. A database is maintained at the SGSN that maps the mobile identity with the TLLI assigned to it. The NSAPI is associated with and The table of entries for the SGSN correlations of attached mobiles shown in Figure 5-6 is updated after the PDP activation phase.

PDP context can be activated or deactivated . Three PDP context functions are ,activate , deactivate , modify. The MS is responsible for activation and deactivation. GGSN is responsible for activation (for incoming packets ) and deactivation. SGSN is responsible for modification. Packet Data Protocol (PDP): Session Logical tunnel between MS and GGSN Anchored GGSN for session PDP Context activities Activation Modification Deactivation Each active PDP Context stores: Requested QoS profile Subscribed QoS profile Negotiated QoS profile GPRS has two main types of CDR s: G-CDRCreated by GGSN and used for local subscribers charging. S-CDRCreated by SGSN and used for inbound roomers charging.

NSAPI

It is used to identify a Packet Data Protocol (PDP) context (a unique data session) in the Mobile Station (MS) and in the Serving GPRS Support Node (SGSN). It is dynamically selected by the MS (however, the MS should ensure that the selected NSAPI is not currently being used by another session management entity in the MS). When the MS requests a PDP context, it selects an NSAPI that it sends to the SGSN with the request.

y -

How to locate correct GGSN ? SGSN resolves an Access Point Name (APN) into the IP address for the GGSN connected to the target networkusing DNS Billing on CS is time based but in PS is volume based , the need for GPRS emerged from the bursty native of data which led to insufficient use of resources of allocated TCH in GSM.

y -

SGSN Tasks: Packet routing and transfer. mobility management (attach/detach and location management) Logical link management, and authentication, and charging functions. The location register of the SGSNstores location information (e.g., current cell, current VLR) And user profiles (e.g., IMSI, address (es) used in the packetdata network) of all GPRS users registered with this SGSN.

y -

GGSN Tasks:

A gateway GPRS support node (GGSN) acts as an interface between the GPRS backbone network and the externalpacket data networks. - It converts the GPRS packets coming from the SGSN into the appropriate packet data protocol (PDP) format (e.g., IP or X.25) and sends them out on the corresponding packet data network - In the other direction, PDP addresses of incoming data packets are converted to the GSM address of the destination user. The readdressed packets aresent to the responsible SGSN. For this purpose, the GGSN stores thecurrent SGSN address of the user andhis or her profile in its location register. - The GGSN also performs authenticationand charging functions.

Gprs interfaces

GPRS scenarios :

1- Attach scenario
a- A TLLI might be neede in the first attach otherwise the TLLI might be deleted because a failure occurred before. Additional sub-scenarios might include: b- A sub-scenario may arise during this situation when MS-Service Data is available in the SLR. When this occurs, the SGSN will start authenticating and ciphering. When authentication is successful, the Routing Area Code or RAC will be stored in the SLR and a new TLLI can be allocated. Also, during this process, the SGSN is waiting for the Attach Complete message from the MS that confirms the new TLLI. cAnother situation might occur if MS-Service Data is not available in the SLR. With a first dialog, the SGSN retrieves the authentication triplets from the HLR AC by using the MAP message SendAuthenticationInfo. If successful, the triplets will be stored in the SLR and the SGSN will start authentication and ciphering. When authentication is complete, the new RAC will be stored in the SLR. With a second dialog, the SGSN will retrieve the remaining MSservice data from the HLR using MAP message UpdateGPRSLocation. If this inter-working is successful, the retrieved data from HLR will be stored in the SLR. The GPRS Attach is then accepted by the SGSN.

2- Detach scenario
The example on this slide illustrates the Gb Interface-Detach Procedure. a- The MS detaches by sending a Detach Request with Information Elements message Detach Type and Switch Off, for example to the SGSN. Detach Type indicates which kind of detach will be performed. Some examples include GPRS Detach only, IMSI Detach only, or a combined GPRS and IMSI Detach. Switch Off indicates whether or not detach is caused by a switch off situation. b- If GPRS detach is detected, the GGSN s active PDP contexts regarding this MS are deactivated by the SGSN sending GPRS Tunnelling Protocol to the GGSNs. Specifically, it sends a Delete PDP Context Request message using either Tunnel ID, also called TID or a Tunnel Endpoint Identifier, or TEID. The GGSNs acknowledge with a Delete PDP Context Response using TID or TEID. c- In case of IMSI detach, the SGSN sends an IMSI Detach Indication to the VLR. If the MS wants to remain IMSI-attached but is doing a GPRS detach, the SGSN sends a GPRS Detach Indication message to the VLR. The VLR removes the association with the SGSN and handles paging and location updating without going through the SGSN. If Switch Off indicates that detach is not due to a switch off situation, the SGSN sends a Detach Accept message to the MS.

This table provides a sample of the GPRS Mobility Management reject cause values. This list is noninclusive of all available reject causes.

This figure illustrates the Gn interface protocols used on the different layers of the protocol stack with a typical configuration example. The Gn interface lies between two GPRS Support Nodes within the same PLMN. In the intra-PLMN backbone, the Gn provides both a data and signaling interface.

3- Call flow Gn interface PDP context activate procedure

The example here illustrates the Gn Interface PDP Context Activate procedure. First , the MS sends an Activate PDP Context Request message, which is not shown, to the SGSN that contains the following Information Elements: Protocol Discriminator plus Transaction Identifier, referred to as PD+TI Logical Link Code Service Access Point Identifier, or LLC SAPI NSAPI PDP Type PDP Address Access Point Name, or APN Quality of Service Requested And PDP Configuration Options The SGSN can validate the Activate PDP Context Request by using the PDP Type, PDP Address, or APN provided by the MS and the PDP context subscription records. If no GGSN address can be derived or if the Activate PDP Context Request is not valid, then the SGSN rejects the PDP context activation request. If a GGSN address can be derived, the SGSN creates a GTP Tunnel for the requested PDP context, which is shown as the GTP Create PDP Context Request message in the figure on the screen. If the MS requests a dynamic PDP address, the GGSN allocates the address. The GGSN then sends a GTP Create PDP Context Response message to the SGSN. The SGSN then inserts the NSAPI along with the GGSN address in its PDP context. If the MS has requested a dynamic address, the PDP address received from the GGSN is inserted. Then, the SGSN selects a Radio Priority Level based on the level of negotiated QoS, and returns an Activate PDP Context Accept message to the MS, which is not shown. The SGSN is now able to route PDP PDUs between the GGSN and the MS.

This table provides a sample of the Gn Interface cause values. The list is non-inclusive of all cause values.