Documente Academic
Documente Profesional
Documente Cultură
Ludwigsburg
Originator(s)
A. Grtner /
U. Birkel
Domain:
Division:
Rubric:
Type:
Distribution codes:
RCD
Operations
Radio Network Planning
Guidelines
Distribution:
Stuttgart:
C. Brechtmann
K. Eckert
R. Collmann
D. Adolphs
K.-D. Frasch
F. Engmann
K. Daniel
K. Heinlein
H.-G. Tuechle
Cc:
M. Albani
J.D. Calvet
Vlizy:
P. Godet
E. Baudienville
C. Fortuit
L. Carre
J.M. Gabriagues
R. Rouvrais
P. Keryer
J.P. Jardel
F. Collin
Abstract:
This document describes the GSM feature GPRS from the radio network planning
point of view. Basics on GPRS are described in the first part of the document, the
second part focuses on GPRS engineering guidelines. Note: The document
contains industry confidential information.
Keywords: GPRS; packet data; engineering rules;radio network planning; RNP
Name
Date
Signature
C. Brechtmann
Approval
K. Eckert
R. Collmann
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
1/56
Table of Contents
1
Change History............................................................................5
Referenced Documents.................................................................5
Scope..........................................................................................6
Abbreviations..............................................................................6
Basics on GPRS............................................................................8
5.1
Introduction.............................................................................................. 8
5.2
5.2.1
5.2.2
PDCH Multiplexing............................................................................... 11
5.2.3
TBF Establishment.............................................................................. 13
5.2.4
5.2.5
5.3
5.3.1
Channel coding................................................................................... 21
5.3.2
Measurements.................................................................................... 21
5.3.3
Power Control...................................................................................... 22
5.3.4
5.3.5
Routing Areas...................................................................................... 23
5.3.6
5.3.7
Quality of Service................................................................................ 24
5.3.8
5.3.9
BSS/CAE Parameter............................................................................. 25
6.1
6.1.1
6.1.2
6.2
6.2.1
6.2.2
Frequency Planning............................................................................. 33
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
2/56
6.2.3
6.3
6.3.1
Coverage Planning.............................................................................. 36
6.3.2
Interference Analysis..........................................................................36
6.3.3
6.3.4
GPRS Capacity.................................................................................... 37
6.4
6.4.1
6.4.2
Summary...................................................................................39
List Of Tables
Table 1: Achievable data rates for the Coding Schemes CS 1 to 4.......................21
Table 2: GPRS Averaging parameters for uplink and downlink measurements.....21
Table 3: Reliability Classes.................................................................................... 24
Table 4: C/I requirement according to ETSI for GPRS carriers...............................29
Table 5: Level requirement according to ETSI for GPRS carriers...........................30
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
3/56
List Of Figures
Figure 1: New logical entities in the GPRS architecture: SGSN and GGSN..............8
Figure 2: Alcatel GPRS solution............................................................................... 9
Figure 3: PDCH Multiplexing................................................................................. 11
Figure 4: PDCH Multiplexing of different users on PDCHs.....................................12
Figure 5: UL TBF establishment( one phase access on CCCH)..............................13
Figure 6: DL TBF establishment( one phase access on CCCH)..............................14
Figure 7: Coordination of dynamic channel allocation via BSC and MFS A935......15
Figure 8: Dynamic allocation of PDCHs per Group: PDCH resource control..........16
Figure 9: TBF handling per link............................................................................. 17
Figure 10: TBF resource allocation........................................................................17
Figure 11: Parameter and Bitmap example.........................................................18
Figure 12: Subdivision of a Location Area in GPRS Routing areas (RA).................23
Figure 13: Definition of Reference Performance Point..........................................27
Figure 14: Dependency of data throughputs as a function of level (no
interference).................................................................................................. 28
Figure 15: GPRS coverage for different coding schemes (schematic)...................36
Figure 16: Block Error Rate over C/I of the GPRS coding schemes (TU50, no FH). 43
Figure 17: Block Error Rate over C/I of the GPRS coding schemes (TU3, no FH)...44
Figure 18: Block Error Rate over C/I of the GPRS coding schemes CS-1 and CS2. 44
Figure 19: Maximum throughput in kbyte/s over C/I (TU50, no FH)......................45
Figure 20: Maximum throughput in kbyte/s over C/I for CS-1 and CS-2................46
Figure 21: BLER over Eb/N0 of the GPRS coding schemes (TU50, no FH)...............47
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
4/56
1 Change History
Date
Editio
n
Status
Author
Comments
March199
9
01
Draft
A. Grtner
Document Creation
Aug. 1999 01
Proposal 01
U. Birkel
Sept. 1999 01
Release
U. Birkel
2 Referenced Documents
[1]
ETSI specification
[2]
3BK
DSZZA
[3]
ETSI document
[4]
ETSI document
[5]
ETSI document
[6]
ETSI specification
[7]
ETSI specification
[8]
ETSI specification
[9]
ETSI specification
http://aww.mcd.alcatel.com/mcd/technic/index.htm
[12] 3BK
11202
DSZZA
[13] NEM
Meeting
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
5/56
Velizy
[14] 3BK
11202
DSZZA
[15] 3BK
09417
PBZZA
GPRS Dimensioning
3 Scope
The document describes GPRS Radio Network Planning relevant aspects. It is the
scope of the document to provide an RNP engineering guideline for GPRS
networks.
Chapter 5 gives an overview on GPRS, focussing on the PDCH handling and user
multiplexing as well as on basic GPRS features, which are interesting from the
RNP point of view.
GPRS RNP engineering rules are specified in Chapter 6 by defining the design
figures and by describing the methodology for initial and detailed GPRS radio
network designs.
4 Abbreviations
ARQ
BCCH
BCS
BER
BLER
BSC
BSS
BSSGP
BTS
BVC
CCCH
CS
CS-x
DL
DRX
DSP
FEC
FH
Gb
GGSN
Gi
Gn
GPRS
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
6/56
GPU
Gs
GSM
HPLMN
IMSI
IP
ISDN
LA
LLC
MAC
MFS
MO
MS
MSC
MT
NCx
NMC
NS
NSS
NS-VC
O&M
OAM
OMC-R
PACCH
PCH
PCU
PDCH
PDP
PDU
PLMN
PPCH
PRACH
PS
PSPDN
PTM
PTM-G
PTM-M
PTP
PVC
QoS
RA
RACH
RLC
SDCCH
SDU
SGSN
SMS
SPDCH
TBF
TCP
TDMA
TLLI
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
7/56
TRX
TS
UL
USF
VLR
Transceiver
Timeslot
Uplink
Uplink State Flag
Visitor Location Register
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
8/56
5 Basics on GPRS
5.1 Introduction
GSM is based on a circuit switched (CS) concept, which means that a connection
is established between two terminals, that is maintained during the whole
session, reserving the channel resource exclusively. GPRS (General Packet Radio
Service) has been introduced as a new GSM feature to provide end-to-end packetswitched data transmission between MS users and fixed packet data networks.
With GPRS, the radio interface resources are allocated dynamically; the
transmission rate can be varied. The available channel resource is shared by
multiple connections, which means that a user only occupies network resources
when data packets are transmitted (bursty traffic nature). The mobile users are
multiplexed together on one or on several radio TS reserved for GPRS. This is
very efficient if only data bursts have to be transmitted and not continuous data
streams.
Packet switched services can be subdivided into connection oriented services and
connectionless services which are also called datagram services. In the latter
case, each packet contains the complete destination and originating address and
it passes through the network independently from other packets, so that packets
between two communication partners can take different paths through the
network and even overtake each other. So, the routing of the data packets is
possible without a connection establishment. For connection oriented services,
the path through the network is given explicitly for the duration of the virtual
connection. The set-up and release of the virtual connection needs a certain
signalling and switching effort. Both the GSM radio part and the network
architecture are affected by the implementation of GPRS. As shown in Figure 1,
the new backbone network architecture comprises two main elements:
the SGSN (Serving GPRS Support Node) which manages mobility (keep track
of MS location), security functions (encryption), data compression, access
control and charging.
the GGSN (Gateway GPRS Support Node) provides interaction with the
external packet data networks.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
9/56
HLR
BSS
GPRS
MS
MSC/VLR
ISDN, PSTN
TE
SGSN
GGSN
GPRS Backbone
INTERNET,
X25
Data
Signalling
Figure 1: New logical entities in the GPRS architecture: SGSN and GGSN
The Alcatel solution consists of a software upgrade in the BSS and a new
hardware element called Alcatel 935 MFS (Multi-BSS Fast packet Server), which is
typically located beside the transcoder at the MSC site and can be shared by
several BSSs as shown in Figure 2. In addition, it comprises a backbone network
architecture containing the mentioned GPRS Support Nodes.
OMC-R
SGSN
Gb
MFS
(PCU)
Abis
BTS
Abis
BSC
Gb
Ater
MSC
TC
Step 1 end of 1999 shall be in line with SMG 28 (Release B 6.2): This first
GPRS implementation step includes GPRS ETSI phase 1 features, which are
absolutely needed for an operator to provide GPRS service. It is a short term
solution for a first commercial introduction of GPRS. This solution is foreseen
to work with prototype GPRS MS.
Step 1 shall be in line with SMG 29 around mid 2000 (Release B 6.2 M):
Additional interesting features, which are needed by an operator in a service
deployment phase will be incorporated (e.g. Master PDCH). This solution is
then foreseen to work with commercial GPRS Mobiles and is not compatible
with SMG 28.
For more detailed information on the technical features of the Alcatel GPRS
implementation please refer to [10], [17].
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
10/56
PDCH
Multiplexing
and
dynamic
In implementation step 1 only one TRX per cell can be dedicated to GPRS service.
On this carrier, any time slot can be configured to allow the transmission of data
packets between the mobile station and the network. This physical channel or
timeslot is then called a PDCH (Packet Data Channel).
Per TRX the available time slots are dynamically shared by circuit switched (CS)
and GPRS traffic, i.e. n timeslots can be used for CS and the remaining 8-n
timeslots for GPRS, while n is variable between min. 0 and max. 8 (dynamic
channel allocation).
The packets of different users can be transmitted on one PDCH (user
multiplexing), furthermore one user can transmit packages on several PDCHs
(multislot capability).
Data packets are transmitted between the MS and the NW on a PDCH via a
Temporary Block Flow (TBF).
Before the PDCH multiplexing and the TBF establishment is described in more
detail, the mapping of the physical channel on logical channels is explained in the
next section.
5.2.1 Mapping of logical channels on PDCH
The packet data logical channels are mapped on a PDCH as follows:
PCCCH (Packet Common Control CHannel) used to initiate packet transfer
PRACH (Packet Random Access CHannel)
PPCH (Packet Paging CHannel)
PAGCH (Packet Access Grant CHannel)
PBCCH (Packet Broadcast Control CHannel) used for broadcasting system
information
PTCH (Packet Traffic CHannel) used for data transmission and associated
signalling
PTCCH (Packet Timing Advance Control CHannel) used for continuous timing
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
11/56
the circuit switched design are used instead. The usage of a MPDCH has thus the
following advantages:
Reduced BSC and CCCH load and thus improved access delay
4,615
PDCH
1
Frame # 0
Edition
RCD
Block #
01
5
2
B0
B1
277195762.doc
B2
13
17
21
2 26
30
34
3 39
43
B4
B5
Sept.
99
B6
B7
B8
B9
B10
CONFIDENTIAL
1 OC/NPL
(52)-multiframe
= 52
TDMA frames
( 240
ms)
3DF
00995
0005
UAZZA
12/56
47
1
B11
Depending on the coding scheme different effective data throughput rates per
timeslot can be achieved ( 20kbit/s/timeslot see chapter 5.3.1).
For packet data transfer, the data is transmitted on a Temporary Block Flow
(TBF). For a TBF one or more PDCHs are allocated and it comprises a number of
blocks. A TBF is temporary and is maintained only for the duration of the data
transfer. Each TBF is unidirectional, i.e. uplink and downlink TBFs for the same
link are uncorrelated. The TBF of each user is identified by a Temporary Flow
Identity (TFI).
The maximum amount of PDCHs per TBF is limited by O&M or by the mobiles
multislot capability, whichever is lower. The maximum amount of TBFs per PDCH
is also limited by O&M (user multiplexing).
As shown in Figure 4 the TBFs with TFI = 24 and 17 are using several PDCHs,
whereas the user with TFI = 5 does not support the multislot capability and
therefore is only allocated on one PDCH. Further the three TBFs are multiplexed
block wise on the allocated PDCHs.
This packet oriented approach allows optimum usage of the available radio
resource.
B0
B1
B11
B2
B3
B4
B5
B6
B7
B8
B9
B0
B1
B2
B10 B11 B11
B3
B4
B5
B6
B7
B8
B9
The control of the multiplexing of different MSs on an uplink PDCH uses the USF
(Uplink State Flag) mechanism. The USF is a token which is distributed by the
network at UL TBF establishment (one USF per allocated PDCH). The uplink
multiplexing is scheduled by USF values included in the header of each RLC
downlink block. The USF value in downlink block Bn schedules the uplink block
Bn+1, i.e. MS which has been allocated this USF, can use Bn+1 either as a PDTCH
or a PACCH. On the master PDCH, a specific USF value is reserved (USF = FREE)
to schedule a PRACH. Another USF value is reserved to schedule a block for
PACCH related to a downlink TBF.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
13/56
B10
Packet access can be done in either one phase or 2 phases. 2 phase access is
necessary to request a RLC unacknowledged mode and to send the MS multislot class, when access is on CCCH. In this document only the 1 phase access
will be explained.
The packet access uses either the PCCCH (if MPDCH available) or the CCCH
The UL TBF establishment scenario in Table 5 explains the example of the one
phase access on the CCCH (for other scenarios see [11]).
(1) The Channel Request is received on the RACH and indicates one phase
access. In case the request can be satisfied, an Immediate Assignment message
is sent to the MS with a TFI, one allocated PDCH with its USF, the initial timing
advance value (calculated on reception of the Packet Channel Request) and the
Timing advance Index (to be used for continuous timing advance index). A timer
is activated to give time to the MS to receive this command.
(2) At timer expiry a Packet UL Assignment message is sent to MS, assigning the
same resources as those assigned previously, but without the initial timing
advance value. Then the network forces the MS to send a Packet Control
Acknowledgement (polling indication) to be sure that the UL TBF has been
successfully established.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
14/56
(3) Then the MS listens to the allocated PDCHs to detect its USF. On reception of
the Packet Control Ack, the network begins to schedule UL blocks, with the USF
mechanism
(4) The MS transmits UL blocks when allowed by the network. The MS shall
provide its TLLI in RLC data blocks, until the end of the contention resolution (i.e.
reception of the Packet UL ack/Nack with its TLLI)
(5) The network acknowledges as soon as one of these blocks is correctly
received (i.e. the MS using the TBF is non-ambiguously identified)
DL TBF establishment
The procedure may be entered either when the MS is in packet idle mode
(access on PCCCH or CCCH) or when the MS is in packet transfer mode (i.e. an
UL TBF is already established, then the access is performed on the PACCH).
The DL TBF establishment scenario is explained at the example of the one phase
access on the CCCH (for other scenarios see [11]).
(1) An Immediate assignment is sent with a TFI, one PDCH and a Timing Advance
Index (no initial timing advance value is provided). A timer is activated to give
time to the MS to take into account this message. At timer expiry, a packet DL
Assignment message is sent with the TFI, PDCHs (additional PDCHs may be
allocated, since only one PDCH can be allocated when using CCCH) and the
timing advance index.
(2) The network forces the MS to acknowledge to be sure that the DL TBF has
been successfully established and to be able to compute an initial timing
advance value.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
15/56
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
16/56
Allocation
Request
Deallocation
Request
Load Indication
Figure 7: Coordination of dynamic channel allocation via BSC and MFS A935
Timeslots usable for PDCH are grouped into PDCH groups (only one in step 1).
One PDCH group contains time-slots belonging to the same TRX, having the same
frequency configuration without holes (=consecutive timeslots).
5.2.4.1PDCH resource control
As the circuit switched services should be served with priority, a parameter
defining the maximal number of PDCHs within one carrier/group can be set
(MAX_PDCH_GROUP, see below). When the maximal number of time slots is
reached, no more time slots can be allocated to packet data traffic. In case of
high BSC high traffic load, this maximum value is automatically reduced to
MAX_PDCH_HIGH_LOAD, so that there are enough timeslots reserved for circuit
switched traffic. The following parameters are tuneable in order to achieve an
optimum resource utilisation and can be set via O&M:
MIN_PDCH_GROUP
Minimum number of PDCHs per cell which can be activated for GPRS (Range 0 to 8,
Default = 0)
MAX_PDCH_GROUP
Maximum number of PDCHs allocated in a PDCH group in case of normal BSC load
(Range 1 to 8, Default = 8)
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
17/56
MAX_PDCH_HIGH_LOAD
Maximum number of PDCHs allocated in a PDCH group when the BSC has indicated a
high BSC traffic load (Range 0 to 8, Default = 1)
Figure 8 shows the dynamic allocation algorithms of PDCHs. One can observe
that timeslots are allocated by the BSC on MFS request (and deallocated, if no
longer needed). If the maximum number of PDCHs is reached, new requests are
rejected for that group. If the CS load situation changes from normal load to high
load, the MFS limits the number of allocated PDCHs to MAX_PDCH_HIGH_LOAD.
The MFS deallocates PDCHs as soon as exceeding PDCHs become empty and
marks them as not usable for new TBFs (BSC soft pre-emption).
Maximum number of
PDCHs is reached
Allocated PDCHs
MAX_PDCH_GROUP
MAX_PDCH_HIGH_LOAD
MIN_PDCH_GROUP
time
Normal BSC load
Cell is created
A GPRS MS requests
4 timeslots
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
18/56
MAX_UL_TBF_PDCH
Maximum number of UL TBFs per PDCH. Range: [1;7], Default value: 7
MAX_DL_TBF_PDCH
Maximum number of DL TBFs per PDCH. Range: [1;9],.Default value: 9.
MAX_PDCH_PER_TBF:
Maximum number of PDCHs which can be allocated to a single TBF. Range: [1;5], Default
value: 5 Theoretical max. bitrate per MS in Alcatel step 1 implementation (CS-2):
5*12kbit/s = 60kbit/s/user. However the bit rate per user is also limited by the multislot
capacity of the mobiles (see chapter 5.2.4.4).
Figure 9: TBF handling per link
MAX_UL/DL_TBF_PDCH
N_TBF_PER_PDCH
Empty
Full
Active
Busy
MAX_PDCH_PER
_TBF
TBF request
(MS multi-slot
class)
STEP 1:
Selection of
MS supported
multi-slot
conf.
STEP 2:
Analysis of
concurrent
TBF
constraints
STEP 3:
PDCH
selection
Already allocated
PDCHs can
be used
PDCH request to
BSC
Step 4:
PDCH
choice
PDCH allocated by
BSC
Step1: The multi-slot class of the MS (when known) is interpreted and the
O&M parameter MAX_PDCH_PER_TBF. Based on this the maximum
applicable amount of PDCHs for this TBF request can be determined.
Step2: The TBF establishment on one direction shall comply with
constraints imposed by potential concurrent TBF on the other direction
Step 3: To select a PDCH the following command is applied
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
19/56
If n_allocated_pdch<MAX_PDCH_GROUP/MAX_PDCH_HIGH_LOAD then an
ALLOCATION REQUEST is sent to the BSC with the following parameters:
n_MS_requested, MAX_PDCH_GROUP or MAX_PDCH_HIGH_LOAD, bitmap giving
the existing GPRS channels with their status.
with
n_consecutive_pd
ch
n_allocated_pdch
n_MS_requested
the
request is served on
the
than
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
20/56
the time-slots on the centre of this PDCH group are seen as the set of channels to
keep free (i.e. with the lowest priority, for CS traffic). If some TS have been
allocated, the adjacent time-slots are seen as the channels to keep free.
5.2.4.4MS CAPABILITIES
In order to evaluate bitrates per user, the resource allocation has also to be
considered from the MS point of view. Different MS classes and types are defined
for GPRS:
First of all three classes of GPRS MSs are supported:
Class-B MS can monitor control channel for GPRS and other GSM services
simultaneously, but can only operate one set of services at one time.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
21/56
PDP Activation procedure: MS sends request to SGSN, SGSN informs GGSN, the
GGSN creates a context and sends acknowledge to SGSN, SGSN sends
acknowledge to MS Data transmission is possible
When PDP context is activated, the SGSN has a logical tunnel between MS and
GGSN and MS can send data packets as well as computers in external data
networks can send packets to MS using MSs PDP address as destination.
5.2.5.3Mobility Management
Instead of Location Area, GPRS uses Routing Areas to group cells. RA is a subset
of LA (see chapter 5.3.5). Mobiles can be in the following states from the NW
point of view:
IDLE: MS is not known by the network
READY: MSs location is known in accuracy of cell, MS must inform its location
after every cell change, MS can initiate Mobile Originating transfer at any time,
SGSN does not need to page MS before Mobile Terminating data transfer
STANDBY: MSs location is known in accuracy of Routing Area, MS must inform its
location after every Routing Area change (no need to inform cell changes within
the same RA), Before the network can perform Mobile Terminating data transfer,
the MS must be paged within the RA. MS may initiate Mobile Originating data
transfer at any time.
Note that the upper states are defined from the mobility management point of
view, from the radio resource point of view the following states are distinguished:
PACKET IDLE MODE: In this mode, the MS is not allocated any radio resource on a
PDCH, it listens to the PBCCH and PCCCH or, if those are not provided by the
network, to the BCCH and the CCCH.
PACKET TRANSFER MODE: In this mode, the MS is allocated radio resource on one
or more PDCHs for the transfer of LLC PDUs.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
22/56
RLC
data
[bytes]
unit
RLC data
[kbit/s]
unit
CS-1
22
20
CS-2
32
30
12
CS-3
38
36
14,4
CS-4
52
50
20
throuput
The most protected mode is CS1, which is therefore always used for signalling.
Depending on the radio condition CS1 or CS2 are used for traffic. This choice is
done by the MFS, according to the reception quality and level measurements
performed by the BTS. The performance of coding schemes and the coding
scheme adaptation algorithms will be described in more detail in Annex A.
5.3.2 Measurements
Downlink Measurements
MS measurement reports are transmitted from the MS to the MFS in each DL(N)
Acknowledge command containing the averaged level C of the serving (C_VALUE)
and RXQUAL averaged over the received blocks. The reporting period depends on
the parameters DL_ACK_PERIOD or DL_NACK_PERIOD (Range: 1 to 64,
Default=16). This period defines the number of received data blocks between
each DL Ack. So only when the MS receives data, the measurement report is sent.
Thus the reporting period is not tuneable and it varies significantly.
Uplink Measurements
At each received block, level and quality are computed (over 4 TDMA frames) and
sent to the MFS. The measurements are averaged, the averaging algorithms are
quite complex.
The relevant parameters for UL and DL are [13]:
LEVEL
QUALITY
DOWNLINK
T_AVG_T, T_AVG_W
DL_(N)ACK_PERIOD
UPLINK
K_AVG_L
KAVG_Q
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
23/56
The evaluation is similar to the CS approach and is updated every 0.96 sec.
A further important figure which is related to the Radio Link is the Retransmission
rate which is not measured or reported via the air interface but reported by the
MFS. However it is not used for Radio Link Relevant Algorithms (initially it was
planned to use this parameter for dynamic coding scheme adaptation, but has
been withdrawn since it is not always an accurate parameter).
5.3.3 Power Control
In step 1 power control is only implemented on the uplink in an open loop
configuration, i.e. the MS adapts its output power per block (i.e. 4 timeslots)
based on the received average signal strength assuming the same path loss in UL
and DL. When accessing the NW on the (P)RACH the MS uses the output power
defined by (GPRS_)MS_TXPWR_MAX_CCH, which is broadcasted by the (P)BCCH.
In case of closed loop power control (not available in step 1) the output power is
commanded by the NW site as for CS traffic.
5.3.4 Cell re-selection and re-direction instead of handover
5.3.4.1Cell re-selection
There are no handovers for GPRS mobiles. Roaming to other cells is performed by
cell (re)-selection in packet idle mode. When a mobile in packet transfer mode
leaves the coverage range of a BTS or suffers from interference, the link quality
will degrade and retransmission will be activated. In this case the GPRS mobiles
remain connected to their serving cell until the call is dropped or the TBF
transmission is finished (which is more probable, due to the short duration of the
data transfer per block flow). In case of a call drop cell re-selection in packet idle
mode is performed and the data package is resent on the new cell. If the data
transmission is finished without call drop, reselection in packet idle mode is
performed and the next data package will be send on the new cell.
Furthermore the quality criteria of the radio link is for GPRS MS additionally
dependant on the retransmission rate. Therefore are the RXQUAL/RXLEV based
Power Control and Handover algorithms as implemented for CS traffic no longer
applicable.
I.e. for cell roaming the GPRS mobile performs autonomous cell re-selection in
packet idle mode. The MS measures the received signal strength on the (P)BCCH
frequencies of the serving cell and the neighbour cells, as indicated in the GPRS
(if MPDCH available) or the CS neighbourcell list and calculates the received level
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
24/56
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
25/56
Location
Area
RA1
RA4
RA
5
RA2
RA3
RA6
indicated in Table 3.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
26/56
Reliabilit
y Class
RLC Block
Mode
Traffic Type
Acknowledged
Non
real-time
traffic,
error-sensitive
application that cannot cope with data loss.
Acknowledged
Non
real-time
traffic,
error-sensitive
application that can cope with infrequent
data loss.
Acknowledged
Non
real-time
traffic,
error-sensitive
application that can cope with data loss,
GMM/SM, and SMS.
Unacknowledg
ed
Unacknowledg
ed
Real-time
traffic,
error
non-sensitive
application that can cope with data loss.
NOTE: For real-time traffic, the QoS profile also requires appropriate settings
for delay and throughput.
Table 3: Reliability Classes
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
27/56
En_GRPS in the ADJ File in order to enable/disable GPRS traffic within the cell.
TSNO: Sequence Number of the TRX_TS per TRX used for GPRS traffic (07)
Even though these are the only GPRS related BSS parameter, which should be set
by the RNP engineer, it is recommended to cross check if the other GPRS
parameters are set to reasonable defaults. Further important parameters, which
might help to understand the GPRS concept from the BSS parameter point of
view have been already mentioned in the previous chapters. For more detailed
information on these and many other parameters refer to [15].
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
28/56
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
29/56
CS1
CS2
16
12
max)
8
4
0
3dB
7dB
11dB
15dB
C/I
19dB
23dB
27dB
As shown in Figure 14 the cell ranges are defined by the achievable data
throughputs. With decreasing field strength level, four characteristic cell areas
within the GPRS service area for the step 1 implementation (only CS-1 and CS-2)
can be identified:
1. Area of CS-2 Saturation, i.e. data throughput = 12 kbit/s
2. Activation of retransmission due to insufficient coverage, i.e. reduced data
throughput until reference performance point is reached [10.5 kbit/s <
throughput < 12 kbit/s].
3. Performance at reference performance point cannot be longer maintained, the
BSS parameters should be set in a way that CS-1 is activated now => Area of
CS-1 saturation, i.e. data throughput = 8 kbit/s
4. Activation of retransmission due to insufficient coverage in CS-1 area, i.e.
reduced data throughput until reference performance point of CS-1 is reached
[7 kbit/s < throughput < kbit/s]. If the network is designed properly, the
neighbour cell should provide sufficient level and reselection should be
performed at the border of this area. Since no handover are implemented no
cell overlap (as for CS designs) needs to be considered in the network design.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
30/56
Leve
l
[dB
m]
Level of neighbourcell
CS - 2
Data
Throughput
[kbit/s]
12
CS - 1
1
10.5
8
2
3
7.5
4
1.
Throughput
at
CS-2
saturation point
2. Throughput at CS-2 reference
performance point
3.Throughput
at
CS-1
saturation point
4. Throughput at CS-1 reference
performance point
Figure 14: Dependency of data throughputs as a function of level (no interference)
Note, that the switch from CS2 to the more protected CS-1 mode gives higher
reliability, since the operating point is in the more horizontal saturation area.
But this is at the cost of reduced data throughput: Abrupt throughput reduction
from 10.5 kbit/s to 8 kbit/s.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
31/56
TU 3
TU 50
NO FH
[dB]
Ideal
FH
[dB]
NO FH
[dB]
Ideal FH
[dB]
CS-1
13
10
CS-2
15
13
14
13
19
10
12
10
Non-hopping case: For slow moving mobiles the C/I requirements are significantly
higher compared to a typical circuit switched design. Furthermore in order to
maintain secure DL transmission of the USF (Uplink State Flag) for scheduling of
UL TBFs, even 19dB are specified. This would require a drastic increase of the
frequency reuse in the network design. However, it would not be reasonable, to
design a non hopping network for a 19dB co-channel interference margin:
If the USF transmitted on the downlink can not be decoded, the UL TBF
scheduling is postponed. This means, if we design our network for a 13 dB C/I
margin only (CS-1 TU3 requirement) we would suffer from a degradation in the UL
data throughput. However, this can be handled by the network, since the GPRS
traffic is typically unsymmetrical and higher data rates are expected in the DL.
The introduction of frequency hopping reduces the C/I requirements significantly:
For CS-1 almost the same thresholds as for the circuit switched case are valid. In
the non hopping case for an optimised throughput a C/I of 13 dB is
recommended.
Frequency hopping is recommended for the GPRS carrier.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
32/56
The adjacent channel interference requirement is the same like for GSM
circuit switched:
C/Ia = C/Ic - 18dB for all conditions.
6.1.2.2Level/Sensitivity Requirements according to ETSI
For packet switched channels, the minimum input signal level for which the
reference performance shall be met is specified in table 1a in [9], according to
the type of channel and the propagation condition. The levels are given for a
normal BTS. For standard RNP tasks, this table can be simplified to:
ETSI Level thresholds for PDTCH (for Alcatel specific UL threshold see
below)
PDCH level requirements at which
reference performance point is met
TU 3
TU 50
No FH
No FH
CS-1
-104dBm
-104 dBm
CS-2
-104dBm
-100dBm
-104dBm
-103dBm
The thresholds are given for a normal BTS GSM 900. For other equipment, the
levels shall be corrected by the following values:
- for DCS 1800 class 1 or class 2 MS : +2/+4 dB (normal/extreme conditions)
- for DCS 1800 class 3 MS :+2 dB
- for GSM 900 small MS :+2 dB (small MS:Not vehicle mounted, pwr. class 4=2W or
5=0.8W)
- for other GSM 900 MS and normal BTS : 0 dB
For the DL the upper ETSI requirements have to be considered, for the UL
consideration in terms of sensitivity these values are dependent on the system
supplier. As for CS traffic, where the performance of the Alcatel G3 BTS is 7dB
better than required (-111dBm instead of
-104dBm) accordingly for GPRS
the G3 BTS performs also better. However according to simulations these 7dB are
not always reached.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
33/56
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
34/56
BS to MS
TX
Uplink
Downlink
Internal Power
33.0
dBm
45.4
dBm
0.0
dB
1.6
dB
Output Power
33.0
dBm
43.8
dBm
3.0
dB
11.0
dBi
51.8
dBm
4.0
dB
Antenna Gain
EIRP
29.0
RX
Uplink
Rec. Sensitivity
-109 *)
dBm
Downlink
dBm
Body/Indoor Loss
-102/ -98**)
dBm
4.0
dB
3.0
dB
2.0
dB
Antenna Gain
11.0
dBi
2.0
dBi
Diversity Gain
3.0
dB
Interferer Margin
3.0
dB
3.0
dB
-117
dBm
-95.8 / -91.8
dBm
146
dB
146.8 / 142.8
dB
*) For more details on this threshold see previous section. This value is based on
layer 1 simulations and is only preliminary as long as no measurements are
available.
**) Valid for a slow moving MS in CS-1 mode / the second value is fora fast
moving MS in CS-2 mode (TU 50) see Table 5.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
35/56
Under static fading conditions the same sensitivity values can be applied in the
link budget for CS-1 and CS-2. In case of fast moving MS, the sensitivities differ
by 4dB.
The interferer margin considers the fact, that in case of coexistence of
interference the system sensitivity is decreased. This has equally to be taken into
account in GPRS designs. A margin of typically 3dB is applied
A fading margin can additionally be considered, if the path loss for cell range
evaluations with a coverage probability above 50% shall be determined.
The cell ranges in coverage driven environments can then be estimated based on
the analysis of the max. pathloss. According to Table 6 the max. pathloss for CS-1
= 146.8dB and for CS-2 = 142.8dB (fast moving mobiles = TU 50 sensitivity =
98dBm). Applying the Hata Formula with the parameters according to Table 7
the cell ranges and cell areas given in Table 8 can be determined for an omni
configuration with a coverage probability of 90%.
Ant. Height BS
30.0
EIRP
Ant. Height MS
1.7
Max.
Pthloss
Frequency
900.0 MHz
51.8
146.8
Req. Cov.
dBm
dB
0.9
Clutter type
Cor
[dB]
[dB]
CS-2
[km]
Range CS-2
[km]
Area CS-1
[km]
urban, flat
2.27
16.19
2.95
11.12
urban, hilly
14
1.35
5.75
1.76
3.94
suburban, flat
3.60
40.64
4.67
27.92
suburban, hilly
12
2.33
17.11
3.03
11.72
forest, flat
10
4.67
68.56
6.07
47.09
forest, hilly
10
10
3.52
38.96
4.57
26.72
25
12.46
487.24
16.18
334.68
open
hilly
25
10
9.39
276.91
12.19
189.87
area,
Table 8 : Achievable cell ranges in a coverage driven environment (Hata formula) for
TU50
Accordingly 40% of the Cell area is covered by Coding Scheme 1 and 60% of the
cell area is covered by Coding Scheme 2. Assuming that the BSS parameter for
Coding Scheme Adaptation CS_LEV is set to 84dBm (=91.8dBm+8dB=83.8dBm). A lognormal margin of 8dB is added to the isotropic received power of
Table 6 to increase the coverage probability at the cell edge from 50% to 90%.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
36/56
21.6kbyte/hour
171 kbyte/hour
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
37/56
number and duration of the GPRS transfers per user for each traffic model.
With this information, it is possible to calculate the mean number of MS, per
multislot class, that are simultaneously engaged in a TBF in a GPRS cell.
These values can be calculated for each traffic profile:
Nb _ TS
The second step is to use this result as an input of a simulation tool which
enables to measure the impact of GPRS on CS traffic with various cell
configurations.
6.2.3.3Impact on CS traffic
Allocating TS to GPRS traffic reduces the capacity within the circuit switched
design. Depending on the amount of allocated timeslots for GPRS, the CS
capacities based on a blocking probability of 2% are given in Table 9. According
to chapter the amount of timeslots allocated to GPRS is depending on the circuit
switched and packet switched traffic. The maximum amount of PDCH is defined
by MAX_PDCH_HIGH_LOAD in case of high BSC load indication and
MAX_PDCH_GROUP otherwise.
Amoun
t of
TRX
Amoun
t
SDCCH
Amoun
t TCH
+PDC
H
Amount PDCH
1 TRX
2.93
2.27
1.65
2 TRX
14
8.20
7.4
3 TRX
22
14.89
4 TRX
29
5 TRX
37
1.09
0.6
0.2
0.02
6.6
5.8
5.08
4.34
3.62
2.93
14.03
13.18
12.33
11.49
10.65
9.82
9.01
21.03
20.15
19.26
18.38
17.50
16.63
15.76
14.89
28.2
27.3
26.4
24.6
23.7
22.8
21.9
21.03
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
38/56
6 TRX
44
34.6
33.7
32.8
31.9
30.99
30.08
29.16
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
39/56
28.25
CS-2 coverage
area
CS-1 coverage
area
real coding scheme map of course requires both inputs (level and interference).
For an thresholds example see the isotropic received power in Table 6. Additional a
lognormal margin needs to be considered for Pcov> 50%.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
40/56
constraints have to be fulfilled. So, if both constraints are taken into account,
service areas of the different coding schemes can be defined with a certain
probability. This probability corresponds to the probability, that the interference
ratio C/I is higher than the according threshold. Therefore, in a RNP tool, the
calculation of the interference probability has to be executed separately for the
GPRS carriers, taking into account the different thresholds per service class.
In order to achieve a maximum throughput, the service areas should not be
interference limited. That means, in the coverage areas described, the according
C/I constraint should be fulfilled, too. This should be taken into account for
frequency planning of the GPRS carriers. A solution could be to map the GPRS
carrier on the BCCH carrier and to apply a conservative frequency reuse. The
disadvantage is that on this carrier at most only 7 timeslots are available, since
TS0 of the BCCH carrier cannot be used.
6.3.3 Coding scheme and Throughput density map
A more exact coding scheme map and a throughput density map can be derived
from a pixel wise analysis of the C/I and level predictions. These maps can be
used for capacity evaluation (see next section) and further predict the throughput
performance within the service area.
6.3.4 GPRS Capacity
A simplified approach for the evaluation of the maximum amount of GPRS users
is described in chapter 6.2.3. A more accurate approach consists in using the
mentioned coding scheme and throughput density maps (chapter 6.3.3), which
leads to the total throughput by integrating over the whole cell area and
normalising. For each coding scheme, a constant throughput performance can be
assumed with a little degradation at the cell borders. The mean offered data
traffic capacity of one cell is equal to its total throughput and is given in
kbit/s/cell. Considering the user profiles of the GPRS data traffic model as well as
the amount of users and their distribution among these models. The amount of
users per cell can be determined.
The traffic database containing the offered packet switched data traffic in the
planning area has to be completely different from a GSM traffic database. It
should contain the traffic density in kbit/s/pixel. It could be derived from a traffic
budget, where the total occurring traffic in bytes per busy hour is elaborated for
the uplink as well as for the downlink [2]. The limiting link is then selected to feed
the traffic database.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
41/56
conservative planned BCCH carrier. The design values for the USF will still not be
met since they are extremely high with 19dB, however this results only in a
performance degradation in uplink direction. Frequency hopping improves the
system performance under interference conditions significantly, so that the
design values of the circuit switched designs can then be applied.
The expected development is, that in the beginning GPRS traffic is quite limited
and one TRX will be sufficient. One and later more TS will be dedicated to GPRS
traffic. But with increasing traffic for GPRS the CS capacity will be reduced and
carrier upgrading will be necessary. In a bandwidth limited environment this can
then lead to interference problems. According to marketing analysis the total
traffic will increase strongly due to additional data services. NW expansion
strategies like microcells promising the highest capacity gains will then play an
important role.
6.4.2 Evaluation
strategies
of
capacity
gains
based
on
network
expansion
Achievable capacity gains in percent have been determined for the available
network expansion strategies in the circuit switched case. However these values
cannot be applied one to one for the GPRS traffic:
Introducing a network expansion strategy (e.g. SFH, concentric cells, microcells
etc.) in a bandwidth limited environment first of all improves the network quality.
Thus carrier upgrading becomes possible in the circuit switched case, since now
frequencies can be reused more tightly.
If we think now on GPRS step 1 implementation, we can only switch one carrier to
GPRS per cell, thus carrier upgrading (several GPRS TRX per cell) is not possible
in the packet switched case. The upper limit is physically defined and the
relationship between frequency reuse and capacity as it is given for CS traffic is
not valid for packet switched designs. Therefore the achievable capacity gains
have to be analysed from a different point of view.
The evaluation of capacity is also different: Erlang for circuit switched and kbit/s
for packet switched systems.
Of course in GPRS there is a close relationship between radio link quality and
throughput, so introducing a network expansion strategy without carrier
upgrading already improves the maximum throughput rates. This capacity
improvement is further location dependant and the achievable gains depend very
much on the individual design. Therefore it will be very difficult to predict for the
1 TRX GPRS configuration the achievable capacity gains for the classical network
expansion strategies. Tool supported capacity analysis of the individual design
will be required for capacity improvement predictions.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
42/56
7 Summary
With Release B6.2 Alcatel introduces the step 1 implementation of GPRS. To have
GPRS running in an Alcatel EVOLIUM TM BSS only software upgrade is needed. The
software is remotely downloaded from the OMC-R. The PCU function is housed in
the Alcatel Multi-BSS Fast Packet Server A935-MFS, which can be co located with
the MSC and can be connected to up to 22 BSCs, thus allowing easy installation
and maintenance.
GPRS is a bearer service providing end-to-end packet-switched data services at a
rate of up to 96kbit/s per cell in step 1 (max. 12kbit/s per timeslot (CS-2 mode)
and max. 1 TRX for GPRS per cell). It allows efficient usage of the radio resources
and charging can be based on data volume transmitted. A radio connection is
established only when a data packet has to be transmitted.
A timeslot allocated for GPRS is called a Packet Data Channel (PDCH). For the
unidirectional packet data transfer, the data is transmitted on a Temporary Block
Flow (TBF) and is identified by a Temporary Flow Identity (TFI). Several TBFs
(=several users) can be multiplexed on one PDCH. One TBF can be transmitted
on several PDCHs depending on the mobiles multislot capability. The mapping of
logical channels, the user multiplexing and the TBF establishment scenarios for
UL and DL as well as the PDCH dynamic channel allocation is described in chapter
5.2.
On the radio interface, data can be coded according to currently two (later four)
different coding schemes (CS-1 to CS-4). These coding schemes offer different
redundancy levels and thus different data throughput rates. Currently
implemented in step 1 is CS-1 with a timeslot capacity of 8kbit/s and CS-2 with
12 kbit/s.
Radio link measurements are performed in uplink and in downlink direction. Level
and quality is computed block wise in uplink. In downlink the MS measures the
level of the serving cell and 6 strongest neighbours. However only level and
quality of a link is reported, which will be processed by averaging in the BSS
(C_VALUE and RXQUAL). Further the timing advance is determined similar to the
CS method and is updated every 0.96 sec.
Power control is only implemented on the uplink in an open loop configuration.
Cell roaming is performed in form of cell selection and re-selection according to
the circuit switched C1, C2 criterion or the GPRS specific C31, C32 criterion
depending on the PDCH configuration (MPDCH yes or no). I.e. handovers are not
implemented, if the mobile leaves a cell area in the packet transfer mode, the
data transfer will be continued until the call is dropped. After cell re-selection the
last TBF will be resent to the new cell.
Mobility management is performed by defining Routing Areas (RA) which are a
subset of one Location Area (LA).
From the Radio Network Planning point of view, the design values in terms of C/I
ratio and sensitivity are defined by the reference performance point. This point is
specified by ETSI and defines the thresholds below which retransmission due to
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
43/56
bad link quality significantly reduces the effective data throughput (BLER = 10%).
Thus it should be the target of a network design to fulfil the specified thresholds
at this point.
The co-channel C/I requirement in the non-hopping case is significantly higher
compared to the circuit switched case, especially for slow moving mobiles (13dB
for CS-1 and 15dB for CS-2). If a network design should be optimised for data
throughputs, then these should be the design values. However if a throughput
degradation can be handled in interfered areas it is recommended to use reuse
factors of the circuit switched design and to assign the GPRS service on the BCCH
carrier, which is usually planned with larger reuses. Note that this has the
disadvantage that max. 7 TS are usable for data or speech traffic.
Applying this frequency planning strategy will have the effect, that the USF flag
decoding will be interfered, since for the transmission of the USF at reference
performance point a C/I ratio of 19dB is required. This threshold cannot be a
design target value since it would require huge ARCSs. The USF is transmitted via
the BTS and schedules the UL TBFs. The effect of USF decoding problems will
result in reduced throughput in uplink direction.
However if frequency hopping is introduced, the same thresholds as for the CS
designs can be applied without any degradation in the CS-1 performance.
Therefore FH is recommended for the introduction of GPRS.
The downlink sensitivity for fast moving mobiles in CS-2 mode is 4dB lower than
in the other cases (slow moving CS2 and CS1 mode). The uplink sensitivity is
system supplier dependent. For the EVOLIUM BTS no measurements are available
yet. According to simulation results the sensitivity is a little lower then in the
circuit switched case (preliminary value 109dBm for CS-1 and 105dBm for CS2). However, if the network shall not be optimised in terms of data throughput
the same sensitivity thresholds can be applied as for the circuit switched design
(-111dBm), accepting a throughput degradation at the cell border.
Considering these sensitivity thresholds, the link budgets and cell ranges can be
determined accordingly. For the frequency planning in case of no hopping it is
recommended to use the BCCH carrier for GPRS service as long as max. 7
timeslots are sufficient from the traffic point of view. The BCCH carrier is due to
unavailability of PC, DTX or SFH usually planned with a large ARCS. Frequency
hopping is recommended to use with GPRS, since it significantly improves the
resistance. The same threshold as for the circuit switched case can be applied.
In order to determine the cell traffic capacity the easiest approach is to evaluate
the mean data throughput based on an assumed CS-1 and CS-2 contribution
proportional to each service area. In order to map this cell capacity on a capacity
per user a GPRS peak hour traffic model needs to be defined. Based on this the
mean bit rate per user during busy hour can be evaluated. Cell capacity divided
by mean bit rate per users gives the maximum amount of users per timeslot
according to the assumed traffic model.
For a detailed GPRS RNP design a tool supported approach is necessary by
evaluating the data throughput per pixel. This can be done by mapping the
predicted fieldstrength and C/I values to a bitrate. Such a datathroughput map
allows to identify areas of bad and good data throughput. Further cell areas for
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
44/56
CS-1 and CS-2 mode can be identified. By integrating and normalising over the
throughput density map, the offered cell traffic can be evaluated more precisely.
For a more accurate evaluation of the amount of users per cell an according
mapping of the traffic model to the bitrates per user during peak hour is still
missing.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
45/56
A data block consists (incl. 2 header bytes) of 22 bytes for CS-1, of 32 bytes for CS-2, of
38 bytes for CS-3 and of 52 bytes for CS-4.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
46/56
2. CS_QUAL_1_2
constitutes the RX_QUAL threshold used in radio link supervision, to
Range: 0 to 7
Default value: 2
3. CS_QUAL_2_1
constitutes the RX_QUAL threshold used in radio link supervision, to
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
47/56
Figure 16 shows the remaining block error rate (BLER) after decoding for the
different coding schemes for the TU50 environment. The ARQ protocol is not
taken into account.
0,1
0,01
CS1
CS2
CS3
CS4
0,001
0,0001
0,00001
3dB
7dB
11dB
15dB
19dB
23dB
27dB
C/I
Figure 16: Block Error Rate over C/I of the GPRS coding schemes (TU50, no FH)
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
48/56
0,1
CS1
CS2
0,01
CS3
CS4
0,001
0,0001
3dB
7dB
11dB
15dB
19dB
23dB
27dB
C/I
Figure 17: Block Error Rate over C/I of the GPRS coding schemes (TU3, no FH)
An Alcatel simulation for CS-1 and CS-2 shows that with frequency hopping, the
performance curves for TU50 and TU3 are almost identical (see Figure 18) and
significantly better than without FH.
Figure 18: Block Error Rate over C/I of the GPRS coding schemes CS-1 and CS2
Below, the C/I giving a BLER of 10-1 (reference performance) are presented for
information for TU3 and TU50 environment.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
49/56
Type of
channel
TU3 (FH)
TU50 (FH)
CS1
13.5 dB
8.5 dB
10.5 dB
8.5 dB
CS2
15.5 dB
12.5 dB
13.5 dB
12.5 dB
CS3
17.5 dB
not simulated
16 dB
not simulated
CS4
20 dB
not simulated
24 dB
not simulated
Table 10: C/I for a BLER = 10-1 (including the implementation margin of 2 dB)
Applying the protocol containing the ARQ function in the MAC/RLC layer, the
residual block error rate is negligible. However, the signal quality executes a
direct impact on the effective bitrate, since bad transmission conditions lead to a
large number of retransmissions which effects in a decreasing effective
throughput3. Figure 19 shows the maximal throughput per timeslot achievable at
a given C/I value in an TU50 environment, Figure 20 shows this throughput only
for the applied coding schemes CS-1 and CS-2 for different propagation
environments with and without frequency hopping. Since the maximal throughput
is measured, the traffic load doesn't need to be considered.
maximum throughput in TU 50 no FH
koctet/s
2,5
CS1
1,5
CS2
CS3
CS4
0,5
0
3dB
7dB
11dB
15dB
19dB
23dB
27dB
C/I
In this paper, "user data throughput" refers to the LLC data bits. Higher layer overhead
(e.g. for additional error protection, addressing etc...) is included and not taken into
account seperately. This means that that the data bit rate (e.g. for file transfer) seen
directly by the user may be significantly lower.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
50/56
Figure 20: Maximum throughput in kbyte/s over C/I for CS-1 and CS-2
It can be noted that for the applied coding schemes CS-1 and CS-2, the maximal
throughput reaches a saturation point. Above a certain C/I value, the coding
schemes CS-1 or CS-2 in combination with the ARQ protocol implementation lead
to a constant throughput. This "saturation throughput" is indicated in Table 11.
CS
throughput incl.
header (kbit/s)
data unit
throughput (kbit/s)
CS-1
9.05
CS-2
13.4
12
That means, that for one TRX per cell dedicated to GPRS, a maximal effective
data bit rate of 96 kbit/s can be realised.
For an average C/I which is slightly above or equal to the reference performance
point, the following average throughput values per timeslot are valid for CS-1 and
CS-2 (source: Alcatel CIT, Velizy):
CS
CS-1
CS-2
10.5
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
51/56
Sensitivity
Considering no interference, but only white noise as perturbation, the error
performance can be represented over the E b/N0 value. From this simulations, the
required signal input level at the reference performance point can be derived
(=reference sensitivity), for the mobiles as well as for the BTS.
In [5], the Eb/N0 performance is shown for different propagation environments. As
an example, the TU50 environment without frequency hopping is represented in
Figure 21.
BLER
1.00E-01
1.00E-02
CS-1
CS-2
CS-3
CS-4
1.00E-03
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26
Eb/No (dB)
Figure 21: BLER over Eb/N0 of the GPRS coding schemes (TU50, no FH)
Required level
CS-1
-103 dBm
CS-2
-100.5 dBm
CS-3
-98 dBm
CS-4
-90.7 dBm
Table 13: Signal strength needed for a BLER = 10-1 (TU50, no FH)
The ETSI signal level constraints for the different coding schemes and
propagation environments can be found in [9], chapter 6.2 and Table 1a, referring
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
52/56
to GSM900 as well as GSM1800. It has to be noted that CS-4 cannot meet the
reference performance for some propagation conditions.
Delay
The delay parameter defines the maximum values for the mean delay and 95percentile delay4 to be incurred by the transfer of data through the GPRS
network. The delay parameter defines the end-to-end transfer delay incurred in
the transmission of SDUs (service data units) through the GPRS network.
Different delay classes are defined for GPRS, however step 1 of the GPRS
implementation only realises delay class 4, the "Best Effort".
Reliability
Data reliability is defined in terms of the residual error rates for the following
cases (see [6])
probability of data loss
probability of data delivered out of sequence
probability of duplicate data delivery
probability of corrupted data
95-percentile delay=95% of the data are received with this or a lower delay
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
53/56
Throughput
The user throughput is defined by
maximum bit rate (peak throughput)
mean bit rate (mean throughput)
given in kbit/s. In [7], there are defined different throughput classes, which are
part of the higher layer QoS declaration. In the BSC, there is no use of Peak and
Mean throughput parameters. The bandwidth (i.e. the share of the available
physical channels) given to a mobile station depends only on its multislot class 5,
and on the number of other mobiles asking for channel resources. In fact, a
mobile shares its allocated time slot(s) equitably with other mobiles using the
same time slot(s).
The multislot class characterizes the multislot capability of a mobile. It is not part of
QoS. Multislot classes are defined in [8], Annex B.
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
54/56
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
55/56
Index
A935......................................................................16
BLER.............................6, 27, 42, 44, 45, 46, 47, 48
Block Error Rate...................................6, 27, 44, 45
CAE.......................................................................26
Capacity.................................................................38
Cell Ranges...........................................................33
Cell Redirection....................................................51
Cell re-selection....................................................23
Channel coding......................................................22
Coding scheme................................................38, 48
Coding Schemes................................................5, 22
Coverage...............................................................37
Delay...............................................................25, 49
Design Thresholds...........................................27, 30
Detailed RNP design.............................................37
DRX..................................................................6, 25
dynamic channel allocation.............................11, 16
Frequency Planning...............................................34
GGSN........................................................6, 7, 9, 20
handover....................................................23, 24, 28
Initial GPRS Design..............................................33
Interference.....................................................37, 44
Link Budget...........................................................33
Logical Channels...................................................11
Measurements.......................................................22
MFS.........................7, 10, 16, 17, 18, 19, 22, 23, 25
multislot capability................................................11
END OF DOCUMENT
01
RCD
277195762.doc
1 Sept. 99
OC/NPL
CONFIDENTIAL
56/56