GPRS basic

16/08/2009

For internal use 1 Nokia Siemens Networks

Agenda

Why GPRS ? GPRS Architecture GPRS Subscriptions GPRS Registration GPRS Mobility Management GPRS Session Management GPRS Channels

For internal use 2 Nokia Siemens Networks

GPRS Overview

For internal use 3 Nokia Siemens Networks

GSM Limitation:

Data Rates too slow about 9.6 kbps Connection setup time too long Inefficient resource utilization Circuit switched Charged by air-time have limited bandwidth no QOS

For internal use 4 Nokia Siemens Networks

GPRS- What is it?

Second generation GSM standard Wireless packet switched network Connections with different Packet data networks. GPRS supports
widely used IP & X.25. This is called as Packet Data Protocol (PDP) Uses GSM radio networks Strict separation between the radio sub-system and network subsystem - like the GSM system Several quality of services are supported.

For internal use 5 Nokia Siemens Networks

Comparison : GSM / GPRS

GSM Lower bit rates (up to 9.6kbit/s) Reserved bandwidth Fixed access time Time-based billing

GPRS Higher bit rates (up to 170kbit/s) Shared bandwidth Variable access times Traffic based billing

For internal use 6 Nokia Siemens Networks

Salient Features of GPRS

Important step on the path to 3G Standardized by ETSI GPRS is an overlay network over the GSM Provides Data Packet delivery service Support for leading internet communication protocols Billing based on volume of data transferred Utilizes existing GSM authentication and privacy procedures. Circuit switching & Packet Switching can be used in parallel Constant connectivity

For internal use 7 Nokia Siemens Networks

GPRS :Service Types

Bearer Services
Point-to-Point : Internet access by user Point-to-Multipoint : Delivery of information (e.g. news) to multiple locations or interactive conference applications

Supplementary Services
SMS Short Message Service CFU Call Forwarding Unconditional CFNRc Call Forwarding on mobile subscriber not reachable CUG Closed User Group

For internal use 8 Nokia Siemens Networks

A Third Generation of Mobile Systems: What for? The Wireless

Communications Generations
1st Generation 2nd Generation 2.5nd Generation 3rd Generation

Digital Analog National NMT TACS AMPS R2000 Digital Circuit mode only GSM CDMA (IS95) GSM + Packet mode GPRS EDGE HSCSD Worldwide IMT-2000 (ITU)

UMTS CDMA 2000

1990
For internal use 9 Nokia Siemens Networks

2000

A Third Generation of Mobile Systems: What for?

User bit rate

2 Mbps

IMT 2000 384 Kbps EDGE 144 Kbps Evolved 2G (GSM, HSCSD, and GPRS, IS-95B) 10 Kbps Basic 2G (GSM, IS-95) Fixed / Low mobility
For internal use 10 Nokia Siemens Networks

Wide area / High mobility

Applications and Services

1 - Mobile Services Evolution
1G GSM Ph 2+ GPRS UMTS
Streaming Video Location Based Services Internet/Intranet

Conversational Voice and Video

Multimedia Messages MMS Short Messages SMS Conversational Voice

For internal use 11 Nokia Siemens Networks

GPRS Architecture

For internal use 12 Nokia Siemens Networks

Changes to GSM network

Requires new network elements like SGSN and GGSN to integrate GPRS in GSM network. Changes are required to most existing GSM network elements including BTS, BSC, MSC (VLR and HLR) and OMC

For internal use 13 Nokia Siemens Networks

Mobile Systems Architecture

From GSM to GSM/GPRS Network
MSC Um BSC Abis MS BTS Ater TRAU A VLR C PSTN

HLR /AuC
Agprs Gr Gb Frame Relay Backbone Gb Gn SGSN

GGSN Private IP Backbone

Gn Gi

PCU

External Packet Network Intranet, Internet

For internal use 14 Nokia Siemens Networks

GPRS SYSTEM ARCHITECTURE

Other GPRS PLMN SMS-GMSC SMS-INMSC Gd SGSN Gp GGSN Gb Gf BTS BSC Gs Gc BTS EIR MS D
For internal use 15 Nokia Siemens Networks

Gn GGSN Gr PDN Gi

HLR+GPRS Register

MSC/VLR

GPRS Mobile Stations

An MS in
Class-A mode of operation operates GPRS and other GSM services simultaneously. Class-B mode of operation monitors control channels for GPRS and other GSM services, but can only operate one set of services at one time. Class-C mode of operation exclusively operates GPRS services.

For internal use 16 Nokia Siemens Networks

BSS - Packet Control Unit

Packet scheduling Channel access control functions - access request,
access grant etc. Radio channel management functions - power control, congestion control, broadcast control Can be implemented in BTS, BSC or SGSN (mostly implemented in BSC)

For internal use 17 Nokia Siemens Networks

SGSN
Serving GPRS Support Node(SGSN) serves a similar
role to the MSC/VLR for the GPRS network. SGSN is the node that is serving the MS. The SGSN is responsible for:

Logical connections to GPRS Mobile Stations Mobility Management At PS attach, the SGSN establishes a mobility management
context containing information pertaining to e.g. mobility and security for the MS. Packet routing and transmission into the GPRS network At PDP Context Activation, the SGSN establishes a PDP context, to be used for routeing purposes, with the GGSN that the subscriber will be using. Authentication, Encryption GSM Circuit Switched interactions (Paging)

For internal use 18 Nokia Siemens Networks

GGSN
The GGSN is the gateway, Router and Firewall in and out of the
GPRS system.

The GGSN is the first point of PDN interconnection with a GSM

PLMN supporting GPRS

It contains routing information for attached GPRS users. It routes

packets from an external network to the MS and routes packets from the MS to the external network, transparently through the SGSN. This concept is called tunneling.

Responsible for : Packet translation from GSM<->Packet Data Network(IP) Packet routing and transmission Mobility Management Access Control (security and roaming ) Charging

For internal use 19 Nokia Siemens Networks

GPRS interfaces

For internal use 20 Nokia Siemens Networks

10

Interfaces (GSN HLR)

Gr Interface The Gr interface is located between the SGSN and the HLR. It involves the MAP (Mobile Application Part), TCAP, SCCP, and MTP3/2 layers. MM procedures (update/cancel location) use MAP protocol on this interface. Ge Interface The Ge interface is located between the GGSN and the HLR. It involves the MAP (Mobile Application Part), TCAP, SCCP, and MTP3/2 layers.

For internal use 21 Nokia Siemens Networks

Interfaces... ( SGSN GGSN)

Gn Interface The Gn interface is located between the GSNs.(SGSN or GGSN). It involves the GTP, User Datagram Protocol (UDP) and Internet Protocol (IP) layers. The GTP on this interface includes both signalling and data transfer procedures. The following functions are managed through this interface:
PDP context creation/ deletion/ modification, route monitoring.

Gp interface is used for the same function if the GSN

belongs to a different PLMN.

For internal use 22 Nokia Siemens Networks

11

Interfaces..
Gs Interface ( MSC/VLR SGSN) The Gs interface is located between the MSC/VLR and the SGSN. It involves the BSSAP+ (Base Station System Application Part +), SCCP and MTP3/2 layers. Through this interface, an association is created between SGSN and MSC/VLR. This association is used for coordinating MSs that are both GPRS-attached and IMSIattached (coordination of LA and RA update, CS paging via SGSN,...).

For internal use 23 Nokia Siemens Networks

Interfaces.. ( SSN EIR)

Gf Interface The Gf interface is located between the SGSN and the EIR. It involves the MAP (Mobile Application Part), TCAP, SCCP, and MTP3/2 layers. The Ge Interface The Ge interface is located between the GGSN and the HLR. It involves the MAP (Mobile Application Part), TCAP, SCCP, and MTP3/2 layers .

For internal use 24 Nokia Siemens Networks

12

GPRS Subscription Information

For internal use 25 Nokia Siemens Networks

GPRS Subscription Principles.

Subscription is permanently stored in the HLR When a MS performs GPRS Attach, the subscription
information is copied to the SGSN. When the MS changes SGSN, the subscription information is copied to the new SGSN. When the MS activates a PDP context, the relevant info is copied to the GGSN.

For internal use 26 Nokia Siemens Networks

13

Information in HLR
Field Description IMSI MSISDN SGSN Number SGSN Address SMS Parameters MS purged for GPRS MNRG IMSI is the main reference key MSISDN of the MS for SMS The SS7 address of the SGSN currently serving this MS. The IP address of the SGSN currently serving this MS. SMS related parameters.e.g., operator determined barring. Indicates that the MM and PDP contexts of a MS are deleted from the SGSN. Indicates that the MS is not reachable though a SGSN, and that the MS is marked as not reachable for GPRS at the SGSN and possible at the GGSN

GGSN list

The GGSN number and optional IP address pair relate to the GGSN that shall be contacted when activity from the MS is detected and MNRG is set.

Each IMSI contains zero or more of the following PDP context subscription records

PDP type PDP address QoS profile Subscribed VPLMN address Allowed Access point name

PDP type e.g., X.25, IP E.g., X.121 address. This field is empty if dynamic addressing is allowed. The QoS profile subscribed for thid PDP context.

A label according to DNS naming conventions describing the access point to the external packet data network

For internal use 27 Nokia Siemens Networks

HLR Subscription information: Generic, common data.

Static Data Permanently set during subscription. IMSI :The main identifier of the subscriber. MSISDN Dynamic data SGSN SS7 number :SS7 address of the SGSN currently serving the MS. SGSN Address :IP address of the SGSN currently serving the MS. SMS Parameters MS purged for GPRS :Indicates whether the MS context is stored in
listed SGSN.

For internal use 28 Nokia Siemens Networks

14

HLR Subscription information: Generic, common data.

Dynamic data (contd.) GGSN List
List of GGSNs that are serving the network requested PDP context
activation and while the MS has been detached, these GGSNs has got MT packets. These GGSNs will be informed when the MS is attached again.

MNRG
Indicates whether the MS is not currently reachable and, next time
when the MS becomes attached again, the GGSNs in the list shall be informed. Used for network requested context activation.

For internal use 29 Nokia Siemens Networks

HLR Subscription information: PDP Context dependent data.

One PDP Context PDP type:
Identifies the type of the protocol. E.g., IP.

PDP Address
Address of the protocol

QoS profile
Default QoS for this PDP context.

GGSN address/ Access point name

Access point definition, I.e., a logical address of the GGSN that is
serving this PDP context.

For internal use 30 Nokia Siemens Networks

15

QoS Parameters...
QoS Parameters
Precedence class (priority)

Definition
In the case of limited resources, data packets of services with low values are discarded first.

Delay class

The transfer of a data packet through the network takes acertain amount of time, which is called delay time. The acceptable delay time depends on the type of the service e.g.,: Twoway real-time (telephony), one-way real-time (video), interactive, non-real-time (web browsing), background non-real-time (SMS). Considers the probability of errors - e.g., data loss, data delivery out of sequence, duplicate data delivery, data corruption. Limits the rate at which data is transferred through the network Specifies the average rate at which data is expected to be transferred through the network during the activation period of a PDP context.

Reliability class Peak throughput

Mean throughput
For internal use 31 Nokia Siemens Networks

Quality Of Service
Default QoS per user is defined in the HLR SGSN has the main control on QoS MS request the QoS during PDP Context activation SGSN can downgrade the MSs requested QoS. GGSN may further downgrade the requested QoS.

For internal use 32 Nokia Siemens Networks

16

Mobile External Identities

Identities visible to users and/or external networks Addressing the mobile Phone number
Used for CS services and SMS GPRS does not normally use phone numbers.

IPv4 address
Used when user has subscribed IP access service The address is visible to external packet data network.

IPv4 logical name

Based on DNS convention

For internal use 33 Nokia Siemens Networks

Mobile External Identities...

Access Point name (APN) Defines two identities
GGSN that handles a context of the MS In addition, a route from GGSN to external networks.

APN format is based on the DNS naming

conventions..possible names would be --airdata.com.mnc40.mcc400.gprs Name allocation follows the public internet DNS domain reservation.

For internal use 34 Nokia Siemens Networks

17

Mobile Internal Identities

Internal Identities, global IMSI = MCC +MNC + MSIN (Like in GSM) IMEI Internal Identities, over radio P TMSI (for user confidentiality) TLLI (Used in identifying the MS in the LLC level and below) NSAPI
Specifies the PDP context at the SNDCP level over the radio. NSAPIs are allocated dynamically by the MS for each context
during context activation

For internal use 35 Nokia Siemens Networks

Mobile Internal Identities ...

Internal Identities, over radio..contd LAI = MCC+MNC (operator code) + LAC.
Defines the LA where the MS is currently located.

Cell id (CI) -- defines the cell where MS is currently located. RAI = MCC +MNC+LAC+RAC
SGSNs servicing a specific routing area can be defined using the DNS
naming convention as RACxx.LACyy.MNCzz.MCCqq.gprs

For internal use 36 Nokia Siemens Networks

18

GPRS Procedures
Registration (Attach) Session management Location management

For internal use 37 Nokia Siemens Networks

GPRS Registration

For internal use 38 Nokia Siemens Networks

19

GPRS Registration - GPRS attach

An MS shall perform a GPRS Attach to the SGSN in order to obtain access to the GPRS services The MS shall provide its identity and an indication of which type of attach that is to be executed. The identity provided to the network shall be the MS's Packet TMSI (P-TMSI) or IMSI. Authentication check from HLR Download MSs subscription information from HLR to SGSN If SGSN does not already have that info. Update MSC/VLR, If also IMSI Attach is performed. SGSN assign a packet temporary mobile subscriber identity (P-TMSI) to the user. After having executed the GPRS attach, the MS is in READY state and MM contexts are established in the MS and the SGSN. The MS may then activate PDP contexts as described in clause "Activation Procedures".
For internal use 39 Nokia Siemens Networks

GPRS Attach procedure

MS BSS New SGSN Old SGSN HLR

1. Attach request (TMSI)

Authentication
Update Location Request Cancel Location Cancel Location Ack Insert Subscribers data Insert Subscribers data Ack Update Location Ack Attach Accept

Attach Complete

For internal use 40 Nokia Siemens Networks

20

Combined GPRS and IMSI Attach procedure

MS BSS New SGSN Old SGSN New EIR

MSC/VLR

HLR

Old

MSC/VLR

1. Attach request 2. Identification Request 3. Identity Request 3. Identity Response 2. Identification Response 4..Authentication 6a. Update Location 6b. Cancel Location 6c.Insert Subscribers data 6d. Update Location Ack 7a. Location Updating Request 7b. Update Location 7c. Cancel Location 7e.Insert Subscribers data 7h. Location Updating Accept 8. Attach Accept 9. Attach Complete
For internal use 41 Nokia Siemens Networks

7g. Update Location Ack

GPRS Detach
An MS to inform the network that it does not want to access the SGSN-based services any longer The network to inform an MS that it does not have access to the SGSNbased services any more. The different types of detach are: IMSI detach;
GPRS detach; and combined GPRS / IMSI detach (MS-initiated only).

The MS is detached either explicitly or implicitly:

Explicit detach: The network or the MS explicitly requests detach. Implicit detach: The network detaches the MS, without notifying the MS, a configuration-dependent time after the mobile reachable timer expired, or after an irrecoverable radio error causes disconnection of the logical link.

In the Mobile-originated Detach Request message there is an indication to tell if the detach is due to switch off or not. The indication is needed to know whether a Detach Accept message should be returned or not. In the network-originated Detach Request message there may be an indication to tell the MS that it is requested to initiate GPRS Attach and PDP Context Activation procedures for the previously activated PDP contexts.
For internal use 42 Nokia Siemens Networks

21

MS initiated Detach Procedure

MS BS S/U T R AN 1. D e tach R e q u est (A ) 2. D e le te P D P C on te xt R e q u est 2 . D e le te P D P C on te xt R e sp o ns e SG S N G G SN M SC /V LR

3 . IM SI D e ta ch Ind ica tio n 4. G PR S D e tac h In d ica tio n 5 . D e ta ch Accep t 6 . PS Sig n a llin g C o nne ctio n R e le a se

For internal use 43 Nokia Siemens Networks

Network Initiated Detach Procedure

MS BSS/UTRAN SGSN GGSN MSC/VLR
MS BSS/UTRAN SGSN GGSN HLR MSC/VLR 1. Cancel Location (A) 3. Delete PDP Context Request 3. Delete PDP Context Response C1

1. Detach Request (A) 2. Delete PDP Context Request 2. Delete PDP Context Response C1 3. GPRS Detach Indication 4. Detach Accept C2

2. Detach Request

4. GPRS Detach Indication 5. Detach Accept C2 6. Cancel Location Ack

5. PS Signalling Connection Release

7. PS Signalling Connection Release

For internal use 44 Nokia Siemens Networks

22

GPRS Session Management

For internal use 45 Nokia Siemens Networks

Session Management
Mobile Station applies for PDP address For each session PDP context is created & it contains PDP type PDP addressed assigned to MS Address of GGSN that servers access point
to PDN With active PDP context MS able to send or receive data packets Allocation of PDP address can be static or dynamic

For internal use 46 Nokia Siemens Networks

23

Session management

A GPRS subscription contains the subscription of one or more PDP addresses Each PDP address is described by an individual PDP context in the MS, the SGSN, and the GGSN. Every PDP context exists independently in one of two PDP states. The PDP state indicates whether the PDP address is activated for data transfer or not All PDP contexts of a subscriber are associated with the same MM context for the IMSI of that subscriber

For internal use 47 Nokia Siemens Networks

PDP STATES

INACTIVE

Activate PDP Context

Deactivate PDP Context or MM state change to IDLE

ACTIVE

Functional PDP State Model

For internal use 48 Nokia Siemens Networks

24

PDP ADDRESS
Static PDP Address PDP address assigned permanently to the MS For every MS one or more static PDP address per PDP Type can be subscribed to Dynamic PDP Address PDP address assigned to the MS once a PDP context is activated . For every MS one or more dynamic PDP address per PDP Type can be assigned

For internal use 49 Nokia Siemens Networks

PDP Context examples: Static IP address

PDP Type: IPv4 PDP address: 131.228.13.55 QoS profile: Precedence : high Reliability class : 2 ( GTP : unacknowledged, LLC :acknowledged, protected, RLC : acknowledged ) Delay class : 0.5s Mean throughput : 10kbps. Peak throughput : 40kbps. GGSN address : abc.xyz.MNC40.MCC350.gprs

For internal use 50 Nokia Siemens Networks

25

PDP Context examples: Dynamic IP address

PDP Type: IPv4 PDP address: *. *. *. *. ( dynamic) QoS profile: Precedence : medium Reliability class : 2 ( GTP : unacknowledged, LLC :acknowledged, protected, RLC : acknowledged ) Delay class : 0.5s Mean throughput : 10kbps. Peak throughput : 20kbps. GGSN address : abc.xyz.MNC40.MCC350.gprs

For internal use 51 Nokia Siemens Networks

PDP Context Activation

Packet Data Protocol (PDP) context activation per protocol &
QoS, activated by the network or the MS once in ready or standby state PDP contexts remain active until: - the MM moves to the idle state - the MS or Network moves the user to inactive state MS Initiated informs the network that it wants to activate PDP context
PDP type, PDP Address,QoS parameters. SGSN checks that MS is allowed to activate the context

SGSN selects GGSN to be used QoS negotiation

For internal use 52 Nokia Siemens Networks

26

SM-PDP Context activation

SGSN

MS
Activate PDP context Request

GGSN

[ PDP type, PDP addr, QoS

requested , access point,..] Security Functions Create PDP context request [ PDP type, PDP addr, QoS negotiated , access point,..] Create PDP context response [ PDP type, QoS negotiated , access point,..]

Activate PDP context Accept

[ PDP type, PDP addr, QoS

negotiated,]
For internal use 53 Nokia Siemens Networks

Location Management

For internal use 54 Nokia Siemens Networks

27

Location/Mobility Management

The mobility management functions are used to keep track of the

current location of an MS within the PLMN or within another PLMN. The Mobility Management (MM) activities related to a subscriber are characterised by one of three different MM states. The MM states for a GPRS subscriber are IDLE STANDBY READY

For internal use 55 Nokia Siemens Networks

MS States
No or Very Low Traffic

IDLE

MS is not reachable. No PDP or MM context exit in network

GPRS Attach

GPRS Detach Every movement of MS is updated in SGSN

High Traffic

Standby Timer Expired

READY

Ready Timer Expired OR Forced

Packet Sent

Medium Traffic

STANDBY

Movement across cell is not updated. Movement across RA is updated

For internal use 56 Nokia Siemens Networks

28

Routing Area
GPRS introduces a new network area - RA RA can consists of one or more cells RA is always served by only one SGSN One SGSN can serve more than one RA 1 cell < RA < LA.
SGSN 2 SGSN 1

X
RA LA

RA RA

RA 1

RA 2

For internal use 57 Nokia Siemens Networks

When Updates are Sent

If MS is in IDLE state No location update message is sent No matter how fast and how far the mobile moves

If MS is in STANDBY state If mobile moves across routing areas then update message is sent to the SGSN If mobile moves across cells in a routing area, no update message is sent to SGSN If MS is in READY state If a mobile moves across any cell, an update message is sent to SGSN.
For internal use 58 Nokia Siemens Networks

29

State Model of GPRS MS

For internal use 59 Nokia Siemens Networks

Idle State
In GPRS IDLE state, the subscriber is not attached to
GPRS mobility management. The MS and SGSN contexts hold no valid location or routeing information for the subscriber. The subscriber-related mobility management procedures are not performed. Data transmission to and from the mobile subscriber as well as the paging of the subscriber is not possible. The GPRS MS is seen as not reachable in this case. In order to establish MM contexts in the MS and the SGSN, the MS shall perform the GPRS Attach procedure

For internal use 60 Nokia Siemens Networks

30

STANDBY State

Is attached to GPRS mobility management. MS and SGSN have established MM contexts. Pages for data or signalling information transfers may be received. It is also possible to receive pages for the CS services via the SGSN Data reception and transmission are not possible in this state. The MS performs GPRS Routeing Area (RA) and GPRS cell selection and reselection locally. The MS executes mobility management procedures to inform the SGSN when it has entered a new RA The MS does not inform the SGSN on a change of cell in the same RA. Therefore, the location information in the SGSN MM context contains only the GPRS RAI for MSs in STANDBY state. A PDP context shall be activated before data is transmitted or received. The MM state in the MS is changed to READY when the MS responds to the page, and in the SGSN when the page response is received Also, the MM state in the MS is changed to READY when data or signalling information is sent from the MS and, accordingly, the MM state in the SGSN is changed to READY when data or signalling information is received from the MS. The MS or the network may initiate the GPRS Detach procedure to move to the IDLE state. After expiry of the mobile reachable timer the SGSN may perform an implicit detach in order to return the MM contexts in the SGSN to IDLE state. The MM and PDP contexts may then be deleted.

For internal use 61 Nokia Siemens Networks

READY State
In READY state, the SGSN MM context corresponds to the STANDBY MM
context extended by location information for the subscriber on the cell level. The MS performs mobility management procedures to provide the network with the actual selected cell. The MS may send and receive PDP PDUs in this state. The SGSN transfers downlink data to the BSS responsible for the subscriber's actual GPRS cell. The MS may activate or deactivate PDP contexts while in READY state. Regardless if a radio resource is allocated to the subscriber or not, the MM context remains in the READY state even when there is no data being communicated

A timer supervises the READY state. An MM context moves from READY

state to STANDBY state when the READY timer expires. In order to move from READY state to IDLE state, the MS initiates the GPRS Detach procedure.
For internal use 62 Nokia Siemens Networks

31

Mobility Management : Changes in States

Standby -> Ready
When MS sends a packet, starts ready timer PDU transmission: The MS sends an LLC PDU to the SGSN, possibly in response to a page. PDU reception: The SGSN receives an LLC PDU from the MS.

Ready -> Standby

READY timer expiry: The MS and the SGSN MM contexts return to STANDBY state. Force to STANDBY: The SGSN indicates an immediate return to STANDBY state before the READY
timer expires.

Abnormal RLC condition: The SGSN MM context returns to STANDBY state in case of delivery
problems on the radio interface or in case of irrecoverable disruption of a radio transmission.

Idle -> Ready

GPRS Attach: The MS requests access and a logical link to an SGSN is initiated. MM contexts are
established at the MS and SGSN.

Standby -> Idle

Implicit Detach: The MM and PDP contexts in the SGSN shall return to IDLE and INACTIVE state. The MM and PDP contexts in the SGSN may be deleted. The GGSN PDP contexts shall be deleted. Cancel Location: The SGSN receives a MAP Cancel Location message from the HLR, and removes
the MM and PDP contexts.

Ready -> Idle

GPRS Detach: The MS or the network requests that the MM contexts return to IDLE state and that
the PDP contexts return to INACTIVE state. The SGSN may delete the MM and PDP contexts.

Cancel Location: The SGSN receives a MAP Cancel Location message from the HLR, and removes
the MM and PDP contexts

For internal use 63 Nokia Siemens Networks

Mobility Management : GPRS MM States

ID L E ID L E

G P R S A tta c h

G P R S D e ta c h

G P R S A tta c h

G P R S D e ta c h or C a n c e l L o c a ti o n

READY

I m p li c it D e ta c h or C a n c e l L o c a tio n

READY

R E A D Y t im e r e x p ir y or F o r c e to S T A N D B Y

P D U tr a n s m i s s io n

R E A D Y tim e r e x p i ry or F o rc e to S T A N D B Y or A b n o r m a l R L C c o n d itio n

P D U r e c e p ti o n

STANDBY

STANDBY

M M S tate M o de l o f M S
For internal use 64 Nokia Siemens Networks

M M S ta t e M o d e l o f S G S N

32

Routing Area Update

SGSN is informed when MS moves to a new RA MS sends a Routing Area Update Request to its assigned SGSN Two Types Inter SGSN Routing Area Update Intra SGSN Routing Area Update Combined RA / LA Updating
When the MS is both IMSI and GPRS-attached, the LA and RA updating is done
in a co-ordinated way to save radio resources

When the MS enters a new RA in network operation mode I, the MS sends a

Routeing Area Update Request message to the SGSN, as described in clause "Combined RA / LA Update Procedure". The LA update is included in the RA update. The SGSN then forwards the LA update to the MSC/VLR. The MSC/VLR optionally returns a new VLR TMSI that is sent to the MS via the SGSN.

For internal use 65 Nokia Siemens Networks

Intra SGSN Routing Area Update

MS

BSS

SGSN

1. Routeing Area Update Request 2. Security Functions 3. Routeing Area Update Accept C1 4. Routeing Area Update Complete

For internal use 66 Nokia Siemens Networks

33

Inter SGSN Routing Area Update

MS BSS new SGSN old SGSN GGSN HLR 1. Routeing Area Update Request 2. SGSN Context Request 2. SGSN Context Response 3. Security Functions (A) 4. SGSN Context Acknowledge C1 5. Forward Packets (B) 6. Update PDP Context Request 6. Update PDP Context Response 7. Update Location 8. Cancel Location 8. Cancel Location Ack 9. Insert Subscriber Data 9. Insert Subscriber Data Ack 10. Update Location Ack C2 11. Routeing Area Update Accept C3 12. Routeing Area Update Complete
For internal use 67 Nokia Siemens Networks

Combined Intra SGSN RA / LA Update

MS BSS S G SN ne w M S C /V L R HLR o ld M S C /V L R 1 . R o ut eing A re a U p d a te R e q ue st 2 . S e cu r ity F u n ct io ns 3 . L o c a tio n U p da te R e q u e st 4 a . U p d a te L o c a tio n 4 b. C a nc e l L o c a tio n 4 c . C an ce l L o c a tio n A c k 4 d . Inse rt S u bsc ribe r D a ta 4 e . Inse rt S u bsc ribe r D a ta A c k 4 f. U p d a te L o c a tio n A c k 5 . L o c a tio n U p da te A c ce p t 6 . R o ut eing A re a U p d a te A c c e p t C1 7 . R o ut eing A re a U p d a te C o m p le te 8 . T M S I R e a llo ca tio n C o m p le te
For internal use 68 Nokia Siemens Networks

34

CS Paging
When an MS is both IMSI and GPRS-attached , the MSC/VLR executes
paging for circuit-switched services via the SGSN.

If the MS is in STANDBY state, it is paged in the routeing area and If the

MS is in READY state, it is paged in the cell. The SGSN converts the MSC paging message into an SGSN paging message.

MS

BSS

SGSN 1. Page

MSC/VLR

2. Paging Request 3. Paging Request 4. SABM (Paging Response) 5. SCCP Connection Request (Paging Response)

For internal use 69 Nokia Siemens Networks

GPRS Channels

For internal use 70 Nokia Siemens Networks

35

Channels in GPRS

Logical Channel Traffic Channels Signaling Channels (Control Channels)

Physical Channels

For internal use 71 Nokia Siemens Networks

Logical Channels
Group Packet data traffic channel Packet broadcast control channel Packet common control channel (PCCCH) Packet dedicated control channels For internal use
72 Nokia Siemens Networks

Cha nnel PDTCH

Function Data traffic

Dire ction MS BSS

PBCCH

Broadcast control

MS

BSS

PRACH PAGCH PPCH PNCH PACCH PTCCH

Random access Access grant Paging Notification Associated control Timing adv ance control

MS MS MS MS MS MS

BSS BSS BSS BSS BSS BSS

36

Packet Data Channel(PDCH)

Physical Channel for GPRS Traffic PDCH are taken from all channels available in the cell Depending on current traffic load and priority of service, the physical
channel are allocated to either GPRS or GSM services. Physical channels not currently used by GSM can be allocated as PDCH to increase the QOS for GPRS

For internal use 73 Nokia Siemens Networks

Billing
GPRS call records are generated in the GSNs. GSNs may not be able to store charging information. Packet counts are passed to Charging Gateway (CG)
that generates Call Detail Records (CDR), that are sent to the billing system. Tariff is on a certain amounts of GPRS traffic at a flat rate and monitor whether these allocations are exceeded.

For internal use 74 Nokia Siemens Networks

37

Limitations of GPRS
Speed much lower in reality, It is unlikely that a network operator will
assign all time slots for GPRS GPRS uses GMSK as compare to 8-PSK in EDGE which allows much higher bit rate over the air interface. Packets are routed indifferent direction ( like in the internet) and retransmissions as part of data integrity introduces delays. No store and forward

For internal use 75 Nokia Siemens Networks

Thanks for your time

For internal use 76 Nokia Siemens Networks

38