Intro To Edge-Gprs

Introduction to GPRS and EGPRS
Introduction to GPRS and EGPRS/EDGE
Alcatel-Lucent File Reference Date Edition Page

GDEGPRE5.DOC 3DC 21084 0003 TQZZA 05/2003 05 1
All rights reserved. Passing on and copying of this document, use and communication of its contents not permitted without written authorization.
CONTENTS
1. SCOPE ......................................................................................... 3
2. SETTING THE SCENE ........................................................................ 4
2.1 Acronyms............................................................................................................. 4
2.2 Why all that effort ? ............................................................................................... 6
3. GPRS/EGPRS ARCHITECTURE .............................................................. 7

3.1 Overview ............................................................................................................. 7
3.2 GPRS network elements .......................................................................................... 9
4. NOW, HOW DOES IT WORK ? .............................................................11

4.1 The processes..................................................................................................... 11
4.2 Logical and physical channels ................................................................................. 15
4.3 The protocol stack ............................................................................................... 20
5. THE PHYSICAL LAYER......................................................................25

5.1 Modulation schemes ............................................................................................. 25
5.2 Coding schemes................................................................................................... 29
6. NETWORK COVERAGE AND THROUGHPUT .............................................35

6.1 Some basics........................................................................................................ 35
6.2 GPRS and EGPRS performance................................................................................. 36
6.3 How to plan a GPRS/EGPRS network ......................................................................... 42
7. TRAFFIC ASPECT ...........................................................................47

7.1 What is the difference to speech transmission ?.......................................................... 47
7.2 Multi-Service Traffic Model .................................................................................... 47
7.3 Mobile station capabilities ..................................................................................... 49
8. INTERFACES AND TRANSMISSION ASPECTS ............................................50

8.1 Capacity aspect for the Abis interface ...................................................................... 50
8.2 Transmission management on the Ater interface ........................................................ 50
8.3 The Gb Interface ................................................................................................. 50
9. LITERATURE .................................................................................53
10. LIST OF ABBREVIATIONS ..................................................................54
Notice of proprietary information

This document contains proprietary technical information belonging to Alcatel. By accepting this
material, the recipient agrees that this material will not be reproduced or used in whole or part
except as otherwise agreed between Alcatel and the recipient.
Subject to change without notice.

1. SCOPE
The following document provides a first introduction to GPRS and EDGE (EGPRS). In order to ease
the reading, some simplifications are made. Sometimes, the GSM recommendations specify several
possibilities for certain functions. This document does not cover all these alternatives, but is
restricted to the most commonly implemented ones.
The know-how acquired by working through this paper shall enable the reader to better
understand other documents going further into details.
This document can be grouped into four parts:
The first part (chapter 2) is setting the scene: It introduces the acronyms related to data
services offered for GSM network evolutions and gives some rationales for GPRS / EGPRS.
The second part (chapter 3 to 5) describes the GPRS / EGPRS system from top to bottom:
Starting with the network architecture, via an overview of the processes going on in GPRS /
EGPRS, the protocol stacks are introduced. This part ends with describing the physical layer.
The third part (chapter 6 and 7) gives a first insight into network performance and planning
aspects, from a coverage / throughput aspect as well as from a traffic aspect.
The fourth part (chapter 8) gives a short introduction to the transmission aspects.
For the interested reader, recommendations on further documents are provided in chapter 9. A list
of abbreviations is appended at the end of the document.
A reasonable knowledge of telecommunications and conventional (circuit-switched) GSM systems is

required to fully understand this document.
Please note that this document contains preliminary information:
Performance indications are partially based on simulations and need to be verified in real
hardware.
This document does not give any commitments of Alcatel on product parameters and
availability schedules.

2. SETTING THE SCENE
2.1 Acronyms
GPRS stands for General Packet Radio Service. This packet data service is introduced into GSM
networks in addition to the old fashioned circuit switched services. GPRS provides a true, end-
to-end packet-switched transmission.
Two steps for the GPRS-introduction are distinguished: Step 1 with the (slower) coding schemes
CS-1 and CS-2, and Step 2 with the additional coding schemes CS-3 and CS-4 (higher throughput).
Later in this document, you will find more information on CS-1 to CS-4.
With GPRS, a new entity is

Urban areas
introduced into the radio
network: The Packet Circuit
BTS Core
Control Unit (PCU), realized Network
BSC
in Alcatel networks by the G2
A
Multi-BSS Fast packet BTS T
C
Server (MFS). This entity Suburban areas
contains the major part of BSC MFS Gb

G2 IP
the "GPRS-intelligence"
BTS Core GGSN
within the BSS and controls SGSN
Network
all packet data related
processes. For the rest of the BSS, GPRS is just software.
A packet data core network consisting of the Serving GPRS Support Node (SGSN) and the Gateway
GPRS Support Node (GGSN) is complementing the circuit switched core-network mainly consisting
of the MSC/VLR.
HSCSD stands for High Speed Circuit Switched Data. For a HSCSD connection, more than one time-
slot in a time-division multiple access (TDMA) frame is assigned exclusively to one user. This allows
to offer circuit-switched data services with higher bit-rates.
EDGE stands for Enhanced Data rates for GSM Evolution. EDGE is a concept of improving data
rates in GSM systems. This definition is the headline for all possible applications, let it be circuit-
or packet-switched services including architectural issues, all protocol levels etc. With EDGE, a
new modulation scheme on the Air interface (called 8PSK) is introduced, which allows higher
throughput while maintaining the existing bandwidth and time-division multiple access (TDMA)
structure of GSM.

EGPRS stands for Enhanced General Packet Radio Service. This is nothing else than the application
of GPRS within EDGE: A Packet data services with a higher bit rate.
ECSD is the acronym for EDGE Circuit Switched Data. This is the application of EDGE for circuit
switched traffic applications and could be the evolution of HSCSD. Using 8PSK modulation, data
rates of 28.8 and 32 kbit/s per timeslot in transparent mode, 28.8 and 43.2 kbit/s in non-
transparent mode are available. This service has so far only met limited interest from network
operators and is therefore not further considered in this document.
GERAN stands for GSM/EDGE Radio Access Network. GERAN combines all the GSM services as
described before:
GSM
GSM (voice and circuit-switched data)
(voice and circuit-switched data)
GPRS
GPRS
GERAN
GERAN
HSCSD
HSCSD
EGPRS
EGPRS
EDGE
EDGE ECSD
ECSD

2.2 Why all that effort ?
Because of the Internet. There are big expectations on the potential of

Internet services (Internet including World Wide Web www, e-mail,
Intranet and the like) offered to mobile subscribers.
The good old circuit switched mode of data transmission is not very well
suited to the bursty way the data actually flow between the end-user and
the network.
A packet mode transmission allows other users to reuse the transmission

resources while you are reading the page just downloaded from the
Internet. This even without urging you to disconnect, reconnect,
disconnect, ... GPRS is a real Always On service.
And, quite important, only the actual transmitted data have to be billed
to the subscriber, thus offering a much more affordable way for mobile
Internet surfing.
These are the reasons behind the idea of the General Packet Radio
Service GPRS. This service improves already the data capability of GSM
remarkably.
A further way to increase the speed was found: The use of a new
modulation scheme, named EDGE in combination with GPRS: EGPRS.
The ultimate evolution step will be the availability of services similar to

all you ever expected (and a lot you never expected) from UMTS. The
limitation is just the bandwidth available to the operators (yes, we still
need UMTS ! ).
But what is ultimate ? Some engineers already started discussing about

adding new modulation schemes to GSM allowing even higher data rates
...

3. GPRS/EGPRS ARCHITECTURE
3.1 Overview
The technical solution adopted by ETSI for the GPRS / EGPRS service is based on the common use
of the BSS by circuit and packet-switched services and the introduction of new logical network
entities:
Serving GPRS Support Node (SGSN),
Gateway GPRS Support Node (GGSN),
Packet Control Unit (PCU), in the Alcatel implementation supported by the A935 MFS (Multi-
BSS Fast Packet Server),
GPRS Backbone Network.
The following figure shows the architecture of a GPRS / EGPRS capable network on the example of
the Alcatel implementation with the Multi-BSS Fast Packet Server MFS:
A PTSN
MSC
TC ISDN
VLR
Abis Ater
BTS BSC
MFS
BTS (PCU)
Abis HLR
AuC
BTS
Gb
Packet-switched services Gn GPRS Gi Internet

SGSN backbone GGSN X.25
Circuit-switched services
Mixed packet- and circuit-
switched services
GPRS / EGPRS services use the same BSS architecture as circuit-switched services. Packet-switched
services are routed via Gb and Gn interfaces to SGSN and GGSN prior to interconnection with the
terminating IP- or X.25 based Packet Data Networks (PDNs).
The ETSI specifications allow to combine the SGSN and GGSN in the same physical node or to
implement them in different physical nodes with an IP-based backbone providing interconnection.
The latter option is adopted by Alcatel.

The Home Location Register HLR holds GPRS-specific subscriber information. It provides them to
the SGSN at the instant of a mobile attaches to GPRS services.
The complete overview of all network elements and all interfaces related to GPRS/EGPRS is given
here:
SMS-GMSC
Short Message Service Gateway-MSC SMSC
Short Message
SMS-IWMSC Service Center
Short Message Service - Interworking MSC
E C
MSC/VLR D HLR/AuC
Mobile Switching Center Home Location Register
Visitor Location Register Authentication Center
Gd
Gc
A Gs
Gr
R Um Gb Gn Gi
TE MT BSS SGSN GGSN PDN TE
Terminal Mobile Base Station Serving GPRS Gateway GPRS Terminal
Packet Data Network
Equipment Termination System Support Node Support Node Equipment
Gn Gf
SGSN
Gp EIR
Equipment
Serving GPRS Identification Register
Support Node
GGSN
Gateway GPRS
Support Node
Data and signalling transfer
Other PLMN
Public Land Mobile Network Signalling transfer
Some of the elements and associated interfaces are optional. Examples (not exhaustive):
Equipment Identification Register EIR with interface Gf, or the Short Message Service Center SMSC
with interface Gd.

3.2 GPRS network elements
3.2.1 Alcatel BSS solution
In the BSS, the Packet Control Unit (PCU) is responsible for the lower layer functions on the Um
interface (Radio Link Control and Medium Access Control):
Protocol Data Unit (PDU) segmentation/re-assembly,
Channel access control,
Radio channel management,
Packet Data Channel (PDCH) scheduling,
Transmission error detection,
Automatic request for repetition (ARQ).
The BSC is used for circuit versus packet radio resource allocation and supports Common Control
Channel (CCCH) based GPRS paging, access request and access grant.
Alcatels solution for the BSS part of GPRS is based on no hardware changes to any existing BSS
equipment. Consequently, the key GPRS functions are split between the BTS (only software
upgrade) and the new Multi-BSS Fast packet Server (A935 MFS) located at the transcoder site.
A
TC
Abis Ater
BTS BSC
MFS Gb
BTS (PCU)
Abis
BTS
The only difference for EGPRS service is the requirements for EDGE-capable transceivers in the
BTSes, and likely capacity extensions to the BSC and the transmission network. A BTS can be
equipped with a mixture of normal and EDGE-capable transceivers. The network can consist of a
mixture of normal and EDGE-capable BTS.
The A935 MFS is based on redundant IT (Information Technology) platforms for control aspects and
dedicated Digital Signal Processor boards (known as GPUs) for Gb-interface termination and the
Packet Control Unit (PCU) function. A single MFS can be shared by several BSCs (controlled by the
same OMC-R) terminated at the same MSC site, and its capacity can be incrementally increased to
match GPRS / EGPRS traffic build-up.

3.2.2 Alcatel NSS solution
Serving GPRS Support Node
The heart of the GPRS NSS is the SGSN that plays the central role in managing all GPRS and
EGPRS capable mobile stations within the network.
The basic functions of the SGSN are interfacing to BSS over the Gb interface and to GGSN over
the Gn or Gp interface, mobility management, paging, encryption, data compression, traffic
measurement and charging.
The SGSN detects new GPRS / EGPRS Mobile Stations (MS) in its service area and handles the
process of registering the new MS along with the GPRS registers. It transmits /receives data
packets to/from the GPRS / EGPRS mobile. Records of the location of MS inside of its service
area are kept by the SGSN.
Gateway GPRS Support Node:
The GGSN provides interaction with the external Packet Data Network (PDN).
It transmits/receives data packets from SGSN or PDN. GGSN interfaces to SGSN over Gn or Gp
and to PDN over Gi interface. GGSN updates the location directory using routing information
supplied by the SGSN about the MSs path.
It handles the routing of encapsulated external PDN protocol packets over the GPRS backbone
to the target SGSN that serves the terminating MS and the external PDN.
The charging traffic data to/from external PDNs are registered and handled by the GGSN.

4. NOW, HOW DOES IT WORK ?
The precondition for a subscriber to make use of GPRS / EGPRS services is a subscription with a
service provider or a network operator for certain packet data services. The subscription is related
to one or more Packet Data Protocol (PDP) addresses.
Some examples for such addresses: z The gateway of the GSM-network to the
Internet
z A WAP-server for services offered by the

GSM-operator
z An e-mail server
Each Packet Data Protocol (PDP) address is described by an individual PDP context in the mobile,
the SGSN and the GGSN.
In the following, a simplified description on what is going on in a GPRS / EGPRS network for packet
data transmission is given.
4.1 The processes
Three logical management entities are sharing the tasks of controlling packet data services:
The Session Management (SM)
The GPRS Mobility Management (GMM)
The Radio Resource Management (RRM)
In the following simplified process description, the responsible entities are indicated.
4.1.1 Connecting to GPRS
In order to receive service, a mobile needs to be known as active by the network. For circuit-
switched traffic, this is automatically done when switching-on the mobile: A so-called Location
Update is performed. The Visitor Location Register (VLR) and the Home Location Register (HLR)
are informed about the present location of the mobile and its capabilities.
For packet data services, the mobile needs to register with the network as well. This is, however,
not necessarily done by switching-on of the mobile (it could be done automatically, though).

In order to prepare the mobile and the network for a packet data exchange (i.e. to establish a
session), two main activities have to be performed:
Initiation of a session (Session management SM)
Activation of a Packet Data Protocol (PDP) context (SM)
As the first step, the mobile notifies the Serving GPRS Support Node SGSN. The network checks the
access rights of the mobile (to be precise, the subscriber identity stored in the SIM), copies the
subscriber specific data from the HLR to the SGSN and assigns a Packet Temporary Mobile
Subscriber Identity P-TMSI to the mobile. During this activity, the SGSN and the HLR are informed
about the location of the mobile on a cell level.
This process is associated with the GPRS Attach (GMM). It changes the (GPRS-) Mobility
Management State of the mobile from IDLE to READY (GMM). In the READY state, the mobile
continues to inform the SGSN about all changes in its location on a cell level.
Now, the mobile can apply for one or more Packet Data Protocol (PDP) addresses (SM). Each PDP
address is described by a PDP context, which includes:
The PDP type (IPv4 for example)
The PDP address of the mobile
The requested Quality of Service (QoS) class (presently only Best Effort supported, QoS
handling is only specified in GERAN R5)
The address of the GGSN, which acts as the access point to the respective packet data
network
This PDP context is stored in the mobile, the SGSN and the GGSN.
Upon reaching the READY state (GMM) and activation of at least one PDP context (SM), the mobile
is visible to the outside packet data network PDN and can sent and receive packet data. The
Mobility Management State remains READY regardless if radio resources are allocated or not and if
data is transferred or not. But not for ever: If the READY-timer expires, the mobile goes to the
STANDBY state (more later in chapter 4.1.2).
The mobile can establish several PDP context in parallel. This allows the mobile to communicate,
for example, with the Internet and a Public Switched Packet Data Network PSPDN at the same
time.
While in the Mobility Management State READY, two different Radio Resource (RRM) states are
possible for the mobile:
The Radio Resource state Packet idle mode (not to be mixed-up with the Mobility Management
State IDLE). The mobile listens to the broadcast control channel and the paging sub-channel.
The Radio Resource state Packet transfer mode. A Temporary Block Flow (TBF) is established.
The sub-chapter 4.1.3 below is dedicated to this state.

4.1.2 The STANDBY state
If no packets are transferred for a while, the READY-timer expires and the mobile falls into the
Mobility Management State STANDBY (GMM). The changes:
In the STANDBY state, the location information in the SGSN is only maintained on a Routing
Area (RA) level. A Routing Area (RA) consists normally of several cells. The minimum is one
cell, the maximum the same cells as defined for the Location Area for the circuit-switched
services.
If a packet data exchange shall take place, first a paging for the mobile in the respective
Routing Area has to be performed. The paging answer changes the MS state from STANDBY to
READY (GMM).
While in the Mobility Management State STANDBY, only the Radio Resource state Packet idle mode
exists. The mobile is still visible to the outside packet data network PDN.
4.1.3 Temporary Block Flow
If packet data units are to be transmitted, the mobile enters the Radio Resource state Packet
transfer mode (RRM) and sets up a temporary physical connection on the radio interface: The
Temporary Block Flow (TBF).
A summary:
A TBF is an uni-directional link.
A Temporary Block Flow can be initiated by either the mobile or the network.
Several modes of TBF establishment in uplink and downlink exist. More details can be found in
GSM 03.60 and GSM 03.64.
Radio resources on one or more Packet Data Channels (PDCH) are allocated to one TBF.
The TBF is, as its name suggest, only temporary and maintained for the duration of the data
transfer.
A TBF is addressed by a Temporary Flow Identity (TFI). The TFI is managed by the Packet
Control Unit PCU, the Multi-BSS Fast Packet Server MFS respectively.
An example: During an Internet session, the user clicks on a hyperlink. This action
initiates a short data portion to be transmitted from the mobile to the Internet
server. In order to transport this packet, an uplink TBF is established and addressed by
a Temporary Flow Identity (TFI). After this data portion is completely delivered, the
uplink TBF is terminated, the TFI and the radio resources are available for another
user.

As a response, the Internet delivers, for example, the next page to which the hyperlink
refers. A downlink TBF is established and addressed by another TFI. This TBF is
maintained until the page is completely delivered and then terminated, the TFI and
the radio resources are then free for another user. While the user is reading this page,
no TBF is active for this user.
A typical user session, in which data is exchanged bi-directionally as in the example above,
requires the establishment and termination of several TBFs in each direction. The user, however,
has the impression of a continuous end-to-end dialogue. Such a set of uplink and downlink TBFs is
also called "transaction".
Uplink TBF TBF
Downlink TBF TBF
Transaction
Depending on the mobile capabilities (more to come on that issue in chapter 7.3), TBFs on uplink
and downlink can be active simultaneously.
4.1.4 What about handovers ?
There are no handovers for GPRS / EGPRS mobiles (at least not in the near future). Roaming to
other cells is performed by cell (re)-selection.
When a mobile in packet transfer mode leaves the coverage range of a BTS or suffers from
interference, the link quality will degrade and retransmission will be activated. If the mobile
detects another cell with a better field-strength, the temporary block flow (TBF) is interrupted,
the mobile changes into the Packet idle mode, selects a new cell, reads the system information,
enters the Packet transfer mode and sets up a new TBF.
The cell re-selection is done by the mobile autonomously by measuring the received field-strength
of the Packet Broadcast Control Channels PBCCH of its own and neighboring cells (the field-
strength of the "circuit-switched" Broadcast Control Channel BCCH, in case no PBCCH is available).
More about these logical channels comes in chapter 4.2.1 below. This mode is called NC0.
A little bit later in the product evolution, the feature Network Controlled Cell Reselection (called
NC2) is planned, both for GPRS and EGPRS. Upon activation of this feature and in case the
mobile is in the READY state (GMM), the mobile station does no longer perform cell reselection
autonomously, but sends measurement reports to the network. The network controls the cell
reselection.

The main goal of NC2 is to reduce the number of cell re-selection. Each time there is a cell re-
selection in packet transfer mode, the interruption can be quite significant for the application
level. NC2 allows to maintain a TBF in a cell as long as reasonably possible, therefore improving
the total throughput on the application layer.
In addition, NC2 can be used to push an (E)GPRS-mobile to another cell (for example for traffic
load reasons), given the coverage overlap is sufficient.
4.1.5 Some more key features in short
Discontinuous reception (DRX) is still possible with GPRS and EGPRS.
Uplink power control is provided for GPRS and EGPRS.
Frequency hopping is possible for GPRS and EGPRS.
Ciphering for the packet data is used. In contradiction to circuit-switched voice or data,
where ciphering/de-ciphering for the network side is performed in the BTS, for GPRS/EGPRS
this is handled by the SGSN.
4.2 Logical and physical channels
4.2.1 Logical channels
Similar as defined for voice services, different logical channels are defined for GPRS / EGPRS.
These channels are classified into traffic channels and control channels. Some channels are bi-
directional, other channels are uni-directional. An overview:
Group Class Name Function Direction
Traffic channels Packet Data Traffic PDTCH Packet Data Traffic MSBSS
Channel
Control channels Packet Broadcast Control PBCCH Packet Broadcast Control MSBSS
Channel *)
Packet Common Control PRACH Packet Random Access MSBSS

Channel (PCCCH) *)
PAGCH Packet Access Grant MSBSS
PPCH Packet Paging MSBSS
Packet Dedicated Control PACCH Packet Associated Control MSBSS

Channel
PTCCH Packet Timing Advance Control MSBSS
*) PBCCH and PCCCH capability is mandatory for mobiles, optional for the network.
Table 1: Logical Channels

The function is analog to the logical channels defined for voice service and for the reader probably
self-explaining. New is the Packet Timing Advance Control Channel PTCCH. In the uplink, the
mobile transmits a random access burst (one mobile per PTCCH). In the downlink, the network
transmits timing advance information to the mobiles (several mobiles per PTCCH).
4.2.2 Coordination between packet-switched and circuit-switched services
After introduction of GPRS, mobiles can be attached to two types of services (GSM circuit-switched
and GPRS packet-switched). In that case, they have to receive paging messages for both types.
Three different modes of coordination between paging, called Network Mode of Operation
(NMO), are defined:
NMO I MPDCH used. Paging coordination between CCCH and PCCCH. Mobile needs only to
monitor one paging channel. If attached to GPRS, circuit-switched paging messages
are transmitted on the PDCH. Interface Gs between MSC/VLR and SGSN is required.
NMO II MPDCH not used. Paging for circuit- and packet switched services always on CCCH.
Interface Gs between MSC/VLR and SGSN not required.
NMO III MPDCH used. No paging coordination between CCCH and PCCCH. If attached to GPRS,
the mobile needs to monitor both circuit- and packet switched paging channels.
Interface Gs between MSC/VLR and SGSN is not required.
Recommendation on use of Network Mode of Operation:
NMO I Medium to high data usage
High performance (fast TBF establishment) required
NMO II First phase of GPRS rollout
Low data usage
Compromise on performance acceptable
NMO III Not recommended, as not all mobiles can monitor CCCH and PDCCH
simultaneously

4.2.3 Physical channel: The Packet Data Channel (PDCH)
One physical Packet Data Channel (PDCH) consist of one radio timeslot on the Air interface. Four
bursts from four consecutive TDMA frames are combined to form a radio block:
One TDMA frame

= 8 TS (4,615 ms)
0 1 2 3 4 5 6 7
One PDCH
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 47 48 49 50 51
Block B0 Block B1 Block B2 T Block B3 Block B11 X

PTCCH idle
One 52-multiframe (240 ms)
Up to eight Packet Data Traffic Channels (PDTCH) (in the first software releases limited to five due
to mobile constraints) on different time-slots but the same transceiver can be allocated to one
mobile at the same time (depending on the multi-slot capabilities of the mobile). Several mobiles
can share the same PDCH.
An example:
User 1:
no multislot
capability
PDCH 1 User 2 User 2 User 3 User 3 User 2 User 2
User 2:
with multislot
capability

User 3:
with multislot
capability Block n n+1 n+2 n+3 n+4 n+5 ...
It is possible, to mix GPRS and EGPRS on the same Packet Data Channel (PDCH).

Up to 16 users can share a Packet Data Channel (PDCH). The Alcatel implementation allows a
maximum of seven users in uplink plus nine users in downlink for the initial release. In later
releases, a maximum of six users in uplink plus ten users in downlink can share one PDCH.
Depending on what logical channels are conveyed on a PDCH, it is named:
Primary Master Packet Data Channel (primary MPDCH). PDCH carrying PBCCH and PCCCH.
Minimum 0, maximum 1 per cell.
Secondary Master Packet Data Channel (secondary MPDCH). PDCH carrying PCCCH. Minimum 0,
maximum 15 per cell. Only exists when primary MPDCH is available.
Slave Packet Data Channel (SPDCH). PDCH carrying PDTCH and PACCH, but neither PBCCH nor
PCCCH. Minimum 0, maximum only limited by equipped resources.
The specification allows to multiplex also PDTCH on primary and secondary MPDCH to squeeze out
some more capacity in case the MPDCH is only partially used. The benefit is in reality very limited
compared to the complexibility of this feature. This option is therefore usually not implemented.
Timeslots usable for PDCH are grouped into PDCH groups. One PDCH group contains time-slots
belonging to the same TRX, having the same frequency configuration without holes (= consecutive
timeslots).
4.2.4 Dynamic Packet Data Channel (PDCH) allocation
An important feature in the Alcatel implementation of GPRS/EGPRS is the PDCH Dynamic

allocation. This feature allows to use the same timeslots both for circuit-switched and GPRS
traffic depending on the demand.
The network entity in charge of the coordination between circuit-switched and GPRS traffic is the
MFS. The MFS sents PDCH allocation and de-allocation requests to the BSC, which is in charge of
the execution of such requests. BSC circuit switched traffic load is indicated from the BSC to the
MFS.
There are a number of parameters to tune the dynamic PDCH allocation. They can be controlled by
the operator from the OMC. Some highlights:
An absolute upper limit for the number of PDCH can be set to guarantee the quality of service
for voice.
If circuit-switched services get priority over GPRS, the upper limit for the number of PDCH can
be configured to be dynamically adapted to the traffic situation. Under high traffic load
situation for circuit-switched services, the upper limit for PDCH can be reduced to make room
for more voice calls. There are two possibilities to react on high traffic load:
- A slow mechanism using soft pre-emption to react on normal changes of the traffic
profile. The traffic evaluation period = reactivity is about 15 seconds.

- A fast mechanism using fast pre-emption to react on sudden voice traffic peaks. Even if all
timeslots are occupied by circuit- and packet-switched traffic, a new circuit-switched
request will be served. One PDCH will be cleared immediately, its traffic resumes on other
PDCH with a lower total performance.
A minimum number of PDCH timeslots can be configured to guarantee a minimum performance

for GPRS/EGPRS. These timeslots are not available for circuit-switched services, even if no
GPRS transactions are ongoing. The value for the minimum number of PDCH timeslots can be
set to 0.
4.2.5 Master Packet Data Channel (MPDCH) allocation
The primary MPDCH (NMO I or NMO III) is allocated statically. The MPDCH is allocated per command
from OMC and stays on its timeslot permanently. The advantage: Improved TBF handling available
permanently.
The secondary MPDCH can be enabled or disabled. It can only be enabled, if a primary MPDCH is
allocated. If it is enabled, it can only be allocated dynamically. The maximum number of
secondary MPDCH can be limited by O&M settings.
4.2.6 Mapping of uplink Packet Data Channels: The Uplink State Flag
With GPRS / EGPRS, we have now the situation, that several subscribers share the same physical
resources. For the downlink, the mobile has just to wait for the data addressed to it, but what
about the uplink Packet Data Traffic Channel PDTCH and Packet Associated Control Channel PACCH
?
In order to tell the mobile, when it is allowed to use the Packet Data Channel (PDCH), the Uplink
State Flag USF has been invented.
This flag consists of three bits and is contained in the header of the preceding RLC/MAC block
transmitted in downlink on the same PDCH. If several PDCHs are allocated to a multislot-capable
mobile, each PDCH gets its Uplink State Flag. If the mobile reads his value in the Uplink State
Flag, it is allowed to use the next uplink block on the PDCH.
If a mobile can not decode the Uplink State Flag USF correctly, it can not use it's radio block.
You will therefore find this Uplink State Flag USF regularly mentioned as reference in radio
performance related articles and specifications.

4.3 The protocol stack
4.3.1 Introduction
A rather good way to show the split of responsibilities within a GPRS / EGPRS network is the
protocol stack. This chapter shall give a very brief introduction to the most interesting protocol
stacks used for GPRS and EGPRS. The emphasis is put on the air interface (the Um interface).
Two protocol-stacks have to be considered:
The transmission plane. This plane shows how the data travels through the network.
The control plane. This plane shows the way of control and signaling information.
4.3.2 Transmission plane
The complete protocol-stack including the example of surfing the world wide web is shown below:
www
Application example
World Wide Web
http
Hypertext Transfer
Protocol
TCP
Transmission Control
Protocol
RFC 793
IP IP
Internet Protocol
Internet Protocol
RFC 791
RFC 791
relay
SNDCP SNDCP GTP
Subnetwork
Subnetwork GTP GPRS Tunneling
Dependent GPRS Tunneling
Dependent Protocol
Convergence Protocol
Convergence GSM 09.60
Protocol GSM 09.60
Protocol
GSM 04.65
GSM 04.65
LLC LLC UDP UDP

User Datagram User Datagram
Logical Link Control Logical Link Control Protocol Protocol
GSM 04.64 GSM 04.64 RFC 768 RFC 768
or: or:
TCP TCP
relay Transmission Control Transmission Control
RLC Protocol Protocol
RFC 793 RFC 793
Radio Link Control
GSM 04.60
RLC BSSGP BSSGP
Radio Link Control
GSM 04.60
BSS GPRS Protocol BSS GPRS Protocol IP IP
Internet Protocol Internet Protocol
GSM 08.18 GSM 08.18
RFC 791 RFC 791
MAC MAC Ethernet Ethernet
Medium Access Medium Access
Control Control NS NS FR FR
GSM 04.60 GSM 04.60 Frame Relay Frame Relay
Network Service Network Service
GSM 08.16 GSM 08.16 or: or:
relay L2-GCH
Physical ATM ATM
Physical L2-GCH Layer 2 GPRS Asynchronous Asynchronous
Link Layer Layer 2 GPRS Channel Transfer Mode Transfer Mode
Link Layer Channel
L1bis L1bis and/or: and/or:
Physical Physical L1-GCH L1-GCH Layer 1bis
Layer 1 GPRS Layer 1 GPRS GSM 08.14
Layer 1bis
GSM 08.14
E1 (PCM30) E1 (PCM30)
RF Layer RF Layer Channel Channel G.703 / G.704 G.703 / G.704
MS Um BTS Abis / Ater MFS Gb SGSN Gn GGSN Gi
The blocks highlighted in orange (left from the Gb interface and up to the RLC/MAC layer) are
managed by the BSS and the green ones (right hand from the Gb interface and up to the IP layer)
by the Core Network. Grey blocks (above the IP layer) are examples of external applications, for
which the GSM/GPRS/EGPRS network is transparent. Some explanations are given in chapter 4.3.4
ff.

4.3.3 Control plane
Two different modes are provided as mentioned in chapter 4.2.1 above:
In the first mode, the network uses the existing signaling resources of the circuit-switched
channels (the Common Control Channel CCCH) to establish packet data connections.
The second mode introduces separate signaling channels for packet data. These channels are
called Packet Broadcast Control Channel PBCCH and Packet Common Control Channel PCCCH.
The complete protocol-stack of the control plane is shown below on the example of the second
mode:
GMM/SM GMM/SM
GPRS Mobility GPRS Mobility
Management/ Management/
Session Session
Management Management
LLC LLC
Logical Link Control Logical Link Control
GSM 04.64 GSM 04.64
relay
RLC BSSGP BSSGP
Radio Link Control
GSM 04.60
RLC BSS GPRS Protocol
BSS GPRS Protocol
Radio Link Control
GSM 08.18
GSM 04.60 GSM 08.18
MAC MAC
Control Control NS NS
GSM 04.60 GSM 04.60 Network Service Network Service
GSM 08.16 GSM 08.16
relay L2-GCH
Physical
Physical L2-GCH Layer 2 GPRS
Link Layer Layer 2 GPRS Channel
Link Layer Channel
L1bis L1bis
Physical Physical L1-GCH L1-GCH Layer 1bis Layer 1bis
Layer 1 GPRS Layer 1 GPRS GSM 08.14 GSM 08.14
RF Layer RF Layer Channel Channel
MS Um BTS Abis / Ater MFS Gb SGSN

4.3.4 The "tunnels"
The user data of the application is transported using tunneling. The packets of one protocol are
encapsulated within packets of an underlying protocol. This process is totally transparent for the
application protocol. The advantage is that the applications do not need to be modified for the
specific mechanism of GPRS. That means GPRS/EGPRS can transmit everything that is called data
packet, even protocols which are not yet invented.
There are two parts of the tunnels:
The backbone-part, the GPRS Tunneling Protocol GTP
The radio-part, the SubNetwork Dependent Convergence Protocol SNDCP
relay
SNDCP SNDCP GTP
Subnetwork Subnetwork GTP
Dependent Dependent GPRS Tunneling GPRS Tunneling
Convergence Convergence Protocol Protocol
Protocol Protocol GSM 09.60 GSM 09.60
GSM 04.65 GSM 04.65
MS Um BTS Abis / Ater

MFS Gb
SGSN Gn
GGSN Gi
The tunnels are established upon the PDP context activation.
The backbone-part, the GPRS Tunneling Protocol GTP, is set up between the GGSN (the fixed part
in all matters relating to a certain data service) and the SGSN. If the mobile leaves the area served
by the SGSN, a new GTP tunnel is established between the GGSN and the new SGSN. For each PDP
context, one GTP tunnel is established.
The GPRS Tunneling Protocol GTP is defined for the Gn-interface between SGSN and GGSN within
one network and for the Gp-interface between the SGSN in one network to the GGSN in another
network.
The radio part, the SubNetwork Dependent Convergence Protocol SNDCP, is the "mobile" part of
the tunnel. It follows the mobile to each cell. If several PDP contexts are activated at the same
time, the SubNetwork Dependent Convergence Protocol SNDCP multiplexes all of them onto a
single logical connection of the Logical Link Control LLC layer. User data and redundant header
data are compressed by the SNDCP to save precious Air interface resources.

4.3.5 The Data Link Layer LLC and RLC/MAC
The data link layer between the mobile and the BSS is divided into two sub-layers:
The Logical Link Control LLC
The Radio Link Control / Medium Access Control RLC/MAC
LLC LLC
Logical Link Control Logical Link Control
GSM 04.64 GSM 04.64
relay
RLC RLC
Radio Link Control Radio Link Control
GSM 04.60 GSM 04.60
MAC MAC
Control Control
GSM 04.60 GSM 04.60
MS Um BTS Abis / Ater MFS Gb SGSN
The Logical Link Control LLC provides a highly reliable logical connection between the mobile and
the SGSN. The functionality includes:
Flow control
Provision of data packets in the correct sequence
Error detection
Automatic repetition of erroneously received packets (Automatic Repeat Request ARQ)
Support of different Quality of Services QoS classes
Support of acknowledged and unacknowledged operation
Ciphering of data, user confidentiality
The functionality is based on the LAPDm protocol, which is a High-Level Data Link Control HDLC
derivative (just for the protocol experts of you).
The Radio Link Control RLC is responsible for
Segmentation of the data units to be transferred into radio blocks which will be transmitted in
four subsequent bursts in a PDCH (you remember, we have seen this in chapter 4.2.3 above)
Link adaptation, the dynamic selection of the modulation and coding scheme taking into
account the measured channel quality (you will find more about this later in the document)
The error correction by selective retransmission of erroneous blocks (Automatic Repeat

Request ARQ)

The Medium Access Control MAC is in charge of
the access control to the radio channel. MAC uses paging and random access messages to
control the access to the radio transmission resources. It handles the connection attempts of
several mobiles onto a common resource and the multiplexing of multiple users onto a
common Packet Data Traffic Channel PDTCH.
Queuing of access requests and assignment of resources.
Scheduling of radio block transmission.
In case of different Quality of Service QoS classes, the MAC protocol reserves resources to
ensure the guaranteed service quality.
The MAC protocol used for GPRS / EGPRS is based on the slotted-ALOHA technology as used for
MAC in the GSM voice domain.
4.3.6 The Physical Layer
The physical layer on the air interface is divided into the
Physical Link Layer, specified in GSM 05.03, 05.08, 05.10 and in charge of
- Cell (re)selection, TX power control,

- Discontinuous reception,
- Synchronization, timing advance,
- Forward error correction,
- Channel coding, Interleaving
Physical RF Layer, defined according to GSM 05.02, 05.04, 05.05 and describing the
- GMSK / 8PSK modulation

- TRX characteristics
The Physical Link Layer is rather similar to the well-known procedures of circuit-switched
transmission. The Physical RF Layer is detailed in chapter 5 below.
4.3.7 Comparison GPRS to EGPRS
The basics are the same. The protocol stacks as shown in chapter 4.3.2 and 4.3.3 above look the
same for both GPRS and EGPRS. What is different:
Of course the Physical Layer is different (8PSK modulation as detailed in chapter 5.1).
The RLC/MAC layer is different: Different RLC block formats. Different headers depending on
the modulation and coding schemes used. For modulation and coding schemes providing high
bit rates, two RLC blocks are sent per radio block.
Radio Resource management: There are impacts on the Packet Data Channel (PDCH) allocation
algorithms. Some modification to the allocation of Temporary Block Flows (TBF).

5. THE PHYSICAL LAYER
5.1 Modulation schemes
As mentioned before, an additional, different modulation scheme is introduced in EDGE: While the
standard GSM including GPRS uses exclusively a so-called Gaussian Minimum Shift Keying
(GMSK), for EDGE a Phase Shift Keying with eight states (8PSK) is added for higher bitrates. A
comparison:
5.1.1 Gaussian Minimum Shift Keying (GMSK)
Minimum Shift Keying can be understood as an Offset-Quadrature Phase Shift Keying, where the
modulation signals are applied in form of cosine signals and filtered by a Gaussian function. So far
for the specialists.
Important for us are:

Q
Two states out of four are allowed to
represent a symbol at one instant of Q
t
time. After each symbol, a rotation Q
of /2 takes place as shown to the I
right. I
This means, that one bit per symbol I

can be transported. There is always a
phase change of 90 from one symbol
to the next (not less and not more).
With GMSK, the vector is staying on the dB

circle of the state diagram. The amplitude is PN
therefore constant over the whole burst.
This is indicated by the time mask for a
normal-duration burst with GMSK
modulation:
The average power during the burst (this is (147 bits)
the reference for the power definition) is 542.8 s t
equal to the peak power.
GMSK is a compromise between the width of the occupied spectrum and the side-lobes.

5.1.2 Phase Shift Keying with eight states (8PSK)
8PSK uses eight states as shown to the right:
This means, that each Q

110
modulation period transports 111 100
Q
three information bits (2 bits = 011 111 011 t
101
8 elements). This roughly triples Q
010 110 I
the bit rate compared to GMSK 010
010 001
as used for GSM. 000 011
I 000
000 100
001 111
I 001 101
The states are rotated by 3/8
110
with each symbol clock. 101
100
With 8PSK, we can no longer remain on the circle of the state diagram. To come from one
state to another one (for example from 011 to 101), we are going the direct way through the
inner part of the diagram. This results in the change of the amplitude when transiting from
one state to another, or to say in other words, the amplitude during the active part does
depend on the modulated data.
Without the trick of rotating the phase By using the trick of rotating the phase by
by 3/8 from symbol to symbol, the 3/8 from symbol to symbol, the center will
transitions could go through the center not be touched and the amplitude will never
of the state diagram. This results in an go to zero during the burst:
amplitude of zero for the respective
transitions for a infinitesimal duration of
time:
Q Q
I I

dB
This is indicated by the time mask for a
normal duration burst with 8PSK 0
modulation as shown on the right:

PN
As you can see, the minimum level
during the active part of the burst is -15
-15 dB relative to the nominal level

(and not going to - dB). (147 bits)
542.8 s t
The nominal output power of the transmitters is specified as the average power during the
active part of the burst. In GMSK, the average power is identical to the peak power (ignoring
imperfections like overshoots and ripples). In 8PSK, even though the peak power is the same
as in GMSK, the average power is lower than the GMSK power. This is sometimes called
power back-off. This power backoff is theoretically about 4.8 dB assuming the same peak
power as for GMSK and a random bit pattern. In reality, transmitters are often not limited by
the ability to deliver instant power peaks, but by thermal constraints. It is in that case
therefore possible to increase the peak power for 8PSK without violating the thermal limits.
The real power back-off in the Alcatel products is, depending on the product, lower than the
theoretical value of 4.8 dB (please refer to the EVOLIUM Radio Solutions Alcatel 9100 Base
Station Product Description for details).
The modulated bits are Gray-coded. In case one state is distorted due to interference so much
as to be decoded in its neighboring state, only one bit out of three is wrong. The following
picture tries to explain this effect:
Observation at time tx
Received symbol,
Q distorted so much as to
Ideal location of the symbol
be interpreted as 010
010
instead of 000
Possible real
locations of the 000 011
symbol due to
non-perfect trans- 111
mission 001
I
Area, in which the value of Thanks to the
the received signal will be Gray-coding,
110
decoded correctly 101 only one out
of the three
100
Bits is wrong.
Not using Gray-coding, the neighbouring symbol could be 111 for example.
Then, all three bits would be wrong.
The probability, that the signal is distorted so much as to be decoded two or
even more zones away, in the area of 011 for example, is low.

It is obvious, that the different states in 8PSK are closer together as in GMSK. Without giving
mind-squeezing mathematical formulas, we can conclude, that this modulation scheme is
more susceptible to interference.
Or, to put it in another way: We transmit more bits within a certain time with the same total
energy. The available energy per bit is therefore lower, which automatically results in a lower
bit energy to noise density ratio (Eb/N0).
This is the reason, why within the EDGE concept, the GMSK modulation is kept for
transmission under more degraded radio conditions.

5.2 Coding schemes
5.2.1 Overview
The coding schemes are different between GPRS and EGPRS. The table below gives the
comparison:
System Scheme Modulation Coding schemes Code rate Maximum data rate
schemes for RLC data block per time slot (RLC payload)
[kbps]
EGPRS MCS-9 8PSK 1/3 rate convolutional 1.00 59.2

coding, punctured
MCS-8 8PSK 1/3 rate convolutional 0.92 54.4

coding, punctured

coding, punctured

coding, punctured

coding, punctured
MCS-4 GMSK 1/3 rate convolutional 1.00 17.6

coding, punctured

coding, punctured

coding, punctured

coding, punctured
GPRS CS-4 GMSK No coding 1.00 20.0
CS-3 GMSK Half rate convolutional 0.75 14.4

coding, punctured

coding, punctured

coding
Table 2: Coding schemes
Please note, that the maximum data rate given in the table above refers to the RLC payload (= the
throughput offered to the Logical Link Control LLC layer). The RLC/MAC header, Block Check
Sequence (BCS), Tail bit etc. are already subtracted.

Still, these data rates do not represent the final throughput available to the end user. This is
explained in chapter 5.2.4 below.
Signaling uses always the CS-1 coding scheme, both for GPRS and EGPRS, as it offers the best error
correction capabilities.
You may ask, why four new modulation and coding schemes with GMSK were introduced for EGPRS.
There are already four defined for GPRS, why not use them for EGPRS as well ? Well, in order to
ease the link adaptation, a similar coding scheme (1/3 rate convolutional coding, punctured) is
required for all modulation and coding schemes. Back in time, when the GPRS schemes were
defined, nobody thought about the future extension with EGPRS, the chosen coding schemes are
hardly upwards compatible.
5.2.2 Convolutional coding
In the column Coding scheme in the table above, you find terms like Half rate convolutional
coding, punctured. You also find a column Code rate. Just let us recollect some basics:
Purpose: Convolutional coding is one form to implement a forward error correction (FEC)
function. With forward error correction, additional - redundant information is
inserted into the bit-stream. This allows detection and correction of bit errors
(caused by non-perfect transmission quality) at the receiving side.
Characteristic: Convolutional coding can be applied to a continuous bit stream (in contradiction to
block codes, where a defined number of bits is collected, processed and then
transmitted).
Code rate: The code rate is the relation of the payload to the total transmitted bits. A half
rate convolutional coder produces therefore twice the number of output bits
compared to the input (payload) bits. The lower the code rate, the more
"redundancy" is added which improves the error correction capabilities, but
reduces the payload throughput.
Puncturing: It is possible, to cut some bits out of the convolutional coded bit stream reducing
the error protection capabilities but without losing information. This is used to
squeeze the coded bits into the frames of a given, fixed length. This process is
called puncturing. The code rate given in the table of the previous chapter is
actually already considering the puncturing.

5.2.3 Coding Scheme Adaptation, Link Adaptation (LA) and Incremental Redundancy (IR)
Coding Scheme Adaptation (for GPRS)
The choice of the coding scheme used for a given GPRS user at a given time is done using the
dynamic Coding Scheme adaptation algorithm according to the reception quality (RxQual) and
level (RxLev) measurements performed by the BTS and the mobile. Both uplink and downlink
Coding Scheme adaptation are under control of the network.
Link Adaptation (LA) (for EGPRS)
The modulation and coding scheme (MCS) used for a given EGPRS connection depends on the radio
conditions as well. Measurements of the bit error probability (BEP) and the standard-deviation of
the BEP are used to determine the most suitable MCS for the actual radio propagation. The process
to select the appropriate MCS is called Link Adaptation. The influence of the Link Adaptation on
the performance is discussed in chapter 6.2.6.
Incremental Redundancy (IR) (for EGPRS)
In addition, the feature Incremental Redundancy is introduced for EGPRS. This function was
specified by ETSI as optionally for base stations and mandatory for mobiles. The Alcatel base
station implementation makes use of this feature.
How does it work ? If a block is not properly decoded in the first instance, the bits are stored in
the base station, the mobile respectively, as soft bits. The same block is repeated with a
different puncturing scheme. The resulting soft bits of the second (and, if necessary, third)
transmission are then combined with the previously transmitted block(s). This improves the
likelihood of ending up with the correct data.
Even if one block of data is found to be not good, it still can be used to improve the total bit error
rate of the system (you remember, in GSM speech transmission, blocks with a too high error rate
are just discarded - wasted).
You probably noted when reading table 2, that MCS-9 uses a 1/3 rate convolutional
coding scheme with puncturing resulting in a code rate of 1.0. You wondered,
perhaps, why MCS-9 is not specified like CS-4 without coding at all. Now you
understand, that this way of coding is necessary to allow incremental redundancy for
MCS-9 (if you would not use puncturing, you could not retransmit and combine the
block with a different puncturing scheme).

5.2.4 Bit rates available to the application
The bit rates given for the different modulation and coding schemes in chapter 5.2.1 above refer
to the data payload on the RLC/MAC layer.
These bit rates are not available to the applications of the end-user. Two effects eat up some of
the speed:
The different headers for the protocols
The bit error rate is not 0 %, some data blocks needs to be re-transmitted depending on the
radio conditions.
The first point, the header-overhead, can be visualized on the protocol layers as seen from the
mobile (example of surfing the web):
Application Layer www

World Wide Web
http
Utility Layer Outside of the PLMN
Hypertext Transfer Protocol
TCP
Transport Layer Transaction Control Protocol
Internetwork Layer IP
Internet Protocol
SNDCP NSS
Subnetwork Dependent (Core Network)
Convergence Protocol
Network Layer
LLC
Logical Link Control
RLC
Radio Link Control
Link Layer
MAC BSS
Medium Access Control
Physical Layer GSM-RF

The table below gives the maximum payload data throughput on the RLC layer for error-free
transmission and the payload data throughput on the RLC layer for the ETSI reference point (block
error rate of 10 %). The figures are given for one timeslot each.
System Scheme Max RLC data throughput (RLC RLC data throughput at Reference
payload) Point (BLER=10%)
[kbps] [kbps]
EGPRS MCS-9 59.2 53.3
MCS-8 54.4 49.0
MCS-7 44.8 40.3
MCS-6 29.6 26.7
MCS-5 22.4 20.2
MCS-4 17.6 15.9
MCS-3 14.8 13.3
MCS-2 11.2 10.1
MCS-1 8.8 7.9
GPRS CS-4 20.0 18.0
CS-3 14.4 13.0
CS-2 12.0 10.8
CS-1 8.0 7.2
Table 3: Data throughput
In general, we define the "real" user data rate to be the rate the IP-layer provides to the upper
layers, as we do not know, which application will actually be used. We therefore take into account
the LLC/SNDCP and IP/X.25 headers to evaluate the "real" user throughput. This is not so easy
because the rate depends on the IP payload: For short packets, the overhead is relatively higher
than for long packets.

IP Payload Correction factor

[Bytes]
The table to the right gives a correction factor depending
on the length of the IP payload. In order to get the real 50 63 %
user throughput, simply multiply the RLC throughput with 100 77 %
the factor given.
200 87 %
300 91 %
500 94 %
1000 97 %
1500 98 %
Table 4: Correction factor
Example: IP payload = 300 bytes
CS-4 RLC data throughput at Reference Point (BLER=10%) = 18.0 kbps
Real user data rate = 18.0 kbps x 91 % = 16.38 kbps per time-slot
5.2.5 End-user data-rates
GPRS and EGPRS allow several users to share one timeslot and also to combine several timeslots
for one user. The bitrate seen by one user (the peak bit-rate) can therefore be higher than the
throughput of one timeslot. You will find fantastic rates announced in literature and brochures: Up
to 384 kbps, sometimes even 473.6 kbps (8 x 59.2 kbps) are promoted.
We learned in the previous chapter, that these rates are on the RLC layer and are not really seen
by the end-user. There are a lot of dependencies which have an influence on the transmission
rate. The transmission mechanisms used, for example by the Internet protocols, have a great
influence. High traffic load situations can decrease the throughput drastically.
In addition, we have to be careful on the ability of the mobile terminals, especially for small
handheld devices. As from the knowledge of today, the mobile part will in most cases not provide
more than a 3+1 or 4+2 configuration (timeslots in downlink + timeslots in uplink). The processing
capabilities of the terminals will probably not allow to exceed 100 to 150 kbps. This message is
based on the extrapolation of the technology of today taking also battery limitations into account
(the more processing power, the higher the power consumption).

6. NETWORK COVERAGE AND THROUGHPUT
6.1 Some basics
The introduction of GPRS and EGPRS into existing GSM networks designed for voice is very easy, as
the standard has been defined in a way to offer at least the lowest coding (and modulation)
scheme over the full cell area without constraints on the existing network plan.
If a network, however, shall be planned for a certain minimum throughput, we have to look a little
bit closer on the way to design the GPRS/EGPRS part.
From the design of GSM networks for voice, we are used to cell ranges, cell areas respectively, in
which, with a certain probability, coverage is provided. Considering a certain, market-defined
coverage class and coverage probability, a cell range or an cell area could be defined, where
mobile telephony service can be offered.
A common way for calculating the cell range for voice is the link budget. Based on the equipment
parameters like transmit power, receiver sensitivity, consideration of losses and gains, a path-loss
can be calculated which, using empirical models like Hata-Okumura, COST 231 etc. results in the
cell range.
With GPRS and EGPRS, this is different: Service can be offered everywhere within the cell range
as for voice, but due to the link adaptation, the throughput differs significantly from the center of
the cell towards the edge of the cell. The comparison between voice and packet data:
Voice service Packet data service (GPRS/EGPRS)
Service available, or service not available Service available, service quality (data
(based on a certain, specified probability) throughput) dependent on the location
Service Service
Quality Quality
Distance from base station Distance from base station
The depiction is very much simplified
The conclusion: There is no fixed cell range for GPRS/EGPRS. The coverage area depends directly
on the requested data throughput. If the requested data throughput is low, the cell range for
GPRS/EGPRS can be much larger than for voice. If the requested data throughput is high, the cell
range can be lower as for voice.

6.2 GPRS and EGPRS performance
6.2.1 Introduction
The performance in terms of data throughput per PDCH depends on several parameters:
The carrier-to-interference and noise ratio C/(I+N)
- Carrier -> Level (fieldstrength) from the serving cell at the mobile location
- Interference -> Co- and adjacent channel interference from non-serving cells
- Noise -> assumed to be thermal noise and the noise created by the non-perfect
receivers of mobiles and base stations
Use of frequency hopping
Link adaptation
Use of Incremental Redundancy
6.2.2 Different definitions for network performance
Usually, the data throughput specified refers to one PDCH, ignoring that in GPRS and EGPRS
several PDCH per user can be combined to get a higher data throughput.
Due to the asymmetric traffic expected for packet data services (much more downlink traffic than
uplink traffic), GPRS and EGPRS networks are planned commonly for the downlink only. The
throughput is therefore specified for the downlink.
There are different ways to define the data throughput in a network:
Mean Data Throughput The area of the network can be considered to be divided into equally
sized pixels. The data throughput is calculated pixel per pixel. The
pixels close to the base station will have a high data throughput; the
pixels at the cell border provide only a low throughput. The mean
data throughput is the average of all pixels within one cell.
This is the most common definition for data throughput.
x% Data Throughput Again, the data throughput is calculated pixel per pixel. The defined
data throughput is the minimum value reached by at least x % of all
the pixels. Common values for x are 50%, 90% and 95%.
Example: 90% Data throughput of 20 kbit/s. 90% of the cell area

provides a data throughput of at least 20 kbit/s, 10% of the cell area
are below that value.

Guaranteed Data Throughput A guaranteed throughput in the pure sense does not exist. It is similar
to voice: A coverage probability of 100.0% is not possible.
When talking about a guaranteed data throughput, in fact a minimum

throughput with a certain area probability is meant. The definition is
usually the same as above for x% Data Throughput.
The diagram below visualizes the difference between the mean data throughput and, as example,
the 90% data throughput (this diagram is heavily simplified):
kbit/s Assumed cell border
60
Data throughput as function of

50 the distance mobile to BTS
Mean 40
data
through-
put 30
90%
through- 20
put
10
0
0 200 400 600 800 1000 1200 1400 1600
Distance BTS - Mobile [m]
Why is the Mean Data Throughput the most common definition ?
Because this definition describes best the performance of the complete system. GPRS/EGPRS is
not, like voice, limited to one timeslot. Depending on the mobile capability, several timeslots (up
to eight in theory, up to five with real mobiles) can be combined to provide a higher throughput.
A mobile close to the base station receives a higher data throughput. It therefore occupies less
timeslots. The mobile farther away from the base station receives a lower data throughput, but
can get more timeslots to compensate for that.
Or in other words, even a mobile at the cell border benefits from the higher throughput: The
mobiles close to the BTS occupys less time-slots for a given data throughput or completing the
data transfer earlier. The mobile at the cell border (assuming mobiles with multi-slot capability)
can compensate its lower throughput per timeslot by combining timeslots not occupied by the
mobile close to the BTS. This is an important idea on optimizing the spectrum usage and often
ignored !
The mean data throughput is therefore the appropriate value to design the network.

6.2.3 Simulation results
The following diagrams show exemplary simulation results for the data throughput dependent on
the distance between the mobile and the base station for EGPRS. The results are shown for four
different frequency reuse cluster sizes (1x3, 3x3, 4x3 and 7x3) and a fixed inter-site distance.
Dense urban, GSM 900, with incremental redundancy, no frequency hopping, three-sectored
Fading profile TU3

60
Indoor loss 17 dB
Mean Throughput [kbit/s]
50
Body loss 3 dB
40 7x3 BTS antenna height 20 m
4x3
30 Antenna 65
3x3
beamwidth
20 1x3
EIRP GMSK 57.7 dBm
10
EIRP 8PSK 52.9 dBm
0
0 500 1000 1500
Diagram 1: EGPRS, mean throughput over distance, GSM 900, dense urban
Rural, GSM 900, with incremental redundancy, no frequency hopping, three-sectored
Fading profile RA100

60
In-car loss 8 dB
Mean Throughput [kbit/s]
50
Body loss 3 dB
40 7x3
BTS antenna height 35 m
4x3
30
3x3 Antenna 90
20 1x3 beamwidth
EIRP GMSK 59.3 dBm

10
EIRP 8PSK 54.5 dBm
0
0 2000 4000 6000 8000 10000
Diagram 2: EGPRS, mean throughput over distance, GSM 900, rural
We can see, that EGPRS shows a very good performance both for urban and rural applications. And
please remember, that several timeslots can be combined for one user !

For urban areas, we have to consider, that the cell range for voice with indoor coverage is in a
range of one to three kilometers. EGPRS would, in fact, offer a much wider service area as voice
when accepting lower data rates.
We can also see the influence of the interference: The more intensively we are using the
spectrum, the lower the data rates per timeslot get. The difference between a 3x3 and a 4x3
reuse is rather small, while a 1x3 leads to a severe degradation. Going to a 7x3 reuse increases the
data throughput per timeslot within a certain cell. As the frequencies are less utilized, the total
spectrum efficiency is reduced.
Remark: Important for the interpretation of the above diagrams is to keep in mind that they are
done as function of the distance mobile to BTS for a fixed cell range/site distance. Close
to the base station, the C/I and therefore the data throughput is high (field strength
from serving base station high, distance to neighbour cells high -> interference low).
Further away from the base station, the C/I is low and therefore the data throughput is
lower (field strength from serving base station low, distance to neighbour cells lower ->
interference higher).
An alternative representation would be to show the data throughput as function of the

cell range (mobile would always be located at the cell border for varying cell ranges/site
distances). The resulting diagram would look different. As the C/I is more or less
constant for different cell ranges (reducing the cell range improves the field strength
from serving base station, but also increases the interference level from neighbouring
base stations), the resulting graph would show a more constant bit rate for different cell
ranges.
You can find more details on how these simulations were done in the document "Introducing 3rd
Generation Mobile Communication Services on Evolved GSM Platforms" by Dr.-Ing. Michael
Tangemann, Dr.-Ing. Andreas Weber and Dr.-Ing. Dirk Nikolai.
6.2.4 Some remarks to spectrum efficiency
GPRS and EGPRS will provide a much better spectrum efficiency (in kbps/MHz) compared to voice.
The reason is that the design of a voice network is done to ensure a minimum quality level in the
cell. This leads to an "excessive" good signal-to-noise-and-interference-ration SINR in most of the
cell area. An example for the probability function is given below:

0.18
0.16
0.14
0.12
Probability
0.10
0.08
0.06
0.04
0.02
0.00
-4 0 4 8 12 16 20 24 28 32 36 40
SINR / dB
Diagram 3: Probability function for SINR
A SINR-value of around 17 dB has the highest probability, while 9 dB would be sufficient for voice.
This can be utilized by GPRS and EGPRS by transporting more information bits per second wherever
possible: The total spectrum usage per cell is optimized.
As mentioned before in chapter 6.2.2, even a mobile at the cell border benefits from the higher
throughput: The mobiles close to the BTS get a higher throughput per timeslot, therefore
occupying less time-slots for a given data throughput or completing the data transfer earlier. The
mobile at the cell border can compensate it's lower throughput per timeslot by combining several
timeslots (assuming mobiles with multi-slot capability).
As the throughput of GPRS is reaching its saturation point (the point, where an improvement in C/I
does not result in increased data throughput anymore) earlier than EGPRS, the spectrum efficiency
of EGPRS is better. This is visualized in the curves below:
60
50
Throughput [kbit/s]
40
EGPRS
30
GPRS
20
10
0
-10.0 0.0 10.0 20.0 30.0 40.0 50.0
C/I [dB]
Diagram 4: Throughput of GPRS and EGPRS as function of C/I

6.2.5 Influence of frequency hopping on data throughput
As we have seen above, the data throughput for GPRS and EGPRS depends to a large extend on the
interference experienced within the coverage area. For circuit-switched speech-traffic, frequency
hopping was proven to be a good feature to combat the effects of co-channel and adjacent
channel interference. Frequency hopping is especially useful for slow-moving subscribers. It is now
interesting to know, whether the same positive effect of frequency hopping can be utilized for
GPRS and EGPRS.
With GPRS and EGPRS, it is not so easy:
A GPRS/EGPRS radio block consists of four bursts. If frequency hopping is switched off, there is a
good chance that either all four bursts are good or all four bursts are bad (containing errors). This
is due to the fact that the channel quality changes slowly in case of no frequency hopping, while it
changes for every burst in case of frequency hopping.
Example for frequency hopping: Let us assume we have 25% of bursts with errors before decoding.
Consequently, with frequency hopping there is a chance of 25% that the next burst has errors
(before decoding). The chance that the whole radio block, i.e. at least one of the four bursts, has
errors (before decoding) is 1.0-(1.0-0.25)4 = 68%.
In case of no frequency hopping, the chance that the next burst is defect depends on the present
burst (due to the slowly changing channel quality, see above). If the present burst is without errors
(before decoding), then there is a good chance that the next one is also without errors because
most probably the channel is good and it will stay good for some time for the chosen frequency.
Obviously, the same is true for defect bursts.
For Coding Schemes without error correction capability (like CS-4, MCS-4 and MCS-9) the block
cannot be decoded if at least one burst has errors. With frequency hopping we get a block error
probability of 68% according to the example above. Without frequency hopping, we have a higher
chance that all four bursts are without errors and the radio block can be successfully decoded.
The conclusion of the simulations:
GPRS step 1 (CS-1 and CS-2): Frequency hopping is recommended
GPRS step 2 (CS-1 to CS-4), EGPRS (MCS-1 to MCS-9): Frequency hopping is not recommended
(however, the performance difference is not dramatic). If MCS-9 is disabled (which is possible
in the Alcatel realization), frequency hopping can be used.
6.2.6 Influence of Real Link Adaptation on Data Throughput
The network will adapt the data throughput dynamically. The target is the optimum selection of
the modulation and coding scheme for a given radio condition. For GPRS, the radio condition is
defined by the received level (RXLEV) and the received quality (RXQUAL). For EGPRS, the bit error
probability (BEP) and the standard-deviation of the BEP is used. For the downlink, this is measured
by the mobile and transmitted in signaling messages to the BSS.

Most simulation results are done for ideal Link Adaptation, i.e. always the most appropriate
modulation and coding scheme is used. Ideal link adaptation would be able to make perfect
forecasts of the channel condition before a radio block is transmitted, which is not possible in
reality.
In reality, the results are below this optimum value. This is mainly due to the delay between the
measurements of RXLEV and RXQUAL and the execution of the modulation/coding scheme change.
The delay comes mainly from necessary averaging of the values and the time implied by the
protocol. The real performance depends on lots of parameters including fading profile (mobile
movements), packet length, BSS parameter settings and the link adaptation algorithm.
The data throughput loss under real conditions can be in a range of 7% to around 20%.
6.3 How to plan a GPRS/EGPRS network
We distinguish two levels of network planning:
Preliminary Network Design, resulting in an estimation of the required network elements to

reach a certain network quality. This is commonly done to support business case calculations
in an early stage of the decision making process.
Radio Network Planning, providing as result plots with a prediction of data throughput per
timeslot at given locations (i.e. pixels on a map). This is done to find the most suitable
locations for the base stations.
6.3.1 Process for Preliminary Network Design
Within Alcatel, a simulation tool exists which allows to calculate
either the data throughput possible with a certain cell range,

or the maximum cell range possible when a minimum data throughput has to be met.
The Mobile Network Design department of Alcatel can help to provide the data throughput
estimations for any specific conditions.
One remark to link budgets for GPRS/EGPRS: Designers used to plan GSM networks for
voice are sometimes asking for link budgets for GPRS and EGPRS. The expected schemes
are concentric rings around the base station giving the cell range for each modulation
and coding scheme MCS. The MCS found at the cell border is then taken as equal to the
minimum data throughput.
Now, the explanations given above make something very clear: Link budgets for GPRS /
EGPRS do not make sense. They neither consider the influence of interference, nor the
properties of the link adaptation algorithms, incremental redundancy, frequency hopping
etc.
The results from link budgets for GPRS/EGPRS are misleading and should never be
used to estimate the expected data performance.

6.3.2 Radio Network Planning process for GPRS/EGPRS
The basis for GPRS/EGPRS planning is the radio network planning tool A955. Required are digital
databases for morpho-structure (clutter, landuse) and height (Digital Terrain Model DTM).
Morpho-structure Digital Terrain Model DTM
Urban
Suburban
80 m
Rural
40 m
Some of the planning steps are well known:
Calculation of field strength prediction

per pixel
Some details: GSM 1800
53.4 dBm EIRP 8PSK
(58 dBm EIRP GMSK not shown)
Antenna height over ground 23m
dBm

Best server plot
1000 m
Automatic frequency assignment Site Cell 1 Cell 2 Cell 3

name TRX 1 TRX 2 TRX 3 TRX 1 TRX 2 TRX 3 TRX 1 TRX 2 TRX 3
e 01 582 563 571 561 569 577 576 584 573
e 02 582 570 579 586 568 576 589 574 560
e 03 570 560 566 568 580 588 564 583 586
e 04 575 562 579 560 585 577 583 570 566
e 05 585 561 565 579 582 567 576 589 563
e 06 572 588 577 579 568 586 584 581 564
Average frequency reuse (approximately) 10 e 07 587 578 573 589 580 567 576 561 585
except between the sites e 01, e 05 and e 06, e 08 563 571 588 578 581 585 568 573 561
e 09 585 571 562 577 573 568 583 588 575
were (by intention) a higher interference was
e 10 563 582 575 565 578 573 570 588 560
created. Three TRX per cell are assigned. The e 11 583 569 564 588 560 585 566 571 574
ones with the green background are used for e 12 565 589 561 587 568 572 570 585 574
EGPRS. e 13 589 569 581 562 567 571 587 583 565
e 14 589 571 583 577 569 580 564 586 567
e 15 582 588 565 572 563 584 579 560 586
Interference calculation per pixel

Between the cells e01 and e06, a spot with
high interference was created by intention.
This was done to show the influence of the
interference on the throughput (see the plots
below). In a real system, such spots would be
avoided.
C/I
Increasing C/I

As a result, we have for each pixel the signal level, the interference level, and implicitly the noise
level (just the thermal noise). This is exactly, what we need to calculate the throughput per pixel.
The result for the above example:
Data throughput on RLC/MAC layer.
If you compare with the field strength plot and

the interference plot above, you can see
- the influence of low field strength
- and the influence of high interference
Kbit/s
Please note, that throughput plots

based on the level only as provided
by most other tools will not result
in a correct prediction.
As you can see, the result is too optimistic,
especially in areas with high interference.
Kbit/s

Another interesting information is the

modulation and coding scheme used.
To the left, the modulation and coding
scheme for the example above
considering both level and interference
is shown.
A large portion of the area is covered with MCS-

9. This is due to incremental redundancy.
MCS
9
8
7
6
5
4
3
2
1
0
Remark: The data throughput per pixel is a snapshot of a static situation. During cell reselection,
the data stream is interrupted for a moment. This is not considered in such plots.

7. TRAFFIC ASPECT
7.1 What is the difference to speech transmission ?
With the introduction of packet data schemes, the range of applications available to the users is
much wider than before: We arrive in the multi-media world.
PC, laptop, PDA Remote access Traffic management Automation
Entertainment Information E-commerce And much more

(m-commerce)
It is quite clear, that the traffic behavior can no longer be described with just the Erlang B
formula. We need a more advanced Multi-Service Traffic Model.
7.2 Multi-Service Traffic Model
A complete deterministic multi-service traffic model distinguishes between a session level (for
example, the user dials his Internet service provider), a page level (loading of a selected HTML-
page) and a packet level (the segmented datagrams actually routed from server to client).
This model has to be set up for all services offered, to calculate the average and peak data rate
for which the network has to be designed for. This subject is very mathematical. An interesting
study on this subject has been done and documented by the University of Malaga: "A page-oriented
WWW traffic model for wireless system simulations" (A. Reyes-Lecuona, E. Gonzlez-Parada, E.
Casilari, J. C. Casasola and A. Daz-Estrella).

The deterministic multi-service traffic model is visualized in the diagram below:
Session inter-arrival time: exponential
Session level t
Number of pages: log-normal
Page size: Reading time:

Pareto Gamma law
Page level t
Packet size: Inter-packet time:

multimodal exponential
Packet level t
For a complete view, this static model has to be complemented by a dynamic simulation. This
approach is not easy to use. Other solutions allowing a good approximation with less effort are
discussed. To give more details would go beyond the scope of this document.
Due to the dynamic PDCH allocation available by Alcatel as described in chapter 4.2.4, the model
should combine the circuit-switched and the packet-switched traffic. Just calculating both traffic
types separately and adding up of the results leads to an over-design of the Air interface.
Lets look into a simple example (without proof). We assume the traffic for a cell as below:
Subscribers Volume per Service quality

number subscriber in busy
hour
Voice service 280 20 mErlang Blocking Probability 2.00%
Data service 280 102 Kbytes Service bit rate 12 Kb/s, mean page size 2.5
Kbytes, queuing time delay max. 5 seconds
with a quantile of 95%
Table 5: Traffic example
Using a simplified multi-service traffic model considering the dynamic PDCH allocation, the requested
traffic can be served with 14 timeslots on the Air interface, we have to equip the cell with two TRX.
By calculating the required resources for both circuit- and packet-switched traffic separately and
adding up the results, we would come to 19 timeslots, the cell would have to be equipped
(unnecessarily) with three TRX.

7.3 Mobile station capabilities
Different MS classes and types are defined for GPRS / EGPRS. First of all, three classes of GPRS /
EGPRS mobile devices are supported:
Class-A mobile station: Can operate packet and circuit-switched services simultaneously.
Class-B mobile station: Can monitor control channels for both packet-switched services and
circuit-switched services simultaneously, but can only operate one set
of services at a time.
Class-C mobile station: Can either be attached to circuit-switched services or to GPRS /

EGPRS services, but not to both simultaneously.
The maximum number of PDCHs granted to a mobile depends on its multi-slot class. The
constraints determining the maximum capacity per user are the following:
MS type: Type 1: simplex MS (either transmit or receive)
Type 2: duplex MS (receive and transmit simultaneously)
Maximum number of receive/transmit timeslots per TDMA frame. Examples: 1+1 (one TS
for the downlink plus one TS for the uplink), 3+1 (three TS for the downlink plus one TS
for the uplink)
Minimum time (in timeslots) between receive, transmit and measurements. These values
are defined in GSM 05.02 in more detail.
EGPRS-mobiles can further be divided into two sub-groups:
A first type with 8PSK capability on the downlink only (using only MCS-1 to MCS-4 in uplink)
and a second type with 8PSK capability downlink and uplink.
Considering the unbalanced traffic in Internet-like applications, the first type makes a lot of
sense. Even if the second type is used, it might be acceptable, to have lower data rates on the
uplink.

8. INTERFACES AND TRANSMISSION ASPECTS
An overview on all possible interfaces within an GPRS / EGPRS network was given in chapter 3.1.
Some hints on what's going on on some of them can be extracted from the protocol stacks in
chapter 4.3. A complete overview of all interfaces with their functions and protocols would fill a
book, we therefore concentrate on some aspects which might be most interesting for the practical
engineer.
8.1 Capacity aspect for the Abis interface
Without GPRS step 2 or EDGE/EGPRS, the amount of information provided per Air interface
timeslot allowed to have the eight timeslots of one TRX mapped onto two 64kbit/s timeslots of the
Abis interface (adding some timeslots for signalling and O&M). Using this scheme, even a fully
equipped BTS cabinet could be served by one E1-interface (PCM30).
Introducing GPRS step 2 or even EGPRS, the amount of information provided by the timeslots of
the Air interface increases. If a BTS is fully equipped with TRXes, one E1-link may no longer be
sufficient to carry all data between BTS and BSC.
Upon the introduction of GPRS step 2 and EGPRS, the possibility to connect two E1-links between
BTS and BSC is added. This requires no hardware change to Alcatel EVOLIUM BTS.
8.2 Transmission management on the Ater interface
Two types of Ater interfaces are supported between the BSC and the MFS:
Submultiplexed Ater interface for mixed circuit-switched and GPRS CS-1 and CS-2 channels.
Direct connection of PCM30 links for 64 kbit/s packet data channels between the BSC and the
MFS (no sub-multiplexing, no mixture with circuit-switched channels).
The MFS is the master for the Ater resources used for packet data.
8.3 The Gb Interface
The Gb interface connects the BSS to the NSS (or more fashionable, the Core Network). This is the
interface, where multi-vendor interworking is interesting. The Gb interface has therefore to follow
strictly the GSM recommendations.

Lets recall the protocol stack to see what is transported by the Gb interface:
The BSS GPRS Protocol BSSGP handles Radio Resource

BSSGP BSSGP information, Quality of Service information and
BSS GPRS Protocol BSS GPRS Protocol
routing information. It is based to a large extend on
GSM 08.18 GSM 08.18 the BSSMAP protocol.
The Network Service NS transfers the Packet Data

Units PDU between the BSS and the SGSN. It allocates
NS NS PDUs to Virtual Channels VC and takes care of the
Network Service Network Service
load-sharing. The Network Service is based on a Frame
GSM 08.16 GSM 08.16
Relay Data Network, which is a specific type of a
packet data network.
L1bis L1bis The physical layer can, for example, be provided by
Layer 1bis Layer 1bis
GSM 08.14 GSM 08.14 64 kbit/s timeslots on PCM 30 (E1) trunks according to
ITU G.703 / G.704.
PCU (MFS) Gb SGSN
The PCU (MFS) and the SGSN are often not located in the same room. Therefore different
possibilities are provided to route the Gb interface:
A PTSN
MSC
TC ISDN
VLR
Direct connection between PCU (MFS)
Ater
and SGSN BSC
MFS
(PCU) Gb
SGSN
Packet-switched services
A PTSN
MSC
TC ISDN
VLR
Via a (public) Frame Relay Data
Ater
Network BSC
MFS
Gb Gb
(PCU) Frame Relay
Network SGSN
Packet-switched services

A
PTSN
MSC
TC ISDN
VLR
Via the MSCs BSC

Ater
MFS Gb
(PCU)
MSC Gb
Packet-switched services SGSN
VLR
Co-located
A
PTSN
MSC
TC ISDN
VLR
Via the Ater multiplexed interface BSC

Ater
Gb Gb
through the transcoder and the MSCs MFS
(PCU)
MSC Gb
Packet-switched services SGSN
VLR
Co-located

9. LITERATURE
Papers giving introductions and overviews:
Alcatel's approach to GPRS, Position Paper (3DC 21141 0007 TQZZA)
Wireless Data with HSCSD or GPRS? (Alcatel)
Dr.-Ing. Michael Tangemann, Dr.-Ing. Andreas Weber, Dr.-Ing. Dirk Nikolai: Introducing 3rd
Generation Mobile Communication Services on Evolved GSM Platforms
Data Throughput in EDGE / EGPRS Networks (3DC 21150 0285 TQZZA)
On the Road to 3G with Alcatel
Spectrum Efficiency: A Comparison between EDGE and UMTS (3DC 21084 0005 TQZZA)
Related ETSI documents and recommendations (check for the latest edition):
EDGE: Concept Proposal for Enhanced GPRS (Tdoc SMG2 657/99)
ETSI EN 301 344 (GSM 03.60)
ETSI TS 101 350 V8.2.0 (GSM 03.64)
ETSI EN 301 349 (GSM 04.60)
ETSI TS 100 573 V7.0.1 (GSM 05.01)
Draft ETSI EN 300 959 V7.1.0 (GSM 05.04)
ETSI EN 300 910 V 8.5.1 (GSM 05.05)
ETSI documents are available on the Internet under http://www.etsi.org. As all standardization
activities of GERAN have been transferred to 3GPP, you might better check http://www.3gpp.org.
If you want to dig deeper into theory:
A. Reyes-Lecuona, E. Gonzlez-Parada, E. Casilari, J. C. Casasola and A. Daz-Estrella: "A

page-oriented WWW traffic model for wireless system simulations" (Dpto. Tecnologa
Electrnica, E.T.S.I. Telecomunicacin, Universidad de Mlaga)
Description of Alcatel products related to GPRS and EGPRS:
EVOLIUM Radio Solutions Alcatel 9100 Base Station Product Description (3DC
21083 0001 TQZZA)
EVOLIUM Radio Solutions Alcatel GSM 900/GSM 1800 G2 Base Station

Controller Product Description (3DC 21016 0003 TQZZA)
EVOLIUM Radio Solutions A935 MFS Multi-BSS Fast packet Server Product
Description (3DC 21016 0005 TQZZA)
Alcatel GPRS NSS Product Description (3DN 00501 AAAA DEZZA)

10. LIST OF ABBREVIATIONS

1 E1......... ITU-T G.703/G.704 physical interface
3GPP ......Third Generation Partnership Project F
A FEC ....... Forward Error Correction
AAL5 ......ATM Adaptation Layer 5 FR......... Frame Relay
APN .......Access Point Name FR......... Full Rate
ARQ .......Automatic Repeat Request G
ATC .......ATM Transfer Capability Gb ........ Interface between BSS and SGSN
ATM .......Asynchronous Transfer Mode GERAN ... GSM/EDGE Radio Access Network
AuC........Authentication Center Gc ........ Interface between GGSN and HLR
B Gd ........ Interface between SGSN and SMS-GMSC
BCCH......Broadcast Control Channel Gf......... Interface between SGSN and EIR
BEP........Bit Error Probability GGSN ..... Gateway GPRS Support Node
BGP .......Border Gateway Protocol Gi ......... Interface between a GGSN and a PDN.
BLER ......Block Error Rate GMM ...... GPRS Mobility Management
BSC........Base Station Controller GMSC ..... Gateway MSC
BSS ........Base Station System GMSK ..... Gaussian Minimum Shift Keying
BSSGP.....BSS GPRS Protocol Gn ........ Interface between SGSNs and between SGSN
BSSMAP ...BSS Mobile Application Part and GGSN.
BTS ........Base Transceiver Station Gp ........ Interface between SGSN and GGSN of other
BVC .......BSSGP Virtual Connection network
GPRS ..... General Packet Radio Service
C GPU ...... GPRS Processing Unit
CAC .......Call Acceptance control Gs......... Interface between SGSN and MSC/VLR
CCCH......Common Control Channel GSL ....... GPRS Signaling Link
C/I ........Carrier to Interference Ratio GSN....... GPRS Support Node
C/ICO ......Carrier to Interference Ratio - Common GSM ...... Global System for Mobile communication
Channel Interference GTP....... GPRS Tunneling Protocol
CLNP ......Connectionless Network Protocol
CLNS ......Connectionless Network Service H
CONP......Connection-Orientated Network Protocol HDLC ..... High-Level Data Link Control
CONS......Connection-Orientated Network Service HLR ....... Home Location Register
CS .........Circuit-Switched HPLMN ... Home PLMN
CS-x .......Coding Scheme x (x = 1, 2, 3, 4) HSCSD .... High Speed Circuit Switched Data
http ...... Hypertext Transfer Protocol
D
DF .........Delivery Function I
DHCP......Dynamic Host Configuration Protocol IAP........ Internet Access provider
DNS........Domain Name Server IMSI ....... International Mobile Subscriber Identity
DR .........Dual Rate IP ......... Internet Protocol
DRX .......Discontinuous Reception IPv4....... Internet Protocol Version 4
DSP........Digital Signal Processor IR ......... Incremental Redundancy
ISDN ...... Integrated Service Digital Network
E
ISP ........ Internet Service Provider
ECSD ......Enhanced Circuit Switched Data IT ......... Information Technology
Eb/N0 ......Bit Energy to Noise Density ratio ITU ....... International Telecommunication Union
EDGE ......Enhanced Data Rates for GSM Evolution Iu_CS ..... Interface between RAN and core network, CS
EGP .......Exterior Gateway Protocol Iu_PS ..... Interface between RAN and core network, PS
EGPRS.....Enhanced General Packet Radio Service IWMSC.... Interworking MSC
EIR ....... Equipment Identification Register
K
ERAN ......EDGE Radio Access Network
ETSI .......European Telecomm. Standardization Institute kbps ...... Kilo Bit Per Second

L PRACH ....Packet Random Access Channel

LA ......... Location Area PSPDN ....Public Switched Packet Data Network
LA ......... Link Adaptation PSTN ......Public Switched Telephone Network
LAN ....... Local Area Network P-TMSI ....Packet Temporary Mobile Subscriber Identity
LLC ....... Logical Link Control PVC .......Permanent Virtual Connection
L1 ......... Layer 1 Q
L2 ......... Layer 2 QoS........Quality of Service
M R
MAC....... Medium Access Control RA .........Routing Area
MCS ....... Modulation and Coding Scheme RAN .......Radio Access Network
MFS ....... Multi-BSS Fast Packet Server RF .........Radio Frequency
MM ........ Mobility Management RFC .......Request for Comment
MO ........ Mobile Originated RLC........Radio Link Control
MPDCH ... Master Packet Data Channel (). RNC .......Radio Network Controller
MS......... Mobile Station RRM .......Radio Resource Management
MSC ....... Mobile Services Switching Center
MSP ....... Multiple Subscriber Profile S
MT ........ Mobile Terminating SAP........Service Access Point
SDCCH ....Stand-alone Dedicated Control Channel
N
SDU .......Service Data Unit
NMC....... Network Management Center SGSN ......Serving GPRS Support Node
NMO ...... Network Mode of Operation SIM ........Subscriber Identity Module
NS......... Network Service SINR.......Signal-to-Noise-and Interference Ratio
NSS ....... Network Subsystem SM .........Session Management
O SMS........Short Message Service
OAM ...... Operation, Administration and Maintenance SNDCP ....Sub-Network dependent Convergence Protocol
OMC-R .... Operation and Maintenance Center - BSS SVC........Switched Virtual Circuit
O&M ...... Operation and Maintenance T
P TBF........Temporary Block Flow
PACCH.... Packet Associated Control Channel TC .........Transcoder
PAD ....... Packet Assembly/Disassembly facility TCP .......Transfer Control Protocol
PBCCH.... Packet Broadcast Control Channel TFI ........Temporary Flow Identity
PCCCH.... Packet Common Control Channel TDMA .....Time Division Multiple Access
PCH ....... Paging Channel TLLI .......Temporary Logical Link Identity
PCM....... Pulse Code Modulation TMN .......Telecommunication Management Network
PCU ....... Packet Control Unit TRX .......Transceiver
PDA ....... Personal Data Assistant TS .........Timeslot
PDCH ..... Packet Data Channel TU.........Typical Urban
PDTCH.... Packet Data Traffic Channel U
PDP ....... Packet Data Protocol UDP .......User Datagram Protocol
PDN ....... Packet Data Network UMTS......Universal Mobile Telecommunication System
PDU ....... Protocol Data Unit USF........Uplink State Flag
PLMN ..... Public Land Mobile Network
V
PPCH ..... Packet Paging Channel
PPP ....... Point to Point Protocol VLR........Visitor Location Register
PSK ....... Phase Shift Keying VPLMN ....Visited PLMN
PTM....... Point-To-Multipoint VoIP .......Voice over IP
PTM-G .... Point-To-Multipoint Group W
PTM-M .... Point-To-Multipoint Multicast WAP.......Wireless Application Protocol
PTP ....... Point-To-Point www ......World Wide Web

End of DOCUMENT


Intro To Edge-Gprs

Caricato da

Informazioni sul documento

Titolo originale

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

Intro To Edge-Gprs

Caricato da

Copyright:

Formati disponibili

Introduction to GPRS and EGPRS

Introduction to GPRS and EGPRS/EDGE

Alcatel-Lucent File Reference Date Edition Page

3. GPRS/EGPRS ARCHITECTURE .............................................................. 7

4. NOW, HOW DOES IT WORK ? .............................................................11

5. THE PHYSICAL LAYER......................................................................25

6. NETWORK COVERAGE AND THROUGHPUT .............................................35

7. TRAFFIC ASPECT ...........................................................................47

8. INTERFACES AND TRANSMISSION ASPECTS ............................................50

Notice of proprietary information

Alcatel-Lucent File Reference Date Edition Page

This document can be grouped into four parts:

A reasonable knowledge of telecommunications and conventional (circuit-switched) GSM systems is

Please note that this document contains preliminary information:

Alcatel-Lucent File Reference Date Edition Page

2. SETTING THE SCENE

With GPRS, a new entity is

contains the major part of BSC MFS Gb

Alcatel-Lucent File Reference Date Edition Page

Alcatel-Lucent File Reference Date Edition Page

2.2 Why all that effort ?

Because of the Internet. There are big expectations on the potential of

A packet mode transmission allows other users to reuse the transmission

The ultimate evolution step will be the availability of services similar to

But what is ultimate ? Some engineers already started discussing about

Alcatel-Lucent File Reference Date Edition Page

Serving GPRS Support Node (SGSN),

Gateway GPRS Support Node (GGSN),

GPRS Backbone Network.

Packet-switched services Gn GPRS Gi Internet

Alcatel-Lucent File Reference Date Edition Page

Alcatel-Lucent File Reference Date Edition Page

3.2 GPRS network elements

3.2.1 Alcatel BSS solution

Protocol Data Unit (PDU) segmentation/re-assembly,

Channel access control,

Radio channel management,

Packet Data Channel (PDCH) scheduling,

Transmission error detection,

Automatic request for repetition (ARQ).

Alcatel-Lucent File Reference Date Edition Page

3.2.2 Alcatel NSS solution

Serving GPRS Support Node

Gateway GPRS Support Node:

Alcatel-Lucent File Reference Date Edition Page

4. NOW, HOW DOES IT WORK ?

z A WAP-server for services offered by the

4.1 The processes

The Session Management (SM)

The GPRS Mobility Management (GMM)

The Radio Resource Management (RRM)

4.1.1 Connecting to GPRS

Alcatel-Lucent File Reference Date Edition Page

Initiation of a session (Session management SM)

Activation of a Packet Data Protocol (PDP) context (SM)

The PDP type (IPv4 for example)

The PDP address of the mobile

Alcatel-Lucent File Reference Date Edition Page

4.1.2 The STANDBY state

4.1.3 Temporary Block Flow

A TBF is an uni-directional link.

Alcatel-Lucent File Reference Date Edition Page

Uplink TBF TBF