GPRS Technology, Planning and Optimisation

Copyright 2005 AIRCOM International Ltd
All rights reserved

AIRCOM Training is committed to providing our customers with quality instructor led
Telecommunications Training.

This documentation is protected by copyright. No part of the contents of this
documentation may be reproduced in any form, or by any means, without the prior written
consent of AIRCOM International.

Document Number: PS/TR/003/P015/4.2a

This manual prepared by: AIRCOM International Limited
Grosvenor House
65-71 London Road
Redhill, Surrey RH1 1LQ
ENGLAND

Telephone: +44 (0) 1737 775700
Support Hotline: +44 (0) 1737 775777
Fax: +44 (0) 1737 775770
Web: http://www.aircom.co.uk

GPRS Technology,
Planning and Optimisation

Table of Contents

1. Concepts
1.1 Introduction.................................................................................................................... 1
1.2 Circuit and Packet Switching......................................................................................... 2
1.3 Packet Switching Technologies .................................................................................... 6
1.4 Virtual Circuits ............................................................................................................... 8
1.5 Forward and Backward Error Correction....................................................................... 9

2. Mobile Data Evolution
2.1 Introduction.................................................................................................................. 11
2.2 The Requirement for Mobile Data............................................................................... 12
2.3 Other Current and Emerging Mobile Data Technologies............................................ 13
2.4 HSCSD........................................................................................................................ 16
2.5 EDGE .......................................................................................................................... 17

3. GPRS Overview
3.1 Introduction ................................................................................................................. 19
3.2 Review of GSM Architecture. ...................................................................................... 20
3.3 What is GPRS? ........................................................................................................... 21
3.4 GPRS Network Architecture........................................................................................ 23
3.5 Key User and Network Enhancements ....................................................................... 24
3.6 Limitations of GPRS.................................................................................................... 26
3.7 Current Global GPRS Deployment ............................................................................. 28
3.8 Useful Internet Information Resources........................................................................ 30

4. Architecture and Interfaces
4.1 Introduction.................................................................................................................. 33
4.2 Elements of the GPRS Network.................................................................................. 34
4.3 GPRS Mobile Station Modifications ............................................................................ 35
4.4 BSS Modifications for GPRS....................................................................................... 41
4.5 GPRS Core Network Elements................................................................................... 45
4.6 GPRS-Associated Interfaces ...................................................................................... 50

5. The GPRS Air Interface
5.1 Introduction.................................................................................................................. 53
5.2 GSM/GPRS Physical Channels .................................................................................. 54
5.3 GPRS Multiframe Structure......................................................................................... 58
5.4 GPRS Logical Channels ............................................................................................. 59
5.5 GPRS Coding Schemes.............................................................................................. 65

6. GPRS Protocols Overview
6.1 Introduction.................................................................................................................. 73
6.2 Protocols and the ISO 7-Layer OSI Model.................................................................. 74
6.3 Protocol Stacks and the ISO 7-Layer Model ............................................................... 76
6.4 Protocol Encapsulation .............................................................................................. 78
6.5 Data Tunnelling .......................................................................................................... 79
6.6 GPRS Protocol Stacks ................................................................................................ 80

GPRS Technology for Engineers
AIRCOM International 2002
i

7. GPRS Protocols
7.1 Introduction.................................................................................................................. 85
7.2 The MS-BSS U
m
(Air) Interface................................................................................... 86
7.3 The BSS-SGSN G
b
Interface .................................................................................... 110
7.4 The SGSN-GGSN G
n
Interface................................................................................. 118
7.5 Transmission Protocol Summary .............................................................................. 125
7.6 GPRS Signalling........................................................................................................ 126

8. Mobility Management
8.1 Introduction................................................................................................................ 131
8.2 Mobility Management (MM) States ........................................................................... 132
8.3 GPRS Attach/Detach Procedures............................................................................. 135
8.4 Routing Areas............................................................................................................ 142
8.5 Location Management............................................................................................... 145
8.6 Paging ....................................................................................................................... 153
8.7 Cell Reselection. ....................................................................................................... 155

9. Radio Resource Management
9.1 Introduction................................................................................................................ 157
9.2 Traffic Timeslot Allocation......................................................................................... 158
9.3 Temporary Block Flows (TBFs)................................................................................. 162
9.4 Uplink Packet Access Procedure.............................................................................. 166
9.5 Downlink Packet Access Procedure ......................................................................... 168
9.6 Radio Resource Operating Modes............................................................................ 171

10. Packet Routing and Transfer
10.1 Introduction.............................................................................................................. 175
10.2 Packet Data Protocol (PDP) States ........................................................................ 176
10.3 PDP Contexts and Addresses................................................................................. 177
10.4 Access Point Names (APNs) .................................................................................. 178
10.5 PDP Context Activation/Deactivation...................................................................... 180
10.6 Effect of MM States on Packet Transfer ................................................................. 188
10.7 Packet Transfer Functions ...................................................................................... 189

11. GPRS Operational Issues
11.1 Introduction.............................................................................................................. 195
11.2 Subscriber Services ................................................................................................ 196
11.3 Quality of Service (QoS) ......................................................................................... 197
11.4 GPRS Security ........................................................................................................ 204
11.5 Billing....................................................................................................................... 212

12. Interactions With GSM Services
12.1 Introduction.............................................................................................................. 217
12.2 Interactions Between the SGSN and MSC/VLR..................................................... 218
12.3 Network Operating Modes ...................................................................................... 219
12.4 Combined IMSI/GPRS Attach/Detach..................................................................... 221
12.5 Combined RA/LA Location Updating ...................................................................... 225
12.6 Paging Coordination................................................................................................ 230

ii

13. GPRS Internetworking
13.1 Introduction.............................................................................................................. 233
13.2 The Interworking Interfaces..................................................................................... 234
13.3 The G
i
Interface - IP Connection............................................................................. 235
13.4 The G
i
Interface - X.25 Connection......................................................................... 237
13.5 The Inter -PLMN G
p
Interface.................................................................................. 239

14. GPRS Planning
14.1 Introduction.............................................................................................................. 254
14.2 Channel Coding Schemes ...................................................................................... 256
14.3 Data Rate Arrays..................................................................................................... 257
14.4 Planning for GPRS.................................................................................................. 258
14.5 EDGE ...................................................................................................................... 264

15. The Optimisation Process
15.1 Introduction.............................................................................................................. 269
15.2 Requirements for Optimisation................................................................................ 271
15.3 Outline The Optimisation Process........................................................................... 273
15.4 Network Audit Phase............................................................................................... 275
15.5 Network Performance Review................................................................................. 278
15.6 Activity Phase of Optimisation................................................................................. 280

16. BSS Optimisation Activities
16.1 Introduction.............................................................................................................. 281
16.2 BSS Parameter Review .......................................................................................... 282
16.3 Identify and Fix Hardware Problems....................................................................... 284
16.4 Identify and Fix Neighbour Problems...................................................................... 285
16.5 Identify and Fix Frequency Plan Problems ............................................................. 286

17. NSS Characteristics
17.1 Introduction.............................................................................................................. 287
17.2 NSS Topology ......................................................................................................... 288
17.3 Overview of C7 Signalling....................................................................................... 291

18. NSS Optimisation and Parameter Evaluation
18.1 Introduction.............................................................................................................. 293
18.2 NSS Optimisation Process...................................................................................... 294
18.3 C7 Signal Routing Analysis..................................................................................... 295
18.4 Signalling Link Load Evaluation .............................................................................. 296
18.5 Traffic Loading Evaluation....................................................................................... 297
18.6 NSS Parameter Evaluation ..................................................................................... 298
18.7 NSS Database Usage Evaluation ........................................................................... 299

19. Dimensioning Networks
19.1 Introduction.............................................................................................................. 301
19.2 Multi-Service Dimensioning..................................................................................... 301
19.3 Mixing Packet and Circuit Switched traffic .............................................................. 304
19.4 GPRS Performance Monitoring............................................................................... 306

20. Case Study using ASSET
20.1 Introduction.............................................................................................................. 307
20.2 GPRS Overview...................................................................................................... 308
20.3 Configuring ASSET for GPRS Planning.................................................................. 311

iii

iv

1. Concepts


1. Concepts

________________________________________________________________________________
1.1 Introduction

The Concepts section of the course provides an overview of a number of technological
concepts, the understanding of which is necessary in order to fully understand the concepts
of GPRS. These technologies include:

Circuit and packet switching
Packet switching technologies
Virtual circuits
Forward and backward error correction

________________________________________________________________________________
1.2 Circuit Switching and Packet Switching

Circuit Switching Circuit Switching
CIRCUIT CIRCUIT CIRCUIT CIRCUIT
SWITCH SWITCH
SWITCH SWITCH
CIRCUIT CIRCUIT
SWITCH SWITCH
CIRCUIT CIRCUIT
SWITCH SWITCH
CIRCUIT CIRCUIT
SWITCH SWITCH

Circuit switching was the traditional method of establishing a connection between two voice
end users over a communications network such as the Public Switched Telephone Network
(PSTN).

1

1. Concepts

2
A circuit is established over the network at the start of a session and remains in place until
the call is terminated, at which point the allocated resources are released back to the
network.

The advantage of circuit switching is the connection generally remains uninterrupted with a
guaranteed quality of service for the duration of the session.

However, if the traffic on this path passed is not constant, as is the case with voice and
asynchronous data, the circuit is not in use fully for 100% of the time. If other users were
able to utilise the spare capacity of the network resources when not being used by the end
users, the efficient use of the communications path could be enhanced. This can be achieved
by using packet-switching technology.

Packet Switching Packet Switching
1 2 3 4 5
1
2
3
5
4
PACKET PACKET
ASSEMBLER/ ASSEMBLER/
DISASSEMBLER DISASSEMBLER
PACKET SWITCH PACKET SWITCH
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH
1 3 2
1 3 2 1 2 3
1 2 3
1
2
1
2 3
1
3
2
1
2 3
3
2
1
3
1
3
2

ata blocks (known as packets) between end-users
the data stream down in data blocks of a pre-defined size
(depending on the packet switching technology employed, adds routing information to each
packet and forwards them to the local packet switch. Based on this routing information, the
type of circuit established (see below) and the current network link availability, the Packet
Switch will forward each packet towards its eventual destination.

Packet switching is the transmission of d
ver a communications network. o

The data stream generated by an end user is passed to a Packet Assembler/ Disassembler
(PAD). The PAD breaks

1. Concepts

Advantages of Packet Switching Advantages of Packet Switching
More efficient use of existing bearers
More suited to bursty-type traffic such as
Internet access.
Compatibility with existing packet-switched
networks (PSNs) such as the Internet

Packet switching has a number of advantages over circuit switching:
gle bearer (as demand dictates)
ore efficient use can be made of available bandwidth.
this call is
se of Internet browsing, the channel will only be used for short intermittent
ursts (queries) and occasional short heavy usage (downloads). For the remainder of the

GSM network will simplify interfacing

By multiplexing the packets from several users into a sin
m

Circuit Switching requires a circuit to be established for the duration of the call. If
for the purpo
b
time the channel is idle. During these idle periods, the packets from other users with similar
traffic requirements can be transmitted.

Many data transport networks use packet switching for efficient data transfer, for example
the Internet. The use of packet switching within the
to such data networks.
3

1. Concepts

4
Advantages of Circuit Switching Advantages of Circuit Switching
More suited to time-sensitive applications
No contention for network resources
Less data overheads for routing requirements
Compatibility with existing circuit-switched
networks (eg PSTN/ISDN)

Whilst packet switching seems to have many advantages over circuit switching, circuit
switching still has advantages in certain circumstances.

Where time is critical to many real-time applications such as video streaming, a direct
connection between end users can better guarantee delivery times and consistent
throughput.

Having established a circuit across the network, the resources of that circuit are dedicated to
the end-users and not shared with other users as with packet switching.

As the data has a fixed start-point and end-point, data travels point-to-point and does not
require the same routing overheads as packet data.
GSM circuit switching is more directly compatible with external circuit-switched
communications networks such as PSTN/ISDN.

1. Concepts

Packet Routing Strategies Packet Routing Strategies
Connection-Orientated (CONS):
Packet route established prior to data transfer
No guarantee of delivery
Difficult to implement QoS

:
onnection-Orientated
Supports flow control
Supports QoS functions
Connectionless (CNLS)
No predefined route - packets routed individually

These data packets are transported across the packet network by one of two methods

C . A route is first established across the network between end users.
e is then used by all data blocks whilst the virtual circuit is maintained.
ata
roughput.
This rout
Consequently no routing decision is needed for every cell, thereby speeding d
th

Connectionless. In a connectionless environment, packets are released into the packet
network and each is routed according to the most efficient route at that instant in t
may be the case that the route chosen by the switc
ime. It
h for one packet may not be the most
ppropriate for the following packet due to a change in network conditions. Therefore, the
routes across the network. This may result in packets arriving at the distant
end PAD in a sequence different from the transmitted sequence. Each packet must therefore
also contain sequencing information so that the destination PAD is able to re-sequence the
packets into the original order before passing the re-assembled data to the receiving end
user.
a
packets comprising a particular set of data will be transmitted to the destination end user
using different

5

1. Concepts

6
Packet Data Delivery Packet Data Delivery
Acknowledged Mode:
Guarantees error-free delivery
Supports flow control
Requires additional overheads
Lower data throughput
Unacknowledged Mode
Packets are delivered to the network and forgotten
No indication of delivery or error correction
Generally relies on higher layer protocols for error
detection and correction
More efficient in reliable networks

________________________________________________________________________________
.3 Packet Switching Technologies 1

Packet Switching Technologies Packet Switching Technologies
X.25
Frame Relay
ATM
X.25 Fr Relay ATM
256kbps <2Mbps >45Mbps
Switching Type CNLS CNLS CONS
Transmission Speed <
Data Block Size Var Var 53 octets
Block Header+Trailer 6 octets 7 octets 5 octets
Payload Size Var Var 48 octets

1. Concepts

7

X.25

.
The first widespread deployment of a packet switching technology was X.25, deployed
during the 70s.
s Interconnection (OSI)
sation (ISO). X.25 is
very reliable as it was originally designed to work over variable quality bearers.

It employs a node-by-node store and forward system for error detection and correction
(ED&C). However, this requires significant buffer space and introduces significant delays at
each node.

Frame Relay

This protocol encompasses the first three layers of the Open System
7-layered architecture as defined by the International Standards Organi
.
Frame Relay was developed in the early 90s as a faster version of packet switching that
takes advantage for the more reliable modern bearer networks.

Unlike X.25, Frame Relay leaves the end terminals to carry out error detection and
correction. Therefore, the requirement for store & forward buffering and ED&C processing
at each node is eliminated.

This enables significantly high data rates, up to 2Mbps (Europe) or 1.544Mbps (US).

ATM.
Asynchronous Transfer Mode is a natural progression from Frame Relay.

It differs significantly from Frame relay in that it uses fixed length packets and operates only
over switched or permanent virtual circuits. This enables the ATM nodes to switch packets
almost instantaneously with little processing involved. As a result, it operates at
significantly higher data rates than Frame Relay.

ATM has been selected as the packet-switching technology to be employed for the 3G UMTS
core network.

1. Concepts

8

________________________________________________________________________________
1.4 Virtual Circuits

The Virtual Circuit (VC) Concept The Virtual Circuit (VC) Concept
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH
1 3 2
1 3 2 1 2 3
1 2 3
1
2
1
2
3
3
1
2
1
2 3
3
2
1
3
1
3
2
Virtual Circuit Virtual Circuit
Virtual Circuit Virtual Circuit

When two users are linked together across a network by a dedicated, physical connection,
this is refereed to as a physical circuit. Physical circuits are the common mode of connection
over voice-orientated networks such as the Public Switched Telephone Network (PSTN).

However, data-orientated networks are now predominantly packet-switched. In such
networks, users are not connected by dedicated physical links but rather by a sequence of
data packets. These data packets could individually take different routes along shared
channels between the source and destination. Whilst two users appear to be physically
linked across the network, the route taken by data packets may vary throughout the data
transfer session. This type of connection is referred to as a virtual circuit (VC) i.e. it appears
to the user to be a physical connection but in reality is not.

There are two main types of virtual circuits:

Permanent Virtual Circuits (PVCs). Network resources allocated permanently to a specific
pair of end users. Similar in concept to leased lines on circuit-switched networks.

Switched Virtual Circuits (SVCs). Network resources allocated temporarily to users to
meet their traffic demands. This is similar in concept to dial-up telephone connections on
circuit-switched networks.

1. Concepts

9

Virtual Circuit Connections Virtual Circuit Connections
Permanent Virtual Circuit (PVC):
Established by NMC
Dedicated resource for specific user
Connectionl s
Switched Virtual Circuit (SVC):
Setup on request
Temporary allocation of resources
Cleared on completion of session

________________________________________________________________________________
1.5 Forward & Backward Error Correction

es

Forward and Backward Error Corre Forward and Backward Error Cor ction rection
Backward Error Correction:
Errors detected by BCS/FCS
Correction by retransmission
/convolution encoding
ts and corrects errors at far end

Far end checks for errors
Forward Error Correction:

Source data block/convolution encoded
Far end reverses block
Coding method detec

1. Concepts

10

Summary Summary Sectio Section 1 n 1
Circuit and Packet S itching
CONS, CNLS, Ack/Unack Modes
Packet Switching Technologies
X.25, Frame Relay, ATM
Virtual Circuits
PVCs, SVCs
Forward and Backward Error Correction
Block Error Detection, ARQ, Convolution Coding
w
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH
PACKET
SWITCH


11

. Mobile Data Evolution
________________________________________________________________________________
2.1 Introduction

This Mobile Data Evolution section of the course provides an overview of how GSM
technology has evolved to enhance its capability for carrying increasingly higher speed data.
The topics covered in this section include:

The requirement for mobile data
Current mobile data technologies
Emerging mobile data technologies
HSCSD
EDGE (ECSD/EGPRS)
UMTS data capabilities

2


12

________________________________________________________________________________
2.2 The Requirement for Mobile Data

The Requirement for Mobile Data The Requirement for Mobile Data
Projected increase in demand for data traffic
Requirement to develop additional revenue-generating
streams
Exponential growth in Internet Access
Demand for Internet access on the move.
Evolution towards 3G services

Until recently, voice has been the primary driver in mobile communications. Typically,
SM operators today have portfolios of, at most, a dozen voice-related services. This is set
change dramatically. Most operators estimate that at the launch of 3G they will have
ortfolios of up to 500 services of all types.

and
-switched (IP) networks.

wealth of new service opportunities inconceivable with 2G
networks through the seamless integration of voice, data and IP Multimedia services.
The shift from voice to multimedia applications will also change the way that
operators conduct their business. New players, such as content providers
and application developers, will contribute to deliver the benefits of the
mobile Internet to the user.
G
to
p

Booming applications will demand fundamental changes in core network technology. 3G
will launch using both circuit- and packet-switched technology, but it is predicted that by
2005 packet switching traffic will exceed circuit switching in the mobility core networks,
operators will be moving quickly towards fully packet

This is with good reason. IP networks are more efficient and less costly to run and maintain.
In addition, IP networks bring a



The Requirement for Mobile Data The Requirement for Mobile Data
5
10
15
20
25
30
35
40
45
Mbytes/month
96 98 00 02 04
Circuit Switched Packet Switched

Tec

Until recently, the only data service widely available on GSM has been Circuit-Switched
Data (CSD) which is limited to a single timeslo and a raw data throughput of 9.6kbps.
CSD has subsequently been improved to achieve data rates of 14.4kbps by removing some of
the Radio Control Protocol (RCP) overheads associated with error protection over the air
interface.

The Short Message Service (SMS) is a data capability for transmitting short messages of up
to 160 characters over the GSM network without adversely affecting the traffic capacity over
the air interface. This is achieved by using spare capacity on the control channels for
transmitting these messages. SMS is similar to packet switching in that its route is not pre-
determined and it incorporates a store-and-forward facility whereby messages are stored
until the recipient is available to receive them

________________________________________________________________________________
2.3 Other Current and Emerging Mobile Data
hnologies

t
13


14

GSM Phase 1 & 2 Data Services GSM Phase 1 & 2 Data Services
9.6kbps CSD 9.6kbps CSD
14.4kbps CSD 14.4kbps CSD
USSD USSD
SMS SMS

Unstructured Supplementary Service Data (USSD) is a data capability within the GSM
system for transmitting information over the signalling channels. Unlike SMS, USSD is
session-oriented and establishes an association between source and destination for passa
of data messages and is therefore quicker than SMS. However, it does not support the st
ge
ore-
and-forward capability associated with SMS.

Emerging Mobile Data Technologies Emerging Mobile Data Technologies
3 3
rd rd
Generation Generation
2 2
nd nd
Generation Generation
2
.
5

G
e
n
e
r
a
t
2
.
5

G
e
n
e
r
a
t
i
o
n
i
o
n
CSD
GPRS
HSCSD
ECSD
UMTS
14.4 kb/s
21.4 kb/s
69.2 kb/s
384 kb/s
2 Mb/s
EGPRS
EDGE EDGE
SMS
CSD 9.6 kb/s
Circuit Switched
Packet Switched
38.8 kb/s


15

A number of new data technologies are emerging that utilise the GSM system as a bearer
infrastructure and significantly increase system data capabilities. These are collectively
known as 2.5 Generation technologies and include High Speed Circuit Switched Data
(HSCSD) and General Packet Radio Service (GPRS).

Both HSCSD and GPRS have the ability to simultaneously use multiple timeslots to increase
the effective data throughput.


16

________________________________________________________________________________
2.4 High Speed Circuit Switched Data (HSCSD)

HSCSD can utilise up to 4 timeslots at .4 kbps per timeslot giving a maximum theoretical
raw data rate of 57.6kbps. Currently only Orange provide a consumer HSCSD service in the
UK which operates on a 2-timeslot basis providing up to 28.8kbps raw data throughput.

14
HSCSD HSCSD
Increases bit rate for GSM by a mainly
software upgrade
Uses multiple GSM channel coding
schemes to give 4.8 kb/s, 9.6 kb/s or 14.4
kb/s per timeslot
Multiple timeslots for a connection
e.g. using two timeslots gives data rates
up to 28.8 kb/s
Timeslots may be symmetrical or
asymmetrical, e.g. two downlink, one
uplink, giving 28.8 kb/s downloads but 14.4
kb/s uploads.
Maximum data rate quoted as Maximum data rate quoted as
115 kb/s = 14.4 x 8 115 kb/s = 14.4 x 8

HSCSD Mobile Equipment HSCSD Mobile Equipment
HSCSD handsets are typically limited to 4
timeslots, allowing:
2 up / 2 down (28.8 kb/s in both directions)
3 down and 1 up (43.2 kb/s down 14.4 kb/s up)
This limitation arises because the handset
operates in half duplex and needs time to change
between transmit and receive modes
Nokia cardphone (PCMCIA card for laptops) uses
HSCSD (Orange network)
- quotes data downloads at 28.8 kb/s


17

________________________________________________________________________________
2.5 Enhanced Data Rates for GSM Evolution (EDGE)

Enhanced Data rates for GSM Evolution (EDGE) is a new technology that can be applied to
the air interface to increase the raw da throughput. This is achieved by introducing a new
modulation scheme (8PSK) that can tri le the data throughput. It also provides adaptive
channel coding to match the current radio path quality. EDGE also introduced new coding
schemes for HSCSD (called ECSD) and GPRS (called EGPRS) to accompany the new
modulation scheme. EDGE can increa the raw data throughput to 38.8kbps per HSCSD
timeslot or 69.2kbps per GPRS timeslot.

ta
p
se

EDGE EDGE
Enhanced Data rates for GSM Evolution
Use 8 Phase-Shift Keying (8PSK) modulation
- 3 bits per symbol
Improved link control allows the system to adapt
to variable channel quality
Applied to a GSM channel ra of 271ks te ps, EDGE allows a
maximum data rate of 48 kb per timeslot, giving the quoted
figure of 384 kb/s per carrier timeslots)
EDGE can be applied to HSCSD (ECSD) and GPRS
(EGPRS)
EDGE will be expensive for operators to implement:
Each base station will require a new EDGE transceiver
be upgraded
(0,0,0)
(0,0,1)
(0,1,1)
(0,1,0)
(1,1,0)
(1,1,1)
(1,0,1)
(1,0,0)
/s
(8
Abis interface between BTS and BSC must
New EDGE-enabled handsets required


18

Summary Summary Section 2 Section 2
Requirement for Mobile Data
CONS, CNLS, Ack/Unack Modes
Current Mobile Data Technologies
CSD(9k6), CSD(14k4), USSD, SMS
Emerging Mobile Data Technologies
HSCSD, EDGE
GPRS
HSCSD
ECSD
UMTS
EGPRS
EDGE EDGE
SMS
CSD

3. GPRS Overview

19

. GPRS Overview
.1 Introduction

This section of the course provides an overview of GPRS, explaining in outline the concepts
and capabilities of GPRS prior to discussing each aspect in detail later in the course. The
topics covered include:

A review of GSM Architecture
An conceptual explanation of what GPRS is
GPRS network architecture overview
Key user and network enhancements
Limitations of GPRS
Current global GPRS deployment
Some useful Internet sites for additional GPRS information

3

________________________________________________________________________________
3

3. GPRS Overview

20

________________________________________________________________________________
3.2 Review of GSM Architecture

VLR VLR
GSM Architecture Overview GSM Architecture Overview
BTS BTS
BSC BSC
HLR HLR
MSC MSC
AuC AuC
EIR EIR
PSTN PSTN
TRX TRX
Air Interface Air Interface
(Um) (Um)
BSS BSS
OMC OMC
A Interface A Interface
Abis Abis Interface Interface
MS MS
MS MS
MS MS

up of three subsystems:
iated databases
TS (antenna) and the MS
Station Sub-system
Register
VLR Visitor Location Register
AuC Authentication Centre
EIR Equipment Identity Register
entre
Network

A GSM network is made
The Mobile Station (MS)
The Base Station Sub-system (BSS) comprising a BSC and several BTSs
The Network Switching Sub-system (NSS) comprising an MSC and assoc

Several interfaces are defined between different parts of the system:
The A interface between MSC and BSC
SC and BTS The Abis interface between B
The Um air interface between the B

bbreviations: A
MSC Mobile Switching Centre BSS Base
HLR Home Location BSC Base Station Controller
BTS Base Transceiver Station
TRX Transceiver
MS - Mobile Station

tenance C OMC Operations and Main
STN Public Switched Telephone P

3. GPRS Overview

21
__________________
3.3 What is GPRS?

_________________________________________ ____________________ _

What is GPRS? What is GPRS?
Packet-switching technology
Transparent end-to-end data transport of data
packets over a modified GSM network

Shares Radio Resources with GSM
New GPRS core network distinct from GSM

GPRS GPRS - - Conceptual View Conceptual View
GPRS GPRS
IP Core IP Core
Internet Internet
BSS BSS
Shared GSM/GPRS Shared GSM/GPRS
Infrastructure Infrastructure
GPRS Core GPRS Core
Infrastructure Infrastructure
IP Environment IP Environment

3. GPRS Overview

22

GPRS Features GPRS Features
Introduces new air interface coding schemes
Introduces Quality of Service (QoS) profiles
Supports low and high speed (9.6-171.2kbps) data
Supports various data transfer types (CONS/CNLS
- ACK/UNACK)
Supports multiple Packet Data Protocols (PDPs)
Supports SMS over GPRS
Allows for shared usage of GSM control functions

Phase 1:
TCP/IP and X.25 bearer services
GPRS-specific encryption algorithms
tor functions
ices
Additional Network Interfaces
2 2

GPRS Phases 1 and GPRS Phases 1 and
Opera
SMS Support
Packet Charging Support
Phase 2:
Additional PTP services
PTM Serv
Additional Supplementary services

3. GPRS Overview

23

In order to manage the complexity of implementing GPRS, ETSI has defined two
implementation phases. The first phase includes all the elements to provide a functional
packet-switched service:

Phase1: Officially finalised in Q1/1998
Connectionless (IP) and connection-oriented (X.25) packet data services.
New GPRS Network Identities (inc static and/or dynamic IP addressing)
Independent GPRS security, using a new ciphering algorithm especially tailored for packet
data.
Operator call barring and termination, operator call screening
Support for SMS over GPRS
lling Support for GPRS-specific bi
Limited QoS

Phase 2. Work still ongoing but currently include:
Point-to-Multipoint Services
GPRS Mobile IP Interworking
GPRS Modem and ISDN Interworking
Enhanced QoS support
ew Charging and billing procedures N
Access to ISPs and Intranets

Note that whilst all the above are listed by ETSI as GPRS Phase 2 Work Items, they may not
all be implemented.

________________________________________________________________________________
3.4 GPRS Network Architecture Overview

GPRS Architecture Overview GPRS Architecture Overview
BTS BTS BSC BSC
HLR HLR
SGSN SGSN
VLR VLR
Internet Internet
EIR EIR
TRX TRX
BSS BSS
MS MS
MS MS
GGSN GGSN
MSC MSC
SMS SMS
GMSC GMSC
PLMN PLMN
PCU PCU
GPRS CORE NETWORK GPRS CORE NETWORK
MS MS
traffic traffic
signalling signalling

3. GPRS Overview

24

When defining a modern communications system, it is common practice to first define the
lements of the system and then define how these elements intercommunicate.
or's perspective, the process of transporting GPRS packet data from a mobile
The Mobile Subscriber (MS) being able to create packet data and pass it over the air
interface to the Base Station Subsystem (BSS) and to receive packet data.
icate with, and pass these packets into and out of the

st intercommunicate:
SGSN - Serving GPRS Support Node
GGSN - Gateway GPRS Support Node
SMS GMSC Short Message Service Gateway Mobile Switching Centre
PCU - Packet Control Unit

In order effect the intercommunication of these entities, protocols must be established. These
protocols are defined in the form of interface specifications, which will be described later in
this section.

________________________________________________________________________________
3.5 Key User and Network Enhancements

3.5.1 KEY USER ENHANCEMENTS
e

From an operat
user to a distant location (and receiving packet data from that location) requires 3 basic
entities to interact. These are:

The BSS being able to commun
GPRS core network.
The GPRS Core network being able to reliably transport the data packets end-to-end.
To achieve the above objectives, a number of GPRS-specific entities mu

Speed
Immediacy
Simultaneity
New and Improved Applications
Affordability (?)
Key GPRS User Enhancements Key GPRS User Enhancements

3. GPRS Overview

25

Speed.
GPRS has a theoretical maximum data throughput of 171.2 k
than is generally available to consumers over the public telephone
bps. This is about 3 times faster
network and ten times
faster that standard GSM Circuit Switched Data.

mediacy Im
GPRS is effectively always on subject to coverage and therefore data can be sent and
received without the need to dial-up the intended recipient.

Simultaneity
Using the cor d ob e Te pes) it a calls
multaneously wh transferrin PR

Improved Application
rect GPRS Mo e (see M il rminal Ty is possible to m ke voice
si ilst g G S packet data.
New and s
T
ap
he potential incre in data rat avail PRS enable more bandwidt intensive
plications (such ideo strea g) t e m o the GSM network.
These applications were not suit o th mo ent in the due to the low data
rates available through CSD. GP also nab ive use to be made of existing
such as SM nd WAP.
ffordabilit
ase es able through G
d ont
h-
as v min o b igrate
ed t e bile environm past
RS e les more effect
services S a

A y
GPRS Services will ve to be priced at ve ey are attracti to consum s but
to recover infrastructur nves en on, billing tar s will have be
ly flexible meet a wide range of u s.

.5.2 KEY NET ORK EN ANC M
ha a le
tm
l where th
t. In additi
ve
iff
er
to sufficient
sufficient
e i
to ser requirement
3 W H E ENTS

Packet Switching
Radio Resource Efficient
Dynamic Resource Allocation
Internet Aware
Key GPRS Netw Enhancem nts Key GPRS Netw Enhancem nts

ork ork e e

3. GPRS Overview

26

Packet Switching
GPRS involves overlaying a packet-switched network on top of the existing GSM network.
This enables a user to choose between circuit-switched or packet-switched services. The user
information is split into separate but related packets and transported over the packet network,
not necessarily all via the same route. At the receiving location, the packets are re-sequenced
and reassembled before being presented to the intended recipient. The Internet operates in a
similar fashion.

Radio Resource Efficiency
GSM Circuit Switched Data (CSD) technology requires a dedicated channel to be allocated for
the passage of data in a similar fashion to a voice call. It is often the case that data is not being
passed over this circuit all the time, for example when typing a message on-line. However,
GPRS only sends data packets when they are required to be sent. This allows several users to
share a single channel for passing packet data. This means that potentially more GPRS users
can access the network without increasing the network resources required, although this
depends on the application being used and the data rates required.

Flexible timeslot allocation allows resource usage to be maximises by dynamically allocating
timeslots to voice or data as demand requires. Three new GPRS coding schemes allow the
packet data rates to be varied according to radio path quality. In addition, 3 new network
operation modes allow paging messages for both packet-switched (PS) and circuit-switched
(CS) to use the same paging channel.

Internet Aware
Currently, the only Internet access available to mobile users is via WAP and this is restricted
to WAP-enabled Web sites. The advent of GPRS has the potential to provide mobile users
with the full range of Internet services currently available to computer users. GPRS uses the
same protocols as the Internet (TCP/IP). This, together with the adoption of the Mobile IP
protocols (see later in course), will enable mobile users to potentially have their own IP
addresses and become sub-nets of the Internet.
_______________________________________________________________________________
.6 Limitations of GPRS
Slower Data Rates Than Anticipated

_
3

In order to achieve the theoretical maximum data rates would require a single user to be
allocated all 8 timeslots on specific air interface carrier without error protection. This is
unlikely to happen for several reasons:
It is unlikely that an operator will allocate all 8 timeslots per carrier to data.

Most planned GPRS handsets will only support up to 3 timeslots.
rough the As a result, the theoretical data rates are only likely to be achieved th
implementation of EDGE or UMTS.

3. GPRS Overview

27

Cell Capacity
Althoug ndant capacity on the air interface, it may require the
possibly at the expense of voice users. A conflict may arise between the
service sers and those of GPRS data users.

h GPRS can utilise redu
allocation of timeslots
level required by voice u

Sub-Optimal Modulation Technique
C Air interface modulation uses Gaus urrent sian Minimum Shift Keying or GMSK (see
odulation Techniques). More efficient modulation techniques are now available (such as
PSK used in EDGE technology) that c icantly increase the available data rates (by a
factor of 3) with no increase in the air interface resource requirements.

M
8 an signif
Slower data rates than anticipated.
Cell capacity.
Sub-optimal modulation technique.
Transit delays.
No store and forward.
Limitations of GPRS Limitations of GPRS

Transit Delays
GPRS availability is limited by network resources and the application of high QoS levels are
resource-intensive and may not be achievable in the early stages of GPRS. It cannot guarantee
the route taken by each packet and the retransmission delays incurred with errored packets.
Therefore, transit delays cannot be guaranteed, making it less suited to real-time applications
than circuit-switched data technologies such as HSCSD.

No Store and Forward.
Unlike SMS, where messages are stored until the recipient is available to receive them, GPRS
makes no such provision. Packets that cannot be delivered are generally discarded.

3. GPRS Overview

28
________________________________________________________________________________
3.7 Current Global GPRS Deployment

.7.1 CURRENT GPRS DEPLOYMENT 3

44 Countries adopting GPRS
78 Operators worldwide with Commercial
GPRS Systems
17 Operators trialling GPRS
(inc UK and USA)
Current GPRS Deployment Current GPRS Deployment

GPRS Implementations Worldwide September 2001 (source: GSM World)
Country Commercial Testing Country Commercial Testing
Australi 2 0 Liechtenstein 1 0 a
Austria 5 0 Lithuania 1 0
Belgium 2 0 Luxembourg 2 0
Bulgaria 1 0 Malaysia 1 0
Canada 1 1 Malta 1 0
China 1 18 Netherlands 3 0
Croatia 2 0 New Zealand 1 0
Czech Republic 2 0 Norway 2 0
Denmark 3 1 Poland 4 0
Estonia 1 0 Portugal 3 0
Finland 3 0 Romania 1 0
French W.Indies 1 0 Russia 1 0
Germany 4 0 Singapore 1 2
Greece 2 1 Slovenia 1 0
Hong Kong 4 0 Spain 2 1
Hungary 2 0 Sweden 3 0
Iceland 0 1 Switzerland 3 0
Ireland 0 1 Taiwan 1 0
Israel 1 0 Turkey 1 2
Italy 4 0 UAE 0 1
Jordan 0 1 UK 2 2
Lebanon 1 0 USA 1 3

3. GPRS Overview

29

.7.2 MOST POPULAR ANTICIPATED GPRS SERVICES 3

1. Corporate Email
2. Internet Email
3. Information Services
4. Job Despatch
5. Remote LAN Access
6. File Transfer
7. Web Browsing
8. Still Images
9. Moving Images
Most Popular GPRS Services Most Popular GPRS Services
Source: GSM World Source: GSM World

3. GPRS Overview

30

________________________________________________________________________________
3.8 Useful Internet Information Resources
European Telecommunications Standa s Institute (ETSI):
www.etsi.portal.org

rd

Mobile Applications Initiative (MAI) Forum:
www.gprsworld.com
Mobile GPRS Forum:
www.mobilegprs.com
GSM Association:
www.gsmworld.com
Palowireless: (useful GPRS information ortal)
www.palowireless.com/gprs
p

GPRS GPRS- -Associated Bodies/Portals Associated Bodies/Portals

3. GPRS Overview

31

Summary Summary Sec Sec
Review of GSM Architectu
tion 3 tion 3
re
Overview of GSM Network Elements
GPRS Features
Phase 1/Phase 2 Introduction
GPRS Network Architecture Overview
Overview of new GPRS network entities
d by GPRS
Useful Internet GPRS Resources
User and Network Enhancements provide
Limitations of GPRS
ployment Current GPRS Global De
BTS BTS BSC BSC
HLR HLR
SGSN SGSN
VL VL
R R
EIR EIR
Internet Internet
TRX TRX
BSS BSS
MS MS
MS MS
MS MS
GGSN GGSN
MSC MSC
SMS SMS
GMSC GMSC
PLMN PLMN
PCU PCU

3. GPRS Overview

32

Intentional Blank Page

4. GPRS Architecture and Interfaces

33

. G
In

________________________________________________________________________________
4.1 Intr

Elements of the GPRS network
Mobile Station GPRS Modifications
GPRS-associated interfaces

PRS Architecture and 4
terfaces
oduction

This section of the course looks in more detail at the elements of the GPRS network from the
mobile Station (MT), across the Base Station Subsystem (BSS) to the core Network Subsystem
(NSS). This section also describes the definitions of the interfaces between each of these
elements. Main areas covered in this section include:
BSS modifications for GPRS
GPRS core network elements


34

________________________________________________________________________________
4.2 Elem

ents of the GPRS Network
Elements of the GPRS Network Elements of the GPRS Network
BTS BTS BSC BSC
SGSN
Inter-PLMN
Network
GPRS GPRS
Backbone Backbone
BG
CG
GGSN
GGSN
Internet
Intranet
NMS
Billing
Centre
LIG
DNS
Router
Server
Corporate LAN
PCU
Core Network Core Network

The following are key elements of the GPRS network:
SGSN - Serving GPRS Support Node
GGSN - Gateway GPRS Support Node
PCU Packet Control Unit

The following are additional elements of the GPRS Network, which have subsidiary roles or
are optional implementations:
CG - Charging Gateway
NMS - Network management Centre
BG - Border Gateway
LIG - Legal Interception Gateway
vide GPRS functionality.
DNS - Domain Name Server

Each of these elements will be described below, together with enhancements required to
existing GSM elements to pro


35
4.3 Mobile Station GPRS Modifications
4.3.1 GPRS TERMINAL DESCRIPTION

________________________________________________________________________________

The combination of a Mobile Eq men ME) d Subs ber Identity Module (SIM) form the
Mobile Station (MS). The TE co i lem by such devices as laptop computers or a
PDA. The MS is the m ile tran eiver d often is a mobile handset or a card-type device.
Note that the MS and TE parts could ac ly f the s e physical piece of equipment.

uip t ( an cri
uld be mp ented
ob sc an
tual orm am
GSM/GPRS Mob SM/GPRS Mobile ile Te inal (MT) G Te inal (MT) rm rm
TE TE
MS MS
Mobil rminal ( Mobil rminal (M
TE - Te al Equip t
TA - T l Adapt
MS - M Station
ME - M Equipm
SIM - S iber Ide Mod
Base Station Base Station
Subsystem Subsystem
S S
e Te e Te MT) T)
rmin men
ermina or
obile
obile ent
ubscr ntity ule
U U
m m
GPRS Core GPRS Core
Network Network
M ME E SIM SIM
TA
Refere oints Refere oints nce P nce P
R R G G
b b

is
,

The above diagram indicates the GPRS access points, reference points and interfaces related to
a mobile station (MS).

The physical interface from a TE to the MS is referred to as the R reference point if no
Terminal Adaptor (TE) is in use or the S reference point if a TE is used. This interface
generally proprietary and could comprise V24/V28, Infrared, USB, Bluetooth or PCMCIA
electrical specification etc.

The TE is the computer terminal that the end-user works on. It is the component used by
GPRS to create, transmit and receive end-user packet data, for example a Personal Digital
ssistant (PDA). GPRS provides IP connectivity between the TE and an ISP or Corporate A
LAN connected to the GPRS network. The IP connection is static from the TE point of view
i.e. the TE is not aware of being mobile and retains its assigned IP address until the MS
detaches.


36

Physical connection to the TE at the R or Physical connection to the TE at the R or
S reference points S reference points
Flow Control between TE and MT Flow Control between TE and MT
Mapping user signalling to/from GPRS Mapping user signalling to/from GPRS
Functions Functions GPRS Mobile Station GPRS Mobile Station
bearer bearer
Functions to support character Functions to support character- - and and
packet packet- -based data based data
Nokia 6310 Nokia 6310
GPRS GPRS- -enabled MT enabled MT

The MS communicates with a TE, and over the air interface with a BTS. It is associated with a
subscriber in the GSM system and establishes a link to an SGSN. Channel reselection is
provided at over the air interface radio link between the MT and the SGSN. The MS with an
integral TE can be compared to a modem, connecting the TE to the GPRS network.
4.3.2 GPRS TERMINAL CLASSES

Three GPRS Terminal Classes: Three GPRS Terminal Classes:
A A - - Simultaneous support for GPRS and other Simultaneous support for GPRS and other
GSM services. GSM services.
B B - - Can monitor GPRS and GSM services but Can monitor GPRS and GSM services but
can support only one at any one time. can support only one at any one time.
es. The other e other
GPRS Mobile Terminal Classes GPRS Mobile Terminal Classes

C C - - Supports GPRS or GSM servic Supports PRS or GSM services. Th
service is not available. service is not available.
G


37

A GPRS terminal can be one of three classes: A, B, or C:

Class A terminals support GPRS and other GSM services (such as SMS and voice)
simultaneously. This support includes simultaneous circuit switched (CS) and packet-
switched (PS) attach, activation, monitor, and traffic. As such, a Class A terminal can make or
receive calls on two services simultaneously. In the presence of circuit-switched services,
GPRS virtual circuits will be held or placed on busy rather than being cleared.

Class B terminals can monitor GSM and GPRS channels simultaneously, but can support only
one of these services at a time. Therefore, a Class B terminal can support simultaneous attach,
activation, and monitor, but not simultaneous traffic. As with Class A, the GPRS virtual
circuits will not be closed down when circuit-switched traffic is present.
Instead, they will be switched to busy or held mode. Thus, users can make or receive calls on
either a packet or a switched call type sequentially, but not simultaneously.

Class C terminals officially support GPRS only. However, some C class devices may be
manually set to handle GPRS or GSM, these are then seen as two different devices by the
etwork. Therefore, C class devices effectively support only non-simultaneous attach. The
ser must select which service to connect to and can make or receive calls from only the
anually (or default) selected service. The service that is not selected is not reachable. The

n
u
m
GPRS specifications state that support of SMS is optional for Class C terminals.
4.3.3 GPRS MOBILE TERMINAL MODIFICATIONS

New Mobile Stations will be required New Mobile Stations will be required
Backward compatibility with GSM Backward compatibility with GSM
SIM Card updates to include GPRS SIM Card updates to include GPRS
functionality functionality
GPRS Mobile Station (MS) Modifications GPRS Mobile Station (MS) Modifications
Motorola Motorola
GPRS GPRS- -enabled enabled
Timeport Timeport t250 t250


38

New MTs are required as existing GSM MTs cannot handle the enhanced air interface, nor do
they have the ability to packetize traffic directly. A variety of GPRS devices will exist
including a high-speed version of current MTs with embedded data capability to support
high-speed data access, a new kind of PDA device with an embedded GSM phone and PC
Cards for laptop computers.

Class A and B GPRS terminals (see below) will need to be backwardly-compatible with GSM
for making voice or circuit-switched data calls.

Mobile Terminals with either GPRS-aware or non-GPRS aware SIMs should be capable of
accessing GPRS services. When not stored in the SIM, the additional GPRS data related to
ciphering and location management (elementary files EFKcGPRS and EF LOCIGPRS) must be
stored in the MT memory.

4.3.4 GPRS MULTISLOT TERMINAL CLASSES

Types:
Type 1 - Non-simultaneous TRX
Type 2 - Simultaneous TRX
1 - 12 (Type 1) up to 4 timeslots in any direction (5 max).
GPRS Multislot Types/Classes GPRS Multislot Types/Classes

The GPRS specification defines 29 mult lot classes as shown in the table below. These classes
define the number of timeslots available for GPRS usage. Generally, GPRS devices in the
group 1-12 are currently being made available. It is predicted that Type 2 devices will not
become available until 2003.

Classes
19-29 (Type 1) Synchronous timeslots (3 - 8 max).
13-18 (Type 2) Simultaneous TRX.
is


39

Maximum number
of slots
Multislot
Tx Sum
Type
class
Rx
1 1 1 2 1
2 2 1 3 1
3 2 2 3 1
4 3 1 4 1
5 2 2 4 1
6 3 2 4 1
7 3 3 4 1
8 4 1 5 1
9 3 2 5 1
10 4 2 5 1
11 4 3 5 1
12 4 4 5 1
13 3 3 NA 2
14 4 4 NA 2
15 5 5 NA 2
16 6 6 NA 2
17 7 7 NA 2
18 8 8 NA 2
19 6 2 NA 1
20 6 3 NA 1
21 6 4 NA 1
22 6 4 NA 1
23 6 6 NA 1
24 8 2 NA 1
25 8 3 NA 1
26 8 4 NA 1
27 8 4 NA 1
28 8 6 NA 1
29 8 8 NA 1

Rx: Rx describes the maximum number of receive time slots (TS) that the mobile station can
use per TDMA frame. The mobile station must be able to support all integer values of receive
TS from 0 to Rx (depending on the services supported by the mobile station). The receive TS
need not be contiguous. For type 1 mobile stations, the receive TS is allocated within window
f size Rx, and no transmit TS will occur between receive TS within a TDMA frame.

o
Tx: Tx describes the maximum number of transmit TS that the mobile station can use per
DMA frame. The mobile station must be able to support all integer values of transmit TS T
from 0 to Tx (depending on the services supported by the mobile station). The transmit TS
ns, the transmit TS is allocated within
ween transmit TS within a TDMA frame.
need not be contiguous. For type 1 mobile statio
window of size Tx, and no receive TS will occur bet

Sum: Sum is the total number of uplink and downlink TS that can actually be used by the
mobile t be able to support all combinations
of integ < = Rx + Tx < = Sum (depending on the services
sup rt is not applicable to all classes.

station per TDMA frame. The mobile station mus
er values of Rx and Tx TS where 1
po ed by the mobile station). Sum


40

4.3.5 GPRS TERMINAL FORM FACTORS

GPRS Form factors describe the format in which a GPRS device in manufactured

Many GPRS form factors likely:
Mobile Handset
PCMCIA Card
PDA
GPRS Terminal Form Factors GPRS Terminal Form Factors

sting GSM handsets (example: Nokia 6310 above), PCMCIA cards for insertion
Personal Data Assista ts (PDAs)

There are likely to be many form factors to suit many user purposes from handsets physically
the same as exi
into laptop computers or n


41

________________________________________________________________________________
4.4 Base Station Subsystem GPRS Modifications

4.4.1 HARDWARE/SOFTWARE MODIFICATIONS

BTS Requires software upgrade
Inclusion of a CCU in the BTS
BSC requires software upgrade and
addition of PCUSN
PCUSN can contain multiple PCUs
Base Station Base Station Subsytem Subsytem (BSS) Modifications (BSS) Modifications
Siemens BSC Siemens BSC

grade, but typically will require
o hardware enhancements.
ill also require a software upgrade, as well as the
hen either voice or packet data traffic is originated at the MS, it is transported over the air
wever, at
,
network node called the SGSN, via the PCU over the G

The Base Transceiver Station (BTS) will require a software up
n

The Base Station Controller (BSC) w
installation of a new piece of hardware called a Packet Control Unit (PCU).

W
interface to the BTS and then to the BSC in the same way as a standard GSM call. Ho
the output of the BSC the traffic is separated; voice is sent to the MSC as with normal GSM
and packet data is sent to a new
b
network interface.


42

4.4.2 THE PACKET CONTROL UNIT (PCU)

4.4.2.1 The PCU Support Node

Packet Control Unit Support Node (PCUSN) Packet Control Unit Support Node (PCUSN)
BTS BTS
CCU
CCU
BSC BSC
PCUSN PCUSN
A A
BIS BIS
A A
GPRS GPRS
MSC/VLR MSC/VLR
G G
B B
A A
SGSN SGSN
Physical Connectivity Physical Connectivity

4.4.2.2 PCU Functions

Provides physical and logical data interface out of
the BSS for packet data traffic
LLC layer PDU segmentation/reassembly of RLC
blocks
Packet Control Unit (PCU) Functions Packet Control Unit (PCU) Functions

Packet data transfer scheduling
ARQ functions
Radio channel management function


43

LC layer PDU segmentation into RLC blocks before downlink transmission over the air
terface
LC layer PDU reassembly of RLC blocks into LLC PDUs after receipt on the air interface
plink
cheduling functions for uplink and downlink data transfers
plink and downlink Backward Error Correction (ARQ) functions including RLC block
ck/nack (uplink) and RLC block buffering and retransmission (downlink)
trol, packet scheduling, congestion

4.4.2.3 Circuit/Packet Data Separation
The PCU is responsible for the following GPRS MAC and RLC layer functions:

L
in

L
u

S
U
a

Radio channel management functions including access con
ontrol, power management etc c

Circuit/Packet Data Separation Circuit/Packet Data Separation
BTS BSC
PCU
MSC/VLR
SGSN
Gateway
MSC
GGSN
HLR
Circuit Switched
Packet Switched
PSTN PSTN
PDN PDN
A
G
b
Physical Connectivity Physical Connectivity
TRAU

T
a
s
n

he PCU provides a physical and logical data interface between the base station system (BSS)
nd the SGSN in the GPRS packet data network. It separates packet data traffic from circuit
witched traffic (voice or data) at the BSC and directs the packet data traffic into the GPRS
etwork. The PCU terminates the radio end of the Gb interface.


44

4.4.2.4 PCU Configurations
though the PCU resides lo A gically at the BTS, it may be positioned in a geographically remote
lo

T

I d in the BSC (configuration B), packets are transferred between
th
F

The Abis interface is the same for both B and C configurations but requires in-band signalling
(C-bits), unlike configuration A.
l
cation. Its position determines the interconnecting functionality.
he A configuration is most common and is representative of the logical configuration.
f the PCU is physically locate
e BTS CCU and the PCU with a fixed 320-byte length every 20mS, and are known as PCU
rames.

PCU Configurations PCU Configurations
BTS BTS
CCU
CCU
BSC Site BSC Site SGSN Site SGSN Site
PCU
BTS BTS
CCU
CCU
BSC Site BSC Site SGSN Site SGSN Site
PCU
BTS BTS
CCU
CCU
BSC Site BSC Site SGSN SGSN Site Site
PCU
A A
B B
C C
A A
bis bis
U U
m m
G G
b b
G G
b b
Circuit Switch (16/64kbps) Circuit Switch (16/64kbps) Packet Switch Packet Switch

is a reduced requirement for channel capacity between
TS and BSC/SGSN. However, configurations B and C required fewer PCUs in the system.

4.4

The advantage with configuration A
B
.3 THE CHANNEL CODING UNIT

he (CCU) performs the following functions:
Channel coding functions (CS1-4, see Section 5)
Forward Error Correction (FEC)
Interleaving (see Section 5)
Radio channel measurement functions
o channel measurement functions including received quality level, received signal
vel and information related to timing advance measurements.
T

CCU Radi
le



Data coding / decoding (CS1-4)
CS 1-2 require software upgrade only
rdware upgrade
Forward error correction (convolution coding)
rface interleaving

_______________________________________________________________________________
.5 GPRS Core Network Modifications
In order to transport packet data across an existing GSM infrastructure, new network nodes
have been introduced, known as GPRS Support Nodes (GSNs). These nodes are responsible
for the efficient routing of packet data between a GPRS-enabled MS and an external Packet
Data Network (PDN).

There are two main types of GSN: the Serving GSN (SGSN) and the Gateway GSN (GGSN).
Also, a number of existing GSM network entities need to be modified to accommodate
additional GPRS functionality. These include the MSC and HLR/VLR databases. Also an
interface between the existing Short Message Service (SMS) node and the new GPRS SMS
node has been defined.
The HLR stores the user profiles, current SGSN and PDP address for each GPRS subscriber in
the network.

CS 3-4 require ha
Air inte
Radio channel measurements (RxQual)
Radio management
Channel Codec Unit (CCU) Functions Channel Codec Unit (CCU) Functions

_
4

45


46

4.5.1 GPRS CORE NETWORK ELEMENTS

GPRS Core Network Elements GPRS Core Network Elements
New GPRS entities:
Serving GPRS Support Node (SGSN)
Gateway GPRS Support Node (GGSN)
Modified GSM entities:
HLR
MSC/VLR
SMS-GMSC
The following GSM network changes are required:

4.5.2 GPRS DATABASE CHANGES

GPRS can share GSM database resources
Database software upgrades required to accommodate
new GPRS functionality and parameters when interacting
with GSM
SGSN acts as VLR for GPRS-specific VLR functions
EIR/AuC will also require software upgrades for GPRS-
specific authentication/authorisation
Databases Databases VLR/HLR VLR/HLR
VLR
HLR


47

4.5.3 THE SERVING GPRS SUPPORT NODE (SGSN)

The SGSN can be viewed as a "packet-switching MSC;" it delivers packets to and received
packets from mobile stations (MSs) wit its service area.

SGSNs send queries to home location r s (HLRs) to obtain profile data of GPRS
subscribers.
An SGSN detects new GPRS MSs in its rvice area, process registration and authentication
and manages ciphering between MS and SGSN.

The SGSN also performs mobility man ement functions such as mobile subscriber
attach/detach, location management in ide its GPRS Location Area (LA) and logical link
management towards the MS.
For each MS, the SGSN also collects bil g information related to network usage (as does the
GGSN).

hin
egister
se
ag
s
lin
Packet routing
MS Session management
Authentication and Ciphering
Mobility management
Billing information collection
Serving GP S Support Node (SGSN) Serving GP S Support Node (SGSN) R R
Nokia SGSN

nal

The SGSN is connected to a PCU in the BSS via the Frame-Relay network layer, the Home
Location Register (HLR) and the GGSN for transfer of packet data in from and out to exter
packet networks.


48

4.5.4 THE GATEWAY GPRS SUPPORT NODE (GGSN)

Interface between GPRS backbone and
external PDNs.
ment
Packet routing to rom SGSNs
Billing informatio collection
(GGSN) (GGSN)
NetSpira GGSN

s
up
link to the mobile station (MS), through the SGSN.
The GGSN also translates between data formats, signalling protocols and address information
enable communication between the GPRS network and differing external networks.
mobile
formation that is necessary to tunnel the protocol data units (PDUs) to the SGSNs that
ges PDP contexts between itself and MSs for packet data transfer in and
ut of the GPRS core network.
nctions include network and subscriber screening and address mapping (using a
omain Name Server). One (or more) GGSNs may be provided to support multiple SGSNs

Gateway GPRS Support Node Gateway GPRS Support Node
PDP Conversion and context manage
IP address assignment management
/f
n
The GGSN is the interface towards external Packet Switched Networks (PSNs), such as the IP-
based Internet and X.25 networks. It is acting as an access server to the GPRS network and i
responsible for routing incoming traffic to the correct SGSN, i.e. it is responsible for setting
a logical

to

GGSNs are used as interfaces to external IP networks such as the public Internet, other
service providers' GPRS services, or enterprise intranets. GGSNs maintain routing
in
service particular MSs using the GPRS Tunnelling Protocol (GTP).

The GGSN also mana
o

Other fu
D


49

4.5.5 OTHER GPRS NETWORK ELEMENTS

Additional Elements of the GPRS Network Additional Elements of the GPRS Network
BTS BTS BSC BSC
SGSN
Inter-PLMN
Network
GPRS GPRS
Backbone Backbone
BG
CG
GGS
N
GGS
N
Internet
Intranet
Billing
Centre
LIG
DNS
Route
r
Serve
r
Corporate LAN
PCU
Core Network Core Network
DHCP

The Border Gateway (BG) is a network element that provides a direct connection to
operators' GPRS networks, thus allowing operators to av
other
oid using the public Internet to
ansfer data to other GPRS networks. This means that, when roaming to another GPRS
is provided via a GPRS "tunnel" over an inter-operator backbone network. The
G is also sometimes referred to as the BGSN or BGGSN.
he Charging Gateway (CG) is a stand-alone network element for controlling the Charging
Detail R It collects CDRs from
GGSNs) system (BS) after consolidating the CDRs
d converting them to a suitable format. Quality checking functions are also provided.
he Lawful Interception Gateway (LIG) fulfils an essential function within the GPRS
etwork by providing the ability to intercept GPRS mobile data calls for the purpose of law
forcement, as required by national authorities. In many countries, local regulatory
ompletely different from GSM call interception. In GSM, interception is mainly voice-based
udio recording, while in GPRS data interception occurs between the GPRS terminal and the
he Domain Name System (DNS) provides the Internet naming structure for the GPRS
network, by tran al IP addresses. Based on the URL
requested by the for the correct access point (in
e GGSN) to the Internet.

Dynamic Host Control Protocol (DHCP) Serve function of managing temporary
IP address assignment within the GPRS core network.

tr
network, subscribers can have a secure GPRS connection to their home network. This
connection
B

T
ecords (CDRs) processing routines in the GPRS network.
and SGSNs and forwards them to a billing
an

T
n
en
authorities require a means of lawful data interception before GPRS networks can be
launched commercially. Data call interception in the GPRS network is a new method
c
a
access point (the GGSN).

T
slating Web host addresses into numeric
user, the DNS supplies the actual IP address
th
r fulfils the


50

________________________________________________________________________________
4.6 GPRS
The
referenc ling. An
e -specific
formation is passed and processed in some way.
-Associated Interfaces

G terfaces, optional interfaces and PRS specification defined a number of compulsory in
e points. Some interfaces are defined for transmission and some for signal
rface differs from a reference point in that an interface is defined where GPRS int
in

Gf Gf Gr Gr Gc Gc
Gs Gs
Gd Gd
GPRS GPRS- -Associated Interfaces Associated Interfaces
BTS BTS BSC BSC
HLR HLR
SGSN SGSN
VLR VLR
Internet Internet
EIR EIR
TRX TRX
BSS BSS
GGSN GGSN
MSC MSC
SM SMS S
GMSC GMSC
Gb Gb
Gn Gn
PLMN PLMN
Gp Gp
Gi Gi - - reference point reference point
Um Um
PCU PCU
GPRS CORE NETWORK GPRS CORE NETWORK
MS MS
MS MS
Gb Gb = compulsory interface = compulsory interface
= optional interface = optional interface
MS MS
Gf Gf

4.6.1 COMPULSORY TRANSMISSION INTERFACES

Three compulsory GPRS transmission interfaces are defined:
Um. MS to BSS interface.
Gb. BSS to Core Network (SGSN) interface.
Gn. GSN to GSN interface (primarily SGSN-GGSN).

4.6.2 GPRS REFERENCE POINTS

Two reference points are defined:

Gi. Core Network to External Public Packet-Switched Network (PPSN) reference
point.
The R reference point lies between the TE and MS as illustrated in 4.2 earlier in this
section.


51

There are also a number of optional interface implementations as can be seen from the above
diagram:

4.6.3 OPTIONAL TRANSMISSION INTERFACES

Gc This optional SS7 interface is generally used by the GGSN to interrogate the HLR to
update its location database with the current user location.

Gd This optional interface is used to exchange SMS messages using the GPRS network
rather than the conventional GSM method.

Gp This optional interface is used to interface to other PLMN GPRS networks

4.6.4 SIGNALLING INTERFACES

f This interface connects the SGSN to the Equipment Identity Register (EIR) for accessin
uthentication information.

ill send the MSs profile to the new SGSN via
enerally used to exchange messages between the SGSN and
.

g G
a

Gr This interface is used to pass subscriber profile information between the SGSN and the
HLR. For example, the SGSN informs the HLR about the current location of an MS. When
he MS registers with a new SGSN, the HLR w t
the Gr interface.

s This optional interface is g G
the MSC/VLR when performing circuit-switched paging requests via the SGSN


52

Mobile Station Modifications
Terminal Description and Functions,
Base Station Subsystem (BSS) Modifications
Channel Coding Unit (CCU) Functionality
Core Netwo
SGSN, GGSN , HLR/VLR
GPRS-Associated Interfaces
Terminal Types (A,B,C) and Multislot Classes (1-29)
Terminal Form Factors
Packet Control Unit (PCU) Functionality
rk Modifications
BTS BSC
PCU
MSC/VLR
SGSN
Gateway
MSC
GGSN
HLR
Circuit Switched
Packet Switched
PSTN PSTN
PDN PDN
A
Gb
TRAU

5. GPRS Air Interface

53

_____________________________________________________________________

The introduction of GPRS to a GSM network required a number of different mechanisms to be
employed to enable packet data to be passed across the air interface. This section reviews the
GSM air interface and looks at the GPRS-specific enhancements to the GSM air interface.
Topics covered include:

GSM/GPRS Physical Channel Structure
GPRS Logical Channels
GPRS Multiframe Structure
GPRS Coding Schemes

5.1 Introduction


54

GPRS U GPRS U
m m
New Packet logical channels defined
New multiframe structure defined
Ability for multiple users to share single or
multiple timeslots
Four new channel coding schemes

Enhancements to the GSM Air interface to support GPRS include:

GPRS has defined a number of new logical channels for managing the flow of packet
data across the Um interface.
A new 52-frame multiframe structure has been defined, based on radio blocks of 4
timeslots
Ability to allow up to 8 GPRS users to share a single timeslot.
Ability to allocate multiple timeslots to a single GPRS user.
Four new channel coding schemes (CS-1 to CS-4) have been introduced that allow
greater data throughput when air interface radio path quality permits.

__________ ___________________

the context of GSM and GPRS, the physical channel refers to the resource allocated to a
pecific subscriber for the duration of a communications session. Such a session could
he basic GSM channel is referred to as a timeslot. This is because the air interface resource
(i.e. a
allocate
session.

5.2 GSM/GPRS Physical Channels

________________________________________
In
s
comprise a voice call of a data transfer session.

T
a c rrier frequency) is divided in time into 8 repeating blocks and a single subscriber is
d one of these time blocks (i.e. a timeslot) for the duration of his communications


55

E

5.2.1 PRIMARY GSM (P-GSM) PHYSICAL CHANNEL STRUCTUR
ted to
as Primary
Downlink sub band: 935 MHz to 960 MHz

GSM uses Frequency Division Duplexing (FDD) where the uplink and downlink of each
hannel operates on a different frequency. Therefore, two frequency bands were alloca c
GSM, 20 MHz apart.

he following frequency bands were initially allocated to GSM (now known T
GSM):

Uplink sub band: 890 MHz to 915 MHz
P P- -GSM Physical Channels GSM Physical Channels
Uplink Downlink
890 915 935 960 MHz
Duplex spacing = 45 MHz
Guard Band
100 kHz wide Channel Numbers (n) (ARFCN)
200 kHz spacing
Range of ARFCN:
1 - 124
1 n
Guard Band
100 kHz wide
Fu(n)
2 3 4
0 1 2 3 4 5 6 7
4.615 ms
timeslot = 0.577 ms
1 frame period
Raw data rate =
33.75kbps per traffic channel
270kbps per carrier channel

The up and down bands are divided into a number of carrier frequencies, each having a
200kHz Bandwidth. Therefore 124 carriers are vailable within each of the up and down link
bands (allowing for a 100 MHz guard band at ea h end of the allocated spectrum).
he up and down link channel pair allocation has been arranged such that the two
p and downlink channel frequencies can be calculated as follows:
Uplink frequencies: Fu(n) = 890 + 0.2 n (1 <= n <= 124)
Downlink frequencies: Fd(n) = Fu(n) + 45
a
c

T
frequencies comprising a channel pair are 45Mhz apart

Each frequency pair is identified by an Absolute Radio Frequency Carrier Number
(ARFCN).

U


56

5.2.2 EXTENDED GSM (E-GSM) PHYSICAL CHANNEL STRUCTURE

E-GSM allocated an additional 10MHz of bandwidth at the bottom end of each of the up an
down link frequency bands. The new frequency bands are:

d


E E- -GSM Physical Channels GSM Physical Channels
Guard Band
200 kHz spacing
Range of ARFCN:
1 124
975 1023
1 n
Guard Band
100 kHz wide
Fu(n)
2 3 4
0 1 2 3 4 5 6 7
4.615 ms
timeslot = 0.577 ms
1 frame period
Raw data rate =
Uplink Downlink
880 915 925 960 MHz

link frequency bands from
20MHz to 10MHz
An increase in size of up and down link frequency bands from 25Mhz to 35MHz
Assignment of new ARFCN in the range 975-1023
The P-GSM ARFCN 0 now reverts from a guard band to a valid ARFCN
-GSM up and downlink channel frequencies can be calculated as follows:
plink frequencies: Fu(n) = 890 + 0.2 n (0 <= n <= 124)
Fu(n) = 890 + 0.2 (n 1024) (975 <= n <= 1023)
ownlink frequencies: Fd(n) = Fu(n) + 45

This resulted in the following:

An extra 50 carrier pairs (10MHz / 200kHz channels)
A reduction in bandwidth isolation between up and down

E

U

D



57
.2.3 DCS 1800 PHYSICAL CHANNEL STRUCTURE 5

igital Communication System (DCS) 1800 introduced a further 1800 MHz spectrum range
own link bands are 75MHz each and have a 20MHz separation in the following ranges:
D
for GSM. The characteristics of radio frequencies in this range are such that DCS-1800 is
typically used for smaller microcells overlaid over existing GSM-900 macrocells. The up and
d


DCS DCS- -1800 Physical Channels 1800 Physical Channels
Guard Band
200 kHz spacing
1 n
Guard Band
100 kHz wide
Fu(n)
2 3 4
0 1 2 3 4 5 6 7
4.615 ms
timeslot = 0.577 ms
1 frame period
Raw data rate =
Uplink Downlink
1710 1785 1805 1880 MHz
Range of ARFCN:
512 - 885

nel
numbers

The cha
.
DCS 8

ink 512) (512 <= n <= 885)
ownlink frequencies: Fd(n) = Fu(n) + 95

Each band is divided into 200kHz carriers, as with GSM -900. Therefore 374 carriers are
available within each of the up and down link bands (allowing for guard bands). Chan
are in the range 512-885 (ARFCNs).
nnel pair allocation has been arranged such that the two frequencies comprising a
pair are 95Mhz apart channel

-1 00 up and downlink channel frequencies can be calculated as follows:
frequencies: Fu(n) = 1710.2 + 0.2 (n Upl

D


58

_____________________________________________________________________

GPRS Multiframe Structure GPRS Multiframe Structure
B0 to B11 = Radio Blocks
T = PTCCH (Timing Advance)
X = Signalling/BSIC Measurements
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 T T X X
52-frame GPRS Traffic Channel Multiframe
T T T T T T T T T T T T T T T T T T I T T T T T T S
26-frame GSM Traffic Channel Multiframe
Each radio block comprises 4 x 114-bit bursts
Radio bursts are assigned in the sequence:
B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B11
0 51 26

5.3 .1 GPRS PACKET DATA CHANNEL MAPPING

acket logical control channels use the same control multiframe structure as is used for GSM.
owever, GPRS uses a new Packet Data Traffic Channel (PDTCH) multiframe structure.

he PDTCH multiframe comprises 52 TDMA frames which repeat cyclically. This structure
can be s
frames G
block co

The idle following:

BSI
Idle
When packet data is queued for transmission, radio block resources multiplexing is not
ocated in the following sequence:
B0, B6, B3, B9, B1, B7, B4, B10, B2, B8, B5, B1

5.3 GPRS Multiframe Structure

P
H
T
een as the equivalent of two GSM 26-frame TCH multiframes. These 52-TDMA
PRS Multiframes are divided into 12 traffic blocks and 4 idle frames. Each traffic
mprises four 114-bit frames or data bursts.
frames are used for the

Idle frames 2 and 4 are used by the MS for neighbouring cell signal measurements and
C decoding.
frames 1 and 3 are used by the MS for TA updates

executed sequentially. They are all


59

5.3.2 GPRS LOGICAL CONTROL CHANNEL MAPPING

GPRS Control Channel Mapping GPRS Control Channel Mapping
GPRS may operate without GPRS control channels (GPRS Phase I),
utilising the GSM equivalent logical channels
GPRS does not utilise a dedicated physical signalling channel (TS0)
Where GPRS control channels are implemented:
One GPRS PDCH is designated as the master channel
Up to 4 blocks may be allocated to PBCCH on the master PDCH
PBCCHs blocks are assigned in same sequence as PDTCHs
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 T X
0 51 26
PRS is capable of utilising GSM logical control channels for its signalling requirements. This
was the case with GPRS phase 1. GPRS Phase 2 provides for the use of separate GPRS logical
control channels. Unlike GSM, GPRS does not use a separate physical channel for control
signalling. When GPRS is implemented over the GSM air interface, one of the GPRS channels
is designated as the master packet data channel. This channel has one or more radio blocks
(up to 4) allocated to control channels (PBCCH/PCCCH).

_____________________________________________________________________

5.4.1 PACKET LOGICAL CHANNELS

G

GPRS shares certain logical control channels with GSM. These include the FCCH and SCH.
However, GPRS also defines a number of new packet logical channels specifically to support
GPRS Traffic.

These logical channels can be divided into two categories; traffic and signalling/control. Note
that, unlike conventional GSM, a GPRS handset can be configured to access multiple traffic

5.4 GPRS Logical Channels
channels (PDTCHs) simultaneously.


60

GPRS shares GSM for some logical common control
channel functions (e.g. FCCH, SCH)
New GPRS dedicated control channels are defined
(e.g. PDTCH, PACCH and PTCCH)
Packet control channels are optional
GSM control channels may be substituted for
equivalent GPRS control hannels
Logical Channels Logical Channels

GPRS GPRS
c

GPRS Logical Channel Structure GPRS Logical Channel Structure
Two types of logical channel are defined; Common and Dedicated
Each is further sub-divided as shown:
PDTCH
PDTCH
PCCCH
PCCCH
PBCCH
PBCCH
PDCCH
PDCCH
PPCH
PPCH
PRACH
PRACH
PAGCH
PAGCH
PNCH
PNCH
PACCH
PACCH
PTCCH
PTCCH
Common Channels
Common Channels
Dedicated Channels
Dedicated Channels



5.4.2 PACKET LOGICAL CONTROL CHANNELS

As with GSM, GPRS has defined a number of new logical channels that per
of functions including signalling, system information broadcast, synchroni
form a multiplicity
sation, channel
signment, paging and payload transport. as

PBCCH/PCCCH Logical Channels PBCCH/PCCCH Logical Channels
Channels U / D Purpose Notes
PBCCH
PBCCH Packet
Broadcast
Control Channel
D Used to broadcast
packet data specific
system information.
If PBCCH is not allocated,
this information can be
broadcast on BCCH.
PCCCH
PRACH Packet Random
Access Channel
U Used by MS to initiate
the uplink transfer of
data or signalling
information.
Uses Packet Access burst
and Extended Packet
Access burst. Access burst
is used to obtain TA.
PPCH Packet Paging D Page MS prior to Paging groups allow DRX.
Channel downlink packet transfer. Can be used for CS and PS
data services
PAGCH Packet Access
Grant Channel
D Sends resource
assignment messages to
MS prior to packet
Additional resource
assignment messages can
be sent on a PACCH if the
transfer. MS is currently involved in
packet transfer.
PNCH Packet
Notification
Channel
D Sends a Point To
Multipoint Multicast
(PTM-M) notification to a
group of MSs prior to a
PTM-M is not specified in
GPRS Phase 1
DRX
m
PTM-M packet transfer.
mode is provided for
onitoring PNCH.
Optionally a PTM-M new
Assigns resources for
packet transfer.
message indicator may be
sent on PPCH to each MS
show when they need to
listen to PNCH.

PDTCH/PDCCH Logical Channels PDTCH/PDCCH Logical Channels
Channels U / D Purpose Notes
PDTCH
PDTCH Packet Data
Traffic Channel
U/D Allocated for data
transfer. Temporarily
dedicated to one MS or
a group of MSs for PTM-
M.
In multislot operation, one
MS may use several
PDTCHs in parallel for
individual packet transfer.
A PDTCH is uni-directional:
uplink (PDTCH/U) for a
mobile originated packet
transfer ;
downlink (PDTCH/D) for a
mobile terminated packet
transfer.
PDCCH
PACCH Packet
Associated
Control Channel
U/D Signalling information for
a specific MS, e.g.:
acknowledgements,
power control,
resource assignment
and reassignment
messages,
PACCH shares resources
with PDTCHs that are
currently assigned to one
MS.
An MS transferring packet
data can be paged for CS
services on PACCH.
PTCCH Packet Timing
Advance Control
Channel
U/D Uplink transmits random
access burst for TA
estimation.
Downlink transmits TA
updates.
The downlink TA
transmission is sent to
several MSs.
One downlink PTCCH
(PTCCH/D) is paired with
several uplink PTCCHs
(PTCCH/U).

61


62

When Packet control channels are impl mented, all packet common control signalling takes
place over a PDCH designated as the aster PDCH.

5.4.3 PACKET LOGICAL TRAFFIC CHANNELS
e
m

PDTCH - User-generated information
PTCH Traffic multif me comprising PDTCH and
Dedicated Control Ch nels (PDCCHs)
PDCH - Packet Cha nel comprising possible combination
of PTCH and Packet ontrol Channel (PCCCH/PBCCH)
MPDCH The PDCH carrying the PBCCH.
Packet Channel Terminology Packet Channel Terminology
ra
an
n
C
PDCH
PDCCH
PDTCH
PTCH
PBCCH/P CH CC

The terminology found in various GPRS-related documents to describe Packet data channels
can be a source of confusion. The ETSI

PDCH
GPRS Recommendations defines two terms:
. The Packet Data Channel refers to the assignment of a physical channel to the
GPRS service. The PDCH can comprise a combination of different logical packet data
channels.
PDTCH. The Packet Data Traffic Channel refers to the GPRS traffic (as opposed to
control) channel. It carried the GPRS traffic multiframe and comprises the User traffic
packets and the Dedicated Control Channel (DCCH) packets.

However, some sources also refer to a cket Traffic Channel (PTCH). Where this
terminology is used, the PTCH performs the same function as the PDTCH described above
and the PDTCH refers to the user data annel only, excluding the PDCCH channels.

In addition, some sources refer to a Master PDCH (MPDCH). This is Ericsson-specific
terminology that refers to the GPRS PD H that is carrying the PBCCH.

A PDCH is assigned to a single physic channel (timeslot) on the air interface. Each PDCH
can carry one or a combination of logical packet channels including control and user traffic
types.

Pa
ch
C
al


63

Physical channel allocated to packet traffic
Can comprise combinations of control and user data
May be permanently allocated to a physical channel
May be dynamical assigned to a physical channel on
a contention basis
Unlike GSM, GPR PDCHs are not duplex
Packet Data Channels (PDCHs) Packet Data Channels (PDCHs)

ly

S
PBCCH + PCCCH
PCCCH + PDTCH
PBCCH + PCCCH + PDTCH
PDTCH only
PDCH Configurations PDCH Configurations
1 2 3
3 1 2
PBCCH
PCCCH
PDTCH
Logical Packet Channels 1 PDCH
2

Where timeslots are permanently assigned to GPRS, each GPRS timeslot equates to a single
PDCH. Where no timeslots are permanently assigned to GPRS, PDCHs are dynamically
assigned to a specific physical channel for a variable time period in contention with circuit-
switched services. Therefore, unlike GSM circuit-switched (voice or data) traffic channels,
GPRS PDCHs are not assigned for the duration of a single users communication session


64

5.4.4 PACKET DATA TRAFFIC CHANNELS (PDTCHs)
A PDTCH is a logical channel established temporarily by a user for the transfer of user traffic.
A single user can establish multiple PDTCHs in parallel if necessary. However, only one
PDTCH is mapped onto one physical channel (i.e. one PDCH).

Up to eight PDTCHs, each using a different timeslots (PDCHs) on the same carrier may be
simultaneously allocated to a single MS. Consequently, each MS is capable of terminating
multiple PDTCHs. It is also possible to allocate a single PDTCH to a group of MSs in PTM-M
mode.
All packet data traffic channels are uni-directional, either uplink (PDTCH/U), for a mobile
originated packet transfer or downlink (PDTCH/D) for a mobile terminated packet transfer.

Carries user data traffic and packet dedicated control
channels
One PDTCH is mapped to one GPRS-allocated physical
channel (TS)
Up to 8 PDTCHs can be assigned to a single carrier
Up to 8 PDTCHs can be assigned to a single user or
group of users (PTM-M)
Unidirectional
Asymmetrical user traffic flow in UL and DL
Packet Data Traffic Channels ( Packet Data Traffic Channels (PDTCHs PDTCHs) )

A PDTCH when used for single timesl operation may be either full-rate (PDTCH/F) or half- ot
rate (PDTCH/H) depending on whether it is carried on a PDCH/F or PDCH/H respectively.
sed for multislot operation is always full-rate. A PDTCH, when u



65
______________
5.5 GPRS Coding Schemes

5.5.1 GPRS CODING SCHEME OVERVIEW

__________________________________________________________________

he use of radio as a data transmission medium is prone to errors from a number of sources.
Coding schem interface.

Unfortunately, the more robust the protection, the greater the data overheads required.
Whilst the raw data throughput remains the sa e, the actual information throughput reduces

T
es are used to protect data from errors when crossing this radio path
m
with a corresponding increase in protection overheads. Therefore, to maximise the use of
variable quality radio paths, a number of coding schemes are available. Each coding scheme
has varying levels of protection to maximise the information throughput where good radio
paths allow.

GPRS Coding Schemes GPRS Coding Schemes
Scheme Code rate USF Pre-

coded
USF
Radio Block
excl. USF
and BCS
(Payload)
BCS Tail Coded
bits
Punctured
bits
Data
rate
kbps
CS-1 1/2 3 3 181 40 4 456 0 9.05
CS-2 2/3 3 6 268 16 4 588 132 13.4
CS-3 3/4 3 6 312 16 4 676 220 15.6
CS-4 1 3 12 428 16 - 456 - 21.4
4 coding schemes have been defined for GPRS:
andatory for the BSS

PRS has introduced 4 new coding schemes for this purpose, CS-1 to CS-4. For compatibility
urposes, all coding schemes are mandatory for Mobile Stations but only CS-1 is compulsory
r BSSs.

CS-1 is m
CS-1 to 4 are mandatory for the MS

G
p
fo


66

5.5.2 THE CODING SCHEME PROCESS

In order to illustrate the coding procedure, coding scheme 2 (CS-2) will be used to describe
the process. This process is explained below and illustrated in the following diagram:

Using coding scheme 2 (CS-2), the net data throughput is 13.4kbps, giving a 20mS
block size of 268 bits. To this is added a 3-bit Uplink State Flag (USF) field resulting
in a 271 bit block.

This block is then passed through a systematic block encoder where 16 parity bits are
added in the form of a Block Check Sequence (BCS), giving 287 bits per block. The
BCS enables certain errors to be detected.

GPRS Data Encoding GPRS Data Encoding
data in data in
CS-2
Block Block
Check Check
Coding Coding
USF USF
pre pre- -coding coding
add add
tail bits tail bits
convolution convolution
coding coding
puncturing puncturing
Data out Data out
290 bits 290 bits
294 bits 294 bits
588 bits 588 bits 456 bits 456 bits
287 bits 287 bits
+16 bits +16 bits
+3 bits +3 bits
- -132 bits 132 bits
+4 bits +4 bits
x2 x2
Add USF Add USF
268 bit 268 bit
block block
+3 bits +3 bits
271 bits 271 bits

de for error detection and correction purposes, increasing the size of the block by 3
to 290 bits.
It is now passed through a convolution encoder where bits are added to enable error
correction to take place. The algorithm used produces a block length of 588 bits.

USF pre-coding takes place where the USF bits of the block are mapped to a 6-bit
co

This is followed by the addition of 4 tail bits. These are used to flush the
convolution encoding buffer after processing the data block. The block size is
therefore increased to 294 bits.



67
.
. This is achieved through a process called puncturing whereby some of the
redundancy bits generated by the convolution encoder are deleted. In this case, 132
bits must be removed.
Note that the rate of the convolution encoder mentioned above is determined by the
5.5.3 CODING SCHEME 1

The GPRS radio block size is fixed at 456 bits, regardless of the coding scheme used
Therefore, the 588-bit CS-2 data block has to be squeezed into the 456-bit radio
block

ratio of the pre- and post-convolution coding block sizes (i.e. after puncturing).
Therefore in the case of CS-2, the code rate is 294/456 = 2/3.

GPRS Coding Scheme 1 (CS GPRS Coding Scheme 1 (CS- -1) 1)
6
USF Segmented LLC Frame Data BCS
3 181 40
224 bits
USF RLC Block
4 tail bits added
rate convolutional
coding
(224+4) x 2 = 456 bits
Data Rate = 181 payload bits per 20mS sample = 9.05kbps
MAC Frame

For Coding Scheme 1 (CS-1), 40 bits are used for the Block Check Sequence (BCS) to increase
protection. These and the Uplink State Flag (USF, 3 bits), Header and Data (181 bits), and 4
tail bits are passed through a rate convolutional encoder resulting in a protocol 456 bit
payload. Therefore, when using CS-1, the data rate is equal to: 181 bits/20ms sample =
9.05kbps


68


For Coding Scheme 2 (CS-2), only 16 bits are used for the BCS but, in this case, a Cyclic
undancy Code (CRC) is used. Other differences between CS-2 and CS-1 include the use of
6 bit USF to increase robustness during transmission over the air interface. Once again, 4
tail bits are added to the sequence prior to passing through a rate convoluted encoder. The
result of this is a bit stream of 588 bits/20ms but this needs to be reduced to 456 bits in order
to bring it in line with GSM burst structures. Therefore, 132 bits are punctured. It should be
noted that the USF bits (12 bits after encoding) are not punctured.

Red
a
6 268 16
290 bits
RLC Block
4 tail bits added
rate convolutional coding
12
456 bits
Puncturing (132 bits)
12
(290+4) x 2 = 588 bits USF
USF
MAC Frame

) is used. Other differences between CS-2 and CS-1 include the use of
a 6 bit USF to increase robustness during transmission over the air interface. Once again, 4
tail bits are added to the sequence prior to passing through a rate convoluted encoder. The
result of this is a bit stream of 588 bits/20ms but this needs to be reduced to 456 bits in order
to bring it in line with GSM burst structures. Therefore, 132 bits are punctured. It should be
noted that the USF bits (12 bits after encoding) are not punctured.


For Coding Scheme 2 (CS-2), only 16 bits are used for the BCS but, in this case, a Cyclic
Redundancy Code (CRC

The process used in CS-3 is almost identical to that of CS-2 other than the degree of
puncturing. In this case, the Header and Data is made up of 312 bits and after encoding (with
USF, BCS and tail bits), the result is 676 bits. This is punctured once again to the 456 bits as


69
required by the GSM burst structure. Therefore, when using CS-3, the data rate will be equal
to: 312 bits/20ms sample = 15.6kbps.

6 312 16
334 bits
RLC Block
4 tail bits added
rate convolutional coding
12
456 bits
12
(334+4) x 2 = 676 bits USF
USF
MAC Frame
Puncturing (220 bits)



70
12
12 428 16
456 bits
USF RLC Block
No Coding
456 bits
MAC Frame

or Coding Scheme 4 (CS-4), there is no Forward Error Correction (FEC) applied to the data
d as such, there is more capacity for user information. In this case, we see that the BCS is
d the USF has been extended to 12 bits for robustness.
le to carry 428 bits of header and data.
hus, the data rate for CS-4 is equal to : 428 bits/20ms sample = 21.4kbps

ODING SCHEMES

F
an
made up of 16 bits, using a CRC code an
herefore, using this scheme, it is possib T

T

5.5.7 COMPARISON OF C


Coding Scheme Performance Coding Scheme Performance
C / I
CS-2
CS-3
CS-4
CS-1
Average Data Throughput per TS vs Average Connection C/I
D
a
t
a

t
h
r
o
u
g
h
p
u
t
(Data Source: Nokia Network Testing Results)

The commonly quoted theoretical maximum data throughput for GPRS is 171.2 kbps. This is
based on using CS-4 (21.4kbps) and allocating all 8 timeslots on the carrier.

However, it can be seen from the above that these data rates are only achievable over a very
good radio path i.e. when the mobile subscriber is stationary and close to a base station.
addition, current hardware implementations for GPRS mobile equipment restrict the
number of available timeslots to 4 (multislot classes 1-12).
learly, using current technology, achieving the theoretical maximum GPRS bit rate of
71.2kbps will be a rare occurrence, and then only when handsets capable of utilising all 8-

In

C
1
timeslots become available.

71


72
PDTCH
PDTCH
PCCCH
PCCCH
PBCCH
PBCCH
PDCCH
PDCCH
PPCH
PPCH
PRACH
PRACH
PAGCH
PAGCH
PNCH
PNCH
PACCH
PACCH
PTCCH
PTCCH
Common Channels
Common Channels
Dedicated Channels
Dedicated Channels
GSM/GPRS Physical Channel Structure
FDMA, TDMA, P-GSM900, E-GSM900, DCS1800
GPRS Logical Channels
Logical Control Channels, Logical Data channels
GPRS Multiframes
GPRS Coding Schemes


73



74

. GPRS Protocols Overview
_____________________________________________________________________

This section of the course looks at the protocols used by GPRS to ensure user data in
accurately transported across the GPRS network from source to destination.

The first part of this section provides an overview of the generic ISO 7-layer protocol stack
model. This is followed by a review the protocols used by GPRS and how they relate to this
model.

6.1 Introduction

6


75

_____________________________________________________________________

Protocols Protocols
A protocol is a set of rules, agreed by both sides, to allow
meaningful communication to take place
Protocols are needed whenever systems need to pass
information from one to another
?

The dictionary definition of protocol (in this context) is:

a set of rules governing the exchange of electronically transmitted
data between devices

The need for commonly-agreed protocols has developed as a result of the multitude of
different manufacturers designing equipment to perform essentially the same task. If each of
these manufacturers had proprietary protocols, users would be restricted to using equipment
from one manufacturer. Internationally-agreed open protocols have enabled users to select
equipment from a range of manufacturers where common international protocols have been
implemented.

The International Standards Organisation (ISO) developed a structure on which protocols
could interact at a number of levels. The majority of todays protocols are either based
directly on this model or provide references to it.

Development of the Open Standards Interconnection (OSI) reference model was started in
1983 by a number of major computer and telecommunications companies. It was eventually
adopted as an international standard by the International Standards Organisation (ISO) and is
currently embodied within the ITU-TS X.200 Recommendation.
6.2 Protocols and the ISO 7-Layer OSI Model


76

The model comprises 7 layers which define various functions involved in establishing and
servicing end-to-end communications circuits across a network. These 7 layers are generally
viewed in two blocks;

Application Functional Layers. These are layers 4-7 of the OSI Model and relate to
the end-to-end functions between two or more users at the periphery of a network.

Network Functional Layers. These are layers 1-3 of the OSI Model and refer to th
functions required to transport data across a network.
e

ISO 7 ISO 7- -Layer OSI Model Layer OSI Model
APPLICATION
PRESENTATION
Syntax and data representation management Syntax and data representation management
File transfer, access management File transfer, access management
6 6
7 7
SESSION
TRANSPORT
NETWORK
DATA LINK
PHYSICAL
Mechanical and electrical in
1 1
End End- -to to- -end message transfer end message transfer
Network routing, addressing, call management Network routing, addressing, call management
Data link control (framing, error control) Data link control (framing, error control)
terfacing Mechanical and electrical interfacing
Application entity dialogue and synchronisation Application entity dialogue and synchronisation
4 4
3 3
2 2
5 5

layer...This is the layer at which communication partners are
and

mple,
ions,
nd. It deals with session and
onnection coordination.

ayer 7: The application L
identified, quality of service is identified, user authentication and privacy are considered,
any constraints on data syntax are identified. (This layer is not the application itself, although
some applications may perform application layer functions.)

Layer 6: The presentation layer...This is a layer, usually part of an operating system, that
converts incoming and outgoing data from one presentation format to another (for exa
from a text stream into a popup window with the newly arrived text). This layer is
Sometimes called the syntax layer.

Layer 5: The session layer...This layer sets up, coordinates, and terminates conversat
exchanges, and dialogs between the applications at each e
c



77
Laye
dete
trans

ayer 3: The network layer...This layer handles the routing of the data (sending it in the right
irection to the right destination on outgoing transmissions and receiving incoming
ansmissions at the packet level). The network layer does routing and forwarding.
lectrical and mechanical level. It provides the hardware means of sending and receiving data
on a carrier.

__________

r 4: The transport layer...This layer manages the end-to-end control (for example,
rmining whether all packets have arrived) and error-checking. It ensures complete data
fer.

L
d
tr

Layer 2: The data-link layer...This layer provides synchronization for the physical level and
does bit-stuffing for strings of 1's in excess of 5. It furnishes transmission protocol knowledge
and management.

Layer 1: The physical layer...This layer conveys the bit stream through the network at the
e

___________________________________________________________
Horizontal (Peer Horizontal (Peer- -to to- -Peer) Communication Peer) Communication
APPLICATION
PRESENTATION
SESSION
TRANSPORT
NETWORK
DATA LINK
PHYSICAL
APPLICATION
PRESENTATION
SESSION
TRANSPORT
NETWORK
DATA LINK
PHYSICAL
NETWORK
DATA LINK
PHYSICAL
NETWORK
DATA LINK
PHYSICAL
NETWORK (Transmission Channel) NETWORK (Transmission Channel)
HOST A HOST A HOST B HOST B
Node A Node A Node B Node B
Virtual Link Virtual Link

6.3 Protocols Stacks and Inter-Layer Communication


78

Vertical (Entity Vertical (Entity- -to Entity) Communication to Entity) Communication
APPLICATION APPLICATION
PRESENTATION
SESSION
PRESENTATION
SESSION
TRANSPORT
NETWORK
DATA LINK
PHYSICAL
TRANSPORT
NETWORK NETWORK NETWORK
DATA LINK
PHYSICAL
DATA LINK
PHYSICAL
DATA LINK
PHYSICAL
Node A Node A Node B Node B

Vertical (Entity Vertical (Entity- -to to- -Entity) Communication Entity) Communication
Each layer requests a service from the layer below
The layer below responds by providing a service to
the layer above
Each layer can provide one or more services to
the layer above
Each service provided is known as a service
Entity
Each Entity is accessed via a Service Access
Point (SAP) or a gate.
Each SAP has a unique SAP Identifier (SAPI)
R
e
q
u
e
s
t
S
e
r
v
i
c
e
Entity
Entity
SAP


79

________________________________________________________________________________
6.4 Protocol Encapsulation

Protocol Encapsulation Protocol Encapsulation
PRESENTATION PRESENTATION
SESSION SESSION
TRANSPORT TRANSPORT
NETWORK NETWORK
LINK LINK
PHYSICAL PHYSICAL
User Data
User Data
User Data
User Data
User Data
User Data
User Data
User Data
SESSION SESSION
TRANSPORT TRANSPORT
NETWORK NETWORK
LINK LINK
PHYSICAL PHYSICAL

Protocol Encapsulation Protocol Encapsulation
SESSION SESSION
TRANSPORT TRANSPORT
NETWORK NETWORK
LINK LINK
PHYSICAL PHYSICAL
User Data
User Data
User Data
User Data
User Data
User Data
User Data
SESSION SESSION
TRANSPORT TRANSPORT
NETWORK NETWORK
LINK LINK
PHYSICAL PHYSICAL
User Data


80

________________________________________________________________________________
6.5 Data Tunnelling

Data Tunnelling Data Tunnelling
A technology that enables one network to send its data via
another network's connections.
Tunneling works by encapsulating a network protocol within
packets carried by the second network
(Webopedia definition)
A tunnel is a point-to-point (PTP) virtual connection between
two end points across a network through which data packets
can be transported, transparent to the bearer network

Data Tunnelling Data Tunnelling
Tunneling is used by many technologies:
GPRS (GTP)
Internet (PPTP)
MPLS
VPNs

Mobile IP



81
__________ _________________________

L

__________________________________
6.6.1 GPRS PROTOCOLS AND THE 7-LAYER MODE
he GPRS network is essentially a transport network for conveying data packets from a
GPRS-enabled MS to the GGSN before onward t mission into the public data network (e.g.
ternet). In the reverse direction, the function of the GPRS network is to take data packets
rriving at the GGSN from the public data network and transport then across the network to
should be passed transparently through the
PRS network. Therefore, the protocols relevant to the GPRS relate only to the first three-
i.e. physical, data link and network layers).
PRS-related protocols are divided into two groups known as the transmission plane
LS

T
rans
In
a
the required GPRS-enabled MS.

he actual data packets (be they IP or X.25 etc) T
G
layers of the ISO 7-layer model

G
protocols and signalling plane protocols.

6.6.2 TRANSMISSION PLANE PROTOCO

The GPRS Protocol Stack The GPRS Protocol Stack
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Application Application
Relay Relay
Relay Relay
MS MS BSC/PCUSN BSC/PCUSN SGSN SGSN GGSN GGSN
UDP/TCP UDP/TCP
GTP GTP
L1 L1
L2 L2
IP IP
L2 L2
IP/X.25 IP/X.25
L1 L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis L1bis
Network Network
Service Service
BSSGP BSSGP
LLC LLC
SNDCP SNDCP
UDP/TCP UDP/TCP
L1 L1
L2 L2
IP IP
Network Network
Service Service
BSSGP BSSGP
GTP GTP
L1bis L1bis
GPRS Core GPRS Core
Network Network
PSDN PSDN GGSN
BSC/PCU
BSC/PCU
SGSN
U U
m m
G G
b b
G G
n n
G G
i i

The transmission protocols refer to the protocols used to convey user data across the GPRS
6.6 GPRS Protocol Stacks

network.


82

6.6.3 THE RELAY FUNCTION

Transfers PDP PDUs from input port to appropriate
output port
Packet sequence numbering
Buffering
Employs maximum holding time
unction unction

DP PDUs received from the incoming link

t SGSN and GGSN the relay function stores all valid PDP PDUs until they are forwarded to
the next network node or until the maximum ho ing time of the PDP PDUs is reached, at
hich point the PDP PDUs are discarded. This maximum holding time is implementation

ers to PDP PDUs received from
Us to the Gi
Relay F Relay F
Packet re-sequencing

The relay function of a network node transfers the P
to the appropriate outgoing link.
A
ld
w
dependent and can be influenced by the PDP type, the QoS of the PDP PDU, the resource load
status, and by buffer conditions. The discarding procedure protects resources from useless
transfer attempts, especially the radio resource.

he SGSN and GGSN relay functions add sequence numb T
SNDCP and from the Gi reference point, respectively. The SGSN relay function may perform
re-sequencing of PDP PDUs before passing the PDP PDUs to SNDCP. The GGSN relay
unction may perform re-sequencing of PDP PDUs before passing the PDP PD f
reference point.

6.6.4 SIGNALLING PLANE PROTOCOLS

Signalling Plane Protocols are used to control the passage of information
across the network. Signalling generally takes the form of signalling messages
that are passed between network entities. These messages are passed over the
etwork using the resources of the transmission plane. n



The Network Access Signalling Protocols The Network Access Signalling Protocols
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
Relay Relay
MS MS BSC/PCUSN BSC/PCUSN
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis L1bis
Network Network
Service Service
BSSGP BSSGP
BSC/PCU
BSC/PCU
SGSN
U U
m m
G G
b b
L1bis L1bis
MAC MAC
RLC RLC
LLC LLC
SGSN SGSN
S
N
D
C
P
S
N
D
C
P
S
M
S
S
M
S
G
M
M
/
S
M
G
M
M
/
S
M
S
N
D
C
P
S
N
D
C
P
S
M
S
S
M
S
G
M
M
/
S
M
G
M
M
/
S
M

GPRS Core Network Signalling Protocols GPRS Core Network Signalling Protocols
MAP
TCAP
SCCP
MTP-3
MTP-2
L1
MAP
TCAP
SCCP
MTP-3
MTP-2
L1
Network Network
NODE A NODE A
Network Network
NODE B NODE B
MAP Mobile Application Part
TCAP Transaction Capabilities Application Part
SCCP Signalling Connection Control Part
MTP Message Transfer Part

As t
SGS

Between core network (NSS) entities such as SGSNs, HLRs, EIR, SMS-MSCs etc, the Signalling
Syst
will

he network access level, layer-3 signalling messages are passed between the MS and the
N for controlling the passage of data packets between these two entities.
em No7 (SS7) is used. This follows the protocol format described above. Each of these protocols
be outlined in the course sections below.
83


84

Introduction to Protocols
Definition, ISO 7-Layer Model
Protocol Stacks
Horizontal (Peer-Peer) Communication
SAPs
P t
D a
Transmission Protocol Stack
Vertical (Entity-Entity) Communications
ro ocol Encapsulation
at Tunneling
GPRS Protocol Stacks
Network Access Signalling Protocol Stack
Core Network Signalling Protocol Stack
?


85


7. GPRS Protocols

86

7. GPRS Protocols
_____________________________________________________________________

This section of the course looks in more detail at GPRS protocols. These are the protocols
which provide the physical connectivity between the mobile station and the external access
point to the GPRS network (the GGSN) and control the packet data flow between these two
points. This data is in the form of user or signalling traffic.

In order to describe the function of each protocol entity in a logical fashion, the passage of a
data packet from a GPRS-enabled MS to a GGSN will be described as it crosses each releva
terface in turn i.e.:
The MS-PCUSN (U
m
) Interface
The PCUSN-SGSN (G
b
) Interface
The SGSN-GGSN (G
n
) Interface

nt
in

GPRS Transmission Protocols GPRS Transmission Protocols
IP IP- -based Core based Core
Network Network
Internet Internet
GGSN
U U
m m
G G
b b
G G
n n
G G
i i
Frame Relay Frame Relay
Network Network
BTS PCU
BSS BSS
SGSN
GSM RF GSM RF
ISDN/E1 ISDN/E1
TDMA/GMSK TDMA/GMSK
A A
GPRS GPRS
PSPDN PSPDN

7.1 Introduction

7. GPRS Protocols

87

_____________________________________________________________________

U U
m m
(Air) Interface Protocols (Air) Interface Protocols
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP
L1
L2
IP
Network
Service
BSSGP
GTP
L1bis
BSC/PCU
BSC/PCU
U U
m m
G G
b b
G G
n n
G G
i i

7.2.1 HIGHER LAYER PROTOCOLS

U U
m m
Interface Interface Higher Layer Protocols Higher Layer Protocols
BSC/PCU
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Relay Relay
Relay Relay
MS MS BS BSC/PCUSN C/PCUSN SGSN SGSN GGSN GGSN
UDP/TCP
GTP
L2
IP
L2
IP/X.25
L1 L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP
L2
IP
Network
Service
L1
BSSGP
GTP
L1bis
BSC/PCU
U U
m m
G G
b b
G G
n n
G G
i i

7.2 The MS-BSS U
m
(Air) Interface

7. GPRS Protocols

88

Application Layer:
Generated by TE connected to MT
Application generated data
Transparent to GPRS Network
IP/X.25 Layer:
Generates packet data.
Adds routing formation to application data
Interrogated by GGSN for correct routing
Higher Layer Protocols Higher Layer Protocols

ted
l pass over the GPRS networ seamlessly from end to end.

7.2.1.1 Application Level
in

The higher layer protocols are transparent to the GPRS network. The data packets genera
at this leve k

At the highest level an application oper ting at an MS will intercommunicate with the same
application running on a different host t a geographically remote location. This application
information passes through the GPRS network (and any subsequent network) transparently.
The information is unchanged by the G RS infrastructure, which is responsible only for
reliable transportation of this informat cross the network.

7.2.1.2 Packet Service Level (IP/X.25)
a
a
P
ion a

The application data generated by the application running on the Terminal Equipment (TE)
connected to the Mobile Terminal (MT) is first encapsulated within a routing protocol for
correct transmission and delivery to its ination. In todays environment this protocol is
likely to be the Internet Protocol (IP), al ough a number of legacy X.25 packet protocol
networks still exist. The routing infor ation added at this level is examined by the GGSN to
l to

dest
th
m
ensure it knows the correct destination or routing the data either to a network externa
GPRS or to an MS within the GPRS network.
f

7. GPRS Protocols

89

7.2.2 NSAPI and SAPI FUNCTIONALITY EXPLAINED

Service access points (SAPs) can be visualised as tunnels between protocol layers. In order
that data knows which tunnel to used, they each must have a unique identifier

7.2.2.1 NSAPIs

Network Service Access Points (NSAPs) can be visualised as tunnels between the GPRS
Network and SNDCP layers, each identified by a unique NSAP identifier (NSAPI).

A GPRS users subscription profile can be configured to allow access to a number of different
networks, each using a different Packet Data Protocol (PDP). The GPRS Recommendations
generally support IPv4, IPv6 and X.25 PDPs. Within each of these PDPs, a number of
addresses can be specified in the subscription profile. Therefore, an NSAPI represents the
PDP type and the address within that PDP type.

The MS dynamically assigns an NSAPI to a PDP context from a pool of 15 numbers (1-15, 0
being reserved) each time a new PDP context is activated. When the PDP context is
eactivated, the NSAPI is returned to the available pool.

d

Using Using SAPIs SAPIs and and NSAPIs NSAPIs
AOL AOL
IPv4 IPv4
AOL AOL
IPv6 IPv6
N-PDU
NSAPIs
SAPIs
Freeserve Freeserve
IPv4 IPv4
X.25 X.25
Service Service
in
tion
PDP Contexts defined
GPRS users subscrip
profile
SN-PDU
GMM GMM
Signalling Signalling
SMS SMS
SNDCP
Other Layer 3 Services
4 3 2 1
7 1 3 5 9 11
LLC

Using th

sep s (IPv4) is associated with two
NS APIs have been allocated.

e diagram above to illustrate this principle:
Three PDPs are shown, IPv4, IPv6 and X.25. Each would generally be allocated a
arate NSAPI. However, in this case, one of these PDP
ISPs, AOL and Freeserve. Therefore they also need to be differentiated by unique
API. Hence 4 NS

7. GPRS Protocols

90

.2.2.2 SAPIs 7
SAPIs are used to identify the service being offered by the LLC layer to higher layers. SAPIs
are differentiated firstly by service i.e. GMM, SMS or SNDCP (user data) service. The user
data service is further differentiated by the requested QoS delay class i.e. QoS 1 to QoS 4

A SAPI can support multiple NSAPIs. Using the diagram above to illustrate this principle:

NSAPI services 1 and 2 both require QoS 4 and therefore are both allocated
SAPI 11.
NSAPI service 3 requests QoS 3 so is allocated SAPI 9.
NSAPI service 4 requires QoS 1 so is allocated SAPI 3.

At the SNDCP layer, SAPI 1 is reserved for GMM signalling data and SAPI 7 is reserved for
SMS data.

SAPI Definitions SAPI Definitions
User Data QoS4 11 1011
SMS 7
0111
GMM 1 0001
Description SAPI

ervice Access Points (SAPs) can be visualised as tunnels between the GPRS SNDCP and LLC
laye entified by a unique SAP identifier (SAPI).

S
rs, each tunnel being id

7. GPRS Protocols


7.2.3 SUB-NETWORK DE
91
PENDANT CONTROL PROTOCOL (SNDCP)
.2.3.1 SNDCP Layer Functions

7
PRS is designed to allow different application layer protocol packets (e.g. X.25 or IP) to pass
ansparently across the GPRS network cloud.
he SNDCP layer provides protocol transparency to the GPRS network for network service
user packet formats (e.g. X.25 or IP) and converting them into the payload
of one o rm
fashion
This tra from the IP/X.25 layer and segmenting it
into SN
Link Co

G
tr

T
s by taking specific
r more equal-length segments which are then presented to the LLC layer in a unifo
.

nsparency is achieved by taking packet data
DCP Packet Data Units (SN-PDUs). These SN-PDUs are then passed to the Logical
ntrol Layer for onward processing (see LLC section below).
U U
m m
Inter Interface face SNDCP Protocol SNDCP Protocol
GSM RF GSM RF
MAC MAC
RLC RLC
SNDCP SNDCP
IP/X.25 IP/X.25
Applicatio Application n
LLC LLC
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
LLC
SNDCP SNDCP
UDP/TCP
L1
MAC MAC
RLC RLC
L1bis
Network
Service
BSSGP
L2
IP
Network
Service
BSSGP
GTP
L1bis
BSC/PCU
BSC/PCU
U U
m m
G G
b b
G G
n n
G G
i i
SGSN SGSN

The protocols used above SNDCP consist of commonly used network protocols such as X.25
and IP. They all use the same SNDCP entity that then performs the multiplexing of data
coming from different sources (e.g. different applications running on the same TE), which is
then transferred using the service provided by the LLC layer.

7. GPRS Protocols

92

SNDCP Layer Functions SNDCP Layer Functions
An Interface between higher level network protocols and the
GPRS LLC layer.
Translation of higher level packets into SNDCP packets
(SN-PDUs) through segmentation and re-assembly
Applies an NSAPI packet encapsulation to identify context
Data Compression
Buffering of N-PDUs
Supports acknowledged and unacknowledged data transfer
modes
Provides NSAPI-specific buffering for Ack and Nack modes

N N- -PDU to SN PDU to SN- -PDU Segmentation PDU Segmentation
LLC Layer
Header Payload
Network Layer
Header Payload
SNDCP Layer
Network PDUs
(N-PDUs)
SNDCP
PDUs
SN-PDU SH SN-PDU SH SN-PDU SH SN-PDU SH SN-PDU SH
Higher Level (IP/X.25) Data Packet
SH SNCDP PDU Header
Compression Compression
He..

Each of these different sources would use a unique association with a GGSN at the other side
of the GPRS network (known as PDP Contexts see later). For example, X.25 packets
generated at the MS would have a different association with the GGSN to that associated with
IP packets generated by the MS.

7. GPRS Protocols

93

7.2.3.2 SNDCP SN-PDU Header

The SNDCP Packet Data Unit (SN-PDU) header contains the NSAPI address (see below for
NSAPI explanation), the Network PDU (N-PDU) number and any compression coding
information.

SNDCP SN SNDCP SN- -PDU Format PDU Format
The SNDCP Header comprises 2 (SN-Data PDU) or 5 (SN-
Unitdata PDU) octets:
8 7 6 5 4 3 2 1
1 X F T M
2
n
8 7 6 5 4 3 2 1
1 X F T M
2
3
4 E
5
n
NSAPI
DCOMP PCOMP
NSAPI
Data Segment
N-PDU# (continued)
N-PDU (extended)
Data Segment
PCOMP
SEGMENT # N-PDU#

X t

F s
no assigned defaults to 0.
Fir t Bit. 1 = first SN-PDU of the N-PDU. 0 = not the first SN-PDU of the N-PDU .

p T Ty e Bit. Defined the SN-PDU type; 1 for SN UNITDATA PDU for and 0 for SN DATA
DU. P

M More Bit . Normally set to 1 if more SN-PDUs of the N-PDU are to follow. Set to 0 for
e last SNDCP SN-PDU of the N-PDU. th

NSAPI Network Service Access Point Identifier supplied from the network layer.
DCOMP Data compression type. 0 = no compression.

PCOMP Header compression type. 0 = no compression.

Segment# - SN-PDU segment sequence number of the current N-PDU (range 0-15).

N-PDU# - Packet Sequence number of current N-PDU (range 0-255 acknowledged mode, 0-
4095 unacknowledged mode

7. GPRS Protocols

94

7.2.3.3 SNDCP Buffering

-PDUs are buffered in the SNDCP layer before they are compressed, segmented and
ansmitted to the LLC layer. A separate buffer is allocated for each NSAPI.
uffered N-PDU is
LC layer.
.2.4 LOGICAL LINK CONTROL (LLC) PROTOCOL
N
tr

For acknowledged data transfer, the SNDCP layer buffers an N-PDU until the LLC layer
successfully receives all SN-PDUs carrying segments of that N-PDU. Once confirmation of
ceipt of the complete N-PDU has been received from the LLC layer, the b re
discarded.

For unacknowledged data transfer, the SNDCP layer deletes the N-PDU immediately after the
st associated SN-PDU has been transmitted to the la
L

7

U U
m m
Interface Interface LL LLC Protocol C Protocol
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis
Network
Service
BSSGP
LLC LLC
SNDCP
UDP/TCP
L1
L2
IP
Network
Service
BSSGP
GTP
L1bis
BSC/PCU
BSC/PCU
U U
m m
G G
b b
G G
n n
G G
i i
SGSN SGSN

Having converted the higher level packets into equal-length SNDCP SD-PDUs, these SN-
PDUs are then passed to the LLC layer.

7.2.4.1 LLC Functions

se
nd reliable transportation of information
etween Layer 3 entities in the MS and SGSN, for example, between the GMM layer 3 entity
the MS and the GMM layer 3 entity in the SGSN.
The LLC is considered to be sub-layer of layer 2 in the ISO 7-layer model. The main purpo
of the LLC is to provide a secure (encrypted) a
b
in

7. GPRS Protocols


LLC Layer Functions LLC Layer Functions
Secure and reliable logical link between MS and SGSN
Independent of lower layers
Conveys Signalling (GMM/SM), SMS and SNDCP data in
variable length information packets
Supports Acknowledged and Unacknowledged data transfer
modes

ed between the MS and the SGSN, LLC data is
assed transparently through the BSS. This also enables to LLC to be independent of the
dio technology implemented over the air
f LLC-
Procedures for ciphering LLC PDUs (applicable to both acknowledged and
unacknowledged modes)
Procedures for error detection by interrogating the LLC Frame Check Sequence (FCS)
in acknowledged mode (unacknowledged mode has no error recovery procedures).

Supports precedence QoS classes
Based on HDLC format (less flag fields)

Because the end-to-end relationship is establish
p
ra
interface.

The LLC Layer also supports:

Transfer of SNDCP SN-PDUs between the SNDCP Layer and the LLC layer.

Procedures for acknowledged and unacknowledged point-to-point delivery o
PDUs between the MS and the SGSN.

Procedures for point-to-multipoint delivery of LLC-PDUs between the MS and the
SGSN.

95

7. GPRS Protocols

96

7.2.4.2 Logical Link Identifiers

Logical Link Identifiers Logical Link Identifiers
Data Link Connection Identifier (DLCI)
Uniquely identifies a Logical Link connection between a specific MS and the
SGSN
Assigned by SGSN on completing a GPRS Attach Procedure
Comprises a SAPI and Temporary Logical Link Identifier (TLLI)
SAPI
Identifies the service required by each peer entity (MS and SGSN)
TLLI
Uniquely identifies the MS.
Derived from the MSs assigned P-TMSI

A LLC protocol link is established between the MS and the SGSN upon executing the GPRS
Attach procedure. This link is unique to a particular MS and is uniquely identified by a Data
Link Connection Identifier (DLCI). This DLCI comprises the Service Access Point Identifier
(SAPI) and a Temporary Logical Link Identifier (TLLI). .

The SAPI is used to identify the service access point on the SGSN side and the MS side of the
LLC interface. The SAPI is carried in the address field of each LLC frame.

The TLLI is used to identify a specific MS. TLLI assignment is controlled by GMM. TLLI is
ot carr
furt r

he DL
ssi

Therefo
API. O passed to the higher layer, individual
ackets are distinguished by the TLLI associated with individual MSs.
nce packets have arrived at the individual MSs, their ultimate destination is distinguished
e NSAPI. An MS can have multiple NSAPIs active at any one time.
hese Identifiers are covered in more detail in the later section of the notes entitled Packet
outing and Transfer.

n ied in LLC frames, but in BSSGP messages and in RLC/MAC blocks (see below for
he explanation of RLC/MAC blocks).
CI is dynamically allocated by the SGSN each time a LLC link is established. TLLI T
a gnment is controlled by the GMM Control layer
re, at the LLC layer, the destination of different packets is only distinguished by their
nce the SAPI has been reached and data is to be S
p

O
th

T
R

7. GPRS Protocols

97

7.2.4.3 Logical Link Frame Format

LLC Frame Structure LLC Frame Structure
SAPI
to RLC/MAC Layer
Address
Field
Frame
Check
Sequence
From Layer 3
Control
Field
Transfer Mode
Frame Type
LLC Frame No
Variable Length Information (payload) Field
Header

The LLC frame format is based on the well-known High level Data Link Control (HDLC)
rotocol (as used in X.25), less the frame header and footer flags (a 01111110 sequence at ea
nd of the frame). It includes sequence control, ordered delivery of LLC PDUs, flow control,
etection of transmission errors and ARQs.
inus the BSSGP protocol control
formation (see BSSGP later).

Ad
p
e
ch
d

The length of a LLC PDU cannot exceed 1600 octets m
in
dress Field (1 octet)

4 3 2 1 8 7 6 5
PD C/R X X SAPI

s
set to 1 is received, it is treated as an invalid frame.

C/R. The Command/Response bit identifies a frame as either a command or a response.
esponse = 1. The SGSN side is the opposite.

PD. The Protocol Discriminator bit indicates whether a frame is an LLC frame or belong
to a different protocol. LLC frames have this bit set to 0. Currently, if a frame with the
PD bit
On the MS side Command = 0 and R

X = not defined

SAPI = Service Access Point Identifier (see below for explanation)

7. GPRS Protocols

98

Control Field
The control field typically comprises up to 3 octets but can be extended to 36. The control

ontrol (U) Frame 1 octet control field length

Acknowledged Mode. This mode specifies 2 frame types:

Information (I) Frame 3-36 octet control field length
th
The frame number is contained within the control field of each fame type.

field contains information relating to the transfer mode and frame type. The transfer
mode can be either acknowledged or unacknowledged mode, each mode have specific
frame types:
Unacknowledged Mode. This mode specifies 2 frame types:

Information (UI) Frame 2 octet control field length
C
Supervisory (S) Frame 2-34 octet control field leng

Frame Check Sequence (FCS) Field
This is a fixed 3-octet field containing a 24-bit cyclic redundancy check (CRC) code. Th
code is used to dete
is
ct bit errors in the header and Information fields.

LLC Frame Format LLC Frame Format
8 7 6 5 4 3 2 1
1 PD C/R X X
3
n
n+1
n+m
n+m+1
n+m+2
n+m+3
Information Field (Variable Length)
SAPI
Control Field (max 36 octets)
FCS Field (3 octets)
Address Field
PD = Protocol Discriminator bit
C/R = Command/Response bit
X = not defined
SAPI = Service Access Point Identifier
FCS = Frame Check Sequence

7. GPRS Protocols


7.2.4.4 LLC Frame Creation

LLC Fr LLC Frame Creation ame Creation
Header Payload Network Layer Header Payload
SNDCP Layer
Network PDUs
(N-PDUs)
SNDCP
segments
SNDCP
segment
PH
SNDCP
segment
PH
SNDCP
segment
PH
SNDCP
segment
PH
SNDCP
segment
PH
FH SNDCP Seg nt me FCS LLC Frame
LLC Layer
to RLC/MAC Layer
PH

7.2.4.5 LLC Acknowledged and Unacknowledged Modes

LLC Acknowledged/Unacknowledged Modes LLC Acknowledged/Unacknowledged Modes
Unacknowledged Mode:
Known as Asynchronous Disconnected Mode (ADM)
LLC Transmissions may be initiated without prior establishment of a logical connection
LLC does not guarantee ordered delivery
LLC can detect but not correct errors
Depending on protected or unprotected mode, erroneous packets may be forwarded or
discarded as appropriate
Acknowledged Mode:
Known as Asynchronous Balanced Mode (ABM)
Each terminating entity is responsible for flow control and error recovery
Provides mechanisms for a reliable, ordered packet delivery service
Each terminating entity acts as a data source and data sink allowing bi-directional flows

99

7. GPRS Protocols

100

Unacknowledged Mode:

A logical link entity may initiate transmissions to a peer entity without prior
establishment of a logical connection with the peer entity.
LLC does not guarantee in-order delivery.
LLC can detect errors in a received frame and depending on whether the frame is sent
in protected mode or not, either discard or deliver the erroneous frame.
No error recovery procedures are defined at the LLC layer. Higher-layer protocols
can be used to provide reliability, if needed. This mode of operation is known as
Asynchronous Disconnected Mode (ADM).

Acknowledged Mode:

A balanced data link involves two participating entities, and each entity assumes
responsibility for the organisation of its data flow and for error recovery procedures
associated with the transmissions that it originates.
Each entity operates as both a data source and data sink in a balanced link, allowing
information to flow in both directions.
This mode of operation is known as Asynchronous Balanced Mode (ABM), and
provides a reliable service with in-order delivery.

7.2.5 RADIO LINK CONTROL (RLC) PROTOCOL

U U
m m
Interface Interface RLC Layer RLC Layer
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP
L1
L2
IP
Network
Service
BSSGP
GTP
L1bis
BSC/PCU
BSC/PCU
U U
m m
G G
b b
G G
n n
G G
i i

7. GPRS Protocols

101

7.2.5.1 RLC Functions

The RLC protocol provides a reliable communications link across the radio path for
transporting data packets passed to it from the Logical Link Control (LLC) layer. It is also
responsible for:

Transferring Logical Link Layer (LLC) Packet Data Units (PDUs) between the LLC
layer and the MAC layer.

Segmentation and reassembly of LLC PDUs into RLC data blocks.

Segmentation and reassembly of RLC/MAC control messages into RLC/MAC
control blocks.

Backward Error Correction (BEC) procedures. The RLC adds a Block Check Sequence
(BCS) to each RLC Radio Block. This enables errors in each block to be detected.
Correction of detected errors is achieved through selective block retransmission. This
process is generally known as Automatic ReQuest for retransmission (ARQ).

RLC Layer F RLC Layer Functions unctions
Provides reliable radio link.
Transfer of LLC-PDUs between LLC and MAC
Segmentation and reassembly of RLC/MAC control
messages into RLC/MAC blocks
backward error correction

layers.
Segmentation and reassembly of LLC-PDUs into
RLC data blocks.
Provision of ARQ

7. GPRS Protocols

102

7.2.5.2 RLC Block Format

Uplink RLC Data Block Uplink RLC Data Block
Spare (if present)
Octet N2
Octet N2-1
Octet M+1
LLC PDU(s)
Octet M
(optional)
E M Length Indicator
Octet 3 (optional) E M Length Indicator
Octet 2 E BSN
Octet 1 FBI TFI PR
1 2 3 4 5 6 7 8
PR = Power Reduction E = Extension bit
TFI = Temporary Flow Indicator M = More bit
FBI = Final Block Indicator
BSN = Block Sequence Number

PR Power Reduction Field
Indicates a power level reduction of the urrent RLC block. The amount of the
reduction is identified by the 2-bit code.

TFI Temporary Flow Indicator
c

Identifies the Temporary Block Flow (TBF) to which this data block belongs

FBI Final Block Indicator
Indicates the last RLC block in the associated TBF.
BSN Block Sequence Number
Indicates the sequential number of the current block in the associated TBF.

E Extension Bit
Indicates the presence of an optional octet in the RLC data block header

M More Bit
The M bit, along with the E bit and the Length Indicator (LI), are used to delimit LLC
PDUs within a TBF. When the M bit is present it indicates whether or not another
LLC PDU follows the current one within the RLC data block.

7. GPRS Protocols

103

7.2.5.3 RLC Block Generation

Radio Link Control Block Generation Radio Link Control Block Generation
FH Information field FCS
LLC LLC PDUs PDUs
B
H
BCS
B
H
Information
field
BCS
B
H
BCS
LLC Layer LLC Layer
segment
RLC Blocks RLC Blocks
Information
field
Information
field
segment segment
MAC MAC
BSS BSS
RLC RLC
MS MS
RLC RLC
Link Link
MAC MAC
Link Link

Packets to the RLC layer where they are segmented into
qual size blocks and encapsulated within the RLC protocol header and BCS before being
pas e
of each eing employed (see below).

AC

generated at the LLC layer are passed
e
sed to the MAC layer. Although the total block size is constant, the user data payload siz
block is dependant upon the coding scheme b
In addition, control messages generated at the RLC/MAC later segmented into RLC/M
control blocks. Control blocks are transmitted with a higher precedence than RLC data
blocks.

7. GPRS Protocols

104

.2.6 MEDIUM ACCESS CONTROL (MAC) PROTOCOL 7

U U
m m
Interface Interface MAC Layer MAC Layer
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
2 2 L L
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP
L1
L2
IP
Network
Service
BSSGP
L1bis
BSC/PCU
BSC/PCU
GTP
U U
m m
G G
b b
G G
n n
G G
i i

7.2.6.1 MAC Layer Functions

MAC Layer Functions MAC Layer Functions
Multiplexing
Channel allocation
Access control
Uplink contention arbitration
Downlink packet queuing and scheduling
QoS prioritising

7. GPRS Protocols

105

The Medium Access Control (MAC) layer protocol defines the procedures that enable
multiple MSs to share a common transmission medium, which may itself consist of a number
of physical channels.

For MS-originated access, the MAC layer provides for procedures for the arbitration between
multiple MSs simultaneously attempting to access the shared transmission system.

For MS-terminated connections, the MAC layer provides procedures for queuing and
scheduling of access attempts.

The Medium Access Control (MAC) layer protocol handles packet resource allocation and
multiplexing. It is responsible for:

The efficient multiplexing of data and control signalling packets on both the uplink
and downlink. On the downlink, multiplexing is controlled by a scheduling
mechanism. On the uplink, multiplexing is controlled by resource (channel)
allocation to individual users.
Mobile originated channel access, contention resolution between channel access
attempts including collision detection and recovery.
Mobile Terminate channel access, scheduling of access attempts including queuing of
packet accesses.
applied.
7.2.6.2 MAC Access Modes
Priority handling when QoS levels have been

MAC Access Modes MAC Access Modes
Dynamic Allocation
Extended Dynamic Allocation
Fixed Allocation
Exclusive Allocation

7. GPRS Protocols

106

THE MAC Protocol provides for four modes of access:

Dynamic Allocation
An MS detects an assigned USF for each assigned PDCH allowing it to transmit a
block or group of 4 blocks per PDCH. The MS monitors all assigned downlink
PDCHs looking for an assigned USF. When it detects a valid USF, the MS transmits
either a single RLC/MAC block or a group of 4 blocks on that PDCH only.

Extended Dynamic Allocation
The mode extends Dynamic allocation to allow greater uplink data throughput. The
MS monitors all assigned downlink PDCHs looking for an assigned USF. When it
detects a valid USF, the MS transmits either a single RLC/MAC block or a group of 4
blocks on that and all higher numbered PDCHs.

Fixed Allocation
For fixed allocation, no USF is used. The MS is allocated a fixed number of blocks for
uplink transmission on a fixed PDCH

Exclusive Allocation.
The MS is granted exclusive rights to transmit on each assigned PDCH for the
duration of the uplink TBF. This mode is only applicable in dual transfer mode (i.e.
simultaneous GSM CS connection and GPRS PS connection).

7.2.6.3 MAC Header

Downlink MAC Hea Downlink MAC Header der
USF S/P RRBP Payload Type
1 2 3 4 5 6 7 8
RLC Block
Payload Type = Control/data block
RRBP = Relative Reserved Block Period
S/P = Supplementary Polling bit
USF = Uplink State Flag

7. GPRS Protocols

107

Payload Type
Defines the RLC payload type contained with the MAC block i.e. control payload
data or user payload data

RRBP Relative Reserved Block Period
The RRBP value specifies the identity of a single uplink block in which the mobile
station shall transmit either a PACKET CONTROL ACKNOWLEDGEMENT message
or a PACCH block to the network.

S/P Supplementary Polling bit
The S/P bit is used to indicate whether the RRBP field is valid or not valid (1- RRBP
valid, 0 RRPB invalid).

USF Uplink State Flag
The USF field is sent in all downlink MAC blocks and indicates the owner or use of
the next uplink radio block on the same timeslot. The USF field is three bits in length
and eight different USF values can be assigned, except on PCCCH, where the value
111 (USF=FREE) indicates that the corresponding uplink radio block contains
PRACH.

7.2.6.4 MAC Layer Block Generation

At the MAC layer, additional header information is added for controlling the Air Interface
traffic management. This information differs depending on the direction of traffic flow.

U U
m m
Interface MAC Frame Interface MAC Framess Generation Generation
FH Information field FCS
LLC PDUs LLC PDUs
B
H
BCS
B
H
Information
field
BCS
B
H
BCS
LLC Layer LLC Layer
segment
RLC Blocks RLC Blocks
Information
field
Information
field
segment segment
MAC MAC
BSS BSS
RLC RLC
MS MS
RLC RLC
Link Link
MAC MAC
Link Link
MAC Frame MAC Frame
MAC
HEADER
RLC Block

7. GPRS Protocols

108

7.2.7 GSM PHYSICAL (RF-LINK) LAYER PROTOCOLS

U U
m m
Interface Interface GSM RF Layer GSM RF Layer
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP
L1
L2
IP
Network
Service
BSSGP
GTP
L1bis
BSC/PCU
BSC/PCU
U U
m m
G G
b b
G G
n n
G G
i i

Link Layer Link Layer
The Link Layer is divided into two parts:
Radio F
car
requency (RF) part:
rier frequency
modulation schemes
ons between MS and network
FEC

TRX characteristics
channel structures
Physical Link part:
communicati
burst interleaving

7. GPRS Protocols

109

he Link Layer divided into two parts. T

.2.7.1 Radio Frequency (RF) Sub-Layer 7

The RF layer is responsible for:

Carrier frequency characteristics
n techniques employed
acteristics and performance requirements.
GSM Radio Channel Structures
.2.7.2 Physical Link Sub-Layer
Modulatio
Tx / Rx char

ation between the MSs and the network. It is
sponsible for:
orrection (FEC) Coding
7

The physical layer provides communic
re

Forward Error C . FEC allows the detection and correction of
errors using a Frame Check Sequence (FCS). In some circumstances, errored code
words cannot be corrected, in which case, the error is reported only.
Burst Interleaving. Interleaving breaks a radio block into 4 parts and burst transmit
them over 4 consecutive TDMA frames. This reduces the vulnerability of data to
burst errors on the radio path.
s

ormatting 7.2.7.3 Radio Burst F

U U
m m
Interface Burst Formatting Interface Burst Formatting
B
H
BCS
B
H
Information
field
BCS
B
H
BCS
RLC Block RLC Block
Information
field
Information
field
MAC MAC
BSS BSS
RLC RLC
MS MS
RLC RLC
Link Link
MAC MAC
Link Link
MAC
HEADER
RLC Block
114 bit
TDMA
Burst
114 bit
TDMA
Burst
114 bit
TDMA
Burst
114 bit
TDMA
Burst
MAC Frame MAC Frame

7. GPRS Protocols

110

The RLC Block, together with the MAC header (i.e. the MAC frame) forms the Radio Block.
This radio block is divided into four 114-bit data bursts.

In order to integrate Control channels onto the air interface, GPRS has introduced a new 52-
frame multiframe structure. Each multiframe contains 12 radio blocks and each radio block
is divided into four 114-bit frames or data bursts.

7.2.7.4 Radio Burst Interleaving

If all 4 bursts of a radio block from the same user were to be transmitted consecutively in the
same TDMA frame, a burst of noise could disrupt the whole transmission. Therefore to make
the data transfer more robust, each burst of a 114-bit data block is transmitted in a timeslot of
consecutive TDMA frames as illustrated above.

1
Burst Interleaving Burst Interleaving
B0 B1 B2 B3 B4 B5 B6 B7 B8 B9 B10 B11 T T X X
0 1 2 3 4 4 6 7
1 data burst
114 data bits
1 radio block
456 data bits
1 TDMA frame
B0 to B11 = Radio Blocks
T = PTCCH (Timing Control Channel)
X = Idle
52-frame multiframe
0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
3 8.25 57 data bits
26
training
bits
1 3 57 data bits
1 radio burst
156.25 bits (0.577mS)
Physical Link Part Physical Link Part
Radio Frequency Part Radio Frequency Part

Each data burst is then divided into two 57-bit blocks a d inserted into a 158.25-bit radio burst (1
timeslo

n
t) for transmission across the radio interface.

7. GPRS Protocols


111
.2.8 U 7
m
INTERFACE PROTOCOLS AT THE BSC

U U
m m
(Air) Interface BSC Protocols (Air) Interface BSC Protocols
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP
L1
L2
IP
Network
Service
BSSGP
GTP
L1bis
BSC/PCU
BSC/PCU
U U
m m
G G
b b
G G
n n
G G
i i

When data is received at the BSC, the d ta is de-interleaved and decoded. The MAC
encapsulation information is stripped a ay leaving the RLC data blocks as originally
constructed at the MS. The relay functi n then passes this formatted data to the BSSGP
protocol at the G
b
interface

_____________________________________________________________________

7.3.1 Gb INTERFACE OVERV
a
w
o
IEW

In contrast to the GSM A-interface, where a single user has the sole use of a dedicated
physical resource throughout the dura on of a circuit-switched call, irrespective of
information flow, the GPRS Gb-interfa allows many GPRS users to be multiplexed over a
common physical resource.
GPRS signalling and user data may also be combined on the same physical resources
therefore no separate dedicated physic resources are required to be allocated for signalling
purposes.
7.3 The BSS-SGSN G
b
Interface
ti
ce
al

7. GPRS Protocols

112
Access rates per GPRS user may vary f ro data to the maximum possible bandwidth
(e.g. the available bit rate of an E1).

rom ze
The The G G
b b
Interface Interface
GSM RF
MAC
RLC
LLC
SNDCP
IP/X.25
Application
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF
MAC
RLC
L1bis L1bis
Network k
e e
Networ
Servic Servic
BSSG BSSGP P
LLC LLC
SNDCP SNDCP
UDP/TCP
L1
L2
IP
Network Network
Service Service
BSSGP BSSGP
GTP
L1bis L1bis
BSC/PCU
BSC/PCU
SGSN
U U
m m
G G
b b
G G
n n
G G
i i

The Gb interface allows many users to e multiplexed over the same physical link using
Frame Relay (FR) packet switching tec Bandwidth is allocation on a demand basis
and is immediately released and reallo ted on cessation of the demand. This is in contrast to
the GSM A interface where a single user has exclusive use of a dedicated physical resource for
the duration of the call irrespective of a tivity. GPRS signalling and user data are sent in the
same transmission plane and. Data rat er the Gb interface may vary for each user
without restriction, from no data to the ximum possible rate (e.g. 1984 kbps for an E1 link).

The Gb interface connects the SGSN to BSSs using Frame Relay Technology, allowing
exchange of signalling information and a. If a BSS contains more than one Packet Control
Unit (PCU), the SGSN must have a dis ct Gb interface to each PCU in the BSS.

The protocol architecture on the Gb interface is divided into two parts:

an upper part, which interconnects the MS and the SGSN directly, comprising the
LLC and SNDCP layers. These layers are used for transfer of user data or signalling
data between the SGSN and the MS and are passed transparently through the BSS.

a lower part, which interconnects the BSS and the SGSN, comprises the L1bis,
Network Services and BSSGP layers. These layers are used to ensure reliable passage
of information between the BS and the SGSN.

b
hnology.
ca
c
es ov
ma
dat
tin
S

7. GPRS Protocols

113

7.3.2 THE BASE STATION SUBSYSTEM GPRS PROTOCOL (BSSGP)

G G
b b
Interface Interface BSSGP Protocol BSSGP Protocol
GSM RF
MAC
RLC
LLC
SNDCP
IP/X.25
Application
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF
MAC
RLC
L1bis L1bis
Network Network
Service Service
BSSGP BSSGP
LLC LLC
SNDCP SNDCP
UDP/TCP
L1
L2
IP
Network Network
Service Service
BSSGP BSSGP
GTP
L1bis L1bis
BSC/PCU
BSC/PCU
SGSN
U U
m m
G G
b b
G G
n n
G G
i i

7.3.2.1 BSSGP Functions

BSSGP Layer Functions BSSGP Layer Functions
Transports payload data and signalling between SGSN
and BSS
One BVC is established for each SGSN-BSS connection,
identified by unique BVCI
Provides SGSN-BSS flow control
Separates LLC frames into user data, signalling, GMM
and Network management information
Provides QoS and routing information for SGSN-BSS
data transfer

7. GPRS Protocols

114

The primary functions of the BSSGP include:

in the downlink, provision of r related information used by the RLC/MAC
function by an SGSN to a BSS
in the uplink, the provision of dio related information derived from the RLC/MAC
function by a BSS to an SGSN
the provision of node management control functions to enable an SGSN and a BSS to
interoperate.

The BSS GPRS Protocol (BSSGP) provides means to transport payload (LLC) and signalling
data (GMM/NM/SMS) for the MSs or the BSC between the BSS and the SGSN over the Gb
interface.

7.3.2.2 BSSGP Virtual Circuit
adio
ra
s

BSS-SGSN BSSGP communications takes place via one or more BSSGP Virtual Connections
(BVCs). Each BVC is identified end-to VC Identifier (BVCI). A load sharing
function in the Network Services (NS) layer distributes the BVC traffic on the available
Network Layer Frame Relay Virtual Circuits.

-end by the B
SGSN SGSN
BSSGP BSSGP Virtual Circuits Virtual Circuits
BVCI 1 BVCI 1
BSC BSC
BVCI 2 BVCI 2
BVCI 4 BVCI 4
BVCI 3 BVCI 3
BVCI 2
BVCI 2
BVCI 1
BVCI 1
B
V
C
I 3
B
V
C
I 3
C
I

4
C
I

4
B
V
B
V
G G
b b
Interface
Network Service Network Service
Entity Entity
CI 5 I 5 BV BVC
SGSN SGSN- -BSS Signalling BSS Signalling

For h
spec a
is se v

The SS s for BVC management and for flow control between the BSS
and the SGSN for each cell and for each MS. It separates different packet types
eac GPRS-supporting cell in the BSS area, BSSGP uses one point-to-point BVC. All cell
i . All other signalling dat fic signalling data and user data is sent on the respective BVC
nt ia the Signalling BVC to the BSC.
GP also provides mean B

7. GPRS Protocols

115
(LLC/GMM/SMS etc) from the raw packet data in order to ensure correct onward routing
where necessary.

.3.3 THE NETWORK SERVICE LAYER PROTOCOL 7
e or many Frame Relay
ermanent Virtual Circuits (PVCs) are established between the SGSN and the BSS (known as
etwork Service Virtual Circuits (NS-VCs) for the transfer of signalling and user data. A
Control (NS Control) together make up the NS layer.

7.3.3.1 Network Service Layer Functions

he Gb Network Service interface layer is based on Frame Relay. On T
P
N
Data Link Connection

Identifier identifies the Frame Relay connections between Frame Relay switching nodes.
Frame Relay and Network Service

G G
b b
Interface Netwo ork Service Layer Protocol Interface Netw rk Service Layer Protocol
GSM RF
MAC
RLC
LLC
SNDCP
IP/X.25
Application
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF
LLC LLC
SNDCP SNDCP
UDP/TCP
L1
MAC
RLC
L1bis L1bis
Network Network
Service Service
BSSGP BSSGP
L2
IP
Network Network
Service Service
BSSGP BSSGP
GTP
L1bis L1bis
BSC/PCU
BSC/PCU
SGSN
U U
m m
G G
b b
G G
n n
G G
i i

FR PVCs are established between the SGSN and the BSS. LLC PDUs from many users are
statistically multiplexed onto these PVCs. The PVCs may traverse a network of FR switching
nodes, or may be provided on a simple point-to-point link between the SGSN and BSC.

Upper layer Protocol Data Units are transported across the Gb interface sequentially using
Network Service-Service Data Units (NS-SDUs) generated at the NS level. In the case of
Frame relay, threes NS-SDUs equate to

7. GPRS Protocols

116

Network Services Layer Functions Network Services Layer Functions
Based on Frame Relay (FR) technology
Utilises FR PVCs, known as NS-VCs
One or more NS-VCs established between an SGSN
and each supported BSC
FR N-PDUs transport BSSGP PDUs
Each DLC can contain one or more BVCs
Offers detection of but not recovery from errors
Provides congestion control

ayer Entities

.3.3.2 Network Service L 7

7. GPRS Protocols

Network Service Network Service Entities Entities
(BVCI 1
(BVCI 1- -4) 4)
G G
b b
B B
S S
C C
BVCI 6
BVCI 6
V
C
I 7
V
C
I 7
117
SGSN SGSN
BVCI 5
BVCI 5
B B
S S
C C
BVCI 2
BVCI 2
3 3
BVCI 1
BVCI 1
B
V
C
I
B
V
C
I
B
V
C
I

4
B
V
C
I

4
(B (B
B B
B
V
C
I

8
B
V
C
I

8
V
C
I 5
V
C
I 5- -8
) 8
)
NSEI NSEI- -1 1
NSEI NSEI- -2 2
BVC = BVCI + NSEI

7.3.3.3 Network Service Virtual Links/Connections

G G
b b
NS Layer Virtual Links/Connections NS Layer Virtual Links/Connections
SGSN SGSN
Frame Relay Network Frame Relay Network
BSC BSC
G G
b b
Interface Interface
SGSN SGSN
BSC BSC
PTP 64kbps ISDN PTP 64kbps ISDN
NS NS- -VL VL
NS NS- -VL VL
NS NS- -VC VC
NS NS- -VC VC

7.3.3.4 Network (Frame Relay) Data Link Circuits

7. GPRS Protocols

118

Network Services Layer Network Services Layer DLCs DLCs
BSS 1 BSS 1
SGSN SGSN
FR FR
Switch Switch
BSS 3 BSS 3
FR FR
Switch Switch
FR FR
Switch Switch
FR FR
Switch Switch
BSS 2 BSS 2
FR FR
Switch Switch
19 19
23 23
11 11
67 67
38 38
85 85
32 32 2 2
7 7
44 44
44 44 = Data Link Circuit Identifier (DLC = Data Link Circuit Identifier (DLC
or or
Network Service Virtual Link Network Service Virtual Link
I) I)
Identifier (NS Identifier (NS- -VLI) VLI)
77 77
NS NS- -VC1 VC1
NS NS- -VC2 VC2
NS NS- -VC3 VC3

7.3.4 THE L1bis PHYSICAL LAYER

G G
b b
L1bis Interface Protocols L1bis Interface Protocols
GSM RF
MAC
RLC
LLC
SNDCP
IP/X.25
Application
Relay Relay
Relay Relay
UDP/TCP
GTP
L1
L2
IP
L2
IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF
MAC
RLC
L1bis L1bis
Network Network
Service Service
BSSGP BSSGP
LLC LLC
SNDCP SNDCP
UDP/TCP
L1
L2
IP
Network Network
Service Service
BSSGP BSSGP
GTP
L1bis L1bis
BSC/PCU
BSC/PCU
SGSN
U U
m m
G G
b b
G G
n n
G G
i i

T e
one T1) to connect to a BSS, normally based on G703 (64kbps
speech ch PCM framing) technology. Each physical link supports
one or more Network Service Virtual Circuits (NS-VCs).

h L1bis layer represents the physical layer where data is transported. The SGSN can use
or many physical links (e.g. E1/
annels) and G704 (2Mbps

7. GPRS Protocols


G G
b b
L1bis Interface Protocols L1bis Interface Protocols
One or more physical links between SGSN and
each BSS
Based on E1/T1 links
Supports G703/704 Protocols
Each Physical link can support multiple NS-VCs

_____________________________________________________________________

The The G G
n n
Interface Interface
119
GSM RF
MAC
RLC
LLC
SNDCP
IP/X.25
Application
Relay Relay
Relay Relay
UDP/TCP UDP/TCP
GTP GTP
L1 L1
L2 L2
IP IP
L2
IP/X.25 IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF
MAC
RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP UDP/TCP
L1 L1
L2 L2
IP IP
Network
Service
BSSGP
GTP GTP
L1bis
GPRS Core GPRS Core
Network Network
GGSN SGSN
U U
m m
G G
b b
G G
n n
G G
i i

7.4 The SGSN-GGSN G
n
Interface

7. GPRS Protocols

120
The Gn Interface forms the GPRS backbone (core) network by providing the interface
r, it does include interaction
etween SGSNs for the exchange of user profiles when subscribers move between SGSN
ervice areas.

7.4.1 THE GTP PROTOCOL
specification between the backbone GPRS Support Nodes (GSNs). This interface generally
deals with the interaction between SGSNs and GGSNs. Howeve
b
s

The Gn interface provides a data and signalling interface between GSNs in the GPRS Core
network. The GPRS Tunnelling Protocol (GTP) is used for transporting packet data across the
Gn Interface (see GTP section for details).

In order to ensure reliable transportation of packet data across the GPRS network, all data
packets are encapsulated with GPRS Tunnelling Protocol (GTP) packets. This allows a wide
variety of data packet formats to be transported transparently through the GPRS backbone
between GPRS Support Nodes (GSNs).

GTP is utilised across two GPRS interfaces:

The Gn interface between GSNs within the same network
The Gp interface between GSNs in different networks

The GPRS Tunnelling Protocol (GTP) The GPRS Tunnelling Protocol (GTP)
GPRS Core GPRS Core
Network Network
GGSN SGSN
GSM RF
MAC
RLC
LLC
SNDCP
IP/X.25
Application
Relay Relay
Relay Relay
UDP UDP/TCP /TCP
GTP GTP
L1 L1
L2 L2
IP IP
L2
IP/X.25 IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF
MAC
RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP UDP/TCP
L1 L1
L2 L2
IP IP
Network
Service
BSSGP
GTP GTP
L1bis
U U
m m
G G
b b
G G
n n
G G
i i

7. GPRS Protocols

GPRS Tunnelling Protocol (GTP) GPRS Tunnelling Protocol (GTP)
Enables reliable transportation of multi-protocol
packets between SGSNs and GGSNs.
Two modes of operation:

7.4.1.1 GPRS Tunnelling Concept
Defined for both the Gn (SGSN-GGSN) and Gp
(GGSN-GGSN) interfaces.
Unacknowledged (UDP/IP)
Acknowledged (TCP/IP)

BSC BSC
GPRS Tunnelling Concept GPRS Tunnelling Concept
BTS
GPRS CORE GPRS CORE
INTERNET INTERNET
GTP Protocol
Gp
Gn
GPRS CORE GPRS CORE
Gn
SGSN SGSN
BG BG
GGSN GGSN
BG BG
SGSN SGSN
BSC BSC
BTS

121

7. GPRS Protocols

122
7.4.1.2 Acknowledged and Unacknowledged Modes
Two modes of operation have been defined for the GTP, both of which can be supported
simultaneously:

Unacknowledged Mode (UDP/IP). This mode is used when the user data is based on
Acknowledged Mode (TCP/IP)
connectionless protocols such as IP.

. This mode is used when the user data is based on
connection-oriented protocols such as X.25.
GTP tunnel is defined by two associated PDP contexts in different GSN nodes and is
entified by a Tunnel Identity (TID). The TID identifies the MM (Mobility Management
ntext ID) and the PDP (NSAPI) contexts. The NSAPI is a fixed value between 0 and 15 and
entified a specific PDP context belonging to a specific MM context ID.
GTP tunnel is required for forwarding data packets between an MS and an external packet
ata network. The TID identifies the Mobility Management (MM) and PDP contexts (MM
ontext ID and NSAPI).
he NSAPI is a fixed value between 0 and 15 that identifies a specific PDP context and to
hich specific MM context ID it belongs.

7.4.1.3 GTP Header Format

A
id
co
id

A
d
C

T
w

GTP Header Format GTP Header Format
The GTP Header comprises 20 octets: The GTP Header comprises 20 octets:
8 Octets 8 Octets
8 7 6 5 4 3 2 1
1 PT SNN
2
3
Version Spare '1 1 1'
Message Type
4
10
11
12
13-20
Spare
Spare
Spare
TID (IMSI+NSAPI)
Length
SNDCP NPDU Number
5
6
7
8
9
Sequence Number
Flow Label
20 Octets 20 Octets

7. GPRS Protocols

123

The GTP header contains 16 octets and is used for all GTP messages:
SNN: SNDCP N-PDU Number. Indicates whether the SNDCP N-PDU number is at
octet 9 included or not (set to 0 for signalling messages).
Spare: Reserved for future use - set to 1.
PT: Protocol Type. Indicates GTP version (1= GTP, 0 = GTP).
ates GTP version (Set to 0 if PT=1).
Signalling messages have a value of 1-52, data messages default to
255.
Length: Indicates the length, in octets, of the GTP Packet Data Unit (G-PDU).
Sequence Number: Transaction identity for signalling messages and an incrementing
sequence number for tunnelled T-PDUs. A T-PDU is an IP datagram from an MS or
external network. The T-PDU is the payload that is tunnelled by the GTP.
Flow Label: Uniquely identifies a GTP flow.
SNDCP N-PDU Number: Used in the inter-SGSN routing update procedure to
coordinate data transmission on the link layer between the MS and the SGSN

TID: 8-octet Tunnel Identifier that uniquely identifies virtual tunnels established across the
Gn interface and comprises the IMSI of the associated MS and the NSAPI allocated to the
associated PDP context.

7.4.1.2 GTP Encapsulation

(note: GTP is the version of GTP specifically for gathering charging information)
Version: Indic
Message Type:

GTP Encapsulation GTP Encapsulation
User Data (N-PDU)
L1 L1
User Data Payload
GTP
Header
L1bis L1bis
L2 L2
Network Network
Service Service
LLC LLC
SNDCP SNDCP
UDP/TCP UDP/TCP
GTP GTP
IP IP BSSGP BSSGP
L1 L1
L2 L2
UDP/TCP UDP/TCP
GTP GTP
IP/X.25 IP/X.25
IP IP
GGSN GGSN
SN SN SG SG

7. GPRS Protocols

124

7.4.2 THE TCP/UDP PROTOCOL LAYER

G G
n n
Interface Interface - - TCP/UPD Protocols TCP/UPD Protocols
GSM RF
MAC
RLC
LLC
SNDCP
IP/X.25
Application
Relay Relay
Relay Relay
UDP/TCP UDP/TCP
GTP GTP
L1 L1
L2 L2
IP IP
L2
IP/X.25 IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF
MAC
RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP UDP/TCP
L1 L1
L2 L2
IP IP
Network
Service
BSSGP
GTP GTP
L1bis
GPRS Core GPRS Core
Network Network
GGSN SGSN
U U
m m
G G
b b
G G
n n
G G
i i

TCP or UDP are used to transport GPRS Tunnelling Protocol Packet Data Units (G-PDUs)
across the GPRS backbone network. The ETSI GPRS specification defines UDP as a mandatory
plementation whereas TCP is optional but recommended for X.25 PDP implementations. im

L1 L1
UDP Encapsulation UDP Encapsulation
User Data (e.g IP datagram)
User Data Payload
GTP
Header
User Data Payload
GTP
Header
UDP
Header
L1bis L1bis
L2 L2
Network Network
Service Service
LLC LLC
SNDCP SNDCP GTP GTP
UDP/TCP UDP/TCP
IP IP BSSGP BSSGP
L1 L1
L2 L2
UDP/TCP UDP/TCP
GTP GTP
IP/X.25 IP/X.25
IP IP
GGSN GGSN
SGSN SGSN

7. GPRS Protocols

125

et loss or packet duplication. However, it

7.4.3 THE IP PROTOCOL LAYER
UDP is used for connectionless transmission such as IP where no confirmation of receipt is
required. UDP provides no protection from pack
does allow for rapid passage of packet data (when compared with TCP) with minimum
requirement of network services.

TCP is used for connection-oriented data transmission such as X.25 where confirmation of
receipt of a packet is required in order to control packet flow.

The Internet Protocol (IP) datagram in the Gn Interface is only used in the GPRS backbone
network. The GPRS backbone (core) network and the GPRS subscribers use different IP
addresses.

This makes the GPRS backbone IP network transparent to the subscribers and visa versa. The
GPRS backbone network carries the subscriber IP or X.25 traffic in a secure GPRS Tunnel
using the GPRS Tunnelling Protocol (GTP).
All data from the mobile subscribers or external networks in tunnelled through the GPRS

backbone.

G G
n n
Interface Interface - - TCP/UPD Protocols TCP/UPD Protocols
GSM RF
MAC
RLC
LLC
SNDCP
IP/X.25
Application
Relay Relay
Relay Relay
UDP/TCP UDP/TCP
GTP GTP
L1 L1
L2 L2
IP IP
L2
IP/X.25 IP/X.25
L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF
MAC
RLC
L1bis
Network
Service
BSSGP
LLC
SNDCP
UDP/TCP UDP/TCP
L1 L1
L2 L2
IP IP
Network
Service
BSSGP
GTP GTP
L1bis
GPRS Core GPRS Core
Network Network
GGSN SGSN
U U
m m
G G
b b
G G
n n
G G
i i

7. GPRS Protocols

126
L1 L1
Backbone IP Encapsulation Backbone IP Encapsulation
User D
GGSN GGSN
ata (e.g IP datagram)
User Data Payload
GTP
Header
User Data Payload
GTP
Header
UDP
Header
User Data Payload
GTP
Header
UDP
Header
GPRS
Backbone IP
header
L1bis L1bis
L2 L2
Network Network
Service Service
LLC LLC
SNDCP SNDCP
UDP/TCP UDP/TCP
GTP GTP
IP IP BSSGP BSSGP
L1 L1
L2 L2
GTP GTP
UDP/TCP UDP/TCP
IP/X.25 IP/X.25
IP IP
SGSN SGSN

.4.4 LAYER 2/LAYER 1 PROTOCOL 7

Layer 1 and Layer 2 protocols are vendor-dependant OSI layer 1 and 2 protocols that carry
GPRS backbone network IP datagrams between SGSNs and GGSNs.

_________ ___________________________________________

7.5 Transmission Protocol Summary

_ ________________
Transfer of data packets across the GPRS network is achieved by establishing a number of
physical and virtual connections.

7. GPRS Protocols

GPRS Transport Channels GPRS Transport Channels
SGSN SGSN
MS MS
GGSN GGSN BSS BSS
G G
b b
G G
n n
U U
m m
Virtual Tunnel Virtual Tunnel
BSSGP VC BSSGP VC
BVCI BVCI
TID TID
CONNECTION TYPE CONNECTION TYPE
CONNECTION CONNECTION
IDENTIFIER IDENTIFIER
TDMA TCH TDMA TCH
TCH n TCH n

GPRS Physical Connection Protocols GPRS Physical Connection Protocols
G G
b b
G G
n n
U U
m m
127
SGSN SGSN
MS MS
GGSN GGSN
BSC/ BSC/
PCU PCU
Proprietary Proprietary
TDMA TDMA
E1 E1
BTS BTS
A A
GPRS GPRS
G703 G703
F me Relay ra ra F me Relay
ISDN/E1 ISDN/E1
GMSK GMSK

7. GPRS Protocols

128
GPRS Transmiss sion Protocols GPRS Transmis ion Protocols
SGSN SGSN
MS MS
GGSN GGSN BSS BSS
G G
b b
G G
n n
U U
m m
TCP/UDP TCP/UDP
IP IP
BSSGP BSSGP
RLCP RLCP
SNDCP SNDCP
MACP MACP
LLCP LLCP
GTP GTP

_____________________________________________________________________

the previous parts of this section, data transmission protocols were reviewed. This section reviews
etwork operations i.e. the signalling protocols. Signalling protocols
between network entities for controlling network functions.
hese protocols are covered in two parts.

The first part deals with the signalling proto ols required to control network operations
between the MS and the SGSN. For the purposes of this course, these will be referred to as
Network Access Signalling Protocols.

.6.1 NETWORK ACCESS SIGNALLING PROTOCOL OVERVIEW
In
the protocols used for controlling n
elate to the messaging that passes r

T
c

The second part deals with the signalling protocols required to enable communications
between GPRS network elements within the GPRS Core Network. For the purposes of this
course, these will be known as Core Network Signalling Protocols.

7
7.6 Layer 3 Signalling

7. GPRS Protocols

129
hen data is passed from the Layer 3 into Layer 2 (LLC Layer) at the MS or SGSN, this data relates to
one h

Control data
.6.1.1 User Data
W
of t ree types:
User data
SMS data

7
ser data transfer is passed from the SNDCP layer into the LLC Layer. This process was covered in
etail in the previous section of the notes.
.6.1.2 SMS Data

U
d

7
SMS data refers to data that is using the Short Message Service. SMS text messages are currently
transported over spare GSM signalling channel capacity. However, it is intended that this capability
will eventually be migrated onto GPRS. Integration of SMS into GPRS is covered in the GPRS
Operational Issues section of these notes.

7.6.1.3 Control Data

Control Data refers to the signalling messages required to control GPRS Mobility Management (GMM)
and Session Management (SM). This is the subject of this section of the course.

Layer 3 Services to the LLC Layer Layer 3 Services to the LLC Layer
MAC MAC
RLC RLC
LLC LLC
Relay Relay
L3 L3
L2 L2
GSM RF GSM RF
MS MS BSC/PCUSN BSC/PCUSN
L1 L1 GSM RF GSM RF
MAC MAC
RLC RLC
L1bis L1bis
Network Network
Service Service
BSSGP BSSGP
BSC/PCU
BSC/PCU
SGSN
U U
m m
G G
b b
L1bis L1bis
MAC MAC
RLC RLC
LLC LLC
SGSN SGSN
S
N
D
C
P
S
N
D
C
P
S
M
S
S
M
S
G
M
M
/
S
M
G
M
M
/
S
M
S
N
D
C
P
S
N
D
C
P
S
M
S
S
M
S
G
M
M
/
S
M
G
M
M
/
S
M

7.6.2 SERVICE ACCESS POINT IDENTIFIERS (SAPIs)

7. GPRS Protocols

130

These di are distinguished by the Service Access Point Identifier (SAPI) selected
en data is passed to the LLC layer. The concept of SAPIs was described in the previous section of
this cour
Manage

fferent types of data
wh
se. In this part of the course, the GPRS Mobility Management (GMM) and Session
ment (SM) SAPIs are discussed
Using Using SAPIs SAPIs and and NSAPIs NSAPIs
AOL AOL
IPv4 IPv4
AOL AOL
IPv6 IPv6
N-PDU
NSAPIs
SAPIs
Freeserve Freeserve
IPv4 IPv4
X.25 X.25
Service Service
PDP Contexts defined in
GPRS users subscription
profile
SN-PDU
GMM GMM
Signalling Signalling
SMS SMS
7 1 3 5 9 11
LLC
SNDCP
Other Layer 3 Services
4 3 2 1

7.6.3 GPRS MOBILITY MANAGEMENT (GMM) FUNCTION

MM uses the Logical Link Control (LLC) Layer to transfer control messages between the MS
nd the SGSN. These messages relate to the control of such functions as GPRS attach/detach

G
a
and authentication.
7.6.4 GPRS SESSION MANAGEMENT (SM) FUNCTION

SM uses the Logical Link Control (LLC) Layer to transfer control messages between the M
and the SGSN. These messages relate to the control of such functions PDP Context activati
and deactivations.
S
ons

7. GPRS Protocols

MS-BSS U
m
Interface Protocols
SNDCP, LLC, RLC, MAC, Link Layer
BSS-SGSN G
b
Interface Protocols
BSSGP, Network Services (FR Relay) L1bis physical
layer
GTP, TCP/UDP, IP
SGSN-GGSN G
n
Interface Protocols
G Gb b
IP IP- -based Core based Core
Network Network
131
GGSN
U Um m
G Gn n
G Gi i
Network Network
Frame Relay Frame Relay BTS PCU
BSS BSS
A AGPRS GPRS
SGSN
GSM RF GSM RF
TDMA/GMSK TDMA/GMSK
ISDN/E1 ISDN/E1
PSPDN PSPDN
Internet Internet

7. GPRS Protocols

132

e

Intentional Blank Pag


133

8. M
________________________________________________________________________________
8.1 Intr

Mobility Management (MM) refers to t e GPRS networks procedures for locating, tracking
and monitoring the movement of GPR subscrib throughout the GPRS network. It also
encompasses the procedures for:

obility Management
oduction

h
S ers
Managing the attachment and detachment of GPRS subscribers from the network.
Maintaining records of the subscribers current MM state.
Identifying the current location of each attached subscriber by periodic updating of
location information.


134

____________
8.2 Mobility Management (MM) States
8.2.1 MOBILITY MANAGEMENT STATE OVERVIEW
____________________________________________________________________

For MM purposes, the GPRS subscriber is characterised by one of 3 different MM states. Each
state describes a certain level of functionality and information allocated. The MM information
set is held at both the MS and the SGSN the relationship between the two is known as a
Mobility Management Context.

GPRS defines 3 GMM states:
Idle - camped on but not attached
Standby - attached but not in data transfer mode
Ready - able to transmit/receive packet data
GPRS Mobility Management (GMM) States GPRS Mobility Management (GMM) States


135

8.2.2 MOBILITY MANAGEMENT STATE MODEL

GMM State Models GMM State Models
READY STANDBY IDLE
No Data
Data
Send
GPRS
Detach
GPRS
Attach
SGSN
Time-out
READY STANDBY IDLE
No Data
Transfer
Receive
GPRS
Detach
GPRS
Attach
MS MM State Model:
SGSN MM State Model:

8.2.3 MOBILITY MANAGEMENT STATE CHANGE CONDITIONS

Idle to Ready:
GPRS attach
Ready to Standby:
Ready timer expired
Forced to Standby
Abnormal RLC conditions (SGSN context)
Standby to Ready:
Packet transmission/reception required
Ready to Idle:
GPRS detach
Location cancelled (SGSN context)
Standby to Idle:
Implicit detach (SGSN context)
Location cancelled (SGSN context)
MM State Change Conditions MM State Change Conditions


136

Moving from IDLE to READY:

GPRS Attach: The MS requests access a d the logical link to an SGSN is initiated. A MM
context is established at the MS and SG N.

Moving from READY to STANDBY
n
S
:

READY timer expired: The MS and the GSN MM contexts return to STANDBY state.

Force to STANDBY: The SGSN indicat an immediate return to STANDBY state before the
READY timer expires.

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

Moving from STANDBY to READY
S
es
e or in
:

PDU transmission: The MS sends an L SGSN.
PDU reception: The SGSN receives an C PDU from the MS.

Moving from READY to IDLE
LC PDU to the
LL
:

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

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

Moving from STANDBY to IDLE
a
:

Implicit Detach: The MM and PDP contexts in the SGSN return to IDLE and INACTIVE state.
The MM and PDP contexts in the SGSN may be deleted. The GGSN PDP contexts are deleted.
ADY STATE TIMER

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

8.2.4 THE RE
.
LLC PDU is transmitted and in the SGSN
he a
contexts return to STANDBY sta d
SGS

Onl ew
valu to he MS will immediately be forced into the
STA D (binary), then the READY timer function is
deactivated, i.e., the timer no longer runs and the MS remains in READY state.

The Ready State timer function maintains a timer of equal duration in both the MS and SGSN
This timer controls the time an MS remains in READY state in the MS and SGSN MM
ontexts. It is reset and restarted in the MS when an c
w n n LLC PDU is correctly received. When the timer expires, the MS and SGSN MM
te. The length of the READY timer is the same in the MS an
N.
y the SGSN may initiate a change to the length of the READY timer by transmitting a n
e the MS. If the timer length is set to zero, t
N BY state. If the timer length is set to all 1s


137

Set in both MS and SGSN
Reset on LLC PDU transfer
Forces MS to Standby on expiry
er disabled (MS remains in Ready state)
Timer Timer

_______________________________________________________________________________
8.3 GPRS Attach / Detach Procedures
onds to an IMSI attach used in GSM circuit switched traffic
ode and, in fact, it is possible with Type A or B GPRS handsets to carry out a dual
nce the terminal is attached to the GPRS network, the network knows its location and

Ready State Ready State
Configurable only by SGSN:
All 0s - immediately forces MS to Standby state
All 1s - tim

_

The mobile terminal (MT) makes itself known to the GPRS network by means of a GPRS
Attach request. This corresp
m
GPRS/IMSI attach for both packet and circuit switched service attachment.

O
capabilities.


138

8.3.1 THE GPRS ATTACH PROCEDURE

The GPRS Attach Procedure The GPRS Attach Procedure
BSC BSC
1
2
4
HLR HLR
MSC/ MSC/
VLR VLR
1
2
4
3
3
3
2
SGSN SGSN
BTS BTS

bove and described below, with each of the
tages identified on the diagram:

The basic GPRS attach procedure is illustrated a
s
Stage 1. The MT sends a message to the SGSN to request attachment to the network.
This request indicates the MTs multi-slot capabilities, the ciphering algorithms it
supports, and whether it wants to attach to a packet switched service, a circuit switched
service, or both.

Stage 2 . Authentication is made between the terminal and the HLR via the SGSN.

Stage 3 . Subscriber data from the HLR is inserted into the SGSN and the MSC/VLR.

Stage 4. The SGSN assigns a Packet Temporary Mobile Subscriber Identity (P-TMSI) to
the MS and informs it that it is attached to the network. This function creates a Mobility
Management (MM) Context.


139

Basic GPRS Attach Procedure Basic GPRS Attach Procedure
HLR HLR EIR EIR
SGSN SGSN BSS BSS MS MS
Attach Request Attach Request
Update Location Update Location
Attach Accept Attach Accept
Identity Request Identity Request
Identity Response Identity Response
Authentication Authentication
IMEI Check IMEI Check
Insert Subscriber Data Insert Subscriber Data
Insert Subscriber Data Insert Subscriber Data Ack Ack
Update Location Update Location Ack Ack
Attach Complete Attach Complete
MSC/VLR MSC/VLR
IMSI Attach IMSI Attach

aving successfully attached to the GPRS network and established a MM Context, the MS can
ceive paging information and can communicate with the SGSN but cannot use packet data
ontext has been established via the SGSN with a GGSN.

H
re
until a Packet Data Protocol (PDP) C
8.3.2 THE GPRS DETACH PROCEDURE

The GP The GPRS Detach Circumstances RS Detach Circumstances
S may detach from the network when:
The MS is turned off or the user manually
le Timer expires.

A GPRS M
disconnects from the GPRS network.
The MS Reachab
The SGSN forces a GPRS Detach due to radio
link problems


140

Although a GPRS Detach is normally initiated by the MS, it can also be initiated by the
etwork in certain circumstances:
al),
y be
res.
et to the Idle State and the MM context in the SGSN is deleted.
n

If the MS is switched off or the subscriber disconnects the GPRS connection (Class B termin
part of this operation is initiating a GPRS detach procedure.
If the MS loses power or moves out of coverage for an extended period, the subscriber ma
orced into Idle mode when the Reachable Timer expi f
If the SGSN is unable to communicate effectively with the MS due to a poor quality radio
path, it may initiate a GPRS detach procedure.

When a successful GPRS Detach procedure has been completed, the MM context in the MS is
s

GPRS Detach Types and Modes GPRS Detach Types and Modes
GPRS Detach Types:
IMSI Detach
GPRS Detach
Combined IMSI/GPRS Detach
GPRS Detach Modes:
Explicit MS initiated
Implicit Network initiated

The Detach function allows an MS to inform the network that it wants to make a GPRS
and/or IMSI detach, and it allows the network to inform an MS that it has been GPRS-
detached or IMSI-detached by the network. The different types of detach are:

IMSI Detach. This is a GSM detach and would normally take place if a subscriber
carried out a combined IMSI/GPRS attach and wants to clear the circuit-switched
connection (possibly with a Mode B MS). Or has previously cleared a GPRS
attachment and now wishes to clear the circuit switched attachment.

GPRS Detach. A conventional GPRS Detach.

Combined GPRS / IMSI Detach (MS-initiated only). This is a GSM detach and would

normally take place if a subscriber carried out a combined IMSI/GPRS attach and
wants to clear both connections simultaneously (Mode A MS).



141
he MS is detached from GPRS in one of two modes:
Explicit detach:
T

The network or the MS explicitly requests detach.

Implicit detach: The network (SGSN) detaches the MS, without notifying the MS, a
able timer expired, or after an
he logical link.

configuration-dependent time after the mobile reach
irrecoverable radio error causes disconnection of t

MS MS- -Initiated GPRS Detach Procedure Initiated GPRS Detach Procedure
GGSN GGSN
Detach Request Detach Request
Delete PDP Context Request Delete PDP Context Request
Delete PDP Context Response Delete PDP Context Response
Detach Accept Detach Accept

The S
Typ n
Deta
rocedu
GPRS detach, the active PDP contexts in the GGSNs regarding this particular MS are
eactivated by the SGSN sending Delete PDP Context Request (TID) to the GGSNs. The
owledge with Delete PDP Context Response (TID).
GPRS
d handles paging and location update without going via the SGSN.
e MS.

M detaches by sending Detach Request (Detach Type, Switch Off) to the SGSN. Detach
e i dicates which type of detach that is to be performed, i.e., GPRS Detach only, IMSI
ch only or combined GPRS and IMSI Detach. Switch Off indicates whether the detach
re was initiated due to a switch off situation or not. p

If
d
GGSNs ackn

If IMSI detach, the SGSN sends IMSI Detach Indication (IMSI) to the VLR.
If the MS wants to remain IMSI-attached and is doing a GPRS detach, the SGSN sends a
etach Indication (IMSI) message to the VLR. The VLR removes the association with the D
SGSN an
If Switch Off indicates that the detach procedure is not due to a switch off situation, the SGSN
sends a Detach Accept to th


142

SGSN SGSN- -Initiated GPRS Detach Procedure Initiated GPRS Detach Procedure
GGSN GGSN

e)
ously activated PDP contexts. If so, the attach procedure is
ponse (TID) messages.

s
ng via the SGSN.

The SGSN informs the MS that it has been detached by sending Detach Request (Detach Typ
to the MS. The Detach Type indicates if the MS is requested to make a new attach and PDP
context activation for the previ
initiated when the detach procedure is completed.

The active PDP contexts in the GGSNs regarding this particular MS are deactivated by the
SGSN sending Delete PDP Context Request (TID) messages to the GGSNs. The GGSNs
cknowledge with Delete PDP Context Res a
If the MS was both IMSI- and GPRS-attached, the SGSN sends a GPRS Detach Indication
(IMSI) message to the VLR. The VLR removes the association with the SGSN and handle
aging and location update without goi p

The MS sends a Detach Accept message to the SGSN any time after step 1.



143
8.3.3 THE MS REACHABLE TIMER

Mobile Reachable Timer:
Stops when MS enters READY state
Reset and restarted when MS enters STANDBY
state
Forces IDLE state on expiry (no paging)
MS Reachable Timer MS Reachable Timer

E
m
ach GPRS-enabled MS has an integral Reachable Timer. The purpose of this timer is to
onitor if the GPRS MS is still connected to the network or has detached without carrying out
e Periodic Routing Area (RA) Updates
ee Packet Routing and Transfer Section) generated by the MS.
starts when
the Reachable timer expires without having received updates, the SGSN ceases sending
ts are kept in the GGSN for a
redetermined amount of time before being purged. The timer is reset and restarted when
tivity from the MS is detected.

detach procedures and is measured by monitoring th
(s

The timer is stopped when the MS adopts the READY MM state. It resets and re
the MS adopts the STANDBY MM state.

If
paging messages to the MS. However, The MM and PDP contex
p
ac


144

________________________________________________________________________________
8.4 Routing Areas

Routing Zones Routing Zones
SGSN SGSN- -1 1
RA RA- -1 1
RA RA- -2 2
RA RA- -3 3
LA LA- -1 1
LA LA
BSC BSC- -1 1
BSC BSC- -3 3
SGSN SGSN- -2 2
CELL
CELL
CELL
CELL
CELL
CELL
CELL
CELL
LA LA- -2 2
BSC BSC- -2 2
- Routing Area RA RA
- Location Area

es three Routing Zones. These are:
Cells
Routing Areas
Location Areas

The cell is the generic coverage cell as defined within the GPRS network. Generally, GPRS
cell structures are synonymous with those of the underlying GSM cell structure, although this
may not always be the case.

The Location Area is as defined for GSM networks

The Routing Area is a new routing zone specifically for use by the GPRS network.

Each RA is uniquely identified within an LA by its Routing Area Identity.
The RAI is defined by the operator and identifies one or several cells. It is broadcast as
system information and used by the MS to determine, when changing cell, if an RA border
was crossed. If this is the case, the MS initiates the RA update procedure.
Within the network as a whole, each RA is uniquely identified by its Routing Area Code
(RAC) which comprises the Location Area Identity (LAI) plus the RAI.
The location of an MS in STANDBY state is known in the SGSN on an RA level.
Cells that do not support GPRS within an LA are grouped by the SGSN and BSS into a null
RA.

For the purposes of location management, GPRS us


145

Routing Areas Routing Areas
Served by only one SGSN
Subset of a Location Area

Cannot Span more than one Location Area
Contains one or more GPRS Cells

Cells within RAs
Area Identities Area Identities
Location Area Identity (LAI) comprises:
Mobile Country Code (MCC)
Mobile Network Code (MNC)
Location Area Code (LAC)
Location Area
Routing Area Identity (RAI) comprises:
Routing Area Code (RAC)
AI)
Location Area Identity (LAI)
Routing Areas within LA
Cell Global Identity (CGI) comprises:
Cell Identity (CI)
LAI (or R

ST re the MS is located
whe itched services by the
SGSN

A ANDBY MM State MS is paged for packet services in the RA whe
packet traffic arrives in the SGSN. The MS is paged for circuit-sw n
in the last known RA plus in the null RA.


146

The ly for the Routing Area Identity:

RAC is only unique when presented together with LAI;
The Cell Identity (CI) is only unique when presented together with LAI or RAI;
LAI = MCC + MNC + LAC;
RAI = MCC + MNC + LAC + RAC;

following rules app

Cell Global Identification (CGI) = LAI + CI.
The Periodic RA Update Timer:
Routing Area (RA) Update Timers Routing Area (RA) Update Timers
Monitors RA Update procedure in the MS
Unique for each RA
Initiates periodic RA U date procedure on expiry

on resides in the MS and the SGSN and monitors the
he
ssage.
his time set is unique within an RA. Upon expiry of the periodic RA update timer, the MS
tarts a periodic routing area update procedure.
periodic RA update timer will expire and force a
cation update to conf ttachment of the terminal.

p
Reset after periodic RA update completed
The Periodic RA Update Timer functi
periodic RA update procedure in the MS. The length of the periodic RA update timer is
determined by the network operator (typical example: 1 hour) and is sent by the SGSN to t
MS in the Routing Area Update Accept or Attach Accept me
T
s

The periodic RA Update timer is also used when a GPRS terminal remains static for an
extended period and therefore no location updates are instigated as a result of moving
through the network. In such cases, the
lo irm the continued a


147

_______________ _
8.5 Locatio

AGEMENT REQUIREMENT
__ ______________________________________________________________
n Management

8.5.1 LOCATION MAN

Location Management Requirement Location Management Requirement
Why the need for location management?
Network must know when and where a GPRS MS attaches
to the network.
Network must know where to route packets.
Network must know when a Ready State MS changes cell
and/or RA.
Network must know when a Standby State MS changes RA.
Network must know when an MS changes MM state.

GPRS, by virtue of its association with GSM, is inherently a cellular mobile communications
system. Therefore, users have the capability to move around within the coverage area
supported by the system. In order to enable this to happen, the system must maintain records
of the current location of each connected subscriber in order to be able to route traffic
correctly. Therefore the system {mobile network} must:

Be aware when users connect to and disconnect from the network.
Be aware when a mobile terminal changes is current routing area (this may be a GPRS
routing area of SGSN service area).

mobile terminal in order to route Be aware of the current location of each connected
incoming and outgoing traffic correctly


148

8.5.2 LOCATION INFORMATION STORAGE

Location Information Storage Location Information Storage
Location information stored is dependant
upon MM state of MS:
IDLE - no current location information held
STANDBY - only Routing Area information held
READY - Routing Area and cell information held

.5.2.1 Idle Mode
The method by which an MSs location is tracked depends on the Mobility Management
(MM) State of that MS:
8
from the network. The network therefore has
A GPRS attach procedure must be carried out

In the idle state, the GPRS MS is disconnected
o knowledge of the whereabouts of the MS. n
before the GPRS MS becomes active. On successful completion of the GPRS attach, the MS
changes to the READY state, where the owning SGSN has location information down to cell
level.
.5.2.2 Standby Mode 8

this mode, the SGSN knows the RA for the MS but not the specific cell. Therefore, to
ontact the MS, a packet paging signal is broadcast to all MSs in the known RA. The MS
sponds and changes to the READY state.
.5.2.3 Ready Mode
In
c
re

8
this mode, the SGSN knows the location of the GPRS MS down to cell level and therefore
acket data. In the Ready state, the MS can activate

In
paging is not required for the passage of p
nd deactivate PDP contexts a


149

8.5.3 LOCATION MANAGEMENT FUNCTIONS

Location Management Functions Location Management Functions
Functions provided:
Mechanisms for cell and PLMN selection
A mechanism to know the RA for MSs in a STANDBY
able to:
Detect entering a new cell or RA

Management function provides:

Mechanisms for cell and PLMN selection.
A mechanism for the network to know the Routing Area for MSs in STANDBY and
READY states.
A mechanism for the network to know the cell identity and Routing Area for MSs in
READY state.

The PLMN provides information for th MS to be able to:

Detect when it has entered a new cell or a new RA.
Determine when to perform periodic RA updates.

8.5.4 LOCATION UPDATE CIRCUMSTANCES
state
A mechanism to know the Cell ID for MSs in a READY
state
The Network provides the MS with information to be
Determine when to perform a RA update

The Location
e

Location updating is crucial to the successful routing of packet data across the GPRS core
network. Location updating takes plac in the following circumstances:

GPRS Attach. As has been seen above, location updating is implicit within the GPRS
attach procedure.
When a READY MM state MS changes cell, RA or SA, a routing update is
automatically initiated
When a STANDBY MM state M changes RA or SA, a routing update is automatically
initiated
When the Periodic Routing Update timer in the SGSN expires, it will force a GPRS
Detach (see section 9 for fuller descripti the RA Update Timer function)

e
S
on of


150

Location Update Circumstances Location Update Circumstances
Location updates take place when:
An MS attaches to the network
A Ready-state MS changes cell
A Ready or St ndby-state MS changes RA
A Ready or Standby-state MS changes SA
An MS periodi RA update timer expires

8.5.5 LOCATION UPDATE SCENARIOS
a
c

Location Update Scenarios Location Update Scenarios
When a GPRS terminal camps on to a new
cell, one of 3 possible scenarios is indicated:
A cell update i equired
A Routing Area date is required
A combined Routing Area and Location Area
update is requ

s r
up
ired


151

8.5.5.1 Changing Cells

Changing Cells Changing Cells
Notification only required if MS in Ready state
MS detects change y comparing stored Cell ID with
received Cell ID
Change indicates r uirement for one of three
procedures:
Cell ID update
RAI Update (inter or a-SGSN update)
Combined LAI / RA pdate

A cell-based routing update procedure is invoked when an active (Ready State) GPRS MS
enters a new cell. This is similar to the handover procedure in GSM CS scenarios. In such
cases the MS performs a Cell Update by sending a short message containing information
about its move (the message contains the MS identity and its new cell ID) through GPRS
channels to its current SGSN. This procedure is only used by MSs in a READY MM state.

8.5.5.2 Routing Area (RA) Update
b
eq
intr
I u

RA updates take place:

when a GPRS-attached MS detects that it has entered a new RA.
when the periodic RA update timer has expired.
when a suspended MS is not resumed by the BSS.


152

Changing GPRS Routing Area(RA) Changing GPRS Routing Area(RA)
Notification only required if MS in Ready or Standby
state
Update required wh n:
New RAI detected b MS
Periodic RA update er expires
MS detects change y comparing stored RAI with
received RAI
Cell ID update implicit in RA update

When an MS in a MM READY or STAN state detects that it has moved into a new RA in
the service area of the same SGSN, it m st perform a location update for traffic routing. In
this case the MS sends a short message the SGSN containing the MS identity and its new
RAI, requesting an update of the mobil y management (MM) context. The RA information in
the SGSN is updated and the success of the procedure is indicated in the response message.

8.5.5.3 Combined RA/LA Update
e
y
tim
b
DBY
u
to
it

Changing SGSN Service Area (SA) Changing SGSN Service Area (SA)
When a MS changing RA, one of two states occur:
MS has moved to new RA in same SGSN SA as old RA
MS has moved to new RA in new SGSN SA
A is in same SA, Intra-SGSN RA update is
N type

If new SA is entered, an Inter-SGSN RA update is
initiated by SGSN
If new R
initiated by MS
Periodic RA updates are always of Intra-SGS



153
inal) and
updating is
done in a co-ordinated way to save radio resources if supported by the network

e MSC/VLR. The MSC/VLR optionally returns a new VLR TMSI
that is sent to the MS via the SGSN.

Intra-SGSN Location Updates

When the GPRS terminal is both IMSI and GPRS-attached (Class A term
moves into a new RA which is also in a new LA, simultaneous RA/LA
operation mode.

When the MS enters a new RA it sends a Routing Area Update Request message to
the SGSN. The LA update is included in the RA update. The SGSN then forwards
the LA update to th

Routing Area Update Request Routing Area Update Request
MS MS
SGSN SGSN
BSS BSS
Routing Area Update Accept Routing Area Update Accept
Routing Area Update Confirm Routing Area Update Confirm
Intra Intra- -SGSN Location Updating SGSN Location Updating
Security Functions

Inter-SGSN Location Updates

RA
e
MS location.
)

When a MS changed RA and the new RA is in a new SGSN service area, in addition to an
update, an inter SGSN update must take place. This routing update is significantly more
complex than the two procedures mentioned above as a new SGSN connection must b
established. This means creating a new logical link context between the MS and the new
GSN, as well as informing the GGSN about the new S

The MS sends a Routing Area Update Request (old RAI, old P-TMSI Signature, Update Type
to the new SGSN.


154

P contexts for the MS. Provided that
the security functions in the new SGSN authenticate the MS correctly, the new SGSN sends an
ge to the

ld P-TMSI Signature, New The new SGSN sends SGSN Context Request (old RAI, TLLI, o
SGSN Address) to the old SGSN to get the MM and PD
SGSN Context Request (old RAI, TLLI, MS Validated, New SGSN Address) messa
old SGSN.
Inter Inter- -SGSN Location Updating SGSN Location Updating
MSC/VLR MSC/VLR HLR HLR GGSN GGSN Old SGSN Old SGSN New SGSN New SGSN BSS BSS MS MS
Routing Area Update Request Routing Area Update Request
SGSN Context Request SGSN Context Request
SGSN Context Response SGSN Context Response
SECURITY FUNCTIONS
SGSN Context SGSN Context Ack Ack
Forward Packets Forward Packets
Update PDP Context Request Update PDP Context Request
Update PDP Context Response Update PDP Context Response
Cancel Location Cancel Location
Cancel Location Cancel Location Ack Ack
I Insert Subscriber Data nsert Subscriber Data Ack Ack
Update Location Update Location Ac Ack k
Location Update Request Location Update Request
Routing Area Update Complete Routing Area Update Complete
Location Update Accept Location Update Accept
Routing Area Update Accept Routing Area Update Accept

The new SGSN sends an SGSN Context Acknowledge message to the old SGSN.
The old SGSN duplicates the buffered N-PDUs and starts tunnelling them to the new SGSN.

The new SGSN sends Update PDP Context Request (new SGSN Address, TID. QoS
Negotiated) to the GGSNs concerned. The GGSNs update their PDP context fields and return
Update PDP Context Response (TID).

The new SGSN informs the HLR of the change of SGSN by sending Update Location (SGSN
Number, SGSN Address, IMSI) to the HLR.

The HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with Cancellation
Type set to Update Procedure. The old SGSN acknowledges with Cancel Location Ack (IMSI).

The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new SGSN. The
new SGSN validates the MS's presence in the (new) RA. If all checks are successful, then the
SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI)
message to the HLR.

The HLR acknowledges the Update Location by sending Update Location Ack (IMSI) to the
new SGSN.

Security functions may be executed where Ciphering mode is set if supported.


155

The new SGSN validates the MS's presence in the new RA. If all checks are successful, then
the new SGSN constructs MM and PDP contexts for the MS. A logical link is established
between the new SGSN and the MS. The new SGSN responds to the MS with Routing Area
Update Accept (P-TMSI, P-TMSI Signature, Receive N-PDU Number).

The MS acknowledges the new P-TMSI by returning a Routing Area Update Complete
(Receive N-PDU Number) message to the SGSN.

________________________________________________________________________________
8.6 Paging

8.6.1 PURPOSE OF PAGING

In GPRS, paging is used to locate a GPRS terminal that is in the STANDBY MM State and f
which packet data is destined and to establish a radio resource for the connection.

8.6.2 OUTLINE PAGING PROCEDURE
or

r
pac

Fo a GPRS terminal in the MM STANDBY State, the SGSN only holds the current RA, not the
current cell. It therefore needs to determine the location of the MS down to cell level before
ket transfer can be initiated.

MS MS
SGSN SGSN BSS BSS
Paging Request Paging Request
GPRS Paging Procedure GPRS Paging Procedure
PDP PDU PDP PDU
GPRS Paging Request GPRS Paging Request
Any LLC Frame Any LLC Frame
Any LLC Frame Any LLC Frame


156

An MS in STANDBY state is paged by the SGSN before a downlink transfer to that MS. The
paging procedure changes the MSs MM state to READY to enable the MS to establish a PDP
nk packet data from the SGSN to the MS.
at moves the MM context at the SGSN to
EADY state is a valid response to paging.
he SGSN supervises the paging procedure with a Paging Response Timer. If the SGSN
receives repeats the paging when the timer
expi

he MS can also accept pages in READY state if no radio resource is assigned. This supports

ing
g
rameters:
g area in which the MS is paged.

oS
context in order to facilitate forwarding of downli
Therefore, any uplink message from the MS th
R

T
no response to its Paging Request message, it
res. This repetition strategy is vendor-specific.
T
recovery from inconsistent MM states in MS and SGSN.
The GPRS Paging procedure is illustrated above. Each step is explained in the follow
description:

The SGSN receives a downlink PDP PDU for an MS in STANDBY state. Downlink signallin
to a STANDBY state MS initiates paging as well.

The SGSN sends a BSSGP Paging Request message to the BSS serving the MS with the
following pa

IMSI - used by the BSS to identify the MSs paging group.
P-TMSI - used to identify the specific MS to be paged.
Area - indicates the routin
Channel Needed - indicates GPRS paging.
Q - QoS for the PDP context that initiates the paging procedure, and indicates the priority
f this Paging Request relative to other Paging Request messages buffered in the BSS.
RX Parameters - indicates whether the MS uses discontinuous reception or not. If the MS
ses discontinuous reception, then DRX Parameters also indicate when the MS is in a non-
leep mode able to receive paging requests.
g request (P-TMSI, Channel Needed) message in each
Channel Needed) message, the MS
sp frame)
that i
MS MM

Upon re
RAC an
a .

o
D
u
s

The BSS pages the MS with one pagin
cell belonging to the routing area.

Upon receipt of a GPRS e Paging Request (P-TMSI,
re onds with either any single valid LLC frame (e.g., a Receive Ready or Information
is nterpreted as a page response message by the SGSN. This response also changes the
state to READY.
ception of the LLC frame, the BSS adds the Cell Global Identity (CGI) including the
d LAC of the cell and sends the LLC frame to the SGSN. The SGSN then considers the
me to be an implicit paging response message and stops the paging response timer LLC fr


157

___________ _________________________________________
.7 Cell Reselection

An MS is READY or STANDBY state will participate in cell handovers using normal GSM
procedures. However, an MS in IDLE mode will carry pout the following cell selection and
ement to the
a more general
tool to make cell planning for GPRS as similar to existing planning in GSM as
possible.

_ ___________________________
8
reselection procedures:

New cell re-selection criteria, C31 and C32, are provided as a compl
corresponding GSM C1 and C2 cell re-selection criteria. C31 and C32 provide
Cell Reselection Procedures Cell Reselection Procedures
In standby or Ready states, handover procedures used
In Idle state, C31 and C32 cell reselection criteria used:
C31 Parameter - Signal strength criterion to prioritise cell selection
C32 Parameter - Improvement over C31 by applying:
individual offset and hysteresis value to each pair of cells
uses temporary offsets like C2
additional values that require routing area updates
C31, C32 are only used if PBCCH is implemented. Otherwise
the C2 criteria is used

on is used.
or cells that fulfil the C31 criterion, the cell with highest priority class is selected. If more
an one cell has the highest priority, the one of those with the highest C32 value is selected.
If no cell fulfils the C31 criterion, the cells with the highest C32 value is selected.

32 is an improvement of C2. It applies an individual offset and hysteresis value to each pair
f cells, as well as the same temporary offsets as for C2. Additional hysteresis values apply
e
cel
C2

C31 is a signal strength criterion used to decide whether prioritised cell re-selecti
F
th
C
o
for a cell re-selection that requires cell or routing area update.

C ll re-selection procedure apply to an MS attached to GPRS if a PBCCH exists in the serving
l. If the PBCCH is not allocated, then the MS performs a cell re-selection according to the
criteria.


158

Summary Summary Section Section 8 8
Mobility Management States
GPRS Attach / Detach
Routing Areas
Location Management
Location Updates
Changing Routing and Service Area
Paging
Cell Reselection


159

9. Ra
________________________________________________________________________________
9.1 Introduction
o interface between the MS
Temporary Block Flows.
agement by monitoring GPRS channels to identify congestion or

dio Resource Management

Radio resource functionality refers to the management of the radi
and the BSS. This includes the following functions:

Allocation and release of physical resources (i.e. timeslots) associated with a GPRS
channel.
Creation and management of
n Throughput ma
under-utilisation.
Initiating congestion control procedures.


160

________________________________________________________________________________
9.2 Timeslot Resource Allocation

9.2

.1 USING SPARE GSM AIR INTERFACE CAPACITY

Using Spare GSM Air Interface Capacity Using Spare GSM Air Interface Capacity
Ti
m
esl
ots
Time
Time
Available
for G
Available
for GPRS
Maximum Capacity
Circuit Switched Demand
0
PRS
24
T
i
m
e
s
l
o
t

U
s
a
g
e
Time (hours)
GPRS traffic assigned to dedicated channel
GPRS traffic dynamically assigned
T
r
a
f
f
i
c

L
e
v

r for non
ce
capacity that GPRS can make use of.

The first graph above shows the varying demand for circuit-switched services over a 24-hour
period and where GPRS packet traffic could be inserted with no increase in radio resource
requirements.

The second graph above shows the allocation of timeslots for a combined circuit/packet
switched service over a single carrier. One Timeslot (TS) is permanently assigned for packet
traffic and six can be dynamically allocated for either voice of packet data with voice having
the priority (the 8th TS being for signalling). Therefore, when packet data is to be sent, it will
be allocated a single timeslot initially (shown in red). If packet data demand exceeds the
capacity of a single TS, resources are allocated on one or more of the other 6 TSs (shown in
blue), as voice traffic loading allows.

Note that in this case the circuit-switched traffic can never exceed the 6 available timeslots.

e
l
GPRS can use available traffic capacity on the GSM network away from the busy hou
time-critical data transfers. Even during the busy hour, there may be spare air-interfa


161

9.2.2 THE PACKET DATA CHANNEL (PDCH)

The Packet Data Channel (PDCH) is a physical channel (timeslot) allocated to GPRS packet
data transfer. A PDCH can be permanently assigned to a TS or dynamically allocated as
resources become available.

Unlike GSM full-duplex circuit switched channels, GPRS channels are unidirectional in either
the uplink (PDTCH/U) or downlink (PDTCH/D).

Like GSM, GPRS channels can be assigned as either half-rate or full-rate. However, if
multiple TSs are allocated to a single GPRS user (multislot operation) channels must be full-
rate.

The Packet Data Traffic Channel The Packet Data Traffic Channel (PDCH (PDCH) )
Channel allocated for packet data transfer
Temporary or permanent allocation for one or multiple
GPRS terminals
Unidirectional in either:
Downlink (PDTCH/D)
When used for single timeslot operation can be:
Half rate (PDTCH/H)
Full Rate (PDTCH/F)

If a here
dy rce
av lability basis.

Ge erally, operators give priority to circuit-switched (CS) voice calls, as this is still the major
venue-generating GSM service. Therefore GPRS resources area allocated only when
hannels are not being used for GSM CS voice.
herefore, using dynamic allocation, when a TS is free and packet data is awaiting
ansmission, the TS is designated as a PDCH and packet transfer commences. If the TS is
quired for CS voice again, the packet data is suspended, the PDCH released and the TS
allocated for the voice call.
Uplink (PDTCH/U)
Must be full rate in multislot operation

TS is permanently allocated to GPRS, this becomes a permanent PDCH. However, w
namic allocation is used, PDCHs are created temporarily on an as-required and resou
ai
n
re
c

T
tr
re
re


162

9.2.3 TIMESLOT ALLOCATION

System Timeslot Resource Allocation System Timeslot Resource Allocation
GPRS timeslot allocation to terminals:
Up to 8 timeslots on the same carrier can be allocated to a
single GPRS terminal
Up to 8 GPRS terminals can share a single timeslot
GPRS timeslot allocation for traffic:
Timeslots specifically allocated for GPRS traffic
Allocation of spare CS timeslot capacity on a statistical basis

Operator Timeslot Resource Allocation Operator Timeslot Resource Allocation
Operators can specify the following:
GPRS capacity cell-by-cell or TRX-by-TRX
Dedicated GPRS timeslots
GPRS-capable channels that can be allocated for CS traffic
CS channels dynamically configured to carry GPRS traffic
BCCH or non-BCCH TRX preferences for GPRS



163
.2.4 LOAD SUPERVISION 9
t
ires

Uplink Timeslot Allocation

The GPRS radio interface consists of asymmetric and independent uplink and downlink
hannels. The downlink carries transmissions from the network to multiple MSs and does no c
require contention arbitration. The uplink is shared among multiple MSs and requ
contention control procedures.

Four modes of operation are supported for the purposes of uplink timeslot allocation:

Dynamic
Fixed

Dy ixed allocation methods are mandatory for current GPRS networks.

Th

Th
ED

Extended Dynamic
Exclusive
namic and f
e exclusive allocation mode is optional.
e Extended dynamic allocation mode relates to the EGPRS implementation (GPRS using
GE technology) and is beyond the scope of this course.
Uplink Timeslot Allocation Uplink Timeslot Allocation
Dynamic resource allocation - using the
USF
Fixed resource allocation
Exclusive resource allocation (optional)

Dynamic Resource Allocation. Dynamic resource allocation refers to the allocating of GPRS
packet data traffic to existing timeslots on a statistical basis where circuit-switched traffic
allows (assuming priority is given to circuit-switched traffic). Allocation is based to Uplink
State Flag (USF) assignment (see below)


164

Fixed Resource Allocation. An alternative method of sharing the timeslots is supported
which does not use the USF. In this case, the MS is sent a fixed list of timeslots and radio
blocks in each timeslot which are allocated for its use.

Exclusive Resource Allocation. Exclusive allocation is used to reserve the uplink part of the
PDCH for only one MS during the life of the TBF. Therefore, with exclusive allocation, all the
uplink blocks of the uplink part of the PDCH are available to the MS for transmission.

________________________________________________________________________________
9.3 Temporary Block Flows (TBFs)

9.3.1 TBF DESCRIPTION

Temporary Block Flow (TBF) Temporary Block Flow (TBF)
Supports uni-directional transfers of LLC PDUs on
physical channels between the MS and BSC.

ion and deactivated when no more RLC/MAC blocks are to be transmitted. It
an be established either by the MS (uplink data transfer) or the network (downlink data
ansfer). If available in the cell, the PCCCH is used for this procedure. If no PCCCH is

Allocated Radio resources on one or more PDCHs
Consists of one or more MAC/RLC blocks carrying one or
more LLC PDUs
Exists only for the duration of a specific call
Each TBF is allocated a Temporary Flow Identifier (TFI)
One MS can be assigned multiple TBFs

A Temporary Block Flow (TBF) is a physical connection between two Radio Resource (RR)
entities (e.g. the GPRS MS and the BSS) for the purpose of unidirectional transfer of LLC
PDUs on packet data physical channels. The TBF is allocated radio resources on one or more
Packet Data Channels (PDCHs) and is a session comprising a number of RLC/MAC blocks
carrying one or more LLC PDUs.

A TBF is (as the name implies) temporary as it is maintained only for the duration of the data
ransfer sess t
c
tr
available in the cell, the GSM CCCH can be used.

An MS can be allocated more than one TBF simultaneously.



9.3.2 TEMPORARY FLOW IDENTIFIER (TFI)
Each TBF is assigned a Temporary Flow Identity (TFI) by the network. The assigned TFI is
unique among concurrent TBFs in the same direction (up or down link) and is used instead of
the MS identity in the RLC/MAC layer. The same TFI value ma

y be used concurrently for
TBFs on different PDCHs in the same direction or any TBF in the opposite directions.

Temporary Flow Identifier Temporary Flow Identifier
Identifies recipient MS at RLC/MAC Layer
Assigned by network
Contained within each RLC/MAC radio block
Only unique for one PDCH in one direction
U U
m m
BTS PCU
BSS BSS
A A
GPRS GPRS
GSM RF GSM RF
TFI1
TFI1

The TFI is assigned in a resource assignment message that precedes the transfer of LLC
frames belonging to one TBF to/from the MS. The same TFI is included in every RLC header
belonging to a particular TBF as well as in the control messages associated to the LLC frame
transfer (e.g. acknowledgements) in order to address the peer RLC entities.

9.3.3 MS-INITIATED TBF ESTABLISHMENT

STEP 1
The establishment process is initiated by the MS issuing a Channel Request; message to the
network on the RACH or PRACH and entering Packet Ready mode. If no response is
received, the MS continues to send this message until a timer expires (T3146) and the access
attempt is aborted.

If unacknowledged mode has been requested, the MS requests single block packet
access and attempts a 2-phase packet access.
If the purpose of the Channel Request message is to request resources for layer 3
signalling only, the MS will request 1-phase packet access.

165


166

STEP 2
he network responds with an Immediate Assignment message, assigning a TFI, an initial
ming advance and allocates one PDCH for an uplink TBF. If insufficient resources are
allocated by the network, the MS can be forced into a 2-phase packet access procedure.
TEP 3
T
ti

S
n receipt of the network resource allocation in the Immediate Assignment message, the MS
stablishes an uplink TBF.
O
e

MS MS- -Initiated TBF Establishment Initiated TBF Establishment
Packet Channel Request Packet Channel Request
Packet Immediate Assignment Packet Immediate Assignment
Packet Resource Request Packet Resource Request
Packet Immediate Assignment Packet Immediate Assignment
PRACH or RACH PRACH or RACH
PAGCH or AGCH PAGCH or AGCH
PACCH PACCH
PACCH PACCH
Mobile Mobile BSS BSS
Phase 1 Phase 1
Phase 2 Phase 2
(optional) (optional)

9.3.4 NETWORK-INITIATED TBF ESTABLISHMENT

he purpose of a network-established TBF is to facilitate the transfer of LLC PDUs from the
etwork to the MS.

The outline procedure for establishing a network-initiated TBF is as follows:
TEP 1
T
N

S . The network-initiated TBF is started when the network receives LLC PDUs to be
rwarded to a specific MS of MS group.
TEP 2
fo

S . If the destination MS is in the STANDBY MM state, a Packet Paging Request
essage is issued to the RA of the MS.
TEP 3
m

S . The MS responds to the received paging message by sending a Packet Channel
equest message to the network.
STEP 4
R

. The network then allocates resources using a Packet Downlink Assignment
message.


167

STEP 5. Finally, the MS issues a Packet Paging Response message implicitly within the first
LLC PDU received by the network. The MS moves into READY MM mode and packet
transfer commences.

Packet Paging Request Packet Paging Request
Packet Channel Request Packet Channel Request
Packet Downlink Assignment Packet Downlink Assignment
Packet Paging Response Packet Paging Response
PPCH or PCH PPCH or PCH
PRACH or RACH PRACH or RACH
PAGCH or AGCH PAGCH or AGCH
PACCH PACCH
Mobile Mobile
BSS BSS
Network Network- -Initiated TBF Establishment Initiated TBF Establishment

.3.5 PACKET IMMEDIATE ASSIGNMENT MESSAGE 9

Packet Immediate Assignment Message Packet Immediate Assignment Message
Packet Channel Description
Frequency coding if SFH is implemented
Initial Timing Advance Value
Packet Uplink Assignment Construction
Packet Access type granted (1-phase or single block packet access)
TFI
USF value or fixed allocation bitmap
Channel coding scheme for RLC data blocks
Power Control Parameters
Optional TBF start time (mandatory if fixed allocation usedl)


168

________________________________________________________________________________
9.4 Up-Link Packet Access Procedure

9.4.1 MS PACKET ACCESS INITIATION

The uplink packet transfer procedure is triggered by a request from an upper layer to transfer
a LLC PDU.. This upper layer request specifies the radio priority and the mode
(acknowledged/unacknowledged), or indicated that the packet contains signalling rather
than user data.

The network can grant either 1-phase or 2-phase packet access:

One and Two One and Two- -Phase TBF Access Phase TBF Access
1-Phase Access:
When PCCCH is available in Cell
When in Acknowledged mode
Total data to be transmitted does not exceed 8 RLC/MAC blocks
When layer 3 signalling is requested
2-Phase Access
When PCCCH is not available in Cell
When in Unacknowledged mode
Total data to be transmitted does exceeds 8 RLC/MAC blocks

9.4.2 1-PHASE PACKET ACCESS
ne-phase access is used in the following circumstances:
When the PCCCH is available in the cell.
Automatically when in RLC acknowledged mode or the total data to be transmitted will
fit into 8 or less RLC/MAC blocks. If the total data to be transmitted will not fit into 8 or
less RLC/MAC blocks, 2-phase access can be used.

O


169

9.4.3 2-PHASE PACKET ACCESS

As the title implies, 2-phase access invo a packet access procedure that takes place in two
phases. This procedure varies depending on whether a PCCCH is available in the cell.

If the PCCCH is available, 2-phase access can be initiated by:

The network directing an MS to initiate a Packet Resource Request message
BY the mobile requesting 2-ph e access in the Packet Channel Request message. If
this access is granted, the network directs the MS to send a Packet Resource Request
message.

The first phase is the same as the 1-phase access procedure until the network sends a Packet
Uplink Assignment message with a si le block resource allocation.

Two-phase access is used in the follow g circumstances:

When the PCCCH is not available in the cell.
when in RLC unacknowledged mode, or can optionally be used if the total data to be
transmitted will not fit into 8 or less RLC/MAC blocks.

9.4.4 THE UPLINK STATE FLAG (USF)
lves
as
ng
in

Uplink State Flag (USF) Example Uplink State Flag (USF) Example
B9 B10 B11 B0 B1 B2 B3 B4 T T B5 B6 B7 B8 X X
USF = 1
USF = 2
USF = 3
User A
USF = 1
User B
USF = 2
B0 B1 B2 B3 B4 T
B5 B6 B7 B8 X
Key:


170

The Uplink State Flag (USF) is used on PDCH to allow multiplexing of Radio blocks from a
number of MSs onto a single timeslot. is transmitted only in the downlink direction but
controls allocation of uplink resources where multiple GPRS users are sharing a single
timeslot.

The USF comprises 3 bits and is contai thin the header of each downlink PDCH Radio
Block. It is used to uniquely identify up to 8 different traffic streams that can be multiplexed
onto a single uplink PDCH.

To control the dynamic multiplexing of adio blocks from different MSs, the USF signal is
transmitted on the downlink to tell eac which radio block it may use. In the initial
assignment message on PAGCH, the MS receives a list of the PDCHs each with a
corresponding USF value. The MS monitors the USF values in downlink transmission on the
assigned PDCHs. The MS may only tra smit in the radio blocks that currently have the same
USF value that was sent in the assignm

In the diagram shown above, three US , 2 or 3) have been assigned to the uplink
radio blocks.

User A was sent USF =1 (001) its PAGCH assignment message and so can only use
blocks B0 to B4.
User B was assigned USF = 2 (010) and can use blocks B5 to B8.

________________________________________________________________________________
9.5 Down-Link Packet Access Procedure

9.2.5 DOWNLINK TIMESLOT ALLOCATION
It
ned wi
r
h MS
n
ent message.
F values (1
in

The transmission of a packet to an MS in the Ready state is initiated by the network using a
packet downlink assignment message. This message includes the list of PDCH(s) that will be
used for downlink transfer. The MS may be requested to respond with a Packet Control
Acknowledgement.
w on the
ifferent MSs
e for establishing an MS-initiated TBF is as follows:

The network sends the RLC/MAC blocks belonging to one Temporary Block Flo
assigned downlink channels. Multiplexing the RLC/MAC blocks destined for d
on the same PDCH downlink is enabled with an identifier, e.g. TFI, included in each
RLC/MAC block. The interruption of data transmission to one MS is possible.

The outline procedur

STEP 1. An upper MS layer requests the transfer a LLC PDU.

STEP 2. The MS initiates a packet access procedure by sending a Packet Channel
q Re uest message to the network.

STEP 3. The network responds with a Packet Uplink Assignment message, allocating
d e form of one or more PDCHs, including the USF if dynamic
o

ra io resources in th
all cation is used.


171

STEP 4. Packet transfe

STEP 5
r is established if 1-Phase access is used.
. If 2-phase access is used the MS sends a further Packet Resource Request
message, providing a complete description of the resources required.

STEP 6. The network responds with a second Packet Uplink Assignment message,
allocating further resources if available.

9.5.1 RLC BLOCK FLOW CONTROL

RLC Block Flow Control RLC Block Flow Control
Sliding window in range 0-64
Each block contains a Block Sequence Number
assigned incrementally by the transmitter
Transmitter transmits packets in accordance with the
Acknowledge State Array V(B)
Receiver acknowledges packet receipt using the
Receive Block Bitmap (RBB) contained in the
ack/nack message.
RRB is created in receiver from the Receive State

er with a flow-control window size (WS) of 64.
RLC o
the form
SN) an itmap (RBB). It is transmitted in both acknowledged and

The Receive Block Bitmap (RBB)
Array V(N)

Flow Control at the RLC layer is achieved through the use of counters and Block Sequence
umbers (BSNs), togeth N

bl cks are transmitted by the transmitter and receipt is acknowledged by the receiver in
of a packet Ack/Nack message. This message contains a Starting Sequence Number
d a Received Block B (S
unacknowledged mode but is ignored in unacknowledged mode.

The RBB is contained within the ack/nack message and is an array of binary values, each
array element equates to a valid BSN within the WS range.


172

tmap is generated by extracting from the V(N) array those values within the range
ween V(Q) and V(R)

Block Transmission Variables
For each element in the RBB whose corresponding BSN value is within the transmit window,
the elements binary value represents:

1 = acknowledged (ACKED)
0 = not acknowledged (NACKED)

The bi
bet

To control received block flow, each RLC layer transmit entity (e.g. the MS) uses a receive
window size of 64 and a number of control variables:

Send State Variable, V(S). V(S) is set to 0 at the start of a TBF and increments each
time an RLC block is transmitted. The BSN of the block to be transmitted is assign
the current V(S) value.
ed
Acknowledge State Array V(B). V(B) is an array storing elements equating to the
window size (WS). Each time a block is transmitted, the corresponding V(B) elemen
is set to Pending Acknowledgement.
Each time a packet ack/nack message is received at the transmitter, V(B) is updated
with the contents of the RBB.
t

Block Reception Variables
To control received block flow, each RLC layer receive entity (e.g. the BSC) uses a receive
window size of 64 and a number of control variables:

Receive State Variable, V(R). V ) is set to 0 at the start of (R a TBF and stores a value
han that of the highest BSN r

one higher t eceived. Its value range is 0-127.
Receive Window State Variable, V(Q). V(Q) is set to 0 at the start of a TBF and stores
lu not yet received. When SN equal to
dow that has not
been received.
Acknowledge State Variable, V(A)
lowest BSN va e a block is received with a B
V(A), V(A) is updated with e BSN value of the next block in the win
. V ) is set to 0 at the start of a TBF and holds a
value equal to that of the oldest acknowledged BSN value. It is updates by the
Receive Block Bitmap (RBB) of the pac t acknowledgement message.
Receive State Array, (V(N)
(A
ke
. V(N) is an array storing elements equating to the
window size (WS). Each time a block is received, the corresponding V(N) element is
set to 1 (Received). When the receiver send a packet ack/nack message to the
transmitter, the RBB is populated with the contents of V(N)

For flow control purposes, if the difference between packets sent V(S) and acknowledged
packets V(A) exceeds the window size (WS) of 64, packet transmission will cease until further
acknowledgements are received.


173

________________________________________________________________________________
9.6 Radio Resource Operating Modes

Radio Resource Operating Modes Radio Resource Operating Modes
Packet Idle Mode
No TBF
Listens for paging request
Class A terminals can establish CS connections
Packet Transfer Mode
TBF established
TBF suspended on handover
Dual Transfer Mode
Simultaneous CS and PS connection

E MODE 9.6.1 PACKET IDL
idle mode no packet data flow (i.e. no TBF) exists. Upper layers can require the
er of a LLC PDU which, implicitly, may trigger packet flow and transition to packet
er mode.
s

In packet
transf
transf
In packet idle mode, the MS listens to the PBCCH and to the paging sub-channel for the
paging group the MS belongs to. If PCCCH is not present in the cell, the mobile station listen
to the BCCH and to the relevant paging sub-channels.

9.6.2 PACKET TRANSFER MODE

In packet transfer mode, the mobile station is allocated radio resource providing a TBF on one
or m e le.
Con r RLC
acknowl

or physical channels. Continuous transfer of one or more LLC PDUs is possib
cur ent TBFs may be established in opposite directions. Transfer of LLC PDUs in
edged or RLC unacknowledged mode is provided.


174

9.6.3 DUAL TRANSFER MODE

In dual transfer mode, both packet and circuit-switched connections are established
simultaneously. The MS has an ongoing circuit-switched connection and is allocated radio
resource providing a TBF on one or more physical channels for packet data transfer.
Concurrent TBFs may be established in opposite directions. Transfer of LLC PDUs in RLC
acknowledged or RLC unacknowledged mode is provided.

While in dual transfer mode the MS performs all the tasks of dedicated mode. In addition,
upper layers can require:

the release of all the packet resources, which triggers the transition to dedicated
mode.
the release of the RR resources, which triggers the transition to idle mode and packet
idle mode.

9.6.4 CELL HANDOVER DURING TRANSFER MODE

When handed over to a new cell, the MS leaves the packet/dual transfer mode, enters the
ated mode where it switches to the new cell, may read the system information messages
cket transfer mode in the new cell.

9.6.5 ESTABLISHING CIRCUIT-SWITCHED CONNECTIONS
dedic
sent on the SACCH and may then enter dual/pa

Establishing Circuit Switched Connections. In Packet Idle or transfer mode, an A class GPRS
MS may simultaneously establish a circuit-switched connection. B or C class GPRS MSs must
leaves both packet idle mode and packet transfer modes before establishing a circuit-switched
connection.


175

Summary Summary Sect Section 9 ion 9
Uplink Timeslot Allocation
Downlink Timeslot Allocation
Uplink State Flags (USFs)
Uplink/Downlink Packet Access
Temporary Block Flows (TBFs)
Radio Resource Operating Modes
Timeslot Resource Allocation


176



177

10. Pa
________________________________________________________________________________
10.1 Int

This section of the course describes the processes and protocols involved in creating a packet
Packet Data Protocol (PDP) states

cket Routing and Transfer
roduction

transfer session (PDP Context) and the routing of data packets across the GPRS Network.
Topics covered include:

The effect of mobility management states on packet transfer
PDP contexts and addresses
Access Point Names (APNs)
PDP context activation and deactivation
Packet transfer functions


178

________________________________________________________________________________

PDP state
DP
ssociated with the same MM context for the
IMSI of that subscriber.

10.2 Packet Data Protocol (PDP) Context States
Every PDP context exists independently in one of two PDP states. The
indicates whether the PDP address is activated for data transfer or not. All P
contexts for a specific subscriber are a

PDP States PDP States
ACTIVE ACTIVE INACTIVE INACTIVE
Activate PDP Context Activate PDP Context
Deactivate PDP Context Deactivate PDP Context
MM State change to IDLE MM State change to IDLE
Functional PDP
State Model
Inactive:
PDP Context not established
No packet transfer possible
Active:
PDP Context established
Packet transfer possible
Only possible in READY or STANDBY MM states

INACTIVE State
The INACTIVE state identifies the PDP context for a users particular PDP address as not
activated. The PDP context contains no routing or mapping information to process PDP
PDUs related to that PDP address and hence no data can be transferred.
The MS initiates the movement from INACTIVE to ACTIVE state by initiating the PDP
Context Activation procedure.

ACTIVE State
In the ACTIVE state, the PDP context for a specific PDP address in use is activated in MS,
SGSN and GGSN. The PDP context contains mapping and routing information for
transferring PDP PDUs for that particular PDP address between MS and GGSN.
he PDP ACTIVE state is perm T itted only when the mobility management state of the
IDLE.

subscriber is STANDBY or READY.

An active PDP context is moved to INACTIVE state when the deactivation procedure is
itiated or when the MM state changes to in


179

________________________________________________________________________________
10.3 PDP Contexts and Addresses

E PACKET DATA PROTOCOL CONTEXT 10.3.1 TH

The Packet Data Protocol (PDP) Context The Packet Data Protocol (PDP) Context
A contract set up with the GPRS network to
allow connection to external PDNs
Requires allocation of IP Address:
Static allocation
Dynamic allocation
cess point identity

Having c
established i o transfer data packets across the network.
This n rving the required external
netw

describes the characteristics of the session and contains the PDP type (e.g., IPv4),
address assigned to the mobile station (e.g. 129.187.222.10), the requested QoS, and

e mobile station is "visible" for the external PDN and is able to
This contract (context) specifies:
Protocol Type (IPv4 or IPv6)
IP Address assigned to the MS
QoS level requested
GGSN ac

atta hed to the GPRS network, a Packet Data Protocol (PDP) Context must be
n order t
co text is an association between the MS and the GGSN se
ork, via an intervening SGSN.
This context
the PDP
the address of a GGSN that serves as the access point to the PDN. This context is stored in the
MS, the SGSN, and the GGSN.
With an active PDP context, th
and receive data packets. send

10.3.2 MS PDP CONTEXT ADDRESSING
activate a PDP Context, the MS must have a packet address of the type used in the
nly one currently
lled Packet Data
address).

The PDP le
the GGS een PDN and MS. A user may have several
simu exts active at a given time.

In order to
Public Data Network (PDN). The most common address type, and the o
pported by GPRS implementations is an IP address. This address is ca su
Protocol address (PDP
address is mapped to the International Mobile Subscriber Identity (IMSI) to enab
to transfer data packets betw N
ltaneous PDP cont


180

PDP Addre PDP Address Assignment ss Assignment
ses
PDP context only.

10.3.3 PDP CONTEXT TYPES
Static IP addressing:
Permanently allocated to MS by home PLMN
Network-activated PDP contexts must address static
IP addres
Dynamic IP addressing:
Temporarily allocated to MS by PLMN for duration of
GGSN is responsible for dynamic address
assignment
Multiple IP addresses can be associated with
each IMSI (MS)

PDP Context addressing can be of two types:

Static. The Home Public Land Mobile Network (HPLMN) assigns a permanent address
to the MS and this address is used universally by that MS. This can be an address
assigned from within the PLMNs allocated pool of addresses or a global IP address.

Dynamic. A temporary address is assigned to the MS by the GGSN as part of the PDP
context activation procedure and is recovered by the GGSN when the context is
deactivated. The address is assigned from the pool of IP addresses owned by the GGSN
in the Home PLMN or the Visited PLMN, depending on circumstances.

________________________________________________________________________________
10.4 Access Point Names

can
entif
Acc

When the PDP context is established, the associated GGSN requires a means by which it
id y the external network to which the MS wishes to connect. This is achieved using an
ess Point Name (APN).


181

Access Point Names ( Access Point Names (APNs APNs) )
Identifies external PDN access point at the GGSN
3 APN selection modes:
Supplied by SGSN at PDP activation (default APN(SGSN))
Extracted from subscriber profile at HLR (APN(S))
P activation at the GGSN
APN format in two parts:
{network identifier}.{operator identifier}

ION MODES
Requested by MS at PDP activation (APN(R))
Invalid APN will reject PD
10.4.1 APN SELECT
PDP
ads this, validates it and if successful uses this requested APN (APN(R)) to
ill
sert an APN(R) and no APN(S) exists in the subscriber profile, the

There are three modes of selecting APNs:

subscribed APN selection (from user profile)
non-subscribed APN selection - sent by MS
non-subscribed APN selection - chosen by SGSN

When subscribing to a GPRS service, the subscriber profile can include an APN. When a
context is activated, the SGSN interrogates the HLR to determine if a subscribed APN is
present. If present, the SGSN uses this subscribed APN (APN(S)) it to identify the
appropriate GGSN.

The MS can request a specific APN by inserting it in the PDP context activation message.

SN re The SG
identify the required GGSN. If the requested APN is invalid, the PDP context activation w
be rejected.

S does not in If the M
subscriber profile may contain an APN wildcard. This allows the MS to access any APN for a
given PDP type (e.g. IP-Internet)

Alternatively, if none of the above exist, the SGSN can insert a default APN.


182

10.4.2 APN COMPOSITION

The Access Point Name is composed of two parts:

, to an
on, an APN Network Identifier identical to their domain name in the
public Internet. The APN Network Identifier must not end with ".gprs"
omain name
according to the DNS naming conventions, and consists of three labels, the last of
which must be ".gprs". For example, it may be:
"MNCyyyy.MCCzzzz.gprs"

The APN stored in the HLR does not contain the APN Operator Identifier. A wild card may
be stored in the HLR instead of the APN. This wild card indicates that the user may select an
APN that is not stored in the HLR.
________________________________________________________________________________
10.5 PDP Context Activation/Deactivation

APN Network Identifier. This part is mandatory and is a label (for example
"corporation") or a set of labels separated by dots which is a fully qualified domain
name according to the DNS naming conventions (for example "company.com"). In
order to guarantee the uniqueness of the APN, the GPRS PLMN should allocate
ISP or corporati

APN Operator Identifier. This part is optional. It is a fully qualified d

PDP Context Activation/Deactivation PDP Context Activation/Deactivation
Activation:
Initiated By MS
Requested by GGSN
Modification:
Decided by SGSN
Deactivation:
Initiated by MS, SGSN or GGSN


183
N PROCESS

0.5.1 MS-INITIATED PDP CONTEXT ACTIVATIO 1

SGSN SGSN
MS Initiated PDP Context Activation Process MS Initiated PDP Context Activation Process
GPRS Core GPRS Core
Network Network
MS MS BSS BSS
GGSN GGSN
Activate PDP Context Request Activate PDP Context Request
Create PDP Context Request Create PDP Context Request
Create PDP Context Response Create PDP Context Response
A Activate PDP Context Accept ctivate PDP Context Accept

The basi ure for an PDP context activation is as follows:

a pre-assigned static address. If the IP address is to be
assigned dynamically, this is left blank in the request message. The SGSN validates the
MS subscriber profile and requested connection information.
STEP 2 - Having validated the subscriber request, the SGSN uses the supplied APN to
er

STEP 3 - Having identified the external connection required, the GGSN sends a Create
PDP Context Response back to the SGSN. This message includes the IP address
(unchanged if statically allocated), confirmation of the proposed TID and the Charging ID.
STEP 4 - On receipt of a GGSN response, the SGSN finally sends a Activate PDP Context
Accept message to the MS and the PDP context is established.

c proced

STEP 1 - MS Requests Context Activation by sending an Activate PDP Context Request
message to the SGSN. This message contains the requested GGSN Access Point Name
(APN) and the IP address if

locate the IP address of the required GGSN by interrogating the Domain Name Serv
(DNS). Having located the required GGSN, the SGSN sends it a Create PDP Context
Request message. This message includes the static IP address of the MS (or blank if
dynamically assigned), the APN and a proposed Tunnelling ID (TID).


184

At this stage the following information is stored within each of the three participating
entities:

GGSN MS SGSN
PDP Type PDP Type PDP Type
PDP address PDP address PDP address
NSAPI NSAPI NSAPI
APN APN APN
IMSI IMSI
GGSN Address SGSN Address

10.5 ION .2 SECONDARY PDP CONTEXT ACTIVAT

Whe Name (APN) that
alread signed), and a

full PDP context activation procedures.
ED PDP CONTEXT ACTIVATION PROCESS
n a PDP context is activated from a source to a destination Access Point
y participating in a PDP context (i.e. already has a PDP address as is
different QoS profile is requested, a secondary PDP context is activated.

The same destination PDP address and APN are reused but a new unique NSAPI is assigned.
avoids having to carry out This

10.5.3 NETWORK-REQUEST
P PDUs are received by a GGSN from an external network, a PDP context must be
blished to forward these packets. As the GGSN is incapable of itself establishing a PDP
t must request activation from the destination MS.

When PD
esta
context, i

Network Requested PDP Context Activation Network Requested PDP Context Activation
Process Process
SGSN SGSN
MS MS
GGSN GGSN
GPRS Core GPRS Core
Network Network
Request PDP Context Activation Request PDP Context Activation
BSS BSS
PDP Notification Request PDP Notification Request
PDP Context Activation Procedure PDP Context Activation Procedure
PDP PDU PDP PDU
PDP Notification Response PDP Notification Response


185

The basic procedure for a network to request a PDP context activation is as follows:

STEP 1 - When receiving a PDP PDU the GGSN determines if the Network-Requested
PDP Context Activation procedure has to be initiated. The GGSN may store subsequent
PDP PDUs received for the same PDP address.

STEP 2 - If the SGSN address is present the GGSN sends a PDU Notification Request
(IMSI, PDP Type, PDP Address) message to the SGSN indicated by the HLR. The SGSN
returns a PDU Notification Response message to the GGSN in order to acknowledge that it
will request the MS to activate the PDP context indicated with PDP Address.

STEP 3 - The SGSN sends a Request PDP Context Activation (TI, PDP Type, PDP Address)
message to request the MS to activate the indicated PDP context.

STEP 4 - The PDP context is activated with the PDP Context Activation procedure.

10.5.4 PDP CONTEXT MODIFICATION PROCESS

An SGSN can decide, possibly triggered by the HLR using the "Insert Subscriber Data
Procedure", to modify parameters that were negotiated during an activation procedure for
of parameters by sending a Modify PDP
Context R e to the MS.

one or several PDP contexts. The following parameters can be modified:

QoS Negotiated
Radio Priority.
e modification The SGSN can request th
equest messag
PDP Context Modification Process PDP Context Modification Process
SGSN SGSN
MS MS
GGSN GGSN
GPRS Core GPRS Core
Network Network
Modify PDP Context Request Modify PDP Context Request
BSS BSS
Update PDP Context Request Update PDP Context Request
Update PDP Context Response Update PDP Context Response
Modify PDP Context Accept Modify PDP Context Accept


186

The basic procedure for modifying a PDP context is as follows:

STEP 1 - The SGSN sends an Update PDP Context Request (TID, QoS Negotiated)
message to the GGSN. If the QoS Negotiated received from the SGSN is incompatible
with the PDP context being modified (e.g., the reliability class is insufficient to support the
PDP type), then the GGSN rejects the Update PDP Context Request. The GGSN may
restrict QoS Negotiated given its capabilities and the current load. The compatible QoS
profiles are configured by the GGSN operator.

STEP 2 - The GGSN stores the QoS Negotiated and returns an Update PDP Context
Response (TID, QoS Negotiated) message.

STEP 3 - The SGSN sends a Modify PDP Context Request (TI, QoS Negotiated, Radio
Priority) message to the MS.

STEP 4 - The MS acknowledges by returning a Modify PDP Context Accept message. If
the MS does not accept the new QoS Negotiated it de-activates the PDP context with the
PDP Context Deactivation Initiated by MS procedure.

10.5.5 PDP CONTEXT DEACTIVATION CASES

The PDP context deactivation process can be performed manually or automatically depending
on the manufacturers implementation. The following deactivation cases are valid:

If the connection between the MT and TE is broken, the MT may initiate a PDP Context
Deactivation procedure.
If the radio connection is lost, the MT informs the TE.
If the TE deactivates the last PDP context, the MT may initiate a GPRS Detach procedure.

At GPRS detach, all PDP contexts associated with the MS are implicitly deactivated.

Connection at TE-MT (R reference point) broken
Radio connection lost
TE deactivates last remaining PDP context
MS initiates a deactivation procedure
Valid PDP Context Deactivation Cases Valid PDP Context Deactivation Cases


187

10.5.6 MS-INITIATED PDP CONTEXT DEACTIVATION

The PDP Context Deactivation Initiated by MS procedure is illustrated below.

SGSN SGSN
MS MS
GGSN GGSN
GPRS Core GPRS Core
Network Network
Deactivate PDP Context Request Deactivate PDP Context Request
BSS BSS
GTP Delete PDP Context Request GTP Delete PDP Context Request
GTP Delete PDP Context Response GTP Delete PDP Context Response
Deactivate PDP Context Accept Deactivate PDP Context Accept
MS PDP Context Deactivation Process MS PDP Context Deactivation Process

The basic procedure for a MS-initiated PDP context deactivation is as follows:

STEP 1 - The MS sends a Deactivate PDP Context Request message to the SGSN.

STEP 2 - The SGSN sends a Delete PDP Context Request (TID) message to the GGSN. The
GGSN removes the PDP context and returns a Delete PDP Context Response (TID)
message to the SGSN. If the MS was using a dynamic PDP address, then the GGSN
releases this PDP address and makes it available for subsequent activation by other
MSs. The Delete PDP Context messages are sent over the GPRS backbone network.

STEP 3 - The SGSN returns a Deactivate PDP Context Accept message to the MS.


188

10.5.7 SGSN-INITIATED PDP CONTEXT DEACTIVATION PROCEDURE

The PDP Context Deactivation Initiated by SGSN procedure is illustrated below

SGSN SGSN
MS MS
GGSN GGSN
GPRS Core GPRS Core
Network Network
BSS BSS
SGSN PDP Context Deactivation Process SGSN PDP Context Deactivation Process

STEP 1 - The SGSN sends a Delete PDP Context Request message to the GGSN. The
GGSN removes the PDP context and returns a Delete PDP Context Response message to
the SGSN. If the MS was using a dynamic PDP address, then the GGSN releases this PDP
address and makes it available for subsequent activation by other MSs. The Delete PDP
Context messages are sent over the GPRS backbone network. The SGSN may not wait for
the response from the GGSN before sending the Deactivate PDP Context Request message.

STEP 2 - The SGSN sends a Deactivate PDP Context Request message to the MS. The MS
removes the PDP context and returns a Deactivate PDP Context Accept message to the
SGSN.


189

10.5.8 GGSN-INITIATED PDP CONTEXT DEACTIVATION PROCEDURE

The PDP Context Deactivation Initiated by GGSN procedure is illustrated below:

SGSN SGSN
MS MS
GGSN GGSN
GPRS Core GPRS Core
Network Network
BSS BSS
GGSN PDP Context Deactivation Process GGSN PDP Context Deactivation Process

STEP 1 - The GGSN sends a Delete PDP Context Request (TID) message to the SGSN.

STEP 2 - The SGSN sends a Deactivate PDP Context Request (TI) message to the MS. The
MS removes the PDP context and returns a Deactivate PDP Context Accept (TI) message to
the SGSN.

STEP 3 - The SGSN returns a Delete PDP Context Response (TID) message to the GGSN. If
the MS was using a dynamic PDP address, the GGSN releases this PDP address and makes
it available for subsequent activation by other MSs. The Delete PDP Context messages are
sent over the GPRS backbone network. The SGSN may not wait for
the response from the MS before sending the Delete PDP Context Response message.


190

________________________________________________________________________________
10.6 Effect of MM States on Packet Transfer

Downlink:
Ready - packet download possible
Standby - Paging required
Idle - no data transfer possible
Uplink:
Ready - packet upload possible
Standby - PDP context must be established
Idle - GPRS Attach required
Effect of MM States on Packet Transfer Effect of MM States on Packet Transfer

10.6.1 DOWNLINK PACKET TRANSMISSION

Data is transmitted between an MS and the GPRS network only when the MS is in the READY
state. In this state, the SGSN knows location of the MS down to cell layer. However, in the
STANDBY state only the Routing Area (RA) of the MS known. Before an SGSN can send a
packet to a STANDBY-state MS, the MS must first be paged by sending a packet paging
message (PPM) to the RA for that MS. On receipt of the PPM, the MS forwards its cell
location to the SGSN and adopts the READY state.

Packet transmission to a READY-state MS is initiated by packet paging to notify the MS of an
incoming data packet. The data transmission proceeds immediately after packet paging
through the channel indicated by the PPM. The purpose of the PPM is primarily to simplify
the process of receiving packets, as the MS only has to listen for PPMs instead of all the data
packets in the downlink channels, thereby reducing battery life significantly.

10.6.2 UPLINK PACKET TRANSMISSION

When an MS has a packet to be transmitted, access to the uplink channel is required. This
channel is shared by a number of MSs and its use is controlled by the BSS. The MS requests
use of the channel using a packet random access message. On receipt of this message, the BSS
allocates an unused channel and sends a packet access grant message in reply to the packet
random access message. The description of the channel allocated (one or multiple timeslots)
is included in the packet access grant message. Packets are then transmitted on the reserved
channel(s).


191

The main purposes of the STANDBY mode is to reduce the load in the GPRS network caused
by cell-based routing update messages and to conserve MS battery power. When the MS is in
the standby state there is no need to inform the SGSN of every cell change, only each time the
MS changes its RA. By defining the size of the RA, the network operator can manage the
number of routing update messages.

In the IDLE state, the MS does not have a logical GPRS context activated or any PDP address
allocated. In this state the MS can receive only those multicast messages available to any
GPRS MS. Because the GPRS infrastructure does not know the cell location of the MS, it is not
possible to send messages to the MS from an external network.

________________________________________________________________________________
10.7 Packet Transfer Functions

Packet Routing and Transfer Function (1) Packet Routing and Transfer Function (1)
The packet routing and transfer function:
Transfers packets as NS-PDUs between the
Mobile TE and the GGSN external port
Transfers packets as NS-PDUs between the
Mobile TE and other PLMNs via the Gp
interface
Transfers packets as NS-PDUs between GPRS
user TEs


192

Packet Transfer Function (2) Packet Transfer Function (2)
Packet transfer between BSS and SGSN is
accomplished via SNDCP
Packet transfer between SGSN and GGSN is
accomplished using UDP/IP or TCP/IP via GTP tunnels
Network Node Relay Function:
Relay packets from incoming port to appropriate outgoing port
Stores packets until forwarded or holding time expires

Packet Transmission Connections Packet Transmission Connections
SGSN SGSN
MS MS
GGSN GGSN BSS BSS
G G
b b
G G
n n
U U
m m
PDP Context PDP Context
Logical Link Control Logical Link Control
Connection Connection
Data Link Connection Data Link Connection
IMSI/NSAPI IMSI/NSAPI
TLLI TLLI
DLCI DLCI
TID TID


193

GPRS Transmission Protocols GPRS Transmission Protocols
SGSN SGSN
MS MS
GGSN GGSN BSS BSS
G G
b b
G G
n n
U U
m m
TCP/UDP TCP/UDP
IP IP
BSSGP BSSGP
RLCP RLCP
SNDCP SNDCP
MACP MACP
Frame Relay Frame Relay

Packet Transfer Relay Functions Packet Transfer Relay Functions
Network Node Relay Function:
Relay packets from incoming port to appropriate outgoing port
Stores packets until forwarded or holding time expires
SGSN Relay Function:
Adds sequence numbers to NS-PDU received from SNDCP
May perform packet re-sequencing prior to passing to Gi

May perform packet re-sequencing prior to passing to SNDCP
layer
GGSN Relay Function:
Adds sequence numbers to NS-PDU received from the Gi
interface
Interface


194

Packet Transfer Over the Packet Transfer Over the Gb Gb Interface Interface
BSS BSS
SGSN SGSN
FR FR
Switch Switch
BSS BSS
FR FR
Switch Switch
FR FR
Switch Switch
FR FR
Switch Switch
BSS BSS
FR FR
Switch Switch
19 19
23 23
11 11
32 32
7 7
67 67
44 44
38 38
2 2
85 85
44 44 = Data Link Circuit Identifier (DLCI) = Data Link Circuit Identifier (DLCI)
77 77

GGSN GGSN- -SGSN Packet Encapsulation SGSN Packet Encapsulation
PDP PDU encapsulated by GTP
GTP encapsulated by TCP/UDP
TCP/UDP encapsulated by IP
L1 L1
User Data (e.g IP
datagram)
User Data Payload
GTP
Header
User Data Payload
GTP
Header
UDP
Header
User Data Payload
GTP
Header
UDP
Header
IP header
L2 L2
UDP/TC UDP/TC
P P
GTP GTP
IP IP
L1 L1
L2 L2
UDP/TCP UDP/TCP
GTP GTP
IP/X.25 IP/X.25
IP IP
GGSN GGSN
SGSN SGSN


195

SGSN SGSN- -MS Encapsulation MS Encapsulation
MS or SGSN PDUs encapsulated within LLC
LLC link uniquely identified by a TLLI
Each PDP context established within a TLL is
assigned a unique 4-bit NSAPI.
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Link Link
Layer Layer
MAC MAC
RLC RLC
L1 L1 bis bis
Network Network
Service Service
BSSGP BSSGP
Relay Relay
LLC LLC
SNDCP SNDCP
Network Network
Service Service
BSSGP BSSGP
MS MS
BSS BSS SGSN SGSN
U U
m m
G G
b b
L1bis L1bis


196

PDP Contexts
Context States
Addressing
Activation / Deactivation
Effects of MM States on Packet Transfer
Access Point Names (APNs)
Packet Transfer Functions
BSS BSS
SG SG
SN SN
FR Switch FR Switch
BSS BSS
FR Switch FR Switch
FR Switch FR Switch
FR Switch FR Switch
BSS BSS
FR Switch FR Switch
19 19
23 23
11 11
32 32
7 7
67 67
44 44
38 38
2 2
85 85
77 77


197

________________________________________________________________________________
11.1 Introduction

This section describes some of the operational issues involved with a GPRS network. Areas
covered include:

Bearer Services
Quality of Service (QoS)
GPRS Security
Billing Concepts


198

________________________________________________________________________________
11.2 Bearer Services

Bearer Services Bearer Services
Two Bearer Services offered:
Point-to-Point (PTP):
PTP-CNLS
PTP-CONS
Point-to-Multipoint (PTM)
PTM-M
PTM-G

The GPRS subscriber services offer end-to-end packet switched data transfer. There are two
different kinds:

PTP The Point-to-Point service offers transfer of data packets between two users. This
services is defined in GPRS Phase 1 implementation. There are two kinds of PTP services:

Connectionless mode (PTP-CNLS), for example IP networks
Connection-oriented (PTP-CONS) for example, X-25 networks.

PTM The Point-to-Multipoint service offers transfer of data packets from one user to
multiple recipients. This service is defined in GPRS Phase 2 implementation. There are two
types of PTM services:

PTM-M. In this Multicast option, packets are distributed over a specific
geographical region. A group identifier determines if the packet is for broadcast of a
specific user group.

PTM-G. In this Group option, packets are addresses to a specific group of users and
are sent to all geographical areas where members of that group are located.


199

________________________________________________________________________________
11.3 Quality of Service (QoS)

11.3.1 WHY THE NEED FOR QUALITY OF SERVICE?

GPRS Quality of Service ( GPRS Quality of Service (QoS QoS) )
Why the need for QoS?
Address customer requirements
Dynamic resource allocation
Customer confidence

One of the considerations within the GPRS network is how it should respond to a customers
requirements for a specific data rate. ETSI has stated that GPRS includes the functionality to
increase or decrease the amount of radio resources allocated to GPRS on a dynamic basis
and this is to be controlled by the network operator.

With any service which hopes to offer data transfer, prospective customers always want to
have the confidence that they are getting what they paid for and this is done reliably.
Hence, technologies have to include mechanisms by which they can monitor what is going
on, for example by the use of suitable QoS parameters.

11.3.2 QoS PARAMETERS

GPRS has a number of QoS parameters which provide users with the following QoS profiles:

Service Precedence (priority) - High/ Normal/ Low
Reliability - 3 classes in GSM 02.60, 5 classes in GSM
03.60
Delay - 4 delay classes
Throughput - max and mean bit rate or
Information Transfer Rate (ITR)


200

GPRS Quality of Service ( GPRS Quality of Service (QoS QoS) )
Service Precedence (priority)
Reliability
3 classes (GSM 02.60)
5 classes (GSM 03.60)
Delay
4 delay classes
Throughput
max and mean bit rates

11.3.3 PRECEDENCE QoS PARAMETERS

QoS QoS - - Precedence Precedence
High
Medium
Low


201

Under normal operating conditions, the network attempts to meet the service commitments
of all QoS profiles. The service precedence indicates the relative importance of maintaining
the service commitments under abnormal conditions, for example which packets are
discarded in the event of problems such as limited resources or network congestion. There
are three priority levels as specified by ETSI, namely :

High precedence: Service commitments will be maintained ahead of all other precedence
levels.

Normal precedence : This will be maintained ahead of low priority users.
Low precedence : This will be maintained after the high and normal priority
commitments have been fulfilled.

11.3.4 RELIABILITY QoS PARAMETERS

QoS QoS - - Reliability Reliability
Reliability classes define the effect of the following on
Service Data Units (SDUs):
loss of SDUs
duplication of SDUs
mis-sequencing of SDUs
corruption of SDUs
GSM release 02.60 defines 3 reliability classes
GSM release 03.60 defines 5 reliability classes

The reliability class defines the probability of :
loss of
duplication of
mis-sequencing of
corruption of Service Data Units (SDUs)

For example, if a user with an X.25 application requires the reliable delivery of X.25 packets,
it would be wrong to use a reliability class with a high loss probability. The following table
shows the specified classes.


202

GPRS uses buffers to store information along its route, GPRS is not a store and forward
service, but has delays that are dependent upon the functionality of the equipment and the
protocol being transported (TCP/IP). These stored SDUs could be discarded by GPRS if a
maximum holding timer expires.

Thus, the make up of the GPRS network and the specification of these timers could have a
direct effect on the Lost SDU probability. The corrupt SDU probability is where the SDU
could be delivered with undetected errors.

QoS QoS - - Reliability Reliability
Reliability
Class
GTP Mode LLC Frame Mode LLC Data RLC Block Mode Traffic Type
1 Acknowledged Acknowledged Protected Acknowledged
Non real-time traffic,
error-sensitive
application that cannot
cope with data loss.
2 Unacknowledged Acknowledged Protected Acknowledged
error-sensitive
application that can
cope with infrequent
data loss.
3 Unacknowledged Unacknowledged Protected Acknowledged
error-sensitive
application that can
cope with data loss,
GMM/SM, and SMS.
4 Unacknowledged Unacknowledged Protected Unacknowledged
error-sensitive
5 Unacknowledged Unacknowledged Unprotected Unacknowledged
error-sensitive

11.3.5 DELAY QoS PARAMETERS

Although GPRS is not defined as a store and forward system, it does have inherent delays
within its equipment and the supporting protocols. The amount by which SDUs may be
delayed in the network is specified as one of the four delay classes. The delays specified
include the following :

Radio channel access delay (uplink/downlink)
Radio channel transit delay (uplink/downlink)
GPRS-network delay (multiple hops)

However, this is does not include external network delays.


203

QoS QoS - - Delay Delay
GPRS defines 4 classes of delay and include the
following parameters:
Radio channel access delay (uplink/downlink)
Radio channel transit delay (uplink/downlink)
GPRS-network delay (multiple hops)
This does not include external network delays.

QoS QoS - - Delay Delay
Delay (maximum values)
SDU size : 128 octets SDU size : 1024 octets
Delay Class
Mean
Transfer
Delay (sec)
95 percentile
Delay (sec)
Mean Transfer
Delay (sec)
95 percentile
Delay (sec)
1. (Predictive) <0.5 <1.5 <2 <7
2. (Predictive) <5 <25 <15 <75
3. (Predictive) <50 <250 <75 <375
4. (Best Effort) Unspecified

Whilst the mean transfer delay is specified for the different classes, a 95-percentile delay is
also specified, which is the maximum time delay that 95-percent of SDUs will be delivered
across the interface (as opposed to specifying a time delay for 100% transmission).


204

11.3.6 THROUGHPUT QoS PARAMETERS

The throughput parameter indicates the user data throughput requested by the user.
Throughput is defined by two negotiable parameters:

Peak bit rate
Mean bit rate

QoS QoS - - Throughput Throughput
The throughput parameter indicates the user data
throughput requested by the user.
Throughput is defined by two negotiable
parameters :
Peak bit rate
Mean bit rate

11.3.6.1 Peak Throughput Bit Rate

The peak bit rate can be negotiated up to the Information Transfer Rate (ITR) value.

The peak throughput is measured at the Gi and R reference points in units of octets per
second. It specifies the maximum rate at which data is expected to be transferred across the
network for an individual PDP context. There is no guarantee that this peak rate can be
achieved or sustained for any time period, this depends upon the MS capability and
available radio resources.

The network may limit the subscriber to the negotiated peak data rate, even if additional
transmission capacity is available. The peak throughput is independent of the delay class,
which determines the per-packet GPRS network transit delay.

The peak throughput classes are defined in table below.


205

QoS QoS Peak Throughput Peak Throughput
Peak Throughput Classes Peak Throughput (octets/sec)
1 Up to 1000 (8kbps)
2 Up to 2000 (16kbps)
3 Up to 4000 (32kbps)
4 Up to 8000 (64kbps)
5 Up to 16000 (128kbps)
6 Up to 32000 (256kbps)
7 Up to 64000 (512kbps)
8 Up to 128000 (1024kbps)
9 Up to 256000 (2048kbps)

11.3.6.2 Mean Throughput Bitrate

The mean bit rate has to take into account periods where no data is transmitted, that is,
during 'bursty' transmissions. Furthermore, it should be possible for the network to re-
negotiate the throughput parameter at any time during a session.

QoS QoS Mean Throughput Mean Throughput
Mean
Throughput
Classes
Mean Throughput
(octets/hour)
1 100 (~0.22bps)
2 200 (~0.44bps)
3 500 (~1.11bps)
4 1000 (~2.2bps)
5 2000 (~4.4bps)
6 5000 (~11.1bps)
7 10000 (~22bps)
8 20000 (~44bps)
9 50000 (~111bps)
10 100000 (~0.22kbps)
11 200000 (~0.44kbps)
12 500000 (~1.11kbps)
13 1000000 (~2.2kbps)
14 2000000 (~4.4kbps)
15 5000000 (~11.1kbps)
16 10000000 (~22kbps)
17 20000000 (~44kbps)
18 50000000 (~111kbps)
31 Best Effort


206

The mean throughput is measured at the Gi and R reference points in units of octets per
hour. It specifies the average rate at which data is expected to be transferred across the GPRS
network during the remaining lifetime of an activated PDP context.
The network may limit the subscriber to the negotiated mean data rate (e.g., for flat-rate
charging), even if additional transmission capacity is available.

A "best effort" mean throughput class may be negotiated, and means that
throughput will be made available to the MS on a per need and availability basis.

The mean throughput classes are defined in the table above.

________________________________________________________________________________
11.4 GPRS Security

The security measures used by the GPRS network are similar to those used by GSM and are
as shown above. As with GSM, two cipher keys are used; Ki (subscriber authentication key)
and Kc (cipher key). However, GPRS authentication is handled by the SGSN rather than the
GSM MSC using a new, GPRS-specific, A5 encryption algorithm. The A5 algorithm is
optimised for packet data encryption.

11.4.1 PURPOSE OF GPRS SECURITY

Purposes of GSM Security include:
Protecting of user identity confidentiality
Use of temporary identities (TMSI)
Protection against unauthorised access
Authentication & service request validation
Provision of data confidentiality
Encryption (Ciphering)
Provision of network signalling confidentiality
Purposes of GPRS Security Purposes of GPRS Security

The capability to implement the above security measures is mandatory for both the MS and
the network. However, the implementation is not e.g. ciphering can be switched off. These
security measures are designed to protect data within the GSM PLMN only.
Implementation of end-to-end security of user data is not specified within the GSM
recommendation


207

11.4.2 PROTECTING USER IDENTITY CONFIDENTIALITY

Protecting User ID Confidentiality Protecting User ID Confidentiality
Benefits of user ID confidentiality include:
Ensures IMSI is not disclosed without authorisation
Prevents location tracking using air interface data
Prevents user ID from being extracted from signalling
information
Implemented using replacement Temporary Mobile
Subscriber Identity (P-TMSI)

Subscriber identity confidentiality provides for the privacy of GPRS PLMN subscribers
identities by ensuring that the IMSI is not made available or disclosed without authorisation.
This capability provides protection against location tracing mobile subscribers by listening
to the signalling exchanges on the radio path.

Protection of a subscribers IMSI is achieved through the issuing of a temporary replacement
ID. This is known as the subscribers Packet Temporary Mobile Subscriber Identity (P-TMSI
pronounced pee-tymsie).

This identity is allocated by the SGSN when a subscriber first affiliates to the network (GPRS
Attach) and may be subject to change each time the subscriber re-connects to the network or
when it moves between Routing Areas.


208

11.4.3 AUTHENTICATION

Authentication Authentication
Benefits of authentication include:
Prevents unauthorised network access
Prevents illegal impersonation of legitimate subscribers
Implemented by using an authentication procedure.
Procedure triggered by:
A change in subscriber profile data at the SGSN
Accessing a service
First network access after SGSN restart
Cipher key sequence number mismatch

Authentication is the verification that the International Mobile Subscriber identity (IMSI)
provided by the mobile subscriber within the identification procedure at the radio path, is
the one claimed. Its purpose is to protect the network against unauthorised access. It also
provides a degree of protection for GSM subscribers by preventing intruders from
impersonating authorised users.

A request for Authentication can be initiated by the MS or the network.

The authentication of the GPRS PLMN subscriber identity may be triggered by the network
when the subscriber applies for:
a change of subscriber-related information element in the SGSN or HLR including:
some or all location updating involving change of RA, registration or erasure of
a supplementary service
an access to a service including some or all mobile originating or terminated call
setups,
activation or deactivation of a supplementary service
first network access after restart of SGSN;
in the event of cipher key sequence number mismatch.

If, on an access request to the GSM PLMN, the subscriber identity authentication procedure
fails and this failure is not due to network malfunction, access to the GSM PLMN is denied
to the requesting subscriber.


209

Three items of information are required for the authentication process:

Ki Key
The Ki key is a ciphering key stored permanently only in the MS SIM and in the
subscriber profile in the AuC

RAND
The RAND is a random number generated within the AuC.

SRES
The SRES is a Signed Result code generated by in the AuC by passing the Ki and
RAND through the A3 algorithm.

The AuC, upon request from the SGSN, generates a number of security information
triplets, each comprising a RAND and an SRES and a K
c
key. This group of triplets is sent
to and stored in the SGSN associated with the MS. Each time an authorisation has been
requested, a new triplet is used.

Note: the K
c
key is generated as part of the triplet but is used for encryption rather than
authentication

If all triplets held in the SGSN have been used, the SGSN requests a new batch from the
HLR/AuC using a Send Authentication Info message. The HLR/AuC responds with this
information using a Send Authentication Info Ack message.

11.4.3.1 The Authentication Process

BSS BSS
The GPRS Authentication Process The GPRS Authentication Process
[IMSI] [IMSI]
Authentication & ciphering Request Authentication & ciphering Request
Send Authentication info Send Authentication info
MS MS SGSN SGSN AuC AuC
Send Authentication info Send Authentication info Ack Ack
IMSI, Triplets ( IMSI, Triplets (RAND,SRES,Ki RAND,SRES,Ki) )
Authentication & ciphering Response Authentication & ciphering Response
[RAND] [RAND]
[SRES] [SRES]
A3 A3
Ki Ki Ki Ki RAND RAND
= =
SRES SRES SRES SRES
MS MS
SGSN SGSN


210

The GPRS authentication process is shown in the diagram above and described below:

STEP 1 - The SGSN checks to see if it has the authentication data (Ki, RAND, SRES). If
not, it requests this from the HLR using a Send Authentication Info message. The HLR
responds with this information using a Send Authentication Info Ack message.

STEP 2 - Using the RAND (Random Number) and Ki, the SGSN generates the Signature
Response (SRES) using the A3 algorithm.

STEP 3 - The SGSN sends the RAND to the MS using an Authentication and Ciphering
Request message.

STEP 4 Using its own Ki and the RAND sent from the SGSN, the MS creates its own
SRES and sends it to the SGSN using an Authentication and Ciphering Response
message.

STEP 5 The SGSN compares its self-generated SRES with that received from the MS. If
they are identical, the user is authenticated and granted access to the network.

11.4.4 USER DATA ENCRYPTION

User Data Encryption User Data Encryption
Benefits of user data encryption include:
Provides confidentiality for user data across air interface
Selection from seven encryption algorithms
Capability is mandatory for MS and network
Implementation is optional
Does not provide for end-to-end encryption

The purpose of user data encryption is to ensure the confidentiality and privacy of user data
on physical connections by preventing its availability or disclosed to unauthorised
individuals, entities or processes.


211

Encryption will normally be applied to all voice and non-voice communications. Although a
standard algorithm (A5) will normally be employed, it is permissible for the mobile station
and/or PLMN infrastructure to support more than one algorithm. In this case, the
infrastructure is responsible for deciding which algorithm to use (including the possibility
not to use encryption, in which case confidentiality is not applied).

When encryption is requested, the MS signals to the network indicating which of up to
seven ciphering algorithms it supports . The serving network then selects one of these and
signals this to the MS. The selected algorithm is then used by the MS and network.

Data encryption (ciphering) takes place in the LLC layer. Whereas with GSM, encryption
takes place between the MS and the BSS, GPRS encryption takes place between the MS and
the SGSN.

As with GSM, the A8 algorithm generates an Kc key based on Ki and RAND. This is fed
into the A5 algorithm at the SGSN and the MS and mixed with clear data to produce
encrypted data.

Encrypted data transfer takes place as soon as the Authentication and Ciphering Response
message has been sent and received by the SGSN and MS respectively.
Note that the Kc key described above is GPRS-specific, it is not the same Kc key as is used
for circuit-switched data. Therefore, an MS may have more than one Kc key.

11.4.4.1 Ciphering Key Sequence Number (CKSN)

In order to allow ciphering to commence on a LLC connection without authentication (for
example after an MSC failure) ciphering key sequence numbers are used. The sequence
number is managed by the network in the way that the AUTHENTICATION REQUEST
message contains the sequence number allocated to the key which may be computed from
the RAND parameter carried in that message.

The MS stores this number with the key, and indicates to the network in the first message
(LOCATION UPDATING REQUEST, CM SERVICE REQUEST, PAGING RESPONSE, CM
REESTABLISHMENT REQUEST) which sequence number the stored key has. When the
deletion of the sequence number is described this also means that the associated key is
considered as invalid.

In certain circumstances, the network can start ciphering with the stored key if the CKSN
associated with that key is the same as CKSN stored with the key in the MS.


212

11.4.4.2 General Encryption Procedure

The GPRS Encryption Process The GPRS Encryption Process
A8 A8
Ki Ki Ki Ki
RAND RAND
Kc Kc Kc Kc
MS MS
SGSN SGSN
A5
A5
Data Data
Data Data
Kc Kc + Data + Data

STEP 1 Determining the A5 Algorithm
Assuming authentication has already taken place, when an MS wishes to establish an
encrypted connection to the network, the A5 algorithm is first negotiated on the DCCH
(PACCH) channel in accordance with the following priorities:

1. If the MS and the network have no common versions of the A5 algorithm and the
network and/or MS is not prepared to use an unencrypted connection, then the
connection is released.
2. If the MS and the network have at least one version of the A5 algorithm in common,
then the network selects one of the mutually acceptable versions for use on that
connection.
3. If the MS and the network have no common versions of the A5 algorithm and the
network is willing to use an unencrypted connection, then an unencrypted
connection is established.

STEP 2 Kc Key Generation
Using the Ki key, unique to each MS, and the RAND generated by the AuC, the Kc is
generated at both the MS and AuC. The AuC Kc key is passed to the SGSN along with the
RAND and SRES as part of each Triplet.

STEP 3 Transition to Cipher Mode
Encrypted data is produced by passing the Kc key and the clear user data through the A5
algorithm, stored in both the MS and BSS. The transition from clear mode to ciphered mode
proceeds as follows:

Once this message has been received correctly, both the enciphering and
deciphering start on the MS side.


213

Enciphering on the MS side starts as soon as synchronisation has been achieved and
an encrypted MS-generated frame or a message has been correctly deciphered at the
SGSN

When a PTCH is allocated for user data transmission, the key used for PTCH encryption is
the one set during the preceding DCCH (PACCH) session. The enciphering and deciphering
processes start immediately.

11.4.4.3 Handover Requirements

When a handover occurs, the necessary information (e.g. key Kc, initialisation data) is
transmitted within the system infrastructure to enable the communication to proceed from
the old SGSN to the new one, and the Synchronisation procedure is resumed. The key Kc
remains unchanged at handover.

11.4.5 SIGNALLING DATA ENCRYPTION

Signalling Data Encryption Signalling Data Encryption
Signalling data encryption provides confidentiality for
user identities across air interface
Applied to selected fields of signalling messages
including:
International Mobile Equipment Identity (IMEI)
International Mobile Subscriber Identity (IMSI)
Calling subscriber directory number (mobile terminating calls)
Called subscriber directory number (mobile originated calls)
These fields are not protected on initial connection
Does not provide for end-to-end encryption

The purpose of signalling data encryption is to ensure the confidentiality of user-related
signalling data which is exchanged between MSs and SGSN by preventing its availability or
disclosed to unauthorised individuals, entities or processes.

When used, this feature applies on selected fields of signalling messages which are
exchanged between MSs and SGSN.


214

The following signalling information elements related to the user are protected whenever
used after initial connection establishment:

International Mobile Equipment Identity (IMEI).
International Mobile Subscriber Identity (IMSI).
Calling subscriber directory number (mobile terminating calls).
Called subscriber directory number (mobile originated calls).

Note that on initial connection establishment, the signalling information elements (protocol
discriminator, connection reference, message type and MS identities IMSI, P-TMSI or IMEI)
are not protected.

________________________________________________________________________________
11.5 Billing

11.5.1 GPRS BILLING INFORMATION

Charging for GPRS Services Charging for GPRS Services
GSNs collects GPRS-related billing data
such as:
destination and source address
usage of radio interface
usage of external PDNs
usage of PDP addresses
usage of general GPRS resources
location of mobile station
volume of packet traffic
Internet


215

The GPRS specifications stipulate the minimum charging information that must be collected
in the Phase 1 service description. These include:

destination and source addresses
usage of radio interface
usage of external Packet Data Networks
usage of the packet data protocol addresses
usage of general GPRS resources
location of the Mobile Station.
volume of packets sent and received

Current billing techniques can only handle charging for circuit-switched services (plus SMS)
and therefore new billing methods must be introduced to cope with packet data transfers.

GPRS call records are generated in the GPRS Support Nodes. The GGSN and SGSN may not
be able to store charging information but this charging information needs to be processed.
Therefore a Charging Gateway is introduced with the specific purpose of collecting and
processing billing information in the form of Call Detail Records for onward transmission to
billing systems.

11.5.2 CHARGING FOR GPRS SERVICES

y well be the case that the cost of measuring packets is greater than their value. The
ation is that there will NOT be a per packet charge since there may be too many
packets to warrant counting and charging for. For example, a single traffic monitoring
pplication can generate tens of thousands of packets per day. Thus the Charging Gateway
function is more a policing function than a charging function since network operators are
likely to tariff certain amounts of GPRS traffic at a flat rate and then need to monitor
whether these allocations are exceeded.

It ma
implic
a
Charging for GPRS Services Charging for GPRS Services
GPRS allows the user to be always connected
Some possible methods of charging are:
By volume of data transferred
Flat rate for Internet access
Time spent on-line
By Transaction
For content - operator may provide own
pages (value added services)
These charging methods can be modified by:
Enhanced quality of service
Enhanced security
Internet


216

There are a number of parameters against which charges can be raised. It is likely that any
implemented billing scheme will be based on a combination of these parameters:

Volume: This can be measured in number of packets sent/received or the amount of
data in Kbytes.
Flat Rate: This is similar to the business model used for fixed-line ISPs. Subscribers pay
a fixed fee and then have unrestricted access to the service. Such a service would benefit
heavy users rather than those with occasional access requirements.

Time: Subscribers could be billed for the amount of time spent connected to the GPRS
service, regardless of traffic volume. However, this concept may be difficult to
implement due the always on-line concept of GPRS.

Transaction: For Internet access, ISP functions and services provide their own
accounting data. It is likely that this will be transaction-based (price per response, price
per piece of information for example.

Content. Billing by access to value-added services such as specific internet sites or
downloads such as sports results etc.

he chosen billing tariff will be modified by additional user requirements such as enhanced
ecurity or specific quality of service requirements.

T
s

In order to broaden consumer base appeal, it is likely that a number of tariffs will become
available to suit different usage models.
11.5.3 EXAMPLES OF EXISTING GPRS TARIFFS

UK GPRS Service Provider Tariffs UK GPRS Service Provider Tariffs
Vodafone UK:
GPRS: No monthly access charge. 2p for every 1KB sent or received.
GPRS 1: 7.49 monthly access charge including 1MB of information.
0.5p for every additional 1KB sent or received.
BT Cellnet:
Pay As You Use: 3.99 monthly access charge. 2p for every 1KB sent
or received.
Value Bundle: 7.99 monthly access charge including 1MB of
information. 0.39p for every additional 1KB sent or received.


217

Summary Summary Section Section 11 11
Subscriber Services
PTP, PTM
Quality of Service
Precedence, Reliability, Delay, Throughput,
Parameters, Methods, Existing Tariffs.
Security
Authentication, Encryption, User ID Confidentiality
Billing MS MS
A8 A8
Ki Ki Ki Ki RAND RAND
Kc Kc Kc Kc
SGSN SGSN
A5 A5
Data Data Data Data
Kc Kc + Data + Data


218


12. Interaction With GSM Services

219

12. Interaction with GSM Services
________________________________________________________________________________
12.1 Introduction

his section of the course looks at some of the areas when GSM and GPRS services interact.

T
These areas include:

Interactions between SGSN and MSC/VLR
Network Operating Modes
Combined IMSI/GPRS Attach and Detach
Combined Location Updating
Paging Coordination


220

________________________________________________________________________________
12.2 Interactions Between SGSN and MSC/VLR

Interaction between the MSC/VLR and SGSN only apply if the optional Gs interface is
stalled. When the Gs interface is present, an association is created between SGSN and
SC/VLR to provide for interactions between the two entities. The association is created
when the VLR stores the SGSN number and the SGSN stores the VLR number. This
association is used for co-ordinating MSs that are both GPRS-attached and IMSI-attached
and supports the following:

IMSI attach and detach via SGSN. This makes combined GPRS / IMSI attach and
combined GPRS / IMSI detach possible, thus saving radio resources.
Co-ordination of LA update and RA update, including periodic updates, thus saving
radio resources. A combined RA / LA update is sent from the MS to the SGSN.
SGSN forwards the LA update to the VLR.
Paging for a CS connection via the SGSN.
Alert procedures for non-GPRS services.
Identification procedure.
MM Information procedure.

in
M
SGSN SGSN- -MSC/VLR Supported Functions MSC/VLR Supported Functions
Combined IMSI/GPRS attach
Coordinated / combined RA / LA updating
Coordinated paging for CS/GPRS connections
Alert procedures for non-GPRS services.
Identification procedure
MM Information procedure


221

________________________________________________________________________________
12.3 Network Operating Modes

Implementation of the Gs Interface depends on the network operation mode implemented.

12.3.1 NETWORK OPERATING MODE

Network Operating Mode I Network Operating Mode I
BSS
MSC/
VLR
SGSN
Gs
Combined LA/RA Update
Combined paging
Longer MS sleep periods
Smaller Paging Load (MS
only paged in RA)
A
Gb

12.3.2 THE MSC-SGSN Gs INTERFACE

When the Gs interface is present, all MSC-originated paging of GPRS-attached MSs goes via
the SGSN, thus allowing network co-ordination of paging. Paging co-ordination is
controlled by the SGSN based on the IMSI, and is provided independently of whether the
MS is in STANDBY or in READY state. This network operation mode I.


222

The Gs Interface The Gs Interface
Interface between MSC/VLR and SGSN
Optional implementation
When present:
All MSC-originated paging of GPRS-attached MSs is via
the SGSN
Paging coordination possible
When absent:
All MSC-originated paging of GPRS-attached MSs is via
the A interface
Paging coordination not possible

12.3.3 NETWORK OPERATING MODE II AND III OPERATION

Network Operating Modes II & III Network Operating Modes II & III
BSC
MSC/
VLR
SGSN
Separate LA and RA updates
Two types of paging channels
to be monitored
MS paged in LA
Mode II - PPCH not available in
cell
Mode III - PPCH available in
cell
Gb
A


223

When the Gs interface is not present, all MSC-originated paging of GPRS-attached MSs go
via the A interface and co-ordination of paging cannot be performed. The network will then
either:

operate in mode II, meaning that the packet common control channel has not been
allocated in the cell
operate in mode III, meaning that the packet common control channel is to be used
for GPRS paging when the packet paging channel is allocated in the cell.

The network operation mode (mode I, II, or III) is indicated as system information to MSs.
For proper operation, the mode of operation should be the same in each cell of a routing area
(RA).

________________________________________________________________________________
12.4 Combined IMSI / GPRS Attach and Detach

A GPRS attach is made to the SGSN. A GPRS-attached MS makes IMSI attach via the SGSN
with the combined RA / LA update procedure if the network operation mode is I. In
network operation modes II and III, or if the MS is not GPRS-attached, then the MS makes
IMSI attach as already defined in GSM. An IMSI-attached MS in class-A mode of operation
engaged in a CS connection uses the (non-combined) GPRS Attach procedure when it
performs a GPRS attach.

Combined IMSI/GPRS Attach/Detach Combined IMSI/GPRS Attach/Detach
Simultaneous connection to both CS and PS
services.
Simultaneous disconnection from both CS and PS
services
Only possible with Class A and B GPRS terminals
(class C terminals must IMSI detach before GPRS
attach)


224

12.4.1 COMBINED IMSI/GPRS ATTACH PROCEDURE

In the attach procedure, the MS provides its identity and an indication of which type of
attach that is to be executed. The identity provided to the network is the MS's Packet TMSI
(P-TMSI) or IMSI. P-TMSI and the RAI associated with the P-TMSI are provided if the MS
has a valid P-TMSI. If the MS does not have a valid P-TMSI then the MS provides its own
IMSI.

An IMSI-attached MS that can only operate in class-C mode of operation must follow the
normal IMSI detach procedure before it makes a GPRS attach.

The Combined GPRS / IMSI Attach procedure is illustrated below:

Combined IMSI/GPRS Attach Procedure Combined IMSI/GPRS Attach Procedure
old old
MSC/VLR MSC/VLR
HLR HLR Old SGSN Old SGSN New SGSN New SGSN MS MS
Attach Request Attach Request
Identification Request Identification Request
Identification R n Response Identificatio esponse
ID Request ID Request
new new
MSC/VLR MSC/VLR
ID Response ID Response
Insert Sub Data Insert Sub Data
Insert Sub Data Insert Sub Data Ack Ack
Attach Accept Attach Accept
Attach Complete Attach Complete
TMSI Reallocation Complete TMSI Reallocation Complete
SECURITY FUNCTIONS

The procedure for carrying out a combined IMSI/GPRS attach is described below:

STEP 1 - The MS initiates the attach procedure by the transmission of an Attach Request
message (IMSI or P-TMSI and old RAI, Classmark, CKSN, Attach Type, DRX Parameters,
old P-TMSI Signature) to the SGSN. The IMSI is included if the MS does not have a valid P-
TMSI available. If the MS has a valid P-TMSI, then P-TMSI and the old RAI associated with
P-TMSI will be included. Classmark contains the MS's GPRS multislot capabilities and
supported GPRS ciphering algorithms in addition to the existing classmark parameters.


225

Attach Type indicates which type of attach that is to be performed, i.e., GPRS attach only,
GPRS Attach while already IMSI attached, or combined GPRS / IMSI attach. DRX
Parameters indicates whether the MS uses discontinuous reception or not. If the MS uses
discontinuous reception, then DRX Parameters also indicate when the MS is in a non-sleep
mode able to receive paging requests and channel assignments. If the MS uses P-TMSI
for identifying itself and if it has also stored its old P-TMSI Signature, then the MS will
include the old P-TMSI Signature in the Attach Request message.

STEP 2 - If the MS identifies itself with P-TMSI and the SGSN has changed since detach, the
new SGSN sends an Identification Request (P-TMSI, old RAI, old P-TMSI Signature) to the
old SGSN to request the IMSI. The old SGSN responds with Identification Response (IMSI,
Authentication Triplets). If the MS is not known in the old SGSN, the old SGSN responds
with an appropriate error cause. The old SGSN also validates the old P-TMSI
Signature and responds with an appropriate error cause if it does not match the value stored
in the old SGSN.

STEP 3 - If the MS is unknown in both the old and new SGSN, the SGSN sends an Identity
Request (Identity Type = IMSI) to the MS. The MS responds with Identity Response (IMSI).

STEP 4 Security procedures may be carried out including authentication (if no MM context
for the MS exists anywhere in the network authentication is mandatory), ciphering
procedures and optional IMEI checks with the EIR.

STEP 5 - If the SGSN number has changed since the GPRS detach, or if it is the very first
attach, then the SGSN informs the HLR by sending an Update Location (SGSN Number,
SGSN Address, IMSI) to the HLR. The HLR sends Cancel Location (IMSI, Cancellation
Type) to the old SGSN with Cancellation Type set to Update Procedure and the old SGSN
acknowledges with Cancel Location Ack (IMSI). The HLR sends Insert Subscriber Data
(IMSI, GPRS subscription data) to the new SGSN and the new SGSN validates the MS's
presence in the (new) RA. The HL acknowledges the Update Location message by sending
an Update Location Ack to the SGSN after the cancelling of old MM context and insertion of
new MM context are finished.

STEP 6 - If initiating a GPRS Attach while already IMSI attached, or initiating a combined
GPRS / IMSI attach, the VLR is up ted if the Gs interface is installed. The VLR number is
derived from the RA information.

STEP 7 - The SGSN starts the location update procedure towards the new MSC/VLR upon
receipt of the first Insert Subscriber Data message from the HLR. This operation marks the
MS as GPRS-attached in the VLR:

The SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number,
Location Update Type) message to the VLR. Location Update Type will indicate
IMSI attach if Attach Type indicated combined GPRS / IMSI attach. Otherwise,
Location Update Type will indicate normal location update. The VLR creates an
association with the SGSN by storing SGSN Number.
If the LA update is inter-MSC, the new VLR sends Update Location (IMSI, new
VLR) to the HLR.
If the LA update is inter-MSC, the HLR sends a Cancel Location (IMSI) to the old
VLR.
The old VLR acknowledges with Cancel Location Ack (IMSI).
If the LA update is inter-MSC, the HLR sends Insert Subscriber Data (IMSI, GSM
subscriber data) to the new VLR.
The VLR acknowledges with Insert Subscriber Data Ack (IMSI).
R
da


226

After finishing the inter-MSC location update procedures, the HLR responds with
Update Location Ack (IMSI) to the new VLR.
The VLR responds with Location Update Accept (VLR TMSI) to the SGSN.

STEP 8 - The SGSN selects Radio Priority SMS, and sends an Attach Accept (P-TMSI, VLR
TMSI, P-TMSI Signature, Radio Priority SMS) message to the MS. P-TMSI is included if the
SGSN allocates a new P-TMSI.

STEP 9 - If P-TMSI or VLR TMSI was changed, the MS acknowledges the received TMSI(s)
by returning an Attach Complete message to the SGSN.

STEP 10 - If VLR TMSI was changed, the SGSN confirms the VLR TMSI re-allocation by
sending a TMSI Reallocation Complete message to the VLR.

The Combined IMSI/GPRS detach procedure is similar to the normal GPRS detach
procedure, other than that interaction with the MSC/VLR takes place:

12.4.2 COMBINED IMSI/GPRS DETACH PROCEDURE

MSC/VLR MSC/VLR
GGSN GGSN
IMSI Detach Indication IMSI Detach Indication
GPRS Detach Indication GPRS Detach Indication
Combined IMSI/GPRS Detach Procedure Combined IMSI/GPRS Detach Procedure

A combined IMSI / GPRS Detach procedure can only be initiated by an MS. The procedure is
as follows:

STEP 1 - The MS detaches by sending Detach Request (Switch Off, Detach Type) to the
SGSN. Switch Off indicates whether the detach is due to a switch off situation or not.
Detach Type indicates which type of detach is to be performed i.e.

GPRS Detach Only
IMSI detach only
Combined IMSI/GPRS detach


227

STEP 2 For the GPRS detach part, the active PDP contexts in the GGSNs related to this
particular MS are deactivated by the SGSN sending a Delete PDP Context Request message
to the appropriate GGSN(s). The GGSN(s) acknowledge with Delete PDP Context
Response.

STEP 3 For the IMSI detach part, the SGSN sends IMSI Detach Indication (IMSI) to the
MSC/VLR.

STEP 4 - If the MS is carrying out a GPRS detach but wished to remain IMSI-attached, the
SGSN sends a GPRS Detach Indication (IMSI) message to the MSC/VLR in order to remove
the association with the SGSN such that all future paging and location updating will via the
MSC rather than the SGSN.

STEP 5 - If Switch Off indicates that the detach is not due to a switch off situation, the SGSN
sends a Detach Accept to the MS.

________________________________________________________________________________
12.5 Combined Location Updating

A combined RA / LA update takes place in network operation mode I when a GPRS/IMSI
attached MS enters a new RA or when a GPRS-attached MS performs IMSI attach. The MS
sends a RA Update Request indicating that an LA update may also need to be performed, in
which case the SGSN forwards the LA update to the VLR.

The procedures for Combined RA/LA Location updating vary dependant upon whether the
location change involves a change of host SGSN. The procedures for Inter- and Intra-SGSN
RA/LA updating are described below

12.5.1 COMBINED INTRA-SGSN RA/LA UPDATING

Combined Intra Combined Intra- -SGSN RA/LA Update SGSN RA/LA Update
old old
MSC/VLR MSC/VLR
HLR HLR
SGSN SGSN MS MS
RA Update Request RA Update Request
new new
MSC/VLR MSC/VLR
RA Update Accept RA Update Accept
RA Update Complete RA Update Complete
SECURITY FUNCTIONS


228

STEP 1 - The MS sends a RA Update Request (old RAI, old P-TMSI Signature, Update Type)
to the SGSN. Update Type to indicate a combined RA / LA update, or, if the MS wants to
perform an IMSI attach, combined RA / LA update with IMSI attach requested. The BSS
adds the Cell Global Identity including the RAC and LAC of the cell where the message was
received before passing the message to the SGSN.

STEP 2 - Security functions may be executed.

STEP 3 - If the association has to be established, if Update Type indicates combined RA /
LA update with IMSI attach requested, or if the LA changed with the routing area update
the SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number, Location
Update Type) to the VLR. Location Update Type indicates IMSI attach if Update Type in
step 1 indicated combined RA / LA update with IMSI attach requested. Otherwise,
Location Update Type indicates normal location update. The VLR number is translated
from the RAI via a table in the SGSN. The VLR creates or updates the association with the
SGSN by storing SGSN Number.

STEP 4 - If the subscriber data in the VLR is marked as not confirmed by the HLR, then the
new VLR informs the HLR. The HLR cancels the data in the old VLR and inserts subscriber
data in the new VLR. The new VLR allocates a new VLR TMSI and responds with Location
Update Accept (VLR TMSI) to the SGSN. VLR TMSI is optional if the VLR has not changed.

STEP 5 -The SGSN validates the MS's presence in the new RA. If due to regional
subscription restrictions the MS is not allowed to be attached in the RA, or if subscription
checking fails, then the SGSN rejects the RA update with an appropriate cause. If all checks
are successful then the SGSN updates the MM context for the MS. A new P-TMSI may be
allocated. The SGSN responds to the MS with RA Update Accept (P-TMSI, VLR TMSI, P-
TMSI Signature).

STEP 6 - If a new P-TMSI or VLR TMSI was received, then the MS confirms the reallocation
of the TMSI by returning a RA Update Complete message to the SGSN.

STEP 7 - The SGSN sends a TMSI Reallocation Complete message to the VLR if the VLR
TMSI is confirmed by the MS. If the RA update procedure fails a maximum allowable
number of times, or if the SGSN returns a RA Update Reject message, the MS enters IDLE
state. If the Location Update Accept message indicates a reject, then this should be indicated
to the MS, and the MS will not access non-GPRS services until a successful Location Update
is performed.



12.5.2 COMBINED INTER-SGSN RA/LA UPDATING

Combined Inter Combined Inter- -SGSN R SGSN RA/LA Update A/LA Update
old old
MSC/VLR MSC/VLR
HLR HLR
Old SGSN Old SGSN New SGSN New SGSN MS MS
RA Update Request RA Update Request
SGSN Context request SGSN Context request
SGSN Context Response SGSN Context Response
Update PDP Contexts Request Update PDP Contexts Request
ID Request ID Request
new new
MSC/VLR MSC/VLR
RA Update Accept RA Update Accept
RA Update Complete RA Update Complete
SECURITY FUNCTIONS
SGSN Context SGSN Context Ack Ack
Forward Packets Forward Packets
GGSN GGSN
ID Response ID Response
Update PDP Contexts Response Update PDP Contexts Response

STEP 1 - The MS sends a RA Update Request (old RAI, old P-TMSI Signature, Update Type)
to the new SGSN. Update Type indicating a combined RA / LA update, or, if the MS wants
to perform an IMSI attach, combined RA / LA update with IMSI attach requested. The BSS
adds the Cell Global Identity including the RAC and LAC of the cell where the message was
received before passing the message to the SGSN.

STEP 2 - The new SGSN sends SGSN Context Request (old RAI, TLLI, old P-TMSI Signature,
New SGSN Address) to the old SGSN to get the MM and PDP contexts for the MS. The old
SGSN validates the old P-TMSI Signature and responds with an appropriate error cause if it
does not match the value stored in the old SGSN. This should initiate the security functions
in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN
sends an SGSN Context Request (old RAI, TLLI, MS Validated, New SGSN Address)
message to the old SGSN. MS Validated indicates that the new SGSN has authenticated the
MS. If the old P-TMSI Signature was valid or if the new SGSN indicates that it has
authenticated the MS, the old SGSN stops assigning SNDCP N-PDU numbers to downlink
N-PDUs received, and responds with SGSN Context Response (MM Context, PDP Contexts).
If the MS is not known in the old SGSN, the old SGSN responds with an appropriate error
cause. The old SGSN stores New SGSN Address until the old MM context is cancelled, to
allow the old SGSN to forward data packets to the new SGSN. Each PDP Context includes
the SNDCP Send N-PDU Number for the next downlink N-PDU to be sent in acknowledged
mode to the MS, the SNDCP Receive N-PDU Number for the next uplink N-PDU to be
received in acknowledged mode from the MS, the GTP sequence number for the next
downlink N-PDU to be sent to the MS and the GTP sequence number for the next uplink N-
PDU to be tunnelled to the GGSN. The old SGSN starts a timer and stops the downlink
transfer.

229

230

STEP 3 - Security functions may be executed. Ciphering mode is set if ciphering is
supported. If the security functions fail (e.g. because the SGSN cannot determine the HLR
address to establish the Send Authentication Info dialogue), the Inter SGSN RAU Update
procedure fails. A reject is returned to the MS with an appropriate cause.

STEP 4 - The new SGSN sends an SGSN Context Acknowledge message to the old SGSN.
This informs the old SGSN that the new SGSN is ready to receive data packets belonging to
the activated PDP contexts. The old SGSN marks in its context that the MSC/VLR
association and the information in the GGSNs and the HLR are invalid. This triggers the
MSC/VLR, the GGSNs, and the HLR to be updated if the MS initiates a RA update
procedure back to the old SGSN before completing the ongoing RA update procedure. If the
security functions do not authenticate the MS correctly, then the RA update is rejected, and
the new SGSN sends a reject indication to the old SGSN. The old SGSN continues as if the
SGSN Context Request was never received.

STEP 5 - The old SGSN duplicates the buffered N-PDUs and starts tunnelling them to the
new SGSN. Additional N-PDUs received from the GGSN before the timer described in step 2
expires are also duplicated and tunnelled to the new SGSN. N-PDUs that were already sent
to the MS in acknowledged mode and that are not yet acknowledged by the MS are
tunnelled together with the SNDCP N-PDU number. No N-PDUs are forwarded to the new
SGSN after expiry of the timer described in step 2.

STEP 6 - The new SGSN sends Update PDP Context Request (new SGSN Address, TID, QoS
Negotiated) to the GGSNs concerned. The GGSNs update their PDP context fields and
return an Update PDP Context Response.

STEP 7 - The new SGSN informs the HLR of the change of SGSN by sending Update
Location (SGSN Number, SGSN Address, IMSI) to the HLR.

STEP 8 - The HLR sends Cancel Location (IMSI, Cancellation Type) to the old SGSN with
Cancellation Type set to Update Procedure. If the timer described in step 2 is not running,
then the old SGSN removes the MM and PDP contexts. Otherwise, the contexts are removed
only when the timer expires. This allows the old SGSN to complete the forwarding of N-
PDUs. It also ensures that the MM and PDP contexts are kept in the old SGSN in case the MS
initiates another inter SGSN RA update before completing the ongoing RA update to the
new SGSN. The old SGSN acknowledges with Cancel Location Ack (IMSI).

STEP 9 - The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data) to the new
SGSN. The new SGSN validates the MS's presence in the (new) RA. If due to regional
subscription restrictions the MS is not allowed to be attached in the RA, the SGSN rejects the
RA Update Request with an appropriate cause, and may return an Insert Subscriber Data
Ack (IMSI, SGSN Area Restricted) message to the HLR. If all checks are successful then the
SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack
(IMSI) message to the HLR.

STEP 10 - The HLR acknowledges the Update Location by sending Update Location Ack
(IMSI) to the new SGSN.

STEP 11 - If the association has to be established, if Update Type indicates combined RA /
LA update with IMSI attach requested, or if the LA changed with the RA update, then the
new SGSN sends a Location Update Request (new LAI, IMSI, SGSN Number, Location
Update Type) to the VLR. Location Update Type indicates IMSI attach if Update Type in
step 1 indicated combined RA / LA update with an IMSI attach requested.



Otherwise, the Location Update Type indicates a normal location update. The VLR number
is translated from the RAI via a table in the SGSN. The SGSN starts the location update
procedure towards the new MSC/VLR upon receipt of the first Insert Subscriber Data
message from the HLR. The VLR creates or updates the association with the SGSN by
storing SGSN Number.

STEP 12 If the subscriber data in the VLR is marked as not confirmed by the HLR, the new
VLR informs the HLR. The HLR cancels the old VLR and inserts subscriber data in the new
VLR (this signalling is not modified from existing GSM signalling and is included here for
illustrative purposes):
The new VLR sends an Update Location (new VLR) to the HLR.
The HLR cancels the data in the old VLR by sending Cancel Location (IMSI) to the old VLR.
The old VLR acknowledges with Cancel Location Ack (IMSI).
The HLR sends Insert Subscriber Data (IMSI, GSM subscriber data) to the new VLR.
The new VLR acknowledges with Insert Subscriber Data Ack (IMSI).
The HLR responds with Update Location Ack (IMSI) to the new VLR.

STEP 13 - The new VLR allocates a new TMSI and responds with Location Update Accept
(VLR TMSI) to the SGSN. VLR TMSI is optional if the VLR has not changed.

ing

al link
Receive N-PDU Number contains the acknowledgements for each acknowledged-mode
NSAPI used by the MS, thereby confirming all mobile-originated N-PDUs successfully
transferred before the start of the update procedure.

STEP 15 - The MS confirms the reallocation of the TMSI by returning a RA Update Complete
(Receive N-PDU Number) message to the SGSN. The Receive N-PDU Number contains the
acknowledgements for each acknowledged-mode NSAPI used by the MS, thereby
confirming all mobile-terminated N-PDUs successfully transferred before the start of the
update procedure. If the Receive N-PDU Number confirms reception of N-PDUs that were
forwarded from the old SGSN, then these N-PDUs are discarded by the new SGSN. The
LLC and SNDCP in the MS are reset.

STEP 16 - The new SGSN sends a TMSI Reallocation Complete message to the new VLR if
the VLR TMSI is confirmed by the MS. In the case of a rejected RA update operation, due to
regional subscription or roaming restrictions, or because the SGSN cannot determine the
HLR address to establish the locating updating dialogue, the new SGSN will not construct
an MM context. A reject is returned to the MS with an appropriate cause.

The MS will not re-attempt a RA update to that RA. The RAI value is deleted when the MS
is powered-up. If the SGSN is unable to update the PDP context in one or more GGSNs,
then the SGSN will deactivate the corresponding PDP contexts. This will not cause the SGSN
to reject the RA update. If the RA update procedure fails a maximum allowable number of
times, or if the SGSN returns a RA Update Reject message, the MS enters the IDLE state. If
the timer described in step 2 expires and no Cancel Location (IMSI) was received from the
HLR, then the old SGSN stops forwarding N-PDUs to the new SGSN. If the Location
Update Accept message indicates a reject, then this is indicated to the MS, and the MS will
not access non-GPRS services until a successful location update is performed.

STEP 14 - The new SGSN validates the MS's presence in the new RA. If due to roaming
restrictions the MS is not allowed to be attached in the SGSN, or if subscription check
fails, then the SGSN rejects the RA update with an appropriate cause. If all checks are
successful then the new SGSN establishes MM and PDP contexts for the MS. A logic
is established between the new SGSN and the MS. The new SGSN responds to the MS with
RA Update Accept (P-TMSI, VLR TMSI, P-TMSI Signature, Receive N-PDU Number).

231

232

________________________________________________________________________________
12.6 Pa

d
work sends paging messages for circuit-
switched services on the same channel as used for packet-switched services, i.e., on the

ging Coordination
The network may provide co-ordination of paging for circuit-switched and packet-switche
services. Paging co-ordination means that the net
GPRS paging channel or on the GPRS traffic channel, and the MS needs only to
monitor that channel.
Network Modes Network Modes - - Paging Coordination Paging Coordination
Operating Mode I:
CS paging takes place on GPRS paging or traffic channel
(PCCCH or PPCH)
MS only monitors one paging channel
Operating Mode II:
GPRS and CS paging takes place on CS paging channel
(CCCH)
MS only monitors one paging channel
Operating Mode III:
CS paging uses the CS paging channel (CCCH)
GPRS uses either CCCH or PCCCH
MS must monitor both paging channels

ging coordination procedures are dependant upon the network operation mode
plemented:

Network Operation Mode I
Pa
im
.
The network sends a CS paging message for a GPRS-attached MS, either on the same
channel as th channel or the CCCH paging
chan l S needs only to monitor one
pagin ch it
has n

Network Operation Mode II.
e GPRS paging channel (i.e., the packet paging
ne ), or on a GPRS traffic channel. This means that the M
g annel, and that it receives CS paging messages on the packet data channel when
bee assigned a packet data channel.
The network sends a CS paging message for a GPRS-
continues on this paging channel even if the MS has been assigned a packet data channel.

etwork Operation Mode III
attached MS on the CCCH paging channel, and this channel is also used for GPRS paging.
This means that the MS needs only to monitor the CCCH paging channel, but that CS paging
N . The network sends a CS paging message for a GPRS-
attached MS on the CCCH paging channel, and sends a GPRS paging message on either the
packet paging channel (if allocated in the cell) or on the CCCH paging channel. This means
that an MS that wants to receive pages for both circuit-switched and packet-switched
rvices must monitor both paging channels if the packet paging channel is allocated in the
cell. No paging co-ordination is performed by the network in this network operation mode.
se



Network Modes Network Modes - - Paging Coordination Paging Coordination
Mode GSM Paging Channel GPRS Paging Channel Paging Coord?
I Packet Paging Channel Packet Paging Channel
CS Paging Channel CS Paging Channel Yes
Packet Data Channel not applicable
II CS Paging Channel CS Paging Channel No
III CS Paging Channel Packet Paging Channel No
CS Paging Channel CS Paging Channel

When the Gs interface is present, all MSC-originated paging of GPRS-attached MSs go via
the SGSN, thus allowing network co-ordination of paging. Paging co-ordination is
controlled by the SGSN based on the IMSI and is provided independently of whether the MS
is in STANDBY or in READY state. The network operates in mode I in this scenario.

When the Gs interface is not present, all MSC-originated paging of GPRS-attached MSs go
via the A interface and co-ordination of paging cannot be performed. The network then
operates in mode II, meaning that the packet common control channel are not allocated in
the cell

or

operate in mode III, meaning that the packet common control channel will be used for GPRS
paging when the packet paging channel is allocated in the cell.

The network operation mode (mode I, II, or III) is indicated as system information to MSs.
For proper operation, the mode of operation should be the same in each cell of a RA.
Based on the mode of operation provided by the network, the MS can then choose,
according to its capabilities, whether it can attach to GPRS services, to non-GPRS services, or
to both.

233

234

Interactions Between SGSN and MSC/VLR
The Gs Interface
Network Operating Modes
Combined IMSI/GPRS Attach / Detach Procedures
Combined GSM/GPRS Location Updating
GSM/GPRS Paging Coordination
BSS
MSC/
VLR
SGSN
Gs
A
Gb



13. GP
________________________________________________________________________________
13.1 Introduction

This section of the course describes how the GPRS network interacts with other data
networks external to the GSM system. This includes:

The Interworking interfaces
The Gi Interface IP connection
The Gi Interface X.25 connection
The Gp Interface - Inter-PLMN connections

RS Internetworking

235

236

________________________________________________________________________________
13.2 The Interworking Interfaces

GPRS Interworking Interfaces GPRS Interworking Interfaces
SGSN SGSN
PUBLIC PACKET DATA NETWORK PUBLIC PACKET DATA NETWORK
INTER INTER- -PLMN BACKBONE PLMN BACKBONE
GGSN BG
SGSN SGSN
BG GGSN
GPRS Core
Network
GPRS Core
Network
Gp Interface
Gi Interface Gi Interface

GPR e

Gi Reference Point. This is the reference point specified for connecting to an external Packet
Data Network (PDN) such as an intranet or the Internet. It supports primarily two protocols;
the Internet Protocol (IP) and X.25 by accepting packets from either of these protocols and
encapsulating them for transportation across the GPRS network using the GPRS Tunnelling
Protocol (GTP). The Gi reference point is also commonly referred to the Gi interface.

G Interface. This interface is specified for connecting to other GPRS networks via an
intermediary Public Land Mobile Network (PLMN). This interface is generally implemented
through a Border Gateway (BG) which has specific functionality to make this connection. A
roaming agreement between two Mobile Operators would normally be required for such an
interface to operate.

S d fines two basic interfaces for supporting packet access to external networks:
p



Internet Internet
X.25 X.25
GPRS GPRS- -PDN ( PDN (G G
i i
) Interface ) Interface
GSM RF GSM RF
MAC MAC
RLC RLC
LLC LLC
SNDCP SNDCP
IP/X.25 IP/X.25
Relay Relay
Relay Relay
UDP/TCP UDP/TCP
GTP GTP
L1 L1
L2 L2
IP IP
L2 L2
IP/X.25 IP/X.25
L1 L1
Relay Relay
L3 L3
L1 L1
L2 L2
GSM RF GSM RF
MAC MAC
RLC RLC
L1bis L1bis
Network Network
Service Service
BSSGP BSSGP
LLC LLC
SNDCP SNDCP
UDP/TCP UDP/TCP
L1 L1
L2 L2
IP IP
Network Network
Service Service
BSSGP BSSGP
GTP GTP
L1bis L1bis
GPRS Core GPRS Core
Network Network
GGSN
BSC/PCU
BSC/PCU
SGSN
U U
m m
G G
b b
G G
n n
G G
i i

________________________________________________________________________________
13.3 The G
i
Interface - IP Connection

G G
i i
Interface IP Connection Interface IP Connection
GPRS
NETWORK
G G
i i
IP
NETWORK(S)
TE
PLMN
TE
IPv4 or IPv6 IPv4 or IPv6
Addressing Addressing
IPv4 or IPv6 IPv4 or IPv6
Addressing Addressing

237

238

The conceptual view of the Gi interface to an IP network is shown above. In the same
way that the IP network is transparent to the user for end-to-end connectivity, so
should the GPRS network be transparent.

The diagram below shows how a GPRS network could be connected to an Internet
host. In order to exchange packets with an Internet user, the GPRS user is allocated an
IP address from within the GPRS operators range. In order to support a large number
of GPRS users (in IPv4), dynamic IP address allocation is normally used. Therefore, a
Dynamic Host Control Protocol (DHCP) server must be introduced in conjunction
with a Domain Name System (DNS) server to manage the available address space.

Address resolution between the Internet and GPRS networks is performed by the
GGSN using GPRS Packet Data Protocol (PDP) contexts. Transportation between the
GGSN and SGSN utilises the GPRS Tunnelling Protocol (GTP) over the Gn interface.

It is common to install protection from unauthorised access in the form of an Internet
firewall. In this configuration, from an Internet user perspective, the GPRS system
becomes transparent and the mobile user becomes simply another Internet user.

GGSN GGSN
G G
i i
SGSN SGSN
DNS DNS
Mobile Mobile
Operator Operator
IP IP
Network Network
Internet Internet
GPRS GPRS
Backbone Backbone
DHCP DHCP
Firewall Firewall
LAN LAN
G G
n n G G
n n
G G
i i
Host Host



G G
i i
G G
i i
GGSN GGSN
L2 L2
L1 L1
GPRS GPRS
Bearer Bearer
Router Router
IP Network IP Network
Router Router
L2 L2
L1 L1
IP IP IP IP IP IP IP IP

From a network perspective, the GPRS network looks like another IP sub-network and the
GGSN appears to be a normal IP router.

Being a packet data network (PDN), GPRS is optimised for connection to external PDNs and
more specifically IP-based networks such as the Internet or intranets. GPRS supports both
, t her IP network it looks like any
other IP subnetwork and the GGSN looks like a normal IP router.

________________________________________________________________________________
13.4 The G
i
Interface X.25 Connection

The diagram below represents the case where X.25 is used as the interconnect protocol between
a DCE and a DTE. The DTE resides within the GP S network and the DCE resides within the
PSDN. The GPRS Network is seen as part of the PSPDN, as the Gi reference point is simply the
interconnect point between the DCE and the DTE

IPv4 and IPv6 addressing. As can be seen below, the Gi interface is the internetworking point
with IP networks.

When looking in from outside the GPRS network o anot
R
.

239

240

G G
i i
Interface X.25 Connection Interface X.25 Connection
GPRS
NETWORK
G G
i i
PSPDN
DCE
TE
DTE
PLMN
TE
X.121 Addressing X.121 Addressing
X.121 Addressing X.121 Addressing

G G
i i
Interface X.25 Connection Interface X.25 Connection
GGSN GGSN
LAPB LAPB
L1 L1
G G
i i
GPRS GPRS
Bearer Bearer
X.25 X.25
Relay Relay
LAPB LAPB
L1 L1
X.25 X.25 X.75 X.75
PSDN PSDN
Relay Relay



The transmission protocol stack for the X.25 Gi interface is shown above. In this case the
GGSN resolves the association between the MS GPRS bearer and the X.25 DCE.
L1 is left to operators to determine connection to other networks. The X.25 Relay performs the
mapping of logical channel numbers.

Numbering and Addressing

A fixed X.121 address for the MS maybe allocated by the PSDN operator, and is integral to the
PSDN numbering plan. A dynamic X.121 address can also be used which is assigned by the
GPRS network at PDP context activation.

Charging
The charging information may be collected in the X.25 network, depending upon the
agreement between the GPRS operator and the PSDN operator. The charging may also be
collected in the GPRS network. If the VPLMN assigns the dynamic address, the charging of
the GPRS and the external network is gathered and sent to the HPLMN.

User Facilities
The set of user facilities as defined in ITU-T X.25 may be supported. As a minimum the
following are to be supported:

reverse charging;
reverse charging acceptance;
fast select restricted;
fast select unrestricted;
fast select acceptance.

13.5 The Inter-PLMN G
p
Interface

The primary reason for the Interworking between the GPRS networks is to support roaming
GPRS subscribers. The general model for GPRS network interworking is shown below:

ers that have a PDP address allocated from the HPLMN a forwarding
LMN and the VPLMN is created. This route is used for both mobile
originated data traffic. The communication is done via the Border
G

_______________________________________________________________________________
For roaming subscrib
route between the HP
terminated and mobile
ateways (BG)

241

242

Inter Inter- -PLMN Working Over the PLMN Working Over the G G
p p
Interface Interface
SGSN
PUBLIC/PRIVATE DATA PUBLIC/PRIVATE DATA
GGSN BG
GPRS Core
Network 1
SGSN SGSN
BG GGSN
GPRS Core
Network 2
G
p
Interface
SGSN

Inter Inter- -PLMN Roaming Issues PLMN Roaming Issues
Addressing
Inter-PLMN Link Establishment
QoS Implementation
Security
Routing Protocol Agreement

Charging Agreements



The procedures to set the link between the SGSN in the VPLMN and the GGSN in the
HPLMN is described in 3GPP TS 03.60.
The inter-PLMN link may be any packet data network or dedicated link as described in 3GPP
TS

QoS I l
03.60.
mp ementation.
tation of QoS levels over the inter- Implemen PLMN link can only be achieved if a dedicated
inter-P .
The GPRS PLMN link to fulfil the QoS
requir e

Security Agreements
LMN link exists, where such parameters as delay and throughput can be guaranteed
operators may therefore have a dedicated inter-
em nts of a certain protocol.

Each GPRS operator may support IPsec (RFC 1825) and accompanying specifications for
au hentication (RFC 1826). It may also support encryption (RFC 1827) as a basic set of
security functionality in its border gateways. GPRS operators may decide to use other
security protocols based on bilateral agreements.

Routing Protocol Agreements
t

Ea uting functionality in its
border gateways. GPRS operators may decide to use other routing protocols based on
bilateral agreements.

Charging Agreements
ch GPRS operator may support BGP (RFC 1771) as a basic set of ro

Sharing the cost of the inter-PLMN link is subject to the agreement between the GPRS
operators. There may be a requirement to collect charging information in the Border
G y. This would be subject to the normal interconnect agreement between PLMN and
PDN operators.

atewa

243

244

Interworking Interfaces
The G
i
Interface
IP Connections
X.25 Connections
The Gp Interface
Inter-PLMN Interface
Inter-PLMN GPRS Roaming Issues
SGSN
PUBLIC/PRIVATE DATA PUBLIC/PRIVATE DATA
GGSN BG
GPRS Core
Network 1
SGSN SGSN
BG GGSN
GPRS Core
Network 2
Gp Interface
SGSN


Planning for GPRS
Introduc

G ket Radio Services. It allows for users to be
permanently connected to a data network whilst only paying for data actually transferred.
GPRS works within the same timeslot structure as GSM but exploits the possible methods of
maximising throughput when the propagation channel permits it. It makes more direct use
of the raw data channels available in GSM. The timeslot structure leads to 114 information
b eslot in each 4.615 ms frame. This equates to a bit rate of 24.7 kbits/s
p
b
n
a nels coding
scheme (CCS) used by GPRS systems allows for a user rate of 21.4 kbit/s per timeslot. In
theory it is possible to allocate all 8 timeslots to a single user making a theoretical maximum
u
le

tion
PRS is an abbreviation for General Pac
its being sent per tim
er timeslot. This is reduced to approximately half of this rate when used as a voice channel
y using coding and error correction schemes. If a high quality radio channel exists there is
o need for extensive error correction coding to exist and thus a high proportion of the
vailable 24.7 kbits/s can be allocated to the user. In fact the highest speed chan
ser rate of 171.2 kbit/s a possibility. In practice the offered rate is likely to be substantially
ss as the technology of the equipment and network capacity issues are considered.
Planning for GPRS Planning for GPRS
General Packet Radio Services
Always On
Maximum Throughput
Theoretical Maximum Throughput 171 kbits/s
GPRS Planning

245

246
Structure of a Packet Service Session Structure of a Packet Service Session
Reading Time
Packet Service Session Duration
Packet Size Interarrival Time
Packet Call
A Packet Service Session
consists of a number of
calls. (A period surfing
the internet would form a
service session.)
Each call consists of a
number of packets.
Time intervals between
packets and calls are
important parameters
GPRS Planning

Potential Throughpu Potential Throughput t
GSM Frame contains 57 traffic bits every 4.615 ms.
Voice uses half this rate
Possibility exists to pass data rates closer to 24.7 kbit/s over a single
timeslot
GPRS Planning
This corresponds to 24.7 kbits/s
57 bits 57 bits
4.615 ms


Potential Throughput Potential Throughput
GSM Frame contains 57 traffic
bits every 4.615 ms.
This corresponds to 24.7 kbits/s
Voice uses half this rate
Possibility exists to pass data
rates closer to 24.7 kbit/s over a
single timeslot
GPRS Planning
57 bits 57 bits
4.615 ms
In practice 21.4 kbits/s per
timeslot is the highest that is
offered.
If all 8 timeslots are used,
potential is for 171.2 kbits/s to be
offered.
Actual offered maximum rate is
likely to be less than this.

Channel Coding Schemes (CCS).

The maximum rate of 21.4 kbit/s is only achievable if the mobile experiences very low levels
of interference. In these circumstances the Coding Scheme employed performs very little
error correction. This coding scheme may be regarded as optimised for low interference
areas. However, this particular Coding Scheme performs very badly when the interference
increases and the user throughput will drastically reduce. In such circumstances, other
Schemes are defined, each of which will provide the optimum throughput over a specific
range of C/I values. The diagram below shows how the throughput per timeslot varies
depending on the value of C/I experienced.

Coding Schemes would yield a higher throughput. A GPRS connection will utilise the best
Coding Scheme available depending on the level of interference experienced. Four Coding

247

248

It should be noted that not all GPRS networks or mobiles will have the capability of
operating at all four coding schemes. It is quite common to just have CCS1 (maximum 9.05
kbit/s per timeslot) and CCS2 (maximum 13.4 kbit/s per timeslot) implemented. Examining
vide the
vel Coding
Schemes C/I level exceeds 16 dB.
Data rate Arrays.

As part of the GSM planning process, it is normal to produce a map of the network showing
the levels of C/I that will be experienced by the mobiles. This can be converted by reference
to the coding scheme throughput graphs to a predicted data rate that is possible on the
downlink. An example of such a map (or arr ) is shown here. This reveals that coding
schemes 3 and 4 are only usable near each cell where the C/I levels are very high. CCS 2 is
usab o
oper e

the graph of throughput versus C/I reveals that CCS 1 and CCS 2 would pro
optimum throughput for values of C/I lower than 10 dB. Indeed, the higher le
do not provide a significantly higher throughput until the

ay
le ver a similar area to that which receives GSM coverage. Interestingly, CCS 1 can
at in worse C/I environments than that necessary for GSM voice.


Data Rate Arrays Data Rate Arrays
C/I is predicted as part of the normal GSM Planning Procedure
This can be converted to give a picture showing the maximum
throughput possible for each area.
GPRS Planning
Typically, the higher data
rates are only achievable in
areas close to cells.

Planning for GPRS

Consideration must be given to both the fixed network and to the air interface when
planning for GPRS implementation. Initially, the decision may be taken that the air interface
w ll have to look after itself that is GPRS will utilise spare capacity in the GSM network.
Implications of this will be dealt with later. However, new fixed network equipment must
be installed in order to accommodate GPRS traffic.

The Fixed

GPRS is defined as part of the GSM system. The BSS, as well as being connected to its
serving MSC will also be connected to a Serving GPRS Support Node (SGSN). The HLR and
VLR are common to the circuit-switched and packet-switched networks. Within the BSS
itself e equire software changes for CCS-1 and CCS-2. If CCS-3
and CCS-4 are to be implemented, hardware changes will be necessary so that bit rates
greater than 16 kbit/s can be accommodated. BSCs will require hardware changes in the
form of a Packet Control Unit (PCU). The capacity of the PCU will influence the overall
network capacity for GPRS services. Each PCU will have limitations in terms of the
maximum number of BTSs and total TRXs it can support; its transmission capacity and the
number of PDP contexts (which affects the number of simultaneously on-line users it
can support).

When deciding on the number of PCUs to be purchased and the capacity of the necessary
interf s e maximum network capacity for GPRS (i.e. how
many timeslots in total can be used for G Additionally, redundancy issues both for
the P s ered.

The SGSN is effectively the packet traffic switching centre. Again, it is necessary that the
SGSN is capable of handling the amount of traffic that the network is going to offer. The
SGSN will be equipped with a number of Packet Processing Units (PAPUs). Each PAPU will
i
Network
, th Base Stations will only r
ace , it is also necessary to consider th
PRS?).
CU and for the interfaces needs to be consid

249

250
be capable of handling a certain amount of traffic. The capacity of each PAPU and the
number used will influence the network GPRS capacity and must be appropriate for the
number and capacity of the BSCs being parented by the SGSN.

GPRS Planning GPRS Planning The Fixed Network The Fixed Network
Implementing GPRS will have implications for the
configuration of the BTSs the BSCs and the Core
Network.
GPRS Planning
BSC
MSC
SGSN
BTS
BTS

GPRS Planning GPRS Planning The BTS The BTS
For CCS-1 and CCS-2 only software
changes are necessary.
For Higher schemes (throughputs greater
than 16 kbps per timeslot) new hardware
is required.
GPRS Planning


GPRS Planning GPRS Planning The BSC The BSC
BSCs will require a Packet
Control Unit (PCU).
The PCU will have capacity
limitations for:
Number of TRXs
Number of BTSs
Total Transmission Capacity
PDP Contexts
Further the capacity of
interfaces must be assessed.
Redundancy issues must be
addressed.
GPRS Planning
BSC

GPRS Planning GPRS Planning The SGSN The SGSN
The SGSN is the switch for
Packet Traffic.
Equipped with Packet
Processing Units (PAPUs)
Each Packet Processing Unit
is capable of handling a
certain amount of traffic.
GPRS Planning
SGSN

251

252
General Core Network Architecture General Core Network Architecture
I
U
CN
MSC/VLR
SGSN GGSN
GMSC
HLR
Serving
GSN
Gateway
GSN
Gateway
MSC
Mobile
Switching
Centre
Home
Location
Register
Other SGSN
Other MSC
BSS
BSS
External
Circuit
Switched
Networks
External
Packet
Switched
Networks
I
u-cs
I
u-ps
G
s
G
n
G
n
G
r
G
c
D
D
G
i
F
F
GPRS Planning

Air Interface Planning for GPRS

The throughput possible per timeslot depends upon:

The channel coding scheme being used
The C/I of the radio channel
The characteristics of the propagation channel and the speed of the mobile

Further, the use of Frequency Hopping will allow higher level coding schemes to be used in
more hostile environments.

Also, the GPRS coverage afforded is different for the different CCSs. In general coverage for
CCS-2 is similar to that for GSM voice with a slightly better coverage for CCS-1 and smaller
areas offered CCS-3 and 4.


Air Interface Planning for GPRS Air Interface Planning for GPRS
Throughput influenced by:
Channel Coding Scheme
C/I
Characteristics of Channel
(including mobile speed affects).
Additionally, Frequency Hopping
facilitates the use of higher level
CCSs.
Coverage for CCS-2 generally
similar to that for GSM voice.
GPRS Planning

Measuring GPRS Traffic and Capacity Planning

The use of GPRS per subscriber is critically measured in terms of the busy hour demand.
Suppose a typical subscriber generates 1 Mbit of GPRS traffic in the busy hour (an average of
280 bits per second). If there are 4000 subscribers, this would lead to 4000 Mbits of traffic in
1 hour, which equates to an average demand of 1.1 Mbits/s. This sort of demand can be
accommodated by approximately 100 timeslots (although the exact number will depend on
the channel characteristics and CCSs available).

Capacity Planning for G Capacity Planning for G
Measuring Subscriber Traffic:
PRS PRS
Traffic measured in Megabits during the busy hour (not a constant rate in
kbps).
bit during the busy hour equates to an average of approximately
280 bits per second.
rate an average demand of
approximately 1100 kbits/s.
lays.
GPRS Planning

E.g. 1 M
4000 such subscribers would gene
Number of timeslots required depends on C/I and use of CCSs.
At 11 kbit/s per timeslot, 100 timeslots would be required.
Availability of timeslots would influence de

253

254

Sharing Capacity with CS Traffic.

The normal situation is for CS traffic, such as voice, to take priority over PS traffic.
However, the fact that the CS network has been dimensioned to provide a low blocking ratio
(e.g. 2%) means that the timeslots will only rarely be fully occupied. For example, if a cell
this would expect to carry 14.9
rlangs. That leaves an average of 7.1 timeslots available for packet traffic. This could in
c was
always being offered when there was capacity vailable to take it. This might carry an
average data rate of 80 kbit/s enough for appr ately 280 subscribers at an average of 280
bits per second.

As a rule of thumb, an occupancy rate of between 80 and 90% can be assumed when there is
a moderately heavy demand for services. Thus a more realistic figure would be 240
subscribers being served.

It must be remembered that GPRS services are new and that future subscriber behaviour is
very much an unknown.

uses 3 carriers and has 22 timeslots available for traffic,
E
theory service 7.1 Erlangs of packet traffic, although that assumes that packet traffi
a
oxim
Capacity Planning for GPRS Capacity Planning for GPRS
Sharing Capacity with CS Traffic:
CS traffic will take priority.
Dimensioning for a small (2%) Blocking Probability will mean that there is
usually extra capacity available.
GPRS Planning
Time
Load
Target Load
Non Controllable Real Time
Load


Capacity Planning for GPRS Capacity Planning for GPRS
GPRS Planning
Load
Target Load
Non Controllable Real Time
Load
E.g. 3 TRXs with 22 traffic timeslots will
serve 14.9 E of traffic.
h
alw
av
y
co
of
av
Working to an estimate of 80 90%
occupancy suggests 240 subscribers is a
more realistic value.
Subscriber behaviour
not yet known.

Enhanced Da

GSM use
on the da pproximately 50 kbits/s. In
practice it is always difficult to exceed 50% of this theoretical limit and thus CCS-4 is
pushing throuphput very close to its limit. EDGE utilises 8 PSK (an 8 state modulation
scheme) that encodes 3 bits for every symbol. This pushes the theoretical limit to 150
kbits/s. However, EDGE requires a high quality radio channel in order to exploit its full
potential. To achieve the maximum throughput of over 60 kbits/s per timeslot requires a
C/I (or C/N) level of over 35 dB. However, throughputs in excess of 30 kbits/s are possible
for C/I levels of only 15 dB, a clear improvement over binary modulation schemes.

Implementing EDGE involves hardware changes to both the network and the mobile. It will
provide higher throughputs if the radio channel can sustain it. In general, the fact that
EDGE will only provide partial coverage (at least initially), will still lead to it helping with
t overall PS load as it will allow those users that can benefit from EDGE to be served more
rapidly, thus freeing up network resources for other purposes.

Average of 7.1 timeslots available for
packet traffic.
T is would serve 7.1 Erlangs if traffic was
ays being offered when capacity
ailable.
T pically, these timeslots would have a
mbined throughput of 80 kbit/s capable
serving 280 subscribers with an
erage of 280 bps.
Remember that GPRS
is a new service.
ta Rates for GSM Evolution (EDGE)
s a binary modulation scheme (Minimum Shift Keying). This puts an absolute limit
ta rate that will be possible within a timeslot of a
he

255

256
EDGE EDGE
Bandwidth fundamentally limits the Symbol rate.
Symbol rate is linked to bit rate by the modulation scheme.
BPSK: 1 bit per symbol
8PSK: 3 bits per symbol
0 1
GSM uses a binary scheme.
Absolute limit of 50 kbit/s per
timeslot in a 200 kHz bandwith
Practical limit approx 25 kbit/s
EDGE uses a 8-state scheme.
Absolute limit of 150 kbit/s per
timeslot in a 200 kHz bandwidth
Practical limit approx 63 kbit/s
GPRS Planning

EDGE and C/I EDGE and C/I
EDGE achieves a higher data rate than conventional GSM by utilising an
8PSK modulation scheme. GSM uses a form of BPSK.
EDGE will require a better SNR than GSM to achieve higher (> 40 kbps)
throughputs.
30 kbps possible for C/I > 15dB a clear improvement over GSM
BPSK: 1 bit per symbol 8PSK: 3 bits per symbol
GPRS Planning

BTS location planning

tified as likely to offer a lot of packet traffic, it is good planning practice to ensure
that the C/I levels in that area are as high as possible, not merely sufficient to allow GSM
speech. city of a cell is not a fixed number of bits per second but,
rather, depend on the environment of the user.
Unlike with voice services, the network capacity for GPRS and EDGE will be influenced by
the location of sites in relation to areas of high demand. If for example a particular business
area is iden
This is because the capa



Implementing EDGE Implementing EDGE
Hardware changes to the network and the mobile required.
EDGE will help overall capacity by delivering very high data rates in
areas of high C/I. This influences location planning. If the BTS can be
place near an area of high demand, the throughput will be increased.
GPRS Planning
EDGE area
GPRS area

BTS Location Optimisation BTS Location Optimisation
GPRS Planning
In traditional GSM networks the capacity of a cell is generally unaffected by the
position of users within its coverage area.
With GPRS, it is possible to enhance the capacity of the cell by ensuring that areas
of high demand experience a high C/I.
This is a further consideration for network planning.
High Throughput
Area
Low Throughput
Area

257

258
Why Optimise? Why Optimise?
proving C/I at a point from, for example, 14 dB to 17 dB will have a Im
n
T
voice.
A
T
f y re-use strategies have been adopted.
GSM Optimisation for GPRS
oticeable affect on achievable bitrate.
his will reduce the timeslot demand from GRPS, increasing capacity of
lso, it will improve the coverage, capacity and efficiency of a voice network.
his is particularly noticeable in multi-layer networks in which aggressive
requenc

Examples of Improvement Examples of Improvement
Group planning was applied to a
cluster of 28 sites using a 4/12 re-use
patter
For part
value
GPR
It is p
C/I o
Freq

n. C/I was predicted.
icular coding schemes, these
s of C/I can be converted into a
S data rate.
ssible to improve the values of o
bserved by using an Automatic
uency Planning tool.


AIRCOMs proprietary frequency
planni tool, ILSA, was used to
improv the plan.
The same number of carriers was
allocated but ILSA was able to
optimi e plan so that the
percen
interfer
Most o
16 dB
ng
e

se th
tage area affected by
ence was minimised.
f the area was receiving a C/I of
or better.
Examples of Improv Examples of Improvement ement
A more detailed examination revealed
that significant areas were
exper
than 24

iencing values of C/I of better
dB.

259

260
Examples of Impro Examples of Improvement vement
Zooming into the view
rev that C/I is azimuth-
de
range.
Va
60
typical.

eals
pendent at a given
riations of 5 dB over a
degree movement are
Examining the Channel
Coding Schemes shows
that C/I values of greater
than 12 dB can only be
exploited if Schemes 3 and
4 are implemented.
These higher level
schemes require hardware
modifications.


GPRS and Multiple Re GPRS and Multiple Re- -use Patterns use Patterns
Most benefit from improving
C/I comes at low levels of
initial C/I.
For example. C/I improvement
from 3 dB to 6 dB increases
throughput by 50%.
Improvement from 12 dB to 15
dB increases throughput by
14%.

GPRS and Multiple Re GPRS and Multiple Re- -use Patterns use Patterns
Message is that:
GPRS will operate in
environments too hostile
for voice.
Im
environments will be
be
vi

provements in those
neficial from the
ewpoint of throughput.

261

262
A Re A Re- -use Factor of 3 use Factor of 3
The same 28 site cluster was
manually planned with a re-use
factor of 3.
C/I values varied from 4 to 26
dB.
Throughputs expected to vary
from 5 kbps to 20 kbps.
Typical value: 10 dB (11 kbps).
70% of area good for voice
(greater than 9 dB C/I).

A Re A Re- -use Factor of 3 use Factor of 3
Because of the strict limitation
on the number of carriers, no
improvement was possible
thro

ugh the use of an
matic Frequency Planning Auto
Tool.


Introducing an Extra Carrier Introducing an Extra Carrier
Introducing a fourth carrier
should increase the average
C/I experienced.
This will increase overall
throughput possible.
We can evaluate whether it is
worth the extra carrier.
Should also increase
percentage good for voice.


Result is
ood for
80%
Many areas have much-
improved C/I.
Some areas experience a
worse C/I.
that the percentage
voice increases to g
.

263

264
Providing the extra carrier did
not provide a uniform
improvement.
It may be best to provide a
basic coverage using the 3
carriers, holding the fourth
carrier in reserve for hotspots.
The hotspot issue is of great
interest in GPRS planning and
has implications for MRP
strategies for GSM voice.

Location Optimisation Location Optimisation
Placing sites and orienting
antennas so that hotspots
receive the highest possible C/I
has advantages from the
viewpoint of minimising the
number of timeslots necessary
to provision for demand.
AIRCOMs planning tool,
ASSET, was used to simulate
three different situations.


Firstly: 150 kbps demand from
an area of Low C/I.
Frequency Re-use factor of 3
employed.
5 kbps per timeslot achievable.
37 Timeslots required assuming
80% occupancy.
Low C/I

an area of Moderate C/I.
employed.
11 kbps per timeslot
achievable.
80% occupancy.
Note: this can be achieved by
changing antenna azimuth.
Moderate C/I

265

266
an area of High C/I.
employed.
20 kbps per timeslot
achievable.
80% occupancy.
Note: requires location
planning.
High C/I

Other Possibilities: adding a repeater Other Possibilities: adding a repeater
Repeaters can improve the local
C/I.
An example is shown before
and after the introduction of a
repeater.
Area of interest
Note: colour changes in 4 dB increments


Other Possibilities: adding a repeater Other Possibilities: adding a repeater
C/I improvement is very
sed :- within a few hundred locali
metres of the repeater site.
Improvement lifts C/I to
approximately that which could
be achieved by adjusting
azimuths.
Not as effective as moving the
site; but probably much less
costly.
Area of interest
Note: colour changes in 4 dB increments

The impact on GSM voice The impact on GSM voice
Techniques focussed on
improving thoughput in GPRS.
Most beneficial when tight re-use
factor (e.g. 3 is employed).
This will have an impact on voice
services, particularly when
different re-use factors are
employed on different layers.
Voice area
covered by layer
with re-use factor
of 12
Voice area
covered by layer
with re-use factor
of 3

267

268
The impact on GSM voice The impact on GSM voice
The greater the area that can be
served by both layers, the higher
the trunking efficiency.
E.g. if the two areas shown are
equal and each have 7 timeslots,
each can serve 3 Erlangs: total 6
Erlangs.
If the whole area has access to
14 timeslots, then 8 Erlangs can
be served.
Great advantage in serving
hotspots with all available layers.
Voice area
covered by layer
with re-use factor
of 12
Voice area
covered by layer
with re-use factor
of 3

EDGE and C/I EDGE and C/I
57 kbps 21 kbps 30 dB
10 kbps 7 kbps 5 dB
EDGE GMSK C/I
Compa o
for Binary and 8PSK modulation
scheme .
Note that, due to space and
transmission constraints, a
typical EDGE transmitter may
operate at a few dB lower Tx
power than a standard
transmitter.
Nevertheless, conclusion is that
EDGE will offer superior bitrates.

ris n of bitrates possible
s


Summary Summary
GPRS packet data utilises different coding schemes that will permit data transfer
at a rate that is dependent on the C/I experienced at the receiver.
GPRS can operate at C/I levels too low to permit voice communication.
rom hotspots can be profitable.

GE provides potentially much higher throughput than Binary modulation
emes.

Improvements in GPRS capacity can be achieved through smart planning rather
than heavy investment.
In particular, planning to accommodate demand f
ED
sch

269

270

Self-Assessment Exercises

1. A particular network is to allow mobile users to utilise GRPS by means of seizing two GSM
timeslots simultaneously. By referring to the graph shown earlier in this section, estimate the CCS
that would be used and the throughput achievable for the following C/I values.

C/I CCS Throughput
14 dB
7 dB
18 dB
4 dB

2. A particular 3-sector site is serving an area that will contain an estimated 500 GPRS subscribers. The
average subscriber will transfer 800 kbits during the busy hour. Estimate the number of timeslots
that should be made available for GPRS if on CCS-1 and CCS-2 are implemented.



271

272


_____________________________________________________________________
15.1 Introduction

5.1.1 DEFINITIONS OF OPTIMISATION

1
Dictionary Definition of Optimisation Dictionary Definition of Optimisation
Determining the best compromise
between potentially conflicting
requirements in order to plan and
implement an activity with maximum
efficiency.
Section 7 Optimisation Overview



A Mobile Network Definition of Optimisation A Mobile Network Definition of Optimisation
n and rectification of
ing network

The identificatio
performance affecting problems within
the constraints of an exist
infrastructure.

15.1.2 REASON FOR OPTIMISATION

The goal of optimisation is to ensure the network is operating at optimum efficiency and
hin the de wit fined quality of service constraints.

This is achieved by implementing corrective action and procedures to rectify network
problems identified though analysis of performance management monitoring parameters.

Reason Reason
for Optimisation for Optimisation
Goal:
Identify network problems through analysis of KPIs
Implement corrective actions and/or procedures to rectify problems
Monitor results of modifications
Purpose:
Maintain/improve QoS
R
Attract new customers
Ensure optimum network performance within QoS constraints
Process:
educe churn rate
Maximise revenue-generating service
Maximize efficiency of network functional elements

273

274

The reason this optimisation process is carried out is to:

Maintain or improve quality of service
Reduce churn rate by retaining existing customers
Maximise revenue generating services by maximising efficiency of functional

___________ _
15.2 Requirements for Optimisation

Attract new customers
network elements.
_________________________________________________________
Requirements for Optimisation Requirements for Optimisation
Network issues that may generate a requirement for optimisation include:
Perceived reduction in network quality
Indications from network performance monitoring
Subscribers experience of using the network
Maximising the use of existing infrastructure
operator wants to ensure best return on investment
Introduction of new services
maximise existing resources to accommodate new services such as GPRS
Change in original design parameters
Flawed original design information
Original design information has changed
Regardless of the initiating event, the optimisation procedures remain
generally the same

Vendors are continually seeking ways of maximising revenue generation with minimu
additional investment. One way of achieving this is to identify areas where the network is
not operating at peek efficiency and making adjustments for improvement. For example,
over capacity may exist in certain areas allowing for a possible removal of TRXs.
lternatively, congestion may exist in certain areas and by prudent optimisa
m
tion, additional
capacity can be generated with no additional infrastructure investment.

he Vendor may wish to add new services to the network (such as HSCSD/GPRS) in order
nimal additional infrastructure investment to meet the
creased capacity demand.

A
T
to attract more customers and/or increase revenue generation. This may generate an
increased requirement for network capacity either in terms of additional customers or an
average increase in traffic per existing customer. Network optimisation may enable these
ervices to be introduced with mi s
in



It may be that the original network design was based on flawed information and as a result
the network is not performing as originally envisaged. Alternatively, information on which
the network design was based has subseque

ntly changed, requiring a change to the network
onfiguration. For example, a new airport or shopping mall has been built creating
unforeseen congestion in a particular part of the network.

_____________________________________________________________________
15.3 Outline Optimisation Process

5.3.1 PERFORMANCE MANAGEMENT AND OPTIMISATION
c
1

Performance Ma Performance Management Cycle nagement Cycle
Monitor
Network
Analyse Data
Yes
Identify
Problems
Implement
Changes
No
Initial Network
Design and
Implementation
Performance Management
Optimisation
QoS
Targets
Met?

Optimisation forms part of the performance management process. The objective of the radio
network optimisation is to extract the optimum performance from the cellular network, at
any given phase of its lifecycle. All cellular systems will be associated with continuous
change, with new radio sites being introduced, old sites being enhanced and assigned
additional frequencies, omni-directional sites being sectorised, new frequency plans being
implemented in different regions, etc.

The initial step in performance management is to define a set of QoS (Quality of Service)
arameters such as dropped call rates and call success rates. Key metrics are derived from
ata collected from sources such as drive tests, statistical data, customer complaints and
ld engineer reports and are used to measure the performance of the network. These
metrics are analysed and compared to the QoS targets in order to identify any performance
degradation in the network. If problematic areas are identified from analysis of the network
performance parameters, corrective processes and/or procedures are implemented to rectify
the situation using one or a combination of techniques. This process of corrective actions is
known as optimisation.
p
d
fie

275

276

15.3.2 OUTLINE OPTIMISATION PROCESS

Outline Optimisation Process Outline Optimisation Process
Initial network design
and roll-out phase
Monitoring/
Network Audit Phase
Optimisation Activity
Phase
Design Review and
growth phase

_____________________________________________________________________
15.4 Network Audit Phase of Optimisation

Network Audit Phase of Optimisation Network Audit Phase of Optimisation
Decide on KPIs,
Measurement Strategy and
Tools
Measure Performance,
Establish Benchmark
Performance Review to
Identify Major Performance
Affecting Issues
Decide on Strategy,
Establish Action Plan Feedback from
Optimisation
Activities
Start Optimisation Activity



The t

e the both validity and consistency across the network.
Analysis of data gathered from performance-related network monitoring in order to
ating performance levels.

15.4.1 DECIDING ON KPIs, MEASUREMENT STRATEGY AND TOOLS
ne work audit phase serves two primary purposes:
A review of existing network hardware and software (inc database) configurations
to determin
identify weaknesses or sub-optimal oper

Thi e
within the network. A mature network should already have its KPIs and measurement
strategy in place, together with tools to support this process. However, in such cases, part of
the network audit process would be to validate these measurement counters and
procedures.

15.4.2 MEASURING PERFORMANCE AND ESTABLISHING
s st p in the process is normally only implemented when these elements do not exist

BENCHMARKS

In mature networks, benchmarks would have already been established. Measuring
performance is an ongoing process. However, if a network audit is to carried out as an
independent process, a review of existing performance parameters and benchmarks will be
quired to ensure their validity and applicability to the audit taking place.

15.4.3 PERFORMANCE REVIEW
re

Network Audit Process Network Audit Process
Performance Review Processes:
Network performance statistics (OMC)
A-Interface performance statistical analysis
Call Trace Analysis
Alarms and events
GSM performance drive test
GPRS Performance drive test
Competitive drive test benchmarking

277

278

aving established benchmarks and validated performance parameters, a review of
in the slide

The performance Review is not intended to provide all the answers to all the problems, but
to highlight the major issues and provide all the necessary background for further analysis,
igation and in-depth troubleshooting of the major performance-impacting problems in
e network. It is important that any network performance audit should follow a
methodical process and should be systematic in its approach to data collection.

H
performance is carried out. A possible structure of such a review is as shown
below.
invest
th
For each category the following structure can be
applied:
Objective. What are we trying to measure?
Description. Why measure it and its relevance to
performance?
Report Form. How should the results be presented?
Interpretation. What conclusions can be drawn from
results?
Recommendations. How can the problem be resolved?

For each of the performance category headings in the outline structure, the following logical
process is applied:

Objective: What parameter are we trying to measure?

Description: Why are we measuring it and what is the relevance of the
measurement to network performance?

Report Format: How should the measurement be presented, in what kind of graph
and what format?

Interpretation: What are the possible conclusions we can draw from the results?

Recommendations: Based on our observations and conclusions, what
recommendations can we make for solving the problem or for further investigation?



5.4.3.1 OMC Statistics Review 1

N Network Audit Process etwork Audit Process
OMC Statistics Review:
Call Success Rate
Call Setup Rate
TCH Blocking
TCH Assignment Failure (RF)
DCCH Access performance
Dropped Calls

15.4.3.2 A Interface Analysis
SDCCH RF Loss
S
Handovers

A Interface Analysis:
Call Setup Failures
Location Update Success Rate
Handover Causes

279

280

15.4.3.3 Call Trace Analysis

Call Trace Analysis:
DL receive level and BTS power
UL receive level and MS transmit power
UL and DL RxQual distributions

15.4.3.4 Drive Test Metrics

Drive Test Metrics - Route :
Coverage route plot
Quality route plot
Frame erasure (FER) route plot
Speech Quality Index (SQI) route plot

MS transmit power route plot



Drive Test Metrics - Events :
Dropped call events
Call setup failure events
Handover failure events
Successful handover events

GPRS-Specific Drive Test Metrics:
RLC throughput
LLC throughput
RLC BlkER
)
ated timeslots
Latency/Jitter
PDP context loss (GPRS call drop)

RLC retransmission rate
Coding scheme usage (CS1-4
Alloc
Packet loss rate
PDP Context activation failure

281

282

_____________________________________________________________________
15.5 Network Performance Review Summary

The summary of the Network Performance Review should aim to highlight
the specific performance problems identified in the network, on Network
level, BSC level and Cell level. The following headings should be included
here:

_____________________________________________________________________
15.6 Activity Phase of Optimisation

Activity Phase of Optimisation Activity Phase of Optimisation
Start Optimisation Activity
Identify and Fix Hardware Problems Ongoing
Performance
Measurement
Process
Review Process and Results
Feedback to modify
strategy decisions
BSS Database
Parameters Review:
Settings
Consistency
Change Control
Design Review and Growth Plan
Identify and Fix Neighbour Problems
Identify and Fix Frequency Plan Problems
Network Audit Procedures
Feedback
to
Audit
Procedures

c
c
e
s
s

u
p
D
r
o
p

C
a
l
l

R
a
t
e
T
C
H

C
o
n
g
e
s
t
i
o
n
S
D
C
C
H

A
s
s
i
g
n
m
e
n
t

S
u
c
c
e
s
s

R
a
t
C
a
l
l

V
o
l
u
m
e

/

t
r
a
f
f
i
c
H
a
n
d
o
v
e
r

S
u
c
c
e
s
s

R
a
t
e
1.85% 0.73% 92.10% 1244300 95.60%
e
R
a
t
e

S
u
c
c
e
s
s

R
a
t
Network
Name
C
a
l
l

S
u
C
a
l
l

S
e
t
XYZ-net 91.70% 93.40%



283

284



16. B

_____________________________________________________________________
16.1 Introduction

This section of the course provides guidance on how to improve the performance of the
network by adjusting performance parameters. The performance monitoring phase will
have identified any irregularities in the network by analysing the performance measurement
parameters.

SS Optimisation Activities

285

286

_____________________________________________________________________
16.2 BSS Database Parameter Review

16.2.1 REVIEW DATABASE SETTINGS

BSS Configuration Parameter Review BSS Configuration Parameter Review
Review current settings as related to performance
measurement results
Recommend changes to improve/optimise performance of
specific features.
Review includes:
Handover parameters, timers, thresholds and margins
Power control thresholds
Averaging mechanisms for handover and power control
Call setup parameters to maximise resource utilisation
C1/C2 cell reselection parameters
Any vendor-specific advance traffic management algorithms
Section 8 Optimisation Activities

The BSS database parameter review is intended to review existing BSS database parameter
settings in the light of performance measurement results, and recommend changes
specific features. This review includes
wer window settings, power up/down step size,
adaptive power control parameters, and so on).
nd availability
C1/C2 cell reselection parameters.
Advanced traffic management algorithms (Congestion-based handovers, inter-band
and inter-layer traffic distribution)

necessary to improve or optimise the performance of
the following:

Handover parameters, timers, thresholds and margins (including inter-layer and
inter-band handovers where applicable).
Power Control thresholds (po
Voting and averaging mechanisms for handover and power control decisions.
Call setup and handover timers to maximise resource utilisation a



16.2.2 DATABASE CONSISTENCY AND CHANGE CONTROL
atabase management processes. For example:
a variety of site types (micro,
3, etc.).
n permissions basis (fully

Review of all BSS databases to identify inconsistencies and discrepancies, and a review of
change control, datafill and d

Define pre-configured parameter templates for
highway 2/2, urban 3/3/
Identify sets of parameters allowed for optimisation o
configurable permissions per BSC, region, etc).
Check consistency of live network data against planned configuration.

BSS Database Parameter Consistency BSS Database Parameter Consistency
Within a network, different site types are defined (e.g. urban
micro, rural macro etc) by a standard template
Each site type database will comprise a default parameter
set
Each site may modify default set to suit local conditions
Consistency of the default parameter sets should be
checked across BSS types
Change control management processes should be reviewed
to ensure procedural consistency

16.2.3 BSS CONFIGURATION PARAMETER SETS

Each BSS performs in accordance with its software configuration. Generally, there will be a
common set of default parameters for each BSS, for example, the handover algorithms.
owever, each BSS will be programmed with certain parameters which are tailored to suit
specific actions, locations and/or applications. Examples of BTS-specific parameters include
ttings.

H
the cell ID and power output se

287

288

BSS Configuration Parameter Sets BSS Configuration Parameter Sets
Each BSS operates in accordance with its software
configuration
All BSS are configured with certain standard default
parameters
Each BSS will have a subset of BSS-specific parameters
Parameters defined by:
ETSI GSM Recommendations (GSM 12.04)
Proprietary Parameter Implementation
Potentially hundreds of configuration parameters
Many parameters are inter-dependant
Often vendor-specific abbreviations/acronyms used for same parameter

arameters run into their hundreds and are defined in two
ETSI GSM Recommendations

The number of configurable BSS p
sources:

. ETSI has defined a primary set of parameters which
are listed in the GSM 12.04) document.
Proprietary Parameters. These are additional parameters created by individual
vendors to enhance the capabilities of their equipment when compared that of their
competitors.

This multitude of parameters allows for very sophisticated control of the BSS behaviour.
However, the complexity can also lead to problems:

Many parameters are inter-related so changing one can have a corresponding effect
on others.
Many equipment manufacturers use different abbreviations or acronyms for the
same GSM-recommended parameter, leading to potential confusion when a
network comprises equipment for more than one manufacturer.

16.2.4 BSS PARAMETER TYPES

As mentioned above, the number of performance configuration parameters in a BSS runs
into three figures. Within the scope of this overview course, the following provides an
overview of the type of parameters stored:


289

BSS Configuration Parameter Types BSS Configuration Parameter Types
Identifiers:
CI, LAI, GCI, BSIC etc
Channel Configuration:
TCH channels, Signalling channel configuration (e.g. CCCH)
Timers:
Location Updates, C2 calculations etc
Thresholds:
RxLev, RxQual for handover decisions etc
Offsets:
Hysteresis for handovers etc
Control Features:
SFH, DTX, DRX etc

entifiers

Id .
his includes such parameters as the Cell Identity (CI), Cell Global Identity (CGI) Location
(LAI) and Base Station Identity Code (BSIC) etc
hannel Configuration Parameters.
T
Area Identity

C
eters define the number of traffic channels and control channels. For example,
e configuration of CCCH on the signalling channel (i.e. combined/non-combined
ultiframes).
Timer Parameters
These param
th
m

imers are counters which are set at the start of a certain time period and count down. If an
vent has not happened by the time the counter reaches zero, an alternative action may be
iggered. For example, the time periods between periodic location updates (T3212) or the
penalty timer for C2 calculations (see Cell Reselection in Section 1 for details).
hreshold Parameters
T
e
tr

T
hresholds are certain values which, when exceeded, trigger a certain event. For example,
received signal strength or bit error rate thresholds which may trigger cell handovers.
ffset Parameters
T

O
ffsets are fixed values applied for the purposes of applying bias to certain actions. An
example is the hysteresis bias value applied to BTS at location area boundaries.
ontrol Feature Parameters
O

C
number of parameter settings exist to identify the implementation of certain functions and
atures. Such features include Frequency Hopping, DTX etc

A
fe


290

16.2.5 ADJUSTING BSS CONFIGURATION PARAMETERS

Adjusting BSS Configuration Parameters Adjusting BSS Configuration Parameters
Effected from:
PC connected directly to hardware
Remotely from OMC/NMC
Can be individually addressed or broadcast
May require hardware reset to effect change
Be aware of hierarchical changes (MSCBSCBTS)
Only implement during low-traffic periods
Use test BSS where available
Avoid simultaneous multiple parameter changes

It is normally possible to carry out parameter changes from:

BSS directly into the BSS database via a PC connected to the BSS.

OMC/NMC Many OMC/NMC systems allow parameters to be transmitted to the
BSS remotely including a broadcast capability where a specific parameter change
needs to be transmitted to several network entities simultaneously.

Adjustment of parameters on live network elements should be deferred until low traffic
periods in order to minimise any disruption to existing users. This is particularly important
when a configuration change requires a hardware reset to become effective. A change BSC
parameter is changes it may affect all BTSs associated with that BSC.

Some network operators reserve a BSS for test purposes. This has the advantage of being
able to assess the impact of a parameter change before making the adjustment to a live
network. However, it is a non-revenue generating asset.

Making simultaneous multiple parameter changes should also be avoided where possible
for two reasons:

If an unexpected problem arises as a result of a multiple parameter change, it will be
difficult to identify the specific parameter or parameter combination causing the
problem.
Similarly if a performance improvement is observed, it may be difficult to identify
which of the parameters are causing which part of the performance improvement.



291

_____________________________________________
6.3 Identify and Fix Hardware Problems

Identification of BSS hardware problems can be identified though the analysis of OMC
statistical data, drive test data, A-Bis and A-Interface logs. Worst Performing Cells can be
identified through analysis of established KPIs.

________________________
1
Identify Hardware Problems Identify Hardware Problems
Problems identified through analysis of performance
measurement counters from:
OMC Statistics
Driver \Test data
A-bis and A interface logs
Identify worst performing cells according to established KPI
benchmarks

Typical examples of hardware problems include:

Ty Ty
Section 8 Optimis
pical Hardware Problems pical Hardware Problems
Misaligned Antennas
Increased interference, coverage degradation
Reduced power output, reduced coverage, cell imbalance, distortion
ansmission line performance (water ingress, corrosion,
al damage etc
High VSWR, high Inser ion losses, reduced power output, reduced
coverage, cell imbalance, distortion
Poorly calibrated TRXs
Inconsistent TRX performance
Incorrectly configured combiners/duplexers etc
ation Activities

Wrongly/poorly connected feeders
Poor tr
physic
t
Reduced power output, reduced coverage, cell imbalance, distortion

292

_____________________________________________________________________
1

I
s
b
c

T
resu e to unavailability of resources, causing the handover to be attempted
to the next best neighbour, which can delay the process and deteriorate the quality further.

Under certain circumstances, it may be necessary to remove a potential neighbour from the
neighbour list and provide alternatives. Usually, such decisions are made using
demographic considerations.

6.4 Identify and Fix Neighbour Problems

n GSM, several neighbour cells can be defined for a serving cell. Usually, handovers
hould be made to the strongest neighbour, but in some cases frequent handovers to this
est neighbour can result in congestion in the neighbour cell, affecting the users initiating
alls from that cell.
he situation can also occur in reverse, when a handover required to the best neighbour can
lt in a rejection du
Optimising Neighbour Lists Optimising Neighbour Lists
Effects of poor maintenance:
Unwanted legacy neighbours
Oversized neighbour lists
Co-channel neighbour definitions
Optimise by:
Analyse neighbour performance form statistics.
Utilise automated neighbour detection
Identify inconsistent neighbour profiles
Modify appropriate neighbour lists
ptimisation Activities

The neighbouring BCCH carrier analyser in the GSM receiver makes it easier to determine
these alternative neighbours. It can be used to create a list of all the possible BCCH carriers
in the nearby vicinity and perform the RxLev measurement (linked to the phones RxQual
performance) on each of these carriers.

When the RxQual reaches the handover decision threshold, we can determine the potential
neighbours at that stage and set one of those as the optimum neighbour. This can also be
done by the MS, but in this case the choice is limited to the BA list set in the network, which
may not include all good potential neighbours.

Section 8 O
Missing neighbours
Unintentional 1-way neighbour definitions


293

Optimisation includes a combined study of neighbour performance statistics and network
planning data, using automated neighbour detection techniques via A-Bis traces where
supported by the vendors OMC tool set. The neighbour list is reviewed to identify missing,
redundant and 1-way neighbours, and updating of neighbour lists with required changes.

Lack of neighbour maintenance leads to:
Unwanted legacy neighbours
Over-sized neighbour lists (impossible to add neighbours for new sites, and reduced
handover performance)
Co-channel neighbour definitions
Missing neighbours
Unintentional 1-way neighbour definitions

_____________________________________________________________________
16.5 Identify and Fix Frequency Plan Problems

16.5.1 FREQUENCY OPTIMISATION ACTIVITIES

Frequency optimisation activities involve identification of interference issues due to a
poorly-maintained frequency plan, and rectification through a process of coverage
optimisation and frequency plan modifications.

This includes firstly ensuring problem areas have been identified:

Identify interference issues
Identify coverage optimisation issues impacting frequency plan quality (excessive
coverage overlaps, coverage splashes, etc.)

Having ensured that the issues have been identified correctly, optimisation techniques can
be employed to optimise the frequency plan. uch techniques could include:

S
Frequency Optimisation Activities Frequency Optimisation Activities
Identify problem areas:
Interference issues (internal and external)
Coverage issues ( excessive overlaps, coverage gaps, high sites etc)
Recommend appropriate frequency optimisation techniques
BCCH and TCH Frequency Plans
Frequency Diversity (space, polarity)
Frequency Hopping
DTX
Antenna Down tilting
Advanced Optimisation Techniques


294

16.5.2 BCCH AND TCH FREQUENCY PLANS

The Spectrum allocation should be considered to determine if a change to frequency
allocation is necessary. The diagram below shows a typical frequency allocation for the 900
band.

BCCH and TCH Frequency Plans BCCH and TCH Frequency Plans
BCCH is typically planned with low frequency re-use (long re-use
distance) in order to ensure high quality.
The BCCH plan should take into account: site design, terrain and
topography and subscriber distribution. A good BCCH plan can generally
be achieved with 14 - 15 carriers.
The TCH plan requires the same considerations as BCCH, but may also
employ:
Frequency hopping - synthesiser or baseband
Multiple Re-use Patterns - giving tighter re-use on lower TCH layers
Concentric multi-layer cell arrangements in which BCCH is only required on
one band

The number of channels required to make a good BCCH plan will vary according to a
number of factors:

Site design (high sites etc.)
Terrain and topography
Subscriber distribution
Regularity of cell plan

In a well optimised network, it is generally possible to produce a high quality BCCH plan
within 14-15 channels.

The same issues with the BCCH plan also affect frequency planning of the non-BCCH (TCH)
carriers. However there are additional techniques available for the TCH layer to improve re-
use efficiency and increase capacity, such as:

Synthesizer Frequency Hopping
Baseband Frequency Hopping
MRP (Multiple Reuse Pattern)
Concentric Cell


295

BCCH and TCH Frequency Plans BCCH and TCH Frequency Plans
Guard Band Guard Band
BCCH TCH Hopping MICRO
14 ch
26 ch 8 ch
1 ch 1 ch

16.5.3 HIGH SITE REPLACEMENT

In terms of RF design, the problem with this approach is that the legacy sites from the
launch rollout phase tend to be high and prominent, and increasingly contribute uplink and
downlink interference into the network as the number of lower sites around them increases.
The net effect of this is to minimise frequency re-use efficiency and limit the capacity of the
network.
Therefore a process is required to identify and eliminate these interferers to allow network
growth to continue and high quality to be maintained.

A typical process for replacing or modifying high sites would be as follows:

From BSS performance statistics and call trace logs, identify those cells which
contribute the most interference to the largest number of other cells.

Develop a plan for de-commissioning the site, or lowering the antennas to a position
consistent with surrounding sites if possible. Include the possible requirements for
additional in-fill sites due to the loss of coverage from the high site.

As new low sites are integrated, de-commission or modify the high site in such a
way as to cause minimum disruption to coverage. Prioritise the integration of any
required new sites to target high sites in order of severity.


296

High Site Problems High Site Problems
Initial roll-out tends to concentrate on higher sites
High sites potentially cause excessive interference with
subsequent lower site roll-out
A Typical process for replacement could include:
From performance parameters, identify those cell interference-
contributing the most interference to the most cells
Develop plan to lower antennas or decommission these sites. This
may require additional lower sites to cover any coverage gaps
Prioritise decommissioning and integration of new sites to minimise
disruption to services

16.5.4 ANTENNA DOWN-TILTING

Antenna Down Antenna Down- -Tilting Tilting
An option for adjusting cell coverage
e.g. down tilting may direct coverage deeper into a building
Antenna tilt may be:
mechanical operator set affects directional coverage
electrical manufacturer set affects omni-directional coverage
Omni antennas may have electrical tilt but not mechanical
New technologies allow for remote electrical tilting


297

Examples of Antenna Tilting Examples of Antenna Tilting
-35
-30
-25
-20
-15
-10
-5
0
-35
-30
-25
-20
-15
-10
-5
0
-35
-30
-25
-20
-15
-10
-5
0
-35
-30
-25
-20
-15
-10
-5
0
No Tilt
Mechanical
Downtilt
Electrical
Downtilt
Electrical Downtilt +
Mechanical Uptilt

16.5.5 ANTENNA SELECTION

Antenna specifications have a significant impact on network performance. The suitability of
antennas should be reviewed according to the observed performance problems in the
network, and recommendations made as necessary, for example:

Vertical and Horizontal Beamwidth
Gain
Front-to-Back Ratio
Null Fill
Downtilt (electrical/mechanical)


298

Antenna Selection Antenna Selection
Factors to consider with Antenna selection:
Vertical and Horizontal Beamwidth
Gain
Front-to-Back Ratio
Null Fill
Downtilt (electrical/mechanical)

Antenna positioning is also important with respect to minimising interference and
unwanted radiation. This should also be studied in relation to the RF design strategy.

16.5.6 ANTENNA CONFIGURATION OPTIONS

Antenna Configuration Options Antenna Configuration Options
Combining:
Economical with antenna elements
Reduced coverage due to insertion loss
Diversity Choice:
Horizontal space diversity
Vertical space diversity
Polarisation diversity


299


_____________________________________________________________________
17.1 Introduction

The primary functions of the NSS are to:

Provide a transport medium for voice and data circuits across the network.
Provide the signalling functions required to manage network resources effectively

This section of the course describes how these functions are implemented by covering:

typical NSS topology and connectivity
interfaces between NSS entities
the signalling system used within a GSM NSS


300

_____________________________________________________________________
17.2 NSS Topology

17.2.1 TYPICAL PLMN CONFIGURATION

The following diagram shows a typical configuration for a generic GSM network:

GMSC GMSC
MSC MSC
PLMN Configuration PLMN Configuration
HLR HLR
AuC AuC
EIR EIR
MSC MSC
VLR VLR
VLR VLR
BSC BSC
BSC BSC
BSC BSC
BSC BSC
Traffic Links/Link Sets
Signalling Links/Link Sets
Section 9 NSS Characteristics

17.2.2 ALTERNATIVE PLMN CONFIGURATIONS

17.2.2.1 Big-BSC Configuration

Some operators operate a big-BSC configuration where a smaller number of high-capacity
BSC are deployed. Such an approach has a number of advantages:

Large BSC capacity (TRXs/Cells) and areas less signalling load for mobility
management.

Less BSCs lower infrastructure cost and less BSC maintenance staff needed.

Reduced intra BSC handover traffic. Also reduced Intra-MSC handover signalling
traffic bearer capacity requirements when the BSC is collocated with the MSC.


301

Big BSC Configuration Big BSC Configuration

However, this strategy has a number of significant disadvantages:

High transmission costs (please see picture below). In a case of big BSC collocated
with MSC at the same site A-bis interface transmission is cost consuming. For
smaller BSCs not collocated with MSC site only TRAU units remain at MSC site.

Higher risk of VLR overload problems (VLR expansions have to be planned very
carefully). It may occur that although BSC physical connectivity capacity exists (i.e.
new TRXs and new cells may be still connected to BSCs) this becomes limited by the
BSC reconfigurations or BSCs swaps between MSCs are very difficult (due to BSC

Less growth Flexibility. Eventually there will be a requirement for BSC splits when
maximum BSC signalling or traffic capacity of 16 links per link set is reached. The
the
ts.

maximum capacity of MSC/VLR.

Database size).
Less redundancy i.e. less resistance to failures as a greater number of subscribers
would be affected by a single BSC failure.
larger the BSC, the greater the complexity of the splitting process and the larger
additional transmission capacity requiremen


302

17.2.2.2 Transit Switching Layer

An additional Layer of transit switches (TSCs) can be implemented to reduce the potential
for inter-MSC signalling congestion by making the routing more efficient.

Transit Transit Switching Layer Switching Layer
TSC
1a
HLR 2
300k
HLR 3
150k
HLR 4
1200k
HLR 5
600k
HLR 1
600k
TSC
3b
TSC
4b
TSC
3a
TSC
1b
TSC
4a
TSC
2b
TSC
2a
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
IN
GPRS
VMS
SMS
HLR/SMS/VMS/IN
Layer
TSC Layer
MSC Layer

17.2.3 TRANSMISSION LINKS

S ard Transmission links are used to interconnect PLMN nodes for the transport of user
d
l

These format and protocols used on these transmission lines are described in the following
I

G.703
tand
ata and signalling. Within the NSS these are typically 2.048Mbps E1 links (1.544Mbps T1
inks in US) or 64kbps ISDN links, depending on capacity requirements.
TU-T recommendations:
- Physical and electrical characteristics of the interfaces.
G.705 64kbps IDSN-D channel specification.
G.732 Characteristics for primary rate (2Mbps) PCM multiplex equipment.

The physical implementation of these links could be optical fibre or copper leased land lines
or bespoke microwave radio equipments.

17.2.3.1 A Interface Transmission Links

The A interface transmission configuration is defined within the GSM recommendation. At
the physical level it comprises one or more PCM E1 links each with a 2048kbps capacity.


303

Because the Transcoder and Rate Adaptation Unit (TRAU) lies within the A interface and
significantly affects the capacity requirements, the A interface can be divided logically into
two parts:

The BSC TRAU part
The TRAU-MSC part

Between the BSC and the TRAU GSM channel data is compressed and only occupies of
each PCM 64kbps channel. Hence it is possible to multiplex 4 GSM channels onto one PCM
channel. The exception to this is the common-channel signalling channel (TS 16).

Between the TRAU and the MSC GSM channel data is uncompressed and hence one GSM
channel is mapped onto one PCM channel

A Interface Configuration A Interface Configuration
MSC MSC
BSC BSC
fm Trunk 2 n/u TS31 TS30 TS29 30
:
:
:
:
:
:
:
:
:
:
fm Trunk 3 TS20 TS19 TS18 TS17 19
n/u
TS20
TS20
n/u
n/u
n/u
:
:
TS8
TS4
TS4
TS4
31
18
17
16
5
4
15
14
13
:
:
8
3
2
1
0
fm Trunk 3
fm Trunk 1 TS7 TS6 TS5
fm Trunk 1 Trunk 1 TS0 Data
TS31 TS30 TS29
C7 Signalling
:
:
:
:
:
:
fm Trunk 2 Trunk 2 TS0 Data
Frame Alignment
TRUNK 1
TRUNK 2
TRUNK 3
TRUNK 1
TRUNK 2
TRUNK 3
2Mbps E1 Link

17.2.3.2 TRAU Positioning

At some stage the 16kbps channels (13kbps data +3kbps overhead) must be converted into
64kbps for transportation across the PSTN. This function is carried out by a network
ement known as the Transcoder and Rate Adaption Unit (TRAU).
els

herefore, when making a MS-to-MS call, the originating channel has to be converted from
16kbps to 64kbps, switched by the MSC and then converted back to 16kbps for onward
ansmission to the destination MS. The rate conversion is carried out using A-law coding.
el

The primary function of the TRAU is to convert 16kps (inc signalling) GSM speech chann
to 64kbps PCM channels in the uplink direction and the reverse in the downlink direction.
The reason this process is necessary is because MSCs only switch at the 64kbps channel
level.
T
tr


304

Technically, the TRAU can be physically located in the BTS, BSC or MSC and hence leads to
a

variety of installation configurations.
TRAU Configurations TRAU Configurations
BTS Site BTS Site
BSC Site BSC Site MSC Site MSC Site
TRAU
BTS Site BTS Site
CCU
CCU
BTS Site BTS Site
CCU
CCU
A A
B B
C C
A A
bis bis
U U
m m
A A
MSC Node MSC Node BSC Node BSC Node CCU Channel Coding Unit Channel Coding Unit
TRAU
TRAU
16kbps 16kbps
16kbps 16kbps
16kbps 16kbps 16kbps 16kbps
64kbps 64kbps
64kbps 64kbps
64kbps 64kbps
64kbps 64kbps
16kbps 16kbps
CCU
CCU

If the TRAU is installed at the BTS, each 16kbps GSM channel would need to be mapped to
its own 64kbps PCM channel. This results in 75% of the transmission bandwidth being
wasted across both the Abis (BTS-BSC) and A (BSC-MSC) interface.

However, if the TRAU is placed at the MSC, as is generally the case in current networks, a
m ltiplexer can be placed at the BTS which enables 4 x 16kbps GSM channels to be
multiplexed onto one 64kbps PCM channel, using 4 x 16kbps ISDN D-channels.

I , only at arrival at the MSC is the 16-64kbps channel conversion
necessary imising the efficient usage of the transmission medium by increasing
the G

Also, by s
the netw

17.2.3.3 Intra-NSS Transmission Links
u
n this configuration
, thereby max
SM channel throughput per PCM 2048 bearer from 30 to 120 channels.
centralising the TRAU function at the MSC, the number of TRAUs deployed acros
ork is significantly reduced.

Transmission links between NSS entities are usually operator-dependent and comprise a
comb a
Freque t provided by a third-party carrier and therefore the operator only
sees the channels presented to them in the quantity required, not the actual implementation.

in tion of leased and operator-owned lines.
n ly, these links are


305
However, provisioning of inter-NSS entities i rally in the form of one or more E1/T1
32-channel PCM links. Where more than one such link is provided between two entities (for
increased capacity purposes), it is referred to as a Link Set

17.2.3.4 Signalling Links and Link Sets
s gene

n be reserved on GSM
bearers specifically for C7 Signalling (see A interface illustration above).

A link set is a group of links between two nodes within the network. With each link set a
number of signalling links can be defined. This is usually 2,4,8 or 16 signalling links.

17.2.4 GSM NSS INTERFACES

The C7 network provides full-duplex connections between C7 signalling points. These
connections form an independent signalling network, which is overlaid over the GSM voice
ircuit network. In practical implementation, individual channels ca c
transmission

17.2.4.1 A Interface (BSC-MSC)

The interface between the MSC and its BSS is specified in the 08-series of GSM Technical
Specifications. The BSS-MSC interface is used to carry information concerning:

BSS management;
call handling;
mobility management.

GMSC GMSC
MSC MSC
PLMN Interfaces PLMN Interfaces
HLR HLR
AuC AuC
EIR EIR
MSC MSC
VLR VLR
VLR VLR
A A
C C
C C
F F
F F
B B
B B
H H
D D
D D
E E
A A
A A
A A
G G
E E
E E
BSC BSC
BSC BSC
BSC BSC
BSC BSC


306

17.2.4.2 B Interface (MSC - VLR)

The VLR is the location and management data base for the mobile subscribers roaming in
the area controlled by the associated MSC(s). Whenever the MSC needs data related to a
given mobile station currently located in its area, it interrogates the VLR. When a mobile
station initiates a location updating procedure with an MSC, the MSC informs its VLR
which stores the relevant information.

This procedure occurs whenever an MS roams to another location area. Also, when a
subscriber activates a specific supplementary service or modifies some data attached to a
service, the MSC informs (via the VLR) the HLR which stores these modifications and
updates the VLR if required.

17.2.4.3 C Interface (HLR - MSC)

The Gateway MSC must interrogate the HLR of the required subscriber to obtain routing
information for a call or a short message directed to that subscriber.

17.2.4.4 D Interface (HLR - VLR)

This interface is used to exchange the data related to the location of the mobile station and to
the management of the subscriber. The main service provided to the mobile subscriber is the
capability to set up or to receive calls within the whole service area. To support this, the
location registers have to exchange data.

The VLR informs the HLR of the location of a mobile station managed by the latter and
provides it (either at location updating or at call set-up) with the roaming number of that
station. The HLR sends to the VLR all the data needed to support the service to the mobile
subscriber. The HLR then instructs the previous VLR to cancel the location registration of
this subscriber. Exchanges of data may occur when the mobile subscriber requires a
particular service, when he wants to change some data attached to his subscription or when
some parameters of the subscription are modified by administrative means.

17.2.4.5 E Interface (MSC MSC)

When a mobile station moves from one MSC area to another during a call, a handover
procedure has to be performed in order to continue the communication. For that purpose
the MSCs have to exchange data to initiate and then to realize the operation. After the
handover operation has been completed, the MSCs will exchange information to transfer A-
interface signalling as necessary. When a short message is to be transferred between a
Mobile Station and Short Message Service Cent e (SC), in either direction, this interface is
used to transfer the message between the MSC serving the Mobile Station and the MSC
which acts as the interface to the SC.

17.2.4.6 F Interface
r
(MSC - EIR)

This interface is used between MSC and EIR to ta, in order that the EIR can
v

exchange da
erify the status of the IMEI retrieved from the Mobile Station.


307

17.2.4.7 G Interface (VLR VLR)

When a mobile subscriber moves from a VLR area to another Locati
procedure will happen. This procedure may include the retrieval of t
on Registration
he IMSI and
uthentication parameters from the old VLR.

17.2.4.8 H Interface
a
(HLR - AuC)

the HLR requests the data from the AuC.
he protocol used to transfer the data over this interface is not standardized.

17.2.5 SIGNALLING WITHIN THE GSM NETWORK
When an HLR receives a request for authentication and ciphering data for a Mobile
Subscriber and it does not hold the requested data,
T

ignalling within the GSM Network falls into two categories. Within the BSS and down to
MSs, GSM-specific signalling is used. However, across the BSC-MSC interface (A interface)
and within the NSS, the C7 signalling standard is used. This section of the course looks
specifically at the C& signalling implementation within the NSS.

The C7 signalling requirements fall into three sub-categories:

User Data

S
. For user data signalling requirements, the C7 ISDN User Part (ISUP)
protocol is used.
Intra-NSS Signalling. -For intra-NSS specific signalling (i.e. between MSCs, VLR,
HLRs etc), the C7 Mobile Application Part (MAP) protocol is used. This protocol is
responsible for such functions as updates, enquiries, handover transactions etc
between MSCs and MSC-VLR or HLR.
A Interface Signalling. For the BSC-MSC interface the BSS Application Protocol
(BSSAP) is used.

Network Signalling Requirements Network Signalling Requirements
BSC to MS GSM-specific Signalling
BSC to NSS C7 Signalling:
User Data Connections:
ISDN User Part (ISUP)
Inter-NSS Node Signalling:
C7 Mobile Application Part (MAP)
A Interface Signalling:
tion Part (BSSAP)
l Layers
Message Transfer Part (MTP)

C7 BSS Applica
Physica


308

C7 Network
GMSC GMSC
MSC MSC
nterfaces terfaces C7 Signalling C7 Signalling PLMN I PLMN In
HLR HLR
AuC AuC
EIR EIR
MSC MSC
VLR VLR
VLR VLR
A A
C C
C C
F F
F F
B B
B B
H H
D D
D D
E E
A A
A A
A A
G G
E E
E E
BSC BSC
BSC BSC
BSC BSC
BSC
acteristics

____________
17.3 Overview of C7 Signalling in the NSS

17.3.1 BRIEF OVERVIEW OF GENERIC C7
Section 9 NSS Char
BSC
_________________________________________________________

Within a GSM network, signalling is used to carry out a number of functions including
setting up and clearing connections between end-user terminals.

The signalling standard adopted by ETSI for GSM is Common-Channel Signalling System
Number 7, known as C7 in Europe and SS7 in the USA.

In generic terms, a C7 network comprises a number of Signalling points (SPs).
An SP is defined as a network node where processing of messages addressed to that SP is
allowed.

SPs are either directly connected or interconnected through Signalling Transfer Points
(STPs). STPs may or may not have the functionality of an SP but, by definition, must have
the capability to relay C7 messages without interpretation.


Generic SS7 Network Generic SS7 Network
SP
SP
SP
SP
STP
STP
SP
STP
STP
SP
SP
SP
SP

In a GSM Network, MSCs and BSCs fall into the category of SPs. C7 is used to for inter-
nodal signalling both on all GSM NSS interfaces and across the MSC-BSC A interface.

17.3.2 C7 WITHIN THE NSS

MSC MSC
C7 C7 in the GSM NSS in the GSM NSS
BSC BSC
HLR HLR
AuC AuC
EIR EIR
BSC BSC
BSC BSC
BSC BSC
MSC MSC
VLR VLR
VLR VLR
SP
SP
SP
SP
SP
SP
SP
SP
SP
STP
STP

17.3.3 SIGNALLING OVER THE A INTERFACE
309


310

Over the A Interface, GSM uses C7 signalling with protocol extensions for GSM-specific
requirements.

MTP 1-3
A Interface Signalling A Interface Signalling
SCCP
DTAP
BSSMAP
User Data User Data
BSSAPP BSSAPP
Layer 1 Layer 1- -3 3

The C7 part of the A interface signalling comprises:

Mobile Transfer Part (MTP). The MTP is the C7 protocol responsible for secure routing
and transport of signalling messages. In the GSM network, a modified version of MTP,
known as MTP is used over the A interface for this purpose.

Signalling Connection Control Part (SCCP). For Mobility Management (MM) and
Connection Management (CM) signalling transactions over the A interface it is
necessary to establish distinct logical signalling connections. SCCP is responsible for
this function, used a reduced C7 functionality range.

The GSM-specific part of the A interface signalling comprises:

BSS Application Part (BSSAP). The BSSAP has been implemented to provide for GSM-
specific signalling between the BSC and MSC. The protocol comprises two parts:

Direct Transfer Application Part (DTAP). The DTAP is responsible for transporting
GSM-specific MM and CM messages between the MS and MSC. These messages are not
processed by the BSC and are therefore relayed transparently.

BSS Mobile Application Part (BSSMAP). The BSSMAP is the part of the protocol
responsible for the administration and control of the Radio Resources (RR) within the
BSS that are the responsibility of the MSC. These include, some handover procedures,
channel allocation and release etc. RR messages invoke BSSMAP functions and
BSSMAP functions control the RR protocol functions.


BSS Mobile Application Part (BSSMAP)
All messages exchanged between BSC and MSC processed by
the BSC
Direct Transfer Application Part (DTAP)
Message protocol for direct transfer of MM/CM Layer 3 messaging
between the MSC and the MS
Transparent to the BSS
Signalling Connection Control Part (SCCP)
Logical signalling connection between MSC and MS to support
Layer 3 (MM/CM) message transfers
Uses reduced set of C7 signalling instructions
Message Transfer Part Layers 1-3 (MTP 1-3)
Responsible for routing and transport of signalling messages
A Interface Signalling Protocols A Interface Signalling Protocols

17.3.4 SIGNALLING BETWEEN NSS ENTITIES

A number of interfaces have been defined for interconnections between NSS entities. These
have been described briefly in a previous part of this section. Over the A Interface, GSM
uses C7 signalling with protocol extensions for GSM-specific requirements.

MTP
SCCP
TCAP
MAP
NSS Interface Signalling NSS Interface Signalling
HLR
Layers 4 Layers 4- -6 6
MSC MSC VLR
E E
C C
B B
D D
Layer 3 Layer 3
Layers 1 Layers 1- -2 2
Layer 7 Layer 7
C7 Protocol Stack C7 Protocol Stack
EIR
F F

311


312

Mobile Application Part (MAP)
Mobile-specific extension of C7 standard.
All messages exchanged between NSS Elements (MSC,HLR,VLR)
Transaction Capabilities Application Part (TCAP)
A connectionless transport service provided by the SCCP
Allows its users to access other users via worldwide C7/SS7 network
Logical signalling connection between MSC and MS to support Layer 3
transfers
Uses reduced set of C7 signalling instructions
er Part (MTP)
esponsible for routing and transport of signalling messages
NSS Interface Signalling Protocols NSS Interface Signalling Protocols

Provides core functionality to support roaming
Signalling Connection Control Part (SCCP)
(MM/CM) message
Routes messages via STPs
Message Transf
C7 protocols r

10. NSS Parameter Evaluation and Optimisation


313

18. NSS Optimisation and Parameter
Evaluation

_____________________________________________________________________
18.1 Introduction

This section of the course describes optimisation issues related to the NSS. This
includes:

A review of the NSS optimisation process
Signalling routing and capacity analysis
Traffic loading
NSS-specific parameters
NSS database evaluation


314

__ _______________________________________
18.2 NSS Optimisation Process

A generic approach to the NSS optimisation process would include the following phases:

____________________________
NSS Optimisation Process NSS Optimisation Process
NSS Data Capture
Phase
Data Analysis Phase
Define Optimisation
Requirements
Define Implementation
Strategy
Optimisation Activity
Phase

18.2.1 DATA CAPTURE PHASE

NSS Data Capture Phase NSS Data Capture Phase
Available Data:
C7 signal routing
C7 link loading
User traffic routing
Trunk group configuration and loading
Database loading

NSS configuration parameters



315
Signalling information both routing and loading
User Traffic Routing
Trunk Groupings both configuration and loading
NSS Parameter Configurations
Database loading

18.2.2 NSS Data Analysis Phase

Typical network information the needs to be captured for evaluation includes:

NSS NSS Data Analysis Data Analysis Phase Phase
STEP 1
Organise collected data into functional areas
STEP 2
Validate organised data
STEP 3
Evaluate validated data

During the NSS evaluation phase, the data previously captured is:

es.
corporated that could invalidate the
evaluation
Evaluated to identify if any areas of concern exist regarding NSS performance.

1
Organised into subject areas for reporting purpos
Validated to ensure no spurious readings are in
8.2.3 NSS Optimisation Phase

N s throughout the whole network life cycle.
T work quality is maintained. However, on
nsure

SS optimisation should be an ongoing proces
his ensures that efficient resource usage and net
occasions it is useful to carry out a full audit of the network performance in order to e
there is no gradual degradation occurring.

316

uate capacity is being
provided 2 Mbps links (in particular adding additional C7 links to the link sets,
creating new link sets, deleting some links sets, etc).
Increasing VLR/HLR capacity expansion or BSC swaps between MSCs if needed to
evenly distribute subscriber records
H/W expansion of network elements if needed (for higher capacity).
New network elements implementation proposal to fulfil traffic/VLR requirements.
Redesign of MSC/BSC Location Areas.

Common changes that could be implemented include:

Modification of existing traffic and signalling routing strategies.
Implementation of C7 signalling network-wide where it does not already exist.
Reconfiguration of C7 and trunk links/link sets to ensure adeq
NSS Optimisation Phase NSS Optimisation Phase
STEP 1
Review areas of concern identified as part of
the Validation Phase
STEP 2
Identify optimisation techniques suitable for
improving poorly performing areas

18.2.4 NSS Implementation Phase

Having identified areas where optimisation is necessary, changes must be
carefully planned to ensure that sufficient time and resources are available,
and that activities are de-conflicted.


317

NSS Implementation Phase NSS Implementation Phase
Plan the implementation of optimisation
procedures
Ensure sufficient time/manpower/equipment
resources are available of the right time
De-conflict potentially conflicting procedures
Identify monitoring procedures/periods required
to assess performance changes

18.2.5 NSS Optimisation Activity Phase

Optimisation activities identified during the Evaluation Phase are implemented in
accordance with the plan determined during the Implementation Phase.
Each activity must be carefully monitored to ensure further problems are not created and
the predicted performance improvements materialise.

NSS Optimisation Activity Phase NSS Optimisation Activity Phase
Implement optimisation procedures:
as identified during the Optimisation Phase
in accordance with the plan designed during the
Implementation Phase
monitored as agreed during the Implementation
Phase


318

_____________________________________________________________________
18.3 C7 Signal Routing Analysis

18.3.1 SIGNAL ROUTING EVALUATION

Routing Evaluation Routing Evaluation
Check for:
Main and alternate routing
Consistent implementation of routing strategy
Effective use of transit switches (where used)

The first step in analysing C7 routing is collecting data from all C7-related network
elements. This information is then studied to identify the following:

main and at least one alternate signalling paths for each signalling destination.
presence of any C7 routing circles
consistency of C7 routing strategy
effective usage of transit switches (C7 STPs) in the network

Presence of routing circles


319

18.3.2 MAIN AND ALTERNATE ROUTING

Routing Analysis Routing Analysis M Main and Alternate Routing ain and Alternate Routing
a minimum of a main and alternate route,
few routes can cause loss of signalling
inefficient and overly-complex to
manage

18.3.3 ROUTING CIRCLES
Each signalling destination should be reachable by
particularly HLR connections
Too
messages
Too many routes is

This is also known as Tromboning Three MSCs, A, B and C are all connected together. The
second choice route from MSC-A to MSC-C is via MSC-B and the second choice route from
MSC-B to MSC-C is via MSC-A.

Routing Analysis Routing Analysis Routing Circles Routing Circles
Also known as tromboning
A
C B
A-C Main / B-C Main
A-C Alternate
B-C Alternate
A-C and B-C Fail
A routes via B to C
B routes via A to C
A routes back to B


320
All transmission to and from MSC-C fails. A call from MSC-A to MSC-C is routed to MSC-B.
MSC-B finds its route to MSC-C has failed and takes it second choice route which is back to
MSC-A which it turn routes the call back to MSC-B.

In a fraction of a second all routes from MSC-A to MSC-B are full as the one call goes
backwards and forwards

18.3.4 ROUTING STRATEGY CONSISTENCY

Routing Analysis Routing Analysis Strategy Consistency Strategy Consistency
Strategy for signal routing should be consistent
in order to:
Spread traffic loads evenly across the network
Increase reliability

18.3.5 TRANSIT SWITCHING
Optimise signalling link resources
Ease engineering by applying a consistent approach
Simplify future growth planning

Transit Switching Layer Transit Switching Layer
TSC
1a
HLR 2
300k
HLR 3
150k
HLR 4
1200k
HLR 5
600k
HLR 1
600k
TSC
3b
TSC
4b
TSC
3a
TSC
1b
TSC
4a
TSC
2b
TSC
2a
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
MSC
IN
GPRS
VMS
SMS
HLR/SMS/VMS/IN
Layer
TSC Layer
MSC Layer
MSC


321

Routing Analysis Routing Analysis Transit Layer Switches Transit Layer Switches
Transit Layer switching provides an additional
layer of switching that makes signal routing
more efficient
Signalling traffic should be evenly distributed
across TSCs in TSC layer
If TSCs are used, MSCs should not be used
as STPs as this reduces MSC and SS7
performance

18.3.6 POSSIBLE ROUTING PROBLEMS

Possible Routing Problems Possible Routing Problems
Lack of uniformally implemented routing strategy:
Number of primary/secondary/tertiary routes
Inconsistent Routing parameters
Excessive signal loading on routes
Lack of alternate routing to key network elements
Signalling errors due to routing circles
Too many routes defined uneven spreading of load


322
The final result of this network study could identify a number of potential problems in the
signalling network:

Lack of clear and uniformally-implemented routing strategy e.g.
nd tertiary routes required
Maximum signal loading per link
Inconsistent routing parameters
Lack of alternate signalling routes to key network elements (e.g. HLRs)
Signalling errors due to routing circles
Too many signalling routes defined

_____________________________________________________________________
18.4 Signalling Link Load Evaluation

18.4.1 MONITORING SIGNALLING LOADS
Number of primary, secondary a

C7 Signalling Links:
Signalling links are logically independent of voice traffic links
Links are full-duplex
Periodicity of Monitoring:
Carried out at least monthly (preferably weekly)
Carried out on significant network configuration change
Recommended Capacity:
ITU Q.706 specifies maximum of 200mE per link in each direction
May be exceeded temporarily but is not recommended
Calculation:
Signalling Load [ mErl] = (Number of MSU * 6 + Number of octets of payload)
( 8 * length of time in seconds)
Monitoring Signalling Loads Monitoring Signalling Loads

In an evolving GSM network the load on the signalling links will change constantly. It is
important that these changes are constantly monitored in order to identify points of
potential congestion so that action can be taken to avoid such congestion before it becomes a
problem.

General signalling loads should be measured a regular basis the frequency depending on
network reconfigurations have taken place (for example implementation of new
MSC/TSC/HLR) these areas should be monitored more regularly to assess link state loads
resulting from the new configuration.

the activity changes in the C7 network. At least monthly evaluation of network signalling
load is recommended, although weekly is preferable if resources permit. If significant


323

As a C7 signalling link is a full duplex connection, loading is assesses in each direction.
Therefore the maximum loading of a link is as defined in each direction, not the sum of the
The link load for each C7 signalling link may be calculated according to the following
formula:

Signalling Load [ mErl] = (Number of MSU * 6 + Number of octets of payload)
two (refer to E733/7.1 for details)

( 8 * length of time in seconds)

18.4.2 RECOMMENDED LOAD VALUES FOR C7 SIGNALLING LINKS
endation specifies a maximum planning load of 200 mErl in each
direction on a C7 link. In practice the signalling links may temporarily maintain higher
traffic volume than the recommended (e.g. up to 400mErl per Tx/Rx direction) for example,
during emergency re-routing although this should be avoided where possible.

18.4.3 LINK LOAD SHARING

The ITU-T Q.706 Recomm

rectly dimensioned
Changes to the original network conditions have caused a change in signal loading

ling traffic measured on the signalling links of a link set
network.
Unequal load sharing on signalling links can occur when:

Signal loading was not cor
The following table shows signal
between TSC1 and HLR1 in a live

Signal Load Evaluation Signal Load Evaluation Link Load Sharing Link Load Sharing
Excessive link loads can occur
when:
Original signal load d
not correct
Tx [mErl] Rx [mErl]
Link
No Destination
C7 Load C7 Load TSC1
imensioning was
Network characteristics have changed
Ideal Situation:
Links should not exceed 200mE
should be spread
l links in link set
102 104 9
89 103 8
109 104 7
94 104 6
91 312 5
76 302 4
84 303 3
127 305 2
134 307 1
121 305 0
HLR1
Signalling traffic
evenly across al


324

It can be seen that more than half the Rx links indicate signal loading in excess of the
r of the Rx links are under-utilised. The
clearly scope here for redistribution of
the Rx signalling load to ensure individual links do not become overloaded.

18.4.4 LINK LOAD SHARING
recommended 200mE threshold, while the remainde
Tx links show a reasonable loading spread. There is

In an ideal situation, the volume of incoming MSUs should approximate to the number of
outgoing MSU for good symmetrical loading. This should be true for both individual links
and link sets where possible.

Signal Load Evaluation Signal Load Evaluation Link Load Symmetry Link Load Symmetry
Ideal Situation:
Individual links should not exceed
200mE
Tx/Rx loads should be as symmetrical
as possible
Benefits:
Simplified routing
More efficient bearer usage
437 19 1
483 15 0 MSC3
Reduces risk of lost MSUs
Reduced risk of signalling loops
Tx [mErl] Rx [mErl] Link No Destination
C7 Load C7 Load TSC1

The table above serves as an example of unbalanced signal loading between a TSC and an
MSC in a live network. The Rx side of the two signalling links shown is relatively unused
whereas the Tx side is overloaded (exceeding the 200mE threshold). Inefficient usage of C7
links is wasteful of C7 hardware resources.

This ideal symmetrical configuration, together with ensuring maximum recommended

reduces the risk of lost MSU
reduces the risk of signalling loops being created.
More efficient bearer utilisation due to equal load Tx/Rx volume spreading

thresholds are not exceeded, has the following benefits:
simplified routing


325
18.4.5 NODAL MSU CAPACITY

It is generally recommended by all mobile vendors that nodal MSU capacity does not exceed
1500-2000 MSUs per second.

As mentioned previously, the number of incoming and outgoing MSUs of the network node
should remain at the same level. The graph below illustrates the total number of MSUs per
network node at peak hour measured in a live network.

Total MSU per sec
0
L
R
1

(
R
a
h
a
h
a
n
)
L
R
2

(
R
a
h
a
h
a
n
)
M
S
C
E
M
A
M
M
S
C
K
J
M
S
C
R
A
M
S
C
S
B

A
l
g
h
a
d
i
r

M
S
C
H
L
R
3

(
B
H
)
M
S
C
B
E
H
M
S
C
F
A
R
M
S
C
L
C
T
H
L
R
5

(
E
m
a
m
500
1000
1500
2000
4000
4500
5000
H H
2500
3000
3500
M
S
U

p
e
r

s
e
c
Tx
Rx
)
L
C
T
T
S
C
1
E
M
A
M
T
S
C
1
M
S
C
K
A
N
F
A
T
E
H
M
S
C
Exchange
Recommended Value per Node
H
L
R

1
H
L
R

2
M
S
C
1
M
S
C
2
M
S
C
3
M
S
C
4
M
S
C
5
H
L
R
3
M
S
C
6
M
S
C
7
M
S
C
8
H
L
R
4
T
S
C
1
T
S
C
2
M
S
C
9
M
S
C
1
0
Signal Load Evaluation Signal Load Evaluation Nodal MSU Capacity Nodal MSU Capacity
Recommended Nodal MSU Capacity <= 1500 MSUs/second

ure rate and due to the VLR capacity saturation of that
be the existence of a C7 signalling loop.

_____________________________________________________________________
n

18.5.1 TRUNK MEASUREMENTS

It can be seen that MSC6 and TSC2 indicate the highest MSU volume. High load of MSC6
may be the result of the high LUP fail
MSC. Another reason may

18.5 Traffic Loading Evaluatio

In order to evaluate traffic loading within the NSS, a number of parameters need to be
monitored and the figures obtained evaluated. Two of the areas that require analysis within
the NSS. These are:

Trunk Capacities:
between the PSTN and PLMN
between the PLMN and PSTN
within the PLMN
Answer Bit Ratio (ABRs) across the PLMN.


326
Statistics should be gathered from each switch over periods throughout the day. The level
A minimum of two 1-hours periods should be monitored during each day (e.g. ) detailing
the traffic on all the trunks connected to that switch.

of monitoring will be dependant upon resources available.

Traffic Load Measurement Requirement Traffic Load Measurement Requirement
Recommended twice-daily 1-ho
periods
ur measurement
intervals to
assess capacity on each link
Between MSCs within the PLMN
From PLMN to PSTN
From PSTN to PLMN

Data gathered from MSCs at regular
Trunk capacities assessed:

18.5.2 TRAFFIC LOAD DATA

Traffic Load Data Capture Traffic Load Data Capture
Data captured should include:
Number of trunk available on each traffic link
Level of traffic (erlangs) on each link during
the busy hour
Answer Bit Ratio (ABR) measured on each
link during the busy hour


327

The data gathered for trunk traffic loading should include:
amount of traffic (in Erlangs) being generated on each link during the
measurement period.
The Answer Bit Ratio (ABR) and Answer Seize Ratio (ASR) on each link during the
busy hour

18.5.3 TRAFFIC LOAD ANALYSIS

The number of trunks available on each traffic link(
The

This data gathered should be analysed to identify:

The number of trunks required for the traffic (in Erlangs) being generated on that
link.
Any differences between number of trunks required and number installed and in-
service.
The utilization figure for each trunk group.

Traffic Load Analysis Traffic Load Analysis
Analysis of the measured data should include:
Calculation of number of trunk required to support
traffic on link
Any difference between trunks required and trunks
available
trunk

18.5.4 RECOMMENDED TRAFFIC LOAD THRESHOLDS
Utilisation Factor for each

Recommended thresholds for the measured values are:

Maximum trunk utilisation = 75%
Max Erlangs per trunk =0.7e
GOS = 1%


328
Recommended Traffic Parameters Recommended Traffic Parameters
Maximum erlangs per trunk = 0.7e
Maximum utilisation factor per trunk = 75%
GOS = 1%

The trunk utilisation figure of 75% could be considered somewhat low but is based on
18.5.5 EXAMPLE TRUNKING CAPACITY MEASUREMENTS
allowing capacity for future expansion.

The following table shows some measurements taken as part of a trunk capacity analysis
exercise in a live network using the method described above. Note that only trunk
utilisation in excess of 75% has been included in the tables.

NSS Traffic NSS Traffic Trunk Trunk Utilisation Utilisation
180 84% 1280 1250.2 58% 98,192 1527 11-12 5
373 95% 1311 1281.3 58% 104,514 1375 11-12 4
34 87% 183 162.7 32% 12,324 210 11-12 3
5 77% 139 120.9 51% 6,783 180 11-12 2
154 83% 1207 1177.2 46% 128,394 1455 11-12 1
Required Utilisation Reqd Erlangs ABR% Attempts Trunks Time Trunk Gp
Trunks Trunk Trunks Total NSS NSS Call
Addit.
GoS = 1% Max Erlangs/trunk = 0.7 Only trunk utilisation > 75% shown



329

____________________________________________________________________
18.6 NSS Parameter Evaluation

18.6.1 PURPOSE OF PARAMETER ANALYSIS

Parameters are an important source of network performance data. They are used to define
operating functions within the network and also allow network controllers to modify
network functions to suit localised situations or certain events.

Since parameters have a direct impact to the operation and performance of the system itself,
it is essential that all parameters are correctly set and monitored in order to ensure the
network continues to operate in effective and efficient manner.

Network Parameter Analysis Network Parameter Analysis
Parameters control equipment operation and
performance
Initial parameters determined at network planning
stage
Parameter sets should remain common where
possible to facilitate efficient network management
Parameters may require modification to suit local
conditions.
Periodic operation and performance monitoring
necessary to ensure parameters remain valid

Parameter analysis will improve the utilisation of the network resource by proper setting
which helps shorten the call setup time as well as reduce some unnecessary traffic loading
For the purposes of this course, NSS parameters will be divided into two parts:

VLR parameters

over the network.

PLMN parameters

330

Parameter Analysis Parameter Analysis VLR Parameters VLR Parameters
Fax gr.3 and Alternate Speech (T61)/ Automatic fax group 3 (T62)
Short Message Mobile Terminated (T21)/Originated (T22)
TELESERVICE SUPPORT
Call Barring
Advice of charge charging (AOCC)
Call Hold (HOLD)
Call Waiting (CW)
Call Forwarding
Calling Line Identification Presentation (CLIP)
SUBSCRIBER SERVICES SUPPORT
Minimum Amount of Triplets to be kept on record (MINT)
VLR Cleaning Start Time (for Siemens If capacity above 80%)
Call Waiting Time Limits
Implicit IMSI Detach Time Limit Time
Emergency Call
Implicit Detach Usage
Authentication Usage
TMSI Usage
SUBSCRIBER PROFILE

s respectively.

18.6.2 MSC TMSI PARAMETER

Appendixes D and E provide examples and recommendations for these two sets of
parameter

Parameter Analysis Parameter Analysis TMSI Parameters TMSI Parameters
Advantages of TMSI usage:
Increases paging channel (PCH) capacity
Reduces VLR/HLR signalling requirement
Provides greater security than using IMSI only
TMSI should be unique within a LA
New TMSI issued on change of LA
TMSI allocation/update occurrences set by Operator
Too many TMSI update occurrences increases signalling
capacity requirements
Use of TMSI should be uniform across network


331

18.6.2.1 Advantages of Using TMSIs

es for details).

The use of TMSI also reduces signalling requirements within the NSS. If only IMSIs are in
use, security triplets (for authentication and encryption purposes) must be requested by the
MSC from the HLR. As TMSIs are associated with VLRs, their use allows the same triplets
to be generated within the VLR associated with the MSC.

18.6.2.2 TMSI Allocation Parameters
The use of TMSIs increases paging capacity (i.e. reduces paging signalling load) on air
interface, because one paging message can contain four TMSIs, rather than only two IMSIs
(see the Paging in Section 1 of these not

Parameter Analysis Parameter Analysis TMSI Parameters TMSI Parameters
N Mobile SS Operation
N Mobile Terminating USSD
N Mobile Terminating SMS
N Mobile Terminating Call
N Mobile Originating SMS COUNTERS
N Mobile Originating Call ALLOCATION
N Periodic Location Update TMSI
Y Location Update
Y IMSI Attach
Y Location Update New Visitor
REC PARAMETER

IMSI Attach
If set to Y, new TMSI allocated on every IMSI attach.
(Recommended Y)

Location Update
If set to Y, new TMSI allocated on every location update.
(Recommended Y)

Location Update New Visitor
If set to Y, new TMSI allocated when accessing a PLMN as a visitor.
(Recommended Y)

Periodic Location Update
If set to Y, new TMSI allocated on every periodic location update.
(Recommended N)

Mobile Originated (MO) Call Update


332
If set to Y, new TMSI allocated on every MO call.
(Recommended N)

Mobile Originated (MO) SMS Update
If set to Y, new TMSI allocated on every MO SMS.

Mobile Terminated (MT) Call Update
(Recommended N)

If set to Y, new TMSI allocated on every MT Call.
(Recommended N)

Mobile Terminated (MT) SMS Update
If set to Y, new TMSI allocated on every MT SMS.
(Recommended N)

Mobile Terminated (MT) USSD Update
If set to Y, new TMSI allocated on every MT USSD connection.
(Recommended N)

n Update Mobile SS Operatio
allocated every time a Supplementary Service (SS) is activated.

TICATION ACTIVATION PARAMETERS
If set to Y, new TMSI
(Recommended N)
18.6.3 AUTHEN

Parameter Analysis Parameter Analysis Authentication Parameters Authentication Parameters
Advantages of Authentication usage:
Increases security of network
Implementation of Authentication is an Operator decision
Can be implemented internally to network and/or for
roaming subscribers
Excessive Authentication increases signalling capacity
requirements
Use of Authentication should be uniform across network


333
18.6.3.1 Authentication Usage

Authentication is the process by which a security check is carried out on a subscriber prior
to accessing the network. This is operator-dependent and is defined by the security
operating procedures of that operator.

Whilst providing greater security to the network, it does introduce additional signalling
loads on the network

Parameter Analysis Parameter Analysis Authentication Parameters Authentication Parameters
N Mobile Terminating Call
N Mobile Originating SMS
N Mobile Originating Call
N Periodic Location Update COUNT
N Location Update AUTHENTICATION
Y IMSI Attach
REC
PARAMETER

18.6.3.2 Authentication Activation Parameters

If set to Y, new authentication takes place when accessing a PLMN as a visitor.
(Recommended Y)

IMSI Attach
If set to Y, new authentication takes place on every IMSI attach.
(Recommended Y)

Location Update
If set to Y, new authentication takes place on every location update.
(Recommended N )

If set to Y, new authentication takes place on every periodic location update.
(Recommended N)

If set to Y, new authentication takes place on every MO call.
(Recommended N)


334

If set to Y, new authentication takes place on every MO SMS.
(Recommended N)

If set to Y, new authentication takes place on every MT Call.
(Recommended N)

If set to Y, new authentication takes place on every MT SMS.
(Recommended N)

If set to Y, new authentication takes place on every MT USSD connection.
(Recommended N)

Mobile SS Operation Update
If set to Y, new authentication takes place every time a Supplementary Service (SS) is
activated. (Recommended N)

18.6.4 IMEI CHECKING PARAMETERS

Parameter Analysis Parameter Analysis IMEI Parameters IMEI Parameters
Advantages of IMEI usage:
Increases security of network
Enables tracing/monitoring of Grey/Black-listed MSs
Implementation of IMEI checking is an Operator decision
Can be implemented internally to network and/or for
roaming subscribers
Excessive IMEI checking increases signalling capacity
requirements
Use of IMEI checking should be uniform across network

18.6.4.1 IMEI Usage

IMEI checking is the process by which a security check is carried out on handset equipment.
The IMEI can be checked against the Equipment Identity Register (EIR) which stores IMEIs
in one of three states:

White No restrictions
Grey Additional checks may be required
Black access should be blocked


335

This is operator-dependent and is defined by the security operating procedures of that
operator.

Whilst providing greater security to the network, it does introduce additional signalling
loads on the network

18.6.4.2 IMEI Check Activation Parameters

Parameter Analysis Parameter Analysis IMEI Check Parameters IMEI Check Parameters
BLOCK Unknown IMEI Effect
TRACE Grey List Effect
BLOCK Black List Effect
N Mobile Originating SMS
N Mobile Terminating Call IMEI CHECKING ON.
N Mobile Originating Call
N Periodic Location Update
Y(10) Location Update
Y IMSI Attach
REC PARAMETER

IMSI Attach
If set to Y, IMEI checks take place on every IMSI attach.
(Recommended Y)

Location Update
If set to Y, new authentication takes place on every location update.
(Recommended Y every 10
th
location update)

If set to Y, IMEI checks take place when accessing a PLMN as a visitor.
(Recommended Y)

If set to Y, IMEI checks take place on every periodic location update.
(Recommended N)

If set to Y, IMEI checks take place on every MO call.
(Recommended N)


336

If set to Y, IMEI checks take place on every MO SMS.
(Recommended N)

If set to Y, IMEI checks take place on every MT Call.
(Recommended N)

If set to Y, IMEI checks take place on every MT SMS.
(Recommended N)

If set to Y, IMEI checks take place on every MT USSD connection.
(Recommended N)

Mobile SS Operation Update
If set to Y, IMEI checks take place every time a Supplementary Service (SS) is activated.
(Recommended N)

18.6.5 MSRN LIFETIME

18.6.5.1 Using MSRN Lifetime Function

MSRN allocated by VLR for incoming call routing
Temporary Assignment
After call is connected, MRSN released back to
VLR for future use.
MSRN Lifetime refers to the time between MSRN
allocation and being releasing back to the network
Typical life times are:
Local Subscribers: 20 secs
Visiting Roaming subscribers: 90 secs
NSS NSS MSRN Lifetime MSRN Lifetime

The Mobile Subscriber Roaming Number (MSRN) is a temporary, location-dependent ISDN
number. It is assigned by the VLR to each mobile in its area and is used for routing calls to
tan MS in that area.


337

It is assigned in one of two ways:

When an MS enters a new LA then passed to the HLR.
When an HLR requests the MSRN for setting up an incoming call.

18.6.5.2 MSRN Lifetime Function Values

As the MSRN is allocated temporarily, its lifetime is time-dependent. This lifetime value
should not be too low that call should clear without being answered and not too high that
VLR faces shortage of MSRN allocations.
Typical values are:

Local Subscriber MSRN Lifetime: 20 Sec
Roaming Subscriber MSRN Lifetime: 90 Sec

18.6.6 CALL WAITING TIME

Time between call offered and call accepted
Network resources assigned during call waiting
time
If call not accepted within call waiting period,
network resources are released
Typical call waiting time: 25 secs
NSS NSS Call Waiting Time Call Waiting Time

18.6.6.1 Using Call Waiting Time

Call waiting time refers to the amount of time that network resources are allocated for call
setup. If the calls fails to be connected within this time, the network resources will be
released.


338

18.6.6.2 Call Waiting Time Values

It is recommended that this value is set at 25 sec so that network resources should not be
reserved for long time if call is not answered.

18.6.7 IMPLICIT DEREGISTRATION

18.6.7.1 Implicit Deregistration Usage

Implicit deregistration is feature implemented in the MSC to reduce the signalling load in
the BSS. This is achieved by preventing unnecessary paging of mobile phones that are out
of coverage. To the calling subscriber this is seen in an "Absent subscriber" message instead
of "No paging response" message.

Reduces signalling load towards the BSS by
reducing unnecessary paging
Deregisters MS after period of inactivity
Compares timestamp value in subscriber profile
with inactivity timer.
Timer is reset when MSC-MS interaction takes
If timer value > timestamp MS is deregistered
and paging ceases
Generally at least 2x periodic update timer value
NSS NSS - - Implicit Deregistration Implicit Deregistration

The implicit detach function contains an activity timestamp in the VLR for each subscriber.
Whenever interaction between a mobile terminal and the MSC ceases, a timer is started. If
the timer value reaches the activity timestamp value before the next interaction takes place,
the mobile terminal is marked ad deregistered in the VLR subscriber record and no more
paging to this terminal takes place. If an interaction takes place before the timestamp value
is reached, the timer is reset.

place


18.6.7.2 Implicit Deregistration Values

The timestamp value before implicit deregistration takes place should be set longer than
update interval so the subscriber is not deregistered if one
periodic location update is missed.

It is generally recommended that, where the facility exists, implicit deregistration should be
implemented in order to minimise the signalling load towards the BSS.

___________________________________________________________________
18.7 NSS Database Usage Evaluation

18.7.1 VLR UTILISATION
twice the periodic location

Database Usage Database Usage - - VLR VLR
VLR capacity should be evenly spread where possible
75% capacity limit is recommended to allow for peaks
and future expansion
Options for reducing VLR loading include:
Redistribution of BSCs amongst MSCs
Redesigning LA boundaries
Too large - excessive paging requirement
Too small - excessive location update requirement
Modify parameter settings to reduce signalling occurrences
VLR Cleaning
istration

VLR utilisation refers to the percentage capacity (in terms of subscriber records) of a given
VLR that is currently in use.

Problems that can occur with VLR utilisation include:

Over-capacity on a VLR
Uneven spread of records over a number of VLRs

The table above provides an example of VLR utilisation for a live network:

Implicit Dereg


339

340

NSS Databases NSS Databases VLR VLR Utilisation Utilisation
VLR utilisation refers to subscriber record
capacity and usage within a VLR
Utilisation problems include:
Over-capacity in certain VLRs
Uneven spread of records across the
network
Over-capacity can result in:
Call function failures (e.g. setup/handover,
authentication etc)
Lack of growth capability
7% MSC-10 10
62% MSC-9 9
100% MSC-8 8
71% MSC-7 7
66% MSC-6 6
86% MSC-5 5
100% MSC-4 4
26% MSC-3 3
82% MSC-2 2
65% MSC-1 1
VLR
Utilisation MSC Sr. No.

This table shows a wide range of loading within the MSCs (7% to 100%). MSC 4 may
vers,
failed authentication, failed call establishment etc). In addition growth in the this MSC
icantly underutilised. Although this provides redundant capacity for
expansion, it is wasting valuable resources.

18.7.2 VLR CLEANING
already suffer from congestion and hence subscriber function failures (failed hando
service area will not be possible.
MSC-10 is signif

18.7.2.1 Using VLR Cleaning

VLR cleaning is a Nokia-proprietary function implemented in the VLR to reduce the
number of stored but redundant subscriber records.

This is achieved by placing a timestamp in the subscriber record. A timer is started after the
last time the record is accessed. If the timer reaches the timestamp value before the next
At a pre-determined time (normally a quite period) , cleaning takes place in the VLR where
or deletion are removed.

activity, the subscriber record is marked for deletion. If activity takes place within the
timestamp period, the timer is reset.

all records marked f


341

Reduces capacity loading within a VLR (Nokia proprietary)
Deletes subscriber records that are inactive for a specified
period of time
Compares timestamp value in subscriber profile with
inactivity timer.
Timer is reset when sub scriber record is accessed
If timer value > timestamp, subscriber record is marked for
deletion
Cleaning takes place during non-busy periods
Common settings are typically 24hrs to 3 days
NSS NSS - - VLR Cleaning VLR Cleaning

18.7.2.2 VLR Cleaning Values

VLR cleaning timestamp values range typically from 24 hours to 3 days.

18.7.3 HLR UTILISATION

NSS Databases NSS Databases HLR Utilisation HLR Utilisation
HLR utilisation refers to
subscriber record capacity and
usage within a HLR
Utilisation problems include:
Over-capacity in certain HLRs
Uneven spread of records across
the network
Over-capacity can result in:
Call function failures (e.g.
setup/handover, authentication
etc)
Lack of growth capability
Signalling bottlenecks
0
10
20
30
40
50
60
70
80
%AGE USAGE OF HLRs
90
100
HLR1 HLR2 HLR3 HLR4 HLR5
%AGE USAGE


342

The above graph indicates that at least one of the HLRs has exceeded the 95% mark and at
least one other is approaching that utilisation value. However, HLR 3 is only operating at
50% capacity.

Clearly there is a requirement to redistribute subscriber records more evenly to avoid
congestion problems and signal routing bottlenecks. If expansion is desired, additional HLR
capacity may have to be built into the network


19. Dimensioning Networks for
New Services

____________________________________________________________________
_
19.1 Introduction
new services such as HSCSD or GPRS to the network, careful consideration
en to the additional capacity requirements. The integration of additional
circuit-switched data services such and HSCSD involves significantly different planning
than for packet-switched services such as GPRS.

This section of the notes provides an overview of some of the planning techniques and
considerations when planning for both circuit-switched and packet-switched services.

When adding
should be giv
A-1

arily a voice system. Developments have
ffic offered being in the form of data, either
High Speed Circuit Switched Data (HSCSD) or General Packet Radio Service (GPRS). The
HSCSD service entails a user seizing more than one timeslots on a carrier for a single
session whereas GPRS will initially use spare capacity on the air interface to dynamically
allocate packet data.

Therefore, different traffic dimensioning techniques will be required to accommodate both
voice and data (HSCSD/GPRS) services.

___________________________________________________________________
19.2 Multi-Service Dimensioning

GSM was originally a designed to be prim
included an increasing proportion of the tra
Dimensioning Dimensioning a Multi a Multi- -Service Service System System
The Erlang B formula relies on the v
demand equalling the mean (a Pois
ariance of the
son distribution).
If a particular service requires more than one trunk
per connection, the demand is effectively linearly
scaled and the variance no longer equals the mean.
Methods to investigate:
Equivalent Erlangs
Post Erlang-B
Campbells Theorem
Secti on 10 New Service Optimisation

19.2.1 EQUIVALENT ERLANG TRAFFIC DIMENSIONING

The Erlang B formula is the generally accepted method of calculating capacity within a
cellular radio network. However, one of the assumptions on which the Erlang B formula is
based is that a single call will require a single trunk for a specific duration. Unfortunately,
the Erlang B formula ceases to be as accurate for predicting the required number of
timeslots when the resource is shared amongst services requiring more than one channel
per subscriber as is the case with HSCSD or possibly GPRS.
l (timeslot) per session is said to have
an amplitude of 1. Where a service requires, for example, 2 or 3 channels per session, it is
said to have an amplitude of 2 and 3 respectively.

A service such a voice that requires a single channe
A-2

Using the Equivalent Erlangs approach, the bandwidth of one service is converted to its
equivalent bandwidth in the other service and the total capacity requirement is then
calculated as a single service.

Equivalent Erlangs Equivalent Erlangs
+
Low
Bandwidth
Equivalent
High
Bandwidth
Equivalent
A-3
Combine the two traffic sources together by
converting one to the bandwidth of the other
The trunking efficiency will VARY with the
hoose!
Not suitable for use due to this property
2 Erlangs
of Low
Bandwidth
1 Erlang of
High
Bandwidth
Difference in
capacity
required for
same GoS
bandwidth of equivalent Erlang that you c
Section 10 New Service Optimisation

Equivalent Erlangs Equivalent Erlangs Example Example
Consider 2 services sharing the same resource:
Service 1: uses 1 trunk per connection. 12 Erlangs of traffic.
Service 2, uses 3 trunks per connection. 6 Erlangs of traffic.
We could regard the e as equivalent to 30 Erlangs of
service 1:
30 Erlangs require 39 trunks for a 2% Blocking Probability
Alternatively, we could regard the above as equivalent to 10
Erlangs of service 2.
10 Erlangs require 17 trunks, (equivalent to 51 service 1 trunks) for a
2% blocking probability
Prediction varies depending on what approach you choose.

abov

It can be seen that by taking the Equivalent Erlang approach, different channel capacities
will be required depending on which service is selected for conversion to the equivalent of
the other. Clearly, this cannot be the most accurate appraisal of the capacity requirements.

19.2.2 POST ERLANG B TRAFFIC DIMENSIONING

Post Erlang Post Erlang- -B B
Combine the two traffic
sources together after
calculating required
capacity
1 Erlang of
Service A
+
The trunking efficiency
variation with magnitude
is not considered -
pessimistic about offered
traffic supported to the
same GoS
Not suitable for use due
to this property
1 Erlang of
Service B
1 Erlang and 1
Erlang of of
Service B
Illustration using 2 services of
same bandwidth
Difference
in capacity
required for
same GoS
Accepted correct method

Consider 2 services sharing the same resource:
Service 2: uses 3 trunks per connection. 6 Erlangs of traffic.
We could calculate the requirement separately
Service 1: 12 Erlangs require 19 trunks for a 2% Blocking Probability
Service 2: 6 Erlangs require 12 trunks (equivalen
trunks).
t to 36 service 1
f trunks
ices

Adding these together gives 55 trunks.
This method is known to over-estimate the number o
required as can be demonstrated by considering serv
requiring an equal number of trunks.
A-4

The Post-Erlang B approach differs from the equivalent Erlang approach in that it
calculates the capacity requirements of each service individually and simply adds them
together to determine the overall capacity requirement.

Consider 2 services requiring equal resource:
We could calculate the requirement separately
Service 1: 12 Erlangs require 19 trunks for a 2% Blocking Probability
Service 2: 6 Erlangs require 12 trunks.
Adding these together gives 31 trunks.
The accepted method of treating the above would be to regard
it as a total of 18 Erlangs that would require 26 trunks.

Erlang B approach is simpler than Equivalent Erlangs and gives a constant result
ss of which service capacity is estimated first. However, it has been shown to
overestimate the actual overall capacity requirements.

Post Erlang-B overestimates the requirement.
The Post
regardle
19.2.3 TRAFFIC DIMENSIONING USING CAMPBELLS THEOREM

Campbells Theorem Campbells Theorem
Campbells
A-5
theorem creates a composite distribution where:
The amplitude (a
i
) used in the capacity is the amplitude of the target service
Once the equivalent offered traffic and capacity are derived, GoS can be
derived with Erlang-B
Required capacity can be calculated if offered traffic and GoS target is
known
( )
c
a C
Capacity
i i

=
c
ffic OfferedTra

=
= =
i
i i i
i
i i i
b a
b a
c
2
C
i
= available capacity
= mean
= variance
i
= arrival rate
a
i
= amplitude of service
b
i
= mean holding time
c = capacity factor
i i
b = Traffic Offered Service

An alternative to the two above capacity estimation approaches is the formula devised by
Campbell. Campbells Theorem is seen as an appropriate way to establish the required
xed traffic is offered.
uppose we needed to establish the required resource
to accommodate 12 Erlangs of voice and 6 Erlangs of HSCSD traffic of amplitude 3:

The first step is to calculate the mean: = (12 x 1) + (6 x 3) = 30

Next we calculate the variance: = (12 x 1
2
) + (6 x 3
2
) = 66

From these two parameters a capacity factor is derived.

resource when a certain amount of mi

It is best understood as a procedure. S

2 . 2
mean
variance
factor, capacity = = c

The equivalent offered traffic is calculated by dividing the mean by the capacity factor:

Erlangs 6 . 13
2.2
30
traffic offered = =

From the Erlang B table, 21 trunks would be required.

To convert this into equivalent voice trunks, this figure must be multiplied by the capacity
factor.

46.2 2.2 21 trunks voice Equivalent = =

Campbells Theorem Example Campbells Theorem Example
Consider the same 2 services sharing the same
resource:
Service 2, uses 3 trunks per connection. 6 Erlangs of traffic.
In this case the mean is:
The variance is:
Note: = traffic in Erlangs

= + = = = 30 ) 6 3 ( ) 12 1 ( Erlangs a a b
i i i i

= + = = = 66 ) 3 6 ( ) 1 12 ( Erlangs
2 2 2 2
i i i i
a a b
i i
b

A-6

A minor adjustment must be made depending on which service is defined as the target or
priority service. This is to reflect the fact that if two services share the same resource, the
one that demands the higher unit resource will experience a worse grade of service. So, if
the HSCSD service is deemed to be the target service, a total of 46+3 = 49 timeslots should
be available.

Capacity Factor c (average trunks per connection):
Equivalent offered traffic:
Trunk capacity for equivalent traffic at 2% GoS = 21
2 . 2
30
66
= = =
c
63 . 13
2 . 2
30
Traffic Offered Equivalent = = =
c

Actual trunk requirement is trunk capacity x capacity
factor:
= 21 x 2.2 = 46.2 or 46 trunks
Required Capacity is modified depending upon target
service for GoS (in service 1 Erlangs):
Target is Service 1 C
1
=(2.2 x 21) + 1 = 47
Target is Service 2, C
2
=(2.2 x 21) + 3 = 49
Different services will require a different capacity for the
same GoS depending on the amplitude

A-7

19.2.4 COMPARISON OF TRAFFIC ANALYSIS METHODS

Traffic Analysis Methods Compared Traffic Analysis Methods Compared
Equivalent Erlangs
Optimistic if you use the smallest amplitude of trunk (39)
Pessimistic if you use the largest amplitude of trunk (51)
Post Erlang-B
Pessimistic (55)
Trunking efficiency improvement with magnitude ignored
Campbells theorem
Middle band (47 - 49)
Different capacities required for different services - realistic
Preferred solution for dimensioning, but not ideal...

19.2.5 CAPACITY DIMENSIONING USING CAMPBELLS THEOREM

ith an amplitude of 2. The calculation detailed below suggests
that, if each cell is capable of providing 15 timeslots, 56 cells will be required to service that
demand with each cell then capturing 4.46 Erlangs of voice traffic and 1.13 Erlangs of
HSCSD.

Suppose a particular area was to be forecast to offer 250 Erlangs of voice traffic and 63
Erlangs of HSCSD traffic w
Capacity Dimensioning with Campbells Capacity Dimensioning with Campbells
Theorem Theorem
Consider the following service definition and traffic
forecast.
Service Amplitude Forecast
Voice 1 250 E
HSCSD 2 63 E

Based on a theoretical availability of 15 voice trunks per
cell and using voice as the benchmark service and with
2% blocking, determine the number of cells required to
serve the above traffic levels and the traffic offered per
cell for each service

A-8

Theorem Theorem
Assuming we have n cells, we can determine the loading
per cell.
n n c
c
n n n
n n n
282
335 . 1
376 mean
traffic offered
335 . 1
376
502
mean
variance
502 2 63 250
variance
376 2 63 250
mean
2
=
= =
= = =
=
+ =
=
+ =

Theorem Theorem
Considering the equation:
C
i
(available capacity) is predefined as 15. a
i
(amplitude)
depends on the service we use as our benchmark or priority
service. Choosing the voice service as the benchmark
service make a
i
equal to 1.
10.5 (rounded to 10) trunks will service 5.08 Erlangs.
c
a C
i i

= Capacity
( )
5 . 10
335 . 1
1 15
=
=
i
C

A-9

Theorem Theorem
Each cell requires 10 trunks to service 5.08 Erlangs.
Therefore:
Number of cells required = Equivalent Traffic
Traffic per Cell
=
requirement is established at 56 cells.
of the cells will service:
4.46 Erlangs of voice (250/56)
1.13 Erlangs of HSCSD.(63/56)
Cell
Each
5 . 55
08 . 5
282
=

19.2.6 ASSESSING CELL LOADING USING CAMPBELLS THEOREM

C o indicate the number of carriers that should be
p exercise. An example is given below:

ampbells Theorem can be used t
capture rovided following a traffic
Assessing Cell Loading using Campbells Assessing Cell Loading using Campbells
Theorem Theorem
After placing sites on the coverage map and
spreading the traffic, the next stage is to assess the
cell loading (timeslots required).
If mixed services are used, it is necessary to use
Campbells Theorem to assess the required number
atisfy the likely demand.
case where a particular cell captures 7
SCSD traffic that
2 timeslots per connection.

of timeslots to s
Consider the
Erlangs of voice and 2 Erlangs of H
requires
A-10

Assessing Cell Loadi Assessing Cell Loading using Campbells ng using Campbells
Theorem Theorem
:
timeslots required.
Using Campbells Theorem
Hence 20
( ) 20 1 36 . 1 14 : benchmark as voice Taking
required. trunks 14 B, Erlang From
Erlangs 09 . 8
36 . 1
11
traffic offered Equivalent
36 . 1
11
15
) ( Factor
15 ) 2 2 ( ) 1 7 (
11 ) 2 2 ( ) 1 7 ( mean
2 2
= +
= =
= =
= + =
Capacity
variance
= + =
c

___________________________________________________________________
19.3 Mixing Packet and Circuit-Switched Traffic

Evaluating Traffic Requirements Evaluating Traffic Requirements
Real time non-controllable load
Spare capacity for which can
be allocated to non real time
applications
Peak traffic
Load
Time
Average circuit
switched traffic
Data may be packet switched, in which case it can be made to fill the
gaps in the demand for voice services.
g

A-11

Eval Evaluuating Traffic Requirements ating Traffic Requirements
To evaluate the required cell capacity:
t the packet data can be scheduled to fill the spare real time
capacity has been exhausted we must convert the
t data capacity.
.

First assume tha
capacity.
When all the spare real time
remaining capacity to an equivalen
One GSM timeslot can carry 13 kb/s of data
Traffic Requirement Example Traffic Requirement Example
A cell captures 2 Erlangs of voice traffic and is assigned a GSM carrier
with 7 timeslots. The grade of service is 2%.
Estimate the amount of data traffic that can be handled.
ust be packet data and how much can be circuit
ilable on average = 7 - 2 = 5
a total data rate of 5 x 13 = 65 kb/s
voice traffic requires 6 trunks (timeslots) for 2% blocking.
e dedicated (circuit switched) for data, i.e. 13 kb/s
packet switched = 65 - 13 = 52 kb/s.

How much of this m
switched?
Solution:
Timeslots ava
This represents
2 Erlangs
1 timeslot can b
Remaining data must be
A-12

___________________________________________________________________
19.4 GPRS Performance Monitoring

I gnificantly from that of GSM. Therefore
a mance monitoring parameters need to be defined. This
s e of these parameters including:

n a number of areas, GPRS functionality differs si
number of new GPRS perfor
ection looks at som
Example Exampless of GPRS of GPRS- -Specific Parameters Specific Parameters
Cell Reselection
Service Exceptions
Average Response Times
Suspend/Resume Procedures
Attach/Detach Procedures
Routing Area (RA) Update Procedures
PDP Context Activations
Data Volumes and Rates

GPRS Transmission Connections GPRS Transmission Connections
SGSN SGSN
MS MS
GGSN GGSN BSS BSS
G G
b b
G G
n n
U U
m m
PDP Context PDP Context
Logical Link Control Logical Link Control
Connection Connection
Data Link Connection Data Link Connection
IMSI/NSAPI IMSI/NSAPI
TLLI TLLI
DLCI DLCI
TID TID

A-13

A-14

19.4.1 CELL RESELECTION

Within a GPRS network, the cell reselection procedure with the mobile station (MS) in
ready mode differs fundamentally from the handover procedure in GSM. In GPRS, this
procedure is generally initiated by the MS, unlike GSM mode. The MS indicates to the
network that it has changed cells, sending the network a data sequence that it transmits
directly to the target cell.

The GPRS network has to implement a number of procedures designed to deliver a
continuous data stream to the subscriber. More specifically, it must:

Detect the cell reselection.
Attempt to transfer all of the data buffered by the source cell and not transmitted
to the buffer of the target cell. If this transfer fails, it must erase the data intended
for the subscriber from the source cell buffer and inform the SGSN.
Ensure routing of new data intended for the MS to the target cell.

Any malfunction of these procedures can be detected and recorded, together with any
incorrect parameter settings in the MS, cell and BSS.

GPRS Cell Reselection GPRS Cell Reselection
Cell Reselection per source cell
Cell Reselection Subscribers in READY state
Number of cell
reselections
Number of
Octets
Average Number of Octets Affected
Average Number of Octets Deleted
Average Number of Frames Deleted
Number of Cell Reselections
| 0000100002 | 0000100003 | CI

19.4.2 SERVICE EXCEPTIONS

In a GPRS network, the SGSN must be informed about disruptions on the radio link
between the MS and BTS. The ETSI GPRS standard lists three possible disruption types:

The radio link to the MS was lost.
The quality of the radio link has degraded beyond being able to continue the session
within the negotiated service quality.
The BSS requires the MS to carry out cell reselection.

A-15

GPRS Service Exceptions GPRS Service Exceptions
Radio Link Signal Strength falls below
threshold (link failure)
Link quality falls below threshold (link failure)
Cell Reselection initiated

Cases 1 and 2 mean that exchanges between the MS and the network via the current cell
must be suspended while the exception is processed. These procedures can be monitored
and summarised by cell and/or TLLI in order to detect:

1. Possible malfunctions of::
The radio subsystem
Certain cells, causing holes in the coverage (case 1)
Certain cells causing high BERs
Certain MSs

Frames Frames Lost Through Service Exceptions Lost Through Service Exceptions
Number of frames deleted per TLLI
Number of Frames
Deleted

A-16

2. Cell reselections imposed by the network on the MS. By detecting these malfunctions,
it is possible to take corrective action:

Locate holes in the coverage and then make corrections at the BTS level (tilt,
power, etc.)
Identify and remove the interference or change one or more frequencies assigned
to the BTS.

19.4.3 SUSPEND/RESUME PROCEDURE

The suspend procedure allows a class B mobile station connected in GPRS mode to
suspend operation in GPRS mode and move to GSM mode
in order to make a circuit-mode connection. Checks of the suspend procedure can be
performed and failures summarised by TLLI, by cell and/or by cause.

Suspend / Resume Procedures Suspend / Resume Procedures
Suspend Procedure:
Enables a GPRS Class B MS to suspend GPRS mode in
order to make a circuit-switched connection
Resume Procedure:
Enables a GPRS Class B MS to resume GPRS mode having
made a circuit switched connection
Monitoring:
Procedure can be monitored and failures can be displayed
by TLLI, cell or cause

The resume procedure allows a GPRS class B MS connected in GSM mode to resume its
operation in GPRS mode after a Suspend procedure. Checks can also be carried out on the
resume procedure and similarly, failures can be summarised by TLLI, by cell and/or by
cause.

A-17

19.4.4 AVERAGE RESPONSE TIME

GPRS Average Response Times GPRS Average Response Times
Average response time after paging, per BVCI
Time in millsecs
BVCI

The average response time of the network or mobile station can be measured and recorded.
Using the recorded values, the QoS experienced by the subscriber can be estimated to a
degree. For example, a response time can be measured between paging request message to
an MS and the first message with data content returned by this MS, as this first message is
deemed to be the response to the paging message.

This measurement can be summarised at cell level, per BVCI (BSSGP protocol Virtual
Circuit Identifier) in order to provide mean representative statistics.

This information:

Allows the defined paging repetition period to be compared with the average
response time of the subscribers: For example, a repeat paging request time of 2
seconds when the average response time is greater than 2 seconds results in
wasted repetitions of paging messages.
Highlights cells with an abnormal response time.

By detecting such problems, it is possible to:

Modify the paging repetition period in order to reduce the network signalling
channel load.
Investigate the appropriateness of these cell parameters (e.g. lack of paging,
interference, etc.).

A-18

19.4.5 ATTACH/DETACH PROCEDURES

The GMM attach procedure entails an MS switching from Idle state to Ready state in order
to exchange data in GPRS mode. The GMM detach procedure is the reverse, i.e. reverting
from Ready state to Idle state on completion of GPRS data exchange.

GPRS Attach/Detach Procedures GPRS Attach/Detach Procedures
Number of Attach Procedure Messages
Attach Request Attach Accept Attach Complete Attach Reject
Number of
Procedures
Attach Procedures

Number of Attach Reject Messages per Cell
Attach Rejects per Cell Number of
Attach Rejects

A-19

The following checks can be carried out on these GPRS procedures:

Request for GPRS attach by MS
Attach acceptance response by the network
Acknowledgment of acceptance by MS.

Number of Attach Reject Messages per Subscriber (TLLI)
Number of
Attach Rejects
Attach Rejects per TLLI

Any procedure that does not follow these three phases indicates an error condition.

Detection of one or more subscribers who are failing to correctly attach may indicate an
SGSN VLR that might not be furnishing the correct subscriber profile information

Based on these elements, the following corrective measures can be requested from the
services involved:
Checking of links to the HLR
Checking of VLR parameters
Checking of roaming parameters

A-20

19.4.6 RA UPDATE PROCEDURE

GPRS RA Update Procedures GPRS RA Update Procedures
Number of RA Update Messages
RA Updates
RA Request RA Accept RA Reject RA Request without response
Number

GPRS RA Update Procedures GPRS RA Update Procedures
Number of RA Update Rejects by Cause
Number of
RA Rejects
RA Rejects per Cause
Unknown Causes Network Failures

The GMM Routing Area (RA) update procedure is initiated each time a GPRS MS in Ready
or Standby mode changes Routing Areas. This procedure can be checked as follows:

A-21

Location Update request by MS
Request acceptance response by network
Acknowledgment by MS

Any procedure that does not follow these three phases is incorrect.

19.4.7 PDP CONTEXT ACTIVATION/DEACTIVATION

PDP context activation takes place when packet data communication between an MS and a
GGSN is initiated. It can be monitored as follows:

MS activation request message
Network acceptance or rejection response.

The different cases can then be summarised as shown below:

GPRS PDP Contexts GPRS PDP Contexts
PDP Context Activation by MS
PDP Contexts Activated PDP Contexts Accepted PDP Contexts Rejected
Number PDP
Context
Activations
Number of PDP Context Activation Messages

The PDP Context activation procedure comprises the following elements:

The ID of the entity initiating the activation (MS or network)
LLC SAPI requested
LLC SAPI assigned
QoS requested
QoS assigned
The GGSN access point (if available)
Rejection cause (if any)

A-22

Summaries of these procedures can be created by cell and/or by TLLI. The different
procedural elements described above allow prcis identification of any failure cause. e.g.
Malfunction of an access point, etc.

PDP context deactivation procedures are similar (but in reverse) to the activation
procedures described above.

19.4.8 DATA VOLUME EXCHANGED AND RATES

Cell

The volume of LLC data exchanged and LLC data rates for both UL and DL can be
monitored for each cell. This is useful for instant troubleshooting of a cell where problems
have been identified or which is regularly pushed to its rate limit. Moreover, periods of
heavy usage or even saturation can be detected immediately.

GPRS Data Volumes and Rates GPRS Data Volumes and Rates
Downlink Data Rate of a Cell
DL LLC Rate
Bytes
Time (minutes)

Such analysis is useful for modifying the parameters related to cell dimensioning in order
to provide better QoS to the subscribers.

Mobile Station

The volume of LLC data exchanged and LLC data rate activity for both UL and DL can be
monitored and displayed for each MS. From this it is possible to:

Precisely determine the resources used by a mobile station
Immediately troubleshoot a mobile station that is malfunctioning
Obtain the data you need for dimensioning cells

A-23

GPRS Data Volumes and Rates GPRS Data Volumes and Rates
Downlink Data Rate of a Mobile Station
Time (minutes)
Volume (bytes)
DL LLC Global Size

A-24

A-25

A-26

GPRS Case Study using ASSET planning software
Introduction
The evolution of GSM towards 3G Systems is described in the diagram below:

The main driving force behind this evolution is the requirement for increased data rates.
The four technologies, classed as 2.5 Generation, covered within this session are:
HSCSD: High Speed Circuit Switched Data
ECSD: Extended Circuit Switched Data (using EDGE technology)
GPRS: General Packet Radio Service
EGPRS: Extended General Packet Radio Service (using EDGE technology)
HSCSD/ECSD Overview
HSCSD is one of a number of technologies designed to improve the data-carrying capability of GSM. As its
name implies, HSCSD, has been designed to work using the existing GSM circuit-switched network and
achieves higher data rates by combining several voice channels (each with a maximum data rate of 14.4
kbps) into a singe virtual data channel.
GSM technology dictates that the maximum number of combined voice channels is 4 and therefore the
maximum data throughput could be 57.6 kbps.
ECSD offers higher data rates than HSCSD by employing EDGE technology at the air interference to
improve the capacity of each channel. EDGE uses an enhanced modulation technique (8 PSK). The main
advantage of EDGE is that it will offer higher data rates without fundamentally changing the hardware
infrastructure.

A-27

HSCSD/ECSD offers two different kinds of connections:
Transparent
Non-transparent
Transparent connection means that the number of the timeslots is fixed during the entire connection. This
gives a constant bitrate and transmission delay. There is no error correction made by the network so the end
application must take care of error correction.
Non-transparent connection allows the number of allocated timeslots to be changed during the call. More
timeslots can be allocated if some resources are released from other calls. The number of timeslots can be
decreased for example if traffic load is high and there are not enough free timeslots left for speech traffic
(speech traffic should have priority over data traffic). Increasing and decreasing the number of timeslots are
called resource upgrading and resource downgrading procedures, respectively. Error correction (i.e.
retransmission of the frames) is conducted by the network so the data rate seen by the end application can
vary.
Configuring ASSET for HSCSD/ECSD Planning
Prior to planning HSCSD/ECSD in ASSET, you need to:
a) Set HSCSD or ECSD Channel Coding Schemes
b) Define the timeslot distribution
c) Configure Cell Layers
d) Define Terminal Types
Channel Coding Schemes
HSCSD Channel Coding Scheme
To set a HSCSD Channel Coding Scheme:
From the Tools menu, point to 2.5G and click HSCSD

A-28

Within the window that appears the tables can
be populated with default values by clicking on
the Set to Defaults button:

Or, in the C/I(dB) column, define the C/I, and in the coding scheme (throughput) column define the y axis
values, for example between 0 and 15 kb/s.
By clicking on the Show Graph button a plot
of C/I against data rate per timeslot will be
shown:

Click on the Commit button to save the scheme to the permanent database tables.
ECSD Channel Coding Schemes
To set a ECSD Channel Coding Scheme:
From the Tools menu, point to 2.5G and click ECSD

A-29

Within the window that appears the tables can
be populated with default values by clicking on
the Set to Defaults button:

Or, in the C/I(dB) column, define the C/I, and in the coding scheme (throughput) column define the y axis
values.
By clicking on the Show Graph button a plot
of C/I against data rate per timeslot will be
shown:

Click on the Commit button to save the scheme to the permanent database tables.
Timeslot Distribution
A Channel to Transceiver map is used to define timeslot distribution by specifying how many carriers are
needed to provide a required number of traffic channels.
To set up a channel to transceiver map for HSCSD, from the Options menu, click on Channel Maps
Within the Channel to Transceiver Setup window, click on the Add Map button and enter an appropriate
name for the map (e.g. HSCSD Map), clicking on the OK button to continue.
The following message will now appear: -

Click on the Yes button.

A-30

The following window will now appear:

Within the blank HSCSD Channel to Transceiver Setup window enter the number of traffic channels that can
be supported per carrier (e.g. 8), in the box labelled Default Number of Channels Per Transceiver and
click on the Apply button.
Click on the Add Transceiver button, which will populate your blank setup window with default figures.
To change the information in the table, select the row, and click the
Edit Map button.

The columns within the Channel to Transceiver Set-up window refer to the following information:
TRX: Number of available carriers
No: Total number of available channels for both control and traffic
NGPRS: Number of channels dedicated only for GPRS traffic
NCTRL: Number of control channels shared for GSM and GPRS use
NGPRSCTRL: Number of channels dedicated only for GPRS control
NHSCSD: Maximum number of channels that may be used by HSCSD
NCS: Number of circuit switched traffic channels
Having entered the relevant figures, for NHSCSD, click the OK button to close the GPRS Map Editor
window.
Click on the Apply button in the HSCSD Channel to Transceiver Set-up window to save your changes.

A-31

Cell Layers
In the Cell Layer window re-configure the existing GSM cell layer for HSCSD. Access the Cell Layer
Configuration window from the ENTERPRISE Main Menu by selecting Options Cell Layers.
In the Cell Layer Configuration window highlight the GSM cell layer. Under the Coverage Type tab, using
the drop down menu, select the HSCSD Channel to Transceiver Map created earlier.
Click on the Apply button followed by the Commit button.

Define Terminal Types
There can only be one HSCSD and one ECSD terminal type. Each of these terminal types has a value for the
traffic per terminal (in User Erlangs).
To define the HSCSD Terminal Types, from the Options menu, click Terminal
Types

In the Terminal Types dialogue box, click on the Add button to create a new terminal type. Select the newly
created Terminal Type and change its name, under the General tab.

A-32

Select the switching type from Circuit Switched (default
setting) to High Speed Circuit Switched (HSCSD).

Click on the Cell Layers tab and move the appropriate cell
layer from the Available column to the Selected column.

On the Clutter, Vectors and Polygons tabs, define how the
terminal type is distributed over the Map View.

A-33

On the HSCSD/ECSD tab set the Traffic per Terminal figure, which is common for the HSCSD and
ECSD terminal type.
Note: If you have both HSCSD and ECSD terminal types then the Timeslot Weightings are shared
between the two. Any changes made for one of these Terminal Types will affect the other.

Both transparent and non-transparent data types have dynamic allocation of timeslots and coding schemes
used by the network, however:
For transparent data a constant data rate is maintained provided that the maximum number of
supported timeslots is not exceeded.
For non-transparent data there is a variable data rate depending on the service quality.
You can define the distribution of different data rates for transparent and non-transparent data by specifying
the weights you require for the predefined data rate. Weights, total traffic, traffic distribution and C/I are then
used to determine how traffic is distributed over timeslots.
To change the data rate weighting, on the HSCSD/ECSD tab
Click on the Apply button, followed by the Commit button for other users to see your newly created HSCSD
Terminal Type.
Setting Cell Parameters
In ENTERPRISE, ECSD information is stored on the Cell Layer level. The subcell is considered to provide
ECSD service when you have selected the Enable ECSD check box within the HSCSD/ECSD tab.
To do this:
Select the required GSM cell layer (subcell) in the Site Database window.
Click on the HSCSD/ESCD tab.
Select the Enable ECSD check box. You can also enter a Total HSCSD + ECSD Traffic figure and
% of ECSD 8-PSK figure.

A-34

Note: If all cells within one filter are to be ECSD Enabled this can be achieved using the Global Edit
facility.

The ECSD modulation scheme puts new requirements on the linearity of the power amplifier: as opposed to
GMSK, 8-PSK does not have a constant envelope.
For this reason the average transmit power when transmitting 8-PSK, compared to GMSK, must be reduced
by between 2 and 5 dB (average power decrease APD).

A-35

Within ASSET the APD value can be entered on the Cell
Layer Level of each subcell under the Antenna/TRX tab:

Note: If all cells within one filter have the same APD value it can be set using the Global Edit facility,
under the 2.5G tab.
Calculate HSCSD/ECSD Service Area
Having configured ASSET for HSCSD/ECSD we can now follow the normal coverage planning process,
that is:
From the Tools menu, point to Coverage/Interference and click Predictor, this will run the prediction tool to
calculate Coverage Predictions.
Choose to calculate the Best Server array to visualise on the 2D Map View window the service areas of the
cells and display the array in the Map View Window.
Distribute Terminals and Create a Traffic Array
To distribute the HSCSD/ECSD terminal type:
Open a Map View (2D View) window showing the desired area. From
the Tools Menu, point to Traffic Raster Wizard

Within the first screen of the Traffic Raster Wizard choose the desired view for the traffic raster wizard to
use.
Either leave the default figures, which were calculated on initial project creation (Map data extents), or click
the Select View button, which will calculate the co-ordinates of the current view. Click the Next> button to
continue.
The second screen of the wizard allows you to select one or more terminal types from the list. For each
terminal type selected, a separate traffic array is created.

A-36

Note: If you wish to spread traffic to polygons and use the clutter weights you will define, ensure this
check box is selected.
Click the Next> button to continue.
Choose the required resolution for the raster. The memory required to create the selected resolution of raster
is shown.

Note: If you wish to restrict the traffic spread to Best Server coverage then the resolution must be set the
same.
Choose whether to restrict the traffic spread over an area with either CS Circuit Switched coverage by
selecting the box.

A-37

Note: If this option is unavailable (greyed out) either the resolution selected for the traffic raster is
different from that used in the coverage prediction, or there is no coverage array in memory.
Choose how you wish to spread the traffic. Either Live Traffic, Terminal Traffic or a combination of both.

Specify the expected Circuit Switched traffic in Terminals.

If Polygon Attributes are going to be used for spreading the traffic, select the terminal type and appropriate
polygon attribute within this screen. Click the Next> button to continue.
The last screen of the Traffic Raster wizard allows you to store the Traffic Raster as a file for future
reloading. Click on the Finish button.
Capture Cell Traffic and Calculate the Required Capacity
To start HSCSD/ECSD Capacity Planning, from the Tools menu, point to Traffic Analyse

A-38

Once traffic arrays have been created, click on the Capture Traffic button to collect the traffic information
per map pixel in the cells service area.

A report is produced, in Microsoft Excel, showing the Traffic Captured per Cell:

If the traffic amount is acceptable, apply it to the subcells by clicking on the Traffic button.
Within the HSCSD/ECSD tab the five values are the proportions of HSCSD traffic which is handling
transparent and non-transparent data. The proportions for transparent data are subdivided into proportions
using only one timeslot, two timeslots, three timeslots and all four timeslots.

A-39

These values are entered as weightings, which need not add up to 100.
The inputs required to calculate the Timeslot Distribution (before clicking on the Calculate Now button)
include:
Best Server Array (Circuit Switched)
Average Connection Array
Traffic Raster for HSCSD or ECSD Terminals
HSCSD Throughput vs. Average Connection curve
ECSD Throughput vs. Average Connection curve
Data Rate requirements for both Transparent and Non-Transparent data
Having ensured these prerequisites have been done, click on the Calculate Now button. The calculation is
taken from the data requirement of the terminal type for the latest created traffic raster.

Having entered a QoS level and chosen a capacity calculation (Erlang B or Erlang C), click on the Analyse
button.
A report will be produced (in Microsoft Excel) showing Average Timeslot Erlangs per User Erlang,
HSCSD/ECSD Blocking:

A-40

If you are satisfied with the results click on the Apply Carriers Required on SubCells button.
Having completed capacity planning, the HSCSD/ECSD planning process follows the normal radio network
planning process, that is, Neighbour Planning and Analysis, Interference Tables, Frequency Planning and
Analysis.
GPRS Overview
GPRS, General Packet Radio Services, is an extension to GSM that allows more efficient packet data
transfer compared to traditional GSM data services. The principle is that a user can be constantly connected
to the network without occupying any radio resources (frequency, time slots) until a data packet has to be
transferred.
When a packet is to be transferred, a temporary channel is assigned to the user; after completed transfer, the
channel is quickly released again.
GPRS allows many users to share the same timeslot, and also allows a single user to use more than one time
slot. It uses an error detection and retransmission scheme to ensure that data packets are correctly delivered
to the receiver.
Within this session we will look at the stages in the GPRS Capacity process. The following diagram gives an
overview of the GPRS Planning process: -

A-41

Defining the Targets of the GPRS Service
The aim of this phase is to identify the existing sites and new sites where GPRS is to be enabled and get
some idea of the required modifications that you need to make to the existing network before you can
implement the desired GPRS Service.
In a dimensioning tool, decide:
What kind of data services will be provided?
Where the service is required?
Updating the Plan with Actual Network Data
The information from the current frequency plan is needed when planning for GPRS networks. Therefore,
before you continue, you must update the plan to meet the actual networks site/cell structure, element
identity, neighbours and frequency information.
Defining Data Service Settings
To initialise the GPRS service, you need to:

A-42

a) Set GPRS Channel Coding Schemes
b) Define the timeslot distribution
c) Set Occupancy Table
Set GPRS Channel Coding Schemes
To set GPRS Channel Coding Schemes:
From the Tools menu, point to 2.5G and click Coding Schemes

The following window will then appear: -

You can populate these tables with default values by clicking on the Defaults button. Having populated
the table you may edit the values by highlighting and re-typing.
-or-
In the C/I(dB) column, define the C/I, for example between 0 and 30 dB and in the coding scheme
(throughput) column define the x axis values, for example between 0 and 15 kb/s.
Note: The C/I versus data rate values are dependent on the nature of the network, for example, how fast
the mobiles are expected to move, whether RF hopping is used in the GPRS cells, and so on.
Tune the suggested default values based on that network information.

A-43

You can then:
Click the Show Graph button to see a plot of C/I against data rate per timeslot.
Edit a value by clicking it and changing it.
Click the Remove All button to delete all the values in the columns.
Note: If you select a row with data in it, except the last row, you can then click the Add Row button to add
another row.
Click the Commit button to save the scheme to the permanent database tables.
Repeat the above steps to add a further coding scheme up to a maximum of four.

Coding schemes are optimised, that is, the best one is chosen. The data contained within these tables can be
scaled for any number of timeslots, that is, the data rate for three timeslots is three times the data rate for one
timeslot for a given C/I.
Defining Timeslot Distribution
Use the Channel to Transceiver mapping tables to define timeslot distribution. These mapping tables enable
you to specify how many carriers are needed to provide a required number of traffic channels. You need to
set the amount of Circuit Switched and Packet Switched control channels as well as the amount of dedicated
GPRS traffic channels.
To set up a channel to transceiver map for GPRS, from the Options menu, click on Channel Maps
Within the Channel to Transceiver Setup window, click on the Add Map button and enter an appropriate
name for the map. Click the OK button to continue.

A-44

The following message will now appear: -

As this map will be for GPRS, click on the Yes button.
The following window will now appear:

Within the blank GPRS Channel to Transceiver Setup window enter the number of traffic channels that can
be supported per carrier (e.g. 8), in the box labelled Default Number of Channels Per Transceiver and
click on the Apply button.
Click on the Add Transceiver button, which will populate your blank setup window with default figures.
To change the information in the table, select the row, and click the Edit Map button.

The columns within the Channel to Transceiver Set-up window refer to the following information:
TRX: Number of available carriers
No: Total number of available channels for both control and traffic
NGPRS: Number of channels dedicated only for GPRS traffic
NCTRL: Number of control channels shared for GSM and GPRS use
NGPRSCTRL: Number of channels dedicated only for GPRS control
NHSCSD: Maximum number of channels that may be used by HSCSD

A-45

NCS: Number of circuit switched traffic channels
Having entered the relevant figures, click the OK button to close the GPRS Map Editor window.
Click on the Apply button in the Channel to Transceiver Set-up window to save your changes.
Set the Occupancy Table
Channel Occupancy is used to estimate the efficiency with which GPRS data packets can be packed into the
available timeslots. This is most useful in GPRS when you come close to using full network capacity. The
greater the number of available timeslots means the better the efficiency with which GPRS data packets can
be packed.
To set the Occupancy Table, from the Tools menu point to 2.5G and then select Occupancy.

Populate the columns with default values by clicking on the Set to Defaults button.
Note: If you want to populate columns with your own values, click the Remove Graph button to remove
the default values and then click on the Add Graph button to add an empty column. Manually add values,
using between 0 and 100 in the Occupancy column, where 100 means full capacity.
You can edit any value by clicking on it and then changing it. When you have selected a row with data in it,
except the last row, you can click on the Add Row button and add another row.
Click on the Show Graph button to see a plot of the values, clicking on the Commit button to save the
information to the database.

Occupancy table with default values Occupancy Graph of default values

A-46

Cell Layers
In the Cell Layer window we can either define a different cell layer for GPRS or we can use the existing
GSM cell layer. For the purpose of this training course we will keep the existing GSM cell layer. Under the
Options tab select Cell Layers.
In the Cell Layer Configuration window highlight the relevant GSM cell layer. Under the Coverage Type
tab, using the drop down menu, select the GPRS Channel to Transceiver Map created earlier.
Click on the Apply button followed by the Commit button.

In ENTERPRISE, GPRS information is stored on the Cell Layer level. The subcell is considered to provide
GPRS service when you have selected the Enable GPRS check box on the (E)GPRS tab.
To do this:

A-47

Select the required GSM cell layer (subcell) in the Site Database window.
Click on the (E)GPRS tab.
Select the Enable GPRS check box and choose at least one supported Channel Coding Scheme and
set the Total GPRS + EGPRS Traffic in Kbit/s.

Note: One Coding Scheme must always be selected, so if you want to change to another Coding Scheme,
select it then deselect the first check box.
If the Dedicated PBCCH check box is unchecked the tool ignores NGPRSCTRL in the channel map. This
means that the time slots that have been reserved for GPRS control will become available for circuit
switched traffic.
Note: If all cells within one filter support the same coding schemes the above configuration can be done
using the Global Edit facility.

A-48

Calculating and Analysing the GPRS Service Area
The definition of cell-specific GPRS service areas follows the normal coverage planning process, that is:
From the Tools menu, point to Coverage/Interference and click Predictor, this will run the prediction tool to
calculate Coverage Predictions.
Choose to calculate the Best Server (GPRS/EGPRS) array to visualise on the map the service areas of the
cells where GPRS is enabled.
Display the array in the Map View Window.
Defining Terminal Types using Data Service
For the Traffic and Capacity planning process, and estimate of the GPRS terminal distribution is required as
well as an idea of the services and data rate demand of the terminals.
To define the GPRS Terminal Types, from the Options menu, click Terminal Types

In the Terminal Types dialogue box, click on the Add button to create a new terminal type. Select the newly
created Terminal Type and change its name, under the General tab.

A-49

Select the switching type from Circuit Switched (default setting) to GPRS.
Click on the Cell Layers tab and move the appropriate cell layer from the Available column to the Selected
column.

On the Clutter, Vectors and Polygons tabs, define how the terminal type is distributed over the Map View.

A-50

On the GPRS/EGPRS tab choose the mean busy hour capacity (kb/s) of the terminal.

Note: This figure should include any overhead related to the characteristics of the device, for example
average packet size, TCP/IP protocol and so on, up to a limit of 9999.999. This is an estimate of the traffic
going through in a busy hour, per terminal type.
Also enter the maximum number of timeslots supported by the terminal (dependent on the class of handset -
theoretically up to 8 but realistically up to 4).
Click on the Apply button, followed by the Commit button for other users to see your newly created GPRS
Terminal Type.
Distributing Terminals and Creating Traffic Arrays
To distribute the desired terminal type:
Open a Map View (2D View) window showing the desired area. From the Tools Menu, point to Traffic
Raster Wizard

A-51

Within the first screen of the Traffic Raster Wizard choose the desired view for the traffic raster wizard to
use.

Either leave the default figures, which were calculated on initial project creation (Map data extents), or click
the Select View button, which will calculate the co-ordinates of the current view. Click the Next> button to
continue.
The second screen of the wizard allows you to select one or more terminal types from the list. For each
terminal type selected, a separate traffic array is created.

Note: If you wish to spread traffic to polygons and use the clutter weights you will define, ensure this
check box is selected.

A-52

Choose the required resolution for the raster. The memory required to create the selected resolution of raster
is shown.

Note: If you wish to restrict the traffic spread to GPRS Best Server coverage then the resolution must be
set the same.
Choose whether to restrict the traffic spread over an area with either CS Circuit Switched or GPRS -
Packet Switched coverage by selecting the box.

Note: If this option is unavailable (greyed out) either the resolution selected for the traffic raster is
different from that used in the coverage prediction, or there is no coverage array in memory.
Choose how you wish to spread the traffic. Either Live Traffic, Terminal Traffic or a combination of both.

A-53

Specify the expected Circuit Switched traffic in Erlangs.

Specify the expected Packet Traffic in number of GPRS Terminals.

If Polygon Attributes are going to be used for spreading the traffic, select the terminal type and appropriate
polygon attribute.

The last screen of the Traffic Raster wizard allows you to store the Traffic Raster as a file for future
reloading.

A-54

Click on the Finish button.
The Traffic Raster can now be viewed within the 2D Map View window by selecting the Terminal Type
name from the Traffic category of the Show Data Types list:

Note: The display properties of the Traffic Raster can be changed by double clicking with the left mouse
button on the Terminal Type name.
Calculating the GPRS Data Rate, Average Data Rate and Service Area
Data Rate
The GPRS data rate is calculated as the date rate per one timeslot for each pixel. This calculation is capacity
independent.
To produce a GPRS Data Rate array, from the Tools Menu, point to Coverage/Interference Coverage
Wizard or click on the create arrays button in the Map View (2D View) window.

A-55

In the Create Coverage/Interference window select the GPRS Data rate array option, clicking on the OK
button to produce the array.

When the GPRS Data Rate array has been created you can choose to display it on the 2D View by selecting
GPRS Data Rate from the Show Data Types list. By double clicking with the left mouse button on the
GPRS Data Rate category, the display properties can be modified.

A-56

The average data rates per timeslot and service area data rate can also be visualised by selecting the
categories in the Show Data Types menu. The Map Information bar can also be used to aid the
visualisation of GPRS associated information.
When you calculate the data rate array, the average data rate for each subcell array is simultaneously
calculated.
Capturing Cell Traffic and Calculating the required Capacity
Note: Because Traffic Analysis uses the average data rate values, you must calculate the GPRS data rate
array before performing Traffic analysis. The average data rate for each subcell is calculated at the same
time.
To start GPRS Capacity Planning, from the Tools menu, point to Traffic Analyse

Once traffic arrays have been created, click Capture Traffic to collect the traffic information per map pixel
in the cells service area.

A report showing the Captured GPRS traffic is produced:

A-57

If the traffic amount is acceptable, apply it on to the subcells by clicking on the Traffic button.
The Capacity Estimation Algorithm requires GoS criteria for each service type. Set the Quality of Service
Acceptable blocking probability to speech, and the minimum data rate requirement for GPRS. Click the
Analyse button, which also produces a report.
As a result of the capacity calculation, the report that is produced shows statistics of the current TRX
configuration, QoS level and the required TRX amount.

A-58

If you are satisfied with the results click on the Apply Carriers Required on SubCells button.
Complete the Radio Network Plan
After capacity planning, the GPRS planning process follows the normal radio network planning process, that
is, frequency planning and analysis and plan tuning. Coding schemes 1 and 2 provide relative low data rates
and are not considered to cause extra interference to neighbouring non-GPRS cells. As planning is an
iterative process, for GPRS planning, you may want to check the requirements and tune the plan again if
there appears to be too much interference in some areas.

A-59

A-60

EGPRS Overview
EGPRS, an extension to GPRS that allows for higher bitrates by employing EDGE technology at the air
interface. This is accomplished by using an enhanced modulation technique (8 Phase Shift Keying instead of
GSMs Gaussian Minimum Shift Keying).
The stages involved in the EGPRS Planning process are very similar to those within the GPRS Process.
Defining the EGPRS Service Targets
The first phase of planning is to identify the existing sites and new sites where EGPRS is enabled to get
some idea of the required modifications needed before implementing the desired EGPRS service.
In a dimensioning tool, the following questions should be answered:
What kind of data services will be provided?
Where will the service be required?
Updating the Plan with actual Network Data
The information from the current Frequency Plan is needed when planning for EGPRS Networks. Therefore,
before you continue, you must update the plan to meet the actual networks site/cell structure, element
identity, frequency and neighbour information. This is also important for the EGPRS plan implementation
back to the network.
To do this, use the appropriate File Import option in ENTERPRISE.
Defining Data Service Settings
To initialise the EGPRS service, you need to:
Set EGPRS Channel Coding Schemes
Define the timeslot distribution
Set EGPRS Modulation/Coding Schemes
The EGPRS Calculation algorithm is an extension of the GPRS algorithm. As in GPRS the user has to
specify the available Link adaptation families, and therefore MCS codes, that the base station supports. The
MCS codes are organised in Link adaptation families and one or more of these can be selected. Individual
MCS codes cannot be included.

A-61

ASSET supports three link adaptation families (A, B and C) and a user can select one of them, two of them
or all of them. A different set of families can be assigned to different subcells.
To set EGPRS Modulation/Coding Schemes using the ENTERPRSISE Main Menu select Tools 2.5G
EGPRS Modulation/Coding Schemes

Within the EGPRS Average Data Throughput per TS vs Average Connection C/I window you can
populate the tables with default values by clicking on the Set to Defaults button.
EGPRS Default Figures EGPRS Default Figure displayed as a graph

Note: Having populated the tables with default values you can then edit these values should you wish.
-or-
In the C/I(dB) column, define the C/I, for example between 0 and 30 dB and in the MCS code column define
the x axis values.
EGPRS User entered figures EGPRS User entered figures displayed as a
graph

A-62

If the default values have been chosen, tune these figures based on your networks information.
By clicking on the Show Graph button a Plot of C/I(dB) against Throughput(Kb/s) can be viewed. The
values within the columns can be edited by simply clicking on the value and to save the Scheme to the
database click on the Commit button.
Defining Timeslot Distribution
Use the Channel to Transceiver mapping tables to define timeslot distribution. These can be accessed
through the ENTERPRISE Main Menu by selecting Options Channel Maps

Within the Channel to Transceiver Setup window click on the Add Map button. You will then be
prompted to give the Channel to Transceiver Map a name:

Having given the Map a suitable name (as shown above), click on the OK button.

A-63

You will now be asked if you wish to specify
dedicated GPRS channels. As this map is for a
Packet Switched system (EGPRS), select Yes.

You should now be faced with a blank Channel to Transceiver Setup window:

These mapping tables enable you to specify how may carriers are needed to provide a required number of
traffic channels. You need to set the amount of Circuit Switched and Packet Switched control channels as
well as the amount of dedicated Packet (GPRS) traffic channels.
In the box labelled Default Number of Channels per Transceiver enter the default number of traffic
channels that can be supported per carrier (e.g. 8) and click on the Apply button.
Select the Add Transceiver button to populate
the blank set-up window with default figures:

To change the information contained in the table, select a row and click on the Edit Map button.

A-64

You can then specify the following information in the
GPRS Map Editor window:

Click on the OK button to close the GPRS Map Editor window and within the Channel to Transceiver
Setup window click on the Apply button to save the changes to the database.
Channel Occupancy is used to estimate the efficiency with which data packets can be packed into the
available timeslots. This is very useful when you come close to using full network capacity.
The greater the number of available timeslots the better the efficiency with which data packets can be
packed.
The Occupancy Table can be found through the ENTERPRISE Main Menu by selecting Tools 2.5G
Occupancy

As with previous tables, you can populate the columns with default values by clicking on the Set to
Defaults button. Clicking on the Show Graph button will allow you to see a plot of the values, as shown
below:

A-65

If you want to populate the columns with your own values, click on the Remove Graph button to remove
the default values and then click on the Add Graph button to add an blank column. You can then manually
add values (between 0 and 100) into the Occupancy column, where 100 denotes full occupancy.
Once finished click on the Commit button to save the information to the database.
Cell Layers
Within the Cell Layer Configuration window we can either define a different cell layer for EGPRS or we can
use the existing GSM Cell Layer. The Cell Layer Configuration window can be accessed through the
ENTERPRISE Main Menu by selecting Options Cell Layers
Within the Cell Layer Configuration window, highlight an existing Cell Layer, or click on the Add button
to add a specific cell layer for EGPRS.

A-66

Under the General tab this Cell Layer can then
be given an appropriate name:

Within the Coverage Type tab of the Cell Layer Configuration window use the drop down menu to select
the Channel to Transceiver Map previously created:

Within the Carrier Layers tab select the carrier layers to be used on the Cell Layer and define the Coverage
Schema Threshold values under the Coverage Thresholds tab. Click on the Apply button followed by the
Commit button to save the changes to the database.

A-67

In ENTERPRISE, EGPRS information is stored on the Cell Layer Level. The subcell is considered to
provide an EGPRS service when you have selected the Enable GPRS and the Enable EGPRS check-
boxes within the (E)GPRS tab of the Site Database window:

Having selected the above check-boxes the following options are available for selection within the
(E)GPRS tab:
Dedicated PBCCH: This box should be selected to instruct the software that
another BCCH timeslot for Packet Data control is being
used.
If this box is unselected the tool ignores NGPRSCTL in the
channel map this means that no timeslots have been
reserved for GPRS control so these timeslots are
available for CS traffic.
GPRS Coding Schemes (CCS 1,2,3,4): Choose at least one supported Channel Coding Scheme.
EGPRS Link Adaptation Families
(A,B,C):
At least one Link Adaptation Family should be selected.
Traffic Total GPRS + EGPRS: Total value of the Packet Switched Traffic (Kbit/s)
served by subcell. This value can be set manually for
each subcell or set automatically during the Traffic
Analysis process.
Traffic - % of (E)GPRS 8-PSK: This value is an estimate of the percentage of EGPRS
traffic that is using 8PSK modulation, and therefore the
lower power output.
Note: If all cells within one filter support the same coding schemes the above configuration can be done
using the Global Edit facility.

A-68

The EDGE modulation scheme puts new requirements on the linearity of the power amplifier: as apposed to
GMSK, 8-PSK does not have a constant envelope.
Network Operators have stipulated that EDGE-capable transceivers must fit in a base station cabinet
designed for standard transceivers and also that EDGE transceiver performance is acceptable in terms of
both transmit spectrum and heat dissipation.
To achieve the above requirements a typical high-power EDGE transceiver might need to reduce its average
transmit power when transmitting 8-PSK. Compared to GMSK, the average power decrease (APD) could be
between 2 and 5 dB.
Within ASSET the APD value can be entered on the Cell
Layer Level of each subcell under the Antenna/TRX tab:

Note: If all cells within one filter have the same APD value it can be set using the Global Edit facility,
under the 2.5G tab.
Calculating and Analysing the EGPRS Service Area
The definition of cell-specific EGPRS service areas follows the normal coverage planning process.

A-69

To calculate Coverage Predictions, from the
ENTERPRISE Main Menu select Tools
Coverage/ Interference Predictor or click
on the Predictor button ( ) from the
ENTERPRISE Toolbar.

Having run the Predictor tool go to the ENTERPRISE Main Menu and select Tools Coverage/
Interference Coverage Wizard or select the Create Coverage array button ( ) from the
ENTERPRISE Toolbar, to visualise on the map the service areas of the cells where EGPRS is enabled.
This is done by selecting the Best Server (GPRS/EGPRS) option:

You can then display the array in the 2D Map View window.
Defining Terminal Types using Data Service
For the Traffic and Capacity Planning process, an estimate of the EGPRS terminal distribution is required as
well as an idea of the services and data rate demand of the terminals.
To define an EGPRS Terminal Type go to the ENTERPRISE Main Menu and select Options Terminal
Types
Within the Terminal Types window, click on the Add button. Within the General tab of this window
change the terminal type name so something more appropriate:

A-70

Also within the General tab ensure that the Packet Switched (GPRS) option is selected and the EGPRS
check-box is ticked.
Within the Cell Layer tab link the Terminal type to one or more layers by moving the chosen Cell Layer
from the Available pane to the Selected pane using the > button.

>
Within the Clutter, Vectors and Polygon tabs, define how the terminal type is to be distributed over the 2D
Map View (i.e. Weight or Density with associated values per Clutter category).

A-71

Within the GPRS/EGPRS tab, enter the Mean busy hour capacity (kb/s) of the terminal (e.g. 1 kb/s). This
figure being an estimate of the traffic going through in a busy hour, per terminal type.
Also enter the maximum number of timeslots supported by the terminal (theoretically up to 8 but realistically
up to 4).

Click on the Apply button followed by the Commit button to save the terminal type to the database.
Distributing Terminals and Creating Traffic Arrays
Having opened a 2D Map View window display the desired area together with sites and suitable map data.
From the ENTERPRISE Main Menu select Tools Traffic Traffic Raster Wizard
Within the First screen of the Traffic Raster wizard select the appropriate 2D Map View window and/or
view. Click on the Next> button to progress.

A-72

In the Second wizard screen choose one or more Terminal Types from the list. For each Terminal Type you
select, a separate traffic array is created:

Note: If you wish to spread traffic that you have applied to polygons by clutter type, ensure this check-box
is selected .
Click the Next> to continue through the wizard.
Within the next screen of the wizard a desired resolution is chosen, using the drop down menu. The memory
required to create the resolution chosen is shown. Generally speaking, the less pixels used, the faster the
process will be. Click on the Next> button.
You can have the opportunity to spread traffic
just over the area with coverage, by selecting the
appropriate check-box:

Note: If this option is not available (i.e. greyed out) one reason would be that the resolution chosen in
the previous screen is not the same resolution used for the Coverage Prediction.
Click on the Next> button to progress through the wizard.
In this screen the opportunity to Spread Live Traffic or use the specified traffic (Terminal Type) is
available, click on the Next> button.

A-73

In the Traffic Terminals screen specify the expected packet traffic in number of Terminals:

Progress to the last screen using the Next> button. On the Final wizard screen click on the Finish button
to create the Traffic Raster.
The Traffic Raster can then be viewed in the 2D Map
View window, by selecting the Terminal Type from
the Show Data Types list under the Traffic category:

By double clicking on the Terminal Type name, within the Show Data Types list, its display properties can
be altered:

A-74

Calculating the EGPRS Data Rate, Average Data Rate and Service Area
Data Rate
The EGPRS data rate is data rate per one timeslot per one pixel and it is capacity independent.
The EGPRS Data Rate array can be created by going to the ENTERPRISE Main Menu and selecting Tools
Coverage/ Interference Coverage Wizard or alternatively, by selecting the Create Coverage array
button ( ) from the ENTERPRISE Toolbar.
The appropriate box can then be selected within the Create Coverage/Interference window:

When you have created the EGPRS data rate array, you can choose to display it on the 2D Map View
window by selecting the EGPRS Data rate option within the Coverage category of the Show Data Types
list:

A-75

Having calculated the data rate array, the average data rate for each timeslot array is simultaneously
calculated.

Service Area EGPRS Data Rate shows a data rate for the current number of allocated TRXs. A Low value
indicates to the radio planner that more than enough TRXs have been allocated and a Big value would
indicate an insufficient number of TRXs.
Capturing Cell Traffic and Calculating Required Capacity
Note: Because Traffic Analysis uses the average data rate values, you must calculate the EGPRS Data
rate array before performing Traffic Analysis. The Average data rate for each subcell is calculated at the
same time.
To commence Capacity Planning go to the ENTERPRISE Main Menu and select Tools Traffic
Analyse

A-76

Within the Traffic Analysis window click on the Capture button within the Traffic pane of the window:

This will collect the traffic information per map pixel in the cell service area and produce a report in
Microsoft Excel:

If the traffic amount is acceptable, apply it to the subcells cells by clicking on the Traffic button within the
Apply on to subcells pane of the window:

A-77

The traffic figures (shown in the report) can now be viewed on the subcells within the Site Database
window:

The Capacity Estimation Algorithm requires GoS criteria for each service type. Set blocking probability to
speech (Erlang B) as well as the traffic per customer figure.
Click on the Analyse button to produce a report (in Microsoft Excel) presenting statistics of the current
TRX configuration, QoS level and the required TRX amount.
If you are satisfied with the results click on the Apply Carriers Required on Subcells button.
Complete the Radio Network Plan
After capacity planning, the EGPRS planning process follows the normal radio network planning process,
that is, frequency planning and analysis and planned tuning.

A-78

Appendix A - Glossary of Terms

ABBR MEANING
2G Second Generation
3G Third Generation
3GPP Third Generation Partnership Project
4G Fourth Generation
APN Access Point Name
ARQ Automatic Request for Retransmission
ATM Asynchronous Transfer Mode
AuC Authentication Centre
BCCH Broadcast Control CHannel
BCS Block Check Sequence
BEC Backward Error Correction
BG Border Gateway
BH Block Header
BLER BLock Error Rate
BS Base Station
BS Billing System
BSC Base Station Controller
BSN Block Sequence Number
BSS Base Station Subsystem
BSSGP BSS GPRS Protocol
BTS Base Transceiver Station
BVC BSSGP Virtual Circuit
BVCI BSSGP Virtual Circuit Identifier
CCCH Common Control CHannel
CDMA Code Division Multiple Access
CDR Charging Detail Record
CG Charging Gateway
CH CHannel ?
C/I Carrier/Interference Ratio
CNLS Connectionless
CONS Connection-Oriented
CRC Cyclic Redundancy Check
CS Circuit Switched
CS-x Coding Scheme-x {x = 1-4}
CSD Circuit Switched Data
DHCP Dynamic Host Control Protocol
DNS Domain Name Server
ECSD Enhanced Circuit Switched Data
ED&C Error Detection and Correction
EDGE Enhanced Data rate for GSM {Global} Evolution
EGPRS Enhanced General Packet Radio Service
EIR Equipment Identity Register
ETSI European Telecommunications Standards Institute
FCS Frame Check Sequence
FEC Forward Error Correction
FH Frame Header
FR Frame Relay
GAA GPRS Application Alliance
GGSN Gateway GPRS Support Node
GMM GPRS Mobility Management

A-79

ABBR MEANING
GMSK Gaussian Minimum Shift Keying
GPRS General Packet Radio Service
GSM Global System for Mobile Communications
GSN GPRS Support Node
GTP GPRS Tunnelling Protocol
GTP-U GPRS Tunnelling Protocol Uplink
HLR Home Location Register
HPLMN Home PLMN
HSCSD High Speed Circuit Switched Data
HTML Hypertext Markup Language
HTTP Hypertext Transfer Protocol
IMEI International Mobile Equipment Identity
IMSI International Mobile Subscriber Identity
IP Internet Protocol
ISDN Integrated Services Digital Network
ISO International Standards Organisation
ISP Internet Service Provider
LA Location Area
LAC Location Area Code
LAI Location Area Identity
LIG Legal Intercept Gateway
LLC Local Link Control
MAC Medium Access Control
MAI Mobile Applications Initiative
MAP Mobile Applications Part
MCC Mobile Country Code
MM Mobility Management
MNC Mobile Network Code
MS Mobile Station
MSC Mobile Services Switching Centre
MSIN Mobile Subscriber Identification Number
MT Mobile Terminal
NMS Network Management System
N-PDU Network Packet Data Unit
NSAPI Network Service Access Point Identifier
NS-VC Network Services Virtual Services
OMC Operations and Maintenance Centre
OSI Open Systems Interconnection
PACCH Packet Associated Control CHannel
PAD Packet Assembler-Disassembler
PAGCH Packet Access Grant CHannel
PBCCH Packet Broadcast Control CHannel
PCCCH Packet Common Control CHannel
PCM Pulse Code Modulation
PCU Packet Control Unit
PDA Personal Data Assistant
PDCH Packet Data CHannel
PDN Packet Data Network
PDP Packet Data Protocol
PDTCH Packet Data Traffic CHannel
PDTCH-D Packet Data Traffic CHannel Downlink
PDTCH-U Packet Data Traffic CHannel Uplink
PDU Packet Data Unit
PH Packet Header

A-80

ABBR MEANING
PIM Packet Idle Mode
PLMN Public Land Mobile Network
PNCH Packet Notification Channel
PPCH Packet Paging Channel
PPM Packet Paging Message
PRACH Packet Random Access Channel
PS Packet Switched
PSI Packet data specific System Information
PSK Phase Shift Keying
PSN Packet Switched Network
PSPDN Packet Switched Public Data Network
PSTN Packet Switched Telephone Network
PTCCH Packet Timing Advance Control CHannel
PTCCH-D Packet Timing Advance Control CHannel Downlink
PTCCH-U Packet Timing Advance Control CHannel Uplink
PTCH Packet Traffic CHannel
PTM Packet Transfer Mode
PTM Point to Multipoint
PTM-G Point to Multipoint-Group
PTM-M Point to Multipoint-Multicast
P-TMSI Packet Temporary Mobile Subscriber Identity
PTP Point To Point
PVC Permanent Virtual Circuit
QoS Quality of Service
RA Routing Area
RAC Routing Area Code
RAI Routing Area Identity
RAND Random Number
RBS Radio Block Structure
RLC Radio Link Control
RR Radio Resource
SAP Service Access Point
SAPI Service Access Point Identifier
SDU Service Data Unit
SGSN Serving GPRS Support Node
SIM Subscriber Identity Module
SM Session Management
SMS Short Message Service
SNDCP SubNetwork Dependent Convergence Protocol
SNN SNDCP Network PDU Number
SRES Signature Response
SVC Switched Virtual Circuit
TA Timing Advance
TBF Temporary Block Flow
TCP/IP Transmission Control Protocol/Internet Protocol
TDMA Time Division Multiple Access
TE Terminal Equipment
TFI Temporary Flow Identity
TFT Traffic Flow Template
TI Transaction Identifier
TID Tunnel IDentifier
TLLI Temporary Logical Link Identifier
TMSI Temporary Mobile Subscriber Identity
TOS Type Of Service

A-81

ABBR MEANING
TRX Transmitter-Receiver
TS Time Slot
UDP User Datagram Protocol
UMTS Universal Mobile Telecommunications System
URL Universal Resource Locator
USF Uplink State Flag
VC Virtual Circuit
VLR Visitor Location Register
V-PLMN Visitor PLMN
VPN Virtual Private Network
WAP Wireless Access Protocol

GPRS Technology, Planning and Optimisation

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

GPRS Technology, Planning and Optimisation

Hochgeladen von

Copyright:

Verfügbare Formate

Copyright 2005 AIRCOM International Ltd

All rights reserved

Forward Error Correction:

Scheme Code rate USF Pre-

rom hotspots can be profitable.

Das könnte Ihnen auch gefallen