GPRS Fundamentals

GPRS Fundamentals
For internal use only

1
Nokia Siemens Networks
GPRS Fundamentals / Satyajeet Panda / 04th FEB13
Agenda
GPRS architecture
GMM attach call flow
PDP CONTEXT ACTIVATION call flow
Interfaces and protocols

2
Presentation / Author / Date
GPRS interfaces

3
GPRS Fundamentals / Satyajeet Panda / 04th FEB13
Serving GPRS Support Node (SGSN)
Protocol conversion (for example IP to FR)

Ciphering of GPRS data between the MS and SGSN
Data compression is used to minimise the size of transmitted data units
Authentication of GPRS users
Mobility management as the subscriber moves from one area to another,
and possibly one SGSN to another
Routing of data to the relevant GGSN when a connection to an external
network is required
Interaction with the NSS (that is, MSC/VLR, HLR, EIR) via the SS7
network in order to retrieve subscription information
Collection of charging data pertaining to the use of GPRS users
Traffic statistics collections for network management purposes.

4
Gateway GPRS Support Node (GGSN)

Routing mobile-destined packets coming from external networks to the
relevant SGSN
Routing packets originating from a mobile to the correct external
network
Interfaces to external IP networks and deals with security issues
Collects charging data and traffic statistics
Allocates dynamic or static IP addresses to mobiles either by itself or
with the help of a DHCP or a RADIUS server
Involved in the establishment of tunnels with the SGSN and with other
external networks and VPN.

5
GMM ATTACH FUNCTION

6
GMM ATTACH FUNCTION

7
GMM ATTACH FUNCTION

1. In Gb mode, the MS initiates the attach procedure by the transmission of an
Attach Request (IMSI or PTMSI and old RAI, Classmark, Attach Type, DRX
Parameters, old PTMSI Signature) message to the SGSN. IMSI shall be
included if the MS does not have a valid PTMSI available. If the MS has a valid
PTMSI, then PTMSI and the old RAI associated with PTMSI shall be
included.
Classmark contains the MS's GPRS multislot capabilities and supported GPRS
ciphering algorithms .
Attach Type indicates which type of attach is to be performed, i.e. GPRS attach
only, GPRS Attach while already IMSI attached, or combined GPRS / IMSI attach.
DRX Parameters indicates whether the MS uses discontinuous reception or not.
If the MS uses PTMSI for identifying itself and if it has also stored its old
PTMSI Signature, then the MS shall include the old PTMSI Signature in the
Attach Request message.

8
GMM ATTACH FUNCTION

2. If the MS identifies itself with PTMSI and the SGSN has changed since detach, the new
SGSN sends an Identification Request (PTMSI, old RAI, old PTMSI Signature) to the old
SGSN to request the IMSI.
The new SGSN derives the old SGSN from the old RAI. The old SGSN responds with
Identification Response (IMSI, Authentication Triplets or Authentication Quintets). If the MS
is not known in the old SGSN, the old SGSN responds with an appropriate error cause. The
old SGSN also validates the old PTMSI Signature and responds with an appropriate error
cause if it does not match the value stored in the old SGSN.
3. If the MS is unknown in both the old and new SGSN, the SGSN sends an Identity Request
(Identity Type = IMSI) to the MS. The MS responds with Identity Response (IMSI).
4. If no MM context for the MS exists anywhere in the network, then authentication is
mandatory. The essential authentication triplets( Kc, RAND, SRES) are generated in SGSN
from Ki, RAND.
5. The equipment checking functions are carried out by EIR using IMEI as the key parameter.
Equipment checking is optional.
6. If there are active PDP contexts in the new SGSN for this particular MS (i.e. the MS reattaches to the same SGSN without having properly detached before), the new SGSN
deletes these PDP contexts by sending Delete PDP Context Request (TEID) messages to
the GGSNs involved. The GGSNs acknowledge with Delete PDP Context Response (TEID)
messages.

9
GMM ATTACH FUNCTION

7. If the SGSN number has changed since the GPRS detach, or if it is the very first attach,
then the SGSN informs the HLR:
a) The SGSN sends an Update Location (SGSN Number, SGSN Address, IMSI) to the HLR.
b) The HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with
Cancellation Type set to Update Procedure.
c) The old SGSN acknowledges with Cancel Location Ack (IMSI). If there are any ongoing
procedures for that MS, the old SGSN shall wait until these procedures are finished before
removing the MM and PDP contexts.
d) If there are active PDP contexts in the old SGSN for this particular MS, the old SGSN
deletes these PDP contexts by sending Delete PDP Context Request (TEID) messages to
the GGSNs involved.
e) The GGSNs acknowledge with Delete PDP Context Response (TEID) messages.
f) The HLR sends Insert Subscriber Data (IMSI, GPRS Subscription Data) to the new SGSN.
g) The new SGSN validates the MS's presence in the (new) RA. If all checks are successful
then the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data
Ack (IMSI) message to the HLR.
h) 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. If the Update Location is rejected by the HLR, the SGSN rejects the Attach
Request from the MS with an appropriate cause.

10
GMM ATTACH FUNCTION

8. If Attach Type in step 1 indicated GPRS Attach while already IMSI attached, or combined
GPRS / IMSI attached, then the VLR shall be updated if the Gs interface is installed. The
SGSN starts the location update procedure towards the new MSC/VLR upon receipt of the
first Insert Subscriber Data message from the HLR in step 6d). This operation marks the MS
as GPRS-attached in the VLR.
9. The SGSN selects Radio Priority SMS, and sends an Attach Accept (PTMSI, VLR TMSI,
PTMSI Signature, Radio Priority SMS) message to the MS. PTMSI is included if the SGSN
allocates a new PTMSI.
10. If PTMSI or VLR TMSI was changed, the MS acknowledges the received TMSI(s) by
returning an Attach Complete message to the SGSN.
11. If VLR TMSI was changed, the SGSN confirms the VLR TMSI re-allocation by sending a
TMSI Reallocation Complete message to the VLR.

11
GPRS transmission plane protocols

12

-
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 ciphered 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.
Relay: In the BSS, this function relays LLC PDUs between the Um and Gb interfaces. In the
SGSN, this function relays PDP PDUs between the Gb and Gn interfaces.
Base Station System GPRS Protocol (BSSGP): This layer conveys routeing- and QoSrelated information between the BSS and the SGSN. BSSGP does not perform error
correction.
Network Service (NS): This layer transports BSSGP PDUs. NS is based on the Frame Relay
connection between the BSS and the SGSN, and may - multi-hop and traverse a network of
Frame Relay switching nodes.
RLC/MAC: This layer contains two functions: The Radio Link Control function provides a
radio-solution-dependent reliable link. The Medium Access Control function controls the
access signalling (request and grant) procedures for the radio channel, and the mapping of
LLC frames onto the GSM physical channel.

13

The physical layer can be divided into the Radio Frequency (RF) layer and the
Physical Link layer.
The Radio Frequency (RF) is the GSM physical radio layer responsible for:
The carrier frequency characteristics and GSM radio channel structures
The radio modulation scheme used for the data
The radio transmitter and receiver characteristics as well as performance
requirements.
The Physical Link layer supports multiple MSs sharing a single physical channel
and provides communication between the MSs and the network. Network
controlled handovers are not used in the GPRS service. Instead, routing area
updates and cell updates are used.
The Physical Link layer is responsible for:
Forward Error Correction (FEC) coding, allowing the detection and correction of
transmitted code words and the indication of uncorrectable code words.
The interleaving of one RLC Radio Block over four bursts in consecutive TDMA
frames.

14
What Happens when a Mobile is switched on

15

Medium Access Control (MAC)
The Medium Access Control (MAC) protocol handles the channel allocation and
the multiplexing, that is, the use of physical layer functions. The RLC and the MAC
together form the OSI Layer 2 protocol for the Um interface.
The GPRS MAC function is responsible for:
Providing efficient multiplexing of data and control signalling on both the uplink
and downlink. This process is controlled by the network. On the downlink,
multiplexing is controlled by a scheduling mechanism. On the uplink, multiplexing
is controlled by medium allocation to individual.
Mobile originated channel access, contention resolution between channel access
attempts, including collision detection and recovery.
Mobile terminated channel access, scheduling of access attempts, including
queuing of packet accesses.
Priority handling.

16

Radio Link Control (RLC)
The Radio Link Control (RLC) protocol offers a reliable radio link to the upper
layers. Two modes of operation of the RLC layer are defined for information
transfer: unacknowledged and acknowledged. The RLC layer can support both
modes simultaneously.
The RLC function is responsible for:
Providing transfer of Logical Link Control layer PDUs (LLC-PDU) between the LLC
layer and the MAC function.
Segmentation and reassembly of LLC-PDUs into RLC Data Blocks.
Backward Error Correction (BEC) procedures enabling the selective
retransmission of incorrect code words. This process is generally known as
Automatic Request for Retransmission (ARQ).
Note
The Block Check Sequence for error detection is provided by the Physical Link

17

Logical Link Control (LLC)
The Logical Link Control (LLC) layer offers a secure and reliable logical link
between the MS and the SGSN for upper layer protocols, and is independent of
the lower layers.
The LLC conveys signalling, SMS, and Subnetwork Dependent Convergence
Protocol (SNDCP) packets. SNDCP exists between the MS and the SGSN and
provides a mapping and compression function between the network layer (IP or
X.25 packets) and the lower layers. It also performs segmentation, reassembly,
and multiplexing.
Two modes of operation of the LLC layer are defined for information transfer:
unacknowledged and acknowledged. The LLC layer can support both modes
simultaneously.

18
Segmentation of LLC-PDUs into RLC data blocks

19

The network layer protocols for signalling, SMS, and user data are
multiplexed
to the lower layers in the following way:
NSAPI is the Network layer Service Access Point Identifier, which is
used to identify the PDP context at the SNDCP level.
SAPI is the Service Access Point Identifier, which is used to identify
the points where the LLC provides a service to a higher layer. SAPIs have
different priorities.
TLLI is the Temporary Logical Link Identity, which unambiguously
identifies the logical link between the MS and SGSN. TLLI is used for
addressing at the LLC layer.

20

21

SNDCP (Subnetwork Dependent Convergence Protocol)
Network layer protocols are intended to be capable of operating over a wide
variety of subnetworks and data links. GPRS supports several network layer
protocols providing protocol transparency for the users of the service.
To enable the introduction of new network layer protocols to be transferred over
GPRS without any changes to GPRS, all functions related to the transfer of
Network layer Protocol Data Units (N-PDUs) are carried out in a transparent way
by the GPRS network. This is one of the requirements of SNDCP.
Another requirement of the SNDCP is to provide functions that help to improve
channel efficiency. This is achieved by means of compression techniques.

22

23
Encapsulation Between SGSN and MS in A/Gb

mode
Between an SGSN and an MS in A/Gb mode, 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 derived from the PTMSI. An NSAPI is
assigned when the MS initiates the PDP Context Activation
function.

24

Relay Function
The relay function of a network node transfers the PDP PDUs received from the
incoming link to the appropriate outgoing link. The PDP PDUs are discarded when
buffering is longer than their maximum holding time. This maximum holding time is
implementation dependent and can be influenced by the PDP type, the QoS of the
PDP PDU, the resource load status, and by buffer conditions. The discarding
protects resources from useless transfer attempts, especially the radio resource.
Impacts on user protocol operation by too short holding time shall be avoided.
In A/Gb mode, the SGSN and GGSN relay functions add sequence numbers to
PDP PDUs received from SNDCP and from the Gi reference point, respectively.

25

Network Service Entity
A network service entity (NSE) is composed of a group of NS-VCs; it provides a
communication service to the NS user peer entities (SGSN or BSS). A network service entity
identifier (NSEI) identifies each NSE that has end-to-end significance across the Gb
interface. The NSE at each side of the Gb interface manages the traffic from or to a group of
cells.
One SGSN can be linked to several BSSs. The NSE and NSEI concept can be used to
identify the different BSSs connected to the same SGSN. Each BSS is identified by an NSEI
on the SGSN side. A group of NS-VCs is defined within the NSE identified by the NSEI to
communicate with the BSS.
One NSE and the group of NS-VCs that it integrates are defined by the network operator
through O&M means. The interest in having several NS-VCs within one NSE is to distribute
the traffic from all the cells belonging to this NSE. In case of a problem on one NS-VC, the
traffic is not interrupted and is transferred over the other links.

26

BSSGP Virtual Connection
BSSGP virtual connections (BVCs) are end-to-end virtual connections between the BSS and
the SGSN at BSSGP layer. A BVC is identified by a BVCI that has an end-to-end
significance across the Gb interface. An NSE is associated with a set of BVCs that are
dynamically mapped onto its corresponding NS-VCs.
The main functions for the BSSGP protocol are to:

Provide a connectionless link between the SGSN and the BSS
Transfer data in an unconfirmed way between the SGSN and the BSS
Provide for bi-directional control of the data flow between the SGSN and
the BSS
Handle paging requests from the SGSN to the BSS
Give support for deleting old messages in the BSS, for example when an
MS changes BSSs
Support multiple layer 2 links between the SGSN and the BSS.

27
Overview of the GPRS Logical Architecture

28
User Plane with UTRAN

Application
E.g., IP ,
PPP
E.g., IP ,
PPP
Relay
Relay
PDCP
PDCP
GTP-U
GTP-U
GTP-U
GTP-U
RLC
RLC
UDP/IP
UDP/IP
UDP/IP
UDP/IP
MAC
MAC
L2
L2
L2
L2
L1
L1
L1
L1
L1
L1
Uu
MS
29
Iu-PS
UTRAN
Gn
3G-SGSN
Gi
3G-GGSN
Control Plane MS - SGSN in Iu mode

GMM /
SM / SMS
GMM /
SM / SMS
Relay
RRC
RANAP
RANAP
SCCP
SCCP
Signalling
Bearer
Signalling
Bearer
L1
L1
RRC
RLC
RLC
MAC
MAC
L1
L1
Uu
MS
30
L2
Iu-Ps
RNS
L2
SGSN
AUTHENTICATION IN GPRS

31
Control Plane SGSN HLR
MAP
MAP
TCAP
TCAP
SCCP
SCCP
Signalling
Bearer
Signalling
Bearer
SGSN
32
Gr
HLR
Control Plane SGSN MSC/VLR
BSSAP+
BSSAP+
SCCP
SCCP
Signalling
bearer
Signalling
bearer
Gs
SGSN
33
MSC/VLR
Control Plane SGSN EIR
MAP
MAP
TCAP
TCAP
SCCP
SCCP
Signalling
bearer
Signalling
bearer
Gf
SGSN
34
EIR
GPRS Traffic Management - Mobility Management
Implicit detach
or cancel
location
IDLE
GPRS Attach
GPRS Detach
OR
Cancel Location
READY
READY timer expiry
OR
Force to standby
OR
Abnormal RLC
condition
STANDBY
35
PDU reception

The MS is detached from GPRS either explicitly or implicitly:
Explicit detach: The network or the MS explicitly requests
detach specifying the cause for it
Implicit detach: The network detaches the MS after the mobile
reachable timer expired or after an irrecoverable radio error
causes disconnection of the logical link
After a successful detach:
MM context and PDP context in PAPU are removed;
P-TMSI - IMSI association is not removed from PAPU;
otherwise the data from SMMU is removed when "Detached subscriber
storage time" timer expires. Also the IMSI-P-TMSI association from
PAPU is removed and a "Purge" message is sent to HLR.

36

Mobility management states:
Idle State
Ready State
Standby State
Ready State
Idle State
Standby State

37
Mobility Management States (A/Gb mode)

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

38

STANDBY State
In STANDBY state, the subscriber is attached to GPRS mobility management.
Pages for data or signalling information transfers may be received. Data reception and
transmission are not possible in this state.
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 in the same RA. 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 can be transmitted or received for this PDP context.
The SGSN may have to send data or signalling information to an MS in STANDBY state.The MM
state in the MS is changed to READY when the MS responds to the page, and in the SGSN when
the page response is received. Also, the MM state in the MS is changed to READY when data or
signalling information is sent from the MS and, accordingly, the MM state in the SGSN is changed
to READY when data or signalling information is received from the MS.
The MS or the network may initiate the GPRS Detach procedure to move to the IDLE state. After
expiry of the mobile reachable timer the SGSN may perform an implicit detach in order to return
the MM contexts in the SGSN to IDLE state. The MM and PDP contexts may then be deleted.

39

READY State
In READY state, the SGSN MM context corresponds to the STANDBY MM
context extended by location information for the subscriber on the cell level. The
MS performs mobility management procedures to provide the network with the
actual selected cell.
An identifier of the cell, the Cell Global Identity including RAC and LAC, is
included in the BSSGP header of the data packet from the MS.
The MS may send and receive PDP PDUs in this state. The network initiates no
GPRS pages for an MS in READY state. Pages for other services may be done
via the SGSN. The SGSN transfers downlink data to the BSS responsible for the
subscriber's actual GPRS cell.
The MS may activate or deactivate PDP contexts while in READY state.
Regardless if a radio resource is allocated to the subscriber or not, the MM
context remains in the READY state even when there is no data being
communicated. A timer supervises the READY state. An MM context moves from
READY state to STANDBY state when the READY timer expires. In order to move
from READY state to IDLE state, the MS initiates the GPRS Detach procedure.

40
Functional PDP State Model

41

INACTIVE State
The INACTIVE state characterizes the data service for a certain PDP address of
the subscriber as not activated. The PDP context contains no routing or mapping
information to process PDP PDUs related to that PDP address. No data can be
transferred. A changing location of a subscriber causes no update for the PDP
context in INACTIVE state even if the subscriber is GPRS-attached.
The MS initiates the movement from INACTIVE to ACTIVE state by initiating the
PDP Context Activation procedure.

42

ACTIVE State
In ACTIVE state, the PDP context for the PDP address in use is activated
in the MS, SGSN and GGSN. The PDP context contains mapping and
routing information for transferring PDP PDUs for that particular PDP
address between the MS and the GGSN. The PDP state ACTIVE is
permitted only when the mobility management state of the subscriber is
STANDBY, READY, PMM-IDLE, or PMM-CONNECTED.
An active PDP context for an MS is moved to INACTIVE state when the
deactivation procedure is initiated. All active PDP contexts for an MS are
moved to INACTIVE state when the MM state changes to IDLE or PMMDETACHED.

43
Access Point Name

An Access Point Name is composed of two parts as follows:
The APN Network Identifier
The APN Operator Identifier
The APN Network Identifier is mandatory and is a label (for example
"corporation") or a set of labels separated by dots which is a domain name
according to the DNS naming conventions
The APN Operator Identifier is optional. It is a domain name according to
the DNS naming conventions, and consists of three labels. The APN
Operator Identifier shall end with ".gprs".
APN=
APN Network Id
my.isp.com.
APN Operator Id
mncxxx.mccyyy.gprs
NOTE: The APN stored in the HLR does not contain the APN Operator
Identifier. Also a wild card may be stored in the HLR instead of the APN.
44
APN Selection
The SGSN selects the Access Point Name (APN) to be used for a
PDP context based on the MS-requested parameters and the
subscribed PDP contexts of the user
Based on the APN, SGSN queries the DNS database and obtains
the GGSN address where the PDP session is to be established.
This is called APN Resolution.
For Internet TATA.DOCOMO.INTERNET
For WAP TATA.DOCOMO.DIVE.IN

For MMS TATA.DOCOMO.MMS

45
PDP CONTEXT ACTIVATION (GB mode)

MS BSS
SGSN
DNS
GGSN
1. Activate PDP Context

APN
2. DNS Query
APN
3 . DNS Response
GGSN IP Address
4 . Create PDP Context Request

5 . Create PDP Context Response
IP Address
6 . BSS Packet flow context

7. Activate PDP Context Accept
IP Address

46

1) The MS sends an Activate PDP Context Request (NSAPI, TI, PDP Type,
PDP Address, Access Point Name, QoS Requested, PDP Configuration
Options) message to the SGSN. The MS shall use PDP Address to
indicate whether it requires the use of a static PDP address or whether it
requires the use of a dynamic PDP address. The MS shall leave PDP
Address empty to request a dynamic PDP address.
The MS may use Access Point Name to select a reference point to a
certain packet data network and/or to select a service. Access Point
Name is a logical name referring to the packet data network and/or to a
service that the subscriber wishes to connect to. QoS Requested
indicates the desired QoS profile.

47

4)
The SGSN validates the Activate PDP Context Request using PDP Type (optional), PDP Address
(optional), and
Access Point Name (optional) provided by the MS and the PDP context subscription records.
If no GGSN address can be derived, the SGSN rejects the PDP context activation request.
If a GGSN address can be derived, the SGSN creates a TEID for the requested PDP context. If the MS
requests a dynamic address, the SGSN lets a GGSN allocate the dynamic address. The SGSN may
restrict the requested QoS attributes given its capabilities and the current load, and it shall restrict the
requested QoS attributes according to the subscribed QoS profile.
The SGSN sends a Create PDP Context Request (PDP Type, PDP Address, Access Point Name, QoS
Negotiated, TEID, NSAPI, MSISDN, Selection Mode, Charging Characteristics, Trace Reference, Trace
Type, Trigger Id, OMC Identity, PDP Configuration Options, serving network identity) message to the
serving GGSN.
The SGSN should send the serving network identity to the GGSN. PDP Address shall be empty if a
dynamic address is requested. The GGSN may use Access Point Name to find a packet data network
and optionally to activate a service for this APN. Selection Mode indicates whether a subscribed APN
was selected, or whether a non-subscribed APN sent by an MS or a non-subscribed APN chosen by the
SGSN was selected.

48
5)
Charging Characteristics indicates which kind of charging the PDP context is liable for.The SGSN shall
include Trace Reference, Trace Type, Trigger Id, and OMC Identity if GGSN trace is activated. The
SGSN shall copy Trace Reference, Trace Type, and OMC Identity from the trace information received
from the HLR or OMC.
The GGSN creates a new entry in its PDP context table and generates a Charging Id. The new entry
allows the GGSN to route PDP PDUs between the SGSN and the packet data network, and to start
charging. The way the GGSN handles Charging Characteristics that it may have received from the
SGSN. The GGSN may restrict QoS Negotiated given its capabilities, operator policies and the current
load.
The GGSN then returns a Create PDP Context Response (TEID, PDP Address, PDP Configuration
Options, QoS Negotiated, Charging Id, Cause) message to the SGSN. PDP Address is included if the
GGSN allocated a PDP address. If the GGSN has been configured by the operator to use External PDN
Address Allocation for the requested APN, PDP Address shall be set to 0.0.0.0, indicating that the PDP
address shall be negotiated by the MS with the external PDN after completion of the PDP Context
Activation procedure. The GGSN shall relay, modify and monitor these negotiations as long as the PDP
context is in ACTIVE state, and use the GGSN Initiated PDP Context Modification procedure to transfer
the currently used PDP address to the SGSN and the MS. PDP Configuration Options contain optional
PDP parameters that the GGSN may transfer to the MS.
These optional PDP parameters may be requested by the MS in the Activate PDP Context Request
message, or may be sent unsolicited by the GGSN. PDP Configuration Options is sent transparently
through the SGSN. The Create PDP Context messages are sent over the backbone network. If QoS
Negotiated received from the SGSN is incompatible with the PDP context being activated, the GGSN
rejects the Create PDP Context Request message. The GGSN operator configures the compatible QoS
profiles.

49

6) In A/Gb mode, BSS packet flow context procedures may be executed.
7) The SGSN inserts the NSAPI along with the GGSN address in its PDP context. If
the MS has requested a dynamic address, the PDP address received from the
GGSN is inserted in the PDP context. The SGSN selects Radio Priority and
Packet Flow Id based on QoS Negotiated, and returns an Activate PDP Context
Accept (PDP Type, PDP Address, TI, QoS Negotiated, Radio Priority, Packet Flow
Id, PDP Configuration Options) message to the MS. If the MS indicated in the MS
Network Capability it does not support BSS packet flow procedures, then the
SGSN should not include the Packet Flow Id. The SGSN is now able to route PDP
PDUs between the GGSN and the MS, and to start charging.

50
GPRS Tunneling Protocol principle

GPRS Tunnelling Protocol (GTP)
The GPRS Tunnelling Protocol (GTP) allows multi-protocol packets to be tunnelled
through the GPRS backbone between GPRS Support Nodes (GSNs). The GTP can have
proprietary extensions to allow proprietary features. The relay function in the SGSN relays
the user PDP (Packet Data Protocol) PDUs (IP or X.25) between the Gb and the Gn
interfaces.
GTP is defined both for the Gn interface, that is, the interface between GSNs within the
same PLMN, and the Gp interface between GSNs in different PLMNs.
The UDP/IP and TCP/IP are examples of paths that may be used to multiplex GTP tunnels.
The choice of path is dependent on whether the user data to be tunnelled requires a reliable
link or not. Two modes of operation of the GTP layer are therefore supported for information
transfer between the GGSN and SGSN.
unacknowledged (UDP/IP)
acknowledged (TCP/IP).
A UDP/IP path is used when the user data is based on connectionless protocols, such as IP.
A TCP/IP path is used when the user data is based on connection-oriented protocols, such
as X.25.The GTP layer can support both modes simultaneously.

51

52

Signalling plane
In the signalling plane, the GTP specifies a tunnel control and management
protocol which allows SGSN to provide GPRS network access for an MS.
The signalling plane also handles path management and location
management. Signalling is used to create, modify and delete tunnels.
The GTP signalling flow is logically associated with, but separate from, the
GTP tunnels. For each GSN-GSN pair, one or more paths exist and one or
more tunnels may use each path.

53

Transmission plane
In the transmission plane, the tunnel created by the signalling
plane is used to carry user data packets between network
elements connected to the GPRS backbone network, such as
the SGSNs and GGSNs.
No other systems need to be aware of GTP, for example, the
MSs are connected to a SGSN without being aware of GTP.

54

55

Tunnel ID (TID) format
The Tunnel Identifier (TID) consists of the following:
Mobile Country Code (MCC)
Mobile Network Code (MNC)
Mobile Subscriber Identification Number (MSIN)
Network Service Access Point Identifier (NSAPI)
These represent the MM and PDP contexts.

56
THANK YOU
57

GPRS Fundamentals

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

GPRS Fundamentals

Caricato da

Copyright:

Formati disponibili

GPRS Fundamentals

For internal use only