Documentos de Académico
Documentos de Profesional
Documentos de Cultura
Blank Page
112
Objectives
113
Location Management,
Objectives
114
Table of Contents
115
Page
1 Basics
1.1 Service Overview GPRS
1.2 Service Overview EGPRS
1.3 Support of GPRS QoS classes
1.3.1 Radio Network Planning Impact
1.4 Dual Transfer Mode
1.4.1 Radio Network Planning Impact
1.5 (E)GPRS MS Multislot Classes
1.6 (E)GPRS General Architecture
1.7 Alcatel (E)GPRS Architecture
1.8 (E)GPRS Protocol Layers (Transmission Plane)
1.9 Alcatel (E)GPRS BSS Hardware support
1.10 Modulation Technique: 8-PSK only for EGPRS
1.11 8-PSK TRA Power Aspects
1.12 (E)GPRS Radio Blocks Structure
1.13 GPRS Channel Coding
1.14 EGPRS Channel Coding
1.15 Radio Link Adaptation Overview
1.16 Automatic ReQuest for repetition (ARQ)
1.17 Type-I ARQ mechanism
1.18 Type-I ARQ in GPRS
1.19 Type-I ARQ in EGPRS
1.20 (E)GPRS radio physical channel: PDCH Concept
1.21 (E)GPRS Multiframe
1.22
Logical Channels
EVOLIUM
BSS -(E)GPRS
GPRS and EGPRS
Radio Network
Planning
1.23 Master/Slave
PDCH concept All Rights Reserved Alcatel-Lucent 2007
1.24 Temporary Block Flow
1.25 Resources Sharing
1.26 MS multiplexing co-ordination
1.27 GPRS mobility management (GMM) states for MS
1.28 Radio Resource (RR) operating modes for MS
1.29 Attach procedure
1.30 PDP context activation
1.31 Location management
1.32 Routing Area
1.33 Network Mode of Operation (NMO)
1.34 TBF establishment
1.35 UL TBF establishment on CCCH, 1 phase access
1.36 UL TBF establishment on CCCH, 2 phases access
1.37 DL TBF establishment on CCCH
1.38 System information broadcasting on BCCH
1.39 System information broadcasting on PBCCH
1.40 (E)GPRS Transmission Aspects
1.40 TRX Classes Concept
1.41 Two Abis Links per BTS
2 B9 features
2.1 Enhanced Packet Cell Reselection (R4 MSs)
2.1.1 Radio Network Impact
2.2 Extended Uplink TBF Mode
2.2 Radio Network Planning Impact
2.3 Enhanced support of E-GPRS (EDGE) in uplink
2.3.1 Radio Network Planning Impact
2.4 Counter Improvements for Release B9
2.4.1 Radio Network Planning Impact
2.5 Autonomous Packet Resource Allocation
9
10
11
12
13
14
15
16
17
19
22
23
24
25
29
31
34
39
40
41
42
43
47
48
49
51
52
54
58
61
62
63
65
66
67
68
69
70
72
74
75
77
80
81
84
85
86
87
88
89
91
93
94
98
99
Page
101
102
105
106
108
109
110
111
112
113
114
115
116
117
121
123
130
132
143
145
146
150
153
157
160
161
163
164
166
167
168
171
176
179
180
181
182
183
184
185
186
188
189
191
192
193
195
196
198
199
200
201
203
204
205
Page
206
207
212
217
218
219
222
224
225
228
229
230
231
235
245
248
249
250
251
254
255
256
257
259
260
262
263
264
266
267
268
269
275
276
278
280
283
284
285
288
289
291
292
293
297
301
Blank Page
118
119
1 Basics
1 Basics
connection time
1 Basics
modulation technique:
1 Basics
PFC procedure
Packet Flow Context (PFC) is a concept introduced starting with R99 3GPP release to ensure that the
BSS is involved in the R99 QoS negotiation. The interest of PFC is to differentiate on the radio
interface the conversational and streaming traffics and to reserve resources for these traffics.
Without the PFC, the BSS only knows the R97/98 QoS parameters (correspond to the interactive and
background R99 QoS classes). It enables to perform admission control and QoS based resource
allocation in the BSS.
R99 QoS is taken into account if the PFC (Packet Flow Context) procedures are supported by the MS,
the BSS and the SGSN. It allows the BSS B9 to handle streaming and interactive traffics and also to
negotiate the QoS parameters.
R97/98 QoS should be also taken into account (OP12) if PFC is not supported by the MS or the SGSN in
order to handle interactive traffics or some specific applications as PoC (Push over Cellular).
1 Basics
- PFC_FEATURE_MODE: this 1 bit field is a part of the R99 extensions in the GPRS_Cell_Options. It is
broadcasted on BCCH (SI13) or PBCCH (PSI1, PSI13 and PSI14) and indicates to the MSs if the network supports
the PFC feature.
- The PFC impact on the one phase access: "If the PFC_FEATURE_MODE is set in the system information and if a
PFC exists for the LLC data to be transferred then the PFI shall be transmitted along with the TLLI of the
mobile station in the RLC extended header during contention resolution. The PFI is not used for contention
resolution but is included to indicate to the network which PFC shall initially be associated with the uplink
TBF.
- PI bit (PFI indicator) is created, it indicates the presence of the optional PFI field:
0 PFI is not present
(EGPRS) Packet DL ACK/NACK: PFI field is added (if a Channel Request Description is also present)
UL (EGPRS) RLC data blocks : PFI field is added after the TLLI field (see 44.060 10.2.2 and 10.3a.2).
Activate_PDP_Context_Accept,
Activate_Secundary_PDP_Context_Accept,
PFC_FEATURE_MODE is included in the MS_Network_Capability I.E. (which is sent in the Attach_Request and
1 Basics
1 1 14
1 Basics
1 1 15
presented below:
Half rate
Support of half rate configurations (one single timeslot encompassing one half
rate circuit channel + one half rate packet channel) was not considered in the
first implementation of DTM.
Inter-cell handovers
Intra-cell handovers
Hierarchical networks
As (E)GPRS are preferentially offered in macro cells, the BSS shall ensure that
at least one PDCH can be used in micro cells to re-direct the MS towards the
macro cells. It means that the BSS shall allow a PDCH used by a MS operating in
DTM mode to be shared by other (E)GPRS MS.
1 Basic
E.g. the multislot class of the mobile can be 3 RXs + 2 TXs (class 6) in pure GPRS
mode and 2 RXs + 1 TX (class 2) in pure EGPRS mode
Multislot
Class
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 27 28 29
RX Timeslots 1 2 2 3 2 3 3 4 3
TX Timeslots 1 1 2 1 2 2 3 1 2
5 n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.n.a.
Sum of
Timeslots
2 3 4 4 4 4 4 5 5
MS type
Type 1 are simplex MSs, i.e., without duplexer: they are not able to transmit and receive at the same time
Type 2 are duplex MSs, i.e., with duplexer: they are able to transmit and receive at the same time
Rx
Tx
SUM
The maximum number of received time slots that the MS can use per TDMA frame. The receive TS shall be
allocated within window of size Rx, but they do not need to be contiguous. For SIMPLEX MS, no transmitted
TSs shall occur between receive TS within a TDMA frame. This does not take into account the measurement
window (Mx).
The maximum number of transmitted time slots that the MS can use per TDMA frame. The transmitted TS
shall be allocated within the window of size Tx, but they do not need to be contiguous. For SIMPLEX MS, no
received TS shall occur between transmit TS within a TDMA frame.
The maximum number of transmitted and received time slots (without Mx) per TDMA frame.
- Ttb is the minimum time (in time slot) necessary between the Rx and Tx windows.
- Tra is the minimum time between the last Tx window and the first Rx window of the next TDMA in
order to be able to open a measurement window.
- Ttb is the minimum time necessary between 2 Tx windows belonging to different frames.
- Tra is the minimum time necessary between 2 Rx windows belonging to different frames in order to be
able to open a measurement window.
- Trb is the same as Tra without opening a measurement window.
All Rights Reserved 2007, Alcatel-Lucent
3FL 38020 ACAA Edition 2
Section 1 Module 1 Page 16
1 Basics
1 Basics
PSTN
MSC/VLR
BSS
Gb
Interface
GPRS
backbone
PDN
Gi
Note: Additional IP routers might be used to route the information between the GSNs (intra-PLMN
backbone network). All the elements connected to this backbone have private permanent IP
addresses.
Signaling protocols:
Gc: for Network-Requested PDP contexts Activation (the GGSN asks the HLR for SGSN Routing
Information).
Gs: defines the Network Mode of Operation I. It allows to perform LA + RA combined Location Update,
Gd to deliver the SMS to the mobiles via the GPRS network (SGSN option and subscriber feature).
1 Basics
Alcatel choice:
Packet Server)
smooth and cost effective introduction of the GPRS
The standard specifies that the PCU function shall be implemented in one of the 3 following entities:
BTS,
BSC,
The implementation of the PCU functions determines the position of the Gb interface. ALCATEL chose
the MFS integration in order to offer a faster implementation inside the BSS as well as an easier
maintenance and supervision.
1 Basics
Packet domain
BTS
BSC
Abis
MFS
Ater
SGSN
Gb
GGSN
Fire-
Other
PLMN
wall
Gn
MS
Gp
Gi
Internet/
Intranet
1 Basics
Serving GPRS Support Node (SGSN), at the same hierarchical level as the
MSC, which is linked to several BSSs. It keeps track of the individual MSs
location and performs security functions and access control
Gateway GPRS Support Node (GGSN), which is linked to one or several
data networks, provides interworking with external packet-switched
networks and is connected with SGSNs via an IP-based GPRS backbone
network
1 Basics
Application example
http
Hypertext Transfer
Protocol
TCP
Transmission Control
Protocol
RFC 793
IP
IP
Internet Protocol
RFC 791
SNDCP
SNDCP
LLC
RLC
RLC
relay
MAC
BSSGP
Medium Access
Control
GSM 04.60
relay
Physical L2-GCH
Layer 2 GPRS
Link Layer
Channel
Physical
Link Layer
Physical
RF Layer
Physical
RF Layer
GSM 08.18
GSM 08.18
NS
NS
Um
Layer 2 GPRS
Channel
L1-GCH
Layer 1 GPRS
Channel
BTS
Network Service
GSM 08.16
L2-GCH
L1-GCH
Layer 1 GPRS
Channel
Abis / Ater
BSSGP
MAC
Medium Access
Control
GSM 04.60
MFS
Network Service
GSM 08.16
L1bis
L1bis
Layer 1bis
GSM 08.14
Layer 1bis
GSM 08.14
Gb
GTP
GTP
GPRS Tunneling
Protocol
GSM 09.60
GPRS Tunneling
Protocol
GSM 09.60
LLC
MS
relay
Subnetwork
Dependent
Convergence
Protocol
GSM 04.65
Subnetwork
Dependent
Convergence
Protocol
GSM 04.65
Internet Protocol
RFC 791
UDP
UDP
User Datagram
Protocol
RFC 768
or:
User Datagram
Protocol
RFC 768
or:
TCP
TCP
Transmission Control
Protocol
RFC 793
Transmission Control
Protocol
RFC 793
Internet Protocol
RFC 791
Internet Protocol
RFC 791
IP
IP
Ethernet
FR
Ethernet
FR
Frame Relay
or:
Frame Relay
or:
ATM
and/or:
and/or:
E1 (PCM30)
E1 (PCM30)
G.703 / G.704
SGSN
ATM
Asynchronous
Transfer Mode
Asynchronous
Transfer Mode
G.703 / G.704
Gn
GGSN
Gi
For the exact purposes of the tracing, please refer to Introduction to GPRS & E-GPRS Quality of
Service Monitoring It can be said from this protocol stacks diagram that after allocation of a GCH by
the BSC to the MFS, the data carried over the GCH are transparent for the BSC.
The RLC function defines the procedures for segmentation and reassemble of LLC PDUs into RLC/MAC
blocks and, in RLC acknowledged mode of operation, for the Backward Error Correction (BEC)
procedures enabling the selective retransmission of unsuccessfully delivered RLC/MAC blocks. In RLC
acknowledged mode of operation, the RLC function preserves the order of higher layer PDUs provided
to it. The RLC function provides also link adaptation. In EGPRS in RLC acknowledged mode of
operation, the RLC function may provide Incremental Redundancy (IR).
The MAC function defines the procedures that enable multiple mobile stations to share a common
transmission medium, which may consist of several physical channels. The function may allow a
mobile station to use several physical channels in parallel, i.e., use several time slots within the TDMA
frame. For the mobile station originating access, the MAC function provides the procedures, including
the contention resolution procedures, for the arbitration between multiple mobile stations
simultaneously attempting to access the shared transmission medium. For the mobile station
terminating access, the MAC function provides the procedures for queuing and scheduling of access
attempts.
1 Basics
G1 MK2 and G2 with DRFU: GPRS only, CS-1 and CS-2 only
A9100 EVOLIUM (G3): GPRS only, CS 1-4
A9100 EVOLIUM Evolution (G4): (E)GPRS, CS 1-4, MCS 1-9
TC A9125 (Transcoder)
G2 and G2.5
1 Basics
An 8PSK signal carries three bits per modulated symbol over the radio
011
010
001
dB
001
000
100
111
101
110
000
100
011
011
001
101
111
111
010
010
000
Q
110
PN
101
110
-20
100
(147 bits)
GMSK = the Gaussian Minimum Shift Keying belongs to a subset of phase modulations
8-PSK = 8-state Phase Shift Keying
8-PSK is not a constant envelope modulation. Part of the information is conveyed by the
amplitude of the carrier which varies over time.
An 8-PSK signal carries three bits per modulated symbol over the radio path, which allows to
triple the data transmission rates.
Modulation gross bit rate
The normal burst is divided into 156.35 symbol periods. A normal burst has a duration of 3/5.2
seconds (577 s). (3GPP TS 05.02).
For GMSK modulation, a symbol is equivalent to a bit (3GPP TS 05.04)
A GMSK burst is composed of 156.35 bits (6 tail bits + 26 training sequence bits + 116 encrypted
bits + 8.25 guard period (bits))
Modulation gross bit rate = (156.35 bits) / (3/5.2 seconds) = 270 Kbit/s
For 8-PSK modulation, one symbol corresponds to three bits (3GPP TS 05.04).
An 8-PSK burst is composed of 156.35 x 3 = 468.75 bits (18 tail bits + 78 training sequence bits +
348 encrypted bits + 24.75 guard period (bits)).
Modulation gross bit rate = (468.75 bits) / (3/5.2 seconds) = 810 Kbit/s
GMSK
8-PSK
Modulation type
Frequency modulation
Phase modulation
Channel spacing
Gross bit rate per
carrier
Carrier envelope
200 KHz
200 KHz
270 Kbit/s
constant
810 Kbit/s
Amplitude varies
GPRS / EGPRS
EGPRS
1 Basics
8-PSK peak power is equal to GMSK peak power but the 8-PSK average
900 MP
45 W / 46.5 dBm
15 W / 41.8 dBm
900 HP
60 W / 47.8 dBm
25 W / 44 dBm
1800 MP
35 W / 45.4 dBm
12 W / 40.8 dBm
1800 HP
60 W / 47.8 dBm
25 W / 44 dBm
900 EDGE+
45 W / 46.5 dBm
30 W / 44.8 dBm
1800 EDGE+
35 W / 45.4 dBm
G3 TREs are not able to handle the 8-PSK modulation. Only G4 TREs (also called TRA) are EDGE capable.
1 Basics
-8PSK
= APD
APD = 0
Case 1: BS_TXPWR_MAX=0
Case 2: BS_TXPWR_MAX<>0
SECTOR
GMSK
8-PSK TRE 1
8-PSK TRE 2
HP TRE 1
LEGEND
MP TRE 1
Case 1
GMSK LEVELING
ATTENUATION
BS_TXPWR_MAX
8-PSK POWER
APD
GMSK POWER
HP TRE 1
MP TRE 2
Case 2
8-PSK
The back-off between average GMSK and 8-PSK output power comes from physics since 8-PSK is a non
constant envelope modulation unlike GMSK.
As a consequence power amplifiers can not be used at their maximum power. This results in a
difference between mean output powers for GMSK and 8-PSK modulations.
The BTS sets all the TRE which transmit GMSK output powers at the same level which is the minimum
value among the maximum TRE output power in a sector and in a given band.
On a TRE, the maximum GMSK output power is higher than the maximum 8-PSK output power.
An O&M parameter (BS_TXPWR_MAX) allows a static power reduction of the maximum GMSK output
power of the sector.
The TRE transmit power in 8-PSK shall not exceed the GMSK transmit power in the sector.
The BTS determines for each TRE, the difference between the 8-PSK output power of the TRE and the
GMSK output power of the sector (8-PSK delta power).
According to the 8-PSK delta power value, a TRE is called High Power or Medium Power.
When a GCH channel is activated, the BTS sends the 8-PSK delta power to the MFS.
Together with BS_TXPWR_MAX (static power reduction), the 8-PSK delta power allows the MFS to
determine:
- a possible attenuation (BS_TX_PWR) for the 8-PSK DL RLC block emission, in order not to exceed
the GMSK power of the sector (for GMSK DL RLC block, the attenuation is BS_TXPWR_MAX).
- an Average Power Decrease which is the difference between the 8-PSK output power and the GMSK
output power after having taken into account BS_TXPWR_MAX. The Average Power Decrease is
taken into account in the link adaptation tables.
1 Basics
Example:
RESULTS:
1st step: Output power at BTS antenna connector (after combiner and
duplexer stage):
1 Basics
TRE 1..4 GMSK = 42.1 2 = 40.1 dBm (Effective GMSK Sector Power)
YES, since 40.1 dBm 39.6 dBm 37.4 dBm no reduction of 8-PSK power
5th
Therefore, the system is allocating a higher priority for the packet-switched traffic for non-hopping
TRX in a cell.
In addition, the non-hopping TRX may benefit from a special radio planning with higher reuse cluster
size, in order to ensure higher C/I conditions and offer better throughputs, both for GPRS and EDGE.
APD should be considered in the A9155 planning tool for the throughput estimation (based on
interference calculation per pixel approach) and also to determine the 8-PSK coverage.
The IR gain should also be considered in the throughput estimation. 3 dB can be taken for the average
IR gain.
PS_PREF_BCCH_TRX is a flag at cell level which indicates whether the operator wishes to allocate
packet on the BCCH TRX with highest priority. Actually, is recommended to activate GPRS/EDGE
traffic on the BCCH TRX due to its high RCS. However the activation of EDGE on the BCCH TRX should
be performed cautiously.
3GPP Rec. 05.08 has defined a constraint on the transmitted power of BCCH frequency. This
frequency shall usually be transmitted at a constant level. A tolerance has been introduced with 8PSK: a fluctuation of up to 2 dB is allowed. Depending on the configuration in the BTS, it may happen
that the difference between GMSK and 8-PSK power on the BCCH TRX is greater than 2dB. A possible
solution for this constraint, in case of a BTS (e.g. ANc combined) equipped only with MP TRX (most of
the cases) is presented below: The BCCH MP TRX will be replaced by a HP TRX (to take also
advantage from 8-PSK 25W power and <3dB) BS_TXPWR_MAX will be set to 2 dB The difference
between GMSK and 8-PSK power on BCCH TRX will be: (42.1 2) 39.6 = 0.5 dB which respects the
ETSI constraint. The drawback is that CS and GPRS service may be affected by the GMSK output
power reduction.
1 Basics
one radio block is always entirely assigned to one user; inside a block
1 Basics
RLC header
BCS
MAC header: control fields which are different for uplink and downlink directions
RLC header: control fields which are different for uplink and downlink directions
RLC Data Block: bytes from one or more LLC PDUs
Block Check Sequence (BCS): used for error detection
BCS
RLC/MAC header: control fields which are different for uplink and downlink directions
RLC Data Field: LLC PDUs bytes; contains one or two RLC data blocks
Block Check Sequence (BCS): for error detection of the data part
Header Check Sequence (HCS): for error detection of the header part
1 Basics
The useful data rates on the air interface depend on the channel coding
procedure
For (E)GPRS, different channel coding levels are applied depending on
the actual radio conditions
1 Basics
Four different coding schemes, CS-1 to CS-4, are defined for the
GPRS Radio Blocks carrying RLC data, and are applied depending
from the actual radio conditions
The first step of the channel coding procedure is to add a Block
Check Sequence (BCS) for error detection
For CS-1 to CS-3, the second step consists of pre-coding USF
(except for CS-1), adding four tail bits and a half rate
convolutional coding for error correction that is punctured to give
the desired coding rate
For CS-4 there is no coding for error correction
The most protected mode is CS-1 which is therefore always used for
GPRS signaling (even for EGPRS)
1 Basics
BCS
CS-1
GMSK
modulation
20
Maximum User Payload [kbps]
456 bits
Header + Protection
CS-3
14.4
puncturing
Release B8
CS-2
12
Scheme
Modulation
schemes
Coding schemes
for RLC data block
Code
rate
CS-4
CS-3
GMSK
No coding
1.00
20.0
GMSK
0.75
14.4
CS-2
GMSK
0.66
12.0
CS-1
GMSK
0.50
8.0
CS-4
1 Basics
The puncturing process consists of transmitting only some of the coded bits obtained after the rate 1/3
convolutional coding. Depending on the considered puncturing scheme, different coded bits are transmitted.
Therefore, when the receiver receives two versions of the same RLC block sent with two different puncturing
schemes, it obtains additional information leading to an increased decoding probability.
1 Basics
bytes:
bytes:
bytes:
bytes:
family
family
family
family
A
A (padding)
B
C
1 Basics
GMSK
8.8
MCS-1
11.2
MCS-2
14.8
Family A
MCS-6
MCS-4
MCS-5
14.8 x 2 = 29.6
37 octets
MCS-9
Family A
34 +3 octets 34 +3 octets
padding
MCS-6
34 octets
34 octets
11.2 x 4 = 44.8
MCS-7
MCS-8
14.8 x 4 = 59.2
34 octets
MCS-2
Family B
MCS-9
34 octets
MCS-8
MCS-6
Family C
Header + Protection
37 octets
MCS-3
11.2 x 2 = 22.4
37 octets
37 octets
MCS-3
8.8 x 2 = 17.6
8-PSK
MCS-3
28 octets
28 octets
MCS-5
28 octets
28 octets
MCS-7
MCS-1
22 octets
22 octets
MCS-4
the design of the GPRS coding schemes which were designed independently from the others with
their own data unit.
the fact that once the information contained in an radio block has been transmitted with a
certain CS, it is not possible via the Automatic ReQuest for repetition (ARQ) mechanism to
retransmit with another CS.
- This could lead to the release of the TBF and to the establishment of a new one in order to
transmit the LLC frame.
EGPRS coding schemes have been designed to offset this problem. Four MCS families have been
This allows the re-segmentation of the RLC data blocks when changing of modulation and coding
schemes (within the same family).
- Example: if one MCS-6 radio block has not been received correctly by the receiver and if
radio conditions have degraded in the meantime, it is possible to re-send the same
information in two radio blocks with MCS-3 (more protection).
The level of protection applied (MCS usage) in case of retransmissions is in line with the radio
conditions.
The different code rates within a family are achieved by transmitting a different number of payload
units within one radio block. When 4 payload units are transmitted, these are split into 2 separate RLC
blocks (i.e., with separate sequence numbers).
1 Basics
MCS-9 Example:
3 bits
45 bits
RLC/MAC
header
USF
36 bits
612 bits
HCS E
FBI
135 bits
36 bits
124 bits
BCS
TB
P1
612 bits
P2
puncturing
612 bits
P3
612 bits
P1
1392 bits
TB
1836 bits
puncturing
612 bits
BCS
1836 bits
puncturing
SB=8
612 bits
612 bits
P2
612 bits
P3
1 Basics
Uplink
transfer
Scheme
Modulation
schemes
Coding schemes
for RLC data block
Code
rate
MCS-9
8PSK
1.00
59.2
MCS-8
8PSK
0.92
54.4
MCS-7
8PSK
0.76
44.8
MCS-6
8PSK
0.49
29.6
MCS-5
8PSK
0.37
22.4
MCS-4
GMSK
1.00
17.6
MCS-3
GMSK
0.80
14.8
MCS-2
GMSK
0.66
11.2
MCS-1
GMSK
0.53
8.8
1 Basics
1 Basics
errors in a received RLC block, it requests and receives a retransmission of the same RLC block from the transmitter
The retransmission can be performed using:
Type-I ARQ mechanism. This applies for both GPRS and EGPRS mode
IR is optional for the BTS, but is mandatory for the EGPRS MS (3GPP
requirement)
B9
!!! ARQ type-II applies for UL and DL EGPRS mode !!!
1 Basics
MFS
Uplink RLC data block B1 / PDTCH (1)
Uplink RLC data block B2 / PDTCH (2)
With the type 1 ARQ mechanism, the decoding of a re-transmitted RLC block does not use the
previously transmitted versions (not correctly received) of this RLC block. The decoding of a RLC data
block is only based on the current transmission.
1 Basics
GPRS CSs are designed independently from the others with its own basic
GPRS DRAWBACK
payload unit size, so the family concept does not exists in GPRS
Before its transmission over the radio interface, the LLC frame is segmented
into payload units according to CS that will be used to transmit the radio
block
In case of erroneous reception, the RLC data block can be retransmitted
only with the same CS (segmentation is not possible)
If the radio conditions have changed and the coding rate is not appropriate to
them, the receiver will never be able to decode the retransmission of the RLC
data block. This will lead to the release of the TBF and the establishment of a
new one in order to transmit the LLC frame
In order to avoid this problem, the choice of the CS on the network side has to
be made carefully. This often results in an non-optimized use of the radio
interface, leading to a reduction of network capacity compared with its
theoretical capacity
1 Basics
block, the same or a next lower MCS within the same family is used
The retransmission can be performed with or w/o RLC data segmentation (e.g.
E.g. if the LA mechanism orders the usage of MCS-5 and the first transmission of
an erroneous RLC block was with MCS-6, the transmission will be performed with
MCS-3. The blocks that are sent for the first time will be transmitted with the
last-ordered MCS
1 Basics
In the IR mechanism:
The information which is sent first results from an initial puncturing scheme
The type 2 ARQ mechanism or incremental redundancy (IR) is an ETSI function, mandatory for the EGPRS MS
receiver (downlink path) and optional for the BTS receiver (uplink path). In B8 release, the IR feature is only
available on the downlink path. It is important to notice that the IR feature is always running in the EDGE MS
receiver (except in case of MS memory shortage). The DL incremental redundancy is not used for the signaling
blocks, the GPRS data blocks and the data blocks in RLC unacknowledged mode. It is only used for the EGPRS data
blocks in RLC acknowledged mode.
the first emission of a RLC data block is done using a first puncturing scheme (PS1),
in case of re-transmission of this RLC block, the transmitter uses the same MCS or a MCS of the same family
than the one used for the initial block. On the DL path, depending on the value of the parameter
EN_FULL_IR_DL, re-segmentation of the RLC block may be performed or not,
at the output of the demodulator, the receiver combines the information of soft bits corresponding to the
first transmission of the block and its different re-transmissions, thus increasing the decoding probability of
the RLC block.
Remark : according to the 04.60 (RLC/MAC layers) GSM recommendation, the soft-combining inside the MS
receiver is only performed between an :
- MCSx block and MCSx block (that is the same MCS is used for the re-transmission),
- MCS9 block and an MCS6 block (in that case the RLC data blocks carry the same number of payload
units),
- MCS7 block and an MCS5 block (in that case the RLC data blocks carry the same number of payload
units).
If the "MS OUT OF MEMORY" field is set by the mobile in the EGPRS Packet DL Ack/Nack message, the type I ARQ
shall apply in the MS receiver (ARQ without IR). This occurs when the memory for IR operation runs out in the MS
(that is when the memory of the MS is full due to the storage of the different versions of a RLC block not
correctly decoded).
1 Basics
MS
BTS
MFS
Data Block
Data Block
puncturing
scheme 1
Nack
Data Block
Data Block
puncturing
scheme 2
Data Block
Data Block
if the selected MCS has not changed : if all the different punctured versions of the data block have
been sent, the procedure shall start over and PS1 shall be used, followed by PS2, then by PS3 (if
available for the considered MCS), so that the PS selection is cyclic,
if the selected MCS has changed : the PS to be used is indicated by the table below.
Previous MCS
MCS9
New MCS
MCS6
Previous PS
New PS
PS2
PS2
PS1 or PS3
PS1
MCS6
MCS9
PS1
PS3
MCS7
MCS5
PS1
MCS5
MCS7
PS2
PS1 or PS2
Any
PS2
PS2
PS1
1 Basics
downlink
This mechanism is associated with link adaptation in order to
provide superior radio efficiency on the air interface
IR feature is always running in the EGPRS MS receivers, except when
a memory shortage is reported by the MS the stored packets are
discarded and type-I ARQ is set !
Parameter for IR activation:
EN_FULL_IR_DL which enable or disable the RLC data segmentation for
retransmissions
1 Basics
PDCH group
possible to have hopping and non hopping PDCH groups in one cell
16 TRX/cell achieved with help of the B7 feature cell split over 2 BTSs, EVOLIUM BTS
1 Basics
The frames 25 and 51 are idle frames and the frames 12 and 38 are
One PDCH
Block B0
Block B1
10
Block B2
11
12
13
PTCCH
14
Block B3
15
16
47
48
49
Block B11
50
51
idle
1 Basics
1 Basics
PTCH (Packet Traffic Channel) used for user data transmission and
PDTCH (Packet Data Traffic Channel) used to carry user data (LLC PDU
1 Basics
All other PDCHs, active as slaves, are called Slave PDCH (SPDCH)
B8 release:
1 Basics
Important:
Since B7, it is possible to establish 32 TBFs per PDCH group (See sub-session 2.2 for PDCH group
definition).
TBF
is a group of blocks dynamically allocated to one MS for one transfer of RLC blocks in one direction
inside one cell.
A Temporary Block Flow is a temporary, unidirectional physical connection across the Um interface,
between one mobile and the BSS. The TBF is established when data units are to be transmitted across
the Um interface and is released as soon as the transmission is completed.
1 Basics
More than 32 TFI values per TRX (PDCH group) for each direction (i.e. DL
and UL)
The TLLI identifies the logical link between the MS and the SGSN
The TLLI is allocated by the SGSN to the MS in Standby and Ready states
1 Basics
PDCH Multiplexing
PDCH multiplexing refers to the sharing of one PDCH by more than two users
(TBFs)
It occurs when there are more requests for PDCH resources than available PDCHs
A maximum number of UL/DL_TBF can share the same PDCH in UL and DL
direction respectively
MAX_UL_TBF_SPDCH=6; MAX_DL_TBF_SPDCH=10
When a PDCH is shared between an UL GPRS TBF and a DL EGPRS TBF, then the DL
EGPRS shall be limited to GMSK (i.e. MCS-4) GPRS MS becomes candidate for
radio resource reallocation
1 Basics
Multislot usage
Refers to the case when 1 user can request at once more than 2 PDCH
B8 & B9 release supports 4+2 slots for Type 1 MS and 5+5 for Type 2 MS
1 Basics
lets assume that the data for user 1 has a length of 3 blocks (length of
User 1 has (1+1) and users 2 & user 3 have (3+1) MS multislot capability
1 Basics
User 1:
no multislot
capability
TFI = 5
User 2:
with multislot
capability
TFI = 9
Multislot capability
PDCH 1
User 2
User 2
User 3
User 3
User 2
User 2
User multiplexing
PDCH 2
User 1
User 2
User 3
User 1
User 2
User 2
User multiplexing
User 3:
with multislot
capability
TFI = 13
PDCH 3
Block
User 3
User 2
User 3
User 3
User 2
User 3
n+1
n+2
n+3
n+4
n+5
...
1 Basics
The MS can identify the PDCH blocks intended for it by TFI present on
For an UL TBF, the mobile receives one USF (Uplink State Flag) per
The multiplexing of the different MSs is performed thanks to the TFI which is present in the RLC
block header.
An MS decodes all the blocks of all its allocated PDCHs and keeps the blocks carrying its TFI in the
RLC header.
Uplink PDTCH and PACCH for a UL TBF:
At UL TBF establishment, a MS receives a USF (Uplink State Flag, 8 values, MAC header) per allocated
PDCH.
If the MS receives its USF on the downlink block n of PDCH I, it can transmit in uplink using the block
n+1 of PDCH i.
NB: the values of the USF are entirely dedicated to PDTCH and PACCH transfers. See further (MPDCH
and RRBP) The TFI is use in the UL as well: each mobile shall put its TFI in the UL header of the UL
blocks during a UL TBF, as well as in the RLC header of the UL PACCH blocks of a DL TBF. So we can say
that the de-multiplexing of the blocks is achieved by the use of a TFI.
1 Basics
RRBP values indicates the number of TDMA frames the MS shall wait before
transmitting its uplink RLC/MAC block
DL:
Use of the RRBP field transmitted in the downlink (MAC header) in association with the TFI of the DL
TBF in the RLC header.
At the exact occurrence of the RRBP, a special USF value is used for the UL TBF taking place on the
same PDCH: USF=no emission.
It is a semi-boolean parameter. The RRBP field of a RLC/LAC block is checked each time by the MS
When the RRBP field is valid, the value gives the number of blocks to wait before sending its PACCH
block in the UL
S/P is false means MS has to send an acknowledgement message to the MFS.
1 Basics
Block
number
Bn
Bn+1
Bn+2
Bn+3
Bn+4
Bn+5
Bn+6
TFI
TFIa
TFIb
TFIa
TFIb
TFIb
Downlink
USF
RRBP
USFj
USFk
USFj
FREE
No
Emission
TFIb USFj
TFIa USFk
+3
Uplink
PDTCHj
PDTCHk
PDTCHj
PRACH
PACCHa
PDTCHj
1 Basics
Idle
Idle
GPRS
attach
Ready
Standby
Timer
expiry
Timer
expiry
Standby
timer T_READY keeps the MS in the Ready state just after data transfer.
no Temporary Block Flow exists. Upper layers can require the transfer of an LLC PDU which, implicitly, may trigger the
establishment of TBF and transition to packet transfer mode.
the MS listens to the PBCCH and to the paging sub-channel for the paging group the MS belongs to in idle mode. If PCCCH is not
present in the cell, the mobile station listens to the BCCH and to the relevant paging sub-channels.
In packet transfer mode, the mobile station is allocated radio resource providing a Temporary Block Flow on one or more
physical channels. Continuous transfer of one or more LLC PDUs is possible. Concurrent TBFs may be established in opposite
directions. Transfer of LLC PDUs in RLC acknowledged or RLC unacknowledged mode is provided.
When selecting a new cell, mobile station leaves the packet transfer mode, enters the packet idle mode where it switches to
the new cell, read the system information and may then resume to packet transfer mode in the new cell.
The timers regulating the transition between states are SGSN timers, not tunable in the BSS. Caution: Idle mode in GPRS and Idle
mode in GSM are two different states.
A GSM MS in Idle mode is attached to a MSC and can be paged
PDU transmission
Standby:
Ready:
Ready
GPRS
detach
A GPRS MS in Idle mode is NOT attached to a SGSN, so it cannot be paged but can monitor the GPRS information broadcast in
the SI13 of the BCCH.
The MS state in the SGSN shall be considered apart from the Packet Transfer Mode in the BSS:
MS in Standby mode can be in Packet Transfer Mode.
MS in Ready mode can be in Packet Idle Mode.
The detach procedure is usually triggered by the MS. Three other types of detach are triggered by the CN:
HLR Detach,
1 Basics
GMM States
GMM Ready
GMM Standby
RR Operating Modes
PTM: TBF opened
1 Basics
Aim
1 Basics
Results
1 Basics
Aim
in order to send and receive GPRS data, the MS must activate the PDP
Results
the MS is known in the corresponding GGSN (the GGSN knows the SGSN
1 Basics
Cell update
RA update
RA/LA update
The MS sends any LLC frame in the new cell with its TLLI in the header.
The Cell and RAC information is added by the BSSGP at the programming of the BSSGP frame
RA Update:
The MS sends an RA Update Request message containing the identity of the MS, the old RAI and the
Update Type. The update type is either enter a new RA or periodical RA update.
The BSS adds the cell global Identity when transferring the message into a BSSGP frame towards the
SGSN.
1 Basics
GSM paging, Routing Area (RA) was defined which may be smaller
than Location Area (LA)
One RA is a subset of one and only one LA
RAI (RA Identity) identifies several cells
the SGSN
One RA is served by only one SGSN
1 Basics
Paging Coordination
NMO
CS Paging
Channel
PS Paging
Channel
CCCH
CCCH
(not applicable)
CCCH
PCCCH
CCCH
CCCH
II
III
PCCCH
CCCH
PCCCH
CCCH
Characteristics
- Gs interface
- MPDCH
- Gs interface
- no MPDCH
- Gs interface
- no Gs interface
- no MPDCH
- no Gs interface
- MPDCH
- no Gs interface
- no MPDCH
Since B7, all the possible combinations with the MPDCH are:
NMOIII,
The NMO setting is done from the OMC-R via the NETWORK_OPERATION_MODE parameter.
1 Basics
In PTM mode
UL TBF establishment during a DL TBF on the uplink PACCH
DL TBF establishment during a UL TBF on the downlink PACCH
The TBF establishment is performed through two types of access requests:
One phase access request
Two phase access request
1 Basics
MS is in PIM mode:
MS
The MS
switches
on the
assigned
PDCH
BSC
Also PRACH
(E)GPRS mode
Immediate assignment
AGCH
Also PAGCH
Packet UL assignment
PACCH
Packet control Ack
PACCH
MFS
Channel request + TA
Resource
1
Immediate assignment allocation
TFI, USF, TAI, TA
1 Basics
time
each MS sends its TLLI (and TFI)
the TLLI is present in the acknowledgement from the MFS
the MS with the wrong TLLI is discarded
1 Basics
MS is in PIM mode:
MS
BSC
Channel request + TA
Also PRACH
(E)GPRS mode
Immediate assignment
AGCH
Also PAGCH
Packet resource request
PACCH
The MS
switches
on the
assigned
PDCHs
Packet UL assignment
PACCH
Packet control Ack
PACCH
RLC data block
PDTCH
MFS
Immediate assignment
TBF starting time, TA Single block
allocation
Packet resource request
TLLI
Packet UL assignment, polling
TFI, USFs, TAI, TLLI
Packet control Ack
Resource
allocation
Resource
activation
1 Basics
Main difference:
1 Basics
MS is in PIM mode:
MS
1 PDCH
allocated
PDCH(s)
allocated
4 access bursts
BTS
Immediate assignment
PCH
Also PPCH
Packet DL assignment
PACCH
BSC
Resource
allocation
Immediate assignment
TFI, TAI
MFS
LLC PDU
1 Basics
If GPRS is supported :
Note: do not confuse RA_COLOUR and RA Code. The former is used as a flag which has two uses for the
to know if the GPRS service is supported in the cell (RA_COLOUR has a value different from -1).
to trigger an RA update when the value of the RA_COLOUR changes. It is easy to monitor because it is
broadcast often.
The Routing Area Code is necessary for the RA update procedure (message content).
The SI13 takes the place of a few SI1 occurrences.
1 Basics
each time the SI13 content is updated (PSI field = SI13_CHANGE_MARK set to 1).
every 30 seconds max (even if the TBF has to be interrupted).
The MS has always the time to switch on PSI13 in NMOIII and/or NMOI with a Master PDCH
because PBCCH blocks are always after a I or X TS within the 52 multi-frame.
Access Burst Type: it defines the access burst (8 bits or 11 bits) to be used on the PRACH, PTCCH and
When the Master Channel is present in the cell, the System Information Type 13 message has different
The radio description of the Primary Master Channel (in terms of time slot number, training
sequence code and frequency parameters).
One GPRS Mobile Allocation (MA), if frequency hopping is used for GPRS. This is the GPRS MA of
the Primary Master Channel, if hopping. If the Primary Master Channel is not hopping, the MA
corresponds to the hopping TRX(s) used for GPRS, if any.
Three modes of cell reselection have been defined by the 3GPP Standard for GPRS MSs. These
Network Control (NC) modes, known as the NC0, NC1 and NC2, are shortly described below:
NC0: the GPRS MS performs autonomous cell reselection without sending measurement reports to
the network.
NC1: the GPRS MS performs autonomous cell reselection. Additionally it sends measurement
reports to the network.
NC2: the GPRS MS shall not perform autonomous cell reselection. It sends measurement reports
to the network. The network controls the cell reselection.
1 Basics
C32 criteria)
Cell Parameters
The GPRS cell adjacencies are the same for a MS in Packet Idle Mode as for a MS in Packet Transfer
1 Basics
PSI3, PSI3bis:
One PSI3 instance shall be sent and, as a minimum, one PSI3bis instance shall be sent as well
Neighbor cell parameters: BSIC, BCCH frequency, SI13 PBCCH location, GPRS_RXLEV_ACCESS_MIN,
GPRS_MS_TXPWR_MAX_CCH, GPRS_TEMPORARY_OFFSET, GPRS_PENALTY_TIME,
GPRS_RESELECTION_OFFSET.
Up to 32 neighboring cells may be defined. The field Same_RA_As_Serving_Cell provides
complementary information for reselection process.
1 Basics
PSI 3 / 3bis
1 Basics
1 1 80
GCH (GPRS channel). One GCH uses one Abis nibble and one Ater nibble
Carry CS traffic
Carry PS traffic but only coded with (M)CS-1 or (M)CS-2
Located on Primary Abis
Extra nibbles
Come from additional Abis timeslots for support of high speed packet traffic
Carry PS traffic only
Located on Primary or Secondary Abis
1 Basics
1 Basics
Class 1
Simple
Class 2
Double
GPRS CS 1,2,3,4
EDGE MCS 1,2,3,4,5,6
Class 5
Quintuple
GPRS CS 1,2
EDGE MCS 1,2
GPRS CS 1,2,3,4
EDGE MCS 1,2,3,4,5
Class 3
Triple
Class 4
Quad
G3 or G4 TRX
GPRS CS 1,2,3,4
EDGE MCS 1,2,3,4,5,6,7,8
GPRS CS 1,2,3,4
EDGE MCS 1,2,3,4,5,6,7,8,9
EGCH
An EGCH is made up of a pool of GCHs (from 1 to 5): One main GCH and a pool of auxiliary GCHs (the
GCH uses the basic 16k Abis nibble).
TRX class
The TRX class is defined at MFS level. For a TRX class n, the MFS will use n GCHs to establish one
EGCH. The TRX class varies with the hardware TRX capabilities (TRX type, Hardware PS capability).
Higher the TRX class is, higher the PDCH throughput is.
In case of EGCH establishment, from one to five AterMux nibbles will be necessary. Nibbles have not
to be contiguous.
These nibbles will be taken:
- on free nibbles of one or more already switched 64 Kbit/s channels and on an additional 64 Kbit/s
channel, switched for this purpose, or,
When establishing a PDCH, the number of GCH links per radio time slot is determined according to
the TRX class, the PDCH type (SPDCH/MPDCH), and the AterMux congestion state.
Abis Interface
Several Abis nibbles are also used to handle a throughput higher than 16Kbit/s. Abis configuration is
static due to hardware constraints.
Depending on the requested throughput, a radio time slot needs up to 4 extra Abis nibbles in addition
to the basic one.
As all radio time slots of a TRX must have the same throughput capability, a TRX needs up to 8 extra
Abis time slots. These extra Abis time slots are called a TRX transmission pool.
All Rights Reserved 2007, Alcatel-Lucent
3FL 38020 ACAA Edition 2
Section 1 Module 1 Page 82
1 Basics
TRX
TS0 TS1 TS2 TS3 TS4 TS5 TS6 TS7
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
Basic Nibble
Abis
Radio Timeslot
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
TS0
TS1
TS2
TS3
TS4
TS5
TS6
TS7
Basic
Timeslots
Basic
Timeslots
6 Extra
Timeslots
Extra Nibbles
1 Basics
Primary Abis
EVOLIUM
BTS
Secondary Abis
Primary Abis
BTS
BTS
Topology 1
EVOLIUM
BTS
Secondary Abis
Topology 2
1 1 85
2 B9 features
2 B9 features
1 1 86
reducing the duration of the phase where the MS acquires PSI in the target cell
Packet SI Status procedure, same scope as above for SI in the target cell
Network Assisted Cell Change procedures
reducing, in NC0 and NC2 mode, the duration of the phase where the MS
acquires target cell (P)SI, in the serving cell
allowing, in NC0 mode, the MS to indicate its wish to perform a cell reselection
2 B9 features
2 B9 features
The feature main benefits are: reduced (may be 0) delay before next UL transmission (no new TBF to establish) and
In uplink, it can avoid to re-establish TBF for subsequent burst of data from the same higher layer transaction,
and it avoids to establish a new TBF if new data arrive during countdown procedure on the current TBF.
In uplink, it can avoid to re-establish TBF for subsequent burst of data from the same higher layer transaction,
and it avoids to establish a new TBF if new data arrive during countdown procedure on the current TBF.
in downlink, it allows to perform more often the TBF establishment on concurrent TBF and it saves the DL
bandwidth by sending dummy UI commands (on the DL TBF is in delayed release state) if a concurrent TBF exists.
Both effects are expected to improve the end-to-end transmission delay and consequently to reduce the transfer
duration.
The mechanism proposed has the following characteristics:
The BSS shall be able to acquire the MS capability as fast as possible, using the Radio Access capability update
procedure (or information stored in other GPUs).
When the MS does not support the extended UL TBF mode , the BSS will use the normal release procedure, and
apply the delayed Final PUAN procedure if T_Delayed_final_PUAN is not 0.
If the MS capabilities are not yet known by the BSS at UL TBF establishment, the BSS shall be able to switch to
extended UL TBF mode if the MS capabilities are received before the release of the uplink TBF has been
initiated.
During the uplink TBF extension (i.e., after the last LLC frame has been received from the MS and no data is
being transmitted by the MS), it allows the network to initiate sending of data to the MS without performing a
downlink TBF establishment oncommon control channels.
It allows the MS to send data from newly arrived LLC frames after the countdown has started.
While in the delayed state the network must allocate some radio blocks, to allow the MS to restart the uplink
transfer whenever required by the application.
All Rights Reserved 2007, Alcatel-Lucent
3FL 38020 ACAA Edition 2
Section 1 Module 1 Page 88
2 B9 features
Traffic model changes: the feature will modify the number of UL TBF
2 B9 features
this feature:
uplink.
T_MAX EXTENDED_UL: Maximum duration of the extended uplink TBF
phase. Recommended rule: value between 1s and 2s.
EN_FAST_USF_UL_EXTENDED: Enable the transmission of USF every
20ms in extended mode, when the extended UL TBF feature is activated.
EN_RA_CAP_UPDATE: Enable the Radio Acces Capability update on Gb.
Recommended rule: should be enabled if EN_EXTENDED_UL_TBF is
enabled and RA cap. update is supported by SGSN.
Fast USF UL extended : to keep the link alive in order to be ready as soon as needed. If n MSs in extended,
then USF for 1 MS sent every n x 20ms.
RA CAP Update : the MFS can request the RA capabilities of the MS to the SGSN (based on IMSI)
2 B9 features
introduced.
Release
Modulation
B8
GMSK
B8
GMSK
B8
GMSK
MCS-1
B8
GMSK
MCS-3
B8
B8
B8
B8
GMSK
GMSK
GMSK
CS-1
CS-2
CS-3
User data
rate
8.0 kbit/s
12.0 kbit/s
14.4 kbit/s
CS-4
20.0 kbit/s
MCS-2
11.2 kbit/s
MCS-4
17.6 kbit/s
8.4 kbit/s
14.8 kbit/s
B9
8-PSK
MCS-5
22.4 kbit/s
B9
8-PSK
MCS-7
44.8 kbit/s
B9
B9
B9
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
GMSK
Coding
scheme
8-PSK
8-PSK
8-PSK
MCS-6
MCS-8
MCS-9
29.6 kbit/s
54.4 kbit/s
59.2 kbit/s
2 B9 features
2 B9 features
2 B9 features
2 B9 features
Support of distributions
Counter
Mnemonic
Rationale
P453a
DISTRIB_UL_TBF_DURATION
P453b
DISTRIB_DL_TBF_DURATION
P454a
DISTRIB_UL_TBF_VOLUME
P454b
DISTRIB_DL_TBF_VOLUME
P455a
DISTRIB_UL_PDCH_UNIT_ALLOC
The distribution of the number of PDCH units assigned to an UL TBF is required to check whether
non-optimal allocations come from a lack of radio resources. In this case, parameters like
MAX_PDCH, MAX_PDCH_HIGH_LOAD can be increased.
P455b
DISTRIB_DL_PDCH_UNIT_ALLOC
Support of distributions
Actually, Support of distributions is an enhancement for the feature Radio Measurement Statistics
(RMS), introduced on release B7.2, in order to get statistics on radio measurements such as RXLEV,
RXQUAL, interference level, timing advance, MS or BS transmitted power, etc.
This sub-feature introduces a new concept of counters to monitor PS resource usage. The existing PS
counters count a number of events occurring during the reporting period (i.e. every hour). However,
such counters do not allow retrieving the distribution of the events. For instance, existing counters
allow evaluating the averaged duration of the TBFs. However, it is interesting to know what is the
proportion of short TBFs compared to long TBFs, to evaluate the type of GPRS traffic, to understand
the throughput measured in the fields, etc.. New counters, called distribution, were introduced. The
B7.2 RMS feature is based on the following principles:
- The operator can launch RMS from the OMC-R on a per cell or per BSC basis for a given duration (up
to 23 hours).
- The radio measurements are monitored the closest to the observed functions, i.e. in the BTS.
- During the observation period, it is possible to launch extended measurement reporting in order to
get measurements on radio frequencies not used for CS/PS traffic in the cell.
The measurements are usually reported in vectors made of 10 values (or matrixes made of several
vectors). The ranges of each vector are defined by 9 thresholds. These thresholds are changeable at
the OMC-R.
2 B9 features
Definition
P105c
P105e
Number of DL TBF establishment failures due to CPU processing power limitations of the
GPU.
P105d
P105f
P105g
P105h
Instance
Cell
Cell
Cell
Number of UL TBF establishment failures due to CPU processing power limitations of the
GPU.
Cell
Cell
Cell
2 B9 features
Mnemonic
P38f
CUMULATED_TIME_PDCH_USED_UL_CELL
P38e
CUMULATED_TIME_PDCH_USED_DL_CELL
P451b
CUMULATED_TIME_PDCH_DL_TBF_CELL
P98f
NB_SUSP_UL_TBF_REL
P98e
NB_SUSP_DL_TBF_REL
P451a
P452
CUMULATED_TIME_PDCH_UL_TBF_CELL
CUMULATED_TIME_PDCH_DL_TBF_GMM_SIG_CELL
Rationale
Class B
Class B mobile phones can be attached to both GPRS and GSM services, using one service at a time. Class B
enables making or receiving a voice call, or sending/receiving an SMS during a GPRS connection. During voice
calls or SMS, GPRS services are suspended and then resumed automatically after the call or SMS session has
ended.
This is suspend / resume
2 B9 features
existing (E)GPRS traffic model (i.e. better accuracy of the model can
be achieved) but no impact on radio and other telecom
performances is expected.
2 B9 features
The purpose of this feature is to give to the MFS all the radio
timeslots that are usable for PS traffic, according to the whole BSS
load (CS and PS loads). The MFS needs no more to request radio
timeslots to the BSC; instead the MFS is always aware of all the
available radio timeslots.
2 B9 features
Main principles:
throughputs.
To give to the MFS all the radio timeslots that are usable for PS traffic
Max CS traffic without PS traffic
Max PS traffic without CS traffic
priority for CS
reserved for CS
MIN_SPDCH
MAX_SPDCH_HIGH_LOAD
MAX_SPDCH_LIMIT
MAX_SPDCH
MAX_SPDCH_LIMIT is computed by the BSC and defines the number of SPDCHs that are allocated to the
The allocated SPDCHs are always those having the highest priority for PS allocations and their positions
are provided to the MFS within a new message called Radio Resource (RR) Allocation Indication message
TBFs allocated in the MAX_SPDCH_HIGH_LOAD zone cannot be pre-empted (T1 re-allocation) when
Periodically, the MFS sends to the BSC a Radio Resource Usage Indication message. This message
contains the allocated SPDCHs in the MFS as well as their usage. This message is used by the BSC to
estimate the PS load
If required, the MFS may pre-empt a few SPDCHs to give them back to the BSC. The MFS uses the same
Radio Resource Usage Indication message to indicate to the BSC the de-allocated SPDCHs and to
acknowledge the allocation of new SPDCHs
Reserved for PS: This zone defines the number of radio resources reserved for PS traffic. No CS traffic can
be carried in that zone. The size of this zone is defined by the parameter MIN_SPDCH.
Priority for PS: This zone defines a number of radio resources where CS and PS traffic can be carried, but
the preference is given to PS traffic in that zone. The size of this zone is defined by the parameters
MAX_SPDCH_HIGH_LOAD and MIN_SPDCH.
Priority for CS: This zone defines a number of radio resources where CS and PS traffic can be carried, but
the preference is given to CS traffic in that zone. The size of this zone is given by the difference between the
parameters MAX_SPDCH and MAX_SPDCH_HIGH_LOAD.
Reserved for CS: This zone defines the number of radio resources reserved for CS traffic. No PS traffic can
be carried in that zone. The size of this zone is defined thanks to the parameter MAX_SPDCH.
2 B9 features
2 B9 features
The BSS may reject an external HO incoming from the UTRAN, provided the HO
has not been triggered by an emergency cause
Current load will be compared with a new threshold, namely
THR_CELL_LOAD_3G_REJECT
2 B9 features
declare per 2G cell basis the 3G neighbor cells (the FDD UMTS frequencies
and the scrambling codes). Maximum 3 FDD UMTS frequencies may be
declared per cell basis. When knowing in advance the frequency and the
scrambling code of a 3G cell, an MS should require 10 to 20ms to
synchronize on that cell.
2 B9 features
Regarding the current load, the BSS may reject an external hand-over
coming from the UTRAN, provided the hand-over has not been triggered
by an emergency cause, i.e. provided the hand-over request does not
carry a cause type uplink/downlink quality/strength.
2 B9 features
2 B9 features
This feature provides a solution to share the Ater and Abis nibbles
Terminology
M-EGCH
- The term M-EGCH (Multiplexed-EGCH) is used to refer to a link established between the MFS and
the BTS. An M-EGCH is defined per TRX (instead of an EGCH per radio timeslot in release B8).
GCH
- A GCH is the 16kb/s channel between the MFS and the BTS. It is composed of an Ater nibble and an
Abis nibble cross-connected together in the BSC. The MFS or the BTS periodically send blocks on a
GCH every 20 ms.
GCH frame
- In 20 ms period (also called block period), a number of 320 bits of this GCH can be used: this is the
frame.
Segment
- A segment is formed by a part of an RLC block (after its segmentation on the M-EGCH link) and a
GCH header (different for first segment and subsequent segments). RLC data might be padded or a
segment can be a no-data segment.
- Note that in B9 a frame can be constituted of several segments belonging to different RLC blocks as
now all the RLC blocks sent on several PDCHs of a TRX are multiplexed on the same M-EGCH link.
Padding bits are added to the RLC blocks segments to fill the frame to 320 bits.
2 B9 features
The GCH left while the control blocks are transferred can also be re-
used by other TBFs (which is not the case in B8); indeed control
blocks are encoded with CS1 and do not use an entire 320-bit frame.
The Statistical Multiplexing introduces a new segmentation of the radio blocks on the M-EGCH link: the blocks
of all the PDCHs of the TRX are sent one after the other without padding between them. As in B8 a block for a
PDCH can be spread over several 320-bit frames but after its last segment the block of another PDCH can be
started (if the remaining transmission capacity is sufficient). So a fixed 320-bit frame can have up to 2 or 3
segments of variable size. As in B8, the unused part of a 320bit frame (once all the PDCHs have been
scheduled) is filled with padding and the unused GCHs with a NODATA PDU.
The EGCH layer is highly impacted to support the statistical multiplexing and is renamed M-EGCH layer in
B9. This feature only applies to G3 and G4 TRX while the G2 DRFU TRX uses a B7.2 like GCH stack (1 GCH
allocated per PDCH to support up to CS2 TBFs).
2 B9 features
2 B9 features
2 B9 features
2 B9 features
Deals with the determination of the number and of the nature of the
It is in charge of:
links
Managing transmission resource preemptions
Managing Abis and/or Ater congestion states,
To ensure that, anytime, each cell of a given BTS would be able to support PS traffic, we should
guarantee a minimal number of Abis nibbles to every cell in the BTS. Consequently, it has been
decided that basic Abis nibbles are only shared at cell level (i.e. among TRXs of the same cell or
sector). This restriction prevents some cells from using the whole Abis nibbles of the BTS as a
given cell cannot use the basic Abis nibbles of another cell. However, Extra (and Bonus) Abis
nibbles are shared at BTS level.
A given amount of Ater transmission resource is allocated per GPU. Afterwards, this Ater
transmission resource is shared among the four DSPs of the GPU thanks to the GPU on-board Ater
switch.
Only 64K Ater TS are handled at GPU-level between DSPs. Thus, a 64K Ater TS may be moved
from one DSP to another if, and only if, all its four 16K Ater nibbles are free. This is the unique
restriction to Ater nibbles sharing at GPU-level.
Furthermore, to prevent the above restriction from disturbing the First GPRS traffic in a cell, an
Ater reserve shall always be available. The Ater reserve consists on one or several free 64K Ater
TSs and is defined per GPU. Every 64K TS of the Ater reserve may be connected to any DSP of the
GPU to fulfil GCH requests:
to establish the initial GCH in a cell with the Fast Initial GPRS Access feature activated, or;
to ensure the First GPRS traffic in a cell with no active initial GCH.
Each time a 64K TS is taken from the Ater reserve, a process is launched to retrieved another 64K
TS to replace it in the Ater reserve. This is done by means of GCH pre-emption on the Best effort
traffic supported by the GPU.
2 B9 features
This feature allows monitoring the proper operation of AMR and the
RMS_I1 Indicators:
Mnemonic
RMS_AMR_FR_UL_BAD
RMS_AMR_HR_UL_BAD
RMS_AMR_FR_UL_RXLEV_UL
RMS_AMR_HR_UL_RXLEV_UL
RMS_AMR_FR_DL_RXLEV_DL
RMS_AMR_HR_DL_RXLEV_DL
Definition
Number of bad speech frames using any
AMR FR codec in uplink
Number of bad speech frames using any
AMR HR codec in uplink
Number of speech frames using one
AMR FR codec in uplink per Rxlev on
the uplink path
Number of speech frames using one
AMR HR codec in uplink per Rxlev on
the uplink path
Number of speech frames using one
AMR FR codec in downlink per Rxlev on
the downlink path
Number of speech frames using one
AMR HR codec in downlink per Rxlev on
the downlink path
Formula
RMS44a
RMS45a
RMS46a
RMS48a
RMS47a
RMS49a
2 B9 features
Knowing which codecs are the most used, and comparing them with
link level in the cell, the operator could assess the voice quality and
possibly adapt the AMR parameters (definition of the subset,
thresholds and hysteresis).
These parameters are different for AMR FR and AMR HR, information
2 B9 features
RM_I2 Indicators:
Mnemonic
RMS_TPR_TIMING_ADVANCE
RMS_TPR_UL_RXLEV_TA_BAN
D
RMS_TPR_DL_RXLEV_TA_BAN
D
RMS_TPR_UL_RXQUAL_TA_BA
ND
RMS_TPR_DL_RXQUAL_TA_BA
ND
Definition
The distribution of number of
measurement reports for which the value
of timing advance is in TA band
The average value of RXLEV per TA band
in uplink.
The average value of RXLEV per TA band
in downlink.
The average value of RXQUAL per TA
band in uplink.
The average value of RXQUAL per TA
band in downlink.
Formula
RMS50a
RMS51
RMS52
RMS53
RMS54
2 B9 features
1 1 116
selection
reselection
Cell 1
Cell 2
RA A
Cell 3
RA B
LA 1
LA 2
GMM standby:
Only NC0 mode is applied. Cell reselection is identical to the basic GSM cell reselection in idle mode.
C1 and C2 criteria are used
GMM ready:
NC2 mode is applied if set by the Operator. C1NC2, C2NC2 criteria are used
NC0 mode is applied if NC2 mode is not set and consequently C1, C31 and C32 criteria are used
GMM standby:
GMM ready:
Only NC0 mode is applied. C1, C31 and C32 criteria are used
NC2 mode is applied if set by the Operator. C1NC2, C31NC2 and C32NC2 criteria are used
NC0 mode is applied if NC2 mode is not set and consequently C1, C31 and C32 criteria are used
In GSM
- A = RLA_C - RXLEV_ACCESS_MIN
In GPRS ready and standby states, cell reselection is performed by the MS except for a class A MS while
in dedicated mode of a circuit switched connection, in which case the cell is determined by the
network according to the handover procedures.
For a class B MS which can combine GSM and GPRS states, C1 criterion is used when the MS
simultaneously attached to both, the network and the MS is in Packet Idle Mode (refer to GSM 05.08).
A = RLA_C - RXLEV_ACCESS_MIN
B = MS_TXPWR_MAX_CCH P
AV_RXLEV_NC2(n) is the average received signal level measured by the MS on the BCCH of the cell n.
the MS Radio Access Capability Information Element provided in the Packet Resource Request message
or in the DL LLC PDU. In the NC cell reselection procedure, the parameter P(n) shall always refer to the
RF power capability of the GMSK modulation.
The cell ranking criterion parameter C2NC2 is used to order the candidate cells on an radio criterion.
This criterion applies only in serving cells where there is no PBCCH established.
PENALTY_TIME(n) indicates whether the cell reselection offset shall be positive or negative.
C2 criterion:
PENALTY_TIME = 11111
C2 = C1 - CELL_RESELECT_OFFSET
If CELL_RESELECT_PARAM_IND = 0 then C2 = C1
serving cell
Is used as a minimum signal level criterion for cell reselection for GPRS
The best cell is the cell with the highest C32 value, among those cells that
have the highest priority class, among those cells that have highest LSA priority
The best cell is the cell with the highest C32 value, among all the neighbor
cells
The signal level threshold criterion parameter C31NC2 is used in hierarchical cellular networks to
determine whether the signal level received from a neighboring cell n is sufficient to redirect the MS
towards cell n based on a non-radio priority criterion. This criterion parameter is used only if there is a
PBCCH established in the serving cell. HCS_THR(n) defines a signal threshold for applying the
prioritized hierarchical GPRS cell reselection criterion. The cell n denotes either the serving cell or a
neighboring cell. Contrary to the C31 criterion implemented in the MS, the Alcatel BSS does not
manage the timer T implemented for each cell to monitor the time a neighboring cell is present in the
list of the strongest carriers. Therefore, the Alcatel BSS always assumes that
GPRS_TEMPORARY_OFFSET(n) = 0. As the GPRS_CELL_RESELECT_HYSTERESIS,
RA_RESELECT_HYSTERESIS, and C31_HYST are used to control the triggering conditions of a cell
reselection, they are not taken into account in the criterion C31NC2 and C32NC2 parameters.
The cell ranking criterion parameter C32NC2 is used to order the candidate cells on an radio criterion.
This criterion applies only in serving cells where there is a PBCCH established.
GPRS_RESELECTION_OFFSET(n) applies a positive or negative offset which favors or disfavors the
neighboring cell n. The cell n denotes either the serving cell or a neighboring cell. If the parameter
C32_QUAL is set, the determination of C32NC2 is modified so that the neighboring cell n having the
highest AV_DL_RXLEV_NC2 among all the neighboring cells is applied a GPRS_RESELECTION_OFFSET
(only if the offset is positive) and no GPRS_RESELECTION_OFFSET is applied to the other neighboring
cells.
The MFS shall take care of avoiding ping-pong effects between the old cell and the new cell (i.e.,
circular NC cell reselections). For that purpose, the MFS handles an anti-ping-pong timer and an anti
ping-pong offset, respectively called T_NC_PING_PONG and NC_PING_PONG_OFFSET. While the timer
T_NC_PING_PONG is running the neighboring cells are disfavored by the offset NC_PING_PONG_OFFSET
(expressed in dB) in the cell ranking process.
The MFS starts the anti-ping-pong timer at the creation of the NC2 context for the MS.
The MFS stops the anti ping-pong timer at the deletion of the NC2 context.
C31 criterion
Serving cell:
Neighbor cell:
C31(n) =
GPRS_PRIORITY_CLASS(n)
GPRS_PRIORITY_CLASS(n)
GPRS_PRIORITY_CLASS(s)
GPRS_PRIORITY_CLASS(s)
<>
= RLA_P(n) GPRS_HCS_THR(n)
GPRS_TEMPORARY_OFFSET(n)
= RLA_P(n) - GPRS_HCS_THR(n)
= RLA_P(n) - GPRS_HCS_THR(n)
= RLA_P(n) - GPRS_HCS_THR(n)
cell:
GPRS_HCS_THR is the signal threshold for applying HCS GPRS and LSA re-
selection
C32 criterion
Serving Cell:
C32(s) = C1(s)
Neighbor cell:
C32(n) =
GPRS_PRIORITY_CLASS(n)
GPRS_PRIORITY_CLASS(n)
GPRS_PRIORITY_CLASS(s)
GPRS_PRIORITY_CLASS(s)
= C1(n) +
GPRS_ RESELECTION_OFFSET(n)
= C1(n) +
GPRS_ RESELECTION_OFFSET(n)
<>
= C1(n) +
= C1(n) +
GPRS_ RESELECTION_OFFSET(n) GPRS_ RESELECTION_OFFSET(n)
GPRS_TEMPORARY_OFFSET(n)
seconds, as well as more than one sample per second for each BCCH carrier.
A list of 6 strongest cells shall be kept updated at a rate of at least one update per running average
period.
In Packet Transfer Mode, the MS shall monitor a list of 6 strongest non-serving cell BCCH carriers. It
shall attempt to check the BSIC for each of these 6 strongest cells at least once every 10 seconds.
1. CS change
TBF 1 (Cell 1)
Cell
Re-Selection
TBF 2 (Cell 2)
CS 2
Average
Throughput
Throughput
CS 1
t0
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
t1
t2
t3
t4
t5
Time
[s]
Each time the MS performs a cell reselection, the data transfer is interrupted and a retransmission of
Then, the MS establishes a new UL TBF in this cell to send a Cell Update message to the SGSN.
The MFS deletes or reroutes towards the new cell the LLC PDUs stored in the old cell.
- if they are deleted, a retransmission is needed.
Finally, the data transfer is re-started (after a DL TBF establishment, in case of DL transfer).
All these steps degrade the data throughput or the page access time perceived by the enduser.
NC2 activation
UL serving cell: RXQUAL for GPRS TBF and mean BEP for EGPRS TBF
DL serving cell: RXQUAL for GPRS TBF and mean BEP for EGPRS TBF
DL serving and neighbor cells: RXLEV measurements of BCCH
mode, however since no network manufacturer has implemented the NC2 mode, the R97 and R98 MSs
may not have been sufficiently tested and therefore there is a risk of interoperability with these MSs.
The Packet Measurement Order message is used to activate and de-activate the NC2 mode of
Activation
establishing the first Downlink TBF of the Packet Transfer Mode or when re-establishing
the DL TBF while T3192 is running and there is not any on-going UL TBF.
no measurement report has already been received for that MS during its on-going packet
transfer(s) (UL and/or DL).
the MS has not been forced to operate in NC2 mode by a Packet Cell Change Order
message (during an intra-RA cell reselection).
De-activation
- The Packet Measurement Order (RESET) message is sent at the end of the data transfer, in
case of NC2_DEACTIVATION_MODE = NC2 deactivation at the end of the packet transfer.
- When the MS goes back to the STANDBY state, in case of NC2_DEACTIVATION_MODE = NC2
deactivation at GMM Ready timer expiry.
NC2 reselection are triggered only for EMERGENCY or for POWER BUDGET
causes:
Cause
Cause
Cause
Cause
PT
PT
PT
PT
1:
2:
3:
4:
The criteria calculated by the BSS in NC2 mode are very near from those
used by the MS in NC0 mode. This ensures that the target cell selected
by the MS in NC0 mode or by the BSS in NC2 mode are identical in quite
all cases
C1NC2, C2NC2, C31NC2 and C32NC2 criteria are calculated by the BSS and the
parameters defined for cell reselections in NC0 are re-used
No PBCCH
ANC2(n) = AV_RXLEV_NC2(n) RXLEV_ACCESS_MIN(n)
BNC2(n) = MS_TXPWR_MAX_CCH(n) P(n)
PBCCH established
ANC2(n) = AV_RXLEV_NC2(n) GPRS_RXLEV_ACCESS_MIN(n)
BNC2(n) = GPRS_MS_TXPWR_MAX_CCH(n) P(n)
The cause PT1 is equivalent to check the condition C1NC2 < 0 assuming that the (GPRS_)RXLEV_ACCESS_MIN
threshold is replaced with NC_DL_RXLEV_THR threshold.
Max (Bnc2,0) = handicap on threshold if MS can't reach max UL tx power recommended in the cell
and
{
No PBCCH:
C2NC2(n) > C2NC2(s) + NC_RESELECT_HYSTERESIS (s,n)
PBCCH established:
C32NC2(n) > C32NC2(s) + NC_RESELECT_HYSTERESIS (s,n)
}
Cause PT2 is checked among the neighboring cells n upon receipt of a Packet Measurement Report message. It
is triggered if the value C2NC2 or C32NC2 of one neighboring cell n exceeds the value C2NC2 or C32NC2 of the
serving cell s by at least the O&M hysteresis NC_RESELECT_HYSTERESIS(s,n) defined per cell adjacency link
(respectively whether or not there is a PBCCH in the serving cell).
used to order the candidate cells on a radio criterion and applies only in
C32NC2(n) = C1NC2(n)
Cell n is a neighbor cell:
C32NC2(n) = C1NC2(n) + GPRS_RESELECT_OFFSET(n)
Cause PT4
is checked only for the serving cell whenever one UL RLC data block is correctly received for the ongoing UL TBF provided that T_NC_RXQUAL_VALID seconds have elapsed since the computation of the
first UL samples of the UL TBF.
T_NC_RXQUAL_VALID aims at not triggering false alarms at the beginning of the TBF and not
triggering an NC cell reselection for a very short TBF.
Cause PT3
is checked only for the serving cell each time a (EGPRS) Packet Downlink Ack/Nack message is
received provided that the DL TBF is not in delayed release state and provided that the
T_NC_RXQUAL_VALID seconds have elapsed since the receipt of the first Packet Downlink Ack/Nack
message of the DL TBF.
T_NC_RXQUAL_VALID aims at not triggering false alarms at the beginning of the TBF and not
triggering an NC cell reselection for a very short TBF.
Cell Filtering: this process removes from the list candidates the cells to
No PBCCH
The cell are ranked to their C2NC2 value. The best cell candidate is the cell having the
highest C2NC2 value
PBCCH established
The cell are ranked based on the C31NC2 and C32NC2 criteria. Among the cells, the best
cell is the cell with the highest C32NC2 value among:
o For cells that fulfill C31NC2criterion (C31NC2>0):
All cells
The network triggers the cell reselection by sending a PACKET CELL CHANGE ORDER message
MS
Cell A
SGSN
Cell B
(3)
NC2 deactivation
traffic in the 900 MHz band, due to its better indoor penetration
MS GPRS mainly used in indoor environment
Gain in stability of the GPRS session
configuration
During open loop power control, the MS adapts its output power in
When accessing the network on the (P)RACH the MS uses the output
24 measurements in 480 ms
12 measurements in 480 ms
algorithms
The average levels are calculated by the MS in PIM and PTM modes,
thus proper average level available at transfer start
Averaging
TDRX= parameter which considers the number of measurements that are made
and the paging group; TDRX=BS_PA_MFRMS
BS_PA_MFRMS = number of multiframes needed to send all paging groups
T_AVG_W = 2k/2 /6 (k=1..25, recommended k < 12) is the signal level filter
period for PC in PIM
Default value of k
[6-10]
[6-10]
4
8
10
12
14
16
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
7
8
9
9
Range to
investigate
[1-7]
[5-9]
[6-10]
[6-10]
[7-10]
[7-10]
Averaging
Comparison between GSM averaging and the practical GPRS averaging with
A_LEV_PC=2 and K =4:
50
45
40
35
30
25
20
1
11
16
21
26
31
36
41
46
51
RXLEV_DL
56
61
66
71
76
GSM average
81
86
91
CH : is sent to the MS. This parameter is used for grading the power
Tuning of CH and
CH
MS_Power_MAX = 33 dBm
=1
CH
CH = 0 - 48 - RXLEVUL - PBTS
CH = 33 - 48 - (-80) - 40 = 25 dBm
=
I_LEVEL_TN 1 =
I_LEVEL_TN 2 =
I_LEVEL_TN 3 =
I>C
C - 2dB < I C
C - 4dB < I C - 2dB
C - 6dB < I C - 4dB
MS
Packet DL Ack/Nack
(RXQUAL, I_Level_TNi)
...
Packet DL Ack/Nack
(RXQUAL, I_Level_TNi)
MFS
Averaging
O&M threshold
and hysteresis
- AV_RXQUAL_ST
- AV_RXQUAL_LT
- AV_SIR
Link
adaptation
new CS
current CS
CS1
CS2
CS3
CS4
As it has been observed (in the Alcatel labs during the B8 release validation) that some MS do not
report any interference measurements when the BCCH carrier is included in the frequency hopping
sequence of the allocated PDCH, the algorithm described above is slightly modified in the MR2 version
of the B8 release.
A new triggering condition is used for the CS change between CS3 and CS4. This new triggering
condition shall be applied only to the TBF that do not report any interference level measurements.
Each time a Packet DL Ack/Nack message is received:
either it contains no interference measurements and the new algorithm is applied,
or it contains interference measurements and the standard algorithm is applied.
With the new algorithm, the interference level is replaced by the BLER (RLC BLock Error Rate):
the CS3 BLER is used for a CS change from CS3 to CS4,
the CS4 BLER is used for a CS change from CS4 to CS3.
Remarks :
case of a DL TBF with PDCH allocated on the BCCH TRX and no frequency hopping on the BCCH
TRX : the MS does not report any interference level measurements in the Packet DL Ack/Nack
message (no interference measurements on the BCCH carrier),
case of a DL TBF with PDCH having the BCCH carrier belonging to the frequency hopping
sequence : depending on MS implementation, some MS may not report any interference
measurements (behavior observed in the Alcatel labs during the B8 release validation).
CS1
CS_QUAL_DL_1_2 + CS_HST_DL_LT
CS_QUAL_DL_1_2
CS2
CS_QUAL_DL_2_3 + CS_HST_DL_LT
CS_QUAL_DL_2_3
CS3
0
CS_SIR_DL_4_3
CS3
or
CS4
CS4
CS_SIR_DL_3_4
C S_QUAL_DL_3_4
15
AV_SIR
The change from CS-3 to CS-4 is not only based on AV_RXQUAL_LT for the two following reasons:
RXQUAL range only goes down to 0.2%. However, the change of the coding scheme from CS-3 to CS-4
will probably have to be done for even lower values. Indeed, when the coding scheme is CS-4, in
static (AWGN), a BLER of 0.1 (typical value of the BLER threshold to change from CS-3 to CS-4) is
obtained for a raw BER of 1-(1-0.1)1/456 = 2.10-4. This raw BER would be larger in multipath
channels but is likely to remain below 0.2%. This means that CS_QUAL_DL_3_4 should be close to 0
and that a condition based on RXQUAL is not sufficient to change the coding scheme from CS-3 to CS4.
If the changes from CS-3 to CS-4 and from CS-4 to CS-3 are based on different metrics, a Ping-Pong
effect may occur. Indeed, it may happen that the conditions to change from CS-3 to CS-4 and CS-4 to
CS-3 are simultaneously true in some situations.
MS
BTS
MFS
UL RLC block
RXQUAL
measurement
UL RLC block (RXQUAL)
Averaging
O&M threshold
and hysteresis
- AV_RXQUAL_ST
- AV_RXQUAL_LT
Link
adaptation
new CS
current CS
CS1
CS2
CS3
OR
AV_RXQUAL_ST > CS_QUAL_UL_2_3 + CS_HST_UL_ST
CS4
OR
AV_RXQUAL_ST > CS_QUAL_UL_3_4 + CS_HST_UL_ST
AV_RXQUAL_ST is a short term average whereas AV_RXQUAL_LT is a long term average. The short term
average is used to react quickly in case of fast degradation of the radio conditions.
X = FH or NFH: two thresholds are available for hopping and non-hopping TRXs.
Y = ACK or NACK: two thresholds are available for RLC acknowledged and unacknowledged modes.
CS1
CS_QUAL_UL_1_2 + CS_HST_UL_LT
CS_QUAL_UL_1_2
CS2
CS_QUAL_UL_2_3 + CS_HST_UL_LT
CS_QUAL_UL_2_3
CS3
CS_QUAL_UL_3_4 + CS_HST_UL_LT
CS_QUAL_UL_3_4
CS4
15
AV_SIR
In the uplink, the RXQUAL is available in CS-4 and the SIR measurements are not reported by the BTS to the
MFS so far. Therefore, it is possible to also use RXQUAL measurements to change the coding scheme from CS-3
to CS-4 or from CS-4 to CS-3, contrary to the downlink algorithm, where the SIR was used.
Two new metrics are introduced in EGPRS, Mean_BEP (mean Bit error
Probability) and CV_BEP (Coefficient of Variation of BEP), to offset the fact
that RXQUAL, does not provide an accurate estimation of the bit error rate
of the radio channel
BEP measured on burst basis, is a reflection of the current C/I, time dispersion
MEAN_BEPblock =
1 4
BEPburst i
4 i=1
The variation of BEP value over several bursts also provides additional
1 4
1 4
BEPburst k BEPburst i
3 k =1
4 i=1
4
1
BEPburst i
4 i=1
The mechanism is more efficient than in GPRS, since measurements are taken on
For more details about MEAN_BEP and CV_BEP averages performed by the MS, refer to 3GPP 05.08.
Raw measurements on a radio block basis
For EGPRS (that is during an EGPRS DL TBF), the MS shall calculate the following values, for each radio block (1
radio block = 4 bursts) addressed to it (the DL TBF TFI contained in the radio block must be decoded) :
Mean Bit Error Probability (BEP) of a radio block:
MEAN _ BEPblock =
1 4
BEPburst i
4 i =1
1 4
1 4
BEPburst k BEPburst i
3 k =1
4 i=1
CV _ BEPblock =
4
1
BEPburst i
4 i=1
In the above equations, the BEP is measured on a burst basis by the MS before channel decoding.
Averaging of the raw measurements on a TS basis
The raw measurements made by the MS on a radio block basis are averaged by the MS per TS (TN in the below
equations) and per modulation type (GMSK (MCS1 to MCS4), 8-PSK (MCS5 to MCS9)) as follows:
with
xn
x
) MEAN_BEP_T
Nn1 + e n MEAN_BEP
block,n
Rn
Rn
x
x
CV_BEP_TN n = (1 e n ) CV_BEP_TN n 1 + e n CV_BEPblock,n
Rn
Rn
MEAN_BEP_T
Nn = (1 e
R n = (1 e) R n1 + e x n , R 1 = 0
MS
MFS
EGPRS Packet DL Ack/Nack
(Mean_BEP, CV_BEP)
IR
current CS
Link
adaptation
Average Power
Decrease in 8-PSK
link adaptation
tables
new CS
xn denotes the existence of quality parameters for the nth block, i.e. if the radio block is intended for this MS. xn values 1
A MS shall report the overall MEAN_BEP and CV_BEP (instead of reporting the RXQUAL and SIGN_VAR values) per
modulation type (that is GMSK_MEAN_BEP, GMSK_CV_BEP and/or 8-PSK_MEAN_BEP, 8-PSK_CV_BEP depending on the
received blocks since the last channel quality report sent to the network) averaged over all allocated channels
(timeslots) as follows:
MEAN_BEP
n =
R
j
(j)
n
(j)
MEAN_BEP_T
Nn
(j)
Rn
The BTS measures for each UL burst the BEP and calculates for each UL radio block (4 bursts) the Mean_BEP and the
CV_BEP = Std_BEP / Mean_BEP. The Mean_BEP and the CV_BEP are reported on a radio block basis by the BTS to the
MFS.
MS
BTS
MFS
UL RLC block
CV_BEP, Mean_BEP
computation
Averaging
IR
current CS
Link
adaptation
new CS
Average Power
Decrease in 8-PSK
link adaptation
tables
The MFS verify if a MCS change is needed each time it receives new
APD value
GMSK
GMSK tables
GMSK / 8-PSK
MCS 1..4
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
NO
IR activated
APD value
8-PSK
GMSK
8-PSK tables
GMSK tables
MCS 5..9
MCS 1..4
GMSK / 8-PSK
8-PSK
8-PSK tables
MCS 5..9
TRX ranking
CS traffic
TRX ranking
for PS traffic
TRX characteristics
TRX transmission
pool set-up
A TRX transmission pool groups, together extra Abis nibbles for one TRX
The biggest TRX transmission pools are allocated to the TRXs having the highest
ranking for PS traffic.
p.90 et p.91
Example:
5 TREs in a cell
1 G4-HP TRE
2 G4-MP TREs
2 G3 TREs
5 TRXs
TRXa, TRXb, TRXc, TRXd: TRX_PREF_MARK = 0 (PS capable)
TRXe: TRX_PREF_MARK > 0 (non PS capable)
3 DR TRXs
Pool types
1 type 4
1 type 2
2 type 1
TREs
Dual Rate
usage
associated
TRXs
PS capable
TRX ranking
G4 - HP
G4 - MP
G4 - MP
G3
G3
FR
FR
DR
DR
DR
TRXa
TRXb
TRXc
TRXd
TRXe
1
2
3
4
associated
transmission
pool
type
type
type
type
4
2
1
1
For EGPRS:
TRX type (n=1 to 5), received from BSC
- HW PS
Hardware PS capability of each TRX, received from
capability
- TRX
the BSC
Max_GPRS_CS
type
En_EGPRS (parameter to allow or not EGPRS in the
cell), received from the BSC
TRX GPRS
Max_GPRS_CS (parameter which gives the highest
usable CS in the cell), received from the BSC
capability
Max_EGPRS_MCS (parameter which gives the highest
usable MCS in the cell)
GPRS capability
(CS2/CS3/CS4)
p.119
O&M
BSC
En_EGPRS
Max_EGPRS_MCS
TRX EGPRS
capability
EGPRS capability
(MCS 1-MCS 9)
than on low class TRXs. This ratio has to take into account the maximum
throughput which can be offered by each class of TRX
specific TRX selection for EGPRS TBFs
1 1 168
This state is meaningful only for non-EGPRS capable MSs and only in the
UL direction.
Full : for GPRS TBF : GPRS + EGPRS ts are counted, because some EGPRS TBF on GPRS PDCH are using GMSK
MCS.
PDCH used in DL direction by 8-PSK capable EGPRS TBF, i.e PDCH does
When meaningful, it overwrites active and busy states but not the
full state
Avoids multiplexing of UL GPRS TBF and DL EGPRS TBF, in order
to not reduce the EGPRS throughput
DOWNLINK
UPLINK
MAX_DL_TBF_SPDCH
MAX_UL_TBF_SPDCH
Allocated Active
Full
Allocated Active
[EGPRS]
Full
[EGPRS]
One SPDCH has one state per direction (i.e., one state for the UL, one state for the DL). This state depends on the type of the MSs (EGPRS
capable or non-EGPRS capable) for which the radio resource (re)-allocation algorithm is called.
radio resource allocated to the MFS, but associated transmission resources are not allocated (i.e., the PDCH is not established).
All the following states are related to established PDCHs:
empty:
active:
For GPRS TBF: at least one established TBF and the number of established TBFs (GPRS + EGPRS) is smaller than
N_TBF_PER_SPDCH.
For EGPRS TBF: at least one established EGPRS TBF and the number of EGPRS TBFs (1) is smaller than N_TBF_PER_SPDCH.
busy:
For GPRS TBF: the number of established TBFs (GPRS and EGPRS TBFs) is greater or equal to N_TBF_PER_SPDCH, but smaller
than MAX_UL_TBF_SPDCH/MAX_DL_TBF_SPDCH.
For EGPRS TBF: the number of established EGPRS TBFs (1) is greater or equal to N_TBF_PER_SPDCH, but smaller than
MAX_UL_TBF_SPDCH/MAX_DL_TBF_SPDCH.
full:
For GPRS TBF: the number of established TBFs (GPRS + EGPRS TBFs) is equal to MAX_UL_TBF_SPDCH/MAX_DL_TBF_SPDCH.
For EGPRS TBF: the number of established EGPRS TBFs (3) is equal to MAX_UL_TBF_SPDCH/MAX_DL_TBF_SPDCH.
EGPRS (2)
PDCH used in the DL direction by an 8-PSK capable EGPRS TBF (i.e., the PDCH does not belong to a class 1 TRX).
This state is meaningful only for non-EGPRS capable MSs and only in the UL direction.
When meaningful, it overwrites active and busy states (but not the full state).
(1): Only EGPRS TBFs are taken into account to avoid to establish EGPRS TBFs on PDCHs with a low EGPRS capability, because of
GPRS TBFs.
(2): The aim of this new state is to avoid multiplexing UL GPRS TBF and DL EGPRS TBF, in order not to reduce EGPRS throughput.
(3): Only EGPRS TBFs are taken into account to avoid radio resource allocation failure because of the restricted list of EGPRS
capable TRXs.
throughput
Principle:
maximum number of EGPRS TBFs, the other EGPRS capable TRXs are not
taken into account by the algorithm
mode
MAX_TBF_PDCH_Current(TRXi) : maximum number of EGPRS TBFs per
PDCH, currently allocated in TRXi
N_TBF_PDCH_MCSi_MCSj
It defines for each EGPRS TRX capability (MCSi) in the cell the number of
EGPRS TBFs per PDCH beyond which it becomes more interesting to serve
upcoming EGPRS MSs on TRXs with a lower EGPRS capability (MCSj).
Max_PDCH_Throughput_MCSi / Max_PDCH_Throughput_MCSj
with Max_PDCH_Throughput_MCSx is the maximum theoretical throughput that
can be achieved at RLC/MAC per PDCH using MCSx encoding
All the values between MCS2 and MCS9 are possible because of the
N_TBF_PDCH_MCSi_MCSj
1
1
2
1
2
1
2
4
1
2
4
1
2
2
5
N_TBF_PDCH_MCSi_MCSj are internal parameters which define for each EGPRS TRX capability, in the cell, the
number of EGPRS TBFs per PDCH beyond which it becomes more interesting to serve upcoming EGPRS MSs on
TRXs with a lower EGPRS capability.
This value depends on the throughput gap between 2 consecutive TRXs inside the ordered (according to TRX
Rank) list of EGPRS capable TRXs.
N_TBF_PDCH_MCSi_MCSj = Max_PDCH_Throughput_MCSi DIV Max_PDCH_Throughput_MCSj
Example
N_TBF_PDCH_MCS9_MCS5 = 2
N_TBF_PDCH_MCS5_MCS2 = 2
CELL START
MAX_TBF_PDCH_Current (TRXi) = 0
(with i = a, b, c, d or e )
MAX_TBF_PDCH_Current (TRXa)
< N_TBF_PDCH_MCS9_MCS5
TRXa
MAX_TBF_PDCH_Current (TRXa)
< N_TBF_PDCH_MCS9_MCS5
MAX_TBF_PDCH_Current (TRXa)
= N_TBF_PDCH_MCS9_MCS5
MAX_TBF_PDCH_Current (TRXb)
< N_TBF_PDCH_MCS5_MCS2 _
OR
MAX_TBF_PDCH_Current (TRXc)
< N_TBF_PDCH_MCS5_MCS2 _
MAX_TBF_PDCH_Current (TRXb)
= N_TBF_PDCH_MCS5_MCS2 _
AND
MAX_TBF_PDCH_Current (TRXc)
= N_TBF_PDCH_MCS5_MCS2 _
IMPORTANCE
HIGH
LOW
1 1 176
A.
B.
C.
D.
E.
F.
IMPORTANCE
HIGH
LOW
IMPORTANCE
HIGH
LOW
The SPDCH pre-allocated and established for the fast initial (E)GPRS access
The MPDCH represented by the parameter Nb_TS_MPDCH
IF EN_FAST_INITIAL_GPRS_ACCESS = 1 (true)
MIN_PDCH - Nb_TS_MPDCH - 1 SPDCH are requested to the BSC and preallocated on the TRX with the highest priority
flag to indicate whether or not one Slave PDCH for (E)GPRS traffic usage
1 1 182
C/I = 13 dB
C/I = 9 dB
Distance
CS-2
RL/MAC net
Data Throughput 12
(kbit/s) 10.8
CS-1
8
7.2
Note: the throughput values are ETSI requirements, the C/I values are valid for TU3, SFH enabled
Depending on C/I, CS2 wont provide the same tput (due to lost packets and retransmissions, the useful tput
decreases down to 10.8)
For instance MCS9 can vary from 45 59 kbps
If performing a planning with C/I > 12db : only MS with good C/I will get enough C/I to have max tput.
It is possible to link the C/I and RXLEV to simplify analysis (rxlev = f(C/I), depending on netwpork planning)
Packet data
throughput (ETSI)
Maximum (error free
transmission) on Air
Interface
MCS-9
MCS-8
MCS-7
MCS-6
MCS-5
MCS-4
MCS-3
MCS-2
MCS-1
59.2
54.4
44.8
29.6
22.4
17.6
14.8
11.2
8.8
53.3
49.0
40.3
26.7
20.2
15.9
13.3
10.1
7.9
GPRS
CS-4
CS-3
CS-2
CS-1
20.0
14.4
12.0
8.0
18.0
13.0
10.8
7.2
at BLER=10%
Degradation of RLC
by Level and
Interference
channel
Propagation conditions
TU3(no FH)
PDTCH/MCS-5 dB
PDTCH/MCS-6 dB
PDTCH/MCS-7 dB
PDTCH/MCS-8 dB
PDTCH/MCS-9 dB
TU3(ideal FH)
TU50(no FH)
20
17
18
18
14.5
15.5
14.5
16
17.5
21
23.5
23.5
24
24.5
26.5**
30
32
33
35
28.5
29
30
30
find the minimum required Level and C/I ratio for the reference
error performance, defined by a block error rate Block Error Rate
(BLER) of 10%, the reference performance point
Japanese/Korean behaviour : they use data while in subways and trains. Appearing in France due to tv
online.
kbit/s
20
CS1
CS2
16
12
8
4
0
3dB
7dB
11dB
15dB
19dB
23dB
27dB
Throughput curve as required by ETSI for CS-1and CS-2, typical urban environment with MS speed 3 km/h TU3 with SFH
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
C/I
since saturation occurs. e.g. for CS-1 starting with 7.2 kbit/s at a C/I
ratio of 9dB
With an increasing C/I ratio the data throughput increases only little up
to its maximum value of 8kbit/s (saturation point)
Due to this saturation effect, a further increase of the C/I ratio does
Level (dBm)
C/I = 13 dB
C/I = 9
dB
Level of neighbor-cell
Distance
CS-2
CS-1
RL/MAC net
Data Throughput
(kbit/s)
12
10.8
8
7.2
ETSI requirements and Alcatel values for C/Ico and C/Iadj for CS and GPRS
(PDCH) GSM 900 (Requirement for GMSK modulation: C/Iadj = C/Ico 18dB)
In general: With higher coding scheme, higher C/I ratios required
GPRS functionality more sensitive against interference
GSM 900
Circuit
switched
C/I cochannel
ETSI
C/I adjchannel
Alcatel
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
TU3
TU3
ideal FH
13
-9
Packet switched
CS1
TU50
TU50
ideal FH
TU3
TU3
ideal FH
10
15
-5
-9
-8
-9
11.5
6.7
7.5
-9
-13
-12
CS2
TU50
TU50
ideal FH
13
14
13
-3
-5
-4
-5
6.5
13.1
10.3
11.1
10.8
-13
-6
-8.8
-8.2
-9
Ideal FH : hopping on 4 or more frequencies with at least 800kHz separation between each channel offers
the "ideal FH" diversity gain (4 to 5 dB)
18
16
CS4
CS3
CS2
CS1
13Jul2000 09:45:44
14
Throughput
Parameters :
GPRS
C/I Throughput
Co-channel
Interferer
TU 50
no FH
12
10
8
6
4
2
0
5
10
15
C / I c o [dB]
20
25
CS4 can't resist to interference, even with high C/I, it doesn't reach the saturation point. Expect high
retransmission % when using CS4.
For each C/I, a typical tput can be expected. CS adaptation gives flexibility in case of radio conditions
changes.
At start of a session, which CS to choose?
How would the curve looks like if TU3 was used ? (C/I scale would be squeezed)
30
1 1 191
Traffic Analysis
Field strength prediction
Mutual interference calculation
GSM/GPRS frequency planning
Cell specific interference calculation
TRX assignment to GPRS service
Objectives
Traffic Analysis
PS Traffic
User Profile
Market applications
Customer questionnaire
Traffic model: Example
- Traffic tool
Traffic Analysis
PS Traffic
User Profile
User Behavior
Market applications
Customer questionnaire
Straight forward
Erlang C
Traffic tool
User behavior
Market applications : what is proposed to customers : video on demand ? Live tv ? Mmp games ?
U s e r p ro file
U s e r b e h a v io r
M a r k e t a p p lic a tio n s
C u s to m e r
Q u e s tio n n a ire
a n d s e rv ic e d is trib u tio n s
T ra ffic m o d e l
T ra ffic c a lc u la tio n
A user profile defines a typical user for packet data services, using a
simple, e.g. two profiles can be introduced, business and private user
Market applications
Different services are possible for packet data use e.g. new designed
Uplink bias applications : MMS, ftp upload. Create problem for dimesionning ? No, because MMS are
uploaded and then downloaded. They create equal traffic in both ways.
Current Ms use 2ts in uplink, class 11 and 12 are coming (up to 4 TS in uplink, but still simplex.
Duration and occurrence time of busy hour (BH), assumption busy hour is
number
GPRS user profiles percentage (%), related to the total GPRS subscriber
number
Geographical percentage distribution (%) of GPRS user profiles related to
morphostructure
Daily GPRS user profile activity (days/month)
Core network : can provide statistics per user (pdp context activation, gprs attach, APN usage, etc)
Which interface : Gb (mfs-sgsn) , Gn (sgsn-ggsn)
Special tools : astelia
Customer questionnaire
Speech traffic : from 10mErl to 25 mErl (depends on network age and area covered)
6. Busy hour mix (BHM) : at busy hour, split of different types of traffic
GPRS user profiles percentage (%), related to the total GPRS subscriber number
geographical percentage distribution (%) of GPRS user profiles related to
morphostructure
business
User Profile
Market Application
Update/Month
E-mail+Attachment
mail/Month
WWW
Information (e.g.
Location, event,
transportation services)
e-Commerce
(e.g. On-line shopping)
Audio (MP3)
e.g. (Access audio files on
the net)
TOTAL
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
Private
Business
Kbytes
Mbytes/Month
Kbytes
Mbytes/Month
Pages/Month
Kbytes
Mbytes/Month
info/Month
Kbytes
Mbytes/Month
usage/Month
Kbytes
Mbytes/Month
Min/Month
Kbytes/Min
Mbytes/Month
Mbytes/Month
20
0.117
24
150
30
3.516
0.0878
100
100
25
2.441
25
60
10
0.977
20
60
1.464
1.17
75
75
0.586
0.146
1024
8.124
2.380
User mapping
Behavior in GPRS -> Packet switched service for different users on one
timeslot.
User
User 3
User 2
User 1
Timeslot
1
TS 2
TS 3
TS 4
TS 5
TS 6
TS 7
TS 8
TRX
User mapping should be quite low, in order to allow a high throughput but requires higher capacity
5.11 Multi-Service
1 1 205
One user can use different services. So one user is not directly
S e r v ic e 2
e .g . F T P
S e r v ic e 1
S e r v ic e 3
e .g . H T T P
e .g . W A P
U se r
Queue Delay
Quantile
Bit rate
Queue delay : how long a user can wait before disconnecting ? Usually for data, user can wait up to 30s.
Quantile : percentage of throughputs measures that are within a certain range (to check) STANDARD
DEVIATION !!
Traffic tool
User mapping
Multi-service
mapping
Erlang C for PS
Traffic Model
methods
It calculates for the whole data volume, sum of all users data, the
number of PDCH TS needed to transfer this data volume, regardless of
data transfer peaks
This method is not taking into account parallel data transfer, which is
the benefit of packet transfer (GPRS).
So no service attempt queuing and no service multiplexing is taken into
account by this method.
A calculation method to get in the first step of GPRS planning an idea of
minimum needed PDCH TS.
Erlang C calculation
gives for a required service attempt probability (Quantile) and the queue
The traffic tool is the most exact method to calculate the needed PDCH
WAP users: 60
WEB users: 180
MMS users: 360
= 1.6 kbit/s
= 16 kbit/s
= 32 kbit/s
conditions
But assumption is : all users can bare to wait for 3600 sec to finish their download
WAP service: bit rate = 5 kbit/s for 90% Quantile and 2s queue delay
WEB service: bit rate = 30 kbit/s for 90% Quantile and 2s queue delay
MMS service: bit rate = 30 kbit/s for 90% Quantile and 2s queue delay
The following results calculation can be done with an Erlang C tool. The
9 0 .0 %
MU =
RO =
9 0 .0 %
30
1 .8 7 5 0
Bit rate
Quantile
Subscribers
2 s
1 .8 7 5 0
Bit rate
2 s
Quantile
PDCH =
180
0 .5 3 3 3
360
1 .0 6 6 7
MU =
Subscribers
PDCH =
RO =
40
4 0R L A N G
2
E
C
Volume@BH
WEB
ER LAN G C
Page size (Kbytes)
WAP
MMS
Volume@BH
30
(user capacity)
1 1 218
6.1 General
1 1 219
With the input from GPRS traffic calculation the GPRS Design
Number of timeslots which may be reserved for GPRS in normal and high load
state of the BSC
Number of timeslots which have to be reserved exclusively for GPRS
Number of remaining timeslots for CS traffic
=> Standard BTS configuration
The result of traffic analysis gives the standard BTS configuration for
the different traffic areas. The traffic areas are most commonly linked
to a specific morpho class
Next steps:
1. GPRS Field strength prediction is done as for the GSM network planning
[A9155]
design changes
site
lowering
site densification
network expansion/enhancement strategies (like Dual Band)
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
Needs an higher C/I to ensure better tput. Redo a frequency planning with greater constraints on C/I
Best carrier = the carrier with the less interference BCCH ? Normally, yes.
BCCH
TCH
Hopping, (PC)
6.3 Throughput
1 1 224
throughput
GPRS cells are designed in respect to the
desired data transmission (throughput)
In general, the link budget calculation is the same like for CS design
Attention has to be paid to the hardware related values:
BTS output power & receiver sensitivity according to the coding scheme
MS output power & receiver sensitivity according to the coding scheme
body loss, for PS: 2 dB, due to the fact, that for the most PS applications
the MS is not close to the body , but on an other, from the propagation
point of view unfavorable position (e.g. on the table)
interference margin: minimum 3 dB (urban and dense urban area up to 5
dB, depending of the frequency re-use), due to the high dependency of
the PS service on C/I
(lognormal) fading margin can be added to increase the coverage
probability from 50% up to 95%; e.g. assuming standard deviation sigma =
7 dB =>fading margin:1.65 sigma ~11 dB
TX
Internal Power:
Isol.,Comb.,Filter Loss:
Output Power
Cable,Connectors
Loss:
Body Loss:
Antenna Gain:
Eff. Isotr. Rad. Power:
Uplink
33.00 dBm
0.00 dB
33.00 dBm
0.00 dB
Downlink
45.44 dBm
5.01 dB
40.39 dBm
3.00 dB
Uplink
33.00 dBm
0.00 dB
33.00 dBm
0.00 dB
Downlink
45.44 dBm
5.05dB
40.39 dBm
3.00 dB
Uplink
33.00 dBm
0.00 dB
33.00 dBm
0.00 dB
Downlink
45.44 dBm
5.05dB
40.39 dBm
3.00 dB
3.00 dB
0.00 dBi
30.00 dBm
0.0 dB
18.00 dBi
55.43 dBm
2.00 dB
0.00 dBi
31.00 dBm
0.00 dB
18.00 dBi
55.43 dBm
2.00 dB
0.00 dBi
31.00 dBm
0.00 dB
18.00 dBi
55.43 dBm
Uplink
-111.00
dBm
0.00 dB
3.00 dB
Downlink
-102.00
dBm
3.00 dB
0.00 dB
Uplink
-109.00
dBm
0.00 dB
3.00 dB
Downlink
-102.00
dBm
2.00 dB
0.00 dB
Uplink
-105.00
dBm
0.00 dB
3.00 dB
Downlink
-98.00 dBm
18.00 dBi
3.00 dB
3.00 dB
0.0 dB
-126.00
dBm
0.00 dBi
0.00 dB
3.00 dB
0.0 dB
-96.00
dBm
18.00 dBi
3.00 dB
3.00 dB
0.0 dB
-124.00
dBm
0.00 dBi
0.00 dB
3.00 dB
0.0 dB
-97.00
dBm
18.00 dBi
3.00 dB
3.00 dB
0.0 dB
-120.00 dBm
0.00 dBi
0.00 dB
3.00 dB
0.0 dB
-93.00 dBm
RX
Rec. Sensitivity:
Body Loss:
Cables, Connectors
Loss:
Antenna Gain:
Diversity Gain:
Interference Margin
Fading Margin
Isotr. Rec. Power:
Balance
Uplink
156 dB
Downlink
151.43 dB
Uplink
155 dB
Downlink
152.43 dB
Uplink
151 dB
2.00 dB
0.00 dB
Downlink
148.43 dB
Legend (dB)
> 25 dB
> 16 dB
> 13 dB
> 9 dB
< 9 dB
C/I reduction
Legend (dB)
> 25 dB
> 16 dB
> 13 dB
> 9 dB
< 9 dB
software release:
GPRS/EDGE shall be mapped on the TRX(s) with the best radio quality
PS capable TRXs have to be preferentially mapped (from the best choice to the worst) on:
- FR, HP, EGPRS capable TREs
(When PS_Pref_BCCH_TRX = TRUE, the TRX supporting the BCCH is mapped on the best TRE)
scheme
Throughput
CS-4 coverage
CS 3
CS 2
CS 1
7..13 kbit/s
< 7 kbit/s
a location area.
The location of a MS in STANDBY state is known in the SGSN on a RA
level.
characterized by:
range 0255
range 07
Allows the mobile to quickly check if change of RA : ra colour change (because SI3 update frequent)
SI 13 : once in 1.9s
LA planning
RA planning
Routing area color : shouldn't be the same between two areas that are next to each other
across a LA border (e.g. 1 cell from LA1 and 2 cells from LA2)
a RA can contain one or several cells
one cell can not belong to two RA
cells from one BTS can be allocated to different RA
the maximum number of RA in a LA is 256
it is possible to reuse the RA_Colour in a LA
two adjacent RA in a LA must have different RA_Colour
RA 1
RA 2
RA 3
RA_C: 0
RA_C: 1
RA_C: 2
RA 4
RA 5
RA 6
RA_C: 3
RA_C: 4
RA_C: 5
RA 7
RA_C: 6
RA 8
RA_C: 7
RA 1
RA 2
RA 3
RA_C: 0
RA_C: 1
RA_C: 2
RA 4
RA 5
RA 6
RA_C: 3
RA_C: 4
RA_C: 5
RA 8
RA 9
RA_C: 6
RA_C: 7
RA_C: 0
RA 10
RA 11
RA 12
RA_C: 1
RA_C: 2
RA_C: 3
RA 7
topic
It is necessary to use GSM
counters in order to
complete the analysis of :
GSM QoS
Impact of GSM on GPRS
GPRS QoS
QoS
GPRS QoS
According to GSM, QoS indicators for the Air interface available for GPRS
Indicators based on counters, computed by the MFS, transferred to the
OMC-R
GSM
GPRS
Note: To obtain the QoS for GPRS, it is not sufficient to study only the GPRS
indicators. There is always an influence of GSM service on GPRS service, e.g.
TCH congestion in GSM could be influenced by high CS traffic or the additional
high packed data traffic.
1 1 248
7.1 General
1 1 249
the network
7.2 MPDCH
1 1 251
static is depending on
1 1 252
Till the penetration rate of GPRS MS, which support master channel feature,
So it is guaranteed that all GPRS mobiles in the network can access for GPRS
service. MS, which do not support MPDCH, cannot access the GPRS service if
MPDCH is enabled. Note: MPDCH can be enabled in network mode of operation:
NMO I and NMO III.
L o w p rio rity fo r G P R S o r
lo w G P R S tra ffic ?
YES
NO MPDCH
NO
S ta tic M P D C H
(D y n a m ic M P D C H )
G P R S sig n a lin g
c o n g e stio n
YES
NO
E n a b le s e c o n d a ry M P D C H s d e p e n d in g o n
G P R S s ig n a lin g n e e d
1 1 253
MPDCH):
If the CS signaling channels CCCH getting overloaded due to high GPRS traffic and
signaling in addition to CS signaling
1 1 254
slot
T1 reallocation of TBF's whose MEGCH link becomes too small (basic
nibbles are allocated to the CS calls)
Fast pre-emption
After T_PDCH_Pre-emption = 4s
Locked PDCH = PDCH's that are required by the BSC to the MFS for CS calls
1 1 255
The strategy of the TBF resource sharing is to use the PDCH resources
in a most effective way, that means not to waste a PDCH just with
one user and therefore to limit the available PS capacity. On the
other hand, the more users (different TBFs) share a PDCH, the less
effective the data flow and the longer the download or upload time is
throughput
E.g. if N_MAX_DL_TBF_PDCH and CS-2 is used, the DL bit rate per MS will be
6.0 kbit/s (=12/2) per used timeslot for this MS
A few multi slot mobiles can occupy all resources with the default value of
MAX_PDCH_PER_TBF. Thus the parameter has to be set, depending from the
expected load and in combination with N_TBF_PER_S/MPDCH to reflect
operators strategy on GPRS QoS.
T1
T2
T3
T4 (new in B8 for EGPRS purposes)
Trigger T1 (target maintain a TBF alive when its PACCH is fast preempted):
Reallocate all impacted TBFs using the pre-empted PDCHs instead of releasing them using the
Packet TBF Release procedure
Trigger T2 (target attempt offering more PDCHs to an MS upon concurrent TBF establishment):
get rid of the concurrence constraints imposed by the multislot class of the MS and an existing TBF
to offer the best throughput, the initial TBF can be moved to other PDCHs
Trigger T3 (target periodically attempt offering more PDCHs to an MS which has a TBF in the
direction of the bias with less PDCHs than it can support according to its multislot class):
take benefit of PDCH resource usage variations in a cell to reallocate the resources granted to a
Mobile Station, in case those resources were not using the full multislot class capabilities of the MS
to offer the best throughput in the direction of the bias and even adapt to bias changes in the
course of a packet transfer
Advantages
Drawback
The allocation process is based on the number of PDCHs that the TBF can
be mapped on a new resource and not on the throughput the TBF will get
on these PDCHs
Consequence: in certain cases, available PDCHs will not be used for TBF
reallocation, whilst using them would have improved the TBF throughput
beginning of a TBF:
1 1 260
NC0
NC1
NC2
MS GMM State
Presence of
the PBCCH
Standby
MS autonomous cell
reselection (NC0 mode)
C1, C2
Ready
MS autonomous cell
reselection (NC0 mode)
C1, C2
Standby
MS autonomous cell
reselection (NC0 mode)
Not supported in B8
Ready
(or RMM Mode = PTM)
Network controlled
reselection (NC2 mode)
C1, C2
C1, C2
GPRS cell adjacencies are same in packet idle mode as in packet transfer
mode
GPRS cell adjacencies are set equal to the GSM cell adjacencies (i.e. the
BA(GPRS) list = BA(BCCH) list )
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
Possible to reselect a cell without GPRS service (if in the target cell GPRS
is disabled)
Recommendation : enable the GPRS service on all cells in order to
prevent a MS to reselect a cell without GPRS support
"NC0" Cell reselection criterion for PBCCH established or not
C2)
Radio Network Planning Impacts
Generally optimized GSM/CS parameters for cell reselection shall be kept also
for PS cell reselection
Default values for the parameters are kept
1 1 262
often pages are changed and the content of the downloaded http
looks like. For Web browsing and WAP applications where the PS
traffic is bursty, the gain of the features to delay TBF release will be
very high
The 3 features are complementary and can be activated
independently from each other. Delays to start download of new LLC
PDU depending on feature
HTTP (clustered web page). The round trip time (RTT) can be shortened
by the availability of an already opened TBF. This, in turn, is affected by
the TBF hold time and the time between pings
So in fact less signaling is needed for e.g. download of successive WAP
pages or HTTP links because there is no need to establish a new TBF
during T_DELAYED_DL_TBF_REL time
T_DELAYED_DL_TBF_REL should be in between of 1.5s up to 2s depending
on available resources in the cell. The higher the TS capacity in a cell is
the higher the value of T_DELAYED_DL_TBF_REL can be tuned
T_NETWORK_RESPONSE_TIME T3192
DL TBF
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
DRX_TIMER_MAX
Non-DRX mode
DL TBF establishment
via PCH or PPCH
of MS paging group
p.82
During the delayed release of the DL TBF, the BSS periodically sends to the MS a DL RLC data block (with a
polling request) containing a Dummy UI Command which is a LLC PDU whose checksum is deliberately
wrong. This LLC PDU is hence discarded by the LLC layer of the MS.
Sending periodically Dummy UI Commands enables the mobile station to request an UL TBF establishment in
a PACKET DL Ack/Nack message if it has data to send, and prevents defense RLC timers from expiring in the
mobile station.
If new DL LLC PDUs are received for that MS, the DL LLC PDUs can be sent immediately on the DL TBF. If
the BSS does not receive any DL LLC PDU during the inactivity period, it releases the DL TBF through the
normal TBF release procedure.
Delayed Downlink TBF release -> Total TBF release time is:
T_DELAYED_DL_TBF_REL = T_DELAYED_DL_TBF_REL_RADIO +
Advantage
throughput improved for reason: long RTT. RTT can be shortened by the
Drawback
After reception of the final block by the MS and after the sending of the
T3192 > MS-BSS roundtrip delay + RRBP maximum duration (120 ms)
T3192 + T_MAX_EXTENDED_UL + round_trip_delay < 5 sec
Default Values
Relative Reserved Block Period : waiting time before UL emission (=> for PACCH) is allowed (cf. USF
mechanism)
RRBP : +3RB, +4RB, +5RB or +6RB (approx)
1 1 267
The MFS establishes a DL TBF on the first available AGCH block (without
The discontinuous (DRX) mode applies when the MS is in packet idle mode. This function allows a MS not to
monitor all PCCCH blocks, but only blocks defined by its paging group. The MS applies existing GSM DRX
procedures if there is no MPDCH.
Remove 0.6 seconds, due to AGCH queuing time. So real time in non-DRX is 1.4s.
1 1 268
8.1 General
1 1 269
than traffic analysis and GPRS network design tasks has to be done
before the GPRS introduction step
All GSM network enhancement features and GSM network problems, mainly
GSM QoS and interference, shall be fixed before GPRS is implemented
1 1 270
no
Actual GSM capacity enough to
cope with GSM and GPRS traffic?
yes
yes
Implement Frequency
Plan
no
Increase capacity
How to reach
GPRS QoS?
GPRS
Introduction
yes
yes
no
Add new GPRS features if needed
RA planning
CAE data generation
GPRS QoS reached?
Considerable features to reach
GPRS QoS target
no
1 1 271
Operator requirements define the needed GPRS capacity and GPRS QoS
per user in relation to specific definitions for user and used service:
Volume @BH (Kbytes)
Page size (Kbytes)
Queue delay (seconds)
Quantile (%)
Bit rate (kbit/s)
1 1 272
TRX assignment to GPRS service and the PDCH planning can be done.
Additional TRX & frequencies must be allocated to the sites with not enough
traffic capacity.
A new frequency planning should be done when a not negligible amount of new
frequencies have to be added to a planning area to fulfill (GSM+GPRS) capacity
requirements.
1 1 273
If new sites after GPRS analysis are required to fulfill operators GPRS
The routing area (RA) planning is a must for GPRS introduction into GSM
1 1 274
Dedicated TRX for GPRS in a cell can be done if TRX number in the cell is
2
Introduction of GPRS Master channels (MPDCH to separate GPRS and GSM
signaling
Open question: Penetration rate of GPRS MS which can decode MPDCH
The parameters for PDCH dynamic allocation (and TBF resource
management) depends on GPRS QoS requirements :
Weaker GPRS requirements more TS for GSM can be reserved with a low
value of MAX_PDCH
1 1 275
calls having good quality will get worse, bad calls will get better. This is
valid for GSM, similar it is valid for GPRS.
CS1 is used in bad conditions, thus it will be improved if FH is
introduced.
CS4 is used in very good conditions, which are more seldom in a hopping
network. Thus CS4 will perform less good and will be used more seldom.
The overall gain of CS1 - CS3 will depend on the C/I situation before and
after FH.
CS adaptation parameters can be tuned more optimistic in respect to
throughput and Coding Scheme if FH is used:
performance.
started:
9.2 -cell
1 1 278
Solution:
1 1 279
The strategy is also valid for a different assumption, but this assumption is
more probable.
1 1 280
Two Approaches
1 1 281
Class B and C MSs can make interband cell reselection during data
transmission
if C2 parameters are used in order to give a higher priority to a given layer for
circuit mode
the same priority is obtained for packet mode
thus GPRS can not be kept in 900 MHz layer, if GSM MS is sent to 1800 MHz
layer
1 1 282
TRXs of one band are allocated to the outer zone and the TRXs of the
if C2 parameters are used in order to give a higher priority to a given layer for
circuit mode the same priority is obtained for packet mode
if GSM MS is sent to inner zone in dedicated mode, the GPRS service cannot be
ensured in the inner zone
1 1 283
inner zone is smaller than the outer zone and keeps the disturbing
carriers
concentric cells which are disturbed by other cells:
the inner zone and outer zone carriers have the same output powers;
nevertheless, the size of the inner zone is dimensioned by proper
parameter setting
the same recommendation holds: the TRX for PS traffic must be
configured in the outer zone of the concentric cell
1 1 284
10 E-GPRS
10 E-GPRS
EDGE timeslot
8PSK TX power
Reference sensitivity
GSM900
GSM1800
15 W or 41.76 dBm
12 W or 40.8 dBm
(tolerance 0.5 + 0.5 dB)
(tolerance -0.5 + 0.5 dB)
-112 dBm (static MCS-1)
108 dBm (TU50 ideal FH, MCS1)
-104 dBm (static MCS-5)
- 100 dBm (TU50 ideal FH, MCS5)
10 E-GPRS
MCS-9
60
MCS-8
MCS-7
MCS-6
Throughput [kbps]
50
MCS-5
MCS-4
MCS-3
40
MCS-2
MCS-1
30
20
10
0
-110
-105
-100
-95
-90
Level [dBm]
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
-85
10 E-GPRS
60
MCS-9
MCS-8
MCS-7
MCS-6
MCS-5
MCS-4
MCS-3
MCS-2
MCS-1
Throughput [kbps]
50
40
30
20
10
0 0
10
15
20
25
30
C/Ico(dB)
EVOLIUM BSS - GPRS and EGPRS
Radio Network Planning
35
1 1 288
25 mErl/Sub urban
6. Busy hour occurrence for speech traffic and packet data traffic:
Speech traffic busy hour: 8-11, 13-17 and 18-22 oclock
Packet data service hours: Business: 8-11 and 14-17, private 14-20 oclock
9. PS user behaviour/distribution:
22 days,
30 days
GPRS user profiles percentage (%), related to the total GPRS
subscriber number = 7%: 2% private and 5 % business
Geographical percentage distribution (%) of GPRS user profiles related to
morphostructure:
urban = 70% business, 50% private
rural = 30% business, 50% private
10. Number of BTS in the existing network
2000 BTSs
11. Distribution of existing BTS to morphoclasses:
1200 BTSs in urban,
800 in rural
12. Number of TRX/BTS, in accordance to morphoclass:
3*2 configuration in urban, 3*1 configuration in rural
private
calculated
Due to the different network capacity in urban and rural area and
the different ratio of business and private users in the area, the
GPRS and speech subscriber are split to urban and rural area
Packet data
Speech
Traffic [Erlang]
First step: throughput demand per user profile calculation (due to the
packet data traffic per month is user profile depending (e.g. not during the
whole month, like speech traffic)
PS traffic is not to be spread over the whole day, there are now service
hours/day, depending on the user profile
Packet data traffic occurs only during the service hours.
Packet data traffic is homogeneously distributed over the service hours,
During service hours, the user is continuously active (worst case calculation)
1. CS traffic is maximum
Exception:
CS
PS
Use
In our example, the service hours for PS traffic are in total 6 hours,
but from 14 to17 oclock business and private subscriber will make
data traffic at the same time
Thus the busy hours for data traffic are these 3 hours
It is also visible, that during that time, also for speech traffic a busy
time occurs
Busy hour: GPRS traffic dimensioning will be 14 to17
Speech
Packet
11
1314
Business
Private
17
20
22
Traffic/month [Mbyte]
Traffic/month [kbit]
traffic volume demand /day
[kbit]
throughput demand /service
hours [kbit/s]
throughput demand /busy hours
[kbit/s]
Urban area
Business
Private
4900
300
5200
Rural area
Business
Private
2100
300
2400
Private
2.380
=19964.88
665.49
for 30 days
0.03
6 serv. hours
0.03
during 3 busy hrs
For CS traffic:
Total BTS
BTS
Configuration
Capacity/Erlang 2%
Blocking
CS traffic demand
Urban area
1200
3x2
29520
=1200*3*8.2
20000
2000
Rural area
800
3x1
6960
=800*3*2.9
4000
throughput capacity
For this dimensioning example it is appropriate to consider the result of
the cell ranges dimensioning example
According to it, 59% of the cell area is operated in CS-2 and 41% in CS-1
mode
The cell throughput capacity can be estimated with a data rate of
(0.41*8+0.59*12) kbit/s = 10.36 kbit/s per timeslot
use:
Example:
Total BTS
BTS
Configuration
Total Available TS, BCCH not incl.
Available TS, BCCH not incl.
MAX_PDCH_GROUP = 8 TS
Available TS if BSC in HIGH_LOAD
MAX_PDCH_HIGH_LOAD = 1 TS
Capacity [kbit/s]
(10.36 kbit/s /TS)
Capacity [kbit/s]
if BSC in HIGH_LOAD (10.36 kbit/s /TS)
Urban area
1200
3x2
54000
=(7+8)*3*1200
28800
=8*3*1200
3600
=28800/8
298368
=28800*10.36
37296
=3600*10.36
2000
Rural area
800
3x1
16800
=7*3*300
16800
=7*3*800
2400
=16800/7
174048
24864
switched design
For the busy hour, the BSC is in high load situation, i.e the maximum
of PDCHs is equal to MAX_PDCH_HIGH_LOAD (resource control)
The following table gives the CS capacities based on a blocking
probability of 2% (in Erlang), according to the amount of allocated
timeslots for GPRS in BSC high load situation
Amount
of TRX
1 TRX
2 TRX
3 TRX
4 TRX
5 TRX
6 TRX
Amount
SDCCH
1
2
3
4
4
5
Amount
TCH
+PDCH
7
14
21
28
36
43
2.93
8.2
14.03
20.15
27.34
33.75
2.27
7.4
13.18
19.26
26.43
32.83
1.65
6.61
12.33
18.38
25.52
31.91
Amount PDCH
3
4
1.09
5.84
11.49
17.50
24.62
30.99
0.6
5.08
10.65
16.63
23.72
30.08
0.2
4.34
9.82
15.76
22.82
29.16
0.02
3.62
9.01
14.89
21.93
28.25
0
2.93
8.2
14.03
21.03
27.34
MAX_PDCH_Group = 8 or 7
MAX_PDCH_HIGH_LOAD = 1
Speech
Packet
data
number of BTS
Configuration
Capacity/Erlang @2 % Blocking
Capacity/Erlang @2% Blocking and 1 PDCH
CS traffic demand [Erl]
Capacity [kbit/s] (10.36 kbit/s /TS)
Capacity [kbit/s] if BSC in HIGH_LOAD
(10.36 kbit/s /TS)
PD busy hour throughput demand [kbit/s]
2400
Conclusions:
shrink the cell size of the serving cell (e.g. introduce downtilt) and
Switch
to notes
Access Point
Name view!
ALMAP:
Protocol
Packet Control Unit
AS: Alpha Server (Compaq)
PDCH: Packet Data CHannel
BG: Border Gateway
PDN: Packet Data Network
BSC: Base Station Controller
PDP: Packet Data Protocol (IP or X25)
BSS: Base Station Subsystem
PDU: Protocol Data Unit
BSCGP: BSC-GPRS Protocol
PPCH: Packet- Paging CHannel
BSSGP: BSS-GPRS Protocol
PRACH: Packet- Random Access CHannel
BVCI: BSSGP Virtual Connection Identifier
PS: Packet Switching
CCBS: Customer Care and Billing Center
P-TMSI: Packet- Temporary Mobile Subscriber
CCU: Channel Codec Unit
Identity
CDR: Call Detail Record
PVC: Permanent Virtual Circuit
CG: Charging Gateway
P-VLR: Packet- Visitors Location Register
CS: Circuit Switching
QoS: Quality of Service
DHCP: Dynamic Host Configuration Protocol
RA: Routing Area
DL: Down Link
RIP : Routing Information Protocol
DLCI= Data Link Connection Identifier
RLC: Radio Link Control
DNS: Domain Name System
RADIUS: Remote Authentication Dial In Use
EDGE: Enhanced Data rates for GSM Evolution
Service
FUMO : Frame Unit Module
RRDTUF : Roaming Restriction Data Towards
FR: Frame Relay
Unknown Foreign PLMN
GPRS: General Packet Radio Service
RRM: Radio Resource Management
GGSN: Gateway GSN
RSZ : Regional Subscription Zone
GMM: GPRS Mobility Management
SGSN: Serving GSN
GR: GPRS Register
SM: Session Management | Short Message
GSL: GPRS Signaling Link
SMS: Short Message Service
GSM: Global System for Mobile communication
SMS-C: SMS-Center
GSN: GPRS Support Node
SNDCP: Sub Network-Dependent Convergence
GSS: GPRS
Sub-System
Protocol
EVOLIUM
BSS - GPRS
and EGPRS
All Rights Reserved Alcatel-Lucent 2007
GTP:
GPRSPlanning
Tunneling Protocol
SNMP: Simple Network Management Protocol
Radio
Network
HLR: Home Location Register
SNS: Sub-Network Service layer
HSCSD: High Speed Circuit-Switching Data
TBF: Temporary Block Flow
IMSI: International Mobile Subscriber Identity
TC: Trans Coder
IP: Internet Protocol
TCH: Traffic CHannel
ISDN : Integrated Service Digital Network
TCP: Transmission Control Protocol
ISP: Internet Service Provider
TDMA: Time-Division Multiplexing Access
LAN: Local Area Network
TFI: Temporary block Flow Identifier
LLC: Logical Link Control
TID: Tunnel IDentity
MAC: Medium Access Control
TLLI: Temporary Logical Link Identity
MFS: Multi-Bsc Fast packet Server
TMN: Telecommunication Management Protocol
MNRG: Mobile Not Reachable for Gprs
TS: Time Slot
MS: Mobile Station
UDP: User Datagram protocol
MSC: Mobile Switching Center
UL: Up Link
MT: Mobile Terminal
UMTS: Universal Mobile Transmission System
NE: Network Element
WAP: Wireless Application Protocol
NMC: Network Management Center
WAN: Wide Area Network
NNM: Network Node Manager
NRPA : Network Requested PDP Context
Activation
NSAPI: Network Service Access Point Identifier
NSC: Network Service Control layer
NSEI: Network Service Entity Identifier
NSS: Network Sub-System
NS-VC: Network Service- Virtual Circuit
NTP: Network Time Protocol
DB : On Demand Bandwidth
OMC: Operation & Maintenance Center
OS: Operation System
PAGCH: Packet- Access Grant Channel
PCCCH: Packet- Common Control Channel
APN:
PCO:
PCU:
1 1 307
End of Module
EVOLIUM BSS GPRS and EGPRS