P 97 076

ETSI TC SMG
Meeting #21
Paris, 10th - 14th February 1997
TDoc SMG 76/97
Source:
SMG 3
Title:
GSM 03.60 version 1.0.0 General Packet Radio Service Stage 2 Description
Proposed agenda item: 6.4
Presented for: Information
GSM
TECHNICAL
SPECIFICATION
GSM 03.60
31st January 1997
Version 1.0.0
Source: ETSI TC-SMG
Reference:
ICS:
Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM)
Digital cellular telecommunications system (Phase 2+);

General Packet Radio Service (GPRS);
Service Description;
Stage 2;
(GSM 03.60)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
Postal address: F-06921 Sophia Antipolis CEDEX - FRANCE
Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
X.400: c=fr, a=atlas, p=etsi, s=secretariat - Internet: secretariat@etsi.fr
Tel.: +33 4 92 94 42 00 - Fax: +33 4 93 65 47 16
Copyright Notification: No part may be reproduced except as authorised by written permission. The copyright and
the foregoing restriction extend to reproduction in all media.
European Telecommunications Standards Institute 1997. All rights reserved.
Page 2
GSM 03.60, version 1.0.0, 31st January, 1997
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.
Page 3
Contents
1. Scope.........................................................................................................................................................5
2. Normative References...............................................................................................................................5
3. Definitions and Abbreviations ....................................................................................................................6
3.1 Definitions......................................................................................................................................6
3.2 Abbreviations.................................................................................................................................6
4. Main Concepts...........................................................................................................................................7
5. General GPRS Architecture and Transmission Mechanism .....................................................................7
5.1 GPRS Access Interfaces and Reference Points ...........................................................................7
5.2 Network Interworking.....................................................................................................................8
5.2.1 PSPDN Interworking ...................................................................................................8
5.2.2 Internet (IP) Interworking ............................................................................................8
5.3 High-Level Functions Required for GPRS.....................................................................................8
5.3.1 Network Access Control Functions.............................................................................9
5.3.2 Packet Routing and Transfer Functions ...................................................................10
5.3.3 Mobility Management Functions ...............................................................................10
5.3.4 Logical Link Management Functions ........................................................................11
5.3.5 Radio Resource Management Functions .................................................................11
5.3.6 Network Management Functions ..............................................................................12
5.4 Logical Architecture.....................................................................................................................12
5.4.1 GPRS Support Nodes...............................................................................................12
5.4.2 GPRS Backbone Networks.......................................................................................13
5.4.3 HLR .......................................................................................................................13
5.4.4 SMS-GMSC and SMS-IWMSC.................................................................................13
5.5 Assignment of Functions to General Logical Architecture ..........................................................14
5.6 Transmission and Signalling Planes ...........................................................................................15
5.6.1 Transmission Plane ..................................................................................................15
5.6.2 Signalling Plane ........................................................................................................16
6. Functional Model .....................................................................................................................................18
6.1 Mobility Management Functionality .............................................................................................18
6.1.1 Definition of Mobility Management States.................................................................18
6.1.2 IDLE / STANDBY / READY State Functionality ........................................................20
6.1.3 Interactions Between SGSN and MSC/VLR .............................................................21
6.1.4 MM Procedures.........................................................................................................26
6.1.5 Attach Function .........................................................................................................26
6.1.6 Detach Function........................................................................................................29
6.1.7 Security Function ......................................................................................................30
6.1.8 Location Management Function................................................................................32
6.1.9 PDP Context Activation and Deactivation Functions ................................................40
6.2 Network Management Functionality ............................................................................................42
6.3 Radio Resource Functionality......................................................................................................43
6.3.1 Cell Selection and Reselection .................................................................................43
6.3.2 Radio Resource Management ..................................................................................43
6.3.3 Paging for GPRS Downlink Transfer ........................................................................43
6.4 Packet Routing and Transfer Functionality .................................................................................44
6.4.1 Definition of Packet Data Protocol States .................................................................44
6.4.2 Packet Routing and Transfer Function .....................................................................45
6.4.3 Packet Terminal Adaptation Function.......................................................................46
6.4.4 Encapsulation Function.............................................................................................46
6.5 Message Screening Functionality................................................................................................46
7. Compatibility Issues.................................................................................................................................47
Page 4
8. Transmission........................................................................................................................................... 47
8.1 Logical Link Control Functionality ............................................................................................... 47
8.1.1 Layer Services.......................................................................................................... 47
8.1.2 Layer Functions ........................................................................................................ 47
8.1.3 Service Primitives..................................................................................................... 47
8.1.4 Modes of Operation.................................................................................................. 48
8.2 Subnetwork Dependent Convergence Functionality................................................................... 48
8.2.1 Service Primitives..................................................................................................... 49
8.2.2 Services.................................................................................................................... 49
8.2.3 Subfunctions............................................................................................................. 50
8.3 Gb Interface ................................................................................................................................ 51
8.3.1 Link Layer Protocols................................................................................................. 51
8.3.2 Configuration and Allocation of Physical Resources................................................ 51
8.3.3 Configuration Dependence....................................................................................... 51
8.3.4 Transmission Plane Signalling Between the SGSN and BSS for a BTS ................. 52
8.3.5 Mobile User Messages............................................................................................. 55
8.3.6 General Messages ................................................................................................... 56
8.3.7 Physical Resources Allocation ................................................................................. 57
8.3.8 BSSGP Messages Information Elements ................................................................ 57
8.4 Abis Interface.............................................................................................................................. 59
8.4.1 Remote Packet Control Unit..................................................................................... 60
8.4.2 Resource Allocation ................................................................................................. 60
8.4.3 Resource Release.................................................................................................... 60
8.4.4 Transfer of Idle Frames............................................................................................ 60
9. Information Storage ................................................................................................................................ 60
9.1 HLR .......................................................................................................................................... 60
9.2 SGSN.......................................................................................................................................... 62
9.3 GGSN ......................................................................................................................................... 62
9.4 MS .......................................................................................................................................... 62
9.5 MSC/VLR.................................................................................................................................... 63
10. Identities................................................................................................................................................ 63
10.1 IMSI .......................................................................................................................................... 63
10.2 NSAPI and TLLI........................................................................................................................ 63
10.3 PDP Address ............................................................................................................................ 64
10.4 TEPI.......................................................................................................................................... 64
10.5 Routing Area Identity ................................................................................................................ 64
10.6 Cell Identity ............................................................................................................................... 65
10.7 GSN Address............................................................................................................................ 65
11. Operational Aspects.............................................................................................................................. 65
11.1 Charging ................................................................................................................................... 65
11.1.1 Charging Information.............................................................................................. 65
11.1.2 Reverse Charging .................................................................................................. 66
12. Interactions with Other GSM Services .................................................................................................. 66
12.1 Point-to-point Short Message Service ...................................................................................... 66
12.1.1 Mobile-terminated SMS Transfer ........................................................................... 66
12.1.2 Mobile-originated SMS Transfer............................................................................. 68
12.2 Circuit-switched Services.......................................................................................................... 68
12.3 Supplementary Services ........................................................................................................... 69
Page 5
1. Scope
This specification defines the stage-2 service description for a General Packet Radio Service (GPRS) on
GSM.
In analogy with CCITT Recommendations I.130 [1] and with reference to CCITT Recommendations VI.1
Q.65 (stage 2 of the method for the characterisation of services supported by an ISDN), the second stage
of the following three-level structure is derived from a stage 1 service description.
Stage 1 is an overall service description, from the service subscriber's and user's standpoints, that
views the network as a single entity which provides services to the user. [2] contains the GPRS
stage-1 service description.
10
Stage 2 identifies the functional capabilities and information flows needed to support the service
described in stage 1. Furthermore, it identifies various possible physical locations for the functional
capabilities. The output of Stage 2, which is signalling system independent, is used as an input to
Stage 3, the design of signalling system and switching recommendations.
15
Stage 3 defines the signalling system protocols and switching functions needed to implement the
service described in stage 2.
20
This version of the stage-2 service description covers the first phase of GPRS, and does not meet all the
services and functionality described in [2]. An update to this document to meet all the services and
functionality in [2] is foreseen.
This document does not cover the lower layers of the GPRS GSM radio interface. [3] contains an overall
description of the radio interface.
25
This document does not cover the GPRS Point-to-Multipoint services. [4] contains the PTM Multicast
stage-2 service description. [9] contains the PTM Group Call stage-2 service description.
2. Normative References
30
35
This European Telecommunication Standard (ETS) incorporates, by dated or undated reference,

provisions from other publications. These normative references are cited at the appropriate places in the
text and the publications are listed hereafter. For dated references, subsequent amendments to, or
revisions of, any of these publications apply to this ETS only when incorporated in it by amendment or
revision. For undated references the latest edition of the publication referred to applies.
[1]
CCITT Recommendations I.130 (1988): General modelling methods - Method

for the characterisation of telecommunication services supported by an ISDN
and network capabilities of an ISDN".
[2]
GSM 02.60: Digital cellular telecommunications system (Phase 2+); General

Packet Radio Service (GPRS); Service description; Stage 1.
[3]
GSM 03.64: Digital cellular telecommunications system; Overall description of

the General Packet Radio Service (GPRS) Radio interface; Stage 2.
[4]

Packet Radio Service (GPRS); Point to Multipoint Multicast Service Description;
Stage 2.
[5]
GSM 01.04: Digital cellular

Abbreviations and acronyms.
[6]

Packet Radio Service (GPRS); Subnetwork Dependent Convergence Protocol
(SNDCP).
[7]
GSM 04.64: Digital cellular telecommunications system (Phase 2+), General

Packet Radio Service (GPRS); Logical Link Control (LLC).
40
45
telecommunications
system
(Phase
2+);
Page 6
[8]
GSM 09.60: Digital cellular telecommunications system (Phase 2+), General

Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn
and Gp Interface.
[9]

Packet Radio Service (GPRS); Point to Multipoint Group Call Service
Description; Stage 2.
3. Definitions and Abbreviations

3.1 Definitions
Refer to GSM 02.60 [2].
10
3.2 Abbreviations
For the purposes of this specification the following abbreviations apply (also refer to GSM 01.04 [5]):
15
20
25
30
35
40
BG
CGI
CI
GGSN
GPRS
LA
LAC
LAI
MCC
MNC
MT
MT
PDN
PDP
PDU
PSPDN
RA
RAC
RAI
SGSN
TE
TEPI
TEPIG
TEPIS
Border Gateway
Cell Global Identity
Cell Identity
Gateway GPRS Support Node
General Packet Radio Service
Location Area
Location Area Code
Location Area Identity
Mobile Country Code (E.212)
Mobile Network Code (E.212)
Mobile Terminated
Mobile Termination
Packet Data Network
Packet Data Protocol, e.g., IP or X.25
Protocol Data Unit
Packet Switched Public Data Network
Routing Area
Routing Area Code
Routing Area Identity
Serving GPRS Support Node
Terminal Equipment
Tunnel End Point Identifier
Tunnel End Point Identifier in the GGSN
Tunnel End Point Identifier in the SGSN
S
R
ISDN reference point between TE and MT.

Reference point between a non-ISDN compatible TE and MT. Typically this reference point
supports a standard serial interface.
Interface between an SGSN and a BSC.
Interface between SMS-GMSC and SGSN, and between SMS-IWMSC and SGSN.
Reference point between GPRS and an external packet data network.
Interface between two GSNs within the same PLMN.
Interface between two GSNs in different PLMNs. The Gp interface allows support of GPRS
network services across areas served by the co-operating GPRS PLMNs.
Interface between a SGSN and a HLR.
Interface between an SGSN and MSC.
Interface between the MS and the GPRS fixed network part. The Um interface is the GPRS
network interface for providing packet data services over the radio to the MS. The MT part of
the MS is used to access the GPRS services through this interface.
Gb
Gd
Gi
Gn
Gp
45
Gr
Gs
Um
50
Page 7
4. Main Concepts
Ed. NOTE: This section should contain a short, high-level description of the main concepts of
GPRS, including a description of the split between GSM 03.60 and GSM 03.64. Annex
A contains a draft description. The text is FFS.
5
The general mechanism for GPRS data communication is shown below for the downlink direction of data
transfer. As the figure illustrates, GPRS encapsulates PDUs received from external PDNs, and then
routes and transports these through the PLMN towards the destination TE. Decapsulation of PSPDN
PDUs occurs before the PDUs are delivered to the TE. Transmission in the uplink direction is equivalent.
Mobile TE
Exterior PDN
User PDU
User PDU
GSM PLMN Supporting GPRS

Decapsulation Function
Encapsulation Function
GPRS PDU (header info,

encapsulated User PDU)
GPRS PDU (header info,

encapsulated User PDU)
Routing & Transport of GPRS PDU Through PLMN
Figure 1: Encapsulation
10
5. General GPRS Architecture and Transmission Mechanism

5.1 GPRS Access Interfaces and Reference Points
Each GPRS PLMN has two access points, the Um used for mobile access and the R and S reference
points used for origination or reception of messages.
15
An interface differs from a reference point in that an interface is defined where specific GPRS information
is exchanged and needs to be fully recognised.
There is an inter-GPRS PLMN interface called Gp which connects two independent GPRS networks for
message exchange.
20
There is also a GPRS PLMN to fixed network (typically a Packet Data Network) reference point called Gi
which is not defined and left to the PLMN operator to configure.
Page 8
R or S
reference point
TE
Gi
reference point
Um
MT
GPRS
network 1
PDN or
other network
Gp
MS
GPRS
network 2
Figure 2: GPRS Access Interfaces and Reference Points
There may be more than a single GPRS network interface to several different PDN (or other) networks.
These networks may both differ in ownership as well as in communications protocol (e.g., X.25, TCP/IP,
IBM SDLC etc.). The network operator should define and negotiate interconnect with each external (PDN
or other) network.
5.2 Network Interworking
10
15
Network interworking is required whenever a PLMN supporting GPRS and any other network are involved
in the execution of a GPRS Service Request. With reference to figure 1 GPRS Access Interfaces and
Reference Points, interworking takes place through the Gi reference point and the Gp interface.
The GPRS internal mechanism for conveying the PDU through the GSM PLMN is managed by the GSM
GPRS network operator and is not apparent to the data user. The use of this GSM data service may have
an impact on and increase the transfer time normally found for a message when communicated through a
fixed packet data network.
5.2.1 PSPDN Interworking
GPRS shall support interworking with PSPDN networks. The interworking may be either direct or through
a transit network (e.g., ISDN). GPRS shall support both ITU-T X.121 and ITU-T E.164 addresses.
20
GPRS shall provide support for ITU-T X.25 Virtual Circuits and X.25 Fast Select. X.75 may be used for
interworking with X.25 PDNs.
The GPRS TEs have addresses provided by the GSM PLMN GPRS service operator and belong to the
GPRS service domain. The PSPDN TE sends data to the GPRS TE by use of the GSM PLMN GPRS
DNIC (Data Network Identification Code) or equivalent which uniquely identifies the GPRS network
throughout the world.
25
5.2.2 Internet (IP) Interworking

GPRS shall support interworking with networks based on the internet protocol (IP). GPRS may provide
compression of the total TCP/IP header when an IP-datagram is used within the context of a TCP
connection.
30
In a similar way to the PSPDN X.25 case, the GSM PLMN GPRS service is an IP domain in its own right,
and mobile terminals offered service by a GSM service provider are globally addressable through the
network operators addressing scheme.
5.3 High-Level Functions Required for GPRS
The following list gives the logical functions performed within the GPRS network. Several functional
groupings (meta-functions) are defined which each encompasses a number of individual functions:
35
Network Access Control Functions.
Page 9
Packet Routing and Transfer Functions.

Mobility Management Functions.
Logical Link Management Functions.
Radio Resource Management Functions.
Network Management Functions.
5.3.1 Network Access Control Functions

Network access is the means by which a user is connected to a telecommunication network in order to
use the services and/or facilities of that network. An access protocol is a defined set of procedures that
enables the user to employ the services and/or facilities of the network.
10
15
20
User network access may occur from either the mobile side or the fixed side of the GPRS network. The
fixed network interface may support multiple access protocols to external data networks, for example X.25
or IP. The set of access protocols to be supported is determined by the PLMN operator.
Individual PLMN administrations may require specific access-control procedures in order to limit the set of
users permitted to access the network, or to restrict the capabilities of individual users, for example by
limiting the type of service available to an individual subscriber. Such access control procedures are
beyond the scope of the GPRS specifications.
In addition to the standard PTP data transfer, GPRS can support anonymous access to the network. The
service allows a MS to exchange data packets with a predefined host which can be addressed by the
supported interworking protocols. Only a limited number of destination addresses can be used within this
service. IMSI or IMEI shall not be used when accessing the network thus guaranteeing a high level of
anonymity. Therefore, no authentication and ciphering functionalities are foreseen for anonymous access.
5.3.1.1 Registration Function
25
Registration is the means by which a user's packet data address(es) is(are) associated with a users
Mobile Id within the PLMN. The association can be static, i.e., stored in a HLR, or dynamic, i.e., allocated
on a per need basis.
5.3.1.2 Authentication and Authorisation Function
This function performs the identification and authentication of the service requester, and the validation of
the service request type to ensure that the user is authorised to use the particular network services. The
authentication function is performed in association with the Mobility Management functions.
30
5.3.1.3 Admission Control Function

The purpose of admission control is to calculate which network resources are required to provide the QoS
requested, determine if those resources are available, and then reserve those resources. Admission
control is performed in association with the Radio Resource Management functions in order to estimate
the radio resource requirements within each cell.
35
5.3.1.4 Message Screening Function

A screening function concerned with filtering out unauthorised or unsolicited messages is required. This
should be supported through packet filtering functions. Network-controlled and subscription-controlled
versions are supported in the first phase of GPRS. User-controlled screening may be provided in a later
phase.
40
5.3.1.5 Packet Terminal Adaptation Function

This function adapts data packets received / transmitted from / to terminal equipment to a form suitable for
transmission across the GPRS network.
5.3.1.6 Charging Data Collection Function
This function collects data necessary to support subscription and/or traffic fees.
Page 10
5.3.2 Packet Routing and Transfer Functions
A route is an ordered list of nodes used for the transfer of messages within the PLMN. Each route
consists of the originating node, zero or more relay nodes and the destination node. Routing is the
process of determining and using, in accordance with a set of rules, the route for transmission of a
message within the PLMN.
5.3.2.1 Relay Function
The relay function is the means by which a node forwards data received from one node to the next node in
the route.
5.3.2.2 Routing Function
10
The routing function determines the network node to which a message should be forwarded and the
underlying service(s) used to reach that GPRS Support Node (GSN), using the destination address of the
message. The routing function selects the transmission path for the "next hop" in the route.
NOTE:
15
Data transmission between GSNs may occur across external data networks which
provide their own internal routing functions, for example X.25, Frame Relay or ATM
networks.
5.3.2.3 Address Translation and Mapping Function

Address translation is the conversion of one address to another address of a different type. Address
translation may be used to convert an external network protocol address into an internal network address
which can be used for routing packets within the PLMN.
20
Address mapping is used to map a network address to another network address of the same type for the
routing and relaying of messages within the PLMN, for example to forward packets from one network
node to another.
5.3.2.4 Encapsulation Function
25
Encapsulation is the addition of address and control information to a data unit for routing packets within
the PLMN. Decapsulation is the removal of the addressing and control information from a packet to reveal
the original data unit.
Encapsulation and decapsulation are performed between the support nodes of the GPRS PLMN, and
between the serving support node and the mobile station.
5.3.2.5 Tunnelling Function
30
Tunnelling is the transfer of encapsulated data units within the PLMN from the point of encapsulation to
the point of decapsulation. A tunnel is a two-way point-to-point path. Only the tunnel endpoints are
identified.
5.3.2.6 Compression Function
35
The compression function optimises use of radio path capacity by transmitting as little of the SDU (i.e., the
exterior PDP PDU) as possible while at the same time as preserving the information contained within it.
5.3.2.7 Cipher Function
The cipher function preserves the confidentiality of user data and signalling across the radio channels and
inherently protects the PLMN from intruders.
5.3.3 Mobility Management Functions
40
The mobility management functions are used to keep track of the current location of a MS within the
PLMN or within another PLMN.
Page 11
5.3.4 Logical Link Management Functions
Refer to GSM 03.64 for further information.
Logical link management functions are concerned with the maintenance of a communication channel
between an individual MS and the PLMN across the radio interface. These functions involve the coordination of link state information between the MS and the PLMN as well as the supervision of data
transfer activity over the logical link.
5.3.4.1 Logical Link Establishment Function
Logical link establishment is performed when the MS attaches to the GPRS service.
5.3.4.2 Logical Link Maintenance Functions
10
Logical link maintenance functions supervise the logical link status and control link state changes.
5.3.4.3 Logical Link Release Function
The logical link release function is used to de-allocate resources associated with the logical link
connection.
5.3.5 Radio Resource Management Functions
15
Refer to GSM 03.64 for further information.

Radio resource management functions are concerned with the allocation and maintenance of radio
communication paths. GSM radio resources is shared between the circuit mode (voice and data) services
and the GPRS.
5.3.5.1 Um Management Function
20
This function manages the set of physical channels used in each cell and determines the amount of radio
resources to be allocated for GPRS use. The amount of radio resources allocated for GPRS may vary
from cell to cell depending upon local user demand or other policies established by the PLMN operator.
5.3.5.2 Cell Selection Function
Refer to GSM 03.22 and GSM 03.64 for further information.
25
This function enables the MS to select the optimal cell for use in establishing a communication path with
the PLMN. This involves the measurement and evaluation of signal quality from nearby cells as well as the
detection and avoidance of congestion within candidate cells.
5.3.5.3 Um-tranx Function
30
The Um-tranx function provides packet data transfer capability across the radio interface between the MS
and the BSS. This function includes procedures which:
35
Provide medium access control over radio channels.

Provide packet multiplexing over common physical radio channels.
Provide packet discrimination within the MS.
Provide error detection and correction.
Provide flow control procedures.
5.3.5.4 Path Management Function
40
This function manages the packet data communication paths between the BSS and the serving GSN
nodes. The establishment and release of these paths may be dynamic based upon the amount of data
traffic or may be static based upon the maximum expected load within each cell.
Page 12
5.3.6 Network Management Functions
Network management functions provide mechanisms to support O&M functions related to GPRS.
5.4 Logical Architecture
GPRS is logically implemented on the GSM structure through the addition of two network entities, the
Serving GPRS Support Node and the Gateway GPRS Support Node. It is necessary to name a number of
new interfaces. No inference should be drawn about the physical configuration on an interface from this
figure.
HLR
MAP-D
MAP-C
Gr
SMS-GMSC
SMS-IWMSC
MSC/VLR
Gs
A
TE
MT
R/S
Gd
EIR
MAP-F
Gb
BSS
Um
MAP-H
SM-SC
SGSN
Gp
PDN
GGSN
Gn
TE
Gi
GGSN
other PLMN
Signalling Interface
Signalling and Data Transfer Interface
Figure 3: Overview of the GPRS Logical Architecture
10
5.4.1 GPRS Support Nodes

A GPRS Support Node (GSN) contains functionality required to support GPRS. In one PLMN, there may
be more than one GSN.
15
The Gateway GPRS Support Node (GGSN) is the node which is accessed by the packet data network
due to evaluation of the PDP address. It contains routing information for attached GPRS users. The
routing information is used to tunnel PDUs to the MSs current point of attachment, i.e., the Serving GPRS
Support Node. The GGSN is the first point of PDN interconnection with a GSM PLMN supporting GPRS
(i.e., the Gi reference point is supported by the GGSN).
20
The Serving GPRS Support Node (SGSN) is the node that is serving the MS (i.e., the Gb interface is
supported by the SGSN). At GPRS Attach, the SGSN establishes a mobility management context
containing information pertaining to e.g., mobility and security for the MS. At GPRS Activate, the SGSN
establishes a PDP context, to be used for routing purposes inside the GPRS PLMN, with the GGSNs that
the GPRS subscriber will be using.
25
The SGSN and GGSN functionalities may be combined in the same physical node, or they may reside in
different physical nodes. SGSN and GGSN contain IP routing functionality, and they may be
interconnected with IP routers. When SGSN and GGSN are in different PLMNs, they are interconnected
via the Gp interface. The Gp interface provides the functionality of the Gn interface, plus security
functionality required for inter-PLMN communication.
The SGSN may send location information to the MSC/VLR via the Gs interface. The SGSN may receive
paging requests from the MSC/VLR via the Gs interface.
Page 13
5.4.2 GPRS Backbone Networks
There are two kinds of GPRS backbone networks. These are called the intra-PLMN backbone network
and the inter-PLMN backbone network.
The intra-PLMN backbone network is the IP network interconnecting GSNs within the same PLMN.
5
The inter-PLMN backbone network is the IP network interconnecting GSNs and intra-PLMN backbone
networks in different PLMNs.
Inter-PLMN Backbone
Gp
Gi
BG
GGSN
Intra-PLMN Backbone
SGSN
SGSN
PLMN A
Gp
GGSN
BG
Intra-PLMN Backbone
SGSN
PLMN B
Figure 4: Intra- and Inter-PLMN Backbone Networks
10
Every intra-PLMN backbone network is a private IP network. Two intra-PLMN backbone networks are
connected via the Gp interface using border gateways (BGs) and an inter-PLMN backbone network. The
inter-PLMN backbone network is selected by a roaming agreement. The inter-PLMN backbone can be
e.g., the public Internet or a leased line. The BGs provide the appropriate security.
5.4.3 HLR
15
The HLR contains GPRS subscription data and routing information, and maps IMSI to one or more (PDP
Type, PDP Address) pairs. The HLR also maps each (PDP Type, PDP Address) pair to one or more
GGSNs. The HLR is accessible from the SGSN via the Gr interface.
For roaming MSs, HLR may be in a different PLMN than the current SGSN.
5.4.4 SMS-GMSC and SMS-IWMSC
20
The SMS-GMSC and SMS-IWMSC are connected to the SGSN via the Gd interface to enable GPRS MSs
to send and receive SMs over GPRS radio channels.
Page 14
5.5 Assignment of Functions to General Logical Architecture
The functions identified in the functional model are assigned to the logical architecture.
Table 1: Mapping of Functions to Logical Architecture
Function
Network Access Control:
Registration
Authentication and Authorisation
Admission Control
Message Screening
Packet Terminal Adaptation
Charging Data Collection
MS
X
X
BSS
SGSN
X
X
HLR
X
X
X
X
X
X
X
X
X
X
Packet Routing & Transfer:

Relay
Routing
Address Translation and Mapping
Encapsulation
Tunnelling
Compression
Cipher
X
X
X
X
X
X
X
X
X
Mobility Management:
Logical Link Management:

Logical Link Establishment
Logical Link Maintenance
Logical Link Release
X
X
X
X
X
X
Radio Resource Management:

Um Management
Cell Selection
Um-Tranx
Path Management
GGSN
X
X
X
X
X
X
X
X
X
X
X
X
X
X
X
Page 15
5.6 Transmission and Signalling Planes
5.6.1 Transmission Plane
The transmission plane consists of a layered protocol structure providing user information transfer, along
with associated information transfer control procedures (e.g., flow control, error detection, error correction
and error recovery). The transmission plane independence of the Network Subsystem (NSS) platform
from the underlying radio interface is preserved via the Gb interface. The following transmission plane is
used in GPRS:
Application
IP/ X.25
IP / X.25
SNDCP
SNDCP
LLC
RLC
MAC
GSM RF
IP
L2
BSSGP
BSSGP
MAC
Frame
Relay
Frame
Relay
L2
GSM RF
L1bis
L1bis
L1
Gb
BSS
GTP
IP
RLC
Um
MS
LLC
LLC Relay
GTP
L1
Gn
SGSN
Gi
GGSN
Figure 5: Transmission Plane

Legend:
10
GPRS Tunnelling Protocol (GTP): This protocol tunnels user data and signalling between GPRS
Support Nodes in the GPRS backbone network. All PTP PDP PDUs shall be encapsulated by the
GPRS Tunnelling Protocol.
IP: This is the GPRS backbone network protocol used for routing user data and control signalling.
The GPRS backbone network may initially be based on the IP version 4 protocol. Ultimately, IP
version 6 shall be used.
Subnetwork Dependent Convergence Protocol (SNDCP): This transmission functionality maps

network-level characteristics onto the characteristics of the underlying network.
Logical Link Control (LLC): This layer provides a highly reliable logical link. LLC shall be
independent of the underlying radio interface protocols in order to allow introduction of alternative
GPRS radio solutions with minimum changes to the NSS.
LLC Relay: This function relays LLC PDUs between the Um and Gb interfaces..
Base Station Subsystem GPRS Protocol (BSSGP): This layer conveys routing- and QoS-related
information between BSS and SGSN. BSSGP does not perform error correction.
Frame Relay: This layer transports BSSGP PDUs. The Frame Relay connection between BSS and
SGSN may be multi-hop and traverse a network of Frame Relay switching nodes.
Radio Link Control (RLC): This layer provides a radio-solution-dependent reliable link.
Medium Access Control (MAC): This controls the access signalling (request and grant) procedures
for the radio channel, and the mapping of LLC frames onto the GSM physical channel.
GSM RF: As defined in GSM 05 series.
15
20
25
30
35
Page 16
5.6.2 Signalling Plane
The signalling plane consists of protocols for control and support of the transmission plane functions:
10
15
controlling the GPRS network access connections, such as attaching to and detaching from the
GPRS network;
controlling the attributes of an established network access connection, such as activation of a PDP
address;
controlling the routing path of an established network connection in order to support user mobility;
controlling the assignment of network resources to meet changing user demands;
providing supplementary services.
The following signalling planes are used in GPRS:

5.6.2.1 MS - SGSN
L3MM
L3MM
SNDCP
SNDCP
LLC
LLC
LLC Relay
RLC
RLC
BSSGP
BSSGP
MAC
Frame
Relay
GSM RF
L1bis
Frame
Relay
L1bis
MAC
GSM RF
Um
Gb
MS
SGSN
BSS
Figure 6: Signalling Plane MS - SGSN
Legend:
20
Layer 3 Mobility Management (L3MM): This protocol supports mobility management functionality
such as GPRS attach, GPRS detach, security, routing update, location update, PDP context
activation, and PDP context deactivation, as described in section Mobility Management
Functionality.
5.6.2.2 SGSN - HLR

MAP
MAP
TCAP
TCAP
SCCP
SCCP
MTP3
MTP3
MTP2
MTP2
L1
L1
Gr
SGSN
HLR
Figure 7: Signalling Plane SGSN - HLR
25
Legend:
Mobile Application Part (MAP): This protocol supports signalling exchange with the HLR, as defined
in GSM 09.02, with enhancements for GPRS as described in section Mobility Management
Functionality.
Page 17
TCAP, SCCP, MTP3, and MTP2 are the same protocols as used to support MAP in non-GPRS
GSM PLMNs.
5.6.2.3 SGSN - MSC/VLR

BSSAP+
BSSAP+
SCCP
SCCP
MTP3
MTP3
MTP2
MTP2
L1
L1
Gs
SGSN
MSC/VLR
Figure 8: Signalling Plane SGSN - MSC/VLR

Legend:
10
Base Station Subsystem Application Part + (BSSAP+): A subset of BSSAP procedures supports
signalling between the SGSN and MSC/VLR, as described in section Mobility Management
Functionality.
5.6.2.4 SGSN - SMS-GMSC or SMS-IWMSC

MAP
MAP
TCAP
TCAP
SCCP
SCCP
MTP3
MTP3
MTP2
MTP2
L1
L1
Gd
SGSN
SMS-MSC
Figure 9: Signalling Plane SGSN - SMS-GMSC and SGSN - SMS-IWMSC

Legend:
15
Mobile Application Part (MAP): This protocol supports signalling between the SGSN and SMSGMSC or SMS-IWMSC, as described in section Point-to-point Short Message Service.
5.6.2.5 GSN - GSN

GTP
GTP
UDP
UDP
IP
IP
L2
L2
L1
L1
Gn
GSN
GSN
Figure 10: Signalling Plane GSN - GSN

20
Legend:
GPRS Tunnelling Protocol (GTP): This protocol tunnels user data and signalling messages
between SGSNs and GGSNs, and between SGSNs, in the GPRS backbone network.
Page 18
User Datagram Protocol (UDP): This protocol transfers signalling messages between GSNs. UDP
is defined in RFC 768.
6. Functional Model
5
6.1 Mobility Management Functionality

6.1.1 Definition of Mobility Management States
The mobility management (MM) activities related to a GPRS subscriber are characterised by one of three
different MM states. Each state describes a certain level of functionality and information allocated to the
involved entities. The information sets held at MS and SGSN are denoted MM context.
10
The MM state relates only to GPRS MM activities of a subscriber represented by the IMSI and TLLI. It is
independent of number and state of PDP contexts for that subscriber.
In the anonymous access case, the MM state relates to GPRS MM activities of a MS represented only by
a TLLI.
6.1.1.1 IDLE (GPRS) State
15
In GPRS IDLE state, the subscriber is not attached to the GPRS mobility management. The MS and
SGSN context hold no valid location or routing information for the subscriber. The subscriber-related
mobility management procedures are not performed.
PLMN selection and GPRS cell selection and re-selection processes are performed by the MS.
20
The MS may receive PTM-M transmissions. PTP and PTM-G data transfers to and from the mobile
subscriber as well as the paging of the subscriber are 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.
6.1.1.2 STANDBY State
25
In STANDBY state, the subscriber is attached to GPRS mobility management. The MS and SGSN have
established MM contexts for the subscribers IMSI as described in section Information Storage.
The MS may receive PTM-M and PTM-G data. Pages for PTP or PTM-G data transfers may be received if
a PDP context is activated. It is also possible to receive pages for the CS services via the SGSN. PTP
data reception and transmission, and PTM-G data transmission, are not possible in this state.
30
35
The MS performs GPRS Routing Area (RA) and GPRS cell selection and re-selection 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. Therefore, the location information in the SGSN MM
context contains only the GPRS RAI for MSs in STANDBY state.
The MS may initiate activation or deactivation of PDP contexts while in STANDBY state. A PDP context
shall be activated before data is transmitted.
The state is changed from STANDBY to READY when the MS starts to transmit data.
40
A MT PTP or PTM-G packet can be received by the SGSN in the MM STANDBY state if a PDP context is
activated. The SGSN then sends a Paging Request in the routing area where the MS is located. 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.
Page 19
The MS may initiate the GPRS Detach procedure to move to the IDLE state. If the STANDBY timer
expires, the MM contexts in the SGSN and in the MS are deleted independently and the MM state goes to
the IDLE state.
6.1.1.3 READY State
5
In READY state, the SGSN MM context corresponds to the STANDBY MM context extended by location
information for the subscriber on cell level. The MS performs mobility management procedures to provide
the network with the actual selected cell. GPRS cell selection and re-selection is done locally by the MS.
The cell identity is included in the BSSGP header of the data packet from the MS.
10
The MS may send and receive PTP PDUs in this state. The network initiates no pages for a MS in READY
state. The SGSN transfers downlink data to the LLC Relay function responsible for the subscribers actual
GPRS cell.
The MS may receive PTM-M and PTM-G data in READY state.
The MS may activate or deactivate PDP contexts while in READY state.
15
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. The READY state is supervised by a timer. A 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.
Page 20
6.1.2 IDLE / STANDBY / READY State Functionality
6.1.2.1 State Transitions and Functions
The movement from one state to the next is dependent on the current state (IDLE, STANDBY, or READY)
and the event occurred (e.g., GPRS Attach).
IDLE
IDLE
GPRS Attach
or
PDP Context Activation
STANDBY timer
expiry
GPRS Detach
STANDBY timer expiry

or
Cancel Location
READY
READY timer expiry
GPRS Attach
or
PDP Context Activation
PDU transmission
GPRS Detach
or
Cancel Location
READY
READY timer expiry

or
Abnormal RLC condition
PDU reception
STANDBY
STANDBY
MM State Model of MS
MM State Model of SGSN
Figure 11: Functional Mobility Management State Model
This figure describes the following state transitions:

Moving from IDLE to 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.
PDP Context Activation: If a MS accesses GPRS anonymously, the GPRS Attach procedure shall
not be executed. Instead, the state transition is triggered by the PDP Context Activation. This state
transition applies only to the anonymous access case.
10
15
Moving from STANDBY to IDLE:
20
STANDBY timer expiry: The MM and PDP contexts in the MS, the SGSN, and the GGSN are
deleted.
Cancel Location: The SGSN receives a MAP Cancel Location message from the HLR, and
removes the MM context.
Moving from STANDBY to READY:
Page 21
PDU transmission: The MS sends a PDU to the SGSN, possibly in response to a page.
PDU reception: The SGSN receives a PDU from the MS.
Moving from READY to STANDBY:
READY timer expiry: The MS and the SGSN MM contexts return to STANDBY state.
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.
10
Moving from READY to IDLE:
15
GPRS Detach: The MS requests that the contexts are deleted.
Cancel Location: The SGSN receives a MAP Cancel Location message from the HLR, and
removes the MM context.
6.1.2.2 STANDBY Timer Function
20
The STANDBY timer function maintains the STANDBY timer in the MS and SGSN. The STANDBY timer
controls the time an MS remains in STANDBY state. When the STANDBY timer expires, the MS and
SGSN MM contexts return to IDLE state, and the PDP contexts are deleted.
The length of the STANDBY timer is the same in the MS and SGSN. Normally, the length of the
STANDBY timer is defined by a default value. The SGSN, and only the SGSN, may change this value
dynamically by transmitting a new value in the header part of a GPRS PDU. The length of the STANDBY
timer for anonymous access shall have a separate default value.
25
If this dynamic value is set to ZERO, the MS is immediately forced into IDLE. If this value is set to all 1's
(binary), then the STANDBY timer function is deactivated (i.e., the timer no longer runs and the MS
remains in STANDBY).
The STANDBY timer is reset and begins running in the MS and SGSN every time STANDBY state is
entered.
30
6.1.2.3 READY Timer Function

The READY timer function maintains the READY timer in the MS and SGSN. The READY timer controls
the time an MS remains in READY state after a PDU has been successfully transmitted between the MS
and SGSN. When the READY timer expires, the MS and SGSN MM contexts return to STANDBY state.
35
The length of the READY timer is the same in the MS and SGSN. Normally, the length of the READY
timer is defined by a default value. Only the SGSN may change this value dynamically by transmitting a
new value in the header part of a GPRS PDU.
If this dynamic value is set to ZERO, the MS is immediately forced into STANDBY. If this value is set to all
1's (binary), then the READY timer function is deactivated (i.e., the timer no longer runs and the MS
remains in READY).
40
The READY timer is reset and begins running in the MS and SGSN every time a PDU has been
successfully communicated between the MS and SGSN.
6.1.3 Interactions Between SGSN and MSC/VLR
45
An association is created between SGSN and MSC/VLR to provide for interactions between SGSN and
MSC/VLR. The association is created when the VLR stores the SGSN address and the SGSN stores the
VLR address. The association is used for co-ordinating class-A and B MSs in STANDBY and READY
states. A class-C MS can only be attached to either the GPRS or the CS service.
The association supports the following actions:
Page 22
10
Co-ordination of LA Update and RA Update, including periodic updates, thus saving radio
resources. A combined RA / LA Update is sent from the MS to the SGSN. SGSN forwards the LA
Update to the VLR.
IMSI attach and detach via SGSN. This makes combined IMSI / GPRS attach and combined IMSI /
GPRS detach possible, thus saving radio resources.
Paging for a CS connection via the SGSN.
6.1.3.1 Administration of the SGSN-MSC/VLR Association

The SGSN-MSC/VLR association is initiated at the following occasions:
At IMSI attach when the MS is already GPRS-attached.
At GPRS attach when the MS is already IMSI-attached (IMSI attach is indicated in the GPRS attach
request).
At combined IMSI / GPRS attach.
15
20
The association is initiated by the SGSN. The SGSN creates an association by sending a MAP message
concerning a particular MS to the VLR. To get the VLR address, the SGSN translates the current RAI to a
VLR address via a translation table.
The association is updated on the following occasions:
25
When a MS changes VLR.
When a MS changes SGSN.
When the MS is in GSM IDLE state, the association is updated in the RA and LA updates procedures.
During a CS connection, the association is updated in the following way:
Class A:
30
35
A class-A MS makes RA updates but no LA updates during the CS connection. In the case when the MS
changes SGSN, the SGSN (according to normal RA update procedures, see section Inter SGSN Routing
Update) normally updates the VLR about the new SGSN address. The new SGSN derives the VLR
address from the RA information received in the Routing Area Update Request message.
In the case when the MS changes MSC during the CS connection, the subscriber data still remains in the
old VLR until the CS connection is finished and a LA update is made (normal GSM procedure). The
association is also not updated during the CS connection.
After the CS connection is finished, a combined RA / LA update is performed (if there has been a change
of MSC), and the association is updated according to combined RA / LA update procedures, see section
Combined RA / LA Update Procedure.
40
NOTE:
How and whether the association between the MSC/VLR and the SGSN is maintained
for a class-A MS during a CS connection is FFS.
Class B:
45
50
A class-B MS does not make any RA updates during a CS connection. The SGSN address therefore
remains the same during the CS connection and need not be updated in the VLR. In the case when the
MS changes MSC during the CS connection, the subscriber data still remains in the old VLR until the CS
connection is finished and a LA update is made. Therefore the VLR address remains the same during the
CS connection. After the CS connection is finished, a RA update, or a combined RA / LA update if the RA
and the LA has changed, is performed. The association is updated according to RA update and combined
RA / LA update procedures, see section Inter SGSN Routing Update and section Combined RA / LA
Update Procedure.
Page 23
The SGSN-MSC/VLR association is removed at the following occasions:
At IMSI detach.
At GPRS detach.
5
6.1.3.2 Combined RA / LA Updating
10
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 a MS enters a new cell it checks if RA or LA has changed. If only RA has
changed, the MS sends a Routing Area Update Request message to the SGSN, as described in section
Routing Area Update Procedure. If also LA has changed 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 TMSI
that is sent to the MS via SGSN. The combined RA / LA updating is further described in section
"Combined RA / LA Update Procedure".
A class-A MS involved in a CS connection makes only RA updates to the SGSN.
15
A class-B MS involved in a CS connection does not make any RA updates during the CS connection.
A class-C MS never makes combined RA / LA Updates.
6.1.3.3 CS Paging
20
When a MS is attached to GPRS, the MSC/VLR executes paging for circuit-switched services via SGSN.
Class-A and B MSs have the same capabilities to receive CS page while attached to GPRS. If the MS is in
STANDBY state, then it is paged in the routing area. If the MS is in READY state, then it is paged in the
cell. The paging procedure is supervised in the MSC by a paging timer. The SGSN converts the MSC
paging message into a SGSN paging message.
The CS paging procedure is illustrated in the figure below. Each numbered step is explained in the
following list.
MS
BSS
SGSN
MSC/VLR
1. Page
2. Paging Request
3. Paging Request
4. GPRS Suspend
5. SABM (Paging Response)
6. SCCP Conn_Req (Paging Response)
Figure 12: CS Paging Procedure
25
1.
The SGSN receives a Page (IMSI, TMSI, Channel Needed) message from the MSC. The Channel
Needed parameter is used to indicate to the MS which type of CS channel is needed to be
requested in the response. TMSI and Channel Needed are optional parameters.
2.
The SGSN sends a BSSGP Paging Request (IMSI, TLLI, TMSI, Area, Channel Needed) message
to the BSS serving the MS. TLLI and Area are derived from the MSs MM context in the SGSN.
Area indicates a single cell for a READY state MS or a routing area for a STANDBY state MS. TMSI
and Channel Needed are included if received from the MSC.
3.
If a dedicated radio resource is assigned to the MS, then the BSS transmits a Paging Request
(TMSI, Channel Needed) with the RLC protocol. Otherwise, the BSS pages the MS with one Paging
Request (TMSI, Channel Needed) message in each addressed cell. This is described in GSM
03.64.
30
35
40
Page 24
4.
When a GPRS-attached class-B MS is paged for a CS connection, the MS goes to SUSPENDED

state [FFS]. This is described in section Suspend and Resume Procedure.
5.
Upon receipt of a paging request message for a circuit switched service the MS may accept the CS
connection request and shall then follow the standard CS procedures for paging response (random
access, immediate assignment, and paging response as specified in GSM 04.08). A class-A MS
may simultaneously be active in GPRS data transfer, while a class-B MS shall suspend [FFS]
GPRS data transfer if accepting the CS connection.
6.
When received at the BSS, the Paging Response message is sent to the MSC which shall then
stop the paging response timer.
10
6.1.3.4 Suspend and Resume Procedure

Ed. NOTE: This section is FFS.
15
20
When a GPRS-attached class-B MS is CS paged, the MS sends a GPRS Suspend message to the SGSN
and goes to SUSPENDED state. If data transfer was taking place, it is interrupted. For a MS in
SUSPENDED state, incoming packets may be discarded or buffered [FFS].
The MS subscriber may choose if the CS call shall be accepted. After receiving the CS page, the CS call
set-up procedures are started. This allows the MS subscriber to know the calling-id. If the subscriber
accepts the CS call, the call set-up procedures continues. If the MS subscriber chooses not to accept the
CS call, the MS sends a GPRS Resume message and enters READY state. Data transfer can now be
continued.
The suspend / resume procedure is illustrated in the figure below. Each numbered step is explained in the
following list.
25
MS
BSS
SGSN
MSC/VLR
1. IMSI Attach procedures

2. GPRS Attach procedures
3. CS Page
Incoming CS Call
4. CS Page
4. CS Page
5. GPRS Suspend
6. CS Page Response
7. CS Call Set-up procedures
7. (GPRS Resume)
Note 1
CS CONNECTION
8. CS Call Release procedures
9. GPRS Resume
Figure 13: Suspend and Resume Procedure

Note 1:
If the CS Call set-up procedures are started and the MS subscriber chooses not to
accept the call, a GPRS Resume message is sent from the MS.
Page 25
The suspend and resume procedure consists of the following steps:
1.
The MS performs an IMSI attach.
2.
The MS performs a GPRS attach.
3.
MSC/VLR receives a CS connection request for the MS. The MSC/VLR sends a CS page to the
SGSN.
4.
The SGSN sends the CS page to BSS. BSS pages the MS.
5.
The MS sends GPRS Suspend to the SGSN.
6.
MS responds to the CS Page as already defined in GSM.
7.
CS call set-up is initiated. If the MS subscriber chooses not to accept the call, e.g., by invoking the
UDUB (User Determined User Busy) function, a GPRS Resume message is sent from the MS.
8.
After the CS connection is finished, CS call release procedures are executed as usual.
9.
The MS sends a GPRS Resume message to the SGSN. If required, the MS then performs the
Routing Area Update Procedure. After GPRS resume, the MS is in READY state.
10
15
20
Page 26
6.1.4 MM Procedures
The GPRS and combined GPRS/CS MM procedures in the following subsections use the SNDC and LLC
protocols for efficient and reliable message transmission across the Um interface. Document GSM 03.64
defines the mapping between LLC and the radio channels used.
5
Furthermore, the MM procedures use a MAP interface between:
10
SGSN and MSC/VLR (Gs),

SGSN and HLR (Gr), and
SGSN and EIR.
6.1.5 Attach Function

A GPRS attach is made to the SGSN. A GPRS-attached MS makes IMSI attach via the SGSN. A MS that
is not GPRS-attached makes IMSI attach as already defined in GSM.
15
In the attach, the MS provides its IMSI or old TLLI and old RAI and an indication of which type of attach
that is to be executed. The different types of attach is IMSI attach, GPRS attach and combined IMSI /
GPRS attach.
IMSI or old TLLI and old RAI are used as an identifier during the attach procedure until a new TLLI is
allocated. 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 section
PDP Context Activation and Deactivation Functions.
20
25
An IMSI-attached class-C MS shall follow the normal IMSI detach procedure before it makes a GPRS
attach. A GPRS-attached class-C MS shall always perform a GPRS Detach before it makes an IMSI
Attach.
The SGSN address for this particular MSs location is stored in the HLR so that changes in subscriber
data can be communicated to the SGSN. If new subscriber data is received in the SGSN, and if the MS is
GPRS-attached, the SGSN commands the MS to make a new GPRS attach and new PDP context
activations so that the new subscriber data is immediately taken into use.
The attach procedure is illustrated in the figure below. Each numbered step is explained in the following
list.
Page 27
MS
BSS
1. Attach Request
new SGSN
old SGSN
GGSN
HLR
EIR
new
MSC/VLR
old
MSC/VLR
2. Identification Request
2. Identification Response
3. Identity Request
3. Identity Response
4. Authentication
5. Set Ciphering
6. IMEI Check
7a. Update Location
7b. Cancel Location
7c. Cancel Location Ack
7d. Insert Subscriber Data
7e. Insert Subscriber Data Ack
7f. Update Location Ack
8a. Location Updating Request
8b. Update Location
8c. Cancel Location
8d. Cancel Location Ack
8e. Insert Subscriber Data
8f. Insert Subscriber Data Ack
8g. Update Location Ack
8h. Location Updating Accept
9. Attach Accept
10. Attach Complete
11. TMSI Reallocation Complete
Figure 14: Combined IMSI / GPRS Attach Procedure

1.
5
10
The MS makes its identity (the IMSI or TLLI) known to the SGSN by the transmission of Attach
Request (IMSI or TLLI and old RAI, Classmark, CKSN, IMSI Attach Indication, Attach Type) to the
SGSN. Attach Type indicates which type of attach that is to be performed, i.e., GPRS Attach only,
IMSI Attach only or a combined GPRS and IMSI Attach. IMSI Attach Indication indicates if the MS is
already IMSI-attached (only applicable at GPRS attach).
In addition to the existing classmark 2 parameters (GSM 04.08) and the GPRS class of the MS (A,
B, or C), the Classmark parameter may contain the MSs multislot and channel coding capabilities.
Page 28
2.
If the MS identifies itself with TLLI and the SGSN has changed since detach, the new SGSN sends
an Identification Request (TLLI, old RAI) to the old SGSN to request the IMSI. The old SGSN
responds with Identification Response (IMSI, Triplets). If the MS is not known in the old SGSN, the
old SGSN responds with an appropriate error cause.
3.
If the TLLI is unknown in both the old and new SGSN, the SGSN sends an Identity Request (old
TLLI, Identity Type = IMSI) to the MS. The MS responds with Identity Response (IMSI) and it uses
IMSI to identify itself until a TLLI is allocated.
4.
The authentication functions are defined in the section "Security Functions". If no MM context for
the MS exists anywhere in the network, then authentication is mandatory.
5.
Ciphering procedures are described in section "Security Functions". If TLLI allocation is going to be
done, and if ciphering is supported by the network, ciphering mode shall be set.
6.
The equipment checking functions are defined in the section "Identity Check Procedures".
Equipment checking is optional.
7.
If a GPRS attach is done and the SGSN address has changed since the detach (or if it is the very
first attach), routing update procedures are executed:
10
15
20
a.
The SGSN sends a Update Location (SGSN Address, IMSI) to the HLR.
b.
The HLR sends Cancel Location (IMSI) to the old SGSN.
c.
The old SGSN removes the MM and PDP contexts and acknowledges with Cancel Location
Ack (IMSI).
d.
The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN.
e.
The SGSN acknowledges with Insert Subscriber Data Ack (IMSI). The new SGSN validates
the MSs presence in the (new) RA. If due to regional, national or international restrictions the
MS is not allowed to attach in the RA or subscription checking fails, then the SGSN rejects
the Attach Request with an appropriate cause. If all checks are successful then the SGSN
constructs a MM context for the MS.
f.
The HLR acknowledges the Update Location message by sending an Update Location Ack to
the SGSN after the cancelling of old MM context and insertion of new MM context are
finished.
25
30
35
40
8.
If IMSI attach is done, the SGSN forwards the IMSI attach to the VLR. The VLR address is derived
from the RA information. If the MS is already IMSI-attached and is doing a GPRS attach, an
association is created by sending a Location Updating Request to the VLR. This marks the MS as
GPRS-attached in the VLR.
45
50
55
60
a.
The SGSN sends Location Updating Request (new LAI, IMSI, SGSN Address, GPRS Attach
State) to the VLR. GPRS Attach State indicates that the MS is attached to GPRS, and the
VLR creates an association with the SGSN by storing SGSN Address.
b.
If the LA update is inter-MSC, the new VLR sends Update Location (IMSI, new VLR) to the
HLR.
c.
If the LA update is inter-MSC, the HLR sends a Cancel Location (IMSI) to the old VLR.
d.
The old VLR acknowledges with Cancel Location Ack (IMSI).
e.
If the LA update is inter-MSC, the HLR sends Insert Subscriber Data (IMSI, GSM subscriber
data) to the new VLR.
f.
The VLR acknowledges with Insert Subscriber Data Ack (IMSI).
g.
After finishing the inter-MSC location update procedures, the HLR responds with Update
Location Ack (IMSI) to the new VLR.
Page 29
h.
9.
5
The SGSN sends an Attach Accept (TLLI, PLMN-supported MT-capabilities, TMSI) to the MS. If the
PLMN-Supported MT-Capabilities parameter indicates that only GPRS MS Class C mode of
operation is supported (i.e., the Gs interface is not installed), then a Class-A or B MS shall either:
10
15
The VLR responds with Location Updating Accept (TMSI) to the SGSN.
perform an explicit IMSI detach via the non-GPRS control channels (if the MS was already
IMSI-attached), or
access the non-GPRS control channels for CS operation (the way that CS operation is
performed in parallel with GPRS operation is a MS implementation issue outside the scope of
this specification), or
avoid all CS signalling (in which case the MS is implicitly IMSI detached after a while).
If only MS Class C mode of operation is supported, and the MS requested an IMSI attach, then the
IMSI attach was not performed.
10.
If TLLI or TMSI has changed, the MS acknowledges the received TLLI and/or TMSI with Attach
Complete (TLLI, TMSI).
11.
If TMSI was changed, the SGSN confirms the TMSI re-allocation by sending TMSI Reallocation
Complete (TMSI) to the VLR.
20
25
If the Attach Request cannot be accepted, the SGSN returns an Attach Reject (IMSI, Reject Cause)
message to the MS.
6.1.6 Detach Function
With the Detach function, a MS informs the network that it wants to make a GPRS and/or IMSI detach.
The different types of detach is IMSI detach, GPRS detach and combined IMSI / GPRS detach.
The MS is detached from GPRS either explicitly or implicitly:
30
35
Explicit detach: The SGSN or the MS explicitly requests detach.
Implicit detach: A logical link exists and the STANDBY timer expires indicating lack of activity, or an
irrecoverable MS causes disconnection of the logical link.
In the explicit detach case, a Detach Request (TLLI, Cause) is sent by the SGSN to the MS, or by the MS
to the SGSN.
The MS can make an IMSI detach in one of two ways depending on if it is GPRS-attached or not:
40
A GPRS-attached MS sends a Detach Request message to the SGSN, indicating an IMSI detach.
This can be made in combination with GPRS detach.
A MS not attached to the GPRS makes the IMSI detach as already defined in GSM.
In the 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.
45
SGSN may store the security triplets of the MS after the MS has detached from GPRS. These can be
used at a later GPRS attach.
The detach procedure when initiated by the MS is illustrated in the figure below. Each step is explained in
the following list.
Page 30
MS
BSS
SGSN
GGSN
MSC/VLR
1. Detach Request
2. Delete PDP Context
2. Delete PDP Context Ack
3. IMSI Detach Indication
4. Location Updating Request
4. Location Updating Accept
5. Detach Accept
Figure 15: Combined GPRS / IMSI Detach Procedure

1.
The MS detaches by sending Detach Request (TLLI, Detach Type, Switch Off) to the SGSN.
Detach Type indicates which type of detach that is to be performed, i.e., GPRS Detach only, IMSI
Detach only or combined GPRS and IMSI Detach. Switch Off indicates whether the detach is due to
a switch off situation or not.
2.
If GPRS detach, the active PDP contexts in the GGSNs regarding this particular MS are
deactivated by the SGSN sending Delete PDP Context Request (TEPIG) to the GGSNs. The
GGSNs acknowledge with Delete PDP Context Response (TEPIS).
3.
If IMSI detach, the SGSN sends IMSI Detach Indication (IMSI) to the VLR.
4.
If the MS wants to remain IMSI-attached and is doing a GPRS detach, the SGSN sends a Location
Updating Request (IMSI, GPRS Attach State = detached) to the VLR. The VLR marks the MS as no
longer attached to GPRS and handles the paging and location updating without going via the
SGSN. The VLR acknowledges with a Location Updating Accept (IMSI).
5.
If Switch Off indicates that the detach is not due to a switch off situation, the SGSN sends a Detach
Accept (TLLI) to the MS.
10
15
20
6.1.7 Security Function

The Security function:
25
Guards against unauthorised GPRS service usage (authentication and service request validation).
Provides user identity confidentiality (temporary identification and ciphering).
Provides user data confidentiality (ciphering).
30
6.1.7.1 Authentication of Subscriber
35
Authentication procedures already defined in GSM shall be used, with the distinction that the procedures
are executed from the SGSN. Additionally, the authentication procedure performs the selection of the
ciphering algorithm and the synchronisation for the start of ciphering. Security triplets are stored in the
SGSN. The MSC/VLR shall not authenticate the MS via the SGSN upon IMSI attach, nor Location Update,
but may authenticate the MS during CS connection establishment.
The authentication procedure is illustrated in the figure below. Each step is explained in the following list.
Page 31
MS
BSS
SGSN
HLR
1. Send Authentication Info

1. Send Authentication Info Ack
2. Authentication Request
2. Authentication Response
Figure 16: Authentication Procedure

1.
If the SGSN does not have previously stored authentication triplets, a Send Authentication Info
(IMSI) is sent to the HLR. The HLR responds with Send Authentication Info Ack (Triplets). Each
security triplet includes RAND, SRES and Kc.
2.
The SGSN sends Authentication Request (RAND, CKSN, Algorithm List). The MS responds with
Authentication Response (SRES, Algorithm Id).
10
The MS starts ciphering after sending the Authentication Response message. the SGSN starts ciphering
when a valid Authentication Response with a selected algorithm is received from the MS.
6.1.7.2 User Identity Confidentiality
15
A Temporary Logical Link Identity (TLLI) identifies a GPRS user. The relationship between TLLI and IMSI
is known only in the MS and in the SGSN. TLLI is used between the MS and the SGSN, and is unique
within a routing area. TLLI is allocated by the SGSN, and may be changed by the SGSN while a user is
attached to GPRS.
6.1.7.3 User Data Confidentiality
6.1.7.3.1 Scope of Ciphering
20
In contrast to the scope of ciphering in existing GSM (a single logical channel between BTS and MS), the
scope of GPRS ciphering is from the ciphering function at the SGSN to the ciphering function in the MS.
From the perspective of the existing GSM MS-BTS radio path, a GPRS PDU is transmitted as plain text.
MS
BTS+BSC
SGSN
Scope of GPRS ciphering

25
Scope of existing GSM ciphering
Figure 17: Scope of GPRS Ciphering

6.1.7.3.2 GPRS Ciphering Algorithm
30
A ciphering algorithm to be used for GPRS ciphering shall be selected. A new ciphering algorithm may be
designed. GSM 01.61 contains the requirements for the GPRS ciphering algorithm. The TDMA frame
number is not known at the SGSN. Therefore, a Logical Link Control frame number may replace the
TDMA frame number as an input to the algorithm.
The standard key management procedures for the Kc shall be used.
Page 32
6.1.7.4 Identity Check Procedures
MS identity check procedures already defined in GSM shall be used, with the distinction that the
procedures are executed from the SGSN.
The identity checking procedure is illustrated in the figure below. Each step is explained in the following
list.
MS
BSS
SGSN
EIR
1. Identity Request
1. Identity Response
2. Check IMEI
2. Check IMEI Ack
Figure 18: Identity Check Procedure

1.
The SGSN sends Identity Request (Identity Type) to the MS. The MS responds with Identity
Response (Mobile Identity).
2.
If the SGSN decides to check the IMEI against the EIR, it sends Check IMEI (IMEI) to EIR. The EIR
responds with Check IMEI Ack (IMEI).
10
6.1.8 Location Management Function

15
The Location Management function
provides mechanisms for cell and PLMN selection,

provides a mechanism for the network to know the Routing Area for MSs in STANDBY and READY
states, and
provides a mechanism for the network to know the cell identity for MSs in READY state.
20
Routing Area (RA) is defined in section Identities.
6.1.8.1 Routing Update Procedure
25
The MS invokes the Routing Update procedure to support the mobility of a packet-switched logical link. An
MS in READY state invokes the procedure when a new cell is selected. An MS in STANDBY state invokes
the procedure when the RA changes, or upon expiry of a periodic RA update timer.
The PLMN shall transmit sufficient system information for the MS to be able to:
30
detect when it has entered a new cell or a new RA;

determine when to perform periodic RA updates.
The MS detects that a new cell has been entered by periodically comparing the cell identity stored in its
MM context with that received from the BSS. The MS detects that a new RA has been entered by
periodically comparing the RAI stored in its MM context with that received from the BSS. The MS shall
consider hysteresis in signal strength measurements.
When the MS detects a new cell or RA, this indicates one of three possible scenarios:
35
a Cell Update is required;

a Routing Area Update is required;
a Combined Routing Area and Location Area (RA / LA) Update is required.
In all three scenarios, the MS locally re-selects a new cell, and stores the cell identity in its MM context.
40
If the MS enters a new PLMN, the MS shall not perform a routing update, but enter IDLE state.
Page 33
6.1.8.1.1 Cell Update Procedure
A Cell Update takes place when the MS enters a new cell inside the current RA and the MS is in READY
state. If the RA has changed, a Routing Area Update is executed instead of a Cell Update.
The Cell Update procedure is performed as an implicit procedure on the LLC level, i.e., normal LLC
information and control frames are used to convey the information of the cell change to the SGSN. In the
direction towards the SGSN, the cell identity shall be added to all LLC frames in the BSS.
The SGSN records this MSs change of cell, and further traffic directed towards the MS is conveyed over
the new cell.
6.1.8.1.2 Routing Area Update Procedure
10
A Routing Area Update takes place when a GPRS-attached MS detects that it has entered a new RA or
when the periodic RA update timer has expired. SGSN detects that it is an intra SGSN Routing Update by
noticing that it also handles the old RA. In this case, the SGSN has the necessary information about the
MS and there is no need to inform the GGSNs, the HLR or the MSC/VLR about the new MS location. A
periodic RA update is always an intra SGSN routing update.
15
6.1.8.1.2.1 Intra SGSN Routing Update

The intra SGSN routing update procedure is illustrated in the figure below. Each numbered step is
explained in the following list.
MS
BSS
SGSN
1. Routing Area Update Request

2. Security Functions
3. Routing Area Update Accept
4. Routing Area Update Complete
Figure 19: Intra SGSN Routing Area Update Procedure

20
25
1.
The MS sends a Routing Area Update Request (TLLI, new CI, old RAI, new RAI) to the SGSN. The
CI is added in the BSS to reduce the load on the radio interface.
2.
Security functions may be executed. These procedures are defined in section "Security Function".
3.
The SGSN validates the MSs presence in the new RA. If due to regional, national or international
restrictions the MS is not allowed to attach in the RA or subscription checking fails, then the SGSN
rejects the routing update with an appropriate cause and deletes any stored routing context for that
MS. If all checks are successful then the SGSN updates the MM context for the MS. A new TLLI
may be allocated. A Routing Area Update Accept (TLLI, Cause) is returned to the MS.
4.
If TLLI was changed, the MS acknowledges the new TLLI with Routing Area Update
Complete(TLLI).
30
35
If the routing update procedure fails a maximum allowable number of times, or if the Routing Area Update
Accept Cause parameter indicates a reject, the MS shall enter IDLE state.
Page 34
6.1.8.1.2.2 Inter SGSN Routing Update
The inter SGSN routing update procedure is illustrated in the figure below. Each numbered step is
MS
BSS
new SGSN
old SGSN
GGSN
HLR
MSC/VLR

2. SGSN Context Request
2. SGSN Context Response
4. Modify PDP Context Request
4. Modify PDP Context Response
5. Update Location
6. Cancel Location
6. Cancel Location Ack
7. Insert Subscriber Data
7. Insert Subscriber Data Ack
8. Update Location Ack
Figure 20: Inter SGSN Routing Update Procedure

5
1.
The MS sends a Routing Area Update Request (TLLI, new CI, old RAI, new RAI) to the new SGSN.
The CI is added in the BSS to reduce the load on the radio interface.
2.
The new SGSN sends SGSN Context Request (old RAI, TLLI) to the old SGSN to get the MM and
PDP contexts for the MS. The old SGSN responds with SGSN Context Response (MM context,
PDP Contexts, Triplets). If the MS is not known in the old SGSN, the old SGSN responds with an
appropriate error cause. The old SGSN stores the new SGSN address until the old MM context is
cancelled, to allow the old SGSN to forward data packets to the new SGSN.
3.
TLLI allocation is going to be done, so ciphering mode shall be set if ciphering is supported.
4.
The new SGSN sends Modify PDP Context Request (new SGSN Address, TEPIS, TEPIG, QoS) to
the GGSNs concerned. The GGSNs update their PDP context fields and return Modify PDP
Context Response (TEPIS).
5.
The SGSN informs the HLR of the change of SGSN by sending Update Location (SGSN Address,
IMSI) to the HLR.
6.
The HLR cancels the MM context in the old SGSN by sending Cancel Location (IMSI) to the old
SGSN. The old SGSN removes the MM and PDP contexts and acknowledges with Cancel Location
Ack (IMSI).
10
15
20
25
Page 35
7.
The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. The
SGSN acknowledges with Insert Subscriber Data Ack (IMSI).
8.
The HLR acknowledges the Update Location by sending Update Location Ack (IMSI) to the SGSN.
9.
If the MS is IMSI-attached the association between SGSN and VLR has to be updated. The VLR
address is derived from the RA information. The new SGSN sends Location Updating Request
(SGSN Address, GPRS Attach State, IMSI) to the VLR. The VLR stores SGSN Address and
acknowledges with a Location Updating Accept (IMSI).
10.
The new SGSN validates the MSs presence in the new RA. If due to regional, national or
international restrictions the MS is not allowed to attach in the RA or subscription checking fails,
then the SGSN rejects the routing update with an appropriate cause and deletes any stored routing
context for that MS. If all checks are successful then the SGSN constructs MM and PDP contexts
for the MS. A logical link is established between the new SGSN and the MS. The new SGSN
responds to the MS with Routing Area Update Accept (TLLI, Cause, PLMN-supported MT
capabilities). If the PLMN-Supported MT-Capabilities parameter indicates that only GPRS MS Class
C mode of operation is supported (i.e., the Gs interface is not installed), then a Class-A or B MS
shall either:
10
15
20
25
If the PLMN-Supported MT-Capabilities parameter indicates that also GPRS MS Class A and B
mode of operation is supported, and the MS used to be communicating with a SGSN that only
supports Class-C mode of operation, then a Class-A or B MS:
30
35
IMSI-attached), or
11.
that needs to perform IMSI attach and Location Updates shall do this via the SGSN;
that is already IMSI-attached shall immediately perform a Location Update via the SGSN to
allow the VLR to store the SGSN address.
The MS acknowledges the new TLLI with a Routing Area Update Complete (TLLI).
In the case of a rejected routing update operation, due to Routing Area restrictions, the SGSN shall not
construct a MM context. A reject shall be returned to the MS with an appropriate cause. The MS shall not
re-attempt a routing update to that RA. The RAI value shall be deleted when the MS is powered-up.
40
In the case of no reply from the GGSN the SGSN shall not construct a MM context. A reject shall be
returned to the MS with an appropriate cause. The MS may re-attempt updating to the same RA. As an
option the SGSN may retry the operation before rejecting the routing update.
45
6.1.8.1.3 Combined RA / LA Update Procedure
50
A combined RA / LA Update takes place when the MS enters a new LA while the MS is IMSI and GPRSattached. The MS sends a Routing Area Update Request indicating that a LA update also shall be
performed. The SGSN forwards the LA update to the VLR. This concerns only class-A and B MSs in GSM
IDLE state, as no LA updates are performed during a CS connection. A class-C MS never performs LA
updates when attached to GPRS.
Page 36
6.1.8.1.3.1 Combined Intra SGSN RA / LA Update
The combined RA / LA update (intra SGSN) procedure is illustrated in the figure below. Each numbered
step is explained in the following list.
MS
BSS
SGSN
new
MSC/VLR
HLR
old
MSC/VLR

4a. Update Location
4b. Cancel Location
Figure 21: Combined RA / LA Update in the Case of Intra SGSN RA Update Procedure
5
1.
The MS sends a Routing Area Update Request (TLLI, new CI, old RAI, new RAI, LA update
indication) to the SGSN. The CI is added in the BSS to reduce the load on the radio interface.
2.
Security functions may be executed. This procedure is defined in section "Security Function".
3.
The SGSN sends a Location Updating Request (new LAI, IMSI, SGSN Address, GPRS Attach
State) to the VLR. The VLR address is translated from the RAI via a table in the SGSN. The GPRS
Attach State indicates that the MS is attached to GPRS and the VLR creates an association with the
SGSN by storing SGSN Address.
4.
If the LA update is inter-MSC, the new VLR informs the HLR. The HLR cancels the data in the old
VLR and inserts subscriber data in the new VLR (this signalling is not modified from existing GSM
signalling and is included here for illustrative purposes):
10
15
20
a.
The new VLR sends a Update Location (new VLR) to the HLR.
b.
The HLR cancels the data in the old VLR by sending Cancel Location (IMSI) to the old VLR.
c.
d.
The HLR sends Insert Subscriber Data (IMSI, GSM subscriber data) to the new VLR.
e.
The new VLR acknowledges with Insert Subscriber Data Ack (IMSI).
f.
The HLR responds with Update Location Ack (IMSI) to the new VLR.
25
30
Page 37
5.
The new VLR allocates a new TMSI and responds with Location Updating Accept (TMSI) to the
SGSN.
6.
The SGSN validates the MSs presence in the new RA. If due to regional, national or international
restrictions the MS is not allowed to attach in the RA or subscription checking fails, then the SGSN
rejects the routing update with an appropriate cause and deletes any stored routing context for that
MS. If all checks are successful then the SGSN updates the MM context for the MS. A new TLLI
may be allocated. The SGSN responds to the MS with Routing Area Update Accept (TMSI, TLLI,
Cause).
7.
The MS confirms the TMSI and TLLI allocation by sending Routing Area Update Complete (TLLI,
TMSI) to the SGSN.
8.
The SGSN sends TMSI Reallocation Complete (TMSI) to the VLR.
10
15
If the routing update procedure fails a maximum allowable number of times, or if the Routing Area Accept
Cause parameter indicates a reject, the MS shall enter IDLE state.
If the Location Updating Accept message indicates a reject, then this should be indicated to the MS, and
the MS shall not access non-GPRS services until a successful Location Update is performed.
Page 38
6.1.8.1.3.2 Combined Inter SGSN RA / LA Update
The combined RA / LA update (inter SGSN) procedure is illustrated in the figure below. Each numbered
step is explained in the following list.
MS
BSS
new SGSN
old SGSN
GGSN
new
MSC/VLR
HLR
old
MSC/VLR

2. SGSN Context Request
2. SGSN Context Response
4. Modify PDP Context Request
4. Modify PDP Context Response
5. Update Location
6. Cancel Location
6. Cancel Location Ack
7. Insert Subscriber Data
7. Insert Subscriber data Ack
8. Update Location Ack
10a. Update Location
10b. Cancel Location
13. Routing AreaUpdate Complete
Figure 22: Combined RA / LA Update in the Case of Inter SGSN RA Update Procedure
5
10
1.
The MS sends a Routing Area Update Request (TLLI, new CI, old RAI, new RAI, LA update
indication) to the new SGSN. CI is added in the BSS to reduce the load on the radio interface.
2.
The new SGSN sends SGSN Context Request (old RAI, TLLI) to the old SGSN to get the MM and
PDP contexts for the MS. The old SGSN responds with SGSN Context Response (MM context,
PDP Contexts, Triplets). If the MS is not known in the old SGSN, the old SGSN responds with an
Page 39
appropriate error cause. The old SGSN stores the new SGSN address until the old MM context is
cancelled, to allow the old SGSN to forward data packets to the new SGSN.
3.
TLLI allocation is going to be done, so ciphering mode shall be set if ciphering is supported.
4.
The new SGSN sends Modify PDP Context Request (new SGSN Address, TEPIS, TEPIG, QoS) to
the GGSNs concerned. The GGSNs update their PDP context fields and return a Modify PDP
Context Response (TEPIS).
5.
The SGSN informs the HLR of the change of SGSN by sending Update Location (SGSN Address,
IMSI) to the HLR.
6.
The HLR cancels the MM context in the old SGSN by sending Cancel Location (IMSI) to the old
SGSN. The old SGSN removes the MM and PDP contexts and acknowledges with Cancel Location
Ack (IMSI).
7.
The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. The
SGSN acknowledges with Insert Subscriber Data Ack (IMSI).
8.
The HLR acknowledges the Update Location by sending Update Location Ack (IMSI) to the SGSN.
9.
The SGSN sends a Location Updating Request (new LAI, IMSI, SGSN Address, GPRS Attach
State) to the VLR. The VLR address is translated from the RAI via a table in the SGSN. GPRS
Attach State indicates that the MS is attached to GPRS, and the VLR creates an association with
the SGSN by storing SGSN Address.
10.
If the LA update is inter-MSC, the new VLR informs the HLR. The HLR cancels the old VLR and
inserts subscriber data in the new VLR (this signalling is not modified from existing GSM signalling
and is included here for illustrative purposes):
10
15
20
25
30
a.
The new VLR sends a Update Location (new VLR) to the HLR.
b.
The HLR cancels the data in the old VLR by sending Cancel Location (IMSI) to the old VLR.
c.
d.
The HLR sends Insert Subscriber Data (IMSI, GSM subscriber data) to the new VLR.
e.
The new VLR acknowledges with Insert Subscriber Data Ack (IMSI).
f.
The HLR responds with Update Location Ack (IMSI) to the new VLR.
35
40
11.
The new VLR allocates a new TMSI and responds with Location Updating Accept (TMSI) to the
SGSN.
12.
The new SGSN validates the MSs presence in the new RA. If due to regional, national or
international restrictions the MS is not allowed to attach in the RA or subscription checking fails,
then the SGSN rejects the routing update with an appropriate cause and deletes any stored routing
context for that MS. If all checks are successful then the SGSN establishes MM and PDP contexts
for the MS. A logical link is established between the new SGSN and the MS. The new SGSN
responds to the MS with Routing Area Update Accept (TMSI, TLLI, Cause). If the PLMN-Supported
MT-Capabilities parameter indicates that only GPRS MS Class-C mode of operation is supported
(i.e., the Gs interface is not installed), then a Class-A or B MS shall either:
45
50
55
60
IMSI-attached), or
Page 40
If the PLMN-Supported MT-Capabilities parameter indicates that also GPRS MS Class-A and B
mode of operation is supported, and the MS used to be communicating with a SGSN that only
supports Class-C mode of operation, then a Class-A or B MS:
that needs to perform IMSI attach and Location Updates shall do this via the SGSN;
that is already IMSI-attached shall immediately perform a Location Update via the SGSN to
allow the VLR to store the SGSN address.
13.
The MS confirms the TLLI and TMSI allocation by sending Routing Area Update Complete (TLLI,
TMSI) to the SGSN.
14.
The SGSN sends TMSI Reallocation Complete (TMSI) to the VLR.
10
15
In the case of a rejected routing update operation, due to Routing Area restrictions, the SGSN shall not
construct a MM context. A reject shall be returned to the MS with an appropriate cause. The MS shall not
re-attempt a routing update to that RA. The RAI value shall be deleted when the MS is powered-up.
In the case of no reply from the GGSN the SGSN shall not construct a MM context. A reject shall be
returned to the MS with an appropriate cause. The MS may re-attempt updating to the same RA. As an
option the SGSN may retry the operation before rejecting the routing update.
20
If the Location Updating Accept message indicates a reject, then this should be indicated to the MS, and
the MS shall not access non-GPRS services until a successful Location Update is performed.
6.1.8.1.4 Periodic RA and LA Updates
25
All GPRS-attached MSs, except class-B MSs engaged in CS communication, shall perform periodic RA
updates. MSs that are IMSI-attached and not GPRS-attached shall perform periodic LA updates. Periodic
RA updates are equivalent to intra SGSN routing updates as described in section Intra SGSN Routing
Update. For MSs that are both IMSI-attached and GPRS-attached, the periodic updates depend on
whether the Gs interface is installed or not:
If the Gs interface is installed, periodic RA updates shall be performed, and periodic LA updates
shall not be performed. In this case, the MSC/VLR shall disable implicit detach for GPRS-attached
MSs and instead rely on the SGSN to receive periodic RA updates. If periodic RA updates are not
received in the SGSN and the STANDBY timer times out, the SGSN shall notify the MSC/VLR by
sending an IMSI Detach Indication message.
If the Gs interface is not installed, both periodic RA updates and periodic LA updates shall be
performed independently. RA updates are performed via the Gb interface, and LA updates are
performed via the A interface.
30
35
6.1.9 PDP Context Activation and Deactivation Functions

40
These functions are only meaningful at the Network Subsystem (NSS) level and do not directly involve the
BSS. An MS in STANDBY or READY state can initiate these functions at any time to establish or delete a
virtual data channel from the MS, via SGSN, to one or more GGSNs.
For anonymous access, the MS can initiate PDP Context Activation in IDLE, STANDBY, and READY
states. An existing MM context in the SGSN is neither required nor used.
45
Upon receiving an Activate PDP Context Request message, the SGSN shall initiate procedures to set up
dynamic PDP contexts.
Upon receiving a Deactivate PDP Context Request message, the SGSN shall initiate procedures to delete
dynamic PDP contexts.
50
A MS does not have to receive the (De-)Activate PDP Context Accept message before issuing another
(De-)Activate PDP Context Request. However, only one request can be outstanding for every NSAPI.
Page 41
6.1.9.1 Static and Dynamic PDP Addresses
PDP addresses can be allocated to a MS in three different ways:
The HPLMN operator assigns a PDP address permanently to the MS (static PDP address).
The HPLMN operator assigns a PDP address to the MS when a PDP context is activated (dynamic
HPLMN PDP address).
The VPLMN operator assigns a PDP address to the MS when a PDP context is activated (dynamic
VPLMN PDP address).
10
It is the HPLMN operator that defines in the subscription whether a dynamic HPLMN or VPLMN PDP
address can be used.
When dynamic addressing is used, it is the responsibility of the GGSN to allocate and release the dynamic
PDP address.
15
Only dynamic PDP addressing is applicable in the anonymous access case.

6.1.9.2 PDP Context Activation Procedure
The PDP Context Activation procedure is illustrated in the figure below. Each numbered step is explained
in the following list.
MS
SGSN
GGSN
1. Activate PDP Context Request

3. Create PDP Context Request
3. Create PDP Context Accept
4. Activate PDP Context Accept
Figure 23: PDP Context Activation Procedure

20
1.
The MS sends an Activate PDP Context Request (TLLI, PDP Type, PDP Address, requested QoS,
NSAPI) message to the SGSN. The MS indicates its wish to use a dynamic PDP address by leaving
the PDP Address parameter empty. In the case of anonymous access, a random MS identifier is
used.
2.
3.
The SGSN checks that the MS is allowed to activate the PDP address against the subscription data
which was stored in the SGSN during GPRS attach and allocates a TEPIS if allowed. The
subscription check is not applicable in the anonymous access case. If the MS requests a dynamic
address but only a static PDP address is subscribed to, then the subscribed PDP address is used.
If the MS requests a dynamic address and a dynamic PDP address is allowed, then the SGSN lets
the (first) GGSN allocate the dynamic address. The SGSN may restrict the requested QoS values
given its capabilities and the current load. The SGSN sends Create PDP Context Request (PDP
Type, PDP Address, negotiated QoS, TEPIS) messages to the affected GGSNs. Each GGSN
creates a new entry in its PDP context table. The new entry allows the GGSNs to route PDP PDUs
between the SGSN and the external PDP networks. Each GGSN then allocates a TEPIG and
returns a Create PDP Context Accept (TEPIS, TEPIG, Cause) to the SGSN. The Create PDP
Context messages are sent over the GPRS backbone network.
25
30
35
40
Page 42
4.
10
SGSN inserts the NSAPIs in its PDP Contexts along with the GGSN addresses and TEPIGs
received from the GGSNs. The SGSN returns an Activate PDP Context Accept (TLLI, PDP Type,
PDP Address, NSAPI, negotiated QoS, Cause) message to the MS. In the case of anonymous
access, the message contains a new assigned TLLI. The SGSN is now able to route PDP PDUs
between the GGSNs and the MS. For each PDP Address a different Quality of Service may be
requested. For example, some PDP addresses may be associated with E-mail that can tolerate
lengthy response times. Other applications cannot tolerate delay and demand a very high level of
throughput, interactive applications being one example. These different requirements are reflected
in the QoS. The QoS values are defined in GSM 02.60. If a PDP address QoS requirement is
beyond the capabilities of a PLMN, the PLMN negotiates the QoS as close as possible to the
requested QoS. The MS either accepts the negotiated QoS, or deactivates the PDP context.
After an SGSN has successfully updated the GGSNs, the PDP contexts associated with an MS is
distributed as shown in section Information Storage.
15
If the PDP context activation procedure fails or if the Activate PDP Context Accept Cause parameter
indicates a reject, then the MS may attempt another activation to the same PDP address up to a maximum
number of attempts.
6.1.9.3 PDP Context Deactivation Procedure
20
The PDP Context Deactivation procedure is illustrated in the figure below. Each numbered step is
MS
SGSN
GGSN
1. Deactivate PDP Context Request

3. Delete PDP Context Request
3. Delete PDP Context Accept
4. Deactivate PDP Context Accept
Figure 24: PDP Context Deactivation Procedure
25
1.
The MS sends a Deactivate PDP Context Request (TLLI, NSAPI) message to the SGSN.
2.
3.
SGSN sends Delete PDP Context Request (TEPIG). Each GGSN removes the PDP context and
returns a Delete Context Accept (TEPIS) to the SGSN. If the MS was using a dynamic PDP
address, then the GGSN releases this PDP address and makes it available for subsequent
activation by other MSs. The Delete PDP Context messages are sent over the GPRS backbone
network.
4.
The SGSN returns a Deactivate PDP Context Accept (TLLI, NSAPI) message to the MS.
30
35
At GPRS detach, all PDP contexts for the MS are deactivated.

6.2 Network Management Functionality
The Network Management function provides mechanisms to support O&M functions related to GPRS.
Page 43
6.3 Radio Resource Functionality
6.3.1 Cell Selection and Reselection
An MS (of any class A, B, or C) cannot be camped on more than one cell. This means that the cell
selection and reselection procedure should choose cells that support services the user has subscribed to.
5
If the MS is in IDLE mode (GSM 03.22) and the MS invokes the GPRS service, i.e., wishes to initiate the
GPRS Attach procedure to enter GPRS STANDBY or READY state, the following applies:
If the currently camped-on cell supports GPRS then no cell reselection is required.
If the currently camped-on cell does not support GPRS, then reselection of a cell supporting GPRS
is required before execution of the Attach procedure.
10
If the MS is in STANDBY state, a modified version of the cell reselection procedures presented in GSM
03.22 shall be used. The cell reselection procedure shall be modified to support GPRS.
15
If the MS is in READY state, a modified version of the cell reselection procedures presented in GSM 03.22
and GSM 05.08 shall be used. The cell reselection procedure shall be modified to minimise the cell
changes. It may be necessary to co-ordinate the idle and connected mode procedure used for circuitswitched services with the READY state procedure for MS classes A and B.
6.3.2 Radio Resource Management
20
GSM Radio Resource Management (RRM) functions are defined in GSM 04.07. The RIL3-RR protocol is
specified in GSM 04.08. Additional functions and procedures may be required to support GPRS services.
6.3.2.1 Layer Functions
GPRS Radio Resource Management procedures are required for the following functions:
25
Allocation and release of physical resources (i.e., timeslots) associated with a GPRS channel.
Monitoring GPRS channel utilisation to detect under-utilised or congested GPRS channels.
Initiating congestion control procedures.
Distribution of GPRS channel configuration information for broadcasting to the MSs.
30
BSSGP provides a signalling channel between the GSN and the BSS to support RRM procedures.
6.3.2.2 Model of Operation
6.3.2.2.1 Dynamic Allocation of Radio Resources
A cell may or may not support GPRS.
35
A cell supporting GPRS may have GPRS radio resources allocated at a given instance. If no GPRS radio
resources are allocated, a MS can request allocation of such resources. MSs may then use these radio
resources. The PLMN may dynamically increase, to a PLMN operator-defined maximum, or, decrease to
an operator-defined minimum, the radio resources allocated.
The PLMN periodically transmits GPRS system information on the BCCH.
40
GSM radio resources are dynamically shared between GPRS and other GSM services.
6.3.3 Paging for GPRS Downlink Transfer
A MS in STANDBY state is paged by the SGSN before a downlink transfer to that MS. The paging
procedure shall move the MM state to READY to allow the SGSN to forward downlink data to the radio
Page 44
resource. Therefore, any uplink data from the MS which moves the MM context at the SGSN to READY
state is a valid response to paging. The SGSN supervises the paging procedure with a timer.
The MS shall accept pages also in READY state if no radio resource is assigned. This supports recovery
from inconsistent MM states in MS and SGSN.
5
The paging procedure is illustrated in the figure below. Each numbered step is explained in the following
list.
MS
BSS
SGSN
1. PDP PDU
2. Paging Request
3. GPRS Paging Request
4. Any LLC Frame
5. Any LLC Frame
Figure 25: GPRS Paging Procedure

1.
The SGSN receives a downlink PDP PDU for an MS in STANDBY state. Downlink signalling to a
STANDBY state MS initiates paging as well.
2.
The SGSN sends a BSSGP Paging Request (IMSI, TLLI, Area, Channel Needed) message to the
BSS serving the MS. IMSI is needed by the BSS in order to calculate the MS paging group. TLLI
and Area are derived from the MSs MM context in the SGSN. TLLI is the identifier by which the MS
is paged. Area indicates the routing area in which the MS is paged. Channel Needed indicates
GPRS paging.
3.
The BSS pages the MS with one Paging Request (TLLI, Channel Needed) message in each cell
belonging to the addressed routing area. This is described in GSM 03.64.
4.
Upon receipt of a GPRS Paging Request message, the MS shall respond with either any single
valid LLC frame (e.g., a Receive Ready or Information frame) which implicitly is interpreted as a
page response message by the SGSN. When responding, the MS changes MM state to READY.
The response is preceded by the Packet Channel Request and Packet Immediate Assignment
procedures as described in GSM 03.64.
5.
Upon reception of the LLC frame, the BSS adds CI and sends the LLC frame to the SGSN. The
SGSN shall then consider the LLC frame to be an implicit paging response message and stop the
paging response timer.
10
15
20
25
30
6.4 Packet Routing and Transfer Functionality
6.4.1 Definition of Packet Data Protocol States
35
A PTP GPRS subscription contains the subscription of one or more PDP addresses. Each PDP address is
described by an individual PDP context in MS, SGSN and 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.
6.4.1.1 INACTIVE State
40
The INACTIVE state characterises the data service for a certain PDP address of the subscriber as not
activated. The PDP context of the involved entities contains no routing or mapping information to process
PDUs related to that PDP address. No data can be transferred. A changing location of a subscriber
Page 45
causes no update for the PDP context in INACTIVE state even if the subscriber is attached to the GPRS
MM.
Mobile-terminated PTP packets received in this state invoke error procedures in GGSN relevant to the
external network protocol, for example, an IP packet is discarded and an ICMP packet (error notification)
is returned to the source of the received packet. Other error procedures may be introduced on the
application level, but this is outside the scope of this document.
The MS initiates the movement from INACTIVE to ACTIVE state by transmitting an Activate PDP Context
Request message. If a PDP context to be activated does not exist, then a PDP context is created and the
state is set to ACTIVE.
10
15
6.4.1.2 ACTIVE State

In ACTIVE state, the PDP context for the PDP address in use is activated in MS, SGSN and GGSN. The
PDP context contains mapping and routing information for transferring PDUs for that particular PDP
address between MS and GGSN. The ACTIVE state PDP context is updated according to changed
subscriber location initiated by mobility management procedures, e.g., SGSN address and TEPIs. The
PDP state ACTIVE is permitted only when the mobility management state of the subscriber is STANDBY
or READY.
An active PDP context for an MS is moved to INACTIVE state when the MS sends a Deactivate PDP
Context Request message.
All active PDP contexts for an MS are moved to INACTIVE state when the MM state changes to IDLE.
INACTIVE
Activate PDP
Context
Deactivate PDP Context

or
MM state change to IDLE
ACTIVE
Figure 26: Functional PDP State Model
20
6.4.2 Packet Routing and Transfer Function

The packet routing and transfer function:
routes and transfers packets between a mobile TE and an external network, i.e., between the
reference points R or S and reference point Gi,
routes and transfers packets between mobile TE and other GPRS PLMN, i.e., between the
reference points R or S and interface Gp, and
routes and transfers packets between TEs within the same GPRS PLMN, i.e., between the R or S
interface in different MSs.
25
30
Between the SGSN and the MS, PDP PDUs are transferred with the SNDC protocol.
Page 46
Between the SGSN and the GGSN, PDP PDUs are routed and transferred with the IP protocol. The
GPRS Tunnelling Protocol transfers data through tunnels. A tunnel is identified by a tunnel endpoint
identifier (TEPI) and a GSN address.
To support roaming GPRS subscribers, and for forward compatibility, the SGSN is not required to know
the tunnelled PDP. Every SGSN shall have the capability to transfer PDUs belonging to PDPs not
supported in the PLMN of the SGSN.
6.4.3 Packet Terminal Adaptation Function
The Packet Terminal Adaptation function adapts packets received from and transmitted to the Terminal
Equipment to a form suitable for transmission within GSM.
10
15
A range of MT versions providing different standard interfaces towards the TE can be used, e.g.:
MT with asynchronous serial interface and PAD (Packet Assembly / Disassembly) support (e.g., AT
command set PAD, X.28 / X.29 / X.3 PAD). In the case when the PAD function does not exist in the
MT, it exists in the TE.
"Integrated MT" with industry standard application program interface.
MT with synchronous serial interface.
6.4.4 Encapsulation Function

20
25
GPRS transparently transports PDP PDUs between external networks and mobile stations. All PDP PDUs
are encapsulated and decapsulated for GPRS routing purposes. Encapsulation functionality exists at the
mobile station, at the SGSN, and at the GGSN. Encapsulation allows PDP PDUs to be delivered to and
associated with the correct PDP context in the MS, the SGSN, or the GGSN. Two different encapsulation
schemes are used; one for the GPRS backbone network between two GSNs, and one for the GPRS
connection between SGSN and MS.
30
In the PTP case, encapsulation requires that the MS is attached to GPRS, and that the PDP Context
Activation procedure has been executed. If the Attach or PDP Context Activation procedures cannot be
successfully executed, then uplink-bound PDP PDUs are discarded in the MS. If these procedures have
not been executed when a downlink-bound PDP PDU arrives in the GGSN, then the downlink PDP PDU
may for example be discarded or forwarded [FFS].
6.4.4.1 Encapsulation Between SGSN and GGSN
The GPRS backbone network encapsulates a PDP PDU with a GPRS Tunnelling Protocol header, and
inserts this GTP PDU in an IP PDU. The IP and GTP PDU headers contain the GSN addresses and
tunnel endpoint identifier necessary to uniquely address a GSN PDP context.
35
6.4.4.2 Encapsulation Between SGSN and MS
40
Between SGSN and MS, an SGSN or MS PDP context is uniquely addressed with a temporary logical link
identity and a network layer service access point identifier pair. TLLI is assigned when the MS initiates the
Attach function. NSAPIs are assigned when the MS initiates the PDP Context Activation function. The
relationship between TLLI / NSAPI and LLC / SNDCP is illustrated in figure Multiplexing of Network
Protocols. TLLI and NSAPI are described in section Identities.
6.5 Message Screening Functionality
This screening mechanism is commonly called packet filtering in routers and firewalls, since it provides a
filter for which packets to allow and which to deny.
Three different kinds of message screening shall be supported:
45
Network-controlled screening: This is used to protect the GPRS network from known security
problems. The same screening applies for all MS users.
Page 47
Subscription-controlled screening: This is based on the subscription and is subject to agreement

between the subscriber and the operator.
These types of screening are outside the scope of GPRS standardisation.

5
7. Compatibility Issues
Non-GPRS MSs in GSM PLMNs that support GPRS shall, without changes, be able to continue operation.
GSM PLMNs that do not support GPRS shall, without changes, be able to continue interworking with GSM
PLMNs that do support GPRS.
8. Transmission
10
8.1 Logical Link Control Functionality

The Logical Link Control (LLC) protocol provides a reliable logical link between the MS and its SGSN. As
shown in section Transmission and Signalling Planes, the LLC layer is situated below the SNDC layer.
8.1.1 Layer Services
15
The purpose of the LLC layer is to convey information across the GPRS radio interface. The LLC
functions provide the services necessary to maintain communications capability between the MS and a
SGSN. The LLC layer does not support direct communication between two MSs.
The LLC connection may be maintained as the MS moves between cells served by the same SGSN.
When the MS moves to a cell being served by different SGSN, the existing connection is released and a
new logical connection is established with the new SGSN.
20
25
The LLC connection can be used to transfer Point-To-Point (PTP) and Point-To-Multipoint (PTM) data
between the MS and its SGSN.
LLC shall be independent of the underlying radio interface protocols. In order to allow LLC to operate with
a variety of different radio interface protocols, and to ensure optimum performance, it may be necessary to
adjust e.g., the maximum LLC PDU length the LLC protocol timer values. Such adjustments can be made
through negotiation between the MS and the SGSN.
8.1.2 Layer Functions
The GPRS Logical Link Control layer supports:
30
35
Service primitives allowing the transfer of SNDCP Protocol Data Units (SN-PDUs) between the
Subnetwork Dependent Convergence layer and the Logical Link Control layer.
Procedures for transferring LL-PDUs between the MS and SGSN, including:
Procedures for unacknowledged point-to-point delivery of LL-PDUs between the MS and the
SGSN.
Procedures for acknowledged, reliable point-to-point delivery of LL-PDUs between the MS

and SGSN.
Procedures for point-to-multipoint delivery of LL-PDUs from the SGSN to the MS.
Procedures for detecting and recovering from lost or corrupted LL-PDUs.
Procedures for flow control of LL-PDUs between the MS and the SGSN.
8.1.3 Service Primitives

40
The following table lists the service primitives provided by the LLC layer to the SNDC layer:
Page 48
Table 2: LLC Service Primitives
Name
LL-ESTABLISH
Request
x
Indication
x
LL-REJECT
Response Confirm
x
LL-RELEASE
LL-DATA
x
x
x
x
LL-UNITDATA
LL-ERROR
Comments
Establishes a logical connection
between the MS and its SGSN.
Indicates the rejection of LLESTABLISH.
Releases the logical connection.
Requests the acknowledged
transfer of a SN-PDU.
Request the unacknowledged
transfer of a SN-PDU.
Indicates error in LLC transfer.
8.1.4 Modes of Operation
Two modes of operation of the LLC layer are defined for the SNDC layer information transfer;
unacknowledged and acknowledged. The LLC layer supports both modes simultaneously.
10
In acknowledged mode, the receipt of LL-PDUs are confirmed. The LLC layer retransmits LL-PDUs
if confirmation has not been received within a timeout period.
In unacknowledged mode, there is no confirmation required for LL-PDUs.
The LLC layer shall support several different quality of service (QoS) classes offering different transfer
delay characteristics.
8.2 Subnetwork Dependent Convergence Functionality
15
The Subnetwork Dependent Convergence (SNDC) protocol is situated below the network layer and above
the Logical Link Control layer in the MS and the SGSN, as shown in section Transmission and Signalling
Planes. A variety of network layers are supported, e.g., IP, X.25, PTM-M, PTM-G, SMS, and GPRSspecific signalling. The network layer protocols share the same SNDCP, which then performs multiplexing
of data coming from the different sources to be sent across LLC. This is illustrated in the figure below.
Signalling
Packet Data
Protocol
SMS
N-PDU
NSAPI
SNDCP
SNDC Header
NSAPI + Control
Data
LLC Header
TLLI + Control
SN-PDU
LLC
TLLI
RLC or BSSGP
Figure 27: Multiplexing of Network Protocols
Page 49
The following identities and control information is needed:
NSAPI identifies the network layer. The SNDCP control part contains compression and ciphering
information.
TLLI identifies the MS. The LLC control part contains the rest of the LLC protocol header.
The Subnetwork Dependent Convergence function is defined in terms of service primitives, offered
services, and sub-functions.
8.2.1 Service Primitives
10
Interaction between network layer protocols and SNDCP is described with the following service primitives:
15
SN-DATA.(Request, Indication)
SN-UNITDATA.(Request, Indication)
The SN-DATA primitive is used for acknowledged transfer of network layer PDUs (N-PDUs). Receipt of
data shall be acknowledged at the LLC layer. The SN-DATA primitive conveys NSAPI, TLLI, a subnetwork
quality-of-service parameter, and a N-PDU.
The SN-UNITDATA primitive is used for unacknowledged data transfer. Receipt of data is not
acknowledged by SNDCP or lower layers. The SN-UNITDATA primitive conveys NSAPI, TLLI, a
subnetwork quality-of-service parameter, and a N-PDU.
20
Interaction between SNDCP and LLC is described with the following service primitives:
25
LL-DATA.(Request, Indication)
LL-UNITDATA.(Request, Indication)
The LL-DATA primitive is used for acknowledged data transfer. Receipt of data shall be confirmed by
LLC. The LL-DATA primitive conveys the TLLI, a subnetwork quality-of-service parameter, and a SNPDU.
The LL-UNITDATA primitive is used for unacknowledged data transfer. Receipt of data is not confirmed
by LLC. The LL-UNITDATA primitive conveys the TLLI, a subnetwork quality-of-service parameter, and a
SN-PDU.
30
8.2.2 Services
The SNDC function provides the following services to the network layer:
35
40
Transmission and reception of variable-length N-PDUs with a maximum length of 1600 octets
between the SGSN and MS.
Transmission and reception of N-PDUs between the SGSN and MS according to the selected QoS
class.
Transfer of the minimum amount of data possible between the SGSN and MS through compression
techniques.
Ciphered transmission of N-PDUs.
The SNDC function requires the following services from the LLC layer:
45
Acknowledged and unacknowledged data transfer.
Point-to-point and point-to-multipoint data transfer.
Priority-based transfer of SN-PDUs. 4 priority levels shall be supported.
Page 50
In-order delivery of SN-PDUs per QoS class. I.e., SN-PDUs with the same priority are delivered in
the order transmitted.
Support for variable length SN-PDUs.
5
8.2.3 Subfunctions
SN-UNITDATA.Request
SN-DATA.Request
Network Layer
Compression
Segmentation
De-compression
SNDC Layer
Ciphering
LL-UNITDATA.Request
LL-DATA.Request
SN-UNITDATA.Indication
SN-DATA.Indication
Reassembly
De-ciphering
LLC Layer
LL-UNITDATA.Indication
LL-DATA.Indication
Figure 28: Sequential Invocation of SNDC Functionality

SNDCP performs the following subfunctions:
10
15
Multiplexing of N-PDUs from one or several network layers onto LLC.
Mapping of SN-UNITDATA primitives received from the network layer into corresponding LLUNITDATA primitives to be passed to the LLC layer. SN-UNITDATA can be used for PTP, PTM-G,
and PTM-M services.
Mapping of SN-DATA primitives received from the network layer into corresponding LL-DATA
primitives to be passed to the LLC layer. SN-DATA can be used for PTP and PTM-G services.
Compression of redundant protocol control information and user data. This may include e.g.,
TCP/IP header compression and V.42bis data compression. Compression is performed
independently for each QoS class, and may be performed independently for each network layer.
Compression is not applicable for signalling and SMS. Compression is an optional SNDC function.
Management of the delivery sequence according to the QoS class of SN-UNITDATA and SN-DATA
primitives.
Segmentation and reassembly. The output of the compression subfunctions are segmented to
maximum-length LLC frames.
Ciphering of PDUs to provide user data and signalling confidentiality. Ciphering shall be done
before segmentation if ciphering changes the size of the data.
20
25
30
Page 51
8.3 Gb Interface
The Gb interface connects the BSS and the SGSN, allowing the exchange of signalling information and
user data.
8.3.1 Link Layer Protocols
5
The Gb interface link layer is based on Frame Relay. A semi-permanent connection(s) is established
between SGSN and BSS. LLC PDUs from many users are multiplexed on a connection. The Frame Relay
connection between BSS and SGSN may be multi-hop and traverse a network of Frame Relay switching
nodes. Frame Relay shall be used for signalling and data transmission.
8.3.2 Configuration and Allocation of Physical Resources
10
15
In contrast to the A interface, which is configured as a set of point-to-point trunks between the MSC and
BSS, the Gb interface may be configured with a transit network between the SGSN and BSS. This
provides three configurations (more are possible):
a physical point-to-point link between the SGSN and BSS;

a physical point-to-point link into a transit network;
nailed-up physical point-to-point links via the MSC site into a transit network.
SGSN
SGSN
N/W
router
Transit
network
(a)
N/W
router
(b)
Gb
N/W
router
Gb
BSS
MSC
site
(c)
Gb
BSS
BSS
Figure 29: Gb Interface Configurations
20
Logically, configuration options b) and c) do not differ. Physically, option b) would mean implementing a
second E1, or a fraction thereof, in the BSS while option c) shares existing E1 resources with circuitswitched traffic. In option c), if Gb-interface capacity is dynamically allocated across the A interface,
signalling changes may be required.
There are two ways to allocate physical terrestrial resources for GPRS usage on the Gb interface:
Permanent (nailed-up) allocation of physical resources. In this case, there is no need for connection
management messages as no physical resources are dynamically allocated or deallocated for the
Gb interface. Allocation of resources is via O&M procedures.
Dynamic allocation of the physical resources. In this case, the BSS and SGSN allocate physical
resources using signalling.
25
30
8.3.3 Configuration Dependence
Signalling across the Gb interface is divided into configuration independent signalling and configuration
dependent signalling. Configuration independent signalling is divided into the following signalling subsets:
Page 52
10
User-related signalling. E.g., mobility management for an MS.
SGSN-BSS node management signalling. One node notifies the other node of problems or
inconsistencies, e.g. Reset in the event of equipment failures.
Packet channel allocation signalling, e.g., the setting up of a virtual connection from the SGSN to a
group of radio resources within a BTS.
Configuration dependent signalling is applicable in some configurations of the Gb interface but not in
others. Three cases are identified:
If the Gb interface is configured as a permanent (nailed-up) allocation of physical resources, no

additional signalling is required.
If the Gb interface is configured for dynamic allocation of physical point-to-point circuits between the
SGSN and BSS, additional signalling is required. BSSMAP-like circuit allocation signalling
(Assignment, Release, and Terrestrial Resource messages), or an equivalent protocol, is required.
If the Gb interface is configured for dynamic allocation of physical circuits across a transit network,
point-to-point dynamic circuit allocation is insufficient.
15
20
If the Gb interface is routed via an MSC site, the last two configurations may require changes to the A
interface.
Table 3: Configuration Independent and Dependent Signalling
Total required BSSGP signalling for dynamically allocated terrestrial resources:
Configuration independent signalling:
Packet channel messages.
Mobile User messages.
General messages.
Configuration dependent signalling:
Allocation of physical resources.
25
The BSSGP signalling message structure is adapted from GSM 08.08.

Table 4: BSSGP Messages
BSSGP message category
Packet channel messages
Mobile User messages
General messages
Physical allocation messages
Functionality supported by message category

This function manages the (de)allocation of a virtual connection
between the SGSN and the GPRS radio resources of a BTS.
User-specific transmission functions.
Node management functions.
This function includes the capability to allocate physical
resources across numerous configurations, e.g., an SGSNBSS configuration implemented via a transit network.
8.3.4 Transmission Plane Signalling Between the SGSN and BSS for a BTS
8.3.4.1 Switched and Permanent Virtual Circuits
30
It is a service deployment issue whether to use switched virtual circuits or permanent virtual circuits
across the Gb interface. Switched virtual circuits, the more complex case, is used in the text below.
8.3.4.2 Routing Data over the Gb Interface
In order to assign a transmission path from the SGSN to the BSS across the Gb interface, two resources
have to be allocated:
35
Physical terrestrial resources between the SGSN and the BSS.
Page 53
10
Virtual circuit resources, e.g., a layer 2 and/or 3 packet multiplexing protocol connection over the
SGSN-BSS terrestrial resources.
In contrast to a circuit-switched connection, a physical terrestrial circuit is not directly mapped onto a radio
channel (timeslot). Instead, a virtual circuit identity code (VCIC) is, in the NSS, mapped onto a SGSN and,
in the BSS, a logical BTS address. Many virtual circuits may operate over the same Gb physical circuit
between one SGSN and one or several BTSs. Data routed from the SGSN to the BTS via the virtual
circuit, is merely delivered to the BSS. Thereafter, it is the responsibility of the BSS to deliver the data to
the correct BTS. Only the BSS knows the instantaneous allocation of radio resources. Only the BSS
controls the allocation of radio resources. This is shown figuratively below.
BSS part
NSS part
BTS-1
BSC
PCU
BTS-x
N/W
router
Transit network
SGSN
BTS-1
BSC
BTS-y
PCU
Physical trunk(s)
Virtual circuit
Gb interface
Gb interface
Figure 30: Virtual Circuits Between NSS and BSS
8.3.4.3 Contention Mode and Non-Contention Mode
15
In contention mode, a virtual circuit identifies a packet route shared by multiple MSs. In non-contention
mode, in order to meet a particular QoS requirement, it shall be possible for a (different) virtual circuit to
identify transmission plane resources that have been reserved for a single MS.
8.3.4.4 Initialisation of a Virtual Circuit Between the BSS and SGSN for a BTS
20
When bringing a BTS into GPRS service, a virtual circuit from the BSS to the SGSN shall be allocated.
The obtained VCIC and the CI are sent to the SGSN. The SGSN then establishes a packet routing
relationship between the VCIC and BTS. The same procedure is used to establish a virtual circuit that is
related to a non-contention mode of operation, contention mode or non-contention mode is indicated with
the Contention Mode parameter.
BSS SGSN
|
|
|---->| Virtual Circuit Request (e.g., based on Frame Relay)
|
|
|<----| Virtual Circuit Confirm
|
|
(VCIC)
|---->| Assign Packet Channel Request
|
|
(VCIC, CI, Contention Mode)
|<----| Assign Packet Channel Confirm
|
|
(VCIC, CI)
|
|
Figure 31: Establishing a Virtual Circuit Between the BTS and SGSN
25
Page 54
8.3.4.5 Flow Control Between the SGSN and BSS for a BTS
Across the Gb interface, user data traffic between the SGSN and BTS is flow controlled on the basis of
the QoS associated with the user data. Typically, during periods of BTS congestion, the BSS (or SGSN)
reduces user data traffic based on QoS levels. The lowest QoS level user data is reduced first. After
congestion has eased, the flow control initiator signals the cleared congestion state to its peer entity.
BSS SGSN
|
|
|<----| Flow Control Request
|
|
(VCIC, QoS Allowed)
|---->| Flow Control Confirm
|
|
Figure 32: SGSN-originated Flow Control
BSS SGSN
|
|
|---->| Flow Control Request
|
|
(VCIC, QoS Allowed)
|<----| Flow Control Confirm
|
|
Figure 33: BSS-originated Flow Control
10
8.3.4.6 Release of Virtual Circuit Between the SGSN and BSS for a BTS
The SGSN shall be able to release the virtual circuit between the SGSN and BSS, related to a BTS.
BSS SGSN
|
|
|<----| Clear Packet Channel Request
|
|
(VCIC)
|---->| Clear Packet Channel Confirm
|
|
(VCIC)
|<--- | Release Virtual Circuit Request
|
|
(VCIC)
|---->| Release Virtual Circuit Confirm
|
|
Figure 34: SGSN-originated Virtual Circuit Release
The BSS shall be able to release the virtual circuit between the SGSN and BSS, related to a BTS.
BSS SGSN
|
|
|---->| Clear Packet Channel Indication
|
|
(VCIC)
|---->| Release Virtual Circuit Request
|
|
(VCIC)
|<----| Release Virtual Circuit Confirm
|
|
15
Figure 35: BSS-originated Virtual Circuit Release
Page 55
8.3.5 Mobile User Messages
Table 5: MS-related BSSGP Messages
Messages
Data Request
Direction
SGSN BSS
Unitdata Request
SGSN BSS
Data Confirm
BSS SGSN
Unitdata Confirm
BSS SGSN
Data Indication
BSS SGSN
Flush Request
SGSN BSS
Paging Request
SGSN BSS
Information Elements
Channel Id
MS Id
Transaction Id
QoS
MS Capabilities
DRX Mode
MS Id New
SDU
IMSI
Area
Group Id or MS Id
Transaction Id
QoS
DRX Mode
Number of Repetitions
SDU
IMSI
Channel Id
Transaction Id
Status
QoS
Area
Transaction Id
Status
QoS
Channel Id
MS Id
QoS
SDU
Channel Id or Area
Group Id or MS Id
Transaction Id
Area
MS Id
IMSI
8.3.5.1 Data Request

5
10
This message is submitted by the SGSN to request transmission of a SDU (an LLC PDU) to a certain MS
in READY state. If the BSS maintains a context for the receiver that radio context is also identified by the
Channel Id and MS Id. The QoS and MS Capabilities are used to allocate appropriate radio resources.
The Transaction Id supports indication of the transfer status and flow control between the BSS and the
SGSN. This supports receiver dependent control of the downlink data flow.
The BSS uses RLC level ARQ in transferring data to the MS.
The DRX Mode indicates whether the receiver is using DRX in READY state. In that case, IMSI is
provided for the BSS to calculate the subgroup.
BSSGP Flush Request can be used for terminating the data transfer request.
8.3.5.2 Unitdata Request
15
This message is submitted by the SGSN to request a transmission of a SDU (an LLC PDU) to a certain
MS that is in the READY state or a group of mobiles as indicated by the Group Id or MS Id. The Area is
included so that the BSS can forward the data to the right location(s). The QoS and Number of Repetitions
Page 56
are used to allocate appropriate radio resources. The Transaction Id supports indication of the transfer
status and flow control between the BSS and the SGSN. This support receiver dependent control of the
downlink data flow.
The BSS is not using RLC level ARQ in transferring data to the MS(s) because the BSS cant get
acknowledges from the mobile(s). Instead, the BSS repeats sending the same data over the radio
(according to the QoS specification) to improve reliability of the data transfer.
The DRX Mode indicates whether the receiver is using DRX in the READY state. In that case, IMGI or
IMSI is provided for the BSS to calculate the subgroup.
BSSGP Flush Request can be used for terminating the data transfer request.
10
8.3.5.3 Data Confirm

This message is sent by the BSS to provide transfer status for a certain SDU (LLC PDU) indicated by the
Channel Id and the Transaction Id and to flow control the SGSN. This supports receiver-dependent control
of the downlink data flow.
The actual QoS used at the radio interface is returned to the SGSN.
15
8.3.5.4 Unitdata Confirm

This message is sent by the BSS to provide transfer status for a certain SDU (LLC PDU) indicated by the
Area and the Transaction Id and to flow control the SGSN. This supports receiver-dependent control of
the downlink data flow.
The actual QoS used at the radio interface is returned to the SGSN.
20
8.3.5.5 Data Indication

This message is sent by the BSS to the SGSN to indicate a SDU (LLC PDU) received from a MS. The
BSS adds into the BSSGP header the Channel Id (where the MS is located), and MS Id and QoS (that
were indicated by the MS and used on the radio interface).
8.3.5.6 Flush Request
25
This message is sent by the SGSN to the BSS to indicate that the transmission request for a certain SDU
that is identified by the Channel Id or Area, the Group Id or MS Id, and/or the Transaction Id is no more
valid and can be removed from the BSS. This is useful in buffer handling and optimizing the radio usage.
8.3.5.7 Paging Request
30
This message is sent by the SGSN to the BSS when the SGSN wants to determine the accurate location
of the MS identified by MS Id. The BSS pages the MS in all those cells that are specified in the Area. The
IMSI is used to calculate the paging groups. The MSs paging response from the BSS to the SGSN is a
normal BSSGP Data Indication message.
8.3.6 General Messages
These messages are associated with node management.
35
Table 6: BSSGP General Messages

Messages
As defined in GSM 08.08, except the NSS node is the
SGSN and not MSC.
Direction
SGSN BSS
BSS SGSN
Information Elements
Stage-3 issue.
The operating principle of these messages is as follows: messages sent between the NSS node, i.e., a
MSC or SGSN, and the BSS, only relate to functionality and resources within each nodes control. For
example, a Reset message sent from the MSC to the BSS, indicating that an equipment failure has
Page 57
caused a loss of active call processing information, results in all circuit calls and call setups being cleared
at the BSS. It does not cause the BSS to clear resources allocated to GPRS. When the BSS loses circuitswitched and GPRS-operating contexts, the BSS sends a Reset to both the MSC and SGSN.
8.3.7 Physical Resources Allocation
5
Dynamic allocation of physical resources is not supported in a first release of the GPRS specifications.
Physical resource allocation is a stage-3 issue.
8.3.8 BSSGP Messages Information Elements
These elements are used in Mobile User, General, and virtual-circuit related messages.
Page 58
Table 7: BSSGP Information Elements
Information element
Area
Channel Id
Circuit Pool List

Contention Mode
DRX Mode
Extended Resource
Indicator
Group Id
Explanation
Indicates the area to where the
unit data or paging should be
transmitted.
Identifies a radio resource in the
cell of the BSS.
Ref. GSM 08.08 (3.2.2.46).

Indicates whether a virtual circuit
is related to non-contention mode
or contention mode of operation.
Indicates whether DRX is used in
the READY state.
Ref. GSM 08.08 (3.2.2.13).
MS Capabilities
Identifies group of recipients for a

message.
A MSs capabilities.
MS Id
Identifies the MS.
MS Id New
Indicates the new TLLI for the

given MS.
Number of Repetitions
Identifies how many times the unit

of data is repeated over the radio
interface.
Ref. GSM 08.08 (3.2.2.12).
Quality of Service
Periodicity
QoS
QoS Allowed
Resource Available
Resource Indication Method
RR Cause
SDU
Status
Total Resource Accessible
Transaction Id
VCIC
Indicates the QoS levels that can

still communicate over Gb.
Ref. GSM 08.08 (3.2.2.4).
Ref. GSM 08.08 (3.2.2.29).
Ref. GSM 08.08 (3.2.2.22).
LLC PDU that is sent between the
SGSN and the MS (or set of
mobiles) in the MT direction or
from one MS to the SGSN (in the
MO direction).
Indicates the completion status of
the requested transaction.
Ref. GSM 08.08 (3.2.2.14).
Identifies the LLC PDU that is
submitted by SGSN for
transmission.
Virtual Circuit Identity Code.
Comments
This can be Channel Id, list of
Channel Ids or a Routing Area Id.
This can identify a cell, or if there are
several radio resources in the cell it
can also identify more detailed
information in the cell.
When DRX is used, then SGSN shall

also provide IMSI to the BSS so that
it can calculate the subgroup.
Modify to include GPRS definitions.
Typically an IMGI.
This can be for example MS
Classmark.
E.g., IMSI, TLLI, or TLLI from old
Routing Area.
This information element is used
when SGSN has reallocated a new
TLLI for a MS and now instructing it
to use the new TLLI for the further
communication. To keep the
(optional) MSs context up to date in
BSS, SGSN must also inform the
new TLLI to the BSS (as BSS is not
able to interpret the LLC PDUs).
Repetition of zero indicates that unit
data is sent only once.
This indicates the requested priority

for the radio interface (e.g., number
of time slots, throughput).

This information is totally transparent
to the BSS.
Value can be OK, Error or Flushed.

The SGSN allocates the id and the
BSS returns that id when transfer is
completed with OK or with error.
Depends on multiplexing protocol.
For Frame Relay this is a DLCI.
Page 59
8.4 Abis Interface
10
When the GPRS MAC and RLC layer functions are positioned remote to the BTS the information between
the Channel Codec Unit (CCU) and the remote GPRS Packet Control Unit (PCU) is transferred in frames
with a fixed length of 320 bits (20 msec). In this specification these frames are denoted PCU Frames
and are an extension to the TRAU frames defined in GSM 08.60. Within these frames both GPRS data
and the GPRS MAC/RLC associated control signals are transferred.
The Abis interface should be the same if the PCU is positioned at the BSC site (option B in the figure
below) or at the SGSN site (option C in the figure below). In option B, the PCU could be implemented as
an adjunct unit to the BSC. In option C, the BSC should be considered as transparent for 16 kbits/s
channels. In configurations B and C the PCU is referred to as being a remote PCU.
The remote PCU is considered a part of the BSC, and the signalling between the BSC and the PCU may
be performed by using BSC internal signals. The inband signalling between the CCU and the PCU
functions, using PCU frames is mandatory when the Abis interface is applied (options B and C in the
figure).
Um
Gb
CCU
CCU
BTS
BSC site
GSN site
PCU
Abis
CCU
BTS
BTS
BSC site
CCU
key:
GSN site
PCU
CCU
CCU
BSC site
GSN site
PCU
circuit switching function (16 or 64 Kbps)
Gb
packet switching function
Figure 36: Remote Packet Control Unit (PCU) Positions
15
The PCU is responsible for the following GPRS MAC and RLC layer functions as defined in GSM 03.64:
20
25
30
LLC layer PDU segmentation into RLC blocks for downlink transmission.
LLC layer PDU reassembly from RLC blocks for uplink transmissions.
PDCH scheduling functions for the uplink and downlink data transfers.
PDCH uplink ARQ functions, including RLC block ack/nak.
PDCH downlink ARQ function, including buffering and retransmission of RLC blocks.
Channel access control functions, e.g., access requests and grants.
Radio channel management functions, e.g., power control, congestion control, radio resource
allocation and release, broadcast control information, etc.
The functions inside the Channel Codec Unit (CCU) are:
Page 60
The channel coding functions, including FEC and interleaving.
Radio channel measurement functions, including received quality level, received signal level and
information related to timing advance measurements.
5
8.4.1 Remote Packet Control Unit
10
When the Packet Control Unit (PCU) is remote to the BTS, the Channel Codec Unit (CCU) in the BTS
may control some of the functions in the remote PCU in the BSC. As well, the PCU may control some of
the functions of the CCU. This remote control is performed by inband signalling carried by the control bits
(C-bits) in each PCU frame.
8.4.2 Resource Allocation
At reception of an ASSIGNMENT REQUEST message, e.g., at channel set-up, when a packet switched
radio channel is required, the BSC provides an appropriate PCU to the circuit(s) to be used between the
BSC and the BTS and sends a CHANNEL ACTIVATION message to the BTS.
15
When receiving a CHANNEL ACTIVATION message, the BTS allocates the appropriate radio resources
and one or more CCUs to be used.
The CCU now starts sending uplink frames with the appropriate Frame Type, Channel Type and the
necessary control information (e.g., received quality level, received signal level and timing advance
measurements).
20
When receiving the first frame, the PCU sets the mode of operation accordingly and starts sending
downlink frames with the Frame Type, Channel Type and the necessary control information (e.g.,
transmit signal level and timing advance information).
8.4.3 Resource Release
25
At release of packet switched resources the connection between the CCU and the PCU is released by the
BTS. The BSC has to indicate that the connection has been released. How this is performed is a BSC
internal matter.
8.4.4 Transfer of Idle Frames
30
A PCU frame shall be transferred between the PCU and the CCU every 20 msec. If no data is received
from the MS (uplink direction) or no data is received from the SGSN side of the interface (downlink
direction), idle frames shall be transferred instead of packet data frames.
9. Information Storage
This section describes information storage structures required for GPRS.
9.1 HLR
35
IMSI is the prime key to the GPRS subscription data stored in the HLR. GPRS subscription data could be
stored within a Multiple Subscriber Profile (MSP). The HLR may hold several MSPs per IMSI.
Consequently, there may be several sets of GPRS subscription data per IMSI. This is illustrated in the
following figure.
Page 61
IMSI
MSP
Profile 1
Password
Basic Services
GPRS
Suppl. Services
BS1
BS2
BS3
PDP1
PDP2
PDP3
SS1
Status
SS1
Status
SS1
Status
SS1
Status
SS1
Status
SS1
Status
SS1
Prov.
SS2
Prov.
Supplementary Service 2
Activation Status
MSP
Profile 2
Password
Basic Services
GPRS
BS4
BS5
BS6
PDP4
PDP5
PDP6
SS1
Status
SS1
Status
SS1
Status
SS1
Status
SS1
Status
SS1
Status
Supplementary Service 2
Activation Status
Figure 37: GPRS Subscription Data within MSPs
As the figure indicates, the GPRS subscription data is at the same level as basic services in the MSP.
Each PDP subscription is seen as a basic service. Supplementary services are provisioned as part of the
overall subscription. Activation of SSs is either at the basic service level (SS1) or at the PDP subscription
level (SS2).
The table below shows the GPRS subscription data contained in the HLR.
Table 8: HLR GPRS Subscription Data
Field
Description
IMSI
IMSI is the main reference key.
SGSN Address
The SS7 address of the SGSN currently serving this MS.
Each IMSI contains one or more of the following PDP contexts:
PDP type, e.g., X.25, IP, PTM-G.
PDP Type
PDP Address
PDP address, e.g., an X.121 address or IMGI.
QoS
The Quality of Service subscribed for this PDP Address, 4 levels.
Dynamic address allowed Specifies whether the MS is allowed to use a dynamic address.
VPLMN address allowed
Specifies whether the MS is allowed to use a dynamic address allocated in
the VPLMN.
SS
Supplementary Services subscribed for this PDP Address.
GGSN Addresses
The IP addresses of the GGSNs providing Gi reference points for this PDP
Address.
10
A PDP context can contain more than one GGSN when PDP Type is a CLNP (e.g., IP), in which case
downlink PDUs can arrive at any of the indicated GGSNs. The SGSN may tunnel uplink connection-less
PDUs to any GGSN offering access to the relevant PDP Type network. Message screening functionality
may limit the selection of GGSNs used for PDU routing.
Page 62
A PDP context can also contain more than one GGSN when PDP Type is a CONP and dynamic
addressing is allowed. In this case, only one GGSN can be used at any time.
9.2 SGSN
SGSN maintains MM context and PDP context information for MSs in STANDBY and READY states. The
table below shows the context fields for one MS.
Table 9: SGSN MM and PDP Contexts
Field
Description
IMSI
State
IDLE, STANDBY or READY state.
VLR Address
The SS7 address of the MSC/VLR currently serving this MS.
TLLI
Temporary Logical Link Identity.
Routing Area
Current routing area.
Cell Identity
Current cell, only valid in READY state.
Security
Authentication and ciphering parameters.
Classmark
MS classmark.
Compression
Data compression parameters, active / not active.
Each MM context contains zero or more of the following PDP contexts:
PDP Type
PDP type, e.g., X.25 or IP.
PDP Address
PDP address, e.g., an X.121 address.
NSAPI
Network layer Service Access Point Identifier.
QoS negotiated
The Quality of Service negotiated for this PDP Address, 4 levels.
TEPIS
Tunnel End Point Identifier in the SGSN.
TEPIG-list
List of Tunnel End Point Identifiers in the GGSNs.
GGSN Addresses
The IP addresses of the GGSNs providing Gi reference points for this PDP
Address.
Charging Data
Information for billing and statistical purposes.
Dynamic address allowed Specifies whether the MS is allowed to use a dynamic address.
VPLMN address allowed
Specifies whether the MS is allowed to use a dynamic address allocated in
the VPLMN.
QoS subscribed
The Quality of Service subscribed for this PDP Address, 4 levels.
SS
Supplementary Services applied to this PDP Address.
Screening Data
The message screening functionality subscribed for this PDP Address.
9.3 GGSN
10
GGSN maintains activated PDP contexts. The table below shows the PDP context fields for one PDP
Address.
Table 10: GGSN PDP Context
Field
PDP Type
PDP Address
Dynamic Address
QoS
TEPIS
TEPIG
SGSN Address
Description
Indicates whether PDP Address is static or dynamic.
Tunnel End Point Identifier SGSN.
Tunnel End Point Identifier GGSN.
The IP address of the SGSN currently serving this MS.
9.4 MS
15
Each GPRS MS maintains context information in IDLE, STANDBY and READY states. The information
may be contained in the SIM, the ME, and the TE. The table below shows the MS context fields.
Page 63
Table 11: MS MM and PDP Contexts
Field
Description
State
IDLE, STANDBY or READY state.
TLLI
Temporary Logical Link Identity.
Routing Area
Current routing area.
Cell Identity
Current cell.
Channel Id
Current physical channel.
Security
Authentication and ciphering parameters.
Classmark
MS classmark.
Compression
Data compression parameters, active / not active.
Each MM context contains zero or more of the following PDP contexts:
PDP Type
PDP Address
Dynamic Address Allowed Specifies whether the MS is allowed to use a dynamic address.
NSAPI
Network layer Service Access Point Identifier.
QoSr
The Quality of Service requested for this PDP Address, 4 levels.
QoSn
9.5 MSC/VLR
The MSC/VLR stores the SGSN address of GPRS-attached MSs that are also IMSI-attached.
Table 12: MSC/VLR Association
5
Field
IMSI
SGSN Address
Description
The SS7 address of the SGSN currently serving this MS.
10. Identities
10.1 IMSI
10
A unique International Mobile Subscriber Identity (IMSI) shall be allocated to each mobile subscriber in
GSM. This is also the case for GPRS-only mobile subscribers, except for anonymous-only access
subscribers. IMSI is defined in GSM 03.03.
10.2 NSAPI and TLLI
The Network layer Service Access Point Identifier (NSAPI) and Temporary Logical Link Identity (TLLI) are
used for network layer routing. A NSAPI / TLLI pair is unambiguous within a routing area.
15
20
On the MS side, NSAPI identifies the PDP-SAP. On the SGSN side, NSAPI identifies the PDP context
associated with a PDP address. Between the MS and SGSN, TLLI unambiguously identifies the logical
link.
For example (shown figuratively below), an X.25 packet is received by the MS from a connected TE at the
X.121 address SAP. The X.25 PDU is encapsulated and NSAPI is initialised to NSAPI-1. TLLI is set to the
MSs TLLI before the encapsulated X.25 packet is passed to the SNDC function.
Page 64
GPRS MS
Gi
GGSN associated with:
X.121 address
X.121 address SAP
X.25 /
X.75
NSAPI-1
TLLI
SGSN
Gi
NSAPI-2
GGSN associated with:

IP address
IP address SAP
IP
Figure 38: Use of NSAPI and TLLI
Within a routing area, there is a one-to-one correspondence between TLLI and IMSI that is only known in
the MS and SGSN. If it is not clear from the context which routing area a TLLI belongs to, then TLLI is
used together with RAI. TLLI provides user identity confidentiality as described in section User Identity
Confidentiality.
10.3 PDP Address
A GPRS subscriber identified by an IMSI, shall have one or more network layer addresses, i.e., PDP
addresses, temporarily and/or permanently associated with it that conforms to the standard addressing
scheme of the respective network layer service used, e.g.:
10
15
an IP version 4 address,
an IP version 6 address, or
an X.121 address.
PDP addresses are activated and deactivated through MM procedures described in section PDP Context
Activation and Deactivation Functions.
10.4 TEPI
A Tunnel End Point Identifier (TEPI) is used by the GPRS Tunnelling protocol between GSNs to identify a
PDP context in a peer GSN. There are two types of TEPIs, where the TEPIS identifies a PDP context in a
SGSN and the TEPIG identifies a PDP context in a GGSN.
20
25
When a MS initiates a PDP Context Activation procedure, the SGSN allocates a TEPIS as an endpoint
identifier to the SGSNs local PDP Context for the PDP address to be activated. The TEPIS is forwarded
to the GGSN and it is used in subsequent tunnelling of user data from GGSN to SGSN to identify the MSs
PDP Context in the SGSN. The GGSN allocates a TEPIG, which is forwarded to the SGSN, and it is used
in subsequent tunnelling of user data from SGSN to GGSN to identify the MSs PDP Context in the
GGSN.
10.5 Routing Area Identity
Routing Area Identity (RAI), defined by an operator, identifies one or several cells. RAI is broadcast as
system information and is used by the MS to determine, when changing cell, if a RA border was crossed.
If that was the case, the MS initiates the RA Update procedure.
30
The location of an MS in STANDBY state is known in the SGSN on a RA level. This means that the MS is
paged in the RA where the MS is located when mobile-terminated traffic arrives in the SGSN.
A Routing Area is a subset of one, and only one, Location Area (LA), meaning that a RA cannot span
more than one LA. A RA is served by only one SGSN.
The following rules apply for the Routing Area Identity:
35
RAC is only unique when presented together with LAI.

CI is only unique when presented together with LAI or RAI.
Page 65
CGI may be presented with or without RAC. PLMNs supporting GPRS shall include RAC in CGI.
LAI = MCC + MNC + LAC

RAI = MCC + MNC + LAC + RAC
CGI = LAI + {RAC} + CI
10.6 Cell Identity
10
Cell Identity (CI) identifies one cell. CI information is broadcast as system information and is used by the
MS to identify the selected cell. A mobile station in READY state, that crosses a cell border, conveys cell
change information to the SGSN. This may be performed as an implicit procedure at the LLC level, where
the CI is added by the BSS.
CI is defined in GSM 03.03.
10.7 GSN Address
15
Each SGSN and GGSN have an IP address, either of type IPv4 or IPv6, for inter-communication over the
GPRS backbone network. Each SGSN also has a SS7 address for communication with, e.g., MSC/VLR
and HLR.
11. Operational Aspects

11.1 Charging
20
Charging information in the GPRS network is collected for each MS by SGSNs and GGSNs that are
serving the MS.
The information that the operator uses to generate a bill to a subscriber is operator-specific. Billing
aspects, e.g., a regular fee for a fixed period, are outside the scope of this specification.
Every GPRS operator collects and processes their own charging information.
25
The SGSN collects charging information for each MS related with the radio network usage while the
GGSN collects charging information for each MS related with the external data network usage. Both
GSNs also collect charging information on usage of the GPRS network resources.
11.1.1 Charging Information
PTP charging information is collected for the GPRS subscriber.
As a minimum, the SGSN shall collect the following charging information:
30
35
usage of the radio interface: the charging information shall describe the amount of data transmitted
in MO and MT directions categorised with QoS and user protocols;
usage of the packet data protocol addresses: the charging information shall describe how long the
MS has used the packet data protocol addresses;
usage of the general GPRS resources: the charging information shall describe the usage of other
GPRS-related resources and the MS's GPRS network activity (e.g., mobility management);
location of MS: HPLMN, VPLMN, plus optional higher-accuracy location information.
40
As a minimum, the GGSN shall collect the following charging information:
45
destination and source: the charging information shall describe the destination and source
addresses with a level of accuracy as defined by the GPRS operator;
usage of the external data networks: the charging information shall describe the amount of data
sent and received to and from the external data network;
Page 66
usage of the packet data protocol addresses: the charging information shall describe how long the
MS has used the PDP addresses;
location of MS: HPLMN, VPLMN, plus optional higher-accuracy location information.
5
11.1.2 Reverse Charging
It shall be possible to provide reverse charging as a subscription option. However, reverse charging may
not be applicable to certain external data network protocols.
12. Interactions with Other GSM Services

10
This section describes the interaction between GPRS and the following other GSM services:
15
Point-to-point Short Message Service (SMS).

Circuit-switched Services.
Supplementary Services.
12.1 Point-to-point Short Message Service

It shall be possible for a GPRS-attached MS of any class (A, B, C) to send and receive short messages
over GPRS radio channels. Class-C MSs shall transfer SMs over GPRS channels. Class-A MSs and
class-B MSs shall transfer SMs over GPRS channels or over existing GSM control channels (if existing
control channels are used, then paging for MT SMS goes through the SGSN).
20
The following two subsections define the operation of mobile-terminated and mobile-originated SMS
routing and transfer over GPRS radio channels.
12.1.1 Mobile-terminated SMS Transfer
The figure and description below explain the steps involved in delivering a SMS to a MS over a GPRS
radio channel.
MS BSS SGSN GGSN MSC/VLR HLR SMS-G SM-SC
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|<----| Message Transfer
|
|
|
|
|
|
|
|
(SMS)
|
|
|
|
|
|<----|
| Send Routing Info For Short Message
|
|
|
|
|
|
|
|
|
|
|
|
|
|---->|
| Send Routing Info For Short Message Ack
|
|
|
|
|
|
|
|
(SGSN Address, MSC Address)
|
|
|<----|-----|-----|-----|
| Forward Short Message
|
|
|
|
|
|
|
|
(SMS)
|<----|---->|
|
|
|
|
| Message Transfer
|
|
|
|
|
|
|
|
(SMS)
|
|
|-----|-----|-----|---->|
| Delivery Report
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|---->| Delivery Report
|
|
|
|
|
|
|
|
35
3
4
5
6
7
1.
The short message service centre determines it shall send a SMS to a MS. SM-SC forwards the
SMS to a SMS gateway MSC.
2.
SMS-GMSC examines the destination MS address, and sends a Send Routing Info For Short
Message message to the relevant HLR.
3.
HLR returns a Send Routing Info For Short Message Ack message to the SMS-GMSC. The Ack
may contain the MSs current SGSN Address, the MSC Address, or both. If the Ack does not
contain a SGSN Address, and if the Ack does contain a MSC Address, then existing GSM SMS
delivery procedures are followed. If the Ack contains a SGSN Address, the SMS transfer proceeds
according to the following events.
NOTE:
40
Figure 39: MT SMS Transfer for Class A, B, and C MSs, Successful
25
30
SMS delivery via the SGSN has priority over SMS delivery via the MSC/VLR.
Page 67
4.
SMS-GMSC forwards the SMS to the SGSN.
5.
SGSN transfers the SMS to the MS via SNDCP and LLC.
6.
SGSN returns a Delivery Report to SMS-GMSC indicating successful delivery of the SMS.
7.
SMS-GMSC returns a Delivery Report to SM-SC indicating successful delivery of the SMS.
12.1.1.1 Unsuccessful Mobile-terminated SMS Transfer

10
The SGSN may not be able to deliver the SMS to the MS. This may happen when the MS is not attached
to GPRS, or when the radio channel conditions are bad.
When the SGSN cannot deliver the SMS to the MS, the SGSN sets the Mobile Station Not Reachable
Flag, and return a Failure Report to the SMS-GMSC. Based on the routing information received from the
HLR, SMS-GMSC does one of the following:
15
If a MSC/VLR is available for the MS, the SMS is forwarded to the MS via MSC/VLR using existing
GSM procedures. A copy of the SMS was buffered in the SMS-GMSC while the SGSN attempted to
deliver the SMS to the MS.
If a MSC/VLR is not available for the MS, SMS-GMSC sends a Set Message Waiting Data
message to the HLR, remove the SMS from its buffers, and return a Failure Report to the SM-SC.
20
The figure below illustrates the case when neither the SGSN nor the MSC is able to deliver the SMS.
MS BSS SGSN GGSN MSC/VLR HLR SMS-G SM-SC
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|<----| Message Transfer
|
|
|
|
|
|
|
|
(SMS)
|
|
|
|
|
|<----|
| Send Routing Info For Short Message
|
|
|
|
|
|
|
|
|
|
|
|
|
|---->|
| Send Routing Info For Short Message Ack
|
|
|
|
|
|
|
|
(SGSN Address, MSC Address)
|
|
|<----|-----|-----|-----|
|
|
|
|
|
|
|
|
(SMS)
|<----|---->|
|
|
|
|
| Message Transfer: Failure
|
|
|
|
|
|
|
|
(SMS)
|
|
|-----|-----|-----|---->|
| Failure Report
|
|
|
|
|
|
|
|
|
|
|
|
|<----|-----|
|
|
|
|
|
|
|
|
(SMS)
|<----|-----|-----|---->|
|
|
| Message Transfer: Failure
|
|
|
|
|
|
|
|
(SMS)
|
|
|
|
|-----|---->|
| Failure Report
|
|
|
|
|
|
|
|
|
|
|
|
|
|<----|
| Set Message Waiting Data
|
|
|
|
|
|
|
|
|
|
|
|
|
|---->|
| Set Message Waiting Data Ack
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|---->| Failure Report
|
|
|
|
|
|
|
|
1
2
3
4
5
6
7
8
9
10
11
12
Figure 40: MT SMS Transfer for Class A, B, and C MSs, Unsuccessful

25
1.
The short message service centre determines it shall send a SMS to a MS. SM-SC forwards the
SMS to a SMS gateway MSC.
2.
SMS-GMSC examines the destination MS address, and sends a Send Routing Info For Short
Message message to the relevant HLR.
3.
HLR returns a Send Routing Info For Short Message Ack message to the SMS-GMSC. The Ack
contains the SS7 address of a SGSN, and also the SS7 address of a MSC.
4.
SMS-GMSC forwards the SMS to the SGSN.
5.
SGSN attempts to transfer the SMS to the MS, but fails.
6.
SGSN sets its Mobile Station Not Reachable Flag, and returns a Failure Report to SMS-GMSC
indicating unsuccessful delivery of the SMS.
30
35
Page 68
7.
SMS-GMSC determines that the MS can alternatively be reached via a MSC/VLR, and forwards the
SMS to the MSC/VLR.
8.
MSC/VLR attempts to transfer the SMS to the MS with existing GSM procedures, but fails.
9.
VLR sets its Mobile Station Not Reachable Flag, and returns a Failure Report to SMS-GMSC
indicating unsuccessful delivery of the SMS.
10.
SMS-GMSC sends a Set Message Waiting Data message to the HLR.
11.
HLR updates its Message Waiting Indication fields and returns a Set Message Waiting Data Ack
message to the SMS-GMSC.
15
12.
SMS-GMSC returns a Failure Report to SM-SC indicating unsuccessful delivery of the SMS.
20
The Mobile Station Not Reachable Flag remains set in the SGSN independently of whether the MSC/VLR
was successful in delivering the SMS or not. This means that the SGSN in certain cases sends a Note MS
Present message to the HLR when a MS attaches to GPRS even if no SMS is waiting. This causes a
small amount of dummy signalling between SGSN and HLR only.
10
12.1.2 Mobile-originated SMS Transfer

The figure and description below explain the steps involved in sending a SMS from a MS over a GPRS
radio channel.
MS BSS SGSN GGSN MSC/VLR HLR SMS-IW SM-SC
|
|
|
|
|
|
|
|
|<----|---->|
|
|
|
|
| Message Transfer
|
|
|
|
|
|
|
|
(SMS)
|
|
|-----|-----|-----|---->|
|
|
|
|
|
|
|
|
(SMS)
|
|
|
|
|
|
|---->| Message Transfer
|
|
|
|
|
|
|
|
(SMS)
|
|
|
|
|
|
|<----| Delivery Report
|
|
|
|
|
|
|
|
|
|
|<----|-----|-----|-----|
| Delivery Report
|
|
|
|
|
|
|
|
|<----|-----|
|
|
|
|
| Delivery Report
|
|
|
|
|
|
|
|
1
2
3
4
5
6
Figure 41: MO SMS Transfer for Class A, B, and C MSs, Successful

25
1.
The MS has a SMS to send, and transfers the SMS to the SGSN via SNDCP and LLC.
2.
SGSN checks the MS subscription data, and determines that the MS is allowed to originate the
SMS. SGSN forwards the SMS to a SMS interworking MSC.
3.
SMS-IWMSC passes the SMS to the addressed SM-SC.
4.
SM-SC returns a Delivery Report to SMS-IWMSC indicating successful delivery of the SMS.
5.
SMS-IWMSC returns a Delivery Report to SGSN indicating successful delivery of the SMS.
6.
SGSN returns a Delivery Report to MS indicating successful delivery of the SMS.
30
35
12.2 Circuit-switched Services

40
The ability for a GPRS user to access circuit-switched services depends on the subscription held and the
MS class. Three GPRS MS classes, denoted class A, class B, and class C, are defined in GSM 02.60.
Interaction between GPRS and circuit-switched services is described in section Interaction Between
SGSN and MSC/VLR.
Page 69
12.3 Supplementary Services
Most of the GSM phase 2 supplementary services are not applicable to GPRS, as described in GSM
02.60 [2]. The SSs that may be applicable are Call Forwarding Unconditional (CFU), Call Forwarding on
Mobile Subscriber Not Reachable (CFNRc), Closed User Group (CUG), Advice of Charge - Information
(AoCI), and Advice of Charge - Charging (AoCC).
CFU and CFNRc are not applicable to PTP IP interworking over the Gi reference point. CFU and CFNRc
are not required for PTP X.25 interworking since the equivalent functions can be provided with the ITU-T
X.25 Call Redirection user facility.
10
CUG is not required for PTP interworking since the equivalent function can be provided with the ITU-T
X.25 Closed User Group user facility. CUG is an integral feature of GPRS PTM services.
AoCI and AoCC are not supported in the first phase of GPRS.
Page 70
Annex A (informative):
Data Transmission Routing Examples
Examples of the PDP PDU routing are given below to clarify the GPRS routing concept. It is assumed
here that the MS has subscribed to a PDP type and a PDP address in the home PLMN and that this PDP
address has been activated.
5
The contexts and the main parameters in the figures indicate which information is used to route the data
to the correct network nodes.
A.1
Data Routing for a MS in its Home PLMN to and from an External PDN
The figure below describes how the MS sends a PDP PDU (data packet) to an external data network and
how PDP PDUs from an external data network are sent to a MS.
10
TLLI and NSAPI identify the PDP context of the MS in the SGSN.
TEPIG identifies the PDP context in the GGSN.
To route MO packets, a SGSN needs to have a mapping from TLLI+NSAPI to GGSN+TEPIG.
To route MT packets, a SGSN needs to have a mapping from TEPIS to TLLI+NSAPI.
MS BSS SGSN
GGSN
external PDN
|
|
|
|
|
|-----|---->|
|
| SNDCP PDU (TLLI, NSAPI, PDP PDU)
|
|
|
|
O Context: TLLI + NSAPI -> GGSN + TEPIG
|
|
|
|
|
|
|
|
|
|--------->|
| GTP PDU (TEPIG, PDP PDU)
|
|
|
|
|
|
O Context: TEPIG -> PDP context (PDP Address)
|
|
|
|
|
|
|
|
|
|
|
|--------->| PDP PDU
|
|
|
|
|
|
|
|
|
|
|
|
|
|<---------| PDP PDU
|
|
|
|
|
|
O Context: PDP Address -> TEPIG -> SGSN + TEPIS
|
|
|
|
|
|
|
|
|
|
|<---------|
| GTP PDU (TEPIS, PDP PDU)
|
|
|
|
O Context: TEPIS -> TLLI + NSAPI + RAI + CellId
|
|
|
|
|
|
|
|<----|-----|
|
|
|
|
|
|
Figure 42: Data Routing in HPLMN to and from an External PDN
15
A.2
Data Routing for a Roaming MS to and from an External PDN
This example is almost the same as the previous one. In this case, the MS has roamed to another PLMN
and the SGSN that is currently serving the MS is in a visited PLMN while the GGSN is in the home PLMN.
20
A mobile-terminated GTP PDU is carried from the GGSN to the SGSN via the home intra-PLMN
backbone network to the inter-PLMN backbone network and finally to the visited intra-PLMN backbone
network.
25
For connection-less protocols (e.g., IP) it is possible to optimise the routing. To route MO packets
via the HPLMN may then not be necessary.
An optimised routing for MO and MT packets is always applicable, when the activated PDP address
is dynamically assigned by the visited PLMN.
Page 71
Visited PLMN
Home PLMN
MS BSS SGSN GGSN PDN GGSN external PDN
|
|
|
|
|
|
|
|-----|---->|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
O Context: TLLI + NSAPI -> GGSN + TEPIG
|
|
|
|
|---------------->|
| GTP PDU (TEPIG, PDP PDU)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
O Context: TEPIG -> PDP context (PDP Address)
|
|
|
|
|
|
|
|
|
|
|---->| PDP PDU
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|<----| PDP PDU
|
|
|
|
|
|
|
|
|
|
O Context: PDP Address -> TEPIG -> SGSN + TEPIS
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|<----------------|
| GTP PDU (TEPIS, PDP PDU)
|
|
|
|
|
|
|
|
|
|
|
O Context: TEPIS -> TLLI + NSAPI + RAI + CellId
|
|
|
|
|
|
|
|
|
|<----|-----|
|
|
|
|
|
|
|
|
|
|
Figure 43: Data Routing for a Roaming MS to and from an External PDN
NOTE:
5
A.3
10
Typically, the GGSN that handles mobile-terminated traffic is in the home PLMN of the
MS, while a GGSN that handles mobile-originated traffic can be in the visited PLMN.
For security or monitoring reasons, the mobile-originated traffic can be forced to be
routed via the GGSN of the home PLMN.
MS-to-MS Data Routing via the Same GGSN
This example is basically the same as described in section Data Routing for a MS in its Home PLMN to
and from an External PDN. When the GGSN receives the GTP PDU and decapsulates the PDP PDU, it
detects that the destination address is also in the GPRS network. Then, the PDP PDU that is sent by one
MS is treated the same way as the PDP PDU that is received from the external data network.
In case of connection-oriented protocols (e.g., X.25) an additional DTE/DCE conversion may need
to be performed in the GGSN.
MS1 BSS1 SGSN1

GGSN
PDN
|
|
|
|
|
|-----|---->|
|
| SNDCP PDU (TLLI1, NSAPI1, PDP PDU)
|
|
|
|
O Context: TLLI1 + NSAPI1 -> GGSN + TEPIG1
|
|
|
|
|
|
|
|
|
|--------->|
| GTP PDU (TEPIG1, PDP PDU)
|
|
|
|
|
|
|
|
O Context: TEPIG1 -> PDP context1 (PDP Address1)
O Context: PDP Address2 -> TEPIG2 -> SGSN2 + TEPIS2
MS2 BSS2 SGSN2
|
|
|
|
|
|
|
|
|
|<---------|
| GTP PDU (TEPIS2, PDP PDU)
|
|
|
|
O Context: TEPIS2 -> TLLI2 + NSAPI2 +RA2 +CellId2
|
|
|
|
|
|
|
|<----|-----|
|
|
|
|
|
|
Figure 44: MS-to-MS Data Routing via the Same GGSN
15
Page 72
A.4
This example is basically the same as described in section MS-to-MS Data Routing via the Same
GGSN, with the difference that the same GGSN is not handling the first MSs outgoing traffic and the
second MSs incoming traffic. In practice, this means that when the first GGSN has extracted the
destination address from the PDP PDU and detected the destination subnetwork, its routing table has a
short-cut to the second GGSN. Instead of routing the PDP PDU via an external data network, it is
possible to route it via the inter-PLMN backbone network.
10
MS-to-MS Data Routing via Different GGSNs
If the first GGSN does not know the short-cut from one operator to another, the PDP PDUs are
transmitted via the external data network. From the first GGSNs point of view, the second mobile
station then resembles a normal fixed network node.
In case of connection-oriented protocols (e.g., X.25) an additional DTE/DCE conversion may need
to be performed in the GGSN.
MS1 BSS1 SGSN1

GGSN1
GGSN2
|
|
|
|
|
|-----|---->|
|
|
|
|
|
|
|
|
|
|
O Context: TLLI1 + NSAPI1 -> GGSN + TEPIG1
|
|
|
|
|
|
|
|
|
|--------->|
| GTP PDU (TEPIG1, PDP PDU)
|
|
|
|
|
|
|
|
|
|
|
O Context: TEPIG1 -> PDP context1 (PDP Address1)
|
|
|
|
|
|
|
|
|
|
|
|--------->| GTP PDU (PDP PDU)
|
|
|
|
|
|
|
|
|
|
O Context: PDP Address2 -> TEPIG2 -> SGSN2 + TEPIS2
|
MS2 BSS2 SGSN2
|
|
|
|
|
|
|
|
|
|<--------------------| GTP PDU (TEPIS2, PDP PDU)
|
|
|
|
|
|
|
|
|
O Context: TEPIS2 -> TLLI2 + NSAPI2 + RA2 + CellId2
|
|
|
|
|
|
|
|<----|-----|
|
|
|
|
|
|
Figure 45: MS-to-MS Data Routing via Different GGSNs
Page 73
Annex B (informative):
Basic Concept Description of Point-to-Point GPRS
Ed. NOTE: The text in this annex has been adopted as draft text for section Main Concepts.
Before the text can be moved to the Main Concepts section, it needs to be expanded
in scope to cover all important aspects of GPRS, including PTM. Furthermore, the text
should be kept simple and avoid the use of terms introduced in the subsequent
detailed parts of GSM 03.60. Improvements to this annex are welcome at any time, but
the Main Concepts section will only be completed as the GPRS stage-2 work comes
to a conclusion.
B.1 Attach
10
When a user attaches to GPRS, a logical link is established between the MS and the SGSN. At this time
the mobile can be said to 'have a call in progress and ciphering processes (for this communications pipe)
are as for circuit-switched calls. This logical link has a MS to SGSN path indicated by logical link identity
(TLLI). Each sub-logical link has its own identity and where it exists a relay function maps data from one
logical link to the next.
15
B.2 Data Exchange
20
Data to be passed to or from the MS is processed by the SNDCP function (where ciphering takes place)
and passed into the LLC layer where it begins its journey towards the radio interface. The LLC layer PDUs
are of the form Header, Information, FCS. The information field contains the user data which may include
a whole or a segmented X.25 call request packet, an X.25 data packet, a TCP session packet etc. The
conversion of the user data is managed by the SNDCP layer.
The LLC layer passes its data to the RLC which discards unnecessary information and segments data
further so as to be compatible with the MAC. The protocol exchange between RLC and MAC is where the
data communications meets radio communications.
25
30
The MAC layer now has data to transmit and can initiate the radio resource processes to obtain a traffic
path for transmission (further radio detail is not shown since it is out of the scope of this document - there
may be addition of FEC and interleaving processes before transmission, as well as common control
channel signalling etc.).
The data is received by the corresponding MAC entity on the far side of the radio traffic path and passed
to the RLC layer. RLC passes the data up to the LLC layer or via the LLC relay which maps the data to the
correct link. The data finally passes out of the LLC layer into the SNDCP where the user data is fully
restored and passed onto the next stage of the process (e.g., higher layers in the mobile or tunnelled to
the appropriate GGSN in the network).
B.3 Corruption on the Radio Link
35
When a RLC PDU is detected to be corrupt the RLC layer requests a retransmission by selective
rejection. A buffer is provided within the RLC layer and flow control conditions can be exchanged between
the RLC layer and the LLC layer.
B.4 Corruption on the LLC Link
40
When a LLC PDU is detected to be corrupt the LLC layer requests a retransmission by selective rejection.
A buffer is provided within the LLC layer and flow control conditions can be exchanged between the LLC
layer and the next higher layer.
B.5 Location Update
There are two cases, intra- and inter-SGSN cell reselection of which the MS is not aware, and a number
of BTS update cases.
Page 74
B.5.1 Intra-SGSN Location Update
B.5.1.1 Intra-BTS
B.5.1.2 Inter-BTS (Intra BSC)
In this case only the BTS changes and the lower layer logical links reorganise themselves to as to enable
continued communications. Updates to the mapping relationship between each sub-logical link are made,
and data flow in transit through the pipe will be interrupted while the links re-establish themselves. This
may also mean that flow control towards the originating entity can occur.
B.5.2 Inter-SGSN Location Update
10
In this case the BSS changes and the SGSN changes. This requires a revision to the lower layer logical
links and to the LLC so as to enable continued communications. Updates to the mapping relationship
between each sub-logical link are made, and data flow in transit through the pipe will be interrupted while
the links re-establish themselves. This may also mean that flow control towards the originating entity can
occur.
The SGSN now updates the communications path with the appropriate GGSN.
15
B.6 Charging Data Collection

Segment-based charging data collection records are created by the SGSN. All data processing through
the communications pipe adds towards the segments and records. Both uplink and down link records are
maintained while a pipe exists.
B.7 The Communications Pipe
Communications Pipe
MS
SGSN
LLC
20
30
Tunnel
Key characteristics:
25
GGSN
LLC is established upon GPRS attach.

The pipe is established at PDP context activation.
The pipe is build out of several logical links.
Logical links can be lost and re-established for example when change of SGSN or cell takes place,
both when moving to a new cell, and when moving out of and in to coverage.
There is one LLC per mobile with various tunnels to GGSN.
Ciphering key is obtained and ciphering is carried out on the pipe over the LLC link.
The pipe is unaware of the lower layer links which may perform many more functions and optimise
the user data for each link.
Charging data collection records are created by the SGSN and indicate the number of 'segments' of
data transferred in each direction.
Page 75
Annex C (informative):
Figures
Figure 1: Encapsulation..............................................................................................................................7
Figure 2: GPRS Access Interfaces and Reference Points.......................................................................8
Figure 3: Overview of the GPRS Logical Architecture ..........................................................................12
5
Figure 4: Intra- and Inter-PLMN Backbone Networks ............................................................................13

Figure 5: Transmission Plane ..................................................................................................................15
Figure 6: Signalling Plane MS - SGSN.....................................................................................................16
Figure 7: Signalling Plane SGSN - HLR...................................................................................................16
Figure 8: Signalling Plane SGSN - MSC/VLR..........................................................................................17
10
Figure 9: Signalling Plane SGSN - SMS-GMSC and SGSN - SMS-IWMSC...........................................17

Figure 10: Signalling Plane GSN - GSN...................................................................................................17
Figure 11: Functional Mobility Management State Model .....................................................................20
Figure 12: CS Paging Procedure..............................................................................................................23
Figure 13: Suspend and Resume Procedure ..........................................................................................24
15
Figure 14: Combined IMSI / GPRS Attach Procedure ............................................................................27

Figure 15: Combined GPRS / IMSI Detach Procedure ...........................................................................30
Figure 16: Authentication Procedure ......................................................................................................31
Figure 17: Scope of GPRS Ciphering ......................................................................................................31
Figure 18: Identity Check Procedure .......................................................................................................32
20
Figure 19: Intra SGSN Routing Area Update Procedure........................................................................33

Figure 20: Inter SGSN Routing Update Procedure.................................................................................34
Figure 21: Combined RA / LA Update in the Case of Intra SGSN RA Update Procedure...................36
Figure 22: Combined RA / LA Update in the Case of Inter SGSN RA Update Procedure...................38
Figure 23: PDP Context Activation Procedure .......................................................................................41
25
Figure 24: PDP Context Deactivation Procedure ...................................................................................42

Figure 25: GPRS Paging Procedure ........................................................................................................44
Figure 26: Functional PDP State Model ..................................................................................................45
Figure 27: Multiplexing of Network Protocols ........................................................................................48
Figure 28: Sequential Invocation of SNDC Functionality ......................................................................50
30
Figure 29: Gb Interface Configurations...................................................................................................51
Page 76
Figure 30: Virtual Circuits Between NSS and BSS ................................................................................ 53
Figure 31: Establishing a Virtual Circuit Between the BTS and SGSN ............................................... 53
Figure 32: SGSN-originated Flow Control.............................................................................................. 54
Figure 33: BSS-originated Flow Control................................................................................................. 54
5
Figure 34: SGSN-originated Virtual Circuit Release.............................................................................. 54

Figure 35: BSS-originated Virtual Circuit Release................................................................................. 54
Figure 36: Remote Packet Control Unit (PCU) Positions...................................................................... 59
Figure 37: GPRS Subscription Data within MSPs ................................................................................. 61
Figure 38: Use of NSAPI and TLLI........................................................................................................... 64
10
Figure 39: MT SMS Transfer for Class A, B, and C MSs, Successful .................................................. 66
Figure 40: MT SMS Transfer for Class A, B, and C MSs, Unsuccessful.............................................. 67
Figure 41: MO SMS Transfer for Class A, B, and C MSs, Successful.................................................. 68
Figure 42: Data Routing in HPLMN to and from an External PDN ....................................................... 70
Figure 43: Data Routing for a Roaming MS to and from an External PDN.......................................... 71
15
Figure 44: MS-to-MS Data Routing via the Same GGSN....................................................................... 71

Figure 45: MS-to-MS Data Routing via Different GGSNs ...................................................................... 72
Page 77
Annex D (informative):
Tables
Table 1: Mapping of Functions to Logical Architecture ........................................................................14

Table 2: LLC Service Primitives ...............................................................................................................48
Table 3: Configuration Independent and Dependent Signalling ..........................................................52
5
Table 4: BSSGP Messages .......................................................................................................................52

Table 5: MS-related BSSGP Messages....................................................................................................55
Table 6: BSSGP General Messages.........................................................................................................56
Table 7: BSSGP Information Elements ...................................................................................................58
Table 8: HLR GPRS Subscription Data ...................................................................................................61
10
Table 9: SGSN MM and PDP Contexts ....................................................................................................62

Table 10: GGSN PDP Context...................................................................................................................62
Table 11: MS MM and PDP Contexts .......................................................................................................63
Table 12: MSC/VLR Association ..............................................................................................................63
Page 78
History
Document History
Date
Status
Comments
July 13, 1995
Version 0.9.0
P. Gilchrist and H.P. Naper (Motorola) are new

rapporteurs. Significant changes from v0.8.0:
- Technical changes according to Ipswich meeting
- Restructuring of document
- Upgrade to Word for Windows 6.0
- Compatibility with ETSI WW6 template
September 21,
1995
Version 0.10.0
H.P. Naper (Motorola):

Significant changes from v0.9.0:
- Included adopted changes from TDocs:
- SMG3 95G056: Gb Interface
- SMG3 95G053: Routing Areas
- SMG3 95G048 & 95G078: GR and LOGON
- SMG3 95G049: IDLE/STANDBY signalling
- Numerous editorial improvements (these are not
revision marked)
October 26, 1995
Version 0.11.0

Changes from v0.10.0:
- SMG3 95G084: LOGON functionality, including
cross-updating section 6.5.6
- SMG3 95G088: Descr. of transmission planes
- SMG3 95G094: Various editorial changes
- Added LOGOFF while ACTIVE, sections 6.1 + 6.2
- Included text from 04.60 v0.3.1:
- Section 6.8 moved to 03.60 section 6.6.2
- Section 7 merged into sections 6.5.4 and 6.5.5
January 18, 1996
Version 0.12.0

- Review and editorial improvements by ETSI
- SMG3 96G104: Discarding PDUs in the GGSN
- SMG3 96G117: Routing, Encapsulation and
Tunnelling
- SMG3 96G129: Added RLC, changed LLC
- Deleted the three backbone cases
February 23, 1996
Version 0.13.0

- SMG3 96G139: Frame Relay on Gb interface
- SMG3 96G140: Multiple Subscriber Profile
- SMG3 96G141: Attach and Routing Updates
- SMG3 96G154: Protocol Structure
- The SGSNs shall not need to know tunnelled PDP
April 17, 1996
Proposed version 0.14.0

SMG3 GPRS-ad-hoc had given the GPRS Project
Team the mandate to improve GSM 03.60 in terms
of restructuring the document, deleting redundant
text, and removing ambiguities. The proposed
changes are described in an accompanying cover
letter.
Page 79
April 19, 1996
Version 0.15.0
H.P. Naper:
Changes from proposed v0.14.0:
- SMG3 96G191: MSP and GPRS Profiles
- SMG3 96G204: Basic concept description...
- Other changes adopted by SMG3 GPRS meeting
- Updated terms related to LLC and SNDC
June 19, 1996
Version 0.16.0
H.P.Naper:
- SMG3 96G210: MM States and PDP States
- SMG3 96G227: GPRS Cipher Algorithm
- Added references to 04.60 and PTM-M stage-2
- Other changes adopted by SMG3 GPRS meeting
August 21, 1996
Version 0.17.0
H.P.Naper:
- SMG3 96G277: Examples for data routing
- SMG3 96G283: MM and PDP States
- SMG3 96G285: GPRS Packet Control Unit
- Deleted mention of CLNP interworking
- Updated cover page, added GSM logo
October 16, 1996
Version 0.18.0
H.P.Naper:
- SMG3 96G294: TCP/IP Header Compression
- SMG3 96G303: Abnormal MM Cases
- SMG3 96G312: Transmission Protocol Stacks
- SMG3 96G315: SMS Interworking with GPRS
- SMG3 96G321: BSSGP Messages
- SMG3 96G327: Mobility Management
- SMG3 96G328: Channel Streams
- SMG3 96G332: MM States
- Deleted implicit GPRS Activation
December 2, 1996
H.P.Naper:
Numerous editorial and technical improvements as
detailed in TDoc SMG3 GPRS 96G343
December 4, 1996
Version 0.20.0
H.P.Naper:
- Changes agreed during v0.18.0 review:
- Paging response is PDU transmission
- Clarification of GPRS Detach in IDLE state
- Changes agreed during pv0.19.0 review:
- Added EIR to logical architecture figure
- Added Gd interface signalling plane stack
- MM to IDLE moves PDP state to INACTIVE
- Compression in SNDCP is per QoS class
- Added MSC address to SGSN MM context
- Updated RA and Cell Id definitions in Identities
- SMG3 96G346: Gb Interface CR
- SMG3 96G354: Dynamic PDP Addresses
- SMG3 96G369: Periodic RA and LA Update
- SMG3 96G384: Gb Interface CR, Part 2
- SMG3 96G385: CS Paging and GPRS Paging
- Cancel Location removes MM and PDP contexts
Page 80
January 23, 1997
H.P.Naper:
- Changes that are not revision marked:
- Moved Routing Example section 8.5 to Annex A
- Removed R and Gi diagram section 8.6
- SMG3 97G007: Cipher Mode Setting
- SMG3 97G011: Maximum GPRS N-PDU Size
- SMG3 97G013: Transmission (SNDCP)
- SMG3 97G017: Intra- and Inter-PLMN Network
- SMG3 97G022: PTP Paging over GPRS
- SMG3 97G023: CR with editorial changes
- SMG3 97G027: Routing and Encapsulation
- SMG3 97G034: Charging
- SMG3 97G037: FFS Resolutions
- SMG3 97G041: Message Screening
- SMG3 97G046: Signalling Plane SGSN-MSC
- SMG3 97G048: Anonymous Access
- SMG3 97G049: Routing Area Identity
- SMG3 97G051: TLLI
- SMG3 97G055: GPRS Backbone, Part 2
- Scope is first phase of GPRS, PTP services
- Gb interface link layer is Frame Relay
January 31, 1997
Version 1.0.0
H.P.Naper:
Reviewed by SMG3.
Sent to SMG#21 for information.
Rapporteurs for GSM 03.60 are:

Hans Petter Naper (primary)
Motorola Wireless Data Group
Phone: +47 22 90 92 23
Fax:
+47 22 30 13 16
Email: naperhp@euro.csg.mot.com
Philip Gilchrist
Motorola Inc.
Phone: +49 69 55 23 43
Fax:
+49 69 55 13 47
Email: apc001c@email.mot.com
This document is written in Microsoft Word version 6.0c.

P 97 076

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

P 97 076

Hochgeladen von

Copyright:

Verfügbare Formate

ETSI TC SMG

TDoc SMG 76/97

Proposed agenda item: 6.4

Presented for: Information

Source: ETSI TC-SMG

Digital cellular telecommunications system (Phase 2+);

This European Telecommunication Standard (ETS) incorporates, by dated or undated reference,

CCITT Recommendations I.130 (1988): General modelling methods - Method

GSM 02.60: Digital cellular telecommunications system (Phase 2+); General

GSM 03.64: Digital cellular telecommunications system; Overall description of

GSM 03.61: Digital cellular telecommunications system (Phase 2+); General

GSM 01.04: Digital cellular

GSM 04.65: Digital cellular telecommunications system (Phase 2+); General

GSM 04.64: Digital cellular telecommunications system (Phase 2+), General

GSM 09.60: Digital cellular telecommunications system (Phase 2+), General

GSM 03.62: Digital cellular telecommunications system (Phase 2+); General

3. Definitions and Abbreviations

ISDN reference point between TE and MT.

GSM PLMN Supporting GPRS

GPRS PDU (header info,

GPRS PDU (header info,

Routing & Transport of GPRS PDU Through PLMN

5. General GPRS Architecture and Transmission Mechanism

5.2.2 Internet (IP) Interworking

Network Access Control Functions.

Packet Routing and Transfer Functions.

5.3.1 Network Access Control Functions

5.3.1.3 Admission Control Function

5.3.1.4 Message Screening Function

5.3.1.5 Packet Terminal Adaptation Function

5.3.2.3 Address Translation and Mapping Function

Refer to GSM 03.64 for further information.

Provide medium access control over radio channels.

5.3.5.4 Path Management Function

5.4.1 GPRS Support Nodes

Figure 4: Intra- and Inter-PLMN Backbone Networks

Packet Routing & Transfer:

Logical Link Management:

Radio Resource Management:

Figure 5: Transmission Plane

Subnetwork Dependent Convergence Protocol (SNDCP): This transmission functionality maps

GSM RF: As defined in GSM 05 series.

controlling the assignment of network resources to meet changing user demands;

providing supplementary services.

The following signalling planes are used in GPRS:

5.6.2.2 SGSN - HLR

Figure 7: Signalling Plane SGSN - HLR

5.6.2.3 SGSN - MSC/VLR

Figure 8: Signalling Plane SGSN - MSC/VLR

5.6.2.4 SGSN - SMS-GMSC or SMS-IWMSC

Figure 9: Signalling Plane SGSN - SMS-GMSC and SGSN - SMS-IWMSC

5.6.2.5 GSN - GSN

Figure 10: Signalling Plane GSN - GSN

6.1 Mobility Management Functionality

STANDBY timer expiry

READY timer expiry

READY timer expiry

MM State Model of SGSN

Figure 11: Functional Mobility Management State Model

This figure describes the following state transitions:

Moving from STANDBY to READY:

PDU reception: The SGSN receives a PDU from the MS.

Moving from READY to STANDBY: