Interfaces, Protocols, Procedures Siemens

Interfaces, Protocols, Procedures

Contents
1 Overview: Interfaces & Protocols 3
1.1 Signaling in GSM Phase1/2 4
1.2 Transmission in the GSM/GPRS-PLMN 6
1.3 GPRS Transmission Plane 8
1.4 GPRS (Signaling Plane) in the GPRS 16
2 The Radio Interface (Layer 1) 21
2.1 Layer 1 of the GSM-/GPRS-Radio Interface Um 22
2.2 Channel Bundling, Sharing of Channels 24
2.3 Channel Coding 26
2.4 Logical GPRS Radio Channels 30
2.5 Multiframes in GPRS 34
3 Activation of GPRS Services 37
3.1 Mobility Management States 40
3.2 Packet Data Protocol PDP States 42
3.3 GPRS Packet Data Transmission 44
3.4 Combined GPRS & IMSI Attach 46
3.5 PDP Context Activation Procedure 48
3.6 Start of Mobile Originated Packet Transfer 50

TM2110EU01TM_0003
1
 Siemens Interfaces, Protocols, Procedures

2 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

1 Overview: Interfaces & Protocols

GPRS:
Interfaces,
Protocols & Procedures

Overview:
Interfaces & Protocols

Fig. 1

TM2110EU01TM_0003
3
 Siemens Interfaces, Protocols, Procedures

1.1 Signaling in GSM Phase1/2

In GSM-PLMN phase 1/2 the Signaling System No. 7 SS7 is used for the transmis-
sion of signaling information between the components of the network switching sub-
system NSS (interfaces B-G), as well as between MSC and BSC (A-interface) and in
direction of the external ISDN networks.
SS7 comprises 4 levels, of which the lowest 3 layers are combined to form the mes-
sage transfer part MTP whereas level 4 contains different user parts depending on
the tasks to be performed. Level 1 serves for the physical transmission (physical
layer) of data and for the provision of the requested equipment. (e.g. cable connec-
tion, radio relay links, ...). In the GSM-PLMN PCM30/PCM24 (E1/T1) is used for the
realization of level 1 functions.
Level 2 serves for the safe transmission of signaling information (link layer). Its func-
tions include fault location and clearance across a sub-part of the transport.
Level 3 determines the entire transport link (network layer) including the transport of
information in the event of faults in individual signaling points (e.g. overload).
The Mobile Application Part MAP is the most important User Part UP (layer 4). It
regulates the mobility aspects in the GSM-PLMN between the MSCs as well as be-
tween MSCs and registers. Its functions include amongst others: updating and clear-
ance of location information in the VLR, storing of routing information in the HLR, up-
dating and supplementing of user profiles in the HLR&VLR, Inter-MSC handover, ...
The ISDN user part ISUP handles the connection-oriented signaling between MSCs
and external networks.
GSM-specific signaling between MSC and BSC is defined in the BSS Application
Part BSSAP. The BSSAP is subdivided into the Direct Transfer Application Part
DTAP used for the BSC-transparent transport of signaling (call control CC and mobil-
ity management MM) between MS and MSC, and the BSS Management Application
Part BSSMAP used for radio resource management RR.
The signaling connection control part SCCP and transaction capabilities application
part TCAP are user-neutral user parts which serve for the support of complex MAP
applications. SCCP can be used also for the support of ISUP and BSSAP.
Layer1 and layer 2 tasks (Link access Protocol for D-channel) on the Asub and Abis
interfaces have been slightly modified as compared to SS7. The radio interface Um in
the GSM-PLMN is set up of three layers.
Layer 1 serves for the physical transmission and includes the implementation of the
logical signaling channels (FDMA/TDMA, multiframes, channel coding, etc.)
Layer 2 functions on Um are performed by a modified LAPD unit (LAPDm).

4 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Layer 3 on the Um radio interface is subdivided in three sublayers: radio resource

management RR (channel administration, cell selection, power control and hando-
ver), mobility management MM and connection management CM (set-up, operation
and clear-down of services). The connection management consists of three phases:
call control CC, supplementary services support SS and short message services
SMS support.

Signaling in the GSM-PLMN:

(Phase 1 / 2)
CM
CC SS SMS HLR AC VLR EIR
MM
RR MAP
LAPDm TCAP
L1 LAPD(m) Signalling System
SCCP
L3 No. 7
RR
LAPD
L2 MTP SS7
x L1
L1

BTS BSC MSC ISDN

MS
BSSAP ISUP
BSSMAP DTAP SCCP
SCCP
OMC-B OMC-B MTP
MTP

Fig. 2 Signaling in the GSM-PLMN based on LAPD(m) and SS7

TM2110EU01TM_0003
5
 Siemens Interfaces, Protocols, Procedures

1.2 Transmission in the GSM/GPRS-PLMN

Beside the interfaces in the “classical” GSM PLMN, a number of new interfaces are
defined for the implementation of GPRS services based on the introduction of the
new network elements SGSN and GGSN.
The interfaces Gi (external PDN-GGSN), Gn (GSN-GSN), Gb (SGSN-BSS) and Gd
(SGSN-SMS/IWMSC) serve for the transport of both signaling data and of user data.
Interfaces Gp (GSN-GSN in external PLMNs), Gf (SGSN-EIR), Gc (GGSN-HLR), Gs
(SGSN-MSC/VLR) and Gr (SGSN-HLR) serve exclusively for the transfer of signaling
data.

6 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Transmission in Signaling &

user data
the GPRS-PLMN Signalling

SMS-GMSC
SMS-IWMSC SMS-SC Packet switched

E C
Also for
Gd user data
D transmission
MSC/VLR HLR/(GR)
Protocols
above
Gs Gr Layer 1 !!
A Gc
Um Gb Gn Gi
MS BSS SGSN GGSN PDN TE

Gn Gf
Gp
SGSN EIR
GGSN
other PLMNs

Fig. 3 Transmission and interfaces in the GPRS PLMN

TM2110EU01TM_0003
7
 Siemens Interfaces, Protocols, Procedures

1.3 GPRS Transmission Plane

The transmission plane has a layered protocol structure for the transfer of user infor-
mation. It includes the control procedures associated with the information transfer,
e.g. flow control, fault detection and fault clearance.
The bird's-eye view on the protocols reveals the intention of this structure:
If the application is internet access for example the GPRS MS (WWW client) and the
PDN (WWW server) will exchange IP packets. This is the IP protocol below the appli-
cation in the stack of the MS and the IP on top of the stack of the GGSN. The rec-
ommendations have defined that X.25 protocol is possible too. In case of IP the MS
has to be part of the IP world and needs to be identified by an IP address which can
be either temporary or static. This IP address has to remain the same as long as the
PDP which is related to this application is active. This is necessary because the PDN
is not able to handle the mobility of the subscriber. If the GPRS MS is moving to cell
in the service area of another SGSN the GPRS network has to solve the problem by
the IP layer on the Gn interface above the L2 layers. In consequence the fact that the
GPRS user is a mobile user is not to be seen by the PDN, the user data is tunneled
transparently.
The air interface makes it necessary to introduce protocols which adopt the size of
the packets. They perform segmentation/re-assembly depending on the direction of
the packets to be able to send IP packets via an air interface which consists of bursts
which a fixed bit structure.
One of the main advantages of GPRS compared to HSCSD is that it is packet
switched. This can only be done by introducing new network elements using new
hardware/protocols and by changes in the protocol structure on Um to enable packet
switching. The latter is done by the MAC protocol.

8 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

GPRS transmission plane

Application

IP / X.25 IP / X.25
Relay
SNDCP SNDCP GTP GTP

LLC LLC UDP / UDP /

TCP TCP
Relay
RLC RLC BSSGP BSSGP
IP IP

MAC MAC FR FR L2 L2

GSM RF GSM RF L1bis L1bis L1 L1

Um Gb Gn Gi
MS BSS SGSN GGSN
SNDCP: SubNetwork Depentent Protocol GTP: GPRS Tunnelling Protocol
LLC: Logical Link Control UDP: User Datagrm Protocol
RLC: Radio Link Control BSSGP: BSS GPRS Protocol TCP: Transmission Control Protocol
MAC: Medium Access Control FR: Frame Relayl IP: Internet Protocol

Fig. 4 GPRS protocol layers for data transmission

TM2110EU01TM_0003
9
 Siemens Interfaces, Protocols, Procedures

Protocol Structure for the interfaces Gi and Gn

The following protocols are needed to pass the user data from the PDN to the SGSN
(or vice versa) during GPRS transmission in the GSM-PLMN:

L2‘, L1‘: L2‘ and L1‘ are the link layer and physical layer of the external networks
connected via the Gi-interface to the GSM-GPRS-PLMN. As such, L2‘ and L1‘ are
situated outside the GPRS definition area. However, there has to be an agreement in
terms of these layers functions between the different network operators (GSM-PLMN
and PDN) interconnected via the Gi-interface, or between the GSM network operator
and a transit network.

GTP (GPRS Tunneling Protocol)

The GTP task is to tunnel user data and user signaling between the GPRS support
nodes GSN of the GPRS backbone network. The data packets (protocol data units
PDUs) supplied by different packet data protocols PDPs, e.g. X.25 or IP, have to be
encapsulated / de-capsulated by the GTP prior to tunneling. GTP is specified in
Rec.09.60.

UDP / TCP (User Datagram Protocol / Transmission Control Protocol): UDP and
TCP respectively are used for the transfer of data packets encapsulated by the GTP
across the GPRS backbone network. The protocol needed for this is called UDP. It
has to be supported by all GSNs as minimum solution since it transports data pack-
ets (GTP PDUs) of protocols which require a safe data connection (e.g. IP). UDP
also protects transmission against data corruption/mutilation. TCPs have to be sup-
ported in the GSNs whenever data packets of protocols have to be transported, re-
quiring safe data connections (e.g. X.25). TCP ensures the flow control and provides
protection against loss of data and data corruption.

IP (Internet Protocol): is used in the GPRS backbone network for the routing of user
data and network information. At the beginning, the GPRS backbone network can be
based on the IP version 4. However, the objective envisaged is IP version 6.

L2, L1: L2 and L1 are GPRS-internal link and physical layer. L2 and L1 are situated
outside the area of GPRS definition. Operator-specific solutions are used here.

10 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Relay Protocols
• En-/De-capsulation PDUs (IP,X.25)
GTP via
Gi, Gn
• tunneling of user data & signalling
data between GSNs GPRS
Tunnelling GPRS-
Protocol
transmission plane
UDP
• transmit encapsulated GTP data packets User
• protect against data corruption
• UDP / TCP ® Protocols for unreliable /
Datagram IP / X.25
Protocol
reliable data link (z.B. IP / X.25)
• UDP: minimum solution for each GSN
TCP
• TCP includes flow control & data protection Transmission
Control
Protocol

IP
Internet
Protocol
GPRS backbone network
IP V4 / V6 L2 L2‘
Link Layer Link Layer • extern
• arrangement PLMN
L1 L1‘ -PDN necessary
Operator specific Physical Physical
Layer Layer

PDN
SGSN Gn GGSN Gi
(e.g. X.25, IP)

Fig. 5 Protocols via Gi and Gn, "Ip over IP"

TM2110EU01TM_0003
11
 Siemens Interfaces, Protocols, Procedures

Protocol Structure for the interface(s) Gb (and Um)

SNDCP (SubNetwork Dependent Convergence Protocol):

The SNDCP supports the following functions: compression/segmentation and joining,
multiplexing and de-multiplexing of data packets onto one or several LLC SAPs
(service access points). The compression function is applied to the user data of the
data packet and (if applicable) to the packet header. Segmentation is required to limit
the size of the data packets which is transferred by the LLC as one single unit via the
radio interface. The SNDCP is specified in the GSM Rec. 04.65.

LLC (Logical Link Control): The LLC layer realizes a highly reliable ciphered logical
connection and thus provides the basis for maintaining communication between the
SGSN and the MS. From the point of view of the LLC layer, there is a complete con-
nection between SGSN and MS, even if the RLC/MAC do not support a physical
connection, i.e. even if no data packets are transferred at that point in time. A physi-
cal connection is set-up by the RLC/MAC layer only if the LLC layer supplies the data
required for transmission. LLC layer has several access points to be able to transport
various types of data; also, it distinguishes between several “quality of service QoS”
classes. The LLC layer is also responsible for carrying out the ciphering function in
the GPRS network. LLC is specified in GSM Rec. 04.64.

BSSGP (BSS GPRS Protocol): The BSSGP transports the LLC frames as well as
routing and QoS-related information between the BSS (PCU) and the SGSN. The
BSSGP does not carry out fault correction. It is specified in GSM Rec. 08.18.

FR (Frame Relay): The Network Service (NS) layer transports the BSSGP data
packets. NS is based on frame relay, which thus represents the link layer protocol for
the connection between SGSN and PCU (Gb interface). NS is specified in GSM Rec.
08.16.

L1bis: Physical Layer of the Gb-interface. L1bis is realized through E1/T1

(PCM30/PCM24)technology.

12 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Protocols via Relay

• Compression
Gb, (Um) SNDCP
(user data + maybe header) GPRS- SubNetwork
• Segmentation / Re-assembly transmission plane Dependent GTP
• Multiplexing / De-Multiplexing Convergence
different PDPs Protocol

LLC
• logical connection (even Logical Link
without physical connection) Control UDP /
• different SAPs (SNDCP,
GMM/SM, SMS), QoS,.. Relay TCP
• Ciphering
BSSGP BSSGP
RLC BSS BSS
GPRS GPRS
Protocol Protocol IP
• transmit LLC frames
• & Routing & QoS - Infos
• no error correction
MAC FR FR L2
Frame Relay Frame Relay
Unreliable transport
BSSGP PDUs L1bis L1bis
GSM RF Physical Physical L1
Layer Layer
E1 / T1 (PCM30/24)
Um BSS (PCU) Gb SGSN Gn
SAP: Service Access Point

Fig. 6 Protocols via Gb (and Um)

TM2110EU01TM_0003
13
 Siemens Interfaces, Protocols, Procedures

Protocol Structure for Um

RLC (Radio Link Control) / MAC (Medium Access Control): RLC and MAC are the
layers used for the implementation of a reliable physical connection via the radio in-
terface on which data packets are transported. RLC and MAC are closely associated
with each other and are defined in GSM Rec. 04.60.

RLC (Radio Link Control): The RLC function supplies a reliable connection (pro-
vides BEC) via the radio interface. The physical connection depends on how the ra-
dio transmission is realized in each case (L1-dependency). RLC segments LLC
frames and re-assembles them respectively. In addition, the RLC carries out sub-
multiplexing in order to place more than one MS on a physical channel and to bundle
up to 8 physical channels for one MS.

MAC (Medium Access Control): The MAC function controls the signaling proce-
dures via Um which are required to obtain network access (access signaling proce-
dures), e.g. request and grant of radio resources (packet data channel PDCH). Fur-
thermore, the MAC function controls the mapping of LLC frames to the physical
channels of the radio interface. The identifiers (TFI "Temporary Flow Identifier, USF
"Uplink State Flag") which are used by the MAC protocol enable the sharing of physi-
cal channels by several MSs. Different mechanisms of allocation of radio resources
may be used, dynamic or fixed allocation (to be explained in the next chapter).

GSM RF (Radio Frequency): GSM RF is the physical channel used to transfer

packet data via the GSM radio interface Um.

14 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Protocols via Um
GPRS
TE
Application transmissions plane
GGSN
IP / X.25

RLC/MAC:
SNDCP enable reliable
SGSN physical connection
via Um
LLC

Relay • Segmentation / Re-assembling

LLC-frames « RLC radio blocks
RLC RLC BSSGP • Backward Error Correction BEC
Radio Link Radio Link
Control Control

MAC MAC • Access Signalling Procedures

Medium Access Medium Access FR (Requests, Grants)
• Sub-Multiplexing:
Control Control
different MSs ® 1 physical channel
channel combining ® 1 MS (1..8 TS)
GSM RF GSM RF L1bis
Physical RF-channel
for packet data transmission
MS Um BSS (PCU) Gb

Fig. 7 Protocols via Um

TM2110EU01TM_0003
15
 Siemens Interfaces, Protocols, Procedures

1.4 GPRS (Signaling Plane) in the GPRS

The signaling plane consists of protocols for the control and support of transmission
plane functions:
Control of GPRS network access, e.g. „attaching“ and „detaching“
Control of the data elements (attributes) of an established network connection and
activation of the packet data protocol PDP (e.g. X.25 / IP) addresses.
Control of the routing path of an established connection in terms of subscriber mobil-
ity support.
Support of the network resource allocation to account for various user requests.
Supplementary services implementation

Signaling Plane MS-SGSN:

In addition to the protocols of the transmission plane a further plane, based on the
functions GSM FR, RLC/MAC and LLC, is required:
GMM/SM (GPRS Mobility Management and Session Management): The GMM/SM
protocol supports mobility management functions such as GPRS attach, GPRS de-
tach, safeguarding functions, routing area & location update), and session manage-
ment functions as PDP context activation & deactivation & modification.

16 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

GPRS signaling plane Mobility Management functions

• GPRS attach / detach
MS-SGSN • security functions
• Update Location (CGI, RAI)
• PDP context (de-) activation / modification

GMM/SM GMM/SM
GPRS Mobility GPRS Mobility
Management Management
& Session & Session
Management Management

LLC LLC

Relay
RLC RLC BSSGP BSSGP

MAC MAC FR FR

GSM RF GSM RF L1bis L1bis

Um Gb
MS BSS SGSN

Fig. 8 GPRS signaling plane, GMM/SM

TM2110EU01TM_0003
17
 Siemens Interfaces, Protocols, Procedures

Signaling SGSN - HLR / EIR / SMS-GMSC, GGSN - HLR:

For signaling via Gr-, Gf-, Gd- and Gc-interface, i.e. between SGSN and HLR, EIR,
SMS-GSMC and between GGSN and HLR the same protocols of Signaling System
No. 7 (SS7) are used as in the NSS of GSM-PLMN (Phase1/2). The realization of the
Message Transfer Parts MTP (L1 – L3), of the Signaling Connection Control Part
SCCP as well as of the Transaction Capabilities Application Parts TCAP are identi-
cal.

MAP (Mobile Application Part): The MAP used in GSM (Phase1/2) needs to be ex-
panded by mobility management functions particularly in view of the information ex-
change between SGSN and GGSN and between SGSN and HLR respectively (GSM
Rec. 09.02.)
The information flow between GGSN and HLR can also flow across further GSNs
and is tunneled in this case by using the GPRS tunneling protocol GTP between the
GSNs (Gn-interface).

Signaling plane SGSN – MSC/VLR

Signaling via the Gs interface, i.e. between SGSN and MSC/VLR, uses the same
protocols of the SS7 as the ones used via the A-interface of the GSM-PLMN (GSM
Rec. 09.16).

BSSAP+ (BSS Application Part+): Signaling is performed via a subset of the

BSSAP functions used on the A-interface (GSM Rec. 09.18).

Signaling plane GSN-GSN:

The exchange of signaling information between the different GPRS Support Nodes
GSN (Gn-interface), i.e. via the IP-based GPRS backbone uses the corresponding
transmission plane protocols: L1, L2 (operator-specific), IP (V4, later V6), UDP (User
Datagram Protocol) and GTP (GPRS Tunneling Protocol). The GTP tunnels both
user and signaling data between the various SGSN and GGSN.

18 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

GPRS Signaling plane

MAP enhanced for GPRS Subset of BSSAP functions

MAP MAP BSSAP+ BSSAP+

Mobile Mobile
BSS Application BSS Application
Application Application
Part + Part +
Part Part
TCAP
Transaction
TCAP
Capabilities
Application Part
SCCP
Signalling Connection SCCP SCCP SCCP
Control Part

MTP L3 MTP L3 MTP L3 MTP L3

MTP L2 MTP L2 MTP L2 MTP L2

L1 L1 L1 L1

SGSN Gr,f,d HLR, EIR, SMS-GMSC SGSN Gs MSC/VLR

GGSN Gc HLR

Fig. 9 GPRS signaling plane, protocol stack for CSS7-interfaces

TM2110EU01TM_0003
19
 Siemens Interfaces, Protocols, Procedures

20 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

2 The Radio Interface (Layer 1)

GPRS:
Interfaces,
Protocols & Procedures

The Radio Interface Um

(Layer 1)

Fig. 10

TM2110EU01TM_0003
21
 Siemens Interfaces, Protocols, Procedures

2.1 Layer 1 of the GSM-/GPRS-Radio Interface Um

By introducing GPRS services into the GSM-PLMN, world-wide modifications are
necessary also in the area of physical transmission (layer1) via the air or radio inter-
face Um. The tasks of layer 1 radio interface relate to the transmission of user and
signaling data as well as to the measuring of receiver performance, cell selection,
determination and updating of the delayed MS transmission (timing advance TA),
power control PC and channel coding.
In the GPRS, a decisive difference to the realization of the connection-oriented serv-
ices (circuit-switched services) relates to the fact that a physical channel and a so-
called packet data channel can be used by several mobile stations at the same time.
One packet data channel is allocated per radio block, i.e. for four consecutive TDMA
frames and not for a specific time interval. This means that signaling and the packet
data traffic of several mobile stations can be statistically multiplexed into one packet
data channel. Furthermore, the packet data channel can be seized asymmetrically.
On the other hand it is also possible for a mobile station to use more than one packet
data channel at the same time, i.e. to combine several physical channels of one radio
carrier. In principle, up to 8 packet data channels can be seized simultaneously. The
number of channels that are combined for reception (DL) and transmission (UL) can
be different to achieve asymmetric data rates for certain applications (e.g. file transfer
protocol FTP, internet surfing).
The assignment of radio resources can be done dynamically or in a fixed allocation.
In case of the fixed allocation a message with a bit pattern is sent downlink to indi-
cate which channels can be used by this MS for UL transmission.
If dynamic allocation is applied the MS will be receive a temporary flow identifier (TFI)
and an uplink state flag (USF) for each of the time slots it is allowed to use. The TFI
is part of the control information in the DL packet and identifies the "owner" of the
packet. Each packet also includes an USF that indicates which of the MSs (that has
been assigned to use this time slot UL) is allowed to transmit the next radio block UL.

22 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Transmission
of user & GSM RF:
signaling data
GPRS Layer 1 (Um)
Measure
signal strength Cell Selection

L1-
tasks
determinate &
Power Control Resource optimisation:
actualise
functions 1 physical channel to be used
Timing Advance
by many MSs simultaneously !!

Allocation of physical channel asymmetrical traffic

(Packet Data Channel PDCH) UL / DL possible !!

dynamically: 1 or 4 Radio Blocks High data rate traffic

(1 Radio Block = 4 Normal Burst up to 171.2 kbit/s:
in 4 consecutive TDMA-frames) combining 1..8 PDCH for 1 MS !!
Þ User & signalling data of several MSs
statistically to be multiplexed into 1 PDCH

(also fixed allocation possible)

Fig. 11 Tasks of the GSM air interface, layer 1 (GSM RF)

TM2110EU01TM_0003
23
 Siemens Interfaces, Protocols, Procedures

2.2 Channel Bundling, Sharing of Channels

Sharing of Resources in a Cell: GSM circuit switched (CS) users will share the time
slots in a BTS with the GPRS packet switched (PS)users. A physical channel can ei-
ther be used for GSM CS or GPRS PS traffic but not for both at the same time. De-
pending on the traffic load in the cell there will be more or less channels available for
GPRS, CS connections are dealt with priority.
Sharing of Physical Channels: It is a characteristic of a CS connection that the
physical resource (the time slot) is reserved for one subscriber. Therefore the
GSM CS users cannot share their channels with others. In contrast GPRS PS sub-
scribers can share physical channels. The handling of the channels, the multiplexing
of subscribers onto the same time slots is done by software (protocol, MAC) and
hardware (PCU). Packet oriented connections are not only carried out through the
core network by usage of an appropriate hardware (ATM switches) and software
(protocols) but also on the air interface. This is an important feature of GPRS with re-
gard to an optimized usage of resources on Um which is the limiting bottleneck in the
PLMN.
Multislot Class: The subscribers for GPRS will have different needs (applications,
data rates) and therefore the MS will have more or less capabilities. The network
(PCU) will have to identify these different MSs by their multislot class which indicates
how many time slots (channels) can be bundled by the MS uplink and downlink. A
cheap GPRS mobile will be a GSM mobile that is able to handle the protocols and
coding schemes of GPRS. This will be multislot class 1: one time slot UL and one
time slot downlink can be "bundled". The other extreme is multislot class 29 which
will be able to receive and to transmit in eight time slots UL and DL simultaneously. In
consequence such a MS has to have two synthesizers, and a high battery capacity
because this is more or less continuous transmission and reception. The MS will
send its multislot class and the PCU will only assign time slot combinations which can
be handled by this equipment.

24 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Channel Bundling, Sharing of Channels

e.g. BTS with 2 RFCs => 2 TRX = 16 channels
Signaling:
e.g. 6 GSM e.g. 4 GPRS
BCCH,
CS users PS users
SDCCHs,...

RFC 1 multislot classes

•29 classes defined
•assignment of
UL channels by PCU
according to
RFC 2
capabilities of MS
•identifying “high
end“ and “low cost“
MS
RFC 1
DL sharing of physical
time
channels
RFC 2 slot
=> packet switching
TDMA frame = 8 time slots on Um

Fig. 12 Channel Bundling, sharing of channels, multislot classes

TM2110EU01TM_0003
25
 Siemens Interfaces, Protocols, Procedures

2.3 Channel Coding

Channel coding was modified substantially for GPRS purposes (GSM Rec. 03.64).
Channel coding starts with the division of digital information into transferable blocks.
These radio blocks, i.e. the data to be transferred (prior to encoding) comprise:
l a header for the Medium Access Control MAC (MAC Header)
l signaling information (RLC/MAC Signaling Block) or user information (RLC Data
Block) and
l a Block Check Sequence BCS.
The functional blocks (radio blocks) are protected in the framework of convolutional
coding against loss of data. Usually, this means inserting redundancy.
Furthermore, channel coding includes a process of interleaving, i.e. different ar-
rangement in time. The convolutional radio blocks are interleaved to a specific num-
ber of bursts/burst blocks. In the case of GPRS, interleaving is carried out across four
normal bursts NB in consecutive TDMA frames and, respectively, to 8 burst blocks
with 57 bit each.

Four new coding schemes were introduced for GPRS (Rec. 03.64): CS-1 to CS-4.
These can be used alternatively depending on the information to be transferred and
on the radio interface’s quality.

26 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Channel Coding
4 new Coding Schemes:
BCS: Block Code Sequence
(for error recognition) CS-1, -2, -3, -4

collect
Radio Block
user data MAC Header RLC Data Block BCS
signaling
MAC Header RLC/MAC Control Block BCS
MAC: Medium Access Control
RLC: Radio Link Control

Convolutional Radio Block

coding rate 1/2 convolutional coding (Redundancy !)
(not CS-4)
Radio Block
Puncturing puncturing
(only CS-2, CS-3)
Radio Block (456 Bits)

8 Burst-
Interleaving 57 Bit 57 Bit 57 Bit ••• 57 Bit 57 Bit
blocks

Um: Allocation of PDCH for 1 / 4 Radio Blocks = 4 / 16 Normal Bursts

Fig. 13 Channel Coding, RLC/MAC blocks, redundancy

TM2110EU01TM_0003
27
 Siemens Interfaces, Protocols, Procedures

Coding Schemes:
CS-1: CS-1 uses the same coding scheme as specified by Rec. 05.03 for the
SDCCH. It comprises a half rate convolutional code for FEC forward error correction.
CS-1 corresponds to a data rate of 9.05 kbit/s.
CS-2 and CS-3 are punctured version of the same half rate convolutional code as
CS-1. The coded bits are numbered starting from 0 and certain punctured bits are
removed.
CS-2: With CS-2 the punctured bits have numbers 4 * i + 3 with i = 3,...,146 (excep-
tion: i = 9, 21, 33, 45, 57, 69, 81, 93, 105, 117, 129, 141). This means that none of
the first 12 bits is punctured. CS-2 corresponds to a data rate of 13.4 kbit/s. Remark:
For CS-2 the puncturing pattern must be adapted to the future new TRAU frame for-
mat in order to be used via the Abis interface (e.g. more bits must be punctured to
make space for RLC signaling).
CS-3: With CS-3 the punctured bits have numbers 6 * i + 3 and 6 * i + 5 with i =
2,...,111. CS-3 correspond to a data rate of 15.6 kbit/s.
CS-4: CS-4 has no redundancy (no FEC) and corresponds to a data rate of 21.4
kbit/s.

By bundling up to 8 packet data channels of one carrier into one MS, transmission
rates up to 171.2 kbit/s are possible.

28 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Channel Coding: Coding Schemes

CS-1 CS-2 CS-3 CS-4 different
redundancy
(FEC)
9,05 kbit/s 13,4 kbit/s 15,6 kbit/s 21,4 kbit/s ® Quality Um

Coding Code Radio Coded Punctured Data Rate

Scheme Rate Block* Bits Bits kbit/s
CS-1 1/2 181 456 0 9,05

CS-2 »2/3 268 588 132 13,4

CS-3 »3/4 312 676 220 15,6

CS-4 1 428 456 0 21,4

common bundling
coding & interleaving 1..8 TS
for 4 Normal Bursts:
* Radio Block without 456 Bit coded user
Uplink State Flag USF & max. 171,2 kbit/s
Block Check Sequence BCS
data

Fig. 14 Coding schemes of GPRS, CS1 with high redundancy, CS4 no redundancy, radio blocks

TM2110EU01TM_0003
29
 Siemens Interfaces, Protocols, Procedures

2.4 Logical GPRS Radio Channels

Use of "classical" logical channels for GSM-CS
A Logical channel is used for a special purpose/contents. For example the MSs have
to find out if this cell is a suitable one (operated by the "right" network operator),
which features are offered (e.g. HR/FR/EFR, GPRS, ...), what is the structure of Um
(channel combination), ... This is provided by the BCCH which is naturally only
transmitted in the downlink. Some resources have to be given for initial access for the
MS (RACH). For these reasons logical channels have been defined to fulfil all tasks
which are necessary in a GSM network on the air interface (see figure 13).
The GPRS subscribers will share the air interface with the circuit switched users. On
the other hand the protocol structure of GPRS is different from "classical" GSM-CS.
Therefore the user traffic and (part of) the signaling will have to be separated. Before
this separation can take place the different MS (GPRS/non-GPRS) have to be han-
dled by signaling procedures for access (channel assignment. There are two solution
of this problem. The first one is to use (some of) the logical channels for GSM-CS:
The GPRS-MS detects the BCCH of this particular cell and looks for the system in-
formation to find out if GPRS is available. If this is a cell belonging to the same rout-
ing area the MS can choose this cell and wait for paging or for the user to use the
RACH for activating a PDP. In case that the user wants to run an PS application the
GPRS MS will use an access burst (RACH) which indicates that this is a GPRS MS
and the request will be answered by the PCU assigning resources for packet
switched traffic (time slots reserved for GPRS). Signaling (e.g. for authentication) will
then take place using these resources indicated by the message in the AGCH.
So GPRS uses some of the logical channels of GSM-CS. On one hand this can be
an advantage if the resources are sufficient. On the other hand if in the future more
and more GPRS traffic has to be handled, separate logical channels reserved for
GPRS MS will have to be given. This is the second solution. In any case the GPRS
MS will have to look for the BCCH of the cell to find out if GPRS is available. If the
second solution has been chosen the GPRS MS will also read information where a
PBCCH (Packet Broadcast Control Channel) is to be found (which time slot). This
second solution will be explained in figure 14.

30 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Logical channel
(for GSM Circuit Switched)
BCCH CGI, FR/EFR/HR, GPRS available
BCH
Broadcast Control Channel frequency hopping, channel combination,...)
Broadcast Channel DL
FCCH frequency synchronization
Frequency Correction Channel

SCH
Synchronisation Channel Time synchronization + BSIC, TDMA-No.

CCCH PCH Paging / Searching (MTC)

Paging Channel
DL
Signaling Common Control Channel AGCH
Access Grant Channel Allocation of dedicated signaling channel
UL RACH
Random Access Channel Request for access
Dedicated signaling MS « BTSE (Call
DCCH SDCCH
Stand Alone Dedicated Setup, LUP, Security, SMS, CBCH,...)
Dedicated Control Channel UL Control Channel
+ SACCH Measurement Report,
Slow Associated TA, PC, cell parameters,...
DL Control Channel
FACCH
Fast Associated Signaling instead of TCH
Control Channel
TCH/F User traffic (Full Rate)
Traffic Channe/Fl
Traffic UL + DL TCH/H
User Data Traffic Channel/H User traffic (Half Rate)

Fig. 15 "Classical" logical channels of GSM may be used by GPRS users too

TM2110EU01TM_0003
31
 Siemens Interfaces, Protocols, Procedures

Use of new logical channels for GPRS

In addition to the nine existing logical radio channels used for signaling (BCCH, SCH,
FCCH, PCH, RACH, AGCH as well as SDCCH, SACCH and FACCH) and the Traffic
Channel (TCH) for circuit switched user information, a new set of logical channels
was defined for GPRS.
Packet traffic is realized by means of the Packet Traffic Channel (PTCH) which in-
cludes the following :
Packet Data Traffic Channel PDTCH.
Packet Associated Control Channel PACCH
The PDTCH is temporarily assigned to the mobile stations MS. Via the PDTCH, user
data (point-to-point or point-to-multipoint) or GPRS mobility management and session
management GMM/SM information is transmitted.
The PACCH was defined for the transmission of signaling (low level signaling) to a
dedicated GPRS-MS. It carries information relating to data confirmation, resource al-
location and exchange of power control information.

New GPRS signaling channels are mainly specified analogously to GSM Phase1/2.
The Packet Common Control Channel PCCCH has been newly defined. It consists
of a set of logical channels which are used for common control signaling to start the
connection set-up:
Packet Random Access Channel PRACH
Packet Paging Channel PPCH
Packet Access Grant Channel PAGCH
Packet Notification Channel PNCH
PRACH and PAGCH fulfil GPRS-MS functions which are analogue to the “classical”
logical channels RACH and AGCH for non-GPRS-users. The PNCH is used for the
initiation of point-to-multipoint multicast (PtM multicast).
For the transmission of system information to the GPRS mobile stations, the

Packet Broadcast Control Channel PBCCH

was defined analogue to the “classical” BCCH.
In a physical channel all different types of logical channels can be contained (no
separation into traffic and signaling channels respectively as is done in conventional
GSM). The differentiation of channel contents is carried out per radio block using the
MAC header, i.e. contents are specified for the four normal bursts of a radio block
sent in each case.
The MAC function, which distributes the physical channel to the various mobile sta-
tions and allocates radio resources to an MS can also use the conventional logical
channels in GSM.

32 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

New logical channel

for GPRS
PBCCH
Packet Broadcast System information
DL for GPRS-MS
Control Channel
PPCH Paging
Packet GPRS-MS
Packet Paging Channel
Common Control PAGCH Resource Allocation
Channels Packet Access for Setup of
Packet-Transfer
Packet- PCCCH DL Grant Channel
Signaling Notification
PNCH
Packet for GPRS-MS in
Notification Channel PtM Multicast
UL
PRACH access request for UL
Packet Random packet data transmission
Packet Access Channel Dedicated signaling MS-network
Traffic Channel PACCH e.g.: Acknowledgements,
PTCH Packet Associated Power Control, Resource
UL & DL Control Channel (Re-)Assignment
PDTCH Transmission of user packet data;
Packet Data Multislot operation:
Traffic Channel 1 MS - many PDTCH simultaneously

Fig. 16 New logical channels for GPRS

TM2110EU01TM_0003
33
 Siemens Interfaces, Protocols, Procedures

2.5 Multiframes in GPRS

The GPRS packet data traffic is arranged in 52-type multiframes (GSM Rec. 03.64).
52 TDMA frames in each case are combined to form one GPRS traffic channel multi-
frame which is subdivided into 12 blocks with 4 TDMA frames each. One block
(B0-B11) contains one radio block each (4 normal bursts, which are related to each
other by means of convolutional coding). Every thirteenth TDMA frame is idle. The
idles frames are used by the MS to be able to determine the various base station
identity codes BSIC, to carry out timing advance updates procedures or interference
measurements for the realization of power control.

For packet common control channels PCCH, conventional 51-type multiframes can
be used for signaling or 52-type multiframes. The GPRS users can use "classical"
common control channels of GSM before they will be directed onto their PTCHs. The
BCCH will be read by all mobiles anyway. Either in case of GSM mobiles to fulfil the
same tasks as before and for GPRS equipment this logical channel will indicate
weather GPRS service is available and if extra logical channels (PBCCH, PPCH, ...)
are used.

GSM CS traffic and GPRS subscribers are clearly separated so that there is no con-
flict due to different signaling or multiframe structure.

It is important that there are no "visible" changes for "GSM only mobiles" due to the
introduction of GPRS. GSM CS connections will use for example the same 26 multi-
frame structure for TCH an the 51 multiframe structure for signaling.

34 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

New multiframe • PDCH follows 52 multiframe structure

• 52 Multiframe: 12 Blocks à 4 TDMA-frames
for GPRS • PCCCHs: „classical“ 51er Multiframes
or 52er Multiframes
52 TDMA Frames = PDCH Multiframe
4 Frames 1 Frame

B0 B1 B2 i B3 B4 B5 i B6 B7 B8 i B9 B10 B11 i

B0 - B11 = Radio Blocks (Data / Signaling) Idle frame:

i = Idle frame • Identification of BSICs
• Timing Advance Update Procedure
• BCCH indicates PDCH with PBCCH (in B0) • Interference measurements
for Power Control
• DL: this PDCH bears PDCCH & PBCCH
PBCCH in B0 (+ max. 3 further blocks; indicated in B0)
PBCCH indicates PCCCH blocks & further PDCHs with PCCCH
• UL: PDCH with PCCCH: all blocks to be used for PRACH, PDTCH, PACCH
PDCH without PCCCH: PDTCH & PACCH only

Fig. 17 Multiframes for GPRS consist of a certain time slot in 52 consequent TDMA frames

TM2110EU01TM_0003
35
 Siemens Interfaces, Protocols, Procedures

36 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

3 Activation of GPRS Services

GPRS:
Interfaces,
Protocols & Procedures

Activation of
GPRS services

Fig. 18

TM2110EU01TM_0003
37
 Siemens Interfaces, Protocols, Procedures

States of the GPRS services

With regard to point-to-point PtP packet data transmission the GPRS service oper-
ates in two independent state models/circles. One circle describes the mobility man-
agement behavior whereas the other is assigned to the activation of a packet data
protocol PDP.

The circle related to mobility management states in the MS and the associated SGSN
consist of the :
l "Idle" state
l "Standby" state
l "Ready" state

The circle related to a specific packet data protocol has the:

l "Inactive" state
l "Active" state

38 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

States of
GPRS services 2 circles
regarding:

Idle
State Inactive
State
Mobility
Management
Packet Data
Standby Protocol
State PDP

Ready Active
State State

Fig. 19 States of GPRS services with regard to mobility management and packet data protocols

TM2110EU01TM_0003
39
 Siemens Interfaces, Protocols, Procedures

3.1 Mobility Management States

"Idle" state
A mobile station MS in the idle state is detached from the GPRS. Only GPRS sub-
scription data is available in the HLR. No further information exists in other network
units such as SGSN and GGSN. It is not possible to activate a packet data protocol
PDP or to maintain a PDP in its active state. The GPRS MS must monitor the BCCH
to determine the availability of cells which support GPRS services. Accordingly, the
GPRS MS can carry out PLMN and cell selection procedures. To exit idle state, the
MS must execute the “attach” procedure. Upon successful completion of this proce-
dure, the MS changes to ready state.

"Standby" state
In the standby state the GPRS MS is attached to the GPRS network. The GPRS and
the SGSN have a mobility management context comparable to the circuit switched
connections. The MS monitors the broadcast channel to determine the availability of
cells offering GPRS services and also the paging channel PCH, to be informed about
paging requests. The SGSN recognizes/stores the routing area RA of the GPRS-MS.
The routing area is a sub-unit of the location area LA, in other words a more detailed
determination of the GPRS-MS location. The GPRS-MS informs the SGSN about
changes of the routing area and answers paging requests.

"Ready" state
In the ready state, the SGSN detects the current cell of the GPRS-MS beyond the
routing area RA of the GPRS-MS. If the GPRS-MS changes cells, it informs the
SGSN. Paging is thus superfluous in the ready state. The DL packet data transfer
can be performed any time. Ready state does not mean that a physical connection is
established between SGSN and MS. Only in the ready state, SGSN and MS can
transfer data packets. MS and SGSN exit ready state upon expiry of a ready timer or
in case of a faulty packet data transmission and change to standby state. Upon log-
off, i.e. execution of a detach procedure, MS and SGSN exit ready state and change
to idle state.

40 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Mobility Management
States
• SGSN & GGSN without
MS information IDLE • MS observes BCCH
• only HLR contains subscription data
• no PDP context can be activated
state • PLMN- & Cell Selection

GPRS GPRS
attach detach

• SGSN knows Routing Area & cell !! READY • MS initiates Cell Update
• UL & DL packet transmission possible
state
expire SGSN: Paging / expire READY Timer /
STANDBY Timer MS: initiates Transfer Transmission errors

• SGSN « MS: MM-Context STANDBY • MS observes BCCH, PCH

• initiates RA-Update
• SGSN knows Routing Area
state • reacts to Paging Request

Fig. 20 Mobility management states

TM2110EU01TM_0003
41
 Siemens Interfaces, Protocols, Procedures

3.2 Packet Data Protocol PDP States

There are separate state circles for every authorized PDP of a GPRS-MS

"Inactive" State
The inactive state of a PDP means that this PDP is not operating at that moment.
There is no routing context in the MS, SGSN and GGSN. A transition in the active
state is only possible if there is a mobility management connection and if MS and
SGSN are in the standby or ready state.
No data transfer is possible in the inactive state. Data packets which reach the GPRS
network are either rejected or ignored.

"Active" State
In the active state the MS, GGSN and SGSN are in a routing context. Data can be
transmitted or received by the MS. The active state is ended explicitly if the MS de-
activates a certain PDP. With GPRS detach and expiry of the standby timer, all the
activated PDP are deactivated, too.

42 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

PDP States

• PDP not activated INACTIVE

• no Routing-context state Transition to „Active“ State
for MS, SGSN & GGSN
only if MM-context exists
• no data transmission possible ! ( MS & SGSN: STANDBY / READY)

De-activation PDP context /

GPRS detach Activation
expire STANDBY timer PDP context

ACTIVE
• Routing context
for MS, SGSN & GGSN state
• Data transmission possible !

Fig. 21 States of a Packet Data Protocol

TM2110EU01TM_0003
43
 Siemens Interfaces, Protocols, Procedures

3.3 GPRS Packet Data Transmission

The transmission of GPRS packet data presupposes the execution of
l GPRS Attach Procedure as well as of the
l PDP Context Activation Procedure.
In the case of a mobile packet data transfer, a one or two phase packet access is
added. This access procedure is necessary for packet data transfer.

Common Mobility Management / MS-Location

To reduce the signaling load via the radio interface during GPRS and non-GPRS op-
eration, important mobility management MM procedures are carried out jointly (com-
mon MM). This regards the procedures for : attachment / detachment, location &
routing area update and paging.
The result of a GPRS routing area update procedure is stored in the SGSN. The
routing area represents a more exact indication of the MS location, than is actually
needed for non-GPRS services. Triggered by the MS ( in the framework of a RA up-
date) the SGSN informs the MSC/VLR via the Gs interface of a change in the loca-
tion areas which has taken place simultaneously.
Further mobility management procedures are also executed via GPRS procedures. If
possible , all messages containing mobility management information, are transferred
through signaling data packets. The MM procedures are defined in the GGM/SM
(GPRS Mobility Management & Session Management).

44 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

GPRS Packet data transfer

PDP Context
GPRS Attach One / Two Phase RLC Data
Activation
Procedure Packet Access Transmission
Procedure

Common Mobility Management

Þ Reduce Signaling load via Um

Attachment
MS:
Detachment GPRS Procedures
GPRS & MS, « SGSN
Non-GPRS Location Update (GMM/SM)
operation adjust with
Routing Area Update
HLR, MSC/VLR
CS-Paging

Fig. 22 GPRS packet data transfer, one/two phase access

TM2110EU01TM_0003
45
 Siemens Interfaces, Protocols, Procedures

3.4 Combined GPRS & IMSI Attach

A first prerequisite for the GPRS data transfer to be carried out is the registration of
the MS in the GPRS network, i.e. the execution of an attach procedure. If an MS is
designed for common GPRS & non-GPRS operation, a common procedure for IMSI
and GPRS attach is carried out.

Attach Request (1)

Start of the combined attach procedure. In the attach request transmission the MS
indicates, which attach (only GPRS or also IMSI) is requested. The MS indicates its
identities (IMSI or packet TMSI: P-TMSI) and also the routing area identity RAI.

Identification Request / Response (2)

This is needed in case of SGSN change. The old SGSN (determined by the new
SGSN via P-TMSI) hands over to the new SGSN the IMSI as well as existing authen-
tication triples.

Security procedures (3)

The attach procedure can also contain security functions. The SGSN may request an
authentication of the MS and then initiate ciphering. Furthermore, the MS equipment
number in the EIR can be checked, too (IMEI check).

Update Location / Cancel Location & Ack / Insert Subscriber Data & Ack / Up-
date Location Ack (4)
In the event of SGSN change or first attach, routing area update procedures are
performed. The HLR is updated, the old SGSN released. The HLR delivers the
GPRS subscriber profile to the new SGSN which stores this profile for future PDP
context activation. The SGSN can then establish a mobility management context for
the MS.

Location Updating Request & Accept (5)

The IMSI attach is effected via SGSN in the framework of a combined routing area
RA /location area LA procedure (location updating request / accept). The SGSN ne-
gotiates the IMSI attach procedure with the MSC/VLR. From this, MSC/VLR derive
that the MS is also GPRS-attached and marks the MS accordingly.

Attach Accept & Complete / TMSI Reallocation Complete (6)

If the attach procedure was successful, the SGSN sends an attach accept informa-
tion to the MS. Optionally, a P-TMSI re-assignment takes place.
Upon successful completion of the attach procedure, MS and SGSN change to ready
state. The MS can now transmit SMS, receive point-to-multipoint PtM messages or
activate a PDP context.

46 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

MS new SGSN old SGSN MSC/VLR HLR

1 Attach Request
(GPRS/IMSI, P-TMSI, RAI,..) Identification Request
Common GPRS &
2
IMSI Attach
Identification Response

Security functions
3
(if necessary)
Update Location (SGSN-Id.)

Cancel Location

Cancel Location Acknowledge

4 Insert Subscriber Data

Insert Subscriber Data Acknowledge

Update Location Acknowledge

Location Updating Request

5 normal LUP with HLR,

Location Updating Accept maybe with MSC/VLR change

Attach Accept

6 Signaling message transferred

Attach Complete only for TMSI Reallocation by conventional signaling channel
only if P-TMSI re-allocation
TMSI Reallocation Complete by Packet Data Channel PDCH
MS & SGSN: Ready State

Fig. 23 The combined GPRS/IMSI attach procedure is used to save resources on the air interface

TM2110EU01TM_0003
47
 Siemens Interfaces, Protocols, Procedures

3.5 PDP Context Activation Procedure

For packet data to be transferred, an attach procedure must be followed by a PDP
context activation.

Activate PDP Context Request (1)

Normally, the mobile station starts a request to the network in order to activate the
desired PDP context (PDP type, e.g. Internet Protocol, PDP address) with the
needed Quality of Service QoS.
This request can also be started by a network and is then called network request.

Security functions (2)

Here, too, authentication / ciphering / IMEI can be carried out.

Create PDP Context Request & Response (3)

The SGSN checks the authorization of the data delivered in the activate PDP context
request, i.e. their agreement with the subscription data stored in the SGSN. The QoS
requests can be limited (network capacity, current load state). The routing context is
activated in the GGSN. Hereby, it is possible to transmit (tunneled) packet data be-
tween SGSN and GGSN.

Activate PDP Context Accept (4)

The complete routing context from MS until GGSN is established, activation is com-
pleted successfully. Packet data can now be transmitted.

Network Requested PDP Context Activation Procedure

PDP context activation can also be initiated by the network.
(A) If a new PDP Packet Data Unit PDU reaches the GGSN, the latter checks
whether a PDP context is activated.
(B) If there is no PDP context, the GGSN needs routing information (IMSI, SGSN
address, Mobile Station Not Reachable Reason) from the HLR.
(C) The GGSN contacts the SGSN (IMSI, PDP type, PDP address).
(D) The SGSN request the MS to activate the corresponding PDP context. Then the
PDP context activation procedure (see above) is carried out.

48 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

PDP Context Activation

MS SGSN HLR GGSN
PDP PDU
Send Routing
Info for GPRS A
Network Requested B
Send Routing Info for
PDU Notification GPRS Ack (SGSN Address,
Request IMSI, MS Not Reachable Reason)
C
Request PDU Notification
D PDP Context Activation
Response

Activate PDP Context Request

1
Normal / MS Requested
Security functions
2
(if necessary)
Create PDP Context Request

3 Create PDP Context Response

Activate PDP Context Accept

4

Fig. 24 PDP context activation procedure may be either requested by the MS or by the network

TM2110EU01TM_0003
49
 Siemens Interfaces, Protocols, Procedures

3.6 Start of Mobile Originated Packet Transfer

An MS initiates a packet data transfer in a „One or Two Phase Packet Access“
method. If the GPRS subscriber uses a RACH to send a channel request only 8 bit
are usable to indicate which service is requested. In case of a random access carried
out on a PDCH 11 bit are reserved for the identification of the request. This speeds
up the call set-up by avoiding two phase packet accesses.

One Phase Packet Access

(1) Packet Channel Request: this serves as a starting point of the packet data trans-
fer in an activated MS and is realized via random access channel RACH or via
packet RACH. The message contains a brief information about the resources needed
for the transfer.
(2) Packet Immediate Assignment: is used for allocation of UL resources to one /
several packet data channel(s) PDCH(s) for a number of radio blocks. The packet
immediate assignment message is realized via an access grant channel AGCH or
packet AGCH (PAGCH). The timing advance derived from the received PRACH and
RACH respectively and an information about the MS power control are communi-
cated to the MS as well.

Two Phase Packet Access

If the allocated resources do not have the requested quality of service, (e.g. only 1
time slot allocated), the MS can end the one phase access and initiate a two phase
access. Upon (1) and (2) the MS sends to the network message a complete descrip-
tion of the resources needed for the UL transfer with the
(3) packet resource request.
(4) packet resource assignment: The network confirms the resource request. The
message contains information about the resources allocated in each case. (3) and (4)
are realized via the packet associated control channels PACCH.

The data transfer, i.e. transport of RLD blocks, can now begin. The RLC data is real-
ized as packet data traffic channel PDTCH.

50 TM2110EU01TM_0003
Interfaces, Protocols, Procedures Siemens

Start Packet data transfer

MS Network

Packet Channel Request

1 PRACH or RACH One Phase
Packet Immediate Assignment (TA, PC)
Packet Access
2 PAGCH or AGCH

Packet Resource Request

3 PACCH Two Phase
Packet Access
Packet Resource Assignment
4 PACCH (optional)

RLC Data Transfer

RLC block
4 PDTCH
RLC block

·
·
·

Fig. 25 Start of packet data transfer

TM2110EU01TM_0003
51
 Siemens Interfaces, Protocols, Procedures

52 TM2110EU01TM_0003